HDFS-16791. Add getEnclosingRoot() API to filesystem interface and im…

…plementations (#6198)
The enclosing root path is a common ancestor that should be used for temp and staging dirs as well as within encryption zones and other restricted directories.
Contributed by Tom McCormick

Description of PR
Cherry pick of https://github.com/apache/hadoop/pull/6198#pullrequestreview-1712503495
How was this patch tested?
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

@steveloughran Nearly clean cherry pick. Just a couple of things that exist in trunk but not in 3.3, so all deletes.
Unmerged paths:
  (use "git add <file>..." to mark resolution)
        both modified:   hadoop-hdfs-project/hadoop-hdfs-client/src/main/java/org/apache/hadoop/hdfs/DistributedFileSystem.java
        both modified:   hadoop-hdfs-project/hadoop-hdfs-rbf/src/main/java/org/apache/hadoop/hdfs/server/federation/router/RouterClientProtocol.java

Untracked files:
  (use "git add <file>..." to include in what will be committed)
        hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/placement/

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
5m 10s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+0 :ok:
buf
0m  0s

buf was not available.

+0 :ok:
buf
0m  0s

buf 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 11 new or modified test files.

_ branch-3.3 Compile Tests _

+0 :ok:
mvndep
14m  3s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
22m 46s

branch-3.3 passed

+1 :green_heart:
compile
11m 38s

branch-3.3 passed

+1 :green_heart:
checkstyle
1m 47s

branch-3.3 passed

+1 :green_heart:
mvnsite
3m 59s

branch-3.3 passed

+1 :green_heart:
javadoc
3m 38s

branch-3.3 passed

+1 :green_heart:
spotbugs
6m 33s

branch-3.3 passed

+1 :green_heart:
shadedclient
23m 28s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 25s

Maven dependency ordering for patch

-1 :x:
mvninstall
0m 19s
/patch-mvninstall-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

-1 :x:
compile
3m 13s
/patch-compile-root.txt
root in the patch failed.

-1 :x:
cc
3m 13s
/patch-compile-root.txt
root in the patch failed.

-1 :x:
javac
3m 13s
/patch-compile-root.txt
root in the patch failed.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 32s

the patch passed

-1 :x:
mvnsite
0m 22s
/patch-mvnsite-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

-1 :x:
javadoc
0m 43s
/results-javadoc-javadoc-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-project_hadoop-hdfs-rbf generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

-1 :x:
spotbugs
0m 21s
/patch-spotbugs-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

+1 :green_heart:
shadedclient
23m 47s

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

_ Other Tests _

+1 :green_heart:
unit
15m 23s

hadoop-common in the patch passed.

+1 :green_heart:
unit
1m 53s

hadoop-hdfs-client in the patch passed.

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

-1 :x:
unit
0m 32s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

+1 :green_heart:
asflicense
0m 40s

The patch does not generate ASF License warnings.

336m 37s

Reason
Tests

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

hadoop.hdfs.server.balancer.TestBalancerWithHANameNodes

hadoop.hdfs.server.namenode.ha.TestStandbyCheckpoints

hadoop.hdfs.server.sps.TestExternalStoragePolicySatisfier

hadoop.hdfs.server.namenode.TestAddOverReplicatedStripedBlocks

hadoop.hdfs.server.datanode.fsdataset.impl.TestLazyPersistReplicaRecovery

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets markdownlint cc buflint bufcompat

uname
Linux 064de127f595 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / 82285cee11403d1bcd234b72379b30cc58c1c303

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

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

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

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

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

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

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

This message was automatically generated.

looks like the hadoop-rbf stuff didn't take. just did a local build of branch-3.3 and it is happy, so this probably really is a regression

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 26s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+0 :ok:
buf
0m  0s

buf was not available.

+0 :ok:
buf
0m  0s

buf 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 11 new or modified test files.

_ branch-3.3 Compile Tests _

+0 :ok:
mvndep
14m  0s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
22m 12s

branch-3.3 passed

+1 :green_heart:
compile
11m 45s

branch-3.3 passed

+1 :green_heart:
checkstyle
1m 49s

branch-3.3 passed

+1 :green_heart:
mvnsite
3m 57s

branch-3.3 passed

+1 :green_heart:
javadoc
3m 39s

branch-3.3 passed

+1 :green_heart:
spotbugs
6m 32s

branch-3.3 passed

+1 :green_heart:
shadedclient
23m 29s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 26s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 35s

the patch passed

+1 :green_heart:
compile
11m 10s

the patch passed

+1 :green_heart:
cc
11m 10s

the patch passed

+1 :green_heart:
javac
11m 10s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 52s

the patch passed

+1 :green_heart:
mvnsite
3m 56s

the patch passed

+1 :green_heart:
javadoc
3m 38s

the patch passed

+1 :green_heart:
spotbugs
7m 11s

the patch passed

+1 :green_heart:
shadedclient
23m 38s

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

_ Other Tests _

+1 :green_heart:
unit
15m 54s

hadoop-common in the patch passed.

+1 :green_heart:
unit
2m  7s

hadoop-hdfs-client in the patch passed.

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

+1 :green_heart:
unit
15m 14s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 55s

The patch does not generate ASF License warnings.

359m 19s

Reason
Tests

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

hadoop.hdfs.server.balancer.TestBalancerWithHANameNodes

hadoop.hdfs.server.sps.TestExternalStoragePolicySatisfier

hadoop.hdfs.server.namenode.TestAddOverReplicatedStripedBlocks

hadoop.hdfs.server.datanode.TestDirectoryScanner

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets markdownlint cc buflint bufcompat

uname
Linux be5ac791eb92 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / d74f8cb242150446e609b6e47bb95af213d24ed6

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

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

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

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

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

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 33s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+0 :ok:
buf
0m  0s

buf was not available.

+0 :ok:
buf
0m  0s

buf 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 11 new or modified test files.

_ branch-3.3 Compile Tests _

+0 :ok:
mvndep
13m 51s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
24m 44s

branch-3.3 passed

+1 :green_heart:
compile
11m 48s

branch-3.3 passed

+1 :green_heart:
checkstyle
1m 47s

branch-3.3 passed

+1 :green_heart:
mvnsite
3m 58s

branch-3.3 passed

+1 :green_heart:
javadoc
3m 44s

branch-3.3 passed

+1 :green_heart:
spotbugs
6m 40s

branch-3.3 passed

+1 :green_heart:
shadedclient
23m 18s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 50s

Maven dependency ordering for patch

-1 :x:
mvninstall
0m 30s
/patch-mvninstall-hadoop-hdfs-project_hadoop-hdfs-client.txt
hadoop-hdfs-client in the patch failed.

-1 :x:
mvninstall
0m 30s
/patch-mvninstall-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
mvninstall
0m 19s
/patch-mvninstall-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

-1 :x:
compile
1m 28s
/patch-compile-root.txt
root in the patch failed.

-1 :x:
cc
1m 28s
/patch-compile-root.txt
root in the patch failed.

-1 :x:
javac
1m 28s
/patch-compile-root.txt
root in the patch failed.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 30s

the patch passed

-1 :x:
mvnsite
0m 32s
/patch-mvnsite-hadoop-hdfs-project_hadoop-hdfs-client.txt
hadoop-hdfs-client in the patch failed.

-1 :x:
mvnsite
0m 32s
/patch-mvnsite-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
mvnsite
0m 22s
/patch-mvnsite-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

-1 :x:
javadoc
0m 58s
/results-javadoc-javadoc-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs-project_hadoop-hdfs generated 4 new + 1 unchanged - 0 fixed = 5 total (was 1)

-1 :x:
spotbugs
0m 32s
/patch-spotbugs-hadoop-hdfs-project_hadoop-hdfs-client.txt
hadoop-hdfs-client in the patch failed.

-1 :x:
spotbugs
0m 30s
/patch-spotbugs-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
spotbugs
0m 21s
/patch-spotbugs-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

-1 :x:
shadedclient
7m 19s

patch has errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
15m 25s

hadoop-common in the patch passed.

-1 :x:
unit
0m 33s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs-client.txt
hadoop-hdfs-client in the patch failed.

-1 :x:
unit
0m 31s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
unit
0m 21s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

+1 :green_heart:
asflicense
0m 25s

The patch does not generate ASF License warnings.

131m 51s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets markdownlint cc buflint bufcompat

uname
Linux 729255df80a4 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / 9603a9ec8b3125beda3d4472679e93cfdb97f0c6

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

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

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

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

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

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
4m 25s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+0 :ok:
buf
0m  0s

buf was not available.

+0 :ok:
buf
0m  0s

buf 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 11 new or modified test files.

_ branch-3.3 Compile Tests _

+0 :ok:
mvndep
13m 38s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
23m  4s

branch-3.3 passed

+1 :green_heart:
compile
12m  4s

branch-3.3 passed

+1 :green_heart:
checkstyle
1m 28s

branch-3.3 passed

+1 :green_heart:
mvnsite
3m 11s

branch-3.3 passed

+1 :green_heart:
javadoc
2m 48s

branch-3.3 passed

+1 :green_heart:
spotbugs
5m 38s

branch-3.3 passed

+1 :green_heart:
shadedclient
22m 18s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 22s

Maven dependency ordering for patch

-1 :x:
mvninstall
0m 28s
/patch-mvninstall-hadoop-hdfs-project_hadoop-hdfs-client.txt
hadoop-hdfs-client in the patch failed.

-1 :x:
mvninstall
0m 28s
/patch-mvninstall-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
mvninstall
0m 17s
/patch-mvninstall-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

-1 :x:
compile
1m 34s
/patch-compile-root.txt
root in the patch failed.

-1 :x:
cc
1m 34s
/patch-compile-root.txt
root in the patch failed.

-1 :x:
javac
1m 34s
/patch-compile-root.txt
root in the patch failed.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 16s

the patch passed

-1 :x:
mvnsite
0m 29s
/patch-mvnsite-hadoop-hdfs-project_hadoop-hdfs-client.txt
hadoop-hdfs-client in the patch failed.

-1 :x:
mvnsite
0m 29s
/patch-mvnsite-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
mvnsite
0m 19s
/patch-mvnsite-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

-1 :x:
javadoc
0m 59s
/results-javadoc-javadoc-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs-project_hadoop-hdfs generated 4 new + 1 unchanged - 0 fixed = 5 total (was 1)

-1 :x:
spotbugs
0m 27s
/patch-spotbugs-hadoop-hdfs-project_hadoop-hdfs-client.txt
hadoop-hdfs-client in the patch failed.

-1 :x:
spotbugs
0m 28s
/patch-spotbugs-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
spotbugs
0m 18s
/patch-spotbugs-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

-1 :x:
shadedclient
6m 10s

patch has errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
15m 52s

hadoop-common in the patch passed.

-1 :x:
unit
0m 32s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs-client.txt
hadoop-hdfs-client in the patch failed.

-1 :x:
unit
0m 31s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch failed.

-1 :x:
unit
0m 19s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

+1 :green_heart:
asflicense
0m 22s

The patch does not generate ASF License warnings.

126m 16s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets markdownlint cc buflint bufcompat

uname
Linux 0404f4720b88 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / 9603a9ec8b3125beda3d4472679e93cfdb97f0c6

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

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

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

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

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

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

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

This message was automatically generated.

@steveloughran This kind of seems like yetus issues to me now.
https://github.com/apache/hadoop/pull/6262#issuecomment-1806549653 This check was good after I fixed the path import (you can tell from the revision)
I also locally saw one other failure locally which was the protobuf static import thats not in 3.3.
From a local build i get this (i get this vectorized failure locally even on trunk and 3.3 branch, as do others at LinkedIn)
[INFO] Reactor Summary for Apache Hadoop Main 3.3.9-SNAPSHOT:
[INFO]
[INFO] Apache Hadoop Main ................................. SUCCESS [  2.175 s]
[INFO] Apache Hadoop Build Tools .......................... SUCCESS [  1.702 s]
[INFO] Apache Hadoop Project POM .......................... SUCCESS [  1.783 s]
[INFO] Apache Hadoop Annotations .......................... SUCCESS [  4.200 s]
[INFO] Apache Hadoop Assemblies ........................... SUCCESS [  0.440 s]
[INFO] Apache Hadoop Project Dist POM ..................... SUCCESS [  2.311 s]
[INFO] Apache Hadoop Maven Plugins ........................ SUCCESS [  4.932 s]
[INFO] Apache Hadoop MiniKDC .............................. SUCCESS [  1.763 s]
[INFO] Apache Hadoop Auth ................................. SUCCESS [ 14.290 s]
[INFO] Apache Hadoop Auth Examples ........................ SUCCESS [  3.420 s]
[INFO] Apache Hadoop Common ............................... SUCCESS [ 52.162 s]
[INFO] Apache Hadoop NFS .................................. SUCCESS [  5.820 s]
[INFO] Apache Hadoop KMS .................................. SUCCESS [  4.902 s]
[INFO] Apache Hadoop Registry ............................. SUCCESS [  4.801 s]
[INFO] Apache Hadoop Common Project ....................... SUCCESS [  0.221 s]
[INFO] Apache Hadoop HDFS Client .......................... SUCCESS [ 27.815 s]
[INFO] Apache Hadoop HDFS ................................. SUCCESS [01:03 min]
[INFO] Apache Hadoop HDFS Native Client ................... SUCCESS [  6.074 s]
[INFO] Apache Hadoop HttpFS ............................... SUCCESS [  7.388 s]
[INFO] Apache Hadoop HDFS-NFS ............................. SUCCESS [  8.744 s]
[INFO] Apache Hadoop HDFS-RBF ............................. SUCCESS [ 16.316 s]
[INFO] Apache Hadoop HDFS Project ......................... SUCCESS [  0.110 s]
[INFO] Apache Hadoop YARN ................................. SUCCESS [  0.115 s]
[INFO] Apache Hadoop YARN API ............................. SUCCESS [ 16.592 s]
[INFO] Apache Hadoop YARN Common .......................... SUCCESS [ 19.048 s]
[INFO] Apache Hadoop YARN Server .......................... SUCCESS [  0.151 s]
[INFO] Apache Hadoop YARN Server Common ................... SUCCESS [ 18.680 s]
[INFO] Apache Hadoop YARN NodeManager ..................... SUCCESS [ 16.008 s]
[INFO] Apache Hadoop YARN Web Proxy ....................... SUCCESS [  5.339 s]
[INFO] Apache Hadoop YARN ApplicationHistoryService ....... SUCCESS [  6.741 s]
[INFO] Apache Hadoop YARN Timeline Service ................ SUCCESS [  5.562 s]
[INFO] Apache Hadoop YARN ResourceManager ................. SUCCESS [ 28.425 s]
[INFO] Apache Hadoop YARN Server Tests .................... SUCCESS [ 12.229 s]
[INFO] Apache Hadoop YARN Client .......................... SUCCESS [ 11.407 s]
[INFO] Apache Hadoop YARN SharedCacheManager .............. SUCCESS [  6.134 s]
[INFO] Apache Hadoop YARN Timeline Plugin Storage ......... SUCCESS [  6.123 s]
[INFO] Apache Hadoop YARN TimelineService HBase Backend ... SUCCESS [  0.100 s]
[INFO] Apache Hadoop YARN TimelineService HBase Common .... SUCCESS [  6.191 s]
[INFO] Apache Hadoop YARN TimelineService HBase Client .... SUCCESS [  8.402 s]
[INFO] Apache Hadoop YARN TimelineService HBase Servers ... SUCCESS [  0.223 s]
[INFO] Apache Hadoop YARN TimelineService HBase Server 1.2  SUCCESS [  8.135 s]
[INFO] Apache Hadoop YARN TimelineService HBase tests ..... SUCCESS [  6.883 s]
[INFO] Apache Hadoop YARN Router .......................... SUCCESS [  6.092 s]
[INFO] Apache Hadoop YARN TimelineService DocumentStore ... SUCCESS [  6.275 s]
[INFO] Apache Hadoop YARN Applications .................... SUCCESS [  0.202 s]
[INFO] Apache Hadoop YARN DistributedShell ................ SUCCESS [  6.363 s]
[INFO] Apache Hadoop YARN Unmanaged Am Launcher ........... SUCCESS [  4.921 s]
[INFO] Apache Hadoop MapReduce Client ..................... SUCCESS [  3.996 s]
[INFO] Apache Hadoop MapReduce Core ....................... SUCCESS [ 12.177 s]
[INFO] Apache Hadoop MapReduce Common ..................... SUCCESS [  8.662 s]
[INFO] Apache Hadoop MapReduce Shuffle .................... SUCCESS [ 16.345 s]
[INFO] Apache Hadoop MapReduce App ........................ SUCCESS [ 35.711 s]
[INFO] Apache Hadoop MapReduce HistoryServer .............. SUCCESS [  7.221 s]
[INFO] Apache Hadoop MapReduce JobClient .................. SUCCESS [ 16.106 s]
[INFO] Apache Hadoop Mini-Cluster ......................... SUCCESS [  6.607 s]
[INFO] Apache Hadoop YARN Services ........................ SUCCESS [  0.121 s]
[INFO] Apache Hadoop YARN Services Core ................... SUCCESS [  9.997 s]
[INFO] Apache Hadoop YARN Services API .................... SUCCESS [ 11.396 s]
[INFO] Apache Hadoop YARN Application Catalog ............. SUCCESS [  0.164 s]
[INFO] Apache Hadoop YARN Application Catalog Webapp ...... SUCCESS [ 30.373 s]
[INFO] Apache Hadoop YARN Application Catalog Docker Image  SUCCESS [  1.290 s]
[INFO] Apache Hadoop YARN Application MaWo ................ SUCCESS [  0.109 s]
[INFO] Apache Hadoop YARN Application MaWo Core ........... SUCCESS [  4.645 s]
[INFO] Apache Hadoop YARN Site ............................ SUCCESS [  0.161 s]
[INFO] Apache Hadoop YARN Registry ........................ SUCCESS [  3.270 s]
[INFO] Apache Hadoop YARN UI .............................. SUCCESS [  0.213 s]
[INFO] Apache Hadoop YARN CSI ............................. SUCCESS [ 18.946 s]
[INFO] Apache Hadoop YARN Project ......................... SUCCESS [ 40.277 s]
[INFO] Apache Hadoop MapReduce HistoryServer Plugins ...... SUCCESS [  4.629 s]
[INFO] Apache Hadoop MapReduce NativeTask ................. SUCCESS [  6.116 s]
[INFO] Apache Hadoop MapReduce Uploader ................... SUCCESS [  4.928 s]
[INFO] Apache Hadoop MapReduce Examples ................... SUCCESS [  7.062 s]
[INFO] Apache Hadoop MapReduce ............................ SUCCESS [  9.783 s]
[INFO] Apache Hadoop MapReduce Streaming .................. SUCCESS [  7.484 s]
[INFO] Apache Hadoop Distributed Copy ..................... SUCCESS [  7.579 s]
[INFO] Apache Hadoop Client Aggregator .................... SUCCESS [  6.449 s]
[INFO] Apache Hadoop Dynamometer Workload Simulator ....... SUCCESS [  5.438 s]
[INFO] Apache Hadoop Dynamometer Cluster Simulator ........ SUCCESS [  7.000 s]
[INFO] Apache Hadoop Dynamometer Block Listing Generator .. SUCCESS [  5.220 s]
[INFO] Apache Hadoop Dynamometer Dist ..................... SUCCESS [ 14.487 s]
[INFO] Apache Hadoop Dynamometer .......................... SUCCESS [  0.112 s]
[INFO] Apache Hadoop Archives ............................. SUCCESS [  5.620 s]
[INFO] Apache Hadoop Archive Logs ......................... SUCCESS [  5.841 s]
[INFO] Apache Hadoop Rumen ................................ SUCCESS [  6.825 s]
[INFO] Apache Hadoop Gridmix .............................. SUCCESS [ 24.614 s]
[INFO] Apache Hadoop Data Join ............................ SUCCESS [ 15.760 s]
[INFO] Apache Hadoop Extras ............................... SUCCESS [  6.101 s]
[INFO] Apache Hadoop Pipes ................................ SUCCESS [  0.132 s]
[INFO] Apache Hadoop Amazon Web Services support .......... SUCCESS [ 17.450 s]
[INFO] Apache Hadoop Kafka Library support ................ SUCCESS [  3.482 s]
[INFO] Apache Hadoop Azure support ........................ SUCCESS [ 11.015 s]
[INFO] Apache Hadoop Aliyun OSS support ................... SUCCESS [  4.691 s]
[INFO] Apache Hadoop Scheduler Load Simulator ............. SUCCESS [  6.107 s]
[INFO] Apache Hadoop Resource Estimator Service ........... SUCCESS [  4.900 s]
[INFO] Apache Hadoop Azure Data Lake support .............. SUCCESS [  4.188 s]
[INFO] Apache Hadoop Image Generation Tool ................ SUCCESS [  6.270 s]
[INFO] Apache Hadoop Tools Dist ........................... SUCCESS [ 34.632 s]
[INFO] Apache Hadoop OpenStack support .................... SUCCESS [  3.371 s]
[INFO] Apache Hadoop Common Benchmark ..................... FAILURE [ 19.398 s]
[INFO] Apache Hadoop Tools ................................ SKIPPED
[INFO] Apache Hadoop Client API ........................... SKIPPED
[INFO] Apache Hadoop Client Runtime ....................... SKIPPED
[INFO] Apache Hadoop Client Packaging Invariants .......... SKIPPED
[INFO] Apache Hadoop Client Test Minicluster .............. SKIPPED
[INFO] Apache Hadoop Client Packaging Invariants for Test . SKIPPED
[INFO] Apache Hadoop Client Packaging Integration Tests ... SKIPPED
[INFO] Apache Hadoop Distribution ......................... SKIPPED
[INFO] Apache Hadoop Client Modules ....................... SKIPPED
[INFO] Apache Hadoop Tencent COS Support .................. SKIPPED
[INFO] Apache Hadoop Cloud Storage ........................ SKIPPED
[INFO] Apache Hadoop Cloud Storage Project ................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  15:36 min
[INFO] Finished at: 2023-11-18T11:43:02-08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.4:single (make-assembly) on project hadoop-benchmark: Failed to create assembly: Error creating assembly archive uber: Problem creating jar: jar:file:/Users/tmccormi/projects/hadoop/hadoop-tools/hadoop-benchmark/target/hadoop-benchmark-3.3.9-SNAPSHOT.jar!/org/apache/hadoop/benchmark/generated/VectoredReadBenchmark_jmhType_B1.class -> [Help 1]
[ERROR]

Im gonna try reverting the last commit (although it seems needed) to see if yetus likes it more

After the revert I get building locally
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project hadoop-hdfs-client: Compilation failure
[ERROR] /Users/tmccormi/projects/hadoop/hadoop-hdfs-project/hadoop-hdfs-client/src/main/java/org/apache/hadoop/hdfs/protocolPB/ClientNamenodeProtocolTranslatorPB.java:[2098,13] cannot find symbol
[ERROR]   symbol:   method getRemoteException(org.apache.hadoop.thirdparty.protobuf.ServiceException)
[ERROR]   location: class org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 20s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
markdownlint
0m  1s

markdownlint was not available.

+0 :ok:
buf
0m  1s

buf was not available.

+0 :ok:
buf
0m  1s

buf 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 11 new or modified test files.

_ branch-3.3 Compile Tests _

+0 :ok:
mvndep
13m 39s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
22m 42s

branch-3.3 passed

+1 :green_heart:
compile
11m  3s

branch-3.3 passed

+1 :green_heart:
checkstyle
1m 31s

branch-3.3 passed

+1 :green_heart:
mvnsite
3m 11s

branch-3.3 passed

+1 :green_heart:
javadoc
2m 56s

branch-3.3 passed

+1 :green_heart:
spotbugs
5m 51s

branch-3.3 passed

+1 :green_heart:
shadedclient
21m  9s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 21s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 23s

the patch passed

+1 :green_heart:
compile
10m 42s

the patch passed

+1 :green_heart:
cc
10m 42s

the patch passed

+1 :green_heart:
javac
10m 42s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 25s

the patch passed

+1 :green_heart:
mvnsite
3m 11s

the patch passed

+1 :green_heart:
javadoc
2m 52s

the patch passed

+1 :green_heart:
spotbugs
6m 11s

the patch passed

+1 :green_heart:
shadedclient
21m 12s

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

_ Other Tests _

+1 :green_heart:
unit
15m 42s

hadoop-common in the patch passed.

+1 :green_heart:
unit
1m 55s

hadoop-hdfs-client in the patch passed.

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

+1 :green_heart:
unit
14m 43s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 42s

The patch does not generate ASF License warnings.

335m 54s

Reason
Tests

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

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets markdownlint cc buflint bufcompat

uname
Linux c32133654be4 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / 6a7e834f590cb98332576c8815ba85dc57ba5f57

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09

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

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6262/5/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

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

This message was automatically generated.

@goiri Thoughts? Does this backport look ok. The failure doesn't seem related to my backport right?

@goiri Thoughts? Does this backport look ok. The failure doesn't seem related to my backport right?

LGTM.
@steveloughran do you mind taking a look?

I'm going to say unrelated. HDFS-16740/#4835 addresses flakiness in trunk, but it's not been backported. as usual: volunteers welcome.

merged. If you are on common-dev you can see we've started a discussion about pushing out a branch-3.3 release...


List is now being rehydrated as Map

I upgraded react-native from 0.43 to 0.44 and redux-persist-immutable from 4.1.0 to 4.3.0 and now a List on my reducer (e.g. List(['a', 'b']) is being rehydrated as Map({ 0: 'a', 1: 'b' }).
Reproduction (reducer example)
return Map({
  test1: List(['a', 'b', Math.random()]),
  test2: Set(['a', 'b', Math.random()]),
})

Before rehydration

After rehydration

I don't know what was happening... Reinstalled npm packages and seems fine now.

Yeah this is really happening. @rt2zz which package could be causing this?

Duplicated of https://github.com/glenjamin/transit-immutable-js/issues/36, workaround applied successfully.


Rainbow Triangle App using OpenGL

Replaced by https://github.com/UCSB-CS56-Projects/cs56-android-getting-started/pull/18 which pulls into a separate shane branch


Handle network timeouts

bikeshare file is incomplete due to network timeouts (max attempts) resulting from requesting stations from the "bicipalma" network.
{'id': 3, 'name': 'bicipalma', 'radius': 20000}
Traceback (most recent call last):
  File "extract_bikeshare_data.py", line 74, in <module>
    response.update()
  File "/usr/local/lib/python2.7/site-packages/pybikes/bicipalma.py", line 37, in update
    scraper.request(COOKIE_URL)
  File "/usr/local/lib/python2.7/site-packages/pybikes/utils.py", line 80, in request
    verify = False
  File "/usr/local/lib/python2.7/site-packages/requests/sessions.py", line 357, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python2.7/site-packages/requests/sessions.py", line 460, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python2.7/site-packages/requests/adapters.py", line 354, in send
    raise ConnectionError(e)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='<IP_ADDRESS>', port=8080): Max retries exceeded with url: /eTraffic3/Control?act=mp (Caused by <class 'socket.error'>: [Errno 60] Operation timed out)

{'id': 120, 'name': 'bizi', 'radius': 20000}
Traceback (most recent call last):
  File "extract_bikeshare_data.py", line 85, in <module>
    response.update() # makes an api call for the stations...
  File "/usr/local/lib/python2.7/site-packages/pybikes/smartbike.py", line 49, in update
    raw_req = scraper.request(self.feed_url)
  File "/usr/local/lib/python2.7/site-packages/pybikes/utils.py", line 80, in request
    verify = False
  File "/usr/local/lib/python2.7/site-packages/requests/sessions.py", line 357, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python2.7/site-packages/requests/sessions.py", line 460, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python2.7/site-packages/requests/adapters.py", line 354, in send
    raise ConnectionError(e)
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='www.bizizaragoza.com', port=443): Max retries exceeded with url: /es/formmap/getJsonObject (Caused by <class 'socket.gaierror'>: [Errno 8] nodename nor servname provided, or not known)

