HDFS-14963. Add HDFS Client machine caching active namenode index mechanism.

: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
1097
trunk passed

+1
compile
49
trunk passed

+1
checkstyle
27
trunk passed

+1
mvnsite
51
trunk passed

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

+1
javadoc
35
trunk passed

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

+1
findbugs
130
trunk passed

_ Patch Compile Tests _

+1
mvninstall
47
the patch passed

+1
compile
43
the patch passed

+1
javac
43
the patch passed

+1
checkstyle
19
hadoop-hdfs-project/hadoop-hdfs-client: The patch generated 0 new + 29 unchanged - 1 fixed = 29 total (was 30)

+1
mvnsite
46
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
32
the patch passed

+1
findbugs
134
the patch passed

_ Other Tests _

+1
unit
123
hadoop-hdfs-client in the patch passed.

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

3664

Subsystem
Report/Notes

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

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

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

uname
Linux 3c397cfcb56d 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 / dd90025

Default Java
1.8.0_222

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

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

modules
C: hadoop-hdfs-project/hadoop-hdfs-client U: hadoop-hdfs-project/hadoop-hdfs-client

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1700/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.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
43
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
1077
trunk passed

+1
compile
50
trunk passed

+1
checkstyle
28
trunk passed

+1
mvnsite
52
trunk passed

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

+1
javadoc
32
trunk passed

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

+1
findbugs
139
trunk passed

_ Patch Compile Tests _

+1
mvninstall
47
the patch passed

+1
compile
42
the patch passed

+1
javac
42
the patch passed

+1
checkstyle
19
hadoop-hdfs-project/hadoop-hdfs-client: The patch generated 0 new + 29 unchanged - 1 fixed = 29 total (was 30)

+1
mvnsite
45
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

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

+1
javadoc
32
the patch passed

+1
findbugs
134
the patch passed

_ Other Tests _

+1
unit
123
hadoop-hdfs-client in the patch passed.

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

3675

Subsystem
Report/Notes

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

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

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

uname
Linux 778a1388510a 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 / dd90025

Default Java
1.8.0_222

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

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

modules
C: hadoop-hdfs-project/hadoop-hdfs-client U: hadoop-hdfs-project/hadoop-hdfs-client

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1700/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
36
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
1133
trunk passed

+1
compile
48
trunk passed

+1
checkstyle
24
trunk passed

+1
mvnsite
52
trunk passed

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

+1
javadoc
34
trunk passed

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

+1
findbugs
132
trunk passed

_ Patch Compile Tests _

+1
mvninstall
46
the patch passed

+1
compile
42
the patch passed

+1
javac
42
the patch passed

+1
checkstyle
19
hadoop-hdfs-project/hadoop-hdfs-client: The patch generated 0 new + 29 unchanged - 1 fixed = 29 total (was 30)

+1
mvnsite
45
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

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

+1
javadoc
31
the patch passed

+1
findbugs
136
the patch passed

_ Other Tests _

+1
unit
127
hadoop-hdfs-client in the patch passed.

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

3680

Subsystem
Report/Notes

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

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

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

uname
Linux db5f9f0d3355 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 / dd90025

Default Java
1.8.0_222

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

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

modules
C: hadoop-hdfs-project/hadoop-hdfs-client U: hadoop-hdfs-project/hadoop-hdfs-client

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1700/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
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 _

0
mvndep
23
Maven dependency ordering for branch

+1
mvninstall
1111
trunk passed

+1
compile
205
trunk passed

+1
checkstyle
56
trunk passed

+1
mvnsite
126
trunk passed

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

+1
javadoc
120
trunk passed

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

+1
findbugs
322
trunk passed

_ Patch Compile Tests _

0
mvndep
15
Maven dependency ordering for patch

+1
mvninstall
115
the patch passed

+1
compile
203
the patch passed

+1
javac
203
the patch passed

+1
checkstyle
52
hadoop-hdfs-project: The patch generated 0 new + 29 unchanged - 1 fixed = 29 total (was 30)

+1
mvnsite
112
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
1
The patch has no ill-formed XML file.

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

+1
javadoc
113
the patch passed

+1
findbugs
309
the patch passed

_ Other Tests _

+1
unit
127
hadoop-hdfs-client in the patch passed.

+1
unit
5230
hadoop-hdfs in the patch passed.

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

10038

Subsystem
Report/Notes

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

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

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

uname
Linux 850e01be1a6c 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 247584e

Default Java
1.8.0_222

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

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

modules
C: hadoop-hdfs-project/hadoop-hdfs-client hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1700/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.

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

0
mvndep
23
Maven dependency ordering for branch

+1
mvninstall
1101
trunk passed

+1
compile
199
trunk passed

+1
checkstyle
55
trunk passed

+1
mvnsite
126
trunk passed

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

+1
javadoc
121
trunk passed

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

+1
findbugs
301
trunk passed

_ Patch Compile Tests _

0
mvndep
14
Maven dependency ordering for patch

+1
mvninstall
110
the patch passed

+1
compile
193
the patch passed

+1
javac
193
the patch passed

+1
checkstyle
50
hadoop-hdfs-project: The patch generated 0 new + 29 unchanged - 1 fixed = 29 total (was 30)

+1
mvnsite
111
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
1
The patch has no ill-formed XML file.

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

+1
javadoc
113
the patch passed

+1
findbugs
310
the patch passed

_ Other Tests _

+1
unit
127
hadoop-hdfs-client in the patch passed.

-1
unit
5216
hadoop-hdfs in the patch failed.

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

9996

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.TestDataNodeErasureCodingMetrics

hadoop.hdfs.server.blockmanagement.TestUnderReplicatedBlocks

Subsystem
Report/Notes

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

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

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

uname
Linux 3d872a9f2744 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 / 42fc888

Default Java
1.8.0_222

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1700/5/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt

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

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

modules
C: hadoop-hdfs-project/hadoop-hdfs-client hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1700/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.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ trunk Compile Tests _

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

+1 :green_heart:
mvninstall
19m  1s
trunk passed

+1 :green_heart:
compile
3m 34s
trunk passed

+1 :green_heart:
checkstyle
0m 55s
trunk passed

+1 :green_heart:
mvnsite
1m 59s
trunk passed

+1 :green_heart:
shadedclient
15m 36s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m 56s
trunk passed

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

+1 :green_heart:
findbugs
4m 54s
trunk passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
checkstyle
0m 54s
hadoop-hdfs-project: The patch generated 0 new + 29 unchanged - 1 fixed = 29 total (was 30)

+1 :green_heart:
mvnsite
1m 57s
the patch passed

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

+1 :green_heart:
xml
0m  2s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
12m 56s
patch has no errors when building and testing our client artifacts.

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

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

_ Other Tests _

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

-1 :x:
unit
87m 21s
hadoop-hdfs in the patch failed.

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

168m 59s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.namenode.TestDecommissioningStatus

Subsystem
Report/Notes

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

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

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

uname
Linux 7cbb70fb063b 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 / 4c1a128

Default Java
1.8.0_222

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1700/6/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt

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

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

modules
C: hadoop-hdfs-project/hadoop-hdfs-client hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project

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

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

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ trunk Compile Tests _

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

+1 :green_heart:
mvninstall
18m 12s
trunk passed

+1 :green_heart:
compile
3m 17s
trunk passed

+1 :green_heart:
checkstyle
0m 57s
trunk passed

+1 :green_heart:
mvnsite
1m 57s
trunk passed

+1 :green_heart:
shadedclient
15m 41s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m 54s
trunk passed

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

+1 :green_heart:
findbugs
4m 55s
trunk passed

_ Patch Compile Tests _

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

+1 :green_heart:
mvninstall
1m 48s
the patch passed

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

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

-0 :warning:
checkstyle
0m 49s
hadoop-hdfs-project: The patch generated 1 new + 29 unchanged - 1 fixed = 30 total (was 30)

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

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

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
13m 44s
patch has no errors when building and testing our client artifacts.

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

+1 :green_heart:
findbugs
5m 15s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
2m  3s
hadoop-hdfs-client in the patch passed.

-1 :x:
unit
97m  7s
hadoop-hdfs in the patch failed.

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

177m 42s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestDecommissionWithStriped

