HBASE-22539 WAL corruption due to early DBBs re-use when Durability.A…

…SYNC_WAL is used

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
43
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.

+1
test4tests
0
The patch appears to include 4 new or modified test files.

_ master Compile Tests _

+1
mvninstall
297
master passed

+1
compile
51
master passed

+1
checkstyle
72
master passed

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

+1
javadoc
35
master passed

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

+1
findbugs
237
master passed

_ Patch Compile Tests _

+1
mvninstall
296
the patch passed

+1
compile
57
the patch passed

+1
javac
57
the patch passed

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

+1
whitespace
0
The patch has no whitespace issues.

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

+1
hadoopcheck
881
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1
javadoc
36
the patch passed

+1
findbugs
253
the patch passed

_ Other Tests _

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

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

11695

Reason
Tests

Failed junit tests
hadoop.hbase.security.TestSecureIPC

hadoop.hbase.wal.TestWALCorruptionDueToDanglingByteBuffer

Subsystem
Report/Notes

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

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

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

uname
Linux accfd33bafd3 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-437/out/precommit/personality/provided.sh

git revision
master / 8cfc46d8d0

Default Java
1.8.0_181

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

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

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

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

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-437/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
78
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.

+1
test4tests
0
The patch appears to include 6 new or modified test files.

_ master Compile Tests _

+1
mvninstall
349
master passed

+1
compile
63
master passed

+1
checkstyle
103
master passed

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

+1
javadoc
40
master passed

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

+1
findbugs
271
master passed

_ Patch Compile Tests _

+1
mvninstall
321
the patch passed

+1
compile
57
the patch passed

+1
javac
57
the patch passed

-1
checkstyle
87
hbase-server: The patch generated 1 new + 49 unchanged - 0 fixed = 50 total (was 49)

+1
whitespace
0
The patch has no whitespace issues.

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

+1
hadoopcheck
1001
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1
javadoc
34
the patch passed

+1
findbugs
264
the patch passed

_ Other Tests _

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

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

5482

Reason
Tests

Failed junit tests
hadoop.hbase.coprocessor.TestCoreRegionCoprocessor

Subsystem
Report/Notes

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

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

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

uname
Linux bf2fdf909ae7 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-437/out/precommit/personality/provided.sh

git revision
master / 8cfc46d8d0

Default Java
1.8.0_181

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

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

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

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

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-437/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
87
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.

+1
test4tests
0
The patch appears to include 6 new or modified test files.

_ master Compile Tests _

+1
mvninstall
336
master passed

+1
compile
60
master passed

+1
checkstyle
90
master passed

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

+1
javadoc
37
master passed

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

+1
findbugs
244
master passed

_ Patch Compile Tests _

+1
mvninstall
333
the patch passed

+1
compile
59
the patch passed

+1
javac
59
the patch passed

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

+1
whitespace
0
The patch has no whitespace issues.

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

+1
hadoopcheck
994
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1
javadoc
33
the patch passed

+1
findbugs
255
the patch passed

_ Other Tests _

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

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

16220

Subsystem
Report/Notes

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

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

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

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

Build tool
maven

Personality
<EMAIL_ADDRESS>

git revision
master / 237229cade

Default Java
1.8.0_181

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

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

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

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

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-437/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
33
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.

+1
test4tests
0
The patch appears to include 6 new or modified test files.

_ master Compile Tests _

+1
mvninstall
336
master passed

+1
compile
61
master passed

+1
checkstyle
94
master passed

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

+1
javadoc
38
master passed

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

+1
findbugs
278
master passed

_ Patch Compile Tests _

+1
mvninstall
328
the patch passed

+1
compile
59
the patch passed

+1
javac
59
the patch passed

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

+1
whitespace
0
The patch has no whitespace issues.

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

+1
hadoopcheck
1032
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1
javadoc
35
the patch passed

+1
findbugs
271
the patch passed

_ Other Tests _

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

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

12739

Subsystem
Report/Notes

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

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

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

uname
Linux 331885c1c25d 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-437/out/precommit/personality/provided.sh

git revision
master / 7e6684b1f4

Default Java
1.8.0_181

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

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

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

modules
C: hbase-server U: hbase-server

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

I think in AsyncFSWAL#appendAndSync, we also need to release the BB when IOException thrown..
      try {
        appended = append(writer, entry);
      } catch (IOException e) {
        throw new AssertionError("should not happen", e);
      }

I think the message means this should not happen, so we do not need to deal with it?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
65
Docker mode activated.

_ Prechecks _

+1
dupname
1
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.

+1
test4tests
0
The patch appears to include 6 new or modified test files.

_ master Compile Tests _

+1
mvninstall
410
master passed

+1
compile
89
master passed

+1
checkstyle
80
master passed

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

+1
javadoc
33
master passed

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

+1
findbugs
262
master passed

_ Patch Compile Tests _

+1
mvninstall
392
the patch passed

+1
compile
109
the patch passed

+1
javac
109
the patch passed

+1
checkstyle
125
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

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

+1
hadoopcheck
985
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1
javadoc
33
the patch passed

+1
findbugs
371
the patch passed

_ Other Tests _

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

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

20107

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestSnapshotDFSTemporaryDirectory

Subsystem
Report/Notes

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

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

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

uname
Linux 509cff76c25c 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-437/out/precommit/personality/provided.sh

git revision
master / a6f065396a

Default Java
1.8.0_181

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

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

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

modules
C: hbase-server U: hbase-server

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

The failed UT is unrelated. @openinx @wchevreuil Any other concerns? This is a critical bug, we should roll new releases soon.

I still think we should release the BB in the exceptional case for AsyncFSWAL#appendAndSync,
try {
        appended = append(writer, entry);
      } catch (IOException e) {
        throw new AssertionError("should not happen", e);
      }

There're coprocessorHost.preWALWrite inside the append method, although the Assert message say it shouldn't happen, but user may write an incorrect CP, which would throw an IOException..
Also, I think better to change the message "Shouldn't happen..."

If this happens we just let the region server die, I think this is the correct way to deal with this. The design here can not deal with the IOException.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
137
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.

+1
test4tests
0
The patch appears to include 6 new or modified test files.

_ master Compile Tests _

+1
mvninstall
440
master passed

+1
compile
60
master passed

+1
checkstyle
115
master passed

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

+1
javadoc
46
master passed

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

+1
findbugs
323
master passed

_ Patch Compile Tests _

+1
mvninstall
420
the patch passed

+1
compile
69
the patch passed

+1
javac
69
the patch passed

+1
checkstyle
101
hbase-server: The patch generated 0 new + 48 unchanged - 1 fixed = 48 total (was 49)

+1
whitespace
0
The patch has no whitespace issues.

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

+1
hadoopcheck
1195
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1
javadoc
34
the patch passed

+1
findbugs
258
the patch passed

_ Other Tests _

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

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

16359

Subsystem
Report/Notes

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

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

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

uname
Linux d838541ba2d7 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-437/out/precommit/personality/provided.sh

git revision
master / a6f065396a

Default Java
1.8.0_181

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

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

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-437/7/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
107
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.

+1
test4tests
0
The patch appears to include 6 new or modified test files.

_ master Compile Tests _

+1
mvninstall
336
master passed

+1
compile
61
master passed

+1
checkstyle
89
master passed

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

+1
javadoc
40
master passed

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

+1
findbugs
304
master passed

_ Patch Compile Tests _

+1
mvninstall
333
the patch passed

+1
compile
64
the patch passed

+1
javac
64
the patch passed

+1
checkstyle
87
hbase-server: The patch generated 0 new + 48 unchanged - 1 fixed = 48 total (was 49)

+1
whitespace
0
The patch has no whitespace issues.

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

+1
hadoopcheck
1028
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1
javadoc
41
the patch passed

+1
findbugs
274
the patch passed

_ Other Tests _

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

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

19797

Reason
Tests

Failed junit tests
hadoop.hbase.regionserver.TestHRegionWithInMemoryFlush

hadoop.hbase.TestMetaTableAccessor

Subsystem
Report/Notes

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

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

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

uname
Linux 9ba72caba93a 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-437/out/precommit/personality/provided.sh

git revision
master / abb60faa6c

Default Java
1.8.0_181

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

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

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

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-437/8/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
97
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.

+1
test4tests
0
The patch appears to include 6 new or modified test files.

_ master Compile Tests _

-1
mvninstall
85
root in master failed.

-1
compile
43
hbase-server in master failed.

+1
checkstyle
88
master passed

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

-1
javadoc
34
hbase-server in master failed.

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

-1
findbugs
39
hbase-server in master failed.

_ Patch Compile Tests _

-1
mvninstall
11
root in the patch failed.

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

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

+1
checkstyle
88
hbase-server: The patch generated 0 new + 48 unchanged - 1 fixed = 48 total (was 49)

+1
whitespace
0
The patch has no whitespace issues.

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

-1
hadoopcheck
10
The patch causes 7 errors with Hadoop v2.8.5.

