HDDS-2068. Make StorageContainerDatanodeProtocolService message based

Note: this change requires HDDS-2067 to be merged first.

: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 1 new or modified test files.

_ HDDS-2067 Compile Tests _

0
mvndep
67
Maven dependency ordering for branch

-1
mvninstall
30
hadoop-hdds in HDDS-2067 failed.

-1
mvninstall
24
hadoop-ozone in HDDS-2067 failed.

-1
compile
21
hadoop-hdds in HDDS-2067 failed.

-1
compile
14
hadoop-ozone in HDDS-2067 failed.

+1
checkstyle
50
HDDS-2067 passed

+1
mvnsite
0
HDDS-2067 passed

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

-1
javadoc
20
hadoop-hdds in HDDS-2067 failed.

-1
javadoc
20
hadoop-ozone in HDDS-2067 failed.

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

-1
findbugs
32
hadoop-hdds in HDDS-2067 failed.

-1
findbugs
19
hadoop-ozone in HDDS-2067 failed.

_ Patch Compile Tests _

0
mvndep
29
Maven dependency ordering for patch

-1
mvninstall
35
hadoop-hdds in the patch failed.

-1
mvninstall
28
hadoop-ozone in the patch failed.

-1
compile
23
hadoop-hdds in the patch failed.

-1
compile
20
hadoop-ozone in the patch failed.

-1
cc
23
hadoop-hdds in the patch failed.

-1
cc
20
hadoop-ozone in the patch failed.

-1
javac
23
hadoop-hdds in the patch failed.

-1
javac
20
hadoop-ozone in the patch failed.

+1
checkstyle
58
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

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

-1
javadoc
22
hadoop-hdds in the patch failed.

-1
javadoc
20
hadoop-ozone in the patch failed.

-1
findbugs
31
hadoop-hdds in the patch failed.

-1
findbugs
20
hadoop-ozone in the patch failed.

_ Other Tests _

-1
unit
28
hadoop-hdds in the patch failed.

-1
unit
24
hadoop-ozone in the patch failed.

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

2409

Subsystem
Report/Notes

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

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

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

uname
Linux 18fc7662a6f6 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
HDDS-2067 / 7256c69

Default Java
1.8.0_222

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/branch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/branch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/branch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/branch-compile-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/branch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/branch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/branch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/branch-findbugs-hadoop-ozone.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/patch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/patch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/patch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/patch-compile-hadoop-ozone.txt

cc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/patch-compile-hadoop-hdds.txt

cc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/patch-compile-hadoop-ozone.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/patch-compile-hadoop-hdds.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/patch-compile-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/patch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/patch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/patch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/patch-findbugs-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/patch-unit-hadoop-hdds.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/artifact/out/patch-unit-hadoop-ozone.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/testReport/

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

modules
C: hadoop-hdds/container-service hadoop-hdds/server-scm hadoop-ozone/insight U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/1/console

versions
git=2.7.4 maven=3.3.9

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
41
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 1 new or modified test files.

_ HDDS-2067 Compile Tests _

0
mvndep
48
Maven dependency ordering for branch

-1
mvninstall
31
hadoop-hdds in HDDS-2067 failed.

-1
mvninstall
24
hadoop-ozone in HDDS-2067 failed.

-1
compile
21
hadoop-hdds in HDDS-2067 failed.

-1
compile
14
hadoop-ozone in HDDS-2067 failed.

+1
checkstyle
50
HDDS-2067 passed

+1
mvnsite
0
HDDS-2067 passed

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

-1
javadoc
23
hadoop-hdds in HDDS-2067 failed.

-1
javadoc
20
hadoop-ozone in HDDS-2067 failed.

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

-1
findbugs
34
hadoop-hdds in HDDS-2067 failed.

-1
findbugs
21
hadoop-ozone in HDDS-2067 failed.

_ Patch Compile Tests _

0
mvndep
31
Maven dependency ordering for patch

-1
mvninstall
36
hadoop-hdds in the patch failed.

-1
mvninstall
31
hadoop-ozone in the patch failed.

-1
compile
23
hadoop-hdds in the patch failed.

-1
compile
18
hadoop-ozone in the patch failed.

-1
cc
23
hadoop-hdds in the patch failed.

-1
cc
18
hadoop-ozone in the patch failed.

-1
javac
23
hadoop-hdds in the patch failed.

-1
javac
18
hadoop-ozone in the patch failed.

+1
checkstyle
58
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

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

-1
javadoc
20
hadoop-hdds in the patch failed.

-1
javadoc
20
hadoop-ozone in the patch failed.

-1
findbugs
29
hadoop-hdds in the patch failed.

-1
findbugs
20
hadoop-ozone in the patch failed.

_ Other Tests _

-1
unit
27
hadoop-hdds in the patch failed.

-1
unit
24
hadoop-ozone in the patch failed.

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

2355

Subsystem
Report/Notes

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

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

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

uname
Linux 038d92767dd8 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
HDDS-2067 / e4d4fca

Default Java
1.8.0_222

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/branch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/branch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/branch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/branch-compile-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/branch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/branch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/branch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/branch-findbugs-hadoop-ozone.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/patch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/patch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/patch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/patch-compile-hadoop-ozone.txt

cc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/patch-compile-hadoop-hdds.txt

cc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/patch-compile-hadoop-ozone.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/patch-compile-hadoop-hdds.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/patch-compile-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/patch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/patch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/patch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/patch-findbugs-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/patch-unit-hadoop-hdds.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/2/artifact/out/patch-unit-hadoop-ozone.txt

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

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

modules
C: hadoop-hdds/container-service hadoop-hdds/server-scm hadoop-ozone/insight U: .

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

versions
git=2.7.4 maven=3.3.9

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
3545
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 1 new or modified test files.

_ HDDS-2067 Compile Tests _

0
mvndep
66
Maven dependency ordering for branch

-1
mvninstall
30
hadoop-hdds in HDDS-2067 failed.

-1
mvninstall
29
hadoop-ozone in HDDS-2067 failed.

-1
compile
20
hadoop-hdds in HDDS-2067 failed.

-1
compile
15
hadoop-ozone in HDDS-2067 failed.

+1
checkstyle
60
HDDS-2067 passed

+1
mvnsite
0
HDDS-2067 passed

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

-1
javadoc
22
hadoop-hdds in HDDS-2067 failed.

-1
javadoc
19
hadoop-ozone in HDDS-2067 failed.

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

-1
findbugs
31
hadoop-hdds in HDDS-2067 failed.

-1
findbugs
20
hadoop-ozone in HDDS-2067 failed.

_ Patch Compile Tests _

0
mvndep
30
Maven dependency ordering for patch

-1
mvninstall
35
hadoop-hdds in the patch failed.

-1
mvninstall
28
hadoop-ozone in the patch failed.

-1
compile
25
hadoop-hdds in the patch failed.

-1
compile
19
hadoop-ozone in the patch failed.

-1
cc
25
hadoop-hdds in the patch failed.

-1
cc
19
hadoop-ozone in the patch failed.

-1
javac
25
hadoop-hdds in the patch failed.

-1
javac
19
hadoop-ozone in the patch failed.

+1
checkstyle
57
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

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

-1
javadoc
21
hadoop-hdds in the patch failed.

-1
javadoc
20
hadoop-ozone in the patch failed.

-1
findbugs
31
hadoop-hdds in the patch failed.

-1
findbugs
20
hadoop-ozone in the patch failed.

_ Other Tests _

-1
unit
28
hadoop-hdds in the patch failed.

-1
unit
23
hadoop-ozone in the patch failed.

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

5921

Subsystem
Report/Notes

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

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

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

uname
Linux ffc7647b56ef 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
HDDS-2067 / 63c730a

Default Java
1.8.0_222

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/branch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/branch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/branch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/branch-compile-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/branch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/branch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/branch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/branch-findbugs-hadoop-ozone.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/patch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/patch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/patch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/patch-compile-hadoop-ozone.txt

cc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/patch-compile-hadoop-hdds.txt

cc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/patch-compile-hadoop-ozone.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/patch-compile-hadoop-hdds.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/patch-compile-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/patch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/patch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/patch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/patch-findbugs-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/patch-unit-hadoop-hdds.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/3/artifact/out/patch-unit-hadoop-ozone.txt

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

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

modules
C: hadoop-hdds/container-service hadoop-hdds/server-scm hadoop-ozone/insight U: .

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

versions
git=2.7.4 maven=3.3.9

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

_ trunk Compile Tests _

0
mvndep
65
Maven dependency ordering for branch

-1
mvninstall
30
hadoop-hdds in trunk failed.

-1
mvninstall
29
hadoop-ozone in trunk failed.

-1
compile
20
hadoop-hdds in trunk failed.

-1
compile
16
hadoop-ozone in trunk failed.

+1
checkstyle
60
trunk passed

+1
mvnsite
0
trunk passed

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

-1
javadoc
22
hadoop-hdds in trunk failed.

-1
javadoc
19
hadoop-ozone in trunk failed.

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

-1
findbugs
32
hadoop-hdds in trunk failed.

-1
findbugs
20
hadoop-ozone in trunk failed.

_ Patch Compile Tests _

0
mvndep
30
Maven dependency ordering for patch

-1
mvninstall
35
hadoop-hdds in the patch failed.

-1
mvninstall
29
hadoop-ozone in the patch failed.

-1
compile
25
hadoop-hdds in the patch failed.

-1
compile
19
hadoop-ozone in the patch failed.

-1
cc
25
hadoop-hdds in the patch failed.

-1
cc
19
hadoop-ozone in the patch failed.

