HBASE-23305: Master based registry implementation

Implements a master based registry for clients.

Supports hedged RPCs (fan out configured via configs).
Parameterized existing client tests to run with multiple
registry combinations.
Added unit-test coverage for the new registry implenenation.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 8 new or modified test files.

_ HBASE-18095/client-locate-meta-no-zookeeper Compile Tests _

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

+1 :green_heart:
mvninstall
5m 52s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
compile
1m 44s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
checkstyle
2m 34s
HBASE-18095/client-locate-meta-no-zookeeper passed

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

+1 :green_heart:
javadoc
1m 19s
HBASE-18095/client-locate-meta-no-zookeeper passed

+0 :ok:
spotbugs
4m 48s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
6m 42s
HBASE-18095/client-locate-meta-no-zookeeper passed

_ Patch Compile Tests _

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

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

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

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

-1 :x:
checkstyle
1m 33s
hbase-server: The patch generated 2 new + 224 unchanged - 45 fixed = 226 total (was 269)

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

-1 :x:
shadedjars
2m 42s
patch has 10 errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
17m 26s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

-1 :x:
javadoc
0m 21s
hbase-client generated 2 new + 2 unchanged - 0 fixed = 4 total (was 2)

-1 :x:
findbugs
1m 18s
hbase-client generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

_ Other Tests _

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

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

-1 :x:
unit
205m 58s
hbase-server in the patch failed.

-1 :x:
asflicense
1m 26s
The patch generated 2 ASF License warnings.

283m 25s

Reason
Tests

FindBugs
module:hbase-client

Should org.apache.hadoop.hbase.client.MasterRegistry$BatchRpcCtx be a static inner class?  At MasterRegistry.java:inner class?  At MasterRegistry.java:[lines 100-145]

Failed junit tests
hadoop.hbase.client.TestAsyncRegionAdminApi2

hadoop.hbase.client.TestAsyncTableRegionReplicasScan

hadoop.hbase.client.TestScannersFromClientSide

hadoop.hbase.client.TestMetaWithReplicas

hadoop.hbase.client.TestAsyncResultScannerCursor

hadoop.hbase.replication.TestReplicationDisableInactivePeer

hadoop.hbase.client.TestZKAsyncRegistry

hadoop.hbase.client.TestCIPutOperationTimeout

hadoop.hbase.client.TestCloneSnapshotFromClientAfterSplittingRegion

hadoop.hbase.client.TestMultipleTimestamps

hadoop.hbase.client.TestAdmin3

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/1/artifact/out/Dockerfile

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

JIRA Issue
HBASE-23305

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 55f8f10fe76f 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-954/out/precommit/personality/provided.sh

git revision
HBASE-18095/client-locate-meta-no-zookeeper / e41b46cc28

Default Java
1.8.0_181

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/1/artifact/out/diff-checkstyle-hbase-server.txt

shadedjars
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/1/artifact/out/patch-shadedjars.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/1/artifact/out/diff-javadoc-javadoc-hbase-client.txt

findbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/1/artifact/out/new-findbugs-hbase-client.html

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/1/artifact/out/patch-unit-hbase-server.txt

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

asflicense
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/1/artifact/out/patch-asflicense-problems.txt

Max. process+thread count
9918 (vs. ulimit of 10000)

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

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

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 8 new or modified test files.

_ HBASE-18095/client-locate-meta-no-zookeeper Compile Tests _

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

+1 :green_heart:
mvninstall
5m 48s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
compile
1m 45s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
checkstyle
2m 32s
HBASE-18095/client-locate-meta-no-zookeeper passed

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

+1 :green_heart:
javadoc
1m 16s
HBASE-18095/client-locate-meta-no-zookeeper passed

+0 :ok:
spotbugs
4m 46s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
6m 39s
HBASE-18095/client-locate-meta-no-zookeeper passed

_ Patch Compile Tests _

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

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

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

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

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

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

+1 :green_heart:
checkstyle
1m 32s
hbase-server: The patch generated 0 new + 223 unchanged - 46 fixed = 223 total (was 269)

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

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

+1 :green_heart:
hadoopcheck
17m 29s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

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

-1 :x:
findbugs
1m 18s
hbase-client generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

_ Other Tests _

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

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

-1 :x:
unit
267m 40s
hbase-server in the patch failed.

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

346m 53s

Reason
Tests

FindBugs
module:hbase-client

Should org.apache.hadoop.hbase.client.MasterRegistry$BatchRpcCtx be a static inner class?  At MasterRegistry.java:inner class?  At MasterRegistry.java:[lines 117-162]

Failed junit tests
hadoop.hbase.client.TestSplitOrMergeStatus

hadoop.hbase.client.TestFromClientSideWithCoprocessor

hadoop.hbase.master.TestMasterShutdown

hadoop.hbase.client.TestScannersFromClientSide

hadoop.hbase.client.TestMobSnapshotCloneIndependence

hadoop.hbase.client.TestCIPutOperationTimeout

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/2/artifact/out/Dockerfile

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

JIRA Issue
HBASE-23305

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 2c688ac1523d 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-954/out/precommit/personality/provided.sh

git revision
HBASE-18095/client-locate-meta-no-zookeeper / e41b46cc28

Default Java
1.8.0_181

findbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/2/artifact/out/new-findbugs-hbase-client.html

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/2/artifact/out/patch-unit-hbase-server.txt

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

Max. process+thread count
9917 (vs. ulimit of 10000)

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

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

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 10 new or modified test files.

_ HBASE-18095/client-locate-meta-no-zookeeper Compile Tests _

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

+1 :green_heart:
mvninstall
5m 17s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
compile
1m 47s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
checkstyle
2m 24s
HBASE-18095/client-locate-meta-no-zookeeper passed

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

+1 :green_heart:
javadoc
1m 22s
HBASE-18095/client-locate-meta-no-zookeeper passed

+0 :ok:
spotbugs
4m 22s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
6m 13s
HBASE-18095/client-locate-meta-no-zookeeper passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
checkstyle
0m 26s
hbase-common: The patch generated 0 new + 4 unchanged - 1 fixed = 4 total (was 5)

+1 :green_heart:
checkstyle
0m 32s
hbase-client: The patch generated 0 new + 3 unchanged - 6 fixed = 3 total (was 9)

-1 :x:
checkstyle
1m 23s
hbase-server: The patch generated 2 new + 227 unchanged - 46 fixed = 229 total (was 273)

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

-1 :x:
shadedjars
2m 28s
patch has 10 errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
15m 42s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

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

+1 :green_heart:
findbugs
6m 30s
the patch passed

_ Other Tests _

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

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

-1 :x:
unit
175m 37s
hbase-server in the patch failed.

-1 :x:
asflicense
1m 46s
The patch generated 1 ASF License warnings.

247m 22s

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestFromClientSide

hadoop.hbase.client.TestFromClientSideWithCoprocessor

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/3/artifact/out/Dockerfile

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

JIRA Issue
HBASE-23305

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

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

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-954/out/precommit/personality/provided.sh

git revision
HBASE-18095/client-locate-meta-no-zookeeper / e41b46cc28

Default Java
1.8.0_181

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/3/artifact/out/diff-checkstyle-hbase-server.txt

shadedjars
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/3/artifact/out/patch-shadedjars.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/3/artifact/out/patch-unit-hbase-server.txt

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

asflicense
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/3/artifact/out/patch-asflicense-problems.txt

Max. process+thread count
9903 (vs. ulimit of 10000)

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

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

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 10 new or modified test files.

_ HBASE-18095/client-locate-meta-no-zookeeper Compile Tests _

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

+1 :green_heart:
mvninstall
5m 13s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
compile
1m 44s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
checkstyle
2m 24s
HBASE-18095/client-locate-meta-no-zookeeper passed

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

+1 :green_heart:
javadoc
1m 19s
HBASE-18095/client-locate-meta-no-zookeeper passed

