HDFS-16901: RBF: Propagates real user's username via the caller context, when a proxy user is being used.

HDFS-16901: RBF: Propagates real user's username via the caller context, when a proxy user is being used.

Description of PR
If the router receives an operation from a proxyUser, it drops the realUser in the UGI and makes the routerUser the realUser for the operation that goes to the namenode.
In the namenode UGI logs, we'd like the ability to know the original realUser.
The router should propagate the realUser from the client call as part of the callerContext.
How was this patch tested?
New test case : TestRouterRpc#testRealUserPropagationInCallerContext
For code changes:

[ X] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?

Before this patch the namenode audit log would show

ugi= via ,......,callerContext=...

After this patch

ugi= via ,......,callerContext=...,realUser:

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 48s

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.

+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 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 23s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
33m 29s

trunk passed

+1 :green_heart:
compile
25m  9s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
21m 34s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
4m  5s

trunk passed

+1 :green_heart:
mvnsite
2m 30s

trunk passed

-1 :x:
javadoc
1m  6s
/branch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-common in trunk failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
1m 46s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m  4s

trunk passed

+1 :green_heart:
shadedclient
27m 17s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 53s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 12s

the patch passed

+1 :green_heart:
compile
29m 24s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
29m 24s

the patch passed

+1 :green_heart:
compile
21m 40s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
21m 40s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
3m 54s

the patch passed

+1 :green_heart:
mvnsite
2m 26s

the patch passed

-1 :x:
javadoc
0m 59s
/patch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-common in the patch failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
1m 44s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 19s

the patch passed

+1 :green_heart:
shadedclient
27m 22s

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

_ Other Tests _

+1 :green_heart:
unit
18m 24s

hadoop-common in the patch passed.

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

+1 :green_heart:
asflicense
0m 52s

The patch does not generate ASF License warnings.

289m 56s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.federation.router.TestRouterRPCMultipleDestinationMountTableResolver

Subsystem
Report/Notes

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

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

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

uname
Linux 078843e37bfa 4.15.0-200-generic #211-Ubuntu SMP Thu Nov 24 18:16:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 27c02a95a946d3b36b1f649d782a1730ce2543a1

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

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

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5346/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
12m  2s

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.

+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 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 25s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
30m 50s

trunk passed

+1 :green_heart:
compile
23m  2s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
20m 25s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
4m 17s

trunk passed

+1 :green_heart:
mvnsite
2m 45s

trunk passed

-1 :x:
javadoc
1m 14s
/branch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-common in trunk failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
2m  2s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 11s

trunk passed

+1 :green_heart:
shadedclient
24m 29s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 28s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 45s

the patch passed

+1 :green_heart:
compile
22m 23s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
22m 23s

the patch passed

+1 :green_heart:
compile
20m 20s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
20m 20s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

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

+1 :green_heart:
mvnsite
2m 40s

the patch passed

-1 :x:
javadoc
1m  6s
/patch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-common in the patch failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
2m  1s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 26s

the patch passed

+1 :green_heart:
shadedclient
24m 13s

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

_ Other Tests _

+1 :green_heart:
unit
18m 19s

hadoop-common in the patch passed.

+1 :green_heart:
unit
22m 41s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
1m  1s

The patch does not generate ASF License warnings.

271m  9s

Subsystem
Report/Notes

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

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

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

uname
Linux 325d6a6bb0be 4.15.0-200-generic #211-Ubuntu SMP Thu Nov 24 18:16:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / b1e400f91cceb13183c1997346af3ccfafd6a23a

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

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

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5346/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

+0 :ok:
reexec
0m 54s

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.

+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 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m  1s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
33m 56s

trunk passed

+1 :green_heart:
compile
25m 10s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
21m 43s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
4m 38s

trunk passed

+1 :green_heart:
mvnsite
2m 41s

trunk passed

-1 :x:
javadoc
1m  7s
/branch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-common in trunk failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
1m 45s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m  4s

trunk passed

+1 :green_heart:
shadedclient
26m 44s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 23s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 46s

the patch passed

+1 :green_heart:
compile
24m 33s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
24m 33s

the patch passed

+1 :green_heart:
compile
21m 43s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
21m 43s

the patch passed

+1 :green_heart:
blanks
0m  1s

The patch has no blanks issues.

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

+1 :green_heart:
mvnsite
2m 38s

the patch passed

-1 :x:
javadoc
0m 59s
/patch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-common in the patch failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
1m 45s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 19s

the patch passed

+1 :green_heart:
shadedclient
26m 39s

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

_ Other Tests _

+1 :green_heart:
unit
18m  2s

hadoop-common in the patch passed.

+1 :green_heart:
unit
33m  3s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 54s

The patch does not generate ASF License warnings.

282m 44s

Subsystem
Report/Notes

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

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

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

uname
Linux 2fda639ab79f 4.15.0-200-generic #211-Ubuntu SMP Thu Nov 24 18:16:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / dcbf0c9cf2a8259b31364f23739f6115c56d622a

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

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

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5346/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
17m 25s

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.

+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 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m  5s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
33m 28s

trunk passed

+1 :green_heart:
compile
25m 15s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
21m 43s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
4m 28s

trunk passed

+1 :green_heart:
mvnsite
2m 34s

trunk passed

-1 :x:
javadoc
1m  7s
/branch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-common in trunk failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
1m 46s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m  6s

trunk passed

+1 :green_heart:
shadedclient
26m 40s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 24s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 46s

the patch passed

+1 :green_heart:
compile
24m 29s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
24m 29s

the patch passed

+1 :green_heart:
compile
21m 44s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
21m 44s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

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

+1 :green_heart:
mvnsite
2m 26s

the patch passed

-1 :x:
javadoc
0m 59s
/patch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-common in the patch failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
1m 44s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 21s

the patch passed

+1 :green_heart:
shadedclient
27m 17s

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

_ Other Tests _

+1 :green_heart:
unit
18m 21s

hadoop-common in the patch passed.

+1 :green_heart:
unit
34m  9s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 53s

The patch does not generate ASF License warnings.

300m 27s

Subsystem
Report/Notes

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

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

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

uname
Linux e021a107696b 4.15.0-200-generic #211-Ubuntu SMP Thu Nov 24 18:16:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / b1e400f91cceb13183c1997346af3ccfafd6a23a

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

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

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5346/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 49s

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.

+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 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 17s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
37m 34s

trunk passed

+1 :green_heart:
compile
37m 36s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
40m 50s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
6m 35s

trunk passed

+1 :green_heart:
mvnsite
4m 39s

trunk passed

+1 :green_heart:
javadoc
3m 26s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javadoc
2m 56s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
6m 43s

trunk passed

+1 :green_heart:
shadedclient
38m  9s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 39s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 36s

the patch passed

+1 :green_heart:
compile
35m 10s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
35m 10s

the patch passed

-1 :x:
compile
10m 30s
/patch-compile-root-jdkPrivateBuild-1.8.0_352-8u352-ga-1~20.04-b08.txt
root in the patch failed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08.

-1 :x:
javac
10m 30s
/patch-compile-root-jdkPrivateBuild-1.8.0_352-8u352-ga-1~20.04-b08.txt
root in the patch failed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

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

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

+1 :green_heart:
javadoc
2m 23s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javadoc
2m  8s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
5m 42s

the patch passed

-1 :x:
shadedclient
28m 48s

patch has errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
21m 39s
/patch-unit-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch passed.

+1 :green_heart:
unit
40m 40s

hadoop-hdfs-rbf in the patch passed.

-1 :x:
asflicense
0m 54s
/results-asflicense.txt
The patch generated 1 ASF License warnings.

351m  2s

Reason
Tests

Failed junit tests
hadoop.metrics2.source.TestJvmMetrics

hadoop.metrics2.sink.TestRollingFileSystemSinkWithLocal

Subsystem
Report/Notes

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

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

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

uname
Linux 409f237df2ce 4.15.0-200-generic #211-Ubuntu SMP Thu Nov 24 18:16:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / bcf5a8a9e0bd353ee156cc4fdb2f17870b0ca7bd

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

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

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5346/5/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.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 47s

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.

+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 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
20m 56s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
33m 34s

