'electron27' have been found in the repositories

in  freebsd 14.0 only has electron25-25.9.7.
root@F3ja:/usr/home/luba # pkg install electron27
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
pkg: No packages available to install matching 'electron27' have been found in the repositories

Can the program DiscordBSD  be installed using electron25-25.9.7?

Install electron is necessary only if you want to build from source,
If you install discordbsd from the release, is already packaged with electron, That is to say that electron already comes with discordbsd so to speak, If you need electron27 you can install it here:
https://github.com/tagattie/FreeBSD-Electron/releases/tag/v27.1.2

I cancelled today's attempt to build.
electron29 stated at https://github.com/SrWither/DiscordBSD?tab=readme-ov-file#build-dependencies, the attempt to build shows "depends on executable: electron28".
% ./build.sh
Need to elevate permissions to pack DiscordBSD. Do you want to execute the command with doas or sudo? (1 for doas, 2 for sudo)
2
electron.mk checked

up to date, audited 2 packages in 4s

1 high severity vulnerability

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
npm notice
npm notice New patch version of npm available! 10.8.2 -> 10.8.3
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.8.3
npm notice To update run: npm install -g<EMAIL_ADDRESS>npm notice
grahamperrin's password:
===>  License BSD3CLAUSE accepted by the user
===>  License BSD3CLAUSE accepted by the user
===>   discordbsd- depends on file: /usr/local/sbin/pkg - found
===>   discordbsd- depends on package: npm-node20>0 - found
===>   Setting up node modules cache directory
===>   Prefetching and archiving node modules
npm warn deprecated<EMAIL_ADDRESS>This functionality has been moved to @npmcli/fs
npm warn deprecated<EMAIL_ADDRESS>Please use @electron/asar moving forward.  There is no API change, just a package name change

added 514 packages in 30s
npm notice
npm notice New patch version of npm available! 10.8.2 -> 10.8.3
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.8.3
npm notice To update run: npm install -g<EMAIL_ADDRESS>npm notice
=> SrWither-DiscordBSD--main_GH0.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
=> Attempting to fetch https://codeload.github.com/SrWither/DiscordBSD/tar.gz/main?dummy=/SrWither-DiscordBSD--main_GH0.tar.gz
fetch: https://codeload.github.com/SrWither/DiscordBSD/tar.gz/main?dummy=/SrWither-DiscordBSD--main_GH0.tar.gz: size of remote file is not known
SrWither-DiscordBSD--main_GH0.tar.gz                   632 kB 5832 kBps    00s
===> Fetching all distfiles required by discordbsd- for building
===>  License BSD3CLAUSE accepted by the user
===>   discordbsd- depends on file: /usr/local/sbin/pkg - found
===>   discordbsd- depends on package: npm-node20>0 - found
===> Fetching all distfiles required by discordbsd- for building
===>  Extracting for discordbsd-
=> SHA256 Checksum OK for discordbsd--node-modules.tar.gz.
=> SHA256 Checksum OK for SrWither-DiscordBSD--main_GH0.tar.gz.
===>   Copying package.json and package-lock.json to /usr/home/grahamperrin/dev/DiscordBSD/freebsd/work/DiscordBSD-main
===>   Moving prefetched node modules to /usr/home/grahamperrin/dev/DiscordBSD/freebsd/work/DiscordBSD-main
===>  Patching for discordbsd-
===>   Patching package.json
===>   discordbsd- depends on executable: node - found
===>   discordbsd- depends on executable: electron28 - not found

To build electron, you should have around 2GB of memory
and around 14 GB of free disk space.

===>   NOTICE:

This port is deprecated; you may wish to reconsider installing it:

EOLed upstream, switch to newer version.

It is scheduled to be removed on or after 2024-08-31.

===>  License BSD3CLAUSE LGPL21 MPL11 MIT accepted by the user
===>   electron28-28.3.3_1 depends on file: /usr/local/sbin/pkg - found
===>   electron28-28.3.3_1 depends on package: yarn-node18>0 - not found

===>  License BSD2CLAUSE accepted by the user
===>   yarn-node18-1.22.19 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by yarn-node18-1.22.19 for building
===>  Extracting for yarn-node18-1.22.19
=> SHA256 Checksum OK for yarn-v1.22.19.tar.gz.
===>  Patching for yarn-node18-1.22.19
===>  Applying FreeBSD patches for yarn-node18-1.22.19 from /usr/ports/www/yarn-node18/../yarn-node20/files
===>  Configuring for yarn-node18-1.22.19
===>  Staging for yarn-node18-1.22.19
===>   yarn-node18-1.22.19 depends on executable: node - found
===>   Generating temporary packing list
/bin/mkdir -p /usr/ports/www/yarn-node18/work/stage/usr/local/lib/node_modules/yarn
(cd /usr/ports/www/yarn-node18/work/yarn-v1.22.19/ && /bin/sh -c '(/usr/bin/find -Ed $1 $3 | /usr/bin/cpio -dumpl $2 >/dev/null 2>&1) &&  /usr/bin/find -Ed $1 $3 \(   -type d -exec /bin/sh -c '\''cd '\''$2'\'' && chmod 755 "$@"'\'' . {} +  -o -type f -exec /bin/sh -c '\''cd '\''$2'\'' && chmod 0644 "$@"'\'' . {} + \)' COPYTREE_SHARE . /usr/ports/www/yarn-node18/work/stage/usr/local/lib/node_modules/yarn)
install -l rs /usr/ports/www/yarn-node18/work/stage/usr/local/lib/node_modules/yarn/bin/yarn.js  /usr/ports/www/yarn-node18/work/stage/usr/local/bin/yarn.js
install -l rs /usr/ports/www/yarn-node18/work/stage/usr/local/lib/node_modules/yarn/bin/yarnpkg  /usr/ports/www/yarn-node18/work/stage/usr/local/bin/yarnpkg
install -l rs /usr/ports/www/yarn-node18/work/stage/usr/local/lib/node_modules/yarn/bin/yarn  /usr/ports/www/yarn-node18/work/stage/usr/local/bin/yarn
====> Compressing man pages (compress-man)
===>  Installing for yarn-node18-1.22.19

===>  yarn-node18-1.22.19 conflicts with installed package(s):
      yarn-node20-1.22.19

      They install files into the same place.
      You may want to stop build with Ctrl + C.
^C*** Signal 2
*** Signal 2
*** Signal 2
*** Signal 2
*** Signal 2
grahamperrin's password:
sudo: a password is required
cp: freebsd/work/DiscordBSD-main/out/DiscordBSD-linux-x64: No such file or directory
Done!
% pkg iinfo electron
electron29-29.4.6
electron30-30.4.0_1
electron31-31.4.0_1
% uname -aKU
FreeBSD mowa219-gjp4-zbook-freebsd 15.0-CURRENT FreeBSD 15.0-CURRENT main-n271938-3e76d05231b0 GENERIC-NODEBUG amd64 1500023 1500023
%

now discordbsd depends on electron30 which is in the repository


Deposition form - Imprecise information of associated publications

Tester suggestion:
Tool tip text, change to: “If this data is published, information about the publication where it is found.”

And updated version of the description will appear in general parameters schema version 0.9.16


Tiller image not available

