HADOOP-16490. Improve S3Guard handling of FNFEs in copy

S3Guard retry policy independently configurable from other retry policies,

and use a setting with exponential backoff
new config names
copy raises a RemoteFileChangedException which is not caught in rename() and downgraded to false. Thus: when a rename is unrecoverable, this fact is propagated
tests for this
More logging @ debug in change policies as to policy type and when options are not set, as well as being set. Currently to work out the policy involves looking for the absence of messages, not the presence. It makes the file more verbose, but will aid with debugging these problems.

Also: tests turning auth mode on/off have to handle the auth state being set through an authoritative path, rather than a single flag. Caught me out as of course the first test I saw with this was the ITestS3ARemoteFileChanged rename ones, and I assumed that it was my new code. It was actually due to me setting an auth path last week.
I'm unsure about the use of "RemoteFileChangedException", but it could be a remote file change, especially for an etag, where the file has been deleted since being recorded.I don't know if/how we should adapt to that in S3Guard if the problem persists. The file is either no longer there or changes not yet visible. Maybe consider marking parent dir as nonauth?
Also, how about we log the RemoteFileChangedException error message before we throw it, so that there's more details in the log of the problem, irrespective of the action in the app calling it (i.e. fsshell discarding it, possibly)
Change-Id: I7bb468aca0f4019537d82bc083f0a9887eaa282b

Full test run in progress.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
39
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 4 new or modified test files.

_ trunk Compile Tests _

0
mvndep
72
Maven dependency ordering for branch

+1
mvninstall
1088
trunk passed

+1
compile
1064
trunk passed

+1
checkstyle
146
trunk passed

+1
mvnsite
137
trunk passed

+1
shadedclient
1039
branch has no errors when building and testing our client artifacts.

+1
javadoc
108
trunk passed

0
spotbugs
71
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
193
trunk passed

_ Patch Compile Tests _

0
mvndep
26
Maven dependency ordering for patch

+1
mvninstall
108
the patch passed

+1
compile
1039
the patch passed

+1
javac
1039
the patch passed

-0
checkstyle
177
root: The patch generated 12 new + 27 unchanged - 0 fixed = 39 total (was 27)

+1
mvnsite
133
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
2
The patch has no ill-formed XML file.

+1
shadedclient
696
patch has no errors when building and testing our client artifacts.

+1
javadoc
110
the patch passed

+1
findbugs
212
the patch passed

_ Other Tests _

+1
unit
552
hadoop-common in the patch passed.

+1
unit
294
hadoop-aws in the patch passed.

+1
asflicense
47
The patch does not generate ASF License warnings.

7300

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/2/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml findbugs checkstyle

uname
Linux 97e535d46df6 4.4.0-157-generic #185-Ubuntu SMP Tue Jul 23 09:17:01 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / d6697da

Default Java
1.8.0_212

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/2/artifact/out/diff-checkstyle-root.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/2/testReport/

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

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

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/2/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
53
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 4 new or modified test files.

_ trunk Compile Tests _

0
mvndep
23
Maven dependency ordering for branch

+1
mvninstall
1129
trunk passed

+1
compile
1075
trunk passed

+1
checkstyle
141
trunk passed

+1
mvnsite
112
trunk passed

+1
shadedclient
954
branch has no errors when building and testing our client artifacts.

+1
javadoc
94
trunk passed

0
spotbugs
59
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
179
trunk passed

_ Patch Compile Tests _

0
mvndep
24
Maven dependency ordering for patch

+1
mvninstall
76
the patch passed

+1
compile
1052
the patch passed

+1
javac
1052
the patch passed

-0
checkstyle
132
root: The patch generated 12 new + 27 unchanged - 0 fixed = 39 total (was 27)

+1
mvnsite
108
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
1
The patch has no ill-formed XML file.

+1
shadedclient
639
patch has no errors when building and testing our client artifacts.

+1
javadoc
86
the patch passed

+1
findbugs
201
the patch passed

_ Other Tests _

+1
unit
555
hadoop-common in the patch passed.

+1
unit
285
hadoop-aws in the patch passed.

+1
asflicense
47
The patch does not generate ASF License warnings.

6980

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/3/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml findbugs checkstyle

uname
Linux fe539d9feb9a 4.4.0-157-generic #185-Ubuntu SMP Tue Jul 23 09:17:01 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 3cc0ace

Default Java
1.8.0_212

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/3/artifact/out/diff-checkstyle-root.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/3/testReport/

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

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

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/3/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
61
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 4 new or modified test files.

_ trunk Compile Tests _

0
mvndep
22
Maven dependency ordering for branch

+1
mvninstall
1059
trunk passed

+1
compile
1058
trunk passed

+1
checkstyle
138
trunk passed

+1
mvnsite
111
trunk passed

+1
shadedclient
952
branch has no errors when building and testing our client artifacts.

+1
javadoc
88
trunk passed

0
spotbugs
61
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
171
trunk passed

_ Patch Compile Tests _

0
mvndep
21
Maven dependency ordering for patch

+1
mvninstall
73
the patch passed

+1
compile
1061
the patch passed

+1
javac
1061
the patch passed

-0
checkstyle
156
root: The patch generated 12 new + 27 unchanged - 0 fixed = 39 total (was 27)

+1
mvnsite
106
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
1
The patch has no ill-formed XML file.

+1
shadedclient
615
patch has no errors when building and testing our client artifacts.

+1
javadoc
92
the patch passed

+1
findbugs
190
the patch passed

_ Other Tests _

+1
unit
526
hadoop-common in the patch passed.

+1
unit
279
hadoop-aws in the patch passed.

+1
asflicense
41
The patch does not generate ASF License warnings.

6823

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/4/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml findbugs checkstyle

uname
Linux 72abfc09217a 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 00b5a27

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/4/artifact/out/diff-checkstyle-root.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/4/testReport/

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

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

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/4/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

This currently conflicts with https://github.com/apache/hadoop/pull/1246; that should go in first as it is the basic resilience; here i want to eliminate that HEAD entirely

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
78
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 4 new or modified test files.

_ trunk Compile Tests _

0
mvndep
21
Maven dependency ordering for branch

+1
mvninstall
1073
trunk passed

+1
compile
1157
trunk passed

+1
checkstyle
139
trunk passed

+1
mvnsite
130
trunk passed

+1
shadedclient
1005
branch has no errors when building and testing our client artifacts.

+1
javadoc
87
trunk passed

0
spotbugs
61
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
171
trunk passed

_ Patch Compile Tests _

0
mvndep
23
Maven dependency ordering for patch

+1
mvninstall
75
the patch passed

+1
compile
1035
the patch passed

+1
javac
1035
the patch passed

-0
checkstyle
132
root: The patch generated 2 new + 46 unchanged - 0 fixed = 48 total (was 46)

+1
mvnsite
109
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
1
The patch has no ill-formed XML file.

+1
shadedclient
635
patch has no errors when building and testing our client artifacts.

+1
javadoc
91
the patch passed

+1
findbugs
190
the patch passed

_ Other Tests _

-1
unit
483
hadoop-common in the patch failed.

+1
unit
280
hadoop-aws in the patch passed.

+1
asflicense
46
The patch does not generate ASF License warnings.

6939

Reason
Tests

Failed junit tests
hadoop.fs.shell.TestCopy

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/5/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle xml

uname
Linux a4c2fc14cba2 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 63161cf

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/5/artifact/out/diff-checkstyle-root.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/5/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/5/testReport/

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

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

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/5/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
54
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 4 new or modified test files.

_ trunk Compile Tests _

0
mvndep
26
Maven dependency ordering for branch

+1
mvninstall
1098
trunk passed

+1
compile
1005
trunk passed

+1
checkstyle
136
trunk passed

+1
mvnsite
113
trunk passed

+1
shadedclient
963
branch has no errors when building and testing our client artifacts.

+1
javadoc
88
trunk passed

0
spotbugs
63
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
183
trunk passed

_ Patch Compile Tests _

0
mvndep
24
Maven dependency ordering for patch

+1
mvninstall
82
the patch passed

+1
compile
1066
the patch passed

+1
javac
1066
the patch passed

-0
checkstyle
141
root: The patch generated 4 new + 46 unchanged - 0 fixed = 50 total (was 46)

+1
mvnsite
112
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
2
The patch has no ill-formed XML file.

+1
shadedclient
657
patch has no errors when building and testing our client artifacts.

+1
javadoc
89
the patch passed

+1
findbugs
204
the patch passed

_ Other Tests _

-1
unit
544
hadoop-common in the patch failed.

+1
unit
288
hadoop-aws in the patch passed.

+1
asflicense
43
The patch does not generate ASF License warnings.

6907

Reason
Tests

Failed junit tests
hadoop.fs.shell.TestCopy

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/6/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle xml

uname
Linux e2d2c6ea2623 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 63161cf

Default Java
1.8.0_212

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/6/artifact/out/diff-checkstyle-root.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/6/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/6/testReport/

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

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

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/6/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
46
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 4 new or modified test files.

_ trunk Compile Tests _

