Package request: wmstickynotes

Project description
A sticky note application; pretty handy to label each virtual desktop.
Cf.
https://manpages.ubuntu.com/manpages/focal/man1/wmstickynotes.1.html
Metadata

homepage URL: https://sourceforge.net/projects/wmstickynotes/
source URL: https://sourceforge.net/projects/wmstickynotes/files/wmstickynotes/wmstickynotes-0.7.tar.gz/download
license: GNU General Public License version 2.0 (GPLv2)
platforms: Linux, at least

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

Wow. Last updated June 2015 — practically abandonware. Might consider packaging if there's enough demand (also, this uses X11, so it's pretty much Linux-only for now)

Thanks, I'll try your solution.
In terms of alternatives, try them, then you will feel that wmstickynotes
was amazing at doing the job.
On Mon, Nov 25, 2024 at 9:30 PM Leah Amelia Chen @.***>
wrote:

Since I'm not exactly sure of the utility of this beyond a select few —
seriously there are so many modern alternatives — I'm not making a PR for
this but you can take the derivation if you need to (perfectly PR-ready if
you decide to PR it yourself)
{
lib,
stdenv,
fetchzip,
pkg-config,
gtk2,
versionCheckHook,}:stdenv.mkDerivation (finalAttrs: {
pname = "wmstickynotes";
version = "0.7";
src = fetchzip {
url = "mirror://sourceforge/wmstickynotes/wmstickynotes-${finalAttrs.version}.tar.gz";
hash = "sha256-F/eukXXOCBP4zzoIJxmK1ufWunxgPeep7lsWmT055PI=";
};
nativeBuildInputs = [ pkg-config ];
buildInputs = [ gtk2 ];
doInstallCheck = true;
nativeInstallCheckInputs = [ versionCheckHook ];
meta = {
description = "Dockapp for keeping small notes around on the desktop";
homepage = "https://sourceforge.net/projects/wmstickynotes/";
license = with lib.licenses; [ gpl3Only ];
maintainers = with lib.maintainers; [ pluiedev ];
platforms = lib.platforms.linux;
mainProgram = "wmstickynotes";
};})
—
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/issues/357217#issuecomment-2499075132,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFUFAEBJEXYA6FUTXELOI32COJFXAVCNFSM6AAAAABSBXLB7WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJZGA3TKMJTGI
.
You are receiving this because you authored the thread.Message ID:
@.***>


Can't commit any longer

Just pulled from master, opened a new branch and tried to commit something. Got
An error has occurred: InvalidConfigError:
==> File .pre-commit-config.yaml
==> At Config()
==> At key: minimum_pre_commit_version
=====> pre-commit version 2.7.1 is required but version 2.5.1 is installed.  Perhaps run `pip install --upgrade pre-commit`.
Check the log at /Users/marius/.cache/pre-commit/pre-commit.log

When I actually check which version I have, I get
pre-commit                2.7.1                    pypi_0    pypi

So this does not make sense?
When I check the log in /Users/marius/.cache/pre-commit/pre-commit.log, I find
pre-commit version: 2.5.1
sys.version:
    3.6.9 |Anaconda, Inc.| (default, Jul 30 2019, 13:42:17)
    [GCC 4.2.1 Compatible Clang 4.0.1 (tags/RELEASE_401/final)]
sys.executable: /Users/marius/miniconda3/envs/cellrank/bin/python
os.name: posix
sys.platform: darwin

### error information

An error has occurred: InvalidConfigError:
==> File .pre-commit-config.yaml
==> At Config()
==> At key: minimum_pre_commit_version
=====> pre-commit version 2.7.1 is required but version 2.5.1 is installed.  Perhaps run `pip install --upgrade pre-commit`.

Traceback (most recent call last):
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 31, in validate_context
    yield
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 54, in _check_optional
    self.check_fn(dct[self.key])
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 371, in check
    fn(v)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/pre_commit/clientlib.py", line 36, in check_min_version
    f'pre-commit version {version} is required but version '
cfgv.ValidationError:
=====> pre-commit version 2.7.1 is required but version 2.5.1 is installed.  Perhaps run `pip install --upgrade pre-commit`.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 31, in validate_context
    yield
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 244, in check
    item.check(v)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 54, in _check_optional
    self.check_fn(dct[self.key])
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/contextlib.py", line 99, in __exit__
    self.gen.throw(type, value, traceback)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 34, in validate_context
    raise ValidationError(e, ctx=msg).with_traceback(tb)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 31, in validate_context
    yield
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 54, in _check_optional
    self.check_fn(dct[self.key])
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 371, in check
    fn(v)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/pre_commit/clientlib.py", line 36, in check_min_version
    f'pre-commit version {version} is required but version '
cfgv.ValidationError:
==> At key: minimum_pre_commit_version
=====> pre-commit version 2.7.1 is required but version 2.5.1 is installed.  Perhaps run `pip install --upgrade pre-commit`.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 31, in validate_context
    yield
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 407, in load_from_filename
    validate(data, schema)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 376, in validate
    schema.check(v)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 244, in check
    item.check(v)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/contextlib.py", line 99, in __exit__
    self.gen.throw(type, value, traceback)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 34, in validate_context
    raise ValidationError(e, ctx=msg).with_traceback(tb)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 31, in validate_context
    yield
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 244, in check
    item.check(v)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 54, in _check_optional
    self.check_fn(dct[self.key])
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/contextlib.py", line 99, in __exit__
    self.gen.throw(type, value, traceback)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 34, in validate_context
    raise ValidationError(e, ctx=msg).with_traceback(tb)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 31, in validate_context
    yield
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 54, in _check_optional
    self.check_fn(dct[self.key])
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 371, in check
    fn(v)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/pre_commit/clientlib.py", line 36, in check_min_version
    f'pre-commit version {version} is required but version '
cfgv.ValidationError:
==> At Config()
==> At key: minimum_pre_commit_version
=====> pre-commit version 2.7.1 is required but version 2.5.1 is installed.  Perhaps run `pip install --upgrade pre-commit`.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 40, in reraise_as
    yield
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 408, in load_from_filename
    return apply_defaults(data, schema)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/contextlib.py", line 99, in __exit__
    self.gen.throw(type, value, traceback)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 34, in validate_context
    raise ValidationError(e, ctx=msg).with_traceback(tb)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 31, in validate_context
    yield
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 407, in load_from_filename
    validate(data, schema)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 376, in validate
    schema.check(v)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 244, in check
    item.check(v)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/contextlib.py", line 99, in __exit__
    self.gen.throw(type, value, traceback)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 34, in validate_context
    raise ValidationError(e, ctx=msg).with_traceback(tb)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 31, in validate_context
    yield
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 244, in check
    item.check(v)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 54, in _check_optional
    self.check_fn(dct[self.key])
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/contextlib.py", line 99, in __exit__
    self.gen.throw(type, value, traceback)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 34, in validate_context
    raise ValidationError(e, ctx=msg).with_traceback(tb)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 31, in validate_context
    yield
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 54, in _check_optional
    self.check_fn(dct[self.key])
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 371, in check
    fn(v)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/pre_commit/clientlib.py", line 36, in check_min_version
    f'pre-commit version {version} is required but version '
cfgv.ValidationError:
==> File .pre-commit-config.yaml
==> At Config()
==> At key: minimum_pre_commit_version
=====> pre-commit version 2.7.1 is required but version 2.5.1 is installed.  Perhaps run `pip install --upgrade pre-commit`.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/pre_commit/error_handler.py", line 56, in error_handler
    yield
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/pre_commit/main.py", line 372, in main
    args=args.rest[1:],
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/pre_commit/commands/hook_impl.py", line 217, in hook_impl
    return retv | run(config, store, ns)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/pre_commit/commands/run.py", line 366, in run
    config = load_config(config_file)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 408, in load_from_filename
    return apply_defaults(data, schema)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/contextlib.py", line 99, in __exit__
    self.gen.throw(type, value, traceback)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 43, in reraise_as
    raise tp(e).with_traceback(tb)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 40, in reraise_as
    yield
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 408, in load_from_filename
    return apply_defaults(data, schema)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/contextlib.py", line 99, in __exit__
    self.gen.throw(type, value, traceback)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 34, in validate_context
    raise ValidationError(e, ctx=msg).with_traceback(tb)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 31, in validate_context
    yield
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 407, in load_from_filename
    validate(data, schema)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 376, in validate
    schema.check(v)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 244, in check
    item.check(v)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/contextlib.py", line 99, in __exit__
    self.gen.throw(type, value, traceback)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 34, in validate_context
    raise ValidationError(e, ctx=msg).with_traceback(tb)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 31, in validate_context
    yield
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 244, in check
    item.check(v)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 54, in _check_optional
    self.check_fn(dct[self.key])
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/contextlib.py", line 99, in __exit__
    self.gen.throw(type, value, traceback)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 34, in validate_context
    raise ValidationError(e, ctx=msg).with_traceback(tb)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 31, in validate_context
    yield
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 54, in _check_optional
    self.check_fn(dct[self.key])
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/cfgv.py", line 371, in check
    fn(v)
  File "/Users/marius/miniconda3/envs/cellrank/lib/python3.6/site-packages/pre_commit/clientlib.py", line 36, in check_min_version
    f'pre-commit version {version} is required but version '
pre_commit.clientlib.InvalidConfigError:
==> File .pre-commit-config.yaml
==> At Config()
==> At key: minimum_pre_commit_version
=====> pre-commit version 2.7.1 is required but version 2.5.1 is installed.  Perhaps run `pip install --upgrade pre-commit`.

Running  pip install --upgrade pre-commit does not change anything about this.

Try pre-commit autoupdate

Just tried that, the bug persists nontheless.

I get
An error has occurred: InvalidConfigError:
==> File .pre-commit-config.yaml
==> At Config()
==> At key: minimum_pre_commit_version
=====> pre-commit version 2.7.1 is required but version 2.5.1 is installed.  Perhaps run `pip install --upgrade pre-commit`.
Check the log at /Users/marius/.cache/pre-commit/pre-commit.log

Strange. You could either create a new conda environment, since this one seems to be corrupted, or change the version to 2.5.1 here https://github.com/theislab/cellrank/blob/master/.pre-commit-config.yaml#L9.

I just created an entirely new conda environment and the same error persists.

works again after changing the requirements!