just skipping over these errors with except: continue statements for now...


STORM-1062. Establish the basic structure of the code generator.

This PR establishes the basic structure of the code generator to provide the essential build blocks for the actual implementation of the code generator.

@haohui I am +1 on this but looks like build is broken doesn't look this patch caused it though.


Not creating layouts for erb other than layouts directory

I am trying to create new layout of an erb file which is not inside layouts folder but seems it's not creating a valid layout.

The #layouts method is expected to return a collection of layouts (e.g. an Array), rather than a single layout. This is why you get the undefined method 'each' error. Let #layouts return an array of layouts and this error will go away.


Atom.Object.defineProperty.get is deprecated.

atom.workspaceView is no longer available.
In most cases you will not need the view. See the Workspace docs for
alternatives: https://atom.io/docs/api/latest/Workspace.
If you do need the view, please use atom.views.getView(atom.workspace),
which returns an HTMLElement.
Atom.Object.defineProperty.get (/usr/share/atom/resources/app/src/atom.js:54:11)
Minimap.activate (/home/fminne/.atom/packages/minimap/lib/minimap.coffee:98:11)

Please update to the latest version (4.x), we're no longer using workspaceView since at least 2 minor versions.

OK, thank you. Atom seems to have updated the package but, somehow, the issue was still reported after the update. It works fine today.
Sorry to have bothered you with a false issue.