trunk passed

+1 :green_heart:
compile
25m 12s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
21m 41s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
4m 10s

trunk passed

+1 :green_heart:
mvnsite
2m 48s

trunk passed

+1 :green_heart:
javadoc
2m  6s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javadoc
1m 50s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 47s

trunk passed

+1 :green_heart:
shadedclient
28m 41s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 23s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 46s

the patch passed

+1 :green_heart:
compile
24m 29s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
24m 29s

the patch passed

+1 :green_heart:
compile
21m 44s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
21m 44s

the patch passed

+1 :green_heart:
blanks
0m  1s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
3m 50s

the patch passed

+1 :green_heart:
mvnsite
2m 28s

the patch passed

+1 :green_heart:
javadoc
1m 46s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javadoc
1m 46s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 20s

the patch passed

+1 :green_heart:
shadedclient
27m  1s

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

_ Other Tests _

+1 :green_heart:
unit
18m 25s

hadoop-common in the patch passed.

+1 :green_heart:
unit
34m 16s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 52s

The patch does not generate ASF License warnings.

292m  3s

Subsystem
Report/Notes

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

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

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

uname
Linux 0de0816eb63b 4.15.0-200-generic #211-Ubuntu SMP Thu Nov 24 18:16:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 9e39cb1f86ceb5d60116e8b6f1121d4fc3980c11

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

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

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5346/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

+0 :ok:
reexec
0m 39s

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.

+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 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
17m 26s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
30m 57s

trunk passed

+1 :green_heart:
compile
23m 11s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
20m 36s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
3m 46s

trunk passed

+1 :green_heart:
mvnsite
2m 36s

trunk passed

+1 :green_heart:
javadoc
2m  9s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javadoc
1m 55s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 11s

trunk passed

+1 :green_heart:
shadedclient
23m 52s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 28s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 47s

the patch passed

+1 :green_heart:
compile
26m 47s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
26m 47s

the patch passed

+1 :green_heart:
compile
26m 15s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
26m 15s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
5m 30s

the patch passed

+1 :green_heart:
mvnsite
2m 53s

the patch passed

-1 :x:
javadoc
0m 32s
/patch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-common in the patch failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

-1 :x:
javadoc
0m 40s
/patch-javadoc-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
hadoop-hdfs-rbf in the patch failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

-1 :x:
javadoc
0m 39s
/patch-javadoc-hadoop-common-project_hadoop-common-jdkPrivateBuild-1.8.0_352-8u352-ga-1~20.04-b08.txt
hadoop-common in the patch failed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08.

-1 :x:
javadoc
0m 40s
/patch-javadoc-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkPrivateBuild-1.8.0_352-8u352-ga-1~20.04-b08.txt
hadoop-hdfs-rbf in the patch failed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08.

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

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

+1 :green_heart:
shadedclient
20m 17s

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

_ Other Tests _

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

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

+0 :ok:
asflicense
0m 40s

ASF License check generated no output?

207m  5s

Subsystem
Report/Notes

Docker
ClientAPI=1.42 ServerAPI=1.42 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5346/7/artifact/out/Dockerfile

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

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

uname
Linux 429a5671b10b 4.15.0-200-generic #211-Ubuntu SMP Thu Nov 24 18:16:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 1e7a834e71711477d7a7bbd7dc615f73e3ea799d

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

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

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5346/7/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 40s

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.

+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 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
16m  2s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
31m 18s

trunk passed

+1 :green_heart:
compile
23m  2s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
20m 25s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
3m 45s

trunk passed

+1 :green_heart:
mvnsite
2m 44s

trunk passed

+1 :green_heart:
javadoc
2m 11s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javadoc
2m  2s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 10s

trunk passed

+1 :green_heart:
shadedclient
24m 28s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 29s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 46s

the patch passed

+1 :green_heart:
compile
22m 28s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
22m 28s

the patch passed

+1 :green_heart:
compile
20m 24s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
20m 24s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
3m 37s

the patch passed

+1 :green_heart:
mvnsite
2m 41s

the patch passed

+1 :green_heart:
javadoc
2m  2s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javadoc
2m  4s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 21s

the patch passed

+1 :green_heart:
shadedclient
24m 33s

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

_ Other Tests _

+1 :green_heart:
unit
18m 23s

hadoop-common in the patch passed.

-1 :x:
unit
23m 23s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
1m  4s

The patch does not generate ASF License warnings.

261m 37s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.federation.router.TestRouterRpcMultiDestination

hadoop.hdfs.server.federation.router.TestRouterRpc

hadoop.hdfs.server.federation.router.TestRouterRetryCache

Subsystem
Report/Notes

Docker
ClientAPI=1.42 ServerAPI=1.42 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5346/8/artifact/out/Dockerfile

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

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

uname
Linux 52d2e4187c38 4.15.0-200-generic #211-Ubuntu SMP Thu Nov 24 18:16:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 137b123ad3000a6117dc250cfe43ac03b52d8cf6

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5346/8/testReport/

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5346/8/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 54s

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.

+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 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
18m 44s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
33m 59s

trunk passed

+1 :green_heart:
compile
25m 11s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
23m 40s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
3m 58s

trunk passed

+1 :green_heart:
mvnsite
2m 37s

trunk passed

+1 :green_heart:
javadoc
1m 57s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javadoc
1m 44s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 23s

trunk passed

+1 :green_heart:
shadedclient
29m  1s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 27s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 59s

the patch passed

+1 :green_heart:
compile
29m 26s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
29m 26s

the patch passed

+1 :green_heart:
compile
22m 42s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
22m 42s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
3m 56s

the patch passed

+1 :green_heart:
mvnsite
2m 28s

the patch passed

+1 :green_heart:
javadoc
1m 44s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javadoc
1m 45s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 21s

the patch passed

+1 :green_heart:
shadedclient
27m 32s

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

_ Other Tests _

+1 :green_heart:
unit
19m 17s

hadoop-common in the patch passed.

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

+1 :green_heart:
asflicense
0m 53s

The patch does not generate ASF License warnings.

300m 33s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.federation.router.TestRouterRetryCache

hadoop.hdfs.server.federation.router.TestRouterRpcMultiDestination

Subsystem
Report/Notes

Docker
ClientAPI=1.42 ServerAPI=1.42 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5346/9/artifact/out/Dockerfile

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

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

uname
Linux bd0f6cfc88ba 4.15.0-200-generic #211-Ubuntu SMP Thu Nov 24 18:16:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 5c73bc4faeab061630715706e4c9161fbb46d61f

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5346/9/testReport/

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5346/9/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.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 56s

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.

+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 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 22s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
33m 39s

trunk passed

+1 :green_heart:
compile
30m 16s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
22m 20s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
checkstyle
4m  3s

trunk passed

+1 :green_heart:
mvnsite
2m 33s

trunk passed

+1 :green_heart:
javadoc
1m 55s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javadoc
1m 45s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m  4s

trunk passed

+1 :green_heart:
shadedclient
26m 58s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 24s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 48s

the patch passed

+1 :green_heart:
compile
24m 32s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
24m 32s

the patch passed

+1 :green_heart:
compile
21m 40s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
21m 40s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
3m 51s

the patch passed

+1 :green_heart:
mvnsite
2m 28s

the patch passed

+1 :green_heart:
javadoc
1m 47s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javadoc
1m 47s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
spotbugs
4m 19s

the patch passed

+1 :green_heart:
shadedclient
27m 14s

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

_ Other Tests _

+1 :green_heart:
unit
18m 22s

hadoop-common in the patch passed.

+1 :green_heart:
unit
20m 54s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 54s

The patch does not generate ASF License warnings.

276m 44s

Subsystem
Report/Notes

Docker
ClientAPI=1.42 ServerAPI=1.42 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5346/10/artifact/out/Dockerfile

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

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

uname
Linux 0bff00c38edc 4.15.0-200-generic #211-Ubuntu SMP Thu Nov 24 18:16:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 66684c30ad2b60884ca6a39a92ae729915192a44

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

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

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5346/10/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.


Update ElasticWriter.java

only set timestamp to type date the es will work well in use es dynamic mapping

This pull request is now managed with CodeReviewHub. Refresh.

