[HDFS-15754] Add DataNode packet metrics

NOTICE
Please create an issue in ASF JIRA before opening a pull request,
and you need to set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. HADOOP-XXXXX. Fix a typo in YYY.)
For more details, please see https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
2m  9s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
37m 26s

trunk passed

+1 :green_heart:
compile
1m 28s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
compile
1m 19s

trunk passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
checkstyle
0m 55s

trunk passed

+1 :green_heart:
mvnsite
1m 25s

trunk passed

+1 :green_heart:
shadedclient
19m 36s

branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m  3s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javadoc
1m 26s

trunk passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+0 :ok:
spotbugs
3m 36s

Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 34s

trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 24s

the patch passed

+1 :green_heart:
compile
1m 32s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javac
1m 32s

the patch passed

+1 :green_heart:
compile
1m 19s

the patch passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
javac
1m 19s

the patch passed

-0 :warning:
checkstyle
0m 49s
/diff-checkstyle-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs-project/hadoop-hdfs: The patch generated 8 new + 124 unchanged - 0 fixed = 132 total (was 124)

+1 :green_heart:
mvnsite
1m 25s

the patch passed

+1 :green_heart:
whitespace
0m  0s

The patch has no whitespace issues.

+1 :green_heart:
shadedclient
17m 15s

patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 53s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javadoc
1m 23s

the patch passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
findbugs
3m 36s

the patch passed

_ Other Tests _

-1 :x:
unit
146m 29s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 54s

The patch does not generate ASF License warnings.

249m  1s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.namenode.ha.TestInitializeSharedEdits

hadoop.hdfs.server.namenode.ha.TestPipelinesFailover

hadoop.hdfs.server.namenode.ha.TestRetryCacheWithHA

hadoop.hdfs.TestHAAuxiliaryPort

hadoop.hdfs.TestDatanodeStartupFixesLegacyStorageIDs

hadoop.hdfs.server.namenode.ha.TestEditLogTailer

hadoop.hdfs.server.namenode.ha.TestNNHealthCheck

hadoop.hdfs.TestDecommissionWithBackoffMonitor

hadoop.hdfs.server.namenode.ha.TestEditLogsDuringFailover

hadoop.hdfs.server.balancer.TestBalancer

hadoop.hdfs.TestDecommission

hadoop.hdfs.TestDFSClientFailover

Subsystem
Report/Notes

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

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

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

uname
Linux 9ff4cf04c04e 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 513f1995adc

Default Java
Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2578/1/testReport/

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2578/1/console

versions
git=2.17.1 maven=3.6.0 findbugs=4.0.6

Powered by
Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
2m 21s

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:

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
37m  7s

trunk passed

+1 :green_heart:
compile
1m 30s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
compile
1m 20s

trunk passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
checkstyle
0m 53s

trunk passed

+1 :green_heart:
mvnsite
1m 29s

trunk passed

+1 :green_heart:
shadedclient
19m 22s

branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m  4s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javadoc
1m 29s

trunk passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+0 :ok:
spotbugs
3m 40s

Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 38s

trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 28s

the patch passed

+1 :green_heart:
compile
1m 31s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javac
1m 31s

the patch passed

+1 :green_heart:
compile
1m 16s

the patch passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
javac
1m 16s

the patch passed

-0 :warning:
checkstyle
0m 46s
/diff-checkstyle-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs-project/hadoop-hdfs: The patch generated 8 new + 124 unchanged - 0 fixed = 132 total (was 124)

+1 :green_heart:
mvnsite
1m 26s

the patch passed

+1 :green_heart:
whitespace
0m  0s

The patch has no whitespace issues.

+1 :green_heart:
shadedclient
16m 54s

patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 56s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javadoc
1m 24s

the patch passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
findbugs
3m 35s

the patch passed

_ Other Tests _

-1 :x:
unit
148m 13s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 42s

The patch does not generate ASF License warnings.

250m  1s

Reason
Tests

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

hadoop.hdfs.TestLeaseRecovery

hadoop.tracing.TestTracing

hadoop.hdfs.TestFileAppend4

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-2578/2/artifact/out/Dockerfile

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

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

uname
Linux 0f0a973ee3b8 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 513f1995adc

Default Java
Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2578/2/testReport/

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2578/2/console

versions
git=2.17.1 maven=3.6.0 findbugs=4.0.6

Powered by
Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 47s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:

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

_ trunk Compile Tests _

+0 :ok:
mvndep
13m 39s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
26m 51s

trunk passed

+1 :green_heart:
compile
24m 25s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
compile
19m 57s

trunk passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
checkstyle
2m 44s

trunk passed

+1 :green_heart:
mvnsite
3m  7s

trunk passed

+1 :green_heart:
shadedclient
21m 24s

branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
2m 10s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javadoc
3m 20s

trunk passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+0 :ok:
spotbugs
3m 17s

Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
5m 38s

trunk passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 27s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 10s

the patch passed

+1 :green_heart:
compile
20m 50s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javac
20m 50s

the patch passed

+1 :green_heart:
compile
18m 32s

the patch passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
javac
18m 32s

the patch passed

-0 :warning:
checkstyle
2m 39s
/diff-checkstyle-root.txt
root: The patch generated 4 new + 124 unchanged - 0 fixed = 128 total (was 124)

+1 :green_heart:
mvnsite
3m  4s

the patch passed

+1 :green_heart:
whitespace
0m  0s

The patch has no whitespace issues.

+1 :green_heart:
shadedclient
15m 25s

patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
2m  6s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javadoc
3m 17s

the patch passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
findbugs
5m 52s

the patch passed

_ Other Tests _

+1 :green_heart:
unit
9m 58s

hadoop-common in the patch passed.

+1 :green_heart:
unit
102m  1s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
1m  5s

The patch does not generate ASF License warnings.

311m 16s

Subsystem
Report/Notes

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

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

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

uname
Linux 63beae1e56dc 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 2825d060cf9

Default Java
Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

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

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

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

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

versions
git=2.17.1 maven=3.6.0 findbugs=4.0.6

Powered by
Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 47s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:

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

_ trunk Compile Tests _

+0 :ok:
mvndep
13m 39s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
26m 51s

trunk passed

+1 :green_heart:
compile
24m 25s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
compile
19m 57s

trunk passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
checkstyle
2m 44s

trunk passed

+1 :green_heart:
mvnsite
3m  7s

trunk passed

+1 :green_heart:
shadedclient
21m 24s

branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
2m 10s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javadoc
3m 20s

trunk passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+0 :ok:
spotbugs
3m 17s

Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
5m 38s

trunk passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 27s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 10s

the patch passed

+1 :green_heart:
compile
20m 50s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javac
20m 50s

the patch passed

+1 :green_heart:
compile
18m 32s

the patch passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
javac
18m 32s

the patch passed

-0 :warning:
checkstyle
2m 39s
/diff-checkstyle-root.txt
root: The patch generated 4 new + 124 unchanged - 0 fixed = 128 total (was 124)

+1 :green_heart:
mvnsite
3m  4s

the patch passed

+1 :green_heart:
whitespace
0m  0s

The patch has no whitespace issues.

+1 :green_heart:
shadedclient
15m 25s

patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
2m  6s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javadoc
3m 17s

the patch passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
findbugs
5m 52s

the patch passed

_ Other Tests _

+1 :green_heart:
unit
9m 58s

hadoop-common in the patch passed.

+1 :green_heart:
unit
102m  1s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
1m  5s

The patch does not generate ASF License warnings.

311m 16s

Subsystem
Report/Notes

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

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

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

uname
Linux 63beae1e56dc 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 2825d060cf9

Default Java
Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

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

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

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

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

versions
git=2.17.1 maven=3.6.0 findbugs=4.0.6

Powered by
Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m 32s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:

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

_ trunk Compile Tests _

+0 :ok:
mvndep
13m 27s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
24m 10s

trunk passed

+1 :green_heart:
compile
24m 29s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
compile
20m 52s

trunk passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
checkstyle
2m 53s

trunk passed

+1 :green_heart:
mvnsite
2m 57s

trunk passed

+1 :green_heart:
shadedclient
24m 26s

branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
2m  7s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javadoc
3m  4s

trunk passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+0 :ok:
spotbugs
3m 56s

Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
6m 23s

trunk passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 24s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 13s

the patch passed

+1 :green_heart:
compile
23m  1s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javac
23m  1s

the patch passed

+1 :green_heart:
compile
21m 21s

the patch passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
javac
21m 21s

the patch passed

-0 :warning:
checkstyle
3m 18s
/diff-checkstyle-root.txt
root: The patch generated 4 new + 124 unchanged - 0 fixed = 128 total (was 124)

+1 :green_heart:
mvnsite
2m 59s

the patch passed

+1 :green_heart:
whitespace
0m  0s

The patch has no whitespace issues.

+1 :green_heart:
shadedclient
18m 42s

patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
2m 21s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javadoc
3m 21s

the patch passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
findbugs
7m  5s

the patch passed

_ Other Tests _

+1 :green_heart:
unit
12m  9s