No problem :)


Don't crash on first EAN without installations

This is a continuation of #24130. It turns out you can't reopen a pull request if you force-push to the branch after closing one.
Description:
It seems that some users have multiple "EANs" on their Essent account, possibly without any installations attached to them. This causes an AttributeError. This patch makes it so that it loops over every single EAN, ignoring those that failed.
I honestly do not know of all the possible effects this may cause (because this whole component is reverse engineering), but I can confirm that it doesn't cause any regressions for my setup.
Related issue (if applicable): (hopefully) fixes #24016. I sadly do not have enough information to make completely sure this will actually make meter info show up for these users but I am hopeful it may help and feel it is more likely to improve the situation than make it worse.
Checklist:

[X] The code change is tested and works locally.
[X] Local tests pass with tox. Your PR cannot be merged unless tests pass
[X] There is no commented out code in this PR.
[X] I have followed the development checklist

If the code communicates with devices, web services, or third-party tools:

[X] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[X] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[X] Untested files have been added to .coveragerc.

Let me rephrase the question: should we skip these meters in setup_platform() ? (@amelchio)

Yup, and done now


Stabilize and release

I think we should stabilize the repo and make a release, so that we put a stamp on what is ready. During the process, we will create a tag and this will be handy. If this repo ever needs to evolve in different ways, it is convenient to choose from these tags.

