HBASE-24718 : Generic NamedQueue framework for multiple use-cases (Refactor SlowLog responses)

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Patch Compile Tests _

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

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

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

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

-0 :warning:
javadoc
0m 39s
hbase-server in the patch failed.

_ Patch Compile Tests _

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

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

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

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

-0 :warning:
javadoc
0m 39s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
144m 47s
hbase-server in the patch passed.

171m 29s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 46a0d0d0f541 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 724f0478ed

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/1/testReport/

Max. process+thread count
4297 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

+0 :ok:
prototool
0m  0s
prototool was not available.

+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 21s
Maven dependency ordering for branch

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

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

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

_ Patch Compile Tests _

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

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

-0 :warning:
checkstyle
1m 12s
hbase-server: The patch generated 18 new + 113 unchanged - 4 fixed = 131 total (was 117)

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

+1 :green_heart:
hadoopcheck
12m 12s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
hbaseprotoc
2m  0s
the patch passed

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

_ Other Tests _

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

49m 46s

Reason
Tests

FindBugs
module:hbase-server

Possible doublecheck on org.apache.hadoop.hbase.namequeues.NamedQueueRecorder.namedQueueRecorder in org.apache.hadoop.hbase.namequeues.NamedQueueRecorder.getInstance(Configuration)  At NamedQueueRecorder.java:org.apache.hadoop.hbase.namequeues.NamedQueueRecorder.getInstance(Configuration)  At NamedQueueRecorder.java:[lines 78-82]

Unchecked/unconfirmed cast from org.apache.hadoop.hbase.namequeues.NamedQueuePayload to org.apache.hadoop.hbase.namequeues.RpcLogDetails in org.apache.hadoop.hbase.namequeues.SlowLogQueueService.consumeEventFromDisruptor(NamedQueuePayload)  At SlowLogQueueService.java:org.apache.hadoop.hbase.namequeues.RpcLogDetails in org.apache.hadoop.hbase.namequeues.SlowLogQueueService.consumeEventFromDisruptor(NamedQueuePayload)  At SlowLogQueueService.java:[line 101]

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/2/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle cc hbaseprotoc prototool

uname
Linux 53dfd728afb3 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 3bd54217a0

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

spotbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/2/artifact/yetus-general-check/output/new-spotbugs-hbase-server.html

Max. process+thread count
84 (vs. ulimit of 12500)

modules
C: hbase-protocol-shaded hbase-client hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/2/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 31s
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 23s
Maven dependency ordering for branch

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

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

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

+1 :green_heart:
javadoc
1m 19s
master passed

_ Patch Compile Tests _

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

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

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

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

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

+1 :green_heart:
javadoc
1m 11s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 47s
hbase-protocol-shaded in the patch passed.

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

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

172m 24s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/2/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 0668cebef2d1 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 3bd54217a0

Default Java
1.8.0_232

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/2/testReport/

Max. process+thread count
4871 (vs. ulimit of 12500)

modules
C: hbase-protocol-shaded hbase-client hbase-server U: .

_ Patch Compile Tests _

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

+1 :green_heart:
mvninstall
5m 33s
the patch passed

+1 :green_heart:
compile
3m 17s
the patch passed

+1 :green_heart:
javac
3m 17s
the patch passed

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

-0 :warning:
javadoc
0m 33s
hbase-client in the patch failed.

-0 :warning:
javadoc
0m 48s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
1m 17s
hbase-protocol-shaded in the patch passed.

+1 :green_heart:
unit
1m 24s
hbase-client in the patch passed.

+1 :green_heart:
unit
142m 11s
hbase-server in the patch passed.

186m 51s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux ddc2e161a82f 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 3bd54217a0

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-client.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-client.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/2/testReport/

Max. process+thread count
4498 (vs. ulimit of 12500)

modules
C: hbase-protocol-shaded hbase-client hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/2/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

+0 :ok:
prototool
0m  0s
prototool was not available.

+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 24s
Maven dependency ordering for branch

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

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

+1 :green_heart:
spotbugs
6m 15s
master passed

_ Patch Compile Tests _

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

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

-0 :warning:
checkstyle
1m  6s
hbase-server: The patch generated 18 new + 113 unchanged - 4 fixed = 131 total (was 117)

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

+1 :green_heart:
hadoopcheck
11m 15s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
hbaseprotoc
1m 58s
the patch passed

+1 :green_heart:
spotbugs
6m 46s
the patch passed

_ Other Tests _

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

46m 22s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/3/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle cc hbaseprotoc prototool

uname
Linux 9c69826f8103 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 3bd54217a0

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/3/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
94 (vs. ulimit of 12500)

modules
C: hbase-protocol-shaded hbase-client hbase-server U: .

_ Patch Compile Tests _

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

+1 :green_heart:
mvninstall
4m 28s
the patch passed

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

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

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

-0 :warning:
javadoc
0m 30s
hbase-client in the patch failed.

-0 :warning:
javadoc
0m 50s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
1m 18s
hbase-protocol-shaded in the patch passed.

+1 :green_heart:
unit
1m 19s
hbase-client in the patch passed.

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

183m  7s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux a25ecb6ab3e7 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 3bd54217a0

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/3/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-client.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/3/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/3/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-client.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/3/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/3/testReport/

Max. process+thread count
3899 (vs. ulimit of 12500)

modules
C: hbase-protocol-shaded hbase-client hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/3/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 34s
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 33s
Maven dependency ordering for branch

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

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

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

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

_ Patch Compile Tests _

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

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

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

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

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

+1 :green_heart:
javadoc
1m 12s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 45s
hbase-protocol-shaded in the patch passed.

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

-1 :x:
unit
161m  6s
hbase-server in the patch failed.

192m 25s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/3/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 964cc2c11b4b 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 3bd54217a0

Default Java
1.8.0_232

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

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/3/testReport/

Max. process+thread count
4220 (vs. ulimit of 12500)

modules
C: hbase-protocol-shaded hbase-client hbase-server U: .

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

+1 :green_heart:
mvninstall
4m 29s
the patch passed

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

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

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

-0 :warning:
javadoc
0m 16s
hbase-common in the patch failed.

-0 :warning:
javadoc
0m 25s
hbase-client in the patch failed.

-0 :warning:
javadoc
0m 40s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
1m  2s
hbase-protocol-shaded in the patch passed.

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

+1 :green_heart:
unit
1m 22s
hbase-client in the patch passed.

+1 :green_heart:
unit
188m 50s
hbase-server in the patch passed.

227m 20s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/4/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 87bd73b4c07e 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 2505c7760d

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/4/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-client.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/4/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/4/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/4/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/4/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-client.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/4/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/4/testReport/

Max. process+thread count
3480 (vs. ulimit of 12500)

modules
C: hbase-protocol-shaded hbase-common hbase-client hbase-server U: .

 Binary files and potentially other changes not applied. Please rebase and squash commits if necessary.

_ Patch Compile Tests _

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

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

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

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

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

+1 :green_heart:
javadoc
1m 27s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 47s
hbase-protocol-shaded in the patch passed.

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

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

+1 :green_heart:
unit
201m 35s
hbase-server in the patch passed.

236m 34s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/4/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 6c81c7f0a354 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 2505c7760d

Default Java
1.8.0_232

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/4/testReport/

Max. process+thread count
3476 (vs. ulimit of 12500)

modules
C: hbase-protocol-shaded hbase-common hbase-client hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2052/4/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.


"odo create" supports for dowloading devfile compoent template

/kind user-story
User Story
As a user I want to use the template that is compatible with the devfile I specify during odo create [component type] so that I don't need to bring my own template and I can start working on the component development based on the provided template.
Acceptance Criteria

[ ] Read the template location directly from devfile and use that template location to download template:

projects:
-
  name: example
  source:
    type: git
    location: https://github.com/golang/example.git
  clonePath: src/github.com/golang/example/

[ ] Create a new flag like --template to enable the feature of downloading template

That's my initial thought and rough idea 🤔 , please feel free to add comments or questions
/kind user-story
/area devfile

@GeekArthur This seems like a dupe of https://github.com/openshift/odo/issues/2582?

@johnmcollier Yeah, essentially they are talking about the same thing, but for the time being we can leave this issue open to keep the rough design, then we can use one issue to track until we finalize the design. Thanks for pointing this out.

Closing this one since this is a dup of #2582 . Design info can be found on that item.


For SLE11 there is no Waagent in cloudrepo

Hi Team,
You've mentioned that waagent can be found under Cloud:tools. for SLE 11 but there is no link for the agent there.
https://build.opensuse.org/repositories/Cloud:Tools

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 6ea02d36-fca1-a329-f539-90e22b698977
Version Independent ID: 35d1f897-0d81-98b8-1c28-af1528f1e135
Content: Linux distributions endorsed on Azure - Azure Linux Virtual Machines
Content Source: articles/virtual-machines/linux/endorsed-distros.md
Service: virtual-machines-linux
GitHub Login: @MicahMcKittrick-MSFT
Microsoft Alias: mimckitt