Output of helm version:
Client: &version.Version{SemVer:"v2.8+unreleased", GitCommit:"6b83a4125b94f8454bbc8e34f4c727238b2e1082", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.2", GitCommit:"5fa2db2bd46ac79e5e00a4e6ed24191080aa463b", GitTreeState:"clean", BuildDate:"2018-01-18T21:12:46Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"", Minor:"", GitVersion:"v1.9.0", GitCommit:"925c127ec6b946659ad0fd596fa959be43f0cc05", GitTreeState:"clean", BuildDate:"2018-01-26T19:04:38Z", GoVersion:"go1.9.1", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
Minikube

helm init is defaulting to gcr.io/kubernetes-helm/tiller:v2.8 for the tiller-deploy deployment, but that image tag does not exist in the container registry. The available tags are:

v2.8.2
v2.8.2-rc1
v2.8.1
v2.8.0
v2.8.0-rc.1

Temporary workaround is to override the tiller image version during init:
helm init --tiller-image gcr.io/kubernetes-helm/tiller:v2.8.2

Because you're using an unofficial release of Helm, you'll need to go through the steps provided in the documentation around installing a canary version of tiller, which is:
$ helm init --canary-image

If you want to test an official release of Tiller with a dev release of Helm, you need to do so with
$ helm init --tiller-image gcr.io/kubernetes-helm/tiller:v2.8.2

As you already mentioned in your workaround.
Perhaps what we should do is make "unofficial" helm releases ask you to set these feature flags, or just install the canary release by default. I'm more in favour of the former because you may be using an older dev release of helm so the canary image may not work in that situation.
This would be an easy first enhancement if anyone wants to work on this!

resolved in #3781


x/build,x/pkgsite: enable tests of x/pkgsite in build.golang.org

cmd/pkgsite works for go documentation browsing on users machines and replaces the traditional godoc.

https://github.com/golang/go/issues/40371
https://github.com/golang/go/issues/59056).

Include x/pkgsite to build.golang.org and enable relevant tests in platforms users will use to run cmd/pkgsite.

CC @golang/release
Should this issue be moved to x/build?

There are probably two parts: (1) configure x/build to run the tests for the repo, and (2) fix any tests that are discovered to be already failing. Step (1) is x/build, but step (2) is x/pkgsite.

@hyangah Would you like us to help with the x/build part of this issue? Otherwise most of the work here is to ensure x/pkgsite tests will be passing after a builder is running.

The coordinator has been deployed. x/pkgsite are running.

It's also running in LUCI, finding 636 passing tests and 7 failing tests on Windows.

One problem to solve is the Trybot-Result label. Currently, this is still set by Kokoro.
We should probably do one of the following:

create a separate label for Kokoro
move dockerized tests to LUCI

We've created the label.

Kokoro is updated to write to the new label. Submit requirements were not modified, so we still only need the TryBots to succeed in order to submit. How do folks feel about that? Should we continue to require that Kokoro CI pass before submitting?

Looks like it's working: https://go.dev/cl/509695 (which could use a +1...)
I think we should require kokoro-CI for submission though, since so many tests do not run on TryBots: https://go.dev/cl/509476

What's left to do here?

Looks like

we need to skip some tests if there is no git. https://build.golang.org/log/8e0e86a3f504ff99a3b3f4354cc515ea374328f3

golang.org/x/pkgsite/cmd/pkgsite tests fail on android. Either skip tests if there is no toolchain, or even we can consider disabling tests on android.
https://build.golang.org/log/69d850199eabc8d848033e1dcc1aa709f818575e

Sounds like it's done from the release team's perspective, marking as such.

The tests now pass on all platforms they run on, except for android but only at Go 1.20. Go 1.21 has the benefit of https://go.dev/cl/472096 which fixed issues with GOROOT installation on the device. But Go 1.20 doesn't so it can't find the compile tool, and isn't able to load template files from tests.
I think we should just disable the pkgsite tests on Go 1.20 and then mark this as done.

x/pkgsite is all green on both post-submit dashboards (new and old). Thanks all. Closing as done.


Explain Cipher Choice.

The Cipher Spec listed resolves to the following on a typical OpenSSL 1.0.1g
ECDHE-RSA-AES128-GCM-SHA256
ECDHE-ECDSA-AES128-GCM-SHA256
ECDHE-RSA-AES128-SHA256
ECDHE-ECDSA-AES128-SHA256
ECDHE-RSA-AES128-SHA
ECDHE-ECDSA-AES128-SHA
AES128-GCM-SHA256
AES128-SHA256
AES128-SHA
ECDHE-RSA-AES256-GCM-SHA384
ECDHE-ECDSA-AES256-GCM-SHA384
ECDHE-RSA-AES256-SHA384
ECDHE-ECDSA-AES256-SHA384
ECDHE-RSA-AES256-SHA
ECDHE-ECDSA-AES256-SHA
AES256-GCM-SHA384
AES256-SHA256
AES256-SHA
ECDHE-RSA-DES-CBC3-SHA
ECDHE-ECDSA-DES-CBC3-SHA
DES-CBC3-SHA
ECDHE-RSA-RC4-SHA
ECDHE-ECDSA-RC4-SHA
RC4-SHA
There might be good legacy support reasons to support some of these weaker ciphers, but it would be nice to know the browser overlap/reason for support.

Here is the latest:
https://blog.cloudflare.com/end-of-the-road-for-rc4/


[Feature] ABC Notation Extension

For users to be able to document their music note sheets live in StackEdit, I implemented an extension that parses an ```abc block an renders an svg using abcjs.
Resolves #1339.
Screenshot:

@benweet Are you reviewing this? 😃

done @benweet


Create animated pie chart for homepage

A great suggestion from the community was to use nivo.rocks as a react graph component lib

https://nivo.rocks/ (https://github.com/plouc/nivo) based on d3
Pie chart from https://nivo.rocks/pie
Another sample of animated donut chart http://bl.ocks.org/dbuezas/9572040

We can play around with other charts beside pie after the initial version
Actual chart data can be found in the wireframes

I can take the task tonight. But if there are other candidates , feel free to implement it.

This is how it looks now on my local branch, but they are 2 problems:

If we insist the chart to be animated, maybe we have to use the another library like highchart. I couldn't find an animation option with nivo/pie.
I am facing issues with making the pie responsive, the ResponsivePie pointed in the documentation is not showing on the screen with the current configuration. I will investigate this further tonight.

I've researched a bit and found this codesandbox example of hover animation on a pie chart
https://codesandbox.io/s/nivo-website-9yrvz?file=/src/pages/pie/index.js
Please check it out - if we can achieve that it can be sufficient for the initial release
https://user-images.githubusercontent.com/893608/108965046-fc902d80-7684-11eb-88a6-c79c4ad5d70a.mp4

We can also add a metric of all people as a big number in the middle if not too hard to be achieved.
https://nivo.rocks/storybook/?path=/story/pie--adding-a-metric-in-the-center-using-a-custom-layer

Thanks a lot @kachar , i will apply the changes tonight.

Damn, can't do the animation because the functionality is not released yet:
https://github.com/plouc/nivo/issues/1326


FR: execlastinsertid similar to execrows

:execrows runs the query and returns the number of affected rows. Implementing :execlastinsertid would just be a matter of calling .LastInsertId() rather than .RowsAffected() on the sql.Result.

You're in luck as this already exists. You'll want to use :execresult.


Investigate supporting OAuth2.0 clients with pairwise subject_type and multiple redirect_uris

We have previously encountered an issue obtaining id_tokens when for an OAuth2.0 client which has pairwise subject_Type and multiple redirect_uris:
https://github.com/SecureApiGateway/SecureApiGateway/issues/626
Investigate how clients can support this combination.
Create a wiki page documenting how to achieve this

Documentation explaining how pairwise works:
https://curity.io/docs/idsvr/latest/token-service-admin-guide/openid-connect.html#issuing-pseudonymous-subject-identifiers
OIDC DCR spec for sector_identifier_uri:
https://openid.net/specs/openid-connect-registration-1_0.html#SectorIdentifierValidation
Configuring the sector_identifier_uri when doing DCR will resolve the issue.

Configuring the sector_identifier_uri when doing DCR resolves the issue.
As per the spec, the value must be a uri where the TPP is hosting its redirect_uris json document. This must be hosted on a domain that AM is able to access i.e. publicly accessible.

Everything is working as per the OIDC spec.
Documentation added to the wiki here: https://github.com/SecureApiGateway/SecureApiGateway/wiki/Using-Pairwise-Pseudonymous-Identifiers


[ENH] test all BaseObject descendants for sklearn compatibility

Addresses https://github.com/alan-turing-institute/sktime/issues/3120 by ensuring that all BaseObject descendants are tested for sklearn compatibility.
Approach is adding BaseObject to the base class registry, and splitting off a class TestAllObjects from TestAllEstimators.
Secondary changes needed for this:

check_estimator to be adapted to the split
base class strings added in registry for "estimator" and "object"
scitype function modified to return most specific scitype (e.g., exclude "object" from returns if inherits from subclass)

Issues found and fixed:

CNNNetwork did not have dependency tensorflow isolated
some splitters needed default test params via get_test_params
performance metrics and their tags needed to be properly registered in the registry
PinballLoss constructor was not sklearn compatible, similar to the bug in #3119

If correct, this should find the bug in #3119 before the fix is merged.

Confirmation: it does!
FAILED sktime/tests/test_all_estimators.py::TestAllObjects::test_constructor[ExpandingWindowSplitter]


HADOOP-17650. Bump solr to unblock build failure with Maven 3.8.1

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 52s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 39s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
22m 42s

trunk passed

+1 :green_heart:
compile
22m 15s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
18m 52s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
checkstyle
3m 59s

trunk passed

+1 :green_heart:
mvnsite
1m 15s

trunk passed

+1 :green_heart:
javadoc
0m 56s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 51s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+0 :ok:
spotbugs
0m 29s

branch/hadoop-project no spotbugs output file (spotbugsXml.xml)

+1 :green_heart:
shadedclient
16m 26s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
2m 13s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
0m 50s

the patch passed

+1 :green_heart:
compile
21m 39s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
21m 39s

the patch passed

+1 :green_heart:
compile
18m 55s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
javac
18m 55s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
3m 54s
/results-checkstyle-root.txt
root: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
mvnsite
1m 14s

the patch passed

+1 :green_heart:
xml
0m  2s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
0m 54s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 51s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+0 :ok:
spotbugs
0m 26s

hadoop-project has no data from spotbugs

+1 :green_heart:
shadedclient
16m 45s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
0m 25s

hadoop-project in the patch passed.

+1 :green_heart:
unit
1m  0s

hadoop-yarn-applications-catalog-webapp in the patch passed.

+1 :green_heart:
asflicense
0m 46s

The patch does not generate ASF License warnings.

179m 15s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2939/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2939

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell xml spotbugs checkstyle

uname
Linux 09fa06af58c5 4.15.0-126-generic #129-Ubuntu SMP Mon Nov 23 18:53:38 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / c6ae2b694b9a3560f014f3f8ae6a3d984cfb276b

Default Java
Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2939/1/testReport/

Max. process+thread count
598 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-catalog/hadoop-yarn-applications-catalog-webapp U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2939/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 36s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
20m 11s

trunk passed

+1 :green_heart:
compile
20m 34s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
17m 54s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
checkstyle
3m 46s

trunk passed

+1 :green_heart:
mvnsite
1m 34s

trunk passed

+1 :green_heart:
javadoc
1m 12s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m 11s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+0 :ok:
spotbugs
0m 39s

branch/hadoop-project no spotbugs output file (spotbugsXml.xml)

+1 :green_heart:
shadedclient
14m 20s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
2m 20s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
0m 54s

the patch passed

+1 :green_heart:
compile
19m 55s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
19m 55s

the patch passed

+1 :green_heart:
compile
17m 51s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
javac
17m 51s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
3m 42s
/results-checkstyle-root.txt
root: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
mvnsite
1m 32s

the patch passed

+1 :green_heart:
xml
0m  2s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
1m 12s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
1m  9s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+0 :ok:
spotbugs
0m 35s

hadoop-project has no data from spotbugs

+1 :green_heart:
shadedclient
14m 24s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
0m 34s

hadoop-project in the patch passed.

+1 :green_heart:
unit
1m  7s

hadoop-yarn-applications-catalog-webapp in the patch passed.

+1 :green_heart:
asflicense
0m 55s

The patch does not generate ASF License warnings.

169m 44s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2939/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2939

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell xml spotbugs checkstyle

uname
Linux d06704d459ac 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / c6ae2b694b9a3560f014f3f8ae6a3d984cfb276b

Default Java
Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2939/3/testReport/

Max. process+thread count
752 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-catalog/hadoop-yarn-applications-catalog-webapp U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2939/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  3s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 21s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
22m 52s

trunk passed

+1 :green_heart:
compile
22m 18s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
18m 56s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
checkstyle
4m  2s

trunk passed

+1 :green_heart:
mvnsite
1m 15s

trunk passed

+1 :green_heart:
javadoc
0m 55s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 52s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+0 :ok:
spotbugs
0m 28s

branch/hadoop-project no spotbugs output file (spotbugsXml.xml)

+1 :green_heart:
shadedclient
20m 16s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
2m 27s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 17s

the patch passed

+1 :green_heart:
compile
23m 51s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
23m 51s

the patch passed

+1 :green_heart:
compile
18m 59s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
javac
18m 59s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
3m 53s
/results-checkstyle-root.txt
root: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
mvnsite
1m 13s

the patch passed

+1 :green_heart:
xml
0m  3s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
0m 54s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 52s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+0 :ok:
spotbugs
0m 26s

hadoop-project has no data from spotbugs

+1 :green_heart:
shadedclient
16m 45s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
0m 24s

hadoop-project in the patch passed.

+1 :green_heart:
unit
1m  2s

hadoop-yarn-applications-catalog-webapp in the patch passed.

+1 :green_heart:
asflicense
0m 48s

The patch does not generate ASF License warnings.

186m 27s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2939/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2939

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell xml spotbugs checkstyle

uname
Linux caea08f9b0d4 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / c6ae2b694b9a3560f014f3f8ae6a3d984cfb276b

Default Java
Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2939/2/testReport/

Max. process+thread count
515 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-catalog/hadoop-yarn-applications-catalog-webapp U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2939/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

@smengcl could you please review the PR?
Thanks

@smengcl I have updated release notes on Jira HADOOP-17650

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 50s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 27s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
22m 52s

trunk passed

+1 :green_heart:
compile
22m 19s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
18m 59s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
checkstyle
4m  4s

trunk passed

+1 :green_heart:
mvnsite
1m 16s

trunk passed

+1 :green_heart:
javadoc
0m 54s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 52s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+0 :ok:
spotbugs
0m 29s

branch/hadoop-project no spotbugs output file (spotbugsXml.xml)

+1 :green_heart:
shadedclient
16m 30s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
2m 31s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
0m 51s

the patch passed

+1 :green_heart:
compile
21m 44s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
21m 44s

the patch passed

+1 :green_heart:
compile
18m 54s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
javac
18m 54s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
3m 57s
/results-checkstyle-root.txt
root: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
mvnsite
1m 15s

the patch passed

+1 :green_heart:
xml
0m  2s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
0m 54s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 53s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+0 :ok:
spotbugs
0m 26s

hadoop-project has no data from spotbugs

+1 :green_heart:
shadedclient
16m 50s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
0m 24s

hadoop-project in the patch passed.

+1 :green_heart:
unit
1m  0s

hadoop-yarn-applications-catalog-webapp in the patch passed.

+1 :green_heart:
asflicense
0m 46s

The patch does not generate ASF License warnings.

179m 55s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2939/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2939

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell xml spotbugs checkstyle

uname
Linux 5e8180284a07 4.15.0-126-generic #129-Ubuntu SMP Mon Nov 23 18:53:38 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / c6ae2b694b9a3560f014f3f8ae6a3d984cfb276b

Default Java
Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2939/4/testReport/

Max. process+thread count
599 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-catalog/hadoop-yarn-applications-catalog-webapp U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2939/4/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

FYI @aajisaka if you would like to take a look

@smengcl I have updated release notes on Jira HADOOP-17650
Does it sound good to you?
Thanks

Release notes looks good. Thanks!


Bug: Build preview showing "Inventory" artifacts as equipped to current character

It happens when the character already has a build equipped, but you change the filters or optimization target which results in a different build. You cannot make this happen if the character has no artifacts equipped to start with.

A follow on from this. It can also be reproduced by generating a build "using equipped" then unchecking "use equipped" and regenerating. It will show the slots that had previously been an equipped artifact as still being "equipped" to a character - but they are infact not.
It just appears not to be updating the artifact location icon.


Bogus "Prefer const with constant constructors" lint when using type arguments

class Test<T> { const Test(); }

Test<T> test<T>() => new Test<T>();

void main() {
  test<int>();
}

->
  lint • Prefer const with constant constructors at test.dart:3:22 • prefer_const_constructors

...but that's bogus, because if you actually use a const constructor here, it will fail at runtime since T isn't const.

I just ran into this again.

@a14n In case you're interested in looking at this. It should be fairly simple to check the invocation to see whether it has type arguments, and if so whether any of the type arguments are type parameters.


IOT instruction (core dumped) on dnn TextDetectionModel_EAST::detect

Before reporting an issue please first check the
troubleshooting guide. If
the issue you're encountering is not solved thereby please state the following in your bugreport:

Operating system Linux ... 6.1.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Tue, 24 Jan 2023 21:07:04 +0000 x86_64 GNU/Linux
The way you installed OpenCV: package
OpenCV version 4.7.0-1
rustc version (rustc --version) rustc 1.66.0 (69f9c33d7 2022-12-12)
Attach the full output of the following command from your project directory:
Upon running a detect on an image:

/usr/include/c++/12.2.0/bits/stl_vector.h:1123: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = float; _Alloc = std::allocator<float>; reference = float&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.
/usr/include/c++/12.2.0/bits/stl_vector.h:1123: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = float; _Alloc = std::allocator<float>; reference = float&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.
/usr/include/c++/12.2.0/bits/stl_vector.h:1123: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = float; _Alloc = std::allocator<float>; reference = float&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.
/usr/include/c++/12.2.0/bits/stl_vector.h:1123: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = float; _Alloc = std::allocator<float>; reference = float&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.
[1]    34917 IOT instruction (core dumped)  cargo run -p [crate_name]

Adding additional backtraces appears to not provide any more output (which makes sense due to being warnings from opencv itself)
can confirm this code used to previously work on crate version 0.63.x, but no longer does on 0.76.x.

Thanks! Can you share the minimum example that fails for you on 0.76, but works on 0.63? And if you have some spare time it would be really useful to know which crate version actually broke it.

I'm going to close this for now, but please feel free to reopen it if you think there is something still to work on here!


Feat/targets to new dao

The new admin API is fairly similar to the previously existing one, but there are some breaking changes:

Lists (GET /upstreams or GET /upstreams/{upstream}/targets) don't accept query-attributes for filtering any more
Pagination: the total attribute is gone
Format of error messages has changed to new DAO errors.
PUT actions now are applied to entities instead of to collections. (PUT /upstreams/foo instead of PUT /upstreams
Some error codes have changed:

Attempting to use an invalid name name (such an IP address) when updating an upstream has become a 500 error instead of a 400.
PUT actions return a 200 on creation instead of 201.

timestamps (like created_at) are floating point numbers now (in all entities - not just upstreams and services).

New features:

There is a attribute called next on paginated admin API results.
When listing the targets for an upstream with db.targets:for_upstream(u), the list only includes active targets, and is reverse-sorted by created_at+id. This is the method used in /upstreams/{upstream}/targets
There is also a db.targets:for_upstreams_raw(u) which returns all targets, including those with weight=0, associated with the upstream. That's what used in /upstreams/{upstream}/targets/all
db.targets:for_upstream_with_health(u) is the same list as db.targets:for_upstream(u) but also includes health information (so it is slower to call). It is used in /upstreams/{upstream}/health.
In addition to those there's db.targets:for_upstream_sorted(u) which returns the targets sorted by created_at+id. It is used internally in a couple places for things like cleaning up and building the cache.
The db.targets:delete method creates a new target with weight = 0. The only way to really delete a target from the database is by inserting targets (this will eventually trigger a clean_history call).
The the db.targets:post_health is the one-place for changing health status of a target. It deals with balancer changes and sending events to the cluster. It is used in POST /upstreams/{upstream}/targets/{target}/healthy|unhealthy.

Prerequisites:

Cassandra migrations where not re-entrant (they can not "catch exceptions and continue" like postgres can). In the past the tests where run only in postgresql. I had to add a way to "ignore errors" in order to allow re-entrant migrations in Cassandra.
There was a lurking bug related with partial updates of record-type fields.
Needed a new kind of validator to allow validating the hash_on_header is not equal to hash_fallback_header
The target.target attribute is an endpoint key but it is not unique. Had to remove that restriction from the system.
Timestamps should have millisecond-precision, but until we updated the targets to the new DAO we didn't realize that we where storing them with second-precision in the database.

@kikito please remove from this PR the commits that were already merged via other PRs (I'm not doing it myself to avoid getting your local branch out of sync)

@hishamhm done - I have left the timestamps-as-float commit because it is needed for the tests to pass.


Failed to activate the atom-ctags package

[Enter steps to reproduce below:]

...
...

Atom Version: 1.0.0
System: Unknown Windows Version
Thrown From: atom-ctags package, v4.1.4
Stack Trace
Failed to activate the atom-ctags package
At Module did not self-register.

Error: Module did not self-register.
  at Error (native)
  at Object.module.(anonymous function) (ATOM_SHELL_ASAR.js:118:20)
  at Object.module.(anonymous function) (ATOM_SHELL_ASAR.js:118:20)
  at Object.module.(anonymous function) [as .node] (ATOM_SHELL_ASAR.js:118:20)
  at Module.load (module.js:347:32)
  at Function.Module._load (module.js:302:12)
  at Module.require (module.js:357:17)
  at require (module.js:376:17)
  at Object.<anonymous> (C:\Users\Administrator\.atom\packages\atom-ctags\node_modules\ctags\src\ctags.coffee:1:10)
  at Object.<anonymous> (C:\Users\Administrator\.atom\packages\atom-ctags\node_modules\ctags\src\ctags.coffee:1:1)
  at Module._compile (module.js:452:26)
  at Object.requireCoffeeScript (C:\Users\Administrator\AppData\Local\atom\app-1.0.0\resources\app.asar\node_modules\coffee-cash\lib\coffee-cash.js:85:19)
  at Module.load (module.js:347:32)
  at Function.Module._load (module.js:302:12)
  at Module.require (module.js:357:17)
  at require (module.js:376:17)
  at Object.<anonymous> (C:\Users\Administrator\.atom\packages\atom-ctags\lib\ctags-cache.coffee:3:9)
  at Object.<anonymous> (C:\Users\Administrator\.atom\packages\atom-ctags\lib\ctags-cache.coffee:2:1)
  at Module._compile (module.js:452:26)
  at Object.requireCoffeeScript (C:\Users\Administrator\AppData\Local\atom\app-1.0.0\resources\app.asar\node_modules\coffee-cash\lib\coffee-cash.js:85:19)
  at Module.load (module.js:347:32)
  at Function.Module._load (module.js:302:12)
  at Module.require (module.js:357:17)
  at require (module.js:376:17)
  at Object.module.exports.activate (C:\Users\Administrator\.atom\packages\atom-ctags\lib\main.coffee:33:19)
  at Package.module.exports.Package.activateNow (C:\Users\Administrator\AppData\Local\atom\app-1.0.0\resources\app.asar\src\package.js:240:19)
  at C:\Users\Administrator\AppData\Local\atom\app-1.0.0\resources\app.asar\src\package.js:221:30
  at Package.module.exports.Package.measure (C:\Users\Administrator\AppData\Local\atom\app-1.0.0\resources\app.asar\src\package.js:165:15)
  at Package.module.exports.Package.activate (C:\Users\Administrator\AppData\Local\atom\app-1.0.0\resources\app.asar\src\package.js:213:14)
  at PackageManager.module.exports.PackageManager.activatePackage (C:\Users\Administrator\AppData\Local\atom\app-1.0.0\resources\app.asar\src\package-manager.js:452:21)
  at C:\Users\Administrator\AppData\Local\atom\app-1.0.0\resources\app.asar\node_modules\settings-view\lib\package-manager.js:362:29
  at exit (C:\Users\Administrator\AppData\Local\atom\app-1.0.0\resources\app.asar\node_modules\settings-view\lib\package-manager.js:53:16)
  at triggerExitCallback (C:\Users\Administrator\AppData\Local\atom\app-1.0.0\resources\app.asar\src\buffered-process.js:213:47)
  at ChildProcess.<anonymous> (C:\Users\Administrator\AppData\Local\atom\app-1.0.0\resources\app.asar\src\buffered-process.js:235:18)
  at emitTwo (events.js:87:13)
  at ChildProcess.emit (events.js:169:7)
  at Process.ChildProcess._handle.onexit (child_process.js:1057:12)

Commands
     -8:42.5.0 command-palette:toggle (atom-text-editor.editor.is-focused)
 12x -8:38.7.0 core:backspace (atom-text-editor.editor.mini.is-focused)
     -8:12.6.0 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -8:12.6.0 core:cancel (atom-text-editor.editor.mini.is-focused)
     -6:21.8.0 fuzzy-finder:toggle-file-finder (atom-text-editor.editor.is-focused)
  7x -6:16.7.0 core:backspace (atom-text-editor.editor.mini.is-focused)
     -6:14.1.0 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -6:14.1.0 core:cancel (atom-text-editor.editor.mini.is-focused)
     -3:12.2.0 core:confirm (atom-text-editor.editor.mini.is-focused)

Config
{
  "core": {}
}

Installed Packages
# User
atom-ctags, v4.1.4
linter-php, v0.0.15

# Dev
No dev packages

Yes, I have the same issue. I think when the Atom Version 1.0.0 came out, this is happening...
A little update to fix this would be so much appreciated :)
Thanks.

@Evrei @vstoykov @fxlt @imalitavakoli would you please try:
cd ~/.atom/package/atom-ctags
rm -rf node_modules/
apm install

Also try:
cd ~/.atom/package/atom-ctags
apm rebuild

I am seeing this issue as well.

Install atom-ctags -> see error mentioned above
Uninstall and re-install atom-ctags -> see error mentioned above
Restart Atom -> see warning that symbols-view is have been disabled
atom-ctags seems to work, can execute from command palette and keyboard shortcuts
Attempted combinations of reinstalling atom-ctags with and without symbols-view enabled -> unable to reproduce now

Atom: 1.0.0
atom-ctags: 4.1.4
symbols-view (0.99.0)
atom-beautify (0.28.7)
clipboard-history(0.6.6)
highlight-selected (0.10.1)
rails-transporter (1.2.0)
ruby-test (0.9.11)
last-cursor-position (0.9.0)
OSX Yosemite

@yongkangchen looks like it's working now

Just had this issue, it's still occuring.

Me too

@jaitaiwan @jhasse did you guys removed the plugin completely and installing it again?

I did, also tried a fresh install of atom with just this plugin installed.
The OS itself is a clean install on a new computer as well so everything is
fairly stock standard
On Fri, 3 Jul 2015 22:09 Venelin Stoykov<EMAIL_ADDRESS>wrote:

@jaitaiwan https://github.com/jaitaiwan @jhasse
https://github.com/jhasse did you guys removed the plugin completely
and installing it again?
—
Reply to this email directly or view it on GitHub
https://github.com/yongkangchen/atom-ctags/issues/109#issuecomment-118330696
.

I had the same issue, just tried disabling the symbols-view and restart, it worked.

Probably now atom-ctags do not disable symbols-view on install.
@jaitaiwan @jhasse can you see if symbols-view plugin is enabled on your installations even after atom-ctags is installed?

I can confirm it is still enabled after instilling atom-ctags.

I have that problem but i haven't atom-ctags installed.


Android compile error with latest version

Hi, I have updated bgfx today and following compile error appears:
../../../examples/common/entry/entry_android.cpp:119:58: error: no member named 'get' in 'bx::FilePath'
m_file = AAssetManager_open(m_assetManager, _filePath.get(), AASSET_MODE_RANDOM);

Replacing _filePath.get() with _filePath.getCPtr() fixes the problem.


feat(protocol): fix signal service multi-hop proof verification bugs [wait for base PR to be merged first]

There are two bugs:

We should not allow users to specify the crossChainSync address, it should always be the "taiko" address on the curernt chain.
We should check that each hop relay -- the middleman contract that sends stateRoot as a signal to its local signal service. Previously this address is not verified correctly using the AuthorizableContract contract. Now we removed AuthorizableContract and introduce a HopRelayRegistry to verify hop relays explicitly. Note that if the signal service disabled multi-hop bridging, the HopRelayRegistry is not needed.

approving as merge master. i removed the ! as we wont worry about breaking change for now.

Approved because I think this correctly links the difference chains, but still with low certainty.

Lets disable multi-hop for now in the code.


Scrolling issue on touch devices

Forum: https://forum.playcanvas.com/t/html-elements-block-touch-move-events-on-playcanvas-ui-elements-but-not-mouse-move/34894
Repro: https://playcanvas.com/editor/scene/1904586
Under some conditions, the scrolling does not work on touch devices.
Steps:

launch on a touch device (or chrome emulator)
tap and drag to scroll
scroll doesn't work if started from the square area
works fine with mouse

Might be a user error, as disabling the attached script enables scrolling.

Closing as user error. The overlaying DIV needs to pass the events to the underlying canvas.


Release v7.6.0

v7.6.0 (2020-01-18)
Changed

(react-native): Update bugsnag-cocoa to v6.5.1

Fix a regression where OOM events were missing session information. bugsnag-cocoa#963
Make maxPersistedEvents and maxPersistedSessions default to 32 and 128, respectively. bugsnag-cocoa#966

Fixed

(react-native): Ensure unhandled promise warning is logged in development #1235
(core): the OnErrorCallback type definition now allows Promise<boolean> as a return type. #1224

@bengourley I've updated the changelog & merged https://github.com/bugsnag/bugsnag-js/pull/1244

@bengourley I've updated the changelog & merged https://github.com/bugsnag/bugsnag-js/pull/1244


[5.2] Routing: Controller __call method no longer called on non-existent methods

I have a __call method in my controller to catch calls to non-existant methods from a route, but after upgrading to 5.2 it never gets called.
Instead an error is thrown:
ReflectionException in Route.php line 264:
Method App\Http\Controllers\PagesController::aboutUs() does not exist

It was very useful for serving static pages, as it avoided having dozens of controller methods that just returned a view.
For example, I could do the following and just serve a matching template (if it existed) based on the method name via the __call method (Advantage of using the method name was the path and name can change).
Route::get('/about-us', [
    'as' => 'pages.about-us',
    'uses' => 'PagesController@aboutUs',
]);

Full example here: https://github.com/4lun/laravel-call-test/commit/ea10eb1c40b0a85e91411640b387e7f13ef987a5
Was this a deliberate change?

Why not overriding missingMethod method from Illuminate\Routing\Controller?
namespace App\Http\Controllers;

class TestController extends Controller
{
    protected $staticRoutes = [ 'about-us', 'contact-us' ];

    public function missingMethod( $parameters = [ ] )
    {
        $path = reset( $parameters );

        if (!in_array( $path, $this->staticRoutes )) {
            return parent::missingMethod( $parameters );
        }

        return view( $path );
    }
}

+1, I came across the same problem.

This isn't supported anymore. Maybe you can define a /{wildcard} route and handle it that way.


Yaml output indentation

I am using https://github.com/juhaku/utoipa 's to_yaml which uses serde_yaml::to_string, to generate a openapi 3 yaml file, and there is a lack of typical indentation in the output of arrays/sequences.
e.g.
openapi: 3.0.3
info:
  title: foobar
  description: Service to do blah ...
  contact:
    name: ''
  license:
    name: ''
  version: 0.1.0
paths:
  /my_endpoint_name:
    post:
      tags:
      - my_tag

Typical linters, e.g. https://pypi.org/project/yamllint/,  require the - my_tag to be indented an extra two spaces.  A lot of python cloud tools use yamllint, e.g. ansible-lint.  More can be seen at https://www.wheelodex.org/projects/yamllint/rdepends/ , and that is just Python.  https://developers.home-assistant.io/docs/documenting/yaml-style-guide/ is another style guide which expects that indentation.
I did a quick test against serde_yaml directly, and it looks like that the lack of indentation is the default.  i.e. the following is true
let mut buffer = Vec::new();
let mut ser = serde_yaml::Serializer::new(&mut buffer);
let deserialized: BTreeMap<&str, Vec<&str>> = serde_yaml::from_str("k:\n  - a\n  - b\n  - c\n").unwrap();
deserialized.serialize(&mut ser).unwrap();
assert_eq!(buffer, b"k:\n- a\n- b\n- c\n");

i.e. the indentation is dropped.
It would be great if the default could be updated.
And allow something like serde_json::PrettyFormatter::with_indent.  It would also be handy to be able to specify other defaults, like whether strings should be enclosed in ' or " by default.  I see something similar was asked in https://github.com/dtolnay/serde-yaml/issues/226

I would accept a PR to increase the indentation of sequence elements.

Looks like it might not be possible using libyaml https://github.com/yaml/libyaml/issues/224

fwiw, I was able to workaround this by pushing the yaml through a yaml-rust roundtrip, which defaults to the typical style of indentation in the output of sequences.

Which style does https://github.com/pantoniou/libfyaml do? If it works better we can switch from libyaml to libfyaml.

IMO it looks good.
When I roundtrip yaml which has the desired indentation, forcing it into flow mode and then back to block mode, the desired indentation is restored.
i.e. fy-tool --mode=flow in.yaml | fy-tool --mode=block > out.yaml; cmp in.yaml out.yaml :+1:

Anyone wanting to solve this with postprocessing on the CLI can use Rust tool https://github.com/xbcsmith/ymlfxr ; unfortunately not yet on crates.io - see https://github.com/xbcsmith/ymlfxr/issues/1


help:PullRequestListOptions State

see
// PullRequestListOptions specifies the optional parameters to the
// PullRequestsService.List method.
type PullRequestListOptions struct {
	// State filters pull requests based on their state. Possible values are:
	// open, closed, all. Default is "open".
	State string `url:"state,omitempty"`

	// Head filters pull requests by head user and branch name in the format of:
	// "user:ref-name".
	Head string `url:"head,omitempty"`

Is there State merged?

Hi @tanjunchen - I'm sorry, but I don't understand the question.
What do you mean "Is there State merged"?
Looking at the code, I'm wondering why both State and Head are not string pointers... maybe that is the issue you are having problems with?  If so, then maybe we have a bug.

Sorry, I didn’t describe my problem well. My question is  that we can pass "merged" in flag State.

Oh!  I understand now... sorry I didn't get it before.
According to the GitHub v3 API documentation:
https://developer.github.com/v3/pulls/#list-pull-requests
it doesn't look like it accepts a merged value for State.
But then it also has this endpoint:
https://developer.github.com/v3/pulls/#get-if-a-pull-request-has-been-merged
and our corresponding method is IsMerged:
https://pkg.go.dev/github.com/google/go-github/github?tab=doc#PullRequestsService.IsMerged
I hope that helps.

@gmlewis thanks
/close


Add test fixtures

Purpose

A event test fixture factory could help to test the function of the GELFParser

Proposal

[ ] Implementation of the event test fixture factory

I didn't see any circle-ci config file. Maybe we could add one to run the test suite (and use it as a base in the future for more checks / build)? What do you think @jmaupetit ? Or maybe in a separate PR to also include some linters like in others openfun projects?

I didn't see any circle-ci config file. Maybe we could add one to run the test suite (and use it as a base in the future for more checks / build)? What do you think @jmaupetit ? Or maybe in a separate PR to also include some linters like in others openfun projects?

Hello @slandrault ,
do you search this config file https://github.com/openfun/ralph/blob/master/.circleci/config.yml ?

I didn't see any circle-ci config file. Maybe we could add one to run the test suite (and use it as a base in the future for more checks / build)? What do you think @jmaupetit ? Or maybe in a separate PR to also include some linters like in others openfun projects?

Hello @slandrault ,
do you search this config file https://github.com/openfun/ralph/blob/master/.circleci/config.yml ?

:sweat_smile: Awesome, I don't know why I didn't see it, I was probably on the wrong branch. All good then, sorry about that!

Closing this pull request as it will be split into smaller pieces.
The first part is #59


Installation "functorch" on Windows 11 failed.

My OS:
Edition	Windows 11 Pro
Version	21H2
Installed on	12/23/2021
OS build	22000.556
Experience	Windows Feature Experience Pack 1000.22000.556.0
 >>nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2021 NVIDIA Corporation
Built on Sun_Aug_15_21:18:57_Pacific_Daylight_Time_2021
Cuda compilation tools, release 11.4, V11.4.120
Build cuda_11.4.r11.4/compiler.30300941_0

The first try (Installing functorch beta):
torch.version =  "1.11.0"
>> pip install functorch==0.1.0
ERROR: Could not find a version that satisfies the requirement functorch (from versions: none)
ERROR: No matching distribution found for functorch

The second try (from source):
torch.version = "1.12.0.dev20220228+cu111"
>>pip install --user "git+https://github.com/pytorch/functorch.git"
error_log.txt
Any help would be appreciated. Thanks!

Thanks for reporting @mzhen77 , unfortunately currently there is no binaries for windows: https://pypi.org/project/functorch/#files
I'm not sure if functorch building from source on Windows was solved since https://github.com/pytorch/functorch/issues/331
Which msvc version you are using ?
The error you have is:
AttributeError: 'MSVCCompiler' object has no attribute 'compiler_so'

which means that functorch does not support standard Windows build environment.
We can try to follow same suggestions as for building pytorch from source: https://github.com/pytorch/pytorch#from-source

Thanks for the quick response @vfdev-5
My version of msvc:
Microsoft (R) C/C++ Optimizing Compiler Version 19.29.30133

I'm not sure if my question is appropriate here, but I also experience the same problem on a Mac.
Currently, I am using the Apple M1 pro chip with Monterey 12.3.1.
Whenever I try to install the package from pip install functorch, it gives an error:
ERROR: Could not find a version that satisfies the requirement functorch (from versions: none)
ERROR: No matching distribution found for functorch

functorch instruction page said that
"We currently support manylinux and MacOS, please reach out on GitHub for other platforms."
In this case, does Mac OS include M1 chips or only for Intel chips?
I really want to try vmap and any help would be appreciated!
Thank you in advance!

Currently, I am using the Apple M1 pro chip with Monterey 12.3.1.

@kyoungseoun-chung I assume that you have PyTorch installed and working for your hardware. Can you try install functorch from source using following command:
pip install git+https://github.com/pytorch/functorch

and report if there is an error or things are working. Thanks

Currently, I am using the Apple M1 pro chip with Monterey 12.3.1.

@kyoungseoun-chung I assume that you have PyTorch installed and working for your hardware. Can you try install functorch from source using following command:
pip install git+https://github.com/pytorch/functorch

and report if there is an error or things are working. Thanks

(Just for the clarification, I am working with PyTorch 1.11.0)
With suggested command, I received lengthy error message. (Seems like compilation failure.)
I am not able to copy all of the messages but the last part of the error message is following:
".../site-packages/torch/utils/cpp_extension.py", line 1756, in _run_ninja_build
raise RuntimeError(message) from e
RuntimeError: Error compiling objects for extension
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> functorch

note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.

However, if I install PyTorch-nightly version (1.12.0.dev20220405) and use the command you suggest, I can install functorch without problem.
Should I stick to nightly version? I am working on multiple devices (one is M1 mac and other is intel CPU with NVIDIA GPU). Therefore, I'd like to avoid use of nightly version as much as possible. (do not want to pip install different version of PyTorch depends on availability of CUDA device...)
Thank you in advance!

@kyoungseoun-chung sorry I had to mention in my previous comment that installing from source requires pytorch nightly. Sounds good that you could compile and install functorch with pytorch nightly on your hardware.
However If you wish to use stable pytorch v1.11.0, you can compile corresponding functorch v0.1.0:
pip install --upgrade<EMAIL_ADDRESS>

Thank you so much. Your solution is working now. I can confirm that with --upgrade flag, I can successfully install functorch.
Really appreciate your kind consideration to me.
Have a great day!

@mzhen77 We now support building from source on Windows. Could you please try that again and let us know how it goes?

Thank you very much @zou3519, I was able to install it. I did not play much but the "hello world" works.

Awesome. Please do let us know if you run into problems using functorch on Windows (we haven't done any stress testing yet)


Stack trace is not useful because of queue system loses context

I saw another person raise this issue but it was closed, so I am going to try to explain this a bit differently.
The file connection.ts uses a Queue system and when an error is thrown (e.g. here), the original context of the stack trace is lost. This makes not useful for debugging, I'll include examples below.
To demonstrate this, I added this line to the top of the request method.
 const originalStack = new Error().stack

Then later just before this the line where reject(new ArangoError(res)); is called, I do this:
console.error('Original stack', originalStack)

Now, in the console I print the final thrown error in my application, and you can also see the original stack trace in the console.
See how the original stack trace is my application code, and the error thrown by the arango connection library has no context related to my application?

Anyway, I am not sure what to do about this because I am sure the queue is useful, and also creating errors and saving stack traces is expensive and slow... But this makes things very very difficult to debug when the original context of the call is lost when an error is thrown.

That's a general problem with async errors in Node. It looks like Node 12 will bring a new --async-stack-traces option that improves this significantly: http://thecodebarbarian.com/async-stack-traces-in-node-js-12.html

I don't think using --async-stack-traces resolves this issue. I am hitting the same problem on node 12.16.1 with that flag enabled.

v7 now includes an option for precapturing stacktraces on every request. This will have an inevitable performance impact and only works in environments that support Error.captureStackTrace (i.e. V8) but will provide more meaningful stacktraces.


More information - Guidance on HDI Hbase failback process

Need additional guidance on how to failback an Hbase cluster which was originally implemented with Leader-Follower replication.
Scenario
Customer has setup Leader-Follower replication pattern between two regions.
[Cluster1] = Leader in Azure Region 1
[Cluster2] = Follower in Azure Region 2
Region1 goes down which means Cluster1 is unavailable.
How would the following scenarios play out?
**Question 1 ** - does Cluster2 in Region2 automatically assume leader role and starts accepting writes? Or are there additional steps required for it to accept writes when Cluster1 (Leader) is offline/unavailable?
**Question 2 ** - All writes are landing on Cluster2 (Region2), how do we failback to HDI Hbase Region1 (original primary)? Let's say Cluster1 comes back online after a few hours (or days). How would this scenario play out? As a starting point, we had setup replication between cluster1 (leader) and cluster2 (follower) using a script. When cluster1 comes back online, does it impact operations (reads/writes) on Cluster2?
*Question 3 ** - How do we failback to the original setup where Cluster1 is primary and Cluster2 is follower? Please confirm if the steps are correct or is there another more seamless of going back to the original setup.

take an outage on cluster 2 and sync data from cluster2 to cluster1 (original Leader) so that they are in sync.
re-establish replication from cluster1 to cluster2 using script
Cluster1 becomes Leader again and Cluster2 goes to Follower mode?

Question 4 Would it be a fair statement to that failover and failback is comparitively simpler in Leader-Leader model compared to Leader-Follower model?
Thanks,
Amanjeet

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

ID: 9112aca7-92ac-cd06-70a9-47ec5f074eca
Version Independent ID: 9ff5464f-5713-9d7c-1f82-19ea1700e997
Content: HBase cluster replication in virtual networks - Azure HDInsight
Content Source: articles/hdinsight/hbase/apache-hbase-replication.md
Service: hdinsight
GitHub Login: @JasonWHowell
Microsoft Alias: jasonh

Hello @amanjeetsingh
Thanks for the feedback! We are currently investigating and will update you shortly.

@amanjeetsingh It seems that the questions being posed are very detailed and are outside the intended scope of this document and would be better handled in conversation with the product group. I will connect you to a representative via email who may be able to assist with your questions.

#please-close


fix: dev-9142 Fix missing first grid line

This fixes a bug where the first grid line sometimes isn't shown. It happens often with the respiratory virus charts that are currently live. It would be great if this could go out in the September release.
The bug was introduced in this commit which was related to DEV-7953.
Testing Steps
The testposorig.json file attatched to the Jira ticket can be used to see the issue this fixes. Load that file on the dev branch, see that it's broken, then see that this branch fixes it.

I did 1&2, but will let you guys do #4 during the merge. Thank you!


There has no tid in spring cloud gateway response

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ] Question or discussion
[X] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question

What do you want to know?

How to fix it

Bug

Which version of SkyWalking, OS and JRE?

6.4.0 and 6.5.0-SNAPSHOT

Which company or project?

What happen?
If possible, provide a way for reproducing the error. e.g. demo application, component version.

@Component
@Slf4j
public class TestSWTidFilter implements GlobalFilter, Ordered {
@Override
public Mono filter(ServerWebExchange exchange, GatewayFilterChain chain) {
    // here has tid
    log.info("===========================================>in");

    return chain.filter(exchange).then(Mono.fromRunnable(() -> {

        // [TID:N/A]
        log.info("===========================================>out");
    }));
}

@Override
public int getOrder() {
    return Ordered.LOWEST_PRECEDENCE;
}

}
The same as use ServerHttpResponseDecorator

Requirement or improvement

Please describe about your requirements or improvement suggestions.

If that log runs in another thread, in default, yes there is no trace id there. If you want, you need another plugin to propagate context across threads.


[HYDRATOR-1246] Handle null values in date transform

https://issues.cask.co/browse/HYDRATOR-1246

LGTM


invalid

it shows that i have invalid token

me too

Hi,
Activate these in your discord dev portal!


fix: from numpy float to float

To use the library into pipeline I must change the type of elements in mebeddings from numpy.float to float.
related to issue #358

at the moment I can't fix it, I thought it was more immediate, I will work on it as soon as I can

"I put on a colored patch" (we say in Italy)

Changing the backend should do the trick :smiley:

Changing the backend should do the trick :smiley:

I didn't have the courage to touch it from the GitHub online editor. 😅


Remove unused C++ code and classes

There are likely many functions and even classes that are unused. Review which ones are actually used and remove the rest.

So it seems we are in quite good shape then. Let's keep as is except for the small thing in BoundaryConditions.h. @Georspai Please fix and then close this issue.


provide filter for Alternative and Monad?

We can define filter which work on any Alternative and Monad
filter :: ∀ m a. Alternative m => Monad m => (a -> Boolean) -> m a -> m a
filter f m = m >>= \x -> if f x then pure x else empty

I think this repo is best place for it, but i might be wrong.

Sounds useful, but we should consider using MonadZero or MonadPlus. What can you prove about this function given just Alternative and Monad?

Technically we need Plus for empty, Chain for >>= and Applicative for pure
:: ∀ m a. Plus m => Chain m => Applicative m => (a -> Boolean) -> m a -> m a

But if we should use one from MonadZero or MonadPlus I guess MonadZero is just enough.
About proving something don't know, there are cople filter and filterMap related laws  in Filterable. (btw filterMap could be implemented this way too)
I think these are correct assumptions:
(filter g) <<< (filter f) = filter (\x -> f x || g x) -- composition?
(filter f) <<< (filter f) = filter f -- ???
filter (const true) = id -- identity?

You can prove things with just Monad and Alternative; see for example #51.
filter (const true) = identity is fairly easy to establish: we have:
filter (const true) m
= m >>= \x -> if const true x then pure x else empty
= m >>= \x -> pure x
= m >>= pure
= m

I don't think filter g <<< filter f = filter (\x -> f x || g x) holds though. Consider:
filter isOdd (filter isEven (pure 1))
= filter isOdd (pure 1 >>= \x -> if isEven x then pure x else empty)
= filter isOdd (if isEven 1 then pure 1 else empty)
= filter isOdd empty
= empty >>= if isOdd x then pure x else empty
= empty

filter (\x -> isOdd x || isEven x) (pure 1)
= pure 1 >>= \x -> if (isOdd x || isEven x) then pure x else empty
= if (isOdd 1 || isEven 1) then pure 1 else empty
= pure `

However, I'm struggling to think of a concrete type for which this would be useful. For sequence types like List or Array which have a concat-mappy Bind instance, this will do the same as your standard filterA, but with terrible performance. For effect types like Effect or Aff, it's essentially an assertion that the result satisfies the predicate supplied, except that you'll get a useless error message if it doesn't. If that's the kind of thing you want, it would be better to use MonadThrow, I think.
I'm going to close this for now for this reason plus the fact that it hasn't been touched in a long time, but please feel free to comment if I'm missing something.

This might be correct:
-(filter g) <<< (filter f) = filter (\x -> f x || g x)
+(filter g) <<< (filter f) = filter (\x -> f x && g x)

(not posting with intent to reopen this issue tho)

Oh yeah of course, that certainly seems more plausible.


Support for code of meritocracy

Since the other issue was closed, I just wanted to say that I support the adoption of a code of meritocracy.
And kudos to @jart for not caving in to neo-progressivism bullying on the other issue.

Hey, thanks for the great idea. But we're not doing this.

And, just to be clear: I don't believe, and never have believed, in meritocracy. It's a self-serving myth. Open Source software communities are almost always do-ocracies.
https://communitywiki.org/DoOcracy
Under no circumstances am I interested in enshrining the sham concept of meritocracy into the pump.io community or contributor process.


Failing to mount but returning successful

Hi,
I'm currently writing a script to automatically mount Google drive, sync relevant files, and then dismount Google drive (or leaving it mounted if it was already).  I do not like leaving Google drive mounted because it causes the parent folder to load very slowly (and any process which access information of the mounted file system, such as the system monitor), but that could be a separate issue.
The issue here is that I'd like to ensure that google-drive-ocamlfuse has successfully mounted Google drive and to check that, I thought I'd just look at the exit code; however, it sometimes exits with 0 even if it failed to mount Google drive.  In particular, I have noticed this happening if the folder being mounted to is non-empty.
In the mean time, I can parse mount -l to check that it has been mounted, but google-drive-ocamlfuse should probably not exit with 0 if it failed.  This would also allow the use of && and ||.
Cheers

But what I always want to mount it on start up like Dropbox linux client, it also will show the error I guess.
I have a google account that I mounted & that is not empty after syncing now I added google-drive-ocamlfuse ~/gdrive in my start up application but it doesn't mount & when running google-drive-ocamlfuse ~/gdrive it prints this error.
Now if I run command as you mentioned google-drive-ocamlfuse -o ~/gdrive it will hide the files already synced & again download the files I guess.

Sorry, but this is not a sync app like the Dropbox one. When you unmount your Drive, you cannot access your files anymore.

@astrada so do I have to again delete the folder then again using access token again sync all the file

google-drive-ocamlfuse gives you a view of your Drive. It doesn't download your files locally. If you need to copy your remote files you could use rsync from the mountpoint to a local directory. Or you can switch to a sync app (e.g.: https://github.com/Grive/grive).


Rustup 20150203

Simple changes for recent rustc:
Show -> Debug
String -> Display
some #[feature] attributes for unstable APIs

Thanks :+1:


Minor improvements to the changelog

I'm not 100% sure about this change. I was aiming to be consistent with the new features as listed in the 3.0 release which seem to be framed from the point of view of 'things you, the user, can now do' rather than 'things we have done' / 'changes we have made' – i.e. 'you can now add attributes to the date input fieldset' vs 'We have add[ed the] attributes option to the date input fieldset'.
I know you were more involved with the release notes for 3.0, so if you're sure this is the intended format then I'm happy to go with it, but otherwise it'd be good to try and get clarity from @m-green.

Yeah I find the user centred action stuff odd with features since it's more of a 'you can if you want' rather than a 'you should definitely do this'

Yes it's a bit of a difficult fit for new feature headings as Nick says.
The "X now Y" format works in some cases (eg "GDS Transport now falls back to Arial in Internet Explorer 8 (IE8)" example from v3).
Otherwise I tend to use the "You can now..." format, but strip out the actual "You can now" bit. So "~You can now~ Add attributes to table headings"

I'll update with this in mind thanks for the feedback both.


Behaviour difference between Typesafe config and knobs-typesafe with values loaded optionally from environment

In Typesafe config, we can have non-string values read from environment variables defaulting to other values if no environment variable is set:
foo {
  bar = 123
  bar = ${?BAR}
}

When there is no BAR environment variable set, Typesafe config will find 123 for the key foo.bar but in Knobs, knobs.Typesafe.config.run.require[Int]("foo.bar") fails with knobs.KeyError: No such key: foo.bar

This seems to be something else I've messed up, sorry!


Reoder CI commands

This cleans up our feature build ordering:

no features are enabled, everything is built except warden
examples are built with various backends
warden is built with all the backends, which triggers a rebuild of hal due to required serialize feature
test everything
re-test render with mint feature

This is roughly 20% increase on my laptop. Should be harmless.
bors r+


Unable to locate Fall Guys folder in Tracker settings

It doesn't work, when on browser in the tracker settings to locate my Fall guys game folder, an error message is displayed "The path is not of a legal form."

same am on epic


Question for deepqlearn.js

The following is my understanding about the backward function in deepqlearn.js.
If it is in learning process, after one forward path, it begins to do backward propagation. It does SGD with a batch size of N. Those N samples are randomly selecting from replay memory. The code seems to show that the weight matrix of the network is updated N times by calling the backward function once. But in my opinion, the SGD should only update the weight matrix once by averaging all weight updates of a batch size of N.
Please correct me if I have misunderstood sometime.

It works as you expect. Don't confuse two different functions: Brain.backward() and Trainer.train(). The backward function from deepqlearn.js doesn't update the network's weights, it just calls the train function, which does update the weights, but it does so in batch.


:tada: extend VariableMeta by VariablePresentationMeta

Extend class VariableMeta by fields from the proposal.
An example of metadata JSON.
TODO

[ ] migrate existing data pages
[ ] make schema_version smarter, perhaps as a read-only attribute
[ ] (use different schema versions in JSON schema?)
[ ] merge origins and rebase this PR
[ ] remove the example from the cherry blossom dataset

Merging into origins to make my life easier.


unaligned 64-bit atomic operation on i386

Description
I've recently packaged this library for Debian, as it is required to upgrade another library. When the tests were run on a 32bit system (i386), the following panic is reported:
=== RUN   TestConsumerHandlesExpectationsPausingResuming
    consumer.go:284: Expectations set on other/0, but no partition consumer was started.
    consumer.go:284: Expectations set on test/1, but no partition consumer was started.
    consumer.go:284: Expectations set on test/0, but no partition consumer was started.
 I don't know if this affects armel/armhf, or if this is specific to the 32bit i386 architecture.
Logs
Full log available here.
Additional Context

I've taken a quick look for an easy fix like an unaligned struct field, but didn't see anything obvious.

Looking at this… yeah. suppressedHighWaterMarkOffset probably needs to be moved up next to highWaterMarkOffset for the exact same reason.
There’s definitely no reason for it to be listed under the sync.Mutex as it is not being protected by it.

@gibmat thanks for reporting this as similar to #2337 it will effect Fargate too. Have added a fix and a simple lint check using GOARCH=i386 staticcheck which seems to catch it

@gibmat I've pushed out a tagged release to include this fix so that hopefully you can continue your packaging efforts
Version 1.43.2 (2024-04-25)

Awesome, thanks for the quick response! I've just uploaded the latest release to Debian. :smile:


DeepMerge ends up creating attribute values when it shouldn't

Description
When deep merge is run against a node attribute collection, where the destination is missing a key that the source has declared and set to nil, the act of checking for the existence of the key in the destination will cause it to be populated with an empty vividmash, causing the end result to be the empty mash instead of nil.
Here is where VividMash default to an empty mash when being referenced using []
https://github.com/chef/chef/blob/59c6bd77abb071423daea0b62c4d97a54e0aa26a/lib/chef/node/attribute_collections.rb#L168
And here is where deep_merge checks for the key using [] rather than key?:
https://github.com/chef/chef/blob/2e92c709459dffef54f9d671e10ec9a949a94962/lib/chef/mixin/deep_merge.rb#L67
Chef Version
Chef 12 and 13
Replication Case
Can be seen in normal attribute easily, but would repro in default and override during the apply_role_attributes  method instead of consume_attributes
node.normal['cookbook']['predefined-attribute1'] = nil
node.normal['cookbook']['predefined-attribute2'] = nil
node.consume_attributes({ 'cookbook' => { 'fresh-attribute' => nil, 'predefined-attribute2' => nil } })
puts node['cookbook']['fresh-attribute'].inspect
# Result is `{}`. Expecting `nil`
puts node['cookbook']['predefined-attribute1'].inspect
# Result is `nil`. Expecting `nil`
puts node['cookbook']['predefined-attribute2'].inspect
# Result is `nil`. Expecting `nil`

PR would be most appreciated.  higher level functionalish tests of node attribute merging could get dropped somewhere vaguely appropriate in spec/unit/node_spec.rb which would be sufficient testing


warp-client license info

Which Cloudflare product does this pertain to?
WARP Client
Existing documentation URL(s)
https://developers.cloudflare.com/warp-client/
What changes are you suggesting?
I can't find the license information for cloudflare's client software, including the warp desktop client. What license is the software distrubuted as?  The above url is a suggested place to add the info.
Additional information
No more details at this time.

Howdy @xpufx, it sounds like the information you're looking for might be at https://developers.cloudflare.com/warp-client/legal/?


[Dreamcast Arch]: Incorrect sampling rate for Sound IC

The Sound Integrated Circuit or ‘IC’: A set of modules (Synthesiser, DSP and Mixer) that generates the audio signal and applies effects on it. It supports up to 64 PCM channels with a resolution of 16 or 8 bits and a sampling rate of 44.1MHz

A sampling rate in the house of Megahertz seems astronomical. 44.1 KHz would be the correct rate as found in CDs.

I agree, cheers


Refactor distance of time

What does this PR do and why?
This PR is refactoring the use of the rails function distance_of_time_in_words into a viral component time_ago to include an html title attribute of the date the action was performed (created/updated date, etc.), so that the actual date is available for the user upon hovering. The component in conjunction with the existing viral tooltip component will now give users the ability to hover over the time and see the original action date.
Edit 1: I initially implemented this solution with a helper (as suggested in the issues ticket), but that required an .html_safe tag to return the html with erb tags (or require going from helper to .html.erb I believe to avoid this). This partial seemed like a simpler more straightforward solution that should still be usable throughout the website.
Edit 2: I have now changed the partial into its own viral component called time_ago
Screenshots or screen recordings

How to set up and validate locally

Check the following pages and hover over the time ago element to check if the tooltip contains the expected date. Create the associated element if needed (group, project, members, etc.).

Projects and Groups: Dashboard, Group Links, Members
Sample Attachments

PR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

[x] I have evaluated the PR acceptance checklist for this PR.

This is a really good start.  I would like to see the following changes:

Instead of a partial, can you update this to a view component, I think it could even be a viral component.  Using view components is more performant than partials and allows you to display previews in lookbook and testing.
In the viral tooltip component, can you change the surrounding div to a  span.  The div causes a line break on the tables putting the "by" word on it's own line, really because the div is a block element.  I created the component originally and did not think of that.

@joshsadam I've changed it from a partial to a viral component and changed the tooltip div into a span in 85b83c2574b39edd113d5ef9dde7d20dff907c4b

Good job updating it to a view component.  Just a couple of suggestions here.  I also need you to add a LookBook preview and tests.  Start by adding a preview in: test/components/previewsby copying another one like viral_tooltip_component_preview , and then for tests do something like what is in test/components/viral/form/datepicker_component_test.rb, I ned to update some of the other ones as I did not set them up 100% properly.

Previews are added in 2d0ebb4f7a18e83d0a955ab12faa14d6b7f26095
Tests are added in d08f2957ccc5fee26dca667c20948cdc88bea133


[ENH] - Ability to start stopped shared app, by NOT author

Feature description
Imagine two users, Alice and Bob.
Alice creates an app named "Alice in Wonderland" and shares it with Bob. Now when the app is stopped after a while, say by idle culling and Bob access that app, he can't use the app as it's stopped.
We need the ability to start the app "Alice in Wonderland" by Bob.
The assumption is Bob has sufficient permissions in JupyterHub to start the app (otherwise 403).
Value and/or benefit
Following problems will be solved:

The problem of keeping the app always alive (causing cost) will be solved.
The problem of being able to access a stopped app, when the original author is not available.

Anything else?
No response

The assumption is Bob has sufficient permissions in JupyterHub to start the app (otherwise 403).

What roles are required for "sufficient permissions"?

What roles are required for "sufficient permissions"?

We need a custom role with scope "servers" (this can be limited by servers of a user or group as well) for the user to have permissions to start the app.

@aktech This is only for Starting an app correct? A shared user still cannot Stop an app?

@aktech This is only for Starting an app correct? A shared user still cannot Stop an app?

Technically yes, but not enabled by backend at the moment, but I would say to frontend should make an API call to stop (just like other stop app call) and if the response is 4xx then message user, you don't have permissions to stop.
So that if we enable stopping shared app in future then it would work right away without any frontend changes.


Calibrate visit uncertainty floor

Previously, I used a relation from Nidever that depended on S/N. Since the RV pipeline has changed significantly, we will need to re-calibrate this. One idea is to use the Gaia-inferred semi-amplitudes from https://github.com/dfm/one-datum to identify low-amplitude RV variables and use those to infer the noise floor.

I went with self-calibration -- see the model in https://github.com/adrn/APOGEE-DR17-binaries/blob/main/notebooks/Visit-error-calibrate.ipynb !

TODO: see whether we need to build a dependence on VSINI into the model

It improves it! Closing this because I think I've settled on a calibration model that I like


#86dtu93df - Include how to write token contracts (NEP-17) to the doc…

Summary or solution description
Adds instructions on how to create a NEP-17 contract to the getting started documentation

Task linked: CU-86dtu93df Include how to write token contracts (NEP-17) to the documentation


[BACKPORT-1.3][FLINK-7268] [checkpoints] Scope SharedStateRegistry objects

See #4410 . This is a bugfix backport from 1.4 to 1.3.x .

CC @aljoscha

Forgot to mention, good to merge, modulo the nitpicks and the additional commit that introduces the delaying Executor.

Thanks a lot for the review @aljoscha ! Merging to 1.3 ...


Always call debug_core_start when attaching

Always call debug_core_start when attaching. This ensures that the debug mode is always activated when a Session is created, regardless of the attach method.
The reset_and_halt function now doesn't  call the debug_core_start function anymore, which fixes #324 .
Tested with a board which requires attach under reset, and a board which does not require it.

Thanks a lot!


Can't set SUBUTAI_DISK more than 100 GB

User configuraration parameter(vagrant-subutai.yml):
SUBUTAI_ENV: master
DISK_SIZE: 200

I did following commands:
vagrant init subutai/stretch-master
vagrant up

I got following errors:
==> default: Disk size configured to 200GB, increasing 100GB default by 100GB.
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Cloning VM...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'subutai/stretch-master' is up to date...
==> default: A newer version of the box 'subutai/stretch-master' for provider 'virtualbox' is
==> default: available! You currently have version '0'. The latest is version
==> default: '7.0.5'. Run `vagrant box update` to update.
==> default: Setting the name of the VM: virtualbox_default_1535694236659_48847
==> default: Fixed port collision for 22 => 2222. Now on port 2201.
==> default: Clearing any previously set network interfaces...
==> default: Available bridged network interfaces:
1) br1
2) enp4s0
3) vptp1
4) vptp0
5) enp3s0
6) vmnet1
7) vmnet8
8) vptp2
==> default: When choosing an interface, it is usually the one that is
==> default: being used to connect to the internet.
    default: Which interface should the network bridge to? 1
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: bridged
==> default: Forwarding ports...
    default: 8443 (guest) => 10001 (host) (adapter 1)
    default: 22 (guest) => 2201 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: <IP_ADDRESS>:2201
    default: SSH username: subutai
    default: SSH auth method: private key
    default: Warning: Connection reset. Retrying...
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
[default] No installation found.
Reading package lists...
Building dependency tree...
Reading state information...
dkms is already the newest version (2.3-2).
dkms set to manually installed.
linux-headers-4.9.0-8-amd64 is already the newest version (4.9.110-3+deb9u4).
linux-headers-4.9.0-8-amd64 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Copy iso file /usr/share/virtualbox/VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
Mounting Virtualbox Guest Additions ISO to: /mnt
mount: /dev/loop0 is write-protected, mounting read-only
Installing Virtualbox Guest Additions 5.2.8 - guest version is unknown
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.2.8 Guest Additions for Linux........
VirtualBox Guest Additions installer
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules.
VirtualBox Guest Additions: Starting.
Unmounting Virtualbox Guest Additions ISO from: /mnt
==> default: Checking for guest additions in VM...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
    default: /vagrant => /home/adilet/peer/virtualbox
