HADOOP-18156. Address JavaDoc warnings in classes like MarkerTool, S3ObjectAttributes, etc

Description of PR
Fixed the Javadoc warnings that were there in MarkerTool.java, DirectoryPolicy.java, DirMarkerTracker.java and OperationCallbacks.java
How was this patch tested?
Checked the JavaDoc warnings during build

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 50s

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 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
40m 33s

trunk passed

+1 :green_heart:
compile
0m 52s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
0m 44s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 46s

trunk passed

+1 :green_heart:
mvnsite
0m 50s

trunk passed

+1 :green_heart:
javadoc
0m 36s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 37s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 25s

trunk passed

+1 :green_heart:
shadedclient
22m 10s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 37s

the patch passed

+1 :green_heart:
compile
0m 45s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 45s

the patch passed

+1 :green_heart:
compile
0m 36s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 36s

the patch passed

-1 :x:
blanks
0m  0s
/blanks-eol.txt
The patch has 26 line(s) that end in blanks. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

+1 :green_heart:
checkstyle
0m 27s

the patch passed

+1 :green_heart:
mvnsite
0m 40s

the patch passed

+1 :green_heart:
javadoc
0m 22s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 25s

hadoop-tools_hadoop-aws-jdkPrivateBuild-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07 with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07 generated 0 new + 0 unchanged - 37 fixed = 0 total (was 37)

+1 :green_heart:
spotbugs
1m 10s

the patch passed

+1 :green_heart:
shadedclient
22m 16s

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

_ Other Tests _

+1 :green_heart:
unit
2m 41s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
0m 49s

The patch does not generate ASF License warnings.

102m 37s

Subsystem
Report/Notes

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

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

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

uname
Linux d994151c835f 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / b3e4e7a9cf3a2cb328a005be69910b89ac937d61

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-tools/hadoop-aws U: hadoop-tools/hadoop-aws

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4965/1/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 55s

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 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
42m 59s

trunk passed

+1 :green_heart:
compile
0m 51s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
0m 43s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 39s

trunk passed

+1 :green_heart:
mvnsite
0m 50s

trunk passed

+1 :green_heart:
javadoc
0m 36s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 40s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 29s

trunk passed

+1 :green_heart:
shadedclient
24m 37s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 38s

the patch passed

+1 :green_heart:
compile
0m 47s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 47s

the patch passed

+1 :green_heart:
compile
0m 35s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 35s

the patch passed

-1 :x:
blanks
0m  0s
/blanks-eol.txt
The patch has 26 line(s) that end in blanks. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

+1 :green_heart:
checkstyle
0m 22s

the patch passed

+1 :green_heart:
mvnsite
0m 41s

the patch passed

+1 :green_heart:
javadoc
0m 20s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 27s

hadoop-tools_hadoop-aws-jdkPrivateBuild-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07 with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07 generated 0 new + 0 unchanged - 37 fixed = 0 total (was 37)

+1 :green_heart:
spotbugs
1m 17s

the patch passed

+1 :green_heart:
shadedclient
24m  8s

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

_ Other Tests _

+1 :green_heart:
unit
2m 36s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
0m 41s

The patch does not generate ASF License warnings.

107m 30s

Subsystem
Report/Notes

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

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

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

uname
Linux b3f6400eb8b3 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 57ac83cfc55c96894f27e9c0152cb80bfe576708

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-tools/hadoop-aws U: hadoop-tools/hadoop-aws

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4965/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.

:broken_heart: -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  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 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
39m 18s

trunk passed

+1 :green_heart:
compile
0m 51s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
0m 46s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 42s

trunk passed

+1 :green_heart:
mvnsite
1m  0s

trunk passed

+1 :green_heart:
javadoc
0m 40s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 42s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 26s

trunk passed

+1 :green_heart:
shadedclient
21m  5s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 36s

the patch passed

+1 :green_heart:
compile
0m 44s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 44s

the patch passed

+1 :green_heart:
compile
0m 33s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 33s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 27s

the patch passed

+1 :green_heart:
mvnsite
0m 38s

the patch passed

+1 :green_heart:
javadoc
0m 20s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 30s

hadoop-tools_hadoop-aws-jdkPrivateBuild-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07 with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07 generated 0 new + 0 unchanged - 37 fixed = 0 total (was 37)

+1 :green_heart:
spotbugs
1m 11s

the patch passed

+1 :green_heart:
shadedclient
20m 30s

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

_ Other Tests _

+1 :green_heart:
unit
2m 35s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
0m 44s

The patch does not generate ASF License warnings.

97m 18s

Subsystem
Report/Notes

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

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

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

uname
Linux 2b7f06626cca 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / d4ae4c34daeafb85e1553015e3ee70fc5cf5b976

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-tools/hadoop-aws U: hadoop-tools/hadoop-aws

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4965/3/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 46s

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 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 33s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
25m 42s

trunk passed

+1 :green_heart:
compile
23m 21s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
20m 46s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
4m 22s

trunk passed

+1 :green_heart:
mvnsite
3m 30s

trunk passed

+1 :green_heart:
javadoc
2m 37s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m  5s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
4m 38s

trunk passed

+1 :green_heart:
shadedclient
21m 44s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 30s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 43s

the patch passed

+1 :green_heart:
compile
22m 32s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
22m 32s

the patch passed

+1 :green_heart:
compile
21m  1s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
21m  1s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
4m  6s

the patch passed

+1 :green_heart:
mvnsite
3m  9s

the patch passed

+1 :green_heart:
javadoc
2m 17s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m  4s

hadoop-common in the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07.

+1 :green_heart:
javadoc
1m  9s

hadoop-tools_hadoop-aws-jdkPrivateBuild-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07 with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07 generated 0 new + 0 unchanged - 37 fixed = 0 total (was 37)

+1 :green_heart:
spotbugs
4m 48s

the patch passed

+1 :green_heart:
shadedclient
21m 48s

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

_ Other Tests _

+1 :green_heart:
unit
18m 55s

hadoop-common in the patch passed.

+1 :green_heart:
unit
3m  1s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
1m 30s

The patch does not generate ASF License warnings.

237m 35s

Subsystem
Report/Notes

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

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

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

uname
Linux 4c8a6c797a04 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 708ee5f77c1e89de7284bf8f40c5d3f4b99d2fbe

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-common-project/hadoop-common hadoop-tools/hadoop-aws U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4965/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.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 56s

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 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 33s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
25m 38s

trunk passed

+1 :green_heart:
compile
23m 14s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
20m 48s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
4m 25s

trunk passed

+1 :green_heart:
mvnsite
3m 17s

trunk passed

+1 :green_heart:
javadoc
2m 36s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m 15s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
4m 45s

trunk passed

+1 :green_heart:
shadedclient
21m 45s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 28s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 41s

the patch passed

+1 :green_heart:
compile
22m 32s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
22m 32s

the patch passed

+1 :green_heart:
compile
20m 50s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
20m 50s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
3m 53s

the patch passed

+1 :green_heart:
mvnsite
3m 22s

the patch passed

+1 :green_heart:
javadoc
2m 19s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m  4s

hadoop-common in the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07.

+1 :green_heart:
javadoc
1m  3s

hadoop-tools_hadoop-aws-jdkPrivateBuild-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07 with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07 generated 0 new + 0 unchanged - 37 fixed = 0 total (was 37)

+1 :green_heart:
spotbugs
4m 47s

the patch passed

+1 :green_heart:
shadedclient
21m 45s

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

_ Other Tests _

+1 :green_heart:
unit
18m 57s

hadoop-common in the patch passed.

+1 :green_heart:
unit
2m 56s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
1m 20s

The patch does not generate ASF License warnings.

237m  8s

Subsystem
Report/Notes

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

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

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

uname
Linux b11b0706268e 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 42d43959455fea6446bcaa8e697820a1fd3f4301

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-common-project/hadoop-common hadoop-tools/hadoop-aws U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4965/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.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 56s

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 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 43s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
25m 37s

trunk passed

+1 :green_heart:
compile
23m 14s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
20m 57s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
4m  4s

trunk passed

+1 :green_heart:
mvnsite
3m 10s

trunk passed

+1 :green_heart:
javadoc
2m 39s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m  3s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
4m 35s

trunk passed

+1 :green_heart:
shadedclient
22m 47s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 32s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 44s

the patch passed

+1 :green_heart:
compile
22m 26s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
22m 26s

the patch passed

+1 :green_heart:
compile
20m 48s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
20m 48s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
4m  2s

the patch passed

+1 :green_heart:
mvnsite
3m 19s

the patch passed

+1 :green_heart:
javadoc
2m 20s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m  4s

hadoop-common in the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07.

+1 :green_heart:
javadoc
0m 58s

hadoop-tools_hadoop-aws-jdkPrivateBuild-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07 with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07 generated 0 new + 0 unchanged - 37 fixed = 0 total (was 37)

+1 :green_heart:
spotbugs
4m 40s

the patch passed

+1 :green_heart:
shadedclient
21m 49s

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

_ Other Tests _

+1 :green_heart:
unit
18m 50s

hadoop-common in the patch passed.

+1 :green_heart:
unit
3m  6s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
1m 21s

The patch does not generate ASF License warnings.

237m 43s

Subsystem
Report/Notes

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

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

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

uname
Linux 5baa2d236ee5 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 42d43959455fea6446bcaa8e697820a1fd3f4301

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-common-project/hadoop-common hadoop-tools/hadoop-aws U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4965/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.

