YARN-9591 Expand all entries in JAR archive

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
42
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

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

_ trunk Compile Tests _

+1
mvninstall
1161
trunk passed

+1
compile
1125
trunk passed

+1
checkstyle
42
trunk passed

+1
mvnsite
82
trunk passed

+1
shadedclient
834
branch has no errors when building and testing our client artifacts.

+1
javadoc
78
trunk passed

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

+1
findbugs
143
trunk passed

_ Patch Compile Tests _

+1
mvninstall
60
the patch passed

+1
compile
1434
the patch passed

+1
javac
1434
the patch passed

-0
checkstyle
51
hadoop-common-project/hadoop-common: The patch generated 2 new + 6 unchanged - 0 fixed = 8 total (was 6)

+1
mvnsite
93
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
781
patch has no errors when building and testing our client artifacts.

+1
javadoc
73
the patch passed

+1
findbugs
146
the patch passed

_ Other Tests _

+1
unit
632
hadoop-common in the patch passed.

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

6956

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/hadoop-multibranch/job/PR-897/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/897

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux b034ab1f0459 3.13.0-153-generic #203-Ubuntu SMP Thu Jun 14 08:52:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / bd2590d

Default Java
1.8.0_212

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/1/artifact/out/diff-checkstyle-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/1/testReport/

Max. process+thread count
1346 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/1/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

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
99
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

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

_ trunk Compile Tests _

+1
mvninstall
1230
trunk passed

+1
compile
1192
trunk passed

+1
checkstyle
47
trunk passed

+1
mvnsite
97
trunk passed

+1
shadedclient
910
branch has no errors when building and testing our client artifacts.

+1
javadoc
66
trunk passed

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

+1
findbugs
132
trunk passed

_ Patch Compile Tests _

+1
mvninstall
55
the patch passed

+1
compile
1044
the patch passed

+1
javac
1044
the patch passed

-0
checkstyle
44
hadoop-common-project/hadoop-common: The patch generated 2 new + 6 unchanged - 0 fixed = 8 total (was 6)

+1
mvnsite
88
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
806
patch has no errors when building and testing our client artifacts.

+1
javadoc
67
the patch passed

+1
findbugs
148
the patch passed

_ Other Tests _

-1
unit
559
hadoop-common in the patch failed.

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

6687

Reason
Tests

Failed junit tests
hadoop.security.TestFixKerberosTicketOrder

Subsystem
Report/Notes

Docker
Client=18.09.7 Server=18.09.7 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-897/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/897

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

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

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 6282c02

Default Java
1.8.0_212

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/2/artifact/out/diff-checkstyle-hadoop-common-project_hadoop-common.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/2/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/2/testReport/

Max. process+thread count
1343 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/2/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
42
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

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

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

_ trunk Compile Tests _

+1
mvninstall
1061
trunk passed

+1
compile
1084
trunk passed

+1
checkstyle
39
trunk passed

+1
mvnsite
73
trunk passed

+1
shadedclient
773
branch has no errors when building and testing our client artifacts.

+1
javadoc
59
trunk passed

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

+1
findbugs
125
trunk passed

_ Patch Compile Tests _

+1
mvninstall
51
the patch passed

+1
compile
991
the patch passed

+1
javac
991
the patch passed

-0
checkstyle
35
hadoop-common-project/hadoop-common: The patch generated 2 new + 6 unchanged - 0 fixed = 8 total (was 6)

+1
mvnsite
67
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
625
patch has no errors when building and testing our client artifacts.

+1
javadoc
59
the patch passed

+1
findbugs
127
the patch passed

_ Other Tests _

+1
unit
515
hadoop-common in the patch passed.

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

5843

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-897/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/897

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

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

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / c0a0c35

Default Java
1.8.0_212

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/3/artifact/out/diff-checkstyle-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/3/testReport/

Max. process+thread count
1380 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/3/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
85
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

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

_ trunk Compile Tests _

+1
mvninstall
1216
trunk passed

+1
compile
1141
trunk passed

+1
checkstyle
45
trunk passed

+1
mvnsite
89
trunk passed

+1
shadedclient
884
branch has no errors when building and testing our client artifacts.

+1
javadoc
69
trunk passed

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

+1
findbugs
143
trunk passed

_ Patch Compile Tests _

+1
mvninstall
60
the patch passed

+1
compile
1063
the patch passed

+1
javac
1063
the patch passed

-0
checkstyle
42
hadoop-common-project/hadoop-common: The patch generated 2 new + 6 unchanged - 0 fixed = 8 total (was 6)

+1
mvnsite
80
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
745
patch has no errors when building and testing our client artifacts.

+1
javadoc
71
the patch passed

+1
findbugs
150
the patch passed

_ Other Tests _

+1
unit
608
hadoop-common in the patch passed.

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

6600

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-897/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/897

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

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

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / e20b195

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/4/artifact/out/diff-checkstyle-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/4/testReport/

Max. process+thread count
1344 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/4/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
45
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

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

_ trunk Compile Tests _

+1
mvninstall
1147
trunk passed

+1
compile
1164
trunk passed

+1
checkstyle
43
trunk passed

+1
mvnsite
84
trunk passed

+1
shadedclient
869
branch has no errors when building and testing our client artifacts.

+1
javadoc
71
trunk passed

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

+1
findbugs
142
trunk passed

_ Patch Compile Tests _

+1
mvninstall
56
the patch passed

+1
compile
1250
the patch passed

+1
javac
1250
the patch passed

-0
checkstyle
41
hadoop-common-project/hadoop-common: The patch generated 2 new + 6 unchanged - 0 fixed = 8 total (was 6)

+1
mvnsite
77
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
721
patch has no errors when building and testing our client artifacts.

+1
javadoc
73
the patch passed

+1
findbugs
148
the patch passed

_ Other Tests _

+1
unit
594
hadoop-common in the patch passed.

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

6640

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-897/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/897

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

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

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 70b4617

Default Java
1.8.0_212

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/5/artifact/out/diff-checkstyle-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/5/testReport/

Max. process+thread count
1380 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/5/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
40
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

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

_ trunk Compile Tests _

+1
mvninstall
1064
trunk passed

+1
compile
1039
trunk passed

+1
checkstyle
39
trunk passed

+1
mvnsite
71
trunk passed

+1
shadedclient
751
branch has no errors when building and testing our client artifacts.

+1
javadoc
54
trunk passed

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

+1
findbugs
109
trunk passed

_ Patch Compile Tests _

+1
mvninstall
44
the patch passed

+1
compile
1011
the patch passed

+1
javac
1011
the patch passed

-0
checkstyle
48
hadoop-common-project/hadoop-common: The patch generated 2 new + 6 unchanged - 0 fixed = 8 total (was 6)

+1
mvnsite
74
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
679
patch has no errors when building and testing our client artifacts.

+1
javadoc
72
the patch passed

+1
findbugs
127
the patch passed

_ Other Tests _

+1
unit
526
hadoop-common in the patch passed.

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

5881

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-897/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/897

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

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

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 397a563

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/6/artifact/out/diff-checkstyle-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/6/testReport/

Max. process+thread count
1444 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/6/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
62
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

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

_ trunk Compile Tests _

+1
mvninstall
1114
trunk passed

+1
compile
1151
trunk passed

+1
checkstyle
39
trunk passed

+1
mvnsite
70
trunk passed

+1
shadedclient
761
branch has no errors when building and testing our client artifacts.

+1
javadoc
61
trunk passed

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

+1
findbugs
115
trunk passed

_ Patch Compile Tests _

+1
mvninstall
44
the patch passed

+1
compile
1080
the patch passed

+1
javac
1080
the patch passed

-0
checkstyle
38
hadoop-common-project/hadoop-common: The patch generated 2 new + 6 unchanged - 0 fixed = 8 total (was 6)

+1
mvnsite
67
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
643
patch has no errors when building and testing our client artifacts.

+1
javadoc
60
the patch passed

+1
findbugs
128
the patch passed

_ Other Tests _

+1
unit
524
hadoop-common in the patch passed.

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

6066

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-897/7/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/897

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

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

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / e356e4f

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/7/artifact/out/diff-checkstyle-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/7/testReport/

Max. process+thread count
1383 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/7/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
122
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

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

_ trunk Compile Tests _

+1
mvninstall
1360
trunk passed

+1
compile
1300
trunk passed

+1
checkstyle
55
trunk passed

+1
mvnsite
101
trunk passed

+1
shadedclient
1024
branch has no errors when building and testing our client artifacts.

+1
javadoc
84
trunk passed

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

+1
findbugs
146
trunk passed

_ Patch Compile Tests _

+1
mvninstall
54
the patch passed

+1
compile
1107
the patch passed

+1
javac
1107
the patch passed

-0
checkstyle
42
hadoop-common-project/hadoop-common: The patch generated 2 new + 6 unchanged - 0 fixed = 8 total (was 6)

+1
mvnsite
73
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
721
patch has no errors when building and testing our client artifacts.

+1
javadoc
63
the patch passed

+1
findbugs
129
the patch passed

_ Other Tests _

+1
unit
621
hadoop-common in the patch passed.

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

7106

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-897/8/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/897

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 8a4201f6b949 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 094d736

Default Java
1.8.0_212

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/8/artifact/out/diff-checkstyle-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/8/testReport/