I have the same problem again, can't commit. The error is
An error has occurred: InvalidConfigError:
==> File .pre-commit-config.yaml
==> At Config()
==> At key: minimum_pre_commit_version
=====> pre-commit version 2.9.0 is required but version 2.7.1 is installed.  Perhaps run `pip install --upgrade pre-commit`.
Check the log at /Users/marius/.cache/pre-commit/pre-commit.log

Again, conda tells me I have
pre-commit                2.9.0                    pypi_0    pypi

I already tried upgrading using pip with --no-cache-dir --force-reinstall

I also can't lower the requirements for pre-commit because one of the hooks depends on 2.9.0

I also tried uninstalling and re-installing pre-commit from conda-forge, no success either.

What do you get when you run which pre-commit and pre-commit --version?
If it doesn't produce the correct path/version, let's discuss on Zoom. You can disable the checks by running git commit --no-verify in the meantime.

which pre-commit yields /Users/marius/miniconda3/envs/cellrank_revision/bin/pre-commit, i.e. it uses the one from my conda environment. pre-commit --version yields pre-commit 2.9.3

Don't worry about this now, we can solve it in our meeting after your exam on friday.

To the following to solve it:

Remove the cache: pre-commit clean
uninstall pre-commit
re-install pre-commit:  pip install pre-commit --force-reinstall --no-cache-dir
install pre-commit: pre-commit install

This fixed it on my machine.


Add an .editorconfig file per style

I would ask for help from the community so we can fix all styles by updating this PR.
Currently, all styles are using the same base file provided by @sgrimm, the only changes among them are the properties indent_size and ij_continuation_indent_size (and a few properties related to avoiding wildcard imports), but I think there are more properties that should be updated/added/removed.

I personally use them as fallback so if someone in the team doesn't install the IntelliJ plugin, can at least get a similar formatting before checking the code with the Gradle plugin.
I think IntelliJ IDEA lets to export the .editorconfig, but I don't know all the specific configs of all styles.
Should the README point to the conventions docs of each style to know more specific differences and not only if it is 2/4, 2/2, 4/8, etc?

Having separate per-style files seems like the right approach to me. I have no opinion to offer about whether the settings for the other styles are correct, though, since I don't use those styles. As I said in my initial PR for this, I'm not even all that confident my original file was exactly correct, just closer to ktfmt default style than the default IntelliJ settings are.
My use case is exactly the same as @JavierSegoviaCordoba says: a fallback to reduce the number of complaints from the code style checker if a team member doesn't install the plugin.


output folders

Hi,
Thank you for creating this evaluation framework and accompanying repository.
The README mentions output folders for all real datasets, but these are not present.
Is it possible to add these, or, like with the input folder, a link to a Dropbox folder?
Thanks,
Koen

Hi Koen,
Thanks for your interest in our benchmark work. Currently we only keep the output to illustrate the benchmarking work structure. Due to the file size limit by Github, we didn't upload the result files. But using a Dropbox link is a good idea. I will try to clean up the files a bit and upload them in the next few days.


FDW changes the query plan based on optional key column(s)

Case-1: When visibility is not optional key qual in github_my_repository table
explain select
      r.full_name as resource,
      case
        when b.allow_force_pushes_enabled = 'false' then 'ok'
        else 'alarm'
      end as status,
      r.full_name || ' default branch ' || b.name ||
        case
          when b.allow_force_pushes_enabled = 'false' then ' prevents force push.'
          when b.allow_force_pushes_enabled = 'true' then ' allows force push.'
          -- If not false or true, then null, which means no branch protection rule exists
          else ' is not protected.'
        end as reason,
      r.full_name
    from
      github_my_repository as r
      left join github_branch_protection as b on r.full_name = b.repository_full_name
    where
      visibility = 'public' and r.fork = false and (b.name = 'main' or b.name = 'master')
+---------------------------------------------------------------------------------------------------------------+
| QUERY PLAN                                                                                |
+---------------------------------------------------------------------------------------------------------------+
| Nested Loop  (cost=0.00..30003037600000.00 rows=5000000000 width=128)                                         |
|   ->  Foreign Scan on github_my_repository r  (cost=0.00..30000000000000.00 rows=1000000 width=300)           |
|         **Filter: ((NOT fork) AND (visibility = 'public'::text))**                                                |
|   ->  Foreign Scan on github_branch_protection b  (cost=0.00..3000.00 rows=10 width=300)                      |
|         Filter: ((r.full_name = repository_full_name) AND ((name = 'main'::text) OR (name = 'master'::text))) |
+---------------------------------------------------------------------------------------------------------------+
>

Case-2: When visibility is optional key qual in github_my_repository table
> explain select
      r.full_name as resource,
      case
        when b.allow_force_pushes_enabled = 'false' then 'ok'
        else 'alarm'
      end as status,
      r.full_name || ' default branch ' || b.name ||
        case
          when b.allow_force_pushes_enabled = 'false' then ' prevents force push.'
          when b.allow_force_pushes_enabled = 'true' then ' allows force push.'
          -- If not false or true, then null, which means no branch protection rule exists
          else ' is not protected.'
        end as reason,
      r.full_name
    from
      github_my_repository as r
      left join github_branch_protection as b on r.full_name = b.repository_full_name
    where
      visibility = 'public' and r.fork = false and (b.name = 'main' or b.name = 'master')
+-------------------------------------------------------------------------------------------------------------------------------------------+
| QUERY PLAN                                                                                |
+-------------------------------------------------------------------------------------------------------------------------------------------+
| Nested Loop  (cost=0.00..30000337510000.00 rows=5000000000 width=128)                                                                     |
|   ->  Foreign Scan on github_branch_protection b  (cost=0.00..30000000000000.00 rows=1000000 width=300)
|         **Filter: ((name = 'main'::text) OR (name = 'master'::text))**                                                                        |
|   ->  Foreign Scan on github_my_repository r  (cost=0.00..300.00 rows=1 width=300)                                                        |
|         Filter: ((NOT fork) AND (visibility = 'public'::text) AND (visibility = 'public'::text) AND (full_name = b.repository_full_name)) |
+-------------------------------------------------------------------------------------------------------------------------------------------+
>

The order of filter highlighted in **-** is changed.

Some of the control fails due same reason
https://github.com/turbot/steampipe-mod-github-sherlock/issues/14


Helm Operator removes all releases from a cluster

When changing a field in the values section inside a FluxHelmRelease file the Helm Operator:
a) deletes all Helm releases including itself if it's installed with Helm
b) deletes a release whose related FHR was updated, instead of upgrading
When a FluxHelmRelease is updated the Operator deletes all Helm releases from a cluster. I would expect for the Operator to only instrument the releases managed with FluxHelmReleases not all releases. Also if a FluxHelmRelease values has been modified the Operator should perform a release upgrade not a delete.
Affected version: master-6f427cb
How to reproduce:
helm repo add sp https://stefanprodan.github.io/k8s-podinfo

# Fork https://github.com/stefanprodan/weave-flux-helm-demo

helm install --name cd \
--set git.url=git@github.com:MY-USENAME/weave-flux-helm-demo \
--set helmOperator.create=true \
--namespace flux \
sp/weave-flux

# find the SSH public key with:
export FLUX_POD=$(kubectl get pods --namespace flux -l "app=weave-flux,release=cd" -o jsonpath="{.items[0].metadata.name}")
kubectl -n flux logs $FLUX_POD | grep identity.pub | cut -d '"' -f2 | sed 's/.\{2\}$//'

# copy the public key and create a deploy key with write access on the GitHub repository

# wait for the first sync
# increment the replica count in MY-USENAME/weave-flux-helm-demo/config/frontend.yaml
# wait for the 2nd sync

helm list

# all helm releases have been deleted without purging including weave-flux

helm-integration image based on the latest flux master has manual release sync implemented. This has the following implications:
a)
helm-operator checks at regular intervals whether there are:

      aa) any new manually installed Chart releases => deletes them
            The assumption is that all cluster releases are described/configured through FHRs.
            Not ideal and will be removed.
      ab) deleted Chart releases which have its counterpart in the provided git repo =>
            reinstalled if these had been purged
      ac) manually upgraded releases are reverted to correspond to their corresponding
            FHR declaration

b)
helm-operator and flux agent should not be currently Chart releases:
      This happens due to aa). When aa) is fixed, then there can be any additional
      Chart releases that do not have their FHR counterparts.


Track query params

I noticed campaigns URLs behave a bit differently than ordinary URLs being tracked. I didn't notice a real-time update of those params hit like how usual visitors are tracked. Maybe there's a different scenarios behind how matomo deals with query params.

related to #34

-cc @fredvd @ericof

In the base use case, the query string parameters for campaigns (both from Matomo and from Google) are meaningful on the first access (when we should track then). After this first page view, we do not need to keep them.


Component doesn't reliably respond to a signal after hydration

Describe the bug
I have SSR enabled, and a module-scoped signal that is set onMount in one component. A second component that reads that signal doesn't reliably get notified when that signal is set.
Your Example Website or App
https://stackblitz.com/edit/solidjs-templates-rqx1ev?file=vite.config.ts,src%2Findex.tsx,index.html,src%2FAvatar.tsx,src%2FUser.tsx
Steps to Reproduce the Bug or Issue

Go to https://stackblitz.com/edit/solidjs-templates-rqx1ev?file=vite.config.ts,src%2Findex.tsx,index.html,src%2FAvatar.tsx,src%2FUser.tsx (kindly put together by Astro dev @matthewp via https://github.com/withastro/astro/issues/11017)
Click "Login" button (this sets localStorage user to "ahmed")
Refresh a few times

