Colorized output in external pipelines

I'm using webpack as an external pipeline and am trying to get the output to maintain the colors that webpack outputs when it is run by itself.
I've found that the io from the Thread is read and logged here, but I'm not really sure where to look next.
Has anyone else had this issue and found a fix? Alternatively, could any of the maintainers point me in the right direction towards solving this issue?
Thanks!
Current

Desired

I have absolutely no idea how that stuff works. But happy to accept patches that can make this happen.

I dug into this more and I was wrong — Middleman/Ruby actually handles the colorized output perfectly. The issue was on the webpack side of things — the way it detects whether a terminal supports colorized output was returning false for the Thread being run in Middleman. To fix this, I was able to explicitly specify the stats: { colors: true } option.
Hope this helps someone else!

can confirm @jessepollak's suggestion still works as of June 2019...thanks!!


Make a minor release v0.14.0

Description
Since a fair amount of code has been added since the latest release v0.13.2, we should create a minor release v0.14.0 at some point.
It is not urgent though.

Done. https://github.com/flatcar-linux/mantle/releases/tag/v0.14.0


HBASE-22976 [HBCK2] Add RecoveredEditsPlayer

Make it so WALPlayer can replay recovered.edits files.
hbase-mapreduce/src/main/java/org/apache/hadoop/hbase/mapreduce/WALInputFormat.java
Allow for WAL files that do NOT have a startime in their name.
Use the 'generic' WAL-filename parser instead of the one that
used be local here. Implement support for 'startTime' filter.
Previous was just not implemented.
hbase-mapreduce/src/main/java/org/apache/hadoop/hbase/mapreduce/WALPlayer.java
Checkstyle.
hbase-server/src/main/java/org/apache/hadoop/hbase/wal/AbstractFSWALProvider.java
Use the new general WAL name timestamp parser.
hbase-server/src/main/java/org/apache/hadoop/hbase/wal/WAL.java
Utility for parsing timestamp from WAL filename.
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestRecoveredEdits.java
Export attributes about the local recovered.edits test file
so other tests can play with it.

New push updates doc.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
4m 19s
Docker mode activated.

_ Prechecks _

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

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

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

_ master Compile Tests _

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

+1 :green_heart:
mvninstall
4m  8s
master passed

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

+1 :green_heart:
spotbugs
3m 59s
master passed

_ Patch Compile Tests _

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

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

+1 :green_heart:
checkstyle
0m 27s
The patch passed checkstyle in hbase-common

-0 :warning:
checkstyle
1m 11s
hbase-server: The patch generated 1 new + 5 unchanged - 5 fixed = 6 total (was 10)

+1 :green_heart:
checkstyle
0m 20s
hbase-mapreduce: The patch generated 0 new + 0 unchanged - 15 fixed = 0 total (was 15)

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

+1 :green_heart:
hadoopcheck
19m 13s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1 3.3.0.

+1 :green_heart:
spotbugs
4m 36s
the patch passed

_ Other Tests _

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

54m 40s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/1/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux d169cd8532fc 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
master / a8c49a6463

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
94 (vs. ulimit of 30000)

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

_ Patch Compile Tests _

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

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

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

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

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

-0 :warning:
javadoc
0m 20s
hbase-common in the patch failed.

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

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

_ Other Tests _

+1 :green_heart:
unit
1m 44s
hbase-common in the patch passed.

-1 :x:
unit
153m 25s
hbase-server in the patch failed.

-1 :x:
unit
12m 20s
hbase-mapreduce in the patch failed.

205m 28s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / a8c49a6463

Default Java
2020-01-14

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-common.txt

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

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

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-common.txt

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

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

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

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/1/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-mapreduce.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/1/testReport/

Max. process+thread count
4621 (vs. ulimit of 30000)

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

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/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
0m 29s
Docker mode activated.

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

_ Prechecks _

_ master Compile Tests _

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

+1 :green_heart:
mvninstall
4m 53s
master passed

+1 :green_heart:
compile
2m 22s
master passed

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

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

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

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

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

-1 :x:
unit
19m 13s
hbase-mapreduce in the patch failed.

307m 46s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / a8c49a6463

Default Java
1.8.0_232

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/1/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-mapreduce.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/1/testReport/

Max. process+thread count
3122 (vs. ulimit of 30000)

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

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/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 39s
Docker mode activated.

_ Prechecks _

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

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

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

_ master Compile Tests _

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

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

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

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

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

_ Patch Compile Tests _

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

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

-0 :warning:
checkstyle
2m  6s
root: The patch generated 1 new + 9 unchanged - 20 fixed = 10 total (was 29)

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

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

+1 :green_heart:
hadoopcheck
19m 58s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1 3.3.0.

+1 :green_heart:
spotbugs
15m 46s
the patch passed

_ Other Tests _

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

87m 22s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/2/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle refguide

uname
Linux 186232dd1c2d 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
master / a8c49a6463

refguide
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/2/artifact/yetus-general-check/output/branch-site/book.html

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/2/artifact/yetus-general-check/output/diff-checkstyle-root.txt

refguide
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/2/artifact/yetus-general-check/output/patch-site/book.html

Max. process+thread count
137 (vs. ulimit of 30000)

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

_ Patch Compile Tests _

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

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

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

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

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

-0 :warning:
javadoc
0m 19s
hbase-common in the patch failed.

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

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

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

_ Other Tests _

-1 :x:
unit
180m 52s
root in the patch failed.

220m 39s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / a8c49a6463

Default Java
2020-01-14

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-common.txt

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

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

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-root.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-common.txt

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

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

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-root.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/2/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-root.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/2/testReport/

Max. process+thread count
6118 (vs. ulimit of 30000)

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

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/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 29s
Docker mode activated.

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

_ Prechecks _

_ master Compile Tests _

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

+1 :green_heart:
mvninstall
4m 54s
master passed

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

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

+1 :green_heart:
javadoc
4m 43s
master passed

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

-1 :x:
unit
446m  2s
root in the patch failed.

493m 10s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/2/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / a8c49a6463

Default Java
1.8.0_232

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/2/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-root.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/2/testReport/

Max. process+thread count
3725 (vs. ulimit of 30000)

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

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/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.

Fix tests w/ latest push. The tests were not factoring fact that now the file timestamp is considered.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ master Compile Tests _

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

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

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

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

+1 :green_heart:
spotbugs
12m 12s
master passed

_ Patch Compile Tests _

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

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

-0 :warning:
checkstyle
1m 54s
root: The patch generated 1 new + 9 unchanged - 22 fixed = 10 total (was 31)

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

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

+1 :green_heart:
hadoopcheck
17m 10s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1 3.3.0.

+1 :green_heart:
spotbugs
13m  4s
the patch passed

_ Other Tests _

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

73m  4s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/3/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle refguide

uname
Linux d0a6e282107d 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
master / a8c49a6463

refguide
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/3/artifact/yetus-general-check/output/branch-site/book.html

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/3/artifact/yetus-general-check/output/diff-checkstyle-root.txt

refguide
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/3/artifact/yetus-general-check/output/patch-site/book.html

Max. process+thread count
137 (vs. ulimit of 30000)

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

_ Patch Compile Tests _

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

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

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

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

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

-0 :warning:
javadoc
0m 16s
hbase-common in the patch failed.

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

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

-0 :warning:
javadoc
0m 14s
root in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
176m  5s
root in the patch passed.

211m 45s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 7b26d65c5a20 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / a8c49a6463

Default Java
2020-01-14

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/3/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-root.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/3/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-common.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/3/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-mapreduce.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/3/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/3/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-common.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/3/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/3/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-mapreduce.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/3/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-root.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/3/testReport/

Max. process+thread count
7044 (vs. ulimit of 30000)

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

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/3/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.

Addressed @wchevreuil review.
No plans to move WALPlayer to hbck2. I'd added the hbck2 prefix since it tooling to do fixup (though it core).
Thanks @wchevreuil

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ master Compile Tests _

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

+1 :green_heart:
mvninstall
4m 33s
master passed

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

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

+1 :green_heart:
spotbugs
16m 30s
master passed

_ Patch Compile Tests _

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

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

-0 :warning:
checkstyle
2m 38s
root: The patch generated 1 new + 9 unchanged - 22 fixed = 10 total (was 31)

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

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

+1 :green_heart:
hadoopcheck
20m 18s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1 3.3.0.

+1 :green_heart:
spotbugs
12m 52s
the patch passed

_ Other Tests _

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

88m 47s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/4/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle refguide

uname
Linux 8a9b6146fb16 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
master / 8a995ae81b

refguide
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/4/artifact/yetus-general-check/output/branch-site/book.html

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/4/artifact/yetus-general-check/output/diff-checkstyle-root.txt

refguide
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/4/artifact/yetus-general-check/output/patch-site/book.html

Max. process+thread count
139 (vs. ulimit of 30000)

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

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/4/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

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

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

_ Prechecks _

_ master Compile Tests _

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

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

+1 :green_heart:
compile
2m 57s
master passed

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

