HADOOP-19156. ZooKeeper based state stores use different ZK address c…

Description of PR
Currently, the Zookeeper-based state stores of RM, YARN Federation, and HDFS Federation use the same ZK address config hadoop.zk.address. But in our production environment, we hope that different services can use different ZKs to avoid mutual influence.
This jira adds separate ZK address configs for each service.
How was this patch tested?
unit test
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 50s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint 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 12 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 14s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
35m  6s

trunk passed

+1 :green_heart:
compile
21m 17s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
compile
19m  4s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
checkstyle
5m  0s

trunk passed

+1 :green_heart:
mvnsite
6m 23s

trunk passed

+1 :green_heart:
javadoc
5m 28s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
4m 41s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
11m 37s

trunk passed

+1 :green_heart:
shadedclient
40m 19s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 31s

Maven dependency ordering for patch

-1 :x:
mvninstall
0m 29s
/patch-mvninstall-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

-1 :x:
compile
11m 50s
/patch-compile-root-jdkUbuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.txt
root in the patch failed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.

-1 :x:
javac
11m 50s
/patch-compile-root-jdkUbuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.txt
root in the patch failed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.

-1 :x:
compile
11m  8s
/patch-compile-root-jdkPrivateBuild-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.txt
root in the patch failed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.

-1 :x:
javac
11m  8s
/patch-compile-root-jdkPrivateBuild-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.txt
root in the patch failed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.

-1 :x:
blanks
0m  0s
/blanks-eol.txt
The patch has 1 line(s) that end in blanks. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

+1 :green_heart:
checkstyle
4m 26s

the patch passed

-1 :x:
mvnsite
0m 38s
/patch-mvnsite-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

-1 :x:
javadoc
0m 54s
/results-javadoc-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.txt
hadoop-common-project_hadoop-common-jdkUbuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1 with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1 generated 3 new + 0 unchanged - 0 fixed = 3 total (was 0)

+1 :green_heart:
javadoc
3m 27s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

-1 :x:
spotbugs
0m 33s
/patch-spotbugs-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

+1 :green_heart:
shadedclient
43m 19s

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

_ Other Tests _

+1 :green_heart:
unit
20m  7s

hadoop-common in the patch passed.

+1 :green_heart:
unit
0m 56s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
5m 26s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
3m 56s

hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
unit
109m 46s

hadoop-yarn-server-resourcemanager in the patch passed.

-1 :x:
unit
0m 36s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

+1 :green_heart:
asflicense
0m 38s

The patch does not generate ASF License warnings.

410m  1s

Subsystem
Report/Notes

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

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

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

uname
Linux 7aa6fc55505e 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / c373f0f2777313a13015ec4d0a4a34fe571ddeff

Default Java
Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

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

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

modules
C: hadoop-common-project/hadoop-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager hadoop-hdfs-project/hadoop-hdfs-rbf U: .

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
25m 38s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint 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 12 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 32s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
37m 23s

trunk passed

+1 :green_heart:
compile
19m  8s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
compile
18m 40s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
checkstyle
4m 40s

trunk passed

+1 :green_heart:
mvnsite
6m 31s

trunk passed

+1 :green_heart:
javadoc
5m 48s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
5m  9s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
11m 43s

trunk passed

+1 :green_heart:
shadedclient
40m  3s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 32s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m  0s

the patch passed

+1 :green_heart:
compile
18m 16s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javac
18m 16s

the patch passed

+1 :green_heart:
compile
17m 45s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
javac
17m 45s

the patch passed

-1 :x:
blanks
0m  0s
/blanks-eol.txt
The patch has 1 line(s) that end in blanks. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

+1 :green_heart:
checkstyle
4m 36s

the patch passed

+1 :green_heart:
mvnsite
6m 23s

the patch passed

+1 :green_heart:
javadoc
5m 48s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
5m  7s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
12m 48s

the patch passed

+1 :green_heart:
shadedclient
40m  8s

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

_ Other Tests _

+1 :green_heart:
unit
20m 56s

hadoop-common in the patch passed.

+1 :green_heart:
unit
1m 12s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
5m 42s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
4m  8s

hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
unit
108m 48s

hadoop-yarn-server-resourcemanager in the patch passed.

+1 :green_heart:
unit
33m 27s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
1m  1s

The patch does not generate ASF License warnings.

487m 14s

Subsystem
Report/Notes

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

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

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

uname
Linux 35c89bc7ab28 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / e8412cbc2560c66297b9ed05466ccb1e263d9d22

Default Java
Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

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

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

modules
C: hadoop-common-project/hadoop-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager hadoop-hdfs-project/hadoop-hdfs-rbf U: .

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 51s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint 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 12 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 27s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
36m 31s

trunk passed

+1 :green_heart:
compile
19m 57s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
compile
18m 37s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
checkstyle
4m 41s

trunk passed

+1 :green_heart:
mvnsite
6m 34s

trunk passed

+1 :green_heart:
javadoc
5m 52s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
5m 10s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
11m 37s

trunk passed

+1 :green_heart:
shadedclient
40m  9s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 32s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m  0s

the patch passed

+1 :green_heart:
compile
18m 55s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javac
18m 55s

the patch passed

+1 :green_heart:
compile
18m  8s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
javac
18m  8s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
4m 41s

the patch passed

+1 :green_heart:
mvnsite
6m 27s

the patch passed

+1 :green_heart:
javadoc
5m 46s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
5m 13s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
12m 53s

the patch passed

+1 :green_heart:
shadedclient
39m 38s

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

_ Other Tests _

+1 :green_heart:
unit
20m 58s

hadoop-common in the patch passed.

+1 :green_heart:
unit
1m  9s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
5m 22s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
4m  9s

hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
unit
109m 10s

hadoop-yarn-server-resourcemanager in the patch passed.

-1 :x:
unit
34m 51s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

+1 :green_heart:
asflicense
0m 59s

The patch does not generate ASF License warnings.

464m 49s

Subsystem
Report/Notes

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

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

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

uname
Linux 2fb3f408608c 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 689c74a2c9a5db059cc89a9ff523cbdc545eeb97

Default Java
Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

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

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

modules
C: hadoop-common-project/hadoop-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager hadoop-hdfs-project/hadoop-hdfs-rbf U: .

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

_ Prechecks _

+1 :green_heart:
dupname
0m 03s

No case conflicting files found.

+0 :ok:
spotbugs
0m 01s

spotbugs executables are not available.

+0 :ok:
codespell
0m 01s

codespell was not available.

+0 :ok:
detsecrets
0m 01s

detect-secrets was not available.

+0 :ok:
xmllint
0m 01s

xmllint was not available.

+1 :green_heart:
@author
0m 00s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m 00s

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

_ trunk Compile Tests _

+0 :ok:
mvndep
2m 45s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
88m 30s

trunk passed

+1 :green_heart:
compile
38m 38s

trunk passed

+1 :green_heart:
checkstyle
5m 48s

trunk passed

-1 :x:
mvnsite
4m 18s
/branch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in trunk failed.

+1 :green_heart:
javadoc
28m 55s

trunk passed

+1 :green_heart:
shadedclient
197m 28s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
2m 21s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
20m 24s

the patch passed

+1 :green_heart:
compile
35m 50s

the patch passed

+1 :green_heart:
javac
35m 50s

the patch passed

+1 :green_heart:
blanks
0m 01s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
5m 57s

the patch passed

-1 :x:
mvnsite
4m 21s
/patch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

+1 :green_heart:
javadoc
28m 41s

the patch passed

+1 :green_heart:
shadedclient
203m 25s

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

_ Other Tests _

+1 :green_heart:
asflicense
6m 13s

The patch does not generate ASF License warnings.

602m 49s

Subsystem
Report/Notes

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

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

uname
MINGW64_NT-10.0-17763 f0463bf0a8fe 3.4.10-87d57229.x86_64 2024-02-14 20:17 UTC x86_64 Msys

