HBASE-24284 [h3/jdk11] REST server won't start

Exclude transitive includes of jax-rs 1.x and then
explicitly include jax-rs 2.x glassfish impl for REST
context when hadoop3.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

_ branch-2 Compile Tests _

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

_ Patch Compile Tests _

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

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m 21s
The patch has no ill-formed XML file.

+1 :green_heart:
hadoopcheck
11m 45s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

_ Other Tests _

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

25m 53s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense hadoopcheck xml

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 0d2b959d20

Max. process+thread count
75 (vs. ulimit of 12500)

modules
C: hbase-archetypes/hbase-shaded-client-project hbase-client hbase-endpoint hbase-examples hbase-hadoop2-compat hbase-http hbase-it hbase-mapreduce hbase-rest hbase-rsgroup hbase-server hbase-shaded/hbase-shaded-mapreduce hbase-shaded/hbase-shaded-testing-util hbase-shell hbase-testing-util hbase-thrift U: .

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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 45s
Docker mode activated.

-0 :warning:
yetus
0m  7s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

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

+1 :green_heart:
mvninstall
5m  1s
branch-2 passed

+1 :green_heart:
compile
8m 18s
branch-2 passed

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

-0 :warning:
javadoc
0m 18s
hbase-shaded-client-project in branch-2 failed.

-0 :warning:
javadoc
0m 30s
hbase-client in branch-2 failed.

-0 :warning:
javadoc
0m 24s
hbase-examples in branch-2 failed.

-0 :warning:
javadoc
0m 18s
hbase-hadoop2-compat in branch-2 failed.

-0 :warning:
javadoc
0m 16s
hbase-http in branch-2 failed.

-0 :warning:
javadoc
0m 21s
hbase-mapreduce in branch-2 failed.

-0 :warning:
javadoc
0m 24s
hbase-rest in branch-2 failed.

-0 :warning:
javadoc
0m 23s
hbase-rsgroup in branch-2 failed.

-0 :warning:
javadoc
0m 42s
hbase-server in branch-2 failed.

-0 :warning:
javadoc
1m  0s
hbase-thrift in branch-2 failed.

_ Patch Compile Tests _

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

+1 :green_heart:
mvninstall
4m 43s
the patch passed

+1 :green_heart:
compile
8m  4s
the patch passed

+1 :green_heart:
javac
8m  4s
the patch passed

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

-0 :warning:
javadoc
0m 18s
hbase-hadoop2-compat in the patch failed.

-0 :warning:
javadoc
0m 31s
hbase-client in the patch failed.

-0 :warning:
javadoc
0m 18s
hbase-http in the patch failed.

-0 :warning:
javadoc
0m 51s
hbase-server in the patch failed.

-0 :warning:
javadoc
0m 24s
hbase-mapreduce in the patch failed.

-0 :warning:
javadoc
1m 11s
hbase-thrift in the patch failed.

-0 :warning:
javadoc
0m 28s
hbase-rsgroup in the patch failed.

-0 :warning:
javadoc
0m 28s
hbase-rest in the patch failed.

-0 :warning:
javadoc
0m 24s
hbase-examples in the patch failed.

-0 :warning:
javadoc
0m 18s
hbase-shaded-client-project in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
0m 41s
hbase-hadoop2-compat in the patch passed.

+1 :green_heart:
unit
3m  0s
hbase-client in the patch passed.

+1 :green_heart:
unit
1m  2s
hbase-http in the patch passed.

-1 :x:
unit
210m 10s
hbase-server in the patch failed.

+1 :green_heart:
unit
20m 16s
hbase-mapreduce in the patch passed.

+1 :green_heart:
unit
0m 56s
hbase-testing-util in the patch passed.

+1 :green_heart:
unit
4m 48s
hbase-thrift in the patch passed.

+1 :green_heart:
unit
3m 30s
hbase-rsgroup in the patch passed.

+1 :green_heart:
unit
8m 26s
hbase-shell in the patch passed.

+1 :green_heart:
unit
2m 55s
hbase-endpoint in the patch passed.

+1 :green_heart:
unit
1m  6s
hbase-it in the patch passed.

+1 :green_heart:
unit
4m 25s
hbase-rest in the patch passed.

+1 :green_heart:
unit
2m 33s
hbase-examples in the patch passed.

+1 :green_heart:
unit
0m 36s
hbase-shaded-mapreduce in the patch passed.

+1 :green_heart:
unit
0m 40s
hbase-shaded-testing-util in the patch passed.

+1 :green_heart:
unit
1m  4s
hbase-shaded-client-project in the patch passed.

323m 57s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 54be612b6935 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 0d2b959d20

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-archetypes_hbase-shaded-client-project.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-client.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-examples.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-hadoop2-compat.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-http.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-mapreduce.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-rest.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-rsgroup.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-thrift.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-hadoop2-compat.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-client.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-http.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-mapreduce.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-thrift.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-rsgroup.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-rest.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-examples.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-archetypes_hbase-shaded-client-project.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

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

Max. process+thread count
3871 (vs. ulimit of 12500)

modules
C: hbase-hadoop2-compat hbase-client hbase-http hbase-server hbase-mapreduce hbase-testing-util hbase-thrift hbase-rsgroup hbase-shell hbase-endpoint hbase-it hbase-rest hbase-examples hbase-shaded/hbase-shaded-mapreduce hbase-shaded/hbase-shaded-testing-util hbase-archetypes/hbase-shaded-client-project U: .

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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 46s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

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

+1 :green_heart:
mvninstall
4m  5s
branch-2 passed

+1 :green_heart:
compile
7m 13s
branch-2 passed

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

+1 :green_heart:
javadoc
4m 49s
branch-2 passed

_ Patch Compile Tests _

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

+1 :green_heart:
mvninstall
3m 45s
the patch passed

+1 :green_heart:
compile
7m  2s
the patch passed

+1 :green_heart:
javac
7m  2s
the patch passed

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

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

_ Other Tests _

+1 :green_heart:
unit
0m 29s
hbase-hadoop2-compat in the patch passed.

-1 :x:
unit
1m  2s
hbase-client in the patch failed.

+1 :green_heart:
unit
1m  4s
hbase-http in the patch passed.

-1 :x:
unit
223m 47s
hbase-server in the patch failed.

+1 :green_heart:
unit
21m  5s
hbase-mapreduce in the patch passed.

+1 :green_heart:
unit
1m  1s
hbase-testing-util in the patch passed.

+1 :green_heart:
unit
4m 51s
hbase-thrift in the patch passed.

+1 :green_heart:
unit
4m  2s
hbase-rsgroup in the patch passed.

+1 :green_heart:
unit
8m 14s
hbase-shell in the patch passed.

+1 :green_heart:
unit
3m 53s
hbase-endpoint in the patch passed.

+1 :green_heart:
unit
1m 13s
hbase-it in the patch passed.

+1 :green_heart:
unit
4m 51s
hbase-rest in the patch passed.

+1 :green_heart:
unit
2m 21s
hbase-examples in the patch passed.

+1 :green_heart:
unit
0m 29s
hbase-shaded-mapreduce in the patch passed.

+1 :green_heart:
unit
0m 32s
hbase-shaded-testing-util in the patch passed.

+1 :green_heart:
unit
1m  3s
hbase-shaded-client-project in the patch passed.

328m 20s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 20ff351fad2c 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 0d2b959d20

Default Java
1.8.0_232

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-hbase-client.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/1/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-hbase-server.txt

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

Max. process+thread count
3710 (vs. ulimit of 12500)

modules
C: hbase-hadoop2-compat hbase-client hbase-http hbase-server hbase-mapreduce hbase-testing-util hbase-thrift hbase-rsgroup hbase-shell hbase-endpoint hbase-it hbase-rest hbase-examples hbase-shaded/hbase-shaded-mapreduce hbase-shaded/hbase-shaded-testing-util hbase-archetypes/hbase-shaded-client-project U: .

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 38s
Docker mode activated.

_ Prechecks _

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

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

_ branch-2 Compile Tests _

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

_ Patch Compile Tests _

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

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m 20s
The patch has no ill-formed XML file.

+1 :green_heart:
hadoopcheck
11m 53s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

_ Other Tests _

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

24m 48s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense hadoopcheck xml

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 47dca8eb45

Max. process+thread count
76 (vs. ulimit of 12500)

modules
C: hbase-archetypes/hbase-shaded-client-project hbase-client hbase-endpoint hbase-examples hbase-hadoop2-compat hbase-http hbase-it hbase-mapreduce hbase-rest hbase-rsgroup hbase-server hbase-shaded/hbase-shaded-mapreduce hbase-shaded/hbase-shaded-testing-util hbase-shell hbase-testing-util hbase-thrift U: .

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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
0m 45s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

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

+1 :green_heart:
mvninstall
4m  7s
branch-2 passed

+1 :green_heart:
compile
7m 17s
branch-2 passed

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

-0 :warning:
javadoc
0m 17s
hbase-shaded-client-project in branch-2 failed.

-0 :warning:
javadoc
0m 29s
hbase-client in branch-2 failed.

-0 :warning:
javadoc
0m 21s
hbase-examples in branch-2 failed.

-0 :warning:
javadoc
0m 18s
hbase-hadoop2-compat in branch-2 failed.

-0 :warning:
javadoc
0m 18s
hbase-http in branch-2 failed.

-0 :warning:
javadoc
0m 20s
hbase-mapreduce in branch-2 failed.

-0 :warning:
javadoc
0m 23s
hbase-rest in branch-2 failed.

-0 :warning:
javadoc
0m 22s
hbase-rsgroup in branch-2 failed.

-0 :warning:
javadoc
0m 40s
hbase-server in branch-2 failed.

-0 :warning:
javadoc
0m 50s
hbase-thrift in branch-2 failed.

_ Patch Compile Tests _

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

+1 :green_heart:
mvninstall
3m 58s
the patch passed

