HBASE-26248 Should find a suitable way to let users specify the store…

… file tracker implementation

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ HBASE-26067 Compile Tests _

+1 :green_heart:
mvninstall
4m 46s
HBASE-26067 passed

+1 :green_heart:
compile
3m 43s
HBASE-26067 passed

+1 :green_heart:
checkstyle
1m 10s
HBASE-26067 passed

+1 :green_heart:
spotbugs
2m 24s
HBASE-26067 passed

_ Patch Compile Tests _

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

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

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

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

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

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

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

_ Other Tests _

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

58m 18s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux f02bff8da50b 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-26067 / 0c8db602a9

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m 26s
Docker mode activated.

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

_ Prechecks _

_ HBASE-26067 Compile Tests _

+1 :green_heart:
mvninstall
7m 20s
HBASE-26067 passed

+1 :green_heart:
compile
1m 52s
HBASE-26067 passed

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

+1 :green_heart:
javadoc
1m 12s
HBASE-26067 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

-1 :x:
unit
19m 57s
hbase-server in the patch failed.

71m 33s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 273b903b475f 4.15.0-142-generic #146-Ubuntu SMP Tue Apr 13 01:11:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-26067 / 0c8db602a9

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

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

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3665/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 10s
Docker mode activated.

_ Prechecks _

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

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

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

_ HBASE-26067 Compile Tests _

+1 :green_heart:
mvninstall
4m 14s
HBASE-26067 passed

+1 :green_heart:
compile
3m 30s
HBASE-26067 passed

+1 :green_heart:
checkstyle
1m  5s
HBASE-26067 passed

+1 :green_heart:
spotbugs
2m  7s
HBASE-26067 passed

_ Patch Compile Tests _

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

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

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

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

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

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

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

_ Other Tests _

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

50m  4s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-26067 / 0c8db602a9

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ HBASE-26067 Compile Tests _

+1 :green_heart:
mvninstall
4m 44s
HBASE-26067 passed

+1 :green_heart:
compile
1m 13s
HBASE-26067 passed

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

+1 :green_heart:
javadoc
0m 45s
HBASE-26067 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

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

177m 10s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 968dc31496a7 4.15.0-151-generic #157-Ubuntu SMP Fri Jul 9 23:07:57 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-26067 / 0c8db602a9

Default Java
AdoptOpenJDK-11.0.10+9

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ HBASE-26067 Compile Tests _

+1 :green_heart:
mvninstall
4m  7s
HBASE-26067 passed

+1 :green_heart:
compile
1m  8s
HBASE-26067 passed

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

+1 :green_heart:
javadoc
0m 37s
HBASE-26067 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

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

192m 19s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-26067 / 0c8db602a9

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ HBASE-26067 Compile Tests _

+1 :green_heart:
mvninstall
4m 26s
HBASE-26067 passed

+1 :green_heart:
compile
3m 22s
HBASE-26067 passed

+1 :green_heart:
checkstyle
1m 10s
HBASE-26067 passed

+1 :green_heart:
spotbugs
2m 13s
HBASE-26067 passed

_ Patch Compile Tests _

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

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

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

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

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

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

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

_ Other Tests _

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

53m 53s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux bef4838c8413 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-26067 / 27fd631b52

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ HBASE-26067 Compile Tests _

+1 :green_heart:
mvninstall
3m 39s
HBASE-26067 passed

+1 :green_heart:
compile
1m  2s
HBASE-26067 passed

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

+1 :green_heart:
javadoc
0m 38s
HBASE-26067 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

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

183m 11s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux c23a0b4573c0 4.15.0-151-generic #157-Ubuntu SMP Fri Jul 9 23:07:57 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-26067 / 27fd631b52

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ HBASE-26067 Compile Tests _

+1 :green_heart:
mvninstall
4m 19s
HBASE-26067 passed

+1 :green_heart:
compile
1m 13s
HBASE-26067 passed

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

+1 :green_heart:
javadoc
0m 41s
HBASE-26067 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

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

185m 18s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 90b1e61efb93 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-26067 / 27fd631b52

Default Java
AdoptOpenJDK-11.0.10+9

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

Ping @wchevreuil

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ HBASE-26067 Compile Tests _

+1 :green_heart:
mvninstall
5m 39s
HBASE-26067 passed

+1 :green_heart:
compile
3m 30s
HBASE-26067 passed

+1 :green_heart:
checkstyle
1m 16s
HBASE-26067 passed

+1 :green_heart:
spotbugs
2m 29s
HBASE-26067 passed

_ Patch Compile Tests _

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

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

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

-0 :warning:
checkstyle
1m 15s
hbase-server: The patch generated 1 new + 6 unchanged - 1 fixed = 7 total (was 7)

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

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

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

_ Other Tests _

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

61m 52s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux 1203f9eadc22 4.15.0-147-generic #151-Ubuntu SMP Fri Jun 18 19:21:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-26067 /<PHONE_NUMBER>

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 34s
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 _

_ HBASE-26067 Compile Tests _

+1 :green_heart:
mvninstall
4m  5s
HBASE-26067 passed

+1 :green_heart:
compile
1m  4s
HBASE-26067 passed

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

+1 :green_heart:
javadoc
0m 37s
HBASE-26067 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
151m  6s
hbase-server in the patch passed.

184m 50s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 9659d6591ab0 4.15.0-151-generic #157-Ubuntu SMP Fri Jul 9 23:07:57 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-26067 /<PHONE_NUMBER>

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ HBASE-26067 Compile Tests _

+1 :green_heart:
mvninstall
5m 44s
HBASE-26067 passed

+1 :green_heart:
compile
1m 27s
HBASE-26067 passed

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

+1 :green_heart:
javadoc
0m 46s
HBASE-26067 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

-1 :x:
unit
150m 43s
hbase-server in the patch failed.

190m  1s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 32bff2db5960 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-26067 /<PHONE_NUMBER>

Default Java
AdoptOpenJDK-11.0.10+9

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

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

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

modules
C: hbase-server U: hbase-server

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ HBASE-26067 Compile Tests _

+1 :green_heart:
mvninstall
4m  3s
HBASE-26067 passed

+1 :green_heart:
compile
3m 21s
HBASE-26067 passed

+1 :green_heart:
checkstyle
1m  9s
HBASE-26067 passed

+1 :green_heart:
spotbugs
2m 10s
HBASE-26067 passed