Hi @mukund-thakur @steveloughran @dannycjones . Thanks for your reviews. I have made the recommended changes. Made 1 line javadoc comments for fields. And added the  tag in place of a new line. There are no warning issues now.
Please have a review if you can. Thanks.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 47s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
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 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 37s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
27m 12s

trunk passed

+1 :green_heart:
compile
23m 26s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
20m 53s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
4m  8s

trunk passed

+1 :green_heart:
mvnsite
3m  5s

trunk passed

+1 :green_heart:
javadoc
2m 20s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m 16s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
4m 47s

trunk passed

+1 :green_heart:
shadedclient
22m 14s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 29s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 43s

the patch passed

+1 :green_heart:
compile
22m 21s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
22m 21s

the patch passed

+1 :green_heart:
compile
23m 18s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
23m 18s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
4m  2s
/results-checkstyle-root.txt
root: The patch generated 1 new + 2 unchanged - 0 fixed = 3 total (was 2)

+1 :green_heart:
mvnsite
3m 11s

the patch passed

+1 :green_heart:
javadoc
2m 23s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m  4s

hadoop-common in the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07.

+1 :green_heart:
javadoc
1m  5s

hadoop-tools_hadoop-aws-jdkPrivateBuild-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07 with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07 generated 0 new + 0 unchanged - 37 fixed = 0 total (was 37)

+1 :green_heart:
spotbugs
4m 37s

the patch passed

+1 :green_heart:
shadedclient
21m 48s

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

_ Other Tests _

+1 :green_heart:
unit
19m  3s

hadoop-common in the patch passed.

+1 :green_heart:
unit
2m 55s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
1m 16s

The patch does not generate ASF License warnings.

240m 42s

Subsystem
Report/Notes

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

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

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

uname
Linux a7247575161a 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 263fd2894c80f25917a631bfe6bab52b6160dde4

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-common-project/hadoop-common hadoop-tools/hadoop-aws U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4965/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.

@steveloughran thanks for the review. I have made the changes of keeping the one line comment for fields. I have also added the  tag for new line in JavaDoc.


Update published files for 2.2-preview2

Verification build: https://dnceng.visualstudio.com/internal/_build/results?buildId=17225&view=logs


patrol drive --devices all infinity loop, stdbuf: command not found

Using: patrol drive --device=all
Got a infinity loop on:
Forwarding ports...
Full logs:
patrol drive --device=all --flavor dev
✓ Forwarded ports (21ms)
✓ Installed server (1.8s)
✓ Installed instrumentation (1.3s)
iproxy: /bin/sh: stdbuf: command not found
iproxy:
⠙ Forwarding ports... (3.3s)pl.leancode.automatorserver.ServerLoop:
⠦ Forwarding ports... (84.5s)

Got an error on iOS too maybe related:
➜  patrol devices
ONEPLUS (MY_ID_ANDROID)
iPhone (MY_ID_IOS)
➜ patrol drive -d MY_ID_IOS --flavor dev
Error: Device MY_ID_IOS is not attached

Works fine on MY_ID_ANDROID.

Hi @Kiruel, thanks for creating the issue!
Looks like the stdbuf program is not present on your machine. stdbuf is used by patrol_cli internally to facilitate port forwarding with iproxy.
You can install stdbuf (together with other GNU coreutils) it with Homebrew like this:
$ brew install coreutils

Let me know if this helps!

Checking if stdbuf is present should be done by patrol doctor. Related issue #173.

Using patrol doctor:
➜ patrol doctor
artifact path: /USER/ME/.cache/patrol (default)
➜

Nothing more than that.
After installing:
brew install coreutils

Got the same result:
➜  patrol drive -d MY_ID --flavor dev
Error: Device MY_ID is not attached

Ah, you also need to install iproxy. It's provided by this formula.
Sorry for the problems. I'll improve patrol doctor to be more friendly and useful :)

Still not work with iOS, even with iproxy installed:
➜  patrol drive -d MY_IOS_ID_DEVICE --flavor dev -v
Verbose mode enabled. More logs will be printed.
Error: Device MY_IOS_ID_DEVICE is not attached
#0      throwToolExit (package:patrol_cli/src/common/tool_exit.dart:5:3)
#1      DeviceFinder.findDevicesToUse (package:patrol_cli/src/features/devices/device_finder.dart:97:9)
#2      DeviceFinder.find (package:patrol_cli/src/features/devices/device_finder.dart:44:12)
<asynchronous suspension>
#3      DriveCommand.parseInput (package:patrol_cli/src/features/drive/drive_command.dart:169:29)
<asynchronous suspension>
#4      StagedCommand.run (package:patrol_cli/src/common/staged_command.dart:21:20)
<asynchronous suspension>
#5      CommandRunner.runCommand (package:args/command_runner.dart:209:13)
<asynchronous suspension>
#6      PatrolCommandRunner.runCommand (package:patrol_cli/src/command_runner.dart:232:18)
<asynchronous suspension>
#7      PatrolCommandRunner.run (package:patrol_cli/src/command_runner.dart:183:18)
<asynchronous suspension>
#8      patrolCommandRunner (package:patrol_cli/src/command_runner.dart:45:14)
<asynchronous suspension>
#9      main (file:///Users/MY_USER/.pub-cache/hosted/pub.dartlang.org/patrol_cli-0.7.3+1/bin/main.dart:6:20)
<asynchronous suspension>

Btw I'm on:
Apple M1 Max
macOS Monterey

Okay, this is strange. Very sorry for the problems!
Could you do flutter devices and patrol devices one after another and post output here?

➜  flutter devices
4 connected devices:

ONEPLUS A5010 (mobile)     • ID_ANDROID                • android-arm64  • Android 10 (API 29)
iPhone de ME (mobile)      • ID_IOS • ios              • iOS 16.1 20B79
macOS (desktop)            • macos                     • darwin-arm64   • macOS 12.5.1 21G83 darwin-arm
Chrome (web)               • chrome                    • web-javascript • Google Chrome 106.0.5249.119

• Error: ME's Apple Watch needs to connect to determine its availability. Check the connection between the device and its companion iPhone, and the connection between the iPhone and Xcode. Both devices may also need to be restarted and unlocked. (code 1)
➜  patrol devices
ONEPLUS A5010 (ID_ANDROID)
iPhone de ME (ID_IOS)

Oh boi, I know!
When running tests on iOS, you have to use the device's name instead of its ID. So you should do:
$ patrol drive -d 'iPhone de ME' --flavor dev -v

instead of:
$ patrol drive -d $ID_IOS --flavor dev -v

So sorry about this 🤦🏻  I'll fix this to let users use both the device name and the device ID.

Maybe this is why the --device=all not work as-well, but you find the problem ! :)
I find another issue but probably not related to this one:
➜  patrol drive -d "iPhone de Etienne" --flavor dev -v
Verbose mode enabled. More logs will be printed.
Forwarding ports...
Forwarded ports
Using artifact ios-0.7.4+1
Command line invocation:
/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild test -project AutomatorServer.xcodeproj -scheme AutomatorServer -sdk iphoneos -destination "platform=iOS,name=iPhone de Etienne"
User defaults from command line:
IDEPackageSupportUseBuiltinSCM = YES
Build settings from command line:
SDKROOT = iphoneos16.0
Resolve Package Graph
Fetching from https://github.com/apple/swift-nio-ssl.git (cached)
Fetching from https://github.com/apple/swift-atomics.git (cached)
Fetching from https://github.com/apple/swift-protobuf.git (cached)
Fetching from https://github.com/apple/swift-log.git (cached)
Fetching from https://github.com/apple/swift-nio-transport-services.git (cached)
Fetching from https://github.com/grpc/grpc-swift.git (cached)
Fetching from https://github.com/apple/swift-nio.git (cached)
Fetching from https://github.com/apple/swift-nio-http2.git (cached)
Fetching from https://github.com/apple/swift-nio-extras.git (cached)
Cloning local copy of package ‘swift-nio-ssl’
Checking out 2.22.1 of package ‘swift-nio-ssl’
Cloning local copy of package ‘grpc-swift’
Checking out 1.10.0 of package ‘grpc-swift’
Cloning local copy of package ‘swift-nio-extras’
Checking out 1.14.0 of package ‘swift-nio-extras’
Cloning local copy of package ‘swift-protobuf’
Checking out 1.20.1 of package ‘swift-protobuf’
Cloning local copy of package ‘swift-nio-http2’
Checking out 1.22.1 of package ‘swift-nio-http2’
Cloning local copy of package ‘swift-nio-transport-services’
Checking out 1.13.1 of package ‘swift-nio-transport-services’
Cloning local copy of package ‘swift-log’
Checking out 1.4.4 of package ‘swift-log’
Cloning local copy of package ‘swift-nio’
Checking out 2.41.1 of package ‘swift-nio’
Cloning local copy of package ‘swift-atomics’
Checking out 1.0.2 of package ‘swift-atomics’
Resolved source packages:
SwiftProtobuf: https://github.com/apple/swift-protobuf.git @ 1.20.1
swift-nio-http2: https://github.com/apple/swift-nio-http2.git @ 1.22.1
swift-atomics: https://github.com/apple/swift-atomics.git @ 1.0.2
swift-nio-ssl: https://github.com/apple/swift-nio-ssl.git @ 2.22.1
grpc-swift: https://github.com/grpc/grpc-swift.git @ 1.10.0
swift-nio-transport-services: https://github.com/apple/swift-nio-transport-services.git @ 1.13.1
swift-nio-extras: https://github.com/apple/swift-nio-extras.git @ 1.14.0
swift-nio: https://github.com/apple/swift-nio.git @ 2.41.1
swift-log: https://github.com/apple/swift-log.git @ 1.4.4
Prepare packages
2022-11-02 17:10:23.810 xcodebuild[52102:27332340] [MT] IDEFileReferenceDebug: [Load] <IDESwiftPackageCore.IDESwiftPackageSpecialFolderFileReference, 0x122f84650: name:Docs.docc path:group:Docs.docc> Failed to load container at path: /Users/etiennetheodore/Library/Developer/Xcode/DerivedData/AutomatorServer-fomtdpvbkcvkliantsawynmkhfhp/SourcePackages/checkouts/swift-protobuf/Sources/protoc-gen-swift/Docs.docc, Error: Error Domain=com.apple.dt.IDEContainerErrorDomain Code=6 "Cannot open "Docs.docc" as a "Swift Package Folder" because it is already open as a "Folder"." UserInfo={NSLocalizedDescription=Cannot open "Docs.docc" as a "Swift Package Folder" because it is already open as a "Folder".}