hadoop-common in the patch passed.

-1 :x:
unit
146m 43s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
1m  1s

The patch does not generate ASF License warnings.

370m 13s

Reason
Tests

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

Subsystem
Report/Notes

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

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

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

uname
Linux 5374d5a6f8ad 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / b612c310c26

Default Java
Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2578/4/testReport/

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2578/4/console

versions
git=2.17.1 maven=3.6.0 findbugs=4.0.6

Powered by
Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m 32s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:

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

_ trunk Compile Tests _

+0 :ok:
mvndep
13m 27s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
24m 10s

trunk passed

+1 :green_heart:
compile
24m 29s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
compile
20m 52s

trunk passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
checkstyle
2m 53s

trunk passed

+1 :green_heart:
mvnsite
2m 57s

trunk passed

+1 :green_heart:
shadedclient
24m 26s

branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
2m  7s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javadoc
3m  4s

trunk passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+0 :ok:
spotbugs
3m 56s

Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
6m 23s

trunk passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 24s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 13s

the patch passed

+1 :green_heart:
compile
23m  1s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javac
23m  1s

the patch passed

+1 :green_heart:
compile
21m 21s

the patch passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
javac
21m 21s

the patch passed

-0 :warning:
checkstyle
3m 18s
/diff-checkstyle-root.txt
root: The patch generated 4 new + 124 unchanged - 0 fixed = 128 total (was 124)

+1 :green_heart:
mvnsite
2m 59s

the patch passed

+1 :green_heart:
whitespace
0m  0s

The patch has no whitespace issues.

+1 :green_heart:
shadedclient
18m 42s

patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
2m 21s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04

+1 :green_heart:
javadoc
3m 21s

the patch passed with JDK Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

+1 :green_heart:
findbugs
7m  5s

the patch passed

_ Other Tests _

+1 :green_heart:
unit
12m  9s

hadoop-common in the patch passed.

-1 :x:
unit
146m 43s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
1m  1s

The patch does not generate ASF License warnings.

370m 13s

Reason
Tests

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

Subsystem
Report/Notes

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

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

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

uname
Linux 5374d5a6f8ad 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / b612c310c26

Default Java
Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.18.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_275-8u275-b01-0ubuntu1~18.04-b01

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2578/4/testReport/

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2578/4/console

versions
git=2.17.1 maven=3.6.0 findbugs=4.0.6

Powered by
Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

Thanks @fengnanli for the update. @goiri let me know if you have more comments on this. Otherwise I'll commit later today.

Thanks @fengnanli for the update. @goiri let me know if you have more comments on this. Otherwise I'll commit later today.

Merged to trunk. Thanks @fengnanli for the contribution and @goiri for the review.

Merged to trunk. Thanks @fengnanli for the contribution and @goiri for the review.


[Common] Remove grpcio-client crate

Motivation
First, there's currently no code that uses this.
Second, the original intention of this was that we create a trait for each GRPC client, so in tests we can do mock clients by implementing the trait. However, given that we should use a Rust wrapper for the GRPC clients, any use case should manually create a trait like StorageRead
https://github.com/libra/libra/blob/096245b0343231544ae10f1cc9b7fd15d396afff/storage/storage_client/src/lib.rs#L297
instead of using codegen.
Have you read the Contributing Guidelines on pull requests?
No.
Test Plan
It builds.
Related PRs
None.

@bors-libra r+

:pushpin: Commit c75d388 has been approved by lightmark

:hourglass: Testing commit c75d388703d7eb1f6a86cbdd5d3feda9190295d1 with merge 06ca9ce334b879296139e82a814b5c953a3730f7...

:broken_heart: Test failed - checks-circle_commit_workflow

I think there's a bit code that still uses this. Close for now.

It looks like admission control still uses it, maybe it would still be worth while to stop using it everywhere else except AC for the moment? This would probably help prep our codebase for migrating grpc implementations soonish


genesis bridge investigation

PR Standards
Opening a pull request should be able to meet the following requirements

Closes #XXX
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow-up issues.
For Author:

[ ]  Targeted PR against correct branch
[ ]  included the correct type prefix in the PR title
[ ]  Linked to Github issue with discussion and accepted design
[ ]  Targets only one github issue
[ ]  Wrote unit and integration tests
[ ]  All CI checks have passed
[ ]  Added relevant godoc comments

For Reviewer:

[ ]  confirmed the correct type prefix in the PR title
[ ]  Reviewers assigned
[ ]  confirmed all author checklist items have been addressed

After reviewer approval:

[ ]  In case targets main branch, PR should be squashed and merged.
[ ]  In case PR targets a release branch, PR should be rebased.

see https://github.com/dymensionxyz/dymension-rdk/pull/449


Release 41 into master

What does this PR do?

Motivation

More

[ ] Added/updated tests
[ ] Added/updated documentation

Additional Notes

Went to upstream instead of origin, sorry


Identifiers validation failed for dataset Actualización de la base de datos sobre la flora de la Reserva de la Biósfera Sierra de Manantlán, Jalisco-Colima, México

Identifier validation failed for the dataset Actualización de la base de datos sobre la flora de la Reserva de la Biósfera Sierra de Manantlán, Jalisco-Colima, México:

Crawler attempt: 282
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 19513
Cause: GBIF IDs hit maximum allowed - 50%, duplicates - 96%, total records count 19512, absent records count 18793
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3072985/step

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Actualización de la base de datos sobre la flora de la Reserva de la Biósfera Sierra de Manantlán, Jalisco-Colima, México : https://doi.org/10.15468/5h2rue.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Actualización de la base de datos sobre la flora de la Reserva de la Biósfera Sierra de Manantlán, Jalisco-Colima, México:

Crawler attempt: 285
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 19513
Cause: GBIF IDs hit maximum allowed - 50%, duplicates - 100%, total records count 19512, absent records count 19512
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3093876/step

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Actualización de la base de datos sobre la flora de la Reserva de la Biósfera Sierra de Manantlán, Jalisco-Colima, México : https://doi.org/10.15468/5h2rue.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.


thanos compact panic on GetActiveAndPartialBlockIDs

Thanos, Prometheus and Golang version used:
thanos, version 0.35.0 (branch: HEAD, revision: d9a0efab5709ff6eccc37804996f29990e92ffa5)
  build user:       root@475652f059b4
  build date:       20240502-10:45:11
  go version:       go1.21.9
  platform:         linux/amd64
  tags:             netgo

Object Storage Provider: S3
What happened: It panicked with
panic: send on closed channel

goroutine<PHONE_NUMBER> [running]:
github.com/thanos-io/thanos/pkg/block.(*ConcurrentLister).GetActiveAndPartialBlockIDs.func1()
	/app/pkg/block/fetcher.go:260 +0x20c
golang.org/x/sync/errgroup.(*Group).Go.func1()
	/go/pkg/mod/golang.org/x/sync@v0.6.0/errgroup/errgroup.go:78 +0x56
created by golang.org/x/sync/errgroup.(*Group).Go in goroutine<PHONE_NUMBER>
	/go/pkg/mod/golang.org/x/sync@v0.6.0/errgroup/errgroup.go:75 +0x96

What you expected to happen: No panic
Full logs to relevant components:
Logs

will update with more info

Environment:

OS (e.g. from /etc/os-release): official container
Kernel (e.g. uname -a): Linux thanos-compact-0 5.15.146+ #1 SMP Tue Apr 2 11:55:25 UTC 2024 x86_64 GNU/Linux

I think I hit exactly the same error when context was canceled.
I wonder if it helps to add a context check here before sending id to the channel

Hi,
I'm seeing the same error both in Store & Compactor. I'm able to reproduce this error on latest thanos 0.36.0 (both store & compactor) as well
-- On thanos store
ts=2024-08-09T11:58:11.063840179Z caller=stdlib.go:105 level=debug s3TraceMsg=---------END-HTTP---------
panic: send on closed channel
goroutine 126555170 [running]:
github.com/thanos-io/thanos/pkg/block.(*ConcurrentLister).GetActiveAndPartialBlockIDs.func1()
/app/pkg/block/fetcher.go:260 +0x20c
golang.org/x/sync/errgroup.(*Group).Go.func1()
/go/pkg/mod/golang.org/x/sync@v0.7.0/errgroup/errgroup.go:78 +0x56
created by golang.org/x/sync/errgroup.(*Group).Go in goroutine 126555148
/go/pkg/mod/golang.org/x/sync@v0.7.0/errgroup/errgroup.go:75 +0x96
On Thanos compactor
caller=runutil.go:117 level=error msg="function failed. Retrying in next tick" err="BaseFetcher: iter bucket: read tcp 100.xx:xxx:xxx:32932->10.xx.xxx.xxxx:80 read: connection reset by peer"
panic: send on closed channel
goroutine 178914629 [running]:
github.com/thanos-io/thanos/pkg/block.(*ConcurrentLister).GetActiveAndPartialBlockIDs.func1()
/app/pkg/block/fetcher.go:260 +0x20c
golang.org/x/sync/errgroup.(*Group).Go.func1()
/go/pkg/mod/golang.org/x/sync@v0.7.0/errgroup/errgroup.go:78 +0x56
created by golang.org/x/sync/errgroup.(*Group).Go in goroutine 178914622
/go/pkg/mod/golang.org/x/sync@v0.7.0/errgroup/errgroup.go:75 +0x96
This issue has to be fixed as its been in around for a while. store & compactor pods have restart in production due to this panic!!

