HDFS-16462. Make HDFS get tool cross platform

Description of PR
The source files for hdfs_get uses getopt for parsing the command line arguments. getopt is available only on Linux and thus, isn't cross platform. We need to replace getopt with boost::program_options to make these tools cross platform.
hdfs_get has the same functionality as hdfs_copyToLocal. Thus, we're reusing the same to implement hdfs_get.
How was this patch tested?
Given that hdfs_get has the same functionality as hdfs_copyToLocal, we've implemented hdfs::tools::Get by deriving from hdfs::tools::CopyToLocal. Since we've already tested hdfs::tools::CopyToLocal for functional correctness, we don't need to do any additional testing to validate the same for hdfs::tools::Get.
However, we do ensure that the correct tool name shows up for hdfs_copyToLocal and hdfs_get.
hdfs_copyToLocal
$ ./hdfs_copyToLocal -h

hdfs_get
$ ./hdfs_get -h

For code changes:

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

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
40m  8s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
33m 22s

trunk passed

+1 :green_heart:
compile
3m 21s

trunk passed

+1 :green_heart:
mvnsite
0m 29s

trunk passed

+1 :green_heart:
shadedclient
56m 35s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 16s

the patch passed

+1 :green_heart:
compile
3m 15s

the patch passed

+1 :green_heart:
cc
3m 15s

the patch passed

+1 :green_heart:
golang
3m 15s

the patch passed

+1 :green_heart:
javac
3m 15s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 17s

the patch passed

+1 :green_heart:
shadedclient
18m 39s

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

_ Other Tests _

-1 :x:
unit
40m 11s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs-native-client.txt
hadoop-hdfs-native-client in the patch failed.

+1 :green_heart:
asflicense
0m 36s

The patch does not generate ASF License warnings.

162m  9s

Reason
Tests

Failed CTEST tests
test_test_libhdfs_ops_hdfs_static

test_test_libhdfs_threaded_hdfs_static

test_test_libhdfs_zerocopy_hdfs_static

test_libhdfs_threaded_hdfspp_test_shim_static

test_hdfspp_mini_dfs_smoke_hdfspp_test_shim_static

libhdfs_mini_stress_valgrind_hdfspp_test_static

memcheck_libhdfs_mini_stress_valgrind_hdfspp_test_static

test_libhdfs_mini_stress_hdfspp_test_shim_static

test_hdfs_ext_hdfspp_test_shim_static

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense compile cc mvnsite javac unit codespell golang

uname
Linux 659f64cff5c3 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / f53d0bf26dd50e690928a6fd167ffa3e01517b7b

Default Java
Red Hat, Inc.-1.8.0_322-b06

CTEST
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4003/1/artifact/out/patch-hadoop-hdfs-project_hadoop-hdfs-native-client-ctest.txt

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

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

modules
C: hadoop-hdfs-project/hadoop-hdfs-native-client U: hadoop-hdfs-project/hadoop-hdfs-native-client

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

versions
git=2.9.5 maven=3.6.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 57s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
35m 52s

trunk passed

+1 :green_heart:
compile
3m 28s

trunk passed

+1 :green_heart:
mvnsite
0m 23s

trunk passed

+1 :green_heart:
shadedclient
62m 46s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 14s

the patch passed

+1 :green_heart:
compile
3m 24s

the patch passed

+1 :green_heart:
cc
3m 24s

the patch passed

+1 :green_heart:
golang
3m 24s

the patch passed

+1 :green_heart:
javac
3m 24s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 15s

the patch passed

+1 :green_heart:
shadedclient
22m 11s

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

_ Other Tests _

-1 :x:
unit
37m  7s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs-native-client.txt
hadoop-hdfs-native-client in the patch failed.

+1 :green_heart:
asflicense
0m 31s

The patch does not generate ASF License warnings.

129m 36s

Reason
Tests

Failed CTEST tests
test_test_libhdfs_ops_hdfs_static

test_test_libhdfs_threaded_hdfs_static

test_test_libhdfs_zerocopy_hdfs_static

test_libhdfs_threaded_hdfspp_test_shim_static

libhdfs_mini_stress_valgrind_hdfspp_test_static

memcheck_libhdfs_mini_stress_valgrind_hdfspp_test_static

test_libhdfs_mini_stress_hdfspp_test_shim_static

test_hdfs_ext_hdfspp_test_shim_static

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense compile cc mvnsite javac unit codespell golang

uname
Linux b63fedc65a17 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / c29a2316e9e54e9471b6ddafa3b9af6a913705bf

Default Java
Red Hat, Inc.-1.8.0_322-b06

CTEST
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4003/6/artifact/out/patch-hadoop-hdfs-project_hadoop-hdfs-native-client-ctest.txt

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

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

modules
C: hadoop-hdfs-project/hadoop-hdfs-native-client U: hadoop-hdfs-project/hadoop-hdfs-native-client

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

versions
git=2.9.5 maven=3.6.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
38m 40s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
36m 29s

trunk passed

+1 :green_heart:
compile
4m 30s

trunk passed

+1 :green_heart:
mvnsite
0m 32s

trunk passed

+1 :green_heart:
shadedclient
68m 30s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 24s

the patch passed

+1 :green_heart:
compile
4m 22s

the patch passed

+1 :green_heart:
cc
4m 22s

the patch passed

+1 :green_heart:
golang
4m 22s

the patch passed

+1 :green_heart:
javac
4m 22s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 18s

the patch passed

+1 :green_heart:
shadedclient
24m 44s

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

_ Other Tests _

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

+1 :green_heart:
asflicense
0m 41s

The patch does not generate ASF License warnings.

141m 46s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense compile cc mvnsite javac unit codespell golang

uname
Linux 457a702d7080 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / c29a2316e9e54e9471b6ddafa3b9af6a913705bf

Default Java
Red Hat, Inc.-1.8.0_322-b06

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

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

modules
C: hadoop-hdfs-project/hadoop-hdfs-native-client U: hadoop-hdfs-project/hadoop-hdfs-native-client

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

versions
git=2.9.5 maven=3.6.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
79m  5s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
43m 59s

trunk passed

+1 :green_heart:
compile
4m 33s

trunk passed

+1 :green_heart:
mvnsite
0m 32s

trunk passed

-1 :x:
shadedclient
76m  4s

branch has errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 17s

the patch passed

+1 :green_heart:
compile
4m 34s

the patch passed

+1 :green_heart:
cc
4m 34s

the patch passed

+1 :green_heart:
golang
4m 34s

the patch passed

+1 :green_heart:
javac
4m 34s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 21s

the patch passed

-1 :x:
shadedclient
22m  3s

patch has errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
20m  7s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs-native-client.txt
hadoop-hdfs-native-client in the patch failed.

+1 :green_heart:
asflicense
0m 35s

The patch does not generate ASF License warnings.

205m 35s

Reason
Tests

Failed CTEST tests
test_test_libhdfs_ops_hdfs_static

test_test_libhdfs_threaded_hdfs_static

test_test_libhdfs_zerocopy_hdfs_static

test_test_native_mini_dfs

test_libhdfs_threaded_hdfspp_test_shim_static

test_hdfspp_mini_dfs_smoke_hdfspp_test_shim_static

libhdfs_mini_stress_valgrind_hdfspp_test_static

memcheck_libhdfs_mini_stress_valgrind_hdfspp_test_static

test_libhdfs_mini_stress_hdfspp_test_shim_static

test_hdfs_ext_hdfspp_test_shim_static

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense compile cc mvnsite javac unit codespell golang

uname
Linux 28ef380f6fa1 4.15.0-163-generic #171-Ubuntu SMP Fri Nov 5 11:55:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / c29a2316e9e54e9471b6ddafa3b9af6a913705bf

Default Java
Red Hat, Inc.-1.8.0_322-b06

CTEST
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4003/7/artifact/out/patch-hadoop-hdfs-project_hadoop-hdfs-native-client-ctest.txt

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

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

modules
C: hadoop-hdfs-project/hadoop-hdfs-native-client U: hadoop-hdfs-project/hadoop-hdfs-native-client

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

versions
git=2.9.5 maven=3.6.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
39m 16s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

-1 :x:
mvninstall
4m 59s
/branch-mvninstall-root.txt
root in trunk failed.

+1 :green_heart:
compile
3m 36s

trunk passed

+1 :green_heart:
mvnsite
0m 21s

trunk passed

+1 :green_heart:
shadedclient
30m  1s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 16s

the patch passed

+1 :green_heart:
compile
3m 13s

the patch passed

+1 :green_heart:
cc
3m 13s

the patch passed

+1 :green_heart:
golang
3m 13s

the patch passed

+1 :green_heart:
javac
3m 13s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 18s

the patch passed

+1 :green_heart:
shadedclient
18m 35s

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

_ Other Tests _

+1 :green_heart:
unit
85m 56s

hadoop-hdfs-native-client in the patch passed.

+1 :green_heart:
asflicense
0m 38s

The patch does not generate ASF License warnings.

180m 36s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense compile cc mvnsite javac unit codespell golang

uname
Linux 9f07cb6071e9 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / a5437123151c595b6f4095b04ea9b115881ceb2f

Default Java
Red Hat, Inc.-1.8.0_322-b06

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

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

modules
C: hadoop-hdfs-project/hadoop-hdfs-native-client U: hadoop-hdfs-project/hadoop-hdfs-native-client

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

versions
git=2.9.5 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
51m 38s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
39m  6s

trunk passed