==> default: Running provisioner: shell...
    default: Running: /tmp/vagrant-shell20180831-16867-1uq55e2.sh
    default: Added new virtual disk /dev/sdb
    default: The ZFS modules are not loaded.
    default: Try running '/sbin/modprobe zfs' as root to load them.
    default: The ZFS modules are not loaded.
    default: Try running '/sbin/modprobe zfs' as root to load them.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Followed the commands from above and successfully created VMs (two times):


Update Makefile to support docker build

I've since updated the Makefile on the asciidoc branch such that this change is no longer required.


SCCM CML License

Hello, We have a SCCM CML License and need clarification if this includes the use of a SQL Server License as stated in the FAQ??

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

ID: c3b9a7fa-9585-a2fb-590e-0b74e128035d
Version Independent ID: 9aae8e97-de68-c274-b4c6-cd925568c75b
Content: Product and Licensing FAQ - Configuration Manager
Content Source: sccm/core/understand/product-and-licensing-faq.md
Product: configuration-manager
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Thanks @TomGreenham for the question. If you're a volume license customer, if you can view/access SQL in the Volume License Service Center, then most likely it's included with your license.
Also, refer to the product terms as referenced at the top of this article.
In general, work with your Microsoft account executive for licensing questions. I'm going to close this issue as I don't see anything directly actionable for this article at this time. Please reopen the issue if you disagree.