This is a backward incompatible change, so I'm not too keen on merging it. I would prefer fixing the mapping by adding an explicit format.
Side note: we need some integration tests with elasticsearch.

I actually took a few minutes to read the ElasticWriter code. We do create a mapping at startup. The mapping is probably just missing the appropriate format.
I would need more time than I have right now to actually test and validate any change.
@lmx1989219 you should be able to modify the mapping in your elasticsearch instance (without touching JmxTrans code at all) and validate if that works or not...

that's so cool.

hi gehel,
i found a problem that the index is declared by construct method and the es data folder can not empty with date.i suggest we can get client dynamically so that es can management the index data well
according to date.
e.g:
test_jmx-entries-2016.03.12
test_jmx-entries-2016.03.13
test_jmx-entries-2016.03.14
....

@lmx1989219 I'm not sure I understand what you mean... If you have working code, please send it along as the basis for the discussion...

@gehel
`@JsonCreator
public ElasticWriter(@JsonProperty("typeNames") ImmutableList typeNames,
@JsonProperty("booleanAsNumber") boolean booleanAsNumber, @JsonProperty("rootPrefix") String rootPrefix,
@JsonProperty("debug") Boolean debugEnabled, @JsonProperty("connectionUrl") String connectionUrl,
@JsonProperty("settings") Map<String, Object> settings) throws IOException {
	super(typeNames, booleanAsNumber, debugEnabled, settings);

	this.rootPrefix = firstNonNull(rootPrefix, (String) getSettings().get("rootPrefix"), DEFAULT_ROOT_PREFIX);

	this.connectionUrl = connectionUrl;
	# this.indexName = this.rootPrefix + "_jmx-entries"+"yyyy.MM.dd";
	# this.jestClient = createJestClient(connectionUrl);
}

`
the '#' row copy to follow code
`protected void internalWrite(Server server, Query query, ImmutableList results) throws Exception {
//the '#' row insert here
for (Result result : results) {
log.debug("Query result: [{}]", result);
Map<String, Object> resultValues = result.getValues();
for (Entry<String, Object> values : resultValues.entrySet()) {
Object value = values.getValue();
if (isNumeric(value)) {
				Map<String, Object> map = new HashMap<String, Object>();
				map.put("serverAlias", server.getAlias());
				map.put("server", server.getHost());
				map.put("port", server.getPort());
				map.put("objDomain", result.getObjDomain());
				map.put("className", result.getClassName());
				map.put("typeName", result.getTypeName());
				map.put("attributeName", result.getAttributeName());
				map.put("key", values.getKey());
				map.put("keyAlias", result.getKeyAlias());
				map.put("value", Double.parseDouble(value.toString()));
				 map.put("timestamp", result.getEpoch());

//					map.put("timestamp", sdf.format(new Date(result.getEpoch())));
log.debug("Insert into Elastic: Index: [{}] Type: [{}] Map: [{}]", indexName, ELASTIC_TYPE_NAME,
map);
Index index = new Index.Builder(map).index(indexName).type(ELASTIC_TYPE_NAME).build();
JestResult addToIndex = jestClient.execute(index);
if (!addToIndex.isSucceeded()) {
throw new ElasticWriterException(
String.format("Unable to write entry to elastic: %s", addToIndex.getErrorMessage()));
}
} else {
log.warn("Unable to submit non-numeric value to Elastic: [{}] from result [{}]", value, result);
}
}
}
}`

Wow! A pull request would be easier to read...


Project migration to the component based architecture / Kotlin

Hello,
Is there any plan to migrate the projet to an component based architecture ?
Same to start using Kotlin for new features ?
Best,
Abdellah

I see they are using kotlin https://github.com/kickstarter/android-oss/blob/master/app/build.gradle#L152 to some degree.
I hope you will consider kotlin for future features 🚀

Yep, we're using Kotlin as we see fit for new utils and some classes. The Hope and Dream™ is to get most of our view models, activities, and tests (i.e. everything hehe) to Kotlin, but to keep with our product roadmaps it's not our priority right now 😭


Virus custom range & speed

How to edit virus speed and distance separately ?and is possible to put exact speed ?
The virusVelocity config change the 2 tings at same

? refine what do you want to do, what do you need it

I don't think you can edit both separately, but I may be wrong.

@DeadLord1337 Title


Fix documentation setup

See #68
Accompanying this PR, I created and added the requisite keys to the repository using DocumenterTools and I created the gh-pages branch.
Summary of this PR:

I deleted and gitignored the docs/build directory, which isn't meant to be checked in on main, only on gh-pages. (This is discussed a bit in the Documenter documentation.)
I created a docs/Project.toml to record the dependencies necessary to build the documentation and run the doctests.
The CI setup was unnecessarily complex; much of what was there has been replaced by actions from the julia-actions organization. The docdeploy action will run doctests as part of building the docs.
The base branch was misspecified as master but this repository uses main.
docs/make.jl built docs (with makedocs) but didn't deploy them. I added a call to deploydocs which will push to gh-pages as appropriate, thereby populating the site.
I added a call to setdocmeta! to ensure that this package and LinearAlgebra are loaded in the environment in which doctests run.

Hm, kinda sus that CI wasn't triggered on this PR, but maybe it needs to live on the base branch first

Thanks!

Should there be a docs link in the README.md file, or only after this gets merged and the docs build can be tested?

I figured it'd make sense to do it afterward once we know for sure whether the link would actually work 😅


Typing in Chinese in the editor is super slow and unresponsive

Describe the bug
https://user-images.githubusercontent.com/5107241/177451824-8731e916-b4f3-43ba-b2e2-d8e8f5de44cd.mov
When typing Chinese as fast as possible, the UI become unresponsive and the IME is super slow.
To Reproduce
In the main editor, try typing Chinese with either macOS native IME or Sogou IME, then the IME become very slow and cannot respond to the input quickly.
Expected behavior
No response
Additional context
No response
Logs/tracebacks
No response

Properly involved with:

https://github.com/ueberdosis/tiptap/blob/main/packages/core/src/InputRule.ts#L216
https://github.com/ProseMirror/prosemirror-view/blob/master/src/input.ts#L435
ydoc sync


fix reqwest dependency features

The reqwest dependency brings the native-tls in as part of its default features, even if the rustls feature is specified. Adding default-features = false fixes the problem.

Won't you mind documenting this change in CHANGELOG.md?

Won't you mind documenting this change in CHANGELOG.md?

Done. I think I respected the format, let me know if the level of details is enough.


improve sluggable logic

improve the sluggify javascript snipppet a little bit so that multiple dashes (----) gets translated into a single dash.
In german products its common to use titles like "Foo - Bar" which would translate into "foo---bar" without this patch. ("foo-bar" is desired)

@thyseus
Please resolve conflict

made a mistake wile merging, please wait.... :)

Fixed :)

can not reopen this PR so i made a new one: https://github.com/bagisto/bagisto/pull/1826


⚠ ClamAV has degraded performance

In 97debbc, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 62 ms

Resolved: ClamAV performance has improved in 7eeb2fe.


WIP: Use Everydict instead of lists of tuples

This branch uses a custom version of elm-bridge which uses EveryDict as the default Dict implementation.
Ready for reviews

It works and has been reviewed by @power-fungus


New rule proposal: Do not combine attributes

Category: Readability
Title: Do not combine attributes
Description: C# allows attributes to be combined, such as the following:
[Export, Shared]

This form makes it difficult to distinguish which attributes are applied to a code element, and which arguments are passed to those attributes. To avoid this situation, only place one attribute within a single set of brackets, such as the following:
[Export]
[Shared]

Note: A rule to ensure only one attribute is placed on a given line will be proposed separately.

+1

:+1:

:+1:


feat: add a logger based on plenary.log

Description
Add a logger based on Plenary's log implementation.
I basically hijacked the notify function, so it's trivial to swap out the logger for a more sophisticated one, should you wish so.

Note: It's up to you to decide on how to set the default log level.

Here's a demo of what it looks like in action:

Cool!! This is something I had in mind. One thing that kept me putting this of is the log-to-storage part. I glanced through the code so I think I have the answer, but is there any log rotation/pruning in place? Bit worried that these log files are unbounded in size and will just keep growing forever, which is not very cash money. The amount of logging that is in place today is no cause for concern though, but I was planning on adding a bunch more (like performance metrics and whatnot).

