text:
cve downloads only as far as 2011/dependency-check analysis issue

Hi,
I'm using the master 3.0 dev branch & have uploaded a few test projects scanned by dependency check on Jenkins; I can publish the results to dependency-track but see some strange things in the logs that also exist in the UI.

the UI only has CVEs up to 2011, thus the projects are not fully scanned:

2017-10-18 07:00:32,575 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading https://static.nvd.nist.gov/feeds/json/cve/1.0/nvdcve-1.0-2010.json.gz
2017-10-18 07:00:34,075 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-1.0-2010.json.gz
2017-10-18 07:00:34,386 [] INFO [org.owasp.dependencytrack.parser.nvd.NvdParser] Parsing nvdcve-1.0-2010.json
2017-10-18 07:00:41,686 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-18 07:00:41,687 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading https://nvd.nist.gov/download/nvdcve-2011.xml.gz
2017-10-18 07:00:42,886 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2011.xml.gz
2017-10-18 07:00:43,069 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-18 07:00:43,070 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading https://nvd.nist.gov/feeds/xml/cve/nvdcve-2.0-2011.xml.gz
2017-10-18 07:00:45,454 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2.0-2011.xml.gz
2017-10-18 07:00:45,976 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-18 07:00:45,977 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading https://static.nvd.nist.gov/feeds/json/cve/1.0/nvdcve-1.0-2011.json.gz
2017-10-18 07:00:46,760 [] INFO [alpine.AlpineServlet] Starting Dependency-Track
2017-10-18 07:00:49,364 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-1.0-2011.json.gz
2017-10-18 07:00:50,258 [] INFO [org.owasp.dependencytrack.parser.nvd.NvdParser] Parsing nvdcve-1.0-2011.json

none of the CVEs found in dependency check are uploaded to the UI, looking at the logs:

2017-10-18 06:59:17,929 [] DEBUG [org.owasp.dependencycheck.utils.Settings] Setting: data.directory='/root/.dependency-track/dependency-check/data'
2017-10-18 06:59:17,929 [] INFO [org.owasp.dependencycheck.agent.DependencyCheckScanAgent] Populating settings
2017-10-18 06:59:17,929 [] DEBUG [org.owasp.dependencycheck.utils.Settings] Setting: autoupdate='false'
2017-10-18 06:59:17,929 [] DEBUG [org.owasp.dependencycheck.utils.Settings] Setting: analyzer.central.enabled='true'
2017-10-18 06:59:17,929 [] DEBUG [org.owasp.dependencycheck.utils.Settings] Setting: analyzer.nexus.enabled='true'
2017-10-18 06:59:17,929 [] DEBUG [org.owasp.dependencycheck.utils.Settings] Setting: analyzer.nexus.proxy='true'
2017-10-18 06:59:17,930 [] DEBUG [org.owasp.dependencycheck.analyzer.AnalyzerService] Loaded Analyzer Archive Analyzer
2017-10-18 06:59:17,930 [] DEBUG [org.owasp.dependencycheck.analyzer.AnalyzerService] Loaded Analyzer File Name Analyzer
2017-10-18 06:59:17,930 [] DEBUG [org.owasp.dependencycheck.analyzer.AnalyzerService] Loaded Analyzer Jar Analyzer
2017-10-18 06:59:17,930 [] DEBUG [org.owasp.dependencycheck.analyzer.AnalyzerService] Loaded Analyzer Hint Analyzer
2017-10-18 06:59:17,930 [] DEBUG [org.owasp.dependencycheck.analyzer.AnalyzerService] Loaded Analyzer CPE Analyzer
2017-10-18 06:59:17,930 [] DEBUG [org.owasp.dependencycheck.analyzer.AnalyzerService] Loaded Analyzer False Positive Analyzer
2017-10-18 06:59:17,931 [] DEBUG [org.owasp.dependencycheck.analyzer.AnalyzerService] Loaded Analyzer Cpe Suppression Analyzer
2017-10-18 06:59:17,931 [] DEBUG [org.owasp.dependencycheck.analyzer.AnalyzerService] Loaded Analyzer Dependency Bundling Analyzer
2017-10-18 06:59:17,931 [] DEBUG [org.owasp.dependencycheck.analyzer.AnalyzerService] Loaded Analyzer Dependency Merging Analyzer
2017-10-18 06:59:17,931 [] DEBUG [org.owasp.dependencycheck.analyzer.AnalyzerService] Loaded Analyzer NVD CVE Analyzer
2017-10-18 06:59:17,931 [] DEBUG [org.owasp.dependencycheck.analyzer.AnalyzerService] Loaded Analyzer Vulnerability Suppression Analyzer
2017-10-18 06:59:17,931 [] DEBUG [org.owasp.dependencycheck.analyzer.CentralAnalyzer] Enabling the Central analyzer
2017-10-18 06:59:17,931 [] DEBUG [org.owasp.dependencycheck.analyzer.AnalyzerService] Loaded Analyzer Central Analyzer
2017-10-18 06:59:17,931 [] DEBUG [org.owasp.dependencycheck.analyzer.NexusAnalyzer] Nexus analyzer disabled, using Central instead
2017-10-18 06:59:17,931 [] DEBUG [org.owasp.dependencycheck.analyzer.AnalyzerService] Loaded Analyzer Nexus Analyzer
2017-10-18 06:59:17,931 [] DEBUG [org.owasp.dependencycheck.analyzer.AnalyzerService] Loaded Analyzer Nuspec Analyzer
2017-10-18 06:59:17,931 [] DEBUG [org.owasp.dependencycheck.analyzer.AnalyzerService] Loaded Analyzer Assembly Analyzer
2017-10-18 06:59:17,932 [] DEBUG [org.owasp.dependencycheck.analyzer.AnalyzerService] Loaded Analyzer OpenSSL Source Analyzer
2017-10-18 06:59:17,932 [] DEBUG [org.owasp.dependencycheck.analyzer.AnalyzerService] Loaded Analyzer Node Security Platform Analyzer
2017-10-18 06:59:17,932 [] DEBUG [org.owasp.dependencycheck.analyzer.AnalyzerService] Loaded Analyzer Ruby Bundle Audit Analyzer
2017-10-18 06:59:17,932 [] DEBUG [org.owasp.dependencycheck.analyzer.AnalyzerService] Loaded Analyzer Version Filter Analyzer
2017-10-18 06:59:17,932 [] DEBUG [org.owasp.dependencycheck.utils.Settings] Settings.getDataFile() - file: '/root/.dependency-track/dependency-check/data'
2017-10-18 06:59:17,932 [] DEBUG [org.owasp.dependencycheck.utils.Settings] Connection String: 'jdbc:h2:file:/root/.dependency-track/dependency-check/data/dc;MV_STORE=FALSE;AUTOCOMMIT=ON;LOCK_MODE=0;FILE_LOCK=NO'
2017-10-18 06:59:17,932 [] DEBUG [org.owasp.dependencycheck.utils.Settings] Settings.getDataFile() - file: '/root/.dependency-track/dependency-check/data'
2017-10-18 06:59:17,954 [] DEBUG [org.owasp.dependencycheck.data.nvdcve.CveDB] Database product: h2
2017-10-18 06:59:17,956 [] ERROR [org.owasp.dependencycheck.Engine] No documents exist
Unable to continue dependency-check analysis.
2017-10-18 06:59:17,956 [] DEBUG [org.owasp.dependencycheck.Engine]
org.owasp.dependencycheck.exception.NoDataException: No documents exist
at org.owasp.dependencycheck.Engine.ensureDataExists(Engine.java:897)
at org.owasp.dependencycheck.Engine.analyzeDependencies(Engine.java:604)
at org.owasp.dependencycheck.agent.DependencyCheckScanAgent.executeDependencyCheck(DependencyCheckScanAgent.java:887)
at org.owasp.dependencycheck.agent.DependencyCheckScanAgent.execute(DependencyCheckScanAgent.java:972)
at org.owasp.dependencytrack.tasks.DependencyCheckTask.analyze(DependencyCheckTask.java:149)
at org.owasp.dependencytrack.tasks.DependencyCheckTask.performAnalysis(DependencyCheckTask.java:92)
at org.owasp.dependencytrack.tasks.DependencyCheckTask.inform(DependencyCheckTask.java:64)
at alpine.event.framework.BaseEventService.lambda$publish$0(BaseEventService.java:86)
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)
I have attached some screenshots of what I see in terminal & UI.
Thanks,
AD

After restarting, does it pick up where it left off?
The nist-data-mirror and Dependency-Track share roughly the same code responsible for mirroring the NVD. Neither of these currently support the NVD sending back a 403, which they are doing now. The NVD appears to be limiting excessive or repeated requests to the same downloads and they send a 403 in response. Dependency-Track will need to be changed to address these scenarios.
If the download failures are related to something else, then I'm not sure. Let me add in some additional checks and you can retest and enable debug logging at the same time.

I've added additional logging. Can you try again and see what the logs say?

