NVD API update is failing

Describe the bug
Running dependency-check --enableExperimental --nvdApiKey <my-nvd-api-key> --out ~/file-dependency-check.html --scan Package.resolved on 9.0.5 fails during the records update
Version of dependency-check used
The problem occurs using version 9.0.5 of the CLI
Log file
gist
To Reproduce
Steps to reproduce the behavior:
Run the dependency check
Expected behavior
The update should be successful, and the dependency check report should be generated.
Additional context
This is running on a Circleci job, I'm downloading the latest version of the dependency check. After the update it started failing.

Update: I tested running the command without the nvd API key and it worked. Maybe it's a problem with the key, Are there any know issues with it?

same here, with nvd API key

without nvd API key works, but duration is horrible

I request for new nvd api key and now it works

If you are using an NVD API key and you get an immediate 403 - it is likely your API Key is not valid.
See https://github.com/jeremylong/Open-Vulnerability-Project/tree/main/vulnz#api-key-is-used-and-a-403-or-404-error-occurs

Weirdly my key works when I run the command in my local machine. I even purged the nvd file to check. The issue only happens when I run it on CircleCI with the API key. 🤦

@jeremylong
I've set --nvdApiDelay 8000 which according to documentation is the default value for when we don't have an API key and it worked, then I tried with 2500 and it also worked. When I set it to 2000 it didn't. I don't know why it happens only in CircleCI but it does.
The min value I was able to use consistently is 2500 milliseconds. That's good enough for me so I will take it. 🤷♂
I was able to make it work with 2050, but only the first time, the second run I've got the same issue.
Is it possible that the fact that CircleCI doesn't store the NVD file and it's downloading the entire thing every time (sometimes in a short period since I'm testing the workflow) is messing things up? I plan to try storing it in cache or something, but I didn't yet.

I would highly recommend reading https://jeremylong.github.io/DependencyCheck/data/index.html - specifically "The NVD Database" section. It would be ideal if you persisted the data directory between builds.

Weirdly my key works when I run the command in my local machine. I even purged the nvd file to check. The issue only happens when I run it on CircleCI with the API key. 🤦

Have the same issue: API key works locally but on GitHub Actions the NVD update is interrupted by an exception:
[INFO] Downloaded 90,000/233,564 (39%)
[ERROR] Error updating the NVD Data
org.owasp.dependencycheck.data.update.exception.UpdateException: Error updating the NVD Data
...
Caused by: io.github.jeremylong.openvulnerability.client.nvd.NvdApiException: NVD Returned Status Code: 403`.

Detailed maven log excerpt:
2023-12-18T04:40:04.2168058Z [INFO] Checking for updates
2023-12-18T04:40:06.0015022Z [INFO] NVD API has 233,564 records in this update
2023-12-18T04:40:12.4805299Z [INFO] Downloaded 10,000/233,564 (4%)
2023-12-18T04:40:21.0776143Z [INFO] Downloaded 20,000/233,564 (9%)
2023-12-18T04:40:26.4392808Z [INFO] Downloaded 30,000/233,564 (13%)
2023-12-18T04:40:31.0227923Z [INFO] Downloaded 40,000/233,564 (17%)
2023-12-18T04:40:35.7817056Z [INFO] Downloaded 50,000/233,564 (21%)
2023-12-18T04:40:41.4263361Z [INFO] Downloaded 60,000/233,564 (26%)
2023-12-18T04:40:46.7154836Z [INFO] Downloaded 70,000/233,564 (30%)
2023-12-18T04:40:50.8825364Z [INFO] Downloaded 80,000/233,564 (34%)
2023-12-18T04:40:50.8826214Z [INFO] Downloaded 90,000/233,564 (39%)
2023-12-18T04:40:57.1447264Z [ERROR] Error updating the NVD Data
2023-12-18T04:40:57.1559725Z org.owasp.dependencycheck.data.update.exception.UpdateException: Error updating the NVD Data
2023-12-18T04:40:57.1571805Z     at org.owasp.dependencycheck.data.update.NvdApiDataSource.processApi (NvdApiDataSource.java:375)
2023-12-18T04:40:57.1574019Z     at org.owasp.dependencycheck.data.update.NvdApiDataSource.update (NvdApiDataSource.java:115)
2023-12-18T04:40:57.1575563Z     at org.owasp.dependencycheck.Engine.doUpdates (Engine.java:906)
2023-12-18T04:40:57.1576943Z     at org.owasp.dependencycheck.Engine.initializeAndUpdateDatabase (Engine.java:711)
2023-12-18T04:40:57.1578431Z     at org.owasp.dependencycheck.Engine.analyzeDependencies (Engine.java:637)
2023-12-18T04:40:57.1580127Z     at org.owasp.dependencycheck.maven.BaseDependencyCheckMojo.runCheck (BaseDependencyCheckMojo.java:1943)
2023-12-18T04:40:57.1582075Z     at org.owasp.dependencycheck.maven.BaseDependencyCheckMojo.execute (BaseDependencyCheckMojo.java:1126)
2023-12-18T04:40:57.1584303Z     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126)
2023-12-18T04:40:57.1587704Z     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:342)
2023-12-18T04:40:57.1589515Z     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:330)
2023-12-18T04:40:57.1591232Z     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213)
2023-12-18T04:40:57.1592922Z     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:175)
2023-12-18T04:40:57.1594928Z     at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:76)
2023-12-18T04:40:57.1596603Z     at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:163)
2023-12-18T04:40:57.1598475Z     at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
2023-12-18T04:40:57.1600380Z     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:160)
2023-12-18T04:40:57.1602375Z     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
2023-12-18T04:40:57.1604867Z     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
2023-12-18T04:40:57.1607724Z     at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
2023-12-18T04:40:57.1609961Z     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
2023-12-18T04:40:57.1611578Z     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
2023-12-18T04:40:57.1612909Z     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
2023-12-18T04:40:57.1614194Z     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
2023-12-18T04:40:57.1615714Z     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:910)
2023-12-18T04:40:57.1616923Z     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
2023-12-18T04:40:57.1618076Z     at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
2023-12-18T04:40:57.1619632Z     at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:103)
2023-12-18T04:40:57.1621150Z     at java.lang.reflect.Method.invoke (Method.java:580)
2023-12-18T04:40:57.1622581Z     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:283)
2023-12-18T04:40:57.1624278Z     at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:226)
2023-12-18T04:40:57.1626359Z     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:407)
2023-12-18T04:40:57.1628282Z     at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:348)
2023-12-18T04:40:57.1629982Z     at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:103)
2023-12-18T04:40:57.1631352Z     at java.lang.reflect.Method.invoke (Method.java:580)
2023-12-18T04:40:57.1632618Z     at org.apache.maven.wrapper.BootstrapMainStarter.start (BootstrapMainStarter.java:52)
2023-12-18T04:40:57.1634147Z     at org.apache.maven.wrapper.WrapperExecutor.execute (WrapperExecutor.java:161)
2023-12-18T04:40:57.1635657Z     at org.apache.maven.wrapper.MavenWrapperMain.main (MavenWrapperMain.java:73)
2023-12-18T04:40:57.1637386Z Caused by: io.github.jeremylong.openvulnerability.client.nvd.NvdApiException: NVD Returned Status Code: 403
2023-12-18T04:40:57.1639316Z     at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next (NvdCveClient.java:357)
2023-12-18T04:40:57.1641216Z     at org.owasp.dependencycheck.data.update.NvdApiDataSource.processApi (NvdApiDataSource.java:348)
2023-12-18T04:40:57.1643073Z     at org.owasp.dependencycheck.data.update.NvdApiDataSource.update (NvdApiDataSource.java:115)
2023-12-18T04:40:57.1644534Z     at org.owasp.dependencycheck.Engine.doUpdates (Engine.java:906)
2023-12-18T04:40:57.1645969Z     at org.owasp.dependencycheck.Engine.initializeAndUpdateDatabase (Engine.java:711)
2023-12-18T04:40:57.1647462Z     at org.owasp.dependencycheck.Engine.analyzeDependencies (Engine.java:637)
2023-12-18T04:40:57.1701778Z     at org.owasp.dependencycheck.maven.BaseDependencyCheckMojo.runCheck (BaseDependencyCheckMojo.java:1943)
2023-12-18T04:40:57.1704162Z     at org.owasp.dependencycheck.maven.BaseDependencyCheckMojo.execute (BaseDependencyCheckMojo.java:1126)
2023-12-18T04:40:57.1706263Z     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126)
2023-12-18T04:40:57.1708388Z     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:342)
2023-12-18T04:40:57.1710139Z     at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:330)
2023-12-18T04:40:57.1711794Z     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213)
2023-12-18T04:40:57.1713411Z     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:175)
2023-12-18T04:40:57.1715056Z     at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:76)
2023-12-18T04:40:57.1716755Z     at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:163)
2023-12-18T04:40:57.1718568Z     at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
2023-12-18T04:40:57.1720530Z     at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:160)
2023-12-18T04:40:57.1722322Z     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
2023-12-18T04:40:57.1724646Z     at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
2023-12-18T04:40:57.1727014Z     at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
2023-12-18T04:40:57.1729180Z     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
2023-12-18T04:40:57.1730753Z     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
2023-12-18T04:40:57.1732009Z     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
2023-12-18T04:40:57.1733240Z     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
2023-12-18T04:40:57.1734404Z     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:910)
2023-12-18T04:40:57.1735532Z     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
2023-12-18T04:40:57.1736632Z     at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
2023-12-18T04:40:57.1738209Z     at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:103)
2023-12-18T04:40:57.1739616Z     at java.lang.reflect.Method.invoke (Method.java:580)
2023-12-18T04:40:57.1740977Z     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:283)
2023-12-18T04:40:57.1742632Z     at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:226)
2023-12-18T04:40:57.1744400Z     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:407)
2023-12-18T04:40:57.1745917Z     at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:348)
2023-12-18T04:40:57.1747730Z     at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:103)
2023-12-18T04:40:57.1749153Z     at java.lang.reflect.Method.invoke (Method.java:580)
2023-12-18T04:40:57.1750476Z     at org.apache.maven.wrapper.BootstrapMainStarter.start (BootstrapMainStarter.java:52)
2023-12-18T04:40:57.1752050Z     at org.apache.maven.wrapper.WrapperExecutor.execute (WrapperExecutor.java:161)
2023-12-18T04:40:57.1753548Z     at org.apache.maven.wrapper.MavenWrapperMain.main (MavenWrapperMain.java:73)
2023-12-18T04:40:57.1755138Z [ERROR] Failed to process CVE-2011-1485
2023-12-18T04:40:57.1756498Z org.owasp.dependencycheck.data.nvdcve.DatabaseException: Error updating 'CVE-2011-1485'
2023-12-18T04:40:57.1758196Z     at org.owasp.dependencycheck.data.nvdcve.CveDB.updateVulnerability (CveDB.java:877)
2023-12-18T04:40:57.1760006Z     at org.owasp.dependencycheck.data.update.nvd.api.NvdApiProcessor.call (NvdApiProcessor.java:98)
2023-12-18T04:40:57.1761924Z     at org.owasp.dependencycheck.data.update.nvd.api.NvdApiProcessor.call (NvdApiProcessor.java:33)
2023-12-18T04:40:57.1763432Z     at java.util.concurrent.FutureTask.run (FutureTask.java:317)
2023-12-18T04:40:57.1764799Z     at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1144)
2023-12-18T04:40:57.1766474Z     at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:642)
2023-12-18T04:40:57.1767836Z     at java.lang.Thread.run (Thread.java:1583)
2023-12-18T04:40:57.1770011Z Caused by: org.h2.jdbc.JdbcBatchUpdateException: IO Exception: "C:/Users/runneradmin/.m2/repository/org/owasp/dependency-check-data/9.0/odc.mv.db"; SQL statement:
2023-12-18T04:40:57.1773106Z INSERT INTO cpeEntry (part, vendor, product, version, update_version, edition, lang, sw_edition, target_sw, target_hw, other, ecosystem) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [90028-214]
2023-12-18T04:40:57.1775415Z     at org.h2.jdbc.JdbcPreparedStatement.executeBatch (JdbcPreparedStatement.java:1269)
2023-12-18T04:40:57.1777170Z     at org.apache.commons.dbcp2.DelegatingStatement.executeBatch (DelegatingStatement.java:230)
2023-12-18T04:40:57.1788683Z     at org.apache.commons.dbcp2.DelegatingStatement.executeBatch (DelegatingStatement.java:230)
2023-12-18T04:40:57.1790451Z     at org.owasp.dependencycheck.data.nvdcve.CveDB.executeBatch (CveDB.java:1381)
2023-12-18T04:40:57.1792269Z     at org.owasp.dependencycheck.data.nvdcve.CveDB.updateVulnerabilityInsertSoftware (CveDB.java:1221)
2023-12-18T04:40:57.1794140Z     at org.owasp.dependencycheck.data.nvdcve.CveDB.updateVulnerability (CveDB.java:871)
2023-12-18T04:40:57.1795970Z     at org.owasp.dependencycheck.data.update.nvd.api.NvdApiProcessor.call (NvdApiProcessor.java:98)
2023-12-18T04:40:57.1797869Z     at org.owasp.dependencycheck.data.update.nvd.api.NvdApiProcessor.call (NvdApiProcessor.java:33)
2023-12-18T04:40:57.1799387Z     at java.util.concurrent.FutureTask.run (FutureTask.java:317)
2023-12-18T04:40:57.1800747Z     at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1144)
2023-12-18T04:40:57.1802310Z     at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:642)
2023-12-18T04:40:57.1803491Z     at java.lang.Thread.run (Thread.java:1583)
2023-12-18T04:40:57.1804522Z [ERROR] Failed to process CVE-2011-1486
2023-12-18T04:40:57.1807897Z org.owasp.dependencycheck.data.nvdcve.DatabaseException: Unable to retrieve id for new vulnerability for 'CVE-2011-1486'

do you have more than one repository using the same key? That can cause you to hit the rate limit. Also, if you are using GH Actions I'd highly recommend caching the data directory. here is an example using the maven plugin: https://jeremylong.github.io/DependencyCheck/data/cache-action.html
If you are using something else you can likely just change the paths that are being cached and it should work well.

I'm getting a 404.
Caused by: io.github.jeremylong.openvulnerability.client.nvd.NvdApiException: NVD Returned Status Code: 404
Any ideas?

Please see the enhanced error reporting that will be included in 9.0.7:
https://github.com/jeremylong/DependencyCheck/blob/3e6ee91c9377ad8995763f3ea65f0f7b3a637fd9/core/src/main/java/org/owasp/dependencycheck/data/update/NvdApiDataSource.java#L378-L385
The URLs are:

403/404 errors with an API Key: https://github.com/jeremylong/Open-Vulnerability-Project/tree/main/vulnz#api-key-is-used-and-a-403-or-404-error-occurs
No API Key: https://github.com/jeremylong/DependencyCheck?tab=readme-ov-file#nvd-api-key-highly-recommended

Curl works w/ a new key, but I can't seem to get the key passed in to the gradle tasks.
Tried :

./gradlew dependencyCheckAnalyze -DnvdApiKey=<redacted>
./gradlew dependencyCheckAnalyze -Dnvd.ApiKey=<redacted>

and in build.gradle.kts
dependencyCheck {
    nvd.apiKey = System.getenv("NVD_API_KEY")
}

Is there something in the response body that could/should be logged to help find out what's going on?

I haven't had an issue. I've requested a single API key, I've been using it for a while. It was even temporarily used in GH actions during the build/test. I've never had to request a new key. ¯\_(ツ)_/¯

Curl works w/ a new key, but I can't seem to get the key passed in to the gradle tasks.
Tried :
* `./gradlew dependencyCheckAnalyze -DnvdApiKey=<redacted>`

* `./gradlew dependencyCheckAnalyze -Dnvd.ApiKey=<redacted>`

and in build.gradle.kts
dependencyCheck {
    nvd.apiKey = System.getenv("NVD_API_KEY")
}

edit: now curl is failing w/ the same api key message: Invalid apiKey
edit2: got another key, curl is failing w/ that one too. Just feels like they were simply not ready for this change to go live.

FWIW: You're passing the key as a system property. So you might want to try System.getProperty("nvdApiKey")

./gradlew dependencyCheckAnalyze -DnvdApiKey=<redacted>
dependencyCheck {
    nvd.apiKey = System.getProperty("nvdApiKey")
}

Setting the delay (2500) and retry (10) parameters worked for me. I also had to bump up the JVM memory for Gradle. Got an OOM w/ the default memory settings.

I obtained the api key and provided an api key in my pom but still getting the below error
15:44:42 [INFO] Building **** - Parent POMs 3-0-SNAPSHOT [1/21]
15:44:42 [INFO] --------------------------------[ pom ]---------------------------------
15:44:42 [INFO]
15:44:42 [INFO] --- dependency-check-maven:9.0.2:purge (default-cli) @ parent-poms ---
15:44:44 [INFO] Database file purged; local copy of the NVD has been removed
15:44:44 [INFO] Cache directory purged
15:44:44 [INFO]
15:44:44 [INFO] --- dependency-check-maven:9.0.2:aggregate (default-cli) @ parent-poms ---
15:44:45 [INFO] Checking for updates
15:44:45 [WARNING] An NVD API Key was not provided - it is highly recommended to use an NVD API key as the update can take a VERY long time without an API Key
15:47:06 [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
15:49:13 [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
15:51:19 [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
I had earlier tried with version 9.0.7 and was getting this error
14:33:37 [INFO] --- dependency-check-maven:9.0.7:purge (default-cli) @ parent-poms ---
14:33:42 [INFO] Unable to purge database; the database file does not exist: /apps/jenkins-core-agent/.m2/repository-executor-3/org/owasp/dependency-check-utils/9.0.7/../../dependency-check-data/9.0/odc.mv.db
14:33:42 [INFO]
14:33:42 [INFO] --- dependency-check-maven:9.0.7:aggregate (default-cli) @ parent-poms ---
14:33:43 [INFO] Checking for updates
14:33:43 [WARNING] An NVD API Key was not provided - it is highly recommended to use an NVD API key as the update can take a VERY long time without an API Key
14:44:51 [WARNING] NVD API request failures are occurring; retrying request for the 5 time
14:46:58 [WARNING] NVD API request failures are occurring; retrying request for the 6 time
14:49:04 [WARNING] NVD API request failures are occurring; retrying request for the 7 time
14:51:11 [WARNING] NVD API request failures are occurring; retrying request for the 8 time
14:53:32 [WARNING] NVD API request failures are occurring; retrying request for the 9 time
14:55:39 [WARNING] NVD API request failures are occurring; retrying request for the 10 time
14:57:45 [WARNING] NVD API request failures are occurring; retrying request for the 11 time
15:08:39 [WARNING] NVD API request failures are occurring; retrying request for the 5 time
15:11:01 [WARNING] NVD API request failures are occurring; retrying request for the 6 time
15:13:07 [WARNING] NVD API request failures are occurring; retrying request for the 7 time
15:15:13 [WARNING] NVD API request failures are occurring; retrying request for the 8 time
I read a comment on another this thread that said 9.0.2 worked but it doesn't seem to be working for me. Is the issue fixed please @jeremylong @stevespringett ? Thank you

Have you considered using the latest version?

As mentioned in the other issue you posted the same comment on it looks like the API key is not picked up by DC.
 [WARNING] An NVD API Key was not provided
Also I think the logs on the bottom indicate the job is progressing, but with some retries.

I have the plugin as well as the api key specified. I tested 9.0.7 just moments ago before reading these comments here and testing with 9.02. My previous version of 8.4.2 worked perfectly no issues and i didnt even need to use an api key for this version

org.owasp
dependency-check-maven
9.0.2

HTML,XML
86xxx-xxxxxd90
https://artifactoryurl/artifactory/nvd-cve/feeds/json/cve/1.1/nvdcve-1.1-modified.json.gz
https://artifactoryurl/artifactory/nvd-cve/feeds/json/cve/1.1/nvdcve-1.1-%d.json.gz
https://artifactoryurl/artifactory/cisa-files/sites/default/files/feeds/known_exploited_vulnerabilities.json
${project.build.directory}
false

false
false
false

Right now its been stuck at this stage giving the same output for the last 2 plus hours
15:44:44  [INFO] --- dependency-check-maven:9.0.2:aggregate (default-cli) @ parent-poms ---
15:44:45  [INFO] Checking for updates
15:44:45  [WARNING] An NVD API Key was not provided - it is highly recommended to use an NVD API key as the update can take a VERY long time without an API Key
15:47:06  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
15:49:13  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
15:51:19  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
15:53:41  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
15:55:47  [WARNING] NVD API request failures are occurring; retrying request for the 5 time
15:55:47  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
15:57:54  [WARNING] NVD API request failures are occurring; retrying request for the 6 time
15:57:54  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:00:17  [WARNING] NVD API request failures are occurring; retrying request for the 7 time
16:00:17  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:02:23  [WARNING] NVD API request failures are occurring; retrying request for the 8 time
16:02:23  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:04:30  [WARNING] NVD API request failures are occurring; retrying request for the 9 time
16:04:30  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:06:37  [WARNING] NVD API request failures are occurring; retrying request for the 10 time
16:06:37  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:08:58  [WARNING] NVD API request failures are occurring; retrying request for the 11 time
16:11:05  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:13:11  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:15:33  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:17:41  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:19:48  [WARNING] NVD API request failures are occurring; retrying request for the 5 time
16:19:48  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:21:54  [WARNING] NVD API request failures are occurring; retrying request for the 6 time
16:21:54  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:24:16  [WARNING] NVD API request failures are occurring; retrying request for the 7 time
16:24:16  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:26:22  [WARNING] NVD API request failures are occurring; retrying request for the 8 time
16:26:22  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:28:29  [WARNING] NVD API request failures are occurring; retrying request for the 9 time
16:28:29  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:30:50  [WARNING] NVD API request failures are occurring; retrying request for the 10 time
16:30:50  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:32:57  [WARNING] NVD API request failures are occurring; retrying request for the 11 time
16:35:03  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:37:25  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:39:31  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:41:41  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:43:47  [WARNING] NVD API request failures are occurring; retrying request for the 5 time
16:43:47  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:46:09  [WARNING] NVD API request failures are occurring; retrying request for the 6 time
16:46:09  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:48:17  [WARNING] NVD API request failures are occurring; retrying request for the 7 time
16:48:17  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:50:23  [WARNING] NVD API request failures are occurring; retrying request for the 8 time
16:50:23  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:52:30  [WARNING] NVD API request failures are occurring; retrying request for the 9 time
16:52:30  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:54:52  [WARNING] NVD API request failures are occurring; retrying request for the 10 time
16:54:52  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
16:56:59  [WARNING] NVD API request failures are occurring; retrying request for the 11 time
16:59:05  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:01:26  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:03:33  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:05:40  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:07:46  [WARNING] NVD API request failures are occurring; retrying request for the 5 time
17:07:46  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:10:08  [WARNING] NVD API request failures are occurring; retrying request for the 6 time
17:10:08  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:12:15  [WARNING] NVD API request failures are occurring; retrying request for the 7 time
17:12:15  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:14:21  [WARNING] NVD API request failures are occurring; retrying request for the 8 time
17:14:21  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:16:43  [WARNING] NVD API request failures are occurring; retrying request for the 9 time
17:16:43  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:18:50  [WARNING] NVD API request failures are occurring; retrying request for the 10 time
17:18:50  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:20:57  [WARNING] NVD API request failures are occurring; retrying request for the 11 time
17:23:18  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:25:25  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:27:32  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:29:38  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:32:00  [WARNING] NVD API request failures are occurring; retrying request for the 5 time
17:32:00  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:34:06  [WARNING] NVD API request failures are occurring; retrying request for the 6 time
17:34:06  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:36:13  [WARNING] NVD API request failures are occurring; retrying request for the 7 time
17:36:13  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:38:35  [WARNING] NVD API request failures are occurring; retrying request for the 8 time
17:38:35  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:40:41  [WARNING] NVD API request failures are occurring; retrying request for the 9 time
17:40:41  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:42:48  [WARNING] NVD API request failures are occurring; retrying request for the 10 time
17:42:48  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:44:54  [WARNING] NVD API request failures are occurring; retrying request for the 11 time
17:47:16  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:49:22  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:51:29  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:53:51  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:55:58  [WARNING] NVD API request failures are occurring; retrying request for the 5 time
17:55:58  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
17:58:04  [WARNING] NVD API request failures are occurring; retrying request for the 6 time
17:58:04  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
18:00:26  [WARNING] NVD API request failures are occurring; retrying request for the 7 time
18:00:26  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
18:02:32  [WARNING] NVD API request failures are occurring; retrying request for the 8 time
18:02:32  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
18:04:39  [WARNING] NVD API request failures are occurring; retrying request for the 9 time
18:04:39  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
18:06:45  [WARNING] NVD API request failures are occurring; retrying request for the 10 time
18:06:45  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
18:09:07  [WARNING] NVD API request failures are occurring; retrying request for the 11 time
18:11:13  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
18:13:20  [INFO] Recoverable I/O exception (org.apache.hc.client5.http.ConnectTimeoutException) caught when processing request to {s}->https://services.nvd.nist.gov:443
Please advise @jeremylong @valentijnscholten . Thank you.

@jeremylong
I've been getting a multitude of errors on 9.0.7, from 403s (even though I'm running the command on my local machine with a fresh API Key) to database errors like

org.owasp.dependencycheck.data.nvdcve.DatabaseException: Unable to retrieve id for new vulnerability for 'CVE-2015-8482'
Caused by: org.h2.jdbc.JdbcSQLNonTransientConnectionException: The database has been closed [90098-214]
Writing to sun.nio.ch.FileChannelImpl@22ec811e failed; length 204800 at 9560064 [2.1.214/2]
java.lang.NullPointerException: Cannot invoke "org.apache.commons.dbcp2.BasicDataSource.getConnection()" because "this.connectionPool" is null

    at org.owasp.dependencycheck.data.nvdcve.DatabaseManager.getConnection (DatabaseManager.java:572)
    at org.owasp.dependencycheck.data.nvdcve.CveDB.updateOrInsertVulnerability (CveDB.java:941)
    at org.owasp.dependencycheck.data.nvdcve.CveDB.updateVulnerability (CveDB.java:866)
    at org.owasp.dependencycheck.data.update.nvd.api.NvdApiProcessor.call (NvdApiProcessor.java:98)
    at org.owasp.dependencycheck.data.update.nvd.api.NvdApiProcessor.call (NvdApiProcessor.java:33)

I'm downgrading back to 8.4.2 because 9.x.x has been nothing but trouble for me :-1:

Following up on previous report.

Have the same issue. API key works locally but on GitHub Actions the NVD update is (sometimes) interrupted by an exception:
[INFO] Downloaded 90,000/233,564 (39%)
[ERROR] Error updating the NVD Data
org.owasp.dependencycheck.data.update.exception.UpdateException: Error updating the NVD Data
...
Caused by: io.github.jeremylong.openvulnerability.client.nvd.NvdApiException: NVD Returned Status Code: 403`.

Do you have more than one repository using the same key?

API key only used in one repository and never in used in parallel executions.

Also, if you are using GH Actions I'd highly recommend caching the data directory. here is an example using the maven plugin.

Plugin database is cached in GitHub actions as per https://jeremylong.github.io/DependencyCheck/data/cache-action.html.
With the latest Maven plugin version (i.e. 9.0.7) the 403 Forbidden issue still appeared intermittently.
Since increasing the nvdApiDelay to 8000 the issue did not appear anymore.


Bump Gestalt version to 0.84.0

Deploy preview for gestalt ready!
Built with commit 631398c1f07183b9d0af3ed1c0d23c94564597cf
https://deploy-preview-424--gestalt.netlify.com


Transparency for the AR glasses

Describe your idea
the ability to add transparent objects in the AR glasses would provide people drawing alot more tools to workwith
(also it would be fun to blue people)
Describe alternatives you've considered if you've any
Alternative: a global transparency option that makes all rendered objects transparent over the game
(so that if you cover your screen you can still see)
Additional context
No response
Linked Issues
No response

Just saying that you can render in transparent colors using normal hex transparency colorcodes.
https://gist.github.com/lopspower/03fb1cc0ac9f32ef38f4

this does not work for text


chore(pkg,cmd): updated urlArchFmt to point to github pages urls.

Moreover, updated driverkit to v0.15.2 and dropped LastRunDistro support.
/hold

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

There is not a label identifying the kind of this PR.
Please specify it either using /kind <group> or manually from the side menu.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, maxgio92
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP,maxgio92]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/unhold


