[all charts] Charts compatible with kubernetes 1.16

Replaces extensions/v1beta1 to policy/v1beta1 for PodSecurityPolicy.
sed -i 's@apiVersion: extensions/v1beta1@apiVersion: policy/v1beta1@' `find . -iregex ".*yaml\|.*yml" -exec awk '/kind:\s+PodSecurityPolicy/ {print FILENAME}' {} +`

Replaces extensions/v1beta1 to apps/v1 for Deployment, StatefulSet, ReplicaSet, DaemonSet
sed -i 's@apiVersion: extensions/v1beta1@apiVersion: apps/v1@' `find . -iregex ".*yaml\|.*yml" -exec awk '/kind:\s+(Deployment|StatefulSet|ReplicaSet|DaemonSet)/ {print FILENAME}' {} +`
sed -i 's@apiVersion: apps/v1beta2@apiVersion: apps/v1@' `find . -iregex ".*yaml\|.*yml" -exec awk '/kind:\s+(Deployment|StatefulSet|ReplicaSet|DaemonSet)/ {print FILENAME}' {} +`

Manually modified after searching for rest of files containing extensions/v1beta1 except Ingress objects obtained from: "egrep -rL 'kind:\s+Ingress' | xargs awk '/extensions\/v1beta1|apps\/v1beta2/ {print FILENAME}'"
Manually modified files:

modified:   stable/cluster-autoscaler/README.md
modified:   stable/cluster-autoscaler/values.yaml
modified:   stable/owncloud/README.md
modified:   stable/owncloud/values.yaml
modified:   stable/neo4j/templates/core-statefulset.yaml

Changes based on https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/

NetworkPolicy resources will no longer be served from extensions/v1beta1 by default in v1.16. Migrate to the networking.k8s.io/v1 API, available since v1.8. Existing persisted data can be retrieved/updated via the networking.k8s.io/v1 API.
PodSecurityPolicy resources will no longer be served from extensions/v1beta1 by default in v1.16. Migrate to the policy/v1beta1 API, available since v1.10. Existing persisted data can be retrieved/updated via the policy/v1beta1 API.
DaemonSet, Deployment, StatefulSet, and ReplicaSet resources will no longer be served from extensions/v1beta1, apps/v1beta1, or apps/v1beta2 by default in v1.16. Migrate to the apps/v1 API, available since v1.9. Existing persisted data can be retrieved/updated via the apps/v1 API.

What this PR does / why we need it:
Compatibility k8s v1.16
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[ ] Title of the PR starts with chart name (e.g. [stable/chart])

Updating everything in a single PR will not work because the CI needs to execute some test installing the chart in an individual way. Apart from that, the chart version present in the Chart.yaml should be bumped in every chart.
For example, charts contributed by Bitnami were already updated, see those already merged PRs. The approach should be similar, a single PR per chart with the changes and the version bumped  according to semver:

Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

/assign @mattfarina

Hello @carrodher
In case some of Charts will be long time aren't updated approach from PR can be used to move them forward.
Now CI test is passed.
Versions have been bumped.
while read -r a; do gawk -i inplace -F'.' '{sub(/version:\s+([0-9]{1,}\.)+[0-9]{1,}/,$1"."$2"."1+$3); print }' $a; done < list_of_paths_to_Chart.yaml_files
Some of Charts were failing in CI due to other issues. I've excluded them from PR.
List of failed charts:
 ✖ burrow => (version: "0.3.4", path: "incubator/burrow") > Error waiting for process: exit status 1
 ✖ istio => (version: "0.2.14-chart4", path: "incubator/istio") > Deprecated chart must not have maintainers
 ✖ puppet-forge => (version: "0.1.9", path: "incubator/puppet-forge") > Error validating maintainer 'Gerard Hickey': 404 Not Found
 ✖ aws-cluster-autoscaler => (version: "0.3.4", path: "stable/aws-cluster-autoscaler") > Error waiting for process: exit status 1
 ✖ dask-distributed => (version: "2.0.3", path: "stable/dask-distributed") > Error waiting for process: exit status 1
 ✖ linkerd => (version: "0.4.2", path: "stable/linkerd") > Error validating maintainer 'Vic Iglesias': 404 Not Found
 ✖ mission-control => (version: "0.4.4", path: "stable/mission-control") > Error waiting for process: exit status 1
 ✖ msoms => (version: "0.2.1", path: "stable/msoms") > Error validating maintainer 'Sambit Mishra': 404 Not Found
 ✖ namerd => (version: "0.2.1", path: "stable/namerd") > Error waiting for process: exit status 1
 ✖ nginx-lego => (version: "0.3.2", path: "stable/nginx-lego") > Error waiting for process: exit status 1
 ✖ sapho => (version: "0.2.3", path: "stable/sapho") > Error waiting for process: exit status 1
 ✖ sensu => (version: "0.2.4", path: "stable/sensu") > Error validating maintainer 'Shane Starcher': 404 Not Found

Updating everything in a single PR will not work because the CI needs to execute some test installing the chart in an individual way. Apart from that, the chart version present in the Chart.yaml should be bumped in every chart.
For example, charts contributed by Bitnami were already updated, see those already merged PRs. The approach should be similar, a single PR per chart with the changes and the version bumped according to semver:

Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

Updating everything in a single PR will not work because the CI needs to execute some test installing the chart in an individual way. Apart from that, the chart version present in the Chart.yaml should be bumped in every chart.
For example, charts contributed by Bitnami were already updated, see those already merged PRs. The approach should be similar, a single PR per chart with the changes and the version bumped according to semver:

Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

/hold

@uniuuu thank you for your contribution, but @carrodher and @Aisuko are correct. See the note at https://github.com/helm/charts/blob/master/CONTRIBUTING.md#how-to-contribute-to-an-existing-chart

In order to make testing and merging of PRs easier, please submit changes to multiple charts in separate PRs

If you want to break this into separate PRs that would be helpful. But closing this as it can not be merged as-is.


[WIP] Self-supervised learning example on Sleep Physionet

This PR introduces a new example, along with a new samplers module, to demonstrate how self-supervised learning can be used to learn representations in an unsupervised manner on raw EEG. The example implements the relative positioning task described in this preprint.
I've kept the number of recordings used in the example as well as the number of self-supervised samples and training epochs pretty low, so the example could run relatively quickly. The results are already interesting in that setting, although nicer results are obtained when more examples are included. For instance, with 40 recordings:

It looks like the failed CI is caused by differences in the recorded loss of other tests (test_cropped_decoding.py etc.), similar to what happened some time ago due to a change in skorch version. I'm not sure there's a link with the changes of this PR.
In any case, the rendered example can be found here!

It looks like the failed CI is caused by differences in the recorded loss of other tests (test_cropped_decoding.py etc.), similar to what happened some time ago due to a change in skorch version. I'm not sure there's a link with the changes of this PR.
In any case, the rendered example can be found here!

Hm does it not help to rebase from master? like I thought the problem is solved now.

In any case thanks for sharing self-supervised code, really appreciate it!

It looks like the failed CI is caused by differences in the recorded loss of other tests (test_cropped_decoding.py etc.), similar to what happened some time ago due to a change in skorch version. I'm not sure there's a link with the changes of this PR.
In any case, the rendered example can be found here!

Hm does it not help to rebase from master? like I thought the problem is solved now.

It looks like it's already based on master actually. I haven't looked yet but maybe there's been another skorch update in the meantime...?

It looks like the failed CI is caused by differences in the recorded loss of other tests (test_cropped_decoding.py etc.), similar to what happened some time ago due to a change in skorch version. I'm not sure there's a link with the changes of this PR.
In any case, the rendered example can be found here!

Hm does it not help to rebase from master? like I thought the problem is solved now.

It looks like it's already based on master actually. I haven't looked yet but maybe there's been another skorch update in the meantime...?

yeah since in sliwys PR the same problem, feel free to ignore. we will have to look at it separately again :(

rebasing on master should now make all tests run again @hubertjb. Seems some strange travis UI delays atm, but I received a mail that they pass.
Then you could also fix typo, and we can merge once decision about metadata vs get_metadata() is done (within next few days?).

what does yoda @agramfort https://github.com/agramfort think?

😂
+1 to avoid properties is they involved computations unless you cache the
results

@robintibor I just pushed the latest changes, including changing the metadata property to a get_metadata method, and making sure that the model that is used for visualization is the one that achieved the best valid loss.

I am asking myself if it is necessary or good that the dataset implements get_metadata. From what I see, all the information is accessible from the outside, dataset.description as well as dataset.windows.metadata so we could just move the code into the RecordingSampler and RelativePositionSampler. This would avoid all the problems regarding class properties or naming and could also avoid potential confusion about the term metadata and what it is. Any thoughts on this?

I am asking myself if it is necessary or good that the dataset implements get_metadata. From what I see, all the information is accessible from the outside, dataset.description as well as dataset.windows.metadata so we could just move the code into the RecordingSampler and RelativePositionSampler. This would avoid all the problems regarding class properties or naming and could also avoid potential confusion about the term metadata and what it is. Any thoughts on this?

Hm to me get_metadata seems still ok to me, like it makes sense to have in the class, since it uses a lot of the class members, and to me logically makes sense to be there... also does not introduce any additional changes outside the new function itself...

I am asking myself if it is necessary or good that the dataset implements get_metadata. From what I see, all the information is accessible from the outside, dataset.description as well as dataset.windows.metadata so we could just move the code into the RecordingSampler and RelativePositionSampler. This would avoid all the problems regarding class properties or naming and could also avoid potential confusion about the term metadata and what it is. Any thoughts on this?

Hm to me get_metadata seems still ok to me, like it makes sense to have in the class, since it uses a lot of the class members, and to me logically makes sense to be there... also does not introduce any additional changes outside the new function itself...

@gemeinl I think it makes sense to have BaseConcatDataset return a metadata dataframe directly as it's pretty much what we're already doing with the description attribute (the description attribute of the individual WindowsDatasets are also concatenated into a single dataframe, also called description). I think there are other scenarios in which it might be convenient to have access to this concatenated metadata DataFrame directly too, e.g., for splitting datasets, converting to a (X,y) dataset, sanity checking, etc. For that reason I would at least implement get_metadata outside of the Sampler objects so it can be easily reused down the line.

ok, will merge this!
Keep in mind:

If we agree on some specific data augmentation implementation
AND
this way of implementing augmentations can also very nicely cover the case here (I am aware this is not same as augmentation here)
AND
it is different from what you have done

We may want to adapt the code at that point.
But until then:
https://twitter.com/malonebarry/status/1325284260777955328 :+1: :100: :partying_face: :smiley:

🍾 🎉 🍺

Awesome, thanks @robintibor! :)
Yes, I agree, if this can be implemented with data augmentations it will be worth it to look into changing the implementation of this example. To keep in mind though, I think using a Sampler object is pretty natural and intuitive here, so this could be a reason to keep this implementation.


