Backport "HBASE-28879 Bump hbase-thirdparty to 4.1.9" to branch-2

#6295

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 45s

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.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 19s

branch-2 passed

+1 :green_heart:
compile
6m  9s

branch-2 passed

+1 :green_heart:
spotless
0m 47s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 12s

the patch passed

+1 :green_heart:
compile
8m  1s

the patch passed

-0 :warning:
javac
8m  1s
/results-compile-javac-root.txt
root generated 4 new + 1235 unchanged - 3 fixed = 1239 total (was 1238)

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
xmllint
0m  0s

No new issues.

+1 :green_heart:
hadoopcheck
22m 29s

Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6 3.4.0.

-1 :x:
spotless
0m 10s

patch has 36 errors when running spotless:check, run spotless:apply to fix.

_ Other Tests _

+1 :green_heart:
asflicense
0m 14s

The patch does not generate ASF License warnings.

48m 45s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6297

Optional Tests
dupname asflicense javac codespell detsecrets xmllint hadoopcheck spotless compile

uname
Linux d3b19cedb97a 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / f9aa21bea10460e6c4a7e7e49067a96ef438b434

Default Java
Eclipse Adoptium-11.0.23+9

spotless
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/1/artifact/yetus-general-check/output/patch-spotless.txt

Max. process+thread count
79 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/1/console

versions
git=2.34.1 maven=3.9.8 xmllint=20913

Powered by
Apache Yetus 0.15.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.

-0 :warning:
yetus
0m  6s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 14s

branch-2 passed

+1 :green_heart:
compile
2m 17s

branch-2 passed

+1 :green_heart:
javadoc
2m  2s

branch-2 passed

+1 :green_heart:
shadedjars
6m 20s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

-1 :x:
mvninstall
2m  5s
/patch-mvninstall-root.txt
root in the patch failed.

+1 :green_heart:
compile
2m 20s

the patch passed

+1 :green_heart:
javac
2m 20s

the patch passed

+1 :green_heart:
javadoc
1m 59s

the patch passed

+1 :green_heart:
shadedjars
6m 11s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
279m  9s
/patch-unit-root.txt
root in the patch failed.

312m 20s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/1/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6297

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 36c5dd792cd6 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / f9aa21bea10460e6c4a7e7e49067a96ef438b434

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/1/testReport/

Max. process+thread count
4708 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/1/console

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 44s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 17s

branch-2 passed

+1 :green_heart:
compile
2m 10s

branch-2 passed

+1 :green_heart:
javadoc
1m 50s

branch-2 passed

+1 :green_heart:
shadedjars
6m 11s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

-1 :x:
mvninstall
1m 46s
/patch-mvninstall-root.txt
root in the patch failed.

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

-0 :warning:
javac
0m 56s
/patch-compile-root.txt
root in the patch failed.

+1 :green_heart:
javadoc
1m 45s

the patch passed

+1 :green_heart:
shadedjars
6m  6s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
315m 16s
/patch-unit-root.txt
root in the patch failed.

347m 18s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6297

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux acba9d4ac82a 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / f9aa21bea10460e6c4a7e7e49067a96ef438b434

Default Java
Eclipse Adoptium-11.0.23+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/1/testReport/

Max. process+thread count
4901 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/1/console

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 56s

Docker mode activated.

-0 :warning:
yetus
0m  6s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
2m 34s

branch-2 passed

+1 :green_heart:
compile
1m 47s

branch-2 passed

+1 :green_heart:
javadoc
1m 41s

branch-2 passed

+1 :green_heart:
shadedjars
4m 51s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 52s

the patch passed

+1 :green_heart:
compile
2m 42s

the patch passed

+1 :green_heart:
javac
2m 42s

the patch passed

-0 :warning:
javadoc
2m 29s
/results-javadoc-javadoc-root.txt
root generated 9 new + 87 unchanged - 9 fixed = 96 total (was 96)

+1 :green_heart:
shadedjars
6m 48s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
446m 50s
/patch-unit-root.txt
root in the patch failed.

480m 44s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6297

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 09e36418b525 5.4.0-195-generic #215-Ubuntu SMP Fri Aug 2 18:28:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / f9aa21bea10460e6c4a7e7e49067a96ef438b434

Default Java
Temurin-1.8.0_412-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/1/testReport/

Max. process+thread count
4747 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.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.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
5m  2s

branch-2 passed

+1 :green_heart:
compile
10m  7s

branch-2 passed

+1 :green_heart:
spotless
1m 14s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 43s

the patch passed

+1 :green_heart:
compile
9m 47s

the patch passed

-0 :warning:
javac
9m 47s
/results-compile-javac-root.txt
root generated 4 new + 1235 unchanged - 3 fixed = 1239 total (was 1238)

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
xmllint
0m  0s

No new issues.

+1 :green_heart:
hadoopcheck
24m 29s

Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6 3.4.0.

-1 :x:
spotless
0m 11s

patch has 36 errors when running spotless:check, run spotless:apply to fix.

_ Other Tests _

+1 :green_heart:
asflicense
0m 19s

The patch does not generate ASF License warnings.

58m 35s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6297

Optional Tests
dupname asflicense javac codespell detsecrets xmllint hadoopcheck spotless compile

uname
Linux 0ed31143304f 5.4.0-195-generic #215-Ubuntu SMP Fri Aug 2 18:28:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ab032bcf98e172d3071aa403b5f3a3818c7eda17

Default Java
Eclipse Adoptium-11.0.23+9

spotless
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/2/artifact/yetus-general-check/output/patch-spotless.txt

Max. process+thread count
83 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/2/console

versions
git=2.34.1 maven=3.9.8 xmllint=20913

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  2s

Docker mode activated.

-0 :warning:
yetus
0m  6s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m  6s

branch-2 passed

+1 :green_heart:
compile
2m  3s

branch-2 passed

+1 :green_heart:
javadoc
1m 41s

branch-2 passed

+1 :green_heart:
shadedjars
4m 53s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 34s

the patch passed

+1 :green_heart:
compile
1m 48s

the patch passed

+1 :green_heart:
javac
1m 48s

the patch passed

+1 :green_heart:
javadoc
1m 38s

the patch passed

+1 :green_heart:
shadedjars
4m 53s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
36m 47s
/patch-unit-root.txt
root in the patch failed.

62m 52s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/2/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6297

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 2995db7ad473 5.4.0-195-generic #215-Ubuntu SMP Fri Aug 2 18:28:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ab032bcf98e172d3071aa403b5f3a3818c7eda17

Default Java
Temurin-1.8.0_412-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/2/testReport/

Max. process+thread count
2747 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/2/console

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 44s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 19s

branch-2 passed

+1 :green_heart:
compile
2m 13s

branch-2 passed

+1 :green_heart:
javadoc
1m 53s

branch-2 passed

+1 :green_heart:
shadedjars
6m  0s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m  9s

the patch passed

+1 :green_heart:
compile
2m 12s

the patch passed

+1 :green_heart:
javac
2m 12s

the patch passed

+1 :green_heart:
javadoc
1m 49s

the patch passed

+1 :green_heart:
shadedjars
5m 53s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
232m 31s
/patch-unit-root.txt
root in the patch failed.

264m 20s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/2/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6297

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 6a1d1383d8b5 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ab032bcf98e172d3071aa403b5f3a3818c7eda17

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/2/testReport/

Max. process+thread count
5094 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/2/console

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 55s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 25s

branch-2 passed

+1 :green_heart:
compile
3m 14s

branch-2 passed

+1 :green_heart:
javadoc
2m 19s

branch-2 passed

+1 :green_heart:
shadedjars
7m 12s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 58s

the patch passed

+1 :green_heart:
compile
3m  3s

the patch passed

+1 :green_heart:
javac
3m  3s

the patch passed

+1 :green_heart:
javadoc
2m  9s

the patch passed

+1 :green_heart:
shadedjars
7m 59s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
291m 21s
/patch-unit-root.txt
root in the patch failed.

331m 54s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6297

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 809d9c6694cc 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ab032bcf98e172d3071aa403b5f3a3818c7eda17

Default Java
Eclipse Adoptium-11.0.23+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/2/testReport/

Max. process+thread count
4904 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/2/console

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 48s

Docker mode activated.

-0 :warning:
yetus
0m  6s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m  4s

