HBASE-22739 check bound where removeRegion

https://issues.apache.org/jira/browse/HBASE-22739.
this is the last !!!

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
76
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.1 Compile Tests _

+1
mvninstall
319
branch-2.1 passed

+1
compile
57
branch-2.1 passed

+1
checkstyle
88
branch-2.1 passed

+1
shadedjars
281
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
42
branch-2.1 passed

0
spotbugs
180
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
178
branch-2.1 passed

_ Patch Compile Tests _

+1
mvninstall
296
the patch passed

+1
compile
58
the patch passed

+1
javac
58
the patch passed

-1
checkstyle
84
hbase-server: The patch generated 1 new + 61 unchanged - 0 fixed = 62 total (was 61)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
273
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1326
Patch does not cause any errors with Hadoop 2.7.7 2.8.5 or 3.0.3 3.1.2.

+1
javadoc
35
the patch passed

+1
findbugs
184
the patch passed

_ Other Tests _

-1
unit
14933
hbase-server in the patch failed.

+1
asflicense
22
The patch does not generate ASF License warnings.

18651

Reason
Tests

Failed junit tests
hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures

hadoop.hbase.client.TestAsyncClusterAdminApi2

Subsystem
Report/Notes

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

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

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

uname
Linux f81f0839677e 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 GNU/Linux

Build tool
maven

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

git revision
branch-2.1 / 100a625324

Default Java
1.8.0_181

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

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

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

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

modules
C: hbase-server U: hbase-server

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

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

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
105
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.1 Compile Tests _

+1
mvninstall
348
branch-2.1 passed

+1
compile
53
branch-2.1 passed

+1
checkstyle
78
branch-2.1 passed

+1
shadedjars
244
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
34
branch-2.1 passed

0
spotbugs
184
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
182
branch-2.1 passed

_ Patch Compile Tests _

+1
mvninstall
290
the patch passed

+1
compile
56
the patch passed

+1
javac
56
the patch passed

-1
checkstyle
79
hbase-server: The patch generated 1 new + 61 unchanged - 0 fixed = 62 total (was 61)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
236
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1346
Patch does not cause any errors with Hadoop 2.7.7 2.8.5 or 3.0.3 3.1.2.

+1
javadoc
33
the patch passed

+1
findbugs
177
the patch passed

_ Other Tests _

-1
unit
13645
hbase-server in the patch failed.

+1
asflicense
30
The patch does not generate ASF License warnings.

17316

Reason
Tests

Failed junit tests
hadoop.hbase.replication.TestMasterReplication

hadoop.hbase.client.TestAdmin1

hadoop.hbase.replication.TestReplicationSmallTests

Subsystem
Report/Notes

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

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

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

uname
Linux 77f4d2966b17 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 GNU/Linux

Build tool
maven

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

git revision
branch-2.1 / fd267168d8

Default Java
1.8.0_181

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

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

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

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

modules
C: hbase-server U: hbase-server

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

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

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
100
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.1 Compile Tests _

+1
mvninstall
356
branch-2.1 passed

+1
compile
62
branch-2.1 passed

+1
checkstyle
103
branch-2.1 passed

+1
shadedjars
283
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
37
branch-2.1 passed

0
spotbugs
195
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
193
branch-2.1 passed

_ Patch Compile Tests _

+1
mvninstall
322
the patch passed

+1
compile
62
the patch passed

+1
javac
62
the patch passed

-1
checkstyle
94
hbase-server: The patch generated 1 new + 61 unchanged - 0 fixed = 62 total (was 61)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
278
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1347
Patch does not cause any errors with Hadoop 2.7.7 2.8.5 or 3.0.3 3.1.2.

+1
javadoc
34
the patch passed

+1
findbugs
186
the patch passed

_ Other Tests _

-1
unit
13923
hbase-server in the patch failed.

+1
asflicense
26
The patch does not generate ASF License warnings.

17813

Reason
Tests

Failed junit tests
hadoop.hbase.replication.regionserver.TestReplicationSource

hadoop.hbase.client.TestAdmin1

Subsystem
Report/Notes

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

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

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

uname
Linux 10eb93d7d328 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 GNU/Linux

Build tool
maven

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

git revision
branch-2.1 / f8b592e9f8

Default Java
1.8.0_181

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

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

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

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

modules
C: hbase-server U: hbase-server

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

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

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
67
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.1 Compile Tests _

+1
mvninstall
288
branch-2.1 passed

+1
compile
50
branch-2.1 passed

+1
checkstyle
73
branch-2.1 passed

+1
shadedjars
237
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
36
branch-2.1 passed

0
spotbugs
172
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
170
branch-2.1 passed

_ Patch Compile Tests _

+1
mvninstall
273
the patch passed

+1
compile
57
the patch passed

+1
javac
57
the patch passed

-1
checkstyle
79
hbase-server: The patch generated 1 new + 61 unchanged - 0 fixed = 62 total (was 61)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
234
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1164
Patch does not cause any errors with Hadoop 2.7.7 2.8.5 or 3.0.3 3.1.2.

+1
javadoc
33
the patch passed

+1
findbugs
194
the patch passed

_ Other Tests _

-1
unit
16861
hbase-server in the patch failed.

+1
asflicense
95
The patch does not generate ASF License warnings.

20282

Reason
Tests

Failed junit tests
hadoop.hbase.quotas.TestSpaceQuotas

hadoop.hbase.replication.TestReplicationKillSlaveRSWithSeparateOldWALs

hadoop.hbase.replication.TestReplicationSmallTests

hadoop.hbase.client.TestAsyncTableAdminApi

hadoop.hbase.replication.TestMasterReplication

hadoop.hbase.client.TestFromClientSide3

hadoop.hbase.master.TestAssignmentManagerMetrics

hadoop.hbase.client.TestAdmin1

Subsystem
Report/Notes

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

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

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

uname
Linux aee43a4b4871 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 GNU/Linux

Build tool
maven

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

git revision
branch-2.1 / f8b592e9f8

Default Java
1.8.0_181

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

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

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

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

modules
C: hbase-server U: hbase-server

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

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

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
197
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.1 Compile Tests _

+1
mvninstall
466
branch-2.1 passed

+1
compile
57
branch-2.1 passed

+1
checkstyle
86
branch-2.1 passed

+1
shadedjars
257
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
39
branch-2.1 passed

0
spotbugs
181
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
178
branch-2.1 passed

_ Patch Compile Tests _

+1
mvninstall
329
the patch passed

+1
compile
59
the patch passed

+1
javac
59
the patch passed

-1
checkstyle
72
hbase-server: The patch generated 1 new + 61 unchanged - 0 fixed = 62 total (was 61)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
240
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1260
Patch does not cause any errors with Hadoop 2.7.7 2.8.5 or 3.0.3 3.1.2.

+1
javadoc
32
the patch passed

+1
findbugs
165
the patch passed

_ Other Tests _

-1
unit
15573
hbase-server in the patch failed.

+1
asflicense
61
The patch does not generate ASF License warnings.

19558

Subsystem
Report/Notes

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

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

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

uname
Linux 89d4f7176330 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 GNU/Linux

Build tool
maven

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

git revision
branch-2.1 / e54c4018e7

Default Java
1.8.0_181

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

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

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

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

modules
C: hbase-server U: hbase-server

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

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

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
64
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.1 Compile Tests _

+1
mvninstall
361
branch-2.1 passed

+1
compile
70
branch-2.1 passed

+1
checkstyle
104
branch-2.1 passed

+1
shadedjars
322
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
43
branch-2.1 passed

0
spotbugs
205
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
202
branch-2.1 passed

_ Patch Compile Tests _

+1
mvninstall
361
the patch passed

+1
compile
67
the patch passed

+1
javac
67
the patch passed

-1
checkstyle
86
hbase-server: The patch generated 1 new + 61 unchanged - 0 fixed = 62 total (was 61)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
291
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1483
Patch does not cause any errors with Hadoop 2.7.7 2.8.5 or 3.0.3 3.1.2.

+1
javadoc
40
the patch passed

+1
findbugs
225
the patch passed

_ Other Tests _

-1
unit
13890
hbase-server in the patch failed.

+1
asflicense
33
The patch does not generate ASF License warnings.

18105

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestAsyncTableGetMultiThreaded

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-411/6/artifact/out/Dockerfile

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

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

uname
Linux 5856f5837720 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 GNU/Linux

Build tool
maven

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

git revision
branch-2.1 / 31c99ff393

Default Java
1.8.0_181

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

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

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

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

modules
C: hbase-server U: hbase-server

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

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

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
78
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
1
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.1 Compile Tests _

-1
mvninstall
133
root in branch-2.1 failed.

-1
compile
38
hbase-server in branch-2.1 failed.

+1
checkstyle
73
branch-2.1 passed

-1
shadedjars
166
branch has 24 errors when building our shaded downstream artifacts.