@kylo252 I opened a PR to this branch at https://github.com/kylo252/nvim-lsp-installer/pull/1. Apart from those suggestions I think this is ready to merge!


Next Release Time?

Dear
Last release time is in 2018.4 .
Is the commits adequate for a new release?

Yes. New release was well overdue. Thanks for reminder. Just made 2.8rc which will become proper 2.8 in week or two.


Include PF sass variables as reference (instead of redefining)

Currently pfe-sass redefines sass variables:

Instead it should pull them in from the node_modules/@patternfly/patternfly/sass-utilities directory

@coreyvickery @dcaryll  it's worth noting that the red colors in Patternfly are:
$pf-color-red-100:               #c9190b !default;
$pf-color-red-200:               #a30000 !default;
$pf-color-red-300:               #7d1007 !default;
$pf-color-red-400:               #470000 !default;
$pf-color-red-500:               #2c0000 !default;

So the only place #ee0000 will live is the redhat-theme

+1 this code update appears in the design token fork for one example


wintrt::initialize throws when already initialized

In base.h:
inline void initialize(const initialize_type type = initialize_type::multi_threaded)
{
    check_hresult(WINRT_RoInitialize(static_cast<uint32_t>(type)));
}

You are allowed to call RoInitialize more than once but it returns S_FALSE if it's already initialized. The problem is that check_hresult only accepts S_OK and throws on S_FALSE.
Either check_hresult should use FAILED(result) instead of result != S_OK or initialize should be implemented as follows to avoid using check_hresult:
inline void initialize(const initialize_type type = initialize_type::multi_threaded)
{
    HRESULT result = WINRT_RoInitialize(static_cast<uint32_t>(type)));
    if (FAILED(result))
    {
        impl::throw_hresult(result);
    }
}

This behavior is also discussed in issue #8. The guidance is to only call winrt::initialize once, or to balance calls if necessary. We are avoiding injecting S_FALSE into cppwinrt in any way as the WinRT API surface is designed not to use it and it's avoidable in the initialize() scenario.

The problem is not merely balancing. The problem is that on some platforms you need to explicitly initialize Windows Runtime and on others you don't, so for portability you want to probably always call winrt::initialize. With Windows Store/UWP, this fails as described because the runtime already initialized it.
I don't mind balancing the calls which makes sense. The problem is that if anything (CRT or otherwise) has already done the initialization, the current behavior results in an exception.

We need to look at the throwing behavior for another reason, the side-effect of which would solve your issue: we are treating RoInitialize as an error condition when it returns S_FALSE, whereas the documented behavior is that it should succeed and be balanced by a corresponding call to RoUninitialize (winrt::uninitialized in our case) where it returns S_OK or S_FALSE.
Thanks for bringing this to our attention.

@KevinWelton: I don't understand the rationale behind closing this issue (or issue #8 for that matter). Neither one has been resolved in the published library, creating an unfortunate mismatch between code and documentation. Is there any chance of getting those back in sync in the future?

The thing is that this is not a bug. The check_hresult function is used by the projection to handle WinRT errors and WinRT errors only account for the S_OK success code. You may use it yourself but its purpose is to deal with WinRT errors. If you need something else, feel free to write a helper function of your own. The same goes for winrt::initialize. It is a very low-level function used strategically to initialize the thread context in those corner cases where this is not done automatically on your behalf. If you need something more powerful or more general-purpose then feel free to write a tiny helper class that calls RoInitialize in its constructor and RoUninitialize in its destructor. This is not hard, but we’re not convinced that it is something that most developers need and that is why it is not included in the library.

@kennykerr: I'd still argue, that this is a bug. As you explained in a previous comment:

RoInitialize [...] is not part of the WinRT API surface.

check_hresult, on the other hand, is implemented in a way that allows it to be used on the WinRT API surface only. In short, initialize mixes different interface contracts in its implementation.
Even if you disagree with the assessment, that this were a defect, it's still an issue that users of the library need to be aware of. Providing documentation reflecting the current implementation is one way to achieve that. And that's why I was surprised to see this issue closed, while the published library code still implements this behavior.
I'm not requesting to have the implementation changed. I'm only asking for documentation that matches the implementation, to help us developers use this library reliably.

Sorry for the confusion. We maintain both a private and public repo. We hope to move entirely to the public repo in the future, which will make all this a lot less confusing. I can confirm that we will update winrt::initialize to report errors and non-errors consistently with the underlying RoInitialize call. I’ll leave this issue open until that change has made its way to the public repo. Thanks for the feedback!

I read in a document that to achieve the behavior:
[Platform::MTAThread]
int main(Platform::Array<Platform::String^>^)

We need to call winrt::initialize(). But calling it in  a UWP app causes a crash. So what is the default behavior? Is it documented somewhere?

Both the non-standard C++/CX MTAThread attribute and the winrt::initialize function cause the RoInitialize function to be called to initialize the thread context. The Visual C++ CRT calls RoInitialize before execution arrives at WinMain for UWP store apps, but not for desktop/console apps. That's why it fails: it's already been initialized.

The init_apartment function (formerly called initialize) will no longer throw if it is called repeatedly (redundantly) on the same thread. The check_hresult function has been improved with support for other success codes, as an opt-in feature.


Join with an ID

Can we support joining a meeting by ID?

@haohighview  we appreciate the feedback. Currently, UI libraries supports joining call with meeting link.
To help look into the issue further could you please provide some additional information about the use case(need to join meeting with ID)?

Now created teams meeting will generate meeting id and password. You can join the meeting by entering the id and password.

Hi @haohighview, thank you for the suggestion; it would be an excellent opportunity to improve the libraries. I encourage you to share your ideas here in the Azure Share Ideas forum.
We actively look for improvements and valuable feedback here.

Please vote for this idea:
https://feedback.azure.com/d365community/idea/2b504160-5513-ed11-a81b-6045bd8606d4

Hi @haohighview, https://feedback.azure.com/d365community/idea/2b504160-5513-ed11-a81b-6045bd8606d4 is created as per discussion.
Please reopen issue, if more information is required.


[Doc EN]: Official Vue way to speak about a version and greater version.

Hi @posva, we have seen with @chrisvfritz a way to harmonize speaking about a version and greater version has following:
product version => only this version
product version+ => this version and greater (this one replace the old product >= version way)

Good for me but I don't see those modifications reflected on the PR 😆

https://github.com/vuejs/vue-router/pull/1841

Maintenant que tu le dis... effectivement... XD
« Voilà ! »

Maintenant que tu le dis... effectivement... XD
« Voilà ! » @posva !


ngrx/store setup sample incorrect?

Here: https://github.com/ngrx/store/blob/master/README.md
StoreModule.forRoot(...) is still being used. I imagine this has deprecated. Needless to say misleading if so

Duplicate #349
In the next major release StoreModule.forRoot() will be the correct way to provide store (See Comment). I agree that it is a bit misleading, but should be resolved with the next major release.

Is there an estimate for the v4 release come out?

We just got back from ng-conf this past week, so we'll need to finish up the next release but it will be soon