2022-11-02 17:10:23.823 xcodebuild[52102:27332340] [MT] IDEFileReferenceDebug: [Load] <IDESwiftPackageCore.IDESwiftPackageSpecialFolderFileReference, 0x122dc8560: name:Docs.docc path:group:Docs.docc> Failed to load container at path: /Users/etiennetheodore/Library/Developer/Xcode/DerivedData/AutomatorServer-fomtdpvbkcvkliantsawynmkhfhp/SourcePackages/checkouts/grpc-swift/Sources/protoc-gen-grpc-swift/Docs.docc, Error: Error Domain=com.apple.dt.IDEContainerErrorDomain Code=6 "Cannot open "Docs.docc" as a "Swift Package Folder" because it is already open as a "Folder"." UserInfo={NSLocalizedDescription=Cannot open "Docs.docc" as a "Swift Package Folder" because it is already open as a "Folder".}

2022-11-02 17:10:23.832 xcodebuild[52102:27332340] [MT] IDEFileReferenceDebug: [Load] <IDESwiftPackageCore.IDESwiftPackageSpecialFolderFileReference, 0x116a0d430: name:Docs.docc path:group:Docs.docc> Failed to load container at path: /Users/etiennetheodore/Library/Developer/Xcode/DerivedData/AutomatorServer-fomtdpvbkcvkliantsawynmkhfhp/SourcePackages/checkouts/grpc-swift/Sources/GRPC/Docs.docc, Error: Error Domain=com.apple.dt.IDEContainerErrorDomain Code=6 "Cannot open "Docs.docc" as a "Swift Package Folder" because it is already open as a "Folder"." UserInfo={NSLocalizedDescription=Cannot open "Docs.docc" as a "Swift Package Folder" because it is already open as a "Folder".}

2022-11-02 17:10:23.846 xcodebuild[52102:27332340] [MT] IDEFileReferenceDebug: [Load] <IDESwiftPackageCore.IDESwiftPackageSpecialFolderFileReference, 0x124cae950: name:Documentation.docc path:group:Documentation.docc> Failed to load container at path: /Users/etiennetheodore/Library/Developer/Xcode/DerivedData/AutomatorServer-fomtdpvbkcvkliantsawynmkhfhp/SourcePackages/checkouts/swift-log/Sources/Logging/Documentation.docc, Error: Error Domain=com.apple.dt.IDEContainerErrorDomain Code=6 "Cannot open "Documentation.docc" as a "Swift Package Folder" because it is already open as a "Folder"." UserInfo={NSLocalizedDescription=Cannot open "Documentation.docc" as a "Swift Package Folder" because it is already open as a "Folder".}

2022-11-02 17:10:23.855 xcodebuild[52102:27332340] [MT] IDEFileReferenceDebug: [Load] <IDESwiftPackageCore.IDESwiftPackageSpecialFolderFileReference, 0x122fddf20: name:Docs.docc path:group:Docs.docc> Failed to load container at path: /Users/etiennetheodore/Library/Developer/Xcode/DerivedData/AutomatorServer-fomtdpvbkcvkliantsawynmkhfhp/SourcePackages/checkouts/swift-nio-ssl/Sources/NIOSSL/Docs.docc, Error: Error Domain=com.apple.dt.IDEContainerErrorDomain Code=6 "Cannot open "Docs.docc" as a "Swift Package Folder" because it is already open as a "Folder"." UserInfo={NSLocalizedDescription=Cannot open "Docs.docc" as a "Swift Package Folder" because it is already open as a "Folder".}

2022-11-02 17:10:23.858 xcodebuild[52102:27332340] [MT] IDEFileReferenceDebug: [Load] <IDESwiftPackageCore.IDESwiftPackageSpecialFolderFileReference, 0x122ff7a20: name:Docs.docc path:group:Docs.docc> Failed to load container at path: /Users/etiennetheodore/Library/Developer/Xcode/DerivedData/AutomatorServer-fomtdpvbkcvkliantsawynmkhfhp/SourcePackages/checkouts/swift-nio-transport-services/Sources/NIOTransportServices/Docs.docc, Error: Error Domain=com.apple.dt.IDEContainerErrorDomain Code=6 "Cannot open "Docs.docc" as a "Swift Package Folder" because it is already open as a "Folder"." UserInfo={NSLocalizedDescription=Cannot open "Docs.docc" as a "Swift Package Folder" because it is already open as a "Folder".}

2022-11-02 17:10:23.901 xcodebuild[52102:27332340] [MT] IDEFileReferenceDebug: [Load] <IDESwiftPackageCore.IDESwiftPackageSpecialFolderFileReference, 0x116a568c0: name:Docs.docc path:group:Docs.docc> Failed to load container at path: /Users/etiennetheodore/Library/Developer/Xcode/DerivedData/AutomatorServer-fomtdpvbkcvkliantsawynmkhfhp/SourcePackages/checkouts/swift-nio-extras/Sources/NIOSOCKS/Docs.docc, Error: Error Domain=com.apple.dt.IDEContainerErrorDomain Code=6 "Cannot open "Docs.docc" as a "Swift Package Folder" because it is already open as a "Folder"." UserInfo={NSLocalizedDescription=Cannot open "Docs.docc" as a "Swift Package Folder" because it is already open as a "Folder".}

2022-11-02 17:10:23.902 xcodebuild[52102:27332340] [MT] IDEFileReferenceDebug: [Load] <IDESwiftPackageCore.IDESwiftPackageSpecialFolderFileReference, 0x122e0e760: name:Docs.docc path:group:Docs.docc> Failed to load container at path: /Users/etiennetheodore/Library/Developer/Xcode/DerivedData/AutomatorServer-fomtdpvbkcvkliantsawynmkhfhp/SourcePackages/checkouts/swift-nio-extras/Sources/NIOHTTPCompression/Docs.docc, Error: Error Domain=com.apple.dt.IDEContainerErrorDomain Code=6 "Cannot open "Docs.docc" as a "Swift Package Folder" because it is already open as a "Folder"." UserInfo={NSLocalizedDescription=Cannot open "Docs.docc" as a "Swift Package Folder" because it is already open as a "Folder".}

2022-11-02 17:10:23.903 xcodebuild[52102:27332340] [MT] IDEFileReferenceDebug: [Load] <IDESwiftPackageCore.IDESwiftPackageSpecialFolderFileReference, 0x122e08c00: name:Docs.docc path:group:Docs.docc> Failed to load container at path: /Users/etiennetheodore/Library/Developer/Xcode/DerivedData/AutomatorServer-fomtdpvbkcvkliantsawynmkhfhp/SourcePackages/checkouts/swift-nio-extras/Sources/NIOExtras/Docs.docc, Error: Error Domain=com.apple.dt.IDEContainerErrorDomain Code=6 "Cannot open "Docs.docc" as a "Swift Package Folder" because it is already open as a "Folder"." UserInfo={NSLocalizedDescription=Cannot open "Docs.docc" as a "Swift Package Folder" because it is already open as a "Folder".}

Computing target dependency graph and provisioning inputs
Create build description
Build description signature: 57275c4f6ff8667573ee87fbd6acccbc
Build description path: /Users/etiennetheodore/Library/Developer/Xcode/DerivedData/AutomatorServer-fomtdpvbkcvkliantsawynmkhfhp/Build/Intermediates.noindex/XCBuildData/57275c4f6ff8667573ee87fbd6acccbc-desc.xcbuild
note: Building targets in dependency order
/Users/etiennetheodore/.cache/patrol/ios-0.7.4+1/AutomatorServer.xcodeproj: error: No profiles for 'pl.leancode.AutomatorServerUITests.xctrunner' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'pl.leancode.AutomatorServerUITests.xctrunner'. Automatic signing is disabled and unable to generate a profile. To enable automatic signing, pass -allowProvisioningUpdates to xcodebuild. (in target 'AutomatorServerUITests' from project 'AutomatorServer')
/Users/etiennetheodore/.cache/patrol/ios-0.7.4+1/AutomatorServer.xcodeproj: error: No profiles for 'pl.leancode.AutomatorServer' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'pl.leancode.AutomatorServer'. Automatic signing is disabled and unable to generate a profile. To enable automatic signing, pass -allowProvisioningUpdates to xcodebuild. (in target 'AutomatorServer' from project 'AutomatorServer')
Test session results, code coverage, and logs:
/Users/etiennetheodore/Library/Developer/Xcode/DerivedData/AutomatorServer-fomtdpvbkcvkliantsawynmkhfhp/Logs/Test/Test-AutomatorServer-2022.11.02_17-10-23-+0100.xcresult
Testing failed:
No profiles for 'pl.leancode.AutomatorServerUITests.xctrunner' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'pl.leancode.AutomatorServerUITests.xctrunner'. Automatic signing is disabled and unable to generate a profile. To enable automatic signing, pass -allowProvisioningUpdates to xcodebuild.
No profiles for 'pl.leancode.AutomatorServer' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'pl.leancode.AutomatorServer'. Automatic signing is disabled and unable to generate a profile. To enable automatic signing, pass -allowProvisioningUpdates to xcodebuild.
Testing cancelled because the build failed.

