Added walls to environment disappear in training

hi,
i build a custom env ( https://github.com/flobotics/brax/blob/main/brax/envs/simtoreal.py ) , which is mostly the reacher with walls around it. If i use html.render() it shows everything, but when i then go on with training and then look at the trajectory output, The walls start to sink into the ground and disappear ? I want to use the walls to let the target bounce off the walls , but if they are not there ?  What do i wrong ?
Here a images of the start of the trajectory video output:

Then it disappears

till its complety gone

adding frozen { all: true } to the wall bodies and they do not disappear anymore.  But when i now remove frozen { all: true } from the target-sphere-body,  so that the target-sphere-body can move around inside the walls, the target-sphere-body disappears in the trajectory-video-output ?
How can i use a sphere as a ball, jumping around and so ?

i found that the ball is falling through the ground/plane at the beginnng of the trajectory video output ? I included
collide_include {
    first: "ground"
    second: "ball"
}
collide_include {
    first: "ball"
    second: "ground"
}

But it still falls through ground ? How can i prevent that ?

Hello!  I think you have found a bug where brax doesn’t properly register the sphere collider.  As a workaround until we put in the proper fix, Can you try turning the ball into a sphere-shaped capsule where the length is double the radius?  See the Object body in grasp.py for an example.

turning the ball from sphere into capsule like you said works, the ball bounces off the ground and rolls to the middle.
Perhaps the next bug is, that it seemed that all bodies or joints depend on ground-joint. I cannot describe it good, but if i lower only the parent_offset z value of the ground-arm_0-joint from 0.1 to 0.01 you see that also the walls and the new capsule-ball get lowered too, and sink into the ground ? But i only wanted to lower-down the arm_0 and arm_1 ?

cc @cdfreeman-google
Good timing for pointing this out.  Configs are missing an important piece of information which is to specify an initial offset for an unparented (is not the child of a joint) body.  Right now the system "guesses" where to put these unparented bodies and in your case, the guess is incorrect.
We are adding this new config now and will let you know when it's ready.  After it's done, you'll be able to specify different offsets for your walls vs the ball and arms, to put everything in its right place.

i turned the boxes into capsule for the arms, but now the ball hits the ground, then rolls into the middle of the plane and then at the end one arm seemed to kick the ball out of the arena ?
Why are the arms not all the time hit the ball ?
A gif to watch is here: https://github.com/flobotics/brax/blob/main/out.gif

fyi, you can now specify initial positions for bodies in Brax, see for example this test:
https://github.com/google/brax/blob/main/brax/tests/physics_test.py#L128
Closing this issue, but please reach out if more problems remain.


Error Using pip install dslogparser

I seem to be able to import other packages from pip and I even attempted using the straight .tar.gz file for this but I am getting the following error:
(base) C:\Users\warre\Anaconda3\Scripts>pip install dslogparser
Collecting dslogparser
Using cached dslogparser-1.0.2.tar.gz (6.2 kB)
ERROR: Command errored out with exit status 1:
command: 'c:\users\warre\anaconda3\python.exe' -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\Users\warre\AppData\Local\Temp\pip-install-is7sibmd\dslogparser\setup.py'"'"'; file='"'"'C:\Users\warre\AppData\Local\Temp\pip-install-is7sibmd\dslogparser\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' egg_info --egg-base 'C:\Users\warre\AppData\Local\Temp\pip-install-is7sibmd\dslogparser\pip-egg-info'
cwd: C:\Users\warre\AppData\Local\Temp\pip-install-is7sibmd\dslogparser
Complete output (5 lines):
Traceback (most recent call last):
File "", line 1, in
File "C:\Users\warre\AppData\Local\Temp\pip-install-is7sibmd\dslogparser\setup.py", line 43, in
with open(join(setup_dir, 'README-dslogparser.md'), encoding='utf-8') as f:
FileNotFoundError: [Errno 2] No such file or directory: 'C:\Users\warre\AppData\Local\Temp\pip-install-is7sibmd\dslogparser\README-dslogparser.md'
----------------------------------------
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
Is there a setup tool issue here?
Update:
I was able to clone this code and create my own wheel:
python setup.py bdist_wheel
cd dist
pip install *whl

i will try to take a look at this tomorrow.

I got the same problem when I uninstalled and then reinstalled. Looking...

I think this is fixed with version 1.0.3 (just uploaded).
Justin: I created 2 README files because "README.md" is displayed by Github and holds both a description and historic notes. However, using that file for the PyPi package description seemed wrong, too wordy. So I created "README-dslogparser.md" to provide a more concise and readable PyPi description, but missed loading it into the package. If you have a different suggestion on how to organize this, I am happy to hear.

nah, dont want to complicate it. it looks good to me :-)


HDFS-15098. Add SM4 encryption method for HDFS

SM4 (formerly SMS4)is a block cipher used in the Chinese National Standard for
Wireless LAN WAPI (Wired Authentication and Privacy Infrastructure).
SM4 was a cipher proposed to for the IEEE 802.11i standard, but has so far been
rejected by ISO. One of the reasons for the rejection has been opposition to
the WAPI fast-track proposal by the IEEE. please see:
https://en.wikipedia.org/wiki/SM4_(cipher)

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 40s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
markdownlint
0m  1s
markdownlint was not available.

+0 :ok:
buf
0m  1s
buf 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 3 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
3m 25s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
33m 29s
trunk passed

+1 :green_heart:
compile
26m 37s
trunk passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
compile
21m 54s
trunk passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

+1 :green_heart:
checkstyle
3m 41s
trunk passed

+1 :green_heart:
mvnsite
4m 38s
trunk passed

+1 :green_heart:
shadedclient
23m  7s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
2m  0s
trunk passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
javadoc
3m 58s
trunk passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

+0 :ok:
spotbugs
2m 56s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
8m 17s
trunk passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 29s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 59s
the patch passed

+1 :green_heart:
compile
23m 56s
the patch passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

-1 :x:
cc
23m 56s
root-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 generated 17 new + 145 unchanged - 17 fixed = 162 total (was 162)

+1 :green_heart:
golang
23m 56s
the patch passed

-1 :x:
javac
23m 56s
root-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 generated 4 new + 2049 unchanged - 0 fixed = 2053 total (was 2049)

+1 :green_heart:
compile
19m 17s
the patch passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

-1 :x:
cc
19m 17s
root-jdkPrivateBuild-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01 with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01 generated 28 new + 134 unchanged - 28 fixed = 162 total (was 162)

+1 :green_heart:
golang
19m 17s
the patch passed

-1 :x:
javac
19m 17s
root-jdkPrivateBuild-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01 with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01 generated 4 new + 1944 unchanged - 0 fixed = 1948 total (was 1944)

-0 :warning:
checkstyle
2m 59s
root: The patch generated 3 new + 211 unchanged - 8 fixed = 214 total (was 219)

+1 :green_heart:
mvnsite
4m  5s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  3s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
15m 25s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
2m  9s
the patch passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
javadoc
3m 56s
the patch passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

+1 :green_heart:
findbugs
9m 24s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
10m 34s
hadoop-common in the patch passed.

+1 :green_heart:
unit
2m 28s
hadoop-hdfs-client in the patch passed.

-1 :x:
unit
127m  9s
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
1m  1s
The patch does not generate ASF License warnings.

355m  0s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestDFSStripedOutputStreamWithFailure

hadoop.hdfs.tools.TestViewFileSystemOverloadSchemeWithDFSAdmin

hadoop.hdfs.client.impl.TestBlockReaderLocal

hadoop.hdfs.TestFileChecksumCompositeCrc

hadoop.hdfs.TestDecommissionWithStripedBackoffMonitor

hadoop.hdfs.server.namenode.TestNameNodeRetryCacheMetrics

hadoop.hdfs.server.namenode.ha.TestPipelinesFailover

hadoop.hdfs.TestDFSUpgradeFromImage

hadoop.hdfs.server.namenode.TestAddOverReplicatedStripedBlocks

hadoop.hdfs.server.blockmanagement.TestSequentialBlockGroupId

hadoop.hdfs.server.blockmanagement.TestBlockTokenWithDFSStriped

hadoop.hdfs.qjournal.client.TestQJMWithFaults

hadoop.hdfs.TestReconstructStripedFileWithRandomECPolicy

hadoop.hdfs.server.blockmanagement.TestUnderReplicatedBlocks

hadoop.fs.contract.hdfs.TestHDFSContractMultipartUploader

hadoop.hdfs.TestSafeModeWithStripedFileWithRandomECPolicy

hadoop.hdfs.server.namenode.TestDecommissioningStatus

hadoop.hdfs.TestErasureCodingPolicies

hadoop.hdfs.tools.TestECAdmin

hadoop.hdfs.server.sps.TestExternalStoragePolicySatisfier

hadoop.hdfs.web.TestWebHdfsWithMultipleNameNodes

hadoop.hdfs.TestMiniDFSCluster

hadoop.hdfs.TestFileChecksum

hadoop.hdfs.server.balancer.TestBalancer

hadoop.hdfs.TestDFSStripedOutputStreamWithFailureWithRandomECPolicy

hadoop.hdfs.server.blockmanagement.TestBlocksWithNotEnoughRacks

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml findbugs checkstyle cc golang markdownlint buflint bufcompat

uname
Linux 28bfcd3c87ac 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 7938ebfb9dd

Default Java
Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

cc
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/1/artifact/out/diff-compile-cc-root-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.txt

javac
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/1/artifact/out/diff-compile-javac-root-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.txt

cc
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/1/artifact/out/diff-compile-cc-root-jdkPrivateBuild-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01.txt

javac
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/1/artifact/out/diff-compile-javac-root-jdkPrivateBuild-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01.txt

checkstyle
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/1/artifact/out/diff-checkstyle-root.txt

