HBASE-23239 Reporting on status of backing MOB files from client-facing cells

Adds a new MapReduce job that builds a report of health of mob files
Also builds background information on mob system use

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
1m  9s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

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

_ master Compile Tests _

:blue_heart:
mvndep
0m 33s
Maven dependency ordering for branch

:green_heart:
mvninstall
5m 46s
master passed

:green_heart:
compile
1m 24s
master passed

:green_heart:
checkstyle
1m 50s
master passed

:green_heart:
shadedjars
5m  2s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
0m 52s
master passed

:blue_heart:
spotbugs
4m 21s
Used deprecated FindBugs config; considering switching to SpotBugs.

:broken_heart:
findbugs
4m 19s
hbase-server in master has 1 extant findbugs warnings.

_ Patch Compile Tests _

:blue_heart:
mvndep
0m 14s
Maven dependency ordering for patch

:green_heart:
mvninstall
5m 28s
the patch passed

:green_heart:
compile
1m 23s
the patch passed

:green_heart:
javac
1m 23s
the patch passed

:broken_heart:
checkstyle
0m 19s
hbase-mapreduce: The patch generated 12 new + 1 unchanged - 0 fixed = 13 total (was 1)

:broken_heart:
whitespace
0m  0s
The patch 2 line(s) with tabs.

:green_heart:
shadedjars
5m  4s
patch has no errors when building our shaded downstream artifacts.

:green_heart:
hadoopcheck
17m 32s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

:green_heart:
javadoc
0m 51s
the patch passed

:broken_heart:
findbugs
0m 57s
hbase-mapreduce generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

_ Other Tests _

:broken_heart:
unit
242m 19s
hbase-server in the patch failed.

:green_heart:
unit
21m 36s
hbase-mapreduce in the patch passed.

:green_heart:
asflicense
0m 54s
The patch does not generate ASF License warnings.

331m 27s

Reason
Tests

FindBugs
module:hbase-mapreduce

Exception is caught when Exception is not thrown in org.apache.hadoop.hbase.mob.mapreduce.MobRefReporter.run(String[])  At MobRefReporter.java:is not thrown in org.apache.hadoop.hbase.mob.mapreduce.MobRefReporter.run(String[])  At MobRefReporter.java:[line 465]

Subsystem
Report/Notes

Docker
Client=19.03.4 Server=19.03.4 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/1/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 9385301c1281 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-785/out/precommit/personality/provided.sh

git revision
master / c58e80fbe6

Default Java
1.8.0_181

findbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/1/artifact/out/branch-findbugs-hbase-server-warnings.html

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/1/artifact/out/diff-checkstyle-hbase-mapreduce.txt

whitespace
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/1/artifact/out/whitespace-tabs.txt

findbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/1/artifact/out/new-findbugs-hbase-mapreduce.html

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/1/artifact/out/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/1/testReport/

Max. process+thread count
5466 (vs. ulimit of 10000)

modules
C: hbase-server hbase-mapreduce U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

whitespace | 0m 0s | The patch 2 line(s) with tabs.

hbase-mapreduce/src/main/java/org/apache/hadoop/hbase/mob/mapreduce/MobRefReporter.java:127: * RESULT OF LOOKUP	FILE REF	comma seperated, base64 encoded rows when there's a problem
hbase-mapreduce/src/main/java/org/apache/hadoop/hbase/mob/mapreduce/MobRefReporter.java:133: * MOB DIR	09c576e28a65ed2ead0004d192ffaa382019110184b30a1c7e034573bf8580aef8393402

these are examples of report output that contains tabs, so I'd rather leave them for accuracy.

rebased to current master.
addressed qabot feedback (with the exception of not changing the example output)
addressed most of @cbaenziger 's feedback.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
1m 24s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

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

_ master Compile Tests _

:blue_heart:
mvndep
0m 35s
Maven dependency ordering for branch

:green_heart:
mvninstall
6m  7s
master passed

:green_heart:
compile
1m 33s
master passed

:green_heart:
checkstyle
1m 55s
master passed

:green_heart:
shadedjars
5m 30s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
1m  8s
master passed

:blue_heart:
spotbugs
5m 23s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
6m 21s
master passed

_ Patch Compile Tests _

:blue_heart:
mvndep
0m 15s
Maven dependency ordering for patch

:green_heart:
mvninstall
5m 58s
the patch passed

:green_heart:
compile
1m 33s
the patch passed

:green_heart:
javac
1m 33s
the patch passed

:broken_heart:
checkstyle
0m 19s
hbase-mapreduce: The patch generated 2 new + 1 unchanged - 0 fixed = 3 total (was 1)

:broken_heart:
whitespace
0m  0s
The patch 2 line(s) with tabs.

:green_heart:
shadedjars
5m 18s
patch has no errors when building our shaded downstream artifacts.

:green_heart:
hadoopcheck
17m 45s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

:green_heart:
javadoc
1m  1s
the patch passed

:green_heart:
findbugs
6m 33s
the patch passed

_ Other Tests _

:broken_heart:
unit
250m 12s
hbase-server in the patch failed.

:green_heart:
unit
21m 16s
hbase-mapreduce in the patch passed.

:green_heart:
asflicense
1m  0s
The patch does not generate ASF License warnings.

344m 48s

Reason
Tests

Failed junit tests
hadoop.hbase.master.assignment.TestMergeTableRegionsProcedure

Subsystem
Report/Notes

Docker
Client=19.03.4 Server=19.03.4 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/2/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 16faff6dea32 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-785/out/precommit/personality/provided.sh

git revision
master / f0f7fae400

Default Java
1.8.0_181

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/2/artifact/out/diff-checkstyle-hbase-mapreduce.txt

whitespace
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/2/artifact/out/whitespace-tabs.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/2/artifact/out/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/2/testReport/

Max. process+thread count
5289 (vs. ulimit of 10000)

modules
C: hbase-server hbase-mapreduce U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/2/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

Checkstyle complaints

./hbase-mapreduce/src/main/java/org/apache/hadoop/hbase/mob/mapreduce/MobRefReporter.java:125: * RESULT OF LOOKUP	FILE REF	comma seperated, base64 encoded rows when there's a problem:20: File contains tab characters (this is the first instance). [FileTabCharacter]
./hbase-mapreduce/src/main/java/org/apache/hadoop/hbase/mob/mapreduce/MobRefReporter.java:132: * MISSING FILE    28e252d7f013973174750d483d358fa020191101f73536e7133f4cd3ab1065edf588d509        MmJiMjMyYzBiMTNjNzc0OTY1ZWY4NTU4ZjBmYmQ2MTUtNTIz,MmEzOGE0YTkzMTZjNDllNWE4MzM1MTdjNDVkMzEwNzAtODg=: Line is longer than 100 characters (found 196). [LineLength]

Whitespace complaints

hbase-mapreduce/src/main/java/org/apache/hadoop/hbase/mob/mapreduce/MobRefReporter.java:125: * RESULT OF LOOKUP	FILE REF	comma seperated, base64 encoded rows when there's a problem
hbase-mapreduce/src/main/java/org/apache/hadoop/hbase/mob/mapreduce/MobRefReporter.java:131: * MOB DIR	09c576e28a65ed2ead0004d192ffaa382019110184b30a1c7e034573bf8580aef8393402

These are all literal examples of the report output. I'd like to keep them accurate.

Failed junit tests | hadoop.hbase.master.assignment.TestMergeTableRegionsProcedure

as far as I can tell this unit test failure is unrelated.

that push was just rebasing to current master

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  9s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

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

_ master Compile Tests _

+0 :ok:
mvndep
0m 34s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
5m 48s
master passed

+1 :green_heart:
compile
1m 25s
master passed

+1 :green_heart:
checkstyle
1m 46s
master passed

+1 :green_heart:
shadedjars
5m  6s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 52s
master passed

+0 :ok:
spotbugs
4m 31s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
5m 20s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
5m 32s
the patch passed

+1 :green_heart:
compile
1m 25s
the patch passed

+1 :green_heart:
javac
1m 25s
the patch passed

-1 :x:
checkstyle
0m 19s
hbase-mapreduce: The patch generated 2 new + 1 unchanged - 0 fixed = 3 total (was 1)

-1 :x:
whitespace
0m  0s
The patch 2 line(s) with tabs.

+1 :green_heart:
shadedjars
5m  3s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
17m 26s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1 :green_heart:
javadoc
0m 57s
the patch passed

+1 :green_heart:
findbugs
6m 26s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
241m 41s
hbase-server in the patch passed.

-1 :x:
unit
27m 25s
hbase-mapreduce in the patch failed.

+1 :green_heart:
asflicense
1m 13s
The patch does not generate ASF License warnings.

338m 25s

Reason
Tests

Failed junit tests
hadoop.hbase.snapshot.TestExportSnapshot

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/3/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 84f75a1b8661 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-785/out/precommit/personality/provided.sh

git revision
master / 834ccb4bf6

Default Java
1.8.0_181

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/3/artifact/out/diff-checkstyle-hbase-mapreduce.txt

whitespace
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/3/artifact/out/whitespace-tabs.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/3/artifact/out/patch-unit-hbase-mapreduce.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/3/testReport/

Max. process+thread count
5357 (vs. ulimit of 10000)

modules
C: hbase-server hbase-mapreduce U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/3/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

again, rebase to current master.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 11s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

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

_ master Compile Tests _

+0 :ok:
mvndep
0m 37s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
5m 35s
master passed

+1 :green_heart:
compile
1m 32s
master passed

+1 :green_heart:
checkstyle
1m 44s
master passed

+1 :green_heart:
shadedjars
4m 53s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 55s
master passed

+0 :ok:
spotbugs
4m 16s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
5m  4s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
5m 16s
the patch passed

+1 :green_heart:
compile
1m 26s
the patch passed

+1 :green_heart:
javac
1m 26s
the patch passed

-1 :x:
checkstyle
0m 21s
hbase-mapreduce: The patch generated 2 new + 1 unchanged - 0 fixed = 3 total (was 1)

-1 :x:
whitespace
0m  0s
The patch 2 line(s) with tabs.

