Error: Not implemented: window.computedStyle(elt, pseudoElt)

Describe the bug
Vitest show Error: Not implemented: window.computedStyle(elt, pseudoElt) while Jest not.
I'm about to migrate my react app with Ant Design from Jest to Vitest, after I'm done following migration guide and try run the new test with Vitest, Vitest show the error message come from JSDOM.
The error message only show if I test the the specific Ant Design component (Table in this case).
Reproduction
https://github.com/fikryfahrezy/my-react-app
Run test with Jest
yarn test:jest src/index.jest.test.tsx
Run test with Vitest
yarn test:vitest src/index.vitest.test.tsx
System Info
System:
    OS: Linux 5.19 undefined
    CPU: (8) x64 Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz
    Memory: 6.58 GB / 19.39 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 14.20.0 - /run/user/1000/fnm_multishells/390656_1663662564383/bin/node
    Yarn: 1.22.19 - /usr/bin/yarn
    npm: 6.14.17 - /run/user/1000/fnm_multishells/390656_1663662564383/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Firefox: 103.0.2
  npmPackages:
    @vitejs/plugin-react: ^2.1.0 => 2.1.0
    vite: ^3.1.0 => 3.1.3
    vitest: ^0.23.4 => 0.23.4

Used Package Manager
yarn
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I don't know what Jest does under the hood, but this is normal JSDOM behaviour as far as I understand. Try workaround from this thread: https://github.com/nickcolley/jest-axe/issues/147

The error not showing after try the workaround from NickColley/jest-axe/#147.
Thanks @sheremet-va for your help.


HDFS-16954. RBF:  rename a dir that has multiple destinations  to a dir that just…

Description of PR
https://issues.apache.org/jira/browse/HDFS-16954
How was this patch tested?
TestRouterAllResolver
For code changes:
change in rename  ,rename2

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 48s

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.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
42m 14s

trunk passed

+1 :green_heart:
compile
0m 42s

trunk passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
0m 37s

trunk passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
checkstyle
0m 30s

trunk passed

+1 :green_heart:
mvnsite
0m 41s

trunk passed

+1 :green_heart:
javadoc
0m 48s

trunk passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 55s

trunk passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
spotbugs
1m 32s

trunk passed

+1 :green_heart:
shadedclient
23m 34s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 33s

the patch passed

+1 :green_heart:
compile
0m 37s

the patch passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
0m 37s

the patch passed

+1 :green_heart:
compile
0m 31s

the patch passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
javac
0m 31s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 17s
/results-checkstyle-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-project/hadoop-hdfs-rbf: The patch generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1 :green_heart:
mvnsite
0m 35s

the patch passed

+1 :green_heart:
javadoc
0m 32s

the patch passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 50s

the patch passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
spotbugs
1m 21s

the patch passed

+1 :green_heart:
shadedclient
24m  6s

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

_ Other Tests _

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

+1 :green_heart:
asflicense
0m 33s

The patch does not generate ASF License warnings.

124m 54s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.federation.router.TestRouterAllResolver

Subsystem
Report/Notes

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

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

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

uname
Linux 7dd82c9bb059 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / bf3206afb21c152ac46157910a5392f9fbacd8b3

Default Java
Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

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

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

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

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

Can try with TestRouterRPCMultipleDestinationMountTableResolver
that is a specific varient without MockResolver

TestRouterRPCMultipleDestinationMountTableResolver

@ayushtkn  Thank you for your review.  I move this test to  TestRouterRPCMultipleDestinationMountTableResolver.

: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.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
51m 12s

trunk passed

+1 :green_heart:
compile
0m 44s

trunk passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
0m 37s

trunk passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
checkstyle
0m 33s

trunk passed

+1 :green_heart:
mvnsite
0m 45s

trunk passed

+1 :green_heart:
javadoc
0m 48s

trunk passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 55s

trunk passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
spotbugs
1m 37s

trunk passed

+1 :green_heart:
shadedclient
21m 19s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 35s

the patch passed

+1 :green_heart:
compile
0m 36s

the patch passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
0m 36s

the patch passed

+1 :green_heart:
compile
0m 34s

the patch passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
javac
0m 34s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 18s

the patch passed

+1 :green_heart:
mvnsite
0m 34s

the patch passed

+1 :green_heart:
javadoc
0m 35s

the patch passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 52s

the patch passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
spotbugs
1m 27s

the patch passed

+1 :green_heart:
shadedclient
21m  7s

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

_ Other Tests _

-1 :x:
unit
20m 38s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 37s

The patch does not generate ASF License warnings.

128m 21s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.federation.router.TestRouterRPCMultipleDestinationMountTableResolver

Subsystem
Report/Notes

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

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

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

uname
Linux b77b7c78e468 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / eb9adfec586aadad60d2e24b2c584aa79909f40c

Default Java
Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

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

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

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

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 35s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets 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 2 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
44m 12s

trunk passed

+1 :green_heart:
compile
0m 42s

trunk passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
0m 41s

trunk passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
checkstyle
0m 32s

trunk passed

+1 :green_heart:
mvnsite
0m 45s

trunk passed

+1 :green_heart:
javadoc
0m 51s

trunk passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 56s

trunk passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
spotbugs
1m 36s

trunk passed

+1 :green_heart:
shadedclient
21m  7s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 34s

the patch passed

+1 :green_heart:
compile
0m 36s

the patch passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
0m 36s

the patch passed

+1 :green_heart:
compile
0m 33s

the patch passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
javac
0m 33s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 19s
/results-checkstyle-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-project/hadoop-hdfs-rbf: The patch generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1 :green_heart:
mvnsite
0m 35s

the patch passed

+1 :green_heart:
javadoc
0m 32s

the patch passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 48s

the patch passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
spotbugs
1m 19s

the patch passed

+1 :green_heart:
shadedclient
20m 26s

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

_ Other Tests _

+1 :green_heart:
unit
20m 30s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 39s

The patch does not generate ASF License warnings.

120m 42s

Subsystem
Report/Notes

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

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

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

uname
Linux 03a4cdff8e15 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 68990803b3acc09fc33e0777aaa9cdf312a004dc

Default Java
Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

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

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

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

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 53s

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.

+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 2 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
41m 23s

trunk passed

+1 :green_heart:
compile
0m 44s

trunk passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
0m 40s

trunk passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
checkstyle
0m 34s

trunk passed

+1 :green_heart:
mvnsite
0m 46s

trunk passed

+1 :green_heart:
javadoc
0m 51s

trunk passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 56s

trunk passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
spotbugs
1m 33s

trunk passed

+1 :green_heart:
shadedclient
20m 45s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 34s

the patch passed

+1 :green_heart:
compile
0m 36s

the patch passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
0m 36s

the patch passed

+1 :green_heart:
compile
0m 32s

the patch passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
javac
0m 32s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 18s
/results-checkstyle-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-project/hadoop-hdfs-rbf: The patch generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1 :green_heart:
mvnsite
0m 35s

