RFP: VueScan

https://www.hamrick.com/

Of the few that exist, this is to my knowledge by far the best manufacturer-independent scanner software for Windows (comparable alternatives are much more expensive). Available for Mac OS and Linux as well.

As it brings its own drivers, it's also very useful for older scanners for which manufacturers don't provide updated drivers anymore (e. g. support for the latest Windows versions).

Nearly 6000 supported scanners: https://www.hamrick.com/vuescan/supported-scanners.html

30-day trial, "Standard" and "Professional" editions all use the same download, i. e. the same setup file (edition and thus available features are set by the serial number entered into the application). 32 and 64 bit versions are separate downloads, though: https://www.hamrick.com/old-versions.html

Updates every one to two weeks (e. g. in order to add drivers for new scanner hardware), so automation would make sense.

Status: Review
https://chocolatey.org/packages/vuescan

@chtof Here are alternative, direct download URLs without cloudfront, if you're interested. Don't know which ones are better, though.
Example for v9.6:
32 Bit:
https://www.hamrick.com/files/vuex3296.exe
64 Bit:
https://www.hamrick.com/files/vuex6496.exe

@RiseT  Great, thank you for these links and for your feedback!
You are true, the main download link ("big green download button") on the site was "adapted" to my OS system. And I checked once again and now I saw a download link for other OS, mobile etc...
Package has just been submitted with these changes.
Thanks again!

@chtof Hey, just tried to install the VueScan package and it failed because of a checksum error. When I inspected the current chocolateyinstall.ps1, I noticed that both "url" and "url64" contain the same 32 bit URL. So on my 64 bit system, it downloads the 32 bit version and compares its hash with the 64 bit hash, which of course fails.

@RiseT , corrected version has been published. Well, thanks again!

@RiseT  it fails again and the version of Vuescan has not changed. I think the file is built regularly and maybe something like a date change the checksum of the file:
PS C:*\GitHub\chocolatey-packages\automatic\vuescan> get-remotechecksum https://www.hamrick.com/files/vuex6496.exe
142bacb60e7047a003b6f62e595bc6b06f7e928d44cad17a156755976444f200
PS C:*\GitHub\chocolatey-packages\automatic\vuescan> get-remotechecksum https://www.hamrick.com/files/vuex3296.exe
4aab8beeca3857462dccb67c095dc0cb6f4e69f0121f2b22ffd9bc27f52307d9

Mh. Passed the automatic test & installing the current package went without problems for me.

@chtof I've noticed you're adding a start menu link manually in the latest script. Do you have any idea why the VueScan installer doesn't behave as usual with Chocolatey, i. e. doesn't place any links? I mean one would think an installer does what it always does, independently of Chocolatey.

The checksum changes every day (without new version released), so how to handle this?
Version 9.6.45 - Checksum was 4aab8beeca3857462dccb67c095dc0cb6f4e69f0121f2b22ffd9bc27f52307d9 when I submitted the package.
Yesterday, 20th of July:
get-remotechecksum https://www.hamrick.com/files/vuex3296.exe
ca2f24554df70313ca9d34afbdeab374e353b66cc76c77219e12503c66b79286
Today, 21th of July:
get-remotechecksum https://www.hamrick.com/files/vuex3296.exe
9abaf104ea5fb5697766625aedd5d560aac5d922bdda0ae50a5b7531bac379cb

@ferventcoder Any idea what to do if checksums change on a daily basis without a version change?

@RiseT The author could genuinely be updating the software but not updating the version (happens a LOT). Or they could be doing it to generate a new checksum and defeats direct links to the file from something like Chocolatey. Either way I can't see a way around it.
A suggestion may be to look at embedding the software either using the redistribution rights in the license (if it allows it) or reaching out to the software author directly to see if they would allow it. Note I haven't looked at the license so the first part may be a complete non-starter.

VueScan has been updated to 9.6.46, so you can check if the automatic script generation works.

@RiseT The automatic update has failed as I have had the bad idea to rename for this package on my computer for example chocolateyinstall.ps1 into chocolateyInstall.ps1 and github desktop doesn't published a such change and so, update.ps1 doesn't find the renamed file.
The first point is to know how to handle this package as its checksum changes regularly for a same version. I have written to the editor and he isn't interested to improve this situation, even if it was a way to promote his software without embedding his software but only to give an easier way to install it.
I have raised an issue to Chocolatey support an "-insecure" option but it can take times to have an answer as it needs to know if it would be a good idea to integrate such packages and even if it is case, it would take time to implement it.

@chtof do the version stay exactly the same every time? if not, you could perhaps use something similar to what I am doing for the origin package (checking the response for if the etag have changed, if so create push a new version).
https://github.com/AdmiringWorm/chocolatey-packages/blob/develop/scripts/Update-OnHeaderChanged.ps1
and
https://github.com/AdmiringWorm/chocolatey-packages/blob/develop/automatic/origin/update.ps1#L37 (The call name is different due to having a small helper between the actual script and the updater).
If the version stay the same, there is also the option to set the global variable ($global:au_Force = $true) to force a fix version. Just remember to reset it when the package is updated.

I have written to the editor and he isn't interested to improve this situation, even if it was a way to promote his software without embedding his software but only to give an easier way to install it.

Except for for the people checking out VueScan just as a trial, those who will utiliize this chocolatey package are customers who have purchased VueScan 😠

@RiseT What abour to end your request as customer to the software editor, it can helps.

@RiseT What about to send your request as customer to the software editor, it can helps.

@AdmiringWorm
The version stated within the (setup) file name only changes for major versions (like 9.5 or 9.6), while on the download page, the full version (9.6.46) is mentioned:
https://www.hamrick.com/alternate-versions.html
Also, the properties of the setup file contain the full version (e. g. <IP_ADDRESS>):

@chtof Will do, although I'm somewhat in doubt that it will have any effect.

@RiseT I think it would be appropriate to use just the first 3-parts, then when the checksum changed to use the 4th part as the fix version (ie <IP_ADDRESS>90726, the date is recommended to be used as a fix part of the version)

@chtof

I have written to the editor and he isn't interested to improve this situation, even if it was a way to promote his software without embedding his software but only to give an easier way to install it.

Sorry, I've tried, and same here...

Status: Published
https://chocolatey.org/packages/vuescan
Can be closed.


vMX 16.X doesnt build

Processing triggers for libc-bin (2.19-18+deb8u4) ...
Processing triggers for systemd (215-17+deb8u4) ...
Processing triggers for ca-certificates (20141019+deb8u1) ...
Updating certificates in /etc/ssl/certs... 174 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d....done.
Processing triggers for sgml-base (1.26+nmu4) ...
 ---> d3fd7302ac99
Removing intermediate container 1ab53b3a4bfb
Step 5 : ARG IMAGE
 ---> Running in ec20630d13fe
 ---> 693addb228a1
Removing intermediate container ec20630d13fe
Step 6 : COPY $IMAGE /vmx.tgz
 ---> 6eb1d568022c
Removing intermediate container 639d4e8abc6f
Step 7 : COPY install_vmx.sh /
 ---> 4fa144fbef14
Removing intermediate container bf0fee94f8ca
Step 8 : RUN /install_vmx.sh
 ---> Running in 4c9ad9bd1be9
Installing Juniper vMX
vmx-16.1R1.7/images/vmxhdd.img
vmx-16.1R1.7/images/vFPC-20160617.img
vmx-16.1R1.7/images/metadata_usb.img
'/tmp/vmx-16.1R1.7/images/vmxhdd.img' -> '/vmx/vmxhdd.img'
mv: cannot stat '/tmp/vmx*/images/jinstall64-vmx*img': No such file or directory
'/tmp/vmx-16.1R1.7/images/vFPC-20160617.img' -> '/vmx/vfpc.img'
'/tmp/vmx-16.1R1.7/images/metadata_usb.img' -> '/vmx/metadata_usb.img'
removed '/vmx.tgz'
removed directory: '/tmp/vmx-16.1R1.7/images'
removed directory: '/tmp/vmx-16.1R1.7'
removed directory: '/tmp'

Something changed between 15.1 and 16.1

Unsure if local issue or related to the fact that this does not build:
Additional info:
[root@dockerlab ~]# docker run -i --rm --name 16.1R1.7 vr-vmx:16.1R1.7
add bridge failed: Operation not permitted
qemu-system-x86_64: -netdev tap,ifname=vcp1,id=vcp1,script=no,downscript=no: could not open /dev/net/tun: No such file or directory
qemu-system-x86_64: -netdev tap,ifname=vcp1,id=vcp1,script=no,downscript=no: Device 'tap' could not be initialized
Could not access KVM kernel module: No such file or directory
failed to initialize KVM: No such file or directory
interface vcp1 does not exist!
interface vfpc1 does not exist!
 The .img file has moved so we need to fix that. Secondly you are running the container without --privileged which is probably the reason it fails in creating bridges and stuff like that.

I think the XRv & sros images can be run without --privileged, although significantly slower as it wouldn't use hardware virt support. For vMX we can't since we are building a bridge to connect the VCP and vFPC. I think we can replace that bridge with a UDP/TCP interface and thus be able to run without --privileged too.