+1
javadoc
29
branch-2.1 passed

0
spotbugs
231
Used deprecated FindBugs config; considering switching to SpotBugs.

-1
findbugs
35
hbase-server in branch-2.1 failed.

_ Patch Compile Tests _

-1
mvninstall
134
root in the patch failed.

-1
compile
37
hbase-server in the patch failed.

-1
javac
37
hbase-server in the patch failed.

-1
checkstyle
71
hbase-server: The patch generated 1 new + 61 unchanged - 0 fixed = 62 total (was 61)

+1
whitespace
0
The patch has no whitespace issues.

-1
shadedjars
166
patch has 24 errors when building our shaded downstream artifacts.

-1
hadoopcheck
95
The patch causes 24 errors with Hadoop v2.7.7.

-1
hadoopcheck
194
The patch causes 24 errors with Hadoop v2.8.5.

-1
hadoopcheck
293
The patch causes 24 errors with Hadoop v3.0.3.

-1
hadoopcheck
395
The patch causes 24 errors with Hadoop v3.1.2.

+1
javadoc
29
the patch passed

-1
findbugs
35
hbase-server in the patch failed.

_ Other Tests _

-1
unit
36
hbase-server in the patch failed.

+1
asflicense
10
The patch does not generate ASF License warnings.

1526

Subsystem
Report/Notes

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

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

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

uname
Linux 66bc47482314 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 GNU/Linux

Build tool
maven

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

git revision
branch-2.1 / d45b2d4469

Default Java
1.8.0_181

mvninstall
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-411/7/artifact/out/branch-mvninstall-root.txt

compile
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-411/7/artifact/out/branch-compile-hbase-server.txt

shadedjars
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-411/7/artifact/out/branch-shadedjars.txt

findbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-411/7/artifact/out/branch-findbugs-hbase-server.txt

mvninstall
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-411/7/artifact/out/patch-mvninstall-root.txt

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

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

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

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

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-411/7/artifact/out/patch-javac-2.7.7.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-411/7/artifact/out/patch-javac-2.8.5.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-411/7/artifact/out/patch-javac-3.0.3.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-411/7/artifact/out/patch-javac-3.1.2.txt

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

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

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

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

modules
C: hbase-server U: hbase-server

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

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

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
63
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.1 Compile Tests _

-1
mvninstall
134
root in branch-2.1 failed.

-1
compile
33
hbase-server in branch-2.1 failed.

+1
checkstyle
69
branch-2.1 passed

-1
shadedjars
159
branch has 36 errors when building our shaded downstream artifacts.

+1
javadoc
29
branch-2.1 passed

0
spotbugs
222
Used deprecated FindBugs config; considering switching to SpotBugs.

-1
findbugs
33
hbase-server in branch-2.1 failed.

_ Patch Compile Tests _

-1
mvninstall
131
root in the patch failed.

-1
compile
34
hbase-server in the patch failed.

-1
javac
34
hbase-server in the patch failed.

-1
checkstyle
71
hbase-server: The patch generated 1 new + 61 unchanged - 0 fixed = 62 total (was 61)

+1
whitespace
0
The patch has no whitespace issues.

-1
shadedjars
160
patch has 36 errors when building our shaded downstream artifacts.

-1
hadoopcheck
89
The patch causes 36 errors with Hadoop v2.7.7.

-1
hadoopcheck
186
The patch causes 36 errors with Hadoop v2.8.5.

-1
hadoopcheck
284
The patch causes 36 errors with Hadoop v3.0.3.

-1
hadoopcheck
378
The patch causes 36 errors with Hadoop v3.1.2.

+1
javadoc
29
the patch passed

-1
findbugs
33
hbase-server in the patch failed.

_ Other Tests _

-1
unit
33
hbase-server in the patch failed.

+1
asflicense
9
The patch does not generate ASF License warnings.

1453

Subsystem
Report/Notes

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

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

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

uname
Linux 2f7040e2a26e 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 GNU/Linux

Build tool
maven

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

git revision
branch-2.1 / 65a6b270dd

Default Java
1.8.0_181

mvninstall
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-411/8/artifact/out/branch-mvninstall-root.txt

compile
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-411/8/artifact/out/branch-compile-hbase-server.txt

shadedjars
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-411/8/artifact/out/branch-shadedjars.txt

findbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-411/8/artifact/out/branch-findbugs-hbase-server.txt

mvninstall
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-411/8/artifact/out/patch-mvninstall-root.txt

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

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

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

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

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-411/8/artifact/out/patch-javac-2.7.7.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-411/8/artifact/out/patch-javac-2.8.5.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-411/8/artifact/out/patch-javac-3.0.3.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-411/8/artifact/out/patch-javac-3.1.2.txt

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

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

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

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

modules
C: hbase-server U: hbase-server

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

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

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
40
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.1 Compile Tests _

+1
mvninstall
272
branch-2.1 passed

+1
compile
49
branch-2.1 passed

+1
checkstyle
74
branch-2.1 passed

+1
shadedjars
233
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
31
branch-2.1 passed

0
spotbugs
158
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
155
branch-2.1 passed

_ Patch Compile Tests _

+1
mvninstall
271
the patch passed

+1
compile
51
the patch passed

+1
javac
51
the patch passed

-1
checkstyle
74
hbase-server: The patch generated 1 new + 61 unchanged - 0 fixed = 62 total (was 61)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
228
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1134
Patch does not cause any errors with Hadoop 2.7.7 2.8.5 or 3.0.3 3.1.2.

+1
javadoc
36
the patch passed

+1
findbugs
182
the patch passed

_ Other Tests _

+1
unit
8339
hbase-server in the patch passed.

+1
asflicense
26
The patch does not generate ASF License warnings.

11536

Subsystem
Report/Notes

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

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

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

uname
Linux 6a99de151a68 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 GNU/Linux

Build tool
maven

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

git revision
branch-2.1 / 11b647be23

Default Java
1.8.0_181

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

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

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

modules
C: hbase-server U: hbase-server

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

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

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
93
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.1 Compile Tests _

+1
mvninstall
320
branch-2.1 passed

+1
compile
57
branch-2.1 passed

+1
checkstyle
92
branch-2.1 passed

+1
shadedjars
260
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
33
branch-2.1 passed

0
spotbugs
187
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
185
branch-2.1 passed

_ Patch Compile Tests _

+1
mvninstall
321
the patch passed

+1
compile
58
the patch passed

+1
javac
58
the patch passed

-1
checkstyle
92
hbase-server: The patch generated 1 new + 61 unchanged - 0 fixed = 62 total (was 61)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
283
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1761
Patch does not cause any errors with Hadoop 2.7.7 2.8.5 or 3.0.3 3.1.2.

+1
javadoc
48
the patch passed

+1
findbugs
220
the patch passed

_ Other Tests _

-1
unit
14170
hbase-server in the patch failed.

+1
asflicense
30
The patch does not generate ASF License warnings.

18526

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestFromClientSide

hadoop.hbase.client.TestAdmin1

Subsystem
Report/Notes

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

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

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

uname
Linux b3f38f685855 4.15.0-52-generic #56-Ubuntu SMP Tue Jun 4 22:49:08 UTC 2019 x86_64 GNU/Linux

Build tool
maven

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

git revision
branch-2.1 / 29f8e195ef

Default Java
1.8.0_181

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

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

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

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

modules
C: hbase-server U: hbase-server

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

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

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
121
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.1 Compile Tests _

+1
mvninstall
468
branch-2.1 passed

+1
compile
52
branch-2.1 passed

+1
checkstyle
78
branch-2.1 passed

+1
shadedjars
256
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
31
branch-2.1 passed

0
spotbugs
170
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
167
branch-2.1 passed

_ Patch Compile Tests _

+1
mvninstall
299
the patch passed

+1
compile
50
the patch passed

+1
javac
50
the patch passed

-1
checkstyle
73
hbase-server: The patch generated 1 new + 61 unchanged - 0 fixed = 62 total (was 61)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
228
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1227
Patch does not cause any errors with Hadoop 2.7.7 2.8.5 or 3.0.3 3.1.2.

+1
javadoc
31
the patch passed

+1
findbugs
162
the patch passed

_ Other Tests _

+1
unit
12696
hbase-server in the patch passed.

+1
asflicense
33
The patch does not generate ASF License warnings.

16328

Subsystem
Report/Notes

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

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

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

uname
Linux 0a0ec76dff95 4.4.0-137-generic #163-Ubuntu SMP Mon Sep 24 13:14:43 UTC 2018 x86_64 GNU/Linux

Build tool
maven

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

git revision
branch-2.1 / 29f8e195ef

Default Java
1.8.0_181

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

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

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

modules
C: hbase-server U: hbase-server

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

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

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
66
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.1 Compile Tests _

+1
mvninstall
364
branch-2.1 passed