the patch passed

+1 :green_heart:
javadoc
0m 34s

the patch passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 51s

the patch passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
spotbugs
1m 21s

the patch passed

+1 :green_heart:
shadedclient
20m 26s

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

_ Other Tests _

+1 :green_heart:
unit
21m 52s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 37s

The patch does not generate ASF License warnings.

119m  9s

Subsystem
Report/Notes

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

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

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

uname
Linux c5eda2af2e77 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 6420e07e6d318096ffb70d4f8bf022a183573bb9

Default Java
Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

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

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5483/6/console

versions
git=2.25.1 maven=3.6.3 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 49s

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.

+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 2 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
42m 18s

trunk passed

+1 :green_heart:
compile
0m 42s

trunk passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
0m 36s

trunk passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
checkstyle
0m 29s

trunk passed

+1 :green_heart:
mvnsite
0m 42s

trunk passed

+1 :green_heart:
javadoc
0m 47s

trunk passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 54s

trunk passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
spotbugs
1m 31s

trunk passed

+1 :green_heart:
shadedclient
23m 43s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 33s

the patch passed

+1 :green_heart:
compile
0m 36s

the patch passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
0m 36s

the patch passed

+1 :green_heart:
compile
0m 30s

the patch passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
javac
0m 30s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 16s

the patch passed

+1 :green_heart:
mvnsite
0m 34s

the patch passed

+1 :green_heart:
javadoc
0m 32s

the patch passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 49s

the patch passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
spotbugs
1m 21s

the patch passed

+1 :green_heart:
shadedclient
23m 30s

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

_ Other Tests _

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

+1 :green_heart:
asflicense
0m 34s

The patch does not generate ASF License warnings.

124m 36s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.federation.router.TestRouterRPCMultipleDestinationMountTableResolver

Subsystem
Report/Notes

Docker
ClientAPI=1.42 ServerAPI=1.42 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5483/7/artifact/out/Dockerfile

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

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

uname
Linux 93c3d0171232 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / afc196b7f7e02d758b3bb4bb64e8f0dde3d2430a

Default Java
Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5483/7/testReport/

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5483/7/console

versions
git=2.25.1 maven=3.6.3 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 51s

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  1s

detect-secrets 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 2 new or modified test files.

_ trunk Compile Tests _

-1 :x:
mvninstall
47m 18s
/branch-mvninstall-root.txt
root in trunk failed.

+1 :green_heart:
compile
0m 41s

trunk passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
0m 36s

trunk passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
checkstyle
0m 29s

trunk passed

+1 :green_heart:
mvnsite
0m 42s

trunk passed

+1 :green_heart:
javadoc
0m 48s

trunk passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 53s

trunk passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
spotbugs
1m 31s

trunk passed

+1 :green_heart:
shadedclient
23m 59s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 33s

the patch passed

+1 :green_heart:
compile
0m 36s

the patch passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
0m 36s

the patch passed

+1 :green_heart:
compile
0m 30s

the patch passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
javac
0m 30s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 16s

the patch passed

+1 :green_heart:
mvnsite
0m 34s

the patch passed

+1 :green_heart:
javadoc
0m 32s

the patch passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 47s

the patch passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
spotbugs
1m 22s

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
20m 44s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 33s

The patch does not generate ASF License warnings.

129m 41s

Subsystem
Report/Notes

Docker
ClientAPI=1.42 ServerAPI=1.42 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5483/8/artifact/out/Dockerfile

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

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

uname
Linux 29bc368694b4 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / d5ca17ad0cb132d6d028bcdaca637e6ca7c1547b

Default Java
Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5483/8/testReport/

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5483/8/console

versions
git=2.25.1 maven=3.6.3 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
43m 51s

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.

+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 2 new or modified test files.

_ trunk Compile Tests _

-1 :x:
mvninstall
0m 10s
/branch-mvninstall-root.txt
root in trunk failed.

-1 :x:
compile
0m 10s
/branch-compile-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in trunk failed.

-0 :warning:
checkstyle
0m  8s
/buildtool-branch-checkstyle-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
The patch fails to run checkstyle in hadoop-hdfs-rbf

-1 :x:
mvnsite
0m 10s
/branch-mvnsite-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in trunk failed.

-1 :x:
javadoc
0m 10s
/branch-javadoc-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in trunk failed.

-1 :x:
spotbugs
0m 10s
/branch-spotbugs-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in trunk failed.

-1 :x:
shadedclient
0m 59s

branch has errors when building and testing our client artifacts.

_ Patch Compile Tests _

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

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

-1 :x:
javac
0m 10s
/patch-compile-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in the patch failed.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m  8s
/buildtool-patch-checkstyle-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
The patch fails to run checkstyle in hadoop-hdfs-rbf

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

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

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

-1 :x:
shadedclient
1m 22s

patch has errors when building and testing our client artifacts.

_ Other Tests _

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

+0 :ok:
asflicense
0m 11s

ASF License check generated no output?

49m 24s

Subsystem
Report/Notes

Docker
ClientAPI=1.42 ServerAPI=1.42 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5483/9/artifact/out/Dockerfile

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

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

uname
Linux f3de657134df 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / d5ca17ad0cb132d6d028bcdaca637e6ca7c1547b

Default Java
Red Hat, Inc.-1.8.0_362-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5483/9/testReport/

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5483/9/console

versions
git=2.9.5 maven=3.6.3

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

This message was automatically generated.

Requires a rebase for a green build due to that cyclonedx change, can you rebase once

Requires a rebase for a green build due to that cyclonedx change, can you rebase once

Done. Rebase it. Please review it again. thx.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 49s

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.

+1 :green_heart:
@author
0m  1s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

-1 :x:
mvninstall
0m 10s
/branch-mvninstall-root.txt
root in trunk failed.

-1 :x:
compile
0m 10s
/branch-compile-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkUbuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1.txt
hadoop-hdfs-rbf in trunk failed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1.

-1 :x:
compile
0m 10s
/branch-compile-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkPrivateBuild-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09.txt
hadoop-hdfs-rbf in trunk failed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09.

-0 :warning:
checkstyle
0m  8s
/buildtool-branch-checkstyle-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
The patch fails to run checkstyle in hadoop-hdfs-rbf

-1 :x:
mvnsite
0m  9s
/branch-mvnsite-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in trunk failed.

-1 :x:
javadoc
0m 10s
/branch-javadoc-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkUbuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1.txt
hadoop-hdfs-rbf in trunk failed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1.

-1 :x:
javadoc
0m 10s
/branch-javadoc-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkPrivateBuild-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09.txt
hadoop-hdfs-rbf in trunk failed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09.

-1 :x:
spotbugs
0m  9s
/branch-spotbugs-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in trunk failed.

-1 :x:
shadedclient
1m  9s

branch has errors when building and testing our client artifacts.

_ Patch Compile Tests _

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