Expected behavior
After refresh, I expect both bold lines to say User is "ahmed" (responding to the user signal being set by the User component's onMount)
However, often one or both will say User is "", not reacting to the signal. Sometimes this works, other times it doesn't.
Screenshots or Videos

Platform

OS: dev is macOS but bug tested in macOS and Windows
Browser: all browsers tested
Version

    "solid-js": "^1.7.6"
    "vite": "^4.3.9",
    "vite-plugin-solid": "^2.7.0"

Additional context
Hypothesis from https://github.com/withastro/astro/issues/11017:

There appears to be a timing bug related to hydration and components that render asynchronously.

I see the issue it is just a bit tricky. The we are pretty lax when it comes to hydration in that we assume the server is correct and we don't correct text mismatches. If someone interacts with the page then we cancel hydration/streaming and apply the new state. However, if things are still hydrating we continue to assume the server is correct. What is happening in the example here is that since the one place is hydrating it assumes it doesn't need to do work but the signal under it has changed. So while the signal is being tracked and would update on another change it doesn't try to write the DOM initially.
That being said in general lazy hydrating + shared state is just not a good idea. Because the client state can change and if it is shared hydration will break. Like consider a global counter that can be incremented and the lazy hydrated component shows/hides stuff based on whether the count is above 5. If anything changed the counter before it hydrated you'd have serious hydration errors. This error was less serious and wasn't detected, but it would cause hydration issues just the same in other solutions that were stricter.

@ryansolid ahh, understood, thanks for that cogent explanation! Adding a onMount(() => console.log("Mounting …", new Date().toISOString())) to both components reveals that the incorrect behavior happens only when the signal-reader component (AvatarSolid in the example) is hydrated after the signal-setter component (User): the newly-hydrated component never "heard" the signal being set.
If I can burden your generosity some more. Should I just abandon the hydration + shared state model? Is that just a Bad Idea™?
Or does one just have to be careful about this pitfall by making the signal-writer (User) write the signal only after it's confirmed that all readers have been hydrated? A terrible workaround might be to just wait 100 ms after page load to write to the signal. Are there better ways to work around this or should I just give up?

@fasiha Maybe instead of onMount you could use https://primitives.solidjs.community/package/lifecycle#ishydrated as a way to check if you are safe to change the signal 🤔


Writing help on how to use the software

Someone needs to write how to use the software once developed

I've started a README file for our software, it will need adding to as the software is further developed.

When @Irwin-Blair and @Iarla-Boyce have merged their functions I will update the README

Send it to me and I will add it to the package once completed

I am going to close this as we have a separate branch relating to this


On testing UDP freeRTOS demos (both) , pinging takes too long when EKRA6M5 is connected to the laptop via ethernet

On testing UDP freeRTOS demos (both) , pinging takes too long when EKRA6M5 is connected to the laptop via ethernet

Hardware description: EKRA6M5
RTOS: Ubuntu 20 , (tested on both ROS humble and foxy)
Installation type: UDPv4 micro-ROS Agent
Version or commit hash: FSP 4.4

Steps to reproduce the issue

followed the instructions to test the UDPv4 micro-ROS agent. The code is built and flashed properly. But the agent runs only after a long time.
Expected behavior
The boards connect and the agent runs rightaway
Actual behavior
The ping takes a lot of time.

Hello @Srichitra-S please we need you to provide more details and be more precise on your issues.
What does means that "agent runs only after a long time"? That means that when you run the agent command (ros2 run micro_ros_agent micro_ros_agent [args] if takes time to start the process?
What is a lot of time? Hours?

Hello @Srichitra-S please we need you to provide more details and be more precise on your issues.
What does means that "agent runs only after a long time"? That means that when you run the agent command (ros2 run micro_ros_agent micro_ros_agent [args] if takes time to start the process?
What is a lot of time? Hours?
it takes about 1-1.5 minutes.


Added the article about unmanaged types

Fixes #10583
@BillWagner please advise on the proper location of the article within the C# reference. As soon as the location is settled, I'll add the links to this article from where it's necessary (pointer types, sizeof and stackalloc operators, unmanaged constraint).

@pkulikov I like the location you have chosen (under built-in-types). As we continue this journey, that's going to be where it lives.

@BillWagner I've searched the csharp docs folder for the "unmanaged type" occurrences and added the links to a new article.
Now, it's ready for review.


option to customize Godot Engine UI skin color / warmth / saturation / hue

There are options to change colors for many features in the engine from text editor to bg clear color but nothing for the UI skin itself.

This can be closed now right?

Seems implemented in the new 3.0 GUI indeed.

@bojidar-bg would it be worthwhile if I had a look through other issues and pointed out any worth closing?

@Zephilinox Well, yes, feel free to do so 😃


Package?

HI there, thanks for the amazing work!
We are very interested to use the webgl package, we are on headless-gl for now, but it does not work with gpu. Do you have an ETA on when we could start to test? Thank you!

Do you mean that if I npm install @nvidia/webgl inside the container, it will install the package correctly in my node module?

where can I found a demo for webgl? I am facing the error 2.1.0 Missing GL version

I am trying to replace headless-gl by rapidsai/webgl in that repo https://github.com/descriptinc/webgl-testing

no update here @AjayThorve ?

@nicolasgere are you running the WebGL demo from inside a docker container? If so, are you passing the --runtime=nvidia flag (and have the nvidia-container-toolkit installed)?
Our dev and runtime docker-compose files are configured to run GL apps inside the container but render in X11 on the host.
You can pass the same configuration via docker run. Save the following as a file called run-node-rapids-demo.sh:
Click here to see "run-node-rapids-demo.sh"
#!/usr/bin/env bash
envvars="\-e NODE_NO_WARNINGS=1 \`# Colorize the terminal in the container if possible` \-e TERM=${TERM:-} \`# Use the host's X11 display` \-e DISPLAY=${DISPLAY:-} \-e XAUTHORITY=${XAUTHORITY:-} \-e NVIDIA_DRIVER_CAPABILITIES=all \-e XDG_SESSION_TYPE=${XDG_SESSION_TYPE:-} \-e XDG_RUNTIME_DIR=${XDG_RUNTIME_DIR:-/run/user/$UID} \-e DBUS_SESSION_BUS_ADDRESS=${DBUS_SESSION_BUS_ADDRESS:-unix:path=/run/user/$UID/bus} \"
volumes="\-v /etc/fonts:/etc/fonts:ro \-v /tmp/.X11-unix:/tmp/.X11-unix:rw \-v /usr/share/fonts:/usr/share/fonts:ro \-v /usr/share/icons:/usr/share/icons:ro \-v /etc/timezone:/etc/timezone:ro \-v /etc/localtime:/etc/localtime:ro \-v /run/dbus/system_bus_socket:/run/dbus/system_bus_socket \-v ${XDG_RUNTIME_DIR:-/run/user/$UID}:${XDG_RUNTIME_DIR:-/run/user/$UID} \"
# Default to the "luma.gl-lessons/01" demo if none was passed in
cmd="${@:-npx @rapidsai/demo-luma.gl-lessons 01}"
exec docker run --rm -it --runtime=nvidia \    ${envvars} \    ${volumes} \    ghcr.io/rapidsai/node:22.02.00-runtime-node16.13.2-cuda11.6.0-ubuntu20.04-demo \    `# Run cmd inside the container` \    ${cmd}

Running the above script should open a window on your host with a triangle and square drawn via OpenGL:

Here's an example of running a different demo in the container with this script:


[dplay] Add support for playlists

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.12.10. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2017.12.10

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[x] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
youtube-dl http://www.dplay.no/praktisk-info-med-jon-almaas/ -v
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'http://www.dplay.no/praktisk-info-med-jon-almaas/', u'-v']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2017.12.10
[debug] Python version 2.7.13 - Darwin-17.2.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 3.3.4, ffprobe 3.3.4, rtmpdump 2.4
[debug] Proxy map: {}
[generic] praktisk-info-med-jon-almaas: Requesting header
WARNING: Could not send HEAD request to http://www.dplay.no/praktisk-info-med-jon-almaas/: HTTP Error 405: Method Not Allowed
[generic] praktisk-info-med-jon-almaas: Downloading webpage
WARNING: Falling back on generic information extractor.
[generic] praktisk-info-med-jon-almaas: Extracting information
ERROR: Unsupported URL: http://www.dplay.no/praktisk-info-med-jon-almaas/
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/youtube_dl/extractor/generic.py", line 2163, in _real_extract
    doc = compat_etree_fromstring(webpage.encode('utf-8'))
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/youtube_dl/compat.py", line 2539, in compat_etree_fromstring
    doc = _XML(text, parser=etree.XMLParser(target=_TreeBuilder(element_factory=_element_factory)))
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/youtube_dl/compat.py", line 2528, in _XML
    parser.feed(text)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 1653, in feed
    self._raiseerror(v)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 1517, in _raiseerror
    raise err
ParseError: syntax error: line 1, column 0
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/youtube_dl/YoutubeDL.py", line 784, in extract_info
    ie_result = ie.extract(url)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/youtube_dl/extractor/common.py", line 437, in extract
    ie_result = self._real_extract(url)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/youtube_dl/extractor/generic.py", line 3063, in _real_extract
    raise UnsupportedError(url)
UnsupportedError: Unsupported URL: http://www.dplay.no/praktisk-info-med-jon-almaas/

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: http://www.dplay.no/praktisk-info-med-jon-almaas/season-1-episode-1/
Single video: http://www.dplay.no/neste-sommer/season-1-episode-1-gratis/
Playlist: http://www.dplay.no/praktisk-info-med-jon-almaas/
Playlist: http://www.dplay.no/neste-sommer/

Note that youtube-dl does not support sites dedicated to copyright infringement. In order for site support request to be accepted all provided example URLs should not violate any copyrights.

Description of your issue, suggested solution and other information
All the episode links can be found in a json file, that is loaded when the page loads.
Example with "Praktisk info med Jon Almaas": http://www.dplay.no/api/v2/ajax/shows/15882/seasons/?items=14&sort=episode_number_desc&video_types=-clip&page=0

Hello MrDemocracy!
since you have mentioned:
Single video: http://www.dplay.no/praktisk-info-med-jon-almaas/season-1-episode-1/
Single video: http://www.dplay.no/neste-sommer/season-1-episode-1-gratis/
Playlist: http://www.dplay.no/praktisk-info-med-jon-almaas/
Playlist: http://www.dplay.no/neste-sommer/
A while ago, do you have a new solution to download neste sommer and praktisk info med jon almaas from discoveryplus.com/no with youtube-dl?
Hope you can help with a solution:)


Illegal commander pair

For example , Monoxa + Dee Kay is not a partner-able pair, but it slipped into the data somehow.

>>> pairs = Commander.objects.filter(commander2__partner_type=0)
>>> pairs
<CommanderQuerySet [
    <Commander: Norika Yamazaki, the Poet + Heiko Yamazaki, the General>,
    <Commander: Monoxa, Midway Manager + Dee Kay, Finder of the Lost>,
    <Commander: Spellheart Chimera + Thundering Djinn>
]>
>>> pairs.delete()

>>> pairs = Commander.objects.filter(commander1__partner_type=0, commander2__isnull=False)
>>>

(No results.)


pull request for e2e test at 12/14/2016 15:15:12

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Where does forms go?

Concern in legal about storing legal documents and contracts on an external server.

Hm this is an interesting point. I have no idea how easy/hard it would be to have this read files from, say, internal servers. I'm also wondering what the actual concern is about:

We aren't actually storing any finalized documents, only blank ones/templates.
Finalized documents are already stored on an external server (Onbase)

TODO: Reassure them that typeform is safe. (Talk to tech team/Laura about this).

Issues resolved, given approval by I&P Deputy Director of Operations. Privacy policy forwarded to law dept.


I am building nugets with your code.

I am glad that you have implement the code of create lnk file in Windows.
But I found that there is no solution in your repository and no nugets in nuget.com for use.
I create a solution of ShellLink and PropertyStore and build nuget with azure.
I am sorry for no advance inform.
If you need, I can push all my edit to your repository.
github repository: https://github.com/DaneSpiritGOD/ShellLink

Hi Dane,
Glad to hear you find it useful. If you could create a pull request, I'm happy to merge it.
Thanks, Yorick


Stale version in Gradle Plugin Registry

https://plugins.gradle.org/plugin/com.parmet.buf shows 0.6.3 while GH shows 0.7.1

FWIW https://jitpack.io/#andrewparmet/buf-gradle-plugin reports build errors

JitPack doesn't have the credentials it needs to sign the artifacts.
I'm having trouble publishing to Sonatype - I've put in a request to be migrated to the new (and hopefully more stable) shared. I can't see how any of the changes to the publishing config could have led to the failures I'm seeing.

After much futzing publishing is working again.
https://search.maven.org/artifact/com.parmet/buf-gradle-plugin/0.7.2/jar
https://plugins.gradle.org/plugin/com.parmet.buf/0.7.2 (coming soon)

https://plugins.gradle.org/plugin/com.parmet.buf still reports 0.6.3 as latest

0.7.3 published but waiting on approval from the Gradle team since the plugin ID changed by mistake.

Ok, 0.8.2 is working. https://plugins.gradle.org/plugin/com.parmet.buf/0.8.2


Fix deadline on update issue or PR via API

Backport #8696 to v1.10.

So this should have kind/breaking?

If someone has a script relying on that sending milestone as empty ("") will not change it, the script will have to be rewritten. So maybe better to mark it as breaking to let people check.


Show a skeleton for specific components depending on states before hydration sets state correctly

Describe the bug
A clear and concise description of what the bug is.
I have a page using rx.cond to check on a rx.var being set or not. While the page shows correctly, if I refresh the page, for a split second (on my local dev) it shows the component no longer supposed to render (because the var is now set), then finally the state is correct, the page refreshes to the correct component.
To Reproduce
Steps to reproduce the behavior:

Code/Link to Repo:

Expected behavior
A clear and concise description of what you expected to happen.
Initially if the state is not yet hydrated, have a way not to show the incorrect component at all.
Screenshots
If applicable, add screenshots to help explain your problem.
Specifics (please complete the following information):

Python Version:
Reflex Version:
OS:
Browser (Optional):

Additional context
Add any other context about the problem here.

We can use rx.cond(State.is_hydrated, comp_to_show)


Upgrade KFService to use Knative v1beta1 API

/kind feature
Describe the solution you'd like
[A clear and concise description of what you want to happen.]
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

/area project-health

/assign

in favor of https://github.com/kubeflow/kfserving/issues/574 now.
/close


Update kjob installation guide link.

Fixes / Features

Update kjob installation guide link.

Kjobctl moved to https://github.com/kubernetes-sigs/kjob.
Testing / Documentation
Testing details.

[ y/n ] Tests pass
[ y/n ] Appropriate changes to documentation are included in the PR

cc: @IrvingMg @pawloch00


Publish plugins should provide a form for the JSON configuration

Is your feature request related to a problem? Please describe.
As part of the plugin registration, the plugin should provide a basic form for the JSON configuration that can be used as a placeholder in the "add new profile" flow on the publish page.
Describe the solution you'd like
As part of the payload to addPublishMethod, the plugin should profile a JSON shape.
This will then be included in the call to /publish/types, and made available to the front end client.
The front end client should use this JSON shape to pre-fill the JSON configuration field in the "add new profile" flow.
Related to #2355

@a-b-r-o-w-n hey Andy, this was part of your feedback from a few days ago. Is there a specific way to have the JSON editor pre-filled with this other than just setting the default value?

There is a schema prop on the editor that will be used if present. The editor will not set a default value, so that needs to happen outside of the editor.

addressed via https://github.com/microsoft/BotFramework-Composer/pull/2719


Investigate: Endless activity indicator on Home

Disappears after hard close.

Seems like a request trying to get the state of the pending rewards is lost

Closed by #1571


[BUG] Loc still has some bugs

Issue 1
df = data.cars()
t = df.head(50)

df has correct history but t has a loc and slice included instead of just head
Issue 2
df = data.cars()
t = df.loc[55:100]

df has correct history but t has a slice included in addition to the loc call. However we need to override slice so that if I select without using loc like df[200:500 this still gets logged even though loc wasn't called.

I think you may have already fixed these but I just merged in the loc_log_support branch and these issues were still present in master so I think the fixes didn't get pushed. I went on and merged so the rest of the loc stuff is in master @Acornagain

New bug:
# cell 1
import lux
import pandas as pd

# cell 2
df = pd.read_csv("../data/movies-sample.csv")

# cell 3
df = df[~df.Worldwide_Gross.isna()] # any sort of filter here breaks the next step. e.g. df = df[df.Worldwide_Gross > df.Worldwide_Gross.median()]

# cell 4
df.Worldwide_Gross

When df.Worldwide_Gross is called it leads to a KeyError for "Title" in the loc code somewhere

It turned out that after I am able to directly work on your repo, I stopped updating the original loc_log_supporrts branch of my fork but just updating that in your repo, while the pull request still uses the original branch.

However, the third bug is not due to the loc/iloc function.
The problem arises in the following steps:

First because of the filter function call df = df[~df.Worldwide_Gross.isna()], the last event of the df is filter and the new dataframe copies its history, which makes the last event of df.Worldwide_Gross is also filter. Then according to the implicit_plotter logic, the filter visualization is then triggered.
Inside the functionprocess_filter, it assumes that the child dataframe and parent dataframe share the same set of columns and try to draw the filter view for each column. However, this fails because the child dataframe in this case has only one column. In your case, the error appeared because the Title column was not available in the child dataframe.

I fixed this by only requiring the filter view for columns shared by both the parent and child dataframe.

In addition, another bug (not an error) also appears after I fixed this bug, and I think this is related to the parental relationship.
To make it clear, I modify a few of your codes.
cell 1
import lux
import pandas as pd
cell 2
df = pd.read_csv("../data/movies-sample.csv")
cell 3
newdf = df[~df.Worldwide_Gross.isna()] # any sort of filter here breaks the next step. e.g. df = df[df.Worldwide_Gross > newdf.Worldwide_Gross.median()]
cell 4
df.Worldwide_Gross
When we call df.Worldwide_Gross after the filter, I think what we need is the filter view of the column Worldwide_Gross between the df and newdf. However, when calling newdf.Worldwide_Gross, the parent of this new dataframe is set to be newdf (because of the column reference logic) instead of df. Therefore, we will see an all-true filter view.


Use objc2 and its framework crates

objc2 is a replacement for objc/objc_id that contains a bunch of safety improvements, including automatically generated type-safe APIs objc2-foundation/objc2-app-kit/objc2-quartz-core/objc2-ui-kit and Id which makes memory management very clear.
~This is currently a draft, as it uses yet-unreleased parts of objc2-quartz-core, as well as the unreleased objc2-ui-kit crate.~
Fixes https://github.com/norse-rs/raw-window-metal/issues/13.

Went ahead and merged this now, but thanks for the review!

Went ahead and merged this now

Apologies, I never got around to read through the MacOS documentation to catch back up with anything I didn't understand! Completed the review now!


[6.0] Fix incorrectly-specified platform list in CMake file.

Explanation: Correctly sets SWT_NO_EXIT_TESTS on platforms that don't support them when building with CMake.
Scope: Building iOS, watchOS, tvOS, visionOS, WASI from OSS.
Issue: N/A
Original PR: https://github.com/swiftlang/swift-testing/pull/633
Risk: Low
Testing: Manually tested as we don't have CI using CMake yet.
Reviewer: @compnerd @briancroom

@swift-ci test

Merged to the wrong branch. 🤦


Feat: Add createAt param for NNS Transfers

Motivation
Add optional param createdAt in NNS Transfers.
This parameter is used in the NNS Ledger to identify duplicated transactions. Without it, two transfers with the same params from the same caller would be considered as two different transactions. This could happen if agent-js or the client retries the request.
If the request has the createdAt set and agent-js retries the call, the Ledger canister will consider it as a duplicated and not perform the transaction twice.
Changes

Add createdAt optional param to TransferRequest type.
Handle the new param in transferHardwareWallet.
Handle the new param in toTransferRawRequest.

Tests

Add a test to check that the new param is added in the request.

@mstrasinskis @peterpeterparker please review

DO NOT MERGE
Client gets a TxTooOld error in any transaction when setting the create_at parameter.


How I create a one time job that requires network.? exact is not work for me

Before posting an issue, please check the following:

Do you have a question? Please take a look at the samples and read the FAQ first.
** https://github.com/evernote/android-job#usage
** https://github.com/evernote/android-job/wiki/FAQ

Does the library crash for you? Please provide the version of the library, a log, stacktrace and even better a sample.

 A full log is necessary. Also keep in mind how Doze works and maintenance windows can delay your job.
** https://developer.android.com/training/monitoring-device-state/doze-standby.html
** https://speakerdeck.com/vrallev/scheduling-background-job-on-android-at-the-right-time-1?slide=59

Please read the README and ask questions at Stackoverflow. This is an issue tracker. https://github.com/evernote/android-job#advanced


Fix Issues with Yup & SendPointModal

the three functions equalTo notEqualTo and callbackWithRef should be mixed functions, not string and not number only.
The validationSchema within the SendPointModal has rules that are in opposite order. Make it work with the proper order

You want to validate with:
yup.mixed().test() ?
Or did I kinda missunderstand?


refactor: add more extensive check for reverted contract

Description
Right now, to check if a contract is reverted, we check if the returned res.Failed() == true.
There can be situation where when CallEVM fail, the returned res will be nil and the error with contain the description execution reverted.
Since depositAndCall logic could be updated in the future and create a situation where res could become nil after reverted execution, this PR adds a more extensive check for the contract reverted taking this situation into account.
The PR also add more smoke test to test DepositAndCall with ethers.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Include instructions and any relevant details so others can reproduce.

[ ] Tested CCTX in localnet
[ ] Tested in development environment
[ ] Go unit tests
[ ] Go integration tests
[ ] Tested via GitHub Actions

Checklist:

[ ] I have added unit tests that prove my fix feature works

i vaguely remember this patch might be already incorporated in another PR, is that right? @lumtis

i vaguely remember this patch might be already incorporated in another PR, is that right? @lumtis

This PR is the result of the initial investigation I had on Denis' non-reverted cctx issue. I realize that the check for reverted tx we have doesn't handle all cases (the tx might revert and the check doesn't detect). It doesn't fix a current issue we have in the node right now (always detect reverted) but it might become an issue if we change the DepositAndCall logic in the future

Fix for https://github.com/zeta-chain/node/issues/1347 : https://github.com/zeta-chain/node/pull/1214/commits/b3af0bdf41c86ea6ff247e96fe3d5d10f521b7cc

Alternatively, if the mocks in unit tests can simulate a remote contract call and result then that'll be great too.

I have one unit test here that calls a reverted function:
https://github.com/zeta-chain/node/blob/9a7a7812fef15198f57934fb9b337c19fe1e7a89/x/fungible/keeper/evm_test.go#L358
If we already have the smoke test calling a reverted function, I can add an assert in the smoke test

@brewmaster012 added check in the smoke test
0b2f828
9735294


Test full build of 7.1 on CI with 6.5 just in case

@marko-bekhta Note that being able to build against 6.5 is not the same as being able to run against 6.5.
The dependency-update jobs check that you can run against 6.5, which is what matters.
You may not be able to build against 6.5 due to e.g. deprecation warnings (which cause build failures) or problems related to generics (which are erased anyway and don't always matter at runtime).

That being said, the compilation error we're seing in this build is indeed suspicious. But I think you sent a patch to add a default implementation for that method in ORM... didn't you?


feat: NotifyServerSubscription.appAuthenticationKey

Context: https://walletconnect.slack.com/archives/C044SKFKELR/p1698311303892429

Implemented in Notify Server here: https://github.com/WalletConnect/notify-server/pull/151


Publish blockscout deployment info to pubsub

Description
Sends info about blockscout deployment to a known pubsub topic for handling and posting to slack
Other changes

Add publish to pubsub functionality to gcloud_utils

Tested

Ran locally with --helmdryrun to assert functionality

Let's turn it into a post-upgrade hook similar to other similar tasks?

We can also do that in the helm PR, but until that's released we would need it in celotool to get any value.
I'm not too sure how to go about accessing a pubsub topic from a helm hook - grafana looks like it bundles a shell script which calls out via a dedicated container, we'd have to do something similar with gcloud

We can also do that in the helm PR, but until that's released we would need it in celotool to get any value.
I'm not too sure how to go about accessing a pubsub topic from a helm hook - grafana looks like it bundles a shell script which calls out via a dedicated container, we'd have to do something similar with gcloud

I think from a helm hook container how it would look like:
Inside celotool:

Create a Service Account with using here.
Attach a policy/role allowing to publish in the PubSub topic.
Create the rolebinding to allow a Kubernetes Service account to impersonate this GCP SA (workload identity tutorial)

In the pod run by the Helm hook:

Run a container with a gloud-sdk image.
Container has assigned a K8s Service Account that was authorized in last section point 3.
The K8s service account has an annotation to indicate the GCP Service account to impersonate.
gcloud automatically get the credentials when a Service account is provided in this way.

It is a bit complex setup but I can help you setting up if you prefer that way.

Hey Javi, thanks for reviewing. We went with an approach that consumes GCP audit logs via cloud functions which has the benefit of working directly on the changes applied on the cluster rather than through the deployment mechanism


Arguments for add_argument are now shown in separated lines

I've mainly created this pull request to improve the readability of the source code.

To be honest, I have never used black before but I have some time to look into this formatter. I will read the documentation and let you know whether the code is correctly formatted according to black.

@musically-ut I've looked into this and my changes are not compliant to the Black formatter, so I think it would be appropiate to close this pull request.
It is worth mentioning that I created this pull request because I noticed that there were some add_argument rules that were wrote in separated lines (see below)
https://github.com/Networks-Learning/stackexchange-dump-to-postgres/blob/49d8358a83bb573c63c2715b122afb2fca98376c/load_into_pg.py#L317-L322
https://github.com/Networks-Learning/stackexchange-dump-to-postgres/blob/49d8358a83bb573c63c2715b122afb2fca98376c/load_into_pg.py#L338-L344
while others weren't
https://github.com/Networks-Learning/stackexchange-dump-to-postgres/blob/49d8358a83bb573c63c2715b122afb2fca98376c/load_into_pg.py#L324-L326
so I thought that it would be better to be consistent with one way of writing the add_argument statements, but because Black doesn't consider this, we can close this pull request.

Yup, I'd understood the intentions behind it. :)
However, when it comes to code-formatting, I'd prefer to have effortless conformity rather than meticulous consistency. 🤷

I will consider that in future pull requests. Thanks for the advice! 👍


No support for GDPR compliance for IS Analytics

There is login information of end users shown in Analytics dashboard such as

username if email as username is used
IP address etc.
Which can be used to identify a particular user.

Issue
When I anonymized a user running the tool, I could still see those user information in the Analytics Dashboard.

Fixed with 5.5.0-RC


[WIP]Disable bmo_setup in zuul job

The Zuul Job runs crc vm with 16GB RAM and 6 CPUS.
From last week, the crc vm is hitting with high io
leading to all controller manager pods going to
crashloopbackoff state.

We also added Baremetal integration in install_yamls.

In order to fix the CI and finish the EDPM deployment
on same node.

* We are reducing the rabbitmq resources to avoid high io.
* Disabling bmo_setup[1] during meta operator installation.

These are short term solution to unblock the CI.
In future, we will be using bigger node.

[1]. https://review.rdoproject.org/r/c/config/+/48523

Signed-off-by: Chandan Kumar<EMAIL_ADDRESS>

recheck

recheck


rating filter

Dear
If I set rating player filter from trade enhance and go to auto buyer.. Autobuyer show all players not filtered player

Refer #426


[Request]  Add logseq

A privacy-first, open-source(frontend-only) platform for knowledge sharing and management.
https://github.com/logseq/logseq

#5951
I have creat a json config for Logseq. It might help :)


Shot rates by score state graphs

For teams: scatterplot of shot rates, with league averages grayed out for comparison. Maybe use size to indicate fraction of TOI spent in that state?
For individuals: similar, but maybe use size to indicate TOI60 for team in that score state (to see whether players are more or less trusted in that situation)

Graph could be improved further, but first draft done


Product-based filtering in vexctl

This ticket is something between a discussion item and a bug report, let me know if there is a better place for it.
vexctl can currently filter out entries from a SARIF file, but it doesn't seem to take into account the value of the products array when doing so.
My expected behaviour would be this:
If I vexctl filter a SARIF against a VEX, and for a given vulnerability ID, a value in the locations array in the SARIF matches a value in the products array of the VEX document, the vulnerability ID should be filtered for that particular result. If there is no match between the locations array in the SARIF and the products array, then the value should continue to be reported.
There are some complexities to this, based on the non-standard way in which the locations array is constructed by different scanners, but I think at a high level the locations field is generally where the product version is found in a SARIF (perhaps exactly which field to use should be a customisable option?).
However the current behaviour is:
If the vulnerability ID is found in the SARIF results array, then the vulnerability is removed, even if the product is not specifically listed in the VEX statement for the vulnerability.
For workflows where a single golden VEX file is used to maintain VEX statements relating to multiple products, this means that adding a VEX statement for any one product automatically removes vulnerability reporting for all of the products that are covered by the VEX document + vulnerability ID combination, even if other products may not have been assessed for that vulnerability ID.
Some samples to illustrate this behaviour – I would assume that running vexctl filter sample.sarif.json vex-sample.json should return 1 result due to the product/artifactLocation mismatch, but the vulnerability is removed.
sample.sarif.json:
{
  "version": "2.1.0",
  "$schema": "https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-schema-2.1.0.json",
  "runs": [
    {
      "tool": {
        "driver": {
          "name": "scan-tool",
          "version": "2",
          "informationUri": null,
          "rules": [
            {
              "id": "CVE-2023-29405",
              "shortDescription": {
                "text": "CVE-2023-29405 in go (critical)"
              },
              "fullDescription": {
                "text": "Critical severity CVE-2023-29405 found in go version 1.20.4"
              },
              "help": {
                "text": "",
                "markdown": "| CVE | Severity | CVSS | Package | Version | Fix Status | Published | Discovered |\n| --- | --- | --- | --- | --- | --- | --- | --- |\n| [CVE-2023-29405]
(https://nvd.nist.gov/vuln/detail/CVE-2023-29405) | critical | 9.8 | go | 1.20.4 | fixed in 1.20.5, 1.19.10 | 2023-06-08T21:15:00Z | 2023-08-15T16:01:30Z |"
              }
            }
          ]
        }
      },
      "results": [
          {
          "ruleId": "CVE-2023-29405",
          "level": "warning",
          "message": {
            "text": "Description"
          },
          "locations": [
            {
              "physicalLocation": {
                "artifactLocation": {
                  "uri": "my-product:v1.0.0"
                },
                "region": {
                  "startLine": 1,
                  "startColumn": 1,
                  "endLine": 1,
                  "endColumn": 1
                }
              }
            }
          ]
        }
      ]
    }
  ]
}

vex-sample.json:
{
  "@context": "https://openvex.dev/ns",
  "@id": "test",
  "author": "Feroz Salam",
  "role": "vendor",
  "timestamp": "2023-07-04T17:51:12.004221+01:00",
  "version": "1",
  "statements": [
    {
      "vulnerability": "CVE-2023-29405",
      "products": [
        "random"
      ],
      "status": "not_affected",
      "justification": "vulnerable_code_not_in_execute_path"
    }
  ]
}

I agree @ferozsalam . The main problem is that there is no consistency in the data in the SARIF output of the scanners. I was just looking into the output and it varies wildly, The scanned image is in different places in each tool. For example:
Grype has these logicalLocations:
              "logicalLocations": [
                {
                  "name": "/usr/share/doc/libtiff6/copyright",
                  "fullyQualifiedName": "nginx@sha256:13d22ec63300e16014d4a42aed735207a8b33c223cff19627dd3042e5a10a3a0@sha256:4713cb24eeff341d0c36343149beba247572a5ff65c2be5b5d9baafb345c7393:/usr/share/doc/libtiff6/copyright"
                },
                {
                  "name": "/var/lib/dpkg/info/libtiff6:amd64.md5sums",
                  "fullyQualifiedName": "nginx@sha256:13d22ec63300e16014d4a42aed735207a8b33c223cff19627dd3042e5a10a3a0@sha256:4713cb24eeff341d0c36343149beba247572a5ff65c2be5b5d9baafb345c7393:/var/lib/dpkg/info/libtiff6:amd64.md5sums"
                },
                {
                  "name": "/var/lib/dpkg/status",
                  "fullyQualifiedName": "nginx@sha256:13d22ec63300e16014d4a42aed735207a8b33c223cff19627dd3042e5a10a3a0@sha256:4713cb24eeff341d0c36343149beba247572a5ff65c2be5b5d9baafb345c7393:/var/lib/dpkg/status"
                }

In Trivy, there is a properties section at the end:
      "properties": {
        "imageName": "nginx@sha256:13d22ec63300e16014d4a42aed735207a8b33c223cff19627dd3042e5a10a3a0",
        "repoDigests": [
          "nginx@sha256:13d22ec63300e16014d4a42aed735207a8b33c223cff19627dd3042e5a10a3a0"
        ],
        "repoTags": []
      }

Which flavor of SARIF are you using? Can you post a SARIF sample here? We may be able to support them with custom code for each tool.

Hey @puerco is this something that would be best as a user-configurable option?
On the SARIF question, in my example above I'm using the Prisma Cloud GitHub action, you can see how it inserts image version into the SARIF here. I've provided a sample SARIF in the issue description above, do you need more than that?


[cmap] Revert Format 4 field name idRangeOffset

In OT 1.8.4, the Format 4 field array name idRangeOffset was changed to idRangeOffsets. Presumably this was to provide better consistency with names for arrays of offsets in other tables. However, the change created inconsistency with other references to that field within the cmap chapter. It also created inconsistency with the names for other arrays within the Format 4 format (startCode[], etc.) which have multiple entries used alongside the range offsets but do not have pluralized names.
(This was noticed when comparing the cmap chapter with the corresponding sections of OFF 5th Edn working draft.)
Thus, it makes sense to revert the name to idRangeOffset.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 86923ff4-2b60-9144-e2b4-77cdb36fd698
Version Independent ID: ea221e53-f51a-8233-3c0b-d416e5360623
Content: cmap - Character To Glyph Index Mapping Table (OpenType 1.9) - Typography
Content Source: typographydocs/opentype/spec/cmap.md
Product: typography
GitHub Login: @PeterCon
Microsoft Alias: alib

See OT 1.9.1 alpha for draft revisions addressing this issue.

This is fixed in OT 1.9.1. See the OT 1.9.1 beta for draft revisions addressing this issue.


qt6.qtwebengine: disable signing on x86_64-darwin

Description of changes
I was too optimistic about darwin.autoSignDarwinBinariesHook. As a result, the package times out on Hydra: https://hydra.nixos.org/build/247191915/nixlog/1
Now I wonder why this worked, though.
https://github.com/NixOS/nixpkgs/blob/98ad610d60e0693181d73cf718b325ba8fffebf0/pkgs/applications/networking/syncthing/default.nix#L27-L34
Probably won't spend 12 hours building this on x86_64-darwin.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 283114 run on x86_64-darwin 1

31 packages marked as broken and skipped:

anki
anki.dist
anki.doc
anki.man
calibre
cutterPlugins.rz-ghidra
librealsenseWithCuda
librealsenseWithCuda.dev
mnemosyne
mnemosyne.dist
python311Packages.numbaWithCuda
python311Packages.numbaWithCuda.dist
python311Packages.pycuda
python311Packages.pycuda.dist
python311Packages.pynvml
python311Packages.pynvml.dist
python311Packages.pyrealsense2WithCuda
python311Packages.pyrealsense2WithCuda.dev
python311Packages.theanoWithCuda
python311Packages.theanoWithCuda.dist
python312Packages.pycuda
python312Packages.pycuda.dist
python312Packages.pynvml
python312Packages.pynvml.dist
python312Packages.pyrealsense2WithCuda
python312Packages.pyrealsense2WithCuda.dev
truecrack-cuda
unbook
xgboostWithCuda
zapzap
zapzap.dist

1 package failed to build:

zeal-qt6

12 packages built:

cutter
python311Packages.pyqt6-webengine
python311Packages.pyqt6-webengine.dev
python311Packages.pyqt6-webengine.dist
qlog
qt6.qtwebengine (qt6Packages.qtwebengine ,yuzuPackages.qtwebengine)
qt6.qtwebengine.dev (qt6Packages.qtwebengine.dev ,yuzuPackages.qtwebengine.dev)
qutebrowser
qutebrowser.dist
retext
retext.dist
stellarium

Fortunately, it only took 10 hours.


Enrich documentations

Codecov Report

Merging #51 (d699c20) into master (3142ba8) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #51   +/-   ##
=======================================
  Coverage   85.45%   85.45%
=======================================
  Files           1        1
  Lines          55       55
=======================================
  Hits           47       47
  Misses          5        5
  Partials        3        3

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3142ba8...d699c20. Read the comment docs.


Multidataset - Is there a way to change color of single bar when hovering

I am working with multi-dataset, customers want me when hover to a bar, it will highlight just one bar, not the others.
I'm trying to custom hover event in options, the code likes this:
hover: {
onHover: function (event, elements) {
}
}
But I can not find a way to get current bar which users hover on to control colors of the other bars in same group.
Thank you for response!

Did you try other hover interaction modes such as 'dataset' or 'index'?

Yes, I have tried it, but it didn't work

Hello. Same issue.
I tried with hover interaction modes but can't reach my goal...
Is there a solution?
Thanks

Solved
hover: {
mode: 'nearest'
},


An unknown network error occurred while communicating with the XCUITest server

Is there an existing issue for this?

[X] I have searched the existing issues and didn't find mine.

Steps to reproduce
We're running Maestro on CI on a macos-14 runner (GitHub actions) and are experiencing XCUITest not starting the test. I added some logs of the failure below.
Actual results
The server is not starting and running the tests on CI.
Expected results
We are expecting it to start correctly.
About app
React Native - 0.74.5 - iOS
About environment
Xcode 15.4, arm64
Logs

Logs
Running on iPhone 15 Pro - iOS 17.5 - B23095CC-E2ED-4301-A857-BCC36C176ACB

Flow
Run flow...
ℹ Retrying connection to the XCUITest server for 1...
ℹ Retrying connection to the XCUITest server for 2...
ℹ Retrying connection to the XCUITest server for 3...
ℹ Retrying connection to the XCUITest server for 4...
ℹ Retrying connection to the XCUITest server for 5...
Error: ⚠ Error: An unknown network error occurred while communicating with the XCUITest server. If the issue persists, consider raising a GitHub issue with the error message and any available logs for further assistance.
⚠ Error: An unknown network error occurred while communicating with the XCUITest server. If the issue persists, consider raising a GitHub issue with the error message and any available logs for further assistance.
Error: Request for http://[::1]:7001/deviceInfo failed, because of XCUITest server got crashed/exit, body: {"errorMessage":"An unknown network error occurred while communicating with the XCUITest server. If the issue persists, consider raising a GitHub issue with the error message and any available logs for further assistance.","code":"network-error"}
kotlinx.coroutines.JobCancellationException: BlockingCoroutine is cancelling; job=BlockingCoroutine{Cancelling}@35a3f96
❌ Error: BlockingCoroutine is cancelling
Caused by: NetworkError(errorResponse=Request for http://[::1]:7001/deviceInfo failed, because of XCUITest server got crashed/exit, body: {"errorMessage":"An unknown network error occurred while communicating with the XCUITest server. If the issue persists, consider raising a GitHub issue with the error message and any available logs for further assistance.","code":"network-error"})
at xcuitest.XCTestDriverClient.handleExceptions(XCTestDriverClient.kt:280)
at xcuitest.XCTestDriverClient.processResponse(XCTestDriverClient.kt:258)
at xcuitest.XCTestDriverClient.executeJsonRequest(XCTestDriverClient.kt:207)
at xcuitest.XCTestDriverClient.deviceInfo(XCTestDriverClient.kt:180)
at xcuitest.XCTestDriverClient.deviceInfo$default(XCTestDriverClient.kt:179)
at ios.xctest.XCTestIOSDevice$deviceInfo$1.invoke(XCTestIOSDevice.kt:31)
at ios.xctest.XCTestIOSDevice$deviceInfo$1.invoke(XCTestIOSDevice.kt:30)
at ios.xctest.XCTestIOSDevice.execute(XCTestIOSDevice.kt:227)
at ios.xctest.XCTestIOSDevice.deviceInfo(XCTestIOSDevice.kt:30)
at ios.LocalIOSDevice.deviceInfo(LocalIOSDevice.kt:29)
at maestro.drivers.IOSDriver$deviceInfo$2.invoke(IOSDriver.kt:46)
at maestro.drivers.IOSDriver$deviceInfo$2.invoke(IOSDriver.kt:45)
at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)
at maestro.drivers.IOSDriver.getDeviceInfo(IOSDriver.kt:45)
at maestro.drivers.IOSDriver.access$getDeviceInfo(IOSDriver.kt:41)
at maestro.drivers.IOSDriver$deviceInfo$4.invoke(IOSDriver.kt:79)
at maestro.drivers.IOSDriver$deviceInfo$4.invoke(IOSDriver.kt:76)
at maestro.drivers.IOSDriver.runDeviceCall(IOSDriver.kt:499)
at maestro.drivers.IOSDriver.deviceInfo(IOSDriver.kt:76)
at maestro.Maestro.fetchDeviceInfo(Maestro.kt:60)
at maestro.Maestro.access$fetchDeviceInfo(Maestro.kt:38)
at maestro.Maestro$cachedDeviceInfo$2.invoke(Maestro.kt:44)
at maestro.Maestro$cachedDeviceInfo$2.invoke(Maestro.kt:43)
at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)
at maestro.Maestro.getCachedDeviceInfo(Maestro.kt:43)
at maestro.Maestro.deviceInfo(Maestro.kt:54)
at maestro.orchestra.Orchestra.initJsEngine(Orchestra.kt:227)
at maestro.orchestra.Orchestra.runFlow(Orchestra.kt:83)
at maestro.orchestra.Orchestra.runFlow$default(Orchestra.kt:75)
at maestro.cli.runner.MaestroCommandRunner.runCommands(MaestroCommandRunner.kt:185)
at maestro.cli.runner.TestRunner$runSingle$result$1.invoke(TestRunner.kt:54)
at maestro.cli.runner.TestRunner$runSingle$result$1.invoke(TestRunner.kt:51)
at maestro.cli.runner.TestRunner.runCatching(TestRunner.kt:145)
at maestro.cli.runner.TestRunner.runSingle(TestRunner.kt:51)
at maestro.cli.command.TestCommand$handleSessions$1$1$results$1$1$1.invoke(TestCommand.kt:291)
at maestro.cli.command.TestCommand$handleSessions$1$1$results$1$1$1.invoke(TestCommand.kt:249)
at maestro.cli.session.MaestroSessionManager.newSession(MaestroSessionManager.kt:107)
at maestro.cli.session.MaestroSessionManager.newSession$default(MaestroSessionManager.kt:58)
at maestro.cli.command.TestCommand$handleSessions$1$1$results$1$1.invokeSuspend(TestCommand.kt:249)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:111)
at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:99)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:585)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:802)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:706)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:693)