+1
compile
66
branch-2.1 passed

+1
checkstyle
91
branch-2.1 passed

+1
shadedjars
299
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
42
branch-2.1 passed

0
spotbugs
205
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
202
branch-2.1 passed

_ Patch Compile Tests _

+1
mvninstall
351
the patch passed

+1
compile
66
the patch passed

+1
javac
66
the patch passed

-1
checkstyle
96
hbase-server: The patch generated 1 new + 61 unchanged - 0 fixed = 62 total (was 61)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
301
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1446
Patch does not cause any errors with Hadoop 2.7.7 2.8.5 or 3.0.3 3.1.2.

+1
javadoc
43
the patch passed

+1
findbugs
205
the patch passed

_ Other Tests _

-1
unit
13960
hbase-server in the patch failed.

+1
asflicense
30
The patch does not generate ASF License warnings.

18058

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestAsyncTableGetMultiThreaded

Subsystem
Report/Notes

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

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

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

uname
Linux 88412f50d540 4.4.0-154-generic #181-Ubuntu SMP Tue Jun 25 05:29:03 UTC 2019 x86_64 GNU/Linux

Build tool
maven

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

git revision
branch-2.1 / 29f8e195ef

Default Java
1.8.0_181

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

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

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

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

modules
C: hbase-server U: hbase-server

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

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

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
363
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.1 Compile Tests _

+1
mvninstall
329
branch-2.1 passed

+1
compile
57
branch-2.1 passed

+1
checkstyle
93
branch-2.1 passed

+1
shadedjars
256
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
34
branch-2.1 passed

0
spotbugs
176
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
174
branch-2.1 passed

_ Patch Compile Tests _

+1
mvninstall
311
the patch passed

+1
compile
55
the patch passed

+1
javac
55
the patch passed

-1
checkstyle
91
hbase-server: The patch generated 1 new + 61 unchanged - 0 fixed = 62 total (was 61)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
268
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1416
Patch does not cause any errors with Hadoop 2.7.7 2.8.5 or 3.0.3 3.1.2.

+1
javadoc
36
the patch passed

+1
findbugs
184
the patch passed

_ Other Tests _

-1
unit
11592
hbase-server in the patch failed.

+1
asflicense
28
The patch does not generate ASF License warnings.

15718

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestFromClientSide3

hadoop.hbase.TestRegionRebalancing

hadoop.hbase.master.TestCatalogJanitorCluster

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-411/15/artifact/out/Dockerfile

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

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

uname
Linux e0ba864c4955 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64 GNU/Linux

Build tool
maven

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

git revision
branch-2.1 / 9799e0b6b2

Default Java
1.8.0_181

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

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

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

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

modules
C: hbase-server U: hbase-server

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

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

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.


Added MACD indicator and also added to backtest for plotting

What have you changed and why?
MACD indicator file is added an plotted by adding a line to backtesting/main.go
Related Issues
Link related issues here.

Closes https://github.com/rodrigo-brito/ninjabot/issues/33

Codecov Report

Merging #108 (367a981) into main (dfe33ec) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #108   +/-   ##
=======================================
  Coverage   49.88%   49.88%
=======================================
  Files          15       15
  Lines        2211     2211
=======================================
  Hits         1103     1103
  Misses       1045     1045
  Partials       63       63

Continue to review full report at Codecov.

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

Hi @gunebakan, great job!
I ajusted some visual details and include a warmup period for the data:


Context merging

Which issue does this PR address?
This PR implements (nested) context merging, so things like this will work again:
(
  if
    true
  then
    { foo: { a+: 1 }}
  else
    { foo: { b-: 1 }}
).foo.a+

As a matter of fact this requires adjustments in custom context providers (these must implement the merging properly themselves, cf. https://github.com/nikku/lezer-feel/pull/41/commits/280258ade8f00b550be68db3d8d4b1a775b092dc).
Closes #19

CC @marstamm


Fix variable scope in dashboard.js. Fixes #2672.

OK - think that needs to be a separate PR though.

Alright. Would you add it?

I've made an issue - #2674 . Will try and look at it when I have time.


trx: cancel/committed_version/get_address_for_key

Sorry about the conflicts. I decided to document everything today. I think we’re ready for a release to get some feedback. Also, do you want me to make you a collaborator on the repo?

I updated the PR to fix issues on review. I also rebased to master and fix errors from missing_doc. I tried to fill missing docs with matching styles. Please fill free to revise if there's a problem.
Thanks for the invite. I agree to make a the release for feedback.


Center cfp button

Currently it looks like this :P hopefully this will place it on the next line.

Now it looks like this :)


[WIP] Specify package dependencies

Depending on the type of monorepo, undeclared dependencies break the build.

[ ]  remove ./scripts/sync-deps/ folder.

Going to close this out! Thanks for bringing it up though I'll have to revisit soon


[question] Will the function of lazy injection be available in future?

reference http://php-di.org/doc/lazy-injection.html

It is not currently planned as I don't see a big enough benefit to it. I am open to discussion on use cases but at the moment, unfortunately, it's a no.


Add warning to 'fides deploy' when installed outside of a virtual environment

Code Changes

[X] Add check to fides deploy that logs a warning outside a virtual environment

Steps to Confirm

[X] Use pip install <path/to/fides/repo/dir> to install the local package and run fides deploy to confirm warning"

Example warning:

~/git/sandbox/fides-deploy-test% fides deploy up
Using default configuration values.
Using default configuration values.
in check_virtualenv<EMAIL_ADDRESS><EMAIL_ADDRESS>WARNING: Your 'fides' CLI is installed outside of a virtual environment at<EMAIL_ADDRESS>Docker may not have permission to access this path, so if you encounter issues with Docker mounts, try reinstalling 'ethyca-fides' using a virtual environment (see https://docs.python.org/3/library/venv.html).
If you did install using a virtual environment, check your PATH. You may have a global version of 'ethyca-fides' installed that is taking precedence!
Docker version is compatible, starting deploy...
Pulling ethyca/fides image from DockerHub to match local fides version: 2.6.1.post0.dev70

Pre-Merge Checklist

[X] All CI Pipelines Succeeded
Documentation:

[X] documentation complete, PR opened in fidesdocs
[X] documentation issue created in fidesdocs

[X] Issue Requirements are Met
[X] Relevant Follow-Up Issues Created
[ ] Update CHANGELOG.md

Description Of Changes
Users regularly run into mysterious Docker permissioning issues when using fides deploy because, on most operating systems, the globally installed Python libraries folder isn't accessible to use for a Docker mount. We rely on this to mount some config files for the docker-compose.yml inside fides deploy so this results in mysterious errors like:
Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /opt/homebrew/lib/python3.10/site-packages/fides/data/sample_project/privacy_center/config

This doesn't really fix that issue - a real fix would likely be to not mount from the lib folder at all (and instead make a local copy of the necessary config files in the directory where fides deploy is invoked), but it at least triggers a warning that will let a savvy user notice the issue and recommend they use a venv instead.
Another common problem is  we think we're calling the fides CLI from within a venv, but due to mysterious-reasons-I-cannot-justify it appears that the venv/bin folder is given a lower precedence in the PATH than globally installed Python packages... which means that when you install things in the venv thinking they'll be used, often you end up calling into a globally installed package instead! This warning will also trigger when that happens, so that you can fight with your local shell and do something like:

uninstall the global fides CLI to avoid the footgun
force the venv to be used like ./venv/bin/fides

Ah, interesting - my secret, hidden reason for this PR was to also tinker with the codecov reporting. This exposes that the fides deploy CLI command itself doesn't get covered in our codecov reports, which is why my patch coverage here is only 92%.
I happen to "know" we run that command in a special check ("CLI Command Checks / Fides-Deploy (pull_request)") but it's interesting to see it flagged here as a failing patch. I like that 😄


Get an text when a new eBay item is listed for a specific search

Hi,
I am looking to hire a developer to customize the Huginn script to achieve the following task for me in real time:
Send me a text message when a new eBay item is listed for a specific search item that is listed at a price which is blow my set max price.
I tried using IFTTT for this and although it worked, it has 2 main issues that cannot be overcome with that system.

The results are usually 15-20 minutes (or more) late.
IFTTT as a monthly quota of 100 text messages.

We can integrate Twilio or any other suggested third party sms gateway service. Please contact me if interested.
Thanks!

Hi @Rizonline,
this sounds like an interesting problem so solve. I added the contractor wanted label. I hope that helps to find someone to help. Apart from the agent configuration I recommend reducing DELAYED_JOB_SLEEP_DELAY to something lower then 10 seconds to make huginn feel more "real time".

Hi @dsander,
Perhaps you can do it for me...are you available?
Thanks!

Website agent for parsing ebay, you just need to add Email or Pushbullet agent
{
  "expected_update_period_in_days": "2",
  "url": "http://www.ebay.com/sch/i.html?_from=R40&_trksid=p2050601.m570.l1313.TR0.TRC0.H0.Xpraq+300.TRS0&_nkw=praq+300&_sacat=0",
  "type": "html",
  "mode": "on_change",
  "extract": {
    "title": {
      "xpath": "//*[contains(concat( \" \", @class, \" \" ), concat( \" \", \"vip\", \" \" ))]",
      "value": ".//text()"
    },
    "price": {
      "xpath": "//*[contains(concat( \" \", @class, \" \" ), concat( \" \", \"prc\", \" \" ))]//*[contains(concat( \" \", @class, \" \" ), concat( \" \", \"bold\", \" \" ))]",
      "value": "translate(., translate(.,'0123456789,.',''), '')"
    },
    "url": {
      "xpath": "//*[contains(concat( \" \", @class, \" \" ), concat( \" \", \"prc\", \" \" ))]//*[contains(concat( \" \", @class, \" \" ), concat( \" \", \"bold\", \" \" ))]",
      "value": ".//@href"
    }
  }
}

Thanks @gdomod!


Can't pull image from private repo gcr.io/heptio-images/velero:latest

What steps did you take and what happened:
I don't have access to pull an image for deployment.  It states I need authorization. for image: gcr.io/heptio-images/velero:latest
What did you expect to happen:
I expected to be able to pull the image.  I am still able to pull the ark image from the gcr repo.
The output of the following commands will help us better understand what's going on:
Success
docker pull gcr.io/heptio-images/ark:latest
Trying to pull repository gcr.io/heptio-images/ark ...
latest: Pulling from gcr.io/heptio-images/ark
cd784148e348: Pull complete
fc1bcc5dfa51: Pull complete
be845fffd0a4: Pull complete
84cfeeaf260e: Pull complete
Digest: sha256:97e96915c32af1d382bbb1a56d00cf7e53e5f55839f841af25160b8179782c39
Status: Downloaded newer image for gcr.io/heptio-images/ark:latest

Failure
docker pull gcr.io/heptio-images/velero:latest
Trying to pull repository gcr.io/heptio-images/velero ...
Pulling repository gcr.io/heptio-images/velero
unauthorized: authentication required

The velero image is still not used yet. It will be used in the v0.11.0
As now, it is still being referenced as ark (at least for the latest version v0.10.1).

@nzoueidi When is v0.10.1 coming out? I've installed velero server but the client is not compatible with the velero server. I am running the following command and it's looking for the old ark.heptio.com api rather than velero.io. How can I fix this? Can I change the config somewhere in the client?
[~] velero get backup-locations

An error occurred: the server could not find the requested resource (get backupstoragelocations.ark.heptio.com)

@hhuang1illumina the v0.10.1 is already out (https://github.com/heptio/velero/releases).
You may want to take a look also at the getting started page : https://heptio.github.io/velero/v0.10.0/get-started.html
If you are still facing the same issue even after picking the right version. Please file up a separated issue.

@skriss I am using v0.10.1 tarball and you are correct that it's still ark binary while everything else in git is changed to velero, so nothing is going to work because of this client and server discrepancy.

@hhuang1illumina please see all of the sample YAML files in the release tarball, under config/.  Also please use the versioned docs: https://heptio.github.io/velero/v0.10.0/

@skriss Yes, I realize I can still use the config folder to make ark work. But I can't make velero work at this point with everything that is available on the git website. And it's very confusing for new users is all I am saying.

We've released v0.11 which completes the rename. Closing this issue as it should be addressed, but please open a new issue if you encounter any further issues.


fix: Fixed the gear icon positioning in frontend

fix: Added height, left and right padding in settings-dropdown-cog
present in zulip.scss.
Fixes #15222

Testing Plan:
./tools/test-all
GIFs or Screenshots:
Web:

IPad Pro:

iPhone 6:

iPhone SE:

Moto G4:

Nexus 10:

Thanks for working on this, @sahil9001. It would be a good idea to add screenshots and/or GIFs related to the changes. That makes it easier for others to review your work.
Also, on a side note, I think it'd be a good idea if you went through our version control guide to get a better idea of how Zulip commit messages are written. :)

Thanks for working on this, @sahil9001. It would be a good idea to add screenshots and/or GIFs related to the changes. That makes it easier for others to review your work.
Also, on a side note, I think it'd be a good idea if you went through our version control guide to get a better idea of how Zulip commit messages are written. :)

I've added screenshot related to changes.

@timabbott @showell

@sahil9001 can you also add screenshots for mobile sizes?
And I agree with Vinit, you should read our commit messages guide and rewrite the commit message with git commit --amend to answer the obvious questions one might have with this change (E.g. why are the paddings different on the two sides, and why do we need the height element)?
My guess is this fix is the wrong solution and at least some of that logic is overriding other CSS that we should be deleting instead.  @YashRE42 FYI.

I'm not sure there's a strong reason to keep the absolute here either... but I didn't look too deeply into it, so, pinch of salt.

@sahil9001 can you also add screenshots for mobile sizes?
And I agree with Vinit, you should read our commit messages guide and rewrite the commit message with git commit --amend to answer the obvious questions one might have with this change (E.g. why are the paddings different on the two sides, and why do we need the height element)?
My guess is this fix is the wrong solution and at least some of that logic is overriding other CSS that we should be deleting instead. @YashRE42 FYI.

I guess making paddings same on both sides shifted the gear icon to the right which seemed odd, although I've added height to make the the button fit in the rectangle.

The web screenshot looks off; while is there a blank space above the blue region in those top two screenshots?

The web screenshot looks off; while is there a blank space above the blue region in those top two screenshots?

Yes, the first one is the web screenshot, there is a blank space on top because I don't really know how to fill it, I tried using height property but it filled out blank space on bottom.

Well, I don't think we can merge this while the behavior is buggy, so I encourage you to figure out how to do that correctly and revise your changes.

Well, I don't think we can merge this while the behavior is buggy, so I encourage you to figure out how to do that correctly and revise your changes.

Ok I'll fix that and let you know.

I think you'll find your approach improving if you focus on removing the need to have pos: absolute and related properties (top, right, bottom, left)

I think you'll find your approach improving if you focus on removing the need to have pos: absolute and related properties (top, right, bottom, left)

You mean to use that property in settings-dropdown-cog?

see this block under #navbar-buttons
        .dropdown-toggle,
        li.active .dropdown-toggle {
            font-size: 20px;
            color: inherit;
            opacity: 0.5;
            text-shadow: none;
            padding-left: 0px !important;
            background-color: inherit;
            box-shadow: inherit;
            display: block;
            position: absolute;
            right: 0px;
            top: 3px;
        }

Hey @sahil9001, thanks for reaching out to me on CZO, I realize now that you're trying to fix the click area and not the margin, please keep that in mind when rewriting the title.
I'm replying here so that everyone is on the same page and in case someone else can benefit from reading through this.
so, before making any changes, if you open up the chrome inspector and you look at this element (at min-width > 1180px) you'll notice that it has both a small margin and a padding. The padding will count into the click area and the margin won't. The padding comes from Zulip.scss around line 550, the margin comes from actual-dropdown-menu, Zulip.scss around line 543.

Then at max-width <= 1165px
we have a media query that puts a different padding on settings-dropdown-cog, Zulip.scss around line 2546. You'll want to look into making sure those margins and paddings are okay.
You'll also want to keep in mind that the actual click target is settings-dropdown which has the class dropdown-toggle and contains settings-dropdown-cog.
Note that: dropdown-toggle lies within actual-dropdown-menu which lies within #navbar-buttons.
#navbar-buttons has a margin-top: 7px, Zulip.scss around line 1768 which is probably the cause of that weird region you're getting above the click area in that ipad view.
I hope this is enough to at least get you started.
Play around with the inspector to verify your changes are correct, the styles here might feel annoying but it looks like it'll be fun to make things right :).
(and you can ping me if you need to)

@YashRE42 Thanks for the help! I'll solve this soon.

@YashRE42 @timabbott I've fixed the commit message and the click area positioning in the commit starting with 668f284.

@YashRE42 @timabbott I've fixed the commit message and the click area positioning in the commit starting with 668f284.

This issue this was for was resolved via https://github.com/zulip/zulip/pull/15513. Thanks for your effort on this @sahil9001.


Make Trending Optional

I love this extension, however, the main thing that annoys me about it is that it removes "Trending" without an option to re-enable it.

Good point @brian6932! Will consider tackling this in a future release.
In the meantime, check out @jh3y's extension for more options: https://github.com/jh3y/focussed-twitter


Ability to sort plugins

This might become irrelevant if move/rearrange functionality is available (see #158), but maybe there's a quick and easy way to sort plugins, so they appear in a certain order in the menu bar, whether together as a bunch or (in a later version) separated. I know, it's easy to do by simply renaming the basenames, but sometimes (e.g. with plugin distributions to other users/customers) this is not an option. Therefore my suggestion to add an option (a window) in Preferences, which shows a list of the active plugins, and where the user can just rearrange the order by dragging them up/down the list.

I wonder how this will work in macOS Sierra: http://9to5mac.com/2016/06/18/macos-sierra-rearrange-third-party-menu-bar-icons/

You already have a similar functionality when you install Bartender. But with the Bartender setup you can only move around BitBar plugins en bloc. (Except for the LittleSnitch Monitor, which is strange.) Maybe Sierra will be more intelligent, and you'll be able to move every BitBar plugin individually… we'll see. :)

Has anyone tried this in the macOS 10.12 beta?

It seems to work correctly in Sierra. However, a plugin's position seems to reset if its output is empty.

This looks like a duplicate of #158.

+1
Currently I can reposition my plugins, but only temporarily as they reset their position on refresh.

So I figured out a workaround to this. If you go to the plugins folder, and prefix the plugin files with a number in the order you want them in reverse order it will follow that order regardless of how many times you refresh or reboot.
For example:
1_ColorfulBatteryLevel.5s.sh
2_wifi.15s.sh
3_itunes.10s.sh
4_sonos.3s.sh

Hope this helps!

This only works if none of your plugins ever disappear. I have several plugins which don't produce any output at all under certain conditions (e.g. no new <insert website here> notifications, or battery level above 70%), and these will be added to the left end of the bar, instead of the expected position, when they generate output for the first time after starting or refreshing BitBar.

This still doesn't work #sad

The naming trick doesn't even seem to work for me? Can anyone confirm that it still works for them? Otherwise at the very least, wouldn't the plugins be sorted alphabetically by their filenames, if you don't number them? Which in my case, doesn't seem to be what's happening, anyway.

See code change in #502


Automated cherry pick of #7588: fix: dns record create ignore is_public field

Cherry pick of #7588 on release/3.2.
#7588: fix: dns record create ignore is_public field

/lgtm
/approve


Add re-usable test helpers

Provides:
replaceAppRef(app, ref, [model])

Replaces the app's adapter with your supplied Firebase ref, defaults to replacing the application adapter but you could supply a model here if you have mixed adapters in your app and need to override only a certain model's adapter

You should probably use MockFirebase if you are only needing basic set/update/remove functionality. Queries will need a offline+stubbed reference.
var app, ref;
beforeEach(function () {
  ref = new MockFirebase('https://some-url');
  app = startApp();
  replaceAppRef(app, ref);
});

stubFirebase() / unstubFirebase()

Needed to stub offline refs so that set, update and remove operations fire their callbacks and complete the wrapping promises
Only needed if you are using offline refs, you should probably use MockFirebase unless you need complex things like queries

createOfflineRef([initialData], [url])

Creates a reference in offline mode with optional data. You must run stubFirebase() before this
The url defaults to https://emberfire-tests.firebaseio.com unless specified

stubFirebase();
var ref = createOfflineRef({
  posts: {
    post_1: {
      title: 'Title'
    }
  }
}, 'https://my-cool-app-tests.firebaseio.com');

ref.toString(); // https://my-cool-app-tests.firebaseio.com/

ref.child('posts/post_1').once('value', function(snap) {
  console.log(snap.val()); // { title: 'Title' }
});
unstubFirebase();

Full Example:
import createOfflineRef from '../helpers/create-offline-ref';
import replaceAppRef from '../helpers/replace-app-ref';
import stubFirebase from '../helpers/stub-firebase';
import unstubFirebase from '../helpers/unstub-firebase';

import FIXTURE_DATA from '../helpers/fixture-data'; // defined in your local repo

describe('Acceptance: /post/:id', function() {
  var application, ref;

  beforeEach(function() {
    stubFirebase();
    application = startApp();
    ref = createOfflineRef(FIXTURE_DATA);

    replaceAppRef(application, ref);
  });

  afterEach(function() {
    unstubFirebase();
    Ember.run(application, 'destroy');
  });

  it('can visit /post/post_1', function() {
    visit('/post/post_1');
    andThen(function() {
      expect(find('.post .title').text().trim()).to.equal('Title');
    });
    andThen(function() {
      ref.child('posts/post_1/title').set('Title Updated');
    });
    andThen(function() {
      expect(find('.post .title').text().trim()).to.equal('Title Updated');
    });
  });

});

Please make any suggestions if the helper names or apis can be clearer.
Fixes #251
/cc @brancusi @aceofspades @edborden @scolyer

This looks great @tstirrat . Exactly what I need. I am currently doing this by injecting a replacement firebase service into emberfire. It works ok but isn't as nice as this.

Should we call them (un)stubFirebaseOffline so that it is clear these methods are only needed if you're using the offline refs?

Some others who are interested in EmberFire testing and might want to comment on the methods suggested here:
/cc @gabrielgrant @mtmckenna @RayMangum @leifcr

@tstirrat Thanks for working on this! It's a really needed feature. I just tried this branch on a project I have with emberfire but had the following error:
not ok 1 PhantomJS 1.9 - TestLoader Failures: dummy/tests/acceptance/dummy-test: could not be loaded
    ---
        actual: >
            null
        message: >
            Died on test #1     at test (http://localhost:7357/assets/test-support.js:3183)
                at http://localhost:7357/assets/test-support.js:6175
                at http://localhost:7357/assets/test-loader.js:62
                at http://localhost:7357/assets/test-loader.js:51
                at http://localhost:7357/assets/test-loader.js:82
                at http://localhost:7357/assets/test-support.js:6182: Could not find module `sinon` imported from `dummy/tests/helpers/stub-firebase`

I think the problem with this implementation is that it depends on sinon (sinon shim) which is not available to end users (see this). Would you consider changing the implementation to avoid using sinon?

@san650 good catch! I will see what I can do!

I did a quick test and removed sinon and the acceptance tests worked! You can see the changes I made here https://github.com/san650/emberfire/commit/7638f764a2a47c1f3aa5d7d30cba4e95f0ef2dd1 (quick and dirty hack :stuck_out_tongue:)

@san650 I updated this branch with 63856aa that should fix the sinon issue.

@tstirrat Thanks for the update!
It's still failing, I think you forgot to remove the import sinon statement from https://github.com/firebase/emberfire/blob/63856aa5abb73f365e19fbb16ab9d0688530f1b8/test-support/helpers/stub-firebase.js#L2

LOL, yep. will fix that.

@tstirrat now it's working

@san650 @tstirrat Awesome guys, thanks!

whoa, not sure how i overlooked this in my GH notifications... this is awesome @tstirrat
After a series a frustrations with mocking/stubbing and FirebaseServer, I've ended up just using a real firebase instance for testing (by just subbing out the URL in my config). This obviously gets rid of the annoying, subtle differences between test and live environments, but requires maintaining a bunch of extra code to set/inspect state, causes multiple test instances to interfere with each other, makes the tests run super slow...and just feels wrong. So looking forward to giving this a try.
Haven't seen any docs on this...would be great to get a testing guide (in all your free time ;)

@gabrielgrant @binhums and I sat down yesterday to get a guide going on this very topic :)

@tstirrat awesome, looking forward to seeing it!


Remove unnecessary field in proto

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

Coverage decreased (-0.05%) to 56.582% when pulling 83f06c694e8495d2219ff58042eb35bb4efa8511 on leonwanghui:attach-dock into 7f2140dbfc5bbfcb73e32d7d8032653c6c5671d8 on opensds:development.


multiple select component bug

when I select some options and then reset the form,I found the select component still shows options before selected

related #114


Selectors to improve performance for listing channels

Summary
In order to increase the performance unnecessary re-renders I've created other types of selectors that the regular createSelector those are:

createIdsSelector this on is used to shallow compare all the arguments and memoize the result, try and use it only when the selector returns an array of ids.
createShallowSelector shallow compare all the arguments but does not memoize the result.
createDeepSelector use it when you need to deep compare all the arguments, this one won't memoize the result.

Also I've created a few selectors that make use of the above creators to get sorted team Ids, different type of channels, mentions count, teams count, etc..
Ticket Link
https://mattermost.atlassian.net/browse/RN-415
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] Added or updated unit tests (required for all new features)