+1 :green_heart:
javadoc
4m 14s
master passed

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
163m 14s
root in the patch passed.

204m 20s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/4/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 9276ae9761ae 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
master / 8a995ae81b

Default Java
2020-01-14

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/4/testReport/

Max. process+thread count
6861 (vs. ulimit of 30000)

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

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2504/4/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.


Parse Video Error!!!

Hello,
Currently, some videos are limited by country. Please help to check it.
Domain: XCDYouTubeVideoErrorDomain
Code:   -2
User Info: {
AllowedCountries = "{(\n    "United States"\n)}";
NSLocalizedDescription = "The uploader has not made this video available in your country.";
NSURL = "https://www.youtube.com/get_video_info?eurl=https://youtube.googleapis.com/v/jOAoQO9UOHs&hl=en&sts=&video_id=jOAoQO9UOHs";
}
Thank you,

Are you in the United States?

Are you in the United States?

No. I live in Vietnam.
I have selected some VEVO videos with the region in the United States and occasionally receive this error.

Interesting. Well based on the error message that is why you're getting that error. What I suggest is using a VPN or proxy to change your IP to a US one and try again.


Animations do not sanitize their defaults consistently

https://github.com/kmagiera/react-native-reanimated/blob/a4d6e11902956fe686f119948405641c1493b839/src/animations/backwardCompatibleAnimWrapper.js#L108-L113
If the animation function is called with all three arguments, then config never goes through the AnimationClass which provides default values if they are not available.
It seems like there should be a consistent sanitizer function for the config that works the same both ways.

Hi,
There's few issue, which have to be resolved:

https://github.com/kmagiera/react-native-reanimated/blob/a4d6e11902956fe686f119948405641c1493b839/src/animations/SpringAnimation.js#L38 "sanitizer" like this is not enough, because config could be animated node as well and JS arithmetical operation are not fine. At the very begging proof of concept of RNR was done only in JS and then implemented in Java and ObjC.

How about state? I suppose that state should be also "default" if there's not enough fields

Take a look on this case:
We have some node e.g.const x = add(10, 20)
Then I wish to use it as speed and other node as bounciness.
So it's a bit more complicated:
https://github.com/kmagiera/react-native-reanimated/pull/40/files
I'm preparing this PR and I suppose it will be finished soon

I don't think I ever asked for JS arithmetical operations in this issue. This is about providing defaults if undefined is passed in, or if the state or config objects do not have expected properties, or to support properties like friction which are supported in SpringAnimation but not spring.

Ok, default value is maybe fine for a moment, but I wish to prepare more complex mechanism.
If it is about spring animation, it's not enough to check if values are present or not, but also they have to be "translated" in order to provide fixed structure to spring.js. And this translation can't be done with arithmetical operations in js.

I must have mis-communicated something along the way, because nothing about this issue is related to translation. This is about consistently-handling config objects the same way within:

decay and DecayAnimation
spring and SpringAnimation
timing and TimingAnimation

When calling one of the functions with 3 arguments, the state and config are passed straight-through and the AnimationClass is avoided entirely. Each AnimationClass observes the state and config, pulls out pertinent nodes, and handles defaults. SpringAnimation also supports friction, which is not a standard config for spring.
My proposal is only to consistently handle that initialization.
The work within #40 is great for spring, and also could be applied to its state and also to the decay and timing functions.

Yes, you are right about the need to handle each case of not-complete config and state. I wish only to point that it's not enough just to add missing value because it's more complicated issue (if it is about spring). I wish to cover issue of missing config and state values in this PR I linked

For now decided to do it like ^^, @ckknight
Is it what did you mean?


Add option to override Kafka Broker version

Description
Add option to override Kafka Broker version
Issue reference
https://github.com/dapr/dapr/issues/3806
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[x] Extended the documentation https://github.com/dapr/docs/issues/1912

/cc @artursouza @yaron2


Testing

Adding intial set of tests. Testing coverage up to ~40%

Codecov Report
Attention: Patch coverage is 98.01325% with 3 lines in your changes are missing coverage. Please review.
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files
Coverage Δ

src/operations.rs
91.66% <100.00%> (+91.66%)
:arrow_up:

src/query/mod.rs
71.56% <100.00%> (+71.56%)
:arrow_up:

src/main.rs
10.00% <0.00%> (+10.00%)
:arrow_up:

... and 1 file with indirect coverage changes


Move InternalsVisibleTo to AssemblyInfo

InternalsVisibleTo is usually located in AssemblyInfo.

For some reason Travis failed on:
$ nuget restore KNX.net.sln
WARNING: Error: ConnectFailure (Connection timed out)
Unable to find version '2.6.4' of package 'NUnit'.
The command "nuget restore KNX.net.sln" failed and exited with 1 during .

Didn't change anything to that, can we somehow retrigger the build? Maybe it was a Nuget issue

Closing and re-opening retriggers Travis apparently :)


Clean up mod.s

Move function definitions out of mod.ts, it should only contain exports

https://github.com/denorians/deno_actions_core/issues/10#issuecomment-1521083218


Error populating SpikeSortingRecording