Maestro version
1.38.7
How did you install Maestro?
install script (https://get.maestro.mobile.dev)
Anything else?
No response

If anyone is looking for a temporary solution, it seems 1.37.7 is still working. Here's the steps in the docs for installing a specific version. (Also, I believe the Maestro version listed above is a typo and should be 1.37.8 instead).

Off, that's a bad one. Thanks for a quick report and all the likes, this really makes it obvious to see it's impacting many of you.
Working on a fix right now.
To share a bit more:
We have e2e testing for Android that prevents these kinds of total outages. Unfortunately I wasn't able to get the equivalent E2E pipeline for iOS working on GitHub Actions in a reasonable time (how ironic, lol). This is a strong signal we have to get that done finally.

The cause is likely #1809 (strange, it was working!, sigh)
I reverted that change. Released as Maestro v1.37.9 - please update.
Sorry about sudden breakage. We made some progress on E2E testing pipeline but apparently it's not enough. We will do better.

As a datapoint, I am still seeing the error when using Maestro 1.37.9. Reverting to 1.37.7 does fix it for me.

Logs
Downloading maestro 1.37.9
  Unzipping maestro
  /usr/bin/unzip -o -q /Users/runner/work/_temp/55694391-77df-4b75-8d70-92771dfe4fb6
  maestro succesffuly installed

[snip]

Waiting on http://localhost:8081
› Installing on iPhone 14 Pro
› Opening on iPhone 14 Pro (com.chickfila.international)
› Opening exp+chick-fil-a-international://expo-development-client/?url=http%3A%2F%2F<IP_ADDRESS>%3A8081 on iPhone 14 Pro
› Opening the iOS simulator, this might take a moment.

><EMAIL_ADDRESS>maestro /Users/runner/work/mobile-ordering/mobile-ordering
> scripty ".maestro/RunThrough.yaml"

scripty > Executing "/Users/runner/work/mobile-ordering/mobile-ordering/scripts/maestro/index":

CI detected, analytics was automatically enabled.
To opt out, set MAESTRO_CLI_NO_ANALYTICS environment variable to any value before running Maestro.

kotlinx.coroutines.JobCancellationException: BlockingCoroutine is cancelling; job=BlockingCoroutine{Cancelling}@2e122d32
❌ Error: BlockingCoroutine is cancelling
Caused by: maestro.MaestroDriverStartupException$IOSDriverTimeoutException: Maestro iOS driver did not start up in time
	at maestro.drivers.IOSDriver.awaitLaunch(IOSDriver.kt:494)
	at maestro.drivers.IOSDriver.open(IOSDriver.kt:64)
	at maestro.Maestro$Companion.ios(Maestro.kt:610)
	at maestro.cli.session.MaestroSessionManager.createIOS(MaestroSessionManager.kt:330)
	at maestro.cli.session.MaestroSessionManager.createMaestro(MaestroSessionManager.kt:163)
	at maestro.cli.session.MaestroSessionManager.newSession(MaestroSessionManager.kt:88)
 ELIFECYCLE  Command failed with exit code 1.
	at maestro.cli.session.MaestroSessionManager.newSession$default(MaestroSessionManager.kt:58)
	at maestro.cli.command.TestCommand$handleSessions$1$1$results$1$1.invokeSuspend(TestCommand.kt:249)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
	at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:111)
	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:99)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:585)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:802)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:706)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:693)