unit
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/1/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt

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

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

modules
C: hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs-client hadoop-hdfs-project/hadoop-hdfs U: .

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

versions
git=2.17.1 maven=3.6.0 findbugs=4.0.6

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  0s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
markdownlint
0m  1s
markdownlint was not available.

+0 :ok:
buf
0m  1s
buf 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 3 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
3m 17s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
28m 14s
trunk passed

+1 :green_heart:
compile
20m 56s
trunk passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
compile
17m 39s
trunk passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

+1 :green_heart:
checkstyle
2m 55s
trunk passed

+1 :green_heart:
mvnsite
3m 46s
trunk passed

+1 :green_heart:
shadedclient
22m 35s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
2m  8s
trunk passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
javadoc
3m 32s
trunk passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

+0 :ok:
spotbugs
2m 40s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
8m  3s
trunk passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 22s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 46s
the patch passed

+1 :green_heart:
compile
20m 51s
the patch passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

-1 :x:
cc
20m 51s
root-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 generated 33 new + 129 unchanged - 33 fixed = 162 total (was 162)

+1 :green_heart:
golang
20m 51s
the patch passed

-1 :x:
javac
20m 51s
root-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 generated 4 new + 2049 unchanged - 0 fixed = 2053 total (was 2049)

+1 :green_heart:
compile
18m 28s
the patch passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

-1 :x:
cc
18m 28s
root-jdkPrivateBuild-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01 with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01 generated 31 new + 131 unchanged - 31 fixed = 162 total (was 162)

+1 :green_heart:
golang
18m 28s
the patch passed

-1 :x:
javac
18m 28s
root-jdkPrivateBuild-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01 with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01 generated 4 new + 1944 unchanged - 0 fixed = 1948 total (was 1944)

-0 :warning:
checkstyle
3m  7s
root: The patch generated 3 new + 211 unchanged - 8 fixed = 214 total (was 219)

+1 :green_heart:
mvnsite
3m 50s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  3s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
15m 32s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
2m  6s
the patch passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
javadoc
3m 40s
the patch passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

+1 :green_heart:
findbugs
8m 27s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
9m 30s
hadoop-common in the patch passed.

+1 :green_heart:
unit
2m  9s
hadoop-hdfs-client in the patch passed.

-1 :x:
unit
109m  7s
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 53s
The patch does not generate ASF License warnings.

313m  5s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.namenode.TestCacheDirectives

hadoop.hdfs.TestStripedFileAppend

hadoop.hdfs.server.blockmanagement.TestBlockTokenWithDFSStriped

hadoop.fs.contract.hdfs.TestHDFSContractMultipartUploader

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml findbugs checkstyle cc golang markdownlint buflint bufcompat

uname
Linux d1474fc1dc87 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / e592ec5f8bf

Default Java
Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

cc
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/2/artifact/out/diff-compile-cc-root-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.txt

javac
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/2/artifact/out/diff-compile-javac-root-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.txt

cc
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/2/artifact/out/diff-compile-cc-root-jdkPrivateBuild-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01.txt

javac
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/2/artifact/out/diff-compile-javac-root-jdkPrivateBuild-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01.txt

checkstyle
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/2/artifact/out/diff-checkstyle-root.txt

unit
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/2/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt

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

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

modules
C: hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs-client hadoop-hdfs-project/hadoop-hdfs U: .

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

versions
git=2.17.1 maven=3.6.0 findbugs=4.0.6

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 54s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
markdownlint
0m  1s
markdownlint was not available.

+0 :ok:
buf
0m  1s
buf 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 4 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
3m 18s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
29m  4s
trunk passed

+1 :green_heart:
compile
24m  1s
trunk passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
compile
21m 56s
trunk passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

+1 :green_heart:
checkstyle
3m 53s
trunk passed

+1 :green_heart:
mvnsite
4m 14s
trunk passed

+1 :green_heart:
shadedclient
24m  3s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
2m 14s
trunk passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
javadoc
3m 39s
trunk passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

+0 :ok:
spotbugs
2m 41s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
8m 15s
trunk passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 27s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 58s
the patch passed

+1 :green_heart:
compile
21m 58s
the patch passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

-1 :x:
cc
21m 58s
root-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 generated 26 new + 137 unchanged - 26 fixed = 163 total (was 163)

+1 :green_heart:
golang
21m 58s
the patch passed

+1 :green_heart:
javac
21m 58s
root-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 generated 0 new + 2049 unchanged - 4 fixed = 2049 total (was 2053)

+1 :green_heart:
compile
18m 54s
the patch passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

-1 :x:
cc
18m 54s
root-jdkPrivateBuild-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01 with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01 generated 29 new + 134 unchanged - 29 fixed = 163 total (was 163)

+1 :green_heart:
golang
18m 54s
the patch passed

+1 :green_heart:
javac
18m 54s
root-jdkPrivateBuild-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01 with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01 generated 0 new + 1944 unchanged - 4 fixed = 1944 total (was 1948)

-0 :warning:
checkstyle
2m 49s
root: The patch generated 3 new + 212 unchanged - 8 fixed = 215 total (was 220)

+1 :green_heart:
mvnsite
3m 51s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  3s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
15m 38s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
2m  9s
the patch passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
javadoc
3m 38s
the patch passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

-1 :x:
findbugs
2m 34s
hadoop-common-project/hadoop-common generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

_ Other Tests _

+1 :green_heart:
unit
9m 53s
hadoop-common in the patch passed.

+1 :green_heart:
unit
2m 10s
hadoop-hdfs-client in the patch passed.

-1 :x:
unit
131m  7s
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
1m 26s
The patch does not generate ASF License warnings.

349m  0s

Reason
Tests

FindBugs
module:hadoop-common-project/hadoop-common

Return value of getCipherSuite() ignored, but method has no side effect  At JceSm4CtrCryptoCodec.java:but method has no side effect  At JceSm4CtrCryptoCodec.java:[line 51]

Failed junit tests
hadoop.hdfs.server.sps.TestExternalStoragePolicySatisfier

hadoop.hdfs.TestFileChecksumCompositeCrc

hadoop.hdfs.server.blockmanagement.TestBlockTokenWithDFSStriped

hadoop.hdfs.server.namenode.TestNameNodeRetryCacheMetrics

hadoop.hdfs.TestFileChecksum

hadoop.fs.contract.hdfs.TestHDFSContractMultipartUploader

hadoop.hdfs.server.namenode.ha.TestHAAppend

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml findbugs checkstyle cc golang markdownlint buflint bufcompat

uname
Linux 0ea0f5150711 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / d1c60a53f60

Default Java
Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

cc
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/4/artifact/out/diff-compile-cc-root-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.txt

cc
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/4/artifact/out/diff-compile-cc-root-jdkPrivateBuild-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01.txt

checkstyle
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/4/artifact/out/diff-checkstyle-root.txt

findbugs
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/4/artifact/out/new-findbugs-hadoop-common-project_hadoop-common.html

unit
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/4/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt

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

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

modules
C: hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs-client hadoop-hdfs-project/hadoop-hdfs U: .

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

versions
git=2.17.1 maven=3.6.0 findbugs=4.0.6

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
42m  2s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
markdownlint
0m  1s
markdownlint was not available.

+0 :ok:
buf
0m  1s
buf was not available.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  1s
The patch appears to include 4 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
3m 28s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
36m 31s
trunk passed

+1 :green_heart:
compile
28m 54s
trunk passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
compile
24m 33s
trunk passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

+1 :green_heart:
checkstyle
4m  3s
trunk passed

+1 :green_heart:
mvnsite
4m 51s
trunk passed

+1 :green_heart:
shadedclient
29m  6s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
2m 44s
trunk passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
javadoc
4m 36s
trunk passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

+0 :ok:
spotbugs
3m 35s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
10m 56s
trunk passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 33s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 43s
the patch passed

+1 :green_heart:
compile
28m 21s
the patch passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

-1 :x:
cc
28m 21s
root-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 generated 15 new + 148 unchanged - 15 fixed = 163 total (was 163)

+1 :green_heart:
golang
28m 21s
the patch passed

-1 :x:
javac
28m 21s
root-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 generated 1 new + 2053 unchanged - 4 fixed = 2054 total (was 2057)

+1 :green_heart:
compile
24m 21s
the patch passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

-1 :x:
cc
24m 21s
root-jdkPrivateBuild-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01 with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01 generated 12 new + 151 unchanged - 12 fixed = 163 total (was 163)

+1 :green_heart:
golang
24m 21s
the patch passed

+1 :green_heart:
javac
24m 21s
root-jdkPrivateBuild-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01 with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01 generated 0 new + 1947 unchanged - 3 fixed = 1947 total (was 1950)

-0 :warning:
checkstyle
4m  4s
root: The patch generated 3 new + 213 unchanged - 8 fixed = 216 total (was 221)

+1 :green_heart:
mvnsite
4m 46s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  4s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
19m 35s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
2m 39s
the patch passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
javadoc
4m 32s
the patch passed with JDK Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

+1 :green_heart:
findbugs
11m 38s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
11m 28s
hadoop-common in the patch passed.

+1 :green_heart:
unit
2m 37s
hadoop-hdfs-client in the patch passed.

-1 :x:
unit
131m 59s
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
1m 16s
The patch does not generate ASF License warnings.

440m 24s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.sps.TestExternalStoragePolicySatisfier

hadoop.fs.contract.hdfs.TestHDFSContractMultipartUploader

hadoop.hdfs.TestFileChecksumCompositeCrc

hadoop.hdfs.server.namenode.TestAddStripedBlockInFBR

hadoop.hdfs.server.balancer.TestBalancer

hadoop.hdfs.server.datanode.TestDataNodeMetrics

hadoop.hdfs.TestFileChecksum