Max. process+thread count
1346 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/8/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
45
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

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

_ trunk Compile Tests _

+1
mvninstall
1219
trunk passed

+1
compile
1244
trunk passed

+1
checkstyle
44
trunk passed

+1
mvnsite
86
trunk passed

+1
shadedclient
825
branch has no errors when building and testing our client artifacts.

+1
javadoc
64
trunk passed

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

+1
findbugs
139
trunk passed

_ Patch Compile Tests _

+1
mvninstall
61
the patch passed

+1
compile
1261
the patch passed

+1
javac
1261
the patch passed

-0
checkstyle
47
hadoop-common-project/hadoop-common: The patch generated 2 new + 6 unchanged - 0 fixed = 8 total (was 6)

+1
mvnsite
74
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
674
patch has no errors when building and testing our client artifacts.

+1
javadoc
66
the patch passed

+1
findbugs
150
the patch passed

_ Other Tests _

+1
unit
604
hadoop-common in the patch passed.

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

6707

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-897/9/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/897

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

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

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 69ddb36

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/9/artifact/out/diff-checkstyle-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/9/testReport/

Max. process+thread count
1449 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/9/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
39
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

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

_ trunk Compile Tests _

+1
mvninstall
1091
trunk passed

+1
compile
1046
trunk passed

+1
checkstyle
52
trunk passed

+1
mvnsite
83
trunk passed

+1
shadedclient
829
branch has no errors when building and testing our client artifacts.

+1
javadoc
71
trunk passed

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

+1
findbugs
125
trunk passed

_ Patch Compile Tests _

+1
mvninstall
47
the patch passed

+1
compile
974
the patch passed

+1
javac
974
the patch passed

-0
checkstyle
48
hadoop-common-project/hadoop-common: The patch generated 2 new + 6 unchanged - 0 fixed = 8 total (was 6)

+1
mvnsite
81
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
720
patch has no errors when building and testing our client artifacts.

+1
javadoc
72
the patch passed

+1
findbugs
130
the patch passed

_ Other Tests _

+1
unit
541
hadoop-common in the patch passed.

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

6078

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-897/10/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/897

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

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

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 3329257

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/10/artifact/out/diff-checkstyle-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/10/testReport/

Max. process+thread count
1526 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/10/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
41
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

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

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

_ trunk Compile Tests _

+1
mvninstall
1071
trunk passed

+1
compile
1015
trunk passed

+1
checkstyle
49
trunk passed

+1
mvnsite
85
trunk passed

+1
shadedclient
816
branch has no errors when building and testing our client artifacts.

+1
javadoc
68
trunk passed

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

+1
findbugs
124
trunk passed

_ Patch Compile Tests _

+1
mvninstall
47
the patch passed

+1
compile
968
the patch passed

+1
javac
968
the patch passed

-0
checkstyle
47
hadoop-common-project/hadoop-common: The patch generated 2 new + 6 unchanged - 0 fixed = 8 total (was 6)

+1
mvnsite
82
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
675
patch has no errors when building and testing our client artifacts.

+1
javadoc
69
the patch passed

+1
findbugs
131
the patch passed

_ Other Tests _

+1
unit
554
hadoop-common in the patch passed.

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

5972

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-897/11/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/897

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

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

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 915cbc9

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/11/artifact/out/diff-checkstyle-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/11/testReport/

Max. process+thread count
1394 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-897/11/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

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

This message was automatically generated.


Log In with GitHub error

This could be a temporary issue, but this is what I am getting on prod (preview.boost.org) when trying to connect with GitHub right now.
The URL that gives this response is .. oh.  Now the error makes sense.  We should probably try to prevent this from happening. :grinning:
https://www.preview.boost.[encoded data, 5644 characters]

@4down , I have seen that error happen when the web URL was different than expected. (stage instead of preview), after the production database was imported to staging.
However in this case, could it be due to having multiple social auth accounts?  You are in the database with both "GitHub" and "Google".   Try using the other one.

This issue is resolved now.  Not an issue that we would ever see in the wild, so there is no reason to try to catch this error.  (the problem was created from syncing databases between servers)

see #815

this happened on stage, and was fixed by manually resetting the socal auth id and key after imported the production db.


Add DDL support to SQL Transform

This is a simple answer to the question: "How do I use beam SQL in Java", which does not currently exist outside of "impl" packages.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @amaliujia

It will be interesting to see how to have a unified way to run DDL(including creating UDF) for both dialects.


Uses libpq

Hello,
I wrote this safe crate for pq-sys.

Without wanting to criticize your work I see several major points that are against this change:

It replace a lot of reviewed unsafe code that we known to be in a good state with third party crate that contains bigger amounts of unreviewed unsafe code. (According to a quick grep diesel uses 29 unsafe blocks as part of the postgres connection implementation, while libpq.rs contains 133 unsafe blocks). Additionally with only looking roughly over the corresponding code, I've found already [one](https://github.com/sanpii/libpq.rs/blob/35a7acb014c11b5485ec7d83948fb58f896564e0/src/connection/mod.rs#L21) safety critical soundness issue. (libpq [does not allow](https://www.postgresql.org/docs/current/libpq-threading.html) issuing commands from multiple threads at the same time. Implementing Syncfor theConnection` type would exactly allow that.
The libpq crate has a bus factor of 1 and we do not control this code
It enlarges our dependency tree by adding another bigger dependency
Unknown impact on the performance of PgConnection

To summarize the points above: I'm not in favor of this change

I like the intention behind this but I agree with the unsafe issue pointed out above.


DOM renderer

Lots here!

[x] Basic setup
[x] root
[x] applyFont
[ ] component basics
[ ] Live tests with rollup
[ ] CSS parser
[ ] Finish up component

Superseded by https://github.com/Vehmloewff/versatile-dom-renderer/pull/1


docker run

How dowload image ?

There is currently no direct support for Docker. That said...Docker is used in CI for testing, so you could look here and implement your own Dockerfile based off of this.


How to get the training and validation losses and metrics per iteration

This package is very useful. I am amazed at how much faster I can train the multi-label SketchBoost classifier compared to a (one-vs-all) XGBoost classifier.
However, I was wondering, is there any way to retrieve the training and validation losses and metrics for each iteration in a training run for later use? I would like to save these KPIs so that I can visualize them in a dashboard.
Currently, it seems that there are some limitations:

losses and metrics per iteration cannot be retrieved as a python object for later use
only one of either (a) the training loss (e.g., 'BCE') or (b) the training evaluation metric (e.g., 'F1_score') are shown in the console log output; both loss and metric are not shown together
validation loss and metric are not shown

I see that the training losses per iteration can be obtained after training from model.history

@adkinsty thanks for your feedback! About your question:

Loss and Metric inside Py-Boost are very different entities (also it is so for each GBDT implementation). Loss should produce the gradeints and hessians for building a tree while Metirc produces the values to show in train log and used for early stopping. For example, when you use BCE to train, there is difference between BCELoss and BCEMetric, but BCEMetric is the default choice of metric for BCELoss if nothing else passed. So now we are discussing only Metric, since we are talking about model evaluation.

From the model.history list and train log you can obtain the results only for datasets, that are passed as the eval_sets to .fit method of both GradientBoosting and SketchBoost. So if you do like model.fit(X, y, eval_sets = [{'X': X_test, 'y': y_test}]) you will see the Metric values on X_test. Unfortunately, you can not use multiple metrics to evaulate here. There is an option to pass multiple datasets to eval_sets list, then the last dataset will be used for early stopping, but from history and log you can obtain the results for all datasets. Metric values for train dataset is not saved since I believe it is not informative value, and it is not good practice to use train/valid gap as overfitting detector

However, if you want to monitor everything, it is definetly possible and below I show you multiple ways to do that from simple to efficient

Train as valid set
First option is to pass train datasets to eval_sets list. It will look like
model.fit(X, y, eval_sets = [{'X': X, 'y': y}, {'X': X_test, 'y': y_test}])

This is obviously unefficient, because GBDT will store on GPU and handle X dataset twice and you still will be able to evaluate only one metric
Predict after train
Second option is using .predict_staged method. It will returns the prediction result from all iterations after model is trained. On prediction results you can evaluate manually all the statistics you want
preds = model.predict_staged(X_test, iterations=[100, 300, 500]) # preds shape is (n_iters, n_samples, n_outputs)

That is the better way especially if you don't need to evaluate every step but only from specific iterations list. But if you need to evaluate each step remember that preds array could be quite large
Callback
The last and actually the best way is writting your own Callback class where you will define what you want to compute and save on fly while model is trained
from py_boost.callbacks.callback import Callback

class MultipleMetricsHistory(Callback):

    def __init__(self, metric_list):

        # assume list of callable(y_true, y_pred)
        self.metric_list = metric_list
        self.history = None

    def before_train(self, build_info):

        self.history = []
        # postprocess fn defined by loss function
        self.postprocess_fn = build_info['model'].loss.postprocess_output

    def after_iteration(self, build_info):

        iter_info = []
        # single train dataset
        train = build_info['data']['train']
        # lists of val datasets
        valid = build_info['data']['valid']
        # calc metric on train data
        y_pred = self.postprocess_fn(train['ensemble'])

        metrics = []
        for fn in self.metric_list:
            metrics.append(float(fn(train['target'], y_pred)))
        iter_info.append(metrics)

        # calc metrics on validation sets
        for y_true, y_pred in zip(valid['target'], valid['ensemble']):
            y_pred = self.postprocess_fn(y_pred)
            metrics = []
            for fn in self.metric_list:
                metrics.append(float(fn(y_true, y_pred)))
            iter_info.append(metrics)

        self.history.append(iter_info)

        return False

    def after_train(self, build_info):

        self.history = np.array(self.history)