@aquibqureshi26 Thanks for your Query.
As mentioned in document in the link https://build.opensuse.org/repositories/Cloud:Tools the agent is available under module named "python-azure-agent".
Please see below screenshots:

@aquibqureshi26 Hope the above provided information is helpful.
We will now close this issue. If there are further questions regarding this, please tag me in a comment. I will reopen it and we will continue the discussion.


Positioning IME bars on iOS

Description
Engine: https://github.com/flutter/engine/pull/19929
Keep sending marked text rect / caret rect information for the iOS text input plugin to consume.
Turning this into a real PR when https://github.com/flutter/flutter/pull/61940 is merged .

Related Issues
Depends on https://github.com/flutter/flutter/pull/61940
Fixes https://github.com/flutter/flutter/issues/9344
Tests
I added the following tests:

the "setMarkedTextRect" group

Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[ ] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[ ] I signed the [CLA].
[ ] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[ ] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] All existing and new tests are passing.
[ ] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[ ] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read [Handling breaking changes].

[ ] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: https://flutter.dev/go/breaking-changes-template Replace this with a link to a pull request that adds the migration guide to https://flutter.dev/docs/release/breaking-changes

@GaryQian @justinmc updated. Should be ready for review now.

Waiting for the release to be cut.

Gold has detected about 3 untriaged digest(s) on patchset 16.
View them at https://flutter-gold.skia.org/cl/github/61981


Polished the Time Complexity and Space Complexity Section

Proposed changes
I've polished the Time Complexity and Space Complexity Section, I thought I'd add some grammatical corrections, bullet points, and keep those points according to markdownlint standards.
Types of changes

[x] Proofreading (fix spelling, grammar, punctuation, accuracy) Proofreading
[ ] New content (new section, new readme, etc)
[x] Modifications (modifying existing content, adding new content)
[ ] Other (please describe)

@all-contributors please add @Sayed-Afnan-Khazi for 🖋

Thanks! 🙌


Enhance Support setting initial root password when FE firstly launch

Proposed changes
Issue Number: close #xxx
Doris FE firstly launch with no root password for now. In my organization scene, we use Doris operator start a Doris cluster, then set password for root user via  peripheral system, which increase system Complexity.
This pr introduces FE config initial_root_password to set root user initial 2-staged SHA-1 encrypted password, default as '', means no root password. Subsequent 'set password' operations for root user will overwrite the initial root password.
if initial_root_password is not a valid 2-staged SHA-1 encrypted password, no root password set as before.

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

cc @morningman @chenlinzhong @luozenglin Please have a review, thx

run buildall

run buildall

run buildall

Maybe documentation should be provided on how to convert a plaintext password to initial_root_password.

run buildall

Maybe documentation should be provided on how to convert a plaintext password to initial_root_password.

@luozenglin new commit is pushed, PTAL

@morningman , docs annotations has optimized, PTAL, thx

run buildall

run buildall

run feut


fix(ncyBreadcrumb): Prevent memory leak when label is a binding

Releases collection of watchers, preventing a leak when the label is a binding and not a string.
We found that when using ui-router state definitions, if we used a binding (pictured below) and not a string constant, the related scope is leaked and held onto.  The deregisterWatchers() function does not actually clear out the collection passed in.  This causes the functions in the collections to accumulate, and in this scenario they hold references to scopes.
Clearing out the collections in the calling functions releases the references as expected.

Coverage increased (+0.04%) to 96.71% when pulling 264e10f680e1bbb8d1e00cf500de39cac4222cfd on castle-it:fix-memoryLeak into ef735250f95be945f23e05aa71f29cc448529775 on ncuillery:master.

Hi, thank you for your PR.
Shame of me, arrays are passed by value of course :sweat_smile:

You've built an excellent tool, we're happy to contribute where we can :)


articles deleted from Omnivore are not removed from Logseq upon sync

After having deleted an article from Omnivore I expected it to disappear from Logseq. However after manually syncing it was still there.

Yes, this is doable with the new updateSince API


add missing trailing slash in ADD and COPY /absoluteDir examples.

Accorrding to the specs they are mandatory.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fix/docs-trailing-slash-in-dockerfile-copy-example" git@github.com:bastiaanb/docker-1.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

LGTM

Thank you!
LGTM


fixed Ayatul Kursi link

Title of change
why the change and what has changed
Resolving this issue
Checklist

[ ] Unit tests written
[x] Manually tested
[ ] Prettier & ESLint were run
[ ] New dependencies are included in package-lock.json

Screenshot
insert screenshot if needed

Deployed to: http://staging.quran.com:32832

Deployed to: http://staging.quran.com:32833

@shahednasser /ayatul-kursi was added for seo purpose :)

I understand but the link does not work.

I understand but the link does not work.

https://staging.quran.com/ayatul-kursi
Its working, the error is in audio player :(


Add flag for referrer header directive

This PR adds a patch that allows changing the amount of information passed through the referrer header.
Using the no cross-origin option removes the referrer for cross-origin requests, while the minimal option also strips same-origin referrers to just the origin instead of the full URL.
This can help prevent tracking, but in some instances can also cause some problems for sites that rely on the referrer to function correctly.
The referrer header can be disabled completely by launching with the existing feature:  --enable-features=NoReferrers.
Fixes #1918

The referrer header can be disabled completely by launching with the existing feature: --enable-features=NoReferrers.

Is this feature not available via flags? Only commandline?

Yes, it's a pre-existing feature in upsteam chromium and doesn't have a flag entry.
I could include that as an option in the current flag if it makes sense.
Maybe that should be it's own separate flag?  If so, then it might be something that could be included in #1687.  That PR has been hanging around for a while, I might need to revisit it next time I get the spare time.

I have rebased the patch over yesterday's update and added the noreferrers option, which removes all referrers.

On POST requests minimal does preserve url. Is it how it is supposed to be? All GETs don't have anything after domain, but POSTs have. It could be that XMLHttpRequests are affected.

It should be stripping the URL down, but maybe there's something I missed?  How are you testing those POST requests?
Using https://www.darklaunch.com/tools/test-referer to test everything except for the cross-origin referrer:

How are you testing those POST requests?

I've inspected nginx logs on my personal website, but that's easy to reproduce: open devtools, filter Fetch/XHR write something and hit Preview (seems to work even by hovering over the button). XMLHttpRequests should fire.

At the same time GET is as expected:

Thanks, that helped me figure out what is happening; asynchronous requests are handled differently.  I already have a working solution, but since those requests aren't run on the main thread I'll have to either change the patch to use feature flags or pass the switch through the network context.  I'll test what seems to work better this weekend as I get the time.

It turns out that UtilityProcessHost will copy over command line switches.  This makes things easier and means the flags can stay the same as they were.

Won't they conflict? Maybe after merging #1964

I built with this branch rebased on top of the update, it didn't complain and everything works as expected

🤷 I remember there were some hard-to-catch issues once, when we merged feature-PR before the version-PR.

I mean we can merge the update first of course, though the result on disk will be the same regardless of the order in git

Merging this PR first might make version-PR in need for a rebase due to failing tests, which drops reviews and so on and so forth. Or may not, Im not certain…

The offset on line 33 will have to be incremented for the checks on github to pass, but it won't cause a problem when building.
The PR that is merged after the first will fail the checks if it's not updated to include that offset change.  The order doesn't matter, I'll just need to add a new commit to the second PR which will invalidate the existing approvals.
It's a shame, if there wasn't that single line added to utility_process_host.cc in 102 both PRs would have been able to be done in any order without change!

Good question is: are we tagging new version after merging this PR or not? :)

I'd say we tag after merging both

lets see


Restore paragraph breaks that were lost lost during the RST export

Fixes rdar://102991635

@krilnon It should fix all of them. I used the legacy pipeline to build the XML version of the book, and scripted a search over that XML to find every note box or list item that had more than one paragraph.  But we'll also want to keep an eye out during the rest of the page-turn in case I missed anything.

Through the rest of the page-turn, all of the other instances of this issue we found had already been fixed by this PR.


RINGDAO Merch Branding

Looks very nice, please respond to my message on TG about color scheme - also please share the actual psd etc files in a PR with a new folder and then  inshallah in future we can do it!


Enhancing the design of To Do list Form and adding scroll if there are more no.of tasks and implement sorted order of tasks

Modifying the form design
Also If more tasks are added , there should be a scroll imo.
Also tasks should be sorted datewise and prioritywise
@Kritika30032002

Are these done? Also If I want to add task for the same day, it says due date has passed, it should not be the case right? and How about adding time feature so that we can add the time to complete along with date? @Kritika30032002


lock flame version

Description
Lock flame version to 1.1.1 because class ParentIsA conflicts in 1.2.0
Type of Change

[ ] ✨ New feature (non-breaking change which adds functionality)
[x] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[ ] 🗑 Chore