hadoop.hdfs.server.blockmanagement.TestBlockTokenWithDFSStriped

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/5/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml findbugs checkstyle cc golang markdownlint buflint bufcompat

uname
Linux 1743b6b7bbbe 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 06793da1001

Default Java
Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01

cc
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/5/artifact/out/diff-compile-cc-root-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.txt

javac
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/5/artifact/out/diff-compile-javac-root-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.txt

cc
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/5/artifact/out/diff-compile-cc-root-jdkPrivateBuild-1.8.0_265-8u265-b01-0ubuntu2~18.04-b01.txt

checkstyle
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/5/artifact/out/diff-checkstyle-root.txt

unit
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/5/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/5/testReport/

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

modules
C: hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs-client hadoop-hdfs-project/hadoop-hdfs U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2211/5/console

versions
git=2.17.1 maven=3.6.0 findbugs=4.0.6

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

This message was automatically generated.

the patch in JIRA issue has been merged, abandon this.


Footer Section UI improvement

I would like to improve the frontend aesthetics of the footer section. Please assign me this issue, i would like to work on it.
@vishanurag

assign me this , i already solved similar problems.

okay thank you


Add osx-specific setting for downmixing test

The AudioUnit allows us to set the layout containing other channels that the output device can not provide. For example, setting 3F2-LFE layout to a stereo device is fine. When the audio is played, those channels beyond stereo(Center, LFE, Left Surround, Right Surround) will be dropped.
To keep all the information, we need to mix those audio data before it's dropped. That's what we do in #234. We mix the audio before it's played and dropped. In above case, we mixed the audio in Center, LFE, Left Surround, Right Surround into Left and Right channels before playing, while other channels are not be changed. That is,
+----+----+----+------+-----+-----+----+----+----+------+-----+-----+
| L0 | R0 | C0 | LFE0 | LS0 | RS0 | L1 | R1 | C1 | LFE1 | LS1 | RS1 | ......
+----+----+----+------+-----+-----+----+----+----+------+-----+-----+

   | Downmix
   v

+----+----+---+---+---+---+----+----+---+---+---+---+
| l0 | r0 | x | x | x | x | l1 | r1 | x | x | x | x | ...
+----+----+---+---+---+---+----+----+---+---+---+---+
            ^   ^   ^   ^             ^   ^   ^   ^
           will be dropped            will be dropped
where
l0 = L0+ 0.707*(C0 + LS0)
r0 = R0+ 0.707*(C0 + RS0)

l1 = L1+ 0.707*(C1 + LS1)
r1 = R1+ 0.707*(C1 + RS1)
...

Please see the following discussions for more details:

https://github.com/kinetiknz/cubeb/pull/234#issuecomment-283855601
https://github.com/kinetiknz/cubeb/pull/234#issuecomment-283858288
https://github.com/kinetiknz/cubeb/pull/234#issuecomment-283881631

However, we do not add the corresponding changes in test_mixer.cpp, so the invalid address beyond the array buffer can provide will be used and cause errors. That's the cause for #305.

Thanks for the explanation and fixes!


Exception in /lib/common.js missing stream module?

The line:
var Transform    = require('stream').Transform;
is returning undefined.
....
...
The following line thus throws an exception
// Inherit from Transform
ParserStream.prototype = Object.create(Transform.prototype);
.....
ERROR thrown:
common.js:9 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'prototype')

See tests. Those are ok.

What tests are you referring to? I'm trying to utlize this package and it just crashes because it's undefined.

https://github.com/nodeca/probe-image-size/tree/master/test

Hi Team,
Did you manage to resolve this issue?


How to detect Web Weixin status when trying to remark a contact

Run npm run doctor or wechaty run doctor(for docker user), paste output here
><EMAIL_ADDRESS>doctor /Users/lijiarui/Documents/git/wechaty
> ts-node bin/doctor

#### Wechaty Doctor

1. Wechaty version: #git[2834b0a 0.6.35]
2. Darwin x64 version 14.5.0 memory 6683/16384 MB
3. Docker: false
4. Node version: v7.0.0

Expected behavior
When trying to modify a contact's remark, sometimes it failed and sometimes it succeed.
I found it depends on web Wei Xin:

If failed,web Wei Xin reply two wxoplog with "Ret": 1205.
If success, web Wei Xin reply a webwxsync XHR and two webwxoplog XHR with "Ret": 0.

But now wechaty cannot detect the 2 different statuses, so could wechaty return a web Weixin status when trying to remark a contact, it will really help!
PS: the background as follows:
I'm using bot to modify all my contact's remark (2600 contacts), each operation interval of 15 seconds, after I modified 20 contacts, although log shows bot works well, but it failed to modify contact's remark.
Then I tried to modify my contact's remark manually on web Weixin, and I found an interesting situation:
I can modify the remark on web Weixin, it seems modified successfully, but the remark on my cell phone doesn't change, and when I log out web Weixin and log in again, I found  the remark isn't modified.
So I guess maybe weixin block the API to remark the contact.
Steps to reproduce the behavior (and fixes, if any)
1.When fail...
When it failed to modify a contact's remark, client gets two same XHR as follows:
name:
wxoplog
Reponse:
{
    "BaseResponse": {
        "Ret": 1205,
        "ErrMsg": ""
    }
}

2.When success...
When modify a contact's remark successfully, client get 3 XHR (2 of them are same) as follows:
First XHR
name:
webwxoplog?pass_ticket=Vz4luhOatJin0JGE1XS5k2GFUTY%252Fu%252F%252BsBCwyynIHXD1AvW2X2PvazgBTPV3jSIF1
Response ：
{
    "BaseResponse": {
        "Ret": 1205,
        "ErrMsg": ""
    }
}