Hi @hgsat123 @jzelinskie, can you please help test setting --block-discovery-strategy=recursive. Is this problem still reproducible?

Hi @hgsat123 @jzelinskie, can you please help test setting --block-discovery-strategy=recursive. Is this problem still reproducible?

Sure. Let me test. As i mentioned i've seen / reproducible issue on 0.35.0, 0.35.1 & even in the latest 0.36.0 thanos release. Issue is reproducible only in Compactor & store (statefulset) instances


Reuse stream of HTTP request instead of create new stream

Reuse stream of HTTP request instead of create new stream.
If you can test with your test environment ;).

It does not seem to work properly, both when reusing the guzzle stream and when creating an in memory stream.
1) GitlabAdapterTest::it_can_read_a_file_into_a_stream
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-''
+'# Testing repo for `flysystem-gitlab`'

GitlabAdapterTest.php:81

Maybe a stream factory could be used: https://docs.guzzlephp.org/en/guzzle4/streams.html#creating-streams

Changed:
$this->assertEquals(stream_get_contents($stream, null, 0), $this->gitlabAdapter->read('README.md'));

To:
$this->assertEquals(stream_get_contents($stream), $this->gitlabAdapter->read('README.md'));

Results:
There was 1 failure:

GitlabAdapterTest::it_can_read_a_file_into_a_stream
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'{"file_name":"README.md","file_path":"README.md","size":37,"encoding":"base64","content_sha256":"e9492f2d51b0021ed15b97ecf8780ccd119f3628786de41aaff546aa126584d1","ref":"master","blob_id":"5762108fe413276c03951c653ac041c79e39c279","commit_id":"60324fe92d19b865684c7e5c59390fa32d0b13f8","last_commit_id":"ec1ac4fbb877266574474a7913f9f47ca548cfe1","content":"IyBUZXN0aW5nIHJlcG8gZm9yIGBmbHlzeXN0ZW0tZ2l0bGFiYA=="}'
+'# Testing repo for flysystem-gitlab'

GitlabAdapterTest.php:81
FAILURES!
Tests: 1, Assertions: 2, Failures: 1.

Yes, my bad! JSON result... so not possible to reuse stream.

I read the API documentation; I hadn't seen the "../raw" route; so it's work!

Nice! I should have known this, I even implemented a readRaw method in the client. Thanks for putting in the effort, I will add this in the new version when I have the time to test it in the testing environment.


dhcpv6-pd ERL config settings failing to apply

I believe this portion of the ERL config may be failing in the latest version:
dhcpv6-pd {                  pd 0 {                     interface eth1 {                         host-address ::1                         prefix-id :0                         service slaac                     }                     interface eth2 {                         host-address ::1                         prefix-id :1                         service slaac                     }                     interface eth2.102 {                         host-address ::1                         prefix-id :2                         service slaac                     }                     prefix-length /64                 }                 rapid-commit enable             }
I tried to manually apply these settings via the Config Tree and ran into the below Alert error message:  prefix-id must be less than :: for prefix /64
I was able to apply the settings by removing the prefix id altogether, however, I won't be able to confirm a valid ipv6 address until likely tomorrow?  I'm not sure how important the prefix-id is for each of the interfaces.   (I apologize for the bad formatting, I'm not sure how to add new lines in the code block)
I did notice there was speculation in #24 that the prefix switched back to /56 but not sure if that is accurate or not.

I do have an IPv6 address with /64 and no prefix-ids set.


Can't set display style on row zero of class remi.gui.TableWidget unless use_title=True

I set column zero of each row to display:none (hides a DB key for that row's data), and I don't need or want a title row, so I set TableWidget use_title=False, and then put my data in row 0, setting column 0 to not display:
self.table.item_at(*coords).set_style("display:none")
This line of code is in a while loop, iterating through the database file -- all rows are set properly (no display of column zero) except for row 0 which displays all columns.
My workaround is to set use_title=True -- it then allows me to set display:none (or hidden), and I start my data with row 1 (2nd row).  But a thin blue line is displayed where the title row would be.
Is this expected behavior?  If so, any way to get rid of the blue line?

Hello @jwrothwell2 , I created this example for you, please give it a look and let me know if it solve your problem:
import remi.gui as gui
from remi import start, App
import os

import sqlite3 as lite

# code example from https://pythonspot.com/python-database-programming-sqlite-tutorial/
# creating a custom database
try:
    con = lite.connect('user.db')
    with con:
        cur = con.cursor()
        cur.execute("CREATE TABLE Users(Id INT, Name TEXT)")
        cur.execute("INSERT INTO Users VALUES(1,'Michelle')")
        cur.execute("INSERT INTO Users VALUES(2,'Sonya')")
        cur.execute("INSERT INTO Users VALUES(3,'Greg')")
except lite.OperationalError:
    print("database table seems to already exist")

class MyApp(App):
    def main(self):
        main_container = gui.VBox(style={'margin': '0px auto'})

        self.table = gui.Table()

        #Loading database into table
        con = lite.connect('user.db')
        with con:
            cur = con.cursor()
            cur.execute("SELECT * FROM Users")
            rows = cur.fetchall()
            for row in rows:
                #print row
                table_item_id = gui.TableItem( str(row[0]) )
                table_item_id.style['display'] = 'none'
                table_item_username = gui.TableItem(row[1])
                table_row = gui.TableRow()
                table_row.append([table_item_id, table_item_username])
                self.table.append(table_row)

        main_container.append(self.table)
        return main_container

if __name__ == "__main__":
    # starts the webserver
    start(MyApp, address='<IP_ADDRESS>', port=0, start_browser=True, username=None, password=None)

Kind Regards

This works, of course. ;-)  But even before trying it (since I assumed it would work fine), I started looking at what you did differently.  For one, you used the Table class, whereas I used the TableWidget.  But probably more important (I thought) was that you were populating the row/cell data and style before creating (appending) the table_row, whereas I was creating the row first with set_row_count, and then populating the row and changing its style. And I confirmed this -- I tried your code with both Table and then TableWidget, and got the same results. And I could set TableWidget's use_title to True or False and it didn't affect hiding the first column. So the difference that seems to matter is the sequence.
I'm curious...do you know why setting display:none prior to appending the row works and setting if afterward doesn't?  And why it only affects the first row?  Thanks.

@jwrothwell2 The TableWidget is an automated (simplified) version of Table. It internally updates the first row in some cases. It is not supposed that the user modify directly cells style.
As a side note, I suggest you to not store data in hidden cells. In my opinion, the right way to do so is to overload the TableRow class in order to add custom properties, and store custom info there. This way, when you get a row instance in case of onclick event, you gets custom properties with it.
class MySuperTableRow(gui.TableRow):
    db_index = None
    def __init__(self, _db_index, *args, **kwargs):
        gui.TableRow.__init__(self, *args, **kwargs)
        self.db_index = _db_index

@dddomodossola I really appreciate this -- I had no idea you could do this in Python.  I've only been using Python for a few months, and I've never had much exposure to object-oriented languages and inheritance - and never really understood the concept of overloading.  I didn't realize that you could add properties like this that weren't originally defined.
So, I got this coded and working -- after several hours of trying to retrieve the value I'd stored, using row._db_index.  I almost gave up until I tried row.db_index for some reason and that worked. So I guess now I need to learn the significance of using the leading underscore when assigning the value and dropping it when retrieving the value...always something more to learn...
Thanks again so much -- this is so much easier than using hidden columns and having to search for them later using another column's coordinates. And of course, much cleaner code.  You're teaching me well!  ;-)

@jwrothwell2 you are erally welcome.
The leading underscore has no special meaning in this case. I named the class attribute "db_index" (this is why you access the this attribute without undescrore, it is because it has no underscore) and the parameter of the init function "_db_index". So I assigned the parameter class.db_index = _db_index.

Ah, ok. I'm still trying to wrap my head around extended classes and how they receive arguments or attributes but I think I see what you mean now that you pointed it out. Thanks.


Repositories without slashes in path are ignored.

