disconnection in same time.

Hi.
I am using image: waytrade/ib-gateway:981.3g
I got disconnection every day. Is it a kind of configuration? Can I set disconnection(?) at different time?
2022-02-24	18:46:12 NOTIFY_STORE| ConnectionClosed <connectionClosed>
2022-02-23	18:47:01 NOTIFY_STORE| ConnectionClosed <connectionClosed>
2022-02-22	18:46:12 NOTIFY_STORE| ConnectionClosed <connectionClosed>
2022-02-21	18:46:12 NOTIFY_STORE| ConnectionClosed <connectionClosed>
2022-02-20	18:46:12 NOTIFY_STORE| ConnectionClosed <connectionClosed>
2022-02-17	18:46:12 NOTIFY_STORE| ConnectionClosed <connectionClosed>
2022-02-16	18:46:12 NOTIFY_STORE| ConnectionClosed <connectionClosed>
2022-02-15	18:46:13 NOTIFY_STORE| ConnectionClosed <connectionClosed>
2022-02-14	18:45:10 NOTIFY_STORE| ConnectionClosed <connectionClosed>
2022-02-13	18:45:11 NOTIFY_STORE| ConnectionClosed <connectionClosed>
2022-02-11	18:45:09 NOTIFY_STORE| ConnectionClosed <connectionClosed>
2022-02-10	18:45:10 NOTIFY_STORE| ConnectionClosed <connectionClosed>