SpikeSortingRecording.populate(), restricted to one SpikeSortingRecordingSelection entry, begins to run, and prints:
write_binary_recording with n_jobs 4 chunk_size 156250000
then fails due to one exception, which leads to another exception. Error appears to be related to parallelization of chunks in get_traces in spikeinterface, resulting in OSError: Can't read data (wrong B-tree signature). The first and second exception and their tracebacks look similar at first pass, so will start with this first one for brevity. Thanks in advance for any input.
---------------------------------------------------------------------------
_RemoteTraceback                          Traceback (most recent call last)
_RemoteTraceback:
"""
Traceback (most recent call last):
  File "/home/alison/anaconda3/envs/nwb_datajoint/lib/python3.8/concurrent/futures/process.py", line 239, in _process_worker
    r = call_item.fn(*call_item.args, **call_item.kwargs)
  File "/home/alison/anaconda3/envs/nwb_datajoint/lib/python3.8/concurrent/futures/process.py", line 198, in _process_chunk
    return [fn(*args) for args in chunk]
  File "/home/alison/anaconda3/envs/nwb_datajoint/lib/python3.8/concurrent/futures/process.py", line 198, in <listcomp>
    return [fn(*args) for args in chunk]
  File "/home/alison/anaconda3/envs/nwb_datajoint/lib/python3.8/site-packages/spikeinterface/core/job_tools.py", line 279, in function_wrapper
    return _func(segment_index, start_frame, end_frame, _worker_ctx)
  File "/home/alison/anaconda3/envs/nwb_datajoint/lib/python3.8/site-packages/spikeinterface/core/core_tools.py", line 177, in _write_binary_chunk
    traces = recording.get_traces(start_frame=start_frame, end_frame=end_frame, segment_index=segment_index)
  File "/home/alison/anaconda3/envs/nwb_datajoint/lib/python3.8/site-packages/spikeinterface/core/baserecording.py", line 101, in get_traces
    traces = rs.get_traces(start_frame=start_frame, end_frame=end_frame, channel_indices=channel_indices)
  File "/home/alison/anaconda3/envs/nwb_datajoint/lib/python3.8/site-packages/spikeinterface/toolkit/preprocessing/filter.py", line 107, in get_traces
    traces_chunk, left_margin, right_margin = get_chunk_with_margin(self.parent_recording_segment,
  File "/home/alison/anaconda3/envs/nwb_datajoint/lib/python3.8/site-packages/spikeinterface/toolkit/preprocessing/tools.py", line 34, in get_chunk_with_margin
    traces_chunk = rec_segment.get_traces(start_frame - left_margin, end_frame + right_margin, channel_indices)
  File "/home/alison/anaconda3/envs/nwb_datajoint/lib/python3.8/site-packages/spikeinterface/core/channelslicerecording.py", line 79, in get_traces
    traces = self._parent_recording_segment.get_traces(start_frame, end_frame, parent_indices)
  File "/home/alison/anaconda3/envs/nwb_datajoint/lib/python3.8/site-packages/spikeinterface/toolkit/preprocessing/common_reference.py", line 121, in get_traces
    all_traces = self.parent_recording_segment.get_traces(start_frame, end_frame, slice(None))
  File "/home/alison/anaconda3/envs/nwb_datajoint/lib/python3.8/site-packages/spikeinterface/core/channelslicerecording.py", line 79, in get_traces
    traces = self._parent_recording_segment.get_traces(start_frame, end_frame, parent_indices)
  File "/home/alison/anaconda3/envs/nwb_datajoint/lib/python3.8/site-packages/spikeinterface/core/segmentutils.py", line 91, in get_traces
    return self.parent_segment.get_traces(*args, **kwargs)
  File "/home/alison/anaconda3/envs/nwb_datajoint/lib/python3.8/site-packages/spikeinterface/core/frameslicerecording.py", line 74, in get_traces
    traces = self._parent_recording_segment.get_traces(start_frame=parent_start,
  File "/home/alison/anaconda3/envs/nwb_datajoint/lib/python3.8/site-packages/spikeinterface/extractors/nwbextractors.py", line 231, in get_traces
    traces = es.data[start_frame:end_frame, channel_indices]
  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
  File "/home/alison/anaconda3/envs/nwb_datajoint/lib/python3.8/site-packages/h5py/_hl/dataset.py", line 573, in __getitem__
    self.id.read(mspace, fspace, arr, mtype, dxpl=self._dxpl)
  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
  File "h5py/h5d.pyx", line 182, in h5py.h5d.DatasetID.read
  File "h5py/_proxy.pyx", line 130, in h5py._proxy.dset_rw
  File "h5py/_proxy.pyx", line 84, in h5py._proxy.H5PY_H5Dread
OSError: Can't read data (wrong B-tree signature)

Update: in a totally new conda env w/ fresh pip install, I can populate SpikeSortingRecording with a very small segment of data (100s), but not a longer segment of data, potentially also pointing to get_traces parallelization issue. For a longer time segment, things are extremely slow in the new env, so I haven't reached an error at this point - but based on htop, doesn't look like anything is really happening, so it is unclear what is going on.

Some online searching suggests that this is a problem with parallel reads of an HDF5 file.
We could, as a temporary fix, restrict the spike interface calls to use a single thread or switch to a storing the data in a non-NWB recording extractor. A longer term fix would, from the looks of it, involve changing the way the files are opened for reading in spike interface.
On Mar 4, 2022, at 12:19 PM, acomrie<EMAIL_ADDRESS>wrote:
This Message Is From an External Sender
This message came from outside your organization.
Update: in a totally new conda env w/ fresh pip install, I can populate SpikeSortingRecording with a very small segment of data (100s), but not a longer segment of data, potentially also pointing to get_traces parallelization issue. For a longer time segment, things are extremely slow in the new env, so I haven't reached an error at this point - but based on htop, doesn't look like anything is really happening, so it is unclear what is going on.
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/LorenFrankLab/nwb_datajoint/issues/150*issuecomment-1059492809__;Iw!!LQC6Cpwp!_IrypLAulIkYTM_Kr6Ez-ION57FmsijVyPL2Oxo2deip5IaTbLKdla-Al-T94ape-Q$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ABV4PSJSLLI7V7NBKD5L44DU6JV6LANCNFSM5P4KJHZA__;!!LQC6Cpwp!_IrypLAulIkYTM_Kr6Ez-ION57FmsijVyPL2Oxo2deip5IaTbLKdla-Al-T-EWcVCA$.
Triage notifications on the go with GitHub Mobile for iOShttps://urldefense.com/v3/__https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!LQC6Cpwp!_IrypLAulIkYTM_Kr6Ez-ION57FmsijVyPL2Oxo2deip5IaTbLKdla-Al-THcWMycw$ or Androidhttps://urldefense.com/v3/__https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign*3Dnotification-email*26utm_medium*3Demail*26utm_source*3Dgithub__;JSUlJSU!!LQC6Cpwp!_IrypLAulIkYTM_Kr6Ez-ION57FmsijVyPL2Oxo2deip5IaTbLKdla-Al-RSbCiyLA$.
You are receiving this because you are subscribed to this thread.

@acomrie could you tell me which NWB you're working with here? I'll try to reproduce the error in my test dj database

Update: just testing to confirm that it works, but using n_jobs=1 should be a reasonable interim fix. Will want to expose the //ization params (n_jobs and total_memory, at minimum) as user params at some point. Double checking this with a new test that is currently running - when it finishes, I can make PR for the quick fix


Update manager cli to parse purge and report durations correctly

Currently, the cli converts hours to seconds and days to seconds.
Stratagem uses milliseconds instead of seconds so the conversion needs
to be updated.

Convert hours to milliseconds
Convert days to milliseconds

Signed-off-by: Will Johnson<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1030   +/-   ##
=======================================
  Coverage   95.42%   95.42%
=======================================
  Files           2        2
  Lines         153      153
=======================================
  Hits          146      146
  Misses          7        7

Continue to review full report at Codecov.

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


Fix: Resolving compile error of derive crate with 'online' feature

In a dependent Cargo crate, using the following dependency specification:
kona-derive = { git = "https://github.com/anton-rs/kona.git", branch = "main", features = ["online"] }

This results in the following compile error:
error[E0432]: unresolved import `revm::primitives::kzg`
  --> ... crates/primitives/src/sidecar.rs:14:23
   |
14 | use revm::primitives::kzg::EnvKzgSettings;
   |                       ^^^ could not find `kzg` in `primitives`
   |

The root cause of this error is that the derive crate doesn't enable the "c-kzg" feature, which is required for the code to compile correctly. I plan to submit a pull request (PR) to fix this issue.

This is fixed by https://github.com/anton-rs/kona/pull/482


missing caps i on landing page

Accoring to https://github.com/bioimage-io/bioimage.io/issues/28#issuecomment-802927010 is should be BioImage I think....

Right there in front of our eyes... 👀

Nice catch! Will do!


Private pandas method being used, changed in pandas 1.1

From a report on the pandas issue tracker (https://github.com/pandas-dev/pandas/issues/35404), it seems zipline is using a private pandas utility:
https://github.com/quantopian/zipline/blob/d74ba5a163328e89b321692b621a68c140f1a8be/zipline/utils/pandas_utils.py#L222-L224
(anything in pandas.core is considered private, see https://pandas.pydata.org/docs/reference/index.html

Thanks @jorisvandenbossche ! We haven't looked into making zipline compatible with pandas>0.22 yet, so this will be a good class of compat fix for 1.1+.


toascii - Change std::stringstreams to std::ostringstreams

We use large numbers of temporary input/output std::stringstreams when all we want is to output into them.
The class std:stringstream uses multiple inheritance.

The class std:ostringstream only uses single inheritance, with hopefully faster function dispatch and a simpler internal layout to each object.

Since we create them all over the place, we should use the simplest option we can get away with.
Related:
https://github.com/LunarG/gfxreconstruct/issues/601
https://github.com/LunarG/gfxreconstruct/issues/761

It got done bit by bit.


App Crashes

Ledger Live Version and Operating System

tested on Ledger Live 2.3.0 (121)
Phone version: iPhone 11 Pro Max

Expected behavior
No crashes
Actual behavior
This app crashes ALL THE TIME!! Can the owners and executive team of Ledger actually step up and fix these problems... I mean roughly 1/3 of the times I launch the app it crashes. It's insane how bad this app is in terms of crashing...
Steps to reproduce the behavior
Launch the app

We are aware of this problem and team is actively working on finding a solution. The cause of the issue has been clearly identified and we hope to deliver a fix. (EXC_BAD_ACCESS in lib-ledger-core bindings)

what is the status for fixing this ?

@blockomoco The reality is it looks like Ledger doesn't care about their app crashing. It's absolutely insane that they are so focused on releasing new features like buying crypto within the app, instead of focusing on the priorities that actually matter, having the app not crash in the first place...
This should be considered a blocker for the Ledger team. All focus should be diverted to fixing this crash. No releases should go out until it's fixed.

This is indeed a very annoying issue. Tried to do a transfer yesterday and the app crashed 4 times before being usable. This keeps on happening each time Im using the app. On a positive note: the app seems to be stable if it does not crash within the first seconds.
Im using iOS with an iPhone XS, so that this issue does not seem to be specific to @fishcharlie 's configuration. In other words, this is likely affecting a lot of users.
@gre hope you folks can fix this asap

@blockomoco Agreed. I'd be curious to see the stats about how many users and sessions this is effecting. From my experience and perspective, it seems to be a LOT.
Just incredibly frustrating to have to deal with crashes so often and then to see the Ledger team only focusing on features like buying crypto within the application. What is even the point of that when the application is so incredibly unstable?

Tentative fix with 2.13


Fix perf tests

My last PR broke the non-multi function tests since they weren't starting up a new host every iteration. While looking at this I decided to also fix up the problem where we were starting up the host as part of the test which gave very inflated numbers for the execution time of each iteration.
Now each test will start the host once and then run through its iterations (cleaning up the tables after every run). This makes them run significantly faster and gives more accurate numbers.
I also modified some of the values we use to make the runtimes a bit more reasonable. We still have some that run for quite a while that I want to get back to, but it's at least not 30+min for some of the runs now.

Merging this in now to get other PR out - leave any comments here and I'll follow up later


Toolkit block

This block was requested by Matt, it allows for a toolkit to be inserted into the article to display other related articles or useful links. There is still room for feedback and changes but ideally they would like to use it on the 17th of May.
Test URL:
https://toolkit_block--blog--webistry-development.hlx.page/en/drafts/williambsm/toolkit-demo
I recognize a lot of the code is very specific in it's target and it doesn't allow for much flexibility, but the specificity of the design required me to take this approach. I'm open to ideas on this!

@williambsm I just wanted to note that there is an /icons/icons.svg sprite and you may ant to consider adding the link icon there...


starcoder2 broken for ollama >= 0.1.43

What is the issue?
I’ve encountered a change in the behavior from ollama version <= 0.1.42 to version >= 0.1.43. Specifically, the generated output for a simple Fibonacci function differs significantly between these versions.
Using the following code snippet:
client.generate(model="starcoder2:7b-q4_K_M", prompt="<fim_prefix>def fibonacci(n):<fim_suffix><fim_middle>",
   options={"temperature": 0.0,"seed": 123,"stop": ["<file_sep>"]}, stream=True)

Expected Output (<= 0.1.42):

    if n == 0:
        return 1
    elif n == 1:
        return 2
    else:
        return fibonacci(n-1) + fibonacci(n-2)

print(fibonacci(5))

Actual Output (>= 0.1.43):

    return n

After cherry-picking the commits, starting from ollama 0.1.42, I found that the change in behavior appears to be introduced by https://github.com/ollama/ollama/commit/34f142797aff17af2a1c22d68529269d231cc8d4
@jmorganca @deadbeef84

Was this change in behavior intentional?
If not, are there any suggestions on how to address this issue?

Please let me know if you need any further information or assistance in reproducing the issue.
OS
Linux
GPU
Nvidia
CPU
Intel
Ollama version
0.1.43

I didn't analyze it further, but it seems that latest ollama release 0.2.7 in combination with python package 0.3.0 solves the issue.

This should be fixed now.


Add STRDST

This pull request is to add STRDST token on osmosis.

_Adds STRDST info to source-chain-infos.ts
_Adds a token image to /tokens/strdst.svg

Hey @JeremyParish69 please let me if there is anything more I should do.
thank you.

Hi, @lakmalmabm , is there a liquidity pool with this token? and what is the pool id # ?

Hey @JeremyParish69 , We are planing to use a stream swap so do we need to make the pool before it?

Hey @JeremyParish69 , We are planing to use a stream swap so do we need to make the pool before it?

In that case, no, you don't. When is the StreamSwap panned for?

as soon as the Streamswap team processes our request, most probably within the next 2 weeks.
currently, we are trying to move some testnet tokens from Stargaze testnet osmosis testnet. Once it is done, streamswap team will setup it using testnet tokens.

Hi @JeremyParish69
We are going to start our streamswap session on 10/10 and once it is completed we need to create a pool. so can we continue on this PR.


Can't load assets when the root asset/folder name has # prefix

Release Type: Official Release
Version: <IP_ADDRESS>2 (affects 4.1 as well)
Platform(s): Windows
Describe the bug
Naming a root asset folder or root asset with # prefix will not load the content.
To Reproduce
Steps to reproduce the behavior:

Create 'New game' project
Rename 'MainScene' asset to '#MainScene' (alternatively make a folder called #Scene and move MainScene in there)
Run game

Expected behavior
Game scene should load.
Additional context
Potentially a YAML loading bug, since # prefix represents a comment.
Workaround
Use a different symbol to prefix, eg. $, !, @, etc.

Pinging @IXLLEGACYIXL just to make sure that's something you're aware of for your current yaml rework

the root assets name isnt even stored in the yaml

having special tags in a string should trigger quoting automatically, which the current one and mine do

Sorry I haven't really looked into this as I'm looking at other things, so it might not be a YAML issue. The steps to make the issue happen should be reproducible easily.
Only reason why I speculated on YAML, is because I noticed the diff in file in GameSettings.sdgamesettings
-DefaultScene: 98c3bc8c-99b9-4bd6-a0d3-a4aec9d94845:MainScene
+DefaultScene: 98c3bc8c-99b9-4bd6-a0d3-a4aec9d94845:#MainScene

and then the scene no longer loaded.
I guess GameSettings.DefaultScene stores the scene reference differently.


cmd/compile: provide a more explanatory error message on trying to take the address of an unaddressable value e.g. constants, integer and string literals

What version of Go are you using (go version)?
go version go1.11.1 linux/amd64
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN="/home/24G/.bin"
GOCACHE="/home/24G/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/24G/go"
GOPROXY=""
GORACE=""
GOROOT="/snap/go/2890"
GOTMPDIR=""
GOTOOLDIR="/snap/go/2890/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build434234612=/tmp/go-build -gno-record-gcc-switches"

What did you do?
https://play.golang.org/p/uU1XNXaFYG-
What did you expect to see?
This isn't a bug report, that's exactly what I expected haha. But the purpose of this issue is to get a more helpful error message.
What did you see instead?
cannot take the address of 5
This is quite repulsive toward beginners. People who encounter this error may not understand exactly how constant values work, and what the differences between constants and normal values (after all, they look a lot like variables). Pointers are extremely hard for beginners to deal with, and changing this error message will make the language a bit more approachable.
This is especially unintuitive because &StructValue{...} is okay, but &5 is not.
I propose instead that the message is changed to cannot take the address of the constant value <const>. This should at least explain a reason why the value is not addressable.
If there are cases where this is error message change would be unhelpful, that would be important to consider.

Thank you @deanveloper for filing this bug and welcome to the Go project!
Sounds like a plan, I've updated the title of this issue with the premise of providing a more explanatory error message for trying to take the address of an unaddressable value, that is because 5 is an integer literal while const s = 5 is a still constant and &s would be still valid.
Kindly paging @griesemer @mdempsky, what might you think of these error message suggestions?
a)
cannot take the address of integer literal 5

b)
cannot take the address of 5 (unaddressable because it is an integer literal)

I can work on this sometime soon when I get some free cycles.

I'm sympathetic to making error messages more accessible to new users, but it's not obvious to me that this proposal accomplishes that.
I'm not sure I understand how "cannot take the address of the constant value 5" or "cannot take the address of integer literal 5" is clearer to beginners than "cannot take the address of 5", or how it explains why the value is not addressable. All it does is further emphasize that "5" is a constant value or integer literal, which I expect users already know. (If not, should we emphasize that every time they misuse 5?)
I also don't really like the "unaddressable because it is an integer literal." It's actually unaddressable because it's not one of the cases the Go spec enumerates as addressable: https://golang.org/ref/spec#Address_operators
Is there objective evidence that any of these error messages would be more intuitive to users? What error messages do compilers for other languages emit in similar situations?

It's also noteworthy that constants are not addressable, not just literals.
A better error message would be a lot more useful though in the following case, which is probably what I should have led with: https://play.golang.org/p/G_IxBn_xRz1
I don't have any objective evidence right now. Currently doing this from my phone, I'll look into it when I can though.

I'll admit named constants are a little more compelling, since names can also refer to variables, which are addressable. Similarly, for map indexing, since other syntactically identical index expressions are addressable.
I think elaborating the error messages in circumstances where syntax alone is insufficient to explain why the expression isn't addressable could be reasonable.
However, I'm curious what error folks suggest to use for:
var m map[int][10]struct{ f int }
_ = &m[0][0].f  // ERROR

Maybe something like:
cannot take address of m[0][0].f (m[0] is map index expression)

I.e., drill down past the field selections and array indexing to identify the root non-addressable expression.

What @mdempsky said.
I think the error message is pretty clear, but we could go along the route chosen for binary operators. For instance, for "a" - "b" we get:
invalid operation: "a" - "b" (operator - not defined on string)

Analogously, here we could report:
invalid operation: &5 (operator & not defined on non-addressable 5)

But it really says the same thing, slightly less elegantly.
But I'm also not clear which part of the error message is "repulsive" to newcomers. If one is truly a newcomer, I suspect it's not even clear that & means "take the address" - so a peek into the spec is warranted anyway. If one comes from C, the error message seems "obvious". Maybe this is better:
invalid operation: &5 (constant 5 is not addressable)

Either way, this doesn't need to be a proposal. If a convincingly better error message comes along, I'm ok with changing this; but I don't see the current error as overly problematic.

Closed by mistake. Re-opening.

invalid operation: "a" - "b" (operator - not defined on string)

invalid operation: &5 (operator & not defined on non-addressable 5)

These aren't quite the same, if we make the second one more like the first, the error message is a lot more useful:
with literal values
invalid operation: &5 (operator & not defined on literal values)

with named constants
invalid operation: &foo (operator & not defined on constant expressions)

with map indexes
invalid operation: &m[0][0].f (operator & not defined on map index expressions)

with function calls
invalid operation: &bar() (operator & not defined on function calls)

a "catch all" error message for expressions that really fit with any the above
invalid operation: &(-foo) (operator & not defined on non-addressable expressions)

I think cannot take address of <expression> (<explanation>) is a bit more clear, but invalid operation is a bit more consistent.

I'd argue against using "invalid operation" for more error messages. While technically accurate (the expression is an operation expression and it's invalid), I think when most users see "invalid operation," they think of https://www.google.com/search?tbm=isch&q="invalid+operation" and we might as well just say "error".
I think "cannot take address of foo (foo is a constant)" is better than "invalid operation: &foo (operator & not defined on constants)". The former tells you directly what the error was (cannot take address), and gives you additional details as to why that's the case (foo is a constant). The latter instead tells you something that experienced Go programmers already know (you can't take the address of constants) and leaves it to you to infer how that's relevant here (foo is a constant).
Also, I think the error message "invalid operation: &m[0][0].f (operator & not defined on map index expressions)" is misleading, because m[0][0].f is not a map index expression; it's a field selection expression. But it's non-addressable because of the m[0] map index expression.

Also, I think the error message "invalid operation: &m[0][0].f (operator & not defined on map index expressions)" is misleading, because m[0][0].f is not a map index expression; it's a field selection expression. But it's non-addressable because of the m[0] map index expression.

You're definitely right about that, and I've now removed that example. It should just be caught by the "catch-all" if we do the "invalid operation" route.
Something great about the cannot take address of foo (foo is a constant) is that it is an explanation to newcomers, and it's informative to experienced users (maybe we didn't know foo was a constant). As another upside, it doesn't sound condescending. It's a pretty hard balance to strike a balance like that when you're communicating through a text console.

I'm seeing the same message trying to take the address of a generic struct:
&queue.New[func()]()

Seems this would not fall into constants, integer and string literals. Separate issue?

@andig Not a separate issue. Thanks.


Monkey D. Luffy

Issue no: #4
Added a new anime character

Please sync your Fork & then re-open a new Pull Request!


Maintain Uno-Choice selections between filter applications

Any selections made using the current uno-choice control are lost when the options list is updated after you apply a filter. It would be useful to maintain the existing selections between filtering operations of the same list.
This becomes even more important when the options list is long and the filter (a really useful feature of the current implementation) allows you to select successive related options

Hmmm, this issue will probably stay behind after the 1.0 release. We can ship it into a version later 1.0.

Moved to https://issues.jenkins-ci.org/browse/JENKINS-28734


Update HACS URL

I updated the HACS Badge URL to the new hacs/integration

That's for the URL update👍


The download link is not working

[The download link is not working
https://www.microsoft.com/en-us/download/details.aspx?id=39366]

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

ID: 27364aed-dc10-dcaf-8446-bc93e39bd4ca
Version Independent ID: 907a29a6-6ff3-5c91-5c74-cf98cf71ad88
Content: Download and install the Skype for Business Online Connector module
Content Source: Skype/SfbOnline/set-up-your-computer-for-windows-powershell/download-and-install-the-skype-for-business-online-connector.md
Service: skype-for-business-online
GitHub Login: @tonysmit
Microsoft Alias: tonysmit

Download link is not working for me either. Just used it 2 days ago and it worked fine.

@CarlosFarrica  and  @leebjn
The link shown in the comment does fail, but it appears to be doing so because of the square bracket appended at the end. I'm not able to reproduce this in the article itself.
This download center asset was updated yesterday, or possibly early this morning. When one of these assets is updated, there is a "freeze" period of several hours, and during that time the asset page is unavailable. It's back to normal now.
@tonysmit closing this now on your behalf.


Invalid External Storage Path

I got the following crash from an user on a Samsung Galaxy Tab 2 (Android 9.0)
Fatal Exception: java.lang.IllegalArgumentException
Invalid path: /storage/emulated/0
android.os.StatFs.doStat (StatFs.java:51)
android.os.StatFs.<init> (StatFs.java:41)
github.nisrulz.easydeviceinfo.base.EasyMemoryMod.getAvailableExternalMemorySize (EasyMemoryMod.java:147)

Caused by android.system.ErrnoException
statvfs failed: ENOENT (No such file or directory)
libcore.io.Linux.statvfs (Linux.java)
libcore.io.BlockGuardOs.statvfs (BlockGuardOs.java:333)
android.system.Os.statvfs (Os.java:570)
android.os.StatFs.doStat (StatFs.java:49)
android.os.StatFs.<init> (StatFs.java:41)
github.nisrulz.easydeviceinfo.base.EasyMemoryMod.getAvailableExternalMemorySize (EasyMemoryMod.java:147)

A quick StackOverflow search shows me that the reason it crashes is because you can't assume that an external storage exists.
Currently wrapping getAvailableExternalMemorySize() in a try catch to prevent crash.

Thanks for creating this library, it's fantastic :)

Good catch. I will add that and more fixes related to this soon.
Thank you for reporting this issue.


elm make autocomplete

When using elm make without the hyphen, tab does not complete filenames but it does when using elm-make. Is there a difference between the two commands that would explain this behaviour? Anyway, it's not really problematic but it is easier to type   than -.

It sounds like you're talking about auto-completion when typing shell commands in a terminal. Elm isn't really doing anything at that stage -- the behaviour of auto-completion is controlled by whatever shell you're using (i.e. bash, tcsh, csh, etc).
Now, one difference between elm-make and elm make is that in the second case, make is the first parameter (rather than part of the command name). So, perhaps there is something in your shell's autocompletion logic that turns on whether the first parameter is itself a file name or something like that.
Though, I just tried it in bash on Mac OS X, and it doesn't make a difference there.

I indeed tried it with bash and it works as expected. It is the zsh behaviour that is problematic so no problem on your side. closing.


P2P-bandwidth No peers found...

We retested 2 x MI25 on Supermicro X11DGQ with new test tools.
It looks P2P still have some problems by using the RVS tool. Two GPU cannot peer to each other on dual root setup over UPI.
[RESULT] [    94.478367] [action_4] p2p 7707 7707 peers:false distance:-1
[RESULT] [    94.478397] [action_4] p2p 7707 51576 peers:false distance:-1
[RESULT] [    94.478415] [action_4] p2p 51576 7707 peers:false distance:-1
[RESULT] [    94.478424] [action_4] p2p 51576 51576 peers:false distance:-1
[ERROR ] [    94.478431] [action_4] p2p-bandwidth No peers found
If I put 2GPU under the same CPU, it looks okay. So the P2P over the UPI maybe still have problem.
[RESULT] [  1231.828304] [action_2] peqt TRUE
[RESULT] [  1231.981221] [action_3] pcie-bandwidth 0 2 7707  distance:20 PCIe:20
[RESULT] [  1231.981311] [action_3] pcie-bandwidth 1 2 7707  distance:41 QPI:41
[RESULT] [  1231.981373] [action_3] pcie-bandwidth 0 3 63982  distance:20 PCIe:20
[RESULT] [  1231.981427] [action_3] pcie-bandwidth 1 3 63982  distance:41 QPI:41
[INFO  ] [  1232.2409  ] [action_3] pcie-bandwidth  [1/4] 0 7707  h2d: true  d2h: false  12.562 GBps
[INFO  ] [  1232.9325  ] [action_3] pcie-bandwidth  [2/4] 1 7707  h2d: true  d2h: false  12.567 GBps
[INFO  ] [  1232.26636 ] [action_3] pcie-bandwidth  [3/4] 0 63982  h2d: true  d2h: false  12.571 GBps
[INFO  ] [  1232.32599 ] [action_3] pcie-bandwidth  [4/4] 1 63982  h2d: true  d2h: false  12.477 GBps
[RESULT] [  1232.33685 ] [action_3] pcie-bandwidth  [1/4] 0 7707  h2d: true  d2h: false  12.562 GBps  duration: 0.000759 sec
[RESULT] [  1232.33698 ] [action_3] pcie-bandwidth  [2/4] 1 7707  h2d: true  d2h: false  12.567 GBps  duration: 0.000759 sec
[RESULT] [  1232.33706 ] [action_3] pcie-bandwidth  [3/4] 0 63982  h2d: true  d2h: false  12.571 GBps  duration: 0.000759 sec
[RESULT] [  1232.33714 ] [action_3] pcie-bandwidth  [4/4] 1 63982  h2d: true  d2h: false  12.477 GBps  duration: 0.000764 sec
[RESULT] [  1232.35258 ] [action_4] p2p 7707 7707 peers:false distance:-1
[RESULT] [  1232.35294 ] [action_4] p2p 7707 63982 peers:true distance:40 PCIe:40
[RESULT] [  1232.35322 ] [action_4] p2p 63982 7707 peers:true distance:40 PCIe:40
[RESULT] [  1232.35346 ] [action_4] p2p 63982 63982 peers:false distance:-1
[INFO  ] [  1232.43996 ] [action_4] p2p-bandwidth  [1/2] 7707 63982  bidirectional: true  15.886 GBps
[INFO  ] [  1232.52321 ] [action_4] p2p-bandwidth  [2/2] 63982 7707  bidirectional: true  17.108 GBps
[RESULT] [  1232.53436 ] [action_4] p2p-bandwidth  [1/2] 7707 63982  bidirectional: true  15.886 GBps  duration: 0.001524 sec
[RESULT] [  1232.54530 ] [action_4] p2p-bandwidth  [2/2] 63982 7707  bidirectional: true  17.108 GBps  duration: 0.001415 sec
difCPU.txt
sameCPU.txt

The RVS version is 0.0.21
Here is the bandwidth_test result in RVS:
lab@lab:~/RVS/build/bin$ sudo ./rvs -c conf/pebb_test1.conf -d 3
[RESULT] [   271.84031 ] [action_1] pcie-bandwidth 0 2 7707  distance:20 PCIe:20
[RESULT] [   271.84120 ] [action_1] pcie-bandwidth 1 2 7707  distance:41 QPI:41
[RESULT] [   271.84183 ] [action_1] pcie-bandwidth 0 3 63982  distance:20 PCIe:20
[RESULT] [   271.84239 ] [action_1] pcie-bandwidth 1 3 63982  distance:41 QPI:41
[RESULT] [   271.84295 ] [action_1] pcie-bandwidth 0 4 41051  distance:41 QPI:41
[RESULT] [   271.84348 ] [action_1] pcie-bandwidth 1 4 41051  distance:20 PCIe:20
[RESULT] [   271.84403 ] [action_1] pcie-bandwidth 0 5 51576  distance:41 QPI:41
[RESULT] [   271.84453 ] [action_1] pcie-bandwidth 1 5 51576  distance:20 PCIe:20
[INFO  ] [   271.106563] [action_1] pcie-bandwidth  [1/8] 0 7707  h2d: true  d2h: false  12.841 GBps
[INFO  ] [   271.112995] [action_1] pcie-bandwidth  [2/8] 1 7707  h2d: true  d2h: false  12.572 GBps
[INFO  ] [   271.133592] [action_1] pcie-bandwidth  [3/8] 0 63982  h2d: true  d2h: false  12.838 GBps
[INFO  ] [   271.140650] [action_1] pcie-bandwidth  [4/8] 1 63982  h2d: true  d2h: false  12.840 GBps
[INFO  ] [   271.160665] [action_1] pcie-bandwidth  [5/8] 0 41051  h2d: true  d2h: false  12.835 GBps
[INFO  ] [   271.168225] [action_1] pcie-bandwidth  [6/8] 1 41051  h2d: true  d2h: false  10.137 GBps
[INFO  ] [   271.188514] [action_1] pcie-bandwidth  [7/8] 0 51576  h2d: true  d2h: false  12.830 GBps
[INFO  ] [   271.194793] [action_1] pcie-bandwidth  [8/8] 1 51576  h2d: true  d2h: false  11.309 GBps
[RESULT] [   271.195933] [action_1] pcie-bandwidth  [1/8] 0 7707  h2d: true  d2h: false  12.841 GBps  duration: 0.000743 sec
[RESULT] [   271.195956] [action_1] pcie-bandwidth  [2/8] 1 7707  h2d: true  d2h: false  12.572 GBps  duration: 0.000759 sec
[RESULT] [   271.195965] [action_1] pcie-bandwidth  [3/8] 0 63982  h2d: true  d2h: false  12.838 GBps  duration: 0.000743 sec
[RESULT] [   271.195973] [action_1] pcie-bandwidth  [4/8] 1 63982  h2d: true  d2h: false  12.840 GBps  duration: 0.000743 sec
[RESULT] [   271.195981] [action_1] pcie-bandwidth  [5/8] 0 41051  h2d: true  d2h: false  12.835 GBps  duration: 0.000743 sec
[RESULT] [   271.195989] [action_1] pcie-bandwidth  [6/8] 1 41051  h2d: true  d2h: false  10.137 GBps  duration: 0.000941 sec
[RESULT] [   271.195996] [action_1] pcie-bandwidth  [7/8] 0 51576  h2d: true  d2h: false  12.830 GBps  duration: 0.000743 sec
[RESULT] [   271.196017] [action_1] pcie-bandwidth  [8/8] 1 51576  h2d: true  d2h: false  11.309 GBps  duration: 0.000843 sec

During the bandwidth test, we didn't see any bandwidth test thru UPI as well. Maybe is that the issue?

@kennethchiu-smc

PEBB test: Admittedly, "pcie-bandwidth" label is a bit misleading. In fact, PEBB test measures bandwidth for all available HSA nodes regardless of link type. If you want to filter out on specific link type, please wait for version 0.22
Consequently, from what I can see in the output, QPI links are also tested (see transfers [2/8], [4/8], [5/8], [7/8])

PQT test ("p2p"): it seems that GPUs in your syst are in fact not peers in HSA sence. As suggested, please run rocm_bandwidth_test and look into connection matrix to verify this.

Well, this confirms that GPUs on this system are not peers, hence no p2p bandwidth test is performed.
As per newer tool, there is nothing that I am aware of (except for RVS of course) but you may contact Adrian (@jedwards-AMD)

Support for p2p occurs at the driver/hardware level, and has nothing to do with a "tool". The topology of the interconnections between GPUs is what determines if GPUs are peers.


The content in the warcRecord includes the trailing \r\n

The 'content' ArrayBuffer in the record appears to include the trailing \r\n
Tested this with compressed WARCs, may not be the case for uncompressed

Can you attach an example or give some more information as to in which record it happened? It would be helpful to trace the error.


Add user profile link on tweets

As well as the twitter official, this PR gives an link to the user name in each tweet.

Sounds good. Thank you!

Released as v1.2.3.


[build] Add checker framework for nullness type-checking

Add checker framework for nullness type-checking
We’ve been running into a lot of NPEs lately, so we decided to bring in the Checker Framework for nullness type-checking to help catch and prevent these issues. The checker is off by default and will be turned on gradually for each module. To enable it, pass the -PskipCheckerFramework=false flag when running Gradle.
Example:
./gradlew -PskipCheckerFramework=false compileJava

For more info about checker framework, see Checker Framework
How was this PR tested?

Does this PR introduce any user-facing changes?

[x] No. You can skip the rest of this section.
[ ] Yes. Make sure to explain your proposed changes and call out the behavior change.

Thanks a lot Sushant!
There is a unit test failure, though it looks like a hang. I have seen that before recently, so I wonder if we have a regression of some kind. We need to investigate the test logs to find out which test is causing the hang / time out.
But it seems clear this PR is not the culprit, so let's just re-run the task for now...

Yes, I raised this issue with the committer when it first occurred. I also spent some time investigating but couldn’t pinpoint the actual problem.


candlewriter as a separate node program

So far I have only tried Gekko backtesting on bitstamp and bitfinex. I have noticed that stopping and starting gekko creates a new candle dataset.
My idea is to separate the writeCandles function into a separate program. The benefit is continous data collecting even if gekko is stopped for updating or reconfiguration purposes. This program could be started from inside or outside Gekko like this or similar: [nohup] node gekkoCollect <exchange> [&]

hey @eigilb! I just now (an hour ago) pushed a new version of Gekko that includes a lot of upgrades and a web interace.
On of the other things it includes is two submodes:

A market watcher (that only pushes candles into the database)
A "leecher" stratrunner that gets the information out of the database.

More information can be found in #513.
This allows what you are describing and more:

Keep the watcher runner, restart and stop the trader/stratrunner/etc.
Try out different strats against one market (while only watching the market once)
etc.

Setting up these two submodes can be done automatically using the UI. And I will about how to expose them using the CLI (if you have any ideas how you think this should be configured easily, let me know).

The functionality requested is part of the live UI. Closing this for now.


For new surface area, classes marked as final should not have virtual methods.

Fixes https://github.com/Azure/azure-sdk-for-cpp/issues/5253 (for newly introduced methods)

The generate docs step is failing with errors from doxygen:
https://dev.azure.com/azure-sdk/public/_build/results?buildId=3482607&view=logs&j=7243e6f3-06c3-5944-bf14-6bd5d27ce15f&t=c63633fe-e155-5234-bad3-647fadf86cc7
I don't see why the use of the _azure_NON_FINAL_FOR_TESTS macro (which expands to nothing in non-test builds) causes doxygen to fail with this error:

D:/a/_work/1/s/sdk/identity/azure-identity/inc/azure/identity/azure_cli_credential.hpp(30): error : explicit link request to 'Azure::Identity::AzureCliCredential' could not be resolved [D:\a_work\1\s\build\sdk\identity\azure-identity\azure-identity-docs.vcxproj]

Above, it is not processing the macro correctly. It seems to be parsing text verbatim:

024-02-09T02:34:58.9662865Z   Preprocessing D:/a/_work/1/s/sdk/identity/azure-identity/src/azure_cli_credential.cpp...
2024-02-09T02:34:58.9663734Z D:/a/_work/1/s/sdk/identity/azure-identity/src/azure_cli_credential.cpp(60): error : no matching class member found for [D:\a_work\1\s\build\sdk\identity\azure-identity\azure-identity-docs.vcxproj]
2024-02-09T02:34:58.9664417Z     void AzureCliCredential::ThrowIfNotSafeCmdLineInput(std::string const &input, std::string const &allowedChars, std::string const &description) const
2024-02-09T02:34:58.9664883Z   Possible candidates:
2024-02-09T02:34:58.9665758Z     'void Azure::Identity::_azure_NON_FINAL_FOR_TESTS::ThrowIfNotSafeCmdLineInput(std::string const &input, std::string const &allowedChars, std::string const &description) const' at line 85 of file D:/a/_work/1/s/sdk/identity/azure-identity/inc/azure/identity/azure_cli_credential.hpp

@antkmsft, @LarryOsterman - any other feedback (blocking)? I would like to get this checked-in today :)


[Feature] OpenSearch implementation

OpenSearch and ElasticSearch are widely compatible.
I forked your latest repo on master to add a compatibility layer (factory & proxy objects).
i'd push my branch if you are interested.
I guess You would have some work to adept DSL a bit. I'm using plain elastic queries since i translate GraphQL to plain ElasticSearch/OpenSearch queries.
https://github.com/SineMah/laravel-scout-elasticsearch/tree/opensearch

Good job! Let's see if developers interested in it. So please add reaction to topic so we will know if want the feature.

Hey guys, I checked a little bit, and as I see tests are broken on your branch. Unfortunately, we could not say ES and OpenSearch clients are compatible after ES 8.x version. And as I see, ES side will change the client much more in every release, and in the end, we will try to manage this in this library much more than what we did now. Anyhow, I did some changes to your branch. @SineMah

Thanks for looking over the tests.
Managing both backends could be painful in the future. I agree. Proxying client responses might be necessary in the near future. This is too much for a few maintainers and leads into a bottomless hole.
Atm we cant say if the OpenSearch-client will adept the ES-client interface. Probably OpenSearch support should never get to a stable branch for this lib. So people might be aware the feature is not maintained actively. Let's say it is a PoC for now. :D

Yeah I think you're both right. I didn't think much about it but maybe it should be even new engine if we need wrappers for response client and maybe even our own DSL root object.


Unable to run clean docker container

We are trying to setup the docker container but even without any customization we get the following error:
xcb_connection_has_error() returned true
ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave
AL lib: (EE) ALCplaybackAlsa_open: Could not open playback device 'default': No such file or directory
[ INFO] [1621628661.725817494]: waitForService: Service [/gazebo/set_physics_properties] is now available.
process[odom_compat_node-9]: started with pid [227]
[ INFO] [1621628661.752000601]: Physics dynamic reconfigure ready.
process[zed2_imu_transform_publisher-10]: started with pid [291]
process[zed2_imu_transform_broadcaster-11]: started with pid [294]
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::lock_error> >'
  what():  boost: mutex lock failed in pthread_mutex_lock: Invalid argument
Aborted (core dumped)
[gazebo_gui-3] process has died [pid 65, exit code 134, cmd /opt/ros/melodic/lib/gazebo_ros/gzclient __name:=gazebo_gui __log:=/root/.ros/log/85b1f838-ba72-11eb-82c0-0242ac110002/gazebo_gui-3.log].
log file: /root/.ros/log/85b1f838-ba72-11eb-82c0-0242ac110002/gazebo_gui-3*.log

We are running the docker container with:
docker run --rm -it -v /tmp/.X11-unix:/tmp/.X11-unix -e DISPLAY --name erc_sim --gpus all -e NVIDIA_DRIVER_CAPABILITIES=all erc_navigation_sim
with and without --privileged

Please paste the complete output of the docker run command and answer those questions:

What OS are you using?
Did you pull the image from container registry or did you build it yourself?
Did you run xhost +local:root before running the container?
Have you installed the Nvidia Container Toolkit?

Thanks we forgot to run xhost +local:root


it seems that the key display out the screen on OSX 10.10.1

I type the delete and then

I just tried this out on 10.10.1 and all settings in privacy are good. Application is within /Applications. I get nothing on screen. Activity monitor does show the app is running. Just nothing on screen.

I'm experiencing this same problem but on OSX 10.9.5
May it be retina-related?
If I change the resolution (in Displays) and then re-launch KeyCastr, it appears on different parts of the screen.

Just install KeyCastr and really happy now. : ) and I'm on 10.10.2.
Yes, the initial position is out of screen a bit, but the point is you can drag the window to anywhere you want! Here is my experience that you can do to solve this problem:
Hold any key for a long time, you should see the windows with your typing now. Before it fades out, you can drag the window to where you want it to be.
And now you are happy to go! Problem solved!

Hey @petrowsky Yes this info helps
@mgarciaisaia  I don't think it is retina related.
My experience is mostly the same as @ashfinal , but I think we should look into possible fixes for detecting a corrupted stored NSFrame, and refactor related code to be more reliable on modern OS X versions

Hey @akitchen, had the same problem here.  Happy to help troubleshoot if I can.

There are a few issues in the code conspiring to cause this, which the changes in ddf8ed8f774a cause to manifest when installed on new machines.
I completely agree, this needs to be fixed.  It's top-of-list for the next time I have time to dig into it.
For now, turn off "Display only command keys" and hold down a key.  Eventually the visualizer will appear and you can drag it.

There are commits on master which fix this issue; will publish a new version

Please try out v0.8.5 and let us know if the problem remains

Nice, I have update the v0.8.5 and it works well in OSX 10.10.4

Thanks for confirming @taizilongxu !


get transaction fee using sender,receiver and amount

how do i get the transaction fee before sending a transaction

Future getTransactionFee(String amount, String to) async

You can estimate gas with aptos.estimateGas(tx)


Huawei - TypeError: '>=' not supported between instances of 'str' and 'int'

Hi there, I am running latest HA  released (0.88.1) and I am seeing some error in the logs, the don't seems to affect the ui, but I guess there is a problem there:
Last working Home Assistant release (if known):
New component, didn't exists before
Operating environment (Hass.io/Docker/Windows/etc.):
Linux CentOS 7.6.1810 (AltArch) with Python  3.6 VirtualEnv
Component/platform:
Huawei Component
Description of problem:
Error in the logs related to unexpected value (presumably):
2019-02-25 16:57:53 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/home/ha/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 252, in async_update_ha_state
    icon = self.icon
  File "/home/ha/homeassistant/lib/python3.6/site-packages/homeassistant/components/huawei_lte/sensor.py", line 183, in icon
    return icon(self.state)
  File "/home/ha/homeassistant/lib/python3.6/site-packages/homeassistant/components/huawei_lte/sensor.py", line 91, in <lambda>
    x >= -60 and "mdi:signal-cellular-3"
TypeError: '>=' not supported between instances of 'str' and 'int'

I am really not sure you might need additional data, this seems to me a quite generic error while trying to assign an icon based on the signal rather than a missconfiguration on my side.
Best
Andrea

Hello,
This is because the Huawei modem can return out of range values, for example 'rssi >= -51dBm'.
I have submitted a patch several weeks ago ...
Regards,
Francis

Could you please link the patch location?

The pull request seems to have disappeared, and the architecture of the component has been modified since I have sent it.
The workaround is to replace the regex in sensor.py:format_default by
match = re.match(
r"([>=<])(?P.+?)\s(?P[a-zA-Z]+)\s*$", str(value))
to get rid of the extra chars.
Tested on a B525s-65a.
Note: there are other issues as well, and at least one I have yet to fix. The csrf field goes out of phase between the device and HA and login becomes impossible.


SHIFT BYTE MODE + GT/LT hex

implementation is messy - the xstring is stored as string right now?
https://github.com/abaplint/transpiler/issues/405
https://github.com/abaplint/transpiler/issues/398

thanks, nice trick with the gt, did not consider it before 😁


Node Decommissioning references a non existant command

I was reading through Node Decommissioning and was trying to hunt down the cockroach decommission command.
It took a bit of digging but it looks like the correct command is cockroach node decommission.

Thanks, @chrisseto. I'll fix this as part of broader decommission doc improvements.

This page has been taken offline in the meantime. Our decommissioning docs should be up-to-date: https://www.cockroachlabs.com/docs/v20.1/remove-nodes.html


feat: use actual promql image

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:

@rumstead did you verify that the changes that were there on the fork are already made or if the vulns are fixed on the original project?

@rumstead did you verify that the changes that were there on the fork are already made or if the vulns are fixed on the original project?

There doesn't seem to be any information on these "vulnerabilities". However, I checked the go.mod and the versions are == or greater than the ones in the current go.mod besides golang.org/x/text


[datasets] Add MJSynth (Synth90K)

This PR integrates the ability to load the MJSynth dataset MJSynth
This one is the first pure recognition dataset with ~ 9M english word images
It´s used in many other repositories to train a recognition model (in some cases in addition with crops from SynthText (maybe prepare this later)) before this will be evaluated on IC03, SVT, SVHN, and so on.
I have decided to integrate it not with the download link in fact that the http download takes ~48hrs and the BitTorrent download is a lot faster.
Any feedback is welcome :hugs:
sample:

@fg-mindee
Any chance to integrate this before we (discuss / refactor) the datasets into ocr/detection/recognition splits/tasks ?
How i have wrote you the idea behind this is more for research purpose most model benchmarks (recognition) are created on Mjsynth + SynthText merge for train and svt, ic03, ic13, ... for eval .. so if we want to do something like this we need it :sweat_smile:
And i agree the refactoring into task splits or better to say task specific totally :+1:

Depends on: #891  so for the moment revert to draft :smiley:

@charlesmindee ready to merge :+1:


Redraw gauge after changing section start/end

When using gauge.getSection().get(0).setStart() -> won't redraw until I redraw (resize) it manually
Adding change listeners to section start/end property should fix this issue, however I assume that Section doesn't have internal reference to parent gauge, so this is probably behavior needs to be implemented by changing(appending) to function addSection where for every Section needs to be done something like this section.startProperty.addListener(<redraw>)

The idea is not to change sections on the fly. I would like to avoid adding listeners to each section but I'll make some tests next week.

No problem, I can solve this myself (the ugly way, but works)

Sections will now fire an event of type SectionEvent.SECTION_UPDATE whenever a property changed. You can trigger a redraw of the gauge by using the following line
gauge.getSections().forEach(section -> section.setOnSectionUpdate(sectionEvent -> gauge.fireUpdateEvent(new UpdateEvent(YOUR_APP_CLASS.this, EventType.REDRAW))));

I hope that will help you to avoid "ugly" code ;)


portable vsCode deleting source files

Type: Bug
hi
i have worked with vscode in a portable configuration succefully for long time.
but then i used a setup type user config and then it statrs warning me that my files (that are ate \vscode\data\user-data\MyCode)  could be deleted.
When i updated vcCode it really DID delete all my files but not the folders under MyCode.
So i did  uninstall vscode using uninstall and recreated my vscode folder empty, extracted form the zip file vccode again and recreated folder data\user-data, data\extensions and  data\tmp and deleted folder .vscode under my  user folder.
after starting vscode again, it is writing extentions and tmp files on right folders under data folder but it still give me a warning that they could be deleted and it still recreated  .vscode under my currentuser folder.
Plz help me make vscode understand that it is a portable version again and stop wishing delete my files on a update
VS Code version: Code 1.92.0 (b1c0a14de1414fcdaa400695b4db1c0799bc3124, 2024-07-31T23:26:45.634Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz (16 x 3792)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
undefined

Memory (System)
63.89GB (53.07GB free)

Process Argv
--crash-reporter-id d14c0460-9620-4c79-bfb7-3cc550512a18

Screen Reader
no

VM
0%

Extensions (4)

Extension
Author (truncated)
Version

vscode-language-pack-pt-BR
MS-
1.92.2024073109

debugpy
ms-
2024.10.0

python
ms-
2024.12.1

vscode-pylance
ms-
2024.7.1

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
pythonnoceb:30805159
asynctok:30898717
pythonregdiag2:30936856
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
g316j359:31013175
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
dwnewjupytercf:31046870
impr_priority:31102340
refactort:31108082
ccpltc:31103427
pythonrstrctxt:31103193
wkspc-onlycs-c:31106320

any news?


The scraper does not show that Roads Design Engineer job was duplicated and posted twice

ENVIRONMENT:
https://admin.peviitor.ro/
Browser: Chrome
Device: Laptop
OS: Windows 10
STEPS TO REPRODUCE:
Enter url in browser
In go to "https://admin.peviitor.ro/" and click to jobs for "Arcadis"
Click on "Project Delivery Manager "tab on "Catre Job "option
EXPECTED RESULTS:
The page shows the full description of the job
ACTUAL RESULTS:
The page shows the same full description of the previous job announcement
See below the screenshots
Attachment:
Page from Validator for Arcadis

În validator apare doar un singur job cu "Project Delivery Manager" probabil celălalt nu mai există pe site-ul de cariere, dar și poze par a fi 2 joburi complet diferite. Uită-te atent la link ul jobului ca au id uri unice. Nu sunt duplicate.


Set up the update authors job

Proposed change

Github workflow setup for update authors job: fetches 100 latest commits and updates AUTHORS file.
Type of change

[ ] New country/market holidays support (thank you!)
[ ] Supported country/market holidays update (calendar discrepancy fix, localization)
[x] Existing code/documentation/test/process quality improvement (best practice, cleanup, refactoring, optimization)
[ ] Dependency update (version deprecation/upgrade)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (a code change causing existing functionality to break)
[ ] New feature (new python-holidays functionality in general)

Checklist

[x] I've followed the contributing guidelines
[x] I've run make pre-commit, it didn't generate any changes
[x] I've run make test, all tests passed locally

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
10547

Relevant Lines:
10547

💛  - Coveralls

Closing this out as AUTHORS file will be updated manually for now.


[Bug]: Images don't load with new CDN URL in theme dev environment (shopify theme dev)

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
Theme
Expected behavior
New CDN URLs are being implemented for some Shopify stores it seems.
All images and asset URLs generated by the appropriate liquid filter used to have a prefix like:
//cdn.shopify.com/s/files/.../products/
But now, for some stores, they're like this:
/cdn/shop/products/
This brings with it additional problems which are already affecting many stores I've checked. I've detailed them in a separate issue in the Shopify Liquid repo, which gets little to no attention it seems:
https://github.com/Shopify/liquid/issues/1708
If someone could get the attention of someone who can help, please link them to this issue.
However, this issue is specifically regarding the image assets loaded in shopify-cli dev.
A new CDN image URL looks like this:
/cdn/shop/files/the-name-of-your-image.jpg
Which the browser resolves to:
http://<IP_ADDRESS>:9292/cdn/shop/files/the-name-of-your-image.jpg
It would appear localhost will serve a 200 response but invalid image data so no image loads.
I've confirmed that some other theme devs have started experiencing this within the last 1-2 days.
However other assets like JavaScript and stylesheets and the like are served correctly through the new CDN URLs.
The only way to fix it currently is to prepend every image_url output with shop.url
Actual behavior
Images don't load.
Verbose output
-

Reproduction steps
You need to have a Shopify store that uses the new CDN URLs. It seems most stores are still using the old CDN URLs as mentioned earlier.
Operating System
Windows 11
Shopify CLI version (check your project's package.json if you're not sure)
3.45.1
Shell
No response
Node version (run node -v if you're not sure)
No response
What language and version are you using in your application?
No response

cc @Shopify/theme-developer-tools

@Shopify/theme-code-tools

hey @hedgehog90 thanks for reporting this, we have a team working on this. They've identified the root cause of the problem and are working on a fix.

Is this still not fixed?

We've encountered a significant increase in 404 errors correlating directly with the appearance of /file/ in the URL paths across our Shopify site. Initially, our logs indicated a minor number of 404s, but following recent changes, these have escalated dramatically, specifically after /file/ was introduced into the URL structure. While Shopify CDN URLs containing /file/ are resolving as expected, any attempt to access URLs with /file/ on our actual site results in a 404 error.
This issue suggests there might be a routing or path resolution problem within the Shopify environment when /file/ is included in the URL path. It's unclear whether this is due to a recent update or a change in the way Shopify handles static assets or URL routing. We have verified our theme and asset configurations to ensure no unintentional changes have been made that could contribute to this issue.
Any insights or suggestions on how to resolve these unexpected 404 errors would be greatly appreciated. Is there a known issue with the handling of /file/ in URLs, or could there be a specific configuration required to support this path structure without resulting in 404s?

Still not fixed.

I've the same issue


When i run the run_scripts/caption/train_caption_stage1.sh, i I encountered the following problem.

@logicwong
Thanks for releasing the amazing  work!
When i run the run_scripts/caption/train_caption_stage1.sh, i I encountered the following problem. Can you help me?
train.py: error: argument --max-epoch: invalid int value: '{2,}'
train.py: error: argument --max-epoch: invalid int value: '{2,}'
Traceback (most recent call last):
File "/home/ubuntu/miniconda3/envs/pytorch-zme/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/home/ubuntu/miniconda3/envs/pytorch-zme/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/home/ubuntu/miniconda3/envs/pytorch-zme/lib/python3.7/site-packages/torch/distributed/launch.py", line 340, in
main()
File "/home/ubuntu/miniconda3/envs/pytorch-zme/lib/python3.7/site-packages/torch/distributed/launch.py", line 326, in main
sigkill_handler(signal.SIGTERM, None)  # not coming back
File "/home/ubuntu/miniconda3/envs/pytorch-zme/lib/python3.7/site-packages/torch/distributed/launch.py", line 301, in sigkill_handler
raise subprocess.CalledProcessError(returncode=last_return_code, cmd=cmd)
subprocess.CalledProcessError: Command '['/home/ubuntu/miniconda3/envs/pytorch-zme/bin/python3', '-u', '../../

@cxy990729 Are you sure your local train_caption_stage1.sh is the same as the one on GitHub? Also, are you following the training procedures we provide?

I am sure my train_caption_stage1.sh is the same as the one on GitHub.
train.py: error: argument --max-epoch: invalid int value: '{2,}'
subprocess.CalledProcessError: Command '['/home/ubuntu/miniconda3/envs/pytorch-zme/bin/python3',...]' returned non-zero exit status 2.

I think my shell version judge the ‘for grammar’(for max_epoch in {2,_}) is wrong.

I think my shell version judge the ‘for grammar’(for max_epoch in {2,_}) is wrong. @logicwong

@logicwong OK, I see. The ‘for grammar’ is mainly used for hyper-parameter tuning. If you don't need to tune hyper-parameters, you can remove for max_epoch in {2,_} and set max_epoch directly.