Add Idea EAP

Hello, I'm using idea eap at work which is basically ultimate with additional features, free and usable for commercial uses. I personnaly think it's a great addition but I would understand if you don't think so.
Thanks for your work 👍

Might need to check the version check, I'm not too familiar with the tool finding the version. Here the build number is the version

Added the ultimate eap version and fixed the community eap URL.


Parameters for C++ Inference

Hey,
first of all nice project.
I have a question regarding the input parameters for the segmentation in c++

The size variable is the input size of the model right?
But what is seg_h, seg_w, and seg_channels?
I have a model with 608 (h) x 1280 (w) and want to segment on an image which is 1280 x 720p.

Hey, we also have a lot of problems with the mask and don't know why. The model worked fine in Python with perfect masks. The masks here are completely "random" and the resulting mask for the cone is pretty bad.

if (masks.empty()) {
        printf("Mask empty");
        // masks is empty
    }
    else {
        printf("Mask not empty");
        cv::Mat matmulRes = (masks * protos).t();
        cv::Mat maskMat   = matmulRes.reshape(indices.size(), {seg_w, seg_h});

        std::vector<cv::Mat> maskChannels;
        cv::split(maskMat, maskChannels);
        printf("Num channels: %d", maskChannels.size());
        for (auto channel : maskChannels) {
            cv::imshow("channel", channel);
            cv::waitKey(0);
            cv::destroyAllWindows();
        }

size is the network input size like 640*640
topk is the max number of results after postprocess
seg_h is the proto shape like (640/4) * (640/4) : 4x downsample
seg_channel is the proto channels.
If your network input shape is 608 * 1280
You may set seg_h as 608/4, set seg_w as 1280/4.

Thanks, that helped a lot :)


Prometheus plugin only

See #15, add prometheus plugin.

@brian-brazil thanks for getting this fixed up so quickly!


Info utility

I have implemented RNCryptor in my app IOS, i'm looking for who has written a utility on "OS X" for mutual interest.
thanks.

Is this still an open question? I'm not certain what you mean. There is a rncrypt command-line example project (though it probably needs the same fix as #202).


YARN-10885. Make FederationStateStoreFacade#getApplicationHomeSubCluster use JCache.

JIRA: YARN-10885. add FederationStateStoreFacade#getApplicationHomeSubCluster use JCache.
JunitTest will be added later.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
17m 11s

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 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
41m 13s

trunk passed

+1 :green_heart:
compile
0m 50s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
0m 46s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 40s

trunk passed

+1 :green_heart:
mvnsite
0m 51s

trunk passed

+1 :green_heart:
javadoc
0m 53s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 42s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 41s

trunk passed

+1 :green_heart:
shadedclient
24m 21s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 34s

the patch passed

+1 :green_heart:
compile
0m 44s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

-1 :x:
javac
0m 44s
/results-compile-javac-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.txt
hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> generated 1 new + 53 unchanged - 0 fixed = 54 total (was 53)

+1 :green_heart:
compile
0m 34s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

-1 :x:
javac
0m 34s
/results-compile-javac-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.txt
hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 generated 1 new + 50 unchanged - 0 fixed = 51 total (was 50)

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 23s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common.txt
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common: The patch generated 5 new + 11 unchanged - 0 fixed = 16 total (was 11)

+1 :green_heart:
mvnsite
0m 41s

the patch passed

+1 :green_heart:
javadoc
0m 33s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 33s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 37s

the patch passed

+1 :green_heart:
shadedclient
24m 24s

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

_ Other Tests _

-1 :x:
unit
2m 45s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common.txt
hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
asflicense
0m 43s

The patch does not generate ASF License warnings.

123m 14s

Reason
Tests

Failed junit tests
hadoop.yarn.server.federation.utils.TestFederationStateStoreFacade

Subsystem
Report/Notes

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

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

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

uname
Linux c083b7b2422a 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / d45e599b72403206491bc174bfaff064599ab456

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common

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

+1 :green_heart:
mvninstall
42m 17s

trunk passed

+1 :green_heart:
compile
0m 54s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
0m 44s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 40s

trunk passed

+1 :green_heart:
mvnsite
0m 51s

trunk passed

+1 :green_heart:
javadoc
0m 54s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 41s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 42s

trunk passed

+1 :green_heart:
shadedclient
24m 24s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 36s

the patch passed

+1 :green_heart:
compile
0m 39s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

-1 :x:
javac
0m 39s
/results-compile-javac-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.txt
hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> generated 1 new + 53 unchanged - 0 fixed = 54 total (was 53)

+1 :green_heart:
compile
0m 34s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

-1 :x:
javac
0m 34s
/results-compile-javac-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.txt
hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 generated 1 new + 50 unchanged - 0 fixed = 51 total (was 50)

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 21s

the patch passed

+1 :green_heart:
mvnsite
0m 36s

the patch passed

+1 :green_heart:
javadoc
0m 32s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 29s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 25s

the patch passed

+1 :green_heart:
shadedclient
23m 42s

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

_ Other Tests _

+1 :green_heart:
unit
2m 47s

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

+1 :green_heart:
asflicense
0m 41s

The patch does not generate ASF License warnings.

107m  1s

Subsystem
Report/Notes

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

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

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

uname
Linux 3e46431f81e3 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 6ad96074674391e41239df779717790d4d5030a3

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common

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

@goiri Please help to review the code again, thank you very much!

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 50s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  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 _

+1 :green_heart:
mvninstall
42m 20s

trunk passed

+1 :green_heart:
compile
0m 49s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
0m 45s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 37s

trunk passed

+1 :green_heart:
mvnsite
0m 54s

trunk passed

+1 :green_heart:
javadoc
0m 58s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 43s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 49s

trunk passed

+1 :green_heart:
shadedclient
24m 26s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 40s

the patch passed

+1 :green_heart:
compile
0m 41s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

-1 :x:
javac
0m 41s
/results-compile-javac-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.txt
hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> generated 1 new + 53 unchanged - 0 fixed = 54 total (was 53)

+1 :green_heart:
compile
0m 34s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

-1 :x:
javac
0m 34s
/results-compile-javac-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.txt
hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 generated 1 new + 50 unchanged - 0 fixed = 51 total (was 50)

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 23s

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common: The patch generated 0 new + 10 unchanged - 1 fixed = 10 total (was 11)

+1 :green_heart:
mvnsite
0m 37s

the patch passed

+1 :green_heart:
javadoc
0m 34s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 31s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

-1 :x:
spotbugs
1m 43s
/new-spotbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common.html
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
shadedclient
24m 29s

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

_ Other Tests _

-1 :x:
unit
2m 46s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common.txt
hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
asflicense
0m 45s

The patch does not generate ASF License warnings.

108m 15s

Reason
Tests

SpotBugs
module:hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common

org.apache.hadoop.yarn.api.records.ApplicationId is incompatible with expected argument type String in org.apache.hadoop.yarn.server.federation.utils.FederationStateStoreFacade.getApplicationHomeSubCluster(ApplicationId)  At FederationStateStoreFacade.java:argument type String in org.apache.hadoop.yarn.server.federation.utils.FederationStateStoreFacade.getApplicationHomeSubCluster(ApplicationId)  At FederationStateStoreFacade.java:[line 386]

Failed junit tests
hadoop.yarn.server.federation.utils.TestFederationStateStoreFacade

Subsystem
Report/Notes

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

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

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

uname
Linux 2f5dd32d4381 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 0c9d64877a40db7b319ae6628f8a00b9938ec7d1

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common

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

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  1s

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 _

+1 :green_heart:
mvninstall
42m 18s

trunk passed