+1 :green_heart:
compile
4m 19s

trunk passed

+1 :green_heart:
mvnsite
0m 31s

trunk passed

+1 :green_heart:
shadedclient
68m 48s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 16s

the patch passed

+1 :green_heart:
compile
3m 49s

the patch passed

+1 :green_heart:
cc
3m 49s

the patch passed

+1 :green_heart:
golang
3m 49s

the patch passed

+1 :green_heart:
javac
3m 49s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 18s

the patch passed

+1 :green_heart:
shadedclient
25m 20s

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

_ Other Tests _

+1 :green_heart:
unit
117m  7s

hadoop-hdfs-native-client in the patch passed.

+1 :green_heart:
asflicense
0m 31s

The patch does not generate ASF License warnings.

270m 21s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense compile cc mvnsite javac unit codespell golang

uname
Linux 480d780e8b9d 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / a5437123151c595b6f4095b04ea9b115881ceb2f

Default Java
Red Hat, Inc.-1.8.0_322-b06

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

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

modules
C: hadoop-hdfs-project/hadoop-hdfs-native-client U: hadoop-hdfs-project/hadoop-hdfs-native-client

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

versions
git=2.9.5 maven=3.6.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m  0s

Docker mode activated.

-1 :x:
docker
0m 30s

Docker failed to build yetus/hadoop:c42441a1ec4.

Subsystem
Report/Notes

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

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

versions
git=2.17.1

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
43m 39s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
35m 38s

trunk passed

+1 :green_heart:
compile
3m 30s

trunk passed

+1 :green_heart:
mvnsite
0m 23s

trunk passed

+1 :green_heart:
shadedclient
61m 29s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 14s

the patch passed

+1 :green_heart:
compile
3m 21s

the patch passed

+1 :green_heart:
cc
3m 21s

the patch passed

+1 :green_heart:
golang
3m 21s

the patch passed

+1 :green_heart:
javac
3m 21s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 15s

the patch passed

+1 :green_heart:
shadedclient
22m  7s

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

_ Other Tests _

+1 :green_heart:
unit
99m 14s

hadoop-hdfs-native-client in the patch passed.

+1 :green_heart:
asflicense
0m 31s

The patch does not generate ASF License warnings.

233m 15s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense compile cc mvnsite javac unit codespell golang

uname
Linux 87488cbcc0d8 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 40e9eaae34deebc94be7a3a39378cfe5deeac96f

Default Java
Red Hat, Inc.-1.8.0_322-b06

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

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

modules
C: hadoop-hdfs-project/hadoop-hdfs-native-client U: hadoop-hdfs-project/hadoop-hdfs-native-client

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

versions
git=2.9.5 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
27m 19s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
25m 14s

trunk passed

+1 :green_heart:
compile
3m 41s

trunk passed

+1 :green_heart:
mvnsite
0m 34s

trunk passed

+1 :green_heart:
shadedclient
52m  1s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 20s

the patch passed

+1 :green_heart:
compile
3m 23s

the patch passed

+1 :green_heart:
cc
3m 23s

the patch passed

+1 :green_heart:
golang
3m 23s

the patch passed

+1 :green_heart:
javac
3m 23s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 22s

the patch passed

+1 :green_heart:
shadedclient
24m 13s

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

_ Other Tests _

+1 :green_heart:
unit
114m  4s

hadoop-hdfs-native-client in the patch passed.

+1 :green_heart:
asflicense
0m 39s

The patch does not generate ASF License warnings.

224m 34s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense compile cc mvnsite javac unit codespell golang

uname
Linux 1140c06f4704 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 40e9eaae34deebc94be7a3a39378cfe5deeac96f

Default Java
Red Hat, Inc.-1.8.0_312-b07

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

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

modules
C: hadoop-hdfs-project/hadoop-hdfs-native-client U: hadoop-hdfs-project/hadoop-hdfs-native-client

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

versions
git=2.27.0 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
16m 18s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
32m 43s

trunk passed

+1 :green_heart:
compile
3m 17s

trunk passed

+1 :green_heart:
mvnsite
0m 21s

trunk passed

+1 :green_heart:
shadedclient
67m  4s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 15s

the patch passed

+1 :green_heart:
compile
3m  9s

the patch passed

+1 :green_heart:
cc
3m  9s

the patch passed

+1 :green_heart:
golang
3m  9s

the patch passed

+1 :green_heart:
javac
3m  9s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 15s

the patch passed

+1 :green_heart:
shadedclient
30m 43s

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

_ Other Tests _

+1 :green_heart:
unit
108m 11s

hadoop-hdfs-native-client in the patch passed.

+1 :green_heart:
asflicense
0m 30s

The patch does not generate ASF License warnings.

228m 52s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense compile cc mvnsite javac unit codespell golang

uname
Linux 7782e331541c 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 40e9eaae34deebc94be7a3a39378cfe5deeac96f

Default Java
Debian-11.0.14+9-post-Debian-1deb10u1

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

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

modules
C: hadoop-hdfs-project/hadoop-hdfs-native-client U: hadoop-hdfs-project/hadoop-hdfs-native-client

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

versions
git=2.20.1 maven=3.6.0

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
17m 48s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
24m 21s

trunk passed

+1 :green_heart:
compile
3m 45s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
3m 49s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
mvnsite
0m 24s

trunk passed

+1 :green_heart:
shadedclient
55m 13s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 14s

the patch passed

+1 :green_heart:
compile
3m 45s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
cc
3m 45s

the patch passed

+1 :green_heart:
golang
3m 45s

the patch passed

+1 :green_heart:
javac
3m 45s

the patch passed

+1 :green_heart:
compile
3m 43s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
cc
3m 43s

the patch passed

+1 :green_heart:
golang
3m 43s

the patch passed

+1 :green_heart:
javac
3m 43s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 16s

the patch passed

+1 :green_heart:
shadedclient
22m 36s

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

_ Other Tests _

+1 :green_heart:
unit
108m 40s

hadoop-hdfs-native-client in the patch passed.

+1 :green_heart:
asflicense
0m 30s

The patch does not generate ASF License warnings.

214m 57s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense compile cc mvnsite javac unit codespell golang

uname
Linux e6b6969132ae 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 40e9eaae34deebc94be7a3a39378cfe5deeac96f

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

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

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

modules
C: hadoop-hdfs-project/hadoop-hdfs-native-client U: hadoop-hdfs-project/hadoop-hdfs-native-client

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

versions
git=2.25.1 maven=3.6.3

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

This message was automatically generated.


Bug / Typo in W0D5_Tutorial2_Solution_4e7f8943.py

Line 60: visual = my_gaussian(x, mu_visual, mu_visual) should be visual = my_gaussian(x, mu_visual, sigma_visual)
At the moment the solution plot is wrong because of this.

Good catch! Corrected on the new repo of pre-course material. Thanks!


pick up a random port for metrics when MountPod using hostNetwork

As the MountPod can inherit some attributes from juicefs-csi-node daemonset:
	// inherit attr from csi
	jfsSetting.Attr = PodAttr{
		Namespace:            Namespace,
		MountPointPath:       MountPointPath,
		JFSConfigPath:        JFSConfigPath,
		JFSMountPriorityName: JFSMountPriorityName,
		Image:                MountImage,
		HostNetwork:          CSIPod.Spec.HostNetwork,
		HostAliases:          CSIPod.Spec.HostAliases,
		HostPID:              CSIPod.Spec.HostPID,
		HostIPC:              CSIPod.Spec.HostIPC,
		DNSConfig:            CSIPod.Spec.DNSConfig,
		DNSPolicy:            CSIPod.Spec.DNSPolicy,
		ImagePullSecrets:     CSIPod.Spec.ImagePullSecrets,
		PreemptionPolicy:     CSIPod.Spec.PreemptionPolicy,
		Tolerations:          CSIPod.Spec.Tolerations,
	}

So if we make juicefs-csi-node to be hostNetwork: true, those MountPods will also be hostNetwork: true. What makes the problem is those metrics exported by juicefs mount if these MountPods listen at the same port.
kube-system   juicefs-e-node-s19inspur-36c7-pvc-36e2d025-c704-45e1-8784-43b63daa9092-sugiun   1/1     Running             0          9m13s   x.x.x.x   e-node-s19inspur-36c7    <none>           <none>
kube-system   juicefs-e-node-s19inspur-36c7-pvc-e2ee0faf-6642-4128-9917-f656b4d9aec1-tccate   0/1     NodePorts           0          12s     <none>           e-node-s19inspur-36c7    <none>           <none>

Status:               Failed
Reason:               NodePorts
Message:              Pod Predicate NodePorts failed

This PR makes these MountPods listen at a random port when they are in hostNetwork mode, and we also do not proclaim any container port.

Codecov Report
Base: 41.52% // Head: 41.44% // Decreases project coverage by -0.08% :warning:

Coverage data is based on head (2cc6adb) compared to base (173a77d).
Patch coverage: 33.33% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #586      +/-   ##
==========================================
- Coverage   41.52%   41.44%   -0.08%
==========================================
  Files          32       32
  Lines        3374     3380       +6
==========================================
  Hits         1401     1401
- Misses       1851     1853       +2
- Partials      122      126       +4

Impacted Files
Coverage Δ

