Clip annotator starts returning same UnicodeDecodeError on submission of all annotations

Summary
I get the same UnicodeDecodeError under different circumstances when annotating a new dataset.
Platform
App version: 1.1.1
OS: Windows 10.0.19044 Build 19044 (64-bit)
Browser: Firefox 101.0.1 (64-bit)
Address: localhost:5000
Error message
Type: UnicodeDecodeError
Text: 'utf-8' codec can't decode byte 0x92 in position 8128: invalid start byte
Full: Traceback (most recent call last): File "flask\app.py", line 1950, in full_dispatch_request File "flask\app.py", line 1936, in dispatch_request File "application\views.py", line 458, in label_clip File "dataset\analysis.py", line 134, in update_dataset_info File "dataset\analysis.py", line 29, in get_text File "codecs.py", line 321, in decode UnicodeDecodeError: 'utf-8' codec can't decode byte 0x92 in position 8128: invalid start byte

Dataset details
Audio: PCM 16-bit WAV @ 22050hz
Text: .txt file stripped of non-ASCII unicode characters.
Issue
After creating the dataset in Voice Cloning App, I went to 'Manage Datasets' and selected the new dataset from the drop-down.I successfully annotated one clip, but encountered the above error message when I hit "Submit Query" for the second clip. Subsequent annotations of different clips using both direct typing, pasting from a text cleaner, and pasting from the original in Notepad++ resulted in the same error. I am unable to annotate the dataset further.
Expected behavior
Hitting "Submit Query" would take me to the next clip needing annotation.
Steps taken

Attempted multiple forms of input
Attempted annotating different clips
Deleted all local browser data for localhost
Used a new tab
Restarted the app

Should be fixed with #133
The issue seemed to be a missing specification of utf8 as encoding when updating the metadata file.
It is neccessary to fix already "compromised" files manually as they include broken encoded characters.


[Bazel CI] name 'android_binary' is not defined

CI: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/4170#019255c7-700e-43f2-ac43-a899f5182f0c
Platform: Ubuntu
Logs:
ERROR: /var/lib/buildkite-agent/builds/bk-docker-q9xh/bazel-org-repo-root/rules_jvm_external/tests/integration/override_targets/BUILD:10:1: name 'android_binary' is not defined
ERROR: no such target '//tests/integration/override_targets:override_targets': target 'override_targets' not declared in package 'tests/integration/override_targets' defined by /var/lib/buildkite-agent/builds/bk-docker-q9xh/bazel-org-repo-root/rules_jvm_external/tests/integration/override_targets/BUILD
ERROR: Build did NOT complete successfully
FAILED:
FAILED:
ERROR: Couldn't start the build. Unable to run tests
FAILED:
Error: The command exited with status 1
error: The plugin docker command hook exited with status 1

Culprit:
Steps:
git clone https://github.com/bazelbuild/rules_jvm_external
git reset 2deeda518cf1ccb847c6e188bb3bf7d3f6fb7496  --hard
export USE_BAZEL_VERSION=166eaa09f9cd31836df898ea236e1e0633a73b12
bazel test //tests/integration/override_targets:override_targets

CC Greenteam @mai93

This is from the overall effort to remove the android rules from bazel, the work to update rules_jvm_external to Starlark rules_android is here: https://github.com/bazel-contrib/rules_jvm_external/pull/1215


Mint from ubuntu

This changes the Mint docker file to derive from ubuntu
after the dist-upgrade the docker file is 500MB rather than 2GB

Your branch appears to have everything we need


Trigger publish from release workflow

For the release of 1.0.0-beta.5, I was excited to test out the automated release workflows put in place by #190. Unfortunately, things didn't work exactly as expected. Although a release was created in response to pushing a tag, the deploy workflow didn't trigger in response to that release being created. At first I thought it was an issue with the event type, but then I saw this in the GitHub Actions documentation:

Triggering new workflows using a personal access token
When you use the repository's GITHUB_TOKEN to perform tasks on behalf of the GitHub Actions app, events triggered by the GITHUB_TOKEN will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs. For example, if a workflow run pushes code using the repository's GITHUB_TOKEN, a new workflow will not run even when the repository contains a workflow configured to run when push events occur.
If you would like to trigger a workflow from a workflow run, you can trigger the event using a personal access token. You'll need to create a personal access token and store it as a secret. To minimize your GitHub Actions usage costs, ensure that you don't create recursive or unintended workflow runs.

This PR passes the GH_PERSONAL_ACCESS_TOKEN as GITHUB_TOKEN for the actions/create-release action, which should allow one workflow to trigger the other.

The original publish flow also gets the bottling process totally wrong. I'd like to fix that in this PR.

@MaxDesiatov I know, right? Homebrew is centralized by default, and any documentation I found about the process was specific to their Brew Test Bot service. Back when it launched in 2013, virtualized macOS instances were few and far between, so I can see why that was necessary. But now in 2020 we have GitHub Actions and other infrastructure to stand that up ourselves. I'm not entirely sure when Homebrew started supporting this workflow, but I think this pattern could really start to catch on.


Update celeryworker.dockerfile

update the outdated link for installing poetry in celeryworker dockerfile

Thanks! This was solved in https://github.com/tiangolo/full-stack-fastapi-postgresql/pull/480 🎉
Given that, I'll close this one, but thanks for the effort. ☕


having problems running through jupyterhub

I'm trying to run jupyterlab_tensorboard but I'm getting a 404 error when I try to create a board.  I'm running the system behind a reverse proxy and a jupyterhub so that there may be some broken url mangling issues.

The api which the system creates is
http://big-apple.local/jupyterhub/user/user/api/tensorboard?1549244001578

please install jupyter_tensorboard first, and issue #5 may be helpful.


Msbuild.exe found in Env:Path instead of nuget.exe

What You Are Seeing?
I have setup a new Cake project using the bootstrapper script Invoke-WebRequest http://cakebuild.net/download/bootstrapper/windows -OutFile build.ps1
When I try to run the build.ps1 script I get a nuget restore error which is due to nuget.exe not being found. Instead msbuild.exe is found in the line 135 of build.ps1
$existingPaths = $Env:Path -Split ';' | Where-Object { (![string]::IsNullOrEmpty($_)) -and (Test-Path $_) }     Write-Verbose "paths $existingPaths"     $NUGET_EXE_IN_PATH = Get-ChildItem -Path $existingPaths -Filter "nuget.exe" | Select -First 1
What is Expected?
No matches should be found if nuget.exe does not exist in any of the env:Paths and it should be downloaded
What version of Cake are you using?
0.17.0
Are you running on a 32 or 64 bit system?
64bit
What environment are you running on?  Windows? Linux? Mac?
Windows 7
Are you running on a CI Server?  If so, which one?
No
How Did You Get This To Happen? (Steps to Reproduce)
Run bootstrapper
Invoke-WebRequest http://cakebuild.net/download/bootstrapper/windows -OutFile build.ps1
Run build.ps1
./build.ps1
Output Log

An error occured while restoring NuGet tools.
At D:\dev\e360\build.ps1:172 char:9

    Throw "An error occured while restoring NuGet tools."

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : OperationStopped: (An error occure...ng NuGet tools.:String) [], RuntimeException
FullyQualifiedErrorId : An error occured while restoring NuGet tools.

I'm also with this issue. The step to restore packages always look for the latest version of MsBuild, wich makes no sense, give that some development/CI teams relies on MsBuild for the target Framework that they are using.
Currently Cake looks for MsBuild v.12.xx.xx.
How do I configure the desired MsBuild Path?

@GraemeHack Is msbuild.exe  on your Path? If so , this problem is probably caused by https://github.com/cake-build/resources/issues/22
Update to the latest bootstrapper, and check to see if this still occurs.


Test if presubmit is available

@meteorcloudy I don't have access to the pipeline that failed here, can you make it public?

@keith Done!

It looks like for this to pass we need to update the NDK version we're getting on CI, but if that was done globally that would definitely break tests in bazelbuild/bazel. I guess we could have the scripts here do a download of the version we want and install that


Updated vcpkg instructions to aid discoverability

Description
Added a line for vcpkg users to discover additional opencolorio features they can build with that tool. This will help avoid people trying to build manually to enable features available via that relatively obscure package manager. Looking in the vcpkg repo isn't as helpful for people unfamiliar with that package manager or how it is configured.
Tests
None. Documentation patch only.

That's a great idea, thanks.


Build task stub

CLOUDBLD-8657
Implement the build task stub. It doesn't do anything useful, but the path from here to a functional build task should be relatively short. More info in the individual commits.
Maintainers will complete the following section

[ ] Commit messages are descriptive enough
[ ] Code coverage from testing does not decrease and new code is covered
[ ] Python type annotations added to new code
[ ] JSON/YAML configuration changes are updated in the relevant schema
[ ] Changes to metadata also update the documentation for the metadata
[ ] Pull request has a link to an osbs-docs PR for user documentation updates
[ ] New feature can be disabled from a configuration file

To try this out locally:

prepare files
/tmp/user_params.json
{"user":"acmiel","build_json_dir":"this is not used","git_ref":"idk","git_uri":"idk","image_tag":"container-registry.example.com/osbs/spam:v1.0"}

/tmp/config.yaml
version: 1

koji:
    hub_url: https://koji.example.com/hub
    root_url: https://koji.example.com/root
    auth:
        ssl_certs_dir: /var/run/secrets/atomic-reactor/kojisecret
    use_fast_upload: false

openshift:
    url: https://openshift.example.com
    auth:
        enable: True
    build_json_dir: /usr/share/osbs/

# Output registries (built images are pushed here)
registries:
- url: https://container-registry.example.com/v2
  auth:
    cfg_path: /var/run/secrets/atomic-reactor/v2-registry-dockercfg

# Default source registry (base images are pulled from here)
source_registry:
    url: https://registry.private.example.com

/tmp/build/x86_64/Dockerfile
FROM scratch

/tmp/context/workflow.json
{"dockerfile_images":{"original_parents":[],"local_parents":[],"source_registry":null,"organization":null,"__type__":"DockerfileImages"},"tag_conf":{"primary_images":[],"unique_images":[{"str":"container-registry.example.com/osbs/foo:v1.0","__type__":"ImageName"}],"floating_images":[],"__type__":"TagConf"},"prebuild_results":{"check_and_set_platforms":["x86_64"]},"buildstep_result":{},"postbuild_results":{},"prepub_results":{},"exit_results":{},"plugin_workspace":{},"plugins_timestamps":{},"plugins_durations":{},"plugins_errors":{},"build_canceled":false,"plugin_failed":false,"reserved_build_id":null,"reserved_token":null,"koji_source_nvr":{},"koji_source_source_url":null,"koji_source_manifest":{},"buildargs":{},"exported_image_sequence":[],"files":{},"image_components":null,"all_yum_repourls":[],"annotations":{},"labels":{},"image_id":null,"parent_images_digests":{}}

run (for example in the container used for running unit tests)
python3 -m atomic_reactor.cli.main -v task --build-dir /tmp/build --context-dir /tmp/context --user-params-file /tmp/user_params.json --config-file /tmp/config.yaml binary-container-build --platform x86_64

Rebased on master and resolved conflict

Fixed a few potential issues that the build_imagebuilder implementation doesn't have:

the subprocess polling loop could miss some output because I was checking poll() before calling readline()
no longer returning the empty line '' that readline() returns after the process ends

Also added the "last line as error message" that imagebuilder had

No release notes, this doesn't really do anything yet


