HBASE-27401 Clean up current broken 'n's in our javadoc

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ master Compile Tests _

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

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

+1 :green_heart:
compile
9m 31s
master passed

+1 :green_heart:
checkstyle
3m 42s
master passed

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

+1 :green_heart:
spotbugs
10m  5s
master passed

_ Patch Compile Tests _

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

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

+1 :green_heart:
compile
10m 22s
the patch passed

-0 :warning:
javac
0m 41s
hbase-common generated 4 new + 2 unchanged - 0 fixed = 6 total (was 2)

-0 :warning:
javac
0m 49s
hbase-client generated 8 new + 29 unchanged - 0 fixed = 37 total (was 29)

-0 :warning:
javac
2m 52s
hbase-server generated 5 new + 188 unchanged - 5 fixed = 193 total (was 193)

-0 :warning:
javac
0m 37s
hbase-mapreduce generated 7 new + 189 unchanged - 2 fixed = 196 total (was 191)

-0 :warning:
javac
0m 22s
hbase-testing-util generated 1 new + 11 unchanged - 2 fixed = 12 total (was 13)

-0 :warning:
javac
0m 33s
hbase-it generated 2 new + 0 unchanged - 0 fixed = 2 total (was 0)

-0 :warning:
javac
0m 37s
hbase-rest generated 1 new + 152 unchanged - 1 fixed = 153 total (was 153)

+1 :green_heart:
checkstyle
0m 21s
The patch passed checkstyle in hbase-common

+1 :green_heart:
checkstyle
0m 12s
The patch passed checkstyle in hbase-hadoop-compat

+1 :green_heart:
checkstyle
0m 22s
hbase-client: The patch generated 0 new + 73 unchanged - 10 fixed = 73 total (was 83)

+1 :green_heart:
checkstyle
0m 12s
The patch passed checkstyle in hbase-zookeeper

+1 :green_heart:
checkstyle
0m 14s
The patch passed checkstyle in hbase-balancer

+1 :green_heart:
checkstyle
0m 13s
The patch passed checkstyle in hbase-http

+1 :green_heart:
checkstyle
0m 12s
The patch passed checkstyle in hbase-asyncfs

+1 :green_heart:
checkstyle
0m 13s
The patch passed checkstyle in hbase-procedure

-0 :warning:
checkstyle
0m 50s
hbase-server: The patch generated 3 new + 446 unchanged - 2 fixed = 449 total (was 448)

-0 :warning:
checkstyle
0m 16s
hbase-mapreduce: The patch generated 3 new + 75 unchanged - 1 fixed = 78 total (was 76)

+1 :green_heart:
checkstyle
0m 12s
The patch passed checkstyle in hbase-testing-util

+1 :green_heart:
checkstyle
0m 35s
The patch passed checkstyle in hbase-thrift

+1 :green_heart:
checkstyle
0m 13s
The patch passed checkstyle in hbase-backup

+1 :green_heart:
checkstyle
0m 12s
The patch passed checkstyle in hbase-it

-0 :warning:
checkstyle
0m 12s
hbase-rest: The patch generated 1 new + 27 unchanged - 0 fixed = 28 total (was 27)

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

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

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

+1 :green_heart:
spotbugs
11m  5s
the patch passed

_ Other Tests _

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

82m 24s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 6abc1aefd1

Default Java
Temurin-1.8.0_345-b01

javac
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4812/1/artifact/yetus-general-check/output/diff-compile-javac-hbase-common.txt

javac
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4812/1/artifact/yetus-general-check/output/diff-compile-javac-hbase-client.txt

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

javac
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4812/1/artifact/yetus-general-check/output/diff-compile-javac-hbase-mapreduce.txt

javac
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4812/1/artifact/yetus-general-check/output/diff-compile-javac-hbase-testing-util.txt

javac
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4812/1/artifact/yetus-general-check/output/diff-compile-javac-hbase-it.txt

javac
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4812/1/artifact/yetus-general-check/output/diff-compile-javac-hbase-rest.txt

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

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

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

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

modules
C: hbase-common hbase-hadoop-compat hbase-client hbase-zookeeper hbase-balancer hbase-http hbase-asyncfs hbase-procedure hbase-server hbase-mapreduce hbase-testing-util hbase-thrift hbase-backup hbase-it hbase-rest U: .

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

versions
git=2.17.1 maven=3.6.3 spotbugs=4.7.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ master Compile Tests _

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

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

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

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

+1 :green_heart:
javadoc
2m 59s
master passed

_ Patch Compile Tests _

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

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

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

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

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

+1 :green_heart:
javadoc
2m 53s
the patch passed

_ Other Tests _

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

+1 :green_heart:
unit
0m 29s
hbase-hadoop-compat in the patch passed.

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

+1 :green_heart:
unit
0m 32s
hbase-zookeeper in the patch passed.

+1 :green_heart:
unit
8m 48s
hbase-balancer in the patch passed.

+1 :green_heart:
unit
0m 37s
hbase-http in the patch passed.

+1 :green_heart:
unit
1m  3s
hbase-asyncfs in the patch passed.

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

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

+1 :green_heart:
unit
13m 35s
hbase-mapreduce in the patch passed.

+1 :green_heart:
unit
2m 10s
hbase-testing-util in the patch passed.

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

+1 :green_heart:
unit
10m 31s
hbase-backup in the patch passed.

+1 :green_heart:
unit
0m 41s
hbase-it in the patch passed.

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

297m 48s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 6abc1aefd1

Default Java
Temurin-1.8.0_345-b01

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

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

modules
C: hbase-common hbase-hadoop-compat hbase-client hbase-zookeeper hbase-balancer hbase-http hbase-asyncfs hbase-procedure hbase-server hbase-mapreduce hbase-testing-util hbase-thrift hbase-backup hbase-it hbase-rest U: .

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ master Compile Tests _

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

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

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

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

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

_ Patch Compile Tests _

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

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

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

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

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

+1 :green_heart:
javadoc
4m 23s
the patch passed

_ Other Tests _

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

+1 :green_heart:
unit
0m 46s
hbase-hadoop-compat in the patch passed.

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

+1 :green_heart:
unit
0m 43s
hbase-zookeeper in the patch passed.

+1 :green_heart:
unit
9m 55s
hbase-balancer in the patch passed.

+1 :green_heart:
unit
1m 21s
hbase-http in the patch passed.

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

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

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

+1 :green_heart:
unit
16m 36s
hbase-mapreduce in the patch passed.

+1 :green_heart:
unit
1m 54s
hbase-testing-util in the patch passed.

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

+1 :green_heart:
unit
10m 54s
hbase-backup in the patch passed.

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

+1 :green_heart:
unit
3m 38s
hbase-rest in the patch passed.

352m 11s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 6abc1aefd1

Default Java
Eclipse Adoptium-<IP_ADDRESS>+1

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

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

modules
C: hbase-common hbase-hadoop-compat hbase-client hbase-zookeeper hbase-balancer hbase-http hbase-asyncfs hbase-procedure hbase-server hbase-mapreduce hbase-testing-util hbase-thrift hbase-backup hbase-it hbase-rest U: .

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ master Compile Tests _

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

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

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

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

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

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

_ Patch Compile Tests _

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

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

+1 :green_heart:
compile
7m 24s
the patch passed

+1 :green_heart:
javac
0m 30s
hbase-common in the patch passed.

+1 :green_heart:
javac
0m 16s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
javac
0m 34s
hbase-client in the patch passed.

+1 :green_heart:
javac
0m 16s
hbase-zookeeper in the patch passed.

+1 :green_heart:
javac
0m 17s
hbase-balancer in the patch passed.

+1 :green_heart:
javac
0m 18s
hbase-http in the patch passed.

+1 :green_heart:
javac
0m 16s
hbase-asyncfs in the patch passed.

+1 :green_heart:
javac
0m 18s
hbase-procedure in the patch passed.

-0 :warning:
javac
2m 14s
hbase-server generated 4 new + 189 unchanged - 4 fixed = 193 total (was 193)

-0 :warning:
javac
0m 27s
hbase-mapreduce generated 3 new + 184 unchanged - 7 fixed = 187 total (was 191)

+1 :green_heart:
javac
0m 17s
hbase-testing-util generated 0 new + 11 unchanged - 2 fixed = 11 total (was 13)

+1 :green_heart:
javac
0m 34s
hbase-thrift in the patch passed.

+1 :green_heart:
javac
0m 21s
hbase-backup in the patch passed.

+1 :green_heart:
javac
0m 23s
hbase-it in the patch passed.

+1 :green_heart:
javac
0m 23s
hbase-rest in the patch passed.

+1 :green_heart:
checkstyle
0m 12s
The patch passed checkstyle in hbase-common

+1 :green_heart:
checkstyle
0m  6s
The patch passed checkstyle in hbase-hadoop-compat

+1 :green_heart:
checkstyle
0m 13s
hbase-client: The patch generated 0 new + 73 unchanged - 10 fixed = 73 total (was 83)

+1 :green_heart:
checkstyle
0m  7s
The patch passed checkstyle in hbase-zookeeper

+1 :green_heart:
checkstyle
0m  7s
The patch passed checkstyle in hbase-balancer

+1 :green_heart:
checkstyle
0m  8s
The patch passed checkstyle in hbase-http

+1 :green_heart:
checkstyle
0m  6s
The patch passed checkstyle in hbase-asyncfs

+1 :green_heart:
checkstyle
0m  7s
The patch passed checkstyle in hbase-procedure

+1 :green_heart:
checkstyle
0m 32s
hbase-server: The patch generated 0 new + 446 unchanged - 2 fixed = 446 total (was 448)

+1 :green_heart:
checkstyle
0m 10s
hbase-mapreduce: The patch generated 0 new + 75 unchanged - 1 fixed = 75 total (was 76)

+1 :green_heart:
checkstyle
0m  7s
The patch passed checkstyle in hbase-testing-util

