HBASE-26150 Let region server also carry ClientMetaService

:broken_heart: -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 _

_ master Compile Tests _

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

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

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

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

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

_ Patch Compile Tests _

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

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

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

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

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

-0 :warning:
javadoc
0m 22s
hbase-client generated 1 new + 3 unchanged - 0 fixed = 4 total (was 3)

_ Other Tests _

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

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

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

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

45m 51s

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-3550/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 0e9b08079cc5 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 2e9ab3ce94

Default Java
AdoptOpenJDK-1.8.0_282-b08

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/1/artifact/yetus-jdk8-hadoop3-check/output/diff-javadoc-javadoc-hbase-client.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/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-3550/1/testReport/

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

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

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

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

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

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

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

_ Patch Compile Tests _

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

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

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

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

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

-0 :warning:
javadoc
0m 27s
hbase-client generated 1 new + 55 unchanged - 0 fixed = 56 total (was 55)

_ Other Tests _

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

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

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

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

51m 36s

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-3550/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 328d8c697e89 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
master / 2e9ab3ce94

Default Java
AdoptOpenJDK-11.0.10+9

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/1/artifact/yetus-jdk11-hadoop3-check/output/diff-javadoc-javadoc-hbase-client.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/1/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-3550/1/testReport/

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

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

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

_ Prechecks _

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

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

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

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

_ master Compile Tests _

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

+1 :green_heart:
mvninstall
4m 26s
master passed

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

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

+1 :green_heart:
spotbugs
7m 55s
master passed

_ Patch Compile Tests _

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

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

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

+1 :green_heart:
cc
6m 26s
the patch passed

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

-0 :warning:
checkstyle
1m 11s
hbase-server: The patch generated 4 new + 172 unchanged - 7 fixed = 176 total (was 179)

-0 :warning:
whitespace
0m  0s
The patch has 1 line(s) that end in whitespace. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

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

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

+1 :green_heart:
spotbugs
14m 35s
the patch passed

_ Other Tests _

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

92m 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-3550/1/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile cc hbaseprotoc prototool

uname
Linux 0e536760ff4a 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
master / 2e9ab3ce94

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

whitespace
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/1/artifact/yetus-general-check/output/whitespace-eol.txt

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

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

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/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
0m 35s
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 16s
Maven dependency ordering for branch

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

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

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

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

_ Patch Compile Tests _

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

-1 :x:
mvninstall
1m 11s
root in the patch failed.

-1 :x:
compile
0m 29s
hbase-client in the patch failed.

-1 :x:
compile
0m 39s
hbase-server in the patch failed.

-0 :warning:
javac
0m 29s
hbase-client in the patch failed.

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

-1 :x:
shadedjars
4m 26s
patch has 24 errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 41s
hbase-server generated 3 new + 21 unchanged - 0 fixed = 24 total (was 21)

_ Other Tests _

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

-1 :x:
unit
0m 30s
hbase-client in the patch failed.

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

-1 :x:
unit
0m 41s
hbase-server in the patch failed.

31m 38s

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-3550/2/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / de84c1765a

Default Java
AdoptOpenJDK-1.8.0_282-b08

mvninstall
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-jdk8-hadoop3-check/output/patch-mvninstall-root.txt

compile
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-jdk8-hadoop3-check/output/patch-compile-hbase-client.txt

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

javac
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-jdk8-hadoop3-check/output/patch-compile-hbase-client.txt

javac
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-jdk8-hadoop3-check/output/patch-compile-hbase-server.txt

shadedjars
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-jdk8-hadoop3-check/output/patch-shadedjars.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-jdk8-hadoop3-check/output/diff-javadoc-javadoc-hbase-server.txt

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

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/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-3550/2/testReport/

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

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

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

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

_ Prechecks _

_ master Compile Tests _

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

+1 :green_heart:
mvninstall
5m 13s
master passed

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

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

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

_ Patch Compile Tests _

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

-1 :x:
mvninstall
1m 32s
root in the patch failed.

-1 :x:
compile
0m 31s
hbase-client in the patch failed.

-1 :x:
compile
0m 47s
hbase-server in the patch failed.

-0 :warning:
javac
0m 31s
hbase-client in the patch failed.

-0 :warning:
javac
0m 47s
hbase-server in the patch failed.

-1 :x:
shadedjars
4m 18s
patch has 24 errors when building our shaded downstream artifacts.

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

_ Other Tests _

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

-1 :x:
unit
0m 30s
hbase-client in the patch failed.

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

-1 :x:
unit
0m 45s
hbase-server in the patch failed.

41m 51s

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-3550/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux c2d2d9cc967a 4.15.0-128-generic #131-Ubuntu SMP Wed Dec 9 06:57:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / de84c1765a

Default Java
AdoptOpenJDK-11.0.10+9

mvninstall
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-jdk11-hadoop3-check/output/patch-mvninstall-root.txt

compile
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-jdk11-hadoop3-check/output/patch-compile-hbase-client.txt

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

javac
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-jdk11-hadoop3-check/output/patch-compile-hbase-client.txt

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

shadedjars
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-jdk11-hadoop3-check/output/patch-shadedjars.txt

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

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

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/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-3550/2/testReport/

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

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

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

_ Prechecks _

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

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

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

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

_ master Compile Tests _

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

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

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

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

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

_ Patch Compile Tests _

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

-1 :x:
mvninstall
1m 16s
root in the patch failed.

-1 :x:
compile
0m 56s
hbase-client in the patch failed.

-1 :x:
compile
0m 50s
hbase-server in the patch failed.

-0 :warning:
cc
0m 56s
hbase-client in the patch failed.

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

-0 :warning:
javac
0m 56s
hbase-client in the patch failed.

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

-0 :warning:
checkstyle
1m 16s
hbase-server: The patch generated 1 new + 172 unchanged - 7 fixed = 173 total (was 179)

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

-1 :x:
hadoopcheck
1m 30s
The patch causes 24 errors with Hadoop v3.1.2.

-1 :x:
hadoopcheck
3m  3s
The patch causes 24 errors with Hadoop v3.2.1.

-1 :x:
hadoopcheck
4m 41s
The patch causes 24 errors with Hadoop v3.3.0.

-1 :x:
hbaseprotoc
0m 23s
hbase-client in the patch failed.

-1 :x:
hbaseprotoc
0m 50s
hbase-server in the patch failed.

-1 :x:
spotbugs
0m 19s
hbase-client in the patch failed.

-1 :x:
spotbugs
0m 32s
hbase-server in the patch failed.

_ Other Tests _

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

47m  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-3550/2/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile cc hbaseprotoc prototool

uname
Linux 52bc432bf9f6 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
master / de84c1765a

Default Java
AdoptOpenJDK-1.8.0_282-b08

mvninstall
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-general-check/output/patch-mvninstall-root.txt

compile
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-general-check/output/patch-compile-hbase-client.txt

compile
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-general-check/output/patch-compile-hbase-server.txt

cc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-general-check/output/patch-compile-hbase-client.txt

cc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-general-check/output/patch-compile-hbase-server.txt

javac
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-general-check/output/patch-compile-hbase-client.txt

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

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

hadoopcheck
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-general-check/output/patch-javac-3.1.2.txt

hadoopcheck
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-general-check/output/patch-javac-3.2.1.txt

hadoopcheck
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-general-check/output/patch-javac-3.3.0.txt

hbaseprotoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-general-check/output/patch-hbaseprotoc-hbase-client.txt

hbaseprotoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-general-check/output/patch-hbaseprotoc-hbase-server.txt

spotbugs
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-general-check/output/patch-spotbugs-hbase-client.txt

spotbugs
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/2/artifact/yetus-general-check/output/patch-spotbugs-hbase-server.txt

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

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

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

_ Prechecks _

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

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

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

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

_ master Compile Tests _

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

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

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

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

+1 :green_heart:
spotbugs
7m 45s
master passed

_ Patch Compile Tests _

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

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

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

+1 :green_heart:
cc
6m 14s
the patch passed

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

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

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

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

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

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

_ Other Tests _

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