here is the full log after deploying the war, results are still the same:
2017-10-19 04:28:24,332 [] INFO [alpine.Config] --------------------------------------------------------------------------------
2017-10-19 04:28:24,337 [] INFO [alpine.Config] Initializing Configuration
2017-10-19 04:28:24,337 [] INFO [alpine.Config] System property alpine.application.properties not specified
2017-10-19 04:28:24,337 [] INFO [alpine.Config] Loading application.properties from classpath
2017-10-19 04:28:24,338 [] INFO [alpine.Config] --------------------------------------------------------------------------------
2017-10-19 04:28:24,338 [] INFO [alpine.Config] Application: Dependency-Track
2017-10-19 04:28:24,339 [] INFO [alpine.Config] Version:     3.0.0-SNAPSHOT
2017-10-19 04:28:24,339 [] INFO [alpine.Config] Built-on:    2017-10-19 08:17:57
2017-10-19 04:28:24,339 [] INFO [alpine.Config] --------------------------------------------------------------------------------
2017-10-19 04:28:24,339 [] INFO [alpine.Config] Framework:   Alpine
2017-10-19 04:28:24,339 [] INFO [alpine.Config] Version :    1.0.0-SNAPSHOT
2017-10-19 04:28:24,339 [] INFO [alpine.Config] Built-on:    2017-10-16 18:36:51
2017-10-19 04:28:24,339 [] INFO [alpine.Config] --------------------------------------------------------------------------------
2017-10-19 04:28:24,343 [] INFO [alpine.persistence.PersistenceManagerFactory] Initializing persistence framework
2017-10-19 04:28:29,168 [] INFO [org.owasp.dependencytrack.persistence.CweImporter] Syncing CWEs with datastore
2017-10-19 04:28:30,962 [] INFO [org.owasp.dependencytrack.persistence.CweImporter] CWE sync complete
2017-10-19 04:28:38,373 [] INFO [org.owasp.dependencytrack.tasks.DependencyCheckTask] Executing Dependency-Check update-only task
2017-10-19 04:28:38,375 [] INFO [org.owasp.dependencytrack.tasks.MetricsUpdateTask] Starting metrics update task
2017-10-19 04:28:38,375 [] INFO [org.owasp.dependencytrack.tasks.MetricsUpdateTask] Executing metrics update on portfolio
2017-10-19 04:28:38,378 [] INFO [org.owasp.dependencycheck.agent.DependencyCheckScanAgent] Populating settings
2017-10-19 04:28:38,599 [] INFO [org.owasp.dependencytrack.tasks.NspMirrorTask] Starting NSP mirroring task
2017-10-19 04:28:38,599 [] INFO [org.owasp.dependencytrack.tasks.NspMirrorTask] Retrieving NSP advisories at Thu Oct 19 04:28:38 EDT 2017
2017-10-19 04:28:38,677 [] INFO [org.owasp.dependencycheck.Engine] Checking for updates
2017-10-19 04:28:38,767 [] INFO [org.owasp.dependencycheck.data.update.NvdCveUpdater] starting getUpdatesNeeded() ...
2017-10-19 04:28:39,063 [] ERROR [org.owasp.dependencycheck.utils.Downloader] IO Exception: Network is unreachable (connect failed)
2017-10-19 04:28:39,078 [] ERROR [org.owasp.dependencycheck.utils.Downloader] IO Exception: Network is unreachable (connect failed)
2017-10-19 04:28:39,079 [] ERROR [org.owasp.dependencycheck.utils.Downloader] IO Exception: Network is unreachable (connect failed)
2017-10-19 04:28:39,089 [] ERROR [org.owasp.dependencycheck.utils.Downloader] IO Exception: Network is unreachable (connect failed)
2017-10-19 04:28:39,094 [] WARN [org.owasp.dependencycheck.data.update.NvdCveUpdater] Unable to download the NVD CVE data; the results may not include the most recent CPE/CVEs from the NVD.
2017-10-19 04:28:39,095 [] INFO [org.owasp.dependencycheck.data.update.NvdCveUpdater] If you are behind a proxy you may need to configure dependency-check to use the proxy.
2017-10-19 04:28:39,095 [] ERROR [org.owasp.dependencycheck.utils.Downloader] IO Exception: Network is unreachable (connect failed)
2017-10-19 04:28:39,099 [] ERROR [org.owasp.dependencycheck.utils.Downloader] IO Exception: Network is unreachable (connect failed)
2017-10-19 04:28:39,103 [] ERROR [org.owasp.dependencycheck.utils.Downloader] IO Exception: Network is unreachable (connect failed)
2017-10-19 04:28:39,118 [] ERROR [org.owasp.dependencycheck.utils.Downloader] IO Exception: Network is unreachable (connect failed)
2017-10-19 04:28:39,121 [] ERROR [org.owasp.dependencycheck.utils.Downloader] IO Exception: Network is unreachable (connect failed)
2017-10-19 04:28:39,123 [] ERROR [org.owasp.dependencycheck.utils.Downloader] IO Exception: Network is unreachable (connect failed)
2017-10-19 04:28:39,132 [] ERROR [org.owasp.dependencytrack.tasks.DependencyCheckTask] An error occurred executing Dependency-Check scan agent: org.owasp.dependencycheck.exception.ScanAgentException: One or more exceptions occurred during analysis; please see the debug log for more details.
2017-10-19 04:28:39,132 [] INFO [org.owasp.dependencytrack.tasks.DependencyCheckTask] Dependency-Check update-only complete
2017-10-19 04:28:39,144 [] ERROR [org.owasp.dependencycheck.utils.Downloader] IO Exception: Network is unreachable (connect failed)
2017-10-19 04:28:39,154 [] ERROR [org.owasp.dependencycheck.utils.Downloader] IO Exception: Network is unreachable (connect failed)
2017-10-19 04:28:39,155 [] ERROR [org.owasp.dependencycheck.utils.Downloader] IO Exception: Network is unreachable (connect failed)
2017-10-19 04:28:39,232 [] INFO [org.owasp.dependencytrack.tasks.NspMirrorTask] Retrieving NSP advisories from https://api.nodesecurity.io/advisories
2017-10-19 04:28:39,281 [] INFO [org.owasp.dependencytrack.tasks.MetricsUpdateTask] Metrics update complete
2017-10-19 04:28:39,695 [] INFO [org.owasp.dependencytrack.tasks.NspMirrorTask] Updating datasource with NSP advisories
2017-10-19 04:28:39,998 [] INFO [org.owasp.dependencytrack.tasks.NspMirrorTask] Retrieving NSP advisories from https://api.nodesecurity.io/advisories
2017-10-19 04:28:40,086 [] INFO [org.owasp.dependencytrack.tasks.NspMirrorTask] Updating datasource with NSP advisories
2017-10-19 04:28:40,241 [] INFO [org.owasp.dependencytrack.tasks.NspMirrorTask] Retrieving NSP advisories from https://api.nodesecurity.io/advisories
2017-10-19 04:28:40,305 [] INFO [org.owasp.dependencytrack.tasks.NspMirrorTask] Updating datasource with NSP advisories
2017-10-19 04:28:40,468 [] INFO [org.owasp.dependencytrack.tasks.NspMirrorTask] Retrieving NSP advisories from https://api.nodesecurity.io/advisories
2017-10-19 04:28:40,535 [] INFO [org.owasp.dependencytrack.tasks.NspMirrorTask] Updating datasource with NSP advisories
2017-10-19 04:28:40,727 [] INFO [org.owasp.dependencytrack.tasks.NspMirrorTask] Retrieving NSP advisories from https://api.nodesecurity.io/advisories
2017-10-19 04:28:40,811 [] INFO [org.owasp.dependencytrack.tasks.NspMirrorTask] Updating datasource with NSP advisories
2017-10-19 04:28:40,956 [] INFO [org.owasp.dependencytrack.tasks.NspMirrorTask] NSP mirroring complete
2017-10-19 04:29:28,376 [] INFO [org.owasp.dependencytrack.tasks.DependencyCheckTask] Executing Dependency-Check analysis task
2017-10-19 04:29:28,377 [] INFO [org.owasp.dependencytrack.tasks.DependencyCheckTask] Analyzing portfolio
2017-10-19 04:29:28,401 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Starting NIST mirroring task
2017-10-19 04:29:28,402 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading files at Thu Oct 19 04:29:28 EDT 2017
2017-10-19 04:29:28,417 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:29:28,418 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://nvd.nist.gov/download/nvdcve-2002.xml.gz
2017-10-19 04:29:28,482 [] INFO [org.owasp.dependencytrack.tasks.DependencyCheckTask] Analyzing 116 component(s)
2017-10-19 04:29:28,484 [] INFO [org.owasp.dependencycheck.agent.DependencyCheckScanAgent] Populating settings
2017-10-19 04:29:28,526 [] ERROR [org.owasp.dependencycheck.Engine] No documents exist
Unable to continue dependency-check analysis.
2017-10-19 04:29:28,535 [] ERROR [org.owasp.dependencycheck.agent.DependencyCheckScanAgent] A fatal exception occurred during analysis; analysis has stopped. Please see the debug log for more details.
2017-10-19 04:29:28,535 [] ERROR [org.owasp.dependencytrack.tasks.DependencyCheckTask] An error occurred executing Dependency-Check scan agent: org.owasp.dependencycheck.exception.ScanAgentException: One or more exceptions occurred during analysis; please see the debug log for more details.
2017-10-19 04:29:28,535 [] INFO [org.owasp.dependencytrack.tasks.DependencyCheckTask] Dependency-Check analysis complete
2017-10-19 04:29:28,536 [] INFO [org.owasp.dependencytrack.tasks.DependencyCheckTask] Processing Dependency-Check analysis results
2017-10-19 04:29:28,676 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:29:28,967 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2002.xml.gz
2017-10-19 04:29:29,174 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:29:29,175 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://nvd.nist.gov/feeds/xml/cve/nvdcve-2.0-2002.xml.gz
2017-10-19 04:29:29,311 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:29:29,695 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2.0-2002.xml.gz
2017-10-19 04:29:29,890 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:29:29,890 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://static.nvd.nist.gov/feeds/json/cve/1.0/nvdcve-1.0-2002.json.gz
2017-10-19 04:29:30,113 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:29:30,526 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-1.0-2002.json.gz
2017-10-19 04:29:30,637 [] INFO [org.owasp.dependencytrack.parser.nvd.NvdParser] Parsing nvdcve-1.0-2002.json
2017-10-19 04:29:37,973 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:29:37,973 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://nvd.nist.gov/download/nvdcve-2003.xml.gz
2017-10-19 04:29:38,091 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:29:38,209 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2003.xml.gz
2017-10-19 04:29:38,228 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:29:38,229 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://nvd.nist.gov/feeds/xml/cve/nvdcve-2.0-2003.xml.gz
2017-10-19 04:29:38,347 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:29:38,468 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2.0-2003.xml.gz
2017-10-19 04:29:38,503 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:29:38,503 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://static.nvd.nist.gov/feeds/json/cve/1.0/nvdcve-1.0-2003.json.gz
2017-10-19 04:29:38,637 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:29:38,758 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-1.0-2003.json.gz
2017-10-19 04:29:38,791 [] INFO [org.owasp.dependencytrack.parser.nvd.NvdParser] Parsing nvdcve-1.0-2003.json
2017-10-19 04:29:40,537 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:29:40,537 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://nvd.nist.gov/download/nvdcve-2004.xml.gz
2017-10-19 04:29:40,682 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:29:40,847 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2004.xml.gz
2017-10-19 04:29:40,884 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:29:40,884 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://nvd.nist.gov/feeds/xml/cve/nvdcve-2.0-2004.xml.gz
2017-10-19 04:29:41,007 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:29:41,279 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2.0-2004.xml.gz
2017-10-19 04:29:41,340 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:29:41,340 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://static.nvd.nist.gov/feeds/json/cve/1.0/nvdcve-1.0-2004.json.gz
2017-10-19 04:29:41,459 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:29:41,691 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-1.0-2004.json.gz
2017-10-19 04:29:41,763 [] INFO [org.owasp.dependencytrack.parser.nvd.NvdParser] Parsing nvdcve-1.0-2004.json
2017-10-19 04:29:44,448 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:29:44,448 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://nvd.nist.gov/download/nvdcve-2005.xml.gz
2017-10-19 04:29:45,573 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:29:45,836 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2005.xml.gz
2017-10-19 04:29:45,887 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:29:45,887 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://nvd.nist.gov/feeds/xml/cve/nvdcve-2.0-2005.xml.gz
2017-10-19 04:29:45,984 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:29:46,364 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2.0-2005.xml.gz
2017-10-19 04:29:46,458 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:29:46,461 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://static.nvd.nist.gov/feeds/json/cve/1.0/nvdcve-1.0-2005.json.gz
2017-10-19 04:29:46,559 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:29:46,913 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-1.0-2005.json.gz
2017-10-19 04:29:47,010 [] INFO [org.owasp.dependencytrack.parser.nvd.NvdParser] Parsing nvdcve-1.0-2005.json
2017-10-19 04:29:51,178 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:29:51,179 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://nvd.nist.gov/download/nvdcve-2006.xml.gz
2017-10-19 04:29:51,293 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:29:51,708 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2006.xml.gz
2017-10-19 04:29:51,790 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:29:51,791 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://nvd.nist.gov/feeds/xml/cve/nvdcve-2.0-2006.xml.gz
2017-10-19 04:29:51,924 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:29:52,497 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2.0-2006.xml.gz
2017-10-19 04:29:52,638 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:29:52,640 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://static.nvd.nist.gov/feeds/json/cve/1.0/nvdcve-1.0-2006.json.gz
2017-10-19 04:29:52,759 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:29:53,385 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-1.0-2006.json.gz
2017-10-19 04:29:53,529 [] INFO [org.owasp.dependencytrack.parser.nvd.NvdParser] Parsing nvdcve-1.0-2006.json
2017-10-19 04:30:07,041 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:30:07,041 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://nvd.nist.gov/download/nvdcve-2007.xml.gz
2017-10-19 04:30:07,259 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:30:07,698 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2007.xml.gz
2017-10-19 04:30:07,778 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:30:07,778 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://nvd.nist.gov/feeds/xml/cve/nvdcve-2.0-2007.xml.gz
2017-10-19 04:30:07,891 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:30:08,404 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2.0-2007.xml.gz
2017-10-19 04:30:08,537 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:30:08,537 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://static.nvd.nist.gov/feeds/json/cve/1.0/nvdcve-1.0-2007.json.gz
2017-10-19 04:30:08,743 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:30:09,302 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-1.0-2007.json.gz
2017-10-19 04:30:09,443 [] INFO [org.owasp.dependencytrack.parser.nvd.NvdParser] Parsing nvdcve-1.0-2007.json
2017-10-19 04:30:17,139 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:30:17,139 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://nvd.nist.gov/download/nvdcve-2008.xml.gz
2017-10-19 04:30:17,255 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:30:17,693 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2008.xml.gz
2017-10-19 04:30:17,775 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:30:17,776 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://nvd.nist.gov/feeds/xml/cve/nvdcve-2.0-2008.xml.gz
2017-10-19 04:30:17,920 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:30:18,550 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2.0-2008.xml.gz
2017-10-19 04:30:18,703 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:30:18,703 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://static.nvd.nist.gov/feeds/json/cve/1.0/nvdcve-1.0-2008.json.gz
2017-10-19 04:30:18,820 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:30:19,515 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-1.0-2008.json.gz
2017-10-19 04:30:19,686 [] INFO [org.owasp.dependencytrack.parser.nvd.NvdParser] Parsing nvdcve-1.0-2008.json
2017-10-19 04:30:27,166 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:30:27,167 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://nvd.nist.gov/download/nvdcve-2009.xml.gz
2017-10-19 04:30:27,292 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:30:27,643 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2009.xml.gz
2017-10-19 04:30:27,713 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:30:27,713 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://nvd.nist.gov/feeds/xml/cve/nvdcve-2.0-2009.xml.gz
2017-10-19 04:30:27,852 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:30:28,454 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2.0-2009.xml.gz
2017-10-19 04:30:28,610 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:30:28,610 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://static.nvd.nist.gov/feeds/json/cve/1.0/nvdcve-1.0-2009.json.gz
2017-10-19 04:30:28,729 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:30:29,514 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-1.0-2009.json.gz
2017-10-19 04:30:29,713 [] INFO [org.owasp.dependencytrack.parser.nvd.NvdParser] Parsing nvdcve-1.0-2009.json
2017-10-19 04:30:35,128 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:30:35,128 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://nvd.nist.gov/download/nvdcve-2010.xml.gz
2017-10-19 04:30:35,247 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:30:35,637 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2010.xml.gz
2017-10-19 04:30:35,724 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:30:35,724 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://nvd.nist.gov/feeds/xml/cve/nvdcve-2.0-2010.xml.gz
2017-10-19 04:30:35,838 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:30:36,662 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2.0-2010.xml.gz
2017-10-19 04:30:36,886 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:30:36,886 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://static.nvd.nist.gov/feeds/json/cve/1.0/nvdcve-1.0-2010.json.gz
2017-10-19 04:30:37,035 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:30:38,040 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-1.0-2010.json.gz
2017-10-19 04:30:38,350 [] INFO [org.owasp.dependencytrack.parser.nvd.NvdParser] Parsing nvdcve-1.0-2010.json
2017-10-19 04:30:45,522 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:30:45,522 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://nvd.nist.gov/download/nvdcve-2011.xml.gz
2017-10-19 04:30:45,623 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:30:46,573 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2011.xml.gz
2017-10-19 04:30:46,745 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:30:46,746 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://nvd.nist.gov/feeds/xml/cve/nvdcve-2.0-2011.xml.gz
2017-10-19 04:30:46,870 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:30:48,648 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-2.0-2011.xml.gz
2017-10-19 04:30:49,195 [] ERROR [org.owasp.dependencytrack.tasks.NistMirrorTask] Failed to determine content length
2017-10-19 04:30:49,195 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Initiating download of https://static.nvd.nist.gov/feeds/json/cve/1.0/nvdcve-1.0-2011.json.gz
2017-10-19 04:30:49,339 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Downloading...
2017-10-19 04:30:52,019 [] INFO [org.owasp.dependencytrack.tasks.NistMirrorTask] Uncompressing nvdcve-1.0-2011.json.gz
2017-10-19 04:30:52,870 [] INFO [org.owasp.dependencytrack.parser.nvd.NvdParser] Parsing nvdcve-1.0-2011.json
2017-10-19 04:31:54,455 [] INFO [alpine.AlpineServlet] Starting Dependency-Track