hadoop.hdfs.server.namenode.TestAuditLogs

hadoop.hdfs.TestDFSStripedOutputStreamWithRandomECPolicy

hadoop.hdfs.server.namenode.TestReencryptionWithKMS

hadoop.tools.TestHdfsConfigFields

hadoop.hdfs.server.blockmanagement.TestUnderReplicatedBlocks

hadoop.hdfs.TestDFSStripedInputStreamWithRandomECPolicy

hadoop.hdfs.server.namenode.TestRedudantBlocks

hadoop.hdfs.server.namenode.ha.TestPipelinesFailover

Subsystem
Report/Notes

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

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

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

uname
Linux 1c64c3744187 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 / f8e36e0

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1700/7/artifact/out/diff-checkstyle-hadoop-hdfs-project.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1700/7/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt

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

asflicense
https://builds.apache.org/job/hadoop-multibranch/job/PR-1700/7/artifact/out/patch-asflicense-problems.txt

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

modules
C: hadoop-hdfs-project/hadoop-hdfs-client hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project

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

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

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ trunk Compile Tests _

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

+1 :green_heart:
mvninstall
19m 53s
trunk passed

+1 :green_heart:
compile
4m  8s
trunk passed

+1 :green_heart:
checkstyle
1m  5s
trunk passed

+1 :green_heart:
mvnsite
2m 13s
trunk passed

+1 :green_heart:
shadedclient
17m 17s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
2m  2s
trunk passed

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

+1 :green_heart:
findbugs
5m 57s
trunk passed

_ Patch Compile Tests _

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

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

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

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

-0 :warning:
checkstyle
1m  1s
hadoop-hdfs-project: The patch generated 1 new + 29 unchanged - 1 fixed = 30 total (was 30)

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

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

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
15m 16s
patch has no errors when building and testing our client artifacts.

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

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

_ Other Tests _

+1 :green_heart:
unit
2m 12s
hadoop-hdfs-client in the patch passed.

-1 :x:
unit
90m 55s
hadoop-hdfs in the patch failed.

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

180m 30s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestDFSStripedOutputStreamWithFailureWithRandomECPolicy

hadoop.hdfs.TestFileChecksumCompositeCrc

hadoop.hdfs.TestMultipleNNPortQOP

hadoop.hdfs.TestFileAppend4

hadoop.hdfs.server.balancer.TestBalancerService

hadoop.hdfs.TestDecommission

hadoop.hdfs.TestDFSStripedOutputStream

hadoop.hdfs.server.blockmanagement.TestUnderReplicatedBlocks

Subsystem
Report/Notes

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

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

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

uname
Linux 30f847429568 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 / f8e36e0

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1700/8/artifact/out/diff-checkstyle-hadoop-hdfs-project.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1700/8/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt

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

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

modules
C: hadoop-hdfs-project/hadoop-hdfs-client hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project

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

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

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ trunk Compile Tests _

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

+1 :green_heart:
mvninstall
18m 58s
trunk passed

+1 :green_heart:
compile
3m 37s
trunk passed

+1 :green_heart:
checkstyle
0m 55s
trunk passed

+1 :green_heart:
mvnsite
2m  4s
trunk passed

+1 :green_heart:
shadedclient
15m 41s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m 59s
trunk passed

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

+1 :green_heart:
findbugs
5m  4s
trunk passed

_ Patch Compile Tests _

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

+1 :green_heart:
mvninstall
1m 56s
the patch passed

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

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

+1 :green_heart:
checkstyle
0m 50s
hadoop-hdfs-project: The patch generated 0 new + 29 unchanged - 1 fixed = 29 total (was 30)

+1 :green_heart:
mvnsite
1m 54s
the patch passed

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

+1 :green_heart:
xml
0m  2s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
13m 32s
patch has no errors when building and testing our client artifacts.

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

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

_ Other Tests _

+1 :green_heart:
unit
2m  8s
hadoop-hdfs-client in the patch passed.

-1 :x:
unit
90m 13s
hadoop-hdfs in the patch failed.

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

172m 57s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.balancer.TestBalancerService

hadoop.hdfs.TestDeadNodeDetection

Subsystem
Report/Notes

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

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

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

uname
Linux 05f4cfa97834 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 / 6c20512

Default Java
1.8.0_222

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1700/9/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt

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

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

modules
C: hadoop-hdfs-project/hadoop-hdfs-client hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project

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

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

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ trunk Compile Tests _

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

+1 :green_heart:
mvninstall
20m  0s
trunk passed

+1 :green_heart:
compile
4m 22s
trunk passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
compile
3m 54s
trunk passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
checkstyle
0m 59s
trunk passed

+1 :green_heart:
mvnsite
2m 15s
trunk passed

+1 :green_heart:
shadedclient
17m 17s
branch has no errors when building and testing our client artifacts.

-1 :x:
javadoc
0m 38s
hadoop-hdfs-client in trunk failed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.

-1 :x:
javadoc
0m 33s
hadoop-hdfs in trunk failed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.

+1 :green_heart:
javadoc
1m 18s
trunk passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

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

+1 :green_heart:
findbugs
5m 28s
trunk passed

_ Patch Compile Tests _

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

+1 :green_heart:
mvninstall
1m 55s
the patch passed

+1 :green_heart:
compile
3m 57s
the patch passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

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

+1 :green_heart:
compile
3m 47s
the patch passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

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

+1 :green_heart:
checkstyle
0m 52s
hadoop-hdfs-project: The patch generated 0 new + 29 unchanged - 1 fixed = 29 total (was 30)

+1 :green_heart:
mvnsite
1m 55s
the patch passed

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

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
14m  3s
patch has no errors when building and testing our client artifacts.

-1 :x:
javadoc
0m 35s
hadoop-hdfs-client in the patch failed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.

-1 :x:
javadoc
0m 32s
hadoop-hdfs in the patch failed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.

+1 :green_heart:
javadoc
1m 10s
the patch passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
findbugs
5m 52s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
2m  3s
hadoop-hdfs-client in the patch passed.

-1 :x:
unit
100m 41s
hadoop-hdfs in the patch passed.

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

196m 52s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.namenode.TestNameNodeAcl

hadoop.hdfs.qjournal.TestNNWithQJM

hadoop.hdfs.server.namenode.TestNamenodeRetryCache

hadoop.hdfs.server.namenode.TestINodeFile

hadoop.hdfs.server.blockmanagement.TestUnderReplicatedBlocks

hadoop.hdfs.server.datanode.TestBPOfferService

hadoop.tools.TestHdfsConfigFields

hadoop.hdfs.server.sps.TestExternalStoragePolicySatisfier

hadoop.fs.contract.hdfs.TestHDFSContractMultipartUploader

hadoop.hdfs.server.mover.TestMover

hadoop.hdfs.server.namenode.TestDeleteRace

hadoop.hdfs.client.impl.TestBlockReaderLocal

hadoop.hdfs.TestReadStripedFileWithMissingBlocks

hadoop.hdfs.server.namenode.TestReencryption

hadoop.hdfs.server.blockmanagement.TestBlockTokenWithDFSStriped

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-1700/3/artifact/out/Dockerfile

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

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

uname
Linux 850d90f1323b 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / e756fe35909

Default Java
Private Build-1.8.0_252-8u252-b09-1~18.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_252-8u252-b09-1~18.04-b09

javadoc
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-1700/3/artifact/out/branch-javadoc-hadoop-hdfs-project_hadoop-hdfs-client-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.txt

javadoc
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-1700/3/artifact/out/branch-javadoc-hadoop-hdfs-project_hadoop-hdfs-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.txt

javadoc
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-1700/3/artifact/out/patch-javadoc-hadoop-hdfs-project_hadoop-hdfs-client-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.txt

javadoc
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-1700/3/artifact/out/patch-javadoc-hadoop-hdfs-project_hadoop-hdfs-jdkUbuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1.txt

unit
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-1700/3/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-1700/3/testReport/

asflicense
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-1700/3/artifact/out/patch-asflicense-problems.txt

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

modules
C: hadoop-hdfs-project/hadoop-hdfs-client hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-1700/3/console

versions
git=2.17.1 maven=3.6.0 findbugs=4.0.6

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