Parsing any URL which doesn't contain a / in the path fails.
For example, this is correct (even if the 'owner' part isn't generally meaningful):
>>><EMAIL_ADDRESS>Parsed(pathname='/path/repo.git', protocols=['ssh'], protocol='ssh'<EMAIL_ADDRESS>resource='example.com', user='user', port=None, name='repo', owner='path')

But this yields nonsensical results:
>>><EMAIL_ADDRESS><EMAIL_ADDRESS>protocols=['ssh'], protocol='ssh'<EMAIL_ADDRESS>resource='ssh', user=None, port=None, name='repo'<EMAIL_ADDRESS>
This, again, is correct:
>>> giturlparse.parse('user@example.com:path/repo.git')
Parsed(pathname='path/repo.git', protocols=[], protocol='ssh', href='user@example.com:path/repo.git', resource='example.com', user='user', port=None, name='repo', owner='path')

And this fails:
>>> giturlparse.parse('user@example.com:repo.git')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/rczajka/.local/share/virtualenvs/vdeploy/lib/python3.6/site-packages/git_url_parse-1.0.2-py3.6.egg/giturlparse/__init__.py", line 34, in parse
    return p.parse()
  File "/home/rczajka/.local/share/virtualenvs/vdeploy/lib/python3.6/site-packages/git_url_parse-1.0.2-py3.6.egg/giturlparse/parser.py", line 104, in parse
    raise ParserError(msg)
giturlparse.parser.ParserError: Invalid URL 'user@example.com:repo.git'

Actually, all URLs listed in tests as invalid are valid git URLs:
    'https://example.com/owner',
    'git+ssh://example.com/owner/repo.git'
    'git+https://example.com/owner/repo.git'
    'https://example.com/owner',
    'example.com:repo.git',
    'user@example.com:repo.git',

Even the git+https one is valid, even though it'd require a remote helper for git to understand it. Other ones are totally ok.

Actually, all URLs listed in tests as invalid are valid git URLs:

They are invalid b/c I have chosen not to parse those as valid.  PRs always welcome.

Implemented in #4.


fix: Dockerfile to reduce vulnerabilities

The following vulnerabilities are fixed with an upgrade:

https://dev.snyk.io/vuln/SNYK-DEBIAN9-LIBXML2-429367
https://dev.snyk.io/vuln/SNYK-DEBIAN9-PYTHON35-1063181
https://dev.snyk.io/vuln/SNYK-DEBIAN9-PYTHON35-340072
https://dev.snyk.io/vuln/SNYK-DEBIAN9-PYTHON35-453739
https://dev.snyk.io/vuln/SNYK-DEBIAN9-PYTHON35-584435

reduce vulnerabilities


Snowflake Connections with SSO create infinite loop of auth when trying to reconnect

System information:

Operating system: MacOS 10.14.06, Ubuntu 18.04, others
DBeaver version: 7.0.3 (and prior)
Additional extensions: None

Connection specification:

Database name and version: Snowflake
Driver name: snowflake-jdbc-3.12.0.jar
Do you use tunnels or proxies (SSH, SOCKS, etc)? No

Describe the problem you're observing:
When trying to run a query on a timed-out connection to Snowflake with an Okta SSO authentication, the client goes into an infinite auth loop and never resolves.
Typically on a new connection to Snowflake, 2-3 requests are made to SSO via local browser to authenticate to Okta before the full connection is established.  However, if a connection was already opened (say with an open sql tab), and that connection had timed out, the next time a query is run, DBeaver will attempt to reconnect and create an unresolved auth loop, causing the connection to never be established, but constantly keep trying to authenticate with new browser windows.
The only resolution when this starts I have found is to fully quit DBeaver and restart it once the loop is established.  -OR- If you know the connection has timed out, Reconnect to Dbeaver explicitly before trying to run ANY query.
This is especially burdensome when MFA is enabled on the account.
Steps to reproduce, if exist:

Open a connection to Snowflake with SSO (external browser) authentication.
Allow the connection to timeout (or lose network connection).
Run any query.  (Even select 1;)
Watch as Dbeaver tries to authenticate, but open a bazillion browser connections to Okta.

Include any warning/errors/backtraces from the logs
From dbeaver-debug.log
> Start Draw2d [org.eclipse.draw2d <IP_ADDRESS>606061308]
> Start DBeaver Generic UI Plug-in [org.jkiss.dbeaver.ext.generic.ui <IP_ADDRESS>004191823]
> Start DBeaver MySQL Support [org.jkiss.dbeaver.ext.mysql <IP_ADDRESS>004191823]
> Start DBeaver UI Editors - Connections [org.jkiss.dbeaver.ui.editors.connection <IP_ADDRESS>004191823]
> Start DBeaver Snowflake UI [org.jkiss.dbeaver.ext.snowflake.ui <IP_ADDRESS>004191823]
> Start DBeaver SSH tunnels [org.jkiss.dbeaver.net.ssh.ui <IP_ADDRESS>004191823]
> Start DBeaver SSH tunnels [org.jkiss.dbeaver.net.ssh <IP_ADDRESS>004191823]
Initiating login request with your identity provider. A browser window should have opened for you to complete the login. If you can't see it, check existing browser windows, or your OS settings. Press CTRL+C to abort and try again...
Initiating login request with your identity provider. A browser window should have opened for you to complete the login. If you can't see it, check existing browser windows, or your OS settings. Press CTRL+C to abort and try again...
Initiating login request with your identity provider. A browser window should have opened for you to complete the login. If you can't see it, check existing browser windows, or your OS settings. Press CTRL+C to abort and try again...
Initiating login request with your identity provider. A browser window should have opened for you to complete the login. If you can't see it, check existing browser windows, or your OS settings. Press CTRL+C to abort and try again...
Initiating login request with your identity provider. A browser window should have opened for you to complete the login. If you can't see it, check existing browser windows, or your OS settings. Press CTRL+C to abort and try again...

From .log (there are several of these repeating errors)
!STACK 0
java.lang.NullPointerException
	at org.eclipse.swt.graphics.Image.internal_new_GC(Image.java:1628)
	at org.eclipse.swt.graphics.GC.<init>(GC.java:262)
	at org.eclipse.swt.graphics.GC.<init>(GC.java:223)
	at org.eclipse.jface.text.source.LineNumberRulerColumn.doubleBufferPaint(LineNumberRulerColumn.java:693)
	at org.eclipse.jface.text.source.LineNumberRulerColumn.lambda$2(LineNumberRulerColumn.java:619)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4387)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1512)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1535)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1520)
	at org.eclipse.swt.widgets.Control.drawWidget(Control.java:1266)
	at org.eclipse.swt.widgets.Canvas.drawWidget(Canvas.java:176)
	at org.eclipse.swt.widgets.Widget.drawRect(Widget.java:776)
	at org.eclipse.swt.widgets.Canvas.drawRect(Canvas.java:170)
	at org.eclipse.swt.widgets.Display.windowProc(Display.java:6000)
	at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
	at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:5265)
	at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5673)
	at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
	at org.eclipse.swt.internal.cocoa.NSApplication.nextEventMatchingMask(NSApplication.java:92)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3785)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1160)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1049)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:658)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:557)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:154)
	at org.jkiss.dbeaver.ui.app.standalone.DBeaverApplication.start(DBeaverApplication.java:233)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.base/java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:657)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:594)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1447)

I have the same issue with Snowflake & DBE

I have the same issue; Win10 Enterprise, jdbc, snowflake driver, chrome as default browser. Our company uses proxy servers. So usually it ends up with restart of Dbeaver and/or Chrome. Killing of connections from Chrome with TcpView also works.
Dbeaver 7.04
All in all a great client though!

same....really awful

I can't reproduce this as we don't have such test environment.
However there were a few fixes/improvements of connection state invalidation recently.
Does this problem still happen?

Yes, this still happens on 7.1.5 and most recent Snowflake JDBC driver 3.12.10.

Still happening here for me too - DBE <IP_ADDRESS>008180850

I wrote to Snowflake about this issue and found a solution that can be set up server-side: https://docs.snowflake.com/en/user-guide/admin-security-fed-auth-use.html#optional-using-connection-caching-to-minimize-the-number-of-prompts-for-authentication
This enables token caching for the MFA auth. It solved this problem for me because DBeaver can then re-use the auth token from the initial MFA request.


fix: adjust path finding for schemas in codebuild

Description of changes
There is a difference in the way that paths are resolved in CircleCI vs CodeBuild. This was causing many Windows tests to fail because the paths to schemas would not resolve correctly.
This PR also enables artifacts for Windows tests.

Issue #, if available

Description of how you validated changes
Checklist

[ ] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
[ ] Pull request labels are added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #12771 (df3f417) into dev (ec9a2ba) will increase coverage by 48.43%.
The diff coverage is 57.14%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##              dev   #12771       +/-   ##
===========================================
+ Coverage    0.00%   48.43%   +48.43%
===========================================
  Files        1296      841      -455
  Lines      149743    38076   -111667
  Branches     1296     7752     +6456
===========================================
+ Hits            0    18441    +18441
+ Misses     148447    18045   -130402
- Partials     1296     1590      +294

Impacted Files
Coverage Δ

...ify-category-function/src/events/prePushHandler.ts
33.33% <0.00%> (+33.33%)
:arrow_up:

...ider-utils/awscloudformation/utils/layerHelpers.ts
21.80% <0.00%> (+21.80%)
:arrow_up:

...ib/S3AndCloudFront/helpers/configure-CloudFront.js
87.06% <ø> (+87.06%)
:arrow_up:

...lify-category-hosting/lib/S3AndCloudFront/index.js
89.65% <ø> (+89.65%)
:arrow_up:

...e/src/amplify-node-pkg-detector/lock-file-types.ts
100.00% <ø> (+100.00%)
:arrow_up:

.../src/amplify-node-pkg-detector/yarn-lock-parser.ts
100.00% <ø> (+100.00%)
:arrow_up:

packages/amplify-cli-core/src/constants.ts
100.00% <ø> (+100.00%)
:arrow_up:

...es/amplify-cli-core/src/context/plugin-platform.ts
33.33% <0.00%> (+33.33%)
:arrow_up:

...s/amplify-cli-core/src/errors/amplify-exception.ts
82.35% <ø> (+82.35%)
:arrow_up:

...ackages/amplify-cli-core/src/help/commands-info.ts
100.00% <ø> (+100.00%)
:arrow_up:

... and 33 more

... and 1261 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Added Docs for CDC Webhook Sink

Closes #10876
Added details on sink uri, parameters, options, and examples to docs for webhook sink.
Labeled as beta.

This change is

As you review this @amruss, wondering if the additional section I've added in this PR under the option table for webhook_sink_config would be a good candidate for the "Advanced Configuration/Operator" section mentioned in #11001? — starting working on the docs for this.

As you review this @amruss, wondering if the additional section I've added in this PR under the option table for webhook_sink_config would be a good candidate for the "Advanced Configuration/Operator" section mentioned in #11001? — starting working on the docs for this.

Yes I think that would be a good idea, fits with the kafka_sink_config

As you review this @amruss, wondering if the additional section I've added in this PR under the option table for webhook_sink_config would be a good candidate for the "Advanced Configuration/Operator" section mentioned in #11001? — starting working on the docs for this.

Yes I think that would be a good idea, fits with the kafka_sink_config

OK, I will likely make a separate PR to get those together.

cc @mikeCRL


Remove PR branch

This PR adds a change to the repoman workflow in order to facilitate the removal of PR branches on target template repos, once a template PR has been merged.
The scope of change impacts the repoman pipeline and associated scripts. However, existing functionality and PR comments pre-merge have been preserved and tested in our fork.

@danieljurek - Can you please review?


Use memoized suppliers to lazy load resources

Remove the need to synchronize on reads for lazily initialized
singleton resources, particularly in the configuration and context
utilities, using Suppliers.memoize
Apply to DefaultConfiguration.getInstance() to avoid unnecessary
object creation whenever that is called
Make all ServerContext fields final, and use memoize to lazily load
anything that was previously checking if it was set in a synchronized
getter method
Use computeIfAbsent in ServerConfigurationFactory, and make its caches
of configuration objects non-static, so they only live as long as the
ServerContext that created it lives; this, along with using
ConcurrentHashMaps, dramatically simplifies this code
Reduce ServerContext reliance on ServerConfigurationFactory when it
already has the information (notably, it has the instance of
SiteConfiguration it used to construct the ServerConfigurationFactory)
Add a builder option for SiteConfiguration.empty() for use with tests
Update related tests, and make ServerContextTest.testCanRun more
robust

Were these changes pulled from the ZK single node prop store refactor?

Yes - the goal is to submit changes that are adjacent to the single node changes and have them submitted separately to reduce the number of absolute changes in the single node PR.  It also contains changes that @ctubbsii identified during his review that were not originally in the single node PR, but are general code improvements and were in areas touched by the single node PR
If these changes are merged, the the single prop node PR can be overlaid on top of them with work that is being done as part of his review.


COOK-29 Remove -norandkey, as it's the default (and invalid)

Do not use the invalid -norandkey option as it's only available in certain versions of MIT-KRB5 and it's the default setting. This was done so it would be explicit, but it's not necessary and breaks certain versions of Kerberos, specifically the version shipped with older CentOS.

LGTM 👍


[ libmysql] build failure

Host Environment

OS: Windows 10
Compiler: Visual Studio Build Tools 2019 16.5.5

To Reproduce
Steps to reproduce the behavior:
./vcpkg install libmysql:x64-windows
Failure logs
-err.log:
FEHLER: Auf dem Remotesystem muss Windows 2000 oder höher ausgeführt werden.

-- Acquiring MSYS Packages...
-- Acquiring MSYS Packages... OK
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
    Command failed: TASKKILL /F /IM gpg-agent.exe /fi "memusage gt 2"
    Working Directory: C:/Users/<USER>/vcpkg/vcpkg/downloads/tools/msys2
    Error code: 1
    See logs for more information:
      C:\Users\<USER>\vcpkg\vcpkg\buildtrees\icu\-err.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_acquire_msys.cmake:121 (vcpkg_execute_required_process)
  ports/icu/portfile.cmake:78 (vcpkg_acquire_msys)
  scripts/ports.cmake:90 (include)

Error: Building package icu:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: icu:x64-windows
  Vcpkg version: 2020.02.04-nohash

Additional context
I tried updating vcpkg

Do you have spaces in the path? If so, please move vcpkg to a folder without spaces

Translated - ERROR: Windows 2000 or higher must be running on the remote system.
This message does appear to originate from vcpkg - but from Windows itself while trying to negotiate a secure connection.

Hi @Eschryn
Thanks for posting this issue.
It seems that this is not a port bug. It might be something with the permission on your machine.
Could you please refer to this link  or look for some other similar info to try it again?
Since I am also not familiar with this. I did some search about this, but I'm not sure if this can work for you.

@Eschryn
Could you please help confirm if this only happens for libmysql?
Can you install other ports successfully?

I think @Eschryn had the same issue with icu - #11334, but it was closed as a duplicate.

Sorry for the late reply - yes i have this issue so far only with this port. Also the link you provided - the images aren't available anymore and the link that was added in the post is broken.

libmysql has been updated to 8.0.20.
Could you please try to update vcpkg and rebuild this port?

@Eschryn
Does this issue still exist with the latest version?

I cannot reproduce this on my machine. Please update vcpkg to the latest version to rebuild or clone a new vcpkg repo.
It might be something with msys, please see https://github.com/microsoft/vcpkg/issues/9427
Please feel free to reopen this if it is still a problem for you.


Error Installing Express

Description
Attempting to install express using typings install express --save results in the following error:
typings ERR! message Unable to find "express" ("npm") in the registry. Did you want to try searching another source? Also, if you want contribute these typings, please help us: https:/
/github.com/typings/registry
typings ERR! caused by https://api.typings.org/entries/npm/express/versions/latest responded with 404, expected it to equal 200

Has the end point of the type definition files moved?
Versions
[From typings -v 1.0.2]

It never existed, you must have been using --ambient before. Please search existing issues. There was literally the same issue this morning: https://github.com/typings/typings/issues/503.


OSError: Cannot detect RPi-Sense FB device

Hi there ! Recently receive my rpi together with rpi. Using raspbian and installed sense-hat according to documentation. Still receiving this issue while trying the examples provided for sense-hat.
was looking through "OSError: Cannot detect RPi-Sense FB device #28" and I tried the following command:
sudo apt-get install device-tree-compiler
and I received this output:
pi@raspberrypi:~ $ sudo apt-get install device-tree-complier
Reading package lists... Done
Building dependency tree
Reading state information... Done
Unable to locate package device-tree-complier
could it be "unable to locate package device-tree-complier" the problem? if so, how can I solve it?
Thanks ! on the side note I am working on my final year project using the sense-hat :)

Sorry to hear you're having trouble with it. How is the HAT connected to the pi? This usually seems to be caused by poor contact or an incorrectly fitted HAT. Avoid removing or attaching it while the pi is powered on.
Also note that it's compiler, not complier (typo).
On 2 August 2017 7:43:11 AM GMT+01:00, canxerLX<EMAIL_ADDRESS>wrote:

Hi there ! Recently receive my rpi together with rpi. Using raspbian
and installed sense-hat according to documentation. Still receiving
this issue while trying the examples provided for sense-hat.
was looking through "OSError: Cannot detect RPi-Sense FB device
#28" and I tried the following command:
sudo apt-get install device-tree-compiler
and I received this output:
pi@raspberrypi:~ $ sudo apt-get install device-tree-complier
Reading package lists... Done
Building dependency tree
Reading state information... Done
Unable to locate package device-tree-complier
could it be "unable to locate package device-tree-complier" the
problem? if so, how can I solve it?
Thanks ! on the side note I am working on my final year project using
the sense-hat :)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RPi-Distro/python-sense-hat/issues/77

This is how I connect my HAT to the pi. Am I supposed to push it all the way down? cause the last i tried it didnt work and I was afraid I might push it way down. So the inability to locate the device tree compiler is due to the loose connection of the HAT?

Yes, you do need to push it all the way down, and I believe it should be okay after that. If it feels like you're having to force it, check that all the pins are lined up and none are getting bent.
The reason that you were unable to install device-tree-compiler is that you're written it wrong
You typed 'device-tree-complier' instead of 'device-tree-compiler'. I don't think you'll need it anyway.

