ErrorUsing Cli dependency check  No documents exist.

Hi!
I am getting this error after execute comand line tool:
dic 04, 2015 12:42:49 PM org.owasp.dependencycheck.Engine doUpdates
INFORMACIÓN: Checking for updates
dic 04, 2015 12:42:50 PM org.owasp.dependencycheck.data.update.NvdCveUpdater update
ADVERTENCIA: Unable to download the NVD CVE data; the results may not include the most recent CPE/CVEs from the NVD.
dic 04, 2015 12:42:51 PM org.owasp.dependencycheck.Engine doUpdates
INFORMACIÓN: Check for updates complete
dic 04, 2015 12:42:52 PM org.owasp.dependencycheck.Engine analyzeDependencies
GRAVE: No documents exist
And also getting these messages en .log file:
.
.
.
<errors start here!!>:
2015-12-04 13:09:24,953 org.owasp.dependencycheck.Engine:325
ERROR - No documents exist
Unable to continue dependency-check analysis.
2015-12-04 13:09:24,956 org.owasp.dependencycheck.Engine:326
DEBUG -
org.owasp.dependencycheck.exception.NoDataException: No documents exist
at org.owasp.dependencycheck.Engine.ensureDataExists(Engine.java:497) ~[dependency-check-core-1.3.2.jar:1.3.2]
at org.owasp.dependencycheck.Engine.analyzeDependencies(Engine.java:323) ~[dependency-check-core-1.3.2.jar:1.3.2]
at org.owasp.dependencycheck.App.runScan(App.java:201) [dependency-check-cli-1.3.2.jar:1.3.2]
at org.owasp.dependencycheck.App.run(App.java:123) [dependency-check-cli-1.3.2.jar:1.3.2]
at org.owasp.dependencycheck.App.main(App.java:64) [dependency-check-cli-1.3.2.jar:1.3.2]
2015-12-04 13:09:25,020 org.owasp.dependencycheck.data.nvdcve.CveDB:83
DEBUG - Database dialect: H2
2015-12-04 13:09:25,148 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Initializing Velocity, Calling init()...
2015-12-04 13:09:25,148 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Starting Apache Velocity v1.7 (compiled: 2010-11-19 12:14:37)
2015-12-04 13:09:25,148 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Default Properties File: org/apache/velocity/runtime/defaults/velocity.properties
2015-12-04 13:09:25,149 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Trying to use logger class org.owasp.dependencycheck.reporting.VelocityLoggerRedirect
2015-12-04 13:09:25,149 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Using logger class org.owasp.dependencycheck.reporting.VelocityLoggerRedirect
2015-12-04 13:09:25,151 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - ResourceLoader instantiated: org.apache.velocity.runtime.resource.loader.FileResourceLoader
2015-12-04 13:09:25,152 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Do unicode file recognition:  false
2015-12-04 13:09:25,152 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - FileResourceLoader : adding path '.'
2015-12-04 13:09:25,157 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - ResourceCache: initialized (class org.apache.velocity.runtime.resource.ResourceCacheImpl) with class java.util.Collections$SynchronizedMap cache map.
2015-12-04 13:09:25,158 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Loaded System Directive: org.apache.velocity.runtime.directive.Stop
2015-12-04 13:09:25,159 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Loaded System Directive: org.apache.velocity.runtime.directive.Define
2015-12-04 13:09:25,159 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Loaded System Directive: org.apache.velocity.runtime.directive.Break
2015-12-04 13:09:25,160 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Loaded System Directive: org.apache.velocity.runtime.directive.Evaluate
2015-12-04 13:09:25,160 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Loaded System Directive: org.apache.velocity.runtime.directive.Literal
2015-12-04 13:09:25,161 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Loaded System Directive: org.apache.velocity.runtime.directive.Macro
2015-12-04 13:09:25,162 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Loaded System Directive: org.apache.velocity.runtime.directive.Parse
2015-12-04 13:09:25,162 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Loaded System Directive: org.apache.velocity.runtime.directive.Include
2015-12-04 13:09:25,163 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Loaded System Directive: org.apache.velocity.runtime.directive.Foreach
2015-12-04 13:09:25,179 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Created '20' parsers.
2015-12-04 13:09:25,182 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Velocimacro : "velocimacro.library" is not set.  Trying default library: VM_global_library.vm
2015-12-04 13:09:25,182 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Velocimacro : Default library not found.
2015-12-04 13:09:25,182 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Velocimacro : allowInline = true : VMs can be defined inline in templates
2015-12-04 13:09:25,182 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Velocimacro : allowInlineToOverride = false : VMs defined inline may NOT replace previous VM definitions
2015-12-04 13:09:25,182 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Velocimacro : allowInlineLocal = false : VMs defined inline will be global in scope if allowed.
2015-12-04 13:09:25,182 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Velocimacro : autoload off : VM system will not automatically reload global library macros
2015-12-04 13:09:25,213 org.owasp.dependencycheck.data.nvdcve.CveDB:163
DEBUG - Entering finalize
2015-12-04 13:09:25,213 org.owasp.dependencycheck.data.nvdcve.CveDB:163
DEBUG - Entering finalize
2015-12-04 13:09:25,300 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Null reference [template 'templates/HtmlReport.vsl', line 635, column 46] : $cpeSort cannot be resolved.
2015-12-04 13:09:25,300 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Null reference [template 'templates/HtmlReport.vsl', line 635, column 46] : $cpeSort cannot be resolved.
2015-12-04 13:09:25,301 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Null reference [template 'templates/HtmlReport.vsl', line 635, column 46] : $cpeSort cannot be resolved.
2015-12-04 13:09:25,302 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
I am behind a proxy and I added the parameters, could you help me? Or where can I watch for checking examples. Thank you in advance.
Regards,
Gonzalo

First, there is a bug in 1.3.2 that was discovered shortly after its release (one of those bugs where it works on my system) - I will be releasing 1.3.3 shortly.
Second, are you behind a proxy? You may need to configure the proxy for dependency-check to be able to reach out to the Internet. See http://jeremylong.github.io/DependencyCheck/data/index.html.
Best Regards,
Jeremy

Thank you for answering. I am behind a proxy indeed, actually the exit I put was with proxy parameters. I used something like this:
sudo ./dependency-check.sh --project "project" --scan ".../lib" -f HTML --proxyserver proxy --proxyport 8080 --proxypass password --proxyuser user --log dc.log
Am I using correctly? This was the exit:
Exception in thread "main" java.util.NoSuchElementException
at java.util.StringTokenizer.nextToken(StringTokenizer.java:349)
at sun.net.www.protocol.http.HttpURLConnection.doTunneling(HttpURLConnection.java:2017)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:183)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:153)
at org.owasp.dependencycheck.utils.Downloader.getLastModified(Downloader.java:235)
at org.owasp.dependencycheck.data.update.nvd.UpdateableNvdCve.add(UpdateableNvdCve.java:94)
at org.owasp.dependencycheck.data.update.NvdCveUpdater.retrieveCurrentTimestampsFromWeb(NvdCveUpdater.java:299)
at org.owasp.dependencycheck.data.update.NvdCveUpdater.getUpdatesNeeded(NvdCveUpdater.java:231)
at org.owasp.dependencycheck.data.update.NvdCveUpdater.update(NvdCveUpdater.java:70)
at org.owasp.dependencycheck.Engine.doUpdates(Engine.java:433)
at org.owasp.dependencycheck.Engine.analyzeDependencies(Engine.java:318)
at org.owasp.dependencycheck.App.runScan(App.java:201)
at org.owasp.dependencycheck.App.run(App.java:123)
at org.owasp.dependencycheck.App.main(App.java:64)
Is it because of the bug?
Thanks Jeremy.
Best Regards

I just realized you ran this with sudo - my guess is there is a permission problem with accessing the database directory. By default the data directory for the CLI would be a sibling of the bin and repo directory; that directory must exist and allow read/write. You can change the default data directory using the --data property. Let me know if that helps?
--Jeremy