+0 :ok:
spotbugs
4m 26s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
6m 18s
HBASE-18095/client-locate-meta-no-zookeeper passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
checkstyle
0m 26s
hbase-common: The patch generated 0 new + 4 unchanged - 1 fixed = 4 total (was 5)

+1 :green_heart:
checkstyle
0m 31s
hbase-client: The patch generated 0 new + 3 unchanged - 6 fixed = 3 total (was 9)

+1 :green_heart:
checkstyle
1m 24s
hbase-server: The patch generated 0 new + 227 unchanged - 46 fixed = 227 total (was 273)

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

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

+1 :green_heart:
hadoopcheck
15m 44s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

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

+1 :green_heart:
findbugs
6m 42s
the patch passed

_ Other Tests _

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

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

-1 :x:
unit
189m 42s
hbase-server in the patch failed.

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

264m  2s

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestFromClientSide

hadoop.hbase.client.TestScannersFromClientSide

hadoop.hbase.client.TestFromClientSideWithCoprocessor

hadoop.hbase.quotas.TestQuotaAdmin

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/4/artifact/out/Dockerfile

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

JIRA Issue
HBASE-23305

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

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

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-954/out/precommit/personality/provided.sh

git revision
HBASE-18095/client-locate-meta-no-zookeeper / e41b46cc28

Default Java
1.8.0_181

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/4/artifact/out/patch-unit-hbase-server.txt

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

Max. process+thread count
9909 (vs. ulimit of 10000)

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

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

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 10 new or modified test files.

_ HBASE-18095/client-locate-meta-no-zookeeper Compile Tests _

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

+1 :green_heart:
mvninstall
5m 53s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
compile
1m 43s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
checkstyle
2m 38s
HBASE-18095/client-locate-meta-no-zookeeper passed

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

+1 :green_heart:
javadoc
1m 17s
HBASE-18095/client-locate-meta-no-zookeeper passed

+0 :ok:
spotbugs
4m 43s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
6m 37s
HBASE-18095/client-locate-meta-no-zookeeper passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
checkstyle
0m 25s
hbase-common: The patch generated 0 new + 4 unchanged - 1 fixed = 4 total (was 5)

+1 :green_heart:
checkstyle
0m 35s
hbase-client: The patch generated 0 new + 3 unchanged - 6 fixed = 3 total (was 9)

+1 :green_heart:
checkstyle
1m 33s
hbase-server: The patch generated 0 new + 227 unchanged - 46 fixed = 227 total (was 273)

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

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

+1 :green_heart:
hadoopcheck
17m 21s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

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

+1 :green_heart:
findbugs
7m  3s
the patch passed

_ Other Tests _

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

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

-1 :x:
unit
271m 40s
hbase-server in the patch failed.

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

350m 55s

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestFromClientSideWithCoprocessor

hadoop.hbase.quotas.TestClusterScopeQuotaThrottle

hadoop.hbase.client.TestScannersFromClientSide

hadoop.hbase.client.TestFromClientSide

hadoop.hbase.regionserver.TestSplitTransactionOnCluster

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/5/artifact/out/Dockerfile

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

JIRA Issue
HBASE-23305

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux f3a8a8df9404 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-954/out/precommit/personality/provided.sh

git revision
HBASE-18095/client-locate-meta-no-zookeeper / e41b46cc28

Default Java
1.8.0_181

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/5/artifact/out/patch-unit-hbase-server.txt

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

Max. process+thread count
5491 (vs. ulimit of 10000)

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

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

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

Fixed all the test failures from the last run in the latest push. One of the fixes comes in as a separate PR to master https://github.com/apache/hbase/pull/963 . To pull that in, the current feature branch needs a rebase on master. Also, from the last test run, the thread usage has substantially dropped due to the test cleanup. I think this is in a good shape for 2nd round of review. Appreciate any feedback.

@saintstack / @apurtell Any thoughts on the new design? Happy to address any concerns. Thanks.

FYI, I rebased the feature branch onto the tip of master.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 31 new or modified test files.

_ HBASE-18095/client-locate-meta-no-zookeeper Compile Tests _

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

+1 :green_heart:
mvninstall
5m 50s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
compile
1m 45s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
checkstyle
2m 36s
HBASE-18095/client-locate-meta-no-zookeeper passed

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

+1 :green_heart:
javadoc
1m 24s
HBASE-18095/client-locate-meta-no-zookeeper passed

+0 :ok:
spotbugs
5m 17s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
7m 21s
HBASE-18095/client-locate-meta-no-zookeeper passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
checkstyle
0m 26s
hbase-common: The patch generated 0 new + 4 unchanged - 1 fixed = 4 total (was 5)

-1 :x:
checkstyle
0m 33s
hbase-client: The patch generated 2 new + 14 unchanged - 10 fixed = 16 total (was 24)

+1 :green_heart:
checkstyle
1m 31s
hbase-server: The patch generated 0 new + 226 unchanged - 48 fixed = 226 total (was 274)

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

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

+1 :green_heart:
hadoopcheck
17m 33s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

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

+1 :green_heart:
findbugs
7m 19s
the patch passed

_ Other Tests _

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

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

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

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

252m 59s

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestScannersFromClientSide

hadoop.hbase.client.TestFromClientSide

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/7/artifact/out/Dockerfile

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

JIRA Issue
HBASE-23305

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 265a7760b785 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-954/out/precommit/personality/provided.sh

git revision
HBASE-18095/client-locate-meta-no-zookeeper / dffa9be899

Default Java
1.8.0_181

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/7/artifact/out/diff-checkstyle-hbase-client.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/7/artifact/out/patch-unit-hbase-server.txt

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

Max. process+thread count
6669 (vs. ulimit of 10000)

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

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

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 31 new or modified test files.

_ HBASE-18095/client-locate-meta-no-zookeeper Compile Tests _

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

+1 :green_heart:
mvninstall
5m 59s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
compile
2m  3s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
checkstyle
2m 39s
HBASE-18095/client-locate-meta-no-zookeeper passed

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

+1 :green_heart:
javadoc
1m 18s
HBASE-18095/client-locate-meta-no-zookeeper passed

+0 :ok:
spotbugs
4m 43s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
6m 35s
HBASE-18095/client-locate-meta-no-zookeeper passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
checkstyle
0m 26s
hbase-common: The patch generated 0 new + 4 unchanged - 1 fixed = 4 total (was 5)

-1 :x:
checkstyle
0m 33s
hbase-client: The patch generated 2 new + 14 unchanged - 10 fixed = 16 total (was 24)

+1 :green_heart:
checkstyle
1m 34s
hbase-server: The patch generated 0 new + 224 unchanged - 50 fixed = 224 total (was 274)

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

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

+1 :green_heart:
hadoopcheck
17m 34s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

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

+1 :green_heart:
findbugs
7m 33s
the patch passed

_ Other Tests _

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

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

-1 :x:
unit
166m  9s
hbase-server in the patch failed.

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

247m 11s

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestFromClientSideWithCoprocessor

hadoop.hbase.client.TestFromClientSide

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/8/artifact/out/Dockerfile

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

JIRA Issue
HBASE-23305

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 1bcc84663300 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-954/out/precommit/personality/provided.sh

git revision
HBASE-18095/client-locate-meta-no-zookeeper / dffa9be899

Default Java
1.8.0_181

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/8/artifact/out/diff-checkstyle-hbase-client.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/8/artifact/out/patch-unit-hbase-server.txt

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

Max. process+thread count
6395 (vs. ulimit of 10000)

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

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

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

Fixed the check style issues and rebased on the latest tip of the feature branch (and squashed all the commits). Test failures seem to be flakes and run fine for me locally. I think this is good to go for another round of review.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 10 new or modified test files.

_ HBASE-18095/client-locate-meta-no-zookeeper Compile Tests _

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

+1 :green_heart:
mvninstall
6m  1s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
compile
1m 50s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
checkstyle
2m 37s
HBASE-18095/client-locate-meta-no-zookeeper passed

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

+1 :green_heart:
javadoc
1m 20s
HBASE-18095/client-locate-meta-no-zookeeper passed