** TEST FAILED **
Unhandled exception:
Exception: Test failed. See logs above. Also, consider running with --verbose.
#0      IOSDriver._runServerOnDevice.<anonymous closure> (package:patrol_cli/src/features/drive/platform/ios_driver.dart:218:9)
#1      List.forEach (dart:core-patch/growable_array.dart:416:8)
#2      ProcessListeners.listenStdErr.<anonymous closure> (package:patrol_cli/src/common/extensions/process.dart:50:14)
#3      _RootZone.runUnaryGuarded (dart:async/zone.dart:1586:10)
#4      _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:339:11)
#5      _BufferingStreamSubscription._add (dart:async/stream_impl.dart:271:7)
#6      _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:774:19)
#7      _StreamController._add (dart:async/stream_controller.dart:648:7)
#8      _StreamController.add (dart:async/stream_controller.dart:596:5)
#9      _Socket._onData (dart:io-patch/socket_patch.dart:2324:41)
#10     _RootZone.runUnaryGuarded (dart:async/zone.dart:1586:10)
#11     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:339:11)
#12     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:271:7)
#13     _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:774:19)
#14     _StreamController._add (dart:async/stream_controller.dart:648:7)
#15     _StreamController.add (dart:async/stream_controller.dart:596:5)
#16     new _RawSocket.<anonymous closure> (dart:io-patch/socket_patch.dart:1849:33)
#17     _NativeSocket.issueReadEvent.issue (dart:io-patch/socket_patch.dart:1322:14)
#18     _microtaskLoop (dart:async/schedule_microtask.dart:40:21)
#19     _startMicrotaskLoop (dart:async/schedule_microtask.dart:49:5)
#20     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:122:13)
#21     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:193:5)

Should I need more config before running on iOS ?

Should I need more config before running on iOS?

For physical iOS devices – unfortunately yes, you have to open the Xcode project at ~/.cache/patrol/ios-0.7.4+1 and set up signing. It's just a few clicks, but I admit, it's not perfect experience. We want to distribute prebuilt, resigned .app – this is tracked in #488.


Validators array set from controller not working

What Angular MDC version are you using?
0.41.2
What browser(s) is this bug affecting?
Chrome
What OS are you using?
OS mojave
What are the steps to reproduce the bug?
add the validators to demos/components/textfield-demo/textfield-demo.ts
demoForm = new FormGroup({
    username: new FormControl(
      { value: '', disabled: false }, [Validators.required, Validators.minLength(3)])
  });

remove them from the tag in
demos/components/textfield-demo/textfield-demo.html
<mdc-text-field #demoformInput formControlName="username" label="Username" outlined [helperText]="demoformHelper"></mdc-text-field>
What is the expected behavior?
the validation errors should display
What is the actual behavior?
the validators messages just don't show.
Any other information you believe would be useful?
I actually tested in the example, by changing the code in stack blitz.

@jpinedapetplan Thanks for reporting this.
This feature will be included as part of #1323 by injecting an error state.

@jpinedapetplan Good news, I added detection of Validators.required during initialization without impacting performance.
reference: #1607

That's really awesome! I would love to know how you test performance on
initialize?
On Sat, Dec 15, 2018 at 3:12 PM Dominic Carretto<EMAIL_ADDRESS>wrote:

@jpinedapetplan https://github.com/jpinedapetplan Good news, I added
detection of Validators.required during initialization without impacting
performance.
reference: #1607 https://github.com/trimox/angular-mdc-web/issues/1607
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/trimox/angular-mdc-web/issues/1549#issuecomment-447594744,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Akc5CCnUCPEyI7xtAw0R9t6hsnqdzlINks5u5VeagaJpZM4YpzFp
.

--
Juan Pineda
Sr Dev
pet parent to  mr  kitty (9 year old cat)
https://www.gopetplan.com
petplan pet insurance
3805 west chester pike suite 240
newtown square pa 19073
tel +1<PHONE_NUMBER>
www.gopetplan.com


Customizable algorithm suite defaulting to FIPS compliance

fixes https://github.com/quarkiverse/quarkus-cxf/issues/1173

The ws-trust native failure is a a bug in my code and I'll take care of it.

@ppalaga @ffang
I'd like to ask for help with the native failure.
I think that I see, why the test is failing, but I'm not sure how to fix it correctly.
Let me explain (native mode):

During the build, the map AlgorithmSuite.ALGORITHM_SUITE_TYPES - it is created because it is static field (java identifier of the map is<PHONE_NUMBER>)
The custom alghoritm suite is created in the recorder (part of this PR) in the static init into the same map  (java identifier of the map is<PHONE_NUMBER>)
During test execution the new map is created

2024-01-12 10:33:45,915 INFO  [org.apa.cxf.wsd.ser.fac.ReflectionServiceFactoryBean] (main) Creating Service {https://quarkiverse.github.io/quarkiverse-docs/quarkus-cxf/test/ws-trust}TrustHelloService from WSDL: http://localhost:8081/services/jaxws-samples-wsse-policy-trust/TrustHelloService?wsdl
(java identifier of the map is **888350069**)

The new map does not contain the custom alg. suite, therefore the execution fails.

I saved the stacktrace of the second map cration:
        at org.apache.wss4j.policy.model.AlgorithmSuite.<clinit>(AlgorithmSuite.java:34)
        at org.apache.cxf.ws.security.policy.WSSecurityPolicyLoader.registerBuilders(WSSecurityPolicyLoader.java:275)
        at org.apache.cxf.ws.security.policy.WSSecurityPolicyLoader.<init>(WSSecurityPolicyLoader.java:106)
        at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77)
        at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499)
        at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480)
        at org.apache.cxf.bus.extension.Extension.load(Extension.java:218)
        at org.apache.cxf.bus.extension.ExtensionManagerImpl.loadAndRegister(ExtensionManagerImpl.java:198)
        at org.apache.cxf.bus.extension.ExtensionManagerImpl.getBeansOfType(ExtensionManagerImpl.java:333)
        at org.apache.cxf.ws.policy.AssertionBuilderRegistryImpl.loadDynamic(AssertionBuilderRegistryImpl.java:95)
        at org.apache.neethi.AssertionBuilderFactoryImpl.build(AssertionBuilderFactoryImpl.java:109)
        at org.apache.neethi.PolicyBuilder.processOperationElement(PolicyBuilder.java:224)
        at org.apache.neethi.PolicyBuilder.getAllOperator(PolicyBuilder.java:184)
        at org.apache.neethi.PolicyBuilder.processOperationElement(PolicyBuilder.java:217)
        at org.apache.neethi.PolicyBuilder.getExactlyOneOperator(PolicyBuilder.java:180)
        at org.apache.neethi.PolicyBuilder.processOperationElement(PolicyBuilder.java:215)
        at org.apache.neethi.PolicyBuilder.getPolicyOperator(PolicyBuilder.java:174)
        at org.apache.neethi.PolicyBuilder.getPolicy(PolicyBuilder.java:124)
        at org.apache.cxf.ws.policy.attachment.wsdl11.Wsdl11AttachmentPolicyProvider.getElementPolicy(Wsdl11AttachmentPolicyProvider.java:197)
        at org.apache.cxf.ws.policy.attachment.wsdl11.Wsdl11AttachmentPolicyProvider.getElementPolicy(Wsdl11AttachmentPolicyProvider.java:170)
        at org.apache.cxf.ws.policy.attachment.wsdl11.Wsdl11AttachmentPolicyProvider.getElementPolicy(Wsdl11AttachmentPolicyProvider.java:163)
        at org.apache.cxf.ws.policy.attachment.wsdl11.Wsdl11AttachmentPolicyProvider.getEffectivePolicy(Wsdl11AttachmentPolicyProvider.java:77)
        at org.apache.cxf.ws.policy.PolicyEngineImpl.getAggregatedServicePolicy(PolicyEngineImpl.java:461)
        at org.apache.cxf.ws.policy.EndpointPolicyImpl.initializePolicy(EndpointPolicyImpl.java:151)
        at org.apache.cxf.ws.policy.EndpointPolicyImpl.initialize(EndpointPolicyImpl.java:140)
        at org.apache.cxf.ws.policy.PolicyEngineImpl.createEndpointPolicyInfo(PolicyEngineImpl.java:614)
        at org.apache.cxf.ws.policy.PolicyEngineImpl.getEndpointPolicy(PolicyEngineImpl.java:326)
        at org.apache.cxf.ws.policy.PolicyEngineImpl.getClientEndpointPolicy(PolicyEngineImpl.java:313)
        at org.apache.cxf.ws.policy.PolicyDataEngineImpl.getClientEndpointPolicy(PolicyDataEngineImpl.java:61)
        at org.apache.cxf.transport.http.HTTPConduit.updateClientPolicy(HTTPConduit.java:372)
        at org.apache.cxf.transport.http.HTTPConduit.updateClientPolicy(HTTPConduit.java:392)
        at org.apache.cxf.transport.http.HTTPConduit.getClient(HTTPConduit.java:938)
        at org.apache.cxf.transport.http.HTTPConduit.configureConduitFromEndpointInfo(HTTPConduit.java:414)
        at org.apache.cxf.transport.http.HTTPConduit.finalizeConfig(HTTPConduit.java:494)
        at org.apache.cxf.transport.http.HTTPTransportFactory.getConduit(HTTPTransportFactory.java:257)
        at org.apache.cxf.binding.soap.SoapTransportFactory.getConduit(SoapTransportFactory.java:226)
        at org.apache.cxf.binding.soap.SoapTransportFactory.getConduit(SoapTransportFactory.java:233)
        at org.apache.cxf.endpoint.AbstractConduitSelector.createConduit(AbstractConduitSelector.java:144)
        at org.apache.cxf.endpoint.AbstractConduitSelector.getSelectedConduit(AbstractConduitSelector.java:108)
        at org.apache.cxf.endpoint.UpfrontConduitSelector.prepare(UpfrontConduitSelector.java:63)
        at org.apache.cxf.endpoint.ClientImpl.prepareConduitSelector(ClientImpl.java:885)
        at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:523)
        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:439)
        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:354)
        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:312)
        at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
        at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:140)
        at jdk.proxy2/jdk.proxy2.$Proxy91.sayHello(Unknown Source)
        at io.quarkiverse.cxf.it.ws.trust.CxfWsTrustTest.programmaticSts(CxfWsTrustTest.java:103)