Sorry Jeremy, you mean change the directory data (with --data ) instead of....? Which is the default data directory for the CLI?
The exit now is:
INFO  - Checking for updates
2015-12-11 13:40:10,630 org.owasp.dependencycheck.data.nvdcve.CveDB:83
DEBUG - Database dialect: H2
2015-12-11 13:40:10,632 org.owasp.dependencycheck.data.update.NvdCveUpdater:113
INFO  - Skipping NVD check since last check was within 4 hours.
2015-12-11 13:40:10,632 org.owasp.dependencycheck.data.update.NvdCveUpdater:114
DEBUG - Last NVD was at<PHONE_NUMBER>914, and now<PHONE_NUMBER>632 is within 14400000 ms.
2015-12-11 13:40:10,807 org.owasp.dependencycheck.data.nvdcve.CveDB:83
DEBUG - Database dialect: H2
2015-12-11 13:40:10,807 org.owasp.dependencycheck.data.update.EngineVersionCheck:87
DEBUG - Begin Engine Version Check
2015-12-11 13:40:10,808 org.owasp.dependencycheck.data.update.EngineVersionCheck:93
DEBUG - Last checked:<PHONE_NUMBER>265
2015-12-11 13:40:10,808 org.owasp.dependencycheck.data.update.EngineVersionCheck:94
DEBUG - Now:<PHONE_NUMBER>807
2015-12-11 13:40:10,808 org.owasp.dependencycheck.data.update.EngineVersionCheck:95
DEBUG - Current version: 1.3.2
2015-12-11 13:40:10,808 org.owasp.dependencycheck.data.update.EngineVersionCheck:150
DEBUG - Upgrade not needed
2015-12-11 13:40:10,810 org.owasp.dependencycheck.data.nvdcve.CveDB:163
DEBUG - Entering finalize
2015-12-11 13:40:10,913 org.owasp.dependencycheck.Engine:440
INFO  - Check for updates complete (354 ms)
2015-12-11 13:40:10,976 org.owasp.dependencycheck.data.nvdcve.CveDB:83
DEBUG - Database dialect: H2
2015-12-11 13:40:11,082 org.owasp.dependencycheck.Engine:325
ERROR - No documents exist
Unable to continue dependency-check analysis.
2015-12-11 13:40:11,084 org.owasp.dependencycheck.Engine:326
DEBUG -
org.owasp.dependencycheck.exception.NoDataException: No documents exist
at org.owasp.dependencycheck.Engine.ensureDataExists(Engine.java:497) ~[dependency-check-core-1.3.2.jar:1.3.2]
at org.owasp.dependencycheck.Engine.analyzeDependencies(Engine.java:323) ~[dependency-check-core-1.3.2.jar:1.3.2]
at org.owasp.dependencycheck.App.runScan(App.java:201) [dependency-check-cli-1.3.2.jar:1.3.2]
at org.owasp.dependencycheck.App.run(App.java:123) [dependency-check-cli-1.3.2.jar:1.3.2]
at org.owasp.dependencycheck.App.main(App.java:64) [dependency-check-cli-1.3.2.jar:1.3.2]
2015-12-11 13:40:11,144 org.owasp.dependencycheck.data.nvdcve.CveDB:83
DEBUG - Database dialect: H2
2015-12-11 13:40:11,276 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Initializing Velocity, Calling init()...
2015-12-11 13:40:11,277 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Starting Apache Velocity v1.7 (compiled: 2010-11-19 12:14:37)
2015-12-11 13:40:11,277 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Default Properties File: org/apache/velocity/runtime/defaults/velocity.properties
2015-12-11 13:40:11,277 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Trying to use logger class org.owasp.dependencycheck.reporting.VelocityLoggerRedirect
2015-12-11 13:40:11,277 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Using logger class org.owasp.dependencycheck.reporting.VelocityLoggerRedirect
2015-12-11 13:40:11,280 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - ResourceLoader instantiated: org.apache.velocity.runtime.resource.loader.FileResourceLoader
2015-12-11 13:40:11,281 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Do unicode file recognition:  false
2015-12-11 13:40:11,282 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - FileResourceLoader : adding path '.'
2015-12-11 13:40:11,290 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - ResourceCache: initialized (class org.apache.velocity.runtime.resource.ResourceCacheImpl) with class java.util.Collections$SynchronizedMap cache map.
2015-12-11 13:40:11,291 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Loaded System Directive: org.apache.velocity.runtime.directive.Stop
2015-12-11 13:40:11,292 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Loaded System Directive: org.apache.velocity.runtime.directive.Define
2015-12-11 13:40:11,292 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Loaded System Directive: org.apache.velocity.runtime.directive.Break
2015-12-11 13:40:11,293 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Loaded System Directive: org.apache.velocity.runtime.directive.Evaluate
2015-12-11 13:40:11,293 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Loaded System Directive: org.apache.velocity.runtime.directive.Literal
2015-12-11 13:40:11,294 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Loaded System Directive: org.apache.velocity.runtime.directive.Macro
2015-12-11 13:40:11,295 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Loaded System Directive: org.apache.velocity.runtime.directive.Parse
2015-12-11 13:40:11,296 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Loaded System Directive: org.apache.velocity.runtime.directive.Include
2015-12-11 13:40:11,297 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Loaded System Directive: org.apache.velocity.runtime.directive.Foreach
2015-12-11 13:40:11,317 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Created '20' parsers.
2015-12-11 13:40:11,320 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Velocimacro : "velocimacro.library" is not set.  Trying default library: VM_global_library.vm
2015-12-11 13:40:11,321 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Velocimacro : Default library not found.
2015-12-11 13:40:11,321 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Velocimacro : allowInline = true : VMs can be defined inline in templates
2015-12-11 13:40:11,321 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Velocimacro : allowInlineToOverride = false : VMs defined inline may NOT replace previous VM definitions
2015-12-11 13:40:11,321 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Velocimacro : allowInlineLocal = false : VMs defined inline will be global in scope if allowed.
2015-12-11 13:40:11,321 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Velocimacro : autoload off : VM system will not automatically reload global library macros
2015-12-11 13:40:11,356 org.owasp.dependencycheck.data.nvdcve.CveDB:163
DEBUG - Entering finalize
2015-12-11 13:40:11,356 org.owasp.dependencycheck.data.nvdcve.CveDB:163
DEBUG - Entering finalize
2015-12-11 13:40:11,443 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
DEBUG - Null reference [template 'templates/HtmlReport.vsl', line 635, column 46] : $cpeSort cannot be resolved.
Thank you so much.

When you unzip the CLI you should have the following folders:
dependency-check
--bin
--repo
When you run the tool the first time, it creates a data folder:
dependency-check
--bin
--data
--repo
First thing to try is to delete the data folder and re-run dependency-check with the correct proxy settings. If that fails, double check that the data folder is created and is writtable. If you need to you can specify a different data directory to point to a folder that you setup with the correct permissions:
dependency-check.sh --data /some/data/directory ...

Hi!
It doesnt work, I think is not about permissions problem but maybe I am wrong. Perhaps the problem is because of the proxy, the main error appears this way:
org.owasp.dependencycheck.exception.NoDataException: No documents exist
at org.owasp.dependencycheck.Engine.ensureDataExists(Engine.java:497) ~[dependency-check-core-1.3.2.jar:1.3.2]
at org.owasp.dependencycheck.Engine.analyzeDependencies(Engine.java:323) ~[dependency-check-core-1.3.2.jar:1.3.2]
at org.owasp.dependencycheck.App.runScan(App.java:201) [dependency-check-cli-1.3.2.jar:1.3.2]
at org.owasp.dependencycheck.App.run(App.java:123) [dependency-check-cli-1.3.2.jar:1.3.2]
at org.owasp.dependencycheck.App.main(App.java:64) [dependency-check-cli-1.3.2.jar:1.3.2]
2015-12-11 12:48:12,421 org.owasp.dependencycheck.data.nvdcve.CveDB:83
DEBUG - Database dialect: H2
2015-12-11 12:48:12,558 org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
Thanks and Regards.
G

If the DB file is being created then it isn't a permissions issue. The
issue is with the proxy. You should see something like this in the logs if
it can download the data from the NVD:
Checking for updates
NVD CVE requires several updates; this could take a couple of minutes.
Download Started for NVD CVE - 2002
Download Started for NVD CVE - 2004
Download Started for NVD CVE - 2003
Download Complete for NVD CVE - 2003  (950 ms)
Download Started for NVD CVE - 2005
Processing Started for NVD CVE - 2003
Download Complete for NVD CVE - 2004  (1528 ms)
Download Started for NVD CVE - 2006
Download Complete for NVD CVE - 2002  (1913 ms)
Download Started for NVD CVE - 2007
Download Complete for NVD CVE - 2005  (1365 ms)
Download Started for NVD CVE - 2008
Download Complete for NVD CVE - 2007  (2711 ms)
Download Started for NVD CVE - 2009
Download Complete for NVD CVE - 2008  (3646 ms)
Download Complete for NVD CVE - 2009  (2812 ms)
Processing Complete for NVD CVE - 2003  (5548 ms)
Download Complete for NVD CVE - 2006  (4920 ms)
Processing Started for NVD CVE - 2004
Download Started for NVD CVE - 2011
Download Started for NVD CVE - 2010
Download Started for NVD CVE - 2012
Download Complete for NVD CVE - 2012  (3847 ms)
Download Started for NVD CVE - 2013
Download Complete for NVD CVE - 2010  (4341 ms)
Download Started for NVD CVE - 2014
Processing Complete for NVD CVE - 2004  (4602 ms)
Processing Started for NVD CVE - 2002
Download Complete for NVD CVE - 2011  (7995 ms)
Download Started for NVD CVE - 2015
Download Complete for NVD CVE - 2014  (3656 ms)
Download Started for NVD CVE - Modified
Download Complete for NVD CVE - Modified  (192 ms)
Download Complete for NVD CVE - 2013  (4804 ms)
Download Complete for NVD CVE - 2015  (1414 ms)
Processing Complete for NVD CVE - 2002  (4808 ms)
Processing Started for NVD CVE - 2005
...
If you do not see that, the issue is definately with the proxy. Just to
double check, delete the data directory and re-run dependency-check and
look at the logs. If it fails, you should delete the data directory before
trying again.
--Jeremy
On Wed, Dec 16, 2015 at 6:22 AM, gonzaloFer<EMAIL_ADDRESS>wrote:

Hi!
It doesnt work, I think is not about permissions problem but maybe I am
wrong. Perhaps the problem is because of the proxy, the main error appears
this way:
org.owasp.dependencycheck.exception.NoDataException: No documents exist
at org.owasp.dependencycheck.Engine.ensureDataExists(Engine.java:497)
~[dependency-check-core-1.3.2.jar:1.3.2]
at org.owasp.dependencycheck.Engine.analyzeDependencies(Engine.java:323)
~[dependency-check-core-1.3.2.jar:1.3.2]
at org.owasp.dependencycheck.App.runScan(App.java:201)
[dependency-check-cli-1.3.2.jar:1.3.2]
at org.owasp.dependencycheck.App.run(App.java:123)
[dependency-check-cli-1.3.2.jar:1.3.2]
at org.owasp.dependencycheck.App.main(App.java:64)
[dependency-check-cli-1.3.2.jar:1.3.2]
2015-12-11 12:48:12,421 org.owasp.dependencycheck.data.nvdcve.CveDB:83
DEBUG - Database dialect: H2
2015-12-11 12:48:12,558
org.owasp.dependencycheck.reporting.VelocityLoggerRedirect:68
Thanks and Regards.
G
—
Reply to this email directly or view it on GitHub
https://github.com/jeremylong/DependencyCheck/issues/415#issuecomment-165071067
.

Hi,
The last thing Jeremy, I think you are right and definetely is a proxy issue, however I paste another out in log:
DEBUG -
org.owasp.dependencycheck.exception.NoDataException: No documents exist
at org.owasp.dependencycheck.Engine.ensureDataExists(Engine.java:497) ~[dependency-check-core-1.3.3.jar:1.3.3]
at org.owasp.dependencycheck.Engine.analyzeDependencies(Engine.java:323) ~[dependency-check-core-1.3.3.jar:1.3.3]
at org.owasp.dependencycheck.App.runScan(App.java:201) [dependency-check-cli-1.3.3.jar:1.3.3]
at org.owasp.dependencycheck.App.run(App.java:123) [dependency-check-cli-1.3.3.jar:1.3.3]
at org.owasp.dependencycheck.App.main(App.java:64) [dependency-check-cli-1.3.3.jar:1.3.3]
I dont know if can help to solve this problem. Thanks.

Here is what is going on.

dependency-check is trying to reach out to the Internet to download the CVE data from the NVD; this fails
Failures early in the pipeline (i.e. updating the CVE data) does not halt the dependency-check executioin - the assumption is we likely have data from a previous download and there is a temporary issue with the Internet connection or the NVD site is down (this has happened in the past). As such, execution continues.
When dependency-check gets to a point that it needs CVE data to perform the analysis it does a double check to see if there is any useful data in the DB. Since there is not, it throws this error.

My best suggestions would be to hook up something like Wireshark and see what is actually going across the wire. My guess is there is something misconfigured with the proxy. See the Proxy Configuration section on the dependency-check Maven documentation site.
Jeremy

Have you been able to resolve your issue?

If you continue to have issues with the plugin, please open a new ticket as I believe this issue has been resolved.