Fix Azurite support (#4279)

Port https://github.com/dotnet/aspire/pull/4279 to fix test issue exposed in https://github.com/dotnet/aspire-samples/pull/345
Microsoft Reviewers: Open in CodeFlow

Needs a 2nd review and everyone is out..?

cc @eerhardt


Used structured streaming with kafka Avro message

Hello,
I want to use spark-structured-streaming to process data fetched from kafka messages, and then store as rows cassandra database.
I read your book on structured-streaming. I need one clarification.
The message in kafka are serialized in Avro format.
How can i deserialize the message to json for processing before storing into cassandra?
Is it possible with spark 2.1.0 or 2.1.1?
Any advice or help could be appreciated.
Thanks in advance

Sorry for being late on this. Somehow I haven't noticed your question.
Avro format is not supported directly in Spark (up to 2.2) and so the use case is not possible without some coding. The use case however pops up quite often and think it's time for me to have a solution for it. I'm going to work on it this week.
Let me know if you've sorted it out in the meantime.

Hi @jaceklaskowski
We are having the same problem. Could you please suggest.
What is the best way to decode an avro encoded message from Kafka using Spark Structured Streaming. Is there any option introduced in Spark2.3 ?
We are currently using 2.2 version of Spark and tried using the below sample code without success
val reader = new GenericDatumReaderGenericRecord
val decoder = DecoderFactory.get().binaryDecoder(Array[Bytes], null)
val rec = reader.read(null, decoder)

What is the best way to decode an avro encoded message from Kafka using Spark Structured Streaming. Is there any option introduced in Spark2.3 ?

No built-in support for Avro in Spark 2.3.0. You could give spark-avro a try. See also https://docs.databricks.com/spark/latest/data-sources/read-avro.html.
I've got no experience with Avro, but looks like I should change that soon. Do you have a sample message to send to a Kafka topic so I could use for testing?

Hi @jaceklaskowski , Did you get a chance to look into this?
Thanks

Had no time for this. Sorry.
While we're at it, how do you produce an avro message? How do you consume it? My recommendation would be to use the code to consume avro messages and write a custom streaming source.

Thanks for the response @jaceklaskowski
We are using Confluent Kafka and the Schema-registry of the same is been used to put the message into topic.
We are using avro-console-producer of confluent Kafka to produce messages into Kafka topic. Sure I will try with a custom streaming source too.
And on the consumer Spark Structured Streaming we tried using KafkaAvroDecoder from confluent,
def my_decoder: KafkaAvroDecoder = {
val props2 = new Properties()
props2.put(ConsumerConfig.BOOTSTRAP_SERVERS_CONFIG, brokers)
props2.put(ConsumerConfig.GROUP_ID_CONFIG, "avro-integration-test")
props2.put(ConsumerConfig.AUTO_OFFSET_RESET_CONFIG, "latest")
props2.put(ConsumerConfig.KEY_DESERIALIZER_CLASS_CONFIG, classOf[KafkaAvroDeserializer])
props2.put(ConsumerConfig.VALUE_DESERIALIZER_CLASS_CONFIG, classOf[KafkaAvroDeserializer])
props2.put(AbstractKafkaAvroSerDeConfig.SCHEMA_REGISTRY_URL_CONFIG, schemaRegistryURL)
props2.put(KafkaAvroDeserializerConfig.SPECIFIC_AVRO_READER_CONFIG, "true")
val vProps2 = new kafka.utils.VerifiableProperties(props2)
new KafkaAvroDecoder(vProps2)
}
val kafkaParams = Map[String, String](
"kafka.bootstrap.servers" -> brokers,
"key.deserializer" -> "KafkaAvroDeserializer",
"value.deserializer" -> "KafkaAvroDeserializer",
"group.id" -> "structured-kafka",
"auto.offset.reset" -> "latest",
"failOnDataLoss"-> "false",
"schema.registry.url" -> schemaRegistryURL
)
val avro_schema = new RestService(schemaRegistryURL).getLatestVersion(subjectValueName)
val messageSchema = new Schema.Parser().parse(avro_schema.getSchema)
val df = spark.readStream.format("kafka").option("subscribe", topic).options(kafkaParams).load().map{ x => my_decoder.fromBytes(x.getAsArray[Byte], messageSchema).asInstanceOf[String]}
Note: We were able to decode the avro messages using KafkaAvroDeserializer in Spark Streaming Job(Dstreams)

@jaceklaskowski
Hi,
I have a same use case like others. I'm new to structured streaming and i'm using it on Databricks cloud platform with Python. I am collecting data using kafka which sends avro messages and selected a column "value" and also cast to "string". However, after getting those data  I am still getting pattern like "?0s???LR????(}????4e'd???' So, I'm unable to deserialize it. Is there any way that i can deserialize those value according to my existing schema of avro?
I appreciate your help.
Thanks

I have a working example I adapted from a bunch of stack overflows, but I don't like the map at the end instead of a UDF. If anyone can show me how to use a UDF instead that would be awesome. Also, I'm working on serializing at this point.
`val brokers = "kafka01:9092"
val zookeeper = "zk01:2181"
val schemaRegistryURL = "http://sr:8081"
val topic = "mytest"
val subjectValueName = topic + "-value"
val kafkaParams = Map[String, String](
"kafka.bootstrap.servers" -> brokers,
"key.deserializer" -> "KafkaAvroDeserializer",
"value.deserializer" -> "KafkaAvroDeserializer",
"group.id" -> "structured-kafka",
"auto.offset.reset" -> "latest",
"failOnDataLoss"-> "false",
"schema.registry.url" -> schemaRegistryURL
)
object MyDeserializerWrapper {
val props = new Properties()
props.put(AbstractKafkaAvroSerDeConfig.SCHEMA_REGISTRY_URL_CONFIG, schemaRegistryURL)
props.put(KafkaAvroDeserializerConfig.SPECIFIC_AVRO_READER_CONFIG, "true")
val vProps = new kafka.utils.VerifiableProperties(props)
val deser = new KafkaAvroDecoder(vProps)
val avro_schema = new RestService(schemaRegistryURL).getLatestVersion(subjectValueName)
val messageSchema = new Schema.Parser().parse(avro_schema.getSchema)
}
case class DeserializedFromKafkaRecord( value: String)
val df = spark
.readStream
.format("kafka")
.option("subscribe", topic)
.options(kafkaParams)
.load()
.map( x=>{
DeserializedFromKafkaRecord(MyDeserializerWrapper.deser.fromBytes(x.getAsArray[Byte], MyDeserializerWrapper.messageSchema).asInstanceOf[GenericData.Record].toString)
})
df
.writeStream
.outputMode("append")
.format("console")
.option("truncate", false)
.start()
`

@bclipp Could you please provide the full code snippet?

The above code works, the hard part is the schema , which is not inferred in streaming, you have to pull if from a file... val jsonDF = stringDF.select(
from_json(col("value").cast("string"),
spark.read.json("...").schema
).alias("match")
)

@bclipp @DhineshVijayakumar what is the schema registry url mean( val schemaRegistryURL = "http://sr:8081"  ). what should I provide here if I am running in production.

the URL for your schema registery
On Fri, Sep 14, 2018, 5:03 PM satishreddy487<EMAIL_ADDRESS>wrote:

@bclipp https://github.com/bclipp @DhineshVijayakumar
https://github.com/DhineshVijayakumar what is the schema registry url
mean( val schemaRegistryURL = "http://sr:8081" ). what should I provide
here if I am running in production.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jaceklaskowski/spark-structured-streaming-book/issues/1#issuecomment-421483593,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFngTvXbDFQstpnVa1WQiYVJW5AIBkteks5ubBmFgaJpZM4OD2-6
.

@bclipp No idea what it is..where will it be usally..the kafka broker?

It's available since Spark 2.4 so closing it. See https://jaceklaskowski.gitbooks.io/mastering-spark-sql/spark-sql-avro.html for some information.

well no its not really. there is a big difference if your using schema reg.

spark-sql-avro expects the Avro schema to be part of the binary payload.
It doesn't recongnize Confluent's Avro Binary Format
And ~SPARK-26314~ was closed saying they won't support it.

Spark avro doesnt support Avro schemas with repeated field names.


Fixes #3788-Distinctively show quality images and featured images in Achievements

Description (required)
Fixes #3788
What changes did you make and why?
*Distinctively show quality images and featured images in Achievements
Referred #3823
Tests performed (required)
Tested betaDebug Api 27
Screenshots (for UI changes only)

Codecov Report

Merging #3966 into master will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master    #3966      +/-   ##
============================================
- Coverage     10.51%   10.51%   -0.01%
  Complexity      466      466
============================================
  Files           335      335
  Lines         12636    12642       +6
  Branches        989      989
============================================
  Hits           1329     1329
- Misses        11240    11246       +6
  Partials         67       67

Impacted Files
Coverage Δ
Complexity Δ

...e/nrw/commons/profile/achievements/Achievements.kt
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...ons/profile/achievements/AchievementsFragment.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

Continue to review full report at Codecov.

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


tracker-miners: 3.5.0 → 3.5.2

https://github.com/GNOME/tracker-miners/compare/3.5.0...3.5.2
Description of changes
Closes https://github.com/NixOS/nixpkgs/issues/228639
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

@ofborg build tracker-miners


On iOS, after pressing a cluster and zooming, pressing a marker shows it and then quickly hides it

Reproducible example: https://github.com/findhumane/testmapstouch

git clone https://github.com/findhumane/testmapstouch
cd testmapstouch
npm install
npx expo start --tunnel
Scan the QR code in Expo Go
Tap on the "3" cluster
Move the map over a bit to the left
Tap on the left marker
The callout shows very quickly and then disappears (see demo video below)
However, then, move down and to the right and tap that marker and the callout is persistent, as expected

bug.webm
Some notes:

The above demonstration is with Expo SDK47 and<EMAIL_ADDRESS>The problem also happened on SDK46 and<EMAIL_ADDRESS>I was waiting to report this until I could upgrade to SDK47 and the newer react-native-maps.
This issue does not happen if react-native-maps-super-cluster is not used (i.e. just react-native-maps and markers).
This has been reproduced on multiple iPhones, old and new.

Any ideas?

I noticed that the develop branch is ahead of master, and I had been forking off of master (to fix some issues integrating with newer versions of Expo). I applied the diff between develop and master and the issue is the same.

Proximate cause and workaround described here: https://github.com/react-native-maps/react-native-maps/issues/4573#issuecomment-1369146465
diff --git a/ios/AirMaps/AIRMapMarker.m b/ios/AirMaps/AIRMapMarker.m
index 65098aa..0d66061 100644
--- a/ios/AirMaps/AIRMapMarker.m
+++ b/ios/AirMaps/AIRMapMarker.m
@@ -267,7 +267,7 @@ NSInteger const AIR_CALLOUT_OPEN_ZINDEX_BASELINE = 999;
     _calloutIsOpen = NO;
     [self setZIndex:_zIndexBeforeOpen];
     // hide the callout view
-    [self.map.calloutView dismissCalloutAnimated:YES];
+    [self.map.calloutView dismissCalloutAnimated:NO];

     [self setSelected:NO animated:NO];
     [self.map deselectAnnotation:self animated:NO];


Updated Icebreaker app? (called something different)?

I could have sworn I saw an update to the app but am not able to find the link anymore... i thought a few updates were made where in it added a few "icebreaker" things for folks to ask during the meeting/scheduling... did anyone else remember seeing this?

Thank you for submitting this issue, as we work to ensure consistent responses with items logged in our issues list, we are working to address these items that did not get responses. Please let us know if you are still facing this issue and require assistance and we will be happy to discuss. If no further action is needed at moment and no response is received, we will close out the issue in 3 business days. You may also always open a new issue or respond here if something does come back up. Thank you!


[Bug]: Coverage reporting not working for Integration tests

Package name

global -

Package version

Reproduction steps
Publish IT Coverage report to CodeCov
Current result
Raising error
Expected result
Be correctly published
Additional comments
No response

Can we ever have this working?
The it-tests don't run on source code but on artifacts publish on verdaccio, I don't think the coverage can apply here.

Indeed, let's abort Coverage for IT for now


Requesting Bot Acces

Discord Server Name: DaVinci Corp.
Contact info: Mamurra#9693 (Via Discord)
Server ID:<PHONE_NUMBER>91216643
Room ID:<PHONE_NUMBER>14377226
Invite for DaVinci Corp. Server: https://discord.gg/zbZcqNx
Thanks

This is set up, with a reasonable default set of feeds.


Set peerDependencies of grunt to 0.4.5

Fix for users that don't want to use<EMAIL_ADDRESS>(or cannot use)
See this section in the releases notes of grunt:
http://gruntjs.com/blog/2016-04-04-grunt-1.0.0-released#peer-dependencies

Coverage remained the same at 76.768% when pulling 2e452678d57b1e02f94e4c7dde3b65cf085f138e on hvdb:master into 2f16f704ab93faed2076f53fb0dad146f1f216c4 on devaos:master.

Thanks for the PR. Merged and published as 1.5.3.


Version 6.111.0

hypothesis 6.111.0
Destination channel: defaults
Links

PKG-5523
Upstream repository
Upstream changelog/diff
Relevant dependency PRs:

numpy 2

Explanation of changes:

Updated Hypothesis to version 6.111.0:

Brings the project up to date with the latest features and improvements.
Addresses a critical dependency issue related to NumPy.

Resolved NumPy2 hotfix conflict:

The main channel had a <2.0 dependency for Hypothesis, causing a crash when attempting to test NumPy2.
This update allows Hypothesis to resolve correctly, enabling testing for NumPy2 without crashing.

Rationale for the update:

Ensures that the project can successfully test against NumPy2 by eliminating conflicting dependencies.
Prevents potential issues and supports compatibility across dependencies.

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_bebmjrrxwy/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:91: invalid_url: https://hypothesis.readthedocs.io/ : Not reachable: 403
===== Final Report: =====
1 Error and 0 Warnings were found

So is this to override the hotfix, just for hypothesis? Should this be done in the hotfix code instead? <=2.0.1 doesn't seem to represent inherent compatibility (i.e., compatibility of the upstream software with numpy)

So the hotfix on main currently resolves to
numpy >=1.17.3, <2.0.0

the issue in this instance is that this is a test dependency for numpy 2.0.0 and above, and having a dependency that depends on a lower dependency doesn't seem to sit well

sure, but why don't you remove the hotfix in that case? Having it here would be to state that hypothesis inherently requires numpy <=2.0.1, which is incorrect

From what I see, numpy 2 support was added in 6.100.2 according to HypothesisWorks/hypothesis@eccba85 and numpy/numpy#26191. So I don't see why we need the upper bound.

That's okay, so on the repodata hotfix I will remove the upper bound, as it currently has that applied

@JamesRobertsonGames Ok, thanks. If you do so, please make sure to not remove the hotfix on 6.100.1 and lower.

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_bdrdiw644b/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:91: invalid_url: https://hypothesis.readthedocs.io/ : Not reachable: 403
===== Final Report: =====
1 Error and 0 Warnings were found

nitpick:
I think the linter doesn't allow for redirects, in which case doc_url: https://hypothesis.readthedocs.io/en/latest should be the way to go.

Optional, but nice to have for the CLI tool

I would argue that if these are optional they should still be in run_constrained.

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_9fpg7ceuod/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:91: documentation_specifies_language: Use the generic link, not a language specific one

===== ERRORS =====

clone/recipe/meta.yaml:91: invalid_url: https://hypothesis.readthedocs.io/en/latest : Not reachable: 403
===== Final Report: =====
1 Error and 1 Warning were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_8egaftr0iv/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:91: documentation_specifies_language: Use the generic link, not a language specific one
===== Final Report: =====
0 Errors and 1 Warning were found

I think we should consider moving the CLI extras from required to run constraints. We are being opinionated on the users behalf. Perhaps the user does not want the cli and is using it only as a module for pytest.
Otherwise, I approve.

I think in this instance it being in run constraints hold the balance, happy to remove if there is a strong opposition to this

I am ok to punt this a little more down the road.  I have a strongish opinion in general but perhaps we need a venue to warn people that we will be changing how things are done.

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_e0zwgrucq_/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:91: documentation_specifies_language: Use the generic link, not a language specific one
===== Final Report: =====
0 Errors and 1 Warning were found


Release new pypi version

Howdy,
Is it possible to release a new version with the async changes to pypi?
Cheers

please do, I need a new functionality available only in the lastest release of object store

Any chance you've had a chance to look at publish the latest version? The last release is from 2023...


[silgen] Eliminate an unnecessary static function emitArrayToPointer.

[silgen] Eliminate an unnecessary static function emitArrayToPointer.
We already have a method on SILGenFunction with the exact signature that just
calls this private function. All other uses can be re-routed to the method on
SILGenFunction, allowing us to simplify the code.

@swift-ci smoke test and merge


Fish config

Bind ctrl-l to wipe using bind \cl 'wipe --duration 1200; commandline -f repaint' :)