+1 :green_heart:
compile
7m 30s
the patch passed

+1 :green_heart:
javac
7m 30s
the patch passed

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

-0 :warning:
javadoc
0m 18s
hbase-hadoop2-compat in the patch failed.

-0 :warning:
javadoc
0m 28s
hbase-client in the patch failed.

-0 :warning:
javadoc
0m 18s
hbase-http in the patch failed.

-0 :warning:
javadoc
0m 39s
hbase-server in the patch failed.

-0 :warning:
javadoc
0m 21s
hbase-mapreduce in the patch failed.

-0 :warning:
javadoc
0m 50s
hbase-thrift in the patch failed.

-0 :warning:
javadoc
0m 23s
hbase-rsgroup in the patch failed.

-0 :warning:
javadoc
0m 23s
hbase-rest in the patch failed.

-0 :warning:
javadoc
0m 21s
hbase-examples in the patch failed.

-0 :warning:
javadoc
0m 16s
hbase-shaded-client-project in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
0m 30s
hbase-hadoop2-compat in the patch passed.

+1 :green_heart:
unit
2m 23s
hbase-client in the patch passed.

+1 :green_heart:
unit
0m 39s
hbase-http in the patch passed.

+1 :green_heart:
unit
121m 54s
hbase-server in the patch passed.

+1 :green_heart:
unit
10m 51s
hbase-mapreduce in the patch passed.

+1 :green_heart:
unit
0m 57s
hbase-testing-util in the patch passed.

+1 :green_heart:
unit
4m 18s
hbase-thrift in the patch passed.

+1 :green_heart:
unit
3m  5s
hbase-rsgroup in the patch passed.

+1 :green_heart:
unit
7m 12s
hbase-shell in the patch passed.

+1 :green_heart:
unit
2m 33s
hbase-endpoint in the patch passed.

+1 :green_heart:
unit
1m  9s
hbase-it in the patch passed.

-1 :x:
unit
2m 44s
hbase-rest in the patch failed.

+1 :green_heart:
unit
1m 38s
hbase-examples in the patch passed.

+1 :green_heart:
unit
0m 34s
hbase-shaded-mapreduce in the patch passed.

+1 :green_heart:
unit
0m 36s
hbase-shaded-testing-util in the patch passed.

+1 :green_heart:
unit
0m 57s
hbase-shaded-client-project in the patch passed.

212m 35s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 47dca8eb45

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-archetypes_hbase-shaded-client-project.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-client.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-examples.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-hadoop2-compat.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-http.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-mapreduce.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-rest.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-rsgroup.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-thrift.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-hadoop2-compat.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-client.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-http.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-mapreduce.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-thrift.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-rsgroup.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-rest.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-examples.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-archetypes_hbase-shaded-client-project.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-rest.txt

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

Max. process+thread count
5388 (vs. ulimit of 12500)

modules
C: hbase-hadoop2-compat hbase-client hbase-http hbase-server hbase-mapreduce hbase-testing-util hbase-thrift hbase-rsgroup hbase-shell hbase-endpoint hbase-it hbase-rest hbase-examples hbase-shaded/hbase-shaded-mapreduce hbase-shaded/hbase-shaded-testing-util hbase-archetypes/hbase-shaded-client-project U: .

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

Patch failed because it does the hadoop3 test run with  -Phadoop-3.0 instead of -Dhadoop.profile=3.0

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

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

+1 :green_heart:
mvninstall
3m 36s
branch-2 passed

+1 :green_heart:
compile
6m 20s
branch-2 passed

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

+1 :green_heart:
javadoc
4m 29s
branch-2 passed

_ Patch Compile Tests _

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

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

+1 :green_heart:
compile
6m 21s
the patch passed

+1 :green_heart:
javac
6m 21s
the patch passed

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

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

_ Other Tests _

+1 :green_heart:
unit
0m 27s
hbase-hadoop2-compat in the patch passed.

+1 :green_heart:
unit
2m 30s
hbase-client in the patch passed.

+1 :green_heart:
unit
1m  4s
hbase-http in the patch passed.

+1 :green_heart:
unit
193m 45s
hbase-server in the patch passed.

+1 :green_heart:
unit
18m 20s
hbase-mapreduce in the patch passed.

+1 :green_heart:
unit
0m 56s
hbase-testing-util in the patch passed.

+1 :green_heart:
unit
4m 38s
hbase-thrift in the patch passed.

+1 :green_heart:
unit
3m 20s
hbase-rsgroup in the patch passed.

+1 :green_heart:
unit
8m  7s
hbase-shell in the patch passed.

+1 :green_heart:
unit
3m 17s
hbase-endpoint in the patch passed.

+1 :green_heart:
unit
1m  6s
hbase-it in the patch passed.

+1 :green_heart:
unit
4m 17s
hbase-rest in the patch passed.

+1 :green_heart:
unit
2m 18s
hbase-examples in the patch passed.

+1 :green_heart:
unit
0m 29s
hbase-shaded-mapreduce in the patch passed.

+1 :green_heart:
unit
0m 31s
hbase-shaded-testing-util in the patch passed.

+1 :green_heart:
unit
1m  2s
hbase-shaded-client-project in the patch passed.

290m  7s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1625/2/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux ffe41d3dfe06 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 47dca8eb45

Default Java
1.8.0_232

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

Max. process+thread count
3690 (vs. ulimit of 12500)

modules
C: hbase-hadoop2-compat hbase-client hbase-http hbase-server hbase-mapreduce hbase-testing-util hbase-thrift hbase-rsgroup hbase-shell hbase-endpoint hbase-it hbase-rest hbase-examples hbase-shaded/hbase-shaded-mapreduce hbase-shaded/hbase-shaded-testing-util hbase-archetypes/hbase-shaded-client-project U: .

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

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.


When add two unsigned long long fields to the tx_thread structure，then create some threads, run some time, The system（cortex-m4） will enter a hardware failure.

Describe the bug
hardware environment: cortex-m4
When add two unsigned long long fields to the tx_thread structure，then create some threads, run some time, The system（cortex-m4） will enter a hardware failure.
A thread uses the function vsnprintf to format a variable of type double into a buffer。but this thread formats variables of other types, such as int, there is  hardware failure in the system。
Please also mention any information which could help others to understand
the problem you're facing:

What target device are you using?: cortex-m4
Which version of Azure RTOS?: 6.1.9
What toolchain and environment? : gcc,cortex-m4
What have you tried to diagnose or workaround this issue?
the caller of  the function hardfault_handler is _tx_thread_schedule.
the  procedure go to some abnormal address like 0xFFFFFFF1
when i change the type of the fields to unsigned long ,the bug will disappear.
registers infor

To Reproduce
Steps to reproduce the behavior:

Build my project in IAR Workbench.
See error

Expected behavior
A clear and concise description of what you expected to happen.
Impact
What impact does this issue have on your progress (e.g., annoyance, showstopper)
Logs and console output
If applicable, add console logs or other types of debug information like Wireshark capture as .zip file.
Additional context
Add any other context about the problem here.

Closing.


Fix JsonLinesFile slicing.

This also slightly reworks start on JsonLinesFile. It is now an index into line_starts instead of the actual offset.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Please tag this pr with at least one of these labels to make our release process faster: BREAKING, new feature, bug fix, other change, dev setup

@jaheba please label as bugfix and for backport if it applies


How to avoid extending $PATH with git-now

Hi
I'm a new Zinit user and I've incorporated the Git extensions from the README into my zshrc, however, with a slight change – instead of using as"program", I'm installing the git-now extension with make"install …":
zinit wait=3 lucid as=null make="install PREFIX=$ZPFX" for iwata/git-now

The problem is that git-now's Makefile doesn't respect PREFIX and installs to the /usr/local/… prefix.
Is there any way to install it under $ZPFX and/or(in general) to avoid modifying $PATH?

The best method would be to first load Bin-Gem-Node annex (a Zinit extension) and then to expose the git-now script/binary via shim, i.e.: a forwarder script that has the path to the shielded binary hard-coded inside itself. Shims are created automatically via sbin'' ice, you can:

pass nothing to the ice, i.e.:
zinit sbin for iwata/git-now

This will work because when the ice is empty then an automatic searching for a binary is performed, which works as follows:

first a check for the trailing component of the id-as ice is being performed, e.g.: id_as'exts/git-my' → it'll check if a file git-my exists and if yes, create the shim git-my,
if no success, then a check the plugin name is done, e.g.: for paulirish/git-open it'll check if a file git-open exists and if yes, create the shim git-open,
for snippets, the trailing component of the snippet URL is being took instead of the plugin name,,
then, if no success, it'll take the name of the alphabetically first executable file, if any,
if still no success, the automatic resolution gives up and a warning message is emitted without creating the shim(s).

pass git-my to the ice, i.e.:
zinit sbin=git-my for iwata/git-now