sysdump: Collect also init container logs

Previously we only collected regular container logs, but missed the init
container logs. Gather these as well, they can be useful for debugging.

aks failure expected from forked repos

Multicluster failure is not expected, gke cluster creation failed 😐
btw looks like cilium command isn't there, cilium sysdump command failed to run. i guess @nbusseneau 's suspicion was right. cc @bmcustodio
https://github.com/cilium/cilium-cli/pull/414/checks?check_run_id=3032486960#step:16:48

btw looks like cilium command isn't there, cilium sysdump command failed to run. i guess @nbusseneau 's suspicion was right. cc @bmcustodio

Not sure what you're referring to but in this instance it's expected that cilium is not there because the cluster did not even start. Since we run the command in-cluster, there was not time to set that up :D

The following actions are failing:

AKS - Failed because I submitted the PR from a separate fork
External Workloads - Failed due to the "Missing or incomplete configuration info."

kubectl logs --timestamps -n kube-system job/cilium-cli-install
shell: /usr/bin/bash -e ***0***
...
error: Missing or incomplete configuration info.  Please point to an existing, complete config file:```

GKE - Failed a connectivity check by the looks

Test report says:2021-07-09T20:57:46.525388447Z 📋 Test Report
2021-07-09T20:57:46.525503713Z ❌ 1/9 tests failed (0/74 actions), 0 tests skipped, 0 scenarios skipped:
2021-07-09T20:57:46.525590033Z Test [dns-only]:
2021-07-09T20:57:46.525875565Z
2021-07-09T20:57:46.525901701Z Error: Connectivity test failed: 1 tests failed
error: cannot exec into a container in a completed pod; current phase is Failed
...
/home/runner/work/_temp/d5b10418-40fb-4e1d-9c33-5f27c4d98078.sh: line 4: cilium: command not found
Error: Process completed with exit code 127.

The only string matches for "failed" or "dns-only" or ❌ in the "Post-test installation logs" section of the action output are this on and one outside the logs. Despite reporting that there was a test failure, I can't find the failure itself.
Only other odd thing is that the CLI container is crashing:kube-system   cilium-cli-ckwld                                                 0/1     Error     0          15m   <IP_ADDRESS>   gke-cilium-cilium-cli-10-default-pool-f2d20591-55n8   <none>           <none>

Upload artifacts failed with:Warning: No files were found with the provided path: cilium-sysdump-out.zip. No artifacts will be uploaded.

Multicluster - Failed provisioning due to invalid argument:

ERROR: (gcloud.container.clusters.create) Operation [<Operation
clusterConditions: [<StatusCondition
canonicalCode: CanonicalCodeValueValuesEnum(INVALID_ARGUMENT, 3)
message: 'The network "default" does not have available private IP space in <IP_ADDRESS>/9 to reserve a /14 block for pods for
cluster ***Zone=us-west2-a, ProjectNum=185287498374, ProjectName=***, ClusterName=cilium-cilium-cli-1016427082-mesh-1, ClusterHash=e186c3abb89943bdaf240e0b6aad55b993854d496a384d0dbe801fe7c4c858c5***.'>]```

How do we proceed?

How do we proceed?

Thanks for the detailed analysis @joestringer!
The Multicluster and the External Workloads failures look like some sort of temporary infrastructure issues to me. For the GKE workflow we lack a sysdump which would allow further investigation. Given that, I'd propose to rebase this PR onto latest master, now that #423 and #426 are merged. These should restore sysdump creation on workflow failure/cancellation and would give us at least a sysdump for the failing GKE workflow, in case it turns out not to be a flake.

Agree with Tobias, only blocking flake was the GKE one, but lacking a sysdump it's kinda hard to know which one it was :/

The only failing test is on AKS, which is expected as this PR was opened from a fork.
Merging, thanks!


Best way to run something every N seconds, precisely

Hi!
I am looking to schedule a task with bree every N seconds. N is chosen by the user.
Let's say N=45s. This means the function should be called e.g. at 13:00:00,13:00:45, 13:01:30, 13:02:15, 13:03:00, ...
Of course this becomes more complex for other Ns, such as N=167.
Ideally I could do it like this:
later = require('later')
const textSched = later.parse.text('every 45 sec');
function logTime() {
    console.log(new Date());
}
const timer = later.setInterval(logTime, textSched);

However, this does not actually run every 45 seconds, but it actually triggers every x:00 and x:45.
Is there any way to schedule something like this?

{ interval: ms('45s') }, you could also use dayjs to build a date to start it at, e.g. { interval: ms('45s'), date: dayjs().endOf('minute').toDate() }

{ interval: ms('45s') }, you could also use dayjs to build a date to start it at, e.g. { interval: ms('45s'), date: dayjs().endOf('minute').toDate() }

Thank you for your prompt response!
Unfortunately this solution has the issue that it slowly drifts forwards. For N=5s and with a start at 00, it will log at 00, 05, 10, ...
but after a while, since it drifts by a few ms every execution, it will possibly print at 01, 06, 11, ... etc.
Do you know of any solution to this?

Thank you for your prompt response!
Unfortunately this solution has the issue that it slowly drifts forwards. For N=5s and with a start at 00, it will log at 00, 05, 10, ...
but after a while, since it drifts by a few ms every execution, it will possibly print at 01, 06, 11, ... etc.
Do you know of any solution to this?

The better approach would be to use cron, also see #9

The better approach would be to use cron, also see #9

Edit: Not #9, I meant look at local time support in https://github.com/breejs/bree/pull/76 and https://github.com/breejs/issues/74

Edit: Not #9, I meant look at local time support in https://github.com/breejs/bree/pull/76 and https://github.com/breejs/issues/74

The drifting is most likely because of code execution time, perhaps there can be optimizations done in our source code further in bree itself.

The drifting is most likely because of code execution time, perhaps there can be optimizations done in our source code further in bree itself.

The better approach would be to use cron, also see #9

Unfortunately from what I understand in CRON the same issue with values such as "every 45 seconds" occurs. Using step values (/45) causes CRON to run at 00:00 and 00:45, but not at 01:30.

The drifting is most likely because of code execution time, perhaps there can be optimizations done in our source code further in bree itself.