Creating a LSI with the primary key

Description
Hello,
Since the GraphQL transformer V2 I'm not sure exactly how I'm supposed to create a LSI to achieve this:

I switched in cli.json "secondarykeyasgsi"*** to false and my graphql.schema file is like this:
hashKey: Int! @primaryKey(sortKeyFields: ["rangeKey"]) @index(name: "geohash-index", sortKeyFields: ["geohash"], queryField: "<model>ByGeohash")
geohash: Int!

When I execute
amplify push --yes --allow-destructive-graphql-schema-updates
I get the following error and I must delete "deployment-state.json" from the S3 deployment bucket or I can't push anymore at all.

Can you please help me?
*** It is not possible to have both GSI and LSI ?
Categories

[ ] Analytics
[ ] API (REST)
[X] API (GraphQL)
[ ] Auth
[ ] Authenticator
[ ] DataStore
[ ] Storage

Steps to Reproduce
No response
Screenshots
No response
Platforms

[ ] iOS
[ ] Android

Android Device/Emulator API Level
No response
Environment
N/A

Dependencies
N/A

Device
N/A
OS
N/A
CLI Version
8.2.0
Additional Context
No response

Ok this is weird: I recreated a new amplify project with the following schema and I get my LSI with the PK as expected:
type Test @model {
  hashKey: Int! @primaryKey(sortKeyFields: ["rangeKey"]) @index(name: "geohash-index", sortKeyFields: ["geohash"])
  geohash: Int!
  rangeKey: String!
}