71m 59s

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-3550/3/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile cc hbaseprotoc prototool

uname
Linux f8ad221f3b61 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
master / f3175c5ab6

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

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

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

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

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ master Compile Tests _

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

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

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

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

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

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

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

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

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

-1 :x:
unit
149m 29s
hbase-server in the patch failed.

191m 55s

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-3550/3/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / f3175c5ab6

Default Java
AdoptOpenJDK-1.8.0_282-b08

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/3/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-3550/3/testReport/

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

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

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

+1 :green_heart:
mvninstall
4m 54s
master passed

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

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

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

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

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

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

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

-1 :x:
unit
204m 30s
hbase-server in the patch failed.

250m 45s

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-3550/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 89c96543e322 4.15.0-128-generic #131-Ubuntu SMP Wed Dec 9 06:57:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / f3175c5ab6

Default Java
AdoptOpenJDK-11.0.10+9

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3550/3/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-3550/3/testReport/

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

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

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

_ Prechecks _

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

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

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

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

_ master Compile Tests _

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

+1 :green_heart:
mvninstall
4m 17s
master passed

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

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

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

_ Patch Compile Tests _

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

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

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

+1 :green_heart:
cc
6m 39s
the patch passed

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

-0 :warning:
checkstyle
1m 13s
hbase-server: The patch generated 1 new + 172 unchanged - 7 fixed = 173 total (was 179)

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

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

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

+1 :green_heart:
spotbugs
9m 29s
the patch passed

_ Other Tests _

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

83m 12s

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-3550/4/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile cc hbaseprotoc prototool

uname
Linux c8f58d521665 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
master / f3175c5ab6

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

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

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

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

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

_ Prechecks _

_ master Compile Tests _

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

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

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

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

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

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

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

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

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

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

186m 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-3550/4/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / f3175c5ab6

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

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

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

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

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

_ Prechecks _

_ master Compile Tests _

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

+1 :green_heart:
mvninstall
5m  4s
master passed

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

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

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

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

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

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

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

+1 :green_heart:
unit
202m 54s
hbase-server in the patch passed.

248m 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-3550/4/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 801c5ee43d0b 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
master / f3175c5ab6

Default Java
AdoptOpenJDK-11.0.10+9

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

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

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

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

_ Prechecks _

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

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

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

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

_ master Compile Tests _

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

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

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

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

+1 :green_heart:
spotbugs
7m 52s
master passed

_ Patch Compile Tests _

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

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

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

+1 :green_heart:
cc
6m 22s
the patch passed

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

+1 :green_heart:
checkstyle
0m 11s
The patch passed checkstyle in hbase-protocol-shaded

+1 :green_heart:
checkstyle
0m 29s
The patch passed checkstyle in hbase-client

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

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

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

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

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

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

_ Other Tests _

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

72m  5s

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-3550/5/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile cc hbaseprotoc prototool

uname
Linux 5a417a9da91a 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
master / 73a0411bb9

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

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

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

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

_ Prechecks _

_ master Compile Tests _

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

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

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

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

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

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

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

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

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

+1 :green_heart:
unit
209m 36s
hbase-server in the patch passed.

251m  8s

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-3550/5/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 20acb5b9370e 4.15.0-128-generic #131-Ubuntu SMP Wed Dec 9 06:57:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 73a0411bb9

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

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

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

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


Django version mismatch between README and install_requires.txt

README says this project supports Django 3.2, but install_requires.txt specifies Django>=2.2,<3.2, and pip is unable to install the package alongside Django 3.2

Thanks for bringing this to our attention! Release 2.1.1 should resolve this issue.