+1 :green_heart:
checkstyle
0m 24s
The patch passed checkstyle in hbase-thrift

+1 :green_heart:
checkstyle
0m  7s
The patch passed checkstyle in hbase-backup

+1 :green_heart:
checkstyle
0m  8s
The patch passed checkstyle in hbase-it

+1 :green_heart:
checkstyle
0m  8s
The patch passed checkstyle in hbase-rest

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

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

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

+1 :green_heart:
spotbugs
8m 11s
the patch passed

_ Other Tests _

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

60m  7s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / fa54381cb2

Default Java
Temurin-1.8.0_345-b01

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

javac
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4812/2/artifact/yetus-general-check/output/diff-compile-javac-hbase-mapreduce.txt

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

modules
C: hbase-common hbase-hadoop-compat hbase-client hbase-zookeeper hbase-balancer hbase-http hbase-asyncfs hbase-procedure hbase-server hbase-mapreduce hbase-testing-util hbase-thrift hbase-backup hbase-it hbase-rest U: .

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

versions
git=2.17.1 maven=3.6.3 spotbugs=4.7.2

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

This message was automatically generated.

The remaining javac warnings are not introduced by this PR and the fixes are not straight forward.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ master Compile Tests _

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

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

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

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

+1 :green_heart:
javadoc
2m 51s
master passed

_ Patch Compile Tests _

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

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

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

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

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

+1 :green_heart:
javadoc
2m 50s
the patch passed

_ Other Tests _

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

+1 :green_heart:
unit
0m 29s
hbase-hadoop-compat in the patch passed.

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

+1 :green_heart:
unit
0m 32s
hbase-zookeeper in the patch passed.

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

+1 :green_heart:
unit
0m 35s
hbase-http in the patch passed.

+1 :green_heart:
unit
0m 58s
hbase-asyncfs in the patch passed.

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

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

+1 :green_heart:
unit
13m 18s
hbase-mapreduce in the patch passed.

+1 :green_heart:
unit
2m 12s
hbase-testing-util in the patch passed.

+1 :green_heart:
unit
6m 42s
hbase-thrift in the patch passed.

+1 :green_heart:
unit
10m 36s
hbase-backup in the patch passed.

+1 :green_heart:
unit
0m 42s
hbase-it in the patch passed.

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

289m 41s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / fa54381cb2

Default Java
Temurin-1.8.0_345-b01

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

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

modules
C: hbase-common hbase-hadoop-compat hbase-client hbase-zookeeper hbase-balancer hbase-http hbase-asyncfs hbase-procedure hbase-server hbase-mapreduce hbase-testing-util hbase-thrift hbase-backup hbase-it hbase-rest U: .

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

-0 :warning:
yetus
0m  7s
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 16s
Maven dependency ordering for branch

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

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

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

+1 :green_heart:
javadoc
4m  9s
master passed

_ Patch Compile Tests _

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

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

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

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

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

+1 :green_heart:
javadoc
4m 59s
the patch passed

_ Other Tests _

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

+1 :green_heart:
unit
0m 48s
hbase-hadoop-compat in the patch passed.

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

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

+1 :green_heart:
unit
9m 59s
hbase-balancer in the patch passed.

+1 :green_heart:
unit
1m 13s
hbase-http in the patch passed.

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

+1 :green_heart:
unit
1m 30s
hbase-procedure in the patch passed.

-1 :x:
unit
211m 21s
hbase-server in the patch failed.

+1 :green_heart:
unit
14m  8s
hbase-mapreduce in the patch passed.

+1 :green_heart:
unit
1m 51s
hbase-testing-util in the patch passed.

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

+1 :green_heart:
unit
11m 14s
hbase-backup in the patch passed.

+1 :green_heart:
unit
0m 51s
hbase-it in the patch passed.

+1 :green_heart:
unit
3m 18s
hbase-rest in the patch passed.

313m 13s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / fa54381cb2

Default Java
Eclipse Adoptium-<IP_ADDRESS>+1

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

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

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

modules
C: hbase-common hbase-hadoop-compat hbase-client hbase-zookeeper hbase-balancer hbase-http hbase-asyncfs hbase-procedure hbase-server hbase-mapreduce hbase-testing-util hbase-thrift hbase-backup hbase-it hbase-rest U: .

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.


XSS Found! On "Issuehub.io"!!!!!!!!

Hello Team, I'm Hack3r_Oneness Recently I've found an XSS bug on the "http://issuehub.io/" website.
Vulnerable URL: http://issuehub.io/?label[text]="labels"
Step to Reproduce :

Parameter ?label[text]= is vulnerable to xss
Put this simple payload = "/> in ?label[text]= and BOOM!!!!
As you can see in a snapshot the alert has a popup of domain.

Note: This could be more impactful...
Kindly Contact me on this mail<EMAIL_ADDRESS>

Please contact here<EMAIL_ADDRESS>


MPI and array-valued objectives

This update has 2 features. The first is MPI-parallelized finite-different gradient computation, very similar to stellopt. You can now have multiple VMEC jobs running concurrently, each using multiple processors. For now the MPI communication is coded into simsopt directly; we may want to abstract out the communication later to make things more flexible.
The second update is that the functions going into a LeastSquaresTerm no longer need to return scalars - they can also return 1D numpy arrays. The idea is that if we have a bunch of related terms in the objective function, like the Bmn's for quasisymmetry, they can be represented by a single LeastSquaresTerm.

Thank you Matt!


Add openapi validatior unit tests

What this PR does / why we need it:
Document and validate that the status section should ignore unknown
fields by adding appropriate unit tests. It is an important property of
the update flow which ensures that a newer controller can always write
newer status fields which may not yet be known by all other components.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:
NONE

/lgtm
Wondering how it will work with validation...

Wondering how it will work with validation...

That should not be an issue. We update the CRDs before we update the operators. Here our main issue is that virt-api with the new  validation webhook is rolled out after virt-handler and virt-controller. Also there is the preserveUnknownFields property and CRDs ignore unknown fields on validation always anyway.

Wondering how it will work with validation...

That should not be an issue. We update the CRDs before we update the operators. Here our main issue is that virt-api with the new validation webhook is rolled out after virt-handler and virt-controller. Also there is the preserveUnknownFields property and CRDs ignore unknown fields on validation always anyway.

That should work. Note: You don't want to use preserveUnknownFields because

it's deprecated
crds will not be explainable

/approve

That should work. Note: You don't want to use preserveUnknownFields because

Yes, the CRDs are rolled out first, so should work fine without it.


[FIXED] Subject truncated in message

The issue was when a MSG argument was constructed in several
reads from the socket. An incorrect if conditional was causing
the argument buffer to be reset, resulting in possible storage
of only the end of the subject.
Resolves #141

Coverage increased (+0.09%) to 93.72% when pulling 29ef1f90b67b399e8e63ccbd0bba07b122afa890 on fix_subject_truncated into 1c86a235c6ec57935b5c38fef9f47ba1ea177cfe on master.


fix(attribute): camelCase tabIndex to fix warning

Summary

small fix from renderIcon work, pass tabIndex in attribute as camelcase to fix warning

Acceptance Test (how to verify the PR)

tests pass

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Feat: create get_exchange_rate() method and tests for it

This pull request covers changes that help to implement https://github.com/macxred/cashctrl_ledger/issues/68 issue.

Merging. Thanks a lot!


[BUG] arc export duplicates assay into new study