Indeed. This is the same behaviour of using chained setTimeouts (first example here: https://javascript.info/settimeout-setinterval#nested-settimeout). However for our usecase this is not acceptable. We need to run every N seconds, regardless of how long the task takes, not simply wait 10 seconds between executions. This is well explained in the link above.
Chained setTimeouts with corrections for this are easy to implement, but it'd be nice to be able to use all the niceties of bree for this.

The better approach would be to use cron, also see #9

Unfortunately from what I understand in CRON the same issue with values such as "every 45 seconds" occurs. Using step values (/45) causes CRON to run at 00:00 and 00:45, but not at 01:30.

The drifting is most likely because of code execution time, perhaps there can be optimizations done in our source code further in bree itself.

Indeed. This is the same behaviour of using chained setTimeouts (first example here: https://javascript.info/settimeout-setinterval#nested-settimeout). However for our usecase this is not acceptable. We need to run every N seconds, regardless of how long the task takes, not simply wait 10 seconds between executions. This is well explained in the link above.
Chained setTimeouts with corrections for this are easy to implement, but it'd be nice to be able to use all the niceties of bree for this.

Could you review our source code to check for places we could optimize to ensure accuracy?

Could you review our source code to check for places we could optimize to ensure accuracy?

It's not a matter of code efficiency. The issue is that bree uses setInterval or later.setInterval. Both tend to drift.
If you run this code: setInterval(function() {console.log(new Date())}, 2000)
you will get the following output:
2021-01-20T07:21:36.982Z
2021-01-20T07:21:38.985Z
2021-01-20T07:21:40.986Z
2021-01-20T07:21:42.988Z
2021-01-20T07:21:44.990Z
2021-01-20T07:21:46.992Z
2021-01-20T07:21:48.994Z
2021-01-20T07:21:50.995Z
2021-01-20T07:21:52.998Z
2021-01-20T07:21:54.999Z
2021-01-20T07:21:57.002Z
2021-01-20T07:21:59.003Z
2021-01-20T07:22:01.004Z
2021-01-20T07:22:03.006Z
2021-01-20T07:22:05.009Z
2021-01-20T07:22:07.010Z
2021-01-20T07:22:09.011Z

As you can see, it slowly drifts forward by a few ms every execution. After about 2-300 executions on my system, it will have drifted by a whole second (and now it executes on odd seconds instead of even seconds!).
This is well documented by several issues and blogposts. E.g.:

https://github.com/nodejs/node/issues/21822
https://gist.github.com/manast/1185904
https://stackoverflow.com/questions/8173580/setinterval-timing-slowly-drifts-away-from-staying-accurate

One solution is to use recursive setTimeouts, which automatically compensate after each execution. Or use better timing functions.
Here are a few packages addressing this:

https://www.npmjs.com/package/accurate-interval
https://www.npmjs.com/package/tasktimer
https://www.npmjs.com/package/nanotimer
https://www.npmjs.com/package/self-adjusting-interval

It's not a matter of code efficiency. The issue is that bree uses setInterval or later.setInterval. Both tend to drift.
If you run this code: setInterval(function() {console.log(new Date())}, 2000)
you will get the following output:
2021-01-20T07:21:36.982Z
2021-01-20T07:21:38.985Z
2021-01-20T07:21:40.986Z
2021-01-20T07:21:42.988Z
2021-01-20T07:21:44.990Z
2021-01-20T07:21:46.992Z
2021-01-20T07:21:48.994Z
2021-01-20T07:21:50.995Z
2021-01-20T07:21:52.998Z
2021-01-20T07:21:54.999Z
2021-01-20T07:21:57.002Z
2021-01-20T07:21:59.003Z
2021-01-20T07:22:01.004Z
2021-01-20T07:22:03.006Z
2021-01-20T07:22:05.009Z
2021-01-20T07:22:07.010Z
2021-01-20T07:22:09.011Z

As you can see, it slowly drifts forward by a few ms every execution. After about 2-300 executions on my system, it will have drifted by a whole second (and now it executes on odd seconds instead of even seconds!).
This is well documented by several issues and blogposts. E.g.:

https://github.com/nodejs/node/issues/21822
https://gist.github.com/manast/1185904
https://stackoverflow.com/questions/8173580/setinterval-timing-slowly-drifts-away-from-staying-accurate

One solution is to use recursive setTimeouts, which automatically compensate after each execution. Or use better timing functions.
Here are a few packages addressing this:

https://www.npmjs.com/package/accurate-interval
https://www.npmjs.com/package/tasktimer
https://www.npmjs.com/package/nanotimer
https://www.npmjs.com/package/self-adjusting-interval

So in short this is two issues in 1:

not being able to specify intervals like 'every 45 seconds' and have it executed correctly every 45 seconds and
If using ms('45s') or 45000, there is a drift due to the use of setInterval.

So in short this is two issues in 1:

not being able to specify intervals like 'every 45 seconds' and have it executed correctly every 45 seconds and
If using ms('45s') or 45000, there is a drift due to the use of setInterval.

Thank you so much for this @adrfantini.  Excellent writeup.  By chance are you interested in crafting a pull request to address this?

Thank you so much for this @adrfantini.  Excellent writeup.  By chance are you interested in crafting a pull request to address this?

TBH I'm not really sure where to start (and I am a complete JS noob).
I have no idea how to address 1.The way to address this would be I guess to not use setInterval and instead

TBH I'm not really sure where to start (and I am a complete JS noob).
I have no idea how to address 1.The way to address this would be I guess to not use setInterval and instead


adapters now require node-fetch to be a dependency of the app

Describe the bug
Unanticipated side-effect of https://github.com/sveltejs/kit/pull/1066 — node-fetch isn't available when the app is built on e.g. Netlify:

We could make it a peer dependency of the adapters, but that would suck. I think it might be better if adapters took responsibility for bundling the output of svelte-kit build (with eg. esbuild — this functionality could also be exposed via the adapter utils). Then, if we exposed something like @sveltejs/kit/install-fetch for the relevant adapters to use (rather than expecting them to use the correct version of node-fetch and correctly assign the relevant bits to globalThis), it wouldn't mean needing @sveltejs/kit to be a production dependency.
Severity
Completely blocks use of the affected adapters, AFAICT

I am hit by this as well trying to deploy to Netlify.  Is there any kind of work around?
{"errorType":"Error","errorMessage":"Cannot find package 'node-fetch' imported from /var/task/src/handler.mjs","trace":["Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'node-fetch' imported from /var/task/src/handler.mjs","    at packageResolve (internal/modules/esm/resolve.js:650:9)","    at moduleResolve (internal/modules/esm/resolve.js:691:18)","    at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:784:11)","    at Loader.resolve (internal/modules/esm/loader.js:100:40)","    at Loader.getModuleJob (internal/modules/esm/loader.js:246:28)","    at ModuleWrap.<anonymous> (internal/modules/esm/module_job.js:47:40)","    at link (internal/modules/esm/module_job.js:46:36)"]}

downgrade
installing node-fetch as a prod dependency in your app might fix it?

Weirdly I have the same problem now, neither a downgrade or installing the node-fetch as prod dependency fixes it.

Fixed with netlify adapter 7

Working fine after upgrading to "@sveltejs/adapter-netlify": "^1.0.0-next.7" and "@sveltejs/kit": "1.0.0-next.80"

I can confirm this as well. It also should be noticed that netlify-adapter now uses .netlify subdirectory so netlify.toml should be updated accordingly. The "node-fetch" dependency  should be removed completely as in  sveltejs/realworld.

This should be fixed now — #1091


NN-keras-H2O

Document all the installation processes.
Include more examples.

Best Tutorials:

https://github.com/h2oai/h2o-tutorials


useBuyerJourneyIntercept impossible to know what triggers it.

Please list the package(s) involved in the issue, and include the version you are using

"@shopify/ui-extensions": "2023.7.0",
"@shopify/ui-extensions-react": "2023.7.0"
Describe the bug

Currently it is impossible to know what is triggering the intercept. The issue that this cause is that if you are trying to block the checkout based on an information selected on a later step, you might not be able to make the correct decision about blocking or not the checkout.
Another example we encountered was about adding a third party gift card system. We needed to intercept when the user is trying to complete the order to lock the amount used on the third party gift card. Since we couldn't detect that particular step we had to go with another less ideal solution.
Steps to reproduce the behavior:
For example if you are trying to block the checkout if the selected shipping method is "standard", when you are on the information step you will get that the selected shipping method is "standard" but the user is not yet at the shipping method step so you wouldn't want to block the checkout yet. You would want to wait at least the shipping method step to block but right now it is now possible to know.
Expected behavior
I would expect some kind of property coming from the intercept telling us what is triggering the intercept.
Something like that:
useBuyerJourneyIntercept(({
  interceptLocation
}) => {
  if (interceptLocation != "information") {
    return {
      behavior: 'block',
      reason: 'Blocking from a step after the information step',
    }
  }

  return {
    behavior: "allow"
  }
}

The proposal you show in the top is perfect, in my case I had to use static targets, this way I make sure that the component reacts to t he user's interaction.
Have you tried using a react hook? How does  useDeliveryGroup to know where the user is located or some other API?


Expires value gets sometimes automatically set to null

Hi there,
I am using angular-cache 4.4.3 like this:
Configuration
  CacheFactory('listCacheOnline', {
    maxAge: 15 * 60 * 1000, // Items added to this cache expire after 15 minutes
    deleteOnExpire: 'aggressive', // Items will be deleted from this cache when they expire
    storagePrefix : 'my.news.',
    capacity : 1,
    storageMode: 'localStorage'
  });

Get data:
  $http.get(url, {cache: CacheFactory.get('listCacheOnline')}).then(function (result) {
    doSomethingWith(result);
  });

As you can see I am using 15 min expire time, so after 15 mins I'd expect that angular-cache invalidates this cache entry and gets fresh data from the server. I noticed though that this sometimes does not work. After running my app for a while (especially after not using it for a day or so) I noticed that it won't get the fresh data from the server any more.
When I looked into the issue I saw that the "data" value in localStorage had an attribute called "expires". This is sometimes set to null. If this happens my app will never get fresh data from the server and is stuck at this point. I have to manually flush localStorage and then it starts working normally again with "expires" actually containing a timestamp value until it stops working again when this null value reappears out of nowhere.
So, my question is: How is it possible that expires is set to null with the configuration set above?

I'm not sure, I will have to investigate.

Hi,
Just to say I have observed this behaviour today when using a cache config like so:
        $http.defaults.cache = CacheFactory.createCache('offlineCache', {
            deleteOnExpire: 'none',
            maxAge: 10000,
            storageMode: 'localStorage'
        });

For me, switching deleteOnExpire to passive seems to resolve the issue (at least in my limited testing). However, it seems in this scenario that the cache entry will be served to $http after expiry is reached (which is the behaviour I want, but it seems like none was the correct option to use for that?).
angular-cache 4.4.3
angular 1.3.20
chrome 47.0.2526.106

I'm seeing the expires value set to null as well, but my configuration is using deleteOnExpire: 'passive'.
CacheFactory.createCache('SocialManagerSelectorCache', {
        maxAge: 3 * 60 * 60 * 1000, // 3 hours
        deleteOnExpire: 'passive',
        storageMode: 'localStorage'
      });

Do any of you think this issue might be fixed by jmdobry/CacheFactory#8?

I tried a number of different parameter order configurations related to jmdobry/CacheFactory#8 and I still occasionally see a null expiry on all of them.
Also related, I believe #212 is being affected by this. When using localStorage, this line will return true, triggering the clearing of the key in localStorage.

Should be working better now: https://plnkr.co/edit/Cc1xT8Ra3PWXQvl2J9zs?p=preview

:+1: Thanks!


NOT WORK

hmmm thats interesting
can i get more info on whats happening?

i injected with extreme injector manual map in cs2.exe and all settings are on low windowed mode

not meant to be injected with manual map
loadlibrary only (called standard injection in extreme injector).


problem cleaning and rebuilding public folder on windows

I have patternlab running with grunt and i've set the watch task to do the following
            html: {
                files: ['source/_patterns/**/*.mustache', 'source/_patterns/**/*.json', 'source/_data/*.json'],
                tasks: ['shell:patternlab'],
                options: {
                    spawn: false
                }
            },

with shell:patternlab doing the following
        shell: {
            patternlab: {
                command: "php core/builder.php -g"
            }
        },

this works on a mac, but not back home on my windows machine. everytime i change the content of a pattern i get these warnings:

>> File "source\_patterns\00-atoms\01-global\00-colors.mustache" changed.

Running "shell:patternlab" (shell) task
configuring pattern lab...

Warning: rmdir(C:\xampp\htdocs\living-styleguide-boilerplate\patternlab\core\lib\PatternLab/../../../public/css\partials): Directory not empty in C:\xampp\htdocs\living-styleguide-boilerplate\pa

tternlab\core\lib\PatternLab\Builder.php on line 1243

Warning: rmdir(C:\xampp\htdocs\living-styleguide-boilerplate\patternlab\core\lib\PatternLab/../../../public/css): Directory not empty in C:\xampp\htdocs\living-styleguide-boilerplate\patternlab\
core\lib\PatternLab\Builder.php on line 1250

Warning: rmdir(C:\xampp\htdocs\living-styleguide-boilerplate\patternlab\core\lib\PatternLab/../../../public/js): Directory not empty in C:\xampp\htdocs\living-styleguide-boilerplate\patternlab\c
ore\lib\PatternLab\Builder.php on line 1250

Notice: Undefined property: PatternLab\Generator::$xipHostname in C:\xampp\htdocs\living-styleguide-boilerplate\patternlab\core\lib\PatternLab\Builder.php on line 188
your site has been generated...

site generation took 2.0804319381714 seconds and used 4MB of memory...

PHP Warning:  rmdir(C:\xampp\htdocs\living-styleguide-boilerplate\patternlab\core\lib\PatternLab/../../../public/css\partials): Directory not empty in C:\xampp\htdocs\living-styleguide-boilerpla
te\patternlab\core\lib\PatternLab\Builder.php on line 1243

PHP Warning:  rmdir(C:\xampp\htdocs\living-styleguide-boilerplate\patternlab\core\lib\PatternLab/../../../public/css): Directory not empty in C:\xampp\htdocs\living-styleguide-boilerplate\patter
nlab\core\lib\PatternLab\Builder.php on line 1250

PHP Warning:  rmdir(C:\xampp\htdocs\living-styleguide-boilerplate\patternlab\core\lib\PatternLab/../../../public/js): Directory not empty in C:\xampp\htdocs\living-styleguide-boilerplate\pattern
lab\core\lib\PatternLab\Builder.php on line 1250

PHP Notice:  Undefined property: PatternLab\Generator::$xipHostname in C:\xampp\htdocs\living-styleguide-boilerplate\patternlab\core\lib\PatternLab\Builder.php on line 188

not sure what's happening. also every task triggered by the watch task just hangs. I've opened a question on stack overflow about it: http://stackoverflow.com/questions/35524119/grunt-tasks-hanging-and-not-responding
any task i execute directly (not via the watch task) are successfull.

any suggestions? it used to work and just stopped compiling at some point.

can this be related? https://github.com/nodejs/node-v0.x-archive/issues/6960

I'm getting issues with the rebuild/update using just the PHP builder from the guide let alone applying grunt.  It doesn't even error.  Just says great here you go and then Nah!

@ vlrprbttst
Just a quick thing I noticed, does it make any difference in the errors that some of the file paths include \ as well as / in them?
example
Warning: rmdir(C:\xampp\htdocs\living-styleguide-boilerplate\patternlab\core\lib\PatternLab/../../../public/css\partials):

@eyeamaman I didn't notice! maybe. i'll check it out as soon as i can

@vlrprbttst
So with a repo that doesn't include the public folder I get the same issue. Which isn't useful for when other collaborators try to init the project.  So I've:

removed git ignore on source content
added gulp task "init" which
-- copies the "core/styelguide/**/*" content into "./public/styleguide"
-- builds the project

Seems to work so far, so I guess you could do the grunt equivalent :-)
gulp.task('create', function() {
  gulp.src(['core/styleguide/**/*'])
    .pipe(gulp.dest('./public/styleguide/'));
});

gulp.task('build', shell.task([
  'php core/builder.php -g'
]));

gulp.task('init', function() {
  runSequence('create', ['build']);
});


JS Capstone Project - II

Hello 👋, In this PR we:

Use TV Maze API to create Blase-TV.
Use Involvement API to store user interaction.
Add a movie, comment, and, reservation counter.
Show recent comments added by visitors.
Dynamically added comment and reservation pop-up modal.
Dynamically display multiple HTML pages using JS.

Note: There is a browser error upon fetching an empty array of reservations from the Involvement API provide by microverse.

Here is the presentation link: https://drive.google.com/file/d/1WV3Tpaqe5hd5-PlzI4sOG1bVk6YtHAzU/view?usp=share_link


Order of command line arguments

I think it's good to re-order the command line arguments:

For consistency between the three tools
To have the most useful/used arguments on top

Also group similar functonality together, such as all options related to clustering


Log4j vulnerability -  CVE-2019-17571

Azkaban use log4j 1.2.16 version (which is oldest) and in this version vulnerability is kind of  CVE-2021-44228.
Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.
With this task  log4j version should be the 2.15.0.
If its ok, I'm willing to upgrade version.

Any updates on this? I think this might need some further attention. 🤔

Any updates on this? I think this might need some further attention. 🤔

I opened a pull request. https://github.com/azkaban/azkaban/pull/3033


Option to keep the same position on refresh

It would be great to have an option that allows all items to keep their position on refresh.
For example, if an item has a height of 200px, but then gets extra content pushed to it after page load to make it 500px, all the other elements after it get moved around and reordered into different rows/columns. This can confuse the user since they thought that an item was in one place, yet it has now been moved completely.
Would this be a difficult option to add?

But the others have to be moved around to make room for the bigger item.
Or do you mean, you just want the columns to be reorderd and not the rows?

Correct. So if the height changes on a particular item, just to push down the items below it instead of reordering all the other items into different columns and confusing the user.


Typings are not excluded from the source control

By default the typings folder is not excluded from the source control. Given that all default typings are public and available centrally they shouldn't be included in the source control but listed in tsd.json so that they can be restored.

With Typescript 2.0, the whole typings mechanism will change. SPFx will move to TypeScript 2.0 when it gets released. And hence, we do not need to fix this at the current time. Please let us know if you still think this is an issue.

I guess that depends on when TypeScript 2.0 will be released. If it's released after SPFx reaches GA then this is a bug that should be fixed. If SPFx gets updated before GA to TS 2.0 then I'd say it's fine for the time being.

FYI for our internal projects, we started with the approach you described above.  However, we had problems because the tsd tool (which has now been abandoned by its author) did not always accurately recreate the typings files when you run "tsd install".  Also sometimes we needed to make local edits to the typings files.  These files are tiny, so the safest policy is simply to include them in your Git repo.


[Hacker Rank]: Warmup: Simple Array Sum. Solved ✅.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (d7a451e) to head (3669303).

Additional details and impacted files
@@            Coverage Diff            @@
##              main        #7   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            6         7    +1
  Lines           63        68    +5
=========================================
+ Hits            63        68    +5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


UZ employee cannot log in

Bug description

This person: https://telefoonboek.prd.rad.ugent.be/nl/people/801000591050
Gets this error:

I can log in to his account via "View as"

Do we need extra information? I can ask him in the helpdesk.

This person cannot be found in the UGent LDAP.
UZGent is actually problematic: some are in the UGent LDAP, while others aren't,
so hard to make up a policy (e.g. you can specify which external IDP's you want to allow in openid connect)

There is apparently no UZ way to log in. Users can only log in with an UGent account.
What went wrong:
He tried to log in with an UZ mail address instead of his UGent username and password.
Will try to help him like this.


Event handles called twice

It seems that with services.AddMediatR(); in Startup.cs, all the event handles have been registered automatically.
Explicit register as below will result to handles being called twice.
services.AddTransient<INotificationHandler, OrderChangedCreateOrderHistoryHandler>();

Asking for just learn, why have you registered OrderChangedCreateOrderHistoryHandler to service as twice in Modules/Orders/ModuleInitializer.cs? I couldn't figure out purpose of it.


fixed warning: Object#=~ is deprecated; it always returns nil

ruby 2.6.0-rc1 was released.
https://www.ruby-lang.org/en/news/2018/12/06/ruby-2-6-0-rc1-released/
When I tested on 2.6.0-rc1. Following warnings is outputted:
$ bundle exec ./exe/rspec
/lib/rspec/core/metadata.rb:172: warning: Object#=~ is deprecated; it always returns nil

SEE ALSO: https://bugs.ruby-lang.org/issues/15231

Thanks :)


SAK-41551 Added gradebook to data creation job

Looks good to me @adrianfish , good job. This is basically to populate demo data, right?

@mpellicer Yes, it is. It's the job scheduler task, not sakai.demo=true


[5.3] Add toggle() method to BelongsToMany relation

Following a suggestion of @JeffreyWay on Twitter, I have implemented the toggle() method on the BelongsToMany relation.
This methods accepts a model, collection, id or array of ids, and toggles them in the pivot table. By "toggle" I mean that, if the item already exists, it's detached, and if it not exists, it's attached.

I haven't looked at the PR yet, but, yeah, a toggle() would be very useful.

I'm really curious of a specific use case for this where you wouldn't just be using sync?

I'm not sure if sync would work in this case? Because we're only interested in toggling a single row, rather than all rows associated with the user. Can I use sync for that?
If nothing else, one argument is that sync() isn't overly clear. $user->completions()->toggle($video) makes more sense to me, personally.
For use cases, everything from:

Toggle a video completion at Laracasts. If it's completed, we want to uncomplete. If it doesn't exist, then add the row to mark it as a complete.
Toggle a favorite in the pivot table
Toggle a "watch later"

Stuff like that. But yeah, if sync() works here, it may not be needed. Just not sure that it does.

@taylorotwell, the sync methods replace all entries in the pivot table with the given one's.
The "toggle" method is initially thought to attach or detach an entry to the pivot table, based on the previous existence. For example, if you want to toggle only one model/id, it will detach it if it exists, or attach it if it doesn't.
It also works with multiple models/ids, detaching the existing ones, attaching the non existing, and leaving the rest of the previous existing ones without changes.

OK cool thanks for info.


Artstation no longer working

Ripme version: 1.7.82
Java version: java version "1.8.0_202"
Java(TM) SE Runtime Environment (build 1.8.0_202-b08)
Java HotSpot(TM) 64-Bit Server VM (build 25.202-b08, mixed mode)
Operating system:  Microsoft Windows [Version 10.0.17763.437]
Exact URL you were trying to rip when the problem occurred:
https://www.artstation.com/2buiart
Please include any additional information about how to reproduce the problem:

Expected Behavior
the ripper would get me the pictures from the gallery
Actual Behavior
Error while loading https://www.artstation.com/users/2buiart/quick.json
org.jsoup.HttpStatusException: HTTP error fetching URL. Status=403, URL=https://www.artstation.com/users/2buiart/quick.json
at org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:459)
at org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:434)
at org.jsoup.helper.HttpConnection.execute(HttpConnection.java:181)
at com.rarchives.ripme.utils.Http.response(Http.java:130)
at com.rarchives.ripme.utils.Http.getJSON(Http.java:120)
at com.rarchives.ripme.ripper.rippers.ArtStationRipper.getGID(ArtStationRipper.java:64)
at com.rarchives.ripme.ripper.AbstractRipper.getAlbumTitle(AbstractRipper.java:498)
at com.rarchives.ripme.ripper.AlbumRipper.setWorkingDir(AlbumRipper.java:193)
at com.rarchives.ripme.ripper.AbstractRipper.setup(AbstractRipper.java:179)
at com.rarchives.ripme.App.rip(App.java:98)
at com.rarchives.ripme.App.handleArguments(App.java:182)
at com.rarchives.ripme.App.main(App.java:74)