Hi,
After i did as wrote on :-  http://jeremylong.github.io/DependencyCheck/data/mirrornvd.html
I am facing this issue : -
[root@gitlabserver neeraj]# sh dep-check-date.sh "NVD" "11/28/2016" --project virmani -s "/tmp/neeraj/my_code"
[INFO] Checking for updates
Exception in thread "main" java.lang.IllegalArgumentException: URI has an authority component
at java.io.File.(File.java:423)
at org.owasp.dependencycheck.utils.Downloader.getLastModified(Downloader.java:249)
at org.owasp.dependencycheck.utils.Downloader.getLastModified(Downloader.java:228)
at org.owasp.dependencycheck.data.update.nvd.UpdateableNvdCve.add(UpdateableNvdCve.java:101)
at org.owasp.dependencycheck.data.update.NvdCveUpdater.retrieveCurrentTimestampsFromWeb(NvdCveUpdater.java:330)
at org.owasp.dependencycheck.data.update.NvdCveUpdater.getUpdatesNeeded(NvdCveUpdater.java:259)
at org.owasp.dependencycheck.data.update.NvdCveUpdater.update(NvdCveUpdater.java:79)
at org.owasp.dependencycheck.Engine.doUpdates(Engine.java:678)
at org.owasp.dependencycheck.Engine.analyzeDependencies(Engine.java:489)
at org.owasp.dependencycheck.App.runScan(App.java:272)
at org.owasp.dependencycheck.App.run(App.java:164)
at org.owasp.dependencycheck.App.main(App.java:69)
With NoUpdate :-
[root@gitlabserver neeraj]# sh dep-check-date.sh "NVD" "11/28/2016" --project virmani -s "/tmp/neeraj/my_code" --noupdate
[ERROR] No documents exist
Unable to continue dependency-check analysis.
[ERROR] One or more fatal errors occurred
[ERROR] No documents exist
==========
My env :-
Java :- 1.8.0_91
Dependency Check version :- 1.4.4
Thanks,
Neeraj Virmani

Not sure what is in dep-check-date.sh. Based on googling the error message "URI has an authority component" I'm guessing that the URL you are providing is not valid.

The Data folder should have some old database from any previous run to resolve the issue of " No documents exist"
For URI :- there has to be an extra / in the file , ie
--cveUrl20Modified file:///NVD/2016-11-28/nvdcve-2.0-Modified.xml.gz       CORRECT
--cveUrl20Modified file://NVD/2016-11-28/nvdcve-2.0-Modified.xml.gz         INCORRECT
Thanks,
Neeraj Virmani

so can this issue be closed?
--Jeremy


Include instructions for building and testing with cargo

Is there a reason to do this in the same repository?

Is there a reason to do this in the same repository?

The rust rewrite in general?  The consensus seemed that the main pro was that we could keep the existing issues in place by doing it in the same repo.  And that eventually this would become the master branch once it was deemed ready.

Is there a reason to do this in the same repository?
The rust rewrite in general? The consensus seemed that the main pro was that we could keep the existing issues in place by doing it in the same repo. And that eventually this would become the master branch once it was deemed ready.

OK, as long as there was discussion.


pretrained model are not available

Dear author,
Thanks for your work!
When I reproduce the results in the paper, I found that link  'https://drive.google.com/drive/folders/1PTi37xlPxqhHNyxs_4xiGGj1OsnTQhWD?usp=sharing' is empty. Could you share permissions on the project?
Thanks!!

They should be available now :)


Failed to update registry credential 1c18 Error

Rancher: 1.0
Log:
Checking: https://#########.dkr.ecr.us-east-1.amazonaws.com
Checking registry: #########.dkr.ecr.us-east-1.amazonaws.com against: #########.dkr.ecr.us-east-1.amazonaws.com
Failed to update registry credential 1c18, Resource type [registryCredential] is not updatable
Not entirely sure whether it's a setting I need to configure on the ecr side or a parameter I'm missing/misconfigured on ecr-container.
Please advise

Sounds like a change that they made in the 1.0 release.

@bobjana Not sure what the problem might be here, but I just updated one of my clusters that is using this same service and I'm not having any issues.
Are you still experiencing problems?

I had this issue running v1.0.0 of this image, updating to v1.0.1 fixed it.

Went with comment above and upgraded to 1.0.1
Now I'm getting a different error:
Failed to create rancher client: Get : unsupported protocol scheme ""
Error updating ECR, Get : unsupported protocol scheme ""
Also note that I installed it via rancher catalog (which has the old 1.0.0 version), upgraded it to 1.0.1 and started it from within rancher.

you probably lost the labels - there is one that sets the right env vars which allows you to connect to rancher api.
Start over, remove the service you added from catalog and create a new stack with this docker-compose.yml:
ecr-updater:
  environment:
    AWS_ACCESS_KEY_ID: ${aws_access_key_id}
    AWS_SECRET_ACCESS_KEY: ${aws_secret_access_key}
    AWS_REGION: ${aws_region}
  labels:
    io.rancher.container.pull_image: always
    io.rancher.container.create_agent: 'true'
    io.rancher.container.agent.role: environment
  tty: true
  image: objectpartners/rancher-ecr-credentials:1.0.1
  stdin_open: true

smazurov Thank you very much! Issue resolved.

@smazurov thanks for helping out on this!


[YamlCreate] Don't route through aka.ms when running on Github-Actions

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@denelon since you're online, please take a minute to merge this


Build perf test to profile the algorithm

Perf tests are required to profile how fast/accurate the algorithm performs, comparing to various versions of the application.

Use TestRunner to assert performance of the algorithm.


Question on evaluation protocol used in paper

I would like to check some details in your paper "Pose2Seg: Detection Free Human Instance Segmentation". For the AP scores reported in Tables 2 & 3, can I check if these scores are evaluated on what type of IOU computation (bounding box or segmentation)? To be specific, I am refering to the iouType here https://github.com/cocodataset/cocoapi/blob/master/PythonAPI/pycocotools/cocoeval.py

Hi. Those are segmentation iou. a.k.a segm for iouType

Alright, thank you!


How on earth do I restart Cabernet?

Running Ubuntu, and I cannot find the option on the webinterface to restart, and I don't want to restart my instance just to apply the changes

Scheduled Tasks > Applications > Restart


Recorder: use a shaded version of BouncyCastle

This will only be used by the Recorder and shouldn't be used by end users.
This way, we won't risk clashing with user provided libs, eg https://groups.google.com/g/gatling/c/VRnFH1u7BTs

Breaking classpath change, will only ship in 3.8


Signup Email verification not working

Trying to sign up to your website and the email verification is not received. Please check.

There is our SendGrid account problem, we have fixed it.


Difficult to troubleshoot parsing errors

Environment

Python version:
circuit_maintenance_parser version:

Expected Behavior
Parsing failure should result in a clearly formatted exception and/or logging message to make it easy to troubleshoot and fix.

Observed Behavior
Due to the logic in https://github.com/networktocode/circuit-maintenance-parser/blob/develop/circuit_maintenance_parser/providers.py#L60 that catches all ParsingError exceptions raised by individual parser classes and discards them, the only log messages seen are generic, i.e.:
Parser HtmlParserCogent1 for provider Cogent was not successful

and the ultimately raised ParsingError is similarly generic:
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/nautobot_circuit_maintenance/handle_notifications/handler.py", line 193, in process_raw_notification
    parsed_notifications = parser.process()
  File "/usr/local/lib/python3.7/site-packages/circuit_maintenance_parser/providers.py", line 81, in process
    raise ParsingError("None of the parsers was able to parse the notification")
circuit_maintenance_parser.errors.ParsingError: None of the parsers was able to parse the notification

This makes it very difficult to diagnose why the parsing failed.

Steps to Reproduce

Improved in #42


FIX Exclude thirdparty dir from code coverage

we probably want to enable codecov on 4 branch

Looks like this is for the default branch to display on the dashboard rather than disabling others - https://docs.codecov.io/docs/codecov-yaml#section-default-branch

oh, ok. cool


Cargo Audit Fixes

Motivation

Cargo Audit Fix

Test Plan

CI/CD tests are covered

/canary

:broken_heart: Test Failed - ci-test

/canary

:broken_heart: Test Failed - ci-test

:broken_heart: Test Failed - ci-test

Closing this PR due to technical issue, New PR - https://github.com/diem/diem/pull/10879


Add Polygon zkEVM Testnet

See here.

Resolved via https://github.com/pcaversaccio/create2deployer/commit/93c0296f5cb21f8a6b1e74917168866329570fea.


Create USISubmarinePack.netkan

Fix #2856.  Note that this depends on a version of USITools that hasn't been properly released yet, but is included in the zip. Should mean this mod does not initially appear as available. Should I do a hand-wrought USITools-<IP_ADDRESS>.ckan sourcing from this download?

Please put thin on hold by author.

USI Tools was recently updated, it may be time to give it another look.

Checked with RoverDude last night, and confirming that 'blocked on author' is correct here.  The sub is still considered experimental.

RoverDude is taking over maintenance of his own metadata, so I'll close this and we can re-open if it's ever needed.

Yeah. Sorry for jumping over your PR for removing his mods, but Bob was in the chat complaining about not being able to move forward, and I couldn't think how to remove the deletion of two files from your PR.

It's all a collaboration. There's no jumping over someone else or anything of the sort.


Error when signing a transaction without specifying allowedSignHash to signPsbt request method

I am looking for some guidance here. I am trying to rely on the sig hash's specified in the inputs of a PSBT by not passing allowedSignHash into the signPsbt request method. When doing this, I am getting this error after Confirm in the wallet:

The docs for signPsbt allowedSignHash parameter:
a number representing the sigHash type to use for signing.
will default to the sighash type of the input if not provided.

The full set of parameters are:
{
  "broadcast": false,
  "psbt": "cHNidP8BAJoCAAAAAuYCeZMEme7DCP+M/kzDSjO+aTjpH1adSFnX4gM+cN3IAAAAAAD/////zP/hoEXZoV35MQYEq8y4dmjMWr+XjQHa+6eOd8KknVgAAAAAAP////8CAQAAAAAAAAAWABSDAMplKKzmqC3fqbv2MnZZu3CBUQEAAAAAAAAAFgAUgwDKZSis5qgt36m79jJ2WbtwgVEAAAAAAAEBKwEAAAAAAAAAIlEgzKfnj70ukeU4i0q6DEOJ3S6zPydXyGlyjZGRZ33thfMBAwQBAAAAARcgPcAfGktmVncnTqmhdMz/SuC+th6PgoS71xpyhHxA7mEAAQErAQAAAAAAAAAiUSDMp+ePvS6R5TiLSroMQ4ndLrM/J1fIaXKNkZFnfe2F8wEDBAMAAAABFyA9wB8aS2ZWdydOqaF0zP9K4L62Ho+ChLvXGnKEfEDuYQAAAA==",
  "signInputs": {
    "bc1pgeae0s2zkjvezffs9essn9azf67h29ceh8nd9548vcrcfmfxwajqnh9fkh": [
      0,
      1
    ]
  }
}