branch-2 passed

+1 :green_heart:
compile
2m 10s

branch-2 passed

+1 :green_heart:
javadoc
2m  4s

branch-2 passed

+1 :green_heart:
shadedjars
5m 27s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m  2s

the patch passed

+1 :green_heart:
compile
2m 11s

the patch passed

+1 :green_heart:
javac
2m 11s

the patch passed

+1 :green_heart:
javadoc
1m 59s

the patch passed

+1 :green_heart:
shadedjars
5m 31s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
289m 55s

root in the patch passed.

323m 15s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/3/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6297

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux cd592268d92f 5.4.0-195-generic #215-Ubuntu SMP Fri Aug 2 18:28:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 01ee47ec8cbd1057bbc1ebfb1562e04bf896be0e

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/3/testReport/

Max. process+thread count
8308 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/3/console

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 50s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

-1 :x:
mvninstall
0m 14s
/branch-mvninstall-root.txt
root in branch-2 failed.

+1 :green_heart:
compile
1m 55s

branch-2 passed

-0 :warning:
javadoc
0m 12s
/branch-javadoc-root.txt
root in branch-2 failed.

+1 :green_heart:
shadedjars
5m 21s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 26s

the patch passed

+1 :green_heart:
compile
1m 44s

the patch passed

+1 :green_heart:
javac
1m 44s

the patch passed

-0 :warning:
javadoc
1m 32s
/results-javadoc-javadoc-root.txt
root generated 96 new + 0 unchanged - 0 fixed = 96 total (was 0)

+1 :green_heart:
shadedjars
5m 14s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
357m 59s
/patch-unit-root.txt
root in the patch failed.

383m 41s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/3/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6297

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 99889cf09275 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 01ee47ec8cbd1057bbc1ebfb1562e04bf896be0e

Default Java
Temurin-1.8.0_412-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/3/testReport/

Max. process+thread count
4871 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/3/console

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 57s

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.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 35s

branch-2 passed

+1 :green_heart:
compile
8m 34s

branch-2 passed

+1 :green_heart:
spotless
0m 58s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 38s

the patch passed

+1 :green_heart:
compile
8m 22s

the patch passed

-0 :warning:
javac
8m 22s
/results-compile-javac-root.txt
root generated 4 new + 1236 unchanged - 3 fixed = 1240 total (was 1239)

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
xmllint
0m  0s

No new issues.

+1 :green_heart:
hadoopcheck
18m 11s

Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 57s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 14s

The patch does not generate ASF License warnings.

49m  7s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/4/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6297

Optional Tests
dupname asflicense javac codespell detsecrets xmllint hadoopcheck spotless compile

uname
Linux 11cdbc60a23a 5.4.0-195-generic #215-Ubuntu SMP Fri Aug 2 18:28:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / d683d65b84434455980e2fcfc9d91459deebaf2e

Default Java
Eclipse Adoptium-11.0.23+9

Max. process+thread count
80 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/4/console

versions
git=2.34.1 maven=3.9.8 xmllint=20913

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  2s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 24s

branch-2 passed

+1 :green_heart:
compile
3m 13s

branch-2 passed

+1 :green_heart:
javadoc
2m 50s

branch-2 passed

+1 :green_heart:
shadedjars
7m 32s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m  3s

the patch passed

+1 :green_heart:
compile
3m  5s

the patch passed

+1 :green_heart:
javac
3m  5s

the patch passed

+1 :green_heart:
javadoc
2m 26s

the patch passed

+1 :green_heart:
shadedjars
7m 17s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
261m 50s
/patch-unit-root.txt
root in the patch failed.

303m  3s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/4/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6297

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux e37b3d277991 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / d683d65b84434455980e2fcfc9d91459deebaf2e

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/4/testReport/

Max. process+thread count
5128 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/4/console

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 50s

Docker mode activated.

-0 :warning:
yetus
0m  6s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m  0s

branch-2 passed

+1 :green_heart:
compile
1m 42s

branch-2 passed

+1 :green_heart:
javadoc
1m 34s

branch-2 passed

+1 :green_heart:
shadedjars
5m 22s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 26s

the patch passed

+1 :green_heart:
compile
1m 45s

the patch passed

+1 :green_heart:
javac
1m 45s

the patch passed

+1 :green_heart:
javadoc
1m 32s

the patch passed

+1 :green_heart:
shadedjars
5m 17s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
412m 22s

root in the patch passed.

442m 42s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/4/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6297

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 6bd913237bd6 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / d683d65b84434455980e2fcfc9d91459deebaf2e

Default Java
Temurin-1.8.0_412-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/4/testReport/

Max. process+thread count
7886 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/4/console

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 53s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 47s

branch-2 passed

+1 :green_heart:
compile
2m 50s

branch-2 passed

+1 :green_heart:
javadoc
2m 21s

branch-2 passed

+1 :green_heart:
shadedjars
7m 33s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 17s

the patch passed

+1 :green_heart:
compile
2m 33s

the patch passed

+1 :green_heart:
javac
2m 33s

the patch passed

+1 :green_heart:
javadoc
2m 40s

the patch passed

+1 :green_heart:
shadedjars
7m 14s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
393m 58s
/patch-unit-root.txt
root in the patch failed.

479m 28s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/4/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6297

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux e6a222c20146 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / d683d65b84434455980e2fcfc9d91459deebaf2e

Default Java
Eclipse Adoptium-11.0.23+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/4/testReport/

Max. process+thread count
6978 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6297/4/console

versions
git=2.34.1 maven=3.9.8

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

This message was automatically generated.


Fix gh 629 healthcheck for loadbalancer

Fixes gh-629

Something has gone wrong during the rebase. I'm going to close this PR and submit a new one in order  to avoid messing up git log.


Kotlin DSL Failed to generate type-safe Gradle model accessors for Android plugin

I have precompiled script plugin which applies com.android.library plugin:
plugins {
    id("com.android.library")
    kotlin("android")
}

But static accessors are not available in this precompiled plugin, but work properly in a neighbor plugin which uses only kotlin("jvm").
I see this stack trace from task :buildSrc:generatePrecompiledScriptPluginAccessors
https://gist.github.com/gildor/23e0a1e32b2bb92167ef7cdf76884ca7
As you can see, it cannot find path to SDK, but I have sdk.dir in my local.properties file in root of the project, but apparently it tries to find it in some temporary project.
I tried to specify ANDROID_SDK_ROOT environment variable for
ANDROID_SDK_ROOT=path ./gradlew assembleDebug

But it also does not help.
Expected Behavior
type-safe accessors should be generated properly for precompiled plugin
Current Behavior
Accessors are not generated, I cannot use them in the precompiled plugin (neither android extension, or even dependency configurations, like implementation), but if I do not use them, build is successful, but I see exception from task :buildSrc:generatePrecompiledScriptPluginAccessors in logs
Your Environment
Gradle 5.4.1
Android Gradle Plugin 3.5.0-beta01

Not sure is it still an issue or not, I will check a bit later

I think this issue could be closed.
We are successfully using android plugin generated accessors in precompiled script plugin.

I think this issue could be closed.
We are successfully using android plugin generated accessors in precompiled script plugin.


Installation on Mac 10.14

Component
Other (please describe)
Have you ensured that all of these are up to date?

[X] Foundry
[ ] Foundryup

What version of Foundry are you on?
forge 0.2.0 (6130af7 2022-04-07T00:08:44.543037+00:00)
What command(s) is the bug in?
No response
Operating System
macOS (amd)
Describe the bug
This could be an issue with my specific machine (10.14 Mac), but on installation the PATH was lost after I closed the installation terminal session.  The installation script added the PATH to .bashrc, but I couldn't get the PATH to persist until I added it to .bash-profile. Now everything works as expected.

This is because of how certain distributions of Mac OS work with bash. Every terminal opened on mac is an interactive "login" shell. This means .bash_profile is run on every new terminal session (on other distributions, profile settings are loaded at first login only). Bash has an idiosyncrasy where it won't run .bashrc on login shells automatically, so you have to run it yourself.
Issue is not unique to foundry. I would suggest modifying your .bash_profile to load .bashrc. Or consider other shells :)  This stack exchange goes into much more detail on the behavior. It is definitely weird.

Closing because of above :point_up: Feel free to join https://t.me/foundry_support for more assistance