I recommend you test with these publicly downloadable vMXs files
[root@dockerlab vmx]# md5sum *.tgz
8f06a8ac057f303bf1614bace28d858a  vmx-14.1R5.4-1.tgz
eb128cffde6ab29fdb27b2f52301c5f9  vmx-bundle-15.1F6.9.tgz
d96766848731c12c0492e3ae2349b426  vmx-bundle-16.1R1.7.tgz

Try now! :)


Popup on icon only

Is there a easy way to make the calendar popup only when clicking on the icon and not the input field as well?

Yep, just move the input outside of the a tag.


nfs: use repo from SIG

RPMs for nfs-ganesha aren't hosted anymore at https://download.ceph.com
Signed-off-by: Guillaume Abrioux<EMAIL_ADDRESS>

jenkins test centos-non_container-all_daemons

jenkins test centos-non_container-all_daemons


HBASE-28244 ProcedureTestingUtility.restart is broken sometimes after…

… HBASE-28199

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 28s
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 20s
Maven dependency ordering for branch

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

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

+1 :green_heart:
checkstyle
0m 51s
master passed

+1 :green_heart:
spotless
0m 48s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m  6s
master passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
checkstyle
0m 51s
the patch passed

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

+1 :green_heart:
hadoopcheck
12m 57s
Patch does not cause any errors with Hadoop 3.2.4 3.3.6.

+1 :green_heart:
spotless
1m 14s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
3m  7s
the patch passed

_ Other Tests _

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

47m 51s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5563/1/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 9f021796bb8b 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 25e9228e2c

Default Java
Eclipse Adoptium-11.0.17+8

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

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

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5563/1/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 14s
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 13s
Maven dependency ordering for branch

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

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

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

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

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
1m 58s
hbase-procedure in the patch passed.

-1 :x:
unit
282m 27s
hbase-server in the patch failed.

315m 31s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5563/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 453d54a0c2d3 5.4.0-166-generic #183-Ubuntu SMP Mon Oct 2 11:28:33 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 25e9228e2c

Default Java
Temurin-1.8.0_352-b08

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

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

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

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

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5563/1/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

The failure for TestRollbackSCP is because there are races between rollbacking a OpenRegionProcedure and reportRegionStateTransition.
When rollbacking, we will set the state to rolledback, for recording metrics, and then we will just delete the procedure, but at the same time, a reportRegionStateTransition call is arrived and then persist the rolledback state to procedure store...
Need to find out a way to deal with this...

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 41s
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 11s
Maven dependency ordering for branch

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

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

+1 :green_heart:
checkstyle
0m 47s
master passed

+1 :green_heart:
spotless
0m 44s
branch has no errors when running spotless:check.

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

_ Patch Compile Tests _

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

+1 :green_heart:
mvninstall
2m 35s
the patch passed

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

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

+1 :green_heart:
checkstyle
0m 45s
the patch passed

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

+1 :green_heart:
hadoopcheck
9m 27s
Patch does not cause any errors with Hadoop 3.2.4 3.3.6.

+1 :green_heart:
spotless
0m 41s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 10s
the patch passed

_ Other Tests _

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

34m 55s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5563/2/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 7fe088ecaf4f 5.4.0-163-generic #180-Ubuntu SMP Tue Sep 5 13:21:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 6e421e9d94

Default Java
Eclipse Adoptium-11.0.17+8

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

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

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5563/2/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 31s
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 16s
Maven dependency ordering for branch

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

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

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

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

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
1m 57s
hbase-procedure in the patch passed.

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

294m  0s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5563/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 189776d6f194 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 6e421e9d94

Default Java
Eclipse Adoptium-11.0.17+8

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

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

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

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

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5563/2/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 23s
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 16s
Maven dependency ordering for branch

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

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

+1 :green_heart:
checkstyle
0m 49s
master passed

+1 :green_heart:
spotless
0m 51s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 19s
master passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
checkstyle
0m 48s
the patch passed

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

+1 :green_heart:
hadoopcheck
13m 45s
Patch does not cause any errors with Hadoop 3.2.4 3.3.6.

+1 :green_heart:
spotless
0m 52s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m 37s
the patch passed

_ Other Tests _

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

47m  9s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5563/3/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux eff2f9807938 5.4.0-166-generic #183-Ubuntu SMP Mon Oct 2 11:28:33 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 82a2ce10f2

Default Java
Eclipse Adoptium-11.0.17+8

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

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

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

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 14s
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 11s
Maven dependency ordering for branch

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

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

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

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

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
1m 34s
hbase-procedure in the patch passed.

-1 :x:
unit
229m  8s
hbase-server in the patch failed.

258m 48s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5563/3/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux c3d90ec3f5ae 5.4.0-166-generic #183-Ubuntu SMP Mon Oct 2 11:28:33 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 82a2ce10f2

Default Java
Temurin-1.8.0_352-b08

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5563/3/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-hbase-server.txt

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

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

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

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

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 36s
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 27s
Maven dependency ordering for branch

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

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

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

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

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

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

-1 :x:
unit
261m 42s
hbase-server in the patch failed.

291m  6s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5563/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 233c79575acf 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 82a2ce10f2

Default Java
Eclipse Adoptium-11.0.17+8

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

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

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

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

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

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 43s
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 26s
Maven dependency ordering for branch

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

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

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

+1 :green_heart:
spotless
0m 48s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
2m  6s
master passed

_ Patch Compile Tests _

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

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

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

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

+1 :green_heart:
checkstyle
0m 47s
the patch passed

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

+1 :green_heart:
hadoopcheck
13m 26s
Patch does not cause any errors with Hadoop 3.2.4 3.3.6.

+1 :green_heart:
spotless
1m  9s
patch has no errors when running spotless:check.

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

_ Other Tests _

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

48m 21s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5563/4/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 210b14faa695 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 82a2ce10f2

Default Java
Eclipse Adoptium-11.0.17+8

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

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

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

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 40s
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 16s
Maven dependency ordering for branch

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

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

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

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

_ Patch Compile Tests _

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

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
1m 36s
hbase-procedure in the patch passed.

+1 :green_heart:
unit
219m 23s
hbase-server in the patch passed.

250m 12s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5563/4/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 967dbe444a72 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 82a2ce10f2

Default Java
Eclipse Adoptium-11.0.17+8

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

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

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

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

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 16s
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 14s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 20s
master passed

+1 :green_heart:
compile
0m 54s
master passed

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

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

_ Patch Compile Tests _

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

+1 :green_heart:
mvninstall
2m 19s
the patch passed

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
1m 29s
hbase-procedure in the patch passed.

+1 :green_heart:
unit
250m 32s
hbase-server in the patch passed.

274m 29s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5563/4/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 94b1b482d827 5.4.0-166-generic #183-Ubuntu SMP Mon Oct 2 11:28:33 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 82a2ce10f2

Default Java
Temurin-1.8.0_352-b08

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

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

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

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

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.


Bazel fix

Do not review yet. This is pending on the fixes in rules_go and bazel.

Pending on https://github.com/bazelbuild/rules_go/pull/228


Dl/tf rb sparsity distr mask

It seems to be working, but I don't know how to check distributed masks properly. In eager mode tf runs all operation in synchro mode thus eager mode isn't capable to test distributed masks.  @alexsu52 @andrey-churkin, could you please suggest how to check it?

Please check https://github.com/daniil-lyakhov/nncf/commit/bcf991e072ee16e9175655b9c09a51e648989bc4
tf.print confirms that seeds is equal on each replica
config:
--config
configs/sparsity/resnet50_imagenet_rb_sparsity.json
--data
/home/dlyakhov/datasets/tfds/imagenet2012
--mode
test
--batch-size
4


Docs & Features

Hi, we've been using Celery for a while on our projects, but it's been a pain with all the complexity and confusing/conflicting documentation (not to say the lack of).
There are a few features we are looking for on a new job queue lib, I was wondering what are your thoughts on it, and plans going forward.

Progress / Meta Data: we heavily use meta data on Celery tasks (self.update_state(state='PENDING', meta={'current': i, 'total': NTOTAL}) on a task with bind=True. I couldn't find anything on more granular/custom state handler on any of the libs we've found (Arq, RQ, Saq, Dramatiq), wondering what are the plans/thoughts on that. I would imagine that I could do something similar using the context, maybe?
Dynamic Schedule: we have used Redbeat to make Celery's Beat module dynamic, so we can be able to turn on/off a schedule programatically (that wasn't possible with Celery's Beat only). Given the examples I would think this should be possible, but couldn't find a way to do it.
Retry Logic: The way we are currently using retry logic is a bit weird, raise self.retry(exc=Exception(str(error)), countdown=countdown, max_retries=5) but it's been working well... wondering how would I go by doing retries using Saq.
Gevent: Out app runs with about 250 MB of memory, so leveraging N workers can be taxing on RAM (tasks are complex - many functions - and I/O heavy, taking up to 3-4 minutes). So in this scenario Celery gevent worker with concurrency has been great, not many workers, a ton of parallel tasks. I think Dramatiq has implemented greenlets, but RQ hasn't (there is code somewhere in the wild that implements a custom Gevent Worker if I'm not mistaken)
Different Queues / Priority: while we don't use the priority concept directly, we do leverage different queues (and workers that execute on specific queues only), wondering how could we implement this in Saq.