0
mvndep
22
Maven dependency ordering for branch

+1
mvninstall
1056
trunk passed

+1
compile
1068
trunk passed

+1
checkstyle
145
trunk passed

+1
mvnsite
128
trunk passed

+1
shadedclient
1009
branch has no errors when building and testing our client artifacts.

+1
javadoc
104
trunk passed

0
spotbugs
66
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
184
trunk passed

_ Patch Compile Tests _

0
mvndep
23
Maven dependency ordering for patch

+1
mvninstall
79
the patch passed

+1
compile
1014
the patch passed

+1
javac
1014
the patch passed

-0
checkstyle
145
root: The patch generated 4 new + 46 unchanged - 2 fixed = 50 total (was 48)

+1
mvnsite
123
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
1
The patch has no ill-formed XML file.

+1
shadedclient
698
patch has no errors when building and testing our client artifacts.

+1
javadoc
108
the patch passed

+1
findbugs
199
the patch passed

_ Other Tests _

-1
unit
481
hadoop-common in the patch failed.

+1
unit
83
hadoop-aws in the patch passed.

+1
asflicense
53
The patch does not generate ASF License warnings.

6797

Reason
Tests

Failed junit tests
hadoop.fs.shell.TestCopy

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/7/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle xml

uname
Linux fd968ec4a3a0 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / e25a5c2

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/7/artifact/out/diff-checkstyle-root.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/7/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/7/testReport/

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

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

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/7/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
44
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 4 new or modified test files.

_ trunk Compile Tests _

0
mvndep
23
Maven dependency ordering for branch

+1
mvninstall
1038
trunk passed

+1
compile
1049
trunk passed

+1
checkstyle
132
trunk passed

+1
mvnsite
108
trunk passed

+1
shadedclient
919
branch has no errors when building and testing our client artifacts.

+1
javadoc
97
trunk passed

0
spotbugs
59
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
174
trunk passed

_ Patch Compile Tests _

0
mvndep
23
Maven dependency ordering for patch

+1
mvninstall
75
the patch passed

+1
compile
1021
the patch passed

+1
javac
1021
the patch passed

-0
checkstyle
143
root: The patch generated 2 new + 46 unchanged - 2 fixed = 48 total (was 48)

+1
mvnsite
123
the patch passed

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

+1
xml
1
The patch has no ill-formed XML file.

+1
shadedclient
684
patch has no errors when building and testing our client artifacts.

+1
javadoc
106
the patch passed

+1
findbugs
202
the patch passed

_ Other Tests _

-1
unit
480
hadoop-common in the patch failed.

+1
unit
82
hadoop-aws in the patch passed.

+1
asflicense
54
The patch does not generate ASF License warnings.

6635

Reason
Tests

Failed junit tests
hadoop.fs.shell.TestCopy

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/8/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle xml

uname
Linux 079607da25a0 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / a79564f

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/8/artifact/out/diff-checkstyle-root.txt

whitespace
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/8/artifact/out/whitespace-eol.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/8/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/8/testReport/

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

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

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/8/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

tested s3 ireland  -Ds3guard -Ddynamo. all tests happy.
this is ready for review

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
45
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 4 new or modified test files.

_ trunk Compile Tests _

0
mvndep
66
Maven dependency ordering for branch

+1
mvninstall
1067
trunk passed

+1
compile
1045
trunk passed

+1
checkstyle
147
trunk passed

+1
mvnsite
124
trunk passed

+1
shadedclient
1011
branch has no errors when building and testing our client artifacts.

+1
javadoc
105
trunk passed

0
spotbugs
68
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
181
trunk passed

_ Patch Compile Tests _

0
mvndep
23
Maven dependency ordering for patch

+1
mvninstall
77
the patch passed

+1
compile
1014
the patch passed

+1
javac
1014
the patch passed

+1
checkstyle
141
root: The patch generated 0 new + 46 unchanged - 2 fixed = 46 total (was 48)

+1
mvnsite
124
the patch passed

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

+1
xml
2
The patch has no ill-formed XML file.

+1
shadedclient
670
patch has no errors when building and testing our client artifacts.

+1
javadoc
106
the patch passed

+1
findbugs
199
the patch passed

_ Other Tests _

-1
unit
479
hadoop-common in the patch failed.

+1
unit
77
hadoop-aws in the patch passed.

+1
asflicense
46
The patch does not generate ASF License warnings.

6781

Reason
Tests

Failed junit tests
hadoop.fs.shell.TestCopy

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/9/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle xml

uname
Linux 0eeb6b02f19c 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / fba222a

Default Java
1.8.0_222

whitespace
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/9/artifact/out/whitespace-eol.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/9/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/9/testReport/

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

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

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/9/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

Thinking about the new flag passed in to s3GetFileStatus to skip the object probe
it should be an enumset of probes:

object: check object
marker: look for directory marker
list: make a LIST call

when we create a file, we only want (marker, list)
for mkdir we would only do (object, list) and if those found nothing -create the marker, without ever looking for the marker. This will avoid creating a 404 on that probe.

we can also optimise some directory ops by skipping the list and doing the real list if the (object, marker) calls failed

Proposed changes to this PR then

enum to control which probes to make
tests to verify that create() codepath doesn't do HEAD path when overwrite=true (different asserts for s3guard/s3guard auth)
not in scope for the initial PR: expanding to mkdir and other stat ops;  keeping them separate PRs with their own tests makes the changes more incremental.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
44
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 4 new or modified test files.

_ trunk Compile Tests _

0
mvndep
85
Maven dependency ordering for branch

+1
mvninstall
1447
trunk passed

+1
compile
1386
trunk passed

+1
checkstyle
184
trunk passed

+1
mvnsite
156
trunk passed

+1
shadedclient
1265
branch has no errors when building and testing our client artifacts.

+1
javadoc
113
trunk passed

0
spotbugs
93
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
241
trunk passed

_ Patch Compile Tests _

0
mvndep
24
Maven dependency ordering for patch

+1
mvninstall
101
the patch passed

+1
compile
1089
the patch passed

+1
javac
1089
the patch passed

+1
checkstyle
144
root: The patch generated 0 new + 46 unchanged - 2 fixed = 46 total (was 48)

+1
mvnsite
117
the patch passed

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

+1
xml
2
The patch has no ill-formed XML file.

+1
shadedclient
716
patch has no errors when building and testing our client artifacts.

+1
javadoc
95
the patch passed

+1
findbugs
219
the patch passed

_ Other Tests _

-1
unit
576
hadoop-common in the patch failed.

+1
unit
74
hadoop-aws in the patch passed.

+1
asflicense
42
The patch does not generate ASF License warnings.

8097

Reason
Tests

Failed junit tests
hadoop.fs.viewfs.TestViewFsTrash

hadoop.ha.TestZKFailoverController

hadoop.fs.shell.TestCopy

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/10/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle xml

uname
Linux 45f30d875ee4 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 9b8359b

Default Java
1.8.0_222

whitespace
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/10/artifact/out/whitespace-eol.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/10/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/10/testReport/

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

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

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/10/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
52
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 4 new or modified test files.

_ trunk Compile Tests _

0
mvndep
22
Maven dependency ordering for branch

+1
mvninstall
1045
trunk passed

+1
compile
1116
trunk passed

+1
checkstyle
138
trunk passed

+1
mvnsite
113
trunk passed

+1
shadedclient
983
branch has no errors when building and testing our client artifacts.

+1
javadoc
90
trunk passed

0
spotbugs
58
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
173
trunk passed

_ Patch Compile Tests _

0
mvndep
22
Maven dependency ordering for patch

+1
mvninstall
71
the patch passed

+1
compile
1038
the patch passed

+1
javac
1038
the patch passed

+1
checkstyle
138
root: The patch generated 0 new + 46 unchanged - 2 fixed = 46 total (was 48)

+1
mvnsite
109
the patch passed

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

+1
xml
1
The patch has no ill-formed XML file.

+1
shadedclient
638
patch has no errors when building and testing our client artifacts.

+1
javadoc
104
the patch passed

+1
findbugs
204
the patch passed

_ Other Tests _

-1
unit
537
hadoop-common in the patch failed.

+1
unit
78
hadoop-aws in the patch passed.

+1
asflicense
48
The patch does not generate ASF License warnings.

6738

Reason
Tests

Failed junit tests
hadoop.fs.shell.TestCopy

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/11/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle xml

uname
Linux 45d696c6b8ed 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 6244502

Default Java
1.8.0_212

whitespace
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/11/artifact/out/whitespace-eol.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/11/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/11/testReport/

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

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

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/11/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

last update moves to a probe set so you can choose what to look for; maybeCreateFakeDirectory uses this to only do the LIST call, as we dont care if a fake dir marker is there...saves one HEAD per operation.
not tested; Gabors comments not addressed

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
43
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 4 new or modified test files.

_ trunk Compile Tests _

0
mvndep
25
Maven dependency ordering for branch

+1
mvninstall
1138
trunk passed

+1
compile
1171
trunk passed

+1
checkstyle
143
trunk passed