As far as I remeber, there is some way yo configure this IBC (config: https://github.com/waytrade/ib-gateway-docker/blob/master/config/ibc/config.ini ). As at https://github.com/IbcAlpha/IBC or https://groups.io/g/ibcalpha is can't figure out.
I never did it, what I do instead:
on the run CMD I start a custom script that launches /root/scripts/run.sh and my app afterwards. My app will try to connect to gateway 10 times with a 10s delay, so if can't connect to gateway for more than 1min, it will shutdown.  If you have specified"restart: always", it wil restart afterwards and you system will come back.
Handle all kind of failures: gateway down because of daily restart? reboot container. connectoin dropped because gateway hang? reboot container. whatever happens that brings connection down for more than 1min .. reboot container

Short "how to" on how I address the reboot on my images:

In run my run_delayed.sh from CMD https://github.com/waytrade/ib-api-service/blob/master/Dockerfile#L55
run_delayed.sh: https://github.com/waytrade/ib-api-service/blob/master/scripts/run_delayed.sh

Start gateway "/root/scripts/run.sh &" as you know it from https://github.com/waytrade/ib-gateway-docker/blob/master/Dockerfile#L83
Wait from time until gateway upp
Run the app https://github.com/waytrade/ib-api-service/blob/master/scripts/run_delayed.sh#L19
If App fails to connect to gateway, it will terminate, shutting down the container and restarting it

I am using something like your run_delayed.sh.
But I'd like to move the restart time. It happens middle of the trade hours.
I found the option in gateway.

Thank you for helping this


The project is not finished, maybe you found a ready-made solution?

Tell me if somewhere the definition of series co-integration is implemented, under the c # language. I can’t use R inserts due to the architecture.

Sorry I abandoned the project a while ago, not sure I will get back to finishing it


Update Android.gitignore

Reasons for making this change:
except mac system file DS_Store
Links to documentation supporting these rule changes:
TODO
If this is a new template:

Link to application or project’s homepage: TODO

add # except mac system file

@vsona thanks, but we track all the OS X-specific rules in Global/OSX.gitignore


YARN-11548. [Federation] Router Supports Format FederationStateStore.

Description of PR
JIRA: YARN-11548. [Federation] Router Supports Format FederationStateStore.
How was this patch tested?
Add Junit Test.
For code changes:

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

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 40s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

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

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 41s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
33m 57s

trunk passed

+1 :green_heart:
compile
2m 35s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
compile
2m 32s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
1m 28s

trunk passed

+1 :green_heart:
mvnsite
1m 17s

trunk passed

+1 :green_heart:
javadoc
1m 19s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
1m  9s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
2m 28s

trunk passed

+1 :green_heart:
shadedclient
36m 23s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 31s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
0m 57s

the patch passed

-1 :x:
compile
2m  4s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server-jdkUbuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04.txt
hadoop-yarn-server in the patch failed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04.

-1 :x:
javac
2m  4s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server-jdkUbuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04.txt
hadoop-yarn-server in the patch failed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04.

-1 :x:
compile
1m 53s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server-jdkPrivateBuild-1.8.0_382-8u382-ga-1~20.04.1-b05.txt
hadoop-yarn-server in the patch failed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05.

-1 :x:
javac
1m 53s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server-jdkPrivateBuild-1.8.0_382-8u382-ga-1~20.04.1-b05.txt
hadoop-yarn-server in the patch failed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 13s

the patch passed

+1 :green_heart:
mvnsite
1m  1s

the patch passed

+1 :green_heart:
javadoc
1m  0s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
0m 55s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
2m 36s

the patch passed

-1 :x:
shadedclient
9m 53s

patch has errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
3m 30s

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

+1 :green_heart:
unit
0m 31s

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

+1 :green_heart:
asflicense
0m 35s

The patch does not generate ASF License warnings.

131m 19s

Subsystem
Report/Notes

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

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

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

uname
Linux bc2a2a421b2f 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / befe2bca8e8e4d69a5a8b4e9421ee8565f7bd3e2

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

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

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

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

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 49s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

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

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 58s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
38m 37s

trunk passed

+1 :green_heart:
compile
2m 53s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
2m 34s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
1m 28s

trunk passed

+1 :green_heart:
mvnsite
1m 12s

trunk passed

+1 :green_heart:
javadoc
1m 11s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 59s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
2m 21s

trunk passed

+1 :green_heart:
shadedclient
38m 49s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 29s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
0m 55s

the patch passed

-1 :x:
compile
1m 57s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server-jdkUbuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04.txt
hadoop-yarn-server in the patch failed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04.

-1 :x:
javac
1m 57s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server-jdkUbuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04.txt
hadoop-yarn-server in the patch failed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04.

-1 :x:
compile
1m 48s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server-jdkPrivateBuild-1.8.0_382-8u382-ga-1~20.04.1-b05.txt
hadoop-yarn-server in the patch failed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05.

-1 :x:
javac
1m 48s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server-jdkPrivateBuild-1.8.0_382-8u382-ga-1~20.04.1-b05.txt
hadoop-yarn-server in the patch failed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 13s

the patch passed

+1 :green_heart:
mvnsite
0m 57s

the patch passed

+1 :green_heart:
javadoc
0m 54s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 49s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
2m 30s

the patch passed

-1 :x:
shadedclient
9m 38s

patch has errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
3m 16s

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

+1 :green_heart:
unit
0m 25s

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

+1 :green_heart:
asflicense
0m 32s

The patch does not generate ASF License warnings.

137m 12s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6116/1/artifact/out/Dockerfile

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

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

uname
Linux 64d49f92c257 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / befe2bca8e8e4d69a5a8b4e9421ee8565f7bd3e2

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

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

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

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

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 41s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

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

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 51s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
38m  9s

trunk passed

+1 :green_heart:
compile
2m 47s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
2m 29s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
1m 26s

trunk passed

+1 :green_heart:
mvnsite
1m 19s

trunk passed

+1 :green_heart:
javadoc
1m 23s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 13s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
2m 27s

trunk passed

+1 :green_heart:
shadedclient
37m 21s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 31s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
0m 58s

the patch passed

-1 :x:
compile
1m 59s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server-jdkUbuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04.txt
hadoop-yarn-server in the patch failed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04.

-1 :x:
javac
1m 59s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server-jdkUbuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04.txt
hadoop-yarn-server in the patch failed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04.

-1 :x:
compile
1m 57s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server-jdkPrivateBuild-1.8.0_382-8u382-ga-1~20.04.1-b05.txt
hadoop-yarn-server in the patch failed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05.

-1 :x:
javac
1m 57s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server-jdkPrivateBuild-1.8.0_382-8u382-ga-1~20.04.1-b05.txt
hadoop-yarn-server in the patch failed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 21s

the patch passed

+1 :green_heart:
mvnsite
1m  5s

the patch passed

+1 :green_heart:
javadoc
1m  3s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 59s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
2m 31s

the patch passed

-1 :x:
shadedclient
9m 48s

patch has errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
3m 31s

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

+1 :green_heart:
unit
0m 29s

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

+1 :green_heart:
asflicense
0m 39s

The patch does not generate ASF License warnings.

137m 38s

Subsystem
Report/Notes

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

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

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

uname
Linux 2f904ba994b5 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 52c9df14d321a6fc76779bf7c6ff48c7b0764f76

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

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

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

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

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 53s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

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

_ trunk Compile Tests _

+0 :ok:
mvndep
13m 43s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
35m 41s

trunk passed

+1 :green_heart:
compile
2m 48s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
2m 18s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
1m 21s

trunk passed

+1 :green_heart:
mvnsite
1m 11s

trunk passed

+1 :green_heart:
javadoc
1m 12s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m  2s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
2m 18s

trunk passed

+1 :green_heart:
shadedclient
38m 44s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 28s

Maven dependency ordering for patch

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

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

-1 :x:
compile
0m 31s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server-jdkUbuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04.txt
hadoop-yarn-server in the patch failed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04.

-1 :x:
javac
0m 31s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server-jdkUbuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04.txt
hadoop-yarn-server in the patch failed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04.

-1 :x:
compile
0m 26s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server-jdkPrivateBuild-1.8.0_382-8u382-ga-1~20.04.1-b05.txt
hadoop-yarn-server in the patch failed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05.

-1 :x:
javac
0m 26s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server-jdkPrivateBuild-1.8.0_382-8u382-ga-1~20.04.1-b05.txt
hadoop-yarn-server in the patch failed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 12s

the patch passed

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

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

+1 :green_heart:
javadoc
0m 53s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 48s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

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

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

-1 :x:
shadedclient
14m  8s

patch has errors when building and testing our client artifacts.

_ Other Tests _

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

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

+1 :green_heart:
asflicense
0m 31s

The patch does not generate ASF License warnings.

122m 16s

Subsystem
Report/Notes

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

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

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

uname
Linux c8afd49cf01b 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 19a35dd656da2cb7a8583503542406f8d742b3ec

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

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

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

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

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 50s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

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

_ trunk Compile Tests _

+0 :ok:
mvndep
13m 42s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
35m 40s

trunk passed

+1 :green_heart:
compile
2m 38s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
2m 18s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
1m 23s

trunk passed

+1 :green_heart:
mvnsite
1m 10s

trunk passed

+1 :green_heart:
javadoc
1m 12s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m  1s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
2m 16s

trunk passed

+1 :green_heart:
shadedclient
38m  3s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 28s

Maven dependency ordering for patch

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

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

-1 :x:
compile
0m 33s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server-jdkUbuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04.txt
hadoop-yarn-server in the patch failed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04.

-1 :x:
javac
0m 33s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server-jdkUbuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04.txt
hadoop-yarn-server in the patch failed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04.

-1 :x:
compile
0m 27s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server-jdkPrivateBuild-1.8.0_382-8u382-ga-1~20.04.1-b05.txt
hadoop-yarn-server in the patch failed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05.

-1 :x:
javac
0m 27s
/patch-compile-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server-jdkPrivateBuild-1.8.0_382-8u382-ga-1~20.04.1-b05.txt
hadoop-yarn-server in the patch failed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 12s

the patch passed

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

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

+1 :green_heart:
javadoc
0m 53s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 49s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

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

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

-1 :x:
shadedclient
14m 14s

patch has errors when building and testing our client artifacts.

_ Other Tests _

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

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

+1 :green_heart:
asflicense
0m 31s

The patch does not generate ASF License warnings.

121m 27s

Subsystem
Report/Notes

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

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

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

uname
Linux cf09cf589dd6 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 3de16e6ecff938d38af890954d145d271c30d3db

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

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

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

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

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 41s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+0 :ok:
mvndep
14m  4s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
32m 26s

trunk passed

+1 :green_heart:
compile
2m 45s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
2m 26s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
1m 23s

trunk passed

+1 :green_heart:
mvnsite
2m 27s

trunk passed

+1 :green_heart:
javadoc
2m 17s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m  4s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
4m 23s

trunk passed

+1 :green_heart:
shadedclient
36m 14s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 33s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 52s

the patch passed

+1 :green_heart:
compile
2m 48s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
2m 48s

the patch passed

+1 :green_heart:
compile
2m 32s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
2m 32s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 22s

the patch passed

+1 :green_heart:
mvnsite
2m  1s

the patch passed

+1 :green_heart:
javadoc
1m 51s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 45s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
4m 47s

the patch passed

+1 :green_heart:
shadedclient
36m 33s

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

_ Other Tests _

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

+1 :green_heart:
unit
101m 23s

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

+1 :green_heart:
unit
0m 31s

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

+1 :green_heart:
asflicense
0m 43s

The patch does not generate ASF License warnings.

269m 30s

Reason
Tests

Failed junit tests
hadoop.yarn.server.federation.store.impl.TestZookeeperFederationStateStore

hadoop.yarn.server.federation.store.impl.TestSQLFederationStateStore

Subsystem
Report/Notes

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

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

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

uname
Linux ba7c19b4afcf 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / acd0fd2fbc02965644195fd14073c313ed1300dc

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

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

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

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

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 41s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 35s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
35m 45s

trunk passed

+1 :green_heart:
compile
2m 50s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
2m 34s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
1m 27s

trunk passed

+1 :green_heart:
mvnsite
2m 24s

trunk passed

+1 :green_heart:
javadoc
2m 18s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m  4s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
4m 41s

trunk passed

+1 :green_heart:
shadedclient
36m 54s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 31s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 48s

the patch passed

+1 :green_heart:
compile
2m 25s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
2m 25s

the patch passed

+1 :green_heart:
compile
2m 19s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
2m 19s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 12s

the patch passed

+1 :green_heart:
mvnsite
1m 54s

the patch passed

+1 :green_heart:
javadoc
1m 46s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 40s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
4m 39s

the patch passed

+1 :green_heart:
shadedclient
36m 27s

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

_ Other Tests _

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

+1 :green_heart:
unit
101m 41s

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

+1 :green_heart:
unit
0m 32s

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

+1 :green_heart:
asflicense
0m 43s

The patch does not generate ASF License warnings.

273m 28s

Reason
Tests

Failed junit tests
hadoop.yarn.server.federation.store.impl.TestZookeeperFederationStateStore

Subsystem
Report/Notes

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

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

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

uname
Linux 950e29b13e9a 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / c5d5234edc3cea47de461bf85ab5241e85beffeb

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

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

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

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

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 40s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 54s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
32m 16s

trunk passed

+1 :green_heart:
compile
2m 32s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
2m 17s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
1m 22s

trunk passed

+1 :green_heart:
mvnsite
2m 20s

trunk passed

+1 :green_heart:
javadoc
2m 14s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m 28s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
4m 17s

trunk passed

+1 :green_heart:
shadedclient
34m 42s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 32s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 51s

the patch passed

+1 :green_heart:
compile
2m 36s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
2m 36s

the patch passed

+1 :green_heart:
compile
2m 22s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
2m 22s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 15s

the patch passed

+1 :green_heart:
mvnsite
1m 57s

the patch passed

+1 :green_heart:
javadoc
1m 51s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 45s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
4m 49s

the patch passed

+1 :green_heart:
shadedclient
35m 17s

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

_ Other Tests _

+1 :green_heart:
unit
3m 40s

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

+1 :green_heart:
unit
101m 12s

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

+1 :green_heart:
unit
0m 29s

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

+1 :green_heart:
asflicense
0m 40s

The patch does not generate ASF License warnings.

266m  8s

Subsystem
Report/Notes

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

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

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

uname
Linux 89a6d66a71c9 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 36c8730a97643f9047a0b4cfb57b617d1f581d4d

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

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

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

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

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 45s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
31m 45s

trunk passed

+1 :green_heart:
compile
2m 45s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
2m 22s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
1m 31s

trunk passed

+1 :green_heart:
mvnsite
2m 25s

trunk passed

+1 :green_heart:
javadoc
2m 21s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m  8s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
4m 18s

trunk passed

+1 :green_heart:
shadedclient
33m 24s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 51s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 49s

the patch passed

+1 :green_heart:
compile
2m 23s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
2m 23s

the patch passed

+1 :green_heart:
compile
2m  9s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
2m  9s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 13s

the patch passed

+1 :green_heart:
mvnsite
1m 55s

the patch passed

+1 :green_heart:
javadoc
1m 47s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 41s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
4m 22s

the patch passed

+1 :green_heart:
shadedclient
35m 12s

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

_ Other Tests _

+1 :green_heart:
unit
3m 22s

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

+1 :green_heart:
unit
101m  8s

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

+1 :green_heart:
unit
0m 33s

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

+1 :green_heart:
asflicense
0m 39s

The patch does not generate ASF License warnings.

263m 30s

Subsystem
Report/Notes

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

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

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

uname
Linux 0cb80af38dd0 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / cd940bce55ed121a5698cc1cb102cf6f267d7565

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

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

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

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

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

@goiri Thank you very much for your help in reviewing the code! I will continue to follow up on YARN-11561.


Base model for zero shot speech generation

Hello together,
I am currently trying to use OpenVoice for German language generation. I have not been able to figure out how this zero shot speech synthesis shall work. Is there some kind of multilanguage base model missing? When I use one of the language dependent base models things sound weird.
It would also be interesting if someone could explain how the different emotions/speech styles can be controlled. The documentation of the API could benefit from some more examples.

the text to speech synthesis in v1 is powered with openAI TTS system, the v2 is via MeloTTS. the v2 sounds more improved from my experience.
on first run, the models will be loaded automatically to your system and OpenVoice performs tone color conversion on the synthesized audio. here is the demo set up


[Basic] Add FileManager and start caching stat calls

This is both an optimization -- we avoid stat-ing multiple time -- and a mitigation for a correctness issue. We want to keep track of the file stats from the moment we open a file, and we don't want to stat it after we've opened & read it. This avoids racing where a file might change during compilation, and we record the new modification time when we've read the old one.

This can't be tested until https://reviews.llvm.org/D60735 goes in.

https://github.com/apple/swift-clang/pull/300
@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 82d68dfc4cdae79ef93dc54adde41459f99a0086

Build failed
Swift Test Linux Platform
Git Sha - 82d68dfc4cdae79ef93dc54adde41459f99a0086

apple/swift-clang#300
@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 0dcf07e560dd39b9c4c345bebf6c6fd2c9ad7c10

apple/swift-clang#300
@swift-ci please test Linux

Build failed
Swift Test Linux Platform
Git Sha - 0dcf07e560dd39b9c4c345bebf6c6fd2c9ad7c10

Closing for now.


New VMM extension integration mechanism

New vmm_extension() macro for registering bareflank extensions to the
build system from build configuration file

New VMM extension-specific config variables and extension-specific macros

Added vmm_ex.cmake to be included by all Bareflank extensions

Updated build system documentation

[RFC] #545
Signed-off-by: JaredWright<EMAIL_ADDRESS>

Another general comment I wanted to bring up about this PR:
I think that our build system is starting to cross over the line between normal-CMake and black-magic CMake. In other words, I just want to make sure that everyone is ok with the trade off of adding a non-trivial amount of complexity to our build system, with the payoff of ease-of-use for extension developers.
The only reason I bring this is that CMake has a steep learning curve for future maintenence, and we seem to be taking full advantage of all it has to offer.

Most recent commit adds the following:

Added more instructions to the template bfconfig.cmake file
Renamed all the "_ex" cmake files to "_extension"


Add mock/random MAC address generator

Describe the feature
A function call which would generate a random mock MAC address.
To Reproduce
Steps to reproduce the behavior:

Import mock_data
Use this function with following arguments: mockMacAddress()

Expected behavior
A random MAC address containing a series of hexadecimal bytes in a form of hexadecimal string. Possibly specific separator which separates the hexadecimal bytes, could be colon, no separator or dash.
Additional context
Possibly can be used for Ethernet MAC addresses or Bluetooth device IDs.

I'll look into this one in how to implement it. I wanted to create a small library to test Dart. These days, I'm not working with Dart as I used to before. At this peace, I could rewrite a whole library 😸 .


support scala 2.12 build

I have a scenario where we have a 0.8 Kafka Broker managed by a different org but I would like to upgrade my application to Scala 2.12.
I know the 0.8 branch is no longer maintained and all I am looking for is a one-off publish of a scala 2.12 compatible jar from the head of the 0.8 branch.

test this.

@guozhangwang One test fails when I run them with scala 2.12: https://travis-ci.org/scala212-forks/kafka

@pjfanning Actually I was telling jenkins to re-trigger builds for the unit tests :) But anyways, seems those jenkins builds failed either. May need to investigate more.