I think we are good to go?

I guess so. We can deal with other changes (such as some syntactic redundancy of let binding) later.

I've done the release but the release tab is not showing on the right.

found it. github is really counterintuitive on this.


Registration

@JuliaRegistrator register
Initial version

Registration pull request created: JuliaRegistries/General/44747
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 7325161b6b926f06cf0f705cc34aaf36d0ab8dbe
git push origin v0.1.0

@JuliaRegistrator register

add explicit verbosity arg

Registration pull request created: JuliaRegistries/General/44935
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.1 -m "<description of version>" a977c806d909c3a47d99f6186b15aa65fe4c0967
git push origin v0.1.1

@JuliaRegistrator register

add metadata test

Error while trying to register: "Tag with name v0.1.1 already exists and points to a different commit"

@JuliaRegistrator register

add metadata test

Registration pull request created: JuliaRegistries/General/45213
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.2 -m "<description of version>" de389ad86cd6829deb1407871bacf57617e556ce
git push origin v0.1.2

@JuliaRegistrator register

allow new MLJBase version

Registration pull request created: JuliaRegistries/General/53685
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.4 -m "<description of version>" b9290d42313440aef7f5db2dfadc79ee1bdaabc2
git push origin v0.1.4

@JuliaRegistrator register
Release notes:

Drop Julia 1.5 support and update OutlierDetection version

Registration pull request created: JuliaRegistries/General/57435
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.0 -m "<description of version>" 826cb2033ebdd4250768ec0f0c9f339539692afa
git push origin v0.2.0

@JuliaRegistrator register

drop support for non-categorical arrays as labels

Registration pull request created: JuliaRegistries/General/66469
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.1 -m "<description of version>" 2b541a61f549329b8383ff56ac960aaa82f04068
git push origin v0.2.1

@JuliaRegistrator register
Release notes:
Upgrade to new OutlierDetectionInterface

Registration pull request created: JuliaRegistries/General/97775
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.0 -m "<description of version>" 489b853e3cf82b2c5ff212f3a736109e7ad6f93a
git push origin v0.3.0

@JuliaRegistrator register
Release notes:
Upgrade to new OutlierDetectionInterface

Registration pull request updated: JuliaRegistries/General/97775
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.0 -m "<description of version>" d19abb6bc8ff670bfd85c043f0f252c45c992cfb
git push origin v0.3.0


Add batch script for LV

@EiffL could you please have a look at azure_scripts/lotka_volterra_francois.py
I converted your notebook into a script but it gives me NaNs and I have troubles figuring it out.
Maybe a different pair of eyes could spot something.

Thanks @aboucaud looks great to me!

I made some tests to find the best architecture

this seems to be the best architecture (the yellow dot):
bijector_layers = [128] * 2

bijector = partial(
  AffineSigmoidCoupling,
  layers=bijector_layers,
  n_components=32,
  activation=jnp.sin
)

NF = partial(
  ConditionalRealNVP,
  n_layers=3,
  bijector_fn=bijector
)

class SmoothNPE(hk.Module):
    def __call__(self, y):
        net = lotka_volterra_y_bijector(y)
        net = jnp.sin(hk.Linear(256, name='comp1')(net))
        net = jnp.sin(hk.Linear(256, name='comp2')(net))
        net = jnp.sin(hk.Linear(256, name='comp3')(net))
        net = jnp.sin(hk.Linear(256, name='comp4')(net))
        net = jnp.sin(hk.Linear(256, name='comp5')(net))
        net = hk.Linear(8, name='comp6')(net)
        nvp = NF(args.dimension)(net)
        return tfd.TransformedDistribution(nvp,
                                           tfb.Chain([tfb.Invert(lotka_volterra_theta_bijector),
                                                      tfb.Scale(10.),
                                                      tfb.Shift(-0.5)]))

so the results I got with the previous architecture were not good, don't really have time to understand why ^^ so I just switched to the architecture with vmim compressor and got theses results:

results:

Any idea why the absolute values of the NLP are so different ?

between simulations and simulations + score ?

Between old and new results

the old one starts at 100 and the new one at 20

I mean merge ^^ it's not good to let PRs hang around for too long.

yes just need to make some updates


Basic PoC StorageConnector for UbuntuOne

See

implement OAuth token request and token authorization for UbuntuOne ... [8c67e22fa4af2f00a588c6c022fb7ae0bb6a26bd]
It's now possible to send a file to Ubuntu One [8cd40b9578e3f2f0603ad9f517efccd29e513ee5]
implement the volume concept into the ubuntuone connector ... [8be739b1d1123845b8dce5a4e130c3270e432d1f]
implement the file deletion for UbuntuOne and specify that ... [30412797d5088a4fbaf61c6f7909d6dd80fb8754]


Feature - email notifications for infra failures

To catch future cases like https://github.com/ossf/scorecard/issues/310

Looks like this is a dupe of https://github.com/ossf/scorecard/issues/247


Won't launch on Ubuntu 20.04 daily iso

It built successfully (both with cargo build --release and plain cargo build). When I try to launch it, I see a window briefly open, immediately close, and then my terminal says
thread 'main' panicked at 'Failed to create renderer: VkError(ERROR_INITIALIZATION_FAILED)', src/window.rs:144:32

When run with RUST_BACKTRACE=1
thread 'main' panicked at 'Failed to create renderer: VkError(ERROR_INITIALIZATION_FAILED)', src/window.rs:144:32
stack backtrace:
   0: backtrace::backtrace::libunwind::trace
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88
   1: backtrace::backtrace::trace_unsynchronized
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66
   2: std::sys_common::backtrace::_print_fmt
             at src/libstd/sys_common/backtrace.rs:77
   3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
             at src/libstd/sys_common/backtrace.rs:59
   4: core::fmt::write
             at src/libcore/fmt/mod.rs:1052
   5: std::io::Write::write_fmt
             at src/libstd/io/mod.rs:1426
   6: std::sys_common::backtrace::_print
             at src/libstd/sys_common/backtrace.rs:62
   7: std::sys_common::backtrace::print
             at src/libstd/sys_common/backtrace.rs:49
   8: std::panicking::default_hook::{{closure}}
             at src/libstd/panicking.rs:204
   9: std::panicking::default_hook
             at src/libstd/panicking.rs:224
  10: std::panicking::rust_panic_with_hook
             at src/libstd/panicking.rs:472
  11: rust_begin_unwind
             at src/libstd/panicking.rs:380
  12: core::panicking::panic_fmt
             at src/libcore/panicking.rs:85
  13: core::option::expect_none_failed
             at src/libcore/option.rs:1199
  14: core::result::Result<T,E>::expect
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447/src/libcore/result.rs:991
  15: neovide::window::WindowWrapper::new
             at src/window.rs:144
  16: neovide::window::ui_loop
             at src/window.rs:375
  17: neovide::main
             at src/main.rs:40
  18: std::rt::lang_start::{{closure}}
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447/src/libstd/rt.rs:67
  19: std::rt::lang_start_internal::{{closure}}
             at src/libstd/rt.rs:52
  20: std::panicking::try::do_call
             at src/libstd/panicking.rs:305
  21: __rust_maybe_catch_panic
             at src/libpanic_unwind/lib.rs:86
  22: std::panicking::try
             at src/libstd/panicking.rs:281
  23: std::panic::catch_unwind
             at src/libstd/panic.rs:394
  24: std::rt::lang_start_internal
             at src/libstd/rt.rs:51
  25: std::rt::lang_start
             at /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447/src/libstd/rt.rs:67
  26: main
  27: __libc_start_main
  28: _start
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

This looks really cool and I'd like to try it out. Let me know if you need any more info or have any potential fixes for me to attempt.
EDIT: Forgot to mention that I get this error whether I run with cargo run or cargo run --release

In Hindsight... it's entirely possible the machine I tried building this on doesn't support Vulkan. I tried it on an old Thinkpad, I will try on a newer desktop I have and report back.

This is likely the issue

@leggettc18 did you get a chance to try it on your desktop?

Sorry. I did and it would launch with a bunch of FontConfig errors. It would then appear to work fine except for some weird rendering issues, like the text seemed to kind of warp when the cursor was around ligatures (I was using the Iosevka font) and parenthesis. It would end up where for instance the cursor would show the character underneath its position in the file, but the actual text was rendered such that the same text was also to the left of the cursor. So basically just really weird rendering errors. I didnt think to take screenshots or anything at the time, ended up using a different editor for the time being. I'll take a stab at recompiling it and seeing if I can recreate it and take some screenshots tonight.

Compiling from scratch seems like a good strategy. What you describe seems like metric problems we've seen in the past.

Well that's weird, I tried to re-clone and build and now its not drawing any windows. It appears to launch and doesn't crash, and I see an entry in my dock (no icon, but that's normal I'm pretty sure), but no window appears on my screen, and no errors get logged in my console. The window preview looks like this:

Is that something you've seen before. It doesn't appear to be a fluke, as deleting and re-building has the same result. Also it seems to happen both with release and debug builds.

I've never seen this happen before :l If you build some 10 commits back or so does the same issue occur? We just merged a pr which might effect things, though I doubt it