@hmhealey changes made

@jwilander fixed the comments


Don't send requests for NWAC weather when loading other centers

Unclear why we do this, can use enabled field on the react query call to disable.

Fixed in https://github.com/NWACus/avy/pull/618


Custom component event @change same as @change.native?

Version
3.0.5
Reproduction link
https://stackblitz.com/edit/vue-qfisdz?file=src%2FApp.vue
Steps to reproduce
Add @change to my custom Input Component, and my component didn't $emit('change'), it should not be triggered, but @change is same as @change.native, it trigger like native
What is expected?
@change should not be triggered
What is actually happening?
@change triggered just same as @change.native

Is it a feature? because in vue2, if i do not handle event, It should not be triggered, but in vue3, @change same as @change.native

See https://v3.vuejs.org/guide/component-attrs.html#attribute-inheritance

See https://v3.vuejs.org/guide/component-attrs.html#attribute-inheritance

See https://v3.vuejs.org/guide/component-attrs.html#attribute-inheritance

Thanks for reply, That would be great, We don't have to duplicate redeclare props from other component

See https://v3.vuejs.org/guide/component-attrs.html#attribute-inheritance

Thanks for reply, That would be great, We don't have to duplicate redeclare props from other component


Changing aspectRatio parse from int to float

This allows usage of more common aspect ratios like 1.77 (16:9) and 1.33 (4:3)
Currently parseInt strips the decimals from the passed aspectRatio