Build tool
maven

Personality
/c/hadoop/dev-support/bin/hadoop.sh

git revision
trunk / 689c74a2c9a5db059cc89a9ff523cbdc545eeb97

Default Java
Azul Systems, Inc.-1.8.0_332-b09

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

modules
C: hadoop-common-project/hadoop-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager hadoop-hdfs-project/hadoop-hdfs-rbf U: .

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

versions
git=2.44.0.windows.1

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

This message was automatically generated.

@liubin101 Thanks for your works. Strong +1 from my side.
Just one concerns, we should consider to be compatible with the old configuration keys. Thanks.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

_ Prechecks _

+1 :green_heart:
dupname
0m 03s

No case conflicting files found.

+0 :ok:
spotbugs
0m 01s

spotbugs executables are not available.

+0 :ok:
codespell
0m 01s

codespell was not available.

+0 :ok:
detsecrets
0m 01s

detect-secrets was not available.

+0 :ok:
xmllint
0m 01s

xmllint was not available.

+1 :green_heart:
@author
0m 00s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m 00s

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

_ trunk Compile Tests _

+0 :ok:
mvndep
3m 43s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
89m 17s

trunk passed

+1 :green_heart:
compile
39m 45s

trunk passed

+1 :green_heart:
checkstyle
6m 06s

trunk passed

-1 :x:
mvnsite
4m 23s
/branch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in trunk failed.

+1 :green_heart:
javadoc
29m 50s

trunk passed

+1 :green_heart:
shadedclient
201m 16s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
2m 14s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
21m 45s

the patch passed

+1 :green_heart:
compile
38m 13s

the patch passed

+1 :green_heart:
javac
38m 13s

the patch passed

+1 :green_heart:
blanks
0m 00s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
6m 15s

the patch passed

-1 :x:
mvnsite
4m 34s
/patch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

+1 :green_heart:
javadoc
29m 22s

the patch passed

+1 :green_heart:
shadedclient
210m 51s

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

_ Other Tests _

+1 :green_heart:
asflicense
6m 21s

The patch does not generate ASF License warnings.

619m 38s

Subsystem
Report/Notes

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

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

uname
MINGW64_NT-10.0-17763 a1636150df2d 3.4.10-87d57229.x86_64 2024-02-14 20:17 UTC x86_64 Msys

Build tool
maven

Personality
/c/hadoop/dev-support/bin/hadoop.sh

git revision
trunk / 689c74a2c9a5db059cc89a9ff523cbdc545eeb97

Default Java
Azul Systems, Inc.-1.8.0_332-b09

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

modules
C: hadoop-common-project/hadoop-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager hadoop-hdfs-project/hadoop-hdfs-rbf U: .

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

versions
git=2.44.0.windows.1

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

This message was automatically generated.

@liubin101 Thanks for your works. Strong +1 from my side. Just one concerns, we should consider to be compatible with the old configuration keys. Thanks.

@Hexiaoqiao Thanks very much for your advice, I will fix it.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 53s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
xmllint
0m  1s

xmllint 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 12 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m  9s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
37m 52s

trunk passed

+1 :green_heart:
compile
19m  5s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
compile
17m 52s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
checkstyle
4m 39s

trunk passed

+1 :green_heart:
mvnsite
6m 29s

trunk passed

+1 :green_heart:
javadoc
5m 48s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
5m  6s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
11m 39s

trunk passed

+1 :green_heart:
shadedclient
40m 25s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 32s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 59s

the patch passed

+1 :green_heart:
compile
18m 27s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javac
18m 27s

the patch passed

+1 :green_heart:
compile
17m 34s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
javac
17m 34s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

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

+1 :green_heart:
mvnsite
6m 29s

the patch passed

+1 :green_heart:
javadoc
5m 45s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
5m 10s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
12m 48s

the patch passed

+1 :green_heart:
shadedclient
39m 40s

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

_ Other Tests _

+1 :green_heart:
unit
21m  5s

hadoop-common in the patch passed.

+1 :green_heart:
unit
1m  9s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
5m 23s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
4m 12s

hadoop-yarn-server-common in the patch passed.

-1 :x:
unit
109m 16s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
hadoop-yarn-server-resourcemanager in the patch failed.

+1 :green_heart:
unit
34m 14s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
1m  1s

The patch does not generate ASF License warnings.

463m  0s

Subsystem
Report/Notes

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

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

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

uname
Linux 465519d1596a 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / f66f77f6c0f86cd3375c6f089aa8cd1f598defa4

Default Java
Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

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

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

modules
C: hadoop-common-project/hadoop-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager hadoop-hdfs-project/hadoop-hdfs-rbf U: .

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 21s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint 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 12 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
0m 20s

Maven dependency ordering for branch

-1 :x:
mvninstall
0m 22s
/branch-mvninstall-root.txt
root in trunk failed.

-1 :x:
compile
0m 22s
/branch-compile-root-jdkUbuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.txt
root in trunk failed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.

-1 :x:
compile
0m 22s
/branch-compile-root-jdkPrivateBuild-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.txt
root in trunk failed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.

-0 :warning:
checkstyle
0m 20s
/buildtool-branch-checkstyle-root.txt
The patch fails to run checkstyle in root

-1 :x:
mvnsite
0m 23s
/branch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in trunk failed.

-1 :x:
mvnsite
0m 22s
/branch-mvnsite-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in trunk failed.

-1 :x:
mvnsite
0m 22s
/branch-mvnsite-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in trunk failed.

-1 :x:
mvnsite
0m 22s
/branch-mvnsite-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-common.txt
hadoop-yarn-common in trunk failed.

-1 :x:
mvnsite
0m 23s
/branch-mvnsite-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common.txt
hadoop-yarn-server-common in trunk failed.

-1 :x:
mvnsite
0m 22s
/branch-mvnsite-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
hadoop-yarn-server-resourcemanager in trunk failed.

-1 :x:
javadoc
0m 22s
/branch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.txt
hadoop-common in trunk failed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.

-1 :x:
javadoc
0m 22s
/branch-javadoc-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkUbuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.txt
hadoop-hdfs-rbf in trunk failed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.

-1 :x:
javadoc
0m 22s
/branch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkUbuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.txt
hadoop-yarn-api in trunk failed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.

-1 :x:
javadoc
0m 22s
/branch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-common-jdkUbuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.txt
hadoop-yarn-common in trunk failed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.

-1 :x:
javadoc
0m 23s
/branch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common-jdkUbuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.txt
hadoop-yarn-server-common in trunk failed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.

-1 :x:
javadoc
0m 22s
/branch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager-jdkUbuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.txt
hadoop-yarn-server-resourcemanager in trunk failed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.

-1 :x:
javadoc
0m 22s
/branch-javadoc-hadoop-common-project_hadoop-common-jdkPrivateBuild-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.txt
hadoop-common in trunk failed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.

-1 :x:
javadoc
0m 22s
/branch-javadoc-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkPrivateBuild-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.txt
hadoop-hdfs-rbf in trunk failed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.

-1 :x:
javadoc
0m 23s
/branch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkPrivateBuild-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.txt
hadoop-yarn-api in trunk failed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.

-1 :x:
javadoc
0m 22s
/branch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-common-jdkPrivateBuild-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.txt
hadoop-yarn-common in trunk failed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.

-1 :x:
javadoc
0m 22s
/branch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common-jdkPrivateBuild-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.txt
hadoop-yarn-server-common in trunk failed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.

-1 :x:
javadoc
0m 22s
/branch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager-jdkPrivateBuild-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.txt
hadoop-yarn-server-resourcemanager in trunk failed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.

-1 :x:
spotbugs
0m 22s
/branch-spotbugs-hadoop-common-project_hadoop-common.txt
hadoop-common in trunk failed.

-1 :x:
spotbugs
0m 23s
/branch-spotbugs-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in trunk failed.

-1 :x:
spotbugs
0m 22s
/branch-spotbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in trunk failed.