Fresh installed Ubuntu 20.04 and I think I'm getting a similar issue with this. There's no mention of the font config errors in #228
Here's the log file from running neovide --log
INFO [neovide::bridge] Close watcher started
INFO [neovide::bridge] Neovim process attached
INFO [neovide::bridge] UiCommand processor started
TRACE [neovide::bridge::handler] Neovim notification: "redraw"
TRACE [neovide::editor::grid] Editor resized
TRACE [neovide::editor::grid] Editor cleared
TRACE [neovide::editor::grid] Editor cleared
TRACE [neovide::editor] Option set ArabicShape(true)
TRACE [neovide::editor] Option set AmbiWidth("single")
TRACE [neovide::editor] Option set Emoji(true)
TRACE [neovide::editor] Option set GuiFont("")
TRACE [neovide::editor] Option set GuiFontSet("")
TRACE [neovide::editor] Option set GuiFontWide("")
TRACE [neovide::editor] Option set LineSpace(0)
TRACE [neovide::editor] Option set Pumblend(0)
TRACE [neovide::editor] Option set ShowTabLine(1)
TRACE [neovide::editor] Option set TermGuiColors(false)
TRACE [neovide::editor] Option set Unknown("ext_linegrid", Boolean(true))
TRACE [neovide::editor] Option set Unknown("ext_multigrid", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_hlstate", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_termcolors", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_cmdline", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_popupmenu", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_tabline", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_wildmenu", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_messages", Boolean(false))
TRACE [neovide::editor::grid] Editor resized
TRACE [neovide::editor::grid] Editor cleared
TRACE [neovide::editor::grid] Editor cleared
TRACE [neovide::editor] Image flushed
TRACE [neovide::redraw_scheduler] Next frame queued
WARN [neovide::settings] Initial value load failed for transparency: Error processing request: 1 - 'Key not found: neovide_transparency')
WARN [neovide::settings] Initial value load failed for cursor_vfx_particle_density: Error processing request: 1 - 'Key not found: neovide_cursor_vfx_particle_density')
WARN [neovide::settings] Initial value load failed for cursor_vfx_particle_speed: Error processing request: 1 - 'Key not found: neovide_cursor_vfx_particle_speed')
WARN [neovide::settings] Initial value load failed for cursor_vfx_mode: Error processing request: 1 - 'Key not found: neovide_cursor_vfx_mode')
WARN [neovide::settings] Initial value load failed for cursor_trail_size: Error processing request: 1 - 'Key not found: neovide_cursor_trail_size')
WARN [neovide::settings] Initial value load failed for cursor_vfx_particle_phase: Error processing request: 1 - 'Key not found: neovide_cursor_vfx_particle_phase')
WARN [neovide::settings] Initial value load failed for cursor_vfx_particle_curl: Error processing request: 1 - 'Key not found: neovide_cursor_vfx_particle_curl')
WARN [neovide::settings] Initial value load failed for cursor_animation_length: Error processing request: 1 - 'Key not found: neovide_cursor_animation_length')
WARN [neovide::settings] Initial value load failed for cursor_vfx_particle_lifetime: Error processing request: 1 - 'Key not found: neovide_cursor_vfx_particle_lifetime')
WARN [neovide::settings] Initial value load failed for no_idle: Error processing request: 1 - 'Key not found: neovide_no_idle')
WARN [neovide::settings] Initial value load failed for cursor_antialiasing: Error processing request: 1 - 'Key not found: neovide_cursor_antialiasing')
WARN [neovide::settings] Initial value load failed for refresh_rate: Error processing request: 1 - 'Key not found: neovide_refresh_rate')
WARN [neovide::settings] Initial value load failed for extra_buffer_frames: Error processing request: 1 - 'Key not found: neovide_extra_buffer_frames')
WARN [neovide::settings] Initial value load failed for keyboard_layout: Error processing request: 1 - 'Key not found: neovide_keyboard_layout')
WARN [neovide::settings] Initial value load failed for cursor_animate_in_insert_mode: Error processing request: 1 - 'Key not found: neovide_cursor_animate_in_insert_mode')
WARN [neovide::settings] Initial value load failed for fullscreen: Error processing request: 1 - 'Key not found: neovide_fullscreen')
WARN [neovide::settings] Initial value load failed for cursor_vfx_opacity: Error processing request: 1 - 'Key not found: neovide_cursor_vfx_opacity')
INFO [neovide::window] window created
INFO [neovide::window] renderer created
INFO [neovide::window] Starting window event loop
TRACE [neovide::redraw_scheduler] Next frame queued
TRACE [neovide::redraw_scheduler] Next frame queued
TRACE [neovide::redraw_scheduler] Next frame queued
TRACE [neovide::bridge] UiCommand queued: FocusGained
TRACE [neovide::redraw_scheduler] Next frame queued
TRACE [neovide::redraw_scheduler] Next frame queued
TRACE [neovide::bridge] Executing UiCommand: FocusGained
TRACE [neovide::bridge] UiCommand queued: Resize { width: 0, height: 0 }
DEBUG [neovide::window] Render Triggered
TRACE [neovide::bridge] Executing UiCommand: Resize { width: 0, height: 0 }
TRACE [neovide::renderer] Rendering
TRACE [neovide::editor] Draw commands sent
TRACE [neovide::bridge::handler] Neovim notification: "redraw"
TRACE [neovide::editor] Option set Unknown("ext_cmdline", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_popupmenu", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_tabline", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_wildmenu", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_messages", Boolean(false))
TRACE [neovide::editor::grid] Editor resized
TRACE [neovide::editor::grid] Editor cleared
TRACE [neovide::editor::grid] Editor cleared
TRACE [neovide::editor] Image flushed
TRACE [neovide::redraw_scheduler] Next frame queued
TRACE [neovide::bridge::handler] Neovim notification: "redraw"
TRACE [neovide::editor] Image flushed
TRACE [neovide::redraw_scheduler] Next frame queued
TRACE [neovide::redraw_scheduler] Next frame queued
DEBUG [neovide::window] Render Triggered
TRACE [neovide::renderer] Rendering
TRACE [neovide::editor] Draw commands sent
TRACE [neovide::redraw_scheduler] Next frame queued
DEBUG [neovide::window] Render Triggered
TRACE [neovide::renderer] Rendering
TRACE [neovide::editor] Draw commands sent
TRACE [neovide::redraw_scheduler] Next frame queued
DEBUG [neovide::window] Render Triggered
TRACE [neovide::renderer] Rendering
TRACE [neovide::editor] Draw commands sent
TRACE [neovide::redraw_scheduler] Next frame queued
DEBUG [neovide::window] Render Triggered
TRACE [neovide::renderer] Rendering
TRACE [neovide::editor] Draw commands sent
TRACE [neovide::redraw_scheduler] Next frame queued
DEBUG [neovide::window] Render Triggered
TRACE [neovide::renderer] Rendering
TRACE [neovide::editor] Draw commands sent
TRACE [neovide::redraw_scheduler] Next frame queued
DEBUG [neovide::window] Render Triggered
TRACE [neovide::renderer] Rendering
TRACE [neovide::editor] Draw commands sent
TRACE [neovide::redraw_scheduler] Next frame queued
DEBUG [neovide::window] Render Triggered
TRACE [neovide::renderer] Rendering
TRACE [neovide::editor] Draw commands sent
TRACE [neovide::redraw_scheduler] Next frame queued
DEBUG [neovide::window] Render Triggered
TRACE [neovide::renderer] Rendering
TRACE [neovide::editor] Draw commands sent
TRACE [neovide::redraw_scheduler] Next frame queued

Could you try setting the guifont? I think maybe the font metrics are getting calculated incorrectly and its doing weird things on linux

Fresh installed Ubuntu 20.04 and I think I'm getting a similar issue with this. There's no mention of the font config errors in #228
Edit: I forgot to mention that the similarity is Ubuntu 20.04 and the weird render (against a white background for clarity).