Thanks for your contribution. We've actually decided to archive this repo since we don't have anyone working on it full time these days, since it was mostly a demo for an event, but please don't hesitate to fork the repo (it's open source!) if you want to keep it alive!


Add possibility to get initialBlocks and initialBlocksLayout from backend

Add possibility to get initialBlocks and initialBlocksLayout from backend when adding new content in order to let Site Administrators to dynamically define content default blocks together with DX content definition.
Plone Dexterity Fields

Volto Add Form

Ok, maybe because we didn't make it clear from the beginning what we are trying to achieve with this, the confusion.
Our main requirement from Volto or a Volto Add-on right now is to be able to define Dexterity Content-Types TTW, as in the real world one page content-type with Title as the default block doesn't fit all cases and customers need content with more metadata, they need to define content initial blocks and maybe some required ones. They need to easily change logo, labels, placeholders, default values, etc (not a developer's job, if you ask me)
For this:

We need Dexterity within Volto > ControlPanel ASAP
We are going to extend this panel with a Volto TTW Dexterity layout editor (which may end-up in the core or as a Volto Add-on, to be discussed).

Excerpt from the Zen of Volto:
That means this someone has to be able to run, test and use Volto (and thus Plone), and ultimately customize a simple project without any problem and without having to touch Plone by any mean or write a single line of Python nor implement a single Plone add-on product.

With this in mind, as Dexterity Content-Types already provide the default values feature, without having to write a single line of Python code within a custom Plone Add-on
we think it is the best place were initialBlocks and requiredBlocks should come from. Of course nobody will have to edit this values manually and there will be a nice Volto Control-Panel interface for it.
Also, within current Volto implementation of initialBlocks and requiredBlocks one can NOT provide blocks default values, custom placeholders, etc. Not mentioning the fact that if you add a new Dexterity-Type on backend you need to hire a JavaScript Developer to define the initialBlocks and the requiredBlocks for it. And how is the front-end back-end agnostic if it requires to re-deploy front-end every time you create a new Dexterity Content-Type on backend?
My feeling is that this settings should stay together with the content-type definition.
One last thought:
For the sake of Javascript Developers, let's not cut features and most important let's NOT forget the end-user.
IMHO we should always focus first on the end-User eXperience and the Developer eXperience will follow

Will close this ticket for now and continue work on https://github.com/plone/volto/issues/1517


deploy:writable missing from recipes

Q
A

Issue Type
Bug

Deployer Version
6.2.0

Local Machine OS
WSL

Remote Machine OS
CentOS

Description
Some recipes do not have deploy:writable in the list of deploy tasks. For example, the Codeigniter and Drupal recipes define writable_dirs but never runs the code to make that happen. Also the same for the Composer recipe. The Wordpress recipe is an example that does have it.
Steps to reproduce
Set writable_dirs and use a recipe that does not include deploy:writable in the task list.
Content of deploy.php

namespace Deployer;

set_include_path(get_include_path() . PATH_SEPARATOR . __DIR__ . '/vendor/deployer/recipes');

require 'recipe/composer.php';
require 'recipe/cachetool.php';

// Project name
set('application', 'xxx');

// Project repository
set('repository', 'git@xxxgit');

// Hosts
host('xxx.xx.xx.xxx')
	->stage('production')
	->user('xxx')
    ->set('deploy_path', '/var/www/vhosts/test')
    ->set('cachetool', '<IP_ADDRESS>:9000');

// Shared files/dirs between deploys
add('shared_dirs', [
	'httpdocs/client-area',
	'httpdocs/external',
	'httpdocs/userfiles'
]);

// Writable dirs (does not work out of the box)
add('writable_dirs', [
	'httpdocs/client-area',
	'httpdocs/external',
	'httpdocs/userfiles'
]);

// Clear opcache
after('deploy:symlink', 'cachetool:clear:opcache');

// [Optional] Allocate tty for git clone. Default value is false.
set('git_tty', true);

// [Optional] if deploy fails automatically unlock.
after('deploy:failed', 'deploy:unlock');

Output log
N/A

Is it OK to add deploy:writable to all of the recipes? If so I'll do that and make a PR


feat: Reduce time between status checks for images.

Specifically in redact_folder, adjust status check time for images, which can be done in 1.5-4s.

@georgkoester could you please also check the failing tests? seems like they are legitimate fails

Thanks for the review @radmiratbrighterai !


update R installation, required for RCall

Hopefully this should be sufficient to get RCall working.

Can you test this?

Maybe, but it'll take me a while to look at it.

Same for me

Haha, no worries. I'll try to look into it later this week.

I just tried this out: it seemed to work okay.


Update /admin/reap to return reaped nodes count

See https://github.com/uber/ringpop-node/pull/257#discussion_r62028527 for context.

Can you elaborate more in the description? I don't understand what this is doing. It doesn't seem like it is doing what the title says.

It modifies the /admin/reap test to expect a count instead of ok.

Great. Would you mind adding it to the description with a bit of context?
I'm on the war path to get people to write good descriptions because it helps with releases. It only takes 20 seconds to do this and really helps everyone with reviewing or keeping an eye on the projects... 😄

Totally agree, I added a link for more context.

Doesn't this break the integration test for ringpop-go?
https://github.com/uber/ringpop-go/blob/dev/swim/handlers.go#L162

It does if you enable testing for the reaping-faulty-nodes feature. We'll do a similar change in ringpop-go before this feature is enabled by default.

Am I missing something? I thought it was already enabled by default in ringpop-go...
https://github.com/uber/ringpop-go/blob/master/test/run-integration-tests#L109

Oh, you're right! Good catch, I'll need to update this PR.

LGTM

LGTM

Thanks!!


when.status:failure doesn't work

Component
server
Describe the bug
Step with when.status: [failure] doesn't run on failed pipeline, instead runs step with when.status: [success].
Steps to reproduce

Woodpecker + some Forge
Make a pipeline

# build.yaml
skip_clone: true
steps:
  build:
    image: alpine
    commands:
      - echo 'Building the app'
      - exit 1 # 0 - success, 1 - fail

# notifications.yaml
skip_clone: true
depends_on: [build]
runs_on: [success, failure]
steps:
  fail-notification:
    when:
      - status: [failure]
    image: alpine
    commands:
      - echo 'Build failed'
  success-notification:
    when:
      - status: [success]
    image: alpine
    commands:
      - echo 'Build succeed'

Run manually and get wrong step execution

Expected behavior

fail-notification step runs
success-notification skips

System Info
WP `next-f87e80381b`, `2.7.1`, Gitea, Postgres 16

Additional context
https://github.com/woodpecker-ci/woodpecker/issues/4337#issuecomment-2468498847
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]

It works within a pipeline but not across, hence the title should likely be updated to include this condition/detail.


remove double // and add account name

Codecov Report

Merging #366 (5f3c509) into main (2e5b03f) will increase coverage by 0.07%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #366      +/-   ##
==========================================
+ Coverage   25.73%   25.81%   +0.07%
==========================================
  Files          31       31
  Lines        2848     2851       +3
==========================================
+ Hits          733      736       +3
  Misses       2026     2026
  Partials       89       89

Impacted Files
Coverage Δ

pkg/services/images.go
8.69% <0.00%> (ø)

pkg/services/repobuilder.go
3.00% <0.00%> (ø)

pkg/routes/imagesets.go
33.33% <0.00%> (+1.85%)
:arrow_up:

Continue to review full report at Codecov.

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


When does the training stop?

Hello,
Was there a specific reason for ending the training at 40K steps?
What criteria or basis(i.e. metric) did you use to determine the stopping point?

Hi, Thanks a lot for your interest in the INSTRUCTOR model!
To determine the stopping point of the training, you may observe the loss curve. When the loss decreases slowly and the curve becomes flat, you may stop the training process.
Feel free to add any further questions or comments!

Thanks a lot !

Hi @hongjin-su ,
Just wanted to know whether there is any default support for logging the training loss?
I do not see any log files being generated that captures the training losses.


Increased trailing take profit functionality

It would be awesome if we would be able to specify both the distance to cancel and the distance to execute for the trailing take profit (TTP), that way we can for example change the sensitivity of when we want a new updated higher TTP limit. For example, I was trying to set a TTP of 2% below the current price by specifying the limit price for the sell orders in the config, but that also seemed to alter the difference to cancel making this interval larger. Thus, I would like to skew the difference to execute to be lower from the trigger price than the difference to cancel is.
So, if I want to TTP at 5% for the position in general, I would like to set an updated minimum profit and updated minimum price to sell at if it increases 0.2% more, leading to the minimum profit being updated to 3.2%.
I tried playing around with my position's limit price and stop price for the sell order as I'm still a bit confused from the Wiki on that, but it seem to not allow skewing in the way I try to describe here. It seems like the current behaviour is some form of median so if I have a difference of 1% to cancel from current price (where it does the trigger sell) and 1% to execute, then when it reaches the cancel it seemingly rises with a step of 1% more, whereas what I would love to see is it stepping up i.e. 0.2% more.
If this is possible, this would allow the user to change the sensitivity of the trailing, while keeping a bit higher difference to execute which can be useful in bull-markets like today's scenario.
A second thought I have is dynamic TTP which allows the user to set a minimum initial trailing limit, for example 2% profit as minimum after 5% trigger price, then increasing the limit slowly towards a maximum TTP.
Maybe even have different values depending on if it's for example a strong buy or neutral TV signal.

