YARN-11200 numa support in branch-2.10

Description of PR
YARN-11200
How was this patch tested?
tested patch in the EMR cluster (5.x series)
For code changes:

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

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
15m 38s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
xmllint
0m  1s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ branch-2.10 Compile Tests _

+0 :ok:
mvndep
3m 29s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
13m 14s

branch-2.10 passed

+1 :green_heart:
compile
7m 42s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
compile
6m 38s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
checkstyle
1m 40s

branch-2.10 passed

+1 :green_heart:
mvnsite
3m 45s

branch-2.10 passed

+1 :green_heart:
javadoc
3m 35s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
3m 17s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
spotbugs
6m  7s

branch-2.10 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 28s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 53s

the patch passed

-1 :x:
compile
1m 34s
/patch-compile-hadoop-yarn-project_hadoop-yarn-jdkAzulSystems,Inc.-1.7.0_262-b10.txt
hadoop-yarn in the patch failed with JDK Azul Systems, Inc.-1.7.0_262-b10.

-1 :x:
javac
1m 34s
/patch-compile-hadoop-yarn-project_hadoop-yarn-jdkAzulSystems,Inc.-1.7.0_262-b10.txt
hadoop-yarn in the patch failed with JDK Azul Systems, Inc.-1.7.0_262-b10.

+1 :green_heart:
compile
6m  6s

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

+1 :green_heart:
javac
6m  6s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
1m 30s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn.txt
hadoop-yarn-project/hadoop-yarn: The patch generated 6 new + 187 unchanged - 0 fixed = 193 total (was 187)

+1 :green_heart:
mvnsite
3m 18s

the patch passed

-1 :x:
javadoc
0m 59s
/results-javadoc-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager-jdkAzulSystems,Inc.-1.7.0_262-b10.txt
hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager-jdkAzulSystems,Inc.-1.7.0_262-b10 with JDK Azul Systems, Inc.-1.7.0_262-b10 generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1 :green_heart:
javadoc
2m 52s

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

+1 :green_heart:
spotbugs
5m 53s

the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m  8s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
3m 48s

hadoop-yarn-common in the patch passed.

-1 :x:
unit
16m 12s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt
hadoop-yarn-server-nodemanager in the patch passed.

+1 :green_heart:
asflicense
1m  8s

The patch does not generate ASF License warnings.

121m 21s

Reason
Tests

Failed junit tests
hadoop.yarn.server.nodemanager.containermanager.linux.resources.TestNumaResourceHandlerImpl

hadoop.yarn.server.nodemanager.containermanager.linux.resources.TestNumaResourceAllocator

Subsystem
Report/Notes

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

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

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

uname
Linux c9030cf8bcc7 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-2.10 / addad562c9379ab3beefb0614d68920ee32b6e71

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

Multi-JDK versions
/usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_262-b10 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

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

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

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

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

versions
git=2.17.1 maven=3.6.0 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
8m 34s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ branch-2.10 Compile Tests _

+0 :ok:
mvndep
3m 26s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
13m 15s

branch-2.10 passed

+1 :green_heart:
compile
7m 46s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
compile
6m 36s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
checkstyle
1m 40s

branch-2.10 passed

+1 :green_heart:
mvnsite
3m 43s

branch-2.10 passed

+1 :green_heart:
javadoc
3m 36s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
3m 16s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
spotbugs
6m  4s

branch-2.10 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 27s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 52s

the patch passed

-1 :x:
compile
2m  6s
/patch-compile-hadoop-yarn-project_hadoop-yarn-jdkAzulSystems,Inc.-1.7.0_262-b10.txt
hadoop-yarn in the patch failed with JDK Azul Systems, Inc.-1.7.0_262-b10.

-1 :x:
javac
2m  6s
/patch-compile-hadoop-yarn-project_hadoop-yarn-jdkAzulSystems,Inc.-1.7.0_262-b10.txt
hadoop-yarn in the patch failed with JDK Azul Systems, Inc.-1.7.0_262-b10.

+1 :green_heart:
compile
6m  4s

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

+1 :green_heart:
javac
6m  4s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
1m 29s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn.txt
hadoop-yarn-project/hadoop-yarn: The patch generated 1 new + 186 unchanged - 0 fixed = 187 total (was 186)

+1 :green_heart:
mvnsite
3m 17s

the patch passed

+1 :green_heart:
javadoc
3m  8s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
2m 52s

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

+1 :green_heart:
spotbugs
5m 54s

the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 10s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
3m 49s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
16m  4s

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

+1 :green_heart:
asflicense
1m  7s

The patch does not generate ASF License warnings.

114m 38s

Subsystem
Report/Notes

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

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

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

uname
Linux 24608df9e18e 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-2.10 /<PHONE_NUMBER>7763b64e38b851ab8140c2e12bd603

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

Multi-JDK versions
/usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_262-b10 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

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

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

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

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

versions
git=2.17.1 maven=3.6.0 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 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ branch-2.10 Compile Tests _

+0 :ok:
mvndep
3m 53s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
13m 20s

branch-2.10 passed

+1 :green_heart:
compile
7m 38s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
compile
6m 40s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
checkstyle
1m 40s

branch-2.10 passed

+1 :green_heart:
mvnsite
3m 41s

branch-2.10 passed

+1 :green_heart:
javadoc
3m 37s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
3m 15s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
spotbugs
6m  8s

branch-2.10 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 25s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 53s

the patch passed

+1 :green_heart:
compile
6m 44s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javac
6m 44s

the patch passed

+1 :green_heart:
compile
6m 34s

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

+1 :green_heart:
javac
6m 34s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
1m 29s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn.txt
hadoop-yarn-project/hadoop-yarn: The patch generated 1 new + 186 unchanged - 0 fixed = 187 total (was 186)

+1 :green_heart:
mvnsite
3m 17s

the patch passed

+1 :green_heart:
javadoc
3m 11s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
2m 52s

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

+1 :green_heart:
spotbugs
5m 52s

the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 11s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
3m 49s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
16m  3s

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

+1 :green_heart:
asflicense
1m  6s

The patch does not generate ASF License warnings.

111m 54s

Subsystem
Report/Notes

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

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

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

uname
Linux e32ed62f7668 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-2.10 / 9da62bb85edc904dbcfbce70915a0971f4505223

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

Multi-JDK versions
/usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_262-b10 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

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

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

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

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

versions
git=2.17.1 maven=3.6.0 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 57s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
xmllint
0m  1s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ branch-2.10 Compile Tests _

+0 :ok:
mvndep
3m 28s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
13m 22s

branch-2.10 passed

+1 :green_heart:
compile
7m 41s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
compile
6m 37s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
checkstyle
1m 40s

branch-2.10 passed

+1 :green_heart:
mvnsite
3m 46s

branch-2.10 passed

+1 :green_heart:
javadoc
3m 36s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
3m 16s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
spotbugs
6m  7s

branch-2.10 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 29s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 54s

the patch passed

+1 :green_heart:
compile
6m 51s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javac
6m 51s

the patch passed

+1 :green_heart:
compile
6m 40s

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

+1 :green_heart:
javac
6m 40s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
1m 29s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn.txt
hadoop-yarn-project/hadoop-yarn: The patch generated 1 new + 187 unchanged - 0 fixed = 188 total (was 187)

+1 :green_heart:
mvnsite
3m 18s

the patch passed

+1 :green_heart:
javadoc
3m  7s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
2m 47s

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

+1 :green_heart:
spotbugs
5m 52s

the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 11s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
3m 48s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
16m 13s

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

+1 :green_heart:
asflicense
1m  3s

The patch does not generate ASF License warnings.

112m 31s

Subsystem
Report/Notes

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

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

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

uname
Linux a2533aa44817 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-2.10 / 1dfe2d03300108f851b33852570bbd82b1f1964c

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

Multi-JDK versions
/usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_262-b10 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

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

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

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

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

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 56s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
xmllint
0m  1s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ branch-2.10 Compile Tests _

+0 :ok:
mvndep
3m 31s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
13m 29s

branch-2.10 passed

+1 :green_heart:
compile
7m 32s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
compile
6m 41s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
checkstyle
1m 39s

branch-2.10 passed

+1 :green_heart:
mvnsite
3m 38s

branch-2.10 passed

+1 :green_heart:
javadoc
3m 37s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
3m 18s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
spotbugs
6m  7s

branch-2.10 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 26s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 53s

the patch passed

+1 :green_heart:
compile
6m 48s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javac
6m 48s

the patch passed

+1 :green_heart:
compile
6m 37s

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

+1 :green_heart:
javac
6m 37s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
1m 28s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn.txt
hadoop-yarn-project/hadoop-yarn: The patch generated 1 new + 187 unchanged - 0 fixed = 188 total (was 187)

+1 :green_heart:
mvnsite
3m 17s

the patch passed

+1 :green_heart:
javadoc
3m 11s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
2m 54s

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

+1 :green_heart:
spotbugs
5m 50s

the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 11s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
3m 49s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
16m 14s

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

+1 :green_heart:
asflicense
1m  8s

The patch does not generate ASF License warnings.

112m 10s

Subsystem
Report/Notes

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

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

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

uname
Linux 925eb84a0d38 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-2.10 / 9d522a48e8242b09c0ae354987e384554d29f755

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