This message was automatically generated.


Move the work item link service to work item service.

Currently we have a separate service for work item linking. Since we don't maintain services for sub component, we should move it to the existing work item service.

OR we look at moving the Linking component out. Both options should be considered.


Losslessly optimize boss sprites

This is the result of repeatedly running the images through ImageOptim.app with “optimization level” set to “insane” until no more savings were possible.
Only lossless optimizations are applied so the images are visually identical.
Total savings: 31 kB (out of 680 kB). 5.1% per file on average.

Superseded by #174.


fix bugs on missing lunges class, modify postureResults map in PostureClassifierProcessor and PostureResult data class

The reason for this fix is to reset the list of posture's repetition results displayed on the camera screen  after either Cancel / Complete button is pressed. In addition to that, I added extra value for PostureResult data class in the case when you would like to save it to database for instance and lunges class on PoseClassificationProcessor so that lunge count can be activated

I cannot find any more changes needed before our next sprint so I open this PR now :)


Add Pre-loaded Configuration Selection

Part of requirement FR2 ↗
User Story: As a user, I want to select an existing configuration for my IR-controlled device in the app instead of creating one, so that I can save time setting up the WIOmote.
Acceptance Criteria:

[ ] The app should have a list of all configurations available in the database.
[ ] The user can download a configuration from the list.

Deprecated due to time constraints. Remote database functionality removed. Branch closed.

In GitLab by @albu-razvan on May 9, 2024, 12:26
mentioned in commit d1f5b84884c6f0664388769b799afc6d0bc04ad1


iOS: WebView is blank(empty) when opening the app from background after a few hours

[x] I have read the Getting Started section
[x] I have already searched for the same problem

Environment

Technology
Version

Flutter version
3.7.0, on macOS 13.2 22D49 darwin-arm64

Plugin version
6.0.0-22beta

Android version
-

iOS version
16.1.2

macOS version
13.2

Xcode version
14.2

Device information: Apple iPhone 13
Description
Expected behavior:
put app in background
open it again - web view should show the webpage from url
Current behavior:
put app in background
open app again after a short time (less than around 2hours) - everything is fine
put app in background
open app again after a short time (after around 8hours) - web view is blank - progress seems to be 0
Steps to reproduce

put app in background
open app again after a short time (after around 8hours) - web view is blank - progress seems to be 0

check docs for iosOnWebContentProcessDidTerminate event.
https://pub.dev/documentation/flutter_inappwebview/latest/flutter_inappwebview/InAppWebView/iosOnWebContentProcessDidTerminate.html
and also:
https://developer.apple.com/documentation/webkit/wknavigationdelegate/1455639-webviewwebcontentprocessdidtermi

use onWebContentProcessDidTerminate and reload the webview

Seems to work. Thanks to everybody!


Don't click item_background and background_area simultaneously

Toggle boolean 'clicked' on item_background on mouse press/release to prevent simultaneous clicks on background_area. This should resolve #20.
See https://github.com/fleskesvor/escoria/tree/test/greedy_background_area for a test case using the mountain from device/scenes/test/test.scn as an item_background.

Sorry about the confusing commit history.  My git-revert foo isn't strong enough that I feel confident fixing this, so if you don't mind, I think it's better if you squash merge and apply a more descriptive commit message.

An interactive rebase to fix the commit history is not as hard as you may think :) See a detailed howto in http://docs.godotengine.org/en/latest/community/contributing/pr_workflow.html#mastering-the-pr-workflow-the-rebase

Thanks. :) I tried to follow that, but I messed up badly. Please hang on while I try to sort this out.

Ok, I ended up just resetting to a previous commit and forcing the changes into a new one. It should work now, but I will clean up the test branch too, in case you want to use that for testing.

I tested this, it works perfectly.


Update JavaScript install guides

Update docs
airbrake-js has transitioned into two separate packages:

@airbrake/browser: https://github.com/airbrake/airbrake-js/blob/master/packages/browser
@airbrake/node: https://github.com/airbrake/airbrake-js/blob/master/packages/node

We need to update our JavaScript framework install guides to reflect this change:

[ ] https://airbrake.io/docs/installing-airbrake/installing-airbrake-in-an-angular-2-app/
[ ] https://airbrake.io/docs/installing-airbrake/installing-airbrake-in-an-angularjs-app/
[ ] https://airbrake.io/docs/installing-airbrake/installing-airbrake-in-a-browserify-app/
[ ] https://airbrake.io/docs/installing-airbrake/installing-airbrake-in-an-express-app/
[ ] https://airbrake.io/docs/installing-airbrake/installing-airbrake-in-a-javascript-application/
[ ] https://airbrake.io/docs/installing-airbrake/installing-airbrake-in-a-node-app/
[ ] https://airbrake.io/docs/installing-airbrake/installing-airbrake-js-in-a-rails-app/
[ ] https://airbrake.io/docs/installing-airbrake/installing-airbrake-in-a-react-app/
[ ] https://airbrake.io/docs/installing-airbrake/installing-airbrake-in-a-redux-app/
[ ] https://airbrake.io/docs/installing-airbrake/installing-airbrake-in-a-vuejs-app/

@mmcdaris I believe you have some sort of automated way that pulls examples from the actual airbrake-js GitHub. How does one do this?
Remove old docs
Some frameworks are no longer supported. We should remove these docs:

[ ] https://airbrake.io/docs/installing-airbrake/installing-airbrake-in-an-ember-app/
[ ] https://airbrake.io/docs/installing-airbrake/installing-airbrake-in-a-hapijs-app/
[x] remove bower
[x] remove requirejs

I've updated the fetching scripts and pulled the newest versions of the instructions. 👍, that took care of a few of the update tasks.

Closing as https://github.com/airbrake/airbrake-docs/pull/410 and https://github.com/airbrake/airbrake-docs/pull/411 finished the last remaining items.


docs: update contribuing docs

SUMMARY

remove unused superset-ui section
fix dead link

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

N/A
TESTING INSTRUCTIONS

CI
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@riahk can you take a look at these changes? FYI @zhaoyongjie , Moriah is moving these sections into the docs section, so in the future the majority of this will be featured in the official documentation.


[Question] Is making new instances for each thing you want to store faster for asynchronous writing?

For IndexedDB, this Stack Overflow answer says that one should create a new database for each objectStore they wish to create (as opposed to putting all the object stores on one database), because then the different objectStores can be written to simultaneously without blocking access to each other.
My question is if local forage behaves similarly? Is it the case if I don't create a new instance for objectStore-like set of data, then different writes will block each other's access and slow things down?
Sorry if the Github issues isn't the proper place to ask this question. And many thanks for this fantastic library, by the way. You're doing God's work.

GitHub is the best place for these questions, no worries! I'm excited for GitHub Discussions, but for now an issue is fine 😄
localForage supports multiple databases and multiple objectStores, so you can use multiple to avoid blocking writes. To create multiple objectStores use the storeName config value as outlined here: https://localforage.github.io/localForage/#multiple-stores
From what I recall I don't think you'll see a major performance difference if you aren't making a LOT of read/writes than if you just used one storeName, but it's relatively straightforward to use multiple instances with different stores if you want, so feel free to try it out. If you notice it's a lot more performant feel free to let us know in the issue here 🙂
Glad you're liking the library, thanks! 👍


Optional array of Storable cache

I fix the Optional array of Storable local cache by unwrapping Optional value first
This also include my previous pull request fix, Thanks

Thanks for both of these, they look great!


Uncaught SyntaxError: Failed to execute 'querySelectorAll' on 'Element': '#-' is not a valid sele...

[Enter steps to reproduce below:]

...
...

Atom Version: 1.0.19
System: Mac OS X 10.10
Thrown From: ever-notedown package, v0.2.11
Stack Trace
Uncaught SyntaxError: Failed to execute 'querySelectorAll' on 'Element': '#-' is not a valid selector.
At /Users/macbookair/.atom/packages/ever-notedown/lib/ever-notedown-preview-view.coffee:674