history = MultipleMetricsHistory(...) # pass the metric list here
model = GradientBoosting(..., callbacks=[history, ])
model.fit(X, y, eval_sets=[{'X': X_val0, 'y': y_val0}, {'X': X_val1, 'y': y_val1}])

# should contain np.ndarray of size (n_iter, n_datasets, n_metrics)
# n_datasets = n_val_datasets + 1, fist one is train
evals = history.history

So you can try all of that and decide what is your best choice. If you still have any questions I will try to help you

@btbpanda Thanks for the detailed and helpful response!


Port nuki_hub to Olimex ESP32-POE-ISO Board

Hi,
i was wondering porting this app to an Olimex ESP32 PoE Board?
this has several benefits:

LAN Mode with PoE, no need to wire power
All in one Board
No wifi connection drop issues

Unfortunately, the board uses a LAN8710A Chip in RMII Mode for managing Ethernet, which is not supported by the current firmware.
the board is well documentated, maybe we can write a port for this particular board?
the shematic: https://github.com/OLIMEX/ESP32-POE-ISO/blob/master/HARDWARE/ESP32-PoE-ISO-Rev.H/ESP32-PoE-ISO_Rev_H.pdf

Hi, it should be possible to port this to the Olimex board. However, there are quite a few more boards with LAN connectivity and this is a project I'm running and financing privately - I unfortunately can't buy every hardware out there.

yeah, i understand that, no prob.
Maybe i can help you with stuff? i looked into your code, looks like the network stack is "modular", maybe we can write another stack for LAN8710A ?

Sure ... thinking about maybe it's enough to just wire a LAN8710A module the same way it's wired on the board? They are fairly cheap.

should be. i tried flashing the firmware in hope to use the esp32 wifi, but unfortunately, the gpio pin for eth activation (gpio26) is wired to the nic chip. this leads to deactivating the wifi. which IDE do you used for developing this code?

I'm using clion, but if your question is how to compile the code it's a cmake project. Have a look at my other project "coffeetimer", there's a howto for compiling.
Not sure about the GPIO ... I had to pick one so it was 26. We could make it configurable in software, but that has the risk of someone changing to the setting to LAN and then have an ESP that isn't reachable because the hardware is missing.
Maybe have two settings for LAN:

Let the user choose which GPIO switches on LAN
Let the user select a driver

This way also issue #36 could be addressed.

i have no pratical experience with cmake programs. i managed to install arduino sdk, cmake and toolchain, but i got error when trying to compile:
philipp@PF1RKYGV:~/nuki_hub-master$ Picked up JAVA_TOOL_OPTIONS:
cmake -D CMAKE_TOOLCHAIN_FILE=/home/philipp/Arduino-CMake-Toolchain-master/Arduino-toolchain.cmake .
CMake Error at /home/philipp/Arduino-CMake-Toolchain-master/Arduino/System/BoardBuildTargets.cmake:472 (message):
Arduino library BLE could not be found in
/home/philipp/nuki_hub-master;/home/philipp/nuki_hub-master;/home/philipp/Arduino;/home/philipp/.arduino15/packages/esp32/hardware/esp32/1.0.6;/home/philipp/arduino-1.8.19
Call Stack (most recent call first):
/home/philipp/Arduino-CMake-Toolchain-master/Arduino/System/BoardBuildTargets.cmake:713 (find_arduino_library)
/home/philipp/Arduino-CMake-Toolchain-master/Arduino/System/BoardBuildTargets.cmake:680 (_add_internal_arduino_library)
/home/philipp/Arduino-CMake-Toolchain-master/Arduino/System/BoardBuildTargets.cmake:183 (_link_ard_lib_list)
CMakeLists.txt:93 (target_link_arduino_libraries)
CMake Error at /home/philipp/Arduino-CMake-Toolchain-master/Arduino/System/BoardBuildTargets.cmake:166 (message):
DNSServer is not a CMake target
Call Stack (most recent call first):
CMakeLists.txt:111 (target_link_arduino_libraries)
CMake Error at CMakeLists.txt:111 (target_link_arduino_libraries):
cmake_policy PUSH without matching POP
-- Configuring incomplete, errors occurred!
See also "/home/philipp/nuki_hub-master/CMakeFiles/CMakeOutput.log".
See also "/home/philipp/nuki_hub-master/CMakeFiles/CMakeError.log".
any short hint?

you have to checkout with submodules. Run: git submodule update --init --recursive
You should create a subdirectory for building, usually "build":

mkdir build
cd build
cmake -D CMAKE_TOOLCHAIN_FILE=/home/philipp/Arduino-CMake-Toolchain-master/Arduino-toolchain.cmake ..
Also, please use my fork of the arduino toolchain:
https://github.com/technyon/Arduino-CMake-Toolchain
Which version of the Arduino core for ESP32 did you install?

yeah, the toolchain file worked for me. i used esp32 version 1.0.6, because all of the 2.0 vers does not find a suitable CXX compiler:
-- The CXX compiler identification is unknown
CMake Error at CMakeLists.txt:5 (project):
The CMAKE_CXX_COMPILER:
/home/philipp/.arduino15/packages/esp32/tools/xtensa-esp32-elf-gcc/1.22.0-97-gc752ad5-5.2.0/bin/xtensa-esp32-elf-g++

is not a full path to an existing compiler tool.
Tell CMake where to find the compiler by setting either the environment
variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
to the compiler, or to the compiler name if it is in the PATH.
-- Configuring incomplete, errors occurred!
See also "/home/philipp/nuki_hub/build/CMakeFiles/CMakeOutput.log".
See also "/home/philipp/nuki_hub/build/CMakeFiles/CMakeError.log".

i dont get it, now it compiled, but i dont know how to flash it, the directive "upload-nuki_hub" does not work, because no bootloader is generated.
another hint?

Strange with the compiler, I didn't have that problem. Maybe just set a symbolic link? But for your purposes, 1.0.6 is fine. Pre 2.0 the WiFi problems were much more pronounced, but apart from that it's the same.
You could just copy the bootloader from the official release (basically all .bin files).
I'm using ninja though instead of make, maybe that would fix your problems. Are you on Debian or Ubuntu? In that case run:
apt install ninja-build
Then remove all files from the cmake build directory and add the option "-GNinja" to the cmake command line.

yeah, i was dumb. got it to work.
the initialisation of the lan module seems quite simple, should an easy task.
am i right that i have to add another "adapter" in networkDevices/ and put the init stuff in network.cpp?
or am i missing something?

Yes, create a new device in networkDevices, then instantiate it in network.cpp.
The question is how to switch between W5500 and LAN8720. What do you think about selecting driver and GPIO in the web portal?

yeah, i would use wifi as standard, because every esp32 does have it. after first boot, you can decide in the webinterface which driver you want to use.
this gpio selection is nice, but in this scenario you should use this gpio as a "rescue", so setting the gpio to ground will force to default (wifi), in case you have misconfigured anything.

It's a bit hard to tell like this what's the issue. Could you fork my project and check in your code so I can have a look at it? Also which library are you using to communicate with the LAN8170?
I don't think it's related to cmake ... if you have problems with cmake it's usually about getting your code to compile.

Getting LAN8170 support would be amazing so I could replace my WiFi-based ESP32 by one of these Olimex boards with PoE built-in! Any additional progress so far @pilo1337?

Hi,
I've added support for the M5Stack Atom POE which uses the W5500 chip:
https://docs.m5stack.com/en/atom/atom_poe
If I find some time I'll try to add their other ESP with Ethernet:
https://shop.m5stack.com/products/esp32-ethernet-unit-with-poe
The latter is considerably cheaper, but lacks a USB port so you have to connect a USB-serial converter.

@pilo1337 Can you share the full code ?

The Olimex is finally supported !

Amazing @technyon 👏 ! Will the PoE port be automatically detected or will it still require a WiFi connection to enable the ethernet component?

You have to first connect it to wifi and then select olimex hardware. I don't really have a good way to detect that it's running on an olimex board.

A different image with this pre-defined values would be great. If you use platform.io, you'd just need to compile the image for a different environment with specific build tags. Example: https://github.com/OpenEVSE/ESP32_WiFi_V4.x/blob/master/platformio.ini

You have to first connect it to wifi and then select olimex hardware. I don't really have a good way to detect that it's running on an olimex board.

Hey. I know pretty old issue. But is the way still to "select olimex hardware" because I cant find where I would select it so it runs over lan/poe instead of wlan?!


Using iot-data api to publish message but return signature not match exception

Found some issues about iot-data api
All lib are downloaded by using nuget
version:
<packages>
  <package id="AWSSDK.Core" version="3.3.6" targetFramework="net452" />
  <package id="AWSSDK.IoT" version="<IP_ADDRESS>" targetFramework="net452" />
  <package id="AWSSDK.IotData" version="<IP_ADDRESS>" targetFramework="net452" />
  <package id="AWSSDK.S3" version="<IP_ADDRESS>" targetFramework="net452" />