The sig hash types for the 2 inputs are:
input1 sighash type: 1
input2 sighash type: 3

What am I doing wrong?

@wolfpack94 the documentation is actually incorrect; this is currently a required field. I think it should work for your transaction if you set it to the bitwise-and of all the sighashes you use (in your case, 3 should do it).
We'll be aligning the implementation with the documentation in the next 1 or 2 major releases.


Add Contributors Guide

As a separate document linked to from the Readme. The Linux Foundation has good templates.

pull request submitted: https://github.com/Adora-Foundation/awesome-green-extensions/pull/19


Check why nothing is bundled

Test out command line on some of the libraries: https://rollupjs.org/guide/en/#quick-start

Seems there are some hints here:
https://www.learnwithjason.dev/blog/learn-rollup-js


Date 08/10/2000 in DD/MM/YYYY format is invalid

Versions

vee-validate: 2.1.0-beta.9
vue: 2.5.2

Describe the bug
I have fields set in v-validate="{date_format: 'DD/MM/YYYY'}", but when I enter the date 10/8/2000 the validation returns an error saying that the date is not in DD/MM/YYYY format
To Reproduce
Steps to reproduce the behavior:

Go to https://baianat.github.io/vee-validate/guide/rules.html#date-format. In my browser, the default format is DD/MM/YYYY (pt-br)
Type the date 08/10/2000
See error

Demo Link

Desktop (please complete the following information):

OS: [e.g. Windows]
Browser [chrome]
Version [69]

I tested your examples on Windows Chrome and Firefox and it's working fine for me, are you sure about your code samples? Are you leaving out any additional details about the issue?

I have the same problem.
The date he used does not work here either.
Another example is: 04/11/2018

Same here, i have another dates too:
08/10/2000, 06/10/1996, 06/10/1997, ...
http://prntscr.com/l5o7v0
@woodyalan, @viniazvd and i are brazilians, maybe have some connection with the language of the browser

Have the same problem.  I noticed that seems to occur only in chrome, using firefox some dates validate without any problem.

@logaretm the reproduction has been updated, for me the problem still happens:

I can't reproduce it by using your link but I encountered similar issue with date_format.
Not sure if it's programmatic validation only but that's my case. I encountered it by using $validator.attach()
Steps to reproduce:

Import vee-validate.minimal.esm post beta.9
Name import a rule that relies on paramNames from rules.esm (date_format for example)
Imported rule is an object { validate, options, paramNames }
Prior to beta.9 it was { validate, options } but there was no dependency on paramNames
Since you've never had to write a complex rule that takes a parameter (which is my case 😛) you simply use Validator.extend('date_format', date_format) and it doesn't work since you've lost paramNames

It's not a bug, just a change in API
Change was made in https://github.com/baianat/vee-validate/commit/21657547b1db00f28bb68d9216243d7ca962786d#diff-41be0caf6b7db8122ef83bff240e0222
Solution:
.extend doesn't handle object argument you have to do it either line by line or adopt @logaretm code from https://github.com/baianat/vee-validate/blob/master/src/index.js#L7-L10
The change is mentioned in documentation and briefly in beta.9 changelog
I suggest making the change more explicit for the rules that must have paramNames
I don't want to do a PR as I'm having a hard time understanding API internals and reasoning behind the changes.

I'm having the same problem with the date 25/10/1992 (firefox and chrome on linux)

I have the same issue with the date 04/11/2018.
Versions

vee-validate: 2.1.2
vue: 2.5.17

Describe the bug
I have fields set in v-validate="'required|date_format:DD/MM/YYYY'" but when I enter the date 04/11/2018 the validation returns an error saying that the date is not in DD/MM/YYYY format.
To Reproduce

Go to https://baianat.github.io/vee-validate/guide/rules.html#date-format
Type the date 04/11/2018
See error

Desktop

OS: Windows 10
Browser: Chrome
Version: 70.0.3538.77

Same here, i have another dates too:
08/10/2000, 06/10/1996, 06/10/1997, ...
http://prntscr.com/l5o7v0
@woodyalan, @viniazvd and i are brazilians, maybe have some connection with the language of the browser

Given the people who reported this problem really seems to have some connection with environments configured with the Brazilian Portuguese language.

I have rule for validation:
buyerBirthdayRules () {
        let maxDate = new Date();
        maxDate.setFullYear(maxDate.getFullYear() - 18);
        maxDate = helpers.formatDate(maxDate, true)

        return `required|date_format:DD.MM.YYYY|after:01.01.1900|before:${maxDate}`;
},

Input any dates triggering error: The buyerBirthday must be after 01.01.1900. Even if I input 01.01.1990 of near dates.

This issue is a pain to debug properly since firefox and chrome seem to have different opinions on what new Date() should return. This offsets the date validation.
This is related to #1693
VeeValidate uses<EMAIL_ADDRESS>to validate dates, but the library isn't equipped (yet) to deal with timezones and overflown dates eg: 22/33/2013. So we account for that by parsing the date, then formatting the parsed result and match it with the input. If nothing changes then its a valid date, if something changed (day, hour, or whatever) then the date was manipulated in some way (overflow or timezone offsetted by new Date()).
The new versions seem to address this issue, as the offset isn't observed in firefox anymore, there is a PR that introduces the pkg update #1698 Which introduces a breaking change to the format.
I would appreciate testing the PR against your environments:

Clone the repo
Checkout the update-date-fns branch.
install the dependencies: yarn and build the project: yarn build
Run the local docs version: yarn docs:dev
Test the page

This issue is a pain to debug properly since firefox and chrome seem to have different opinions on what new Date() should return. This offsets the date validation.
This is related to #1693
VeeValidate uses<EMAIL_ADDRESS>to validate dates, but the library isn't equipped (yet) to deal with timezones and overflown dates eg: 22/33/2013. So we account for that by parsing the date, then formatting the parsed result and match it with the input. If nothing changes then its a valid date, if something changed (day, hour, or whatever) then the date was manipulated in some way (overflow or timezone offset by new Date()) the latter wasn't accounted for.
The new versions seem to address this issue, as the offset isn't observed in firefox anymore, there is a PR that introduces the pkg update #1698 Which introduces a breaking change to the format.
I would appreciate testing the PR against your environments:
* Clone the repo

* Checkout the `update-date-fns` branch.

* install the dependencies: `yarn` and build the project: `yarn build`

* Run the local docs version: `yarn docs:dev`

* Test the page

It looks like in this branch the validation stopped working.
Tested on:
Firefox 63.0.1 (locale pt_BR) - Windows 10
Chrome 70.0.3538.77 (locale pt_BR) - Windows 10

I believe the problem is just the documentation. Changing date_format from "DD/MM/YYYY" to "dd/MM/yyyy" worked fine.

@fabianosobreira yep the docs haven't been updated yet in the branch, it "breakingly" changes the format.

i'm having same issue with date 04/11/2018... pt_br too.
tried "dd/MM/yyyy" and it doen't work

I am having the same problem. Valid dates are not validating. Has this been merged in yet?

closed by #1698


Feat & Fix : markdown added and removed html rendering

Fixes  #75 #76 #77

Great work @saisumanthkumar! Merging your PR


:book: Restore and Update installation info for go in required packages documentation

Summary
Restore notes about installing go as a prerequisite if the user intends to build kubestellar locally
Instructions for all OS tabs were added to the file
in response to issue #1026
Fixes #

The new instructions are only for human reading, not docs-ecutable running in bash, right? That would be different from the other instructions; is that deliberate?

Also, as a general rule: if I already have something installed by a different package manager, please do not do an additional install.

The new instructions are only for human reading, not docs-ecutable running in bash, right? That would be different from the other instructions; is that deliberate?

Yes. As I was reading the assorted instructions on the go website, it was abundantly clear that go is SUPER fussy about how it is installed (or re-installed). So I copied the instructions for different OS configurations from there as well as referring back to that page.

And the GitHub workflows cover for go by having a step that installs it.
I wonder if there is a GitHub action that installs ko?
/approve


append x-request-start header to incoming HTTP requests

Some tracing applications support reporting on queuing time for incoming requests. Generally this is implemented by adding a X-Request-Start timestamp header to the requests as early as possible in the request path.
New Relic and datadog are two examples of tools that support this header.
The envoy docs say:

Custom request/response headers can be added to a request/response at
the weighted cluster, route, virtual host, and/or global route
configuration level

I've opted to add them at the weighted cluster level, based on a slack discussion with @stevesloka. I'm happy to change that if requested though - my envoy knowledge is pretty low, and I'm not sure what the tradeoffs of each location are.
The header is added to all requests unconditionally, as suggested in the original github issue.
Fixes #646

I tested this by pushing it to a test GKE cluster, in front of a nginx pod that echos back the request headers. The result looked like this:
$ curl -v http://echo.yob.id.au
* Added echo.yob.id.au:80:<IP_ADDRESS> to DNS cache
> GET / HTTP/1.1
> Host: echo.yob.id.au
> User-Agent: curl/7.61.0
> Accept: */*
>
< HTTP/1.1 200 OK
< server: envoy
< date: Thu, 04 Oct 2018 13:48:22 GMT
< content-type: text/plain
< x-envoy-upstream-service-time: 0
< transfer-encoding: chunked
<
GET / HTTP/1.1
host: echo.yob.id.au
user-agent: curl/7.61.0
accept: */*
x-forwarded-for: <IP_ADDRESS>
x-forwarded-proto: http
x-envoy-internal: true
x-request-id: ce2e2dea-e639-4bca-ace5-5e5d2ec6d790
x-envoy-expected-rq-timeout-ms: 15000
x-request-start: t=1538660902.962
content-length: 0

Test flake is #705, please rebase.

Test flake is #705, please rebase

done

@yob, can you please rebase to master. Thanks

done :)

Thank you!

Thanks!


Pin xgboost<1.6.1 so we (temporarily) avert documentation failing to build

Description

This is a temporary fix - I don't know what the root cause of the docs build failure is in relation/from xgboost, but I know xgboost=1.5.1 (the last version before the latest 1.6.1) is not causing it - @schlunma @zklaus if you guys have some time to investigate deeper, if not, let's get this in for now methinks :+1:

Closes #2779

Before you get started

[x] ☝ Create an issue to discuss what you are going to do

Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

[x] 🛠 This pull request has a descriptive title
[x] 🛠 Tests run successfully
[x] 🛠 Any changed dependencies have been added or removed correctly
[x] 🛠 All checks below this pull request were successful