When running multilingual LUKE an error is reported

Hello, when I run multilingual LUKE, the following error is reported, how can I fix this bug?

It's the code:
`# Load the model checkpoint
#model_name = "studio-ousia/luke-base"
#model_name = 'studio-ousia/luke-large-finetuned-conll-2003'
model_name = "studio-ousia/mluke-base"
#model = LukeForEntitySpanClassification.from_pretrained(model_name)
model = LukeForEntitySpanClassification.from_pretrained(model_name)
model.eval()
model.to("cuda")
Load the tokenizer
#tokenizer = LukeTokenizer.from_pretrained(model_name)
tokenizer = MLukeTokenizer.from_pretrained(model_name)`
`text = "Beyoncé lives in Los Angeles"
List all possible entity spans in the text
word_start_positions = [0, 8, 14, 17, 21]  # character-based start positions of word tokens
word_end_positions = [7, 13, 16, 20, 28]  # character-based end positions of word tokens
entity_spans = []
for i, start_pos in enumerate(word_start_positions):
for end_pos in word_end_positions[i:]:
entity_spans.append((start_pos, end_pos))
inputs = tokenizer(text, entity_spans=entity_spans, return_tensors="pt").to("cuda")
outputs = model(**inputs)
logits = outputs.logits
predicted_class_indices = logits.argmax(-1).squeeze().tolist()
for span, predicted_class_idx in zip(entity_spans, predicted_class_indices):
if predicted_class_idx != 0:
print(text[span[0] : span[1]], model.config.id2label[predicted_class_idx])`

Hi, our code has not supported using mLUKE for downstream tasks.
We will release example code of using mLUKE for downstream tasks including NER, and also will look into this use case, so please wait for a while.


Switch tab page cause previous tab page reload on Xamarin.Forms Android

I have a project and I use bottomtabbedpage-xamarin-forms plug-in in my project.
I use Xamarin.Forms Version <IP_ADDRESS>0555.
It is fine.
But if I update grade Xamarin.Forms to higher version, I got an problem.
The problem is if I switch tab page then switch back to previous tab page.
The previous tab page would reload.
For example, I switch to page3 from page1, and then switch back to page1.
Page1 would reload.
I tried <IP_ADDRESS>1731 got the same result.
My test project
I don't if this caused by bottomtabbedpage-xamarin-forms or by Xamarin.Forms.
Thanks.

Hi,
I just create a page(Page1) with scroll view and put about 10 labels in the scroll view.
And I put Page1 to MainPage which is set 5 tabbed page.
I don't load any data and not use any kind of MVVM framework.
Thanks.


Update installation.md

Use new version of expo cli

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

thanks for the contribution 😎


Allows for more flexible forecasting

This PR improves our ability to forecast incidents and show historical accuracy. It attempts to get the best of both worlds by doing a forward-looking forecast to see how many incidents will be handled in the future, as well as "rolling historical forecasts". By restricting the data sets in the past we are able to re-forecast a historical month as if it were the last day of the previous month.
We are then able to use that forecast to compare against the actual number of incidents in a given month. Combining these two strategies allows us to both observe the historical accuracy of our forecasting while using all currently available data for future forecasting.
Additionally, this PR adds the ability for us to forecast based on different subsets of data, e.g. how many incidents of type foo do we expect to see? how many incidents of priority bar, how many incidents of type foo AND priority bar and so on.
See also #923
@snkilmartin I had to remove the box cot fit to the model due to it having issues with the smaller filtered datasets, in my tests I didn't see that this had any effect. Please let me know if this will greatly affect forecasting.

I reviewed our internal data with box_cox and without, and the forecast is a bit more stable without the transform so I'm fine with this change. Thanks for making all these updates; this was a much bigger change that I realized!

Thanks for the review @snkilmartin and @mvilanova !


Site not detecting Figma

I used the app and have Figma v 97.7 installed, but the site did not detect it.
I opened figma and did a re-login and tested again with the app open, but still without success.
Tested on Windows 10

Can you please check if your browser can open figma:// links?
You may invoke document.location.replace or just create an HTML link and click on it.

Yes, this works. For example, I created figma://test and this opnened figma. I can also verify this by using figmas "login via browser" option: This also creates a figma link and opens it.

Got it, thanks. What browsers did you try?

When I reported this, only Chrome 92 (Chrome Dev version if that makes a difference)
Tried it right now with Firefox and MS Edge and it worked in both cases.
I also just noticed the same thing for Postman -> Works in Firefox and Edge, not in chrome.

The accuracy can be low because of:

Custom browser settings or flags - The demo was designed for the default setup, but that doesn’t mean your custom setup is not vulnerable.
Poorly performant hardware (including virtual machines) - Some timings are just hardcoded and were tested on the MacBook hardware.
Fullscreen mode - The demo will work faster and more accurate if the browser is not in a fullscreen mode
Slow internet connection
Gestures during the process

I also made a special branch for Chromium (Chrome, Brave, Edge, etc.) that works much slower, but should be more accurate.
https://609d9f4d79c4f6000700782c--boring-visvesvaraya-dbefd4.netlify.app/
It still may not work for your browser with a custom configuration. Like downloading PDFs instead of opening it.

may be related with #17


Document Localization Extensibility

Copy of #8867
Explain the extensibility points in localization APIs, including:
- Create a custom RequestCultureProvider.
- Create a custom StringLocalizer.
/cc @Rick-Anderson @ryanbrandenburg

@hishamco did you want this in docs.microsoft.com/en-us/aspnet/core/fundamentals/localization ?
Can you provide code samples for those?

Yep they should go there, by adding a new section after PO Localization section
Can you provide code samples for those?
I already have many sample such as My.Extensions.Localization.Json, My.AspNetCore.Localization.Json, My.AspNetCore.Localization.Session

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

ID: d1833676-ff1b-c587-cc9c-81afffa8ef68
Version Independent ID: ad989395-3f49-4d55-521e-cf6fe56281ee
Content: Globalization and localization in ASP.NET Core
Content Source: aspnetcore/fundamentals/localization.md
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

CC @eriawan in case you're interested in helping out on this one.

@Rick-Anderson I'm interested on this one

@Rick-Anderson
Yes, I'd love to work on this one, but I think I will finish the client side (user agent) culture handling article first.
I'll wait for @hishamco to do the Document Localization Extensibility first 🙂

No problem we can work together on this :smile:

@hishamco thanks! 👍

Abstract

Describe localization extensibility
Describe the extensibility points in request culture provider in ASP.NET Core (with sample code)
Describe the extensibility points in underlying provider for localization resources in ASP.NET Core (with sample code)

Items to track

[ ] Introduction to localization extensibility
[ ] Create custom RequestCultureProvider with sample code
[ ] Create custom StringLocalizer with sample code

Please if there 's anything need to be added let me know /cc @Rick-Anderson @ryanbrandenburg also hope to here from the community folks @damienbod @Bartmax

How dose IStringLocalizer chooses which types are localized?

This is valuable stuff, but I really don't want talk about implementing your own RequestCultureProvider and IStringLocalizer included on the main Localization doc page as the document details here seem to imply. That page is already massive and covers a ton of topics, including something as advanced and niche as writing your own extensibility is likely to cause more confusion than it solves.
If we're thinking of this as a separate page or blog post then I have no problems.

If we're thinking of this as a separate page or blog post then I have no problems.

Or create it as a discussion issue. I'd be happy to edit/help.

@lucaGabi I think you need to check the README.md file of the localization repo which contains examples for both custom RequestCultureProvider and IStringLocalizer

This is valuable stuff, but I really don't want talk about implementing your own RequestCultureProvider and IStringLocalizer included on the main Localization doc page as the document details here seem to imply.

My intend is to separate this into another page, which I think don't have any problem with you 😄

Having recently written (and continuing to maintain) a reasonably comprehensive piece of request localization middleware that extends the framework's native tools I would be very interested to read docs on this topic!

I think it's the time to start to finalize this ..

guys, I'm sorry I could not finish this sooner.
big apologize...
I'm quite busy this last 4 months with main jobs.
@hishamco I would like to help you to test the doc you have submitted as PR

@eriwan I'd like to help you on you in your other PR if you submitted 😊

@Rick-Anderson this is takes so long because my ankle was broken since 3-4 months ago, hope to push some updates ASAP