I've pushed it down all the way. Still didnt work. here's some of the output from my terminal:
sudo apt-get install device-tree-compiler
Reading package lists... Done
Building dependency tree
Reading state information... Done
device-tree-compiler is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
uname -a
Linux raspberrypi 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
vcgencmd version
Jul  3 2017 14:20:31
Copyright (c) 2012 Broadcom
version 4139c62f14cafdb7d918a3eaa0dbd68cf434e0d8 (tainted) (release)
ls /dev/fb*
/dev/fb0
dmesg.txt
sudo dtc -I fs (slash)proc(slash)device-tree.txt
the device-tree-compiler is fine now. I am guessing there is something wrong with dmesg and sudo dtc -I fs /proc/device-tree because there are some warnings and unsuccessful messages.
P.s. I am learning everything from scratch. please be patient with me :P

Sorry about the late reply.
What that output tells us is that the HAT is not seen. It could be because the HAT is faulty or because there is still an issue with the contacts.
I would shut down the pi, unplug the power, take the HAT off and put it back on a few times to make sure it's properly seated. If that doesn't work, I'd try adding dtoverlay=rpi-sense to /boot/config.txt and rebooting. That would bypass the auto-detection and act as if the HAT is there even if it doesn't look like it. If that still doesn't work, I would ask for a replacement from the seller.

@XECDesign Hello, I am a student and I have the same problem to use my sense hat for a project, I already read many answers that you wrote but I cant to make it work, could you help me please? I have a RPI 3 and the error says
OSError: Cannot detect Rpi-Sense FB device

Hi @Zam95, if the information in this issue and other issues does not help, you may have to get the HAT replaced. If it's attached correctly and has good contact with all of the pins, but isn't working while running Raspbian, then there's something wrong with the hardware.