_ Patch Compile Tests _

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

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

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

+1 :green_heart:
checkstyle
1m  8s
hbase-server: The patch generated 0 new + 6 unchanged - 1 fixed = 6 total (was 7)

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

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

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

_ Other Tests _

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

51m 18s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux 830b2ed3fbdf 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-26067 /<PHONE_NUMBER>

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3665/5/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ HBASE-26067 Compile Tests _

+1 :green_heart:
mvninstall
4m 16s
HBASE-26067 passed

+1 :green_heart:
compile
1m 12s
HBASE-26067 passed

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

+1 :green_heart:
javadoc
0m 42s
HBASE-26067 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

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

179m 44s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 8073228bfd09 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-26067 /<PHONE_NUMBER>

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3665/5/testReport/

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3665/5/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  0s
Docker mode activated.

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

_ Prechecks _

_ HBASE-26067 Compile Tests _

+1 :green_heart:
mvninstall
4m 26s
HBASE-26067 passed

+1 :green_heart:
compile
1m  3s
HBASE-26067 passed

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

+1 :green_heart:
javadoc
0m 40s
HBASE-26067 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

-1 :x:
unit
216m 23s
hbase-server in the patch failed.

249m  2s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 7c8eec91f559 4.15.0-143-generic #147-Ubuntu SMP Wed Apr 14 16:10:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-26067 /<PHONE_NUMBER>

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3665/5/testReport/

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3665/5/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 35s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
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.

_ HBASE-26067 Compile Tests _

+1 :green_heart:
mvninstall
5m  7s
HBASE-26067 passed

+1 :green_heart:
compile
4m 45s
HBASE-26067 passed

+1 :green_heart:
checkstyle
1m 25s
HBASE-26067 passed

+1 :green_heart:
spotbugs
2m 36s
HBASE-26067 passed

_ Patch Compile Tests _

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

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

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

+1 :green_heart:
checkstyle
1m 19s
hbase-server: The patch generated 0 new + 6 unchanged - 1 fixed = 6 total (was 7)

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

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

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

_ Other Tests _

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

63m  6s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux 775a17ae9bf5 4.15.0-147-generic #151-Ubuntu SMP Fri Jun 18 19:21:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-26067 / d76ba9616c

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3665/8/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ HBASE-26067 Compile Tests _

+1 :green_heart:
mvninstall
3m 38s
HBASE-26067 passed

+1 :green_heart:
compile
1m  1s
HBASE-26067 passed

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

+1 :green_heart:
javadoc
0m 37s
HBASE-26067 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
153m  0s
hbase-server in the patch passed.

182m 52s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 7df785cdf779 4.15.0-151-generic #157-Ubuntu SMP Fri Jul 9 23:07:57 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-26067 / d76ba9616c

Default Java
AdoptOpenJDK-1.8.0_282-b08

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3665/8/testReport/

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3665/8/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
2m  0s
Docker mode activated.

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

_ Prechecks _

_ HBASE-26067 Compile Tests _

+1 :green_heart:
mvninstall
4m 47s
HBASE-26067 passed

+1 :green_heart:
compile
1m 20s
HBASE-26067 passed

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

+1 :green_heart:
javadoc
0m 51s
HBASE-26067 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

-1 :x:
unit
154m 57s
hbase-server in the patch failed.

192m 43s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 74c6c7cc47f9 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-26067 / d76ba9616c

Default Java
AdoptOpenJDK-11.0.10+9

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

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3665/8/testReport/

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3665/8/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 15s
Docker mode activated.

_ Prechecks _

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

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

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

_ HBASE-26067 Compile Tests _

+1 :green_heart:
mvninstall
9m 21s
HBASE-26067 passed

+1 :green_heart:
compile
3m 23s
HBASE-26067 passed

+1 :green_heart:
checkstyle
1m 10s
HBASE-26067 passed

+1 :green_heart:
spotbugs
2m 13s
HBASE-26067 passed

_ Patch Compile Tests _

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

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

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

+1 :green_heart:
checkstyle
1m  7s
hbase-server: The patch generated 0 new + 6 unchanged - 1 fixed = 6 total (was 7)

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

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

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

_ Other Tests _

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

59m 15s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux a777857546b0 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-26067 / d76ba9616c

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3665/9/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ HBASE-26067 Compile Tests _

+1 :green_heart:
mvninstall
4m 19s
HBASE-26067 passed

+1 :green_heart:
compile
1m 15s
HBASE-26067 passed

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

+1 :green_heart:
javadoc
0m 43s
HBASE-26067 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
151m 12s
hbase-server in the patch passed.

184m 16s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 00f09c3b8f5c 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-26067 / d76ba9616c

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3665/9/testReport/

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3665/9/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ HBASE-26067 Compile Tests _

+1 :green_heart:
mvninstall
3m 57s
HBASE-26067 passed

+1 :green_heart:
compile
1m  4s
HBASE-26067 passed

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

+1 :green_heart:
javadoc
0m 36s
HBASE-26067 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

-1 :x:
unit
159m 10s
hbase-server in the patch failed.

189m 54s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux bff8f256b7aa 4.15.0-151-generic #157-Ubuntu SMP Fri Jul 9 23:07:57 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
HBASE-26067 / d76ba9616c

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3665/9/testReport/

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

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3665/9/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.


editorGroupModel should be source of truth for editorGroupView

Right now we have onDidGroupChange and #137388 seeks to add onDidModelChange. However, the model is less informed than the view at the moments.
To clean up this debt we should

Enrich the model to know about all view changes and act as the "source of truth"
Have onDidModelChange replace onDidGroupChange so we don't have two listeners doing similar things. We can then rename onDidModelChange to onDidGroupChange as it is a better name.

If you want to make an attempt via a new PR now that the other PR is merged, I am happy to review 👍

Actually I'm not sure we want to do this. The first part yes we should figure out where active is being set and where it isn't. The second part we won't be able to replace all events because there's on will and on did close for example which is based on when the UI updates. The model already considers the editor closed.


Refactor visUtils to avoid mutation

closed in https://github.com/BostonGlobe/elections-2016/commit/fe950f4d019310f5aadbdc219e9e32533867389c


Codespell currently failing on CI

Describe your issue
It's started complaining a lot about assertIn and similar. Unsurprisingly this has affected other people https://github.com/codespell-project/codespell/issues/3430 so I expect will be fixed pretty quickly. I think it's best to ignore it and wait for it to be fixed elsewhere.