This instructs Bin-Gem-Node annex to create the shim for the provided file. Note: the sbin'' argument can be a pattern, e.g.: zinit sbin'bin/*' gem'jekyll' for zdharma/null will create the shims for all binaries of the jekyll gem (the example slightly runs forward and introduces the gem'' ice, another feature of Bin-Gem-Node – refer to the annex's README for more information).

That's it. Of course, you would probably also want Turbo, so the full command would be e.g.:
zinit wait=1 lucid sbin for iwata/git-my

Thank you for that answer, it is very helpful.


BUG: Navbar issue on seller page

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
If i shrink size to mobile there is a problem in hamburger menu.

Record

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

This issue already exists. Please check the existing issues before raising a new  one. Find another issue or feature to contribute to. Thank you!


Switch await core.sleep to yield

This is a fix for issue #32

I may add some further examples for UART and bluetooth buffers as well

See https://github.com/adafruit/Adafruit_CircuitPython_asyncio/pull/30 for use of the _Never class.

I agree, this is probably the same problem again, just in code we weren't testing. If changing to 'yield' works, then changing to use the never class will probably work also, while allowing our linters and more importantly our doc-builder to work with the code.

also, super stoked to see the examples, thank you!

As mentioned in #30:

Micropython can use a non-standard construct of yield in an async def to cause the async function to be suspended indefinitely, until some other task causes it to be scheduled again.

It seems to me it should await something that will cause it to be schedule again, instead of this "anonymous" suspension. The _Never class is an implementation of this anonymous suspension. But could it await an Event or something else instead?
An interesting point raised in an asyncio tutorial:

One of the most important points to get across is that the currently executing Task cannot be paused by any means other than awaiting a future (or a custom awaitable object that behaves like one).

I did refactor a bit so that await _never can be written in asyncio itself. I tried but failed to find a way to reuse sleep's singleton code, but probably shouldn't worry about that, it's just a small memory optimization.
diff --git a/asyncio/core.py b/asyncio/core.py
index dcd4b24..f1994eb 100644
--- a/asyncio/core.py
+++ b/asyncio/core.py
@@ -94,11 +94,11 @@ def sleep(t):

 ################################################################################
 # "Never schedule" object"
-# Don't re-schedule the object that awaits the _never singleton.
+# Don't re-schedule the object that awaits _never().
 # For internal use only. Some constructs, like `await event.wait()`,
 # work by NOT re-scheduling the task which calls wait(), but by
 # having some other task schedule it later.
-class _Never:
+class _NeverSingletonGenerator:
     def __init__(self):
         self.state = None
         self.exc = StopIteration()
@@ -117,7 +117,10 @@ class _Never:
            self.exc.__traceback__ = None
            raise self.exc

-_never = _Never()
+def _never(sgen=_NeverSingletonGenerator()):
+    # assert sgen.state is None, "Check for a missing `await` in your code"
+    sgen.state = False
+    return sgen

 ################################################################################
diff --git a/asyncio/event.py b/asyncio/event.py
index 442c5bb..164a269 100644
--- a/asyncio/event.py
+++ b/asyncio/event.py
@@ -62,8 +62,7 @@ class Event:
             self.waiting.push_head(core.cur_task)
             # Set calling task's data to the event's queue so it can be removed if needed
             core.cur_task.data = self.waiting
-            core._never.state = False
-            await core._never
+            await core._never()
         return True

diff --git a/asyncio/lock.py b/asyncio/lock.py
index b5080a3..71c972f 100644
--- a/asyncio/lock.py
+++ b/asyncio/lock.py
@@ -69,8 +69,7 @@ class Lock:
             # Set calling task's data to the lock's queue so it can be removed if needed
             core.cur_task.data = self.waiting
             try:
-                core._never.state = False
-                await core._never
+                await core._never()
             except core.CancelledError as er:
                 if self.state == core.cur_task:
                     # Cancelled while pending on resume, schedule next waiting Task

It seems a bit odd to have a bunch of places where core._io_queue.queue_[read|write] is called immediately followed by yield or await _never. What about making IOQueue.queue_[read|write] a coroutine and call await _never before exit?
This would make the code in stream.py neater and avoid duplication?

What about making IOQueue.queue_[read|write] a coroutine and call await _never before exit?

Seems logical to me, but I'd also look to see if something similar is done in CPython asyncio.

CPython asyncio doesn't seem to have much similarity with the circuitpython code for stream management. I've therefore converted to make IOQueue.queue_read/write methods coroutines.

Looks like as of today we are running pre-commit hooks on python 3.11. This conflicts with pylint 2.11.1 - so I've upgraded the pylint requirement for pre-commit to 2.13.9


Migrate Nested test

Hmm interesting. Only fails on native. I was only running the JVM variant locally when migrating.

It looks like the override isn't working on native. When I force step into equals it goes to kotlin_Any_equals symbol.

I dumped the LLVM bitcode and then converted it back to LLVM assembly to confirm that the poko.Nested.equals() function is completely absent from the native compilation. Its hashCode and toString are present, but something weird is happening with equals. From logging in the compiler plugin I can see that it does match on the fake equals and attempts to replace its body, but for some reason that doesn't end up in the binary and I don't know why.


[Request for Exernal] - Codeunit: Copy Doc. Mgt: Event: OnCopyPurchDocLineOnBeforeCopyThisLine

Describe the request
could NextLineNo be added to this event as a reference?
 OnCopyPurchDocLineOnBeforeCopyThisLine(ToPurchLine, FromPurchLine, MoveNegLines, FromPurchDocType, LinesNotCopied, CopyThisLine, Result, IsHandled, ToPurchHeader, RecalculateLines,NextLineNo);

  [IntegrationEvent(false, false)]
    local procedure OnCopyPurchDocLineOnBeforeCopyThisLine(var ToPurchLine: Record "Purchase Line"; var FromPurchLine: Record "Purchase Line"; MoveNegLines: Boolean; FromPurchDocType: Enum "Purchase Document Type From"; var LinesNotCopied: Integer; var CopyThisLine: Boolean; var Result: Boolean; var IsHandled: Boolean; ToPurchaseHeader: Record "Purchase Header"; var RecalculateLines: Boolean;Var NextLineNo:Integer)
    begin
    end;

Additional context
Because we have our own attach to. fields, and want to use it to insert attached lines.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 14309.


Add a contributors guide

We need a document that outlines the various ways to engage with the team.  Leverage the work that's been done by VS and Azure for this.

A little early but will we be able to submit custom extractors for considerations as well or rather not?

You can definitely submit more samples here, but it may be just as easy to have your own repo, we would be happy with either.
On Wed, Nov 4, 2015 at 7:58 PM -0800, "Tom Kerkhove" <notifications<EMAIL_ADDRESS>wrote:
A little early but will we be able to submit custom extractors for considerations as well or rather not?

Reply to this email directly or view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftBigData%2Fusql%2Fissues%2F7%23issuecomment-153948913&data=01|01|mwinkle%40microsoft.com|ab7ba562983844cd6cdd08d2e5955a24|72f988bf86f141af91ab2d7cd011db47|1&sdata=mz2a93fbwBp6mnwVAAzz5KqOrLvfGpue7dIFCbP67Fw%3D.

Sounds great, I've put them in a seperate repo for now as I need to provide more testing first.


sokol-app: WinMain cmdline args using __argc & __argv

WHAAAT? How?!? Why didn't anybody tell me about this in the last 20 years?

Thanks btw :)


Close the opened document