+1 :green_heart:
compile
0m 53s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
0m 49s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 42s

trunk passed

+1 :green_heart:
mvnsite
0m 55s

trunk passed

+1 :green_heart:
javadoc
1m  0s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 42s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 46s

trunk passed

+1 :green_heart:
shadedclient
24m 36s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 39s

the patch passed

+1 :green_heart:
compile
0m 44s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

-1 :x:
javac
0m 44s
/results-compile-javac-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.txt
hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> generated 1 new + 53 unchanged - 0 fixed = 54 total (was 53)

+1 :green_heart:
compile
0m 37s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

-1 :x:
javac
0m 37s
/results-compile-javac-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.txt
hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 generated 1 new + 50 unchanged - 0 fixed = 51 total (was 50)

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 25s

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common: The patch generated 0 new + 10 unchanged - 1 fixed = 10 total (was 11)

+1 :green_heart:
mvnsite
0m 45s

the patch passed

+1 :green_heart:
javadoc
0m 35s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 29s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

-1 :x:
spotbugs
1m 39s
/new-spotbugs-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common.html
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
shadedclient
23m 56s

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

_ Other Tests _

-1 :x:
unit
2m 50s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common.txt
hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
asflicense
0m 42s

The patch does not generate ASF License warnings.

108m 17s

Reason
Tests

SpotBugs
module:hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common

org.apache.hadoop.yarn.api.records.ApplicationId is incompatible with expected argument type String in org.apache.hadoop.yarn.server.federation.utils.FederationStateStoreFacade.getApplicationHomeSubCluster(ApplicationId)  At FederationStateStoreFacade.java:argument type String in org.apache.hadoop.yarn.server.federation.utils.FederationStateStoreFacade.getApplicationHomeSubCluster(ApplicationId)  At FederationStateStoreFacade.java:[line 386]

Failed junit tests
hadoop.yarn.server.federation.utils.TestFederationStateStoreFacade

Subsystem
Report/Notes

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

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

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

uname
Linux c8eb9cedb068 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 0c9d64877a40db7b319ae6628f8a00b9938ec7d1

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common

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

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 48s

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  1s

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 _

+1 :green_heart:
mvninstall
41m 51s

trunk passed

+1 :green_heart:
compile
0m 51s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
0m 46s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 40s

trunk passed

+1 :green_heart:
mvnsite
0m 51s

trunk passed

+1 :green_heart:
javadoc
0m 54s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 42s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 40s

trunk passed

+1 :green_heart:
shadedclient
23m 50s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 35s

the patch passed

+1 :green_heart:
compile
0m 39s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
0m 39s

the patch passed

+1 :green_heart:
compile
0m 33s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 33s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 21s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common.txt
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common: The patch generated 1 new + 10 unchanged - 1 fixed = 11 total (was 11)

+1 :green_heart:
mvnsite
0m 37s

the patch passed

+1 :green_heart:
javadoc
0m 32s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 29s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 25s

the patch passed

+1 :green_heart:
shadedclient
23m 27s

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

_ Other Tests _

+1 :green_heart:
unit
2m 46s

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

+1 :green_heart:
asflicense
0m 42s

The patch does not generate ASF License warnings.

105m 44s

Subsystem
Report/Notes

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

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

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

uname
Linux 628bba0259e1 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 12d77ad81edcf288c4fc02e70f3485a79abe9ee7

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common

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

+1 :green_heart:
mvninstall
41m  0s

trunk passed

+1 :green_heart:
compile
0m 51s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
0m 46s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 40s

trunk passed

+1 :green_heart:
mvnsite
0m 51s

trunk passed

+1 :green_heart:
javadoc
0m 55s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 42s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 40s

trunk passed

+1 :green_heart:
shadedclient
24m  2s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 35s

the patch passed

+1 :green_heart:
compile
0m 40s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
0m 40s

the patch passed

+1 :green_heart:
compile
0m 33s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 33s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 22s

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common: The patch generated 0 new + 10 unchanged - 1 fixed = 10 total (was 11)

+1 :green_heart:
mvnsite
0m 38s

the patch passed

+1 :green_heart:
javadoc
0m 32s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 31s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 31s

the patch passed

+1 :green_heart:
shadedclient
23m 51s

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

_ Other Tests _

+1 :green_heart:
unit
2m 46s

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

+1 :green_heart:
asflicense
0m 42s

The patch does not generate ASF License warnings.

105m 30s

Subsystem
Report/Notes

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

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

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

uname
Linux 28cfbcc832ba 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 0eefb19e003b934c7314abbfced5203f959148d0

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common

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

@goiri Please help to review the code again, thank you very much!

@goiri Please help to review the code again, thank you very much!

: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 _

+1 :green_heart:
mvninstall
41m  3s

trunk passed

+1 :green_heart:
compile
0m 52s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
0m 46s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 41s

trunk passed

+1 :green_heart:
mvnsite
0m 51s

trunk passed

+1 :green_heart:
javadoc
0m 54s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 42s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 40s

trunk passed

+1 :green_heart:
shadedclient
24m 14s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 34s

the patch passed

+1 :green_heart:
compile
0m 41s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
0m 41s

the patch passed

+1 :green_heart:
compile
0m 34s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 34s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 22s

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common: The patch generated 0 new + 10 unchanged - 1 fixed = 10 total (was 11)

+1 :green_heart:
mvnsite
0m 37s

the patch passed

+1 :green_heart:
javadoc
0m 33s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 29s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 27s

the patch passed

+1 :green_heart:
shadedclient
23m 46s

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

_ Other Tests _

+1 :green_heart:
unit
2m 46s

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

+1 :green_heart:
asflicense
0m 42s

The patch does not generate ASF License warnings.

105m 40s

Subsystem
Report/Notes

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

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

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

uname
Linux 5984ce125517 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / ce5ca51ede060697da77e7dc71bcb16cfd8813e3

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common

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

@goiri Please help to review the code again, Thank you very much!

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 45s

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 _

+1 :green_heart:
mvninstall
41m 36s

trunk passed

+1 :green_heart:
compile
0m 53s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
0m 45s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 40s

trunk passed

+1 :green_heart:
mvnsite
0m 51s

trunk passed

+1 :green_heart:
javadoc
0m 54s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 42s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 41s

trunk passed

+1 :green_heart:
shadedclient
23m 48s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 36s

the patch passed

+1 :green_heart:
compile
0m 40s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
0m 40s

the patch passed

+1 :green_heart:
compile
0m 35s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 35s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 20s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-common.txt
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common: The patch generated 5 new + 10 unchanged - 1 fixed = 15 total (was 11)

+1 :green_heart:
mvnsite
0m 37s

the patch passed

+1 :green_heart:
javadoc
0m 32s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 30s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 25s

the patch passed

+1 :green_heart:
shadedclient
24m 10s

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

_ Other Tests _

+1 :green_heart:
unit
2m 47s

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

+1 :green_heart:
asflicense
0m 42s

The patch does not generate ASF License warnings.

106m  7s

Subsystem
Report/Notes

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

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

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

uname
Linux 4ff157afc7d2 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / fb42275602f4a7c125e6e764a230ead1beec24c9

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common

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

@goiri Please help to review the code again, thank you very much!

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 48s

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 _

+1 :green_heart:
mvninstall
43m 29s

trunk passed

+1 :green_heart:
compile
0m 52s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
0m 46s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 40s

trunk passed

+1 :green_heart:
mvnsite
0m 52s

trunk passed

+1 :green_heart:
javadoc
0m 54s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 42s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 40s

trunk passed

+1 :green_heart:
shadedclient
24m 12s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 35s

the patch passed