-1 :x:
compile
0m 10s
/patch-compile-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkUbuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1.txt
hadoop-hdfs-rbf in the patch failed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1.

-1 :x:
javac
0m 10s
/patch-compile-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkUbuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1.txt
hadoop-hdfs-rbf in the patch failed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1.

-1 :x:
compile
0m  9s
/patch-compile-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkPrivateBuild-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09.txt
hadoop-hdfs-rbf in the patch failed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09.

-1 :x:
javac
0m  9s
/patch-compile-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkPrivateBuild-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09.txt
hadoop-hdfs-rbf in the patch failed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m  7s
/buildtool-patch-checkstyle-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
The patch fails to run checkstyle in hadoop-hdfs-rbf

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

-1 :x:
javadoc
0m 10s
/patch-javadoc-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkUbuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1.txt
hadoop-hdfs-rbf in the patch failed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1.

-1 :x:
javadoc
0m 10s
/patch-javadoc-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkPrivateBuild-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09.txt
hadoop-hdfs-rbf in the patch failed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09.

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

-1 :x:
shadedclient
1m 46s

patch has errors when building and testing our client artifacts.

_ Other Tests _

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

+0 :ok:
asflicense
0m 11s

ASF License check generated no output?

7m 22s

Subsystem
Report/Notes

Docker
ClientAPI=1.42 ServerAPI=1.42 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5483/10/artifact/out/Dockerfile

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

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

uname
Linux 81beb221371b 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 503f466cc46924848913821aeba89a59ac88089e

Default Java
Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5483/10/testReport/

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5483/10/console

versions
git=2.25.1 maven=3.6.3

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 54s

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.

+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 2 new or modified test files.

_ trunk Compile Tests _

-1 :x:
mvninstall
0m 13s
/branch-mvninstall-root.txt
root in trunk failed.

-1 :x:
compile
0m 12s
/branch-compile-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkUbuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1.txt
hadoop-hdfs-rbf in trunk failed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1.

-1 :x:
compile
0m 12s
/branch-compile-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkPrivateBuild-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09.txt
hadoop-hdfs-rbf in trunk failed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09.

-0 :warning:
checkstyle
0m 10s
/buildtool-branch-checkstyle-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
The patch fails to run checkstyle in hadoop-hdfs-rbf

-1 :x:
mvnsite
0m 13s
/branch-mvnsite-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in trunk failed.

-1 :x:
javadoc
0m 12s
/branch-javadoc-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkUbuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1.txt
hadoop-hdfs-rbf in trunk failed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1.

-1 :x:
javadoc
0m 13s
/branch-javadoc-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkPrivateBuild-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09.txt
hadoop-hdfs-rbf in trunk failed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09.

-1 :x:
spotbugs
0m 13s
/branch-spotbugs-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
hadoop-hdfs-rbf in trunk failed.

-1 :x:
shadedclient
1m 27s

branch has errors when building and testing our client artifacts.

_ Patch Compile Tests _

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

-1 :x:
compile
0m 13s
/patch-compile-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkUbuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1.txt
hadoop-hdfs-rbf in the patch failed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1.

-1 :x:
javac
0m 13s
/patch-compile-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkUbuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1.txt
hadoop-hdfs-rbf in the patch failed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1.

-1 :x:
compile
0m 13s
/patch-compile-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkPrivateBuild-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09.txt
hadoop-hdfs-rbf in the patch failed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09.

-1 :x:
javac
0m 13s
/patch-compile-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkPrivateBuild-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09.txt
hadoop-hdfs-rbf in the patch failed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 11s
/buildtool-patch-checkstyle-hadoop-hdfs-project_hadoop-hdfs-rbf.txt
The patch fails to run checkstyle in hadoop-hdfs-rbf

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

-1 :x:
javadoc
0m 12s
/patch-javadoc-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkUbuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1.txt
hadoop-hdfs-rbf in the patch failed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1.

-1 :x:
javadoc
0m 12s
/patch-javadoc-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkPrivateBuild-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09.txt
hadoop-hdfs-rbf in the patch failed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09.

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

-1 :x:
shadedclient
2m 19s

patch has errors when building and testing our client artifacts.

_ Other Tests _

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

+0 :ok:
asflicense
0m 14s

ASF License check generated no output?

8m 36s

Subsystem
Report/Notes

Docker
ClientAPI=1.42 ServerAPI=1.42 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5483/11/artifact/out/Dockerfile

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

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

uname
Linux a6cf46ce767f 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 503f466cc46924848913821aeba89a59ac88089e

Default Java
Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5483/11/testReport/

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5483/11/console

versions
git=2.25.1 maven=3.6.3

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

This message was automatically generated.

[WARNING] 'build.plugins.plugin.version' for org.cyclonedx:cyclonedx-maven-plugin is missing. @ line 611, column 15
[ERROR] Unresolveable build extension: Plugin org.apache.felix:maven-bundle-plugin:2.5.0 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.felix:maven-bundle-plugin:jar:2.5.0 @
 @

It appears that the compilation failure is not related to this patch.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 46s

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.

+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 2 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
42m 10s

trunk passed

+1 :green_heart:
compile
0m 43s

trunk passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
0m 36s

trunk passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
checkstyle
0m 30s

trunk passed

+1 :green_heart:
mvnsite
0m 43s

trunk passed

+1 :green_heart:
javadoc
0m 48s

trunk passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 53s

trunk passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
spotbugs
1m 31s

trunk passed

+1 :green_heart:
shadedclient
23m 36s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 34s

the patch passed

+1 :green_heart:
compile
0m 38s

the patch passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
0m 38s

the patch passed

+1 :green_heart:
compile
0m 32s

the patch passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
javac
0m 32s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 16s

the patch passed

+1 :green_heart:
mvnsite
0m 35s

the patch passed

+1 :green_heart:
javadoc
0m 33s

the patch passed with JDK Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
0m 50s

the patch passed with JDK Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

+1 :green_heart:
spotbugs
1m 25s

the patch passed

+1 :green_heart:
shadedclient
23m 54s

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

_ Other Tests _

+1 :green_heart:
unit
21m 12s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 34s

The patch does not generate ASF License warnings.

124m 59s

Subsystem
Report/Notes

Docker
ClientAPI=1.42 ServerAPI=1.42 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5483/12/artifact/out/Dockerfile

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

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

uname
Linux 61fac2cdd00f 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 503f466cc46924848913821aeba89a59ac88089e

Default Java
Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.18+10-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u362-ga-0ubuntu1~20.04.1-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5483/12/testReport/

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

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

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5483/12/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

In case interested the reason for compilation failure was due to INFRA-24478
Something got screwed with the DNS


Seperate permission for Warehouse / Stocks

What I'm trying to achieve
Seperate permissions for resolving warehouse/stocks, as usually different teams in company are responsible for managing orders and stock / inventory
Describe a proposed solution
New permission
Other solutions I've tried and won't work
…
Screenshots or mockups