-1
hadoopcheck
19
The patch causes 7 errors with Hadoop v2.9.2.

-1
hadoopcheck
29
The patch causes 7 errors with Hadoop v3.1.2.

-1
javadoc
32
hbase-server in the patch failed.

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

_ Other Tests _

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

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

1348

Subsystem
Report/Notes

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

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

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

uname
Linux af6708122807 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-437/out/precommit/personality/provided.sh

git revision
master / d0e5ea1b87

Default Java
1.8.0_181

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

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

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-437/9/artifact/out/branch-javadoc-hbase-server.txt

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

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

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

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

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

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-437/9/artifact/out/patch-javac-2.9.2.txt

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

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

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

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

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

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

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-437/9/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
81
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.

+1
test4tests
0
The patch appears to include 6 new or modified test files.

_ master Compile Tests _

-1
mvninstall
11
root in master failed.

-1
compile
40
hbase-server in master failed.

+1
checkstyle
87
master passed

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

-1
javadoc
31
hbase-server in master failed.

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

-1
findbugs
38
hbase-server in master failed.

_ Patch Compile Tests _

-1
mvninstall
10
root in the patch failed.

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

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

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

+1
whitespace
0
The patch has no whitespace issues.

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

-1
hadoopcheck
11
The patch causes 7 errors with Hadoop v2.8.5.

-1
hadoopcheck
23
The patch causes 7 errors with Hadoop v2.9.2.

-1
hadoopcheck
34
The patch causes 7 errors with Hadoop v3.1.2.

-1
javadoc
42
hbase-server in the patch failed.

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

_ Other Tests _

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

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

1301

Subsystem
Report/Notes

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

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

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

uname
Linux 1df5b21627dd 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-437/out/precommit/personality/provided.sh

git revision
master / ff96485396

Default Java
1.8.0_181

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

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

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-437/10/artifact/out/branch-javadoc-hbase-server.txt

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

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

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

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

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

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-437/10/artifact/out/patch-javac-2.9.2.txt

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

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

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

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

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

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

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-437/10/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.

Let me merge this back if no other big concerns. This is a critical bug...

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
70
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.

+1
test4tests
0
The patch appears to include 6 new or modified test files.

_ master Compile Tests _

+1
mvninstall
434
master passed

+1
compile
81
master passed

+1
checkstyle
96
master passed

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

+1
javadoc
46
master passed

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

+1
findbugs
294
master passed

_ Patch Compile Tests _

+1
mvninstall
471
the patch passed

+1
compile
96
the patch passed

+1
javac
96
the patch passed

+1
checkstyle
102
hbase-server: The patch generated 0 new + 48 unchanged - 1 fixed = 48 total (was 49)

+1
whitespace
0
The patch has no whitespace issues.

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

+1
hadoopcheck
1251
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1
javadoc
42
the patch passed

+1
findbugs
318
the patch passed

_ Other Tests _

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

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

6476

Reason
Tests

Failed junit tests
hadoop.hbase.coprocessor.TestCoreRegionCoprocessor

hadoop.hbase.coprocessor.TestRegionCoprocessorHost

Subsystem
Report/Notes

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

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

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

uname
Linux 67d28139dc12 4.4.0-143-generic #169-Ubuntu SMP Thu Feb 7 07:56:38 UTC 2019 x86_64 GNU/Linux

Build tool
maven

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

git revision
master / f6ece8d8e3

Default Java
1.8.0_181

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

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

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

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-437/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
61
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.

+1
test4tests
0
The patch appears to include 6 new or modified test files.

_ master Compile Tests _

+1
mvninstall
285
master passed

+1
compile
51
master passed

+1
checkstyle
72
master passed

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

+1
javadoc
31
master passed

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

+1
findbugs
254
master passed

_ Patch Compile Tests _

+1
mvninstall
299
the patch passed

+1
compile
51
the patch passed

+1
javac
51
the patch passed

+1
checkstyle
70
hbase-server: The patch generated 0 new + 48 unchanged - 1 fixed = 48 total (was 49)

+1
whitespace
0
The patch has no whitespace issues.

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

+1
hadoopcheck
911
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1
javadoc
37
the patch passed

+1
findbugs
268
the patch passed

_ Other Tests _

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

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

19824

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestAsyncTableAdminApi

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-437/12/artifact/out/Dockerfile

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

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

uname
Linux d2b008745cee 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-437/out/precommit/personality/provided.sh

git revision
master / f6ece8d8e3

Default Java
1.8.0_181

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

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

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

modules
C: hbase-server U: hbase-server

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


Link to dask-examples repository

See https://github.com/dask/dask-ml/blob/56714b4a8749d0b0d1948de443bcce43dc60354e/docs/source/conf.py#L203-L226

For reference, https://dask.github.io/dask-ml/examples.html, each of those links to a rendered version of the notebook (built with nbsphinx when the docs are built)
I'd like to make it so the TOC includes a "try on binder" link next to the notebook title.

I briefly played with writing a sphinx extension to take a toctree like
.. toctree:

   examples/foo :binder:

and  turn it into something like
..toctree:

   xgboost .. image:: https://mybinder.org/badge.svg :target: https://mybinder.org/v2/gh/dask/dask-examples/master?filepath=%2Fmachine-learning%2Fxgboost.ipynb

to render like

xgboost

I didn't get very far though. It seems like sphinx doesn't recursively parse markup in the toctree.

It seems like we're also heading to a point where we get better at
integrating many different doc pages into one cohesive system.  Maybe we
wait on that and manage examples separately within the dask-examples repo
itself.
On Fri, Aug 31, 2018 at 4:18 PM, Tom Augspurger<EMAIL_ADDRESS>wrote:

I briefly played with writing a sphinx extension to take a toctree like
.. toctree:
examples/foo :binder:
and turn it into something like
..toctree:
xgboost .. image:: https://mybinder.org/badge.svg :target: https://mybinder.org/v2/gh/dask/dask-examples/master?filepath=%2Fmachine-learning%2Fxgboost.ipynb
to render like

xgboost
https://mybinder.org/v2/gh/dask/dask-examples/master?filepath=%2Fmachine-learning%2Fxgboost.ipynb

I didn't get very far though. It seems like sphinx doesn't recursively
parse markup in the toctree.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/3921#issuecomment-417778337, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASszESS382NlCPvOF8ZO8FgluPRzMIIks5uWZoSgaJpZM4WTq8t
.

FWIW an alternative approach to including a binder badge in the toctree would be to specify a nbsphinx_prolog in conf.py (ref https://nbsphinx.readthedocs.io/en/0.3.5/prolog-and-epilog.html) that adds a binder badge to the top of each rendered notebook
Example usage: https://jrbourbeau.github.io/pyunfold/notebooks/tutorial.html

Ooh, nice.
On Fri, Sep 14, 2018 at 3:49 PM, James Bourbeau<EMAIL_ADDRESS>wrote:

FWIW an alternative approach to including a binder badge in the toctree
would be to specify a nbsphinx_prolog in conf.py (ref
https://nbsphinx.readthedocs.io/en/0.3.5/prolog-and-epilog.html) that
adds a binder badge to the top of each rendered notebook
Example usage: https://jrbourbeau.github.io/pyunfold/notebooks/tutorial.
html
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/3921#issuecomment-421466175, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASszGqynxiJ1gimkLvAsA_YUkhG6LZSks5ubAhFgaJpZM4WTq8t
.

My understand was Sphinx-Gallery was trying to solve this too.

examples.dask.org is now integrated into docs.  Closing.  Thanks all


Node.js  Community Committee Meeting 2021-05-27

Time
UTC Thu 27-May-2021 16:00 (04:00 PM):

Timezone
Date/Time

US / Pacific
Thu 27-May-2021 09:00 (09:00 AM)

US / Mountain
Thu 27-May-2021 10:00 (10:00 AM)

US / Central
Thu 27-May-2021 11:00 (11:00 AM)

US / Eastern
Thu 27-May-2021 12:00 (12:00 PM)

EU / Western
Thu 27-May-2021 17:00 (05:00 PM)

EU / Central
Thu 27-May-2021 18:00 (06:00 PM)

EU / Eastern
Thu 27-May-2021 19:00 (07:00 PM)

Moscow
Thu 27-May-2021 19:00 (07:00 PM)

Chennai
Thu 27-May-2021 21:30 (09:30 PM)

Hangzhou
Fri 28-May-2021 00:00 (12:00 AM)

Tokyo
Fri 28-May-2021 01:00 (01:00 AM)

Sydney
Fri 28-May-2021 02:00 (02:00 AM)

Or in your local time:

https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Community Committee+Meeting+2021-05-27&iso=20210527T1600
or https://www.wolframalpha.com/input/?i=04PM+UTC%2C+May+27%2C+2021+in+local+time

Links

Minutes Google Doc: https://docs.google.com/document/d/1F9emADCJHH4JMh_jo75lw6k7Lkj2-31a16cLcVxLxkc/edit

Agenda
Extracted from cc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
Invited

CommComm Members: @nodejs/community-committee

Observers/Guests
Feel free to follow along on the YouTube live stream, or attend meeting as a guest
by calling in to Zoom, using the links below. If you will be attending as a guest,
please comment on this issue to let us know you'll be joining.
Notes
The agenda comes from issues labelled with cc-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.
Joining the meeting

Link for participants: https://zoom.us/j/95198277339
For those who just want to watch: https://www.youtube.com/channel/UCQPYJluYC_sn_Qz_XE-YbTQ

Invitees
Please use the following emoji reactions in this post to indicate your
availability.

:+1: - Attending
:-1: - Not attending
:confused: - Not sure yet

I'm not going to be able to make it today - something's wrong with my throat and talking is extremely painful 😞

Since we have no agenda and I'm swamped getting ready for OpenJS World and other things, I am in favor of canceling today's meeting.

Canceling meeting, yall. See you next time. :)

See you next time, folks! :)
Get well soon, @bnb 🙌