pkg/juicefs/mount/builder/pod.go
55.88% <33.33%> (-2.58%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


G3.10 Support drawing arrows between points based on time series information in host application

Description from user story ": I want to view the location of all cases in an area, with a visual representation (e.g., arrows, lines) of the relationship between each index case and introduced cases related to each index case."
We need to support the ability to draw arrows on the map from one point to the next showing how a case has moved from point 1 to 2 to 3 to 4, etc. The arrows should be drawn directly as lines, not following any types of path or road.
Use Case:

A user moves from house to house testing each member for malaria.
If the malaria test is positive, they provide treatment immediately and each test is recorded in the host application.
Forms are submitted at every house as the user moves through the village and each form contains time series information (formSubmission datetime).
The user wants to view the location of all cases in the area displayed on the GeoWidget so they can see how they moved throughout the village and all of the positive cases.

Development Required:
The sample app will need to have a push button that toggles drawing arrows between 5 points based on some "dateTime" property that's passed in from the host application. The arrows should identify which points have the earliest dateTime, order them earliest to latest and then draw an arrow from structure to structure. At this moment, the sample app does not need bounding box support, just work on sample data.

[ ] Define an appropriate dateTime property and testStatus property (positive, negative, not-tested) that we want to track on each structure "passed in by the host application"
[ ] Create 10 points of demo data with the dateTime property. Six are blue representing cases found  (testStatus = positive) and four are purple representing visited but no cases found (testStatus = negative).
[ ] Add the business logic that does the calculations (1. Find all points that have the dateTime property on the screen; 2. Within those, find all the points that have the testStatus = positive; 3. Order the points;
[ ] Add a button to the GeoWidget that draws the arrows. No animation is needed, we just need arrows to show up on the map

The arrows can probably be like above. Taken from the Mapbox navigation site
DRAFT OF THE FEATURE SUPPORTING DRAWING ARROWS

Arrow-line color + stroke + shadow(if any) should be configurable
The arrows should be drawn passing below the structures
At least or probably just one arrow between two edges
One of the parameters can be the list of GeoJSON for which to draw the vertices(arrows in this case) . The host application can use the query API to fetch features from the style
The Expressions query provided by Mapbox is enough for making the feature selection(query)  and case relationship dynamic enough
Another option of the parameters could also be to pass expressions and/or layer-ids so as to make the case relationship dynamic enough
Arrows should be draw below the structures
Only one arrow between two edges(cases)
The sort field & sort order should be configurable

String and numbers should work OK natively
We should add support for DATE in case of string formatted dates which should work the the provided string to date conversion native functions
Provision of sorting interface so that this is also easily changeable to the host preference

Assumptions

The arrow color might change depending on theme or case relationship being displayed
The arrow direction might be different depending for different use-cases
The cases might be on different layers
The cases(features) might need to match different conditions - This will be easy IF the Mapbox Expressions can work to fit the query requirements since it's already used in querying features on the Mapbox map

@githengi @craigappl

@Kigamba this looks great. I have a couple more notes:

We will need to support 'n' points as we draw this. The index case is the first, then, based on the time series, we will have to draw the lines point to point until the investigation is complete. So, this feature will need to demonstrate drawing lines from the first structure to 5 structures
This will need to support drawing lines from any point, polygon or multi-polygon.
We definitely need to sort by datetime.

@craigappl

We will need to support 'n' points as we draw this. The index case is the first, then, based on the time series, we will have to draw the lines point to point until the investigation is complete. So, this feature will need to demonstrate drawing lines from the first structure to 5 structures

Definitely, forgot to explicitly state that.

This will need to support drawing lines from any point, polygon or multi-polygon.

I will add this also to the current draft

We definitely need to sort by datetime.

Cool, this will be high priority

It seems like the feature querying provided by Mapbox will not work for our feature selection
The current MapboxMap.queryRenderedFeatures method only works for rendered features.
The current VectorSource/GeoJsonSource.querySourceFeatures methods  have the following limits:

According to Mapbox documentation here, it cannot retrieve features outside the current viewport "The domain of the query includes all currently-loaded vector tiles and GeoJSON source tiles: this function does not check tiles outside the currently visible viewport"
Do not work either across sources or across layers uniformly. For each to work, we would need to define different params around each and specific conditions for each which do not seem to achieve our goals easily or out of our scope provided. From the scope, the host application will be assumed to always have a list of features from which the selection will be made

We currently only need a dynamic enough feature selection feature so that the feature selection can work dynamically for the few use-cases
TERMS
Feature selection - This is definition of conditions for which features should meet to be selected for case relationship

I think the host application should be able to pass the property that has date time to the GeoWidget.
The host app should also pass the property that has status, also the status states when arrows should be drawn.
The host app should also send the GeoJSON of the points.
The Geowidget with the above data should be able to

Filter points that have a status that should be drawn
Filter points from 1 above that have date time property
Sort the points from 2 above
Draw the arrows from the earliest one to the last one

Cool, so for filtering of points. Do we only make equalTo filtering for a single string property on the GeoWidget?

@craigappl please reply to this.
equalTo should be mandatory and probably filtering via regex should also be supported.

@githengi and @Kigamba , are these really two separate features that should be split out?
Feature 1) Allow for filtering of points on the GeoWidget (https://github.com/onaio/kujaku/issues/259)
Feature 2) Draw lines between the filtered points
They may not need to be separate features in the UI, but I would recommend considering different methods that can be used by the host application.

@craigappl  @Kigamba
The features should be split. Filtering should be different from drawing lines between points.
The filtering can be by any of the feature(business data) properties. A builder pattern can be used to chain multiple filters using different properties e.g type = residential and tesstatus =  positive
Drawing the arrows will use the filtering feature to filter and draw the arrows for only the valid structures.


gRPC HTTP/3 support in Tonic

Feature Request
Tracking issue for supporting client and server http3 transport for gRPC services. Functionality should mostly be inherited by dependency crates, but would likely need exposure through tonic layer.
Crates
In Tonic:
https://github.com/hyperium/tonic/blob/master/tonic/src/transport/mod.rs
Inheriting from Hyper:
https://github.com/hyperium/hyper/issues/1818
Inheriting from Quinn:
https://github.com/djc/quinn/issues?q=is%3Aissue+is%3Aopen+label%3Ah3
Motivation
To have a rust and tokio framework that is futures based and supports H3 for machine to machine APIs, as well as upcoming browser to server H3 requests.
Alternatives
There are other libraries that implement H3 like quiche, but they all still require significant work to get gRPC based services working.

Thanks for opening this! You are on the right track here, once hyper gets h3 we can easily expose it for tonic.

Initial progress is here https://github.com/hyperium/h3/pull/1

I think I'll close this for now. Until hyper supports h3 there isn't much we can do.

Here's the issue for adding h3 support into hyper: https://github.com/hyperium/hyper/issues/1818
As of writing, it's currently waiting on this exploratory effort to add h3 support to reqwest, which will inform how h3 is supported in hyper: https://github.com/seanmonstar/reqwest/issues/1558

any news?

@usmonie See the linked issues. If nothings been posted there then there is probably nothing new. No need to post on old issues.

waiting on this exploratory effort to add h3 support to reqwest,
See the linked issues. If nothings been posted there then there is probably nothing new.

@davidpdrsn But looks like ...
This was done in https://github.com/seanmonstar/reqwest/pull/1599, and released in v0.11.15
Current 0.11.18

That's reqwest. What about hyper?

As far as I understand, it was hyper waiting on reqwest (for client-side support), and even as of 0.12.5, reqwest's http/3 support still requires an experimental flag; my understanding from https://github.com/hyperium/hyper/issues/1818 is that Hyper is waiting for that to stabilise before taking it on. The request-side issue for this is https://github.com/seanmonstar/reqwest/issues/2303.
So long-story-short, it still appears to be blocked in a grand-dependency in a PRs-welcome state.


[DOCFIX]Update wording in docs/cn/Running-Alluxio-Fault-Tolerant.md

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17722/
Test PASSed.


Ellipsis consistency: choose between word... or word ...

Steps to reproduce

crc setup
crc start

Expected
INFO Adding user's pull secret to instance disk...
INFO Verifying validity of the kubelet certificates...

Actual
INFO Adding user's pull secret to instance disk...
INFO Verifying validity of the kubelet certificates ...

Description
Three dots are often used in crc: sometimes with a space before, sometimes directly next to the word. We should make a choice! :)
ping @robin-owen

From a "grammatically correct" standpoint, we should not have a space before the ellipses.

From a "grammatically correct" standpoint, we should not have a space before the ellipses.

wikipedia lists various point of views on this https://en.wikipedia.org/wiki/Ellipsis#In_English :) But no spaces look nicer to me!


chore(client): enable foreign_keys pragma on startup

Closes VAX-880.
No need to also enable the compensations because they are already enabled by the base migration:

defined here with compensations set to 1: https://github.com/electric-sql/electric/blob/main/clients/typescript/src/migrators/schema.ts#L20
and applied here: https://github.com/electric-sql/electric/blob/main/clients/typescript/src/migrators/bundle.ts#L38

N.b.: let's also remove the dupe calls from the examples. N.n.b: this may require another PR, i.e.: merge this, release library, then merge PR relying on it.

N.b.: let's also remove the dupe calls from the examples. N.n.b: this may require another PR, i.e.: merge this, release library, then merge PR relying on it.

Yep. This makes me think, do we really want the examples to run against the latest published version?
Having the examples run against the ts client in the mono repo would simplify the worklow and simplify evolution of the examples together with the codebase. Because now, examples cannot be evolved until next release which is also cumbersome for our own testing purposes.

Yup, we had the same discussion whilst you were away. Another option was versioning the published docs and examples. No solution is ideal. We need to pick one and work with it.