I will add a fish config file as soon as I have time.
Thank you for your contribution!

I have added a config file at misc/shell/wipe.fish. The file is included in a new patch release. (I also upgraded some dependencies.)
Please close this issue, if it has been resolved.

Thanks!


Storefront client not showing exact error instead showing invalid json

Issue summary
I tried running storefront client to fetch products from my store. I intentionally put wrong storefront token to check the error message. Apparently I got invalid json input error.
Here's the snippet code I am running ( example code provided in documentation ).
  const client = new Shopify.Clients.Storefront(
    shopifyShopName,
    storefrontToken,
  )
  try {
    const products = await client.query({
      data: {
        query: `query GetProducts($first: Int!, $query: String!) {
      products (first: $first, query: $query) {
        edges {
          node {
            id
            title
            descriptionHtml
          }
        }
      }
    }`,
        variables: {
          first: 1,
          query: 'a',
        },
      },
    })

    return products.body
  } catch (error) {
    console.log({ error })
    throw new Error(error.message)
  }

Expected behavior
Error should be provided by shopify api. In this particular case it should something like token is not valid.
Actual behavior
I was given error about invalid json response body.
error: HttpRequestError: Failed to make Shopify HTTP request: FetchError: invalid json response body at https://{my-shop-name}/api/unstable/graphql.json reason: Unex
pected end of JSON input
      at HttpRequestError.ShopifyError [as constructor] ({directory}/@shopify/shopify-api/dist/error.js:13:28)
      at new HttpRequestError ({directory}/@shopify/shopify-api/dist/error.js:79:42)
      at {directory}/@shopify/shopify-api/dist/clients/http_client/http_client.js:242:35
      at processTicksAndRejections (node:internal/process/task_queues:96:5)
}