[cherry-pick][sui-transaction-builder] Remove dependency on sui-adapter (#11163)

Description
Remove logic in the transaction builder that relies on the execution layer, namely:

Type checking move call parameters, which other SDKs do not do, and is complicated by execution versioning.
Preventing calls to non-entry functions in Normal execution mode (which is not longer a restriction with the introduction of programmable transactions).

This removes the dependency on sui-adapter from sui-json and sui-sdk.
Test Plan
$ cargo simtest
$ env SUI_SKIP_SIMTESTS=1 cargo nextest run

Type of Change

[x] user-visible impact
[x] breaking change for a client SDKs
[x] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release Notes

unsafe_moveCall and unsafe_batchTransaction now ignore their execution_mode parameter, and always allow calls to non-entry programmable transactions.
Rust SDK no longer performs type resolution and checks (matching behaviour with TypeScript SDK).

Closing, as no longer necessary!


Add a trait/derive macro for transforming Rust type definitions into Binja Type objects

Supersedes #4545.
This time around I was able to see this work through to a good enough state to not publish as a draft. Obviously, I would very much like feedback on this, as introducing a proc-macro into the codebase adds a clear extra maintenance burden that normal Rust code doesn't come with.
Overview
This PR adds the following trait:
pub trait AbstractType {
    const SIZE: usize = std::mem::size_of::<Self>();
    const ALIGN: usize = std::mem::align_of::<Self>();
    fn resolve_type() -> Ref<Type>;
}

Implementing this trait allows creating a Type object corresponding to the layout and representation of whatever type implements it. For example, take the following type:
#[derive(AbstractType)]
#[repr(C)]
struct S {
    first: u64,
    second: u8,
    third: i32
}

Calling S::resolve_type() produces the following type (shown after defining it in a view):

Derive macro
The accompanying derive macro is very convenient for automatically generating implementations of the AbstractType trait, as long as the deriving type meets the following requirements:

For structs/unions, the type must be #[repr(C)], and must have named fields.
For enums, the type must not be #[repr(C)] but instead #[repr(<int>)] (e.g. u8, u64). Also, variants must not contain any data, and must have an explicit discriminant. Note that usize and u128 (and their signed counterparts) are not supported as enum reprs.

Alignment
The derive macro supports #[repr(packed)] and #[repr(align)] on types and will propagate that information into the generated Binja Type (i.e. marking a struct #[repr(packed)] will result in a __packed type in Binja).
Named types
Named types are supported by decorating a field with a #[named] attribute. As an example:
#[derive(AbstractType)]
#[repr(u64)]
enum E {
    One = 1,
    Two = 2,
}

#[derive(AbstractType)]
#[repr(C)]
struct S {
    first: u64,
    #[named]
    second: E,
}

The result of S::resolve_type() is the following type:

Note that defining S in a view does not require that E already be defined. As long as E is eventually defined, then clicking on the type of second will redirect to the correct type.
Pointers
Any pointer fields (of type *const T or *mut T) must be decorated with #[width = "<type>"], where the specified type implements AbstractType. Since pointers can change width depending on architecture, users must specify the width ahead of time. (Note: In theory the width should be restricted to only primitive integer types, but I didn't feel like hardcoding that decision at the moment). As an example, if we modify S from above to look like:
#[derive(AbstractType)]
#[repr(C)]
struct S {
    first: u64,
    #[named]
    #[width = "u64"]
    second: *const E,
}

Then we will get the following:

Miscellaneous notes

I'm not sure if there should be a #[name = "..."] field attribute that allows specifying a name for the type that's different than the name of the Rust type.
Since it's likely that pointers will always be of a single size for a given binary view, I wonder if instead of decorating each pointer field with #[width = "..."], it makes more sense to decorate the struct itself with #[pointer_width = "..."] or something similar.
Should I add tests to verify that the generated Binja types are what we expect them to be? It's possible that I haven't squashed every possible edge-case bug.

I'm not going to be comfortable merging this until we have tests to ensure it doesn't go stale...

For sure, I'll look into adding some tests. I probably should have included them from the start since I was using a standalone Rust plugin to test how the generated types would look in the UI. I see that Type implements PartialEq, would this work for my purposes, so that I could test using assert_eq? I don't know how type equality is done in Binja, and what exactly is compared.

Please add the #[name = "..."] thing.

Yeah, this is a good idea in principle. I'm thinking there should be a single attribute here instead of two (named and name), so that the mental model becomes: if a string literal value isn't provided, then the name of the Rust type is used as the default. Bikeshedding on an attribute name is definitely welcome here, as well as for the #[pointer_width] attribute (that's not a very good name imo).

I'm not sure I understand how #[repr(align)] works. Could you please provide an example?

Decorating a type declaration with #[repr(align(N))] changes that type's minimum alignment to be at least N. For example, say a struct's normal alignment is 4 bytes. Then, decorating the struct definition with #[repr(align(8))] will change it to be 8-byte aligned. However, decorating it with #[repr(align(2))] will keep the alignment at 4. I also uses this internally in my macro for doing type-mocking of pointer types:
// Assuming we know T
const ALIGN: usize = std::mem::align_of::<T>();
const SIZE: usize = std::mem::size_of::<T>();

#[repr(C)]
#[repr(align(ALIGN))] // invalid syntax - we use `elain` to accomplish this
struct Mock {
    t: [u8; SIZE],
}

We've basically created a type with arbitrary size and alignment, since we can change the values of the SIZE and ALIGN constants. And, since align_of<[u8; N]> == align_of<u8> == 1, we know that align_of::<Mock> == ALIGN since ALIGN is always at least 1.

Is there a way to omit #[named]? Is it possible to fall back on to being named if the type is otherwise unrecognized?

There might be some cases where users might want to keep the type definition inline rather than reference a named type. I think for that reason, always falling back to the Rust name as a default might be too opinionated.

Thanks for the additional feedback. I already mentioned this in Slack, but don't worry about assert_eqing types against each other; so long as the procedural macro is able to generate valid API code that gets checked by cargo when we build, I'll be happy with it.

Bikeshedding on an attribute name is definitely welcome here, as well as for the #[pointer_width] attribute (that's not a very good name imo).

Personally I'm fine with name, named, and pointer_width. If you wanna merge name and named, I'm more partial to named since it has to do with named_types.

There might be some cases where users might want to keep the type definition inline rather than reference a named type. I think for that reason, always falling back to the Rust name as a default might be too opinionated.

What about the opposite then? Add a #[inline]/#[inline_type]

What about the opposite then? Add a #[inline]/#[inline_type]

IMO this feels slightly awkward, since then the default behavior with no attributes would be to create a named type using the Rust type's name, and then providing #[name = "..."] would add a custom name whereas #[inline_type] would remove the name. So basically we have two switches controlling a singe property.

Personally I'm fine with name, named, and pointer_width. If you wanna merge name and named, I'm more partial to named since it has to do with named_types.

For some reason, I think if we wrap all three in a #[binja(...)] attribute it might actually look fine. So, it would be #[binja(named)], #[binja(name = "...")], and #[binja(pointer_width = "u64")]. Then, it's kind of like those attributes belong to the binja namespace, whereas when they nakedly decorate a field they feel a bit out of place. Is binja alright for this or would binaryninja be preferred? I don't know how hard y'all stick to not using the Binja nickname in user-facing code/docs.
Btw, should the value of pointer_width be changed to an int literal instead of a string literal? That way the "width" can be interpreted more literally, and it seems that Binja supports pointers of arbitrary width.

Alright, I think all the behavioral changes are taken care of. To briefly demonstrate: a type that derives AbstractType might now look like this:
#[derive(AbstractType)]
#[repr(u64)]
enum E {
    One = 1,
    Two = 2,
}

#[derive(AbstractType)]
#[repr(C)]
#[binja(pointer_width = 8)]
struct S {
    first: u64,
    #[binja(named)]
    second: *const E,
}

What remains to be done is adding documentation and tests. Ideally I would like #5435 to be resolved and then rebase on top of it, however that might take some time so in the meantime I'll go with the original suggestion of adding to examples/ since those aren't run in CI.

@KyleMiles This PR should be ready for re-review now. In total, the new changes since you last reviewed are the commit range 98fde41 through d1205c9 (total changes).
The only thing missing at this point is support for fields of type void *, however I'm not sure how to support it given that raw void is not a valid type for a field. Additionally, the documentation for std::ffi::c_void explain that void corresponds to () but void * corresponds to*{const,mut} c_void rather than *{const,mut} ().

I have discussed this with @mkrasnitski and the plan forward for this is as a separate crate. We need to actually version the binaryninja crate with an attached ABI version (i.e. 0.1.0-69) before this can be split off.
We should aim to have a myriad of helper crates instead of maintaining large effort abstractions/helpers in this repository. This will allow greater flexibility and a clear line between where the API ends and the helpers begin, something that is not clear within our python bindings.
We are going to keep this PR open until the above is at-least partially completed.


Why are all generated splash screens for iOS on the same size?

On iOS the @1, @2 and @3 images are all 2732x2732 px.
Xcode also gives a warning when running "The launch screen exceeds the memory limit and may not display during app launch. Use images requiring less space."
Shouldn't these be smaller for @1 and @2?
When the app is launched, you first see a black screen. If I reduce the @3 to 2400x2400px I see the splashscreen instead of the black screen again on an iPhone 14. I have to do the same on an iPhone 6 with @2 and so on. It seems to me that the tool still has a bug here when creating the splashscreens.
Note: The changes are only visible when you delete the app and restart and reset the device / simulator.

Facing the same issue.
for 1x, 2x, and 3x its generating same size image can you guys check here whats going wrong?

Looks like this project doesn't get enough attention...

So to make it clear: What are the correct sizes for @1, @2 & @3 ?
I can't get the splash screen to work on iOS.


Fix handling of erlang syntax errors

I noticed that Erlang's SyntaxError or MissingTokenError are currently triggering an ArgumentError when trying to generate the error message:

** (TokenMissingError) got ArgumentError with message "argument error" while retrieving Exception.message/1 for %TokenMissingError{...}

This is due to error.snippet being a map %{content: "erlang", offset: 6} instead of a string, this PR fixes it to just a string: "erlang" as expected by TokenMissingError.message/1.
I couldn't figure out where this offset was being used so I just removed it, but perhaps the fix is more involved in some other cases?
Before

After

 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.


fix python3 compatibility in sqla examples without future

Fixes #1364
I tried running the examples for the first time in a while and got ImportError: No module named 'future'. After messing with it, I don't think this module is necessary to run the examples.
It's better to just use __str__ in the models to be compatible with both python 2 and 3. I thought maybe python_2_unicode_compatible was being used to make __unicode__ work in python 3, but it doesn't.

I added these when I added support to python 3 for this example.
I thought future was a builtin module in python 2?
Didn't want to break anything, since __str__ in python 2 should return bytes and not a string.
If it works without it I guess that's better.


[BUG] wrong value is displayed in the GUI panel

it seems the value has range in 0-255.
i know i can use in { 0.0, 5.0 } for float, but for vec3/vec4 i don't know how to limit the range, or simply just use the original value the vec3/vec4 have and don't multiply by 255?

Back when we added this feature it was a restriction in dat.gui which we use to draw the gui. I will check if this has changed, but don't get your hopes up.

ok, thanks anyway~ :)

hi, @Malacath-92
1, can we have a new option to specify the value is a color type? and by default it will be the type as how vec4 does?
for example vec3 hslAdjust = vec3(0.0, 2.1, 1.0) on the dat.GUI it will have hslAdjust.x, hslAdjust.y, hslAdjust.z
and if you specify something like vec3 hslAdjust = vec3(0.0, 2.1, 1.0) as color then it will be a color option on the GUI?
2, can we add step support for the iUniform?
then for the dat.GUI we call .step(0.05);
for example
#iUniform float myScalar = 1.0 in { 0.0, 5.0 } step .05
#iUniform vec3 hslAdjust = vec3(0.0, 2.1, 1.0) step .1  // invalid for as color
what do you think?

That'd both be possible:

not sure if it's a good idea to introduce a new keyword for this, but rather a new type. So it'd look like this

#iUniform color3 hslAdjust = color3(0.0, 2.1, 1.0)

was something I wanted to do. Implicitly that's what we're forced to do for integer types, so only need to add a parsing for it. It's unclear how we would handle that though when the underlying types are integers.