Second XHR:
name:
webwxsync?sid=DCtzuSvdOMDv5Izt&skey=@crypt_ec621fb6_23b21f1e43a919944cb9fb974aa4992f&pass_ticket=Vz4luhOatJin0JGE1XS5k2GFUTY%252Fu%252F%252BsBCwyynIHXD1AvW2X2PvazgBTPV3jSIF1
Response ：
{
    "BaseResponse": {
        "Ret": 0,
        "ErrMsg": ""
    },
    "AddMsgCount": 0,
    "AddMsgList": [ ],
    "ModContactCount": 1,
    "ModContactList": [
        {
            "UserName": "@75527d77fa288dbc6d4823250153d89f",
            "NickName": "æŽä½³èŠ®",
            "Sex": 2,
            "HeadImgUpdateFlag": 1,
            "ContactType": 0,
            "Alias": "ruirui_0914",
            "ChatRoomOwner": "",
            "HeadImgUrl": "/cgi-bin/mmwebwx-bin/webwxgeticon?seq=631539765&username=@75527d77fa288dbc6d4823250153d89f&skey=@crypt_ec621fb6_23b21f1e43a919944cb9fb974aa4992f",
            "ContactFlag": 1,
            "MemberCount": 0,
            "MemberList": [ ],
            "HideInputBarFlag": 0,
            "Signature": "å›žå±±æ´žé‡Œ",
            "VerifyFlag": 0,
            "RemarkName": "",
            "Statues": 0,
            "AttrStatus":<PHONE_NUMBER>,
            "Province": "åŒ—äº¬",
            "City": "æµ·æ·€",
            "SnsFlag": 1,
            "KeyWord": "qq5"
        }
    ],
    "DelContactCount": 0,
    "DelContactList": [ ],
    "ModChatRoomMemberCount": 0,
    "ModChatRoomMemberList": [ ],
    "Profile": {
        "BitFlag": 0,
        "UserName": {
            "Buff": ""
        },
        "NickName": {
            "Buff": ""
        },
        "BindUin": 0,
        "BindEmail": {
            "Buff": ""
        },
        "BindMobile": {
            "Buff": ""
        },
        "Status": 0,
        "Sex": 0,
        "PersonalCard": 0,
        "Alias": "",
        "HeadImgUpdateFlag": 0,
        "HeadImgUrl": "",
        "Signature": ""
    },
    "ContinueFlag": 0,
    "SyncKey": {
        "Count": 9,
        "List": [
            {
                "Key": 1,
                "Val": 631544760
            },
            {
                "Key": 2,
                "Val": 631546796
            },
            {
                "Key": 3,
                "Val": 631546798
            },
            {
                "Key": 11,
                "Val": 631546595
            },
            {
                "Key": 13,
                "Val": 631532646
            },
            {
                "Key": 201,
                "Val":<PHONE_NUMBER>
            },
            {
                "Key": 1000,
                "Val":<PHONE_NUMBER>
            },
            {
                "Key": 1001,
                "Val":<PHONE_NUMBER>
            },
            {
                "Key": 1003,
                "Val":<PHONE_NUMBER>
            }
        ]
    },
    "SKey": "",
    "SyncCheckKey": {
        "Count": 9,
        "List": [
            {
                "Key": 1,
                "Val": 631544760
            },
            {
                "Key": 2,
                "Val": 631546796
            },
            {
                "Key": 3,
                "Val": 631546798
            },
            {
                "Key": 11,
                "Val": 631546595
            },
            {
                "Key": 13,
                "Val": 631532646
            },
            {
                "Key": 201,
                "Val":<PHONE_NUMBER>
            },
            {
                "Key": 1000,
                "Val":<PHONE_NUMBER>
            },
            {
                "Key": 1001,
                "Val":<PHONE_NUMBER>
            },
            {
                "Key": 1003,
                "Val":<PHONE_NUMBER>
            }
        ]
    }
}
```

Please post all the logs when this issue happen with WECHATY_LOG=silly set.

code as follows:
import {
    Wechaty,
    Contact
} from '../'
const qrcode = require('qrcode-terminal')

const bot = Wechaty.instance({profile:'kzshequ'})
bot
.on('scan',(url,code)=>{
    let loginQrcode = url.replace('qrcode','l')
    qrcode.generate(loginQrcode)
    console.log(`${url} Scan to login`)
})

.on('login',async function(username){
    console.log(`${username.name()}login`)
      let contact
      contact = await Contact.find({name:"演欢"})
      if(contact){
        await contact.ready()
        let nickName = contact.name()
        let oldRemak = contact.remark()
        contact.remark('')
        console.log(`${oldRemak}----->${nickName}`)
      }
})
.init()

As you care about the remark('') result, what you need to do is get the return value of remark.
It seems you do not care about what remark() returns in your code:
        contact.remark('')

It's a bad behavior.
The good practice is to always save the return value of the function, like the following:
const result = await contact.remark('')
if (result) {
  console.log('success')
} else {
  console.error('failed')
}

Hope it will help you to understand what you need to do.

Thanks！
You are so sweet!


Ldap authentification failed when using jenkins in container with docker bridge

Hi,
I tryed to use Ldap to authenticate my users with Docker Jenkins in version 1.625.2 whitout success.
After a long investigation due to no log report, i tryed to setup my Jenkins Docker container with --net host. In this configuration, my ldap authentification success.
After looking in Jenkins code, it seem that LdapTemplate used by Jenkins requiere a RemoteAdressIp. In case of our Jenkins run in a container with brigeded network, this code retrive private IP of container which not allow to get an Ldap connection. (I try to found this code again).
In my case, i run my docker-engin in a IAAS provider which provide a private network to my VMs. Run my Jenkins Docker with  --net host not allow me to solve this issue.
I'm ready to help to solve this issue, but i don't have any idea good entry point to solve it.
Regards,
Jean-Pascal

That's more related to Jenkins than to the Docker image,  you should ask in the Jenkins user mailing list or check the LDAP plugin docs https://wiki.jenkins-ci.org/display/JENKINS/LDAP+Plugin


[DEVREL-38] Ruby Gap Updates

Fixes

Adds support to missing recipient endpoints
Adds missing integration spec to recipient account
Adds support to delete multiple batches

A short description of what this PR does.
Checklist

[x] I acknowledge that all my contributions will be made under the project's license
[ ] I have made a material change to the repo (functionality, testing, spelling, grammar)
[ ] I have titled the PR appropriately
[ ] I have updated my branch with the main branch
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added the necessary documentation about the functionality in the appropriate .md file
[ ] I have added inline documentation to the code I modified

If you have questions, create a GitHub Issue in this repository.

Hi Aman, these are the ruby gap updates packaged in a single PR. I'd like to merge this before creating a new branch in the ruby project (not this fork) to rename/rebrand to trolley classes
Could you help me accomplish this?

Thanks for the review, @Sheikh-Aman. I've added the requested changes and will request your re-review now


Scale line shows incorrect sizes.

The scale line control (ol/control/ScaleLine), assumes a pixel size of 0.28mm.
This creates very large errors in the scale.
On mobile devices we tested we found the average error being more that 50%.
Passing the screen density as an option when creating the control should give an easy solution.
In addition the function converts mm to inch (X25.4) and then inch to meters(X39.37), since these are only used internally it seems redundant to introduce these errors instead of converting mm to meters directly.
getScaleForResolution() {
const resolution = this.getMap().getView().getResolution();
const dpi = 25.4 / 0.28;
const mpu = this.viewState_.projection.getMetersPerUnit();
const inchesPerMeter = 39.37;
return parseFloat(resolution.toString()) * mpu * inchesPerMeter * dpi;
}

There is no way for a browser to determine the precise pixel size of a device. However if exporting to a PDF with specified dpi and with the map resolution set for a specified scale at that dpi there should be a way to reflect that in the scalebar https://codesandbox.io/s/export-pdf-r2m3x  Developers could also use that to better reflect that characteristics of target devices.

This has been discussed here before, and still bugs me a bit.
I think it all comes to de dpi values of ( map / resolutions / browser / canvas / etc)

the ol scale line control uses a fixed dpi of 25.4 / 0.28 = 90,714.
if the map is created with pixelRatio: 1 it should not change on different devices and should make math easier.
if we export the canvas/dom/(map), it exports an image from the browser canvas that has a fixed 96dpi, so map/scales are created with 90,714 but the export comes on 96, so you need to adjust the export image size from 90,714 to 96, otherwise you get an image with the scale calculated to 90.714 but it actually is at 96.

If you want fixed scale values for each zoom (1:1000, 1:2000, 1:5000, ...) so you can export a map image at 1:1000, you need to match each zoom level each scale value, using a dpi value of 25.4 / 0.28, like this each zoom will be even with the scale line control.
All this because "DPI defined by OGC specification (dpi assumes 0.28mm as the physical distance of a pixel)." witch since the browser is at 96dpi, and since OL is to show layers/data on browsers, shouldn't the zoom lvls be visually more accurate using 96dpi?
I would like to build a map/resolutions at 96dpi, with a scaleLineControl at 96dpi, the exported map to png/pdf will be exported at 96(browser), and if the pdf is created with 96dpi, 1cm on the screen should correspond to a even scale line value and after the export with should be 1cm on the pdf as well, if printed with 96dpi also, we should be getting the "same" approximated 1cm on paper.
All this is a bit confusing and i am stretching quite a bit here...

If you are exporting to a 300 dpi printer (or a PDF intended for one such as in the example https://openlayers.org/en/latest/examples/export-pdf.html) the ScaleLine's dpi should be 300 as the export has been correspondingly enlarged.  Also the resolution used in the ScaleLine is currently incorrect unless you are at the equator - it needs to be adjusted for the point resolution of the view center.  Here is my previous example patched to show the correct scale when exported  https://codesandbox.io/s/export-pdf-wquew  (the controls are not yet correctly positioned on the export - that is a limitation of the basic example which wasn't intended to include controls).

ok...

so you adjusted/replaced this.getMap().getView().getResolution() with getPointResolution() using the center point of the map in order to have a more accurate resolution value, right?
also override the consts on ScaleLine so it would auto adjust to the chosen DPI value?

By default ScaleLine uses const dpi = 25.4 / 0.28, do you know if the map when created and calculating the resolution for all the zoom levels also uses a dpi = 25.4 / 0.28?

if so? if we want to try to approximate what we see in our screen to reallity/paper can or should we calculate map resolutions using dpi = 25.4 / 0.28 OR dpi = 96(browser)?
thanks in advance


chore: update maintainer

Description

Related links

Notes for reviewers

Pre-review checklist for the PR author

[ ] I've confirmed the contribution guidelines.
[ ] The PR is ready for review.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR has been properly tested.
[ ] The PR has been reviewed.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

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

Comparison is base (2dc3da8) 25.14% compared to head (bb56e0e) 36.99%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##             main     #244       +/-   ##
===========================================
+ Coverage   25.14%   36.99%   +11.84%
===========================================
  Files          58       28       -30
  Lines        3297     2041     -1256
  Branches     1075     1058       -17
===========================================
- Hits          829      755       -74
+ Misses       1734      556     -1178
+ Partials      734      730        -4

Flag
Coverage Δ

differential
36.99% <ø> (?)

total
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 30 files with indirect coverage changes

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


Just a minor typo fix

Just a minor typo fix

@jadhavajay thanks. Mind changing the commit message to adhere to the contributing guidelines? https://github.com/SpoonX/about/blob/master/CONTRIBUTING.md#commit


Update http4s-blaze-server, http4s-circe, ... to 0.21.20

Updates

org.http4s:http4s-blaze-server
org.http4s:http4s-circe
org.http4s:http4s-dsl

from 0.21.1 to 0.21.20.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Migrations

dependency:v0_21@org.http4s:http4s-scalafix:0.21.5

Documentation:

https://github.com/http4s/http4s/releases/tag/v0.21.5

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

labels: library-update, semver-patch, scalafix-migrations

Superseded by #272.


Create Kadane's Algorithm.md

📥 Pull Request
Description
This Pull Request implements Kadane's Algorithm, which efficiently finds the maximum sum of a contiguous subarray within a one-dimensional numeric array.
Fixes #919
Type of change

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

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

@ajay-dhangar, I have completed the pr, Kindly review it and provide feedback also gssoc and hacktoberfest labels.

@ajay-dhangar Made the changes according to your suggestions, also kindly add hactoberfest accepted label.


Crossorigin attribute not added to link prefetch element

crossorigin attribute is properly added to the Plausible script tag itself, but not to the link prefetch element:
<link rel="preload" href="https://plausible.io/js/script.js" as="script" integrity="sha256-foobar">

Warning in Chrome console is as follows:

A preload for 'https://plausible.io/js/script.js' is found, but is not used because the request credentials mode does not match. Consider taking a look at crossorigin attribute.

Here's the script itself for comparison:
<script src="https://plausible.io/js/script.js" async="" defer="" data-domain="foobar.com" integrity="sha256-foobar" crossorigin="anonymous" data-nscript="afterInteractive"></script>

Hey I can't reproduce this locally. Can you set up a reproduction repo?

I can't reproduce this. I do not get the  element. Can you share how you are using <PlausibleProvider/>?

Sure! Maybe that's due to Next 15?
/* package.json */

"next": "15.0.0-rc.0",
"next-plausible": "^3.12.0",
"react": "19.0.0-rc-f994737d14-20240522",

// layout.tsx

import PlausibleProvider from "next-plausible"

...

export default function RootLayout({
  children,
}: Readonly<{
  children: React.ReactNode
}>) {
  return (
    <html lang="pl">
      <head>
        <PlausibleProvider
          domain="foobar.pl"
          integrity="sha256-0yIPQuNDyhSEo..."
          enabled={process.env.VERCEL_ENV === "production"}
          trackOutboundLinks={true}
          taggedEvents={true}
        />
      </head>

I don't insert anything manually. I only use the script itself and a hook in one component:
import { usePlausible } from "next-plausible"
...
export function SearchInput() {
  ...
  const plausible = usePlausible()
  ...
  const performSearch = async (query: string) => {
    ...
    plausible("search", {
      props: { query: encodeURIComponent(query) },
    })
    ...
  }
  ...
}

On my website this inserts the two scripts mentioned in the first post.


Identify replica sets for dashboard

We don't have proper display for replica set yet (see #567), but as mentioned in #1229, we need to know sometimes how many replicas a resource have. Having a proper mechanism to identify would be helpful.

It means "we want to do this before we ship GA but we don't know which preview this fits into as yet, but it's not being punted until after GA (which is future)".

@davidfowl  you beat me to it :)

We should do this earlier. We are having more places where we need to identify replicas (endpoints and naming are 2). For every time we have to iterate over whole list. (The display of replica set can come later in UI)

@kvenkatrajan this should be re-triaged. I do not know what app-model/dcp work has been done, as currently we parse the specific resource name format to compute replicas. We shouldn't be doing that long-term

Just an FYI:.... been (attempting) to get through eShop.... I think (right now me head hurts)  replicas (in the branch but not in main?!?!?!) had me chasing my tail most of the day.....

@kvenkatrajan moving to this to 8.1


rules/eslint/style/walmart.js not compatible with strict mode, though marked as such

rules/eslint/style/walmart.js contains a duplicate field name:
"space-before-keywords": 0,
// require or disallow space before blocks
"space-before-blocks": [2, "always"],
// require or disallow space before function opening parenthesis
"space-before-function-paren": [2, {"anonymous": "always", "named": "never" }],
// require a space before certain keywords (fixable)
"space-before-keywords": [2, "always"],

GIving the following error when running eslint:
/src/scripts/provision-test-environment/node_modules/eslint-config-defaults/rules/eslint/style/walmart.js:122
"space-before-keywords": [2, "always"],
^^^^^^^^^^^^^^^^^^^^^^^
SyntaxError: Cannot read config package: eslint-config-defaults/rules/eslint/style/walmart
Error: Duplicate data property in object literal not allowed in strict mode

Created a pull request for this.

@JanNorden -- There's actually multiple instances of this. I'm fixing and adding eslint of the configs themselves to travis CI.
/cc @baer

Thanks for the quick reply. Guessed there might be more after seeing the
other pull request. Looking forward to the fixes.
2016-01-12 16:08 GMT+01:00 Ryan Roemer<EMAIL_ADDRESS>
@JanNorden https://github.com/JanNorden -- There's actually multiple
instances of this. I'm fixing and adding eslint of the configs
themselves to travis CI.
/cc @baer https://github.com/baer
—
Reply to this email directly or view it on GitHub
https://github.com/walmartlabs/eslint-config-defaults/issues/54#issuecomment-170941683
.

--
/Jan Norden


[request]: Retry if the request fails with a TooManyRequestsError

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue, please leave a comment

Tell us about your request
Automatic retries with backoff when the aws API fails with a TooManyRequestsError
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I'm building a rust script to get concurrently the version of several lambda functions pointed by a certain alias name.
The problem is some of these calls fails with a TooManyRequestsError and causes the whole script to fail.
Are you currently working around this issue?
The workaround I found so far is to turn down the level of concurrency with which I call the get_alias method, but this is not the best case for me and is also flaky.
Additional context
I'm using the aws-sdk-lambda version: v0.0.6-alpha
The TooManyRequestsError I get reads as follows:
Error: ServiceError { err: GetAliasError { kind: TooManyRequestsError(TooManyRequestsError { retry_after_seconds: None, r#type: Some("User"), message: Some("Rate exceeded"), reason: Some(CallerRateLimitExceeded) }), meta: Error { code: Some("TooManyRequestsException"), message: Some("Rate exceeded"), request_id: Some("****"), extras: {} } }, raw: Response { status: 429, version: HTTP/2.0, headers: {"date": "Wed, 02 Jun 2021 14:41:24 GMT", "content-type": "application/json", "content-length": "76", "x-amzn-requestid": "****", "x-amzn-errortype": "TooManyRequestsException"}, body: SdkBody { inner: Once(Some(b"{\"Reason\":\"CallerRateLimitExceeded\",\"Type\":\"User\",\"message\":\"Rate exceeded\"}")), retryable: true } } }

This error actually is retriable. Would you mind turning on debug logging? I suspect that we're retrying here, but actually just running out of retries.
// Cargo.toml:
tracing-subscriber = "0.2.18

// in main:
tracing_subscriber::fmt::init();

then: RUST_LOG='smithy_http_tower::dispatch=trace,smithy_http::middleware=trace'
You should hopefully see some spans that indicate that we're retrying those errors

@rcoh you are right!, there are retries before failing.
I will close this issue but first, I would like to ask you, how can I configure the number of retries and the exponential backoff parameters?
For example in the Java version of the sdk there is a RetryPolicy attribute on the ClientConfiguration, is there anything analogous here?
Thank you very much!

It's not currently possible but please file an issue to request it :-)


What is the correct way to set the NuGet version of a set of packages that reference each other

When I use Nerdbank.GitVersioning in my .csproj files, and some projects reference each other, and all have the same version as specified in verison.json, the generated packages reference >= v1.0.0 of the other referenced csproj packages. It is not clear from the documentation how to get them to reference the current version.
I thought that one would be able to add the <Version> element in the csproj with some variable as its content. If so, where is that variable documented, and how is its value generated before the Nerdbank.GitVersioning is seen?
If not, how is this achieved?
I can write a script that runs before the build and either sets an environment variable or updates the .csproj files with the correct version, but that seems to make Nerdbank.GitVersioning of limited use.
I imagine this is the normal versioning requirement, so I am sure I am missing some documentation. Any pointers would be appreciated.

Great question. It's a dupe of #113 which describes the workaround to the Nuget bug.

I saw #113 but did not like that answer. My workaround is to get the NuGet version string in the Setup method of my Cake build script by invoking the Get-Version.ps1 tool. I then pass that to MSBuild as a property via the 'dotnet' invocations, and have the Version element of the csproj set by that value. It is a five line change to the Cake build script, and does not require messing up the csproj scripts at all.
I should write a Cake addin for this, and submit a PE, and will do so if I ever need this again.

*PR


Cross browser testing

Opened after #368 reappeared on Firefox, something that wouldn't have happened with some cross browser testing.
There was also a mention of performance testing too in https://github.com/reakit/reakit/issues/429#issue-490585539. This would be nice to have IMO but isn't as crucial as testing functionality testing in real browsers.
I've seen BrowserStack mentioned before, is this a good avenue to go down?

I've seen BrowserStack mentioned before, is this a good avenue to go down?

Definitely! I think we have an open source account on BrowserStack. We just need to re-add their attribution in the readme.
Unfortunately, I haven’t had time to explore this.

Ok great, I'll take a look at BrowserStack. I've also applied for a Cypress license, I'll evaluate that too - I've heard great things about Cypress in this space.

One thing I've been trying to do is concentrate test cases, stories and, in the future, website live examples in __examples__ folders. Right now they have a few tests (in a __tests__ folder inside) and are being used for storybook. Maybe we could use them for browser testing as well.

After some initial investigation Cypress looks much more suited to the task of functionality testing than BrowserStack, the official GitHub action looks great.
Here's the plan I'm currently exploring:
Create a simple dev server that will serve all of the examples in the __examples__ folders. We could use Storybook here, but Storybook has a very long startup time which isn't ideal if we want this to run on commit for example.
Once this is setup and I have a couple of tests added as an example I'll open a PR. By the time that's merged we'll hopefully have the Cypress OSS license come through, at which point we can work on getting the tests running in a GitHub action and auto-uploaded to the Cypress dashboard.

@tom-sherman I had a go on my own project with Browserstack Automate. If you plan to migrate your Cypress setup to it, ping me if you need help.
All my setup does right now is renderring my example.html page on Safari/IE/Chrome/FF.
Right now it's using Intern to run the test as you can do functional tests with it and it supports BrowserStack.
It looks like this then on BrowserStack then:

Tha KS @Grsmto, this is really helpful.
I've had less time than I'd like to work on this recently so I've unassigned myself, if anyone else wants to pick this up then feel free!


v3.7.0 and above immediately crashes Next.js app

Bug description
I've been using Prisma and Next.js together for quite a while.
When I upgrade Prisma to 3.7.0 or above, and then run my Next.js app, it immediately crashes the process when I load any page.
The console just gives:
zsh: killed     npm run dev

Is there any more useful logging I could get, to help debug this?
Has anything changed in 3.7.0 which could  cause this? I have tested with 3.8.0 too and it gives the same result.
I'm using the latest version of Next.js 12.0.8
Thanks
How to reproduce

Expected behavior
No response
Prisma information

Environment & setup

OS: Mac OS
Database: MySQL RDS
Node.js version: 16.13.0

Prisma Version
3.7.0 and above

Is there any more useful logging I could get, to help debug this?

You can always enable logging and debugging for Prisma itself: https://pris.ly/d/logging + https://pris.ly/d/debugging But as your application is crashing, that might not even give you much. Let's see.

Thanks, so with both those things enabled, I get this:

Server started on https://local.dev:3000
wait  - compiling / (client and server)...
info  - Using external babel configuration from /Users/[redacted]/.babelrc
event - compiled client and server successfully in 516 ms (1195 modules)
prisma:tryLoadEnv Environment variables not found at null +0ms
prisma:tryLoadEnv Environment variables loaded from /Users/[redacted]/prisma/.env +0ms
prisma:tryLoadEnv Environment variables not found at null +1ms
prisma:tryLoadEnv Environment variables loaded from /Users/[redacted]/prisma/.env +0ms
prisma:client clientVersion: 3.8.0 +0ms
prisma:client clientEngineType: library +0ms
prisma:client:libraryEngine internalSetup +0ms
prisma:client:libraryEngine Searching for Query Engine Library in /Users/[redacted]/node_modules/.prisma/client +4ms
prisma:client:libraryEngine loadEngine using /Users/[redacted]/node_modules/.prisma/client/libquery_engine-darwin-arm64.dylib.node +0ms
zsh: killed     npm run dev

Can you show the comparison of the older version running?

Sure:

Server started on https://local.dev:3000
wait  - compiling / (client and server)...
info  - Using external babel configuration from /Users/[redacted]/.babelrc
event - compiled client and server successfully in 599 ms (1195 modules)
prisma:tryLoadEnv Environment variables not found at null +0ms
prisma:tryLoadEnv Environment variables loaded from /Users/[redacted]/prisma/.env +0ms
prisma:tryLoadEnv Environment variables not found at null +1ms
prisma:tryLoadEnv Environment variables loaded from /Users/[redacted]/prisma/.env +0ms
prisma:client clientVersion: 3.6.0 +0ms
prisma:client clientEngineType: library +1ms
prisma:client:libraryEngine internalSetup +0ms
prisma:client:libraryEngine Search for Query Engine Library in /Users/[redacted]/node_modules/.prisma/client +4ms
prisma:client:libraryEngine loadEngine using /Users/[redacted]/node_modules/.prisma/client/libquery_engine-darwin-arm64.dylib.node +0ms
Refresh token with api
You are the first - lets start the new promise
wait  - compiling /api/auth/refresh-token...
event - compiled client and server successfully in 167 ms (1209 modules)
prisma:client Prisma Client call: +393ms
prisma:client prisma.refreshToken.findUnique({
prisma:client   select: {
... etc ...
prisma:client }) +1ms
prisma:client Generated request: +0ms
prisma:client query {
prisma:client   findUniqueRefreshToken(where: {
prisma:client     id: "....."
prisma:client   }) {
... etc ...
prisma:client }
prisma:client  +0ms
prisma:client:libraryEngine sending request, this.libraryStarted: false +393ms
prisma:client:libraryEngine library starting +0ms
prisma:info Starting a mysql pool with 5 connections.
prisma:client:libraryEngine library started +204ms
... etc

"Refresh token with api" is from my code.

So it seems between new PrismaClient() and your console.log("Refresh token with api") the application crashes. Can you share the code that is excecuted in between? (Is this all outside a request to the app, so all on startup?)

I totally appreciate why you've asked for that, but that's quite difficult to pin down.
I don't know if this helps, but this is how I initiate Prisma. It's based on this comment for managing connections in a serverless environment.
import {PrismaClient} from '@prisma/client';

/**
 * @type PrismaClient
 */
let prisma;

if (process.env.NODE_ENV === 'production') {
  prisma = new PrismaClient();
} else {
  if (!global.prisma) {
    global.prisma = new PrismaClient();
  }

  prisma = global.prisma;
}

export default prisma;

Yep, that is fine - the question is where this gets executed and what code runs in between that and then the logging of the "Refresh token with api"?
As we have no other reports of Nextjs apps crashing, I have to act under the assumption that something between the first missing log output ("Refresh token with api") and where Prisma Client is instantiated (we know that still happens as we have related log output) is causing your app to crash. The more log outputs you can put there closer to the new PrismaClient(); the better. Maybe just add it in the line after that one actually and see if it is output with 3.7.0+

Ok thanks, I'll get lots of console logs dropped in and see where we get to.

Ok, so console logs after new PrismaClient() appear. They're logged anywhere they're placed outside of functions, but any I place inside functions don't appear. This includes in the default export in _app.js.

Sorry, I don't fully understand. Which logs are working and which are not?

So as an example:
import Whatever from 'wherever';
console.log('This log appears');

function App() {
  console.log("This log doesn't appear");
};

export default App;

So this produces:
...
wait  - compiling / (client and server)...
event - compiled client and server successfully in 435 ms (1195 modules)
This log appears
zsh: killed     npm run dev

Logs before and after new PrismaClient() all appear.

Hm. Can you maybe create a minimal reproduction app with a new Next.js project?

Well I'm baffled. Without doing anything, it's just suddenly started working. I'm now on Prisma 3.8.0 and it's working perfectly. I can't explain it, and I'm never keen on behaviour changing without explanation but I'm not sure what else to say. Thank you for your assistance, I'll be back if the problem returns.

No worries, we like when things just solve itself magically :D Let us know if this ever happens again, and we can take another look. Probably some Node dependency cache thing or whatever. It's usually one of those.

FWIW I ran into this exact same problem. Running rm -rf node_modules; npm i fixed it for me, so likely something strange being cached.

I just updated from Prisma 3.8.1 to 3.9.1 on an express application and saw, shortly after initializing the PrismaClient instance, my whole server process get killed via SIGKILL.
I reduced the application code more and more until it was basically doing nothing but initializing Prisma - and when commenting out the Prisma code or reverting back to the old version it would work fine.
After finding this thread I tried a rm -rf node_modules; npm i and it started working again. Maybe still worth looking into whatever kind of caching the prisma module is doing, especially after updates? Or even recommending a full node_modules wipe on every update in the Release notes? I know this would have saved me some time and headache.
I'm using npm -v 8.1.3 and node -v v16.13.0.

Seeing the same thing that @idolize did at prisma 3.9.2, npm 8.3.1, and v17.4.0.

I ran into this as well. I know it's not technically in prisma's scope to account for weird node caching issues, but maybe this could be documented more clearly when performing an upgrade to the prisma library? This was a rather painful thing to figure out.

Had the same issue upgrading from 3.7.0 -> 3.11.0, Node 16.3.0 and yarn 1.22.17:
[INFO] 18:01:36 ts-node-dev ver. 1.1.8 (using ts-node ver. 9.1.1, typescript ver. 4.5.5)
Debugger listening on ws://<IP_ADDRESS>:9229/2faa48f9-b3ff-45e5-9040-55e5a15629bf
For help, see: https://nodejs.org/en/docs/inspector
  prisma:tryLoadEnv Environment variables loaded from /Users/okomarov/Documents/repo/api/.env +0ms
  prisma:tryLoadEnv Environment variables loaded from /Users/okomarov/Documents/repo/api/.env +755ms
  prisma:client clientVersion: 3.11.0 +0ms
  prisma:client clientEngineType: library +0ms
  prisma:client:libraryEngine internalSetup +0ms
  prisma:client:libraryEngine Searching for Query Engine Library in /Users/okomarov/Documents/repo/api/node_modules/.prisma/client +36ms
  prisma:client:libraryEngine loadEngine using /Users/okomarov/Documents/repo/api/node_modules/.prisma/client/libquery_engine-darwin-arm64.dylib.node +0ms

and solved by reinstalling node modules as in https://github.com/prisma/prisma/issues/11128#issuecomment-1019264372

I also had this issue (not in Next) right now on macOS. Removing the ./node_modules/.prisma folder and running prisma generate again solved this issue.
I hope it helps somebody.


Drain Machines while scaling down

We should drain the Machines before we scale them down via MachineSet. Interesting question would be, which controller should we give responsibility of draining.
Possible options could be : MachienSet or introduce new drain-controller.
On the same line, we should also add new value for MachinePhase, DRAINING(?) may be.

I have implemented the drain logic, but I am still not sure about the best way to trigger forced deletion.

Can this issue be closed?

Yes sure, this has been implemented now.


Update MARC field mappings

Price:
981$i
Vendor:
980$v

fund:
980$h

should quantity be a required field.  It's currently in 980$q

@fereira quantity should be 980$g

All the mappings for the POOF case:
980$y Selector
980$g Quantity
980$h fund
980$z - internal note
980$v - vendor
981$k currency
981$n receiving note
981$q if Rush: Yes toggle rush field to true
981$i price
981$r Requester

@starsplatter Is this complete on your end, or are you still working through the non POOF case?

Previously a Note was in the 980$n field.   980$z was used as the Electronic Indicator.  If it’s going to be used for an Internal note I’ll need to know what field is used to indicate that item is electronic or physical
From: Jenn Colt @.>
Reply-To: cul-it/order-import-poc @.>
Date: Sunday, March 21, 2021 at 2:11 PM
To: cul-it/order-import-poc @.>
Cc: John Fereira @.>, Mention @.***>
Subject: Re: [cul-it/order-import-poc] Update MARC field mappings (#9)
All the mappings for the POOF case:
980$y Selector
980$g Quantity
980$h fund
980$z - internal note
980$v - vendor
981$k currency
981$n receiving note
981$q if Rush: Yes toggle rush field to true
981$i price
981$r Requester
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/cul-it/order-import-poc/issues/9#issuecomment-803634406, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAEOZVF5BLSJPZJRBRDP7K3TEYZDRANCNFSM4Y66WKIQ.

What is the non-poof case?   Will there be purchase orders using the old marc subfields still be entered?   That would be a use case that wasn't communicated to me

We won't need the old fields they are from Lehigh and aren't relevant for us.
For electronic, if the 952$b is serv,remo it is electronic
For the non-POOF case, I am still working on tracking down vendor files before we edit them. It happens through automation so I have to get them off the vendor ftp rather than our system and I'm still working on it. Implementing the POOF case will take care of a large part of what will come through the app.

Okay…that makes sense to use the same field as is used for the physical location.   I’ll need to make some changes In the code to test the location field rather than the electronic indicator field.   I don’t believe I’ve seen any mrc files that have serv,remo in that field yet.  The mrc files I have available seem to have some, but not all of the use cases I’ll need.   That’s what issue #14 is all about:  https://github.com/cul-it/order-import-poc/issues/14
From: Jenn Colt @.>
Reply-To: cul-it/order-import-poc @.>
Date: Tuesday, March 23, 2021 at 8:29 AM
To: cul-it/order-import-poc @.>
Cc: John Fereira @.>, Mention @.***>
Subject: Re: [cul-it/order-import-poc] Update MARC field mappings (#9)
We won't need the old fields they are from Lehigh and aren't relevant for us.
For electronic, if the 952$b is serv,remo it is electronic
For the non-POOF case, I am still working on tracking down vendor files before we edit them. It happens through automation so I have to get them off the vendor ftp rather than our system and I'm still working on it. Implementing the POOF case will take care of a large part of what will come through the app.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/cul-it/order-import-poc/issues/9#issuecomment-804863193, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAEOZVHOBPFEHZC4SZ4NTVTTFCCRJANCNFSM4Y66WKIQ.

@fereira I've updated the issue description, summarizing the field mappings provided in the comments. My vote is to create a separate issue for 952$b logic.

We sort of already have one in issue #6 though it indicates that the 952$b field will be used for physical holdings but didn’t say that it was also going to be used to indicate that an item is electronic or physical.
From: Nick Cappadona @.>
Reply-To: cul-it/order-import-poc @.>
Date: Tuesday, March 23, 2021 at 9:38 AM
To: cul-it/order-import-poc @.>
Cc: John Fereira @.>, Mention @.***>
Subject: Re: [cul-it/order-import-poc] Update MARC field mappings (#9)
@fereirahttps://github.com/fereira I've updated the issue description, summarizing the field mappings provided in the comments. My vote is to create a separate issue for 952$b logic.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/cul-it/order-import-poc/issues/9#issuecomment-804910083, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAEOZVHYDAG3I5EX34H5CSDTFCKWVANCNFSM4Y66WKIQ.

@fereira Correct. Since the linked PR #16 is still open, do you prefer to handle the 952$b logic there?

I think we need to determine if the app is going to be used at all for eResources, and if not create an issue which pulls out all the code which references eResources.

Although the app currently is hardcoding the currency field as USD, all of the test data which has the currency in 981$k subfield has two instances of the $k subfield in the 981 datafield.  As a result, the MarcReader library returns USDUSD for the currency.

Yep...the currency hardcoding is listed under areas for improvement in the README. Sounds like its days are numbered 😉

The question that I have regarding the currency field is if there is a bug in marc4j that concatenates the values of multiple instances of a subfield, or if the marc shouldn't have multiple $k subfields in the 981 field.  Other than this issue,  I have a version of the MarcUtils class which addresses all other mappings


Progress log of image generation not working

There was a discussion in  https://github.com/replicate/replicate-python/issues/152 that Prediction class instance now provides progress information. But I don't thinks it's working as expected. Could you please have a look at this and confirm that progress property is always available for Prediction instance?
Also there used to progress info in the log property of Prediction class instance, but I don't get this anymore (I was relying on this to check the progress in our UI)

Hey @921kiyo. Sorry for not responding to #152.
The way progress is determined is by scanning the prediction logs and scanning for output in a given pattern. If the logs aren't present or not in the right format, the progress property will return None.
In a recent issue over on the JS client (https://github.com/replicate/replicate-javascript/issues/146#issuecomment-1762144306), someone was reporting a similar issue with their mode, and it turned out to be an issue with logs not populating for their predictions. That was also a fine-tune of SDXL. That issue appeared to be resolved, but perhaps it's come up again. I'll ask around to see what's going on.

Following up on this —
I believe the issue of logs populating for in-flight predictions should now be resolved Please let me know if you're still having issues with prediction logs, and I'd be happy to take a look for Replicate's platform. But for now, I'll go ahead and close this issue, since there's nothing actionable here as far as the client library is concerned.


使用deepspeed和torch_ddp都会在训练的过程中报timeout的错误

我正在用1万小时在8张A800上重新训练cosyvoice，在训练或验证的过程中经常会报timeout的错误，num worker设的8，timeout设置1800s或5400s都不行，内存也没有oom，如下面两张图所示，从GPU的占用率上面看，确实是有一张卡的任务还未结束，请问是网络通信的问题吗？
使用deepspeed

使用torch_ddp
使用torch_ddp时，去掉join和不去掉也都会报错

are you using libritts? try set partition=False

are you using libritts? try set partition=False

I trained on my own datasets, what are the problems associated with setting up partitions

are you using libritts? try set partition=False

I have set parition=False，but It seems like different devices training on the same data

are you using libritts? try set partition=False

I have set partition=False， but It seems like different devices training on the same datas

Hey, did you solve the problem? I also met with the same thing. Can I ask if there is any suggestions to solve/improve it?

Hey, did you solve the problem? I also met with the same thing. Can I ask if there is any suggestions to solve/improve it?

ddp timeout should not interrupt the training, this is anticipated

Hey, did you solve the problem? I also met with the same thing. Can I ask if there is any suggestions to solve/improve it?

you can follow this url： wenet-e2e/wenet#2266 (comment)

thanks a lot!


Migrate UpdateMessageSignatureDto to zod

Summary
This migrates the validation of UpdateMessageSignatureDto to zod.
Changes

Remove UpdateMessageSignatureDtoValidationPipe and associated schemas.
Add test-covered UpdateMessageSignatureDtoSchema and infer types from it.
Propagate type requirements.
Update tests accordingly.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

6 of 6 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 93.384%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
6470

Relevant Lines:
6683

💛  - Coveralls


[Release][Ruby][CI] Verification job fails to install python 3.13 for Ruby under conda due to glib pin

Describe the bug, including details regarding any error messages, version, and platform.
The verify-rc-source-ruby-linux-conda-latest-amd64 job is failing with:
Looking for: ['glib==2.80.5', 'gobject-introspection', 'meson', 'ninja', 'ruby']

Pinned packages:
  - python 3.13.*

Could not solve for environment specs
The following packages are incompatible
├─ glib 2.80.5  is requested and can be installed;
└─ gobject-introspection is installable with the potential options
   ├─ gobject-introspection 1.51.1 would require
   │  └─ glib 2.51.* , which conflicts with any installable versions previously reported;
   ├─ gobject-introspection [1.51.3|1.55.0|1.56.1] would require
   │  └─ python [2.7* |>=2.7,<2.8.0a0 ], which can be installed;
   ├─ gobject-introspection [1.51.3|1.55.0|1.56.1] would require
   │  └─ python [3.5* |>=3.5,<3.6.0a0 ], which can be installed;
   ├─ gobject-introspection [1.51.3|1.55.0] would require
   │  └─ python 3.6* , which can be installed;
   ├─ gobject-introspection [1.55.0|1.56.1|...|1.70.0] would require
   │  └─ python >=3.6,<3.7.0a0 , which can be installed;
   ├─ gobject-introspection [1.56.1|1.58.2|...|1.74.0] would require
   │  └─ python >=3.7,<3.8.0a0 , which can be installed;
   ├─ gobject-introspection [1.58.2|1.64.1|...|1.80.1] would require
   │  └─ python >=3.8,<3.9.0a0 , which can be installed;
   ├─ gobject-introspection [1.66.1|1.68.0|...|1.82.0] would require
   │  └─ python >=3.9,<3.10.0a0 , which can be installed;
   ├─ gobject-introspection [1.70.0|1.72.0|...|1.82.0] would require
   │  └─ python >=3.10,<3.11.0a0 , which can be installed;
   ├─ gobject-introspection [1.74.0|1.76.1|...|1.82.0] would require
   │  └─ python >=3.11,<3.12.0a0 , which can be installed;
   ├─ gobject-introspection 1.78.1 would require
   │  └─ python >=3.12.0rc3,<3.13.0a0  with the potential options
   │     ├─ python [3.12.0|3.12.1|...|3.12.7], which can be installed;
   │     └─ python 3.12.0rc3 would require
   │        └─ _python_rc, which does not exist (perhaps a missing channel);
   ├─ gobject-introspection [1.80.1|1.82.0] would require
   │  └─ python >=3.12,<3.13.0a0 , which can be installed;
   └─ gobject-introspection 1.82.0 would require
      └─ libglib >=2.82.1,<3.0a0 , which requires
         └─ glib 2.82.1 *_0, which conflicts with any installable versions previously reported.

We did pin glib here:

https://github.com/apache/arrow/issues/44268

but this seems to be failing now.
This is failing for the maintenance branch on 18.0.0
Component(s)
Packaging, Ruby

Issue resolved by pull request 44382
https://github.com/apache/arrow/pull/44382


UnityPakcageManager support

will be cool

prototype: https://github.com/shivaduke28/kanikama/tree/feature/upm
it works for scripts, but prefabs with Udon scripts are broken...


Feature request: background image

We have a use case in which we want the user to be able to draw over an image. For example, the image could be a maze and the user should draw a path to get out of it.
It would be very nice if the component had a prop that allowed the board to start with a given image on the background. Ideally, the image would not be removable via the undo and clear buttons.

@gabrielguilhoto that scenario makes sense and I will add the background image feature with:

initial background image setting
change the background image and automatically clear the board
the layout of the background image, maybe fill/contain/original

are those features fulfill you requirements?

Hi @dilidili, thank you very much! For our use case the requirements are:

The image should not be removable via the undo and clear buttons (pressing clear should remove everything but the image)
The image should be in the center of the board, maintaining the original image dimensions (except if the image is larger than the board; then it should be resized to fit the board)

Dealing with a changing background image or changing its layout is not something that we would need right now, but those features could also be useful.
Do you have any idea when the feature might be implemented?

@gabrielguilhoto recently in China's Mid-Autumn holiday, I'll deliver this feature in one or two weeks.

Hi @gabrielguilhoto  one more question here, do you need the prop to set initial background image and prop to hide the set background button in UI?

@dilidili for our use case the background image should only be set programmatically (there would be no button on the interface for the user to set or hide the background). But the regular image button that exists currently would still be there. Thanks.

@dilidili And something I hadn't mentioned: the background image should be present on the saved image.

Hi @gabrielguilhoto , I've release the 0.5.0-beta.0 version which add the initialBackground and enableBackground props. Please help to test some use cases.

@gabrielguilhoto thank you very much! The background image is appearing on the canvas and being saved properly. I noticed the following issues:

The image is stretched to fit the canvas:

We would like the original image dimensions to be preserved.

When zooming in or out, the image stays fixed but the drawing changes. That leads to the drawing being misplaced:

https://user-images.githubusercontent.com/1630009/135635916-1b48d76a-ce12-4884-ac3a-74e0c340bb46.mov
The zoom should be applied to the background image as well. If, by any chance, that is hard to implement, it would be ok if the zoom could be disabled.

If I open a board with a background image, close it and then open it with another image, the first background image is shown instead of the second one.

I tested the initialBackground prop without the useBackground prop. I understood that the useBackground prop enables a button to set the background but it's not necessary to set a background programatically, right? Then I would call it something like showBackgroundButton, to make it clear that only the button is affected.

Hey @gabrielguilhoto, I've modified the RDB as you suggested on version 0.5.0-beta.1 and the useBackground has been renamed to showBackgroundTool. Feel free to let me known if there are any other requirements!

@dilidili can u merge new feature into the master branch? Thanks

@gabrielguilhoto I wanna apply into my project, but I cann't build it on the master branch with command: npm run build.
Can u help me? pls

@gabrielguilhoto I wanna apply into my project, but I cann't build it on the master branch with command: npm run build. Can u help me? pls

Hi @tungdau93, have you tried including the following commits when building?

@gabrielguilhoto thank bro. I dit it. But I wonder: when pass initialBackground props -> my background only = 1/2 canvas, it's not full background. Where can I check it? Can u help me.
initialBackground:
https://upanh.org/image/209Qi0
image after initialBackground loaded:
https://upanh.org/image/209cXt

@gabrielguilhoto I always want to set initialBackground full 100% canvas. So I can check it in function drawBackgroundImage of ImageTool.tsx, right? I just found it.

hi, is there a prop to araser don`t arase background pic?