+1 :green_heart:
shadedjars
4m 48s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
17m 28s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1 :green_heart:
javadoc
1m  1s
the patch passed

+1 :green_heart:
findbugs
6m  6s
the patch passed

_ Other Tests _

-1 :x:
unit
288m  3s
hbase-server in the patch failed.

+1 :green_heart:
unit
24m 48s
hbase-mapreduce in the patch passed.

+1 :green_heart:
asflicense
1m 20s
The patch does not generate ASF License warnings.

381m 30s

Reason
Tests

Failed junit tests
hadoop.hbase.master.procedure.TestProcedurePriority

hadoop.hbase.replication.multiwal.TestReplicationEndpointWithMultipleAsyncWAL

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/4/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

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

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-785/out/precommit/personality/provided.sh

git revision
master / 9c82a65b29

Default Java
1.8.0_181

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/4/artifact/out/diff-checkstyle-hbase-mapreduce.txt

whitespace
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/4/artifact/out/whitespace-tabs.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/4/artifact/out/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/4/testReport/

Max. process+thread count
5471 (vs. ulimit of 10000)

modules
C: hbase-server hbase-mapreduce U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/4/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 13s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

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

_ master Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
5m 28s
master passed

+1 :green_heart:
compile
3m 16s
master passed

+1 :green_heart:
checkstyle
2m 48s
master passed

+0 :ok:
refguide
6m 10s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
shadedjars
5m  3s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
3m 41s
master passed

+0 :ok:
spotbugs
15m  3s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
20m 15s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
5m 26s
the patch passed

+1 :green_heart:
compile
3m 17s
the patch passed

+1 :green_heart:
javac
3m 17s
the patch passed

-1 :x:
checkstyle
2m 51s
root: The patch generated 5 new + 2 unchanged - 0 fixed = 7 total (was 2)

-1 :x:
whitespace
0m  0s
The patch 2 line(s) with tabs.

+0 :ok:
refguide
6m 17s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
shadedjars
4m 58s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
21m  5s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1 :green_heart:
javadoc
4m 27s
the patch passed

+1 :green_heart:
findbugs
22m 30s
the patch passed

_ Other Tests _

-1 :x:
unit
241m 40s
root in the patch failed.

+1 :green_heart:
asflicense
1m 41s
The patch does not generate ASF License warnings.

370m 32s

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/6/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile refguide

uname
Linux 30e8eb0a86c2 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-785/out/precommit/personality/provided.sh

git revision
master / 60d9430195

Default Java
1.8.0_181

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/6/artifact/out/branch-site/book.html

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/6/artifact/out/diff-checkstyle-root.txt

whitespace
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/6/artifact/out/whitespace-tabs.txt

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/6/artifact/out/patch-site/book.html

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/6/artifact/out/patch-unit-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/6/testReport/

Max. process+thread count
4650 (vs. ulimit of 10000)

modules
C: hbase-server hbase-mapreduce . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/6/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

this last commit implements some feedback I got from someone in our support organization. essentially, they suggested I make sure each individual line about sizes was a clear stand alone statement to minimize the chances that someone would misinterpret the numbers.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 10s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

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

_ master Compile Tests _

+0 :ok:
mvndep
0m 38s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
5m 42s
master passed

+1 :green_heart:
compile
3m 18s
master passed

+1 :green_heart:
checkstyle
2m 52s
master passed

+0 :ok:
refguide
6m 27s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
shadedjars
5m  2s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
3m 39s
master passed

+0 :ok:
spotbugs
4m  5s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
20m 20s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
5m 28s
the patch passed

+1 :green_heart:
compile
3m 19s
the patch passed

+1 :green_heart:
javac
3m 19s
the patch passed

-1 :x:
checkstyle
2m 54s
root: The patch generated 5 new + 2 unchanged - 0 fixed = 7 total (was 2)

-1 :x:
whitespace
0m  0s
The patch 2 line(s) with tabs.

+0 :ok:
refguide
6m 29s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
shadedjars
5m 55s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
22m  5s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1 :green_heart:
javadoc
4m 28s
the patch passed

+1 :green_heart:
findbugs
22m 18s
the patch passed

_ Other Tests _

-1 :x:
unit
260m 11s
root in the patch failed.

+1 :green_heart:
asflicense
1m 21s
The patch does not generate ASF License warnings.

393m 17s

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/7/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile refguide

uname
Linux 165a0f8d61c8 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-785/out/precommit/personality/provided.sh

git revision
master / 82e155eb26

Default Java
1.8.0_181

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/7/artifact/out/branch-site/book.html

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/7/artifact/out/diff-checkstyle-root.txt

whitespace
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/7/artifact/out/whitespace-tabs.txt

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/7/artifact/out/patch-site/book.html

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/7/artifact/out/patch-unit-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/7/testReport/

Max. process+thread count
4548 (vs. ulimit of 10000)

modules
C: hbase-server hbase-mapreduce . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/7/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

have time to take another look @cbaenziger ?

these three checkstyle things are new and I'll push a fix for them shortly.