Hi @dasbts, I had similar reflexions on how to control the spread (between limit and stop price) of a trade. It turns out that even if we give control to the end-user (allowing to apply settings manually), you quickly end-up in a never-ending reconfiguration cycle where you try and adapt to the ever-changing market conditions. Eventually you rarely get it right.
This lead me to think about adding a new trending signal. I'm currently testing HeikinAshi trend signal to restrict from selling in a bullish trend and restrict from buying in ongoing bearish trend. I know this is not the solution you suggest, but if the approach makes a positive difference, I'll submit a PR.

That sounds like a great idea!
Skickat från Outlook för Androidhttps://aka.ms/AAb9ysg

From: rando128 @.>
Sent: Wednesday, February 22, 2023 2:24:10 PM
To: chrisleekr/binance-trading-bot @.>
Cc: dasbts @.>; Mention @.>
Subject: Re: [chrisleekr/binance-trading-bot] Increased trailing take profit functionality (Issue #603)
Hi @dasbtshttps://github.com/dasbts, I had similar reflexions on how to control the spread (between limit and stop price) of a trade. It turns out that even if we give control to the end-user (allowing to apply settings manually), you quickly end-up in a never-ending reconfiguration cycle where you try and adapt to the ever-changing market conditions. Eventually you rarely get it right.
This lead me to think about adding a new trending signal. I'm currently testing HeikinAshi trend signal to restrict from selling in a bullish trend and restrict from buying in ongoing bearish trend. I know this is not the solution you suggest, but if the approach makes a positive difference, I'll submit a PR.
—
Reply to this email directly, view it on GitHubhttps://github.com/chrisleekr/binance-trading-bot/issues/603#issuecomment-1440012134, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJTXKSP5H5P4XN3ANETTX2DWYYHPVANCNFSM6AAAAAAU5M4L3Y.
You are receiving this because you were mentioned.Message ID: @.***>

This lead me to think about adding a new trending signal. I'm currently testing HeikinAshi trend signal to restrict from selling in a bullish trend and restrict from buying in ongoing bearish trend.

I have tried using Heikin Ashi for trading and it did not turn out to be very reliable. It often tends to indicate a reverse in the trend, even though the trend has not ended. SMA is better for this but "sluggish". MACD performed much better, but still not reliable. In general this bot works best, when we are a global uptrend.
And as far as my experience goes, correcting the profit upwards will only work if you drag your stop loss up as well. Taking profit works best if you set yourself a fixed percentage. And you shouldn't care whether or not the price continues to rise above your trigger price. Be disciplined first, before you try to maximize your profit.
The biggest challenge I see, is to configure this bot to buy at the right time.
I'll explain what I see quite often in an example:
Let's assume you would like to trade on the 5m time frame:
The bot "sees" a drop and is buying after Tradingview has signaled that it is on the rise.
Taking a look at the 1h frame, you see that the graph is in a down trend with lots of lower highs and lower lows. During this situation you only make profit as long as you buy at the lower low and sell at the next lower high. Most of the time there are less than 3-4% between the LL and LH. If you wait for TV to signal, there is not a lot of margin left for taking profit. If you are lucky it is 1-2%, mostly less.
Buying when the price is in a down trend conflicts with the 1st rule: "Never trade against the trend.".
You may say: "Well we have grid trades to counter buying against the trend".
Unless you are able put a whole lot of money in there, you can only cover a certain drop percentage of about 10-15% with a margin drop of 1-2%.
And grid trades in my opinion are bad for the following reason:
Imagine you start out with $200 on the first grid. You set your stop loss to 0.978 and your take profit to 1.025. You also have 5 grid trades to cover a 10% drop (so a new grid fires after a 2% drop).
Now let's say the setting works for you 5 times in a row. Which is $25 for the amount of money invested.
 After all grids trades have fired, you have invested close to 4k to cover the drop. If it drops 2.2% more, then stop loss will kick in and you will lose ~$88.
It maybe just be me, who is not able to configure this beast correctly, but I had more consistent profits trading manually.
Trading while taking several Tradingview time frames into account as in #539, may better the situation.

I agree, and yes, caring for margin as well when price drops is definitely a more difficult use case as you also have liquidation. In general tho, it's good to care for confluence in the timeframes, which in my opinion (after trying) is a difficult one to implement as there are then more parameters to care about and it's easy to never get any entry scenario at all.


Add support for Traefik as ingress controller

This adds support for Traefik as an Ingress controller
To use it simply comment the nginx annotations and uncomment the traefik annotations.
Tested with Traefik 1.3.3

Thanks @Miouge1! Do you want this to be released as a new chart version? I'm not sure it makes sense since this is just updating documentation, but if you feel it should then bump the version in Chart.yaml.

Codecov Report

Merging #329 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #329   +/-   ##
=======================================
  Coverage   88.99%   88.99%
=======================================
  Files          15       15
  Lines         618      618
=======================================
  Hits          550      550
  Misses         45       45
  Partials       23       23

Continue to review full report at Codecov.

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

Agreed, I don't think a new version number is necessary either

Ok, in that case I'll merge as-is. Thanks again!


Warning: Unknown prop updateImmediately on  tag. Remove this prop from the element.

<FormsyText
    name="password"
    required
    floatingLabelText="Password"
    type="password"
    updateImmediately
    fullWidth={true}
/>

I get the error:

Warning: Unknown prop updateImmediately on <input> tag. Remove this prop from the element. For details, see https://fb.me/react-unknown-prop
in input (created by TextField)
in div (created by TextField)
in TextField (created by FormsyText)
in FormsyText (created by Login)
in div (created by Login)
in form (created by Formsy)
in Formsy (created by Login)
in div (created by Login)
in div (created by Login)
in div (created by Login)
in Login (created by RouterContext)
in MuiThemeProvider (created by App)
in App (created by RouterContext)
in RouterContext (created by Router)
in Router
in Provider

@lookapanda did you use directly from github? The code withupdateImmediately prop has not been pushed to npm yet.

That explains a lot. Will try out the github version then :) Thanks!


Request: Check the new HA template sensors from the UI

Hi, first of all, many thanks for this project.
In the new HA release (2023.9) there is the possibility to create sensors based on templates from the UI.
More info here: https://www.home-assistant.io/blog/2023/09/06/release-20239/#template-sensors-from-the-ui
These templates are not stored in configuration.yaml, I think that are stored in database,
Therefore, they are not being checked.

I think that are stored in database,

They are stored in "core.config_entries":

I created some sensor:

Then set it to unavailable manually in Dev tools -> Set state, and Watchman does not see it.

Then set it to unavailable manually in Dev tools -> Set state, and Watchman does not see it.

I've just tested it, and Watchman has successfully detected the unavailable UI template sensor when its state is changed via Developer tools.
sensor.test_template_sensor    | unavail | fake_service.yaml:4
The initial request was to include templates from the config_entries registry into Watchman as monitored parts of the configuration. This seems technically feasible, as we already monitor Lovelace UI dashboards which have a similar structure.
The only drawback is that Watchman will not provide additional details to identify these entries besides the line number in the entries registry (the same applies to Lovelace UI config).


Add WDF_STRUCTURE_SIZE macro equivalent

WDF_STRUCTURE_SIZE is a macro available in the WDK, but isn't available in wdk-sys since bindgen can't generate macros. WDF_STRUCTURE_SIZE is useful since many of the _INIT macros are also not available right now. A 1:1 implementation of WDF_STRUCTURE_SIZE should be made available in wdk-sys, although an equivalent shouldn't be needed in wdk given that the safe abstractions shouldn't need to do any of the c-style manual initializations.

I'd like to have a look at this @wmmc88. Would this live in wdk-sys/ntddk.rs?

I'd like to have a look at this @wmmc88. Would this live in wdk-sys/ntddk.rs?

It would live in wdf.rs, however i would hold off on doing anything here yet since we're investigating whether we can look into using bindgen's new clang_macro_fallback feature

Ok no probs! Looking for some places to contribute so I'll keep my eyes open


Seems page 2+ of YakuCorp always has the same cursor value