Error: Failed to execute 'querySelectorAll' on 'Element': '#-' is not a valid selector.
  at Error (native)
  at EVNDPreviewView.module.exports.EVNDPreviewView.scrollToRow (/Users/macbookair/.atom/packages/ever-notedown/lib/ever-notedown-preview-view.coffee:674:21)
  at EVNDPreviewView.scrollToRow (/Users/macbookair/.atom/packages/ever-notedown/lib/ever-notedown-preview-view.coffee:25:1)
  at /Users/macbookair/.atom/packages/ever-notedown/lib/ever-notedown-preview-view.coffee:221:8
  at /Users/macbookair/.atom/packages/ever-notedown/lib/ever-notedown-preview-view.coffee:236:9
  at Emitter.module.exports.Emitter.emit (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:82:11)
  at /Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:120:32
  at Emitter.module.exports.Emitter.emit (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:82:11)
  at DisplayBuffer.module.exports.DisplayBuffer.setScrollTop (/Applications/Atom.app/Contents/Resources/app.asar/src/display-buffer.js:478:22)
  at TextEditor.module.exports.TextEditor.setScrollTop (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:2871:33)
  at TextEditorPresenter.module.exports.TextEditorPresenter.setScrollTop (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor-presenter.js:1063:20)
  at TextEditorComponent.module.exports.TextEditorComponent.onMouseWheel (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor-component.js:512:24)
  at HTMLDivElement.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor-component.js:3:61)

Commands

Config
{
  "core": {},
  "ever-notedown": {}
}

Installed Packages
# User
atom-alignment, v0.12.1
docblockr, v0.7.3
docs-snippets, v0.8.0
ever-notedown, v0.2.11
japanese-wrap, v0.2.7
project-manager, v2.6.1
terminal-panel, v1.14.1
vim-mode, v0.61.0
vim-mode-visual-block, v0.2.13

# Dev
No dev packages

Version 0.2.16 should have this problem fixed so I'll close this issue for now. Please let me know if it's still present.


Programmatic way to find all required files

There are so many files in the vs/min/ folder. In some simple usage of the library, many of them are not required.
Is there a programmatic way to find and include only the necessary files in project folder, aside from using DevTools?

vs/base/worker/workerMain.js - needed for normal editor operation
vs/basic-languages/ - only loaded based on how you use the editor (what language you pick)
vs/editor/editor.main.js, vs/editor/editor.main.css, vs/editor/editor.main.nls.js -- there are loaded in a normal editor
vs/editor/editor.main.nls.* - only loaded if you configure the editor to be loaded with a different i18n language like German, Chinese, etc.
vs/language - only loaded if you use those richer languages
loader.js - normally used, but can be replaced by require.js.


Make REPL more robust