@hishamco  sorry to hear that. Hope you're feeling better. No hurry.

Thanks Rick .. hope to work on this in the next few days ..


Audit Logs guidance on Power Platform

It's not clear from this documentation where to find this configuration (e.g.- what is the landing page to get to these settings).  With the multiple admin portals integrated for Power Platform alongside dynamics, some of this is buried in Dynamics while some if exposed through Power Platform admin center.  I can't see how to get to this configuration based on a simple Power Platforms configurations with CDS.  There needs to be better guidance on which UI you need to go through to get to these settings.

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

ID: 97f28a46-531e-d373-40ad-f9e81b55fdf3
Version Independent ID: a47230d1-92c1-28a3-2f2c-ada21450b1f2
Content: Enable and use Activity Logging - Power Platform
Content Source: power-platform/admin/enable-use-comprehensive-auditing.md
Service: power-platform
GitHub Login: @jimholtz
Microsoft Alias: jimholtz

@breakpoint7
Thanks for the feedback. We are working to consolidate the various admin centers and settings locations. Can't provide an ETA but work is progressing.


Use with external CloudFront resource

Currently the main CloudFront resource is created & managed by the module itself.
While this is great as a quick setup for new users, it can become difficult for advanced use cases to integrate the module into an existing setup.
So we should switch to a similar approach as we did on the image optimizer module:

Create a managed CloudFront distribution by default (Quick setup)
Prevent creation of CloudFront distribution and export all configuration (Cache & Origin Policies), so that it can be integrated into an existing CloudFront Distribution

ToDo

[ ] Rework Custom Domain Example to use external CloudFront distribution

Thanks for introducing this feature! In my case I found that certain changes (ex: resource names) could recreate CF distribution and I have to update naming manually each time my pipeline runs. This decoupling helps to keep that constant.


Removing trailing slash

Versions

nuxt: v2.15.7
node: v14.17.0 LTS

Problem
Hi 👋
I have a problem, the trailing slash is simply removed from the url on the first load.
With further routing, the trailing slash is not removed.
Before load page:
http://localhost:3000/help/
After load page:
http://localhost:3000/help
Problem appeared after updating to version 2.15.7.
Version 2.15.6 does not have this problem.
I suspect this may be related to this PR

Same error

Please fix this issue :(

Released in v2.15.8


⚠ GLDDNS Server (ns2.glddns.com) has degraded performance

In 38da6e3, GLDDNS Server (ns2.glddns.com) (ns2.glddns.com) experienced degraded performance:

HTTP code: 200
Response time: 472 ms

Resolved: GLDDNS Server (ns2.glddns.com) performance has improved in 3d39fd4 after 9 minutes.


[Feature Request] Endpoint for jitsi tokenAuthUrl

Mattermost Version: 6.3
Plugin Version: 2.0.0
Describe the issue
There is no way to "login" as Host on an already existing jitsi room.
Additional context
Jitsi offers mechanism to ask to an authentication service for a JWT to connect to a room. As described here: https://github.com/jitsi/jitsi-meet/pull/728
The mechanism works as follow:

a user try to join some room on https://instance.jitsi/room where authentication is required to host a room, and the user is not identified
a popup shows, click on "I'm the host"
this redirects to some tokenAuthUrl, exemple https://instance.mattermost/plugins/jitsi/auth-callback?room={room}&roleUpgrade={roleUpgrade}, where {room} and {roleUpgrade} are replaced with the room's name and a flag set to false.
the auth-callback endpoint checks whether the user is identified (some other criterion could be used too, should anyone logged have the right to join any room?)
(if success) auth-callback redirects the user to https://instance.jitsi/room?jwt=valid_token
(if the user is not authenticated to mattermost) ask the user to login and then perform the redirection
otherwise, fails with an error message (or redirect back without a valid jwt)

Notice that the callback can be called with roleUpgrade=true, in that case, it shouldn't redirect back to the room, but only return the JWT. This seems to be used when a user asks for a promotion to moderator.

@givors-anabasis Should the MM server act as the JWT provider or another service?

@hanzei My thought was that when the MM jitsi plugin was configured to be a JWT provider, then it would be natural to also be able to use it as a JWT provider for this use-case (since MM jitsi knows the app secret and id and provides the well formed valid JWT). No need to use any external service.

@givors-anabasis
I trying work on this issue.
Is there any jwt or other message that send to callback from jitsi?

@catalintomai @hanzei @givors-anabasis is 6) possible. I am not aware of any features that allow us to do the same. I had a call with @lufty-demansol and this is the part we couldn't figure out.


Update cardano-node after addition of the new BulkSync implementation

This PR updates tracing and exposes the genesis configuration.
It requires https://github.com/IntersectMBO/ouroboros-consensus/pull/1179. cabal.project is made to point to a back-port of the BulkSync implementation on ouroboros-network-<IP_ADDRESS> and ouroboros-consensus-<IP_ADDRESS>.

This PR will likely be superseded by #6050 and the changes in https://github.com/IntersectMBO/cardano-node/tree/amesgen/genesis-10.2 (ie the last commit there basically is a cleaned-up version of this PR)


Expose 'timePartitionPattern' in Python API [ WIP ]

Description

Expose 'timePartitionPatter' in python API
Add related test cases
Pending to add more test case using public real data

How was this PR tested?

Tested locally and it run succeeded. Getting data source from my private storage:
batch_source = HdfsSource(name="testTimePartitionSource"<EMAIL_ADDRESS>                        time_partition_pattern="yyyy/MM/dd"                         )
Succeeded to run the job and got results like:

Does this PR introduce any user-facing changes?

[ ] No. You can skip the rest of this section.
[ ] Yes. Make sure to clarify your proposed changes.

Please remove the WP tag.


KOGITO-2207 Introduce ProcessInstanceReadMode to allow read only proc…

…ess instances

jenkins please retest this

jenkins please retest this

@tiagodolphine exactly, take a look in the docs part, I tried to explain a bit more in details there, see https://github.com/kiegroup/kie-docs/pull/2746/files#diff-551ebcaf10443155f86f0ebb04bda41cR10

Ok, so I got the point... one other thing it is worth and it would be important to scale at a huge number of process instances, is to get rid of the values() method https://github.com/kiegroup/kogito-runtimes/blob/a26c98a4b251c3cce513cd0310691288a291c7e1/api/kogito-api/src/main/java/org/kie/kogito/process/ProcessInstances.java#L25 because it brings all instances into memory + all the marshalling process... I mean this does not scale, and on the REST APIs perspective, the getting all instances does not make sense we have data-index to fetch the instances/filter/pagination etc... WDYT? I'm wondering why this method is really needed and if it would be feasible to remove it.

jenkins please retest this

@tiagodolphine I see your point and I agree that for any querying, the data index should be used, I just feel that we would restrict too much, even for demos? that the process id would need to be stored always, as we would only provide methods based on the process id.  Iwould say that use is disincouraged but not sure we should remove it entirely.

jenkins please retest this

jenkins please retest this

jenkins please retest this


Fix animation height problem by adding fontSize value

I had the issue, that the jumping dots were not visible anymore.
This solved the issue and i think it's a bug since 0.1.1 or maybe earlier.

LGTM


cannot allocate memory (gotype)

I don't have this issue when running locally, but when run in CircleCI I get this error:
oauth/internal/api/oauth2/authorize.go:5:2:error: could not import net/http (type-checking package "net/http" failed (/usr/local/go/src/net/http/client.go:13:2: could not import crypto/tls (type-checking package "crypto/tls" failed (/usr/local/go/src/crypto/tls/cipher_suites.go:15:2: could not import crypto/x509 (type-checking package "crypto/x509" failed (/usr/local/go/src/crypto/x509/pkcs8.go:8:2: could not import crypto/ecdsa (type-checking package "crypto/ecdsa" failed (/usr/local/go/src/crypto/ecdsa/ecdsa.go:25:2: could not import encoding/asn1 (read /usr/local/go/src/encoding/asn1/common.go: read /usr/local/go/src/encoding/asn1/common.go: cannot allocate memory))))))))) (gotype)