-1 :x:
spotbugs
0m 22s
/branch-spotbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-common.txt
hadoop-yarn-common in trunk failed.

-1 :x:
spotbugs
0m 22s
/branch-spotbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common.txt
hadoop-yarn-server-common in trunk failed.

-1 :x:
spotbugs
0m 23s
/branch-spotbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
hadoop-yarn-server-resourcemanager in trunk failed.

+1 :green_heart:
shadedclient
9m 59s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 20s

Maven dependency ordering for patch

-1 :x:
mvninstall
0m 23s
/patch-mvninstall-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
mvninstall
0m 22s
/patch-mvninstall-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

-1 :x:
mvninstall
0m 22s
/patch-mvninstall-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch failed.

-1 :x:
mvninstall
0m 22s
/patch-mvninstall-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-common.txt
hadoop-yarn-common in the patch failed.

-1 :x:
mvninstall
0m 22s
/patch-mvninstall-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common.txt
hadoop-yarn-server-common in the patch failed.

-1 :x:
mvninstall
0m 23s
/patch-mvninstall-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
hadoop-yarn-server-resourcemanager in the patch failed.

-1 :x:
compile
0m 22s
/patch-compile-root-jdkUbuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.txt
root in the patch failed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.

-1 :x:
javac
0m 22s
/patch-compile-root-jdkUbuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.txt
root in the patch failed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.

-1 :x:
compile
0m 22s
/patch-compile-root-jdkPrivateBuild-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.txt
root in the patch failed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.

-1 :x:
javac
0m 22s
/patch-compile-root-jdkPrivateBuild-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.txt
root in the patch failed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 20s
/buildtool-patch-checkstyle-root.txt
The patch fails to run checkstyle in root

-1 :x:
mvnsite
0m 22s
/patch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
mvnsite
0m 23s
/patch-mvnsite-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

-1 :x:
mvnsite
0m 22s
/patch-mvnsite-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch failed.

-1 :x:
mvnsite
0m 22s
/patch-mvnsite-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-common.txt
hadoop-yarn-common in the patch failed.

-1 :x:
mvnsite
0m 22s
/patch-mvnsite-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common.txt
hadoop-yarn-server-common in the patch failed.

-1 :x:
mvnsite
0m 21s
/patch-mvnsite-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
hadoop-yarn-server-resourcemanager in the patch failed.

-1 :x:
javadoc
0m 21s
/patch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.txt
hadoop-common in the patch failed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.

-1 :x:
javadoc
0m 22s
/patch-javadoc-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkUbuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.txt
hadoop-hdfs-rbf in the patch failed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.

-1 :x:
javadoc
0m 22s
/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkUbuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.txt
hadoop-yarn-api in the patch failed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.

-1 :x:
javadoc
0m 23s
/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-common-jdkUbuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.txt
hadoop-yarn-common in the patch failed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.

-1 :x:
javadoc
0m 22s
/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common-jdkUbuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.txt
hadoop-yarn-server-common in the patch failed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.

-1 :x:
javadoc
0m 22s
/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager-jdkUbuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.txt
hadoop-yarn-server-resourcemanager in the patch failed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1.

-1 :x:
javadoc
0m 23s
/patch-javadoc-hadoop-common-project_hadoop-common-jdkPrivateBuild-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.txt
hadoop-common in the patch failed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.

-1 :x:
javadoc
0m 22s
/patch-javadoc-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkPrivateBuild-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.txt
hadoop-hdfs-rbf in the patch failed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.

-1 :x:
javadoc
0m 22s
/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api-jdkPrivateBuild-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.txt
hadoop-yarn-api in the patch failed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.

-1 :x:
javadoc
0m 22s
/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-common-jdkPrivateBuild-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.txt
hadoop-yarn-common in the patch failed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.

-1 :x:
javadoc
0m 23s
/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common-jdkPrivateBuild-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.txt
hadoop-yarn-server-common in the patch failed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.

-1 :x:
javadoc
0m 22s
/patch-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager-jdkPrivateBuild-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.txt
hadoop-yarn-server-resourcemanager in the patch failed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06.

-1 :x:
spotbugs
0m 23s
/patch-spotbugs-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
spotbugs
0m 22s
/patch-spotbugs-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

-1 :x:
spotbugs
0m 22s
/patch-spotbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch failed.

-1 :x:
spotbugs
0m 22s
/patch-spotbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-common.txt
hadoop-yarn-common in the patch failed.

-1 :x:
spotbugs
0m 23s
/patch-spotbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common.txt
hadoop-yarn-server-common in the patch failed.

-1 :x:
spotbugs
0m 22s
/patch-spotbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
hadoop-yarn-server-resourcemanager in the patch failed.

+1 :green_heart:
shadedclient
11m 36s

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

_ Other Tests _

-1 :x:
unit
0m 22s
/patch-unit-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
unit
0m 22s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

-1 :x:
unit
0m 22s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch failed.

-1 :x:
unit
0m 23s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-common.txt
hadoop-yarn-common in the patch failed.

-1 :x:
unit
0m 22s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common.txt
hadoop-yarn-server-common in the patch failed.

-1 :x:
unit
0m 22s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
hadoop-yarn-server-resourcemanager in the patch failed.

+0 :ok:
asflicense
0m 23s

ASF License check generated no output?

32m 38s

Subsystem
Report/Notes

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

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

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

uname
Linux 0f03378a7607 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 260ff827bf731de6129fe287e0007c1db35f61f1

Default Java
Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

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

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

modules
C: hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs-rbf hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager U: .

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

versions
git=2.25.1 maven=3.6.3

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

This message was automatically generated.

@liubin101 Almost look good to me. Also need to update ResourceManagerHA.md / Federation.md / ResourceManagerRestart.md about zk config guide. Thanks.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

_ Prechecks _

+1 :green_heart:
dupname
0m 03s

No case conflicting files found.

+0 :ok:
spotbugs
0m 01s

spotbugs executables are not available.

+0 :ok:
codespell
0m 01s

codespell was not available.

+0 :ok:
detsecrets
0m 01s

detect-secrets was not available.

+0 :ok:
xmllint
0m 01s

xmllint was not available.

+1 :green_heart:
@author
0m 00s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m 00s

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

_ trunk Compile Tests _

+0 :ok:
mvndep
2m 27s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
93m 30s

trunk passed

+1 :green_heart:
compile
43m 26s

trunk passed

+1 :green_heart:
checkstyle
6m 11s

trunk passed

-1 :x:
mvnsite
4m 48s
/branch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in trunk failed.

+1 :green_heart:
javadoc
30m 50s

trunk passed

+1 :green_heart:
shadedclient
208m 53s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
2m 20s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
22m 02s

the patch passed

+1 :green_heart:
compile
38m 32s

the patch passed

+1 :green_heart:
javac
38m 32s

the patch passed

+1 :green_heart:
blanks
0m 00s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
6m 38s

the patch passed

-1 :x:
mvnsite
4m 47s
/patch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

+1 :green_heart:
javadoc
31m 23s

the patch passed

+1 :green_heart:
shadedclient
222m 37s

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

_ Other Tests _

+1 :green_heart:
asflicense
6m 09s

The patch does not generate ASF License warnings.

646m 50s

Subsystem
Report/Notes

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

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

uname
MINGW64_NT-10.0-17763 4260df6a58f1 3.4.10-87d57229.x86_64 2024-02-14 20:17 UTC x86_64 Msys

Build tool
maven

Personality
/c/hadoop/dev-support/bin/hadoop.sh

git revision
trunk / 260ff827bf731de6129fe287e0007c1db35f61f1

Default Java
Azul Systems, Inc.-1.8.0_332-b09

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

modules
C: hadoop-common-project/hadoop-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager hadoop-hdfs-project/hadoop-hdfs-rbf U: .

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

versions
git=2.44.0.windows.1

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

_ Prechecks _

