HBASE-27321 The ReplicationLogCleaner is not thread safe but can be c…

…alled from different threads at the same time

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 39s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 22s
master passed

+1 :green_heart:
compile
0m 49s
master passed

+1 :green_heart:
shadedjars
4m  1s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 35s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 10s
the patch passed

+1 :green_heart:
compile
0m 49s
the patch passed

+1 :green_heart:
javac
0m 49s
the patch passed

+1 :green_heart:
shadedjars
4m  0s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 33s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 28s
hbase-common in the patch passed.

-1 :x:
unit
8m  7s
hbase-server in the patch failed.

27m 12s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4730

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux a73252d7b171 5.4.0-1081-aws #88~18.04.1-Ubuntu SMP Thu Jun 23 16:29:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 92cf962fee

Default Java
AdoptOpenJDK-1.8.0_282-b08

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/1/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/1/testReport/

Max. process+thread count
569 (vs. ulimit of 30000)

modules
C: hbase-common hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/1/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 43s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 28s
master passed

+1 :green_heart:
compile
2m 44s
master passed

+1 :green_heart:
checkstyle
0m 40s
master passed

+1 :green_heart:
spotless
0m 38s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 41s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 10s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m  8s
the patch passed

+1 :green_heart:
compile
2m 43s
the patch passed

+1 :green_heart:
javac
2m 43s
the patch passed

-0 :warning:
checkstyle
0m 28s
hbase-server: The patch generated 2 new + 0 unchanged - 0 fixed = 2 total (was 0)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
8m 13s
Patch does not cause any errors with Hadoop 3.2.4 3.3.4.

+1 :green_heart:
spotless
0m 37s
patch has no errors when running spotless:check.

-1 :x:
spotbugs
1m 22s
hbase-server generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

_ Other Tests _

+1 :green_heart:
asflicense
0m 15s
The patch does not generate ASF License warnings.

31m 14s

Reason
Tests

FindBugs
module:hbase-server

Inconsistent synchronization of org.apache.hadoop.hbase.master.cleaner.CleanerChore.future; locked 75% of time  Unsynchronized access at CleanerChore.java:75% of time  Unsynchronized access at CleanerChore.java:[line 244]

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4730

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux b9ebda4b963b 5.4.0-1081-aws #88~18.04.1-Ubuntu SMP Thu Jun 23 16:29:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 92cf962fee

Default Java
AdoptOpenJDK-1.8.0_282-b08

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

spotbugs
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/1/artifact/yetus-general-check/output/new-spotbugs-hbase-server.html

Max. process+thread count
64 (vs. ulimit of 30000)

modules
C: hbase-common hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/1/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
15m 24s
Docker mode activated.

-0 :warning:
yetus
0m  2s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 55s
master passed

+1 :green_heart:
compile
1m  6s
master passed

+1 :green_heart:
shadedjars
3m 52s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 45s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 36s
the patch passed

+1 :green_heart:
compile
1m  5s
the patch passed

+1 :green_heart:
javac
1m  5s
the patch passed

+1 :green_heart:
shadedjars
3m 46s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 43s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
2m  6s
hbase-common in the patch passed.

+1 :green_heart:
unit
211m 40s
hbase-server in the patch passed.

248m 42s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4730

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux ccb2d0d7c9a5 5.4.0-122-generic #138-Ubuntu SMP Wed Jun 22 15:00:31 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 92cf962fee

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/1/testReport/

Max. process+thread count
2606 (vs. ulimit of 30000)

modules
C: hbase-common hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/1/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 41s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 10s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 14s
master passed

+1 :green_heart:
compile
2m 44s
master passed

+1 :green_heart:
checkstyle
0m 38s
master passed

+1 :green_heart:
spotless
0m 36s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 38s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 10s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 10s
the patch passed

+1 :green_heart:
compile
2m 43s
the patch passed

+1 :green_heart:
javac
2m 43s
the patch passed

-0 :warning:
checkstyle
0m 27s
hbase-server: The patch generated 2 new + 0 unchanged - 0 fixed = 2 total (was 0)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
8m  9s
Patch does not cause any errors with Hadoop 3.2.4 3.3.4.

+1 :green_heart:
spotless
0m 36s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 52s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 14s
The patch does not generate ASF License warnings.

30m 43s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4730

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 0adc25fe84e6 5.4.0-1081-aws #88~18.04.1-Ubuntu SMP Thu Jun 23 16:29:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 92cf962fee

Default Java
AdoptOpenJDK-1.8.0_282-b08

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/2/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
64 (vs. ulimit of 30000)

modules
C: hbase-common hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/2/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 13s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 48s
master passed

+1 :green_heart:
compile
1m  7s
master passed

+1 :green_heart:
shadedjars
3m 52s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 45s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 38s
the patch passed

+1 :green_heart:
compile
1m  6s
the patch passed

+1 :green_heart:
javac
1m  6s
the patch passed

+1 :green_heart:
shadedjars
3m 50s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 43s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
2m  8s
hbase-common in the patch passed.

+1 :green_heart:
unit
210m 43s
hbase-server in the patch passed.

233m 13s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4730

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 1fc67bbf67a0 5.4.0-122-generic #138-Ubuntu SMP Wed Jun 22 15:00:31 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 92cf962fee

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/2/testReport/

Max. process+thread count
2647 (vs. ulimit of 30000)

modules
C: hbase-common hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/2/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 14s
Docker mode activated.

-0 :warning:
yetus
0m  2s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 25s
master passed

+1 :green_heart:
compile
0m 59s
master passed

+1 :green_heart:
shadedjars
3m 45s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 41s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 15s
the patch passed

+1 :green_heart:
compile
0m 56s
the patch passed

+1 :green_heart:
javac
0m 56s
the patch passed

+1 :green_heart:
shadedjars
3m 51s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 39s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 44s
hbase-common in the patch passed.

+1 :green_heart:
unit
215m 31s
hbase-server in the patch passed.

236m 34s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/2/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4730

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 8f6a161e4d69 5.4.0-124-generic #140-Ubuntu SMP Thu Aug 4 02:23:37 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 92cf962fee

Default Java
AdoptOpenJDK-1.8.0_282-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/2/testReport/

Max. process+thread count
2457 (vs. ulimit of 30000)

modules
C: hbase-common hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/2/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 41s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m  9s
master passed

+1 :green_heart:
compile
2m 41s
master passed

+1 :green_heart:
checkstyle
0m 37s
master passed

+1 :green_heart:
spotless
0m 35s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 35s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m  7s
the patch passed

+1 :green_heart:
compile
2m 39s
the patch passed

+1 :green_heart:
javac
2m 39s
the patch passed

+1 :green_heart:
checkstyle
0m 38s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
8m  0s
Patch does not cause any errors with Hadoop 3.2.4 3.3.4.

+1 :green_heart:
spotless
0m 35s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 48s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 14s
The patch does not generate ASF License warnings.

29m 53s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/3/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4730

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 7ba945e26335 5.4.0-1081-aws #88~18.04.1-Ubuntu SMP Thu Jun 23 16:29:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 92cf962fee

Default Java
AdoptOpenJDK-1.8.0_282-b08

Max. process+thread count
60 (vs. ulimit of 30000)

modules
C: hbase-common hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/3/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 43s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m  9s
master passed

+1 :green_heart:
compile
1m 12s
master passed

+1 :green_heart:
shadedjars
4m 22s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 43s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m  6s
the patch passed

+1 :green_heart:
compile
1m  5s
the patch passed

+1 :green_heart:
javac
1m  5s
the patch passed

+1 :green_heart:
shadedjars
4m 15s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 41s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
2m  4s
hbase-common in the patch passed.

-1 :x:
unit
11m 47s
hbase-server in the patch failed.

34m 36s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4730

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux eeedf37c26ce 5.4.0-1083-aws #90~18.04.1-Ubuntu SMP Fri Aug 5 08:12:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 92cf962fee

Default Java
AdoptOpenJDK-11.0.10+9

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/3/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/3/testReport/

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

modules
C: hbase-common hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/3/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 38s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 10s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 10s
master passed

+1 :green_heart:
compile
0m 49s
master passed

+1 :green_heart:
shadedjars
4m 15s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 39s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 54s
the patch passed

+1 :green_heart:
compile
1m 16s
the patch passed

+1 :green_heart:
javac
1m 16s
the patch passed

+1 :green_heart:
shadedjars
5m  4s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 54s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 49s
hbase-common in the patch passed.

-1 :x:
unit
230m  4s
hbase-server in the patch failed.

253m 10s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/3/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4730

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 4c3ae827b330 5.4.0-1081-aws #88~18.04.1-Ubuntu SMP Thu Jun 23 16:29:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 92cf962fee