</packages>

using following code to publish, but the exception
"The request signature we calculated does not match the signature you provided. Check your AWS Secret"
is always thrown
  AmazonIotDataConfig amazonIotDataConfig = new AmazonIotDataConfig();
  amazonIotDataConfig.RegionEndpoint = RegionEndpoint.APNortheast1;
  amazonIotDataConfig.UseHttp = false;
  amazonIotDataConfig.SignatureVersion = "4";
  amazonIotDataConfig.ServiceURL = amazonIotDataConfig.DetermineServiceURL();
  AmazonIotDataClient amazonIotDataClient = new AmazonIotDataClient("[ACCESS_KEY_ID]",   "[SECRET_ACCESS_KEY]", amazonIotConfig);
  try
  {
    String jsonString = "{"
               + "\"state\": {"
               + "\"reported\": {"
               + "\"door\": \"OFF\""
               + "}"
               + "}"
               + "}";

      MemoryStream memStream = new MemoryStream(Encoding.UTF8.GetBytes(jsonString ?? string.Empty));

      PublishRequest publishRequest = new PublishRequest();
      publishRequest.Qos = 0;
      publishRequest.Payload = memStream;
      publishRequest.Topic = "\\$aws/things/[THING_ID]/shadow/update";

      return amazonIotDataClient.Publish(publishRequest);
  }
  catch (System.Exception e)
  {
    throw e;
  }

Had use the same ACCESS_KEY_ID,  SECRET_ACCESS_KEY with Python boto3 iot-data api to publish message. In that context, the key pair works fine.
Had use another key pair with S3 R/W permission and .net aws s3 api to list my S3 Objects. In that context, it is normal.
Summarize the situation:

the key pairs are ok, permissions of key pair are also ok.
the AWS4Signer is ok, because using S3 Client to list S3 Objects in root Bucket is ok.
There might be some issues in AmazonIotDataClient or AmazonIotDataConfig for api user to config request for producing siginature.

Thanks.

Thank you for reporting this issue. It's a bug with how the SDK signs and invokes requests where Topic contains the "$" character. We're looking into a possible fix. At the moment it looks like you'll need to use a different SDK for these sorts of requests.

@PavelSafronov Thank you for your reply.
We need to implement a mobile application based on Xamarin, but not familiar with .net and c#.
so we need to ask for more details to evaluate the way to work-around.

Would you describe more specifically about "a different SDK for these sorts of requests"? Did you mean that we need to use other lib to access AWS iot-data web service?

When the issue possibly be fixed?

3.Our purpose is to control mcu based device that connected to AWS iot service via MQTT.
Is it possible to follow the information the article (UpdateThingShadow http://docs.aws.amazon.com/iot/latest/developerguide/API_UpdateThingShadow.html) provided to update iot thing status through iot thing shadow HTTP Restful api and aws will deliver the update status req to mcu based device via MQTT?
Thanks.

We're working on a possible fix right now, but can't say for sure when the fix would be available.

Currently, the .NET SDK is not capable of making calls against topics which have a "$" in the name.
Don't know yet.
Not certain, this would be a question for the IoT forum.

We've just released version <IP_ADDRESS> of IotData package which works with topics that contain "$". Please try that.

@PavelSafronov
Thank you and your team members.
It's works, message can be sent with topics contains "$" via AWS iotdata library <IP_ADDRESS>.

Issue solved!


Hide class docstring

Hi
Thanks for a great package!
I am trying to create sections in the docs for a class LCA . In the example below I first document the class and it's attributes from the class docstr. Subsequently methods starting with "set", "plot" and finally the remaining public methods are documented.
With my current approach the class docstr on LCA gets repeated in each section. Is there a way to avoid the class docstr being included e.g. options.self: no. Alternatively, is there a different pattern I could use - I would like to avoid adding and sorting all methods manually.
Happy holidays to you all.
Cheers, Jacob
::: src.analyses.LCA
    options:
        members: no

## `set` methods

Some general description of set methods

::: src.analyses.LCA
    options:
      show_root_heading: false
    selection:
        filters:
            - "^set"

## `plot` methods

Some general description of plot methods

::: src.analyses.LCA
    options:
      show_root_heading: false
    selection:
        filters:
            - "^plot"

## Other methods

::: src.analyses.LCA
    options:
      show_root_heading: false
    selection:
        filters:
            - "!^_"
            - "!^set"
            - "!^plot"

Hi, thanks for the kind words :slightly_smiling_face:
We could probably wrap the rendered docstring into a div with a specific class so that users can hide it through CSS.
An alternative is to auto-generate the Markdown page with mkdocs-gen-files, to add ::: src.analyses.LCA.method_name for each desired method.
By the way, you should use the paths option (see https://mkdocstrings.github.io/python/usage/#global-only-options) instead of prefixing your paths with src.

Thanks. The div solution would be nice. Meanwhile I'll try the gen-files solution and post my findings here.

If anyone comes across this post here's my working solution using gen-files. Following the gen-files docs I added a gen_pages.py (see below) which in this case generates foo.md which I reference from the nav: section in mkdocs.yml.
import inspect
import textwrap
from typing import Any, Optional, Sequence, TextIO
import mkdocs_gen_files

def gen_sectioned_docs(
    cls: type,
    filename: str,
    section_names: Sequence[str],
    section_descriptions: Optional[dict[str, str]] = None,
):
    """Generate sectioned documentation for the class in the specified `filename`.

    Args:
        cls: The target class.
        filename: Target filename of the generated docs.
        section_names: Sections names used to segrgate the member functions.
        section_descriptions: Description for each section. The keys
            are the section names and the values are the corresponding
            section descriptions. Missing and extraneous section keys
            are ignored.
    """

    # Get class name and dotted path
    cls_name = cls.__name__
    dotted_path = cls.__module__

    # Get list of (name, value) for cls
    methods = inspect.getmembers(cls, predicate=inspect.isfunction)
    methods += inspect.getmembers(cls, predicate=inspect.ismethod)

    # For bookeeping
    seen_methods = set()

    # Handle section_descriptions not specified
    if section_descriptions is None:
        _section_descriptions = {}
    else:
        _section_descriptions = section_descriptions

    def filter_methods(
        methods: Sequence[tuple[str, Any]], section_name=None
    ) -> list[tuple[str, Any]]:
        """Returns a filtered version of the specified methods list"""
        methods_in_section = []
        for name, fun in methods:

            # Skip methods that don't match the section name
            if (section_name is not None) and (not name.startswith(section_name)):
                continue

            # Skip private methods
            if name.startswith("_"):
                continue

            # Skip methods with no docstr
            if inspect.getdoc(fun) is None:
                continue

            methods_in_section.append((name, fun))

        return methods_in_section

    def add_methods_to_docs(methods: Sequence[tuple[str, Any]], file: TextIO):
        """Add lines to documentation file"""
        for method_name, _ in methods:
            file.write(f"::: {dotted_path}.{cls_name}.{method_name}\n")

    with mkdocs_gen_files.open(filename, "w") as f:

        # Add class docs
        f.write(
            textwrap.dedent(
                f"""
                ::: {dotted_path}.{cls_name}
                    options:
                        members: no
                """
            )
        )

        for section_name in section_names:

            # Add header
            f.write(f"## `{section_name}` methods\n")

            # Add section introduction
            if section_name in _section_descriptions:
                f.write(f"{_section_descriptions[section_name]}\n")

            # Filter methods to match section
            methods_in_section = filter_methods(methods, section_name)

            # Add filtered method
            add_methods_to_docs(methods_in_section, f)

            # Save methods that were added
            seen_methods.update(methods_in_section)

        # Make section for remaining methods
        f.write(f"## Other methods\n")
        unseen_methods = list(set(methods) - seen_methods)
        methods_in_section = filter_methods(unseen_methods)
        add_methods_to_docs(methods_in_section, f)

from src.analyses import LCA

SECTION_NAMES = "from", "set", "plot", "add", "save"

SECTION_DESCRIPTIONS = {
    "from": "`from_` methods can create an `LCA` object from a data source.",
    "set": "`set_` methods can _description goes here_.",
    "plot": "`plot_` methods can _description goes here_.",
    "add": "`add_` methods can _description goes here_.",
    "save": "`save_` methods can save the object in various representations.",
}

gen_sectioned_docs(LCA, "foo.md", SECTION_NAMES, SECTION_DESCRIPTIONS)


(Second attempt)Fix Route Locator for both ZuulServlet and DispatcherServlet scenarios

Conversation history here: https://github.com/spring-cloud/spring-cloud-netflix/pull/784

Created a cleaner pull request without merges, etc

I still get a test failure in ProxyRequestHelperTests. It only fails for the whole suite on the command line so I don't think it's related to your change, but we need to fix it.
BTW, can you use UNIX line endings and tabs for whitespace please?

Merged with squash and some whitespace changes.


Update from master

These translations have been added on master, but not develop.

@thijskh please review :)

:+1:


Publish foundation's test artifact

Otherwise downstream dependencies that make use of quasar tests cannot
access QuasarSpecification.

Current coverage is 74.75% (diff: 100%)

Merging #1297 into master will not change coverage

@@             master      #1297   diff @@
==========================================
  Files           192        192
  Lines         11208      11208
  Methods       10955      10955
  Messages          0          0
  Branches        123        123
==========================================
  Hits           8379       8379
  Misses         2829       2829
  Partials          0          0

Powered by Codecov. Last update 07037a3...e914882

LGTM! Bonus points for avoiding the doc/src artifacts. If only the tests would cooperate.

(I restarted the job which failed but as things currently stand I really think 3/4 passing jobs ought to be a pass.)

I strongly disagree and if I have to drop everything to fix those random test failures I'm willing to do it.

You are more than welcome to join me in my current CI investigations. I don't think it'll be a matter of fixing a thing but a longer process of hardening/improving a number of things.

@paulp Yeah, I think you're right about the CI issues. Though even if this PR passes, I'd like to wait and see if #1286 gets a clean build, I've been trying to merge that one since yesterday and gave up last night.

This is where we're at. We've been merging 3/4 PRs (and even 2/4 PRs) for a while now :/

Yes, I'm aware of how bad it's gotten. With the larger team, it's much more difficult now to wait for clean builds. That doesn't make it right.

It would be useful to know exactly what is being accomplished with the four different test runs. I understand they are using different versions of mongo, but how many different code paths are genuinely exercised? The first run also does code coverage and generates the secondary artifacts; in my branch-in-progress I broke those tasks up across multiple jobs to get a little job parallelism out.

This passed 3/4 builds and doesn't actually change any non-build code, so I'm going to merge unless anyone objects.


How to change home directory location ?

The home directory is hardwired to /home/username in /etc/aadpasswd by the extension. Is there anyway that we can change the location if the users home directory is coming from an external NFS mountpoint? (for example mounted to /shared/home/username). This does appear to be an option on the aaduseradd command, but is there an option we can set to change the aaduseradd command that runs when the user logs in to specify the correct homedir location?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: bb8e2623-1f79-aee3-bd97-8b5f647b6980
Version Independent ID: 6346b54d-cc8d-0b79-a6b8-f9144cfa2459
Content: Log in to a Linux VM with Azure Active Directory credentials
Content Source: articles/virtual-machines/linux/login-using-aad.md
Service: virtual-machines-linux
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

Thanks for the feedback! We are currently investigating and will update you shortly.

@yyanev Can you please share your insights on this? Thanks :)