+1 :green_heart:
dupname
0m 05s

No case conflicting files found.

+0 :ok:
spotbugs
0m 01s

spotbugs executables are not available.

+0 :ok:
codespell
0m 01s

codespell was not available.

+0 :ok:
detsecrets
0m 01s

detect-secrets was not available.

+0 :ok:
xmllint
0m 01s

xmllint was not available.

+1 :green_heart:
@author
0m 00s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m 00s

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

_ trunk Compile Tests _

+0 :ok:
mvndep
3m 30s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
126m 51s

trunk passed

+1 :green_heart:
compile
59m 54s

trunk passed

+1 :green_heart:
checkstyle
9m 24s

trunk passed

-1 :x:
mvnsite
7m 14s
/branch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in trunk failed.

+1 :green_heart:
javadoc
46m 17s

trunk passed

+1 :green_heart:
shadedclient
290m 26s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
3m 54s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
33m 56s

the patch passed

+1 :green_heart:
compile
56m 32s

the patch passed

+1 :green_heart:
javac
56m 32s

the patch passed

+1 :green_heart:
blanks
0m 00s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
9m 23s

the patch passed

-1 :x:
mvnsite
7m 16s
/patch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

+1 :green_heart:
javadoc
47m 55s

the patch passed

+1 :green_heart:
shadedclient
316m 49s

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

_ Other Tests _

+1 :green_heart:
asflicense
9m 17s

The patch does not generate ASF License warnings.

911m 40s

Subsystem
Report/Notes

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

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

uname
MINGW64_NT-10.0-17763 d7c133dbab49 3.4.10-87d57229.x86_64 2024-02-14 20:17 UTC x86_64 Msys

Build tool
maven

Personality
/c/hadoop/dev-support/bin/hadoop.sh

git revision
trunk / 260ff827bf731de6129fe287e0007c1db35f61f1

Default Java
Azul Systems, Inc.-1.8.0_332-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6767/6/testReport/

modules
C: hadoop-common-project/hadoop-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager hadoop-hdfs-project/hadoop-hdfs-rbf U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6767/6/console

versions
git=2.44.0.windows.1

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 58s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+0 :ok:
markdownlint
0m  0s

markdownlint 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 12 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 21s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
37m  4s

trunk passed

+1 :green_heart:
compile
19m 50s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
compile
17m 44s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
checkstyle
4m 45s

trunk passed

+1 :green_heart:
mvnsite
7m 11s

trunk passed

+1 :green_heart:
javadoc
6m 25s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
5m 39s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+0 :ok:
spotbugs
0m 34s

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

+1 :green_heart:
shadedclient
38m 10s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 33s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 16s

the patch passed

+1 :green_heart:
compile
18m 58s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javac
18m 58s

the patch passed

+1 :green_heart:
compile
19m  6s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
javac
19m  6s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
4m 38s

the patch passed

+1 :green_heart:
mvnsite
7m  5s

the patch passed

+1 :green_heart:
javadoc
6m 21s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
5m 41s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+0 :ok:
spotbugs
0m 36s

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site has no data from spotbugs

+1 :green_heart:
shadedclient
38m 45s

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

_ Other Tests _

+1 :green_heart:
unit
21m 11s

hadoop-common in the patch passed.

+1 :green_heart:
unit
1m  9s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
5m 21s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
4m 16s

hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
unit
109m 52s

hadoop-yarn-server-resourcemanager in the patch passed.

+1 :green_heart:
unit
34m 10s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
unit
0m 34s

hadoop-yarn-site in the patch passed.

+1 :green_heart:
asflicense
1m  1s

The patch does not generate ASF License warnings.

470m 30s

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6767/6/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets xmllint markdownlint

uname
Linux 61aa43f30264 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 957f15512ff56f923b1e813ade3f061494944830

Default Java
Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6767/6/testReport/

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

modules
C: hadoop-common-project/hadoop-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager hadoop-hdfs-project/hadoop-hdfs-rbf hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6767/6/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

_ Prechecks _

+1 :green_heart:
dupname
0m 04s

No case conflicting files found.

+0 :ok:
spotbugs
0m 01s

spotbugs executables are not available.

+0 :ok:
codespell
0m 01s

codespell was not available.

+0 :ok:
detsecrets
0m 01s

detect-secrets was not available.

+0 :ok:
xmllint
0m 01s

xmllint was not available.

+0 :ok:
markdownlint
0m 01s

markdownlint was not available.

+1 :green_heart:
@author
0m 00s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m 00s

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

_ trunk Compile Tests _

+0 :ok:
mvndep
2m 25s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
94m 06s

trunk passed

+1 :green_heart:
compile
41m 54s

trunk passed

+1 :green_heart:
checkstyle
6m 13s

trunk passed

-1 :x:
mvnsite
4m 52s
/branch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in trunk failed.

+1 :green_heart:
javadoc
35m 25s

trunk passed

+1 :green_heart:
shadedclient
221m 01s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
2m 25s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
23m 54s

the patch passed

+1 :green_heart:
compile
38m 00s

the patch passed

+1 :green_heart:
javac
38m 00s

the patch passed

+1 :green_heart:
blanks
0m 00s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
6m 17s

the patch passed

-1 :x:
mvnsite
4m 31s
/patch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

+1 :green_heart:
javadoc
34m 42s

the patch passed

+1 :green_heart:
shadedclient
222m 28s

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

_ Other Tests _

+1 :green_heart:
asflicense
5m 48s

The patch does not generate ASF License warnings.

658m 35s

Subsystem
Report/Notes

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets xmllint markdownlint

uname
MINGW64_NT-10.0-17763 3044357b75fb 3.4.10-87d57229.x86_64 2024-02-14 20:17 UTC x86_64 Msys

Build tool
maven

Personality
/c/hadoop/dev-support/bin/hadoop.sh

git revision
trunk / 957f15512ff56f923b1e813ade3f061494944830

Default Java
Azul Systems, Inc.-1.8.0_332-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6767/7/testReport/

modules
C: hadoop-common-project/hadoop-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager hadoop-hdfs-project/hadoop-hdfs-rbf hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6767/7/console

versions
git=2.44.0.windows.1

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

This message was automatically generated.

Committed to trunk. Thanks @liubin101, @slfan1989 and @ayushtkn .


Async completions type checking error

Instructor 1.3.7
Python 3.12.3
Here's my example code:
client = instructor.from_litellm(litellm.acompletion, mode=instructor.mode.Mode.PARALLEL_TOOLS)

class Person(BaseModel):
    name: str
    age: int

class Company(BaseModel):
    name: str
    location: str

r = await client.chat.completions.create(
    model="gpt-4o-mini",
    messages=[
        {

            "role": "user",
            "content": """
            John Smith, 29, works for Acme Corporation in San Francisco.
            """

        }
    ],
    response_model=typing.Iterable[Person | Company],
)

for obj in r:
    print(obj)

Pylance gives me these errors:
However this seems to happen even without the parallel tools option

Is there something different I'm supposed to do to get async type hints working correctly?

we encounter the same issue, also with the sync version: No overloads for "create" match the provided arguments.
    client = instructor.from_openai(
        openai.OpenAI(),
        mode=instructor.Mode.PARALLEL_TOOLS,
    )

    result = client.chat.completions.create(
        messages=[{"content": prompt, "role": "system"}],
        response_model=Iterable[Schema],
    )

weirdly the type hints seems to work once Iterable is removed, but that in return breaks the actual logic.


[$500] Web- Wrong path when getting back on workspace settings after reloading

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open website > any workspace chat > open details > click on workspace name to open workspace's settings menu
Click on back icon to get back till chat and remeber the path
Repeat 1st step to reach workspace's settings menu and reload the page
Repeat 2nd step to check path's difference