I think the issue is coming from the fact that I have another table with two GSI already and switching "secondarykeyasgsi" to false breaks the push feature.
Is there a way to specify the type of an index out of cli.json?


[Snyk] Upgrade typescript from 5.5.4 to 5.6.2

Snyk has created this PR to upgrade typescript from 5.5.4 to 5.6.2.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 80 versions ahead of your current version.

The recommended version was released on 22 days ago.

Release notes

Package name: typescript

5.6.2 - 2024-09-09For release notes, check out the release announcement.
For the complete list of fixed issues, check out the

fixed issues query for Typescript 5.6.0 (Beta).
fixed issues query for Typescript 5.6.1 (RC).
fixed issues query for Typescript 5.6.2 (Stable).

Downloads are available on:

npm
NuGet package

5.6.1-rc - 2024-08-23

5.6.0-dev.20240819 - 2024-08-19

5.6.0-dev.20240818 - 2024-08-18

5.6.0-dev.20240817 - 2024-08-17

5.6.0-dev.20240816 - 2024-08-16

5.6.0-dev.20240815 - 2024-08-15

5.6.0-dev.20240814 - 2024-08-14

5.6.0-dev.20240813 - 2024-08-13

5.6.0-dev.20240812 - 2024-08-12

5.6.0-dev.20240811 - 2024-08-11