I fixed some issues in https://github.com/cython/cython/commit/101d2a2b640250b48cde88073621d2587f3373b8


Extend PR #77 - Add Test Data Builders

This is an extension of the concepts originally introduced in PR #77 by @up2go-rsoesemann.  A big Thank You to him for getting this started!
Enhancements from #77:

Add ability to build existing or new SObjects in-memory
** build(Boolean) on Base / build() & buildNew() on derived
Persist single builder to DB or register multiple builders for persistence to DB
** Single - persistBuilder(fflib_ISObjectUnitOfWork) on base / persist(fflib_ISObjectUnitOfWork) on derived
** Multiple - persistRegistered(fflib_ISObjectUnitOfWork) on base
Test Coverage - fflib_DomainObjectBuilder
Add Object Mother pattern for simplified builder creation

Comments:

Per discussion in #77:
** Rather than have builder create Unit Of Work, decided to have it be a method parameter.  The reason for this is a couple of fold but ultimately, every test data situation is slightly different and if list of SObjectTypes is maintained in the builder itself, it limits what SObject can be built during persist operations.  By passing in as a parameter, the test setup code can ensure the UOW has the correct SObjectTypes.  Also, the derived class can choose to have a persist() and a persist(fflib_ISObjectUnitOfWork) convenience methods that both wrap persistBuilder(uow).  The persist method can create a 'default' UOW internally and when necessary, persist(uow) can be called when the default of the builder does not satisfy the needs.  In short, get the best of both worlds here I think.
** Persistance to the DB when operating on registered builders held in static is done via a static method
** Persistance to the DB on an individual builder instance (and it's related data) is done via instance method
** Decided not to add @IsTest to fflib_DomainObjectBuilder since this class can be used for non-test purposes (see future enhancements below as well) and has 100% test coverage.
** Regarding a single file per builder or one file with lots of inner builders, this is really the choice of the implementer and I don't think having to choose one way or the other as it relates to fflib itself is required.
Chose to be a little verbose on method names in base class (e.g. persistBuilder, registerBuilder, etc.).  While these methods are marked public, the intention is that derived classes will always wrap these methods exposing a shorter name (e.g. persist, register).  This allows the derived class to cast to its own type (or the specific SObject type) avoiding the caller from having to cast return values all over the place and also allowing for fluent configuration in certain situations (e.g. registerBuilder).
fflib_DomainObjectBuilderTest contains samples of how to leverage the library for all 4 "build" methods.  Review any of the TestXXXBuilder inner classes for the standard methods that would/should be included in all derived classes.
Liberal use of protected & virtual allowing for derived classes to extend as needed

Future Enhancements:

Test Data Builder generator similar to Apex Mocks Generator
Ability to handle 'updates' of SObject data not just inserts making the pattern more useful in production situations
Updates to fflib-apex-samplecode demonstrating pattern (samples already exist in fflib_DomainObjectBuilderTest) - See Samples
MavensMate template - See Templates

Feedback encouraged and welcome.  Look forward to everyone's thoughts!

@jondavis9898 thanks for giving my idea a new chance of being merged by adressing some of the problems.
I totally get the rationale behind your changes. I am also quite sure that you implemented them thoroughly. Your changes (actually a rewrite) are way to massive to understand them without really digging in for hours ;-).
But..what I can say from looking at the tests for 5 minutes is that the resulting test don't look like I would like to have them. I don't care if I don't understand the implementation anymore (thats why I use a library). But...if the result doesn't make my test more readable and concise and tech free I won't use it. There are TestXYZBuilders and pattern-related names all over the place. I would say the implementation details shine through... ;-)
I think some renaming in your classes public interface could probably do the job. Maybe you could also rebuild my test implementation (https://github.com/up2go-rsoesemann/fflib-apex-common-samplecode/commit/adab15414782cff1ffb914f89d211c5e7b283d2e) with your implementation and see how clean and readable the are.

@up2go-rsoesemann Thanks for reviewing the proposed changes and providing your feedback!
Regarding the tests for fflib_DomainObjectBuilder itself and the TestXYZBuilder naming convention, these are intended to be tests for the Builder itself and not meant to represent what a naming convention in actual use might be.  That said, it does demonstrate that the name of the actual "builders" an be anything that the consumer of the builder desires as it doesn't influence the functionality.  For example, your example used Opportunity_t while someone else could use OpportunityBuilder, etc.  In short, apologize if the naming convention made things more challenging to understand.
I have updated the sample code repo with example using using the naming convention that you chose.  I wrote the same test that you did in there as well as several others to demonstrate all the functionality of fflib_DomainObjectBuilder.  Please have a look and let me know if this helps clarify usage.
I agree that the naming convention on the public interface of the fflib_DomainObjectBuilder is a little cumbersome.  When writing a test, other than the persistBuilders(uow) method, you would never call a method on fflib_DomainObjectBuilder directly.  Instead, you would call methods on the derived classes which, as you'll see in the sample, are shorter and easier to follow.
The reason I chose to do it this way is two-fold:

As I mentioned in my previous post above, it avoids having to cast the result of the method call whenever you build/persist something within a test.  By having the derived classes expose "build()" and call fflib_DomainObjectBuilder's build(Boolean), the derived class build() can cast to the specific SObjectType it needs.  If the test code called a build method on fflib_DomainObjectBuilder directly, each call would need to be cast in the test code itself making things much more difficult to follow/read within the test itself.
I've added 3 new ways of creating SObjects using the builders but wanted to keep the naming similar - this caused method names to be a little more verbose in the base class itself.  As an example, with the ability to create in-memory SObjects and not just DB based, you can use the builder to write a true unit test that doesn't require the database, something that wasn't possible in the original version of fflib_DomainObjectBuilder (see testService_UsingBuildersWithoutDML).

Keeping with trying to make tests as easy to read/follow as possible, I've also implemented an Object Mother pattern to avoid having "new" keywords all over the tests.
In addition to adding the sample code, I've added MavensMate templates at https://github.com/joeferraro/MavensMate-Templates/pull/18.  By creating a new DomainObjectBuilderBase and then specific DomainObjectBuilder classes, the boiler plate code really leaves you only to have to add "withXXX" methods to the build classes themselves and then write your tests.
Here's the approach:

Create DomainObjectBuilderBase (e.g. Domain_t)
Modify createUnitOfWork() on DomainObjectBuilderBase as appropriate (see comments in method from template)
Create DomainObjectBuilder (e.g. Account_t, Opportunity_t) for each SObject you want to create a builder for
Add "withXXX" methods to the builders as appropriate
Optional: Add additional Object Mother static methods to the builders as appropriate
Write your tests and use the following:
Instance Methods
build() - Builds an in-memory Existing SObject (Id is NOT null) and returns the SObject cast to the derived SObjectType
buildNew() - Builds an in-memory New SObject (Id is null) and returns the SObject cast to the derived SObjectType
persist() - Commits the builder and any of its related data through the default Unit Of Work (obtained via createUnitOfWork) and returns an instance of the SObject cast to the derived SObjectType
persist(uow) - Commits the builder and any of its related data through the Unit Of Work specified and return an instance of the SObject cast to the derived SObjectType
register() - Registers the builder for commit when persistBuilders(uow) is called
Record - Returns the SObject cast to the derived SObjectType
but() - Creates a clone of the builder instance

Static Methods on Derived Builders
Object Mother Helpers
Static Methods on Base
persistRegistered(uow) - Commits all registered builders and any of their related data through the Unit of Work specified
I'm hopeful that once you review the sample code, you'll see how all this plays out and how clean the actual test itself is.  Hope this helps, let me know what you think and any questions you might have.  Thanks!

Thanks for clarifiying you concepts. Looks like there are dependancies to ApexMocks and its related classes (e.g. Application). I never bought into applying those concepts in Apex and hope that dicussions like #36 will lead to a more lightweight direction.

@up2go-rsoesemann Thanks for reviewing the samples.  To answer your questions:

There is no depdency on Application within fflib_DomainObjectBuilder which is what this PR covers.  The only dependency on "Application" is in one place in the sample code and is optional.  Since the sample code contains an Application class, createUnitOfWork() uses it.  It could very easily not use it and just create an fflib_SObjectUnitOfWork(List) directly.  In the MavensMate template you'll see a comment that indicates there are multiple options on how to write createUnitOfWork.  In fact, you don't even need to have a createUnitOfWork at all, it's simply a helper method.  The consumer could choose not to implement persist() and only expose persist(fflib_ISObjectUnitOfWork) instead in which case createUnitOfWork() wouldn't even be needed.

If you wanted to add a child object to a parent, you could add a method to your Account_t called "add(OpportunityBuilder)" and then handle the relationship setting in that method.  Something like:
public Account_t add(OpportunityBuilder value) {
value.withAccount(add);
return this;
}

Please keep in mind that fflib_DomainObjectBase is simply an abstract base class.  How the consumer of the library chooses to use it is up to them.  They could name their builder Opportunity_t or OpportunityBuilder, they could use a derived class like Domain_t or choose not to, they could use Application class or choose not to.  The samplecode is just one example of how the library could be used, it doesn't require that everyone use it that way.  This is one of the reasons why there is test coverage for fflib_DomainObjectBuilder, because there is no right or wrong way to use it.  It's up to the consumer of the base class to choose how to use it and up to the base class to provide the functionality to satisfy most (if not all) use cases.

@afawcett Who under which process decides if a pull request is going to be merged in, rejected or just ignored?

Do we need this kind of thing? Ok so i've been reviewing this finally, so sorry for the delay. Firstly i want to progress this for sure! I agree for certain developers that expect this type of facility on the platforms they work on its a great addition. I'm happy and honoured to support the great community around this library to lead the charge as you guys are doing.
ApexMocks parallel? For me this feels much like the time Paul Hardaker and I first discussed introducing ApexMocks. We worried about the bloat and who would really understand it and i'm pleased to see its really taken off. I think the same can be true here for sure!
Some more specific thoughts...

In or Out this Repo? Given the thoughts already shared about the library getting large, which i also support, i'm torn by potentially compounding this and building debt for when we also get round to splitting up this library vs the fact that this is really an additional two classes.... Robert i hear what your saying, and tbh felt the same way. However as per the discussion on the https://github.com/financialforcedev/fflib-apex-common/issues/36 its also about barrier to entry for new devs that might intimidated and ignore the whole library all together and also adoption in none ISV/packaged scenarios john-m and others are talking about.
Builder Classes There is a lot of boiler plate needed for the builder classes, i think this will inhibit adoption of it tbh. Again we had the same discussions around ApexMocks, hence we ended up with a generator tool, perhaps the same approach here is needed? I also think we need to provide the option to scope the builder classes or at least in the hand written samples, show them as inner classes and not pollute the top level namespace with essentially supporting classes.

Proposal: I think on balance i'm going to recommend we add this fine work into a fflib-apex-testbuilder repo. As far a test builder classes go perhaps contain these in the sample app in a TestBuilders class, hand maintained for now, but then perhaps think about a generator much like ApexMocks.

Thanks for reviewing Andrew, glad to here you feel a builder concept like this has merit.
I'm in full support of a separate repo.  I think using the builder pattern is completely optional and doesn't need to be in apex common core.  Personally, I'd like to have it in the core library but in my use cases, I'm using everything in fflib so it's nice to just have one place to manage everything from.  That said, I think there is very good merit to having thinks like Mocks, Builder and a few others in separate repos since they aren't "core".
Regarding inner classes vs. separate classes, I feel that decision is completely up to the consumer of the pattern/library and the library itself doesn't need to dictate.  Demonstrating both options makes sense and provides flexibility.  In the test cases for the builder I used inner classes, however in apex sample code, I used separate classes.  Along these same lines, I feel that naming convention should also be at the consumers discretion (e.g. Account_t vs. AccountBuilder, etc.).
Regarding a generator, I actually started writing one when I updated this PR but unfortunately, I didn't get very far and finishing it has been put on the backburner do to other priorities.  My design calls for a flag that would emit the classes as inner classes or separate so I think that is in-line with your suggestion.  The design also called for options for naming pattern, what the "Object Mother" default method should be named, etc.  If someone wants to jump in and write the generator, I'd be all for that!
In the meantime, I did update mavensmate templates with templates for the builders (also updated Domain template since it was a little out of date).  For those using MM at least, creating a builder is very simple.  I agree that there is a lot of boiler plate code (but there's a lot of goodies in there :)).  If we can work to complete a generator, I think that will reduce concerns folks would have on the amount of code required to use the builder.  In the meantime, the MM templates should hopefully help.

Per discussion in #77, a new repo was created for this.  Submitted https://github.com/financialforcedev/fflib-apex-common-builder/pull/2 to the new repo.
This issue can be closed.


16 refactoring

This is a popo-platter of refactoring.  Changes include merging three obstacle builder methods into one, changing window size, making cockpit class more readable, swapping collision spheres for collisions boxes in all but player class, gets rid of Maths class and moves unit and scalar mult to vector class.

Looks good.


Tests: Adds code coverage for gmaps.load method.

rel: #74

Coverage increased (+3.36%) to 95.36% when pulling 562a7bf6f578ba058915ba6a880d3ce8a80f368a on yago/code-coverage-100 into 531e98464dcdf7795a02771396783994888f72ea on master.

Coverage increased (+4.0%) to 96.0% when pulling 483bab820a228141f1d687af10ab05c16c3fc2d4 on yago/code-coverage-100 into 531e98464dcdf7795a02771396783994888f72ea on master.

Coverage increased (+8.0%) to 100.0% when pulling 22e2fd724b8900aee5e4a0b301358fb1d08fd302 on yago/code-coverage-100 into 531e98464dcdf7795a02771396783994888f72ea on master.


Compiling issue in Hygieia Executive Dashboard Setup

I have downloaded the latest version of Hygieia executive Dashboard from below link
https://github.com/Hygieia/ExecDashboard.
I have Team dashboard with Hygieia 3.0.2 version.
I got an exception while compiling the exec-api folder using below command
mvn clean install
Exception:
[ERROR] Failed to execute goal on project exec-api: Could not resolve dependencies for project com.capitalone.dashboard:exec-api:jar:1.0.0-SNAPSHOT: Could not find artifact com.capitalone.dashboard:exec-core:jar:1.0.0-SNAPSHOT -> [Help 1].
Please help me to resolve the issue.

+1 I am also seeing this issue. Any resolution to this?

@codygulley can you add the entire log file?

I think executive dashboard uses multi-maven module structure. So triggering mvn clean install from the root - ExecDashboard folder seems to compile all the modules including api and analysis.


Unpredictable behavior of statusBar.displayMode when connecting to the server

Problem description

There is a strange problem that sometimes appears in issues on Github (but no one has opened a separate issue about it). In the assembled application, you can specify statusbar.displayMode = 'float', but if you connect to the console (with 'tabris serve') this setting will be ignored. The problem occurs on Android 10, 11 (maybe even older)
Expected behavior

I want the behavior of statusbar.displayMode to be always predictable.
Environment

Tabris.js version: 3.7.2
Device: Samsung A51, Xiaomi Redmi 5 Plus
OS: Android 11, Android 10

Code snippet
import { statusBar } from 'tabris';

statusBar.background = 'transparent';
statusBar.theme = 'dark';
statusBar.displayMode = 'float';

The issue has been solved.


Bump Dependencies #10973527625

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/10973527625

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


References (not just links) to item (view and menu item) – Update to released plone.restapi.relations

PLIP https://github.com/plone/volto/issues/4339
Update to PR https://github.com/plone/volto/pull/4787
Nice to have

[ ] Show relation name (relation field title) instead relation field id.

Made some refactoring:

queryRelations can be done with list of paths of targets. No need to go via UID.

no need to check if items back links are already available in store. Just fetch if itempath changes (hook dependency)

title: getContent, if no title (request /links-to-item without referer)
no reset of REDUX store (content, relations). Just leave it.
I've added a column with the content type. Does not distuorb. Thought it would be of interest.

Thank you @stevepiercy for reviewing. I updated the wording according your suggestions and made some more changes. Can you have a look again, please.
@pgrunewald and @danalvrz, please take some minutes and share your thoughts, thank you.

Thank you @stevepiercy for reviewing. I updated the wording according your suggestions and made some more changes. Can you have a look again, please.
@pgrunewald and @danalvrz, please take some minutes and share your thoughts, thank you.
Preview of docs: https://deploy-preview-4842--volto.netlify.app/user-manual/links-to-item.html

@ksuess it looks great! 🎉

Thanks for this great addition, @ksuess!


device-tree-overlays: Adapt to updated dtc

The canbus clock changed in the upstream dtc to 40mhz and in doing so
they changed the node name, which makes the overlay no longer apply.
Change the node name to make the overlay work again.

We should wait for a build to complete, but manually compiling and inserting this overlay does make the system boot.


Bug or Download Manipulation of Model

As the author of the model, I am concerned about the unusual download activity observed. The download count is very high, the download graph is erratic, and most importantly, there are many downloads but no corresponding likes or discussions in the community.
https://huggingface.co/Necent/distilbert-base-uncased-detected-jailbreak

if you dont want the model to be downloaded, you can make it "private".
Also, this doesnt seem like an issue related to AutoTrain. Please email<EMAIL_ADDRESS>if you have concerns.


Fix false positive alarms on missed  or  header.

The case of a non-STL realization of the one of the functions under test that
is called via class name/namespace resolution syntax (e.g. type type::min)
was not handled by the regular expression.
Fixes the #174
@rakhimov, please check if this fix solves your case.

@googlebot, I signed it!

Consider submitting the patch to the fork at https://github.com/cpplint/cpplint


Nick: Watch +2347032606674

Nick requests the watch of the watch_number +2347032606674. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by Jeff Schaller in Charcoal HQ


Implement non-nested struct statistic extraction

Which issue does this PR close?

Closes #10609
Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

Did not implement the nested struct type since the current RowGroupMetaData and ColumnChunkMetaData seems not to support nesting


Feature Request: Generate resolution-aware variants

I am thinking whether it could be useful to generate resolution-aware variants of the webp output automatically.
Lets say I input an image with 10.000px x 10.000px and I set a target size of 1000 x 1000 so that it generates

image.webp (1000px x 1000px)
/2.0x/image.webp (2000px x 2000px)
/3.0x/image.webp (3000px x 3000px)

Is this anyhow doable with the provided API and is this any useful with the webp format?
I am not aware of the details of the webp format and whether this could improve performance (I am assuming no cause the p stands for progressive loading, right?) and size (maybe not as the resolution specific variants are all bundled anyways as long as they are not stored in the native android/iOS asset folders I think).
Happy to get feedback on this and to provide implementation help once we figured out if this is useful and doable.
Cheers!

Hey!

Is this anyhow doable with the provided API?

The asset transformers API currently allows only the transformation of one asset into one asset, we cannot create n assets based on one like you proposed. If you think that's a good case (maybe not for the webp package specifically) you should definitely create an issue on https://github.com/flutter/flutter.

whether this could improve performance

I am not well familiar with the technicalities of the WebP format and its implementation in Flutter either, but it would make the transformation itself during compile/build time longer, as the CI/developer's machine would need to scale such images down. As for the performance on end-user devices, yes, serving assets more appropriate images based on the pixel density of the user's device will make it so that the device won't need to make such heavy scaling locally, but will already be supplied with an asset in exactly (or close) resolution it expects.

and size (maybe not as the resolution specific variants are all bundled anyways as long as they are not stored in the native android/iOS asset folders I think)

What you answered yourself is right. Having resolution (or rather pixel-density) aware assets increase the size of the output app, it doesn't take advantage like Android App Bundles with native assets or the iOS counterpart would have - see https://github.com/flutter/flutter/issues/16015
As this is not doable with the current API and I believe is not the scope of this package, I'm closing the issue.

Hi @Albert221
Thanks for the quick response to my inquiry!
Your answers came close to what I'd thought...
Please allow me one last question as it was a tedious search to find your package already.
I wasn't specifically looking for a webp asset converter but just wanted to shrink my image assets in size in general. Are you aware of another package which is not specific to webp?
Thank you in advance!


Release Notes 1.32.1 list.toggleKeyboardNavigation is hard to understand

The description for Automatic Keyboard Navigation setting is hard to understand without the right context or previous knowledge. Being a non-native english speaker, the use of certain scientific terms make it even harder to understand and further deepens the confusion. Visual clues such as screenshots or gifs of the feature would help a lot.

Automatic Keyboard Navigation setting
A new setting List: Automatic Keyboard Navigation controls whether lists and trees capture lexicographic keypresses in order to navigate and filter elements. If disabled, keyboard navigation becomes modal and the list.toggleKeyboardNavigation command will toggle its state. You can assign a specific keyboard shortcut to that command. For example, you could set it to be / and only after pressing /, will subsequent keypresses filter items in lists/trees. This setting defaults to enabled.

The keybinding, when added to my keybindings.json seemingly does not work, which makes it even harder to understand by "reverse engineering" it, ie. discover the feature by trying to simulate the behavior.

While gathering information for this suggestion, I ultimately discovered what the Automatic Keyboard Navigation is about and that I have actually used it since some previous release, but it was nonetheless frustrating to be not able to understand and visualise the introduced changes.

This is an advanced setting which under 0.01% of our users should even be aware of. It is only interesting for users who have simple keyboard shortcuts in trees (eg A to create a file in the explorer) yet see those shortcuts collide with the new automatic filtering feature. The setting allows to disable the filtering feature so you can still have those shortcuts.

Thank you for explanation and while I agree with what you say, it shouldn't mean that it is mentioned in the changelog just btw. VSCode team has set a high standard for explaining things in the changelog, which is great, but this one feature didn't meet the standard. I always read the changelog thoroughly to discover new features and options to better customize my workplace and I was really frustrated to not be able to better understand it.


jeayeson is broken after updating to boost 1.58.0

https://gist.github.com/xu-cheng/90bd80b17fe88f65dd2d

Interesting! This is with the latest master branch? I'll test this locally to see if I can reproduce it.

@xu-cheng I've pushed up a commit which has resolved the issue locally; all tests still pass properly. Let me know if you have any more problems.

Thanks it fixes the problem for me.


Add dual case erc721 receiver

Fixes #633 and fixes #634.

PR Checklist

[x] Tests
[ ] Tried the feature on a public network
[ ] Documentation

LGTM!


quickstart-validium Blockscout new UI screenshot

Update quickstart-validium guide:

change port for explorer new UI
change screenshot of the explorer

Thanks so much @vbaranov :)
Approving and merging now.
Will test in staging later on.


Help with doing parameter selection in nin direction

See testset "Mutate-prune" - "Merge two vertices".
Basic issue is that when selecting indices which might propagate through a SizeStack vertex after having changed the size with an IoChange mutation, one must be careful to not select "out of range".
Either some improvement to allow for the param selection to override the size or some helper function to see what are the valid indices, or maybe both would be useful.
For now, one is better of selecting parameters from the bottom in the "nout" direction.

Uhm, I just checked this and it no longer fails, maybe due to some other improvement.
A helper function could still be useful as it now is very possible to add a bunch of new neurons to one vertex while taking away all from another vertex. At least the user should have a chance to avoid this.

Ok, this turned out to be a big can of worms in disguise. Luckily a working solution seems to be on the way in #37
Concatentations + elementwise ops + emergence = trouble!
Here it goes just for the record:
Assume we have a concatenation c1 = [v1, v2, v1] (v1 appearing twice is a crucial component) and another one c2 = [v3, v3, v4] and that nout(c1) == nout(c2). The next ingredient is an elementwise op e = c1 + c2.
Now, how can one select outputs from e in a consistent manner?
To break it down, the outputs of c1 is [v1_1, v1_2, ..., v1_N, v2_1, v2_2,...,v2_M, v1_1, ... v1_N] while the outputs of c2 is [v3_1, v3_2, ...,v3_P, v3_1, v3_2, ..., v3_P, v4_1, ..., v4_Q] (N, M, P, Q are nout(v1), nout(v2), nout(v3), nout(v4) respectively).
Now, selecting e.g output index 2 from e, implictly also selects both 2 + N + M (due to c1[2] == c1[2 + N + M]) and 2 + P (due to c2[2] == c2[2 + P]). The former also implicitly selects c2[2 + N + M] while the latter implicity selects c1[2 + P] which depending on how P relates to N + M just propagates to having even more indices selected. Yuck! Thank you JuMP for coming to the rescue here!


could not compile ic-agent (lib) due to 2 previous errors

target wasm32-unknown-unknown
ic-agent-0.25.0/src/agent/mod.rs:556:19
    |
556 |             match retry_policy.next_backoff() {
    |                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^ pattern `Some(_)` not covered
    |
note: `std::option::Option<std::time::Duration>` defined here
   --> .rustup/toolchains/stable-x86_64-apple-darwin/lib/rustlib/src/rust/library/core/src/option.rs:572:5
    |
564 | pub enum Option<T> {
    | ------------------
...
572 |     Some(#[stable(feature = "rust1", since = "1.0.0")] T),
    |     ^^^^ not covered
    = note: the matched value is of type `std::option::Option<std::time::Duration>`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
    |
576 ~                 None => return Err(AgentError::TimeoutWaitingForResponse()),
577 ~                 Some(_) => todo!(),
    |

error[E0308]: mismatched types

ic-agent-0.25.0/src/agent/http_transport/reqwest_transport.rs:36:47
   |
36 |     pub fn create<U: Into<String>>(url: U) -> Result<Self, AgentError> {
   |            ------                             ^^^^^^^^^^^^^^^^^^^^^^^^ expected `Result<ReqwestTransport, AgentError>`, found `()`
   |            |
   |            implicitly returns `()` as its body has no tail or `return` expression
   |
   = note:   expected enum `Result<ReqwestTransport, AgentError>`
           found unit type `()`

You need the wasm-bindgen feature.


Provide zerocopy trait implementations behind feature flag

A common use of unsafe code is to access or modify the bytes of libc types (e.g. by transmuting them; here's an example). Many libc types could implement the zerocopy traits (FromBytes, AsBytes, and Unaligned) by using a custom derive, so this would just be a matter of adding #[cfg_attr(feature = "zerocopy", derive(FromBytes, AsBytes, Unaligned))] to the types which support it. This would allow all of those uses to be safe.
If this is something that the maintainers would be open to, I'd be happy to put up a PR.

This needs some level of team discussion since it would involve an ecosystem crate. I don't really have any objection for an addition in 1.0 (or later) as long as it is pretty unintrusive.

This needs some level of team discussion since it would involve an ecosystem crate, I suggested a Zulip discussion on #3924 (comment). I don't really have any objection for an addition in 1.0 (or later) as long as it is pretty unintrusive.

I've started a Zulip thread.

@tgross35 Is there an official process to put this proposal forward somewhere? Not sure whether to take the radio silence on the Zulip thread as disinterest or lack of opposition.

I think the t-libs/crates channel just doesn't get very much traffic. I'll poke things here tomorrow.

Sounds good, thanks!

Per the Zulip discussion, I'm going to close this for now.


Version mismatch - How to get the current one?

Hello,
thank you for all your effort and your time!
I saw now, that the spotty repo was archived and you switched over to this one. Are there any changes to do to get the updates from this repo?
I'm a little bit confused, since in the changelog the latest version is 0.4.2 (probably from the upstream), in the tags there is a version spotty-v1.3.0 and in LMS I see the version 4.8.8 installed. It would be great, if you can clarify this and tell me how I can be sure, that the correct and up to date version is installed.
GitHub tags

LMS plugins

0.4.2 is - as you guessed - the upstream library version I'm based on.
1.3.0 is the helper application's version, which obviously can differ from the library version and the plugin version.
4.8.8 is the plugin's version.
The plugin uses the helper application, which in turn uses the library. Therefore the different version numbers.

Thanks


Calculate MAX_DIFF at __init__ Time.

Hi all,
MAX_DIFF is required for the basis generation (in __init__ time code) to be compilable. It may be worth removing this constant to make the code more readable since it will not occur at run time. However, it is theoretically possible that someone may want a large basis ~10-100 vectors. In this case being able to compile this code segment could be useful. Regardless, it is possible for the minimum MAX_DIFF to be calculated at __init__ time from the noll_indices. This could reduce memory usage (and hence time as well) be reducing MAX_DIFF for smaller, ,more typical cases.
Regards
Jordan.

So I decided to abandon MAX_DIFF entirely because it was faster and made the code much simpler.


Use time.NewTimer() instead of time.After()

For efficiency, cancel time.Timer after no longer needed. See https://pkg.go.dev/time#After
Note on behavior change:
timeout duration <= 0 now means waiting forever instead of immediately times out..

Very interesting, I didn't know time.After() leaks memory!

The underlying Timer is not recovered by the garbage collector until the timer fires.

Out of curiosity I wanted to see it for myself so I added profiling in https://github.com/andreykaipov/goobs/pull/57 and sure enough:
❯ GOOBS_PROFILE=memprofile=mem.out OBS_PORT=4455 go test -v -run=profile client_test.go
❯ go tool pprof -top -sample_index=inuse_space mem.out
Type: inuse_space
Time: Sep 19, 2023 at 6:05pm (CDT)
Showing nodes accounting for 512.05kB, 100% of 512.05kB total
      flat  flat%   sum%        cum   cum%
  512.05kB   100%   100%   512.05kB   100%  time.NewTimer
         0     0%   100%   512.05kB   100%  command-line-arguments_test.Test_profile
         0     0%   100%   512.05kB   100%  github.com/andreykaipov/goobs/api.(*Client).SendRequest
         0     0%   100%   512.05kB   100%  github.com/andreykaipov/goobs/api/requests/scenes.(*Client).GetSceneList
         0     0%   100%   512.05kB   100%  testing.tRunner
         0     0%   100%   512.05kB   100%  time.After (inline)

Hope you don't mind I updated your PR to use defer timer.Stop() instead of potentially waiting forever. Found that in https://github.com/golang/go/issues/27169 and it seems like it's hit others too. Thanks again!

@andreykaipov no problem on the updated PR. defer also works for efficiency.
But I am curious about:

As I understand, the timeout duration <= 0 means immediately times out (without the if in my newTimeoutTimer). So how is this better than waiting forever for c.IncomingResponses/authComplete? In my opinion, "no timeout" fits duration <= 0.
I think the possibility of waiting forever mentioned in the golang issue is different from what I mean in (1) since the one in the golang issue is caused by deadlock while the one I mentioned in (1) is about interpretation of duration <= 0.

Thank you for the merge.

My apologies -- I thought the motivation of the PR was only for the timer memory efficiency. Sorry for discarding your timeout changes without any comment.
I suppose I was concerned about backwards compatibility for anybody that might've been using a zero timeout already. However thinking about it now... that'd be impossible since immediately timing out wouldn't allow for the connection to establish in the first place.
I'm not against adding a way to specify an indefinite timeout but out of curiosity does using a really large timeout (e.g. 24 hours) not meet your needs?

@andreykaipov
The default timeout works for me and setting large timeout is not an issue for me if needed.
I agree that the need of unlimited timeout is almost as unreasonable as immediate timeout.
But in my opinion, unlimited makes more sense than immediate timeout.
I just wanted to clarify between the deadlock issue vs unlimited timeout.
Not really against immediate timeout though, but my preference is over unlimited in the case of a value <= 0 .
If you prefer to keep the existing behavior, that is fine as well.


add config for new Bazel CI

apologies for missing your project when migrating to the new CI.
@ittaiz I have invited you to Buildkite. Please take a look at https://github.com/bazelbuild/continuous-integration/blob/master/buildkite/README.md for a getting started guide.

that was just a test of course :P ... good catch .. it's early :D


Release v2.1.0

Summary
This PR release the v2.1.0 version to production
Other Informations
Contained in this version:

New lightweight LoggerService compatible w/ the debug package (https://github.com/Mindsers/yabf/issues/35, https://github.com/Mindsers/yabf/pull/36)
New documentation block for LoggerService (https://github.com/Mindsers/yabf/pull/36)
Yabf adopts a new code of conduct to enforce a harassement-free experience for everyone in the community
Upgrade some dependencies.
Optimize build steps.
Remove a disapointing log message.
Fix typo error on the ava config. Due to this error the avajs never worked as expected.
Error about build instructions are clearer. The name of the class is correctly specified.

This pull request fixes 2 alerts when merging a7b525884a3559be80ebcbdb3245b1555a7dca95 into 85da638234d63ad14715efd0b437d148e26d6fd9 - view on LGTM.com
fixed alerts:

1 for Wrong use of 'this' for static method
1 for Unused variable, import, function or class

Comment posted by LGTM.com


const char* as return values for read/write characteristic callbacks,…

… add extern C keyword to public header files

Thank you!


Enabling Defender for specific subscriptions or management groups instead of everywhere

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description
It seems that the scope of the assignment that enables Defender is "root" in this Terraform template. This does not suit our organization because we do not want Defender to be enabled in Sandbox management group in order to avoid the unnecessary expense in non-production resources. Is there a way to enable Defender for specific subscriptions or management groups?

Thank you for the question @sean-kang
Our recommendation in this scenario would be to create a copy of the Policy Assignment in your custom library (as specified by the library_path input variable) and add the Sandbox Management Group to the notScopes value.
But if you really want to change the scope, this is where the ability to edit archetype definitions comes into play, as documented on the Wiki in the following example:
[Examples] Expand built in archetype definitions
To cover your specific scenario, you would create the following two files and place them in your custom library.
lib/archetype_exclusion_es_root.tmpl.json
{
  "exclude_es_root": {
    "policy_assignments": [
      "Deploy-ASC-Configuration"
    ],
    "policy_definitions": [],
    "policy_set_definitions": [],
    "role_definitions": [],
    "archetype_config": {
      "parameters": {},
      "access_control": {}
    }
  }
}

lib/archetype_extend_es_landing_zones.tmpl.json
{
  "extend_es_landing_zones": {
    "policy_assignments": [
      "Deploy-ASC-Configuration"
    ],
    "policy_definitions": [],
    "policy_set_definitions": [],
    "role_definitions": [],
    "archetype_config": {
      "parameters": {},
      "access_control": {}
    }
  }
}

Note you will need to provide all of the required parameters to configure this Policy Assignment at the new scope as the configuration included through configure_management_resources will no longer work on this Policy Assignment due to the change of scope.
Hope this helps but please let us know if you have further questions regarding this.

I copied the policy assignment to our library and edited the notScopes as recommended and it seems to be working. I added the following line.
lib/policy_assignments/policy_assignment_es_deploy_asc_configuration.tmpl.json
"notScopes": [ "${root_scope_resource_id}-sandboxes" ]
Thank you for your help.


watch should ignore .DS_Store

When browsing the site source the browser gets updated a lot. I'm guessing it is because .DS_Store is updated and watch triggers a page reload. If that's the case might it be an idea to support a watch exclude list supporting file globs

It is https://github.com/spf13/hugo/blob/b5030782ae5e6cda3aa7a7dd9fb8ffa4f2d16a32/commands/hugo.go#L748
I think you must experience "something else"
As to your other question; we have a ignoreFile config option for /content -- and there is an open issue about doing the same for /static.

could it be .git (wouldn't have thought so as it is two levels up). I'm starting to speculate if the Tower git app is triggering something, just navigating the git changes triggers a site rebuild.


Update chain.json

remove http link

Please use a descriptive title for your PR.
By "remove http link" in your description did you intend to update to https? I see the end point is still functional.

Which is correct? https://github.com/cosmos/chain-registry/pull/4401


Transaction fails with 100% gas consuming

IBAMM.zip
to reproduce the problem use the ABI with contract -> 0xD839F4468A47Ac17321c28669029d069AB73F535
call method -> liquidateBorrow
parameters -> 0xc207a5dc49771a71367bd3a97fe58aaf9c5dfdae, 3131255, 0xec2bf7ec6afcec1594baf4f33736573d0a12c25e
result: On staticCall method pass but on normal it hang and consume all the gas

I just tried to reproduce in my local environment(by loading binaries from mainnet). Here is what I see.
I can confirm the transaction failed, but _100% gas consuming is not confirmed. Gas used ~474_000.
The tx is failed in a very weird way. It looks like this contract cannot be found. I'm still working on it. It's more like a bad way to produce in my local env.
Meantime, can you please share a minimum repo with us including solidity files? That will help a lot. @Roger-RumbleFish

Hi, @Roger-RumbleFish
The max cycles of a layer2 transaction has been tune up to 500M since mainnet_v1_block#233000.
The issue should now be resolved. Can you confirm this?
References

fork(consensus): Increase l2 tx max cycles from 150M to 500M
https://github.com/godwokenrises/godwoken/pull/852
https://github.com/godwokenrises/godwoken-info/pull/78

Please feel free to re-open this issue if you still encounter this kind of tx.


New package: Generators v0.1.0

Registering package: Generators
Repository: https://github.com/zot/Generators.jl
Created by: @zot
Version: v0.1.0
Commit: 1d64090beb2d8b68615183e9c424808fe5be2030
Reviewed by: @zot
Reference: https://github.com/zot/Generators.jl/commit/1d64090beb2d8b68615183e9c424808fe5be2030#commitcomment-61630403
Description: Lightweight, task-based generators for Julia

@zot please see the message above.  Once you fix the automerge issues you can register again the new revision without changing the version number and this pull request will be automatically updated.
[noblock]

Hi @giordano, I have a jldoctest that automatically runs for me from make.jl. Isn't this run by CI?