./hbase-mapreduce/src/main/java/org/apache/hadoop/hbase/mob/mapreduce/MobRefReporter.java:160: *   * MISSING FILE BUT FAILURE WHILE CHECKING HLINKS - We could not find the referenced file, however: Line is longer than 100 characters (found 102). [LineLength]
./hbase-mapreduce/src/main/java/org/apache/hadoop/hbase/mob/mapreduce/MobRefReporter.java:225:    final Text INCONSISTENT_ARCHIVE_BAD_LINK = new Text("ARCHIVE WITH HLINK BUT NOT FROM OUR TABLE");: Line is longer than 100 characters (found 101). [LineLength]
./hbase-mapreduce/src/main/java/org/apache/hadoop/hbase/mob/mapreduce/MobRefReporter.java:355:          LOG.error("Exception while checking mob area of our table for HFileLinks that point to {}",: Line is longer than 100 characters (found 101). [LineLength]

the other two are the previously mentioned example report output.

whitespace | 0m 0s | The patch 2 line(s) with tabs.

these are example report output, so I think the tabs should be left in place.

[ERROR] Failures:
[ERROR]   TestReplicationEndpointWithMultipleAsyncWAL>TestReplicationEndpoint.testInterClusterReplication:235 Waiting timed out after [30,000] msec Failed to replicate all edits, expected = 2500 replicated = 2467
[WARNING] Flakes:
[WARNING] org.apache.hadoop.hbase.namespace.TestNamespaceAuditor.testRegionMerge(org.apache.hadoop.hbase.namespace.TestNamespaceAuditor)
[ERROR]   Run 1: TestNamespaceAuditor.testRegionMerge:387 Â» Timeout
[INFO]   Run 2: PASS

these failures in the unit tests are not related AFAICT.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 14s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

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

_ master Compile Tests _

+0 :ok:
mvndep
0m 40s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
6m  3s
master passed

+1 :green_heart:
compile
3m 20s
master passed

+1 :green_heart:
checkstyle
2m 55s
master passed

+0 :ok:
refguide
6m 30s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
shadedjars
5m 10s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
3m 48s
master passed

+0 :ok:
spotbugs
4m  8s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
21m  6s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
5m 42s
the patch passed

+1 :green_heart:
compile
3m 18s
the patch passed

+1 :green_heart:
javac
3m 18s
the patch passed

-1 :x:
checkstyle
2m 57s
root: The patch generated 2 new + 2 unchanged - 0 fixed = 4 total (was 2)

-1 :x:
whitespace
0m  1s
The patch 2 line(s) with tabs.

+0 :ok:
refguide
6m 16s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
shadedjars
5m  5s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
17m 16s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1 :green_heart:
javadoc
4m 40s
the patch passed

+1 :green_heart:
findbugs
23m 16s
the patch passed

_ Other Tests _

-1 :x:
unit
284m 14s
root in the patch failed.

+1 :green_heart:
asflicense
1m 34s
The patch does not generate ASF License warnings.

413m 19s

Reason
Tests

Failed junit tests
hadoop.hbase.io.hfile.TestCacheOnWrite

hadoop.hbase.client.TestFromClientSideWithCoprocessor

hadoop.hbase.client.TestFromClientSide

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/8/artifact/out/Dockerfile

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

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile refguide

uname
Linux 1acf3e45d0a0 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-785/out/precommit/personality/provided.sh

git revision
master / d561130e82

Default Java
1.8.0_181

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/8/artifact/out/branch-site/book.html

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/8/artifact/out/diff-checkstyle-root.txt

whitespace
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/8/artifact/out/whitespace-tabs.txt

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/8/artifact/out/patch-site/book.html

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/8/artifact/out/patch-unit-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/8/testReport/

Max. process+thread count
4548 (vs. ulimit of 10000)

modules
C: hbase-server hbase-mapreduce . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-785/8/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

@joshelser  you self-resolved all your concerns, does that mean you're +1?


Dashboard nightly total peicharts do not display correct number of tests

Env: Win7, Chrome, Firefox
Description:
Zafira doesn't show results of web tests.
I can see correct data in JIRA Tickets table, but Nightly total pies do not include those tests (WEB). It is showing only tests from mobile runs.

zafira_project is declared incorrectly as result project filter doesn't include those runs. not a bug but configuration issue in test automation scripts


Feature request: support the schema.org recipe standard’s JSON+LD meta data

I am impressed by the picture to text to webpage current solution already!
I have tried the convertor today with the goal to import the generated file in Nextcloud cookbook.
The html output doesn't satisfy NC Cookbook however as the import end in a "No parser found for the given import" error.
My understanding is that the page needs to support the schema.org recipe standard’s JSON+LD meta data.
Not sure if that is an easy addition or not :/ I will happily participate to that implementation if I can get some directions.
Thank you!

thanks for the feedback! i'll look into this when i have a moment and see what's happening. I have some code for another project that does this already but i can't remember if i integrated it into this solution.

@cben0ist are you able to provide a copy of the html that's generated so I can have a look why the schema.org recipe markup isn't working. It is indeed built in as a feature as I needed that for my pipeline, we should be able to use the google markup validation tool to confirm if and where there's a problem.

@referefref
Sure! Here is 1 example:
`
  |
-- | --
  |
  |
  |
  |
  | Popovers Recipe
  |
  |
  |
  |
  | Popovers
  | Author: Not Specified
  | Date Published: Not Specified
  | Description: This American version of Yorkshire pudding can be served with marmalade and fresh fruit at breakfast or add some grated cheese and herbs for a more savory accompaniment to lunch or dinner.
  | Cuisine: American
  | Prep Time: 10 minutes
  | Cook Time: 20 minutes
  | Total Time: 30 minutes
  | Keywords: popovers, breakfast, savory, American cuisine
  | Yield: 6 servings
  | Category: Side Dish
  | Calories: Not Specified
  |
  | Ingredients
  |
  | 1 1/2 cups milk
  | 3 large eggs
  | 1/2 teaspoon kosher salt
  | 1 tablespoon butter, melted
  | 1 1/2 cups all-purpose flour
  | 2 tablespoons butter, cut into 6 even pieces
  |
  |
  | Instructions
  |
  | Preheat Oven: Preheat oven to 400°F and grease popover pan.
  | Blend Ingredients: Add milk, eggs, kosher salt, melted butter, and all-purpose flour to jar in order listed, excluding the 2 tablespoons butter cut into 6 even pieces. Secure lid and select 'Batters'.
  | Prepare Pan: Place 1 piece of the cut butter into each cup of the popover pan and place pan back in oven until butter is melted.
  | Bake: Pour batter into each cup, filling half full. Bake for 20 minutes. Reduce oven temperature as necessary to prevent over-browning.
  | Serve: Serve popovers hot with marmalade and fresh fruit for breakfast or with grated cheese and herbs for a savory lunch or dinner accompaniment.
  |
  |
  |
  |
  |
`

another one, just in case:

<!DOCTYPE html>

<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Nestles Quik Cake Recipe</title>

Nestles Quik Cake

By Ramona Caudle

A delightful chocolate cake made with Nestles Quik, perfect for any occasion.

Category: Dessert

Cuisine: American

Yield: 1 9x13" cake

Prep Time: 15 minutes

Cook Time: 30 minutes

Total Time: 45 minutes

Ingredients

2 cups flour

2 cups sugar

1/2 tsp. salt

6 T. Nestles Quik

2 eggs, beaten

2 tsps. soda

2 cups buttermilk

1 tsp. vanilla

1-1/2 cups powdered sugar (for topping)

1 stick margarine, melted (for topping)

1/2 cup milk (for topping)

1 tsp. vanilla (for topping)

Instructions

Mix together flour, sugar, Nestles Quik, and salt.

Add beaten eggs, buttermilk (add soda to milk), and vanilla to the dry ingredients.

Grease and flour a 9x13" pan; add batter.

Bake at 350° for 30 minutes.

For the topping, mix together powdered sugar, melted margarine, milk, and vanilla.

Pour the topping over the hot cake.

I've made some updates, it should put the schema at the bottom of the page for now, which isn't technically correct but Nextcloud might not be as picky about the placement of it as Google is. Let me know if there's still an issue, otherwise i'll come back to this later and tidy it up properly.


Some non ASCII characters are not encoded and script fails

I have some user's Full Names which were imported from a CSV file and the non ASCII charcters were turned into symbols.  Specifically names with characters with tildes like the following character: é
The script will see non ASCII characters and fail, if possible could a fix be introduced to allow the script to skip the character or add a random character and continue to finish the report for later editing?  The error I received was:
[!] There was a problem processing campaign ID 32!
L.. Details: 'ascii' codec can't encode character u'\ufffd' in position 16: ordinal not in range(128)
Quick search online says to use .encode() to encode a string instead of using str
Source: https://stackoverflow.com/questions/9942594/unicodeencodeerror-ascii-codec-cant-encode-character-u-xa0-in-position-20
Thank you,
JC

Any news on this?

Please note that this appears only an issue for when using python instead of python3.

I intend to work on this issue this week.
Do you mean you do not see this problem when you use Python 3? GoPhish is written for Python 3 and will not work properly if you use Python 2.7.

It is properly working for python3. I was confused by the documentation because it is stating:
pip install -r requirements.txt instead of pip3 install -r requirements.txt
My bad.

Thanks for the update! I may change the README to point people in the direction of using pipenv to avoid these sorts of issues.
Let me know if you run into any issues!


<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">=18". Got "16.14.2"

yarn安装依赖报错
为什么要node18以上？
有没有其他解决方案？
报错代码：
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">=18". Got "16.14.2"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

ask commander.js team.

解决了么


Finding Address

I've tried running both the 100-channel scanner as well as the 10/40/70 channel hopping version that was commented out. Both are spitting out unique addresses anytime a packet is found and I cannot seem to find a stable address or get a reading with valid probe data.
All of my readings I'm picking up have unique address and gibberish probe readings.
     Probe 1: 2953.30 (alarm min: 2344.70, max: -2937.80)
     Probe 2: -93.50 (alarm min: -2376.60, max: -1901.80)

Is the latest Smoke_NRF24_Address/Smoke_NRF24_Address.ino the sketch I should be using?
Why did you switch to scanning 100 channels vs originally hopping the FCC documented 10/40/70?

Thanks

Hey, yeah, the latest Smoke_NRF24_Address/Smoke_NRF24_Address.ino is the one I used to find the address of my Smoke unit. I switched from 10/40/70 to 100 because I wanted to see if any other channels are used. I just left it running for about 30 minutes. In the end I saw valid transmissions only on channels 10, 40 and 70. All other channels were fairly quiet.
Here is the actual output of my scanning:
Switching frequency: 71
Switching frequency: 70
 Data: 29 60 5D 0E 17 85 02 40 06 40 01 73 03 40 06 40 01 00 00 00 03 01 00 00 96 00
     Probe 1: 64.50 (alarm min: 32.00, max: 160.00)
     Probe 2: 88.30 (alarm min: 32.00, max: 160.00)
 Data: 29 60 5D 0E 17 85 02 40 06 40 01 73 03 40 06 40 01 00 00 00 03 01 00 00 96 00
     Probe 1: 64.50 (alarm min: 32.00, max: 160.00)
     Probe 2: 88.30 (alarm min: 32.00, max: 160.00)
 Data: 29 60 5D 0E 17 85 02 40 06 40 01 73 03 40 06 40 01 00 00 00 03 01 00 00 96 00
     Probe 1: 64.50 (alarm min: 32.00, max: 160.00)
     Probe 2: 88.30 (alarm min: 32.00, max: 160.00)
 Data: 29 60 5D 0E 17 85 02 40 06 40 01 73 03 40 06 40 01 00 00 00 03 01 00 00 96 00
     Probe 1: 64.50 (alarm min: 32.00, max: 160.00)
     Probe 2: 88.30 (alarm min: 32.00, max: 160.00)
 Data: 29 60 5D 0E 17 85 02 40 06 40 01 73 03 40 06 40 01 00 00 00 03 01 00 00 96 00
     Probe 1: 64.50 (alarm min: 32.00, max: 160.00)
     Probe 2: 88.30 (alarm min: 32.00, max: 160.00)
 Data: 29 60 5D 0E 17 85 02 40 06 40 01 73 03 40 06 40 01 00 00 00 03 01 00 00 96 00
     Probe 1: 64.50 (alarm min: 32.00, max: 160.00)
     Probe 2: 88.30 (alarm min: 32.00, max: 160.00)
 Data: 29 60 5D 0E 17 85 02 40 06 40 01 73 03 40 06 40 01 00 00 00 03 01 00 00 96 00
     Probe 1: 64.50 (alarm min: 32.00, max: 160.00)
     Probe 2: 88.30 (alarm min: 32.00, max: 160.00)
Switching frequency: 69
Switching frequency: 68
Switching frequency: 67
Switching frequency: 66
Switching frequency: 65
Switching frequency: 64
Switching frequency: 63
Switching frequency: 62
Switching frequency: 61
 Data: 5A 90 12 84 53 2A 20 52 96 52 95
     Probe 1: 823.40 (alarm min: -2731.00, max: -2705.40)
     Probe 2: -2107.20 (alarm min: -2129.00, max: -2190.60)
 Data: 54 A5 55 2A 5C AB 42 09 E9 C8 A8 AA A5 2D
     Probe 1: 1706.70 (alarm min: -2232.80, max: -587.90)
     Probe 2: -2312.60 (alarm min: -2402.30, max: -2811.50)
Switching frequency: 60
Switching frequency: 59
Switching frequency: 58
Switching frequency: 57
Switching frequency: 56

Hope this helps.

OK, thanks for sanity checking the code for me - I'm not seeing anything like that at all. I'm starting to question my nrf24 now as even with a Flipper it's spitting out unique addresses and random packet lengths every time.

Do you have a second nrf24 unit to test with? Or, if you have one, you can try setting up a basic sender/receiver just to make sure everything is wired correctly and you are not dealing with a faulty unit.

I did just that - I set up two completely different NRF24 modules and was able to verify they can TX/RX (the guide you linked). They were able to talk fine. However, unfortunately I'm still getting only random length packets.
Do you reliably see the Smoke every ~15 seconds? If I didn't know any better it's as if my Smoke isn't even transmitting, but I'm watching the Smoke receiver get updates every 15 seconds, so clearly it is.

I found it! I'll contribute back a slightly more robust address finder later, but for now I just wanted to share my excitement and explain. You (or your Smoke rather) used a 0x55 preamble. I needed to us 0xAA because my MAC's first bit is a 1. From Travis Goodspeed:
In the case of the Nordic radios, there is no SYNC pattern unique to the radio. Instead, the MAC address itself serves this purpose. So an [OpenBeacon](http://www.openbeacon.org/) packet will begin with {0x55, 0x01, 0x02, 0x03, 0x02, 0x01} while a [Turning Point Clicker](http://travisgoodspeed.blogspot.com/2010/07/reversing-rf-clicker.html)'s packets will begin with {0x55, 0x12, 0x34, 0x56}. The preamble in this case will be 0x55 if the first bit of the SYNC/MAC is a 0 and 0xAA if the first bit is a 1. To make matters worse, the chip does not allow a MAC shorter than three bytes, so previously it was believed that at least so many bytes of the destination address must be known in order to receive a packet with this chip.

So, a more robust scanner should try both. I don't think it necessary to even hop 10/40/70 - the transmitter already broadcasts all three. It would just help with interference I suppose.
Thanks for your help. I'll share my project once I've completed it. I was stuck on step 0 :)

Added changed in #3

Great find!! Thanks for the updates.


Add SPARQL queries to interlink contributors from BnF

During data integration we extract relevant links from BnF dumps to own named graphs

ISNI links in <http://bnf-contributors-isni>
VIAF links in <http://bnf-contributors-viaf>
Wikidata links in <http://bnf-contributors-wikidata>

The sparql query in this file creates links for ISNI according to the Bibframe ontology. The same is needed for VIAF and Wikidata
Then the queries can be written.

There are now 3 SPARQL update queries which try to enrich existing BELTRANS contributor records (via ISNI, VIAF or Wikidata). Additionally, there is 1 SPARQL update query which creates BELTRANS contributors from BnF data in case none of the existent records links already via schema:sameAs.


[BUG] Random LoadProhibited when publishing command callback

The crash will occur after around 20000000 ticks, and happens when trying to send a new publish to AWS IoT. The program is set to publish to AWS IoT every 30 seconds.
The error occurs when performing xTaskNotify, which is coming from the example function provided in this repo.
System information

Hardware board: ESP32-PICO-MINI
Operating System: Linux

Expected behavior
A clear description of the expected behavior.
Screenshots or console output
I (21102850) coreMQTT: Ack packet deserialized with result: MQTTSuccess.
I (21102850) coreMQTT: State record updated. New state=MQTTPublishDone.
Guru Meditation Error: Core  0 panic'ed (LoadProhibited). Exception was unhandled.

Core  0 register dump:
PC      : 0x400964de  PS      : 0x00060f33  A0      : 0x800e1b51  A1      : 0x3ffe7170
0x400964de: xTaskGenericNotify at /Users/test/esp/esp-idf/components/freertos/FreeRTOS-Kernel/tasks.c:5718

A2      : 0x0000cdcd  A3      : 0x3ffbdc38  A4      : 0x80096c4c  A5      : 0x00000003
A6      : 0x00000000  A7      : 0x00000031  A8      : 0x800964ce  A9      : 0x0000cecd
A10     : 0x00000001  A11     : 0x3ffc3638  A12     : 0x00060f20  A13     : 0x00060f23
A14     : 0x0000000f  A15     : 0x0000cdcd  SAR     : 0x00000004  EXCCAUSE: 0x0000001c
EXCVADDR: 0x0000cf21  LBEG    : 0x400014fd  LEND    : 0x4000150d  LCOUNT  : 0xfffffffc

Backtrace: 0x400964db:0x3ffe7170 0x400e1b4e:0x3ffe7190 0x400e7919:0x3ffe71b0 0x400e7b50:0x3ffe71f0 0x400e9a11:0x3ffe7210 0x400e9b51:0x3ffe7290 0x400e7e69:0x3ffe72b0 0x400dbea8:0x3ffe7300 0x40096c49:0x3ffe7320
0x400964db: xTaskGenericNotify at /Users/test/esp/esp-idf/components/freertos/FreeRTOS-Kernel/tasks.c:5718

0x400e1b4e: prvPublishCommandCallback at /Users/test/esp-git/esp-matter/examples/im/outlet/main/aws_iot/fleet_prov_by_claim_demo.c:380

0x400e7919: concludeCommand at /Users/test/esp-git/esp-matter/libraries/esp-aws-iot/libraries/coreMQTT-Agent/coreMQTT-Agent/source/core_mqtt_agent.c:808

0x400e7b50: handleAcks at /Users/test/esp-git/esp-matter/libraries/esp-aws-iot/libraries/coreMQTT-Agent/coreMQTT-Agent/source/core_mqtt_agent.c:638
 (inlined by) mqttEventCallback at /Users/test/esp-git/esp-matter/libraries/esp-aws-iot/libraries/coreMQTT-Agent/coreMQTT-Agent/source/core_mqtt_agent.c:700

0x400e9a11: handlePublishAcks at /Users/test/esp-git/esp-matter/libraries/esp-aws-iot/libraries/coreMQTT/coreMQTT/source/core_mqtt.c:1555
 (inlined by) handleIncomingAck at /Users/test/esp-git/esp-matter/libraries/esp-aws-iot/libraries/coreMQTT/coreMQTT/source/core_mqtt.c:1601
 (inlined by) receiveSingleIteration at /Users/test/esp-git/esp-matter/libraries/esp-aws-iot/libraries/coreMQTT/coreMQTT/source/core_mqtt.c:1756

0x400e9b51: MQTT_ProcessLoop at /Users/test/esp-git/esp-matter/libraries/esp-aws-iot/libraries/coreMQTT/coreMQTT/source/core_mqtt.c:3065

0x400e7e69: processCommand at /Users/test/esp-git/esp-matter/libraries/esp-aws-iot/libraries/coreMQTT-Agent/coreMQTT-Agent/source/core_mqtt_agent.c:611
 (inlined by) MQTTAgent_CommandLoop at /Users/test/esp-git/esp-matter/libraries/esp-aws-iot/libraries/coreMQTT-Agent/coreMQTT-Agent/source/core_mqtt_agent.c:1059

0x400dbea8: prvMQTTAgentTask at /Users/test/esp-git/esp-matter/examples/im/outlet/main/aws_iot/networking/mqtt/core_mqtt_agent_manager.c:521

0x40096c49: vPortTaskWrapper at /Users/test/esp/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/port.c:154

static void prvPublishCommandCallback( MQTTAgentCommandContext_t * pxCommandContext,
                                       MQTTAgentReturnInfo_t * pxReturnInfo )
{
    /* Store the result in the application defined context so the task that
     * initiated the publish can check the operation's status. */
    pxCommandContext->xReturnStatus = pxReturnInfo->returnCode;

    if( pxCommandContext->xTaskToNotify != NULL )
    {
        /* Send the context's ulNotificationValue as the notification value so
         * the receiving task can check the value it set in the context matches
         * the value it receives in the notification. */
        xTaskNotify( pxCommandContext->xTaskToNotify,
                     pxCommandContext->ulNotificationValue,
                     eSetValueWithOverwrite ); # LINE 380
    }
}

static void prvPublishToTopic( MQTTQoS_t xQoS,
                               char * pcTopicName,
                               char * pcPayload )
{
    uint32_t ulPublishMessageId, ulNotifiedValue = 0;

    MQTTStatus_t xCommandAdded;
    BaseType_t xCommandAcknowledged = pdFALSE;

    MQTTPublishInfo_t xPublishInfo = { 0 };

    MQTTAgentCommandContext_t xCommandContext = { 0 };
    MQTTAgentCommandInfo_t xCommandParams = { 0 };

    xTaskNotifyStateClear( NULL );

    /* Create a unique number for the publish that is about to be sent.
     * This number is used in the command context and is sent back to this task
     * as a notification in the callback that's executed upon receipt of the
     * publish from coreMQTT-Agent.
     * That way this task can match an acknowledgment to the message being sent.
     */
    xSemaphoreTake( xMessageIdSemaphore, portMAX_DELAY );
    {
        ++ulMessageId;
        ulPublishMessageId = ulMessageId;
    }
    xSemaphoreGive( xMessageIdSemaphore );

    /* Configure the publish operation. The topic name string must persist for
     * duration of publish! */
    xPublishInfo.qos = xQoS;
    xPublishInfo.pTopicName = pcTopicName;
    xPublishInfo.topicNameLength = ( uint16_t ) strlen( pcTopicName );
    xPublishInfo.pPayload = pcPayload;
    xPublishInfo.payloadLength = ( uint16_t ) strlen( pcPayload );

    /* Complete an application defined context associated with this publish
     * message.
     * This gets updated in the callback function so the variable must persist
     * until the callback executes. */
    xCommandContext.ulNotificationValue = ulPublishMessageId;
    xCommandContext.xTaskToNotify = xTaskGetCurrentTaskHandle();

    xCommandParams.blockTimeMs = fleetprovbyclaimconfigMAX_COMMAND_SEND_BLOCK_TIME_MS;
    xCommandParams.cmdCompleteCallback = prvPublishCommandCallback;
    xCommandParams.pCmdCompleteCallbackContext = &xCommandContext;

    do
    {
        /* Wait for coreMQTT-Agent task to have working network connection and
         * not be performing an OTA update. */
        xEventGroupWaitBits( xNetworkEventGroup,
                             CORE_MQTT_AGENT_CONNECTED_BIT | CORE_MQTT_AGENT_OTA_NOT_IN_PROGRESS_BIT,
                             pdFALSE,
                             pdTRUE,
                             portMAX_DELAY );

        ESP_LOGI( TAG,
                  "Sending publish request to coreMQTT-Agent with message \"%s\" on topic \"%s\" with ID %ld.",
                  pcPayload,
                  pcTopicName,
                  ulPublishMessageId );

        /* To ensure ulNotification doesn't accidentally hold the expected value
         * as it is to be checked against the value sent from the callback.. */
        ulNotifiedValue = ~ulPublishMessageId;

        xCommandAcknowledged = pdFALSE;

        xCommandAdded = MQTTAgent_Publish( &xGlobalMqttAgentContext,
                                           &xPublishInfo,
                                           &xCommandParams );

        if( xCommandAdded == MQTTSuccess )
        {
            /* For QoS 1 and 2, wait for the publish acknowledgment.  For QoS0,
             * wait for the publish to be sent. */
            ESP_LOGI( TAG,
                      "Waiting for publish %ld to complete.",
                      ulPublishMessageId );

            xCommandAcknowledged = prvWaitForNotification( &ulNotifiedValue );
        }
        else
        {
            ESP_LOGE( TAG,
                      "Failed to enqueue publish command. Error code=%s",
                      MQTT_Status_strerror( xCommandAdded ) );
        }

        /* Check all ways the status was passed back just for demonstration
         * purposes. */
        if( ( xCommandAcknowledged != pdTRUE ) ||
            ( xCommandContext.xReturnStatus != MQTTSuccess ) ||
            ( ulNotifiedValue != ulPublishMessageId ) )
        {
            ESP_LOGW( TAG,
                      "Error or timed out waiting for ack for publish message %ld. Re-attempting publish.",
                      ulPublishMessageId );
        }
        else
        {
            ESP_LOGI( TAG,
                      "Publish %ld succeeded.",
                      ulPublishMessageId );
        }
		// @note newly added
		/* Add a little randomness into the delay so the tasks don't remain
         * in lockstep. */
        vTaskDelay( pdMS_TO_TICKS( 125 ) +
                        ( rand() % 0xff ) );

    } while( ( xCommandAcknowledged != pdTRUE ) ||
             ( xCommandContext.xReturnStatus != MQTTSuccess ) ||
             ( ulNotifiedValue != ulPublishMessageId ) );
}

Thank you.

Thank you for reporting this problem. We will look into this problem and discuss with you here.

@law-ko
Can you help to provide the following information?

Your esp-idf version
Your iot-reference-esp32c3 tag or commit
The application code which calls prvPublishToTopic

@chinglee-iot
Your esp-idf version: v5.0.1
Your iot-reference-esp32c3 tag or commit: latest
The application code which calls prvPublishToTopic:
char *jsonString = cJSON_PrintUnformatted(rootJSON);
prvPublishToTopic( xQoS, pcPubTopicBuffer, (char *) jsonString );

We have adjusted the code into our app that work with AWS IoT with desired and reported style. This is uncommon error to see and looking deeper into the code we don't know what was causing this.

The exception you shared indicates a LoadProhibited exception in the tasks.c. From the tasks.c in v5.0.1, the xTaskToNotify is passed by parameters in prvPublishCommandCallback. It looks like xTaskToNotify points to an invalid address.
    BaseType_t xTaskGenericNotify( TaskHandle_t xTaskToNotify,
                                   UBaseType_t uxIndexToNotify,
                                   uint32_t ulValue,
                                   eNotifyAction eAction,
                                   uint32_t * pulPreviousNotificationValue )
    {
            ...
            ucOriginalNotifyState = pxTCB->ucNotifyState[ uxIndexToNotify ]; /* This line has LoadProhibited exception. */

xTaskNotify(xTaskGenericNotify) is called in the prvPublishCommandCallback and is a member variable of input parameter pxCommandContext.
pxCommandContext points to a local variable xCommandContext in prvPublishToTopic. Therefore, it is on the stack of the task which calls prvPublishToTopic.
static void prvPublishToTopic( MQTTQoS_t xQoS,
                               char * pcTopicName,
                               char * pcPayload )
{
...
    MQTTAgentCommandInfo_t xCommandParams = { 0 };
...
    xCommandContext.ulNotificationValue = ulPublishMessageId;
    xCommandContext.xTaskToNotify = xTaskGetCurrentTaskHandle();

    xCommandParams.blockTimeMs = subpubunsubconfigMAX_COMMAND_SEND_BLOCK_TIME_MS;
    xCommandParams.cmdCompleteCallback = prvPublishCommandCallback;
    xCommandParams.pCmdCompleteCallbackContext = &xCommandContext;

Base on these information, we can troubleshoot the following possible causes:

Stack overflow
Local variable xCommandContext in prvPublishToTopic may be corrupted if there is stack overflow. FreeRTOS supports stack overflow detection mechanism. You can reference this page to enable stack overflow checking.

Used after free
The prvPublishCommandCallback is called from another task. If the task calls prvPublishToTopic exited, the stack memory will be used by other task. The pxCommandContext may point to memory modified by other task. We would like to suggest to check the status of the task which calls prvPublishToTopic.

We also suggest you to run the sub_pub_unsub_demo only on your platform to see if this problem can be reproduced and feedback the result. This can help us to narrow down the problem.

@chinglee-iot Would it be possible that this crash is related to the MQTT_ProcessLoop being blocked like xEventGroupWaitBit?

@law-ko
MQTT_ProcessLoop is blocked by transport interface receive function in receiveSingleIteration and is only called in the prvMQTTAgentTask.
static MQTTStatus_t receiveSingleIteration( MQTTContext_t * pContext,
                                            bool manageKeepAlive )
{
    ....
    recvBytes = pContext->transportInterface.recv( pContext->transportInterface.pNetworkContext,
                                                   &( pContext->networkBuffer.pBuffer[ pContext->index ] ),
                                                   pContext->networkBuffer.size - pContext->index );

Could you help to provide the xEventGroupWaitBits call in question so we can discuss it with you here?

Closing this issue due to inactivity. Feel free to re-open the issue if it persists.


CTECH-1586: Updates docker files to accomodate access_token

Signed-off-by: Paul Saunders<EMAIL_ADDRESS>Pull Request Checklist

[x] Read the contributing guidelines
[x] Tests pass

Description of the PR
Updates the docker file and docker-compose file to accommodate personal access tokens.

/LGTM


[DO NOT MERGE] Upgrade jQuery to 1.12.4 (take 2)

Same as https://github.com/alphagov/static/pull/869 but with added fix for jquery tabs.

Performance of the selector engine has improved thanks to a shortcut path that immediately uses precompiled Sizzle selectors when the selector cannot be processed by the native querySelectorAll or matchesSelector methods. This results in a significant speedup in some real-world cases.

Release notes:
https://blog.jquery.com/2016/01/08/jquery-2-2-and-1-12-released/
https://blog.jquery.com/2016/02/22/jquery-1-12-1-and-2-2-1-released/
https://blog.jquery.com/2016/03/17/jquery-1-12-2-and-2-2-2-released/
https://blog.jquery.com/2016/04/05/jquery-1-12-3-and-2-2-3-released/
https://blog.jquery.com/2016/05/20/jquery-1-12-4-and-2-2-4-released/
Similar to previous upgrade jQuery PR:
https://github.com/alphagov/static/pull/628

I've changed the required status checks for this repo. You'll need to rebase this branch against master so that this branch gets a Jenkinsfile can be built against new CI.

I'm holding off merging this until we have Smokey tracking JS errors.

Smokey JS tests are working now (they alerted us to an error with tabs this morning).
It'd be good to get this upgrade out now.

I'd dearly love for someone to review this. Is :cake: required?


Fixing MuxServerSocketChannel when binding to "anyLocalAddress" and attempting to reuse socket by binding a particular interface

As discussed in http://lists.jitsi.org/pipermail/dev/2015-July/024766.html

Thank you very much for the contribution. I'd like to gather opinions on the details here:
Let's say "any local address" covers addresses A and B, we have (1) one MuxServerSocketChannel bound to "any local address" and (2) another one bound to address A.
The way you've done it, if a connection arrives on address B and it matches the filter of (2), (2) will accept it even though it was bound to address A only.
Do we want this behavior? Or do we actually want to make sure that (2) does not accept the connection that arrived on address B because it was bound to address A only?

I and a couple of colleagues had an offline discussion so I wanted to bring you up to speed with our latest view on the subject. We will "want to make sure that (2) does not accept the connection that arrived on address B because it was bound to address A only". Since this behavior includes your proposed modifications, we'll be happy to accept them now and extend them later. As stated at https://jitsi.org/Documentation/FAQ#patch, we will need you to sign our contributor agreement as either an individual (https://jitsi.org/icla) or a corporation (https://jitsi.org/ccla) before we can merge your pull request. Thank you very much!

Makes sense. Just submitted the signature via DocuSign.

Any idea when this is going to make it to the latest build of JVB?


babashka: 0.8.0 -> 0.8.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for babashka is: "A Clojure babushka for the grey areas of Bash"
meta.homepage for babashka is: "https://github.com/babashka/babashka"
meta.changelog for babashka is: "https://github.com/babashka/babashka/blob/v0.8.1/CHANGELOG.md"
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/8n35ssciv0lff2213rv89b87fbb3afq1-babashka-0.8.1/bin/bb had a zero exit code or showed the expected version
0 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 0.8.1 with grep in /nix/store/8n35ssciv0lff2213rv89b87fbb3afq1-babashka-0.8.1
found 0.8.1 in filename of file in /nix/store/8n35ssciv0lff2213rv89b87fbb3afq1-babashka-0.8.1

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

5 total rebuild path(s)

3 package rebuild(s)

2 x86_64-linux rebuild(s)
3 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
babashka
neil
obb

Instructions to test this update (click to expand)

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

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

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

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

2 packages built:

babashka
neil

Maintainer pings
cc @bandresen @bhougland18 @DerGuteMoritz @jlesquembre @thiagokokada for testing.

Result of nixpkgs-review pr 168849 run on x86_64-linux 1

2 packages built:

babashka
neil


statement,slowquery: add request unit part in the detail page

Statement:

Slow Query

ptal @baurine  @Renkai


how to use navigateForResult

how to use navigateForResult?
i didn't find document about it.
please give me an example.

You can use navigateForResult with goBackWith in onter route that you want to return result.

close as inactive


More Recursive Type Declarations

TypeScript Version:
nightly
Code
// A self-contained demonstration of the problem follows...
type Json = string | number | boolean | null | JsonObject | JsonArray;
type JsonObject = { [key:string]: Json };
type JsonArray = Array<Json>;

Expected behavior:
Compiles.
Actual behavior:
Type alias 'Json' circularly references itself.
Type alias 'JsonArray' circularly references itself.
As a workaround, I'm using the more verbose:
declare type Json = JsonObject | number | string | JsonArray;
declare type JsonArray = IMaybeRecursiveArray<JsonObject | number | string>;
interface IMaybeRecursiveArray<T> {
  [i: number]: T | IMaybeRecursiveArray<T>;
}
interface JsonObject {
  [paramKey: string]: Json
}

But FlowType can compile the more "direct" type declarations. It would be nice if Typescript could support this as well.

please see https://github.com/Microsoft/TypeScript/issues/3496#issuecomment-128553540

I definitely never saw that comment. My apologies.


Maximum of 20 TB shown in cache-details

If I open a cache with more than 20 TB (Yes I know, this is rare) the cache-details and the TB-page will only show 20 of them.
Example: At the moment GC193BP  has 24 TBs, but in c:geo I can only count 20.

I wouldn't mind that much about it

Right, the cache page shows only 20 with a link to “Show all TB“
@mucek4: Nor do I, but a bug is a bug so I reported it as I have seen it today. :-)

I agree. But to get more of them we need to load 2 or more pages.

20 entries should be enough. You need the tracking code nevertheless to log it and then you can use the search, so it's more an indicator that there are travelbugs than a full list.

What about a hint like “Check browser for more TB“ or “x more TB in cache“ ? I think this info could be retrieved from the cache page anyway, because the complete amount of TB is shown there.

A hint about more TBs (as in the web) sounds like a good idea.

We could also read the separate cache listing, but only in cases where we have parsed 20 caches on the cache page itself. That way we would have the additional page requests only if there are really that much trackables in a cache.

Here is another cache for testing: GC2W3FD
28 TBs at the moment
By the way: Cool caching...I will visit this one as soon as possible :-)

@Lineflyer GC2W3FD 24/7 and very deluxe !
Changed label from "bug" to "feature request".

http://coord.info/GC29JDX
ober 70 TB at The moment :-)

http://coord.info/GC2W3FD
Over 70 TB at the Moment...

I think it will be worked on this as soon as time permits. At the moment there are some open bugs for the next release, where most of the work is focussed on.
In the meantime I also visited some other TB-hotels with more than 20TBs, so its not so rare as I thought initially.
I raised the priority to medium as a marker/reminder (but this does not mean it will be faster...it always depends on amount of programming which need to be done).
@glider74: This reminds me of calling you maybe in the next week :-)