In the jvm execution, there is only 1 map (created by the recorder) and all works.
I'm a little bit confused, why is the recorder adding values to the statically created map but the client from the test creates anew default map? (and  thus ignoring the custom modification)

Per

@ppalaga @ffang I'd like to ask for help with the native failure. I think that I see, why the test is failing, but I'm not sure how to fix it correctly.
Let me explain (native mode):

During the build, the map AlgorithmSuite.ALGORITHM_SUITE_TYPES - it is created because it is static field (java identifier of the map is<PHONE_NUMBER>)
The custom alghoritm suite is created in the recorder (part of this PR) in the static init into the same map  (java identifier of the map is<PHONE_NUMBER>)
During test execution the new map is created

2024-01-12 10:33:45,915 INFO  [org.apa.cxf.wsd.ser.fac.ReflectionServiceFactoryBean] (main) Creating Service {https://quarkiverse.github.io/quarkiverse-docs/quarkus-cxf/test/ws-trust}TrustHelloService from WSDL: http://localhost:8081/services/jaxws-samples-wsse-policy-trust/TrustHelloService?wsdl
(java identifier of the map is **888350069**)

The new map does not contain the custom alg. suite, therefore the execution fails.

I saved the stacktrace of the second map cration:
        at org.apache.wss4j.policy.model.AlgorithmSuite.<clinit>(AlgorithmSuite.java:34)
        at org.apache.cxf.ws.security.policy.WSSecurityPolicyLoader.registerBuilders(WSSecurityPolicyLoader.java:275)
        at org.apache.cxf.ws.security.policy.WSSecurityPolicyLoader.<init>(WSSecurityPolicyLoader.java:106)
        at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77)
        at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499)
        at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480)
        at org.apache.cxf.bus.extension.Extension.load(Extension.java:218)
        at org.apache.cxf.bus.extension.ExtensionManagerImpl.loadAndRegister(ExtensionManagerImpl.java:198)
        at org.apache.cxf.bus.extension.ExtensionManagerImpl.getBeansOfType(ExtensionManagerImpl.java:333)
        at org.apache.cxf.ws.policy.AssertionBuilderRegistryImpl.loadDynamic(AssertionBuilderRegistryImpl.java:95)
        at org.apache.neethi.AssertionBuilderFactoryImpl.build(AssertionBuilderFactoryImpl.java:109)
        at org.apache.neethi.PolicyBuilder.processOperationElement(PolicyBuilder.java:224)
        at org.apache.neethi.PolicyBuilder.getAllOperator(PolicyBuilder.java:184)
        at org.apache.neethi.PolicyBuilder.processOperationElement(PolicyBuilder.java:217)
        at org.apache.neethi.PolicyBuilder.getExactlyOneOperator(PolicyBuilder.java:180)
        at org.apache.neethi.PolicyBuilder.processOperationElement(PolicyBuilder.java:215)
        at org.apache.neethi.PolicyBuilder.getPolicyOperator(PolicyBuilder.java:174)
        at org.apache.neethi.PolicyBuilder.getPolicy(PolicyBuilder.java:124)
        at org.apache.cxf.ws.policy.attachment.wsdl11.Wsdl11AttachmentPolicyProvider.getElementPolicy(Wsdl11AttachmentPolicyProvider.java:197)
        at org.apache.cxf.ws.policy.attachment.wsdl11.Wsdl11AttachmentPolicyProvider.getElementPolicy(Wsdl11AttachmentPolicyProvider.java:170)
        at org.apache.cxf.ws.policy.attachment.wsdl11.Wsdl11AttachmentPolicyProvider.getElementPolicy(Wsdl11AttachmentPolicyProvider.java:163)
        at org.apache.cxf.ws.policy.attachment.wsdl11.Wsdl11AttachmentPolicyProvider.getEffectivePolicy(Wsdl11AttachmentPolicyProvider.java:77)
        at org.apache.cxf.ws.policy.PolicyEngineImpl.getAggregatedServicePolicy(PolicyEngineImpl.java:461)
        at org.apache.cxf.ws.policy.EndpointPolicyImpl.initializePolicy(EndpointPolicyImpl.java:151)
        at org.apache.cxf.ws.policy.EndpointPolicyImpl.initialize(EndpointPolicyImpl.java:140)
        at org.apache.cxf.ws.policy.PolicyEngineImpl.createEndpointPolicyInfo(PolicyEngineImpl.java:614)
        at org.apache.cxf.ws.policy.PolicyEngineImpl.getEndpointPolicy(PolicyEngineImpl.java:326)
        at org.apache.cxf.ws.policy.PolicyEngineImpl.getClientEndpointPolicy(PolicyEngineImpl.java:313)
        at org.apache.cxf.ws.policy.PolicyDataEngineImpl.getClientEndpointPolicy(PolicyDataEngineImpl.java:61)
        at org.apache.cxf.transport.http.HTTPConduit.updateClientPolicy(HTTPConduit.java:372)
        at org.apache.cxf.transport.http.HTTPConduit.updateClientPolicy(HTTPConduit.java:392)
        at org.apache.cxf.transport.http.HTTPConduit.getClient(HTTPConduit.java:938)
        at org.apache.cxf.transport.http.HTTPConduit.configureConduitFromEndpointInfo(HTTPConduit.java:414)
        at org.apache.cxf.transport.http.HTTPConduit.finalizeConfig(HTTPConduit.java:494)
        at org.apache.cxf.transport.http.HTTPTransportFactory.getConduit(HTTPTransportFactory.java:257)
        at org.apache.cxf.binding.soap.SoapTransportFactory.getConduit(SoapTransportFactory.java:226)
        at org.apache.cxf.binding.soap.SoapTransportFactory.getConduit(SoapTransportFactory.java:233)
        at org.apache.cxf.endpoint.AbstractConduitSelector.createConduit(AbstractConduitSelector.java:144)
        at org.apache.cxf.endpoint.AbstractConduitSelector.getSelectedConduit(AbstractConduitSelector.java:108)
        at org.apache.cxf.endpoint.UpfrontConduitSelector.prepare(UpfrontConduitSelector.java:63)
        at org.apache.cxf.endpoint.ClientImpl.prepareConduitSelector(ClientImpl.java:885)
        at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:523)
        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:439)
        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:354)
        at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:312)
        at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
        at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:140)
        at jdk.proxy2/jdk.proxy2.$Proxy91.sayHello(Unknown Source)
        at io.quarkiverse.cxf.it.ws.trust.CxfWsTrustTest.programmaticSts(CxfWsTrustTest.java:103)

In the jvm execution, there is only 1 map (created by the recorder) and all works.
I'm a little bit confused, why is the recorder adding values to the statically created map but the client from the test creates anew default map? (and thus ignoring the custom modification)

Perhaps different bus? which has to be customized as well? (but then the execution should fail in JVM as well)

I forgot to put a reason of the failure here (the custom alg suite is not registered):
[ERROR] io.quarkiverse.cxf.it.ws.trust.CxfWsTrustIT.programmaticSts -- Time elapsed: 1.006 s <<< ERROR!
jakarta.xml.ws.soap.SOAPFaultException: Algorithm suite "CustomizedAlgorithmSuite" is not registered
        at org.apache.cxf.jaxws.JaxWsClientProxy.mapException(JaxWsClientProxy.java:195)

@ppalaga  thanks for the review, I'll fix all items.
I understand that using Fips in the name of the customAlgSuite would make sense. On the other hand, if user changes attributes for its own purpose, so it won't work on fips (and there will be no FIPS in user's environment), the word FIPS would be misleading