Expected Result:
Wrong path when getting back on workspace settings after reloading
Actual Result:
Wrong path when getting back on workspace settings after reloading
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: n/a
Reproducible in production?: n/a
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
https://github.com/Expensify/App/assets/93399543/a833ff25-0d23-48d5-b29e-dfdc2e7ada58
Expensify/Expensify Issue URL:
Issue reported by: @mahmudjontoraqulov
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1692266593020639
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~014b85eaf7126eba9f
Upwork Job ID:<PHONE_NUMBER>952188928
Last Price Increase: 2023-09-01

I asked in Slack but didn't get any feedback - could you confirm whether this is a bug or intended @s77rt?

@lschurr We have this similar issue https://github.com/Expensify/App/issues/22041 but it won't handle this case. This is intended for now. Let's close this.

Hi, is this issue solved or not?
I want to work on this case.
Please let me know, thanks.

Wow, do I have to share my email here?

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/sulong

Not overdue. @lschurr We can close this one


fix: update the Makefile so that that install command can execute

Current dependencies on/for this PR:

#1  👈
main

This stack of pull requests is managed by Graphite.


How to make every slides having the height of the highest slide ?

Issue description:
With an option or css rule, how to make every slides having the height of the highest slide ?
Demo link/slider setting:
https://codepen.io/neko2/pen/jOPBGQq
The middle slide has the highest height. The goal is to make the others having the same.
Tiny-slider version:
2.9.2

You can add flex to your slider parent and each child will get flex 1 by default which sets the height to all be equal.
.my-slider {   display: flex; }

Indeed @thewrush thanks. I tried the same but was wrong adding heigth: 100% on the children at the same time.

The display: flex; rule does not work in Edge. In fact, it prevents any slide from rendering at all.
You can do this using the pen above. Just add the display: flex rule to .my-slider and see for yourself. You can even open Dev Tools, remove the above CSS rule and the slides will return.
Edge stats (on Windows 10):


Trying to use with keycloak-passport