Conversion of specimen table to workbench import file

The specimen table is in itself not fully fit for import into Specify. Some kind of conversion needs to happen in order to make this happen.
We either:

Change the specimen table itself so it can be directly imported as-is
Add a conversion feature for creating export files ready for import

In either case analogies of the following columns need to be rendered:

[x] Perhaps recaption "multispecimen" as "containername"
[x] taxon name columns as "family", "genus", "species" and infraspecific taxa
[x] storage name columns as "institution" "site" "collection" and lower ranks like "box" and "shelf"
[x] Column "locality name" for linking "georegionname" to locality (will just mirror georegionname value)
[x] Column "agentfullname" as "cataloger first name" "cataloger middle" & "cataloger last name" (Covered by #290 )
[x] Add "publish" column to be mapped to "collectionobject.yesno1"
[x] Add flag that is mapped into field in taxon record when new taxon has been entered (indicated by empty taxonspid)
[x] Handle new taxa by parsing taxonfullname because taxonrankname is not set (assume subgeneric taxa)

Needs testing in workbench


Dataset subset assignments in doc

Added explanation of new feature (PR #5045) that allows assigning values to a subset of a dataset to the documentation.

Thanks @matzegoebel ! If you'd like to add a whatsnew, please feel free to in another PR

Thanks @matzegoebel ! If you'd like to add a whatsnew, please feel free to in another PR

there's already one for the new feature so the most that should be done is adding this PR to that entry (definitely optional, though).
Thanks again, @matzegoebel.


python311Packages.rye: 2.23.0 -> 2.24.0

Description of changes
Changelog: https://github.com/ray-project/ray/releases/tag/ray-2.24.0
cc @BillHuang2001
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 317838 run on aarch64-darwin 1

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

Result of nixpkgs-review pr 317838 run on aarch64-linux 1

Result of nixpkgs-review pr 317838 run on x86_64-linux 1

2 packages marked as broken and skipped:

python311Packages.vllm
python311Packages.vllm.dist

4 packages built:

python311Packages.kserve
python311Packages.kserve.dist
python311Packages.ray
python311Packages.ray.dist


scripts: Updates for arm64

@marineam bump -- we need this to be able to build arm64 images.

lgtm

Ah dam, sorry about that.


better baseline

goes with: https://github.com/UV-CDAT/uvcdat/pull/1658

@doutriaux1 how is better? Seems like default text has much larger background..

this is not my doing @aashish24 it's actually @chaosphere2112 that "fixed" this it takes the width of the longest colormap name

@doutriaux1 I see. so.. there are more entries in that drop down. sure, thanks. What else has changed?

@aashish24 lots has changed now :wink: first of all the "initial.attributes" will only save the user-defined graphic method, that fastens tihngs a lot, that meant "recording" what is loaded as default and not re-store that. Also there were some issues in loading "old format" .scr initial.attribute files. I discovered these while converting one from Michael Wehner.


Changed WebActivity and webhook activity auth to support both AKV and…

… Secrets
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

@erich-wang can you please review this PR. The changes in this are not breaking as the type change is to base class. Let me know if you need any other details.


fix: Adding graphQL with cache constrcut

Coverage Report

Totals

Statements:
95.43% ( 5132 / 5378 )

Methods:
91.16% ( 196 / 215 )

Coverage Report

Totals

Statements:
95.23% ( 5134 / 5391 )

Methods:
91.16% ( 196 / 215 )


Fix const validations

This fixes #620

NOTICE: pydantic is currently pushing towards V1 release,
see issue 576. Changes not required to release version 1
may be be delayed until after version 1 is released. If your PR is a bugfix for v0.32, please base off and target the v0.32.x branch.
Change Summary

Related issue number

Checklist

[X] Unit tests for the changes exist
[x] Tests pass on CI and coverage remains at 100%
[x] Documentation reflects the changes where applicable
[x] changes/<pull request or issue id>-<github username>.rst file added describing change
(see changes/README.md for details)

Not sure if you wan't this in master or 0.32 so I submitted both

does this also resolve #793?

does this also resolve #793?

No, unfortunately it doesn't, and I don't really have a clue how to fix it. However it might not be a big issue for us since we initialize the constant fields with json compatible dicts instead of submodel instances

does this also resolve #793?

No, unfortunately it doesn't, and I don't really have a clue how to fix it. However it might not be a big issue for us since we initialize the constant fields with json compatible dicts instead of submodel instances

Ok changed it up a bit more and now it should work for #793. At least in the most obvious cases

Hi @hmvp would be great if you could work on fixing this. I'm trying to get a beta for version 1 out the door asap and I want to include this.

Sure, I will try to get a fixed MR out today

Pushed an update


Special Flow Panel (with height) required by tutorial and templated p…

…erspectives. This is related with: https://issues.jboss.org/browse/UF-185. This panel used to live as default in our archetype

http://github.com/uberfire/uberfire/commit/c40a0cee2


beekeeper-studio: 3.6.2 -> 4.0.3, refactor

Description of changes
Updated Beekeeper Studio to 4.0.3, moved it to by-name, added mainProgram, added aarch64 version.
Someone has to check if aarch64 version works as currently I can't.

[x] Tested SQLite connection
[x] Tested PostgreSQL connection

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2954

Result of nixpkgs-review pr 269338 run on x86_64-linux 1

1 package built:

beekeeper-studio

Runs fine, LGTM. Thanks!


Feature/8 golang

Codecov Report

Merging #10 (590f7e2) into main (5fa1d16) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Current head 590f7e2 differs from pull request most recent head dc5fa6c. Consider uploading reports for the commit dc5fa6c to get more accurate results

@@            Coverage Diff            @@
##              main       #10   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         3
  Lines           95        91    -4
=========================================
- Hits            95        91    -4

Impacted Files
Coverage Δ

main.go
100.00% <100.00%> (ø)

task.go
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


UNK replacement

Does a good will feel like implementing this promising http://arxiv.org/pdf/1410.8206v4.pdf way to replace UNK using this code https://github.com/sebastien-j/LV_groundhog/blob/master/experiments/nmt/replace_UNK.py ?

@sebastien-j any chance you'll implement this here? :)

is there a chance that the .pkl and .npz files are compatible with groundhog ?

@vince62s Unfortunately, that is not going to be an easy job to do, and there's no plan for it.


LSTM Example has same val and test set

The validation data and test data in this example are the same. It's probably better to have separate val and test data.
Or maybe I misunderstand the purpose of validation data here, and it's just to see how the model improves on the test data. As long as you don't use the val results to select the best model, and as long as you don't train multiple models to look for the best model, then maybe it's OK?

Correct, you're OK as long as you don't optimize hyperparameters on it. This has been brought up before in #1753. Unfortunately, no common ground was reached and the examples remain a potential trap for inexperienced beginners.


evcc: 0.130.9 -> 0.130.12

https://github.com/evcc-io/evcc/releases/tag/0.130.12
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 343790 run on x86_64-linux 1

1 package blacklisted:

nixos-install-tools

1 package failed to build:

evcc

Care to share a log of your build failure?

Logs

Running phase: unpackPhase
unpacking source archive /nix/store/cdcna8090xkp6nhzmn5gzfbmqsaqycdw-source
source root is source
Running phase: patchPhase
Executing npmConfigHook
Configuring npm
Validating consistency between /build/source/package-lock.json and /nix/store/8iajacxaxrb3pjqv6zl4l289fj9kajq2-npm-deps/package-lock.json
Installing dependencies
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: undefined,
npm warn EBADENGINE   required: { npm: '>=10.0.0', node: '>=22.0.0' },
npm warn EBADENGINE   current: { node: 'v20.17.0', npm: '10.8.2' }
npm warn EBADENGINE }
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>Use @eslint/config-array instead
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Use your platform's native atob() and btoa() methods instead
npm warn deprecated<EMAIL_ADDRESS>Use @eslint/object-schema instead
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Use your platform's native DOMException instead
npm warn deprecated<EMAIL_ADDRESS>Please migrate to https://github.com/antfu/shikiji
added 753 packages, and audited 754 packages in 4s
169 packages are looking for funding
run npm fund for details
found 0 vulnerabilities
patching script interpreter paths in node_modules
<EMAIL_ADDRESS>interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
<EMAIL_ADDRESS>interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/eslint/bin/eslint.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
<EMAIL_ADDRESS>interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/rimraf/bin.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/markdown-it/bin/markdown-it.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/resolve/bin/resolve: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/json5/lib/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/acorn/bin/acorn: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/browserslist-to-esbuild/cli/index.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/browserslist/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/cssesc/bin/cssesc: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/esbuild/bin/esbuild: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/escodegen/bin/escodegen.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/escodegen/bin/esgenerate.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/eslint-config-prettier/bin/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/editorconfig/node_modules/semver/bin/semver.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/editorconfig/bin/editorconfig: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/eslint-plugin-vue/node_modules/semver/bin/semver.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/esprima/bin/esparse.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/esprima/bin/esvalidate.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/glob/dist/esm/bin.mjs: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/gray-matter/node_modules/js-yaml/bin/js-yaml.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/histoire/bin.mjs: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/is-docker/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/jiti/bin/jiti.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/js-beautify/js/src/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/js-beautify/js/lib/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/js-beautify/js/bin/css-beautify.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/js-beautify/js/bin/html-beautify.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/js-beautify/js/bin/js-beautify.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/js-yaml/bin/js-yaml.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/jsesc/bin/jsesc: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/nanoid/bin/nanoid.cjs: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/prettier/bin/prettier.cjs: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/rollup/dist/bin/rollup: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/nopt/bin/nopt.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/semver/bin/semver.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/open/xdg-open: interpreter directive changed from "#!/bin/sh" to "/nix/store/izpf49b74i15pcr9708s3xdwyqs4jxwl-bash-5.2p32/bin/sh"
node_modules/vite-node/vite-node.mjs: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/vite/bin/vite.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/wait-on/bin/wait-on: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/which/bin/node-which: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/why-is-node-running/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/playwright-core/lib/utilsBundleImpl/xdg-open: interpreter directive changed from "#!/bin/sh" to "/nix/store/izpf49b74i15pcr9708s3xdwyqs4jxwl-bash-5.2p32/bin/sh"
node_modules/playwright-core/bin/reinstall_chrome_beta_linux.sh: interpreter directive changed from "#!/usr/bin/env bash" to "/nix/store/izpf49b74i15pcr9708s3xdwyqs4jxwl-bash-5.2p32/bin/bash"
node_modules/playwright-core/bin/reinstall_chrome_beta_mac.sh: interpreter directive changed from "#!/usr/bin/env bash" to "/nix/store/izpf49b74i15pcr9708s3xdwyqs4jxwl-bash-5.2p32/bin/bash"
node_modules/playwright-core/bin/reinstall_chrome_stable_linux.sh: interpreter directive changed from "#!/usr/bin/env bash" to "/nix/store/izpf49b74i15pcr9708s3xdwyqs4jxwl-bash-5.2p32/bin/bash"
node_modules/playwright-core/bin/reinstall_chrome_stable_mac.sh: interpreter directive changed from "#!/usr/bin/env bash" to "/nix/store/izpf49b74i15pcr9708s3xdwyqs4jxwl-bash-5.2p32/bin/bash"
node_modules/playwright-core/bin/reinstall_msedge_beta_linux.sh: interpreter directive changed from "#!/usr/bin/env bash" to "/nix/store/izpf49b74i15pcr9708s3xdwyqs4jxwl-bash-5.2p32/bin/bash"
node_modules/playwright-core/bin/reinstall_msedge_beta_mac.sh: interpreter directive changed from "#!/usr/bin/env bash" to "/nix/store/izpf49b74i15pcr9708s3xdwyqs4jxwl-bash-5.2p32/bin/bash"
node_modules/playwright-core/bin/reinstall_msedge_dev_linux.sh: interpreter directive changed from "#!/usr/bin/env bash" to "/nix/store/izpf49b74i15pcr9708s3xdwyqs4jxwl-bash-5.2p32/bin/bash"
node_modules/playwright-core/bin/reinstall_msedge_dev_mac.sh: interpreter directive changed from "#!/usr/bin/env bash" to "/nix/store/izpf49b74i15pcr9708s3xdwyqs4jxwl-bash-5.2p32/bin/bash"
node_modules/playwright-core/bin/reinstall_msedge_stable_linux.sh: interpreter directive changed from "#!/usr/bin/env bash" to "/nix/store/izpf49b74i15pcr9708s3xdwyqs4jxwl-bash-5.2p32/bin/bash"
node_modules/playwright-core/bin/reinstall_msedge_stable_mac.sh: interpreter directive changed from "#!/usr/bin/env bash" to "/nix/store/izpf49b74i15pcr9708s3xdwyqs4jxwl-bash-5.2p32/bin/bash"
node_modules/playwright-core/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/regjsparser/node_modules/jsesc/bin/jsesc: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/regjsparser/bin/parser: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/typescript/bin/tsc: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/typescript/bin/tsserver: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/update-browserslist-db/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/rollup-plugin-visualizer/dist/bin/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/vue-eslint-parser/node_modules/semver/bin/semver.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/vitest/node_modules/vite-node/vite-node.mjs: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/vitest/vitest.mjs: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/terser/bin/terser: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/terser/bin/uglifyjs: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/tsconfig-paths/node_modules/json5/lib/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
node_modules/playwright/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
<EMAIL_ADDRESS>interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
<EMAIL_ADDRESS>interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/w78sh036dyn14f29w8za9ni9syrmwm3q-nodejs-20.17.0/bin/node"
rebuilt dependencies successfully
patching script interpreter paths in node_modules
Finished npmConfigHook
Running phase: updateAutotoolsGnuConfigScriptsPhase
Running phase: configurePhase
Running phase: buildPhase
npm run build

build
vite build

vite v5.4.5 building for production...
✓ 472 modules transformed.
../dist/assets/TopHeader-legacy-CpdQwkIF.js           3.50 kB │ gzip:   1.84 kB
../dist/assets/smoothscroll-legacy-CgPWaVMB.js        4.46 kB │ gzip:   1.67 kB
../dist/assets/Log-legacy-BByBQ7Of.js                11.34 kB │ gzip:   4.68 kB
../dist/assets/ChargingSessions-legacy-IN0V6rNW.js   21.05 kB │ gzip:   6.03 kB
../dist/assets/polyfills-legacy-DC-7tKGt.js          53.84 kB │ gzip:  21.28 kB
../dist/assets/Config-legacy-oDzy7_yq.js            117.46 kB │ gzip:  32.57 kB
../dist/assets/index-legacy-CVB1HV-q.js             822.43 kB │ gzip: 216.64 kB
(!) Some chunks are larger than 800 kB after minification. Consider:

Using dynamic import() to code-split the application
Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/configuration-options/#output-manualchunks
Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.
../dist/index.html                                 3.06 kB │ gzip:   1.22 kB
../dist/assets/Montserrat-Bold-Bsf7A8hH.woff2     86.80 kB
../dist/assets/Montserrat-Medium-BttyIOWL.woff2   87.04 kB
../dist/assets/TopHeader-BvJlCROq.css              0.07 kB │ gzip:   0.09 kB
../dist/assets/Log-DeG7ErH8.css                    0.95 kB │ gzip:   0.43 kB
../dist/assets/ChargingSessions-BiuCTtmI.css       1.17 kB │ gzip:   0.41 kB
../dist/assets/Config-D-lyMjZo.css                 4.24 kB │ gzip:   1.25 kB
../dist/assets/index-6ISEwPV8.css                262.55 kB │ gzip:  37.77 kB
../dist/assets/TopHeader-BuCa98Gd.js               3.25 kB │ gzip:   1.69 kB
../dist/assets/smoothscroll-DY25IEHY.js            4.53 kB │ gzip:   1.65 kB
../dist/assets/Log-YON3aZxb.js                    10.45 kB │ gzip:   4.31 kB
../dist/assets/ChargingSessions-BBZZSidR.js       19.90 kB │ gzip:   5.69 kB
../dist/assets/Config-i_DO59ks.js                115.41 kB │ gzip:  32.26 kB
../dist/assets/index-C5COYabp.js                 572.73 kB │ gzip: 186.42 kB
✓ built in 6.89s
Building subPackage .
Building subPackage ./api
Building subPackage ./api/globalconfig
Building subPackage ./api/proto/pb
Building subPackage ./api/store
Building subPackage ./charger
Building subPackage ./charger/connectiq
Building subPackage ./charger/daheimladen
Building subPackage ./charger/easee
Building subPackage ./charger/echarge
Building subPackage ./charger/echarge/ecb1
Building subPackage ./charger/echarge/salia
Building subPackage ./charger/evse
Building subPackage ./charger/go-e
Building subPackage ./charger/keba
Building subPackage ./charger/nrg/ble
Building subPackage ./charger/nrg/connect
Building subPackage ./charger/ocpp
Building subPackage ./charger/openevse
Building subPackage ./charger/openwb
Building subPackage ./charger/openwb/pro
Building subPackage ./charger/pcelectric
Building subPackage ./charger/smaevcharger
Building subPackage ./charger/warp
Building subPackage ./charger/zaptec
Building subPackage ./cmd
Building subPackage ./cmd/configure
Building subPackage ./cmd/detect
Building subPackage ./cmd/detect/tasks
Building subPackage ./cmd/ocpp
Building subPackage ./cmd/shutdown
Building subPackage ./cmd/soc
Building subPackage ./cmd/tools
Building subPackage ./core
Building subPackage ./core/circuit
Building subPackage ./core/coordinator
Building subPackage ./core/keys
Building subPackage ./core/loadpoint
Building subPackage ./core/planner
Building subPackage ./core/prioritizer
Building subPackage ./core/session
Building subPackage ./core/site
Building subPackage ./core/soc
Building subPackage ./core/vehicle
Building subPackage ./core/wrapper
Building subPackage ./hems
Building subPackage ./hems/eebus
Building subPackage ./hems/relay
Building subPackage ./hems/semp
Building subPackage ./meter
Building subPackage ./meter/bosch
Building subPackage ./meter/discovergy
Building subPackage ./meter/fritzdect
Building subPackage ./meter/goodwe
Building subPackage ./meter/homematic
Building subPackage ./meter/homewizard
Building subPackage ./meter/lgpcs
Building subPackage ./meter/mystrom
Building subPackage ./meter/obis
Building subPackage ./meter/shelly
Building subPackage ./meter/tapo
Building subPackage ./meter/tasmota
Building subPackage ./meter/tibber
Building subPackage ./meter/tplink
Building subPackage ./packaging
Building subPackage ./provider
Building subPackage ./provider/golang
Building subPackage ./provider/javascript
Building subPackage ./provider/mqtt
Building subPackage ./provider/pipeline
Building subPackage ./provider/sma
Building subPackage ./push
Building subPackage ./server
Building subPackage ./server/assets
Building subPackage ./server/db
Building subPackage ./server/db/settings
Building subPackage ./server/eebus
Building subPackage ./server/modbus
Building subPackage ./server/oauth2redirect
Building subPackage ./server/updater
Building subPackage ./tariff
Building subPackage ./tariff/amber
Building subPackage ./tariff/awattar
Building subPackage ./tariff/elering
Building subPackage ./tariff/energinet
Building subPackage ./tariff/entsoe
Building subPackage ./tariff/fixed
Building subPackage ./tariff/ngeso
Building subPackage ./tariff/octopus/graphql
Building subPackage ./tariff/octopus/rest
Building subPackage ./tariff/smartenergy
Building subPackage ./templates/definition
Building subPackage ./util
Building subPackage ./util/auth
Building subPackage ./util/cloud
Building subPackage ./util/config
Building subPackage ./util/encode
Building subPackage ./util/jq
Building subPackage ./util/locale
Building subPackage ./util/locale/internal
Building subPackage ./util/logstash
Building subPackage ./util/machine
Building subPackage ./util/modbus
Building subPackage ./util/oauth
Building subPackage ./util/pipe
Building subPackage ./util/registry
Building subPackage ./util/request
Building subPackage ./util/shortrfc3339
Building subPackage ./util/sponsor
Building subPackage ./util/telemetry
Building subPackage ./util/templates
Building subPackage ./util/templates/generate
Building subPackage ./util/test
Building subPackage ./util/transport
Building subPackage ./util/urlvalues
Building subPackage ./vehicle
Building subPackage ./vehicle/aiways
Building subPackage ./vehicle/audi
Building subPackage ./vehicle/audi/etron
Building subPackage ./vehicle/bluelink
Building subPackage ./vehicle/bmw
Building subPackage ./vehicle/fiat
Building subPackage ./vehicle/ford
Building subPackage ./vehicle/ford/autonomic
Building subPackage ./vehicle/ford/connect
Building subPackage ./vehicle/jlr
Building subPackage ./vehicle/mb
Building subPackage ./vehicle/mercedes
Building subPackage ./vehicle/mercedes/pb
Building subPackage ./vehicle/mercedes/pb/protos
Building subPackage ./vehicle/nissan
Building subPackage ./vehicle/niu
Building subPackage ./vehicle/ovms
Building subPackage ./vehicle/polestar
Building subPackage ./vehicle/porsche
Building subPackage ./vehicle/psa
Building subPackage ./vehicle/renault
Building subPackage ./vehicle/renault/gigya
Building subPackage ./vehicle/renault/kamereon
Building subPackage ./vehicle/renault/keys
Building subPackage ./vehicle/saic
Building subPackage ./vehicle/saic/requests
Building subPackage ./vehicle/seat
Building subPackage ./vehicle/seat/cupra
Building subPackage ./vehicle/skoda
Building subPackage ./vehicle/skoda/connect
Building subPackage ./vehicle/skoda/myskoda
Building subPackage ./vehicle/skoda/myskoda/service
Building subPackage ./vehicle/skoda/myskoda/tokenrefreshservice
Building subPackage ./vehicle/smart
Building subPackage ./vehicle/smart/hello
Building subPackage ./vehicle/tesla
Building subPackage ./vehicle/tronity
Building subPackage ./vehicle/vag
Building subPackage ./vehicle/vag/aazsproxy
Building subPackage ./vehicle/vag/cariad
Building subPackage ./vehicle/vag/idkproxy
Building subPackage ./vehicle/vag/loginapps
Building subPackage ./vehicle/vag/mbb
Building subPackage ./vehicle/vag/service
Building subPackage ./vehicle/vag/tokenrefreshservice
Building subPackage ./vehicle/vag/vwidentity
Building subPackage ./vehicle/volvo
Building subPackage ./vehicle/volvo/connected
Building subPackage ./vehicle/vw
Building subPackage ./vehicle/vw/id
Building subPackage ./vehicle/zero
buildPhase completed in 56 seconds
Running phase: checkPhase
ok      github.com/evcc-io/evcc/api     0.002s
[ocpp  ] WARN 2024/09/22 19:55:34 unknown charge point connected: test-3
[ocpp  ] WARN 2024/09/22 19:55:34 unknown charge point connected: test-1
[ocpp  ] WARN 2024/09/22 19:55:34 unknown charge point connected: test-2
[ocpp  ] WARN 2024/09/22 19:55:34 unknown charge point connected: test-4
panic: Log in goroutine after TestOcpp has completed: 2024-09-22 19:55:39 enqueued CALL [485651043, MeterValues]

goroutine 260 [running]:
testing.(*common).logDepth(0xc0009971e0, {0xc000af4a00, 0x3b}, 0x3)
/nix/store/mi0ybwsm6pmxzv9hsm6bcbqaq1pkf8wh-go-1.23.1/share/go/src/testing/testing.go:1029 +0x4c5
testing.(*common).log(...)
/nix/store/mi0ybwsm6pmxzv9hsm6bcbqaq1pkf8wh-go-1.23.1/share/go/src/testing/testing.go:1011
testing.(*common).Log(0xc0009971e0, {0xc000b43bd0?, 0x348f1e0?, 0x1e7e3a3?})
/nix/store/mi0ybwsm6pmxzv9hsm6bcbqaq1pkf8wh-go-1.23.1/share/go/src/testing/testing.go:1052 +0x4a
github.com/evcc-io/evcc/charger.print(0xc0009971e0, {0xc000ae4870, 0x26})
/build/source/charger/ocpp_test_logger.go:14 +0x92
github.com/evcc-io/evcc/charger.(*ocppLogger).Debugf(0xc000818000, {0x1e870f2?, 0xc000011000?}, {0xc000615440?, 0x100?, 0x1abfcc0?})
/build/source/charger/ocpp_test_logger.go:19 +0x47
github.com/lorenzodonini/ocpp-go/ocppj.(*Client).SendRequest(0xc0007efe60, {0x21d9580, 0xc000aeaf00})
/build/source/vendor/github.com/lorenzodonini/ocpp-go/ocppj/client.go:206 +0x27c
github.com/lorenzodonini/ocpp-go/ocpp1.6.(*chargePoint).SendRequest.func1()
/build/source/vendor/github.com/lorenzodonini/ocpp-go/ocpp1.6/charge_point.go:222 +0x25
github.com/lorenzodonini/ocpp-go/internal/callbackqueue.(*CallbackQueue).TryQueue(0xc000c12128, {0x1e508c6, 0x4}, 0xc000b43e00, 0xc000ca46c0)
/build/source/vendor/github.com/lorenzodonini/ocpp-go/internal/callbackqueue/callbackqueue.go:26 +0x157
github.com/lorenzodonini/ocpp-go/ocpp1.6.(*chargePoint).SendRequest(0xc000c120b0, {0x21d9580, 0xc000aeaf00})
/build/source/vendor/github.com/lorenzodonini/ocpp-go/ocpp1.6/charge_point.go:224 +0x194
github.com/lorenzodonini/ocpp-go/ocpp1.6.(*chargePoint).MeterValues(0xc000c120b0, 0x1, {0xc0006153e0, 0x1, 0x1}, {0x0, 0x0, 0x0?})
/build/source/vendor/github.com/lorenzodonini/ocpp-go/ocpp1.6/charge_point.go:111 +0xc7
github.com/evcc-io/evcc/charger.(*ocppTestSuite).handleTrigger(0xc0009d6960, {0x22179a8, 0xc000c120b0}, 0x1, {0xc000c04150?, 0x578e40?})
/build/source/charger/ocpp_test.go:94 +0x1f3
github.com/evcc-io/evcc/charger.(*ocppTestSuite).startChargePoint.func1()
/build/source/charger/ocpp_test.go:71 +0x73
created by github.com/evcc-io/evcc/charger.(*ocppTestSuite).startChargePoint in goroutine 259
/build/source/charger/ocpp_test.go:69 +0x538
panic: Log in goroutine after TestOcpp has completed: 2024-09-22 19:55:39 sent JSON message to test-4: [3,"117107786",{}]
goroutine 338 [running]:
testing.(*common).logDepth(0xc0009971e0, {0xc000942410, 0x44}, 0x3)
/nix/store/mi0ybwsm6pmxzv9hsm6bcbqaq1pkf8wh-go-1.23.1/share/go/src/testing/testing.go:1029 +0x4c5
testing.(*common).log(...)
/nix/store/mi0ybwsm6pmxzv9hsm6bcbqaq1pkf8wh-go-1.23.1/share/go/src/testing/testing.go:1011
testing.(*common).Log(0xc0009971e0, {0xc0007d9d10?, 0x348f1e0?, 0x1e7e3a3?})
/nix/store/mi0ybwsm6pmxzv9hsm6bcbqaq1pkf8wh-go-1.23.1/share/go/src/testing/testing.go:1052 +0x4a
github.com/evcc-io/evcc/charger.print(0xc0009971e0, {0xc0009ea630, 0x2f})
/build/source/charger/ocpp_test_logger.go:14 +0x92
github.com/evcc-io/evcc/charger.(*ocppLogger).Debugf(0xc000818000, {0x1e94524?, 0x12?}, {0xc000c01ea0?, 0x12?, 0x40?})
/build/source/charger/ocpp_test_logger.go:19 +0x47
github.com/lorenzodonini/ocpp-go/ocppj.(*Server).SendResponse(0xc0007ee090, {0xc000aa8cdd, 0x6}, {0xc0009a7960, 0x9}, {0x21d94e0?, 0x34b51e0?})
/build/source/vendor/github.com/lorenzodonini/ocpp-go/ocppj/server.go:203 +0x4e9
github.com/lorenzodonini/ocpp-go/ocpp1.6.(*centralSystem).sendResponse(0xc0007ee120, {0xc000aa8cdd, 0x6}, {0x21d94e0, 0x34b51e0}, {0x0?, 0x0?}, {0xc0009a7960, 0x9})
/build/source/vendor/github.com/lorenzodonini/ocpp-go/ocpp1.6/central_system.go:443 +0x47e
github.com/lorenzodonini/ocpp-go/ocpp1.6.(*centralSystem).handleIncomingRequest.func1()
/build/source/vendor/github.com/lorenzodonini/ocpp-go/ocpp1.6/central_system.go:538 +0x8ba
created by github.com/lorenzodonini/ocpp-go/ocpp1.6.(*centralSystem).handleIncomingRequest in goroutine 277
/build/source/vendor/github.com/lorenzodonini/ocpp-go/ocpp1.6/central_system.go:512 +0x58f
panic: Log in goroutine after TestOcpp has completed: 2024-09-22 19:55:39 test-4 ready to transmit again
goroutine 77 [running]:
testing.(*common).logDepth(0xc0009971e0, {0xc000a752c0, 0x33}, 0x3)
/nix/store/mi0ybwsm6pmxzv9hsm6bcbqaq1pkf8wh-go-1.23.1/share/go/src/testing/testing.go:1029 +0x4c5
testing.(*common).log(...)
/nix/store/mi0ybwsm6pmxzv9hsm6bcbqaq1pkf8wh-go-1.23.1/share/go/src/testing/testing.go:1011
testing.(*common).Log(0xc0009971e0, {0xc0005b7c90?, 0x348f1e0?, 0x1e7e3a3?})
/nix/store/mi0ybwsm6pmxzv9hsm6bcbqaq1pkf8wh-go-1.23.1/share/go/src/testing/testing.go:1052 +0x4a
github.com/evcc-io/evcc/charger.print(0xc0009971e0, {0xc00075eb40, 0x1e})
/build/source/charger/ocpp_test_logger.go:14 +0x92
github.com/evcc-io/evcc/charger.(*ocppLogger).Debugf(0xc000818000, {0x1e91db4?, 0xc000aa8cdd?}, {0xc000c50e20?, 0x21d8f80?, 0xc0003b6f01?})
/build/source/charger/ocpp_test_logger.go:19 +0x47
github.com/lorenzodonini/ocpp-go/ocppj.(*DefaultServerDispatcher).messagePump(0xc0009dbe00)
/build/source/vendor/github.com/lorenzodonini/ocpp-go/ocppj/dispatcher.go:556 +0x7e9
created by github.com/lorenzodonini/ocpp-go/ocppj.(*DefaultServerDispatcher).Start in goroutine 76
/build/source/vendor/github.com/lorenzodonini/ocpp-go/ocppj/dispatcher.go:410 +0x14e
FAIL    github.com/evcc-io/evcc/charger 5.099s
FAIL

Can you retry? This test failure could be spurious.

I've rebuilt two times, the error is the result for both. Will try again shortly.

Result of nixpkgs-review pr 343790 run on x86_64-linux 1

1 package blacklisted:

nixos-install-tools

1 package built:

evcc

Okay I'm not sure what's causing the tests to fail, but it built this time. LGTM I guess?

@ofborg build evcc.tests

Tested on aarch64-linux and x86_64-linux.


bump scaler from 1.0.2 to 1.1.0

A single new feature is included in this release. When the elastic stack is very small (<=2 running instances), consider adding a new instance when we suspect the current instances are shutting down and there's pending jobs.
Pull request with more details is here: https://github.com/buildkite/buildkite-agent-scaler/pull/40

@dbaggerman  - once this merges your scaler change will be on master and included in the next release.

As a sanity check I've created a test stack with this branch and confirmed that autoscaling works as normal.


Keypoint task for mechanical turk

Hi! I have a dataset I want to annotate with both keypoints and their corresponding bounding-boxes. I see that you have created a task for annotating bounding-boxes with Mechanical Turk and I'm wondering what needs to be done to support keypoints as well.

I'm also wondering about this issue. Hope for the suggestions!

I'm also looking for a similar solution. I'd love to hear if anyone has made some progress and is willing to share


question: Using chat on Android device

Summary
I want to run chat application on my android device. So I have build wasmedge for Android using NDK and following below link:
https://wasmedge.org/docs/contribute/source/os/android/build
I have changed the build_for_android.sh to support ggml backend.
`#!/bin/bash
if [ ! $ANDROID_NDK_HOME ]; then
echo "Environment variable ANDROID_NDK_HOME is not set."
exit 1
else
echo "Use Android NDK path: $ANDROID_NDK_HOME"
fi
WASMEDGE_ROOT_PATH=$(dirname $(dirname $(dirname $(dirname $0))))
cd ${WASMEDGE_ROOT_PATH}
if ! cmake -Bbuild -DCMAKE_BUILD_TYPE=Release -DWASMEDGE_USE_LLVM=OFF -DCMAKE_SYSTEM_NAME=Android -DCMAKE_SYSTEM_VERSION=23 -DCMAKE_ANDROID_ARCH_ABI=arm64-v8a -DCMAKE_ANDROID_NDK=$ANDROID_NDK_HOME -DCMAKE_ANDROID_STL_TYPE=c++_static -DWASMEDGE_BUILD_STATIC_LIB=ON -DWASMEDGE_LINK_TOOLS_STATIC=ON -DWASMEDGE_PLUGIN_WASI_NN_BACKEND=GGML -DWASMEDGE_PLUGIN_WASI_NN_GGML_LLAMA_BLAS=OFF; then
echo === CMakeOutput.log ===
cat build/CMakeFiles/CMakeOutput.log
echo === CMakeError.log ===
cat build/CMakeFiles/CMakeError.log
exit 1
fi
cmake --build build
echo "Build finished."
For the WASI-NN plugin, you should install this project.
cmake --install build
echo "install done.ß"
`
Build runs successfully. but while running in adb I am getting this error:
command ->  1|violet:/data/local/tmp $ ./wasmedge/wasmedge --dir .:. --nn-preload default:GGML:AUTO:llama-2-7b-chat.Q5_K_M.gguf llama-chat.wasm --prompt-template llama>
error - > unknown option: nn-preload

Appendix
No response

You will need to build the ggml plugin for Android as well. @hydai can you pint us to the instructions on how to compile the plugin from source? Thanks.

Hi  @singhaki
You can check out this doc for building ggml/llama.cpp plugin from source. https://wasmedge.org/docs/contribute/source/plugin/wasi_nn#build-wasmedge-with-wasi-nn-llamacpp-backend

Hi  @singhaki
You can check out this doc for building ggml/llama.cpp plugin from source. https://wasmedge.org/docs/contribute/source/plugin/wasi_nn#build-wasmedge-with-wasi-nn-llamacpp-backend

I tried general linux without acceleration from this doc. Can check the cmake build command i have attached in issue, if I missed anything.

@singhaki
Do you set the plugin path?
https://wasmedge.org/docs/contribute/source/plugin/wasi_nn/#appendix

Thanks @hydai  setting this param worked but when running in adb shell I am getting this error:
Hello[2024-04-10 10:24:26.706] [error] [WASI-NN] GGML backend: Llama input is not set! Error: "Operation error during the chat. Reason: Stream compute error. Backend Error: WASI-NN Backend Error: Caller module passed an invalid argument"
using command:
WASMEDGE_PLUGIN_PATH=/data/local/tmp/build/plugins/wasi_nn ./wasmedge/wasmedge --dir .:. --nn-preload default:GGML:AUTO:dolphin-2_6-phi-2-GGUF.gguf llama-chat.wasm --prompt-template phi-2-instruct

Please use options to log more information:
      --log-prompts
          Print prompt strings to stdout
      --log-stat
          Print statistics to stdout
      --log-all
          Print all log information to stdout

Getting the same error not much info on error side.


Popper in Tooltip always renders children

Bug Report
The Tooltip's Popper's children are always rendered, even if the tooltip content is not visible to the user. This is a performance issue if we have many Tooltip components.
Steps
A clear and concise description of steps to reproduce the problem.
Expected Result
The content is only rendered when its visible to the user.
Actual Result
The content is always rendered 💣
Version
0.37.0

A bit rephrase:
We should render children, we should not execute positioning stuff in Popper until it's visible.


Oncloud Build issues

I actually came here because of owncloud/core#36976
The v2.0.2 tag/commit ref... has disappeared from this repo. So existing yarn.lock that references 2.0.2 now fails. I guess there will be other projects that use this that will also be failing.
Of course we can update to v2.0.3 - but v2.0.2 should still be left available.

Change has been reverted.


add github oidc cloudformation

Add OIDC for github. To be used with pipelines. Refer: https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect

Merging to main for the team to start using the project.


skip screen choice between live and vod when coming back from LTI select

Purpose
When a video creation is started in the LTI select request, we want to continue it once we are in a classic LTI request.
Proposal

[x] Introduce initializing upload state
[x] Redirect to good video create page from lti select

Fixes #1714

Shouldn't you also have a new side effect to set the upload_state at INITIALIZING when clicking on the button create a video ?

No because we want to distinguish if the video has been created in the LTI select request or not.


redis error

Hi, I'm receiving this error:
| redis.exceptions.ConnectionError: Error -2 connecting to your_redis_instance.your_region.redisenterprise.cache.azure.net:10000. Name or service not known.
Based on my understanding, this error suggests that a Redis setup is required in Azure. However, I couldn't find any information about this infrastructure in the project's readme. I'm also curious about the presence of a Redis Docker container in the setup, and how it relates to the Azure setup. I mean, it should work with the local Redis and should not be need of an Azure one, doesn't?
Regards.

At the end it was very simple to solve it, just check the IP of the redis that creates the docker compose in local, change the redis_host variable to this IP, and put the port that appears in the dockerfile for the local REDIS, in this way you can save some money and work in local.


Update NuGet package to 1.3

Hi Tom,
Could you please upload the NuGet package for this project to v1.3.
Cheers

Nevermind all good.


refactor: simpify makefile

Contributor Comments
Simplify the makefile.  Depends on #34
Pull Request Checklist
Thank you for submitting a contribution to easy_sast!
In order to streamline the review of your contribution we ask that you review and comply with the below requirements:

[X] Ensure that make build completes successfully
[X] Keep our reports up-to-date by committing the output of make report
[X] Rebase your branch against the latest commit of the target branch, which likely should be master
[X] If there is an issue associated with your Pull Request, align your PR title with this documentation

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@cba9c51). Click here to learn what that means.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             master       #35   +/-   ##
==========================================
  Coverage          ?   100.00%