Hi @XECDesign I try to make sense hat work with 2 diferent raspberrys. In the raspberry pi3 the leds only flash in white when I connect raspberry to the power, in the raspberry pi2 the leds always are on in rainbow until I disconect the raspberry.
 I see files but i dont understand, sorry I am new in the Raspberry world :(
Thanks for your attention and sorry for my bad english

I don't have instructions, but off the top of my head:
On a pi with the sense hat, enable SPI in raspi-config, clone that repo, install dependencies, run make and make flash.
This is getting more into AVR territory than Raspberry Pi.

Hi @XECDesign  Thanks for your reply, I already clone that repo, SPI is enabled, but what is "install dependencies"?
When I put make inn terminal the output is  make: *** No targets specified and no makefile found.    Stop.
Sorry I am really really n00b but i need make it work the Sense hat

Hi @XECDesign Thanks for your reply, I already clone that repo, SPI is enabled, but what is "install dependencies"?

sudo apt-get install gcc-avr avr-libc avrdude

When I put make inn terminal the output is make: *** No targets specified and no makefile found. Stop.
You need to run it from the rpi-sense directory that you cloned earlier.

Thanks @XECDesign  I install dependencies, I run Make and the output is:
pi@raspberrypi:~/rpi-sense $ make
avr-gcc -g -Wall -Os -mmcu=attiny88 -c -o main.o main.c
avr-gcc -Wall -mmcu=attiny88 -c -o rpi-sense.o rpi-sense.S
avr-gcc -g -Wall -Os -mmcu=attiny88 -Wl,- Map,rpi-sense.map -o rpi-sense.elf main.o rpi-
sense.o
avr-objdump -h -S rpi-sense.elf > rpi-sense.lst
avr-objcopy -j .text -j .data -O ihex rpi-sense.elf rpi-sense.hex
avr-objcopy -j .text -j .data -O binary rpi-sense.elf rpi-sense.bin
avr-objcopy -j .text -j .data -O srec rpi-sense.elf rpi-sense.srec
avr-objcopy -j .eeprom -- change-section- lma .eeprom=0 -O ihex rpi-sense.elf rpi-
sense_eeprom.hex \
|| { echo empty rpi-sense_eeprom.hex not generated; exit 0; }
avr-objcopy: -- change-section- lma .eeprom=0x00000000 never used
avr-objcopy -j .eeprom -- change-section- lma .eeprom=0 -O binary rpi-sense.elf rpi-
sense_eeprom.bin \
|| { echo empty rpi-sense_eeprom.bin not generated; exit 0; }
avr-objcopy: -- change-section- lma .eeprom=0x00000000 never used
avr-objcopy -j .eeprom -- change-section- lma .eeprom=0 -O srec rpi-sense.elf rpi-
sense_eeprom.srec \
|| { echo empty rpi-sense_eeprom.srec not generated; exit 0; }
avr-objcopy: -- change-section- lma .eeprom=0x00000000 never used

and make flash
pi@raspberrypi:~/rpi-sense $ make flash
sudo avrdude -c linuxspi -p t88 -P /dev/spidev0.0 -U flash:w:rpi-sense.hex
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
avrdude: Device signature = 0x1e9311 (probably t88)
avrdude: NOTE: "flash" memory has been specified, an erase cycle will be performed
To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "rpi-sense.hex"
avrdude: input file rpi-sense.hex auto detected as Intel Hex
avrdude: writing flash (1168 bytes):
Writing | ################################################## | 100% 0.24s
avrdude: 1168 bytes of flash written

avrdude: verifying flash memory against rpi-sense.hex:
avrdude: load data flash data from input file rpi-sense.hex:
avrdude: input file rpi-sense.hex auto detected as Intel Hex
avrdude: input file rpi-sense.hex contains 1168 bytes
avrdude: reading on-chip flash data:
Reading | ################################################## | 100% 0.16s
avrdude: verifying ...
avrdude: 1168 bytes of flash verified
avrdude: safemode: Fuses OK (E:FF, H:DF, L:EE)
avrdude done.  There's not much else you can do without access to a scope or logic analyser and an AVR JTAG debugger and that's certainly not something somebody could talk you through remotely.

AVR was left open by design
'...As a fun bonus mode, the SPI peripheral on the Atmel has been hooked up
to the Pi’s SPI interface – you can reprogram your HAT in the field! We use
this method to get the firmware into the Atmel during production test – and
we leave it unprotected so you can substitute the stock firmware to get it
to do whatever you want. Seriously. First person to turn this sensor HAT
into a quadcopter controller HAT wins a cookie from me.'
Does the bottom of this page help ?
https://www.raspberrypi.org/documentation/hardware/sense-hat/
On 14 Sep 2017 17:18, "XECDesign"<EMAIL_ADDRESS>wrote:

I am a little surprised it was even programmable. There's not much else
you can do without access to a scope or logic analyser and an AVR JTAG
debugger and that's certainly not something somebody could talk you through
remotely.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/RPi-Distro/python-sense-hat/issues/77#issuecomment-329533857,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALALt46theoWV-Sc9ECaNeJv3i86a8lEks5siVHigaJpZM4Oqqi9
.

@bsimmo, op has already re-programmed the AVR firmware and it has not helped the issue. The instructions on the page you linked are for flashing the EEPROM, which would not help.

I though that but it's straight after the AVR heading.. that's why I asked
if it would help.
(I was manly saying why the AVR was open to write, though given it can be
written to why can it not see it (is that a different interface and what
you meant)).
I'd send it back personally/ask for a replacement (warranty), something's
not right obviously.
On 14 Sep 2017 17:51, "XECDesign"<EMAIL_ADDRESS>wrote:

@bsimmo https://github.com/bsimmo, op has already re-programmed the AVR
firmware and it has not helped the issue. The instructions on the page you
linked are for flashing the EEPROM, which would not help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RPi-Distro/python-sense-hat/issues/77#issuecomment-329543071,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALALtwvC0MnOVnKzQn4vk7esR6aYDgOPks5siVmtgaJpZM4Oqqi9
.

Ah right. Programming is done over SPI. Although that part of it is clearly working, I2C communication is not.

Thanks @XECDesign  and @bsimmo I am very confused, the behavior of the Sense hat is weird.
The different behaviour between devices is interesting. It means when the device is plugged into a pi 3, the firmware on the AVR is not able to turn on the LEDs and display the rainbow pattern. On the pi 2, it is. This is the first thing the AVR tries to do when it gets power.
How are you powering your pi? Do you ever see a lightning bolt or any other icon in the top right corner?

Hi @XECDesign my power supply give me 5V, 2000 mA, I remember at some point
a lightning appeared in RPI3
Do you know if the sense hat can be repair? Where? Or I have to throw it in
the trash and buy a new :(
Greetings from Mexico.
2017-09-15 10:38 GMT-05:00 XECDesign<EMAIL_ADDRESS>
When you run i2cdetect -y 0, you're looking devices on a different bus.
The different behaviour between devices is interesting. It means when the
device is plugged into a pi 3, the firmware on the AVR is not able to turn
on the LEDs and display the rainbow pattern. On the pi 2, it is. This is
the first thing the AVR tries to do when it gets power.
How are you powering your pi? Do you ever see a lightning bolt or any
other icon in the top right corner?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RPi-Distro/python-sense-hat/issues/77#issuecomment-329818713,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ad8pDaT9SCZVa7q24arsWXaqyp7Ly-Akks5sipnagaJpZM4Oqqi9
.

It's not something you'd typically get repaired, but it should be covered by warranty.


reduce comparison conditional

:bow: I really appreciate the contribution, but since it does not affect performance and either functionality I am going to decline this.
As a matter of taste, I prefer the so called yoda conditions with identical operator since they make for less mistakes and are not easy to ignore as an !.
PS: I am really sorry for the delay in the response, I saw this early but declined to comment due to not being eager to merge it... I was afraid to discourage you or something. Seems like I've done it without making any comment, so for that I am sorry. Thank you again and keep awesome! :panda_face:


use local registry when running acceptance tests

Closes: https://github.com/weaveworks/weave-gitops/issues/1158

What changed?
When running make acceptance, it builds the local docker image locally and ensures that its used by all the acceptance tests

Why?
To ensure the acceptance tests actually run against the local code changes

How did you test it?
Manually

Release notes
no

Documentation Changes
no
Example
Local code change (not comitted):
modified: pkg/helm/watcher/controller/helm_watcher.go
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
@ pkg/helm/watcher/controller/helm_watcher.go:52 @ type HelmWatcherReconciler struct {
// Because the watcher watches all helmrepositories, it will update data for all of them.
func (r *HelmWatcherReconciler) Reconcile(ctx context.Context, req ctrl.Request) (ctrl.Result, error) {
    log := logr.FromContextOrDiscard(ctx).WithValues("repository", req.NamespacedName)
    log.Info("jake rocks")

running make acceptance-tests:
make acceptance-tests
./tools/deploy-local-registry.sh
66d0e4d9eb6b7fda1899742fb97c5df6a5249f52c4fd937b23c10988fecdd29c
registry deployed
docker build -t localhost:5000/wego-app:latest .
Sending build context to Docker daemon  418.2MB
Step 1/29 : FROM node:14-buster AS ui

Once the tests are finished we can play around with the cluster to check everything is as expected
check the pod is using a local image:
k -n test-namespace describe pod wego-app-59f86c677f-pjxzh
Containers:
  wego-app:
    Image:         localhost:5000/wego-app:latest
    Image ID:      localhost:5000/wego

check logs:
k -n test-namespace logs wego-app-59f86c677f-pjxzh | grep jake
{"level":"info","ts":1643993610.278945,"logger":"controller.helmrepository","msg":"jake rocks".....

Running a local check on this.

@aclevername Yep, there is a problem. On OSX the port 5000 is a reserved port by ControlCenter. Make it 5001 and then you're golden. :)

Can we please have a kind create cluster in the make acceptance-test target?

@aclevername Nice, worked for me. I stand by my +1

@aclevername Yep, there is a problem. On OSX the port 5000 is a reserved port by ControlCenter. Make it 5001 and then you're golden. :)

👍

Can we please have a kind create cluster in the make acceptance-test target?

What do you mean? Why do we need this?

What do you mean? Why do we need this?

When I start the test:
STEP: Given I have a brand new cluster with a long cluster name
time="2022-02-07T09:10:48+01:00" level=info msg="Creating a kind cluster "
Delete existing kind clusters
Deleted clusters: []
Create a new kind cluster with name
Registry Host: kind-registry
ERROR: unknown command "kindest/node:v1.21.1" for "kind create cluster"
time="2022-02-07T09:10:49+01:00" level=info msg="Failed to create kind cluster"
time="2022-02-07T09:10:49+01:00" level=fatal msg="exit status 1"

So maybe this is a problem with one of the tests which doesn't create a cluster for itself?

Oh also, a follow-up should be to remove the pend from the profiles tests.


HSOptical sample

Existing Sample Changes
Description
Fix for error on PVC machine, CMakefile change and README update.
Type of change
Please delete options that are not relevant. Add a 'X' to the one that is applicable.

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[X] Implement fixes for ONSAM Jiras

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[X] Command Line
[ ] oneapi-cli
[ ] Visual Studio
[ ] Eclipse IDE
[ ] VSCode
[X] When compiling the compliler flag "-Wall -Wformat-security -Werror=format-security" was used

.ipynb_checkpoint has to be removed

.ipynb_checkpoint has to be removed

deleted .ipynb_checkpoints from folders.

can be merged

@jkinsky Can you review the README? Once I get your approval, I will merge.


cmd.exe not found

running: docker run -it --rm --entrypoint "cmd.exe" counter-image
Yields: docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "cmd.exe": executable file not found in $PATH: unknown.

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

ID: 4c7470d2-9a57-7654-e13a-4f912898f7aa
Version Independent ID: 58d57b81-4ca6-6536-8788-f212402b41a7
Content: Containerize an app with Docker tutorial - .NET
Content Source: docs/core/docker/build-container.md
Product: dotnet-fundamentals
Technology: dotnet-docker
GitHub Login: @IEvangelist
Microsoft Alias: dapine

The error mentions OCI which is Linux. You're using the Windows, switch to the Linux tab instead.
Windows

Linux

docker run -it --rm --entrypoint "bash" counter-image

I'm going to close this, but we can reopen it if needed.


SPIKE signing out of DSI when we sign out of support or Manage

Proof of concept — not for merging!
Context
When a user signs out of Support or Manage, they stay signed in to DfE Sign-in. This means it's possible to log back in as them by clicking on the "Sign in with DfE Sign-in" button — DSI recognises them and forwards them back to us for a new session.
We would like to sign them out of DSI at the same time. Thankfully, TVS are doing this already so we can look at their work to see what we need to do.
The process is outlined in the (draft!) OpenID Connect spec here: https://openid.net/specs/openid-connect-session-1_0.html#RPLogout.
The basic idea is that when we sign a user out, we send them to DfE Sign-in first, then DSI sends the user back to us for a final logout.
I've attempted this in the following way:
Add two methods to DfESignInUser: logout_url_for_support_interface and logout_url_for_provider_interface. These return the special sign-me-out path on DfE Sign-in, which will sign the user and and then redirect them to us. We have separate methods because this can happen in two contexts, and we need to know which context we started in so we can send the user to the appropriate 'just signed out' page. We persist this information using the state param on the DSI URL.
When we hit the destroy actions in SupportInterface::SessionsController or ProviderInterface::SessionsController we redirect immediately to DSI's sign-me-out path. I preferred to leave these actions in the controllers rather than write the DSI urls directly into the template as we want to continue to support bypass mode and authentication by email. These modes are both broken by this PR — fixing the destroy actions should make them work again. Maybe we could still "optimistically" destroy the session in those actions.
After DSI has signed us out, it sends the user to DfESignInController#callback_after_signout. This destroys the session on our side (but see above) and redirects to the right page using the state param we passed earlier.
ALSO
We store id_token in the DSI user details in the session. This is "recommended" in the spec and TVS do it, but I'm not sure what happens if it's missing. We could well have user sessions in an id_token-less state when we first ship this.

https://trello.com/c/HofRikzT/2381-spike-signing-out-of-manage-also-signs-you-out-of-dfe-sign-in

This looks good, but I have questions about DfESignInController#callback_after_signout. Is that URL also called if the user signs out from DSI independently (say, from Find or from the DSI UI directly).

This looks good, but I have questions about DfESignInController#callback_after_signout. Is that URL also called if the user signs out from DSI independently (say, from Find or from the DSI UI directly)?

I think callback is probably not the right name for this action as it implies a webhook or sth, whereas in reality the user's own browser visits it. DSI knows to send them there bc we include our post_logout_redirect_uri when we build the link to sign out of DSI
https://github.com/DFE-Digital/apply-for-teacher-training/pull/2433/files#diff-e2f6e0bbd2ff99fd653c1c30472258aaR65-R72

Small updates:

on re-reading the spec, it actually prescribes the optimistic sign-out (ie kill the apply session before redirecting), so this branch now does that
I've hopefully clarified some of the method names to indicate that DSI is what's being signed out of, and that the callback as was is really a redirect

I've discovered that missing out the id_hint parameter yields an (unhelpful) error — see below . We'll have to handle this case when we write this code proper.

https://trello.com/c/k9crMTdY/531-when-a-user-signs-out-of-manage-also-sign-them-out-of-dfe-sign-in

Thanks for the clarification @duncanjbrown! In my head the DSI logout system did have a callback system, so that we could log out users even if they signed out in a different service. But this improves the thing quite a bit! I'll do a proper review tomorrow.

Added a commit to handle the case where there's no id_token, which should unbreak email and dev-mode

Thanks for the notes @tijmenb — I'm going to close this branch now and link it from the Trello card. We'll make sure to fix these up when we do this for production.


Support Flask 2.3

next step should be to support Flask 3.0 by supporting Werkzeug 3.0. I have yet to test that
Why
prevent errors due to deprecated features (as seen in https://github.com/replit/replit-py/issues/188 in the part after Flask was downgraded as poetry wanted)
What changed
Support 2.3 by accounting for the deprecation of json_encoder
Test plan
poetry update

Rollout

[x] This is fully backward and forward compatible

Thank you!


Cypress test. Canvas3D. Add check a context image.

Motivation and context
Added check a context image.
Updated the structure of .zip archive with the .pcd files.
How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below)

# Copyright (C) 2021 Intel Corporation
#
# SPDX-License-Identifier: MIT

Coverage increased (+0.02%) to 73.754% when pulling 555d2d03aecbf0432df36d427aa514cab3f01989 on dvkruchinin:dkru/update-canvas3d-check-context-image into 83a08cb22fd8e7d9ec07ce090ebefd80672278e8 on openvinotoolkit:develop.


Js+svg

OH. I see the :bug:! Your files should be named svg.transform.js and js.transform.js
While you're at it, I would rename the Transformers to Transforms too.

It's much worse than that!  This branch is so old it uses the old API!!!

Thanks!
Torn between merging your code and holding you to writing a few more tests to ensure that the JS runs, the SVG is displayed, etc.

Actually... can you make a test that ensures that all our exports happen (testing index.js).

I'll go ahead and merge this and add on some tests.


samples: Add AuthorizedView examples

Change-Id: I77bb799eb448275928bcf0b562c0d4e06870c96d
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)
[ ] Rollback plan is reviewed and LGTMed
[ ] All new data plane features have a completed end to end testing plan

Fixes #<issue_number_goes_here> ☕
If you write sample code, please follow the samples format.

/gcbrun

/gcbrun


[CINFRA-687] Use larger int types in v8-replicated-logs

Scope & Purpose
This mostly replaces uint32 types for LogIndexes, because these can be expected to grow large. Additionally, an assertion is introduced when errors can't be handled.
Please review the latter part (in lib/V8/v8-utils.cpp) with extra care whether you agree that it's sensible.

Formatting issues is unrelated to this PR and already in staging/replication-2.0.


Receipt card is not working and throwing error

We have tried Receipt card as mentioned in the documentation but we are facing Go back to the main window to see this content issue like below

We have tried two ways -
1. JSON -

2. Csharp -

Could you please help on this.

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

ID: 3fb4394d-25b1-8752-3996-fe3a2934732d
Version Independent ID: 6d391381-89d0-117c-27cc-00043bd26a36
Content: Types of cards - Teams
Content Source: msteams-platform/task-modules-and-cards/cards/cards-reference.md
Service: msteams
GitHub Login: @surbhigupta
Microsoft Alias: lajanuar

@Harikrishnan-MSFT - Thanks for reporting your issue. We will test this and update you soon. Thanks

@Harikrishnan-MSFT - We tested the Receipt card in Teams chat and channel.
In chat we are getting below message.

In channel the card is showing properly.

We have raised a bug for this. We will let you know once we get any updates on it.

@Harikrishnan-MSFT - We received an update from the engineering team that receipt cards are now deprecated. We plan to update the documentation accordingly. It is recommended to use Adaptive Cards whenever possible.


wrong variable name _code => $fail_code

first case was using $fail_code, others were using _code
switch ... when instead of if ... elsif
better English

@Bischoff , we need also to backport this change to the 3.0 theoretically, if the step is there.

ok rebase the 3 commits in one and i merge it


fix: disable tool menu when no active project

This PR...
Changes

disable tool buttons on Get Start screen

Fixes

add disabled prop to the menu button

How to test it

open Get Start screen
show disabled File Explorer - kustomize - helm buttons

Screenshots

Checklist

[x] tested locally
[ ] added new dependencies
[ ] updated the docs
[ ] added a test

Thanks @mortada-codes , this looks good!
I just found one small thing: If you have the Helm, Kustomize or Templates pane open before closing Monokle, next time when you open the app the icon in the left menu is highlighted/active but it's also disabled.
I'm thinking we should reset the left menu selection, but maybe only if the "automatically load last project" setting is disabled.

and I also think we should have a vertical divider between the Plugin Manager pane and the "Start a project" pane

and I also think we should have a vertical divider between the Plugin Manager pane and the "Start a project" pane


[refactor] syntax cleanup

remove redundant tab/space
reuse ef declaration

You made me rethink the whole part, but it has a logical error, the declaration is not the problem. this is fixed in #175. The double declaration is purposely because otherwise it would instantiate the open source embedding, even if you provide your own, which is inefficient.
I will get #175 merged, please remove that part from your code. Thanks.

removed ef related patch

waiting for merge of #175 then

thanks @gasolin for this. We need to setup a proper linting guideline as well.


make slot usage range match structured syntax patterns

The current range constraints where the range is a class are frequently looser than the constraints on identifier mentions via structured syntax patterns.  This is causing confusion as people read the linkml documentation without looking at the linkml source and makes the inter-class diagrams refscan is making impractical to use.
Example: Range for has_input on WorkflowExecution has a range of NamedThing, this can be tightened to DataObject which what is specified in the structured_pattern syntax
'{id_nmdc_prefix}:(dobj)-{id_shoulder}-{id_blade}$'
Please go through the ranges in the schema to make sure the level of granularity is the same, making grouping classes as appropriate.

@sierra-moxon @turbomam any update on this one?  I see no updates or comments for 2 weeks so I will remove from the sprint and add the backlog label unless you're working on it?
FYI @aclum @eecavanna

I am just seeing this; apologies.  I will take it on, but I have not started it during this sprint - it should go to the next.

Agree with @sierra-moxon . Important issue, but needs to move to next sprint... is that this sprint now?
Requires automation, and seperately a long term plan to avoid saying the same thing two different ways. To be implemented in LinkML.

Agree with @sierra-moxon . Important issue, but needs to move to next sprint... is that this sprint now?
Requires automation, and seperately a long term plan to avoid saying the same thing two different ways. To be implemented in LinkML.

Yes @turbomam the new sprint started yesterday. This is a short sprint due to the Thanksgiving holiday.

Appears to have related PRs. Moving to next sprint.
@sierra-moxon let me know if this is not active.

needs to move to the next sprint.

Moving one more sprint?  @sierra-moxon let me know if you're not actively working on this.


Alt key is being mapped to meta key

The alt key ("option key") on OS X gets mapped to the meta key, making it impossible to write e.g. "@" (on my keyboard layout "@" is alt+2) and a range of other characters (©, £, $, ∞, §, |, [, ], etc.).

Hi @jsageryd,
I'm not sure this helps, but could you try configuration (~/.gotty) described below?
preferences {
    alt-sends-what = "browser-key"
}

or
preferences {
    alt_is_meta: true
}

By the way, what type of keyboard are you using? Just curious.

Context
$ gotty --version
gotty version 0.0.10

This works:
preferences {
  alt-sends-what = "browser-key"
}

This does not work:
preferences {
  alt_is_meta = true
}

Problem solved! Is there any way to supply this as a cmdline option?

Sorry, the correct syntax was alt_sends_what = "browser-key" (underscores).
Anyway, I'm glad to hear you can now use your alt key.
It sounds hard to support preferences by command line options because there are too many preferences and some of them needs json objects.

Closing as the issue has been solved. As for the command line option support, please create a new issue as a feature request.


Remove fluid on compare diff page

As discuessed in https://github.com/go-gitea/gitea/pull/24598/files#r1189290462
After:
Diff Page

New PR Page

Right edge of boxes should align. Is this an existing issue or regression from here?

Not regression, 1.19 is the same.


How to configure +org-eval-handler to use jupyter python interpreter?

https://github.com/hlissner/doom-emacs/commit/8ae0e799189b2685acd10632aa5ea24e573cd1a9
Before this commit, I used to execute my source blocks with gr and it would just work.
Now I can eval a region but it is with a different interpreter than org-ctrl-c-ctrl-c. How can I configure it?
Thank you!

Since jupyter-python blocks are likely using python's eval handlers, you should be able to set python-shell-interpreter to your interpreter of choice.
A more robust system is needed to accommodate wider support of more src block languages. It's a non-trivial endeavor and low priority at the moment, but I'll welcome PRs.

I am not really sure what functions are being called when org-ctrl-c-ctrl-c is called inside a jupyter-python source block. What I would like is to use the current "session" also when running quickrun.
For now, I just mapped gr back to executing the code block. Thank you anyway.

The original gr operator is used for evaluating code on the fly. As of 3b13105e0 it now has jupyter support. To use it to evaluate a src block, type g r i e. gr = the evaluate operator, ie = "inner element" (a src block is an element).
This differs from C-c C-c in how they are evaluated. C-c C-c will evaluate the src block conventionally, as a whole. gr can be used to evaluate a subset of a src block (or the entire thing if you like). It would be especially useful for folks with literate configs. They can evaluate subsets of their elisp blocks on the fly.
I would suggest using C-c C-c (RET will also conventionally execute babel blocks at point) separately from gr, but I'll leave that to you to decide. I'll consider this issue resolved, in any case.

Thank you for explaining the difference to me! It is indeed really nice to just use gr in my literate config!
I would like to achieve the same convenience when running jupyter-python code blocks. When I try to evaluate just one line of the block with grr, I receive the error:
cl-no-applicable-method: No applicable method: jupyter-send-execute-request, nil, :code, "import pandas as pd
", :store-history, nil

while C-c C-cing a code block with just that single line works as expected.


Scaling laws pipeline

Scripts for power law fitting

@liujch1998 I'm closing this in favor of ladder-1xC branch so that we don't have to work on two separate branches. I've merged all the changes from this branch into that one, so that all the scaling / power laws related code is consolidated.