Describe the bug
When I run arc export on the proteomics samplearc (https://git.nfdi4plants.org/martinkuhl/SampleARC_Proteomics), the output json file contains two studies (see first screenshot):

A "normal" study 01Minimal with filename 01Minimal/isa.study.xlsx
A study assay with filename assay1/isa.assay.xlsx

However, the assay is actually registered in the study, as can be seen with arc a list or arc s list (see second screenshot). Therefore, there should only be one study containing the only assay. The study 01Minimal contains assay1 in the json output, but whithout a process sequence attached, whereas the assay itself (and therefore the second study) does contain the process sequence.
To Reproduce
Run arc export on the proteomics samplearc (https://git.nfdi4plants.org/martinkuhl/SampleARC_Proteomics).
Expected behavior
The output should only contain one assay and one study, with the only assay being part of the only study.
Screenshots

OS and framework information (please complete the following information):

OS: Ubuntu
OS Version 20.04

I think the duplication issue is fixed. However, arc study list stills throws the error

WARNING: The ARC contains following registered studies that have no associated file:

check arc s list on freshly re-built https://git.nfdi4plants.org/brilator/samplearc_rnaseq


[forwardport] Vsphere Template - Creation method defaults to "RancherOS ISO(Deprecated)"

Forwardport of rancher/rancher#24060

Tested with Rancher server rancher\rancher:master-head version 9f8763def
We default to "Deploy from template: Data Center" and "Rancher ISO" is called out as legacy.


process exceptions are returned with http code 200

Description
If an exception occurs in the execution of a process the wps exception report will be returned with http code 200:
https://github.com/geopython/pywps/blob/20e1e254a3f7914e555fa89f363d1f6eb5f3895c/pywps/app/Process.py#L265
Is this indented or should we raise a NoApplicableCode exception with http code 400?
https://github.com/geopython/pywps/blob/20e1e254a3f7914e555fa89f363d1f6eb5f3895c/pywps/exceptions.py#L28
Environment

operating system:
Python version:
PyWPS version:
source/distribution
[ ] git clone
[ ] Debian
[ ] PyPI
[ ] zip/tar.gz
[ ] other (please specify):
web server
[ ] Apache/mod_wsgi
[ ] CGI
[ ] other (please specify):

Steps to Reproduce
Raise an exception in the process, example:
https://github.com/bird-house/emu/blob/master/emu/processes/wps_error.py
Additional Information
See PRs working on exceptions: #358, #406

@jachym @gschwind @tomkralidis thoughts on this?

There are two kinds of exceptions. The InvalidParameterValue etc exceptions are raised before the job is started:
https://github.com/geopython/pywps/blob/master/pywps/exceptions.py
These already return a HTTP code 400.
In our case the exception is raised after the job has started ... maybe in async mode. In this case we can only update the xml status document which is read via the nginx (or apache ...) file-service. I suppose in this case we don't have the chance to set the HTTP code. Right?
ping @huard @davidcaron
So, it might be an issue with the wps 1.0.0 protocol. This is probably different with wps 2.0.0 because the service has a GetStatus request.

This will be fixed when move to the ogcapi rest-api.


Set enumerator missing

Hi
I want to loop through all cards of a specific set, after getting the set by running the code explained in the docs:
Find a set by code:
SetService service = new SetService();
var result = service.Find("ktk");
So the code I try to run to loop through all cards of 'result' set is:
foreach (Card card in result.Value)
{
//do something with the card
}
I get the following error:
Error	CS1579	foreach statement cannot operate on variables of type 'Set' because 'Set' does not contain a public instance or extension definition for 'GetEnumerator'
I'm a C# beginner and can't implement this enumerator myself.
Would it be possible to add a Set enumator so it's possible to get all cards of a Set?
What is the default way now to get all cards of a set (without this enumerator)?
best regards

you are using the wrong service. You need to use the CardService with a query.
cardService.Where(x => x.Set, "ktk");


What is nbproject???

I get these issues while execute make:
$ make
makefile:106: nbproject/Makefile-impl.mk: No such file or directory
makefile:109: nbproject/Makefile-variables.mk: No such file or directory
make: *** 没有规则可以创建目标“nbproject/Makefile-variables.mk”。 停止。

nbproject means it was created using Netbeans (a few years back, did not expect anyone to use this code)
I will have a look when I have some time

Fixed the makefile, run make all to compile now works again. See Readme for updated instructions, also I just added a rather open/user-friendly license


chore: quarantine high-scale IPcache

Quarantine of high-scale IPCache test, fixing the flake documented in https://github.com/cilium/cilium/issues/36323
Once this PR https://github.com/cilium/cilium/pull/36373 deprecating the high-scale ipcache mode is merged, the test will be deleted
Fixes: #36323
Quarantine of high-scale IPcache

/test

/test


avp-helm-container spawns bash processes which do not get terminated

Bug description
After the execution of the defined generate process for helm charts (avp-helm) the executed bash sub-processes are stuck in state "defunct" instead of being terminated.

The number of zombie processes is increasing rapidly and after some hours the process limits within the underlying node gets reached. By reaching the limit the node itself is unusable.
Logs
time="2023-02-01T14:35:34Z" level=info msg="sh -c find . -name 'Chart.yaml' && find . -name 'values.yaml'" dir=/tmp/_cmp_server/98b7b460-f3d6-46e0-af3c-8f1585a50f70 execID=4e02c
time="2023-02-01T14:35:34Z" level=info msg="finished streaming call with code OK" grpc.code=OK grpc.method=MatchRepository grpc.service=plugin.ConfigManagementPluginService grpc.start_time="2023-02-01T14:35:34Z" grpc.time_ms=10.849 span.kind=server system=grpc
time="2023-02-01T14:35:34Z" level=info msg="Generating manifests with no request-level timeout"
time="2023-02-01T14:35:34Z" level=info msg="bash -c helm template $ARGOCD_APP_NAME -n $ARGOCD_APP_NAMESPACE ${ARGOCD_ENV_HELM_ARGS} ${ARGOCD_ENV_HELM_OPTIONS} -f <(echo \"$ARGOCD_ENV_HELM_VALUES\") . |\nargocd-vault-plugin generate -s infrastructure:argocd-vault-plugin-credentials -\n" dir=/tmp/_cmp_server/7e16abb9-c649-49ef-af46-15e5e3d3a716 execID=562f5
time="2023-02-01T14:35:34Z" level=info msg="finished streaming call with code OK" grpc.code=OK grpc.method=GenerateManifest grpc.service=plugin.ConfigManagementPluginService grpc.start_time="2023-02-01T14:35:34Z" grpc.time_ms=78.883 span.kind=server system=grpc

Using the --verbose-sensitive-output parameter did not log more than the logs above (or I did something wrong :D).
Installation setup
Used Dockerfile for image creation
ARG ARGOCD_VERSION=2.5.7
ARG AVP_VERSION=1.13.1

FROM registry.access.redhat.com/ubi8 as download

RUN mkdir /custom-tools/ && \
    cd /custom-tools/ && \
    curl -L https://github.com/argoproj-labs/argocd-vault-plugin/releases/download/v1.13.1/argocd-vault-plugin_1.13.1_linux_amd64 -o argocd-vault-plugin && \
    chmod +x argocd-vault-plugin

FROM quay.io/argoproj/argocd:v${ARGOCD_VERSION} as target

COPY certs.crt /etc/ssl/certs/
COPY --from=download /custom-tools/argocd-vault-plugin /usr/local/bin/

Used values for argocd-vault-plugin sidecar installation
extraContainers:
  - name: avp-helm
    command: [/var/run/argocd/argocd-cmp-server]
    image: <internal-registry>/path/to/image/argocd-vault-plugin-sidecar:<internal tag>
    securityContext:
      runAsNonRoot: true
      runAsUser: 999
    volumeMounts:
      - mountPath: /var/run/argocd
        name: var-files
      - mountPath: /home/argocd/cmp-server/plugins
        name: plugins
      - mountPath: /tmp
        name: tmp-dir
      - mountPath: /home/argocd/cmp-server/config/plugin.yaml
        subPath: avp-helm.yaml
        name: cmp-plugin

Used config for the avp-helm-sidecar-container
apiVersion: argoproj.io/v1alpha1
kind: ConfigManagementPlugin
metadata:
  name: argocd-vault-plugin-helm
spec:
  allowConcurrency: true
  # Note: this command is run _before_ any Helm templating is done, therefore the logic is to check
  # if this looks like a Helm chart
  discover:
    find:
      command:
        - sh
        - "-c"
        - "find . -name 'Chart.yaml' && find . -name 'values.yaml'"
  generate:
    command:
      - bash
      - "-c"
      - |
        helm template $ARGOCD_APP_NAME -n $ARGOCD_APP_NAMESPACE ${ARGOCD_ENV_HELM_ARGS}
        ${ARGOCD_ENV_HELM_OPTIONS} -f <(echo "$ARGOCD_ENV_HELM_VALUES") . | argocd-vault-plugin generate -s
        infrastructure:argocd-vault-plugin-credentials -
  lockRepo: false

ArgoCD example application
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: dex
spec:
  destination:
    namespace: infrastructure
    server: "https://kubernetes.default.svc"
  project: default
source:
  repoURL: <internal-registry>/path/to/chart
  chart: dex
  targetRevision: 0.9.0
  plugin:
    env:
      - name: HELM_VALUES
        value: >-
          replicaCount: 1
          image:
            repository: <internal-registry>/path/to/image/dex
            pullPolicy: IfNotPresent
            tag: ""

          imagePullSecrets:
            - name: container-pullsecret
          config:
            staticClients:
              - id: grafana-client
              secret: "<path:cluster/data/testcluster/dex#grafana-client>"
              name: 'Grafana'
              redirectURIs:
              - https://grafana.domain/login/generic_oauth
      - name: HELM_OPTIONS
        value: '--include-crds'
syncPolicy:
  automated:
    selfHeal: true
  syncOptions:
    - CreateNamespace=true
    - ApplyOutOfSyncOnly=true

How to reproduce

Deploy argocd together with the argocd-vault-plugin by using the above configuration.
Deploy an application which contains avp placeholders like in the example above.
Connect to the avp-helm container and list the running processes by executing:
kubectl exec -it -n <namespace> <pod name> -c <container name (in my case avp-helm)> -- bash -c "ps -ef | head"
Deploy some more helm charts with avp placeholders or update already present applications so that the avp-helm-sidecar has something to do.
Check the number of running sub-processes in state "defunct" and count them, e.g. by using wc -l after listing.
Wait a little and see how the number is growing rapidly. The more apps are deployed, the more zombie processes will be available in a short matter of time.

Expected behavior
I would expect that the sub-processes of the argocd-cmp-server, which are spawned within the avp-helm-sidecar-container, will be terminated after execution instead of being zombies.
Workaround
For a temporary workaround we implemented a cronjob which restarts the argocd-repo-server-pod (which contains the avp-helm-sidecar-container) on a daily basis. Therefore the spawned zombie processes will be killed and the node itself will not reach its process limit.

@werne2j: Thanks for the hint. I'll open up an issue there. Let's see how it goes. :)
I'll leave this issue open until I got some feedback from Argo CD team.

Hi again,
The issue could be fixed with the input I got from the parent ticket I've opened.
I'll create a merge request so that you can takeover the results and other people won't run in the same error. :)


update release webinar link and wording

Update wording and broken release link. Once we get the correct link we will add this back.
Closes https://github.com/kubernetes/website/issues/42563#issuecomment-1679905162
cc @gracenng @divya-mohan0209

Thanks.
/lgtm


Added in drag and drop capability.

Allows the user to drag/drop tabs around in any particular view. Should resolve #167 .

wow that was fast!

Well done! I was thinking to something with animations but that would be much more complicated.
Your implementation is perfect, thank you.


Wrong time zone

Expected Behavior
When I tick off tasks in my list, there is a "Set done date" option. This is supposed to set the correct date next to the task ticked off.
Current behaviour
In my time zone (Germany), the time zone seems to be interpreted incorrectly. Ticking off something at 09:29 am gives me a date that reads 10:31.
The problem occurs in both Windows (11 pro) and Android (12)
Steps to reproduce
Tick off tasks and see what happens
Which Operating Systems are you using?