==========================================
  Files             ?         8
  Lines             ?       922
  Branches          ?       173
==========================================
  Hits              ?       922
  Misses            ?         0
  Partials          ?         0

Impacted Files
Coverage Δ

veracode/check_compliance.py
100.00% <ø> (ø)

veracode/config.py
100.00% <ø> (ø)

veracode/utils.py
100.00% <ø> (ø)

veracode/submit_artifacts.py
100.00% <100.00%> (ø)

veracode/api.py
100.00% <0.00%> (ø)

veracode/constants.py
100.00% <0.00%> (ø)

... and 2 more

Continue to review full report at Codecov.

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

@pb-seiso had to deconflict, can I get another look?


How does regex greedy quantifier "!" work?

[10:33]  m: say 'fooobar' ~~ /fo**:{1..3}obar/;
[10:33] <+camelia> rakudo-moar 697e4ecff: OUTPUT: «Nil␤»
[10:33]  m: say 'fooobar' ~~ /fo**:?{1..3}obar/;
[10:33] <+camelia> rakudo-moar 697e4ecff: OUTPUT: «｢fooobar｣␤»
[10:33]  m: say 'fooobar' ~~ /fo**:!{1..3}obar/;
[10:33] <+camelia> rakudo-moar 697e4ecff: OUTPUT: «｢fooobar｣␤»
If "!" does be the explicit way to enable greed, and /fo**:{1..3}obar/ using greedy, there is a way to explicitly request greedy with "!" in the regex.