+0 :ok:
spotbugs
5m 22s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
7m 22s
HBASE-18095/client-locate-meta-no-zookeeper passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
checkstyle
0m 27s
hbase-common: The patch generated 0 new + 4 unchanged - 1 fixed = 4 total (was 5)

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

+1 :green_heart:
checkstyle
1m 36s
hbase-server: The patch generated 0 new + 223 unchanged - 50 fixed = 223 total (was 273)

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

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

+1 :green_heart:
hadoopcheck
17m 59s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

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

-1 :x:
findbugs
11m 30s
hbase-server in the patch failed.

_ Other Tests _

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

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

-1 :x:
unit
193m 28s
hbase-server in the patch failed.

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

284m 46s

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestFromClientSideWithCoprocessor

hadoop.hbase.client.TestFromClientSide

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/9/artifact/out/Dockerfile

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

JIRA Issue
HBASE-23305

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux eff02e1348bf 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-954/out/precommit/personality/provided.sh

git revision
HBASE-18095/client-locate-meta-no-zookeeper / d016cd9962

Default Java
1.8.0_181

findbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/9/artifact/out/patch-findbugs-hbase-server.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/9/artifact/out/patch-unit-hbase-server.txt

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

Max. process+thread count
6672 (vs. ulimit of 10000)

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

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

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

Something broke fund bugs on master perhaps?
[INFO] --- findbugs-maven-plugin:3.0.4:findbugs (default-cli) @ hbase-server ---
[INFO] Fork Value is true
     [java] SLF4J: No SLF4J providers were found.
     [java] SLF4J: Defaulting to no-operation (NOP) logger implementation
     [java] SLF4J: See http://www.slf4j.org/codes.html#noProviders for further details.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 10 new or modified test files.

_ HBASE-18095/client-locate-meta-no-zookeeper Compile Tests _

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

+1 :green_heart:
mvninstall
7m 29s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
compile
2m  9s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
checkstyle
2m 55s
HBASE-18095/client-locate-meta-no-zookeeper passed

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

+1 :green_heart:
javadoc
1m 19s
HBASE-18095/client-locate-meta-no-zookeeper passed

+0 :ok:
spotbugs
5m  2s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
6m 56s
HBASE-18095/client-locate-meta-no-zookeeper passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
checkstyle
0m 26s
hbase-common: The patch generated 0 new + 4 unchanged - 1 fixed = 4 total (was 5)

+1 :green_heart:
checkstyle
0m 33s
hbase-client: The patch generated 0 new + 0 unchanged - 12 fixed = 0 total (was 12)

+1 :green_heart:
checkstyle
1m 30s
hbase-server: The patch generated 0 new + 223 unchanged - 50 fixed = 223 total (was 273)

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

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

+1 :green_heart:
hadoopcheck
17m 25s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

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

+1 :green_heart:
findbugs
7m 14s
the patch passed

_ Other Tests _

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

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

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

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

251m  4s

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestScannersFromClientSide

hadoop.hbase.client.TestFromClientSideWithCoprocessor

hadoop.hbase.client.TestFromClientSide

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/10/artifact/out/Dockerfile

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

JIRA Issue
HBASE-23305

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 209b7b181d42 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-954/out/precommit/personality/provided.sh

git revision
HBASE-18095/client-locate-meta-no-zookeeper / d016cd9962

Default Java
1.8.0_181

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/10/artifact/out/patch-unit-hbase-server.txt

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

Max. process+thread count
4757 (vs. ulimit of 10000)

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

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

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

Surprising.
[ERROR] org.apache.hadoop.hbase.client.TestFromClientSideWithCoprocessor.testCheckAndDeleteWithCompareOp[0]  Time elapsed: 0.142 s  <<< ERROR!
java.lang.OutOfMemoryError: Java heap space
	at org.apache.hadoop.hbase.client.TestFromClientSideWithCoprocessor.<init>(TestFromClientSideWithCoprocessor.java:50)

[ERROR] org.apache.hadoop.hbase.client.TestFromClientSideWithCoprocessor.testCheckAndDeleteWithCompareOp[0]  Time elapsed: 0.142 s  <<< ERROR!

@ndimiduk I think I figured out the flaky test problem. I pushed another commit that deflakes the test and all of these TestClient* now pass in my IDE too. To summarize, JUnit parameterization (with test class hiearchy) is a PITA. Without my last commit, every unit test of every parameterized test run was reseting the cluster state. JUnit does not yet provide of a way to execute a hook at the end of each parameterized test run. So, I hacked my way around it. I'm hoping it should pass now.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 10 new or modified test files.

_ HBASE-18095/client-locate-meta-no-zookeeper Compile Tests _

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

+1 :green_heart:
mvninstall
5m 50s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
compile
1m 45s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
checkstyle
2m 33s
HBASE-18095/client-locate-meta-no-zookeeper passed

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

+1 :green_heart:
javadoc
1m 17s
HBASE-18095/client-locate-meta-no-zookeeper passed

+0 :ok:
spotbugs
4m 55s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
6m 50s
HBASE-18095/client-locate-meta-no-zookeeper passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
checkstyle
0m 26s
hbase-common: The patch generated 0 new + 4 unchanged - 1 fixed = 4 total (was 5)

+1 :green_heart:
checkstyle
0m 33s
hbase-client: The patch generated 0 new + 0 unchanged - 12 fixed = 0 total (was 12)

+1 :green_heart:
checkstyle
1m 30s
hbase-server: The patch generated 0 new + 223 unchanged - 50 fixed = 223 total (was 273)

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

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

+1 :green_heart:
hadoopcheck
17m 25s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

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

+1 :green_heart:
findbugs
7m 22s
the patch passed

_ Other Tests _

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

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

-1 :x:
unit
174m 22s
hbase-server in the patch failed.

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

253m 59s

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestFromClientSide

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/11/artifact/out/Dockerfile

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

JIRA Issue
HBASE-23305

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 629e2ad8c337 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-954/out/precommit/personality/provided.sh

git revision
HBASE-18095/client-locate-meta-no-zookeeper / d016cd9962

Default Java
1.8.0_181

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/11/artifact/out/patch-unit-hbase-server.txt

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

Max. process+thread count
4468 (vs. ulimit of 10000)

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

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

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

Running tests locally I get
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 312.454 s <<< FAILURE! - in org.apache.hadoop.hbase.client.TestFromClientSideWithCoprocessor
org.apache.hadoop.hbase.client.TestFromClientSideWithCoprocessor.testScanMetrics[0]  Time elapsed: 33.15 s  <<< ERROR!
java.io.IOException: org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /hbase/hbaseid
Caused by: org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss for /hbase/hbaseid

Works for me. Try re-running? I noticed the mini cluster in cluster is very flaky, especially when you run it in a dev setup.

I was mentioning this to @ndimiduk offline but just wanted to update here too, for the record. JUnit BeforeParam does not work for us as expected because it runs before the test class constructor is called and does not have access to the test parameters. I've clarified this in the test comments. Also rebased and squashed commits. Thanks for the reviews. At this point we are waiting for @apurtell to take another look.

Rebased on top of my other patch that was merged few minutes ago.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 10 new or modified test files.

_ HBASE-18095/client-locate-meta-no-zookeeper Compile Tests _

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

+1 :green_heart:
mvninstall
5m 49s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
compile
1m 50s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
checkstyle
2m 42s
HBASE-18095/client-locate-meta-no-zookeeper passed

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

+1 :green_heart:
javadoc
1m 21s
HBASE-18095/client-locate-meta-no-zookeeper passed

+0 :ok:
spotbugs
5m 20s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
7m 20s
HBASE-18095/client-locate-meta-no-zookeeper passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
checkstyle
0m 26s
hbase-common: The patch generated 0 new + 4 unchanged - 1 fixed = 4 total (was 5)

+1 :green_heart:
checkstyle
0m 33s
hbase-client: The patch generated 0 new + 0 unchanged - 12 fixed = 0 total (was 12)