Hope you feel better soon @bnb! ♥
Best of luck with all your OpenJS World prep @joesepi! 🚀
Thanks all, looking forward to connecting next time. 😄


Bump open-aea to v1.12.0

Proposed changes
Bump open-aea to latest
Types of changes
What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.)
Put an x in the box that applies

[ ] Non-breaking fix (non-breaking change which fixes an issue)
[ ] Breaking fix (breaking change which fixes an issue)
[ ] Non-breaking feature (non-breaking change which adds functionality)
[ ] Breaking feature (breaking change which adds functionality)
[ ] Refactor (non-breaking change which changes implementation)
[ ] Messy (mixture of the above - requires explanation!)

Checklist
Put an x in the boxes that apply.

[x] I have read the CONTRIBUTING doc
[x] I am making a pull request against the main branch (left side). Also you should start your branch off our main.
[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have locally run services that could be impacted and they do not present failures derived from my changes

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

So 4 Failures in total.

FAILED tests/test_autonomy/test_cli/test_replay/test_tendermint.py::TestTendermintRunner::test_run caused by

E         [Tendermint] Successfully initialized 4 node directories
E         Error: Cannot find valory/open-autonomy-tendermint:0.1.0, Please build images first.

On macOS network failure while installing dependencies, again !

Same network failure on windows

E2E

FAILED tests/test_agents/test_oracle_abci.py::TestAgentCatchup::test_run[4]
FAILED tests/test_agents/test_register_reset_abci.py::TestTendermintResetInterruptNoRejoin::test_run[4]
FAILED tests/test_agents/test_register_reset_abci.py::TestTendermintReset::test_run[4]
FAILED tests/test_agents/test_register_reset_abci.py::TestTendermintResetInterrupt::test_run[4]

I found this while going through the logs
err="precommit step; +2/3 prevoted for an invalid block: wrong Block.Header.AppHash.  Expected 726F6F743A3072657365743A30, got 726F6F743A3172657365743A31" stack="goroutine 24972795 [running]:\nruntime/debug.Stack()\n\t/opt/hostedtoolcache/go/1.18.0/x64/src/runtime/debug/stack.go:24 +0x65\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine.func2()\n\t/home/runner/work/tendermint/tendermint/consensus/state.go:727 +0x4c\npanic({0xe554c0, 0xc001dfb460})\n\t/opt/hostedtoolcache/go/1.18.0/x64/src/runtime/panic.go:838 +0x207\ngithub.com/tendermint/tendermint/consensus.(*State).enterPrecommit(0xc00057a700, 0x11, 0x0)\n\t/home/runner/work/tendermint/tendermint/consensus/state.go:1408 +0x16ff\ngithub.com/tendermint/tendermint/consensus.(*State).addVote(0xc00057a700, 0xc001e875e0, {0xc000d40b10, 0x28})\n\t/home/runner/work/tendermint/tendermint/consensus/state.go:2123 +0x188f\ngithub.com/tendermint/tendermint/consensus.(*State).tryAddVote(0xc00057a700, 0xc001e875e0, {0xc000d40b10?, 0xc00055b700?})\n\t/home/runner/work/tendermint/tendermint/consensus/state.go:1949 +0x2c\ngithub.com/tendermint/tendermint/consensus.(*State).handleMsg(0xc00057a700, {{0x12901e0?, 0xc00000f8f8?}, {0xc000d40b10?, 0x0?}})\n\t/home/runner/work/tendermint/tendermint/consensus/state.go:856 +0x44b\ngithub.com/tendermint/tendermint/consensus.(*State).receiveRoutine(0xc00057a700, 0x0)\n\t/home/runner/work/tendermint/tendermint/consensus/state.go:763 +0x419\ncreated by github.com/tendermint/tendermint/consensus.(*State).OnStart\n\t/home/runner/work/tendermint/tendermint/consensus/state.go:379 +0x12d\n"

What's up with tests/test_autonomy/test_cli/test_replay/test_tendermint.py::TestTendermintRunner::test_run in Ubuntu + py3.10?


Conduct UI Overhaul for Enhanced User Interface

Description:
To improve user engagement and satisfaction, the current UI requires a series of enhancements. This includes refining the color scheme, improving layout responsiveness, and ensuring a consistent design language across the application.
Acceptance Criteria:

A cohesive color scheme that aligns with the brand identity.
Improved responsiveness of all UI components.
Consistent use of Material UI design elements across all pages.

Tasks:

[x] Audit existing UI for design inconsistencies.
[x] Update color scheme and apply it across the application.
[x] Refactor UI components for improved responsiveness.
[x] Test UI on various devices for consistency and usability.

Completed


Update Leap Motion recipe (currently not working) to 2.2.3

Coverage remained the same at 83.75% when pulling 79ba8b9a7582af5af765ca15bb0a4911f35b86fd on jhanschoo:master into fc0647bec996877ef41984511d012d2da72046e6 on caskroom:master.


Batch Notebooks for CP4D - 4.0

@patelkishore - Please review this PR. Thanks

@arsuryan - When do you plan to merge?


Conda install problem

Hello !
I tried to install poliastro on fresh anaconda / anaconda3.
When I run the command:
conda install poliastro
After adding conda-forge.
I get the following error message:

Collecting package metadata: | WARNING conda.core.index:push_record(193): Skipping conda-forge/noarch::poliastro-0.10.0-py_1 due to InvalidSpec: <4.*
WARNING conda.core.index:push_record(193): Skipping conda-forge/noarch::poliastro-0.11.0-py_0 due to InvalidSpec: <4.*
WARNING conda.core.index:push_record(193): Skipping conda-forge/noarch::poliastro-0.11.1-py_0 due to InvalidSpec: <4.*
done
Solving environment: failed

InvalidVersionSpec: Invalid version '<4.*': invalid operator with '.*'

So I go through PIP which has been successful in installing poliastro.

:(
I will go through PIP while waiting.

Updating to the just-released conda 4.6.3 fixes the problem https://github.com/conda/conda/releases/tag/4.6.3 @dragonlost I just tried on my side, but would you please confirm as well and close the issue if appropriate?

Ah Super ! I just tested and it works!
Just a warning message:
Collecting package metadata: | WARNING conda.models.version:get_matcher(528): Using .* with relational operator is superfluous and deprecated and will be removed in a future version of conda. Your spec was 4., but conda is ignoring the . and treating it as 4

I see! Well, we already fixed the conda package, so I hope this is not a problem in the future (by handling the failure in a less catastrophic way).
Closing!


Earlgrey: sram_ctrl.sv doesn't work in verilator

It gives errors:
%Error: Unknown object type: unsupported_typespec
%Error: vpiTypespec node of type unsupported_typespec can't be handled as AstNodeDType
%Error: Internal Error: /builds/git/systemverilog-automatic-uhdm-earlgrey-tests/verilator/uhdm-integration/build/lowrisc_systems_top_earlgrey_verilator_0.1/src/lowrisc_ip_sram_ctrl_0.1/rtl/sram_ctrl.sv:18:40: ../V3Ast.cpp:344: Null item passed to setOp1p

I created the test and verilator passes it: https://github.com/chipsalliance/UHDM-integration-tests/pull/394
It looks like it doesn't work in opentitan only due to lack of dependencies.

Removed from Verilator list in https://github.com/antmicro/verilator/pull/433


Inspector is broken in RTL

Is this a bug report?
Yes.
Have you read the Contributing Guidelines?
Yes.
Environment

react-native -v: 0.47.1
node -v: 8.2.1
npm -v: 5.3.0
yarn --version: 0.27.5

Then, specify:

Target Platform: IOS and Android

Development Operating System: macOS

Build tools: Xcode

Is the issue specific to a particular iOS or Android SDK? no.

Steps to Reproduce

(Write your steps here:)

Use RTL language or enforce RTL layout
open inspector
try to inspect an element aligned to the left or to the right

Expected Behavior

The element bounding box should be coloured
Actual Behavior

The bounding box is aligned to the opposite side.

This issue should definitely remain open

It's a bug, definitely.


A small patch which enables scroll view toggling. - Replaces #647

If there are many columns, the board adds a horizontal scrollbar. However, This looses the full board visibility. Now there is a menu item on the Board, Action > Toggle view which switches. This can also be toggled by 'c' keypress.
Replaces #647

This has got some problem which messes up dragging tasks. Will fix and test more.


protoc plugins not installed by install target

What version of gRPC and what language are you using?
v1.11.0 (bd44e485f69d70ca4095cea92decd98de3892aa6)
What operating system (Linux, Windows, …) and version?
Windows 7
What runtime / compiler are you using (e.g. python version or version of gcc)
Visual Studio 15.5.1
What did you do?
Followed the build instructions from Install.md (build & install with ninja)
What did you expect to see?
Install directory should contain protoc plugins such as grpc_cpp_plugin.exe
What did you see instead?
No protoc plugins have been installed. I can see they have all been build and are located in the .build folder.

After reading further I have come to the understanding that due to #10759 gRPC_INSTALL is set to OFF when using ny dependency from git-submodules. Unfortunately this means that the installation guide is incorrect. Further it seems impossible to build & install on Windows with BoringSSL since the package variant does only search for openssl.
I am aware that I can still build and create my own installation script but that's a lot of work :(

@Ozaq I agree with your assesment, but it is unclear to me what can be done about this.
In cmake world, it is incorrect to perform installation of your submodules  while performing cmake install (and cmake actually wouldn't allow it, which is why autodisabling of gRPC_INSTALL has been introduced in the past) - you should install all your dependencies separately and then install grpc. This process can be simplified by e.g. using cmake's ExternalProject_Add feature.
Here are examples of various (tested) ways how to install gRPC with cmake
https://github.com/grpc/grpc/tree/master/test/distrib/cpp Each of these approaches has its limitations, so you have to choose which
I think the solution that might be best for your case it to use the cmake "superbuild" approach.

@jtattermusch I understand that there is no easy solution, but it was very surprising to have to read that kind of information from the cmake files (and the issue tracker). The part that irritated me most was that install does seemingly succeed just that there are some files missing. I would rather prefer the install targets to be completely disabled so that I do not get the impression there is a working install step.

@Ozaq   thanks for the feedback, I think you have a point - we are working on improving the cmake  (and/or build instructions in gereral) instructions so that there's no confusion.


Feature request: compatibility with radios running OpenGD77

Hello dev-team,
Could I please request for dmrconfig to be bale to read and write 'code-plug' for the GD77 radios running OpenGD77 firmware?
Thank you for your time and support.

This would be fantastic. The GD77 running OpenGD77 presents a ACM serial device (generally, /dev/ttyACM0). There are existing implementations in e.g. the qdmr project that could perhaps be used as a reference if the protocol is different from already supported radios.

This looks like a dupe of https://github.com/OpenRTX/dmrconfig/issues/49


Remove New User wiki page

resolution_fixed   |    by<EMAIL_ADDRESS>
The wiki page https://accessdev.nci.org.au/trac/wiki/Admin Guides/New User looks outdated since the access is now set up so anyone in the "access" group can log in to accessdev.
Does anyone object to me deleting this page?

Issue migrated from trac:145 at 2024-01-31 18:08:08 +1100

<EMAIL_ADDRESS>commented

Go ahead

<EMAIL_ADDRESS>commented

OK, I've left the page, but made it clear that they are old instructions and all "access" group members can log into accessdev

<EMAIL_ADDRESS>commented

can we keep it as a useful piece of puppet instructions and just mark it superseded by use of access group.
Just for future reference if needed :-)
Robin

<EMAIL_ADDRESS>changed status from new to closed

<EMAIL_ADDRESS>changed resolution from `` to fixed


object type settings (work around)

Please take a moment to fill out the following:
Fixes # .
Changes Proposed in this pull request:

library supports string, so i think that we can use serialization. because many setting could encapsulate by object.

This is not recommended to save complex objects in settings as there are size limits to strings. Files or Databases should be created. Thanks for the sample, but I do not want to recommend this route to developers.


Undo remove table: selection is not restored

Since v0.11.0
See comment https://github.com/GitbookIO/slate-edit-table/pull/38

@Soreine just wondering would you have time about https://github.com/GitbookIO/slate-edit-table/pull/63 to resolve the selection issue?


[Bug] DeadCodeInjection puts unobfuscated code

I think it is too obviously if all code is obfuscated but some part don't.

I think this bug is because obfuscator doesn't obfuscate variables and function that weren't declared in current scope. DeadCodeInjector just steals a part of code, but declaration of variable is in outer scope.
So my solution is to run deadCodeInjection after renaming variables.

Yes, i know about this and will try to fix it in the future. This is because some identifiers HAS NOT declarations and these identifiers keep without obfuscation.

Issue for export * as exports
https://github.com/javascript-obfuscator/javascript-obfuscator/issues/710

So. I'll close this issue. Tomorrow i'll release a new version with literals fix

How do you think about just taking random variables from upper scope?
That will be pretty messy😏

No. I have added additional transformer for dead code injection that renames ALL through identifiers (identifiers without declaration. It will rename some global identifiers too like console and others, but it should affect runtime, because dead code isn't evaluated during runtime.

PR: https://github.com/javascript-obfuscator/javascript-obfuscator/pull/715


Fix hiscore api after jagex reordered it, and reorder lists after update

Fixes #6279

Theres at least one test in the http-service which also needs to be updated. Maybe also add to it a test for the things which moved.

Updated the existing test and added new tests for the fields that moved


VS Code: [Mac]After installing the 'Visual Studio Green' vsix, open it again to solution, the C # extension is missing.

Describe the bug:
After installing the 'Visual Studio Green' vsix, open it again to solution, the C # extension is missing.
Version used:
VS Code: 1.74.3
C# Extension version:visual-studio-green-0.0.187-alpha.vsix
SDK: 7.0.102
Platform

[X] Mac

To reproduce:

Download one of the VS-GREEN vsix files from its pipeline artifacts: For example: Pipelines - Run 0.0.187-alpha artifacts (visualstudio.com)

Open VS Code, go to the Extensions Tab, select "Install from VSIX" > install the file you downloaded.

Open a normal Terminal Emulator, create MVC project and open it using VS code

     dotnet new sln -o sk
     cd sk
     dotnet new mvc -o xx
     dotnet sln add xx
     code .

Actual behavior
Error is always displayed in the lower right corner.

Expected behavior

I think you should contact the authors of "Visual Studio Green" about this. I don't think anyone here can provide answers, given that I can't even find online what "Visual Studio Green" is supposed to do, and the link you provide seems to require  a login. I get an HTTP 401 error when I try to visit.


No log file created when using Xcode UI Tests

See discussion here:
https://github.com/plu/pxctest/commit/dc69f3be518e06f4c637e87928ccf42c045405c0

So far I cannot reproduce the issue. I've created a sample iOS project, using Xcode's UI tests. The log file is created successfully:
$ run-tests --testrun build/Products/UITestSample_iphonesimulator10.2-i386.xctestrun --destination "name=iPhone 5,OS=iOS 10.2" --output out\ put
...

$ ls -la out\ put/UITestSampleUITests/iOS\ 10.2/iPhone\ 5/UITestSampleUITests-Runner.log
-rw-r--r--  1 plu  staff  8339 Feb 26 08:36 out put/UITestSampleUITests/iOS 10.2/iPhone 5/UITestSampleUITests-Runner.log

I'm on mac OS Sierra 10.12.3 (16D32), using Xcode Version 8.2.1 (8C1002).
@davetobin are you on the same mac OS and Xcode version?

@plu Thanks for checking this out. I'll start with a clean slate when I get a chance and check this out again. I'm on the same Xcode version but OS Sierra 10.12.2 (16C67). I'll update also. You can close this issue if you like and I can reopen with steps to reproduce if it doesn't work for me.

@plu  Having tried this from scratch on Sierra 10.12.3, it seems I am now getting a log file but it's the UITests-Runner.log file as opposed to the AppName.log that I got previously. Do you know if there's a way to get the app log file like before?

I need to investigate this. We could go back to the previous way of obtaining logs, but I'd like to avoid that, if possible.


Add stops to dropdown for lines 110 and 550 where service is restored

Service is being restored so we can make the case that riders that previously used these stops are familiar with them.

[ ] Add the restored stops to the dropdown list.
[ ] Add the stops with a new category of "service_restored" to the stop changes Google Sheet
[ ] Make sure they show up on the front end with the message "Service to this stop is restored"

Line 110

stop_id
stop_name
direction

65300037
WATERS EDGE / JEFFERSON
EB & WB

176153
JEFFERSON / CONCERT PARK DRIVE
EB

2701
JEFFERSON / BEETHOVEN
EB

11194
JEFFERSON / MC CONNELL
EB

2702
JEFFERSON / MC CONNELL
WB

2703
JEFFERSON / WESTLAWN
EB

11197
JEFFERSON / WESTLAWN
WB

2704
JEFFERSON / CAMPUS CENTER DRIVE
EB

140878
JEFFERSON / CENTINELA
EB

20501
JEFFERSON / CENTINELA
WB

2705
JEFFERSON / MESMER
EB

11195
JEFFERSON / MESMER
WB

2706
JEFFERSON / SLAUSON
EB

16943
JEFFERSON / SLAUSON
WB

14660
SLAUSON / SEPULVEDA
WB

12124
JEFFERSON / INGLEWOOD
WB

8683
JEFFERSON / ALLA RD
WB

Line 550

stop_id
stop_name
direction

30005
HARBOR GATEWAY TC / BAY 05
NB

2321
HARBOR TRANSIT WAY / ROSECRANS
NB

10855
HARBOR TRANSIT WAY / I105 GREEN LINE STA
NB

2320
HARBOR TRANSIT WAY / MANCHESTER
NB

2322
HARBOR TRANSIT WAY / SLAUSON
NB

7262
39TH ST / FIGUEROA
NB

1886
EXPOSITION / FIGUEROA
NB

10378
EXPOSITION / TROUSDALE WALK
NB

10390
EXPOSITION / WATT WAY
NB

5635
VERMONT / EXPOSITION
NB

5656
VERMONT / 36th PL
NB

7766
JEFFERSON / VERMONT
NB

7752
JEFFERSON / MC CLINTOCK
NB

2457
MC CLINTOCK / JEFFERSON
NB

2457
MC CLINTOCK / JEFFERSON
SB

2458
JEFFERSON / MC CLINTOCK
SB

140951
VERMONT / JEFFERSON
SB

14039
VERMONT / 36th PL
SB

1841
EXPOSITION / VERMONT
SB

12002
EXPOSITION / WATT WAY
SB

1830
EXPOSITION / UNIVERSITY WALK
SB

10437
EXPOSITION / FIGUEROA
SB

13424
FIGUEROA / STATE
SB

15616
39TH ST / FIGUEROA
SB

10994
HARBOR TRANSIT WAY / SLAUSON
SB

10853
HARBOR TRANSIT WAY / MANCHESTER
SB

2324
HARBOR TRANSIT WAY / I105 GREEN LINE STA
SB

10846
HARBOR TRANSIT WAY / ROSECRANS
SB

Here are the spreadsheets that Scott had sent me- only adding blue
Copy of Copy of list_550 Effective 06-23-13 Revised 08-13-20 (1).xls
Copy of Copy of list_110 Effective 6-27-21 add Playa Vista (1).xls

@EbbyEbby ok, good, these are what I used!


feat(spanner): add PG.OID support

The PG.OID type is an int64 value with a PG_OID type annotation, mostly used by pg_catalog tables. This PR adds support for representing PG.OID values in the C# client.
Tests are added for being able to query a PG.OID value.
User tables can't be created with PG.OID as a column type so no tests were added for DML or mutations. Since the currently available set of pg_catalog tables don't have PG.OID columns, we also don't test being able to read a PG.OID from a table.

Please address the comment from Amanda, but otherwise this looks okay to me. All the changes you have made look fine - but I can't vouch for whether there are other places that have been missed. Can I assume you looked for "jsonb" as an example?

Yeah exactly. I found all the PG.JSONB PRs (#9085, #9243, #9492) and followed exactly what those did. I think PG.JSONB is the closest type to PG.OID.
What I skipped was adding the type to apis/Google.Cloud.Spanner.Data/Google.Cloud.Spanner.Data.IntegrationTests/AllTypesTableFixturePostgreSql.cs since you shouldn't be able to create a user table with this thype.

@amanda-tarafa and @jskeet  I'll let you merge this when you're ready.


hello what can i do

hello what can i do with this ??
RuntimeError: CUDA out of memory. Tried to allocate 58.00 MiB (GPU 0; 5.81 GiB total capacity; 4.95 GiB already allocated; 58.44 MiB free; 5.08 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF

i think there is something i can do in the .txt runsetting template is there a way to render only frame by frame what is the parameter

how to change batch size in the run setting template ?

is there a way to use CPU instead of GPU to have not th eprobleme of cuda ?? may be for more time of work for the computer ?

Using CPU instead of GPU would work. Use smaller image sizes.


ARROW-9680: [Java] Support non-nullable vectors

This issue was first discussed in the ML (https://lists.apache.org/thread.html/r480387ec9ec822f3ed30e9131109e43874a1c4d18af74ede1a7e41c5%40<dev.arrow.apache.org>), from which we have received some feedback.
We briefly resate it here as below:

Non-nullable vectors are widely used in practice. For example, in a database engine, a column can be declared as not null, so it cannot contain null values.
2.Non-nullable vectors has significant performance advantages compared with their nullable conterparts, such as:

the memory space of the validity buffer can be saved.
manipulation of the validity buffer can be bypassed
some if-else branches can be replaced by sequential instructions (by the JIT compiler), leading to high throughput for the CPU pipeline.

We open this Jira to facilitate further discussions, and we may provide a sample PR, which will help us make a clearer decision.

In the first commit of this PR, we only support IntVector.

I think consensus on the mailing list is that this isn't something we want to pursue?

I think consensus on the mailing list is that this isn't something we want to pursue?

I think consensus on the mailing list is that this isn't something we want to pursue?

@emkornfield Thanks for your kind reminder. I am closing it.


Fix Debian install

Hi @mpdehaan
Tested on debian 9 stretch and Ubuntu 18.04.1 LTS

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 3 committers have signed the CLA.:white_check_mark: mpdehaan:x: root:x: rafadevdbroot seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Per #66 seems Debian stable doesn't have expect in it.

The above message about root if from me  is ignorable, but a good sign this should be submitted on a clean feature branch instead rather than your copy of master.
See the development guide and use git pull --rebase vs "git pull" and "git merge" to stay up to date on that branch.

Close was inadvertent - reopening to say it still needs expect, sorry for confusion


[Go Live][March 23]

Push to live

Docs Build status updates of commit 62349b7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/images/teams-toolkit-v2/prerequisites/upload-custom-app.PNG
:white_check_mark:Succeeded
View

msteams-platform/concepts/app-fundamentals-overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/map-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/plan-responsive-tabs-for-teams-mobile.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/planning-checklist.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/design/understand-use-cases.md
:white_check_mark:Succeeded
View

msteams-platform/get-started/get-started-overview.md
:white_check_mark:Succeeded
View

msteams-platform/m365-apps/extend-m365-teams-personal-tab.md
:white_check_mark:Succeeded
View

msteams-platform/sbs-gs-blazorapp.yml
:white_check_mark:Succeeded
View

msteams-platform/sbs-gs-csharp.yml
:white_check_mark:Succeeded
View

msteams-platform/sbs-gs-javascript-debug-F5key.yml
:white_check_mark:Succeeded
View

msteams-platform/sbs-gs-nodejs.yml
:white_check_mark:Succeeded
View

msteams-platform/sbs-gs-spfx.yml
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-CLI.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


SVGs broken in latest release

SVG viewing is broken in the latest release.

SVG Support is still experimental, some svgs might be supported, some might not.

SVG Support is based on the library used here
So, between releases I did not touch any svg implementation, but if this issue still persists over any further release, I'll consider moving from depending on an external library for the implementation

Has been fixed.


regression in integration tests: pass in GitHub Actions on ubuntu-20.04; tests pass locally in 22.04, but fail in GitHub Actions

Description
Our organization publishes networked client software in multiple languages. For our python client, we have observed a regression in integration tests when switching to ubuntu-22.04 runners. The integration tests pass consistently when using an ubuntu-20.04 runner, but are consistently flaky and fail when using ubuntu-22.04.
To contrast, when doing local development on ubuntu 22.04, the integration tests consistently pass. We have verified this in multiple environments, both in a desktop environment and on cloud VMs. We have never observed locally the behavior we see on the failed jobs.
Some context we believe is relevant: the integration tests issue many network calls. The failed tests are due to timeouts. The client library uses gRPC for communication.
Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[X] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
python failed tests https://github.com/momentohq/client-sdk-go/actions/runs/4003037059/jobs/6870798171
Is it regression?
Yes -- the linked pull request where the actions fail only change the runner image from ubuntu-20.04 to ubuntu-latest
Expected behavior
Integration tests should pass
Actual behavior
Integration tests with networked calls fail on some tests, which can change from run to run. See logs here.
Repro steps
Change integration test runner image from ubuntu-20.04 to ubuntu-latest, eg here

Hello @malandis, we'll take a look at it.

Since the agents with the latest image (ubuntu-22.04) are heavily used, the network component can be a bottleneck here, that cause timeouts in your tests.
Could you please add the following snippets to your pipeline?
- run: |
            sudo tcpdump -nn -i any -w sntp.cap &
            sleep 1
           <your problematic steps here>

and then
 - name: Upload capture
          if: always()
          run: |
            sleep 1
            sudo kill -2 $(pgrep tcpdump)
            sleep 1
            sudo curl -F<EMAIL_ADDRESS>https://file.io/?expires=1w

and attach your dump somewhere
(we did something similar in the https://github.com/actions/runner-images/issues/5615) that way we could retrieve a potentially problematic dump.

Possibly related to https://github.com/actions/runner-images/discussions/6862

@Alexey-Ayupov thank you for your help on this. I will make the changes you suggested and upload the dump.

@Alexey-Ayupov thank you for patience. I granted you access to the shared file.

Hello @malandis, I have checked the .cap file and see some strange things. The most strange here is the communication between local IPs <IP_ADDRESS> and <IP_ADDRESS>. Also, some DNS names couldn't be found during such communication.
Could you please check the DNS names in your tests and DNS settings as well if you have such?
By the way how many timeouts were during tcpdump run?

Hello @malandis, could you please send the tcpdump file from the successfully passed run?

Hello @malandis, I have checked the .cap file and see some strange things. The most strange here is the communication between local IPs <IP_ADDRESS> and <IP_ADDRESS>. Also, some DNS names couldn't be found during such communication. Could you please check the DNS names in your tests and DNS settings as well if you have such? By the way how many timeouts were during tcpdump run?

@Alexey-Ayupov thank you for the follow up. To your questions: (1) we do not have any custom DNS settings. (2) We found this issue related to the DNS cache which some are reporting still in 22.04. Does this look familiar? (3) Number of timeouts varies. Our test runner fails fast so sometimes we see only one timeout which short circuits the tests and sometimes several when they run concurrently.
Additionally we see similar looking errors on our Node.js client in both 22.04 and 20.04 runners. Failed runs are here

Hello @malandis, could you please send the tcpdump file from the successfully passed run?

Do you mean the successful runs on 20.04?

Do you mean the successful runs on 20.04?

Yes. I would like to compare the successful run and the failed one.

Do you mean the successful runs on 20.04?

Yes. I would like to compare the successful run and the failed one.

You may find the cap file here

I have compared your tcp dumps, and my doubts were confirmed. The only problem I can see is in the DNS protocol communication. I tried to resolve some DNS names on ubuntu 20.04 and 22.04 the results are the same, both OSes resolve sites correctly. Since you are using the "poetry" utility it can be a problem between it and the OS level, or possibly it can be a problem on the Azure side. We have no ETA and network issues of that kind are out of our scope, so we handed over this issue to the Azure support team.
If you have any other questions do not hesitate to reach us.

Thank you I didn't know what to do w what's being enumerated between notebook & S21, some bloat, scripts, apk mirrors & xml idk what to. Thank you again.   HT Fudge. On Feb 23, 2023 10:02 AM, Alexey-Ayupov @.***> wrote:
I have compared your tcp dumps, and my doubts were confirmed. The only problem I can see is in the DNS protocol communication. I tried to resolve some DNS names on ubuntu 20.04 and 22.04 the results are the same, both OSes resolve sites correctly. Since you are using the "poetry" utility it can be a problem between it and the OS level, or possibly it can be a problem on the Azure side. We have no ETA and network issues of that kind are out of our scope, so we handed over this issue to the Azure support team.
If you have any other questions do not hesitate to reach us.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>


Added Q measurements to DV Hydrographs. Also consolidated data parsing

for ground water data between DV/UV hydrograph and 5yr reports. NOTE
that the json is changing from "groundWater" to "gwLevel".

Coverage remained the same at 86.141% when pulling 528bd884f228ede5c0db1b34608078009f8a3f21 on thongsav-usgs:master into 95b9c637894c2b5e07aa96a6c647432903d980cb on USGS-R:master.

Coverage remained the same at 86.141% when pulling 990e7ab7969d5558dba4e6fe6fceffd8c16c04d9 on thongsav-usgs:master into 95b9c637894c2b5e07aa96a6c647432903d980cb on USGS-R:master.

@thongsav-usgs there are huge chunks that are shown as added/deleted, so I am having troubling figuring out what has changed. You added: getGroundWaterLevels and getFieldVisitMeasurementsQPoints? Both are used in dvhydro, but only getGroundWaterLevels is used in fiveyrgwsum. Is that correction?

@lindsaycarr getGWL is used in all 3 (DV/UV/5yr), the getFVM used in UV and DV.
Pretty much any function in uvhydro-data that was pulling common data elements, I moved into util-shared.R
Do we want a data specific shared util file?

hmm well the utils-shared.R I think could be named better. All the util-[].R files are for shared utilities, so that name is pointless (I named it so I feel okay pointing out its uselessness). I think the data parsing functions are currently in utils-json. I would rename that to utils-data and consider migrating stuff from utils-shared into that.

Let's hold off and do a non-functional refactor later without any feature changes involved so we can isolate that.


json_dumps function not working correctly

I have been using this library for a while. When i was using json_dumps function it was throwing garbage in the end of buffer. I reduced my JSON_INDENT from 4 to 2. it got fixed.
In another case i have two 2 string items in the array (confirmed with  json_array_size).  when i do
json_dumps(json_array_get(json_ret, 1), JSON_INDENT(2));

It returning NULL value. I am using latest version.

You need to use the JSON_ENCODE_ANY flag with json_dumps() to encode a plain string. RFC 4627 (the old JSON spec) says that objects and arrays are the only valid top-level values.
This will requirement will probably be lifted in the future because RFC 7159 (the new spec) doesn't have this requirement anymore.
What comes to garbage produced by json_dumps(), I'd like to have more information. Could you post an example that reproduces the issue?

I'm having the same problem trying to print a json object with json_dumpf(). I've tested 0-5. 0-3 works fine, 4-5 randomly produces garbled output. Happens about 1 in 5 times.
Running with valgrind --leak-check=full --show-leak-kinds=all fixes the garbled output, but no errors are logged.
Output and diff:
https://gist.github.com/nfnty/2db2bf1de27e1bae2872
Code:
https://github.com/nfnty/bspwm/blob/master/messages.c#L663-L705
https://github.com/nfnty/bspwm/blob/master/query.c#L36-L247

The dump_indent function that writes the indentation whitespace is here: https://github.com/akheron/jansson/blob/master/src/dump.c#L46-L69. I don't see how it could output garbage, unless the static whitespace buffer has been overwritten because of a buffer overrun.
You could add a guard in the beginning of dump_indent to check whether whitespace contains 32 spaces. But even if it doesn't, it might be hard to find out why.


command subscription-send does not support option -t / --Type

Bug Description
In DSpace CRIS 2022.03 the option -t / --Type was supported in the subscription-send command. The DS CRIS 2023.01 documentation still describes this parameter at page 78.

-t or --Type representing notification type to be sent, one between "content" and "statistics"

The option was removed in the code base in December 2022.
Currently (in DS CRIS 2023.01), the command execution throws an exception if option -t is used:
$ ./dspace subscription-send -f D -t content
org.apache.commons.cli.UnrecognizedOptionException: Unrecognized option: -t

Hello, this issue has been solved with commit https://github.com/4Science/DSpace/commit/191ac97dbc2fa4e1dc15e5f17887c3334d450757


Any way to automatically upload to Notion?

Is it possible to make any modifications to this code so that it can maybe interact with notion API and upload the kindle highlights directly to my library on Notion? That would be so cool and time-saving.

As of now, myself I modified to remove the ---\n and then I copie paste the whole into a Code Block in Notion so it keeps the structure. Then I modify to Text Block et voilà.


Ordering keys in the yaml dump

When using the to_yaml function of Workflows, it results in unnatural ordering, in particular relating to Task objects
with Workflow(
   ...
) as w:
    a = Task(
        name="entrypoint",
        command=["python", "-c"],
        args=["print('Hello, a!')"],
    )

w.to_yaml()

Gets yaml for the entrypoint task template:
  templates:
  - container:
      args:
      - print('Hello, a!')
      command:
      - python
      - -c
      image: python:3.7
    name: entrypoint

Where name comes after the container definition. Is there a way or could we add some way to manually order the yaml spec?

Thanks for bringing it up @elliotgunton! Can totally see how this can affect the user experience. Any thoughts on the ordering problem you mentioned? Perhaps there's a common set of keys to always "keep at the top"?


Update CONTRIBUTORS.md

Hey @rabby420
Thanks for your PR & contribution :wave:!
Don't forget to join follow me, join our organization, & follow our organization to stay updated with the latest developments 💻
Thank you, and have a good day ahead 😊


Add regular DB backups

We should have something like a Cron job to regularly store a full DB backup to GCS (e.g. once a day).
We should also have monitoring to alert us in case the backups don't happen.
Once a year we should try disaster recovery by completely restoring the DB to a new instance.

@vivbak, how's your documentation for this going?

Aloha, nearly ready for review :)
https://github.com/populationgenomics/sample-metadata/pull/6

Now that we're relying on the metadata server for seqr (yay!), we should make sure that the backups are working as soon as possible.

Hi @lgruen :) As an update, most of this is done. You can find the update script here #9.
I'll prioritize the DR documentation this week.

Excellent, thanks!!

Hey @vivbak, I think this task has been actioned, are we right to close the issue?

oh, yup :) Addressed in #28


Append -js to container image name

Change the container image name to lightbend-docker-registry.bintray.io/cloudstate-samples/shopping-cart-js to distinguish it from other shopping cart samples.

Java shopping cart image name needs to be changed as well: cloudstateio/samples-java-shoppingcart#12

@pvlugter, there could be more than one service per repository, as in https://github.com/cloudstateio/samples-js-chat and https://github.com/cloudstateio/samples-ts-shoppingcart/tree/inventory
So we cannot always have 1:1 correspondence between a repo and an image.
However, we can use the sample-<lang>-<service_name> pattern instead of <service_name>-<lang> for images.

@pvlugter, the sample images are in the lightbend-docker-registry.bintray.io/cloudstate-samples/ image repo, so we already have sample in the image name.

Hmm, there are some old images hosted at https://hub.docker.com/u/cloudstateio as well.

According to @michaelpnash, all the sample images should be hosted on the bintray repo.
I'm merging this PR as is, since it is blocking images upload. We can easily change the name again later.


UAR-1289 Remove confirmation details for a change journey

JIRA link
https://companieshouse.atlassian.net/browse/UAR-1289
Change description

If entity (not agent) details supplied, confirmation screen text now correct
A new specific test added for this and some extra assertions added to an existing test

Work checklist

[X] Tests added where applicable
[ ] UI changes meet accessibility criteria

Merge instructions
We are committed to keeping commit history clean, consistent and linear.  A BREAKING CHANGE can be part of commits of any type,
types other than fix: and feat: are allowed, for example build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others,
footers other than BREAKING CHANGE: <description> may be provided.

https://companieshouse.atlassian.net/browse/UAR-1289

Yep, delivered by UAR-1288, the first story of this trilogy I did.


feat(parameters): ability to set maxAge and decrypt via environment variables

Description of your changes
This PR introduces two new environment variables to configure the behavior of the Parameters utility around caching (maxAge) and decryption (for SSM only).
Problem statement
Today the utility allows customers to configure caching and decryption via arguments passed to the utility functions or class methods. This allows to configure the retrieval and lifecycle of parameter values in a granular way.
Some customers however want to have shared settings that apply to all parameter values. For this reason we are adding two environment variables: POWERTOOLS_PARAMETERS_MAX_AGE and POWERTOOLS_PARAMETERS_SSM_DECRYPT that once set will apply to all parameter retrievals.
Additional info on the changes
Prior to this PR the Parameters utility was using environment variables only in one instance and only in the AppConfigProvider. With the introduction of these new environment variables this PR adds the EnvironmentVariablesService from the commons package to this library. With this service the Parameters utility has now access to shared utilities that allow to read and standardize the env vars retrieval.
Once merged this PR will close #1380.
Related issues, RFCs

Issue number: #1380
Checklist

[x] My changes meet the tenets criteria
[x] I have performed a self-review of my own code
[x] I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] I have made corresponding changes to the examples
[x] My changes generate no new warnings
[x] The code coverage hasn't decreased
[x] I have added tests that prove my change is effective and works
[x] New and existing unit tests pass locally and in Github Actions
[x] Any dependent changes have been merged and published
[x] The PR title follows the conventional commit semantics

Breaking change checklist
Is it a breaking change?: NO

[ ] I have documented the migration process
[ ] I have added, implemented necessary warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

cc @heitorlessa - would like your input on env variables naming. Ideally I'd want to use the same names across runtimes so let's agree now if possible.
If not, we still have time to change the names on our side before GA.

Happy with the env var name 👏
On Wed, 29 Mar 2023 at 21:11, Alexander Schueren @.***>
wrote:

@.**** approved this pull request.
Looks good.
—
Reply to this email directly, view it on GitHub
https://github.com/awslabs/aws-lambda-powertools-typescript/pull/1384#pullrequestreview-1363785156,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZPQBGEKBKH3YFQJMV2H6DW6SCOJANCNFSM6AAAAAAWK3EC6Y
.
You are receiving this because you were mentioned.Message ID:
<awslabs/aws-lambda-powertools-typescript/pull/1384/review/1363785156@
github.com>


Could not resolve io.flutter:flutter_embedding_debug:1.0.0

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'.
> Could not resolve all task dependencies for configuration ':app:debugCompileClasspath'.
   > Could not resolve io.flutter:flutter_embedding_debug:1.0.0-3953c3ccd15a54a0718700aa11ead664b264b7dd.
     Required by:

 Could not resolve io.flutter:flutter_embedding_debug:1.0.0-3953c3ccd15a54a0718700aa11ead664b264b7dd.
         > Could not get resource 'https://https/storage.flutter-io.cn/download.flutter.io/io/flutter/flutter_embedding_debug/1.0.0-3953c3ccd15a54a0718700aa11ead664b264b7dd/flutter_embedding_debug-1.0.0-3953c3ccd15a54a0718700aa11ead664b264b7dd.pom'.
            > Could not GET 'https://https/storage.flutter-io.cn/download.flutter.io/io/flutter/flutter_embedding_debug/1.0.0-3953c3ccd15a54a0718700aa11ead664b264b7dd/flutter_embedding_debug-1.0.0-3953c3ccd15a54a0718700aa11ead664b264b7dd.pom'.
               > Remote host closed connection during handshake

the url in error log was wrong...
https://https/storage.flutter-io.cn/download.flutter.io/io/flutter/flutter_embedding_debug/1.0.0-3953c3ccd15a54a0718700aa11ead664b264b7dd/flutter_embedding_debug-1.0.0-3953c3ccd15a54a0718700aa11ead664b264b7dd.pom

Flutter (Channel dev, 1.19.0-0.0.pre, on Mac OS X 10.15.1 19B88, locale zh-Hans-CN)

Hi @wasabia
have you configured a mirror site as here https://flutter.dev/community/china#configuring-flutter-to-use-a-mirror-site?
> Could not GET link doesn't look correct, there should be https://storage.flutter-io.cn instead of https://https/storage.flutter-io.cn

I encoutered the same problem on the github pre version, so I switch to the 1.17 stable version which works just fine.

possible dupe for https://github.com/flutter/flutter/issues/56861

@VladyslavBondarenko
echo $FLUTTER_STORAGE_BASE_URL

https://storage.flutter-io.cn

for me this error just happened on
Flutter (Channel dev, 1.19.0-0.0.pre, on Mac OS X 10.15.1 19B88, locale zh-Hans-CN)

Hi @wasabia
can you please provide your complete flutter doctor -v and flutter run --verbose?

Possibly a duplicate of https://github.com/flutter/flutter/issues/56861

Without additional information we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


stack_size_test02 redundant or incomplete (same as test01 currently)

$ diff stack_size_test01/main.c stack_size_test02/main.c returns nothing :)

Well the readme says it tests different stack sizes, which are specified in the Makefile, which are different between the two apps.


Update requirements.txt

added manifest tool version tag

let's put this one now in and I'll go thru the rest of the dependencies later on


Fix bug in DevOps logging command

Use the correct syntax for debug logging in DevOps.

/check-enforcer override


bug: Pagination Section Cursor Issue

Description
The pagination section is currently displaying a default cursor on hover instead of a pointer cursor, which can lead to confusion regarding the interactivity of the buttons.
Steps to reproduce

Navigate to the landing page.
Scroll to the bottom of the page to locate the Pagination Section.
Hover over the "Prev," "Next," and other page buttons.
Observe that the cursor remains as a default arrow instead of changing to a pointer.

Current Behaviour (Default cusor on hover)
The cursor does not change on hover, indicating that the buttons are not interactive.

Expected Behaviour
The cursor should change to a pointer when hovering over pagination buttons, indicating that they are clickable.

Solution
Adding cursor-pointer class to <PaginationItem/> in LandingScreen

But, the pagination does not work on clicking those buttons, also all the tracks are loaded with scroll, thus pagination is not required
Either one of the should be implemented
https://github.com/code100x/daily-code/issues/651

@jals413 I agree. I will think about it and comeup with something

https://github.com/code100x/daily-code/pull/652
I have created a PR for removing pagination as it does not make any sense here, if you feel so you can merge it.

Yeah saw that @jals413

@jals413  @devsargam  we need to scroll alot to reach the end of the landing page and I guess its not a good UX and idea to display all the tracks as in the future the no. of tracks gonna increase only.

I agree, but in my opinion if you want to handle pagination it should be handled from BE then only it will make the true sense

yes, that's the optimial way to avoid overfetching


feat: implements upgrade test

Reason for Change:

Implements upgrade tests to validate backward compatibility.

Requirements

[ ] squashed commits
[ ] included documentation
[ ] added unit tests and e2e tests (if applicable).

Issue Fixed:

https://github.com/Azure/secrets-store-csi-driver-provider-azure/issues/305
Does this change contain code from or inspired by another project?

[ ] Yes
[x] No

If "Yes," did you notify that project's maintainers and provide attribution?
Special Notes for Reviewers:

Codecov Report

Merging #489 (15bc7ff) into master (dead813) will not change coverage.
The diff coverage is n/a.


File Upload using S3

When you using s3 for file upload and managing access via AWS policies and if disk visibility is public file upload will fail silently.

I made PR to export visibility method https://github.com/eighty9nine/filament-excel-import/pull/19


support for user defined middleware

I would like to load some ws-specific middleware when starting the websockets server. Goal is to log connections within a database. As the database config is dynamic i would like to have a middleware which writes the connection details to config('database.connections'). Someone an idea how to accomblish this?

config/websockets.php
...
'middleware' => [
        // Authorize::class,
],
...


Add python 3.x support

This module will not work under python 3.x at least because of import urlparse which replaced by urllib.parse.urlparse in 3.x

I'll accept any PR, I'm not currently using this in anything. :P


Transformer utils

This PR includes the new activation function for structure-preserving transformers (orthonormal_activation_cayley) and also some utils that make it easier to handle data in tensor form (folder data_loader; we should probably give this a different name).

Please remove the images from the commit and in general make sure not to check in binary files (images, hdf5, jld2).

Removed binary files and orthonormal_activation_old.


Recommendation 3.7: Usage of whitespace for code separation

Any keywords (like 'if', 'when', 'for', e.t.c) should be separated with a single whitespace from the opening parenthesis.
Only exceptions are: 'super' and 'constructor' keywords. They should not be separated from a parenthesis.

Separate any keywords (such as else or catch, etc.) from the opening brace ('{') with a single whitespace.

Use single whitespace before any opening brace ({).
Only exception is passing a lambda as an argument inside parenthesis:
    private fun foo(a: (Int) -> Int, b: Int) {}
    foo({x: Int -> x}, 5) // no space before '{'

Single whitespace should be placed on both sides of binary operators. This also applies to operator-like symbols, for example:

Colon in generic structures with 'where' keyword： where T : Type
Arrow in lambdas： (str: String) -> str.length()

Exceptions：

Two colons (::) are written without spaces: Object::toString
Dot separator (.) that stays on the same line with an object name: object.toString()

Spaces should be used after ',',':',';' (except cases when those symbols are in the end of line). There should be no whitespaces in the end of line.

There should be only one space between identifier and it's type： list: List<String>

When using '[]' operator (get/set) there should be no spaces between identifier and '[': someList[0]

There should be no space between a method name and a parenthesis: foo() {}

I believe in koltin super keyword cannot have parentheses after it.


Medieval Weapons Incompatability

Mod Name
Medieval Weapons
Mod Homepage
https://www.curseforge.com/minecraft/mc-mods/medievalweapons
Describe the bug
Game crashes when the mod and its dependencies is placed in the mods folder, along with connector and connector extras.
Steps to reproduce

...
Logs
https://pastebin.com/XiHebiwk
Additional context
No response

Looks like a weird interaction between medieval weapons and reach entity attributes (which is loaded from connector extras)


Engineer - ProdOps-SDK-Elixir Release - Publish on Hex

Background
Prepare the ProdOps-SDK-Elixir for release on Hex package manager.
Acceptance Criteria
Scenario: Packaging and publishing ProdOps-SDK-Elixir to Hex

[ ] Given the ProdOps-SDK-Elixir code is reviewed and all tests pass
[ ] When I package the SDK following Hex specifications for publishing
[ ] Then the SDK should be published on Hex.pm under the name "ProdOpsEx"
[ ] And the version number, dependencies, and documentation are accurately reflected
[ ] And the package is installable via mix deps.get by users.

created by<EMAIL_ADDRESS>using Prodops

I made changes so this runs against the newest and oldest supported version of Elixir we want to allow, and set up a GitHub action to do the publishing to hex. Will need to actually run it an make sure it works, but if so I think this will be all done.

This is now published! Docs are here: https://hexdocs.pm/prodops_ex/0.1.0/readme.html


Add Chau Van Liem high school

School official website: https://chauvanliem.edu.vn/
School on Wikipedia (in Vietnamese): https://vi.wikipedia.org/wiki/Trường_Trung_học_phổ_thông_Châu_Văn_Liêm,_Cần_Thơ

@tamhac2001 Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Enable px4io on pi 2

Enable px4io
I will still optimize the IRQ load by using rx buffer threshold interrupt, when the threshold is freely settable in the fpga uart block

Removed extra mutual exclusion, it was already managed in src/drivers/px4io common code, no need to do it in _bus_exchange.

Still fixed the uart baud rate calculation. It was a copy paste from mpfs_serial.c, and looked very strange to me...

Added critical section around uart tx fifo fill; the px4io expects to get the bytes in one burst. A break in there will timeout the px4io dma and cause error


docs(v2): fix typo in plugin-content-pages example

fixed grammar error in @docusaurus/plugin-content-pages example from 'blog' to 'page'

Motivation
While reading through the docs I found a small grammar error here: #docusaurusplugin-content-pages
I've concluded it to be a grammar error due to the fact that we see the exact same sentence in the blog example.

Have you read the Contributing Guidelines on pull requests?
Yes, small change. 👍
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work. Bonus points for screenshots and videos!)
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

Thank you!

Could you also make the change to the the corresponding file in website/docs?

@yangshun sure thing!


Installing via homebrew also installs Go via homebrew

What version of Delve are you using (dlv version)?

homebrew package "stable 1.0.0-rc.1, HEAD"

What version of Go are you using? (go version)?

go version go1.7.6 darwin/amd64

What operating system and processor architecture are you using?

macOS Sierra

What did you do?

$ brew install go-delve/delve/delve

What did you expect to see?

go-delve installed via homebrew

What did you see instead?

go-delve and Go installed via homebrew, overwriting my install of the official Go package.
Possibly this is a bug in homebrew, or homebrew's Go package (why did it overwrite my official Go install without asking? why can't it detect official Go installations as surrogates for homebrew installations?). Possibly this is a bug in delve's package. But at the least, it would be nice to have a warning in the installation docs that the homebrew install will also install Go via homebrew.

Duplicate of https://github.com/go-delve/homebrew-delve/issues/9


Final SETI addition to CKAN for the current project

Self-administered netkan file as usual.
Thank you and best regards,
Yemo

Merging with thanks!


Add support for specular tints and maps per the KHR_materials_specular glTF extension.

This commit allows specular highlights to be tinted with a color and for the reflectance and color tint values to vary across a model via a pair of maps. The implementation follows the KHR_materials_specular glTF extension. In order to reduce the number of samplers and textures in the default StandardMaterial configuration, the maps are gated behind the pbr_specular_textures Cargo feature.
Specular tinting is currently unsupported in the deferred renderer, because I didn't want to bloat the deferred G-buffers. A possible fix for this in the future would be to make the G-buffer layout more configurable, so that specular tints could be supported on an opt-in basis. As an alternative, Bevy could force meshes with specular tints to render in forward mode. Both of these solutions require some more design, so I consider them out of scope for now.
Note that the map is a specular map, not a reflectance map. In Bevy and Filament terms, the reflectance values in the specular map range from [0.0, 0.5], rather than [0.0, 1.0]. This is an unfortunate KHR_materials_specular specification requirement that stems from the fact that glTF is specified in terms of a specular strength model, not the reflectance model that Filament and Bevy use. A workaround, which is noted in the StandardMaterial documentation, is to set the reflectance value to 2.0, which spreads the specular map range from [0.0, 1.0] as normal.
The glTF loader has been updated to parse the KHR_materials_specular extension. Note that, unless the non-default pbr_specular_textures is supplied, the maps are ignored. The specularFactor value is applied as usual. Note that, as with the specular map, the glTF specularFactor is twice Bevy's reflectance value.
This PR adds a new example, specular_tint, which demonstrates the specular tint and map features. Note that this example requires the KHR_materials_specular Cargo feature.
Changelog
Added

Specular highlights can now be tinted with the specular_tint field in StandardMaterial.
Specular maps are now available in StandardMaterial, gated behind the pbr_specular_textures Cargo feature.
The KHR_materials_specular glTF extension is now supported, allowing for customization of specular reflectance and specular maps. Note that the latter are gated behind the pbr_specular_textures Cargo feature.

@JMS55 I thought glTF spec compliance was a goal, though?

Ehh, kinda? It lets us import stuff from blender better, yeah. But it's not necessarily the best option. The paper I linked has a really nice parameterization of edge tints.
But I haven't looked at the gltf spec for this specifically so up to you.