Yup, we had the same discussion whilst you were away. Another option was versioning the published docs and examples. No solution is ideal. We need to pick one and work with it.

Yes. If we want examples against latest published version, i would advocate for using a separate repo as it does not make much sense to put it in the mono repo. But i'm sure you've discussed this. We can catch up on this.

If we start managing the next release PR through Linear or with a open PR here we can track pending changes. I suspect @icehaunter might have some input on this too.

@balegas i moved it to the base electrify call as that is the earliest point where we can get to the user-defined database connection. Let me know if that is fine.

Just to chip in: I think that's a great place for it. That's where we take a standard conn and electrify it, which thus includes making sure it's got the right settings etc.
That said, perhaps you could extract to a prepare(conn) function that's called at the start of electrify and make that function overridable, in case drivers need custom setup?


integrations: ultralytics/yolo

Need to document the yolo callback from https://github.com/ultralytics/ultralytics/blob/main/ultralytics/yolo/utils/callbacks/dvc.py into dvclive and utralytics docs.

Ultralytics generates their docs for all the callbacks I think? Or do you want to add a more comprehensive overview, etc? I was thinking about this, but I don't feel we are ready for that. I don't know how to use the callback in the real project yet. (specifically, what do with images folder, how to combine it with the existing dvc.yaml, etc)- I felt we need some time to address those (or agree that those are not important / we have a good workaround).

Ultralytics generates their docs for all the callbacks I think?

This is the only thing rendered, which is not very helpful I guess https://docs.ultralytics.com/reference/yolo/utils/callbacks/dvc/

Or do you want to add a more comprehensive overview, etc?

I think we could start by adding a page to our docs https://dvc.org/doc/dvclive/ml-frameworks with minimum explanation on how to use it.

I was thinking about this, but I don't feel we are ready for that. I don't know how to use the callback in the real project yet. (specifically, what do with images folder, how to combine it with the existing dvc.yaml, etc)- I felt we need some time to address those (or agree that those are not important / we have a good workaround).

I was planning to try to use it in a project myself.
Also, I see that images can be valuable but can we start by not using them? Other loggers don't do anything with them and I think it is ok to start with metrics and linear plots while we figure this other things

For comparison: https://docs.wandb.ai/guides/integrations/yolov5

Also, I see that images can be valuable but can we start by not using them? Other loggers don't do anything with them and I think it is ok to start with metrics and linear plots while we figure this other things

All loggers actually do log them, and support per step navigation.

I think we could start by adding a page to our docs https://dvc.org/doc/dvclive/ml-frameworks with minimum explanation on how to use it.

Yes, I can start on that.

I think it's not done, right? We still don't have docs / guide on the YOLO side, let's keep it open for now?

Relevant https://github.com/ultralytics/ultralytics/pull/4343#issuecomment-1676447390

Lowering to p2, as we have a decent enough integration for now, not sure what is left beyond docs/guide on YOLO side


put details-control button in  Master and Details Table in the last column of table

As you see in this documai datatables.yajrabox.com  the  details-control button is located in the first column, i want to place it in last column
is there anyway?
System details

Operating System:
PHP Version: 7.1.3
Laravel Version:5.8.*
Laravel-Datatables Version 8.0

I think you just need to arrange the columns and make it as last?
columns: [
            {data: 'id', name: 'id'},
            {data: 'name', name: 'name'},
            {data: 'email', name: 'email'},
            {data: 'created_at', name: 'created_at'},
            {data: 'updated_at', name: 'updated_at'},
            {
                "className":      'details-control',
                "orderable":      false,
                "searchable":      false,
                "data":           null,
                "defaultContent": ''
            },
        ],

Thanks in advance


JsonBuilder required

Currently, Codec generation is all based on macro expansion.
trait Codecs extends CodecDef {
  val codec: Codec[???] = {
    "id".parsed[String] ++
    "name".parsed[String]
  }.apply(User.apply)(User.unapply)
}

JSON key cannot be a variable due to macro property.
def codec(key: String): Codec[???] = {
  key.parsed[String] // This will fail
}.apply(User.apply)(User.unapply)

Failure to do this may increase Codec definition costs. play-json can do this.
def codec(key: String): OWrites[???] = OWrites { x =>
  Json.obj(
    key -> x.id
  )
}

Without equivalent function, it is not suitable for API response formatter.

Fix https://github.com/giiita/refuel/pull/61


Fixed a bug in constructUrlFromInputs which was resulted in malformed URLs.

Description
Fixed a bug in constructUrlFromInputs which was resulted in malformed URLs.
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #359 (0fe3b2a) into main (3869c74) will decrease coverage by 0.04%.
The diff coverage is 33.33%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##               main     #359      +/-   ##
============================================
- Coverage     73.30%   73.27%   -0.04%
- Complexity      698      699       +1
============================================
  Files           110      110
  Lines          4612     4614       +2
  Branches        606      608       +2
============================================
  Hits           3381     3381
  Misses          980      980
- Partials        251      253       +2

Impacted Files
Coverage Δ