Here's the log file from running neovide --log
INFO [neovide::bridge] Close watcher started
INFO [neovide::bridge] Neovim process attached
INFO [neovide::bridge] UiCommand processor started
TRACE [neovide::bridge::handler] Neovim notification: "redraw"
TRACE [neovide::editor::grid] Editor resized
TRACE [neovide::editor::grid] Editor cleared
TRACE [neovide::editor::grid] Editor cleared
TRACE [neovide::editor] Option set ArabicShape(true)
TRACE [neovide::editor] Option set AmbiWidth("single")
TRACE [neovide::editor] Option set Emoji(true)
TRACE [neovide::editor] Option set GuiFont("")
TRACE [neovide::editor] Option set GuiFontSet("")
TRACE [neovide::editor] Option set GuiFontWide("")
TRACE [neovide::editor] Option set LineSpace(0)
TRACE [neovide::editor] Option set Pumblend(0)
TRACE [neovide::editor] Option set ShowTabLine(1)
TRACE [neovide::editor] Option set TermGuiColors(false)
TRACE [neovide::editor] Option set Unknown("ext_linegrid", Boolean(true))
TRACE [neovide::editor] Option set Unknown("ext_multigrid", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_hlstate", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_termcolors", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_cmdline", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_popupmenu", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_tabline", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_wildmenu", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_messages", Boolean(false))
TRACE [neovide::editor::grid] Editor resized
TRACE [neovide::editor::grid] Editor cleared
TRACE [neovide::editor::grid] Editor cleared
TRACE [neovide::editor] Image flushed
TRACE [neovide::redraw_scheduler] Next frame queued
WARN [neovide::settings] Initial value load failed for transparency: Error processing request: 1 - 'Key not found: neovide_transparency')
WARN [neovide::settings] Initial value load failed for cursor_vfx_particle_density: Error processing request: 1 - 'Key not found: neovide_cursor_vfx_particle_density')
WARN [neovide::settings] Initial value load failed for cursor_vfx_particle_speed: Error processing request: 1 - 'Key not found: neovide_cursor_vfx_particle_speed')
WARN [neovide::settings] Initial value load failed for cursor_vfx_mode: Error processing request: 1 - 'Key not found: neovide_cursor_vfx_mode')
WARN [neovide::settings] Initial value load failed for cursor_trail_size: Error processing request: 1 - 'Key not found: neovide_cursor_trail_size')
WARN [neovide::settings] Initial value load failed for cursor_vfx_particle_phase: Error processing request: 1 - 'Key not found: neovide_cursor_vfx_particle_phase')
WARN [neovide::settings] Initial value load failed for cursor_vfx_particle_curl: Error processing request: 1 - 'Key not found: neovide_cursor_vfx_particle_curl')
WARN [neovide::settings] Initial value load failed for cursor_animation_length: Error processing request: 1 - 'Key not found: neovide_cursor_animation_length')
WARN [neovide::settings] Initial value load failed for cursor_vfx_particle_lifetime: Error processing request: 1 - 'Key not found: neovide_cursor_vfx_particle_lifetime')
WARN [neovide::settings] Initial value load failed for no_idle: Error processing request: 1 - 'Key not found: neovide_no_idle')
WARN [neovide::settings] Initial value load failed for cursor_antialiasing: Error processing request: 1 - 'Key not found: neovide_cursor_antialiasing')
WARN [neovide::settings] Initial value load failed for refresh_rate: Error processing request: 1 - 'Key not found: neovide_refresh_rate')
WARN [neovide::settings] Initial value load failed for extra_buffer_frames: Error processing request: 1 - 'Key not found: neovide_extra_buffer_frames')
WARN [neovide::settings] Initial value load failed for keyboard_layout: Error processing request: 1 - 'Key not found: neovide_keyboard_layout')
WARN [neovide::settings] Initial value load failed for cursor_animate_in_insert_mode: Error processing request: 1 - 'Key not found: neovide_cursor_animate_in_insert_mode')
WARN [neovide::settings] Initial value load failed for fullscreen: Error processing request: 1 - 'Key not found: neovide_fullscreen')
WARN [neovide::settings] Initial value load failed for cursor_vfx_opacity: Error processing request: 1 - 'Key not found: neovide_cursor_vfx_opacity')
INFO [neovide::window] window created
INFO [neovide::window] renderer created
INFO [neovide::window] Starting window event loop
TRACE [neovide::redraw_scheduler] Next frame queued
TRACE [neovide::redraw_scheduler] Next frame queued
TRACE [neovide::redraw_scheduler] Next frame queued
TRACE [neovide::bridge] UiCommand queued: FocusGained
TRACE [neovide::redraw_scheduler] Next frame queued
TRACE [neovide::redraw_scheduler] Next frame queued
TRACE [neovide::bridge] Executing UiCommand: FocusGained
TRACE [neovide::bridge] UiCommand queued: Resize { width: 0, height: 0 }
DEBUG [neovide::window] Render Triggered
TRACE [neovide::bridge] Executing UiCommand: Resize { width: 0, height: 0 }
TRACE [neovide::renderer] Rendering
TRACE [neovide::editor] Draw commands sent
TRACE [neovide::bridge::handler] Neovim notification: "redraw"
TRACE [neovide::editor] Option set Unknown("ext_cmdline", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_popupmenu", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_tabline", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_wildmenu", Boolean(false))
TRACE [neovide::editor] Option set Unknown("ext_messages", Boolean(false))
TRACE [neovide::editor::grid] Editor resized
TRACE [neovide::editor::grid] Editor cleared
TRACE [neovide::editor::grid] Editor cleared
TRACE [neovide::editor] Image flushed
TRACE [neovide::redraw_scheduler] Next frame queued
TRACE [neovide::bridge::handler] Neovim notification: "redraw"
TRACE [neovide::editor] Image flushed
TRACE [neovide::redraw_scheduler] Next frame queued
TRACE [neovide::redraw_scheduler] Next frame queued
DEBUG [neovide::window] Render Triggered
TRACE [neovide::renderer] Rendering
TRACE [neovide::editor] Draw commands sent
TRACE [neovide::redraw_scheduler] Next frame queued
DEBUG [neovide::window] Render Triggered
TRACE [neovide::renderer] Rendering
TRACE [neovide::editor] Draw commands sent
TRACE [neovide::redraw_scheduler] Next frame queued
DEBUG [neovide::window] Render Triggered
TRACE [neovide::renderer] Rendering
TRACE [neovide::editor] Draw commands sent
TRACE [neovide::redraw_scheduler] Next frame queued
DEBUG [neovide::window] Render Triggered
TRACE [neovide::renderer] Rendering
TRACE [neovide::editor] Draw commands sent
TRACE [neovide::redraw_scheduler] Next frame queued
DEBUG [neovide::window] Render Triggered
TRACE [neovide::renderer] Rendering
TRACE [neovide::editor] Draw commands sent
TRACE [neovide::redraw_scheduler] Next frame queued
DEBUG [neovide::window] Render Triggered
TRACE [neovide::renderer] Rendering
TRACE [neovide::editor] Draw commands sent
TRACE [neovide::redraw_scheduler] Next frame queued
DEBUG [neovide::window] Render Triggered
TRACE [neovide::renderer] Rendering
TRACE [neovide::editor] Draw commands sent
TRACE [neovide::redraw_scheduler] Next frame queued
DEBUG [neovide::window] Render Triggered
TRACE [neovide::renderer] Rendering
TRACE [neovide::editor] Draw commands sent
TRACE [neovide::redraw_scheduler] Next frame queued

Same issue on
Linux ubuntu-workstation 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Any fixes?

I think this has been fixed in main. Please reopen if you come back to this and the issue remains.


Missing Downsampling in inference_no_ground_truth.py Causes Mismatch Error

In the inference_no_ground_truth.py script, the code does not include the downsampling step for in_patch_prev and in_patch_curr using torch.nn.functional.interpolate. This omission leads to a mismatch error when running the super-resolution model, as the model expects inputs at a specific scale.
The missing code:
in_patch_prev = torch.nn.functional.interpolate(in_patch_prev,
                                                scale_factor=1/4,
                                                mode="bicubic")
in_patch_curr = torch.nn.functional.interpolate(in_patch_curr,
                                                scale_factor=1/4,
                                                mode="bicubic")

Problem
The mismatch error occurs because the input patches are not downscaled as required by the super-resolution model. This issue is handled correctly in inference.py, but the same logic is missing in inference_no_ground_truth.py.
Proposed Fix
Add the following lines in the inference_no_ground_truth.py script where patches in_patch_prev and in_patch_curr are defined:
in_patch_prev = torch.nn.functional.interpolate(in_patch_prev,
                                                scale_factor=1/4,
                                                mode="bicubic")
in_patch_curr = torch.nn.functional.interpolate(in_patch_curr,
                                                scale_factor=1/4,
                                                mode="bicubic")

This change will prevent the mismatch error and align the preprocessing steps in inference_no_ground_truth.py with those in inference.py.

Hi,
Thanks for raising the issue and pointing out the problem in detail. The bug is fixed now.


nixos/gnupg: unable to locate a valid pinentry command

Describe the bug
continuation of #90214
using just programs.gnupg.agent.enable = true; doesn't create a fully valid gnupg installation, as the toolchain will also want to have access to a pinentry application.
gpg: agent_genkey failed: No pinentry
Key generation failed: No pinentry

gpgconf --check-programs
gpgconf: error running '/nix/store/dxf4w1gdp2x87d2q326a0064qnbvcl19-gnupg-2.2.20/bin/pinentry': probably not installed
gpg:OpenPGP:/nix/store/dxf4w1gdp2x87d2q326a0064qnbvcl19-gnupg-2.2.20/bin/gpg:1:1:
gpg-agent:Private Keys:/nix/store/dxf4w1gdp2x87d2q326a0064qnbvcl19-gnupg-2.2.20/bin/gpg-agent:1:1:
scdaemon:Smartcards:/nix/store/dxf4w1gdp2x87d2q326a0064qnbvcl19-gnupg-2.2.20/libexec/scdaemon:1:1:
gpgsm:S/MIME:/nix/store/dxf4w1gdp2x87d2q326a0064qnbvcl19-gnupg-2.2.20/bin/gpgsm:1:1:
dirmngr:Network:/nix/store/dxf4w1gdp2x87d2q326a0064qnbvcl19-gnupg-2.2.20/bin/dirmngr:1:1:
pinentry:Passphrase Entry:/nix/store/dxf4w1gdp2x87d2q326a0064qnbvcl19-gnupg-2.2.20/bin/pinentry:0:0:

To Reproduce
programs.gnupg.agent.enable = true; in configuration.nix
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Notify maintainers

Metadata
sent on behalf of someone else in discord. Personal environment is irrelevant.

@jonringer do you use home-manager or not? Is this a graphical or non-graphical system? Can you show us the output of systemctl --user cat gpg-agent.service?

I'm more or less just reposting what someone on discord had trouble with. Seemed like an issue with the service, unfortunately I forgot who it was, and I personally don't use the service. I'm going to close as I don't have any further context to move forward.

Yeah, I encourage that someone on discord to open a bugreport ;-)
This likely requires some back-and-forth to understand the problem and possible solutions.

My original assumption was that adding the package to environment.systemPackages would have fixed the user issue. Wasn't aware of the variants


Feature/graph refactor k paths

Scope & Purpose
This PR is Part 1 of the graph refactor feature. It covers currently the K_PATHS algorithm execution on a single server.
More partial PR's will follow and will include more algorithms and cluster features.

[x] :pizza: New feature (requires CHANGELOG entry, feature documentation and release notes)
[ ] :fire: Performance improvement
[x] :hammer: Refactoring/simplification
[ ] :book: CHANGELOG entry made

Backports:

[x] No backports required

Related Information

[ ] Docs PR:
[ ] Enterprise PR:
[x] Design document: https://github.com/arangodb/documents/blob/7ddae6f13a37b4524f32115d345288ce380f7907/DesignDocuments/02_PLANNING/GraphRefactoring.md

Testing & Verification
(Please pick either of the following options)

[x] The behavior in this PR was manually tested
[x] This change is already covered by existing tests, such as (please describe tests).
[x] This PR adds tests that were used to verify all changes:

[x] Added new C++ Unit tests
[x] Added new integration tests (e.g. in shell_server / shell_server_aql)

[ ] I ensured this code runs with ASan / TSan or other static verification tools

Link to Jenkins PR run:
Documentation

All new features should be accompanied by corresponding documentation.
Bugs and features should furthermore be documented in the CHANGELOG so that
support, end users, and other developers have a concise overview.

[ ] Added entry to Release Notes
[ ] Added a new section in the Manual
[ ] Added a new section in the HTTP API
[ ] Added Swagger examples for the HTTP API
[ ] Updated license information in LICENSES-OTHER-COMPONENTS.md for 3rd party libraries

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/13255/

http://jenkins.arangodb.biz:8080/job/arangodb-matrix-pr/13256/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/13348/

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/13357/