The following are the possible combinations of backtracking modifiers for the ** 1..3 quantifier:

greedy matching with backtracking:

say "aaa" ~~ /           a **   1..3  a /;  # ｢aaa｣
say "aaa" ~~ /           a **!  1..3  a /;  # ｢aaa｣
say "aaa" ~~ /           a **:! 1..3  a /;  # ｢aaa｣
say "aaa" ~~ / :ratchet  a **!  1..3  a /;  # ｢aaa｣
say "aaa" ~~ / :ratchet  a **:! 1..3  a /;  # ｢aaa｣

frugal matching with backtracking:

say "aaa" ~~ /           a **?  1..3  a /;  # ｢aa｣
say "aaa" ~~ /           a **:? 1..3  a /;  # ｢aa｣
say "aaa" ~~ / :ratchet  a **?  1..3  a /;  # ｢aa｣
say "aaa" ~~ / :ratchet  a **:? 1..3  a /;  # ｢aa｣

greedy matching without backtracking ("ratchet"):

say "aaa" ~~ /           a **: 1..3  a /;  # Nil
say "aaa" ~~ / :ratchet  a **  1..3  a /;  # Nil
say "aaa" ~~ / :ratchet  a **: 1..3  a /;  # Nil

Some notes:

:! is the default behavior. You only need to specify it explicitly when you used the :ratchet modifier but want to override it for a single atom.