+1 :green_heart:
checkstyle
1m 32s
hbase-server: The patch generated 0 new + 223 unchanged - 50 fixed = 223 total (was 273)

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

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

+1 :green_heart:
hadoopcheck
19m 16s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

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

+1 :green_heart:
findbugs
8m 27s
the patch passed

_ Other Tests _

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

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

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

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

273m 39s

Reason
Tests

Failed junit tests
hadoop.hbase.quotas.TestClusterScopeQuotaThrottle

hadoop.hbase.security.access.TestSnapshotScannerHDFSAclController

hadoop.hbase.client.TestFromClientSide

hadoop.hbase.client.TestAsyncTableGetMultiThreaded

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/12/artifact/out/Dockerfile

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

JIRA Issue
HBASE-23305

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux f67fc951fca9 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-954/out/precommit/personality/provided.sh

git revision
HBASE-18095/client-locate-meta-no-zookeeper / d9c17c3681

Default Java
1.8.0_181

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/12/artifact/out/patch-unit-hbase-server.txt

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

Max. process+thread count
5531 (vs. ulimit of 10000)

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

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

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 10 new or modified test files.

_ HBASE-18095/client-locate-meta-no-zookeeper Compile Tests _

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

+1 :green_heart:
mvninstall
5m 45s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
compile
1m 47s
HBASE-18095/client-locate-meta-no-zookeeper passed

+1 :green_heart:
checkstyle
2m 34s
HBASE-18095/client-locate-meta-no-zookeeper passed

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

+1 :green_heart:
javadoc
1m 18s
HBASE-18095/client-locate-meta-no-zookeeper passed

+0 :ok:
spotbugs
5m  5s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
7m  0s
HBASE-18095/client-locate-meta-no-zookeeper passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
checkstyle
0m 25s
hbase-common: The patch generated 0 new + 4 unchanged - 1 fixed = 4 total (was 5)

+1 :green_heart:
checkstyle
0m 32s
hbase-client: The patch generated 0 new + 0 unchanged - 12 fixed = 0 total (was 12)

+1 :green_heart:
checkstyle
1m 30s
hbase-server: The patch generated 0 new + 223 unchanged - 50 fixed = 223 total (was 273)

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

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

+1 :green_heart:
hadoopcheck
17m 29s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

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

+1 :green_heart:
findbugs
7m  7s
the patch passed

_ Other Tests _

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

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

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

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

250m 44s

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestFromClientSide

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/13/artifact/out/Dockerfile

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

JIRA Issue
HBASE-23305

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 2294597fcad8 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-954/out/precommit/personality/provided.sh

git revision
HBASE-18095/client-locate-meta-no-zookeeper / d2d7b2bb24

Default Java
1.8.0_181

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-954/13/artifact/out/patch-unit-hbase-server.txt

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

Max. process+thread count
5489 (vs. ulimit of 10000)

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

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

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

@apurtell, @saintstack no further comments? I'd like to merge this one today.

Just had an offline chat with @apurtell about this. He mentioned he has no objections for the patch to go in today.


Acer osiris sound crashes with the latest LTS kernel in ArchLinux

Chromebook: Acer Chromebook 516 GE (CBG516-1H)
Write protect disabled, full ROM UEFI Firmware coreboot 4.20.1

Sound works in ArchLinux and is stable, but only like this:

Older ArchLinux LTS kernel from May 2023 - 6.1.27-1-lts
No sof-firmware

ArchLinux 6.1.51-1 - Starts okay, but crashes within minutes
ArchLinux 6.4.12.arch1-1 - No sound at all, however devices listed thanks to your script
Is there a patch somewhere available? I'd like to port it to the stable kernel (or LTS) and publish it to AUR if it works. I did this before for Swanky working with another contributor years ago for audio with Bay Trail.

Please provide logs.

You got it. Let me know if you need anything else, attached.
Booted into 6.4.12-arch1-1 when I grabbed these.
Debug.zip

It seems to be missing audio server logs.

Attached pulse audio logs set to max verbosity.
pulseaudio.zip

Not seeing anything wrong in pulseaudio, can you send dmesg for both the bad kernel and working kernel?