Also, just to add to the discussion and share my experiences:

RQ: For now we decided not to go that route because of the lack of concurrency, the API seems pretty nice though.
Celery: a huge pain to setup, manage and debug. Bad documentation, confusing, and even worse error messages (think of Celery and Flask contexts)
Dramatiq: seems nice, I tend to like RQ API's better, but the scheduler has to be a third party library. Still want to invest more time understanding the library.
Arq: seems great also, but it does look like is less mature than the libraries above (documentation, material, help etc), also couldn't explicitly find the things I was looking for.

I know this is quite a list in terms of features, I was just wondering what are your thoughts and if you reckon it could make sense for the future. I'm probably not the most knowledgable person, but I would be more than happy to help!
Thanks!

@lowercase00 saq already has progress metadata, you can just do job.update(progress=0.2) in terms of intermediate state, you can already do that with a custom result object, you can store anything you want in results, but happy to discuss other options
i'm not sure what you mean by dynamic schedule, right now you can schedule a job for later or do a cron
i don't understand what you're asking for retry logic?
we use asyncio, so if your code is async, you can run many concurrent workers with limited overhead
yes, this is easily done in saq, simply having a new settings hash with a different queue name.

I'm happy to continue answering more questions here, but I'm going to close the issue for now.


f7-input clear-button not working

This code:
<f7-input type="text" clear-button :value="budget" @input="budget = $event.target.value">
But 'clear-button' not working ，'budget' stay filled with old values
What should I do？

Can you please provide a fiddle with the issue?

Try this
@change="budget = $event.target.value"
, it should work.

@nolimits4web @almazk Thanks, I tried this @change="budget = $event.target.value", it work.


License

Adding license to the code.
Following a path similar to cmssw.

We could use https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files perhaps

Once a new release is made (or an old one) we should upload to zenodo https://zenodo.org/ so a DOI can be made

Finally! I tried to advocate for that years ago in the HComb meeting :)

For what concern the CITATION, I added a CITATION.md file, for the moment.

@guitargeek, since you are the only non-CMS contributor at the moment, should we assume that you are fine with the License above (when we will manage to converge)?

Yes, thanks for asking, I'm completely okay with it and I think using the same license as CMSSW is a good approach!