any fix for this?

The fix has been merged and should be in the next release of ripme

1.7.83 still has this issue!

Oh no, I worded it incorrectly. What I meant was 1.7.83 also has the issue, not still has issue.

Oh no, I worded it incorrectly. What I meant was 1.7.83 also has the issue, not still has issue.

@UnforeseenOcean last reply was 4 days ago when he said he solved the problem. 1.7.83 was much before that. Calm down it will be solved next release.


Ignore coingecko failing tests

Usually due to rate limits
Fix a bug on the indexer status endpoint, as both tests depend on each other to pass

Only mentions that I would like to have in the description the fix of erc20 indexing.

Done!

Could we do at the same way here? https://github.com/safe-global/safe-transaction-service/blob/master/safe_transaction_service/history/tests/clients/test_ens_client.py#L29

What do you mean?


proc: step now goes to next line, including funcs

This patch modifies the step command to step to the next source line,
stepping into any function encountered along the way.
Fixes #360

Not mentioned in commit msg, but it also introduces the step-instruction command, which has parity with how step used to work (steps exactly 1 cpu instruction).
cc: @aarzilli

LGTM


Updated link to langchain instructions

Looks like the docs file structure changed at some point.

thanks your patch.


Please merge radix-ui's icon library to support nextjs & react19

Question
Please merge radix-ui's icon library to support nextjs & react19

please do merge

anyone?


Automated Package Upgrade

:tada: This PR is included in version 7.7.153 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add plan year end date

For https://rippling.atlassian.net/browse/BENFLEX-2333

@Kingpin007 added


Can I open another component inside modal window?

I really like your smart modal. But I have one question.
I would like to open another component inside your modal.
Example:
<ngx-smart-modal #modalData
                   identifier="modalData"
                   customClass="nsm-dialog-animation-ltr">

Hey I am chart modal

      <tradingview [symbol]="'XXX'"></tradingview>

    <button class="button -dark"
            (click)="modalData.close()">Close</button>
  </ngx-smart-modal>

tradingview  is my component.
But the problem is that is never called and executed.

Hello, yes of course you can open a component inside a modal.
Like here => https://stackblitz.com/edit/angular-ws258v
You may have forgotten to import this component into your module 😄

No I import it. But the content is not shown. Can you provide whole example. And my component has another component call inside ...

Look at https://stackblitz.com/edit/angular-ws258v
I updated it with your code

Maybe is problem because I am not loading static but dynamic data in component. I need to reinitialize ngOnInit() method after modal is open and prepare data.

Can you give me an exemple of your problem on stackblitz please ?

I will try to prepare it.
In the meanwhile. Can you test if in TradingViewComponent class ngOnInit will be executed after modal is open?

I just tested it and it is not
import { Component, Input, OnInit, OnDestroy } from '@angular/core';

@Component({
  selector: 'tradingview',
  template: `

I'm a component inside another component

  `,
  styles: [`h1 { background-color: red; }`]
})
export class TradingViewComponent implements OnInit, OnDestroy {

  ngOnInit() {
    alert('test')
  }

  ngOnDestroy() {
  }

}

It's because I import it on app.module, then he init on start of application. If you want to init the composant on modal open. Just add a ngIf condition on the component.
<tradingview *ngIf="modalData.visible"></tradingview>

@senzacionale Is there still a need to keep this issues open?

Hey. Sorry for delay. It is working very well. Thank you!