I changed the log level to DEBUG in logback.xml & added my proxy.url & proxy.port in dependency-check-core-2.1.2-SNAPSHOT.jar; there's nothing really extra though, hope you can find something.
dependency-track.log

Note - I modified the code to run from 2002 to 2010 first & then redeployed with downloads going from 2011 to 2017; doing this 2002 to 2010 are cached & all the *.gz are downloaded.

authors: adunkey stevespringett

repo: stevespringett/dependency-track


text:
Progress bar and progress % do not match - how is the math done?

Hello,
I love this plugin but I need to be able to show my clients that it makes sense.
I often see project that show the bar 1/2 way across but the percent complete says 0%.
I've tried to fnd the documentation that explains how you calculate the % complete but I can not find anything.
I would gladly help update the documentation to explain the process or show how the % complete is calculated if you can tell me.
Thanks

@Saylrman64 please read comments for #10. Seems it should explain you how these progress bars work. Let me know if you still have any questions.
Thanks for loving my plugin :)

I did and it helps.
Still some strange math.
Thank you!

source: gharchive/issue

license: mit

license_type: permissive

license_source: bigquery


text:
Handle circumstance during discovery where device.name is None

While running discovery I noticed that bleak can report devices whose device.name is None, which trips up this bit of the _discover() logic.

Aha...I think @bede 's PR includes a commit which fixes this!
I'll leave this PR open since the other includes several other changes (not sure if it's easier to land this one more quickly?), but if not I'm happy to close this out.

Thanks!

source: gharchive/pull-request

authors: jeffmo stijnstijn

license: MIT

license_source: github-api


text:
H745, 747 RCC regs incorrect

See RM0399, Table 87. RCC register map and reset values, and the values generated: https://github.com/stm32-rs/stm32-rs-nightlies/blob/master/stm32h7/src/stm32h747cm7/rcc.rs
Of note, the generated PAC values are the same as for H742 and 743. These are mostly the same, but with some differences near the top. Specifically, ICSCR, and HSICFGR. It's possible others are incorrect that I haven't noticed.

Hmm. The plot thickens. This may be due to Revision V on the H745. Maybe we need a Revision V in the PAC, as is done for H743?


text:
cluster-proxy-addon migration to MCE

Signed-off-by: Erin Murphy erinmurp@redhat.com
Issue: https://github.com/stolostron/backlog/issues/23518

RBAC validation check failing because resource route.openshift.io/Route not accounted for in RBAC generation. Since this PR introduced several new resources they will need to be accounted for in our rbac generator.

I opened https://github.com/eemurphy/backplane-operator/pull/1 to update rbac

@eemurphy After hacking around the missing image I see two deployments installed: cluster-proxy-addon-manager and cluster-proxy-addon-user, which looks right but the status does not.
    - kind: Component
      lastTransitionTime: "2022-07-13T18:13:02Z"
      message: No resources present
      name: cluster-proxy-addon-manager
      reason: ComponentDisabled
      status: "True"
      type: NotPresent
    - kind: Component
      lastTransitionTime: "2022-07-13T18:13:02Z"
      message: No resources present
      name: cluster-proxy-addon-user
      reason: ComponentDisabled
      status: "True"
      type: NotPresent

Due to the conflict I rebased this off main and it had a lot more conflicts to go through so I opened a new PR with my branch https://github.com/stolostron/backplane-operator/pull/238

authors: JakobGray eemurphy

repo: stolostron/backplane-operator


text:
Enable translation pruning

https://github.com/stolostron/backlog/issues/23473
Signed-off-by: Kevin Cormier kcormier@redhat.com

/cc @RobDolares

repo: stolostron/console


text:
Update golang to 1.17.9, add 1.18

Just builder things

/lgtm

authors: arewm schmidtd

repo: stolostron/image-builder


text:
update crypto (2.3)

Signed-off-by: Wei Liu liuweixa@redhat.com

refer to https://github.com/stolostron/backlog/issues/18857

/lgtm


text:
*: Refactor codebase with linters/formatters and upstream patterns

Lots of TODOs still pending (that will be done in separate PRs), but this does the following.

Bump prom client, and add rules to use similar upstream patterns for instrumentation
Deprecate ioutil
Make all errors consistent and move completely to github.com/efficientgo/core/errors
Add bingo and several linters/formatters
Deprecate fake.NewClient
Fix a bunch of lint problems (although many still exist within tests)

/retest tests-unit

/test test-unit

/retest

Errors

I would avoid adding the new error package

I understand the reason for the new error package and not wanting to depend on small package, but there are a few of reasons, why I think it is generally better than combination of stdlib fmt.Errorf and errors.New,