+1 :green_heart:
compile
0m 39s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
0m 39s

the patch passed

+1 :green_heart:
compile
0m 33s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 33s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 21s

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common: The patch generated 0 new + 10 unchanged - 1 fixed = 10 total (was 11)

+1 :green_heart:
mvnsite
0m 36s

the patch passed

+1 :green_heart:
javadoc
0m 32s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 30s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 26s

the patch passed

+1 :green_heart:
shadedclient
23m 45s

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

_ Other Tests _

+1 :green_heart:
unit
2m 45s

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

+1 :green_heart:
asflicense
0m 41s

The patch does not generate ASF License warnings.

107m 42s

Subsystem
Report/Notes

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

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

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

uname
Linux 1d075bf83006 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 7a9c9a5c322f29af22c0153f25aa241e32f7cb48

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common

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

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 45s

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 _

+1 :green_heart:
mvninstall
43m  6s

trunk passed

+1 :green_heart:
compile
0m 51s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
0m 47s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 40s

trunk passed

+1 :green_heart:
mvnsite
0m 52s

trunk passed

+1 :green_heart:
javadoc
0m 54s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 41s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 42s

trunk passed

+1 :green_heart:
shadedclient
24m 16s

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

-0 :warning:
patch
24m 39s

Used diff version of patch file. Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 35s

the patch passed

+1 :green_heart:
compile
0m 39s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
0m 39s

the patch passed

+1 :green_heart:
compile
0m 34s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 34s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 21s

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common: The patch generated 0 new + 10 unchanged - 1 fixed = 10 total (was 11)

+1 :green_heart:
mvnsite
0m 36s

the patch passed

+1 :green_heart:
javadoc
0m 32s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 30s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 27s

the patch passed

+1 :green_heart:
shadedclient
23m 39s

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

_ Other Tests _

+1 :green_heart:
unit
2m 46s

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

+1 :green_heart:
asflicense
0m 41s

The patch does not generate ASF License warnings.

107m 32s

Subsystem
Report/Notes

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

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

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

uname
Linux 4f7a582835cc 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 0ed4dd4f501fcd1d924c6da5e937338e4e963cb2

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4701/11/testReport/

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

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common

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

@goiri Thank you very much for helping to review the code!


x/pkgsite: better discoverability for extension interfaces

I was reading https://pkg.go.dev/io/fs, trying to find all the extension interfaces available for fs.FS. I had to scan the entire package API. It would have been even harder had the package not used a consistent naming convention.
Now that the standard library is using it, I suspect we'll see increasing uptake of the extension pattern. It'd be nice if pkg.go.dev could recognize it and surface extension interfaces, either through different grouping or through an explicit list at the base interface type.

yes yes milestone it is i see! love it. hard work of learning does pay off


404 broken link on README.md to BioConda install

https://bioconda.github.io/user/install.html

Hi,
Thanks for pointing that. I've updated the url.
Best
Santiago


libretro.fuse: init at unstable-2023-06-23

Description of changes
A port of the Fuse Unix Spectrum Emulator to libretro: https://github.com/libretro/fuse-libretro.
For reference, homepage of the Fuse emulator itself: https://sourceforge.net/projects/fuse-emulator/
Things done

Built on platform(s)