Multi-JDK versions
/usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_262-b10 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

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

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

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

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

versions
git=2.17.1 maven=3.6.0 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
8m 34s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
xmllint
0m  1s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ branch-2.10 Compile Tests _

+0 :ok:
mvndep
3m 30s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
13m 23s

branch-2.10 passed

+1 :green_heart:
compile
7m 35s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
compile
6m 40s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
checkstyle
1m 39s

branch-2.10 passed

+1 :green_heart:
mvnsite
3m 43s

branch-2.10 passed

+1 :green_heart:
javadoc
3m 38s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
3m 17s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
spotbugs
6m  5s

branch-2.10 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 29s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 52s

the patch passed

+1 :green_heart:
compile
6m 47s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javac
6m 47s

the patch passed

+1 :green_heart:
compile
6m 35s

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

+1 :green_heart:
javac
6m 35s

the patch passed

+1 :green_heart:
blanks
0m  1s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 29s

the patch passed

+1 :green_heart:
mvnsite
3m 17s

the patch passed

+1 :green_heart:
javadoc
3m 10s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
2m 54s

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

+1 :green_heart:
spotbugs
5m 52s

the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 11s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
3m 50s

hadoop-yarn-common in the patch passed.

-1 :x:
unit
16m  6s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt
hadoop-yarn-server-nodemanager in the patch passed.

+1 :green_heart:
asflicense
1m  7s

The patch does not generate ASF License warnings.

120m 11s

Reason
Tests

Failed junit tests
hadoop.yarn.server.nodemanager.amrmproxy.TestFederationInterceptor

Subsystem
Report/Notes

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

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

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

uname
Linux 90c6fa5a29fc 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-2.10 / c12f934b31c0f181aa425f12730455065b0a012d

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

Multi-JDK versions
/usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_262-b10 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

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

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4587/8/console

versions
git=2.17.1 maven=3.6.0 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
1m  9s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
xmllint
0m  1s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ branch-2.10 Compile Tests _

+0 :ok:
mvndep
3m 27s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
14m  1s

branch-2.10 passed

+1 :green_heart:
compile
7m 41s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
compile
6m 55s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
checkstyle
1m 34s

branch-2.10 passed

+1 :green_heart:
mvnsite
3m 27s

branch-2.10 passed

+1 :green_heart:
javadoc
3m 20s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
3m  8s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
spotbugs
6m 10s

branch-2.10 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 25s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 52s

the patch passed

+1 :green_heart:
compile
6m 48s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javac
6m 48s

the patch passed

+1 :green_heart:
compile
7m  0s

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

+1 :green_heart:
javac
7m  0s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 31s

the patch passed

+1 :green_heart:
mvnsite
3m 20s

the patch passed

+1 :green_heart:
javadoc
3m  8s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
2m 55s

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

+1 :green_heart:
spotbugs
6m 15s

the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 12s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
3m 50s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
16m  6s

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

+1 :green_heart:
asflicense
1m  7s

The patch does not generate ASF License warnings.

113m 22s

Subsystem
Report/Notes

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

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

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

uname
Linux 65b77e696592 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-2.10 / c51ce6d41e660b9dfda0a31ff470accaa27b115b

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

Multi-JDK versions
/usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_262-b10 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

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

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

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

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

versions
git=2.17.1 maven=3.6.0 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 44s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ branch-2.10 Compile Tests _

+0 :ok:
mvndep
3m 30s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
14m  4s

branch-2.10 passed

+1 :green_heart:
compile
7m 41s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
compile
7m  0s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
checkstyle
1m 40s

branch-2.10 passed

+1 :green_heart:
mvnsite
3m 32s

branch-2.10 passed

+1 :green_heart:
javadoc
3m 27s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
3m  7s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
spotbugs
6m 16s

branch-2.10 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 26s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 56s

the patch passed

+1 :green_heart:
compile
6m 55s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javac
6m 55s

the patch passed

+1 :green_heart:
compile
6m 59s

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

+1 :green_heart:
javac
6m 59s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 33s

the patch passed

+1 :green_heart:
mvnsite
3m 20s

the patch passed

+1 :green_heart:
javadoc
3m  6s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
2m 54s

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

+1 :green_heart:
spotbugs
6m 16s

the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 12s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
3m 51s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
16m  6s

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

+1 :green_heart:
asflicense
1m  8s

The patch does not generate ASF License warnings.

115m 16s

Subsystem
Report/Notes

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

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

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

uname
Linux e35044e8cdac 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-2.10 / c51ce6d41e660b9dfda0a31ff470accaa27b115b

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

Multi-JDK versions
/usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_262-b10 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

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

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4587/9/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

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

This message was automatically generated.

@PrabhuJoseph please review !
checkstyle warnings are fixed

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 54s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ branch-2.10 Compile Tests _

+0 :ok:
mvndep
3m 28s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
13m 20s

branch-2.10 passed

+1 :green_heart:
compile
7m 31s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
compile
6m 38s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
checkstyle
1m 39s

branch-2.10 passed

+1 :green_heart:
mvnsite
3m 44s

branch-2.10 passed

+1 :green_heart:
javadoc
3m 36s

branch-2.10 passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
3m 17s

branch-2.10 passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

+1 :green_heart:
spotbugs
6m  8s

branch-2.10 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 26s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 52s

the patch passed

+1 :green_heart:
compile
6m 49s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javac
6m 49s

the patch passed

+1 :green_heart:
compile
7m 52s

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

+1 :green_heart:
javac
7m 52s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 26s

the patch passed

+1 :green_heart:
mvnsite
3m  4s

the patch passed

+1 :green_heart:
javadoc
3m  5s

the patch passed with JDK Azul Systems, Inc.-1.7.0_262-b10

+1 :green_heart:
javadoc
2m 52s

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

+1 :green_heart:
spotbugs
6m 12s

the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 12s

hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
3m 50s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
unit
16m 10s

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

+1 :green_heart:
asflicense
1m  6s

The patch does not generate ASF License warnings.

113m 16s

Subsystem
Report/Notes

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

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

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

uname
Linux 1ee49f02fe53 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-2.10 / 7558b5457e0f01cb8851e82574864db28d7403d0

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

Multi-JDK versions
/usr/lib/jvm/zulu-7-amd64:Azul Systems, Inc.-1.7.0_262-b10 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~18.04-b07

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

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4587/11/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

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

This message was automatically generated.

Thanks @Samrat002  for the backport.


removed prettier/@typescript-eslint in package.json

Please verify the following:

[x] yarn ci:test jest tests pass with new tests, if relevant
[x] README.md has been updated with your changes, if relevant

Describe your PR
prettier/@typescript-eslint was removed in eslint-config-prettier v8.0.0
see https://github.com/prettier/eslint-config-prettier/issues/173
also see more - https://github.com/prettier/eslint-config-prettier/blob/main/CHANGELOG.md#version-800-2021-02-21

(This will go out in the next Ignite release.)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


don't insert style when tag is not mount

riot.tag('tag-pc', 'some html', 'some style', function(){});
riot.tag('tag-mobile', 'some html', 'some style', function(){});
riot.mount('#view', isMobile ? 'tag-mobile' : 'tag-pc', {});

tag-mobile is not mount, but it's scope css is insert.

Riot.js injects CSS immediately after calling riot.tag().
https://github.com/muut/riotjs/blob/v2.0.11/lib/tag/vdom.js#L30

but, tag is something like define,  not exec,  it should not insert css immediately

Yeah, I understand what you feel @atian25 . Actually at the first I tried to implement this on mount function. But I didn't, because, if not, we should care about these things.

Riot.js injects CSS dynamically and should check that it's first time of mount or not
We can't control the order of CSS injection

BTW I'm struggling on Scoped CSS #430. If it becomes 'default', we'll not have to care the order of CSS anymore.