@maarcingebala  is there any docs about creating new permissions for saleor based on django permissions? It's kinda complicated and some additional info would be great

Unfortunately, there are no docs for that currently. To add new permission you have to:

Add a new enum (or extend existing one) in saleor/core/permissions.py. Permissions are grouped into enums for each Django app or specific models if it makes sense.
Make sure that your enum is added to PERMISSIONS_ENUMS in the same file.
Add the permission in class Meta of a related model
Generate new migrations and apply them to create permission in DB.

After discussion, we agreed we should introduce separate permission for warehouses (MANAGAE_WAREHOUSES). Not sure though if the Stock model should also have its own permission or use the warehouses permission.


What are the steps to install uWebsockets on Ubuntu 18.04?

Hi,
I am using uwebsocket for my project, but when I am installing it , sudo make install command is not working. So can anyone please mention the steps which i need to follow. I already install openSll and zlib .
Thanks

Make sure you're using node v9 or earlier, later versions of node does not support uws.

yes I am using node 12, what are steps to install uWebsockets and use then on socketcluster?


Simplify argparse serialization

This should allow for more consistent de/serialization and possibly fixes #1101

It's a nice idea and does exactly what it's supposed to. Unfortunately the commands it generates are very verbose:
[361] outputs/img-samples/000017.686688794.png: --model=stable-diffusion-1.4 --esrgan_bg_tile=400 --outdir=outputs/img-samples --save_intermediates=0 --threshold=0.0 --sampler_name=k_euler_a --conf=configs/ls-models.yaml --gfpgan_dir=./src/gfpgan --last_operation=generate --seed=686688794 --iterations=1 --facetool_strength=0.8 --host=<IP_ADDRESS> --strength=0.75 --perlin=0.0 --facetool=gfpgan --esrgan --port=9090 --width=512 --cfg_scale=7.5 --codeformer_fidelity=0.75 --steps=50 --height=512 --gfpgan_model_path=experiments/pretrained_models/GFPGANv1.4.pth --precision=auto --variation_amount=0.0 --prompt='banana sushi' --restore

In addition, because of the way that I wrote args.py, you get a mixture of shell command switches (--model) and invoke  command (--prompt) so you can't actually feed the command back into the CLI and regenerate the image.
I'm afraid my preference is to stick with the hand-generated command line for now.