When working in older LTS kernel, no errors in dmesg. When in new kernel, a lot of these (also attached output)):
[   86.027556] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x60010000 (msg/reply size: 108/20): -22
[   86.027563] sof-audio-pci-intel-tgl 0000:00:1f.3: HW params ipc failed for stream 1
[   86.027568] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:00:1f.3: -22
[   86.027587]  Bluetooth: ASoC: error at __soc_pcm_hw_params on Bluetooth: -22
[   86.027590]  Bluetooth: ASoC: error at dpcm_fe_dai_hw_params on Bluetooth: -22
[   86.028332] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x60010000 (msg/reply size: 108/20): -22
[   86.028342] sof-audio-pci-intel-tgl 0000:00:1f.3: HW params ipc failed for stream 1
[   86.028346] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:00:1f.3: -22
[   86.028380]  Bluetooth: ASoC: error at __soc_pcm_hw_params on Bluetooth: -22
[   86.028385]  Bluetooth: ASoC: error at dpcm_fe_dai_hw_params on Bluetooth: -22
[   86.029089] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x60010000 (msg/reply size: 108/20): -22
[   86.029103] sof-audio-pci-intel-tgl 0000:00:1f.3: HW params ipc failed for stream 1
[   86.029109] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:00:1f.3: -22
[   86.029124]  Bluetooth: ASoC: error at __soc_pcm_hw_params on Bluetooth: -22
[   86.029126]  Bluetooth: ASoC: error at dpcm_fe_dai_hw_params on Bluetooth: -22
[   86.029819] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x60010000 (msg/reply size: 108/20): -22
[   86.029828] sof-audio-pci-intel-tgl 0000:00:1f.3: HW params ipc failed for stream 1
[   86.029831] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:00:1f.3: -22
[   86.029851]  Bluetooth: ASoC: error at __soc_pcm_hw_params on Bluetooth: -22
[   86.029856]  Bluetooth: ASoC: error at dpcm_fe_dai_hw_params on Bluetooth: -22
[   86.031095] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x60010000 (msg/reply size: 108/20): -22
[   86.031106] sof-audio-pci-intel-tgl 0000:00:1f.3: HW params ipc failed for stream 1
[   86.031108] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:00:1f.3: -22
[   86.031120]  Bluetooth: ASoC: error at __soc_pcm_hw_params on Bluetooth: -22
[   86.031123]  Bluetooth: ASoC: error at dpcm_fe_dai_hw_params on Bluetooth: -22
[   86.031783] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x60010000 (msg/reply size: 108/20): -22
[   86.031792] sof-audio-pci-intel-tgl 0000:00:1f.3: HW params ipc failed for stream 1
[   86.031797] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:00:1f.3: -22
[   86.031812]  Bluetooth: ASoC: error at __soc_pcm_hw_params on Bluetooth: -22
[   86.031813]  Bluetooth: ASoC: error at dpcm_fe_dai_hw_params on Bluetooth: -22
[   86.032461] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x60010000 (msg/reply size: 108/20): -22
[   86.032469] sof-audio-pci-intel-tgl 0000:00:1f.3: HW params ipc failed for stream 1
[   86.032474] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:00:1f.3: -22
[   86.032485]  Bluetooth: ASoC: error at __soc_pcm_hw_params on Bluetooth: -22
[   86.032487]  Bluetooth: ASoC: error at dpcm_fe_dai_hw_params on Bluetooth: -22
[   86.033125] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x60010000 (msg/reply size: 108/20): -22
[   86.033126] sof-audio-pci-intel-tgl 0000:00:1f.3: HW params ipc failed for stream 1
[   86.033126] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:00:1f.3: -22
[   86.033129]  Bluetooth: ASoC: error at __soc_pcm_hw_params on Bluetooth: -22
[   86.033129]  Bluetooth: ASoC: error at dpcm_fe_dai_hw_params on Bluetooth: -22
[   86.033681] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x60010000 (msg/reply size: 108/20): -22
[   86.033685] sof-audio-pci-intel-tgl 0000:00:1f.3: HW params ipc failed for stream 1
[   86.033687] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:00:1f.3: -22
[   86.033694]  Bluetooth: ASoC: error at __soc_pcm_hw_params on Bluetooth: -22
[   86.033696]  Bluetooth: ASoC: error at dpcm_fe_dai_hw_params on Bluetooth: -22
[   86.034451] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x60010000 (msg/reply size: 108/20): -22
[   86.034453] sof-audio-pci-intel-tgl 0000:00:1f.3: HW params ipc failed for stream 1
[   86.034454] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:00:1f.3: -22
[   86.034457]  Bluetooth: ASoC: error at __soc_pcm_hw_params on Bluetooth: -22
[   86.034458]  Bluetooth: ASoC: error at dpcm_fe_dai_hw_params on Bluetooth: -22
[   86.034936] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x60010000 (msg/reply size: 108/20): -22
[   86.034937] sof-audio-pci-intel-tgl 0000:00:1f.3: HW params ipc failed for stream 1
[   86.034938] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:00:1f.3: -22
[   86.034941]  Bluetooth: ASoC: error at __soc_pcm_hw_params on Bluetooth: -22
[   86.034942]  Bluetooth: ASoC: error at dpcm_fe_dai_hw_params on Bluetooth: -22
[   86.035605] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x60010000 (msg/reply size: 108/20): -22
[   86.035614] sof-audio-pci-intel-tgl 0000:00:1f.3: HW params ipc failed for stream 1
[   86.035619] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:00:1f.3: -22
[   86.035635]  Bluetooth: ASoC: error at __soc_pcm_hw_params on Bluetooth: -22
[   86.035636]  Bluetooth: ASoC: error at dpcm_fe_dai_hw_params on Bluetooth: -22
[   86.036281] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x60010000 (msg/reply size: 108/20): -22
[   86.036283] sof-audio-pci-intel-tgl 0000:00:1f.3: HW params ipc failed for stream 1
[   86.036284] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:00:1f.3: -22
[   86.036288]  Bluetooth: ASoC: error at __soc_pcm_hw_params on Bluetooth: -22
[   86.036289]  Bluetooth: ASoC: error at dpcm_fe_dai_hw_params on Bluetooth: -22
[   86.036914] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x60010000 (msg/reply size: 108/20): -22
[   86.036916] sof-audio-pci-intel-tgl 0000:00:1f.3: HW params ipc failed for stream 1
[   86.036916] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:00:1f.3: -22
[   86.036920]  Bluetooth: ASoC: error at __soc_pcm_hw_params on Bluetooth: -22
[   86.036921]  Bluetooth: ASoC: error at dpcm_fe_dai_hw_params on Bluetooth: -22
[   86.040914] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x60010000 (msg/reply size: 108/20): -22
[   86.040938] sof-audio-pci-intel-tgl 0000:00:1f.3: HW params ipc failed for stream 1
[   86.040940] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:00:1f.3: -22
[   86.040949]  DMIC16kHz: ASoC: error at __soc_pcm_hw_params on DMIC16kHz: -22
[   86.040955]  DMIC16kHz: ASoC: error at dpcm_fe_dai_hw_params on DMIC16kHz: -22
[   86.041886] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x60010000 (msg/reply size: 108/20): -22
[   86.041900] sof-audio-pci-intel-tgl 0000:00:1f.3: HW params ipc failed for stream 1
[   86.041903] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:00:1f.3: -22
[   86.041917]  DMIC16kHz: ASoC: error at __soc_pcm_hw_params on DMIC16kHz: -22
[   86.041925]  DMIC16kHz: ASoC: error at dpcm_fe_dai_hw_params on DMIC16kHz: -22
[   86.042861] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x60010000 (msg/reply size: 108/20): -22
[   86.042873] sof-audio-pci-intel-tgl 0000:00:1f.3: HW params ipc failed for stream 1
[   86.042879] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_h
[dmesg.zip](https://github.com/WeirdTreeThing/chromebook-linux-audio/files/12550331/dmesg.zip)
w_params on 0000:00:1f.3: -22
[   86.042891]  DMIC16kHz: ASoC: error at __soc_pcm_hw_params on DMIC16kHz: -22
[   86.042897]  DMIC16kHz: ASoC: error at dpcm_fe_dai_hw_params on DMIC16kHz: -22
[   86.043874] sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x60010000 (msg/reply size: 108/20): -22
[   86.043881] sof-audio-pci-intel-tgl 0000:00:1f.3: HW params ipc failed for stream 1
[   86.043884] sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC: error at snd_soc_pcm_component_hw_params on 0000:00:1f.3: -22
[   86.043900]  DMIC16kHz: ASoC: error at __soc_pcm_hw_params on DMIC16kHz: -22
[   86.043908]  DMIC16kHz: ASoC: error at dpcm_fe_dai_hw_params on DMIC16kHz: -22

Those errors are usually harmless, something else is probably wrong.

Switched to wireplumber, and the latest kernel and lts work now. Probably something with pulseaudio 🤷♂


Forgotten Realms: Demon Stone has multiple issues

Please describe your issue as accurately as possible. If you run into a problem with a binary release, make sure to test with latest master as well.
Important: When reporting an issue with a specific game or application, such as crashes or rendering issues, please include log files and a D3D11/D3D9 Apitrace (see https://github.com/apitrace/apitrace) so that the issue can be reproduced.
In order to create a trace for D3D11/D3D10: Run wine apitrace.exe trace -a dxgi YOURGAME.exe.
In order to create a trace for D3D9: Follow https://github.com/Joshua-Ashton/d9vk/wiki/Making-a-Trace.
DO NOT use DXVK together with apitrace!
Software information
Forgotten Realms: Demon Stone
System information

GPU: Nvidia GeForce GTX 960
Driver: 430.40.0
Wine version:  4.14 TKG
DXVK version: https://github.com/Joshua-Ashton/d9vk/commit/8490b27bf20b3ee20d0aa5d850e430841415e7e0

Apitrace file(s)
Windows trace (AMD Graphics): https://drive.google.com/file/d/1SWVx7KwEV3KmGI_o8LD1rgKLrKOg5Y-2/view?usp=sharing
D9VK trace (Nvidia Graphics):
https://drive.google.com/file/d/1cVXHeDhA3tcf6mxyehAClSsLdZqUQSiM/view?usp=sharing
Log files

d3d9.log: demonstone_d3d9.log
d3d11.log: N/A
dxgi.log: N/A

Hello! Demon Stone has several issues as of the current master. The HUD is missing some elements, models have white textures, and the loading screens aren't rendered properly.
D9VK:

Native (taken from Windows trace):

The Windows trace plays back without errors on my Nvidia machine, so it might be an nvidia issue :confused:
Also, the character models occasionally freeze during animations(which isn't shown in either trace), and @NerosTie mentioned an issue with the logo (not sure if I covered that here already or not). Thanks!

Are you using Wine's d3dcompiler impl?
ie. did you install d3dcompiler[_43/_47/_whatever] and d3d9x stuff via proton/winetricks

It doesn't seem like I'm using Wine's d3dcompiler. I installed d9vk through winetricks, and winetricks shows that d3dx9 and d3dcompiler_43 are installed. All those dlls are set to native from what I can see, and I went ahead and installed the extra d3dcompiler stuff just in case, but it looks like the issues persist.

With https://github.com/doitsujin/dxvk/issues/1409 and https://github.com/doitsujin/dxvk/commit/b9474cf787f52e3faf8fa670bdb85ce058d47ade , everything except the character halting has been fixed. Good job!

Can you show me what that issue is?

I apologize for my earlier statement. I honestly don't know what happened or how I came to my previous conclusion, but it seems pretty smooth now. When playing, there is some micro-stutter (am I using that correctly?) right after the camera turns to face the protagonist, however it's much harder to notice compared to before. It also didn't show up in my attempt to record the issue with OBS :ghost: , so I don't really know how to show it outside of describing it. My not-very-helpful failed attempt is here if you're curious (the relevant part would be at 0:12). I guess I'm OK closing it here if @NerosTie doesn't have any further objections.
Closing #321 for now.

Everything looks great now 🎉


fix(sticky-header): do not consider vertical ToC height in calculations

Related Ticket(s)
Description
The StickyHeader utility has logic for how to calculate the total height of elements on a given web page that are "stuck" to the top of the viewport. It exposes a CSS custom property, --dds-sticky-header-height, with this calculated value for other page elements to use.
In AEM, we were seeing this value be set much higher than the actual sum height of all stuck elements. It turns out we were adding the height of <dds-table-of-contents> elements that are configured to use the vertical presentation, which is unnecessary.
Changelog
Changed

Removes <dds-table-of-contents> in the vertical orientation from --dds-sticky-header-height calculation.
Fixes incorrectly named properties related to <dds-leadspace-with-search>, allowing those elements to be properly factored into calculations.

Testing Instructions
Visit the Dotcom Shell deploy preview's various Stories and verify the --dds-sticky-header-height custom property set on the root element has a value that matches the current "stuck" elements' height.

We should probably update the storybook story that helps demo this utility. Can we add a knob to add the L1 menu?
https://ibmdotcom-webcomponents.s3.us-east.cloud-object-storage.appdomain.cloud/deploy-previews/10605/index.html?path=/story/components-dotcom-shell--without-shell

Looks like we have a knob for that already.


Update MatterIDL codegen to not take into account enabled for client attributes

We expect to generate accessors for all client side attributes, so for client side this switches
code generation loops to use zcl_attributes_server.
This also switches to workardouns for other settings because of different helper modes:

clusterRef for isGlobalAttributes
entryType for isArray
completely DROPS isReportable (since everything is reportable currently ...only added a TODO)

As a result, .matter files are now expected to have all attributes in client clusters, regardless of zap enabling/disabling on them.
After https://github.com/project-chip/zap/pull/899  usage, we may be able to simplify these back...
Fixes #25684

Closing as #25693 will fix this and makes sure java zap-codegen is in sync with matter IDL codegen.


Sentinel-Queries/Azure Active Directory/Identity-AADRiskEventCorrelation.kql

Hello,
First of all, i love every single letter you have written so far. Its greatly appreciated in my learning of KQL! :)
Anyways, i tried this one today (Sentinel-Queries/Azure Active Directory/Identity-AADRiskEventCorrelation.kql) in a fully licensed tenant and get error:

Ive used the code as is and maybe im missing something. But incase not id let you know! :)
thank you very much.

Hello good sir,
I was working in both Sentinel and Advanced Threat Hunt.
However, in this instance it indeed looks like i copied it into the wrong window - i was 100% sure it was correct, god was i wrong :)
Thanks, i needed a mental break to realize it.
Thank you very much for the great work