Steps to reproduce the problem

Create new storefront client.
Try any request that fails ( enter invalid token or shopname )

Checklist

[x] I have described this issue in a way that is actionable (if possible)

The same issue is happening in my server HttpRequestError: Failed to make Shopify HTTP request: FetchError: invalid json response body at https://wonderchefind.myshopify.com/admin/api/2022-07/graphql.json  but with using the Admin API. Did someone found a solution for this?

Hi sorry for replying this late. This issue can be fixed usually by generating new token.


can't build with active state perl 5.14

Due to the change in util\copy-if-different.pl and util\copy.pl it's not possible anymore to build openssl with active state perl 5.14. I didn't verify newer versions of perl though.
Culplrit is the qq that was added.
foreach (glob qq("$arg"))
It's a problem for me to change the perl version on some of my older machines...  Would you consider removing the qq? currently i'm adjusting the buildscripts for my older computers.

Hmmm... I recall testing it when it went to 1.0.2 (and I customarily test with 5.10), and seeing that it works... But apparently I could have been testing wrong thing. It's not clear when behaviour changed, but in 5.10 (and I guess even in yours 5.14) qq("$arg") works as expected only if there is white space in $arg. If there are no white spaces, then it does something else. And I must have checked it only with pathnames with white spaces, because that what proposed modification was allegedly solving. In later Perl versions qq("$arg") works as expected even without white spaces... Go figure...

Also see #4680

On certain level it can be (and arguably should be) viewed as problem to address, because we do specify that 5.10 is minimum requirement, and it doesn't work with it. Could you try to replace qq("$arg") with ($arg =~ /\s/ ? qq("$arg") : $arg)?

Yes, the related issue is exactly the same problem that i am describing here. I didn't look at closed issues, that#s why i overlooked that.
Thanks for analyzing this. You're right, about qq() and i don't use paths with blanks in it.
Your regex is working, i was rather thinking on
foreach (glob "\"$arg\"")
to get rid of qq() at all, but that's also a solution.

I don't quite follow, qq("$arg") is supposed to be equivalent of "\"$arg\"", so how would it help? Does it actually help?

Sry, i got you wrong... i thought the problem's with qq() and not glob(). I just tried it and it doesn't work if you add the quotes, so your solution is perfectly fine.
Should i close the ticket?

It's appropriate to keep in open till fix is committed... I can take care of both...

Since copy-if-different.pl was mentioned, it ought to be 1.0.2. The problem was addressed in #4696.


template does not validate on validator.w3.org

Hello,
If I copy-paste any page from the template on validator.w3.org I get a bunch of errors.  Anyone check that the template is valid?
Thank you

Element a not allowed as child of element ul in this context.
Element hr not allowed as child of element ul in this context.
Element div not allowed as child of element ul in this context.
amount others

same problem.
you can add li wrap not allowed element.

class="sidebar-divider">

to

#355 will address this in the next build!


"Adding custom authentication" Documentation Edit Suggestion

Current documentation

let router = express.Router()
router.use((req, res, next) => {
  if (req.session && req.session.admin) {
    req.adminUser = req.session.admin
    next()
  } else {
    res.redirect(adminBro.options.loginPath)
  }
})
router = AdminBroExpress.buildRouter(adminBro, router)

Current documentation works well. But Logout button doesn't seem to appear. To work that around,
req.adminUser = req.session.admin
should be
req.session.adminUser = req.session.admin
and req.session.admin must be object containing email field
since current frontend component renders logout button with information inside req.session.adminUser

thx - I will add that in the next release (probably this week)


Use Dependency Groups

See: https://github.com/python-poetry/poetry-core/pull/183
Pending Implementation in Poetry. Would simplify the optional=True nonsense
Docs: https://github.com/python-poetry/poetry/blob/1da3e7292f59fc539fd2ddc2c057fcbd98a9bd60/docs/managing-dependencies.md#L14

Requires pre-release of poetry: pipx upgrade poetry --pip-args="--pre", but works locally