+1
mvnsite
129
trunk passed

+1
shadedclient
979
branch has no errors when building and testing our client artifacts.

+1
javadoc
102
trunk passed

0
spotbugs
65
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
189
trunk passed

_ Patch Compile Tests _

0
mvndep
62
Maven dependency ordering for patch

+1
mvninstall
87
the patch passed

-1
compile
993
root in the patch failed.

-1
javac
993
root in the patch failed.

-0
checkstyle
145
root: The patch generated 1 new + 46 unchanged - 2 fixed = 47 total (was 48)

+1
mvnsite
124
the patch passed

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

+1
xml
1
The patch has no ill-formed XML file.

+1
shadedclient
666
patch has no errors when building and testing our client artifacts.

+1
javadoc
87
the patch passed

+1
findbugs
192
the patch passed

_ Other Tests _

-1
unit
483
hadoop-common in the patch failed.

+1
unit
75
hadoop-aws in the patch passed.

+1
asflicense
41
The patch does not generate ASF License warnings.

6872

Reason
Tests

Failed junit tests
hadoop.fs.shell.TestCopy

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/12/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle xml

uname
Linux 5b0a4f4ad5c2 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 269b543

Default Java
1.8.0_222

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/12/artifact/out/patch-compile-root.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/12/artifact/out/patch-compile-root.txt

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/12/artifact/out/diff-checkstyle-root.txt

whitespace
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/12/artifact/out/whitespace-eol.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/12/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/12/testReport/

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

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

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/12/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

tested s3 ireland, all good but an error which hits all my branches and is clearly a config change of mine
[ERROR] test_100_FilesystemPrune(org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardDDBRootOperations)  Time elapsed: 0.856 s  <<< ERROR!
java.lang.IllegalArgumentException: No DynamoDB table name configured
	at com.google.common.base.Preconditions.checkArgument(Preconditions.java:141)
	at org.apache.hadoop.fs.s3a.s3guard.DynamoDBMetadataStore.initialize(DynamoDBMetadataStore.java:496)
	at org.apache.hadoop.fs.s3a.s3guard.S3GuardTool.initMetadataStore(S3GuardTool.java:317)
	at org.apache.hadoop.fs.s3a.s3guard.S3GuardTool$Prune.run(S3GuardTool.java:1071)
	at org.apache.hadoop.fs.s3a.s3guard.S3GuardTool.run(S3GuardTool.java:401)

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
74
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 4 new or modified test files.

_ trunk Compile Tests _

0
mvndep
22
Maven dependency ordering for branch

+1
mvninstall
1211
trunk passed

+1
compile
1083
trunk passed

+1
checkstyle
159
trunk passed

+1
mvnsite
127
trunk passed

+1
shadedclient
1111
branch has no errors when building and testing our client artifacts.

+1
javadoc
100
trunk passed

0
spotbugs
68
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
191
trunk passed

_ Patch Compile Tests _

0
mvndep
23
Maven dependency ordering for patch

+1
mvninstall
82
the patch passed

+1
compile
1019
the patch passed

+1
javac
1019
the patch passed

-0
checkstyle
155
root: The patch generated 1 new + 85 unchanged - 2 fixed = 86 total (was 87)

+1
mvnsite
126
the patch passed

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

+1
xml
1
The patch has no ill-formed XML file.

+1
shadedclient
769
patch has no errors when building and testing our client artifacts.

+1
javadoc
98
the patch passed

+1
findbugs
206
the patch passed

_ Other Tests _

-1
unit
609
hadoop-common in the patch failed.

+1
unit
89
hadoop-aws in the patch passed.

+1
asflicense
47
The patch does not generate ASF License warnings.

7303

Reason
Tests

Failed junit tests
hadoop.security.TestFixKerberosTicketOrder

hadoop.ha.TestZKFailoverController

hadoop.fs.shell.TestCopy

Subsystem
Report/Notes

Docker
Client=18.09.7 Server=18.09.7 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/14/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle xml

uname
Linux 12487ab0521f 4.15.0-52-generic #56-Ubuntu SMP Tue Jun 4 22:49:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 28fb4b5

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/14/artifact/out/diff-checkstyle-root.txt

whitespace
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/14/artifact/out/whitespace-eol.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/14/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/14/testReport/

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

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

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/14/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
36
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 4 new or modified test files.

_ trunk Compile Tests _

0
mvndep
24
Maven dependency ordering for branch

+1
mvninstall
1251
trunk passed

+1
compile
1138
trunk passed

+1
checkstyle
147
trunk passed

+1
mvnsite
123
trunk passed

+1
shadedclient
1086
branch has no errors when building and testing our client artifacts.

+1
javadoc
99
trunk passed

0
spotbugs
69
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
193
trunk passed

_ Patch Compile Tests _

0
mvndep
25
Maven dependency ordering for patch

+1
mvninstall
82
the patch passed

+1
compile
1019
the patch passed

+1
javac
1019
the patch passed

-0
checkstyle
156
root: The patch generated 1 new + 85 unchanged - 2 fixed = 86 total (was 87)

+1
mvnsite
121
the patch passed

-1
whitespace
1
The patch has 2 line(s) that end in whitespace. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

+1
xml
1
The patch has no ill-formed XML file.

+1
shadedclient
739
patch has no errors when building and testing our client artifacts.

+1
javadoc
90
the patch passed

+1
findbugs
219
the patch passed

_ Other Tests _

-1
unit
550
hadoop-common in the patch failed.

+1
unit
73
hadoop-aws in the patch passed.

+1
asflicense
42
The patch does not generate ASF License warnings.

7221

Reason
Tests

Failed junit tests
hadoop.fs.viewfs.TestViewFsTrash

hadoop.fs.shell.TestCopy

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/15/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle xml

uname
Linux aa370dfb0df7 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 28fb4b5

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/15/artifact/out/diff-checkstyle-root.txt

whitespace
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/15/artifact/out/whitespace-eol.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/15/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/15/testReport/

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

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

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/15/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
627
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 5 new or modified test files.

_ trunk Compile Tests _

0
mvndep
1711
Maven dependency ordering for branch

+1
mvninstall
1111
trunk passed

+1
compile
1008
trunk passed

+1
checkstyle
145
trunk passed

+1
mvnsite
133
trunk passed

+1
shadedclient
1006
branch has no errors when building and testing our client artifacts.

+1
javadoc
114
trunk passed

0
spotbugs
68
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
192
trunk passed

_ Patch Compile Tests _

0
mvndep
26
Maven dependency ordering for patch

+1
mvninstall
82
the patch passed

+1
compile
942
the patch passed

+1
javac
942
the patch passed

+1
checkstyle
146
root: The patch generated 0 new + 97 unchanged - 2 fixed = 97 total (was 99)

+1
mvnsite
130
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
1
The patch has no ill-formed XML file.

+1
shadedclient
672
patch has no errors when building and testing our client artifacts.

+1
javadoc
114
the patch passed

+1
findbugs
206
the patch passed

_ Other Tests _

+1
unit
547
hadoop-common in the patch passed.

+1
unit
93
hadoop-aws in the patch passed.

+1
asflicense
49
The patch does not generate ASF License warnings.

9096

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/16/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle xml

uname
Linux 2e49e7b6df2e 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 689d2e6

Default Java
1.8.0_222

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/16/testReport/

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

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

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/16/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
34
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 5 new or modified test files.

_ trunk Compile Tests _

0
mvndep
24
Maven dependency ordering for branch

+1
mvninstall
1282
trunk passed

+1
compile
1196
trunk passed

+1
checkstyle
158
trunk passed

+1
mvnsite
129
trunk passed

+1
shadedclient
1076
branch has no errors when building and testing our client artifacts.

+1
javadoc
92
trunk passed

0
spotbugs
65
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
181
trunk passed

_ Patch Compile Tests _

0
mvndep
23
Maven dependency ordering for patch

+1
mvninstall
83
the patch passed

+1
compile
1043
the patch passed

+1
javac
1043
the patch passed

+1
checkstyle
159
root: The patch generated 0 new + 97 unchanged - 2 fixed = 97 total (was 99)

+1
mvnsite
132
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
2
The patch has no ill-formed XML file.

+1
shadedclient
718
patch has no errors when building and testing our client artifacts.

+1
javadoc
110
the patch passed

+1
findbugs
204
the patch passed

_ Other Tests _

+1
unit
583
hadoop-common in the patch passed.

+1
unit
73
hadoop-aws in the patch passed.

+1
asflicense
44
The patch does not generate ASF License warnings.

7330

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/17/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle xml

uname
Linux 30aa52bd4dd8 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 3329257

Default Java
1.8.0_222

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/17/testReport/

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

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

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/17/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
39
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 5 new or modified test files.

_ trunk Compile Tests _

0
mvndep
65
Maven dependency ordering for branch

+1
mvninstall
1038
trunk passed

+1
compile
994
trunk passed

+1
checkstyle
145
trunk passed

+1
mvnsite
135
trunk passed

+1
shadedclient
1026
branch has no errors when building and testing our client artifacts.