@atian25 you are right, but we need to wait for the plugin system (#416) to make that possible.

got it~

closed with this https://github.com/muut/riotjs/pull/430


go build on master branch is broken

I tried to build on master branch, go build fails -
go build -v
github.com/xenolf/lego/providers/dns/dnsimple
# github.com/xenolf/lego/providers/dns/dnsimple
providers/dns/dnsimple/dnsimple.go:179:54: cannot use whoamiResponse.Data.Account.ID (type int) as type int64 in argument to strconv.FormatInt

#546 Fixes this issue.

Also build fails for tags/v0.4.1 using the Dockerfile -
docker build -t lego .

throws this error -
# github.com/miekg/dns
go/src/github.com/miekg/dns/msg_helpers.go:144: base32.HexEncoding.WithPadding undefined (type *base32.Encoding has no field or method WithPadding)
go/src/github.com/miekg/dns/msg_helpers.go:144: undefined: base32.NoPadding

This is because miekg/dns package requires go version > 1.9 to build. Refer https://github.com/miekg/dns/issues/686
Once, I updated go version to 1.9.2 in Dockerfile. It still fails with the following error -
github.com/Azure/azure-sdk-for-go (download)
package github.com/Azure/azure-sdk-for-go/arm/dns: cannot find package "github.com/Azure/azure-sdk-for-go/arm/dns" in any of:
	/usr/local/go/src/github.com/Azure/azure-sdk-for-go/arm/dns (from $GOROOT)
	/go/src/github.com/Azure/azure-sdk-for-go/arm/dns (from $GOPATH)

This is because the azure-sdk-for-go repo has been updated and the arm/dns has been removed. Need to vendor this in this repo.

You might try "go get -u -v ./..." on master.  I can't reproduce this this using 1.9.2 or 1.9.6.  You will see the first error on 1.8.x, though, and they just removed 1.8 testing from TravisCI as it's no longer supported.

I'll close this issue, because it's resolve by #550.


v2 stable: Revert @rc tag for Getting Started docs

Link to the Page
https://www.skeleton.dev/docs/get-started
Describe the Issue (screenshots encouraged!)
We'll need to revert from the @rc -> @latest for the CLI install, then prune the tags for the Skeleton core package/plugin in the manual install instructions before this launches for v2 stable.

https://github.com/skeletonlabs/skeleton/pull/1875
https://github.com/skeletonlabs/skeleton/pull/1878

Note: go ahead and use this commit to include a new "v2 is now live banner" on the homepage


[Navigation Animation]  Pop transitions performed are not what was expected

Description
https://user-images.githubusercontent.com/54979514/169891310-c3d33164-1b53-4d64-b824-740e2b8b8315.mp4
The pop transitions performed are not what was expected. Screen B (Popular) should only slide to the right and not fade out. However, Screen A (Discover) should fade in.
Here the code
AnimatedNavHost(
        modifier = Modifier
            .fillMaxSize()
            .background(MaterialTheme.colors.background),
        navController = navController,
        startDestination = startDestination.route,
        enterTransition = { slideIntoContainer(Left, tween(durationMillis)) },
        exitTransition = { fadeOut(tween(durationMillis)) },
        popEnterTransition = { fadeIn(tween(durationMillis)) },
        popExitTransition = { slideOutOfContainer(Right, tween(durationMillis)) },
    )

Compose:  1.2.0-beta02
Accompanist: 0.24.9-beta

Any update ?

Reopened for @jbw0033 to have a look at


Convolution2d seems to be not correct.

Actual behavior
If i provide the example sobel_scharr.cpp with following image:
I get (for sobel filter)

Grad X
Grad Y

Which is not correct in my opinion.
Expected  behavior
I have written a unit test which explains what I would expect from a 2 d convolution with sobel filter for the x direction.
void test_convolve_2d_with_sobel_x_filter()
{
  gil::uint8_t img[] =
      {
          0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
          0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
          0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
          0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
          0, 0, 255, 255, 255, 255, 0, 0, 0, 0,
          0, 0, 255, 255, 255, 255, 0, 0, 0, 0,
          0, 0, 255, 255, 255, 255, 0, 0, 0, 0,
          0, 0, 255, 255, 255, 255, 0, 0, 0, 0,
          0, 0, 255, 255, 255, 255, 0, 0, 0, 0,
          0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
          0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
          0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
          0, 0, 0, 0, 0, 0, 0, 0, 0, 0
      };

  gil::int16_t const exp_output[] =
      {
          0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
          0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
          0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
          0, 255, 255, 0, 0, -255, -255, 0, 0, 0,
          0, 765, 765, 0, 0, -765, -765, 0, 0, 0,
          0, 1020, 1020, 0, 0, -1020, -1020, 0, 0, 0,
          0, 1020, 1020, 0, 0, -1020, -1020, 0, 0, 0,
          0, 1020, 1020, 0, 0, -1020, -1020, 0, 0, 0,
          0, 765, 765, 0, 0, -765, -765, 0, 0, 0,
          0, 255, 255, 0, 0, -255, -255, 0, 0, 0,
          0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
          0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
          0, 0, 0, 0, 0, 0, 0, 0, 0, 0
      };

  gil::gray16_image_t img_gray_out(10, 13);
  auto src_view =
      gil::interleaved_view(10, 13, reinterpret_cast<const gil::gray8_pixel_t*>(img), 10);
  auto exp_out_view =
      gil::interleaved_view(10, 13, reinterpret_cast<const gil::gray16_pixel_t*>(exp_output), 10);
  gil::detail::convolve_2d(src_view, gil::generate_dx_sobel(1), view(img_gray_out));
  BOOST_TEST(gil::equal_pixels(exp_out_view, view(img_gray_out)));
}

C++ Minimal Working Example
See unit test in Expected  behavior.
Environment
Should be independent of environment. I didn't have any crash or something.
PS: I also don't know how to properly debug code in GIL properly. How I can see the content of an image in the debugger?

I think fixed the issue already. Will crate PR.


This line create problem when nothing is passed calling the application command!

https://github.com/RSuter/NConsole/blob/d7b18d19ec71a61ac98eb9e26711bf3325b01554/src/NConsole/CommandLineProcessor.cs#L215

Yeah it's a bit annoying. Is this package still maintained?

Is this package still maintained?

Yes, it is still used and maintained. Can you create a PR?

Did so. Please have look


Incremented production/RELEASE for 1.19-3

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold
wait dev RELEASE is merged

/unhold


[BUG] Link-time issues when Cython output compiled as C++

Overview
I recently created the following BPO:

https://bugs.python.org/issue43816

as well as associated PR:

https://github.com/python/cpython/pull/25365

to fix (what I felt was) a bug in (at least) Python 3.8/Python 3.9.
However, I received push-back from at least one commenter on the Python mailing list that the issue was discussing was an "API misuse" of Python.h (maybe that's true).
Anyway, since this came about because of Cython, I thought it was worth discussing it here.
Actual issue
If you Cythonate something like:
float(1)

then you end-up with some code that looks like this in your output:
static CYTHON_UNUSED double __Pyx__PyBytes_AsDouble(PyObject *obj, const char* start, Py_ssize_t length) {
    double value;
    Py_ssize_t i, digits;
    const char *last = start + length;
    char *end;
    while (Py_ISSPACE(*start))
        start++;
...

And where Py_ISSPACE has an expansion like:
#define Py_ISSPACE(c)  (_Py_ctype_table[Py_CHARMASK(c)] & PY_CTF_SPACE)

(in pyctype.h)
and where the variable _Py_ctype_table looks like this:
PyAPI_DATA(const unsigned int) _Py_ctype_table[256];

Problematically, the inclusion of (cpython) pyctype.h in Python.h does not guard _Py_ctype_table against the case of C++ compilation.
This then leads to the following issue:

You use pre-compiled version of Python38 (e.g., on Windows), which has been compiled with a C compiler
This means that all symbols are not name-managled
You Cythonate some code and pull in a C++-only header
You then compile your Cythonated code as C++ (e.g., with /TP if you're using Visual Studio)
Finally, you try to link your Cythonated object code with Python38.lib

This then falls apart because Python38.lib has a un-name-mangled version of _Py_ctype_table, while your Cythonated code has C++-name-managled version of _Py_ctype_table, which means the linker cannot resolve the symbol, giving a link time error:
cl /Fe:test.exe /TP /I include cython_output.c test.c /link libs/python39.lib
Microsoft (R) C/C++ Optimizing Compiler Version 19.28.29336 for x64
Copyright (C) Microsoft Corporation.  All rights reserved.

cython_output.c
test.c
Generating Code...
Microsoft (R) Incremental Linker Version 14.28.29336.0
Copyright (C) Microsoft Corporation.  All rights reserved.

/out:test.exe
libs/python39.lib
cython_output.obj
test.obj
   Creating library test.lib and object test.exp
cython_output.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) unsigned int const * const _Py_ctype_table" (__imp_?_Py_ctype_table@@3QBIB) referenced in function "double __cdecl __Pyx__PyBytes_AsDouble(struct _object * __ptr64,char const * __ptr64,__int64)" (?__Pyx__PyBytes_AsDouble@@YANPEAU_object@@PEBD_J@Z)
test.exe : fatal error LNK1120: 1 unresolved externals

Resolution
Without changing the use of Py_ISSPACE within Cython, I feel that the only solution is to change the generated C code to look like this:
#ifdef __cplusplus
extern "C" {
#endif
#include <Python.h>
#ifdef __cplusplus
}
#endif

Personally, given that other files downstream of Python.h do have extern "C", I felt that this really is a Python bug rather than a "user" bug.
However, I'm sharing this in here in case my feelings are off-base and, indeed, this is a Cython bug.
If this is considered a Cython bug, I'm more than happy to make a PR with the above change.

This does look to turn up in our Appveyor CI logs:
[00:05:13]    Creating library C:\projects\cython\TEST_TMP\1\memoryview\cpp\numpy_memoryview_readonly\numpy_memoryview_readonly.cp38-win_amd64.lib and object C:\projects\cython\TEST_TMP\1\memoryview\cpp\numpy_memoryview_readonly\numpy_memoryview_readonly.cp38-win_amd64.exp
[00:05:13] numpy_memoryview_readonly.obj : error LNK2001: unresolved external symbol "__declspec(dllimport) unsigned int const * const _Py_ctype_table" (__imp_?_Py_ctype_table@@3QBIB)
[00:05:13] C:\projects\cython\TEST_TMP\1\memoryview\cpp\numpy_memoryview_readonly\numpy_memoryview_readonly.cp38-win_amd64.pyd : fatal error LNK1120: 1 unresolved externals

It's only an issue on Windows I think - presumably GCC doesn't mangle this kind of symbol.
I think whether it's ultimately a Python bug or not, it should be fixed in Cython since there are enough Python versions with this unguarded code in the wild.

Maybe we should use Py_UNICODE_ISSPACE universally rather than just as a workaround?
https://github.com/cython/cython/blob/cd6e29d0251b21d6b1b45f3de8eb452bcfe2cf68/Cython/Utility/ModuleSetupCode.c#L787-L789
That has the advantage that it's both documented and in the correct C++ guards

I think whether it's ultimately a Python bug or not, it should be fixed in Cython since there are enough Python versions with this unguarded code in the wild.

Okay, so would you like the #ifdef __cplusplus PR?

That has the advantage that it's both documented and in the correct C++ guards

Would you like me to take a look at doing this?
Plus, yes, it does have the correct guards.

That has the advantage that it's both documented and in the correct C++ guards

Would you like me to take a look at doing this?

To me the Py_UNICODE_ISSPACE fix feels like a more proportionate change, so a PR doing that would be welcome. It's always possible that I'm wrong about this though...
It looks like this is already tested on appveyor (https://ci.appveyor.com/project/cython/cython) so I don't think there's any need to add specific tests.

Or possibly don't do anything until a decision has been made on the Python bug...

Or possibly don't do anything until a decision has been made on the Python bug...

Okay, so given my PR got a positive review, it seems this is likely to go in ...
However, we still have:

To me the Py_UNICODE_ISSPACE fix feels like a more proportionate change

I can take a look at this

I also searched for other occurrences of the Py_IS… macros, but it seems that all we're doing is testing for space characters.
The only difference that I can see is that Py_UNICODE_ISSPACE() treats NBSP (0xA0) as space whereas Py_ISSPACE() does not since it only looks at US-ASCII characters. This would mean that parsing floats surrounded by non-breaking spaces from a byte string would work in Cython but not in Python. Seems rather nice to have, but it's not how Python works here.
Given that we are talking about either 0x20 or 0x9 … 0xd as positive matches here, and the number of spaces around a value should be very low on average, I guess that an inline function to test that range should be fast enough. See 7ce24bc7381c83972e5b6d24bbb8e6ab610541fa


Non-null fragment value returned as nullable when using inline fragments

Using the following query, the fragment's value ...fragment().characterDetails() is being returned as nullable.
query getCharacterDetails {
    ...CharacterDetails
}

fragment CharacterDetails on Character {
    id
    name
    ... on Droid {
        droidType
    }
}

interface Character
type Droid implements Character

This only happens when the inline fragment ... on Droid is used in the CharacterDetails fragment. Removing this returns a non-null value, as expected.
On our iOS codebase, Apollo is not generating the fragment result as nullable (thus, adhering to the schema), however on Android, Apollo is returning a nullable value for the above scenario.
What could be the cause of this, am I missing something or could it be an Apollo client bug?

I guess this is an issue with the way how we generate the code. But I need more info.
Not sure that provided sample query is valid. Could you please attach generate IR.json file for this query (can be located at generated source folder /build/generated/source/apollo/generatedIR)

Here's the revised query that fully replicates this issue, along with the generated IR.
query GetDroids {
    droids {
       ...DroidFull
    }
}

fragment DroidFull on Droid {
    id
    name
    description
    image
    ... on ProtocolDroid {
        languagesSpoken
    }
    ... on BattleDroid {
        battlesWon
    }
}

# Generated IR

{
    "operations": [
        {
            "filePath": "../GetDroids.graphql",
            "operationName": "GetDroids",
            "operationType": "query",
            "rootType": "Query",
            "variables": [],
            "source": "query GetDroids {\n  droids {\n    __typename\n    ...DroidFull\n  }\n}",
            "fields": [
                {
                    "responseName": "droids",
                    "fieldName": "droids",
                    "type": "[Droid!]",
                    "isConditional": false,
                    "isDeprecated": false,
                    "deprecationReason": null,
                    "fields": [
                        {
                            "responseName": "__typename",
                            "fieldName": "__typename",
                            "type": "String!",
                            "isConditional": false
                        }
                    ],
                    "fragmentSpreads": [
                        "DroidFull"
                    ],
                    "inlineFragments": []
                }
            ],
            "fragmentSpreads": [],
            "inlineFragments": [],
            "fragmentsReferenced": [
                "DroidFull"
            ],
            "sourceWithFragments": "query GetDroids {\n  droids {\n    __typename\n    ...DroidFull\n  }\n}\nfragment DroidFull on Droid {\n  __typename\n  id\n  name\n  description\n  image\n  ... on ProtocolDroid {\n    languagesSpoken\n  }\n  ... on BattleDroid {\n    battlesWon\n  }\n}",
            "operationId": "80231ff654d27a276e62ed54b72c2d4e463d2b6222cd92b152f6718701b50bb9"
        }
    ],
    "fragments": [
        {
            "typeCondition": "Droid",
            "possibleTypes": [
                "ProtocolDroid",
                "BattleDroid"
            ],
            "fragmentName": "DroidFull",
            "filePath": "../fragments.graphql",
            "source": "fragment DroidFull on Droid {\n  __typename\n  id\n  name\n  description\n  image\n  ... on ProtocolDroid {\n    languagesSpoken\n  }\n  ... on BattleDroid {\n    battlesWon\n  }\n}",
            "fields": [
                {
                    "responseName": "__typename",
                    "fieldName": "__typename",
                    "type": "String!",
                    "isConditional": false
                },
                {
                    "responseName": "id",
                    "fieldName": "id",
                    "type": "ID!",
                    "isConditional": false,
                    "isDeprecated": false,
                    "deprecationReason": null
                },
                {
                    "responseName": "name",
                    "fieldName": "name",
                    "type": "String!",
                    "isConditional": false,
                    "isDeprecated": false,
                    "deprecationReason": null
                },
                {
                    "responseName": "description",
                    "fieldName": "description",
                    "type": "String!",
                    "isConditional": false,
                    "isDeprecated": false,
                    "deprecationReason": null
                },
                {
                    "responseName": "image",
                    "fieldName": "image",
                    "type": "URL!",
                    "isConditional": false,
                    "isDeprecated": false,
                    "deprecationReason": null
                }
            ],
            "fragmentSpreads": [],
            "inlineFragments": [
                {
                    "typeCondition": "ProtocolDroid",
                    "possibleTypes": [
                        "ProtocolDroid"
                    ],
                    "fields": [
                        {
                            "responseName": "__typename",
                            "fieldName": "__typename",
                            "type": "String!",
                            "isConditional": false
                        },
                        {
                            "responseName": "id",
                            "fieldName": "id",
                            "type": "ID!",
                            "isConditional": false,
                            "isDeprecated": false,
                            "deprecationReason": null
                        },
                        {
                            "responseName": "name",
                            "fieldName": "name",
                            "type": "String!",
                            "isConditional": false,
                            "isDeprecated": false,
                            "deprecationReason": null
                        },
                        {
                            "responseName": "description",
                            "fieldName": "description",
                            "type": "String!",
                            "isConditional": false,
                            "isDeprecated": false,
                            "deprecationReason": null
                        },
                        {
                            "responseName": "image",
                            "fieldName": "image",
                            "type": "URL!",
                            "isConditional": false,
                            "isDeprecated": false,
                            "deprecationReason": null
                        },
                        {
                            "responseName": "languagesSpoken",
                            "fieldName": "languagesSpoken",
                            "type": "Int!",
                            "isConditional": false,
                            "isDeprecated": false,
                            "deprecationReason": null
                        }
                    ],
                    "fragmentSpreads": []
                },
                {
                    "typeCondition": "BattleDroid",
                    "possibleTypes": [
                        "BattleDroid"
                    ],
                    "fields": [
                        {
                            "responseName": "__typename",
                            "fieldName": "__typename",
                            "type": "String!",
                            "isConditional": false
                        },
                        {
                            "responseName": "id",
                            "fieldName": "id",
                            "type": "ID!",
                            "isConditional": false,
                            "isDeprecated": false,
                            "deprecationReason": null
                        },
                        {
                            "responseName": "name",
                            "fieldName": "name",
                            "type": "String!",
                            "isConditional": false,
                            "isDeprecated": false,
                            "deprecationReason": null
                        },
                        {
                            "responseName": "description",
                            "fieldName": "description",
                            "type": "String!",
                            "isConditional": false,
                            "isDeprecated": false,
                            "deprecationReason": null
                        },
                        {
                            "responseName": "image",
                            "fieldName": "image",
                            "type": "URL!",
                            "isConditional": false,
                            "isDeprecated": false,
                            "deprecationReason": null
                        },
                        {
                            "responseName": "battlesWon",
                            "fieldName": "battlesWon",
                            "type": "Int!",
                            "isConditional": false,
                            "isDeprecated": false,
                            "deprecationReason": null
                        }
                    ],
                    "fragmentSpreads": []
                }
            ]
        }
    ],
    "typesUsed": [
        {
            "kind": "ScalarType",
            "name": "URL",
            "description": ""
        }
    ]
}

Sorry for the delay.
So this PR introduced fragments that have inline fragments to be always optional https://github.com/apollographql/apollo-android/pull/899
but after this PR https://github.com/apollographql/apollo-android/pull/971 it doesn't make any sense as we always generate base class for inline fragment.
So I can assume we can remove this condition inlineFragments.isNotEmpty()


Unchecks "Use all F1, F2, etc. keys as standard function keys" in System Preferences

Avoids 'fn' with Rubymine shortcuts to run specs etc.
Uses a marker file to make sure it only runs once so it doesn't undo the change when run again.
Leave it upto you to decide where to wire this in

I finally figured out how to make this idempotent by reading the state of the checkbox.  You can see the end result here: https://github.com/pivotal/pivotal_workstation/commit/bea88ff9c3cd6a0dad68116bea8b8e638c438a02
I changed the name to function_keys.rb.  I also defaulted it to true in the next commit.
I'm not sure where to wire this in, as I don't want to irritate people using the meta recipes on their home laptops.  For now I'll put it in meta_lion_image.  Maybe some day it'll make sense to have a meta_desktop recipe and put it in there.


ionic4 --color css propery of ion-label is not usable

Ionic version:
[x] 4.1.2
Current behavior:
on a simple
<ion-list>
    <ion-item>
        <ion-label position="floating">Username</ion-label>
        <ion-input formControlName="username" type="text" (keydown.enter)="doSave()"></ion-input>
    </ion-item>
</ion-list>

with a css file
ion-label {
    --color: blue;
}

does not overwrite the color of a label, see the styles adapted by chrome

ALSO IMO:
an ion-label with an floating position should have a rgba(0,0,0,.6) as color, like MD adopts in angular-material

You can do in css
ion-item > ion-label...
But this is not what I'm expecting reading documentation

Hi there,
Thanks for the issue! I am going to close this as a duplicate of #17425. As a temporary workaround you will need to do:
ion-label {
  --color: blue !important;
}

Thanks for bearing with us as we investigate this issue! 🙂


{include_erts, false}. excludes stdlib and other erlang dependencies

Reproduction
Using the exrm-test project as a base, create the ./rel directory and
add a relx.config with the following:
$ mkdir rel
$ cat << EOF > ./rel/relx.config
{include_erts, false}.
EOF

Create the release:
$ MIX_ENV=prod mix do deps.get, compile, release

Check the output of ./rel/test/lib/:
$ ls ./rel/test/lib
certifi-0.4.0  hackney-1.6.0  logger-1.2.4   ssl_verify_fun-1.1.0
tzdata-0.5.7 combine-0.7.0  idna-1.2.0     metrics-1.0.1  test-0.0.1
elixir-1.2.4   iex-1.2.4      mimerl-1.0.2   timex-2.0.0

Expected Output
Using the same steps as above, without creating the relx.config file, the
./rel/test/lib folder contains the expected output:
$ ls ./rel/test/lib
asn1-4.0.2      hackney-1.6.0  mimerl-1.0.2          test-0.0.1
certifi-0.4.0   idna-1.2.0     public_key-1.1.1      timex-2.0.0
combine-0.7.0   iex-1.2.4      sasl-2.7              tzdata-0.5.7
compiler-6.0.3  kernel-4.2     ssl-7.3 crypto-3.6.3    logger-1.2.4
ssl_verify_fun-1.1.0 elixir-1.2.4    metrics-1.0.1  stdlib-2.8

Other Notes
As a side note, adding {system_libs, true}. explicitly to ./rel/relx.config
does not solve this issue, none of the Erlang/system libraries are included.
All steps above were done on Arch Linux.
$ elixir --version
Erlang/OTP 18 [erts-7.3] [source] [64-bit] [smp:8:8] [async-threads:10] [hipe] [kernel-poll:false]

Elixir 1.2.4

They shouldn't be included, by not bundling ERTS, modules which are linked to that specific ERTS installation will be loaded from the ERTS on the target system (where you are deploying the release to).


Support --no-browser

Currently, if you start jupyter server it always starts a browser process. Should support --no-browser that makes this not happen.

Good point. I think that should even be the default behavior, because Jupyter Server without extensions is supposed to be headless.

Seems like anything related to starting a browser belongs in the extension and not the server. Could this "browser-related code" be placed into, for example, ExtensionWebApp that derives from ExtensionApp and from which the likes of Notebook and Lab derive?  Things like Enterprise Gateway - that don't want a browser would derive from ExtensionApp.
I understand that's probably easier said than done, but strikes me as the right separation.

Should support --no-browser that makes this not happen.

@yuvipanda  Try this:
jupyter server --ServerApp.open_browser=False

We should make a --no-browser alias to simplify this command though.

auto-closed by mistake

Solved in #82.


Internal error occurred: resource quota evaluates timeout

I used helm to publish my application, but when I executed helm install ./kps --tls for the first time, this error was reported
release kps failed: Internal error occurred: resource quota evaluates timeout

I used helm lists to check the status and found the status was failed.
Then I executed the delete operation and executed the install command again, it's success!
Has anyone encountered such a situation？

This internal server error comes right from kubernetes. Helm is just passing along the error back to the client. In other words, Helm tried to interact with the kubernetes cluster and received an internal server error while making requests, so it was unable to perform certain tasks.
I have not seen such an error before. Let us know what you find out.

Hi, @fancc - based on https://github.com/rancher/rancher/issues/18658#issuecomment-470360645 I looked in the 1.18 code, and as mentioned about, it does appear this timeout is coming from Kubernetes:
https://github.com/kubernetes/kubernetes/blob/32fd3186a9604b4bb8bfc5d8e8f7ce1c7d020751/plugin/pkg/admission/resourcequota/controller.go#L617-L625
So you probably want to investigate your cluster's responsiveness and stability. Hope this helps! As this does not seem to be caused by Helm, I'll resolve this issue at this time.


live home page

rather like #73 it would be nice if the home page refreshed periodically as new pipelines start or complete/fail

yes! it's a bit of work, because right now all the templating is done server-side, and if we want to do that we need to rewrite the templating client-side.
btw you've seen the new /running page which shows the running steps in real time?

yes! it's a bit of work, because right now all the templating is done server-side, and if we want to do that we need to rewrite the templating client-side.
btw you've seen the new /running page which shows the running steps in real time?

I use Code Injector plugin to inject this:
setTimeout(() => window.location.reload(), 10000)


Event listener/callback functionality

It would be nice to introduce some sort of event listener / callback functionality to react to events. Cards should be able to register events to react to certain conditions, and when those conditions are met, callbacks need to fire.
For example, Merchant needs to listen for silver to be played, Moat needs to listen for incoming attacks.

@evanofslack
I'm willing to look into this. I can create a draft PR for us to discuss

closed by @jbw3 with #104


There might be duplicate framework history records in database

For some corner cases, there might be multiple output line of the same framework and the same attempt index. So there might be duplicate framework history records in database.
For now, we can handle this in rest-server. We may use more complex SQL syntax to guarantee there is no duplicate records in future.

Use hash(uid, attemptIndex, historyType) to solve this problem.


PATENT npl_class: Parsing and Consolidation ?

Hello,
Since v0.2-npl, we have introduced a PATENT npl_class
Question
How should this class of citations be structured and consolidated?
Food for thoughts
Below is a sample of 100 citations for this class.

WITH
  tmp AS (
  SELECT
    npl_publn_id
  FROM
    `npl-parsing.patcit.v02_npl`
  WHERE
    npl_class="PATENT")
SELECT
  npl_biblio
FROM
  `usptobias.patstat.tls214` AS tls214,
  tmp
WHERE
  tmp.npl_publn_id = tls214.npl_publn_id

Row | npl_biblio |
-- | -- | --
1 | Specification and Drawings for U.S. Appl. No. 13/718,951, filed Dec. 18, 2012, 64 pages. |
2 | Eto (US Application No. 14/666,752) date 3/24/2015 |
3 | PATENT ABSTRACTS OF JAPAN vol. 3, no. 54 6 July 1979 (1979-07-06) |
4 | PATENT ABSTRACTS OF JAPAN, vol. 6, no. 162 (P-137)[1040], 25th August 1982; & JP-A- 57 078 670 (HITACHI SEISAKUSHO K.K.) 17-05-1982 |
5 | Google Content-Targeted Advertising FAQ (Mar. 12, 2007). |
6 | PATENT ABSTRACTS OF JAPAN vol. 015, no. 461 (C - 0887) 22 November 1991 (1991-11-22) |
7 | U.S. Appl. No. 12/701,089 / Issue Fee Payment, filed May 15, 2014, 1 page. |
8 | PATENT ABSTRACTS OF JAPAN vol. 0120, no. 89 (E - 592) 23 March 1988 (1988-03-23) |
9 | PATENT ABSTRACTS OF JAPAN vol. 1995, no. 09 31 October 1995 (1995-10-31) |
10 | U.S. Appl. No. 13/663,022, filed Oct. 29, 2012. |
11 | Machine Translation, Kameda et al., JP 2003-213369, Jul. 2003. |
12 | U.S. Appl. No. 10/837,142, filed on Apr. 30, 2004. |
13 | JP 07.248211A (Toyota Central Research & Development Lab Inc.), Sep. 26, 1995. |
14 | Patent Abstracts of Japan vol 6 no 181 (M-156) 1982 & JP 57 088 963 A |
15 | Ohashi 717 discloses an ink ejecting device having a multi layer protective film for electrode. |
16 | PATENT ABSTRACTS OF JAPAN vol. 1996, no. 10 31 October 1996 (1996-10-31) |
17 | PATENT ABSTRACTS OF JAPAN vol. 011, no. 080 (C - 409) 11 March 1987 (1987-03-11) |
18 | U.S. Appl. No. 14/598,568, filed Jan. 16, 2015, Vascular Implant and Delivery Method. |
19 | PATENT ABSTRACTS OF JAPAN vol. 1999, no. 08 30 June 1999 (1999-06-30) |
20 | CN 2928231 Y, Bai et al. Derwent, Abstract, English Translation, Aug. 1, 2007. |
21 | U.S. Appl. No. 14/332,828, filed Jul. 16, 2014, Customizing Offers for Sales of Combinations of Virtual Items. |
22 | PATENT ABSTRACTS OF JAPAN vol. 008, no. 281 (E - 286) 21 December 1984 (1984-12-21) |
23 | PATENT ABSTRACTS OF JAPAN vol. 015, no. 443 (M - 1178) 12 November 1991 (1991-11-12) |
24 | Patent Abstracts of Japan, vol. 7, No. 9, Japanese Publication No. JP57168051, Oct. 16, 1982. |
25 | JP 2-118251 A., In: Patents Abstracts of Japan, Sect. M-1001, July 23, 1990, Vol. 14, No. 339 |
26 | PATENT ABSTRACTS OF JAPAN vol. 8, no. 80 (M - 289) 12 April 1984 (1984-04-12) |
27 | Patent Abstracts of Japan, Publication No. 2000 057483, Published on Feb. 25, 2000, Nippon Telegr. & AMP; Teleph Corp. |
28 | PATENT ABSTRACTS OF JAPAN vol. 010, no. 154 (P - 463) 4 June 1986 (1986-06-04) |
29 | 'Patent Abstracts of Japan', Vol. 12, No. 424 (M-761), Nov. 10, 1988 & JP 63 159040 A (Sumitomo Rubber Ind Ltd), Jul. 1, 1988. |
30 | PATENT ABSTRACTS OF JAPAN vol. 012, no. 071 (P - 673) 5 March 1988 (1988-03-05) |
31 | Inert Anode Containing Oxides of Nickel, Iron and Zinc Useful for the Electrolytic Production of Metals-Ray et al., U.S. Ser. No. 09/542,318, filed Apr. 4, 2000. |
32 | U.S. Appl. No. 13/113,231, filed May 23, 2011, David M. Garrison. |
33 | PATENT ABSTRACTS OF JAPAN vol. 006, no. 026 (M - 112) 16 February 1982 (1982-02-16) |
34 | PATENT ABSTRACTS OF JAPAN |
35 | U.S. Appl. No. 60/189,862. |
36 | 'INJECTION, FONCTIONNEMENT AFFIN ET MAINTENANCE FACILIT E', REVUE TECHNIQUE AUTOMOBILE, vol. 50, no. 570, 1 February 1995 (1995-02-01), pages XXVI - XXXIII, XP000494843 |
37 | ERNEST M.HODNETT等，: 'Schiff bases of salicylaldehyde and their cobalt(II) derivatives as antitumor agents', 《PROCEEDINGS OF THE OKLAHOMA ACADEMY OF SCIENCE》 |
38 | Translation of Opponents Grounds of Appeal Sep. 8, 2010 (EP Patent No. 1539115). |
39 | English Abstract CN102643985, 'Method for extracting valuable metals from high-iron bauxite with step-by-step acid leaching', published on Aug. 22, 2012. |
40 | RoHS-Richtlinie 2011/65/EU |
41 | U.S. Appl. No. 14/102,379, filed Dec. 10, 2013, Fernando. |
42 | U.S. Appl. No. 09/739,122, Mar. 17, 2004, Interview Summary. |
43 | U.S. Appl. No. 14/350,467, filed Apr. 8, 2014, Cimpeanu, et al. |
44 | U.S. Appl. No. 61/073,542, entitled “Dynamic Media Bit Rates Based on Enterprise Data Transfer Policies,” filed Jun. 18, 2008. |
45 | U.S. Appl. No. 12/792,008, filed Jun. 2, 2010, Duane E. Kerr. |
46 | U.S. Appl. No. 12/913,650, filed Oct. 27, 2010, Dholakia et al. |
47 | U.S. Appl. No. 14/226,421, Amendment and Response filed Aug. 5, 2016, 8 pgs. |
48 | Authors et al. Apparatus and Method of Tenant Context Generation and Propagation in SaaS Environment. Aug. 19, 2010. IP.com. pp. 1-4. |
49 | Anthony Anthony et al., Pending specification, claims, figures for U.S. Appl. No. 09/996,355, Claims 1-73; filed Nov. 29, 2001. |
50 | U.S. Appl. No. 61/706,692, by Xiang Li, filed Sep. 27, 2012. |
51 | Junker, E., 2004, PIRSCH, 2: 4-10 |
52 | Patent Abstracts of Japan, 13, 355 (P-914) for JP 1-114780, dated May 8, 1989. |
53 | DATABASE WPI ON EPOQUE, Week 9109, LONDON: DERWENT PUBLICATIONS LTD., AN 91-058363, Class D16; & BR,A,89 03571 (CRUZ F O). |
54 | Patent Abstracts of Japan, vol. 96, No. 10, Oct. 31, 1996 & JP 08 167801 A (Murata Mfg Co Ltd), Jun. 25, 1996, abstract. |
55 | PATENT ABSTRACTS OF JAPAN vol. 010, no. 140 (P - 458) 23 May 1986 (1986-05-23) |
56 | PATENT ABSTRACTS OF JAPAN vol. 017, no. 279 (M - 1419) 28 May 1993 (1993-05-28) |
57 | Patent Abstract of Japan, for publication No.: 10-228431. |
58 | Patent Abstract of Japanese Application No. 4 140783, May 14, 1992. |
59 | JP<PHONE_NUMBER> A (Abstract) |
60 | Gregory Nieminen. U.S. Appl. No. 11/458,040, entitled 'Mitral Valve Annuloplasty Device with Twisted Anchor,' filed Jul. 17, 2006. |
61 | PATENT ABSTRACTS OF JAPAN vol. 009, no. 132 (M - 385) 7 June 1985 (1985-06-07) |
62 | Kilpatrick Stockton, LLP, Answers to Complaint, Affirmative Defenses and Counterclaims, dated Feb. 4, 2010. |
63 | File History for U.S. Appl. No. 12/638,692, filed Dec. 15, 2009, Inventor: Timothy Haines. |
64 | U.S. Appl. No. 11/933,019, filed Oct. 31, 2007, Kurth et al. |
65 | United States Patent and Trademark Office, 'Notice of Allowance and Fee(s) Due,' U.S. Appl. No. 12/420,907, May 6, 2010. |
66 | Machine translation of the description of JP<PHONE_NUMBER> A. |
67 | U.S. Appl. No. 12/990,296, filed Mar. 1, 2011, Claremon et al. |
68 | Su, Qiaojuan, et al., U.S. Appl. No. 12/234,435 titled, 'Directional Expression-Based Scientific Information Knowledge Management,' filed Sep. 19, 2008. |
69 | Patent Abstracts of Japan vol. 017, No. 332 (P-1562), Jun. 23, 1993 & JP 05 040418 A (Canon Inc.). |
70 | Patent Abstracts of Japan & JP 62002560 A. E-511, May 30,1987,Vol.11,No.169 |
71 | Abstract: Nakano et al., 'Biodegradable microspheres for Prolonged Anesthesia', HCAPLUS 102:209896 (1985). |
72 | PATENT ABSTRACTS OF JAPAN vol. 095, no. 004 31 May 1995 (1995-05-31) |
73 | WPI Abstract accession no. 99-076491 & JP10316720 Kunhoseokyui [2/12/98] |
74 | Translation, Tokairin, JP H05-299702, Translation Date June 2013, FLS, Inc., all pages. |
75 | PATENT ABSTRACTS OF JAPAN vol. 009, no. 307 (M - 435) 4 December 1985 (1985-12-04) |
76 | PATENT ABSTRACTS OF JAPAN vol. 009, no. 234 (E - 344) 20 September 1985 (1985-09-20) |
77 | English language abstract of German Publication No.3920879. |
78 | Patent Abstracts of Japan vol. 018, No. 335 (M-1627), Jun. 24, 1994 & JP 06 080071 A (Sumitomo Electric Ind Ltd), Mar. 22, 1994, siehe Zusammenfassung; Abbildungen 1,2,5,6. |
79 | PATENT ABSTRACTS OF JAPAN vol. 013, no. 067 (M - 798) 15 February 1989 (1989-02-15) |
80 | PATENT ABSTRACTS OF JAPAN vol. 017, no. 327 (C - 1073) 22 June 1993 (1993-06-22) |
81 | Ltd. Tetsutani Nippon Aerosil - Google machine translation of webpage http://www.tetsutani.co.jp/ganryou_evo_04.html downloaded on September 13, 2014. |
82 | U.S. Appl. No. 11/763,363, filed Jun. 14, 2007, James Reztlaff II; Thomas Ryan, 'Search Results Generation and Sorting.' |
83 | U.S. Appl. No. 61/154,945, filed Feb. 24, 2009. |
84 | PATENT ABSTRACTS OF JAPAN vol. 017, no. 264 (E - 1370) 24 May 1993 (1993-05-24) |
85 | U.S. Application No. 08/664,262 filed May 13, 1996 Automatic Funds Processing System. |
86 | DATABASE WPI Week 8527, Derwent World Patents Index; AN 85-162563 |
87 | U.S. Appl. No. 60/198,014, Bretl et al. |
88 | English translation of JP 06 211511, Aug. 1994. |
89 | Persson, Carl J., et al., 'Head-up Display Communication System and Method', filed Nov. 6, 2007, U.S. Appl. No. 11/936,074. |
90 | PATENT ABSTRACTS OF JAPAN vol. 012, no. 491 (C - 554) 21 December 1988 (1988-12-21) |
91 | PATENT ABSTRACTS OF JAPAN vol. 014, no. 165 (P - 1030) 30 March 1990 (1990-03-30) |
92 | U.S. Appl. No. 10/761,524, filed Jan. 21, 2004, Robert Wham. |
93 | Kato et al.: 'Wireless IC Device and Wireless IC Device Composite Component'; U.S. Appl. No. 12/276,444, filed Nov. 24, 2008. |
94 | PATENT ABSTRACTS OF JAPAN vol. 017, no. 085 (E - 1322) 19 February 1993 (1993-02-19) |
95 | Pending U.S. Patent Application entitled 'Data Breakout Appliance At the Edge of a Mobile Data Network', U.S. Appl. No. 13/297,807, filed Nov. 16, 2011 by William F. Berg et al. |
96 | PATENT ABSTRACTS OF JAPAN vol. 1995, no. 08 29 September 1995 (1995-09-29) |
97 | PATENT ABSTRACTS OF JAPAN vol. 1998, no. 13 30 November 1998 (1998-11-30) |
98 | PATENT ABSTRACTS OF JAPAN vol. 1998, no. 02 30 January 1998 (1998-01-30) |
99 | PATENT ABSTRACTS OF JAPAN vol. 015, no. 181 (C - 0830) 9 May 1991 (1991-05-09) |
100 | PATENT ABSTRACTS OF JAPAN vol. 1998, no. 09 31 July 1998 (1998-07-31)

Open questions

Need for further sub-classification? If yes, which sub-classes?
Fields to be parsed?
Corpus/ reference database for consolidation?

I leave these questions open to discussion.
Cheers

Some ideas:

Corpus: Patent abstracts of Japan, derwent abstract, etc
Corpus metadata: volume, issue, date
Patent:  original, status (consolidation), orgname (consolidation), epodoc (consolidation)

Hello,
Some thoughts on the consolidation task.
There is a key question: from the bibliographical data reported on the Patent Abstracts of Japan, can we get back a high quality/richer database. Here is what I was able to find on the EPO website

Where can I find English abstracts of Japanese patent documents?
You can find English abstracts of Japanese patent documents (Patent Abstracts of Japan, PAJ) on the website of the JPO's Japan Platform for Patent Information (J-PlatPat). The JPA include bibliographic information, the abstract and a representative drawing for Japanese unexamined patent publications from 1976 to date. Due to the translation work involved, the time delay between publication of an unexamined patent application in Japan and the availability of the corresponding PAJ abstract is approximately four months.
https://www.epo.org/service-support/faq/searching-patents/asian/japan.html

There is also this document which explains how to access PAJ on the JpatPlat website. However, I still can't find how to map the data in PAJ citations (e.g. "PATENT ABSTRACTS OF JAPAN vol. 017, no. 279 (M - 1419) 28 May 1993 (1993-05-28)" to a publication_number... which is what we want in the end.
Cheers


Fix provider versions in docs

Description of your changes
Fix provider versions in docs
I have:

[x] Run make reviewable test to ensure this PR is ready for review.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Typings Installer continuously runs and consumes lots of resources

VSCode Version: 1.11.2
OS Version: Windows 10

Steps to Reproduce:

Open a NodeJS project in VS Code

VS Code will run some Typings installer in the background:
"C:\Program Files (x86)\Microsoft VS Code\Code.exe" "c:\Program Files (x86)\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib/typingsInstaller.js" --globalTypingsCacheLocation C:/Users/Oliver/AppData/Local/Microsoft/TypeScript --enableTelemetry

This process continuously performs I/O and uses a 100% of 1 core. The process never seems to complete. The process with the command line quoted above has been running at this resource usage for over 1 hour.
I am not aware of what special condition causes this as this seems to be a constant state on my machine.

Thanks. We're tracking this issue upstream with https://github.com/Microsoft/TypeScript/issues/15301 Hopefully we'll be able to get a fix in the next TS release
If this is blocking your work, try clearing the C:/Users/Oliver/AppData/Local/Microsoft/TypeScript location to see if this resolve things. You can also set "typescript.disableAutomaticTypeAcquisition": true to disable the typings install entirely

Thank you


Fixes 3066: introspect aarch64 repositories

Summary
Google aarch64 repositories don't need to be introspected yet, as we don't build aarch64 images for google cloud.
Testing steps
Checklist

[x] Tested with snapshotting feature disabled and pulp server URL not configured if appropriate

https://issues.redhat.com/browse/HMS-3066

oktotest

/test

[test]

failing test is unrelated and fixed in master.


mod manager completely blank.

ive tried full reinstalls of the manager including older versions and purging the %appdata% , it was literally working this morning and has just out of the blue gone blank.

I did a complete reinstall of all of the mods and the mod manager+purging the appdata again, this time everything managed to link back up and the problem was solved


Cannot read credentials

An uncaught Exception was encountered
Type: InvalidArgumentException
Message: Cannot read credentials from C:\Users\Cesare/.ebay_sdk/credentials
Filename: >C:\xampp\htdocs\test\application\third_party\ebaysdk\DTS\eBaySDK\Credentials\CredentialsProvider.php
Line Number: 132
Backtrace:

Hi,
I have the error above when I try to use the code in 03-refresh-user-token.php
Could you help me?
Thank you in advance

Probably the credentials you provided are missing.


🐛 7.0.1 - Incompatible versions for FirebaseInstallations in generated Podfile

[REQUIRED] Please fill in the following fields:

Unity editor version: 2020.1.17.f1
Firebase Unity SDK version: 7.0.1
Source you installed the SDK: UPM
Problematic Firebase Component: Installations
Other Firebase Components in use: Auth, Crashlytics, ANalytics, Messaging, Remote Config
Additional SDKs you are using: Facebook, GoogleMobileAds
Platform you are using the Unity editor on: Mac
Platform you are targeting: iOS
Scripting Runtime: IL2CPP

[REQUIRED] Please describe the issue here:
pod install
Analyzing dependencies
[!] CocoaPods could not find compatible versions for pod "FirebaseInstallations":
  In Podfile:
    Firebase/RemoteConfig (= 7.0.0) was resolved to 7.0.0, which depends on
      FirebaseRemoteConfig (~> 7.0.0) was resolved to 7.0.0, which depends on
        FirebaseInstallations (~> 7.0)

    FirebaseInstallations (= 1.7.0)

Steps to reproduce:
package.json
    "com.google.external-dependency-manager": "1.2.163",
    "com.google.firebase.analytics": "7.0.1",
    "com.google.firebase.auth": "7.0.1",
    "com.google.firebase.crashlytics": "7.0.1",
    "com.google.firebase.installations": "7.0.1",
    "com.google.firebase.messaging": "7.0.1",
    "com.google.firebase.remote-config": "7.0.1",

Generated Podfile
source 'https://github.com/CocoaPods/Specs.git'
source 'https://github.com/CocoaPods/Specs'
platform :ios, '11.0'

target 'UnityFramework' do
  pod 'FBSDKCoreKit', '~> 8.0'
  pod 'FBSDKGamingServicesKit', '~> 8.0'
  pod 'FBSDKLoginKit', '~> 8.0'
  pod 'FBSDKShareKit', '~> 8.0'
  pod 'Firebase/Analytics', '7.0.0'
  pod 'Firebase/Auth', '7.0.0'
  pod 'Firebase/Core', '7.0.0'
  pod 'Firebase/Crashlytics', '7.0.0'
  pod 'Firebase/Messaging', '7.0.0'
  pod 'Firebase/RemoteConfig', '7.0.0'
  pod 'FirebaseInstallations', '1.7.0'
  pod 'GoogleMobileAdsMediationFacebook', '<IP_ADDRESS>'
  pod 'GoogleMobileAdsMediationUnity', '<IP_ADDRESS>'
  pod 'Google-Mobile-Ads-SDK', '~> 7.68'
  pod 'GoogleSignIn', '>= 5.0.0'
end
target 'Unity-iPhone' do
end
use_frameworks!

Relevant Code:
See above

Someone forgot to update the dependencies with a commit that was recently made.
This seems to only affect Unity users.
Easy fix for now:
Add a new FirebaseInstallationFixDependencies.xml to one of your Editor folders.
This will then bump up the version from 1.7.0 to 7.0.0 (or whatever you need).

This is a build issue that could have been prevented via a CI/CD build test before releasing new versions that obsolete an older API.

**_:smile:yes _ **

Another stopgap fix would be to change the generated podfile line from
pod 'FirebaseInstallations', '1.7.0'

to
pod 'FirebaseInstallations', '7.0.0'

We have a proper fix for this on the way in an upcoming release.

@alexames : FYI I also see this in 7.0.2.

@alexames : FYI I also see this in 7.0.2.

Same here. It is showing in Firebase Unity SDK 7.0.2

pod 'FirebaseInstallations', '1.7.0'

This should be fixed in the next release


Bundler: Support multiple versions of Gemfile and Gemfile.lock

The BootBoot gem makes it very easy to run tests against
against future versions of Rails.
When running bundle install it produces a Gemfile_next.lock
alongside the usual Gemfile.lock. At the moment Dependabot
only fetches the standard Gemfile.lock
This commit enables the Bundler::FileFetcher to fetch
all Gemfile.lock files and all Gemfile versions.
Fix https://github.com/dependabot/dependabot-core/issues/2106

Thank you for submitting this!  We'll give it a review as soon as we can!

@paulsturgess nice work on this! I think this is a good way there but we should also test out and make sure the rest of the update flow works as expected.
The basic flow of an update goes through the following steps which should be tested:

[x] FileFetcher: fetch manifests

This is mostly there, just commented around gems.rb files

[ ] FileParser: parse the manifest files into an array of Dependency objects de-duping any duplicates across multiple manifests but adding each one with a lockfile to the Dependency#requirements array pointing to the source Gemfile (this should already be happening in the file parser just need to make sure we are parsing all of the files and generate the correct Dependency objects)

Our data model here is a bit limited in the sense that we de-dupe the same dependency across   multiple manifests to the lowest version of the set
Tests should include multiple manifests and lockfiles with different names checking that the parsed dependencies array includes looks correct, is de-duped and picks the lowest lockfile version when the dependency is specified with different versions across multiple lockfiles

[ ] UpdateChecker: for each parsed dependency check what the latest resolvable version is (also needs to support running bundler on the correct Gemfile)

Same input as the file parser tests with multiple manifests checking that it produces updated dependencies that exists across multiple manifests

[ ] FileUpdater: write the manifest files to a temp directory and tell bundler to update a specific dependency to a specific version updating the correct Gemfiles

Same input as file parser and update checker with multiple manifest files checking they are all updated with the correct versions

Hopefully, it's not too daunting! I think it makes sense to tackle one at a time. Happy to help with any questions/issues.

Thanks @feelepxyz, indeed that looks very complex from my point of zero knowledge of the Dependabot internals at this time.
Out of interest, if I was to revert the change to enable multiple Gemfiles and only support the multiple Gemfile.lock files – would that make this task significantly simpler?
The bootboot bundler plugin only uses a single Gemfile but produces 2 lock files and this is the primary reason I opened this PR.
So if I can get that feature working first with a much smaller PR, I'd prefer to work on just that. What do you think?

@paulsturgess ah yeah it's quite a complex setup! I think we'll need to do similar amount of work for a single Gemfile with multiple lockfiles as this has the same implications on how we need to model the dependencies and make sure to run bundler on the right ones.
We're pretty stretched at the moment so don't have much spare capacity to help out on this, hoping to get some more people on board soon though.

Related:

https://github.com/dependabot/dependabot-core/issues/3266


CONTRIBUTING.md much less detailed than the Guide's contributing page

https://docs.symbol.dev/contribute/contributing.html contains far clearer and more detailed instructions on contributing to the guide than CONTRIBUTING.md in the Symbol-docs root directory. CONTRIBUTING.md should be updated to reflect this - either by linking to the guide's page(s) on contributing to the guide, or updating CONTRIBUTING.md to include the same contents.
New contributors who find CONTRIBUTING.md will likely be unaware of the more refined set of contribution instructions/guidelines more deeply nested in the repository.

The instructions on https://docs.symbol.dev/guidelines/writing-a-guide.html don't include instructions to create a .po file, which is required for translation. These instructions also seem to be missing from https://docs.symbol.dev/guidelines/translating-the-documentation.html - so it seems there is a gap in the workflow set out by the guide.
This gap is at least partially bridged by the instructions in under the heading "Updating translations".
Ideally the guide should be updated to cover the creation of .po files in addition to any changes made to CONTRIBUTING.md .


Documentation review

Attempt to update and clean up the documentation.
Preview: https://sphericart--143.org.readthedocs.build/en/143/

I haven't touched the CUDA C++ and torch docs yet. I think we should wait for CUDA C++ to match the C++ API and for #141 to be merged. Everything else should be ready

The CUDA c++ example seems to imply that there is just compute, but the API also specify compute_with_gradient and compute_with_hessian - I suspect it needs updating.


TypeError: must be string, not int

In a freshly installed Debian (2015-03-01) on Beaglebone Black Rev A6A, the encoder_test.py example shows this error:
Traceback (most recent call last):
  File "encoder_test.py", line 24, in <module>
    run(setup, loop)
  File "/usr/local/lib/python2.7/dist-packages/PyBBIO-0.9.3-py2.7-linux-armv7l.egg/bbio/bbio.py", line 60, in run
    loop()
  File "encoder_test.py", line 22, in loop
    delay(1000)
  File "/usr/local/lib/python2.7/dist-packages/PyBBIO-0.9.3-py2.7-linux-armv7l.egg/bbio/common.py", line 36, in delay
    time.sleep(ms/1000.0)
TypeError: must be string, not int
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "/usr/local/lib/python2.7/dist-packages/PyBBIO-0.9.3-py2.7-linux-armv7l.egg/bbio/bbio.py", line 21, in bbio_cleanup
    for cleanup in ADDITIONAL_CLEANUP:
TypeError: must be string, not int
Error in sys.exitfunc:
Traceback (most recent call last):
  File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "/usr/local/lib/python2.7/dist-packages/PyBBIO-0.9.3-py2.7-linux-armv7l.egg/bbio/bbio.py", line 21, in bbio_cleanup
    for cleanup in ADDITIONAL_CLEANUP:
TypeError: must be string, not int

Code is wrong at time.sleep(ms/1000), is ms previously defined. Check for
that because sleep function takes int.
On Saturday, March 14, 2015, Ali Yousuf<EMAIL_ADDRESS>wrote:

In a freshly installed Debian (2015-03-01) on Beaglebone Black Rev A6A,
the encoder_test.py example shows this error:
Traceback (most recent call last):
File "encoder_test.py", line 24, in
run(setup, loop)
File "/usr/local/lib/python2.7/dist-packages/PyBBIO-0.9.3-py2.7-linux-armv7l.egg/bbio/bbio.py", line 60, in run
loop()
File "encoder_test.py", line 22, in loop
delay(1000)
File "/usr/local/lib/python2.7/dist-packages/PyBBIO-0.9.3-py2.7-linux-armv7l.egg/bbio/common.py", line 36, in delay
time.sleep(ms/1000.0)
TypeError: must be string, not int
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
File "/usr/local/lib/python2.7/dist-packages/PyBBIO-0.9.3-py2.7-linux-armv7l.egg/bbio/bbio.py", line 21, in bbio_cleanup
for cleanup in ADDITIONAL_CLEANUP:
TypeError: must be string, not int
Error in sys.exitfunc:
Traceback (most recent call last):
File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
File "/usr/local/lib/python2.7/dist-packages/PyBBIO-0.9.3-py2.7-linux-armv7l.egg/bbio/bbio.py", line 21, in bbio_cleanup
for cleanup in ADDITIONAL_CLEANUP:
TypeError: must be string, not int
--
Reply to this email directly or view it on GitHub
https://github.com/graycatlabs/PyBBIO/issues/58.

--
Saleem Ahmad

I have not changed anything in the example. It is in integer already. The error says "must be String" -- I'm also confused at this.
Here is the code
#!/usr/bin/env python
"""
 encoder_test.py
 Rekha Seethamraju

 An example to demonstrate the use of the eQEP library
 for PyBBIO.

 This example program is in the public domain.
"""
from bbio import *
from bbio.libraries.RotaryEncoder import RotaryEncoder

encoder = RotaryEncoder(RotaryEncoder.EQEP2b)

def setup():
  encoder.setAbsolute()
  encoder.zero()

def loop():
  print "encoder position : \t"+encoder.getPosition()
  delay(1000)

run(setup, loop)

Hmm... this is an odd one. Seems that either the RotaryEncoder library itself or the sysfs C extension it uses to read/write the eQEP driver files is the source of the problem (time.sleep most certainly doesn't take a string!). I'm looking into it...

Just letting you know I'm having the exact same problem with the same code
I'm on Beaglebone Black Rev C.  Version is:
Linux beaglebone 3.8.13-bone70 #1 SMP Fri Jan 23 02:15:42 UTC 2015 armv7l GNU/Linux
Any new ideas on this yet?  I'm stuck

OK got it, I was missing a type check in a C extension, and the TypeError was popping up at a weird time.