I have been trying to use next-auth with this keycloak-passport Strategy. (I did have to modify the strategy's name to be lowercase to be able to test it out)
I can log in no problem and it creates a session. Only problem is, getProfile() doesn't seem to fire at all so the session just contains the csrfSecret but no user. Keycloak recognises I'm already logged in when trying to log in.
Have been trying to debug through what could be happening but couldn't get to the bottom of it. Any direction on what might be the issue would be great. If I get it working would be happy to submit some documentation on it.

I haven't used that strategy before, but in theory they should all work (of course the oAuth spec is a bit vague on the details of profiles, so reality is different).
The getProfile() function should be fired on line 77 of next-auth/src/passport-strategies.js, and passed a profile object as returned by the remote service (even if it's null).
Can you see if your getProfile() function in next-auth.providers.js fires (e.g. console.log) and the 'profile' object in your is null or contains anything?
To debug you could hard code a user object response in getProfile() that looks something like this to see if that helps.
getProfile(profile) {
 console.log("Got profile from keycloak: ", profile)
  return {
    id: "123",
    name: "J Smith"
    email<EMAIL_ADDRESS>  }
}

The fields you need are 'id', 'name' and email. If you don't get an email address from the service (e.g. sites like Twitter don't return it unless you explicitly request it) you can use something like<EMAIL_ADDRESS>Another thing to watch for is some providers require explicit options, like scope, e.g.:
providerOptions: {
  scope: ['profile', 'email']
},

Next.js refreshes the output on the console so can be handy to do something like npm run dev > debug.log | tail -f debug.log to log the output for debugging.

I've just looked at #38 raised by @mBeierl and I think the same issue impacts this strategy.
https://github.com/exlinc/keycloak-passport
It passes a different list of arguments in the callback (accessToken, refreshToken, profile, done)  but next-auth is expecting the strategy to return (req, accessToken, refreshToken, _profile, next).
I thought the method signature for this callback was standardised in all strategies (because it works this way in Google, Facebook and Twitter and a few others) but I guess not in the wild!
It's easy to hack for a specific strategy (e.g. fork the strategy and change what it returns) as a workaround but I'm not sure what the best way to handle different responses in strategies like this is (as there is already too much complexity to configuration and I should be focusing on reducing it :-).
I'll have a think and see what we can do!

Thanks for looking into it 😄
Yeah trying that snippet in the getProfile and no joy. I am testing this out in your example so added a console to line 76 of next-auth/src/passport-strategies.js and it doesn't get fired. Based on your comment I'm assuming this is due to the difference in method signatures?

I'm not sure how you can solve this compatibility issue easily, with maybe having your own version of keycloak-passport. :-(

Lookinking more likely I might just have go this route 😢

The keycloak-passport strategy doesn't seem to do too much, I wonder if a generic oAuth 2 module for Passport (other than err passport-oauth2… there seem to be a few at least!) might work in this case?

Not 100% sure by what you mean here 🤔

Hmm looking at the options that may not be a good idea.
Can you paste in your config for the provider from next-auth/src/passport-strategies.js?
I think I have a fix I can suggest.

 Damn. Nevermind that then.
So err sorry something else is going on with the service. :-(
keycloak-passport uses passport-oauth2 under the hood and there are a bunch of open issues about callbacks not firing  there.  I'm not sure what's going on or how you can fix it, as it seems like it's not something next-auth can fix. :-/
I would maybe as the maintainer of passport-keycloak if they have any tips.

providers.push({
    providerName: 'keycloak',
    Strategy: KeycloakStrategy,
    strategyOptions: {
      host: 'https://www.sie.com',
      authorizationURL:
        'https://www.site.com/auth/realms/daft/protocol/openid-connect/auth',
      tokenURL:
        'https://www.site.com/auth/realms/daft/protocol/openid-connect/token',
      userInfoURL:
        'https://www.site.com/auth/realms/daft/protocol/openid-connect/userinfo',
      realm: 'realm',
      clientID: 'web-client',
      clientSecret: 'SECRET',
      callbackURL: '/auth/callback',
      passReqToCallback: true
    },
    getProfile(profile) {
      console.log('Got profile from keycloak: ', profile);
      return {
        id: '123',
        name: 'J Smith',
        email<EMAIL_ADDRESS>      };
    }
  });

This is my config. No joy with the suggestion 😑

Thanks for the help. I will open an issue over @passport-keycloak. If I make any progress, I will update this issue.

Okies, so you can remove passReqToCallback as it already adds it, but one last thing to try:

Remove callbackURL and let it be set automatically, as the current value (/auth/callback) isn't right.

If you need to set it manually, set it to /auth/oauth/keycloak/callback (you can also specify your servers protocol and hostname, name like: http://localhost:300/auth/oauth/keycloak/callback)

😄 Nice one
So removing the callback and setting my host to http://localhost:300/auth/oauth/keycloak/callback has moved me along. I can now log in and it returns the correct profile. It also updates the session as expected.
Not sure if this is related but if I click log out I now get this screen if trying to log in again:

Hmm no that should not be related, but I'm not sure what's causing that.
You might want to close down your browser, stop and start the service again and try and replicate it.
In development mode, Next.js does hot-reloading and caches pages in Service Workers and browser behaviour can get weird if you stop and start things and the only way to clear it out is to close and re-open the browser. Both those things (which only happen in development mode on Next.js projects) cause weird page refreshes.
PS: Thanks for reminding me a I need to fix a typo on that that example error page (just pushed that).

Tried it in a new browser in production mode and no joy, still not allowing me to log in after logging out. Interestingly if I stop and start the server it authenticates me when I click sign in, so looks like it's not actually logging me out correctly.
But as far as the original issue goes I think we can close it? I will do a bit more digging on this logging out issue and see can I get to the bottom of it. It seems like I am not actually being logged out.
😆 I'm terrible for typos so didn't even notice

Thanks for all the help with this by the way! 💪

You welcome! And great yes, lets close this off so it's easy for anyone to follow if they find it when Googling in case they have the same thing. :-) Happy to help with the separate log out issue!
The logout button code should be pretty simple, so hopefully won't involve too much debugging.
You might want to take look at the handleSignoutSubmit() function in the nextjs-starter project if it helps. You absolutely don't need to set the cookie like it does, but it can be nice user behaviour (as it signs them out but keeps them on the same page).

Did you solve this or have a repo that has a basic implementation of nextjs + keycloak?


FIPS derxxx.h.in in wrong directory

Files like der_digests.h.in are in providers/common/der.  For every other .in file in OpenSSL (all 130 of them), they exist in the same directory where the target file exists.  There is no reason this should be otherwise.

The files in providers/common/der is a set that belongs together.  Contrary to you, I don't think it matters very much if the generated files end up in the same directory or elsewhere.

These caused pain in the check-summing script....

Aha, that...  I'll have a look, configdata.pm's --query should certainly be able to make that much easier

Yup, wasn't so hard.  All that was needed was to stop guessing and use the available database instead.  See #15514

I believe that with #15514, this can be closed?

just move the darn files.  sigh.  openssl source is viewed by many more people, and maintained, than just the under a dozen active developers here on this project.

Something I did discover, though, is that those generated files don't contain the usual autowarn text.

The point of this issue is that "foo.h.in" should be in the same directory as "foo.h"  Just like everything else ".in" is in the same directory as the generated ""
The missing autowarn text is a bug, of course :)

I'm with @richsalz here, we should move the generated headers.  Leave the generated C files since they are in the right place.  I don't care where the .asn1 files but a comment should be included giving their location for files not in the same directory.

There is more than checksumming scripts involved here.

Do tell.
Me, I'm looking at it pragmatically (and in that respect, I find "I don't care where the .asn1 files" a bit flippant).
Right now, all build.info instructions to generate those files are in one place.  Do you suggest spreading that around? Just to show what I'm talking about:
https://github.com/openssl/openssl/blob/43dbe3b72de0ba4ebd20e9e6a2c526ef747326ab/providers/common/der/build.info#L1-L10
These all go together in my view.  What you suggest is splitting them up and spreading that to different locations.

Side note:  Thinking the other way around, I would have no issues whatsoever moving, for example, include/openssl/x509.h.in to crypto/x509, and only have the generated x509.h in include/openssl.

There is no need to move the quoted build.info instructions, you could just use a variable for the header file is you want.  Or move them up a level like doc/build.info for the man1 pages.
The number of people who will look at build.info is much lower than the number of people who will look at .in.h and .h files.
I do not understand why you're so insistent.  We're just asking that foo.h.in be right next to foo.h because that will be most obvious to an external openssl developer/user, and it is consistent.  I am sorry that those arguments fall on deaf ears, or that you think the clarity of the build.info files is more important.

I do not understand why you're so insistent.

Because I view these files are a related set: der_digests_gen.c.in, der_digests.h.in, NIST.asn1, DIGESTS.asn1
So while you're claiming that der_digests.h.in should be right next to der_digests.h, I claim that it should be right next to the set it's related with.
I only brought up the build.info file because that's where the set mentality is most visible.
Different viewpoints.
Speaking of insistence, I'm just as stumped by yours.

So while you're claiming that der_digests.h.in should be right next to der_digests.h, I claim that it should be right next to the set it's related with.

Why?  There is nothing in that .in file but an invocation to an external function.  If der_digests.h.in should be with the related set, why not der_digests.h?
I'm insistent because I am trying to make my point.  If you feel you understood what I am saying, and disagree, oh well. I'll stop.

What @richsalz wrote:

The number of people who will look at build.info is much lower than the number of people who will look at .in.h and .h files.

I'm one of these people.  Perhaps I'm being naïve to believe that I've some experience with OpenSSL.

@levitte the .in files should be in the same place as the output files in general - and what they depend on if not used elsewhere should be with them. If that means we have some copied logic in build.info that doesn't alter that we should be placing things where people would naturally expect to find them. I agree with both @paulidale and @richsalz that these seem to be the odd ones out at not logical - and your arguments don't really make sense to me - unless you placed the output files in that same location (which wouldn't be a logical outcome either).
The related-to-sets-proximity is a much weaker argument than simplicity and clarity and also a much less clear "rule" to follow.
And yes - they should have the auto-generated warning comments too.
My view would be entirely different if all the .in files were grouped together somewhere else - but they aren't.

I will continue to disagree with what's said here, but am not going to oppose a PR


Auto entitlements broke in last update

I've done some digging to figure out the exact issue:

In the last commit, you switched to using a Hash for code sign, and thus return a hash for the identity option instead of the string (see https://github.com/electron-userland/electron-osx-sign/commit/f1b226ac6c22335f8885de74ed49c1d33479e82f)
In the entitlements utility, if ElectronTeamID isn't in Info.plist, you use opts.identity to parse out the value from the identity option (see https://github.com/electron-userland/electron-osx-sign/blob/master/util-entitlements.js#L53)
Being as the identity value is now a Hash instead of the identity string, this fails and causes an incorrect value to be added to com.apple.security.application-groups array, even if the correct value already exists

One other note: when using electron-builder, the identity is actually passed as an option, so it would probably to use that rather than looking in the Info.plist

Hi @feens, thanks for reporting this issue! I will post a fix for this shortly.

@feens, I've released v0.4.6 which should address this issue since v0.4.5. 👍


Using QueueTaskDispatcher to block jobs using a locked resource before deploying to node

Hi,
I don't know if I'm writing this in the correct place, but I have been wondering about how to solve the following problem:
Given:
A declarative Jenkinsfile 'A' that references label 'B':
Pipeline { agent { label: 'B'} ... }
One of the stages in the Pipeline takes Lock 'L'.
When:

There exists N jobs using Jenkinsfile 'A'
K nodes with labels 'B'

Then:
If any job of the set N takes the lock 'L', I want the rest  N-1 to be blocked with CauseOfBlockage set to BecauseLabelIsBusy.
So only 1 node should be running and the rest K-1 should be free for other jobs of another set to execute on.
Note: This is needed to lock resources to different hardware setups, in reality the lock string is a parameter passed by the job. Some jobs don't need any resource and thus will pass BUILD_TAG as a unique lock string.
This way we should be able to have higher utilization of the nodes and avoid having dedicated nodes for specially constrained jobs.
I have been looking around and I found two plugins that if combined in someway might give a good solution:

Lockable plugin (to manage the locking mechanism)
Build-blocker-plugin (to hook to QueueTaskDispatcher extension point)

Am I looking in the right direction? or can this be totally done by the Lockable plugin?
Thank you in advance for your feedback!

@maljaberi I don't use declarative pipelines, I use full groovy pipelines but this is something you can do with only this plugin.
Just make sure you don't take a node until you have acquired the lock. Using full pipeline this would mean:
lock(label: 'L') {
    node('B') {
        ...
    }
}

@dcendents  This does not block other jobs from allocating other executors with label 'B'. For my case, each executor runs on a different node.
I think I need something to lock on the label B itself, in a way to block jobs from being scheduled.
Btw, what is the difference between declarative and fully groovy pipelines?

@maljaberi Then I don't understand your use case. I though you said you wanted the rest (K-1) to be free to run other jobs.
In my opinion node labels should reflect capabilities to restrict where a job can be executed successfully. The lock plugin should be used to make sure you don't use more resources than are available (licenses, physical hardware, etc). Sometimes it can be hard to mix both so maybe make sure you use the same labels on both.
Job A requires resources with label B, if it acquires it it will require to run on a node with label B. If no node is available it will be in the queue until a node is free, during that time no one else will be able to lock resource B but other jobs already in the queue might get to run on node B before A.
If you want to reserve node B for jobs that acquire lock on resource B, change the node usage to run only jobs that match the label.
Finally the right name for fully groovy pipelines is "Scripted Pipelines". You can see the difference between the two here: https://jenkins.io/doc/book/pipeline/syntax/

Then I don't understand your use case. I though you said you wanted the rest (K-1) to be free to run other jobs.

yes, I want them to run other jobs not from the N jobs that require the lock to a hardware resource

In my opinion node labels should reflect capabilities to restrict where a job can be executed successfully. The lock plugin should be used to make sure you don't use more resources than are available

We don't disagree here :)
Maybe an example of the declarative pipeline will be more clear to discuss about:
pipeline {   agent { label: 'B' }   stages {       stage(1) { ... }       stage(2) {           lock ('L') {...}       }       stage(3) {...}    } }
Declarative pipeline requires me to define an executor to run in for the entire pipeline, so if I use your segguestion with lock ('L') { node('B') { ... } } in stage 2 it will only allocate another executor, so now I'm allocating twice as many.
Now in declarative, I cannot enclose the whole pipeline with a lock.
Nor can I enclose the 'stages' section with a lock. It will not help either because the job has already been scheduled in the start of the pipeline.
Conceptually I want to be able to add an option to the agent section telling it to lock the resource before scheduling the job, something like `agent { label: 'B' lock:'L' }
It looks like a limitation in the declarative pipeline?

Yes I believe you will need to switch to scripted pipelines if you want to lock first and then take an executor (node). The advantage of the scripted pipelines is if your jobs are all similar, you can define a single script and add conditional blocks, that's what I do (single script, over 100 jobs, mostly maven, a few ants, a few don't have unit tests, etc)
Example:
// Job specific configuration
def hasUnitTests = true
def hasIntegrationTests = true
def gitUrl = 'http://...'
def buildCommand = 'mvn clean install'
etc

// Global script
node {
  stage("compile") {
    // git clone
    // sh buildCommand
    if (hasUnitTests) {
      junit ...
      jacoco ...
    }
  }
}

if (hasIntegrationTests) {
  lock('wildfly') {
    node {
      stage("integration tests") {
        // git clone (might not get the previous workspace)
        ...
      }
    }
  }
}

...

the lock plugin guarantees the execution will wait there until the lock is acquired (single job if locking by name or multiple jobs if locking by label). The nodes are free to process all the node blocks from your jobs as the pipelines get executed.
In my example above, the jobs will always compile and execute unit tests, but only 1 job at a time will be able to execute its integration tests. Jobs without integration tests will never be blocked.

Thank you for sharing your method.
I use same pipeline too, it's defined as a global variable that then is imported as a library in a Jenkins file that will call the pipeline variable with different parameters for each job, one of which is the lock string.
 Is this achievable in someway? If yes, can you guide me where to start?

I think the idea discussion above misses one crucial point: if you want the node which fulfills "node label B" to only be used by one build at a time to avoid conflicts, you can define its node properties as having one executor (it may run parallel make or whatever as children of that executor thread). That way the example pipeline above would first lock a resource (say printer), then get a node by label (say, has printer drivers), and while it uses that node nobody else can use it, neither by name nor by label match - the only executor there is busy. There may be many other similar nodes with same label that would still be available, one executor each...


Release roadmap

Feel free to modify/suggest modifications for the release. Strictly bounded with #8
Will it be v2.0.0 or v1.1.0?

[ ] repository cleanup #31
[ ] quotas (admin api)
…

There are no roadmaps for this SDK yet, closing this we will get to it when we can.


add flags for headscale serve to provide initial api key

Just played around to check one of the possible solutions to https://github.com/juanfont/headscale/issues/662.
Here i introduced 3 new flags for headscale serve command: api-key-prefix, api-key-pass and api-key-expiration. Together they allow to save pre-generated API key into DB to use it later for authentication.

Another, probably better, idea is to introduce new command: headscale apikeys save --prefix<> --password<> --expiration<>. That would be more flexible.

I agree. I think the place to create predefined api keys is in the apikeys subcommand. serve is... well... to serve the server.

I dont think we should implement this, comment in the issue.

Going to close this one, as we need to rethink a bit how to do it.


proxy support

PR replacing #155 .Due to the commits done for testing Travis in GitHub, this PR will be squashed.

We also need to add the documentation:

the httpProxy param in config.yml;
the noProxy option for all the components;
the -x option in generate prefixes;

I can't push my changes directly to this repo (no access rights). I've pushed my commits to our fork here: https://github.com/criteo-forks/BGPalerter/commits/criteo-forks/dev
Should I re-submit another PR ?

No, thanks, I will merge them.

Thanks for your work (and sorry for the multiple branches). I think we are good to go. The only thing I think it is missing is to "block" outgoing traffic during the proxy test. On the other side, if the proxy is set but not configured properly the app fails and doesn't work so the test fails anyway. I think this is not a blocking point and we can merge this right now.

I was thinking about the same point, the proxy test is partial compared to the main one. We are not testing and checking that all modules are going through the proxy.
I don't have a precise idea of how we could perform this, however here are some suggestions :

watch all requests received by anyproxy and raised an error if a request has not been seen by anyproxy (but implies to run anyproxy as an npm module, and it doesn't seem trivial).
filter in Travis by allowing only HTTP proxy to go to the Internet. I don't know how we could segment these two services (proxy and BGPalerter) from a network aspect in Travis, maybe we could accomplish this with the use of docker.

Anyway, I guess it's a good start. If you wish, we can test the pre-release in our environment and give you feedback. And thank you very much for the refactoring, the code looks much better than my first attempt.

Testing in your environment would be great. Could you tell me if you run the source code, the binary, or docker? So I can provide you with the fastest way to deploy the dev version.

The binary for Linux would be perfect.

Easy version: download this (zipped due to GitHub restrictions on attached file types, unzip it)
To compile it yourself, do:
git clone git@github.com:nttgin/BGPalerter.git
git checkout dev
npm run build

The compiled version will be in bin/. More info here and here.
Since the latest release was some days ago, the next pre-release will be in some weeks. I hope this can help you in the meanwhile.


[Feature] Sellable plots in Admin Claimed Areas

Subdivision in claimed area is possible, perhaps a way to integrate these subdivisions into the economy's of servers for towns among other things. Possibly

Subdivisions selling for money
A tax/charge system that can be triggered daily or weekly

Latest builds support buy/selling of claims. There is also tax/bank system. Read wiki for further info.


[YUNIKORN-1995] Preemption CheckPreemptionQueueGuarantee need to compare aggregated Victims with ask resource

What is this PR for?
Preemption CheckPreemptionQueueGuarantee need to compare aggregated Victims with ask resource
PR try to fix following problems:

Compare the aggregated PotentialVictims, to see if it is enough to fit the ask resource.
And about the aggregated process, make sure preempted queue after preempted, it should be larger than the guaranteed resource.

What type of PR is it?

[ ] - Bug Fix
[x] - Improvement
[ ] - Feature
[ ] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[ ] - Task

What is the Jira issue?

Open an issue on Jira https://issues.apache.org/jira/browse/YUNIKORN-1995
Put link here, and add [YUNIKORN-Jira number] in PR title, eg. [YUNIKORN-2] Gang scheduling interface parameters

How should this be tested?
Screenshots (if appropriate)
Questions:

[ ] - The licenses files need update.
[ ] - There is breaking changes for older versions.
[ ] - It needs documentation.

Hi @craigcondit, @wilfred-s
I am not sure if we need to fix about the queue check for preemption, i push a draft code about this.
And one question about the unit tests errors,
For example, when the preemption ask in the queue root.A, it preemption other queue's asks such as queue root.b, if we need to make sure after preempting other queues, the preemption ask's queue root.A not equal or exceed the guaranteed resources?
And if we can let root.A just equal to the guaranteed resource? I see unit test errors, the unit test case is after root.a preempt other asks, it will just equal to the guaranteed resources, but not execeed.

Thank you, @craigcondit, for explanation, close this PR, duplicated with @lixmgl  jira.


[QUESTION] Maybe an issue ? Contrast slider

Hello, first off, I freakin love this extension! Lots of potential.
Second, I think the contrast slider has some issues because I've tried with all the settings with XYZ grids, and the contrast doesn't seem to have any major impact. Which is a shame because I would love to choose how much contrast the output images have by either lowering it to make the image more flat, or increasing it for more depth.
How come ?

The latest commit (https://github.com/Haoming02/sd-webui-vectorscope-cc/commit/c2da3b97109a61ca73a47c36498d52be1deff66e) attempted to fix this

Sampler: DPM++ 2M Karras
Hires. fix: Enabled
Noise: Multi-Res Abs.
Scaling: Cos

Sampler: Euler a
Alt: Enabled
Scaling: 1 - Cos

I'll make some tests!


chore(package): update npm-pkgbuild to version 5.2.1

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Localize to French

Confirm that machine translations of resources  are correct using Multilingual App Toolkit
Confirm that resources.js French string is correct
Translate about.FR.html file
Translate Google Play Store text:

Google Play Store Text:
App name*
10 / 50 chars
This is how your app will appear on Google Play. It should be concise and not include price, rank, any emoji or repetitive symbols.
Sketch 360
Short description
77 / 80 chars
A short description for your app. Users can expand to view your full description.
Create 360-degree panoramic sketches that can easily be shared as 360 photos.
Full description*
1333 / 4000 chars
Sketch 360: A Microsoft Garage Project
Sketch 360 helps you easily create 360 degree panoramic sketches, which are useful when you want to create a quick sketch of a space, real or virtual, when modeling might take too long.
Whether you are an architect, a VR designer, an urban sketcher, a 3D game designer or a 360 video producer, you can easily construct an accurate sketch from a single viewpoint that's easily shareable online using Sketch 360.
Draw on one pane using equirectangular grid and stencils as guides.  The stencils help you draw the vertical and curved horizontal lines that end up looking straight when seen in 360.
As you sketch on the drawing pane, the sketch is projected onto the inside of a sphere with you at the center, rotating the 360 view to point at the latest sketch stroke.  You can also use the tilt and rotation of your device to determine the gaze of a virtual window pane.
Works great with multi-screen devices and devices that support pressure-sensitive pens like the Microsoft Surface Duo.
Export these images as viewable as 360 degree photos on sites like Facebook.com, Adobe Lightroom, Kuula.co or apps like VR Media Player.
Sketch 360 is a Microsoft Garage project. The Microsoft Garage turns fresh ideas into real projects. Learn more about The Garage at: http://microsoft.com/garage

Translate the XLF file instead of the resx file.

Closed


FP for FLD_NEW_FUNDING bot

https://app.forta.network/alerts/0xba76b6570c8309147552be7f5df2220abd51078556bd715d80289a7948b3029f (binance funding, cexes with proper kyc shouldn't be alerted on)
https://app.forta.network/alerts/0x81d1587e6b7d2788499204d45cf45beb53697790991ffb640260694480433d57 (uniswap tx)

Closing this one considering the mentioned bot is no longer part of the AD

Closing this one considering the mentioned bot is no longer part of the AD


text-decoration: underline  problem

when i set div  css text-decoration: underline and  a big font-size such as 30px，and then html2canvas this，underline in this canvas do not match to dom。
example: https://jsfiddle.net/18915788061/9xgjrmLo/8/

Hi, I have the same issue on Chrome. Is there any workaround?


Add batmat to support-core releasers

Description
Add myself to the list of people allowed to release the support-core plugin.
@jglick advised me to do so in https://github.com/jenkinsci/support-core-plugin/pull/89#issuecomment-264034017 and @christ66 did the same in private.
Permissions pull request checklist
Always

[x] Add link to plugin/component Git repository in description above

For a newly hosted plugin only

[ ] Add link to resolved HOSTING issue in description above

For a new permissions file only

[ ] Make sure the file is created in permissions/ directory
[ ] artifactId (pom.xml) is used for name (permissions YAML file).
[ ] groupId / artifactId (pom.xml) are correctly represented in path (permissions YAML file)
[ ] Check that the file is named plugin-${artifactId}.yml for plugins

When adding new uploaders (this includes newly created permissions files)

[x] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[x] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[x] All newly added users have logged in to Artifactory at least once

Pretty obvious endorsement from Jesse there.


MXNet Neural Network performance improvements (~25% reduced runtime)

Issue #, if available:
Description of changes:
nd.sum(loss).asscalar() is doing implicit conversion tonumpy(), which is expensive (especially on GPU). Computing everything in NDArray speeds up computation. This problem exists in other parts of the NN training loop (scoring), but not as severe since loss is computed on batch level.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-174-1 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-174/1/index.html

Nice find!  Can you make the analogous changes in the training function in tabular_nn_trial.py which is used for HPO:
https://github.com/awslabs/autogluon/blob/master/autogluon/utils/tabular/ml/models/tabular_nn/tabular_nn_trial.py
And then verify there are no bugs and the speedup persists with hyperparameter_tune = True?
To do this easily, you can run:  python tests/unittests/test_tabularHPO.py

Job PR-174-2 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-174/2/index.html

I updated HPO trials too. However, in the fast mode the number of batches in trials is very low and the improvement effects are not visible clearly. The speedup is mostly noticable in tabular data with lots of rows. Training 3 iterations on the following dataset: 582348 examples, 6 features (4 vector, 2 embedding, 0 language) went from 83s to 65s.

Job PR-174-4 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-174/4/index.html

@jwmueller Does the code look good to you?

Job PR-174-8 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-174/8/index.html

@jwmueller Does the code look good to you?

yes am discussing it with Alex offline, will merge when confirmed that it won't cause any potential issues.

Impacts of this change on a few problems (20 n_repeat 10 fold (200 NN models trained):
1630s -> 1408s
1667s -> 1459s
289s -> 275s
Improvements are stable and consistent across datasets. No issues have been found on any dataset.


Persist lastEventId and lastBattleId in a temp file

Persist these values in a temp file so the bot does not forget theses values when it restarts.

Won't fix: heroku apps are ephemeral, so tmp files will be deleted.
Database is also not good.


Tabs are only for up to V2.1 need 3.1

Issue description
The .NET Core documentation, eg dotnet publish command, only is for V2.1 and below. Need a 3.1 tab, even if nothing is changed.
Target framework
Check the .NET target framework(s) being used, and include the version number(s).

[ x] .NET Core  3.1
[ ] .NET Framework
[ ] .NET Standard

If using the .NET Core SDK, include dotnet --info output. If using .NET Framework without the .NET Core SDK, include info from Visual Studio's Help > About Microsoft Visual Studio dialog.

Update documentation for V3.1

@djaus2  The .NET Core CLI documentation was recently updated for 3.1.  Which articles does this issue refer to that aren't yet updated?

OK,
I must have had some older version in my browser cache ??
https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-publish
Is updated.
From: Tom Dykstra<EMAIL_ADDRESS>Sent: Saturday, 29 February 2020 7:53 AM
To: dotnet/docs<EMAIL_ADDRESS>Cc: David Jones (MVP<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [dotnet/docs] Tabs are only for up to V2.1 need 3.1 (#17242)
@djaus2https://github.com/djaus2 The .NET Core CLI documentation was recently updated for 3.1. Which articles does this issue refer to that aren't yet updated?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/dotnet/docs/issues/17242?email_source=notifications&email_token=AC7U2EI2WIQ6AS4TXXITOMDRFF2S7A5CNFSM4K42F72KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENKDZBI#issuecomment-592723077, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC7U2EMITJFB6AGVCTCADSDRFF2S7ANCNFSM4K42F72A.

OK
Checked https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-publish
That is OK


⚠ ETF has degraded performance

In 62ce635, ETF (https://markets.hankyung.com/equity-product/etf) experienced degraded performance:

HTTP code: 200
Response time: 5242 ms

Resolved: 거래대금 performance has improved in e05221d.


Use the stringToBytes helper function in more places

Rather than manually reimplementing, more-or-less, this functionality in a few spots we can simply use the existing helper function instead.

/botio unittest

Looks good; thanks!