scripty ERR! script failed: '/Users/runner/work/mobile-ordering/mobile-ordering/scripts/maestro/index'
scripty ERR! exit status: 1

As a datapoint, I am still seeing the error when using Maestro 1.37.9. Reverting to 1.37.7 does fix it for me.
Logs

Hm, 1.37.9 is working for me so far...

Hey @CodingItWrong, it looks like a different error. The stacktraces are different.
@disrae thanks for confirming!

@gtokman, please mark the issue as closed if the problem is resolved for you after upgrading to v1.37.9

thank you @bartekpacia, I will work on a minimal repro of my error so I can open a separate issue

i see, thank you!

As a heads up, the error I posted above is no longer occurring for me as of today, with no changes to Maestro version or otherwise. Must have either been a transient error or some underlying change in GitHub Actions.


TS2786: 'Helmet' cannot be used as a JSX component

Helmet works in JSX but not in Typescript, I am getting:
TS2786: 'Helmet' cannot be used as a JSX component
Type 'Helmet' is missing the following properties from type 'ElementClass':
render, context, setState, forceUpdate

import { Helmet } from 'react-helmet';

return (
    <>
      <Helmet>
        <title>
          {translation('supportPage.heading')}
        </title>
      </Helmet>
      <Breadcrumbs />
      ...
  </>
);

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>(devDependencies)