-1
javac
25
hadoop-hdds in the patch failed.

-1
javac
19
hadoop-ozone in the patch failed.

+1
checkstyle
56
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

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

-1
javadoc
22
hadoop-hdds in the patch failed.

-1
javadoc
20
hadoop-ozone in the patch failed.

-1
findbugs
31
hadoop-hdds in the patch failed.

-1
findbugs
20
hadoop-ozone in the patch failed.

_ Other Tests _

-1
unit
28
hadoop-hdds in the patch failed.

-1
unit
24
hadoop-ozone in the patch failed.

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

2420

Subsystem
Report/Notes

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

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

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

uname
Linux e4c58fbbfa51 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 / 1a2a352

Default Java
1.8.0_222

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/branch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/branch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/branch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/branch-compile-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/branch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/branch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/branch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/branch-findbugs-hadoop-ozone.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/patch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/patch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/patch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/patch-compile-hadoop-ozone.txt

cc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/patch-compile-hadoop-hdds.txt

cc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/patch-compile-hadoop-ozone.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/patch-compile-hadoop-hdds.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/patch-compile-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/patch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/patch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/patch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/patch-findbugs-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/patch-unit-hadoop-hdds.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/4/artifact/out/patch-unit-hadoop-ozone.txt

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

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

modules
C: hadoop-hdds/container-service hadoop-hdds/server-scm hadoop-ozone/insight U: .

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

versions
git=2.7.4 maven=3.3.9

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
35
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 1 new or modified test files.

_ trunk Compile Tests _

0
mvndep
59
Maven dependency ordering for branch

-1
mvninstall
29
hadoop-hdds in trunk failed.

-1
mvninstall
30
hadoop-ozone in trunk failed.

-1
compile
18
hadoop-hdds in trunk failed.

-1
compile
12
hadoop-ozone in trunk failed.

+1
checkstyle
56
trunk passed

+1
mvnsite
0
trunk passed

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

-1
javadoc
20
hadoop-hdds in trunk failed.

-1
javadoc
16
hadoop-ozone in trunk failed.

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

-1
findbugs
33
hadoop-hdds in trunk failed.

-1
findbugs
16
hadoop-ozone in trunk failed.

_ Patch Compile Tests _

0
mvndep
25
Maven dependency ordering for patch

-1
mvninstall
31
hadoop-hdds in the patch failed.

-1
mvninstall
25
hadoop-ozone in the patch failed.

-1
compile
21
hadoop-hdds in the patch failed.

-1
compile
14
hadoop-ozone in the patch failed.

-1
cc
21
hadoop-hdds in the patch failed.

-1
cc
14
hadoop-ozone in the patch failed.

-1
javac
21
hadoop-hdds in the patch failed.

-1
javac
14
hadoop-ozone in the patch failed.

+1
checkstyle
51
the patch passed

+1
mvnsite
0
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

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

-1
javadoc
19
hadoop-hdds in the patch failed.

-1
javadoc
18
hadoop-ozone in the patch failed.

-1
findbugs
32
hadoop-hdds in the patch failed.

-1
findbugs
18
hadoop-ozone in the patch failed.

_ Other Tests _

-1
unit
25
hadoop-hdds in the patch failed.

-1
unit
22
hadoop-ozone in the patch failed.

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

2483

Subsystem
Report/Notes

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

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

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

uname
Linux 67ae69447d23 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 8a9ede5

Default Java
1.8.0_222

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/branch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/branch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/branch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/branch-compile-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/branch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/branch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/branch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/branch-findbugs-hadoop-ozone.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/patch-mvninstall-hadoop-hdds.txt

mvninstall
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/patch-mvninstall-hadoop-ozone.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/patch-compile-hadoop-hdds.txt

compile
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/patch-compile-hadoop-ozone.txt

cc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/patch-compile-hadoop-hdds.txt

cc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/patch-compile-hadoop-ozone.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/patch-compile-hadoop-hdds.txt

javac
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/patch-compile-hadoop-ozone.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/patch-javadoc-hadoop-hdds.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/patch-javadoc-hadoop-ozone.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/patch-findbugs-hadoop-hdds.txt

findbugs
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/patch-findbugs-hadoop-ozone.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/patch-unit-hadoop-hdds.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-1504/5/artifact/out/patch-unit-hadoop-ozone.txt

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

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

modules
C: hadoop-hdds/container-service hadoop-hdds/server-scm hadoop-ozone/insight U: .

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

versions
git=2.7.4 maven=3.3.9

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

This message was automatically generated.

/retest

@arp7  Thanks for the review. I have verified this patch on my machine and committed this patch to the trunk. @elek  Thank you for the contribution.


Fix index page card styling and dark mode also

Description

Fix index page styling and dark mode visibility also. I eliminate the Show  more buttons  which is not necessary after make the whole card clickable.
Shift the Love icon in right side of the card for better space allignment.
I also remove the tags that shown in the index page, Which ruin the card style and make it different height. And also the Airbnb type big website has not shown the tags in index page. Though this was good in individual show page. For change this, it's force user to visit the individual show page, this is also an  UX logic.
This changes make all the card good looking

Related Issues
Link any related issues using the format Fixes #issue_number.
This helps to automatically close related issues when the PR is merged.

Placeholder: "Fixes #483  "

Screenshots (if applicable)
Add any screenshots that help explain or visualize the changes.

Checklist
Make sure to check off all the items before submitting. Mark with [x] if done.

[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] I am working on this issue under GSSOC

@Soujanya2004   Marge it. And don't forget to add all the labels as per ISSUE #483

@Soujanya2004  i would like to add same style for search results card and the top list card in the ISSUE #549


form not attached to controller when using controllerAs/bindToController

Hi,
I have a directive with { controllerAs: "vm", bindToController: true } defined. When using a <form name="thisForm"> inside the directive template, the vm.thisForm is undefined inside the controller. $scope.thisForm is working fine (if I inject $scope, obviously). Is this working as intended? Couldn't find any documentation on this.

This is working as expected, see https://code.angularjs.org/snapshot/docs/api/ng/directive/form


Master to Live

Docs Build status updates of commit 325b2fd:
:clock10: Full build: the average full build time is 14 min(s) 15 sec(s), this is based on the last 227 build(s) for this repository.

Docs Build status updates of commit 325b2fd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/mailboxes/Get-CalendarDiagnosticLog.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mailboxes/Get-CalendarDiagnosticObjects.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mailboxes/Get-RecoverableItems.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mailboxes/Restore-RecoverableItems.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/server-health-and-performance/New-ThrottlingPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

sharepoint/docs-conceptual/overview.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Add-SPOHubSiteAssociation.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Enable-SPOCommSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-server/Get-SPExcelBIServer.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-server/New-FASTSearchMetadataFullTextIndex.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-server/Remove-FASTSearchMetadataCategory.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-server/Set-FASTSearchMetadataFullTextIndexMapping.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Added responseJSON property to JQueryXHR object

I'm pretty certain this is the correct place to put the property. This available in functions like success, error, complete.

For those following along at home, it looks like this change to add responseJSON was ultimately made.  See Issue #2324

@stephenmcd1 Thanks.
I was using xhr['responseJSON'] for a work around.
Glad this finally got merged. :camel:


Update README.md to link to rtx page

Found it somewhat confusing on how rtx got renamed to mise and what the migration path is.  https://mise.jdx.dev/rtx.html page answers a lot of my questions.  Might be helpful for others as well.

yeah I've done the same on the docs page so this makes sense


Handle complex file names in rose_listen

Pointed out in #18
Currently, rose_listen.py assumes the file names for currently playing episode to be simple.
Need to extend to cover atleast the following cases:

Doctor.Who.S05e12.extraneoustext.mkv
Attack On Titan - S03E01 - Smoke Signal (720p) (x265) (E-Subs) [Baba_Bhayanak].mkv
Bojack Horseman - S01E01 [WEBRip 720p] [Daiki_Aomine].mkv
Brooklyn.Nine-Nine.S01E01.1080p.WEB-DL.DD5.1.H.264-NTb.mkv

Assigning this issue to @agarwalrounak

Closed with #28.


A small set of fixes and updates

Hi, thanks for this library! It looks really useful.
Here are a number of small fixes. Each is a separate commit. If you prefer, I can break each one out into its own PR.

Thanks!


enhancement increasing the max_write_buffer_number parameter to improve save meta performance

Proposed changes
Issue Number: close #xxx

I0627 17:05:46.669010 339643 olap_meta.cpp:71] [Rocksdb] [WARN] [db/column_family.cc:738] [meta] Stopping writes because we have 2 immutable memtables (waiting for flush), max_write_buffer_number is set to 2
increasing the max_write_buffer_number parameter of rocksdb to improve save meta performance.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 44.51 seconds
stream load tsv:          462 seconds loaded<PHONE_NUMBER>9 Bytes, about 154 MB/s
stream load json:         21 seconds loaded<PHONE_NUMBER> Bytes, about 107 MB/s
stream load orc:          59 seconds loaded<PHONE_NUMBER> Bytes, about 17 MB/s
stream load parquet:          29 seconds loaded 861443392 Bytes, about 28 MB/s
insert into select:          70.1 seconds inserted 10000000 Rows, about 142K ops/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230628005614_clickbench_pr_169023.html


add local testing of json schema generation

Tried it. WFM

Tested it and it works

@ashetty1 thanks!

@kadel ping