Create a method to close and free the resources os the current renderized document.
I can`t exclude the pdf file after load in the pdfviewer. (this file is being used by another process).

To really free the resources, i have to use the method dispose of the PDFViewer and the Renderer, like this:
pdfViewer.Document?.Dispose();
pdfViewer..Renderer.Document?.Dispose();
Would be correctly run the dispose method of Document inside the renderer, when the dispose method of the Document inside the PDFViewer is called?

I have encountered the same problem, how did you solve it?

To close the document on demand, i used:
pdfViewer1.Document?.Dispose();
pdfViewer1.Renderer.Document?.Dispose();
Also, I put this code on the form_closing event like this:
private void frmIncluirF_FormClosing(object sender, FormClosingEventArgs e)
{
if (!e.Cancel)
{
pdfViewer1.Document?.Dispose();
pdfViewer1.Renderer.Document?.Dispose();
}
}

Thank you. I'll try.

@pedrohas2000
I tried, but I didn't solve it.

This really should solve the issue of the PDF document being kept open.
Please note that pdfViewer1.Document and pdfViewer1.Render.Document always refer to the same document. You only have to dispose one.
The PdfiumViewer control does not dispose the PdfDocument itself. This is expected behavior and e.g. the same as what the built in .NET control PictureBox does. If you open an image from file using that control, it will also not close it when the control is disposed. As such you need to make sure that you dispose the PdfDocument yourself.
The advise is:

Whenever you assign the Document property, make sure that you Dispose whatever's there before you assign it;
When you close e.g. the form, make sure you Dispose the contents of the Document property;
If none of these are possible for you, or you need to be able to delete the PDF document before the control/form is closed, you can also load the PDF document into memory like so:

pdfViewer1.Document = PdfDocument.Load(new MemoryStream(File.ReadAllBytes(form.FileName)));

Please note that this should solve your issue. PdfiumViewer does not keep a reference to the PdfDocument or file in any other place. Properly closing the PdfDocument instances you create should solve your issue.


feat: support ng6

Closes #51
ATM ngrx is on a beta release to support ng6, for that reason I fixed the perDeps to the latest beta version.
@amcdnl would you mind taking a look? 😃

Thanks for the ng6 support, I was planning to do exactly the same this evening. Instead I tested your branch, seems to work fine 👍


++![WATCH@LIVE]UPDATES=] AEW All Out 2024 LIVE Ｂｒｏａｄｃａｓｔ Ｆｒｅｅ ＯＮ Ｔｖ Ｃｈａｎｎｅｌ 07． ０9． ２０２４

+AEW All Out 2024 live updates: Full card, updates, results>!Here's Way To Watch 024 AEW All Out fight tonight? card, matches, start time, PPV preview, date, location, match card, wrestlers..All Elite Wrestling is going All Out three weeks removed from All In. AEW stars performed for tens of thousands at Wembley Stadium in London earlier this month and now make the trip to Illinois for All Out, one of their "big four" pay-per-views, on Saturday. After finally earning the AEW world title in England, Bryan Danielson is right back to work. Danielson is set to defend his title against TNT champion Jack Perry, who attacked him on AEW Dynamite after his title win.
GO LIVE==>>> CLICK HERE TO WATCH LIVE
STREAMING==>>> CLICK HERE TO WATCH LIVE
AEW’s Labor Day Weekend tradition, All Out, is getting a bit of a late start this year, bumped a week due to All In. That doesn’t make it any less exciting of a card, though: a rare AEW Steel Cage Match will take place, Bryan Danielson makes his first World Title defense, and a lot more from the Now Arena in Chicagoland. Get caught up to speed with everything you need to know about the show, as well as predictions for every match from our esteemed panel of experts:
AEW All Out 2024 date, start time
AEW All Out will air live on Saturday, September 7, 2024 from the Now Arena in Hoffman Estates, IL. It will begin at 8pm ET.
AEW All Out 2024 card and predictions
Will Ospreay (c) vs. Pac for the AEW International Championship
Darius: I’m a big fan of chaos (the concept, not the stable), so I’d be super down for Pac to undo everything MJF and Ospreay did at Wembley and just win the belt here. Pac is a stellar singles champion, and as happy as I am to watch him get high-profile matches, I’m a little tired of watching him lose big one-on-one encounters and only find success in the trios division. Unfortunately, Pac’s last run with a singles belt was as the simultaneous International and Trios Champion, so I highly doubt that they’re running it back. This is guaranteed to be one of the two best matches of the night, and it’s likely going to lead to matches that involve both members of this match and Ricochet, so I can’t complain too much. Still, as a long-time Pac guy, it sucks that the odds are heavily against him again.
Winner: Will Ospreay
Patrick: This match should be insane, but yeah, I agree with Darius. Pac isn’t walking out the winner here. Ospreay has all the momentum in the world and Pac seems busy awkwardly sliding into the Blackpool Combat Club without really acknowledging it.
Winner: Will Ospreay
Willow Nightingale vs. Kris Statlander (Chicago Street Fight)
Darius: This one’s a tough one, and I think the fact that it’s not for Willow’s CMLL title makes it even harder to guess. Since Stat’s heel turn, Willow and Stat are 1-1, with Willow winning in the Owen and Stat winning a shot at the Willow’s CMLL World Women’s Championship. If this was the match for Willow’s belt, Stat would be losing, 1,000%. Now that it’s non-title, I think back to Moxley vs Takeshita from Double or Nothing and I think, “Hey, Willow might still win this.” With that impending Women’s Championship match happening in Mexico, though, I think Kris is going to beat Willow silly and win this one for the bad guys.
Winner: Kris Statlander
Patrick: I like Stat and Stoke, but I think they need to start building a little more momentum than just being a funny combo. The fact that the match is non-title opens up the possibility of Willow losing, and I think that’s exactly what’s going to happen.
Winner: Kris Statlander
MJF vs. Daniel Garcia
Darius: Unlike with Pac, where I’m disappointed to see him lose but otherwise accept the situation, I just cannot accept a reality where Garcia loses this match. MJF can take a loss; he’s not going anywhere, and he can be heated back up with one promo. I’m not saying Garcia is done for good if he loses a match against the rarely losing MJF, but I AM saying that Garcia is a bit of a goober for the foreseeable future if he can’t pull this one off. Of course, there’s always a chance that MJF cheats to win and this feud extends to a later date (for example, both of these New York boys could certainly go crazy at Grand Slam in a few weeks), but Garcia’s had all this time to stew, and he missed wrestling at All In for the second year in a row. I think giving him a statement win at All Out would be a smart move.
Winner: Daniel Garcia
Patrick: Garcia really needs this win, especially since the feud has kinda started and stopped due to AEW’s hectic PPV schedule around this time of year. However, I wouldn’t be surprised if this builds into a longer feud with MJF taking the first win and Garcia getting him back at say, Dynasty or Full Gear. I say MJF cheats out a win here and the story continues.
Winner: MJF
Mercedes Moné vs. Hikaru Shida for the TBS Championship
Darius: I definitely think Mercedes is winning, but unlike Pac where I’m just bummed to see him lose, I actively want Shida to win. I think Shida should have all of the belts. When Shida isn’t on screen, Stokely Hathaway should be asking, “Where’s Shida?” She’s recently started calling herself the ace of AEW’s women’s division, and I think that’s true, which is also why I think she’s a fine choice to beat Mercedes for the TBS Championship. I’m not sure when it’s the RIGHT time to take Mercedes’s championship from her, but it’s not like she’d never hold AEW gold again. Let Shida win the belt, Tony! Anyways, Shida’s not winning.
Winner: Mercedes Moné
Patrick: This totally feels like an apology match after whatever Moné/Baker was. It should be a great contest that finally lets Mercedes show her in-ring chops to the AEW crowd, but I would be absolutely shocked if Shida won here. I do think she sounded more convincing than ever on Dynamite this past week, though, so hopefully this is the start of good things for Shida.
Winner: Mercedes Moné
Kazuchika Okada (c) vs. TBD vs. TBD vs. TBD for the AEW Continental Championship
Darius: Okada is winning this, but I have two other thoughts to add to this. First, Okada and Takeshita in the ring is going to be magical, even if it’s not the focus of the match. Second, isn’t the AEW Continental Championship the only one with, like, a REAL gimmick? It’s built for singles matches with no managers, 20-minute time limits, and huge fines for anyone who interferes. Why is this belt being defended in a match that inherently doesn’t follow Continental Crown rules? Once the rules are stripped away, what keeps this from being anything more than the third nondescript midcard belt? Now, if Takeshita wins, ignore every complaint I’ve made. However, I don’t foresee that happening; I just see myself moping about the loss of AEW’s one stand-out midcard belt on Discord for a few months.
Winner: Kazuchika Okada
Patrick: Yeah, Okada ain’t losing this. Bitch.
Winner: Kazuchika Okada
Bryan Danielson (c) vs. Jack Perry for the AEW World Championship
Darius: Jack Perry is not going to retire Bryan Danielson, but he sure is going to try. The funny thing about Jack Perry is that, even if he didn’t always have the character down, he was always a stupendous wrestler. New Japan gave him an edge, and the Elite storyline gave him a real character as the Scapegoat, and I think now’s as good a time as any to give him an amazing match with the best wrestler in the world. Again, he is NOT going to retire Bryan Danielson, but the threat of him doing so should make for some high-stakes drama.
Winner: Bryan Danielson
Patrick: I’m a little annoyed that Perry is Danielson’s first challenger for the World Title. It gives me flashbacks to WWE’s Daniel Bryan coming out of retirement to feud with….Big Cass. No offense to Perry – I’m actually starting to turn the corner with him and enjoy his work, but he is just not even in the same league as the American Dragon.
Winner: Bryan Danielson
Swerve Strickland vs. “Hangman” Adam Page (Lights Out Steel Cage Match)
Darius: I’ve thought hard about this one because this is the story I’m the most invested in throughout all of wrestling. I know that, whatever happens in this match, it has to further — not end — the story. That’s how I landed on the cowboy. If Swerve won this, he’d have 3 wins, 0 losses, and one draw with Hangman, excluding the triple threat match they both lost, and while I think that another loss would keep the fire burning within Hangman, I think Hangman winning here continues the thread from Wednesday: the shoe is on the other foot. Hangman has done the most despicable thing (or the most recent despicable thing) between the two, and it made Swerve look anguished. It’s the inverse of Full Gear 2023, as now Swerve is the one I imagine being too blinded by anger to capitalize and get the big win. Swerve is going to lose this match, and it’s going to keep the fire burning within him, much like the fire that burns in Hangman and burned down Swerve’s House.
Winner: “Hangman” Adam Page
Patrick: Completely agree with Darius here for nearly every reason. Hangman needs a win in this feud, and I think Swerve will be blinded by rage to the point where he can’t focus on securing the victory. Either way, a Steel Cage match is a rare treat in AEW, and I can’t wait to see these two kill each other.


WIFI_MODE_NULL is no longer supported

Environment

Development Kit: ESP32-Wrover-Kit
Kit version (for WroverKit/PicoKit/DevKitC): v1
IDF version: a2556229aa6f55b16b171e3325ee9ab1943e8552
Development Env: make
Operating System: Linux
Power Supply: USB

Problem Description
WIFI_MODE_NULL as documented here http://esp-idf.readthedocs.io/en/latest/api-guides/wifi.html#wi-fi-mode doesn't seem to be supported anymore.
Expected Behavior
Calling esp_wifi_set_mode(WIFI_MODE_NULL) should work and then esp_wifi_get_mode(&mode) should return WIFI_MODE_NULL.
Actual Behavior
esp_wifi_set_mode(WIFI_MODE_NULL) results in a warning:
W (204) wifi: Do not support NONE mode any more!

and it doesn't disable the STA or AP if it's enabled.

Thanks for the link!  It seems I wasn't able to search previous issues very well...


Why is the VerifyMessage method no longer available?

Hi! I'm following the Guid Programming The Blockchain in C#! But in Proof of ownership as an authentication method section I noted that VerifyMessage() method no longer available. Is there any alternative to this method? Thanks!!!
var message = "I am Craig Wright";
var signature = "IN5v9+3HGW1q71OqQ1boSZTm0/DCiMpI8E4JB1nD67TCbIVMRk/e3KrTT9GvOuu3NGN0w8R2lWOV2cxnBp+Of8c=";

var address = new BitcoinPubKeyAddress("1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa", Network.Main);
bool isCraigWrightSatoshi = address.VerifyMessage(message, signature);

Console.WriteLine("Is Craig Wright Satoshi? " + isCraigWrightSatoshi);

Closing this, but long story short, I removed the feature https://github.com/MetacoSA/NBitcoin/issues/1107


Content Widget content push

Hi,  I was curious if content widgets can be configured to push text. for example, I want to insert a snippet inline with my code and I want it to push all my code over instead of simply rendering on top.
If this is not possible with content widgets could someone point out a way this would be possible?
I've tried view zone's but they don't see to have a feature to change width. since I want to render my widget inline with the code, I cant have a whole line. I want to have something like test("random string"  ), when I try doing this with simple content widget's they render on top thus hiding the code beneath.

This is possible with decorations:
You can run it at https://microsoft.github.io/monaco-editor/playground.html#interacting-with-the-editor-line-and-inline-decorations

js:

var jsCode = [
	'"use strict";',
	'function Person(age) {',
	'	if (age) {',
	'		this.age = age;',
	'	}',
	'}',
	'Person.prototype.getAge = function () {',
	'	return this.age;',
	'};'
].join('\n');

var editor = monaco.editor.create(document.getElementById("container"), {
	value: jsCode,
	language: "javascript"
});

var decorations = editor.deltaDecorations([], [
	{ range: new monaco.Range(7,7,7,24), options: { afterContentClassName: 'inlinedec' }},
]);

CSS:

.inlinedec::after {
    content: '[[hello, I am some random content]]';
    color: darkgreen;
    background: yellow;
}

Interesting, I never knew you could do this with CSS. Thanks for the reply. much appreciated.

@alexandrudima That trick has been working great for me lately but I can't seem to find a way to have onclick functionality. Do you guys have any ways of detecting a click on decorations? I have thought up a workaround where I could have a decoration where the content is an X amount of spaces then place a content widget in that spot and then I have direct access to the DOM Element, thought I would ask before trying to write something like that.


Remove experimental from terminal image support

Follow up from https://github.com/microsoft/vscode/issues/182443
Ideally before we do this the following will be done:

[ ] xterm-addon-image is moved into the xterm.js core codebase. This is important because the addon uses internal APIs which are easy to break between versions, if it's in the core codebase we can strongly type the internal API usage. https://github.com/jerch/xterm-addon-image/issues/49
[x] Documentation added to vscode-docs.
[ ] Serialization support is implemented in the xterm-addon-image. See https://github.com/xtermjs/xterm.js/issues/614#issuecomment-1490098983 and https://github.com/jerch/xterm-addon-image/pull/48. This isn't critical but a nice to have, we could document this limitation on the docs website.

This was done


[VC] Fix a nulltpr crash

PR #745 introduces a bug such that the nodeNameToCluster map is mistakenly removed. This change fixes it.

/lgtm
/approve


fix(copy-tex): Use JS (instead of CSS) to select full equation, solving display glitches

What is the previous behavior before this PR?
When selecting a subrange of a KaTeX equation, we currently use user-select: all to ensure that the entire equation is selected, which is needed to get the tex code correctly.
I found this behaviour to be unstable on Chrome (not just on Safari, like mentioned in the README), and I would often get a partial selection, leading to strange HTML content:
https://user-images.githubusercontent.com/6933510/159169941-cf4aaf8e-bc40-4182-af40-0aa0588dc5ab.mov
What is the new behavior after this PR?
This PR uses JS to guarantee that when a subrange of an equation is selected, the parent equation is used for the copying logic. We use .closest('.katex') to find this parent.
When the selection is not fully contained inside a katex equation element, the old behaviour is used, which was working great!
This means that the user-select: all class (and in fact, the entire CSS file), can be be removed 🎉  This fixes the display bugs:
https://user-images.githubusercontent.com/6933510/159170237-08f5ae44-b76b-48e1-bd5c-c4d039a0f150.mov
Removing the CSS file should not be breaking, as importing it from a future version will just give a 404, which is fine. (Right?) If not, we can put the file back with empty contents.
Let me know what you think!

Looks great, thanks for the help!

Ooh and an instant release after the merge, that's awesome! 🌟

Hi @fonsp (contributor) and @edemaine (approver), curiously to find out that this PR is made a long time ago.
Currently the file is written in flow (I guess?), but the file is obviously not a valid js file for most browsers and it's publishing to npm as-is.
Can anyone try to fix it by compiling it to a standard JS file when publishing?
See main branch content and you will get what I am talking:

https://github.com/KaTeX/KaTeX/blob/main/contrib/copy-tex/copy-tex.js
https://github.com/KaTeX/KaTeX/blob/main/contrib/copy-tex/katex2tex.js

related issue https://github.com/KaTeX/KaTeX/issues/3948


support for cluster clients via zookeeper

Ok, to be honest i meant to have this pull request locally first, but well :))
What i've added here:

ability to use akka.cluster.client.ClusterClient that would resolve it's initial-contacts from zookeeper
integration tests to check if the whole thing works (for both seeds and clients)

what works:

the code for connecting to zookeeper is shared across seeds and clients - in theory all exhibitors, authentications etc. should Just Work ™

gotchas:

the library has an extra dependency to akka-cluster-tools in order to be able to use ClusterClient code

Ok, to be honest i meant to have this pull request locally first, but well :))
What i've added here:

ability to use akka.cluster.client.ClusterClient that would resolve it's initial-contacts from zookeeper
integration tests to check if the whole thing works (for both seeds and clients)

what works:

the code for connecting to zookeeper is shared across seeds and clients - in theory all exhibitors, authentications etc. should Just Work ™

gotchas:

the library has an extra dependency to akka-cluster-tools in order to be able to use ClusterClient code

LGTM 👍

@szimano let me know when you're all done here and I'll merge

I’m done :)
Implementing zk-based auto-downing of cluster nodes now, but i’ll send it in a separate PR.

@szimano just pushed a new 0.1.10-SNAPSHOT to oss.onatype containing this PR's commits.

Sweet


rake pull fails

I've built my db but when testing the rake pull command I get the following error
** Execute pull
*** update event fixtures...
update event >>World Cup Quali Africa 2014<< (world.quali.africa+2014)
  using dlbase >>https://raw.github.com/openfootball/world-cup/master/2014<<
   downloading source (1/3) >>https://raw.github.com/openfootball/world-cup/master/2014/africa_i.txt<< ...
*** error - fetch HTTP - 404 Not Found
   importing/reading source...
rake aborted!
NoMethodError: undefined method `read_fixtures_worker' for #<SportDb::GameReader:0x007fcefccf2e48 @include_path="/tmp">
/Users/ryan/.rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/sportdb-1.8.23/lib/sportdb/readers/game.rb:53:in `read_fixtures_from_string'

@RyanMacG  Not sure if you're still interested. The "new" way is to git for updates - no need to rebuild the update system. Again thanks for reporting. The issue is closed now. Cheers.

@geraldb Thanks for the update


Cannot send using 2nd sim slot

When sending using the 1st sim slot, the code bellow works.
SmsSender sender = new SmsSender();
SimCardsProvider provider = new SimCardsProvider();
card = await provider.getSimCards();
SmsMessage message = new SmsMessage("address", "content");
sender.sendSms(message, simCard: card.first);

However, when using card.last, in order to send via the 2nd sim slot like this:
sender.sendSms(message, simCard: card.last);
I always get this error.

E/flutter ( 6443): [ERROR:flutter/shell/common/shell.cc(181)] Dart Error: Unhandled exception:
E/flutter ( 6443): PlatformException(#01, message state change error, null)
E/flutter ( 6443): #0      _rootHandleUncaughtError. (dart:async/zone.dart:1112:29)
E/flutter ( 6443): #1      _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
E/flutter ( 6443): #2      _startMicrotas

I am testing using Samsung Galaxy J7 Prime (SM-G610Y) with android version 6.0.1.

Are you using the function onSmsDelivered?

I've pushed a fix, this should be good now

Are you using the function onSmsDelivered?

No. I am not using that function.

I've pushed a fix, this should be good now. Reopen if not

I've tested it and still messages are not sent via 2nd sim slot. I am getting the following error messages and incorrect message.onStateChanged saying the SMS was sent.

D/flutter_sms(21885): Sent result: SmsManager.RESULT_ERROR_GENERIC_FAILURE
I/flutter (21885): SMS is sent!`