For TSX you can go with simple ignore as a quick win.
//@ts-ignore
const helmet = <Helmet><title>App title</title></Helmet>

return (
       <div>
                {helmet}
       </div>
);

Ah yea of course! That will do for now! Thank you @EVASIVE!

@sunnz install @types/react-helmet

Yes I've got these installed:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

The same. Installing @types/react-helmet did not help.

Are there any updates on this? Using helmet in many nested components is a pain currently

+1 i'm having this issue also

also experiencing issues with this once upgrading to react-18

+1 Similar issue with react 18

I have the same issue on my side with last versions of react-helmet and its @types/react-helmet.
I've just solved it by removing the @types/react-helmet package and adding declare module "react-helmet"; to a .d.ts file instead.

+1. this does kinda make the package unusable...

For those of you guys who are having a TS error after upgrading to react 18, you can try adding a simple wrapper for Helmet:
type HelmetProps = React.ComponentProps<typeof Helmet>;

const HelmetWithChildren: FC<HelmetProps & { children?: React.ReactNode }> = ({
    children,
    ...rest
}) => <Helmet {...rest}>{children}</Helmet>;

Running into a similar issue but I'm on react 17. DId anyone figure this out?

this project is dead. Use react-helmet-async instead.

@gilluminate running into the same invariant error with react-helmet-sync.  I'm using react with typescript. Any resources you recommend?