Wrapping errors with fmt.Errorf needs a %w which is super easy to forget to do, and easy to miss in review. I think we can construct some linter rule for it using some custom lint tools (faillint, golangci-lint don't do this I think), but that's extra check to maintain. Due to the nature of such a single arg function, it is prone to inconsistent wrapping.
Relying on errors.New for new errors and then fmt.Errorf for wrapping doesn't look clean, and increases cognitive load.  I'd rather prefer using single package consistently for everything.

Regarding the stack trace, I don't see why we would need it. I mean, if so, it is a symptom of bad error handling that is not descriptive enough in the stack.
I don't like depending on those small libs while the stdlib does the job.

I get what you're saying about non-descriptive errors @thibaultmg, but I'd argue stack traces aren't exactly to describe the error or "cause" of the error, but rather to highlight the specific code path that the error resulted from, which is extremely useful when debugging issues with complex codebases like this one. And stacktraces are useful enough that people even created o11y signal from it i.e profiling. I'd rather have stacktraces and not use it, rather than not have stacktraces but need it. 😅 Wdyt?

And if anything, we maintain efficientgo/core, so there isn't much worry about governance.
Bingo

and bingo

Curious about this, why do we want to avoid bingo? Is it the extra files or something else you noticed @thibaultmg?
Logging
Also, I have an outstanding question apart from errors, which is logging. Seems like this repo uses go-kit/log (which we use upstream quite a lot in Prometheus and Thanos), and klog which is the standard k8s logger, quite a lot. Also, Kubebuilder-based operators usually use zapr which is what obo uses. I'd like to move to one consistent logger. What do you think we should use here then? My personal pick would be go-kit/log as we can do multiple formats and filter via log level, and it's the one current team is most familiar with. But what do you think @thibaultmg @philipgough? 🙂

/retest

On error handling, I heavily agree with @thibaultmg's point.

I do not think adding a %w is easy to forget and miss in review. In fact, it becomes instinct after a few uses. Some of us in the team might see it as easy to forget only because we lack experience with the standard library's error wrapping. It's a matter of getting acquainted with the habit (less things to keep inside our heads = cognitive_load--).
I don't think fmt.Errorf implies in extra cognitive load -- where would such load come from? It might not look clean for some, which is fair, but not a good reason to rely on a 3rd party library. In fact, we are better off using the Golang's standard library way, which can be improved over time. The Go team will take care of the backwards compatibility and migration for us.
Extra: by using the official error wrapping of Go, in the future we might get stacktraces for free and won't need a 3rd party package for this. To me it's fine to use a 3rd party package for stacktraces if they prove helpful. More than once I already caught myself with a stacktrace that didn't help me pinpoint the issue.

On Bingo, I also agree with @thibaultmg's point.

It's not about "why avoid Bingo?" it's about "why use Bingo if go install is enough"? Bingo comes from a time where go install didn't exist. Nowadays we have a proper solution from the Go team which they will evolve over time together with all the rest of the toolchain. It's much more likely that a Go developer already knows go install (less things to keep inside our heads = cognitive_load--) than Bingo.
It's not only about how many files Bingo adds to the project, but also how much maintenance is required to upgrade tooling (more things to keep inside our heads = cognitive_load++). Meanwhile, go install is just a few lines in a README, Makefile or Shell script -- to upgrade something I change the version number and that's all. Also note that the commands in Bingo and go install have slightly different syntax sometimes (more things to keep inside our heads = cognitive_load++).

Overall, my opinion is: I like to stick with the standard library whenever possible. We should all be very familiar with it. When not possible, let's look for tools that are "de-facto" standards in the community. There are many good reasons for this, including but not limited to:

By using the standard library and "de-facto" standard packages, we reduce onboarding time and cost of codebase because we will be using constructs that are familiar to every Go developer (less things to keep inside our heads = cognitive_load--). On the maintainership side, we don't have to create and maintain a package for this. The less code we have to maintain (less things to keep inside our heads = cognitive_load--), the more we can focus on what matters most.
We see that the standard library is constantly evolving, getting new features and incorporating feedback from people using it. The Go team has been doing a great job at this and keeping backwards compatibility. It's a bad idea to lock ourselves out of it or push the responsibility of adopting updates to the standard library to someone else.

Hey,

Relying on errors.New for new errors and then fmt.Errorf for wrapping doesn't look clean, and increases cognitive load. I'd rather prefer using single package consistently for everything.

I think it is more of a matter of what tools you are used to. Because for me, it is this errors.Wrap that increases the cognitive load. I have to check the package to understand why it's there.
Regarding the stack trace, this can be added when debugging with 3 lines of code. And it happens rarely. So adding a specific dependency for that doesn't seem worth it to me.

Curious about this, why do we want to avoid bingo? Is it the extra files or something else you noticed

I admit it brings useful things to the table. But I don't think we need it enough to not use go install. We could isolate these dev bins in a .bin dir in the package and have all tools consume these deps from here. The other useful things is the ability to selectively add deps. We could have one make target by dep. To me there are few things that bingo brings that cannot be done with standard tooling plus some small conventions.

Also, I have an outstanding question apart from errors, which is logging.

I don't have strong opinions on this. In my personal projects I use zerolog which I like. With go 1.21 I would give a shot to slog from the standard lib.
Overall I totally agree with @douglascamata remarks about the benefits of using the standard lib as much as possible. This is what I strive for in my projects. But again, It is not a blocker if the majority of the team enjoys these tools 😉

Bingo is not a blocker. You have already integrated it, let's go with that. After, I don't think anybody will spend time changing it just for the sake of removing it.
Still good to remove the errors package 😄 .

That being said, I also do not feel strongly about blocking any alternatives to bingo in the context of this repo. So @thibaultmg / @douglascamata if you feel like bingo is causing you more difficulties or is hindering you in any way, please feel free to raise a follow-up to this PR with an alternative. 🙂

It's not about difficulties of Bingo. As I said before, it's more about using a non-standard tool when a standard one that can achieve the same things already exists. Bingo is far from a standard tool -- besides Thanos and grpc-middleware, only some other Red Hat projects are using it. Everyone else out there has figured how to live without it and it's not difficult. We can achieve with go install everything that Bingo does and the only "manual work" will be to add a variable in a Makefile (done once per lifetime of the project, not a burden at all).
Not a blocker for me too.

/retest test-unit

/test test-unit

authors: douglascamata saswatamcode thibaultmg


text:
Fix: fix etcd and apiserver dashboards for hypershift and more

Service monitors scraping etcd and apiserver jobs for hosted clusters were missing some metrics for their respective specialized dashboards.
I am also fixing missing data for other cases, as well as fixing some bugs in the etcd dashboard.
https://issues.redhat.com/browse/ACM-13524

/retest


text:
Upgrade client-go to v0.27.2 and controller-runtime to v0.15.0

Signed-off-by: myan myan@redhat.com

Blocked by https://github.com/stolostron/backplane-operator/pull/493
# github.com/stolostron/backplane-operator/api/v1
vendor/github.com/stolostron/backplane-operator/api/v1/multiclusterengine_webhook.go:102:27: cannot use &MultiClusterEngine{} (value of type *MultiClusterEngine) as admission.Validator value in variable declaration: *MultiClusterEngine does not implement admission.Validator (wrong type for method ValidateCreate)
                have ValidateCreate() error
                want ValidateCreate() (admission.Warnings, error)
make: *** [Makefile:93: vet] Error 1

ref: https://github.com/stolostron/multicluster-global-hub/pull/600

/lgtm

/override ci/prow/sonar-pre-submit "SonarCloud Code Analysis"
Overriding to unblock the PR. We will aim to increase the code-coverage within a separate PR.

authors: dislbenn yanmxa

repo: stolostron/multiclusterhub-operator


text:
Rebuild images for CVE updates

Signed-off-by: Stephen Kitt skitt@redhat.com

@tpantelis why did you close this?

repo: stolostron/submariner-addon


text:
Confused? Where to put chrome folder in?

Ok,
Is this path the correct location for chrome folder to be in?
C:\Users\Xelbayria\AppData\Roaming\Mozilla\Firefox\Profiles\chrome
or was it
C:\Users\Xelbayria\AppData\Roaming\Mozilla\Firefox\Profiles\default-folder\chrome
it seems to not working for me. I've followed the instructions. What am I missing?

Oh right, Thanks for close this issue and your answer is correct. It's working as it is intended. Thanks for correcting my approaches.  Take care!

repo: stonecrusher/simpleMenuWizard


text:
fix(elements-core): response tab overflow

Elements Default PR Template
Addresses #2260
This dose touch the section component effecting more than just the response tabs. I think the breaking of children to fall below the heading is an overall good UI change

[ ] Read CONTRIBUTING.md

Other Available PR Templates:

Release: https://github.com/stoplightio/elements/compare?template=release.md

[ ] Read the release section of CONTRIBUTING.md

@porotki How about this approach instead?
There is an open issue in Mosaic for horizontal tab scroll  which would be the best fix but I thought this looked/worked a little better.
https://user-images.githubusercontent.com/2607104/195891295-9b440fe2-863c-4630-b58c-6d30bf7d69e4.mov

Yeah, that's great, thank you. I'm gonna close #2260

Yeah, that's great, thank you. I'm gonna close #2260

Great, next release should include this change.

authors: Amjcraft porotkin

repo: stoplightio/elements


text:
Remove react-typescript-docgen-loader from preset-typescript

What I did
Removed all instances of react-typescript-docgen-loader from preset-typescript per https://github.com/storybookjs/storybook/issues/8337 since preset-typescript should be for all frameworks, not just react.
Incremented major version change
There's an accompanying PR that adds it to addon-docs: https://github.com/storybookjs/storybook/pull/8984

Looks great!

@patricklafrance I'll merge & release once storybookjs/storybook#8984 is ready

@shilman 👍

@shilman can we get this merged? I'm working on an easier vue+ts setup and this is would help simplify things.

authors: graup mrmckeb patricklafrance shilman

repo: storybookjs/presets


text:
Format the full error message before passing it to the Error class

Closes #

What I did
Allows formatting of error messages that are spit out during tests by passing a function to the test runner config , sometimes they are incredibly long and impossible to figure out why a test failed.
https://github.com/storybookjs/storybook/discussions/25131

Checklist for Contributors
Manual testing
This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!
Documentation

[ ] Add or update documentation reflecting your changes in this repository
[ ] Request documentation updates in the test-runner docs website

Checklist for Maintainers

[ ] Make sure this PR contains one of the labels below:

Available labels

skip-release: Skip any releases, e.g., documentation only changes, CI config etc.
patch: Upgrade patch version (e.g. 0.0.x)
minor: Upgrade patch version (e.g. 0.x.0)
major: Upgrade patch version (e.g. x.0.0)

@yannbf I couldn't push to your branch so had to create a sep PR

Hey @Foxhoundn thanks for providing the code! I think we need to think a bit more about this since it should be a common function for errors, and right now it seems to be applied only if an exception is coming from the play function.
@kasperpeulen @shilman do you want to chime in regarding:

functionality/behavior
API
naming

Hey @Foxhoundn thanks for providing the code! I think we need to think a bit more about this since it should be a common function for errors, and right now it seems to be applied only if an exception is coming from the play function.
@kasperpeulen @shilman do you want to chime in regarding:

functionality/behavior
API
naming

I would say this function should be applicable to other error events too, and receive as second argument some metadata (whenever possible) that contains at least the storyId, so users have more flexibility to know how to deal with formatting their messages.

That would be splendid - I would love to have a list of stories that failed at the end of the test run too, right now it just says 5 test suites, 25 tests. Then you have to scroll through the whole history to find those 25 tests, but it would be wonderful to have the actual story list there, for easy orientation. Something to think about?

authors: Foxhoundn yannbf

repo: storybookjs/test-runner


text:
Type of withKnobs

Describe the bug
The type of withKnobs is not valid for the addDecorator function. Looks like the @types/storybook_addon-knobs is out of date maybe?
To Reproduce
Using the following relevant libraries:
    "@babel/core": "^7.2.2",
    "@storybook/addon-knobs": "^4.1.13",
    "@storybook/vue": "^4.1.11",
    "@types/node": "^11.9.4",
    "@types/react": "^16.8.4",
    "@types/storybook__addon-knobs": "^4.0.1",
    "@types/storybook__vue": "^3.3.2",
    "babel-core": "^6.26.3",
    "babel-loader": "^8.0.5",
    "babel-preset-vue": "^2.0.2",
    "ts-loader": "^5.3.3",
    "typescript": "^3.3.3",
    "vue-template-compiler": "^2.6.6",
    "vue": "^2.6.6"

Not exactly sure the @types/react is needed, but it's part of the docs for using knobs with TypeScript.
Component.stories.ts
import { storiesOf, Story } from '@storybook/vue'
import { withKnobs, text } from '@storybook/addon-knobs'
import MyComponent from './MyComponent.vue'

const stories: Story = storiesOf('MyComponent.vue', module)

// This throws a type checking error
stories.addDecorator(withKnobs)

// This compiles and works as expected
stories.addDecorator(<any>withKnobs)

stories.add('as component', () => ({
  components: { MyComponent },
  props: {
    text: {
      default: text('Text', 'some text')
    }
  },
  template: '<my-component></my-component>'
})

System:

OS: Windows10
Device: Toshiba Satellite
Browser: N/A
Framework: Vue
Addons: knobs
Knobs Version: 4.1.13
Knobs Types Version: 4.0.1 (This is latest)
Storybook Version: 4.1.11

Additional context
This isn't a huge deal, just a minor annoyance as I cringe any time I have to use the any type.

Thanks for the bug! Unfortunately, we don't maintain the types on DefinitelyTyped and I'm not sure about what's the procedure for getting those updated.
The good news is that we're in the process of converting our codebase into Typescript, so you should be seeing those types defined "in house" in an upcoming release. You can check the progress and contribute yourself here: https://github.com/storybooks/storybook/issues/5030
Closing this for now! 🙇

Awesome, that will be great! Thanks @shilman

authors: Jack-Barry shilman

repo: storybooks/storybook


text:
Have Integration-Tests

with Testcontainers

see https://github.com/stphngrtz/project-konphite/pull/25

repo: stphngrtz/project-konphite


text:
Make dom nodes public

For interactive components like Button I created a mirrored HTML node and added it to the DOM in order to support screen readers and get keyboard navigation. I added them as private _dn properties but I should make them public properties as wanting to move the DOM nodes around when using them is necessary when making accessible higher order components (like a dialog).

Example of manually moving node:
const button = kontra.Button({
  x: 10,
  y: 20,
  text: {
    text: 'Hello World'
  }
});
const grid = document.createElement('div');
grid.setAttribute('role', 'grid');
grid.innerHTML = `

`;
document.body.appendChild(grid);
grid.querySelector('[role="gridcell"]').appendChild(button._dn);

repo: straker/kontra


text:
Cosmos SDK v0.47

Continuation of https://github.com/strangelove-ventures/ibctest/pull/337
Working branch for update to SDK v0.47

regarding the failure for the TestCosmosChain_BroadcastTx, I just checked out main, and changed the broadcast mode here to broadcast sync, and it failed. This implies that the current broadcasting code fails with BroadcastSync and these changes may not be breaking something that wasn't already failing.
cc @agouin

I opened a pr on the go relayer to bump to v0.47, unsure if it is related to issues faced here, but it seems the tests cannot get past ConnectionOpenInit. Hopefully those tests can help with debugging the remaining issues

I think we found the issue @agouin, in our genesis modification function,  we create a genesis doc object. The fields have changed in this type and so we are overwriting the genesis file that was created by ibctest with a new unknown format for chains using an older sdk.

Hi @agouin, I tested this branch with out newly updated 0.47 chain and I think there is an issue with some of the genesis commands that have been moved if you use the new genutil setup (which we do) from this: https://github.com/cosmos/cosmos-sdk/pull/14149
Meaning, things like add-genesis-account fails because it is now under genesis add-genesis-account.

I hacked a solution for myself to get past this blocker here: https://github.com/gjermundgaraba/ibctest/commit/28412748e293eec207f43c31d06248c7e266b905
Probably not a good way to solve this problem, but if anyone finds it useful 🤷

This seems like a good first step in making this possible. We can revisit to try and add a detection mechanism in a follow up issue. Would you like to open a PR with your change?

Another issue which I think is a blocker for me is the relayer itself which seems to be very unsupportive of either the SDK version or tendermint version I think. Just a heads up if anyone else finds this issue :)

https://github.com/cosmos/relayer/pull/1068 this branch should unblock you with the relayer. It has a detection mechanism for the tendermint version so it can relay before/after v0.37

@agouin I opened a PR against the v0.47 for this change. If you prefer I can try to move the changes to main and open the PR against it instead.

There was an issue with the broadcast messages functionality, I created a fix for it here #388

Hi, just curious what the status of this pr is? Is there more work to be done to get it merged or is it waiting on a final SDK version? Thanks :)