5.6.0-dev.20240810 - 2024-08-10

5.6.0-dev.20240809 - 2024-08-09

5.6.0-dev.20240808 - 2024-08-08

5.6.0-dev.20240807 - 2024-08-07

5.6.0-dev.20240806 - 2024-08-06

5.6.0-dev.20240805 - 2024-08-05

5.6.0-dev.20240804 - 2024-08-04

5.6.0-dev.20240803 - 2024-08-03

5.6.0-dev.20240802 - 2024-08-02

5.6.0-dev.20240801 - 2024-08-01

5.6.0-dev.20240731 - 2024-07-31

5.6.0-dev.20240730 - 2024-07-30

5.6.0-dev.20240729 - 2024-07-29

5.6.0-dev.20240728 - 2024-07-28

5.6.0-dev.20240727 - 2024-07-27

5.6.0-dev.20240726 - 2024-07-26

5.6.0-dev.20240725 - 2024-07-25

5.6.0-dev.20240724 - 2024-07-24

5.6.0-dev.20240723 - 2024-07-23

5.6.0-dev.20240722 - 2024-07-22

5.6.0-dev.20240721 - 2024-07-21

5.6.0-dev.20240720 - 2024-07-20

5.6.0-dev.20240719 - 2024-07-19

5.6.0-dev.20240718 - 2024-07-18