Run the following and page 2, 3 (and if u do more) they have the exact same value returning, which makes it impossible to page through that accounts tweets
async function TestHandle() {
    try {
        const rettiwt = Rettiwt();
        const user = await rettiwt.users.getUserDetails("YakuCorp");
        const page1 = await rettiwt.users.getUserTweets(user.id);

        console.log("page 1 cursor " + page1.next.value);
        const page2 = await rettiwt.users.getUserTweets(user.id, 100, page1.next.value);
        console.log("page 2 cursor " + page2.next.value);
        const page3 = await rettiwt.users.getUserTweets(user.id, 100, page2.next.value);
        console.log("page 3 cursor " + page3.next.value);

    } catch (e) {
        console.error('Error:', e);
    }

}

I assume as long as the page.next.value is not null then there is a page after, but it seems in this case there is unlimited number of pages but they all same value as page2

Just confirmed. This is actually a problem with getUserTweets method. I will be working on it but because of my ongoing exams, I'll not be able to for 3 more days.
In the meantime, you can use this method to fetch tweets, but this requires you to use cookies.
The problem is, getUserTweets method was implemented as a fail-safe after Twitter required you to login to use advanced search (the best way to fetch tweets is using advanced search). getUserTweets fetches the tweets from the target user's timeline. It is not as polished as fetching from advanced search.
The alternate method that I gave above is the one that uses advanced search, so it will work very well, although it requires using cookie.

Thank you for the reply, I am trying to avoid cookies at all costs as I do not want an twitter account tied to the queries.
I am more interested in technical details on what is required and which calls are required to just get user tweets without any sort of cookies, I like to replicate this functionality in .NET instead of nodejs/typescript calls.
Are you able to provide me with any information on this. I looked at the traffic sent for the call using fiddler/http intercept, i see one call going out to guest end point but couldnt figure out all the headers etc.

I'm back!
Now for the important thing at hand, I check that this 'anomaly' occurs only with the account 'YakuCorp'. All other (afaik) accounts work as intended. Now that I have replicated, I have started debugging.
Expect results soon!

Thank you and if you can figure out how to share the postman calls for the guest calls, I would really appreciate it
I tried looking through inspect but that was a mess as there were many different things being passed. So if you can just provide that.
I think you can manually export collections to json in postman

right click a collection
select export
save file as json
send json file

Thank you and if you can figure out how to share the postman calls for the guest calls, I would really appreciate it
I tried looking through inspect but that was a mess as there were many different things being passed. So if you can just provide that.
I think you can manually export collections to json in postman
right click a collection
select export
save file as json
send json file

API.zip
Here you go.
Not all endpoints have been well documented by me, as it's still a work in progress.


Initialize backingimage and backingimagedatasource sourceType

Fix upgrade failure from v1.1.x to master-head.
The sourceType of backingimage and backingimagedatasource in v1.1.x is "", so initialize it in the mutating webhook.
Signed-off-by: Derek Su<EMAIL_ADDRESS>

@derekbit we should probably need to check if we’d just remove the related empty check conditions if needed.


GH-648 Permit any output to connect to boolean input

Fixes #648

Applied to main (=2.1) and branch 2.0.


Update scala-library, scala-reflect to 2.12.13

Updates

org.scala-lang:scala-library
org.scala-lang:scala-reflect

from 2.12.7 to 2.12.13.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (2.12.7).
You might want to review and update them manually.
.travis.yml

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang" } ]

labels: library-update, semver-patch, old-version-remains

Superseded by #2234.


chat with app for out of k8s cluster user

is this for our gpts?

A requirement, similar to the above, is to share a public link, which should contain the application and authentication information in its parameters.

similar requirement as https://github.com/kubeagi/arcadia/issues/463?

similar requirement as https://github.com/kubeagi/arcadia/issues/463?

463 just want get static chat history,one png or some text。
This issue like encode auth message into url


404 page

Displaying a 404 page when the user navigates to a URL that isn't routed to any other path

[ ] Displays a 404 text and an explanation when navigating to any page that isn't part of the app
[ ] Appropriately styled


WIP Client SDK

This adds client SDK(grpc, rest) for accessing Ark server.
Check commit msg for short desc.
Code is not tested with Ark server running.
Once sdk interfaces are ACKed I can proceed with bellow tasks, or I can handle them in next PRs.
TODO:

[ ] Move client-sdk and api-spec to root
[ ] Test

@tiero @altafan please review.
Closes #192.

No need for grpc-web support, we can drop the grpc-web client too.
@tiero suggested to put the SDK in pkg/client-sdk, is it ok to have it in common? Also, it would be appropriate to create a dedicated module for the SDK (ie cd into client-sdk and go mod init github.com/ark-network/ark-sdk)
Let's proceed then by using the SDK within the CLI, this way we have the integration tests as testing suite for the SDK.

@altafan what about @tiero comment ?

pkg/client-sdk,

yes lets move it in root, not inside common

we can drop the grpc-web client too.

From what I understood, when compiling to WASM targets, we should use gRPC-web like the example I found. Not sure if using JSON interface instead, we can then do code-gen of client stubs like with gRPC and gRPC web?

 I understand browser would then not suppport http2 streaming out of the box, but should not be an issue for unary requets?
Just a curiosity

In the commit that removes grpc-web we are also removing the WASM toolchain and glue code from examples. Can you reintroduce it, but now using the rest package?

lets move client-sdk from common to pkg already as it is being imported by CLI

Let's also create a dedicated submodule:
$ cd pkg/client-sdk
$ go mod init github.com/ark-network/ark-sdk

in client's go.mod we need to add also the following line:
replace github.com/ark-network/ark-sdk => ../pkg/client-sdk

The Admin service is not needed

@tiero @altafan i created sdk and added example.
Note that for REST protocol some of sdk methods wont work cause this is not implemented yet as i need to check if grpc-gateway supports REST(i guess websockets are needed) to Stream.
Also WASM wrapper is missing.
@altafan please check if signing is properly done.
I guess we can work on wallet abstraction and think about if general cleaning of ark_sdk.go is possible so its more maintainable/readable.

this part of code to the SDK too?

Yes would be best to abstract also the storage component with a common interface, so that based in the target (linux server, wasm browser etc..) we can use the most appropriate:

SQLite for simple of deployemnt of Ark nodes
Postgres for enterprise Ark node
IndexDB  for light clients in the browser
AsyncStorage for mobile apps with React native

etc..
Also BitcoinDevKit does the same, and provdes some reference implementations 👇
https://docs.rs/bdk_wallet/latest/bdk_wallet/#persistence
We can have SQLite driver using the native Go impl (which it may also compile to WASM? maybe! big if possible)

Regarding comments:

the "database" management is in the CLI, ie reading the wallet keypair from the json file in the cli datadir.
Considering that we could support an HD wallet with btc-wallet, that comes with a full managed db, wouldn't it be better to move this part of code to the SDK too?

Yes would be best to abstract also the storage component with a common interface

IMO sdk should be stateless(separated from wallet) its not an ark wallet but sdk others can use to create ark wallet which will have persistence.
For this reason i provided Wallet interface as arg to Ark Sdk factory func in here
@tiero @altafan

IMO sdk should be stateless(separated from wallet) its not an ark wallet but sdk others can use to create ark wallet which will have persistence. For this reason i provided Wallet interface as arg to Ark Sdk factory func in here
@tiero @altafan WDYT?

Try to take a look at btcwallet: it is a complete wallet SDK that we used to implement the embedded wallet for the bitcoin version of the service.
It comes with a fully managed db and the operator can decide which kind of db he wants to use. It's super handy and leaves to the dev only the job of creating an interface around the imported package. We want to have something similar for our SDK.
I agree with what tiero suggested in his comment.

A Bitcoin wallet is stateful by nature and the main source of errors is usually efficient caching and retrieval of the UTXO set (or in this case VTXO set eheh)

It's totally ok to define a DB interface and pass the concrete impl when instantiating the SDK

It's totally ok to define a DB interface and pass the concrete impl when instantiating the SDK

@tiero @altafan please review Config and Wallet abstraction, i guess this can be improved, but current solution covers code in cli, we can think of HD wallet abstraction and how to support it.

@tiero @altafan client sdk is working and tested for grpc,rest here and wasm here, bellow u can see wasm example which simulates sending of vtxo's from one wallet to another.


Possible leak with recursive finallys

Hey,
I'm using bluebird latest (version 3.3.1) and there appears to be a leak when using finally to recurse. For example, this keeps leaking promises:
var P = require('bluebird');
function tick() { return P.delay(100).finally(tick); };
tick();

Doing the same recursion with then does not leak promises:
var P = require('bluebird');
function tick() { return P.delay(100).then(tick, tick); };
tick();

Is this a leak, or am I missing something?

For what it's worth, this also happens on 2.10.2 (the version I originally noticed the leak with)