You have this error because you're second sim card cannot send SMS

I see. It seems to just preferring to send with a particular sim card, even if I try to switch the default sim for text. It will find it and send it with sender.sendSms(message, simCard: card.first); even if I put it on either slot 1 or slot 2.
I then tried using other sim cards without the preferred one, the same message appears and now I  cannot send on both  sender.sendSms(message, simCard: card.first); or  sender.sendSms(message, simCard: card.last);:

D/flutter_sms(21885): Sent result: SmsManager.RESULT_ERROR_GENERIC_FAILURE
I/flutter (21885): SMS is sent!`

Not sure how this is still happening, since all sim cards work perfectly fine if I do not use an a simcard parameter in sender.sendSms(message);

Is the address valid?

I can't find where is the issue, if I found how to fix I will ping you


ToTestTests.cs:449: When shared object is used several...

The puzzle 60m-99c1dd43 from #60m has to be resolved:
https://github.com/DenisZhukovski/ObjectToTest/blob/058cb86f09ce22b35757fb7f6d2dda0ef7608e01/tests/ObjectToTest.UnitTests/ToTestTests.cs#L449-L449
The puzzle was created by @DenisZhukovski on 08-Dec-22.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 60m-99c1dd43 has disappeared from the source code, that's why I closed this issue.


zong0jie

This work is very good and I want to use it in my project. However I find that here may have error when I want to copy or move files in hdfs.
So I modify the HadoopFileSystem.java and make it works.
I would like to know whether the work is useful.

@zong0jie thanks a lot for your interest and I'm glad you want to be part of this project :)
I'm analyzing your PR. Will make FB soon.

Thanks.

Thank you for the merge. If you have  some other plan which you may not have enough time, maybe you can let me know, I think I can do something for you.
It's the first time I join an open source project, so please point my error at anytime.


use field-defined primary_key for default has_ reference

Currently, when using has_many or has_one, the default for the references: option is determined entirely by the @primary_key value. This doesn't work for primary_key(s) that are defined by the primary_key: field option.
Example of when a default references: could default to the schema primary_key but isn't.
defmodule MyApp.Schema do
  defmacro __using__(_) do
    quote do
      use Ecto.Schema
      @primary_key false
    end
  end
end

defmodule MyApp.Post do
  use MyApp.Schema
  schema "posts" do
    field :id, Ecto.UUID, autogenerate: true, primary_key: true
    has_many :comments, MyApp.Comment
    # ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ requires^, references: :id
  end
end

defmodule MyApp.Comment do
  use MyApp.Schema
  schema "posts" do
    field :id, Ecto.UUID, autogenerate: true, primary_key: true
    belongs_to :post, MyApp.Post
  end
end

There is also an example in the tests, modified in this PR where the has_many references: is defaulted and maybe shouldn't be, given the schema has multiple primary keys. Luckily, since it's likely not a very frequent scenario and it's also a compile time check, upgrading Ecto and it "breaking" would be unlikely, a quick find, a quick fix, and have no possibility of effecting released code.
My apologies that I'm not quite sure of the preferred way to add a test for a compile time check to this PR

Hi @dallincrane, thanks for the PR! :heart:
This difference is intentional as the approach you propose has some issues. For example, it is ordering dependent. If the primary key fields are defined after, then it won't affect relationships. Another issue, as you noted, is composite keys. Therefore I have pushed a commit that makes this explicit in the docs. If there are other places in the docs you would rather change, a PR in the area is also welcome.


Taking lots of time to train the data and its not showing any messages or logs

Rasa NLU version: 0.11.4
Used backend / pipeline: spacy_sklearn
Operating system: osx
Issue:
Hi all,
I am new in to machine learning and chat bots. I have installed the installed rasa core and rasa nlu and read the tutorials. After experimenting with the basic examples, I started to create a new data set from scratch and experiment on that. The issue I am facing now is training time.
I gave 35000+ examples with 3 indents and 2 entities.
It has been running for 8 hours continuously with 99% CPU usage and 1 to 2GB RAM Usage.
The data I generated is using Chatito
Is there anything I can do to increase the training performance.
Content of configuration file (if used & relevant):
{
  "pipeline": "spacy_sklearn",
  "path": "./models",
  "data": "data.json"
}

After one more hour the memory usage increased to 2.2 GB and Compressed memory which was 0 earlier is now 1.88 GB

That is a lot of training data! I would start with some small experiments, because I don't think you'll need that many examples for 3 intents and 2 entities. Start with 100 (should train in a few seconds) and work your way up!

ok let me try.

I tried with 200 data for 3 indents and 2 entities. But the entities are not extracting from the result. If i give the exact data as in the training set its working. In my case one of the entity is name  and second entity is amount. Both can be dynamic I cant train all the possible names. What will be appropriate method to train such data.

I also tried with 800 data. No difference.

Could you post your training data in a zip file so we can take a look?

I generated the data using Chatito, This is the DSL for generating the dataset.
%[initTransactionAmountBeneficiary]
    ~[can] ~[please]? ~[send] @[beneficary] ~[currency]? @[amount]
    ~[can] ~[please]? ~[send] @[beneficary] @[amount] ~[currency]?
    ~[can] ~[please]? ~[send] @[beneficary] @[amount]

    ~[please]? ~[send] @[beneficary] ~[currency]? @[amount]
    ~[please]? ~[send] @[beneficary] @[amount] ~[currency]?
    ~[please]? ~[send] @[beneficary] @[amount]

    ~[want]? ~[send] @[beneficary] ~[currency]? @[amount]
    ~[want]? ~[send] @[beneficary] @[amount] ~[currency]?
    ~[want]? ~[send] @[beneficary] @[amount]

    ~[can] ~[please]? ~[send] ~[currency]? @[amount] to @[beneficary]
    ~[can] ~[please]? ~[send] @[amount] ~[currency]? to @[beneficary]
    ~[can] ~[please]? ~[send] @[amount] to @[beneficary]

    ~[please]? ~[send]  ~[currency]? @[amount] to @[beneficary]
    ~[please]? ~[send]  @[amount] ~[currency]? to @[beneficary]
    ~[please]? ~[send] @[amount] to @[beneficary]

    ~[want]? ~[send] ~[currency]? @[amount] to @[beneficary]
    ~[want]? ~[send] @[amount] ~[currency]? to @[beneficary]
    ~[want]? ~[send]  @[amount] to @[beneficary]

%[initTransactionAmount]
    ~[can] ~[please]? ~[send] ~[currency]? @[amount]
    ~[can] ~[please]? ~[send] @[amount] ~[currency]?
    ~[can] ~[please]? ~[send] @[amount]

    ~[please]? ~[send] ~[currency]? @[amount]
    ~[please]? ~[send] @[amount] ~[currency]?
    ~[please]? ~[send] @[amount]

    ~[want]? ~[send] ~[currency]? @[amount]
    ~[want]? ~[send] @[amount] ~[currency]?
    ~[want]? ~[send] @[amount]

    ~[can] ~[please]? ~[send] ~[currency]? @[amount]
    ~[can] ~[please]? ~[send] @[amount] ~[currency]?
    ~[can] ~[please]? ~[send] @[amount]

    ~[please]? ~[send]  ~[currency]? @[amount]
    ~[please]? ~[send]  @[amount] ~[currency]?
    ~[please]? ~[send] @[amount]

    ~[want]? ~[send] ~[currency]? @[amount]
    ~[want]? ~[send] @[amount] ~[currency]?
    ~[want]? ~[send]  @[amount]

%[initTransactionBeneficiary]
    ~[can] ~[please]? ~[send] @[beneficary]
    ~[please]? ~[send] @[beneficary]
    ~[want]? ~[send] @[beneficary]

~[want]
    i want to
    i need to

~[send]
    send
    transfer
    give

~[please]
    pls
    please

~[can]
    can you

@[beneficary]
    neeraj
    neeraj das
    niju
    ebrahim k k
    ajumell
    dasbingo

~[currency]
    Rs
    Rupees
    INR

@[amount]
    100
    1000
    200
    2000
    thousand
    ten thousand
    one lakh two hundred

When I updated the config the data named entity recognition works well. This is the new config file.
{
  "pipeline": [
    "nlp_spacy",
    "tokenizer_spacy",
    "intent_entity_featurizer_regex",
    "intent_featurizer_spacy",
    "ner_crf",
    "ner_spacy",
    "ner_synonyms",
    "intent_classifier_sklearn"
  ],
  "path": "./models-03",
  "data": "data-03.json"
}

looks like your issue is solved then right? that config file looks good to me. ner_duckling also works very well for numbers, if you're still having issues with that

Thanks @akelad, I will try that also.


Add FileLineMap data structure

Use as underlying data structure for Spectra.
Also, add __len__ to both FileLineMap and FileLineSet.

This is no longer needed.

This is no longer needed.

No longer needed.

This is no longer needed.


fix: reorder cleanupAtContainer code

Closes https://github.com/kentcdodds/react-testing-library/issues/326

What:

Why:

How:

Checklist:

[ ] Documentation added to the docs site
[ ] Tests
[ ] Typescript definitions updated
[ ] Ready to be merged

[ ] Added myself to contributors table

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


invalid predicate "rename:located_in" showing up

This issue was reported by @maximusunc via RTX Issue 1828 (thank you @maximusunc).
Apparently, in predicate-remap.yaml, there are three UBERON relations that are incorrectly mapped to rename:located_in:
https://github.com/RTXteam/RTX-KG2/blob/85bf397963c48a11cbb151c686fb7ab3401836f0/predicate-remap.yaml#L4540-L4551
they should be mapped to biolink:located_in, I think.

Hi @acevedol we should also scan the predicate-remap.yaml file to see if any similar bugs are lurking, i.e., any other cases where the predicate starts with rename: (but with a different predicate label instead of located_in) instead of the correct predicate CURIE prefix, biolink:.

I corrected the three invalid predicates on the issue-199 branch. There do not appear to be any additional invalid predicates.

@saramsey What is the protocol for a high priority bug like this? Should I rebuild ASAP?

Can we close this out?  Is it fixed in the production RTX-KG2 service?

@saramsey Yes, thank you for bringing this up. This was fixed in 2.7.6, I believe. I checked against neo4j and it shows no results for the relationship "rename:located_in" but several results for "biolink:located_in"


no signal.SIGPIPE on windows

Platform: Windows 7
$ python
Python 3.5.1 |Anaconda custom (64-bit)| (default, Feb 16 2016, 09:49:46) [MSC v.1900 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

$ git rev-parse HEAD
9e31a4624c0884c7169733adafa22aca87ffc6af

$ gl history
✘ Some internal error occurred
  ➜ If you want to help, see http://gitless.com for info on how to report bugs and include the following information:

  0.8.4

  Traceback (most recent call last):
    File "D:\Python\Anaconda\lib\site-packages\gitless-0.8.4-py3.5.egg\gitless\cli\gl.py", line 82, in main
      return SUCCESS if args.func(args, repo) else ERRORS_FOUND
    File "D:\Python\Anaconda\lib\site-packages\gitless-0.8.4-py3.5.egg\gitless\cli\gl_history.py", line 50, in main
      helpers.page(tf.name, repo)
    File "D:\Python\Anaconda\lib\site-packages\gitless-0.8.4-py3.5.egg\gitless\cli\helpers.py", line 74, in page
      from signal import signal, SIGPIPE, SIG_DFL
  ImportError: cannot import name 'SIGPIPE'

oops, sorry about that. 38457cc357e5d86f4232b12230fe5228cfd7cd35 introduced the bug (I wish travis ci had an option to run tests on Windows).

I don't know if there would be unintended side effects, but it might be okay to just introduce a platform-specific 'fix':
if sys.platform != 'win32':
  from signal import signal, SIGPIPE, SIG_DFL
  signal(SIGPIPE, SIG_DFL)

Yes, that would prevent the exception from happening. But I have to test if we need to do something in Windows to prevent the "broken pipe error" that occurs in Unix if we don't have that code. I'll look into it later tonight. In the meantime, since it seems you are installing Gitless from the repo, you can change the head to commit d0aabff3cd0c7cf466d4fe67d11c3a1a156d57a9 and reinstall.

d948e16a97a1aff2efdd09a92bb998e4e1041079


:Unable to generate responses, "XYZ is not a function"

Copilot Chat is unable to generate responses. I just get errors like this:
e.request.message.startsWith is not a function
e.split is not a function

I have Copilot Chat extension v0.12.2023120701 (pre-release). Same errors happen with Release version. The issue persists even after restarting VS Code and rebooting my machine. It was working earlier today.

VS Code Version:
Version: 1.85.0 (Universal)
Commit: af28b32d7e553898b2a91af498b1fb666fdebe0c
Date: 2023-12-06T18:18:04.614Z (1 day ago)
Electron: 25.9.7
ElectronBuildId: 25551756
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 23.1.0

OS Version:
MacOS Sonoma v14.1.1
Connected to 2-core 8 GB Codespace (Ubuntu 20.04.6 LTS)

Logs:

2023-12-08 03:53:30.440 [info] [gitExtensionService] Initializing Git extension service.
2023-12-08 03:53:30.671 [info] [gitExtensionService] Successfully activated the vscode.git extension.
2023-12-08 03:53:30.671 [info] [gitExtensionService] Enablement state of the vscode.git extension: true.
2023-12-08 03:53:30.671 [info] [gitExtensionService] Successfully registered Git commit message provider.
2023-12-08 03:53:30.991 [info] [auth] Logged in as TheOnlyZac
2023-12-08 03:53:32.041 [info] [chat] copilot token chat_enabled: true
2023-12-08 03:53:32.041 [info] [githubTitleAndDescriptionProvider] Initializing GitHub PR title and description provider provider.
2023-12-08 03:53:32.041 [info] [auth] Got Copilot token for TheOnlyZac
2023-12-08 03:53:32.921 [info] [auth] Logged in as TheOnlyZac
2023-12-08 03:53:32.927 [info] [chat] copilot token chat_enabled: true
2023-12-08 03:53:32.927 [info] [auth] Got Copilot token for TheOnlyZac
2023-12-08 03:53:34.529 [info] [asyncCompute] Failed to compute async parser based result: Error: Unrecognized language: makefile
    at y (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:5:9338)
    at E (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:178:1334)
    at Object.Xe (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:178:1905)
    at MessagePort.<anonymous> (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:180:2311)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:735:20)
    at exports.emitMessage (node:internal/per_context/messageport:23:28)
2023-12-08 03:53:34.530 [info] [asyncCompute] Failed to compute async parser based result: Error: Unrecognized language: makefile
    at y (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:5:9338)
    at E (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:178:1334)
    at Object.et (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:178:2326)
    at MessagePort.<anonymous> (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:180:2311)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:735:20)
    at exports.emitMessage (node:internal/per_context/messageport:23:28)
2023-12-08 03:53:34.531 [info] [asyncCompute] Failed to compute async parser based result: Error: Unrecognized language: makefile
    at y (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:5:9338)
    at E (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:178:1334)
    at Object.st (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:178:3497)
    at MessagePort.<anonymous> (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:180:2311)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:735:20)
    at exports.emitMessage (node:internal/per_context/messageport:23:28)
2023-12-08 03:53:34.535 [info] [asyncCompute] Failed to compute async parser based result: Error: Unrecognized language: makefile
    at y (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:5:9338)
    at E (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:178:1334)
    at Object.tt (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:178:2585)
    at MessagePort.<anonymous> (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:180:2311)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:735:20)
    at exports.emitMessage (node:internal/per_context/messageport:23:28)
2023-12-08 03:53:34.541 [info] [asyncCompute] Failed to compute async parser based result: Error: Unrecognized language: makefile
    at y (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:5:9338)
    at E (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:178:1334)
    at Object.rt (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:178:3238)
    at MessagePort.<anonymous> (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:180:2311)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:735:20)
    at exports.emitMessage (node:internal/per_context/messageport:23:28)
2023-12-08 03:53:34.544 [info] [asyncCompute] Failed to compute async parser based result: Error: Unrecognized language: makefile
    at y (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:5:9338)
    at E (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:178:1334)
    at Object.nt (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:178:2898)
    at MessagePort.<anonymous> (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/worker2.js:180:2311)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:735:20)
    at exports.emitMessage (node:internal/per_context/messageport:23:28)
2023-12-08 03:53:35.168 [info] [githubTitleAndDescriptionProvider] Successfully activated the GitHub.vscode-pull-request-github extension.
2023-12-08 03:53:35.168 [info] [githubTitleAndDescriptionProvider] Successfully registered GitHub PR title and description provider.
2023-12-08 03:53:38.876 [info] [extension] TypeError: e.request.message.startsWith is not a function
    at /home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/extension.js:1046:80
    at Array.map (<anonymous>)
    at Object.turnFilter (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/extension.js:1046:54)
    at yi.buildPrompt (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/extension.js:608:1597)
    at Zy._provideResponseWithProgress (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/extension.js:858:798)
    at Zy.provideResponseWithProgress (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/extension.js:856:4103)
    at s.x (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/extension.js:868:1022)
    at f.$invokeAgent (/vscode/bin/linux-x64/af28b32d7e553898b2a91af498b1fb666fdebe0c/out/vs/workbench/api/node/extensionHostProcess.js:141:128938)
2023-12-08 03:56:57.376 [info] [extension] TypeError: e.request.message.startsWith is not a function
    at /home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/extension.js:1046:80
    at Array.map (<anonymous>)
    at Object.turnFilter (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/extension.js:1046:54)
    at yi.buildPrompt (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/extension.js:608:1597)
    at Zy._provideResponseWithProgress (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/extension.js:858:798)
    at Zy.provideResponseWithProgress (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/extension.js:856:4103)
    at s.x (/home/codespace/.vscode-remote/extensions/github.copilot-chat-0.12.2023120701/dist/extension.js:868:1022)
    at f.$invokeAgent (/vscode/bin/linux-x64/af28b32d7e553898b2a91af498b1fb666fdebe0c/out/vs/workbench/api/node/extensionHostProcess.js:141:128938)

Steps to Reproduce:

Use any feature that would prompt Copilot to respond (chat, /explain, etc)

Hm, so you have some invalid data in your chat history due to a bug. I fixed that bug in https://github.com/microsoft/vscode/pull/199581 so invalid history won't be saved anymore. However I realize that once the invalid history is there, you will continue seeing this until you clear the chat session (use the plus icon) so maybe I should do something to patch up the history.
Anyway, unblock yourself for now but using the + icon in the header to start a new chat session.

This has been out for awhile- not going to plan more changes here


[feat-1368][logminer]add enableFetchAll

Purpose of this pull request
Support oracle logminer historical + incremental data sync
Which issue you fix
Fixes #1368
Checklist:

[x] I have executed the 'mvn spotless:apply' command to format my code.

[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] New and existing unit tests pass locally with my changes.
[ ] I have checked my code and corrected any misspellings.
[ ] My commit is only one. (If there are multiple commits, you can use 'git squash' to compress multiple commits into one.)

@yanghuaiGit  @FlechazoW  please review it
新增enableFetchAll是否开启同步存量数据

获取要同步的表 (只能为单表，  不支持正测匹配多个表)
以ROW SHARE的方式锁定表

lock table xx IN ROW SHARE MODE

获取当前的SCN

select scn, seg_owner, table_name from v$logmnr_contents
	where seg_owner='%s' and table_name='%s' order by scn desc

对这个表， 生成create table ddl事件
释放锁

rollback

根据SCN号， select数据，转换成column row data

select * from xxx as of scn xxx

注意: 不支持断点续传，同步存量数据失败时，需要手动删除目标表


Unexpected difference between AbstractControllerTestCase's dispatch with POST and PUT

After setting up a restful controller and using dispatch to test the controller, I get unexpected differences using POST and PUT.
// PostController.php
namespace Application\Controller;

use Zend\Mvc\Controller\AbstractRestfulController;
use Zend\View\Model\JsonModel;

class PostController extends AbstractRestfulController {

    public function create($data) {
        return new JsonModel($data);
    }

    public function update($id, $data) {
        return new JsonModel($data);
    }
}

// PostControllerTest.php
namespace ApplicationTest\Controller;

use Zend\Test\PHPUnit\Controller\AbstractHttpControllerTestCase;

class PostControllerTest extends AbstractHttpControllerTestCase {

    public function setUp() {
        $appConfig = include 'config/application.config.php';
        $this->setApplicationConfig($appConfig);
        parent::setUp();
    }

    public function testCreateWithDispatch() {
        $this->dispatch('/application/post', 'POST', [
            'author' => null
        ]);
        $content = json_decode($this->getResponse()->getContent());
        $this->assertObjectHasAttribute('author', $content);
        $this->assertNull($content->author);
    }

    public function testUpdateWithDispatch() {
        $this->dispatch('/application/post/1', 'PUT', [
            'author' => null
        ]);
        $content = json_decode($this->getResponse()->getContent());
        $this->assertObjectHasAttribute('author', $content);
        $this->assertNull($content->author);
        // Failed asserting that '' is null
    }
}

Notice that in the create action, author is null, and the update action, author is an empty string. I was able to trace this issue back to #3916. It seems as though there is assumptions being made on how data is sent using GET, POST, and PUT. I suppose that wouldn't be a problem as long as there was consistency.

This issue has been closed as part of the bug migration program as outlined here - http://framework.zend.com/blog/2016-04-11-issue-closures.html


Dashboard > Page Search : Editing multiple properties results in Fatal Error

When trying to edit multiple pages in the Page Search the console returns this error:
Nesting level too deep - recursive dependency?
After some research I noticed that the issue was with a custom page attribute.
https://github.com/concrete5/concrete5/blob/03cf1b42f39bf218755e30cef330ab41f264363f/concrete/elements/attribute/editable_attribute.php#L17-L20
The getDisplayValue() function is called. In this case it does not return a string but an Object with a __toString function (which is of type Concrete\Core\Html\Object\Picture).
On line 20 the $lastDisplay and $display are compared using !=  which results in PHP comparing all object properties one by one. In this case recursion occurs which results in a fatal error.
I can think of two possible solutions. 1. The comparison should be on identity !== or 2. the result of the getDisplayValue function should always be of scalar type.

getDisplayValue ought to always return a value of the scalar type.


nixpkg-provided OpenBLAS seems completely broken

Describe the bug
Any program trying to use OpenBLAS seems to fail spectacularly.
To Reproduce
I made a reproduction repository here. Please see the README.
Roughly:
Steps to reproduce the behavior:

Write any program that uses libopenblas.so: I proved a trivial fortran program in the repro to avoid any FFI weirdness.
Try run it, get strange result or segfault.
Build your own libopenblas.so, run the exact same program with it instead (via LD_LIBRARY_PATH): get the expected result.

Expected behavior
No segfault, no strange behaviour.
Additional context
I have tried building the nixpkgs-defined OpenBLAS myself when I tried adding debug symbols and the result was the same: so perhaps it is not a hydra problem or anything like that but the definition problem.
Notify maintainers
@ttuegel
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 5.4.99, NixOS, 21.05.git.6739ee70216 (Okapi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.10`
 - channels(root): `"nixos-17.09.3269.14f9ee66e63"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

I have also tried on an Ubuntu bionic system with nix-provided OpenBLAS with the exact same result. I have initially found the issue on OpenBLAS 0.3.10. After updating to 0.3.13 (most recent) via newer nixpkgs, no improvement. The issue was initially found through a completely different program that was found to work well on MacOS, Ubuntu, Debian but failed with nixpkgs-provided OpenBLAS.
Maintainer information:
- openblas

What is your default integer size?

What is your default integer size?

I'm... not sure? I assume 64-bit? I don't think we're setting anything non-default anywhere... I suspect the code in the build expression:
  blas64 =
    if blas64_ != null
      then blas64_
      else hasPrefix "x86_64" stdenv.hostPlatform.system;

sets blas64 to true here... I could try explicitly changing it and see if that gives a different result.
Indeed if I do openblas.override { blas64 = false; } in the repro repository linked in the original issue, the code succeeds... I'm not sure what this means for me though...

Does this mean the default should just be 32-bit like the rest of the packaging world?

This is primarily a Fortran issue, which becomes a packaging issue: Fortran's default integer size is 32 bit (integer4) if not specified otherwise. This can be changed by using  the -fdefault-integer-8  compiler switch to select 64 bit. The BLAS/LAPACK and interfaces do not explicitly specify the type of integer, but it is traditionally assumed to be 32 bit (see also ILP64 vs. LP64: https://en.wikipedia.org/wiki/64-bit_computing).
The big problem is that the compiler can can not see what a library expects (and simply crashes at run time if mismatched, as you have noticed).
There are the following options to solve your problem:

Use openblasCompat instead of openblas to get a 32 bit interface.
Use the -fdefault-integer-8 switch to compile your program together with openblas.
Use the blas and lapack derivations. They are wrappers pointing to openblasCompat. Here you can check to the isILP64 attributes to make sure you are building against the right version (see also https://nixos.org/manual/nixpkgs/stable/#sec-overlays-alternatives-blas-lapack).

Hm, it seems the documentation at https://nixos.org/manual/nixpkgs/stable/#sec-overlays-alternatives-blas-lapack is wrong/out of date. It says:

The Nixpkgs attribute is openblas for ILP64 (integer width = 64 bits) and openblasCompat for LP64 (integer width = 32 bits). openblasCompat is the default.

which is not true:
  openblas = callPackage ../development/libraries/science/math/openblas { };

  # A version of OpenBLAS using 32-bit integers on all platforms for compatibility with
  # standard BLAS and LAPACK.
  openblasCompat = openblas.override { blas64 = false; };

Perhaps 32-bit used to be the default at some point...
For our case, I simply set openblas.override { blas64 = false; }; and this works for us (I suppose I should just say openblasCompat. I think we can close this in favour of #35208.
Thank you for the help.

Hm, it seems the documentation at https://nixos.org/manual/nixpkgs/stable/#sec-overlays-alternatives-blas-lapack is wrong/out > of date. It says:

The Nixpkgs attribute is openblas for ILP64 (integer width = 64 bits) and openblasCompat for LP64 (integer width = 32 bits). >> openblasCompat is the default.

The documentation is correct in the sense that openblasCompat is the default provider for the blas and lapack packages. The recommendation is to use blas and lapack instead of using the openblas/openblasCompat packages directly as they provide an easy switch mechanism (i.e. if you want to try MKL or some other implementation).


Fix logging for LoggingMetricsConsumer STORM-584

Currently the metrics.log file is always empty and it declared in the cluster.xml file whereas it should be in the worker one. The metrics end up in the log file which is not a huge issue but it would be cleaner to have them in a separate file, as originally intended.
This patch addresses this and makes so that there is one metrics file per worker, as per the other log files, which should address the issues mentioned in [https://issues.apache.org/jira/browse/STORM-584].

+1

+1

LGTM

+1

+1

+1


Support HTTP Byte Serving via Ranges header

Currently, if you have a <video> tag whose src is served through staticfile, seeking doesn't work. This can be fixed by supporting Byte Serving.

This would be awesome! :) If anyone wants to pick this up please let us know and we can try to help!

I'd like to pick this up. If I run into trouble I'll let you know.
Funnily enough, video playback doesn't work at all with staticfile, let alone seeking. Any video just refuses to play, either via firefox or via mpv. The same video works if played with firefox or mpv and if the video is hosted with an apache. I wonder if it's related ?
I will try to dig this up and come back with some news.

I suspect usage of X-Sendfile will fix this too.

@Cobrand on my end, video playback works fine (in Chrome), it's just seeking that doesn't work. (note if you don't set autoplay and/or controls in the <video> tag, you'll need to tell the video to play via context menu.

Turns out that I tested with mp4, and it doesn't work in iron at all (probably because . webm either works without seeking in mpv, or hangs in the middle for long videos (> 30s). So that's definitely our issue here.
For info, the difference between Iron and Apache :
Iron
HTTP/1.1 200 OK
Content-Length: 29271156
Content-Type: video/webm
Date: Mon, 06 Feb 2017 19:20:56 GMT

Apache
HTTP/1.1 200 OK
Accept-Ranges: bytes
Connection: Keep-Alive
Content-Length: 29271156
Content-Type: video/webm
Date: Mon, 06 Feb 2017 19:21:57 GMT
ETag: "1bea474-54227ffe25f38"
Keep-Alive: timeout=5, max=100
Last-Modified: Fri, 25 Nov 2016 22:54:07 GMT
Server: Apache/2.4.25 (Unix) PHP/7.1.1

So I dug a little bit into how this stuff works, and I have some questions.
Basically if you answer with the Accept-Range: bytes header, you must be able to receive and process the Range header (event though you can still ignore the Range header).
Basically a client can request things like these (one line = one different request) :
Range: bytes=0-
Range: bytes=200-
Range: bytes=200-1000, 2000-3000, 4000-

First one is dead simple: just send a "File" like we used to do.
Second one is less simple but feasible: Answer with the proper Content-Range, and offset the file by 200 bytes (from a File struct using a Bytes Iterator I guess)
Third one is way less simple, you have to answer something like this according to RFC 2046 :
Content-type: multipart/byteranges; boundary="xxironstaticfileboundaryxx"

--xxironstaticfileboundaryxx
Content-type: application/octet-stream;

200 to 1000 bytes here
--xxironstaticfileboundaryxx
Content-type: application/octet-stream;

2000 to 3000 bytes here...
--xxironstaticfileboundaryxx
Content-type: application/octet-stream;

4000 bytes to end of file here

--xxironstaticfileboundaryxx--

This is technically what we must answer, but unfortunately there is no proper way to answer a multipart body in Iron as of now, so for now I guess I'll pass.
I guess there might also be a way to only reply bytes 200 to 1000, but not only this isn't mentioned as allowed or forbidden in the RFCs, but I don't really know what to answer as well. Do we just answer as if only one range was asked, and we just set the Content-Length and Content-Range accordingly ?
For info, Apache will answer this to a Range: bytes=1000-2000, 3000-4000 request:
Content-Length: 2208
Content-Type: multipart/byteranges; boundary=beb42d06bc54e552

(2208 instead of 2000 is because the delimiter + "Content-type: video/webm" + "Content-range: bytes 3000-4000/29271156" are added as well, twice)
Since we can choose to ignore the "Range" header, I guess we can choose to ignore it when we got more than 1 range as well.
So yeah if someone knows If I can answer only bytes 1000 to 2000 for a request "Range: bytes=1000-2000, 3000-4000", that'd be great.

You could just ignore the range request if it's composed of multiple ranges for now.

Can someone have a look at PR #95 ?

I'm very excited to see this -- it turns a simple "serve this folder" webserver into something significantly more useful than python's equivalent, especially in the case of e.g. a home media server.

I totally forgot that I had a PR open about that ... I'll try to find some time to get this PR finally merged


The sadness of UWP

Is UWP dead?  If you exclude your own technology from your own documentation and your own product, I think it means it is dead

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e40fbe03-a099-3b24-4654-162103003d6a
Version Independent ID: 01e8c667-ed94-7054-758d-2399e879714a
Content: Use C/C++ libraries with Xamarin - Xamarin
Content Source: docs/cross-platform/cpp/index.md
Product: xamarin
Technology: xamarin-crossplatform
GitHub Login: @mikeparker104
Microsoft Alias: miparker

UWP is a product separate from Xamarin, though we offer an SDK that allows Xamarin user interfaces to render on UWP. Getting C or C++ to run on UWP is a separate issue to Xamarin's integration.
In our C/C++ documentation we have focused on the area of most concern to our customers - getting their libraries on Android and iOS with Xamarin. The community has contributed some help to use UWP on this issue thread. I hope that's useful for you also.