Any objections to closing this, now that a license has been assigned (see: https://github.com/cms-analysis/HiggsAnalysis-CombinedLimit/commit/43d983dd8e2261696e30216d797d43ad72fa80cb)?

Ok with me


gulp build.dev and gulp serve.dev fail with Error: Cannot find module

May seem related to #711 but I have Nodejs 6.0.0, tsc 1.8.10, NPM 3.8.6 @ MacOS 10.11
$ sudo npm run build.dev
gives error:
><EMAIL_ADDRESS>build.dev /Users/myaccount/angular-2-ts/angular2-seed
> gulp build.dev --color

(node:17291) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
[20:12:48] Loading tasks folder /Users/myaccount/angular-2-ts/angular2-seed/tools/tasks/seed
[20:12:48] Registering task /Users/myaccount/angular-2-ts/angular2-seed/tools/tasks/seed/build.assets.dev
[20:12:48] Registering task /Users/myaccount/angular-2-ts/angular2-seed/tools/tasks/seed/build.assets.prod
//..so on
[20:12:48] Loading tasks folder /Users/myaccount/angular-2-ts/angular2-seed/tools/tasks/project
[20:12:48] Registering task /Users/myaccount/angular-2-ts/angular2-seed/tools/tasks/project/sample.task
[20:12:48] Using gulpfile ~/angular-2-ts/angular2-seed/gulpfile.js
[20:12:48] Starting 'build.dev'...
[20:12:48] Starting 'clean.dev'...
[20:12:48] 'clean.dev' errored after 198 μs
[20:12:48] Error: Cannot find module '/Users/myaccount/angular-2-ts/angular2-seed/tools/tasks/seed/clean.dev'
    at Function.Module._resolveFilename (module.js:438:15)
    at Function.Module._load (module.js:386:25)
    at Module.require (module.js:466:17)
    at require (internal/module.js:20:19)
    at Gulp.<anonymous> (/Users/myaccount/angular-2-ts/angular2-seed/tools/utils/seed/tasks_tools.js:16:20)
    at module.exports (/Users/myaccount/angular-2-ts/angular2-seed/node_modules/orchestrator/lib/runTask.js:34:7)
    at Gulp.Orchestrator._runTask (/Users/myaccount/angular-2-ts/angular2-seed/node_modules/orchestrator/index.js:273:3)
    at Gulp.Orchestrator._runStep (/Users/myaccount/angular-2-ts/angular2-seed/node_modules/orchestrator/index.js:214:10)
    at Gulp.Orchestrator.start (/Users/myaccount/angular-2-ts/angular2-seed/node_modules/orchestrator/index.js:134:8)
    at runNextSet (/Users/myaccount/angular-2-ts/angular2-seed/node_modules/run-sequence/index.js:86:16)```

, same goes to any task like ```gulp serve.dev --color```

Have you tried deleting node_modules adn typings directories. and npm init again?

npm update you mean? tried that, no luck

Hi @shershen08, if it is not too much of a hassle, could you try to downgrade to Node 5.x, if it is still reproducable? If have a feeling that it might be a Node 6 related issue.
Greetings
Dope

@TheDonDope , tried downgrading to 5.0.0, still having issues.
I've posted some relevant details here - http://stackoverflow.com/questions/37346512/how-to-fix-fs-re-evaluating-native-module-sources-is-not-supported-graceful)
Now I have NPM 2.15.1, NodeJS v4.4.3
and heres's current stacktrace
Using gulpfile ~/_Other/angular-2-ts/angular2-seed/gulpfile.js
[11:10:55] Starting 'serve.dev'...
[11:10:55] Starting 'build.dev'...
[11:10:55] Starting 'clean.dev'...
[11:10:55] 'clean.dev' errored after 677 μs
[11:10:55] Error: Cannot find module '/Users/myaccount/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/clean.dev'
    at Function.Module._resolveFilename (module.js:325:15)
    at Function.Module._load (module.js:276:25)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Gulp.<anonymous> (/Users/myaccount/_Other/angular-2-ts/angular2-seed/tools/utils/seed/tasks_tools.js:16:20)
    at module.exports (/Users/myaccount/_Other/angular-2-ts/angular2-seed/node_modules/gulp/node_modules/orchestrator/lib/runTask.js:34:7)
    at Gulp.Orchestrator._runTask (/Users/myaccount/_Other/angular-2-ts/angular2-seed/node_modules/gulp/node_modules/orchestrator/index.js:273:3)
    at Gulp.Orchestrator._runStep (/Users/myaccount/_Other/angular-2-ts/angular2-seed/node_modules/gulp/node_modules/orchestrator/index.js:214:10)
    at Gulp.Orchestrator.start (/Users/myaccount/_Other/angular-2-ts/angular2-seed/node_modules/gulp/node_modules/orchestrator/index.js:134:8)
    at runNextSet (/Users/myaccount/_Other/angular-2-ts/angular2-seed/node_modules/run-sequence/index.js:86:16)

@shershen08 It looks like require function is redefined at some point (looking for a .js file which doesn't exist instead of a .ts). It should be patched/replaced by ts-node/register but for reason at this point this is not working.
To workaround this issue, you can compile the tools with npm run gulp -- build.tools (to clean the folder up npm run gulp -- clean.tools).

I've tried npm run gulp -- clean.tools and npm run gulp -- build.tools - but they both fail witht he same kind of output:
$ npm run gulp -- clean.tools
><EMAIL_ADDRESS>gulp /Users/myuserfolder/_Other/angular-2-ts/angular2-seed
> gulp "clean.tools"

[16:34:47] Loading tasks folder /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/build.assets.dev
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/build.assets.prod
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/build.bundles.app
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/build.bundles
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/build.docs
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/build.html_css
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/build.index.dev
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/build.index.prod
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/build.js.dev
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/build.js.e2e
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/build.js.prod
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/build.js.test
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/build.js.tools
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/check.versions
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/clean.all
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/clean.dev
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/clean.prod
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/clean.tools
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/copy.js.prod
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/css-lint
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/karma.start
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/serve.coverage
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/serve.docs
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/server.prod
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/server.start
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/tslint
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/watch.dev
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/watch.e2e
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/watch.test
[16:34:47] Loading tasks folder /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/project
[16:34:47] Registering task /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/project/sample.task
[16:34:47] Using gulpfile ~/_Other/angular-2-ts/angular2-seed/gulpfile.js
[16:34:47] Starting 'clean.tools'...
[16:34:47] 'clean.tools' errored after 182 μs
[16:34:47] Error: Cannot find module '/Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/tasks/seed/clean.tools'
    at Function.Module._resolveFilename (module.js:325:15)
    at Function.Module._load (module.js:276:25)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Gulp.<anonymous> (/Users/myuserfolder/_Other/angular-2-ts/angular2-seed/tools/utils/seed/tasks_tools.js:16:20)
    at module.exports (/Users/myuserfolder/_Other/angular-2-ts/angular2-seed/node_modules/gulp/node_modules/orchestrator/lib/runTask.js:34:7)
    at Gulp.Orchestrator._runTask (/Users/myuserfolder/_Other/angular-2-ts/angular2-seed/node_modules/gulp/node_modules/orchestrator/index.js:273:3)
    at Gulp.Orchestrator._runStep (/Users/myuserfolder/_Other/angular-2-ts/angular2-seed/node_modules/gulp/node_modules/orchestrator/index.js:214:10)
    at Gulp.Orchestrator.start (/Users/myuserfolder/_Other/angular-2-ts/angular2-seed/node_modules/gulp/node_modules/orchestrator/index.js:134:8)
    at /Users/myuserfolder/_Other/angular-2-ts/angular2-seed/node_modules/gulp/bin/gulp.js:129:20

npm ERR! Darwin 15.4.0
npm ERR! argv "/usr/local/Cellar/node4-lts/4.4.4/bin/node" "/usr/local/bin/npm" "run" "gulp" "--" "clean.tools"
npm ERR! node v4.4.4
npm ERR! npm  v2.15.1

@ludohenin thank you for the pointer - "It looks like require function is redefined at some point (looking for a .js file which doesn't exist instead of a .ts"

actually I had both gulpfile.js and gulpfile.ts in my directory!

removing the gulpfile.js helped!

I am still having this issue with all versions of node I try. What is the --color?


new constructor for json string

--- @jelic98 ---

Gradle Upgrade
Upgrade Android Dependencies
Added a new Constructor for a JSON String
Added a new Option so ONLY_STRING

Thank you for contributing.


Fix the bug with extra qualification ‘mlperf::loadgen::PerformanceSum…

…mary:: for gcc
labuser@dalibeast06:~/Work/Projects/MlPerf/inference/loadgen/build$ make
Scanning dependencies of target mlperf_loadgen
[ 12%] Building CXX object CMakeFiles/mlperf_loadgen.dir/loadgen.cc.o
/home/labuser/Work/Projects/MlPerf/inference/loadgen/loadgen.cc:748:3: error: extra qualification ‘mlperf::loadgen::PerformanceSummary::’ on member ‘PerformanceSummary’ [-fpermissive]
PerformanceSummary::PerformanceSummary(
^
CMakeFiles/mlperf_loadgen.dir/build.make:86: recipe for target 'CMakeFiles/mlperf_loadgen.dir/loadgen.cc.o' failed
make[2]: *** [CMakeFiles/mlperf_loadgen.dir/loadgen.cc.o] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/mlperf_loadgen.dir/all' failed
make[1]: *** [CMakeFiles/mlperf_loadgen.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
labuser@dalibeast06:~/Work/Projects/MlPerf/inference/loadgen/build$
labuser@dalibeast06:~/Work/Projects/MlPerf/inference/loadgen/build$ c++ --version
c++ (Ubuntu 5.4.0-6ubuntu1~16.04.10) 5.4.0 20160609
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
labuser@dalibeast06:~/Work/Projects/MlPerf/inference/loadgen/build$

https://github.com/mlperf/inference/pull/379

Thanks @goldgeisser and @guschmue. Closing this one out.


Add action to expand/collapse all nodes in call hierarchy

I would like to reconsider #81857, the feature seems extremely welcomed.
To address the possible loop problem, we could add a max depth restriction as a quick solution (and in the future detect the loops maybe).
@jrieken @miguelsolorio

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_smiling_face: This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Update for CastorGUI Changes

Features GUI file HTML GUI added since lots of questions asked about different GUIs can give this as a ref in the forum.
Plus update following changes Dad72 made to CastorGUI

Thanks for the changes.


Added shorthand for git rev-parse

I have added a command grp as a shorthand for git rev-parse. It's an annoying long command.

This isn't used as often as to require an alias. Completion is your friend ;)


Add Function keys to shortcut guide

Summary of the new feature/enhancement
Some applications make use of the function keys, F1-F9, for shortcuts. Please add them to the shortcut overlay.

Shortcut guide is for OS level shortcuts.  #130 is what i think you're semi asking for, no?

That may cover it. However, they are not always OS level I believe, e,g. my editor uses:
F5 - insert data and time
F6 - Back in edited files
F7 - Next comparison mark
F9 - Focus Editor
F10 - Files Panel
F11 - Word Wrap

These are per app however.    VS Code for instance.  For F5, in Visual Studio, that is Building and running your application
If this is something you think you'd want to start building out, happy to help out but right now i think this would be low priority of a PowerToy.  We may be able to leverage work from #130 to enable this so it is programmatic.

#130 is searchable menu items which this feels more in tune there.  This has been xref'ed so we'll look at it when it gets there.


calling play() is slow

I have 700 audio files that I manually loop by checking their playhead position against their duration.
In previous versions on an older system this worked fine.
But on OSX 10.12 with OF 0.10. this slowed my app down to 1fps.
So I made a custom resetToStart() function that basically does the same as play() but does not all of the priming.
https://github.com/antimodular/ofxAudioUnit/blob/b09d380ce3396c38aa700e4d5ca2ef7c112bc15b/src/ofxAudioUnitFilePlayer.cpp#L267-L293

are you compiling ok for 0.10 ?


Disable swarm tracker logging

Is it possible to disable the log messages you get when running Quantum that look like this:
2018-10-04T09:30:50.892Z info [swarm on nonode@nohost] [tracker:init] started

I don’t think so, but you can use a library like this one to more selectively log messages: https://hexdocs.pm/flex_logger/FlexLogger.html


codec: Raise max_request_headers_kb limit to 96 KiB

Signed-off-by: Auni Ahsan<EMAIL_ADDRESS>Bump up max configurable max_request_headers_kb to 96 KiB.
Add a check to http1/codec_impl.cc for headers size.
Raise the default library limits in http_parser (at compilation) and nghttp2 (at options) to 0x7fffffff, so we'll rely on our own codec check.
Risk Level: Medium.
Testing: Moved all the large request headers tests to ProtocolIntegrationTest.
Part of #5626.

What's missing this PR is an actual runtime call of http_parser_set_max_header_size. That will go in the Http conn manager config, but it's impossible to test AFAIK because the proto validator limit is lower than the http_parser default limit. When the limit is bumped past 80kb, i'll add an http1 integration test and a settings call to conn manager/config.cc.

Hey Auni, as discussed offline, ping me when CI is happy?
/wait

Hi! I need some input on how to resolve this. Essentially, my test is failing because the nghttp2 library max request headers check, which I now manually configure, trips differently from the existing codec check. The codec check at codec_impl.cc:563 will check if the headers exceed the limit and reset the stream if so, while the nghttp2 library check will just flat-out close the stream.
How should I resolve this? Two ideas:

In the onStreamClose callback check if the nghttp2 limit was reached and interrupt with a reset stream if so. (Not sure if this is possible or logical.)
Set the nghttp2 limit to something arbitrarily higher and solely rely on our own check, whose behaviour we're in more control of. I was thinking either the max configurable limit from envoy; though since that would have to be edited twice each time the config limit is changed, maybe the configured limit + 1 would work.

Thoughts?

Ahh, some more details. The library check triggers before any header bytes are dispatched to the library, so server_callbacks_.newStream() is never called (and so it's never reset, which is why my test fails). So yeah again, I could configure the library check up high as I suggested to never get hit, or we could decide that behaviour is useful.

OK so I went with an arbitrarily hard-coded nghttp2 max-header-len setting of 100kb. This can be easily changed or be configurable later, but this changes no envoy behaviour. (Both before and after this PR, the nghttp2 max check will not ever be triggered.)

/retest

Hi @mattklein123, working on some changes to this. I'm having an issue with the http codec configuration I could use some input on.
Basically, to set the http parser limits you need to call http_parser_set_max_header_size(x). What I'm finding from my testing is that this setting persists across test runs, i.e. making that call in one http1/codec_impl test affects the success of a different test. I had thought previously that each envoy codec would be instantiating its http parser separately, but it looks like these settings are global. Does that make sense?

I had thought previously that each envoy codec would be instantiating its http parser separately, but it looks like these settings are global. Does that make sense?

Did you look at the http_parser code? I'm guessing it's setting some global variable (unfortunately).

Indeed it is. I think for now I'll make this http_set_parser call just one time, in the conn manager config. This could be messy if we ever set up per-service header limiting or something like that.

Alright, I did a bunch of cleanup here. Notable changes:

http_parser_set_max_header_size is called by conn manager/config.cc. In my codec tests I manually set the limits on instantiation, and the limits are tested in integration test. Unfortunately I was unable to add a unit test to conn manager/config_test.cc, because this sets a static global variable my test has no way of accessing.
I changed the expected error code to 400. This should be 431, but I need to work out how to do that. The 431 error code came from the conn manager impl rejecting the request, but now the HPE_HEADER_OVERFLOW dispatch error comes from the http_parser codec library before the conn manager checks it. I need to catch that dispatch error and reject the request at the http1 codec, but I'm not sure of what the neatest way to do that is.

@mattklein123: OK, how about this. I have DEFAULT_MAX_REQUEST_HEADERS_KB defined in codec.h. I'll add a MAX_CONFIGURABLE_MAX_REQUEST_HEADERS_KB, which will be equal to the maximum setting in the conn manager proto. (If there's to infer the max proto invalidation programmatically that would be cool.)
In response to your comment on nghttp2: yes, a different codec could theoretically exceed this limit, but that can't actually happen because the hard-coded 100kb I set is higher than the max configurable (96kb) in the conn manager.
On the http1 side, I'm fine with doing the same thing and just never touching the http_parser max limit once it's been set super high. An HTTP/1-specific check is totally doable, but also maybe not even needed since the conn manager has its own check. The reason this http_parser check is coming up now is because I'm bumping the limit up, so if it's just by default set higher than the max configurable of 96 that's chill.

Cleaned up comments with KiB.

Set both libraries' max request headers checks to 0x7fffffff, effectively disabling them and relying on our own checks. This fixes the 431 error code problem too.

Remove http1/codec_impl_test.cc tests for headers being rejected, since the http1 codec now never rejects large request headers. In the integration test, http1 large headers will hit the codec_impl.cc check.

OK bless got, did the following:

Added back reject-case tests to http1/codec_impl_test.
Added a check in http1/codec_impl onHeaderValue. Lmk if there's a better spot for that, but tests pass!!!!

Wahu my tests pass, had to make some kind of clunky test interface changes (these need a bigger refactor).

Okaaay so did the following:

max_request_headers_kb_ -> max_headers_kb_ in the ConnectionImpl.

ServerConnectionImpl passes stuff in the same.

ClientConnectionImpl gets a max_response_headers_kb_ parameter, but it's just default set to a big number. DIdn't want to expose the max_response interface in this PR without more testing around it. As well, the exception itself has to be request/response agnostic, "headers are too large", though that could be reworked later.

Oky I changed the ClientConnectionImpl max response headers from a default parameter to a class constant, added a test for large response headers rejection, and tweaked the API comment.

Ok, updated with Matt's suggestion on the API commenting + added a note on nghttp2 to the test file. I got a mysql_integration_test failure, hoping that was a flake bc idk how I'd have touched that.

Yep, that's a known and fixed flake.  If you merge master you'll pick up the fix

!rekick

/retest

cc @RyanTheOptimist @yanavlasov @KBaichoo also on ^

@ramaraochavali Can you file an issue about there were we can discuss the details? I think that's probably better than a 4 year old already committed PR :) Please feel free to link to this PR or any related issues there.

@RyanTheOptimist  created https://github.com/envoyproxy/envoy/issues/26690


AttributeError: 'Model3' object has no attribute 'f'

Fix for the below error in lessson7-human-numbers.py

Fix: def reset(self): self.h = torch.zeros(bs, nh).cuda()

Thanks a lot for your PR!
Sadly, I can't merge this PR because of conflicts in lesson3-camvid notebook (I don't think you wanted to change anything there) and I made a mistake by using the web interface (I though delete would remove it from the PR but it wants to remove it entirely from the repo now...)
I'd suggest closing this PR, making sure you are on par with master then redo your change in lesson7-human-numbers (which we indeed want). Does that sound okay to you?

Sorry for the confusion. I will do as suggested.


⚠ ClamAV has degraded performance

In c61ee5c, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 194 ms

Resolved: ClamAV performance has improved in 8e2e57a.


Provisioning support security mode 2 SRP6a + AES-GCM.

Thanks @mikkeldamsgaard, now we could use origin host tool and Android APP without modifying.


Add some columns you expect to use before moving database stuff to prod

Migrations will be tough if we don't do it now

Nah, we don't have to do migrations, we'll just add the columns when we need to.


Use HTTPS where possible

This fixed the mixed content issues on https://oxyc.github.io/luaparse/.

Thanks!

Now that HTTPS works, why not update this link?

:+1:


configuring of project, add step to populate data

Documentation Feedback
to populate list of possible audits, I needed to do manual run for task

this may be useful to reflect in documentation, otherwise unable to create project with empty audit section field.

@CoolCold Hi! Thank you for opening an issue, I agree that this can be a serious impediment on a first install.
Would you consider updating the docs to include this extra (but mandatory) step? You can open a Pull Request directly from GitHub by following this link: https://github.com/theodo/falco/edit/master/docs/docs/getting-started/configuring-your-first-project.md

here is it https://github.com/theodo/falco/pull/116

Out of curiosity, which way did you install Falco—Heroku or manual installation? Because I just tested a new Heroku install and the list of audit parameters was already populated.

@phacks I did it with manual installation.

Merged with #129!


[Serve] add allocator in Storage as the upstream change

The changes in https://github.com/apache/tvm/pull/16750 modified the signature of the Storage, this pull request updates the caller code in mlc-llm to accommodate the new Storage class signature. Ran into build error w/o the change.
mlc-llm/cpp/serve/model.cc:67:96: error: no matching function for call to ‘tvm::runtime::memory::Storage::Storage(tvm::runtime::memory::Buffer)’
   67 |         memory::Storage(allocator->Alloc(device_host, {prefill_chunk_size_}, DataType::Int(32)));

cc: @MasterJH5574 @vinx13 @tqchen

Hey @yongwww thank you for the patch - I was just about to do that.
Just you will need to format the file, given it's over 100 characters.


Rename :NvimWebDeviconsHiTest to anything else like WebDeviconsHiTest

Distros often reserve the command prefix :Nvim for their own stuff, so it would be a good idea to leave it free.

I see, it looks like we might be the only ones doing this. From my setup:
NvimTreeClipboard
NvimTreeClose
NvimTreeCollapse
NvimTreeCollapseKeepBuffers
NvimTreeFindFile
NvimTreeFindFileToggle
NvimTreeFocus
NvimTreeHiTest
NvimTreeOpen
NvimTreeRefresh
NvimTreeResize
NvimTreeToggle
NvimWebDeviconsHiTest

What do you mean by distro? Something like lunar vim?

We cannot tiptoe around every possible set of configurations, sorry. Commands from this and nvim-tree repositories are prefixed by their respective names to avoid clashes. There isn't anything special about Nvim and if some disteos choose to use such generic name rather than their name (like, for example Lvim, but I am not sure, never used any of those) it's kind a on them.

That is not a good thing. We should change the border cases like this where it happens.

alex-courtis we distribute 100 plugins in our distro and you don't have a single one that do that. So if you see it in a plugin, report it like I did.
Plus, the naming convention for neovim plugins is <name-of-the-plugin>.nvim, so this doesn't happen.

That is not a good thing. We should change the border cases like this where it happens.

Unfortunately that's not something we can do - it will break users.
You could change nvim-tree commands via API: :help nvim-tree-api.commands
This will break nvim-tree users of your distribution as readme, help, wiki will not be correct.
local api = require("nvim-tree.api")

-- retrieve all nvim-tree commands
local commands = api.commands.get()
print(vim.inspect(commands))

local open = commands[1]

-- create command with a different name
vim.api.nvim_create_user_command("FooNvimTreeOpen", open.command, open.opts)

-- remove old command
vim.api.nvim_del_user_command(open.name)

What exactly is the problem here? What does the Nvim command prefix break?

It doesn't break anything. They maintain configuration called NormalNvim and supposedly have bunch of commands starting with Nvim (https://github.com/NormalNvim/NormalNvim?tab=readme-ov-file#commands). I guess having non-related commands in completion items is an issue. This really is an no-op. Sorry.

Myself and my colleagues really don't understand nvim distributions; why do they exist?
The issue is that new neovim users don't understand the basics like buffers and windows and tabs. It's difficult to know what's built in functionality vs provided by plugins. Most of the issues that lunarvim users raise here are not a plugin issue, but an issue with their understanding.
In our #vim slack channel: "I'm new to vim, what plugins should I use?" The answer was a resounding NONE.


use toBeCalledXxxx

Codecov Report
Base: 62.31% // Head: 62.31% // No change to project coverage :thumbsup:

Coverage data is based on head (4875052) compared to base (a4d92c7).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #226   +/-   ##
=======================================
  Coverage   62.31%   62.31%
=======================================
  Files          60       60
  Lines        3983     3983
  Branches      782      782
=======================================
  Hits         2482     2482
  Misses        802      802
  Partials      699      699

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add an indication that the MARC analysis page is loading

From the main provider page, when you select the "MARC analysis" tab, that page takes a while to load. But from a user perspective it isn't necessarily clear what is happening; a user could think the tab just isn't working.
We should add some sort of indication of the page loading situation.

I've noticed that this is often on the client/turbolinks side, and happens on other pages too. Interestingly, there is a default indicator (a small, thin line that crawls across the top of the screen), but it seems to be hidden by our current CSS. You can see it in the DOM while the page is loading (there's an invisible element whose width is rapidly being changed by javascript). Fixing this could be as simple as re-coloring/styling the line so it's visible to users (if we like that UX).

Ah yeah, I have noticed that progress updating in the web inspector but never connected it to the progress indicator at the top of the viewport. And I see that progress line at the top of the viewport in other Rails apps, such as Exhibits.
So yeah, that would be an easy fix, although maybe not an ideal one, I'd argue, since I think it's easy to overlook. But I'd be okay with it as an interim solution, until and if we decide the MARC analysis page at least (since it is likely to almost always takes a fairly long time to load, and in a context where it's easy to think the tab you just clicked isn't working correctly or something) deserves something more prominent.

@ggeisler any thoughts on a color and/or thickness (in px) for this line, as an interim solution? i can make a quick PR

Let's try something pretty noticeable. Maybe the Bootstrap warning color (same as POD icon badge bg)? Maybe 3px? Totally guessing, feel free to try whatever looks good to you.

cool, i'll try that. incidentally, just noticed that github has the same bar (maybe it's using turbolinks too) and they went with a blue color, pretty thin. visible (just) in this screenshot; nearly fully loaded:

Yeah, my suggestion for the warning yellow and a possibly thicker width line is the examples I've seen, like Github's, are very easy to not notice. Developers might notice them but I'm not sure they catch the attention of the average user. Especially with a color that is not a high contrast to the topbar (thus my suggestion for yellow to contrast with our dark topbar, rather than something like the blue Github used with their similar topbar color).


[Suggestion] Headphones

Basically, add headphones that you can equip to a neural interface / pocket computer (as a peripheral) that work like a speaker but only the owner of the computer can hear the audio
also the peripheral name should be named something else rather then "speaker" so in programs you can switch between speakers and headphones (for neural interface)
I would do a pull request, but i'm not (that) good with java yet
you could also put them into the manipulator for it work with computers (don't know the use, but would be cool)

could also just be a plethora feature instead of sc-goodies

This issue will probably get transferred to that repo, but since I don't want to forget, this could be a really interesting way to handle outputting sound out without the player hearing it. Something like how the entity sensor in tandem with the introspection module works, adding getMetaOwner, some kind of method could be made available that only outputs sound to the world, but "noise cancels" for the player when a speaker and headset is present.

I'd like this to allow stereo playback for the player listening


Travis Spends Most Time Building Vim

From recent build, the second one is the nox one that just installs a version of vim. Total is usually around 15 mins now. If we didn't build vm, would probably be like 3/4.
93.1   4 min 34 sec    3 minutes ago   1.8.7   linux
93.2    1 min           7 minutes ago   1.9.2   linux
93.3    5 min 27 sec    2 minutes ago   1.9.3   linux
93.4    4 min 52 sec    3 minutes ago   2.0.0   linux
Build time for all cases except nox are lengthy not because of our project but because the initial hg clone is really long and the subsequent build is quite long too.
All we need to do is prebuild a compatible version of vim (with dynamic python/ruby) I guess. I mean it isn't like we absolutely always need to test the immediate latest vim tag. I might investigate this in a bit on a separate branch.

Zip/Extract onto machine
Have some Ubuntu PPA with our own prebuild deb

I know. It would be nice if we could cut down the time, but more important I think is that we make sure vim-plug works with various versions of Vim, which is the point that the current set of Travis CI builds is missing. I frequently have to work with the ancient RHEL 5 servers with Vim 7.0 at work, and vim-plug seems to work fine there. I wish such old versions of Vim are also tested on Travis CI.

@junegunn Right, too bad travis doesn't seem to be looking at that so far. Only thing I see is OSX on horizon. Currently might have ruby support, but python non functional > https://github.com/travis-ci/travis-ci/issues/2320

@junegunn Putting this on hold while I look at other stuff like recent bug.
I tried to create a deb & extract it from travis and that worked. Seem to have a small problem with vim runtimedir when reinstalled. Small error to solve.
Alternatively, noticed that travis has arbitrary directory caching. http://docs.travis-ci.com/user/caching/#Fetching-and-storing-caches
If we made our vim builds sit in some dir under home like $HOME/cache, we could then maybe cache them between builds & conditionally build if cache was empty.

@starcraftman The page you linked says:

The features described here are currently only available for private repositories on travis-ci.com and our new container-based infrastructure.

So it doesn't seem like an option. Anyway, thanks for looking into this.

@junegunn Damn, read a bit too quick. Guess they gotta make money somehow. Also seem to have extra dependency features for privates.
Guess the debian thing I made probably only route.

@junegunn Update. I've created a rudimentary example on my branch vim_deb2. Here the travis simply downloads a deb and installs. The build script & debs get managed on a separate git repo using an encrypted oauth. I didn't want to push debs into our main repo. See here https://github.com/plugvim/cache.
See speedup on this travis build. About 1 minute for each.
Thoughts? I'm not a huge fan of using git for debs, I'm open to any other easy mechanism. I just used it because it was easy.

To be honest, I'm not even sure if I like this idea anymore. Funny since I brought it up. It adds complexity, and I don't think the current build time is a major impediment. I think this was more my own curiosity about what if I built a larger component based program on Travis. Shows a base method for test dependencies.

@starcraftman Hmm, yeah, I agree. It would be of course nice if it's faster, but the current build time is not really the problem and I don't like having to maintain yet another repository just for testing vim-plug. Maybe there are other options, let's leave this issue open, and try to find a better solution as a long term goal.

@junegunn Agreed.

You might be interested in what many Perl repos are doing this. They are pre-built versions of Perl set up so that any Perl-using project can test on many versions of Perl at once: https://github.com/travis-perl/helpers. Maybe you can make helpers so that any Vim project can do the same?

@zmughal I see, they kind of arrived at the same idea I did before me. So basically they just made an organization with scripts to keep these builds up to date with security fixes. It is out of scope of this project, but I might undertake it after the neovim patch. So you are suggesting I make something like Travis-Vim with prebuilt vim versions from latest 7.1-7.4, maybe even neovim snaps.

 See our .travis.yml for example. Their documentation is pretty good, see http://docs.travis-ci.com/ . You can arbitrarily run any bash/scripting language to test/manipulate the env.

Cache is now available for public repos.

@rubik Yup, known this for a bit. I been a bit lazy on that. We don't issue many builds though as development has stabilized quite a bit.
I should make a PR for it, have leveraged it in my other projects.

I was building Vim for my plugin's tests, and it took roughly 1m30s for a single job (65 of those seconds was spent building Vim).  It was annoying slow, so I created a Docker base image for testing Vim: https://github.com/tweekmonster/vim-testbed
It could be used to drastically cut down the time it takes to run CI.  The idea is that you build a container with the versions of Vim you need to test once, then use that in Travis CI.  I did this with my plugin and it cut the job time to about 30s: https://travis-ci.org/tweekmonster/braceless.vim/builds/110045243
This is the pre-built container I used for my tests, which has an extremely simple Dockerfile: https://github.com/tweekmonster/ubuntu-vims
It's not built with python or ruby, but a new image could be created easily with them prebuilt.  It looks like Travis-CI caches the images as well which means that the build times will be shorter after the image is initially pulled.
When I find some time today, I wouldn't mind submitting a PR.  But, since this solution requires a hosted container, it might be better for the prebuilt container to be hosted on @junegunn's own Docker Hub repo.

@tweekmonster I think we are generally happy enough with how short the build is now (about 2 mins). When this was first made, we used to always build and it was like 5+ per job.
At this time, we only build for one of the jobs (rest use the package version). We cache the build using travis cache.

@starcraftman I guess I missed the part above about the cache...and the age of this issue.  I contacted @junegunn through email about the Docker images and he pointed me here.  The goal with vim-testbed is not just to improve the Travis-CI speed, but also allow for easy local testing with different builds of Vim.
FWIW here's the modifications required: https://github.com/junegunn/vim-plug/compare/master...tweekmonster:docker-tests
The script can still run like it used to locally without Docker, or with docker run -it --rm -v $PWD:/testplugin tweekmonster/vim-plug vim-py
Here's the Travis-CI build results from my branch: https://travis-ci.org/tweekmonster/vim-plug/builds/110246705

@tweekmonster Although it's hard to say that the current test configuration impedes our development process, I'm in favor of the suggested approach as it seems easier to add more build targets and it allows local testing against different configurations. And it's faster, of course. Thanks for sharing the idea.
One thing I noticed while looking at the change you made is that it's not testing against different versions of Ruby. Is it possible?

@junegunn I was looking into having the image build different versions of Python and Ruby, but RVM doesn't work in Alpine Linux.  I tried ruby-build as well, but a lot of the versions I tested failed to build.
I went with Alpine because it's very small and I wasn't sure about Travis CI caching docker images.  But, since it does cache, I will probably use an Ubuntu base image which is larger, but better supported.

Turns out I was incorrect in saying that Travis CI caches the docker images.  I must've misread the output saying that it was fetching a new version :sweat:  It's still not bad in terms of speed.
I made a version that's based on Debian that's able to build arbitrary versions of Vim with arbitrary versions of Python with PyEnv and Ruby with RVM.  The resulting container size is much larger than with Alpine, but the impact is ~10 extra seconds per build job.  The bulk of the time was spent building the image locally, which was about 17 minutes for 5 Vim versions.
Travis CI: https://travis-ci.org/tweekmonster/vim-plug/builds/110536649
Updated Dockerfile so you can see the versions: https://github.com/tweekmonster/vim-plug/blob/b316dcbc41ea4a1126e243fb77340c45f815e909/Dockerfile

@junegunn

it seems easier to add more build targets

Any target in particular we are missing that you want added? Main whole I see is Windows which we'd need AppVeyor for.
@tweekmonster Very interesting, big thanks for the continuing work. Too bad didn't have these speedy builds earlier when we were doing much more dev.

@starcraftman

Any target in particular we are missing that you want added?

We're currently testing against the latest source (except vim-nox case), but wouldn't it be better if we also test using explicit version tags, like 7.0, 7.3, and 7.4 when Vim turns 7.5 in the future, the number of combinations will increase but that's what I'm thinking. Having said that, I think our coverage is already pretty good and fiddling with archaic 7.0 is probably a waste of time but the point is that it'll be easier to extend in the future.

@starcraftman No problem at all.  vim-plug would be a great use case, but I'm working on this because unit testing Vim plugins is such a pain in the ass.  So if you have any input on vim-testbed regardless of its use in vim-plug, it would be much appreciated.
In other news, since you mentioned it I've been successful in getting the Vim win32 binary to run via wine in the container.  I've never used wine to run CUI programs, so I'm not getting the exact results I wanted.  Vader seems to run, but fails soon after since Vim seems to be confused about the $SHELL.  Wine clears the output before exiting, so nothing gets printed with Vader!.

@tweekmonster I'm not sure testing against wine is the best route to go. Several issues, most importantly wine != Windows so even if vim-plug or someone else's plugin worked in wine it wouldn't guarantee it worked in Windows. Moreover, wine doesn't always work itself, hard to base tests on an unstable platform.  I'd say two choices present themselves.

Make use of AppVeyor, something we should probably look into on our own.
Perhaps use one of MIcrosoft's own VMs . I would be happy just being able to specify testing against Windows 7.

True enough about wine.  It's been a little too obtuse to even get running reliably just for vim-only features.
A Win7 VM is a great idea for local testing since it could run programs in compatibility mode if you really wanted to go that old.  The only problem I see with it is that it's not very portable at 3.5GB for the Win7+IE9 one.  A script would most likely be needed to setup the VM for testing to have environment consistency across workstations.

This is still very much the case for the vim-nightly build, just not a concern for any of the others, correct?


Lazyload fails to load items on previous page

I have a setup of 21 items and 6 items per page as example. When switching from the first page to the last (by pressing previous page) it will only render 3 items.
This is only an issue with lazyLoad={true}
Sandbox:
https://codesandbox.io/s/react-slick-playground-forked-f2t97?fontsize=14&hidenavigation=1&theme=dark

Just press the left arrow once and you will only see 3 kittens, instead of the expected 6

I tried fixing this myself but after 1 Day had zero progress, I can't justify putting more time into this. Does anyone maybe have any pointers where this issue could come from?


F# logo use

@reedcopsey This is a project for strongly typed access to SQL server. I am considering a logo like the below (not necessarily final colors/proportions). Is that an acceptable use of the F# logo elements? (Related: https://github.com/cmeeren/Felicity/issues/1)

@cmeeren I think this is fine. Thank you for checking.

Thanks a lot!


feat: support use_frameworks

This is a follow up to https://github.com/dominicstop/react-native-ios-utilities/pull/11, but for the react-native-ios-context-menu library. It should enable use_frameworks!

Oh whoops, something got messed up in a rebase. I'll reopen this tonight.


Issues installing - failures and segmentation fault

Hi, I've been trying to install gmt-python for the past day and a half with no avail. I am on macOS 10.13.4, Python 3.6.5 (installed with Anaconda 3). I've been following all of the installation instruction, and everything seems fine except when I get to the very end, with the gmt.test().
I am in the conda environment (using source activate gmt-python), and trying this in the Python interpreter. This is what happens:

(gmt-python) Chandras-MacBook-Pro:~ chandra$ python
Python 3.6.5 | packaged by conda-forge | (default, Apr  6 2018, 13:44:09)
[GCC 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

import gmt
gmt.test()

returns

============================= test session starts ==============================
platform darwin -- Python 3.6.5, pytest-3.5.0, py-1.5.3, pluggy-0.6.0 -- /anaconda3/envs/gmt-python/bin/python
cachedir: .pytest_cache
Matplotlib: 2.2.2
Freetype: 2.8.1
rootdir: /Users/chandra, inifile:
plugins: mpl-0.9
collected 126 items
gmt/base_plotting.py::gmt.base_plotting.BasePlotting._preprocess <- ../../anaconda3/envs/gmt-python/lib/python3.6/site-packages/gmt/base_plotting.py PASSED [  0%]
gmt/figure.py::gmt.figure.Figure <- ../../anaconda3/envs/gmt-python/lib/python3.6/site-packages/gmt/figure.py FAILED [  1%]
gmt/clib/core.py::gmt.clib.core.LibGMT <- ../../anaconda3/envs/gmt-python/lib/python3.6/site-packages/gmt/clib/core.py PASSED [  2%]
gmt/clib/core.py::gmt.clib.core.LibGMT._check_dtype_and_dim <- ../../anaconda3/envs/gmt-python/lib/python3.6/site-packages/gmt/clib/core.py PASSED [  3%]
gmt/clib/core.py::gmt.clib.core.LibGMT.extract_region <- ../../anaconda3/envs/gmt-python/lib/python3.6/site-packages/gmt/clib/core.py gmt-python-session [ERROR]: Long input record (236 bytes) was truncated to first 126 bytes!
FAILED [  3%]
gmt/clib/core.py::gmt.clib.core.LibGMT.grid_to_vfile <- ../../anaconda3/envs/gmt-python/lib/python3.6/site-packages/gmt/clib/core.py FAILED [  4%]
gmt/clib/core.py::gmt.clib.core.LibGMT.log_to_file <- ../../anaconda3/envs/gmt-python/lib/python3.6/site-packages/gmt/clib/core.py Segmentation fault: 11

I feel like this might be because of a bash profile issue. I am not sure how to set up a .bashrc profile properly on the Mac (sorry!), but my .bash_profile looks like this (note the 'added by...' is commented out):

added by Anaconda3 5.1.0 installer
export PATH="/anaconda3/bin:$PATH"
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/anaconda3/envs/gmt-python/lib

Any help would be much appreciated! 😄
ps. let me know if any clarifications are needed, sorry first time writing an issue in!
pps. attached a screenshot of terminal, just to be super clear!

@chandrex thank you reporting this and sorry for all the trouble! I really appreciate the amount of effort you put in to the issue. That really helps! Welcome to the world of open-source! I hope you'll like it and consider becoming involved :grinning:
OK, this is a bad crash. It normally shouldn't happen but it's really tricky dealing with C code from Python. One possibility is that Python is finding the wrong version of GMT. Do you have GMT installed from another source (homebrew, fink, etc)?
Could you try removing the LD_LIBRARY_PATH line? That's not usually necessary unless you can't get it to work otherwise. Sorry about this, it should be clearer in the docs and I opened #165 to remind me to deal with this.
If that doesn't work, then can you please post the output of conda list? That way I can try to see if everything is being installed in the correct version.
Again, thanks for detailed issue!

Hiya,
Yes I have GMT installed already (5.4.2), which I installed with homebrew. It won't work with or without the LD_LIBRARY_PATH (I tried!), but I will remove it anyhow.
Here is my conda list

Thanks for your help 😁

OK, here are a few things you can try:

I noticed that your pandas and xarray were installed by pip. Which indicates that they were pulled in when you installed gmt-python. Also, your numpy is a release candidate. We noticed these problems before so we updated the install instructions to match. Could you dele the current environment (conda env remove -n gmt-python) and follow these steps?
If that doesn't work, then try setting LD_LIBRARY_PATH using export LD_LIBRARY_PATH=$HOME/anaconda3/envs/gmt-python/lib:$LD_LIBRARY_PATH . This gives anaconda a higher priority.

I'm working on a better way that we can diagnose these problems (#167).
Again, thanks for reporting this!

@chandrex just to let you know that your issue contributed several changes to the project: #168 #173 #175 #176 and #177
#177 introduces a new way to set the path to the GMT shared library. Once, that's incorporated (it will say "Merged" on the link) please try deleting your conda environment and following the new instructions that will appear in http://www.gmtpython.xyz/install.html
Again, thank you for helping us make things more robust!

@chandrex please let me know if the new changes work for you. If not we can at least better diagnose the problem.

Hi.
I just followed your wiki download/install instructions on mac os 10.10.5 and I get the exact same error:

gmt.test()
...
gmt/clib/core.py::gmt.clib.core.LibGMT.get_libgmt_func PASSED                                                       [  4%]
gmt/clib/core.py::gmt.clib.core.LibGMT.grid_to_vfile PASSED                                                         [  5%]
gmt/clib/core.py::gmt.clib.core.LibGMT.log_to_file Segmentation fault: 11

My dependencies (e.g., xarray, pandas) were all installed with conda.
Everything looks good (no complaints) except for the seg fault.
Please let me know if anyone makes any progress on solving this.
Cheers!
-Mike

Hi @mikehagerty and @chandrex this is a very strange failure. I'll try to get my hands on a Mac to investigate.
@mikehagerty out of curiosity, do you also have GMT5 installed?

OK, I managed to replicate the issue using Travis CI on #180. It's not a problem with your installation or with the pre-installed GMT5. I'll investigate further to try to get to the bottom of this.
Thanks for bringing this to my attention! It's hard to track these issues when I'm not using a Mac.

Hi there,
Any luck on the mac os test fails ?
I just did a clean install of gmt-python and tried the test again:
(gmt-python) mth@Mikes-MBP [~/mth]> python
Python 3.6.5 |Anaconda, Inc.| (default, Mar 29 2018, 13:14:23)
[GCC 4.2.1 Compatible Clang 4.0.1 (tags/RELEASE_401/final)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

import gmt
gmt.test()
=============================================== Currently loaded libgmt
================================================
binary dir: /Users/mth/mth/miniconda3/envs/gmt-python/bin
cores: 4
grid layout: rows
image layout:
library path: /Users/mth/mth/miniconda3/envs/gmt-python/lib/libgmt.dylib
padding: 2
plugin dir: /Users/mth/mth/miniconda3/envs/gmt-python/lib/gmt/plugins
share dir: /Users/mth/mth/miniconda3/envs/gmt-python/share/gmt
version: 6.0.0
usage:  [options] [file_or_dir] [file_or_dir] [...]
: error: unrecognized arguments: --mpl
inifile: None
rootdir: /Users/mth/mth

It seems the usage has changed (?)
Cheers!
-Mike
(gmt-python) mth@Mikes-MBP [~/mth]> conda list gmt
packages in environment at /Users/mth/mth/miniconda3/envs/gmt-python:

Name                    Version                   Build  Channel
dcw-gmt                   1.1.3                         0    conda-forge
gmt                       6.0.0a14        blas_openblas_201
[blas_openblas]  conda-forge/label/dev
gmt-python                0+unknown
gshhg-gmt                 2.3.7                         0    conda-forge
On Thu, May 10, 2018 at 10:43 PM, Leonardo Uieda<EMAIL_ADDRESS>wrote:

OK, I managed to replicate the issue using Travis CI on #180
https://github.com/GenericMappingTools/gmt-python/pull/180. It's not a
problem with your installation or with the pre-installed GMT5. I'll
investigate further to try to get to the bottom of this.
Thanks for bringing this to my attention! It's hard to track these issues
when I'm not using a Mac.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GenericMappingTools/gmt-python/issues/164#issuecomment-388243192,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACDAwkjw0uvHtdeTG851Wq472kl8HlPfks5txPq7gaJpZM4TdsgC
.

@mikehagerty sorry, haven't had much time to look into to yet.
It seems like you don't have pytest-mpl installed. Can you check, please? A lot of the tests compare generated plots using the matplotlib pytest plugin (hurray for duck typing!).

Hi Leonardo,
You were right that I didn't have pytest-mpl installed, however installing
it doesn't fix the seg-fault (see below).
(gmt-python) mth@Mikes-MBP [~/mth/python_pkgs/gmt-python]> python
Python 3.6.5 |Anaconda, Inc.| (default, Mar 29 2018, 13:14:23)
[GCC 4.2.1 Compatible Clang 4.0.1 (tags/RELEASE_401/final)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

import gmt
gmt.test()
=============================================== Currently loaded libgmt
================================================
binary dir: /Users/mth/mth/miniconda3/envs/gmt-python/bin
cores: 4
grid layout: rows
image layout:
library path: /Users/mth/mth/miniconda3/envs/gmt-python/lib/libgmt.dylib
padding: 2
plugin dir: /Users/mth/mth/miniconda3/envs/gmt-python/lib/gmt/plugins
share dir: /Users/mth/mth/miniconda3/envs/gmt-python/share/gmt
version: 6.0.0
================================================= test session starts
==================================================
platform darwin -- Python 3.6.5, pytest-3.5.1, py-1.5.3, pluggy-0.6.0 --
/Users/mth/mth/miniconda3/envs/gmt-python/bin/python
cachedir: .pytest_cache
Matplotlib: 2.2.2
Freetype: 2.8.0
rootdir: /Users/mth/mth/python_pkgs/gmt-python, inifile:
plugins: mpl-0.9
collected 133 items

gmt/base_plotting.py::gmt.base_plotting.BasePlotting._preprocess PASSED
[  0%]
gmt/figure.py::gmt.figure.Figure gmt-python-session [ERROR]: Long input
record (246 bytes) was truncated to first 126 bytes!
PASSED
[  1%]
gmt/clib/core.py::gmt.clib.core.LibGMT PASSED
[  2%]
gmt/clib/core.py::gmt.clib.core.LibGMT._check_dtype_and_dim PASSED
[  3%]
gmt/clib/core.py::gmt.clib.core.LibGMT.extract_region gmt-python-session
[ERROR]: Long input record (236 bytes) was truncated to first 126 bytes!
gmt-python-session [ERROR]: Long input record (247 bytes) was truncated to
first 126 bytes!
gmt-python-session [ERROR]: Long input record (239 bytes) was truncated to
first 126 bytes!
PASSED                                                     [  3%]
gmt/clib/core.py::gmt.clib.core.LibGMT.get_libgmt_func PASSED
[  4%]
gmt/clib/core.py::gmt.clib.core.LibGMT.grid_to_vfile FAILED
[  5%]
gmt/clib/core.py::gmt.clib.core.LibGMT.log_to_file Segmentation fault: 11
(gmt-python) mth@Mikes-MBP [~/mth/python_pkgs/gmt-python]>
Update: Here's a quick test:
import gmt
with gmt.clib.LibGMT() as lib:
mode = lib.get_constant('GMT_MODULE_CMD')
with lib.log_to_file() as logfile:
call_module = lib.get_libgmt_func('GMT_Call_Module')
print("MTH: mode=", mode)
print("MTH: session=", lib.current_session)
print("MTH: type(call_module)=", type(call_module))
status = call_module(lib.current_session, 'info'.encode(),
mode, 'bogus-file.bla'.encode())
print("MTH: status=", status)
It seems to be dying when trying to follow the pointer to call_module().
So maybe it's a ctypes issue ?
MTH: mode= 0
MTH: session=<PHONE_NUMBER>25120
MTH: type(call_module)= <class 'ctypes.CDLL.init.._FuncPtr'>
Segmentation fault: 11
Cheers!
-Mike
On Wed, May 30, 2018 at 7:31 PM, Leonardo Uieda<EMAIL_ADDRESS>wrote:

@mikehagerty https://github.com/mikehagerty sorry, haven't had much
time to look into to yet.
It seems like you don't have pytest-mpl installed. Can you check, please?
A lot of the tests compare generated plots using the matplotlib pytest
plugin (hurray for duck typing!).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GenericMappingTools/gmt-python/issues/164#issuecomment-393352225,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACDAwqoKhLMo0NC00mHPIeZM92j66ivfks5t3yvYgaJpZM4TdsgC
.

@mikehagerty thanks for the info!
I suspect that it's the log file actually but it's a bit tough to debug when TravisCI is not cooperating. I haven't found a good fix for that yet so I might just disable it for now. This is used to get the error messages printed by GMT. It's helpful but not vital for now.

Good news everyone @chandrex @mikehagerty! :tada: :cake: :balloon:
I finally managed to fix this issue in #188! It was a long struggle and I still have no idea why the fault was happening. But I replaced the code that was causing the problem with something better and the fault went away. Things should be working smoothly on Mac now.
Could you please give it a try and report back? Thank you for all the information you all provided and sorry for long delay. :rocket:


The skip option does not work properly

I tired the following combinations to skip the vendor folder but none of them was successful:
gas -skip vendor ./...
gas -skip vendor/* ./...
gas -skip *vendor* ./...
gas -skip vendor/*.go ./...
The vendor folder was always included into the scan.

The changes here will address this. Effectively GAS only scans complete packages, not individual files. By default it excludes the vendor directory and the files returned by a built package This will automatically exclude test files.


In the project built by @vue/cli 5.0.8, the problem of modifying filename such as images and fonts.

Discussed in https://github.com/vuejs/vue-cli/discussions/7260

Originally posted by<PHONE_NUMBER> August  4, 2022
In the project built with vue-cli 5.x version, the corresponding webpack 5.x version is used. For the static resources produced by the build, such as: js, css, image, fonts, etc., we do not need to do too much configuration. , cli has already configured it for us. If we want to modify the default configuration, cli is also supported.
使用vue-cli 5.x版本搭建的项目中，对应使用的是webpack 5.x版本，对于构建产出的静态资源，例如：js、css、image、fonts等等不需要我们做过多的配置，cli已经帮我们配置好了。如果我们想修改默认的配置，cli也是支持的。
For example, in my team, we are not used to the default naming method, like this: about.04f11358.js, we are more accustomed to putting the hash value at the end, like this: about.js?t=04f11358. The code can look like this:
比如在我的团队中，不太习惯默认的命名方式，像这样：about.04f11358.js，我们更习惯于把hash值放到最后，像这样：
about.js?t=04f11358。代码可以像下面这样：
...
module.exports = defineConfig({
chainWebpack: (config) => {
...
config.output
.filename("js/[name].js?t=[hash:7]")
.chunkFilename("js/[name].js?t=[hash:7]");
...
}
})
However, in webpack5, for the processing of resources such as images and fonts, url-loader, file-loader, etc. are no longer used, but built-in assets are used. How should I modify their filenames?
但是在webpack5中对于图片、字体等资源的处理，不再使用url-loader、file-loader等等，而是使用内置的asset，我应该如何修改它们的filename呢？

output
.assetModuleFilename('your file name')