What about the name QuarkusCxfCustomAlgorithmSuite (instead of suggested QuarkusCxfFipsAlgorithmSuite)?

Those are all valid proposals, however, after studying the PR in more depth, I am not sure it is a good idea to make it like this. Here is why:
The set of AlgSuites is defined in version 1.2 of the XML Schema for the policy files: http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/ws-securitypolicy-1.2.xsd If you CTRL-F for "7.1 AlgorithmSuite Assertion", you'll see all suites defined in https://github.com/apache/ws-wss4j/blob/master/policy/src/main/java/org/apache/wss4j/policy/model/AlgorithmSuite.java#L41-L200
The policies are used on both server and client side to configure the security and those standardized AlgSuites guarrantee that clients and servers will encrypt/sign the messages in an expected, mutually comprehensible way, across all vendors.
Introducing an AlgSuite that is configurable through an intransparent config of the client or server would break that interoperability. Actually only Quarkus CXF clients and servers could communicate and only those ones whose custom-algorithm-suite is configured in the same way.
Saying that introducing any new AlgSuite would make the policy files non-compliant with the schema would be true, but there is already a precedent that CXF introduced new AlgSuites in response to a CVE: https://coheigea.blogspot.com/2012/04/note-on-cve-2011-1096.html I wonder wheter we should not try the same: Introduce one or more FIPS-compliant AlgSuites to https://github.com/apache/cxf/blob/main/rt/ws/security/src/main/java/org/apache/cxf/ws/security/policy/custom/DefaultAlgorithmSuiteLoader.java#L74-L114 In that way, the new suites would be at least comprehensible for clients and servers based on CXF.
WDYT?

Those are all valid proposals, however, after studying the PR in more depth, I am not sure it is a good idea to make it like this. Here is why:
The set of AlgSuites is defined in version 1.2 of the XML Schema for the policy files: http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/ws-securitypolicy-1.2.xsd If you CTRL-F for "7.1 AlgorithmSuite Assertion", you'll see all suites defined in https://github.com/apache/ws-wss4j/blob/master/policy/src/main/java/org/apache/wss4j/policy/model/AlgorithmSuite.java#L41-L200
The policies are used on both server and client side to configure the security and those standardized AlgSuites guarrantee that clients and servers will encrypt/sign the messages in an expected, mutually comprehensible way, across all vendors.
Introducing an AlgSuite that is configurable through an intransparent config of the client or server would break that interoperability. Actually only Quarkus CXF clients and servers could communicate and only those ones whose custom-algorithm-suite is configured in the same way.
Saying that introducing any new AlgSuite would make the policy files non-compliant with the schema would be true, but there is already a precedent that CXF introduced new AlgSuites in response to a CVE: https://coheigea.blogspot.com/2012/04/note-on-cve-2011-1096.html I wonder wheter we should not try the same: Introduce one or more FIPS-compliant AlgSuites to https://github.com/apache/cxf/blob/main/rt/ws/security/src/main/java/org/apache/cxf/ws/security/policy/custom/DefaultAlgorithmSuiteLoader.java#L74-L114 In that way, the new suites would be at least comprehensible for clients and servers based on CXF.
WDYT?

Hi @ppalaga ,
This is a good proposal and I'm actually thinking about the same thing.
Created https://issues.apache.org/jira/browse/CXF-8971 to track this enhancement.
@JiriOndrusek , please feel free to send a PR there!
But probably this PR for quarkus-cxf still stands as don't need to wait for CXF side fix and release.
Thanks!
Freeman

Hi @ppalaga ,
thanks for the proposal.
To clarify some details. Suggested solution is to move "customization" mechanism into cxf.
If so, we can keep alg suite config parameters (after refactor to fixed ones) to configure such  algSuirta via cxf parameters.
@ffang I try to prepare a draft for cxf to fix issue  https://issues.apache.org/jira/browse/CXF-8971.

As I'm thinking about the customizationAlgSuite in Cxf, what about addition of a FIPS approved algSuite among https://github.com/apache/cxf/blob/main/rt/ws/security/src/main/java/org/apache/cxf/ws/security/policy/custom/DefaultAlgorithmSuiteLoader.java#L74-L114
That would make usage of the suite much easier for the users. I can imagine, that in the future there can servers customized with ALG1 or ALG2 (both works for FIPS). It might be inconvenient for the clients (because every server requires different custom alg). If there is a default fips suite, the usage can be much easier (the customization would still exist, but might not be needed in so many cases)

Hi Jiri,
Yes, the current CXF DefaultAlgorithmSuiteLoader is a good place. You can add a new policy with name "CustomerizedAlgorithmSuite" which has default FIPS compliant paramenters so it can work OOTB with zero configuration, but these parameters should be configurable/overridable from CXF bus properties. I believe you can define new added necessary properties name in org.apache.cxf.ws.security.SecurityConstants class with prefix like "ws-security.policy".
Cheers
Freeman

Created https://issues.apache.org/jira/browse/CXF-8971 to track this enhancement.

I commented there