Call set_current_order explicitly where we need it

set_current_order will be moved out of a before_filter in the ControllerHelpers::Order module.  This is currently hitting the database on just about every frontend page load when we really just need it when someone is signing in.  This moves that call to signing in and will be accompanied with an explanation for people that don't use solidus auth devise.

I think that you'd only need to adjust the comment slightly, as after the Solid PR gets merged, it will be no longer the case that the method will be called before.

This looks great, thank you @Murph33 - would you mind also adding a CHANGELOG.md entry, similar-ish to the one for your corresponding PR in core?


Add integration for controller-runtime controllers

This allows this library to trigger reconciles in a controller-runtime controller.

/unhold


Small pictures cannot be uploaded, but we know it too late

What

When we try to upload a picture that is deemed too small by the server, we get a localized error message at the background task level and that's it.
"Background task error (Exception: Could not upload picture: status not ok / La photo est trop petite. Attention à ne pas envoyer de photos prises sur Internet. Merci de n'envoyer que vos propres photos.)"
And the background task will be run again and again, and will always fail.
That brings inconsistency, as on the server the picture is not visible (as it was never uploaded) and on the user device the picture is considered OK.

Several solutions:

know in advance the limit sizes of the pictures for the server, so that we can reject from the app pictures that are too small
know when a picture was rejected because it was too small - for the moment we only get a localized message AFAIK (and it could fail for other reasons)
be able to warn the user that the picture was rejected because it was too small, and clean the device by removing the transient file and the background task

Steps to reproduce the behavior

Try to upload a very small picture
Go to the background task page
See that background task is still there, and failed

@stephanegigandet What is the minimum size (in pixels) of a picture that we upload, below which the server rejects it?

@stephanegigandet Thank you, I'll impact that in Smoothie.

@stephanegigandet By the way it looks like the 640x160 minimum size is enforced on the server side for new picture uploads, but not the crop on existing pictures, am I right?

@stephanegigandet By the way it looks like the 640x160 minimum size is enforced on the server side for new picture uploads, but not the crop on existing pictures, am I right?

@monsieurtanuki that's correct, the size is only for the upload of the image, not the cropping.

@monsieurtanuki that's correct, the size is only for the upload of the image, not the cropping.

@stephanegigandet OK, then we're done in Smoothie: we enforce the minimum size only for image uploads.


Publish to crates.io

[x] Prep repo for publishing
[x] Make a github release
[x] Publish to crates.io
[x] Make sure all links and properties are valid

This shouldn't have been closed. It got closed because it was linked to the PR #6

The docs aren't great right now, but they'll do.
I'll improve them once I've got a hilbert implementation and can figure out the doc structure better.

All done. First release of insides has been published. Wooo!


Feat/os2values

I just build opentype after our last commit. I don't really know where the change in dist/opentype.js come from (at least it's not from us :smile: )
We welcome any comment.
This PR only add os2 values for width weight et flag selection. We mimicked the behavior that happens when someone parse a font (i.e the values goes into tables.os2) and we provided an exhaustive list of values accepted by the standard.

Something like this is absolutely necessary.
It seems like you would need to directly set OS2 table values to have it affect the weight. Could you write example usage code of how that would look?

Customizing OS/2 values is a good idea ;)
@FranzPoize is it ready for merge?