@tungdau93 same problem here can solve now?


Unload model plugins when the model is removed from the world

As discussed in https://github.com/ignitionrobotics/ign-gazebo/issues/39#issuecomment-613957221, model plugins are not unloaded when the model is removed from the world.
There are few problems that this behaviour could cause:

Memory leak. If the simulation is very long and models are inserted and deleted multiple times, the RAM consumption slowly increases. (e.g. https://github.com/ignitionrobotics/ign-gazebo/issues/47)
If the plugin access ECM components of the model and it does not handle properly the case when they are not found (because the model has been removed), the behaviour could be undefined.

In #39 the problem was acknowledged but no specific issue was opened to track it.

Hi,
I can confirm that this problem is still present in gazebo Garden.
It's easily reproducable with an Hydrodynamics system which prints "No linear vel" once its model has been removed from the world. Which means the system is still running, but the entity is not present anymore.

Hi.
This problem seems to occur in Fortress as well, and can be reproduced by simply deleting the plugin-enabled model with the following command:
ign service -s /world/empty/remove --reqtype ignition.msgs.Entity --reptype ignition.msgs.Boolean --timeout 5000 --req 'type: MODEL; name: "my_model"'
How can I properly delete a model?
I looked up the ign command but couldn't find the answer.


[Bug] shell login option drops me to a blinking cursor, not bash

Pre-requisites

[X] I have looked for any other duplicate issues

Ly version
1.1.0
Observed behavior
When running ly, and selecting "shell" login as the "other" field, I can log in (get past the ly screen) but then I get dropped to a blank cursor, not even showing a bash prompt. Is there some missing config I need to set up in order to use plaintext mode?

Expected behavior
I expected to be placed into a bash prompt, just like regular plaintext mode used to work on login, prior to installing ly.
Steps to reproduce

select "shell" as the login method
log in
get dropped into empty screen

Relevant logs
OS debian 12, x86_64

Can confirm on arch linux

@mchaker @port19x I can reproduce this issue on both Debian 12 and Arch Linux. Now, after much tinkering, changing the shell to Fish worked, but Bash or Dash didn't want to work. Or well, that's what I thought... I realized that, in the TTY, I can still execute commands:

I can do this on both Debian and Arch. Can you guys confirm that's the case?

Okay, I finally identified the problem. It's due to PR #621, which redirected StandardError to systemd's journal, but of course, only with systemd. A fix is to modify the service and change the following:
- StandardError=journal

I tried looking online, but unfortunately it doesn't seem like you can direct the output to 2 places at the same time.

Confirming that is the case - I can run commands up until I hit "Ctrl-C" or "Ctrl-D".
I will test modifying the service as you described and report back.

Confirming that modifying the service as described works!

I'm not sure if the manual fix is compatible with GUIs/DEs, so not sure what code changes need to happen here, but the manual fix does work :)

It is fully compatible, as the previously mentioned PR was a simple one-line change anyway.

I've pushed the fix just in case, and I'll also backport it for v1.0.2. I'll leave the issue open so that port19x can verify if it works on their part.

@port19x Ly v1.0.2 hit the repos, can you confirm the bug is fixed on your side please?

unexpected behavior: after pulling from master, rebuilding, reinstalling, now logging out leaves the past session on the screen, behind the ly login window: is that expected?

unexpected behavior: after pulling from master, rebuilding, reinstalling, now logging out leaves the past session on the screen, behind the ly login window: is that expected?

That's definitely a bug. I'll try to reproduce it and hunt it down.

@mchaker This should be fixed with the latest commit. Can you check on your machine please?

Checking now, will report back with results.

This bug seems fixed - the console is now cleared when logging out of a shell login session :)