I've played with options a bit, and it looks like problem is running too many processes which takes too much RAM. Any one of these options solves issue in my case: -j 8 (default is 32, and with 16 it still fails), --enable-gc or -D gotype (of course). (Update: I've just get similar error from 3 different linters with -j 8. :disappointed: Still, -j 4 looks safe for now, and it's faster than --enable-gc.)
At a glance CircleCI provides enough RAM, but OOM still somehow happens. This is before running gometalinter:
              total        used        free      shared  buff/cache   available
Mem:       61830888     8910860     9264020     1266068    43656008    51173964
Swap:             0           0           0

This is shortly after it started:
              total        used        free      shared  buff/cache   available
Mem:       61830888    13230316     3432468     1421244    45168104    46694836
Swap:             0           0           0

And this is right before gotype fails:
              total        used        free      shared  buff/cache   available
Mem:       61830888    14440164     1341936     1425568    46048788    45478220
Swap:             0           0           0

I'm not sure what is right thing to do here. Maybe defaults should be changed to more conservative -j 4 or more safe --enable-gc. Or maybe some linters run themselves in parallel too, and this should be prevented to avoid using too much resources.
May be related to #427

Thanks!


brload: fix premature socket closure

Brload borrows the file descriptor from a af_packet.TPacket structure in order to use it with sendmmsg (not available via TPacket). In the process it left the original TPacket, only used on the receiving side, exposed to garbage collection, resulting in the premature closure of the socket. Fixed it by keeping a reference to TPacket on the sending side.
In passing:

temporarily increase the benchmark packet size to 1500 bytes, to show bandwidth (~10Gb/s) with normal frames.
display brload's output to help in diagnosing issues.

Fixes #4590

Saving everyone's time by bypassing re-review for this.


how to call Wallet_watchAsset method?

Hello! I need to call the wallet_watchAsset method using the wallet connect provider. How can I do that?

Hello. I'll add this today

Hello! I need to call the wallet_watchAsset method using the wallet connect provider. How can I do that?

Please upgrade to v2.1.0 and check the readme


add CSX to debuggable extensions

Roslyn is now able to emit debugging symbols for C# scripts too so it makes sense to add .csx to the list of allowed file extensions.

thanks for the PR!


How to test plugins?

Yet another question ;)  I just created my first tiny httpyac plugin \o/. Same time its my first JS project ever, too.
https://github.com/rngtng/httpyac-plugin-yaml-body
No TS and all that jazz (yet) - but I wanted at least to test it before releasing. I got the test framework up and running, but I wonder how can I ensure cli.execute to load the plugin for testing? I thought of a deeper layer than the cli which could be evoked and load the plugin? Any ideas?
If you have the time pls check https://github.com/rngtng/httpyac-plugin-yaml-body/blob/main/test/index.test.js#L12-L17.  Thanks

Ah I think I found it. The *.http file needs a global script:
{{
  const plugin = require("../src/index");
  plugin(httpFile);
}}
...

It would work since my PluginAPI and the HttpFile both have the property hooks, but doesn't feel right. However, I would not test this at all. Instead, I would export the method and test it. For me, this would be a unit test and the test via CLI would be an integration test.
onRequestHook.js
module.exports = (request, context) => {
    var { headers, body } = request;
    if (!isYamlContent(headers['content-type']) && isYaml(body)) {
      response.headers["content-type"] = "application/json";
      request.body = JSON.stringify(YAML.parse(body));
    }
  }

index.js
api.hooks.onRequest.addHook("signRequest", require('./onRequestHook');

For checking if the interface is still implemented correctly, I would leave exactly Typescript. By implementing Typescript you will also find that the body can also be a buffer or array and your script will generate an error in other use cases (< ./icon.pdf, multipart/form-data requests). To get automatic updates from httpyac, you can then enable Dependabot in Github. And automatic delivery in npm would be the following.

And reading the header using headers['...'] is problematic. I don't change the casing of the headers. If someone uses Content-Type it doesn't work properly. Use api.utils.getHeader('...') instead.

thanks the feedback. just figured it on my own, but will update to your suggestions.

I think it's a great idea, by the way. And it should all be just suggestions. I can't help myself when I see something to improve:-)

Updated: https://github.com/rngtng/httpyac-plugin-yaml-body/pull/2
I kept one high-level integration test, moved the edge cases to unit test. I c&p you getHeader to stay independent as much of the inner httpyac implementation. Next setting up pipeline and publish npm :P

I was wondering the same thing, if I would copy the method or just use it. I would have copied it too.

And there it is https://www.npmjs.com/package/httpyac-plugin-yaml-body!!! wuhu :)

closing this issues. guess my plugin answers the question. Sure the API could be improved, but no urgency.

Very cool!  The one earlier was a hack and didn't work for any parsing related hooks. BUT this works: Create at .httpyac.js in test folder and init plugin with:
const plugin = require("..path to plugin index...");

module.exports = {
  configureHooks: function (api) {
    plugin(api);
  }
}

I don't think that's quite straight yet either. Better would be to create a package.json and import the dependency there using "httpyac-plugin-yaml-body": "../". Then it would also be tested if the name is recognized correctly. I haven't gotten around to trying it out yet, though.

hm but at least the interface of api is now the same!? In a certain way I like the explicit nature of loading the plugin this way..