Prevent crashing when a syntax error is encountered (and don't bother printing stack trace in that case).
Do still crash if interpreter encounters internal error.

Lgtm
Sent (awkwardly) from an Android device.
On 16 Aug 2018 10:13, "Christopher Allen"<EMAIL_ADDRESS>wrote:
@cpcallen https://github.com/cpcallen requested your review on:
NeilFraser/CodeCity#224 https://github.com/NeilFraser/CodeCity/pull/224
Make REPL more robust.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/NeilFraser/CodeCity/pull/224#event-1792493358, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAPScMiHvDWxnc6YIIlMnxZ9sIc1QtdVks5uRX4dgaJpZM4V_8IC
.


Fix CI flow for eventing-contrib release branches

Proposed Changes

eventing-contrib release CI jobs are consistently failing - https://testgrid.knative.dev/knative-0.10#eventing-contrib, since it misses the required test images.
Vendor the images from eventing, and upload them before test execution, if the job is running on a release branch.
Clean up some required dependencies since they are not being used.

NOTE this PR does not fix the existing releases, but the future release cuts.
Release Note

NONE

/cc @nachocano
/cc @matzew

@chizhg mind rebasing this ?

@chizhg mind rebasing this ?

Done.

/test all

/lgtm
/approve


Mbed-Greentea: --shuffle flag does not work with Python3

Description

Passing the --shuffle flag to mbedgt as in the following:
mbed test -t GCC_ARM -m CY8CPROTO_062_4343W -n "*mbed_hal-*" --compile
mbedgt --shuffle
results in the following error:
Traceback (most recent call last):
  File "C:\Users\dcro\AppData\Local\Programs\Python\Python37\Scripts\mbedgt-script.py", line 11, in <module>
    load_entry_point('mbed-greentea==1.7.4', 'console_scripts', 'mbedgt')()
  File "c:\users\dcro\appdata\local\programs\python\python37\lib\site-packages\mbed_greentea\mbed_greentea_cli.py", line 358, in main
    cli_ret = main_cli(opts, args)
  File "c:\users\dcro\appdata\local\programs\python\python37\lib\site-packages\mbed_greentea\mbed_greentea_cli.py", line 872, in main_c
li
    random.shuffle(filtered_ctest_test_list_keys, lambda: shuffle_random_seed)
  File "c:\users\dcro\appdata\local\programs\python\python37\lib\random.py", line 284, in shuffle
    x[i], x[j] = x[j], x[i]
TypeError: 'dict_keys' object is not subscriptable

The issue is the .keys() call here:
https://github.com/ARMmbed/mbed-os-tools/blob/master/packages/mbed-greentea/mbed_greentea/mbed_greentea_cli.py#L869
In python2 .keys() returns a list of the dictionary keys.
In python3 .keys() returns a view object (dict_keys) that is not subscriptable.
Explicitly converting filtered_ctest_test_list_keys to a list should be all that is required to fix the issue for both py2 and py3.
Issue request type

[ ] Question
[ ] Enhancement
[x ] Bug

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers.
Internal Jira reference: https://jira.arm.com/browse/IOTBTOOL-763

Quick fix would be filtered_ctest_test_list_keys = list(filtered_ctest_test_list.keys()). In python 3 dict.keys returns a keysview and not a list.

Just tested that as a fix and it works well. I can put in a PR if that fix seems sufficient to resolve this.


warn on deprecated fields

add an eslint rule to warn on deprecated field.
I need to fix the deprecated warnings before merging though.
PTAL @coda/packs
/Users/huayang/code/packs-sdk/api.ts
  335:29  warning  'makeSimpleAutocompleteMetadataFormula' is deprecated. If you have a hardcoded array of autocomplete options, simply include that array
as the value of the `autocomplete` property in your parameter definition. There is no longer
any needed to wrap a value with this formula  deprecation/deprecation

/Users/huayang/code/packs-sdk/api_types.ts
  311:22  warning  'Network' is deprecated. use `isAction` and `connectionRequirement` on the formula definition instead  deprecation/deprecation
  377:25  warning  'NetworkConnection' is deprecated. use `ConnectionRequirement` instead                                 deprecation/deprecation

/Users/huayang/code/packs-sdk/builder.ts
   94:7   warning  'formulaNamespace' is deprecated.   deprecation/deprecation
  103:10  warning  'formulaNamespace' is deprecated.   deprecation/deprecation

/Users/huayang/code/packs-sdk/compiled_types.ts
  112:5  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation

/Users/huayang/code/packs-sdk/helpers/metadata.ts
  25:47  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
  28:29  warning  'formulaNamespace' is deprecated.                                                                                deprecation/deprecation
  56:44  warning  'PackFormulas' is deprecated. Formulas should now only be defined as an array, as namespaces are deprecated                                                                                deprecation/deprecation

/Users/huayang/code/packs-sdk/helpers/migration.ts
  15:52  warning  'id' is deprecated. Use {@link idProperty }                deprecation/deprecation
  19:57  warning  'primary' is deprecated. Use {@link displayProperty }      deprecation/deprecation
  23:60  warning  'featured' is deprecated. Use {@link featuredProperties }  deprecation/deprecation

/Users/huayang/code/packs-sdk/helpers/sample_utils.ts
  11:50  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
  12:14  warning  'PackFormulas' is deprecated. Formulas should now only be defined as an array, as namespaces are deprecated                                                                                deprecation/deprecation
  15:70  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation

/Users/huayang/code/packs-sdk/index.ts
    6:14  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations                                                                               deprecation/deprecation
    6:14  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations                                                                               deprecation/deprecation
    7:14  warning  'PackId' is deprecated. Use `number` in new code                                                                                deprecation/deprecation
    7:14  warning  'PackId' is deprecated. Use `number` in new code                                                                                deprecation/deprecation
   74:14  warning  'Network' is deprecated. use `isAction` and `connectionRequirement` on the formula definition instead                                                                                deprecation/deprecation
   74:14  warning  'Network' is deprecated. use `isAction` and `connectionRequirement` on the formula definition instead                                                                                deprecation/deprecation
   75:9   warning  'NetworkConnection' is deprecated. use `ConnectionRequirement` instead                                                                                deprecation/deprecation
   75:9   warning  'NetworkConnection' is deprecated. use `ConnectionRequirement` instead                                                                                deprecation/deprecation
   77:14  warning  'PackFormulas' is deprecated. Formulas should now only be defined as an array, as namespaces are deprecated                                                                                deprecation/deprecation
   77:14  warning  'PackFormulas' is deprecated. Formulas should now only be defined as an array, as namespaces are deprecated                                                                                deprecation/deprecation
  112:9   warning  'makeSimpleAutocompleteMetadataFormula' is deprecated. If you have a hardcoded array of autocomplete options, simply include that array
as the value of the `autocomplete` property in your parameter definition. There is no longer
any needed to wrap a value with this formula  deprecation/deprecation
  112:9   warning  'makeSimpleAutocompleteMetadataFormula' is deprecated. If you have a hardcoded array of autocomplete options, simply include that array
as the value of the `autocomplete` property in your parameter definition. There is no longer
any needed to wrap a value with this formula  deprecation/deprecation

/Users/huayang/code/packs-sdk/legacy_exports.ts
  26:9   warning  'PackCategory' is deprecated.                                               deprecation/deprecation
  26:9   warning  'PackCategory' is deprecated.                                               deprecation/deprecation
  29:14  warning  'RateLimit' is deprecated. Define these in the pack management UI instead   deprecation/deprecation
  29:14  warning  'RateLimit' is deprecated. Define these in the pack management UI instead   deprecation/deprecation
  30:14  warning  'RateLimits' is deprecated. Define these in the pack management UI instead  deprecation/deprecation
  30:14  warning  'RateLimits' is deprecated. Define these in the pack management UI instead  deprecation/deprecation

/Users/huayang/code/packs-sdk/test/auth_test.ts
    35:28  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   100:38  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   130:31  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   176:31  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   202:31  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   229:31  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   251:31  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   273:31  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   293:31  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   323:31  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   348:40  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   367:77  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   374:76  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   382:16  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   418:37  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   437:37  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   461:27  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   462:37  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   486:27  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   487:37  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   511:37  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   532:37  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   561:37  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   586:37  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   610:37  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   637:37  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   660:37  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   778:37  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   802:27  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   804:37  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   831:37  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
   855:37  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
  1071:37  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
  1125:27  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
  1140:37  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
  1163:27  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
  1165:37  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation

/Users/huayang/code/packs-sdk/test/execution_test.ts
  348:29  warning  'makeSimpleAutocompleteMetadataFormula' is deprecated. If you have a hardcoded array of autocomplete options, simply include that array
as the value of the `autocomplete` property in your parameter definition. There is no longer
any needed to wrap a value with this formula  deprecation/deprecation

/Users/huayang/code/packs-sdk/test/packs/fake.ts
  28:24  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation

/Users/huayang/code/packs-sdk/test/test_utils.ts
  18:24  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
  21:13  warning  'PackCategory' is deprecated.                                                                                deprecation/deprecation
  50:46  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation
  50:69  warning  'PackDefinition' is deprecated. use `#PackVersionDefinition`

The legacy complete definition of a Pack including un-versioned metadata.
This should only be used by legacy Coda pack implementations  deprecation/deprecation

/Users/huayang/code/packs-sdk/testing/upload_validation.ts
   484:30  warning  'Network' is deprecated. use `isAction` and `connectionRequirement` on the formula definition instead  deprecation/deprecation
   487:30  warning  'NetworkConnection' is deprecated. use `ConnectionRequirement` instead                                 deprecation/deprecation
  1096:28  warning  'PackCategory' is deprecated.                                                                          deprecation/deprecation

/Users/huayang/code/packs-sdk/types.ts
  800:13  warning  'RateLimit' is deprecated. Define these in the pack management UI instead                                    deprecation/deprecation
  801:19  warning  'RateLimit' is deprecated. Define these in the pack management UI instead                                    deprecation/deprecation
  855:14  warning  'PackFormulas' is deprecated. Formulas should now only be defined as an array, as namespaces are deprecated  deprecation/deprecation
  873:7   warning  'PackId' is deprecated. Use `number` in new code                                                             deprecation/deprecation
  878:14  warning  'PackCategory' is deprecated.                                                                                deprecation/deprecation
  884:16  warning  'RateLimits' is deprecated. Define these in the pack management UI instead                                   deprecation/deprecation

✖ 85 problems (0 errors, 85 warnings)

Ah hmm. Seems like we still need to use many deprecated fields in the SDK in order to make things backwards compatible and to exercise their usage. So not sure how useful it is here, though maybe if the rule allows us to exempt certain symbols we could suppress intentional usage and catch some other cases.
This might be more useful in the packs-examples and packs repos (once we fix all of the packs)?

Or rather, it would be useful here in this repo if applied only to the documentation directory where the examples live, to make sure our examples aren't using anything deprecated?

yeah, I am not sure how useful this is as well.

good point to add that to packs/packs-example and documentation.


quartata: Watch nairasleek.info

quartata requests the watch of the watch_keyword nairasleek.info. See the Metasmoke search here

!!/approve


Update website

I've updated the website to be in dark mode, have an image on the homepage, and a go back button on the versions page.

Looks pretty awesome thanks!


Fix Company Service non unique constraint error

Company Service is throwing a SQL non-unique constraint error. Fix the error by treating non-uniqueness before sending to sqlite.
Acceptance criteria:
1 - No more non-unique constraint error in Company Service.

Company service was checking if the company exists before sending the request to EnrichService. Since the request to enrich service was queued we could have multiple requests for the same company waiting in the queue, which could lead to duplicates.
Now we are checking if the local company exists after EnrichService answers. This way even with lots of requests for the same company in the list, it will just check the company existence after the request is processed in the queue, which will prevent duplicates.


upx-unstable: init at 2022-08-23

Description of changes
Unstable version of upx from https://github.com/upx/upx/commit/8ee39aaa34f41d4db0c28be966a7cb35e392eb79
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 188364 run on x86_64-linux 1

1 package built:

upx-unstable

Closing this in favor of a future bump of upx to 4.0.2


Feedback: New code cells inserted with language ini and are not executable

Today I opened up a markdown notebook that I had been using for awhile and when I added a new code cell and tried to execute it nothing happened.
Here's a screenshot.

To be more precise, I entered the command "ls -la" and when I executed it it just echo'd the command rather than printing it.
I was stumped and tried a bunch of things (e.g. reloading the window, reinstalling the extension,...) before realizing that in the lower right corner of the code cell it was showing "INI" and the icons looked a bit different. It looks like "ini" is indicating the language of the code cell. When I changed that to "sh" it started working again.
Here's what I think happened. I created a markdown cell and inside that markdown cell I nested a code block. I often use nested code blocks inside markdown to provide preformatted output such as errors.
RunMe doesn't preserve the nesting when the file is serialized (discord thread). So when I reopened the file, the nested code block was no longer nested and was turned into a code cell. The inferred language was then "INI". This then seems to cause subsequent newly added code cells to have a default language of "INI".
Is this behavior determined by RunMe or VSCode?
I wanted to log this in GitHub in case someone else encounters similar behavior and wonders how to fix it.
One possible AI might be to create a troubleshooting section in the docs and a description of the problem and resolution to it.

RunMe doesn't preserve the nesting when the file is serialized (discord thread). So when I reopened the file, the nested code block was no longer nested and was turned into a code cell. The inferred language was then "INI". This then seems to cause subsequent newly added code cells to have a default language of "INI".
Is this behavior determined by RunMe or VSCode?

The VS Code extension is using a neutral net called guesslang as part of https://www.npmjs.com/package/@vscode/vscode-languagedetection to infer a newly inserted (likely due to unnesting you're describing) cell's languageID. While guesslang is pretty decent it performs poorly on short test, e.g. ls -la.
We've lowered the minimum threshold from the recommended 20 characters in the past. However, I'm wondering if we should ignore results like ini (already doing some tricks to bias the inference results). Ini is just so irrelevant to what Runme does.

Is the list of languages its allowed to guess easily configurable?


fancier support for customizable optimization

figure out if/how pytorch param groups interact with PyroOptim
add necessary support for pytorch lr_scheduler
make gradient clipping and the like cleaner

I think the things mentioned have basically been addressed by pyro.optim.multi and pyro.optim.lr_scheduler, we can open more specific follow-up issues as necessary


Discuss derive_var_atirel()

Tester feedback:

is "PRIOR_CONCOMITANT" actually a proper value per CDISC standard?

and

Not quite sure what this function is for.

It seems that derive_var_atirel() implements the Roche specific derivation of ATIREL.
Should we move it to admiral.roche or should we make it more general, e.g., parameterize the values of the new variable?
The name of the function and the documentation should be reviewed. Should we use "atirel" in the function name and documentation? Some information on the context where the function could be used (ADCM, ADMH) would be helpful.

@bundfussr did you ever get any feedback on this one? happy to leave it in admiral core if no objections and close this issue. even if companies have their own specific ways to do this then at least this code gives them a starting point to copy and update for their needs.

We haven't discussed this issue so far.
I would not close it without discussion.

ok thanks - let me know what gets decided. please raise my preference as above. my perspective on it is if i'm a new company adopting admiral then i rather have something in place to work from here as a guide even if my company rules vary.

@rossfarrugia , I have set it on the agenda for next Monday but the agenda is already quite long. So I am not sure if we will manage to discuss it.
By the way, should I invite you to the meeting?

sure @bundfussr - i got added to a sprint meeting (not sure if thats same thing?), but feel free to add me to anything as useful, especially to cover Robin whilst he's away.

@bundfussr no reply yet... i spent some time reflecting on this one and i went back and forth in my head of what to propose, and then i opened the actual code and saw it's just a simple mutate(...case_when(...)) & i thought we're probably spending more time considering this than any user would even take to program it themselves for whatever study-specific condition they needed! plus trying to make this function more generic to cover different scenarios like ADMH would just further over-complicate a simple IF/ELSE rule.
so in the ethos of there being no "perfect" answer here and wanting to just make a decision and move forwards... here's my proposal:

keep the function as it is in admiral core, but just add a bit extra to the documentation to clarify what this is doing (e.g. explain the conmeds possible use case) and what PRIOR_CONCOMITANT means to address the feedback above. if we remove it, then i bet someone will only ask for it later, and although it's a very specific way of deriving this with no real flexibility, for me the rule is quite sensible so some companies would be happy to follow the Roche rules here. if not nyone could take a version down to company-level or study-level using this as a starting point.
for Roche ADMH.ATIREL let's just use mutate and case_when directly as it's an even simpler version of this derivation, and i can imagine study teams having need to change the conditions anyway in some cases.

I am not sure if we should spend more time on explaining the function.
I would deprecate it as it is too specific and at Roche use mutate() and case_when() for both ADCM.ATIREL and ADMH.ATIREL. I see your point that the specific code may be useful as a starting point. But I am concerned that if we start adding specific functions as "examples" to admiral core, it becomes hard for the users to distinguish between general functions and "example" functions.
@koegerr , @thomas-neitmann , @bms63 what do you think.

Fine for me @bundfussr - let's deprecate it! if anyone ever asks for it we can point to this line in the updated programming strategy:
If something needed for ADaM could be achieved simply via an existing tidyverse function, then we do not wrap this into an admiral function, as that would add an unnecessary extra layer for users.

OK, I'll deprecate it.

Are we going to move this function to {admiralroche}?

No, it works for ADCM.ATIREL only but not for ADMH.ATIREL. Therefore we think it is easier just to use mutate() and case_when().

agree - i cut and paste the mutate() and case_when() lines from this function into our Roche planned implementation. it will do exactly the same thing, only this simple code won't be hidden away one level deeper for users to need to dig into.


Add NetworkSettings field to /containers/json response

@abronan Hello, I am adding the NetworkSettings>Networks property I introduced in Docker Remote API v1.22 and I will integrate this to Swarm afterwards by updating vended package.
More info: https://github.com/docker/docker/pull/18559
My end goal is to find out which network each container is in along with its IP address in /containers/json response (otherwise I need to query each container's info individually) so that with wagl I can provide seamless name resolution for containers in the same overlay network.
Copied EndpointSettings from here.

Thanks @ahmetalpbalkan,
SGTM when docker/docker#18559 will be merged

@abronan that's now merged.

Thanks @ahmetalpbalkan!

LGTM
ping @vieux @ehazlett

LGTM

Thanks! I'm having trouble updating the vended version at docker/swarm, I'm getting a nasty error from godep: https://github.com/tools/godep/issues/372.
I tried to do it manually but it's not trivial. The new version of dockerclient comes with github.com/docker/go-units, which needs to be vended as well, and other code using docker/docker/pkg/units should move to this (and thus remove dependency to docker/docker/pkg/units).
If one of you could try, I really appreciate.

@ahmetalpbalkan PTAL docker/swarm#1558.
We are updating Godeps as there are a lot of stuff under docker/pkg being moved into their own repository.


SVGATTROPTS make into a default/short/less confusing/easier/thing to use

move defaults to class from combined, change constructor.
do what simulationattropts does.
may need to pass library for w and h

add option to change font

add new option for fill to be enterexit
remove dglos for enterext


compose: do not allow the pwd to be another than "portus"

This is known to be problematic, since our docker compose setup expects the
portus_web container to be created. The problem that this is based on the pwd
alone. It's not possible to specify a name for this, as reported on the
following issue: https://github.com/docker/compose/issues/2092.
Thanks to @jjperezaguinaga for investigating this.
Fixes #469
Signed-off-by: Miquel Sabaté Solà<EMAIL_ADDRESS>

Good catch indeed!

@mssola Np, happy to help :)


fix error in ws_connect

Fix an error in the implementation of consumers API

Coverage increased (+0.003%) to 95.304% when pulling 117952a1d79417d24918e439d382ada713ec5b7d on hotfix/channels_connect into 24a77632deeb8880efa9fb50e670c4dccf29aeb3 on develop.


services/horizon: remove remote captive core

What problem does your feature solve?
Remote captive core is currently publicized in our docs, but we do not maintain it or test it when we do releases. It has not kept up with feature development on main line (ex. on-disk mode), and we do not dogfood it ourselves so are unaware of any potential bugs or operational issues (ex. recent issue with metrics endpoint).
What would you like to see?

Remove the configuration options / env variables for it
Remove all functionality and codepaths associated with it
Remove any reference to it or mention of it in public-facing documentation

What alternatives are there?

Start maintaining + testing it so that we can confidently document and recommend it. I don't see this option being worthwhile as I find it unlikely anyone is actually using this option, and we don't have a solid use case for it internally
Don't remove it from code, just remove it from public-facing documentation. This could still achieve the goal of dissuading people from using it, but it would still be available if they were currently using it
Remove it from code, but leave mention of it (and it's deprecation) in public-facing documentation. This could be useful for anyone that was currently using it and give them a clear path as to how to migrate away from it
Don't remove it from code or documentation, but change the existing documentation disclaimer about it being experimental to make it clear that it is not maintained at all and to use at your own risk. This is probably the quickest and safest option that achieves the end goal

I support (2), since it's still a useful piece of code (even if it needs some maintenance), because it already lives in the exp/ (as in experimental) folder which should imply that its usage is risky.


Predicted obstacle box is too far from the actual points, which impacts obstacle stop planner

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
I have observed that predicted objects are always "further in time" than their tracked/detected counterpart. Typically, the faster the object is and the farther it will appear from th raw point cloud or raw detection. For example:
https://github.com/autowarefoundation/autoware.universe/assets/18645627/a354804d-3aef-467a-b57b-eff26e3adf14
I could not find any kind of delay compensation, but I guess this is what the prediction algorithm is doing.
One annoying side effect is that obstacle stop planner is sometimes not able to associate points on the path with the tracked objects they come from (because they are too far from each other), and so autoware stops.
One way I have found to "fix" this issue is to increase the object_polygon_length_margin in the adaptive cruise control parameters (which is the case in the video). However it is not a great solution, because it increases the likeliness autoware would associate points to the wrong object.
Expected behavior
obstacle stop planner can reliabily associate points to objects of any speed
Actual behavior
when the object is fast, the predicted obstacle is too far from the pointcloud obstacle stop planner is using for comparison.
Steps to reproduce
use lidar based detection.
Versions
No response
Possible causes
No response
Additional context
No response

For whoever gets this issue in the future: obstacle cruise planner does not have such issue at all because it does not use pointcloud data. It is also way more reliable than obstacle stop planner module but that's another topic.

Hi!
I am recently working on perception latency reduction.
What actually happening is, the tracking objects are in "current time" and the point clouds are "past time".
From the sensor time to detection may takes several hundreds micro seconds.
(in case of 36 kph = 10 m/s of target related speed, 400 ms latency causes 4 m difference)

I could not find any kind of delay compensation

the delay compensation is done in object tracking - object publish time.
Config: https://github.com/autowarefoundation/autoware.universe/blob/804600599c546e5947d34666e842d6e29840909a/perception/multi_object_tracker/config/multi_object_tracker_node.param.yaml#L15
Prediction: https://github.com/autowarefoundation/autoware.universe/blob/804600599c546e5947d34666e842d6e29840909a/perception/multi_object_tracker/src/tracker/model/normal_vehicle_tracker.cpp#L377
You can disable this option, but you will get old objects.
It is impossible to reduce the latency to zero, but can be mitigated.
This is a case to be improved.
https://github.com/autowarefoundation/autoware.universe/pull/6710
The improvement will continue.

@VRichardJP
I linked this issue to my latest work for feedback.
I didn't know that the issue is closed by the PR is merged.
As I mentioned, the positions of point cloud, detected object, and tracked object cannot be the same unless there is no latency.
If it is not acceptable from your side, please reopen the Issue.


fix(package): update gcp-metadata to version 0.6.1

Closes #397

It's all good @googlebot.

The tests are failing. This will need to be looked at. I'll do so when I get a chance, but others are welcome to look too in the meanwhile.

/cc @JustinBeckwith
The failures are from tsc.
I think it's because gcp-metadata recently upgraded to tsc 2.7.0 and started to use the "Constant named properties" feature that was added to 2.7.0: http://www.typescriptlang.org/docs/handbook/release-notes/typescript-2-7.html#constant-named-properties.
See the recent change that introduced it: https://github.com/stephenplusplus/gcp-metadata/commit/0b6eb38466ab9b9588dc6101fb9a4b736abe903a#diff-f41e9d04a45c83f3b6f6e630f10117feR10

Yeah, I was kinda excited about that feature :)  Is it ok if we just upgrade this lib to TypeScript 2.7?

I think we should upgrade all our repos to TS 2.7 anyway. As a related note, I'd love gts to be upgraded to TS 2.7 and to support --esModuleInterop. For that, we need to merge https://github.com/google/ts-style/pull/125 into the master branch.

Closing since this has been replaced by PR #407.


EM-5019 fix-pipeline

EM-5019 fix-pipeline

merged with https://github.com/hmcts/em-ccd-orchestrator/pull/1073


Pop-up on startup when system performance does not meet "good" specs

Would rely on https://github.com/Kitware/vtk-js/issues/625

Some feedback but not obvious enough...

I'm thinking of adding either a blocking popup or a non-blocking notification to tell the user if they are loading too large of a file, e.g. 80MB or higher. From your experiences, what is a good threshold, e.g. at what file size does Glance seem to just "hang" when crunching on lots of bytes?

Can we set a threshold such as detecting if the file is larger than 30% of
the system's GPU memory?
On Thu, Apr 19, 2018 at 3:28 PM, Forrest Li<EMAIL_ADDRESS>wrote:

I'm thinking of adding either a blocking popup or a non-blocking
notification to tell the user if they are loading too large of a file, e.g.
80MB or higher. From your experiences, what is a good threshold, e.g. at
what file size does Glance seem to just "hang" when crunching on lots of
bytes?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Kitware/pv-web-viewer/issues/31#issuecomment-382853596,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAREr8IEJIua3xFMuMAxGEMrsK16JcNKks5tqOVVgaJpZM4SdQ5o
.

--
Stephen R. Aylward, Ph.D.
Senior Director of Strategic Initiatives, North Carolina, Kitware, Inc.
http://www.kitware.com and http://www.aylward.org
(919) 969-6990 x300

80MB or higher

Compressed? Can you tell the difference when doing the check?
With my system (integrated GPU macbook pro) I can load data that's 200Mb compressed and still do volume rendering.

Right now I don't think there is a way to get the system's GPU memory size, let alone a cross-platform method to get JS heap memory size. I can however detect upload file sizes before they are actually loaded and rendered.
I'm ball-parking 80MB because that's the largest dataset I have to test with. :) We need to refine and decide on some threshold to notify the user. Can you give the 200Mb data a shot in Glance?