Hi, just curious what the status of this pr is? Is there more work to be done to get it merged or is it waiting on a final SDK version? Thanks :)

We are preparing to merge this to main asap. Remaining items are to rebase this on top of main's latest changes, branch v6, then this can be merged.

Just wanted to say thank you to everyone who worked on this! Being able to run e2e's has been a big improvement for us, so we really appreciate all maintence that goes into maintaining interchaintest :pray:

authors: agouin chatton colin-axner gjermundgaraba

repo: strangelove-ventures/ibctest


text:
Lucene hard limit on number of docs

Lucene is having a hard limit on number of docs.
So in Elassandra, will the doc limit be per partition or per node.
Example: If I enable num_tokens:64, Does it imply each 64 partitions will have 2billion limit (1st partition= 2B values, 2nd Partition=2B values etc)
or
that node will have a total limit of 2B values regardless of number of partitions.
Thanks

Hi,
Lucene hard limit is per index shard.
By default, Elassandra has one shard per index and per node (not per cassandra partition).
You can override this limit by partitioning your index (see http://doc.elassandra.io/en/latest/mapping.html#partitioned-index ), split the index shard into 2 or more shards on each shards.
In cassandra, num_token is not a number of tokens, but a number of token ranges per nodes.
For example, with 3 nodes and num_token=8,  the 2^128 ring is divided into 24 token ranges, and each node have 8 token ranges.

Le 13 févr. 2019 à 21:52, dbapramod882 notifications@github.com a écrit :
Lucene is having a hard limit on number of docs.
So in Elassandra, will the doc limit be per partition or per node.
Example: If I enable num_tokens:64, Does it imply each 64 partitions will have 2billion limit (1st partition= 2B values, 2nd Partition=2B values etc)
or
that node will have a total limit of 2B values regardless of number of partitions.
Thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/strapdata/elassandra/issues/267, or mute the thread https://github.com/notifications/unsubscribe-auth/AJzHmVisykU92G-8LuCopthYyJSWyWxEks5vNHsRgaJpZM4a6QD2.

repo: strapdata/elassandra


text:
Don't copy NLog.config on every build

Don't copy NLog.config on every build, that overrides custom nlog configs sometimes which is really annoying during debugging

fixed

repo: stratisproject/StratisBitcoinFullNode


text:
token swap is not working

Stratis Core 2.1.1
Something went wrong
Not enough funds to cover the target with missing amount
0.00000110

if it is really impossible to calculate fees you should maybe let the people edit the amount of tokens to swap

and it is not great to be forced to swap if this is not working

Hi, please update to v2.2.1 where this issue has been resolved: https://github.com/stratisproject/StratisCore/releases/tag/2.2.1.0

hello dev0tion, I tried Version 2.2.0 before 2.1.1 and this did not work either, due to some "bitcoin" error, but now I could burn my stratis token.
Thank you very much

repo: stratisproject/StratisCore


text:
Add information on required mapping of /

What can we improve?
In chapter 5, the book talks about deploying a Spring Boot app using CDK and uses the authors' Todo app as a sample.  I wanted to try this but use my own app in place of the Todo app.  So I replaced the URL to the docker image and tried to build / deploy.
It look me a long time to discover that the load balancing service periodically checks the health of the deployed app by accessing the URL /, and that if this fails enough times, the deployment fails.  My app didn't have a mapping for this URL.  Once I added it, deployment was smooth.
Version
1.12
Suggested Changes
Add a note about the requirement for the root URL to be mapped by the application being deployed.  This probably also belongs in the chapter 1 example that uses CloudFormation directly as well.

Thanks for this finding, we'll adjust the book 👍

That's indeed not optimal, what I would suggest is to map the health check to the Actuator endpoint (/actuator/health or info) to have it consistent across all apps.

authors: rieckpil ryanmcfall

repo: stratospheric-dev/stratospheric


text:
Use action from docker to make it faster

Continuation of #1091, this makes the action a bit faster as it uses the image from docker hub instead of building it all the time :)

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

This is a test 🍓🍓

repo: strawberry-graphql/strawberry


text:
make change picture

the picture is https don't cache and my network is slowly so the picture don't show
so can make the picture uploading from my PC , and the information from the network

Not sure what you are saying - caching should be enabled with or without https, see screenshot:

What exactly do you wish to improve?

repo: streamaserver/streama


text:
🛑 EAM Cencosud is down

In 1dbb56b, EAM Cencosud (https://eam.cencosud.com/web/base/logindisp?tenant=SCSPROD) was down:

HTTP code: 502
Response time: 188 ms

Resolved: EAM Cencosud is back up in 0109ced after 8 minutes.

repo: streamlined-scs/upptime


text:
[BUG] ClassNotFoundException: io.streamnative.pulsar.handlers.amqp.authentication.AuthenticationProviderBasic

Describe the bug
I am trying to configure Basic AMQP authentication using apachepulsar/pulsar
Docker image + AoP. I can successfully install the protocol handler. When I register the io.streamnative.pulsar.handlers.amqp.authentication.AuthenticationProviderBasic provider in the standalone.conf authenticationProviders=org.apache.pulsar.broker.authentication.AuthenticationProviderBasic,io.streamnative.pulsar.handlers.amqp.authentication.AuthenticationProviderBasic I get a ClassNotFoundException :
2023-03-23T16:15:58,773+0000 [main] ERROR org.apache.pulsar.broker.PulsarService - Failed to start Pulsar service: Failed to load an authentication provider.
org.apache.pulsar.broker.PulsarServerException: Failed to load an authentication provider.
       at org.apache.pulsar.broker.authentication.AuthenticationService.<init>(AuthenticationService.java:81) ~[org.apache.pulsar-pulsar-broker-common-2.11.0.jar:2.11.0]
       at org.apache.pulsar.broker.service.BrokerService.<init>(BrokerService.java:348) ~[org.apache.pulsar-pulsar-broker-2.11.0.jar:2.11.0]
       at org.apache.pulsar.broker.PulsarService.newBrokerService(PulsarService.java:1839) ~[org.apache.pulsar-pulsar-broker-2.11.0.jar:2.11.0]
       at org.apache.pulsar.broker.PulsarService.start(PulsarService.java:756) ~[org.apache.pulsar-pulsar-broker-2.11.0.jar:2.11.0]
       at org.apache.pulsar.PulsarStandalone.start(PulsarStandalone.java:348) ~[org.apache.pulsar-pulsar-broker-2.11.0.jar:2.11.0]
       at org.apache.pulsar.PulsarStandaloneStarter.main(PulsarStandaloneStarter.java:141) ~[org.apache.pulsar-pulsar-broker-2.11.0.jar:2.11.0]
Caused by: java.lang.ClassNotFoundException: io.streamnative.pulsar.handlers.amqp.authentication.AuthenticationProviderBasic
       at jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641) ~[?:?]
       at jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188) ~[?:?]
       at java.lang.ClassLoader.loadClass(ClassLoader.java:520) ~[?:?]
       at java.lang.Class.forName0(Native Method) ~[?:?]
       at java.lang.Class.forName(Class.java:375) ~[?:?]
       at org.apache.pulsar.broker.authentication.AuthenticationService.<init>(AuthenticationService.java:57) ~[org.apache.pulsar-pulsar-broker-common-2.11.0.jar:2.11.0]
       ... 5 more

What am I doing wrong ?
To Reproduce
Steps to reproduce the behavior:

Write a Dockerfile to install the AoP NAR file in the apachepulsar/pulsar image
Add io.streamnative.pulsar.handlers.amqp.authentication.AuthenticationProviderBasic to the authenticationProviders parameter in the standalone.conf file.
Run the image with the command bin/pulsar standalone
Look for the error in the logs.