@Lineflyer
Medium is a bit too much for this. Medium is already something critical, that makes some minor functions not usable, high means that something is really not working and c:geo is unusable. The lowest level is "nothing", so this has already a higher priority.

OK...Lets leave it low.
Maybe sometime we find another way how to sort all the feature requests to get a clue what is worth working on it.


Action event on loaded component Async

What problem does this feature solve?
Reference: https://vuejs.org/v2/guide/components-dynamic-async.html#Handling-Loading-State
Current Issue: We do not know when the async component was loaded, with this, the 'Ref' is also not recognized in the 'mounted()' father
What does the proposed API look like?
Feature Request: Prop from 'created' in asynchronous component to go event
const AsyncComponent = () => ({
  // The component to load (should be a Promise)
  component: import('./MyComponent.vue'),
  // A component to use while the async component is loading
  loading: LoadingComponent,
  // A component to use if the load fails
  error: ErrorComponent,
  // Delay before showing the loading component. Default: 200ms.
  delay: 200,
  // The error component will be displayed if a timeout is
  // provided and exceeded. Default: Infinity.
  timeout: 3000,
  created: () => something()
})

If something needs to happen after the component is loaded, it should be placed inside that component. If that doesn't suit your use case you need to provide more context instead of a single sentence that I can barely understand.