the compile still needs ran here. I just wanted to get this fix available for anyone else possibly banging their head against the wall trying to figure out why their aspect ratios were unexpectedly skinny.


Update image resources for mentors and speakers page [WIP]

What
Replace images of speakers with the right ones.
Pending
Reference the new resources in the sections that are used.

Yo, mate, you change png namepath withoud modifying .json "images" value, I'm hella mad.
No, just kidding. Let me finish with some home work, and then I'll finish this PR.
Thank you for everything.


Add a link to the article

Thanks for that article by the way. It's a very good intro to playing with gRPC in Go.

Thanks @pzurek.
I was meaning to add the link after it was published, thanks for the reminder!


Fix redis deprecation warnings

This PR fixes deprecation warnings of redis:
(called from /home/blackst0ne/.asdf/installs/ruby/2.7.5/lib/ruby/gems/2.7.0/gems/sidekiq-status-2.1.2/lib/sidekiq-status/storage.rb:16:in `block in store_for_id'}
.....................................Pipelining commands on a Redis instance is deprecated and will be removed in Redis 5.0.0.

redis.pipelined do
  redis.get("key")
end

should be replaced by

redis.pipelined do |pipeline|
  pipeline.get("key")
end

@kenaniah can you review, please?

Thank you for the PR @blackst0ne. This has been released in v2.1.3


Better error handling when a newly added class couldn't be compiled

What needs to be done
Provide better handling in JavaSourceSetImpl when adding a JavaSource which doesn't compile.
List<J.CompilationUnit> compilationUnits = javaParser.parse(sourceCode);
        J.CompilationUnit parsedCompilationUnit = compilationUnits.get(0);

Verify that compilationUnits is not empty/null
Why it needs to be done
The error message when compilationUnits is empty, because compilation failed)

Acceptance Criteria
/info panel
Given a user adds a new Java source file through JavaSourceSetImpl
When the source code doesn't compile and the list of compilation units is empty
Then the stacktrace should provide more precise information about what went wrong
Additional Information

@sanagaraj-pivotal ☝


New variable time constraint with time inequality

@paulWegiel
Can you confirm it is done by the #126 PR?

Exactly, it is resolved since #126 PR !

Done!


HTTP/3

Describe the problem

https://github.com/square/okhttp/issues/907

OkHttp may never support HTTP/3 and suggested using an interceptor.
Describe the solution you'd like

https://github.com/google/cronet-transport-for-okhttp

Describe alternatives you've considered

Additional context

Hi @UjuiUjuMandan! Thanks for this suggestion.
I'd be happy to review a PR that adds HTTP/3 using that Cronet transport, as long as we continue to use ktor. I suppose it'd have to configure the OkHTTP client used by Ktor, which I'm not sure would be possible or easy.
Alternatively, if you can find an alternative ktor engine that works on desktop and Android 8+, I'd be happy to consider it, since ktor itself won't support HTTP/3 any time soon by the looks of it:

https://slack-chats.kotlinlang.org/t/16907912/is-there-any-further-plan-for-ktor-to-support-http3-or-any-o
https://youtrack.jetbrains.com/issue/KTOR-6008/Support-QUIC-protocol


[repl] scroll wheel doesn't work (windows)

Also happens with runtime. Hopefully it's just some windows mode flag


Basic CLI testing capabilities

will take a swing at it since I need it soon-ish

@MykolaGolubyev shall we close this one now?

Yeah. Thanks. Closing.


Integrate Angular 8 lazyload loadchildren import

Angular 8 introduces a new way to use loadchildren, see https://github.com/angular/angular/commit/c61df39.
This change allows the lazyloadChildren endpoint to use Angular 8 way of importing as well.
Description
This change allows the lazyloadChildren endpoint to use Angular 8 way of importing as well.
e.g.:
loadChildren: () => import('./lazy-route/lazy.module').then(mod => mod.LazyModule),
Motivation
This removes the need of the magic string and offers significant advantages in terms of:

type checking via TypeScript
simplicity of generated code
future potential to run natively in supporting browsers
(see: caniuse: dynamic import())

How Has This Been Tested?
Integrated this change succesfully in our code
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have read the Contributing guide.
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.

Closed due to dependancy on Angular 8 upgrade with aot and ivy compiler. See https://blog.angularindepth.com/automatically-upgrade-lazy-loaded-angular-modules-for-ivy-e760872e6084#9ccf


Update screenshot for sign-on option in AD Connect

Passthrough authentication and seamless SSO are generally available and no longer in Preview, updating screenshots to reflect the same.

@billmath

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

image updates need to be done on my end and in the private repo.  I will handle this on my end.  Thanks!
#Please-close


fix footer links

Pull Request Template

Please provide all of the details below. Pull requests missing any of the information below will be closed!
Providing the issue number/url helps us identify the problem being solved and keep the issues tab clean and tidy

This is not a fix. This is a request to add login and signup pages to the site.
Summarize what this PR fixes:- Fix the footer links that are broken
Fixes #510
Checklist
(Add an x between the brackets to check the items)

[x ] I have summarize what this PR fixes above
[x ] I have provided the issue ID/URL above
[ x] I have not added Bootstrap or jQuery and used correct styling guide.
[x ] This PR fixes only the issue mentioned above (create separate PRs for separate issues)
[x ] I was the first one to claim the issue or I created the issue - I created the issue

@Agilulfe something is wrong with the index.html in your pull request. The pricing and meet the team section have been merged and duplicated I think. See below, please fix and resubmit.


Please refrain from using scripts for now due to changes in bot detection methods to avoid any issues!

Hi, What if I will directly access here in the browser do they detect my autoclicker?

@nobiskriper If the number of clicks you make is high and sent towards the server with a high amount, yes. Otherwise, it is unlikely.

NEW UPDATE

The attempt was made to have the headers change automatically.
After each Tap, a natural time delay was inserted.

Our goal is to make the script undetectable! As much as possible. 😏
However, keep in mind that the script can still be detectable! Proceed at your own risk. ⚠

@THMaST3R app.py

Does the script pick a random spot on the screen to tap?

@BraveCanister Such thing doesn't matter. There is no such thing in the script. Only the total number of clicks and the intervals between clicks and request headers matter.

I recommend all of you to use this project!
https://github.com/Poryaei/All-In-One


Redirect non-www to www subdomain

We will launch a product soon and decided to enforce the www subdomain and 301 redirect from the non-www version of it.
In Nginx this would look like the below but how do I achieve the first server-block with RAP?
server {
    listen               80;
    listen               443 ssl;
    server_name         example.com;
    ssl_certificate      path/to/cert;
    ssl_certificate_key  path/to/key;

    return 301 $scheme://example.com$request_uri;
}

server {
    listen               80;
    listen               443 ssl;
    server_name          www.example.com;
    ssl_certificate      path/to/cert;
    ssl_certificate_key  path/to/key;

    # RAP generated stuff...
}

Hi Ali,
why are you trying to do the redirect with RAP?
Usually the webserver serving the website(s) does the redirect to the URL preferred.
RAP takes care that you have valid SAN SSL certificates for all hostname combinations valid for access.

For my project RAP proxies to an Express webserver.
Of course it could do the routing but Nginx is much faster at this. I also don't want to put another Nginx after RAP because IMO that is kinda pointless.

Hello @dj-hedgehog ,
I just push a new version v0.9.0 ( should be building right now ) that enable _server configuration .
This enable you to manually set the server block for a given vhost !
Do not hesitate to test if everything is working as expected !


Inconsistent ability to build cargo on OS X

Issue #2295 reported a link error on OS X due to OpenSSL being installed by brew. The fix is to define the following variables:
export OPENSSL_ROOT_DIR=$(brew --prefix openssl)
export OPENSSL_LIB_DIR=$(brew --prefix openssl)"/lib"
export OPENSSL_INCLUDE_DIR=$(brew --prefix openssl)"/include"

However, even this gives spotty results. I find that with these variables defined, I still get link errors to openssl symbols maybe 4/5 times. And sometimes it works.
The link errors are:
  = note: Undefined symbols for architecture x86_64:
  "_EVP_aes_256_ctr", referenced from:
      _libssh2_crypt_method_aes256_ctr in liblibssh2_sys-5b58702936280067.rlib(crypt.c.o)
     (maybe you meant: __libssh2_EVP_aes_256_ctr)
  "_EVP_aes_192_ctr", referenced from:
      _libssh2_crypt_method_aes192_ctr in liblibssh2_sys-5b58702936280067.rlib(crypt.c.o)
     (maybe you meant: __libssh2_EVP_aes_192_ctr)
  "_EVP_aes_128_ctr", referenced from:
      _libssh2_crypt_method_aes128_ctr in liblibssh2_sys-5b58702936280067.rlib(crypt.c.o)
     (maybe you meant: __libssh2_EVP_aes_128_ctr)
ld: symbol(s) not found for architecture x86_64

$ uname -a
Darwin myhostname 15.6.0 Darwin Kernel Version 15.6.0: Thu Jun 23 18:25:34 PDT 2016; root:xnu-3248.60.10~1/RELEASE_X86_64 x86_64
$ brew info openssl| head -1
openssl: stable 1.0.2h (bottled) [keg-only]

To clarify, you cleaned out the build directory after setting the environment variables, right?

Yes, when I begin working on #1747, I clean the directory and then run source env.sh where env.sh contains the appropriate exports.  Then sometimes it builds and sometimes it fails. I end up just repeatedly building until it links.

Log of failed build: http://sprunge.us/YRiQ
Repeated builds can succeed: http://sprunge.us/BUdd
This works/fails with stable and nightly.

It looks like this may be because "-L" "/usr/lib" is getting passed to the linker before "-L" "/usr/local/opt/openssl/lib" which is where OpenSSL is. That typically comes up when pkg-config gets overzealous and finds libs in that directory.
I'm not sure what build script would be asking for linkage to that directory, though? Could you try digging around in target/debug/*/output to see which build script is asking for that?

Looks like libz may be the culprit.
$ fgrep '/usr/lib' target/debug/build/*/output
target/debug/build/libgit2-sys-7e806e051f3bd634/output:-- Found ZLIB: /usr/lib/libz.dylib (found version "1.2.5")
target/debug/build/libgit2-sys-7e806e051f3bd634/output:-- Found Iconv: -L/usr/lib -liconv
target/debug/build/libssh2-sys-a1010066147c936a/output:-- Found ZLIB: /usr/lib/libz.dylib (found version "1.2.5")
target/debug/build/libz-sys-b246b9f3989628d7/output:cargo:rustc-link-search=native=/usr/lib

$ cat target/debug/build/libz-sys-b246b9f3989628d7/output
cargo:rustc-link-search=native=/usr/lib
cargo:rustc-link-lib=z

The build script for libz-sys doesn't ever print only those two options, so I'm intrigued how this works.

That's probably printed by pkg-config. The script for libz-sys probably shouldn't run pkg-config at all on OSX :(

The script for libz-sys probably shouldn't run pkg-config at all on OSX :(

I'm not sure. It exists in brew and can be used to find things like libreadline, etc. But OS X has a tonne of packaging headaches for other systems. e.g. Python. OpenSSL is another place where OS X is all screwy.
Either way, I think the main issue here is that the build is not deterministic. If that can be solved, then we can figure out a shim environment to setup so builds can work reliably.

Ok, I've pushed https://github.com/alexcrichton/libz-sys/commit/043a4cd1dab66e49a44d120d6e8323f23e853325. @ehiggs could you try that out?

I added the following to my cargo/Cargo.toml:
[replace]
"libz-sys:1.0.5" = {git = "https://github.com/alexcrichton/libz-sys" }

I can no longer to get the build to break even if I don't have the environment variables set. This is probably because /usr/lib is no longer on the link line at all. So this fix was even better than expected! :tada: :tada: :tada:
Thanks!


Feature: Incremental camera control values

Firstly, thanks for the camera control implementation.
I'm looking to increment some of the values rather than define a fixed value e.g. increasing/decreasing the camera gain.
I've attempted to use variable expressions as described here but it looks like the module doesn't support that yet?

I'm not sure that using expressions is the ideal solution anyway as it could result in values above or below the allowed range at which point the below error occurs:
warn Instance/Wrapper/atem Error executing action: The value of "value" is out of range. It must be >= -128 and <= 127. Received 130

How would you feel about a separate action (or expanding the existing ones) to increment the values up/down?
I've been experimenting on a fork and initially would look to replicate across:

Video Gain
Video Exposure
Lens Iris

Fork here: https://github.com/bitfocus/companion-module-bmd-atem/compare/main...NoahCallaway:companion-module-bmd-atem:main
Any feedback, suggestions and ideas are welcome!

I'm trying just now to do something simiilar.
It seems that value is a stirng, and not a number, so, just as example assume that the value of the variable il "2", the expression
?(atem:camera_1_gain) returns "2" and adding the string "10" set the new value to "210" and not  the number 12.
Isn't that?
In case, is there a way to convert the returned value "2", convert it to the number 2, add avalue and then convert it again to a string to pass as to the method to set a new value?

I've got it working with a dedicated action now:
https://github.com/bitfocus/companion-module-bmd-atem/assets/24882928/cd9dbea8-bd3e-440b-afbd-da0e355b2791
Will raise a PR to implement this and some other actions.

I'm looking for a way to increment the IRIS value, but as far as I know, at the moment there is no way to do that.
Am I wrong?

@vbMizio - there is no way to do that at the moment.
I've included the functionality in my PR #293. Just waiting for a review/feedback.

@NoahCallaway
Thank you Noah, we have to wait.

This will be in the betas shortly

Thank you @Julusian

@vbMizio - I found some issues with the initial implementation which you'll probably hit too.
Have resolved them in #297

@NoahCallaway Thank you Noah


[PF 03] Adjust job assigning to include pigeon performance information

We want to assign jobs to pigeons based on several weighted features.  The groundwork for this should already be done, and the data should be tracked.  Now, it's time to add it into the weighting system

The pigeon's message uptake rate
The pigeon's message delivery success rate
The pigeon's message delivery speed
Active MEV Endpoint * (Mev endpoint setting)
Active tx type: 2 set* (eip 1559 for lower gas)

More info can be found in the epic: More info can be found in the Epic: https://www.notion.so/volumefi/EPIC-09-26-22-Paloma-Gas-Management-78319280833e4c7c8ffad368eddb1d91

⏰ Estimate
1 - 2 days

@byte-bandit and to confirm, we include Pigeon Relay Fee as one of the factors to adjust the assignment. Yes?

@taariq Correct. We still have to push out PF02 for this to take effect, but that should be a straight forward change. After that, the only large piece of engineering left is tracking the fees and collecting them, which still has some question marks on it.


DynamicExpression parser can't parse when there is a dot in a string

1. Description
I need to parse a condition that checks that the Name of an entity is "System.Int32" , but because of the dot, I get an error. Could you see why is that happening please? It seems to me that it's a very simple situation.
2. Exception
Unhandled exception. '.' or '(' or string literal expected (at index 19)
3. Fiddle
https://dotnetfiddle.net/hdL13r

You mean :
"Name=\"System.Int32\""

?

Yes, this part "System.Int32"  is a string token and should not be interpreted by the interpretor.

What do you mean by string token?
The whole purpose from this library is to allow dynamic querying using a string expression, like:
var resultDynamic = context.Customers
     .Where("City == \"Paris\"")
    .ToList();

https://dynamic-linq.net/basic-simple-query

The string token is "System.Int32" .
For example, this code should work:
var resultDynamic = context.Customers
.Where("City == "System.Int32"")
.ToList();
"Paris" is a string token, and the interpretor should not try to understand what is "inside" the string. Like "1/0" should not be a problem but 1/0 will raise an exception, anything inside a string should not be considered by the interpretor. I don't see any usecase where intepreting inside a string is useful ( and that's not string interpolation )

It will be fixed in next release.
https://github.com/zzzprojects/System.Linq.Dynamic.Core/pull/687

Great, thanks a lot!


Add theme: Collapsed Tab X Button

Add theme: Collapsed Tab X Button
This PR adds a new theme to the theme library.
Theme Details

Name: Collapsed Tab X Button
Description: This theme adds a close button to the collapsed tabs in Zen Browser.
Homepage: https://github.com/burnt0rice/zen-themes/tree/main/collapsed-tab-close-button
Author: @burnt0rice

Really cool!

Thanks!


TextEditingController in a Provider used after being disposed

Describe the bug
Trying to use TextEditingController in a Provider. When I use it with .autoDispose it throws an error. Without it, works fine but can't dispose it.
In my app, I need to edit the TextEditingController from other Providers. I don't know if this is the best practice here. I'm having a hard time working on form fields with RiverPod.
To Reproduce
Sample app
class Home extends ConsumerWidget {
  const Home({Key? key}) : super(key: key);

  static final textController = Provider.autoDispose<TextEditingController>((ref) {
    final controller = TextEditingController();

    ref.onDispose(() {
      controller.dispose();
    });

    return controller;
  });

  @override
  Widget build(BuildContext context, WidgetRef ref) {
    return Scaffold(
      body: Center(
        child: Column(
          mainAxisSize: MainAxisSize.min,
          children: [
            TextField(
              controller: ref.read(textController),
            ),
            ElevatedButton(
              onPressed: () {},
              child: const Text('Click me'),
            ),
          ],
        ),
      ),
    );
  }
}

Exception
════════ Exception caught by gesture ═══════════════════════════════════════════
The following assertion was thrown while handling a gesture:
A TextEditingController was used after being disposed.

Once you have called dispose() on a TextEditingController, it can no longer be used.
When the exception was thrown, this was the stack
#0      ChangeNotifier._debugAssertNotDisposed.<anonymous closure>
package:flutter/…/foundation/change_notifier.dart:114
#1      ChangeNotifier._debugAssertNotDisposed
package:flutter/…/foundation/change_notifier.dart:120
#2      ChangeNotifier.notifyListeners
package:flutter/…/foundation/change_notifier.dart:288
#3      ValueNotifier.value=
package:flutter/…/foundation/change_notifier.dart:412
#4      TextEditingController.value=
package:flutter/…/widgets/editable_text.dart:186
#5      EditableTextState._value=
package:flutter/…/widgets/editable_text.dart:1988
#6      EditableTextState._formatAndSetValue
package:flutter/…/widgets/editable_text.dart:2310
#7      EditableTextState.userUpdateTextEditingValue
package:flutter/…/widgets/editable_text.dart:2532
#8      RenderEditable._setTextEditingValue
package:flutter/…/rendering/editable.dart:597
#9      RenderEditable._setSelection
package:flutter/…/rendering/editable.dart:617
#10     RenderEditable.selectPositionAt
package:flutter/…/rendering/editable.dart:3405
#11     RenderEditable.selectPosition
package:flutter/…/rendering/editable.dart:3381
#12     _TextFieldSelectionGestureDetectorBuilder.onSingleTapUp
package:flutter/…/material/text_field.dart:112
#13     _TextSelectionGestureDetectorState._handleTapUp
package:flutter/…/widgets/text_selection.dart:1471
#14     TapGestureRecognizer.handleTapUp.<anonymous closure>
package:flutter/…/gestures/tap.dart:606
#15     GestureRecognizer.invokeCallback
package:flutter/…/gestures/recognizer.dart:193
#16     TapGestureRecognizer.handleTapUp
package:flutter/…/gestures/tap.dart:606
#17     BaseTapGestureRecognizer._checkUp
package:flutter/…/gestures/tap.dart:296
#18     BaseTapGestureRecognizer.acceptGesture
package:flutter/…/gestures/tap.dart:267
#19     GestureArenaManager.sweep
package:flutter/…/gestures/arena.dart:157
#20     GestureBinding.handleEvent
package:flutter/…/gestures/binding.dart:444
#21     GestureBinding.dispatchEvent
package:flutter/…/gestures/binding.dart:420
#22     RendererBinding.dispatchEvent
package:flutter/…/rendering/binding.dart:278
#23     GestureBinding._handlePointerEventImmediately
package:flutter/…/gestures/binding.dart:374
#24     GestureBinding.handlePointerEvent
package:flutter/…/gestures/binding.dart:338
#25     GestureBinding._flushPointerEventQueue
package:flutter/…/gestures/binding.dart:296
#26     GestureBinding._handlePointerDataPacket
package:flutter/…/gestures/binding.dart:279
#30     _invoke1 (dart:ui/hooks.dart:183:10)
#31     PlatformDispatcher._dispatchPointerDataPacket (dart:ui/platform_dispatcher.dart:285:7)
#32     _dispatchPointerDataPacket (dart:ui/hooks.dart:96:31)
(elided 3 frames from dart:async)
Handler: "onTapUp"
Recognizer: TapGestureRecognizer#57296
    debugOwner: _TextSelectionGestureDetectorState#43a97
    state: ready
    won arena
    finalPosition: Offset(154.9, 371.6)
    finalLocalPosition: Offset(154.9, 29.1)
    button: 1
    sent tap down
════════════════════════════════════════════════════════════════════════════════

Expected behavior
I expect the sample code to work as-is, dispose the TextEditingController when needed.

Using ref.watch instead of ref.read seems to solve the issue. However, getting the same error after changing a screen. :cry:


Pair - wait for disconnect; Flash - restart after bonding

I think we might want to talk about the connection flow, but it seems to fix the issue on my phone regarding trying to pair and flash after unpairing the micro:bit. I will merge it.


retrieval api, ldevnet multiple miners, renaming

Closes #94
Closes #100
In this PR the ldevnet package now supports multiple miners; generally less than 6 without starting to have some problems. Most of the work needed for supporting this was done in the previous PR but it needed a special tweak (after lots of testing), and was only allowing one miner to mine. This is like simulating that there's a very powerful miner in the network. This isn't a problem for our needs since we only need that all miners accept deals and do their stuff. We aren't interested in them earning block rewards or similar.
Regarding tests:

Extended the TestStore for deals to test for 1, 3 and 5 miners; works.
Created a new Retrieve API in the Deals Module to have a test to check the full cycle of storing something, and checking that the retrieval matches what was stored.

Unfortunately, the current code in Lotus doesn't accept fetching the data from multiple miners where we store; it only remembers the last miner where the data was stored. So, even we can store things in multiple miners, the retrieval tests can't test each of them, only the last one. I left the code generic since this will be eventually implemented, but the test case is configured to store and retrieve only from one miner (since storing in extra ones cant be retrieved so it's meaningless).
Other changes:

Renamed the DealConfig to a better name since there will be also RetreievalDeals.
The retrieval of data is with the dataCID which was stored, not with the ProposalCids. Since this is crucial information to retrieve what was stored, I added it to the return values of Store and to all the path backward of gRPC types and on.

Thanks!

I had a look too... Nice work! Tricky stuff.


Keycloak integration

Adding the ability to create extended profile information and use filtering.
Still WIP

Still pretty much WIP but going to do master now to avoid conflicts


Create Password function in App.js

This issue should create a createPassword function using the below logic:
Input (Character List based on the requirement by user)
Loop through passwordLength

pick a random character from the characterList
Append to a password String
Return (Password)

Hey. I am down with this. Shall I get assigned for this ?

Please assign me this @warrenferns


clone node on drag-n-drop across trees

Hi there, is this an existing out of the box option?
If not can it be added?
Thanks!

Just in case the scenario is not clear:
When dragging a node from tree1 and dropping it in tree2, i want the node to be cloned, and not moved.

Hi,
I will add copyNode soon so you can use it. Stay tuned
If you're in a hurry you can override actionMapping and supply a copy function of your own - refer to the docs.

Hey,
will add a copyNode function, and a getNodeClone callback option in 4.1.0.
Please review the updates docs


Add trusted sources to ConnectorConfig

The trustedsources table in Cassandra lists pages that the user wishes to watch. Each entry specifies the connector (i.e. "InstagramTag", "InstagramPost", "TwitterPost") that the page is applicable to. For some connectors, the list of pages to watch is needed when creating the stream.
This task captures the addition of trusted sources to ConnectorConfig so that StreamFactorys can use the list of trusted sources when creating streams/connections.

Completed by #67


Fix a bug in io.ga that requires an index_col

See: http://stackoverflow.com/questions/26858077/pandas-io-ga-not-working-for-me-solved

needs a test, however I don't think the ga infrastructure is currently tested on ci at all though.

closing as stale, but if you would like to reopen and fixup pls do.


PolkaOracle

Grant Application Checklist

[ ] The application-template.md has been copied, renamed ( "project_name.md") and updated.
[ ] A BTC address for the payment of the milestones is provided inside the application.
[ ] The software of the project will be released under the Apache license version 2.0 as specified in the terms and conditions.
[ ] The total funding amount of the project is below CHF 30k at the time of submission.

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

Thanks for the application, besides signing the CLA, you should also take a look at our template. You application is currently missing quite a few details: https://github.com/w3f/Open-Grants-Program/blob/master/applications/application-template.md


How to make this plugin responsive

Hi,
any approach how to make this whole thing work responsive?

Yes, we can rebuild the grid when screen size changes. So I think we will add option to support this feature. If you can implement, please PR. I will take a look on this on the weekend. Thanks.

Did you manage to incoporate this? @jerryc-nguyen


feat: Change during slide

A new feature that allows to send new values to the entity while changing the slider, without releasing it.

Any chance to get that PR submitted and integrated soon in main code ?