These attributes are better for the final state(#13628)

These attributes are better for the final state(#13628)
Description

ok i will do this
---Original---
From: "Greg @.>
Date: Fri, Aug 9, 2024 23:12 PM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [apache/lucene] These attributes are better for the finalstate(#13628) (PR #13630)
@gsmiller commented on this pull request.
In lucene/backward-codecs/src/java/org/apache/lucene/backward_codecs/lucene99/Lucene99SkipWriter.java:
>    private long[] lastSkipPosPointer;    private long[] lastSkipPayPointer;
@mrhbj were you planning to push an update to this PR that also marks these fields final? Thanks!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Closing in favor of #13639


Confusion about image->caption example

Hello,
Thank you for creating a great repository. I'm new to x-transformers and I'm a bit confused about the provided sample usage for image captioning:
import torch
from x_transformers import ViTransformerWrapper, TransformerWrapper, Encoder, Decoder

encoder = ViTransformerWrapper(
    image_size = 256,
    patch_size = 32,
    attn_layers = Encoder(
        dim = 512,
        depth = 6,
        heads = 8
    )
)

decoder = TransformerWrapper(
    num_tokens = 20000,
    max_seq_len = 1024,
    attn_layers = Decoder(
        dim = 512,
        depth = 6,
        heads = 8,
        cross_attend = True
    )
)

img = torch.randn(1, 3, 256, 256)
caption = torch.randint(0, 20000, (1, 1024))

encoded = encoder(img, return_embeddings = True)
decoder(caption, context = encoded) # (1, 1024, 20000)

I suppose the code is for model training, where pairs of [img, caption] is available.

Why do we feed caption (our target predictions) into the decoder? Shouldn't the decoder only take encoded as input, and produce predictions for caption?
How should I use the trained model for inference, when onlyimg is available (andcaption is unknown/hidden)?

Thanks in advance!

I also have the same question, hoping to clarify it. Thank you!


[BUG] ZHA Light groups doesn't turn of children

Describe the bug
Since I'm not sure where to report I also reported here: https://github.com/home-assistant/core/issues/76205
I have 3 groups of GU10 spots.
1 group is IKEA > This group works well!
2 groups are eWeLink > These have issues.
When I turn on the ZHA group entity the children respond normally. However, when I turn off the ZHA group then the children still lists as being ON (even though the light is off!).
After a few minutes one-by-one the devices register as OFF again, most likely since they report this themselved.
Expected behavior
The group children should turn off as well :)
Screenshots
If applicable, add screenshots to help explain your problem.

Device signature
{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice: 142>, manufacturer_code=0, maximum_buffer_size=80, maximum_incoming_transfer_size=160, server_mask=0, maximum_outgoing_transfer_size=160, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": 49246,
      "device_type": "0x0210",
      "in_clusters": [
        "0x0000",
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0006",
        "0x0008",
        "0x0300"
      ],
      "out_clusters": []
    },
    "13": {
      "profile_id": 49246,
      "device_type": "0xe15e",
      "in_clusters": [
        "0x1000"
      ],
      "out_clusters": [
        "0x1000"
      ]
    }
  },
  "manufacturer": "eWeLight",
  "model": "ZB-CL01",
  "class": "zigpy.device.Device"
}

Additional context
No idea what to find further.

Its looks like the eWeLink is not reporting off state as Zigbee standard and ZHA is pulling its status some minutes later and updating the device status and then all is off ZHA is making the group off.
I have read some similar problem but i cant remember with brands it was.
Philips HUE is not reporting at all and ZHA is pulling the lights for getting  the status from then and i thin its one or 2 more brands that have the same fix.

Hi @MattWestb
Thank you for your quick reply again!
How was it fixed for these devices? I honestly thought that ZHA would simply turn off the children within HA.

Philips HUE is "hard coded" for pulling the status from the device in ZHA.
I think @TheJulianJES (sorry for pinging you directly) is knowing more of the "bad" no standard Zigbee lights and how its working.
ZHA is waiting that the device in light groups is updating there state and if the device is not reporting its changed state ZHA is not putting the light group in off state.
Zigbee light devices shall reporting there changes state to the coordinator (or configured device / address) if its being changed so the coordinator dont need spamming the network with pulls all the time to all lights in the system for getting its status.
You can try reconfigure the device from the device card and see if they is start reporting OK but i think its not helping then on state is reported OK.

Thanks for the detailed report!
Do you know if these eWeLink lights in ZHA groups were also broken in HA 2022.7.x?
When a ZHA light group is turned on/off, it waits about a second (default turn on/off transition time of most lights) and then polls all individual group members for their status.
(For single Hue lights, this is done in a 3-5 minute interval. For all other "single" lights, it's done every 45 to 70 minutes IIRC.) If an attribute reports is received after that 1.25 second delay, it also gets parsed.
For the eWeLink lights, can you check the following attribute (ZHA -> Devices -> eWeLink light -> three dots -> Manage Clusters -> select OnOff cluster -> select on_off attribute -> Read attribute:

The attribute should read Bool.false when the light is off and Bool.true when it's on. (Please check if this works)
Otherwise, turn on debug logging (restart HA), then wait a bit and turn on/off a ZHA group. Then send the relevant log part here.
https://www.home-assistant.io/integrations/zha/#debug-logging

Hi @TheJulianJES
Checked the cluster and this works as you mentioned!
So the spots turn off but ZHA doesn't yet check it's status?
I also tested turning the group on and off. Once the group was off (and the spot still reports as on) I checked the cluster again an ZHA instantly updated and turned the light off in HA.
For this reason I think (guess) the bulb isn't the issue. Even if I get the cluster value instantly after turning off the group it reports as off (Bool.false) and HA is updated.
Oh and yes, the same issue occurs on 2022.7.x

Please reconfigure each bulb and post screenshots of the dialogs. Also provide a debug log as described by @TheJulianJES

Hi @dmulcahey
Reconfiguration can be done without issues. See screenshot below.
I'd very much like provide log data but I'll need a bit of help on how to filter out the relevant records. I have 60 devices in ZHA so if I simply log everything it will be a mess I suppose.

Check if the behavior is now different after reconfiguration.
Regarding the logs: each Zigbee bulb has a unique Nwk id (like 0xe77c). That can be found on the device page and in some log lines.
If possible, just let HA/ZHA settle down a bit after restarting with debug logging. Then just turn on/off the ZHA group light (wait some time in between) and send the entire "log chunks" of where a group is turned on/off (even if there are other ZHA devices mixed in between).

I can handle the mess :) Just give us the nwk addresses as @TheJulianJES mentions.

Ok no problem! I'll run HA with logger asap!
I currently cannot access my PI remotely to change yaml files since I'm not at home :/

No rush. Thanks!

No hurries. FYI, the following service calls should also do the same:

Set to debug
service: logger.set_level
data:
  homeassistant.core: debug
  homeassistant.components.zha: debug
  bellows.zigbee.application: debug
  bellows.ezsp: debug
  zigpy: debug
  zigpy_deconz.zigbee.application: debug
  zigpy_deconz.api: debug
  zigpy_xbee.zigbee.application: debug
  zigpy_xbee.api: debug
  zigpy_zigate: debug
  zigpy_znp: debug
  zhaquirks: debug

Reset to info
service: logger.set_level
data:
  homeassistant.core: info
  homeassistant.components.zha: info
  bellows.zigbee.application: info
  bellows.ezsp: info
  zigpy: info
  zigpy_deconz.zigbee.application: info
  zigpy_deconz.api: info
  zigpy_xbee.zigbee.application: info
  zigpy_xbee.api: info
  zigpy_zigate: info
  zigpy_znp: info
  zhaquirks: info

Hi @dmulcahey and @TheJulianJES
I'm a bit flabbergasted at the moment. Just updated to 2022.8.1 and it seems the issue is gone :/
However, I don't see and ZHA related changes in the logs..
While I hate to admit it, I'm now thinking the restart might have simply fixed it..
Could it be that the Zigbee network had too much spam?

I have also having problem for some versions ago that controller (IKEA and tuya remotes) was "silent" (was not getting zha_event) but was starting reporting after HA restart.
ZHA change log is in HA release notes https://rc.home-assistant.io/changelogs/core-2022.8 only need searching for "ZHA" and is normally linking to zigpy release notes if its changes made in the Zigbee libs.
Glad that your spots start reporting OK and hope its staying so !!

Hope so you! Sorry to waste your time.
If I encounter the same issue again I will start with the logs directly :)


Fields not showing

Hi,
I have installed package and cast my json field - imported with use statement t the top as so:
use Laravel\Nova\Fields\Text;
use Stepanenko3\NovaJson\JSON;

// other use statements and code