(Feel free to close this PR now that #199 has been merged)


issue with Jasmine defaultTimeOutInterval

I am using protractor 5.1.1 and jasmine 2.6.0. all it steps in my spec file fail with error - A Jasmine spec timed out. Resetting the WebDriver Control Flow.
Message:
Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
Stack:
Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
at ontimeout (timers.js:365:14)
at tryOnTimeout (timers.js:237:5)
at Timer.listOnTimeout (timers.js:207:5)
below is the spec file -
`describe('test',function(){
it('1',function(){
console.log('step 1');
},10000);
it('2',function(){
    console.log('step 2');
},10000);

it('3',function(){
    console.log('step 3');
},10000);

});`
the script executes and console output is shown but for each of the steps (it) timeout error (mentioned above) is displayed. I have also tried setting the defaultTimeOutInterval in config file. I have also tried using  framework: 'jasmine',  framework: 'jasmine2', but same error is displayed in either of the options. have also tried scriptTimeout and pagetimeout options, but same issue persists
after executing the script, console looks like this -
step 1
A Jasmine spec timed out. Resetting the WebDriver Control Flow.
Fstep 2
A Jasmine spec timed out. Resetting the WebDriver Control Flow.
Fstep 3
A Jasmine spec timed out. Resetting the WebDriver Control Flow.
Note- I am executing my tests using grunt. is there any need of loading the plugins like the few I already have -  grunt.loadNpmTasks('grunt-protractor-runner');, grunt.loadNpmTasks('grunt-contrib-jshint');
grunt.loadNpmTasks('grunt-mocha-test'); ?
grunt version-
grunt-cli v1.2.0
grunt v1.0.1

Hi there!
Because it involves an error that could be any number of things and may be specific to your testing environment, your question is better suited for StackOverflow or Gitter. Please ask a question there with the 'protractor' tag or post in the Gitter Channel to get help.
From the the getting help section of the README:

Please ask usage and debugging questions on StackOverflow (use the "protractor" tag) or in the Angular discussion group. (Please do not ask support questions here on Github.)

Thanks!


Adds HumioUsers CRD

Currently a work in progress, soliciting feedback.

I fixed the last remaining bug. This is ready for review.


Documentation Tool?

I have a question about your docs. Did you use a template which is served with Nuxt (I see the powered by Nuxt at the bottom).
I have been considering moving my various oss projects to VitePress and figure that is what you were using?

I used nuxt/content with the official docs theme.
You can easily use create-nuxt-content-docs to build your docs.
I am also trying to use vitepress to replace nuxt/content to write documents for a better development experience.
But vitepress is still early WIP, I'm not sure it is a good idea to replace all documents with vitepress now.
vitepress and @nuxt/content-theme-docs are both awesome

@hunterliu1003 In addition to VitePress, I have reviewed VuePress which seems pretty slick as well (and more mature) but I would like to learn Nuxt so using nuxt/content would be a win win approach.
Thanks for response, much appreciated.


add GHA badge and remove Travis-CI

The GitHub Actions should run and we expect the tests to fail.

As expected, all the tests fail when trying to access api.iobis.org. The next PRs will address some more boilerplate code formatting and checks before we start addressing the code update.


This first click wouldn't produce any sound

I think this might be related to browser restriction. It does not allow you to play a sound until you click the page.

The issue has been fixed by adding a loading page


Runtime Lag

I'm working on the CodeCombat level "The Dunes" in Python. I'm noticing that when I have my code structured in a certain way, there's runtime lag.
If I have it set up this way, it's fine.
loop:
    enemy = self.findNearestEnemy()
    item = self.findNearestItem()
    if item:
        # Collect coins.
          if item:
            pos = item.pos
            itemX = pos.x
            itemY = pos.y
            self.moveXY(itemX, itemY)
    if enemy:
        if enemy.type is 'sand-yak' or enemy.type is 'burl':
            # Don't fight Sand Yaks or Burls! Just keep collecting coins.
            pass
        # But if the enemy is a 'thrower' or an 'ogre', fight them.
        if enemy.type is 'thrower' or enemy.type is 'ogre' and self.distanceTo(enemy) < 20:

If I move my 'if item' near to the end of my code, with an else, then the loop appears to prioritise the 'enemy' portion of the code, and slows down on going to the 'item' part of the code. There is a significant delay, as it seems to constantly be working in the 'enemy' portion, and rarely going to the 'item' portion.
However, if I structure the code as I have it set up, above, it runs smoothly, and will prioritise the coins first, and rarely jump to the enemy (only if no coins are left). Which is fine.
Just curious as to why this might be the case :)
Thanks!

I've fixed a bunch of perceived runtime lag with the plan() yielding dropped frame fix. I'm not sure this is what was causing your problem–the code is a bit strange–but I can't reproduce it now, so I assume it is fixed.


Support for complex LR scheduler configuration

Recursively construct objects if cls is present in sub-arguments. This means that complex schedulers such as SequentialLR str possible. The following is a demo config:
lr_scheduler_args:
  scheduler_cls: torch.optim.lr_scheduler.ChainedScheduler
  schedulers:
  - cls: torch.optim.lr_scheduler.SequentialLR
    schedulers:
    - cls: torch.optim.lr_scheduler.StepLR
      step_size: 10
    - cls: torch.optim.lr_scheduler.CosineAnnealingWarmRestarts
      T_0: 10
    milestones:
    - 10
  - cls: torch.optim.lr_scheduler.SequentialLR
    schedulers:
    - cls: torch.optim.lr_scheduler.ExponentialLR
      gamma: 0.5
    - cls: torch.optim.lr_scheduler.LinearLR
    - cls: torch.optim.lr_scheduler.MultiStepLR
      milestones:
      - 10
      - 20
    milestones:
    - 10
    - 20

Meanwhile, the side effect of supporting the complex configuration is that the LR scheduler state in the checkpoint is deprecated. The new learning rate will be calculated according to the latest configurations before training starts.

There are conflicts after merging #120 into main


Classifier without CNN features

Check whether there is again a big drop in performance when training on CDFS and testing on ELIAS.

To confirm what you mean: Using just magnitude features, train on CDFS and test on ELAIS, then compare against Middelburg (Norris equivalent for ELAIS)?

Was just discussing with Julie after your seminar about the worrying result from last Friday. To be left for after thesis is submitted.

Features: Magnitude, distance, everything except CNN.

No big drop in performance. ~78.0% CDFS -> ~75.5% ELAIS.


Question: Symbol Binding for 'fake' node

I'm trying to implements the JSX support for typescript, I have something that 'more or less' works for the parsing type-checking and emitting phases, but I fail to understand how I can do proper symbol binding for that case (and if my problems really come from that):
a JSX element:
<module.MyTagName ref="ref"  key="key" foo={bar}>Hello {name}</module.MyTagName>

should be the equivalent of :
{
    type : module.MyTagName;    //<== JSXElement tagName
    key : "key" // <== key attribute
    ref : "ref"   // <== ref attribute
    props : {
      children: ['Hello', name], //<== child
      { foo: bar} // attributes !== (ref || key)
    };
 }

Like you can see we have to pretty much manipulate the symbol, and for some properties 'type', 'props', 'children', we don't really have a declaration for attaching the symbol.
Like I said I have somewhat acceptable result:
({ type: Hello.world, key: "hello", ref: foo, props: { foo: "bar", callback: bar } });
>({ type: Hello.world, key: "hello", ref: foo, props: { foo: "bar", callback: bar } }) : { type: boolean; key: string; ref: () => any; props: { foo: string; callback: () => string; }; }
>{ type: Hello.world, key: "hello", ref: foo, props: { foo: "bar", callback: bar } } : { type: boolean; key: string; ref: () => any; props: { foo: string; callback: () => string; }; }
>type : boolean
>Hello.world : boolean
>Hello : typeof Hello
>world : boolean
>key : string
>ref : () => any
>foo : () => any
>props : { foo: string; callback: () => string; }
>{ foo: "bar", callback: bar } : { foo: string; callback: () => string; }
>foo : string
>callback : () => string
>bar : () => string

<Hello.world key="hello" ref={foo} foo="bar" callback={bar} />;
><Hello.world key="hello" ref={foo} foo="bar" callback={bar} /> : { type: boolean; key: string; ref: () => any; props: { foo: string; callback: () => string; }; }
>Hello : unknown
>world : unknown
>key : unknown
>ref : unknown
>foo : () => any
>foo : unknown
>callback : unknown
>bar : () => string

I have proper type resolution for the element itself, but the type for all the children of the element are not bound.
Questions:

Is the problem really comes from binding ?
Should I create dummy Node that extends declaration just to attach the symbols at something ?
Is there another way ?

I am not sure i understand the way you have it setup now. but just off the top of my head, i would assume you want to do that as a preprocessor transformation after you parse and before binding. I would say create a new "fake" node that has pos/length matching the original text when possible and 0 length when auto generated (e.g. in your example "type" would have length 0, where "module.MyTagName" would match your input pos and length). Then let the binder do its work to create the correct symbols. then from that point on, things should just proceed normally, and the emitted code should just be what you want.
in general the system amuses that everything is available at bind time and that there are no more symbol binding after that.

This is really interesting work. Would love to see it in action. Let me know if there are any API changes you need to ease your work.

Ok thanks to you it seems going well, you can see my branch here https://github.com/fdecampredon/TypeScript/tree/jsx (work in progress)

I'll close this issue since now everything is ok for me thanks for your help.


appClosed being set prematurely

The variable appClosed is being set to 1 if a blocking process is found, but before any processes are actually closed. This has unintended behavior in the case where BLOCKING_PROCESS_ACTION is silent_fail since nothing is actually closed in this case statement, only the cleanupAndExit function is called.
This function calls reopenClosedProcess which checks whether appClosed is set and tries to reopen the app if so. Because the app was already open (which is why we entered this case statement in the first place) and the variable was set prematurely, all this does is instead pop the app into focus on the user's screen, interrupting whatever it was they were doing.
This was noticed due to any app that we attempted to update with this method popping into focus one or more times a day.
I added an additional function to set this value in cases where Apple Script is being used to try and closed the app, so that this variable gets set correctly in each case. I also set the variable for the case where instead of Apple Script, the pkill command is used.