Jenkins:
http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/13567/
All Blue

Jenkins:
http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/13567/
All Blue


Error normalising data when morphToMany relationship key doesn't exist

Stumbled across this today, seems like there's an issue normalising the data when the relationship key is missing, at least for the morphToMany relationship:
export default class Project extends Model {
  static get entity () {
    return 'projects'
  }

  static fields () {
    return {
      id: this.attr(null),
      name: this.attr(''),
      tags: this.morphToMany(Tag, Taggable, 'tag_id', 'taggable_id', 'taggable_type'),
    }
  }
}

Trying to insertOrUpdate with this project object
{
  'id': 1
  'name' 'Hello'
}

(Notice the tag key is missing in the data)
TypeError: related is undefined                vuex-orm.esm.js:6894

Thanks for the report! I've reproduced it and made a fix at #120. I'll merge this and release the new version soon!

This is fixed with Vuex ORM 0.23.1!
https://github.com/vuex-orm/vuex-orm/releases/tag/v0.23.1
Thank you for reporting this issue and I hope the new version will help your development ❤

This package is already helping with our development a alot! Thanks for the fix


API pruning

Since MergingWithMaster day is coming up I tried out some of the commands from the API.
I realized after I went through the API that #27 exists already, :expressionless: so I struck through the issues I found that were caused by unimplemented API.
Started with:
from PyOpenWorm import *
connect('default.conf')

(Is there a way to get to PyOpenWorm's worm.db from anywhere, to avoid having to make a new .conf file that has the relative .db position for every directory I want to run PyOW from?)
API inconsistencies (?)

Worm().cells() does not return anything.
The first example here returns an error on the line c = Connection(pre=n1,post=n2,class="synapse") due to outdated syntax.
The same line as above appears here as well.
Tried Relationship().pull() for this, but it didn't work ('Relationship' object has no attribute 'pull')
This example doesn't work as it is written. It works if you get the Cell object via net.aneuron('ADAL') where net is the Network from Worm().neuron_network().
This example does not work for me either. It returns a generator object, and wrapping it in list returns an empty list.
This seems incomplete.
I don't know enough about this to say if it is working or not, but it produces no errors.
Can't get morphology using this part of the API with net.aneuron('ADAL').morphology.
This suffers from the same slowness as Neuron.connection() from #90.
Error from this. Got a Muscle by doingmvl06 = list(Worm().muscle())[0], then tried mvl06.receptor(). Muscle object has no attribute 'receptor'
The same for this as well.
Here population is not defined.
This doesn't work either, because of above.
I believe these arguments into the Connection constructor are supposed  to be updated (pre_cell instead of pre, etc.)
No attribute 'type' for the same reason as above, I suspect.
The same for strength, neurotransmitter and ConnectionType.

Hi @travs. The document you reference was a proposal that mostly hasn't been modified since moving into the implementation phase, so it may not entirely reflect what I, at least, intend to support with PyOpenWorm for the next release. Is this ticket meant to propose an update to that document to reflect the state of the API as it has been implemented or to propose changes to what has been implemented in order to bring it into line with that document?

The first one.
I can definitely help update the docs before we merge alpha0.5 into master, I'm just not familiar with Sphinx, so I'll have to brush up on that as we start.

I think the most that document needs is a pointer back to the live API as generated from the docstrings in source code.

Probably lol. Where is the live API?

http://pyopenworm.readthedocs.org/en/alpha0.5/

@travs Awesome list of things you tested out!!!  So cool.  You make good points on the documentation side of this.  I'll include this one in the alpha0.5 critical path.

Related to #98: The autodocs generated documentation is already present on the main page of the docs. Rather than delete the draft, I would create a document summarizing the design considerations that went into our current iteration and link to the draft from there. The draft itself could hold a link to the most recent docs to resolve residual confusion.

Sounds like a good idea to me


No such file or directory: '/content/DeepDreamAnim/models/bvlc_googlenet/deploy.prototxt'

Hi ! When starting to dream i get "FileNotFoundError: [Errno 2] No such file or directory: '/content/DeepDreamAnim/models/bvlc_googlenet/deploy.prototxt'" Any idea whats wrong ??
Full error:
"Traceback (most recent call last):
File "dreamer.py", line 533, in
args.zoom, args.stepsize, args.blendflow, args.blendstatic, args.layers, args.guide, args.gpu, args.flow, args.flowthresh, args.divide, args.maxWidth, args.maxHeight, args.modeln)
File "dreamer.py", line 281, in main
text_format.Merge(open(net_fn).read(), model)
FileNotFoundError: [Errno 2] No such file or directory: '/content/DeepDreamAnim/models/bvlc_googlenet/deploy.prototxt'
" Ubuntu 20.04 RTX 2080 TI

I recommend running this code in google colab. Colab notebook is included in the repo.
The problem you are facing is because of this line
The code was setup to run in google colab by default.
You can change that line but then you will have to download the bvlc_googlenet model from the Caffe Model Zoo and place it in the models directory.
Check out this reddit post for the context of this repo.
P.S. This code is still under development. You can contribute if you want :}

Mate ! Thx for the fast help ! Will change the line and hoping i can make it work. Can i run this on my 2080 TI ?? Or will it be too slow ?

Mate ! Thx for the fast help ! Will change the line and hoping i can make it work. Can i run this on my 2080 TI ?? Or will it be too slow ?

It depends on the resolution of your video.
I recommend starting with a 9:16 (Tik Tok/Instagram Reels) resolution.
Main parameters you should use for a decent amount of dreaming:
3 octaves, 4 iteration per octave, 1.2 octave scale and flow 1
This code is under development. It will give errors. If you resolve them please send a PR I will be more than happy to merge.

I wish i am good enough to help you but still a noob !

Just tested out the colab. Not working for me :-(

Yeah as I said it still needs cleaning. Check the comments of that reddit post. I discussed the problems there.
In the mean time you can watch the repo. 😅


Add print option to hide code blocks

Is your feature request related to a problem? Please describe.
Consumers, who wish to expose GraphQL documentation for non technical users may desire to hide code blocks from type definition pages. In those cases, code blocks do not provide any value and have potential to overwhelm the readers.
Describe the solution you'd like
Consider adding a new field within printTypeOptions such as code, so that the configuration can be supplied as:
plugins: [
    [
      "@graphql-markdown/docusaurus",
       {
        ...otherOptions /* not included for brevity */,
        printTypeOptions: {
          code: false, // disable code blocks, same as CLI flag --noCode
        },
      },
    ],
  ],

Hi @ris314
I admit that's something I though about and never implemented, since I didn't have a use case :sweat_smile:
Since it is a low hanging fruit, it will be release today in 1.20.2.

Released in 1.20.2 :rocket:

that was super fast!!
thank you


active menu class makes the 'hover dropdown menu' stop working

Hey guys, just did the following thing with my menu:
`

FooBarMenu

Foo
Bar

`
With that, when I put the mouse over the menu, the dropdown menu stop working, in other words, the 'Foo' and 'Bar' sub item dosen't show up.
Does any know if this is an error or am I doing something wrong?
Thanks!

Please, try to reproduce the bug from here: http://jsfiddle.net/rduvhn8u/1/


API-6752:Upgraded gson to 2.9.1

Purpose
In order to fix CWE-502 . More info here https://github.com/SiftScience/sift-android/issues/96
Technical Details
Upgraded to latest version of gson 2.9.1
Testing details

Ran hello-sift app. Click buttons
Check app logs

D/EGL_emulation: app_time_stats: avg=83.64ms min=6.97ms max=948.31ms count=14
D/siftscience.android.Uploader: Built HTTP request for batch of size 3
D/siftscience.android.Uploader: Uploading batch of size 3
D/siftscience.android.Uploader: Sending HTTP request
D/siftscience.android.Uploader: HTTP 200
D/EGL_emulation: app_time_stats: avg=23.96ms min=13.52ms max=402.50ms count=53
D/siftscience.android.Queue: Append event: com.sift.api.representations.MobileEventJson@a5660c5[time=1662727189723,path=<null>,mobileEventType=<null>,userId=TestUser,installationId=7cacc71792d22b83,fields=<null>,deviceProperties=<null>,androidDeviceProperties=<null>,androidAppState=com.sift.api.representations.AndroidAppStateJson@5a16a1a[activityClassName=OtherActivity,location=<null>,sdkVersion=1.1.3,batteryLevel=1.0,batteryState=4,batteryHealth=2,plugState=0,networkAddresses=[fe80::b449:54ff:fe0e:f895, fe80::5054:ff:fe12:3456, 2001:2::5054:ff:fe12:3456, <IP_ADDRESS>, fe80::22:ab59:f553:76c, 2001:2::110e:8049:4b7f:4ff0, 2001:2::336f:7c6b:56a1:1121, <IP_ADDRESS>]]]

Clicked the buttons and check logs if we still receive events in moby logs

Sep 9 15:42:48 istio-gateway-7b6d6b7b9b-lqpfv istio-proxy "GET /v3/accounts/4e1a50e172beb95cf1e4ae54/users/al_capone/devices HTTP/1.1" 200 - via_upstream - "-" 0 69 47 47 "<IP_ADDRESS>, <IP_ADDRESS>,<IP_ADDRESS>" "Pingdom.com_bot_version_1.4_(http://www.pingdom.com/)" "f928ac38-9ba3-4b25-af27-ec4cc56c9d14" "api3-gke.prod.us-e4.gcp.sift.com" "<IP_ADDRESS>:8080" outbound|8080||api3.api3.svc.cluster.local <IP_ADDRESS>:49404 <IP_ADDRESS>:8443 <IP_ADDRESS>:10307 - -

Release Plan
Release new version 1.1.3

From version 2.8. to 2.9.1 there were mainly bug fixes https://github.com/google/gson/blob/master/CHANGELOG.md. The only reason why version was bumped there is removal of support of java 6 which is ok for our android.
I tested like I mentioned in pr by checking what we send and that the payload is processed by moby, there is  only one type of event that we send, so normally it is ok. I tried with several phones.


[BUG] Nodes with names consisting of numbers and single underscores are considered as numbers

Hi there @timcera !
Thank you for this great software. I ran into the following problem today:
'node,19_3,Depth_above_invert' leads to the node label beeing interpreted as 193 in acordance to https://peps.python.org/pep-0515/.
The issues seems to be part of tsutils.make_list. I will leave a comment with a solution if I find any.

Could you post the output file with node "19_3"?  Just a short run.

@timcera I will create a sample snippet and post the file and the run here once I have access to the data on Monday again.

Looked this up and this is an unwanted feature of python.  I don't like so I will include some logic in swmmtoolbox to make sure the names are considered labels rather than numbers...
Here is the culprit: https://peps.python.org/pep-0515/

I will take a look at this.  I can include some logic to not convert to float or int for swmmtoolbox.

@timcera I'm also running into this issue. I've confirmed that the bug is in tsutils.make_list. Do you have availability / intent to patch this yourself or would you be okay with a PR? Note I don't have good context for what tsutils is used for outside of swmmtoolbox

A PR would be great!
First choice would be to remove using tsutils.make_list from swmmtoolbox.  tsutils.make_list is way overkill, because all swmmtoolbox needs is consistent split of strings on " " and "," if a string is passed.  I looked a little bit at this option and it is a bit painful because it needs to support both Python and command line APIs.
A close second choice would be to move processing of labels for the command line API to extract_cli, and then remove all labels processing from the extract Python API which could then expect labels to be a Python list of lists.  Maybe this idea should be first actually.
Third choice would be to add a keyword to tsutils.make_list, something like "return_all_strings=False" as the default, which if True wouldn't convert number like strings to numbers.
Any help would be appreciated.  Just so there isn't duplication of effort, I might be able to work on this next week and I am going to explore the second choice because that might help with some of my other toolboxes.  However, any help is appreciated and if you have some idea or workaround that you can put together into a PR that solves your problem that would be fantastic.

Hi Tim,
thanks for coordinating with Lucas and making this fix.
4.0.14 works for our needs
Attached is a test file that i tried it on. It is an .OUT file but i've had to rename it
this functions in 4.0.14
swmmtoolbox.extract(outfile_location, [['node', '6666_8', 'Total_inflow']])
but was failing in 4.0.13 (different calling syntax)
swmmtoolbox.extract(outfile_location, 'node, 6666_8, Total_inflow')
Thanks
Sanjay
zeta_renamed_tank.out.rename.zip


Investigate performance of #initTxnIndexMap()

The #initTxnIndexMap() rule traverses the <transaction> cell and builds the <txnIndexMap>, a service cell which clusters the transactions by their groups and maintains a reverse index from group indices to transaction ids.
The #initTxnIndexMap() rule will be executed when a transaction group evaluation is triggered by the #evalTxGroup() rule, which fires both when the initial (outer) group is evaluated and an inner group is evaluated.
We suspect that this rule is expensive to execute, and we would like to determine how, in fact, expensive it is.
As an initial step, we should investigate the tests/specs/calls/buy-asset-spec.md:

create a variant of this spec that has the <txnIndexMap> cell pre-built.
compare execution time with the base spec
ideally, figure out a way to do rule-level profiling

I tried the test you suggested in the linked branch. There seems to be about a 10 second speedup between the two (160 vs. 170 seconds). I'm guessing this means that these are a bit slower than the average rewrite, but not that much worse. Was there an example where it seemed to be causing problems?

Thanks @nwatson22. OK, I'll be closing it for now.


Banner should be unset

We should have a button to remove banner in case of not wanting to have one.

PR'd

PR'd

Closed by #187

Closed by #187


KAFKA-15045: Fix RackAwareTaskAssignorTest

Some unnecessary changes to RackAwareTaskAssignor broke the tests, this PR reverts those changes.

@apourchet Thanks for your contribution. The failed test is already fixed by #16044


Blue warning icon has insufficient contrast

The blue warning icon does not have enough contrast against the background (this should be at least 3:1).
See https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html

I can't verify or replicate this, it might be better now after some other changes. The only contrast problem I can see if the blue links against the table background in the problem list.


PNCK DEV APP

Describe the bug:
สวัสดี ครับผม
Link to the blitz that caused the error
https://stackblitz.com/edit/node-ymc5qp?file=index.js
Steps to reproduce:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior:
OK รู้เรื่อง
Version of webcontainer:
Hash: ed9672a3e8d5b719017191dac2dba042f373a0d7
Screenshots:

Desktop (please complete the following information):
Browser name  = Chrome
Full version  = 91.0.4472.114
Major version = 91
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 88921030,
  "usedJSHeapSize": 80152418,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}