There is also a version 1.6.2 (https://github.com/dmlc/xgboost/releases/tag/v1.6.2), did that also cause the problem?

I guess we'll have to wait and see - it's not yet on conda-forge, the latest there is still 1.6.1 https://anaconda.org/conda-forge/xgboost - but a good pointer to maybe hang on with this PR until we can test with 1.6.2 from c-f

good find @zklaus - I shall take it for a spin!

many thanks for suggesting the new 1.6.2 @schlunma  @zklaus - xgboost                               1.6.2  cpu_py310hd1aba9c_0          conda-forge/linux-64      is doing the trick for our documentation! :beer:


Suggestion: follow symlinks to save the macOS use-case

It's common to install libraries with Homebrew on macOS. However, when linking those libraries with the pkg-config crate, the -L/usr/local/lib flag is passed to Cargo. This may cause conflicts with dynamic resolution: /usr/local/lib gets always searched first, and unrelated libraries may override system libraries causing havoc.
An example: dynamically loaded libjpeg is a transitive dependency of Diesel. However, an incompatible version of libjpeg is also commonly installed to /usr/local/lib as a dependency of some Homebrew application. A dependency of Diesel, libpq used to support finding the native library using the pkg-config crate, but since that passes -L/usr/local/lib to Cargo which breaks libjpeg, the support had to be revoked.
libpq itself now avoids passing /usr/local/lib to Cargo, and instead checks if the library is actually a symlink. In the case of Homebrew, it always is; every library resides in their own directories, like /usr/local/Cellar/jpeg/8d/lib/. Thus, passing that to Cargo doesn't cause conflicts with other libraries.
To be usable in the macOS ecosystem, it would be beneficial if the pkg-config crate would provide this symlink-following behaviour for the users.

Btw. part of the problem seems to be that Homebrew is inconsistent with the link flags: some .pc files declare the /usr/local/lib directory while some directly declare the "keg" directory (=actual, single-library-exclusive install directory). I filed a GitHub issue to Homebrew that it would be good if they had a general guideline to declare the "keg" dir, since passing an exclusive directory should prevent any conflicts, and that's why they have them, but it would be super nice if pkg-config also had this stop-gap measure to improve the overall robustness of this stuff!

This sounds like it'd almost want to be a pkg-config feature rather than a pkg-config-rs feature? How would we know what symlinks to follow?

You're right in the sense that it would be ideal if pkg-config always returned the "right" directory. However, it quite simply returns what's stated in the .pc files, and in that sense, this is actually a problem of Homebrew as they provide .pc files with slightly misleading information.
What pkg-config-rs could do, is to check the library file like compilers do. It already knows the -L and -l flags pkg-config returned to it. Let's say that we're on macOS and pkg-config returned the flags -L/usr/local/lib -lpq. That would mean checking whether /usr/local/lib/libpq.dylib is a symlink, and if it is, follow it, and return updated flags, for example: -L/usr/local/Cellar/jpeg/8d/lib/ -lpq instead.

I'd prefer to avoid adding a pseudo-linker in pkg-config-rs, though. All we get is flags, we don't actually know where libs are ourselves. Passing something more specific would require pkg-config-rs to interpret the meaning of flags and start looking in paths and such.

Yeah, that is totally understandable. I just wonder, what's the next best thing to do? pkg-config as it currently is, is broken on macOS (For Homebrew users, that is. But that's the most popular package manager for macOS. It may be broken for Fink and MacPorts too, but I haven't tested.), and just trying this simple heuristic should fix the problem, and make it an it-just-works experience. It's something that isn't pkg-config-rs's responsibility, as it's doing what's expected of a simple wrapper. It just seems the most straightforward way to fix things.

What package is printing out -L/usr/local/lib? A few I've spot-checked I've got install with homebrew all print out -L/usr/local/Cellar/... which seems to me like the best solution here

Okay, that's great to hear. It's specifically libpq of the postgresql package that prints out -L/usr/local/lib. I checked all of my packages, and found out that most of the packages did print out the Cellar path which is great. postgres-related things didn't, and SDL-related things didn't.
I was under an impression that a larger portion of packages would print out the problematic -L/usr/local/lib, but apparently this was false. So maybe it's possible to fix at the Homebrew side after all, case-by-case.

Oh yeah that'd be ideal if the postgres package could be updated to print out the local version to avoid pollution of picking up other libs by accident.


November updates

updated dependencies
modified text
added county to identify
Please visit https://parcels.dev.utah.gov/ and approve the changes to deploy to production.

I think this looks great. Adding the county name to the website link seems a bit redundant but I am sure next week I will love it.


Decision Tree Regressor

Define You:

[x] DevIncept Participant
[x] Contributor

Is your feature request related to a problem? Please describe.

I want to contribute Decision Tree Regressor Algorithm using this dataset by following the given project structure.

Describe the solution you'd like...

I'll proceed by following steps:
Step 1: Data preprocessing and exploration.
Step 2: Data visualization to draw useful insights.
Step 3: Data training & model creation.
Step 4: Performance evaluation to check efficiency of the algorithm by error & accuracy check.

@prathimacode-hub, please assign it to me.

Issue assigned. @ayushi424


FAILURE: Build failed with an exception.

Current Behavior
BUILD SUCCESSFUL in 29s
1 actionable task: 1 executed
Subproject Path: CordovaLib
Subproject Path: app
Downloading https://services.gradle.org/distributions/gradle-7.6-all.zip
...............10%................20%................30%................40%...............50%................60%................70%................80%...............90%................100%
Welcome to Gradle 7.6!
Here are the highlights of this release:

Added support for Java 19.
Introduced --rerun flag for individual task rerun.
Improved dependency block for test suites to be strongly typed.
Added a pluggable system for Java toolchains provisioning.

For more details see https://docs.gradle.org/7.6/release-notes.html
Starting a Gradle Daemon (subsequent builds will be faster)
BUILD SUCCESSFUL in 29s
1 actionable task: 1 executed
Subproject Path: CordovaLib
Subproject Path: app
Downloading https://services.gradle.org/distributions/gradle-7.6-all.zip
...............10%................20%................30%................40%...............50%................60%................70%................80%...............90%................100%
Welcome to Gradle 7.6!
Here are the highlights of this release:

Added support for Java 19.
Introduced --rerun flag for individual task rerun.
Improved dependency block for test suites to be strongly typed.
Added a pluggable system for Java toolchains provisioning.

For more details see https://docs.gradle.org/7.6/release-notes.html
Starting a Gradle Daemon (subsequent builds will be faster)
FAILURE: Build failed with an exception.

What went wrong:
Could not open settings generic class cache for settings file 'C:\Users\ehab\eqlimy\platforms\android\settings.gradle' (C:\Users\ehab.gradle\caches\7.6\scripts\dqjrgsw17c62wbpoagod92e1e).

BUG! exception in phase 'semantic analysis' in source unit 'BuildScript' Unsupported class file major version 64

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.6/userguide/command_line_interface.html#sec:command_line_warnings
BUILD FAILED in 2m 34s
Command failed with exit code 1: C:\Users\ehab\eqlimy\platforms\android\gradlew -b C:\Users\ehab\eqlimy\platforms\android\build.gradle cdvBuildDebug
C:\Users\ehab\eqlimy>

What went wrong:
Could not open settings generic class cache for settings file 'C:\Users\ehab\eqlimy\platforms\android\settings.gradle' (C:\Users\ehab.gradle\caches\7.6\scripts\dqjrgsw17c62wbpoagod92e1e).

BUG! exception in phase 'semantic analysis' in source unit 'BuildScript' Unsupported class file major version 64

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.6/userguide/command_line_interface.html#sec:command_line_warnings
BUILD FAILED in 2m 34s
Command failed with exit code 1: C:\Users\ehab\eqlimy\platforms\android\gradlew -b C:\Users\ehab\eqlimy\platforms\android\build.gradle cdvBuildDebug
C:\Users\ehab\eqlimy>
Expected Behavior
gradle-8.7-all
Context (optional)
No response
Steps to Reproduce
gradle-8.7-all
Gradle version
gradle-8.7-all
Build scan URL (optional)
gradle-8.7-all
Your Environment (optional)
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

Starting Daemon
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.7/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
BUILD SUCCESSFUL in 29s
1 actionable task: 1 executed
Subproject Path: CordovaLib
Subproject Path: app
Downloading https://services.gradle.org/distributions/gradle-7.6-all.zip
...............10%................20%................30%................40%...............50%................60%................70%................80%...............90%................100%
Welcome to Gradle 7.6!
Here are the highlights of this release:

Added support for Java 19.
Introduced --rerun flag for individual task rerun.
Improved dependency block for test suites to be strongly typed.
Added a pluggable system for Java toolchains provisioning.

For more details see https://docs.gradle.org/7.6/release-notes.html
Starting a Gradle Daemon (subsequent builds will be faster)
FAILURE: Build failed with an exception.

What went wrong:
Could not open settings generic class cache for settings file 'C:\Users\ehab\eqlimy\platforms\android\settings.gradle' (C:\Users\ehab.gradle\caches\7.6\scripts\dqjrgsw17c62wbpoagod92e1e).

BUG! exception in phase 'semantic analysis' in source unit 'BuildScript' Unsupported class file major version 64

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.6/userguide/command_line_interface.html#sec:command_line_warnings
BUILD FAILED in 2m 34s
Command failed with exit code 1: C:\Users\ehab\eqlimy\platforms\android\gradlew -b C:\Users\ehab\eqlimy\platforms\android\build.gradle cdvBuildDebug
C:\Users\ehab\eqlimy>

Your issue appears to be a question about how to use Gradle. They should be asked in a different channel, so we will close it. Your question might be answered in Gradle documentation or on our community Slack or forums. Find links to these resources on help.gradle.org.
If you think our analysis is wrong, please provide us with more detailed information explaining why.


docs: Customize the namespace used for installation

In the latest version we have introduced a new configuration item.
When users want to install them into different namespaces through Helm,
they need to specify it.
Signed-off-by: Jintao Zhang<EMAIL_ADDRESS>Please answer these questions before submitting a pull request

Why submit this pull request?

[ ] Bugfix

[ ] New feature provided

[ ] Improve performance

[ ] Backport patches

[x] Docs Only

Related issues

Bugfix

Description

How to fix?

New feature or improvement

Describe the details and related test reports.

Backport patches

Why need to backport?

Source branch

Related commits and pull requests

Target branch

ping @gxthrj  @lingsamuel  PTAL


Fix bugs

Ref.

#12689
#12936
#15210
https://github.com/mozilla/pdf.js/commit/3f29892d63fb0fe438c80b67e5173cd9d0d70150#r84442440
#14869
#12432
#14957

Sorry, but we unfortunately cannot accept a PR like this.
Please note that all patches need to contain proper commit messages explaining what's being and importantly why, hence "Fix bugs" is really not sufficient in order to understand the changes. Also, if at all possible, all patches should ideally include tests.
Finally, please note that completely separate changes should usually be split into separate commits (or even separate PRs) to allow reviewing/testing without "mixing" different things.


Switch ModelSearch from os.walk to os.scandir

What type of PR is this? (check all applicable)

[x] Refactor
[ ] Feature
[ ] Bug Fix
[ ] Optimization
[ ] Documentation Update
[ ] Community Node Submission

Have you discussed this change with the InvokeAI team?

[x] Yes
[ ] No, because:

Have you updated all relevant documentation?

[x] Yes
[ ] No

Description
Drastically speeds up initial invokeai startup time and subsequent model scans
Related Tickets & Documents

Related Issue #
Closes #

QA Instructions, Screenshots, Recordings

Merge Plan

Added/updated tests?

[ ] Yes
[ ] No : please replace this line with details on why tests
have not been included

[optional] Are there any post deployment tasks we need to perform?

This needs cross platform testing. Scandir uses different system APIs for each platform than walk.
Also we should probably manually test the outputs from each method to ensure the behaviour isn't changed.

This needs cross platform testing. Scandir uses different system APIs for each platform than walk.
Also we should probably manually test the outputs from each method to ensure the behaviour isn't changed.

The only change I think we need to make here is to pass the as_posix value to scandir rather than the Path object because that is where the cross platform issues might pop up. Afaik, scandir itself works well cross platform as long as the supplied path is a string that is absolute.


Correct docker command for starting Jaeger

Currently specified command is not enough to make it work.

I think someone recently modified and simplified the command - we should double check how this could go so wrong.

I think someone recently modified and simplified the command - we should double check how this could go so wrong.

@janpio
Do you mean someone modified the page in the docs? Looking at the page history, the line has already been the simplified form. Original commit where the page was added: https://github.com/prisma/docs/commit/effab66f11c0a2415cff54ad20ce09140bb272a2

I am probably remembering a change done to that PR while it was till open then - I am pretty sure that I commented that the command does not work on windows being multi line.
It now again does not run on Windows of course:
C:\Users\Jan\Documents\throwaway>docker run -d --name jaeger \
docker: invalid reference format.
See 'docker run --help'.

C:\Users\Jan\Documents\throwaway>  -e COLLECTOR_ZIPKIN_HOST_PORT=:9411 \
'-e' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Jan\Documents\throwaway>  -e COLLECTOR_OTLP_ENABLED=true \
'-e' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Jan\Documents\throwaway>  -p 6831:6831/udp \
'-p' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Jan\Documents\throwaway>  -p 6832:6832/udp \
'-p' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Jan\Documents\throwaway>  -p 5778:5778 \
'-p' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Jan\Documents\throwaway>  -p 16686:16686 \
'-p' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Jan\Documents\throwaway>  -p 4317:4317 \
'-p' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Jan\Documents\throwaway>  -p 4318:4318 \
'-p' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Jan\Documents\throwaway>  -p 14250:14250 \
'-p' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Jan\Documents\throwaway>  -p 14268:14268 \
'-p' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Jan\Documents\throwaway>  -p 14269:14269 \
'-p' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Jan\Documents\throwaway>  -p 9411:9411 \
'-p' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Jan\Documents\throwaway>  jaegertracing/all-in-one:latest


navigator is undefined

Looks like those navigators need to be checked for, at least for SSR:
https://github.com/daphnesmit/prntr/blob/d9b17e2529b417e4a26910eee182365565023e5b/src/utils/browser.ts#L22-L24

Im fixing

2.0.14 on its way now

sorry 2.0.15


Make Flutter NavigationDelegate Webview API Async

https://b.corp.google.com/issues/142816106.

Closing; dupe of https://github.com/flutter/flutter/issues/43271.


[PHPStanRules] Fixes #2327 Add CheckTypehintCallerTypeRule

All checks have passed 🎉 @TomasVotruba it is ready for review.

Very nice, thank you :+1:


Use go routines for batch pipeline

Closing this issue. We don't want to push a lot of traffic to the static maps API to avoid ban


docs: end-user documentation

[ci skip]
(Closes #52)

The commits will be squashed, and there are 3 diagrams that will be added ~1 hour, the text though is ready for review


Footer section

I have removed the share on twitter button and the twitter logo from the footer section..
Issue no #226

thanks


Upgrade from jade@1 to pug@2

Upgrade jade to pug@2
see: https://pugjs.org/api/migration-v2.html
closes: #1575

Coverage increased (+0.7%) to 74.734% when pulling dbbf6d643b2fd0e727b4e7deabe506eef22d9796 on vxcamiloxv:feature-jade-to-pug into 3637b31c7b3159d9c5e8c02448ad87363eae9eab on pump-io:master.

Coverage increased (+0.7%) to 74.734% when pulling dbbf6d643b2fd0e727b4e7deabe506eef22d9796 on vxcamiloxv:feature-jade-to-pug into 3637b31c7b3159d9c5e8c02448ad87363eae9eab on pump-io:master.

@vxcamiloxv this has merge conflicts now; do you want to rebase this branch? If you don't have time that's ok and I can do it

@strugee I'll do it

OK, thank you! I feel bad cause I know it's been a really long time so if you change your mind, I'm happy to do it :thumbsup:

@strugee rebase done, please review it before another major conflict :D

@strugee yeah, already tested


Fixed Schematic building location issue for SpongeSchematics

https://github.com/CrystalGamesMC/Scaffolding/issues/2

Thanks for merging, when do you think you'll be able to release a new maven repo artifact/build that contain the changes from this PR?

Whoops, normally have CI to do that for me, should be all done now.

I was expecting it to be under a new snapshot version but a quick Gradle dependency refresh fixed it! Thanks again.

Once it's stable versions will start to be bumped.


TreatmentStatus vs ReferralTask profile: identifier cardinality does not fit

@NathanPeeters @SmalsJulien
The cardinality does not fit for the identifier. Will the identifier be created by the client or the server?
Please advise!

see https://github.com/hl7-be/referral/issues/400

The identifier will be created by Uhmep (no info about identifier in the payload, and then identifier is created at reception in UHMEP system). => 0..1 (no additional identifier needed at the moment)


Artifacts should be pushed to maven central

From<EMAIL_ADDRESS>on April 26, 2010 20:39:21
Currently, powermock is hosted under it's own repository. The project would
have much greater visibility if it were available under central. Also, most
companies(like mine) have policies preventing developers from pulling in
artifacts from random respositories across the internet. Furthermore, if
everyone were to follow what powermock does, you would need a repository for
every artifact specified in the pom.
It's very simple to set this up, it can be accomplished by one of the project
admins in an afternoon: http://maven.apache.org/guides/mini/guide-central-repository-upload.html Please please consider this request very  carefully. Thank you
Original issue: http://code.google.com/p/powermock/issues/detail?id=257

From<EMAIL_ADDRESS>on April 27, 2010 23:51:17
The reason why we can't upload PowerMock to the central repo is because Javassist is
not there (at least not the version we're depending on). See issue #45 .
Status: Duplicate


Add basic telemetry support

Why this PR?
Allow user to set onFeatureEvaluated callback which be executed whenever a feature flag with telemetry enabled is evaluated.

@rossgrambo Yan used these feature flags for test which are from the centralized feature flag sample. The targeting hash behavior was guarded by it.


Add Elixir exsample

Hi! This PR is to add a Hello World project in case of
Elixir. Details on how to run it, etc. can be found
in the README in the elixir_lang directory.
Thanks for the exciting project!

I have confirmed the operation and will proceed with the merge. Thank you for your cooperation 👍


Consider porting UI to Blueprint

Blueprint (https://jwestman.pages.gitlab.gnome.org/blueprint-compiler/) greatly improves the readability of .ui by reducing the verbosity of the syntax, as well as having better integration with IDEs.
I've done a port of almost all .ui files here https://github.com/alissonlauffer/spot/compare/development...blp if you want to see the diff, but I didn't open a PR because I wanted to know your opinion, and we need to coordinate this task since it would make all PRs that touch .ui files conflict.

Oh I'm definitely interested in switching to blueprint, its even possible to inline some of the definitions in the rust code with the latest gtk-rs. the PR is most welcome :) CI will help us identify what's possibly missing (I suspect we'll have to add the blueprint-compiler to the flatpak manifest)
if we merge this I'll do my best to help those with open PRs. I will try and think about the best strategy for this (worst case scenrio it's always possible to mix ui files and bp ones)


[Hub Generated] Review request for Microsoft.ContainerRegistry to add version preview/2022-02-01-preview

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
April 2022

When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
April 2022

If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ x] No refresh required for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

        "$ref": "#/definitions/InnerErrorDescription"

pl work thru the error flags and ping on armapireview for further review.

Refers to: specification/containerregistry/resource-manager/Microsoft.ContainerRegistry/preview/2022-02-01-preview/containerregistry.json:6033 in cca3c5c. [](commit_id = cca3c5cd4f9a6562ee6fa5b1235ed72d73121c25, deletion_comment = False)

        "$ref": "#/definitions/InnerErrorDescription"

pl work thru the error flags and ping on armapireview for further review.

@Azure/arm-api-review-board Can someone please elaborate on what this means?

@rkmanda The "Swagger SDK Breaking Change" test is flagging API version that are not modified by this PR, and verifying those versions the types have not changed, those were always arrays, is there a suggestion on how to handle this?
https://github.com/Azure/azure-rest-api-specs/pull/18176/checks?check_run_id=6065938225

  "properties": {

Removing the virtualNetworkRules property is a cross-version breaking change, so breaking change review is needed. I've added the appropriate label: next step/instructions are added as a PR comment.

Refers to: specification/containerregistry/resource-manager/Microsoft.ContainerRegistry/preview/2022-02-01-preview/containerregistry.json:4485 in 562b5f7. [](commit_id = 562b5f769776810f4814160868353830b3830bda, deletion_comment = False)

@nelson-wu - Will complete ARM review after breaking change label is resolved. If it happens after this week, please ping the current ARM on-call reviewer to be sure they pick up your PR.

@mentat9 the 'virtualNetworkRules' property was deprecated in our last GA API (2021-09-01 PR) and we are just following with the same on this preview.
Do we still need to open a review for the breaking change?

@mentat9 the 'virtualNetworkRules' property was deprecated in our last GA API that has already been approved and merged (2021-09-01 PR), we are just following with the same on this preview. Do we still need to open a review for the breaking change?

I see it was removed from 2021-09-01, but it shipped in 2021-12-01-preview, which is newer. Presumably that is why it's getting flagged here. This is really confusing, but I guess you don't need another breaking change review for this version.

    "id": {

Recommend not using id, which ARM uses at the top level. Consider storageAccountId, storageAccountResourceId, or resourceId, or similar.

Refers to: specification/containerregistry/resource-manager/Microsoft.ContainerRegistry/preview/2022-02-01-preview/containerregistry.json:4473 in 562b5f7. [](commit_id = 562b5f769776810f4814160868353830b3830bda, deletion_comment = False)

Signed off from ARM with comments.

Thanks for the review.
@fengzhou-msft can you help us with a final review and merge?


Fixed units test execution

Hello!
You've had an incorrect directory to unit tests. I've fixed it by removing /unit/ part from path.

ahhh right, thank you very much


Raidboss popping up with triggers randomly

The issue (in a nutshell), is FFXIV_ACT_Plugin is currently outputting wrong ability name usage, for a bunch of abilities (seems to mostly be related to certain mounts, ponys specifically) - this can cause any of the tank immunity triggers to go off in rhalgar's, etc.
link to that issue here: https://github.com/ravahn/FFXIV_ACT_Plugin/issues/204
however I believe this could also be resolved on the module's end, potentially by limiting those triggers to zones where the raidboss module is loaded through other trigger files might be a cleaner way of solving this issue. (or maybe i'm just spitting out hot garbo)

I think its random people using their skills. I have that in certain areas too.

This is also the same as issue #191.  Until this is fixed upstream in the ACT plugin, in the meantime don't run ACT when idling in RR if this bothers you?


Unset proxy settings from launchpad.

1.We unset http_proxy and https_proxy of launchpad to
avoid the docker getting the inherited values.
2.Move help from src to bin folder to simplify the yaml file.

(reviewing https://github.com/docker-snap/docker/pull/13 first; then we can cargo-cult it here)


Revert path filter

As a related note: It looks like publishing the library to npm, with npm 6, misses the carto-vl.min.js file, even that file is included when using npm pack


Income Breakdown showing erroneous expense

Name of Defective Feature

Income Breakdown

System Settings (Required)

ToolKit Version: 2.13.0
Operating System (Mac/Windows/Etc): Windows 10
Browser (Chrome/Firefox/Safari): Chrome
Browser Version: 76.0.3809.100 (64-bit)
Other Extensions: AdBlock, Grammarly, Ghostery, Dark Reader (not active)

Export of Toolkit Settings (Bottom Left of Settings Page)

[{"key":"AccountsDisplayDensity","value":"2"},{"key":"AccountsEmphasizedOutflows","value":true},{"key":"AccountsStripedRows","value":true},{"key":"AdditionalColumns","value":true},{"key":"AdjustableColumnWidths","value":true},{"key":"AutoDistributeSplits","value":true},{"key":"AutomaticallyMarkAsCleared","value":false},{"key":"BetterScrollbars","value":"0"},{"key":"BudgetCategoryFeatures","value":true},{"key":"BudgetProgressBars","value":"both"},{"key":"BudgetQuickSwitch","value":true},{"key":"BudgetSpendingGoal","value":false},{"key":"CalendarFirstDay","value":"0"},{"key":"CategoryActivityCopy","value":true},{"key":"CategoryActivityPopupWidth","value":"2"},{"key":"ChangeEnterBehavior","value":true},{"key":"CheckCreditBalances","value":true},{"key":"CheckNumbers","value":true},{"key":"ClearSelection","value":true},{"key":"CollapseSideMenu","value":true},{"key":"ColourBlindMode","value":true},{"key":"CompactIncomeVsExpense","value":true},{"key":"CreditCardEmoji","value":true},{"key":"CurrentMonthIndicator","value":true},{"key":"CustomFlagNames","value":true},{"key":"DaysOfBuffering","value":true},{"key":"DaysOfBufferingHistoryLookup","value":"3"},{"key":"DeselectTransactionsOnSave","value":false},{"key":"DisableToolkit","value":false},{"key":"DisplayTargetGoalAmount","value":"0"},{"key":"DisplayTotalMonthlyGoals","value":true},{"key":"DisplayUpcomingAmount","value":true},{"key":"EasyTransactionApproval","value":true},{"key":"EditAccountButton","value":"2"},{"key":"EnableRetroCalculator","value":true},{"key":"EnlargeCategoriesDropdown","value":true},{"key":"EnterToMove","value":true},{"key":"FilterCategories","value":true},{"key":"GoalIndicator","value":false},{"key":"GoalWarningColor","value":true},{"key":"GoogleFontsSelector","value":"4"},{"key":"HideAccountBalancesType","value":"0"},{"key":"HideAgeOfMoney","value":false},{"key":"HideHelp","value":true},{"key":"HideReferralBanner","value":true},{"key":"HideTotalAvailable","value":false},{"key":"HighlightNegatives","value":true},{"key":"ImportNotification","value":"1"},{"key":"IncomeFromLastMonth","value":"1"},{"key":"IncomeVsExpenseHoverHighlight","value":true},{"key":"LargerClickableIcons","value":true},{"key":"LinkToInflows","value":false},{"key":"MonthlyNotesPopupWidth","value":"2"},{"key":"NavDisplayDensity","value":"2"},{"key":"Pacing","value":"2"},{"key":"PrintingImprovements","value":true},{"key":"PrivacyMode","value":"0"},{"key":"QuickBudgetWarning","value":true},{"key":"ReconciledTextColor","value":"0"},{"key":"RemovePositiveHighlight","value":true},{"key":"RemoveZeroCategories","value":false},{"key":"ResizeInspector","value":true},{"key":"ResizeSidebar","value":false},{"key":"RightClickToEdit","value":true},{"key":"RowHeight","value":"0"},{"key":"RowsHeight","value":"0"},{"key":"RunningBalance","value":"1"},{"key":"SeamlessBudgetHeader","value":true},{"key":"SetMultipleFlags","value":false},{"key":"ShowCategoryBalance","value":true},{"key":"ShowIntercom","value":true},{"key":"SpareChange","value":false},{"key":"SplitKeyboardShortcut","value":true},{"key":"SplitTransactionAutoAdjust","value":true},{"key":"SquareNegativeMode","value":false},{"key":"StealingFromFuture","value":true},{"key":"SwapClearedFlagged","value":false},{"key":"TargetBalanceWarning","value":true},{"key":"ToBeBudgetedWarning","value":true},{"key":"ToggleMasterCategories","value":true},{"key":"ToggleSplits","value":false},{"key":"ToggleTransactionFilters","value":"1"},{"key":"ToolkitReports","value":true},{"key":"TransactionGridFeatures","value":true},{"key":"ViewZeroAsEmpty","value":true},{"key":"goalIndicator","value":true},{"key":"highlightNegativesNegative","value":true},{"key":"l10n","value":"0"},{"key":"pacing","value":"0"},{"key":"popupCalculator","value":true},{"key":"reports","value":true}]

Steps to Reproduce the Behavior

Toolkit Reports
Income Breakdown
Filter: Last month

Expected Behavior

Budget totals that mirror amounts paid in the month of July 2019
Actual Behavior

An increased budget line is showing as an expense and causing a ripple effect of incorrect numbers in the report. Specifically, we had a car insurance claim payout last month. Rather than putting it in TBB, I inflowed it directly to a category. That inflowed more money into our Vehicle Maintenance and Repair category than was spent (pic 1). The activity in that category for July is a positive number ($1,036.53). In the Income breakdown, the data to the right showing expenses for each category show this amount as an expense (pic 2). This causes my True Expenses Category Group (pic 2) and the Budget (pic 3) to display a significant error of twice that increase. The graph looks like we spent $2,073.06 more than we did (pic 4) and shows an overdraft when we actually had a net gain that month (pic 5).

Console Error
ynab-toolkit.js:4096 Error:  attribute height: A negative value is not valid. ("-0.35470351298650865")
^This error appears in the window about 60 times with different values in the parentheses.

Damn, I'm sorry about that.
I figured out why it happens, and can remove it as a faulty expense. But I'm not really sure how to show that income visually

Ok so I quickly tried out my 2 ideas:

All positive categories grouped and added as one single income source

Every positive category added as separate income sources

@joshmadewell any thoughts on this?

For what it's worth, I like option 1
Get Outlook for Androidhttps://aka.ms/ghei36

From: Maarten Schroeven<EMAIL_ADDRESS>Sent: Wednesday, August 14, 2019 4:41:50 AM
To: toolkit-for-ynab/toolkit-for-ynab<EMAIL_ADDRESS>Cc: ejn284<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [toolkit-for-ynab/toolkit-for-ynab] Income Breakdown showing erroneous expense (#1622)
Ok so I quickly tried out my 2 ideas:

All positive categories grouped and added as one single income source

[Screenshot 2019-08-14 at 11 27 54]https://user-images.githubusercontent.com/10436899/63011287-4db44400-be88-11e9-9b82-1efe53f9a6f4.png

Every positive category added as separate income sources

[Screenshot 2019-08-14 at 11 38 21]https://user-images.githubusercontent.com/10436899/63011362-6f153000-be88-11e9-99c0-752b83ba8045.png
@joshmadewellhttps://github.com/joshmadewell any thoughts on this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/toolkit-for-ynab/toolkit-for-ynab/issues/1622?email_source=notifications&email_token=AKZHK247CYXCF2SCJJYLLWDQEPHN5A5CNFSM4IK2XTCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4IIUEA#issuecomment-521177616, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKZHK25M4BELREXKL6DOHF3QEPHN5ANCNFSM4IK2XTCA.

My guess is that it'll be somewhat rare for a category to be positive so it may be better to be explicit about where the money is coming from in the report. I'd go with the first implementation @Sonaryr
@ejn284 Does that make sense to you? I'm really fine with either approach.

That makes sense. Up to you.
Get Outlook for Androidhttps://aka.ms/ghei36

From: Josh Madewell<EMAIL_ADDRESS>Sent: Wednesday, August 14, 2019 11:20:56 AM
To: toolkit-for-ynab/toolkit-for-ynab<EMAIL_ADDRESS>Cc: ejn284<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [toolkit-for-ynab/toolkit-for-ynab] Income Breakdown showing erroneous expense (#1622)
My guess is that it'll be somewhat rare for a category to be positive so it may be better to be explicit about where the money is coming from in the report. I'd go with the first implementation @Sonaryrhttps://github.com/Sonaryr
@ejn284https://github.com/ejn284 Does that make sense to you? I'm really fine with either approach.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/toolkit-for-ynab/toolkit-for-ynab/issues/1622?email_source=notifications&email_token=AKZHK2444Y2NWZKWYGN4RDTQEQWGRA5CNFSM4IK2XTCKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4JKP5A#issuecomment-521316340, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKZHK26TAXIE7YI2K2PKX2LQEQWGRANCNFSM4IK2XTCA.

This is the first time I've been aware of an upcoming update. How often does one get pushed?

There is no set schedule for pushing a new release. It's mostly as needed and when our build manager has time to do a release.

Pull request created

Any movement on this? Thanks.

Hey @ejn284 the pull request is open, so just waiting on a merge and release for this one

Not sure if this should be a separate issue, or a continuation of this one...
I would really like to see Option #2, where each positive category is added as a separate income source. Perhaps this could be a checkbox option?
In my case, a common positive category is "House Expenses via [my partner]". This is a contribution towards costs that should show separately from other occasionally positive categories such as Tax Refunds, or Insurance Claims when trying to understand the flow of money.

I just realized that my comment said "we should be explicit" and then I followed up by suggesting we go with the generic approach...
I'm not sure what I was thinking but I definitely think we should have implemented the "individual sources".
I'm going to get a release out soon with @Sonaryr's PR in it but hopefully in the near future we can get it changed over to be split up. Sorry about that @ZoneMR  haha

Hey @ejn284 the fix for this should be in our current release! If you notice the issue still exists and you're definitely running the newest version of the toolkit, please reopen! Thanks!
Please note, all browser can take up to an hour to provide updates to all users. You can force an update if it's available for you by going to chrome://extensions and clicking the "Update" button. Firefox users can go to about:addons, click the setting cog, and click "Check for updates...".

@ZoneMR just to let you know I opened a pull request with option 2 as the default option to split them (with an option to regroup them) see #1669

Brilliant - thank you :)


fix(reactivity): Array.prototype.push causes infinite recursion

Calling Array.prototype.push, which gets .length and sets values at the same time, may lead to an infinite recursion
for example
  const a = reactive([])

  watchEffect(() => {
      a.push(1)
  })

  watchEffect(() => {
      a.push(1)
  })

This is fixed by 3810de7d

@yyx990803 This fix has nothing to do with https://github.com/vuejs/vue-next/commit/3810de7d6bd0044177f043285228c2e988093883

I've pull the latest code and run the test
  it('should avoid infinite recursive loops when use Array.prototype.push', () => {
    const arr = reactive<number[]>([])

    const counterSpy1 = jest.fn(() => arr.push(1))
    const counterSpy2 = jest.fn(() => arr.push(2))
    effect(counterSpy1)
    effect(counterSpy2)
    expect(arr.length).toBe(2)
    expect(counterSpy1).toHaveBeenCalledTimes(1)
    arr.push(3)
    expect(arr.length).toBe(3)
    expect(counterSpy1).toHaveBeenCalledTimes(1)
  })

This recursion is not due to the self-calls of the effect, but that push changes length while it depends on length.

@unbyte If so, unshift should also be included.

@dsonet and pop and shift, they all cause infinite recursion cuz they all depend on .length


Fixed bug with duplicate categories

@hellozjf Could you explain why delete data.categories?
data.categories is parsed from filesystem's directory, like javascript from '.../javascript/doc.md'.
This is an important feature of this plugin


State plugin delay

I think there is a problem (or maybe a feature request) concerning the state plugin. I have explained it here (there is also an example showing the problem).
Can you have a look at it and tell us what you think about it?

Sorry, I do not use angular, so I really can't help you, I can only guarantee that if you load data properly (in one of the many ways described in the docs) the state plugin will work just fine.
Let me know if I can help in any way. If you have spotted a problem - please provide steps to reproduce or a demo, but without an angular wrapper.
Best regards,
Ivan

@vakata The problem is that the data is added way after the jstree is initiated. By the time the data gets added, state plugin has already kicked in and restored the state (unsuccessfully because there are no nodes).
Maybe a good solution would be to allow passing a state argument to restore_state. Then we could catch the state with state.filter() and restore it after the data is loaded manually with restore_state(state). What do you think?

The question is why do you add data after the ready event? And how do you add that data?

@vakata Nodes are added with create_node, and I'm adding them way after the jstree is initialized because the data that should be loaded depends on user select (dropdown) (note that even nothing is selected, the tree should be visible).

I am sure there are way more elegant solutions to this (including refreshing the tree, with the needed data from the dropdown, and even using different state keys).
Anyway, the state plugin has nothing to do with create_node - that is by design and it will not change.
Aside from that - create_node should not be used to populate the tree - it is a run-time method so that the end user can modify the structure, and as such is has limitations. Using it to populate the tree will be very slow, it will also prevent any plugin that reacts on ready from doing its job (just like in your case with state).
Your best bet is to start loading your data properly and not using create_node.
Best regards,
Ivan

@vakata So... let me see if I understand it correctly.

Create the (empty) tree.
Fill core.data with nodes, based on user selection
Call refresh().

Is that how I should do it? Also, if I do it that way, will the state plugin work? I mean, will it restore my open nodes after calling refresh()?

It all depends on your requirements - you can either:

set core.data to a function, in that function read the current user selection and return nodes accordingly, and when the selection is changed - call .refresh
destroy the tree each time selection is changed and create it anew, and do not forget to set a proper state.key for each instance - so that the correct state will be restored and it will not be overwritten
Same as 2) but with a single state key, and the initial (empty) tree should not have the state plugin loaded so that state is not lost.

Personally 2 or 3 are easier and the choice between them depends on your needs - I can not tell you which approach is better for your use case without diving into the specifics of your application, which I simply should not and can not do.
Best regards,
Ivan

IMHO all your suggestions don't make any sense from performance or complexity point of view.

A function inside jstree's config that will listen for events on the DOM and do ajax calls and parsing and refreshing? Doesn't sound like a thing one would put in it's config. Really, think about it.

Why would I destroy and recreate my entire tree if the only thing I want to do is to restore a state?! Something as simple as "look, I had nodes 1, 5 and 9 opened; open them". Instead, this is going to destroy the entire tree, DOM operations, data parsing, nodes creation, more DOM operations, triggering all sort of events. Completely wasting all type of resources and time.

Same as point 2.

You NACKed my plugin because it had a couple of calls to jQuery and now you're suggesting me to destroy and recreate the entire tree or write complex functions to do all sort of thing instead of just making a simple change in the state plugin to allow restoring a state from an (optional!) parameter? As I said,  doesn't make much sense.
It would be much easier if jstree let me save the state on load (possible already, making a copy of the state with the filter callback from the state plugin) and let me apply it later, on demand. @vakata

Hi,
You totally misunderstood 1) - nothing to do with a function listening for DOM events. I only suggested 2) and 3) because I was under the impression you were loading a totally different tree, and not storing different states of the same tree - be more clear next time.
jsTree already does what you are suggesting, and the jQuery calls in your plugin (I did not even know it was you) have nothing to do with the current issue - if you want me to go into detail - I will - just ask.
As for your issue - start describing the problem more accurately - you did not let me know what your problem is, just what you think a solution should look like, and it was a bad idea. This time - please explain what you need, not what you think the fix should be.
Best regards,
Ivan

Judging on your comments - here is what you probably need in a single line of code using set_state, you do not even need the state plugin:
http://jsfiddle.net/DGAF4/429/
As you may notice I am manually creating the nodes, then applying a state that will reveal them. I guess that is what you need. You can collect the current state at any given moment using get_state and do whatever you need with it - store it for later use, etc. Once again - set_state and get_state are core functions, all plugins respect those and they work without the need of the state plugin.
The state plugin simply calls get_state every time a node is opened or selected, stores the result in localStorage and then calls set_state the next time the same tree fires a ready.jstree event.
Here is everything state related:
http://www.jstree.com/api/#/?q=state
If you need something else - let me know, and provided a detailed description.
Now, as for your plugin:

I can not just pull any plugin to the core, because of two reasons

the plugin needs to be frequently requested, if it is not - that will only make the jstree download larger, and most users will not use a custom build
the plugin I pull in will then be my responsibility - I should support it and make sure there is no conflict with any other plugin, and that it works in all possible scenarios that jstree users are used to (tens of thousands of nodes, etc).

the jQuery calls are a problem, because they are very expensive, that is why the _redraw_node function is written in vanillaJS, if you are interested I can show you performance tests I did.
I was and am really happy you decided to make that plugin - third party plugins are great and I am really excited when a new one emerges. If I was too harsh - I apologize, I just wanted to make sure your plugin will work properly in all jstree use cases / configs / etc.

That being said - I do not appreciate your tone. As grateful as I am for any bug reports and the plugin, if you do not like the way I am developing jstree there is nothing I can do about it, every day I deal with hundreds of different use cases, help debug various systems, etc, and I do it all for free. There is a limit to what I can do, especially when I am not given enough information.
Please let me know if the above solution is what you needed - if not - please clarify so that I can help you further.
Best regards,
Ivan

A few hours after posting I kind of worked out the save/restore thing, but thank you for making that jsfiddle!
About the plugin, the way I see it, once the plugin reaches certain maturity level, it doesn't need any further maintenance (try to search the last time you had to patch one of the core plugins). Anyways, I won't push that subject any further, the plugin can live in a separate repository too, no harm.
And yes, you do have a point, my tone was inappropriate, I'm sorry about that.
One last thing (I'm not sure if I should open yet another bug report for this one). It would be nice to have a scheme of the life-cycle of the events. Which one is triggered before/after which one.
For example, load_node, redraw, refresh and create_node. What is the order of those events if I add a tree using create_node?
Does the refresh event gets triggered when creating a node or only after calling refresh()?
Does the redraw event gets called after each call to create_node, or are you using some sort of debounce (underscore) to trigger that event only once N ms after the last call of create_node?

That is truly my bad - the documentation is far from perfect - there is no clear order of events that you can expect, etc. I will try to improve on this in the future. I view the docs as a constant work in progress. I will dedicate some time especially for the docs in the near future.
I do not agree about the maturity level - yes, at some point it is mostly minor tweaks, but still - there is always something happening behind the scenes - I added a few lines to the core just a day ago - it is easy to see from the commit log. I hope that you can understand why I am reluctant to adopt plugins. As I said in my initial comment about the plugin - I will adopt it as soon as it becomes frequently requested. It is pretty robust now, and it also seems quite finished - with the repo and npm package. I do not think it is a bad idea to keep it as a separate plugin for the time being.
As for the events (just a few lines until I get the time to update the docs):

using create_node() will only trigger create_node.jstree and model.jstree as mentioned in the "Triggers" section of the function:
http://www.jstree.com/api/#/?q=create_node&f=create_node([obj, node, pos, callback, is_loaded])
refresh.jstree will only be triggered when a refresh() call is made
redraw.jstree will not fire after create_node() - or at least - you should not depend on it. The reason behind this is that create_node() internally calls redraw_node(), which bypasses the _redraw() function. The original idea was to collect nodes that need to be redrawn and then debounce a call to _redraw() but that proved to add way too much complexity, so it is not used everywhere. And there is no separate redraw_node.jstree event because that would be way too expensive - it brings a tree with as little as a few hundred nodes to a halt, as redraw_node() is called very often.

Best regards,
Ivan

Hi Ivan,
I am pretty new to web and currently using jstree and I load/build my tree nodes using a function like "data": function (obj, cb) {cb.call(this, getdata));. I have a problem and think I am not doing it correctly. When I add or remove a node from the tree the state plugin doesn't save whether a node has been added or removed. But once I check the check box or expand a node then state is saved in the 'checkbox' and 'core : open' array on my local storage. How can I clear the node values from those arrays if I remove a node . I read earlier in this discussion to refresh the tree after removing or adding a node but it doesn't work.
Thanks
Ash