https://github.com/staylor/react-helmet-async/issues/154

How should I solve this problem? Still can't solve it?

I have the same issue on my side with last versions of react-helmet and its @types/react-helmet. I've just solved it by removing the @types/react-helmet package and adding declare module "react-helmet"; to a .d.ts file instead.

yes or in a .ts (like react-helmet.ts) in one of your typeRoots folders (you still need to remove @types/react-helmet) with, based on @types/react-helmet, something like :
/* BASED ON https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/react-helmet/index.d.ts */
/* WAITING FOR https://github.com/nfl/react-helmet/issues/646 FIX */
declare module 'react-helmet' {
  // Type definitions for react-helmet 6.1
  // Project: https://github.com/nfl/react-helmet
  // Definitions by: Evan Bremer <https://github.com/evanbb>
  //                 Isman Usoh <https://github.com/isman-usoh>
  //                 Yui T. <https://github.com/yuit>
  //                 Yamagishi Kazutoshi <https://github.com/ykzts>
  //                 Justin Hall <https://github.com/wKovacs64>
  //                 Andriy2 <https://github.com/Andriy2>
  //                 Piotr Błażejewicz <https://github.com/peterblazejewicz>
  // Definitions: https://github.com/DefinitelyTyped/DefinitelyTyped

  import * as React from 'react';

  interface OtherElementAttributes {
    [key: string]: string | number | boolean | null | undefined;
  }

  type HtmlProps = JSX.IntrinsicElements['html'] & OtherElementAttributes;

  type BodyProps = JSX.IntrinsicElements['body'] & OtherElementAttributes;

  type LinkProps = JSX.IntrinsicElements['link'];

  type MetaProps = JSX.IntrinsicElements['meta'];

  export interface HelmetTags {
    baseTag: any[];
    linkTags: HTMLLinkElement[];
    metaTags: HTMLMetaElement[];
    noscriptTags: any[];
    scriptTags: HTMLScriptElement[];
    styleTags: HTMLStyleElement[];
  }

  export interface HelmetProps {
    async?: boolean | undefined;
    base?: any;
    bodyAttributes?: BodyProps | undefined;
    children?: React.ReactNode;
    defaultTitle?: string | undefined;
    defer?: boolean | undefined;
    encodeSpecialCharacters?: boolean | undefined;
    htmlAttributes?: HtmlProps | undefined;
    onChangeClientState?:
      | ((newState: any, addedTags: HelmetTags, removedTags: HelmetTags) => void)
      | undefined;
    link?: LinkProps[] | undefined;
    meta?: MetaProps[] | undefined;
    noscript?: any[] | undefined;
    script?: any[] | undefined;
    style?: any[] | undefined;
    title?: string | undefined;
    titleAttributes?: object | undefined;
    titleTemplate?: string | undefined;
  }