1, actually not sure what will people think, vec3 is native type, but you have to learn as xxx new keyword, color3 is good way but don't know if people don't like it. (i like this way)
2, for this situation I think ceil(step) for integer?

I am heavily leaning towards introducing a type for this. It's clear that color3 has similar semantics to vec3, so this isn't an issue. And it is clear that only color3 is supported, as opposed to introducing as color, which doesn't make it clear that only vec3 is supported.

I think it's better to only allow signed integers in that case and present the user with an error otherwise


Revamp Guardian user/roles and permissions model

Problem description
Current user/roles model in Guardian is somewhat simplistic, and often does not map perfectly on business operations. For example policy authors is a very different level of responsibility to policy reviewer/approver, and even more so to token issuance account/role. Currently all these responsibilities are mapped to the same Standard Registry role.
Requirements

Fundamentally separate the concept of users, roles and permissions in Guardian
Introduce granular concept of permissions which could be assigned to users, a user could then perform a specific function within the role if its assigned role 'contains' this permission. These should include (but not limited to):

Policy edit/submit for review
Policy view
Policy approval & publish
...

Introduce a "user admin" role, which allows:

defining new roles from permissions
assigning of roles to users

Create a permissioning system which verifies actor role before any action has been taken throughout Guardian
Package in suitable most-common role set into Guardian so it can be operated immediately 'out of the box' without the need for additional configuration
Create a concept of 'delegation' where a user with a particular role/permission can explicitly 'delegate' this role/permission to another user
Introduce the functionality to produce a report (page, download) which lists all users and their roles/permissions mapping in the system

Definition of done

Roles/permissions functionality is created as specified above
The new functionality is documented

Acceptance criteria

Users are able to fine-tune the user/permissions/roles settings on their system at a granular level
Guardian comes with an out-of-the box set of roles/permissions which allow immediate usage of the system in the most common generic use-cases
It should be possible, for example, for an organisation to set up an SR and then invite multiple users to that SR account, which then will work in the same workspace on different policies but in the same instance

the same for project developers
the same for VVBs

@Neurone please add your thoughts cc: @sergmetelin @justin-atwell @prernaadev01 @anvabr regarding CURD operations

@anvabr Can we update to include the new user management via VCs enabled by the DID spec? cc @Neurone

This should be done via VCs and VCs should be revokable, which would be the key behavior we need to enable.

List of permissions, grouped by type. The standard CRUD model is supported across most of the items. Other 'non-standard' permissions need to be processed and grouped into some generic one which can mean different things for different items.
Guardian Permissions.xlsx


Respect the XDG base directory specification

This doesn’t change the default configuration directory, except when the user defined $XDG_CONFIG_HOME manually in the environment. This patch is best viewed in git diff -w to ignore indentation changes.
The other patch prevents the creation of the configuration directory on the build computer, which is useful for packages in distributions.

Thanks.
It got better.


@react-native-community/async-storage => @react-native-async-storage/async-storage in RN Bare Package

📦 Pull Request
@react-native-community/async-storage has been deprecated and replaced by @react-native-async-storage/async-storage. This updates our dependencies to match the update.
✅ Fixed Issues
n/a
🚨 Test instructions
[Describe any additional context required to test the PR/feature/bug fix.]
⚠ Don't forget to add a semver label!
Please only add one label:

patch: Bug Fix?
minor: New Feature?
major: Breaking Change?
skip-release: It's unnecessary to publish this change.

Is it tested?

Is it tested?

yes with https://github.com/magiclabs/react-native-demo/pull/43

:rocket: PR was released in<EMAIL_ADDRESS><EMAIL_ADDRESS>:rocket:

Hi,
It looks like the test failed and the requester acknowledged that the app wasn't running https://github.com/magiclabs/react-native-demo/pull/43#issuecomment-1483675336
Even before this, there is something odd going on with the async storage where it crashes apps in production but not when running off an expo server
Error: [@RNC/AsyncStorage]: NativeModule: AsyncStorage is null.

This is happening on an Android emulator Pixel_5_API_31 but my FlightTest iOS app also crashes with a memory exception at 0x0 but doesn't when I remove the Magic-SDK entirely.
That's all to say, maybe this will fix this issue, maybe not but something weird with asyncstorage is definitely already happening.


HIVE-27262: send notifications on add / drop / grant / revoke role and grant / revoke privileges

What changes were proposed in this pull request?

HIVE-27262
Why are the changes needed?

Sending an event to transactional listeners on adding / removing / granting / revoking a role or granting / revoking privileges. No notification events were being generated for these scenarios before this change.
Does this PR introduce any user-facing change?

No
Is the change a dependency upgrade?

No
How was this patch tested?

On local setup by running itests. Added tests to itests.

@nrg4878 can you please review?


Assign APTasks to Queues

Is your feature request related to a problem? Please describe.
I cannot assign APTasks to Queues
Describe the solution you'd like
Allow assignment of Tasks to Queues when the parent record is owned by a queue, or allow APTasks to be assigned to queues.

Update the lookup to include queues, probably filtering for that related object type. Include error handling if the queue is not allowed for tasks and the parent object. This may need a text field for APTask ownerId, though this would make reporting quite difficult. Using APTask.OwnerId is not an option due to the Master-Detail relationship.
I would rather not clear the User field if the Task is owned by a Queue, as that may confuse reporting, but here, reporting is inaccurate, so this is a significant lift.

Describe alternatives you've considered
Assigning the APTask to some user and then using Flow on Task to reassign to the parent record owner. (This would require a text field on ActionPlan for the OwnerId of the parent record. How do we handle this when the parent owner changes?)
Additional context
There are a lot of considerations for this, so it is low-priority. For now, updating the Task OwnerId using Flow or a trigger may be the best option, but those values may be overwritten if the APTask is edited.
For now, we have blocked the APTask owner from updating to a queue, and the record will keep the existing value. The hope is that this will not create a loop that will overwrite the Task if the User field is still a User when the Task owner is a Queue.

Partially fixed in release 4.3.0, which will be put on AppExchange shortly. Still curious about how to have a field that holds a user or a queue, as I REALLY don't want to put too much logic in the VF page or controller. If anything, I'd like to move all logic to a central worker class.

@dschach Do you know when ver 4.3 will be on AppExchange? Thanks

Great question. I've been locked out of the repo because I'm not a
Salesforce employee. Currently trying to get access.
On Thu, Oct 13, 2022, 11:30 Emily Cobb @.***> wrote:

@dschach https://github.com/dschach Do you know when ver 4.3 will be on
AppExchange? Thanks
—
Reply to this email directly, view it on GitHub
https://github.com/SalesforceLabs/ActionPlansV4/issues/42#issuecomment-1278019461,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAE3QMLA7WTP66V2JQE52U3WDBILXANCNFSM5YALJYJQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Total transaction counts more than 1 but less than 303.
All interactions with a Safe wallet are from the same account4.
Interaction in a very short period of time (All TX in 6 hours since wallet account setup)
Current token balances of the Safe account are less than 0.026.

after this ,I Got 415 safes.  after that ,I checked this safes with the rule: there are a same wallet who created this safe and execed transactions with this safe（That means: one wallet created a safe and the safe was execed transactions only with the wallet）
after that, I got 193 safes as above.
Methodology
Firstly, we establish a database containing the $Safe airdrop addresses on Dune. Then we extract suspicious accounts that satisfy all types of behavior at the same time from this database.
In other words, an account created before 2022/02/10, having few(5-20) transactions with only one account in a short time(6 hours), leaving no money(<0.02) now, sharing same owners with several(>10) brother/sister accounts from a same parent account(creator) , is most likely to be an airdrop farmer's account.
Furthermore, we track not only ERC20 tokens, but also NFTs, in order not to mistakenly hurt real users.
Based on that, an algorithm was used to identify potential airdrop farmers' accounts. The details of algorithm can be found in the query listed below. All the numeric parts in our method are set as parameters to dynamically modify our strategy. Just simply input the rational parameters and run the query.
Dune link: https://dune.com/queries/1272695
here we can get 415 safes.
after that, I checked with python code below:

Safe Address
0xfdf11fa8ae68ddb3ff2b9138a517e6518f2e8796

update rules:
1.Safe accounts created before 2022/02/102.
2.Total transaction counts more than 1 but less than 30.
3.All interactions with a Safe wallet are from the same account
4.Interaction in a very short period of time (All TX in 6 hours since wallet account setup)
5.Current token balances of the Safe account are less than 0.02.

and 415 safes info as this file:
415.txt

Add a note:

transfer in

exec transaction and transfer out

Reasoning
I think SixDegreeDev provided a good method in #427 ,but there must have some farms even before the "GIP-29: Spin-off safeDAO and launch SAFE Token", so I modified the rule as below:

Safe accounts created before 2022/02/102.
Total transaction counts more than 1 but less than 303.
All interactions with a Safe wallet are from the same account4.
Interaction in a very short period of time (All TX in 6 hours since wallet account setup)
Current token balances of the Safe account are less than 0.026.

after this ,I Got 415 safes. after that ,I checked this safes with the rule: there are a same wallet who created this safe and execed transactions with this safe（That means: one wallet created a safe and the safe was execed transactions only with the wallet）
after that, I got 193 safes as above.

e.g. checking this Safe: https://gnosis-safe.io/app/eth:0xe83867033ac19d27ffd062936b267d748a0c8594/transactions/history
Seems like it doesn't fit to your restrictions. It stores a significant amount of USDC and has made txs during a longer period than 6h.
Also you say that one indicator for airdrop farming has less than 303 tx? So e.g. 300 txs seems to be airdrop farming? That doesn't sound reasonable.
There is quite high chance we would eliminate legit users with your list.

Dear @tschubotz
I'm sorry that I made two mistakes: 1. The deadline in the dune program was written incorrectly, resulting in the generation of unqualified addresses; 2. The serial numbers written in advance in the instructions are merged into the previous line after automatic typesetting.
I have made changes:
1、The description text above has been updated;

2、The DUNE program has been modified and rerun. The new DUNE address is https://dune.com/queries/1287862  See the following file for new operation results:
safe.xlsx
and the final address are:
safelist.txt
I would like to ask if you can take another look at whether the materials currently submitted are acceptable.
Thank you very much


Question regarding ClientScriptResource and ASCX controls

Hi,
I am in the process of trying to update our code base to .Net 4.6.1 and also update the Toolkit from 4.6 to 16.1 (I know, this is far from ideal). So far I have been able to get most controls to build and function correctly with the exception of around 6 ascx controls. The team that build these controls back in 2009-2010 used the ClientScriptResource tag along with the ScriptUserControl in the Toolkit to embed javascript files that handled all of the control's AJAX. I removed all references to the ScriptUserControl and the controls build but the embedded javascript files are no longer being loaded into the browser. All of the controls were setup as follows:
<Assembly: WebResource("ProjectName.OrderQuantityBehavior.js", "text/javascript")>  <ClientScriptResource("ProjectName.OrderQuantityBehavior", "ProjectName.OrderQuantityBehavior")> _ Partial Public Class OrderDatesAndQuantityControl
The javascript files are located in a subfolder where all of the controls are located, specifically Controls/App_LocalResources/Scripts. I have tried different paths, different namespaces, and moving files around and I cannot find anything that will load the JS correctly. The frustrating part is that I can't even get an error to throw. No console errors, no Visual Studio exceptions, nothing. Is this a simple issues of the paths needed changed or is there something else I need to add to get these javascript files back into the browser?

Hi @cshomo11,
Thank you for contacting us with such an interesting issue!
The ScriptUserControl, which is derived from the UserControl, was removed from the AJAX Control Toolkit in v15.1.
This means it is not affected by the control processing pipeline of the toolkit, despite you applied proper attributes to your custom control and embedded valid scripts in the assembly.
To return these controls into the toolkit flow, you need to derive them from the ScriptControlBase class.
Please refer to this article for more details: Creating a custom control.
If such a conversion is not possible, the only way to load these scripts is to make it explicitly.
For example, you can use the ClientScriptManager.RegisterClientScriptResource method to register required scripts or any other method that suit you needs.
Please don't hesitate to contact me if you need additional information regarding the upgrade process.