Similarly, you only need : when you're not in ratchet mode but want to prevent backtracking for a single atom.

Also, :! and :? can be abbreviated to ! and ? when they're applied to a quantifier. The full form with the colon is only necessary when applying them to an alternation, as in:

"ab" ~~ / :ratchet [a || ab]:! $ /

say "aabb" ~~ /           . **:! 1..4  b /;  # ｢aabb｣
(The quantifier first matches aabb, but then the next atom cannot match, so it backtracks to match aab, after which the b can match.)
say "aabb" ~~ /           . **: 1..4  b /;  # Nil
(The quantifier first matches aabb, but then the next atom cannot match, and backtracking into the quantifier is disabled so the match fails.)

So I can be ! override :?

09:13 | yoleaux | 06:32Z  moritz: why say 'fooobar' ~~ /fo**:{1..3}obar/; results differently with say 'fooobar' ~~ /fo**:!{1..3}obar/;
09:14 | moritz | why wouldn't it? it's not the same regex :)
09:16 |   | with : you disable backtracking, so the first part matches all o's, causing the "obar" to fail
09:16 |   | with ! you re-enable it, so the quantifier can give up the extra o again
09:16 |   | :! seems kinda non-sensical
10:50 | wander | moritz, so can I say, in ":!", "!" override ":"? does it imply we can only have one modifier on quantifier?
10:53 | moritz | wander: yes, and I think so