5.6.0-dev.20240717 - 2024-07-17

5.6.0-dev.20240716 - 2024-07-16

5.6.0-dev.20240715 - 2024-07-15

5.6.0-dev.20240714 - 2024-07-14

5.6.0-dev.20240713 - 2024-07-13

5.6.0-dev.20240712 - 2024-07-12

5.6.0-dev.20240711 - 2024-07-11

5.6.0-dev.20240710 - 2024-07-10

5.6.0-dev.20240709 - 2024-07-09

5.6.0-dev.20240708 - 2024-07-08

5.6.0-dev.20240707 - 2024-07-07

5.6.0-dev.20240706 - 2024-07-06

5.6.0-dev.20240705 - 2024-07-05

5.6.0-dev.20240704 - 2024-07-04

5.6.0-dev.20240703 - 2024-07-03

5.6.0-dev.20240702 - 2024-07-02

5.6.0-dev.20240701 - 2024-07-01

5.6.0-dev.20240630 - 2024-06-30

5.6.0-dev.20240629 - 2024-06-29

5.6.0-dev.20240628 - 2024-06-28

5.6.0-dev.20240627 - 2024-06-27

5.6.0-dev.20240626 - 2024-06-26

5.6.0-dev.20240625 - 2024-06-25

5.6.0-dev.20240624 - 2024-06-24