[X] Android
[ ] iPhone/iPad
[ ] Linux
[ ] macOS
[X] Windows

Obsidian Version
1.0.3
Tasks Plugin Version
1.16.0
Checks

[ ] I have tried it with all other plugins disabled and the error still occurs

Possible solution
None

Obsidian tasks does not work with time, only date. When I mark a task as done, I get 2022-10-31, which is the date of today, October 31.

Thanks Cito for the correct answer.
@feedhopper if you still believe there is a problem, please disable all your other plugins and show us the steps to reproduce the problem.
For now, I’m closing this issue as tasks does not add times, so something else in your vault must be doing this.
If you can give me a numbered list of individual steps that we can follow to reproduce the problem with only tasks enabled, I will of course very happily reopen the issue for investigation.

Oh wow, you are right, please excuse my wrong interpretation. I double checked with both disabling tasks and disabling the "Set done" option within tasks.
What I didn't realize: It showed the date and not the time...

@feedhopper But there are some requests and discussions around adding time stamps to due or done dates already. The "reminder" plugin also supports times.

@feedhopper You can start a thread about that in the discussions section. Obsidian itself is just a platform, it is agnostic of time and task management and does not prescribe or control how it is done. This is up to the plugins and of course becomes difficult when you want to integrate different plugins because they are developed by different persons or teams with different ideas and goals. But if you search the discussion forum, there are already several threads around integration.

@Cito Thanks again! I will do this.
I am new to github and not so familiar with the customs around here. So thanks for pointing me to the right place.


oci: Add conatiner ID to error message

Improve one of the errors returned by getExistingContainerInfo() when
it fails to obtain the container status by including the container ID
in the returned error.
Fixes #735.
Signed-off-by: James O. D. Hunt<EMAIL_ADDRESS>

LGTM

Coverall report: https://coveralls.io/jobs/30354688.
Merging...


[SECURITY-CONCERN]:  Make NuGet repository trustful for windows module installation

Related Problem
I am trying to do a module installation on windows 11. The fact that it returns it as an "untrusted repository" feels discouraging to continue.
The Elevator Pitch
Is this something that can be addressed by NuGet?
Additional Context and Details

PS C:\WINDOWS\system32> Install-Module -Name Microsoft.PowerShell.UnixCompleters
NuGet provider is required to continue
PowerShellGet requires NuGet provider version '<IP_ADDRESS>' or newer to interact with NuGet-based repositories. The NuGet provider must be available in 'C:\Program
Files\PackageManagement\ProviderAssemblies' or 'C:\Users<foobar>\AppData\Local\PackageManagement\ProviderAssemblies'. You can also install the NuGet provider by running
'Install-PackageProvider -Name NuGet -MinimumVersion <IP_ADDRESS> -Force'. Do you want PowerShellGet to install and import the NuGet provider now?
[Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"): y
Untrusted repository
You are installing the modules from an untrusted repository. If you trust this repository, change its InstallationPolicy value by running the Set-PSRepository cmdlet.
Are you sure you want to install the modules from 'PSGallery'?
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "N"):

This is set at a repository level and in my environment is set at a Domain level.
The Public PSGallery repository where anyone can realistically upload any old tat is untrusted but when you connect to the repository in the first place you can define how that repository is treated using the Register-PSRepository cmdlet.
We have an internally hosted copy of the NuGet Repository where we can push trusted scripts and modules for internal use and that repository is trusted by our computers:
 Register-PSRepository -Name YourRepository -InstallationPolicy Trusted -PackageManagementProvider NuGet -PublishLocation 'https://some.url/api/v2/package/' -SourceLocation 'https://some.url/api/v2/'
I would not recommend ever registering the public PSGallery as a trusted repository.


feat(telemetry): Add ability to fetch tags from local kube

copilot:all

Current dependencies on/for this PR:

main

PR #3493

PR #3574   👈

This comment was auto-generated by Graphite.


[Ethereum] Fix baseFee suggestion 0 issue

Add option to pad left when parsing hex string from Ethereum rpc

I would include handling of odd-length, but otherwise valid hex string right in the parse_hex() method.


Skip reporting TPU sigverify stats if no packets received

Problem
No point in submitting datapoints that are empty, especially for nodes that are not leaders and should never receive TPU traffic

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 82.1%. Comparing base (b1b6b9d) to head (3c1cefc).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##           master    #1154     +/-   ##
=========================================
- Coverage    82.1%    82.1%   -0.1%
=========================================
  Files         881      881
  Lines      235749   235750      +1
=========================================
- Hits       193711   193695     -16
- Misses      42038    42055     +17


[pt-BR] Adding on/off lights sentences

Improving tests/_fixtures file
Improving sentences/_common file
Adding sentences to on/off lights domain
Improving on/off responses

Resolve conflicts

Done!

I can't merge changes for 'languages.yaml' 🤷♂

Resolve conflicts

Done!

Try again. Thank you

pytest --language pt-br

Thanks @nikito7 fixing the linting
Right know I think I have fixed all expansion rules I have changed at their respective sentences (liga/desliga/name) to the new ones on __common

I saw you added some test sentences for TurnOn/Off and there are some warnings, maybe I should add a light entity at sala_de_estar to get some coverage?

Try do this first

Done


[CLI] input is ignored, output is misleading

The CI docs mention passing in the commit message.
After trying to set this up in CircleCI, I realized that the CLI completely ignores the input arguments.  It actually reads from the .git/COMMIT_EDITMSG file, which is the last edited commit message for that git client.  In a CI environment, this'll be empty because the VM didn't commit anything.

see https://github.com/conventional-changelog/validate-commit-msg/pull/87

From the releases page, it looks like my best bet is rolling back to 2.12.1 in the meantime?

I believe https://github.com/conventional-changelog/validate-commit-msg/pull/92 should solve the problem. Feel free to give it a shot :)

Cool, I haven't tried it out yet but I've verified 2.12.1 does work.

I'm closing this since https://github.com/conventional-changelog/validate-commit-msg/pull/92#issuecomment-313691307 is merged. Please comment if I'm wrong @maxcnunes @Garbee Thanks.


Rename flake option tree to outputs?

Alternatively, define flake.self? (readonly)
Technically flake.outputs would be accurate, but also an eyesore.

I think it's too late for such an invasive change without a significant benefit.


Support for returning past_key_values from the model

The current implementation allows the passing of a KV cache into the forward functions of the Q\Value models but does not get the KV cache of such a call. This limits the ability to use the KV cache with these models.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

I change the order of variables, and synced the branch with main


Software title translation doesn't work properly

In the recent changes, "for" in title is able to translate. But the translation can't work properly.
On startup, the title is not translated:

After loading up a world, the title changes, in a wrong way:

The title keeps showing in the wrong way afterwards, even if you return to the main menu. Closing and reopening MCEdit will make the title go back to the untranslated stage.

Since this was debated anyway, I just disabled the for translation for the time being.


Add pyproject.toml

HI,
This PR has two purposes:

The following hack for numpy.get_include() is no longer required since we can specify the build environment putting pyproject.toml

https://github.com/lumaku/ctc-segmentation/blob/1170c6ce9e6c6ac23afae33edec14679b785e34f/setup.py#L5-L12

To avoid the following issues, oldest-supported-numpy is used for building instead of numpy: https://github.com/scipy/oldest-supported-numpy

ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject

Numpy-ABI is compatible with newer numpy, but incompatible with older numpy, thus the best practice is to build modules with the oldest numpy.
Fortunately, scipy organizers maintain the  oldest-supported-numpy. I think this way is reliable.
(Alternative solution is, without specifying numpy version in setup.py/pyproject.toml, rather, distributing the wheel file with the oldest numpy)

Thank you for the fix! Merged.


Improving the usability of "Deciders"

list behavior similar to considered options (easy support for several deciders)
add a label


allsky.sh: exit after msg about Bullseye

Exit if the user is running on Bullseye with a Pi.  capture_RPiHQ doesn't support Bullseye yet so they'll get errors.

No longer needed


Adding optimizations to ci tests

-Adding checks for changes to ios and codegen code
-Updating jobs to only run if changes were made in relevant areas of the code

I think it's possible there may be even better ways to handle this where maybe the matrix based jobs can just not run at all instead of starting and skipping steps and then ending, may be something to look into for the future.


update uriBase

Hi
Should update:
const string uriBase = "https://.cognitive.microsoft.com/face/v1.0/detect";
new value:
const string uriBase = "https://.cognitiveservices.azure.com/face/v1.0/detect";

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

ID: 61d93091-7054-48af-bf9a-fe4f6bad231a
Version Independent ID: 419a0e45-3f15-a220-8b16-fa420b464cae
Content: Quickstart: Detect faces in an image with the Azure REST API and C# - Azure Cognitive Services
Content Source: articles/cognitive-services/Face/QuickStarts/CSharp.md
Service: cognitive-services
Sub-service: face-api
GitHub Login: @PatrickFarley
Microsoft Alias: pafarley

Hi @ernestodeltoro, thanks for your feedback! We will review and update this doc accordingly.

@ernestodeltoro thanks for your feedback, the document will be updated accordingly soon.


Added option to disable deploying Cosmos DB and Service Bus

Added an option to our Bicep files to not deploy Cosmos DB and Service Bus. Doesn't change the default (they are deployed by default), but I created this for a test and thought it would make sense to upstream these just in case we could use them in the future.

/ok-to-test

/ok-to-test


Long error message overflows its container in the status area

Description of the bug
While I was working on #751, I found out that a long error message overflows its container in the status area.
A picture is worth a thousand words:

Steps to reproduce

Throw an Error with a long message (the error can be thrown anywhere in the code I think)
The error message does not fit its container in the status area

Expected behaviour
The error message should fit its container in the status area. If the error message is very long, it should be scrollable.
Environment