...arch/commons/alerting/model/ClusterMetricsInput.kt
79.01% <33.33%> (-0.99%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Remove unstable package & cross compile executor

@jorive this fixes the test error and also replaces the alpha dependency with a stable netstandard2.0 package. This removes a compiler warnings because of two different assembly identities. I also opened a PR but I doubt it will be accepted as the project seems dead: https://github.com/Wheelies/MarkdownLog/pull/16
You can now publish the packages. Thanks!

@dotnet-bot test this please


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 646 ms

Resolved: ClamAV performance has improved in d9ae0a2.


Nested Scrollbable Tab Views?

I need one of the children to have it's own scrollable tab view. Like a sub menu of tabs.
It doesn't seem like this is supported? The sub children tabbar renders but none of the child elements render.
Any pointers to what I might need to change in your code to get this to work?
Thanks

I guess sliding left/right in this child component that has it's own scrollable tab view would ideally only scroll that component. Hmm. get's a little finicky I guess. Thoughts?

https://github.com/brentvatne/react-native-scrollable-tab-view/blob/master/examples/FacebookTabsExample/FacebookTabsExample.js#L18
It might be helpful. Could you make a photo of your interface? I'm not sure that I understood you correct?

Hi, I actually have 2 rows of tabs. These are some online examples that I think show the idea:
http://cdn.makeuseof.com/wp-content/uploads/2011/05/image-146.jpg?77608b
https://help.comodo.com/uploads/Comodo KoruMail/4b9a3ae6e2cbd6008bec704ed0edea34/5eac818f1e1c4adc19d335055b06586b/7ea73eb6802c802d11af9131b08f5d7c/km_sysconfig50.png
It is like this in JSX

any updates on this?

this issue is still there

any updates ?

any updates ?

@reactor81
I have the same issue.  "The sub children tabbar renders but none of the child elements render."
had you resolved this problem? would you like to help me?
please give me some advise.
thank you very much.

i have the same problem,
please give me some advise.
thank you very much.

Any fixes or workarounds?

I have the same problem, but only the first two children tabviews do not render.

Closing as this issue is very old, feel free to open a new issue if its still happening in the latest release


Input checks for interpolation parameter

After #7176, we no longer warn and coerce integer inputs for interpolation into our enum. This means, passing an int will just fail down the line:
import torch
from torchvision import transforms

transform = transforms.Resize(size=(32, 64), interpolation=0)

transform(torch.rand(3, 256, 128))

Traceback (most recent call last):
  File "/home/philip/git/pytorch/vision/main.py", line 6, in <module>
    transform(torch.rand(3, 256, 128))
  File "/home/philip/.conda/envs/pytorch-vision-dev/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1488, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/philip/git/pytorch/vision/torchvision/transforms/transforms.py", line 336, in forward
    return F.resize(img, self.size, self.interpolation, self.max_size, self.antialias)
  File "/home/philip/git/pytorch/vision/torchvision/transforms/functional.py", line 430, in resize
    raise TypeError("Argument interpolation should be a InterpolationMode")
TypeError: Argument interpolation should be a InterpolationMode

(Note that it is failing in the functional rather in the transforms part)
However, the above is only true for transforms v1. We don't have any such checks for transforms v2:
import torch
from torchvision.prototype import transforms

transform = transforms.Resize(size=(32, 64), interpolation=0)

transform(torch.rand(3, 256, 128))

Traceback (most recent call last):
  File "/home/philip/git/pytorch/vision/main.py", line 6, in <module>
    transform(torch.rand(3, 256, 128))
  File "/home/philip/.conda/envs/pytorch-vision-dev/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1488, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/philip/git/pytorch/vision/torchvision/prototype/transforms/_transform.py", line 40, in forward
    flat_outputs = [
  File "/home/philip/git/pytorch/vision/torchvision/prototype/transforms/_transform.py", line 41, in <listcomp>
    self._transform(inpt, params) if check_type(inpt, self._transformed_types) else inpt for inpt in flat_inputs
  File "/home/philip/git/pytorch/vision/torchvision/prototype/transforms/_geometry.py", line 69, in _transform
    return F.resize(
  File "/home/philip/git/pytorch/vision/torchvision/prototype/transforms/functional/_geometry.py", line 243, in resize
    return resize_image_tensor(inpt, size, interpolation=interpolation, max_size=max_size, antialias=antialias)
  File "/home/philip/git/pytorch/vision/torchvision/prototype/transforms/functional/_geometry.py", line 170, in resize_image_tensor
    mode=interpolation.value,
AttributeError: 'int' object has no attribute 'value'

We won't get silent bugs here, but it is still worth it to have an expressive error message. Especially since int was allowed before.

Might be irrelevant in the light of #7205.


Fixing @strapi/icons peer dependency in design system

Strapi design system requires an alpha version of strapi. This change just fixes that
Describe the technical changes you did.
Updated version for @strapi/icons to 1.1.1 in @strapi/design-system
Why is it needed?
To keep dependencies accurate and explicit
Related issue(s)/PR(s)
Let us know if this is related to any issue/pull request

What exactly failed on this test? I only changed one line

@kibblerz I'm re-running the tests, sice this failure occurred a couple times today. Might be something related to GitHub.


Turn on editor.experimental.asyncTokenization by default

The experiment still needs to be deleted after the setting default value got deployed.

Reopening, as the experiment still needs to be deleted.


Overlapping navbar + Invisible Text + inappropriate background size

Description

Expected Behavior
I would like to fix these bugs.
Please assign it to me under gssoc'23
Show us the trouble with screenshots

Which browsers are affected?
No response
Which OS are affected?
No response
Enter the version of your web browser
all browsers afftected.
Device?
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

@Vaishnavi-Patil2211 Please assign this to me

Thank you so much. I will do my best to.
Sent from Outlook for Androidhttps://aka.ms/AAb9ysg

From: github-actions[bot] @.>
Sent: Thursday, July 20, 2023 3:44:37 PM
To: OSCode-Community/OSCodeCommunitySite @.>
Cc: Khadija Rizvi @.>; Assign @.>
Subject: Re: [OSCode-Community/OSCodeCommunitySite] Overlapping navbar + Invisible Text + inappropriate background size (Issue #956)
Hello @akanksha984https://github.com/akanksha984, thank you for raising an issue. 🙌 I have assigned the issue to you. You can now start working on it. If you encounter any problems, please feel free to connect with us. 👍
—
Reply to this email directly, view it on GitHubhttps://github.com/OSCode-Community/OSCodeCommunitySite/issues/956#issuecomment-1643653114, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A7UBO7A23XGMZY4FANUQQKLXREAI3ANCNFSM6AAAAAAZYTLAGQ.
You are receiving this because you were assigned.Message ID: @.***>
Disclaimer - The information contained in this electronic communication is intended solely for the individual(s) or entity to which it is addressed. It may contain proprietary, confidential and/or legally privileged information. Any review, retransmission, dissemination, printing, copying or other use of, or taking any action in reliance on the contents of this information by person(s) or entities other than the intended recipient is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us by responding to this email or telephone and immediately and permanently delete all copies of this message and any attachments from your system(s). The contents of this message do not necessarily represent the views or policies of ABES.


FilePicker keep showing when called from a Command in a SplitButton [repro provided]

Describe the bug
I have a SaveImage command binded to a SplitButton.
In the attached repro, the SaveImage command just display a SaveFilePicker.
When you click the SplitButton (or via SplitButton flyout menu), the FilePicker is showing, but if you modify the filename and click Ok, after the picker is closed, the SaveImage function is called again, and again, and again.... each time you change the filename in the FilePicker.
Note: When use with a Button instead of a SplitButton, it work as expected (even if command is in a FlyoutMenu).
To Reproduce

Load the attached Repro
Click on the SplitButton, a SaveFilePicker is displayed with "Untitled.png" as default filename.
Replace the filename with something like "lmkfdmlkm"
Validate the SaveFilePicker
You should see the SaveImage() method called again, and the SaveFilePicker display again...

AvaloniaSaveFilePickerBug.zip

OS: Windows 11
Version 11.0.0

Any status about this?

@robloo do you have any idea about it?

I have no idea and would have to debug it when I have some time. The SplitButton is designed to work the same as Button and the command handling code was copied from Button too.
How this can be affected by a FilePicker is really strange as well.

I took a quick look at this. It isn't reproducible with Window 10 Pro. I tried with both the provided sample app and with a few tests in ControlCatalog.
I suspect it has something to do with the file save picker or Windows 11 rather than the SplitButton. Therefore, I don't plan to investigate further unless information points back to the SplitButton.

A few more thoughts:

Try binding to just the method directly (avoiding MVVM toolkit usage)
Try using the managed file picker instead of system-native one
Try doing something other than opening a picker in the command

The answer to those checks should narrow this down quite a bit.

@robloo Thank you to had a look.
This issue is very strange, I retry my repro sample on my Windows 10  machine after your comment yesterday and cannot reproduce it.
At the same time I retry on Windows 11 and on 20 tries, I only had the issue 1 time.
Finally, I retried again this morning on Windows 11 and I have the issue 100% of the time...
I'll to copy SplitButton code in another class and see if I got the issue and why when I have time.

@robloo An interesting find. It look like the issue only arise when I close the SaveFileDialog with Enter key (whatever I change the filename or not), no problem when I click on the Save button with mouse.
https://github.com/AvaloniaUI/Avalonia/assets/3595443/f2ce297e-86c4-4516-bd79-5510f9f17852

@robloo I copy/pasted the code of SplitButton and I found the issue!
When I close the FilePicker by pressing enter, the SplitButton received the KeyUp event and call the command again...
(I do not tested in Windows 10 yet).

Could be fixed by check if there was a corresponding KeyDown with 'Enter' I suppose...

@dbriard looks reasonable to me to add this check. Maybe you can file a PR and see if any test fail and to check the PR in your App. If all positive, I guess it can be merged.

@timunie I may give a try!

@timunie I am trying to push my fix but I got the error below:
Failed to push to the remote repository. See the Output window for more details.
Pushing fix-12320
Remote: Permission to AvaloniaUI/Avalonia.git denied to dbriard.
Failed to push to the remote repository. See the Output window for more details.
Error encountered while pushing to the remote repository: Git failed with a fatal error.
Git failed with a fatal error.
unable to access 'https://github.com/AvaloniaUI/Avalonia/': The requested URL returned error: 403

I never contributed on Github, do you have to approve my account or something to contribute?

you need to fork the repo and then add a PR later from your fork / branch. I personally use GitKraken to handle all this.
Maybe this tutorial helps: https://www.freecodecamp.org/news/how-to-make-your-first-pull-request-on-github-3/

I want to understand this a but more before the fix is merged.

Do we need to do somethung different with focus in this case. Technically the file picker should be in focus and we wouldn't receive ANY enter key again in SplitButton.
Compare with other controls. Is this a problem with any other buttons?


How to download the data sets mentioned in corpora.properties?

Would be good to have a script for it.

Unfortunately, the datasets are not publicly available. They can be found on the LDC website though:
https://catalog.ldc.upenn.edu/LDC95T7
https://catalog.ldc.upenn.edu/LDC2005T13
The current code is mainly for replicating the reported results. I will soon add a demo that doesn't rely on these datasets. Sorry for the inconvenience.

Ok Thank,
Looking forward to the demo.


[WIP] Run on Summitdev

The magic is
-D MPI_EXEC="jsrun"
-D MPI_EXEC_NUMPROCS_FLAG="-a"
-D MPI_EXEC_POST_NUMPROCS_FLAGS="-n1;-c20;-bpacked:5"

semicolons in MPI_EXEC_POST_NUMPROCS_FLAGS instead of spaces!
bpacked means threads per task/mpirank.
-n1 means one resource set
-c20 means use all 20 cores
Since in cmake max procs for MPI is set to 4, I've set 5 threads per rank maximum to not create more threads then there are cores.
Technically -bpacked is supposed to be 20 divided by the number of ranks.

If you want more maximum threads, you'd either make -bpacked adaptable or live with using hyperthreading / multiple threads per core.

Can one of the admins verify this patch?

ok to test
@hydroo Were you actually able to run all the tests on summitdev using ctest after you configured with these flags?

Codecov Report

Merging #388 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #388   +/-   ##
=======================================
  Coverage   97.96%   97.96%
=======================================
  Files          86       86
  Lines        5957     5957
=======================================
  Hits         5836     5836
  Misses        121      121

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 58621ef...c094da0. Read the comment docs.

Jsrun is awfully slow. And the graphicscard setup seems wrong (I'll fix that). Other than that it looks promissing. Will keep you updated.

You either want to disable the CUDA ETI or pass -g1 to jsrun

I sent the ctest logs to @dalg24. Looks OK (Except DataTransferKitDiscretization_PointSearch_MPI_4 is segfaulting on Peak).
Should I mention somewhere that these instruction work on Summit?
I.e. rename things to just "summit" or "summitdev_and_summit"?


Add active switch discovery documentation and examples

Adding initial documentation describing how to create custom switch discovery workflows to create catalogs and deploy startup config files.
Supports:
https://github.com/RackHD/on-http/pull/210
https://github.com/RackHD/on-taskgraph/pull/84
FYI @dpasupathi
@RackHD/corecommitters @heckj @johren @pscharla

:+1:

+1

+1

👍


Process media resources as multipart/form-data in OData v4 as sent by sap.ui.unified.FileUploader

Hello UI5 Experts,
in addition to the issue #20 there is also a problem when using the OData v4 endpoint from an SAPUI5 UI. The control sap.ui.unified.FileUploader uses a HTTP POST and multipart/form-data to upload the file. To switch to the required PUT operation as described here I've used the a CustomFileUploader from  Arindam Seth. But also this one uses multipart/form-data. As CAP and UI5 are both created by SAP I would expect that both work together smoothly.
You can replicate the issue by using my example project that can be found at:
https://github.com/gregorwolf/cap-community/tree/master/examples/media-handling
you can get it running by using:
npm run build
npm run deploy
npm run start

Now open http://localhost:4004/ and try to upload a png file. I.e. the one from the srv/tests folder of the project.
After the upload the picture should be displayed in the list below the field. But you will only see a GUID. That is caused due to to fact that simply all body data is stored without parsing. When you run the tests in srv/tests/media.http with the VS Code REST Client you will see the uploaded picture.
Best regards
Gregor

hi, i think i'll grab this use case (ui5 file uploader & cap media handling) and utilize it for the upcoming ui5con in belgium.
so please expect some work here until end of jan 2020 - and nothing over xmas and new years :)
merry whatever you in the #cap- and #ui5-community celebrate 🍩🍹🎉🎄

volker

Where you able to share something at UI5con Belgium regarding this topic?

yes, I did - and finally got around cleaning it up some: https://github.com/vobu/ui5-cap
will also replace the (your) custom Upload control soon w/ a more streamlined one - and probably also move controls to web components where applicable

Great. Have you tried it also for OData V2?

In the case that you didn't check it in the meantime by yourself @gregorwolf. Yes, it does also work with V2


[Bug report] custom scope enter empty will output ___CUSTOM___

✅ Checklist

[X] I am using the latest version
[X] I have searched FAQ

📄 System Info
System:
    OS: macOS 12.3
    CPU: (8) arm64 Apple M1 Pro
    Memory: 103.77 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 18.6.0 - /opt/homebrew/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 8.13.2 - /opt/homebrew/bin/npm
  npmGlobalPackages:
    commitizen: 4.2.5
    cz-git: 1.3.10

🔎 Description
Concise Description
custom scope enter empty will output ___CUSTOM___
Expected behavior
feat: asd
Steps to reproduce

select custom
enter empty

Screenshots or Screen Recording(if possible)

🔗 Reproduction link / repo:
No response

⭐ v1.3.9 ⭐ has been released 🥳


fix(core): when adding sub fields, the field type does not get passed correctly

Fixed in https://github.com/margarita-form/margarita-form/commit/83031194221bb7c627539a42511c4a6ae6e1e042


Whip teammates doesn't save in config (very minor issue)

Fedoraware Version Date: April 5 2022 10:56:21
Config used:
Any config
Description:
Whip teammates doesn't save in config, so whenever you save a config with the Whip teammates ticked on it won't save
Steps to reproduce:

[x] I am able to consistently reproduce this error

Steps to reproduce the behavior:

Load fedware
Load a config that doesn't have the Whip teammates ticked on
Whip teammates will still be active
tl;dr Whip teammates doesn't save on the config file

Additional context
tl;dr Whip teammates doesn't save on the config file

[x] I have included the steps to reproduce to the best I am able to share.

you could fix this yourself.


Changed parameter for 'linkType'

The parameter for link type is 'pe'. This is not passed in the header.

Suggested a change the analytics parameter for link type.

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Hold off on merging until I can look this over and discuss with @shay-o

Tracked internally via AN-326503

lgtm


OpenGraph/TwitterCard support

When sharing the URL on social media, it would likely be more impactful if there was OpenGraph/Twittercard metadata so we get a cool visual clicky thing.
Compare

Vs

Can have a crack at this maybe tomorrow, but as it's part of the branding of the product I'm sure the originators would like to have a say in what gets shown graphically / copy wise!
Great service, by the way. 🌟

I love the idea! Not one of the originators, but a huge fan of the product

This is a great idea! How much space do we have for copy?


Add build tooling with support for HMR

Vite seems to be the best available tool (currently) for development
The main package, rollup-plugin-module-federation, would need to be built in library mode

Library mode includes a simple and opinionated configuration for browser-oriented and JS framework libraries. If you are building non-browser libraries, or require advanced build flows, you can use Rollup or esbuild directly.

As per vite's official documentation, vite is not suited for this use case

The example projects have the potential to use vite as they integrate with an html

The example project needs to support multiple output targets (like ESM, SystemJS, AMD, UMD) with custom consumption patterns according to the output target


Fix docker manifest doc link

Proposed changes
Link is not relative, remove leading .

Deploy preview for docsdocker ready!
Built with commit 0ca264d2b8144bf82da6a2579461c3533c951db0
https://deploy-preview-7646--docsdocker.netlify.com


Some dev dependencies needed for all builds

In GitLab by @arisilon on Oct 21, 2019, 16:52
keyring, twine, setuptools, and xmlrunner need to be installed for all builds.

In GitLab by @arisilon on Oct 24, 2019, 10:39
closed


drivers: ssd1306: When 128x32 is used, only half of the screen is output.

I have a 128x32 SSD1306 module.
SSD1306 Module(128x32): Adafruit PiOLED - 128x32 Monochrome OLED Add-on for Raspberry Pi
There is height in dts of SSD1306.
height:
  type: int
  category: required
  description: Height in pixel of the panel driven by the controller
  generation: define

So I put 32 in the height as shown below.
However, only half of the screen is printed.
ssd1306@3c {
        compatible = "solomon,ssd1306fb";
        reg = <0x3c>;
        label = "SSD1306";
        width = <128>;
        height = <32>;
        segment-offset = <0>;
        page-offset = <0>;
        display-offset = <0>;
        segment-remap;
        com-invdir;
        prechargep = <0x22>;
};

Below is the output of the screen according to the height value.
I tested it with cfb_shell.
cfb init
cfb print 0 0<PHONE_NUMBER>

height = <64>
height = <32>

I tried to modify it as below.
The results are slightly different, but still half the output.
diff --git a/drivers/display/ssd1306.c b/drivers/display/ssd1306.c
index 3c91e3d812..b354d6e4e3 100644
--- a/drivers/display/ssd1306.c
+++ b/drivers/display/ssd1306.c
@@ -32,7 +32,7 @@ LOG_MODULE_REGISTER(ssd1306);
 #define SSD1306_PANEL_NUMOF_PAGES      (DT_SOLOMON_SSD1306FB_0_HEIGHT / 8)
 #define SSD1306_CLOCK_DIV_RATIO                0x0
 #define SSD1306_CLOCK_FREQUENCY                0x8
-#define SSD1306_PANEL_MUX_RATIO                63
+#define SSD1306_PANEL_MUX_RATIO                (DT_SOLOMON_SSD1306FB_0_HEIGHT  - 1)
 #define SSD1306_PANEL_VCOM_DESEL_LEVEL 0x20
 #define SSD1306_PANEL_PUMP_VOLTAGE     SSD1306_SET_PUMP_VOLTAGE_90

Am I using dts incorrectly?
Or is it a driver bug?

@KwonTae-young please check #19073

@jfischer-phytec-iot
I am currently in holiday season.
I'll check it next Monday. :)

@jfischer-phytec-iot
It works fine.

@KwonTae-young :+1: maybe you would like to try samples/gui/lvgl, lvgl is more sophisticated as cfg

@jfischer-phytec-iot I checked using lvgl. Works fine. :smile:


Secure iframe

This change add iframe to the list of approved tags that can be used by VM.
The iframe takes the following properties: className, style, src, srcDoc, title, message, onMessage. The iframe has a sandbox property set to sandbox="allow-scripts", which only allows scripts.
message and onMessage are used to communicate with this iframe instance.

message will be passed to the iframe every time, the deep equal is different or the iframe is recreated. The message is passed using contentWindow.postMessage(message, "*") on the iframe.
onMessage(data) is called when the iframe passes a message to window.top. Only event.data is passed to the onMessage

Iframes can be used to embed external HTML or to use custom DOM elements, for example canvas.
The following example demonstrates how you can use an iframe to call eval:
State.init({
  text: `"b" + "a" + +"a" + "a"`,
});

const code = `

Expression:

Results:

`;

return (

    <input
      value={state.text || ""}
      onChange={(e) => State.update({ text: e.target.value })}
    />
    Iframes below

       State.update({ res1 })}
      />
       State.update({ res2 })}
      />

    Result:{" "}

      res1 = {JSON.stringify(state.res1)}
      res2 = {JSON.stringify(state.res2)}

);

@evgenykuzyakov I am happy to review this and raise any red flags, but I want to be clear in my skillset that my input should not be taken as a "security review" with approval indicating the absence of attack vectors
This seems like an addition where we might want to get eyes from the Pagoda security team or another reviewer they recommend

Important focus for anyone else who reviews: is there any way to communicate code for execution via postmessage which might bypass the VM?
Currently the answer seems like no. The structured clone algorithm prevents functions from being passed, and passing a string would run up against the same limitations of trying to define a function as a string directly in component code

Another example uses external npm library to make an Markdown editor:
const initialText = "# Hello World\n\n";
State.init({
  m: initialText,
});

const code = `

<link rel="stylesheet"<EMAIL_ADDRESS>/>

`;

return (

     State.update({ m })}
    />
    <Markdown text={state.m} />

);


Configure Anti Virus step failing

Description
Running the generateresourcesandimage.ps1 script to generate the image. the configure anti-virus script is failing with the following error :

i retried and it still fails with the same error.
i think the task names should be passed into the get-scheduledtask command let, but the current one does not, not sure if this is is the cause of the problem.
Please guide on this.
Platforms affected

[X] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 10.15
[ ] macOS 11
[ ] macOS 12
[ ] Windows Server 2019
[X] Windows Server 2022

Image version and build link
windows2022
Is it regression?
no
Expected behavior
expect it to move forward
Actual behavior
failing it with the error described as above.
Repro steps
run the generateresourcesandimage.ps1 script

Hello!
We do not observe this problem in our nightly builds:

@mikhailkoliada
I am using centralus as the region.
Do you recommend running these at the night rather than in the mrng?

@vamshisiram I am nor sure it is region/az dependent. looks like some network failure and rerun must help you

I already did rerun from the same attempt, it did not work. I mean from the same session in powershell.
I will try again in a new session.
Thanks @mikhailkoliada

Did in a new session and fails with same error.
We have defender for cloud enabled in azure subscription, that might be playing a role here. @mikhailkoliada


Hidden Test set - Semantic Kitti dataset

Hi, thanks for your amazing wonderful work. For the semantic kitti data preparation, your code only contains 00-10 sequences which contain training and val splits, in your paper you mentioned the testing split is "hidden split" which is on "online server"? Could you please tell me how to prepare the testing split (11-21 sequences), it looks that there is no .label and .invalid files for these sequences.
Thanks!

Hi @BlarkLee, Thanks for your interest in our work!
Indeed, there is no label available for the test sequences. To get the test performance you need to perform inference on the test dataset, save the output, then submit it to this competition.
https://competitions.codalab.org/competitions/22037#learn_the_details-participate
You can get the test dataset code from the KittiDataModule here
https://github.com/cv-rits/MonoScene/blob/master/monoscene/data/semantic_kitti/kitti_dm.py#L47

I see! Thank you so much for the information!


add windows test

Description of changes
Added Windows platform test
Checklist

[x] Created unit tests in tests/unit and/or in Rust for my feature if needed
[x] Ran make fix to format JS and apply Clippy auto fixes
[x] Made sure my code didn't add any additional warnings: make check
[ ] Added relevant type info in types/ directory
[ ] Updated documentation if needed (API.md/README.md/Other)

I am a bit wary of doing manual path handling, I am wondering if we should transform all the string in Path and use the std or a library. It very complex to handle all the edge cases, especially windows that has a bunch of weird paths. I use dunce for normalization.

Mixing different styles and platform differences is very troublesome. However, there is no such thing as node_resolve or node_path. Deno uses js to implement path logic and also distinguishes win and unix. We only need to ensure that common scenarios can be consistent with node. In most cases, llrt runs the bundled code.
const path = require('path')

console.log(
  path.isAbsolute("C:/"),
  path.isAbsolute("/a"),
)

/*
win: true true
unix: false ture
 */

@ahaoboy thanks for the PR. Doesn't windows also support forward slash paths these days? Can we consolidate the path module by supporting forward slashes only?

@ahaoboy thanks for the PR. Doesn't windows also support forward slash paths these days? Can we consolidate the path module by supporting forward slashes only?

There are three path separators that can be used on Windows: / , \ //  :D
In most cases, using / is fine, and in import statements, only / can be used, but considering that we cannot get rid of the influence of node and npm, and the behavior of many third-party libraries may depend on this inconsistency, I think the best way is to be consistent with node. Adding win path support is just for developers(like me) using windows to test and develop.

Stick to a shared function between linux and windows as much as possible even within functions to reduce maintenance burden and reduce error risks. Only if the same function has completely different implementations use a dedicated per OS.

Using a platform-dependent SEP_PAT variable for path segmentation seems to work well.


[DDW-1002] Implement Incentivized Testnet Daedalus Theme

This PR implements the incentivized-testnet theme as well as:

Disables theme selection in "Incentivized Testnet" Daedalus version
Defaults to "Incentivized Testnet" theme
Removes "Display Settings" item in the "Settings" screen menu

Screenshots

Testing Checklist

Slack QA thread

Review Checklist
Basics

[x] PR has been assigned and has appropriate labels (feature/bug/chore, release-x.x.x)
[x] PR is updated to the most recent version of the target branch (and there are no conflicts)
[x] PR has a good description that summarizes all changes and shows some screenshots or animated GIFs of important UI changes
[x] CHANGELOG entry has been added to the top of the appropriate section (Features, Fixes, Chores) and is linked to the correct PR on GitHub
[x] Automated tests: All acceptance and unit tests are passing (yarn test)
[x] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in development build (yarn dev)
[x] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in production build (yarn package / CI builds)
[x] There are no flow errors or warnings (yarn flow:test)
[x] There are no lint errors or warnings (yarn lint)
[x] There are no prettier errors or warnings (yarn prettier:check)
[x] There are no missing translations (running yarn manage:translations produces no changes)
[ ] Text changes are proofread and approved (Jane Wild / Amy Reeve)
[x] Japanese text changes are proofread and approved (Junko Oda)
[ ] UI changes look good in all themes (Alexander Rukin)
[x] Storybook works and no stories are broken (yarn storybook)
[x] In case of dependency changes yarn.lock file is updated

Code Quality

[x] Important parts of the code are properly commented and documented
[x] Code is properly typed with flow
[x] React components are split-up enough to avoid unnecessary re-renderings
[x] Any code that only works in main process is neatly separated from components

Testing

[x] New feature/change is covered by acceptance tests
[x] New feature/change is manually tested and approved by QA team
[x] All existing acceptance tests are still up-to-date
[x] New feature/change is covered by Daedalus Testing scenario
[x] All existing Daedalus Testing scenarios are still up-to-date

After Review

[ ] Merge the PR
[ ] Delete the source branch
[ ] Move the ticket to done column on the YouTrack board
[ ] Update Slack QA thread by marking it with a green checkmark

No plans to add this theme to storybook?

@SebastienGllmt it will be added. No worries!
cc @MarcusHurney

for "dark-cardano" and "ITN" themes let's switch this spinner color on button to a text color

https://zpl.io/b6B0oYN checkboxes and radio buttons should have dark instead of white

May be it's an old branch fork, but this issue with paddings again here:

@MarcusHurney Hello Marcus. Could you please update PR description with details about which screens were already implemented. Comparing to Zeplin info in Story Book we are missing a lot of screen so it might be the case all of those missing screens are just not Ready yet.
Thank you in advance.

@DmitriiGaico only existing screens are styled. No new screens need to be added in the scope of this PR. Please list what are your concerns.

@MarcusHurney @nikolaglumac
Please see below :
Having Trouble Connecting to Network screen in Zeplin

Same screen in StoryBook

It's not the same at all.

@DmitriiGaico only background should be fixed. Other changes will be implemented in a separate task.

https://zpl.io/b6B0oYN

Here are styles for the warning button to avoid confusion with original red buttons (with white text) and theme-specific buttons (dark text)

@DmitriiGaico I've corrected the background color of the syncing and connecting screens to match the Zeplin mockup as you pointed out.
@nikolaglumac  @a-rukin The export wallet screen doesn't actually exist in the app so there is no need to worry about the colors there. The spinner on all the other buttons is the same color as the button text. I've also changed the warning buttons to the orange color, along with the warning check boxes. Unfortunately we do not use the terminology "warning" in the code itself, so I don't actually know which buttons are considered warning buttons. I've just made my best guess here.
There is however an issue with changing the checkmark color. We do not have a CSS variable implemented in react-polymorph for the checkmark color, therefore it can't be overwritten in our theme files. In order to change the checkmark color from white (as it currently is) to the dark blue text color in the mockups, I would need to implement the variable in react-polymorph, then install it in this PR, and overwrite the new color variable. This will change the checkmark color. Yes or no?

@a-rukin can you assist us here? Please check if @MarcusHurney updated the correct warning buttons and didn't leave out some of them.
@MarcusHurney in general "warning" buttons are the ones displayed in red background color in other themes - e.g. the light-blue one.
I believe we can go without having the right checkmark color BUT I believe we can probably modify those even without updating the React polymorph. I will check if this is doable today.

Button for the "delete wallet" dialog is updated 👍
Checkbox background updated also, but check-marks √ are white. If it's a tough issue to fix, we probably can live with this. This decision is up to @nikolaglumac then.

in general "warning" buttons are the ones displayed in red background color in other themes - e.g. the light-blue one.

And how do we call these "delete wallet" buttons or when we try to cancel something?

@MarcusHurney @a-rukin the checkbox icon color has been fixed: https://github.com/input-output-hk/daedalus/pull/1620/commits/74420428b45f61625e4114b4cd4cbced889b2bd3
Currently, I have overridden the color but we will fix this properly in within React-Polymorph in the scope of this task: https://iohk.myjetbrains.com/youtrack/issue/DDW-1031
cc @DominikGuzei


[WIP] Make searching through Tag categories and values work

Related BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1797737
The related BZ says about a different bug (found in CFME 5.11/ivanchuk) but we need changes in this PR to be able to reproduce (and to fix) that bug also on the newest master, where we were not able to search for categories or values at all, while tagging selected items, because isSearchable was always set to false.

Before:
Selecting Tag Category:

Selecting Tag Value:

After:

If there is no Category chosen yet, there is no reason to search through values:

@PanSpagetka @himdel @Hyperkid123 This PR is WIP because probably I will need to update the tests and because I am not 100% sure about these changes but you can review it anyway. Thank you in advance! :)