so can I say, in ":!", "!" override ":"?

No, :! is a single modifier. (! is its short-hand form, for use with quantifiers.)
: is a different modifier.
That both happen to contain a colon character like that, doesn't mean one is composed of the other.
Compare e.g. how in Perl 6, +< (left bit-shift) is not a composition of < (smaller-than) and + (addition), but a completely separate operator. Or the same with ~~ and ~, etc.


Windows support

This module wont work on windows due to the following issues:

windows searches the path for executables but if the exec doesn't have a file extension it searches for files with extensions from PATHEXT environment variable. Thus a mock file such as "git" is never found because when it is being searched Windows searches for "git.exe" "git.cmd" "git.bat" etc.
windows doesn't support shebangs so even if the command was magically found, it would not be executed as a node script.

The solution to both of these is to use ForbesLindesay/cmd-shim. It's the same package npm uses to create the executables in node_modules/.bin/ for windows. One caveat is that the actual mock bin will need a mock extension, because cmd-shim creates a cygwin startup script with the bin's name. About to open a pull request.

What shell are you using? I use powershell and git-bash for work (I never use Windows for my open source projects though) and they do support shebangs.

Tried this with cmd.exe and cygwin bash. Neither worked, but pretty cygwin was because child_process.spawn still spawns the child process with cmd.exe instead of bash.

It's seems plausible that this could be also "fixed" by using childProcess exec/spawn with the options.shell = /powershell path/ in packages using this, but that requires them to

find the powershell path
always specify it when using e.g. childProceess.spawn or shelljs.exec
instead of it "just working". Seems like an unnecessary amount of hassle.

Where did you get that idea? Of course they do, npm uses the cmd-shim package I used in that pull request.

Ok, I'm no Windows expert. And I don't particularly like it :) If you could help setting up a Windows CI everything would be clear 😄

Sure, that was on my to do list anyway! I'll open up a PR shortly. I'm just stuck on supporting windows for work reasons, but still want to use the awesome OSS I use for personal projects too :blush:

Added the appveyor ci config to #3.


LocalMode fails to evaluate expression

Hello,
I have a simple RDLC report with a TextBox with the following value :
=Globals!ExecutionTime
I use MvcReportViewer with the 4.5 Framework. The report displays correctly, but this expression fails and displays #Error. The rest of the report is OK.
Apparently a single line should fix the problem :
localReport.SetBasePermissionsForSandboxAppDomain(
AppDomain.CurrentDomain.PermissionSet.Copy());
Source : https://stackoverflow.com/questions/6347125/reportviewer-2010-fails-to-evaluate-expressions
Is it possible to add a parameter to the FluentApi to activate this option?
Or maybe I missed something an existing setting?
Thanks

Sure, I will add this setting to the configuration.

Please use nuget package v0.8.2.

It's perfect, thanks :)


Fix GitHub annotation for using WORKING_DIRECTORY environment variable

When using the newly introduced optional WORKING_DIRECTORY environment variable (#34), the output of this GitHub action, meaning all warnings and errors, is relative to the given WORKING_DIRECTORY. While the action correctly fails or succeeds, the annotations are not displayed correctly within a pull request's "Files changed" tab.
In order to fix this problem, the file parameter in the output should always be an absolute path, starting from the root of the GitHub repository, also when using the WORKING_DIRECTORYenvironment variable. Example:
::warning file=Working-Directory/Package.swift,line=12,col=33::Trailing Comma Violation: Collection literals should not have trailing commas. (trailing_comma)

Thanks!


How do you do the conversion

Hi I wanted to ask you the question : How do you do the conversion from the coordinate on Unity to Unreal is there a Multiplication or an equation depending on the axis ?
Thanks

This is not a bug report...
There's no equation.
Unity has X axis pointing right, Z axis pointing forward, Y axis pointing up. And by default uses one meter unit scale.
Unreal has Y axis is right, X axis pointing forward, and Z is up. And by default it uses 1 centimeter unit scale.
So to convert unity world space matrix, you break it into components - position and basis vectors, convert them all to unreal convention and assemble unreal matrix back from them.
Actually you can see how it is done by looking through UnrealUtilities.cpp and reading UnrealUtilities::unityWorldToUe function. The one that does not have localPositionOffset parameter. Currently it is located at line 278 of the file.

Sorry for putting this on Issue :c
Weird because when I import some asset :
Grid 4 :

Unity : "pos":{"x":-26.318,"y":-12.544,"z":67.172},"rot":{"x":47.486,"y":359.987,"z":281.519},"scale":{"x":1.0,"y":1.0,"z":1.0}
Unreal Engine : Post (X=6717.199707,Y=-2631.800049,Z=-1254.400024) Rot : (Pitch=-47.486000,Yaw=-0.013000,Roll=78.480988)  Scale : (X=1.000000,Y=1.000000,Z=1.000000)
Stalagmite :
-Unity : "pos":{"x":-88.336,"y":-63.158,"z":-74.799},"rot":{"x":0.0,"y":42.077,"z":0.0},"scale":{"x":0.7,"y":0.7,"z":0.7}
-Unreal Engine : Pos : (X=-7479.900391,Y=-8833.599609,Z=-6315.800293)Rot : (Pitch=0.000000,Yaw=42.077011,Roll=0.000000)Scale :(X=0.700000,Y=0.700000,Z=0.700000)

@DiabloFox The numbers you posted are completely correct.
X: -26.318; Y:-12.544;Z:67.172 turns respectively into
Y:-2631.8;Z:-1254.4;X:6717.2. Scale does not change, and... yaw pitch roll are not meant to match euler angles.
Basically, see if the object is at the same spot, faces the same direction and is at the same relative scale compared to the parent.
If it looks the same, then it is positioned correctly.

Oh ! Thank you so much !
So it's  :
X :  Unity(x) -> UE4(y)
Y : Unity(y) -> UE4(z)
Z :  Unity(z) -> UE4(x)

@DiabloFox
That's true only if you're dealing with direction.
With position, you'll have to multiply it by 100 (because unreal uses centimeter scale). See
UnrealUtilities.cpp , functions called "unityPosToUe" and "unityVecToUe". "Pos" means Position, "Vec" means vector or direction.

If you have to do a documentation about it try to add this because there is not really anybody talking about this. And it's really good work, I wish you the best ! Thanks again !

Hi, sorry to bother you but how the rotation is convert from unity to unreal standard ?

Hi, sorry to bother you but how the rotation is convert from unity to unreal standard ?

@DiabloFox As I said before, the plugin does not attempt to convert rotation directly and instead extracts unity object matrix, splits it into basis vectors and  then reassembles it on unreal side as a matrix.
A transform matrix is composed from X/Y/Z vectors that determine object orinetation and scale, and position vector that denotes where the object is.
The conversion procedure for matrices is defined within UnrealUtilities.cpp, function UnrealUtilities::unityWorldToUe .
`FMatrix UnrealUtilities::unityWorldToUe(const FMatrix &unityWorld, const FVector &localPositionOffset){
	FVector xAxis, yAxis, zAxis;
	unityWorld.GetScaledAxes(xAxis, yAxis, zAxis);
	FVector pos = unityWorld.GetOrigin();

	pos += xAxis * localPositionOffset.X + yAxis * localPositionOffset.Y + zAxis * localPositionOffset.Z;

	pos = unityPosToUe(pos);//unityToUe(pos)*100.0f;
	//unityPosToUe(pos);
	xAxis = unityVecToUe(xAxis);
	yAxis = unityVecToUe(yAxis);
	zAxis = unityVecToUe(zAxis);

	FMatrix ueMatrix = FMatrix::Identity;//Well, wow. I expected matrix to have a local constructor.
	ueMatrix.SetAxes(&zAxis, &xAxis, &yAxis, &pos);
	return ueMatrix;
}

Which uses following subroutines:
	return FVector(arg.Z, arg.X, arg.Y);
}

FVector UnrealUtilities::unityPosToUe(const FVector& arg){
	return unityVecToUe(arg) * 100.0f;
}

Again, defined in the same file.
To convert rotation this way, you'd need to first convert rotation to rotation matrix, and then convert the matrix on unreal side to the rotation method you prefer.
Meaning the plugin does not directly convert Quaternions or Euler angles or any other form of rotation and deals with matrices only.

@DiabloFox As I said before, the plugin does not attempt to convert rotation directly and instead extracts unity object matrix, splits it into basis vectors and  then reassembles it on unreal side as a matrix.
A transform matrix is composed from X/Y/Z vectors that determine object orinetation and scale, and position vector that denotes where the object is.
The conversion procedure for matrices is defined within UnrealUtilities.cpp, function UnrealUtilities::unityWorldToUe .
`FMatrix UnrealUtilities::unityWorldToUe(const FMatrix &unityWorld, const FVector &localPositionOffset){
	FVector xAxis, yAxis, zAxis;
	unityWorld.GetScaledAxes(xAxis, yAxis, zAxis);
	FVector pos = unityWorld.GetOrigin();

	pos += xAxis * localPositionOffset.X + yAxis * localPositionOffset.Y + zAxis * localPositionOffset.Z;

	pos = unityPosToUe(pos);//unityToUe(pos)*100.0f;
	//unityPosToUe(pos);
	xAxis = unityVecToUe(xAxis);
	yAxis = unityVecToUe(yAxis);
	zAxis = unityVecToUe(zAxis);

	FMatrix ueMatrix = FMatrix::Identity;//Well, wow. I expected matrix to have a local constructor.
	ueMatrix.SetAxes(&zAxis, &xAxis, &yAxis, &pos);
	return ueMatrix;
}

Which uses following subroutines:
	return FVector(arg.Z, arg.X, arg.Y);
}