Tomorrow

I can confirm shell login now working flawlessly on arch linux with bash (my current login shell).
I'd say you can safely close this issue now


Allow to configure custom http client

Pull Request
Related issue
Fixes #357
What does this PR do?

Allows to configure custom http client

PR checklist
Please check if your PR fulfills the following requirements:

[x] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
[x] Have you read the contributing guidelines?
[x] Have you made sure that the title is accurate and descriptive of the changes?

README doesn't have anything conf related, but we can add to the Wiki

@curquiza https://github.com/meilisearch/meilisearch-symfony/wiki/Http-Client not sure if I managed to properly explain


⚠ API - Lens has degraded performance

In 00a14a4, API - Lens ($LENS_API_URL) experienced degraded performance:

HTTP code: 504
Response time: 10336 ms

Resolved: API - Lens performance has improved in d16986f after 6 minutes.


docs/custom multi-commands: prefer submodule import over eval

See #467.

There's absolutely nothing wrong with eval in this case.  It's concise, and the files are from a trusted location.  You realize that importing allows arbitrary execution as well, right?


Async compiler keyword + More secure SSL protocols

In a number of places in code the library uses #if NET45 || CORE to check if the framework supports await/async keywords. To make it more readable, I've added a ASYNC compiler keyword.
Also, I noticed that the library defaults to SSL3 + TLS 1.0 by default on .NET core. SSL3 is now considered obsolete and insecure, and the default since .NET 4.6 is to use TLS 1.0-1.2, so I've updated that.
The FtpClient class has an override to customise that (say you want to connect to older servers), but it was ignored by the FtpSocketStream class, so I've rectified that as well, making sure that we store the default SslProtocols value in a single place.