Expected behavior
The basic authentication provider for AMQP should register successfully.
Additional context
Using Pulsar 2.11.0 and AoP 2.11.0.3

Note that the result is the same when I use the streamnative/sn-pulsar:2.10.3.6 image instead of building a custom image with only the AoP plugin.

Well, I finally noticed that the io.streamnative.pulsar.handlers.amqp.authentication.AuthenticationProviderBasic class is not included in the NAR, hence the issue.

repo: streamnative/aop


text:
Adjust maven dependencies

Motivation
Recently, we have upgraded log4j2 version, but find that MoP relies on log4j independently.
For MoP relies on Pulsar, and Pulsar even has the log4j dependency.
We need to check if we can remove log4j2 from MoP.
Furthermore, some other dependencies.

paste a link:

relative link : https://github.com/advisories/GHSA-fp5r-v3w9-4333

authors: Technoboy- mattisonchao

repo: streamnative/mop


text:
[Feature] support for source code build in docker

Signed-off-by: Qi Zhang smallqi1@163.com
What to solve?
StreamX is currently started using docker-compose, But this also relies on the user's local env for compilation. This can be time-consuming when users just want to install and experience StreamX.
So, I provide Streamx images, This will make things easier for the user.
It support source code compilation in Docker, No longer rely on the local Java and maven environment.
what is provided?
Support for compilation detached mode and mixed mode in docker.
docker in docker is not used, This will make the image very bloated, use docker sock /var/run/docker.sock:/var/run/docker.sock

@zzzhangqi  “Support for compilation detached mode and mixed mode in docker.” What is the usage scenario and can you tell us about it?

@MonsterChenzhuo
The problem that needs to be solved is no longer relying on the local environment for deployment.
Users can deploy StreamX simply by pulling the image.

这里有个最大的问题，客户群体的考虑，你考虑到了新的用户畅快的体验，但是没有覆盖到一些使用历史版本但是有升级需求的用户，当用户想通过docker镜像来体验新功能看是否满足目前需求时，就会暴露出当前pr的短板，同时还要考虑后面的e2e测试，他也要基于当前的docker-cpmose来进行。就必须要求镜像是随着新pr的合并实时更新的。

官方是有做ci的，会自动打镜像推docker，地址@wolfboys应该是清楚的

不区分新老用户，老用户仍可使用旧的 docker-compose 方式，挂载 /streamx 目录.
随着合并的实时更新可以依赖于 github action，这块不应该我来做，我将提供 docker build 方法

“docker in docker is not used, This will make the image very bloated, use docker sock /var/run/docker.sock:/var/run/docker.sock”
Have you tested the whole deployment based on k8s after the change?

进行过简单测试，你可以基于此命令再次进行验证
wget https://raw.githubusercontent.com/zzzhangqi/streamx/dev/deploy/docker/docker-compose.yaml && docker-compose up -d

前后端部署这块抽离出来了，既然架构上做了解偶，那么就要提供前后端分离部署

@zzzhangqi  在docker中分离部署的实际意义是什么？就是能解决什么样的问题，有这方面的痛点么？

docker 中分离部署意义不大，这块打算应用在k8s中

我的意思是如果去动，一定是要有实际使用痛点

依赖本地环境，既然使用了 docker 部署，为什么还要依赖本地环境，那么 docker 的意义在哪？
为什么提供前后端分离部署，如在 k8s 中部署，前后端均有多个副本，其中一个 ui 副本挂了也不会影响使用

我建议可以这么去改，首先把ci的手动，改成每次和pr后自动执行，这样保证streamx官方的dockerhub镜像永远是最新的代码，然后docker-compose去依赖这个镜像。
我用的就是docker sock /var/run/docker.sock:/var/run/docker.sock实现，但是当时是发现不用docker:bind这个镜像，docker环境还是不通的，部署k8s那块一定要测这个问题。因为你这个pr已经涉及到这些了，包括ci的逻辑也要测了，因为ci也是基于这个的

我用的就是docker sock /var/run/docker.sock:/var/run/docker.sock实现，但是当时是发现不用docker:bind这个镜像，docker环境还是不通的，部署k8s那块一定要测这个问题。因为你这个pr已经涉及到这些了，包括ci的逻辑也要测了，因为ci也是基于这个的

这块如何测试，我对这块并不是很熟悉

authors: MonsterChenzhuo zzzhangqi

repo: streamxhub/streamx


text:
Separate docker image pull and build process

What problem does this PR solve?
When an incorrect flink-base-image was specified to submit flink-job on flink-k8s application mode, the associated error log is vague and does not provide sufficient error information.
What is changed ?
Separate the docker image pull and build process on DockerTool.

LGTM.

authors: Al-assad wolfboys


text:
"Multi_valued" for datatype definitions not exported

I don't know if this expected/desired behavior, but no matter what I specify in the datatype definition (ReqIFDataTypeDefinitonEnumeration), the multi_valued metadata is never exported into the reqIF output.
Is that due to missing code in data_type_parser.py (line 270ff in the case of enumerations)?

Hi @DavidKroeter84 , thanks for reporting.
All sorts of things can be still missing. Would you mind sharing here a minimal ReqIF sample that features a good ReqIFDataTypeDefinitonEnumeration example that we could use as a test fixture to fix this?

Hi @stanislaw !
I think the form the reqIF standard suggests would look the following:
...
<DATATYPE-DEFINITION-ENUMERATION DESC="Requirement category" IDENTIFIER="type-reqtype" LAST-CHANGE="2019-01-01T00:00:00.000+02:00" LONG-NAME="Requirement type">
	<SPECIFIED-VALUES>
		<ENUM-VALUE IDENTIFIER="value-reqtype-hardware" LAST-CHANGE="2019-01-01T00:00:00.000+02:00" LONG-NAME="hardware">
			<PROPERTIES>
				<EMBEDDED-VALUE KEY="0" OTHER-CONTENT="hardware"/>
			</PROPERTIES>
		</ENUM-VALUE>
		<ENUM-VALUE IDENTIFIER="value-reqtype-project" LAST-CHANGE="2019-01-01T00:00:00.000+02:00" LONG-NAME="project">
			<PROPERTIES>
				<EMBEDDED-VALUE KEY="1" OTHER-CONTENT="project"/>
			</PROPERTIES>
		</ENUM-VALUE>
		<ENUM-VALUE IDENTIFIER="value-reqtype-software" LAST-CHANGE="2019-01-01T00:00:00.000+02:00" LONG-NAME="software">
			<PROPERTIES>
				<EMBEDDED-VALUE KEY="2" OTHER-CONTENT="software"/>
			</PROPERTIES>
		</ENUM-VALUE>
	</SPECIFIED-VALUES>
</DATATYPE-DEFINITION-ENUMERATION>

...

<ATTRIBUTE-DEFINITION-ENUMERATION IDENTIFIER="attr-reqtype" IS-EDITABLE="true" LAST-CHANGE="2019-01-01T00:00:00.000+02:00" LONG-NAME="Requirement type" MULTI-VALUED="false">
  <TYPE>
	  <DATATYPE-DEFINITION-ENUMERATION-REF>type-reqtype</DATATYPE-DEFINITION-ENUMERATION-REF>
  </TYPE>
  <DEFAULT-VALUE>
	  <ATTRIBUTE-VALUE-ENUMERATION>
		  <VALUES>
			  <ENUM-VALUE-REF>value-reqtype-software</ENUM-VALUE-REF>
		  </VALUES>
		  <DEFINITION>
			  <ATTRIBUTE-DEFINITION-ENUMERATION-REF>attr-reqtype</ATTRIBUTE-DEFINITION-ENUMERATION-REF>
		  </DEFINITION>
	  </ATTRIBUTE-VALUE-ENUMERATION>
  </DEFAULT-VALUE>
</ATTRIBUTE-DEFINITION-ENUMERATION>

Note that the MULTI-VALUED tag is only part of the ATTRIBUTE-DEFINITION-ENUMERATION.

Please check this: https://github.com/strictdoc-project/reqif/pull/173. I believe that you found some dead code 👍 Thanks for reporting this.

Note that the MULTI-VALUED tag is only part of the ATTRIBUTE-DEFINITION-ENUMERATION.

Indeed, it looks like it.

Please confirm that this change makes sense to you as well, and I will release a new Pip.

Hi @stanislaw
Hm, but what about line 105? Is the attribute really unused?
I thought that the multi-value property shall be there, but only for enumerations
(in      , see my code snippets above)
But I must admit I am not 100% firm with the reqIF specification.

repo: strictdoc-project/reqif


text:
Investigate supabase CLI integration

Evaluate if it's ease of integrating with the supabase CLI

Heyy, I came across this repo when it was shared internally at Supabase. I think what you are doing here is really cool. If there's anything I can help with, please feel free to give us a shout :)

Definitely! I think the biggest feature I want to have is support for non-public schemas before I attempt to integrate this with your folks' CLI. I'm not sure if you have any strong thoughts there?
Overall, any help with integrating this into your folks' CLI would be great. Not sure if you have any strong prefs for how to do it. I
-- I also realized I posted this initial issue on the wrong github account, oops!

I want to have is support for is non-public schemas before I attempt to integrate this with your folks' CLI

That's great to hear! I think it's not necessarily a blocker for integration.
Supabase CLI supports --schema flag for diffing specific schemas. We can introduce a new flag --with-pg-schema-diff that is required together with --schema public. This allows users to invoke your tool and provide feedback as you build out support for other schemas.

Overall, any help with integrating this into the supabase CLI would be great. Not sure if you have any strong prefs for how to do it.

We run existing tools like migra and pgadmin-diff in docker containers mainly because they are not written in go. I hope Supabase CLI can import this package natively so we don't need to rely on docker for diffing.
I will probably give it a shot next week but if you see any immediate blocker please let me know.

Ahh that's perfect. As an initial integration, it makes sense to just error out if folks don't have the schema filter set to public.
I can't think of any immediate blockers. I'm excited to see the PR! Let me know if there's anyway I can help.

I briefly explored the integration in my linked PR. There are a few questions that would need your help to clarify.

Is there any plans to support diffing database by their connection string?
Ideally we also want to support users who make schema changes through our dashboard GUI and diff those changes to save as a migration file. Currently I'm implementing the tempdb.Factory interface to create a database from existing schema file but I'm not sure how it would work if we want to use the current schema of the database instead of recreating from an array of DDL statements. Perhaps we can expose schema.go in pkg instead so that users can call GetPublicSchema directly?

I realise some of the important entities, like RLS policies, are not included in the diff. What is the process and timeline for requesting these entities to be added?

A minor issue I faced when calling GeneratePlan method is that planOptions is declared as a private type. Can we make it public so that I can override some of the options?

Yes, we can add support for diffing between databases. It should be pretty trivial to implement an initial implementation of that. I don't want to expose GetPublicSchema because the underlying structs of the schema object are volatile, and I don't want folks to build dependencies on them.
I imagine things like RLS policies will be pretty straight-forward to add. What other entities are you thinking? Materialized views will certainly be trickier but doable.
What options are you trying to modify? The options struct is intentionally not-exported, since modification of options is supposed to be constrained to the With{X} options. If you're looking at the schema getter options, those are not supported yet because we still need to update the SQL generation code to support multiple schemas. We can now fetch multiple schemas but the SQL generation will still fall apart with multiple schemas.

As a follow up to the above, some things I think would be good to establish:

What schema entities would you like to be diffable before you feel comfortable exposing to users (by priority)?
What schema entities would you like to be supported in an ideal world? (maybe the answer is everything)
Do you want all of the DDL to be able to be run in a transaction? I know some folks are looking for that use case (ticket)

The options struct is intentionally not-exported, since modification of options is supposed to be constrained to the With{X} options.

Thanks for the tip. I was looking for ways to disable validation and WithDoNotValidatePlan is working like a charm.

we can add support for diffing between databases.

Also thanks for the quick turnaround on diffing between databases. I think that was a major blocker for exposing to CLI users because our current convention uses their local database as source of truth.

Do you want all of the DDL to be able to be run in a transaction?

I don't think this is a problem for us because we split each migration file into individual statements and run them in an implicit transaction using pgx.Batch. The implicit transaction is a feature of extended PostgreSQL protocol which doesn't error with concurrent index build. I verified this by running db reset with a diff file containing CREATE UNIQUE INDEX CONCURRENTLY.
But in the worst case, if any DDL statement can't be used in the same transaction as others, users always have the option to move it to a new file independently. This might be one of the benefits of using timestamped migration files.

What schema entities would you like to be diffable before you feel comfortable exposing to users (by priority)? What schema entities would you like to be supported in an ideal world?

In terms of priority, RLS policies and custom enum types are probably the highest on my list.
I haven't had the time to test other pg entities exhaustively but I find the unit tests created by migra/schemainspect to be a good starting place. There are other areas of migra that leaves more to be desired but we can probably discuss those in a separate issue.

Yes, I've discovered migra has poor support of partitions, which is where this library partially comes into play.
A lot of our DDL is non-transactional to optimize minimizing locks, i.e., when a col is switch to NOT NULL, we build a
invalid check constraint, validate it, mark the column as not null, and then drop the check constraint.
I think the enums and RLS policies should be pretty straight forward, since it's not as much of a schema entity dependency problem 🤞 .
I should have public schema support up by EoW. It's basically done; I just need to build tests (and confidence). Diffing DB's is now a matter of implementing SchemaSource for a sql.DB, which should be pretty straightforward. I can probably knock out RLS policies next week and maybe enums.
This project is not my primary focus, so I cannot guarantee any timelines here unfortunately 😆 .

I cannot guarantee any timelines here unfortunately

That's totally fine with us. Thank you for all the efforts you've put into this open source project.

Multi-schema support is in. I'll try to get the DatabaseSchemaSource in today, and then I can work on rolling out the enum + RLS policy diffing.

Having a database as a schema source is now supported. This should unblock the actual integration.
In terms of next steps, I'm going to:

Update the CLI to support non-public schemas, schema filters, and comparing two databases directly. I realize this isn't on your desired feature set, but it's important that the CLI doesn't become too out of date from the features the library supports.
Add row-level security support
Add enum support

@sweatybridge , would you say that the lack of RLS and enum support is blocking your PR to add pg-schema-diff support ?

Not necessarily blocking. I can add a warning message after generating diff so that users are aware of the unsupported entities.
Let me update my PR and hopefully merge it before end of this week.

@sweatybridge, sounds like a plan! I'm really just trying to assess priority of features for you folks!
If you want your integration to be fancy, you could use pg_dump to check the migration actually matches what your user expects (assuming you have access to that binary).
TempDB -> Apply old schema -> Apply migration -> pg_dump . TempDB -> Apply new schema -> pg_dump. Make sure they match! Could be useful as validation for any of your migration generation integrations (migra, pgadmin)

I've shipped the --use-pg-schema flag to CLI beta channel with a warning message. Your new changes have made my integration work a lot easier. Kudos to you!

Amazing! Thanks @sweatybridge! I'm going to close out this ticket, but feel free to open any tickets for feature requests/etc. I'll cut tickets for enums and RLS policies.
Also feel free to cut any tickets/start any discussions if there's something else you folks are looking for! I think supabase will be a great way to battle-test this library and find its shortcomings/sharp-edges.

authors: Navbryce bplunkett-stripe sweatybridge

repo: stripe/pg-schema-diff


text:
[BUG]: Missing implementation of 'retrieveCardNetworks' method in the package

What happened?
trying to implement Co-badged cards compliance, and custom integration as described here:
https://docs.stripe.com/co-badged-cards-compliance?type=custom-integration#available-networks-for-card-numbers
the method exists on "https://js.stripe.com/v3"
but not exist on @stripe/stripe-js package
I'm using the last version "@stripe/stripe-js": "3.5.0",

but not exist on @stripe/stripe-js package

Can you explain more about what exactly isn't working, such as sharing a code snippet and the error you encounter? This module does not define any methods, so as you note the method exists in Stripe.js it would be usable when loaded via this module.
It's possible you mean that the types are missing this method, which you can temporarily work around with // @ts-ignore.

@Mage111 , Do you implement this logic?

authors: Mage111 aharodnikau brendanm-stripe

repo: stripe/stripe-js


text:
Make all TestCaseWithRepository based tests to use @TestRepository and @TestArtifact annotations

Task Description
We need to complete test resources management refactoring and make all tests to use @TestRepository and @TestArtifact annotations (or layout specific shortcut annotations).
As a result we should get rid of TestCaseWithRepository class.
Please note, that this task could be done by multiple people as smaller pull requests fixing separate tests.
Tasks
The following tests will need to be refactored:

[ ] MavenArtifactTest
[ ] MavenArtifactControllerTest
[ ] RetryDownloadArtifactWithUnsupportedRangeRequestTest
[ ] ArtifactManagementServiceImplTest
[ ] MockedRestArtifactResolverTestBase
[ ] ArtifactDirectoryLocatorTest
[ ] RebuildMavenMetadataCronJobTestIT
[ ] MavenChecksumServiceTest
[ ] WhenRepositoryIsAliveCleanExpiredArtifactsTestIT
[ ] WhenRepositoryIsNotAliveDontCleanExpiredArtifactsTestIT
[ ] MavenMetadataExpirationMultipleGroupCaseTest
[ ] MavenProxyRepositoryProviderTestIT
[ ] TrashControllerTest
[ ] ResourcesBooterTest
[ ] RawArtifactControllerTest
[ ] BrowseControllerTest
[ ] ArtifactMetadataServiceSnapshotsTest
[ ] MavenMetadataGroupRepositoryComponentOnAddTest
[ ] PingControllerTest
[ ] RawArtifactControllerTestIT
[ ] TestCaseWithMavenArtifactGenerationAndIndexing
[ ] MavenRestAssuredBaseTest
[ ] Maven2LayoutProviderTest
[ ] MavenGroupRepositoryProviderTest
[ ] MavenTestCaseWithArtifactGeneration
[ ] MavenRepositoryManagementServiceImplTest
[ ] MavenMetadataGroupRepositoryComponentOnUploadTest
[ ] ArtifactOutputStreamTest
[ ] MavenArtifactGeneratorTest
[ ] MavenMetadataManagementControllerTest
[ ] MergeMavenGroupRepositoryIndexCronJobTestIT
[ ] BaseMavenMetadataExpirationTest
[ ] RepositoryHostedIndexCreatorTest
[ ] BaseCronJobWithMavenIndexingTestCase
[ ] ClearTrashCronJobFromMaven2RepositoryTestIT
[ ] ParallelDownloadRemoteArtifactTest
[ ] MavenMetadataExpirationSingleGroupCaseTest
[ ] BaseMavenGroupRepositoryComponentTest
[ ] MavenDependencyFormatterTest
[ ] TestCaseWithRepositoryManagement
[ ] BaseLocalStorageProxyRepositoryExpiredArtifactsCleanerTest
[ ] RetryDownloadArtifactWithPermanentFailureStartingAtSomePointTest
[ ] RepositoryGroupIndexCreatorSearchTest
[ ] MavenSearchControllerTest
[ ] MavenMetadataExpirationProxyCaseTest
[ ] RemoveTimestampedMavenSnapshotCronJobTestIT
[ ] ArtifactCoordinateValidatorsManagementControllerTest
[ ] TrashControllerUndeleteTest
[ ] AqlControllerTest
[ ] RepositoryHostedIndexCreatorSearchTest
[ ] DownloadRemoteMavenIndexCronJobTestIT
[ ] MavenMetadataGroupRepositoryComponentOnDeleteTest
[ ] RawRestAssuredBaseTest
[ ] RetryDownloadArtifactWithSingleFailureAtSomePointTest
[ ] CleanupExpiredArtifactsFromProxyRepositoriesCronJobTestIT
[ ] MavenIndexControllerTest
[ ] ArtifactMetadataServiceReleasesTest
[ ] RepositoryProxyIndexCreatorTest
[ ] RebuildMavenIndexesCronJobTestIT
[ ] RegenerateMavenChecksumCronJobTestIT

Task Relationships
This task:

Is a follow-up of: #1083 , #1084.
Relates to: #1165

Useful Links

Writing tests

Help

Our chat
Points of contact:

@carlspring
@fuss86
@sbespalov
@steve-todorov

Hi! I'd like to pick this up.

Great! Thanks! :)

authors: carlspring ptirador sbespalov

repo: strongbox/strongbox


text:
Share page returns 500 without any log