I just tried. Even though I can open my NRRD files with my custom itk.js/vtk.js viewers, it crashes in Glance:
Workbox service worker successful with scope: https://kitware.github.io/pv-web-viewer/nightly/
/pv-web-viewer/nightly/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.wasm:1 GET https://kitware.github.io/pv-web-viewer/nightly/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.wasm net::ERR_BLOCKED_BY_CLIENT
itkNrrdImageIOJSBindingWasm.js:1 DOMException: Failed to execute 'send' on 'XMLHttpRequest': Failed to load 'https://kitware.github.io/pv-web-viewer/nightly/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.wasm'.
    at Object.readBinary (https://kitware.github.io/pv-web-viewer/nightly/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:3073)
    at getBinary (https://kitware.github.io/pv-web-viewer/nightly/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:18406)
    at doNativeWasm (https://kitware.github.io/pv-web-viewer/nightly/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:19500)
    at Object.Module.asm (https://kitware.github.io/pv-web-viewer/nightly/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:21334)
    at https://kitware.github.io/pv-web-viewer/nightly/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:171730
    at loadEmscriptenModule (https://kitware.github.io/pv-web-viewer/nightly/itk/WebWorkers/ImageIO.worker.js:54:527)
    at readImage (https://kitware.github.io/pv-web-viewer/nightly/itk/WebWorkers/ImageIO.worker.js:30:2172)
    at https://kitware.github.io/pv-web-viewer/nightly/itk/WebWorkers/ImageIO.worker.js:30:4159
    at i (https://kitware.github.io/pv-web-viewer/nightly/itk/WebWorkers/ImageIO.worker.js:2:2049)
    at o (https://kitware.github.io/pv-web-viewer/nightly/itk/WebWorkers/ImageIO.worker.js:2:1874)
itkNrrdImageIOJSBindingWasm.js:1 DOMException: Failed to execute 'send' on 'XMLHttpRequest': Failed to load 'https://kitware.github.io/pv-web-viewer/nightly/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.wasm'.
    at Object.readBinary (https://kitware.github.io/pv-web-viewer/nightly/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:3073)
    at getBinary (https://kitware.github.io/pv-web-viewer/nightly/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:18406)
    at doNativeWasm (https://kitware.github.io/pv-web-viewer/nightly/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:19500)
    at Object.Module.asm (https://kitware.github.io/pv-web-viewer/nightly/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:21334)
    at https://kitware.github.io/pv-web-viewer/nightly/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:171730
    at loadEmscriptenModule (https://kitware.github.io/pv-web-viewer/nightly/itk/WebWorkers/ImageIO.worker.js:54:527)
    at readImage (https://kitware.github.io/pv-web-viewer/nightly/itk/WebWorkers/ImageIO.worker.js:30:2172)
    at https://kitware.github.io/pv-web-viewer/nightly/itk/WebWorkers/ImageIO.worker.js:30:4159
    at i (https://kitware.github.io/pv-web-viewer/nightly/itk/WebWorkers/ImageIO.worker.js:2:2049)
    at o (https://kitware.github.io/pv-web-viewer/nightly/itk/WebWorkers/ImageIO.worker.js:2:1874)
abort @ itkNrrdImageIOJSBindingWasm.js:1
getBinary @ itkNrrdImageIOJSBindingWasm.js:1
doNativeWasm @ itkNrrdImageIOJSBindingWasm.js:1
Module.asm @ itkNrrdImageIOJSBindingWasm.js:1
(anonymous) @ itkNrrdImageIOJSBindingWasm.js:1
loadEmscriptenModule @ ImageIO.worker.js:54
readImage @ ImageIO.worker.js:30
(anonymous) @ ImageIO.worker.js:30
i @ ImageIO.worker.js:2
o @ ImageIO.worker.js:2
(anonymous) @ ImageIO.worker.js:2
itkNrrdImageIOJSBindingWasm.js:1 failed to compile wasm module: abort({"stack":"Error: Failed to execute 'send' on 'XMLHttpRequest': Failed to load 'https://kitware.github.io/pv-web-viewer/nightly/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.wasm'.\n    at Object.readBinary (https://kitware.github.io/pv-web-viewer/nightly/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:3073)\n    at getBinary (https://kitware.github.io/pv-web-viewer/nightly/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:18406)\n    at doNativeWasm (https://kitware.github.io/pv-web-viewer/nightly/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:19500)\n    at Object.Module.asm (https://kitware.github.io/pv-web-viewer/nightly/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:21334)\n    at https://kitware.github.io/pv-web-viewer/nightly/itk/ImageIOs/itkNrrdImageIOJSBindingWasm.js:1:171730\n    at loadEmscriptenModule (https://kitware.github.io/pv-web-viewer/nightly/itk/WebWorkers/ImageIO.worker.js:54:527)\n    at readImage (https://kitware.github.io/pv-web-viewer/nightly/itk/WebWorkers/ImageIO.worker.js:30:2172)\n    at https://kitware.github.io/pv-web-viewer/nightly/itk/WebWorkers/ImageIO.worker.js:30:4159\n    at i (https://kitware.github.io/pv-web-viewer/nightly/itk/WebWorkers/ImageIO.worker.js:2:2049)\n    at o (https://kitware.github.io/pv-web-viewer/nightly/itk/WebWorkers/ImageIO.worker.js:2:1874)"}).   I've marked it as an issue.

We have a pop-up in the new Glance v2 that details potential issues. May need to test more potential issues, but what we have works as a first iteration.


support id, path or object of groups and project

Now the user of the library does not have to worry about path encoding of group and project.
I also tried to unify query parameters and requests objects and methods.
fixes #18
fixes #33
fixes #66

Codecov Report

Merging #68 into master will increase coverage by 1.6%.
The diff coverage is 10.19%.

@@            Coverage Diff            @@
##           master      #68     +/-   ##
=========================================
+ Coverage   24.07%   25.67%   +1.6%
=========================================
  Files         115      112      -3
  Lines        1537     1472     -65
  Branches      111      126     +15
=========================================
+ Hits          370      378      +8
+ Misses       1093     1014     -79
- Partials       74       80      +6

Impacted Files
Coverage Δ

...iClient/Models/Users/Requests/UpdateUserRequest.cs
0% <ø> (ø)
:arrow_up:

...Projects/Requests/UpdateProjectMilestoneRequest.cs
0% <ø> (ø)
:arrow_up:

...lient/Models/Issues/Requests/UpdateIssueRequest.cs
0% <ø> (ø)
:arrow_up:

...odels/MergeRequests/Requests/AcceptMergeRequest.cs
0% <ø> (ø)
:arrow_up:

...lient/Models/Groups/Requests/UpdateGroupRequest.cs
0% <ø> (ø)
:arrow_up:

...els/Groups/Requests/UpdateGroupMilestoneRequest.cs
0% <ø> (ø)
:arrow_up:

...els/Projects/Requests/UpdateProjectLabelRequest.cs
0% <ø> (ø)
:arrow_up:

...odels/MergeRequests/Requests/UpdateMergeRequest.cs
0% <ø> (ø)
:arrow_up:

...c/GitLabApiClient/Internal/Queries/QueryBuilder.cs
76.66% <ø> (ø)
:arrow_up:

...tLabApiClient/Models/Releases/Responses/Release.cs
0% <ø> (ø)
:arrow_up:

... and 30 more

Continue to review full report at Codecov.

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

@nmklotas Hi Julius.
I know this is a bigger PR, do you have any concerns with the changes. I know I am breaking the API a lot lately, I might look into cleaning up Milestone and Note API to be a separate API client with a interface since they are shared between Groups and Projects. See https://github.com/jdalrymple/node-gitlab/blob/master/src/core/templates/ResourceMilestones.ts.
Could also adopt more of the template resources like members.
I tried to align the methods.

Hi @nmklotas I would appreciate a review or a merge 😅
Just ran into not being able to call
        public async Task<Project> GetProject(string projectId)
        {
            return await _client.Projects.GetAsync(projectId);
        }

Thanks for this big beutiful PR :) sorry for the delay.
I think we need to change few things.

Don't use projectBaseUrl() or other BaseUrl() methods, we should embrace the declarative nature of strings then it's very easy to mind map them to gitlab and its docs.

For parameters we should use a simple class, let's call it ProjectId, untyped object might cause problems.

it should have these properties:
ToString() overriden to create string for int, or encode if it's the path
implicit operator to create it from string
implicit operator to create it from int

so user can simply pass int or string and these operators would created class ProjectId object.
Then it's typed and easy to use and easy to maintain.
and since we are overriding ToString() it can be used in the path & it converts automatically.
what do you think?

Sounds totally reasonable! 👍

Thanks 👍

Travis CI come on gotta support dotnet core 3...

There we go 😆 New and improved code coverage 👍

Docker works fine locally, but Travis and appveyor both have blocking issues.
I think with appveyor using gitlab 11 which still uses postgres 10 we got closer :)

Okay cleaned up the branch to only handle the API cleanup.
Moving the test setup fixes into a separate PR.

@nmklotas Hope you don't mind Julius that I used my new found powers to release a new version 😄


added some pix to service html

check my submission

Let's take note of the naming convention....


Issue: New version of VSCode extension does not work on Apple Silicon (M1) (ARM64)

VSCode Extension version: v1.2.23
Update used from 7/29/2022 release
The new version of the Snyk VSCode extension does not work properly on an Apple Silicon machine.
Before, when the extension used to download the binary (which downloaded the wrong platform and had errors), you have the dirt workaround to download the Darwin binary manually and replace it under /Users/<user>/.vscode/extensions/snyk-security.snyk-vulnerability-scanner-x.x.xx/, which is not only a terrible user experience but also a nightmare to maintain.
Now that you include the nodejs source, it causes all kindsof problems.
When you try to connect using the "Connect VS Code with Snyk" button, you get the infinity "Welcome to Snyk for Visual Studio Code" after you authenticate to the https://app.snyk.io/login/cli?token=xxx.
So, the remained option (that used to work) is to include the token on settings.json manually: settings >> Snyk > Advanced: Token Storage.
This also fails.
Then when try "To set the token manually, run the VS Code command Snyk: Set Token.", the output console for the extension shows this nasty error:
[Info] Starting full scan
[Info] Starting Snyk dependencies download...
[Info] Snyk dependencies (CLI v1.981.0) have been successfully downloaded.
[Error] {"stack":["Error: Password is required.","    at checkRequired (/Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/keytar/lib/keytar.js:5:11)","    at Object.setPassword (/Applications/Visual Studio Code.app/Contents/Resources/app/node_modules.asar/keytar/lib/keytar.js:20:5)","    at u (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/electron-main/main.js:33:8527)","    at async f.setPassword (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/code/electron-main/main.js:33:8948)"],"name":"Error","message":"Password is required."}

This only happens with the Snyk extension, as other extensions properly use the VSCode secret storage without problems.
This is related to https://github.com/snyk/cli/issues/3510

Hi @junior, I appreciate you raising this. Please raise a ticket via official support channel. We'll be closing issues by the end of this week here on GitHub.


.clear

Hi, is it possible to add a .clear command to clear the chat memory ?

that will need to be a client side mod, so not here.
Try to post it as a mod idea perhaps.