Yes. I is the same api. It was also more a test to see if the idea works. I dont really like the extra npm i` either. I close the PR.


Detailed Query Plan and Indexes

Tutorial URL: https://developers.sap.com/tutorials/dt-query-processing-part4.html
Please specify the step you are referring to:
Hello, dear colleagues,
THe picture in this page are all lost.
Please double check it.
Thank you
&
Best Regards
Yang

Sorry, My mistake.
It's my chrome's problem.

Hope it straightens out.

@ganyang88 How did you know it was a Chrome issue?

Hope it straightens out.

Thank you :)

@ganyang88 How did you know it was a Chrome issue?

Good Question.
Acutally, I'm not 100% sure.


Update autorest version to prerelease 6.9.9-alpha.20231115.4

Triggered from branch: users/pahallis/cookiecutter

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-developer-devcenter


elektroid: 3.0 -> 3.0.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/dagargo/elektroid/releases.
meta.description for elektroid is: Sample and MIDI device manager
meta.homepage for elektroid is: https://github.com/dagargo/elektroid
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.0.1 with grep in /nix/store/yysbk40krxx8bxkr44mjkygp7jsazj1c-elektroid-3.0.1
found 3.0.1 in filename of file in /nix/store/yysbk40krxx8bxkr44mjkygp7jsazj1c-elektroid-3.0.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
elektroid

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/yysbk40krxx8bxkr44mjkygp7jsazj1c-elektroid-3.0.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A elektroid https://github.com/r-ryantm/nixpkgs/archive/52b6b9051abbd7c28c227da1e8e490b5016dc95a.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/52b6b9051abbd7c28c227da1e8e490b5016dc95a#elektroid

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/yysbk40krxx8bxkr44mjkygp7jsazj1c-elektroid-3.0.1
ls -la /nix/store/yysbk40krxx8bxkr44mjkygp7jsazj1c-elektroid-3.0.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

elektroid

Maintainer pings
cc @camelpunch for testing.

LGTM :+1:


python310Packages.findpython: 0.2.0 -> 0.2.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.findpython is: "A utility to find python versions on your system"
meta.homepage for python310Packages.findpython is: "https://github.com/frostming/findpython"
meta.changelog for python310Packages.findpython is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 0.2.1 with grep in /nix/store/blylgfkj0pk5g5pgdhajpp49rmm3cfqx-python3.10-findpython-0.2.1
found 0.2.1 in filename of file in /nix/store/blylgfkj0pk5g5pgdhajpp49rmm3cfqx-python3.10-findpython-0.2.1

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
pdm
python310Packages.findpython
python39Packages.findpython

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/blylgfkj0pk5g5pgdhajpp49rmm3cfqx-python3.10-findpython-0.2.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.findpython https://github.com/r-ryantm/nixpkgs/archive/b501c45b210688b81af3c026b5fdedcf5c6bd774.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/blylgfkj0pk5g5pgdhajpp49rmm3cfqx-python3.10-findpython-0.2.1
ls -la /nix/store/blylgfkj0pk5g5pgdhajpp49rmm3cfqx-python3.10-findpython-0.2.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

pdm

2 packages built:

python310Packages.findpython
python39Packages.findpython

Maintainer pings
cc @mweinelt for testing.

The pdm package is already broken on master. Fixes in #182981.


Markdown cell doesn't always update when editing in split notebook editor

Open a notebook with a markdown cell
Split it
Edit a markdown cell on one side, see that it's not updated on the other side in preview mode
If it works, repeat a couple times

Seems that the right events are being fired, but getText in the viewmodel returns the old text. If I put the preview cell into edit mode, the editor has the right contents.
Any idea what's going on @rebornix? I touched this area recently but I can still repro after reverting my changes.
Pushed a1feacf5c445f040d42419ddbe07b29bbe5bc165 because I removed that and I think I shouldn't have.

Now I've really broken it

I was not able to reproduce this issue with https://github.com/microsoft/vscode/pull/100545 .


SMB listener not working on 1.1.0

As discussed in #363, the fix for SMB does not appear to work on v1.1.0
Interactsh version:
1.1.0
Current Behavior:
Starting interactsh with -smb does not start the smb listener.
Expected Behavior:
Starting interactsh with -smb starts the smb listener.
Steps To Reproduce:
Run interactsh-server -domain xxx -listen-ip x.x.x.x -ip x.x.x.x -token xxx -ftp -smb
(_)___  / /____  _________ ______/ /______/ /_
/ / __ \/ __/ _ \/ ___/ __ '/ ___/ __/ ___/ __ \
/ / / / / /_/  __/ /  / /_/ / /__/ /_(__  ) / / /
/_/_/ /_/\__/\___/_/   \__,_/\___/\__/____/_/ /_/ 1.1.0
projectdiscovery.io
[INF] Loading existing SSL Certificate for:  [*.xxx, xxx]
[INF] Listening with the following services:
1.67700946105734e+09        info        maintenance        started background certifi
[FTP] Listening on TCP <IP_ADDRESS>:21
[SMTPS] Listening on TCP <IP_ADDRESS>:587
[DNS] Listening on TCP <IP_ADDRESS>:53
[DNS] Listening on UDP <IP_ADDRESS>:53
[HTTP] Listening on TCP <IP_ADDRESS>:80
[LDAP] Listening on TCP <IP_ADDRESS>:389
[SMB] Listening on TCP <IP_ADDRESS>:445
[SMTP] Listening on TCP <IP_ADDRESS>:25
[HTTPS] Listening on TCP <IP_ADDRESS>:443
[WRN] The TCP SMB service has unexpectedly stopped

SMB port is not running:
# netstat -tlnp | grep 445
#

This is on an EC2 instance. Not sure, but perhaps this is somehow related to public/internal IPs?

@ldionmarcil can you retry with latest release - https://github.com/projectdiscovery/interactsh/releases/tag/v1.1.1?

@ldionmarcil I'm unable to reproduce the issue, can you please verify if you are able to execute successfully the standalone smb_server.py in cmd/interactsh-server:
# python3 smb_server.py test.txt 445

Closing due to inactivity


Route-MAC-JWT opaque token claim

Put the opaque bearer token claim into the Route-MAC-JWT payload.

Route-MAC-JWT changed to Route-JWT and Itinerary-MAC-JWT to Itinerary-JWT


Callback is not called if request takes a lot of time

So if I create twitter client like so:
var client = new Twitter({
            consumer_key       : access['tw']['consumer_key'],
            consumer_secret    : access['tw']['consumer_secret'],
            access_token_key   : access['tw']['oauth_token'],
            access_token_secret: access['tw']['oauth_token_secret']
        });

and then fetch data
client.get('users/show', params, function (error, user, response) {
//callback body
});

Callback body could be called after 20min or even few hours after the request is sent (proxy is used in my case). So, maybe it's better to add some default request timeout, for example, 30s?
If I add a timeout to requst_options it works great for me.
var client = new Twitter({
            consumer_key       : access['tw']['consumer_key'],
            consumer_secret    : access['tw']['consumer_secret'],
            access_token_key   : access['tw']['oauth_token'],
            access_token_secret: access['tw']['oauth_token_secret'],
            request_options: {
                timeout: 20000
            }
        });

This could help other people to find why callback is not called.

Thanks for the details here.  This brings up a good point.  We may want to make it more clear to folks that they can easily extend the Request object by using the request_options key.


In version 2.0, all IP addresses are not allowed.

Environment:
OS : Windows 10 Home

Python version: Python 3.8.10 on Anaconda
Flask version: 2.0.1

$ pip install Flask==1.1.4
$ flask run --host=<IP_ADDRESS>
 * Serving Flask app "app.py"
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: off
 * Running on http://<IP_ADDRESS>:5000/ (Press CTRL+C to quit)

$ pip install Flask==2.0.1
$ flask run --host=<IP_ADDRESS>
 * Serving Flask app 'app.py' (lazy loading)
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: off
 * Running on all addresses.
   WARNING: This is a development server. Do not use it in a production deployment.
 * Running on http://<IP_ADDRESS>:5000/ (Press CTRL+C to quit)

In fact, it is run in docker, and as above, it is set as the private IP address(http://<IP_ADDRESS>:5000/) of the docker container.

From the output:

* Running on all addresses.

See https://github.com/pallets/werkzeug/pull/2010, which changed the "running on" message to always show a valid address.

@davidism
Even if the displayed message is like that, I can't actually connect from another IP.

I can't reproduce that issue. Sounds like there's something wrong with your Docker setup.


ValueError in my_txtutils.py

When run rnn_train.py, I got the following error:
Traceback (most recent call last):
File "/tensorflow-rnn-shakespeare/rnn_train.py", line 148, in
txt.print_learning_learned_comparison(x, y, l, bookranges, bl, acc, epoch_size, step, epoch)
File "/tensorflow-rnn-shakespeare/my_txtutils.py", line 180, in print_learning_learned_comparison
footer = format_string.format('INDEX', 'BOOK NAME', 'TRAINING SEQUENCE', 'PREDICTED SEQUENCE', 'LOSS')
ValueError: Invalid conversion specification
I use Python 2.7.6 and tensorflow 1.1.0 on Ubuntu 14.04. How can I fix this? Any reply will be very much appreciated.

This looks like a Python 2 / Python 3 discrepancy but theoretically "".format() works in Pyhon 2.7. i do not have an immediate answer. I will have to test under Python 2.7.6.

Hi Martin
I study many script and code in tensorflow and python. It is obvious in all of them they use tf.reduce _mean() function after tf.nn.softmax_cross_entropy_with_logits to make loss but you don't, my question is Why????????

see issue #15  , no problem on python3, windows 10, tensorflow 1.1.0.

@mahmood431226 it is because on a mini-batch of input images, you get one loss per image. The loss is supposed to be a single scalar though so you average them.


Clarification around transpileDependencies

What problem does this feature solve?
transpileDependencies searches for the provided terms in the full path, meaning that if we have something like transpileDependencies: ['vuetify'] (see https://github.com/vuetifyjs/vue-cli-plugin-vuetify/issues/55) then any vuetify in the path will cause Babel to translate the files.
For example, if my path is /home/aymkdn/projects/vuetify/my-app/, EVERYTHING is compiled, causing multiple errors. Even if the path is /home/aymkdn/projects/my-app/ Babel will translate all node modules with "vuetify" in their name (like vue-cli-plugin-vuetify or vuetify-loader)
The expected behavior when reading the documentation is to only compile the module called "vuetify"
What does the proposed API look like?
I see three options here :

Clarify the documentation to explain that this option will search for the terms in the whole path
Change transpileDependencies to only look at node module names (for example transpileDependencies: ['vuetify'] will be equivalent to /home/aymkdn/projects/vuetify/my-app/node_modules/vuetify/)
Add a new parameter, called transpileModules that will do the same as option 2 above

I would rather rate this a bug

Does that fix work if node_modules is above the project folder, like in a monorepo?

@KaelWD I think so. That fix is essentially changing the regexp from vuetify to node_modules/vuetify.


E154: Duplicate tag ":VGit"

Description
In nix building the plugin with pkgs.vimUtils.buildVimPlugin fails because of duplicated tags in the docs:
       > Executing vimPluginGenTags
       > Building help tags
       > Error detected while processing command line:
       > E154: Duplicate tag ":VGit" in file /nix/store/7c8911a675bw7h6j5rmd87q13g50w6kl-vimplugin-vgit/./doc/vgit.txt
       > E154: Duplicate tag ":VGit" in file /nix/store/7c8911a675bw7h6j5rmd87q13g50w6kl-vimplugin-vgit/./doc/vgit.txtFailed to build help tags!

I was able to overcome this with a patch that removes the repeated tags at the bottom of the docs file:
diff --git a/doc/vgit.txt b/doc/vgit.txt
index 411056b..8dbb233 100644
--- a/doc/vgit.txt
+++ b/doc/vgit.txt
@@ -419,7 +419,6 @@ toggle_tracing()                                          *vgit.toggle_tracing()
 ==============================================================================
 COMMAND                                                        *vgit-navigation*

-                                                                         *:VGit*
 Any VGit preview that contains changes with highlights is navigatable,
 enhancing your git workflow drastically. Please refer to |hunk_up| and
 |hunk_down| mapping these functions to "<C-j>" and "<C-k>" is a personal
@@ -429,7 +428,6 @@ with a diff will also enable hunk navigations.
 ==============================================================================
 COMMAND                                                   *vgit-diff-preference*

-                                                                         *:VGit*
 Any VGit preview with a diff can be seen visually in two different ways,
 unified and split. Users can switch between these two styles anytime using
 |toggle_diff_preference|.

I don't open PR because I am not sure if you want to keep it removed or replace it with something else.

nvim --version output:

NVIM v0.8.3
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by nixbld

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "
/nix/store/cm208hvfg4nyrrvmf8424dda0mg6iiaw-neovim-unwrapped-master/share/nvim
"

Run :checkhealth for more info

Operating system:

Linux yueix <IP_ADDRESS>-microsoft-standard-WSL2 #1 SMP Fri Jan 27 02:56:13 UTC 2023 x86_64 GNU/Linux

I just Lazy.nvim (https://github.com/folke/lazy.nvim) installation fail because of this issue.

I just had Lazy.nvim (https://github.com/folke/lazy.nvim) installation fail because of this issue.

Me too.

Closed by https://github.com/tanvirtin/vgit.nvim/pull/358


bind EADDRINUSE

Hello. I tried to run some sample code such as takeoff.js.
However, I am consistently getting the following error:
dkkim930122@dkkim930122:~/node-bebop/examples$ node takeoff.js
events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: bind EADDRINUSE
    at exports._errnoException (util.js:746:11)
    at dgram.js:224:28
    at dns.js:85:18
    at process._tickCallback (node.js:355:11)

Could someone help me with this error?
For more information,
I installed node-bebop through using the following command:
npm install git:github.com/hybridgroup/node-bebop.git
My node version is v0.12.6 and npm is 2.11.2.
Thank you for your help!

Hi, @dk683 are you sure you are connected from your computer to the drone's wifi? Remember you need to use the Bebop as an access point when connecting from your computer to the Bebop.
Or are you already connected from your mobile app to the drone? That error indicates some kind of IP address conflict, such as when you are already connected to the Bebop from something else.
Hope that helps!

Hello @deadprogram! Thank you for your comment.
Yes, I made sure that I connected my computer with Bebop.
And the error was actually consistently happening after successfully flying (or getting mjpeg streaming) once.
Previously, when I was working with Bebop's SDK code (https://github.com/Parrot-Developers/ARSDKBuildUtils), I noticed that they clean up Bebop(i.e. free reader thread array, stopping network) after commands were done.
However, if I noticed correctly, I could not find the clean up process in the nodejs code.
Could this be the reason why?
Thank you again for your help!

That is not a problem we ourselves have run into ourselves. Node.js does not expose low-level threading routinues, and normally that is not needed.
Can you provide the code sample, as well as letting us know what OS and version of Node you are using? Thanks.

Thank you for your reply.
The code sample of the SDK was: BebopDroneReceiveStream.c that can be found in the following link: https://github.com/Parrot-Developers/Samples/tree/master/Unix/BebopDroneReceiveStream.
My OS verison is Ubuntu 14.04 and my node version is v0.12.6 and npm is 2.11.2.
I will try to debug further and figure out what is exactly causing the connection problem!
Thank you.

I was referring to which node sample code you were running, sorry if that was unclear.
Do you have this same problem with other versions of node, such as 0.10.29?

I am using the latest github node (https://github.com/hybridgroup/node-bebop), and the sample code was takeoff.js:
"use strict";
var bebop = require("../.");
var drone = bebop.createClient();

drone.connect(function() {
  drone.takeOff();

  setTimeout(function() {
    drone.land();
  }, 5000);
});

I haven't tried the other versions of node yet, but I will try!
Thank you.

Dear @deadprogram,
Thank you! The problem was solved by downgrading node version from v0.12.6 to v0.10.29! :+1:


Language model unavailable

Type: Bug
Language model unavailable
Extension version: 0.23.1
VS Code version: Code 1.96.0 (138f619c86f1199955d53b4166bef66ef252935c, 2024-12-11T02:29:09.626Z)
OS version: Windows_NT x64 10.0.22631
Modes:
Remote OS version: Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2
Prompt Details

Info: Can't use the Electron fetcher in this environment.
Info: Using the Node fetch fetcher.
Info: Initializing Git extension service.
Debug: [context keys] Updating context keys.

System Info

Item
Value

CPUs
13th Gen Intel(R) Core(TM) i7-13850HX (28 x 2304)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
undefined

Memory (System)
31.61GB (4.87GB free)

Process Argv
--crash-reporter-id 9cfd0538-5b46-47af-89e5-8677df8e920d

Screen Reader
no

VM
0%

Item
Value

Remote
Dev Container: OneDriving Devcontainer - Docker Compose

OS
Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

CPUs
13th Gen Intel(R) Core(TM) i7-13850HX (28 x 0)

Memory (System)
15.62GB (10.94GB free)

VM
0%

I am also getting this error in the UI after updating to 0.23.1. Everything appears to work correctly when switching back to 0.22.4.
Error in chat:

Error notification:

Also, I noticed when switching to 0.23.1 I get an additional error message about a different plugin. Incompatibility maybe?

0.23.1 "Run Diagnostics"
## GitHub Copilot Chat

- Extension Version: 0.23.1 (prod)
- VS Code: vscode/1.96.0
- OS: Linux
- Remote Name: wsl

## Network

User Settings:

  "github.copilot.advanced.debug.useElectronFetcher": true,
  "github.copilot.advanced.debug.useNodeFetcher": false,
  "github.copilot.advanced.debug.useNodeFetchFetcher": true

Connecting to https://api.github.com:
- DNS ipv4 Lookup: <IP_ADDRESS> (25 ms)
- DNS ipv6 Lookup: Error (262 ms): getaddrinfo ENOTFOUND api.github.com
- Proxy URL: None (1 ms)
- Electron fetch: Unavailable
- Node.js https: HTTP 200 (184 ms)
- Node.js fetch (configured): HTTP 200 (195 ms)
- Helix fetch: HTTP 200 (266 ms)

Connecting to http://localhost:5000/_ping:
- DNS ipv4 Lookup: <IP_ADDRESS> (1 ms)
- DNS ipv6 Lookup: ::1 (175 ms)
- Proxy URL: None (1 ms)
- Electron fetch: Unavailable
- Node.js https: Error (2 ms): connect ECONNREFUSED <IP_ADDRESS>:5000
- Node.js fetch (configured): Error (1 ms): fetch failed
  connect ECONNREFUSED <IP_ADDRESS>:5000
- Helix fetch: Error (2 ms): connect ECONNREFUSED <IP_ADDRESS>:5000

## Documentation

In corporate networks: [Troubleshooting firewall settings for GitHub Copilot](https://docs.github.com/en/copilot/troubleshooting-github-copilot/troubleshooting-firewall-settings-for-github-copilot).

Output from 0.22.4
2024-12-13 11:11:31.923 [info] Can't use the Electron fetcher in this environment.
2024-12-13 11:11:31.923 [info] Using the Helix fetcher.
2024-12-13 11:11:31.923 [info] Initializing Git extension service.
2024-12-13 11:11:31.932 [info] Successfully activated the vscode.git extension.
2024-12-13 11:11:31.932 [info] Enablement state of the vscode.git extension: true.
2024-12-13 11:11:31.932 [info] Successfully registered Git commit message provider.
2024-12-13 11:11:32.520 [info] Logged in as b_REDACTED_n
2024-12-13 11:11:32.677 [info] Removed 1 expired certificates
2024-12-13 11:11:34.315 [info] Got Copilot token for b_REDACTED_n
2024-12-13 11:11:34.586 [info] copilot token chat_enabled: true, sku: copilot_for_business_seat
2024-12-13 11:11:34.586 [info] GitHub.vscode-pull-request-github extension is not yet activated.
2024-12-13 11:11:34.595 [info] Registering default platform agent...
2024-12-13 11:11:35.043 [info] Fetched model metadata in 724ms 329b68b7-34ab-4678-99cc-e506bfce784e
2024-12-13 11:11:35.275 [info] activationBlocker from 'languageModelAccess' took for 3169ms

Output from 0.23.1
2024-12-13 11:09:02.199 [info] Can't use the Electron fetcher in this environment.
2024-12-13 11:09:02.199 [info] Using the Node fetch fetcher.
2024-12-13 11:09:02.199 [info] Initializing Git extension service.
2024-12-13 11:09:02.199 [info] Successfully activated the vscode.git extension.
2024-12-13 11:09:02.199 [info] Enablement state of the vscode.git extension: true.
2024-12-13 11:09:02.199 [info] Successfully registered Git commit message provider.
2024-12-13 11:09:03.149 [info] Logged in as b_REDACTED_n
2024-12-13 11:09:04.064 [info] Got Copilot token for b_REDACTED_n
2024-12-13 11:09:04.195 [error] TypeError: fetch failed
    at node:internal/deps/undici/undici:13392:13
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at ek._fetch (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:763:5811)
    at _p._fetchModels (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:2213:11405): Failed to fetch models (600ca856-8409-4c3e-bbf4-047f875a295e)
2024-12-13 11:09:04.195 [info] activationBlocker from 'languageModelAccess' took for 1832ms
2024-12-13 11:09:04.346 [info] copilot token chat_enabled: true, sku: copilot_for_business_seat
2024-12-13 11:09:04.347 [info] GitHub.vscode-pull-request-github extension is not yet activated.
2024-12-13 11:09:04.356 [info] Registering default platform agent...
2024-12-13 11:09:04.379 [error] TypeError: fetch failed
    at node:internal/deps/undici/undici:13392:13
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at ek._fetch (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:763:5811)
    at V0._doRefreshRemoteAgents (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:491:8964): Failed to load remote copilot agents
2024-12-13 11:09:04.380 [error] TypeError: fetch failed
    at node:internal/deps/undici/undici:13392:13
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at ek._fetch (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:763:5811)
    at _p._fetchModels (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:2213:11405)
    at _p.getChatModelFromFamily (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:2213:10055)
    at WO.getChatEndpoint (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:2213:14751)
    at Object.A [as task] (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:488:834)
    at xC._processQueue (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:487:1101): Failed to fetch models (711e2856-56a2-44c2-958b-9511255b2731)
2024-12-13 11:09:04.380 [error] TypeError: fetch failed
    at node:internal/deps/undici/undici:13392:13
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at ek._fetch (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:763:5811)
    at _p._fetchModels (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:2213:11405)
    at _p.getChatModelFromFamily (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:2213:10055)
    at WO.getChatEndpoint (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:2213:14751)
    at Object.A [as task] (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:488:834)
    at xC._processQueue (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:487:1101): [LanguageModelAccess] FAILED to update language models
2024-12-13 11:09:04.592 [error] TypeError: fetch failed
    at node:internal/deps/undici/undici:13392:13
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at ek._fetch (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:763:5811)
    at _p._fetchModels (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:2213:11405): Failed to fetch models (8a23ae8a-e540-472c-91fe-97bac3c1ff51)
2024-12-13 11:09:04.627 [info] Subscription based route failed when legacy route succeeded. Retrying in 5 seconds. Error: http://localhost:5000/_ping failed with error: fetch failed
  connect ECONNREFUSED <IP_ADDRESS>:5000
2024-12-13 11:09:04.746 [error] TypeError: fetch failed
    at node:internal/deps/undici/undici:13392:13
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at ek._fetch (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:763:5811)
    at _p._fetchModels (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:2213:11405)
    at _p.getChatModelFromFamily (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:2213:10055)
    at WO.getChatEndpoint (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:2213:14751)
    at Object.A [as task] (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:488:834)
    at xC._processQueue (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:487:1101): Failed to fetch models (012f6a45-92ea-42d4-a57b-d3b85105fe82)
2024-12-13 11:09:04.746 [error] TypeError: fetch failed
    at node:internal/deps/undici/undici:13392:13
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at ek._fetch (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:763:5811)
    at _p._fetchModels (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:2213:11405)
    at _p.getChatModelFromFamily (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:2213:10055)
    at WO.getChatEndpoint (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:2213:14751)
    at Object.A [as task] (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:488:834)
    at xC._processQueue (/home/b_REDACTED_n/.vscode-server/extensions/github.copilot-chat-0.23.1/dist/extension.js:487:1101): [LanguageModelAccess] FAILED to update language models
2024-12-13 11:09:09.825 [info] Subscription based route failed when legacy route succeeded. Retrying in 5 seconds. Error: http://localhost:5000/_ping failed with error: fetch failed
  connect ECONNREFUSED <IP_ADDRESS>:5000
2024-12-13 11:09:15.022 [error] Subscription based route failed when legacy route succeeded. Error: http://localhost:5000/_ping failed with error: fetch failed
  connect ECONNREFUSED <IP_ADDRESS>:5000

The obvious thing I notice is switching from the "Helix" fetcher to the "Node Fetch" fetcher.

For some reason my user settings included this setting. This could have been an experiment I did. I don't remember. 🤷♂
  "github.copilot.advanced": {
    "debug.overrideCapiUrl": "http://localhost:5000"
  },

Removing this setting fixed my problem.

Output from 0.23.1
2024-12-13 12:01:50.110 [info] Can't use the Electron fetcher in this environment.
2024-12-13 12:01:50.110 [info] Using the Node fetch fetcher.
2024-12-13 12:01:50.110 [info] Initializing Git extension service.
2024-12-13 12:01:50.110 [info] Successfully activated the vscode.git extension.
2024-12-13 12:01:50.110 [info] Enablement state of the vscode.git extension: true.
2024-12-13 12:01:50.110 [info] Successfully registered Git commit message provider.
2024-12-13 12:01:51.352 [info] Logged in as b_REDACTED_n
2024-12-13 12:01:52.528 [info] Got Copilot token for b_REDACTED_n
2024-12-13 12:01:52.822 [info] copilot token chat_enabled: true, sku: copilot_for_business_seat
2024-12-13 12:01:52.822 [info] GitHub.vscode-pull-request-github extension is not yet activated.
2024-12-13 12:01:52.831 [info] Registering default platform agent...
2024-12-13 12:01:53.290 [info] Fetched model metadata in 759ms 01e33e65-3092-4334-9b7e-7a816e0fc369
2024-12-13 12:01:53.292 [info] activationBlocker from 'languageModelAccess' took for 2739ms


Update TagBot yaml

This PR updates the TagBot yaml to the latest version on https://github.com/JuliaRegistries/TagBot.
I think this, plus making sure that secrets are properly configured, should result in tagbot working.

Thanks! Let's give this a try.


Actions not invoked in definition order

The documentation on multiple actions states:

Stimulus invokes the actions from left to right in the order that their descriptors appear.

However given this link  and 2 simple controllers where the actions simply output to console, the execution order I get is:
image a
image b
modal a

If I change the order to data-action="image#b modal#a image#a", I get:
image b
image a
modal a

This appeared to me like it is ordering the actions by the controller name, to test this out further I added a aardvark controller action at the end data-action="image#b modal#a image#a aardvark#a" which results in:
image b
image a
aardvark a
modal a

I also tried with including the event name but it made no difference.
The controller structure of the DOM is:

Just to be sure the controller definitions weren't causing an issue I tried swapping the controller order on the root node or moving the image controller up or down in the DOM and that made no difference.

I'm trying to replicate this in an isolated test case but I am observing the desired behaviour. In our use case the modal controller is actually defined in a package of ours whereas the image & aardvark are defined in the application so it is most likely a quirk with our setup. I will investigate and post here if I find anything useful.