duplicate of #657 which is already merged into the dev branch for v11


Add content types for .bval and .bvec

Could somebody with more knowledge about both content types and neuroimaging review this PR?
@lzehl, maybe @apdavison?

@Peyman-N can you review this, since it seems to be for MRI data?

Hi Lyuba,
Do we need the ".text" part at the end of the name? Looking at other similar schema names, I was wondering if application/vnd.fsl.bval and application/vnd.fsl.bvec would be enough, since I don't see the ending .text in other names. I'm asking because we need to rename the files as well, I suppose (text_x-bval.jsonld -> application_vnd.fsl.bval.jsonld if I omit the .text part).
What do you think?
All the best,
Eszter

@eapapp I took this part from IANA as example where often the base format (in this case text) is indicated in the name. @apdavison what do you think? I find these indications useful but I'm not sure I fully understand the IANA naming convention there.

@apdavison thank you. @eapapp then let's update to "text/vnd.fsl.bval" / "text/vnd.fsl.bvec" (including updating the filenames to "text_vnd.fsl.bval.jsonld" / "text_vnd.fsl.bvec.jsonld")

@Peyman-N would you please review the changes I made to support the merge of @eapapp PR? If you think this is good please approve and merge

Hi @Peyman-N, could you please review and merge this PR if it looks okay? It would be great to have these two content types available in the KG. Thanks a lot! 🙏🏻

Hi @eapapp Sorry I don't know why I didn't get any notification for this.
Just a small modification and I think it is good to go.

Hi @Peyman-N , I have updated the description. Please let me know if there is anything more I can do (you can also edit the files directly if you like).


Fix bug occuring upon server restart

Either we do it like that or we enforce that only one token can have the characteristics of an admin token. At the moment those characteristics are that the token can be used infinitely and it has api rights.

yes


{:?} should be debug, and text format should be another function like .text_format()

Currently println!("{:?}", message) prints protobuf text format, which is against rust conventions.
println!("{:?}", message) should print in a format similar to debug info.
message.text_format() (name suggestions welcome) should output protobuf text format.

Done in v3.


Rendering problem in markdown and Jekyll

Hi Tate,
Thanks for the project. I am using it in my own blog built with Jekyll and Minimal theme. When I put the following raw html code in the middle of Markdown file
<pre id="ts" style="display:none">
\begin{algorithmic}
\PRINT \texttt{'hello world'}
\end{algorithmic}
</pre>

<script type="text/javascript">
    var testExamples = document.getElementById("ts").textContent;
    pseudocode.render(testExamples, document.body, {
        lineNumber: true,
        noEnd: false
    });
</script>

the output html will put the algorithm in the end of the post like the following:

I will appreciate it a lot if you can provide some helpful suggestions.
Thanks,
Chao

I have found the reason. I need to change the second parameter of pseudocode.render to the element I want my algorithm to be placed at.

@Alanthink How do you render pseudocode.js in your the minimal theme? Can provide some hints for me. Currently I am stuck at it.
Thanks for any help!


Remove qoutes from browser option var

Hi please remove qoutes from browser option vars specifically for firefox
If not then when firefox private windows opens up with two tabs one containing aws console and other one displaying all your file / directories in local drive @ following URL file:///Users/myusername/
"$AWS_VAULT_PL_BROWSER_LAUNCH_OPTS" should be updated with $AWS_VAULT_PL_BROWSER_LAUNCH_OPTS

Hi @farhansaed - thank you for reporting this issue. I'm currently away from a laptop to confirm/fix this. Would you please submit a PR? I'll be happy to merge it.

I have generated the pull request.


configure file for training fbwq_half

would you mind share the configure file for training fbwq_half and fbwq_full?
Also, why do you name it fbwq_half instead of WebQuestionsSP_half?
Another thing is
May I know how you pre-train MetaQA data? Do you use the code in directory "train_embeddings" to learn the embedding? If so, can you share the command of running the main.py with me?

May I know why you don't kge to train MetaQA?

Fbwq = freebasewebquestions. Other names might have been better
We used that code to train embeddings for MetaQA. Since that code isn't scalable, we used libkge for fbwq
In hindsight, it would have been better to use libkge for all datasets
If I remember correctly, in one of the closed issues a config file has been shared. If you can look for it there it would be great

Yes, I checked that issue. https://github.com/malllabiisc/EmbedKGQA/issues/97
But I don't know whether it could achieve the same performance as your model. Because there are many parameters in the file, e.g., learning_rate, max_epochs, batch_size, drop out rate. It would be great if you could share your original file.

Let me look for it and I'll get back to you
On Sat, Nov 20, 2021, 10:10 AM lihuiliullh @.***> wrote:

Yes, I checked that issue. #97
https://github.com/malllabiisc/EmbedKGQA/issues/97
But I don't know whether it could achieve the same performance as your
model. Because there are many parameters in the file, e.g., learning_rate,
max_epochs, batch_size, drop out rate. It would be great if you could share
your original file.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/malllabiisc/EmbedKGQA/issues/108#issuecomment-974592890,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAO6ADYQJSWA7QPIUTNBYU3UM4RDTANCNFSM5INPYVLQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Thanks. Also, can you share the command line you use to pre-train MetaQA?

This should be the correct config
complex:
  entity_embedder:
    dropout: 0.44299429655075073
    regularize_weight: 7.830760727899156e-12
  relation_embedder:
    dropout: -0.4746062345802784
    regularize_weight: 1.182876478423781e-10
dataset:
  name: fbwq_half
eval:
  batch_size: 200
  chunk_size: 25000
  num_workers: 2
import:
- complex
lookup_embedder:
  dim: 400
  initialize_args:
    normal_:
      mean: 0.0
      std: 5.8970567449527816e-05
  regularize_args:
    p: 1
    weighted: true
  sparse: true
model: complex
negative_sampling:
  implementation: batch
  num_samples:
    o: 7851
    s: 2176
  shared: true
  with_replacement: false
train:
  auto_correct: true
  batch_size: 1024
  loss_arg: .nan
  lr_scheduler: ReduceLROnPlateau
  lr_scheduler_args:
    factor: 0.95
    mode: max
    patience: 1
    threshold: 0.0001
  max_epochs: 200
  num_workers: 8
  optimizer_args:
    lr: 0.6560544891789137
  type: negative_sampling
valid:
  early_stopping:
    min_threshold:
      epochs: 10
      metric_value: 0.1
    patience: 10


One authenticate method on the authenticator interface.

Instead of having one instance of Authenticator, and that interface
defines two methods, we now have two instances of Authenticator and
that interface defines one method.
This prevents leaking request-specific configuration (the authenticator)
into shared connection configuration (the proxy authenticator).

LGTM


Epic: ATBD Upload Feature

For NASA FY23Q3, a new feature is requested to allow for uploading ADBD PDFs into APT, allowing users to use other editing tools (Word, Google Docs, and LaTeX) or to upload historical ATBDs. A new workflow, infrastructure, and document search/display capabilities will need to be added.

Replaced with https://github.com/NASA-IMPACT/nasa-apt/issues/714


Php additions

new php files were added for the interfacing of html with the database

Linking to pgsql has yet to be tested, but will be done soon


Tenancy for central admin

This PR is adding a way how to use tenancy from remote region in central admin.
This change would require the user to manually create the tenant structure that exists in the remote regions in the global region.
Links

https://bugzilla.redhat.com/show_bug.cgi?id=1465158

@miq-bot assign @gtanzillo
@miq-bot add_label enhancement, rbac

@lpichler Can this be hammer/yes?

@lpichler Can this be hammer/yes?

@simaishi yes, I tested it locally.


Add direct link to FAQ from Main Page

there is a FAQ link on main nav, but I think you wanted something else. please clarify