Aries OpenAPI Demo Errors

Following the Demo Script I have following issues:

Issuing a credential I receive the following error - "Error: agent Faber.Agent has no method handle_issue_credential to handle webhook on topic issue_credential"
Trying to find the Public DID on the ledger http://dev.greenlight.bcovrin.vonx.io. returns Null

Thanks
Olli

This is Alice side's Error: agent Alice.Agent has no method handle_issue_credential to handle webhook on topic issue_credential

The code now uses v2 of these protocols: I will update the docs accordingly


fix: make menu filter case-insensitive

Simple change, or you can regard this as an issue.

LGTM!


Related

I am trying to make a relation between a team member and a project, so in project will appear team member related and in team member will appear project. I tried sharing tags, but in team member appears only other team members and in project appears no one. Does anyone knows how to do that, or this does not exists?

The next major version of Academic will add multi-user support. In the meantime, please use forums if you need help with customization: https://discourse.gohugo.io


Cannot paste and drop down menu is not working

Paste:
Firefox, IE, not working. But Chrome and Edge is normal.
Drop down menu
When clicked, it will reload the page. For example, I type "Hello", then want to change the color to be red, I click the color button, then the page reloads.
The page link:
http://projbonus.codepulse.com.tw/test_materialNote.html

Have you tried using latest materialnote release?