public function fields(NovaRequest $request)
    {
        return [

            ID::make()->hideFromIndex()->sortable(),
            JSON::make('Custom Fields', [
                Text::make('Field 1', 'field1'),
                Text::make('Field 2', 'field2'),
                // Add more fields as needed
            ]),

However unfortunately this has not worked for me - on Nova detail and edit it shows label name but no text fields.
https://share.getcloudapp.com/xQuRodN4
Any idea why would be much appreciated.

@HeadStudios
I have completely redesigned the JSON package, please check the documentation


Doesn't work with pymdownx.superfences (9.0)

#19 only supports pymdown-extensions < 9.0, but with the update the support is broken again.

_legacy attribute for default validator was dropped (see extension.py#L102), thus an exception was triggered by custom_fences configuration of markmap.


Design System > Build Verification > [Version <IP_ADDRESS>] received on 8thNov 2024

Design System > Build Verification > [Version <IP_ADDRESS>] received on 8thNov 2024

Sr.No
PR
GitHub   Link
Status
Remark
Dev
QA

1
Completed   Task 777 : Design System > Elements > Enhancements in file uploader   by @abhijeetjawale1 in #957

2
Resolved   Bug 862 : Design System > Components > Alert Popup > Default >   Popup cancel delete button is not working by @DeepashriDatar in #983

3
Resolved   Bug 749 : Design System > Element > Alert : Alert issues by @nitinsonawane123 in #986

4
Resolved   Bug 969 : Design System >Elements > Payment Card > Default >   Label and button alignment issue by @nitinsonawane123 in #980

5
Resolved   Bug 810 : Component > Datatable > Action button on Left side > Not   able to see the 'Edit' option after hovering over the row below in the table   by @VenuKG in #985

6
Resolved   Bug 892 : Design System > Components > Testimonials > Default >   UI issues by @poojagurav21 in #955

7
Resolved   Bug 671 : Storybook > Component > Forms basic > Required message is   not display by @nitinsonawane123 in #993

8
Completed   Task 742 : Badge minor issue & enhancement is completed by @suchithravipin1991 in #998

9
Resolved   Bug 752 : Design System > Badge Minor issue resolved by @suchithravipin1991 in #757

10
Completed   Task 1001 : Elements > Enhancement > Nav Tab : Enhancements in nav tab   > File Mover : Dynamic Icons > New Element > Button Grid by @DeepashriDatar in #1010

11
Resolved   Bug 659 : Storybook > Components > Contact Us > Default >   Displaying multiple error messages at the one time by @nitinsonawane123 in #1004

12
Completed   Task 981 : Design-system > Create icon for custom images for RDS icon   by @rahulp34 in #1012

13
Completed   Task 938 : Design system enhancement in checkbox as per new project flow   by @rahulp34 in #939

14
Resolved   Bug 789 : Design System > Elements > Scrollspy > Dark theme Go Top   button is not visible. by @abhijeetjawale1 in #1023

15
Resolved   Bug 807 : Design System > Charts > Polar Area Chart > Change theme   and size display error massage by @abhijeetjawale1 in #1025

16
Completed   Task 900 : Design System > Element > Create new element Time Picker   by @abhijeetjawale1 in #1028

17
Resolved   Bug 1027 : Design System > Charts >Bubble Charts >Click on Outline   to the preview & enable measures show error by @abhijeetjawale1 in #1034

18
Completed   Task 592 : Design System > Implement different types of Avtaars by @abhijeetjawale1 in #1030

19
Resolved   Bug 690 : Design System > Components > Data Table > Add new   component for Action by @abhijeetjawale1 in #1015

20
Resolved   Bug 894 : Component > Visual Setting > default > mobile view (small   & large) footer overlapping issue & other changes by @DeepashriDatar in #1035

21
Resolved   Bug 898 : Design System > Components > Claim Type & Language >   Default > After submission dropdown field does not clear & some label   changes by @DeepashriDatar in #1020

22
Resolved   Bug 814 : Component > Product list > Product list with Inline price   > small mobile > Not able to see full image by @nitinsonawane123 in #1026

23
Resolved   Bug 1005 : Design System > Components> Claims > Default > Plus   button alignment issue by @nitinsonawane123 in #1022

24
Resolved   Bug 1029 : Components >Admin Dashboard > UI does not display proper.   by @nitinsonawane123 in #1031

25
Completed   Task 995 : Design System > Element > Add new element for header   by @poojagurav21 in #1007

26
Completed   Task 996 : Design System > Element > Enhancement in Divider by @poojagurav21 in #1006

27
Resolved   Bug 885 : Design System > Components > Payment Tenure > Default >   After submitting field not clear and data is not display in action by @prakashmhaske in #979

28
Resolved   Bug 991 : Design System > Components > Calendar > Small mobile view   text and alignment issue by @prakashmhaske in #1016

29
Completed   Task 850 : Design System > Element > Progress Bar > Enhancements in   style for Circular by @rohit9096 in #877

30
Completed   Task 1014 : Design System > Elements > Text changes in element name   by @rahulp34 in #1021

31
Completed   Task 902 : Design System > Element > Create new element Truncated Text   by @suchithravipin1991 in #942

32
Completed   Task 1013 : Design System > Element > Add New Story for Stepper with   checkbox by @rahulp34 in #1036

33
Completed   Task 786 : Design System > Elements > Enhancements in pagination   by @abhijeetjawale1 in #1043

34
Completed   Task 999 : Design System > Component > Card : Enhancement in card view   by @poojagurav21 in #1037

35
Completed   Task 796 : Design System > Elements > Enhancements in Review by @prakashmhaske in #937

36
Completed   Task 794 : Design System > Elements > Enhancements in breadcrumb   by @poojagurav21 in #968

37
Completed   Task 796 : Design System > Elements > Enhancements in Review by @poojagurav21 in #1045

38
Completed   Task 962 : Design System > Element > Create new element file uploader   with avatar by @rahulp34 in #1048

39
Merge   Development : Moving Changes from Development to Staging Branch by @hemalatagaikwad in #1057

Sr.No
PR
GitHub Link
Status
Remark
Dev
QA

1
Resolved   Bug 862 : Design System > Components > Alert Popup > Default >   Popup cancel delete button is not working by @DeepashriDatar in #983
Design   System > Components > Alert Popup > Default > Popup cancel delete   button is not working. · Issue #862 · Wai-Technologies/raaghu-react
PR Approved
Ready   For Prod
Deepashri
Rameshwar

2
Completed   Task 796 : Design System > Elements > Enhancements in Review by @poojagurav21 in #1045
Design   System > Elements > Enhancements in Review · Issue #796 ·   Wai-Technologies/raaghu-react
PR Approved
Reopen
Pooja
Rameshwar

3
Resolved   Bug 749 : Design System > Element > Alert : Alert issues by @nitinsonawane123 in #986
Design   System > Element > Alert : Alert issues · Raaghu Design System
Ready for QA
Reopen
Nitin
Rameshwar

4
Resolved   Bug 969 : Design System >Elements > Payment Card > Default >   Label and button alignment issue by @nitinsonawane123 in #980
Design   System >Elements > Payment Card > Default > Label and button   alignment issue. · Issue #969 · Wai-Technologies/raaghu-react
Ready for QA
Reopen
Nitin
Rameshwar

5
Resolved   Bug 810 : Component > Datatable > Action button on Left side > Not   able to see the 'Edit' option after hovering over the row below in the table   by @VenuKG in #985
Design   System > Version 8.3 > Component > Datatable > Action button on   Left side > Not able to see the 'Edit' option after hovering over the row   below in the table · Issue #810 · Wai-Technologies/raaghu-react
Ready for QA
Ready   For Prod
Venu
Rameshwar

6
Resolved   Bug 892 : Design System > Components > Testimonials > Default >   UI issues by @poojagurav21 in #955
Design   System > Components > Testimonials > Default > UI issues. · Issue   #892 · Wai-Technologies/raaghu-react
PR Approved
Ready   For Prod
Pooja
Rameshwar

7
Resolved   Bug 671 : Storybook > Component > Forms basic > Required message is   not display by @nitinsonawane123 in #993
Storybook   > Component > Forms basic > Required message is not display. · Issue   #671 · Wai-Technologies/raaghu-react
Ready for QA
Ready   For Prod
Nitin
Rameshwar

8
Completed   Task 742 : Badge minor issue & enhancement is completed by @suchithravipin1991 in #998
Design   System > Elements > Badge : Minor issues in Badge · Issue #752 ·   Wai-Technologies/raaghu-react
Ready for QA
Reopen
Abhijeet
Rameshwar

9
Resolved   Bug 752 : Design System > Badge Minor issue resolved by @suchithravipin1991 in #757
Design   System > Elements > Badge : Minor issues in Badge · Issue #752 ·   Wai-Technologies/raaghu-react
Ready for QA
Reopen
Abhijeet
Rameshwar

10
Completed   Task 1001 : Elements > Enhancement > Nav Tab : Enhancements in nav tab   > File Mover : Dynamic Icons > New Element > Button Grid by @DeepashriDatar in #1010
Design   System > Elements > Enhancement >Nav Tab : Enhancements in nav tab   > File Mover : Dynamic Icons > New Element > Button Grid · Issue   #1001 · Wai-Technologies/raaghu-react
PR Approved
Reopen
Deepashri
Rameshwar

11
Resolved   Bug 659 : Storybook > Components > Contact Us > Default >   Displaying multiple error messages at the one time by @nitinsonawane123 in #1004
Storybook   > Components > Contact Us > Default > Displaying multiple error   messages at the one time. · Issue #659 · Wai-Technologies/raaghu-react
Ready for QA
Ready   For Prod
Nitin
Rameshwar

12
Completed   Task 981 : Design-system > Create icon for custom images for RDS icon   by @rahulp34 in #1012
Design-system   > Create icon for custom images for RDS icon · Issue #981 ·   Wai-Technologies/raaghu-react
PR Approved
Ready   For Prod
Rahul
Rameshwar

13
Completed   Task 938 : Design system enhancement in checkbox as per new project flow   by @rahulp34 in #939
Design   System > Enhancement in checkbox as per new project flow · Issue #938 ·   Wai-Technologies/raaghu-react
PR Approved
Ready   For Prod
Rahul
Rameshwar

14
Resolved   Bug 789 : Design System > Elements > Scrollspy > Dark theme Go Top   button is not visible. by @abhijeetjawale1 in #1023
Design   System > Elements > Scrollspy > Dark theme Go Top button is not   visible. · Issue #789 · Wai-Technologies/raaghu-react
Ready for QA
Ready   For Prod
Abhijeet
Rameshwar

15
Resolved   Bug 807 : Design System > Charts > Polar Area Chart > Change theme   and size display error massage by @abhijeetjawale1 in #1025
Design   System > Charts > Polar Area Chart > Change theme and size display   error massage. · Issue #807 · Wai-Technologies/raaghu-react
Ready for QA
Reopen
Abhijeet
Rameshwar

16
Completed   Task 900 : Design System > Element > Create new element Time Picker   by @abhijeetjawale1 in #1028
Design   System > Element > Create new element Time Picker. · Issue #900 ·   Wai-Technologies/raaghu-react
Ready for QA
Ready   For Prod
Abhijeet
Rameshwar

17
Resolved   Bug 1027 : Design System > Charts >Bubble Charts >Click on Outline   to the preview & enable measures show error by @abhijeetjawale1 in #1034
Design   System > Charts >Bubble Charts >Click on Outline to the preview   & enable measures show error. · Issue #1027 ·   Wai-Technologies/raaghu-react
Ready for QA
Ready   For Prod
Abhijeet
Rameshwar

18
Completed   Task 592 : Design System > Implement different types of Avtaars by @abhijeetjawale1 in #1030
Design   System > Implement different types of Avtaars · Issue #592 ·   Wai-Technologies/raaghu-react
Ready for QA
Reopen
Abhijeet
Rameshwar

19
Resolved   Bug 690 : Design System > Components > Data Table > Add new   component for Action by @abhijeetjawale1 in #1015
Design   System > Components > Data Table > Add new component for Action ·   Issue #690 · Wai-Technologies/raaghu-react
Ready for QA
Ready   For Prod
Abhijeet
Rameshwar

20
Resolved   Bug 894 : Component > Visual Setting > default > mobile view (small   & large) footer overlapping issue & other changes by @DeepashriDatar in #1035
Design   System > Components > Visual Setting> Default > Small large   mobile Subheader Footer overlap. · Issue #894 · Wai-Technologies/raaghu-react
PR Approved
Reopen
Deepashri
Rameshwar

21
Resolved   Bug 898 : Design System > Components > Claim Type & Language >   Default > After submission dropdown field does not clear & some label   changes by @DeepashriDatar in #1020
Design   System > Components > Claim Type > Default >After submitting   field not clear. · Issue #898 · Wai-Technologies/raaghu-react
PR Approved
Ready   For Prod
Deepashri
Rameshwar

22
Resolved   Bug 814 : Component > Product list > Product list with Inline price   > small mobile > Not able to see full image by @nitinsonawane123 in #1026
Design   System > Version 8.3 > Component > Product list > Product list   with Inline price > small mobile > Not able to see full image · Issue   #814 · Wai-Technologies/raaghu-react
Ready for QA
Ready   For Prod
Nitin
Rameshwar

23
Resolved   Bug 1005 : Design System > Components> Claims > Default > Plus   button alignment issue by @nitinsonawane123 in #1022
Design   System > Components> Claims > Default > Plus button alignment   issue. · Issue #1005 · Wai-Technologies/raaghu-react
Ready for QA
Reopen
Nitin
Rameshwar

24
Resolved   Bug 1029 : Components >Admin Dashboard > UI does not display proper.   by @nitinsonawane123 in #1031
Design   System > Components >Admin Dashboard > UI does not display proper. ·   Issue #1029 · Wai-Technologies/raaghu-react
Ready for QA
Ready   For Prod
Nitin
Rameshwar

25
Completed   Task 995 : Design System > Element > Add new element for header   by @poojagurav21 in #1007
Design   System > Element > Add new element for header · Issue #995 ·   Wai-Technologies/raaghu-react
PR Approved
Ready   For Prod
Pooja
Rameshwar

26
Completed   Task 996 : Design System > Element > Enhancement in Divider by @poojagurav21 in #1006
Design   System > Element > Enhancement in Divider · Issue #996 ·   Wai-Technologies/raaghu-react
PR Approved
Ready   For Prod
Pooja
Rameshwar

27
Resolved   Bug 885 : Design System > Components > Payment Tenure > Default >   After submitting field not clear and data is not display in action by @prakashmhaske in #979
Design   System > Components > Payment Tenure > Default > After submitting   field not clear and data is not display in action. · Issue #885 ·   Wai-Technologies/raaghu-react
PR Approved
Reopen
Prakash
Rameshwar

28
Resolved   Bug 991 : Design System > Components > Calendar > Small mobile view   text and alignment issue by @prakashmhaske in #1016
Design   System > Components > Calendar > Small mobile view text and   alignment issue. · Issue #991 · Wai-Technologies/raaghu-react
PR Approved
Reopen
Prakash
Rameshwar

29
Completed   Task 850 : Design System > Element > Progress Bar > Enhancements in   style for Circular by @rohit9096 in #877
Design   System > Element > Progress Bar > Enhancements in style for Circular   · Issue #850 · Wai-Technologies/raaghu-react
PR Approved
Ready   For Prod
Rahul
Rameshwar

30
Completed   Task 1014 : Design System > Elements > Text changes in element name   by @rahulp34 in #1021
Design   System > Elements > Text changes in element name · Issue #1014 ·   Wai-Technologies/raaghu-react
PR Approved
Reopen
Rahul
Rameshwar

31
Completed   Task 902 : Design System > Element > Create new element Truncated Text   by @suchithravipin1991 in #942
Design   System > Element > Create new element Truncated Text. · Issue #902 ·   Wai-Technologies/raaghu-react
Ready for QA
Reopen
Abhijeet
Rameshwar

32
Completed   Task 1013 : Design System > Element > Add New Story for Stepper with   checkbox by @rahulp34 in #1036
Design   System > Element > Add New Story for Stepper with checkbox · Issue   #1013 · Wai-Technologies/raaghu-react
PR Approved
Ready   For Prod
Rahul
Rameshwar

33
Completed   Task 786 : Design System > Elements > Enhancements in pagination   by @abhijeetjawale1 in #1043
Design   System > Elements > Enhancements in pagination · Issue #786 ·   Wai-Technologies/raaghu-react
Ready for QA
Reopen
Abhijeet
Rameshwar

34
Completed   Task 999 : Design System > Component > Card : Enhancement in card view   by @poojagurav21 in #1037
Design   System > Component > Card : Enhancement in card view · Issue #999 ·   Wai-Technologies/raaghu-react
PR Approved
Ready   For Prod
Pooja
Rameshwar

35
Completed   Task 796 : Design System > Elements > Enhancements in Review by @prakashmhaske in #937
Design   System > Elements > Enhancements in Review · Issue #796 ·   Wai-Technologies/raaghu-react
PR Approved
Reopen
Pooja
Rameshwar

36
Completed   Task 794 : Design System > Elements > Enhancements in breadcrumb   by @poojagurav21 in #968
Design   System > Elements > Enhancements in breadcrumb · Issue #794 ·   Wai-Technologies/raaghu-react
PR Approved
Ready   For Prod
Pooja
Rameshwar

37
Completed   Task 777 : Design System > Elements > Enhancements in file uploader   by @abhijeetjawale1 in #957
Design   System > Elements > Enhancements in file uploader · Issue #777 ·   Wai-Technologies/raaghu-react
Ready for QA
Done
Abhijeet
Rameshwar

38
Completed   Task 962 : Design System > Element > Create new element file uploader   with avatar by @rahulp34 in #1048
Design   System > Element > Create new element file uploader with avatar · Issue   #962 · Wai-Technologies/raaghu-react
PR Approved
Reopen
Rahul
Rameshwar

Ready for Prod - 21
Reopen - 17


truncate thread comment to max size allowed

resolves #89
This should avoid the error observed in #89.
A secondary problem
The thread-comments text is the same string used in step-summary text. But step-summary is not limited to a certain number of characters because it is written to a file. Therefore, if I truncate the comment's text when it is created in make_comment(), then the step-summary text will show the same lack of data, even though it isn't limited to 65535 characters.
As an alternative, I've chosen to just truncate the payload["body"] when posting a thread-comment using the REST API call. However, thread-comments may become malformed markdown syntax if they are longer than 65535 characters.
For example:
A very long comment body that exceeds 65535 characters in the next line.

</details>

could become malformed like so
A very long comment body that exceeds 65535 characters in the next line.

</det

However, thread-comments may become malformed markdown syntax if they are longer than 65535 characters.

Can this be solved by truncating characters less than 65535?

Thread-comments may become malformed because I'm truncating text to only 65535 characters.
It would be solved by making the comment twice, once for step-summary (with no length limit) and once for thread-comments (with length limit). But the API isn't currently designed to call make_comment() twice (which can be costly for large sets of files). Truncating the text is just easier/quicker for now. And implementing a length limit isn't a simple patch to make_comment().

superceded by #91


Finished SearchBar Component and Filter Repositories, issue #191

ℹ Repository information
The repository has:

[ ] At least three issues with the good first issue, or other labels specified in config.json (see labels and the end).
Link:
[ ] At least 10 contributors.
[ ] At least 1000 stars.
[ ] Detailed setup instructions for the project.
Link:
[x] CONTRIBUTING.md
[ ] Actively maintained (last updated less than 1 months ago).

Hey @lucavallin, kindly check the recent PR that I have made.


[v2.9] Revert changes to hosted providers gke and eks clusterconfigs

Cherry-pick of PR https://github.com/rancher/shepherd/pull/289 for release/v2.9 branch.

Do we need a v2.8 back port?

No Israel, code is already there.
Thanks for pointing it.


ADAT and MDAT in FileA

Transferring this issue from the private repo. I'm not sure that it's been resolved yet. Have we differentiated between DOY and DAP in all FileAs?
from @palderman :
I'm going through some final (I hope) checking for the DSSAT R package I've put together and about to start writing up. Anyway, I've been noticing that a lot of the A files (files A?) that are in the DSSAT CSM repo have only 3-digit values in the columns for MDAT and ADAT. For example:
Barley/IEBR8201.BAA
Barley/MTBO7701.BAA
Canola/USON0801.CNA
Canola/USOT0801.CNA
I'm thinking that people have mislabeled those columns (should be ADAP or MDAP?), but I wanted to check to be sure I haven't missed something.
Some additional examples:
Chickpea/ITBW9205.CHA
Chickpea/ITBW9306.CHA
For these examples, it seems that the ADAT values might be simply day of year? In any case, there seems to be some problem.
from @GerritHoogenboom
Yes, that's correct. Currently FileA is read by the model only and there are smarts to associate the Year with the DOY value.

Hi @palderman
I checked the subroutines in the model and the column names based on the source code.
If the FileA has ADAT and MDAT, the subroutine (usually OPHARV.for) will associate the name of the column with what has hard-coded.
Please see the subroutine MZ_OPHARV for Maize:
`!-----------------------------------------------------------------------
ACOUNT = 22  !Number of FILEA headings.
!     Headings in FILEA for Measured data
DATA OLAB /
&    'ADAT  ',     !1  DFLR
&    'PD1T  ',     !2  IFPD
&    'PDFT  ',     !3  IFSD
&    'MDAT  ',     !4  DMAT
&    'HWAM  ',     !5  XGWT
&    'PWAM  ',     !6  XPDW
&    'H#AM  ',     !7  XNOGR
&    'HWUM  ',     !8  XGWU
&    'H#UM  ',     !9  XNOGU
&    'CWAM  ',     !10 XCWT
!         08/11/2005 CHP
!         Change BWAH to BWAM -- by-product produced to maturity, but
!           not necessarily removed from field
!     &    'BWAH',     !11 XSWT
&    'BWAM  ',     !11 XSWT
 &    'LAIX  ',     !12 XLAM
 &    'HIAM  ',     !13 XHIN
 &    'THAM  ',     !14 XTHR
 &    'GNAM  ',     !15 XNGR
 &    'CNAM  ',     !16 XNTP
 &    'SNAM  ',     !17 XNST
 &    'GN%M  ',     !18 XNPS
 &    'CWAA  ',     !19 XCWAA
 &    'CNAA  ',     !20 XCNAA
 &    'L#SM  ',     !21 XLFNO
 &    'EDAT  ',     !22 Emergence date
 &    18*'      '/

`
These lines of code show the hard-coded structure used to associate the column names in the FileX with the output file.
Conclusion is that there is no error or mislabeled columns. The variables match what is inside the Fortran code.
Also, confirming what Dr. Hoogenboom mentioned : "Yes, that's correct. Currently FileA is read by the model only and there are smarts to associate the Year with the DOY value."
Thank you so much,
Fabio Oliveira


CircleCI: Don't try to push docker images in PRs from forks

The deploy task in CircleCI fails in PRs opened from forks. The reason is that this task tries to push docker images to our registry and the docker credentials are not available in PRs from forks.
This PR solves the issue by skipping the push instruction when the credentials are not set.

:+1:


stm32-rs: 0.14 -> 0.15

AES tests are timing out in CI because the AES peripheral clock is not enabled, see https://github.com/rust-embedded/svd2rust/issues/620


Fix row headers on Footnotes style guidance

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/contributing/style-guide-and-content-model/style-guide#footnotes
What part(s) of the article would you like to see updated?
The first column of the example table in the Footnotes section should be row headers but it's missing the necessary markup, so they render as data.
Additional information
I'll happily open a PR 💜

@streats Annie!! ✨ 😄 So good to hear from you! You or anyone else is welcome to open a PR with this fix 💛 🤓


Show Boxes view on creating new document

Select Objects tab and either create new document or open an existing document that contains no boxes. You see a grey rectangle:

Inselect should show Boxes tab when opening a new document


Linux: make setTitleBarStyle() GTK/HDY/CSD/SSD compatible

When it comes to hiding the window title bar, there are a few cases to consider.

The default Flutter app template defaults to a server-side decorated window title on non-GNOME X11 desktops.
Any desktop running on Wayland, and GNOME on X11, default to a client-side decorated GtkHeaderBar.
Furthermore, the handy_window package, which is popular in Flutter-based Ubuntu apps, provides a more modern-looking HdyWindow with rounded bottom corners and the header bar replaced by HdyHeaderBar.

This PR ensures that setTitleBarStyle() works in all these three cases on Linux.

GTK & SSD
gtk_ssd.webm

GTK & CSD
gtk_csd.webm

HDY & SSD
hdy_ssd.webm

HDY & CSD
hdy_csd.webm

LGTM

@lijy91 any chance to have a new version published?


TSX files not loading in WASM

The current approach for loading TSX files relies on futures_lite which doesn't work in WASM builds.
We need a new approach for loading these assets in WASM

For anyone who encounters this, the workaround I used was to embed the tilesets in the tilemaps in Tiled.
There are two ways to do this:

When creating a new tileset there is a checkbox on the right saying "Embed in map"
OR, when editing a map, in the tileset pane at the bottom right, see the buttons along the bottom. The second button from the left says "Embed". If you click this, it will embed the tileset into the map. Make sure to only use the tiles from the embedded set.

This embeds the tileset info into the TMX file rather than just referencing a TSX file that contains the same info. The actual tile images are still separate regardless. But it just means Bevy doesn't need to load the TSX file separately, which is where the issue occurs.
It's related to the fact that the Tiled hook for fetching the TSX file is sync while the Bevy way to fetch asset data is async. So it needs to call an async method from a sync method, and currently it does this by using futures_lite. That works on most platforms but not WASM.

Here is the issue in rs-tiled for async loading, which when closed should make closing this issue trivial: https://github.com/mapeditor/rs-tiled/issues/304

Hi,
I believe I am having the same problem. When I used the this plugin, and attempt to serve my project with Trunk the wasm seems to fail and I get:
Uncaught TypeError: The specifier “env” was a bare specifier, but was not remapped to anything. Relative module specifiers must start with “./”, “../” or “/”. bevy_game-39230fd36e2500b.js:1:30

After searching around I found your (@stevepryde) post here and that you managed to get it working on your project dizzy-ducks, and successfully export a working wasm build to itchio.
But when I cloned the dizzy ducks repo and tried to serve it locally using Trunk, I get the same issue:
Uncaught TypeError: The specifier “env” was a bare specifier, but was not remapped to anything. Relative module specifiers must start with “./”, “../” or “/”. dizzy-ducklings-46bff8eb8e30afb.js:1:30

Did you have the same issue, or is it a problem with my local dev environment? If so, how did you get a web build working for itchio/how did you test your web build locally?
Thank you in advance, and thank you for everything you have posted so far!

Hi,
I believe I am having the same problem. When I used this plugin, and attempt to serve my project with Trunk the wasm seems to fail and I get:
Uncaught TypeError: The specifier “env” was a bare specifier, but was not remapped to anything. Relative module specifiers must start with “./”, “../” or “/”. bevy_game-39230fd36e2500b.js:1:30

After searching around I found your (@stevepryde) post here and that you managed to get it working on your project dizzy-ducks, and successfully exported a working wasm build to itchio.
But when I cloned the dizzy ducks repo and tried to serve it locally using Trunk, I get the same issue:
Uncaught TypeError: The specifier “env” was a bare specifier, but was not remapped to anything. Relative module specifiers must start with “./”, “../” or “/”. dizzy-ducklings-46bff8eb8e30afb.js:1:30

Did you have the same issue, or is it a problem with my local dev environment? If so, how did you get a web build working for itchio/how did you test your web build locally?
Thank you in advance, and thank you for everything you have posted so far!

So turns the ZSTD dependency of rs-tiled, even though it was supposed to be compiled without that feature? It might be a bug with WASM bindgen or something. As a quick fix I just forked rs-tiled, removed the ZSTD dependency, then forked bevy-ecs-tiled and had it depend on that modified rs-tiled repo.


⚠ SolarOscp has degraded performance

In e9f7b53, SolarOscp ($SOLAROSCP_URL) experienced degraded performance:

HTTP code: 200
Response time: 311 ms

Resolved: SolarOscp performance has improved in 57f3e8c after 9 minutes.


Improve check-new-commit job

Build nightly when the latest commit is a pull request

LGTM :+1:
Merged.


Improve performance of clone

Instead of creating copy function on each _clone call, create it once.

I have unintentionally discovered that ramda's clone noticeably slower than the one from lodash. https://jsperf.com/region-clone-original/
One simple thing to improve in current clone implementation is to create copy function once, not every time _clone is called.
Нere is the same benchmark as above, but with ramda built from code of this PR: https://jsperf.com/regions-clone/

i see how your implementation should be an improvement, but I don't see any actual difference when I run the benches on the two versions. Testing in Chrome 58.0.3029 / Mac OS X 10.11.6

I ran benchmark in chrome-based browser and got theese numbers:
https://yadi.sk/i/yl_ZfXp23JzY7Q and https://yadi.sk/i/wVmsvJg13JzY8q
However, in Chrome 58.0.3029 I also can't see any difference.
Maybe it's a bug in Yandex.Browser or maybe newer version of js engine became smart enough to optimize this case.


Feature pebble game algorithm

This adds all features to support the pebble game algorithm that is necessary for the 2d combinatorial rigidity.
I added a new class directed_graph, that supports the directed graph structure necessary for the pebble game algorithm. I connected the relevant functions of Graph to the directed_graph class.
Some unit tests are added for both classes.
This is not necessarily a complete implementation of every potential of the pebble game algorithm, but a first - simple - approach for it, that can be improved later down the line. I'm not even 100% sure on the O(|V|^2) nature of this implementation, since that depends on the internal implementations of python.
But I believe that this is a usable implementation that can be a good basis of further development.

Thanks a lot @mihalykoandras !! I took the liberty to make a couple of minimal changes to that the code would pass the flake8 check. Is it ok to comment out the two print statements in the is_rigid method of Graph so that the tests will not fail?

Thanks for the flake fix. I removed the unnecessary print() statements.

Thanks for the flake fix. I removed the unnecessary print() statements.

Thanks a lot!

Would it be ok to transform the comments to the methods at the end of directed_graph.py into docstrings? I can take care of that if you agree.

I updated the docstrings. While I believe there are still some unit tests that I'd need to add, I will move it to ready state from draft.


ceph-salt can no longer bootstrap pacific as of ceph commit 5c9227bbdf987365ae90433ac4e501e1a88b7aca

As of https://github.com/ceph/ceph/commit/5c9227bbdf98 ceph-salt can no longer bootstrap pacific clusters:
    master: [2021-11-08 09:44:23.138464] [master.pacific-m] Finished with failures
    master: Failure in minion: master.pacific-mini.test
    master: __id__: add host to ceph orch
    master: __run_num__: 104
    master: __sls__: ceph-salt.apply.cephorch
    master: changes: {}
    master: comment: "Warning: Permanently added 'master.pacific-mini.test' (ECDSA) to the list\
    master:   \ of known hosts.\r\nError EINVAL: Can not automatically resolve ip address of host\
    master:   \ where active mgr is running. Please explicitly provide the address."
    master: duration: 748.424
    master: name: add host to ceph orch
    master: result: false
    master: start_time: '09:44:22.328683'
    master: state: ceph_orch_|-add host to ceph orch_|-add host to ceph orch_|-add_host
    master: Finished execution of ceph-salt formula

ANALYSIS:
The relevant yaml is:
{{ macros.begin_stage('Add host to ceph orchestrator') }}
add host to ceph orch:
  ceph_orch.add_host:
    - host: {{ my_hostname }}
    - is_admin: {{ is_admin }}
    - failhard: True
{{ macros.end_stage('Add host to ceph orchestrator') }}

which triggers the following Salt State code:
and my_hostname is getting populated by this line:
{% set my_hostname = salt['ceph_salt.hostname']() %}

which in turns triggers the following function:
def hostname():
    return socket.gethostname()

All this seems to mean that the hostname returned by socket.gethostname() is passed to the following function, add_host:
def add_host(name, host, is_admin=False):
    """
    Requires the following grains to be set:
      - ceph-salt:execution:admin_host
    """
    ret = {'name': name, 'changes': {}, 'comment': '', 'result': False}
    admin_host = __salt__['grains.get']('ceph-salt:execution:admin_host')
    cmd_ret = __salt__['ceph_salt.ssh'](
                       admin_host,
                       "sudo ceph orch host add {}{}".format(
                           host,
                           ' --labels _admin' if is_admin else '',
                        ),
                       attempts=10)
    if cmd_ret['retcode'] == 0:
        ret['result'] = True
    else:
        ret['comment'] = cmd_ret.get('stderr')
    return ret

Now, when I try socket.gethostname() in the sesdev environment, it returns the short hostname (master). And it seems that cephadm is expecting to get the short hostname here. But I couldn't find any log message to confirm that ceph-salt is really sending the short hostname.

The commit https://github.com/ceph/ceph/commit/5c9227bbdf98 comes originally from here - https://github.com/ceph/ceph/pull/42772 - which was added to fix https://tracker.ceph.com/issues/51667
The description of that PR says:
force users to use set-addr or label add/rm to modify host
this prevents labels being removed if a host is readded
or addr being set to 127.0.... if readding host active mgr is on

which is rather cryptic, but I did confirm that ceph-salt is not issuing any ceph orch host set-addr command. Maybe it should be?
What's weird is that the error is being triggered when the host is first being added. The PR description seems to indicate it was intended to fix a bug in subsequent host modification.

cc @Daniel-Pivonka

From what I can see, the linked PR includes a check that requires explicitly providing an address when calling "ceph orch host add" for the host the active mgr is running on. I think this was to prevent issues where the active mgr, when trying to resolve its own ip, would resolve to a loopback address rather than a proper ip. During cephadm bootstrap this typically isn't an issue because we explicitly pass the --mon-ip arg as the address for the bootstrap host (where the active mgr is at the time). If ceph-salt is doing things differently and just calling "ceph orch host add" without an explicit ip  addr for the bootstrap host then it would trigger this. Perhaps that check is a bit too severe and we should only throw errors if the address actually resolves to a loopback address?

@sebastian-philipp This is happening post-bootstrap, when ceph-salt tries to add the cluster hosts to the orchestrator.

Hm, this thing is: we should not make this a requirement, as this is often just not necessary, cause we can deduce the IP of many hosts properly anyway.

Yeah, I think many will be surprised when they this this error, especially since the error message:

does not make clear why mgr/cephadm thinks the IP address cannot be determined
does not say what the user should do to make the command succeed

At the very least it could say something like: "re-run the command providing the host's IP address as a second argument".

This error message will only appear when trying to readd the host that the active mgr is running on. we do not want to have the active mgr try to resolve its own ip as there is some weirdness with the /etc/hosts file inside containers and can result in the ip resolving to <IP_ADDRESS>.1 which is not correct.
Im not sure we should be explaining the weirdness of the container /etc/host file in this error message as that would be a long wordy error message.
and the error does say the user needs to provide an ip address to make this command succeed.
the error message needs to be generic enough that its applicable to both adding hosts via cli or yml spec so it cant say explicitly say add the ip to the second argument.
if ceph-salt is readding the host the active mgr is running it need to explicitly provide the ip address


Issue with HighSierra 10.13.4

Julian, The program is not working for 10.13.4.
It is not able to load the kext file. I've tried the file provided earlier but still it asks for the location of the file, which I am not able to select.
Any solution for this ?

I've tried but still getting error that file not found and even not able to select it.
Suggestion : Include this kext file with new version may be 0.6.1.
Check if file exist, then just run patch otherwise put the file in extensions before running patch.
It'll be easier for others too.

Nice suggestion, thanks

Resetting the SMC helped me get 10.13.4 in order

Hi Julian, I just ran your patch on my 2010 MBP 2.4GHz i5 and it told me that is successfully installed the patch. However, shortly after the machine did another random shutdown. I might also mention some background:  that I had  previously replaced the cap in the GPU rail, actually twice now. It seemed to work well after the first replacement (with a cap I got from Louis Rossmann) until a few weeks later, then crash. So I doubted my solder job , installed another new cap. Again , good for a while on a fresh El Capitan install. But when I put the original SSD ( belonging to my friend for whom I am trying to fix this) the shutdown reoccurred.  I have the panic report if that would help to shed light on this.


Update pipenv version to 2022.11.30

Not much to describe, this is just a singleliner with the latest stable pipenv version.

Hi! Thank you for the PR.
Updating to newer pipenv is on my list for next week - several releases since the old 2020.11.15 version we're on have had regressions, which is why it hasn't been updated sooner, but things are looking better with newer pipenv versions, so hopefully safer to try now.
The CI for this repo needs credentials to run, so I'll have to update this from a non-forked PR. (I'll also update the tests that need updating for this change at the same time.)


Plugin not working in the new versions of Compass

Hi Aaron and everyone,
I've successfully used rgbapng about half a year ago, but trying to apply it now to the projects with a new versions of Compass causes transparency to disappear even in the modern browsers.
Additionally it's not reporting about the generation of images to the console as it was doing before. There are no errors on the "require" and "import" of rgbapng in the respective files - seems that it's found.
I'm using Compass 0.11.5 at the moment. Is there a new configuration one should apply?
Thank you in advance.

Sorry, my fault, forgot that it's used as a mixin.