Indiekit version: forked from main at commit SHA db7012aed4d01fc24439fcb02a5456e9dc003925
Browser: Chrome 125.0.6422.112

Additional context
No response

Not sure why I was preventing details summary text from wrapping; have removed that behaviour from the details component, which is used in the notification component shown here.


Add Clusus Information Solutions Pvt. Ltd., BlackBox Technologies Pvt. Ltd. & Impetus Incorporation Pvt. Ltd.

The website of Segonatech seems to be down and it's facebook page is last updated on 2019. So, I assume they may have shut down their operation.


Typo fixes, and a question

I spotted two typos and fixed them (entires -> entries).
And a question: In the example, shouldn't the string example appear somewhere in the resulting log ("The log now contains these entries")?

Merged, thanks!


Fix player on worldmap continuing to walk after encounter

Probably due to the timer and the state being set after an encounter is triggered, so when it is resumed it continues where it left off.
Starting an encounter or otherwise exiting the worldmap should reset the state. In addition, it should lock the player from being able to mark a destination while it's paused/loading the encounter.

Related to #63.


provision a Kubernetes cluster to deploy into

Details and Assumptions

[document what you know]

Acceptance Criteria
Given [some context]
When [certain action is taken]
Then [the outcome of action is observed]

I think we can write something like :
As a User
I need the service to be publicly available on Kubernetes
So that I can use it from the Internet
Additionally, can we consider it as user enhancement ?

Hey team! Please add your planning poker estimate with ZenHub @dggjsc @mpourostad @xiaokailll @yuluqinn


enforceDomains option based on emailDomain

Implemented https://www.pivotaltracker.com/n/projects/997278/stories/152248593

Added a boolean enforceDomains identityProvider property to restrict or not the logging in users based on their email address domain matching with the existing emailDomain identityProvider property.
Refactored the ExternalLoginAuthenticationManagerTest test class to make it easier to add the tests related to that new feature. All the existing tests were kept and their logic unchanged.
Added a bunch of Builders to help with tests readability and maintainability (only used in ExternalLoginAuthenticationManagerTest)

Default general behavior is the same: enforceDomains is false by default.

@pdelagrave fyi the CI test suite failed ^

Out of travis 12 jobs in the build, 4 failed:

8319.2
Failed test: org.cloudfoundry.identity.uaa.oauth.UaaTokenServicesTests#testCreateAccessTokenRefreshGrantAllScopesAutoApproved
It passes on my workstation, flake or environment difference?

8319.4
Connect to repo.maven.apache.org:443 [repo.maven.apache.org/<IP_ADDRESS>] failed: connect timed out

8319.6
curl: (7) Failed to connect to nodejs.org port 443: Connection timed out

8319.10
Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to repo.maven.apache.org:443 [repo.maven.apache.org/<IP_ADDRESS>] failed: connect timed out

@pdelagrave possible to rebase/remove conflicts and see if it passes tests?

Closing due to inactivity.


Blind control not showing correct cover level

Home Assistant version (if applicable):
0.91.1
Describe the bug
When controlling the blind (HMIP-BROLL) via home assistant and setting e.g. 50% level it is working fine and the state in HA switches to 50%.
When controlling the blind via the switch on the HMIP-BROLL, the state in HA switches to 100% or 0% and nothing in between.
But the correct level is available and transmitted to HA, but I guess not in the right place:
2019-04-24 21:22:47 INFO (Thread-2) [pyhomematic.devicetypes.generic] HMGeneric.event: address=1234:3, interface_id=homeassistant-ip, key=LEVEL, value=0.24
2019-04-24 21:22:48 INFO (Thread-2) [pyhomematic.devicetypes.generic] HMGeneric.event: address=1234:4, interface_id=homeassistant-ip, key=LEVEL, value=1.0
2019-04-24 21:22:48 DEBUG (Thread-2) [homeassistant.components.homematic] 1234 received event 'LEVEL' value: 1.0
As you can see in the log the correct level is present in the address=1234:3 level (0.24), but not in the address=1234:4 level (1.0). pyhomematic should tell HA to take the 24% as the new level.
Since I'm new to homematic I don't get the difference between the :3 and :4 address - I hope you can help.
Thanks for this great pyhomematic!

Since I don't own such devices I'll tag this as help wanted, so anyone with such a device can participate in fixing this. 👍

Can you give me sme hints on how to debug and approach this? I'd be happy to help! :)

It looks like that it is kind of a bug in the homematic firmware, but it should be possible to get the current level out of channel 3 instead of channel 4 that is currently used by pyhomematic:
https://homematic-forum.de/forum/viewtopic.php?f=58&t=47868

That would be a hack to fix something that is broken in the device. Implementing such a fix could potentially break other blind-actors that don't have that problem. On top of that, it somehow has to be detected that the problem is present. I doubt this can be achieved without great impact on the startup performance. Especially given that HomeMatic IP devices are known to cause problems when looking at their configuration details. Have a look at this issue for more information about that.

Can you give me sme hints on how to debug and approach this? I'd be happy to help! :)