This is actually unfixable given how finally works (not like .then(fn, fn)). Finally has to save the fulfillment value/rejection reason until the promise returned by the finally body is settled.
So you have the equivalent of:
// F1
Promise.delay(100).finally(function() {
    // F2
    return Promise.delay(100).finally(function() {
        // F3
        return Promise.delay(100).finally(function() {
            // F4
            return Promise.delay(100).finally(function() {
                // F5
                return Promise.delay(100).finally(function() {
                    // ...
                }) // Only now can get rid of F5's value/reason
            }) // Only now can get rid of F4's value/reason
        }) // Only now can get rid of F3's value/reason
    }) // Only now can get rid of F2's value/reason
}); // Only now can get rid of F1's value/reason

Each iteration of the loop adds one more value/reason to save while not one of them could be get rid of. So I don't see how it's possible to implement without leaking in this case.

Thanks for looking into it. After a bit more investigating, I understand which property of finally makes this behaviour "by design". Your comment vas very helpful.


Replace base64 with base64ct

The base64ct crate is specifically designed to provide constant-time decoding and encoding of Base64 strings for cryptographic and security-sensitive applications. Since in this crate base64 is used for handling sensitive data, it's probably worth to replace it with base64ct.
Unfortunately, using base64ct would mean MSRV bump to at least 1.51 (for pre-1.3 versions) or to 1.56 for the latest released version.
cc @tarcieri

Doesn't timing-attacks require physical access to the cpu that's parsing the data?
In that case isn't it a bit useless as you would practically have access to everything already?
I am probably missing something important though as it probably exists for a reason.

Doesn't timing-attacks require physical access to the cpu that's parsing the data?

No. Timing attacks over the network (or any medium) are just as readily achieved.

oh, had no idea that was practical, would have thought the differences around it (NIC buffering, routers, switches etc),
would make the range so big that it would be impractical decipher it.
It seems these techniques are more advanced than i thought.
In that case my take on this is to have it as an option (if the performance difference is "big").
And then give some practical example in the documentation on when the user should consider using the securer method/feature compared to the faster basic one:)

Exploiting sidechannels as a network-based attacker is possible. It usually involves a fairly noisy attack which is repeated over and over many times (e.g. millions of times) combined with statistical methods to observe timing variabilities. Such attacks have been used in the past for full plaintext recovery against protocols like TLS e.g. Lucky13 (great paper if you want to see how such attacks work).
However, the most practical attack against a Base64 decoder/encoder is probably going to be a local microarchitectural sidechannel. Such sidechannels have been used in a research setting to recover Base64-encoded cryptographic keys and could still be possible against e.g. a local webserver (possibly on a cotenant container or VM): https://arxiv.org/pdf/2108.04600.pdf

Closing with my commentary at https://github.com/SergioBenitez/cookie-rs/pull/196#issuecomment-1247332479.


[Event Parameter Request] 99000845 "Reservation Management" - OnBeforeDeleteReservEntries

Dear Support,
We would need the ItemTrackingHandling as parameter for the event OnBeforeDeleteReservEntries.
This is what we need:
Original:
    [IntegrationEvent(false, false)]
    local procedure OnBeforeDeleteReservEntries(var ReservationEntry: Record "Reservation Entry"; var DownToQuantity: Decimal; CalcReservEntry: Record "Reservation Entry"; var CalcReservEntry2: Record "Reservation Entry"; var IsHandled: Boolean)
    begin
    end;

New:
    [IntegrationEvent(false, false)]
    local procedure OnBeforeDeleteReservEntries(var ReservationEntry: Record "Reservation Entry"; var DownToQuantity: Decimal; CalcReservEntry: Record "Reservation Entry"; var CalcReservEntry2: Record "Reservation Entry"; var ItemTrackingHandling: Option "None","Allow deletion",Match; var IsHandled: Boolean)
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 11267.