if I run it locally, I get following error:
$ make test-jsonschema-generation
docker run -v `pwd`/pkg/spec/spec.go:/data/spec.go:ro,Z surajd/kedgeschema
+ curl https://raw.githubusercontent.com/kedgeproject/json-schema-generator/master/scripts/k8s-release
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100    12  100    12    0     0     12      0  0:00:01 --:--:--  0:00:01    22
+ curl -O https://raw.githubusercontent.com/kubernetes/kubernetes/release-1.7/api/openapi-spec/swagger.json
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 1776k  100 1776k    0     0    423      0  1:11:40  1:11:36  0:00:04 1023k
+ curl -O https://raw.githubusercontent.com/kedgeproject/kedge/master/pkg/spec/spec.go
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0Warning: Failed to create the file spec.go: Read-only file system
 25  7696   25  1925    0     0   1925      0  0:00:03 --:--:--  0:00:03  3493
curl: (23) Failed writing body (0 != 1925)
Makefile:125: recipe for target 'test-jsonschema-generation' failed
make: *** [test-jsonschema-generation] Error 23

using sudo in travis will work (for docker)

@surajnarwade

if I run it locally, I get following error:

for some reason curl seemed to fail in there

using sudo in travis will work (for docker)

yes added sudo in front of docker command and also added sudo: required in travis config file

Other than SemaphoreCI test failing, LGTM!


loss function parameters problem

model.compile(loss='categorical_crossentropy',
optimizer='sgd',
metrics=['accuracy'])
while using codes above, I can't set parameters of categorical_crossentropy. how can i assign a value to label_smoothing so that i can use label_smoothing to improve my model performance?

You can use the loss like this instead: keras.losses.categorical_crossentropy(label_smoothing=somevalue)
You can read more here.

I tried, not work. @am1tyadav

You can you partial from functools
from functools import partial
loss_func = partial(categorical_crossentropy, label_smoothing=somevalue)

This should work.

TypeError: binary_crossentropy() got an unexpected keyword argument 'label_smoothing'

Let me try to give a more complete example @pengpaiSH @Kantshun :
def cc_loss_w_smoothing(y_true, y_pred):
    label_smoothing = 0.1
    return keras.losses.categorical_crossentropy(y_true, y_pred, label_smoothing)

model.compile(
    loss=cc_loss_w_smoothing,
    optimizer="adam",
    metrics=["accuracy"]
)

def cc_loss_w_smoothing(y_true, y_pred):
    label_smoothing = 0.1
    return keras.losses.categorical_crossentropy(y_true, y_pred, label_smoothing=label_smoothing )

Thank you !!! I tried exactly as you suggested. It worked perfectly after I updated Keras.

The docs say binary_crossentropy supports label_smoothing but it clearly does not.

return keras.losses.binary_crossentropy(y_true, y_pred, label_smoothing=0.1)
TypeError: binary_crossentropy() got an unexpected keyword argument 'label_smoothing'

@am1tyadav your method works quite well!!  thank you very much.

@am1tyadav your method can be used to train a model, but the model can't be loaded later.

@am1tyadav i successfully trained my model with your method, then i save it. error raise when i loaded it.

That's correct @Kantshun . When using a custom loss function, you will not be able to use the keras.models.load_model function to load a full model file. Instead, you will have to save and load weights of the model. I'll extend my example from above assuming you have already trained a model:
model.save_weights("filename")

# Now we will load the weights after creating a new model instance
model = keras.models.Sequential([
  # Your model architecture etc.
])

model.load_weights("filename")

@am1tyadav your method seems not work for my case. the architecture of my network looks like picture below:

my model is not a sequentail model.
keras is not as simple as i expected.

@Kantshun You don't have to use Sequential class, you can use the Model class

@Kantshun
Moving this issue to closed status as there has been no activity, in case you still face the error please create a new issue.


misc fixes

While working on #323 I found a few issues, I had intended to just push them together but I found two more today so might as well fix separately.
Individual commit messages have better descriptions, but to recap:

the chain.create logic in iptables was never correct, we cannot skip creation of the dn chain as it's referred to in unchecked path. That only really matters with next PR as we start doing it all the time but it's also probably possible to pass an empty vec as opposed to None and trigger this today.
we were trying to delete too many chains, causing chain does not exist errors in teardown when they aren't created in setup
the logic to cleanup /run/containers/networks/aardvark-dns/<network> files was a bit broken, in particular when multiple lines belonged to a container and that was the last to shut down (which happens on dualstack network) we wouldn't correctly identify the new file as empty and didn't delete it. That caused aardvark to not shutdown when all configs are gone. This isn't really a problem normally but when playing with changing ports we need aardvark to be stopped.
the way we're handling subnets means we would only ever listen to one of the IPs configured for a container in /etc/resolv.conf.
This part is still not 100% coherent, resolv.conf content comes from ipam config whatever that is and we use gateway addresses for listening IPs here, but it's a start: at least with this aardvark listens to both ipv4 and ipv6 when both are set.

We don't actually need the distinction of gateway v4 or v6 as we just treat it as a string so I simplified that a bit as well and removed unneeded mut flags when I saw them. Hopefully that won't make a difference.

@martinetd Can you add a test for the iptables changes.

hmm I guess the checks don't currently check if we remove chains or not, I'll add that.

I had missed it, it's currently checked by this line:
    expected_rc=1 run_in_host_netns iptables -nvL NETAVARK-1D8721804F16F -t nat

So this makes sure we still remove chains that we created and I didn't break that.
The failure case this fixes is hard to test currently (I have no idea how to create a config that would consider an empty vec instead of None for port forwarding), but it'll be tested with the next PR anyway as that will no longer make a difference -- I don't think that warrants any new test.

@martinetd Can you add a test for the iptables changes.

hmm I guess the checks don't currently check if we remove chains or not, I'll add that. If I'm going to modify the test though I'd like to bring in my patch converting it from iptables -L to iptables -S (present in #323) so I won't need to do this twice -- I didn't get any comment on that, is it acceptable?

I am fine with using -S if you prefer that.
If there is no way to trigger that now I fine with merging. I just have to manually check the aardvark config changes since there is no way to test it in this CI, all dns tests are the aardvark repo (something we should fix so we can test these changes in netavark as well)


update

@NikitaGandhi ,what is the oregan africa db odc user? is it just ows-db?

@NikitaGandhi ,what is the oregan africa db odc user? is it just ows-db?

I think so. See https://docs.dev.dea.ga.gov.au/internal_services/rds_databases.html#db-secrets-to-access-africa-database


11 July 2015 - Initialize _unique_count to 1

Interestingly, only Redditors, Multireddits, and WikiPages are affected by this bug. Subreddits, Submissions and Comments were not. I'm not actually sure why.
I added the test in test_wiki_page because it doesn't really belong to any particular category, and it works well for this purpose. I could have also used the MultiReddit suite, but neither is really better.
Sorry, the commits got a little messy when I created this new branch.

Here's what you can do to fix the commits (if you're interested). Run:
git fetch origin master  # make sure you know about the latest on the praw remote
git rebase -i origin/master  # Use the editor to manipulate your commit history, save when done

If you mess up, you can always git reset --hard COMMITHASH to get to get back to any commit based on its hash.

Looks great otherwise. Feel free to merge whether or not you do the rebase.

 I'm too nervous to screw with this stuff on praw. Thanks for the advice though.

It gets easier. :)


Missing Manifest

msgpack is missing a manifest, please consider adding a v.mod file with the modules metadata
$ v install msgpack
Scanning `msgpack`...
warning: `msgpack` is missing a manifest file.
details: Help to ensure future-compatibility by adding a `v.mod` file or opening an issue at:
         `https://github.com/vlang/msgpack/issues/new?title=Missing%20Manifest&body=msgpack%20is%20missing%20a%20manifest,%20please%20consider%20adding%20a%20v.mod%20file%20with%20the%20modules%20metadata.`
Installing `msgpack`...
Installed `msgpack`.

It is now fixed:
#0 10:13:43 ᛋ asn1-x /d/programs/v❱v install msgpack
Scanning `msgpack`...
Installing `msgpack`...
Installed `msgpack` in %USERPROFILE%\.vmodules\msgpack .
#0 12:13:25 ᛋ asn1-x /d/programs/v❱


[tcgc] add xml usage

for xml support

All changed packages have been documented.

:white_check_mark: @azure-tools/typespec-client-generator-core

Show changes
@azure-tools/typespec-client-generator-core - fix ✏

have @clientName work for operation groups as well

@azure-tools/typespec-client-generator-core - feature ✏

add xml usage


Converting to Alpine

Has anyone looked into converting this to use alpine linux? It kinda gets addictive to run small containers after spending some time with it...
I even use a few of your (other) alpine based containers :+1:

I looked very quickly.
Would most likely need to unpack the deb file to get the pieces.
So should be doable though unlikely to happen soon.
Unless they release on alpine.

As plex now has there own image for docker and most likely going to be moving people over to that one.
I'm going to close this.
https://github.com/plexinc/pms-docker


dashboards: rework composer dashboard

Divides the dashboard into three sections:

SLO section with error budgets
API throughput:

success rate of compose / non-compose requests
amount of compose requests
request throughput per endpoint (success and error)

API latency:

overall request latency
slow request rate
request latency per endpoint

https://grafana.stage.devshift.net/d/image-builder-composer-sanne

Closing for #3538


QT: minimum amount calculation for "Send" warning

For further detail see: https://github.com/zathras-crypto/mastercore/issues/17#issuecomment-74415174

LGTM:

Merging...

I think for the future, we can even do a similar calculation, or approximation for other types, given that we have the 255 character limit. :)


Incorrect imports in inferno-mobx example?

