HDFS-16227. De-flake TestMover#testMoverWithStripedFile

Description of PR
TestMover#testMoverWithStripedFile fails intermittently with stacktrace:
[ERROR] testMoverWithStripedFile(org.apache.hadoop.hdfs.server.mover.TestMover)  Time elapsed: 48.439 s  <<< FAILURE!
java.lang.AssertionError: expected:<ARCHIVE> but was:<DISK>
	at org.junit.Assert.fail(Assert.java:89)
	at org.junit.Assert.failNotEquals(Assert.java:835)
	at org.junit.Assert.assertEquals(Assert.java:120)
	at org.junit.Assert.assertEquals(Assert.java:146)
	at org.apache.hadoop.hdfs.server.mover.TestMover.testMoverWithStripedFile(TestMover.java:965)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:299)
	at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:293)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.lang.Thread.run(Thread.java:748)

Example of this flaky behaviour: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3386/6/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
How was this patch tested?
Introduced wait until Namenode reports correct storage type for all blocks of given file as there might be some delay in the reporting.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 39s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
31m  5s

trunk passed

+1 :green_heart:
compile
1m 23s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
1m 16s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
1m  0s

trunk passed

+1 :green_heart:
mvnsite
1m 26s

trunk passed

+1 :green_heart:
javadoc
0m 57s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 27s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m 12s

trunk passed

+1 :green_heart:
shadedclient
16m 19s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 11s

the patch passed

+1 :green_heart:
compile
1m 14s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
1m 14s

the patch passed

+1 :green_heart:
compile
1m 10s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
1m 10s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 51s

hadoop-hdfs-project/hadoop-hdfs: The patch generated 0 new + 33 unchanged - 1 fixed = 33 total (was 34)

+1 :green_heart:
mvnsite
1m 14s

the patch passed

+1 :green_heart:
javadoc
0m 45s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 20s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m 10s

the patch passed

+1 :green_heart:
shadedclient
16m 13s

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

_ Other Tests _

+1 :green_heart:
unit
230m  7s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 46s

The patch does not generate ASF License warnings.

314m 43s

Subsystem
Report/Notes

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

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

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

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

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 8c520fca41985956cc9b30483ed78cbe7a38a0a9

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

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