Description
I'm having a strange issue with our on-premises installation since we changed our S3 secret/key.
The initial page (http://example.com/) loads and shows all workspaces. The same applies for the diagram page (http://example.com/share/7/diagrams), but the configuration/home page for the diagram (http://example.com/share/7) returns an status code 500 with the text:
Error
Sorry, something went wrong.

I tried to debug changing the log4j2 levels to ALL, but nothing is logged:
[INFO ] 2023-09-21 20:16:51.704 [main] ContextLoaderListener - ***********************************************************************************
[INFO ] 2023-09-21 20:16:51.711 [main] ContextLoaderListener -   _____ _                   _              _
[INFO ] 2023-09-21 20:16:51.711 [main] ContextLoaderListener -  / ____| |                 | |            (_)
[INFO ] 2023-09-21 20:16:51.711 [main] ContextLoaderListener - | (___ | |_ _ __ _   _  ___| |_ _   _ _ __ _ _____ __
[INFO ] 2023-09-21 20:16:51.711 [main] ContextLoaderListener -  \___ \| __| '__| | | |/ __| __| | | | '__| |_  / '__|
[INFO ] 2023-09-21 20:16:51.711 [main] ContextLoaderListener -  ____) | |_| |  | |_| | (__| |_| |_| | |  | |/ /| |
[INFO ] 2023-09-21 20:16:51.712 [main] ContextLoaderListener - |_____/ \__|_|   \__,_|\___|\__|\__,_|_|  |_/___|_|
[INFO ] 2023-09-21 20:16:51.712 [main] ContextLoaderListener -
[INFO ] 2023-09-21 20:16:51.712 [main] ContextLoaderListener - Structurizr on-premises installation
[INFO ] 2023-09-21 20:16:51.715 [main] ContextLoaderListener -  - build: 3080 (2023-06-21T09:31:25Z
[INFO ] 2023-09-21 20:16:51.719 [main] ContextLoaderListener -  - structurizr-java: v1.24.1
[INFO ] 2023-09-21 20:16:51.748 [main] ContextLoaderListener -  - structurizr-dsl: v1.30.2
[INFO ] 2023-09-21 20:16:51.749 [main] ContextLoaderListener -  - structurizr-import: v1.4.1
[INFO ] 2023-09-21 20:16:51.787 [main] ContextLoaderListener - Data directory: /usr/local/structurizr (r: true; w: true; x: true)
[INFO ] 2023-09-21 20:16:51.788 [main] ContextLoaderListener - URL: (removed for privacy)
[INFO ] 2023-09-21 20:16:51.800 [main] ContextLoaderListener - Memory: used=604MB; free=419MB; total=1024MB; max=1024MB
[INFO ] 2023-09-21 20:16:51.800 [main] ContextLoaderListener -
[INFO ] 2023-09-21 20:16:51.801 [main] ContextLoaderListener - Authentication: file
[INFO ] 2023-09-21 20:16:51.801 [main] ContextLoaderListener - Session: local
[INFO ] 2023-09-21 20:16:51.802 [main] ContextLoaderListener - Data storage: aws-s3
[INFO ] 2023-09-21 20:16:51.802 [main] ContextLoaderListener - Search: lucene
[INFO ] 2023-09-21 20:16:51.802 [main] ContextLoaderListener - dot: true
[INFO ] 2023-09-21 20:16:51.802 [main] ContextLoaderListener - DSL editor: false
[INFO ] 2023-09-21 20:16:51.803 [main] ContextLoaderListener - Safe mode: true
[INFO ] 2023-09-21 20:16:51.803 [main] ContextLoaderListener - ***********************************************************************************
[INFO ] 2023-09-21 20:16:51.803 [main] ContextLoaderListener - MIT License
[INFO ] 2023-09-21 20:16:51.803 [main] ContextLoaderListener -
[INFO ] 2023-09-21 20:16:51.803 [main] ContextLoaderListener - Copyright (c) 2023 Structurizr Limited
[INFO ] 2023-09-21 20:16:51.803 [main] ContextLoaderListener -
[INFO ] 2023-09-21 20:16:51.803 [main] ContextLoaderListener - Permission is hereby granted, free of charge, to any person obtaining a copy
[INFO ] 2023-09-21 20:16:51.803 [main] ContextLoaderListener - of this software and associated documentation files (the "Software"), to deal
[INFO ] 2023-09-21 20:16:51.804 [main] ContextLoaderListener - in the Software without restriction, including without limitation the rights
[INFO ] 2023-09-21 20:16:51.804 [main] ContextLoaderListener - to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
[INFO ] 2023-09-21 20:16:51.804 [main] ContextLoaderListener - copies of the Software, and to permit persons to whom the Software is
[INFO ] 2023-09-21 20:16:51.804 [main] ContextLoaderListener - furnished to do so, subject to the following conditions:
[INFO ] 2023-09-21 20:16:51.804 [main] ContextLoaderListener -
[INFO ] 2023-09-21 20:16:51.804 [main] ContextLoaderListener - The above copyright notice and this permission notice shall be included in all
[INFO ] 2023-09-21 20:16:51.804 [main] ContextLoaderListener - copies or substantial portions of the Software.
[INFO ] 2023-09-21 20:16:51.804 [main] ContextLoaderListener -
[INFO ] 2023-09-21 20:16:51.805 [main] ContextLoaderListener - THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
[INFO ] 2023-09-21 20:16:51.805 [main] ContextLoaderListener - IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
[INFO ] 2023-09-21 20:16:51.805 [main] ContextLoaderListener - FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
[INFO ] 2023-09-21 20:16:51.805 [main] ContextLoaderListener - AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
[INFO ] 2023-09-21 20:16:51.805 [main] ContextLoaderListener - LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
[INFO ] 2023-09-21 20:16:51.805 [main] ContextLoaderListener - OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
[INFO ] 2023-09-21 20:16:51.805 [main] ContextLoaderListener - SOFTWARE.
[INFO ] 2023-09-21 20:16:51.806 [main] ContextLoaderListener - ***********************************************************************************
21-Sep-2023 20:16:55.794 INFO [main] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [/usr/local/tomcat/webapps/ROOT.war] has finished in [11,286] ms
21-Sep-2023 20:16:55.797 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
21-Sep-2023 20:16:55.812 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [11470] milliseconds

My log42j file looks like this:
appender.console.type = Console
appender.console.name = LogToConsole
appender.console.layout.type = PatternLayout
appender.console.layout.pattern = [%-5level] %d{yyyy-MM-dd HH:mm:ss.SSS} [%t] %c{1} - %msg%n

appender.file.type = File
appender.file.name = LogToFile
appender.file.fileName=${sys:structurizr.dataDirectory}/logs/structurizr.log
appender.file.layout.type=PatternLayout
appender.file.layout.pattern=[%-5level] %d{yyyy-MM-dd HH:mm:ss.SSS} [%t] %c{1} - %msg%n

logger.app.name = com.structurizr
logger.app.level = ALL
logger.app.additivity = false
logger.app.appenderRef.console.ref = LogToConsole
logger.app.appenderRef.file.ref = LogToFile

logger.springSecurity.name = org.springframework.security
logger.springSecurity.level = ALL
logger.springSecurity.additivity = false
logger.springSecurity.appenderRef.console.ref = LogToConsole
logger.springSecurity.appenderRef.file.ref = LogToFile

rootLogger.level = ALL
rootLogger.appenderRef.stdout.ref = LogToConsole
rootLogger.appenderRef.file.ref = LogToFile

I had this behavior in the past and could debug as something related to trying to access the s3 object history, but could not reproduce this time.
Steps to reproduce
1 - run the Structurizr on premises pointing to S3 bucket;
2 - access the home of the workspace;
3 - get the 500 error page.
Screenshot
No response
Code sample
No response
Configuration
build: 3080 (2023-06-21T09:31:25Z
Severity
Major
Priority
Low
Resolution
I'm willing to fix this myself and raise a PR
More information
No response

since we changed our S3 secret/key

Perhaps related to the permissions you've granted this new credential pair?

I'm willing to fix this myself and raise a PR

Thanks!

@simonbrowndotje I believe you are correct - do you have a list of the needed Actions that should be granted in this credential?

Update from 3080 to 3142 and now the log4j2 configuration file appers to works - now I can see the error more clearly:
[DEBUG] 2023-09-22 11:00:02.853 [http-nio-8080-exec-8] wire - http-outgoing-31 >> "GET /?versions&prefix=workspaces%2F3%2Fworkspace.json&max-keys=30&encoding-type=url HTTP/1.1[\r][\n]"
[DEBUG] 2023-09-22 11:00:02.853 [http-nio-8080-exec-8] wire - http-outgoing-31 >> "Host: (removed for privacy)[\r][\n]"
....
[DEBUG] 2023-09-22 11:00:02.863 [http-nio-8080-exec-8] wire - http-outgoing-31 << "HTTP/1.1 403 Forbidden[\r][\n]"
...
[DEBUG] 2023-09-22 11:00:02.863 [http-nio-8080-exec-8] wire - http-outgoing-31 << "<?xml version="1.0" encoding="UTF-8"?>[\n]"
[DEBUG] 2023-09-22 11:00:02.864 [http-nio-8080-exec-8] wire - http-outgoing-31 << "<Error>AccessDenied<Message>Access Denied</Message><RequestId>(removed for privacy)</RequestId><HostId>(removed for privacy)</HostId></Error>[\r][\n]"

There's two actions that I would like to do:

improve the error handling and logging (maybe a more detailed 5xx error page?) on this function: https://github.com/structurizr/onpremises/blob/main/structurizr-onpremises/src/main/java/com/structurizr/onpremises/component/workspace/AmazonWebServicesS3WorkspaceDao.java#L228;
find out the specific permissions/actions that Structurizr uses - some organizations doesn't allow using the AmazonS3FullAccess.

Sounds in the right direction?

Hi @iowaz
FYI: Here is my working S3 Policy config.
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:ListAllMyBuckets",
"s3:GetBucketLocation"
],
"Resource": "arn:aws:s3:::"
},
{
"Sid": "AllowStatement2B",
"Action": [
"s3:ListBucket",
"s3:ListBucketVersions"
],
"Effect": "Allow",
"Resource": [
"arn:aws:s3:::structurizr"
]
},
{
"Sid": "AllowStatement4B",
"Effect": "Allow",
"Action": [
"s3:"
],
"Resource": [
"arn:aws:s3:::structurizr/*"
]
}
]
}

Update from 3080 to 3142 and now the log4j2 configuration file appers to works - now I can see the error more clearly:
[DEBUG] 2023-09-22 11:00:02.853 [http-nio-8080-exec-8] wire - http-outgoing-31 >> "GET /?versions&prefix=workspaces%2F3%2Fworkspace.json&max-keys=30&encoding-type=url HTTP/1.1[\r][\n]"
[DEBUG] 2023-09-22 11:00:02.853 [http-nio-8080-exec-8] wire - http-outgoing-31 >> "Host: (removed for privacy)[\r][\n]"
....
[DEBUG] 2023-09-22 11:00:02.863 [http-nio-8080-exec-8] wire - http-outgoing-31 << "HTTP/1.1 403 Forbidden[\r][\n]"
...
[DEBUG] 2023-09-22 11:00:02.863 [http-nio-8080-exec-8] wire - http-outgoing-31 << "<?xml version="1.0" encoding="UTF-8"?>[\n]"
[DEBUG] 2023-09-22 11:00:02.864 [http-nio-8080-exec-8] wire - http-outgoing-31 << "<Error>AccessDenied<Message>Access Denied</Message><RequestId>(removed for privacy)</RequestId><HostId>(removed for privacy)</HostId></Error>[\r][\n]"

There's two actions that I would like to do:

improve the error handling and logging (maybe a more detailed 5xx error page?) on this function: https://github.com/structurizr/onpremises/blob/main/structurizr-onpremises/src/main/java/com/structurizr/onpremises/component/workspace/AmazonWebServicesS3WorkspaceDao.java#L228;
find out the specific permissions/actions that Structurizr uses - some organizations doesn't allow using the AmazonS3FullAccess.

Sounds in the right direction?

authors: ddelucaenhesa iowaz simonbrowndotje

repo: structurizr/onpremises


text:
Equivalent mutant created for if(x) return undefined

Stryker-js creates a mutant that is equivalent to the original code:

Actually it is hard to say if it is equivalent... it removes return statement from there, meaning that it can possibly return something else or return undefined later
see:
case: we always get response.status = 404
function test() {
  if(response.status === 404) {
    return undefined;
  } else {
    return true;
   }
   const res = doSomethingWithResponse();

   if(res.error) {
     return undefined;
    }
   return res;
}```

now mutating it:
```js
function test() {
  if(response.status === 404) { // passes through
  } else {
    return true;
   }
   const res = doSomethingWithResponse();

   if(res.error) { // if error - we still return `undefined`. From what i remember, we want to kill mutatans - tests should fail... if our test asserts result to be `undefined` test passes..
     return undefined;
    }
   return res; // unless there was error in `res.error` and goes here, then test fails which is good i believe
}```

so i think the result "might" be equivalent mutant, but its not necessarily always true

correct me if i am wrong

Yeah, I asked @hugo-vrijswijk to create this issue. I thought it had to do with mutating undefined in this way:
- return undefined;
+ return;

This would most definitely be an equivalent mutant. But seeing as it's the block statement mutator, it would probably be impossible to detect deterministically.
You either have to refactor the code to not use this return, or disable the mutant with a comment

authors: hugo-vrijswijk kmdrGroch nicojs

repo: stryker-mutator/stryker-js