Additional context:

Closing this issue as it's unclear what goes wrong and none of the required details are filled in. Feel free to open a new issue and fill in all the necessary details so we have enough information to have a look ourselves. The more information we have, the better we can help you 🙏 .


StoryblokComponent vs component

I get huge performance issues when using the StoryblokComponent instead of component:
example using component: https://family-business-unit-f0hhivfwp-cloudnova-srl.vercel.app/

example using StoryblokComponent: https://family-business-unit-6nuzynxzr-cloudnova-srl.vercel.app/

Hi @m0zz094 thanks for this issue! I'm curious about this, because StoryblokComponent is a basic wrapper of component as you can see https://github.com/storyblok/storyblok-vue/blob/main/lib/StoryblokComponent.vue
Have you investigated this further?

@manuelschroederdev keeping you on the loop

Hi @alexjoverm, I haven't investigated this further, but if you need more context here's what I'm doing on [...slug].vue
``

Hey @m0zz094, could you possibly provide a link to your complete project on GitHub or StackBlitz? That would make it a little easier for us to debug the issue. Thanks. 😊

I've create two different versions of a demo project, one using the StoryblokComponent, one using the default component. I've uploaded them to Vercel and couldn't identify any notable performance differences.
https://storyblok-components-test.vercel.app
https://components-test-inky.vercel.app
Are you still encountering these issues?

I'm also experiencing the issue with the StoryblokComponent.
Here's a comparison of the markup generated for the two test sites @manuelschroederdev set up with Javascript disabled.
Notice that the component markup is only generated on https://components-test-inky.vercel.app/

Thank you very much for pointing this out, @Lauritzz77 and @caroillemann. We will investigate this further and get back to you as soon as possible.

Hi, @m0zz094 do you know if this is still an issue? @manuelschroederdev @Dawntraoz any update from our side?

Hi @alvarosabu, I haven't changed my codebase since then honestly, I'm still using the component approach for now

As per the abovementioned issue, this behavior was fixed from v4.x.x -> https://github.com/storyblok/storyblok-nuxt/issues/204#issuecomment-1350794291.
Can you @m0zz094 replace your solution with StoryblokComponents using a v4.x or above of this package so we can be sure this issue can be closed <3 Thanks in advance!

Any updates @m0zz094?


Migrate old meetup images from directus to Google Photos

Some images are hosted in our directus instance. We don't use that anymore

Those images should be downlaoded and reuploaded in google photos albums
Those albums should be linked to old meetups respectively and the photos field in directus should be removed
The photos fields in the api routes should be removed in astro

that's fixed ayy


default-theme.textpattern.com is down

Need to unpick and resurrect.

I thought we had got rid of it in favour of the demo site?

Hmm, maybe we did - I'll check the archives.

Evidently we did!
https://github.com/textpattern/server-config/commit/e896f9d8ed1c83569bda70dea8c8dec450524816#diff-88af101bd2443893d675c53f49d1b78f901e0588aff514471875800dce82d938


Receiver link "modify" method causing exception

The "modify" method causes an "undefined is not a function" exception, as the Modified delivery state sets the ForcedType of the boolean values to "bool". When the codec is then looking for an encoder for for these values it fails as there are none in Types for "bool", changing the ForcedType to "Boolean" fixes this issue:
Modified.prototype.getValue = function() {
  var self = this;
  return [
    new ForcedType('boolean', self.deliveryFailed),
    new ForcedType('boolean', self.undeliverableHere),
    new AMQPFields(self.messageAnnotations)
  ];
};

thanks for the bug report, nice catch!


Update logic for adding time bounds

Is your feature request related to a problem? If yes, Please describe

Currently, time bounds are generated using the same generic bounds function as lat and lon.
Describe your proposed solution

TBD
Describe alternatives solutions you've considered

Additional context

Will reopen this issue if necessary.


PHOENIX-4765 Add client and server side config property to enable rol…

…lback of splittable System Catalog if required
@ChinmaySKulkarni  can you please review. This PR adds a config that is used to enable rollback of splittable SYSTEM.CATALOG if required. If the config is true, we continue storing the parent table column metadata while creating a view. We also block any add columns and while creating a view try to lock the parent table to prevent conflicting concurrent changes.

@karanmehta93  Can you please review?

Once flipped back to "false", setting this flag back to "true" may not cleanly rollback since SYSCAT may have split since then. Let's add a comment about that as well as the SYSTEM.CHILD_LINK metadata that we discussed. Otherwise +1. Thanks @twdsilva


Music Generation with Memory Retention

Hey there. I would like to add a new sub project/topic/example here which would be great for users who have interests in music creation and also for those who just want to try different instrumentals out.This can be done using Memory Retention methods,which will not only allow the model to remember what the user wanted before but also what the model itself provided as an output previously depending upon its importance.
I have been doing ML/DL tasks for quite a while now and have made projects and done an internship on the same domain.
I would like to take this issue under GSSOC'24 and solve it real quick.
Hope I make it to your sight.
Thanks..

This issue has been assigned to you @Soubeer.
Please follow the PR guidelines.

I didn't get your point. Did you make a PR earlier and now it's not visible? Try looking in the closed ones, in case.

I didn't get your point. Did you make a PR earlier and now it's not visible? Try looking in the closed ones, in case.

@invigorzz313 I am going to make a new PR now , can you assign me a level here just to make things easier to count from the PR?


Correct secret generation for external secrets.

Description
This change will fix external secret configuration, such that when a secret is provided for external db/storage, the appropriate internal DSPO managed secrets are created.
Summary of changes:

Made externaldb fields required
made db secret non mariadb specific (to account for externaldb)
allow deployment of storage/db secrets for external options
disable minio deployment by default
add tests

How Has This Been Tested?
Tested with external mariadb/minio on ocp live.
Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

/test pr-image-mirror

/lgtm