[Fix #8283] Fix length calculation for Style/IfUnlessModifier

Fixes #8283.
Fixes #8226.
Fixes #8025, #8006, #7969 (look like duplicates).

The code to calculate line length for Style/IfUnlessModifier when considering conversion to single-line form now uses the same method that actually computes the replacement. This allows us to take into account a comment on a first line of the if-end condition or some code that is on the same line before the if-condition (which both contribute to the line length).
Added code so that if-end condition that is either an element of an array or a value of a hash now correctly converted to a single-line form with parentheses.

Before submitting the PR make sure the following are checked:

[x] Wrote [good commit messages][1].
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Run bundle exec rake default. It executes all tests and RuboCop for itself, and generates the documentation.

The changes look good to me. Thanks!

Thank you! :heart:


Bulk creation / update

Hi @kocsismate,
I can see that we can GET compound document
https://jsonapi.org/format/upcoming/#document-compound-documents
Can this also be done for creation at the moment ?
Regards,

Hi @waghanza ,
No, unfortunately the spec doesn't have this thing yet. But it has been long time on their roadmap, so JSON:API will probably support this in the future...
I'm closing this ticket for now. :)


Unable to set view to 100% height

Hello,
I am unable to set each swipeable view to a height of 100%.  I would like each swipeable view to have the height of its container.
Is there a way to do this?

Did you had a look at the source code of the demos? For instance the DemoSimple.

In the source code for DemoSimple, minHeight is 100 which sets a value of 100px for min-height on the swipeable view.
However, I need the swipeable view to have a height of 100%, the full height of the container.
Is there another demo that demonstrates how to do this?

I need the swipeable view to have a height of 100%

I don't see where it's the issue. You can add a height: 100% or apply the height of the container to the slide themselves. Have a look at the properties documentation/DOM structure/source. You should be able to customize anything you need.

I bumped into the same issue.
Is there any way to set style of the root element? (the one that holds the overflow-x: hidden)?

nvm, find style attribute of the SwipeableViews

I don't know why this was closed before a solution was given.
I have a solution for those who find this thread from a google search and still are puzzled:
There is another useful property to SwipeableViews: containerStyle. Setting containerStyle={ {height: '100%'} } will get you the container to be full height.


[WIP] Support this gem

Hi, I will run some test and upgrade this gem in order to keep up to date the compatibility.
@lowjoel  I will maintain this project, let me know I can use your repository (there are some issue I will work on)
if you prefer I can create a fork and when the gem is ready, you can just write "Deprecated new one"
I read that you were working on a new release, can you push the code in a new branch?
If there are other users that will contribute, just comment this pull request

Hm. I think it's best for you to write yet another fork. I was hoping to use this but my day job has moved away from using Rails, and I'm struggling to find time to maintain this.
This makes permissions with RubyGems etc. easier, too. I'll update the readme.

Thank you, I will work on this in the next weeks. And update you when the update is ready.

Hi @lowjoel  @Nittarab anything on this yet?
I badly need the fix for on: create as it's breaking and don't want to change the ref to yet another fork

Hi @deepakmahakale  I dont't have had the time to work on it, but I will do it


How to differentiate between making an element as first child and dropping it over the parent?

If i drop a node as first child and if i drop it over the parent, in both the cases i get same information, i.e. from, to.parent and index. So if i want to change the functionality to append a node in the end instead of beginning. How can i do it? I need this difference for allowDrop and drop both.

Hi,
I will add a dropOnNode boolean value to the to object in the coming release

Ok. So if it will be true then it will be on the parent node and if it will be false then it will be first child?

Yes.
Added in 3.7.0

Thank you. You are doing a great job. I am extensively using your library. I wish it gets popular enough like extJs is.


resolved_ts doesn't push forward, it's stuck, which will cause ebs backup failed

Bug Report

What version of TiKV are you using?

What operating system and CPU are you using?

Steps to reproduce

create cluster
do volumebackup

What did you expect?

volumebackup success

What did happened?

volumebackup failed,

[2023/06/15 02:57:43.947 +00:00] [INFO] [raft.rs:384] [newRaft] [peers="Configuration { incoming: Configuration { voters: {} }, outgoing: Configuration { voters: {} } }"] ["last term"=0] ["last index"=0] [applied=0] [commit=0] [term=0] [raft_id=426644] [region_id=242469]
[2023/06/15 02:57:43.947 +00:00] [INFO] [raw_node.rs:315] ["RawNode created with id 426644."] [id=426644] [raft_id=426644] [region_id=242469]
[2023/06/15 02:57:43.947 +00:00] [INFO] [raft.rs:1364] ["received a message with higher term from 415815"] ["msg type"=MsgHeartbeat] [message_term=18] [term=0] [from=415815] [raft_id=426644] [region_id=242469]
[2023/06/15 02:57:43.947 +00:00] [INFO] [raft.rs:1120] ["became follower at term 18"] [term=18] [raft_id=426644] [region_id=242469]
[2023/06/15 05:17:43.969 +00:00] [WARN] [peer.rs:6108] ["leader missing longer than max_leader_missing_duration. To check with pd and other peers whether it's still valid"] [expect=2h] [peer_id=426644] [region_id=242469]

/severity major

/assign @overvenus

Per @overvenus, this problem could be mitigated by PR https://github.com/tikv/tikv/pull/15934


[Possible Bug] Pechs not spawning

So, I started a world with TC6 beta 14, and from the beggining I lived in a Magical Forest, however, I never came across a Pech, I can't even hear the sounds they make, so it seems they are not spawning
Is this a bug or do I only have bad luck?

Yup, they are semi-rare. They do indeed spawn, but aren't particularly plentiful.

Additionally, they may spawn underground, if there's a dungeon or ravine hidden under your feet.

Thanks, that just seemed very unfortunate since I have this world for some weeks now


It should be possible to disable ngf-drop

it should be possible to disable ngf-drop based on a variable value for example:
<div ngf-drop="false">
ngFileUpload.directive('ngfDrop', [
....
link: function (scope, elem, attr, ngModel) {
          if (attr.ngfDrop != "false")
            linkDrop(scope, ....);
        }

Use   ngf-drop-disabled="boolean" // default false, disables file drop on this element
read the docs!


global statement cannot pass compile

Issue description
global statement cannot pass compile

facing the same issue, it is not an issue with ts-node

Same issue here. I can use the Typescript compiler normally, VSCode also does not show me any errors. But with ts-node-dev I can get the application to run because it does not recognize the global declare.

Ok, so apparently I thought it was working with ts-node only but it wasn't. Running both ts-node and ts-node-dev with the --files flag solved the issue for me.


1.55

Our team needs to deploy a Virtual machine that will host a SQL Server. The Virtual machine will
have 2 data disks, one for the log file and the other for the data files. You need to recommend a
caching policy for each disk
Which of the following would you recommend for the data disk containing the logs?
A. None
B. ReadOnly
C. WriteOnly
D. ReadWrite

B

A*


Inline axum-test-helper.

Its dependency tree does not agree with us.
We can simply reproduce the TestClient from the internals of axum ourselves (which is what axum-test-helper does, too).
Our version has even fewer features, because we only need to support GET requests.

Could this be used by other clients of the sdk, like ndc-postgres?

@soupi: Yes, I'd be up for pulling it into a separate crate if we find it useful.


ok.ru no 4k support?

The best thing about ok.ru is, it encodes the videos in 4k so why cant we download 4k via youtube-dl?


Not possible to change appservice plan for existing webapp

Describe the bug
With version 2.0.67 of Azure CLI a pre-validation on webapp name was introduced, preventing the command from executing when a webapp with the same name exists. Effectively blocking for scenarios such as changing a webapps appservice plan.

This is a [BREAKING CHANGE] and should be marked as such in the change log.

This also goes against the command guidelines that states that all CREATE commands should be idempotent. We use Azure CLI for CI/CD to provision all resources and is heavily dependent on create commands being idempotent.
Command Name
az webapp create
Errors:
The site with name [xxx] already exists in resource group [xxx].

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

For any existing webapp
az webapp create --resource-group {} --name {} --plan {}

Expected Behavior
As stated in the guidelines, CREATE command should be idempotent, thus expecting it to execute regardless of the existence of a webapp with the same name.
Environment Summary
Windows-10-10.0.17763-SP0
Python 3.6.6
Shell: powershell.exe

azure-cli 2.0.68

Extensions:
azure-devops 0.11.0
mesh 0.10.6

@yugangw-msft I believe you already fixed this, yes?

@LarsSkovslund I believe this has already been fixed in: https://github.com/Azure/azure-cli/pull/9847.  cc/ @panchagnula

@tjprescott, that is correct. The fix will be released on July 16

Thanks, really appreciate it

Hi all,
Currently all of our releases (hosted agent vs2019) are failing because of this issue in azure cli.
I have set the tasks on app service plan create and app service create on continue on error but
now im facing issues with web app deploy task as well because the app service stays in a running state
So we have to wait for one week until this fix will be pushed to the master?
Grtz,
Ben


Restore deleted DNS request from audit log

Feature Request
Create a new command that allows for detecting deleted DNS records from the audit log and follow the process similar to how the dns cleaner works.

This is no longer possible as Cloudflare does not return the original entry from the audit log.


Describe the behavior with limit_*_batches=1|1.0

What does this PR do?
The behavior for limit_*_batches is wildly different when the user passes 1 vs 1.0. This can be a footgun.
This PR aims to increase transparency by showing a message clarifying the behavior.
In reaction to https://twitter.com/jxmnop/status/1494007900494303243 cc @jxmorris12
Proposed by @williamFalcon
Does your PR introduce any breaking changes? If yes, please list them.
None
Before submitting

[n/a] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[n/a] Did you make sure to update the documentation with your changes? (if necessary)
[x] Did you write any new necessary tests? (not for typos and docs)
[x] Did you verify new and existing tests pass locally with your changes?
[x] Did you list all the breaking changes introduced by this pull request?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

thank you!!!!!


update containerd (1.6.16), CNI plugins (1.2.0), BuildKit (0.11.2), Kubo (0.18.0), etc.

Rootless tests are failing

=== FAIL: github.com/containerd/nerdctl/cmd/nerdctl TestNetworkCreate (0.40s)
    network_create_linux_test.go:50: assertion failed:
        Command:  /usr/local/bin/nerdctl --namespace=nerdctl-test run --rm --net nerdctl-testnetworkcreate ghcr.io/stargz-containers/alpine:3.13-org ip route
        ExitCode: 1
        Error:    exit status 1
        Stdout:
        Stderr:   time="2023-01-28T20:53:18Z" level=fatal msg="failed to create shim: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: time=\"2023-01-28T20:53:18Z\" level=fatal msg=\"failed to call cni.Setup: plugin type=\\\"tuning\\\" failed (add): open /etc/cni/tuning/allowlist.conf: permission denied\"\nFailed to write to log, write /home/rootless/.local/share/nerdctl/1935db59/containers/nerdctl-test/415ce76938b7aa15a6048fcb748db92adb8858f89e82e82dbcc57e39c913ece9/oci-hook.createRuntime.log: file already closed: unknown"

        Failures:
        ExitCode was 1 expected 0
        Expected stdout to contain "<IP_ADDRESS>/24"
        Expected no error


fix(steve/actions): fix missing type attribute of secret resource

Summary
Fixes #9280

Occurred changes and/or fixed issues

Technical notes summary

Areas or cases that should be tested

Areas which could experience regressions

Screenshot/Video

@ly5156 Could you add unit and/or e2e tests for this, please.

@ly5156 There will be some changes requested, there should be / we should make a way to do this without referencing specific resources in the action

@richard-cox
Add a map to the cleanForDownload method that maps kind to the root keys to be removed(as shown in the code below)，otherwise we might need to modify the file in the screenshot.

cleanForDownload action
// secret resource contains the type attribute
// ref: https://kubernetes.io/docs/reference/kubernetes-api/config-and-storage-resources/secret-v1/
// ref: https://kubernetes.io/docs/concepts/configuration/secret/#secret-types
const removedRootKeysMap = {
Secret: [
'id',
      'links',
      'type',
      'actions'
]
}
// remove fields added by steve before showing/downloading yamls
  cleanForDownload(ctx, yaml) {
    if (!yaml) {
      return;
    }
    let rootKeys = [
      'id',
      'links',
      'type',
      'actions'
    ];
    const metadataKeys = [
      'fields',
      'relationships',
      'state',
    ];
    const conditionKeys = [
      'error',
      'transitioning',
    ];
    const obj = jsyaml.load(yaml);

   rootKeys = removedRootKeysMap[obj.kind] ?? rootKeys;

    dropKeys(obj, rootKeys);
    dropKeys(obj?.metadata, metadataKeys);
    (obj?.status?.conditions || []).forEach((condition) => dropKeys(condition, conditionKeys));

    return jsyaml.dump(obj);
  }
};

@richard-cox
Thanks a lot for reviewing and modifying the code.
I've updated the unit test code and it runs as expected!

@aalves08
I've rebased the code, and all checks have passed.


The plugin is not working anymore for latest GitBucket versions

Subj.
GITBUCKET_VERSION | 4.32.0
Will be very nice to have this plug-in up-n-running again.

Fixed by https://github.com/asciidoctor/gitbucket-asciidoctor-plugin/pull/20.

Well done! Thank you very much.


Sync conflict shown - but there is no conflict

Pictures tell more than words:

You said you "restarted" and it didn't go away: what did you restart? Syncthing? SyncTrayzor?

The Conflict Resolver window and the alerts bar use slightly different mechanisms to determine how many conflicted files there are. Both will do an exhaustive scan of your filesystem, but the alerts bar will use filesystem notifications to see when conflict files are added or removed, to avoid lots of scanning. It looks like it might be getting confused when loads of versions of a conflict are deleted at once.... I'll do some testing, try and reproduce.

 It looks like both might be happening at around about the same time...

restart =  I restarted synctrayzor
After some hours the message seems to be away. I will confirm at today afternoon.

restart = I restarted synctrayzor

OK that's really odd. When you restart SyncTrayzor, it will do a full rescan for all conflicted files - exactly the same mechanism that's used when you open the conflict editor.

After some hours the message seems to be away
That also shouldn't happen...

I'm confused. Let me have a bit more of a think, and dig more into your log file.

Interesting: your log file doesn't actually show you resolving any conflicts. Did you use the Conflict Resolver UI to resolve conflicts at any point?

I opened the conflict resolver to see the folders/files. I opened up the foldes and moves the files manually away,

Aha right, that explains that.

I didn't have quite enough logging in 1.1.1 to figure out what was going on.
Would you mind trying the intermediate build available here? https://ci.appveyor.com/project/canton7/synctrayzor/build/<IP_ADDRESS>/artifacts
I've made several changes to how conflict files are found and monitored, so you might not see the issue pop up again. If you do, the log file will contain more useful information.
Thanks!

Quite a lot of fixing has happened in v1.1.2 - please reopen this if you can still reproduce it in v1.1.2. Thanks!


update engine to get fix for dartbug.com/26550

This should fix crashing observatory in --profile mode.


New Feature - Adjusted Probability when using scale_pos_weight

In the documentation, it says that we can use scale_pos_weight to help with unbalanced data, but it shouldnt be used when you care about predicting the right probability.
There is an equation that can be used to turn the predicted probability using scale_pos_weight into the right probability. This would allow for us to use scale_pos_weight, and get the right probability.
Here is the calculation: (app = adjusted posterior probability)

app0 <- (1-prediction) * (A/E) / (C/F)
app1 <- (prediction) * (B/E) / (D/F)
adjusted.prediciton <- app1 / (app1 + app0)
Legend:
prediction = predicted probability for each record
A = Original # of Non-Rare Records
B = Original # of Rare Records
C = New # of Non-Rare Records
D = New # of Rare Records
E = Original Total # of Records
F = New Total # of Records

Would you be able to implement this into the xgboost package? This would be very helpful and i wouldnt need to run this calculation myself on the back end.

You are talking about re-calibration. This can be supported as a post processing step that is rather independent of xgboost package. On the other hand, if you really want to handle imblance data and still get the probability see https://xgboost.readthedocs.org/en/latest/param_tuning.html#handle-imbalanced-dataset

Not related to xgboost, but just for people found this page: the formulas above are incorrect. Should be
app0 <- (1-prediction) * (C/F) / (A/E)
app1 <- (prediction) * (D/F) / (B/E)

Dmitry, you are actually incorrect. You should run through an example and you will see the problem, the original formula is correct. If I used A = 10000; B = 100; C = 100; D = 100; E = 10100; F = 200, and given these 3 predictions: .37, .89, and .46, after running these predictions through the equations I get .0058, .0748 and .0084 respectively, in relation to an original response rate of .0099, these numbers look perfect.
If I use your "corrected" formula, it gives .983, .998, and .988, which are obviously not correct.

@Deom23 Your intuition seems to be wrong. In your case old prior p(y=1) = 0.01, and new prior q(y=1) = 0.5. How do you think the probabilities should change if you know, that you are more likely to get an object of class 1 now? The probabilities should increase, right? In the limit, when q(y=1) = 1, our prediction should be "definitely class 1" p(y|x) = 1 for any x. Looks intuitive to me, while you say the probabilities should decrease 0.37->0.0058.
And of course these formulas are not developed by intuition, and we only check if the result is intuitive. To get sense how it is derived see e.g. p.2.3 of "Classifier Adaptation at Prediction Time", Royer and Lampert. Compare the formulas in the paper with original ones and mine.

Dmitry, I think we are talking about different things. Lets say I am building a logistic probability model, trying to identify buyers from non-buyers. If my universe has 100 buyers and 10,000 nonbuyers. The predictions coming out of this model will average out to .0099, because this is the original response rate of the universe.
In this rare-case scenario, lets say I decide to build a second model, using the same 100 buyers, but only using 100 non-buyers this time, instead of 10,000. The predictions coming out of this model will average out to .5, because this is the new response rate of this smaller universe.
The equations above take the predictions from Model 2, and put them onto the same scale as Model 1. So yes, I fully expect for a prediction of .37 coming out of the second model to be changed to .0058, because this is on the same scale as the original .0099 response rate.
Your equations do not accomplish this, they dont take predictions made from over-sampling and "undo" the over-sampling to put them back on the original scale of the universe.


Requirements: Rework adding / setting of new requirements and its goal to new design

Something in the spirit of this picture:


Title: Create a Concentration game(pair the matching cards)

Is your feature request related to a problem? Please describe.
 The object of the game is to turn over pairs of matching cards.
Describe the solution you'd like.
I will develop a game using javascript with a beautiful UI and try different themes of cards like pokemon, trump, food, cartoons,etc.
Describe alternatives you've considered.
none
Add any other context or screenshots about the feature request here.
Please assign gssoc and level3 labels to this.
Thank You!

@aRUsh-codes Thank you for providing your insight but it is not required as of now


Hue white light via deconz not reporting supported_features correctly

The problem
Phillips Hue WHITE lights controlled via Deconz are all showing supported_features: 0. My color lights are showing the correct value of 63. What is strange is that I can call the light.turn_on service with a brightness value and they work as expected. So something within the last 3 or 4 releases has caused an issue of supported features to be reported incorrectly. This is frustrating as the brightness controls in the UI are not shown and adjusting the brightness using Alex is also not supported.
I was hoping it would be fixed without reporting an issue but it doesn't seem like anyone else is having this problem?
Environment

Home Assistant release with the issue: 0.105.4
Last working Home Assistant release (if known): Probably 0.100 or 0.101
Operating environment (Hass.io/Docker/Windows/etc.): Docker
Integration causing this issue: Deconz
Link to integration documentation on our website:

Problem-relevant configuration.yaml

Traceback/Error logs

Additional information

My Hue white lights works as expected. Can you enable debug and share the detailed logs of the device you say you have this issue with

Sure, I'll do that now.
Just saw this in the logs as well
Sat Feb 15 2020 11:24:17 GMT-0800 (Pacific Standard Time)
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 576, in async_request_call
    await coro
  File "/usr/src/homeassistant/homeassistant/components/deconz/light.py", line 176, in async_turn_on
    await self._device.async_set_state(data)
  File "/usr/local/lib/python3.7/site-packages/pydeconz/deconzdevice.py", line 41, in async_set_state
    await self.async_set(field, data)
  File "/usr/local/lib/python3.7/site-packages/pydeconz/deconzdevice.py", line 48, in async_set
    await self._request("put", field, json=data)
  File "/usr/local/lib/python3.7/site-packages/pydeconz/gateway.py", line 106, in request
    _raise_on_error(response)
  File "/usr/local/lib/python3.7/site-packages/pydeconz/gateway.py", line 220, in _raise_on_error
    raise_error(data["error"])
  File "/usr/local/lib/python3.7/site-packages/pydeconz/errors.py", line 58, in raise_error
    raise cls("{} {}".format(error["address"], error["description"]))
pydeconz.errors.pydeconzException: /lights/18 parameter, /lights/18/bri, is not modifiable. Device is set to off.

Never seen that error message before. Don't forget the device description from the logs

Ping @sberryman

@Kane610 - Sorry for the delay, caught the flu.
Config:
https://github.com/sberryman/homeassistant-config
Logs:
home-assistant.log.zip
Unfortunately I don't have the brain power to look for secrets in the logs, hoping there are not any. Please let me know if you find any.

Get well, and I hope it's not Corona

Well it doesn't report anything but on so the integration assumes it can be dimmed
18': {'etag': '5e9c87c4f7da5cac5d6a2c87a5a244ec',
'hascolor': False,
'manufacturername': 'Philips',
'modelid': 'LWB014',
'name': 'Livingroom Entry Table',
'state': {'alert': 'none', 'on': True, 'reachable': True},
'swversion': '1.29.0_r21169',
'type': 'Dimmable light',
'uniqueid': '00:17:88:01:02:88:2e:81-0b'},

I know that it showed the dimmable slider in the UI until very recently. Although for a number of releases prior to supported_features=0 it would also show the slider at 0% regardless of the current value.

I changed how supported features where calculated to allow for lights without brightness. So 0.105 was first release with that. But it works properly in that no brightness slider is visible now? If you expect brightness in the device from Deconz you need to report an issue on deconz github

I can still dim the lights via automations and calling the service light.turn_on with the brightness parameter. I just can't control them using the UI as the sliders are not shown.
I would be okay with showing the sliders and having each light think it is at 0% as it was prior to 0.105.
But I also understand that deconz should be updated to report the actual brightness level.  A type: Dimmable light should still show the slider I would think. I haven't updated deconz in a while.
Version: 2.05.66 / 6/16/2019
Firmware: 26330500
It appears 2.05.71 is the latest.

After upgrading to 2.05.71 and restarting home assistant the features are reported correctly. Sliders are back and it is reporting the correct brightness levels to HA. Seems to be an issue with the older 2.05.66 I was running.
So sorry for wasting your time, that should have been the first thing I looked at.