5.6.0-dev.20240623 - 2024-06-23

5.6.0-dev.20240622 - 2024-06-22

5.6.0-dev.20240621 - 2024-06-21

5.6.0-dev.20240620 - 2024-06-20

5.6.0-dev.20240619 - 2024-06-19

5.6.0-dev.20240618 - 2024-06-18

5.6.0-dev.20240617 - 2024-06-17

5.6.0-dev.20240616 - 2024-06-16

5.6.0-dev.20240615 - 2024-06-15

5.6.0-dev.20240614 - 2024-06-14

5.6.0-dev.20240613 - 2024-06-13

5.6.0-dev.20240612 - 2024-06-12

5.6.0-dev.20240611 - 2024-06-11

5.6.0-dev.20240610 - 2024-06-10

5.6.0-dev.20240609 - 2024-06-09

5.6.0-dev.20240608 - 2024-06-08

5.6.0-dev.20240607 - 2024-06-07

5.6.0-dev.20240606 - 2024-06-06

5.6.0-dev.20240605 - 2024-06-05

5.6.0-dev.20240604 - 2024-06-04

5.6.0-beta - 2024-07-26

5.5.4 - 2024-07-22For release notes, check out the release announcement.
For the complete list of fixed issues, check out the

fixed issues query for TypeScript v5.5.4 (Stable).
fixed issues query for TypeScript v5.5.3 (Stable).
fixed issues query for TypeScript v5.5.2 (Stable).
fixed issues query for TypeScript v5.5.1 (RC).
fixed issues query for TypeScript v5.5.0 (Beta).

Downloads are available on:

npm
NuGet package (soon!)

    from typescript GitHub release notes

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
📜 Customise PR templates
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Dupe of #169