Have a look at example.py and 8actors.py](https://github.com/danielperna84/pyhomematic/blob/master/pyhomematic/devicetypes/actors.py). You would have to modify the class that your device inherits its features from.

Do you know an easy way to test the idea I have for fixing this?
I can't get the pyhomematic Code to be overridden by my Code in home assistant environment (I thought I can just out it in as a custom components). :(

Ideally you should set up a development VM completely separate from your productive Home Assistant. You can use these instructions on how to set up a development environment. You can't / shouldn't do that with a custom component. Modify the existing component.

OK Thank you!
I'm currently testing a few ways on how to solve this and I have a question:
https://github.com/danielperna84/pyhomematic/blob/8b91f3e84c83f05d289c740d507293a0d6759d8e/pyhomematic/devicetypes/generic.py#L330
Shouldn't the channel parameter be used as a override when it is handed in to _getNodeData()? Or do I understand it wrong and it has another functinality? What is this channel parameter for?
If this would be the case, I could just override the get_level() in IPKeyBlind with using channel 3.
It does not seem to be a bug per se in the HmIP-Broll, it seems to be always the case that the level has to be set with channel 4, the result is than stored in channel 3 (see docs). The "sync" to channel 4 just seems to be buggy and just work in some circumstances.

Shouldn't the channel parameter be used as a override when it is handed in to _getNodeData()?

Yes. If you don't provide a channel, then a default value (nodeChannelList[0])  is being used. It's for simpler devices where this way it's possible to just not specify a channel and it still works.

If this would be the case, I could just override the get_level() in IPKeyBlind with using channel 3.

Yes. But in the thread you have mentioned it's stated, that this problem only appears with devices where Expertenmodus has been toggled. At least to me it seems as if everything works fine for regular users. And the highest priority is to retain functionality for the majority of users.
As far as I understand, the extra channel for your device is a virtual actor channel that is misbehaving. Not everybody has those activated, and implementing a fix that uses them wouldn't work for most people. So there needs to be some mechanism to actually figure out if the fix is needed. After all the device itself has been supported for a while, and until yet nobody has reported this problem.
Try to implement a fix, and then we'll see if anyone with the same device experiences problems. 👍

Yes. If you don't provide a channel, then a default value (nodeChannelList[0]) is being used.

The way it is implemented currently, channel parameter is only used if nothing is in nodeChannelList. I will include this fix in my PR.

At least to me it seems as if everything works fine for regular users.

Yes but according to the specification the level is always maintained in channel 3, therefore it should not make a problem for other users.
To be honest, I don't really need the expert mode but I can't turn it off without the ccu2 gui (I'm only using a docker container xml api).
I will create a PR that fixes the problem at least when used from the pyhomematic command line. In home assistant it is still not shown correctly but this has nothing todo with this framework anymore I guess.

The way it is implemented currently, channel parameter is only used if nothing is in nodeChannelList.

Huh? The line is: nodeChannel = channel if channel is not None else nodeChannelList[0]
According to my understanding that means:

Use channel if it is provided with the call and it's not None
Otherwise use the value of nodeChannelList[0]

The other case is in the line below, which will be used if nodeChannelList only has a length of 1, so only one channel is defined for the device. If only one channel is available, then overriding the channel wouldn't make sense.

Yes but according to the specification the level is always maintained in channel 3, therefore it should not make a problem for other users.

I don't think you can rely on the specification too much. I for example have a HMIP-PSM, which is a switch. The transmitter is on channel 2, but in pyhomematic channel 3 (the first virtual receiver) has to be used in order for the device to be controllable.
For your HMIP-BROLL the transmitter is on channel 3, and the first virtual receiver on channel 4. And when it has been implemented (I don't know by whom), channel 4 has been used. So to me it seems as if in terms of channel functionality our devices are comparable. And looking at other devices this scheme is also used. It's always the first virtual receiver channel after the channel that should be the correct one that works in pyhomematic (XML-RPC). 🤔
Anyways, we'll see what other BROLL-users report about your change. 👍

Yes, but if an override is handed in it makes sense to use it and it doesn't matter how many other values are present I think?
Hm unfortunately I can't get it working in home assistant even with my proposed fix. HASS is not using the get_level() or set_level() methods of pyhomematic, but is using some one logic if I see it right.

Yes, but if an override is handed in it makes sense to use it and it doesn't matter how many other values are present I think?

Yeah, makes sense. Although I'n not sure if other parts of the code might rely on it working this way. 🤔

HASS is not using the get_level() or set_level() methods of pyhomematic, but is using some one logic if I see it right.

A callback function is used. The CCU / Homegear sends events to HASS. They are handled here. Which is actually the biggest problem you might be facing. The entity in HASS is pretty much bound to a single channel. It's not built in a way that the state is received for channel a, but written on channel b. In the HASS ecosystem those would be two separate entities, where one would be a read-only representation of the device-state, the other a write-only entity to modify the state. But that would be pretty useless.

A callback function is used. The CCU / Homegear sends events to HASS. They are handled here. Which is actually the biggest problem you might be facing.

After some thinking and trying I given up whit adapting the homematic component in a meaningful way. Big changes would be necessary that would never be merged into the project.
I now ended up "hacking" the init.py:_subscribe_homematic_events() so that it subscribes to channel 3 instead of 4 for all of my blinds. Built-In HASS components can simply be overriden by copying them to the custom_components folder.
Just if someone will ever run into the same problem... :)
Thanks anyway!

Just if someone will ever run into the same problem... :)

lud-hu, I did run into the same issue.
The HA sliders are behaving strange with HmIP-FROLL and -BROLL - just as you described in your entry post. The status is changing from to 0% to 100% whenever stopped at or sent to values  in between.
How did you solve this issue?
I'm running a Home Assistant 0.101.2. on HassOS 2.12, HomeMatic is running on CCU3.
Any would be highly appreciated.

Hi @basekk,
sorry for the late response.
As described, I added some lines to init.py:_subscribe_homematic_events() of the homematic component (you can just copy it to your configuration to overwrite it):
        # Set callbacks
        for channel in channels_to_sub:
            # DIRTY-HACK
            # Check if the device is any of my covers and if the channel to subscribe is 4
            # then change it to 3:
            if (channel == 4) and ((self._name == "001118...") or (self._name == "001118...") or (self._name == "001118...")):
                channel = 3

You can find the file here: https://github.com/home-assistant/home-assistant/blob/5f177fa42e48f298400b45725926da6f2ffb8e72/homeassistant/components/homematic/init.py#L1003

If this would be the case, I could just override the get_level() in IPKeyBlind with using channel 3.

Yes. But in the thread you have mentioned it's stated, that this problem only appears with devices where Expertenmodus has been toggled. At least to me it seems as if everything works fine for regular users. And the highest priority is to retain functionality for the majority of users.

That conclusion was wrong: Expert mode only changes the display of the CCU's WebUI. It does not change any values reported by the XML-RPC API. Therefore it's broken for everybody, including regular users.

Seems to me that updating the ccu3 to firmware 3.53.26 fixed the issue.
At least HA 0.114.0 with CCU3 3.53.26 is working.
Can someone confirm? @mtdcr @lud-hu @basekk

@leinich After upgrading my CCU3 to 3.53.26 some HmIP-BROLLs (latest firmware) regularly have communication issues with CCU3 and also Home Assistant shows them as "unavailable" then. I already created a ticket at eq-3.
Besides that it doesn't seem to fix the issue with the incorrect cover level for me. When I use the BROLL push buttons directly Home Assistant still shows 100 or 0. (I saw some new (for me) configuration options in the BROLL configuration in CCU3, did not have time yet to check if this might fix it)

Same issue here with the HMIP-BBL (blind actuator with position+tilt) + CCU3.
Just want to make sure that this issue is kept open a little longer.
Like everyone else in this thread I tried all kinds of combinations (with/without expert mode, all kinds of resets, ...), I even did something not mentioned here before: I changed the original direct link of the HMIP-BBL which uses expert mode to a simpler one (non-expert), but without any luck.
I spent quite some time in the logs and it all makes sense now. Truth seems to be:

Channel 4 should not be used at all for these devices for reading the state, only for setting values
Channel 3 has to be used for getting current position/tilt
It's not a bug, but intended. In fact, what I see in various forums is that more IP devices are about to change to this kind of behaviour and we should therefore start splitting the read and write channels more clearly both in pyhomematic, but also in the consuming libraries like the homeassistant core component. E.g., by specifying the Sensornodes more often in pyhomematic and stopping to use Writenodes for event subscriptions in (e.g.) homeassistant core component

Any thoughts? I'm glad to help, but would wait for some guidance regarding the way forward from the experts

@rbloehm
I'm actually at a point where I think it might make more sense to completly re-do the HomeMatic integration.
What I have in mind so far:
pyhomematic (or an alternative project to have a clear separation) should only act as a communication interface. A little bit like MQTT. There are a ton of device categories with MQTT support available in Home Assistant, and the logic is implemented in Home Assistant, not the MQTT broker.
To make things a bit easier, the new pyhomematic should also read and store all the paramsets of all detected devices. Essentially a cache (autobuilt on first connection, then refreshed on demand). By using this cache, the library could tell Home Assistant: "the parameter STATE is boolean and read-only" (which would be a binary sensor), "the parameter STATE is boolean and read-write" (which would be a switch), OR do it differently if you have a more specific device-dependent implementation in the code.
Eventually my goal with this approch would be, that practically all devices will be supported in at least some simple form, and only complex devices like thermostats will be handled differently. And as said before, not in the library, but in the consumer of the library. Only because pyhomematic initially happened to be build for Home Assistant doesn't mean the application-specific stuff has to be done in the library in my opinion. The result is a split-brain situation where problems could be either inside pyhomematic or in Home Assistant. And I heavily vote for keeping things separate. On top of that, there wouldn't be the requirement to always first update pyhomematic with support for a new device, and then update Home Assistant with the new pyhomematic version and possibly some device-specifiv stuff (like new classes) which sometimes is needed as well.
This new library then could be used in a custom Component while it's being developed. Along with a GUI to setup in Home Assistant. And when it reaches a stable form, it could replace the existing integration.
I would also set the entities to be named af if the resolvenames option is turned off. This will result in stable and uniqe entity IDs. The friendly-names then can be applied as the customizable friendly names. The way it is now is mainly driven by the way Home Assistant was years ago when the HomeMatic integration was first introduced. Much has changed since then, so things can be done differently now.
That being said, I'm aware that the HA-Devs want to keep out device-specific stuff as much as possible. So maybe there could be an additional library which does device-specifiy stuff. But I think it makes more sense to do logic within Home Assistant. The way it is now there are tons of callbacks registered to handle the events. It would be way more efficient if Home Assistant would just have one listener for the events, which passes the state changes to the correct entity. The entity logic would then know how to make use of the new value. In case of the blind actuators for example the entity-code would check the device-type (read-write on one channel or on different channels) and update the entity accordingly.
Obviously this would take a lot of work on the Home Assistant side. Simplifying pyhomematic to just do the messaging could be done fairly easy I guess. I actually already started doing that (the simplified pyhomematic) a while ago, but didn't find the time to finish it yet. Maybe during the holidays.
What do you think?
Mentioning @pvizeli to let him know about my thoughts on this.

As this issue is open for more then 2 years now, I want to give some other desperate people some hints how to fix this the "ugly way". Beware of this issue before continuing: https://github.com/home-assistant/core/pull/44620#issuecomment-752181772

Download the current folder core/homeassistant/components/homematic/ folder for your installed core version.
e.g. https://github.com/home-assistant/core/tree/2021.6.4/homeassistant/components/homematic
(can be downloaded easily with https://download-directory.github.io/)
Create a folder config/custom_components/homematic on your home assistant machine
Copy content from downloaded folder from step 1 to folder from step 2
Replace this function in homeassistant/components/homematic/entity.py.
Source: https://github.com/home-assistant/core/pull/44620

    def _subscribe_homematic_events(self):
        """Subscribe all required events to handle job."""
        # Ordered list of nodes to determine priority when subscribing to
        # events. Only one channel per parameter should be subscribed to
        # to avoid jumping values.
        # E.g., if a sensor node is given, that one should be used.
        # Highest priority is on the bottom
        node_priority = [
            self._hmdevice.ACTIONNODE,
            self._hmdevice.EVENTNODE,
            self._hmdevice.WRITENODE,
            self._hmdevice.ATTRIBUTENODE,
            self._hmdevice.BINARYNODE,
            self._hmdevice.SENSORNODE,
        ]

        def _channel_list_to_single_channel(channel_list):
            if len(channel_list) == 1:
                return channel_list[0]
            return self._channel

        channel_dict = {
            node: _channel_list_to_single_channel(channels)
            for metadata in node_priority
            for node, channels in metadata.items()
            if node in self._data  # Data is needed for this instance
        }

        for node, channel in channel_dict.items():
            # Remember the channel for this attribute to ignore invalid events later
            self._channel_map.add(f"{node}:{channel!s}")
        _LOGGER.debug("Channel map for %s: %s", self._address, str(self._channel_map))

        # Set callbacks
        self._hmdevice.setEventCallback(callback=self._hm_event_callback, bequeath=True)

insert version to config/custom_components/homematic/manifest.json
as this a custom integration now and no longer a core integration
https://developers.home-assistant.io/docs/creating_integration_manifest/#version

As this issue is open for more then 2 years now, I want to give some other desperate people some hints how to fix this the "ugly way".

@sVnsation Works like a charm. Thanks a lot.
Now I can remove my other "ugly hacks" since this one is much better (so far).

Hello Guys, thx for the "solution" however I cannot locate core/homeassistant/components/homematic/ folder. I integrated homematic just in the configuration.yaml with a few lines of code.
What do I have to do?
thx in advance!

Thank you @sVnsation for this solution. I implemented this on Home Assistant core-2021.9.7 supervisor-2021.09.1 with Raspberrymatic CCU as Docker container.
If i change the position within the homematic CCU the value is correct in Home Assistant. If i use the Home Assistant to change the position i have the "old" behavior: 0 or 100 only. Any idea/hint?

@chises Whats your version downloaded in step 1? The example link leads to 2021.6.4.

i used 2021.9.7 with the following link:
https://download-directory.github.io/?url=https%3A%2F%2Fgithub.com%2Fhome-assistant%2Fcore%2Ftree%2F2021.9.7%2Fhomeassistant%2Fcomponents%2Fhomematic

Currently i'm on the failry old piVCCU version 3.47.15
But any time soon in the next weeks i also plan to migrate to the rasperrymatic addon inside HA and HB-RF-USB.
I will report back if the solution still works.
In the mean time enable logging in the configuration.yaml:
logger:
  default: info
  logs:
    homeassistant.core: debug
    homeassistant.components.mqtt: debug

Look for the entries "Channel map for..." and post the log.

I am sorry, but the whole log file does not contain something like "channel map".

The log should start with something like
2021-09-22 18:38:02 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration homematic which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

@lud-hu @basekk @djm193 @chises
Please vote for this Pullrequest https://github.com/home-assistant/core/pull/56619 to get this finally fixed.

If the log file does not contain something like "channel map", then the custom_component isn't loaded.
The log should start with something like
2021-09-22 18:38:02 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration homematic which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

Found m issue, missed a "," in my manifest. I am sorry, everything is working!

for me the problem solved with auto calibration on device parameter in ccu3

Blind-devices are working properly with the new integration, therefore closing this issue.


"Unexpected Error"

Not really an issue, but maybe something for documentation on the integration.
I was getting "Unexpected Error" when attempting to set up the SmartCocoon integration. I set the integration up through HACS, but when I attempted to set up the integration, at the point where you enter your username and passport, I received an "Unexpected Error" message.
Turns out I needed to open MQTT port (TCP 1883) outbound from Home Assistant. I'm sure most people have outbound ports fully open from HA, so probably not an issue for most people.
Here are the log error details from HA:
Logger: custom_components.smartcocoon.config_flow
Source: custom_components/smartcocoon/config_flow.py:37
Integration: smartcocoon ([documentation](https://github.com/davecpearce/hacs_smartcocoon/blob/main/README.md), [issues](https://github.com/davecpearce/hacs_smartcocoon/issues))
First occurred: 4:03:46 PM (5 occurrences)
Last logged: 8:23:34 PM
Unexpected exception

Traceback (most recent call last):
  File "/config/custom_components/smartcocoon/config_flow.py", line 73, in async_step_user
    info = await validate_input(self.hass, user_input)
  File "/config/custom_components/smartcocoon/config_flow.py", line 37, in validate_input
    if not await scmanager.async_start_services(
  File "/usr/local/lib/python3.10/site-packages/pysmartcocoon/manager.py", line 82, in async_start_services
    await self._fans[fan_id].async_start_services()
  File "/usr/local/lib/python3.10/site-packages/pysmartcocoon/fan.py", line 441, in async_start_services
    self._mqttc.connect(
  File "/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py", line 914, in connect
    return self.reconnect()
  File "/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py", line 1044, in reconnect
    sock = self._create_socket_connection()
  File "/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py", line 3685, in _create_socket_connection
    return socket.create_connection(addr, timeout=self._connect_timeout, source_address=source)
  File "/usr/local/lib/python3.10/socket.py", line 845, in create_connection
    raise err
  File "/usr/local/lib/python3.10/socket.py", line 833, in create_connection
    sock.connect(sa)
TimeoutError: timed out

Hi Sean
Thanks for letting me know. The integration is not actively using MQTT at the moment. That code is there to try and get updates from the fan if you control it via the SmartCocoon app but unfortunately the way the integration uses the credentials it’s hard to use their app and the integration logged in at the same time.
I have some dependency updates to make to the code I just haven’t had any time. I will look at the code to make sure I’m not actually calling the MQTT code at all. Sorry but I may not be able to get to this until the weekend.
Regards
Dave
On May 29, 2024, at 8:45 PM, Sean Baker @.***> wrote:

Not really an issue, but maybe something for documentation on the integration.
I was getting "Unexpected Error" when attempting to set up the SmartCocoon integration. I set the integration up through HACS, but when I attempted to set up the integration, at the point where you enter your username and passport, I received an "Unexpected Error" message.
Turns out I needed to open MQTT port (TCP 1883) outbound from Home Assistant. I'm sure most people have outbound ports fully open from HA, so probably not an issue for most people.
Here are the log error details from HA:
Logger: custom_components.smartcocoon.config_flow
Source: custom_components/smartcocoon/config_flow.py:37
Integration: smartcocoon (documentation, issues)
First occurred: 4:03:46 PM (5 occurrences)
Last logged: 8:23:34 PM
Unexpected exception
Traceback (most recent call last):
File "/config/custom_components/smartcocoon/config_flow.py", line 73, in async_step_user
info = await validate_input(self.hass, user_input)
File "/config/custom_components/smartcocoon/config_flow.py", line 37, in validate_input
if not await scmanager.async_start_services(
File "/usr/local/lib/python3.10/site-packages/pysmartcocoon/manager.py", line 82, in async_start_services
await self._fans[fan_id].async_start_services()
File "/usr/local/lib/python3.10/site-packages/pysmartcocoon/fan.py", line 441, in async_start_services
self._mqttc.connect(
File "/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py", line 914, in connect
return self.reconnect()
File "/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py", line 1044, in reconnect
sock = self._create_socket_connection()
File "/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py", line 3685, in _create_socket_connection
return socket.create_connection(addr, timeout=self._connect_timeout, source_address=source)
File "/usr/local/lib/python3.10/socket.py", line 845, in create_connection
raise err
File "/usr/local/lib/python3.10/socket.py", line 833, in create_connection
sock.connect(sa)
TimeoutError: timed out
—
Reply to this email directly, view it on GitHubhttps://github.com/davecpearce/hacs_smartcocoon/issues/156, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEHDT2Y6VBLX7SHN4KJFA73ZEZZBLAVCNFSM6AAAAABIP5U6BSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMZDINBUG42TGNQ.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Not a problem for me, I only intend to control the fan via HA and your code works perfectly for that purpose. Thanks so much for your work on this project!

Hi Sean
Isaac this the first time you are trying the integration or had you been using it before?
Regards
Dave
On May 30, 2024, at 7:33 AM, Sean Baker @.***> wrote:

Not a problem for me, I only intend to control the fan via HA and your code works perfectly for that purpose. Thanks so much for your work on this project!
—
Reply to this email directly, view it on GitHubhttps://github.com/davecpearce/hacs_smartcocoon/issues/156#issuecomment-2139358207, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEHDT243KYOMDL7XSMZY57LZE4FA3AVCNFSM6AAAAABIP5U6BSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZZGM2TQMRQG4.
You are receiving this because you commented.Message ID: @.***>

First time for me, I just received a SmartCocoon register fan yesterday. So while I don't have much experience with the integration, it seems to be working well so far.

Hi Sean
I released a new version of the integration. You need v1.1.0. Let me know if this resolves your MQTT issues.
Regards
Dave
On May 30, 2024, at 9:48 AM, Sean Baker @.***> wrote:

First time for me, I just received a SmartCocoon register fan yesterday. So while I don't have much experience with the integration, it seems to be working well so far.
—
Reply to this email directly, view it on GitHubhttps://github.com/davecpearce/hacs_smartcocoon/issues/156#issuecomment-2139598816, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEHDT237BUGBIZSAUQDXOQTZE4U2RAVCNFSM6AAAAABIP5U6BSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZZGU4TQOBRGY.
You are receiving this because you commented.Message ID: @.***>

I don't have the issue now because I opened up the MQTT port on my firewall. Are you saying the code has been changed so that outbound MQTT is no longer required during the initial configuration of the fan? I can probably test this if you want, but I'd probably need to go through the initial configuration process for the integration again because I was getting the error when I first set up the integration. Thank you.

Yes I removed the functionality for MQTT. It wasn’t actively being used in the integration and needed a rewrite anyway.
Glad it’s working for you.
On Jun 3, 2024, at 8:13 AM, Sean Baker @.***> wrote:

I don't have the issue now because I opened up the MQTT port on my firewall. Are you saying the code has been changed so that outbound MQTT is no longer required during the initial configuration of the fan? I can probably test this if you want, but I'd probably need to go through the initial configuration process for the integration again because I was getting the error when I first set up the integration. Thank you.
—
Reply to this email directly, view it on GitHubhttps://github.com/davecpearce/hacs_smartcocoon/issues/156#issuecomment-2145038412, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEHDT23APQLZYR37PVGFUK3ZFRMVRAVCNFSM6AAAAABIP5U6BSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBVGAZTQNBRGI.
You are receiving this because you commented.Message ID: @.***>


Documentation Site - Performance Optimization

Link to the Page
https://www.skeleton.dev/
Describe the Issue
Now that the visual and context improvements are in place, let's round it out by focusing on performance tweaking. This will include a few things:

[ ] (PRIORITY) Decouple and make theme fonts local imports
[ ] (PRIORITY) Make font awesome icons local imports
[ ] Improving our Chrome Lighthouse scores
[ ] Ensuring images and large media are properly optimized
[ ] Any network calls are non-blocking and running in an optimal fashion
[ ] Better support for remote fonts (ex: Google fonts) (reference)
[ ] (and more)

If you're experiencing a particular issue on the site right now please report it below. We need the following to ensure we can replicate your issue:

The specific page(s) the issue occurs
What OS and OS version you're running
What browser(s) you're running
Any additional info about your device as relevant (ex: phone model)

Performance optimizations tends to be a process, not a one-and-done kind of thing. So please be patient while we make steps to improve this. Thanks!
Are you able to create a Pull Request with the fix?
Yes

Reference:
https://discord.com/channels/1003691521280856084/1048010639219642419/threads/1084219252770340894

Image lazy load:
https://twitter.com/joyofcodedev/status/1636442268780355584

I would like to work on this issue.

@Mahmoud-zino actually on second thought I've got some ideas for this that I want to handle myself. Best to leave this one to me for now. Thanks though!

Overall the site is performing in an adequate manner, so I'm going to close this out. If and when we eventually do a major update to the site, I think this will be a better time to address any outstanding issues.


Add some key version 25 capabilitles

Update documentation by noting some of the version 25 capabilities. This doesn't add everything in version 25, but I wanted to at least get started on updating this document.

This doesn't add everything in version 25, but I wanted to at least get started on updating this document.

I don't think it is needed to add everything. Only some main features would be enough. And looks like the search by pattern is the only one which should be added because it adds a lot of flexibility in the search.

I think the bookmarks, at least, should also be noted in the documentation :-).

How about:
search-pattern ::= ['$'modifiers] MATH-SYMBOL+ ( '$'modifiers MATH-SYMBOL+ )*

search-pattern ::= ['$'modifiers] MATH-SYMBOL+ ( '$'modifiers MATH-SYMBOL+ )*

This also doesn't work. For example, it allows the first sub-pattern not to have modifiers in all cases. But actually a sub-pattern may not have modifiers when it is the only sub-pattern in the pattern. If there are two or more sub-patterns, then each of them must have at least one modifier h or a. For example, for the pattern ph -> $a ps <-> you will get the error "Malformed pattern text: Each sub-pattern must be either a hypothesis or an assertion."

Another problem is that it is not allowed to use a and h for the same sub-pattern. But this doesn't follow from the EBNF as well. I don't think this EBNF should be very precise. Currently it gives a general idea. If users misspell the pattern they will see some meaningful error message. It also should be common logic that you cannot put two sub-patterns without any modifiers because it is not clear where one ends and another begins.


Forking from development and local for game development

siban, coachshake, sammight
aquaogen, ionic, sammight
asail, vamos, kamatera (server)
kamatera (server): helix4git to github

https://github.com/Aquaogen/ionic

Had to enable private repository forking
Settings > Member priveleges > Respository forking

only sammight forking privately
the rest are public only
expect the one perforce

#117


Data type json doesn't work

Hello,
even though you can find data type json in official documentation  here, it is not supported. I would use deprecated type  json_array insted, but it incorrectly converted to text in Mysql 5.7.18, even though json is native type in Mysql for 2 years already!

It is in DBAL master only for now.


Player generate div with the class name "container" cause bootstrap mix

When player load, it generate div with class="container pointer-enabled".  We use boostrap for website and the player ui affacted. Can I change the generated class name as player-container as well ?

@Lethea it also use data-container element attribute. This may allow you to write some css override rules using, for example, the .container[data-container] selector.
Anyway, i think you are correct, a possible enhancement in next Clappr major release could be to add prefixes to css classes used by player to avoid these conflicts.

Hi! I have the same problem using Tailwind CSS. Any news?

Issue closed due to inactivity.

@rafaellotto Hi, did you find any fix? for me, play button is getting of centered when using with tailwindcss

@rafaellotto Hi, did you find any fix? for me, play button is getting of centered when using with tailwindcss

Hi, @arunpt. No, the only project I use Clappr now is without Tailwind CSS.

@rafaellotto Thanks for the update


Bugfix/essifi 112

Bug fix, feature, and docs update

verifiableCredential's type in our library was a singular string and not an array. it's changed in this PR
Changed behavior of selectFrom API to send the error logs (in case of not finding anything
In case of an unhandled error, we also include a stack trace  in our exception
we no longer use fs in our main code. the usage is limited just to the test scope
5, we no longer use &&= some of our users had some complaints about that
updated doc accordingly
added test for new selectFrom behavior
added test for pejs wrapper

Codecov Report

Merging #51 (50d5652) into develop (b7a1bae) will decrease coverage by 1.46%.
The diff coverage is 88.88%.

:exclamation: Current head 50d5652 differs from pull request most recent head de3828f. Consider uploading reports for the commit de3828f to get more accurate results

@@             Coverage Diff             @@
##           develop      #51      +/-   ##
===========================================
- Coverage    91.98%   90.52%   -1.47%
===========================================
  Files           43       43
  Lines         1397     1129     -268
  Branches       231      213      -18
===========================================
- Hits          1285     1022     -263
+ Misses         112       82      -30
- Partials         0       25      +25

Flag
Coverage Δ

unittest
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

lib/evaluation/evaluationClient.ts
90.62% <66.66%> (-4.25%)
:arrow_down:

lib/evaluation/evaluationClientWrapper.ts
77.77% <66.66%> (-1.36%)
:arrow_down:

lib/evaluation/subjectIsHolderEvaluationHandler.ts
92.22% <88.88%> (-0.44%)
:arrow_down:

...dation/bundlers/PresentationSubmissionWrapperVB.ts
97.72% <100.00%> (-0.43%)
:arrow_down:

...ib/validation/bundlers/presentationDefinitionVB.ts
91.89% <100.00%> (-6.99%)
:arrow_down:

...ib/validation/bundlers/presentationSubmissionVB.ts
88.46% <0.00%> (-11.54%)
:arrow_down:

lib/validation/bundlers/constraintsVB.ts
89.47% <0.00%> (-10.53%)
:arrow_down:

lib/validation/bundlers/inputDescriptorsVB.ts
90.32% <0.00%> (-6.98%)
:arrow_down:

lib/validation/bundlers/fieldsVB.ts
95.55% <0.00%> (-4.45%)
:arrow_down:

... and 26 more

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 b7a1bae...de3828f. Read the comment docs.


A File compaction function for EEL

Something we have discussed before is having a compact function on the EEL API.
This essentially merges all individual files into a single file.
The reasons for this is 2 fold:

Keeps the name node memory compact as each HDFS block occupies around 250 bytes of RAM

Fewer memory partitions are created for Spark RDDs/DFs and HDFS native reads - in general this should make read performance more optimal.

There are a number of ways you could approach this:

Given that the data is already in HDFS you could use EEL to discover the partitions you desire and create a DF, coalesce to 1 and save

Same as the above but use a EEL combination of the HiveSource and the HdfsSink

Note as part of the process you could remove any empty files.
You might consider writing the new file to a  staging .directory and archiving the original directory to .directory on completion, and then renaming the staging directory back to the original name.

Added


Add methods to override Span.Options on the span created by the client middleware

This would allow callers to set the Span Creation Policy, etc., on the span created by the middleware.

I can't remember why I marked this as a Draft PR, so I'm going to mark it ready for review and see what feedback I get. 😅


#140583907 Set up frontend environment

What does this PR do?
Setup environment for the frontend
Description of Task to be completed?
Configure webpack and babel
What are the relevant pivotal tracker stories?
#140583907

Coverage increased (+0.5%) to 81.818% when pulling 930b9a02c5bb5565f40a1ef9c920b7fc4ae4c89a on feature/140583907/Set-up-frontend-environment into 0b3cf4bd864caf54fabd76da5a031f50a155689b on develop.


Move the tests to a separate PHP namespace

Also add PSR-4 dev-autoloading for this namespace.

@sabberworm @westonruter Gentle ping for a review as this hopefully fixes some PHPStan issues on higher levels.

@sabberworm Thanks! :heart:


Swift 4 and Xcode 9 beta support

The Swift 4 support was added by #48 that was merged. Closing this PR.


(SERVER-1150) Add support for custom oid mappings

Add support for Puppet's custom trusted oid mapping feature.

:+1: on this overall.  From bench testing, I saw that the short names for my custom-named oids were being returned in my catalog requests via $trusted['extensions'] references placed in the compiled manifest.
The couple of things I'd recommend looking at are ensuring that the trusted oid mapping file only gets parsed no more than once per JRuby initialization and that the server can still handle the absence of a trusted oid mapping file.
This whole code path also reminded me of how the core Ruby Puppet code handles the registration of custom OID mnemonics, basically relying upon the OpenSSL gem.
OIDs are registered here...
https://github.com/puppetlabs/puppet/blob/4.4.1/lib/puppet/ssl/oids.rb#L115
... and extracted from here ...
https://github.com/puppetlabs/puppet/blob/4.4.1/lib/puppet/ssl/certificate.rb#L87
We've consciously been trying to avoid having any code running under Ruby via Puppet Server use the OpenSSL gem because of various issues we'd found working with it earlier on in JRuby.  This PR furthers the approach of not having Puppet Server use Ruby's OpenSSL, which seems good.
Since the OpenSSL oid registrations are essentially global, though, it would seem that any arbitrary code running under Ruby might just try to use OpenSSL to handle the OID -> short name translation.  The code above in certificate.rb is essentially replaced under Puppet Server via Puppet Server's own certificate.rb.  I grepped through the Ruby code, though, and only found one other place that does an OpenSSL::ASN1.decode, here:
https://github.com/puppetlabs/puppet/blob/4.4.1/lib/puppet/ssl/certificate_request.rb#L123
I don't think the above code runs under Puppet Server since Puppet Server's CA is hopefully the only portion of the stack that deals with certificate request objects.
That said, though, I wonder if we might want to look into filing a follow-on ticket to Ruby Puppet to have a class / module do a one-time stash of the oid mappings with a getter method that could be called to obtain that list when needed at various points and then modifying existing code in Puppet to use that new mapper class / module to do the translation rather than OpenSSL.  I worry at some point about the possibility of some other Ruby-level code being introduced that tries to use OpenSSL directly to do the OID -> name translation and having that unknowingly be broken when run under Puppet Server.

Closing out this PR, I am planning to refactor this so that we do all the parsing in the clojure code instead.

Re-opening, as we've decided doing things in the ruby code is the only reasonable approach.

This is currently blocked on https://github.com/puppetlabs/puppet/pull/4827. Once that is merged, I'm planning to update our submodule dependency and remove some of the code added in this PR.

@fpringvaldsen we merged the puppet PR, you should be good to go

Okay, all the feedback on this has been addressed, and the Puppet changes have been pulled in, so this is all ready for review/merge.

I'm :+1: with one nitpick about reversing a conditional.

@haus I've addressed that conditional

:+1: from me.

This should have been merged to stable instead of master since we need to ship it in the 2.3.2 release.  @fpringvaldsen would you mind opening a PR against stable which just cherry-picks this commit?

@KevinCorcoran Sure, I'll get to work on that

@KevinCorcoran https://github.com/puppetlabs/puppet-server/pull/1006