+1
javadoc
114
trunk passed

0
spotbugs
69
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
186
trunk passed

_ Patch Compile Tests _

0
mvndep
25
Maven dependency ordering for patch

+1
mvninstall
79
the patch passed

+1
compile
932
the patch passed

+1
javac
932
the patch passed

+1
checkstyle
143
root: The patch generated 0 new + 97 unchanged - 2 fixed = 97 total (was 99)

+1
mvnsite
132
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
2
The patch has no ill-formed XML file.

+1
shadedclient
683
patch has no errors when building and testing our client artifacts.

+1
javadoc
117
the patch passed

+1
findbugs
208
the patch passed

_ Other Tests _

+1
unit
540
hadoop-common in the patch passed.

+1
unit
91
hadoop-aws in the patch passed.

+1
asflicense
52
The patch does not generate ASF License warnings.

6774

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/18/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle xml

uname
Linux 56aeb84dcda3 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 915cbc9

Default Java
1.8.0_222

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/18/testReport/

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

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

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/18/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

committed to trunk -thanks for all reviews

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
39
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 6 new or modified test files.

_ trunk Compile Tests _

0
mvndep
65
Maven dependency ordering for branch

+1
mvninstall
1020
trunk passed

+1
compile
982
trunk passed

+1
checkstyle
140
trunk passed

+1
mvnsite
133
trunk passed

+1
shadedclient
991
branch has no errors when building and testing our client artifacts.

+1
javadoc
112
trunk passed

0
spotbugs
69
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
183
trunk passed

_ Patch Compile Tests _

0
mvndep
24
Maven dependency ordering for patch

+1
mvninstall
80
the patch passed

+1
compile
934
the patch passed

+1
javac
934
the patch passed

+1
checkstyle
149
root: The patch generated 0 new + 97 unchanged - 2 fixed = 97 total (was 99)

+1
mvnsite
129
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
xml
2
The patch has no ill-formed XML file.

+1
shadedclient
684
patch has no errors when building and testing our client artifacts.

+1
javadoc
112
the patch passed

+1
findbugs
203
the patch passed

_ Other Tests _

+1
unit
550
hadoop-common in the patch passed.

+1
unit
94
hadoop-aws in the patch passed.

+1
asflicense
52
The patch does not generate ASF License warnings.

6724

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/19/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle xml

uname
Linux 9a81c091b006 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 172bcd8

Default Java
1.8.0_222

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/19/testReport/

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

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

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1229/19/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

I closed the wrong PR!


Small caps

If the font supports native small caps, we should be able to use them. If not, a runtime error should occur - no ugly small caps here!

There are new small caps features in San Francisco, and they should be supported as well.

Dup #173


Add missing overlay buttons on linked field in demo cards

Previously, the "Open" buttons in demo cards did not show up in cases of embedded "author" and "friend". They show up now:

This was due to missing ...attributes which I added to demo cards where necessary.
Adding ...attributes allows for the LinksToCardComponentModifier to be applied on linked card elements, which registers the element in operator mode so that we know where to place the overlayed "Open" buttons.

@burieberry sounds good.


Get Titlebar fixed for the Datapack Generator Electron App

Titlebar is currently fairly broken, showing a < in the top left, and having wrong proportions

This actually is a part of devOS-Sanity-Edition/DimensionsDatapackGen

This actually is a part of devOS-Sanity-Edition/DimensionsDatapackGen


This does not work for me

Dumping update log :
AppPath: xxxx
AppPathFolder: xxxxx
1.0.0
Update available: 1.0.1
Downloading http://www.abc.com/api/xyz/update_download/update.zip
Do something after request finishes
ZipFilePath: xxxx
Updater.update.file: F:\Users\xyz\Desktop\win-unpacked\resources\update.asar
Update Zip downloaded: F:\Users\xyz\Desktop\win-unpacked\resources
Checking for F:\Users\xyz\Desktop\win-unpacked\resources\update.asar
Going to shell out to move: F:\xxx to: F:\xxx
Going to start the windows updater: F:\xxx\updater.exe F:\xxx\update.asar F:\xxx\resources\app.asar
"F:\xxx\updater.exe" "F:\xxx\resources\update.asar" "F:\xxx\app.asar"

Update : the zip file gets downloaded but this happens :
AppPath: F:\Users\xyz\Desktop\win-unpacked\resources\app.asar/
AppPathFolder: F:\Users\xyz\Desktop\win-unpacked\resources
1.0.0
Update available: 1.0.1
Downloading http://www.abc.com/api/xyz/update_download/update.zip
Do something after request finishes
ZipFilePath: F:\Users\xyz\Desktop\win-unpacked\resources
unzip error: Invalid or unsupported zip format. No END header found

Thank you for responding @yansenlei
Platform : Windows 7 (x64)
I have used WinRaR, 7-Zip and the node module 'adm-zip' to pack my asar file but none of them solved this issue.
The asar file works just fine when I unpack the generated zip manually.

@Pepnode
Ok, thank you for your feedback, I will reproduce this bug according to your environment.
Before that, can you try to use adm-zip in your code? Because I used it to decompress.

@yansenlei I wrote a script using 'adm-zip' and successfully extracted the archive without any errors. But when I use the your code, it throws the exception
"unzip error: Invalid or unsupported zip format. No END header found"
It is possible that the the archive is being extracted before it gets fully downloaded.

@yansenlei any luck?

@Pepnode
I am pushed a update demo: https://github.com/yansenlei/asar-update-project

@yansenlei thank you! I got it to work.


Clarify numba ufunc supported features

Added a note mentioning that users shouldn't expect all ufunc features to work in compiled code.
Based on comment here https://github.com/numba/numba/issues/4504#issuecomment-527102530.

Thanks for the PR, totally agree that this needs some clarification. I've commented on the PR about how to perhaps investigate what's going on.


could you upload the source of TweakLoader?

could you upload the source of TweakLoader?

I really love libhooker, it's a modern hooking framework written entirely in C.


[pre alpha]  ERROR: Failed building wheel for faiss-cpu

Describe the bug
an error causing install failures. See below for details,
Browser and Version

Browser [e.g. chrome, safari]- n/a
Version [e.g. 22]- n/a

To Reproduce
Steps to reproduce the behavior:

Run python -m pip install langflow --pre --force-reinstall -U, and errors as below:

...
Collecting grpcio-status<2.0.dev0,>=1.33.2
  Using cached grpcio_status-1.64.1-py3-none-any.whl (14 kB)
  Using cached grpcio_status-1.64.0-py3-none-any.whl (14 kB)
  Using cached grpcio_status-1.64.0rc1-py3-none-any.whl (14 kB)
  Using cached grpcio_status-1.63.0-py3-none-any.whl (14 kB)
  Using cached grpcio_status-1.63.0rc2-py3-none-any.whl (14 kB)
  Using cached grpcio_status-1.63.0rc1-py3-none-any.whl (14 kB)