PR for CXF is prepared (https://github.com/apache/cxf/pull/1660). I plan to refactor this PR to leverage this change (only minimum of this PR will stay as is)

This PR has to be reworked, because the customizableAlgSuite is proposed on the CXF source instead here. See https://github.com/apache/cxf/pull/1660

@JiriOndrusek this PR builds against the staging repo of CXF 4.0.4 that is under vote right now.
Would you like to rebase this PR on top of it?
I'd like to release Quarkus CXF 3.8.1 on Friday once the CXF 4.0.4 artifacts are available on Central.

@JiriOndrusek this PR builds against the staging repo of CXF 4.0.4 that is under vote right now. Would you like to rebase this PR on top of it? I'd like to release Quarkus CXF 3.8.1 on Friday once the CXF 4.0.4 artifacts are available on Central.

Thanks for he upgrading PR, I'll look at that and rebase this PR.

@ppalaga @ffang Is the staging repo working now? I can not download any artifact from it and the url does not work in the browser: https://repository.apache.org/content/repositories/orgapachecxf-1196

Shouldn't it be https://repository.apache.org/content/repositories/orgapachecxf-1197/ ?

I switch staging repo to https://repository.apache.org/content/repositories/orgapachecxf-1197/ to make the CI pass (new repo is part of the second voting)

Thanks for rabasing, @JiriOndrusek !
I took over you commit to https://github.com/quarkiverse/quarkus-cxf/pull/1274
and added some fixups https://github.com/quarkiverse/quarkus-cxf/pull/1274/commits/78e12a8346118f1a3b9f6b24cd70c5ee46bc78f8 - could you please review there?
I'd also add a bit more docs text to the new options.

Replaced by https://github.com/quarkiverse/quarkus-cxf/pull/1274


Consider using queue interprop as abstraction for queues

Hello!
Please look at https://github.com/queue-interop/queue-interop project. Using interfaces from it allows us reuse some implementations like enqueue, which supports a lot of transports. You can outsource some code

Hi!
Thank you. I will look into it in 2020.


Do not set pixel-width for  tags

Setting min-width to a pixel-value on the  tag breaks the layout if the -tag is inside a nested grid. It should be enough to have width: 100%.
Consider this example:
<container>
   <row>
      <columns large="10">
         <row>
            <columns large="6">
               Some centered content
            </columns>
            <columns large="6">
               Some centered content
            </columns>
         </row>
      </columns>
      <columns large="2">
         Some side-content
      </columns>
   </row>
</container>

Basing the width of the  tags on the size of the containing column doesn't work, since they are within a column with size 6 inside a column with size 10.

I have now cleaned up the commit. Any chance this might be merged?

Hi @Stadly,
Do you have a reproducible testcase where we can see this problem?

Did you try the example in the first post? That should show the problem.

I did not yet time to do that (setting up a new project with this). A complete reproducible testcases makes it easier for us to test it. Because I do not have so much time normally.

Not sure how to make it more reproducible. Just create a file inside src/pages/ with the contents from the first post and build the email. Opening the corresponding file in dist/ will show the issue.
What do you have in mind to make it more easy for you to test?

What do you have in mind to make it more easy for you to test?

A complete repo with this setup.


Workplanes from Locations

If nothing is provided to Workplanes use the existing locations to define new planes.

Complete with commit https://github.com/gumyr/build123d/commit/c12309772de66cf8d45997052c99319deac4a8ce


How to make some context/state available to components

This is going to be weird, hard to explain, and likely involve sharing some broken code.
I want to do something similar to hooks. Namely, components get get some arguments from props and some from the outside world. In my case, I want to usewired and the dependency injector I wrote for it. With this, lookups are done in the context of a "container". The container would roughly match to each call to the html() function for a tagged template.
I have a working example by stepping in where the html function (wrapped by the htm) does return tag_factory(tag, children=children, **props). But it requires the per-request container to be a global.
I first tried converting the htm decorator to a class, so the instance have some state, and let the __call__ do the wrapping. But the tagged code in def __tag doesn't like having an instance as the first arg, when @htm is applied to the __call__.
I then tried writing a custom htm decorator and taking control of the calling. With this, rather than have some stateful callable, I'd do functions that pass arguments (the container). But def __htm at the end returns return htm_eval(h1, ops, values) and this intermediate function drops my attempt to get the container into my html function.
I know what's at the finish line for this and it is quite compelling. So I'm motivated to keep trying. But I'm quite certain that some paths are worse than others.

Perhaps I should give an example of what would be ideal.
result = str(html("""
<{Heading}><//>
""", container=container))

...and then:
@htm
def html(tag, props, children, container=None):
    ...

Meaning, a way to get arbitrary values into to the rendering. There are a few challenges:

The htm decorator doesn't like this. But I will be writing a custom decorator anyway (for my registry.)
The trip through tagged doesn't do arbitrary **kwargs
html_eval doesn't collect **kwargs and pass along to the wrapped function

Solved this in the rendering layer in viewdom


Add op_return to bitcoin-magazine/bitcoin-explained

This PR adds OP_RETURN transcript to the bitcoin-magazine/bitcoin-explained directory.

@kouloumos Thanks for the feedback. I will make the required changes

Great work, thank you @realdezzy! We hope that you learn something out of this and that we will see more transcripts from you in the future!
If you haven't done that already, We'd love to hear your feedback for this project and your experience as a reviewer as we are trying to improve and make the experience better for all.


mongodb testcontainers cannot run in GitLab - while postgres can

Describe the bug
Launching MongoDB Testcontainer in GitLab with dind yields error: "Exception: port mapping for container xxxx and port 27017 is not available"  - i.e.:
"testcontainers.core.exceptions.TimeoutException: Wait time (120s) exceeded for get_exposed_port(args: (27017,), kwargs {}). Exception: port mapping for container afa0edc97197698ae51ad40d64a8f2b37de2a52027d3cb9f4c9e9959442a9b8d and port 27017 is not available"
Expected test to run as it does in the local test with docker.
Tried running the postgres testcontainer in the same test file and pipeline, which works. So am suspecting an issue with the mongodb testcontainer implementation.
To Reproduce
Add the test from here:
https://github.com/testcontainers/testcontainers-python/blob/928af5a88393d8223a0d5a55e9378941826997ec/mongodb/tests/test_mongodb.py#L57
And the postgres test which works from here:
https://testcontainers-python.readthedocs.io/en/latest/postgres/README.html
And run in GitLab pipeline with:
.test:
  services:
     - name: docker:dind
       command: ["--tls=false"]

  variables:
    DOCKER_HOST: "tcp://docker:2375"
    DOCKER_TLS_CERTDIR: ""
    DOCKER_DRIVER: overlay2

  image: python:3.12.0-slim-bookworm

  script:
    - python -m pip install poetry
    - poetry install --with dev
    - poetry run pytest .

Runtime environment
Running GitLab Community version 16.4.0 with GitLab runners and docker in docker.
Testcontainers version 3.7.1
Python 3.12.0
pymongo 4.5.0

https://github.com/testcontainers/testcontainers-python/issues/401
I was having issue with mongo this may help
currently writing as test to support the bug I raised


cap: drop MKNOD, NET_RAW, SETFCAP, SYS_CHROOT, AUDIT_WRITE by default

Fix #10434

Why do we also want to drop MKNOD, SETFCAP, SYS_CHROOT, and AUDIT_WRITE?

Why do we also want to drop MKNOD, SETFCAP, SYS_CHROOT, and AUDIT_WRITE?

Because CRI-O has already dropped them
https://github.com/cri-o/cri-o/blob/v1.30.3/internal/config/capabilities/capabilities_linux.go#L15-L27

Need to look into this.
I don't see why we would block SYS_CHROOT.
AUDIT_WRITE may be problematic, but maybe something has changed since https://github.com/moby/moby/issues/6770.
Also not sure why we would block MKNOD at all.
Last I knew kube-proxy requires NET_RAW, though I suppose ppl should set this on the pod spec.
This one I am generally in favor of removing from the default cap list, though it may break ping.

This one I am generally in favor of removing from the default cap list, though it may break ping.

For ping, the cap is set on the binary. So, I dont think this change should cause any issues with ping.

Because CRI-O has already dropped them

Do we have context on why they made these choices?

For ping, the cap is set on the binary. So, I dont think this change should cause any issues with ping.

File capabilities are still restricted by the bounding set, so if we remove NET_RAW from the bounding set even a setfcap'd binary like ping will not be able to gain that capability.

I don't see why we would block SYS_CHROOT.

  I don't know whether pivot_root would be as useful, but that could be blocked by seccomp.

Also not sure why we would block MKNOD at all.

The devices cgroup should restrict device node creation sufficiently.  Is there some other case where we'd want to drop MKNOD?

It probably makes more sense to have a single PR for capability change. I was going to create one just to remove NET_RAW.


Disallow generic object and array of object parameter types (temporarily)

CARML makes heavy use of "object" and "array of object" parameter types. Here's an example in the network/virtual-network module:

definition: https://github.com/Azure/bicep-registry-modules/blob/main/modules/network/virtual-network/main.bicep#L11
usage: https://github.com/Azure/bicep-registry-modules/blob/main/modules/network/virtual-network/main.bicep#L106
instantiation example: https://github.com/Azure/bicep-registry-modules/blob/main/modules/network/virtual-network/README.md#example-2

While this is good for flexibility, it makes consumption of the module impossible unless you look at the source code or have an example reference.
I recommend we block this pattern until we have full support for custom types, which is tracked here:
https://github.com/Azure/bicep/issues/4158
That may be overly strict. We can wait until we get more feedback before making this decision, but I'd like to get out in front of it or "limit the damage" as much as possible.

For now, we are going to leave this issue open to collect feedback, but we won't block this pattern for now. At least at the start of the bicep registry, we'd prefer to be more open with patterns than strict in the interest of learning more quickly.
We are going to clarify in docs that early adopters of public registry code should expect changes as we learn about better ways to author modules for broad consumption/add new features to bicep to support that. This should simply manifest as new versions of a module in most cases, but may require us to re-organize the repo which would be a more drastic change.
FYI @MrMCake

No longer relevant since we now have the functionality for user-defined types (though it is not yet enabled by default)


We should get rid of deprecations

We have some deprecated dependencies, that is printed by npm:
npm WARN deprecated<EMAIL_ADDRESS>This functionality has been moved to @npmcli/fs
npm WARN deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm WARN deprecated<EMAIL_ADDRESS>Cuid and other k-sortable and non-cryptographic ids (Ulid, ObjectId, KSUID, all UUIDs) are all insecure. Use @paralleldrive/cuid2 instead.

@marcopiraccini on which package or which directory command is executed that displays these warnings?

@marcopiraccini after latest pull the error above is not displayed and deprecated dependencies warning is gone

Done


Back navigation link

Closes #136

Codecov Report

Merging #141 (2e43572) into main (2b1afdd) will decrease coverage by 1.09%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #141      +/-   ##
==========================================
- Coverage   79.06%   77.97%   -1.10%
==========================================
  Files          40       44       +4
  Lines         301      336      +35
  Branches       89       94       +5
==========================================
+ Hits          238      262      +24
- Misses         55       64       +9
- Partials        8       10       +2

Impacted Files
Coverage Δ

src/lib/shared/ui/icon-button.svelte
100.00% <ø> (ø)

...s/podcast-episodes/ui/podcast-episodes-page.svelte
100.00% <100.00%> (ø)

src/lib/shared/lib/jest-hacks/mock-component.ts
100.00% <100.00%> (ø)

...rc/lib/features/like-episode/ui/like-button.svelte
41.66% <0.00%> (ø)

src/lib/widgets/episode/ui/episode-card.svelte
60.00% <0.00%> (ø)

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 2b1afdd...2e43572. Read the comment docs.


[QST] How to add pre-trained embeddings?

❓ Questions & Help
I have a working model, but I would like to add  pre-trained item embeddings as a feature.
I've seen 572, but I'm unsure how to use this and what changes need to be made to the schema to accommodate the embeddings.
Is there documentation or an example of this?

Currently we cannot add pre-trained embeddings as a feature which requires dataloader to take 3D arrays and we dont support that yet.  you can add them to embedding layer. for that you can check this unit test example.
We dont have an example yet for adding pre-trained embeddings to embedding layer either, we will create one in the upcoming weeks.

We dont have an example yet for adding pre-trained embeddings to embedding layer either, we will create one in the upcoming weeks.

Is there any news with the support of adding text embeddings to the models? Thanks!

We dont have an example yet for adding pre-trained embeddings to embedding layer either, we will create one in the upcoming weeks.

Is there any news with the support of adding text embeddings to the models? Thanks!

Hi @rnyak,
I'm also still interested in this.
Has an example been completed?

We dont have an example yet for adding pre-trained embeddings to embedding layer either, we will create one in the upcoming weeks.

Is there any news with the support of adding text embeddings to the models? Thanks!

Hi @rnyak ,
I'm also still interested in this.
Has an example been completed?

Not yet, the functionality is being developed currently. Once it is ready we will create an example.

Hi @rnyak,
I was wondering if the "add text embeddings to the models" functionality is ready.
If yes, do you have a example notebook to share?
Thank you!

Hi I'm also interested in this, just want to check in if there are any updates. Thank you!


Extra sensors temperature not being sent to MQTT

I have a WS-5000 station with a few extra temperature sensors. I can see all of the data from the sensors aside from the temperature. I captured the request from the station to the docker container and I can see that the data is there. Here's an example from tcpdump:
GET /data/?stationtype=AMBWeatherV4.3.3&PASSKEY=<removed>&dateutc=2022-09-16+15:29:06&tempinf=63.3&battin=1&humidityin=59&baromrelin=29.510&baromabsin=29.510&tempf=62.2&battout=1&battrain=1&humidity=56&winddir=261&winddir_avg10m=327&windspeedmph=0.0&windspdmph_avg10m=1.6&windgustmph=2.2&maxdailygust=6.3&hourlyrainin=0.000&eventrainin=0.000&dailyrainin=0.000&weeklyrainin=0.890&monthlyrainin=3.110&yearlyrainin=18.520&lightning_day=0&lightning_time=1663113495&lightning_distance=20&batt_lightning=0&solarradiation=561.48&uv=5&soilhum1=23&battsm1=1&temp1f=63.7&humidity1=58&temp2f=63.9&humidity2=54&temp3f=72.5&humidity3=40&temp4f=59.4&humidity4=64&batt1=1&batt2=1&batt3=1&batt4=1&batt_co2=1 HTTP/1.1
The &temp#f parameters have the data, but it doesn't seem to make it over to MQTT.

@Doonga Thanks for reporting this. I think I fixed it but don't have any way to test. New release is generating, give it about 15-20 minutes then pull the latest Docker image and see if it works.

Looks good, thank for the very fast turnaround!

It worked ok?

Yep, worked perfectly!

Woo!!!!!!!!!!!!!!!!!!!!!!!!!


(serv3) Cargo telepad is unpowered now

Description

Screenshots

Additional context

Not working cause it's unanchored.


elxElastixFilter.hxx

RuntimeError: Exception thrown in SimpleITK Elastix: ....SimpleElastix/Code/Elastix/src/sitkElastixImageFilterImpl.cxx:259:
sitk::ERROR:
itk::ExceptionObject (0x5634e2d2e190)
Location: "unknown"
File: ..../build/Elastix/Core/Main/elxElastixFilter.hxx
Line: 253
Description: itk::ERROR: ElastixFilter(0x5634e3fcf8c0): Internal elastix error: See elastix log (use LogToConsoleOn() or LogToFileOn()).
I face this problem while trying different types of registration but default one ("translation") works fine.
What am supposed to do to tackle this problem?
I compiled elastix as it was proposed in tutorial

Hi, as stated in the error message, the actual error message can be found in the elastix log file. To get the log file add this to your code before executing the registration:
elastix.LogToFileOn()
elastix.SetOutputDirectory(@'C:\...')

I face this problem while trying different types of registration but default one ("translation") works fine.

Here you just gather the default parameters for a translation registration from simple elastix (other possible default parameter maps are 'affine', 'rigid', 'bspline' or 'nonrigid'). In most cases it makes more sense to create your own default parameter files and pass them to elastix by calling
elastix.ReadParameterFile(@'C:\...')
Examples for parameter files can be found here: http://elastix.bigr.nl/wiki/index.php/Parameter_file_database#:~:text=The parameter file database is,here many examples of usage.

@michaelsfr thank you!


proc_manager: replace poll thread by workqueue plus timer

@microbuilder PTAL

@uLipe Can you update the Zephyr header references to start with zephyr/zephyr.h (etc.)? With the latest Zephyr code, builds will fail:
/Users/kevintownsend/Linaro/zephyr/modules/lib/step/tests/src/floatcheck.h:17:10: fatal error: zephyr.h: No such file or directory
   17 | #include <zephyr.h>
      |          ^~~~~~~~~~
compilation terminated.
[16/139] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/crc7_sw.c.obj
[17/139] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/crc32c_sw.c.obj
[18/139] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/crc32_sw.c.obj
[19/139] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/crc8_sw.c.obj
[20/139] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/crc16_sw.c.obj
[21/139] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/cbprintf_packaged.c.obj
ninja: build stopped: subcommand failed.

INFO    - Total complete:    1/   1  100%  skipped:    0, failed:    0
INFO    - 0 of 1 test configurations passed (0.00%), 1 failed, 0 skipped with 0 warnings in 4.66 seconds
INFO    - In total 21 test cases were executed, 0 skipped on 1 out of total 488 platforms (0.20%)
INFO    - 0 test configurations executed on platforms, 1 test configurations were only built.
INFO    - Saving reports...
INFO    - Writing JSON report /Users/kevintownsend/Linaro/zephyr/modules/lib/step/twister-out/twister.json
INFO    - Writing xunit report /Users/kevintownsend/Linaro/zephyr/modules/lib/step/twister-out/twister.xml...
INFO    - Writing xunit report /Users/kevintownsend/Linaro/zephyr/modules/lib/step/twister-out/twister_report.xml...
INFO    - Run completed

Ahhh that is true I suffered same problem inside of other PR I submit.
Will update it.

@microbuilder PTAL again.

@uLipe I was going to make a PR for the Zephyr header cleanup since it's quick to do, but that will make a conflict with the partial changes you've started here, so lets just roll it all up into this PR. Thanks!

Also ... further changes likely required in the future, renaming <zephyr/zephyr.h to <zephyr/kernel.h> but we can sort that out when the changes is merged in and we've moved to a major release using the new name.
See: https://github.com/zephyrproject-rtos/zephyr/pull/49510

@uLipe That PR above was just merged, so maybe we should switch to the latest Zephyr commit, and just update to kernel.h to solve this hopefully once and for all?

Yes agreed, I will take the opportunity to update all zephyr headers, regardless samples or not (zephyr namespace is only required if you build twister, applications out of tree actually does not need it)
And then we can check the header cleanup.

@microbuilder PTAL


feat(tutorial): complete step 5

carbon-tutorial-mbrandt.mybluemix.net

Looks good.  I've marked your step 5 as complete.
Our records how you have all 5 steps complete.


fix #3219

To my knowledge, this appears to fix the outstanding issue. Validation of the two required fields is handled by bootstrap and jinja2. Unselected pulldowns will now display a default tool-tip bubble.

Superseded by https://github.com/qiita-spots/qiita/pull/3278


Revise documentation and indexing for STORE

The problem
Besides appearing two times in this page, the description is LTA.
Suggestions
Revise and improve.

Reopened since description is still LTA.


Track protected queues creation when capturing and replaying trimmed

The problem is that in a couple of places we are calling vkGetDeviceQueue while we should be calling vkGetDeviceQueue2
This is because ANGLE creates the queues with VkDeviceQueueCreateInfo->flags == VK_DEVICE_QUEUE_CREATE_PROTECTED_BIT
In that case the spec says that vkGetDeviceQueue2 should be called instead of vkGetDeviceQueue.
We always call vkGetDeviceQueue which is returning null hence the segfault (Haven't looked into why this doesn't happen in the untrimmed version).
This happens both when recording and when playing the trimmed traces.
This patch is still in progress as it doesn't properly fix the issue when replaying the trimmed trace.
Basically I'm trying to store the flags passed at device creation in the struct DeviceInfo and access later but unfortunately this doesn't seem to work as the DeviceInfo struct allocated when the device is created is different when vkGetDeviceQueue is called so it holds different information.

CI gfxreconstruct build queued with queue ID 23422.

CI gfxreconstruct build # 1670 running.

CI gfxreconstruct build # 1670 failed.

CI gfxreconstruct build queued with queue ID 23899.

CI gfxreconstruct build # 1671 running.

CI gfxreconstruct build queued with queue ID 24009.

CI gfxreconstruct build # 1672 running.

CI gfxreconstruct build # 1672 failed.

CI gfxreconstruct build queued with queue ID 24050.

CI gfxreconstruct build # 1673 failed.

CI gfxreconstruct build queued with queue ID 24425.

CI gfxreconstruct build # 1679 running.

CI gfxreconstruct build # 1679 passed.

CI gfxreconstruct build queued with queue ID 24479.

CI gfxreconstruct build # 1680 passed.

CI gfxreconstruct build queued with queue ID 24527.

CI gfxreconstruct build # 1685 running.

CI gfxreconstruct build queued with queue ID 25030.

CI gfxreconstruct build # 1689 running.

CI gfxreconstruct build # 1689 passed.

CI gfxreconstruct build queued with queue ID 25168.

CI gfxreconstruct build # 1690 running.

CI gfxreconstruct build # 1690 passed.


Add LICENSE file

The package.json indicates that this project is MIT licensed but the license text was not included.

released as v3.1.5 🎉


Ucsc utils

Errors in the docker container are like:
./addCols: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory

I can get this to work in the docker container by requiring libpng ==1.2.50 as a dependency in the recipe, but that libpng version makes matplotlib fail in the same environment.
Is this something we can add to the docker container?

I see you beat me to it - I had no time for this last week but was thinking of something similar in terms of meta templates and an automation script for the process. Have you given the meta-packaging any thought or should we open that discussion in a separate issue? Great work and initiative, thanks.

Closing -- #209 is a much-improved version


Pagination over the results of a query

Hi guys,
I'm having this problem, with queries with a lot of results, it would be nice if you can add a paginator on the different layouts (tables, list tasks), so you define the number of elements you want to see at the time in your note.
I think it should be a frontend ( view ) paginator, I mean, get the entire query result, and if the number exceeded the max items per page, display the paginator component. instead of creating a paginated query...

Front-end pagination is incoming; I had to rewrite the Dataview frontend to use more modern tooling which is why it took so long, but I am targeting it for 0.4.24 this month (after the upcoming tasks update).

Did this ever get implemented? Been looking for documentation as would be nice to have.

See https://github.com/blacksmithgu/obsidian-dataview/issues/1703#issuecomment-1368031232