FVector UnrealUtilities::unityPosToUe(const FVector& arg){
	return unityVecToUe(arg) * 100.0f;
}

Again, defined in the same file.
To convert rotation this way, you'd need to first convert rotation to rotation matrix, and then convert the matrix on unreal side to the rotation method you prefer.
Meaning the plugin does not directly convert Quaternions or Euler angles or any other form of rotation and deals with matrices only.


gulp.src is not processing globs properly

EDIT 3: SEE NEXT COMMENT
Given the glob build/*/ and the following directory structure:
- gulpfile.js
- build/
  - dir1/
  - dir2/
  - dir3/
  - dir4/
  - 1.txt
  - 2.txt
  - 3.txt
  - 4.txt

I'm using gulp.src("build/*/"), which should resolve to only the directories under build, but gulp-debug shows it's actually resolving the glob to both directories and files under build.
I tested with node-glob and glob-stream separately, and they both work properly. I have issues only when running with gulp.
I've created a repo containing my test cases here: https://github.com/gmahomarf/gulp-blob-test
Here's the output for my test cases, which you can verify with the repo above:
 $ gulp
[09:21:19] Using gulpfile ~/Code/gulp-test/gulpfile.js
[09:21:19] Starting 'default'...
[09:21:19] gulp-debug: build/1.txt
[09:21:19] gulp-debug: build/2.txt
[09:21:19] gulp-debug: build/3.txt
[09:21:19] gulp-debug: build/4.txt
[09:21:19] gulp-debug: build/dir1
[09:21:19] gulp-debug: build/dir2
[09:21:19] gulp-debug: build/dir3
[09:21:19] gulp-debug: build/dir4
[09:21:19] gulp-debug: 8 items
[09:21:19] Finished 'default' after 58 ms

 $ node gulp
[09:21:26] gulp-debug: build/1.txt
[09:21:26] gulp-debug: build/2.txt
[09:21:26] gulp-debug: build/3.txt
[09:21:26] gulp-debug: build/4.txt
[09:21:26] gulp-debug: build/dir1
[09:21:26] gulp-debug: build/dir2
[09:21:26] gulp-debug: build/dir3
[09:21:26] gulp-debug: build/dir4
[09:21:26] gulp-debug: 8 items

 $ node glob
[ 'build/dir1/', 'build/dir2/', 'build/dir3/', 'build/dir4/' ]

 $ node stream
{ cwd: '/home/gazy/Code/gulp-test',
  base: '/home/gazy/Code/gulp-test/build/',
  path: '/home/gazy/Code/gulp-test/build/dir1/' }
{ cwd: '/home/gazy/Code/gulp-test',
  base: '/home/gazy/Code/gulp-test/build/',
  path: '/home/gazy/Code/gulp-test/build/dir2/' }
{ cwd: '/home/gazy/Code/gulp-test',
  base: '/home/gazy/Code/gulp-test/build/',
  path: '/home/gazy/Code/gulp-test/build/dir3/' }
{ cwd: '/home/gazy/Code/gulp-test',
  base: '/home/gazy/Code/gulp-test/build/',
  path: '/home/gazy/Code/gulp-test/build/dir4/' }

EDIT: I tried changing the arguments for gulp.src to ['build/*/', '!build/{,*}.*'] to explicitly ignore all files, but unfortunately that also ignores a couple of folders in my project that have dots in their name
EDIT 2: Added vinyl-fs to the list of tests, also working properly. Also added two extra dirs with dots in their name
 $ node vinyl
[10:22:38] gulp-debug: build/dir.1
[10:22:38] gulp-debug: build/dir.2
[10:22:38] gulp-debug: build/dir1
[10:22:38] gulp-debug: build/dir2
[10:22:38] gulp-debug: build/dir3
[10:22:38] gulp-debug: build/dir4
[10:22:38] gulp-debug: 6 items

I finally traced the issue. It's an issue with the older versions of glob-stream, which gulp uses via an old version of vinyl-fs. The problem is this line https://github.com/gulpjs/glob-stream/blob/v3.1.18/index.js#L113
path.resolve('/some/path', 'build/*/') // results in "/some/path/build/*"

Is there any chance you can update the dependencies?

This has been addressed in issue  #1571

@waynebloss how about you actually read my comment and leave the answering to the repo collaborators?

I did not read the whole entire thing. I see now where you mentioned #1571. Good luck to you.

I'm guessing #1486 would be relevant here too.

Sorry, vinyl-fs has had many breaking changes and we can't update the dependency until gulp 4 to avoid breaking semver.  However, you can use vinyl-fs directly in your gulpfile by replacing gulp.src and gulp.dest with vinylfs.src and vinylfs.dest respectively, which would allow you to use the newer versions or you can upgrade to gulp 4.

@phated Thanks, I endend up using vinyl.src. Purely academic curiosity here: considering the error is in glob-stream and not in vinyl-fs, would updating the glob-stream version only result in breaking changes?

@gmahomarf we've done very small changes in vinyl 0.3.x in the past but it has lead to very messy PRs when other people submit them so we typically reserve it for extreme cases.


Bugfix for -c/--config flag

This patch fixes the issue of a config file specified by the command line not being respected by modules.

Coverage remained the same at 100.0% when pulling f5f6a2bb79c0a3d7d2f9c71d5d0d3ec92fd96af5 on akutz:bugfix/custom-config-file into 5b9b0911e501dd3e6a62bd103b3a195a3f8b3181 on emccode:master.


Add logo, remove Utility from Namespace, add licence to the nuget pac…

the logo was created by me
https://github.com/BinaryKits/ZPLUtility/blob/bca374ecd2f010794de50a12521e778d47fd6d78/doc/logo.png

@tinohager
Changing name space will break existing code, can we keep "BinaryKits.Utility" prefix?

Yes I know it is a breaking change. But I think the project has not yet had a major release and we have now rebuilt some things. And then there is a version 2. We have also moved the elements into a separate folder that has changed the namespace already. A consideration would also be in this step to adapt the models again to PascalCase  "ZplBarcode" instead of "ZPLBarcode"

@tinohager 2.0 would be a good idea.
Help fill your ideas at https://github.com/BinaryKits/ZPLUtility/milestones/1/edit also?


Use new Uyuni POOL repositories

What does this PR change?
As part of the new Uyuni product definitions, we are removing the version from the POOL repositories. And we decided to remove the distribution name from the URL as well (so it's now images so we don't need to change it when we change the base OS.
This means than in the future no sumaform changes will be needed for new Uyuni versions or base OS changes (also good for development)
Requires https://github.com/uyuni-project/uyuni/pull/1535

Apply complete! Resources: 4 added, 0 changed, 0 destroyed

Merging :-)

The Uyuni PR is not required for sumaform, as it worked.


Solax Inverter Component - Improvement

Home Assistant release with the issue:
0.94.3
Last working Home Assistant release (if known):
0.94.3
Operating environment (Hass.io/Docker/Windows/etc.):
HASSIO
Component/platform:
https://www.home-assistant.io/components/solax/
Description of problem:
Are you able to add a "name" to the platform allowing for multiple sensors to be added
I have two inverters and homeassistant by default is adding the second inverter as "_2" on the end but is hard to distinguise between the two
Not sure if it works this way but would the following be how it works?
sensor:
platform: solax
ip_address: IP_ADDRESS
name: inverter1
platform: solax
ip_address: IP_ADDRESS
name: inverter2
This would produce the sensors in the following format
sensor.inverter1_battery_capacity
and
sensor.inverter2_battery_capacity

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum. Thanks!

@matthewjporter it's on my radar :)

@squishykid
Thanks, Let me know if you need me to do any testing, Always happy to help

@matthewjporter
So this wasn't exactly the solution you were looking for, but this is probably the best way to handle it for home-assistant. You can see the discussion on the PR.
This means you just need to change the names manually in the front-end if you want to give the sensors different names.

by serial number and custom name in frontend would work great


OC integration: extractItems voiding excess items

https://github.com/raoulvdberge/refinedstorage/blob/fed239246611d9d3aa52847a447d4b1b3d979c2b/src/main/java/com/raoulvdberge/refinedstorage/integration/oc/EnvironmentNetwork.java#L332
This line is extracting count items instead of insertedSim.getCount() and then inserting what was extracted, so when destination inventory has less space available then extracted all remaining items are lost.
Also, I'm not sure that line 322 and 323 are correct... line 327 would match only if insertedSim.getCount() was greater then transferAmount, which is not possible?
Regards,
Garagoth.