@SanDeo-MSFT @yyanev Can either of you help answer this question. Thanks :)

The user provisioning is done by a tool named aaduseradd, which is modelled after the stock useradd Linux tool. It uses the same config file to set up the default home directory.
If this is rather about changing the home directory of already provisioned user, you can try again aaduseradd tool, but it is not thoroughly tested for doing updates and may not work. An alternative will be to update the record in /etc/aadpasswd file.
From: Karishma Tiwari - MSFT<EMAIL_ADDRESS>Sent: Wednesday, November 27, 2019 8:40 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Yancho Yanev<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] How to change home directory location ? (#43401)
@SanDeo-MSFThttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSanDeo-MSFT&data=02|01|yyanev%40microsoft.com|32348839b71c4ef82dcf08d773bcffa3|72f988bf86f141af91ab2d7cd011db47|1|0|637105127891071761&sdata=iD9vsiMDo3Lc1iSegEiJ4993K6ELaBZ2NxYlcdQrAtY%3D&reserved=0 @yyanevhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fyyanev&data=02|01|yyanev%40microsoft.com|32348839b71c4ef82dcf08d773bcffa3|72f988bf86f141af91ab2d7cd011db47|1|0|637105127891071761&sdata=bOn02EZJ5mWkR8LgJDWa2Vvpox8HvSbH982zqItQx%2Bo%3D&reserved=0 Can either of you help answer this question. Thanks :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F43401%3Femail_source%3Dnotifications%26email_token%3DAHTUXPHPDU2ZGPOO7K3NRLLQV5DRHA5CNFSM4JQVU7PKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFLNJRA%23issuecomment-559338692&data=02|01|yyanev%40microsoft.com|32348839b71c4ef82dcf08d773bcffa3|72f988bf86f141af91ab2d7cd011db47|1|0|637105127891081756&sdata=W84EmEG9C6oLB0EH77iLw9G%2B2px%2BlZb7eZe4lJ%2FyTlE%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHTUXPEBIJMOZ6C2673SXMLQV5DRHANCNFSM4JQVU7PA&data=02|01|yyanev%40microsoft.com|32348839b71c4ef82dcf08d773bcffa3|72f988bf86f141af91ab2d7cd011db47|1|0|637105127891081756&sdata=EEhXP895eDBpyCu7VCZK7D0t8JzlZO%2F77VUrNPlIF1g%3D&reserved=0.

@yyanev Thank you :)
@mkiernan We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


No nohup, move log file out of git and append.

Hopefully this will fix the automatic website updates.

Cool. Updated manually this time, but then redeployed the webhook payload and I think it worked. So fingers crossed, should work automatically again in the future 👍


Support basic auth authentication

If the schema registry is behind basic auth, there is no way to authenticate currently. This was brought up by Mensah in the KafkaJS slack.
I suggest adding a new auth property to the constructor, which gets forwarded to mappersmith:
new SchemaRegistry({ host: 'http://registry:2181/', auth: { username: 'bob', password: '******' } })

#21 addresses this exact issue, but moving forward we should probably expose the forge configuration in the constructor, why not enable users to leverage the full capabilities of mappersmith :)

There's pros and cons to doing that. It would be exposing an internal implementation detail, and lock you to using Mappersmith forever. Then again, it would be very powerful for users to be able to add whatever middleware they want.

There's pros and cons to doing that. It would be exposing an internal implementation detail, and lock you to using Mappersmith forever. Then again, it would be very powerful for users to be able to add whatever middleware they want.

I agree it's an internal implementation detail. However, there's already somewhat mappersmith-specific fields in the interface (e.g. clientId and retry).
At this point a change of http client seems unlikely. I'd argue that the profit from exposing mappersmith capabilities outweighs the cons, which in this case would be e.g. a major version bump since a switch in http client wouldn't necessarily be backwards compatible. I much rather have this than people doing registry.api._manifest.middleware.unshift(BasicAuth); and expecting that to be future proof 😅

maybe a "middleware" configuration option since that seems something that could easily be adapted to a different http client if that were to change.


Support for IJ 2020.3

Checklist

[ ] I have filed an issue about this change and discussed potential changes with the maintainers.
[ ] I have received the approval from the maintainers to make this change.
[ ] This is not a stylistic, refactoring, or cleanup change.

Discussion thread for this change
Issue number: #2102
Description of this change
This change drops support for 2020.1, and in its place adds support for 2020.3.
Dropping support for 2020.1 was done in order to simplify the number of places that needed to be updated or changed, but it should be trivial to back that out of this PR if necessary.

Thanks for working on the compatibility with 2020.3. I didn't have time for a full review yet but I noticed that you dropped the 2020.1 support. Unfortunately, we still need the compatibility with 2020.1 (and even 2019.3 for CLion). Can you please add it back?

I am looking forward to this being merged and released. @shs96c is there anything I can do to help?

@shs96c are you still working on this?

@shs96c are you still working on this?

Not over the holidays :)

On 2 Jan 2021, at 05:31, Chaitanya Munukutla<EMAIL_ADDRESS>wrote:

@shs96c are you still working on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Not over the holidays :)

On 2 Jan 2021, at 05:31, Chaitanya Munukutla<EMAIL_ADDRESS>wrote:

@shs96c are you still working on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hey @shs96c
thanks for the PR. Can it be already used even if it is not merged?

Hey @shs96c
thanks for the PR. Can it be already used even if it is not merged?

This needs rebasing, but it could be used when I submitted it. When I get a chance, I'll do so and respond to the review comment about leaving in support for IJ 2020.1

This needs rebasing, but it could be used when I submitted it. When I get a chance, I'll do so and respond to the review comment about leaving in support for IJ 2020.1

Thank you @shs96c . Looking forward to this!

I've tried to build your changes and I get:
$ bazel build //clwb:clwb_bazel_zip --define=ij_product=clion-latest
INFO: Repository jarjar instantiated at:
  /home/user/Documents/code/bazel-intellij/WORKSPACE:236:26: in <toplevel>
  /home/user/.cache/bazel/_bazel_user/56942b33bc8dbd16ebb2ad1b7be140d7/external/bazel_tools/tools/build_defs/repo/jvm.bzl:285:24: in jvm_maven_import_external
Repository rule jvm_import_external defined at:
  /home/user/.cache/bazel/_bazel_user/56942b33bc8dbd16ebb2ad1b7be140d7/external/bazel_tools/tools/build_defs/repo/jvm.bzl:217:38: in <toplevel>
ERROR: /home/user/Documents/code/bazel-intellij/third_party/javascript/BUILD:46:13: no such package '@intellij_ue_2019_3//': The repository '@intellij_ue_2019_3' could not be resolved and referenced by '//third_party/javascript:angular_internal'
ERROR: Analysis of target '//clwb:clwb_bazel_zip' failed; build aborted: Analysis failed
INFO: Elapsed time: 0.275s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded, 7 targets configured)
    Fetching @clion_2019_3; fetching
    Fetching @bazel; fetching
    Fetching @remotejdk11_linux; fetching

Thanks again for creating this, we have by now added support for 2020.3 in a beta release. Which you can now also install in IntelliJ https://github.com/bazelbuild/intellij/issues/2102
Please do not feel like this PR was in vain! When implementing the changes, I had looked at your suggestions and found them very helpful. Unfortunately, due to the nature of the code partly living on our internal repository, we cannot merge PRs easily at the moment. We have plans to improve this in the future.