Thank you!!

New version published to nuget at last. I was able to easily build it and create the nuget package during the build. Credits added into release notes for the 19.0.0 version. Credits also added here. Thanks for all the help.

Can you please check the nuget package for .NET apps and .NET standard apps since its the first time I'm building via your new workflow?


Add search for virtual disk image

This PR adds search with id functionality for VDIs (similar to search_with_id in VirtualServer).
Hi @SLsthompson ,
Could you please take a look and let me know if this PR needs more work before merging ?
Thanks
Bhavya ( @mbhavya )

Coverage remained the same at 99.762% when pulling 4a82864c16fc23426f8e754874d285d92a5904e0 on bhavyaaha:vdiSearch into 0adc0e4f26251252be7d29234bb2c8758da83504 on softlayer:master.

Coverage increased (+0.06%) to 99.821% when pulling<PHONE_NUMBER>536391c69ad27013fdb28da511577c on mbhavya:vdiSearch into 0adc0e4f26251252be7d29234bb2c8758da83504 on softlayer:master.

@SLsthompson FYA, the checks in this pull request fails only when testing on JRuby19, because of the coveralls->tins dependency (tins requires Ruby 2.0).
So, should we remove jruby19 testing from .travis.yml? Or should we use something other than coveralls for the coverage testing? e.g. simplecov

Coverage remained the same at 99.762% when pulling e2f1f635b6db8e40b656d89ac23303a72a1a3c43 on mbhavya:vdiSearch into 0adc0e4f26251252be7d29234bb2c8758da83504 on softlayer:master.


Update Copyright date.

Signed-off-by: William Lee<EMAIL_ADDRESS>Update Copyright date.

Thanks @william-leez :)
/cc @thaJeztah, is it necessary to update the year on the License and README? I thought this was optional and unnecessary. Feel free to merge this one if you think it's useful :)

@abronan I don't think the end-date is required (but IANAL), however, since it's there, it's nice to update it, so LGTM


src/config.py: Update pydantic to pydantic-settings

In the release of pydantic version 2, the developers have created a separate library for settings and config class called pydantic-settings, more information can be found here: https://docs.pydantic.dev/latest/usage/pydantic_settings
This PR adds pydantic-settings as a dependency in requirements.txt and update from pydantic in src/config.py

@Devansh3712  can you please sign the commit?