Reverse Proxy Serving up container app

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
I have setup yarp to proxy traffic to another appservice/container app.  Where I want to use yarp as reverse proxy/validate the user and if authorized allow the proxy to continue to https:// endpoint of the container app.
The user hits the proxy with Path https://localhost:44321/custom/{**catch-all}
I can catch with a route this first hit, however the container application then references another resources (such as js found at the root of the container app) and I see a hit on the proxy like https://localhost:44321/_dash-layout (NOTICE that now it is request the resource from the root path (without the /custom prefix) and so now it does not find a route to be proxied to.
How can I setup so that subsequent requests for resources also are matching a route?  (please keep in mind that I am proxying another application that references resources from root / and not using my /custom/{**catch-all} pattern
I would like to use YARP to proxy to a number of different container apps.

Unfortunately this path prefix pattern doesn't work well with proxies for exactly this reason, the destination doesn't know about the custom prefix when generating links. You're much better off routing based on host, port, etc. because links are implicitly relevant to the current host.
See some similar discussions:
https://github.com/microsoft/reverse-proxy/discussions/466
https://github.com/microsoft/reverse-proxy/issues/1460

Does this mean I have to host 1 proxy web app for each backend container I am hosting?
i.e. my proxy is https://myproxy and the container app is like https://mycontainer1
I could route based on host of myproxy but all would be directly to just one container.  Correct?
I was hoping I could host 1 proxy and through a path I could redirect to different destination containers? i.e. myproxy/app1 would go to https://mycontainer1 and myproxy/app2 would go to https://mycontainer2

If using host names, it would go something like this:

Your apps would have urls app1.xxx.yy and app2.xxx.yy
You would have DNS resolve both of these names to map to your proxy server.

It can use the same IP address/port for the two names.

At the back end, they could be distributed how you want

using 1 server / 1 port with something like IIS/http.sys mapping the apps
using 1 server, different ports for each app
using multiple back end servers

The proxy route would be configured using the hostname rather than a path extension. It can then route traffic to the appropriate destination based on the host name used the http request

As long as the apps only adjust the path as part of the urls they use, they will happily coexist with this pattern.

If you have a large number of backend containers or are planning to expand the number, then you can also consider a single DNS record for *.xxx.yy which also simplifies cert management (with a corresponding, single *.xxx.yy wildcard cert to monitor/manage).
That way, adding a new app is only an update to the Route/Cluster config.


Parser Deprecation warning during autocorrect

Be clear, concise and precise in your description of the problem.
Open an issue with a descriptive title and a summary in grammatically correct,
complete sentences.
Use the template below when reporting bugs. Please, make sure that
you're running the latest stable RuboCop and that the problem you're reporting
hasn't been reported (and potentially fixed) already.
Before filing the ticket you should replace all text above the horizontal
rule with your own words.

Expected behavior
No warnings unrelated to the rubocop output, particularly to stderr.
Actual behavior
running rubocop -a emits a warning to stderr saying
rubocop -a
Inspecting 737 files
Parser::Source::Rewriter is deprecated.
Please update your code to use Parser::Source::TreeRewriter instead
..........

Some tooling interpret the presence of output on stderr as an error and then fail.
RuboCop version
Include the output of rubocop -V. Here's an example:
$ rubocop -V
0.52.1 (using Parser <IP_ADDRESS>, running on ruby 2.2.8 x86_64-darwin16)

This issue appears to be resolved by https://github.com/bbatsov/rubocop/pull/5575

See #5611

It has been fixed. Thank you!


[Feature Request] VSCode Plugin

It would be a huge DX improvement if there was a VSCode extension that decrypted the .env file when you're viewing it
I see this: https://github.com/vinnymac/dotenvx-decrypt-vscode which is great, but it's "unofficial" which always makes me hesitate as I have to trust an additional author

we eventually will but it's further down our list of priorities currently.
@vinnymac is an honest guy and solid programmer. i would personally trust his plugin right now. he's participated in discussions here on dotenvx.


test: IRQ_PIC incomplete

[ ] Missing new test system (test.py)
[x] Does not compile
[ ] Not automated

We don't use PIC anymore, so either remove the test (technical debt) or update it (but never run the test, because why would we?)

Test is removed


Magic Connect Demo - log in dialog never loads

✅ Prerequisites

[x] Did you perform a cursory search of open issues? Is this bug already reported elsewhere?
[x] Are you running the latest SDK version?
[x] Are you reporting to the correct repository (magic-sdk)?

🐛 Description
The Log in link on Connect demo sandbox shows an empty dialog without any buttons.
The network tab in devtools suggests that there was an auth error.
I tried the login some weeks ago and it was working fine.
In network tab https://auth.magic.link/v1/session/refresh request fails with this:
{
data: {},
error_code: "auth_relayer/UNABLE_TO_REFRESH_SESSION",
message: "Unable to refresh user session. Please log in using the magic link flow to enable session persistence.",
status: "failed"
}

🧩 Steps to Reproduce

Follow the demo link from Connect docs
Press Log in button

🤔 Expected behavior
I should be able to see sign in options.
😮 Actual behavior
See empty dialog

💻 Code Sample
My fork with latest package versions https://codesandbox.io/s/magic-connect-demo-forked-z84ll6
🌎 Environment

Software
Version(s)

magic-sdk

Browser

yarn

Operating System

Hello @SpadarShut , thank you for reporting this. To fix this issue now in your forked codesandbox you will just need to update line 8 in App.tsx from network: "rinkeby", to network: "goerli",. We will update our demo today. Thanks again for pointing this out!


FFImageLoading Xamarin.Forms sample for .Net Standard 2.0

Would be please possible to add a sample Xamarin.Forms project (IoS, Droid, UWP) for VS 2017, where FFImageLoading is used from a .NetStandard 2.x library ?
Thx for help.

FFImageLoading supports .NET Standard  >= 1.0 - just be sure you install all packages (There are some informations, that Visual Studio doesn't install it sometimes, but that's not an FFImageLoading issue). You don't need to do anything else.


snowflake - uppercase model names?

This is a little confusing for new dbt users on snowflake. @cmcarthur should we default to uppercase model names? Or is uppercasing model names sufficient in your opinion?

Per my conversation with one of Snowflake's sales engineer today, here's what I learned:

if you create table/view with double-quotes, then one must use double-quotes when referencing the table/view during its query.
if you create table/view without double-quotes, Snowflake will automatically transform the name to upper-case.  However, one can still query against the table/view using lower-case (even thought Snowflake's UI describes it as upper-case).

My current conclusion, Snowflake is case insensitive unless you make it explicit with double-quotes.

this is fixed in 0.10.1 with quoting config settings. Closing!


Investigate using batch operations in the verifier

See https://docs.aws.amazon.com/AmazonS3/latest/dev/batch-ops-examples-java.html

Given we already make 1 request per object in the verifier to GetObject, we might bite the bullet and accept a separate PutObjectTagging call for each object – but this might be useful for backfilling tags on existing objects.


Config file authorization system

Allows user to specify an authorization function with a standard signature. Two example auth functions are provided. The new auth system is hooked up to the GET /rawscheduler endpoint.

This looks ready to go, though there are a few comments that said things would be fixed but were not. Is there a missing commit?


Memory leak with WeakReferences

Hello,
You have memory leak in the bsh.classpath. ClassManagerImpl. public
void addListener( Listener l ) { at
listeners.addElement( new WeakReference( l, refQueue) );
Checked with JProfiler in NetBeans.
Objects are added to listeners collection but are never removed, in
short time (with massive code execution – test stress framework) it
causes Java Heap Out of Space.
Tested with  Java 1.6
Also bsh.Name and java.util.Hashtable$Entry are massively used just
like native String class!
The line in code are NameSpace.getNameResolver for java.util.Hashtable
And BSHAmbiguousName. getName for bsh.Name
You should try to tweak its memory usage, since I execute the same
code and it is not complicated, but memory foot print is huge.
Bye!
Reported by: *anonymous
Original Ticket: beanshell/bugs/329

https://github.com/beanshell/beanshell/blob/41352867a2698223d933b13a19d76f5d292cf3a6/src/test/java/bsh/SourceForgeIssuesTest.java#L87-L99
Closed: fixed


Replace get_lhs and get_rhs with something more appropriate

I just realized the obvious when thinking about dynamic analyses. We have to rename the commands how the local matrices are assembled. Here is a short memo

Eigenvalue analysis
Modal analysis
Damping matrix?
Explicit Euler
Newmark https://en.wikipedia.org/wiki/Newmark-beta_method
HHT (Hilber-Hughes-Taylor) http://opensees.berkeley.edu/wiki/index.php/Hilber-Hughes-Taylor_Method
BDF
Crank-Nicholson method
Backward Differences Formula (BDF) https://en.wikipedia.org/wiki/Backward_differentiation_formula
Bossak
Generalized alpha-method http://opensees.berkeley.edu/wiki/index.php/Generalized_Alpha_Method
Linear multistep methods https://en.wikipedia.org/wiki/Linear_multistep_method
Energy-momentum methods (EMM)
Generalized energy-momentum method (GEMM)

The thing is that while technically we are finally always solving linear system of equations, i.e. Ax=b, which has left hand side and right hand side, in implicit methods the same global matrix (mass matrix for instance) can be in both sides of equation. In multistep methods (like BDF2) earlier solutions are used to stabilize the next solution and again depending on the order of method they can be on left of right side. While there is always some kind of fundamental Ax=b with LHS and RHS, it depends heavily from solution algorithm what actually is on left and and what is in right side.
So while this a(u,v) = l(v) canonical form works for some set of problems very well it's not general enough. Any suggestions for better naming convention, @JuliaFEM/owners ? It's not a big job to change this in this point of development but later on it definitely will be so the changes must be done immediately.

What first comes to mind is to have something like

get_stiffness_matrix
get_mass_matrix
get_damping_matrix
get_force_vector

which would work for linear systems (Mu'' + Ku = f) well, but I suspect this is causing some headaches with non-linear systems, where the equation is more like Mu'' = f(u), where f(u) contains (at least) internal forces f_int(u) and external forces f_ext(u). And depending from problem type, some interface forces like f_contact(u) etc. If we are using automatic differentiation then we don't have to take care of linearizing f(u) to tangent stiffness but of course it should still be possible.
Yet another source of confusion would be Dirichlet boundary conditions (and contact boundary conditions for instance) which contribute to both sides. Technically the lhs is mass matrix like thing without anything or very little to do with mass.
Anyway it should be now very obvious that calling get_lhs and get_rhs is way too straightforward approach to ask for a local element matrices.

After thinking a bit we could start from virtual work or residual vector, and get_lhs and get_rhs are more like low level function calls, which are used internally but can be defined also by user.

Now we have

get_mass_matrix
get_stiffness_matrix
get_force_vector

for a "traditional approach", which is activated using has_mass_matrix, has_stiffness_matrix and has_force_vector set true for equation. Furthermore, we have

get_residual_vector and has_residual_vector if only residual force vector is known and ForwardDiffhandles automatic differentiation of jacobian. This situation arises when equations are derived using principle of virtual work.

-get_potential_energy and has_potential_energy if only potential energy of system is known and ForwardDiff handles automatic differentiation of hessian + gradient of equation. This situation arises when equations are derived using principle of minimum potential energy.
Finally, we have calculate_local_assembly! which can be overridden by user defined function if nothing above doesn't fit for needs. This for example allows to access problem (=larger set of equations) if element needs to interact with other elements, which is the case in interface problems (fluid-structure-interaction, contact mechanics, ...)


fc varint unpacking out of bound check

fix #7378
Change Description
out of bound check for unpacking fc::signed_int and fc::unsigned_int. add test cases
Consensus Changes
N/A
API Changes
N/A
Documentation Additions
N/A

You'll need to merge in changes from develop too. Looks like you're using older build scripts that don't install c++ properly and allow it to build on our new base images.

Please submit the changes to fc in a PR to that repo so that it can be integrated into the master branch there and then pulled into this submodule.
In addition, please place the new test cases into their own test module, perhaps test_io_raw.cpp and follow the pattern(s) established in the other test modules so that it is logically easier to find test cases related to certain systems.

Sure. Would you check https://github.com/EOSIO/fc/pull/99?

@taokayan @b1bart This is so old, I'm presuming that we should start again, rather than keeping this hanging around.


navigation in a collection with remote or keyboard

Hi, is it possible to navigate in collection items with a keyboard. Scroll up and down and validate the selected item?

at the moment this is not possible but we have it on our roadmap.

Glad its on the roadmap.!


Update translations

Failures like

They were moved from base-ui to compose-material in https://github.com/google/horologist/pull/1343


updated to EF5, moved failing namespace, bumped framework

Hi Michael.
Your project is great, but i wanted to use it with EFCore 5. The issue is that they moved a namespace and deleted the obsolete DBQuery. I've Moved them and updated EF in this pull

Great.
Did you see that project is not compiling?

I added support as my own code because this one was not compiling.


Only load tests under tests/mocha/

Fixes https://github.com/meteor-velocity/velocity/issues/173

Thanks @Sanjo !


⚠ ClamAV has degraded performance

In 38cf024, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 92 ms

Resolved: ClamAV performance has improved in 5d56cdd after 5 minutes.


Top3 pc veg

This runs if and only if points are removed from latlong.csv
397, 587, and 845, for which there are no point counts and which are too loud for ARUs
We can merge this, and I will concurrently upload an edited version of latlong.csv to
Resilience Data Drive/acoustic/data_ingest/input/latlong.csv

I ran the model and it converged.


egypt time is wrong

it's right, the app doesn't support Summer Timezones and differences, egypt is GMT+2 normally but now it's GMT+3, if u want the correct time, change Timezone setting to manual and edit to Europe/Istanbul until summer-time difference is over.


Calling a new transition from inside a lifecycle method

If I want to decide between two transitions on entering a state, I am unable to call a transition from inside any lifecycle event. Say I have a very simple FSM with 3 states: A, B, and C. There is a transition A->B called step1() and another transition B->C called step2(). Say I only want to print hello when we get to B then call step2(). How would this be achieved? If I write an onEnterB or onAfterStep1 function, I get an error saying that a new transition cannot be called while the old one is still in effect.

You can't transition while in a transition.
What i do is pass an object as a param, and the current transition sets a
'nextTransition' value in it, which i feed back to the state machine after
the first transition is over.
On 9 Nov 2017 0:19, "Reuben Abraham"<EMAIL_ADDRESS>wrote:

If I want to decide between two transitions on entering a state, I am
unable to call a transition from inside any lifecycle event. Say I have a
very simple FSM with 3 states: A, B, and C. There is a transition A->B
called step1() and another transition B->C called step2(). Say I only want
to print hello when we get to B then call step2(). How would this be
achieved? If I write an onEnterB or onAfterStep1 function, I get an error
saying that a new transition cannot be called while the old one is still in
effect.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jakesgordon/javascript-state-machine/issues/143, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACE68CjEmCed4ebsAwRRypxU94Ll9cTvks5s0ikAgaJpZM4QXIcP
.

Pretty much any event system will choke if you try to invoke an event within an event.
The typical solution is to back out to the event loop (let the current event complete) before invoking the internal event.  You can do this with either a custom event, or a timeout.
A 0 length timeout is the easiest:
setTimeout(function() {
  fsm.newState() } , 0
)}

I've been doing process.nextTick(() => transition()) and it seems to be working fine.

Even though that the workaround will do it`s job, if before the execution of process.nextTick you go for some reason into another transition you will have a race condition and undefined state in the end.
For example A(init) -> calls (B) -> process.nextTick to (C)
still on same tick but another piece of the code checks
if Current State (B) -> move to (D)
That move to D should fail because you are already scheduled async transition to (C), but there is no way for the fsm to know this. Ideally you want to replicate the lock mechanism...

Got multiple state transitions working async.
Could just be my ignorance but it doesn't seem like it would be too crazy to support in the library
const fsm = new StateMachine({
      init: "init",
      transitions: [
        { name: "step", from: "init", to: "dbWrite" },
        { name: "step", from: "dbWrite", to: "submitTo311" },
        { name: "step", from: "submitTo311", to: "imageUpload" },
        { name: "step", from: "imageUpload", to: "success" }
      ],
      methods: {
        onTransition: lifecycle => this.onTransition(lifecycle),
        onDbWrite: () =>
          this.onDbWrite().then(() => setTimeout(() => this.fsm.step(), 0)),
        onSubmitTo311: () =>
          this.onSubmitTo311().then(() => setTimeout(() => this.fsm.step(), 0)),
        onImageUpload: () =>
          this.onImageUpload().then(() => setTimeout(() => this.fsm.step(), 0)),
        onSuccess: () => this.onSuccess()
      }
    });

Update 11-7-2018
Reads even cleaner with async / await
const fsm = new StateMachine({
      init: "init",
      transitions: [
        { name: "step", from: "init", to: "dbWrite" },
        { name: "step", from: "dbWrite", to: "submitToApi" },
        { name: "step", from: "submitToApi", to: "imageUpload" },
        { name: "step", from: "imageUpload", to: "success" }
      ],
      methods: {
        onDbWrite: async () => {
          await this.onDbWrite();
          setTimeout(() => this.fsm.step(), 0);
        },
        onSubmitToApi: async () => {
          await this.onSubmitTo311Api();
          setTimeout(() => this.fsm.step(), 0);
        },
        onImageUpload: async () => {
          await this.onImageUpload();
          setTimeout(() => this.fsm.step(), 0);
        },
        onSuccess: async () => {
          await this.onSuccess();
        }
      }
    });

Got multiple state transitions working async.
Could just be my ignorance but it doesn't seem like it would be too crazy to support in the library
const fsm = new StateMachine({
      init: "init",
      transitions: [
        { name: "step", from: "init", to: "dbWrite" },
        { name: "step", from: "dbWrite", to: "submitToApi" },
        { name: "step", from: "submitToApi", to: "imageUpload" },
        { name: "step", from: "imageUpload", to: "success" }
      ],
      methods: {
        onTransition: lifecycle => this.onTransition(lifecycle),
        onDbWrite: () =>
          this.onDbWrite().then(() => setTimeout(() => this.fsm.step(), 0)),
        onSubmitToApi: () =>
          this.onSubmitToApi().then(() => setTimeout(() => this.fsm.step(), 0)),
        onImageUpload: () =>
          this.onImageUpload().then(() => setTimeout(() => this.fsm.step(), 0)),
        onSuccess: () => this.onSuccess()
      }
    });

My fsm lives inside of a class with member functions that are async await or return promises.
Seems like a really neat way of implementing lifecycle hooks

Will this approach have any other effects or disadvantages?

Hi,
I could solve this problem calling the transtition inside the method writing:
setTimeout(() => fsm.step(),0);
If I wrote setTimeout(fsm.step(),0) I get the error. I don´t know the difference, but using => solves the problem.

Maybe creator of the lib can provide example how to make state machine which changes its state from first to last (without setTimeout) when previous transition is finished? A -> B -> C. I guess this is pretty often case.

Maybe creator of the lib can provide example how to make state machine which changes its state from first to last (without setTimeout) when previous transition is finished? A -> B -> C. I guess this is pretty often case.


Use assertEqual instead of deprecated assertEquals

Fixes warnings when running tests of the form:
DeprecationWarning: Please use assertEqual instead.

Codecov Report

Merging #1220 into develop will decrease coverage by 0.04%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop    #1220      +/-   ##
===========================================
- Coverage    98.05%   98.01%   -0.05%
===========================================
  Files           45       45
  Lines         7306     7306
===========================================
- Hits          7164     7161       -3
- Misses         142      145       +3

Impacted Files
Coverage Δ

botocore/credentials.py
97.73% <0%> (-0.57%)
:arrow_down:

Continue to review full report at Codecov.

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

Thanks!


EPIX West channel was removed that still exists

Source
https://tvpassport.com
Channels
<channel id="EpixWest.us"><display-name>Epix West</display-name><icon src="https://upload.wikimedia.org/wikipedia/commons/thumb/8/83/Epix_Logo_2019.svg/512px-Epix_Logo_2019.svg.png"/><url>https://tvpassport.com</url></channel>

Notes
Since the EPIX  thread "Update directv.com_us.channels.xml #1264" is closed I want to mention that EPIX West/Pacific still broadcasts.
At TVPassport:
epix--pacific/13443
I watch both EPIX East and West.

The channel has been returned to the list:
https://github.com/iptv-org/epg/blob/1d10a1df2e548d1c0d3c82a6f0283615f60b927a/sites/tvpassport.com/tvpassport.com_us.channels.xml#L17


Fix Splunk Streaming Command dict_reader.py attempts to iterate over none

Close #110
Fix provided by @David-Noble-at-work

Thanks for doing this work @kkirsche, can you please make a PR against the develop branch?

@shakeelmohamed @David-Noble-at-work  seems you have the fix in Develop and have since August 11, 2014. Any reason you don't have it in your master branch then....?

@kkirsche Ah, thanks for pointing that out. We will have a new release out the door shortly :)

No worries @shakeelmohamed. It's just very concerning in regards to development process that it's been there a year and it isn't in your master branch. Your master has newer files than develop which signals to me a red flag that it isn't being used fully as a develop branch :\
cc: @David-Noble-at-work @glennblock

@kkirsche for some reason, that commit from Nov 24 is literally the only one missing from master that is in develop from that timeframe. For some reason it looks like it didn't get merged over when we did a release in March. We will get to the bottom of why that happened, but apologies for the problem it caused.
We do use develop exclusively for development, and no changes are made to master directly that are not documentation changes like the contribution guidelines, etc.

@itay I'm not so sure I can believe you with regards to that anymore — You also don't have your format function for your Set validator from 9 months ago when your last release was after that. These types of lapses in master that exist in develop so long ago raise large concerns for me.
cc: @glennblock

@kkirsche I did get to the bottom off it. When Python 2.7.9 came out, we did a hotfix release that just updated support for it. It did not include any of the fixes we had pending in develop, which is why you're seeing a case where there are some fixes in develop that are not in master, but master also has some "newer" commits.
You are right that we haven't done a new full Python SDK release in quite a while - we were focused on a few other things. However, we're prepping one now that should be out in the next few weeks.

Thank makes sense. I guess my frustration is that in the current state I consider the SDK broken and in need of a hot fix to bring it to where it was supposed to be even if it's not a feature release. I understand the focus elsewhere it just leaves me wondering where the SDK lies if you don't plan to bring master to parity until "a few weeks"


[WIP] Feature - Add task detail page

The route looks like this now:
#/services/[serviceID]/task-detail/[taskID]/

I've put in an additional rudimentary 'Marathon Task Configuration' that shows up below the Mesos task information. Extending this Marathon information is a huge task, that should be done outside of this PR. Also I think it needs a refinement together with @leemunroe at some point, how to merge Mesos and Marathon task information.

I've adjusted the ServiceBreadcrumbs to be able to display and route the task id. But the ServiceBreadcrumbs are not generic right now, so I disabled them in the 'Node' task view, which is actually the same. @pierlo-upitup

The status (Running, Finished, etc) in the PageHeader isn't shown up emphazied, even though it is set as emphasize. This is a Canvas UI definition, that I am not meant to influence. If Canvas UI changes the emphazise setting, this status line will follow automatically, because the 'emphasize' is set.

The code container in the logs view needs some adjustment, so the "Go to bottom" button isn't shown up accidentally. But this is a Reactjs-components fix. This PR is not responsible for it.

Without the help of @kennyt and @mlunoe I would have been screwed up.

Reviewer: @MatApple

Awesome work!!! Still reviewing but this is really great progress.
I noticed two minor UX issues 👓 :

By default the Details tab is selected (which is fine) however the tab is the 2nd in order. We should probably rearrange them.

The log viewer shows the "Go To Bottom" button even when there is no need for it (the log itself is shorter than the textarea). The button should not be shown unless we are scrolling away from the bottom. If this is a known bug in DC/OS and it wasn't introduced by this PR then I'm fine with solving it in a separate one.

Extremely good job! A few nitpicks/suggestion but it mostly works flawlessly. Thanks!

@pierlo-upitup You did an amazing, precise and helpful review job. Thanx a lot!
I will take care of all your comments.

@aldipower Nice work Felix. We discussed a lot of this in person but documenting it here. Mostly stylistic.

Is it important to differentiate Mesos details from Marathon details with a heading or could these all be combined? I'm not quite clear on the differences and if users expect them to be called out as different groups of information
The icon, heading and state positioning should be consistent throughout so when I go from Service detail to Task detail there isn't a jump in alignment
For the list of key:value details it feels like the key column is very wide in most cases and could be narrower
I think "Log Viewer" could just be "Logs"
There is some odd styling left on the log container e.g. white border
The margin between the tabs and search bar, then between the search bar and logs container, looks different, I would suggest keeping these consistent
Add a tooltip to the download button so it is clear what it does
Ensure long values are wrapped and don't introduce a horizontal scrollbar

@leemunroe I've captured the comments not addressed in the PR in a separate Jira for later.

Let's please make sure, that we (re)implement all the integration test (https://github.com/dcos/dcos-ui/blob/f39b03810d4ea57588d939ff2bf5b8750a9b9d08/tests/pages/services/TaskSidePanel-cy.js) to ensure the task detail page is properly working.

Obviously those can't exactly be re-implemented, but I can certainly implement some more tests if we want to keep the numbers up.

Last two rebase attempts on this branch were unsuccessful, but I have at least pushed some new tests.

🚢

Seems like one of the refactorings broke the layout. 😖

phew Rebasing fixed the layout issue

FWIW the layout issue was addressed in my comment here: https://github.com/dcos/dcos-ui/pull/118/commits/ae12976ba489ecf2577627f14e56dce4d4cb04e8#r63559757
Looks like it was overly terse, will elaborate more next time.

🚀


Add back minimal amounts of the cookicutter to get make dev working

For:

https://github.com/hypothesis/report/issues/84

This project doesn't need the supervisor conf, as at the moment it doesn't run anything useful. I think there was an idea to have it run Metabase and connect up to H and LMS etc, but we've not seen a practical reason to do it yet, as we develop in the real Metabase.
This doesn't do anything useful once it's running, but it does create the dev tox environment without spitting out any errors which might confuse people.
Technically the erroring version would create the environment too, but it's likely to trigger repeated investigations to see what's wrong by people so this seems tidier.

I think it might make sense if there was something better for us to run that didn't fit into the supervisor settings? At the moment we don't really have anything productive to put here.


Azure Sandbox Deployment Errors Resource Not Supported

Hi, I am having difficulties when trying to deploy the Sandbox environment to Azure via Business Central. I ran the template & parameters through the Azure RM Template Validation and receive the following.
arm | NotSupported |
-- | -- | --
--  azuredeploy.json | NotSupported | NotSupported: Resource type 'firewallrules' NotSupported: Resource type 'databases' NotSupported: Resource type 'databases'

Could you share some info on which template you use (aka.ms/???) and which selections you have done?

Hi Freddy,
I used the template (attached)  that is downloaded when you try to deploy an environment via the business central admin page.   As far as selections go I left it pretty well default. Using SQL Express, and allowing all IP to connect.
Josh
From: Freddy Kristiansen<EMAIL_ADDRESS>Sent: March 17, 2019 11:56 PM
To: Microsoft/navcontainerhelper<EMAIL_ADDRESS>Cc: Josh Fraser<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/navcontainerhelper] Azure Sandbox Deployment Errors Resource Not Supported (#383)
Could you share some info on which template you use (aka.ms/???) and which selections you have done?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/navcontainerhelper/issues/383#issuecomment-473761570, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AuWlKII43_R5DMzUcE1btXYkTC725F4bks5vXw5TgaJpZM4b3QKq.

Freddy,
The errors that I was getting lead me to believe it was something to do with the Azure SQL items in the JSON template.
From: Freddy Kristiansen<EMAIL_ADDRESS>Sent: March 17, 2019 11:56 PM
To: Microsoft/navcontainerhelper<EMAIL_ADDRESS>Cc: Josh Fraser<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/navcontainerhelper] Azure Sandbox Deployment Errors Resource Not Supported (#383)
Could you share some info on which template you use (aka.ms/???) and which selections you have done?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/navcontainerhelper/issues/383#issuecomment-473761570, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AuWlKII43_R5DMzUcE1btXYkTC725F4bks5vXw5TgaJpZM4b3QKq.

That specific piece of the template will only be included if you select Azure SQL and if you select Azure SQL you also need to specify bacpacs for app and tenant database.

See that’s what I thought too, but I know I specified to use SQL Server
From: Freddy Kristiansen<EMAIL_ADDRESS>Sent: March 18, 2019 5:00 PM
To: Microsoft/navcontainerhelper<EMAIL_ADDRESS>Cc: Josh Fraser<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/navcontainerhelper] Azure Sandbox Deployment Errors Resource Not Supported (#383)
That specific piece of the template will only be included if you select Azure SQL and if you select Azure SQL you also need to specify bacpacs for app and tenant database.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/navcontainerhelper/issues/383#issuecomment-474099046, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AuWlKKR5pYgAYBnlOXdj0wr4Uu_Vaq-Vks5vX_5pgaJpZM4b3QKq.

Not sure if this makes a difference but I’m logging into the BC environment using an @.onmicrosoft.com account and deploying to an Azure subscription with my @work.com account.
From: Freddy Kristiansen<EMAIL_ADDRESS>Sent: March 18, 2019 5:00 PM
To: Microsoft/navcontainerhelper<EMAIL_ADDRESS>Cc: Josh Fraser<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/navcontainerhelper] Azure Sandbox Deployment Errors Resource Not Supported (#383)
That specific piece of the template will only be included if you select Azure SQL and if you select Azure SQL you also need to specify bacpacs for app and tenant database.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/navcontainerhelper/issues/383#issuecomment-474099046, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AuWlKKR5pYgAYBnlOXdj0wr4Uu_Vaq-Vks5vX_5pgaJpZM4b3QKq.

I was able to get this working! Thanks for your help Freddy.
From: Freddy Kristiansen<EMAIL_ADDRESS>Sent: Monday, March 18, 2019 5:00 PM
To: Microsoft/navcontainerhelper<EMAIL_ADDRESS>Cc: Josh Fraser<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/navcontainerhelper] Azure Sandbox Deployment Errors Resource Not Supported (#383)
That specific piece of the template will only be included if you select Azure SQL and if you select Azure SQL you also need to specify bacpacs for app and tenant database.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/navcontainerhelper/issues/383#issuecomment-474099046, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AuWlKKR5pYgAYBnlOXdj0wr4Uu_Vaq-Vks5vX_5pgaJpZM4b3QKq.


Provide mechanism for transformers to validate parameters

 Issue by blois
Originally opened as dart-lang/sdk#20170

Angular's transformers need a complex chunk of code to read and validate transformer parameters from the pubspec.yaml file, and generates not-too-helpful errors-
https://github.com/angular/angular.dart/blob/master/lib/transformer.dart#L64
It would be great if this were provided by BarbackSettings and could give users much better error messages (with location in the pubspec file?)
Polymer has a very similar validation as well (and all of them are currently just printing errors).

 Comment by nex3

As we discussed in person, throwing errors rather than just printing them to stdout will cause them to be handled gracefully by pub and associated with the configuration being processed.
There's probably room here for a json_rpc_2-style API for easily validating the presence and type of values, though. See http://www.dartdocs.org/documentation/json_rpc_2/0.1.0/index.html#json_rpc_2/json_rpc_2.Parameters for example.


Price formatter

So the price format function for CoinList and CoinDetails will show very low values to 2 significant figures. Hope it's what you wanted!
But now prices of some of the lowest value coins can wrap vertically if the display is less than ~400px

Also changing minimumSignificantDigits to 1 instead of 2 will get rid of the trailing zeroes :)

Super appreciate it! Yeah, this is one of those simple ones I just slacked on going back to fix haha. I super appreciate the assistance and sorry you had to look at my very rough code!