@hstastna just update the jest snapshots please.

@Hyperkid123 I am not sure why it is still failing...

:tada: This PR is included in version 0.11.61 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Unify init scripts

There is a simple matrix to handle service initialization among different different Wildfly versions/OS's:
Init system: init.d, systemd
Markerfile: with, without
Use latest version init script as module template and handle the differences.
It solves issue #125

Recovered a mapping I did while ago and decided to keep the current strategy, but using params class to handle these differences instead of init parameters:

Wildfly Version >= 10

docs/contrib/init.d/wildfly-init-{redhat,debian}.sh
wildfly.conf
docs/contrib/systemd/wildfly.service
wildfly.conf
launch.sh

Wildfly < 10

bin/init.d/wildfly-init-{redhat,debian}.sh
wildfly.conf
NOTE: Version 8.2 introduced JBOSS_OPTS in wildfly.conf. i.e. a nice way to change bind.

JBoss AS 7

bin/init.d/jboss-as-standalone.sh
jboss-as.conf
NOTE: RedHat family and standalone mode only

JBoss EAP 6

bin/init.d/jboss-as-{standalone,domain}.sh
jboss-as.conf
NOTE: RedHat family only

JBoss EAP 7

bin/init.d/jboss-eap-rhel.sh
jboss-eap.conf
NOTE:: RedHat family only
Anything different from Wildfly 10 will need to use systemd with init.d scripts.
systemd for (Debian >= 8 and RHEL >= 7)
Problem: All custom types auto require wildfly service. Alternative: change to `['wildfly', 'jboss-as', 'jboss-eap']' or introduce a new param.

Will not handle AS 7, but still need to let people manage service in their own way.


Linking issue with IPOPT/Missing IpIpoptData.hpp

I am getting an annoying compiling error:
quad-sdk/nmpc_controller/include/nmpc_controller/quad_nlp.h:15:10: fatal error: IpIpoptData.hpp: No such file or directory
And I am not sure why as all installations and setup bash scripts ran as instructed.

HI all, actually it seems that IpIpoptData.hpp does not exist in the IPOPT HSL solver.  So it might not be a linking issue but rather a change on the IPOPT package?

Yeah, I get the same error and cant find a way to get rid of it. I did manage the build 2 months ago. However, when i try to reinstall the quad-sdk, i repeatedly get this error :(

This may be due to the update on the IPOPT side as we have not made any changes on the main related to this. We are investigating this and will post a solution soon.

The issue appear to be with the latest update of IPOPT. Simply changing line 19 of /external/setup_deps.sh to "./coinbrew fetch<EMAIL_ADDRESS>--no-prompt" to use release 3.13 should work. We will push this change along with some updates to dependency installations soon.

Hello! Tried your suggestion @ardalantj. Still having issues with the build. Did this work for someone else?! This is a new installation for me.

Hi. I also tried @ardalantj's suggestion and it did not work. I still have this error.

Hi all, OK it compiles if you change also line 29 accordingly, i.e<EMAIL_ADDRESS>

@dkanou Great ! thanks for sharing that.

@Boogard2021 @fegaeze Let me know if this works for you so we can close the issue.

Hello! Just tried to change the version for both lines. Everything seemed fine during setup. When I tried to catkin build, nmpc_controller failed. Maybe there are some other issues? Still the same error about Missing IpIpoptData.hpp

I build ipopt by hand. By opening terminal at external folder and write ./configure and then make and then sudo make install after that i recieve error in #318. To solve it I reinstall some dependencies and write sudo apt-get update and then sudo apt-get upgrade which solve my issues. However, I am a newbie at Ubuntu, I do not know what exactly solved my issues. Hope this helps somehow.

@ardalantj Tried a clean install. Still didn't work. Then tried fix by @eorhon, and it worked.

@eorhon Thanks for your suggestion. It compiled successfully.

@eorhon, @dkanou, the issue appear to be with the latest update of IPOPT. Simply changing line 19 of /external/setup_deps.sh to "./coinbrew fetch<EMAIL_ADDRESS>--no-prompt" to use release 3.13 should work. We will push this change along with some updates to dependency installations soon.

after done, more errors occured:
Errors     << nmpc_controller:make /home/ros/cmu/quad_sdk/logs/nmpc_controller/build.make.014.log
In file included from /home/ros/cmu/quad_sdk/src/quad-sdk/nmpc_controller/src/quad_nlp_utils.cpp:1:0:
/home/ros/cmu/quad_sdk/src/quad-sdk/nmpc_controller/include/nmpc_controller/quad_nlp.h:15:10: fatal error: IpIpoptData.hpp: No such file or directory
#include <IpIpoptData.hpp>
^~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/nmpc_controller.dir/src/quad_nlp_utils.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
In file included from /home/ros/cmu/quad_sdk/src/quad-sdk/nmpc_controller/src/quad_nlp.cpp:1:0:
/home/ros/cmu/quad_sdk/src/quad-sdk/nmpc_controller/include/nmpc_controller/quad_nlp.h:15:10: fatal error: IpIpoptData.hpp: No such file or directory
#include <IpIpoptData.hpp>
^~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/nmpc_controller.dir/src/quad_nlp.cpp.o] Error 1
In file included from /home/ros/cmu/quad_sdk/src/quad-sdk/nmpc_controller/src/nmpc_controller.cpp:1:0:
/home/ros/cmu/quad_sdk/src/quad-sdk/nmpc_controller/include/nmpc_controller/nmpc_controller.h:16:10: fatal error: IpIpoptApplication.hpp: No such file or directory
#include "IpIpoptApplication.hpp"
^~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/nmpc_controller.dir/src/nmpc_controller.cpp.o] Error 1
make[1]: *** [CMakeFiles/nmpc_controller.dir/all] Error 2
make: *** [all] Error 2
cd /home/ros/cmu/quad_sdk/build/nmpc_controller; catkin build --get-env nmpc_controller | catkin env -si  /usr/bin/make --jobserver-fds=3,4 -j; cd -
...........................................................................................................................................................................................................
Failed     << nmpc_controller:make               [ Exited with code 2 ]
Failed    <<< nmpc_controller                    [ 3.2 seconds ]
Abandoned <<< local_planner                      [ Unrelated job failed ]
[build] Summary: 11 of 13 packages succeeded.
[build]   Ignored:   None.
[build]   Warnings:  None.
[build]   Abandoned: 1 packages were abandoned.
[build]   Failed:    1 packages failed.
[build] Runtime: 5.6 seconds total.


⚠ DDoS-Relay AU-syd1-02 has degraded performance

In ec5d4ad, DDoS-Relay AU-syd1-02 (http://<IP_ADDRESS>:42069/;csv) experienced degraded performance:

HTTP code: 200
Response time: 369 ms

Resolved: DDoS-Relay AU-syd1-02 performance has improved in 072d0bc after 12 minutes.


DTSPB-1869-remove-logs

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/DTSPB-1869
Change description
removed unnecessary logs
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[X] No

reviewed PR and looks fine


Use proper types for addSnapshotSerializer

The current flow-typed definition will error on any proper usage of this function, since it needs to take in an object shaped as such, not a function (input: Object): string.
This PR uses the same types as Jest declares for these functions internally.
This function is defined within Jest here, by assigning the value to the function addSerializer, defined here, which takes in a type Plugin, defined here.
You can see how Jest tests this internally here.
You can see more documentation about expect.addSnapshotSerializer(serializer) in Jest's docs.

Hm, this error is interesting. Any idea why this is failing? https://travis-ci.org/flowtype/flow-typed/jobs/243716405#L1151-L1154

I'm going to close this since this repo seems to be unmaintained.

Stumbled upon this today, too bad you closed it as you provided a correct fix.

@AndrewSouthpaw  @GAntoine  @villesau is it possible to re-open this PR again?

I don't mind reopening it, but I don't use flow-typed any more, so others can feel free to get this wrapped up and merged.

Thanks for bringing this up @mikewoudenberg. Considering the age of this PR, I'd recommend opening a new PR branched from the latest version of master with these changes. Would you be up for it?
@eliperkins Sorry no one got around to this issue the first time around. 😞


Public API for computed prop's similar to Vue.observable

What problem does this feature solve?
With the new Vue.observable you can create a simple reactive store which is super nice. It seems you can use these reactive properties directly in views (you don't need to use them through local computed properties). In this scenario, it would be nice to be able to also have global state based computed properties. This way, you'd be able to create a very nice and imo quite capable yet simple store pattern (compared to more verbose and complex solutions like Vuex). You also don't have to sprinkle computed props on components where they imo don't really belong.
It's possible to do a workaround by initiating new Vue instances, but I assume that causes some significant and completely unnecessary overhead.
What does the proposed API look like?
I'm completely open for your wisedom ;-) A few suggestions:
A)
Vue.computed({
computedProp: function() { ... }
});
B)
Vue.observable({
regularReactiveProp: 'something',
get computedProp: function () { ... }
});
I'm btw. not a big fan of transforming all functions to computed props, as this makes it less simple (impossible?) to pass along one store object that also contains all methods (for a more full scale model layer).

There are plans of exposing these things in Vue 3 and maybe 2.x. An RFC will be published in the following weeks :)
Closing to prevent duplication

Excellent! Thanks! 🙂


how-tos missing

From README.md on 27 May 2015 (almost two years ago):

How-tos will be added in a day or two...

I know it might be late, but they are in the Wiki section

@epekel, can you please direct me to them?  None of the three pages I can see in the Wiki section have any how-tos.

I disagree that these qualify as how-tos.

One of those pages is a single “welcome” sentence.
Another merely lists parameters.
“The bare minimum” gives a function call with minimal explanation.

I've added a page to the wiki which gives an example of how to use this library. Took a while for me to figure it out myself, thought it'd be nice to share with others so they don't have to go through the same thing.
See https://github.com/vikramkakkar/SublimePicker/wiki/Example