Mikhail,
Thanks for the speedy reply. I changed the ascx control’s inherited base class to inherit from ScriptControlBase instead of UserControl but now I am confronted with this error.
<EMAIL_ADDRESS>Neither ScriptControlBase or ExtenderControlBase inherit from UserControl.  I don’t know if there is anything else I can do with that or if I should just move on to the ClientScriptManager method you also recommended.
From: MikhailTymchukDX<EMAIL_ADDRESS>Sent: Tuesday, September 06, 2016 12:23 PM
To: DevExpress/AjaxControlToolkit
Cc: Chris Shomo; Mention
Subject: Re: [DevExpress/AjaxControlToolkit] Question regarding ClientScriptResource and ASCX controls (#216)
Hi @cshomo11https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_cshomo11&d=CwMFaQ&c=D35fws0esX4dbzGkMoSSSiyixYO2sfGUYyarAm1-S78&r=UogZ8n0HKmQt52D2AJyn2DVx-HESLJy4cY4ATr7uWsI&m=VdxKUA7U8M1HLHGbuUl_UHRBOLxGas-TCehNOM8IOkA&s=sap8B6nQFunHVCiz9rGMOnTiTu19GLOM34DeqL2li3w&e=,
Thank you for contacting us with such an interesting issue!
The ScriptUserControl, which is derived from the UserControl, was removed from the AJAX Control Toolkit in v15.1.
This means it is not affected by the control processing pipeline of the toolkit, despite you applied proper attributes to your custom control and embedded valid scripts in the assembly.
To return these controls into the toolkit flow, you need to derive them from the ScriptControlBasehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_DevExpress_AjaxControlToolkit_blob_master_AjaxControlToolkit_ExtenderBase_ScriptControlBase.cs&d=CwMFaQ&c=D35fws0esX4dbzGkMoSSSiyixYO2sfGUYyarAm1-S78&r=UogZ8n0HKmQt52D2AJyn2DVx-HESLJy4cY4ATr7uWsI&m=VdxKUA7U8M1HLHGbuUl_UHRBOLxGas-TCehNOM8IOkA&s=2lFnQc3T9KviAg5paUUdxkeJ-L1nvqHe_lK27shP_d0&e= class.
Please refer to this article for more details: Creating a custom controlhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_DevExpress_AjaxControlToolkit_wiki_Creating-2Da-2Dcustom-2Dcontrol&d=CwMFaQ&c=D35fws0esX4dbzGkMoSSSiyixYO2sfGUYyarAm1-S78&r=UogZ8n0HKmQt52D2AJyn2DVx-HESLJy4cY4ATr7uWsI&m=VdxKUA7U8M1HLHGbuUl_UHRBOLxGas-TCehNOM8IOkA&s=hDdzUCFcz3j68WaHKS851KLyhM10X4V4l_7zr6ybeao&e=.
If such a conversion is not possible, the only way to load these scripts is to make it explicitly.
For example, you can use the ClientScriptManager.RegisterClientScriptResourcehttps://urldefense.proofpoint.com/v2/url?u=https-3A__msdn.microsoft.com_en-2Dus_library_system.web.ui.clientscriptmanager.registerclientscriptresource-28v-3Dvs.110-29.aspx&d=CwMFaQ&c=D35fws0esX4dbzGkMoSSSiyixYO2sfGUYyarAm1-S78&r=UogZ8n0HKmQt52D2AJyn2DVx-HESLJy4cY4ATr7uWsI&m=VdxKUA7U8M1HLHGbuUl_UHRBOLxGas-TCehNOM8IOkA&s=rnuXMgUWC7pb3FaAuTP87rl1SfrdSI8WcSXpN_2qNiM&e= method to register required scripts or any other method that suit you needs.
Please don't hesitate to contact me if you need additional information regarding the upgrade process.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_DevExpress_AjaxControlToolkit_issues_216-23issuecomment-2D245006329&d=CwMFaQ&c=D35fws0esX4dbzGkMoSSSiyixYO2sfGUYyarAm1-S78&r=UogZ8n0HKmQt52D2AJyn2DVx-HESLJy4cY4ATr7uWsI&m=VdxKUA7U8M1HLHGbuUl_UHRBOLxGas-TCehNOM8IOkA&s=Whqo5tkXaG3YzRS7dB-76EkMX_5Mwju7cOvFt6j2g6Y&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AGcE-5F8ve6otn0taEtIHfKwuocVkwdK8aks5qnZNmgaJpZM4J18OY&d=CwMFaQ&c=D35fws0esX4dbzGkMoSSSiyixYO2sfGUYyarAm1-S78&r=UogZ8n0HKmQt52D2AJyn2DVx-HESLJy4cY4ATr7uWsI&m=VdxKUA7U8M1HLHGbuUl_UHRBOLxGas-TCehNOM8IOkA&s=WhSun_iZ6JXBTR29MugFqqP4mZRCipzfNFObaVLg2wY&e=.

[cid:imagecb7ab1.JPG@0495be46.4f8ae1d4]http://        Chris Shomo, Developer
<EMAIL_ADDRESS>www.sapphire-health.comhttp://www.sapphire-health.com
<EMAIL_ADDRESS>       724.349.1111 x1124
877.532.2345 x1124<EMAIL_ADDRESS>       724.349.2064<EMAIL_ADDRESS>       654 Kolter Dr. Indiana, Pennsylvania 15701
This communication may contain information that is proprietary, confidential, or exempt from disclosure. If you are not the intended recipient, please note that any other dissemination, distribution, use or copying of this communication is strictly prohibited. Anyone who receives this message in error should notify the sender immediately by telephone or by return e-mail and delete it from his or her computer.

@cshomo11
I don't see the image. Would you please submit it again?

Sorry, I sent it as an attachment this time.
From: MikhailTymchukDX<EMAIL_ADDRESS>Sent: Wednesday, September 07, 2016 3:06 AM
To: DevExpress/AjaxControlToolkit
Cc: Chris Shomo; Mention
Subject: Re: [DevExpress/AjaxControlToolkit] Question regarding ClientScriptResource and ASCX controls (#216)
@cshomo11https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_cshomo11&d=CwMCaQ&c=D35fws0esX4dbzGkMoSSSiyixYO2sfGUYyarAm1-S78&r=UogZ8n0HKmQt52D2AJyn2DVx-HESLJy4cY4ATr7uWsI&m=lfqHz1HDVgDEIGoc_91Ns1D1OT4NjP_pdRg2OCr6Zog&s=iYOA7lgUMlDYXNRgVDgbCzeqcEUIGupJsn_lBvNRiJo&e=
I don't see the image. Would you please submit it again?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_DevExpress_AjaxControlToolkit_issues_216-23issuecomment-2D245193863&d=CwMCaQ&c=D35fws0esX4dbzGkMoSSSiyixYO2sfGUYyarAm1-S78&r=UogZ8n0HKmQt52D2AJyn2DVx-HESLJy4cY4ATr7uWsI&m=lfqHz1HDVgDEIGoc_91Ns1D1OT4NjP_pdRg2OCr6Zog&s=bqmym_U1O8n6MD-R0U3Fv_b6T8q0WDyvxhciiNKULUQ&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AGcE-5Fxu5LztMzig6UquSrdNBQoien7hJks5qnmJzgaJpZM4J18OY&d=CwMCaQ&c=D35fws0esX4dbzGkMoSSSiyixYO2sfGUYyarAm1-S78&r=UogZ8n0HKmQt52D2AJyn2DVx-HESLJy4cY4ATr7uWsI&m=lfqHz1HDVgDEIGoc_91Ns1D1OT4NjP_pdRg2OCr6Zog&s=jER4qkzcQQyMUGH5asRebe9f-zBWHM3D9btvkwZYKlk&e=.

[cid:imageba6bbe.JPG@98f83bc9.46904316]http://        Chris Shomo, Developer
<EMAIL_ADDRESS>www.sapphire-health.comhttp://www.sapphire-health.com
<EMAIL_ADDRESS>       724.349.1111 x1124
877.532.2345 x1124<EMAIL_ADDRESS>       724.349.2064<EMAIL_ADDRESS>       654 Kolter Dr. Indiana, Pennsylvania 15701
This communication may contain information that is proprietary, confidential, or exempt from disclosure. If you are not the intended recipient, please note that any other dissemination, distribution, use or copying of this communication is strictly prohibited. Anyone who receives this message in error should notify the sender immediately by telephone or by return e-mail and delete it from his or her computer.

Nope, still no image.
It seems that GitHub email relay can not put mail attachments to the web site posts.
Would you please use the site to upload the image or provide a public link to that image?

Ah okay, here is a link to the error image. https://postimg.org/image/osrjkdkzz/
From: MikhailTymchukDX<EMAIL_ADDRESS>Sent: Wednesday, September 07, 2016 8:08 AM
To: DevExpress/AjaxControlToolkit
Cc: Chris Shomo; Mention
Subject: Re: [DevExpress/AjaxControlToolkit] Question regarding ClientScriptResource and ASCX controls (#216)
Nope, still no image.
It seems that GitHub email relay can not put mail attachments to the web site posts.
Would you please use the site to upload the image or provide a public link to that image?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_DevExpress_AjaxControlToolkit_issues_216-23issuecomment-2D245260249&d=CwMFaQ&c=D35fws0esX4dbzGkMoSSSiyixYO2sfGUYyarAm1-S78&r=UogZ8n0HKmQt52D2AJyn2DVx-HESLJy4cY4ATr7uWsI&m=Rp1QQU-2X06GL0V200XBq62n9CaFJpYeid3o260oBRE&s=54Dw8oG_vxZok8EhGhEKPJ7zbFbmrqZ-eRQTJ7AIDhY&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AGcE-5F1CBgM1Xwud4kroDLJmPsSslaUYaks5qnqk8gaJpZM4J18OY&d=CwMFaQ&c=D35fws0esX4dbzGkMoSSSiyixYO2sfGUYyarAm1-S78&r=UogZ8n0HKmQt52D2AJyn2DVx-HESLJy4cY4ATr7uWsI&m=Rp1QQU-2X06GL0V200XBq62n9CaFJpYeid3o260oBRE&s=myNmlmS8769JeJl55fwv4Oskzopblbg_Lnv9qaV0MTo&e=.

[cid:imageed2401.JPG@6f77d8ff.4c87cd28]http://        Chris Shomo, Developer
<EMAIL_ADDRESS>www.sapphire-health.comhttp://www.sapphire-health.com
<EMAIL_ADDRESS>       724.349.1111 x1124
877.532.2345 x1124<EMAIL_ADDRESS>       724.349.2064<EMAIL_ADDRESS>       654 Kolter Dr. Indiana, Pennsylvania 15701
This communication may contain information that is proprietary, confidential, or exempt from disclosure. If you are not the intended recipient, please note that any other dissemination, distribution, use or copying of this communication is strictly prohibited. Anyone who receives this message in error should notify the sender immediately by telephone or by return e-mail and delete it from his or her computer.

Thank you for the image.
As the error message states, you cannot use an arbitrary class with the @Control directive, because it implies that the class is derived from the System.Web.UI.UserControl class.
Converting UserControl to ScriptControlBase requires changing the architecture of the application.
It's currently difficult to guess how complex your control is, so it would be nice if you provide a code sample that illustrates your controls' structure.

This control is pretty complex. It has several date fields that all interact with one another and also complies an order quantity amount based on the days selected. Between this and the 4 or 5 other controls built this way, I don't know if we would currently have the time to change the architecture. I will have to try the other method you described yesterday using the RegisterControlScriptResource and see if that might help. Thank you for your help!


Inline media queries with

Hello,
First to mention, I am using mjml 3.3.3.
Is your feature request related to a problem? Please describe.
I am trying to inline all the styling by using  tags but the media queries do not get inlined.
Describe the solution you'd like
Is there a way to inline the media queries using ?

Nope, you can't add media queries on style HTML attribute so there's no way to do so.


Prototype Date Filter

Black Rock City is our test case:
https://openhistoricalmap.github.io/openhistoricaltiles/dateissues/#15.00/40.77470/-119.21600/
This should work for filters that can separate 2008 and 2009.
Allow user to select start_date and end_date.

Someday a slider, but for now could be a basic date-picker.
Or if single-day granularity is an issue, it could also be a Year Picker that doesn't allow closer resolution than a whole year *and appends -01-01 to start and -12-31 to end

I'm still a little foggy on how exactly these filters work in MBGL. So there might be discussion needed and expansion of this into multiple issues.

I have a working prototype up, and it's pretty cool:
https://openhistoricalmap.github.io/openhistoricaltiles/datefilter/#14.16/40.77635/-119.21658/
There are two clear date periods where all content fits:

2009-08-31 to 2009-09-07
2008-08-25 to 2008-09-01

Still some refinements I'd like to make to the UI:

[ ] datepicker widget; I have one in code but commented-out cuz it blocks the ability to type into the date box, and manually clicking the < button 120 times to go 10 years is tedious
[ ] check that start date <= end date
[ ] modify hash control, to include date range in the URL string
[ ] modify startup, to read date ranges from URL string

The URL has now uses a date component as well:
http://localhost:9000/#14.16/40.77626/-119.21650/2008-01-01,2008-12-31/
http://localhost:9000/#14.16/40.77643/-119.21527/2009-01-01,2009-12-31/
This means that the prior URL which lacks a date, will no longer zoom to the region as it is now missing required parameters.

Quoting @jeffreyameyer "will this have any impacts on other URL-based methods for accessing tiles?"
No; the URL of individual PBF tiles has not changed in any way. The URL params are provided so the application may configure itself e.g. pan and zoom the map, enable or disable some controls or UI elements, etc. and is not at all related to the URLs used to fetch vector tile data.

muy bueno!
On Tue, Sep 4, 2018 at 3:35 PM, Greg Allensworth<EMAIL_ADDRESS>wrote:

Quoting @jeffreyameyer https://github.com/jeffreyameyer "will this have
any impacts on other URL-based methods for accessing tiles?"
No; the URL of individual PBF tiles has not changed in any way. The URL
params are provided so the application may configure itself e.g. pan and
zoom the map, enable or disable some controls or UI elements, etc. and is
not at all related to the URLs used to fetch vector tile data.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/OpenHistoricalMap/openhistoricaltiles/issues/20#issuecomment-418539845,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABbOEu7dtgLK-uUAbDP2JpXIUel7xl9lks5uXwBLgaJpZM4WUWYW
.

--
Jeff Meyer
206-676-2347
osm: Open Historical Map (OHM)
http://wiki.openstreetmap.org/wiki/Open_Historical_Map / my OSM user page
http://www.openstreetmap.org/user/jeffmeyer
t: @OpenHistMap


SAA-1388 adding support for changing between paid and unpaid activities (only when no allocations present).

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

Comparison is base (f483f19) 86.72% compared to head (cd25381) 86.70%.

Files
Patch %
Lines

...activitiesmanagementapi/service/ActivityService.kt
70.00%
1 Missing and 2 partials :warning:

...ps/hmppsactivitiesmanagementapi/entity/Activity.kt
83.33%
0 Missing and 1 partial :warning:

...nagementapi/model/request/ActivityUpdateRequest.kt
75.00%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #703      +/-   ##
============================================
- Coverage     86.72%   86.70%   -0.02%
- Complexity     3418     3428      +10
============================================
  Files           356      356
  Lines         11680    11690      +10
  Branches        958      961       +3
============================================
+ Hits          10129    10136       +7
  Misses         1095     1095
- Partials        456      459       +3

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


Investigate rendering alternatives

Description
Rendering is currently implemented using Glium. I picked this library initially because it was the only one I was familiar with.
My main concerns with it are that it looks like WASM is not supported (which we do want), and that compile times may be excessively long for what we need (we only need a handful of OpenGL functions).
Possible alternatives

glow: https://github.com/grovesNL/glow

pixels: https://github.com/parasyte/pixels
It looks like WebGL/wasm support is WIP but it might be ready for the things we need

Raw calls to OpenGL (look into https://crates.io/crates/gl_generator)

I have to mention here that changing crates could introduce some problems for old intel graphics cards.
Not sure what exactly causes it but it's a known issue in Godot engine where people using GLES3 and 3d without lights with intel hd 620 causes screen to flash rapidly. And it's a very common old card.
And more relevant is that Macroquad using it's own graphics library has the same damn issue. It isn't even related to 3d or lighting in this case, I know this because I happen to have a laptop with intel hd 620. Literally just having a non black background or a few other colors already causes the flashing which makes it completely unusable. However building to wasm or changing screen dimensions circumvents this problem?
It's not the fault of the graphics libraries, it may be possible for Macroquad to make it work in these edge cases but I've never looked that deep into it. I just think this is important to mention because using this project is very fitting for low end devices.
Here's a link if you like flashing lights in your face: https://github.com/not-fl3/macroquad/issues/520
TLDR: OpenGL drivers are broken on old cards and never got fixed, they mostly work though. For me the intel hd 620 on the current setup works but that could stop working if you add different OpenGL features I think. I believe if you use Vulkan it's supposed to always work on anything that supports it, which is almost everything these days.
I'm not saying you shouldn't try an alternative, but it's important to be aware of this. I'd be willing to test it out if you do change crates. Not sure how glow compares to glium but pixels uses wgpu so it supports things other than OpenGL which is good. I don't know what part about OpenGL causes the flashing so don't take this too literally do what you want.
Also I see your recent commit mentions wasm, so is it supported?

This is a pretty stale issue, I stopped using glium in https://github.com/jjant/runty8/pull/28 in favour of glow for wasm support. pixels or wgpu are interesting alternatives to try, but I'm not sure if it's currently worth it to spend time on that, glow seems to work well enough, and the compile times are okay (and tbh I doubt they'll be better with the other crates) which is the main thing I was concerned about IIRC.

Oh ok, in that case glow seems to work well on this bad driver. I've not had any issues so pixels doesn't seem needed, you could close this.

I only mentioned serve because it's an easy to set up local server but it shouldn't matter what you using for serving those file.
I think yours might have failed because you had too many files in the deployment? I've configured GH pages to use the /docs directory in this branch, moving the generated files from the build script and it deployed successfully here.

Btw, it's a cool idea to have some games deployed on push to master. Ideally I would like to not need to have these files commited in the repo (i.e, have a GH action run the build_script and deploy those files).

Closed as stale/not worth diving into right now.

I only mentioned serve because it's an easy to set up local server but it shouldn't matter what you using for serving those file.
I think yours might have failed because you had too many files in the deployment? I've configured GH pages to use the /docs directory in this branch, moving the generated files from the build script and it deployed successfully here.

You're right after putting the files in a directory it started working, I haven't had that problem before.
Also your github pages is pointing to a custom domain that isn't loading: https://github.com/jjant/runty8/deployments


questions about LLM2CLIP finetune

when LLM2CLIP finetue, do you try unfreeze the LLM gradients and ViT model simultaneously，do you think this method may generate better results？

We have tried using LoRA to fine-tune the gradients of the LLM, and it does lead to a slight performance improvement, but not a substantial one. Perhaps more data is needed to fully unlock its potential. It’s also possible that the distribution of image captions might disrupt the original capabilities of the LLM. Therefore, I believe this requires some new design efforts. We will disclose more related experiments in our next version of the work. If you have tried similar approaches, we would be happy to exchange ideas and share experiences.


Analysis Services Driver

Provide an interface to SQL Server Analysis Services.
Work Item Details
Original CodePlex Issue: Issue 16555
Status: Proposed
Reason Closed:  Unassigned
Assigned to:    Unassigned
Reported on:    Feb 26, 2010 at 6:27 AM
Reported by:    MitchMcBride
Updated on: Mar 8 at 11:04 AM
Updated by: miguelajh

Closing as it is out of scope for now.


Use regex.lastIndex

Use regex.lastIndex instead of calculating it from the start index and length.

Thanks for the PR.  I didn't know about lastIndex.


ARROW-1708: [JS] Fix linter error

@trxcllnt @TheNeuralBit Can you have a look why this build fails with
npm ERR! code EINTEGRITY
npm ERR! sha1-enz1ER1zdrN2znRhE34bA5MD8eo= integrity checksum failed when using sha1: wanted sha1-enz1ER1zdrN2znRhE34bA5MD8eo= but got sha1-KR8EDnOp3PO/NrKqKBg0RjQrnA4=. (716484 bytes)


[match] add support for App Store Connect API Key

Motivation and Context
App Store Connect API is the best API ❤ And last big step to get match fully working with App Store Connect API
Description

Added api_key and api_key_path options to match

Examples
1. New action
lane :release do
  api_key = app_store_connect_api_key(
    key_id: "D383SF739",
    issuer_id: "6053b7fe-68a8-4acb-89be-165aa6465141",
    key_filepath: "./D383SF739.p8",
    duration: 1200, # optional
    in_house: false, # optional but may be required if using match/sigh
  )

  match( api_key: api_key )
end

2. New file format
{
  "key_id": "D383SF739",
  "issuer_id": "6053b7fe-68a8-4acb-89be-165aa6465141",
  "key": "-----BEGIN PRIVATE KEY-----\nMIGTAgEAMBMGByqGSM49AgEGCCqGSM49AwEHBHknlhdlYdLu\n-----END PRIVATE KEY-----",
  "duration": 1200, # optional
  "in_house": false, # optional but may be required if using match/sigh,
  "portal_team_id": "D1839F83", # optional but may be required if using match/sigh,
}

lane :release do
  match( api_key_path: "fastlane/me.json" )
end

Testing Steps
Update Gemfile and run bundle install, bundle update fastlane, or bundle update
gem "fastlane", :git => "https://github.com/fastlane/fastlane.git", :branch => "joshdholtz-match-app-store-connect-api"

I got Unresolved conflict between options: 'api_key' and 'username' what I'm missing.

I got Unresolved conflict between options: 'api_key' and 'username' what I'm missing.

I think these 2 keys are mutually exclusive now. If you provide the api_key, you don't need to provide the username (actually we made it so that you shouldn't provide it, because it'd be ignored anyway)
Can you simply remove the username parameter and see if it works? :)

@PH9 @rogerluan Ahhhhh yeah yeah yeah, I can kind of see how that conflict might cause an issue since :username is also picking stuff up from FASTLANE_USER and DELIVER_USER 😬 It probably is best to remove these conflicts!

Guys just wanted to say you're amazing!! This was the last bit I needed to get my CI sorted out, thank you!


why do loaders need to be in context?

this is not such an obvious thing when trying to use the lib, and it becomes difficult to use it
suggestion:

use the direct loader without having to add it in the context
create a required parameter in createLoader to show where to consume the loader

can you give examples about your idea?

Suggestion 1,
https://github.com/entria/graphql-mongo-helpers/blob/master/src/createLoader.ts#L80
context.dataloaders[loaderName]
here it's get from the context, instead it's get direct of createLoader function internally
Suggestion 2,
createLoader({
  name: 'UserLoader',
  getLoader: (ctx) => ctx.userLoader; // here it is optional for the developer to choose where to get it.
})

on second thought, maybe the first suggestion is not so valid, because it creates an instance globally and not for request

i didn't understand the need of context loaders, maybe how it's currently is the best way

I do like your second suggestion, feel free to implement it
add tests to avoid regressions, and keep the old default behavior


Textbox failed display with chinese on Linux

Describe the bug
Textbox with chinese will be garbled on Linux enviroment, it works fine with textblock.
To Reproduce

Expected behavior
Textbox can display chinese successfully on linux
Screenshots
If applicable, add screenshots to help explain your problem.

Duplicate of #4859

Workaround:

You need to use a font that has Chinese characters. https://github.com/anthonyfok/fonts-wqy-microhei is a good one
WenQuanYiMicroHei-01.ttf.zip
Place it into Assets, add as AvaloniaResource and add something like
<Style Selector="TextBlock">
   <Setter Property="FontFamily" Value="avares://YourAssemblyName/Assets/Fonts#WenQuanYi Micro Hei" />
</Style>

to your App.xaml after the theme

Workaround:

You need to use a font that has Chinese characters. https://github.com/anthonyfok/fonts-wqy-microhei is a good one
WenQuanYiMicroHei-01.ttf.zip
Place it into Assets, add as AvaloniaResource and add something like
<Style Selector="TextBlock">
   <Setter Property="FontFamily" Value="avares://YourAssemblyName/Assets/Fonts#WenQuanYi Micro Hei" />
</Style>

to your App.xaml after the theme

Thanks, it works fine.


Test failed: “We don't know what to do with this node type. We were previously a Statement but we can't fit in here?”

Do you want to request a feature or report a bug?
What is the current behavior?
Test this
Error message:
><EMAIL_ADDRESS>test /Users/huaji/Projects/react-typescript-kits
> jest --config jest.json

 FAIL  src/a.test.js
  ● Test suite failed to run

    /Users/huaji/Projects/react-typescript-kits/src/a.js: We don't know what to do with this node type. We were previously a Statement but we can't fit in here?

      at NodePath.insertBefore (node_modules/babel-traverse/lib/path/modification.js:61:13)
      at VisitState.insertCounter (node_modules/istanbul-lib-instrument/dist/visitor.js:197:22)
      at VisitState.insertStatementCounter (node_modules/istanbul-lib-instrument/dist/visitor.js:224:18)
      at VisitState.coverStatement (node_modules/istanbul-lib-instrument/dist/visitor.js:340:10)
      at node_modules/istanbul-lib-instrument/dist/visitor.js:327:15
          at Array.forEach (<anonymous>)
      at VisitState.wrappedEntry (node_modules/istanbul-lib-instrument/dist/visitor.js:326:15)
      at NodePath._call (node_modules/babel-traverse/lib/path/context.js:76:18)
      at NodePath.call (node_modules/babel-traverse/lib/path/context.js:48:17)
      at NodePath.visit (node_modules/babel-traverse/lib/path/context.js:105:12)

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        0.802s
Ran all test suites.
----------|----------|----------|----------|----------|----------------|
File      |  % Stmts | % Branch |  % Funcs |  % Lines |Uncovered Lines |
----------|----------|----------|----------|----------|----------------|
All files |        0 |        0 |        0 |        0 |                |
 a.js     |        0 |        0 |        0 |        0 |            1,4 |
----------|----------|----------|----------|----------|----------------|
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>test: `jest --config jest.json`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/huaji/.npm/_logs/2017-10-29T09_49_44_256Z-debug.log

I fixed this with:
https://github.com/EYHN/react-typescript-kits/commit/3c69bb8b4a98b9796b8bd610f8dbcd1beb63eb59
If the current behavior is a bug, please provide the steps to reproduce and either a repl.it demo through https://repl.it/languages/jest or a minimal repository on GitHub that we can yarn install and yarn test.
https://github.com/EYHN/react-typescript-kits/tree/bugtest
Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.
Jest 21.2.1
node 8.5.0
yarn 1.0.2
macOS 10.13

This seems to be one of your babel plugins (that may not work well with other babel plugins, like code coverage) , but it isn't coming from Jest.

Thank you, but I still do not know how to solve this problem.
In the simplest configuration it still does not work well( babel and code coverage ).
.babelrc
{
  "presets": [
    "es2015"
  ],
  "plugins": [
  ]
}

jest.json
{
  "testRegex": "a.test.js",
  "moduleFileExtensions": [
    "js",
    "jsx"
  ],
  "browser": true,
  "collectCoverage": true,
  "collectCoverageFrom" : ["src/**/*.{js,jsx}", "!**/node_modules/**"],
  "coverageDirectory": "coverage",
  "moduleDirectories": ["node_modules", "./src"]
}