Max. process+thread count
3258 (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-3429/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m 35s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  1s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
35m 27s

trunk passed

+1 :green_heart:
compile
1m 31s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
1m 23s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
1m  1s

trunk passed

+1 :green_heart:
mvnsite
1m 32s

trunk passed

+1 :green_heart:
javadoc
1m  0s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 32s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m 37s

trunk passed

+1 :green_heart:
shadedclient
19m 21s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 21s

the patch passed

+1 :green_heart:
compile
1m 29s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
1m 29s

the patch passed

+1 :green_heart:
compile
1m 18s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
1m 18s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 54s

hadoop-hdfs-project/hadoop-hdfs: The patch generated 0 new + 33 unchanged - 1 fixed = 33 total (was 34)

+1 :green_heart:
mvnsite
1m 22s

the patch passed

+1 :green_heart:
javadoc
0m 53s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 27s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m 46s

the patch passed

+1 :green_heart:
shadedclient
19m 34s

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

_ Other Tests _

+1 :green_heart:
unit
384m 18s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
1m  1s

The patch does not generate ASF License warnings.

482m 34s

Subsystem
Report/Notes

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

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

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

uname
Linux 1eafcc4d8f45 4.15.0-142-generic #146-Ubuntu SMP Tue Apr 13 01:11:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 8c520fca41985956cc9b30483ed78cbe7a38a0a9

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

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

Max. process+thread count
2019 (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-3429/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +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:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
35m 55s

trunk passed

+1 :green_heart:
compile
1m 34s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
1m 21s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
0m 59s

trunk passed

+1 :green_heart:
mvnsite
1m 31s

trunk passed

+1 :green_heart:
javadoc
0m 59s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 36s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m 40s

trunk passed

+1 :green_heart:
shadedclient
19m 36s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 24s

the patch passed

+1 :green_heart:
compile
1m 27s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
1m 27s

the patch passed

+1 :green_heart:
compile
1m 14s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
1m 14s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 55s

hadoop-hdfs-project/hadoop-hdfs: The patch generated 0 new + 33 unchanged - 1 fixed = 33 total (was 34)

+1 :green_heart:
mvnsite
1m 24s

the patch passed

+1 :green_heart:
javadoc
0m 53s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 30s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m 47s

the patch passed

+1 :green_heart:
shadedclient
18m 59s

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

_ Other Tests _

+1 :green_heart:
unit
385m  6s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 42s

The patch does not generate ASF License warnings.

482m 58s

Subsystem
Report/Notes

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

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

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

uname
Linux 4588aec4a1f7 4.15.0-142-generic #146-Ubuntu SMP Tue Apr 13 01:11:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 8c520fca41985956cc9b30483ed78cbe7a38a0a9

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

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

Max. process+thread count
1954 (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-3429/4/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

@ferhui @tasanuma could you please review? This is known flaky issue.

@aajisaka could you please take a look? It's a known issue. Thanks

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  9s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
37m 43s

trunk passed

+1 :green_heart:
compile
1m 26s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
1m 16s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
0m 59s

trunk passed

+1 :green_heart:
mvnsite
1m 24s

trunk passed

+1 :green_heart:
javadoc
0m 59s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 23s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m 36s

trunk passed

+1 :green_heart:
shadedclient
38m 38s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 23s

the patch passed

+1 :green_heart:
compile
1m 27s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
1m 27s

the patch passed

+1 :green_heart:
compile
1m 13s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
1m 13s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 52s

hadoop-hdfs-project/hadoop-hdfs: The patch generated 0 new + 33 unchanged - 1 fixed = 33 total (was 34)

+1 :green_heart:
mvnsite
1m 32s

the patch passed

+1 :green_heart:
javadoc
0m 54s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 28s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m 30s

the patch passed

+1 :green_heart:
shadedclient
36m 30s

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

_ Other Tests _

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

+1 :green_heart:
asflicense
0m 39s

The patch does not generate ASF License warnings.

491m 53s

Reason
Tests

Failed junit tests
hadoop.hdfs.web.TestWebHdfsFileSystemContract

Subsystem
Report/Notes

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

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

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

uname
Linux 69d7c950d9db 4.15.0-142-generic #146-Ubuntu SMP Tue Apr 13 01:11:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 3ddebe03089a1a01d32dc89ecce42e9c02809206

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3429/5/testReport/

Max. process+thread count
2050 (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-3429/5/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
13m 53s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
33m 24s

trunk passed

+1 :green_heart:
compile
1m 26s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
1m 16s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
0m 59s

trunk passed

+1 :green_heart:
mvnsite
1m 20s

trunk passed

+1 :green_heart:
javadoc
0m 57s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 26s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m  8s

trunk passed

+1 :green_heart:
shadedclient
21m 50s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 12s

the patch passed

+1 :green_heart:
compile
1m 14s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
1m 14s

the patch passed

+1 :green_heart:
compile
1m  6s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
1m  6s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 49s

hadoop-hdfs-project/hadoop-hdfs: The patch generated 0 new + 33 unchanged - 1 fixed = 33 total (was 34)

+1 :green_heart:
mvnsite
1m 14s

the patch passed

+1 :green_heart:
javadoc
0m 45s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 15s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
3m 13s

the patch passed

+1 :green_heart:
shadedclient
21m 47s

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

_ Other Tests _

+1 :green_heart:
unit
228m 47s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 47s

The patch does not generate ASF License warnings.

339m 45s

Subsystem
Report/Notes

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

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

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

uname
Linux 1655d0a4cc97 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 887156444d80a7b762d4caa2f289b36e259b3da9

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3429/6/testReport/

Max. process+thread count
3018 (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-3429/6/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

@virajjasani Thanks for contribution. @tasanuma @goiri @jojochuang Thanks for review!


Product Board missing 1.0 features from roadmap

Per announcement, Product Board has replaced the Windows App SDK roadmap documentation. But Product Board is missing previously listed 1.0 features, which may lead to confusion, panic, and/or volcanoes.
Product Board currently shows 8 items as landing for 1.0:

Unpackaged app support
Windowing APIs
Activation APIs
Single/multi-instancing API
Power State Notifications
Single project MSIX
Project templates
Single NuGet package

Observe none of these items make a distinction between unpackaged and packaged apps.
Attempting to associate Product Board items to previously documented roadmap items results in the following mapping:

Unpackaged app support -> ?
Windowing APIs -> Windowing
Activation APIs -> App lifecycle
Single/multi-instancing API -> App lifecycle
Power State Notifications -> Power state notifications
Single project MSIX -> Single-project MSIX
Project templates -> ?
Single NuGet package -> ?

The following items are missing from Product Board (previously on the roadmap):

WinUI 3
Text rendering
Resource management
Framework-dependent deployment

Thanks @riverar for the feedback.
In 1.0, the packaged and unpackaged features are supported equally (aside from XAML Hot Reload and Live Visual Tree) so we're removing the distinction between what's supported in packaged vs unpackaged.
WinUI 3 is listed in the Released tab under 0.5, and expanding that to support unpackaged is what the 1.0 "Unpackaged app support" item covers.
Same with text rendering, that's in the Released tab for 0.5 since that's when it was released (and didn't have unpackaged support), under the name DWriteCore (I'm going to update the name to be the friendly name we use in docs).
I'll add resource management to 0.5.
For framework-dependent deployment, that's also a 0.5 feature and given it's so fundamental and low-level, I'm not sure that's worth putting on there. The feature some developers are interested in going forward is self-contained deployment, which is in the Under Consideration tab.

@andrewleader Thanks, I missed the items on the Released tab!


Add toggle component and tests

Description

Adds the toggle component from scenic_toggle as a core Scenic.Component.Input component.
Motivation and Context

It's a nice component to have, and it was already on @boydm's roadmap.
Issues
There are a few choices I made that seemed fine for a standalone component, but should be re-thunk-about in the context of Scenic core, for consistency's sake.
Theme
I'm not totally satisfied with the handling of themes. To look "right" with the dark theme, the track's  "on" color has to be the theme's thumb color. Meanwhile, the thumb's color is the theme's text color. I wasn't sure about the best way to handle that, but I think it will be confusing, especially for a core component.
If you pass one of the "bootstrap" themes, then it's even weirder, because the track's "on" color should be the theme's background color.
Boolean ?s
I had added ? to the end of the boolean fields in the component state. It's idiomatic Elixir, but not idiomatic for Scenic components. Probably should match the rest of the components (i.e. should be removed from Toggle)
State struct
I also made the Toggle's state into a struct. That's nice for testing, but inconsistent with the rest of the components. Since state is internal to components, it would be fine to either make Toggle state into a map like the other components, or to make the other component state into structs, to match Toggle. It shouldn't affect users either way.
Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[x] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to
not work as expected)
[ ] Improvement/refactoring (non-breaking change that doesn't add any feature
but make things better)

Checklist

[x] Check other PRs and make sure that the changes are not done yet.
[x] The PR title is no longer than 64 characters.

Looking at it now.

This is great. Merging soon.
Thinking about your observations.

You are right, putting a ? at the end of the boolean fields is better. I'll update the other components, probably for 0.9

The theme thing was tricky. Somehow needed a standard way to specify a bucket of colors that gets passed around to all the components. A map with named colors seemed the easiest thing to specify. Totally get it the standard ones need more names. Also you can request that your own ones get added. Only the Components really use the theme map.

In other words, Themes was added fairly late in the game. If you have ideas on a better way to do it, I'm open to suggestions.

....and done! Thanks :)
For themes, I think the best thing to do is add any other components that belong to Core, and then take a look at the map keys. Maybe the right names will be more obvious then.


feat: add upload_id as a parameter

Fixes TRUNK-7654 and TRUNK-7716, along with trunk-io/trunk#9735.
Allows for the check service to create an empty CheckRun, then pass the id to the CLI so it can update it. See trunk-io/trunk#9735 for a more detailed explanation.
This PR must go in before trunk-io/trunk#9735.

Is it sufficient to have the old tests without upload id, or did you want me to add new ones?

old tests w/o is sufficient


SVG False After Animation

I Parse SVG, it's right.
But,after animation,it's false.
up, it's animation.
down. only show.
code:

PODS:

Macaw (0.9.2):

SWXMLHash

SWXMLHash (4.7.0)

svg image
svg.zip
result

Thank you

Reproduced. Looks like a bug, will try to fix it in this milestone.


Transpiler error when executing Clifford circuit in stabilizer simulator

Environment

Qiskit Terra version: 0.24.1
Python version: 3.10.8
Operating system: IBM Quantum Experience jupyter notebook

What is happening?
When I run the following circuit:
from qiskit import QuantumCircuit, execute
from qiskit_ibm_provider import IBMProvider

qc = QuantumCircuit(1)
qc.x(0)

provider = IBMProvider()
sim = provider.get_backend("simulator_stabilizer")
execute(qc, backend=sim, optimization_level=3)

I get the following error:
TranspilerError: "The number of qubits for Instruction(name='cy', num_qubits=2, num_clbits=0, params=[]) does not match the number of qubits in the properties dictionary: (0,)"

How can we reproduce the issue?
Run the code given above.
What should happen?
The circuit should run fine as it is only applying an X gate and therefore is apt for the stabilizer simulator.
Any suggestions?
No response

This looks to me like a miscalibration on the server-side backend.  If so, it's not related to Terra, but we can ask some people who might know who to pass this on to (@jyu00, @wshanks?).
For ease, a reproducer without attempting to run the circuit is:
from qiskit import QuantumCircuit
from qiskit_ibm_provider import IBMProvider

qc = QuantumCircuit(1)
qc.x(0)

provider = IBMProvider()
sim = provider.get_backend("simulator_stabilizer")
sim.target

I see
>>> sim.configuration().gates
[GateConfig(cx, [], gate cx c,t { CX c,t; }, [[0], [1], [2], [3], [4]], True, 'Two-qubit Controlled-NOT gate'),
 GateConfig(cy, ['lambda'], gate cy a,b { U(0,0,-pi/2) b; CX a,b; U(0,0,pi/2) b; }, [[0], [1], [2], [3], [4]], True, 'Two-qubit Controlled-Y gate'),
 GateConfig(cz, ['phi', 'lambda'], gate cz a,b { U(pi/2,0,pi) b; CX a,b; U(pi/2,0,pi) b; }, [[0], [1], [2], [3], [4]], True, 'Two-qubit Controlled-Z gate'),
 GateConfig(id, ['theta', 'phi', 'lambda'], gate id a { U(0,0,0) a; }, [[0], [1], [2], [3], [4]], True, 'Single-qubit identity gate'),
 GateConfig(x, [], gate x a { U(pi,0,pi) a; }, [[0, 1], [1, 0], [1, 2], [1, 3], [2, 1], [3, 1], [3, 4], [4, 3]], True, 'Single-qubit Pauli-X gate'),
 GateConfig(y, [], gate y a { U(pi,pi/2,pi/2) a; }, True, 'Single-qubit Pauli-Y gate'),
 GateConfig(z, [], gate z a { U(0,0,pi) a; }, True, 'Single-qubit Pauli-Z gate'),
 GateConfig(h, [], gate h q { U(pi/2,0,pi) q; }, True, 'Single-qubit Hadamard gate'),
 GateConfig(s, [], gate s q { U(0,0,pi/2) q; }, True, 'Single-qubit phase gate'),
 GateConfig(sdg, [], gate sdg q { U(0,0,-pi/2) q; }, True, 'Single-qubit adjoint phase gate'),
 GateConfig(sx, [], gate sx q { U(pi/2,-pi/2,pi/2) q; }, True, 'Single-qubit Sqrt(X) gate'),
 GateConfig(swap, [], TODO, True, 'Two-qubit SWAP gate'),
 GateConfig(delay, [], TODO, True, 'Delay instruction')]

which looks like things are quite out of sync - the parameters and qubit numbers don't match the gate names.

I'm moving this to the provider.


Fix kubectl-convert plugin typo on "Install kubectl on macOS"

Compared with the other distro guide about installation kubectl(linux, windows), the macOS installation guide has a typo about validation of kubectl-convert.
This commits fixes the typo on "Install kubectl on macOS" documentation.

/approve


Parallelize groups of integration tests in a Python module

Issue
Integration tests are slow (#104)
Solution
Group tests in a Python test file with pytest.mark.group(#)
Run each group number in a separate GitHub runner

Not suggesting. I like the performance gain of course, it's just my future maintenance anxiety kicking in.
I'd like to hear other opinions. @shayancanonical @taurus-forever

I agree with Paulo, a 2x speed up in performance is amazing. However, I am also wary of the maintenance cost. One other point not mentioned is that we now have a few tests that are not grouped - if we decide to move this direction, we should at some point change those tests to use this framework as well. Additionally, I'd like to preserve a way to run tests locally (and so would appreciate some documentation for this)

The incredible job done! Respect, Carl!
The speedup 40 mins -> 17-25 mins worth to continue here!
BTW, why difference is so high 25-17=8 mins! Could be a slow GH runner... or not-optimal charm/test is waiting for the next update-status? IMHO jammy and focal tests should take more/less the same time. Isn't it?
Unfortunately, the old approach is not scalable. The 40 mins will grow after adding new testcases to test_replication.py. We need an ability to add new tests/test-cases without slowing down PRs testing. Yes, 60 GH runners is a current problem, but we will solve HW issue.

What are other options to decrease maintenance anxiety?
What is the negative impact of split the existing test files into multiple files with a self-explanatory filenames?

FYI I've noticed that sometimes the setup (charmed-kubernetes/actions-operator) can take 5 minutes or sometimes closer to 15 minutes—but maybe that's an unrelated issue.

I saw it today too, here:
Thu, 02 Mar 2023 13:35:40 GMT  Run charmed-kubernetes/actions-operator@main
Thu, 02 Mar 2023 13:35:40 GMT  Install core snap
Thu, 02 Mar 2023 13:35:40 GMT   /usr/bin/sudo snap install core
Thu, 02 Mar 2023 13:44:34 GMT   core 16-2.58.2 from Canonical** installed

No ideas about the reasoning.
Re: tests, let's discuss in a sync today.


Bold README Features

What is the reason behind making everything bold? I do not see any benefit here? In fact, I think it makes it worse actually.


catsbhop.exe

So what does catsbhop.exe do? I am concerned cause if this is sort of cheats that are not allowed on TF2 and causes VAC ban...

This program basically came from a forums hacks that I obtained 8 years ago, which basically allows you to bhop on any server, virustotal.com identifies a trojan there so that's my mistake. However, it only takes action if you execute it, not that VAC can't detect cuz it's just a macro type of thing.


Mailbox Verification added to return accurate validation result

Is_valid was no longer returning the correct result as Mailgun added another parameter mailbox_verification as they announce changes in their email validation API.

Thanks for the PR!

Thank you very much


Popup events

This adds on:open and on:close events to the Popup class, and an example for how they might be used. I also took the opportunity to add Typescript annotations to the dispatched events for some of the other components in this project, as well.

New release going out tonight. Thanks!


Enhancement: Output different namespace

It would be nice to have an different namespace for the output i.e:
 Source({name: "mongo", namespace: "foo.bar"})
  .transform({filename: "transformers/process.js", namespace: "foo.bar"})
  ...
  .save({name: "es", namespace: "foo.bar"});

Always requires that both input and destination is the same namespace.
And ends up in this case from the mongo collection foo.bar into the elasticsearch index foo/bar.
But in some cases one would like to export to a different namespace than the default namespace used to math input/output such a feature could be e.g:
 Source({name: "mongo", namespace: "foo.bar"})
  .transform({filename: "transformers/process.js", namespace: "foo.bar"})
  ...
  .save({name: "es", namespace: "foo.bar", outputNamespace: "collections.baz"});

This is just a suggestion.
Where the input from foo.bar int the mongo collection ends into the collections/baz  -> index/mapping in elasticsearch instead of foo/bar.
As far as i can this is possible with Embulk, this would be a killer feature for transporter to have.

You can change the namespace within a transformer and set it to your desired target namespace. You can then set the sink to save for that namespace. This allows the transformer script to target different sinks using different namespaces.
See "changing namespaces" in https://www.compose.io/articles/transporters-namespace-aware-data-transfer/

Ok did not know that this site misses a wiki section for more complex examples that the articles thanks for the input here.
But still this raises question as why do i need a transformer for that?
Is it not easier to add this as part of the output sink as part of the options in the .save({...}) operation.

I was doing something similar here https://github.com/compose/transporter/issues/133

@Alino thanks yes i got it working, but still think this should be an enhancement as part of the options in the output sink.

@cristobal sorry for the lack of documentation and DSL changes.
the original purpose for the namespace was for defining the database/index + table/collection but when we wanted the ability to perform easy filtering, we chose to repurpose the namespace attribute and turned it into a regexp where the pipeline would only route messages if the document namespace matched the namespace on the node.


Open questions

Docs / Examples at: https://bsiever.github.io/microbit-pxt-softclock/
General features

What other time/date formats should be included?

Current ones may be common uses for U.S. notation, but what about international?

Currently I'm ignoring the special cases for leap years at centuries, although including them is just another couple of mods and and AND statement.  (Code is there/correct, just commented out).   It seems like the major use-cases are "calendar from 0" and "calendar from now".  Should I bother with the special cases for leap years?  Eh...Decided it wasn't significant.
Should I include anything that translates to weekday abbreviations or names ("Mon", "Tues", etc.) and month abbreviations/names?  Or is that an exercise for the user?  (Decided on "exercise for the user")
The "stopwatch" behavior could be handy.  Should I update the package to highlight this a bit more? Added completed example.
I could expose access to milli-seconds, but I didn't think it'd be useful generally.  Any thoughts? Decided accuracy undermined utility.
How's the Palette color?  I just used a default from the playground and am open to suggestions. Calling it done.
Anything else? :)

Package Prep

I should probably add a comment that indicates this assumes the micro:bit sleeps "regularly".  (Time won't be kept if a background task can't run at least every 512s or so.  The "minute changed" update requires updates at least once a minute)
Action call backs:  Is there a better approach than storing them like this?

What about re-entrant?  If there's a "on next minute" that includes a 2 minute sleep, will multiple calls be queued?

How can I improve documentation?  See: https://bsiever.github.io/microbit-pxt-softclock/ (Probably, but calling it good here for now)~~
The block and in-line block environments aren't working, but blocks does. Just the attempts to show reporter blocks in isolation are failing.
Should I use a docs directory?
Blocks don't always seem to render correctly.  Suggestions?
Add tutorial?
Is there a better way to do string formatting (padding with zeros) than the current approach, which calls leftZeroPadTo() in main.ts.
Python support check?  (looks ok so far)?
Any guidance on test.ts for this? Or examples of effective tests are included in comparable types of extensions?
Is there anything I can do to improve internationalization efforts?

Typescript vs. C++ & Performance Questions

How does C++ performance/memory compare to TS.  Should I move all the code to C++ with shims for all exported blocks?

  Do I need to mark the helper methods as shims in my typescript to avoid compiling them?  Or are unused typescript functions omitted from the executable?

In typescript I'm using constants like 60*60  (for seconds in hour).  I commonly do this in C++ for readability and know that the compiler will simplify.  Will typescript or should I just use the final value?
In typescript I'm using a const cdoy: uint16[]  = [ ... ].  Will this consume ram or go to code space? (I'd want code space)

Any plans for MicroPython support?

Hi @AirplanegoBrr --- I wasn't planning too, but I'll try to look into it.
My original code was prototyped in Python (https://github.com/bsiever/software-based-RTC-algorithm).  I think it would be pretty easy to update it a bit to work with Micro:Python's utime.  The big unknown is accuracy:  I had to do some really low-level tricks to get the MakeCode version to be accurate.

@AirplanegoBrr : A quick update.  I did make a Python version using utime and tested it.  (Test version here: https://github.com/bsiever/micropython-timeanddate).  It lost about 4 minutes of time in about 12 hours, so it's not very accurate.  I suspect this is because of the way MicroPython configures the micro:bit.  I hope to look into this in a week or two, but I think accuracy will require a more complex solution than just use of Python code.


Fix bullet points in Installation instructions.

GitHub requires four spaces to consider the bullet points at a new level.

thanks!


Update Podman to v5.0.0

Update Podman to v5.0.0
Release notes: https://github.com/containers/podman/releases/tag/v5.0.0
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[x] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This should work everywhere but I've only been able to test on an M1 macbook.
cc: @marsam

You should rebase your commit to be
podman: 4.9.3 -> 5.0.0
Also please split the patch commit to be separate and change the PR title
Check out: https://github.com/NixOS/nixpkgs/blob/master/pkgs/README.md#commit-conventions

@DontEatOreo , done.

The patch should have a different name, something like:
podman: remove mac helper message
Also please update the PR title to podman: 4.9.3 -> 5.0.0

Done.

https://github.com/containers/podman/releases/tag/v5.0.1 is now out

Hi!

Podman switched to passt for user level networking (#265409). Is it not needed here?

I needed to patch the paths in vendor/github.com/containers/common/pkg/config/default.go. Without that patch, it tried to run executables in /usr/bin, ignoring the PATH built by the nixpkgs wrapper. Have you run into this?

Reference: https://github.com/NixOS/nixpkgs/pull/301553

@WxNzEMof I didn't run into those issues yet. But I wouldn't be surprised if they were needed. I haven't had the time to come back to this for a bit. If someone else want's to take over I'll not be offended. Otherwise it can wait till I have time again.

Since v5.0.1 is out, could you amend the last commit with the new version and update the PR title?

Closing in favor of #301553 because it has a more complete approach to all features


Migrate libp2p website accounts from fleek.co to fleek.xyz

### Tasks

fleek.xyz is still in beta and fleek.co will continue to work through 2024. they keep promising a 1-click migration tool which hasn't been deployed yet. I will wait until then.

fleek.xyz is till in beta and I have confirmed that fleek.co will continue to function through the end of 2024. at least that's their current plan. they continue to promise a 1-click migration tool that has not been deployed. I will wait until then.


Bypass Low Target SDK Block

Please help

Read the comments in #22 & #47

@zacharee should it state/repeat the same line twice ?

This is addressed in the readme: https://github.com/zacharee/InstallWithOptions/?tab=readme-ov-file#install_failed_no_matching_abis.
@drogga the dialog just shows what the system returned, so if it's doubled, that means Android doubled it.


How to acknowledge Numbat in a scientific paper?

Hi, I am in the process of writing a paper, and Numbat was super helpful in doing some of the calculations. How can I acknowledge Numbat? My current plan is the following,
We thank the developers of the programming languages Julia [REF] and Numbat, which were utilized for numerical computations in this paper.

It would be great if you create a citation link for the github repo as described in https://academia.stackexchange.com/a/172780/128673 and https://x.com/natfriedman/status/1420122675813441540

I am working on excitonic condensates. I can share the link the paper once it is in arxiv (it may take a couple of weeks).
I did not write any program with numbat. All the codes were written in Julia. I used numbat to convert the values obtained from the my code into realistic units and vice versa. For example, I know how the kinetic and interaction energy scales with momentum, so I use numbat to evaluate it at one point in my momentum space grid and I use Julia to scale it accordingly everywhere.
Numbat really helps with quickly estimating a quantity when some parameter is changed.

That sounds really interesting and I will look forward to you sharing it.
Even though it wasn't a program really it still fits the issue I think. From the issue description:

All kinds of programs are welcome. Everything from simple one-line expressions to larger computations. Polished or unpolished.

I would love to hear what you would need to be able to write the Julia portions in Numbat too. I realize that Julia is a mature language with a rich ecosystem so it probably isn't feasible in the near future. But any feedback on what could drive numbat in the direction of being able to handle more of those sorts of tasks would help steer the project in the right direction.

Hi, I am in the process of writing a paper, and Numbat was super helpful in doing some of the calculations. How can I acknowledge Numbat?

Awesome, thank you for asking. I added a CITATION.cff file. Please let me know if you see any issues with it.

I'm very interested in what the paper is about and how you used Numbat while writing it. If you want to share a bit about your work and experience as it relates to Numbat it would be more than welcome as a comment on this issue: #610.

I can second this.

I would love to hear what you would need to be able to write the Julia portions in Numbat too. I realize that Julia is a mature language with a rich ecosystem so it probably isn't feasible in the near future. But any feedback on what could drive numbat in the direction of being able to handle more of those sorts of tasks would help steer the project in the right direction.

And this :+1:

I will answer the rest of the comments later, but can you also somehow add "A statically typed programming language for scientific computations with first class support for physical dimensions and units " ?
Otherwise, this is how it appears

I edited the .bib entry to the following
@misc{Peter_Numbat_2024,
author = {Peter, David},
license = {MIT},
month = oct,
title = {{Numbat}:  A statically typed programming language for scientific computations with first class support for physical dimensions and units },
url = {https://github.com/sharkdp/numbat},
version = {1.14.0},
note = {version: 1.14.0},
year = {2024}
}

It produces this

what you would need to be able to write the Julia portions in Numbat too.

I don't think that would be a good idea. Both Julia and Numbat are extremely good at what they currently do, and there is no need to implicate one's features into the other.
But here goes the answer to your question :smile:

MATLAB syntax and (almost) all linear algebra routines in MATLAB
Almost all features of matplotlib
Speed of C
Parallelization support

There are reasons why Julia was created.
However, Numbat is the best tool I know for what it already does. Please don't make it more complicated. There is no need to include matrix diagonalization or differential equation solver routines in Numbat. Those things have been implemented in every other widely-adopted languages used for scientific computing. But, no other tool is as good and reliable at converting dimension-full quantities into one another.

how you used Numbat while writing it

I mainly use Numbat as a unit converter (not as a programming language).
For example let's say I am trying to model bands in Gallium Arsenide. I have a momentum space lattice with grid spacing 0.02*h_bar/(50 angstrom) and I know the effective mass of electron is 7% of the bare electron mass. What is the kinetic energy in meV at a particular point on the grid? I can easily get the answer with Numbat
(0.02*h_bar/(50 angstrom))^2/(2 * 0.07 * electron_mass) -> meV

  (0.02 h_bar / 50 angstrom)² / (2 × 0.07 × electron_mass) ➞ millielectronvolt

    = 0.00870853 meV    [Energy or Torque]

I could in principle use a regular calculator (or even Julia), but Numbat knows all the conversion factors and fundamental constants. Julia wouldn't know that.
Once I know the kinetic energy (which is usually quadratic in momentum) at a single point, I can scale it appropriately at every point on the grid using Julia.
Suppose I have to change some parameters and do the whole calculation again? Simple, it is still a one-liner in Numbat.
I can do a similar procedure for the interaction energy (where I use numbat to get the value of the interaction at a typical point, and do rest of the calculation with Julia).
Finally, I use Julia to self-consistently solve the quantum problem using Hartree-Fock like techniques.

I will answer the rest of the comments later, but can you also somehow add "A statically typed programming language for scientific computations with first class support for physical dimensions and units " ?

This is included as abstract:
https://github.com/sharkdp/numbat/blob/ccf3aca7034c36822411ff403a4f48f0e2542ad4/CITATION.cff#L14-L17
Maybe there is a better way?

It produces this with REVTEX, which I like better than the previous one.

That looks great — thank you

Here is the paper. https://arxiv.org/pdf/2411.08091
It would be nice if the Numbat documentation is published at a journal like https://scipost.org/SciPostPhysCodeb at some point.

Thank you for the reference and good luck with your paper. Reminds me of the good old times when I was also publishing in cond-mat :smile:


addrundata reduce metadata to only fields testtracker cares about

Pull Request Functional Test Report for #1945 / 7f8e14007d17f35763c488639a427d2909666724
No tests identified for validation.
Help


Warnings about authentication storage backends

I'm not sure what these warnings are about, but I see a million of them in my builds:
2024-02-02T20:44:40.359834Z  WARN rattler_networking::authentication_storage::storage: Error retrieving credentials from backend: Platform secure storage failure: no secret service provider or dbus session found
2024-02-02T20:44:40.360430Z  WARN rattler_networking::authentication_storage::backends::file: Can't find path for file storage on /root/.rattler/credentials.json

I also get these :/ I can probably look into it.

TL;DR: This error occurs if there's no secret service daemon (e.g. KWallet, gnome-keyring, KeePassXC, ...) running. *
rattler-build depends on the following authentication storage backends from rattler_networking:

file
keyring
netrtc

And this error originates from the keyring implementation. We depend on the keyring crate for storing credentials in a compatible daemon such as KWallet, gnome-keyring or KeePassXC.
You can simply reproduce the error with this snippet:
// [dependencies]
// keyring = "2.3.2"

use keyring::Entry;

fn main() {
    let entry = Entry::new("my_service", "my_name").unwrap();
    entry.set_password("topS3cr3tP4$$w0rd").unwrap();
}

thread 'main' panicked at src/main.rs:5:45:
called Result::unwrap() on an Err value: PlatformFailure(Zbus(MethodError(OwnedErrorName(ErrorName(Str(Owned("org.freedesktop.DBus.Error.ServiceUnknown")))), Some("The name is not activatable"), Msg { type: Error, sender: UniqueName(Str
(Borrowed("org.freedesktop.DBus"))), reply-serial: 2, body: Signature("s") })))
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

keyring crate also supports multiple backends:
[target.'cfg(target_os = "linux")'.dependencies]
secret-service = { version = "3", optional = true }
linux-keyutils = { version = "0.2", features = ["std"], optional = true }

secret-service crate is used as default which depends on a secret service running.

Secret Service provides a secure place to store secrets. Gnome keyring and KWallet implement the Secret Service API.

Also, see https://specifications.freedesktop.org/secret-service/latest/
Which also means we can reproduce the same error with this snippet:
// [dependencies]
// secret-service = { version = "3.0.0", features = ["rt-tokio-crypto-rust"] }
// tokio = { version = "1.36.0", features = ["full"] }

use secret_service::EncryptionType;
use secret_service::SecretService;
use std::error::Error;

#[tokio::main]
async fn main() -> Result<(), Box<dyn Error>> {
    // initialize secret service (dbus connection and encryption session)
    let ss = SecretService::connect(EncryptionType::Dh).await.unwrap();

    Ok(())
}

thread 'main' panicked at src/main.rs:15:63:
called Result::unwrap() on an Err value: Zbus(MethodError(OwnedErrorName(ErrorName(Str(Owned("org.freedesktop.DBus.Error.ServiceUnknown")))), Some("The name is not activatable"), Msg { type: Error, sender: UniqueName(Str(Borrowed("org.f
reedesktop.DBus"))), reply-serial: 2, body: Signature("s") }))
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

There is also another case where a secret service is available but it is locked. In that case, we need to unlock it as follows:

If you are running on a headless Linux box, you will need to unlock the Gnome login keyring before you can use it.  The following bash function may be very helpful.

function unlock-keyring ()
{
    read -rsp "Password: " pass
    echo -n "$pass" | gnome-keyring-daemon --unlock
    unset pass
}

Trying to access a locked keychain on a headless Linux box often returns the  platform error that displays as SS error: prompt dismissed.  This refers to the fact that there is no GUI running that can be used to prompt for a keychain unlock.

Okay so, what can we do?
Luckily, keyring crate supports another backend (linux-keyutils) which will work on Linux systems without Gnome keyring etc.
// keyring = { version = "2.3.2", default-features = false, features = ["linux-keyutils"] }

use keyring::Entry;

fn main() {
    let entry = Entry::new("my_service", "my_name").unwrap();
    entry.set_password("topS3cr3tP4$$w0rd").unwrap();
}

The only downside of this approach is the keyring is provided in-memory by the running kernel so it will not persist across reboots.
See https://docs.rs/keyring/latest/keyring/keyutils/index.html for more information.
With all of this considered, it might be a good idea to switch to linux-keyutils backend for authentication storage.

We do have a fallback storage implemented that stores authentication data in a JSON file and which users can use if they don't want to run a fancy authentication daemon.
However, we need to silently fall through and ignore this warning / error.

I see, I created #599 to suppress the warnings.


Separate filtering algorithm from UI

The filtering algorithm can be standalone without UI components like Parser or FilteringFlow. Move the filtering algorithm into a new core components package and the UI stuff into the core ui components.

Closed by bcb9d8b81f8ca6aa255884bd05ad74396e2545ac


Can we co-exist with angular-cli project ?

Can we run angular-cli project with angular-seed ? any plan or not possible

We're using different build system. Probably it might be possible to reuse the scaffolding and code generation features of the CLI at some point, if we work on such integration, but we need to consider if it's worth it.
Do you mean anything specific? What is your use case?

@ishara, if you have any ideas please message me at gitter, or continue the discussion here.


Connection Timeout (client)

The server is normally appearing on the ASA server list, but players are unable to join.
I'm not quite sure if this has something to do with this docker image alas other images have the same problem on my vHost. Maybe it's on wildcards part.
Already mentioned in #6

Pasting my comment from #6.
Can't say that I've noticed the bug yet, I'll spin a new server and see if I experience it. After a quick check on the official discord, it looks like a bunch of people are experiencing it:

any idea why some players of my asa server could not connect and getting "Lost/timeout connection lost to host" - they could play the last days, but since the latest update its not possible

Hello everyone! I am struggling with the server I am on with constant timeouts. Is this a server issue or game issue? Can be on the server for a few seconds to a couple minutes before it either crashes or timeouts.

Connection timeout when trying to join servers, constantly.

It's likely a bug on the recent server (or client?) builds. Some people were able to temporarily fix the bug by synchronizing their clock in the Windows settings of the client PC.

This issue can be closed because it is either a issue on wildcards side or with the users firewall settings.


this is not gesture, is hand posture!!~!

this is not gesture, is hand posture!!~!

I agree. Thanks for correcting me.


No weather data available

For a few days, the built-in weather extension has shown "No weather data available" in the DashClock widget on my home screen. I tried with custom location (Anaheim, California) and with automatic location, and I got the same result. I assume it's a problem with the Yahoo Weather API, but there isn't another source that I can choose (like openweathermap or yr.no) to test that theory.

Having same issue. Tried installing better weather and changed to openweathermap with the same result. Clock and other extensions still work well for me, just not the weather.

Same issue here... no weather data the past few days

Same

Looks like Yahoo changed their API a bit:
To increase the security measure and better serving our YDN customers, weather data source will enforce OAuth 1 starting March 15, 2016. Please update your API calls with OAuth 1 enabled (via the OAuth /v1/yql end point if using YQL) using your Yahoo App key and secret.
In the meantime please try out third party weather extensions!

The more I look at Yahoo's new Weather API stuff, the more I'm thinking of just turning off the built-in weather extension in favor of third parties :( Will try to provide an update in a few days; part of their developer site is down.

Roman - I would encourage you not to remove the built-in weather extension!  Relatively speaking, there are only a few third-party weather extensions. Most of them rely on Amber Weather--and while I have nothing against Amber Weather, I don't see the need to install a third program when the extension can be authored to get the weather information directly.
This leave only a handful of other weather extensions. Unfortunately, the two that I have tried this morning both use Yahoo and are broke as well...
Perhaps you can abandon Yahoo and easily implement the Forecast.io, or another API?.

Unfortunately Forecast.io and other weather APIs cost money, which isn't really acceptable for a free app like DashClock.

https://play.google.com/store/apps/details?id=net.imatruck.betterweather was updated yesterday and should work in theory, does not in practice for me. Uses OpenWeatherMap API (http://openweathermap.org/api) which sounds like it is free.

I found one that's working for me: DashClock Weather (yr.no)
https://play.google.com/store/apps/details?id=com.ctrlplusz.dashclock.yr

Correction, BetterWeather works as well, you just have to grant the location permission manually.

Hey Roman,
I'm not very familiar with the issue, but weather.com seems to have an API which Google uses for their weather widget. Is there any way to get that data and to allow the widget shortcut to bring up a weather search to Google's card in the Google App?
https://www.wunderground.com/weather/api/

Unfortunately Weather Underground is also a paid service / has a prohibitively low free quota.

Ah, yeah, I see that. Too bad you can't hop onto the Google API key license.
Any way to ask for in-app donations to cover the costs? Or offer a paid version of the app?

Try to change:
http://weather.yahooapis.com/
to:
http://xml.weather.yahoo.com/
worked for my own scripts.

I was considering that too but that seems like a short term fix and isn't
official AFAICT?
On Wed, Mar 30, 2016, 3:23 PM keckelt<EMAIL_ADDRESS>wrote:

Try to change:
http://weather.yahooapis.com/
to:
http://xml.weather.yahoo.com/
worked for my own scripts.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/romannurik/dashclock/issues/865#issuecomment-203594341

I've come across this issue as the weather extension is also not working for me. Given that this merge is almost a year old, is it broken again? Or is there something else amiss?
Is the official statement still to use a 3rd party extension?

I've been using the app Arcus Weather, which shows up as a Dashclock
extension, and it works well and looks great.
On Apr 12, 2017 5:16 AM, "Michel Albert"<EMAIL_ADDRESS>wrote:

I've come across this issue as the weather extension is also not working
for me. Given that this merge is almost a year old, is it broken again? Or
is there something else amiss?
Is the official statement still to use a 3rd party extension?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/romannurik/dashclock/issues/865#issuecomment-293558291,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAbh5EZVkZcIoUqoDZX2aVZ5it1TLWsiks5rvMCJgaJpZM4H5Jh9
.


Can you compress it into an APK file?

Jednak nieistotne

Download it here https://github.com/EmiyaSyahriel/CrossLauncher/releases

Yes thank you, I have already found. Thank you for the best launcher I have
ever used. PlayStation 3 is my favorite console ever, so I enjoy using the
launcher inspired by it.  From what I saw help with the translation is
needed? I'm not sure, but if it's true - I can help with the Polish
language. I don't write much English, but Polish is another matter! Yes…
pt., 18 gru 2020, 14:14 użytkownik VirtualPedestrian <
<EMAIL_ADDRESS>napisał:

Download it here https://github.com/EmiyaSyahriel/CrossLauncher/releases
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/EmiyaSyahriel/CrossLauncher/issues/3#issuecomment-748077850,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASFNJJONNTWEIF7BGCH2TX3SVNIUVANCNFSM4VBAKUZQ
.

So this issue is done then. And yes, We need translation for this project.
To translate the project, you can fork this repo, open it in Android Studio, open the Localization Editor / String Editor from there, add your language, then start translating. And when done, you can Commit, Push, and merge your repo to this repo.
Or if you cannot use Android Studio, just download this file, make a copy of it, translate it while using the copy as your reference. Then send it here. By the way, Issue page is for issues only, for APK request and other thing like resource submission. You can go to the Discussion page.
And currently I am not very active because I have a project at work. So, There wouldn't be much update unless I have some free time.


[Feature Request] Bring back particle types that have a parameter

The following do not currently work because they require a parameter of some sort:
iconcrack
blockcrack
blockdust
Can we make them work?

Fixed with 1.5.


Editable tags feature

This PR enables editable tags (on click). There's also a new method on the TAG class called addSvgListener which binds listeners to svg actions (ie label-updated) which are called on each svg event.

Should be good now.


Error 400

> POST /gateways/XXXXXXXXXXXXXXX/orders?amount=13&keychain_id=1 HTTP/1.1
Host: gateway.gear.mycelium.com
Accept: */*
X-Nonce: -1487945470
X-Signature: XXXXXXXXXXXXXXXXXXXXXXXXXX
Content-Length: -1
Content-Type: application/x-www-form-urlencoded
Expect: 100-continue

< HTTP/1.1 400 Bad Request
* Server nginx/1.8.0 is not blacklisted
< Server: nginx/1.8.0
< Date: Sun, 27 Nov 2016 19:42:53 GMT
< Content-Type: text/html
< Content-Length: 172
< Connection: close
<
* Closing connection 0
Error:
<title>400 Bad Request</title>

400 Bad Request

nginx/1.8.0

Try to regenerate a new Gateway Secret. I tested their API past few days and when I change Gateway settings my secret becomes invalid sometimes.


Derivative work from record project

I saw your project published on pub.dev.
Regarding the modifications applied to the repository, you are not compliant with the Apache 2.0 license as you are not stating the changes made to the original content.
Regarless the above, this is a waste to not contribute to the record package to make a duplicate of it...

Feel free to pull any changes from the clearly visible and detailed commit history which details the changes that were made. The original project I forked this from had a large disclaimer that they were discontinuing the project and to use flutter_sound instead. The one I forked was broken and in need of repair and hadn't seen development in over a year. This was easier than starting from scratch since I would have basically written the same thing since it's just a loose wrapper around existing APIs.

I'm the maintainer of this project so I know pretty well where my time is spent.
Anyway, I got my answers in between what you said and what you did.


metaphlan: init at 4.1.0

Description of changes
Closes #299219
NOTE: Fails due to a broken dependency on python >= 3.12 (https://github.com/NixOS/nixpkgs/pull/326199)
:warning: Warning to reviewers: The closure size is 51.55 GiB, due to a large database (metaphlan-db, closure size 50.7 GiB) that is downloaded as part of the package.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

7 packages built:

hclust2
hclust2.dist
metaphlan
metaphlan-db
metaphlan.dist
phylophlan
phylophlan.dist

Re-requesting review: @fabaff

@GrahamcOfBorg eval

Bump

I've made a couple modifications to save some disk space, format the packages more correctly, and build faster.

Rebased, since it was getting a lil out of date.

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

4 packages failed to build:

python312Packages.metaphlan
python312Packages.metaphlan.dist
python312Packages.phylophlan
python312Packages.phylophlan.dist

9 packages built:

metaphlan-db
python311Packages.hclust2
python311Packages.hclust2.dist
python311Packages.metaphlan
python311Packages.metaphlan.dist
python311Packages.phylophlan
python311Packages.phylophlan.dist
python312Packages.hclust2
python312Packages.hclust2.dist

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

13 packages built:

metaphlan-db
python311Packages.hclust2
python311Packages.hclust2.dist
python311Packages.metaphlan
python311Packages.metaphlan.dist
python311Packages.phylophlan
python311Packages.phylophlan.dist
python312Packages.hclust2
python312Packages.hclust2.dist
python312Packages.metaphlan
python312Packages.metaphlan.dist
python312Packages.phylophlan
python312Packages.phylophlan.dist


[SPARK-41994] Assign SQLSTATE's (1/2)

What changes were proposed in this pull request?
In this PR we review the first batch of error classes and assign proper SQLSTATE's to them.
To this end we have compiled a grant list of SQLSTATEs used by various vendors and added them to errors/README.md
We also dedicate a subclass range that is currently unused for Spark: "K**"
Why are the changes needed?
SQLSTATE is the API through which JDBC and ODBC based tools and applications catch and process error conditions.
Does this PR introduce any user-facing change?
Yes, for many error classes the SQLSTATEs have been refined (moved from e.g. 42000 to a specific subclass), changed if they were in the wrong class (often between 42 (compiler) and 22 (runtime), and finally added SQLSTATE to many that had none so far.
How was this patch tested?
Run existing pre-checkin workload

Can one of the admins verify this patch?


fix: correct back button behavior on copilot confirmation page

Explanation of Change

Fixed Issues

$ https://github.com/Expensify/App/issues/53007
PROPOSAL: https://github.com/Expensify/App/issues/53007#issuecomment-2500299844
Tests

Open Settings page
Open Security
Press "Add copilot"
Select any user as copilot
Select an access level
Press "Add Copilot"
On Magic Code page, use the device back button to return to previous page
Verify that: user is redirected to copilot confirmation page

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

Open Settings page
Open Security
Press "Add copilot"
Select any user as copilot
Select an access level
Press "Add Copilot"
On Magic Code page, use the device back button to return to previous page
Verify that: user is redirected to copilot confirmation page

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/user-attachments/assets/52f03985-84d7-4795-8fea-c393932f9071

Android: mWeb Chrome
https://github.com/user-attachments/assets/a49d1c0d-4f22-4228-b7ee-45518c0a534e

iOS: Native
https://github.com/user-attachments/assets/6c304709-e386-471f-89b4-2598df93edf7

iOS: mWeb Safari
https://github.com/user-attachments/assets/f8455d32-c981-4d23-ba7e-e08cea3deeb9

MacOS: Chrome / Safari
https://github.com/user-attachments/assets/4a6d4d1c-0ecd-4c00-8d55-86f0038a53cf

MacOS: Desktop
https://github.com/user-attachments/assets/c10c31ff-1daf-4262-af73-a9bffda11d15

@daledah can you fix the conflicts before we move forward with merge?

@daledah bump

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.


Brute Force Development

[ ] Motor control validation
[ ] Drift characterization

[ ] Determine glide rate

[ ] Locomotion validation

exploded, trying again

Redid spacers and attached new props, still investigating failure


Todo: rewrite receiveTokensStore.js in TypeScript

One of the few js files left... goal is to have 100% ts.

Hello I would like to do this.

Hi @callebtc I currently have a PR up that address this. Looking forward to your review and feedback, thanks

It seems the change has already been done in 738de22f3ec16196679aac9bc7a07e4f5be6f829 as part of https://github.com/cashubtc/cashu.me/pull/287
We can close this issue


feat: allow T.UnionOf to work with read only arrays

🎁 Pull Request

[X] Used a clear / meaningful title for this pull request
[X] Tested the changes in your own code (on your projects)
[X] Added / Edited tests to reflect changes (tst folder)
[X] Have read the Contributing part of the Readme
[X] Passed npm test

Fixes

Why have you made changes?

It is common to use as const to declare a tuple like the following:

const Foos = ['a', 'b'] as const;
type Foo = T.UnionOf<typeof Foos> // previously this will be an error

O.UnNest
Some times I want to get all possible types of the values of an object (used as a dict):

type Country = 'US' | 'UK' | 'CN'
type CountryCityMap = { US: ['NY', 'LA'], UK: ['London', 'Nottingham'], CN: ['Beijing', 'Shanghai'] };

// or O.UnNest<CountryCityMap>
// City = "NY" | "LA" | "London" | "Nottingham" | "Beijing" | "Shanghai"
type City = O.UnNest<CountryCityMap, Country>

What changes have you made?

changed this to achieve this
changed that to achieve this
...

What tests have you updated?

tested this in tst/...
tested that in tst/...
...

Is there any breaking changes?

[ ] Yes, I changed the public API & documented it
[ ] Yes, I changed existing tests
[ ] No,  I added to the public API & documented it
[X] No,  I added to the existing tests
[ ] I don't know

Anything else worth mentioning?

Hey @pengx17 thanks for your pull request! I'm not going to accept it, but I'm going to help you out:

To achieve what your type does, use Path instead:

type Country = 'US' | 'UK' | 'CN'
type CountryCityMap = { US: ['NY', 'LA'], UK: ['London', 'Nottingham'], CN: ['Beijing', 'Shanghai'] };

// City = "NY" | "LA" | "London" | "Nottingham" | "Beijing" | "Shanghai"
type City = Path<CountryCityMap, [Country, any]>

And I've just pushed a new version that accepts readonly arrays for all the types, so you don't have to worry about this anymore :)

(cc @tonivj5)

Thanks @pirix-gh. I saw you refactored all tuple types which is a great effort! Your repo on ts really inspires me a lot and thanks for maintaining it :D

You're welcome @pengx17, thanks!


hi there regarding the pathslider.

i have it curved exactly how i want it and its moving freely.
my question is how do i set the position using javascript and how would i use it the same way as i am using this volume control.
<input type="range" id="volume"  width="500" height="20px" min="0" max="100" step="1"oninput="actions(this.id,this.value);" onchange="actions(this.id,this.value);"/>

i would like to use 2 sliders on the same page.
any chance you could give me an example on how to interact with the slider please. BTW i love it, very easy to implement :)
my email address is<EMAIL_ADDRESS>

I'm guessing this issue has been resolved, so I'm going to close it. If you continue to have problems, please feel free to continue the discussion in this thread.


FCA (Independent Publisher) Connector - Added and Updated Actions

Fixed the 'Common Search' action.
Added 'Find Firm Details' and 'Find Product Details' actions.

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)
If this is your first time submitting to GitHub and you need some help, please sign up for this session.

[x] I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
[x] I attest that the connector works and I verified by deploying and testing all the operations.
[x] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
[x] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
[x] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
[x] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

[x] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
[x] Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
[x] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
[x] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

Hello @gulshankhurana,
Thank you for submitting a new PR. However you have merged this PR too, kindly don't merge it until the review completes. Additionally the is still in progress state, please change it.

@vmanoharas , it is ready for review again. Thanks.

[[certify-connector]]

Hello @gulshankhurana,
Your connector artifacts have not been uploaded into our internal tool after multiple attempts, as you have modified the title of the connector. Modifying title is not allowed for Independent Publisher, kindly submit new connector with new version. Apologies for the inconvenience caused.
Thanks for your patience and understanding.

[[certify-connector]]

@vmanoharas , please could you review this. Thanks.

[[certify-connector]]

Hello @gulshankhurana,
Please accept my apologies, I thought I have reviewed and approved this PR already. Unfortunately, old name is also not accepted. Last time we had same issue so we have taken files from here manually and certified.  Please see the validation error below and correct the title.

Hello @gulshankhurana,
Please accept my apologies, I thought I have reviewed and approved this PR already. Unfortunately, old name is also not accepted. Last time we had same issue so we have taken files from here manually and certified. Please see the validation error below and correct the title.

If only I knew what it meant, it's all like a foreign language to me. I don't know where the error is, let alone knowing how to resolve this :(
What would the quickest/easiest way for a non-dev like me to get my request approved? Start afresh with new pull request and fresh submission?

Hello @gulshankhurana,
Please accept my apologies, I thought I have reviewed and approved this PR already. Unfortunately, old name is also not accepted. Last time we had same issue so we have taken files from here manually and certified. Please see the validation error below and correct the title.

If only I knew what it meant, it's all like a foreign language to me. I don't know where the error is, let alone knowing how to resolve this :(
What would the quickest/easiest way for a non-dev like me to get my request approved? Start afresh with new pull request and fresh submission? @vmanoharas

Hello @gulshankhurana,
If you understand the error mentioned in the image below, the title should not be like all uppercase or lower case, it should be as per the example below.
-- AsHashTable

@vmanoharas , thanks for the prompt response. I really appreciate that.
Originally, the title was "FCA" only which I changed to "Financial Conduct Authority" UK but it was agaisnt the system rules to change the name so I changed it back to "FCA" and now you're saying that the system doesn't accept all capital letters but it did originally. Since "FCA" is an abbreviation so I can't/mustn't change it to "Fca".
What do you propose I should do? If possible, I'd rather go for the name "Financial Conduct Authority UK" as this is what the connector is all about.

Hello @gulshankhurana,
Sorry for lot of confusions created, we will go ahead with FCA now, and let's decide next time. As our certification process is going to change soon. I will request our engineers to take the files from here and certify it.

[[certify-connector]]

@vmanoharas, Thanks again for all your help.
Please advise how can I track the usage stats for my connector?

@vmanoharas, Thanks again for all your help. Please advise how can I track the usage stats for my connector?

@gulshankhurana, unfortunately, you cannot track as an Independent Publisher.

Hi @vmanoharas
Any luck progress it to deployment stage?

Hello @gulshankhurana, Yes, your connector was included in last week's deployment cycle and is expected to be completed within the next 2-3 weeks.

Hi @vmanoharas
Any further updates on deployment date?

Hi @vmanoharas
Any further updates on deployment completion date?

Hi @gulshankhurana,
your connector is being deployed, it may approximately complete in another 5 to 6 working days.

@vmanoharas , I've just created a new PR #3547 and wondering if this would delay the deployment of my existing (already approved) #3500 PR.

Hello @gulshankhurana,
Your new changes in this PR https://github.com/microsoft/PowerPlatformConnectors/pull/3547 will be approved and included after your current version of the connector deployed to all regions.

Hello @gulshankhurana,
Your new changes in this PR #3547 will be approved and included after your current version of the connector deployed to all regions.

Thank @vmanoharas. Eagerly waiting for FCA connector update to be deployed.

Hi @vmanoharas, it's been 5 weeks now since you approved the changes. Are there any updates regarding deployment yet? Thanks.

Hi @vmanoharas, it's been 5 weeks now since you approved the changes to the FCA Connector. Are there any updates regarding deployment yet? Thanks.

Hi @gulshankhurana, Apologies for the delay in deploying your connector, now your connector is deployed to last but one region, it will be completed by early next week.
Thank you for your patience and understanding.

Hi @vmanoharas, it's been 5 weeks now since you approved the changes to the FCA Connector. Are there any updates regarding deployment yet? Thanks.

Hi @gulshankhurana, Apologies for the delay in deploying your connector, now your connector is deployed to last but one region, it will be completed by early next week.
Thank you for your patience and understanding.

Hi @vmanoharas
Another week gone, still waiting :(

Hello @gulshankhurana ,
I hope you are doing well.
Congratulations, the deployment of your connector and documentation page was already completed, We have a short survey on the connector certification process that we would like for you to complete. Your feedback is appreciated and will help us improve the program.
Thank you very much for working with us.

Hello @gulshankhurana ,
I hope you are doing well.
Congratulations, the deployment of your connector and documentation page was already completed, We have a short survey on the connector certification process that we would like for you to complete. Your feedback is appreciated and will help us improve the program.
Thank you very much for working with us.


ARN template for os disk encryption.

Is this a request for help?:
Yes!!! Definitely!
Is this an ISSUE or FEATURE REQUEST? (choose one):
Feature Request
What version of acs-engine?:
v. 0.9.3 and v.0.1.0

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes
What happened:
I attempted to use a power-shell script to run a deployment inside another deployment and it failed. I also tried setting up a vault with secrets and modifying the ARN template to enable disk encryption, specifying the vault is and secret... I couldn't get it to work. I reached out the MS tech team and they directed me here...
What you expected to happen:
I expected the disks to encrypt themselves during the creation of the cluster and I expected that the auto scaled nodes would spin up with encrypted disks enabled....
How to reproduce it (as minimally and precisely as possible):

use acs engine to make the ARN template with the template above.
and that is as far as I have gotten... I haven't been able to successfully encrypt the disks on cluster creation...
and the rest is history!

Anything else we need to know:
k8s is not as easy as it looks...! :)

the acs engine template I am using...
ac-eng-k8s.txt

Hi @LaneEnglot, please track #747 which we're currently working through. Sorry we don't have a working solution just yet!


font awesome: Icons from 4.7.0 not appearing.

We updated our font awesome version to 4.7.0 in ee0b16b, but git grep for the icons at the top of http://fontawesome.io/icons/ (i.e. the ones in 4.7.0) doesn't seem to find anything. Not sure if this is a provisioning issue, or something else. The old icon definitions seem to be in static/third/thirdparty-fonts.css.
Once this is done, a small followup is to replace <i>@</i> in static/templates/user_info_popover_content.handlebars with http://fontawesome.io/icon/at/, since the @ doesn't have the right spacing (you can see this in the profile popovers you get by clicking on the avatar of any user.)
Adding @khantaalaman, in case you have any ideas?

I suspect we just need to add something like this:
.icon-vector-trello:before {
  content: "\f181";
}

at the bottom of static/third/thirdparty-fonts.css (we're not using their modern API).

and/or start switching to using their modern API.

I just took a look at the latest font awesome css file from there website and its looks like a whole lot difference in them to me. I am not a css expert but it feels like we might require a whole lot of refactoring to move to font awesome 4.7.0 since the css file looks quite different from what we currently have.
eg.
From 4.7.0
.fa-trello:before {
  content: "\f181";
}

What tim already mentioned above from our version of file.
.icon-vector-trello:before {
  content: "\f181";
}

Also i couldn't find the actual official font awesome site link to font awesome 3.0.2 but the css file in font awesome 3.2.1 is also different. Here is the same icon from 3.2.1
.icon-trello:before {
  content: "\f181";
}

In regard to this difference does Zulip use some customised version of font awesome?

We shouldn't be; I suspect it's just that we haven't been upgrading correctly in the past.
Guide to upgrading from 3 to 4:
https://github.com/FortAwesome/Font-Awesome/wiki/Upgrading-from-3.2.1-to-4
Even if we don't do a migration, I think it is worth making it so that we can at least use the icons in Font Awesome 4; there have been several times when I've felt the best icon for something has been introduced in 4.*.

I have a crazy idea by the way(might not be that crazy).
Since we already have updated most stuff in the commit you mentioned above why don't just miss out the migration of uses of font-awesome 3.0.2 classes on the front end and just edit the thirdparty-fonts.css file to append it with stuff from new font-awesome file. I guess Tim has mentioned this in a way already.
I have tried it and it works for the @ task you mentioned.

I believe this shouldn't create any issues seeing the pattern the file uses (content: "\f049";). Some kind of code to match icons from another file which seems to retain older icon mapping to same code.

Nice! You may as well submit the @ as a quick PR, to solve that problem :).
I could go either way. There are ~90 unique icons in the codebase, so not a small amount of work to migrate. Though possibly we should just upgrade to take advantage of features like fixed-width icons for menus, etc (fa-fw).
https://github.com/jdewit/grunt-html-upgrader has a possibly beta-quality upgrade script.

Here is a quick PR.

I believe the script you mentioned might not be useful directly. Not at least without modifications since the script is written to upgrade font-awesome from 3.2.1 to 4.* standards rather than from 3.0.2 which i believe is the actual version of file we have been using.
Prime difference i believe being in the base class.
3.0.2 uses icon-vector-* and 3.2.1 uses icon-*.
Might be other changes be present but i couldn't find a suitable documentation for such changes upon a google search.

ah, got it.
And cool! From the PR it looks like the hack is essentially to use both Font Awesome 3.0.2 and 4.7.0? If so that seems like the best of both worlds :).
Possibly doing the migration could be a good pycon sprints project (and e.g. include in that changing menu icons to fixed width, maybe checking if there are improved 4.7.0 variants, etc)

yeah the hack ensures Font-awesome 3.0.2 works as it is and enables us to use 4.7.0 as well.

This might be a migration better done in the style of our HTML templates whitespace migration, where we try to avoid merge conflicting with anything while we refactor.

I can pick it up to do that way. Probably even develop some kind of tooling to automate stuff. Better try modifying the script rishi already posted.

Awesome :).

OK I'll merged #4306 and then we can work on migrating and thus being able to get rid of the old font stuff.
Based on $ git grep icon-vector  | grep -v translations | grep -v thirdparty | wc, there's only 325 references, so I think it shouldn't be too painful to migrate this.

#4306 resolves the original issue here; @adnrs96 can you open a new issue for the migration?

Sure. Here is the new issue


Dev Container doesn't support Mac arm64

In the install.sh file, we're downloading ubuntu_x86_64_moon_setup.sh to setup development toolkits. Obviously, it's used on x86_64 OS. If I replace that URL with https://cli.moonbitlang.com/install/unix.sh, the built container complains the following:
------
 > [dev_containers_target_stage 5/5] RUN --mount=type=bind,from=dev_containers_feature_content_source,source=moonbit_0,target=/tmp/build-features-src/moonbit_0     cp -ar /tmp/build-features-src/moonbit_0 /tmp/dev-container-features  && chmod -R 0755 /tmp/dev-container-features/moonbit_0  && cd /tmp/dev-container-features/moonbit_0  && chmod +x ./devcontainer-features-install.sh  && ./devcontainer-features-install.sh  && rm -rf /tmp/dev-container-features/moonbit_0:
0.059 ===========================================================================
0.059 Feature       : moonbit-cli
0.059 Description   :
0.059 Id            : Unknown
0.059 Version       : 0.0.1
[2024-08-21T11:44:13.045Z]
0.059 Documentation :
0.059 Options       :
0.059     VERSION="0.0.1"
0.059 ===========================================================================
0.994 error: Unsupported platform: Linux aarch64
0.998 ERROR: Feature "moonbit-cli" (Unknown) failed to install!

This indicates moonbit-cli doesn't make it on arm64 platform.

I've tried to download the moonbit compiler manually. This failed with an error - Unsupported platform: Linux aarch64. Maybe It doesn't work on Linux aarch64 yet?


User agent fix

What
Fixes an issue where user-agent header was being overwritten with a default value,  making some Completed Checkout events be shown  as client_type = web.
Why
https://trello.com/c/pl9yHIQ0/543-native-clienttype-detection

 Native client_type detection


Error when slices using order by columns opened in dashboardorder_by_cols: '[' is not a valid choice for this field

Please post the backtrace from caravel logs. And close the other duplicated issue you have opened.


Add network Address class

blocked by #1259
Description
Add a network Address class, as proposed in the issue.
Checklist

[x] Self-review changes.
[x] Evaluate impact on the documentation.
[x] Ensure test coverage.
[x] Write new samples.
[x] Add entry to the changelog's unreleased section.

It would be nice to have 100% line coverage or close to that in the test cases.

Im 99% sure that codecov is borked.

It would be nice to have 100% line coverage or close to that in the test cases.

Im 99% sure that codecov is borked. It should be > 90%

You didn't add the test in the CMakeLists.txt, so its not being compiled & run

Thanks @RiscadoA , nice catch.


OC-595 Log information about messages on Kafka topics

Adds KafkaLogger for use with consumer configuration on Kafka topics to
be able to log data and metadata of messages that are posted on a topic.
Adds osgp-adapter-kafka-logging as deployable project in servlet
containers with configuration of consumers for currently known topics
in the GXF code base.
The configurations of the different logging consumers are subject to a
Spring conditional, following a boolean property (for instance
peakshaving.kafka.logging.enabled). Default this enabled property is set
to false, which should prevent warning or error logging if a Kafka
broker is not available for certain topics in a monitored environment.
The consumed messages for the configured topics will be logged to a file
specified in the logback configuration with an appender named MESSAGES.
This appender leaves out most of the default stuff that is normally
added as context with logged data, leaving only the date and time of
logging, and the message that is logged.

SonarQube analysis reported 1 issue
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 MeterReadingDeserializer.java#L23: Define and throw a dedicated exception instead of using a generic one.

SonarQube analysis reported 1 issue
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 MeterReadingDeserializer.java#L23: Define and throw a dedicated exception instead of using a generic one.

SonarQube analysis reported 1 issue
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 MeterReadingDeserializer.java#L23: Define and throw a dedicated exception instead of using a generic one.