Sorry about my English.
I meant that it has no way of knowing when an asynchronous component was loaded.
The parent component does not recognize the role or property of the child component in the mounted method because the child component is asynchronous.
Example:
<template>
  <div>
    <ChildAsync ref="child"/>
  </div>
</template>

<script>
export default {
  name: "Example",
  components: {
    ChildAsync: () => import("./childExample")
  },
  mounted() {
    this.$refs.child.someFunction(); // *ERROR* -> undefined
  }
};
</script>

You can add a listener on the child component:
<ChildAsync @ready="doSomething"/>

Then in the child's mounted hook do this.$emit('ready')

All right, thank you!

I found a cleaner way to do this (without modify child component):
<ChildAsync @hook:mounted="doSomething"/>


Mac OS X v1.0.4-rc won't start: Termination Reason:    DYLD, [0x1] Library missing

Report output:
Process:               BarterDEX [55447]
Path:                  /private/var/folders/*/BarterDEX.app/Contents/MacOS/BarterDEX
Identifier:            com.electron.barterdex
Version:               1.0.4-rc (1.0.4)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           BarterDEX [55447]
User ID:               501

Date/Time:             2018-05-10 09:46:34.939 +0300
OS Version:            Mac OS X 10.13.4 (17E199)
Report Version:        12
Anonymous UUID:        596382B7-4A5A-37E1-03F5-6A20CCA0179C

Sleep/Wake UUID:       6545D3FF-6087-4B0A-A5D5-49BA1E1A7853

Time Awake Since Boot: 720000 seconds
Time Since Wake:       770 seconds

System Integrity Protection: enabled

Notes:                 Translocated Process

Crashed Thread:        0

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    DYLD, [0x1] Library missing

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: @rpath/Electron Framework.framework/Electron Framework
  Referenced from: /private/var/folders/*/BarterDEX.app/Contents/MacOS/BarterDEX
  Reason: image not found