I'm not able to update my IntelliJ to 2020.3 yet on OSX. Is the plugin update released? Or do I need to do something to get the beta plugin?


Add splunk and ohss urls

This adds the Splunk and OHSS URLs from my bash "cluster-context" script.
To get InfraID(), ocm-sdk-go needs to be at least 0.1.278, which required ocm-cli to be updated beyond their tagged releases.

/lgtm


ktlint: 0.40.0 -> 0.41.0

Motivation for this change
https://github.com/pinterest/ktlint/releases/tag/0.41.0
ktlint has been permanently moved from https://github.com/shyiko to  https://github.com/pinterest
Things done

Bumped version
Updated github repository link due to ownership transfer

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 119877 at 6e0272b6 run on aarch64-linux 1

1 package failed to build:

ktlint

1 suggestion:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/development/tools/ktlint/default.nix:16:3:
   |
16 |   installPhase = ''
   |   ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement.


Refactor project to separate core from extensions (#320)

Generally speaking there is now a hierarchy of projects to allow the project to more easily grow, rather than the previous flat module structure.
This did introduce breaking changes to the persistence model.
Here's a set of points covered within this issue:

To separate Spatial temporal core implementation details from the more general purpose multi-dimensional index and key-value store, a new core module, 'geotime' was created.  To separate all spatial-temporal components from the core, field readers and writers are now pluggable through SPI.

Also, analytics and ingest are now both able to run through GeoWaveMain using SPI to inject commandline operations (and there's a new "cli" module that contains the core for the command line tooling).

The ingest framework now allows the optional dimensionality types to be injected through SPI, in which the geotime module injects "spatial" and "spatial-temporal".

The different ingest types within geowave-types are now broken out individually in extensions/formats (and the term "type" is replaced by the term "format" to avoid confusion between ingest formats and data adapters).

Analytics was quickly broken out between "api" and "mapreduce" but perhaps its worth revisiting to look more closely at the logical breakdown, because I didn't want to go down too deep a rabbit hole with this initial cut.

Services were broken out between the service API (jax-rs interfaces), the java client stub (and if we were to provide more languages as clients than just java, this could become a directory), and the service implementation webapp

"packaging" was placed in deploy to limit the top-level directories

the eclipse formatter and cleanup were place in dev-resources as a standalone maven module so projects do not depend on a relative path to the formatter when running the maven format goal - therefore in order to run maven commands for geowave, the dev-resources must be installed first.  We should look to publish this artifact to maven central.

deleted benchmarks and vagrant setup from the root geowave project and separated each into its own project on github/ngageoint

Should we add a new category for Analytics rather than using the ingest category (CLI)?

good catch on the CLI analytic category, the category class existed, just the provider was still using the ingest category - it should be fixed now

Probably small updates to #320 needed (vagrant, benchmark moving outside).
Should add a documents page that gives an overview of the project layout (but that can be a separate ticket)
Think there are still issues with the jacoco/coveralls stuff;  looks like all the source directories are removed in the test pom - which I don't think will work (unless there's some other trick I'm not seeing)

Coverage decreased (-25.31%) to 36.8% when pulling 224828e0cd58f1d490994792170a070afb9bb1e7 on GEOWAVE-320-final into 845ac4b7e883a10d005f223b9ee84967d06b8b93 on master.

Coverage decreased (-25.31%) to 36.8% when pulling 224828e0cd58f1d490994792170a070afb9bb1e7 on GEOWAVE-320-final into 845ac4b7e883a10d005f223b9ee84967d06b8b93 on master.

Coverage decreased (-25.3%) to 36.8% when pulling 409eb5e467e0d92b79bc182f526a3b740a597210 on GEOWAVE-320-final into 845ac4b7e883a10d005f223b9ee84967d06b8b93 on master.

Coverage increased (+1.25%) to 63.35% when pulling 37a075726c6d2a82f57bf16eee80889c3b2376d0 on GEOWAVE-320-final into 845ac4b7e883a10d005f223b9ee84967d06b8b93 on master.

Coverage increased (+1.25%) to 63.35% when pulling 37a075726c6d2a82f57bf16eee80889c3b2376d0 on GEOWAVE-320-final into 845ac4b7e883a10d005f223b9ee84967d06b8b93 on master.


Unable to open help pages

Since updating to R 4.2, I'm unable to open help pages using either radian or the default R terminal. I appended the snippet provided in the wiki  to my .Rprofile to enable the session watcher. Once I add this and I try to open a help page (even for a base function, e.g. ?abs), I get an error message stating:
"couldn't show help for path: /library/base/html/Mathfun.html"
Creating plots (e.g. plot(mtcars)) and viewing objects (View(mtcars)) work as expected.
If I remove the code snippet described above from my .Rprofile, I'm able to open help pages as normal, albeit in an external browser window. So, I suspect something in the init.R file (or rather the vsc.R file) may be causing the issue, but I'm not sure exactly what I'm looking for.
FWIW, the directory to which I install packages (since upgrading to 4.2) is C:/Users/erice/AppData/Local/R/win-library/4.2, and my R path is C:/Program Files/R/R-4.2.0/bin
Environment info:
-Windows 11
-R 4.2
-vscode 1.67.0
-vscode-r 2.4.0

Update: commenting out the print.help_files_with_topic method on line ~723 of the vsc.R file fixes the issue (as a workaround) and allows help pages to open

The help pages seem to work properly on macOS and Linux. Looks like it is a Windows-specific issue. Let me see if I could reproduce it in a Windows environment.

I tried with R 4.2  in a Windows 10 machine on azure, but I cannot reproduce it.
Do you have multiple R versions installed but has some inconsistency in the registry or PATH so that vscode-R starts the background processes with incorrect R version?


Return the same input vector if its a unit vector in VectorUtil#l2normalize

Description
While going through VectorUtil class, I observed we don't have a check for unit vector in VectorUtil#l2normalize so passing a unit vector goes thorough the whole L2 normalization(which is totally not required and it should early exit?). I confirmed this by trying out a silly example of VectorUtil.l2normalize(VectorUtil.l2normalize(nonUnitVector)) and it performed every calculation twice. We could also argue that user should not call for this for a unit vector but I believe there would be cases where user simply want to perform the L2 normalization without checking the vector or if there are some overflowing values.
TL;DR : We should early exit in VectorUtil#l2normalize, returning the same input vector if its a unit vector
This is easily avoidable if we introduce a light check to see if the L1 norm or squared sum of input vector is equal to 1.0 (or) maybe just check Math.abs(l1norm - 1.0d) <= 1e-5 (as in this PR) because that unit vector dot product(v x v) are not exactly 1.0 but like example : 0.9999999403953552 etc. With 1e-5 delta here we would be assuming a vector v having v x v >= 0.99999 is a unit vector or say already L2 normalized which seems fine as the delta is really small? and also the check is not heavy one?.
I'm not sure this there existed some sort of similar check before or something(I tried to check but didn't find any history) so looking forward to thoughts if this makes sense to be added or not. Thanks!

@shubhamvishu could you add a "CHANGES.txt" entry under optimizations?

Oh nice! @benwtrent I have added a CHANGES.txt entry under optimizations now. Thanks!

@shubhamvishu I will merge and backport today


Fatal error to report

Does this happen often? You didn't give me any info

Sorry ^^ I just saw "Please report the follow to author", then I reported...
If you wanna have more details, I think the problem came from my PC.
Actually, I had issues with WMI since I tinkered a RGB keybord (it was before trying Aurora). When I installed Aurora and launched it, I get this error. I tryed several times, it was always the same.
Then I repaired my WMI tonight ; and now Aurora launch properly.
I hope this could help you a bit ; if you have any question about this issue I had, don't hesitate, it would be a pleasure if I could help in this great job you have done.
Regards

Well, seems like this is not something to fix in Aurora :)


Bump Prometheus to 2.3.2, Grafana to 5.2.2

Modify Dockerfile and entrypoint script to leverage Grafana's dashboard
and datasource provisioning. Also misc Kubernetes config updates.
Signed-off-by: Andrew Seigner<EMAIL_ADDRESS>

Grafana dashboards updates, to better match Grafana 5.2.2 features, will come in a subsequent PR.

@siggy Ahh, whoops -- I just read your comment about the dashboard updates. Totally fine to address those in a separate PR.


LogPipeline has a complete UI using the extensibility feature

Description
We use the Extensibility feature to implement a complete UI for LogPipeline. This UI contains a navigation node, list, detail and edit with fields.
Acceptance Criteria

[ ] All the components necessary for list view, detail view and edit view are created
[ ] Navigation is Cluster level -> Kyma
[ ] We follow the DOD

Documentation

https://github.com/kyma-project/kyma/pull/14063/files
https://dashboard.dev.kyma.cloud.sap/cluster/shoot--hasselhoff--kmain/customresourcedefinitions/details/logpipelines.telemetry.kyma-project.io

Create a ConfigMap (a small thing, creating navigation and pasting the CRD and creating empty objects for details and list) - we already have a ConfigMap so it's mostly modifying it.
Insert the components into the form - Add the schema

It's not going to be baked into the cluster.

Here is a proposed structure for the pages

List
status.condition[-a] - last condition