[x] x86_64-linux
[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

@ofborg eval


[INLONG-3883][Manager] Support create table of ClickHouse

Title Name: [INLONG-3883][Manager]Support create table with clickhouse
Add create table to Manager Group.

git rebase master before pull request.


Feature: dev menu option to change packager location during runtime

Add an option to dev menu to change packager location on the fly on iOS (similar to Dev Settings in Android)
Test Plan:
Tested the code change in iOS 12.1 beta 5, Xcode 10.1 beta. Set up two different PCs in the same LAN, then pointed to each one of them during runtime. Then closed the app and reopened to confirm that the last setting persists in user defaults.

Release Notes:
[IOS] [FEATURE] [DevMenu] - Added an option to change packager location during runtime

It looks like this PR doesn't work with changing bundler ports. Created an issue here: https://github.com/facebook/react-native/issues/25772


Upgrade to Pyarrow 1.0

In #1377 we require pyarrow<0.17, but since Pyarrow 1.0 released, we should update to new stable API.

Gandiva appears to be no longer part of the default pyarrow wheel.
There is an open issue to package it separately: https://issues.apache.org/jira/browse/ARROW-8518

Thanks @itamarst, this will be an issue in updating. Unfortunately that issue is slated for resolution in version 2. We probably will have to make the gandiva import conditional.


Router fails with 2+ implicit bindings where one of the params does not match function variable name

Laravel Version: 5.3.19
PHP Version: 5.6.19
Database Driver & Version: MySQL mariadb-10.1.9

Description:
When resolving the route where one of the params does not match an implicit binding name, an exception is thrown:
Argument 2 passed to App\Providers\RouteServiceProvider::{closure}() must be an instance of App\User, string given, called in ...\vendor\laravel\framework\src\Illuminate\Routing\Route.php on line 176 and defined

Steps To Reproduce:
Create a route
Route::get('/{user}/{childid}', function (\App\User $user, \App\User $child) {
    return [$user->toArray(), $child->toArray()];
});

and try to access it: e.g. laravel.app/1/2
Is this supposed to happen, from my understanding the expected behavior should be that it at least passes an empty model to the second param?

You need to have the parameter name matching the name in the route definition:
/{user}/{child} instead of /{user}/{childid}

Then is there a way to change how the implicit model binding should be resolved without binding all kinds of parameter names?

Not sure I understand what you mean.

In Router class, there is $method = $parameter->isDefaultValueAvailable() ? 'first' : 'firstOrFail';, but I want to manually decide how it should be resolved - if it's an integer, then first/firstOrFail, else try to unhash the value ant find the model.

Now I have to bind every model name parameter I have to get custom behavior.

What do you mean by "unhash"?

I use hashed id's for models instead plain ids so the requests end up like dashboard/clients/z1vre64enk87 and to make this work I have to bind all parameters which I'm doing in RouteServiceProvider.
$this->bindModelParamsByHashId($router, [
            'client',
            'company',
            ....
        ]);

protected function bindModelParamsByHashId($router, array $names)
    {
        foreach ($names as $key => $value) {
            $routeParam = $value;
            $class = '\\App\\Database\\' . ucfirst(Str::camel($routeParam));

            if (is_string($key)) {
                $routeParam = $key;
                $class = $value;
            }

            $router->bind($routeParam, function ($value) use ($class) {
                return $class::findOrFail(unhashid($value));
            });
        }
    }


feat: Allow to serialize source files into a snapshot

This commit changes snapshotting methods to allow to serde
source files.
The pointers to these source files are passed to V8, but we currently
don't use this functionality. I'll try to implement that before landing this PR.

Not needed anymore.


Fix instanceof check and cast with pattern matching (#85)

related to #85

Sorry @dirk-olmes I did not recognize that the findings have already been adressed for a long time. Just ping in a comment. Did you know that you could (re-)request a review when clicking on one of the reviewers in top right?


[ITensors] [BUG] Inconsistent Behavior of mindim

Description of bug
When using mindim!, the link dimension behavior at the "edge" is different depending on the value of cutoff!.
If there is a cutoff, some tensors get set to the mindim while others are not, and if there isn't a cutoff (cutoff!(sweeps,0)) the link dimensions are symmetric.  I'm not sure which output is preferred but I suspect its the latter?
Minimal code demonstrating the bug or unexpected behavior
Minimal runnable code
using ITensors

N = 32
sites = siteinds("S=1/2", N; conserve_qns=false)

ampo = AutoMPO()
for j in 1:(N - 1)
  ampo .+= 0.5, "S+", j, "S-", j + 1
  ampo .+= 0.5, "S-", j, "S+", j + 1
  ampo .+= "Sz", j, "Sz", j + 1
end
H = MPO(ampo, sites)

ψ₀ = randomMPS(sites)

sweeps = Sweeps(6)
maxdim!(sweeps, 4, 16, 64)
mindim!(sweeps, 1, 16,64,)
cutoff!(sweeps,1e-10)
noise!(sweeps, 0)
energy, ψ = @time dmrg(H, ψ₀, sweeps)
@show linkdims(ψ)

Expected output or behavior
Expected Output
If cutoff!(sweeps,0):
linkdims(ψ) = [2, 4, 8, 16, 32, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 32, 16, 8, 4, 2]

Actual output or behavior
Output of minimal runnable code
linkdims(ψ) = [64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 64, 32, 16, 8, 4, 2]

Version information

Output from versioninfo():

julia> versioninfo()
Julia Version 1.8.5
Commit 17cfb8e65ea (2023-01-08 06:45 UTC)
Platform Info:
  OS: Linux (x86_64-linux-gnu)
  CPU: 24 × Intel(R) Xeon(R) Gold 6128 CPU @ 3.40GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-13.0.1 (ORCJIT, skylake-avx512)
  Threads: 1 on 24 virtual cores

Output from using Pkg; Pkg.status("ITensors"):

julia> using Pkg; Pkg.status("ITensors")
Status `~/.julia/environments/v1.8/Project.toml`
  [9136182c] ITensors v0.3.43

I think this may be because we don't really have a full QR/SVD, only thin versions, so the maximum dimension is set by the smaller matrix dimension and you get these boundary effects depending on the sweep direction.

Though I'm a bit confused about what behavior you are hoping for, do you want the bonds to be 64 everywhere?
Because of the thin QR/SVD, the bond dimension pattern will depend on the gauge center, which isn't really something particular to the DMRG function (i.e. try orthogonalize(ψ, 1), orthogonalize(ψ, N), orthogonalize(ψ, N÷2)).

My personal preference would be forcing of the bulk tensors to be the mindim but would also be ok with 64 everywhere, as long as its consistent. (This came up benchmarking two codes where I was trying to get the tensor sizes to match exactly)

I thought in your example above mindim is 64, so I'm a bit confused by your comment where it seems like you're implying they are different from each other. Also it seems like the bulk tensors are mindim/64 in the output you show in your first post.

To get the output you expected (based on your first post) does it work to call orthogonalize(ψ, N÷2)?

Yeah I can call orthogonalize(ψ, N÷2)  to get it in the right form at the end, but during DMRG sweeping the wave function sometimes has [2, 4, 8, 16, 32, 64, 64,...` as the link dims but ends with `[64, 64, 64, 64, 64, 64, 64, 64,` on the left side only.
Here are the link dims at every sweep for `N=12`
[2, 64, 64, 64, 64, 64, 32, 16, 8, 4, 2]
[2, 4, 64, 64, 64, 64, 32, 16, 8, 4, 2]
[2, 4, 8, 64, 64, 64, 32, 16, 8, 4, 2]
[2, 4, 8, 16, 64, 64, 32, 16, 8, 4, 2]
[2, 4, 8, 16, 32, 64, 32, 16, 8, 4, 2]
[2, 4, 8, 16, 32, 64, 32, 16, 8, 4, 2]
[2, 4, 8, 16, 32, 64, 64, 16, 8, 4, 2]
[2, 4, 8, 16, 32, 64, 64, 64, 8, 4, 2]
[2, 4, 8, 16, 32, 64, 64, 64, 64, 4, 2]
[2, 4, 8, 16, 32, 64, 64, 64, 64, 64, 2]
[2, 4, 8, 16, 32, 64, 64, 64, 64, 64, 64]
[2, 4, 8, 16, 32, 64, 64, 64, 64, 64, 2]
[2, 4, 8, 16, 32, 64, 64, 64, 64, 4, 2]
[2, 4, 8, 16, 32, 64, 64, 64, 8, 4, 2]
[2, 4, 8, 16, 32, 64, 64, 16, 8, 4, 2]
[2, 4, 8, 16, 32, 64, 32, 16, 8, 4, 2]
[2, 4, 8, 16, 32, 64, 32, 16, 8, 4, 2]
[2, 4, 8, 16, 64, 64, 32, 16, 8, 4, 2]
[2, 4, 8, 64, 64, 64, 32, 16, 8, 4, 2]
[2, 4, 64, 64, 64, 64, 32, 16, 8, 4, 2]
[2, 64, 64, 64, 64, 64, 32, 16, 8, 4, 2]
[64, 64, 64, 64, 64, 64, 32, 16, 8, 4, 2]

Is this the bond dimension after each sweep or each 2-site update? If it's the latter, that's what I would expect based on how MPS gauging works.

It's after each 2-site update (in measure! I have println("$(linkdims(psi))")).
After each sweep (once we hit 64) the bond dimensions are [64, 64, 64, 64, 64, 64, 32, 16, 8, 4, 2]

Basically, if you imagine doing a sweep without doing any actual updates (say DMRG on an identity MPO), it should act like calling orthogonalize on each sweep location j.

Quick update, a more minimal example. Say we have a two-site tensor that we want to factorize
s  = Index(2)
s′ = Index(2)
l = Index(64)
r = Index(16)
T = randomITensor(l,s,s′,r)

The inconsistent behavior manifests as
> L,R,spec = factorize(T,l,s; cutoff=0,mindim=64)
> @show inds(L)
inds(L) = ((dim=64|id=719), (dim=2|id=499), (dim=32|id=847|"Link,fact"))

where we get the 64->32 stepdown.
Or with cutoff
> L,R,spec = factorize(T,l,s; cutoff=1e-10,mindim=64)
> @show inds(L)
inds(L) = ((dim=64|id=444), (dim=2|id=941), (dim=64|id=961|"Link,fact"))

Where the factorize respects the mindim by pads the link dimension. I think the cutoff=0 behavior is best here.

Thanks. So when you call factorize with cutoff=1e-10, it calls the ITensors.factorize_eigen backend, which uses a Hermitian eigendecomposition instead of an SVD for performance when the cutoff is larger that 1e-12 and therefore high precision of the singular values isn't needed.
You can see that here:
julia> L, R = ITensors.factorize_eigen(T, l, s; cutoff=1e-4, mindim=64);

julia> R
ITensor ord=3 (dim=64|id=630|"Link,eigen")' (dim=2|id=791) (dim=16|id=387)
NDTensors.Dense{Float64, Vector{Float64}}

julia> L
ITensor ord=3 (dim=64|id=131) (dim=2|id=103) (dim=64|id=630|"Link,eigen")'
NDTensors.Dense{Float64, Vector{Float64}}

This helps explain some of the confusion I had about this behavior, since using an eigendecomposition circumvents the thin QR/SVD behavior.
I quick fix could be to set the maxdim in factorize_eigen to the minimum dimension of the left or right spaces.


Fix neogeo cd scraping

Platform name needs to be changed from console to neogeocd.

This has been accommodated as part of today's online update.

This has been accommodated as part of today's online update.


Laura content apr21

All Sauce Connect, Live Testing, and Test Results content.

Description

Motivation and Context

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[X] Documentation fix (typos, incorrect content, missing content, etc.)

Checklist

[ ] I have read the contributing document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@lauramthomas I'm confused now, is this the new branch/pr to work off of? If so can you close the other PR?

@spider-sauce Yes, this is the new, possibly functional branch. I just closed lt-content-merge.


Support opting out of tessen phone home

Pull Request Checklist

Description

Support the ability to opt out of tessen phone home.
Motivation and Context

Sensu Go 5.5 added Tessen phone-home and is opt-in by default.  This change maintains default behavior of opt-in but makes it easy to opt-out.
How Has This Been Tested?

Unit and acceptance.

Looks great, just waiting on Travis. Thanks @treydock


Lex line comments with no trailing newline.

Fixes #422. The spec does require line comments to end with a newline character, but I think that's an unnecessary restriction, so I'm happy to update it too if this is okay.

Yeah makes sense, thanks!
Also, we're in the process of changing the license, so if you agree to the change, can you sign off your contribution under the new license as stated in the thread?

Yep, I'll do that, though I'd prefer not to use my full name if that's alright. Should I just use name on the commit instead?

I guess you can use your GitHub username lol. I mean the consent is not a magical incantation.

Thanks!


Update client.go

quote field in order condition

@xujif was not having quotes causing any issues?

@sosedoff  can not order the data when click the field which with uppercases

@xujif Could you provide an example SQL so i can reproduce, add a test and fix the issue?

Nevermind, i was able to fix the issue in #191.


Width text see picture

I already have set font size 36pt on Visual Studio Code.app for mac
Please fix width see picture

This is a duplicate. Unfortunately, I don't recall the exact issue number nor its title :flushed: Anyways, searching for issues with the same labels will likely help you :point_right:
https://github.com/microsoft/vscode/issues?utf8=✓&q=is%3Aopen+label%3Asuggest+label%3Aux

Allright I have low vision and I use UI enlarge of ACCESSIBILITY.
When too small text hurt my eyes on focus.

I understand that and what I said is that there is already an issue that discusses custom/better sizing of the suggest widget

goooooooooooood Thank you for explain me


export 'internal_processStyles' (imported as 'processStyles') was not found in '@mui/styled-engine'

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
The React app won't start as this error pops up when I run yarn start on my project with the latest version of @mui/material (5.10.0). The error I am seeing is:
Compiled with problems:X

ERROR in<EMAIL_ADDRESS>106:4-17

export 'internal_processStyles' (imported as 'processStyles') was not found in '@mui/styled-engine' (possible exports: GlobalStyles, StyledEngineProvider, ThemeContext, css, default, keyframes)

Expected behavior 🤔
My React app should compile without errors.
Steps to reproduce 🕹
Not completely sure where this error is arising from.
Steps:

Upgrade to @mui/material at version 5.10.0
I am using also styled-components at version 5.3.5
In my tests, it points that the error is coming from here import { createTheme } from '@mui/material/styles';

Context 🔦
I just got an update of @mui/material from dependabot and all my tests are failing. I am just trying to upgrade this dependency.
Your environment 🌎

npx @mui/envinfo
  System:
    OS: Linux 5.15 Ubuntu 20.04.4 LTS (Focal Fossa)
  Binaries:
    Node: 17.9.0 - ~/.nvm/versions/node/v17.9.0/bin/node
    Yarn: 1.22.18 - ~/.nvm/versions/node/v17.9.0/bin/yarn
    npm: 8.5.5 - ~/.nvm/versions/node/v17.9.0/bin/npm
  Browsers:
    Chrome: 104.0.5112.79
    Firefox: 103.0
  npmPackages:
    @mui/base:  5.0.0-alpha.92
    @mui/material: ^5.10.0 => 5.10.0
    @mui/private-theming:  5.9.3
    @mui/styled-engine-sc:  5.4.2
    @mui/system: ^5.10.0 => 5.10.0
    @mui/types:  7.1.5
    @mui/utils:  5.9.3
    @mui/x-data-grid:  5.15.1
    @mui/x-data-grid-pro: ^5.15.1 => 5.15.1
    @mui/x-license-pro: ^5.15.0 => 5.15.0
    @types/react: ^17.0.40 => 17.0.40
    react: ^17.0.2 => 17.0.2
    react-dom: ^17.0.2 => 17.0.2
    styled-components: ^5.3.5 => 5.3.5
    typescript: ^4.7.4 => 4.7.4

Same issue here.

i have the same error : 'internal_processStyles' is not exported from '@mui/styled-engine' (imported as 'processStyles')
Version mui : "@mui/material": "5.4.4"
Version React : "17.0.2"
is this issue still in progress?

Just a heads up @DavidArmendariz & @mpanjato, I was able to resolve this issue by upgrading the following packages to the latest version:
<EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

@cjones26 @mnajdova Thanks! I guess dependabot doesn't make upgrades to @mui/styled-engine because of the way it is specified in package.json?
"dependencies: {
  "@mui/styled-engine": "npm:@mui/styled-engine-sc@latest",
  ...
},
"resolutions": {
  "@mui/styled-engine": "npm:@mui/styled-engine-sc@latest"
}

Is this still the correct way to specify @mui/styled-engine package?

any news on this? my dev env is unusable without me changing anything

@giladv upgrading @mui/styled-engine worked for me.

doesn't work with styled-engine-sc unfortunately for me

doesn't work with styled-engine-sc unfortunately for me

Try updating all MUI related packages.  If that still doesn't work, it's likely another third-party package is pulling in an older version of @mui/styled-engine-sc and / or @mui/material which you may need to add to overrides (if using npm) or resolutions (if using yarn).

nothing works.

tried updating all packages to latest
removing yarn.lock

for some reason styled-engine-sc is staying 5.8 while there's already a 5.10

FINALLY. for anyone having problem with this make<EMAIL_ADDRESS>will not work with latest mui/system version.
do everything you can to make yarn upgrade it. including messing with yarn.lock

The solution to return to 5.8.0 was not working for me with these values in package.json:
"dependencies": {
  "@mui/styled-engine": "npm:@mui/styled-engine-sc@latest",
  "@mui/styled-engine-sc": "5.8.0"
},
"resolutions": {
  "@mui/styled-engine": "npm:@mui/styled-engine-sc@latest"
},

However, our app builds correctly with this package in dependencies:
"@mui/styled-engine-sc": "5.9.3",

By the way, we are finally upgrading the Text-Em-All web app to MUI v5...the app that started this entire project. Thanks for the continuing development and care that you put into MUI, everyone! 🙏

By the way, we are finally upgrading the Text-Em-All web app to MUI v5...the app that started this entire project. Thanks for the continuing development and care that you put into MUI, everyone! 🙏

Nice to hear this! :) Out of curiosity @m2mathew, why did you decided to use styled-components instead of emotion? There are still some issues around it, related to SSR, e. g. https://github.com/mui/material-ui/issues/29742. I am curious to knwo what's the reason for people to put additional effort just to be able to use styled-components.

By the way, we are finally upgrading the Text-Em-All web app to MUI v5...the app that started this entire project. Thanks for the continuing development and care that you put into MUI, everyone! 🙏

Nice to hear this! :) Out of curiosity @m2mathew, why did you decided to use styled-components instead of emotion? There are still some issues around it, related to SSR, e. g. #29742. I am curious to knwo what's the reason for people to put additional effort just to be able to use styled-components.

@mnajdova We had already moved about 50% of the web app to use styled-components in Material-UI v4 instead of JSS. It seemed like an easier solution to use styled-components for MUI v5, too. Our web app is client-side rendered, so we don't have any issues with it...at least not in the giant feature PR that is making this change. 😅

@mnajdova We had already moved about 50% of the web app to use styled-components in Material-UI v4 instead of JSS. It seemed like an easier solution to use styled-components for MUI v5, too. Our web app is client-side rendered, so we don't have any issues with it...at least not in the giant feature PR that is making this change. 😅

Sounds like it should work as expected, thanks for the info :))

@cjones26 & @mnajdova thank you, upgrading @mui/styled-engine worked for me too

I don't know how it's possible but after updating InputBase stop accepting styles.
here is my pkgs:
"@mui/lab": "^5.0.0-alpha.91",
"@mui/material": "^5.10.2",
"@mui/x-data-grid-premium": "^5.16.0",
"@mui/x-license-pro": "^5.16.0",
"overrides": {
    "@mui/styled-engine": <EMAIL_ADDRESS>}

And downgrade causes the same problem as mentioned in issue.
Any idea?

I'm getting this suddenly despite having changed no dependency versions.
It seems to be tracking it back to @mui/lab/Masonry:
ERROR in ./node_modules/<EMAIL_ADDRESS>115:4-17
export 'internal_processStyles' (imported as 'processStyles') was not found in '@mui/styled-engine' (possible exports: GlobalStyles, StyledEngineProvider, ThemeContext, css, default, keyframes)
 @ ./node_modules/<EMAIL_ADDRESS>35:0-57 35:0-57 36:0-31 36:0-31
<EMAIL_ADDRESS>6:0-139 64:24-47 68:22-40 72:27-35 83:29-46 86:23-46 94:56-64 102:29-46 107:31-48 113:24-32
<EMAIL_ADDRESS>1:0-36 1:0-36

I'm getting this suddenly despite having changed no dependency versions.
It seems to be tracking it back to @mui/lab/Masonry:

Can you please create an issue with reproduction? Would be great to know the specific versions you use.

I had this fixed with 'use client' in NextJS.


[NetAppFiles] ANF-31445 :  Add x-ms-mutability and x-ms-secret extensions for unix permissions property.

ARM (Control Plane) API Specification Update Pull Request

Tip: overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

 Click here to see the details of Step 1
Breaking changes review (Diagram Step 1)
If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

 Click here to see the details of Step 2
ARM API changes review (Diagram Step 2)

If this PR is in purview of ARM review then automation will add the ARMReview label.
If you want to force ARM review, add the label yourself.
Proceed according to the diagram at the top of this comment.

 Click here to see the diagram footnotes
Diagram footnotes
[1] ARM review queue (for merge queues, see [2])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] public repo merge queue, private repo merge queue (for ARM review queue, [1])
If you need further help with anything, see Getting help section below.

Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[ ] New API version. (If API spec is not defined in TypeSpec, the PR should have been generated using OpenAPI Hub).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[x] Other, please clarify:

Update existing swagger for enhancing user experience

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the Diagram Step 2, "ARM API changes Review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

@Reviewer: This change was already reviewed & approved with https://github.com/Azure/azure-rest-api-specs-pr/pull/16442. Reraising the MR for targeting to different API version only.

Due to some reasons, it was decided to not add this change. For more details, pls refer ANF-31445.
Closing the MR.


Parallelize the module build in python/setup.py

Installing jotdown from pip is slower than it could be, because the module sources are compiled in sequence.  The pymodule_dev target in bake.py builds the module in parallel for testing purposes.  I'd like to figure out how to do this using a setuptools extension so that I can have parallel builds in setup.py too.  Maybe I can invoke bake.py instead of relying on setuptools to build the extension, or maybe I can just publish a binary distribution with the module pre-compiled.

Fixed in 7453c0d9adb392acd65454d057e948c6830267fd by consolidating module sources into a single jotdown.cpp.


Add bash shebang to toolchain build script

pushd and popd are bash-specific extensions, so the script does not properly work when run under (for example) zsh. This specifies that bash should be used.

Thanks for letting me know, however I find that they work under the majority of shells (including zsh), although it is does not work in busybox. I feel that it would be better to just remove pushd and popd.

Interesting, it didn't seem to work on my particular zsh shell.

Alright, I replaced the use of pushd and popd, it is preferable to me to use an alternative rather than force the use of a specific shell, thanks for highlighting the issue.


npm start error

bro when i try to run server it shows like this

npm start
npm ERR! missing script: start

npm ERR!      C:\Users\Neer\Appta\Roamig\npm-cache_logs\2020-08-12T12_58_58_386Z-debug.log

And also when i try to run index.js file it returns error as follows

node index.js
D:\realtime-face-recognition-master\socket.js:3
if (!cv.xmodules.face) {
^

TypeError: Cannot read property 'face' of undefined
at Object. (D:\realtime-face-recognition-master\socket.js:3:18)
at Module._compile (internal/modules/cjs/loader.js:1138:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
at Module.load (internal/modules/cjs/loader.js:986:32)
at Function.Module._load (internal/modules/cjs/loader.js:879:14)
at Module.require (internal/modules/cjs/loader.js:1026:19)
at require (internal/modules/cjs/helpers.js:72:18)
at Object. (D:\realtime-face-recognition-master\index.js:24:21)
at Module._compile (internal/modules/cjs/loader.js:1138:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)

can u please tell me .Thank u broo

bro when i try to run server it shows like this
npm start
npm ERR! missing script: start
npm ERR!  C:\Users\Neer\Appta\Roamig\npm-cache_logs\2020-08-12T12_58_58_386Z-debug.log

you have open cv installed properly right ?

properly in the sense i used npm to install opencv4nodejs.
I have to install opencv also ?.

I also checked for face module and it is present in the opencv4nodejs module als brooo

Yup its jst a wrapper for opencv
On Aug 13, 2020 at 9:49 AM, Neerajms25<EMAIL_ADDRESS>wrote:
properly in the sense i used npm to install opencv4nodejs.
I have to install opencv also ?.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/riazXrazor/realtime-face-recognition/issues/1#issuecomment-673245669,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADEVI6YUC2QXJXZXXH7J67TSANSWXANCNFSM4P4WKVWQ
.


pin community.general collection to version in dci repo

Some roles using community.general.python_requirements_info module are not playing well with the latest version (8.4.0) provided via galaxy. This CR is pinning the collection to match the version used in the rpm provided in DCI dnf repo.
Test-Hints: sno

This is an example of the jobs that are failing without the fix: https://www.distributed-ci.io/jobs/00665bb8-7e4c-4534-9ec4-e1427bd791af/jobStates?sort=date&task=1a2e1c67-780a-4011-a4c9-b1359c18d1e3


Where's customise button in 1.19.3

Ive launched fresh build with only Fabric API, Cloth Config and Modern Beta, theres just no button for some reason

It exists in 1.19.4 but not in 1.19.3 for some reason

Setup: Apple MacBook Air M2, Prism Launcher
Ask if you need any more info :)

Not implemented in 1.19.3, I just re-added it in 1.19.4.

The problem is that i really want to have it in 1.19.3 as i play this version right now and also theres not a lot of mods transfered to 1.19.4 yet
I'll be very happy if you will update version 1.19.3, please!

I will see whether backporting to 1.19.3 isn't too much trouble (vs. 1.19.3 -> 1.19.2 which contains much more changes under the hood).

I've updated the 1.19.3 version to 6.0, the whole feature list is there. If you run into any problems, feel free to open a new issue.


Widgets

Similar to Robin's system, allow for widget cells which maybe have custom UI using iframe
Also maybe allow the widgets to be developed in the same sheet as theyre being displayed
Wanna stay functional-ish in the spirit of sheets, so for widgets the "return value" of a widget should be a two-way websocket interface or similar. When the return value changes we do the same chaining execution that a spreadsheet would do, but the idea is that the channel won't change frequently.
There's additional questions about reactivity when in lua or etc, we can deal with that later I guess.
Widget Ideas

Budget app

Categorize transactions using tf-idf weighted words, sum words' weights on each transaction to try to guess the primary category
Simple spend analyzer
Import from CSV

For websocket output, you can create a "websocket" cell and have some cells which communicate over it using essentially pubsub.


order of keys shouldn't matter

Describe your problem and how to reproduce it:
The order of the keys shouldn't matter, but only solutions where the title key is above the rating key are accepted.
// this isn't accepted
const ratings = watchList.map(({ Title, imdbRating }) => ({
  rating: imdbRating,
  title: Title,
}));

// this is accepted
const ratings = watchList.map(({ Title, imdbRating }) => ({
  title: Title,
  rating: imdbRating,
}));

Add a Link to the page with the problem:
https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures/functional-programming/use-the-map-method-to-extract-data-from-an-array

@SimonSiefke Thanks for reporting.  I created a PR to resolve the issue.  Once it gets reviewed/merged, a user will be able to put the properties in any order (as it should be).


Git-ignore top-level /venv/ directory

I'm tired of accidentally committing my virtual
environment.
Change applies to cookiecutters for XBlocks, Python
packages, and Django apps, all of which are usually
developed using a virtual envs. Omitting IDAs because
they usually use Docker instead.

I use virtualenvs with the Python version in the name so that I can work with both 3.5 or 3.8, etc. How about /venv*/?

Several thoughts:

I use virtualenvs with the Python version in the name so that I can work with both 3.5 or 3.8, etc. How about /venv*/?
Several IDAs I've worked with are well-suited to running tests, building requirements, and another virtualenv-requiring actions outside of docker, so may as well include IDAs too.
Alternatively... you can also add whatever pattern you like to your global gitignore, which allows you to exclude temp files and IDE config files as well, independently of other people's working patterns.

you can rebase from master and run the CI checks manually from Actions

@timmc-edx Thanks for the global gitignore tip--that worked great for me.


Update favicon from react default

Reviewers: @taliamax @DudeRandom21
Description:
Add "legal scale" favicon to replace default react one.

I should mention that this will be added in later today as it'll require rebuilding the container


Version 0.0.2

Landed in https://github.com/metarhia/lowscript/commit/957b4876057a180d79db5a6c228e4a7b25c39969


[FLINK-25927][connectors] Make flink-connector-base dependency usage consistent across all connectors

What is the purpose of the change
flink-connector-base was previously inconsistently used in connectors (directly shaded in some and transitively pulled in via flink-connector-files which was itself shaded in the table uber jar). FLINK-24687 moved flink-connector-files out from the flink-table uber jar. This commit implements a combined approach for ensuring a smooth transition for both Flink users and for external connector developers, as outlined in this :

all internal Flink connectors that depend on flink-connector-base now shade and relocate it
for compatibility, until external developers implement the same change, flink-connector-base is also included into flink-dist

The rationale behind this combined approach was discussed here.
Brief change log

flink-connector-base dependency is shaded and relocated in all connectors
flink-connector-base is added into flink-dist

Verifying this change
This change is already covered by existing tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes)
The public API, i.e., is any changed class annotated with @Public(Evolving): ( no )
The serializer: ( no )
The runtime per-record code paths (performance sensitive): ( no )
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: ( no )
The S3 file system connector: ( no )

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (release notes). The following text was added to the tickets' release notes:

Known issues:

Due to the setup of the newly added Kafka end-to-end tests, they became incompatible with this change when executed in the IDE (unshaded classes from IntelliJ modules get used in the RemoteStreamEnvironment). The testing approach is due to be revisited in the next versions of Flink.
I had to modify an existing ArchUnit violation in order to get green CI because the rule correctly does not take into account if the caller of a @VisibleForTesting method is itself marked with the same annotation.  Also should it be always properly shaded?

Thanks for the review, @dmvk, and for spotting this:

I did a quick sanity check for all connector artifacts:
...There seems to be some weird ones, eg.:

These were pulled in from the connector's transitive dependencies and packaged because of the "double shading" in the SQL connector distribution. I added exclusions so that the flink-connector-base classes are only packaged once. CI is running, let's see if it breaks anything.

I'm also wondering whether we'd be able to add some test (bash based?) for the shaded artifacts, making sure this contract will hold with future changes

Would checking that there are no unshaded org/apache/flink/connector/base/* classes in the connectors would suffice? What do you think?

Would checking that there are no unshaded org/apache/flink/connector/base/* classes in the connectors would suffice? What do you think?

That plus checking that we only have a single shaded version per final artifact?
WDYT?

CI fails with a compile error.

I am looking into this. The CI was green before the recent rebase on master. Something changed in the tests setup for Kinesis.

@flinkbot run azure


[Feature][Metric]support spark job metric

seatunnel spark job metric

hi, please don't put Chinese comments in the code


Fix regression in 0.49RC1

Fixes #5470

Thanks for the patch. Should dc1c088 be present in the patchset ?

No, it should not.

@pearu would it be possible to rebase to remove the commit: https://github.com/numba/numba/commit/dc1c088654e9a4073e7a26b1113599077f92baa2

@pearu would it be possible to rebase to remove the commit: dc1c088

Done.

/AzurePipelines run

Thanks for the patch, it's queued for review.

Note for reviewers: there was some back and forth on #5470 - but it does appear like this PR does indeed fix that issue. Thank you @pearu !

Thanks, @stuartarchibald for the review. I have cleaned up the tests and updated the docs.
Using jit-decorated first-class functions in tuples has now a restriction that at least of the items must have a precise function type. So the support for the tuple of dispatcher instances is not completely disabled. For the full support, some further work is required on the numba type-inference algorithm.

Thanks for doing all the work on this @pearu, I branched off this in #5529 taking all the history you created and added in a couple of patches to address the remaining review comments. Will close this but the credit for fixing this is most definitely yours! Thanks again.

Thanks, @stuartarchibald ! Sorry for the delay in my part to address these issues.

@pearu no problem, and no delay at all, @sklam and I just had some external constraints applied on getting 0.49.0RC2 out so we decided to just move stuff as fast as we could!


Fix running the tests

Hi!
During working on one of my latests PR I noticed some strange behaviour that I know the tests should fail, but they pass. After a lot of digging I found out that not all tests are run!
It turned out that PHPUnit load all *Test classes and execute them, but if you load some of them on your own - PHPUnit won't know about them. And we are loading some *Test classes by ourselves in our tests...
λ phpunit
(...)
Tests: 2532, Assertions: 41425, Skipped: 5.

λ rm Symfony/CS/Tests/ProjectCodeTest.php

λ phpunit
(...)
Tests: 2698, Assertions: 41991, Skipped: 7.

I encapsulate the tricky test to run on it's own, separately from all other tests.
after my changes:
λ composer test
> phpunit
(...)
Tests: 2698, Assertions: 41991, Skipped: 7.
> phpunit Symfony/CS/Tests/Standalone/ProjectCodeTest.php
(...)
OK (252 tests, 252 assertions)

I do not like the solution showed by this PR, but I can't figure out any better :(

working, ready to merge

Better merge asap. ;)

:+1:  thanks @keradus


Jenkins plugins NOT installed as expected

Hi guys,
I run my play book with "geerlingguy.jenkins" role from Ansible galaxy, but found this issue: Jenkins will install and launch perfectly, but plugins can NOT be installed as expected.
See Ansible output and plugin list:

And I did nothing change to my local "geerlingguy.jenkins", just simply include it, see my major play site.yml:
DASH name: Install Jenkins and its plugins
hosts: jenkins_servers
remote_user: root

vars:
  jenkins_hostname: localhost
  jenkins_plugins:
    - git
    - sonar
    - ssh
    - gerrit-trigger
    - gearman-plugin
    - zmq-event-publisher
    - ansicolor
    - matrix-project
    - workflow-aggregator
    - extended-read-permission
    - ssh-slaves

roles:
  DASH geerlingguy.jenkins

Can you give more environment information? It seems like it's definitely installing plugins, if the status is changed for all of those. Maybe Jenkins just needs to be restarted?

Same approach at me and facing the same situation even Jenkins get restarted.

Not sure if this has anything to do with the OPs issue, but I can't install plugins either:
TASK [geerlingguy.jenkins : Install Jenkins plugins using password.] ********************************************************************
failed: [jenkins] (item=active-directory) => {"changed": false, "item": "active-directory", "msg": "The params option to jenkins_plugin was removed in Ansible 2.5since it circumvents Ansible's option handling"}

I'm using Ansible 2.5 and geerlingguy.jenkins 3.2.2

Operation system: Red Hat Enterprise Linux Server release 7.4 (Maipo)
Kernel: 3.10.0-693.5.2.el7.x86_64
Ansible version: <IP_ADDRESS>
Python version: 2.7.5
SE Linux: Disabled
@geerlingguy
Every time I re-run the playbook, output always show as "changed", looks like Ansible do execute the installation process , but do not effect in the end. Just like we type some content in a file, but always forget to save it, so we always see a empty file and re-type again and again.
Actually we did some tests among several VMs, it works on some VMs. But in most time, it's the case I put forward.

@pigulla Your issue should be with Ansible version know from the error messgae, looks like geerlingguy.jenkins is NOT compatible with Ansible 2.5

I have a same issue on Ubuntu 16.04 with Ansible 2.5
I run first, all items have been changed status.
I checked the installed plugins, then some plugin installed ( sometimes nothing)
When I run the playbook again, then it will fix the missing plugins.

Hi,
I am also experiencing the issue that I install with plugins and after the last Jenkins restart the plugins folder is empty (jenkins fails to properly start as it can't find the plugins). Any ideas?
Thanks, other than that this and many of your other roles work greatly!


improve error handling when parsing CHANGELOG

Fixes #160

@bwplotka @juliusv Does this look ok for fixing #160?

:+1: yep, looks good, thanks!


one consumer group subscribe multiple topic, some messages not consumed

Please describe the issue you observed:

I have a consumer group, it include 3 instances,  it subscribes 3 topics using CLUSTER mode, each topic have 16 queues.
I expect the consumer group consumes all the messages in the 3 topics.
When I check the  consumer of each topic, I find that some queues have not assigned to the consumers.
It seems that the consumer group should be unique in broker level.

Please tell us about your environment:
4.6.0 dleager mode cluster

Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):

The subscription relationship must be consistent among all consumers in the consumer group.

please check subscription in all topic exist in all broker

The subscription relationship must be consistent among all consumers in the consumer group.

Do you mean only support one consumer group subscribes one topic ?
Don't support one consumer group subscribes three topics at the same time ?

The first thing you should be aware of is that different Consumer Group can consume the same topic independently, and each of them will have their own consuming offsets. Of course, the consumers in the same consumer group can also consume multiple topics at the same time. Please make sure each Consumer within the same Group to subscribe to the same topics.

I got it.
Thanks


Fix #4061: Report a linking error on export of non-JS ident in a Script.

When emitting a Script (NoModule), we cannot export on the top-level under a name that is not a valid JavaScript identifier. Such exports must be emitted as vars or lets, which is only possible for valid JS identifiers.
Previously, attempts at such invalid exports would silently result in invalid .js code, producing a SyntaxError at run-time. In this commit, we preemptively report a linking error instead (as a thrown LinkingException).
It can be argued that we might want fallback behaviors for these cases, as discussed in #4061. However, this commit is a definitive improvement over the status quo, and leaves the door open for fallbacks in the future, if they prove desirable/necessary.

I wonder if this is the right spot to check this.
I realize there is precedent with imports.
It's just unclear to me which checks we perform where. E.g. export collisions, we check in the Analyzer.
My general concern is that we have no error collection infrastructure in the Emitter (or elsewhere, really). As such, we have to keep things together to report "all" errors.

Yes, I was also a bit uneasy about this. As you noticed, we had precedent for imports, so it seemed to be the best place given the status quo.
Rationalizing the status quo, it seems that we report in the Analyzer errors that are independent of the module kind (or other backend concerns), and in the Emitter for things that are module kind-specific. This might be a remnant from the time where we segregated much more which Config went to the frontend and to the backend.
It seems like we should probably report all expected linking errors in the Analyzer.

Updated to resolve the wrong commits.

It seems like we should probably report all expected linking errors in the Analyzer.

Yes, I feel so too. Module splitting will make the need for this even bigger.
So the options we have here are:

Accept this PR as-is, fix it later (I'll probably do so soon).
Do it now, rewrite this PR in the new system

Since this PR is quite infrastructure heavy, I'm inclined to go with option 2 (some of the infra changes will become unnecessary IIUC). OTOH, it is basically ready (I haven't reviewed the changes yet, but I really don't expect any problems).
WDYT?

Yes, option 2 is better.

Half of option 2 (fixing #4061, but not moving the existing check from the Emitter to the Analyzer) available in #4081.

I take it we can close this PR?

Yes, indeed.


[BUG-3581] [Code Style] HttpStatus & Headers should not be imported from org.apache.hc.core5.http - Header Refactor Only

Description
Accounts for refactor of Header classes from hc.core5.http to just http by adding checkstyle test, and manually refactoring all current occurrences of the illegal import. Additionally updated spotlessApply to make the refactor automatic on future cases of illegal import.

Category (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)

Bug fix/refactor

Why these changes are required?

Refer to #3581

What is the old behavior before changes and new behavior after changes?

Ideally nothing.
Issues Resolved

#3581

Is this a backport? If so, please add backport PR # and/or commits #
No.
Testing
Tests have been modified and should work before merging.
Check List

[x] New functionality includes testing
[x] New functionality has been documented
[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@peternied @cwperks @scrawfor99 I refactored Header for this PR. In trying to fix the compiler issues that arose, I tried to change the import of BasicHeader from import org.apache.hc.core5.http.message.BasicHeader; to import org.apache.http.message.BasicHeader;. Let me know if this is a bad change to make. For four files the errors that arose were not because of this reason: OpensearchClientProvider.java, TestRestClient.java, MockSamlldpServer.java, RestHelper.java. It looks like for these files the error is trying to pass the new Header import into a function that only takes in the old Header import. I cannot change these functions because they are outside the security repo. Any other ideas on how to fix these?

@prabhask5, thanks for your work on the issue [1]. In open-source projects, contributors are expected to not just find issues but also seek solutions, deepening their understanding of the codebase. I suggest you further explore how your changes affect the existing code. If it's too complex, maybe try another project aspect. Remember, as maintainers, we guide and review, but you're responsible for developing and testing solutions.
We're here for feedback and help with any specific questions!

[1] https://github.com/opensearch-project/security/issues/3581

@prabhask5, thanks for your work on the issue [1]. In open-source projects, contributors are expected to not just find issues but also seek solutions, deepening their understanding of the codebase. I suggest you further explore how your changes affect the existing code. If it's too complex, maybe try another project aspect. Remember, as maintainers, we guide and review, but you're responsible for developing and testing solutions.
We're here for feedback and help with any specific questions!

[1] [BUG] [Code Style] HttpStatus & Headers should not be imported from org.apache.hc.core5.http #3581

@peternied Thanks for the comment, I’ll continue to do so! Just to check though, is the basic header change a valid change in this context or should I figure this out without making any other import changes? Tysm!