Binary Images:
       0x10ff69000 -        0x10ff69ff7 +com.electron.barterdex (1.0.4-rc - 1.0.4) <D7B5F7CF-DBCF-309E-9186-AB4AF9F6EB54> /var/folders/*/BarterDEX.app/Contents/MacOS/BarterDEX
       0x11a5c6000 -        0x11a6109df  dyld (551.3) <AFAB4EFA-7020-34B1-BBEF-0F26C6D3CA36> /usr/lib/dyld

Model: MacBookPro10,2, BootROM MBP102.010D.B00, 2 processors, Intel Core i7, 2,9 GHz, 8 GB, SMC 2.6f59
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x10F), Broadcom BCM43xx 1.0 (<IP_ADDRESS>.1a3)
Bluetooth: Version 6.0.5f3, 3 services, 27 devices, 1 incoming serial ports
Network Service: Apple USB Ethernet Adapter, Ethernet, en6
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SD128E, 121,33 GB
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: FaceTime HD Camera (Built-in)
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: Hub
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB 3.0 Bus
Thunderbolt Bus: MacBook Pro, Apple Inc., 23.4

[solved] in 1.0.5-rc


Examples: Add combined bond/linuxbridge/vlan example

Add a real-life complex example to ensure it is working and to use it
for demos in the future.
Signed-off-by: Till Maas<EMAIL_ADDRESS>

This change is

Coverage decreased (-4.2%) to 65.651% when pulling 4faf0ca6842bdf82bcc55706ae1905f1e006992b on tyll:bond_linuxbridge_vlan into afde385d6b06921a0073f04995542974a42e5bab on nmstate:master.


Security Definition Request, Security Definition and Security Definition Request Reject

Security Definition Request (35=d), Security Definition (35=d), and Security Definition Request Reject (35=j) messages in the FIX protocol:
Security Definition Request (35=d) Fields:
SecurityReqID (Tag 320): Unique identifier assigned by the requester to the security definition request message.
SecurityRequestType (Tag 321): Specifies the type of security definition being requested (e.g., requesting all securities, by symbol, by security type, etc.).
Symbol (Tag 55): Unique identifier for the security being requested.
SecurityExchange (Tag 207): Code or identifier representing the exchange where the security is listed.
Issuer (Tag 106): Identifier of the issuer or issuer-specific identifier for the security.
SecurityDesc (Tag 107): Description or name of the security.
SecurityType (Tag 167): Type of the security (e.g., stock, bond, option, future).
Currency (Tag 15): Currency in which the security is denominated.
SubscriptionRequestType (Tag 263): Indicates whether the request is for snapshot, subscribe, unsubscribe, or a snapshot with updates.
Security Definition (35=d) Fields:
SecurityReqID (Tag 320): Unique identifier of the original security definition request.
SecurityResponseID (Tag 322): Unique identifier assigned by the responder to the security definition message.
SecurityResponseType (Tag 323): Type of response to the security definition request (e.g., acceptance, rejection, etc.).
Symbol (Tag 55): Unique identifier for the security.
SecurityExchange (Tag 207): Code or identifier representing the exchange where the security is listed.
Issuer (Tag 106): Identifier of the issuer or issuer-specific identifier for the security.
SecurityDesc (Tag 107): Description or name of the security.
SecurityType (Tag 167): Type of the security (e.g., stock, bond, option, future).
Currency (Tag 15): Currency in which the security is denominated.
ContractMultiplier (Tag 231): Multiplier applied to the contract size to calculate the actual quantity.
MinPriceIncrement (Tag 969): Minimum price increment for the security.
MinPriceIncrementAmount (Tag 1146): Minimum price increment expressed as a monetary amount.
UnitOfMeasure (Tag 996): Unit of measure for the contract size.
PriceUnitOfMeasure (Tag 1191): Unit of measure for the price.
SettlType (Tag 63): Type of settlement for the security.
SettlDate (Tag 64): Date of settlement for the security.
MaturityMonthYear (Tag 200): Month and year of maturity for the security.
CouponRate (Tag 223): Coupon rate or interest rate for the security.
Factor (Tag 228): Factor applied to the price to calculate the actual value.
CreditRating (Tag 255): Credit rating assigned to the security.
SecurityExchangeID (Tag 2076): Unique identifier for the security exchange.
Security Definition Request Reject (35=j) Fields:
SecurityReqID (Tag 320): Unique identifier of the rejected security definition request.
SecurityRequestResult (Tag 560): Result of the security definition request (e.g., successful, invalid security, etc.).
SecurityRequestError (Tag 560): Description of the error or reason for rejecting the security definition request.
SecurityRequestErrorCode (Tag 560): Code indicating the specific error or reason for rejecting the request.
Text (Tag 58): Additional free-text description or information related to the rejection.
These fields provide essential information for requesting and responding to security

who is responsible for sending security definition request

who is responsible for sending security definition request?

In the FIX protocol, the responsibility for sending a Security Definition Request (MsgType 35=d) typically lies with the trading system or market participant who requires information about specific securities. It is the initiator's responsibility to send the Security Definition Request message to request detailed information about one or more securities.
The entity or system that needs information about the securities will initiate the request. This could be a buy-side firm, sell-side firm, exchange, or any other participant involved in trading or market data retrieval.
The sender of the Security Definition Request message specifies the criteria for the requested securities, such as symbol, security type, exchange, or other relevant parameters. The message is then sent to the counterparty or appropriate party responsible for providing the security definitions.
Once the request is made, the counterparty or data provider will respond with a Security Definition (MsgType 35=d) message, which contains the detailed information about the requested securities.
So, in summary, the responsibility for sending the Security Definition Request lies with the entity or system that requires the security information, while the counterparty or data provider is responsible for responding with the Security Definition message

when sending a new Security Definition Request (35=d) message to update or modify the request, it is not necessary to use the same SecurityReqID (Tag 320) as the old request. The SecurityReqID serves as a unique identifier for each individual request, allowing for proper tracking and correlation with its associated response or rejection messages.
When you need to update the request, you can generate a new unique SecurityReqID for the updated message. This new SecurityReqID will differentiate the updated request from the previous one and ensure that the responses or rejections received correspond to the correct request.
By using a new SecurityReqID, you maintain the clarity and integrity of the request-response flow, facilitating accurate identification and tracking of the messages exchanged between the parties involved

In the FIX protocol, when a new Security Definition Request (35=d) message is sent with a new SecurityReqID, it is expected that the acceptor or the counterparty will handle the most recent request and disregard any previous or outdated requests.
The acceptor distinguishes between different requests based on the unique SecurityReqID assigned to each message. When processing incoming messages, the acceptor can maintain a record of the most recent or active SecurityReqID received.
Upon receiving a new Security Definition Request message, the acceptor compares the SecurityReqID of the incoming message with the record of active requests. If the SecurityReqID is different from any previous requests, the acceptor will treat it as a new and separate request.
The acceptor should only respond to the most recent or active requests, ensuring that the responses or rejections are correlated with the correct request. Any previous requests with different SecurityReqID can be considered outdated and ignored by the acceptor


Show upcoming/next block

The original Tetris show the upcoming/next block somewhere. Didn't see it immediately in the demo or options.

+1

:+1:

+1

+1

+1

+1

Almost 2 years later I assume there's not going to be a preview added?

@zfbTony Probably not, but we'd be happy to accept a PR with that feature!

On file blockrain.jquery.src.js, at line 35, add:
      // When next shape is generated
      onNext: function(next){}
and at line 755, add:
          game.options.onNext.call(game.element, this.next);
On constructor, add a method:
onNext: function (next) {
      console.log(next.blockType)
}
So you can use it to your preview.


Coverage for dataStoreInterfaces

This is... much more questionable code than I anticipated going in.
Not gonna change it in this commit though.

Pull Request Test Coverage Report for Build 018e1627-d39c-4896-a310-38db9d3522fb
Details

5 of 5 (100.0%)  changed or added relevant lines in 1 file are covered.
106 unchanged lines in 13 files lost coverage.
Overall coverage increased (+0.02%) to 63.802%

Files with Coverage Reduction
New Missed Lines
%

common/task/fifo_task_scheduler.go
2
85.57%

common/task/weighted_round_robin_task_scheduler.go
2
89.05%

service/history/execution/mutable_state_builder.go
2
68.74%

service/history/task/timer_task_executor_base.go
2
78.38%

service/history/task/transfer_active_task_executor.go
2
72.38%

service/history/task/fetcher.go
3
85.57%

service/history/task/redispatcher.go
4
89.53%

service/history/task/transfer_standby_task_executor.go
4
87.42%

common/persistence/nosql/nosqlplugin/cassandra/workflow.go
6
63.03%

common/persistence/statsComputer.go
6
94.29%

Totals

Change from base Build 018e1613-5a84-4b9d-978a-cd89a943d096:
0.02%

Covered Lines:
93533

Relevant Lines:
146600

💛  - Coveralls


Consider migrating from pydantic to traitlets

we define the config file (soopervisor.yaml) schema using pydantic but traitlets looks more suited for this task as it also allows us to replace values via cli https://traitlets.readthedocs.io/en/stable/

Discarded, tried traitlets. pydantic is a better fit for this project.


not being displayed if too deep.

Is there a limitation to how <content> is inserted into a polymer element's <template>?
If I put the <content> in something like
<content></content>
 it doesn't show.
Here is a jsfiddle demonstrating the problem: http://jsfiddle.net/dannyfritz/vqCFw/6/
I'm on Chrome 29.

@peterwmwong The link to the issue is private. I am getting a 404.
I have been told it's been fixed, can you share a link to the fix please?

@yattias no idea man, its been 2 years and they rewrote Polymer since I commented on this issue.

Yeah, I have no idea what the current status is too.

This is long fixed. The shadow DOM bug isn't private; the link is broken because the polyfills were combined into to a single repo and moved to https://github.com/webcomponents/webcomponentsjs.
I took a look at the list of closed issues that mentioned "content" and nothing's leaping out at me.
AFAIKT, the original jsfiddle listed above now works fine.
And here's a version of the original bug repro in modern polymer, which also doesn't show the described symptoms:
http://jsbin.com/dupine/edit?html,console,output
So, short answer—bug fixed in 2013. If you're seeing something that you think is the same problem, it probably isn't.


Doc: Provide a new WebSocket sample

Based on http://www.websocket.org/echo.html, as chatroom sample was removed from Play 2.3.

Any progress here?


Fix/Advice: cargo audit and unsafe code

PLEASE
use cargo audit regularly and keep the project clean of known vulnerabilities in dep tree.

-> ferrumc/Cargo.toml

Further, it would be nice to prohibit unsafe code directly in lib.rs or main.rs, it's just 1 line at top:
#![forbid(unsafe_code)]
Otherwise, exciting project, keep it up :+1:

Thanks for your advice, and we'll try regularly use cargo audit as you mentioned. And for the unsafe code, sometimes we need to use unsafe code for stuff like SIMD and others, but sure, we'll see what we can do. Thanks again for the advice!


[$1000]  "Mark as unread" option remains checked in the mini menu after performing the action, unlike the behavior of "Copy to Clipboard." option

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open a chat
Hover over a message to open mini menu
Click on "Mark as unread" option from mini menu
Click on "Copy to Clipboard" without closing mini menue

Expected Result:
The "Mark as unread" option should be unmarked in a few seconds in the mini menu after performing the action, similar to the behavior of "Copy to Clipboard" option
Actual Result:
The "Mark as unread" option remains checked in the mini menu after performing the action, unlike the behavior of "Copy to Clipboard." option.
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] MacOS / Chrome / Safari
[ ] MacOS Desktop

Version Number: 1.2.63-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/216225935-23cbbdf8-dd8b-46c4-884f-0ffec38844b3.mp4
https://user-images.githubusercontent.com/43996225/216225950-0ff29839-c5f1-4131-83ca-70dc63ae540f.mp4
Expensify/Expensify Issue URL:
Issue reported by: @Harshdeep
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1675287631133079
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0111b018e5aadca59d
Upwork Job ID:<PHONE_NUMBER>021575680
Last Price Increase: 2023-02-02

Proposal
We need to make autoReset true in:
https://github.com/Expensify/App/blob/a171133dbbda4552366511fc2acedec1816e6137/src/pages/home/report/ContextMenu/ContextMenuActions.js#L157-L68
-        autoReset: false,
+        autoReset: true,

Proposal

In order to match Mark as unread function same as Copy to Clipboard we need to set autoReset parameter to true or remove the parameter at all since by default value is true

https://github.com/Expensify/App/blob/a171133dbbda4552366511fc2acedec1816e6137/src/pages/home/report/ContextMenu/ContextMenuActions.js#L168
    {
        textTranslateKey: 'reportActionContextMenu.markAsUnread',
        icon: Expensicons.Mail,
        successIcon: Expensicons.Checkmark,
        shouldShow: type => type === CONTEXT_MENU_TYPES.REPORT_ACTION,
        onPress: (closePopover, {reportAction, reportID}) => {
            Report.markCommentAsUnread(reportID, reportAction.created);
            if (closePopover) {
                hideContextMenu(true, ReportActionComposeFocusManager.focus);
            }
        },
        getDescription: () => {},
+       autoReset: true,
or
-       autoReset: false, // remove this props since by default always true
    },

Result
https://user-images.githubusercontent.com/47522946/216298063-6f9eee9c-91bd-4183-b7e5-76cfa1e1000b.mov

Proposal
Remove the autoReset field from the markAsUnread context menu option as the default value for it's true.
diff --git a/src/pages/home/report/ContextMenu/ContextMenuActions.js b/src/pages/home/report/ContextMenu/ContextMenuActions.js
index a75e3963e7..a552f74aeb 100644
--- a/src/pages/home/report/ContextMenu/ContextMenuActions.js
+++ b/src/pages/home/report/ContextMenu/ContextMenuActions.js
@@ -165,7 +165,6 @@ export default [
             }
         },
         getDescription: () => {},
-        autoReset: false,
     },

I think this is expected behavior, why would we need to reset it since it is one time action to make it unread

I think this is expected behavior, why would we need to reset it since it is one time action to make it unread

Makes sense - you mark the message as unread so the mark in menu indicates it.

I think it's not expected behaviour because "Copy to clipboard" and "Copy link" has different behaviour.
When you mark a message as unread and move your cursor to a different message then on going back to the previous you will see the mail icon and not the check icon so if the check icon is expected it should stay checked until the message gets read again
In case we think that it's an expected behaviour then it's creating inconsistent behaviour with "Copy to clipboard" and "Copy link" .  So we need to false autoReset from "Copy to clipboard" and "Copy link" .

In case we think that it's an expected behaviour then it's creating inconsistent behaviour with "Copy to clipboard" and "Copy link" . So we need to false autoReset from "Copy to clipboard" and "Copy link" .

This also makes sense, for MarkAsUnread as we make an api call it is beneficial to remain it checked.

It's intentional
https://github.com/Expensify/App/pull/12484
https://github.com/Expensify/App/issues/12319

Proposal
This bug is caused because autoReset is set to false for mark as unread option
removing this line would fix this issue
https://github.com/Expensify/App/blob/a171133dbbda4552366511fc2acedec1816e6137/src/pages/home/report/ContextMenu/ContextMenuActions.js#L168
Originally posted on slack (with bug report)
https://expensify.slack.com/archives/C049HHMV9SM/p1675322574936699?thread_ts=1675287631.133079&cid=C049HHMV9SM

I agree this should be consistent and the checkmark should revert just like the other options in the comment action menu. 👍

@rushatgabhane I first proposed the solution on slack before everyone and I am reporter of this bug as well. I also linked the slack proposal on this issue as per the rules.  I couldn't post it earlier on GitHub because it was locked. Shouldn't I be selected for this job if my proposal is correct?

Hey @Harshdeepjoshi, appreciate that's a tad frustrating. I agree your proposal came first in the Slack thread, but it looks like you posted the bug report in Slack and then later a proposal after the issue creator had created the issue. That delay meant that it didn't get captured in the GH by the issue creator ahead of the other proposals once it opened up, and we ultimately review proposals in GitHub:

Note: whilst you may optionally propose a solution for that job on Slack, solutions are ultimately reviewed in GitHub. The onus is on you to propose the solution on GitHub, and/or ensure the issue creator will include a link to your proposal.

If you have a proposal to fix the bug identified, I'd suggest posting it at the same time as the bug report to avoid that kind of delay and so that the issue creator can include it on the issue when they go about creating it.

@trjExpensify I am still new to this project and trying to learn how things work here, thanks for your advice I will try my best to follow it.

Upwork job price has been updated to $1000

Yep! To confirm, this is the proposal we're going with @nkuoch for you to 🟢: https://github.com/Expensify/App/issues/14748#issuecomment-1413990772

🟢!

📣 @Harshdeepjoshi You have been assigned to this job by @trjExpensify!
Please apply to this job in Upwork and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻
Keep in mind: Code of Conduct | Contributing 📖

@trjExpensify  @rushatgabhane The  PR is ready for review.

@nkuoch, @trjExpensify, @rushatgabhane, @Harshdeepjoshi Huh... This is 4 days overdue. Who can take care of this?

Reviewing label has been removed, please complete the "BugZero Checklist".

The solution for this issue has been :rocket: deployed to production :rocket: in version 1.2.74-0 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

https://github.com/Expensify/App/pull/15057

If no regressions arise, payment will be issued on 2023-02-28. :confetti_ball:
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

[ ] External issue reporter
[ ] Contributor that fixed the issue
[ ] Contributor+ that helped on the issue and/or PR

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

Merged PR within 3 business days of assignment - 50% bonus
Merged PR more than 9 business days after assignment - 50% penalty

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[ ] [@rushatgabhane / @nkuoch] The PR that introduced the bug has been identified. Link to the PR:
[ ] [@rushatgabhane / @nkuoch] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[ ] [@rushatgabhane / @nkuoch] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[ ] [@Harshdeepjoshi] Propose regression test steps to ensure the same bug will not reach production again.
[ ] [@trjExpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

Alrighty, payments are due! Sent offers for the following:

@Harshdeepjoshi $,1250 for the fix and bug report
@rushatgabhane $1,000 for the C+ review

[@rushatgabhane / @nkuoch] The PR that introduced the bug has been identified. Link to the PR:
[@rushatgabhane / @nkuoch] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[@rushatgabhane / @nkuoch] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:

What are your thoughts on these @rushatgabhane @nkuoch? I believe it was this PR?

[@Harshdeepjoshi] Propose regression test steps to ensure the same bug will not reach production again
[@trjExpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

We already have this test case, so I think we could add a small edit to bring it in line with how we test for copy to clipboard:

Navigate to a 1:1 conversation that has a large history of messages.
Scroll the conversation a little and tap hold/hover over a message from the other user and mark the message as "Unread"
Web/Desktop: Verify that the green checkmark doesn't remain checked in the comment action menu
Scroll further up the conversation and verify a "New Messages" button appears
Click/ tap on New Messages button
Verify you are scrolled to the message you marked as unread

Let me know your thoughts!

What are your thoughts on these @rushatgabhane @nkuoch? I believe it was https://github.com/Expensify/App/pull/12484?

I think so yes

Cool, @rushatgabhane if you also agree, can you comment on it and let me know when that's done?

@nkuoch, @trjExpensify, @rushatgabhane, @Harshdeepjoshi Eep! 4 days overdue now. Issues have feelings too...

@nkuoch, @trjExpensify, @rushatgabhane, @Harshdeepjoshi Eep! 4 days overdue now. Issues have feelings too...

Bump on the above @rushatgabhane :)

Reached out to @rushatgabhane!

Excellent, I've gone ahead and issued the payments. Closing this out!


Use templated image for metrics-server.

Use templated image for metrics-server
Fix a bug in install-kube-system.service introduced in #973

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1035   +/-   ##
=======================================
  Coverage   34.92%   34.92%
=======================================
  Files          59       59
  Lines        4160     4160
=======================================
  Hits         1453     1453
  Misses       2545     2545
  Partials      162      162

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6455d68...2ba34ba. Read the comment docs.

Merging this because the bug introduced in #973 prevents controllers to start.


how to get my own intent

eg：define a custom skills  ,i speak alexa,please turn left,how can i get intent,them i can control my device to turn left,now i get the following json:
{
"directive":{
"header":{
"namespace":"SpeechSynthesizer",
"name":"Speak",
"messageId":"40099ed0-acff-42d4-b398-92f8ae0f1e16",
"dialogRequestId":"dialogRequest-321"
},
"payload":{
"url":"cid:ValidatedSpeakDirective_amzn1.ask.skill.3088929e-d56b-4b22-a246-67d28fe2aaf7_819da5fe-ac4f-40ea-9025-f799536207dd_698848474",
"format":"AUDIO_MPEG",
"token":"amzn1.as-ct.v1.ThirdPartySdkSpeechlet#ACRI#ValidatedSpeakDirective_amzn1.ask.skill.3088929e-d56b-4b22-a246-67d28fe2aaf7_819da5fe-ac4f-40ea-9025-f799536207dd"
}
}
}
i can not get useable field to judge my intent
but when i say set a alarm,i get:
{
"directive":{
"header":{
"namespace":"Alerts",
"name":"SetAlert",
"messageId":"f8c02ddb-b0a3-45f7-bbce-c2725bedb8fb"
},
"payload":{
"type":"ALARM",
"scheduledTime":"2017-07-31T16:00:00+0000",
"token":"amzn1.as-ct.v1.Domain:Application:Notifications#DNID#7f9c588c-64cf-3802-96da-b562cf6b2267"
}
}
}
so we can get the filed  like "type".so i can set alarm in my project
so,how can i define a skills let amazon web service respone useable filed to judge my intent
look forward for your replay thanks

Sorry for the late reply.
You can't get your custom skill intent in json response. If you try to invoke your skill then you have to say
"Alexa ask " and then the words set to invoke your skill . For instance, "Alexa ask turn off the light" and in response to that you will get the same response as the first one and not like the second one in which the type will be equal to your intent. As far as I think this is done to maintain the implementation process easy.
You can get an expect speech directive if you have set you session to be continuous in your code while building your skill. And after that ask that question in your skill in which you have set the session to be ended.


Net::ReadTimeout  Exception while trying to upload through the URL method

Hi,
I am uploading the images through the URL method provided by Kraken Ruby Gem. However, at times I get this exception and the upload operation fails.
C:/Ruby21/lib/ruby/2.1.0/net/protocol.rb:158:in rescue in rbuf_fill': Net::ReadTimeout (Net::ReadTimeout)                          from C:/Ruby21/lib/ruby/2.1.0/net/protocol.rb:152:inrbuf_fill'
from C:/Ruby21/lib/ruby/2.1.0/net/protocol.rb:134:in readuntil'                                                            from C:/Ruby21/lib/ruby/2.1.0/net/protocol.rb:144:inreadline'
from C:/Ruby21/lib/ruby/2.1.0/net/http/response.rb:39:in read_status_line'                                                 from C:/Ruby21/lib/ruby/2.1.0/net/http/response.rb:28:inread_new'
from C:/Ruby21/lib/ruby/2.1.0/net/http.rb:1408:in block in transport_request'                                              from C:/Ruby21/lib/ruby/2.1.0/net/http.rb:1405:incatch'
from C:/Ruby21/lib/ruby/2.1.0/net/http.rb:1405:in transport_request'                                                       from C:/Ruby21/lib/ruby/2.1.0/net/http.rb:1378:inrequest'
from C:/Ruby21/lib/ruby/2.1.0/net/http.rb:1371:in block in request'                                                        from C:/Ruby21/lib/ruby/2.1.0/net/http.rb:853:instart'
from C:/Ruby21/lib/ruby/2.1.0/net/http.rb:1369:in request'                                                                 from C:/Ruby21/lib/ruby/gems/2.1.0/gems/httparty-0.13.7/lib/httparty/request.rb:117:inperform'
from C:/Ruby21/lib/ruby/gems/2.1.0/gems/httparty-0.13.7/lib/httparty.rb:545:in perform_request'                            from C:/Ruby21/lib/ruby/gems/2.1.0/gems/httparty-0.13.7/lib/httparty.rb:492:inpost'
from C:/Ruby21/lib/ruby/gems/2.1.0/gems/kraken-io-0.1.3/lib/kraken-io.rb:39:in block in url'                               from C:/Ruby21/lib/ruby/gems/2.1.0/gems/kraken-io-0.1.3/lib/kraken-io.rb:67:incall_kraken'
from C:/Ruby21/lib/ruby/gems/2.1.0/gems/kraken-io-0.1.3/lib/kraken-io.rb:38:in `url'

+1


ci: support multi distro CI

Description

Related: #268
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

CI passed: https://github.com/autowarefoundation/autoware.universe/actions/runs/2389557662

I had to check other workflows.

CI:

https://github.com/autowarefoundation/autoware.universe/actions/runs/2389794808
https://github.com/autowarefoundation/autoware.universe/actions/runs/2389791220
https://github.com/autowarefoundation/autoware.universe/actions/runs/2389794364

No galactic container for arm64. :thinking:

Mm, same kind but another error. :thinking:
https://github.com/autowarefoundation/autoware/runs/6612576310?check_suite_focus=true#step:6:5286

CI: https://github.com/autowarefoundation/autoware/actions/runs/2392404596