I just tried the latest version 2.0.0, still the same. About the drop down menu, I see the summernote buttons have <button type="button"... >, but materialNote's buttons don't . We know that button's default type is "submit", I think this caused the dropdown menu. Why you dont have the problem...

My solution for Drop menu is to find the line
class="waves-effect waves-light btn dropdown
It's
'<button class="waves-effect waves-light btn dropdown ' + (btnClassName ? btnClassName : '') + '"',
Add type="button"
'<button type="button" class="waves-effect waves-light btn dropdown ' + (btnClassName ? btnClassName : '') + '"',
Then drop menu works.

I also see that there was a same issue:
Dropdown menus submit form
#18 opened on 31 Aug 2016 by diegonc
Why you don't fix this ?

these should be fixed in latest release


defineCustomElement does not support async component

What problem does this feature solve?
While the new defineCustomElement feature is really nice, it does not supports async components.
This feature is useful when you want to define multiple web components in one file without loading all of them (they will be loaded when the custom elements are used).
The following attempt mount the component but custom elements attributes are not passed to the Vue component.
customElements.define(
  'my-element',
  defineCustomElement(defineAsyncComponent(() => import('MyComponent.vue')))
)

Async components are currently supported by web-component-wrapper for Vue 2.x (https://github.com/vuejs/vue-web-component-wrapper)
const CustomElement = wrap(Vue, () => import(`MyComponent.vue`))
window.customElements.define('my-element', CustomElement)

What does the proposed API look like?
The defineCustomElement function could receive a function returning a Promise to a Vue Component like this :
customElements.define(
  'my-element',
  defineCustomElement(() => import('MyComponent.vue'))
)

When the <my-element></my-element> element is inserted somewhere in the DOM, the MyComponent.vue file should be be downloaded by the browser (if not already) and mounted.

A note: when importing SFCs as custom elements, the tooling needs to process the SFC styles as inlined CSS strings for shadow DOM injection.
This use case makes me realize that the current way SFC toolings handle custom elements (which imports the SFC directly as the custom element constructor) is flawed, since it makes it impossible to define a custom element with defineAsyncComponent + SFC. So I'll have to rework the behavior in @vitejs/plugin-vue and vue-loader.

Awesome ! Thanks for the super fast fix @yyx990803 and congrats for the 3.2 release !


Formatting Values in a Column (Please Help)

Newbie PowerShell user here.  Thanks so much for ImportExcel!!!
I’m creating an automated daily report on various server checks.  An example is DHCP scopes and the percentage used per scope.  I can’t seem to be able to format the Percentage in Use column (Column E) as a percentage.  I have a number of other similar outputs with the same issue.  Please can someone help as this would be great to crack!
Thanks in advance.  Please see example code:
#Variable for DHCP Servers
$DHCPServers = "DHCP001", "DHCP002", "DHCP003", "DHCP004", "DHCP005"
#Conditional Format Variables
$ScopeRed = New-ConditionalText -Range "E2:E1081" -ConditionalType GreaterThan 75  -BackgroundColor Red -ConditionalTextColor Black
$ScopeAmber = New-ConditionalText -Range "E2:E1081" -ConditionalType GreaterThan 50 -BackgroundColor LightYellow -ConditionalTextColor Orange
$ScopeGreen = New-ConditionalText -Range "E2:E1081" -ConditionalType LessThan 50  -BackgroundColor lightgreen -ConditionalTextColor Green
ForEach ($DHCPServer in $DHCPServers)
{
$DHCPScope = Get-DhcpServerv4Scopestatistics -ComputerName $DHCPServer | select ScopeID, Free, InUse, Reserved, PercentageInUse | Sort-Object ScopeID
$Line +=  $DHCPScope
}
$Line | Export-Excel -AutoSize  -FreezeTopRowFirstColumn -AutoFilter -WorksheetName "DHCPScopes" -Path "$Path\Server Checks - $Date.xlsx" -ConditionalText$ScopeRed, $ScopeAmber, $ScopeGreen
#Set-ExcelRange -Worksheet 'DHCPScopes' -Range e:e -NumberFormat 'Percentage'
#I can’t get this bit to work!!^^^^

Try this
$xlpkg = $Line | Export-Excel -AutoSize -FreezeTopRowFirstColumn -AutoFilter -WorksheetName "DHCPScopes" -Path "$Path\Server Checks - $Date.xlsx" -ConditionalText$ScopeRed, $ScopeAmber, $ScopeGreen -PassThru

Set-ExcelRange -Worksheet $xlpkg.DHCPScopes -Range e:e -NumberFormat 'Percentage'

Close-ExcelPackage $xlpkg -Show

Thanks so much for your answer.  That’s worked!!!
Although I need to divide the percentage values by 100 to display properly.  As an example the output value is showing as 4237.29%
There’s probably an easy way to do that.  But as the PercentageInUse is not a variable I don’t know how to achieve that?
So sorry, just trying to learn and getting caught with these gotchas
(I know this has nothing to do with Import-Excel and all to do with my lack of knowledge)

@dfinke
Please ignore my last comment.  I’ve managed to learn how to create a label and expression to get the values I wanted.
Thanks so much for your help, very much appreciated!


[BUG] Should popups be transparent with transparent_mode = true ?

Describe the bug

With active transparent mode popups looks weird.

Expected behaviour
We need to mark popups somehow (to keep background or add borders)
Screenshots

gruvbox.nvim is a colorscheme and it is not responsible for the floating window configuration. If you are using language servers and its floating windows, you can set up lspconfig borders in your own config like this:
local lsp = vim.lsp

vim.api.nvim_create_autocmd("LspAttach", {
  group = vim.api.nvim_create_augroup("UserLspConfig", {}),
  callback = function(event)
    lsp.handlers["textDocument/hover"] = lsp.with(lsp.handlers.hover, { border = "rounded" })
    lsp.handlers["textDocument/signatureHelp"] = lsp.with(lsp.handlers.signature_help, { border = "rounded" })

    local opts = { buffer = event.buf }
    local map = vim.keymap.set
    local lsp_buf = lsp.buf

    map("n", "K", lsp_buf.hover, opts)
    map("n", "gs", lsp_buf.signature_help, opts)
    -- more keymaps
  end,
})

@xudyang1 this issue is related to all popups windows.
Here is how which-key looks without and with transparent mode

@timsofteng For whichkey, you can set up border style by calling require('which-key').setup({ window = { border = "single" }).
Generally, if you want to configure all these plugin popup windows, you have to refer to the plugin's github page. Most configuration options are available in the README, so updating your config may not take too long.
Again, gruvbox.nvim is only a colorscheme and it does not have the capability to set up the border style (you can find details about border styles from :help nvim_open_win()). gruvbox.nvim only sets some plugins' border highlight or links them into existing highlight groups (see :h 'highlight', :h highlight-groups, and :h :highlight-link).
If you want to customize the popup border:

enable the plugin popup window border in the your config

then, if you want to change the border highlight (e.g., color), you can search for the highlight group of the plugin popup window border. Next, override it in gruvbox.nvim's config. For example:

require("gruvbox").setup({
  overrides = {
    LspInfoBorder = {
      link = "FloatBorder",
    },
  }
})

hey @timsofteng not sure if that's a bug, and honestly I don't use transparent mode so I am a little biased on how to process with this. If you think you have a good suggestion using an override that can be the default color please open a PR, add some screenshots and we can discuss. How about that?

I recently moved from the older gruvbox plugin to this one, and while it's nice that this has a built-in transparent mode unlike the stuff I hacked together with the other one, it does basically break popups. Popups should not use transparent backgrounds, they should keep whatever their existing backgrounds are for basic readability.


Modify depth dimensions to match our input

The original application is intended to be executed while capturing the NeRF input at the same time, or transmitting the input with DSS.
This PR performs the required tweaks to use previously recorded datasets in the following format:
dataset-dir
|
|--- depth
|    |
|    `--- 0.png
|--- rgb
|    |
|    `--- 0.png
|
` transforms.json

Changes:

The depth vector has the channels separated into 3 vectors, but the algorithm expects them to be all in 1 vector. Flattening the last dimension solves this by taking those 3 vectors and joining them.

When using the depth mask for the color_mask, it is expected that it has only 1 channel instead of 3, so the tiling is adapted for 3 channels. This is because the depth image is black and white, and could have been represented with 1 channel.

Add the possibility of generating a pointcloud output with the visualization script.
WARNING: Visualization script freezes if there is no GUI when ran.

Closing because changes are deprecated.


Add ability to make textField becomeFirstResponder

This is an awesome library, thanks for doing it. It would be a cool enhancement if I could make the textField firstResponder so that the user could start typing immediately.

HI @mlchild, thanks for the idea. This one should be easy. We can do it for the next release.
Do you maybe have time to help out with this?

Sure, I think could just add:
public func becomeFirstResponder() {
textField.becomeFirstResponder()
}
after the show/hide/add functions in CDAlertView.swift at line 320 (not sure how to do pull request, ha).
Could also do this one for symmetry:
public func resignFirstResponder() {
textField.resignFirstResponder()
}

It's better to check with isTextFieldHidden property. If it is hidden, we don't need to interrupt current responder chain. So I would suggest that
if !isTextFieldHidden {
    textField.becomeFirstResponder()
}```

same for resigning.

To do a PR, you should fork the repository first. This process will clone this repository to your account with saving connection to this one. Than you do your changes in forked repository (the one in your account). And from there, you will see `New Pull Request` button next to branch list. After pressing that, GitHub'll show you this repository and `master` branch as a `base fork`. And you only need to press `Create Pull Request` button in there :)


File structure migration

Thank you for making this component! I purchased one of these as soon as I discovered your component! I was going to do the bare minimum to get the component to work with my Home Assistant install anyway, so I figured I might as well try to go a little further and make it available to everyone else as well.
I attempted to migrate the structure of this component to match the structure requirements of recent Home Assistant versions. I may have missed something, but Home Assistant is adding additional requirements for components.
Here are a list of changes I made:

Reorganized the custom_components folder in the fashion required from now on. (example: emu2/sensor.py instead of sensors/emu2.py)
Created __init__.py.
Created manifest.json.
Created custom_components.json (in the root of this repository).
Renamed the emu2 to rainforest.

Sorry, I realize #5 steps on your toes a bit. My thinking was this reflects the name of the manufacturer instead of the model number. Which is how most official components work (examples: Raincloud, Ring, etc.) I also figure someday someone may want to extend this component to support other Rainforest models. You are welcome to undo that one if you prefer, it just helps my brain keep track of things a bit better.
#4 is totally optional but it helps people using custom_updater to keep their custom components and custom lovelace cards up to date.
If I understood what was going on a little better I would try to break the sensor up like the custom_components blueprint repository. Someday I will have to make a Hello World component so I can understand the process better. For now, let me know what you think.

Hi @brianhanifin, glad this worked for you! I've been very happy with the EMU2's reliability so far.
I pulled your changes and tested on my local instance (V0.91.1), they work perfectly. Also no worries about stepping on my toes! I like the changes, makes total sense.
#4 I not heard of this, but seems neat. I need to read up on this more when I get a chance.
I think it would be great if we could get the component to match the blueprint, then maybe that would make it easy to get integrated as an official component.

You are welcome. I'm glad I could help.
FYI, here is a screenshot of your component appearing on the Lovelace tracker card which goes with the Custom Updater component. I just added a link to your new custom_components.json file, and as long as you update the version number in both the sensor.py and custom_components.json files anyone with it setup will be able to click the "Update" button and your component will be updated automatically!

oh that's cool!

BTW, it worked. It showed 0.2.1 was available, I clicked update and it was done. :)


Intellisense NOT working at all

Issue Type: Bug
Can not get any intellisense when entering sql like "Select ... from MyTable".
I'm expecting the tool to show the table names after typing "from " but not at all.
In addition, when moving back to type fields after "select ", there is NO field available  to help input as well.
Peek definition returns "No definition for MyTable"
However, the select does work!
Azure Data Studio version: azuredatastudio 1.1.3 (2c007115f77427a7ff7af47ad6916fccf111ea11, 2018-10-17T21:21:46.083Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz (4 x 2592)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: unavailable_off

Memory (System)
15.88GB (4.31GB free)

Process Argv
C:\Program Files\Azure Data Studio\azuredatastudio.exe

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

agent
Mic
0.34.0

import
Mic
0.3.0

profiler
Mic
0.2.0

@shueybubbles this looks like it was introduced with the SMO 15 preview update.  I think we should rollback that update until we have a fix since this is a high impact bug.  I'm able to consistently repro on Azure DB and rolling-back to the previous SMO version resolves the issue for me.

@kburtram: thank you for the feedback and rollback to SMO 14 sounds like a reasonable solution, but there seems to be a path/parameter issue when issuing the command within ADS Terminal:
PS C:\Users\czhai> Install-Package Microsoft.SqlServer.SqlManagementObjects -Version 140.17283.0
Install-Package : A parameter cannot be found that matches parameter name 'Version'.
At line:1 char:58

... all-Package Microsoft.SqlServer.SqlManagementObjects -Version 140.172 ...

                                                     ~~~~~~~~

CategoryInfo          : InvalidArgument: (:) [Install-Package], ParameterBindingException
FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackage

PS C:\Users\czhai> dotnet add package Microsoft.SqlServer.SqlManagementObjects --version 140.17283.0
Could not find any project in C:\Users\czhai\.
Usage: dotnet add  package [options] <PACKAGE_NAME>
PS C:\Users\czhai> Install-Package -Name  Microsoft.SqlServer.SqlManagementObjects -MinimumVersion 140.17283.0 -MaximumVersion 140.17283.0
Install-Package : No match was found for the specified search criteria and package name 'Microsoft.SqlServer.SqlManagementObjects'. Try
Get-PackageSource to see all available registered package sources.

@CalvinZhai we're currently investigating this issue still.  We think it's an intellisense initialization issue introduced by https://github.com/Microsoft/sqltoolsservice/pull/702.  Once we have a fix available I'll publish an updated insiders build and the fix will be included in the Nov. release next week.

@MattIrv I merged your proposed fix for this issue with https://github.com/Microsoft/sqltoolsservice/pull/724.  Could you please verify that intellisense and peek\goto definition are working for the Nov release?  Thanks!

The fix for the Intellisense cache initialization bug is included in https://github.com/Microsoft/azuredatastudio/releases/tag/1.2.3.  Please reactive this issue if you still have this problem with this build or a subsequent build.  Thanks!


Color Picker - show color name

Summary of the Pull Request
Showing color name in the picker.
PR Checklist

[x] Applies to #7361
[x] CLA signed. If not, go over here and sign the CLA
[ ] Tests added/passed
[x] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Info on Pull Request
Ported internal WinUI implementation, now we show the same name as WinUI color picker
Added Niel's attribution into settings
In action:

When show color name is disabled the color picker looks the same as it does now (one row, smaller color square)
Settings:

Validation Steps Performed
Manual validation

@niels9001 Any opinions on the design?
I am not sure about the settings - where to place that checkbox - I don't want to put it at the end because no-one will find it, but now on the top it looks a little weird.

I'd personally under color format

Awesome!!!
Maybe under the shortcuts radiobuttons? And we could update the title to 'Shortcut & behavior' (like we have in Run or FancyZones if I recall correctly.

I would move the new checkbox under formats between clipboard format and editor format.
Reason: On the picker window the first value is the clipboard format and the second value is the name.
I wouldn't create a combined section for shortcut and behaviour.

Would it make sense to add the name as format for the editor too?

Does it make sense to add the name as format for the editor too?

Yeah we can add it, maybe not as a format, but just show that name somewhere, however I would prefer to keep it out of this PR as that will require some thinking and showing color name in the picker itself is probably the most useful part.

Moved checkbox -

when you toggle on / off. it does not resize the window until it finds a different color name.

@crutkas please open a new issue for this, it is not related to this PR

@martinchrzan I think this PR exposes the quirky behavior but ok

@crutkas fixed that issue in this PR

Moved checkbox -

@martinchrzan , @niels9001
Is there an incorrect spacing between Dropdown, Checkbox and "Editor Fornat"-header?
Sory for not seeing it before.

Does it make sense to add the name as format for the editor too?

Yeah we can add it, maybe not as a format, but just show that name somewhere, however I would prefer to keep it out of this PR as that will require some thinking and showing color name in the picker itself is probably the most useful part.

Let's wait if other users request it after release of next version.


Add Binary Lifting in the Tree Section

I will add binary lifting code in C++, a proper explanation, and sample questions.

I would like to work on this issue .

Hi @aaryahjolia , I am a GSSoC'23 contributor and would love to work on this issue.I have solved around 900 questions on leetcode(https://leetcode.com/code_hobby_2404/).


Make use of the extracted ErrorResponse

The ErrorResponse class moved into the scim-schema preoject. This
commit makes use of the class from the scim-schema. It need osiam/scim-schema#152 to be accepted.

I triggered the tests again, the tests are green now.

I guess you need to update also the ITs, right?

LGTM, thanks.


Alpha Doesn't Always Go to 1.0f

Started swiping back and forth after you mentioned how it could lead to problems https://github.com/mamaral/Onboard/pull/82#issuecomment-137148925 and noticed that the alpha wasn't always being fully reset back to 1.0 and sometimes it seems like it gets stuck at 0.  Swiping a little to the left/right takes things back to normal.
I downloaded the latest version (2.1.7) and recorded these while running the second example as the first one has the alerts popping up and makes it hard to demonstrate the swiping.
gfycat showing page disappearing: http://gfycat.com/SolidGregariousKouprey#?speed=0.5
alpha getting set somewhere between 0 and 1
http://gfycat.com/OrneryUnequaledFlycatcher?speed=0.5

I wrote a fix for that a while ago. Will submit a PR.

@sirdharma Awesome, thank you!


feat: dummy photos for when user doesn't have photo

change the value of style in app/utils/constants.tsx to change the image style
you can see and try them from here : dicebear.com

can you post to a profile without a n image

@ChristianChiarulli ok fixed, https://note-2l2r860m9-nodetec.vercel.app/4764a8f0f79ee607fdb614d64afdc03e59c893d08d6efaf2c6e6c5f7905a9c99
we should re-use the same usercard component for the post and profile, I can do it


feat: support more methods for errors and warnings in Compilation

… (6222)

Summary
Proxy array's method to compilation.rs for fix this issue. I don't know how to transfer functions between js and rust, so I didn't proxy the sort method of the array.
Checklist

[x] Tests updated (or not required).
[x] Documentation updated (or not required).

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I didn't see which issue you're trying to resolve. The link you provided seems not correct.

I didn't see which issue you're trying to resolve. The link you provided seems not correct.

Sorry, I made a mistake. Is this issue

I didn't see which issue you're trying to resolve. The link you provided seems not correct.

Sorry, I made a mistake. Is this issue

Looks good to me. Would you please fix get warnings() in Compilation too?

Ok, of course!

@h-a-n-a I have added tests for map function.

This patch made a breaking change by changing the type of compilation.errors to any.
In<EMAIL_ADDRESS>class Compilation {
    get errors(): {
        push: (...errs: (Error | JsStatsError | string)[]) => void;
        readonly length: number;
        [Symbol.iterator](): {
            next(): {
                done: boolean;
                value?: undefined;
            } | {
                value: JsStatsError;
                done: boolean;
            };
        };
    };
    get warnings(): {
        push: (...warns: (Error | JsStatsError)[]) => void;
        [Symbol.iterator](): {
            next(): {
                done: boolean;
                value?: undefined;
            } | {
                value: import("@rspack/binding").JsStatsWarning[];
                done: boolean;
            };
        };
    };
}

In<EMAIL_ADDRESS>class Compilation {
    get errors(): any;
    get warnings(): JsStatsWarning[];
}

@rspack/core

The error of rspack is different from WebpackError, and I don't know how to be compatible, so I gave it an any type. Can you give me some advice.🌟

I think JsStatsError would work.

I think JsStatsError would work.

you can open an issue.


Improve display of alerts in /alerts

The alerts on /alerts are currently ordered by their order in the rule files. As rule file names are not visible in that table, the order appears to be random. One way would be to sort all alerts alphabetically.

...or alternatively, group them by rule file. This could be better because thematically related alerts that are not necessarily alphabetically adjacent will stay grouped together.

By rule group would make the most sense, once we have those.

@brian-brazil Since rule groups cannot span files, it could even be nested. File -> Group.

I can have a look into this

I know this feature/issue has been mentioned a few times #3579
Here's what I've managed to do so far.
The alerts are grouped by their group name. The group name row isn't a chevron but just the name of the group. When I refresh the page however the Group rows shuffle (I haven't changed/added any code on how alerts within groups should be organised since I am unsure of how it works exactly, it might be a change in web.go).
Here's a link to my branch
https://github.com/BAESystemsAI/prometheus/tree/SortingAlertsv1
Any suggestions/ help would be really appreciated.

@pbhudiaBAE Looks like a great start! For the group sorting, you see how we use a byAlertStateAndNameSorter to sort alerts - we'd need something similar for the groups in web.go.

@juliusv Thanks. Having trouble sorting the groups. I tried to implement a similar method as to how alerts are grouped but I get the following error:
web/web.go:501:33: cannot use alerts (type *rules.AlertingGroups) as type []*rules.AlertingGroups in field value
web/web.go:503:9: cannot use groupSorter.Groups (type []*rules.AlertingGroups) as type *rules.AlertingGroups in assignment
web/web.go:947:21: invalid operation: s.Groups[i] < s.Groups[j] (operator < not defined on pointer)
I'm fairly new to Go and pointers aren't my strongest suit. Any suggestions/ help would be great :)

@pbhudiaBAE No problem, could you file a draft pull request (https://github.blog/2019-02-14-introducing-draft-pull-requests/)? That way it'll be easier to comment and all...

@juliusv I've made a draft pull request #5448. Ignore the first one, I accidentally made it open and couldn't make it a draft again. The latest commit failed the tests because it doesn't build due to those pointer issues in web.go.

Can this issue be closed now since #5448 has been merged

Thanks, closing it.


fix: numeric type input widget should accept zero after decimal point

Description
Originally we solved this issue by converting the text property into a derived property. but that started causing issues when the Input widget was placed inside the List widget. https://github.com/appsmithorg/appsmith/issues/11833
Note:

Ideally, the text property of the input widget should be a derived property.
But derived properties of List widget children won't work. so having the text
property of the Input widget as a derived property causes issues. hence changing
it to a meta property.

Fixes #11449
Fixes #11839
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions, so we can reproduce.
Please also list any relevant details for your test configuration.

Test A
Test B

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented on my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

/ok-to-test sha=9b534d1

/ok-to-test sha=4be3ce4

@sbalaji1192 Tested and LGTM

/ok-to-test sha=4be3ce4

/ok-to-test sha=4be3ce4

/ok-to-test sha=20c699b

/ok-to-test sha=ad3a3ea


Bootstrap 4 and Laravel 5.5

Is there any plan or activities going on regarding Bootstrap 4 and Laravel 5.5?

5.5 has been tested #407 and package auto discovery has been working since release 1.8.1 as per this PR #352 .
About bootstrap 4 i'm not sure. Bootstrap is still in aplha now. Do you think it will add extra value when it releases?

Bootstrap v4 is Beta now and it is the default version at http://getbootstrap.com. So from now on anyone download the library will get this version. But as like the previous version there are links to visit the Bootstrap v3.
For the next release, Bootstrap v4 should be added. As every one is not ready and not all the the templates are v4 ready, so v3 and v4 select option could be added on the config page.

Cool I wasn't aware the beta was out. The filemanager runs in a new window or iframe so there will not be any compatibility issues when people use the Bootstrap 4 beta in their project.

Laravel 5.5 is supported already. It's true that the styles of filemanager does not have compatibility with laravel project. But still we should use Bootstrap v4 instead of v3 for future version. I will add this as a milestone of v2.0 .

Implemented in d3c7aba.


Upgrade to python 3.7

Fixes #306

The travis tests won't run on my last commit. In Travis, I can see that the tests passed here and here. but it doesn't appear in the PR. It seems to be a problem with the settings or the branch (as explain here), but i don't have permissions to access the settings tab and fix it.

 In Travis, I can see that the tests passed here and here. but it doesn't appear in the PR. It seems to be a problem with the settings or the branch (as explain here), but i don't have permissions to access the settings tab and fix it.

it seems to be a bug, also see here: https://github.com/neuropoly/spinalcordtoolbox/pull/2739
try to re-commit something?

Re-commit did the trick, thanks!

This PR is ready for re-review with the addition of ADS version change to 3.2.


docker desktop for windows

so I'm using docker desktop for windows, I have the container installed and the rasp stream entered and I believe the filters and the output is right but I still get nothing.

Can you post your config.yaml here? Don't forget to remove sensitive information.

If you're still having problems, let me know. Closing this issue until then.


Bundle external dependencies

In my project I'm using both npm modules and bower components (with debowerify) which I want to bundle together as vendor.js while keeping my own code in an app.js bundle.
What I did so far is created the app.js bundle by setting external to the npm modules and bower components. To figure out what modules to set as external I read the dependencies from package.json and bower.json.
Now, in a similar fashion I would like to parse my codebase, see which requires are external modules and bundle them together.
How could I do this?

Hello, anybody have a solution to the question above? I know it's very old, but I am now starting to use factor-bundle, and I am facing the same situation.

Factor Bundle has the ability to run a custom filter via the transform option. So you could do:
#!/usr/bin/env node
var browserify = require('browserify')
var fs = require('fs')
var path = require('path')

var entries = [
  path.join(__dirname, 'index.js')
]

var outputFiles = [
  path.join(__dirname, 'dist-main.js')
]

var b = browserify(entries)

b.plugin('factor-bundle', {
  output: outputFiles,
  threshold: function (row, groups) {
    // Get a relative directory to where we are building
    var rPath = path.relative(__dirname, row.file)

    // Assuming our node_modules folder is in the same directory that we are
    // building in then just declare vendor files as those presiding in it
    return !!rPath.match(/^node_modules\//)
  }
})

b.bundle().pipe(fs.createWriteStream(path.join(__dirname, 'dist-vendor.js')))

I've made a simply repository showing it all together.


Use stderr, python3 support

This PR is extended on #23 and will show many changes until that PR is merged. This change will prevent joe from writing an error to the .gitignore file.

A lot has changed since PR #23, and if that is merged, PR #19 (Make joe.py play better with Python 3.x by @keph) won't be very clean. Now the only print statements are in main(), so the only changes that had to be made were three times in that function.

Just one minor issue. Otherwise looks good.


[FEAT] C++ template can be updated

Hello maintainer, I just came across this CP template and it's really awesome!
CP Template Gist
What's your opinion??? And don't tag me this time for comment!!! Just say your review bro, and don't tag me!

Seriously, don't tag me :(

We are not looking to make changes to the default C++ template, we have provided functionality for user to use their own templates in their programs. Therefore, closing this issue now.


De-pivotal code and make a code.cloudfoundry.org package

This change removes more references to Pivotal and makes the package import path code.cloudfoundry.org/tlsconfig in line with other cloudfoundry org Go packages.
We left in this reference: https://github.com/cloudfoundry/tlsconfig/blob/a69ae9ffab8df04fb51451427b6b5203990c2fe0/config.go#L77 as we were not yet sure what to update this to or if we should just leave it alone, comments on this would be appreciated

The comment is probably fine for now but we should find a way to take relevant excerpts of that document and make them public. I'll try to work on that over the next few weeks.


EFS names_regex is not applied when the EFS file system has no name

For using cloud-nuke aws --config test_config.yaml --dry-run --region eu-west-1 a config files was set up called cloud-nuke.yaml
This included the following block
ElasticFileSystem:
  include:
    names_regex:
    - test_cm

The name property for AWS Elastic File Systems is optional.   The expectation is that EFS with no names would be excluded as they do not match the include names_regex.

Behaviour type
Description

Expected
Where a names_regex is specified, only those items whose name matches the RegEx are retrieved.  Objects without names are excluded

Actual
Object whose names match the RegEx are correctly chosen. Objects with no names are incorrectly included

Hi @Macaw-DJP, are you sure you've included the followings in your test_config.yaml file? Make sure you have this inside your test_config.yaml, not the cloud-nuke.yaml file.
ElasticFileSystem:
  include:
    names_regex:
    - test_cm

I just tested your command with the latest change and it seems to work fine.

Without Config

With Config

As you spotted, here was a typo in the example command I gave, it should have said cloud-nuke.yaml rather than test_config.yaml.  However the results I am seeing are as described earlier.
This sounds like one of those problems that is hard to reproduce.
cloud-nuke aws --config cloud-nuke.yaml --dry-run --region eu-west-1

I have also tried
cloud-nuke aws --config cloud-nuke.yaml --dry-run --region eu-west-1 --resource-type efs

I've double checked cloud-nuke.yaml and it does have
ElasticFileSystem:
  include:
    names_regex:
    - test_cm

I'm experimenting with  cloud-nuke on a MacBook running OSX Sonoma 14.5.
# The following returns 0.37.1
cloud-nuke --version

I wasn't able to reproduce this issue. Are you using the latest version of cloud-nuke or some specific version? As you can see from my screenshots, I created EFS with specific name and tested running the command and it worked fine.

Just using cloud-nuke installed on a MacBook as per the README.md. brew install cloud-nuke which installed 0.37.1.
I'm going to try running it with --log-level debug.  It's going to be an embarrassing PEBCAK error at my end, I just can't see it at the moment.
I will feed back ASAP though I think this issue may need to be closed with "Cannot reproduce".
Great product though, wish I'd had it a couple of months ago when I had to do a complete tear-down of a legacy environment.

--log-level debug did not reveal anything new.
Re-ran my scenarios and got the same resultas before.

Where a name exists then the names_regex works as expected.
Where a name is empty RegEx is not applied.

Interesting. Seems like you are using the latest version so using the same version as mine.
Yeah since we cannot reproduce, won't be able to help with further troubleshooting.
Will close this issue for now but let us know if you have further issue with this.

I have a suspicion as to what may be going on but I am not a GO developer so can't confirm.
EFS objects do not have a Name property.  They use a Tags list property of Key:Value pairs with a Key of Name where the Value holds the name.
If I deliberately create an EFS object from the AWS console without a name then this still gets a Name tag
"Tags": [
        {
          "Key": "Name",
          "Value": ""
        },
        {
          "Key": "aws:elasticfilesystem:default-backup",
          "Value": "enabled"
        }
      ]

This EFS object is correctly ignored by cloud-nuke because, as expected, the empty string value for Name does not match the test_cm listed in names_regex.
The 2 empty named EFS objects that are showing up unexpectedly DO NOT have a Name tag.
      "Tags": [
        {
          "Key": "Customer",
          "Value": "cm"
        },
        {
          "Key": "EFSCreationToken",
          "Value": "ttanyw"
        },
        {
          "Key": "Environment",
          "Value": "test"
        },
        {
          "Key": "Project",
          "Value": "ttanyw"
        }
      ]

As there is no Name tag, cloud-nuke cannot filter on Name therefore does not exclude these items.
HOWEVER - The Terraform resource aws_efs_file_system does not insist on a Name tag and will therefore create an object that cannot be filtered out.
Our work around is to ensure our Terraform module for creating EFS objects always includes a Name tag.
If my diagnosis is correct then my recommendation for cloud-nuke would be that (for AWS objects who rely on a tag with a Name key for the object name) items an include2 names_regex filter exclude any objects that DO NOT have the desired Name key in their tags.


Grub efi amd64 image

Changes

Add a amd64 example image which makes use of grub-efi.

Dependencies:
none
Tests results
<!-- add Robot test CLI logs here. -->

Developer Checklist:

[x] Test: Changes are tested
[ ] Doc: Documentation has been updated
[x] Git: Informative git commit message(s)
N/A Issue: If a related GitHub issue exists, linking is done

Checklists for documentation

[ ] Grammar: the content is grammatically correct
(spelling, grammar, formatting, US English is used)
[ ] Comprehensibility/Unambiguousness: the content is easy readable, clear to understand
[ ] Correctness and consistency: the content is technically correct and consistent,
no contradictions, no double descriptions
[ ] Terminology: technical terms are clear and they are used correctly and documented in the glossary
[ ] Level of detail: the content matches the detail level necessary for the reviewed object

Reviewer checklist:

[ ] Review: Changes are reviewed
[ ] Review: Tested by the reviewer

Checklists for documentation

[ ] Grammar: the content is grammatically correct
(spelling, grammar, formatting, US English is used)
[ ] Comprehensibility/Unambiguousness: the content is easy readable, clear to understand
[ ] Correctness and consistency: the content is technically correct and consistent,
no contradictions, no double descriptions
[ ] Terminology: technical terms are clear and they are used correctly and documented in the glossary
[ ] Level of detail: the content matches the detail level necessary for the reviewed object

Skipping the documentation for the new image now. Images needs to be aligned and clean up.


[fix][perf] fix performanceConsumer log error throughput

Motivation
fix error throughput log in performanceConsumer. bytes -> Mb no need to *8.
Modifications
fix error.
Verifying this change

[x] Make sure that the change passes the CI checks.

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

fix error throughput log in performanceConsumer. bytes -> Mb no need to *8.

The previous calculation is intentional. The previous unit has been megabits instead of megabytes.
https://github.com/apache/pulsar/blob/002fa49692ff4b8b038bf2edeeb3b32ed218e64f/pulsar-testclient/src/main/java/org/apache/pulsar/testclient/PerformanceConsumer.java#L526

Ok. But I think MB is clearer

Ok. But I think MB is clearer

@TakaHiR07 I agree that it's confusing to use Mbit/s here and MB/s in many other locations.
Network bandwidth is commonly expressed as Mbit/s. Perhaps the reason to use Mbit/s here is to match the unit that is used for network bandwidth.


Play Store Listing

Prepare play store listing and everything necessary there: rating, etc

[x] create a list of things to prepare

We need to prepare:

[ ] Short description
[ ] Full description
[ ] Screenshots
[ ] Hi-res icon
[ ] Feature graphic
[ ] Application type
[ ] Category

We need to prepare:

[ ] Short description
[ ] Full description
[ ] Screenshots
[ ] Hi-res icon
[ ] Feature graphic
[ ] Application type
[ ] Category

Please do :)

Please do :)


seems java issue when doing opengrok indexing

08:15:05 WARNING: Failed to determineCurrentVersion for /opt/o-source: java.io.IOException: error: packfile .git/objects/pack/pack-d66eed4a94133ad4ab2fae55a3f561520b58ce62.pack does not match index
error: packfile .git/objects/pack/pack-d66eed4a94133ad4ab2fae55a3f561520b58ce62.pack does not match index
error: packfile .git/objects/pack/pack-d66eed4a94133ad4ab2fae55a3f561520b58ce62.pack does not match index
error: packfile .git/objects/pack/pack-d66eed4a94133ad4ab2fae55a3f561520b58ce62.pack does not match index
fatal: bad object HEAD
08:15:05 WARNING: Non-zero exit status 128 from command [/usr/local/bin/git, log, --abbrev-commit, --abbrev=8, --name-only, --pretty=fuller, --date=iso8601-strict, --, /opt/o-source] in directory /opt/o-source: error: packfile .git/objects/pack/pack-d66eed4a94133ad4ab2fae55a3f561520b58ce62.pack does not match index
error: packfile .git/objects/pack/pack-d66eed4a94133ad4ab2fae55a3f561520b58ce62.pack does not match index
error: packfile .git/objects/pack/pack-d66eed4a94133ad4ab2fae55a3f561520b58ce62.pack does not match index
error: packfile .git/objects/pack/pack-d66eed4a94133ad4ab2fae55a3f561520b58ce62.pack does not match index
fatal: bad object HEAD
08:15:05 WARNING: An error occurred while creating cache for /opt/o-source/ (GitRepository)
org.opensolaris.opengrok.history.HistoryException: Failed to get history for: "/opt/o-source" Exit code: 128
at org.opensolaris.opengrok.history.GitHistoryParser.parse(GitHistoryParser.java:181)
at org.opensolaris.opengrok.history.GitRepository.getHistory(GitRepository.java:484)
at org.opensolaris.opengrok.history.Repository.createCache(Repository.java:332)
at org.opensolaris.opengrok.history.HistoryGuru.createCache(HistoryGuru.java:587)
at org.opensolaris.opengrok.history.HistoryGuru.access$000(HistoryGuru.java:63)
at org.opensolaris.opengrok.history.HistoryGuru$1.run(HistoryGuru.java:638)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

works well on Mac with Java compiled using HomeBrew

This may be a joke, it was my mistake
I put some source under /source
but I 'git init' for that directory by accident, and ignore it after that, ha..
and '08:15:05 WARNING: Failed to determineCurrentVersion for /opt/o-source: java.io.IOExce'
points to that directory


Resizing of text box for nodes with narrow widths

My main issue here is that the text box for a node doesn't seem to resize with the height of the node.
Streamlit Flow is a great new component. It looks like it could be just what I need for my app project which involves hierarchically tree-linked lists.
To use Flow I need to give nodes an interior node structure, a stacked set of nodes within a node. I can do this, as is illustrated in this file. Most everything seems to work well. Particularly, with interaction, clicking on a subnode returns the subnode, while clicking on the node area still properly returns the parent node.
My principal problem is that specifying the height of a node does not resize the associated text box. I have tried css to correct this, but have found only that setting top padding to zero reduces the problem. Negative padding does not work. In the example code, the left node and subnodes are properly realized. The text for the right node and subnodes with narrower height does not realize properly.
Additionally, it would be nice to have text for the parent nodes that appears above the stack of subnodes.
A fix or an explanation of how to use css to solve this problem would be great.
One additional problem, which I have not extensively investigated yet, is that the edges don't seem to properly display. This may have something to do with the specification of the node types. There doesn't seem to be much documentation about this. I have coded for four edges, but only one is displayed in this example. Any pointers here will be appreciated!
Example file: https://github.com/stepsbystep/stopwatch/blob/main/flowInteraction2A.py

@stepsbystep
Let's do it step by step ;o)
Padding issue

My principal problem is that specifying the height of a node does not resize the associated text box. I have tried css to correct this, but have found only that setting top padding to zero reduces the problem. Negative padding does not work. In the example code, the left node and subnodes are properly realized. The text for the right node and subnodes with narrower height does not realize properly.

I saw your code, well done on trying various css options, I've been there as well :)
This issue is caused due to the default margin-top: 8px css settings for the paragraph within the node, you can see when inspecting the node:

To address this issue you need to enter your content data with specific paragraph styling, and add zero padding to the node:
StreamlitFlowNode('24', (300, 250), {'content': '
Node 2-4
'}, 'output', target_position='left', draggable=True,
                      width=100, height=25, style={ "padding": 0 }),

Also a note - padding doesn't support negative values, only margin does. Negatives are considered 0.
Parent text

Additionally, it would be nice to have text for the parent nodes that appears above the stack of subnodes.
A fix or an explanation of how to use css to solve this problem would be great.

Just change the parent height, so the subnodes won't hide the parent text from view, the text is on top, and you can use the previous method to control where the text appears on the parent.
In any case, in React Flow there's a node type called group which is exactly what you're trying to achieve.
When I'll have some time I'll add this type to streamlit-flow in the next version, it should be easier than using an input/output node for it.

Edges issue

One additional problem, which I have not extensively investigated yet, is that the edges don't seem to properly display. This may have something to do with the specification of the node types. There doesn't seem to be much documentation about this. I have coded for four edges, but only one is displayed in this example. Any pointers here will be appreciated!

The nodes currently have 3 types: default, input, output
default - has two connections - input and output
input/output - has one connection to be used as input or output respectively.
When initializing a StreamlitFlowNode() object, you have these parameters:
node_type - choose one of the 3 types above, according to the use case.
source_position - if the node is of input type, this determines where the "out" edge connection resides (out of the input node)
target_position - if the node is of output type, this determines where the "in" edge connection resides (into the output node)
So if your edges are configured like this:
edges = [
    StreamlitFlowEdge('14-21', '14', '21', animated=True),
    StreamlitFlowEdge('11-23', '11', '23', animated=True),
    StreamlitFlowEdge('12-21', '12', '21', animated=True),
    StreamlitFlowEdge('13-24', '13', '24', animated=True)
]

The input nodes are - 14, 11, 12 and 13
The output nodes are - 21, 23 and 24
Once you configure the nodes types and connections properly, it all renders as expected:

This is the code:
nodes = [
    StreamlitFlowNode(id='10', pos=(90, 90), data={'content': "Node 1-0"},  node_type='output', draggable=False,
                      width=120, height=220),
    StreamlitFlowNode(id='11', pos=(100, 100), data={'content': "Node 1-1"},  node_type='input', source_position='right', draggable=False,
                      width=100, height=50),
    StreamlitFlowNode('12', (100, 150), {'content': 'Node 1-2'}, 'input', 'right', draggable=False,
                      width=100, height=50),
    StreamlitFlowNode('13', (100, 200), {'content': 'Node 1-3'}, 'input', 'right', draggable=False,
                      width=100, height=50, style={'width': '50px'}),
    StreamlitFlowNode('14', (100, 250), {'content': 'Node 1-4'}, 'input', source_position='right', draggable=False,
                      width=100, height=50),

    StreamlitFlowNode(id='20', pos=(290, 90), data={'content': "Node 2-0"},  node_type='output', draggable=False,
                      width=120, height=220),
    StreamlitFlowNode(id='21', pos=(300, 100), data={'content': "Node 2-1"},  node_type='output', target_position='left', draggable=False,
                      width=100, height=25),
    StreamlitFlowNode('22', (300, 150), {'content': 'Node 2-2'}, 'input', 'left', draggable=False,
                      width=100, height=25),
    StreamlitFlowNode('23', (300, 200), {'content': 'Node 2-3'}, 'output', target_position='left', draggable=False,
                      width=100, height=25, style = {'padding-top' : 0}),
    StreamlitFlowNode('24', (300, 250), {'content': '
Node 2-4
'}, 'output', target_position='left', draggable=False,
                      width=100, height=25, style={ "padding": 0 }),
]

All the best...


Add display of direct messages

Add the ability to show direct message channels between an ad hoc
group of users.
The data model here is that direct message channels don't exist inside
all_channels_holder, but instead are based on being a member of a
group named dm:USERID1,USERID2.  The channel fetcher on the backend
finds all the groups the user is a member of that have the dm:
prefix and sends them to the client.  Then the client mostly just
treats those as channels like normal except for using a different
icon.
The main code change is to expand the Channel structure to include a
name separate from the ID, and then a chunk of code in the channels
provider to fetch the list of channels, look up the names of all the
users in all the DM channels, and set the names of the channels to the
appropriate things.
This doesn't yet include the ability to create a DM channel, so it
only works if you create these groups manually in the command line,
the Cord console, etc.  That will come in a future diff.
I'm also not super pleased with all the places that have to check for
channel.id.startsWith(DM_CHANNEL_PREFIX).  I might add a separate
property in the Channel struct for that to make the code clearer in
a future diff.

#147  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @flooey and the rest of your teammates on  Graphite

Merge activity

May 1, 1:36 PM GMT+1: @flooey started a stack merge that includes this pull request via Graphite.


Fix typo in get-started.md

Simple typo in the docs has strings and numbers the wrong way round. Not sure what's happening with the bottom line on the diff - maybe a line ending difference?

Never mind, someone else has fixed this in the mean time :)

Appreciate the effort nonetheless @matthewpull!


Embed in Single Basic HTML

Hi,
I am wondering how to include the library in single page HTML ?
I tried this, but it didn't work
    <script<EMAIL_ADDRESS>It says like this

ReactPlayer.js:3 Uncaught ReferenceError: exports is not defined
    at ReactPlayer.js:3
(anonymous) @ ReactPlayer.js:3

@ejabu it looks like is a bundle bug. i will take a look