Detail

status:

filters
- this is a table with 1 column - multiline string - use monaco

outputs
- this is a table with 1 column - multiline string - use monaco

secretRefs
- list of secrets and deep linked

files
- this is a table with 2 column - multiline string - use monaco
- we can use name key for 1 column

parsers
- this is a table with 2 column - multiline string - use monaco
- we can use name key for 1 column

Resource Graph
- we use secretRefs

Edit/Create

- we will prefill the fields with defaults from schema

Simple
- outputs - multiline text - monaco

Advance
filters
- this is a  multiline string - use monaco

outputs
- this is a  multiline string - use monaco

secretRefs
- list of secrets and deep linked

files
- this is a table with 2 column - multiline string - use monaco
- we can use name key for 1 column

parsers
- this is a table with 2 column - multiline string - use monaco
- we can use name key for 1 column


Add ALLOW_OPACITY_MICROMAPS template flag to RayQuery object

Inline raytracing needs to be aware OMMs may be used, just like non-inline raytracing does.
Non-inline raytracing has RAYTRACING_PIPELINE_FLAG_ALLOW_OPACITY_MICROMAPS.
But raytracing pipeline state doesn't apply to inline raytracing.  So for in the inline case, add a RAYQUERY_FLAG_ALLOW_OPACITY_MICROMAPS flag to the template parameters for instantiating the RayQuery object.

@amarpMSFT - sorry for the delay here.  Does adding this new template flag to the RayQuery object mean we also need to add new diagnostics, or make any changes to DXIL?  If so, then this also needs to be detailed in the proposal.

@amarpMSFT - sorry for the delay here. Does adding this new template flag to the RayQuery object mean we also need to add new diagnostics, or make any changes to DXIL? If so, then this also needs to be detailed in the proposal.

My guess is it would.  If HLSL folks can confirm this solution is something you're ok with, the same folks might be able to quickly summarize the necessary DXIL/diag changes.  But if not, I can take a stab.

@amarpMSFT - sorry for the delay here. Does adding this new template flag to the RayQuery object mean we also need to add new diagnostics, or make any changes to DXIL? If so, then this also needs to be detailed in the proposal.

My guess is it would. If HLSL folks can confirm this solution is something you're ok with, the same folks might be able to quickly summarize the necessary DXIL/diag changes. But if not, I can take a stab.

After sorting out some questions:

Is SM 6.9 the only requirement, or is there an optional feature bit we need to introduce?  With the DXR pipeline, we could detect feature usage from the subobject flag or use of the equivalent flag in the API.  For RayQuery we don't have that luxury, so we may need an optional feature flag to indicate use in the shader.
Do we need additional runtime info (RDAT, PSV0) to indicate a usage with a RaytracingAccelerationStructure resource?  Maybe this will be nothing because we would rely on GBV only for these checks.

This will require additions in:

AllocateRayQuery DXIL op
updated diagnostic requirements
validation changes
potential new feature info flag and/or additional runtime info (RDAT, PSV0) required for runtime checks
research/comment on SPIR-V alignment
various test additions

Is SM 6.9 the only requirement, or is there an optional feature bit we need to introduce?  With the DXR pipeline, we could detect feature usage from the subobject flag or use of the equivalent flag in the API.  For RayQuery we don't have that luxury, so we may need an optional feature flag to indicate use in the shader.

OMM support isn't required in SM 6.9, so a feature bit makes sense.

Do we need additional runtime info (RDAT, PSV0) to indicate a usage with a RaytracingAccelerationStructure resource?  Maybe this will be nothing because we would rely on GBV only for these checks.

I don't think we need this.  Just the feature flag is sufficient.  The runtime would already have visibility into pipeline flags usage.


Add minimal spancat demo

Description
cf. https://github.com/explosion/spaCy/discussions/9635, https://github.com/explosion/spaCy/discussions/11517, https://github.com/explosion/spaCy/discussions/11518
This PR adds a minimal spancat_demo project that demonstrates how to convert and train a spancat pipeline. It borrows heavily from the ner_demo project (the dummy data, command organization, etc.), with minimal changes (conversion script, config, etc.)
Types of change
Enhancement
Checklist

[x]  I confirm that I have the right to submit this contribution under the project's MIT license.
[x]  I ran the tests, and all new and existing tests passed.
[x] My changes don't require a change to the documentation, or if they do, I've added all required information.

I'll take a closer look. I agree it's a bit weird, it's just two Examples though.

@adrianeboyd this doesn't answer our question but in the meantime, I increased training.patience to prevent early stopping. It seems that spancat takes more time to "ramp-up" than NER. Running with this change should reach 100% now.

For the sake of completeness, I reran this on (1) three different seeds ([0, 42, 10010]) and on a (2) GPU and CPU. For all cases it reached 100%. The only noticeable difference is that it learns faster on GPU, i.e., reaches 100% faster on a smaller number of steps. I've also updated the project.yml to make the seed configurable
On CPU, it does take a while to get to the accuracy we want. I also encountered long stretches of low recall, but on 1000-th step or so it starts going out of local optima again.
I can also change the samples if need be. Aside from that, what else should I try? @adrianeboyd

I can see examples where you get to 100% between 500-1000 steps, but I really think there must be a bug in the component or in the config if this does not converge faster, or really if this does not converge at all, which it doesn't seem to do. There are only 12 different tokens and the entities are identical between the train and dev examples. There is nothing about the entity tokens that the attributes do not capture unambiguously. I really think this may be pointing to a more serious issue?

Ah I suspect the same thing. I can probably start by checking the default config and play around it first, then proceed to figuring out what's happening in the component itself. Might take a bit long for this.

The basics of the project are all fine here, it's just that I'd rather not publish it until we understand what's going on.

I added a new training sample and with that I got 100%.


about CRD

I need to control the access of CRD use mutatewebhook. It seems that this framework will not work,does it support CRD?

Hi @PualrDwade!
What is the problem you are having?
Kubewebhook supports CRDs, you can check the types (dynamic and static)of webhooks here.
TL;DR: For CRDs is better the Static webhooks, if you use Dynamic webhooks, the type is unknown and will fallback to Unstructured
There are integration tests for CRDs also. Check this Webhook for a CRD:
https://github.com/slok/kubewebhook/blob/9df65e34ec7ac175252e6a212420147e49715aa8/test/integration/webhook/mutating_test.go#L195-L209
Hope it helps.

Closing, if you continue with doubts reopen this or open a new issue.


Simple fix for #52: file size matters

Fix for bug #52: check file size wrt chunk size.

:+1: 1d3d121


Discord: clicking images no longer opens them full size, but instead opens them in a web browser

Bug description:
Clicking posted images in Discord no longer shows the image full screen with the background darkened and a "show original" link, as it does in both the desktop app and web app. Instead it opens the image immediately in a web browser. This behavior is the same effect as clicking the "show original" link.
Steps to reproduce:

Open any channel on a Discord server where someone has posted an image
Click the image

Expected behavior
The rest of the page darkens and the image opens up at a larger size, with a X button to dismiss it and a link that says "open original".
Screenshots
Here is a screen shot of what's supposed to happen when clicking an image, taken from the Discord web app running in Chrome:

Environment:

Operating System: macOS 10.14.6

Ferdi Version: 5.6.2

Server: Ferdi, using without an account

Debug information:

{"host":{"platform":"darwin","release":"18.7.0","screens":[{"id":69734409,"bounds":{"x":0,"y":0,"width":1440,"height":900},"workArea":{"x":0,"y":23,"width":1440,"height":877},"accelerometerSupport":"unknown","monochrome":false,"colorDepth":24,"colorSpace":"{primaries_d50_referred: [[0.6818, 0.3196],  [0.2846, 0.6747],  [0.1549, 0.0554]], transfer:0.0777*x + 0.0000 if x < 0.0450 else (0.9495*x + 0.0495)**2.3955 + 0.0003, matrix:RGB, range:FULL}","depthPerComponent":8,"size":{"width":1440,"height":900},"displayFrequency":60,"workAreaSize":{"width":1440,"height":877},"scaleFactor":2,"rotation":0,"internal":true,"touchSupport":"unknown"}]},"ferdi":{"version":"5.6.2","electron":"13.3.0","installedRecipes":[{"id":"discord","version":"1.4.0"},{"id":"skype","version":"3.2.0"},{"id":"slack","version":"1.3.0"},{}],"devRecipes":[],"services":[{"id":"a2c79c9c-0fc8-4693-a0e2-4a9dd759b5a3","recipe":"skype","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"27dcb796-4475-426d-a414-5d0d89a3391b","recipe":"slack","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"b4fd6689-0f2c-425e-8c4d-5958bc66cb93","recipe":"slack","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"9daecdde-9d8f-45e0-a37f-992100171f15","recipe":"slack","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"4c73a83d-a0dc-40c3-b02f-fed839109742","recipe":"slack","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"66a5fb6e-9e0b-4572-a153-f501feaf52df","recipe":"slack","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"6dd085f1-937f-4974-9d5c-f29172231621","recipe":"discord","isAttached":true,"isActive":true,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false}],"messages":[{"type":"error","info":["error","Warning: Failed prop type: Invalid prop `actions.service` of type `Object` supplied to `_class2`, expected instance of `_class`.\n    in _class2 (created by inject-_class2-with-stores-actions)\n    in inject-_class2-with-stores-actions (created by RouterContext)\n    in RouterContext (created by Router)\n    in Router (created by _class)\n    in _class (created by inject-_class-with-stores-actions)\n    in inject-_class-with-stores-actions\n    in IntlProvider (created by _class)\n    in _class (created by inject-_class-with-stores)\n    in inject-_class-with-stores\n    in Provider"]},{"type":"error","info":["error","Warning: Failed prop type: Invalid prop `actions.settings` of type `Object` supplied to `_class2`, expected instance of `_class`.\n    in _class2 (created by inject-_class2-with-stores-actions)\n    in inject-_class2-with-stores-actions (created by _class2)\n    in div (created by _class2)\n    in div (created by _class2)\n    in _class2 (created by Jss(_class2))\n    in Jss(_class2) (created by _class2)\n    in _class2 (created by Jss(_class2))\n    in Jss(_class2) (created by _class2)\n    in ThemeProvider (created by _class2)\n    in _class2 (created by inject-_class2-with-stores-actions)\n    in inject-_class2-with-stores-actions (created by RouterContext)\n    in RouterContext (created by Router)\n    in Router (created by _class)\n    in _class (created by inject-_class-with-stores-actions)\n    in inject-_class-with-stores-actions\n    in IntlProvider (created by _class)\n    in _class (created by inject-_class-with-stores)\n    in inject-_class-with-stores\n    in Provider"]},{"type":"error","request":{"result":null,"wasExecuted":true,"method":"getInfo"},"error":{},"response":{},"server":"You are using Ferdi without a server"},{"type":"error","request":{"result":null,"wasExecuted":true,"method":"features"},"error":{},"response":{},"server":"You are using Ferdi without a server"},{"type":"error","request":{"result":null,"wasExecuted":true,"method":"all"},"error":{},"response":{},"server":"You are using Ferdi without a server"}],"workspaces":[],"windowSettings":{"width":977,"height":877,"x":0,"y":23,"displayBounds":{"x":0,"y":0,"width":1440,"height":900},"isMaximized":false,"isFullScreen":false},"settings":{"autoLaunchInBackground":false,"runInBackground":false,"reloadAfterResume":true,"enableSystemTray":false,"startMinimized":false,"confirmOnQuit":false,"minimizeToSystemTray":false,"closeToSystemTray":false,"privateNotifications":false,"clipboardNotifications":true,"notifyTaskBarOnMessage":false,"showDisabledServices":true,"showMessageBadgeWhenMuted":true,"showDragArea":false,"enableSpellchecking":true,"spellcheckerLanguage":"en-us","darkMode":true,"locale":"en-US","fallbackLocale":"en-US","beta":false,"isAppMuted":false,"enableGPUAcceleration":true,"server":"You are using Ferdi without a server","predefinedTodoServer":"https://app.franztodos.com","autohideMenuBar":false,"lockingFeatureEnabled":false,"locked":false,"lockedPassword":"******","useTouchIdToUnlock":true,"scheduledDNDEnabled":false,"scheduledDNDStart":"17:00","scheduledDNDEnd":"09:00","hibernateOnStartup":true,"hibernationStrategy":300,"wakeUpStrategy":300,"inactivityLock":0,"automaticUpdates":false,"showServiceNavigationBar":false,"universalDarkMode":false,"userAgentPref":"","adaptableDarkMode":false,"accentColor":"#7367f0","serviceRibbonWidth":68,"iconSize":20,"sentry":false,"nightly":false,"navigationBarBehaviour":"never","searchEngine":"duckDuckGo","useVerticalStyle":false,"alwaysShowWorkspaces":false,"liftSingleInstanceLock":false,"serviceLimit":5,"hibernate":false,"todoServer":"isUsingCustomTodoService","noUpdates":true,"customTodoServer":""},"features":{"isServiceProxyEnabled":true,"isWorkspaceEnabled":true,"isTodosEnabled":true,"isSettingsWSEnabled":false},"user":"82c1cf9d-ab58-4da2-b55e-aaa41d2142d8"}}

I have some additional information: I just updates another mac system to 5.6.2. After the update, clicking an image in Discord behaved correctly. Then a banner appeared at the bottom saying that my services had been updated, and I clicked the reload button. Now after that, clicking images erroneously opens them in a browser.

I'm also seeing this behavior on Manjaro Linux with Ferdi 5.6.2. via ferdi-bin (AUR), so I don't think it's a Mac-exclusive bug.

The problem is in the Discord recipe. I've confirmed that it was introduced with recipe version 1.2.0 by fe6130.
Should I recreate this issue in the recipe repo?

I just updated Ferdi and Discord as well and saw this bug so I wasn't sure what caused it. Thanks for the quick PR I hope it'll get applied soon. 👍

This will be in the upcoming nightly (v5.6.3-nightly.4) in an hour or so. Please upgrade and verify.

Considering this is an issue with the stable version I reckon it should be fixed in the stable channel as well

@m-vlad - though that is true, it doesn't mean that we will release to stable for every bug that gets fixed. Please be assured that the nightlies are also quite stable (and you can turn off auto-updates to stop the reminders of new updates).

The issue is it's been a month now and the "stable" version still has this issue. Stable versions shouldn't have these kinds of bugs. I am also unable to switch to nightly because I installed ferdi through choco and choco doesn't have the nightly version available.

@m-vlad - in a commercial product, a stable version can be quickly released. For any OSS software, its upto the prerogative of the maintainers to release the software. (Ironically, that's the reason I started contributing to Ferdi in the first place!)
That being said, we released a beta version just a week ago, and if there's no significant movement in the coming week, I would be willing to release a new version to fix such niggles.
btw - the nightlies are quite stable, and we rarely have to call out an urgent fix on them.


Add React Hook Form

hi,
any chance to include my hook lib?
many thanks
bill

Can you sort it alphabetically?

sure, thanks


[AzureMonitorDistro] fix link in readme

This PR is to fix a link in our Readme.
The Community renamed the package. https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/1840

API change check
API changes are not detected in this pull request.


Improve main donation button on mobile

On mobile, the main donation button might be misleading, especially on duo streams, as it always brings you to the main streamer page of the two:

Maybe it is better to change this button on mobile to just scroll down if the page is already on a wish page.

Von bxrbie:
As a donator I want to be able to only access the donation form of the streamer of my choice when I am on the respective donation page, so that I can donate quicker, easier and without confusion.
Acceptance criteria:

the big donate button in the header is not visible on streamer donation pages
the page jumps to wish description on page load
desktop + mobile

As discussed we decided to make it scroll down to the donation form!


Adding nexus staging plugin

Adding the nexus staging maven plugin to allow for easy deployments to Maven Central

Thanks for the contribution @ivan-kyosev-gs ! @TheJuanAndOnly99 is adding you to our internal systems. When ready, we will re-summon this PR and the verification/cla-signed check will pass.

@cla-bot[bot] check

Closing this pull request in favor of https://github.com/finos/legend-engine/pull/508


node-abi missing from electron 17.X

electron-rebuild: 3.2.7
Electron-Builder Version: 22.14.13
Node Version: v14.18.1
Electron Version: 17.1.0
Electron Type (current, beta, nightly): current
Target: windows
 • executing electron-rebuild electron=17.1.0 platform=windows arch=x64 appDir=D:\app\dist
  ⨯ Could not detect abi for version 17.1.0 and runtime electron.  Updating "node-abi" might help solve this issue if it is a new release of electron  failedTask=build stackTrace=Error: Could not detect abi for version 17.1.0 and runtime electron.  Updating "node-abi" might help solve this issue if it is a new release of electron
    at Object.getAbi (D:\app\node_modules\node-abi\index.js:39:9)
    at Rebuilder.get ABI [as ABI] (D:\app\node_modules\electron-rebuild\src\rebuild.ts:124:33)
    at PrebuildInstall.prebuiltModuleExists (D:\app\node_modules\electron-rebuild\src\module-type\prebuild-install.ts:65:149)
    at ModuleRebuilder.prebuildInstallNativeModuleExists (D:\app\node_modules\electron-rebuild\src\module-rebuilder.ts:56:33)
    at Rebuilder.rebuildModuleAt (D:\app\node_modules\electron-rebuild\src\rebuild.ts:179:31)
    at Rebuilder.rebuild (D:\app\node_modules\electron-rebuild\src\rebuild.ts:158:9)
    at exports.default (D:\app\resources\beforeBuildHook.js:11:5)
    at Packager.installAppDependencies (D:\app\node_modules\app-builder-lib\src\packager.ts:499:51)
    at WinPackager.doPack (D:\app\node_modules\app-builder-lib\src\platformPackager.ts:216:5)
    at WinPackager.pack (D:\app\node_modules\app-builder-lib\src\platformPackager.ts:136:5)
    at Packager.doBuild (D:\app\node_modules\app-builder-lib\src\packager.ts:441:9)
    at Object.executeFinally (D:\app\node_modules\builder-util\src\promise.ts:12:14)
    at Packager._build (D:\app\node_modules\app-builder-lib\src\packager.ts:376:31)
    at Packager.build (D:\app\node_modules\app-builder-lib\src\packager.ts:337:12)
    at Object.executeFinally (D:\app\node_modules\builder-util\src\promise.ts:12:14)

Same Issue.
I was install node-abi 3.5.0 but electron-rebuild could not detect.