Yes, it should extract count and not insertedSim.getCount() since insertedSim is the remainder after the insertion, NOT the items inserted?
It probably needs transferableAmount instead of count in the extractItem call on line 332, and needs to handle overflow (which it currently doesn't).
Can you verify my theory?

Ah, true, insertedSim is the remainder, correct. Night time reading, apologies.
So maybe, if in line 332 we already know the we can extract count and should be able to insert transferableAmount (from simulations), then we can first insert transferableAmount, get remainder of what was left (should be 0 most of time?), and then extract from RS network transferableAmount - inserted.getCount(), this way overflowing items are handled - by never extracting them from network...
... or you can insert remainder into network again, but that is more operations on network, so worse performance (I imagine inserting is not trivial).

Fixed, thx. Can you verify my fix?


Use custom dataset

Hello,
Thank you for this code it is really helpful. I have a question is it possible to use the same code with custom dataset?
If so please tell me what to change.
Best regards

Yes, you can use AugMax on your own dataset, as long as the augmentations make sense on it.
For implementation, you need to:

Create a file named your_dataset_name.py under AugMax/dataloaders
Define your own dataset class as an inheritance of torch.utils.data.Dataset in your_dataset_name.py. Here is a official tutorial from PyTorch on how to do it.
Write the dataloader code for your own dataset in your_dataset_name.py. You can take my CIFAR10 dataloader as an example.
Import your own dataloader function and load data as I did for CIFAR10 in augmax_training_ddp.py.


Will RLOS indexed based querying work in cluster enabled Redis?

When we use cluster enabled Redis like AWS EC, it's possible that objects gets stored on different shards. Will the indexed based querying still work here?

Sharded index supported only in PRO version.

I really appreciate the quick turnaround. You are doing a great job @mrniko. Thanks a lot!

@mayurgoenka
Thank you!

Hi @mrniko ,
I see that the index is created in the following fashion:
"redisson_live_object_index:{com.org.application.MyLiveObject}:index_field:<some_hash>"
I see that we are using hash tag : {com.org.application.MyLiveObject} for storing all indices belonging to same class inside same keyslot.
In my use case, m trying to store billions of objects of the same class MyLiveObject and there are multiple indices as well. It's obvious that this won't fit in the same keyslot and will need sharding.
Your comment, "Sharded index supported only in PRO version.", does this mean that the index itself will also get sharded across nodes and above use case will still work in PRO version? Same hashtag {com.org.application.MyLiveObject} won't be used in PRO version for indices?
Sorry for the repeated query, but just want to make sure before I finalise my design.
Hope my query is clear.

does this mean that the index itself will also get sharded across nodes and above use case will still work in PRO version

In this case name will be different to distribute evenly across all Redis master nodes.

Same hashtag {com.org.application.MyLiveObject} won't be used in PRO version for indices?

This name still will be present in key, but without braces.

Thank you @mrniko , this means that I can safely use RLOS for huge data in redis clustered mode.
Another query is, are there any plans for supporting batch operations and transactions with RLOS objects?

What kind of batch / transaction operations over RLOS do you need? Could you describe some use cases?

Suppose I want to merge 1000s of Live objects into redis cache, like a batch update OR batch insert. I see that we do have rlos.persist(list) but I not sure if its using pipelining inside or not? Also, rlos.merge(list) is what I was primarily looking for.
These operations are mainly required for warming up the cache in my use case.
Transactions could be required when I want to update 2 different Live objects together or not do them at all. Live objects here can be of same class or different classes.
I need this in my use case because there's a parent-child type of relationship in my application, where if I delete the parent object, child object also needs to get deleted.

org.redisson.api.RLiveObjectService#persist(T...) method stores object in a batch. merge() method for multiple object isn't implemented yet.
As for transactions, I can recommend you to use RLock object.

yes, thank you for the response @mrniko , appreciate it.


Preserve style definition order

Hi there :wave:
We've been using bs-css for a while and we just updated to 6.3.1. It's a great change on all accounts except we noticed a few styles broke. It seems to only occur for styles like this:
className=(
  style(
    merge([
      Styles.input,
      [
        wordWrap(`normal),
        width(px(120)),
        padding2(~v=px(6), ~h=px(8)),
        fontSize(Styles.FontSize.small)
      ]
    ])
  )
)

What happens in this case is that Styles.input contains a fontSize which we assumed would be overwritten by the one declared later. This was the behavior in previous versions.
I traced the problem to this line: https://github.com/SentiaAnalytics/bs-css/blob/master/src/Css.re#L38.
This patch fixed our issue. I'm not aware of any side effects from removing the List.rev application.

I should note that we upgraded from a 5.x version.

Hi thats actually on purpose though its not documented well enough :(
since styles are just lists of css rules it makes sense to treat them as a list. reason/ocaml uses linked lists where its cheap to append to the head, but expensive to add to the tail.
because of this I tried to optimise for the most common example:
let fanzyButton = style([background(hotPink), ...defaultButton])

Your example would be written:
className=style([
  wordWrap(`normal),
  width(px(120)),
  padding2(~v=px(6), ~h=px(8)),
  fontSize(Styles.FontSize.small),
  ...Styles.input
])

simply put i chose the reason way over the css way.
If you disagree with this decision, or think there is a better way to do it please open an issue, I would love your input. :)

It makes sense. Thanks for the explanation.


exo twee <INVALID_CIK>

Running this command now throws an exception of 'type error' rather than a 1P message about the CIK.

I need an example of <INVALID_CIK>. It works for me
$ exo -v
Exosite Command Line 0.9.21
$ exo twee 2262c45567f35451b9e0d44e6bac634e9b243ef3
One Platform exception: {u'message': u'Authorization failed', u'code': 401}

I updated to 0.9.23 and it stopped happening. Maybe it was some partial change leftover from the hackathon.


SSR

How about Server Side Rendering?

I am not a big fan of SSR as it comes with a lot of complexity for very little added value, if any.


refac: Use client from wholesale NuGet

Description

References

https://app.zenhub.com/workspaces/mandalorian-5fd22a1a59e4740018f5ab5a/issues/energinet-datahub/opengeh-wholesale/17

Codecov Report

Merging #998 (8a7b5c7) into main (c6d4721) will increase coverage by 9.56%.
The diff coverage is 88.70%.

@@            Coverage Diff             @@
##             main     #998      +/-   ##
==========================================
+ Coverage   62.88%   72.45%   +9.56%
==========================================
  Files          20       18       -2
  Lines         291      265      -26
  Branches       27       23       -4
==========================================
+ Hits          183      192       +9
+ Misses         94       63      -31
+ Partials       14       10       -4

Impacted Files
Coverage Δ

...stration/JwtTokenSecurityRegistrationExtensions.cs
100.00% <ø> (ø)

...gistration/HealthEndpointRegistrationExtensions.cs
78.94% <78.94%> (ø)

apps/dh/api-dh/source/DataHub.WebApi/Startup.cs
93.90% <80.00%> (+4.05%)
:arrow_up:

...ebApi/Registration/DomainRegistrationExtensions.cs
93.10% <93.10%> (ø)

...Hub.WebApi/Controllers/WholesaleBatchController.cs
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


feat: Support Auth Plugins

Support Auth Plugins

Codecov Report

Merging #140 (fe9821e) into master (d340553) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #140   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            6         6
  Lines          197       197
  Branches        23        23
=========================================
  Hits           197       197

Impacted Files
Coverage Δ

src/citric/client.py
100.00% <ø> (ø)

src/citric/session.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Feature-Request: Please add preferred language (for final output)

Independently from the input language Perplexica most of the time replies in English.
Could you please introduce "preferred output language" in the settings? With prompting like "Please write your final output in {final_output_language}." the preferred language could be used. Thx for considering this.
@ItzCrazyKns: I LOVE THIS PROJECT! IT'S AMAZING!!

Yeah, that would be great.
I haven't tested it yet, but can't you specify that in the prompt?

The issue is same as this one https://github.com/ItzCrazyKns/Perplexica/issues/72, so I will close it, you can follow the other issue for updates.

No, this is not the same. It has to do with the wish to get a new option in the settings. Preferred output language. I cannot see, where to set the preferred output language, because I have no field to set additional prompting exclusively to the final output prompt.

@ItzCrazyKns I think this request is a bit different from #72. That issue is about system prompts for various tasks, but the preferred output language is a separate thing. Adding a setting for this would be super user-friendly and helpful, as we could support many common languages directly.
Thanks for considering it!


irmin-pack: Symlink current generation files

This would simplify the computation of statistics on a pack file.

Same as #1854 ?

Yes it is


Use elastic config options to replace current elastic options

Sometimes I want to search data for a long time such as -last :1 month: , juttle will except Error: internal error Error: Request Timeout after 30000ms (INTERNAL-ERROR). So can I open a PR to replace current elastic options?

Yeah!


Blurry text at certain browser window zoom levels

Description
The Tether module (used by the datepicker to position its popup calendar) uses CSS transforms to trigger GPU optimizations. Using these CSS transforms would result in blurry texts in certain zoom levels. (See Optimization section @ http://tether.io)
Here's a pair of screenshots showing the difference (viewing https://hacker0x01.github.io/react-datepicker/ on [13" MBP, macOS Sierra - Chrome version 58 (Window @ 67% Zoom Level)]:

Proposed Solution
Thankfully, the guys at Hubspot implemented a prop for us to disable this.
<TetherComponent
  classPrefix={'react-datepicker__tether'}
  attachment={this.props.popoverAttachment}
  targetAttachment={this.props.popoverTargetAttachment}
  targetOffset={this.props.popoverTargetOffset}
  renderElementTo={this.props.renderCalendarTo}
  constraints={this.props.tetherConstraints}

  // *** exposing Tether's `optimizations` prop to the datepicker ***
  optimizations={this.props.tetherOptimizations}
>
  ...
</TetherComponent>

Disabling GPU optimization:
<DatePicker
  selected={this.state.startDate}
  onChange={this.handleChange}
  tetherOptimizations={{ gpu: false }}/>

I've made a fix on my end, would love to create a pull request for it! Really liked this library, would be great to get this patched on NPM asap so that we can use it for production =)

So is this a problem? may be a bit blurry is better than lack of GPU optimizations? With this optimization tethered component won't be repainted on scrolling.

Hmm true, this might not be a huge problem for everyone. =S
By exposing more props for the user to control, we can allow them to fine tune the component to their specific use case (might be the reason by this optimization can be disabled in the first place)

This blur is annoying and is becoming a stopper for using this component in our system. +1

I'm very uneasy about adding a prop that is directly tied to the internal implementation of the component -- aside from increasing the API footprint, it hinders our ability to change the internals in the future.  Relatedly, tether's project status is up in the air, and they are encouraging people to use popper.js instead, which may be worth exploring.

@rafeememon I do understand your concerns, isn't tetherConstraints something similar that's already implemented?

@tohjustin, yep it is =)  But I don't think that's a reason to make the hole any deeper.

@rafeememon @alex-shamshurin I guess this fix isn't going through? =S
On a side note, any plans to migrate over popper.js? I can start working on it this weekend =)

If popper is proposed by tether itself, I'd be supportive in moving to
that.
On Thu, 22 Jun 2017 at 18:59, Justin Toh<EMAIL_ADDRESS>wrote:

@rafeememon https://github.com/rafeememon @alex-shamshurin
https://github.com/alex-shamshurin I guess this fix isn't going
through? =S
On a side note, any plans to migrate over popper.js
https://popper.js.org/? I can start working on it this weekend =)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Hacker0x01/react-datepicker/issues/899#issuecomment-310440570,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABWNKKlKjLKq5Dtzo091i6zpiIY4_DX9ks5sGp1YgaJpZM4OAeym
.

@martijnrusschen Is this a green light for me to start working on it? =0

Yeah would love to see a PR 👍

Okay, will create an issue & start working on it this weekend =)

@tohjustin, I think it's worth keeping this open to track the blurriness issue; the switch may or may not solve it

@rafeememon  Thanks for the heads up! =)
I'm aware that this might not fix the issue but will still be glad to help out you guys to migrate over to Popper.js

Popper.js roundes the offset values to avoid half pixels and prevent text blurring

I released the new popper implementation, this should be resolved. Let me know if this still happens.

@martijnrusschen Thanks for the heads up 👍 will let you know if the blurry text is still there!