Actually requires an updated version of the poetry 1.2 preview (pipx install git+https://github.com/python-poetry/poetry.git@6a35cc41e950d4ff0f1efad649c1d15d689a9ce2 --force) with fixes for non-PEP440 versioning (>=3.5.*) that is rare (https://github.com/python-poetry/poetry/issues/4095), but common enough to cause issues
Dropping for now while still in preview (https://github.com/python-poetry/poetry/issues/1644). May revisit in the future


Allow provisions for global containers

Currently in easyengine v4, each site creates following containers -

nginx
mysql
php
redis(optional)

However it might start creating issues when one starts to create more and more sites as each container consumes more resources(especially ram).
Hence if the user passes any flag during ee site create, we should use the global container.
It does not make sense to allow php and nginx global containers due to security implication and because they're pretty lightweight containers.
Hence it seems only mysql and redis would benifit most from global containers as they're more resource intensive(esp mysql) so there should be provison for these two atleast.

This is being tracked in https://github.com/EasyEngine/easyengine/issues/1010


Fix type on _create to match use at call site

Fixes #19 .

Seems OK for now. The Isolate.spawn function will/has become generic (spawn<T>(void Function(T) entryPoint, T message, ...)), but until Dart 2, it's probably safer to not depend on that.

Thanks!


Stop building a dictionary

Building a Japanese morphological dictionary consumes a lot of memory.
Currently, the build script builds the dictionary, but we stop building it and change to download the pre-built dictionary.

This might be relevant too.
https://github.com/rust-lang/rust/issues/65818

It doesn't look like this patch is going to resolve https://github.com/lindera-morphology/lindera/issues/62, so I'll close it.


Add syndicate pAI to uplink

About the PR

Part 2 for https://github.com/space-wizards/space-station-14/pull/18625, changed the description to retain the HHGTTG reference and added it to the uplink. You can only buy one pAI per uplink to prevent ghost role spam.
Redo of #18629 because something went wrong.
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl: crazybrain

add: Uplinks can now purchase one Syndicate pAI.

would be cool if the pai could change its appearance to look normal to not be giga sus

would be cool if the pai could change its appearance to look normal to not be giga sus

wyci :trollface:

sure


Wrong syntax for "joinSub" method in mysql driver

Laravel Version
11.35.1
PHP Version
8.4|8.3
Database Driver & Version
MySQL 8.0.33 DBngin
Description
The error occurs in Laravel when executing a query that uses the joinSub method. Laravel generates invalid SQL syntax by adding parentheses around the table name in the INNER JOIN clause. Specifically, the SQL generated includes INNER JOIN (receipt_participants) instead of a valid reference to the table or subquery. MySQL does not support parentheses around a table name in this context, leading to the following syntax error:
1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'as `issuer` on `issuer`.`id` = `receipts`.`issuer_id`
inner join (receipt_part' at line 5

Steps To Reproduce

Set up the database:

Create the following tables in your MySQL database:

receipts (with columns like id, issuer_id, beneficiary_id, deleted_at, and created_at).
receipt_participants (with columns like id, name and other participant details).

Add the necessary Laravel models for these tables, such as Receipt.
Use the following query in your Laravel code:

Receipt::query()
    ->select([
        'receipts.*',
        'issuer.name',
        'beneficiary.name',
    ])
    ->joinSub(
        'receipt_participants',
        'issuer',
        'issuer.id',
        '=',
        'receipts.issuer_id'
    )
    ->joinSub(
        'receipt_participants',
        'beneficiary',
        'beneficiary.id',
        '=',
        'receipts.beneficiary_id'
    )
    ->orderByDesc('created_at')
    ->get();

Run the query. Laravel will execute a SQL query similar to the following:

select
  `receipts`.*,
  `issuer`.`name`,
  `beneficiary`.`name`
from
  `receipts`
  inner join (receipt_participants) as `issuer` on `issuer`.`id` = `receipts`.`issuer_id`
  inner join (receipt_participants) as `beneficiary` on `beneficiary`.`id` = `receipts`.`beneficiary_id`
where
  `receipts`.`deleted_at` is null
order by
  `created_at` desc

Observe the error in MySQL:

1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'as `issuer` on `issuer`.`id` = `receipts`.`issuer_id`
  inner join (receipt_part' at line 7

Working solution (just removing the parentheses)

select
  `receipts`.*,
  `issuer`.`name`,
  `beneficiary`.`name`
from
  `receipts`
  inner join receipt_participants as `issuer` on `issuer`.`id` = `receipts`.`issuer_id`
  inner join receipt_participants as `beneficiary` on `beneficiary`.`id` = `receipts`.`beneficiary_id`
where
  `receipts`.`deleted_at` is null
order by
  `created_at` desc

We can just use the join method to make this query work, passing 'table_name as table_alias' in the table parameter. The question remains, should the above code also work?

Hi @allanmcarvalho,

We can just use the join method to make this query work, passing 'table_name as table_alias' in the table parameter.

That's the correct way.

The question remains, should the above code also work?

You are using joinSub() incorrectly, IMO. The method is meant for subquery joins and that's not the case in your example. The first parameter only accepts strings so you can pass a subquery as raw SQL.


Initial Mono-repo setup.

Summary

This pr is setting up a mono-repo for terra-graphs, powered by carbon graphs and is our first step towards incorporating carbon into the terra ecosystem in a first class way.

Closes #
Deployment Link

https://terra-graphs-deployed-pr-#.herokuapp.com/
Testing

Additional Details

Thank you for contributing to Terra.
@cerner/terra
@cerner/carbon

I was going to have a separate pr to add in the terra-graphs template package, but tests and lint expect at least one package to be available so i'll add in a template generated terra-graphs package.


Dashboard crashes randomly

Hi,
my Dashboards are Crasing randomly since the last Update (1.5.3)
Here is a Screenshot of the console!

Hi,
my Dashboards are Crasing randomly since the last Update (1.5.3)
Here is a Screenshot of the console!

Optimized Mode enabled!

im having a weird issue too with the horizontal stack

Hi,
my Dashboards are Crasing randomly since the last Update (1.5.3)
Here is a Screenshot of the console!

It looks like that some cards don't like being removed when the pop-ups are closed. I have mostly Bubble Cards in my pop-ups, I will have to extend my test pop-ups to more custom cards.
I will take a serious look at that for the next release.

This is now fixed in the new v1.6.0 beta!
https://github.com/Clooos/Bubble-Card/releases/tag/v1.6.0-beta.1

This is now fixed in the new v1.6.0 beta!
https://github.com/Clooos/Bubble-Card/releases/tag/v1.6.0-beta.1

Thanks a lot. No problems since updating this morning. 😍


Aggregate javadoc plugin v8 fails due to project plugins

The PR 'Bump io.freefair.aggregate-javadoc from 6.6.3 to 8.0.1 #7602' failed to build due to
A problem occurred evaluating root project 'egeria'.
> Failed to apply plugin 'org.gradle.java'.
   > The aggregate-javadoc plugin should not be used on a java project

Our top level project is indeed java (as is typical)
See https://github.com/odpi/egeria/pull/7602
Need to evaluate & consider how to address. For now will not update

@lpalashevski FYI another dependency update being held-back


ESP_EARLY_LOGX calls can't be filtered even after startup (IDFGH-7546)

Calls to ESP_EARLY_LOGX macros cannot be filtered using esp_log_level_set(...), even after the processor is up and running and normal ESP_LOGX calls are working.
This results in extra log spam that cannot be disabled. For example, from the efuse component.
I would suggest checking an 'initialised' flag and directing the call to either:

the direct esp_rom_printf call if not yet initialised
the ESP_LOG_LEVEL macro if initialised (which allows filtering to work)

It should be filtered based on default log level esp_log_level_set("*", ESP_LOG_INFO);
https://github.com/espressif/esp-idf/blob/01d014c42def8d0c19e1ce55c07de6761e092ffa/components/log/include/esp_log.h#L323
You have an interesting suggestion however I think ESP_EARLY_LOGX and ESP_DRAM_LOGX would first have to be fully distinguished in the codebase.

The log is printed by ESP_EARLY_LOGX if the (LOG_LOCAL_LEVEL >= (log_level) && esp_log_get_default_level() >= (log_level)) allows it. esp_log_get_default_level() is directed by esp_log_level_set().
If you do not want to see startup logs you can set CONFIG_LOG_MAXIMUM_LEVEL=INFO and CONFIG_LOG_DEFAULT_LEVEL=WARN
    Default log verbosity (Warning)  --->
    Maximum log verbosity (Info)  --->

In the code raise the default log level till INFO using esp_log_level_set(), then info logs will go.
I close this issue because it was answered above. Thanks.


include node_modules when transpiling

Fixes issues where required modules weren't probably transpiled to work with our browser matrix.
Usually packages are supposed to produce proper ES5 builds, but not all of them do :(
E.g. @lightspeed/i18n-number-format contains rest and spread.
Will come at the expense of slower builds.
🎩 dev and prod build locally with newly created argo-checkout-template project.
Installed and used @lightspeed/i18n-number-format (as this package is known to cause issues) and checked that no rest or spread was to be found anymore.
🎩 prod
yarn build
cd build
npx http-serve -c-1 -p 39351

use http://localhost:39351/main.js as script_url
We can always go back to another solution (like allowing consumers to allowlist packages) later.

I'd probably cut a beta release and have that tested before releasing that to all of the public

re-requested reviews as I now changed it to be two distinct configs for node_modules vs app code

Added compact mode for node_module files to speed things up, but also to remove the warning:
The code generator has deoptimised the styling of ...

caused by large packages (esp in development) like react-reconciler.

This was tested successfully by a partner with a beta version I had released.


[auto-merge] branch-23.04 to branch-23.06 [skip ci] [bot]

auto-merge triggered by github actions on branch-23.04 to create a PR keeping branch-23.06 up-to-date. If this PR is unable to be merged due to conflicts, it will remain open until manually fix.

FAILURE - Unable to auto-merge. Manual operation is required.
{'message': 'Pull Request is not mergeable', 'documentation_url': 'https://docs.github.com/rest/reference/pulls#merge-a-pull-request'}

Please use the following steps to fix the merge conflicts manually:
# Assume upstream is NVIDIA/spark-rapids remote
git fetch upstream branch-23.04 branch-23.06
git checkout -b fix-auto-merge-conflict-8250 upstream/branch-23.06
git merge upstream/branch-23.04
# Fix any merge conflicts caused by this merge
git commit -am "Merge branch-23.04 into branch-23.06"
git push <personal fork> fix-auto-merge-conflict-8250
# Open a PR targets NVIDIA/spark-rapids branch-23.06

IMPORTANT: Before merging this PR, be sure to change the merging strategy to Create a merge commit (repo admin only).
Once this PR is merged, the auto-merge PR should automatically be closed since it contains the same commit hashes

I will take care of the merge conflict later