Default Java
AdoptOpenJDK-1.8.0_282-b08

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/3/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/3/testReport/

Max. process+thread count
2646 (vs. ulimit of 30000)

modules
C: hbase-common hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/3/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

Ah, let me check the TestCleanerChore.

2022-08-25T20:03:33,978 WARN  [hfile_cleaner-dir-scan-pool-1] cleaner.CleanerChore(411): Attempted to delete:file:/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-4730/yetus-jdk11-hadoop3-check/src/hbase-server/target/test-data/9bca84d1-7e68-2548-36e6-a8726d0c142c/child/file, but couldn't. Run cleaner chain and attempt to delete on next pass.

Strange...

2022-08-25T20:03:33,977 DEBUG [cleaner.Chore.1] hbase.ScheduledChore(165): test-retry-ioe execution time: 22 ms.
2022-08-25T20:03:33,978 WARN  [hfile_cleaner-dir-scan-pool-1] cleaner.CleanerChore(411): Attempted to delete:file:/home/jenkins/jenkins-home/workspace/Base-PreCommit-GitHub-PR_PR-4730/yetus-jdk11-hadoop3-check/src/hbase-server/target/test-data/9bca84d1-7e68-2548-36e6-a8726d0c142c/child/file, but couldn't. Run cleaner chain and attempt to delete on next pass.
2022-08-25T20:03:33,979 DEBUG [cleaner.Chore.2] hbase.ScheduledChore(165): test-retry-ioe execution time: 32 ms.

OK, seems we execute the chore at the same time concurrently in different chore thread. Let me dig more on how could this happen.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 43s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 18s
master passed

+1 :green_heart:
compile
3m 36s
master passed

+1 :green_heart:
checkstyle
1m  0s
master passed

+1 :green_heart:
spotless
0m 54s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 23s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 10s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m  6s
the patch passed

+1 :green_heart:
compile
4m 11s
the patch passed

+1 :green_heart:
javac
4m 11s
the patch passed

+1 :green_heart:
checkstyle
0m 55s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
10m 27s
Patch does not cause any errors with Hadoop 3.2.4 3.3.4.

+1 :green_heart:
spotless
0m 43s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 17s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 19s
The patch does not generate ASF License warnings.

42m 17s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/4/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4730

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 29fe1d8233d0 5.4.0-1081-aws #88~18.04.1-Ubuntu SMP Thu Jun 23 16:29:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 92cf962fee

Default Java
AdoptOpenJDK-1.8.0_282-b08

Max. process+thread count
60 (vs. ulimit of 30000)

modules
C: hbase-common hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/4/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  4s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 38s
master passed

+1 :green_heart:
compile
1m  5s
master passed

+1 :green_heart:
shadedjars
3m 48s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 44s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 34s
the patch passed

+1 :green_heart:
compile
1m  6s
the patch passed

+1 :green_heart:
javac
1m  6s
the patch passed

+1 :green_heart:
shadedjars
3m 50s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 43s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
2m  7s
hbase-common in the patch passed.

+1 :green_heart:
unit
217m  7s
hbase-server in the patch passed.

239m 11s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/4/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4730

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux e8dab7eaaa97 5.4.0-122-generic #138-Ubuntu SMP Wed Jun 22 15:00:31 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 92cf962fee

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/4/testReport/

Max. process+thread count
2724 (vs. ulimit of 30000)

modules
C: hbase-common hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/4/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 12s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 46s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 44s
master passed

+1 :green_heart:
compile
0m 51s
master passed

+1 :green_heart:
shadedjars
4m 39s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 40s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 56s
the patch passed

+1 :green_heart:
compile
1m 13s
the patch passed

+1 :green_heart:
javac
1m 13s
the patch passed

+1 :green_heart:
shadedjars
5m  0s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 44s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 45s
hbase-common in the patch passed.

+1 :green_heart:
unit
221m  5s
hbase-server in the patch passed.

245m 26s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/4/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4730

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 7c23709f1b83 5.4.0-1081-aws #88~18.04.1-Ubuntu SMP Thu Jun 23 16:29:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 92cf962fee

Default Java
AdoptOpenJDK-1.8.0_282-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/4/testReport/

Max. process+thread count
2601 (vs. ulimit of 30000)

modules
C: hbase-common hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4730/4/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.


Update in driver.py to make ts_avg_window Optional, works for both ts_avg_window specified in yaml or not

Earlier ts_avg_window was needed in 'timeseries' plot type (e.g., 'H' or 'D' for hourly or daily averages), and didn't work with None specified to ts_avg_window.
This would be more useful for aircraft evaluations (looking at timeseries with altitude profile data, without the need of time window averaging)

I'll see if I can fix the CI tomorrow.

@quaz115 I was able to fix the CI in #184 so if you merge upstream develop branch to your develop branch it should work properly now.

@quaz115 I was able to fix the CI in #184 so if you merge upstream develop branch to your develop branch it should work properly now.

@zmoon Done, all 4 tests passed now

@quaz115 I was able to fix the CI in #184 so if you merge upstream develop branch to your develop branch it should work properly now.

@zmoon Done, all 4 tests passed now

@zmoon @rschwant is this ready to be merged to https://github.com/NOAA-CSL/MELODIES-MONET/tree/develop branch now

@quaz115 I think we should give @rschwant a bit more chance to take a look since she is the lord of control file options and their documentation.


HV-1408 Add small usage tests for each HV annotation

https://hibernate.atlassian.net/browse/HV-1408

Thanks @gunnarmorling, just got to this. It's strange that headers are missing as I remember adding them (at least I think I do:) ).
As for the removed tests - I actually just moved them between packages. As for the tests themselves - I tried to make them as simple as possible to just test positive/negative scenario to make sure that all implemented validators are picked up.
I was also thinking to maybe rewrite the country specific constraints tests - to have a test for the validator and in the tests of this new package just do a simple verification that annotations work. WDYT?

I was also thinking to maybe rewrite the country specific constraints tests - to have a test for the validator and in the tests of this new package just do a simple verification that annotations work. WDYT?

I don't think it's worth it.
Btw, I removed the package-info file as I don't think it's time well spent to add them for the tests. Let's only add them for the main packages.
Merged. Thanks!


Suspend/resume a running VM

We should be able to suspend a running CKB VM, save the states somewhere, and resume the previously running VM at a latter time, or even on a different machine. One potential design here might be:

A signal is sent from another thread to CKB VM to start suspending
CKB VM will pack the current register states, as well as any dirty memory pages in a packed data structure. Notice we can easily exclude the following memory pages from dirty memory page list:

Page with all zeros as the data
All executable pages, since they must come from some binaries
Writable pages coming from an ELF, but hasn't been modified in any way.

Then the packed data structure can be restored elsewhere into a running VM instance that is exactly the same as what it is before suspending. Execution can then continue from there.

In the above design, the ELF binary needs to be reloaded again when the VM is resumed. Have you considered just dumping the entire memory? there may be better performance.

I was under the impression that the ELF binary will be available elsewhere(for example: in CKB this will be in a cell). Dumping the entire memory might result in much bigger memory consumption. Consider the fact that it is typically long running programs that would require suspend/resume, I would bet that loading the binary again is a acceptable tradeoff to reduce load on memory & (possibly) disk requirements.

One additional idea from @doitian: instead of using a signal, we can simply allow suspending when the available cycles are all consumed. That will suit CKB's use case much better.


[Missing SNMP Polling Profile] Brocade ICX6450-48P-HPOE

Device Vendor: Brocade
Device Model: ICX6450-48P-HPOE
System Object Identifier (SysOID): .<IP_ADDRESS>.4.1.19<IP_ADDRESS>.<IP_ADDRESS>
List of critical metrics that you expect in the profile (does not need to be all-inclusive, just a general idea of your expectations):

All performance and interface metrics

Gist Link: https://gist.github.com/ASchneider-GitHub/02e9da48fa42ee492d78a25438f3f87e

Low priority project. Missing this Brocade model from existing profile.


Error extracting a lib on Ubuntu

When the pip3 install aqtinstall==0.7.1 command is run, sometimes we get the following error:
2020-02-18 23:37:53,175 - aqt - INFO - -Extracting qtremoteobjects-Linux-RHEL_7_4-GCC-Linux-RHEL_7_4-X86_64.7z...
Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.7.6/x64/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/opt/hostedtoolcache/Python/3.7.6/x64/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/opt/hostedtoolcache/Python/3.7.6/x64/lib/python3.7/site-packages/aqt/__main__.py", line 28, in <module>
    sys.exit(main())
  File "/opt/hostedtoolcache/Python/3.7.6/x64/lib/python3.7/site-packages/aqt/__init__.py", line 38, in main
    return cli.run()
  File "/opt/hostedtoolcache/Python/3.7.6/x64/lib/python3.7/site-packages/aqt/cli.py", line 218, in run