It seems as though the imports in the inferno-mobx example here: https://www.npmjs.com/package/inferno-mobx are actually based on v0.8 where you'd be importing import { connect } from 'mobx-inferno' as shown in the example. However, isn't the correct import statement: import { connect } from 'inferno-mobx'?

Thanks! Copy pasta gone wrong :)


Add gift card product

Now with release of Vendr v.1.2 which includes gift card feature, it would be great to add a gift card product to demonstrate how to buy gift cards in Vendr. It could either be separate products with different amounts or a single product with amount in e.g. a dropdown similar to variants.
Some inspiration from various stores with gift card products:
https://shop.mikkeller.dk/products/gift-card
https://www.soundboks.com/dk/products/gift-card/
Maybe even the opportunity to add a basic message:
https://www.amazon.com/dp/B07P76HM3B/

We've already setup a simple example for you to test with https://try.vendr.net/products/accessories/gift-card/

Cool 👍
Not sure if you want the different amount as well as in the links? 😁

Yea, possibly. Open to a PR on this one if you/anyone has the time?

Fixed in https://github.com/vendrhub/vendr-demo-store/pull/9


Upgrade sig storage lib external provisioner

This also requires to update the minimun go version from 1.21 to 1.22.,
as sig-storage-lib-external-provisioner requires at least go 1.22.0.
Additionally, sig-storage-lib-external-provisioner now uses patch
to modify finalizers on PersistentVolumes, meaning that external
provisioners now need permission rules to patch PersistentVolumes.
The permission is already present in deploy/local-path-storage.yaml.
https://github.com/kubernetes-sigs/sig-storage-lib-external-provisioner/releases/tag/v10.0.0
https://github.com/kubernetes-sigs/sig-storage-lib-external-provisioner/releases/tag/v10.0.1
Steps executed:

Update to sig-storage-lib-external-provisioner/v10 v10.0.1
go mod tidy
go mod vendor

Fixes #179.

Tests pass locally with make && make e2e-test
--- PASS: TestPVCTestSuite (227.23s)
    --- PASS: TestPVCTestSuite/TestPodWithCustomPathPatternStorageClasses (41.71s)
    --- PASS: TestPVCTestSuite/TestPodWithHostPathVolume (20.26s)
    --- PASS: TestPVCTestSuite/TestPodWithLocalVolume (13.02s)
    --- PASS: TestPVCTestSuite/TestPodWithLocalVolumeDefault (13.28s)
    --- PASS: TestPVCTestSuite/TestPodWithNodeAffinity (13.02s)
    --- PASS: TestPVCTestSuite/TestPodWithRWOPVolume (12.93s)
    --- PASS: TestPVCTestSuite/TestPodWithSecurityContext (27.10s)
    --- PASS: TestPVCTestSuite/TestPodWithSubpath (40.10s)
PASS

Tests pass locally with make && make e2e-test
--- PASS: TestPVCTestSuite (227.23s)
    --- PASS: TestPVCTestSuite/TestPodWithCustomPathPatternStorageClasses (41.71s)
    --- PASS: TestPVCTestSuite/TestPodWithHostPathVolume (20.26s)
    --- PASS: TestPVCTestSuite/TestPodWithLocalVolume (13.02s)
    --- PASS: TestPVCTestSuite/TestPodWithLocalVolumeDefault (13.28s)
    --- PASS: TestPVCTestSuite/TestPodWithNodeAffinity (13.02s)
    --- PASS: TestPVCTestSuite/TestPodWithRWOPVolume (12.93s)
    --- PASS: TestPVCTestSuite/TestPodWithSecurityContext (27.10s)
    --- PASS: TestPVCTestSuite/TestPodWithSubpath (40.10s)
PASS

Thanks @rorosen
I'm checking why it failed in the ci runner.

Thanks!

Thanks for the contribution @rorosen.


PR2

This patch add some imprint
Self evaluation:
Build test: [ ]Passed [ ]Failed []Skipped
Run test: [ ]Passed [ ]Failed [ ]Skipped
Signed-off-by: JBROAD0706<EMAIL_ADDRESS>

:memo: Version: 1.20180820. Thank you for submitting PR #342. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://invain.mooo.com/.


test(pynanoid): simplify test suite

Summary by CodeRabbit

New Features

Introduced a comprehensive suite of unit tests for the pynanoid library, validating ID generation functionalities.

Bug Fixes

Enhanced consistency of error messages in ID generation functions.

Chores

Updated formatting of development dependencies for improved clarity.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

8 of 8 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+22.4%) to 100.0%

Totals

Change from base Build<PHONE_NUMBER>4:
22.4%

Covered Lines:
44

Relevant Lines:
44

💛  - Coveralls


Unable to run botkit server after delete a skill module file!