test this please.

Given how old 0.8.2 is and the fact that we haven't published 2.12 JARs for 0.9.0.x and 0.10.0.x, it seems unlikely that we'll publish JARs for 0.8.2.

I have published a scala 2.12 jar to maven central using a forked repo:
com.github.scala212-forks:kafka_2.12:<IP_ADDRESS>


Add mafia and build with GHC 8.0.2.

@markhibberd I found that bumping the version of network-api-support and cleaning up some warnings resulted in a clean build.

I guess the travis setup will need to be adjusted to build with mafia?


When page is loaded I see Russian translation, but in html-mode still english.

Describe the bug
When page is loaded I see Russian translation, but in html-mode still english but should be Russian.
Steps to reproduce
Check this repo
$ yarn dev
open http://localhost:3000/ru

Please provide a reproducible repository.

In my sample query props are works!
Check this repo
$ yarn dev
open http://localhost:3000/ru
What do we see? English translation in SSR, but should to be a Russian.

I assume that has something to do with your use of next-routes. Sorry, can't help much further as I have not personally used that package. Feel free to post on StackOverflow or similar. Good luck!

@isaachinman I solved it. Thanks


Cards on home page fail WCAG AA for contrast, Open Sans font isn't loading all weights

Was looking at #1663, and it alerted me to something else.

For the card descriptions on the front page, contrast fails WCAG AA at normal text sizes. The background color needs to be darker, the text perhaps lighter.
The font weights for Open Sans aren't being loaded correctly, so we can't select as many weights as we should be able to.

/assign @simmscg

/close


feat: Update REAME.md

Update README.md to reflect "vm_size" variable
pre-commit changes

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


change .obj color by program!

Money: 1000R
there should be a script by python or elixir or rust.
.obj example:
归档.zip

🙋🏻♂here


Modern build still loads "nomodule" scripts