args.func(args)
  File "/opt/hostedtoolcache/Python/3.7.6/x64/lib/python3.7/site-packages/aqt/cli.py", line 122, in run_install
    logging=self.logger).install(command=sevenzip, target_dir=output_dir)
  File "/opt/hostedtoolcache/Python/3.7.6/x64/lib/python3.7/site-packages/aqt/installer.py", line 94, in install
    ret_arr = p.map(functools.partial(self.retrieve_archive, command=command, path=base_dir), archives)
  File "/opt/hostedtoolcache/Python/3.7.6/x64/lib/python3.7/multiprocessing/pool.py", line 268, in map
    return self._map_async(func, iterable, mapstar, chunksize).get()
  File "/opt/hostedtoolcache/Python/3.7.6/x64/lib/python3.7/multiprocessing/pool.py", line 657, in get
    raise self._value
  File "/opt/hostedtoolcache/Python/3.7.6/x64/lib/python3.7/multiprocessing/pool.py", line 121, in worker
    result = (True, func(*args, **kwds))
  File "/opt/hostedtoolcache/Python/3.7.6/x64/lib/python3.7/multiprocessing/pool.py", line 44, in mapstar
    return list(map(*args))
  File "/opt/hostedtoolcache/Python/3.7.6/x64/lib/python3.7/site-packages/aqt/installer.py", line 83, in retrieve_archive
    os.unlink(archive)
FileNotFoundError: [Errno 2] No such file or directory: 'qtscxml-Linux-RHEL_7_4-GCC-Linux-RHEL_7_4-X86_64.7z'

It didn't happen before, so is it related to aqtinstall? Thanks in advance for your help! :)

Could you try with aqtinstall == 0.7.3?

v0.7.4 is released. Any help?

Thanks @miurahr! It seems to work now! :)


exclude "counter" images from cache description

There are some well known domains for creating counter images in cache descriptions so that you can see how many people had a look at this cache already or similar things. I'd like to automatically skip those images during parsing because they have absolutely no value for the caching experience and I more often than not find that those images can not be correctly loaded in c:geo because the server is unreachable or whatever.
For implementation of this I would create a blacklist of URI parts and if an image matches an entry of that blacklist, it is not added to the images list of the cache in c:geo.

@Bananeweizen: ok to close?

Yes, this was mainly left open because of your concerns regarding a setting for that feature.


ReferenceError: window is not defined

I am facing issue "ReferenceError: window is not defined" using leaflet with nodeJs in as:
c:\Projects\Leaflet\node_modules\leaflet\dist\leaflet-src.js:9180
}(window, document));
^
ReferenceError: window is not defined
at Object. (c:\Projects\Leaflet\node_modules\leaflet\dist\leaflet-src.js:9180:3)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (c:\Projects\Leaflet\app.js:7:9)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)

Based on your backtrace it looks like you're trying to use it in node or some other non-browser environment, which isn't going to work. Leaflet is a browser library.


Dashboard, supports cloning across business groups, refer to the cloning interaction of the built-in dashboard

v7 版本已支持


Dropdowns drop under element

❗ please do not add sensitive information in issues, you can provide extra information via email using issue number as reference ❗
Describe the issue

Reporter
Please state your name. If we don't know who is reporting, a solution of the issue might be delayed.

To Reproduce
Steps to reproduce the behavior:

Go to (https://frank4example.frankframework.org/iaf/gui/#!/logging/settings)
Open the Level dropdown for the last element in either Log Definitions or Loggers
See menu not being completely visible

Screenshots
If applicable, add screenshots to help explain your problem.
Configuration
Please provide the configuration of the Pipe or Receiver with the problem.

Input
Please provide an example of the input message.
Alternatively, provide a Ladybug report.

Environment
FF! 7.8-20220311.171822: Ibis4Example
Running on ae0c43ffe608 using Apache Tomcat/8.5.60
Java Version: OpenJDK Runtime Environment (1.8.0_275-b01)
Heap size: 1330M, total JVM memory: 1910M
Free disk space: 11GB, total disk space: 50GB
Up since: 2022-03-11 17:44:20 (3d)

Additional Environment

DBMS: [e.g. Oracle, MSSQL, MariaDB, MySql, PostgreSQL]
Browser: [e.g. Chrome, Safari, Edge, Firefox]

Additional Context
Add any other context about the problem here. (f.e. ladybug report / test adapter with larva test)

Work around is to scroll down, but yes, this is clumsy.


NPM load issue

From console
./node_modules/srt-support-for-html5-videos/src/track.js 20:5
Module parse failed: Unexpected token (20:5)
File was processed with these loaders:

./node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
|    * @type {string}
|    */

src;
|   /**
|    * @readonly

From Chrome
main.js:12 Uncaught Error: Module parse failed: Unexpected token (22:8)
File was processed with these loaders:

./node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
|    * @type {number}
|    */

number;
|
|   /**
at ./node_modules/srt-support-for-html5-videos/src/cue.js (main.js:12:1)
at webpack_require (bootstrap:856:1)
at fn (bootstrap:150:1)
at ./node_modules/srt-support-for-html5-videos/src/helpers.js (helpers.js:1:1)
at webpack_require (bootstrap:856:1)
at fn (bootstrap:150:1)
at ./node_modules/srt-support-for-html5-videos/main.js (main.js:1:1)
at webpack_require (bootstrap:856:1)
at fn (bootstrap:150:1)
at Module. (index.css?ee34:82:1)
at ./src/slate-transcript-editor/src/components/index.js (index.js:805:1)
at webpack_require (bootstrap:856:1)
at fn (bootstrap:150:1)
at Module. (index.js:28:1)
at ./src/slate-transcript-editor/src/index.js (index.js:11:1)
at webpack_require (bootstrap:856:1)
at fn (bootstrap:150:1)
at Module. (index.css?bb0a:82:1)
at ./src/index.js (index.js:298:1)
at webpack_require (bootstrap:856:1)
at fn (bootstrap:150:1)
at 1 (timecodeToSeconds.js:34:1)
at webpack_require (bootstrap:856:1)
at checkDeferredModules (bootstrap:45:1)
at Array.webpackJsonpCallback [as push] (bootstrap:32:1)
at main.chunk.js:1:63

I will look into this issue

Do you have steps on how to reproduce this error? For example a github project where the error occurs?

Not responding, closing


remove remains of label col

Closes #1176

Coverage remained the same at 82.199% when pulling fc1d2e6ab7d9fa088912074f50dafb8e9cfd7e73 on na3d:remove-label-col into da451df13aa93c3d86ab2705a23aa42bf62b2dac on linode:master.

Coverage remained the same at 82.199% when pulling dc420dbe46b6b0687b4a77bc518e90046e67b548 on na3d:remove-label-col into da451df13aa93c3d86ab2705a23aa42bf62b2dac on linode:master.

Coverage remained the same at 82.199% when pulling ee2bb7b6162f5bdd8819867ad5d690424a733e53 on na3d:remove-label-col into da451df13aa93c3d86ab2705a23aa42bf62b2dac on linode:master.

At this point I'd just drop all changes to EditConfigPage. @abemassry should have sorted that page out.

Just checked, all references to label-col have been removed from the EditConfigPage

Coverage remained the same at 81.985% when pulling 3229b1f6030fb8368e029c7c11837060ac0de9b3 on na3d:remove-label-col into 008389b79fa33970e4badd0baa093d4970b1556d on linode:master.


LEDs will not light up with this script. MQTT works, Circuit tested with another script and works

Spent a few days trying to get this to work. I'm having strange issues with this, managed to get to the stage where the HA showing the switch, colour selection and effects. Problem is LED's aren't switching on at all. I've checked my data pin and it's correct. My MQTT works and shows the requests from HA in Ardunio IDE serial monitor. I flashed my nodemcu with the neopixel strandtest code, as a test and the LED's work. Not entirely sure what is going on. Any help is much appreciated! Thanks

Hi Hazoomeh, I had the same issue and did the same tests. But the issue was that I thought I bought WS2811 and I bought WS2812 so after I change the chipset to WS2812 it works perfect, maybe you are facing same issue :)

WS2812 or WS2811 wich one is correct ?

For me the correct one was WS2812


Add DNS servers to vm definition

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
What type of PR is this?

Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:

Documentation:

Closed in favor of #19


Update variable elimination web app link with archived version

The link in the notes was broken for me but the archive.org version seems to still be running

Thanks, Daniel!


consider querying and updating inspector view with running other thread

See
http://answers.unity3d.com/questions/305882/how-do-i-invoke-functions-on-the-main-thread.html
Also can be accessed on here: https://gist.github.com/kimsama/a0cf529f5e9f97bfa5a0

It does not seem to be needed at the moment.


[AMBARI-24619] Horizontal scroll bar on assign slaves and clients page is not convenient for deploy with numerous hosts

What changes were proposed in this pull request?
It is not convenient to configure slaves and clients for deploy with numerous hosts because horizontal scroll bar is placed in the bottom of hosts list.
How was this patch tested?
Tested manually

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3908/
Test PASSed.


Generated assets/js/base.js is shadowing the Docsy file of the same name

I don't think that this is what we want.

Closed by #776


Secrets manager deleted before SecretInjector processed.

Describe the bug
Educates training platform package creates educates-registry-credentials SecretInjector resource. The SecretInjector resource has a finalizer added by the secrets-manager operator. When deleting Educates, if the operator is deleted before the instance of SecretInjector, then deletion of the package will get stuck as finalizer can't be removed.
To avoid problems kapp delete ordering rules should be set up using annotations to ensure that any SecretInjector instances created with the training platform package are deleted before secrets-manager operator is deleted.
Related issue: https://github.com/vmware-tanzu-labs/educates-training-platform/issues/208
Additional information
No response

kapp docs state:

kapp includes builtin rules to make sure certain changes are applied in particular order:
Creates/updates
CRDs are created/updated before custom resources
Namespaces are created/updated before namespaced resources
Pod related resources (ServiceAccount, ConfigMap, Secret, etc.) are created/updated before other resources (v0.25.0+)
RBAC related resources (Role, RoleBinding, etc.) are created/updated before other resources (v0.25.0+)
Deletions (below is order as of v0.29.0+)
Custom resources are deleted first
CRDs are deleted next
Rest of resoures are deleted

So technically the default order should result in custom resources being deleted first and before the operator would be deleted. So adding an explicit rule should not actually be required.

Note that there will be an issue with stuck resources when deleting Educates package if issue described in https://github.com/vmware-tanzu-labs/educates-training-platform/issues/202 occurs as the operator will not be running properly to clean up instances of secrets-manager resources. Thus deletion of Educates package will hang.


Challenge 3 solution

Solution to IBM Quantum Challenge Fall 2021 Challenge 3.

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


Updated Tutorial video to include locating save files

Created a video walk through to show how to access Elden ring save files for base game and modded version of the game.

Thank you very much for your tutorial


UpdateInstalled Event should fire, after the reload

The UpdateInstalled event fires directly after the update and not after your reload. I can do nothing with an event, that fires directly before a reload happens. Because i could never be shure if my code did rung through successfully.
So the UpdateInstalled event should fire after the reload.

Yes, you probably right about that.

Cool that you are still working on this project, you are my last hope ;)
So thank you very much!

Thank you for your feedback!

It's a great plugin,
I just have one question, is it possible to restart app automatically and apply the new code.
Because it seems I need to restart app 2 times before seeing changes (I did changes in some html template)
Or am I using this wrong.

@dongdh I moved your question to the separate issue, since it doesn't relate to this one.


Aborting a cross-domain request

Is it possible with easyXDM (specifically the CORS implementation) to abort a request?
The default CORS implementation doesn't seem to return the request, but even if it does, I think that XDM internally doesn't (or maybe it is even illegal to do due to iframes).

You are free to extend the interface used by cors.html to include an abort method.


python310Packages.docformatter: 1.5.0 -> 1.5.1

~This breaks xsdata: https://github.com/tefra/xsdata/issues/728~
Description of changes
https://github.com/PyCQA/docformatter/blob/v1.5.1/CHANGELOG.md

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 206890 run on x86_64-linux 1

5 packages built:

dmarc-metrics-exporter
python310Packages.docformatter
python310Packages.xsdata
python311Packages.docformatter
python311Packages.xsdata

@ofborg eval


NTR: G-quadruplex unwinding activity

Please provide as much information as you can:

Suggested term label:

G-quadroplex unwinding activity

Definition:

Unwinding G-quadruplex structures in nucleic acids, DNA or RNA.

Reference, in format PMID:#######
PMID:26883636
PMID:1324186
PMID:34113828

Gene product name and ID to be annotated to this term
Pif1
DHX36
RPA1

Parent term(s)
GO:0140640 catalytic activity, acting on a nucleic acid

Children terms (if applicable) Should any existing terms that should be moved underneath this new proposed term?

Synonyms (please specify, EXACT, BROAD, NARROW or RELATED)
G4 unwinding activity (EXACT)
G-quadruplex resolving activity (EXACT)

Cross-references

For enzymes, please provide RHEA and/or EC numbers.

Can also provide MetaCyc, KEGG, Wikipedia, and other links.

Any other information

https://github.com/geneontology/go-annotation/issues/5540
@ValWood Is this good? RPA1 seems to break the typical helicase classification.

add definition gloss " A DNA quadruplex (or G-quadruplex), is a specialized structure formed in DNA/RNA when sequences rich in guanine (G) assemble into a unique four-stranded arrangement."

Sounds good. Good point that  it isn't a helix!

+[Term]
+id: GO:0160225
+name: G-quadruplex unwinding activity
+namespace: molecular_function
+def: "Unwinding G-quadruplex structures in nucleic acids. A G-quadruplex is a specialized structure formed in DNA/RNA when sequences rich in guanine (G) assemble into a unique four-stranded arrangement." [PMID:1324186, PMID:26883636, PMID:34113828]
+synonym: "G-quadruplex resolving activity" EXACT []
+synonym: "G4 unwinding activity" EXACT []
+is_a: GO:0140640 ! catalytic activity, acting on a nucleic acid
+property_value: term_tracker_item "https://github.com/geneontology/go-ontology/issues/29309" xsd:anyURI
+created_by: rynl
+creation_date: 2024-12-04T00:07:15Z

https://github.com/geneontology/go-ontology/issues/29153


Speed up travis runtime.

Vast majority of time is in bundle install, and the vast majority of
that is installing nokogiri. Parallelize bundle install, and use system
libraries for nokogiri installation.

Thank you!


Feature header responsiveness

[x] Incorporating custom screen configurations to optimize the layout for smaller devices.
[x] Improving the header logo's responsiveness.
Fixed header:

@vsmedeiros Hi! Can you make that "קורסים" and "העלאת שאלה" buttons will become a Hamburger menu bar flat icon on small screen?

like in this project:
https://zeon.studio/preview?project=nextplate
https://github.com/zeon-studio/nextplate/blob/main/src/layouts/partials/Header.tsx

@vsmedeiros Thanks!
By the way, do you know how to fix that if the user navigating between pages using Link component,
close the drop down?
In other words, set the value "isDropdownOpen" to false when navigating between routes?

@vsmedeiros Thanks! By the way, do you know how to fix that if the user navigating between pages using Link component, close the drop down? In other words, set the value "isDropdownOpen" to false when navigating between routes?

@noams24 You're welcome! I'll aim to address this functionality later.

Amazing work!

Pleased to make a contribution!


[TEST] Introduce Negative Testing

What's the test to develop? Please describe
Test Longhorn functionality with involuntary factors
Longhorn functionalities

volume-related operations (rebuild, purge, snapshot, backup restore, DR, clone, etc)
backing-image-related operations (ex: backing image CRUD, cross-nodes sync)
Longhorn system operations (ex: system backup & restore, recurring jobs, orphan clean, etc)

Involuntary factors

host-related (ex: break volume/snapshot files or metafiles, network partition, node down, disk space outage, etc)
K8s related (ex: kubelet down, CSI components impact, etc)

Describe the items of the test development (DoD, definition of done) you'd like

Please use a task list for items on a separate line with a clickable checkbox https://docs.github.com/en/issues/tracking-your-work-with-issues/about-task-lists

[ ] Create negative test cases via robot and add them to the longhorn-tests repo
[ ] Execute the negative test cases by phases, and create corresponding bugs
[ ] Automate the negative test cases by phases.

[ ] Phase 1 - Automate the existing node disruption test cases
[ ] Phase 2 - Automate stress on the Longhorn system with repeated tasks and concurrent operations of purging/deletion
[ ] Phase 3 - Combination of test cases from phase1 & phase 2

Additional context
cc @longhorn/qa

@khushboo-rancher feel free to update this task description, so we can plan it accordingly.
cc @longhorn/qa

Moved this from 1.5.0, but follow this on QA board instead.

The current status is @yangchiu is working on the framework part with some example test case implementation. When they are ready and get merged, we will start the remaining case implementation based on priority.
cc @nitendra-suse @chriscchien @roger-ryao @khushboo-rancher

@yangchiu I feel the description of this issue is outdated. Please help keep this up-to-date and refer the related issues to this EPIC.
If need a separate epic, go ahead to create it.
cc @khushboo-rancher

@yangchiu remember to update the description of this ticket, as discussed.

@yangchiu remember to update the description of this ticket, as discussed.

I find I've updated it before. Read through the ticket description, I think it's quite clear, and the newly created ticket https://github.com/longhorn/longhorn/issues/7211 is also recorded.

Great. Thanks.

https://github.com/longhorn/longhorn/issues/6499
https://github.com/longhorn/longhorn/issues/6704
https://github.com/longhorn/longhorn/issues/6705
https://github.com/longhorn/longhorn/issues/6706
https://github.com/longhorn/longhorn/issues/6707
https://github.com/longhorn/longhorn/issues/6708


data/ecam-table-taxa.tsv is relativae abundance?

Hi,
Thanks for the development of this grateful DA analysis tool!
I just found that the demo data (data/ecam-table-taxa.tsv) that been passed to the feature_table_pre_process script was a relative abundance table.  Thanks!
Best wishes!

Hi @BinhongLiu,
Thank you for using ANCOM!
You are right, the ecam dataset (ecam-table-taxa.tsv)) is not a good example. This dataset contains relative abundance data rather than absolute abundance data. We use this dataset anyway just for a demonstration purpose, however, we switch to a better example dataset once ANCOM is submitted to Bioconductor.
Meanwhile, we still recommend you use "absolute abundance table, and do not transform it to relative abundance table (where the column totals are equal to 1)" while analyzing your own data.
Best,
Huang


[DRAFT][FLINK-32632][test] Fixes Minikube/cri-dockerd issue

What is the purpose of the change
Looking at the error message error: Internal error occurred: error executing command in container: http: invalid Host header pointed to several issues that indicated that the actual problem appears when building cri-dockerd with go-lang 1.20.6 (e.g. https://github.com/moby/moby/issues/45935 or https://github.com/kubernetes/minikube/issues/16909).
Brief change log
Instead of building cri-dockerd manually, we can rely on the binaries which are provided on github.
Verifying this change

Run Kubernetes test succeeds again.
Verification that go 1.20.6 was installed in the CI machine

Does this pull request potentially affect one of the following parts:

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

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

Initially, I tried to download the debian package. But there, I ran into problems with the corresponding dependencies (I installed the required containerd dependency. But this one required runC which couldn't be resolved by apt).

The fixes worked in this CI build:
Jul 22 09:52:18 Preparing to unpack .../conntrack_1%3a1.4.5-2_amd64.deb ...
Jul 22 09:52:18 Unpacking conntrack (1:1.4.5-2) ...
Jul 22 09:52:18 Setting up conntrack (1:1.4.5-2) ...
Jul 22 09:52:18 Processing triggers for man-db (2.9.1-1) ...
2023-07-22 09:52:20 URL:https://objects.githubusercontent.com/github-production-release-asset-2e65be/80172100/7186c302-3766-4ed5-920a-f85c9d6334ac?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20230722%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230722T095038Z&X-Amz-Expires=300&X-Amz-Signature=303c32e959498b92632316af16b5f885c7084357e0640f5b0262e6a8335fbc85&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=80172100&response-content-disposition=attachment%3B%20filename%3Dcrictl-v1.24.2-linux-amd64.tar.gz&response-content-type=application%2Foctet-stream [14553934/14553934] -> "crictl-v1.24.2-linux-amd64.tar.gz" [1]
Jul 22 09:52:20 crictl
+ local CRI_DOCKERD_VERSION=0.2.3
+ local CRI_DOCKERD_BIN=cri-dockerd-0.2.3.amd64.tgz
+ wget -nv https://github.com/Mirantis/cri-dockerd/releases/download/v0.2.3/cri-dockerd-0.2.3.amd64.tgz
2023-07-22 09:52:20 URL:https://objects.githubusercontent.com/github-production-release-asset-2e65be/318491505/e304ee45-ccad-4438-bc2c-039c8f6755d1?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20230722%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230722T095039Z&X-Amz-Expires=300&X-Amz-Signature=902a67ea6c321d1860c4e7840bec24ed1169cbd5a72b4dddcaabf8e8fee2ec9d&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=318491505&response-content-disposition=attachment%3B%20filename%3Dcri-dockerd-0.2.3.amd64.tgz&response-content-type=application%2Foctet-stream [23042323/23042323] -> "cri-dockerd-0.2.3.amd64.tgz" [1]
+ local BIN_NAME=cri-dockerd
+ sudo tar xzvf cri-dockerd-0.2.3.amd64.tgz cri-dockerd/cri-dockerd
Jul 22 09:52:20 cri-dockerd/cri-dockerd
+ sudo install -o root -g root -m 0755 cri-dockerd/cri-dockerd /usr/local/bin/cri-dockerd
+ wget -nv https://raw.githubusercontent.com/Mirantis/cri-dockerd/v0.2.3/packaging/systemd/cri-docker.service
2023-07-22 09:52:21 URL:https://raw.githubusercontent.com/Mirantis/cri-dockerd/v0.2.3/packaging/systemd/cri-docker.service [1337/1337] -> "cri-docker.service" [1]
+ wget -nv https://raw.githubusercontent.com/Mirantis/cri-dockerd/v0.2.3/packaging/systemd/cri-docker.socket
2023-07-22 09:52:21 URL:https://raw.githubusercontent.com/Mirantis/cri-dockerd/v0.2.3/packaging/systemd/cri-docker.socket [204/204] -> "cri-docker.socket" [1]
+ sudo mv cri-docker.socket cri-docker.service /etc/systemd/system/
+ sudo sed -i -e s,/usr/bin/cri-dockerd,/usr/local/bin/cri-dockerd, /etc/systemd/system/cri-docker.service
+ sudo systemctl daemon-reload
+ sudo systemctl enable cri-docker.service
Created symlink /etc/systemd/system/multi-user.target.wants/cri-docker.service → /etc/systemd/system/cri-docker.service.
+ sudo systemctl enable --now cri-docker.socket
Created symlink /etc/systemd/system/sockets.target.wants/cri-docker.socket → /etc/systemd/system/cri-docker.socket.

I'm gonna go ahead, reorganize the changes and prepare the PR for review.

CI run succeeded with debug output enabled (see CI run with initialization of 'Run Kubernetes Test'). I'm gonna drop the debug commit to make the PR reviewable and mergable

Backports created hoping that there's nothing I missed :innocent:

thanks for looking into this issue
great finding
LGTM


OAuth 2.0 Login with access token

Hi,
I'm using NextJS and NextAuth.js with an OAuth provider (Strava). As document at NextAuth.js the library includes some callbacks for using an OAuth-provider to hook into the login process. However, it does not include a callback to get the code returned by the provider to request the access token.
This pull request implements a pocktebase-oauth-login with an access token sent by the user rather requesting the access token with a code by itself.
To have not a major change for the JS library I've used some convention:

The redirectURL in the JS method "client.Users.authViaOAuth2" must include the oauth2.Token struct as query params as follows: http://localhost:3000?access_token=XXX123&refresh_token=ABC123&token_type=Bearer&expires_at=123344

Only the query param "access_token" is a must have
The host is not relevant for but must be valid address to be validated by the original implementation
(The other token details are used for later implementation to store the token in the user's profile)

The JS is as follows:
client.Users.authViaOAuth2('strava', `NOT_RELEVANT`, 'NOT_RELEVANT', `http://example.com?access_token=${account.access_token}&refresh_token=${account.refresh_token}&token_type=${account.token_type}&expires_at=${account.expires_at}`)
        .then((userData) => {
          console.log("Pocketbase user data: ", JSON.stringify(userData, undefined, 2))
          return true;
        })
        .catch((err) => {
          console.log('Error requesting auth / signin at pocketbase: ', err);
          return false;
        });

Feature request for better implementation:

Implement an own API endpoint which takes the oauth2.Token as the input for querying the user's detail
Implement the new endpoint in the JS library

Unfortunately, this pull request includes the other one as well. I've created this branch based on the "oauth strava"-branch; maybe I should create a branch based in the main-branch?

Hi,
I think "hacky" is the right word for the implementation :-) Thanks for your feedback and I do understand your feedback.
Besides that, I've managed to use NextAuth.js to use it with PocketBase the correct way.
But, may I ask: With NextAuth.js I can do the PKCE flow on the client side; isn't that safe?
Great work and thanks, again!

It is safe to make request client side to a OAuth2 PKCE service because the client side doesn't hold the OAUTH2 access token.
Here is a great article with example SPA integration using the PKCE flow - https://www.taniarascia.com/oauth-pkce-authorization/


refactor(traverse): TraverseAncestry use NonEmptyStack

#6206 moved stack types into a shared crate. So now we can use it for the stack in TraverseAncestry.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#6219
#6218
#6217  👈
#6216
#6215
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite

At last! Stack types are paying some dividends:


Possible Error in Anatomy of a STARK, Part 1: STARK Overview

Hello! Been studying STARKs, found this is in Part 1 of the Anatomy of a STARK, in the Cryptographic Compilation with FRI section.

Is the non-interactive proof system described here suppose to be a SNARK and not a STARK?

That depends on whether the meaning of the term "STARK" includes what is being described.

STARK$_1$: a scalable transparent proof system for arguments of knowledge
STARK$_2$: a concrete way of building SNARKs using AIRs and AETs etc
STARK$_3$, the SNARK proof that results from this construction

The end-result after applying the Fiat-Shamir transform is certainly a SNARK. But what is being described in this text is STARK$_2$. In this context, the end-result is also is a STARK$_3$.


Use hot-melt insert with set screw for small gear

The small gear is rotationally constained to the potentiometer with a small groove, but can still move up and down the potentiometer. For now, this is 'fixed' with some hot glue, but that's not an ideal solution since it might come loose.

Reprinting the gead and adding a hole on the side on the gear for a hot-melt threaded insert would allow us to put in a set-screw that keeps the gear secured on the potentiometer.

Alternatively, you can replace the hot-melt insert with just a regular nut inside of the gear, but this might be tricky to put in place and won't work if the size of the nut is bigger than the size of the shaft of the potentiometer


Inspector issue with CPU usage

Hello,
We have 2 agents running on the same machine: one is the classic Java Agent, the other one is the new Node Agent. We noticed in the inspector that the CPU usage data is not properly "merged".
In the inspector of the Java application, this is the CPU usage:

Very low, but not zero for both System and JVM.
In the inspector of the Node application, installed on the very same machine, this is the CPU usage:

Constantly 0.0%.
To my understanding, at least the CPU usage of the Java application should have been shown in the Node application CPU usage diagram as "System" CPU usage. This does not happens and the CPU usage in the Node application shows a flat 0.0%, despite having for sure some usage on the CPU by the other monitored Java application.
Am i misunderstanding something or this could possibly be a bug (or maybe just a feature that still needs to be implemented)?

Hello @davide-parini
Node agent only checks process cpu usage. System usage is a Todo feature.
I am always grateful for your detailed questions.


Fixes the link to the bootstrap script

boostrap should also be changed to bootstrap (missing t)

Fixed in unknown commit..


Etcd together with workers?

So I haven't been able to give this a shot yet but is it possible to schedule the etcd cluster on the same nodes as the workers to reduce resource consumption?

You  can co-locate etcd on the kubernetes-workers @toonsevrin. However, we call this approach "hulk smashing" because it can have some unintended side effects. Such as port collision with a supporting workload on the worker unit wanting to occupy port's 4001, 2380, 2379.
You cant fully isolate etcd in a lxd container on cloud units as there is additional work that needs to happen for the networking segments. However, if you don't plan on launching etcd (or another workload) that wants those ports, and accept the disk i/o bottlenecks that will happen with having your data/wal directory on the same disk as your containers, there's absolutely nothing stopping you from piloting this and giving it a go.
when you deploy etcd, you'll need to specify to which units with a to: directive in the bundle, or if deploying by hand with a --to on the command

Thanks for answering the question, we map all our ports by dns so I don't see us using anything sub 30000.  We are considering running our production cluster on OVH.com vps's.

(Sorry if this is to unrelated to the project)

To be completely honest: I haven't done enough performance profiling to make a definitive call. But my guess is that it would be fine. If you're only operating a small cluster it should be fine to colocate the applications and get that density out of your deployment. There will be a scale limitation here though, as etcd is the primary bottleneck of a cluster operating with high worker count and busy operations (When you start talking deployments/operations per second).
If you're willing to pilot this and feedback any performance issues, it would be good to have those documented and we can triage appropriately.
Thanks for following up @toonsevrin 👍

I'm currently still playing with single node kubernetes, but once I get a complete grasp of things I'll setup a three node testing cluster for our project, and document how it went :)

With several days having passed without additional feedback I presume this issue has been resolved. I'm going to close this for now. if any further issues should arise regarding having etcd colocated with the workers feel free to re-open.


Incorrect datetime value: '2016-10-13 18:59:57.892599+00:00' for column 'created_at' at row 1")

Orator-ORM: 0.9.1
Python: 2.7.10
MySQL: 5.7.15
It happened when I save a model.
orator.exceptions.query.QueryException: (1292, "Incorrect datetime value: '2016-10-13 18:59:57.892599+00:00' for column 'created_at' at row 1") (SQL: INSERT INTO admins (created_at, email, updated_at) VALUES (%s, %s, %s) ([<Pendulum [2016-10-13T18:59:57.892599+00:00]><EMAIL_ADDRESS><Pendulum [2016-10-13T18:59:57.892599+00:00]>]))
The migration script:
from orator.migrations import Migration

class CreateAdminsTable(Migration):

    def up(self):
        """
        Run the migrations.
        """
        with self.schema.create('admins') as table:
            table.increments('id')
            table.string('email', 64).unique()
            table.json('profile').nullable()
            table.json('token').nullable()
            table.small_integer('status').default(0)
            table.timestamps()

    def down(self):
        """
        Revert the migrations.
        """
        self.schema.drop('admins')

I guess the question is timezone info (+00:00).

Are you using mysqlclient or PyMySQL as your database package?

@sdispater Yes, I have installed PyMySQL package.

Which version of PyMySQL do you use?

@sdispater PyMySQL (0.7.9)

Thanks. I will check out what the problem is an get back to you.

I can't reproduce. How do you save your model?

@sdispater
class Admin(db.Model):

    def __repr__(self):
        return '<Admin %r>' % self.id

admin = Admin()
admin.email = email
admin.save()

That's strange. I still can't reproduce. Everything is behaving as expected on my end.
Here is the query that is executed on my system:
INSERT INTO `admins` (`created_at`, `email`, `updated_at`)
 VALUES ('2016-10-14 17:10:25.721616'<EMAIL_ADDRESS>'2016-10-14 17:10:25.721616')

Pendulum instances are properly formatted in my case.

@sdispater
I made a new env by virtualenv for test, The model works perfect.
I try to find out what happened.
After all, it reproduced when I installed MySQL-python.

I can only reproduce with the mysql-python package which is not supported by orator you should use mysqlclient which is an up-to-date version of mysql-python which also support python 3. Or you can use pymysql.
Also if you have both installed, mysqlclient (or mysql-python) will have priority.

Got it.
I've installed MySQL-python and PyMySQL, so I have to uninstall MySQL-python to fix the issue, right?

Yes.
And if you ever need mysql-python, use mysqlclient instead.


Kernel dies during sparse linear solve

I ran into a strange problem today. After a few repetitions (5 should do) the following code makes the kernel crash for me on juliabox
B1 = sprandn(100,100,0.1)
B2 = speye(100)
x  = kron(B2,B1)\randn(100*100)

Can anyone reproduce this problem and knows how to fix it?
Also: I tried to follow the steps on https://github.com/JuliaLang/IJulia.jl to increase the verbosity of juliabox, but couldn't get it to work. Is this only working on local installations?

Possibly JuliaLang/julia#10342?

Quite possible. We need to update the PPAs.

It seems to be different. Tests for issue https://github.com/JuliaLang/julia/issues/10342 seem to run fine.
But the error I get with this is:
julia> x  = kron(B2,B1)\randn(100*100)
julia: symbol lookup error: /usr/bin/../lib/x86_64-linux-gnu/julia/libcholmod.so: undefined symbol: dpotrf_

This is with the latest 0.3.6 binary install. Is it some deps version mismatch?

Cc: @staticfloat @andreasnoack  This certainly seems to be an older version of SuiteSparse. Which one are we using?

@tanmaykm How are B1 and B2 defined?
@ViralBShah We are using CHOLMOD 3.0.4 from SuiteSparse 4.4.3

I tried the snippet from this issue description:
B1 = sprandn(100,100,0.1)
B2 = speye(100)
x  = kron(B2,B1)\randn(100*100)

We are using CHOLMOD 3.0.4 from SuiteSparse 4.4.3

Only on the julianightlies PPA. The juliareleases PPA looks like it's on 4.2.0. For generic binaries from master, Versions.make says 4.4.2, and release-0.3 is on 4.2.1.

dpotrf should be coming from lapack. I think on the PPA we use openblas for blas but netlib for lapack.

Should we install Julia on JuliaBox using the tarball, rather than the PPA - so that we get all the right libraries?

I think it's easier to control everything that way, and we don't need to wait for Elliot to fix the PPA when problems happen. We might occasionally need Elliot to fix the buildbots if something breaks there, but we haven't had many issues with them.
Since JuliaBox is using docker and needs to rebuild the container image anyway to update versions, I don't think using the PPA has any specific advantages here.

Yeah - this seems the way to go for 0.3.6. Also, we can start publishing these as the docker containers then.

Reusing the PPA does make it a lot easier to build the JuliaBox images though.
There are already quite a bit of dependencies that JuliaBox needs to build for the packages. It currently uses the automated trustedbuild facility of dockerhub. And dockerhub does not act nicely with images that take too long to build.

@tanmaykm see https://gist.github.com/anonymous/9db1ce5252adbe8c9803 for a rough sketch - should be faster to build (curl | tar) than using the PPA.

I'm apparently not fully awake yet so sorry for the misinformation about the versions. I should have checked Versions.make instead of guessing and read the top of this issue.
I've just tried to run the example on Ubuntu 14.10 with Julia release from @staticfloat's PPA and it works so I don't know why you are getting the error. Is your system up to date?

@andreasnoack JuliaBox is built on 14.04. Will that make a difference? But doesn't installing from PPA install all dependencies for Julia? Then the base Ubuntu version should not matter.
@tkelman Thanks. Will try that. I misunderstood the tarball to be a source tarball.

I guess the question is how recently was the PPA updated, since I think the suitesparse stuff was tweaked recently.

Yes, I recently (about a week ago) fixed some sparse stuff. Make sure
you've updated and upgraded your packages recently.
On Thu, Mar 19, 2015, 04:23 Tony Kelman<EMAIL_ADDRESS>wrote:

I guess the question is how recently was the PPA updated, since I think
the suitesparse stuff was tweaked recently.
—
Reply to this email directly or view it on GitHub
https://github.com/JuliaLang/JuliaBox/issues/221#issuecomment-83517215.

@staticfloat I see this issue in a docker image built 4 days back using this Dockerfile and without any cache: https://github.com/tanmaykm/JuliaDockerImages/blob/master/base/v0.3/Dockerfile
Can you spot anything there that could be causing this?
I'm also going to try with a fresh build.

Happens with a fresh build and also with this minimal Dockerfile:
FROM ubuntu:14.04

RUN apt-get install -y apt-utils software-properties-common \
    && apt-add-repository -y ppa:staticfloat/juliareleases \
    && add-apt-repository -y ppa:staticfloat/julia-deps \
    && apt-get update \
    && apt-get install -y julia=0.3.6-depsfix9-trusty \
    && apt-get clean

ENTRYPOINT /bin/bash

Strangely, the Julia banner shows:
               _
   _       _ _(_)_     |  A fresh approach to technical computing
  (_)     | (_) (_)    |  Documentation: http://docs.julialang.org
   _ _   _| |_  __ _   |  Type "help()" for help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 0.3.6 (2015-01-08 22:33 UTC)
 _/ |\__'_|_|_|\__'_|  |  Official http://julialang.org release
|__/                   |  x86_64-linux-gnu

julia>

Shouldn't the date be a more recent one?

@tanmaykm I've built a new version (julia-0.3.6-depsfix10) which doesn't have the problem above.  Try updating and see if it's any better for you.  It also removes a bunch of dependencies (the dependencies are bundled within Julia itself) so you might want to apt-get autoremove afterwards.

The date isn't getting updated properly because of a trick of the build process.  Don't worry about it.  :P

Thanks @staticfloat !


transition-group is not working on tables rows (tr)

Version
2.4.2
Reproduction link
https://jsfiddle.net/c8vqajb4/
Steps to reproduce
click the button no transition
What is expected?
transition on opacity property when the row appear
What is actually happening?
no transition just appear

see also https://stackoverflow.com/questions/45720175/vuejs-transition-on-table-rows/45720882?noredirect=1#comment78400529_45720882

The tag <transition> is not allowed in <table> according to HTML spec, it will be stripped automatically by the browser, you can use template option, https://jsfiddle.net/xujiongbo/c8vqajb4/7/


Ontology Embedding

您好，请问公式3的Stage 1 表述是什么呢？
没有在您的论文中看到。
代码复现时，这里出现了维度匹配的错误。

我也遇到了同样的问题：
Traceback (most recent call last):
File "run_gbert.py", line 492, in
main()
File "run_gbert.py", line 488, in main
test(task=0)
File "run_gbert.py", line 472, in test
input_ids, dx_labels=dx_labels, rx_labels=rx_labels)
File "/usr/local/lib/python3.7/dist-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "/content/drive/MyDrive/Colab Notebooks/Multimodal/G-Bert/code/predictive_models.py", line 157, in forward
_, bert_pool = self.bert(input_ids, token_types_ids)
File "/usr/local/lib/python3.7/dist-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "/content/drive/MyDrive/Colab Notebooks/Multimodal/G-Bert/code/bert_models.py", line 312, in forward
x = self.embedding(x, token_type_ids)
File "/usr/local/lib/python3.7/dist-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "/content/drive/MyDrive/Colab Notebooks/Multimodal/G-Bert/code/graph_models.py", line 292, in forward
input_ids) + self.type_embedding(input_types)
File "/usr/local/lib/python3.7/dist-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "/content/drive/MyDrive/Colab Notebooks/Multimodal/G-Bert/code/graph_models.py", line 266, in forward
[self.special_embedding, self.rx_embedding(), self.dx_embedding()], dim=0)
File "/usr/local/lib/python3.7/dist-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "/content/drive/MyDrive/Colab Notebooks/Multimodal/G-Bert/code/graph_models.py", line 59, in forward
emb = self.g(self.g(emb, self.edges1.to(emb.device)),
File "/usr/local/lib/python3.7/dist-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "/content/drive/MyDrive/Colab Notebooks/Multimodal/G-Bert/code/graph_models.py", line 219, in forward
return self.propagate('add', edge_index, x=x, num_nodes=x.size(0))
File "/content/drive/MyDrive/Colab Notebooks/Multimodal/G-Bert/code/graph_models.py", line 116, in propagate
out = self.message(*message_args)
File "/content/drive/MyDrive/Colab Notebooks/Multimodal/G-Bert/code/graph_models.py", line 223, in message
alpha = (torch.cat([x_i, x_j], dim=-1) * self.att).sum(dim=-1)
RuntimeError: Sizes of tensors must match except in dimension 3. Expected size 2 but got size 1 for tensor number 1 in the list.

@eh58 : Were you able to fix this issue. I have the same issue the repo.


span issue

Description
there is an issue with  tag. For example
var html =

  // does NOT work
//var html =

  // does NOT work

Input
The code looked like this before beautification:

Expected Output
The code should have looked like this after beautification:

Actual Output

var html =

  // does NOT work
//var html =

  // does NOT work
//var html =

 // does NOT work
//var html =

  // works

var tidyHtml = html_beautify(html, {
  indent_size: 2
})

Steps to Reproduce
Environment
OS: web browser, jsFiddle
the same for https://beautifier.io/
using
https://jsfiddle.net/radek/5ekt70u8/18/

has anyone fixed this issue? I'd love to work on it

Hi @bitwiseman, I tried fixing this. Thing is that on achieving this behaviour, a lot of  the test cases end up failing. I wanted to be absolutely sure if I'm achieving the correct behaviour.
Example:
Input:

Inside divInside spanInside aInside div

Expected:

    Inside div
    Inside span
    Inside a
    Inside div

Or should the output be like this?

    Inside divInside spanInside aInside div


Case correction for Linux-like systems in docs

If using variables in uppercase this guide doesn't work, precising that at least in Linux-like (Ubuntu etc.) variables must be in lowercase.
Tested on a Ubuntu 19.04 while creating Docker image FROM 18.04 via Dockerfile.

Deploy preview for docsdocker ready!
Built with commit 6adba1c7c2af987df0d3fdef769f87ef98c4bed4
https://deploy-preview-9502--docsdocker.netlify.com


How to test

How to test
Unable to test the effect,

throw new \Exception('Testing Telegram Logger');


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Patch docker and setup.py errors for prod build

Hello erwan-b,
My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.
Status report is not available.

Incorrect fix version
The Fix Version/s in issue BERTE-542 contains:

None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

3.5.1

Please check the Fix Version/s of BERTE-542, or the target
branch of this pull request.

Waiting for approval
The following approvals are needed before I can proceed with the merge:

the author

2 peers

/approve

In the queue
The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.
The changeset will be merged in:

:heavy_check_mark: development/3.5

The following branches will NOT be impacted:

development/1.0
development/2.0
development/3.0
development/3.1
development/3.2
development/3.3
development/3.4

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.
IMPORTANT
Please do not attempt to modify this pull request.

Any commit you add on the source branch will trigger a new cycle after the
current queue is merged.
Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.
The following options are set: approve

I have successfully merged the changeset of this pull request
into targetted development branches:

:heavy_check_mark: development/3.5

The following branches have NOT changed:

development/1.0
development/2.0
development/3.0
development/3.1
development/3.2
development/3.3
development/3.4

Please check the status of the associated issue BERTE-542.
Goodbye erwan-b.


ngrok Tunnel

im having trouble setting up a ngrok Tunnel.
i have mine installed as docker on unraid
setup with docker-compose
the Tunnel works showing the frontpage but if i go to one of this it just keeps loading and nothing happens
performers
galleries
scenes
ngrok setup
ive stuff with *'s is just random stuff i typed insetd of whats really there that is for my eyes only
#'s is commutes
ngrok.yml
GNU nano 2.5.3                             File: ngrok.yml
authtoken: 897fsao8u7f89yud89iq89*****68976789  # account key
tunnels:
stash:  # name of tunnel
addr: 8008 # port to foward
proto: http # type of tunnel
subdomain: stash*****    # sub domain of ngrok so it be stash*****.ngrok.io
auth: "user***:password****" # user and pass for tunnel
bind_tls: false # only forwards http and not https
inspect: false # turns off data passing though

You likely need to forward another port.  The UI is served through port 8008 (on docker), but you also need port 4000 for the GraphQL API.

Ngrok only let's you open one port per url
So I went with noip.net


Alexa Chatbase Analytics Update

Proposed changes

I fixed the format of the agent message for Alexa chatbase analytics and added some unit tests.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My code follows the code style of this project
[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly
[x] I have added tests to cover my changes
[ ] All new and existing tests passed

Awesome! First external PR for v2! Thank you so much.


Add high level cloud architecture diagram + advanced configuration to IaSQL on EC2 post

Add ELB for SSL certificate
Add ACM certificate
Add Route53 entry for domain
Maybe add EBS volume
Diagram like https://www.reddit.com/r/webdev/comments/zpsseu/my_saas_architecture_tech_stack_on_aws_as_a_solo/


The version button is not closing after opening it on the documentation page(Getting Started/Your first wagtail site)

Issue Summary
On getting_started/tutorial.html on the bottom right  we have a "versions" button, and the problem is if we click on it, then it normally opens but there is no close button for It
Steps to Reproduce

Search wagtail on browser

Open  wagtail's official site https://wagtail.org/, and click on get started button

And then click on Build Your First Site

On the bottom right corner we can see a button for different versions

Click on It and  It normally opens but there is no way of closing it, until we refresh the site.

Video version of problem
https://user-images.githubusercontent.com/91000828/218751798-bab9b96a-5492-4b38-a4c0-2be962e4a29c.mp4

The fix is already here:
https://github.com/wagtail/sphinx_wagtail_theme/blob/5a42098f0c75843b0f7aab922b9c69994dbf4768/sass/_component_versionpicker_fix.scss#L11
but it loses to the specificity of the default .rst-versions.shift-up rule:

Adding the .shift-up selector should fix it.

I am currently going through development instructions to set up local environment so before I do anything ahead can you assign me this issue plaese.

@MJCoder15 we don't assign issues - just go ahead and give it a go when you're ready.

OK Got It👍🏽

PR up https://github.com/wagtail/sphinx-wagtail-theme/pull/261


ResistanceLowersTarget does not work

Describe the bug
due to this line the oref functionality resistance_lowers_target does not work as it is always false
To Reproduce
Steps to reproduce the behavior:

activate that setting in preferences
watch for an autosens >1
see if target in popup will be lower when from from profile
See that is the same, which would be an error and target is not adjusted due to the setting in oref

Expected behavior
target need to be lower than profile target
Solution
case resistanceLowersTarget = "resistance_lowers_target" in preferences.swift (see above)

Yes, I'm aware of this. However, your suggested fix will reset the OpenAPS settings for everyone.
There is another fix to migrate this conversion without resetting which I'll push later

I pushed a fix to dev now.


To get the duration of the SoundwaveProcedural

Dear Santtu Keskinen.
Is it possible to have the SoundwaveProcedural's duration(length)?
or could you kindly provide any hints to have it?
Thanks.

Hi redbean.
Sorry for late reply but I'm not really providing support for this package.
The sound wave is created asynchronously so you to wait until the sound wave is actually created before you can get the duration. You could add callback to function Say that is called when the processing is actually done.


After the execution of “npm install" is completed,but not generate  the script of "start"

Please consult the simple-viewer-app README: https://github.com/imodeljs/simple-viewer-app
There are several options for starting the app depending on whether you want to run it in electron or a browser, and whether you want to start the webserver, the backend, or both.
To start it so that you can run it in a browser on localhost, use: npm run start:servers


Appstudio update hacbs-test-project-dnis

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI has failed.There was an error creating the PipelineRun: hacbs-test-project-dnis-on-pull-request-
creating pipelinerun hacbs-test-project-dnis-on-pull-request- in namespace rhtap-demo-xwgq-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: hacbs-test-project-dnis-on-pull-request-
creating pipelinerun hacbs-test-project-dnis-on-pull-request- in namespace rhtap-demo-okmf-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: hacbs-test-project-dnis-on-pull-request-
creating pipelinerun hacbs-test-project-dnis-on-pull-request- in namespace rhtap-demo-dkfi-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request


"Maximum batch size" and "Maximum batch time" are not overwritten through env variables

if the two variable max_batch_time and max_batch_size are defined in the model-settings.json:
{
    "name": "node-1",
    "implementation": "models.NodeOne",
    "max_batch_size": 5,
    "max_batch_time": 1,
    "parameters": {
        "uri": "./fakeuri"
    }
}

Then they couldn't be overwritten by environment variables MLSERVER_MODEL_MAX_BATCH_SIZE and MLSERVER_MODEL_MAX_BATCH_TIME and mlserver will always revert back to the values set in the model-settings.json. However, it is expected to use the values in the json as defaults and env variable as user arguments for overwriting them.

Hey @saeid93 ,
Yeah, it's a known issue that, when using mlserver build, local setting files override environment variables. This is due to how they get injected during the container's startup (which is essentially by injecting them as env vars as well).
Having said that, there wasn't an issue for that yet, so thanks for opening one!

Hey @adriangonz,
Sure, no problem. Since the setting.json is also injected by env vars why the same env var is not used for the initialization as well? so it will be overwritten by the user-defined var?

Hey @saeid93 ,
When you build a custom image and it has a settings.json present, the same issue should occur. As in, the values set up on that local settings.json will get injected through env vars, overriding whatever else comes from upstream.


Let's separate the code into an algorithm part and a traffic-environment-connection part

Currently, the algorithm-related codes and traffic-environment-connection-related codes are mixed in one file.
If you want to add another algorithm that uses the same traffic environment or apply the same algorithm to another traffic environment, you have to rewrite all the code.
Separation of code increases reusability and extensibility.
Then you can easily add other algorithms and easily connect with other traffic environments.

done.
ref. following pull request.
https://github.com/etri-city-traffic-brain/traffic-signal-optimization/pull/10


Implement payout & backer details modal

The new Issue row redesign has information regarding backers & payment events. This information should also be available in a modal which can be brought up from the Issue row.
Design ticket: https://github.com/polarsource/polar/issues/1202
Figma link: https://www.figma.com/file/1p2oOjsRBgSrr3SC4zySJG/Polar-v0.3%3A-Rewards-%26-Social?type=design&node-id=603-6613&mode=design&t=FphuEgKnbb5OOyUW-4

Cleaning up our GitHub issues and closing stale issues unless they're related to current focus. They'll resurface if needed.


Update optimize, Compilers, and GV

Support generating source code in Compilers;
Change the leafmap generation from optimize!() returns to statically compiler returns.

Codecov Report
Attention: 20 lines in your changes are missing coverage. Please review.

Comparison is base (6034184) 67.87% compared to head (7d17f38) 67.88%.

Files
Patch %
Lines

src/frontend/GV.jl
11.76%
15 Missing :warning:

src/backend/static.jl
68.75%
5 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##           computgraph     #159   +/-   ##
============================================
  Coverage        67.87%   67.88%
============================================
  Files               64       64
  Lines             4579     4543   -36
============================================
- Hits              3108     3084   -24
+ Misses            1471     1459   -12

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Appstudio update test-component-pac-tdyq

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-tdyq-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
9 seconds
init

✅ Succeeded
16 seconds
clone-repository

✅ Succeeded
37 seconds
build-container

✅ Succeeded
18 seconds
inspect-image

✅ Succeeded
18 seconds
deprecated-base-image-check

✅ Succeeded
1 minute
clair-scan

✅ Succeeded
35 seconds
clamav-scan

✅ Succeeded
12 seconds
sbom-json-check

✅ Succeeded
13 seconds
label-check

✅ Succeeded
13 seconds
optional-label-check

✅ Succeeded
5 seconds
show-sbom

✅ Succeeded
8 seconds
show-summary