MacBook-Pro:botkitweb mycom$ node .
Initializing Botkit v0.6.16
info: ** Using simple storage. Saving data to /Users/mycom/BOTKIT/botkitweb/.data/db/
/Users/mycom/BOTKIT/botkitweb/skills/.DS_Store:1
(function (exports, require, module, __filename, __dirname) {
SyntaxError: Invalid or unexpected token
at Object.exports.runInThisContext (vm.js:78:16)
at Module._compile (module.js:543:28)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at /Users/mycom/BOTKIT/botkitweb/bot.js:69:3
at Array.forEach (native)
This error happen after I deleted a skill module file downloaded from Botkit Studio!
Thanks

This issue has been solved by recursively remove .DS_Store
Open up Terminal
In the command line, cd to/your/directory
Finally, in the command line, type: find . -name '.DS_Store' -type f -delete. Press enter.


Additional parameters for Bing

How can I pass additional parameters to bing lookup?
For example I want to get country code i.e. need to pass include=ciso2
Is it possible in the current version?

Is there a way to pass additional param to geocoded_by method in a model?
i.e. something like
geocoded_by :address, :include => "ciso2" do |obj, results|
.......
thanks

Not currently, though I'm open to a pull request for this functionality. For now you have to write a custom geocoding method, eg:
after_validation :geocode
def geocode
  if coords = Geocoder.coordinates(address, :params => {:include => "ciso2"})
    self.latitude, self.longitude = coords
  end
end


mmap error for most operations on debian 10

Hi,
I tried to use mig-parted on a debian 10 system with 6 A100 GPUs installed and backports kernel 5.10 (5.10.0-0.bpo.8-amd64 #1 SMP Debian 5.10.46-4~bpo10+1 (2021-08-07) x86_64 GNU/Linux) as well as kernel 4.19 and get the following error:
# nvidia-mig-parted -d assert --config-file /etc/nvidia-mig-manager/config.yaml --selected-config all-disabled
DEBU[0000] Parsing config file...
DEBU[0000] Selecting specific MIG config...
DEBU[0000] Asserting MIG mode configuration...
DEBU[0000] Walking MigConfig for (devices=all)
DEBU[0000]   GPU 0: 0x20F110DE
DEBU[0000]     Asserting MIG mode: Disabled
DEBU[0000] Error checking MIG capable: error opening bar0 MMIO resource: failed to open file for mmio: failed to mmap file: invalid argument

FATA[0000] Assertion failure: selected configuration not currently applied

# nvidia-mig-parted -d apply --config-file /etc/nvidia-mig-manager/config.yaml --selected-config all-disabled
[...]
DEBU[0001] Applying MIG mode change...

DEBU[0014] Walking MigConfig for (devices=all)
DEBU[0014]   GPU 0: 0x20F110DE
DEBU[0014] Running pre-apply-config hook
[...]
DEBU[0014] Applying MIG device configuration...
DEBU[0014] Walking MigConfig for (devices=all)
DEBU[0014]   GPU 0: 0x20F110DE
DEBU[0014] Running apply-exit hook
[....]
FATA[0015] Error checking MIG capable: error opening bar0 MMIO resource: failed to open file for mmio: failed to mmap file: invalid argument

The change for mig mode (equivalent to nvidia-smi -mig 0) works fine but the assertion always fails with this error and setting up mig instances doesn't work.
I tried to debug the mmap failure but couldn't find anything obvious.
I also used strace to how the call:
strace -e trace=%memory nvidia-mig-parted -d assert --config-file /etc/nvidia-mig-manager/vrvis.yaml --selected-config all-disabled
brk(NULL)                               = 0x1255000
mmap(NULL, 25926, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f904a11f000
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f904a11d000
mmap(NULL, 132288, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f904a0fc000
mmap(0x7f904a102000, 61440, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x6000) = 0x7f904a102000
mmap(0x7f904a111000, 24576, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x15000) = 0x7f904a111000
mmap(0x7f904a117000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1a000) = 0x7f904a117000
mmap(0x7f904a119000, 13504, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f904a119000
mmap(NULL, 16656, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f904a0f7000
mmap(0x7f904a0f8000, 4096, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1000) = 0x7f904a0f8000
mmap(0x7f904a0f9000, 4096, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x7f904a0f9000
mmap(0x7f904a0fa000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x7f904a0fa000
mmap(NULL, 1837056, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f9049f36000
mprotect(0x7f9049f58000, 1658880, PROT_NONE) = 0
mmap(0x7f9049f58000, 1343488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x22000) = 0x7f9049f58000
mmap(0x7f904a0a0000, 311296, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x16a000) = 0x7f904a0a0000
mmap(0x7f904a0ed000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1b6000) = 0x7f904a0ed000
mmap(0x7f904a0f3000, 14336, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f904a0f3000
mmap(NULL, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f9049f33000
mprotect(0x7f904a0ed000, 16384, PROT_READ) = 0
mprotect(0x7f904a0fa000, 4096, PROT_READ) = 0
mprotect(0x7f904a117000, 4096, PROT_READ) = 0
mprotect(0x878000, 4096, PROT_READ)     = 0
mprotect(0x7f904a14d000, 4096, PROT_READ) = 0
munmap(0x7f904a11f000, 25926)           = 0
brk(NULL)                               = 0x1255000
brk(0x1276000)                          = 0x1276000
mmap(NULL, 262144, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f9049ef3000
mmap(NULL, 131072, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f9049ed3000
mmap(NULL, 1048576, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f9049dd3000
mmap(NULL, 8388608, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f90495d3000
mmap(NULL, 67108864, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f90455d3000
mmap(NULL, 536870912, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f90255d3000
mmap(0xc000000000, 67108864, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xc000000000
mmap(0xc000000000, 67108864, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xc000000000
mmap(NULL, 33554432, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f90235d3000
mmap(NULL, 2165768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f90233c2000
mmap(0x7f9049ed3000, 131072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f9049ed3000
mmap(0x7f9049e53000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f9049e53000
mmap(0x7f90499d9000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f90499d9000
mmap(0x7f9047603000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f9047603000
mmap(0x7f9035753000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f9035753000
mmap(NULL, 1048576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f90232c2000
mmap(NULL, 65536, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f90232b2000
mmap(NULL, 65536, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f90232a2000
mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7f9022aa1000
mprotect(0x7f9022aa2000, 8388608, PROT_READ|PROT_WRITE) = 0
mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7f90222a0000
mprotect(0x7f90222a1000, 8388608, PROT_READ|PROT_WRITE) = 0
mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7f9021a9f000
mprotect(0x7f9021aa0000, 8388608, PROT_READ|PROT_WRITE) = 0
--- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=6578, si_uid=0} ---
mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7f9020a5d000
mprotect(0x7f9020a5e000, 8388608, PROT_READ|PROT_WRITE) = 0
mmap(NULL, 262144, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f9020a1d000
DEBU[0000] Parsing config file...
DEBU[0000] Selecting specific MIG config...
DEBU[0000] Asserting MIG mode configuration...
--- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=6578, si_uid=0} ---
mmap(NULL, 1439992, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f90208bd000
--- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=6578, si_uid=0} ---
DEBU[0000] Walking MigConfig for (devices=all)
DEBU[0000]   GPU 0: 0x20F110DE
DEBU[0000]     Asserting MIG mode: Disabled
--- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=6578, si_uid=0} ---
--- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=6578, si_uid=0} ---
mmap(NULL, 65536, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f902086d000
--- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=6578, si_uid=0} ---
--- SIGURG {si_signo=SIGURG, si_code=SI_TKILL, si_pid=6578, si_uid=0} ---
mmap(NULL, 16777216, PROT_READ, MAP_SHARED, 3, 0) = -1 EINVAL (Invalid argument)
DEBU[0000] Error checking MIG capable: error opening bar0 MMIO resource: failed to open file for mmio: failed to mmap file: invalid argument

FATA[0000] Assertion failure: selected configuration not currently applied
+++ exited with 1 +++

Thanks for your help,
Valentin

You need sudo or root to change the MIG mode.

i'm running the commands as root user
running nvidia-smi commands to create mig instance and change the mig mode works flawlessly on the same shell

i just realised that there was a misunderstanding:

setting the mig mode inluding the device reset works.
the check for mig capability fails every time with:
failed to mmap file: invalid argument
the corresponding syscall: mmap(NULL, 16777216, PROT_READ, MAP_SHARED, 3, 0) = -1 EINVAL (Invalid argument)

Sorry for my quick response yesterday. I only quickly glanced at the error and others have had a similar problem with mmap not succeeding because of a permission error (hence me jumping to conclusions that you weren't running as root).
I've not had any reports of this particular error, so it's unclear immediately what could be causing this. The arguments to the mmap all look reasonable. The reason an EINVAL might be returned are:
       EINVAL We don't like addr, length, or offset (e.g., they are too
              large, or not aligned on a page boundary).

       EINVAL (since Linux 2.6.12) length was 0.

       EINVAL flags contained none of MAP_PRIVATE, MAP_SHARED, or
              MAP_SHARED_VALIDATE.

In this case:

addr is NULL (which is OK, it just means that the kernel will pick the address for us)
length is 16777216 or 0x1000000 (which appears to be of a reasonable size but we should check)
offset is 0 (so should still be page aligned assuming the kernel gives us an addr that is page aligned)
flags contains MAP_SHARED

We also have an fd of 3 being passed in, which I don't see an open() for in the strace (maybe you grepped it out?), but from the code that calls this, I don't see how it could have an incorrect fd:
https://gitlab.com/nvidia/cloud-native/mig-parted/-/blob/master/vendor/gitlab.com/nvidia/cloud-native/go-nvlib/pkg/nvpci/mmio/mmio.go#L43
In any case, an incorrect fd would return an EACCES not an EINVAL so this seems unlikely to be the culprit.
The only thing I can think of is maybe the length is somehow bigger than the actual file? Which again seems unlikely given the code linked above which calls Stat() to get the length from the actual file size.
Also, I have the exact same size for this file on my machine where mig-parted is working:
$ ls -la /sys/bus/pci/devices/0000\:06\:00.0/resource0
-rw------- 1 root root 16777216 Jan 30  2021 /sys/bus/pci/devices/0000:06:00.0/resource0

What's also interesting is that your trace seems to show that the "mig capable" check succeeds when changing MIG mode (and only failing when applying an actual MIG config). Why it would work in one scenario and not the other is very odd.

Hi,
We did some more investigating and it seems the issue is that the debian kernel is compiled with the flag CONFIG_IO_STRICT_DEVMEM
This leads to an mmap error EINVAL if one tries to mmap a pci devices bar0 while the device is bound to a kernel driver.
I could confirm this behavior with a small c program and an unbound device for reference.
Unfortunately I do not know how to get around this other than unloading the kernel driver which is not a viable option.
It would be great if we could find a solution.
Cheers, Valentin

Can you change this line from:
func NewCombinedMigManager() CombinedMigManager {
...
}{mode.NewPciMigModeManager(), config.NewNvmlMigConfigManager()}

to
func NewCombinedMigManager() CombinedMigManager {
...
}{mode.NewNvmlMigModeManager(), config.NewNvmlMigConfigManager()}

and recompile and try it out.
This basically says use NVML for the mode check instead of the PCI bus. It will be slower (but not much hopefully).
This also explains why this worked for MIG mode changes but not for MIG config changes. Only config changes instantiate this "combined" manager (and hard code it to use the PCI variant of the mode manager). Mode changes use NVML if it is available and PCI if it is not (and your setup clearly has the driver / NVML installed).

I also changed cmd/assert/mode.go:28 to
    manager := mode.NewNvmlMigModeManager()
in addition to the suggested change to have everything work via the nvml library. Now export, assert and apply work.
Thanks for your suggestion, maybe a change to detect nvml for this functions would enable mig-parted to run on systems with the kernel flag CONFIG_IO_STRICT_DEVMEM enabled
thanks

Both of these changes seem reasonable to make unconditionally. I wasn't aware of this restriction with CONFIG_IO_STRICT_DEVMEM or I probably would have done it this way in the first place. The next release will have these changes in it.

The following MR is now out to address this. Review welcome:
https://gitlab.com/nvidia/cloud-native/mig-parted/-/merge_requests/45

The fix for this is now included in https://github.com/NVIDIA/mig-parted/releases/tag/v0.1.3 so I m closing this issue. Please reopen (or create a new issue) if you encounter this again in the future.


PostConfirmation does not triggered

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
12
Amplify CLI Version
5
What operating system are you using?
Mac
Amplify Categories
auth
Amplify Commands
Not applicable
Describe the bug
I made an API like following:
mahdijaberzadehansari@Mac-mini-von-Mahdi cimplycitywebapp % amplify add api
? Please select from one of the below mentioned services: GraphQL
? Provide API name: cimplycitywebapp
? Choose the default authorization type for the API Amazon Cognito User Pool
Using service: Cognito, provided by: awscloudformation

 The current configured provider is Amazon Cognito.

 Do you want to use the default authentication and security configuration? Manual configuration
 Select the authentication/authorization services that you want to use: User Sign-Up, Sign-In, connected with AWS IAM controls (Enables per-user Storage features for images or o
ther content, Analytics, and more)
 Please provide a friendly name for your resource that will be used to label this category in the project: cimplycitywebappAuth
 Please enter a name for your identity pool. cimplycitywebappIdentityPool
 Allow unauthenticated logins? (Provides scoped down permissions that you can control via AWS IAM) No
 Do you want to enable 3rd party authentication providers in your identity pool? No
 Please provide a name for your user pool: cimplycitywebappUserPool
 Warning: you will not be able to edit these selections.
 How do you want users to be able to sign in? Email
 Do you want to add User Pool Groups? Yes
? Provide a name for your user pool group: Supers
? Do you want to add another User Pool Group Yes
? Provide a name for your user pool group: Admins
? Do you want to add another User Pool Group Yes
? Provide a name for your user pool group: Employees
? Do you want to add another User Pool Group Yes
? Provide a name for your user pool group: Users
? Do you want to add another User Pool Group No
✔ Sort the user pool groups in order of preference · Supers, Admins, Employees, Users
 Do you want to add an admin queries API? No
 Multifactor authentication (MFA) user login options: OFF
 Email based user registration/forgot password: Enabled (Requires per-user email entry at registration)
 Please specify an email verification subject: Your verification code
 Please specify an email verification message: Your verification code is {####}
 Do you want to override the default password policy for this User Pool? Yes
 Enter the minimum password length for this User Pool: 8
 Select the password character requirements for your userpool: Requires Lowercase, Requires Uppercase, Requires Numbers
 Warning: you will not be able to edit these selections.
 What attributes are required for signing up? Email
 Specify the app's refresh token expiration period (in days): 30
 Do you want to specify the user attributes this app can read and write? Yes
 Specify read attributes: Address, Birthdate, Email, Family Name, Middle Name, Gender, Locale, Given Name, Name, Nickname, Phone Number, Preferred Username, Picture, Profile, We
bsite, Phone Number Verified?
 Specify write attributes: Address, Birthdate, Family Name, Middle Name, Gender, Locale, Given Name, Name, Nickname, Phone Number, Preferred Username, Picture, Profile, Updated
At, Website, Zone Info
 Do you want to enable any of the following capabilities? Add User to Group
 Do you want to use an OAuth flow? No
? Do you want to configure Lambda Triggers for Cognito? Yes
? Which triggers do you want to enable for Cognito Post Confirmation
? What functionality do you want to use for Post Confirmation Add User To Group
? Enter the name of the group to which users will be added. Users
Successfully added resource cimplycitywebappAuthPostConfirmation locally.

Next steps:
Check out sample function code generated in <project-dir>/amplify/backend/function/cimplycitywebappAuthPostConfirmation/src
"amplify function build" builds all of your functions currently in the project
"amplify mock function <functionName>" runs your function locally
"amplify push" builds all of your local backend resources and provisions them in the cloud
"amplify publish" builds all of your local backend and front-end resources (if you added hosting category) and provisions them in the cloud
Successfully added the Lambda function locally
? Do you want to edit your add-to-group function now? No
Successfully added auth resource cimplycitywebappAuth locally

Some next steps:
"amplify push" will build all your local backend resources and provision it in the cloud
"amplify publish" will build all your local backend and frontend resources (if you have hosting category added) and provision it in the cloud

? Do you want to configure advanced settings for the GraphQL API No, I am done.
? Do you have an annotated GraphQL schema? No
? Choose a schema template: Single object with fields (e.g., “Todo” with ID, name, description)

The following types do not have '@auth' enabled. Consider using @auth with @model
         - Todo
Learn more about @auth here: https://docs.amplify.aws/cli/graphql-transformer/auth

GraphQL schema compiled successfully.

Edit your schema at /Users/mahdijaberzadehansari/Git/cimplycitywebapp/amplify/backend/api/cimplycitywebapp/schema.graphql or place .graphql files in a directory at /Users/mahdijaberzadehansari/Git/cimplycitywebapp/amplify/backend/api/cimplycitywebapp/schema
? Do you want to edit the schema now? No
Successfully added resource cimplycitywebapp locally

Some next steps:
"amplify push" will build all your local backend resources and provision it in the cloud
"amplify publish" will build all your local backend and frontend resources (if you have hosting category added) and provision it in the cloud

I expect it adds Users pool group to every new confirmed user. As I defined
? Do you want to configure Lambda Triggers for Cognito? Yes
? Which triggers do you want to enable for Cognito Post Confirmation
? What functionality do you want to use for Post Confirmation Add User To Group
? Enter the name of the group to which users will be added. Users
Successfully added resource cimplycitywebappAuthPostConfirmation locally.

However, it does not execute the PostConfirmation function.
Expected behavior
It adds new confirmed users to a defined goupe
Reproduction steps
App Id: d33iqssbpej0f4
Region: us-east-1
GraphQL schema(s)
No response
Log output
No response
Additional information
No response

I even tried to accept all suggested predefined names for functions and so on. However, after creating a user and confirm it, still there is no log in the CloudWatch regarding invocation of PostConfirmation function.

My suspicion is that some sort of role or permission is missing!

In is interesting to know, when I go to my Manage User Pools there is no connection between the function and the event:

After assigning the suitable function to the Post Confirmation event, I received the following error as soon as the original function is executed:

PostConfirmation failed with error AccessDeniedException: User: arn:aws:sts::226915686048:assumed-role/cimplycitywebappAuthPostConfirmation-staging/cimplycitywebappAuthPostConfirmation-staging is not authorized to perform: cognito-idp:CreateGroup on resource: arn:aws:cognito-idp:us-east-1:226915686048:userpool/us-east-1_fjJQIrPif.

Anyway, finally I figure out which permissions I need to provide for my function.
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "cognito-idp:AdminAddUserToGroup",
                "cognito-idp:GetGroup",
                "cognito-idp:CreateGroup"
            ],
            "Resource": "arn:aws:cognito-idp:eu-west-1:xyz:userpool/abc…",
            "Effect": "Allow"
        }
    ]
}

However, I have this question. Isn't it a bug that it does not bind the function to event and also does not provide enough permissions?
At least it must provide enough explanation in the cli.

I discovered another error also.
The auto generated code for add-to-group.js file in amplify-cli V5.0.1 is as follows:
/* eslint-disable-line */ const aws = require('aws-sdk');

exports.handler = async (event, context) => {
  const cognitoidentityserviceprovider = new aws.CognitoIdentityServiceProvider({ apiVersion: '2016-04-18' });
  const groupParams = {
    GroupName: process.env.GROUP,
    UserPoolId: event.userPoolId,
  };

  const addUserParams = {
    GroupName: process.env.GROUP,
    UserPoolId: event.userPoolId,
    Username: event.userName,
  };

  try {
    await cognitoidentityserviceprovider.getGroup(groupParams).promise();
  } catch (e) {
    await cognitoidentityserviceprovider.createGroup(groupParams).promise();
  }

  try {
    await cognitoidentityserviceprovider.adminAddUserToGroup(addUserParams).promise();
    return {
      statusCode: 200,
      body: JSON.stringify(event)
    }
  } catch (error) {
    return {
      statusCode: 500,
      body: JSON.stringify(error)
    }
  }
};

However, the line body: JSON.stringify(event) makes to see the following error as well:

message: "Invalid lambda function output : Invalid JSON"
__type: "InvalidLambdaResponseException"

Although the code from the old amplify-cli does not generates this error:
  try {
    await cognitoidentityserviceprovider.getGroup(groupParams).promise();
  } catch (e) {
    await cognitoidentityserviceprovider.createGroup(groupParams).promise();
  }

  try {
    await cognitoidentityserviceprovider.adminAddUserToGroup(addUserParams).promise();
    callback(null, event);
  } catch (e) {
    callback(e);
  }

We were able to reproduce it with user groups involved, closing in favor of https://github.com/aws-amplify/amplify-cli/issues/7561.
We are opening a separate issue for tracking the trigger template code.


[http-add-on] admin-port in http-add-on-operator does not exist anymore when using latest commit

The operator cannot start when using latest http-add-on commit
This is due to https://github.com/kedacore/charts/blob/main/http-add-on/templates/deployment-operator.yaml#L53 which apparently does not exist anymore in latest operator code and should thus be removed from the chart manifests as well as its variable.
Expected Behavior
The operator should start
Actual Behavior
The operator crashes with the help message
Steps to Reproduce the Problem

Use commit 0321ee0 from keda-http-add-on in helm chart
Operator crashes

@JorTurFer: Would you like me to submit a PR to remove this admin-port or did I misunderstand why it's not working?

@JorTurFer: Would you like me to submit a PR to remove this admin-port or did I misunderstand why it's not working?

I'm reviewing the whole chart to be sure that it works

I think that this PR aligns the helm chart with latest version. Once it's merged you can use it (pulling it and deploying it locally or building your own chart) if you want to try it.
I have added a validation check for the interceptor ScaledObject, so I hope that the issue won't come back as a regression in the future 🤞

Thanks, yes it looks like it :)


[Sugesstion] Potion Effects

Create Potion Effects for Resistant Types
Talked about that in "[Thoughts] Lets talk a bit #28".
Description:
Create Potion Effects that reduce or raise current defence of the target resistant types.
Implementation:

As Potions: Throw able at targets / drinkable by player - change given Value by X
As Enchantment on Weapons: Enchanting them so they decrease Effect of a given Type with by X% (or after each attack until an max value)
On Armor to inflict this effect on the attacker
On Shields to inflict this effect on the attacker

Auto Creation Effects:

Every Custom Effect added in the config, will generate automatically an potion effect for this custom damage

I'm thinking it's far more reasonable to have a potion effect that increases resistances across the board by say, 10% per level. You can also reverse this and decreases resistances by 10% per level. Dynamically creating potions on the fly sounds like a huge pain as you now need to create your own brewing recipes on the fly too. If you don't then you need to make sure CraftTweaker would be able to create these recipes on the fly instead, so I may stick with something a little more static.
Besides, an 'across the board' buff seems more usable and less niche.


Emacs as a service:  set EDITOR in tty and set VISUAL

Issue description
When using Emacs as a service in NixOS, in a tty EDITOR is not set; at least here it's nano.
VISUAL is not set at all.

You have to set services.emacs.defaultEditor = true;

@rnhmjoj I have.
Did you notice I said "in a tty"?

What do you mean with a tty? a linux virtual terminal?
I just tried with a VM and EDITOR is set even in this case.

Yes, a virtual terminal.
For me EDITOR is set to nano in there.

Uhm, The variable is being reset or the not picked up. What shell are you using?

I'm using zsh.

So @magnetophon there are two problems:

Although services.emacs.defaultEditor = true, the variable EDITOR was still not set in a tty. To reproduce this, I could press Ctrl-Alt-F1 to go to text mode, log in as my user, then type env | grep EDITOR.
VISUAL is not set at all.

For 1, I can't reproduce this. Are you sure you have a clean zsh config?
For 2, we can of course set it with #34570. But as far as I can tell [1], [2], [3], it doesn't matter. Do you have a particular program which is not working?

1: I just renamed my .zshrc and logged in to a tty; problem remains.
2: I mostly use magit, but when I occasionally use git on the cli and commit, it drops me in nano.
Setting VISUAL fixes this.
The sources you cite mostly say to set VISUAL, and optionally set EDITOR to the same thing.
They also say that officially The EDITOR editor should be able to work without use of "advanced" terminal functionality (like old ed or ex mode of vi)..
I won't go as far as advocating we actually do this...

My suggestion is to unset and forget about VISUAL because it's not necessary. git commit will use EDITOR -- if it's set.
We have a NixOS test case that specifically checks for correct setting of the EDITOR variable. How does your setup differ from this?

@rvl To be clear: EDITOR is set by NixOS for me, just not in a tty.
I figured out why VISUAL was set to nano: it was in my .zprofile.
git commit will use VISUAL and fall back to EDITOR if it's not set, so I still suggest we set VISUAL.

So, I tried with zsh and still can't reproduce it. Here's the config
{ config, pkgs, ...}:

{
  imports = [ <nixpkgs/nixos/modules/virtualisation/qemu-vm.nix> ];

  networking.hostName = "vmhost";

  users.extraUsers.vm = {
    isNormalUser = true;
    password     = "vm";
    shell        = "${pkgs.zsh}/bin/zsh";
    extraGroups  = [ "wheel" ];
  };

  services.emacs = {
    enable = true;
    defaultEditor = true;
  };

  programs.zsh = {
    enable = true;
    enableAutosuggestions = true;
    syntaxHighlighting.enable = true;
  };

}

I can't think of any reason why the environment would be different in a vt, unless something in your shell setup is specifically doing this.

Thanks @rnhmjoj.
@magnetophon, try checking all zsh config files listed on the ArchWiki zsh page, and the files that they source. The list was written for Arch Linux but also applies to NixOS.
Also, by default, things should work without needing to set the VISUAL variable.

I found the issue with the vt; it was indeed in my zsh config.
I didn't think to look there, since it was working in X11.
Sorry for the noise.

Also, by default, things should work without needing to set the VISUAL variable.
This came about after some discussion in the #ranger IRC channel.
Maybe @toonn or @Vifon could comment on that?

I recently found out about the proper use of VISUAL and EDITOR, my source.
Ranger's always just used EDITOR as the user's preferred editor. This behavior would be inconvenient for someone who's doing "the right thing." I updated ranger to prefer VISUAL over EDITOR and tried to keep the change backwards compatible, I missed the case where VISUAL's configured but EDITOR is not, so the latest release is technically not backwards compatible but the next one will be.
Technically emacs -nw would fit in VISUAL not EDITOR and emacs's gui mode fits neither. Whether anyone cares is another issue.
I'd hoped NixOS could resolve this misuse because the config is declarative so it could easily define VISUAL instead and every program (Are there many?) that relies exclusively on EDITOR could be fairly easily patched in nixpkgs.

@magnetophon Thanks for the report. Please feel free to close this issue, unless it is stopping you from efficiently using ed.

@rvl your reply reads somewhat glib to me. The issue was already resolved further up in the thread.
If you believe the distinction is pointless on modern systems then please just say so.

If there are official guidelines on the usage of VISUAL and EDITOR I would love to find out.
Would doing "the right thing" actually cause breakage? Afaik most tools check VISUAL before EDITOR.


Update reference to ol/control in OpenFairViewer.js

Described here: https://github.com/eblondel/OpenFairViewer/issues/173

I reproduced several times in Docker and Debian 12 VM


Update app-attach.md

@TomHickling : Thanks for your contribution! The author(s) have been notified to review your proposed change.


[SPARK-11842] [ML] Small cleanups to existing Readers and Writers

Updates:

Add repartition(1) to save() methods' saving of data for LogisticRegressionModel, LinearRegressionModel.
Strengthen privacy to class and companion object for Writers and Readers
Change LogisticRegressionSuite read/write test to fit intercept
Add Since versions for read/write methods in Pipeline, LogisticRegression
Switch from hand-written class names in Readers to using getClass

CC: @mengxr
CC: @yanboliang Would you mind taking a look at this PR?  @mengxr might not be able to soon.  Thank you!

Test build #46288 has started for PR 9829 at commit f042948.

Also @yanboliang please ping me if you send other read/write PRs

Test build #46291 has started for PR 9829 at commit 590f62f.

Test build #46288 has finished for PR 9829 at commit f042948.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * public final class UnsafeSorterSpillReader extends UnsafeSorterIterator implements Closeable \n  * class Pipeline(override val uid: String) extends Estimator[PipelineModel] with MLWritable \n  *   class LogisticRegressionModelWriter(instance: LogisticRegressionModel)\n  *  class CountVectorizerModelWriter(instance: CountVectorizerModel) extends MLWriter\n  * final class IDF(override val uid: String) extends Estimator[IDFModel] with IDFBase\n  *  class MinMaxScalerModelWriter(instance: MinMaxScalerModel) extends MLWriter\n  * class SQLTransformer @Since(\"1.6.0\") (override val uid: String) extends Transformer\n  *  class StandardScalerModelWriter(instance: StandardScalerModel) extends MLWriter\n  *  class StringIndexModelWriter(instance: StringIndexerModel) extends MLWriter\n  * class ALS(override val uid: String) extends Estimator[ALSModel] with ALSParams\n  * abstract class MLWriter extends BaseReadWrite with Logging \n  * trait MLWritable \n  * abstract class MLReader[T] extends BaseReadWrite \n  * trait MLReadable[T] \n  * trait ScalaReflection \n  *   case class Schema(dataType: DataType, nullable: Boolean)\n  *            s\"Unable to generate an encoder for inner class$\n  * case class EncodeUsingSerializer(child: Expression, kryo: Boolean) extends UnaryExpression \n  * case class DecodeUsingSerializer[T](child: Expression, tag: ClassTag[T], kryo: Boolean)`\n

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/46288/
Test PASSed.

Test build #46291 has finished for PR 9829 at commit 590f62f.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  *   class LogisticRegressionModelWriter(instance: LogisticRegressionModel)\n

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/46291/
Test PASSed.

Merged build finished. Test PASSed.

LGTM. Merged into master and branch-1.6. Thanks!


Update agents-overview.md

@guywi-ms : Thanks for your contribution! The author(s) have been notified to review your proposed change. @guywild

#sign-off

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @guywild

#sign-off

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @guywild

Microsoft authors of articles need to make updates through the private repository, so the updates can be staged and validated by current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.
It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
 Public repo URL: https://github.com/MicrosoftDocs/{docs-repo}
 Private repo URL: https://github.com/MicrosoftDocs/{docs-repo-pr}
We have closed this pull request. Please resubmit the updates through the private repo. For more information, see the contributor guide.


How to train?

I am a beginning student.I want to how to train?How should I setting parameters in the "config.py"?

Please check the train command in the readme file.


Update README.md to reflect project transition

This should be merged upon TOC decision to Archive the project.

Approved


Add a script to manage marker traits

Closes https://github.com/rust-lang/regex/issues/756.
This PR introduces a Python script named public-types-tests.py that manages marker traits for the public API types. Following the discussion in https://github.com/rust-lang/regex/issues/756, this script is responsible for two tasks:

Generate a test that asserts marker traits being implemented on the public API types (This test might need to be tweaked so it passes). This is done by generating the docs for this crate, parsing them, and
writing the assertions to the file tests/marker_traits.rs. This shouldn't have to be done very often, probably just once. We pass the -g flag as an argument to the script to generate the tests.
Check the existence of marker-trait tests for each public API type, failing if it doesn't find at least one of the possible four.

This accomplishes three objectives:

Automate generating the assertion for each type.
Failing CI when a new type is added because no test related to it exists.
Avoid regressions in current types having marker traits auto-implemented.

Two things remain for this PR to be ready:

[x] Add comments to the script.
[ ] Setup CI (I need help with this 😅)

@BurntSushi Let me know if this is somewhat near what you had in mind.

@BurntSushi Sorry to bother, is something blocking this PR, or is it way too different from what you expected? 🥺

Haven't had a chance to look yet, sorry. I have a baby at home and the past few weeks have been hectic.

@BurntSushi  Oh, no worries at all. Congrats!!! Sorry for bothering 😅

I'm going to close this out due to inactivity, but I would still like something simple that checks that we're covering the API with tests for marker traits.


what is the meaning of 5D images, dimension, timepoint for image details?

Hi,
Thanks for your great job, I am instesting in it. Now, I have a problem with the meaning of image details.

what does mean for Z-sections,Timepoints, Dimensions (XY)?
Best

Hi @semir2 you can read more about OME's definition of images as five-dimensional entities in the original paper.
Dimensions(XY) and Z-sections define the dimensions of the image alongside the three spatial dimensions (XYZ)
Timepoints defines the dimension of the image alongside the time dimension e.g. in the case of a time-lapse acquisition

Many thanks

No problem. Closing this issue as resolved.


New SequenceGenerator standalone package

This one of the most common needs in a XAF solution and although eXpandFramework has a build-in implementation it is not tested nor documented and has many unrelated dependencies.
A new standalone package that can work with all XAF versions, has a UI and  is tested on each build and documented is required.
Credits: To the company that already sponsored this module implementation

When released the package will also distributed with the Xpand.SystemModule and the existing SequenceGenerator implementation that is not shared to all packages will be removed. The new package will not have support for released sequences.

The pre-release <IP_ADDRESS> in the DevExpress.XAF lab branch  includes commits that relate to this task:

SequenceGenerator: Tests #696
SequenceGenetor: module release #696

To minimize version conflicts we recommend that you use the Xpand.XAF.Core.All, Xpand.XAF.Win.All, Xpand.XAF.Web.All packages. Doing so, all packages will be at your disposal and .NET will add a dependecy only to those packages that you actually use and not to all.

Released packages:
1. [Xpand.Extensions v.<IP_ADDRESS>](https://github.com/eXpandFramework/DevExpress.XAF/tree/master/src/Extensions/Xpand.Extensions)

Xpand.Extensions.Reactive v.<IP_ADDRESS>

Xpand.Extensions.XAF v.<IP_ADDRESS>

Xpand.Extensions.XAF.Xpo v.<IP_ADDRESS>

Xpand.VersionConverter v.2.201.6

Xpand.XAF.Core.All v.<IP_ADDRESS>

Xpand.XAF.ModelEditor v.1.201.5

Xpand.XAF.Modules.AutoCommit v.<IP_ADDRESS>

Xpand.XAF.Modules.CloneMemberValue v.<IP_ADDRESS>

Xpand.XAF.Modules.CloneModelView v.<IP_ADDRESS>

Xpand.XAF.Modules.GridListEditor v.<IP_ADDRESS>

Xpand.XAF.Modules.HideToolBar v.<IP_ADDRESS>

Xpand.XAF.Modules.LookupCascade v.<IP_ADDRESS>

Xpand.XAF.Modules.MasterDetail v.<IP_ADDRESS>

Xpand.XAF.Modules.ModelMapper v.<IP_ADDRESS>

Xpand.XAF.Modules.ModelViewInheritance v.<IP_ADDRESS>

Xpand.XAF.Modules.OneView v.<IP_ADDRESS>

Xpand.XAF.Modules.ProgressBarViewItem v.<IP_ADDRESS>

Xpand.XAF.Modules.Reactive v.<IP_ADDRESS>

Xpand.XAF.Modules.Reactive.Logger v.<IP_ADDRESS>

Xpand.XAF.Modules.Reactive.Logger.Client.Win v.<IP_ADDRESS>

Xpand.XAF.Modules.Reactive.Logger.Hub v.<IP_ADDRESS>

Xpand.XAF.Modules.Reactive.Win v.<IP_ADDRESS>

Xpand.XAF.Modules.RefreshView v.<IP_ADDRESS>

Xpand.XAF.Modules.SequenceGenerator v.2.201.0

Xpand.XAF.Modules.SuppressConfirmation v.<IP_ADDRESS>

Xpand.XAF.Modules.ViewEditMode v.<IP_ADDRESS>

Xpand.XAF.Web.All v.<IP_ADDRESS>

Xpand.XAF.Win.All v.<IP_ADDRESS>

Please update the related Nuget packages and test if issues is addressed. These are nightly nuget packages available only from our NugetServer.
If you do not use these packages directly but through a module of the main eXpandFramework project, please wait for the bot to notify you again when integration is finished or update the related packages manually.
Thanks a lot for your contribution.

The pre-release <IP_ADDRESS> in the DevExpress.XAF lab branch  includes commits that relate to this task:

SequenceGenerator: documentation #696

To minimize version conflicts we recommend that you use the Xpand.XAF.Core.All, Xpand.XAF.Win.All, Xpand.XAF.Web.All packages. Doing so, all packages will be at your disposal and .NET will add a dependecy only to those packages that you actually use and not to all.

Released packages:
1. [Xpand.XAF.Core.All v.<IP_ADDRESS>](https://github.com/eXpandFramework/DevExpress.XAF/tree/master/src/Modules)

Xpand.XAF.Modules.AutoCommit v.<IP_ADDRESS>

Xpand.XAF.Modules.CloneMemberValue v.<IP_ADDRESS>

Xpand.XAF.Modules.GridListEditor v.<IP_ADDRESS>

Xpand.XAF.Modules.HideToolBar v.<IP_ADDRESS>

Xpand.XAF.Modules.LookupCascade v.<IP_ADDRESS>

Xpand.XAF.Modules.MasterDetail v.<IP_ADDRESS>

Xpand.XAF.Modules.ModelMapper v.<IP_ADDRESS>

Xpand.XAF.Modules.OneView v.<IP_ADDRESS>

Xpand.XAF.Modules.ProgressBarViewItem v.<IP_ADDRESS>

Xpand.XAF.Modules.Reactive v.<IP_ADDRESS>

Xpand.XAF.Modules.Reactive.Logger v.<IP_ADDRESS>

Xpand.XAF.Modules.Reactive.Logger.Client.Win v.<IP_ADDRESS>

Xpand.XAF.Modules.Reactive.Logger.Hub v.<IP_ADDRESS>

Xpand.XAF.Modules.Reactive.Win v.<IP_ADDRESS>

Xpand.XAF.Modules.RefreshView v.<IP_ADDRESS>

Xpand.XAF.Modules.SequenceGenerator v.<IP_ADDRESS>

Xpand.XAF.Modules.SuppressConfirmation v.<IP_ADDRESS>

Xpand.XAF.Modules.ViewEditMode v.<IP_ADDRESS>

Xpand.XAF.Web.All v.<IP_ADDRESS>

Xpand.XAF.Win.All v.<IP_ADDRESS>

Please update the related Nuget packages and test if issues is addressed. These are nightly nuget packages available only from our NugetServer.
If you do not use these packages directly but through a module of the main eXpandFramework project, please wait for the bot to notify you again when integration is finished or update the related packages manually.
Thanks a lot for your contribution.

eXpand.lab release 19.2.702.2 includes commit that relate to this task:

SequenceGenerator: Remove old implementation #696

Please test if it addresses the problem. If you use nuget add our LAB NugetServer as a nuget package source in VS.
To minimize version conflicts we recommend that you switch to PackageReference format and use only the eXpandAgnostic, eXpandWin, eXpandWeb packages. Doing so, all packages will be at your disposal and .NET will add a dependecy only to those packages that you actually use and not to all.
Thanks a lot for your contribution.

eXpand.lab release 19.2.702.4 includes commit that relate to this task:

SequenceGenerator: register standalone package in System module #696

Please test if it addresses the problem. If you use nuget add our LAB NugetServer as a nuget package source in VS.
To minimize version conflicts we recommend that you switch to PackageReference format and use only the eXpandAgnostic, eXpandWin, eXpandWeb packages. Doing so, all packages will be at your disposal and .NET will add a dependecy only to those packages that you actually use and not to all.
Thanks a lot for your contribution.

Closing issue for age. Feel free to reopen it at any time.
.Thank you for your contribution.


COPS-4320: Configurable timeouts for readiness checks.

Make readiness-check interval, timeout and delay configurable for the following:

Cassandra
HDFS (current defaults maintained for journal-node, name-node and data-node)
Elasticsearch
Hello-World

Default readiness interval is set to 60 and timeout to 20 to match Marathon default values. Values still need to be fine-tuned via discussion through this PR.

@vishnu2kmohan any objections to @porridge's approach above? We'll leave the current values as default, but they can be overriden as needed by the customer.

@akirillov we can indeed set minimums in config.json. I figured we'd set sane minimums after we had conducted our benchmarks.


Publish 8.2-20230522231450+0000

Publish 8.2-20230522231450+0000

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

There's merge conflict between your PR branch and base branch. Please fix it and try again.

I've triggered a build for you.


MINOR: Get rid of agent checks in Jenkinsfile

We see the ARM agent check timing out frequently. I think the 5 minute timeout might be too aggressive. I think the original intent of this check was to prevent one of these agent check timeouts from propagating to the top level, but that never really worked. So perhaps we don't need these.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

The ARM build is still failing. I've rebuilt it and failed, too.
https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka-pr/detail/PR-12380/2/pipeline/76
I can also take a look when I have time. Thanks.

+1 for removing these builds from PRs. Generally, we should only include widely used platforms where we also have stable build machines.

Using different Jenkins jobs that runs on trunk seems to be a good tradeoff.

@showuon @ijuma @mumrah @dajac Thanks. I've removed these builds from the Jenkinsfile. I am not sure I know how to run them only against trunk. If one of you knows how to do that, let me know or we can consider doing it separately.

I suppose that we could use the “when” clause like here: https://github.com/apache/kafka/blob/8f64477832ac190ec349e188ba47d830aaaed3c8/Jenkinsfile#L170
We can definitely do this separately.

Yeah, these builds are out of control, failing all the time. It's probably more appropriate to make these nightly builds anyway


Applying pyansys/actions v0.4 patch on 0.62

As the title.

Same here, update package versions for asnys-sphinx-theme

Same here, update package versions for asnys-sphinx-theme

Done!

Question... Have you investigated why the docs build process is failing @germa89? We might need to update some other deps as well. This applies to all PRs

Question... Have you investigated why the docs build process is failing @germa89? We might need to update some other deps as well. This applies to all PRs

Because pymapdl install latest numpy ... jezzz

I'm going to avoid pre-commit fails, and style errors


Do less work to add/remove workers to/from PartialRange

r @Raynos @rf

This gets the torch difference between full and partial refresh peers to within a fraction of a percent.

Seems legit.


Lost workers

I use this gem to deploy workers.
But I start 10 workers, only 9, 8 is started.
Please help me!

Take a look at https://github.com/sshingler/capistrano-resque/pull/96
I turned pty off instead of using a nohup.

Closing in favor of #96.