Version
2.6.1
Reproduction link
http://example.com/sorry_it_is_impossible
Steps to reproduce
Have a simple nuxt.js SPA.
nuxt.config.js
module.exports = {
    mode: "spa",

    modern: "client",

...

Build it:
NODE_ENV=production ./node_modules/.bin/nuxt generate

What is expected ?
See the picture. Only the green scripts are expected to be loaded.
What is actually happening?
The "nomodule" scripts are still loaded.
Additional comments?
How would I completely drop support of the non-modern browsers?

This bug report is available on Nuxt community (#c9013)

@koresar
Could you provide more details about the repo ?
I tried with latest Nuxt, it works fine.

@koresar Sorry, just realized that it's generate, I'll have a look

Woohoo! Amazing fix @clarkdo. Thank you very much


Installation with Linuxbrew fails

Here is the log output from brew install lfe
==> Downloading https://github.com/rvirding/lfe/archive/v1.3.tar.gz
Already downloaded: /home/michel/.cache/Homebrew/lfe-1.3.tar.gz
==> make
Last 15 lines from /home/michel/.cache/Homebrew/Logs/lfe/01.make:
erlc -I include -o ebin -DERLANG_VERSION=\"20.3.6\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_types.erl
erlc -I include -o ebin -DERLANG_VERSION=\"20.3.6\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_init.erl
erlc -I include -o ebin -DERLANG_VERSION=\"20.3.6\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe_eval.erl
erlc -I include -o ebin -DERLANG_VERSION=\"20.3.6\" -DHAS_MAPS=true -DHAS_FULL_KEYS=true -DNEW_REC_CORE=true -DNEW_RAND=true -W1 src/lfe.erl
erlc -o src src/lfe_scan.xrl
install -m755 bin/lfeexec /usr/local/lib/lfe/bin
install: cannot stat 'bin/lfeexec': No such file or directory
Makefile:121: recipe for target 'bin/lfeexec' failed
make[1]: *** [bin/lfeexec] Error 1
make[1]: *** Waiting for unfinished jobs....
src/lfe_types.erl:37: Warning: export_all flag enabled - all functions will be exported
rm src/lfe_scan.erl
make[1]: Leaving directory '/tmp/lfe-20180527-7047-e845ta/lfe-1.3'
Makefile:95: recipe for target 'compile' failed
make: *** [compile] Error 2

I am usisg Ubuntu 16.04

Hrm, good to know. We have only tested brew on Mac.

I suspect, though, that this is a duplicate of issue #342.

The fix is in the develop branch, and once that's merged to master + released, and once Homebrew gets updated with the latest, this issue should go away.

Yes, the problem with this is that I have a mac and there everything just works fine. A simple way around it in the master branch is to by hand first do:
cc -o bin/lfeexec c_src/lfeexec.c

then it works. I don't why there is this problem.

LFE 2.0 is on the way ... when that's released, the Brew maintainers will be able to consume it.
Going to close this ticket, as the code-fix has been in place for a while.


Update CLI to 2.5.539

Should we update to "Microsoft.NET.Sdk.Functions": "1.0.26"? Why haven't we updated it before?

Should we update to "Microsoft.NET.Sdk.Functions": "1.0.26"? Why haven't we updated it before?

We generally don't update the reference to net sdk package by default. The process is to just release it on nuget and wait for people to try it themselves. If we see some issues we can roll out a fix for it. otherwise after sometime we change the defaults for net sdk pacakage


fix(layer): layer reference now reacts to layersChanged signal to unset reference when a layer is deleted

While testing the timestamp/cave annotation functionality, I came across this "issue" where deleting a segmentation layer that is linked from an annotation layer triggers this exception TypeError: Cannot read properties of undefined (reading 'visibleSegmentEquivalencePolicy')

Having LayerReference listen layersChanged instead of specificationChanged seems to make sense and works for both deleting a layer through the UI and through the state editor.

Also, this wasn't causing any obvious bugs in neuroglancer other than the error showing up in the console. It was only noticeable to me since I had "pause on uncaught exceptions" enabled.
Here is a link where you can reproduce it by deleting the first layer
https://neuroglancer-demo.appspot.com/#!{"dimensions":{"x":[4e-9%2C"m"]%2C"y":[4e-9%2C"m"]%2C"z":[4e-8%2C"m"]}%2C"position":[109421.8984375%2C41044.6796875%2C5417]%2C"crossSectionScale":2.1875%2C"projectionOrientation":[-0.08939177542924881%2C-0.9848012924194336%2C-0.07470247149467468%2C0.12882165610790253]%2C"projectionScale":27773.019357116023%2C"layers":[{"type":"segmentation"%2C"source":"precomputed://gs://fafb-ffn1-20190805/segmentation"%2C"tab":"rendering"%2C"segments":["710435991"]%2C"name":"fafb-ffn1-20190805"}%2C{"type":"annotation"%2C"source":"precomputed://gs://neuroglancer-20191211_fafbv14_buhmann2019_li20190805"%2C"tab":"rendering"%2C"annotationColor":"#cecd11"%2C"shader":"#uicontrol vec3 preColor color(default=\"blue\")\n#uicontrol vec3 postColor color(default=\"red\")\n#uicontrol float scorethr slider(min=0%2C max=1000)\n#uicontrol int showautapse slider(min=0%2C max=1)\n\nvoid main() {\n  setColor(defaultColor())%3B\n  setEndpointMarkerColor(\n    vec4(preColor%2C 0.5)%2C\n    vec4(postColor%2C 0.5))%3B\n  setEndpointMarkerSize(5.0%2C 5.0)%3B\n  setLineWidth(2.0)%3B\n  if (int(prop_autapse()) > showautapse) discard%3B\n  if (prop_score()<scorethr) discard%3B\n}\n\n"%2C"shaderControls":{"scorethr":80}%2C"linkedSegmentationLayer":{"pre_segment":"fafb-ffn1-20190805"%2C"post_segment":"fafb-ffn1-20190805"}%2C"filterBySegmentation":["post_segment"%2C"pre_segment"]%2C"name":"synapses_buhmann2019"}]%2C"showAxisLines":false%2C"showSlices":false%2C"selectedLayer":{"visible":true%2C"layer":"synapses_buhmann2019"}%2C"layout":"xy-3d"}

I think specificationChanged is correctly being triggered, it is just that it may be triggered later.  I think a better fix would be to simply delete this entire function (https://github.com/google/neuroglancer/blob/39272cdd398459bcbc03bf2f18affa9ebc2e340d/src/shared_disjoint_sets.ts#L70) so that accessing the object after its reference count becomes zero does not trigger exceptions.
I don't think "clearing" those fields had any significant impact on garbage collection anyway.

@jbms I forgot to say that from my testing at least specificationChanged does not get called when deleting a layer, I can work on some changes to make that happen. It looks like layerManager.specificationChanged is an aggregate of each individual layer.specificationChanged signal so probably that doesn't get fired when/before a layer is deleted.
Deleting disposed does fix this issue as well. I know I've run into this same type of error with disjoint sets in other places, probably a timing thing so any solution would be useful.

Ensuring that specificationChanged is triggered when a layer is deleted would be a helpful change --- it was intended to trigger any time the JSON representation changes.
I think we should combine that fix with the disposed fix.


Better Travis CI configuration

Currently, we run tests with 1.6 and tip for PostgreSQL 9.1 and SQLite.
We need to:

[x] add MySQL;
[ ] add PostgreSQL 9.2-9.6;
[ ] add different versions of MySQL.

Alternatively, we can switch to https://circleci.com – I was told it's better for such tests I don't think so anymore.

Looks like we are dumping Travis and moving to self-hosted Drone CI.


Reproducing results on my videos, with a custom trained yolox model

Hello, i have a custom trained model that i trained, (yolox), can i use it, is there any script on the repo that can let me use it along with reid or bytetracker, so i test the tracking on a video of mine?
Thanks in advance.

Hello, Yes. Try to use our demo scripts:
https://github.com/NirAharon/BoT-SORT/blob/a720e0490c6613dacccc0088f8c39c61725f1a63/README.md?plain=1#L213
Pass your YOLOX weights, exp files and video and it should work.
If you trained your network for more than one class use the multi-class tracker version: mc_demo.py.
Good luck!

Thanks for the reply,
I did this exactly, passed my weights to the -c argument, -f as my exp file, and video as my path argument, detector work correctly , but for some reason detection are being discarded and the final saved video has no visualized bboxes,
I am using mot17 S50weights also,
is there any logic in mc_demo that discard detections? So i can fix it?
Thanks in advance

May you provide more information?
Maybe you need to adjust the tracker thresholds, did you change the --new_track_thresh argument according to your network scores?
Did you check that the tracker gets the detections correctly?
Are you using demo.py or mc_demo.py? if you use the one class demo.py there is --aspect_ratio_thresh argument that filters vertical objects.

I am using mc_demo, okay will check the threshold, thanks

@AhmedKhaled945 Has this been resolved? I ask because I am about to use this repo but your answer might save me some headaches if you have a workaround or found a fix.
Thanks!

hi, i want to track multiclass when i pass this code, it still track only pedestrian. Any solution for this
python3 tools/mc_demo.py video --path v1.mp4 -f yolox/exps/example/mot/yolox_x_mix_det.py -c pretrained/bytetrack_x_mot17.pth.tar --with-reid --fuse-score --fp16 --fuse --save_result

Hi.
As you mentioned before, I passed my weights to the -c argument, -f as my exp file, and video path, also using mot17 S50weights.
And the final saved video has no visualized bboxes.
Can you tell me how you solved this problem? @AhmedKhaled945
(python3 tools/demo.py video --path test.mp4 -c /home/YOLOX_outputs/yolox_voc_s/latest_ckpt.pth -f yolox/exps/example/mot/yolox_voc_s.py --with-reid --fuse-score --fp16 --fuse --save_result)
When I print outputs of [outputs, img_info = predictor.inference(img_path, timer)] line 162 in demo.py,
"None" is printed.
I think I should change [class Predictor(object)] line 89 in demo.py as I changed -f exp file.
Is there any other advice for me? @NirAharon
Thank you.

@faziii0 did you change the Exp file self.num_classes from 1 and used trained multi-class YOLOX weights?

Hi @NirAharon I am also facing the same problem.
I am using the pretrained YOLOX tiny weight from the official YOLOX github repo model zoo and along with that I am also passing the corresponding YOLOX tiny exp file of yours and I have also change the number of classes to 80 since the original YOLOX model is trained on 80 classes however still I cannot visualise any detection box in the output video.
It will be really helpful if you can suggest any update

Has this issue already been resolved?
We want to use YOLOX for object detection and are having trouble detecting objects when using the custom model.
We have confirmed that object detection with the custom model has been successful, with an accuracy of approximately 70%.
It seems to be a problem before tracking.
Thanks in advance

same issue. has anyone resolved??

Hi, @NirAharon
I'm running a multi-class test with YOLOX , executing the following code:(Modified --new_track_thresh)
python tools/mc_demo.py video --path 1.mp4 -f yolox/exps/example/yolox_voc/yolox_voc_s.py -c pretrained/best_ckpt.pth --with-reid --fuse-score --fp16 --fuse --save_result
And the final saved video has no visualized bboxes, and there's nothing in the text. Is there any other advice for me? Thanks.


Problem with beep.Resample, Song speeds up

I am having a problem with resampling audio where when if I have already started playing one audio file and I want to stop the currently playing file and start playing another. The problem is the second audio file I play sounds speeded up.
The documentation says:
func beep.Resample(quality int, old beep.SampleRate, new beep.SampleRate, s beep.Streamer)

and I did exactly that with the following code:
resampled = beep.Resample(6, oldSampleRate, format.SampleRate, *streamer)

where oldSample is 48000 and format.SampleRate 44100
When I run the code like shown above the second file plays at a higher speed and tone, but when I swap oldSampleRate and  format.SampleRate like shown below I get the expected result, ie, the second file plays at its normal rate
resampled = beep.Resample(6, oldSampleRate, format.SampleRate, *streamer)

Working example can be found here https://github.com/nkalait/test_beep
There are two media fils in folder "audio books".  It should compile and run without any modifications.
In main.go you can edit the variable rootPath to give the path of the audio books folder provided and then compile and run

Hey, it looks like there might be a misunderstanding about how the resampler works. Just to clarify, the resampler is meant to convert the samplerate of the source streamer to a desired samplerate. The old samplerate should match that of streamer s, and the new samplerate should be the desired sample rate, which typically (and in your case as well) is the one the speaker was initialized with. The swapped example is the correct usage.
I noticed in your example that the audioPanel's format gets updated with every song. Keep in mind that the speaker's sample rate cannot be changed, so the new sample rate shouldn't be updated either. You could store the sample rate of the first audiobook played for that purpose, or simply initialize the speaker with a predefined sample rate like 44100 or 44800 and use it as a constant.
Feel free to reach out if you have any questions or need further clarification.

Thank you for your timely response, I'll make the necessary changes in my code and get back in touch if I run into more challenges

Thank you very much,
all is well now, does exactly what it is supposed to. I'll close the issue now


chore: update axios to 1.5.0

Codecov Report

Merging #60 (814a3e6) into main (44037df) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #60   +/-   ##
=======================================
  Coverage   79.68%   79.68%
=======================================
  Files           3        3
  Lines         123      123
  Branches       24       24
=======================================
  Hits           98       98
  Misses         11       11
  Partials       14       14


Fetch outside temperature from gateway

I do not know if that information is available through the Hilo Gateway, but it would be nice to be able to get the outside temperature used on the thermostats.
With that info, it could be used to display the same information on other thermostat not part of Hilo (Sinope per exemple) and other dashboard so the "outside temperature" will be constant all accross Home Assistant

Hilo uses Weather Underground's API to get outside temperature. You could always setup a REST API sensor to get the same info and have it displayed elsewhere.
AFAIK it's not part of the API calls we make at the moment as it's on a different endpoint. I'll try and get Hilo to publish the doc for it.

Awesome ! I knew they were using an API crossmatched with postal code, didn't know which one !
Thanks a bunch ! I'll use the source then :)

You're welcome.

@dwlfrth This will be added by #411. I'm trying for a release sometime this month.

OMG this is AWESOME !

Merci !!

@dwlfrth released just now.
Fait plaisir

Rebuilding now !

Great success ! Now we're jasing !
You might want to consider https://github.com/dvd-dev/hilo/pull/419 :)
Let me know !


Handle .pb filenames and paths dynamically in PbFileFetcher

The current version is limited to the usage of only the .pb files in the LTS and in addition it requires that the granularity is set to yearly, resulting in a filename which ends with the four digits of the year (_yyyy.pb). As our archiver appliance for the Belle II PXD is setup with a granularity of one file per month in the LTS (_yyyy_mm.pb), I needed a modification. This proposal now does not only cope for our specific case but should be able to find all required files for a PV across LTS, MTS and STS independently of the configured granularity of the archiver.
As far as I understand this patch completely keeps backwards compatibility.
Changes in tests/test_data.py and tests/test_js.py were only made to satisfy flake8/black rule checker.
I added several test functions to tests/test_pb.py which helped me to fix the logic of _get_pb_files(). But I'm pretty new to pytest and especially to mocking, so I guess there might be better solutions to avoid duplicated code.
Thank you very much in advance for your comments!

Sorry for the multiple pushes. I think the issues should be fixed now.

Just a quick note. Thanks for pushing the changes. Sorry for the delay in reviewing them. I'll try to do this in the next couple of days.

Hi @philipp-leitl and @aawdls ,
I was wondering about the status of this merge request? Is there something missing?
Greetings


Error response from daemon: no such id: apollo_release

now i update my docker version
it's Docker version 1.9.1, build a34a1d5
but when i try this "docker/scripts/release_start.sh"
there will be some errors ,like below:
OK ] Found device: /dev/loop7.
[ OK ] Found device: /dev/loop6.
[ OK ] Found device: /dev/loop5.
[ OK ] Found device: /dev/loop4.
[ OK ] Found device: /dev/loop3.
[ OK ] Found device: /dev/loop2.
[ OK ] Found device: /dev/loop1.
[ OK ] Found device: /dev/loop0.
[ OK ] Found device: /dev/loop-control.
flag provided but not defined: --shm-size
See 'docker run --help'.
Error response from daemon: no such id: apollo_release
Error response from daemon: no such id: apollo_release
Error response from daemon: no such id: apollo_release
Can anyone help me?

Did you install the docker by apollo's script?
https://github.com/ApolloAuto/apollo/blob/master/docker/scripts/install_docker.sh
The installed docker is supposed to be:
$docker -v
Docker version 17.05.0-ce, build 89658be

This error message is coming from "docker rm -f apollo_release", because your system does not have this container before. We add a conditional statement to fix this issue.

This issue has been fixed.  Please update your code repo.

you mean i have to download the new code from https://github.com/ApolloAuto/apollo.git.

[ OK ] Found device: /dev/loop0.
[ OK ] Found device: /dev/loop-control.
flag provided but not defined: --shm-size
See 'docker run --help'.
Error response from daemon: no such id: apollo_release
Error response from daemon: no such id: apollo_release
Error response from daemon: no such id: apollo_release
@startcode @wanglei828   can give me any advise.

@sgong4 which docker version are you using?
--shm-size is docker command's option. In my docker,
% docker --version
Docker version 17.05.0-ce, build 89658be

This option is supported.

@startcode @quning78 @wanglei828
i have updated the version . now it's ok for no such id: apollo_release.
but there is another problem :some command not found , what should i do next.
error information :
sgong4@in_dev_docker:/apollo$ docker/scripts/release_start.sh
APOLLO_ROOT_DIR=/apollo
docker/scripts/release_start.sh: line 72: docker: command not found
docker/scripts/release_start.sh: line 74: docker: command not found
tee: /proc/sys/kernel/core_pattern: Read-only file system
/apollo/data/core/core_%e.%p
[WARNING] Failed to find device with pattern "ttyUSB*" ...
[ OK ] Found device: /dev/ttyS0.
[ OK ] Found device: /dev/ttyS1.
[ OK ] Found device: /dev/ttyS2.
[ OK ] Found device: /dev/ttyS3.
[ OK ] Found device: /dev/ttyS4.
[ OK ] Found device: /dev/ttyS5.
[ OK ] Found device: /dev/ttyS6.
[ OK ] Found device: /dev/ttyS7.
[ OK ] Found device: /dev/ttyS8.
[ OK ] Found device: /dev/ttyS9.
[ OK ] Found device: /dev/ttyS10.
[ OK ] Found device: /dev/ttyS11.
[ OK ] Found device: /dev/ttyS12.
[ OK ] Found device: /dev/ttyS13.
[ OK ] Found device: /dev/ttyS14.
[ OK ] Found device: /dev/ttyS15.
[ OK ] Found device: /dev/ttyS16.
[ OK ] Found device: /dev/ttyS17.
[ OK ] Found device: /dev/ttyS18.
[ OK ] Found device: /dev/ttyS19.
[ OK ] Found device: /dev/ttyS20.
[ OK ] Found device: /dev/ttyS21.
[ OK ] Found device: /dev/ttyS22.
[ OK ] Found device: /dev/ttyS23.
[ OK ] Found device: /dev/ttyS24.
[ OK ] Found device: /dev/ttyS25.
[ OK ] Found device: /dev/ttyS26.
[ OK ] Found device: /dev/ttyS27.
[ OK ] Found device: /dev/ttyS28.
[ OK ] Found device: /dev/ttyS29.
[ OK ] Found device: /dev/ttyS30.
[ OK ] Found device: /dev/ttyS31.
[ OK ] Found device: /dev/can0.
[WARNING] Failed to find device with pattern "ram*" ...
[ OK ] Found device: /dev/loop-control.
[ OK ] Found device: /dev/loop0.
[ OK ] Found device: /dev/loop1.
[ OK ] Found device: /dev/loop2.
[ OK ] Found device: /dev/loop3.
[ OK ] Found device: /dev/loop4.
[ OK ] Found device: /dev/loop5.
[ OK ] Found device: /dev/loop6.
[ OK ] Found device: /dev/loop7.
docker/scripts/release_start.sh: line 111: docker: command not found
docker/scripts/release_start.sh: line 136: docker: command not found
docker/scripts/release_start.sh: line 137: docker: command not found
docker/scripts/release_start.sh: line 139: docker: command not found

release_start.sh is to run out of docker env.


how to test the app

Hi there, i am new to app developement. Do you know the best way to test the apps ? on an emulator and then on the tv? thanks

At the bottom of the README: https://github.com/immosmart/smartbox#autotests
Apparently runs Jasmine tests, (a good starting point).


Feature branch

This project is an online directory of chemicals in Brazil, you can find all of the requirements here. You can find the video presentation in this link.
In this project, I built:

The main page, with a link to the results page by clicking the "search" button or the "companies" link in the navbar;
The search results page, with a list of chemical companies, each with a link to the detail company page;
The detail company page.

Each of these pages have versions for 3 different screen sizes:

mobile: up to 768px;
tablet: up to 1024px;
desktop: from 1024px.

I followed the guidelines of the given design, including:

Colors;
Typographies: font face, size, and weight (used a similar one given the design);
Layout: composition and space between elements, for the 3 given screen sizes.

In this project I:

Used semantic HTML tags;
Used CSS selectors correctly;
Used HTML elements box model (margin, padding, width, height);
Used industry-standard tools (flexbox) to place elements in the page;
Created UIs adaptable to different screen sizes using media queries;
Applied front-end best practices;
Used CSS grid and flexbox;
Used SASS.

Your project looks great @MuriloRoque ...
Good luck!
With all my respect...
Your feedback will be on your dashboard, don't look here :)


@chunk="to-content" in map causes file not found error

When using @chunk="to-content" in a ditamap file,
the topicpull process throws ``Error! java.io.FileNotFoundException:''
for each topic in the ditamap. These errors do not seem to affect the
success of the output.
Method to reproduce:

Add @chunk="to-content" to samples/hierarchy.ditamap.
Build the xhtml: ant -f samples/ant_sample/sample_xhtml.xml

Hi. I've just started working with DITA 2.0 and I am seeing this issue.
I have modified hierarchy.ditamap and sequence.ditamap to add @chunk="to-content" in the  element, and renamed them hierarchy_to_content.ditamap and sequence_to_content.ditamap. When I try to build html5 help using the command "dita -f html5 -i samples/hierarchy_to_content.ditamap -o test/html5", I get many errors of the form "The file. . . is not available to resolve link information."
It's worth noting that the errors specify files such as /concept/sequence_to_content.dita or /task/sequence_to_content.dita, where the "task" or "concept" folder is appended. The file sequence_to_content.dita does exist in the temporary directory, but it doesn't exist in these subfolders.

I'm not able to reproduce this with 3.1. I followed the last steps above (rename hierarchy.ditamap to hierarchy_to_content.ditamap, set the chunk value to to-content on the map, and build), but got a single HTML5 output file without any build errors. Generated file content is correct with working links. I think this issue is obsolete.


Ensemble simulations2

https://github.com/NQCD/NQCDynamics.jl/blob/619997c6683d17e0df79a7aaddc6d2b397cad625/docs/src/ensemble_simulations.md?plain=1#L10
Why do you need to write atoms = NQCDynamics.Atoms([:H]) instead of  atoms = Atoms([:H])?

It shouldn't be necessary, I'm not sure why it's like this. It can be removed.


add "feature flags", and API to expose

Rather than incrementing the distribution spec version as certain optional features are added, this API and mapped values of "feature flags" will be used by registries to indicate whether new features are implemented. (Like PEP or similar extensions)

Rather... or as well as, we already have the v2 semantic as a legacy issue. What do you think about plain ole name value pairs as is done by feature gates in kube? https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/

I'm thinking more simply like
GET /v2/features

Add get back a response like:
["OEP-1", "OEP-4"]

like "OCI Extension Proposals", where we have markdown docs describing the feature (similar to https://www.python.org/dev/peps/ or https://github.com/kubernetes/enhancements/tree/master/keps)

ok so no false positives... just a set of distribution extension proposals (DEPs) for the optional extension points.

DEP is fine. Sounds like an abbreviation for "dependency" and I wondered if there would be a proposal that spans specs. But regardless.
Looking at xEP examples, the first proposal is setting up the proposal process itself. I'll take a stab at that

spec spanning ... never happen :)    xEPs is fine pronunciation zeps or eh'ps?

I like the extension proposal idea, I think that is a good way to separate the core of the spec from additional features in the future. As I have stated before, I think the specification needs to stay focused on the distribution of images (push and pull) rather than on registry operation. Just as we wouldn't expect the git protocol to continuously be added to with Github API features, we wouldn't expect this protocol to expand for all the needs of operating a registry. However, there are many different registry operators and agreeing on common APIs is good, I am fine with defining those here.
As for the /v2/features endpoint itself. We have discussed adding an endpoint like this for awhile but were never sure of what the scope of it might be. Simple is nice, but I might advocate for having a single endpoint which could fulfil requirements about getting the API version as well as more contextual metadata such as mirrors. So in that case, it might look like {"extensions":[]} rather than [].
Lastly, I think we need to consider that the extensions may need to define some configuration. Adding new endpoints via extensions may be easy, but that may end up putting a burden on the operators as well as the extension authors when it comes to defining the path. From an operational perspective, the service which implements the extension may be (and in some cases should be) different from the service handling the core specification API. For example today the authorization server and "distribution" server (such as a docker/distribution instance) would always run separately since they have different security profiles and scale requirements. An authorization server handles a smaller volume of requests and requires both a private key to sign tokens and user database access. While the "distribution" server only needs to be configured with storage backend access (which may be configured through something like IAM) and a public key for the authorization server. For a search extension, access to a completely different search backend would be necessary with a lower volume of requests. For pub sub, there was discussion about being able to send authorization keys, something a "distribution" server mentioned earlier should never have access to do. All that is to say that we should be flexible in how we let the registries configure their service extensions and not make an assumption they will be at the same URL prefix.

I think the specification needs to stay focused on the distribution of images

Fair, I think these are strictly related. Also, the registry is a CAS storage, so when much of these mechanics are already here, it makes sense to leverage it.

as for the endpoint itself ...

good point!
Perhaps a structure more like:
{
  "extensions": {
    "OEP-1": {
      "version": "0.1",
      "url.base": "https://example.com/v1/"
    },
    "OEP-4": {
      "version": "0.1",
      "url.prefix": "/sig"
    }
  }
}

which is easy enough to walk through the keys of the extensions, and then also have fields to give that kind of information.

Let's not reinvent the wheel anywhere.
I think some applications reuse the RFC for .well-known to accomplish this.
If Kubernetes does something, copying that might work, too.

The .well-known approach would cover a bit more than what is discussed here, primarily it was discussed as a way to "discover" registries and configurations across an entire domain. We still need something that could cover the capabilities of a single registry host. For example, /.well-known/ is always at the root path, but a registry may already be served as a sub path /v2/. We do need to solve that discovery from <domain> to <host>/v2 though. If we were to add features in a well known document, then we would always have to start at the <domain> (even if the client just has a host/mirror) and have that document synchronize with the capabilities of individual registry hosts. I still think we should keep the two separate, previously we suggested discovery for 1.1 but we wanted to figure out features before we finalize 1.0.
We still need to figure out the extension approach and formatting either way, but I am all for following a pattern that has proven successful in other projects. Any standard isn't going to help us with the formatting for defining the extensions though.


Firebase: NetworkError when attempting to fetch resource

Problem Description
When the client connects to POST https://firebaseremoteconfigrealtime.googleapis.com/v1/projects/<..>/namespaces/firebase:streamFetchInvalidations HTTP/1.1 , the remote server seems to disconnect our connection. Based on this, I guess missing http2 support might be the reason.
Is there a way to enable http2 for a specific set of domains? (e.g. firebaseremoteconfigrealtime.googleapis.com)
Error getting content: TypeError: NetworkError when attempting to fetch resource..

Edit:
Or maybe the problem is that it's a streaming response?

Same answer as in https://github.com/mitmproxy/mitmproxy/issues/7378#issuecomment-2527353293: If you think this is a mitmproxy bug and not a server error, this needs conclusive evidence.


Can you publish new version to include package.json dependencies changes

I found you move some development dependencies to devDependencies. That's great, I want to use it.
But no new version published. Can you publish a version to include this change?

Also, would be great if contour_plot was removed from dependencies when those changes are published


ci: Report coverage with CodeCov

Closes #2857
Closes #1391
Closes #175
This PR configures Vitest to generate coverage in JSON format per each test suite.
Multiple coverage files are uploaded into CodeCov, then CodeCov automatically merges those uploaded coverages smartly.
https://github.com/exoego/hono/pull/3 is a working demo how CodeCov bot reports coverage changes on each PR
You can also see the demo coverage on my CodeCov account:

(this demo coverage is not "accurate" since it includes unexpected files like benchmarks and runtime_tests. Such unexpected files are excluded in this PR)
:warning: Attention :warning:
Repo administrator should set CODECOV_TOKEN as GitHub secret for Actions.
The token can be obtained in https://app.codecov.io/github/honojs/hono/settings
or maybe https://app.codecov.io/github/honojs/hono
Note
CodeCov is free for open-source repos while some enterprise-level features are not available.
https://about.codecov.io/pricing/
This PR does not enable coverage report on terminal (text reporter).
Because it is required to merge multiple coverage.
I will implement that in a separate PR if needed.
You can configure behavior in codecov.yml. Refer https://docs.codecov.com/docs/common-recipe-list#set-non-blocking-status-checks
The author should do the following, if applicable

[ ] Add tests
[ ] Run tests
[ ] bun run format:fix && bun run lint:fix to format the code
[ ] Add TSDoc/JSDoc to document the code

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:

@exoego
Awesome! I've never used CodeCov, but this seems so great! Let's go with it. Merge now, and then I'll set the CODECOV_TOKEN. Thank you!


InteractBlockEvent.Secondary bug with alex

I report a bug about the event InteractBlockEvent.Secondary, who is not active when you are alex.

?

When i try the event InteractBlockEvent.Secondary with an account with Alex skin, the event is not read.

Does this happen on the latest version? If so, post the version of Minecraft and Sponge that you're using.


Add initial set of configuration hints and sample for Spring Data REST

This PR adds the initial set of required hints to run a sample application using Spring Data REST and the HAL representation model.
http :8080/api/customers/1

{
    "_links": {
        "customer": {
            "href": "http://localhost:8080/api/customers/1{?projection}",
            "templated": true
        },
        "self": {
            "href": "http://localhost:8080/api/customers/1"
        }
    },
    "address": {
        "city": "Charlottesville",
        "state": "VA",
        "street": "4711 Some Place",
        "zipCode": "54321"
    },
    "firstname": "Dave",
    "lastname": "Matthews"
}

Along with Data REST specific hints the allowWrite attribute has been added to the FieldHint annotation (via ffdca18)
So far it is possible to expose the collection and entity endpoints. The search endpoint and others (like profile), as well as support for other media types and ALPS will be added subsequently moving forward.
We'll potentially require additional changes in Data REST (eg. to fully support the search endpoint as the parameter name for the @PathVariable is not resolved from the method parameter name) and will upgrade to a more recent version once the upcoming Spring Data RC is out.

The data-rest sample in there works for me. Thanks for implementing allowWrite I see you found my todo about supporting it when a use case came along :) I've pushed your commits (Hope that is OK??) and I further polished field descriptor handling, including implementing merging. I plan to do some more here to tidy things up further.

Since it has been merged I close this PR.
@christophstrobl Feel free to create other ones to refine or just push if that's straightforward.


Errors caused by R-version conflicts

Hi,
There seems to be some conflicts with the version of R and some packages, maybe only the package scales. The entire pipeline ran smoothly with the test data, but on my own data this error arose:
Mar-15 14:07:32.450 [Task monitor] ERROR nextflow.processor.TaskProcessor - Error executing process > 'MOSDEPT
H_AMPLICON_PLOT'

Caused by:
  Process `MOSDEPTH_AMPLICON_PLOT` terminated with an error exit status (1)

Command executed:

  plot_mosdepth_regions.r \
      --input_files SWIFT25213950.trim.mkD.amplicon.regions.bed.gz \
      --input_suffix .trim.mkD.amplicon.regions.bed.gz \
      --output_dir ./ \
      --output_suffix .trim.mkD.amplicon.regions

Command exit status:
  1

Command output:
  (empty)

Command error:
  package ‘scales’ was built under R version 3.6.3
  Loading required package: grid
  ========================================
  ComplexHeatmap version 2.2.0
  Bioconductor page: http://bioconductor.org/packages/ComplexHeatmap/
  Github page: https://github.com/jokergoo/ComplexHeatmap
  Documentation: http://jokergoo.github.io/ComplexHeatmap-reference

  If you use it in published research, please cite:
  Gu, Z. Complex heatmaps reveal patterns and correlations in multidimensional
    genomic data. Bioinformatics 2016.
  ========================================

  Loading required package: viridisLite

  Loading required package: viridisLite

  Attaching package: ‘viridis’

  The following object is masked from ‘package:scales’:

      viridis_pal

  Warning messages:
  1: package ‘viridis’ was built under R version 3.6.3
  2: package ‘viridisLite’ was built under R version 3.6.3
  ── Attaching packages ─────────────────────────────────────── tidyverse 1.3.0 ──
  ✔ tibble  3.0.1     ✔ dplyr   1.0.0
  ✔ tidyr   1.1.0     ✔ stringr 1.4.0
  ✔ readr   1.3.1     ✔ forcats 0.5.0
  ✔ purrr   0.3.4
  ── Conflicts ────────────────────────────────────────── tidyverse_conflicts() ──
  ✖ readr::col_factor() masks scales::col_factor()
  ✖ purrr::discard()    masks scales::discard()
  ✖ dplyr::filter()     masks stats::filter()
  ✖ dplyr::lag()        masks stats::lag()
  Warning messages:
  1: package ‘tidyverse’ was built under R version 3.6.3
  2: package ‘tibble’ was built under R version 3.6.3
  3: package ‘tidyr’ was built under R version 3.6.3
  4: package ‘readr’ was built under R version 3.6.3
  5: package ‘purrr’ was built under R version 3.6.3
  6: package ‘dplyr’ was built under R version 3.6.3
  7: package ‘stringr’ was built under R version 3.6.3
  8: package ‘forcats’ was built under R version 3.6.3
  Error:   Dimensions exceed 50 inches (height and width are specified in 'cm' not pixels).
    If you're sure you want a plot that big, use `limitsize = FALSE`.
  Backtrace:
      █
   1. └─ggplot2::ggsave(...)
   2.   └─ggplot2:::plot_dim(...)
  Execution halted

Apologies for the late response @jonbra ! Did you manage to get to the bottom of this?

We have been threatening to release v2.0 for a while now but hopefully soon 🤞🏽 If you haven't already be great if you can test with
nextflow pull nf-core/viralrecon
nextflow run nf-core/viralrecon ......... -r dev

Hello sorry to re-open this. Have encountered the similar issue. Please see the error message below -
ERROR ~ Error executing process > 'NFCORE_VIRALRECON:ILLUMINA:PLOT_MOSDEPTH_REGIONS_AMPLICON'
Caused by:
Process NFCORE_VIRALRECON:ILLUMINA:PLOT_MOSDEPTH_REGIONS_AMPLICON terminated with an error exit status (1)
Command executed:
plot_mosdepth_regions.r
--input_files cGMPSARS-CoV-2.regions.bed.gz
--output_dir ./
--output_suffix mosdepth
--input_suffix .regions.bed.gz
cat <<-END_VERSIONS > versions.yml
"NFCORE_VIRALRECON:ILLUMINA:PLOT_MOSDEPTH_REGIONS_AMPLICON":
r-base: $(echo $(R --version 2>&1) | sed 's/^.R version //; s/ .$//')
END_VERSIONS
Command exit status:
1
Command output:
(empty)
Command error:
Warning message:
package ‘optparse’ was built under R version 4.0.5
Warning message:
package ‘scales’ was built under R version 4.0.5
Loading required package: grid
Error: package or namespace load failed for ‘ComplexHeatmap’:
.onLoad failed in loadNamespace() for 'Cairo', details:
call: dyn.load(file, DLLpath = DLLpath, ...)
error: unable to load shared object '/root/work/conda/env-05a634cd6ec064941b9d92badb58aa6c/lib/R/library/Cairo/libs/Cairo.so':
libicuuc.so.70: cannot open shared object file: No such file or directory
Execution halted
Have updated my r-base in conda-forge, which is 4.3.3 instead of 4.0.5. Attempted with the following command -
conda install -c conda-forge r-base=4.0.5
That didn't work though...
Any input would be much appreciated! Thank you!


Unusable release on npm

The release doesn't contain any files, see<EMAIL_ADDRESS>Might be related to the recent name change https://github.com/webpack-contrib/babel-minify-webpack-plugin/issues/54.

Published 🎉

Thanks @boopathi.


how to use?

Hi, Can add an executable target to show sending emails every hour?

Hi there, I'm not 100% positive what's being asked here but if you're inquiring about whether or not it's possible to send an email every hour, then yes, that's definitely possible :)

Hello, is there a demo?
https://github.com/vapor/api-template/tree/kitchen-sink
Me run jobs
Email can be printed, but how to print it regularly?
I did not find the documentation.
Sorry, this may not be an issue.  But I look at the iOS library, they have demos, which is very convenient.

Right now there is no complete documentation as that will be published when it is tagged 1.0. The best reference is from the recent forum update: https://forums.swift.org/t/whats-new-in-vapor-4/31832

Okay thank you


Bug when compiling multiple files

The current Yatima.Compiler.CompileState.union function doesn't compute the resulting array of constants properly. It's not as simple as appending either, because some constants might be on both arrays. Also, there would be the need for reindexings in some constants after the merge.
In the end, it's debatable if we should even build this array at compilation time because it leaves us with two ways to build the array of constants, increasing the technical burden of maintainability and consistency across the codebase.

Here's an idea: we keep it for testing purposes but we commit to never relying on it for the official CLI

Oh no, it's even worse!
When compiling files A and B such that B imports A, some constants from A can potentially have expressions with different ConstIdxs in the resulting stores because the array of constants can be in a different order. And this will lead to a conflict when uniting the compile states.
The O(1) accesses for arrays are backfiring with these idx compatibility issues. We might want a map from Name to Const instead. Then we reference constants by names, like Lean 4 does

Nevermind. It works if the compilations are piped. Will mention it in the next PR for documentation


[FLINK-25249][connector/kafka] Reimplement KafkaTestEnvironment with KafkaContainer

What is the purpose of the change
This pull request uses KafkaContainer to rewrite the existing unstable KafkaTestEnvironment, which was previously based on in-memory Kafka.
Brief change log

Reimplement KafkaTestEnvironment with KafkaContainer

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

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

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@flinkbot run azure

@fapaul would you like to merge this PR? Thanks.

@JingGe I made a force push to fix conflict with master. Should be able to merge now.

@PatrickRen Unfortunately there are still some kafka test failures, the error messages also look pretty new to me so maybe it is related to your change.

I checked the latest CI failure and it is caused by Zookeeper session expiration processing create topic request. Actually the broker configuration zookeeper.session.timeout has been increased to 60000ms (1min) so I'm not sure if it is helpful to increase it to higher value again...

ERROR [Admin Manager on Broker 1]: Error processing create topic request CreatableTopic(name='runProduceConsumeMultipleTopics-2', numPartitions=3, replicationFactor=1, assignments=[], configs=[]) (kafka.server.ZkAdminManager)
org.apache.zookeeper.KeeperException$SessionExpiredException: KeeperErrorCode = Session expired for /brokers/topics/runProduceConsumeMultipleTopics-2
at org.apache.zookeeper.KeeperException.create(KeeperException.java:134)
at org.apache.zookeeper.KeeperException.create(KeeperException.java:54)
at kafka.zookeeper.AsyncResponse.resultException(ZooKeeperClient.scala:576)
at kafka.zk.KafkaZkClient.pathExists(KafkaZkClient.scala:1692)
at kafka.zk.KafkaZkClient.topicExists(KafkaZkClient.scala:482)
at kafka.zk.AdminZkClient.validateTopicCreate(AdminZkClient.scala:129)
at kafka.server.ZkAdminManager.$anonfun$createTopics$2(ZkAdminManager.scala:192)
at scala.collection.Iterator$$anon$9.next(Iterator.scala:575)
at scala.collection.immutable.List.prependedAll(List.scala:153)
at scala.collection.immutable.List$.from(List.scala:651)
at scala.collection.immutable.List$.from(List.scala:648)
at scala.collection.IterableFactory$Delegate.from(Factory.scala:288)
at scala.collection.immutable.Iterable$.from(Iterable.scala:35)
at scala.collection.immutable.Iterable$.from(Iterable.scala:32)
at scala.collection.IterableFactory$Delegate.from(Factory.scala:288)
at scala.collection.IterableOps.map(Iterable.scala:671)
at scala.collection.IterableOps.map$(Iterable.scala:671)
at scala.collection.AbstractIterable.map(Iterable.scala:919)
at kafka.server.ZkAdminManager.createTopics(ZkAdminManager.scala:156)
at kafka.server.KafkaApis.handleCreateTopicsRequest(KafkaApis.scala:1787)
at kafka.server.KafkaApis.$anonfun$handle$2(KafkaApis.scala:186)
at kafka.server.KafkaApis.$anonfun$handle$2$adapted(KafkaApis.scala:186)
at kafka.server.ZkSupport.maybeForward(MetadataSupport.scala:87)
at kafka.server.KafkaApis.handle(KafkaApis.scala:149)
at kafka.server.KafkaRequestHandler.run(KafkaRequestHandler.scala:74)
at java.base/java.lang.Thread.run(Thread.java:829)

I'd like to trigger the CI again and see if it could be reproduced.

@flinkbot run azure