Building wheels for collected packages: faiss-cpu
  Building wheel for faiss-cpu (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for faiss-cpu (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [8 lines of output]
      running bdist_wheel
      running build
      running build_py
      running build_ext
      building 'faiss._swigfaiss' extension
      swigging faiss/faiss/python/swigfaiss.i to faiss/faiss/python/swigfaiss_wrap.cpp
      swig -python -c++ -Doverride= -doxygen -Ifaiss -I/private/var/folders/q3/s2px_6w50ks2cxmcc00k3wyh0000gp/T/pip-build-env-j4tnsdqd/overlay/lib/python3.10/site-packages/numpy/core/include -Ifaiss -I/usr/local/include -o faiss/faiss/python/swigfaiss_wrap.cpp faiss/faiss/python/swigfaiss.i
      error: command 'swig' failed: No such file or directory
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for faiss-cpu
Failed to build faiss-cpu
ERROR: Could not build wheels for faiss-cpu, which is required to install pyproject.toml-based projects

[notice] A new release of pip is available: 23.0.1 -> 24.1
[notice] To update, run: pip install --upgrade pip

Screenshots
n/a
Additional context
n/a

This is the same error even if I remove the -pre from the command - python -m pip install langflow --force-reinstall -U cc/ @rodrigosnader

@msmygit You don't need --force-reinstall if you want to just use langflow.

okay. This is what fixed my issue of upgrading from the 1.0.0a61 --> 1.0.5,
python -m pip install langflow -U

Expand/Collapse
```
...
Installing collected packages: smmap, gitdb, gitpython, langchain-mongodb, langchain-aws, langflow-base, langflow
  Attempting uninstall: langflow-base
    Found existing installation: langflow-base 0.0.72
    Uninstalling langflow-base-0.0.72:
      Successfully uninstalled langflow-base-0.0.72
  Attempting uninstall: langflow
    Found existing installation: langflow 1.0.0a61
    Uninstalling langflow-1.0.0a61:
      Successfully uninstalled langflow-1.0.0a61
Successfully installed gitdb-4.0.11 gitpython-3.1.43 langchain-aws-0.1.8 langchain-mongodb-0.1.6 langflow-1.0.5 langflow-base-0.0.81 smmap-5.0.1

[notice] A new release of pip is available: 23.0.1 -> 24.1
[notice] To update, run: pip install --upgrade pip
```

Although, it screwed up my existing projects and wiped out everything 🤯 😭


Relax scipy dependency to >=0.13.3

Codecov Report

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

@@          Coverage Diff          @@
##           master   #611   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          41     41
  Lines        1997   1997
=====================================
  Hits         1997   1997

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 e1a24e7...7d59d32. Read the comment docs.


fix:Include prop for track

There was no prop to change the entire background of the bar just the section within the progress range. I have included a trackColor prop that gives the capacity to do this

@rewdt great job! Thankssss :)


Option to exclude/include files by archive type

Option currently exists to check by globs, but we check the actual file signature which may not match extension.
This would be to add a new option so you could specify for example: only extract zips, or extract everything but zips.
Options should be two lists of Archive Type Enums.

Fixed in #80


Fixup startVM on simulator

Description
If we stop and start the VM again on another host, simulator doesn't update the host id in simulator database. This PR updates the host id and other parameters which might change for a VM.

Steps to reproduce

Start a VM. (Let's say the VM started on host H1)
Stop the above VM and start it on any other host (let's say H2).
VM gets started on the specified host H2.
After some time, host for the VM changes back to H1.

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[x] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[x] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

How did you try to break this feature and the system with this change?

@blueorangutan package

@rohityadavcloud a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 9855

@vishesh92 can you check the GHA failures quickly and merge if these are easily explained?

@vishesh92 can you check the GHA failures quickly and merge if these are easily explained?

Simulator CI jobs failed due to failure in publishing results to codecov.
There was a test failure in Coverage Check / codecov (pull_request) which doesn't seem to be related to this PR. I have triggered the job again for verification.

Error:  Tests run: 33, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 10.176 s <<< FAILURE! - in org.apache.cloudstack.api.response.QuotaResponseBuilderImplTest
Error:  validateEndDateOnCreatingNewQuotaTariffTestSetValidEndDate(org.apache.cloudstack.api.response.QuotaResponseBuilderImplTest)  Time elapsed: 0.02 s  <<< ERROR!
com.cloud.exception.InvalidParameterValueException: The quota tariff's end date [Tue Jun 11 08:34:00 UTC 2024] cannot be less than now [Tue Jun 11 08:34:00 UTC 2024].
	at org.apache.cloudstack.api.response.QuotaResponseBuilderImplTest.__CLR4_4_1z0nq4d18x(QuotaResponseBuilderImplTest.java:335)
	at org.apache.cloudstack.api.response.QuotaResponseBuilderImplTest.validateEndDateOnCreatingNewQuotaTariffTestSetValidEndDate(QuotaResponseBuilderImplTest.java:331)

@DaanHoogland the above test is failing and is not related to this PR. I am creating another PR to fix the unit test failure.

@DaanHoogland Looks like updating the branch fixed the issue.


Fix/typedoc and bump

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

GitHub release
1.0.8
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


SPRAYING SEMEN ON GEOSN0W!!!

I LOVE SPRAYING SEMEN ON GEOSN0W SEMEN FEELS COOL!!! AND QUITE SLIPPERY ON ORAL SEX!!!

 I AM THE REAL DIATRUS!!!


deps: update osbuild/images to 9548bf0d0140

Update osbuild/images dependency to osbuild/images@9548bf0d0140
Relevant PRs:

https://github.com/osbuild/images/pull/43
https://github.com/osbuild/images/pull/91

@henrywang It's now possible to specify parent ostree commits using the commit ID, like we could before we introduced changing refs. (see https://github.com/osbuild/osbuild-composer/issues/3107).
Can we add a test case for this to one of the ostree tests?  Building a child commit from a parent, but specify the parent using the commit ID instead of the ref.

@achilleas-k Questions about this change:

Does --parent <parent ref> still work? If not, the rebase upgrade, like upgrade from rhel 8 to rhel 9 will not work.
Commit ID is used as vaule of --parent. Which ref will be used if there're two or more refs in ostree repo?
If we have issue on 1 or 2, we should add one more arg --commit

@achilleas-k Questions about this change:

Does --parent <parent ref> still work? If not, the rebase upgrade, like upgrade from rhel 8 to rhel 9 will not work.

Yes, it still works.

Commit ID is used as vaule of --parent. Which ref will be used if there're two or more refs in ostree repo?

The ref for the new (child) commit will be the --ref argument or the default for the distribution of it's not specified.  For pulling the parent, the ref doesn't matter.  It just pulls the commit with the given ID from the repo.

If we have issue on 1 or 2, we should add one more arg --commit

There shouldn't be any issues.

Looking good.  Failures are
An error occurred (VpcLimitExceeded) when calling the CreateVpc operation: The maximum number of VPCs has been reached.

Marking PR as ready.

@achilleas-k Yes, it's not caused by this PR.

@achilleas-k All green now.


Feature : Starting a Component Cluster

Starting automatically a Component Cluster composed by a set a Components Classes linked by a componentName.
For example :
MolUtils startComponentsCluster: aComponentList named: aComponentName.
This method start each components classes using "aComponentName" instead of #default key and map automatticaly each of them inside the cluster.

Components are linked with the default component name without specified declaration, the component name is "#default".
The cluster connexion principles are to re-use this default settings but with another component name, for example "#cluster1". When the cluster is started all components are automaticaly linked with #cluster1 key.

Transfered to discussion #33.


Illegal zeroing of all coin inputs on 04/04/2024 under the guise "RentalWithdraw".

https://mexc.com/support/articles/17827791514312

This is dishonest behavior by the development team towards the owners of BHD coins (BHD1). I honestly purchased these 30,500 coins for money on the MEXC exchange and now I am left with nothing.
My BHD/BHD1/DePC cold wallet address: 3K6snLLu8N16vJLNYuScYXptKKNGqN6bmo
Link#1 https://depinc.dwd.com/explorer/tx/19f5a743241e17d54f702957824308ed843799e67d89fd28293588107876dc08
Link#2 https://depinc.dwd.com/explorer/tx/87eb9f91f1d1ed2eed3661c04b6df13460b0f4a16c6a74b2f56d0417fd52de2e
Link#3 https://depinc.dwd.com/explorer/tx/2f348ae49dce0bb6cfff6c9946dab6204505c0e04079dbc49a002f18f0ac8327
Link#4 https://depinc.dwd.com/explorer/tx/e669982c868ca4586a80e8966f563f953f0c9150b75278252f05817f174eae3f
Link#5 https://depinc.dwd.com/explorer/tx/6c7e324c794f09489d9e22108b5f5bbf0a3fb0d42f93c9a834406042ee5e0f87
Link#6 https://depinc.dwd.com/explorer/tx/648854e896f81fb9984dd5fa8d081d3995f9a1c0f836f84d4ad7ed48c1843076
Link#7 https://depinc.dwd.com/explorer/tx/820dd1438d8431c7f256581b728f06ce383dd87a4dafdbe924411b25cae7c8a2
Link#8 https://depinc.dwd.com/explorer/tx/e583888a40b5a8e5c8b832800bd71ebd1055b9ccf1fba3bab60f4b3cf7a213b8
Link#9 https://depinc.dwd.com/explorer/tx/66077e2a2cc515c792ecfac146226d75096dc83a0a5a3544ec0e10aebc7f2ccc
Link#10 https://depinc.dwd.com/explorer/tx/494fd0c0a40cc11fe16dd57b9881cbc55f2ef82a366f97ec38fa2f3577aaffe0
All coins were sent to the same address: https://depinc.dwd.com/blocksaddress/34tofduRS3aSeqQM8Hy2hzq7xcSbGSbFiL
The BHD network is working properly and you can send and receive coins, but the block explorer does not work because no one pays for hosting.
BHD1 network was forcibly stopped by the developers, the new DePC team
The BHD coins that I bought on the MEXC exchange are not accepted for exchange for DePC, which can be considered illegal collusion with the DePC team.
In this situation, the MEXC exchange must be deprived of its license for listing an unscrupulous DePC asset in violation of the rebranding rules announced by the DePC team.
I really hope that a new team will emerge that will rebrand the BHD coins with honesty and integrity, and the DePC team will be fined or receive jail time for such a coin scam.
P.S. I want to remind everyone that It was not AIRDROP it was REBRANDING and in such a situation this behavior is called fraud and nothing else. In addition, the BHD1 team, after the first rebranding, increased the issue of coins from 21 to 63 million pieces and received a premine, which they successfully sold on the MEXC exchange, but this was not enough for them and they decided to burn coins in the wallets owners and reduce competition on the exchange after this move DePC team wants inflate the price and sell coins premine again.

All my coins were also stolen 04/04/2024
were purchased when the price of the parent coin was 20 bucks.. and then mined into a dual with Signa..
as a result, now instead of 16,747 coins --> zero
new owners STOLEN!

I want to understand one thing: if by the power of "fork", the old BHD (even BHD1) project is still available, even the binaries, could some one with credits in the account turn the wallet on with a minimum solo miner to keep the network alive and invite the other affected folks to join the network? I believe the coins won't longer be worth the original price, but now we have 0. Then explain to the exchanges what happened to see if the old BHD / BHD1 can be listed again. The explorer is not really necessary since what matters is the database of the wallet. Is this feasible?

I want to understand ... Is this feasible?

At this point in time, the BHD network is working very well, just download the BHD Core wallet from this link https://disk.yandex.ru/d/LDnTICTSsYH3fg
In order for the BHD coin to be placed on some exchange, you need to have an explorer, for example this one https://dwd.com/
There were just over 6 million BHD in circulation of the 21 million BHD coins, but some of the coins were exchanged as a result of dishonest rebranding for the new DePC coins.
The BHD1 network has been forced stopped by DePC team and is under him control.
Here are some videos that were popular when the BHD network started.
http://youtube.com/watch?v=FHh5lAx5o3Q
http://youtube.com/watch?v=d916SBET-nE
http://youtube.com/watch?v=V0yrmSQAaWQ
http://youtube.com/watch?v=n2Mtf8C9784
http://youtube.com/watch?v=qCLouoX2-tI
http://youtube.com/watch?v=Yvm2nmCD6Wg
http://youtube.com/watch?v=x-FmgH1UqCM
http://youtube.com/watch?v=YuieWJhA_yI
http://youtube.com/watch?v=DYyKRoQ1gNA
I wrote a letter to CHIA Network to all 3 mailing addresses that are on their website asking for help and to rebrand the BHD-->CHIA coin honestly, with the hope that Bram Cohen will not ignore his younger brothers.
I don’t know if he will read my letter, but what is happening now is a real nightmare and lawlessness on the part of the MEXC exchange, which is probably in collusion with the DePC team, which carried out a dishonest rebranding.

ok! I've installed back the BHD wallet and it'll be running the whole day to try to sync and download the full database. Let's see later how to put a solo miner to provide network support

ok! I've installed back the BHD wallet and it'll be running the whole day to try to sync and download the full database. Let's see later how to put a solo miner to provide network support

You can also download the mining guide and software, as well as the BHD white paper
https://disk.yandex.ru/d/Eu8v6NgWVAuQiQ
If you manage to start the solo mining process, please post instructions about it. Thanks!

After the synchronization was over, I managed to change the "point to" to my own address for solo mining because I still have some BHD in my account. It takes 0.2 BHD to do the operation, and I've configured scavenger to point to the IP and port of my BHD wallet, but the communications protocol of the wallet seems to not be the same than with Burstcoin. So I'm looking for information about how a solo miner for BHD should communicate with the wallet. When the Foxy pool was around, it was straight forward because the pool was offering a web API similar to Burstcoin but the actual mining was being done for your BHD account.
https://www.reddit.com/r/bhdcoin/comments/ck45gn/four_steps_of_mining_bhd/

https://chainz.cryptoid.info/bhd/
I hope that the MEXC exchange will resume the listing of BHD, since the rebranding of the coin was carried out by the DePC team in violation of the law and through a hard fork, due to which investors and owners of BHD coins were illegally harmed. It would be great if someone would help draw attention to the BHD coin and the listing of BHD coins would be on other exchanges.

To everyone who has suffered from the joint illegal actions of the MEXC exchange and the DePC team, please leave your answers and messages here: https://bitcointalk.org/index.php?topic=5497719.0


Adding Platzi to ADOPTERS.md

Adding Platzi as adopter
Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

@yorjaggy can you check out the comment about DCO signing the commit for this PR? :pray:

@benjdlambert sure, closing this PR since new PR was created to address the comments


Flutter InAppWebView how to disable cross origin policy?

hello everyone
I'm using InAppWebView to make a video downloader app by listening to onLoadResource even and grab the video played by the user and ofc the video inside an iframe and because of cross origin policy i can't get the url inside iframe (.mp4,.m3u8......), i did set allowUniversalAccessFromFileURLs and allowFileAccessFromFileURLs to true but no result i can't get the resources the iframe called :/, this is my initialoptions :
initialOptions: InAppWebViewGroupOptions(
android: AndroidInAppWebViewOptions(
supportMultipleWindows: true,
offscreenPreRaster: true,
allowUniversalAccessFromFileURLs: true,
allowFileAccessFromFileURLs: true,
),
crossPlatform: InAppWebViewOptions(
useOnLoadResource: true,
debuggingEnabled: true,
userAgent:
"Mozilla/5.0 (Linux; Android 9; Redmi Note 8) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.125 Mobile Safari/537.36",
javaScriptEnabled: true,
javaScriptCanOpenWindowsAutomatically: true,
)),
if anyone very familiar with inappwebview or flutter would tell me how to disable the cross origin policy in flutter or how to listen to my app http requests without using a proxy ... , i'll be grateful

It's not possible to disable the cross origin policy.
Options allowUniversalAccessFromFileURLs and allowFileAccessFromFileURLs are related to local files.
Probably, to get the resources of an iFrame on Android, you can use the androidShouldInterceptRequest event.
To use this event, the useShouldInterceptRequest android-specific option must be true.


Kinect DK SDK k4arecorder.exe Access Denied Error on Windows 10

I  just received my new Kinect DK a few days back. I have successfully installed the SDK on Ubuntu 1804, the viewer/recorder seem to work great so far. But, on W10, I cannot seem to get around the following error:
C:\temp>"C:\Program Files\Azure Kinect SDK v1.1.0\tools\k4arecorder.exe" -l 5 output.mkv
libusb: error [winusbx_open] could not open device \.\USB#VID_045E&PID_097C#000041292112#{A5DCBF10-6530-11D2-901F-00C04FB951ED} (interface 0): [5] Access is denied.
[2019-07-04 08:39:44.111] [error] [t=11648] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\usbcommand\usbcommand.c (305): find_libusb_device(). Unable to open LIBUSB at index 0
[2019-07-04 08:39:44.114] [error] [t=11648] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\depth_mcu\depth_mcu.c (68): usb_cmd_create(USB_DEVICE_DEPTH_PROCESSOR, device_index, NULL, &depthmcu->usb_cmd) returned failure in depthmcu_create()
[2019-07-04 08:39:44.115] [error] [t=11648] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\sdk\k4a.c (129): depthmcu_create(index, &device->depthmcu) returned failure in k4a_device_open()
Runtime error: k4a_device_open() failed
Runtime error: k4a_device_get_serialnum(device, serial_number_buffer, &serial_number_buffer_size) returned 1
On Ubuntu, running in su seems to remedy this, but for W10, I am running the CMD window in admin mode. I am unclear as to why this error is occuring. From additional research, seems USB incompatability could also be the issue. My dev preference is VS, but C in Linux is doable if this is the path I should persue. Maybe my issue is a simple fix, but if it actually is the USB, that's a problem.
Thanks

This error pattern does not match the errors I have seen resulting from USB Host controller issues. It seems more like something else is using the camera exclusively.
Please make sure you are powered with the provided power supply and the back power LED is solid white. Also please make sure you are not using any extension cable and just the provided cables.

Thanks for the response. I have only used the provided cables / power supply. Solid white has always been fine. No extension cords. The odd thing is it works as described on a NUC717 w/Ubuntu 1804. The viewer, recorder, all seems to be fine. On w10, the viewer works great (I think), it's the recorder which breaks down. I do not seen anything odd running as this Alien is brand new; it also throws the exact same exception on Surface Pro as well as Alien.

Hmm, if you had the viewer open then that might be to app using the camera exclusively. Can you confirm that viewer works or not. You might just reboot too first if you have not tried that.
The viewer and the recorder both use the same SDK code so if one works you should expect to the other to also work.

OK, not sure what happened, but both the viewer and k4arecorder.exe command
seem to work fine...
Not sure what I fat fingered. Thank you so much!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
On Mon, Jul 8, 2019 at 9:34 AM wes-b<EMAIL_ADDRESS>wrote:

Hmm, if you had the viewer open then that might be to app using the camera
exclusively. Can you confirm that viewer works or not. You might just
reboot too first if you have not tried that.
The viewer and the recorder both use the same SDK code so if one works you
should expect to the other to also work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues/465?email_source=notifications&email_token=ABDM43P7YALDZOIXLODNFETP6NUBJA5CNFSM4H64HLY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZNUSSA#issuecomment-509299016,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDM43KRYK3KWMUSQG6ZORLP6NUBJANCNFSM4H64HLYQ
.

Great!

Hmm, if you had the viewer open then that might be to app using the camera exclusively. Can you confirm that viewer works or not. You might just reboot too first if you have not tried that.
The viewer and the recorder both use the same SDK code so if one works you should expect to the other to also work.

After closing Viewer, the recorder starts working properly.

Had the same issue turned out to be just a cable issue, make sure you plug in both your cables to the correct sources ;)


called Result::unwrap() on an Err value: "Couldn't parse default value:  \r\n CREATE DEFAULT DF__N_\r\n \tAS 'N'\r\n"

Hi Prisma Team! The following command just crashed.
Command
db pull
Versions

Name
Version

Platform
windows

Node
v16.16.0

Prisma CLI
4.3.1

Engine
c875e43600dfe042452e0b868f7a48b817b9640b

Error
Error: [libs\sql-schema-describer\src\mssql.rs:317:30] called `Result::unwrap()` on an `Err` value: "Couldn't parse default value: ` \r\n CREATE DEFAULT DF__N_\r\n \tAS 'N'\r\n`"

Hi, can you please share your schema.prisma file and SQL dump with us? Thank you.
Moreover, which SQL Server version are you currently using exactly?

Hi,
I only changed the provider of the datasource block in schema.prisma to sqlserver according to the "Next steps" that appeared when I ran npx prisma init.
`
generator client {
provider = "prisma-client-js"
}
datasource db {
provider = "sqlserver"
url      = env("DATABASE_URL")
}
`
Then I ran prisma db pull to turn my database schema into a Prisma schema according to #3 of the "Next steps", then the error occurred, so I don't have the SQL dump.
I'm using Microsoft SQL Server Standard (64-bit) v12 in Microsoft Windows NT 6.3.
For your reference, below is the "Next steps" that I'm referring to:

Set the DATABASE_URL in the .env file to point to your existing database. If your database has no tables yet, read https://pris.ly/d/getting-started
Set the provider of the datasource block in schema.prisma to match your database: postgresql, mysql, sqlite, sqlserver, mongodb or cockroachdb.
Run prisma db pull to turn your database schema into a Prisma schema.
Run prisma generate to generate the Prisma Client. You can then start querying your database.

SQL Server v12 is the same as 2012. Unfortunately we have no ways of testing with this version, especially due to the missing docker images, meaning we cannot test against that version on CI.
Therefore we officially support SQL Server versions 2017 and 2019 only, because those have docker images available and we can guarantee them working with our CI.

Thank you for your support. I guess I can't use prisma with SQL Server 2012 🥲
The database was created by other developers, so, I wish I knew. lol
Thanks!


[4.x] Complete incomplete and missing tests

This PR completes the missing/skipping tests. Now there is only one skipping test related to the Debuggable feature. As discussed internally, this feature is still incomplete, so I left the test as it is.

Codecov Report

Merging #947 (6d90312) into master (abd17f8) will decrease coverage by 0.15%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #947      +/-   ##
============================================
- Coverage     87.34%   87.19%   -0.16%
- Complexity      408      410       +2
============================================
  Files           112      112
  Lines          1130     1132       +2
============================================
  Hits            987      987
- Misses          143      145       +2

Impacted Files
Coverage Δ

...e/TenantDatabaseManagers/SQLiteDatabaseManager.php
73.33% <100.00%> (-11.29%)
:arrow_down:

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

The ternary I told you to convert to a proper if check — don't overcomplicate it. You're using str() just to join strings and then you have to call ->toString() at the end. That just adds complexity.
Also, the comments aren't needed.
All you need to do there is just change the ternary into an if () and the code will be perfect.


Dev

@hootlex Could you make a new release from develop ? It's better.

@nahid This is duplicate with https://github.com/hootlex/laravel-friendships/pull/45

@hootlex Maybe he thought that it will directly merge on master. It's why he makes new PR.

@stephane-monnot Now that I see it again, I can't understand this .
The concept isn't to check if the recipient has a pending friend request? Is it the opposite?

@hootlex Yes, opposite. I didn't check the discussion. We already had hasFriendRequestFrom. The concept is "have Already Sent A Friend Request To".

@stephane-monnot oh, I was totally confused and talking about the wrong method the whole time!!
Why u didn't say anything on my suggestion? :P
@nahid sorry man, what about naming the method hasSentFriendRequest?

@hootlex Didn't see it :stuck_out_tongue_winking_eye: . hasSentFriendRequest or hasSentFriendRequestTo ?

hasSentFriendRequestTo :punch:

yes it will be hasSentFriendRequestTo

@hootlex /!\ the branch dev has already been merged with #45. Maybe git cherry-pick to get only 2 last commits on dev branch and after reviewing, merge dev with master ?

Thank you :)

@nahid :smiley:


Adding swagger updates to support the new NRP resource "DSCP Configuration"

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[x] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.

adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

@davelasc Could you fix CI errors according to the instruction and error mesages?

/azp run automation - sdk

/azp run automation - sdk

@MyronFanQiu having issues understanding why the readme is throwing the duplicate exception. Trying to add the directive to suppress warnings about the missing name, id and type properties since they will be inherited. By any chance you know why this is cause or know someone that I can talk to about this.
Right now that change has been removed to (hopefully) have fixed all other issues

@davelasc I checked the error message and I think they gave enough instructions. Each CI error implies that something wrong in your swagger spec like example, conflict or network validation. Usually we cannot suppress these CI errors. If you have specific question for some of them, please let me know and I can invite corresponding authors.

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

@MyronFanQiu been able to fix most of the issues, some are still confusing me. The number one is regarding the readme file. Why is it saying that it is duplicated? Need that entry to fix the error of the id, name and type are not being define in the dscpConfiguration.json. Those 3 are inherited from the resource.json.

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

@MikhailTryakhov @number213 @MyronFanQiu @v-shhatt just a friendly reminder to review the PR. Hopefully it can get approved :D

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk


Added release candidate for OSDM 2.0.0-RC01

@tls-sbb The commited YAML file contains unrelated HTML. Please review it.

@tls-sbb The commited YAML file contains unrelated HTML. Please review it.
Thanks for checking it. My fault. Something went wrong on upload. Now its fixed.

Ciao @jspetrakhttps://github.com/jspetrak
What do you mean with unrelated HTML?
Von: Josef Petrák @.>
Gesendet: Mittwoch, 28. September 2022 20:58
An: UnionInternationalCheminsdeFer/OSDM @.>
Cc: Schall Tillmann (IT-PTR-CEN2-SME1 - Extern) @.>; Mention @.>
Betreff: Re: [UnionInternationalCheminsdeFer/OSDM] Added release candidate for OSDM 2.0.0-RC01 (PR #308)
@tls-sbbhttps://github.com/tls-sbb The commited YAML file contains unrelated HTML. Please review it.
—
Reply to this email directly, view it on GitHubhttps://github.com/UnionInternationalCheminsdeFer/OSDM/pull/308#issuecomment-1261339610, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXZ3ULSREWSUOTD6BXAMW73WASIMTANCNFSM6AAAAAAQX6FAX4.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@tls-sbb Hello, you have already resolved the issue with the commit "Fixed invalid file content".

Yes, issue is fixed since a long time ;-)


Tracking daily tasks

Oh no my friend, I'll miss you for the next few weeks. Please be safe and stay healthy, I'll be here waiting for you!

So now you have to text me to remind me that i have to check the PR🥹🥹🥹


Connecting time between tag and anchor

I am using dw1000 module outdoor. I am a moving tag and I am approaching to the anchors. But the connecting time is too slow. How can i connect tag and anchor faster? Can i regulate the time in dw1000 library?

Wired connection
On Tue, 10 Oct 2023 at 08:22, memirerdol @.***> wrote:

I am using dw1000 module outdoor. I am a moving tag and I am approaching
to the anchors. But the connecting time is too slow. How can i connect tag
and anchor faster? Can i regulate the time in dw1000 library?
—
Reply to this email directly, view it on GitHub
https://github.com/thotro/arduino-dw1000/issues/337, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEWE7KVYFOY7BMZK37GNJ3X6TZS7AVCNFSM6AAAAAA5Z3UEJKVHI2DSMVQWIX3LMV43ASLTON2WKOZRHEZTINJYGYZTQMY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


binder/runtime.txt specifies python 2.7

@DrDrij:
We've moved to python 3 as the default, and do not want to guarantee that future content will work on both py27 and py3.  Need to:

Make sure all existing content works for py3
Update the runtime.txt to specify py3

Can you take this on?

Closed by merging pull request #23


Bump golang.org/x/net to v0.7.0 to fix CVE

@rayandas thanks for making this PR, would it be also possible to:

Bump Go to 1.20 in:

https://github.com/rancher/confd/blob/release/v0.16/Dockerfile.dapper#L1
https://github.com/rancher/confd/blob/release/v0.16/go.mod#L3

Bump github.com/aws/aws-sdk-go to v1.34.0 in https://github.com/rancher/confd/blob/release/v0.16/go.mod#L12 as the current version has at least 03 medium severity issues?

Thanks!

@macedogm Updated the PR


libdocker.GenerateMountBindings(): Disable RRO mounts when bumping up the Docker API client package to v25 (API v1.44)

https://github.com/Mirantis/cri-dockerd/blob/8ae7a0ee2a81ec928aee8a276ffe6ba0ec6125ba/libdocker/helpers.go#L205-L261
Docker v25 (API v1.44) treats read-only mounts as recursively read-only by default: https://github.com/moby/moby/pull/45278#issuecomment-1499557245
But this appeared to be too much breaking for Kubernetes: https://github.com/kubernetes/enhancements/pull/3858#issuecomment-1925441072
So cri-dockerd has to disable RRO by setting BindOptions.ReadOnlyNonRecursive.

(This needs migrating from the legacy bind strings to the modern mount structs, but migrating "Z" isn't straightforward)

PR:

#311

Should probably have been 0.4.0, and not 0.3.12

Hindsight being what it is, probably. At the time this seemed like a pretty simple bugfix for an unintended regression caused by an unintended API change.


PRUNE_MODULES=1 does not seem to do anything

I had a previous Pi running Raspbian that ran out of disk space and had to rebuild. Since my reinstall I have been very cognizant of checking its disk space. After a couple of rpi-update's I have tried running it with the PRUNE_MODULES=1 setting but I still see old versions in /lib/modules. What files is PRUNE_MODULES=1 supposed to be removing?

See: https://github.com/Hexxeh/rpi-update/issues/197
For me it prints out:
Pruning /lib/modules/5.4.42+
Pruning /lib/modules/5.4.28-v7l+
Pruning /lib/modules/4.19.79-v8+
Pruning /lib/modules/4.19.79+
Pruning /lib/modules/4.19.23-v7+
Pruning /lib/modules/4.19.84-v7l+
Pruning /lib/modules/4.19.84-v7+
Pruning /lib/modules/4.19.57+
Pruning /lib/modules/5.5.0-rc5+
Pruning /lib/modules/5.5.0-rc5-v7l+
Pruning /lib/modules/4.19.60-v7+
Pruning /lib/modules/4.19.57-v7+
Pruning /lib/modules/4.19.1-v7+
Pruning /lib/modules/4.19.85-v8+
Pruning /lib/modules/4.19.80-v8+
Pruning /lib/modules/4.19.105-v7l+
Pruning /lib/modules/4.19.56+
Pruning /lib/modules/4.19.37-v7+
Pruning /lib/modules/4.19.64-v7l+
Pruning /lib/modules/4.19.102-v8+

It deletes any directory in /lib/modules/* whose content only include files of type *.ko or modules.* (i.e. default kernel modules)

I don't get that output or anything like that. I am using pi-hole on Raspbian. Is there something I should do to help troubleshoot?

Can you show me what you entered to run rpi-update?

What exactly are you typing to run the prune?

sudo PRUNE_MODULES=1 rpi-update

Looking at #197 helped. I deleted the /root/.firmware_revision and re-ran, which worked. Is deleting /root/.firmware_revision a requirement?

It deletes all modules before installing the new ones. It will only do this if you actually updating. Otherwise you'd be left with no modules at all.

So I performed the command incorrectly? As I said, if I run, sudo PRUNE_MODULES=1 rpi-update on an up-to-date system, nothing happens for me. Only worked after I deleted /root/.firmware_revision.

It only deletes modules when it has an update to do. If you are up to date the script does nothing.

I guess I am confused. I thought running sudo PRUNE_MODULES=1 rpi-update on an up-to-date system would remove unneeded/unused files. But you are saying I have to run, sudo PRUNE_MODULES=1 rpi-update on an out of date system in order for it to work? Is there a way to do a uname -a and delete all that do not correspond to the current running kernel? At least that way it could remove unneeded/unused files on an up-to-date system while keeping those that are currently in use.

The description of PRUNE_MODULES is "Allows you to delete unused module directories when doing an update."
You need to have an update to do for it to do anything. As you discovered you can force an update by removing  /root/.firmware_revision.
There are no plans to change the behaviour.
If you always use PRUNE_MODULES=1 in the future when running rpi-update your sdcard space will no longer fill up with old modules.

But if I use PRUNE_MODULES=1 in the future, won't that delete a possible working version of my system? When I reboot and if I deleted the modules prior to the update, I would not be able to fix it since those files would be deleted?
Initially, I wasn't sure which files were 'needed', so I guess if you do not plan to change the behavior, I will just script a way to delete the unneeded directories after comparing it to a current running 'uname -a'. Since I now know modules that do not match the uname are not needed. Thanks.

PRUNE_MODULES=1 only deletes modules before it installs new ones. When you reboot it will use the new modules that have been installed (along with the new kernel which only works with the new modules).


OpenEBench summary workflow: Remove duplicates in assessment ids

The summary workflow creates three assessments (n_matched_sites, n_unmatched_sites, correlation) but the first two have the same _id, which causes issues when adding the results to the database. The value of _id for those assessments is defined in lines 70 and 74 of compute_metrics.py:
[Line 70] data_id_1 = community + ":" + challenge + "_runtime_" + participant + "_A"
[Line 74] data_id_2 = community + ":" + challenge + "_runtime_" + participant + "_A"

If you replace "runtime" with something related to the name of the metrics (e.g. "matched" and "unmatched"), this issue would be solved. Similarly, the id of the correlation assessment could also include "correlation" instead of "memory" (see line 78):
data_id_3 = community + ":" + challenge + "_memory_" + participant + "_A"
Also, the trailing "_A"s are unnecessary and they can be dropped.

I forgot to mention that we also need the community variable to be removed from the ids because of issues downstream. If you could replace it with a hardcoded 'APAeval' that would solve the problem. This is the same approach I have suggested in issue 153.

Thanks, Asier! I have updated the code with the changes you suggested: https://github.com/yuukiiwa/APAeval-summary-workflow/commit/faf1e20860183f330a5695db5ce0654542902fad

Fantastic, thank you @yuukiiwa!

The changes had the desired effect - I'm closing the ticket. Thank you for the great work @yuukiiwa!


[BUG] App UI errors after using label selection filter

After using the label search UI to select a label to view, some App features stop working.
For example, in the state below, the checkbox to toggle the label field on and off no longer works after selecting the person label via the UI:

Resolved in 00ce78c8265ce3b810378b828b29ca44ad1cc4e4 on colab
Essentially, there was a recursion bug which froze up the window. I will say more when I have the PR up.


Custom paginating legend for c3.js charts

What does this PR do? How does it affect users?
This PR introduces a new custom paginating legend component that prevents long labels and large datasets from breaking or crashing a chart. Previously, long labels would cause the default legend supplied by c3.js to outgrow the chart view, effectively hiding the data (and looking pretty awful). Large datasets would have the same effect, and could even cause the page to crash.

Specifically, this PR does the following:

Replaces the default c3.js legend with a custom right-aligned legend, built directly with d3.js
Truncates long labels and displays a custom tooltip overlay with the complete value on hover
Correctly interacts with the chart instance when legend items are hovered and clicked (toggled)
Controls text-wrapping of c3.js's default tooltip popups w/ some new CSS work
Disables the little marker dots for each data point drawn on linear graphs, drastically reducing the number of DOM nodes that get rendered and adjusted on resize

This PR does NOT:

Manually load/unload data when paginating, however this should be introduced later, above a reasonable threshold, to prevent a crash for the largest datasets (this logic has been built in #14 and should follow in a later release)

How should this be tested?
Load up the branch, launch the demo site at http://localhost:9002/demo/, and test the following:

[ ] Does the code compile without warnings (check shell, console)?
[ ] Do all tests pass?
[ ] Does the UI, pixel by pixel, look exactly as expected (check various screen sizes, including mobile)?

Related tickets?
This PR covers #14 and also resolves #22.

Latest commit sets a smaller pagination range for donut/pie charts, and restores color mapping for those types, to reduce the visual clutter:

Moving to #39


Getting Query Parameters in Codable Router

router.get("/items") { (respondWith: ([Item]?, RequestError?) -> Void) in

}

How can I get any query parameters that came along with the request? In the last version before 2.0, I had access to the request object.
Also, It seems pretty limiting that I have to make my response be an array of Codable objects. I would like to wrap that inside another codable object. So, I'd love it to be Item? instead of [Item]? or support both ways.

I was just talking the other day about adding a single-object version of the Codable get, so look for a PR for this soon.
We are discussing the design of query parameters and path parameters with Codable routing right now and would welcome thoughts and feedback (and use cases) to help guide the design. Feel free to comment here or join us on our Slack (https://swift-at-ibm-slack.mybluemix.net/).

For the query parameters we're looking at a "type safe" implementation where you specify a struct/class of the allowable parameters (including optionals) which is pre-parsed and passed into your handler as a parameter.
We'll publish a "Kitura Evolution" proposal soon, but it would be good to get your feedback ahead of then if your happy to.

I like the idea of type safe. Can't wait to see the proposal

The PR for single object get was merged (https://github.com/IBM-Swift/Kitura/pull/1176) and went into Kitura 2.1.0

Type-safe query parameters were released in Kitura 2.2


Change timezone possible?

Hi,
I would like to change the timezone, and I tried it per volume and envireoment variable, but nothing worked for me:
docker run (.....)
--volume /etc/localtime:/etc/localtime:ro
-e "TZ=Europe/Berlin"
The "date" is always one hour behind my host.
Greetings
Steffen

I am sorry but I could not give this repo the love it deserves. 😞
So I decided to archive it and make it read only, so people can fork and apply their changes.
Thank you for taking the time to rise an issue! ❤