  /**
   * Used by Helmet.peek()
   */
  export type HelmetPropsToState = HelmetTags &
    Pick<
      HelmetProps,
      | 'bodyAttributes'
      | 'defer'
      | 'htmlAttributes'
      | 'onChangeClientState'
      | 'title'
      | 'titleAttributes'
    > & {
      encode: Required<HelmetProps['encodeSpecialCharacters']>;
    };

  class Helmet extends React.Component<HelmetProps> {
    static peek(): HelmetPropsToState;
    static rewind(): HelmetData;
    static renderStatic(): HelmetData;
    static canUseDOM: boolean;
  }

  const HelmetExport: typeof Helmet;

  export { HelmetExport as Helmet };
  export default HelmetExport;

  export interface HelmetData {
    base: HelmetDatum;
    bodyAttributes: HelmetHTMLBodyDatum;
    htmlAttributes: HelmetHTMLElementDatum;
    link: HelmetDatum;
    meta: HelmetDatum;
    noscript: HelmetDatum;
    script: HelmetDatum;
    style: HelmetDatum;
    title: HelmetDatum;
    titleAttributes: HelmetDatum;
  }

  export interface HelmetDatum {
    toString(): string;
    toComponent(): React.ReactElement;
  }

  export interface HelmetHTMLBodyDatum {
    toString(): string;
    toComponent(): React.HTMLAttributes<HTMLBodyElement>;
  }

  export interface HelmetHTMLElementDatum {
    toString(): string;
    toComponent(): React.HTMLAttributes<HTMLHtmlElement>;
  }

  export const canUseDOM: boolean;
}

Hi, I had the same issue. I found out that in my node_modules (or yarn cache), I had @types/react v17 and v18, even though I only had v18 in my package.json. I deleted the entry for v17 (@types/react only) in my yarn.lock, re-ran yarn, and it worked. I must not have updated react typings cleanly.

Attempted to upgrade a TypeScript project to React 18 and and the supposed fix was to have the latest @types/react as a resolution in the package.json:
  "resolutions": {
    "@types/react": "18.0.28"
  },

Wrapper did not work in our case while we attempted to upgrade a TypeScript project to React 18. The supposed fix was to have the latest @types/react as a resolution in the package.json:
  "resolutions": {
    "@types/react": "18.0.28"
  },

Ran into this same error with:

"react": "18.2.0",
"react-helmet": "6.1.0",
"@types/react": "18.2.24",
"@types/react-helmet": "6.1.7",

Adding the "resolutions" section as mentioned by @sutt0n appears to have fixed our issue as well.


Invalid checksum does not throw an exception

Hi @ohyeah521 , rechecked this, and I believe an exception should be thrown when an invalid checksum is found.
On what grounds do you believe this should be converted to a warning?
Is there a case where a valid APK shows this behavior?


Error after installing draft-js with webpack

Hello i just have install draft-js (last version) and i'm getting this hole errors!
i have installed react-dom and in my component i have imported react, react-dom and draft-js like this
import React, { Component } from 'react';
import ReactDOM from 'react-dom';
import Radium from 'radium'
import Calendar from './Calendar'
import IconLabel from '../../commons/IconLabel'
import moment from 'moment'
//draft-js
import {Editor, EditorState} from 'draft-js';

.....

render(){
       return (
<Editor />
)
}

Errors in console

React version : 15.3.0
Draft version : 0.8.0
fbjs version : 0.8.0
Webpack version : 1.13.1
How can i fix this?

This sounds like a dependency issue. Try deleting your node_modules folder and running npm install again.

Thanks for you quick replay @adrianmc after install draft-js i need to restart hole webpack server, thanks! so issue is closed


O8S Trigger ID's

I noticed while browsing around the trigger ID's that are in the O8S.js file that two are using " instead of '. I don't know if it causes any issues. The two are:
"O8S Past's End"
"O8S Future's End"

When you use the double quote like that, it simply prevents you from having to escape the apostrophe.
'O8S Past's End' would be the same effect, but the other way looks cleaner and achieves the same effect.
No harm there.

This is all valid JS! No problems here.  :)


Add link validator

closes #18

I will integrate markdownlint action directly...

@joshmue: I have extracted the comments from the json into a table

Thank you all!


Incompatible with React 16.x

After having upgraded to React 16, the react-treeview-mui dependency no longer works:
Uncaught TypeError: Cannot read property 'string' of undefined
    at Object../node_modules/react-treeview-mui/src/ListItem.js (ListItem.js:70)
    at __webpack_require__ (bootstrap 6e287e636bcb6a3b0931:712)
    at fn (bootstrap 6e287e636bcb6a3b0931:117)
    at Object../node_modules/react-treeview-mui/src/TreeList.js (TreeList.js:17)
    at __webpack_require__ (bootstrap 6e287e636bcb6a3b0931:712)
    at fn (bootstrap 6e287e636bcb6a3b0931:117)
    at Object../node_modules/react-treeview-mui/src/index.js (index.js:8)
    at __webpack_require__ (bootstrap 6e287e636bcb6a3b0931:712)

I see package.json has not been updated in slightly over a year. Is this project still maintained? If not, perhaps it would be best to indicate this as so within the project readme.

I don't believe this project is still maintained.
Nonetheless fixing this for React 16 is fairly easy. Update the package.json + replace tap with click.
As of 16.4 tap is no longer supported facebook/react#11689.


Sock files are piling up in tmp folder. They are not getting cleared up automatically.

I am using simple code similar to as follow as shown in AMPHP parallel example. However, sock files in tmp folder keep piling up
`$executions = [];
foreach ($urls as $url) {
// FetchTask is just an example, you'll have to implement
// the Task interface for your task.
$executions[$url] = Worker\submit(new FetchTask($url));
}
// Each submission returns an Execution instance to allow two-way
// communication with a task. Here we're only interested in the
// task result, so we use the Future from Execution::getFuture()
$responses = Future\await(array_map(
fn (Worker\Execution $e) => $e->getFuture(),
$executions,
));
class FetchTask implements Task
{
public function __construct(
private readonly string $url,
) {
}
public function run(Channel $channel, Cancellation $cancellation): string
{
    return file_get_contents($this->url); // Example blocking function
}

}
`
The code runs fine but sock files are not cleared in system tmp folder. Please any suggestion what need to be done?

Thanks for pointing out this issue! The temporary file was removed if the IPC socket was explicitly closed, but was not removed if the IPC socket was closed through destruction.

Hello @trowski, i had encountered the issue of .socket files left in server /tmp/ folder, which was successfully resolved after your fix in >2.2.4.
Today after deploying an ASYNC work doing the same parallel work, I have found that the sockets are again still left in the /tmp/ folder.
I am using 2.2.9 parallel, the sync method is freeing the /tmp/ from socket but the Async does leave the .socket files.


Regex update to match only google's links.

Regex update to match only google's links.
Currently the regex is targeting all a tags in the search results, while this is working for a normal page layout, if you have different plugins that modifying the layout, stack-search crashes and have a weird behavior.

did you test it?
it not working for me.

My bad, should be working now

Deployed in version 1.7.2


Autoclicker

Script Title -
what will change - Adding a script for Autoclicker in Python using pynput

I would like to work on this issue.


Independent build tasks dependent on the performed changed (build.dev)

We already commented out the clearn.dev task so it might be appropriate to implement the following behavior for speeding-up the development build:

On change in an external template and/or style only copy them to the corresponding location inside of the dist/dev directory.
On change of inline template, inline style or TypeScript file, transpile them and move them to the corresponding location inside of dist/dev.

This way we will achieve some performance improvements, however, their impact should not be as dramatical as disabling type checking or using gulp-cache as described here.
Based on suggestion by @mpetkov https://github.com/mgechev/angular2-seed/issues/645.
// @ludohenin @NathanWalker @d3viant0ne

Recently, while using the seed, I had to create a task which execution takes 5s. This is a lot for dev build since it blocks everything else. I thought what I can do and with the current stateless task management (which is great but a bit limiting) there was no right way to approach.
I was thinking that we can have a global state, which mutates in utils/seed/watch.ts. So for instance:
export function watch(taskname: string) {
  return function () {
    let paths:string[]=[
      join(Config.APP_SRC,'**')
    ].concat(Config.TEMP_FILES.map((p) => { return '!'+p; }));

    plugins.watch(paths, (e: any) => {
      Config.getPluginConfig('files-changed').push(e.path);
      runSequence(taskname, () => {
        Config.getPluginConfig('files-changed').length = 0;
        notifyLiveReload(e);
      });
    });
  };
}

Later in the individual tasks, based on the file type we can:
// build.js.dev
export = (done: any, filesChanged: string[]) => {
  if (anyOfTheFilesIsTs...) {
    return gulp.src(...).pipe(ts()).pipe(gulp.dest(...));
  } else {
    done();
  }
};

What do you think? We can extend this even further by exporting not only a single function but a task object which processes only tasks of given type:
const task: ITask = {
  activate(files: string[]) {
    // decide if it should be activated
  },
  processFiles: [/*\.ts$/],
  run(done) {
    // ...
  }
};

interface ITask {
  activate(files: string[]);
  processFiles: FileType[];
  run(done: any): GulpStream | any;
}

@ludohenin @TheDonDope what do you think?

PR here https://github.com/mgechev/angular-seed/pull/1443.


Add Assign Current Density and Assign Current Density Terminal in Maxwell 3D

Description of the feature
Current Density is an excitation type that is sometimes needed, if the current density is known instead of current. Current Density Terminal needs to be specified, if Current Density excitation type is used. This is applicable to Magnetostatic and Eddy Current designs.
Steps for implementing the feature
Implementation of existing APIs:
oModule = oDesign.GetModule("BoundarySetup")
oModule.AssignCurrentDensity(
[
"NAME:CurrentDensity1",
"Objects:="		, ["NewObject_45UOWT"],
"Phase:="		, "0deg",
"CurrentDensityX:="	, "0",
"CurrentDensityY:="	, "0",
"CurrentDensityZ:="	, "1",
"CoordinateSystem Name:=", "Global",
"CoordinateSystem Type:=", "Cartesian"
])
"Phase" is applicable in Eddy Current design only.
oModule.AssignCurrentDensityTerminal(
[
"NAME:CurrentDensityTeminal1",
"Faces:="		, [35]
])
Useful links and references
No response

Please @gmalinve could you check this issue?