Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 7 112 | repo_url stringlengths 36 141 | action stringclasses 3 values | title stringlengths 1 744 | labels stringlengths 4 574 | body stringlengths 9 211k | index stringclasses 10 values | text_combine stringlengths 96 211k | label stringclasses 2 values | text stringlengths 96 188k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
73,301 | 24,554,429,969 | IssuesEvent | 2022-10-12 14:51:16 | SeleniumHQ/selenium | https://api.github.com/repos/SeleniumHQ/selenium | opened | [🐛 Bug]: Unable to find an exact match for CDP version 106, so returning the closest version found: a no-op implementation | I-defect needs-triaging | ### What happened?
I am trying to save a screenshot from my RemoteWebDriver session (GRID 4 distributed mode) and it looks like there is an issue with the websocket connection or the cdp version is not compatiable with selenium-java version: 4.5.0
### How can we reproduce the issue?
```shell
Java code:
driver = WebDriverManager.chromedriver()
.remoteAddress("http://seleniumgridtest.check24tech.de:4444")
.capabilities(DesiredCapabilitiesFactory.createChromeOptions())
.create();
WebDriver augmentedDriver = new Augmenter().augment(driver);
srcFile = ((TakesScreenshot) augmentedDriver).getScreenshotAs(OutputType.FILE);
```
```
### Relevant log output
```shell
Connected to the target VM, address: '127.0.0.1:64835', transport: 'socket'
Oct 12, 2022 3:58:12 PM org.openqa.selenium.remote.tracing.opentelemetry.OpenTelemetryTracer createTracer
INFO: Using OpenTelemetry for tracing
Oct 12, 2022 3:58:25 PM org.openqa.selenium.remote.ProtocolHandshake createSession
INFO: Detected upstream dialect: W3C
Oct 12, 2022 4:02:05 PM org.openqa.selenium.devtools.CdpVersionFinder findNearestMatch
WARNING: Unable to find an exact match for CDP version 106, so returning the closest version found: a no-op implementation
Oct 12, 2022 4:02:05 PM org.openqa.selenium.devtools.CdpVer
Oct 12, 2022 4:20:19 PM org.openqa.selenium.devtools.CdpVersionFinder findNearestMatch
WARNING: Unable to find an exact match for CDP version 106, so returning the closest version found: a no-op implementation
Oct 12, 2022 4:20:19 PM org.openqa.selenium.devtools.CdpVersionFinder findNearestMatch
INFO: Unable to find CDP implementation matching 106.
Oct 12, 2022 4:20:29 PM org.openqa.selenium.remote.http.netty.NettyWebSocket lambda$new$0
WARNING: connection timed out: /172.20.0.5:4444
java.net.ConnectException: connection timed out: /172.20.0.5:4444
at org.asynchttpclient.netty.channel.NettyConnectListener.onFailure(NettyConnectListener.java:179)
at org.asynchttpclient.netty.channel.NettyChannelConnector$1.onFailure(NettyChannelConnector.java:108)
at org.asynchttpclient.netty.SimpleChannelFutureListener.operationComplete(SimpleChannelFutureListener.java:28)
at org.asynchttpclient.netty.SimpleChannelFutureListener.operationComplete(SimpleChannelFutureListener.java:20)
at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:578)
at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:571)
at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:550)
at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:491)
at io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:616)
at io.netty.util.concurrent.DefaultPromise.setFailure0(DefaultPromise.java:609)
at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:117)
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:262)
at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:153)
at io.netty.util.concurrent.AbstractEventExecutor.runTask$$$capture(AbstractEventExecutor.java:174)
at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java)
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute$$$capture(AbstractEventExecutor.java:167)
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:832)
Caused by: io.netty.channel.ConnectTimeoutException: connection timed out: /172.20.0.5:4444
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:261)
... 12 more
Oct 12, 2022 4:20:29 PM org.openqa.selenium.remote.http.WebSocket$Listener onError
WARNING: connection timed out: /172.20.0.5:4444
java.net.ConnectException: connection timed out: /172.20.0.5:4444
at org.asynchttpclient.netty.channel.NettyConnectListener.onFailure(NettyConnectListener.java:179)
at org.asynchttpclient.netty.channel.NettyChannelConnector$1.onFailure(NettyChannelConnector.java:108)
at org.asynchttpclient.netty.SimpleChannelFutureListener.operationComplete(SimpleChannelFutureListener.java:28)
at org.asynchttpclient.netty.SimpleChannelFutureListener.operationComplete(SimpleChannelFutureListener.java:20)
at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:578)
at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:571)
at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:550)
at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:491)
at io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:616)
at io.netty.util.concurrent.DefaultPromise.setFailure0(DefaultPromise.java:609)
at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:117)
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:262)
at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:153)
at io.netty.util.concurrent.AbstractEventExecutor.runTask$$$capture(AbstractEventExecutor.java:174)
at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java)
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute$$$capture(AbstractEventExecutor.java:167)
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:832)
Caused by: io.netty.channel.ConnectTimeoutException: connection timed out: /172.20.0.5:4444
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:261)
... 12 more
org.openqa.selenium.remote.http.ConnectionFailedException: Unable to establish websocket connection to http://172.20.0.5:4444/session/b47bfd6fa8d3d37c813e127f67f8cb0d/se/cdp
Build info: version: '4.5.0', revision: 'fe167b119a'
System info: os.name: 'Mac OS X', os.arch: 'aarch64', os.version: '12.5', java.version: '15.0.8'
Driver info: driver.version: unknown
at org.openqa.selenium.remote.http.netty.NettyWebSocket.<init>(NettyWebSocket.java:102)
at org.openqa.selenium.remote.http.netty.NettyWebSocket.lambda$create$3(NettyWebSocket.java:128)
at org.openqa.selenium.remote.http.netty.NettyClient.openSocket(NettyClient.java:107)
at org.openqa.selenium.devtools.Connection.<init>(Connection.java:77)
at org.openqa.selenium.devtools.SeleniumCdpConnection.<init>(SeleniumCdpConnection.java:34)
at org.openqa.selenium.devtools.SeleniumCdpConnection.lambda$create$0(SeleniumCdpConnection.java:56)
at java.base/java.util.Optional.map(Optional.java:258)
at org.openqa.selenium.devtools.SeleniumCdpConnection.create(SeleniumCdpConnection.java:54)
at org.openqa.selenium.devtools.SeleniumCdpConnection.create(SeleniumCdpConnection.java:47)
at org.openqa.selenium.devtools.DevToolsProvider.getImplementation(DevToolsProvider.java:50)
at org.openqa.selenium.devtools.DevToolsProvider.getImplementation(DevToolsProvider.java:31)
at org.openqa.selenium.remote.Augmenter.augment(Augmenter.java:186)
at de.check24.testumgebung.TestListener.savePng(TestListener.java:64)
at de.check24.testumgebung.TestListener.createScreenshot(TestListener.java:42)
at de.check24.testumgebung.TestListener.onTestFailure(TestListener.java:160)
at org.testng.internal.TestListenerHelper.runTestListeners(TestListenerHelper.java:96)
at org.testng.internal.TestInvoker.runTestResultListener(TestInvoker.java:219)
at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:834)
at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:146)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
at org.testng.TestRunner.privateRun(TestRunner.java:794)
at org.testng.TestRunner.run(TestRunner.java:596)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:377)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:371)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:332)
at org.testng.SuiteRunner.run(SuiteRunner.java:276)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1212)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1134)
at org.testng.TestNG.runSuites(TestNG.java:1063)
at org.testng.TestNG.run(TestNG.java:1031)
at com.intellij.rt.testng.IDEARemoteTestNG.run(IDEARemoteTestNG.java:66)
at com.intellij.rt.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:109)
Disconnected from the target VM, address: '127.0.0.1:64835', transport: 'socket'
Process finished with exit code 255
```
### Operating System
macOS Monterey Version 12.5
### Selenium version
Selenium 4.5.0 | openjdk 15.0.8 2022-07-19 | Chrome-driver 4.5.0
### What are the browser(s) and version(s) where you see this issue?
Chrome v.106.0
### What are the browser driver(s) and version(s) where you see this issue?
browserVersion= v.106.0.5249.91
### Are you using Selenium Grid?
Selenium Grid 4.5.0 (revision fe167b119a) | 1.0 | [🐛 Bug]: Unable to find an exact match for CDP version 106, so returning the closest version found: a no-op implementation - ### What happened?
I am trying to save a screenshot from my RemoteWebDriver session (GRID 4 distributed mode) and it looks like there is an issue with the websocket connection or the cdp version is not compatiable with selenium-java version: 4.5.0
### How can we reproduce the issue?
```shell
Java code:
driver = WebDriverManager.chromedriver()
.remoteAddress("http://seleniumgridtest.check24tech.de:4444")
.capabilities(DesiredCapabilitiesFactory.createChromeOptions())
.create();
WebDriver augmentedDriver = new Augmenter().augment(driver);
srcFile = ((TakesScreenshot) augmentedDriver).getScreenshotAs(OutputType.FILE);
```
```
### Relevant log output
```shell
Connected to the target VM, address: '127.0.0.1:64835', transport: 'socket'
Oct 12, 2022 3:58:12 PM org.openqa.selenium.remote.tracing.opentelemetry.OpenTelemetryTracer createTracer
INFO: Using OpenTelemetry for tracing
Oct 12, 2022 3:58:25 PM org.openqa.selenium.remote.ProtocolHandshake createSession
INFO: Detected upstream dialect: W3C
Oct 12, 2022 4:02:05 PM org.openqa.selenium.devtools.CdpVersionFinder findNearestMatch
WARNING: Unable to find an exact match for CDP version 106, so returning the closest version found: a no-op implementation
Oct 12, 2022 4:02:05 PM org.openqa.selenium.devtools.CdpVer
Oct 12, 2022 4:20:19 PM org.openqa.selenium.devtools.CdpVersionFinder findNearestMatch
WARNING: Unable to find an exact match for CDP version 106, so returning the closest version found: a no-op implementation
Oct 12, 2022 4:20:19 PM org.openqa.selenium.devtools.CdpVersionFinder findNearestMatch
INFO: Unable to find CDP implementation matching 106.
Oct 12, 2022 4:20:29 PM org.openqa.selenium.remote.http.netty.NettyWebSocket lambda$new$0
WARNING: connection timed out: /172.20.0.5:4444
java.net.ConnectException: connection timed out: /172.20.0.5:4444
at org.asynchttpclient.netty.channel.NettyConnectListener.onFailure(NettyConnectListener.java:179)
at org.asynchttpclient.netty.channel.NettyChannelConnector$1.onFailure(NettyChannelConnector.java:108)
at org.asynchttpclient.netty.SimpleChannelFutureListener.operationComplete(SimpleChannelFutureListener.java:28)
at org.asynchttpclient.netty.SimpleChannelFutureListener.operationComplete(SimpleChannelFutureListener.java:20)
at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:578)
at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:571)
at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:550)
at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:491)
at io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:616)
at io.netty.util.concurrent.DefaultPromise.setFailure0(DefaultPromise.java:609)
at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:117)
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:262)
at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:153)
at io.netty.util.concurrent.AbstractEventExecutor.runTask$$$capture(AbstractEventExecutor.java:174)
at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java)
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute$$$capture(AbstractEventExecutor.java:167)
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:832)
Caused by: io.netty.channel.ConnectTimeoutException: connection timed out: /172.20.0.5:4444
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:261)
... 12 more
Oct 12, 2022 4:20:29 PM org.openqa.selenium.remote.http.WebSocket$Listener onError
WARNING: connection timed out: /172.20.0.5:4444
java.net.ConnectException: connection timed out: /172.20.0.5:4444
at org.asynchttpclient.netty.channel.NettyConnectListener.onFailure(NettyConnectListener.java:179)
at org.asynchttpclient.netty.channel.NettyChannelConnector$1.onFailure(NettyChannelConnector.java:108)
at org.asynchttpclient.netty.SimpleChannelFutureListener.operationComplete(SimpleChannelFutureListener.java:28)
at org.asynchttpclient.netty.SimpleChannelFutureListener.operationComplete(SimpleChannelFutureListener.java:20)
at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:578)
at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:571)
at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:550)
at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:491)
at io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:616)
at io.netty.util.concurrent.DefaultPromise.setFailure0(DefaultPromise.java:609)
at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:117)
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:262)
at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98)
at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:153)
at io.netty.util.concurrent.AbstractEventExecutor.runTask$$$capture(AbstractEventExecutor.java:174)
at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java)
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute$$$capture(AbstractEventExecutor.java:167)
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:832)
Caused by: io.netty.channel.ConnectTimeoutException: connection timed out: /172.20.0.5:4444
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:261)
... 12 more
org.openqa.selenium.remote.http.ConnectionFailedException: Unable to establish websocket connection to http://172.20.0.5:4444/session/b47bfd6fa8d3d37c813e127f67f8cb0d/se/cdp
Build info: version: '4.5.0', revision: 'fe167b119a'
System info: os.name: 'Mac OS X', os.arch: 'aarch64', os.version: '12.5', java.version: '15.0.8'
Driver info: driver.version: unknown
at org.openqa.selenium.remote.http.netty.NettyWebSocket.<init>(NettyWebSocket.java:102)
at org.openqa.selenium.remote.http.netty.NettyWebSocket.lambda$create$3(NettyWebSocket.java:128)
at org.openqa.selenium.remote.http.netty.NettyClient.openSocket(NettyClient.java:107)
at org.openqa.selenium.devtools.Connection.<init>(Connection.java:77)
at org.openqa.selenium.devtools.SeleniumCdpConnection.<init>(SeleniumCdpConnection.java:34)
at org.openqa.selenium.devtools.SeleniumCdpConnection.lambda$create$0(SeleniumCdpConnection.java:56)
at java.base/java.util.Optional.map(Optional.java:258)
at org.openqa.selenium.devtools.SeleniumCdpConnection.create(SeleniumCdpConnection.java:54)
at org.openqa.selenium.devtools.SeleniumCdpConnection.create(SeleniumCdpConnection.java:47)
at org.openqa.selenium.devtools.DevToolsProvider.getImplementation(DevToolsProvider.java:50)
at org.openqa.selenium.devtools.DevToolsProvider.getImplementation(DevToolsProvider.java:31)
at org.openqa.selenium.remote.Augmenter.augment(Augmenter.java:186)
at de.check24.testumgebung.TestListener.savePng(TestListener.java:64)
at de.check24.testumgebung.TestListener.createScreenshot(TestListener.java:42)
at de.check24.testumgebung.TestListener.onTestFailure(TestListener.java:160)
at org.testng.internal.TestListenerHelper.runTestListeners(TestListenerHelper.java:96)
at org.testng.internal.TestInvoker.runTestResultListener(TestInvoker.java:219)
at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:834)
at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:146)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
at org.testng.TestRunner.privateRun(TestRunner.java:794)
at org.testng.TestRunner.run(TestRunner.java:596)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:377)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:371)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:332)
at org.testng.SuiteRunner.run(SuiteRunner.java:276)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1212)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1134)
at org.testng.TestNG.runSuites(TestNG.java:1063)
at org.testng.TestNG.run(TestNG.java:1031)
at com.intellij.rt.testng.IDEARemoteTestNG.run(IDEARemoteTestNG.java:66)
at com.intellij.rt.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:109)
Disconnected from the target VM, address: '127.0.0.1:64835', transport: 'socket'
Process finished with exit code 255
```
### Operating System
macOS Monterey Version 12.5
### Selenium version
Selenium 4.5.0 | openjdk 15.0.8 2022-07-19 | Chrome-driver 4.5.0
### What are the browser(s) and version(s) where you see this issue?
Chrome v.106.0
### What are the browser driver(s) and version(s) where you see this issue?
browserVersion= v.106.0.5249.91
### Are you using Selenium Grid?
Selenium Grid 4.5.0 (revision fe167b119a) | non_process | unable to find an exact match for cdp version so returning the closest version found a no op implementation what happened i am trying to save a screenshot from my remotewebdriver session grid distributed mode and it looks like there is an issue with the websocket connection or the cdp version is not compatiable with selenium java version how can we reproduce the issue shell java code driver webdrivermanager chromedriver remoteaddress capabilities desiredcapabilitiesfactory createchromeoptions create webdriver augmenteddriver new augmenter augment driver srcfile takesscreenshot augmenteddriver getscreenshotas outputtype file relevant log output shell connected to the target vm address transport socket oct pm org openqa selenium remote tracing opentelemetry opentelemetrytracer createtracer info using opentelemetry for tracing oct pm org openqa selenium remote protocolhandshake createsession info detected upstream dialect oct pm org openqa selenium devtools cdpversionfinder findnearestmatch warning unable to find an exact match for cdp version so returning the closest version found a no op implementation oct pm org openqa selenium devtools cdpver oct pm org openqa selenium devtools cdpversionfinder findnearestmatch warning unable to find an exact match for cdp version so returning the closest version found a no op implementation oct pm org openqa selenium devtools cdpversionfinder findnearestmatch info unable to find cdp implementation matching oct pm org openqa selenium remote http netty nettywebsocket lambda new warning connection timed out java net connectexception connection timed out at org asynchttpclient netty channel nettyconnectlistener onfailure nettyconnectlistener java at org asynchttpclient netty channel nettychannelconnector onfailure nettychannelconnector java at org asynchttpclient netty simplechannelfuturelistener operationcomplete simplechannelfuturelistener java at org asynchttpclient netty simplechannelfuturelistener operationcomplete simplechannelfuturelistener java at io netty util concurrent defaultpromise defaultpromise java at io netty util concurrent defaultpromise defaultpromise java at io netty util concurrent defaultpromise notifylistenersnow defaultpromise java at io netty util concurrent defaultpromise notifylisteners defaultpromise java at io netty util concurrent defaultpromise defaultpromise java at io netty util concurrent defaultpromise defaultpromise java at io netty util concurrent defaultpromise tryfailure defaultpromise java at io netty channel nio abstractniochannel abstractniounsafe run abstractniochannel java at io netty util concurrent promisetask runtask promisetask java at io netty util concurrent scheduledfuturetask run scheduledfuturetask java at io netty util concurrent abstracteventexecutor runtask capture abstracteventexecutor java at io netty util concurrent abstracteventexecutor runtask abstracteventexecutor java at io netty util concurrent abstracteventexecutor safeexecute capture abstracteventexecutor java at io netty util concurrent abstracteventexecutor safeexecute abstracteventexecutor java at io netty util concurrent singlethreadeventexecutor runalltasks singlethreadeventexecutor java at io netty channel nio nioeventloop run nioeventloop java at io netty util concurrent singlethreadeventexecutor run singlethreadeventexecutor java at io netty util internal threadexecutormap run threadexecutormap java at io netty util concurrent fastthreadlocalrunnable run fastthreadlocalrunnable java at java base java lang thread run thread java caused by io netty channel connecttimeoutexception connection timed out at io netty channel nio abstractniochannel abstractniounsafe run abstractniochannel java more oct pm org openqa selenium remote http websocket listener onerror warning connection timed out java net connectexception connection timed out at org asynchttpclient netty channel nettyconnectlistener onfailure nettyconnectlistener java at org asynchttpclient netty channel nettychannelconnector onfailure nettychannelconnector java at org asynchttpclient netty simplechannelfuturelistener operationcomplete simplechannelfuturelistener java at org asynchttpclient netty simplechannelfuturelistener operationcomplete simplechannelfuturelistener java at io netty util concurrent defaultpromise defaultpromise java at io netty util concurrent defaultpromise defaultpromise java at io netty util concurrent defaultpromise notifylistenersnow defaultpromise java at io netty util concurrent defaultpromise notifylisteners defaultpromise java at io netty util concurrent defaultpromise defaultpromise java at io netty util concurrent defaultpromise defaultpromise java at io netty util concurrent defaultpromise tryfailure defaultpromise java at io netty channel nio abstractniochannel abstractniounsafe run abstractniochannel java at io netty util concurrent promisetask runtask promisetask java at io netty util concurrent scheduledfuturetask run scheduledfuturetask java at io netty util concurrent abstracteventexecutor runtask capture abstracteventexecutor java at io netty util concurrent abstracteventexecutor runtask abstracteventexecutor java at io netty util concurrent abstracteventexecutor safeexecute capture abstracteventexecutor java at io netty util concurrent abstracteventexecutor safeexecute abstracteventexecutor java at io netty util concurrent singlethreadeventexecutor runalltasks singlethreadeventexecutor java at io netty channel nio nioeventloop run nioeventloop java at io netty util concurrent singlethreadeventexecutor run singlethreadeventexecutor java at io netty util internal threadexecutormap run threadexecutormap java at io netty util concurrent fastthreadlocalrunnable run fastthreadlocalrunnable java at java base java lang thread run thread java caused by io netty channel connecttimeoutexception connection timed out at io netty channel nio abstractniochannel abstractniounsafe run abstractniochannel java more org openqa selenium remote http connectionfailedexception unable to establish websocket connection to build info version revision system info os name mac os x os arch os version java version driver info driver version unknown at org openqa selenium remote http netty nettywebsocket nettywebsocket java at org openqa selenium remote http netty nettywebsocket lambda create nettywebsocket java at org openqa selenium remote http netty nettyclient opensocket nettyclient java at org openqa selenium devtools connection connection java at org openqa selenium devtools seleniumcdpconnection seleniumcdpconnection java at org openqa selenium devtools seleniumcdpconnection lambda create seleniumcdpconnection java at java base java util optional map optional java at org openqa selenium devtools seleniumcdpconnection create seleniumcdpconnection java at org openqa selenium devtools seleniumcdpconnection create seleniumcdpconnection java at org openqa selenium devtools devtoolsprovider getimplementation devtoolsprovider java at org openqa selenium devtools devtoolsprovider getimplementation devtoolsprovider java at org openqa selenium remote augmenter augment augmenter java at de testumgebung testlistener savepng testlistener java at de testumgebung testlistener createscreenshot testlistener java at de testumgebung testlistener ontestfailure testlistener java at org testng internal testlistenerhelper runtestlisteners testlistenerhelper java at org testng internal testinvoker runtestresultlistener testinvoker java at org testng internal testinvoker methodinvocationagent invoke testinvoker java at org testng internal testinvoker invoketestmethods testinvoker java at org testng internal testmethodworker invoketestmethods testmethodworker java at org testng internal testmethodworker run testmethodworker java at java base java util arraylist foreach arraylist java at org testng testrunner privaterun testrunner java at org testng testrunner run testrunner java at org testng suiterunner runtest suiterunner java at org testng suiterunner runsequentially suiterunner java at org testng suiterunner privaterun suiterunner java at org testng suiterunner run suiterunner java at org testng suiterunnerworker runsuite suiterunnerworker java at org testng suiterunnerworker run suiterunnerworker java at org testng testng runsuitessequentially testng java at org testng testng runsuiteslocally testng java at org testng testng runsuites testng java at org testng testng run testng java at com intellij rt testng idearemotetestng run idearemotetestng java at com intellij rt testng remotetestngstarter main remotetestngstarter java disconnected from the target vm address transport socket process finished with exit code operating system macos monterey version selenium version selenium openjdk chrome driver what are the browser s and version s where you see this issue chrome v what are the browser driver s and version s where you see this issue browserversion v are you using selenium grid selenium grid revision | 0 |
77,993 | 15,569,908,899 | IssuesEvent | 2021-03-17 01:16:27 | Killy85/python-bot | https://api.github.com/repos/Killy85/python-bot | opened | CVE-2020-11538 (High) detected in Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl, Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl | security vulnerability | ## CVE-2020-11538 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl</b>, <b>Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary>
<p>
<details><summary><b>Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary>
<p>Python Imaging Library (Fork)</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/0d/f3/421598450cb9503f4565d936860763b5af413a61009d87a5ab1e34139672/Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/0d/f3/421598450cb9503f4565d936860763b5af413a61009d87a5ab1e34139672/Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl</a></p>
<p>Path to vulnerable library: python-bot/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl** (Vulnerable Library)
</details>
<details><summary><b>Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary>
<p>Python Imaging Library (Fork)</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/b6/4b/5adc1109908266554fb978154c797c7d71aba43dd15508d8c1565648f6bc/Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/b6/4b/5adc1109908266554fb978154c797c7d71aba43dd15508d8c1565648f6bc/Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl</a></p>
<p>Path to vulnerable library: python-bot/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl** (Vulnerable Library)
</details>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In libImaging/SgiRleDecode.c in Pillow through 7.0.0, a number of out-of-bounds reads exist in the parsing of SGI image files, a different issue than CVE-2020-5311.
<p>Publish Date: 2020-06-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11538>CVE-2020-11538</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/python-pillow/Pillow/commit/41b554bc56982ee4f30238a7677c0f4ff90a73a8">https://github.com/python-pillow/Pillow/commit/41b554bc56982ee4f30238a7677c0f4ff90a73a8</a></p>
<p>Release Date: 2020-06-25</p>
<p>Fix Resolution: 7.1.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-11538 (High) detected in Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl, Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl - ## CVE-2020-11538 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl</b>, <b>Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary>
<p>
<details><summary><b>Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary>
<p>Python Imaging Library (Fork)</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/0d/f3/421598450cb9503f4565d936860763b5af413a61009d87a5ab1e34139672/Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/0d/f3/421598450cb9503f4565d936860763b5af413a61009d87a5ab1e34139672/Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl</a></p>
<p>Path to vulnerable library: python-bot/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl** (Vulnerable Library)
</details>
<details><summary><b>Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary>
<p>Python Imaging Library (Fork)</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/b6/4b/5adc1109908266554fb978154c797c7d71aba43dd15508d8c1565648f6bc/Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/b6/4b/5adc1109908266554fb978154c797c7d71aba43dd15508d8c1565648f6bc/Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl</a></p>
<p>Path to vulnerable library: python-bot/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl** (Vulnerable Library)
</details>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In libImaging/SgiRleDecode.c in Pillow through 7.0.0, a number of out-of-bounds reads exist in the parsing of SGI image files, a different issue than CVE-2020-5311.
<p>Publish Date: 2020-06-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11538>CVE-2020-11538</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/python-pillow/Pillow/commit/41b554bc56982ee4f30238a7677c0f4ff90a73a8">https://github.com/python-pillow/Pillow/commit/41b554bc56982ee4f30238a7677c0f4ff90a73a8</a></p>
<p>Release Date: 2020-06-25</p>
<p>Fix Resolution: 7.1.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_process | cve high detected in pillow whl pillow whl cve high severity vulnerability vulnerable libraries pillow whl pillow whl pillow whl python imaging library fork library home page a href path to vulnerable library python bot requirements txt dependency hierarchy x pillow whl vulnerable library pillow whl python imaging library fork library home page a href path to vulnerable library python bot requirements txt dependency hierarchy x pillow whl vulnerable library vulnerability details in libimaging sgirledecode c in pillow through a number of out of bounds reads exist in the parsing of sgi image files a different issue than cve publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
289,894 | 32,003,900,981 | IssuesEvent | 2023-09-21 13:49:23 | hughcdemocorp-mend/WebGoat | https://api.github.com/repos/hughcdemocorp-mend/WebGoat | opened | xstream-1.4.5.jar: 35 vulnerabilities (highest severity is: 9.9) reachable | Mend: dependency security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.5.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (xstream version) | Remediation Possible** | Reachability |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- | --- |
| [CVE-2021-21345](https://www.mend.io/vulnerability-database/CVE-2021-21345) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.9 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-21344](https://www.mend.io/vulnerability-database/CVE-2021-21344) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2013-7285](https://www.mend.io/vulnerability-database/CVE-2013-7285) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | xstream-1.4.5.jar | Direct | 1.4.10-java7 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-21350](https://www.mend.io/vulnerability-database/CVE-2021-21350) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-21347](https://www.mend.io/vulnerability-database/CVE-2021-21347) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-21346](https://www.mend.io/vulnerability-database/CVE-2021-21346) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-21342](https://www.mend.io/vulnerability-database/CVE-2021-21342) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.1 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-21351](https://www.mend.io/vulnerability-database/CVE-2021-21351) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.1 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39139](https://www.mend.io/vulnerability-database/CVE-2021-39139) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.8 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> |
| [CVE-2020-26217](https://www.mend.io/vulnerability-database/CVE-2020-26217) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.8 | xstream-1.4.5.jar | Direct | 1.4.13-java7 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-29505](https://www.mend.io/vulnerability-database/CVE-2021-29505) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.8 | xstream-1.4.5.jar | Direct | 1.4.17 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-21349](https://www.mend.io/vulnerability-database/CVE-2021-21349) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.6 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39150](https://www.mend.io/vulnerability-database/CVE-2021-39150) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> |
| [CVE-2021-39152](https://www.mend.io/vulnerability-database/CVE-2021-39152) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39151](https://www.mend.io/vulnerability-database/CVE-2021-39151) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39154](https://www.mend.io/vulnerability-database/CVE-2021-39154) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39153](https://www.mend.io/vulnerability-database/CVE-2021-39153) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39141](https://www.mend.io/vulnerability-database/CVE-2021-39141) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> |
| [CVE-2021-39145](https://www.mend.io/vulnerability-database/CVE-2021-39145) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39144](https://www.mend.io/vulnerability-database/CVE-2021-39144) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39147](https://www.mend.io/vulnerability-database/CVE-2021-39147) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39146](https://www.mend.io/vulnerability-database/CVE-2021-39146) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39149](https://www.mend.io/vulnerability-database/CVE-2021-39149) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39148](https://www.mend.io/vulnerability-database/CVE-2021-39148) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2020-26258](https://www.mend.io/vulnerability-database/CVE-2020-26258) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.7 | xstream-1.4.5.jar | Direct | 1.4.14-jdk7 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-21343](https://www.mend.io/vulnerability-database/CVE-2021-21343) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-21341](https://www.mend.io/vulnerability-database/CVE-2021-21341) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2022-41966](https://www.mend.io/vulnerability-database/CVE-2022-41966) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | xstream-1.4.5.jar | Direct | 1.4.12-java7 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2017-7957](https://www.mend.io/vulnerability-database/CVE-2017-7957) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | xstream-1.4.5.jar | Direct | 1.4.10 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2016-3674](https://www.mend.io/vulnerability-database/CVE-2016-3674) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | xstream-1.4.5.jar | Direct | 1.4.9 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> |
| [CVE-2021-43859](https://www.mend.io/vulnerability-database/CVE-2021-43859) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | xstream-1.4.5.jar | Direct | 1.4.6 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2022-40151](https://www.mend.io/vulnerability-database/CVE-2022-40151) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | xstream-1.4.5.jar | Direct | 1.4.20 | ✅| |
| [CVE-2021-21348](https://www.mend.io/vulnerability-database/CVE-2021-21348) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2020-26259](https://www.mend.io/vulnerability-database/CVE-2020-26259) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.8 | xstream-1.4.5.jar | Direct | 1.4.14-jdk7 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39140](https://www.mend.io/vulnerability-database/CVE-2021-39140) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.3 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
<p>**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation</p>
## Details
> Partial details (17 vulnerabilities) are displayed below due to a content size limitation in GitHub. To view information on the remaining vulnerabilities, navigate to the Mend Application.<br>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-21345</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability which may allow a remote attacker who has sufficient rights to execute commands of the host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-21345>CVE-2021-21345</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.9</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-hwpc-8xqv-jvj4">https://github.com/x-stream/xstream/security/advisories/GHSA-hwpc-8xqv-jvj4</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: 1.4.16</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-21344</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability which may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-21344>CVE-2021-21344</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-59jw-jqf4-3wq3">https://github.com/x-stream/xstream/security/advisories/GHSA-59jw-jqf4-3wq3</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: 1.4.16</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2013-7285</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
Xstream API versions up to 1.4.6 and version 1.4.10, if the security framework has not been initialized, may allow a remote attacker to run arbitrary shell commands by manipulating the processed input stream when unmarshaling XML or any supported format. e.g. JSON.
<p>Publish Date: 2019-05-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2013-7285>CVE-2013-7285</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-7285">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-7285</a></p>
<p>Release Date: 2019-05-15</p>
<p>Fix Resolution: 1.4.10-java7</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-21350</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability which may allow a remote attacker to execute arbitrary code only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-21350>CVE-2021-21350</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-43gc-mjxg-gvrq">https://github.com/x-stream/xstream/security/advisories/GHSA-43gc-mjxg-gvrq</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: 1.4.16</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-21347</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability which may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-21347>CVE-2021-21347</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-qpfq-ph7r-qv6f">https://github.com/x-stream/xstream/security/advisories/GHSA-qpfq-ph7r-qv6f</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: 1.4.16</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-21346</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability which may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-21346>CVE-2021-21346</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-4hrm-m67v-5cxr">https://github.com/x-stream/xstream/security/advisories/GHSA-4hrm-m67v-5cxr</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: 1.4.16</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-21342</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability where the processed stream at unmarshalling time contains type information to recreate the formerly written objects. XStream creates therefore new instances based on these type information. An attacker can manipulate the processed input stream and replace or inject objects, that result in a server-side forgery request. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-21342>CVE-2021-21342</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-hvv8-336g-rx3m">https://github.com/x-stream/xstream/security/advisories/GHSA-hvv8-336g-rx3m</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: 1.4.16</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-21351</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-21351>CVE-2021-21351</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-hrcp-8f3q-4w2c">https://github.com/x-stream/xstream/security/advisories/GHSA-hrcp-8f3q-4w2c</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: 1.4.16</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2021-39139</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
<p>The vulnerable code is not reachable.</p>
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a simple library to serialize objects to XML and back again. In affected versions this vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. A user is only affected if using the version out of the box with JDK 1.7u21 or below. However, this scenario can be adjusted easily to an external Xalan that works regardless of the version of the Java runtime. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. XStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.
<p>Publish Date: 2021-08-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-39139>CVE-2021-39139</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-64xx-cq4q-mf44">https://github.com/x-stream/xstream/security/advisories/GHSA-64xx-cq4q-mf44</a></p>
<p>Release Date: 2021-08-23</p>
<p>Fix Resolution: 1.4.18</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2020-26217</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream before version 1.4.14 is vulnerable to Remote Code Execution.The vulnerability may allow a remote attacker to run arbitrary shell commands only by manipulating the processed input stream. Only users who rely on blocklists are affected. Anyone using XStream's Security Framework allowlist is not affected. The linked advisory provides code workarounds for users who cannot upgrade. The issue is fixed in version 1.4.14.
<p>Publish Date: 2020-11-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-26217>CVE-2020-26217</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-mw36-7c6c-q4q2">https://github.com/x-stream/xstream/security/advisories/GHSA-mw36-7c6c-q4q2</a></p>
<p>Release Date: 2020-11-16</p>
<p>Fix Resolution: 1.4.13-java7</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-29505</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is software for serializing Java objects to XML and back again. A vulnerability in XStream versions prior to 1.4.17 may allow a remote attacker has sufficient rights to execute commands of the host only by manipulating the processed input stream. No user who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types is affected. The vulnerability is patched in version 1.4.17.
<p>Publish Date: 2021-05-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-29505>CVE-2021-29505</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-7chv-rrw6-w6fc">https://github.com/advisories/GHSA-7chv-rrw6-w6fc</a></p>
<p>Release Date: 2021-05-28</p>
<p>Fix Resolution: 1.4.17</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-21349</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability which may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-21349>CVE-2021-21349</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.6</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-f6hm-88x3-mfjv">https://github.com/x-stream/xstream/security/advisories/GHSA-f6hm-88x3-mfjv</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: 1.4.16</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2021-39150</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
<p>The vulnerable code is not reachable.</p>
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a simple library to serialize objects to XML and back again. In affected versions this vulnerability may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream with a Java runtime version 14 to 8. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.18.
<p>Publish Date: 2021-08-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-39150>CVE-2021-39150</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-hph2-m3g5-xxv4">https://github.com/x-stream/xstream/security/advisories/GHSA-hph2-m3g5-xxv4</a></p>
<p>Release Date: 2021-08-23</p>
<p>Fix Resolution: 1.4.18</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-39152</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a simple library to serialize objects to XML and back again. In affected versions this vulnerability may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream with a Java runtime version 14 to 8. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.18.
<p>Publish Date: 2021-08-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-39152>CVE-2021-39152</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-xw4p-crpj-vjx2">https://github.com/x-stream/xstream/security/advisories/GHSA-xw4p-crpj-vjx2</a></p>
<p>Release Date: 2021-08-23</p>
<p>Fix Resolution: 1.4.18</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-39151</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a simple library to serialize objects to XML and back again. In affected versions this vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. XStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.
<p>Publish Date: 2021-08-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-39151>CVE-2021-39151</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-hph2-m3g5-xxv4">https://github.com/x-stream/xstream/security/advisories/GHSA-hph2-m3g5-xxv4</a></p>
<p>Release Date: 2021-08-23</p>
<p>Fix Resolution: 1.4.18</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-39154</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a simple library to serialize objects to XML and back again. In affected versions this vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. XStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.
<p>Publish Date: 2021-08-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-39154>CVE-2021-39154</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-6w62-hx7r-mw68">https://github.com/x-stream/xstream/security/advisories/GHSA-6w62-hx7r-mw68</a></p>
<p>Release Date: 2021-08-23</p>
<p>Fix Resolution: 1.4.18</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-39153</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a simple library to serialize objects to XML and back again. In affected versions this vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream, if using the version out of the box with Java runtime version 14 to 8 or with JavaFX installed. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. XStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.
<p>Publish Date: 2021-08-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-39153>CVE-2021-39153</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39153">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39153</a></p>
<p>Release Date: 2021-08-23</p>
<p>Fix Resolution: 1.4.18</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details>
***
<p>In order to enable automatic remediation for this issue, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p> | True | xstream-1.4.5.jar: 35 vulnerabilities (highest severity is: 9.9) reachable - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.5.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (xstream version) | Remediation Possible** | Reachability |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- | --- |
| [CVE-2021-21345](https://www.mend.io/vulnerability-database/CVE-2021-21345) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.9 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-21344](https://www.mend.io/vulnerability-database/CVE-2021-21344) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2013-7285](https://www.mend.io/vulnerability-database/CVE-2013-7285) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | xstream-1.4.5.jar | Direct | 1.4.10-java7 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-21350](https://www.mend.io/vulnerability-database/CVE-2021-21350) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-21347](https://www.mend.io/vulnerability-database/CVE-2021-21347) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-21346](https://www.mend.io/vulnerability-database/CVE-2021-21346) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-21342](https://www.mend.io/vulnerability-database/CVE-2021-21342) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.1 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-21351](https://www.mend.io/vulnerability-database/CVE-2021-21351) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.1 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39139](https://www.mend.io/vulnerability-database/CVE-2021-39139) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.8 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> |
| [CVE-2020-26217](https://www.mend.io/vulnerability-database/CVE-2020-26217) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.8 | xstream-1.4.5.jar | Direct | 1.4.13-java7 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-29505](https://www.mend.io/vulnerability-database/CVE-2021-29505) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.8 | xstream-1.4.5.jar | Direct | 1.4.17 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-21349](https://www.mend.io/vulnerability-database/CVE-2021-21349) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.6 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39150](https://www.mend.io/vulnerability-database/CVE-2021-39150) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> |
| [CVE-2021-39152](https://www.mend.io/vulnerability-database/CVE-2021-39152) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39151](https://www.mend.io/vulnerability-database/CVE-2021-39151) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39154](https://www.mend.io/vulnerability-database/CVE-2021-39154) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39153](https://www.mend.io/vulnerability-database/CVE-2021-39153) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39141](https://www.mend.io/vulnerability-database/CVE-2021-39141) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> |
| [CVE-2021-39145](https://www.mend.io/vulnerability-database/CVE-2021-39145) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39144](https://www.mend.io/vulnerability-database/CVE-2021-39144) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39147](https://www.mend.io/vulnerability-database/CVE-2021-39147) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39146](https://www.mend.io/vulnerability-database/CVE-2021-39146) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39149](https://www.mend.io/vulnerability-database/CVE-2021-39149) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39148](https://www.mend.io/vulnerability-database/CVE-2021-39148) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2020-26258](https://www.mend.io/vulnerability-database/CVE-2020-26258) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.7 | xstream-1.4.5.jar | Direct | 1.4.14-jdk7 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-21343](https://www.mend.io/vulnerability-database/CVE-2021-21343) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-21341](https://www.mend.io/vulnerability-database/CVE-2021-21341) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2022-41966](https://www.mend.io/vulnerability-database/CVE-2022-41966) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | xstream-1.4.5.jar | Direct | 1.4.12-java7 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2017-7957](https://www.mend.io/vulnerability-database/CVE-2017-7957) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | xstream-1.4.5.jar | Direct | 1.4.10 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2016-3674](https://www.mend.io/vulnerability-database/CVE-2016-3674) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | xstream-1.4.5.jar | Direct | 1.4.9 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> |
| [CVE-2021-43859](https://www.mend.io/vulnerability-database/CVE-2021-43859) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | xstream-1.4.5.jar | Direct | 1.4.6 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2022-40151](https://www.mend.io/vulnerability-database/CVE-2022-40151) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | xstream-1.4.5.jar | Direct | 1.4.20 | ✅| |
| [CVE-2021-21348](https://www.mend.io/vulnerability-database/CVE-2021-21348) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | xstream-1.4.5.jar | Direct | 1.4.16 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2020-26259](https://www.mend.io/vulnerability-database/CVE-2020-26259) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.8 | xstream-1.4.5.jar | Direct | 1.4.14-jdk7 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
| [CVE-2021-39140](https://www.mend.io/vulnerability-database/CVE-2021-39140) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.3 | xstream-1.4.5.jar | Direct | 1.4.18 | ✅|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20>](## 'The vulnerability is likely to be reachable.')</a></p> |
<p>**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation</p>
## Details
> Partial details (17 vulnerabilities) are displayed below due to a content size limitation in GitHub. To view information on the remaining vulnerabilities, navigate to the Mend Application.<br>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-21345</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability which may allow a remote attacker who has sufficient rights to execute commands of the host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-21345>CVE-2021-21345</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.9</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-hwpc-8xqv-jvj4">https://github.com/x-stream/xstream/security/advisories/GHSA-hwpc-8xqv-jvj4</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: 1.4.16</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-21344</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability which may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-21344>CVE-2021-21344</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-59jw-jqf4-3wq3">https://github.com/x-stream/xstream/security/advisories/GHSA-59jw-jqf4-3wq3</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: 1.4.16</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2013-7285</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
Xstream API versions up to 1.4.6 and version 1.4.10, if the security framework has not been initialized, may allow a remote attacker to run arbitrary shell commands by manipulating the processed input stream when unmarshaling XML or any supported format. e.g. JSON.
<p>Publish Date: 2019-05-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2013-7285>CVE-2013-7285</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-7285">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-7285</a></p>
<p>Release Date: 2019-05-15</p>
<p>Fix Resolution: 1.4.10-java7</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-21350</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability which may allow a remote attacker to execute arbitrary code only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-21350>CVE-2021-21350</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-43gc-mjxg-gvrq">https://github.com/x-stream/xstream/security/advisories/GHSA-43gc-mjxg-gvrq</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: 1.4.16</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-21347</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability which may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-21347>CVE-2021-21347</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-qpfq-ph7r-qv6f">https://github.com/x-stream/xstream/security/advisories/GHSA-qpfq-ph7r-qv6f</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: 1.4.16</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-21346</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability which may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-21346>CVE-2021-21346</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-4hrm-m67v-5cxr">https://github.com/x-stream/xstream/security/advisories/GHSA-4hrm-m67v-5cxr</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: 1.4.16</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-21342</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability where the processed stream at unmarshalling time contains type information to recreate the formerly written objects. XStream creates therefore new instances based on these type information. An attacker can manipulate the processed input stream and replace or inject objects, that result in a server-side forgery request. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-21342>CVE-2021-21342</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-hvv8-336g-rx3m">https://github.com/x-stream/xstream/security/advisories/GHSA-hvv8-336g-rx3m</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: 1.4.16</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-21351</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-21351>CVE-2021-21351</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-hrcp-8f3q-4w2c">https://github.com/x-stream/xstream/security/advisories/GHSA-hrcp-8f3q-4w2c</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: 1.4.16</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2021-39139</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
<p>The vulnerable code is not reachable.</p>
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a simple library to serialize objects to XML and back again. In affected versions this vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. A user is only affected if using the version out of the box with JDK 1.7u21 or below. However, this scenario can be adjusted easily to an external Xalan that works regardless of the version of the Java runtime. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. XStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.
<p>Publish Date: 2021-08-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-39139>CVE-2021-39139</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-64xx-cq4q-mf44">https://github.com/x-stream/xstream/security/advisories/GHSA-64xx-cq4q-mf44</a></p>
<p>Release Date: 2021-08-23</p>
<p>Fix Resolution: 1.4.18</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2020-26217</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream before version 1.4.14 is vulnerable to Remote Code Execution.The vulnerability may allow a remote attacker to run arbitrary shell commands only by manipulating the processed input stream. Only users who rely on blocklists are affected. Anyone using XStream's Security Framework allowlist is not affected. The linked advisory provides code workarounds for users who cannot upgrade. The issue is fixed in version 1.4.14.
<p>Publish Date: 2020-11-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-26217>CVE-2020-26217</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-mw36-7c6c-q4q2">https://github.com/x-stream/xstream/security/advisories/GHSA-mw36-7c6c-q4q2</a></p>
<p>Release Date: 2020-11-16</p>
<p>Fix Resolution: 1.4.13-java7</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-29505</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is software for serializing Java objects to XML and back again. A vulnerability in XStream versions prior to 1.4.17 may allow a remote attacker has sufficient rights to execute commands of the host only by manipulating the processed input stream. No user who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types is affected. The vulnerability is patched in version 1.4.17.
<p>Publish Date: 2021-05-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-29505>CVE-2021-29505</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-7chv-rrw6-w6fc">https://github.com/advisories/GHSA-7chv-rrw6-w6fc</a></p>
<p>Release Date: 2021-05-28</p>
<p>Fix Resolution: 1.4.17</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-21349</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability which may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-21349>CVE-2021-21349</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.6</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-f6hm-88x3-mfjv">https://github.com/x-stream/xstream/security/advisories/GHSA-f6hm-88x3-mfjv</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: 1.4.16</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2021-39150</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
<p>The vulnerable code is not reachable.</p>
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a simple library to serialize objects to XML and back again. In affected versions this vulnerability may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream with a Java runtime version 14 to 8. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.18.
<p>Publish Date: 2021-08-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-39150>CVE-2021-39150</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-hph2-m3g5-xxv4">https://github.com/x-stream/xstream/security/advisories/GHSA-hph2-m3g5-xxv4</a></p>
<p>Release Date: 2021-08-23</p>
<p>Fix Resolution: 1.4.18</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-39152</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a simple library to serialize objects to XML and back again. In affected versions this vulnerability may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream with a Java runtime version 14 to 8. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the [Security Framework](https://x-stream.github.io/security.html#framework), you will have to use at least version 1.4.18.
<p>Publish Date: 2021-08-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-39152>CVE-2021-39152</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-xw4p-crpj-vjx2">https://github.com/x-stream/xstream/security/advisories/GHSA-xw4p-crpj-vjx2</a></p>
<p>Release Date: 2021-08-23</p>
<p>Fix Resolution: 1.4.18</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-39151</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a simple library to serialize objects to XML and back again. In affected versions this vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. XStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.
<p>Publish Date: 2021-08-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-39151>CVE-2021-39151</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-hph2-m3g5-xxv4">https://github.com/x-stream/xstream/security/advisories/GHSA-hph2-m3g5-xxv4</a></p>
<p>Release Date: 2021-08-23</p>
<p>Fix Resolution: 1.4.18</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-39154</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a simple library to serialize objects to XML and back again. In affected versions this vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. XStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.
<p>Publish Date: 2021-08-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-39154>CVE-2021-39154</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-6w62-hx7r-mw68">https://github.com/x-stream/xstream/security/advisories/GHSA-6w62-hx7r-mw68</a></p>
<p>Release Date: 2021-08-23</p>
<p>Fix Resolution: 1.4.18</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaRed.png' width=19 height=20> CVE-2021-39153</summary>
### Vulnerable Library - <b>xstream-1.4.5.jar</b></p>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/hughcdemocorp-mend/WebGoat/commit/90ca0683b3d57c0f5483c3728ebe5df4938f2912">90ca0683b3d57c0f5483c3728ebe5df4938f2912</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Reachability Analysis
<p>
This vulnerability is potentially used
```
org.owasp.webgoat.lessons.vulnerablecomponents.VulnerableComponentsLesson (Application)
-> ❌ com.thoughtworks.xstream.XStream (Vulnerable Component)
```
</p>
<p></p>
### Vulnerability Details
<p>
XStream is a simple library to serialize objects to XML and back again. In affected versions this vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream, if using the version out of the box with Java runtime version 14 to 8 or with JavaFX installed. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. XStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose.
<p>Publish Date: 2021-08-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-39153>CVE-2021-39153</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39153">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39153</a></p>
<p>Release Date: 2021-08-23</p>
<p>Fix Resolution: 1.4.18</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details>
***
<p>In order to enable automatic remediation for this issue, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p> | non_process | xstream jar vulnerabilities highest severity is reachable vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to dependency file pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar found in head commit a href vulnerabilities cve severity cvss dependency type fixed in xstream version remediation possible reachability critical xstream jar direct the vulnerability is likely to be reachable critical xstream jar direct the vulnerability is likely to be reachable critical xstream jar direct the vulnerability is likely to be reachable critical xstream jar direct the vulnerability is likely to be reachable critical xstream jar direct the vulnerability is likely to be reachable critical xstream jar direct the vulnerability is likely to be reachable critical xstream jar direct the vulnerability is likely to be reachable critical xstream jar direct the vulnerability is likely to be reachable high xstream jar direct the vulnerability is non reachable high xstream jar direct the vulnerability is likely to be reachable high xstream jar direct the vulnerability is likely to be reachable high xstream jar direct the vulnerability is likely to be reachable high xstream jar direct the vulnerability is non reachable high xstream jar direct the vulnerability is likely to be reachable high xstream jar direct the vulnerability is likely to be reachable high xstream jar direct the vulnerability is likely to be reachable high xstream jar direct the vulnerability is likely to be reachable high xstream jar direct the vulnerability is non reachable high xstream jar direct the vulnerability is likely to be reachable high xstream jar direct the vulnerability is likely to be reachable high xstream jar direct the vulnerability is likely to be reachable high xstream jar direct the vulnerability is likely to be reachable high xstream jar direct the vulnerability is likely to be reachable high xstream jar direct the vulnerability is likely to be reachable high xstream jar direct the vulnerability is likely to be reachable high xstream jar direct the vulnerability is likely to be reachable high xstream jar direct the vulnerability is likely to be reachable high xstream jar direct the vulnerability is likely to be reachable high xstream jar direct the vulnerability is likely to be reachable high xstream jar direct the vulnerability is non reachable high xstream jar direct the vulnerability is likely to be reachable high xstream jar direct high xstream jar direct the vulnerability is likely to be reachable medium xstream jar direct the vulnerability is likely to be reachable medium xstream jar direct the vulnerability is likely to be reachable in some cases remediation pr cannot be created automatically for a vulnerability despite the availability of remediation details partial details vulnerabilities are displayed below due to a content size limitation in github to view information on the remaining vulnerabilities navigate to the mend application cve vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to dependency file pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy x xstream jar vulnerable library found in head commit a href found in base branch main reachability analysis this vulnerability is potentially used org owasp webgoat lessons vulnerablecomponents vulnerablecomponentslesson application ❌ com thoughtworks xstream xstream vulnerable component vulnerability details xstream is a java library to serialize objects to xml and back again in xstream before version there is a vulnerability which may allow a remote attacker who has sufficient rights to execute commands of the host only by manipulating the processed input stream no user is affected who followed the recommendation to setup xstream s security framework with a whitelist limited to the minimal required types if you rely on xstream s default blacklist of the security framework you will have to use at least version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution in order to enable automatic remediation please create cve vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to dependency file pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy x xstream jar vulnerable library found in head commit a href found in base branch main reachability analysis this vulnerability is potentially used org owasp webgoat lessons vulnerablecomponents vulnerablecomponentslesson application ❌ com thoughtworks xstream xstream vulnerable component vulnerability details xstream is a java library to serialize objects to xml and back again in xstream before version there is a vulnerability which may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream no user is affected who followed the recommendation to setup xstream s security framework with a whitelist limited to the minimal required types if you rely on xstream s default blacklist of the security framework you will have to use at least version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution in order to enable automatic remediation please create cve vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to dependency file pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy x xstream jar vulnerable library found in head commit a href found in base branch main reachability analysis this vulnerability is potentially used org owasp webgoat lessons vulnerablecomponents vulnerablecomponentslesson application ❌ com thoughtworks xstream xstream vulnerable component vulnerability details xstream api versions up to and version if the security framework has not been initialized may allow a remote attacker to run arbitrary shell commands by manipulating the processed input stream when unmarshaling xml or any supported format e g json publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution in order to enable automatic remediation please create cve vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to dependency file pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy x xstream jar vulnerable library found in head commit a href found in base branch main reachability analysis this vulnerability is potentially used org owasp webgoat lessons vulnerablecomponents vulnerablecomponentslesson application ❌ com thoughtworks xstream xstream vulnerable component vulnerability details xstream is a java library to serialize objects to xml and back again in xstream before version there is a vulnerability which may allow a remote attacker to execute arbitrary code only by manipulating the processed input stream no user is affected who followed the recommendation to setup xstream s security framework with a whitelist limited to the minimal required types if you rely on xstream s default blacklist of the security framework you will have to use at least version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution in order to enable automatic remediation please create cve vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to dependency file pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy x xstream jar vulnerable library found in head commit a href found in base branch main reachability analysis this vulnerability is potentially used org owasp webgoat lessons vulnerablecomponents vulnerablecomponentslesson application ❌ com thoughtworks xstream xstream vulnerable component vulnerability details xstream is a java library to serialize objects to xml and back again in xstream before version there is a vulnerability which may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream no user is affected who followed the recommendation to setup xstream s security framework with a whitelist limited to the minimal required types if you rely on xstream s default blacklist of the security framework you will have to use at least version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution in order to enable automatic remediation please create cve vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to dependency file pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy x xstream jar vulnerable library found in head commit a href found in base branch main reachability analysis this vulnerability is potentially used org owasp webgoat lessons vulnerablecomponents vulnerablecomponentslesson application ❌ com thoughtworks xstream xstream vulnerable component vulnerability details xstream is a java library to serialize objects to xml and back again in xstream before version there is a vulnerability which may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream no user is affected who followed the recommendation to setup xstream s security framework with a whitelist limited to the minimal required types if you rely on xstream s default blacklist of the security framework you will have to use at least version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution in order to enable automatic remediation please create cve vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to dependency file pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy x xstream jar vulnerable library found in head commit a href found in base branch main reachability analysis this vulnerability is potentially used org owasp webgoat lessons vulnerablecomponents vulnerablecomponentslesson application ❌ com thoughtworks xstream xstream vulnerable component vulnerability details xstream is a java library to serialize objects to xml and back again in xstream before version there is a vulnerability where the processed stream at unmarshalling time contains type information to recreate the formerly written objects xstream creates therefore new instances based on these type information an attacker can manipulate the processed input stream and replace or inject objects that result in a server side forgery request no user is affected who followed the recommendation to setup xstream s security framework with a whitelist limited to the minimal required types if you rely on xstream s default blacklist of the security framework you will have to use at least version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution in order to enable automatic remediation please create cve vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to dependency file pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy x xstream jar vulnerable library found in head commit a href found in base branch main reachability analysis this vulnerability is potentially used org owasp webgoat lessons vulnerablecomponents vulnerablecomponentslesson application ❌ com thoughtworks xstream xstream vulnerable component vulnerability details xstream is a java library to serialize objects to xml and back again in xstream before version there is a vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream no user is affected who followed the recommendation to setup xstream s security framework with a whitelist limited to the minimal required types if you rely on xstream s default blacklist of the security framework you will have to use at least version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required high user interaction none scope changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution in order to enable automatic remediation please create cve vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to dependency file pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy x xstream jar vulnerable library found in head commit a href found in base branch main reachability analysis the vulnerable code is not reachable vulnerability details xstream is a simple library to serialize objects to xml and back again in affected versions this vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream a user is only affected if using the version out of the box with jdk or below however this scenario can be adjusted easily to an external xalan that works regardless of the version of the java runtime no user is affected who followed the recommendation to setup xstream s security framework with a whitelist limited to the minimal required types xstream uses no longer a blacklist by default since it cannot be secured for general purpose publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution in order to enable automatic remediation please create cve vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to dependency file pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy x xstream jar vulnerable library found in head commit a href found in base branch main reachability analysis this vulnerability is potentially used org owasp webgoat lessons vulnerablecomponents vulnerablecomponentslesson application ❌ com thoughtworks xstream xstream vulnerable component vulnerability details xstream before version is vulnerable to remote code execution the vulnerability may allow a remote attacker to run arbitrary shell commands only by manipulating the processed input stream only users who rely on blocklists are affected anyone using xstream s security framework allowlist is not affected the linked advisory provides code workarounds for users who cannot upgrade the issue is fixed in version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution in order to enable automatic remediation please create cve vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to dependency file pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy x xstream jar vulnerable library found in head commit a href found in base branch main reachability analysis this vulnerability is potentially used org owasp webgoat lessons vulnerablecomponents vulnerablecomponentslesson application ❌ com thoughtworks xstream xstream vulnerable component vulnerability details xstream is software for serializing java objects to xml and back again a vulnerability in xstream versions prior to may allow a remote attacker has sufficient rights to execute commands of the host only by manipulating the processed input stream no user who followed the recommendation to setup xstream s security framework with a whitelist limited to the minimal required types is affected the vulnerability is patched in version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution in order to enable automatic remediation please create cve vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to dependency file pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy x xstream jar vulnerable library found in head commit a href found in base branch main reachability analysis this vulnerability is potentially used org owasp webgoat lessons vulnerablecomponents vulnerablecomponentslesson application ❌ com thoughtworks xstream xstream vulnerable component vulnerability details xstream is a java library to serialize objects to xml and back again in xstream before version there is a vulnerability which may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream no user is affected who followed the recommendation to setup xstream s security framework with a whitelist limited to the minimal required types if you rely on xstream s default blacklist of the security framework you will have to use at least version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope changed impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution in order to enable automatic remediation please create cve vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to dependency file pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy x xstream jar vulnerable library found in head commit a href found in base branch main reachability analysis the vulnerable code is not reachable vulnerability details xstream is a simple library to serialize objects to xml and back again in affected versions this vulnerability may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream with a java runtime version to no user is affected who followed the recommendation to setup xstream s security framework with a whitelist limited to the minimal required types if you rely on xstream s default blacklist of the you will have to use at least version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction none scope changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution in order to enable automatic remediation please create cve vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to dependency file pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy x xstream jar vulnerable library found in head commit a href found in base branch main reachability analysis this vulnerability is potentially used org owasp webgoat lessons vulnerablecomponents vulnerablecomponentslesson application ❌ com thoughtworks xstream xstream vulnerable component vulnerability details xstream is a simple library to serialize objects to xml and back again in affected versions this vulnerability may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream with a java runtime version to no user is affected who followed the recommendation to setup xstream s security framework with a whitelist limited to the minimal required types if you rely on xstream s default blacklist of the you will have to use at least version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction none scope changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution in order to enable automatic remediation please create cve vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to dependency file pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy x xstream jar vulnerable library found in head commit a href found in base branch main reachability analysis this vulnerability is potentially used org owasp webgoat lessons vulnerablecomponents vulnerablecomponentslesson application ❌ com thoughtworks xstream xstream vulnerable component vulnerability details xstream is a simple library to serialize objects to xml and back again in affected versions this vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream no user is affected who followed the recommendation to setup xstream s security framework with a whitelist limited to the minimal required types xstream uses no longer a blacklist by default since it cannot be secured for general purpose publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction none scope changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution in order to enable automatic remediation please create cve vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to dependency file pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy x xstream jar vulnerable library found in head commit a href found in base branch main reachability analysis this vulnerability is potentially used org owasp webgoat lessons vulnerablecomponents vulnerablecomponentslesson application ❌ com thoughtworks xstream xstream vulnerable component vulnerability details xstream is a simple library to serialize objects to xml and back again in affected versions this vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream no user is affected who followed the recommendation to setup xstream s security framework with a whitelist limited to the minimal required types xstream uses no longer a blacklist by default since it cannot be secured for general purpose publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction none scope changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution in order to enable automatic remediation please create cve vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to dependency file pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy x xstream jar vulnerable library found in head commit a href found in base branch main reachability analysis this vulnerability is potentially used org owasp webgoat lessons vulnerablecomponents vulnerablecomponentslesson application ❌ com thoughtworks xstream xstream vulnerable component vulnerability details xstream is a simple library to serialize objects to xml and back again in affected versions this vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream if using the version out of the box with java runtime version to or with javafx installed no user is affected who followed the recommendation to setup xstream s security framework with a whitelist limited to the minimal required types xstream uses no longer a blacklist by default since it cannot be secured for general purpose publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction none scope changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution in order to enable automatic remediation please create in order to enable automatic remediation for this issue please create | 0 |
9,652 | 12,624,898,409 | IssuesEvent | 2020-06-14 08:58:49 | frictionlessdata/forum | https://api.github.com/repos/frictionlessdata/forum | closed | Organizing this forum (and triaging issues) | Idea: Improvement Size: ★ Topic: Process | Having some structure to this forum would help us manage stuff as it comes in.
## Job Stories
When someone asks a question I want to make sure it gets answered so that they are helped
When new ideas/suggestions come in I want to triage them by topic and priority so that I can find them again, others can find them ...
## Acceptance
* [x] Have a process **See analysis below**
* [x] Have board and labels setup **Done. Labels created and board for ideas is here https://github.com/frictionlessdata/forum/projects/1**
* [x] Classified current issues **Done. All labels added and ideas in https://github.com/frictionlessdata/forum/projects/1**
## Tasks
* [x] Do an analysis of what is needed **See job stories and analysis below**
* [x] Create proposals for labels and board structure **See below**
* [x] Implement for questions
* [x] Implement for ideas
* [x] Classify existing issues
## Analysis
Two primary categorisations:
* Questions
* Ideas
In more detail
* Question (and Bugs)
* How do i use X
* Can do i do Y
* Speculation ...
* Idea/Suggestion
* New App / Feature
* Improvement to existing
* Discussion (?)
### Topics
Common to both would be classification by topic. An initial list of topics would be:
* Specs
* Tools
* Apps
* Process
* Docs
### Question process
* Label stuff with question
* Regularly review
* If we did have board it would have these states
* No responses ...
* Resolved (FIXED)
* Awaiting response (from them)
* Awaiting answer
### Idea process
* Classify ideas using topics plus additional labels below
* Handle "state" via a board with usual states e.g. in progress, prioritized etc
Create the following dimensions and attributes as labels:
Size
* Small
* Medium
* Large | 1.0 | Organizing this forum (and triaging issues) - Having some structure to this forum would help us manage stuff as it comes in.
## Job Stories
When someone asks a question I want to make sure it gets answered so that they are helped
When new ideas/suggestions come in I want to triage them by topic and priority so that I can find them again, others can find them ...
## Acceptance
* [x] Have a process **See analysis below**
* [x] Have board and labels setup **Done. Labels created and board for ideas is here https://github.com/frictionlessdata/forum/projects/1**
* [x] Classified current issues **Done. All labels added and ideas in https://github.com/frictionlessdata/forum/projects/1**
## Tasks
* [x] Do an analysis of what is needed **See job stories and analysis below**
* [x] Create proposals for labels and board structure **See below**
* [x] Implement for questions
* [x] Implement for ideas
* [x] Classify existing issues
## Analysis
Two primary categorisations:
* Questions
* Ideas
In more detail
* Question (and Bugs)
* How do i use X
* Can do i do Y
* Speculation ...
* Idea/Suggestion
* New App / Feature
* Improvement to existing
* Discussion (?)
### Topics
Common to both would be classification by topic. An initial list of topics would be:
* Specs
* Tools
* Apps
* Process
* Docs
### Question process
* Label stuff with question
* Regularly review
* If we did have board it would have these states
* No responses ...
* Resolved (FIXED)
* Awaiting response (from them)
* Awaiting answer
### Idea process
* Classify ideas using topics plus additional labels below
* Handle "state" via a board with usual states e.g. in progress, prioritized etc
Create the following dimensions and attributes as labels:
Size
* Small
* Medium
* Large | process | organizing this forum and triaging issues having some structure to this forum would help us manage stuff as it comes in job stories when someone asks a question i want to make sure it gets answered so that they are helped when new ideas suggestions come in i want to triage them by topic and priority so that i can find them again others can find them acceptance have a process see analysis below have board and labels setup done labels created and board for ideas is here classified current issues done all labels added and ideas in tasks do an analysis of what is needed see job stories and analysis below create proposals for labels and board structure see below implement for questions implement for ideas classify existing issues analysis two primary categorisations questions ideas in more detail question and bugs how do i use x can do i do y speculation idea suggestion new app feature improvement to existing discussion topics common to both would be classification by topic an initial list of topics would be specs tools apps process docs question process label stuff with question regularly review if we did have board it would have these states no responses resolved fixed awaiting response from them awaiting answer idea process classify ideas using topics plus additional labels below handle state via a board with usual states e g in progress prioritized etc create the following dimensions and attributes as labels size small medium large | 1 |
61,543 | 15,024,823,166 | IssuesEvent | 2021-02-01 20:11:31 | sandboxie-plus/Sandboxie | https://api.github.com/repos/sandboxie-plus/Sandboxie | closed | Sandboxie Plus: restore maximized state from systray | fixed in next build | First, maximize window and close.
systray icon -> contenxt menu -> show/hide = open maximized window, as expected
double left mouse click on systray icon = restore latest manual changed size and position before maximized state. | 1.0 | Sandboxie Plus: restore maximized state from systray - First, maximize window and close.
systray icon -> contenxt menu -> show/hide = open maximized window, as expected
double left mouse click on systray icon = restore latest manual changed size and position before maximized state. | non_process | sandboxie plus restore maximized state from systray first maximize window and close systray icon contenxt menu show hide open maximized window as expected double left mouse click on systray icon restore latest manual changed size and position before maximized state | 0 |
102,066 | 8,816,990,113 | IssuesEvent | 2018-12-30 17:49:59 | zeromq/libzmq | https://api.github.com/repos/zeromq/libzmq | closed | make check error: tests/test_shutdown_stress | Area (Testing) Platform (osx) stale | 
I try to compile libzmq on my mac: Yosemite 10.10.3
After successfully running ./autogen.sh and ./configure , I got the above error while doing make check ,is it curcial for compling libzmq ? I supposed not , but how does it happen and how to fix ? I know it it testing for shutdown not to incur a sigpipe which will cause program core, and afraid of getting some issues at run time if I get round the error.
| 1.0 | make check error: tests/test_shutdown_stress - 
I try to compile libzmq on my mac: Yosemite 10.10.3
After successfully running ./autogen.sh and ./configure , I got the above error while doing make check ,is it curcial for compling libzmq ? I supposed not , but how does it happen and how to fix ? I know it it testing for shutdown not to incur a sigpipe which will cause program core, and afraid of getting some issues at run time if I get round the error.
| non_process | make check error tests test shutdown stress i try to compile libzmq on my mac yosemite after successfully running autogen sh and configure i got the above error while doing make check is it curcial for compling libzmq i supposed not but how does it happen and how to fix i know it it testing for shutdown not to incur a sigpipe which will cause program core and afraid of getting some issues at run time if i get round the error | 0 |
18,972 | 24,947,632,089 | IssuesEvent | 2022-11-01 02:34:46 | solop-develop/frontend-core | https://api.github.com/repos/solop-develop/frontend-core | closed | [Bug Report] Procesos asociados a la pestaña duplicados | bug (PRC) Processes (RPT) Reports (WIN) Windows | <!--
Note: In order to better solve your problem, please refer to the template to provide complete information, accurately describe the problem, and the incomplete information issue will be closed.
-->
## Bug report
#### Steps to reproduce
1. Iniciar sesión con el rol `System`.
2. Abrir la ventana `Window, Tab and Field`.
3. Mostrar los procesos asociados en la pestaña padre.
#### Screenshot or Gif（截图或动态图）
#### Expected behavior
Se espera que no se dupliquen los procesos asociados.
#### Additional context
El proceso que se esta duplicando en esa ventana, esta asociado en una campo tipo botón, y en los procesos asociados a la tabla.
| 1.0 | [Bug Report] Procesos asociados a la pestaña duplicados - <!--
Note: In order to better solve your problem, please refer to the template to provide complete information, accurately describe the problem, and the incomplete information issue will be closed.
-->
## Bug report
#### Steps to reproduce
1. Iniciar sesión con el rol `System`.
2. Abrir la ventana `Window, Tab and Field`.
3. Mostrar los procesos asociados en la pestaña padre.
#### Screenshot or Gif（截图或动态图）
#### Expected behavior
Se espera que no se dupliquen los procesos asociados.
#### Additional context
El proceso que se esta duplicando en esa ventana, esta asociado en una campo tipo botón, y en los procesos asociados a la tabla.
| process | procesos asociados a la pestaña duplicados note in order to better solve your problem please refer to the template to provide complete information accurately describe the problem and the incomplete information issue will be closed bug report steps to reproduce iniciar sesión con el rol system abrir la ventana window tab and field mostrar los procesos asociados en la pestaña padre screenshot or gif（截图或动态图） expected behavior se espera que no se dupliquen los procesos asociados additional context el proceso que se esta duplicando en esa ventana esta asociado en una campo tipo botón y en los procesos asociados a la tabla | 1 |
6,401 | 9,485,783,572 | IssuesEvent | 2019-04-22 11:40:40 | material-components/material-components-ios | https://api.github.com/repos/material-components/material-components-ios | closed | [ActionSheet] Mark ActionSheet theming extension ready | [ActionSheet] type:Process | This was filed as an internal issue. If you are a Googler, please visit [b/130716161](http://b/130716161) for more details.
<!-- Auto-generated content below, do not modify -->
---
#### Internal data
- Associated internal bug: [b/130716161](http://b/130716161) | 1.0 | [ActionSheet] Mark ActionSheet theming extension ready - This was filed as an internal issue. If you are a Googler, please visit [b/130716161](http://b/130716161) for more details.
<!-- Auto-generated content below, do not modify -->
---
#### Internal data
- Associated internal bug: [b/130716161](http://b/130716161) | process | mark actionsheet theming extension ready this was filed as an internal issue if you are a googler please visit for more details internal data associated internal bug | 1 |
181,546 | 14,049,596,932 | IssuesEvent | 2020-11-02 10:29:59 | microsoft/CCF | https://api.github.com/repos/microsoft/CCF | closed | Run forum sample tests in CI | TODO js testing | `samples/apps/forum`, essentially `npm install && npm test`. Some changes may have to be done to `samples/apps/forum/test/util.ts` to allow testing different configurations (enclave type etc). | 1.0 | Run forum sample tests in CI - `samples/apps/forum`, essentially `npm install && npm test`. Some changes may have to be done to `samples/apps/forum/test/util.ts` to allow testing different configurations (enclave type etc). | non_process | run forum sample tests in ci samples apps forum essentially npm install npm test some changes may have to be done to samples apps forum test util ts to allow testing different configurations enclave type etc | 0 |
7,031 | 10,192,211,429 | IssuesEvent | 2019-08-12 10:28:23 | bisq-network/bisq | https://api.github.com/repos/bisq-network/bisq | closed | Cannot distinguish between instant offers and regular offers in portfolio view | in:gui in:trade-process was:dropped | It doesn't seem like someone with multiple offers open can tell which are instant and which aren't.
If I'm stepping away from my desk and need to disable a live offer, I need to check offer details until I find the ones that are instant.
Also, the user will only know the offer is instant if they especially marked it so when creating the payment account—the actual payment method (in this case, "Altcoins Instant") is not specified in the offer details pop-up:
 | 1.0 | Cannot distinguish between instant offers and regular offers in portfolio view - It doesn't seem like someone with multiple offers open can tell which are instant and which aren't.
If I'm stepping away from my desk and need to disable a live offer, I need to check offer details until I find the ones that are instant.
Also, the user will only know the offer is instant if they especially marked it so when creating the payment account—the actual payment method (in this case, "Altcoins Instant") is not specified in the offer details pop-up:
 | process | cannot distinguish between instant offers and regular offers in portfolio view it doesn t seem like someone with multiple offers open can tell which are instant and which aren t if i m stepping away from my desk and need to disable a live offer i need to check offer details until i find the ones that are instant also the user will only know the offer is instant if they especially marked it so when creating the payment account—the actual payment method in this case altcoins instant is not specified in the offer details pop up | 1 |
189,594 | 22,047,072,793 | IssuesEvent | 2022-05-30 03:50:16 | Trinadh465/device_renesas_kernel_AOSP10_r33_CVE-2022-0492 | https://api.github.com/repos/Trinadh465/device_renesas_kernel_AOSP10_r33_CVE-2022-0492 | closed | CVE-2021-26931 (Medium) detected in linuxlinux-4.19.88, linuxlinux-4.19.88 - autoclosed | security vulnerability | ## CVE-2021-26931 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linuxlinux-4.19.88</b>, <b>linuxlinux-4.19.88</b></p></summary>
<p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in the Linux kernel 2.6.39 through 5.10.16, as used in Xen. Block, net, and SCSI backends consider certain errors a plain bug, deliberately causing a kernel crash. For errors potentially being at least under the influence of guests (such as out of memory conditions), it isn't correct to assume a plain bug. Memory allocations potentially causing such crashes occur only when Linux is running in PV mode, though. This affects drivers/block/xen-blkback/blkback.c and drivers/xen/xen-scsiback.c.
<p>Publish Date: 2021-02-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-26931>CVE-2021-26931</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-26931">https://nvd.nist.gov/vuln/detail/CVE-2021-26931</a></p>
<p>Release Date: 2021-02-17</p>
<p>Fix Resolution: linux-libc-headers - 5.13;linux-yocto - 5.4.20+gitAUTOINC+c11911d4d1_f4d7dbafb1,4.8.26+gitAUTOINC+1c60e003c7_27efc3ba68</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-26931 (Medium) detected in linuxlinux-4.19.88, linuxlinux-4.19.88 - autoclosed - ## CVE-2021-26931 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linuxlinux-4.19.88</b>, <b>linuxlinux-4.19.88</b></p></summary>
<p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in the Linux kernel 2.6.39 through 5.10.16, as used in Xen. Block, net, and SCSI backends consider certain errors a plain bug, deliberately causing a kernel crash. For errors potentially being at least under the influence of guests (such as out of memory conditions), it isn't correct to assume a plain bug. Memory allocations potentially causing such crashes occur only when Linux is running in PV mode, though. This affects drivers/block/xen-blkback/blkback.c and drivers/xen/xen-scsiback.c.
<p>Publish Date: 2021-02-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-26931>CVE-2021-26931</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-26931">https://nvd.nist.gov/vuln/detail/CVE-2021-26931</a></p>
<p>Release Date: 2021-02-17</p>
<p>Fix Resolution: linux-libc-headers - 5.13;linux-yocto - 5.4.20+gitAUTOINC+c11911d4d1_f4d7dbafb1,4.8.26+gitAUTOINC+1c60e003c7_27efc3ba68</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_process | cve medium detected in linuxlinux linuxlinux autoclosed cve medium severity vulnerability vulnerable libraries linuxlinux linuxlinux vulnerability details an issue was discovered in the linux kernel through as used in xen block net and scsi backends consider certain errors a plain bug deliberately causing a kernel crash for errors potentially being at least under the influence of guests such as out of memory conditions it isn t correct to assume a plain bug memory allocations potentially causing such crashes occur only when linux is running in pv mode though this affects drivers block xen blkback blkback c and drivers xen xen scsiback c publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution linux libc headers linux yocto gitautoinc gitautoinc step up your open source security game with whitesource | 0 |
253,283 | 8,053,703,799 | IssuesEvent | 2018-08-02 00:37:18 | MSFREACH/msf-reach | https://api.github.com/repos/MSFREACH/msf-reach | closed | error once we click on email address on test environment | High Priority bug | 
This is the case for all email address link
Pretty urgent as we have demo for South Africa tomorrow morning (CET). will do it in test environment. | 1.0 | error once we click on email address on test environment - 
This is the case for all email address link
Pretty urgent as we have demo for South Africa tomorrow morning (CET). will do it in test environment. | non_process | error once we click on email address on test environment this is the case for all email address link pretty urgent as we have demo for south africa tomorrow morning cet will do it in test environment | 0 |
19,570 | 25,887,966,136 | IssuesEvent | 2022-12-14 15:48:53 | daoanhhuy26012001/training-responsive-example | https://api.github.com/repos/daoanhhuy26012001/training-responsive-example | closed | Setup project | in-process | - [x] update package.json
- [x] create .gitignore
- [x] create reset.css
- [x] create variables.css
- [x] add fonts word
- [x] add images
- [x] create index.css
- [x] create index.html | 1.0 | Setup project - - [x] update package.json
- [x] create .gitignore
- [x] create reset.css
- [x] create variables.css
- [x] add fonts word
- [x] add images
- [x] create index.css
- [x] create index.html | process | setup project update package json create gitignore create reset css create variables css add fonts word add images create index css create index html | 1 |
18,456 | 24,548,794,412 | IssuesEvent | 2022-10-12 10:53:56 | GoogleCloudPlatform/fda-mystudies | https://api.github.com/repos/GoogleCloudPlatform/fda-mystudies | closed | [PM] When clicked on Cancel button in My account screen, Admins are navigated to Studies screen | Bug P1 Participant manager Process: Fixed Process: Tested dev | **AR:** When clicked on 'Cancel' button in My account screen, Admins are navigated to 'Studies' screen
**ER:** When clicked on 'Cancel' button in My account screen, Admins should be navigated to 'Sites' screen | 2.0 | [PM] When clicked on Cancel button in My account screen, Admins are navigated to Studies screen - **AR:** When clicked on 'Cancel' button in My account screen, Admins are navigated to 'Studies' screen
**ER:** When clicked on 'Cancel' button in My account screen, Admins should be navigated to 'Sites' screen | process | when clicked on cancel button in my account screen admins are navigated to studies screen ar when clicked on cancel button in my account screen admins are navigated to studies screen er when clicked on cancel button in my account screen admins should be navigated to sites screen | 1 |
14,748 | 18,019,200,576 | IssuesEvent | 2021-09-16 17:09:35 | geneontology/go-ontology | https://api.github.com/repos/geneontology/go-ontology | closed | Merge GO:1902187 negative regulation of viral release from host cell and GO:0044790 negative regulation by host of viral release from host cell | multi-species process | * Merge GO:1902187 negative regulation of viral release from host cell and
GO:0044790 negative regulation by host of viral release from host cell
*Merge and change label to 'suppression of viral release by host'
*change subclass to 'defense response to virus' (instead of GO:1902186 regulation of viral release from host cell) | 1.0 | Merge GO:1902187 negative regulation of viral release from host cell and GO:0044790 negative regulation by host of viral release from host cell - * Merge GO:1902187 negative regulation of viral release from host cell and
GO:0044790 negative regulation by host of viral release from host cell
*Merge and change label to 'suppression of viral release by host'
*change subclass to 'defense response to virus' (instead of GO:1902186 regulation of viral release from host cell) | process | merge go negative regulation of viral release from host cell and go negative regulation by host of viral release from host cell merge go negative regulation of viral release from host cell and go negative regulation by host of viral release from host cell merge and change label to suppression of viral release by host change subclass to defense response to virus instead of go regulation of viral release from host cell | 1 |
63,010 | 15,396,424,616 | IssuesEvent | 2021-03-03 20:37:27 | spack/spack | https://api.github.com/repos/spack/spack | closed | Installation issue: <callpath, mpileaks> | build-error | ### Steps to reproduce the issue
Minimal test case: following the Spack packaging tutorial with Docker (https://spack-tutorial.readthedocs.io/en/latest/tutorial_packaging.html, I used the Docker image for OSX: https://hub.docker.com/editions/community/docker-ce-desktop-mac/), the mpileaks packaging example won't work after adding depends_on('callpath').
<!-- Fill in the exact spec you are trying to build and the relevant part of the error message -->
```console
$ spack install mpileaks
==> Error: '<' not supported between instances of 'str' and 'NoneType'
$ spack install callpath
==> Error: '<' not supported between instances of 'str' and 'NoneType'
```
### Information on your system
It's a Docker image running on Mac OS, 10.15.3 (Catalina).
Spack debug report:
* **Spack:** 0.15.4-1048-165dbf719
* **Python:** 3.6.9
* **Platform:** linux-ubuntu18.04-haswell
<!-- If you have any relevant configuration detail (custom `packages.yaml` or `modules.yaml`, etc.) you can add that here as well. -->
### Additional information
It failed on an early stage, it didn't let me 'spack cd mpileaks', gave the same error shown above.
### General information
<!-- These boxes can be checked by replacing [ ] with [x] or by clicking them after submitting the issue. -->
- [x] I have run `spack debug report` and reported the version of Spack/Python/Platform
- [ ] I have run `spack maintainers <name-of-the-package>` and @mentioned any maintainers
- [ ] I have uploaded the build log and environment files
- [x] I have searched the issues of this repo and believe this is not a duplicate
| 1.0 | Installation issue: <callpath, mpileaks> - ### Steps to reproduce the issue
Minimal test case: following the Spack packaging tutorial with Docker (https://spack-tutorial.readthedocs.io/en/latest/tutorial_packaging.html, I used the Docker image for OSX: https://hub.docker.com/editions/community/docker-ce-desktop-mac/), the mpileaks packaging example won't work after adding depends_on('callpath').
<!-- Fill in the exact spec you are trying to build and the relevant part of the error message -->
```console
$ spack install mpileaks
==> Error: '<' not supported between instances of 'str' and 'NoneType'
$ spack install callpath
==> Error: '<' not supported between instances of 'str' and 'NoneType'
```
### Information on your system
It's a Docker image running on Mac OS, 10.15.3 (Catalina).
Spack debug report:
* **Spack:** 0.15.4-1048-165dbf719
* **Python:** 3.6.9
* **Platform:** linux-ubuntu18.04-haswell
<!-- If you have any relevant configuration detail (custom `packages.yaml` or `modules.yaml`, etc.) you can add that here as well. -->
### Additional information
It failed on an early stage, it didn't let me 'spack cd mpileaks', gave the same error shown above.
### General information
<!-- These boxes can be checked by replacing [ ] with [x] or by clicking them after submitting the issue. -->
- [x] I have run `spack debug report` and reported the version of Spack/Python/Platform
- [ ] I have run `spack maintainers <name-of-the-package>` and @mentioned any maintainers
- [ ] I have uploaded the build log and environment files
- [x] I have searched the issues of this repo and believe this is not a duplicate
| non_process | installation issue steps to reproduce the issue minimal test case following the spack packaging tutorial with docker i used the docker image for osx the mpileaks packaging example won t work after adding depends on callpath console spack install mpileaks error not supported between instances of str and nonetype spack install callpath error not supported between instances of str and nonetype information on your system it s a docker image running on mac os catalina spack debug report spack python platform linux haswell additional information it failed on an early stage it didn t let me spack cd mpileaks gave the same error shown above general information i have run spack debug report and reported the version of spack python platform i have run spack maintainers and mentioned any maintainers i have uploaded the build log and environment files i have searched the issues of this repo and believe this is not a duplicate | 0 |
14,384 | 17,402,348,882 | IssuesEvent | 2021-08-02 21:44:58 | googleapis/python-firestore | https://api.github.com/repos/googleapis/python-firestore | opened | Split out system tests into separate Kokoro job | type: process | Working to reduce CI latency.Here are timings on my local machine (note the pre-run with `--install-only` to avoid measuring virtualenv creation time):
```bash
$ for job in $(nox --list | grep "^\*" | cut -d " " -f 2); do
echo $job;
nox -e $job --install-only;
time nox -re $job;
done
lint
nox > Running session lint
nox > Creating virtual environment (virtualenv) using python3.8 in .nox/lint
nox > python -m pip install flake8 black==19.10b0
nox > Skipping black run, as --install-only is set.
nox > Skipping flake8 run, as --install-only is set.
nox > Session lint was successful.
nox > Running session lint
nox > Re-using existing virtual environment at .nox/lint.
nox > python -m pip install flake8 black==19.10b0
nox > black --check docs google tests noxfile.py setup.py
All done! ✨ 🍰 ✨
109 files would be left unchanged.
nox > flake8 google tests
nox > Session lint was successful.
real 0m3.902s
user 0m16.218s
sys 0m0.277s
blacken
nox > Running session blacken
nox > Creating virtual environment (virtualenv) using python3.8 in .nox/blacken
nox > python -m pip install black==19.10b0
nox > Skipping black run, as --install-only is set.
nox > Session blacken was successful.
nox > Running session blacken
nox > Re-using existing virtual environment at .nox/blacken.
nox > python -m pip install black==19.10b0
nox > black docs google tests noxfile.py setup.py
All done! ✨ 🍰 ✨
109 files left unchanged.
nox > Session blacken was successful.
real 0m1.007s
user 0m0.884s
sys 0m0.127s
lint_setup_py
nox > Running session lint_setup_py
nox > Creating virtual environment (virtualenv) using python3.8 in .nox/lint_setup_py
nox > python -m pip install docutils pygments
nox > Skipping python run, as --install-only is set.
nox > Session lint_setup_py was successful.
nox > Running session lint_setup_py
nox > Re-using existing virtual environment at .nox/lint_setup_py.
nox > python -m pip install docutils pygments
nox > python setup.py check --restructuredtext --strict
running check
nox > Session lint_setup_py was successful.
real 0m1.067s
user 0m0.946s
sys 0m0.123s
unit-3.6
nox > Running session unit-3.6
nox > Creating virtual environment (virtualenv) using python3.6 in .nox/unit-3-6
nox > python -m pip install asyncmock pytest-asyncio -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.6.txt
nox > python -m pip install mock pytest pytest-cov aiounittest -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.6.txt
nox > python -m pip install -e . -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.6.txt
nox > Skipping py.test run, as --install-only is set.
nox > Session unit-3.6 was successful.
nox > Running session unit-3.6
nox > Re-using existing virtual environment at .nox/unit-3-6.
nox > python -m pip install asyncmock pytest-asyncio -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.6.txt
nox > python -m pip install mock pytest pytest-cov aiounittest -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.6.txt
nox > python -m pip install -e . -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.6.txt
nox > py.test --quiet --junitxml=unit_3.6_sponge_log.xml --cov=google/cloud --cov=tests/unit --cov-append --cov-config=.coveragerc --cov-report= --cov-fail-under=0 tests/unit
........................................................................ [ 5%]
...............................................................s..s.ss.. [ 10%]
........................................................................ [ 15%]
........................................................................ [ 20%]
...................................................s..s.ss.............. [ 25%]
........................................................................ [ 30%]
........................................................................ [ 35%]
........................................................................ [ 40%]
........................................................................ [ 45%]
........................................................................ [ 50%]
........................................................................ [ 55%]
........................................................................ [ 60%]
........................................................................ [ 65%]
........................................................................ [ 70%]
............................................................ssssssssssss [ 75%]
ssssssssssssssssssssssssssssssss........................................ [ 80%]
........................................................................ [ 85%]
........................................................................ [ 90%]
........................................................................ [ 95%]
........................................................... [100%]
- generated xml file: /home/tseaver/projects/agendaless/Google/src/python-firestore/unit_3.6_sponge_log.xml -
1375 passed, 52 skipped in 14.10s
nox > Session unit-3.6 was successful.
real 0m18.388s
user 0m17.654s
sys 0m0.675s
unit-3.7
nox > Running session unit-3.7
nox > Creating virtual environment (virtualenv) using python3.7 in .nox/unit-3-7
nox > python -m pip install asyncmock pytest-asyncio -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.7.txt
nox > python -m pip install mock pytest pytest-cov aiounittest -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.7.txt
nox > python -m pip install -e . -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.7.txt
nox > Skipping py.test run, as --install-only is set.
nox > Session unit-3.7 was successful.
nox > Running session unit-3.7
nox > Re-using existing virtual environment at .nox/unit-3-7.
nox > python -m pip install asyncmock pytest-asyncio -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.7.txt
nox > python -m pip install mock pytest pytest-cov aiounittest -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.7.txt
nox > python -m pip install -e . -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.7.txt
nox > py.test --quiet --junitxml=unit_3.7_sponge_log.xml --cov=google/cloud --cov=tests/unit --cov-append --cov-config=.coveragerc --cov-report= --cov-fail-under=0 tests/unit
........................................................................ [ 5%]
................................................................s..s..ss [ 10%]
........................................................................ [ 15%]
........................................................................ [ 20%]
....................................................s..s..ss............ [ 25%]
........................................................................ [ 30%]
........................................................................ [ 35%]
........................................................................ [ 40%]
........................................................................ [ 45%]
........................................................................ [ 50%]
........................................................................ [ 55%]
........................................................................ [ 60%]
........................................................................ [ 65%]
........................................................................ [ 70%]
............................................................ssssssssssss [ 75%]
ssssssssssssssssssssssssssssssss........................................ [ 80%]
........................................................................ [ 85%]
........................................................................ [ 90%]
........................................................................ [ 95%]
........................................................... [100%]
- generated xml file: /home/tseaver/projects/agendaless/Google/src/python-firestore/unit_3.7_sponge_log.xml -
1375 passed, 52 skipped in 14.09s
nox > Session unit-3.7 was successful.
real 0m17.930s
user 0m17.185s
sys 0m0.732s
unit-3.8
nox > Running session unit-3.8
nox > Creating virtual environment (virtualenv) using python3.8 in .nox/unit-3-8
nox > python -m pip install asyncmock pytest-asyncio -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.8.txt
nox > python -m pip install mock pytest pytest-cov aiounittest -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.8.txt
nox > python -m pip install -e . -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.8.txt
nox > Skipping py.test run, as --install-only is set.
nox > Session unit-3.8 was successful.
nox > Running session unit-3.8
nox > Re-using existing virtual environment at .nox/unit-3-8.
nox > python -m pip install asyncmock pytest-asyncio -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.8.txt
nox > python -m pip install mock pytest pytest-cov aiounittest -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.8.txt
nox > python -m pip install -e . -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.8.txt
nox > py.test --quiet --junitxml=unit_3.8_sponge_log.xml --cov=google/cloud --cov=tests/unit --cov-append --cov-config=.coveragerc --cov-report= --cov-fail-under=0 tests/unit
........................................................................ [ 5%]
................................................................s..s..ss [ 10%]
........................................................................ [ 15%]
........................................................................ [ 20%]
....................................................s..s..ss............ [ 25%]
........................................................................ [ 30%]
........................................................................ [ 35%]
........................................................................ [ 40%]
........................................................................ [ 45%]
........................................................................ [ 50%]
........................................................................ [ 55%]
........................................................................ [ 60%]
........................................................................ [ 65%]
........................................................................ [ 70%]
............................................................ssssssssssss [ 75%]
ssssssssssssssssssssssssssssssss........................................ [ 80%]
........................................................................ [ 85%]
........................................................................ [ 90%]
........................................................................ [ 95%]
........................................................... [100%]
- generated xml file: /home/tseaver/projects/agendaless/Google/src/python-firestore/unit_3.8_sponge_log.xml -
1375 passed, 52 skipped in 13.40s
nox > Session unit-3.8 was successful.
real 0m17.162s
user 0m16.517s
sys 0m0.638s
unit-3.9
nox > Running session unit-3.9
nox > Creating virtual environment (virtualenv) using python3.9 in .nox/unit-3-9
nox > python -m pip install asyncmock pytest-asyncio -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.9.txt
nox > python -m pip install mock pytest pytest-cov aiounittest -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.9.txt
nox > python -m pip install -e . -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.9.txt
nox > Skipping py.test run, as --install-only is set.
nox > Session unit-3.9 was successful.
nox > Running session unit-3.9
nox > Re-using existing virtual environment at .nox/unit-3-9.
nox > python -m pip install asyncmock pytest-asyncio -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.9.txt
nox > python -m pip install mock pytest pytest-cov aiounittest -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.9.txt
nox > python -m pip install -e . -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.9.txt
nox > py.test --quiet --junitxml=unit_3.9_sponge_log.xml --cov=google/cloud --cov=tests/unit --cov-append --cov-config=.coveragerc --cov-report= --cov-fail-under=0 tests/unit
........................................................................ [ 5%]
................................................................s..s..ss [ 10%]
........................................................................ [ 15%]
........................................................................ [ 20%]
....................................................s..s..ss............ [ 25%]
........................................................................ [ 30%]
........................................................................ [ 35%]
........................................................................ [ 40%]
........................................................................ [ 45%]
........................................................................ [ 50%]
........................................................................ [ 55%]
........................................................................ [ 60%]
........................................................................ [ 65%]
........................................................................ [ 70%]
............................................................ssssssssssss [ 75%]
ssssssssssssssssssssssssssssssss........................................ [ 80%]
........................................................................ [ 85%]
........................................................................ [ 90%]
........................................................................ [ 95%]
........................................................... [100%]
- generated xml file: /home/tseaver/projects/agendaless/Google/src/python-firestore/unit_3.9_sponge_log.xml -
1375 passed, 52 skipped in 15.70s
nox > Session unit-3.9 was successful.
real 0m19.250s
user 0m18.510s
sys 0m0.715s
system-3.7
nox > Running session system-3.7
nox > Creating virtual environment (virtualenv) using python3.7 in .nox/system-3-7
nox > python -m pip install --pre grpcio
nox > python -m pip install mock pytest google-cloud-testutils pytest-asyncio -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.7.txt
nox > python -m pip install -e . -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.7.txt
nox > Skipping py.test run, as --install-only is set.
nox > Session system-3.7 was successful.
nox > Running session system-3.7
nox > Re-using existing virtual environment at .nox/system-3-7.
nox > python -m pip install --pre grpcio
nox > python -m pip install mock pytest google-cloud-testutils pytest-asyncio -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.7.txt
nox > python -m pip install -e . -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.7.txt
nox > py.test --verbose --junitxml=system_3.7_sponge_log.xml tests/system
============================= test session starts ==============================
platform linux -- Python 3.7.6, pytest-6.2.4, py-1.10.0, pluggy-0.13.1 -- /home/tseaver/projects/agendaless/Google/src/python-firestore/.nox/system-3-7/bin/python
cachedir: .pytest_cache
rootdir: /home/tseaver/projects/agendaless/Google/src/python-firestore
plugins: asyncio-0.15.1
collected 77 items
tests/system/test_system.py::test_collections PASSED [ 1%]
tests/system/test_system.py::test_collections_w_import PASSED [ 2%]
tests/system/test_system.py::test_create_document PASSED [ 3%]
tests/system/test_system.py::test_create_document_w_subcollection PASSED [ 5%]
tests/system/test_system.py::test_cannot_use_foreign_key PASSED [ 6%]
tests/system/test_system.py::test_no_document PASSED [ 7%]
tests/system/test_system.py::test_document_set PASSED [ 9%]
tests/system/test_system.py::test_document_integer_field PASSED [ 10%]
tests/system/test_system.py::test_document_set_merge PASSED [ 11%]
tests/system/test_system.py::test_document_set_w_int_field PASSED [ 12%]
tests/system/test_system.py::test_document_update_w_int_field PASSED [ 14%]
tests/system/test_system.py::test_update_document PASSED [ 15%]
tests/system/test_system.py::test_document_get PASSED [ 16%]
tests/system/test_system.py::test_document_delete PASSED [ 18%]
tests/system/test_system.py::test_collection_add PASSED [ 19%]
tests/system/test_system.py::test_query_stream_w_simple_field_eq_op PASSED [ 20%]
tests/system/test_system.py::test_query_stream_w_simple_field_array_contains_op PASSED [ 22%]
tests/system/test_system.py::test_query_stream_w_simple_field_in_op PASSED [ 23%]
tests/system/test_system.py::test_query_stream_w_not_eq_op PASSED [ 24%]
tests/system/test_system.py::test_query_stream_w_simple_not_in_op PASSED [ 25%]
tests/system/test_system.py::test_query_stream_w_simple_field_array_contains_any_op PASSED [ 27%]
tests/system/test_system.py::test_query_stream_w_order_by PASSED [ 28%]
tests/system/test_system.py::test_query_stream_w_field_path PASSED [ 29%]
tests/system/test_system.py::test_query_stream_w_start_end_cursor PASSED [ 31%]
tests/system/test_system.py::test_query_stream_wo_results PASSED [ 32%]
tests/system/test_system.py::test_query_stream_w_projection PASSED [ 33%]
tests/system/test_system.py::test_query_stream_w_multiple_filters PASSED [ 35%]
tests/system/test_system.py::test_query_stream_w_offset PASSED [ 36%]
tests/system/test_system.py::test_query_with_order_dot_key PASSED [ 37%]
tests/system/test_system.py::test_query_unary PASSED [ 38%]
tests/system/test_system.py::test_collection_group_queries PASSED [ 40%]
tests/system/test_system.py::test_collection_group_queries_startat_endat PASSED [ 41%]
tests/system/test_system.py::test_collection_group_queries_filters PASSED [ 42%]
tests/system/test_system.py::test_partition_query_no_partitions PASSED [ 44%]
tests/system/test_system.py::test_partition_query PASSED [ 45%]
tests/system/test_system.py::test_get_all PASSED [ 46%]
tests/system/test_system.py::test_batch PASSED [ 48%]
tests/system/test_system.py::test_watch_document PASSED [ 49%]
tests/system/test_system.py::test_watch_collection PASSED [ 50%]
tests/system/test_system.py::test_watch_query PASSED [ 51%]
tests/system/test_system.py::test_array_union PASSED [ 53%]
tests/system/test_system.py::test_watch_query_order PASSED [ 54%]
tests/system/test_system_async.py::test_collections PASSED [ 55%]
tests/system/test_system_async.py::test_collections_w_import PASSED [ 57%]
tests/system/test_system_async.py::test_create_document PASSED [ 58%]
tests/system/test_system_async.py::test_create_document_w_subcollection PASSED [ 59%]
tests/system/test_system_async.py::test_cannot_use_foreign_key PASSED [ 61%]
tests/system/test_system_async.py::test_no_document PASSED [ 62%]
tests/system/test_system_async.py::test_document_set PASSED [ 63%]
tests/system/test_system_async.py::test_document_integer_field PASSED [ 64%]
tests/system/test_system_async.py::test_document_set_merge PASSED [ 66%]
tests/system/test_system_async.py::test_document_set_w_int_field PASSED [ 67%]
tests/system/test_system_async.py::test_document_update_w_int_field PASSED [ 68%]
tests/system/test_system_async.py::test_update_document PASSED [ 70%]
tests/system/test_system_async.py::test_document_get PASSED [ 71%]
tests/system/test_system_async.py::test_document_delete PASSED [ 72%]
tests/system/test_system_async.py::test_collection_add PASSED [ 74%]
tests/system/test_system_async.py::test_query_stream_w_simple_field_eq_op PASSED [ 75%]
tests/system/test_system_async.py::test_query_stream_w_simple_field_array_contains_op PASSED [ 76%]
tests/system/test_system_async.py::test_query_stream_w_simple_field_in_op PASSED [ 77%]
tests/system/test_system_async.py::test_query_stream_w_simple_field_array_contains_any_op PASSED [ 79%]
tests/system/test_system_async.py::test_query_stream_w_order_by PASSED [ 80%]
tests/system/test_system_async.py::test_query_stream_w_field_path PASSED [ 81%]
tests/system/test_system_async.py::test_query_stream_w_start_end_cursor PASSED [ 83%]
tests/system/test_system_async.py::test_query_stream_wo_results PASSED [ 84%]
tests/system/test_system_async.py::test_query_stream_w_projection PASSED [ 85%]
tests/system/test_system_async.py::test_query_stream_w_multiple_filters PASSED [ 87%]
tests/system/test_system_async.py::test_query_stream_w_offset PASSED [ 88%]
tests/system/test_system_async.py::test_query_with_order_dot_key PASSED [ 89%]
tests/system/test_system_async.py::test_query_unary PASSED [ 90%]
tests/system/test_system_async.py::test_collection_group_queries PASSED [ 92%]
tests/system/test_system_async.py::test_collection_group_queries_startat_endat PASSED [ 93%]
tests/system/test_system_async.py::test_collection_group_queries_filters PASSED [ 94%]
tests/system/test_system_async.py::test_partition_query_no_partitions PASSED [ 96%]
tests/system/test_system_async.py::test_partition_query PASSED [ 97%]
tests/system/test_system_async.py::test_get_all PASSED [ 98%]
tests/system/test_system_async.py::test_batch PASSED [100%]
=================== 77 passed in 211.00s (0:03:31) ===================
nox > Command py.test --verbose --junitxml=system_3.7_sponge_log.xml tests/system passed
nox > Session system-3.7 was successful.
real 3m34.561s
user 0m11.371s
sys 0m1.881s
cover
nox > Running session cover
nox > Creating virtual environment (virtualenv) using python3.8 in .nox/cover
nox > python -m pip install coverage pytest-cov
nox > Skipping coverage run, as --install-only is set.
nox > Skipping coverage run, as --install-only is set.
nox > Session cover was successful.
nox > Running session cover
nox > Re-using existing virtual environment at .nox/cover.
nox > python -m pip install coverage pytest-cov
nox > coverage report --show-missing --fail-under=100
Name Stmts Miss Branch BrPart Cover Missing
---------------------------------------------------------------------------------------------------------------------------------
google/cloud/firestore.py 35 0 0 0 100%
google/cloud/firestore_admin_v1/__init__.py 23 0 0 0 100%
google/cloud/firestore_admin_v1/services/__init__.py 0 0 0 0 100%
google/cloud/firestore_admin_v1/services/firestore_admin/__init__.py 3 0 0 0 100%
google/cloud/firestore_admin_v1/services/firestore_admin/async_client.py 168 0 38 0 100%
google/cloud/firestore_admin_v1/services/firestore_admin/client.py 282 0 90 0 100%
google/cloud/firestore_admin_v1/services/firestore_admin/pagers.py 82 0 20 0 100%
google/cloud/firestore_admin_v1/services/firestore_admin/transports/__init__.py 9 0 0 0 100%
google/cloud/firestore_admin_v1/services/firestore_admin/transports/base.py 72 0 12 0 100%
google/cloud/firestore_admin_v1/services/firestore_admin/transports/grpc.py 100 0 34 0 100%
google/cloud/firestore_admin_v1/services/firestore_admin/transports/grpc_asyncio.py 103 0 34 0 100%
google/cloud/firestore_admin_v1/types/__init__.py 6 0 0 0 100%
google/cloud/firestore_admin_v1/types/field.py 12 0 0 0 100%
google/cloud/firestore_admin_v1/types/firestore_admin.py 48 0 0 0 100%
google/cloud/firestore_admin_v1/types/index.py 28 0 0 0 100%
google/cloud/firestore_admin_v1/types/location.py 4 0 0 0 100%
google/cloud/firestore_admin_v1/types/operation.py 57 0 0 0 100%
google/cloud/firestore_bundle/__init__.py 7 0 0 0 100%
google/cloud/firestore_bundle/_helpers.py 4 0 0 0 100%
google/cloud/firestore_bundle/bundle.py 111 0 32 0 100%
google/cloud/firestore_bundle/services/__init__.py 0 0 0 0 100%
google/cloud/firestore_bundle/types/__init__.py 2 0 0 0 100%
google/cloud/firestore_bundle/types/bundle.py 33 0 0 0 100%
google/cloud/firestore_v1/__init__.py 37 0 0 0 100%
google/cloud/firestore_v1/_helpers.py 478 0 240 0 100%
google/cloud/firestore_v1/async_batch.py 19 0 2 0 100%
google/cloud/firestore_v1/async_client.py 41 0 4 0 100%
google/cloud/firestore_v1/async_collection.py 32 0 4 0 100%
google/cloud/firestore_v1/async_document.py 44 0 4 0 100%
google/cloud/firestore_v1/async_query.py 45 0 16 0 100%
google/cloud/firestore_v1/async_transaction.py 98 0 22 0 100%
google/cloud/firestore_v1/base_batch.py 32 0 4 0 100%
google/cloud/firestore_v1/base_client.py 151 0 42 0 100%
google/cloud/firestore_v1/base_collection.py 101 0 16 0 100%
google/cloud/firestore_v1/base_document.py 145 0 24 0 100%
google/cloud/firestore_v1/base_query.py 331 0 130 0 100%
google/cloud/firestore_v1/base_transaction.py 65 0 6 0 100%
google/cloud/firestore_v1/batch.py 19 0 2 0 100%
google/cloud/firestore_v1/client.py 42 0 4 0 100%
google/cloud/firestore_v1/collection.py 30 0 2 0 100%
google/cloud/firestore_v1/document.py 48 0 4 0 100%
google/cloud/firestore_v1/field_path.py 135 0 56 0 100%
google/cloud/firestore_v1/order.py 130 0 54 0 100%
google/cloud/firestore_v1/query.py 47 0 14 0 100%
google/cloud/firestore_v1/services/__init__.py 0 0 0 0 100%
google/cloud/firestore_v1/services/firestore/__init__.py 3 0 0 0 100%
google/cloud/firestore_v1/services/firestore/async_client.py 178 0 30 0 100%
google/cloud/firestore_v1/services/firestore/client.py 276 0 90 0 100%
google/cloud/firestore_v1/services/firestore/pagers.py 121 0 30 0 100%
google/cloud/firestore_v1/services/firestore/transports/__init__.py 9 0 0 0 100%
google/cloud/firestore_v1/services/firestore/transports/base.py 80 0 12 0 100%
google/cloud/firestore_v1/services/firestore/transports/grpc.py 122 0 44 0 100%
google/cloud/firestore_v1/services/firestore/transports/grpc_asyncio.py 125 0 44 0 100%
google/cloud/firestore_v1/transaction.py 97 0 22 0 100%
google/cloud/firestore_v1/transforms.py 39 0 10 0 100%
google/cloud/firestore_v1/types/__init__.py 6 0 0 0 100%
google/cloud/firestore_v1/types/common.py 16 0 0 0 100%
google/cloud/firestore_v1/types/document.py 27 0 0 0 100%
google/cloud/firestore_v1/types/firestore.py 157 0 0 0 100%
google/cloud/firestore_v1/types/query.py 66 0 0 0 100%
google/cloud/firestore_v1/types/write.py 45 0 0 0 100%
google/cloud/firestore_v1/watch.py 325 0 78 0 100%
tests/unit/__init__.py 0 0 0 0 100%
tests/unit/test_firestore_shim.py 10 0 2 0 100%
tests/unit/v1/__init__.py 0 0 0 0 100%
tests/unit/v1/_test_helpers.py 22 0 0 0 100%
tests/unit/v1/conformance_tests.py 106 0 0 0 100%
tests/unit/v1/test__helpers.py 1653 0 36 0 100%
tests/unit/v1/test_async_batch.py 98 0 0 0 100%
tests/unit/v1/test_async_client.py 267 0 18 0 100%
tests/unit/v1/test_async_collection.py 223 0 20 0 100%
tests/unit/v1/test_async_document.py 334 0 32 0 100%
tests/unit/v1/test_async_query.py 327 0 26 0 100%
tests/unit/v1/test_async_transaction.py 584 0 0 0 100%
tests/unit/v1/test_base_batch.py 98 0 0 0 100%
tests/unit/v1/test_base_client.py 238 0 0 0 100%
tests/unit/v1/test_base_collection.py 239 0 0 0 100%
tests/unit/v1/test_base_document.py 293 0 2 0 100%
tests/unit/v1/test_base_query.py 1006 0 20 0 100%
tests/unit/v1/test_base_transaction.py 75 0 0 0 100%
tests/unit/v1/test_batch.py 92 0 0 0 100%
tests/unit/v1/test_bundle.py 268 0 4 0 100%
tests/unit/v1/test_client.py 256 0 12 0 100%
tests/unit/v1/test_collection.py 197 0 10 0 100%
tests/unit/v1/test_cross_language.py 207 0 82 0 100%
tests/unit/v1/test_document.py 307 0 26 0 100%
tests/unit/v1/test_field_path.py 355 0 8 0 100%
tests/unit/v1/test_order.py 138 0 8 0 100%
tests/unit/v1/test_query.py 318 0 0 0 100%
tests/unit/v1/test_transaction.py 560 0 0 0 100%
tests/unit/v1/test_transforms.py 78 0 8 0 100%
tests/unit/v1/test_watch.py 667 0 4 0 100%
---------------------------------------------------------------------------------------------------------------------------------
TOTAL 13967 0 1588 0 100%
nox > coverage erase
nox > Session cover was successful.
real 0m3.581s
user 0m3.419s
sys 0m0.163s
docs
nox > Running session docs
nox > Creating virtual environment (virtualenv) using python3.8 in .nox/docs
nox > python -m pip install -e .
nox > python -m pip install sphinx==4.0.1 alabaster recommonmark
nox > Skipping sphinx-build run, as --install-only is set.
nox > Session docs was successful.
nox > Running session docs
nox > Re-using existing virtual environment at .nox/docs.
nox > python -m pip install -e .
nox > python -m pip install sphinx==4.0.1 alabaster recommonmark
nox > sphinx-build -W -T -N -b html -d docs/_build/doctrees/ docs/ docs/_build/html/
Running Sphinx v4.0.1
making output directory... done
[autosummary] generating autosummary for: README.rst, UPGRADING.md, admin_client.rst, batch.rst, changelog.md, client.rst, collection.rst, document.rst, field_path.rst, index.rst, multiprocessing.rst, query.rst, transaction.rst, transforms.rst, types.rst
loading intersphinx inventory from https://python.readthedocs.org/en/latest/objects.inv...
loading intersphinx inventory from https://googleapis.dev/python/google-auth/latest/objects.inv...
loading intersphinx inventory from https://googleapis.dev/python/google-api-core/latest/objects.inv...
loading intersphinx inventory from https://grpc.github.io/grpc/python/objects.inv...
loading intersphinx inventory from https://proto-plus-python.readthedocs.io/en/latest/objects.inv...
loading intersphinx inventory from https://googleapis.dev/python/protobuf/latest/objects.inv...
intersphinx inventory has moved: https://python.readthedocs.org/en/latest/objects.inv -> https://python.readthedocs.io/en/latest/objects.inv
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 15 source files that are out of date
updating environment: [new config] 15 added, 0 changed, 0 removed
reading sources... [ 6%] README
reading sources... [ 13%] UPGRADING
/home/tseaver/projects/agendaless/Google/src/python-firestore/.nox/docs/lib/python3.8/site-packages/recommonmark/parser.py:75: UserWarning: Container node skipped: type=document
warn("Container node skipped: type={0}".format(mdnode.t))
reading sources... [ 20%] admin_client
reading sources... [ 26%] batch
reading sources... [ 33%] changelog
/home/tseaver/projects/agendaless/Google/src/python-firestore/.nox/docs/lib/python3.8/site-packages/recommonmark/parser.py:75: UserWarning: Container node skipped: type=document
warn("Container node skipped: type={0}".format(mdnode.t))
reading sources... [ 40%] client
reading sources... [ 46%] collection
reading sources... [ 53%] document
reading sources... [ 60%] field_path
reading sources... [ 66%] index
reading sources... [ 73%] multiprocessing
reading sources... [ 80%] query
reading sources... [ 86%] transaction
reading sources... [ 93%] transforms
reading sources... [100%] types
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
writing output... [ 6%] README
writing output... [ 13%] UPGRADING
writing output... [ 20%] admin_client
writing output... [ 26%] batch
writing output... [ 33%] changelog
writing output... [ 40%] client
writing output... [ 46%] collection
writing output... [ 53%] document
writing output... [ 60%] field_path
writing output... [ 66%] index
writing output... [ 73%] multiprocessing
writing output... [ 80%] query
writing output... [ 86%] transaction
writing output... [ 93%] transforms
writing output... [100%] types
generating indices... genindex py-modindex done
highlighting module code... [ 3%] google.cloud.firestore_admin_v1.services.firestore_admin.client
highlighting module code... [ 7%] google.cloud.firestore_v1.async_batch
highlighting module code... [ 11%] google.cloud.firestore_v1.async_client
highlighting module code... [ 15%] google.cloud.firestore_v1.async_collection
highlighting module code... [ 19%] google.cloud.firestore_v1.async_document
highlighting module code... [ 23%] google.cloud.firestore_v1.async_query
highlighting module code... [ 26%] google.cloud.firestore_v1.async_transaction
highlighting module code... [ 30%] google.cloud.firestore_v1.base_batch
highlighting module code... [ 34%] google.cloud.firestore_v1.base_client
highlighting module code... [ 38%] google.cloud.firestore_v1.base_collection
highlighting module code... [ 42%] google.cloud.firestore_v1.base_document
highlighting module code... [ 46%] google.cloud.firestore_v1.base_query
highlighting module code... [ 50%] google.cloud.firestore_v1.base_transaction
highlighting module code... [ 53%] google.cloud.firestore_v1.batch
highlighting module code... [ 57%] google.cloud.firestore_v1.client
highlighting module code... [ 61%] google.cloud.firestore_v1.collection
highlighting module code... [ 65%] google.cloud.firestore_v1.document
highlighting module code... [ 69%] google.cloud.firestore_v1.field_path
highlighting module code... [ 73%] google.cloud.firestore_v1.query
highlighting module code... [ 76%] google.cloud.firestore_v1.transaction
highlighting module code... [ 80%] google.cloud.firestore_v1.transforms
highlighting module code... [ 84%] google.cloud.firestore_v1.types.common
highlighting module code... [ 88%] google.cloud.firestore_v1.types.document
highlighting module code... [ 92%] google.cloud.firestore_v1.types.firestore
highlighting module code... [ 96%] google.cloud.firestore_v1.types.query
highlighting module code... [100%] google.cloud.firestore_v1.types.write
writing additional pages... search done
copying static files... done
copying extra files... done
dumping search index in English (code: en)... done
dumping object inventory... done
build succeeded.
The HTML pages are in docs/_build/html.
nox > Session docs was successful.
real 0m12.548s
user 0m12.024s
sys 0m0.354s
```
Given that the system tests take 3 - 4 minutes to run, ISTM it would be good to break them out into a separate Kokoro job, running in parallel with the other test.
This change will require updates to the google3 internal configuration for Kokoro, similar to those @tswast made to enable them for googleapis/python-bigtable#390. | 1.0 | Split out system tests into separate Kokoro job - Working to reduce CI latency.Here are timings on my local machine (note the pre-run with `--install-only` to avoid measuring virtualenv creation time):
```bash
$ for job in $(nox --list | grep "^\*" | cut -d " " -f 2); do
echo $job;
nox -e $job --install-only;
time nox -re $job;
done
lint
nox > Running session lint
nox > Creating virtual environment (virtualenv) using python3.8 in .nox/lint
nox > python -m pip install flake8 black==19.10b0
nox > Skipping black run, as --install-only is set.
nox > Skipping flake8 run, as --install-only is set.
nox > Session lint was successful.
nox > Running session lint
nox > Re-using existing virtual environment at .nox/lint.
nox > python -m pip install flake8 black==19.10b0
nox > black --check docs google tests noxfile.py setup.py
All done! ✨ 🍰 ✨
109 files would be left unchanged.
nox > flake8 google tests
nox > Session lint was successful.
real 0m3.902s
user 0m16.218s
sys 0m0.277s
blacken
nox > Running session blacken
nox > Creating virtual environment (virtualenv) using python3.8 in .nox/blacken
nox > python -m pip install black==19.10b0
nox > Skipping black run, as --install-only is set.
nox > Session blacken was successful.
nox > Running session blacken
nox > Re-using existing virtual environment at .nox/blacken.
nox > python -m pip install black==19.10b0
nox > black docs google tests noxfile.py setup.py
All done! ✨ 🍰 ✨
109 files left unchanged.
nox > Session blacken was successful.
real 0m1.007s
user 0m0.884s
sys 0m0.127s
lint_setup_py
nox > Running session lint_setup_py
nox > Creating virtual environment (virtualenv) using python3.8 in .nox/lint_setup_py
nox > python -m pip install docutils pygments
nox > Skipping python run, as --install-only is set.
nox > Session lint_setup_py was successful.
nox > Running session lint_setup_py
nox > Re-using existing virtual environment at .nox/lint_setup_py.
nox > python -m pip install docutils pygments
nox > python setup.py check --restructuredtext --strict
running check
nox > Session lint_setup_py was successful.
real 0m1.067s
user 0m0.946s
sys 0m0.123s
unit-3.6
nox > Running session unit-3.6
nox > Creating virtual environment (virtualenv) using python3.6 in .nox/unit-3-6
nox > python -m pip install asyncmock pytest-asyncio -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.6.txt
nox > python -m pip install mock pytest pytest-cov aiounittest -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.6.txt
nox > python -m pip install -e . -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.6.txt
nox > Skipping py.test run, as --install-only is set.
nox > Session unit-3.6 was successful.
nox > Running session unit-3.6
nox > Re-using existing virtual environment at .nox/unit-3-6.
nox > python -m pip install asyncmock pytest-asyncio -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.6.txt
nox > python -m pip install mock pytest pytest-cov aiounittest -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.6.txt
nox > python -m pip install -e . -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.6.txt
nox > py.test --quiet --junitxml=unit_3.6_sponge_log.xml --cov=google/cloud --cov=tests/unit --cov-append --cov-config=.coveragerc --cov-report= --cov-fail-under=0 tests/unit
........................................................................ [ 5%]
...............................................................s..s.ss.. [ 10%]
........................................................................ [ 15%]
........................................................................ [ 20%]
...................................................s..s.ss.............. [ 25%]
........................................................................ [ 30%]
........................................................................ [ 35%]
........................................................................ [ 40%]
........................................................................ [ 45%]
........................................................................ [ 50%]
........................................................................ [ 55%]
........................................................................ [ 60%]
........................................................................ [ 65%]
........................................................................ [ 70%]
............................................................ssssssssssss [ 75%]
ssssssssssssssssssssssssssssssss........................................ [ 80%]
........................................................................ [ 85%]
........................................................................ [ 90%]
........................................................................ [ 95%]
........................................................... [100%]
- generated xml file: /home/tseaver/projects/agendaless/Google/src/python-firestore/unit_3.6_sponge_log.xml -
1375 passed, 52 skipped in 14.10s
nox > Session unit-3.6 was successful.
real 0m18.388s
user 0m17.654s
sys 0m0.675s
unit-3.7
nox > Running session unit-3.7
nox > Creating virtual environment (virtualenv) using python3.7 in .nox/unit-3-7
nox > python -m pip install asyncmock pytest-asyncio -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.7.txt
nox > python -m pip install mock pytest pytest-cov aiounittest -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.7.txt
nox > python -m pip install -e . -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.7.txt
nox > Skipping py.test run, as --install-only is set.
nox > Session unit-3.7 was successful.
nox > Running session unit-3.7
nox > Re-using existing virtual environment at .nox/unit-3-7.
nox > python -m pip install asyncmock pytest-asyncio -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.7.txt
nox > python -m pip install mock pytest pytest-cov aiounittest -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.7.txt
nox > python -m pip install -e . -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.7.txt
nox > py.test --quiet --junitxml=unit_3.7_sponge_log.xml --cov=google/cloud --cov=tests/unit --cov-append --cov-config=.coveragerc --cov-report= --cov-fail-under=0 tests/unit
........................................................................ [ 5%]
................................................................s..s..ss [ 10%]
........................................................................ [ 15%]
........................................................................ [ 20%]
....................................................s..s..ss............ [ 25%]
........................................................................ [ 30%]
........................................................................ [ 35%]
........................................................................ [ 40%]
........................................................................ [ 45%]
........................................................................ [ 50%]
........................................................................ [ 55%]
........................................................................ [ 60%]
........................................................................ [ 65%]
........................................................................ [ 70%]
............................................................ssssssssssss [ 75%]
ssssssssssssssssssssssssssssssss........................................ [ 80%]
........................................................................ [ 85%]
........................................................................ [ 90%]
........................................................................ [ 95%]
........................................................... [100%]
- generated xml file: /home/tseaver/projects/agendaless/Google/src/python-firestore/unit_3.7_sponge_log.xml -
1375 passed, 52 skipped in 14.09s
nox > Session unit-3.7 was successful.
real 0m17.930s
user 0m17.185s
sys 0m0.732s
unit-3.8
nox > Running session unit-3.8
nox > Creating virtual environment (virtualenv) using python3.8 in .nox/unit-3-8
nox > python -m pip install asyncmock pytest-asyncio -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.8.txt
nox > python -m pip install mock pytest pytest-cov aiounittest -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.8.txt
nox > python -m pip install -e . -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.8.txt
nox > Skipping py.test run, as --install-only is set.
nox > Session unit-3.8 was successful.
nox > Running session unit-3.8
nox > Re-using existing virtual environment at .nox/unit-3-8.
nox > python -m pip install asyncmock pytest-asyncio -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.8.txt
nox > python -m pip install mock pytest pytest-cov aiounittest -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.8.txt
nox > python -m pip install -e . -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.8.txt
nox > py.test --quiet --junitxml=unit_3.8_sponge_log.xml --cov=google/cloud --cov=tests/unit --cov-append --cov-config=.coveragerc --cov-report= --cov-fail-under=0 tests/unit
........................................................................ [ 5%]
................................................................s..s..ss [ 10%]
........................................................................ [ 15%]
........................................................................ [ 20%]
....................................................s..s..ss............ [ 25%]
........................................................................ [ 30%]
........................................................................ [ 35%]
........................................................................ [ 40%]
........................................................................ [ 45%]
........................................................................ [ 50%]
........................................................................ [ 55%]
........................................................................ [ 60%]
........................................................................ [ 65%]
........................................................................ [ 70%]
............................................................ssssssssssss [ 75%]
ssssssssssssssssssssssssssssssss........................................ [ 80%]
........................................................................ [ 85%]
........................................................................ [ 90%]
........................................................................ [ 95%]
........................................................... [100%]
- generated xml file: /home/tseaver/projects/agendaless/Google/src/python-firestore/unit_3.8_sponge_log.xml -
1375 passed, 52 skipped in 13.40s
nox > Session unit-3.8 was successful.
real 0m17.162s
user 0m16.517s
sys 0m0.638s
unit-3.9
nox > Running session unit-3.9
nox > Creating virtual environment (virtualenv) using python3.9 in .nox/unit-3-9
nox > python -m pip install asyncmock pytest-asyncio -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.9.txt
nox > python -m pip install mock pytest pytest-cov aiounittest -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.9.txt
nox > python -m pip install -e . -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.9.txt
nox > Skipping py.test run, as --install-only is set.
nox > Session unit-3.9 was successful.
nox > Running session unit-3.9
nox > Re-using existing virtual environment at .nox/unit-3-9.
nox > python -m pip install asyncmock pytest-asyncio -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.9.txt
nox > python -m pip install mock pytest pytest-cov aiounittest -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.9.txt
nox > python -m pip install -e . -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.9.txt
nox > py.test --quiet --junitxml=unit_3.9_sponge_log.xml --cov=google/cloud --cov=tests/unit --cov-append --cov-config=.coveragerc --cov-report= --cov-fail-under=0 tests/unit
........................................................................ [ 5%]
................................................................s..s..ss [ 10%]
........................................................................ [ 15%]
........................................................................ [ 20%]
....................................................s..s..ss............ [ 25%]
........................................................................ [ 30%]
........................................................................ [ 35%]
........................................................................ [ 40%]
........................................................................ [ 45%]
........................................................................ [ 50%]
........................................................................ [ 55%]
........................................................................ [ 60%]
........................................................................ [ 65%]
........................................................................ [ 70%]
............................................................ssssssssssss [ 75%]
ssssssssssssssssssssssssssssssss........................................ [ 80%]
........................................................................ [ 85%]
........................................................................ [ 90%]
........................................................................ [ 95%]
........................................................... [100%]
- generated xml file: /home/tseaver/projects/agendaless/Google/src/python-firestore/unit_3.9_sponge_log.xml -
1375 passed, 52 skipped in 15.70s
nox > Session unit-3.9 was successful.
real 0m19.250s
user 0m18.510s
sys 0m0.715s
system-3.7
nox > Running session system-3.7
nox > Creating virtual environment (virtualenv) using python3.7 in .nox/system-3-7
nox > python -m pip install --pre grpcio
nox > python -m pip install mock pytest google-cloud-testutils pytest-asyncio -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.7.txt
nox > python -m pip install -e . -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.7.txt
nox > Skipping py.test run, as --install-only is set.
nox > Session system-3.7 was successful.
nox > Running session system-3.7
nox > Re-using existing virtual environment at .nox/system-3-7.
nox > python -m pip install --pre grpcio
nox > python -m pip install mock pytest google-cloud-testutils pytest-asyncio -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.7.txt
nox > python -m pip install -e . -c /home/tseaver/projects/agendaless/Google/src/python-firestore/testing/constraints-3.7.txt
nox > py.test --verbose --junitxml=system_3.7_sponge_log.xml tests/system
============================= test session starts ==============================
platform linux -- Python 3.7.6, pytest-6.2.4, py-1.10.0, pluggy-0.13.1 -- /home/tseaver/projects/agendaless/Google/src/python-firestore/.nox/system-3-7/bin/python
cachedir: .pytest_cache
rootdir: /home/tseaver/projects/agendaless/Google/src/python-firestore
plugins: asyncio-0.15.1
collected 77 items
tests/system/test_system.py::test_collections PASSED [ 1%]
tests/system/test_system.py::test_collections_w_import PASSED [ 2%]
tests/system/test_system.py::test_create_document PASSED [ 3%]
tests/system/test_system.py::test_create_document_w_subcollection PASSED [ 5%]
tests/system/test_system.py::test_cannot_use_foreign_key PASSED [ 6%]
tests/system/test_system.py::test_no_document PASSED [ 7%]
tests/system/test_system.py::test_document_set PASSED [ 9%]
tests/system/test_system.py::test_document_integer_field PASSED [ 10%]
tests/system/test_system.py::test_document_set_merge PASSED [ 11%]
tests/system/test_system.py::test_document_set_w_int_field PASSED [ 12%]
tests/system/test_system.py::test_document_update_w_int_field PASSED [ 14%]
tests/system/test_system.py::test_update_document PASSED [ 15%]
tests/system/test_system.py::test_document_get PASSED [ 16%]
tests/system/test_system.py::test_document_delete PASSED [ 18%]
tests/system/test_system.py::test_collection_add PASSED [ 19%]
tests/system/test_system.py::test_query_stream_w_simple_field_eq_op PASSED [ 20%]
tests/system/test_system.py::test_query_stream_w_simple_field_array_contains_op PASSED [ 22%]
tests/system/test_system.py::test_query_stream_w_simple_field_in_op PASSED [ 23%]
tests/system/test_system.py::test_query_stream_w_not_eq_op PASSED [ 24%]
tests/system/test_system.py::test_query_stream_w_simple_not_in_op PASSED [ 25%]
tests/system/test_system.py::test_query_stream_w_simple_field_array_contains_any_op PASSED [ 27%]
tests/system/test_system.py::test_query_stream_w_order_by PASSED [ 28%]
tests/system/test_system.py::test_query_stream_w_field_path PASSED [ 29%]
tests/system/test_system.py::test_query_stream_w_start_end_cursor PASSED [ 31%]
tests/system/test_system.py::test_query_stream_wo_results PASSED [ 32%]
tests/system/test_system.py::test_query_stream_w_projection PASSED [ 33%]
tests/system/test_system.py::test_query_stream_w_multiple_filters PASSED [ 35%]
tests/system/test_system.py::test_query_stream_w_offset PASSED [ 36%]
tests/system/test_system.py::test_query_with_order_dot_key PASSED [ 37%]
tests/system/test_system.py::test_query_unary PASSED [ 38%]
tests/system/test_system.py::test_collection_group_queries PASSED [ 40%]
tests/system/test_system.py::test_collection_group_queries_startat_endat PASSED [ 41%]
tests/system/test_system.py::test_collection_group_queries_filters PASSED [ 42%]
tests/system/test_system.py::test_partition_query_no_partitions PASSED [ 44%]
tests/system/test_system.py::test_partition_query PASSED [ 45%]
tests/system/test_system.py::test_get_all PASSED [ 46%]
tests/system/test_system.py::test_batch PASSED [ 48%]
tests/system/test_system.py::test_watch_document PASSED [ 49%]
tests/system/test_system.py::test_watch_collection PASSED [ 50%]
tests/system/test_system.py::test_watch_query PASSED [ 51%]
tests/system/test_system.py::test_array_union PASSED [ 53%]
tests/system/test_system.py::test_watch_query_order PASSED [ 54%]
tests/system/test_system_async.py::test_collections PASSED [ 55%]
tests/system/test_system_async.py::test_collections_w_import PASSED [ 57%]
tests/system/test_system_async.py::test_create_document PASSED [ 58%]
tests/system/test_system_async.py::test_create_document_w_subcollection PASSED [ 59%]
tests/system/test_system_async.py::test_cannot_use_foreign_key PASSED [ 61%]
tests/system/test_system_async.py::test_no_document PASSED [ 62%]
tests/system/test_system_async.py::test_document_set PASSED [ 63%]
tests/system/test_system_async.py::test_document_integer_field PASSED [ 64%]
tests/system/test_system_async.py::test_document_set_merge PASSED [ 66%]
tests/system/test_system_async.py::test_document_set_w_int_field PASSED [ 67%]
tests/system/test_system_async.py::test_document_update_w_int_field PASSED [ 68%]
tests/system/test_system_async.py::test_update_document PASSED [ 70%]
tests/system/test_system_async.py::test_document_get PASSED [ 71%]
tests/system/test_system_async.py::test_document_delete PASSED [ 72%]
tests/system/test_system_async.py::test_collection_add PASSED [ 74%]
tests/system/test_system_async.py::test_query_stream_w_simple_field_eq_op PASSED [ 75%]
tests/system/test_system_async.py::test_query_stream_w_simple_field_array_contains_op PASSED [ 76%]
tests/system/test_system_async.py::test_query_stream_w_simple_field_in_op PASSED [ 77%]
tests/system/test_system_async.py::test_query_stream_w_simple_field_array_contains_any_op PASSED [ 79%]
tests/system/test_system_async.py::test_query_stream_w_order_by PASSED [ 80%]
tests/system/test_system_async.py::test_query_stream_w_field_path PASSED [ 81%]
tests/system/test_system_async.py::test_query_stream_w_start_end_cursor PASSED [ 83%]
tests/system/test_system_async.py::test_query_stream_wo_results PASSED [ 84%]
tests/system/test_system_async.py::test_query_stream_w_projection PASSED [ 85%]
tests/system/test_system_async.py::test_query_stream_w_multiple_filters PASSED [ 87%]
tests/system/test_system_async.py::test_query_stream_w_offset PASSED [ 88%]
tests/system/test_system_async.py::test_query_with_order_dot_key PASSED [ 89%]
tests/system/test_system_async.py::test_query_unary PASSED [ 90%]
tests/system/test_system_async.py::test_collection_group_queries PASSED [ 92%]
tests/system/test_system_async.py::test_collection_group_queries_startat_endat PASSED [ 93%]
tests/system/test_system_async.py::test_collection_group_queries_filters PASSED [ 94%]
tests/system/test_system_async.py::test_partition_query_no_partitions PASSED [ 96%]
tests/system/test_system_async.py::test_partition_query PASSED [ 97%]
tests/system/test_system_async.py::test_get_all PASSED [ 98%]
tests/system/test_system_async.py::test_batch PASSED [100%]
=================== 77 passed in 211.00s (0:03:31) ===================
nox > Command py.test --verbose --junitxml=system_3.7_sponge_log.xml tests/system passed
nox > Session system-3.7 was successful.
real 3m34.561s
user 0m11.371s
sys 0m1.881s
cover
nox > Running session cover
nox > Creating virtual environment (virtualenv) using python3.8 in .nox/cover
nox > python -m pip install coverage pytest-cov
nox > Skipping coverage run, as --install-only is set.
nox > Skipping coverage run, as --install-only is set.
nox > Session cover was successful.
nox > Running session cover
nox > Re-using existing virtual environment at .nox/cover.
nox > python -m pip install coverage pytest-cov
nox > coverage report --show-missing --fail-under=100
Name Stmts Miss Branch BrPart Cover Missing
---------------------------------------------------------------------------------------------------------------------------------
google/cloud/firestore.py 35 0 0 0 100%
google/cloud/firestore_admin_v1/__init__.py 23 0 0 0 100%
google/cloud/firestore_admin_v1/services/__init__.py 0 0 0 0 100%
google/cloud/firestore_admin_v1/services/firestore_admin/__init__.py 3 0 0 0 100%
google/cloud/firestore_admin_v1/services/firestore_admin/async_client.py 168 0 38 0 100%
google/cloud/firestore_admin_v1/services/firestore_admin/client.py 282 0 90 0 100%
google/cloud/firestore_admin_v1/services/firestore_admin/pagers.py 82 0 20 0 100%
google/cloud/firestore_admin_v1/services/firestore_admin/transports/__init__.py 9 0 0 0 100%
google/cloud/firestore_admin_v1/services/firestore_admin/transports/base.py 72 0 12 0 100%
google/cloud/firestore_admin_v1/services/firestore_admin/transports/grpc.py 100 0 34 0 100%
google/cloud/firestore_admin_v1/services/firestore_admin/transports/grpc_asyncio.py 103 0 34 0 100%
google/cloud/firestore_admin_v1/types/__init__.py 6 0 0 0 100%
google/cloud/firestore_admin_v1/types/field.py 12 0 0 0 100%
google/cloud/firestore_admin_v1/types/firestore_admin.py 48 0 0 0 100%
google/cloud/firestore_admin_v1/types/index.py 28 0 0 0 100%
google/cloud/firestore_admin_v1/types/location.py 4 0 0 0 100%
google/cloud/firestore_admin_v1/types/operation.py 57 0 0 0 100%
google/cloud/firestore_bundle/__init__.py 7 0 0 0 100%
google/cloud/firestore_bundle/_helpers.py 4 0 0 0 100%
google/cloud/firestore_bundle/bundle.py 111 0 32 0 100%
google/cloud/firestore_bundle/services/__init__.py 0 0 0 0 100%
google/cloud/firestore_bundle/types/__init__.py 2 0 0 0 100%
google/cloud/firestore_bundle/types/bundle.py 33 0 0 0 100%
google/cloud/firestore_v1/__init__.py 37 0 0 0 100%
google/cloud/firestore_v1/_helpers.py 478 0 240 0 100%
google/cloud/firestore_v1/async_batch.py 19 0 2 0 100%
google/cloud/firestore_v1/async_client.py 41 0 4 0 100%
google/cloud/firestore_v1/async_collection.py 32 0 4 0 100%
google/cloud/firestore_v1/async_document.py 44 0 4 0 100%
google/cloud/firestore_v1/async_query.py 45 0 16 0 100%
google/cloud/firestore_v1/async_transaction.py 98 0 22 0 100%
google/cloud/firestore_v1/base_batch.py 32 0 4 0 100%
google/cloud/firestore_v1/base_client.py 151 0 42 0 100%
google/cloud/firestore_v1/base_collection.py 101 0 16 0 100%
google/cloud/firestore_v1/base_document.py 145 0 24 0 100%
google/cloud/firestore_v1/base_query.py 331 0 130 0 100%
google/cloud/firestore_v1/base_transaction.py 65 0 6 0 100%
google/cloud/firestore_v1/batch.py 19 0 2 0 100%
google/cloud/firestore_v1/client.py 42 0 4 0 100%
google/cloud/firestore_v1/collection.py 30 0 2 0 100%
google/cloud/firestore_v1/document.py 48 0 4 0 100%
google/cloud/firestore_v1/field_path.py 135 0 56 0 100%
google/cloud/firestore_v1/order.py 130 0 54 0 100%
google/cloud/firestore_v1/query.py 47 0 14 0 100%
google/cloud/firestore_v1/services/__init__.py 0 0 0 0 100%
google/cloud/firestore_v1/services/firestore/__init__.py 3 0 0 0 100%
google/cloud/firestore_v1/services/firestore/async_client.py 178 0 30 0 100%
google/cloud/firestore_v1/services/firestore/client.py 276 0 90 0 100%
google/cloud/firestore_v1/services/firestore/pagers.py 121 0 30 0 100%
google/cloud/firestore_v1/services/firestore/transports/__init__.py 9 0 0 0 100%
google/cloud/firestore_v1/services/firestore/transports/base.py 80 0 12 0 100%
google/cloud/firestore_v1/services/firestore/transports/grpc.py 122 0 44 0 100%
google/cloud/firestore_v1/services/firestore/transports/grpc_asyncio.py 125 0 44 0 100%
google/cloud/firestore_v1/transaction.py 97 0 22 0 100%
google/cloud/firestore_v1/transforms.py 39 0 10 0 100%
google/cloud/firestore_v1/types/__init__.py 6 0 0 0 100%
google/cloud/firestore_v1/types/common.py 16 0 0 0 100%
google/cloud/firestore_v1/types/document.py 27 0 0 0 100%
google/cloud/firestore_v1/types/firestore.py 157 0 0 0 100%
google/cloud/firestore_v1/types/query.py 66 0 0 0 100%
google/cloud/firestore_v1/types/write.py 45 0 0 0 100%
google/cloud/firestore_v1/watch.py 325 0 78 0 100%
tests/unit/__init__.py 0 0 0 0 100%
tests/unit/test_firestore_shim.py 10 0 2 0 100%
tests/unit/v1/__init__.py 0 0 0 0 100%
tests/unit/v1/_test_helpers.py 22 0 0 0 100%
tests/unit/v1/conformance_tests.py 106 0 0 0 100%
tests/unit/v1/test__helpers.py 1653 0 36 0 100%
tests/unit/v1/test_async_batch.py 98 0 0 0 100%
tests/unit/v1/test_async_client.py 267 0 18 0 100%
tests/unit/v1/test_async_collection.py 223 0 20 0 100%
tests/unit/v1/test_async_document.py 334 0 32 0 100%
tests/unit/v1/test_async_query.py 327 0 26 0 100%
tests/unit/v1/test_async_transaction.py 584 0 0 0 100%
tests/unit/v1/test_base_batch.py 98 0 0 0 100%
tests/unit/v1/test_base_client.py 238 0 0 0 100%
tests/unit/v1/test_base_collection.py 239 0 0 0 100%
tests/unit/v1/test_base_document.py 293 0 2 0 100%
tests/unit/v1/test_base_query.py 1006 0 20 0 100%
tests/unit/v1/test_base_transaction.py 75 0 0 0 100%
tests/unit/v1/test_batch.py 92 0 0 0 100%
tests/unit/v1/test_bundle.py 268 0 4 0 100%
tests/unit/v1/test_client.py 256 0 12 0 100%
tests/unit/v1/test_collection.py 197 0 10 0 100%
tests/unit/v1/test_cross_language.py 207 0 82 0 100%
tests/unit/v1/test_document.py 307 0 26 0 100%
tests/unit/v1/test_field_path.py 355 0 8 0 100%
tests/unit/v1/test_order.py 138 0 8 0 100%
tests/unit/v1/test_query.py 318 0 0 0 100%
tests/unit/v1/test_transaction.py 560 0 0 0 100%
tests/unit/v1/test_transforms.py 78 0 8 0 100%
tests/unit/v1/test_watch.py 667 0 4 0 100%
---------------------------------------------------------------------------------------------------------------------------------
TOTAL 13967 0 1588 0 100%
nox > coverage erase
nox > Session cover was successful.
real 0m3.581s
user 0m3.419s
sys 0m0.163s
docs
nox > Running session docs
nox > Creating virtual environment (virtualenv) using python3.8 in .nox/docs
nox > python -m pip install -e .
nox > python -m pip install sphinx==4.0.1 alabaster recommonmark
nox > Skipping sphinx-build run, as --install-only is set.
nox > Session docs was successful.
nox > Running session docs
nox > Re-using existing virtual environment at .nox/docs.
nox > python -m pip install -e .
nox > python -m pip install sphinx==4.0.1 alabaster recommonmark
nox > sphinx-build -W -T -N -b html -d docs/_build/doctrees/ docs/ docs/_build/html/
Running Sphinx v4.0.1
making output directory... done
[autosummary] generating autosummary for: README.rst, UPGRADING.md, admin_client.rst, batch.rst, changelog.md, client.rst, collection.rst, document.rst, field_path.rst, index.rst, multiprocessing.rst, query.rst, transaction.rst, transforms.rst, types.rst
loading intersphinx inventory from https://python.readthedocs.org/en/latest/objects.inv...
loading intersphinx inventory from https://googleapis.dev/python/google-auth/latest/objects.inv...
loading intersphinx inventory from https://googleapis.dev/python/google-api-core/latest/objects.inv...
loading intersphinx inventory from https://grpc.github.io/grpc/python/objects.inv...
loading intersphinx inventory from https://proto-plus-python.readthedocs.io/en/latest/objects.inv...
loading intersphinx inventory from https://googleapis.dev/python/protobuf/latest/objects.inv...
intersphinx inventory has moved: https://python.readthedocs.org/en/latest/objects.inv -> https://python.readthedocs.io/en/latest/objects.inv
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 15 source files that are out of date
updating environment: [new config] 15 added, 0 changed, 0 removed
reading sources... [ 6%] README
reading sources... [ 13%] UPGRADING
/home/tseaver/projects/agendaless/Google/src/python-firestore/.nox/docs/lib/python3.8/site-packages/recommonmark/parser.py:75: UserWarning: Container node skipped: type=document
warn("Container node skipped: type={0}".format(mdnode.t))
reading sources... [ 20%] admin_client
reading sources... [ 26%] batch
reading sources... [ 33%] changelog
/home/tseaver/projects/agendaless/Google/src/python-firestore/.nox/docs/lib/python3.8/site-packages/recommonmark/parser.py:75: UserWarning: Container node skipped: type=document
warn("Container node skipped: type={0}".format(mdnode.t))
reading sources... [ 40%] client
reading sources... [ 46%] collection
reading sources... [ 53%] document
reading sources... [ 60%] field_path
reading sources... [ 66%] index
reading sources... [ 73%] multiprocessing
reading sources... [ 80%] query
reading sources... [ 86%] transaction
reading sources... [ 93%] transforms
reading sources... [100%] types
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
writing output... [ 6%] README
writing output... [ 13%] UPGRADING
writing output... [ 20%] admin_client
writing output... [ 26%] batch
writing output... [ 33%] changelog
writing output... [ 40%] client
writing output... [ 46%] collection
writing output... [ 53%] document
writing output... [ 60%] field_path
writing output... [ 66%] index
writing output... [ 73%] multiprocessing
writing output... [ 80%] query
writing output... [ 86%] transaction
writing output... [ 93%] transforms
writing output... [100%] types
generating indices... genindex py-modindex done
highlighting module code... [ 3%] google.cloud.firestore_admin_v1.services.firestore_admin.client
highlighting module code... [ 7%] google.cloud.firestore_v1.async_batch
highlighting module code... [ 11%] google.cloud.firestore_v1.async_client
highlighting module code... [ 15%] google.cloud.firestore_v1.async_collection
highlighting module code... [ 19%] google.cloud.firestore_v1.async_document
highlighting module code... [ 23%] google.cloud.firestore_v1.async_query
highlighting module code... [ 26%] google.cloud.firestore_v1.async_transaction
highlighting module code... [ 30%] google.cloud.firestore_v1.base_batch
highlighting module code... [ 34%] google.cloud.firestore_v1.base_client
highlighting module code... [ 38%] google.cloud.firestore_v1.base_collection
highlighting module code... [ 42%] google.cloud.firestore_v1.base_document
highlighting module code... [ 46%] google.cloud.firestore_v1.base_query
highlighting module code... [ 50%] google.cloud.firestore_v1.base_transaction
highlighting module code... [ 53%] google.cloud.firestore_v1.batch
highlighting module code... [ 57%] google.cloud.firestore_v1.client
highlighting module code... [ 61%] google.cloud.firestore_v1.collection
highlighting module code... [ 65%] google.cloud.firestore_v1.document
highlighting module code... [ 69%] google.cloud.firestore_v1.field_path
highlighting module code... [ 73%] google.cloud.firestore_v1.query
highlighting module code... [ 76%] google.cloud.firestore_v1.transaction
highlighting module code... [ 80%] google.cloud.firestore_v1.transforms
highlighting module code... [ 84%] google.cloud.firestore_v1.types.common
highlighting module code... [ 88%] google.cloud.firestore_v1.types.document
highlighting module code... [ 92%] google.cloud.firestore_v1.types.firestore
highlighting module code... [ 96%] google.cloud.firestore_v1.types.query
highlighting module code... [100%] google.cloud.firestore_v1.types.write
writing additional pages... search done
copying static files... done
copying extra files... done
dumping search index in English (code: en)... done
dumping object inventory... done
build succeeded.
The HTML pages are in docs/_build/html.
nox > Session docs was successful.
real 0m12.548s
user 0m12.024s
sys 0m0.354s
```
Given that the system tests take 3 - 4 minutes to run, ISTM it would be good to break them out into a separate Kokoro job, running in parallel with the other test.
This change will require updates to the google3 internal configuration for Kokoro, similar to those @tswast made to enable them for googleapis/python-bigtable#390. | process | split out system tests into separate kokoro job working to reduce ci latency here are timings on my local machine note the pre run with install only to avoid measuring virtualenv creation time bash for job in nox list grep cut d f do echo job nox e job install only time nox re job done lint nox running session lint nox creating virtual environment virtualenv using in nox lint nox python m pip install black nox skipping black run as install only is set nox skipping run as install only is set nox session lint was successful nox running session lint nox re using existing virtual environment at nox lint nox python m pip install black nox black check docs google tests noxfile py setup py all done ✨ 🍰 ✨ files would be left unchanged nox google tests nox session lint was successful real user sys blacken nox running session blacken nox creating virtual environment virtualenv using in nox blacken nox python m pip install black nox skipping black run as install only is set nox session blacken was successful nox running session blacken nox re using existing virtual environment at nox blacken nox python m pip install black nox black docs google tests noxfile py setup py all done ✨ 🍰 ✨ files left unchanged nox session blacken was successful real user sys lint setup py nox running session lint setup py nox creating virtual environment virtualenv using in nox lint setup py nox python m pip install docutils pygments nox skipping python run as install only is set nox session lint setup py was successful nox running session lint setup py nox re using existing virtual environment at nox lint setup py nox python m pip install docutils pygments nox python setup py check restructuredtext strict running check nox session lint setup py was successful real user sys unit nox running session unit nox creating virtual environment virtualenv using in nox unit nox python m pip install asyncmock pytest asyncio c home tseaver projects agendaless google src python firestore testing constraints txt nox python m pip install mock pytest pytest cov aiounittest c home tseaver projects agendaless google src python firestore testing constraints txt nox python m pip install e c home tseaver projects agendaless google src python firestore testing constraints txt nox skipping py test run as install only is set nox session unit was successful nox running session unit nox re using existing virtual environment at nox unit nox python m pip install asyncmock pytest asyncio c home tseaver projects agendaless google src python firestore testing constraints txt nox python m pip install mock pytest pytest cov aiounittest c home tseaver projects agendaless google src python firestore testing constraints txt nox python m pip install e c home tseaver projects agendaless google src python firestore testing constraints txt nox py test quiet junitxml unit sponge log xml cov google cloud cov tests unit cov append cov config coveragerc cov report cov fail under tests unit s s ss s s ss ssssssssssss ssssssssssssssssssssssssssssssss generated xml file home tseaver projects agendaless google src python firestore unit sponge log xml passed skipped in nox session unit was successful real user sys unit nox running session unit nox creating virtual environment virtualenv using in nox unit nox python m pip install asyncmock pytest asyncio c home tseaver projects agendaless google src python firestore testing constraints txt nox python m pip install mock pytest pytest cov aiounittest c home tseaver projects agendaless google src python firestore testing constraints txt nox python m pip install e c home tseaver projects agendaless google src python firestore testing constraints txt nox skipping py test run as install only is set nox session unit was successful nox running session unit nox re using existing virtual environment at nox unit nox python m pip install asyncmock pytest asyncio c home tseaver projects agendaless google src python firestore testing constraints txt nox python m pip install mock pytest pytest cov aiounittest c home tseaver projects agendaless google src python firestore testing constraints txt nox python m pip install e c home tseaver projects agendaless google src python firestore testing constraints txt nox py test quiet junitxml unit sponge log xml cov google cloud cov tests unit cov append cov config coveragerc cov report cov fail under tests unit s s ss s s ss ssssssssssss ssssssssssssssssssssssssssssssss generated xml file home tseaver projects agendaless google src python firestore unit sponge log xml passed skipped in nox session unit was successful real user sys unit nox running session unit nox creating virtual environment virtualenv using in nox unit nox python m pip install asyncmock pytest asyncio c home tseaver projects agendaless google src python firestore testing constraints txt nox python m pip install mock pytest pytest cov aiounittest c home tseaver projects agendaless google src python firestore testing constraints txt nox python m pip install e c home tseaver projects agendaless google src python firestore testing constraints txt nox skipping py test run as install only is set nox session unit was successful nox running session unit nox re using existing virtual environment at nox unit nox python m pip install asyncmock pytest asyncio c home tseaver projects agendaless google src python firestore testing constraints txt nox python m pip install mock pytest pytest cov aiounittest c home tseaver projects agendaless google src python firestore testing constraints txt nox python m pip install e c home tseaver projects agendaless google src python firestore testing constraints txt nox py test quiet junitxml unit sponge log xml cov google cloud cov tests unit cov append cov config coveragerc cov report cov fail under tests unit s s ss s s ss ssssssssssss ssssssssssssssssssssssssssssssss generated xml file home tseaver projects agendaless google src python firestore unit sponge log xml passed skipped in nox session unit was successful real user sys unit nox running session unit nox creating virtual environment virtualenv using in nox unit nox python m pip install asyncmock pytest asyncio c home tseaver projects agendaless google src python firestore testing constraints txt nox python m pip install mock pytest pytest cov aiounittest c home tseaver projects agendaless google src python firestore testing constraints txt nox python m pip install e c home tseaver projects agendaless google src python firestore testing constraints txt nox skipping py test run as install only is set nox session unit was successful nox running session unit nox re using existing virtual environment at nox unit nox python m pip install asyncmock pytest asyncio c home tseaver projects agendaless google src python firestore testing constraints txt nox python m pip install mock pytest pytest cov aiounittest c home tseaver projects agendaless google src python firestore testing constraints txt nox python m pip install e c home tseaver projects agendaless google src python firestore testing constraints txt nox py test quiet junitxml unit sponge log xml cov google cloud cov tests unit cov append cov config coveragerc cov report cov fail under tests unit s s ss s s ss ssssssssssss ssssssssssssssssssssssssssssssss generated xml file home tseaver projects agendaless google src python firestore unit sponge log xml passed skipped in nox session unit was successful real user sys system nox running session system nox creating virtual environment virtualenv using in nox system nox python m pip install pre grpcio nox python m pip install mock pytest google cloud testutils pytest asyncio c home tseaver projects agendaless google src python firestore testing constraints txt nox python m pip install e c home tseaver projects agendaless google src python firestore testing constraints txt nox skipping py test run as install only is set nox session system was successful nox running session system nox re using existing virtual environment at nox system nox python m pip install pre grpcio nox python m pip install mock pytest google cloud testutils pytest asyncio c home tseaver projects agendaless google src python firestore testing constraints txt nox python m pip install e c home tseaver projects agendaless google src python firestore testing constraints txt nox py test verbose junitxml system sponge log xml tests system test session starts platform linux python pytest py pluggy home tseaver projects agendaless google src python firestore nox system bin python cachedir pytest cache rootdir home tseaver projects agendaless google src python firestore plugins asyncio collected items tests system test system py test collections passed tests system test system py test collections w import passed tests system test system py test create document passed tests system test system py test create document w subcollection passed tests system test system py test cannot use foreign key passed tests system test system py test no document passed tests system test system py test document set passed tests system test system py test document integer field passed tests system test system py test document set merge passed tests system test system py test document set w int field passed tests system test system py test document update w int field passed tests system test system py test update document passed tests system test system py test document get passed tests system test system py test document delete passed tests system test system py test collection add passed tests system test system py test query stream w simple field eq op passed tests system test system py test query stream w simple field array contains op passed tests system test system py test query stream w simple field in op passed tests system test system py test query stream w not eq op passed tests system test system py test query stream w simple not in op passed tests system test system py test query stream w simple field array contains any op passed tests system test system py test query stream w order by passed tests system test system py test query stream w field path passed tests system test system py test query stream w start end cursor passed tests system test system py test query stream wo results passed tests system test system py test query stream w projection passed tests system test system py test query stream w multiple filters passed tests system test system py test query stream w offset passed tests system test system py test query with order dot key passed tests system test system py test query unary passed tests system test system py test collection group queries passed tests system test system py test collection group queries startat endat passed tests system test system py test collection group queries filters passed tests system test system py test partition query no partitions passed tests system test system py test partition query passed tests system test system py test get all passed tests system test system py test batch passed tests system test system py test watch document passed tests system test system py test watch collection passed tests system test system py test watch query passed tests system test system py test array union passed tests system test system py test watch query order passed tests system test system async py test collections passed tests system test system async py test collections w import passed tests system test system async py test create document passed tests system test system async py test create document w subcollection passed tests system test system async py test cannot use foreign key passed tests system test system async py test no document passed tests system test system async py test document set passed tests system test system async py test document integer field passed tests system test system async py test document set merge passed tests system test system async py test document set w int field passed tests system test system async py test document update w int field passed tests system test system async py test update document passed tests system test system async py test document get passed tests system test system async py test document delete passed tests system test system async py test collection add passed tests system test system async py test query stream w simple field eq op passed tests system test system async py test query stream w simple field array contains op passed tests system test system async py test query stream w simple field in op passed tests system test system async py test query stream w simple field array contains any op passed tests system test system async py test query stream w order by passed tests system test system async py test query stream w field path passed tests system test system async py test query stream w start end cursor passed tests system test system async py test query stream wo results passed tests system test system async py test query stream w projection passed tests system test system async py test query stream w multiple filters passed tests system test system async py test query stream w offset passed tests system test system async py test query with order dot key passed tests system test system async py test query unary passed tests system test system async py test collection group queries passed tests system test system async py test collection group queries startat endat passed tests system test system async py test collection group queries filters passed tests system test system async py test partition query no partitions passed tests system test system async py test partition query passed tests system test system async py test get all passed tests system test system async py test batch passed passed in nox command py test verbose junitxml system sponge log xml tests system passed nox session system was successful real user sys cover nox running session cover nox creating virtual environment virtualenv using in nox cover nox python m pip install coverage pytest cov nox skipping coverage run as install only is set nox skipping coverage run as install only is set nox session cover was successful nox running session cover nox re using existing virtual environment at nox cover nox python m pip install coverage pytest cov nox coverage report show missing fail under name stmts miss branch brpart cover missing google cloud firestore py google cloud firestore admin init py google cloud firestore admin services init py google cloud firestore admin services firestore admin init py google cloud firestore admin services firestore admin async client py google cloud firestore admin services firestore admin client py google cloud firestore admin services firestore admin pagers py google cloud firestore admin services firestore admin transports init py google cloud firestore admin services firestore admin transports base py google cloud firestore admin services firestore admin transports grpc py google cloud firestore admin services firestore admin transports grpc asyncio py google cloud firestore admin types init py google cloud firestore admin types field py google cloud firestore admin types firestore admin py google cloud firestore admin types index py google cloud firestore admin types location py google cloud firestore admin types operation py google cloud firestore bundle init py google cloud firestore bundle helpers py google cloud firestore bundle bundle py google cloud firestore bundle services init py google cloud firestore bundle types init py google cloud firestore bundle types bundle py google cloud firestore init py google cloud firestore helpers py google cloud firestore async batch py google cloud firestore async client py google cloud firestore async collection py google cloud firestore async document py google cloud firestore async query py google cloud firestore async transaction py google cloud firestore base batch py google cloud firestore base client py google cloud firestore base collection py google cloud firestore base document py google cloud firestore base query py google cloud firestore base transaction py google cloud firestore batch py google cloud firestore client py google cloud firestore collection py google cloud firestore document py google cloud firestore field path py google cloud firestore order py google cloud firestore query py google cloud firestore services init py google cloud firestore services firestore init py google cloud firestore services firestore async client py google cloud firestore services firestore client py google cloud firestore services firestore pagers py google cloud firestore services firestore transports init py google cloud firestore services firestore transports base py google cloud firestore services firestore transports grpc py google cloud firestore services firestore transports grpc asyncio py google cloud firestore transaction py google cloud firestore transforms py google cloud firestore types init py google cloud firestore types common py google cloud firestore types document py google cloud firestore types firestore py google cloud firestore types query py google cloud firestore types write py google cloud firestore watch py tests unit init py tests unit test firestore shim py tests unit init py tests unit test helpers py tests unit conformance tests py tests unit test helpers py tests unit test async batch py tests unit test async client py tests unit test async collection py tests unit test async document py tests unit test async query py tests unit test async transaction py tests unit test base batch py tests unit test base client py tests unit test base collection py tests unit test base document py tests unit test base query py tests unit test base transaction py tests unit test batch py tests unit test bundle py tests unit test client py tests unit test collection py tests unit test cross language py tests unit test document py tests unit test field path py tests unit test order py tests unit test query py tests unit test transaction py tests unit test transforms py tests unit test watch py total nox coverage erase nox session cover was successful real user sys docs nox running session docs nox creating virtual environment virtualenv using in nox docs nox python m pip install e nox python m pip install sphinx alabaster recommonmark nox skipping sphinx build run as install only is set nox session docs was successful nox running session docs nox re using existing virtual environment at nox docs nox python m pip install e nox python m pip install sphinx alabaster recommonmark nox sphinx build w t n b html d docs build doctrees docs docs build html running sphinx making output directory done generating autosummary for readme rst upgrading md admin client rst batch rst changelog md client rst collection rst document rst field path rst index rst multiprocessing rst query rst transaction rst transforms rst types rst loading intersphinx inventory from loading intersphinx inventory from loading intersphinx inventory from loading intersphinx inventory from loading intersphinx inventory from loading intersphinx inventory from intersphinx inventory has moved building targets for po files that are out of date building targets for source files that are out of date updating environment added changed removed reading sources readme reading sources upgrading home tseaver projects agendaless google src python firestore nox docs lib site packages recommonmark parser py userwarning container node skipped type document warn container node skipped type format mdnode t reading sources admin client reading sources batch reading sources changelog home tseaver projects agendaless google src python firestore nox docs lib site packages recommonmark parser py userwarning container node skipped type document warn container node skipped type format mdnode t reading sources client reading sources collection reading sources document reading sources field path reading sources index reading sources multiprocessing reading sources query reading sources transaction reading sources transforms reading sources types looking for now outdated files none found pickling environment done checking consistency done preparing documents done writing output readme writing output upgrading writing output admin client writing output batch writing output changelog writing output client writing output collection writing output document writing output field path writing output index writing output multiprocessing writing output query writing output transaction writing output transforms writing output types generating indices genindex py modindex done highlighting module code google cloud firestore admin services firestore admin client highlighting module code google cloud firestore async batch highlighting module code google cloud firestore async client highlighting module code google cloud firestore async collection highlighting module code google cloud firestore async document highlighting module code google cloud firestore async query highlighting module code google cloud firestore async transaction highlighting module code google cloud firestore base batch highlighting module code google cloud firestore base client highlighting module code google cloud firestore base collection highlighting module code google cloud firestore base document highlighting module code google cloud firestore base query highlighting module code google cloud firestore base transaction highlighting module code google cloud firestore batch highlighting module code google cloud firestore client highlighting module code google cloud firestore collection highlighting module code google cloud firestore document highlighting module code google cloud firestore field path highlighting module code google cloud firestore query highlighting module code google cloud firestore transaction highlighting module code google cloud firestore transforms highlighting module code google cloud firestore types common highlighting module code google cloud firestore types document highlighting module code google cloud firestore types firestore highlighting module code google cloud firestore types query highlighting module code google cloud firestore types write writing additional pages search done copying static files done copying extra files done dumping search index in english code en done dumping object inventory done build succeeded the html pages are in docs build html nox session docs was successful real user sys given that the system tests take minutes to run istm it would be good to break them out into a separate kokoro job running in parallel with the other test this change will require updates to the internal configuration for kokoro similar to those tswast made to enable them for googleapis python bigtable | 1 |
38,951 | 8,559,455,272 | IssuesEvent | 2018-11-08 21:19:43 | inspec/inspec | https://api.github.com/repos/inspec/inspec | opened | True Source Code Parsing | CLI: check Component: Code Generation Type: Feature Request Type: RFC | ### 🎛 Description
🙋 feature request
When InSpec examines a profile, it evaluates the profile code directly. This makes some operations, such as code generation, `check`, and profile inheritance, difficult and hard to debug.
An alternate approach might be to parse the source code of the profile, then manipulate the controls as desired, optionally executing.
This may very well be impossible; InSpec makes deep assumptions about how it exposes context to a running control, and many of those assumptions are based on RSpec's approach.
Alternatively, source parsing might be possible for other, non-exec use cases, such as profile generation and `check`.
It's not super likely this would ever be implemented; but I wanted to have an issue to tie together several other issues that might benefit from it.
### 🌍 InSpec and Platform Version
3.0.28
### 💁 Possible Solutions
Rubocop, among others, is able to examine source trees of arbitrary Ruby.
| 1.0 | True Source Code Parsing - ### 🎛 Description
🙋 feature request
When InSpec examines a profile, it evaluates the profile code directly. This makes some operations, such as code generation, `check`, and profile inheritance, difficult and hard to debug.
An alternate approach might be to parse the source code of the profile, then manipulate the controls as desired, optionally executing.
This may very well be impossible; InSpec makes deep assumptions about how it exposes context to a running control, and many of those assumptions are based on RSpec's approach.
Alternatively, source parsing might be possible for other, non-exec use cases, such as profile generation and `check`.
It's not super likely this would ever be implemented; but I wanted to have an issue to tie together several other issues that might benefit from it.
### 🌍 InSpec and Platform Version
3.0.28
### 💁 Possible Solutions
Rubocop, among others, is able to examine source trees of arbitrary Ruby.
| non_process | true source code parsing 🎛 description 🙋 feature request when inspec examines a profile it evaluates the profile code directly this makes some operations such as code generation check and profile inheritance difficult and hard to debug an alternate approach might be to parse the source code of the profile then manipulate the controls as desired optionally executing this may very well be impossible inspec makes deep assumptions about how it exposes context to a running control and many of those assumptions are based on rspec s approach alternatively source parsing might be possible for other non exec use cases such as profile generation and check it s not super likely this would ever be implemented but i wanted to have an issue to tie together several other issues that might benefit from it 🌍 inspec and platform version 💁 possible solutions rubocop among others is able to examine source trees of arbitrary ruby | 0 |
368,900 | 25,813,465,204 | IssuesEvent | 2022-12-12 01:50:36 | MAKAIABootcamp/demo-day-projects-ruta-mental | https://api.github.com/repos/MAKAIABootcamp/demo-day-projects-ruta-mental | closed | Creación Readme | documentation | Crear el readme del proyecto
- [x] Hacer descripción técnica de la app y algunos de sus funciones
- [x] Describir el uso de firebase
- [x] Describir los pre-requisitos
- [x] Instrucciones para correr el proyecto local | 1.0 | Creación Readme - Crear el readme del proyecto
- [x] Hacer descripción técnica de la app y algunos de sus funciones
- [x] Describir el uso de firebase
- [x] Describir los pre-requisitos
- [x] Instrucciones para correr el proyecto local | non_process | creación readme crear el readme del proyecto hacer descripción técnica de la app y algunos de sus funciones describir el uso de firebase describir los pre requisitos instrucciones para correr el proyecto local | 0 |
82,705 | 16,016,991,458 | IssuesEvent | 2021-04-20 17:15:17 | mozilla/fxa | https://api.github.com/repos/mozilla/fxa | closed | sasslint errors should cause Circle to fail | code_quality | Follow on from #1285 and #1328, @vladikoff noticed several sasslint errors. @mirefly fixed those in #1328. It brings up, sasslint errors should cause Circle to fail like any other lint error.
┆Issue is synchronized with this [Jira Task](https://jira.mozilla.com/browse/FXA-112)
┆Issue Number: FXA-112
| 1.0 | sasslint errors should cause Circle to fail - Follow on from #1285 and #1328, @vladikoff noticed several sasslint errors. @mirefly fixed those in #1328. It brings up, sasslint errors should cause Circle to fail like any other lint error.
┆Issue is synchronized with this [Jira Task](https://jira.mozilla.com/browse/FXA-112)
┆Issue Number: FXA-112
| non_process | sasslint errors should cause circle to fail follow on from and vladikoff noticed several sasslint errors mirefly fixed those in it brings up sasslint errors should cause circle to fail like any other lint error ┆issue is synchronized with this ┆issue number fxa | 0 |
20,530 | 6,896,572,172 | IssuesEvent | 2017-11-23 18:41:23 | eclipse/openj9 | https://api.github.com/repos/eclipse/openj9 | opened | Fold runtime/compiler/trj9 directory | comp:build comp:jit | Now that `tr.source` has been renamed to `compiler` as part of https://github.com/eclipse/openj9/pull/589 I wanted to start a discussion on possibly folding the `trj9` directory as well. To me it currently serves no purpose as it's parent `compiler` directory is completely empty.
@0xdaryl notes down some thoughts in https://github.com/eclipse/openj9/issues/550#issuecomment-344695397 which may possibly cause problems. I think the only way to find out would be to implement the change and see what fails.
Before we go down this road, do people even support this idea? Do we have internal or external dependencies on this? As I understand the compiler makefile currently resides in the `trj9` directory. Moving it one level up is sure to break _something_? What is this _something_? Any ideas, comments, or concerns are welcome. | 1.0 | Fold runtime/compiler/trj9 directory - Now that `tr.source` has been renamed to `compiler` as part of https://github.com/eclipse/openj9/pull/589 I wanted to start a discussion on possibly folding the `trj9` directory as well. To me it currently serves no purpose as it's parent `compiler` directory is completely empty.
@0xdaryl notes down some thoughts in https://github.com/eclipse/openj9/issues/550#issuecomment-344695397 which may possibly cause problems. I think the only way to find out would be to implement the change and see what fails.
Before we go down this road, do people even support this idea? Do we have internal or external dependencies on this? As I understand the compiler makefile currently resides in the `trj9` directory. Moving it one level up is sure to break _something_? What is this _something_? Any ideas, comments, or concerns are welcome. | non_process | fold runtime compiler directory now that tr source has been renamed to compiler as part of i wanted to start a discussion on possibly folding the directory as well to me it currently serves no purpose as it s parent compiler directory is completely empty notes down some thoughts in which may possibly cause problems i think the only way to find out would be to implement the change and see what fails before we go down this road do people even support this idea do we have internal or external dependencies on this as i understand the compiler makefile currently resides in the directory moving it one level up is sure to break something what is this something any ideas comments or concerns are welcome | 0 |
8,935 | 12,052,802,465 | IssuesEvent | 2020-04-15 08:17:56 | MHRA/products | https://api.github.com/repos/MHRA/products | opened | Job set to error status even though it was being retried | BUG :bug: EPIC - Auto Batch Process :oncoming_automobile: | **Describe the bug**
A delete job failed because it was unable to reach the search service, the job status was changed to `Error(: error sending request for url (https://mhraproductsnonprod.search.windows.net/indexes/products-index/docs?api-version=2019-05-06&highlight=content&queryType=full&%40count=true&%40top=10&%40skip=0&search=CON1563509585664&scoringProfile=preferKeywords): error trying to connect: unexpected EOF)`.
It was then retried and was successful.
The consumer (Sentinel batch process) stopped checking for updates after the first error status.
**To Reproduce**
Check logs with following query:
```let correlationId = "f9ec57a6-3d54-43d6-a1ee-924117f2b72b";
let timeframeFrom = totimespan(7d);
let timeframeTo = totimespan(5d);
let clusterId = '/subscriptions/bec11470-1346-4cdd-af2e-ce1f360671a1/resourceGroups/adazr-rg-1001/providers/Microsoft.ContainerService/managedClusters/non-prod';
let ContainerIdList = KubePodInventory
| where TimeGenerated > now() - timeframeFrom and TimeGenerated < now() - timeframeTo
| where ContainerName contains 'doc-index-updater'
| where ClusterId =~ clusterId
| distinct ContainerID;
ContainerLog
| where TimeGenerated > now() - timeframeFrom and TimeGenerated < now() - timeframeTo
| where ContainerID in (ContainerIdList)
| project LogEntrySource, LogEntry, TimeGenerated, Computer, Image, Name, ContainerID
| order by TimeGenerated desc
| render table
| extend message_ = tostring(parse_json(tostring(parse_json(LogEntry).fields)).message)
| where parse_json(tostring(parse_json(LogEntry).span)).correlation_id == correlationId```
**Expected behavior**
The job status should not be updated to `error` if the message is not removed from the queue.
**Screenshots**
N/A
**Additional context**
N/A
| 1.0 | Job set to error status even though it was being retried - **Describe the bug**
A delete job failed because it was unable to reach the search service, the job status was changed to `Error(: error sending request for url (https://mhraproductsnonprod.search.windows.net/indexes/products-index/docs?api-version=2019-05-06&highlight=content&queryType=full&%40count=true&%40top=10&%40skip=0&search=CON1563509585664&scoringProfile=preferKeywords): error trying to connect: unexpected EOF)`.
It was then retried and was successful.
The consumer (Sentinel batch process) stopped checking for updates after the first error status.
**To Reproduce**
Check logs with following query:
```let correlationId = "f9ec57a6-3d54-43d6-a1ee-924117f2b72b";
let timeframeFrom = totimespan(7d);
let timeframeTo = totimespan(5d);
let clusterId = '/subscriptions/bec11470-1346-4cdd-af2e-ce1f360671a1/resourceGroups/adazr-rg-1001/providers/Microsoft.ContainerService/managedClusters/non-prod';
let ContainerIdList = KubePodInventory
| where TimeGenerated > now() - timeframeFrom and TimeGenerated < now() - timeframeTo
| where ContainerName contains 'doc-index-updater'
| where ClusterId =~ clusterId
| distinct ContainerID;
ContainerLog
| where TimeGenerated > now() - timeframeFrom and TimeGenerated < now() - timeframeTo
| where ContainerID in (ContainerIdList)
| project LogEntrySource, LogEntry, TimeGenerated, Computer, Image, Name, ContainerID
| order by TimeGenerated desc
| render table
| extend message_ = tostring(parse_json(tostring(parse_json(LogEntry).fields)).message)
| where parse_json(tostring(parse_json(LogEntry).span)).correlation_id == correlationId```
**Expected behavior**
The job status should not be updated to `error` if the message is not removed from the queue.
**Screenshots**
N/A
**Additional context**
N/A
| process | job set to error status even though it was being retried describe the bug a delete job failed because it was unable to reach the search service the job status was changed to error error sending request for url error trying to connect unexpected eof it was then retried and was successful the consumer sentinel batch process stopped checking for updates after the first error status to reproduce check logs with following query let correlationid let timeframefrom totimespan let timeframeto totimespan let clusterid subscriptions resourcegroups adazr rg providers microsoft containerservice managedclusters non prod let containeridlist kubepodinventory where timegenerated now timeframefrom and timegenerated now timeframeto where containername contains doc index updater where clusterid clusterid distinct containerid containerlog where timegenerated now timeframefrom and timegenerated now timeframeto where containerid in containeridlist project logentrysource logentry timegenerated computer image name containerid order by timegenerated desc render table extend message tostring parse json tostring parse json logentry fields message where parse json tostring parse json logentry span correlation id correlationid expected behavior the job status should not be updated to error if the message is not removed from the queue screenshots n a additional context n a | 1 |
120,431 | 4,789,114,939 | IssuesEvent | 2016-10-30 22:14:52 | vidalborromeo/eecshelp-beta | https://api.github.com/repos/vidalborromeo/eecshelp-beta | opened | The "favicon.ico" File Is Not Loading | Bug Priority: Low | v2.0.60
Chrome/Firefox
Instead of the M logo, it just shows the default GWT logo. | 1.0 | The "favicon.ico" File Is Not Loading - v2.0.60
Chrome/Firefox
Instead of the M logo, it just shows the default GWT logo. | non_process | the favicon ico file is not loading chrome firefox instead of the m logo it just shows the default gwt logo | 0 |
19,417 | 25,565,288,566 | IssuesEvent | 2022-11-30 13:53:47 | open-telemetry/opentelemetry-collector-contrib | https://api.github.com/repos/open-telemetry/opentelemetry-collector-contrib | closed | The type of kafka_producer_connection_count keeps changing between counter and gauge | bug exporter/prometheus needs triage processor/servicegraph | ### Component(s)
cmd/otelcontribcol, exporter/prometheus, processor/servicegraph
### What happened?
The type of kafka_producer_connection_count keeps changing between counter and gauge
```
# HELP kafka_producer_connection_count The current number of active connections.
# TYPE kafka_producer_connection_count counter
kafka_producer_connection_count{client_id="producer-1",job="otel-demo-provider",kafka_version="3.1.1",spring_id="kafkaProducerFactory.producer-1"} 1
```
```
# HELP kafka_producer_connection_count The current number of active connections.
# TYPE kafka_producer_connection_count gauge
kafka_producer_connection_count{client_id="producer-1",job="otel-demo-provider"} 1
```
### Collector version
0.66.0
### Environment information
_No response_
### OpenTelemetry Collector configuration
```yaml
receivers:
otlp:
protocols:
grpc:
endpoint: 0.0.0.0:14317
otlp/dummy: # Dummy receiver for the metrics pipeline
protocols:
grpc:
endpoint: localhost:65535
processors:
servicegraph:
metrics_exporter: prometheus/servicegraph # Exporter to send metrics to
dimensions: [cluster, namespace] # Additional dimensions (labels) to be added to the metrics extracted from the resource and span attributes
store: # Configuration for the in-memory store
ttl: 2s # Value to wait for an edge to be completed
max_items: 200 # Amount of edges that will be stored in the storeMap
exporters:
prometheus/servicegraph:
endpoint: 0.0.0.0:9091 # to prometheus
otlp:
endpoint: http://localhost:4317 # to jaeger
tls:
insecure: true
logging:
logLevel: debug
service:
pipelines:
traces:
receivers: [otlp]
processors: [servicegraph]
exporters: [logging, otlp]
metrics/servicegraph:
receivers: [otlp]
processors: []
exporters: [prometheus/servicegraph]
```
### Log output
```shell
2022-11-24T19:18:02.384+0800 error prometheusexporter@v0.64.0/log.go:34 error gathering metrics: collected metric kafka_producer_connection_count label:<name:"client_id" value:"producer-1" > label:<name:"job" value:"otel-demo-provider" > label:<name:"kafka_version" value:"3.1.1" > label:<name:"spring_id" value:"kafkaProducerFactory.producer-1" > counter:<value:2 > should be a Gauge
{"kind": "exporter", "data_type": "metrics", "name": "prometheus"}
github.com/open-telemetry/opentelemetry-collector-contrib/exporter/prometheusexporter.(*promLogger).Println
github.com/open-telemetry/opentelemetry-collector-contrib/exporter/prometheusexporter@v0.64.0/log.go:34
github.com/prometheus/client_golang/prometheus/promhttp.HandlerForTransactional.func1
github.com/prometheus/client_golang@v1.13.1/prometheus/promhttp/http.go:139
net/http.HandlerFunc.ServeHTTP
net/http/server.go:2109
net/http.(*ServeMux).ServeHTTP
net/http/server.go:2487
go.opentelemetry.io/collector/config/confighttp.(*decompressor).wrap.func1
go.opentelemetry.io/collector@v0.64.0/config/confighttp/compression.go:162
net/http.HandlerFunc.ServeHTTP
net/http/server.go:2109
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.(*Handler).ServeHTTP
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp@v0.36.4/handler.go:204
go.opentelemetry.io/collector/config/confighttp.(*clientInfoHandler).ServeHTTP
go.opentelemetry.io/collector@v0.64.0/config/confighttp/clientinfohandler.go:39
net/http.serverHandler.ServeHTTP
net/http/server.go:2947
net/http.(*conn).serve
net/http/server.go:1991
```
### Additional context
_No response_ | 1.0 | The type of kafka_producer_connection_count keeps changing between counter and gauge - ### Component(s)
cmd/otelcontribcol, exporter/prometheus, processor/servicegraph
### What happened?
The type of kafka_producer_connection_count keeps changing between counter and gauge
```
# HELP kafka_producer_connection_count The current number of active connections.
# TYPE kafka_producer_connection_count counter
kafka_producer_connection_count{client_id="producer-1",job="otel-demo-provider",kafka_version="3.1.1",spring_id="kafkaProducerFactory.producer-1"} 1
```
```
# HELP kafka_producer_connection_count The current number of active connections.
# TYPE kafka_producer_connection_count gauge
kafka_producer_connection_count{client_id="producer-1",job="otel-demo-provider"} 1
```
### Collector version
0.66.0
### Environment information
_No response_
### OpenTelemetry Collector configuration
```yaml
receivers:
otlp:
protocols:
grpc:
endpoint: 0.0.0.0:14317
otlp/dummy: # Dummy receiver for the metrics pipeline
protocols:
grpc:
endpoint: localhost:65535
processors:
servicegraph:
metrics_exporter: prometheus/servicegraph # Exporter to send metrics to
dimensions: [cluster, namespace] # Additional dimensions (labels) to be added to the metrics extracted from the resource and span attributes
store: # Configuration for the in-memory store
ttl: 2s # Value to wait for an edge to be completed
max_items: 200 # Amount of edges that will be stored in the storeMap
exporters:
prometheus/servicegraph:
endpoint: 0.0.0.0:9091 # to prometheus
otlp:
endpoint: http://localhost:4317 # to jaeger
tls:
insecure: true
logging:
logLevel: debug
service:
pipelines:
traces:
receivers: [otlp]
processors: [servicegraph]
exporters: [logging, otlp]
metrics/servicegraph:
receivers: [otlp]
processors: []
exporters: [prometheus/servicegraph]
```
### Log output
```shell
2022-11-24T19:18:02.384+0800 error prometheusexporter@v0.64.0/log.go:34 error gathering metrics: collected metric kafka_producer_connection_count label:<name:"client_id" value:"producer-1" > label:<name:"job" value:"otel-demo-provider" > label:<name:"kafka_version" value:"3.1.1" > label:<name:"spring_id" value:"kafkaProducerFactory.producer-1" > counter:<value:2 > should be a Gauge
{"kind": "exporter", "data_type": "metrics", "name": "prometheus"}
github.com/open-telemetry/opentelemetry-collector-contrib/exporter/prometheusexporter.(*promLogger).Println
github.com/open-telemetry/opentelemetry-collector-contrib/exporter/prometheusexporter@v0.64.0/log.go:34
github.com/prometheus/client_golang/prometheus/promhttp.HandlerForTransactional.func1
github.com/prometheus/client_golang@v1.13.1/prometheus/promhttp/http.go:139
net/http.HandlerFunc.ServeHTTP
net/http/server.go:2109
net/http.(*ServeMux).ServeHTTP
net/http/server.go:2487
go.opentelemetry.io/collector/config/confighttp.(*decompressor).wrap.func1
go.opentelemetry.io/collector@v0.64.0/config/confighttp/compression.go:162
net/http.HandlerFunc.ServeHTTP
net/http/server.go:2109
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.(*Handler).ServeHTTP
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp@v0.36.4/handler.go:204
go.opentelemetry.io/collector/config/confighttp.(*clientInfoHandler).ServeHTTP
go.opentelemetry.io/collector@v0.64.0/config/confighttp/clientinfohandler.go:39
net/http.serverHandler.ServeHTTP
net/http/server.go:2947
net/http.(*conn).serve
net/http/server.go:1991
```
### Additional context
_No response_ | process | the type of kafka producer connection count keeps changing between counter and gauge component s cmd otelcontribcol exporter prometheus processor servicegraph what happened the type of kafka producer connection count keeps changing between counter and gauge help kafka producer connection count the current number of active connections type kafka producer connection count counter kafka producer connection count client id producer job otel demo provider kafka version spring id kafkaproducerfactory producer help kafka producer connection count the current number of active connections type kafka producer connection count gauge kafka producer connection count client id producer job otel demo provider collector version environment information no response opentelemetry collector configuration yaml receivers otlp protocols grpc endpoint otlp dummy dummy receiver for the metrics pipeline protocols grpc endpoint localhost processors servicegraph metrics exporter prometheus servicegraph exporter to send metrics to dimensions additional dimensions labels to be added to the metrics extracted from the resource and span attributes store configuration for the in memory store ttl value to wait for an edge to be completed max items amount of edges that will be stored in the storemap exporters prometheus servicegraph endpoint to prometheus otlp endpoint to jaeger tls insecure true logging loglevel debug service pipelines traces receivers processors exporters metrics servicegraph receivers processors exporters log output shell error prometheusexporter log go error gathering metrics collected metric kafka producer connection count label label label label counter should be a gauge kind exporter data type metrics name prometheus github com open telemetry opentelemetry collector contrib exporter prometheusexporter promlogger println github com open telemetry opentelemetry collector contrib exporter prometheusexporter log go github com prometheus client golang prometheus promhttp handlerfortransactional github com prometheus client golang prometheus promhttp http go net http handlerfunc servehttp net http server go net http servemux servehttp net http server go go opentelemetry io collector config confighttp decompressor wrap go opentelemetry io collector config confighttp compression go net http handlerfunc servehttp net http server go go opentelemetry io contrib instrumentation net http otelhttp handler servehttp go opentelemetry io contrib instrumentation net http otelhttp handler go go opentelemetry io collector config confighttp clientinfohandler servehttp go opentelemetry io collector config confighttp clientinfohandler go net http serverhandler servehttp net http server go net http conn serve net http server go additional context no response | 1 |
431,142 | 12,475,656,737 | IssuesEvent | 2020-05-29 12:03:05 | zairza-cetb/bench-routes | https://api.github.com/repos/zairza-cetb/bench-routes | opened | Extend system-metrics with additional details | feature priority:high | Currently, system-metrics monitor the following:
1. CPU usage (percent)
2. Memory usage (percent)
3. Memory cache
4. Disk I/O
There are tons of other details that are required:
1. Network speed
2. CPU clock rate
3. Total number of threads (OS and kernel)
4. Per-core performance
Feel free to comment for other related details. | 1.0 | Extend system-metrics with additional details - Currently, system-metrics monitor the following:
1. CPU usage (percent)
2. Memory usage (percent)
3. Memory cache
4. Disk I/O
There are tons of other details that are required:
1. Network speed
2. CPU clock rate
3. Total number of threads (OS and kernel)
4. Per-core performance
Feel free to comment for other related details. | non_process | extend system metrics with additional details currently system metrics monitor the following cpu usage percent memory usage percent memory cache disk i o there are tons of other details that are required network speed cpu clock rate total number of threads os and kernel per core performance feel free to comment for other related details | 0 |
16,530 | 21,558,535,595 | IssuesEvent | 2022-04-30 20:53:15 | gfx-rs/naga | https://api.github.com/repos/gfx-rs/naga | closed | Secure out-of-bounds accesses | kind: feature area: processing | For WebGPU, we need to guarantee that all out-of-bound accesses are not really happening. We can employ one of the following strategies:
1. Read zeroes, write nothing (follows D3D)
2. Clamp reads and writes (one of the possible behaviors of Vulkan)
3. Detect this and early return (signalling a failure of any sort to wgpu). | 1.0 | Secure out-of-bounds accesses - For WebGPU, we need to guarantee that all out-of-bound accesses are not really happening. We can employ one of the following strategies:
1. Read zeroes, write nothing (follows D3D)
2. Clamp reads and writes (one of the possible behaviors of Vulkan)
3. Detect this and early return (signalling a failure of any sort to wgpu). | process | secure out of bounds accesses for webgpu we need to guarantee that all out of bound accesses are not really happening we can employ one of the following strategies read zeroes write nothing follows clamp reads and writes one of the possible behaviors of vulkan detect this and early return signalling a failure of any sort to wgpu | 1 |
69,331 | 7,131,506,665 | IssuesEvent | 2018-01-22 11:14:48 | dwyl/product-owner-guide | https://api.github.com/repos/dwyl/product-owner-guide | closed | How do I know what's happening on a project? | T1h enhancement please-test | As a product owner
I would like to be able to take a look at the project's backlog and know where things are at
So that I don't have to rely on emails or telephone exchanges with the team. | 1.0 | How do I know what's happening on a project? - As a product owner
I would like to be able to take a look at the project's backlog and know where things are at
So that I don't have to rely on emails or telephone exchanges with the team. | non_process | how do i know what s happening on a project as a product owner i would like to be able to take a look at the project s backlog and know where things are at so that i don t have to rely on emails or telephone exchanges with the team | 0 |
430,818 | 12,466,506,875 | IssuesEvent | 2020-05-28 15:34:44 | kiudee/cs-ranking | https://api.github.com/repos/kiudee/cs-ranking | opened | Check if dataset generator exists and otherwise raise an exception | Priority: Medium | Currently, if the dataset generator receives an invalid dataset, it silently picks a default generator.
https://github.com/kiudee/cs-ranking/blob/5bdc0e414dde196761b7c827369b605a024bae42/csrank/dataset_reader/objectranking/object_ranking_data_generator.py#L35-L36
This is unexpected behavior and should be changed. If the dataset generator is unknown, an exception should be raised. | 1.0 | Check if dataset generator exists and otherwise raise an exception - Currently, if the dataset generator receives an invalid dataset, it silently picks a default generator.
https://github.com/kiudee/cs-ranking/blob/5bdc0e414dde196761b7c827369b605a024bae42/csrank/dataset_reader/objectranking/object_ranking_data_generator.py#L35-L36
This is unexpected behavior and should be changed. If the dataset generator is unknown, an exception should be raised. | non_process | check if dataset generator exists and otherwise raise an exception currently if the dataset generator receives an invalid dataset it silently picks a default generator this is unexpected behavior and should be changed if the dataset generator is unknown an exception should be raised | 0 |
21,238 | 3,875,699,887 | IssuesEvent | 2016-04-12 02:52:37 | ComputationalRadiationPhysics/libSplash | https://api.github.com/repos/ComputationalRadiationPhysics/libSplash | closed | readMeta: ColType is "Random" (First) | affects latest release bug | As commented [here](https://github.com/ComputationalRadiationPhysics/libSplash/pull/203/files#r59259938) the `readMeta` function is acidently returning the `CollectionType` of the *first* found entry in a `id` (time step) instead of the matched entry by name. | 1.0 | readMeta: ColType is "Random" (First) - As commented [here](https://github.com/ComputationalRadiationPhysics/libSplash/pull/203/files#r59259938) the `readMeta` function is acidently returning the `CollectionType` of the *first* found entry in a `id` (time step) instead of the matched entry by name. | non_process | readmeta coltype is random first as commented the readmeta function is acidently returning the collectiontype of the first found entry in a id time step instead of the matched entry by name | 0 |
18,816 | 24,717,914,304 | IssuesEvent | 2022-10-20 08:29:09 | NEARWEEK/CORE | https://api.github.com/repos/NEARWEEK/CORE | closed | Facilitate weekly synch & monthly evaluation calls | Process | ## 🎉 Subtasks
- [x] 1 hour (when not needed reduced to 30 min) weekly start of week call
- [x] Daily check in call of 20 min
- [x] Monthly process evaluation call
## 🤼♂️ Reviewer
@P3ter-NEARWEEK & rest of NEARWEEK team
| 1.0 | Facilitate weekly synch & monthly evaluation calls - ## 🎉 Subtasks
- [x] 1 hour (when not needed reduced to 30 min) weekly start of week call
- [x] Daily check in call of 20 min
- [x] Monthly process evaluation call
## 🤼♂️ Reviewer
@P3ter-NEARWEEK & rest of NEARWEEK team
| process | facilitate weekly synch monthly evaluation calls 🎉 subtasks hour when not needed reduced to min weekly start of week call daily check in call of min monthly process evaluation call 🤼♂️ reviewer nearweek rest of nearweek team | 1 |
280,765 | 21,315,158,444 | IssuesEvent | 2022-04-16 06:24:03 | brandonrhan/pe | https://api.github.com/repos/brandonrhan/pe | opened | The error message of add command is different from UG | severity.Low type.DocumentationBug | The parameter is p/PHONE_NUMBER in UG but it is p/PHONE in error message
<!--session: 1650088334924-14f9646a-82c3-4f8e-a7ee-2eb0f6619db9-->
<!--Version: Desktop v3.4.2--> | 1.0 | The error message of add command is different from UG - The parameter is p/PHONE_NUMBER in UG but it is p/PHONE in error message
<!--session: 1650088334924-14f9646a-82c3-4f8e-a7ee-2eb0f6619db9-->
<!--Version: Desktop v3.4.2--> | non_process | the error message of add command is different from ug the parameter is p phone number in ug but it is p phone in error message | 0 |
137,171 | 20,085,573,314 | IssuesEvent | 2022-02-05 00:18:29 | Azure/WALinuxAgent | https://api.github.com/repos/Azure/WALinuxAgent | closed | [BUG] System crash may cause waagent exception | by design | **Describe the bug: A clear and concise description of what the bug is.**
After system crash and reboot, sometimes there are exceptions in waagent.log:
```
2022-01-06T14:07:06.202463Z ERROR TelemetryEventsCollector ExtHandler Event: name=WALinuxAgent, op=CollectEventErrors, message=DroppedEventsCount: 6
Reasons (first 5 errors): [EventError] Error parsing event: no element found: line 1, column 0: Traceback (most recent call last):
File "bin/WALinuxAgent-2.6.0.2-py2.7.egg/azurelinuxagent/common/event.py", line 206, in parse_event
return parse_json_event(data_str)
File "bin/WALinuxAgent-2.6.0.2-py2.7.egg/azurelinuxagent/common/event.py", line 196, in parse_json_event
data = json.loads(data_str)
File "/usr/lib64/python3.6/json/__init__.py", line 354, in loads
return _default_decoder.decode(s)
File "/usr/lib64/python3.6/json/decoder.py", line 339, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib64/python3.6/json/decoder.py", line 357, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "bin/WALinuxAgent-2.6.0.2-py2.7.egg/azurelinuxagent/common/event.py", line 229, in parse_xml_event
xml_doc = parse_doc(data_str)
File "bin/WALinuxAgent-2.6.0.2-py2.7.egg/azurelinuxagent/common/utils/textutil.py", line 41, in parse_doc
return minidom.parseString(xml_text)
File "/usr/lib64/python3.6/xml/dom/minidom.py", line 1968, in parseString
return expatbuilder.parseString(string)
File "/usr/lib64/python3.6/xml/dom/expatbuilder.py", line 925, in parseString
return builder.parseString(string)
File "/usr/lib64/python3.6/xml/dom/expatbuilder.py", line 223, in parseString
parser.Parse(string, True)
xml.parsers.expat.ExpatError: no element found: line 1, column 0
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "bin/WALinuxAgent-2.6.0.2-py2.7.egg/azurelinuxagent/common/event.py", line 208, in parse_event
return parse_xml_event(data_str)
File "bin/WALinuxAgent-2.6.0.2-py2.7.egg/azurelinuxagent/common/event.py", line 239, in parse_xml_event
raise ValueError(ustr(e))
ValueError: no element found: line 1, column 0
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "bin/WALinuxAgent-2.6.0.2-py2.7.egg/azurelinuxagent/ga/collect_telemetry_events.py", line 430, in process_events
event = parse_event(event_data)
File "bin/WALinuxAgent-2.6.0.2-py2.7.egg/azurelinuxagent/common/event.py", line 210, in parse_event
raise EventError("Error parsing event: {0}".format(ustr(e)))
azurelinuxagent.common.exception.EventError: [EventError] Error parsing event: no element found: line 1, column 0
, duration=0
```
**Steps:**
1. Create a RHEL-8 VM on Azure. Enable kdump.
2. Trigger crash:
`echo c > /proc/sysrq-trigger`
3. Wait for the VM reboot, check /var/log/waagent.log
Usually trigger crash 2-3 times can see these exceptions.
**Distro and WALinuxAgent details (please complete the following information):**
- Distro and Version: RHEL-8.6
- WALinuxAgent version:
WALinuxAgent-2.3.0.2 running on redhat 8.6
Python: 3.6.8
Goal state agent: 2.6.0.2
* If disable auto update, it also happens in WALinuxAgent-2.3.0.2 guest agent | 1.0 | [BUG] System crash may cause waagent exception - **Describe the bug: A clear and concise description of what the bug is.**
After system crash and reboot, sometimes there are exceptions in waagent.log:
```
2022-01-06T14:07:06.202463Z ERROR TelemetryEventsCollector ExtHandler Event: name=WALinuxAgent, op=CollectEventErrors, message=DroppedEventsCount: 6
Reasons (first 5 errors): [EventError] Error parsing event: no element found: line 1, column 0: Traceback (most recent call last):
File "bin/WALinuxAgent-2.6.0.2-py2.7.egg/azurelinuxagent/common/event.py", line 206, in parse_event
return parse_json_event(data_str)
File "bin/WALinuxAgent-2.6.0.2-py2.7.egg/azurelinuxagent/common/event.py", line 196, in parse_json_event
data = json.loads(data_str)
File "/usr/lib64/python3.6/json/__init__.py", line 354, in loads
return _default_decoder.decode(s)
File "/usr/lib64/python3.6/json/decoder.py", line 339, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib64/python3.6/json/decoder.py", line 357, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "bin/WALinuxAgent-2.6.0.2-py2.7.egg/azurelinuxagent/common/event.py", line 229, in parse_xml_event
xml_doc = parse_doc(data_str)
File "bin/WALinuxAgent-2.6.0.2-py2.7.egg/azurelinuxagent/common/utils/textutil.py", line 41, in parse_doc
return minidom.parseString(xml_text)
File "/usr/lib64/python3.6/xml/dom/minidom.py", line 1968, in parseString
return expatbuilder.parseString(string)
File "/usr/lib64/python3.6/xml/dom/expatbuilder.py", line 925, in parseString
return builder.parseString(string)
File "/usr/lib64/python3.6/xml/dom/expatbuilder.py", line 223, in parseString
parser.Parse(string, True)
xml.parsers.expat.ExpatError: no element found: line 1, column 0
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "bin/WALinuxAgent-2.6.0.2-py2.7.egg/azurelinuxagent/common/event.py", line 208, in parse_event
return parse_xml_event(data_str)
File "bin/WALinuxAgent-2.6.0.2-py2.7.egg/azurelinuxagent/common/event.py", line 239, in parse_xml_event
raise ValueError(ustr(e))
ValueError: no element found: line 1, column 0
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "bin/WALinuxAgent-2.6.0.2-py2.7.egg/azurelinuxagent/ga/collect_telemetry_events.py", line 430, in process_events
event = parse_event(event_data)
File "bin/WALinuxAgent-2.6.0.2-py2.7.egg/azurelinuxagent/common/event.py", line 210, in parse_event
raise EventError("Error parsing event: {0}".format(ustr(e)))
azurelinuxagent.common.exception.EventError: [EventError] Error parsing event: no element found: line 1, column 0
, duration=0
```
**Steps:**
1. Create a RHEL-8 VM on Azure. Enable kdump.
2. Trigger crash:
`echo c > /proc/sysrq-trigger`
3. Wait for the VM reboot, check /var/log/waagent.log
Usually trigger crash 2-3 times can see these exceptions.
**Distro and WALinuxAgent details (please complete the following information):**
- Distro and Version: RHEL-8.6
- WALinuxAgent version:
WALinuxAgent-2.3.0.2 running on redhat 8.6
Python: 3.6.8
Goal state agent: 2.6.0.2
* If disable auto update, it also happens in WALinuxAgent-2.3.0.2 guest agent | non_process | system crash may cause waagent exception describe the bug a clear and concise description of what the bug is after system crash and reboot sometimes there are exceptions in waagent log error telemetryeventscollector exthandler event name walinuxagent op collecteventerrors message droppedeventscount reasons first errors error parsing event no element found line column traceback most recent call last file bin walinuxagent egg azurelinuxagent common event py line in parse event return parse json event data str file bin walinuxagent egg azurelinuxagent common event py line in parse json event data json loads data str file usr json init py line in loads return default decoder decode s file usr json decoder py line in decode obj end self raw decode s idx w s end file usr json decoder py line in raw decode raise jsondecodeerror expecting value s err value from none json decoder jsondecodeerror expecting value line column char during handling of the above exception another exception occurred traceback most recent call last file bin walinuxagent egg azurelinuxagent common event py line in parse xml event xml doc parse doc data str file bin walinuxagent egg azurelinuxagent common utils textutil py line in parse doc return minidom parsestring xml text file usr xml dom minidom py line in parsestring return expatbuilder parsestring string file usr xml dom expatbuilder py line in parsestring return builder parsestring string file usr xml dom expatbuilder py line in parsestring parser parse string true xml parsers expat expaterror no element found line column during handling of the above exception another exception occurred traceback most recent call last file bin walinuxagent egg azurelinuxagent common event py line in parse event return parse xml event data str file bin walinuxagent egg azurelinuxagent common event py line in parse xml event raise valueerror ustr e valueerror no element found line column during handling of the above exception another exception occurred traceback most recent call last file bin walinuxagent egg azurelinuxagent ga collect telemetry events py line in process events event parse event event data file bin walinuxagent egg azurelinuxagent common event py line in parse event raise eventerror error parsing event format ustr e azurelinuxagent common exception eventerror error parsing event no element found line column duration steps create a rhel vm on azure enable kdump trigger crash echo c proc sysrq trigger wait for the vm reboot check var log waagent log usually trigger crash times can see these exceptions distro and walinuxagent details please complete the following information distro and version rhel walinuxagent version walinuxagent running on redhat python goal state agent if disable auto update it also happens in walinuxagent guest agent | 0 |
70,745 | 15,105,715,970 | IssuesEvent | 2021-02-08 13:25:26 | mozilla-mobile/fenix | https://api.github.com/repos/mozilla-mobile/fenix | closed | [Bug]Screenshot feature in private browsing mode | Feature:Privacy&Security Feature:PrivateBrowsing eng:qa:needed 🐞 bug | ## Steps to reproduce
EDIT: Uploaded video to be more clear.
1. Take a screenshot.
2. Minimize the application.
3. Go back to Fenix.
4. Take a screenshot.
### Expected behavior
You will be able to take a screenshot.
### Actual behavior
Fenix will say "This app doesn't allow taking screenshots".
https://user-images.githubusercontent.com/73644544/106727709-b4ae5580-6646-11eb-959d-702839ab00e4.mp4
### Device information
* Device vendor / model and Android version: Mi 9T Pro / MIUI 12
* Firefox for Android version: Nightly (Build #2015791019)
| True | [Bug]Screenshot feature in private browsing mode - ## Steps to reproduce
EDIT: Uploaded video to be more clear.
1. Take a screenshot.
2. Minimize the application.
3. Go back to Fenix.
4. Take a screenshot.
### Expected behavior
You will be able to take a screenshot.
### Actual behavior
Fenix will say "This app doesn't allow taking screenshots".
https://user-images.githubusercontent.com/73644544/106727709-b4ae5580-6646-11eb-959d-702839ab00e4.mp4
### Device information
* Device vendor / model and Android version: Mi 9T Pro / MIUI 12
* Firefox for Android version: Nightly (Build #2015791019)
| non_process | screenshot feature in private browsing mode steps to reproduce edit uploaded video to be more clear take a screenshot minimize the application go back to fenix take a screenshot expected behavior you will be able to take a screenshot actual behavior fenix will say this app doesn t allow taking screenshots device information device vendor model and android version mi pro miui firefox for android version nightly build | 0 |
7,713 | 10,819,971,158 | IssuesEvent | 2019-11-08 15:27:25 | deeplearningunb/pneumonia-diagnose | https://api.github.com/repos/deeplearningunb/pneumonia-diagnose | opened | Adicionar funcoes de data augmentation | preprocessing | Adicionar funcoes relevantes para o tipo de dado trabalhado
- Zoom
- Random rotation
- Flip
etc | 1.0 | Adicionar funcoes de data augmentation - Adicionar funcoes relevantes para o tipo de dado trabalhado
- Zoom
- Random rotation
- Flip
etc | process | adicionar funcoes de data augmentation adicionar funcoes relevantes para o tipo de dado trabalhado zoom random rotation flip etc | 1 |
13,632 | 16,240,796,010 | IssuesEvent | 2021-05-07 09:17:51 | hermeznetwork/hermez-node | https://api.github.com/repos/hermeznetwork/hermez-node | closed | Save sender IP address at TX table | txprocessor | ## Rationale
Today sender's IP address is stored at tx-pool table but it is not stored in tx table after the transaction has been forged. We need to save sender's IP address also in tx table. | 1.0 | Save sender IP address at TX table - ## Rationale
Today sender's IP address is stored at tx-pool table but it is not stored in tx table after the transaction has been forged. We need to save sender's IP address also in tx table. | process | save sender ip address at tx table rationale today sender s ip address is stored at tx pool table but it is not stored in tx table after the transaction has been forged we need to save sender s ip address also in tx table | 1 |
2,096 | 4,931,466,634 | IssuesEvent | 2016-11-28 10:17:16 | tomlutzenberger/frontal-coding-guideline | https://api.github.com/repos/tomlutzenberger/frontal-coding-guideline | opened | Browser-Sync | process suggestion | **BrowserSync (https://www.browsersync.io)**
Im Gegensatz zu `grunt-watch`, werden hier die Aktionen in allen Browsern (Scroll, Click etc.) syncronisiert und ermöglichen so paralleles Testing (gedacht für manuelle Tests) | 1.0 | Browser-Sync - **BrowserSync (https://www.browsersync.io)**
Im Gegensatz zu `grunt-watch`, werden hier die Aktionen in allen Browsern (Scroll, Click etc.) syncronisiert und ermöglichen so paralleles Testing (gedacht für manuelle Tests) | process | browser sync browsersync im gegensatz zu grunt watch werden hier die aktionen in allen browsern scroll click etc syncronisiert und ermöglichen so paralleles testing gedacht für manuelle tests | 1 |
51,958 | 12,829,931,710 | IssuesEvent | 2020-07-07 00:32:06 | googleapis/nodejs-dlp | https://api.github.com/repos/googleapis/nodejs-dlp | closed | redact: should redact multiple sensitive data types from an image failed | api: dlp buildcop: issue priority: p1 type: bug | This test failed!
To configure my behavior, see [the Build Cop Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/master/packages/buildcop).
If I'm commenting on this issue too often, add the `buildcop: quiet` label and
I will stop commenting.
---
commit: 10a87626c46bdc5753d366fe02d1894614856d4f
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/30db634f-75b1-473b-ae0e-4d6749f2775c), [Sponge](http://sponge2/30db634f-75b1-473b-ae0e-4d6749f2775c)
status: failed
<details><summary>Test output</summary><br><pre>expected 0.05801004235742938 to be below 0.03
+ expected - actual
-0.05801004235742938
+0.03
AssertionError: expected 0.05801004235742938 to be below 0.03
at Context.it (system-test/redact.test.js:103:12)
at process._tickCallback (internal/process/next_tick.js:68:7)</pre></details> | 1.0 | redact: should redact multiple sensitive data types from an image failed - This test failed!
To configure my behavior, see [the Build Cop Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/master/packages/buildcop).
If I'm commenting on this issue too often, add the `buildcop: quiet` label and
I will stop commenting.
---
commit: 10a87626c46bdc5753d366fe02d1894614856d4f
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/30db634f-75b1-473b-ae0e-4d6749f2775c), [Sponge](http://sponge2/30db634f-75b1-473b-ae0e-4d6749f2775c)
status: failed
<details><summary>Test output</summary><br><pre>expected 0.05801004235742938 to be below 0.03
+ expected - actual
-0.05801004235742938
+0.03
AssertionError: expected 0.05801004235742938 to be below 0.03
at Context.it (system-test/redact.test.js:103:12)
at process._tickCallback (internal/process/next_tick.js:68:7)</pre></details> | non_process | redact should redact multiple sensitive data types from an image failed this test failed to configure my behavior see if i m commenting on this issue too often add the buildcop quiet label and i will stop commenting commit buildurl status failed test output expected to be below expected actual assertionerror expected to be below at context it system test redact test js at process tickcallback internal process next tick js | 0 |
18,144 | 24,186,783,995 | IssuesEvent | 2022-09-23 13:56:42 | cloudfoundry/korifi | https://api.github.com/repos/cloudfoundry/korifi | closed | [Feature]: Developer can push apps using the top-level `health-check-http-endpoint` field in the manifest | Top-level process config | ### Background
**As a** developer
**I want** top-level process configuration in manifests to be supported
**So that** I can use shortcut `cf push` flags like `-c`, `-i`, `-m` etc.
### Acceptance Criteria
* **GIVEN** I have the following node app:
```js
var http = require('http');
http.createServer(function (request, response) {
if (request.url == '/health') {
response.writeHead(200, {'Content-Type': 'text/plain'});
response.end('ok');
} else {
response.writeHead(500, {'Content-Type': 'text/plain'});
response.end('no');
}
}).listen(process.env.PORT);
```
with the following `manifest.yml`:
```yaml
---
applications:
- name: real-app
health-check-http-endpoint: /health
processes:
- type: web
health-check-type: http
```
**WHEN I** `cf push`
**THEN I** see the push succeeds with an output similar to this:
```
name: test
requested state: started
routes: test.vcap.me
last uploaded: Mon 29 Aug 16:28:36 UTC 2022
stack: cflinuxfs3
buildpacks:
name version detect output buildpack name
nodejs_buildpack 1.7.61 nodejs nodejs
type: web
sidecars:
instances: 1/1
memory usage: 256M
start command: npm start
state since cpu memory disk details
#0 running 2022-08-29T16:28:54Z 1.6% 42.3M of 256M 115.7M of 1G
```
* **GIVEN** I have the same app with the following manifest:
```yaml
---
applications:
- name: my-app
health-check-http-endpoint: /wrong
processes:
- type: web
health-check-type: http
health-check-http-endpoint: /health
```
**WHEN I** `cf push`
**THEN I** see the push succeeds with the same output as above | 1.0 | [Feature]: Developer can push apps using the top-level `health-check-http-endpoint` field in the manifest - ### Background
**As a** developer
**I want** top-level process configuration in manifests to be supported
**So that** I can use shortcut `cf push` flags like `-c`, `-i`, `-m` etc.
### Acceptance Criteria
* **GIVEN** I have the following node app:
```js
var http = require('http');
http.createServer(function (request, response) {
if (request.url == '/health') {
response.writeHead(200, {'Content-Type': 'text/plain'});
response.end('ok');
} else {
response.writeHead(500, {'Content-Type': 'text/plain'});
response.end('no');
}
}).listen(process.env.PORT);
```
with the following `manifest.yml`:
```yaml
---
applications:
- name: real-app
health-check-http-endpoint: /health
processes:
- type: web
health-check-type: http
```
**WHEN I** `cf push`
**THEN I** see the push succeeds with an output similar to this:
```
name: test
requested state: started
routes: test.vcap.me
last uploaded: Mon 29 Aug 16:28:36 UTC 2022
stack: cflinuxfs3
buildpacks:
name version detect output buildpack name
nodejs_buildpack 1.7.61 nodejs nodejs
type: web
sidecars:
instances: 1/1
memory usage: 256M
start command: npm start
state since cpu memory disk details
#0 running 2022-08-29T16:28:54Z 1.6% 42.3M of 256M 115.7M of 1G
```
* **GIVEN** I have the same app with the following manifest:
```yaml
---
applications:
- name: my-app
health-check-http-endpoint: /wrong
processes:
- type: web
health-check-type: http
health-check-http-endpoint: /health
```
**WHEN I** `cf push`
**THEN I** see the push succeeds with the same output as above | process | developer can push apps using the top level health check http endpoint field in the manifest background as a developer i want top level process configuration in manifests to be supported so that i can use shortcut cf push flags like c i m etc acceptance criteria given i have the following node app js var http require http http createserver function request response if request url health response writehead content type text plain response end ok else response writehead content type text plain response end no listen process env port with the following manifest yml yaml applications name real app health check http endpoint health processes type web health check type http when i cf push then i see the push succeeds with an output similar to this name test requested state started routes test vcap me last uploaded mon aug utc stack buildpacks name version detect output buildpack name nodejs buildpack nodejs nodejs type web sidecars instances memory usage start command npm start state since cpu memory disk details running of of given i have the same app with the following manifest yaml applications name my app health check http endpoint wrong processes type web health check type http health check http endpoint health when i cf push then i see the push succeeds with the same output as above | 1 |
19,044 | 25,045,768,657 | IssuesEvent | 2022-11-05 08:04:11 | googleapis/google-cloud-python | https://api.github.com/repos/googleapis/google-cloud-python | opened | Your .repo-metadata.json file has a problem 🤒 | type: process repo-metadata: lint | You have a problem with your .repo-metadata.json file:
Result of scan 📈:
* api_shortname 'apiName' invalid in containers/python-bootstrap-container/.repo-metadata.json
☝️ Once you address these problems, you can close this issue.
### Need help?
* [Schema definition](https://github.com/googleapis/repo-automation-bots/blob/main/packages/repo-metadata-lint/src/repo-metadata-schema.json): lists valid options for each field.
* [API index](https://github.com/googleapis/googleapis/blob/master/api-index-v1.json): for gRPC libraries **api_shortname** should match the subdomain of an API's **hostName**.
* Reach out to **go/github-automation** if you have any questions. | 1.0 | Your .repo-metadata.json file has a problem 🤒 - You have a problem with your .repo-metadata.json file:
Result of scan 📈:
* api_shortname 'apiName' invalid in containers/python-bootstrap-container/.repo-metadata.json
☝️ Once you address these problems, you can close this issue.
### Need help?
* [Schema definition](https://github.com/googleapis/repo-automation-bots/blob/main/packages/repo-metadata-lint/src/repo-metadata-schema.json): lists valid options for each field.
* [API index](https://github.com/googleapis/googleapis/blob/master/api-index-v1.json): for gRPC libraries **api_shortname** should match the subdomain of an API's **hostName**.
* Reach out to **go/github-automation** if you have any questions. | process | your repo metadata json file has a problem 🤒 you have a problem with your repo metadata json file result of scan 📈 api shortname apiname invalid in containers python bootstrap container repo metadata json ☝️ once you address these problems you can close this issue need help lists valid options for each field for grpc libraries api shortname should match the subdomain of an api s hostname reach out to go github automation if you have any questions | 1 |
359,432 | 10,676,044,634 | IssuesEvent | 2019-10-21 13:01:33 | rubyforgood/babywearing | https://api.github.com/repos/rubyforgood/babywearing | closed | Item images in browsable inventory should be the same size | Hacktoberfest Priority: High beginner friendly | See #59
All images (placeholder and uploaded) should be the same size.
- Each `item` (ie `/carriers/5/edit) has a photo upload option that is used for that specific item. | 1.0 | Item images in browsable inventory should be the same size - See #59
All images (placeholder and uploaded) should be the same size.
- Each `item` (ie `/carriers/5/edit) has a photo upload option that is used for that specific item. | non_process | item images in browsable inventory should be the same size see all images placeholder and uploaded should be the same size each item ie carriers edit has a photo upload option that is used for that specific item | 0 |
21,608 | 30,014,299,021 | IssuesEvent | 2023-06-26 17:27:09 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | System.Diagnostics.Process with CreateNoWindow does not redirect stdout/stderr to parent process | area-System.Diagnostics.Process needs-author-action | ### Description
When using `System.Diagnostics.Process` with `CreateNoWindow = true` the output does not get redirected to the parent process. It will end up in no output.
The [docs](https://docs.microsoft.com/en-us/dotnet/api/system.diagnostics.processstartinfo.createnowindow?view=net-6.0) don't say anything about this behaviour, thats why I'm opening this issue and `CreateNoWindow` changes the behaviour if stdout/err gets redirected or not.
### Reproduction Steps
```cs
using System.Diagnostics;
if (args.Length >= 1 && args[0] == "--start-process")
{
var currentExecutable = Environment.ProcessPath;
if (currentExecutable == null)
{
Console.Error.WriteLine("Could not get current executable path");
return;
}
var playwrightStartInfo = new ProcessStartInfo(currentExecutable)
{
UseShellExecute = false,
RedirectStandardError = false,
RedirectStandardOutput = false,
CreateNoWindow = true,
};
using var pwProcess = new Process()
{
StartInfo = playwrightStartInfo,
};
pwProcess.Start();
pwProcess.WaitForExit();
}
else
{
Console.WriteLine("Hello stdout!");
Console.Error.WriteLine("Hello stderr!");
}
```
Run it with `./bin/Debug/net6.0/dotnetrepro.exe --start-process`.
### Expected behavior
`Hello stderr!` and `Hello stdout!` are getting printed.
### Actual behavior
They get not printed.
### Regression?
_No response_
### Known Workarounds
Remove `CreateNoWindow = true`.
or:
Using `RedirectStandardError = true` and `RedirectStandardOutput = true` and manually redirecting it to the parent stdout/stderr.
### Configuration
I can only reproduce it on Windows 10 + 11 amd64.
### Other information
```
PS C:\Users\maxsc\Desktop\dotnet-process-redirect-issue> dotnet --list-sdks
6.0.102 [C:\Program Files\dotnet\sdk]
``` | 1.0 | System.Diagnostics.Process with CreateNoWindow does not redirect stdout/stderr to parent process - ### Description
When using `System.Diagnostics.Process` with `CreateNoWindow = true` the output does not get redirected to the parent process. It will end up in no output.
The [docs](https://docs.microsoft.com/en-us/dotnet/api/system.diagnostics.processstartinfo.createnowindow?view=net-6.0) don't say anything about this behaviour, thats why I'm opening this issue and `CreateNoWindow` changes the behaviour if stdout/err gets redirected or not.
### Reproduction Steps
```cs
using System.Diagnostics;
if (args.Length >= 1 && args[0] == "--start-process")
{
var currentExecutable = Environment.ProcessPath;
if (currentExecutable == null)
{
Console.Error.WriteLine("Could not get current executable path");
return;
}
var playwrightStartInfo = new ProcessStartInfo(currentExecutable)
{
UseShellExecute = false,
RedirectStandardError = false,
RedirectStandardOutput = false,
CreateNoWindow = true,
};
using var pwProcess = new Process()
{
StartInfo = playwrightStartInfo,
};
pwProcess.Start();
pwProcess.WaitForExit();
}
else
{
Console.WriteLine("Hello stdout!");
Console.Error.WriteLine("Hello stderr!");
}
```
Run it with `./bin/Debug/net6.0/dotnetrepro.exe --start-process`.
### Expected behavior
`Hello stderr!` and `Hello stdout!` are getting printed.
### Actual behavior
They get not printed.
### Regression?
_No response_
### Known Workarounds
Remove `CreateNoWindow = true`.
or:
Using `RedirectStandardError = true` and `RedirectStandardOutput = true` and manually redirecting it to the parent stdout/stderr.
### Configuration
I can only reproduce it on Windows 10 + 11 amd64.
### Other information
```
PS C:\Users\maxsc\Desktop\dotnet-process-redirect-issue> dotnet --list-sdks
6.0.102 [C:\Program Files\dotnet\sdk]
``` | process | system diagnostics process with createnowindow does not redirect stdout stderr to parent process description when using system diagnostics process with createnowindow true the output does not get redirected to the parent process it will end up in no output the don t say anything about this behaviour thats why i m opening this issue and createnowindow changes the behaviour if stdout err gets redirected or not reproduction steps cs using system diagnostics if args length args start process var currentexecutable environment processpath if currentexecutable null console error writeline could not get current executable path return var playwrightstartinfo new processstartinfo currentexecutable useshellexecute false redirectstandarderror false redirectstandardoutput false createnowindow true using var pwprocess new process startinfo playwrightstartinfo pwprocess start pwprocess waitforexit else console writeline hello stdout console error writeline hello stderr run it with bin debug dotnetrepro exe start process expected behavior hello stderr and hello stdout are getting printed actual behavior they get not printed regression no response known workarounds remove createnowindow true or using redirectstandarderror true and redirectstandardoutput true and manually redirecting it to the parent stdout stderr configuration i can only reproduce it on windows other information ps c users maxsc desktop dotnet process redirect issue dotnet list sdks | 1 |
21,116 | 28,079,791,165 | IssuesEvent | 2023-03-30 04:58:09 | AssetRipper/AssetRipper | https://api.github.com/repos/AssetRipper/AssetRipper | closed | [Bug]: Fonts material problems | bug help wanted good first issue export processing | ### Describe the issue
### Are you on the latest version of AssetRipper?
Yes, I'm on the latest release of AssetRipper.
### Which release are you using?
Linux x64
### Which game did this occur on?
My own test project here (ignore the name, it doesn't have to do with shaders):
[ShadersExportTest.zip](https://github.com/AssetRipper/AssetRipper/files/10327941/ShadersExportTest.zip)
Issue is very likely affecting Bug Fables: https://steamdb.info/app/1082710/
### Which Unity version did this occur on?
2018.4.12f1
### Is the game Mono or IL2Cpp?
Mono
### Describe the issue.
If you check in my project, you will see there is a font assigned to a text mesh that is rendered in front of the camera. Notice that there is no texture or material inside the project, but they are present in the asset explorer (they were auto generated on import).
If I extract with AssetRipper, now the render is wrong. This is because AssetRipper extracted the font material, but the project is opened after extraction, it still autogenerate the font material, but binds the TextMesh to the wrong one that AssetRipper put. I have to remove the material and reset the font to the textmesh so it renders.
### Relevant log output
[AssetRipper.log](https://github.com/AssetRipper/AssetRipper/files/10327943/AssetRipper.log)
| 1.0 | [Bug]: Fonts material problems - ### Describe the issue
### Are you on the latest version of AssetRipper?
Yes, I'm on the latest release of AssetRipper.
### Which release are you using?
Linux x64
### Which game did this occur on?
My own test project here (ignore the name, it doesn't have to do with shaders):
[ShadersExportTest.zip](https://github.com/AssetRipper/AssetRipper/files/10327941/ShadersExportTest.zip)
Issue is very likely affecting Bug Fables: https://steamdb.info/app/1082710/
### Which Unity version did this occur on?
2018.4.12f1
### Is the game Mono or IL2Cpp?
Mono
### Describe the issue.
If you check in my project, you will see there is a font assigned to a text mesh that is rendered in front of the camera. Notice that there is no texture or material inside the project, but they are present in the asset explorer (they were auto generated on import).
If I extract with AssetRipper, now the render is wrong. This is because AssetRipper extracted the font material, but the project is opened after extraction, it still autogenerate the font material, but binds the TextMesh to the wrong one that AssetRipper put. I have to remove the material and reset the font to the textmesh so it renders.
### Relevant log output
[AssetRipper.log](https://github.com/AssetRipper/AssetRipper/files/10327943/AssetRipper.log)
| process | fonts material problems describe the issue are you on the latest version of assetripper yes i m on the latest release of assetripper which release are you using linux which game did this occur on my own test project here ignore the name it doesn t have to do with shaders issue is very likely affecting bug fables which unity version did this occur on is the game mono or mono describe the issue if you check in my project you will see there is a font assigned to a text mesh that is rendered in front of the camera notice that there is no texture or material inside the project but they are present in the asset explorer they were auto generated on import if i extract with assetripper now the render is wrong this is because assetripper extracted the font material but the project is opened after extraction it still autogenerate the font material but binds the textmesh to the wrong one that assetripper put i have to remove the material and reset the font to the textmesh so it renders relevant log output | 1 |
9,747 | 12,734,482,024 | IssuesEvent | 2020-06-25 13:58:20 | nodejs/node | https://api.github.com/repos/nodejs/node | opened | implement process.exitWithException() | feature request process | In the stalled PR https://github.com/nodejs/node/pull/25715, @Fishrock123 was working to introduce a new API... from the original description:
> Adds a public way to access node::FatalException from javascript, as process.exitWithException().
>
> If an error stack is available on the value, this method of exiting does not add additional context, unlike regular re-throwing, yet also uses the regular error printing logic. This behavior is particularly desirable when doing 'fatal exits' from the unhandledRejection event.
While the PR had plenty of support to move forward, there was an edge case around the `uncaughtException` event handler that would need to be worked through in order for it to move forward.
The original PR stalled out and has been closed, but given the support the idea had, I wanted to make sure to open a Feature Request issue in case someone else wanted to pick up the work and move it forward. | 1.0 | implement process.exitWithException() - In the stalled PR https://github.com/nodejs/node/pull/25715, @Fishrock123 was working to introduce a new API... from the original description:
> Adds a public way to access node::FatalException from javascript, as process.exitWithException().
>
> If an error stack is available on the value, this method of exiting does not add additional context, unlike regular re-throwing, yet also uses the regular error printing logic. This behavior is particularly desirable when doing 'fatal exits' from the unhandledRejection event.
While the PR had plenty of support to move forward, there was an edge case around the `uncaughtException` event handler that would need to be worked through in order for it to move forward.
The original PR stalled out and has been closed, but given the support the idea had, I wanted to make sure to open a Feature Request issue in case someone else wanted to pick up the work and move it forward. | process | implement process exitwithexception in the stalled pr was working to introduce a new api from the original description adds a public way to access node fatalexception from javascript as process exitwithexception if an error stack is available on the value this method of exiting does not add additional context unlike regular re throwing yet also uses the regular error printing logic this behavior is particularly desirable when doing fatal exits from the unhandledrejection event while the pr had plenty of support to move forward there was an edge case around the uncaughtexception event handler that would need to be worked through in order for it to move forward the original pr stalled out and has been closed but given the support the idea had i wanted to make sure to open a feature request issue in case someone else wanted to pick up the work and move it forward | 1 |
387,977 | 11,472,768,530 | IssuesEvent | 2020-02-09 19:12:43 | Code-and-Response/Prometeo | https://api.github.com/repos/Code-and-Response/Prometeo | closed | Logistics/operations: Prepare scope for February field test | high-priority logistics-operations | There is a prescribed or preventative burn that will occur in mid-February. Several fires are intentionally lit at several locations throughout Catalonia in order to remove combustible material ahead of real wildfires.
This will involve both the local GRAF team as well as the 70 plus firefighters around the area. At each site, there will be about 10 firefighters executing the burns, and the Prometeo team will work with one of those teams to test the device.
The goal is to test the next version of the hardware, firmware, and a dashboard. | 1.0 | Logistics/operations: Prepare scope for February field test - There is a prescribed or preventative burn that will occur in mid-February. Several fires are intentionally lit at several locations throughout Catalonia in order to remove combustible material ahead of real wildfires.
This will involve both the local GRAF team as well as the 70 plus firefighters around the area. At each site, there will be about 10 firefighters executing the burns, and the Prometeo team will work with one of those teams to test the device.
The goal is to test the next version of the hardware, firmware, and a dashboard. | non_process | logistics operations prepare scope for february field test there is a prescribed or preventative burn that will occur in mid february several fires are intentionally lit at several locations throughout catalonia in order to remove combustible material ahead of real wildfires this will involve both the local graf team as well as the plus firefighters around the area at each site there will be about firefighters executing the burns and the prometeo team will work with one of those teams to test the device the goal is to test the next version of the hardware firmware and a dashboard | 0 |
119,059 | 4,760,279,794 | IssuesEvent | 2016-10-25 02:20:36 | PowerlineApp/powerline-mobile | https://api.github.com/repos/PowerlineApp/powerline-mobile | opened | New Event - Pre-fill RSVP Options | bug P4 - Really Low Priority | It would be great if the first two RSVP answer options were pre-filled with:
"Yes, I can make it"
"No, I can't make it"
But still editable by the user. | 1.0 | New Event - Pre-fill RSVP Options - It would be great if the first two RSVP answer options were pre-filled with:
"Yes, I can make it"
"No, I can't make it"
But still editable by the user. | non_process | new event pre fill rsvp options it would be great if the first two rsvp answer options were pre filled with yes i can make it no i can t make it but still editable by the user | 0 |
96,548 | 8,617,574,510 | IssuesEvent | 2018-11-20 06:17:43 | humera987/FXLabs-Test-Automation | https://api.github.com/repos/humera987/FXLabs-Test-Automation | opened | projecttesting20 : ApiV1DashboardCountRunsBetweenGetPathParamFromdateMysqlSqlInjectionTimebound | projecttesting20 | Project : projecttesting20
Job : UAT
Env : UAT
Region : US_WEST
Result : fail
Status Code : 404
Headers : {X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Set-Cookie=[SESSION=ZmFlYTZjYjEtODAxOS00MmNhLWExNjQtNDY3MzdmNzkwMDNm; Path=/; HttpOnly], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Tue, 20 Nov 2018 06:17:41 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/dashboard/count-runs-between?fromDate=
Request :
Response :
{
"timestamp" : "2018-11-20T06:17:41.561+0000",
"status" : 404,
"error" : "Not Found",
"message" : "No message available",
"path" : "/api/v1/api/v1/dashboard/count-runs-between"
}
Logs :
Assertion [@ResponseTime < 7000 OR @ResponseTime > 10000] resolved-to [1321 < 7000 OR 1321 > 10000] result [Passed]Assertion [@StatusCode != 404] resolved-to [404 != 404] result [Failed]
--- FX Bot --- | 1.0 | projecttesting20 : ApiV1DashboardCountRunsBetweenGetPathParamFromdateMysqlSqlInjectionTimebound - Project : projecttesting20
Job : UAT
Env : UAT
Region : US_WEST
Result : fail
Status Code : 404
Headers : {X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Set-Cookie=[SESSION=ZmFlYTZjYjEtODAxOS00MmNhLWExNjQtNDY3MzdmNzkwMDNm; Path=/; HttpOnly], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Tue, 20 Nov 2018 06:17:41 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/dashboard/count-runs-between?fromDate=
Request :
Response :
{
"timestamp" : "2018-11-20T06:17:41.561+0000",
"status" : 404,
"error" : "Not Found",
"message" : "No message available",
"path" : "/api/v1/api/v1/dashboard/count-runs-between"
}
Logs :
Assertion [@ResponseTime < 7000 OR @ResponseTime > 10000] resolved-to [1321 < 7000 OR 1321 > 10000] result [Passed]Assertion [@StatusCode != 404] resolved-to [404 != 404] result [Failed]
--- FX Bot --- | non_process | project job uat env uat region us west result fail status code headers x content type options x xss protection cache control pragma expires x frame options set cookie content type transfer encoding date endpoint request response timestamp status error not found message no message available path api api dashboard count runs between logs assertion resolved to result assertion resolved to result fx bot | 0 |
31,698 | 4,714,507,299 | IssuesEvent | 2016-10-15 01:09:24 | institutotim/timtec | https://api.github.com/repos/institutotim/timtec | reopened | [importante] Melhorar o cadastro de usuário | waiting test | 1. [x] No form de cadastro inicial, verificar se o campo "nome de usuário" corresponde a "login". Se sim e não for obrigatório, retirar;
2. [x] Ainda no form de cadastro inicial, acrescentar os campos "primeiro nome", "sobrenome", "estado" e "cidade" e deixar como campos obrigatórios;
3. [x] No form de cadastro interno (edição de perfil http://demo.timtec.com.br/profile/edit), acrescentar campos para data de nascimento, redes sociais (facebook, twitter, whatsapp[campo de telefone com ddd], telegram)
4. [x] No cadastro, inserir uma mensagem (tip) ao usuário "Após o cadastro, você deve se logar usando email e senha";
5. [x] Implementar os itens anteriores nos 2 temas: tema ifcolors (http://demo.timtec.com.br/accounts/signup/) + tema timtec (http://mooc.timtec.com.br/#)
Tela de cadastro atual tema IF:
Tela de cadastro atual tema timtec:
7. [x] Detalhe importante: nos temas atuais o login do usuário é por login e senha. Depois das mudanças acima, Isto deve ser trocado para email e senha.
ex.: Login atual:
Como deve ser:
 | 1.0 | [importante] Melhorar o cadastro de usuário - 1. [x] No form de cadastro inicial, verificar se o campo "nome de usuário" corresponde a "login". Se sim e não for obrigatório, retirar;
2. [x] Ainda no form de cadastro inicial, acrescentar os campos "primeiro nome", "sobrenome", "estado" e "cidade" e deixar como campos obrigatórios;
3. [x] No form de cadastro interno (edição de perfil http://demo.timtec.com.br/profile/edit), acrescentar campos para data de nascimento, redes sociais (facebook, twitter, whatsapp[campo de telefone com ddd], telegram)
4. [x] No cadastro, inserir uma mensagem (tip) ao usuário "Após o cadastro, você deve se logar usando email e senha";
5. [x] Implementar os itens anteriores nos 2 temas: tema ifcolors (http://demo.timtec.com.br/accounts/signup/) + tema timtec (http://mooc.timtec.com.br/#)
Tela de cadastro atual tema IF:
Tela de cadastro atual tema timtec:
7. [x] Detalhe importante: nos temas atuais o login do usuário é por login e senha. Depois das mudanças acima, Isto deve ser trocado para email e senha.
ex.: Login atual:
Como deve ser:
 | non_process | melhorar o cadastro de usuário no form de cadastro inicial verificar se o campo nome de usuário corresponde a login se sim e não for obrigatório retirar ainda no form de cadastro inicial acrescentar os campos primeiro nome sobrenome estado e cidade e deixar como campos obrigatórios no form de cadastro interno edição de perfil acrescentar campos para data de nascimento redes sociais facebook twitter whatsapp telegram no cadastro inserir uma mensagem tip ao usuário após o cadastro você deve se logar usando email e senha implementar os itens anteriores nos temas tema ifcolors tema timtec tela de cadastro atual tema if tela de cadastro atual tema timtec detalhe importante nos temas atuais o login do usuário é por login e senha depois das mudanças acima isto deve ser trocado para email e senha ex login atual como deve ser | 0 |
21,961 | 30,456,171,093 | IssuesEvent | 2023-07-16 22:52:32 | h4sh5/pypi-auto-scanner | https://api.github.com/repos/h4sh5/pypi-auto-scanner | opened | roblox-pyc 1.16.25 has 2 GuardDog issues | guarddog silent-process-execution | https://pypi.org/project/roblox-pyc
https://inspector.pypi.io/project/roblox-pyc
```{
"dependency": "roblox-pyc",
"version": "1.16.25",
"result": {
"issues": 2,
"errors": {},
"results": {
"silent-process-execution": [
{
"location": "roblox-pyc-1.16.25/src/robloxpy.py:86",
"code": " subprocess.call([\"luarocks\", \"--version\"], stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL, stdin=subprocess.DEVNULL)",
"message": "This package is silently executing an external binary, redirecting stdout, stderr and stdin to /dev/null"
},
{
"location": "roblox-pyc-1.16.25/src/robloxpy.py:93",
"code": " subprocess.call([\"moonc\", \"--version\"], stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL, stdin=subprocess.DEVNULL)",
"message": "This package is silently executing an external binary, redirecting stdout, stderr and stdin to /dev/null"
}
]
},
"path": "/tmp/tmpz_uck_vg/roblox-pyc"
}
}``` | 1.0 | roblox-pyc 1.16.25 has 2 GuardDog issues - https://pypi.org/project/roblox-pyc
https://inspector.pypi.io/project/roblox-pyc
```{
"dependency": "roblox-pyc",
"version": "1.16.25",
"result": {
"issues": 2,
"errors": {},
"results": {
"silent-process-execution": [
{
"location": "roblox-pyc-1.16.25/src/robloxpy.py:86",
"code": " subprocess.call([\"luarocks\", \"--version\"], stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL, stdin=subprocess.DEVNULL)",
"message": "This package is silently executing an external binary, redirecting stdout, stderr and stdin to /dev/null"
},
{
"location": "roblox-pyc-1.16.25/src/robloxpy.py:93",
"code": " subprocess.call([\"moonc\", \"--version\"], stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL, stdin=subprocess.DEVNULL)",
"message": "This package is silently executing an external binary, redirecting stdout, stderr and stdin to /dev/null"
}
]
},
"path": "/tmp/tmpz_uck_vg/roblox-pyc"
}
}``` | process | roblox pyc has guarddog issues dependency roblox pyc version result issues errors results silent process execution location roblox pyc src robloxpy py code subprocess call stdout subprocess devnull stderr subprocess devnull stdin subprocess devnull message this package is silently executing an external binary redirecting stdout stderr and stdin to dev null location roblox pyc src robloxpy py code subprocess call stdout subprocess devnull stderr subprocess devnull stdin subprocess devnull message this package is silently executing an external binary redirecting stdout stderr and stdin to dev null path tmp tmpz uck vg roblox pyc | 1 |
45,403 | 12,793,792,240 | IssuesEvent | 2020-07-02 05:10:51 | fieldenms/tg | https://api.github.com/repos/fieldenms/tg | closed | Missing adjustment for JS API method for editor value promotion | Actions Defect Entity master Property editor Pull request Regression Selection criteria | ### Description
Method `setEditorValue4PropertyFromConcreteValue` has not been adjusted during #1044 issue implementation. This has been slipped through a crack when multitude of API changes were provisioned and corresponding platform / application code adjusted. Web tests are required to employ early check of its functioning.
*Implementation details*: what was changed in #1044?
```
convert => tg_toString or tg_convert
convertPropertyValue => tg_convertPropertyValue
convertOriginalPropertyValue => tg_convertOriginalPropertyValue
formatDecimal => tg_formatDecimal
formatNumber => tg_formatInteger
formatMoney => tg_formatMoney
_getValueFor => tg_getFullValue
getBindingValue => tg_getBindingValue
getPropertyValue => tg_getBindingValueFromFullEntity
generateShortCollection (REMOVED)
_convertFullPropertyValue (REMOVED)
```
### Expected outcome
Working API for changing editor's value and committing it through custom post-actions.
### Actual outcome
API for changing+committing editor's value does not work and produce `Cannot read property 'bind' of undefined` client-side error leaving action in uncompleted state. | 1.0 | Missing adjustment for JS API method for editor value promotion - ### Description
Method `setEditorValue4PropertyFromConcreteValue` has not been adjusted during #1044 issue implementation. This has been slipped through a crack when multitude of API changes were provisioned and corresponding platform / application code adjusted. Web tests are required to employ early check of its functioning.
*Implementation details*: what was changed in #1044?
```
convert => tg_toString or tg_convert
convertPropertyValue => tg_convertPropertyValue
convertOriginalPropertyValue => tg_convertOriginalPropertyValue
formatDecimal => tg_formatDecimal
formatNumber => tg_formatInteger
formatMoney => tg_formatMoney
_getValueFor => tg_getFullValue
getBindingValue => tg_getBindingValue
getPropertyValue => tg_getBindingValueFromFullEntity
generateShortCollection (REMOVED)
_convertFullPropertyValue (REMOVED)
```
### Expected outcome
Working API for changing editor's value and committing it through custom post-actions.
### Actual outcome
API for changing+committing editor's value does not work and produce `Cannot read property 'bind' of undefined` client-side error leaving action in uncompleted state. | non_process | missing adjustment for js api method for editor value promotion description method has not been adjusted during issue implementation this has been slipped through a crack when multitude of api changes were provisioned and corresponding platform application code adjusted web tests are required to employ early check of its functioning implementation details what was changed in convert tg tostring or tg convert convertpropertyvalue tg convertpropertyvalue convertoriginalpropertyvalue tg convertoriginalpropertyvalue formatdecimal tg formatdecimal formatnumber tg formatinteger formatmoney tg formatmoney getvaluefor tg getfullvalue getbindingvalue tg getbindingvalue getpropertyvalue tg getbindingvaluefromfullentity generateshortcollection removed convertfullpropertyvalue removed expected outcome working api for changing editor s value and committing it through custom post actions actual outcome api for changing committing editor s value does not work and produce cannot read property bind of undefined client side error leaving action in uncompleted state | 0 |
227,172 | 17,376,126,933 | IssuesEvent | 2021-07-30 21:36:21 | Carmoruda/JetBrains-Academy-Projects | https://api.github.com/repos/Carmoruda/JetBrains-Academy-Projects | closed | README | documentation | - [x] Change the type of headline from the difficulty of the projects in the README document (Python Developer).
- [x] Append the link to the document with the stage 1 code (Coffee Machine) | 1.0 | README - - [x] Change the type of headline from the difficulty of the projects in the README document (Python Developer).
- [x] Append the link to the document with the stage 1 code (Coffee Machine) | non_process | readme change the type of headline from the difficulty of the projects in the readme document python developer append the link to the document with the stage code coffee machine | 0 |
217,473 | 16,718,088,968 | IssuesEvent | 2021-06-10 01:31:42 | streamnative/pulsar | https://api.github.com/repos/streamnative/pulsar | closed | ISSUE-10237: [Doc + Website] generate 2.8.0-SNAPSHOT for various API docs | component/documentation component/website | Original Issue: apache/pulsar#10237
---
[All API docs](https://pulsar.apache.org/api/) should be automatically generated after each release.
However, the following API docs do not have 2.8.0-SNAPSHOT currently.
- [Java admin API](https://github.com/apache/pulsar/tree/asf-site/content/api/admin)
- [pulsar-broker](https://github.com/apache/pulsar/tree/asf-site/content/api/pulsar-broker)
- [pulsar-functions](https://github.com/apache/pulsar/tree/asf-site/content/api/pulsar-functions)
Besides, the [Pulsar Website build](https://github.com/apache/pulsar/actions/workflows/ci-pulsar-website-build.yaml) always fails in recent days.
@tuteng thinks there are some bugs in this [script](https://github.com/apache/pulsar/blob/master/site2/tools/javadoc-gen.sh). He will look into this issue and solve the problem.
After https://pulsar.apache.org/api/admin/2.8.0-SNAPSHOT/ is generated, I'll check the [commands that should be shown on https://pulsar.apache.org/api/admin/2.8.0-SNAPSHOT/](https://docs.google.com/spreadsheets/d/1GYi9O4bwL-7spFiBcXJ82wB4QSwlCDkSubDUDSBDLjI/edit#gid=0). | 1.0 | ISSUE-10237: [Doc + Website] generate 2.8.0-SNAPSHOT for various API docs - Original Issue: apache/pulsar#10237
---
[All API docs](https://pulsar.apache.org/api/) should be automatically generated after each release.
However, the following API docs do not have 2.8.0-SNAPSHOT currently.
- [Java admin API](https://github.com/apache/pulsar/tree/asf-site/content/api/admin)
- [pulsar-broker](https://github.com/apache/pulsar/tree/asf-site/content/api/pulsar-broker)
- [pulsar-functions](https://github.com/apache/pulsar/tree/asf-site/content/api/pulsar-functions)
Besides, the [Pulsar Website build](https://github.com/apache/pulsar/actions/workflows/ci-pulsar-website-build.yaml) always fails in recent days.
@tuteng thinks there are some bugs in this [script](https://github.com/apache/pulsar/blob/master/site2/tools/javadoc-gen.sh). He will look into this issue and solve the problem.
After https://pulsar.apache.org/api/admin/2.8.0-SNAPSHOT/ is generated, I'll check the [commands that should be shown on https://pulsar.apache.org/api/admin/2.8.0-SNAPSHOT/](https://docs.google.com/spreadsheets/d/1GYi9O4bwL-7spFiBcXJ82wB4QSwlCDkSubDUDSBDLjI/edit#gid=0). | non_process | issue generate snapshot for various api docs original issue apache pulsar should be automatically generated after each release however the following api docs do not have snapshot currently besides the always fails in recent days tuteng thinks there are some bugs in this he will look into this issue and solve the problem after is generated i ll check the | 0 |
715,828 | 24,611,452,260 | IssuesEvent | 2022-10-14 22:05:10 | phylum-dev/cli | https://api.github.com/repos/phylum-dev/cli | closed | Command line argument `--no-check-certificate` is saved to config | bug high priority | # Overview
Setting `--no-check-certificate` on the command line gets saved to the config so that all future runs no longer check certificates. And since we do not have a `--check-certificate` option (see #483), the only way to get phylum to start checking certificates again is to manually modify the config file. This is very similar to #582
# How To Reproduce
```
❯ grep 'ignore_certs' ~/.config/phylum/settings.yaml
ignore_certs: false
❯ phylum --no-check-certificate ping
[2022-09-02T15:12:10Z WARN phylum] Ignoring TLS server certificate verification per user request.
✅ alive!
❯ grep 'ignore_certs' ~/.config/phylum/settings.yaml
ignore_certs: true
```
# Expected Behavior
Config from command line arguments or environment variables should never be written out to the config file. | 1.0 | Command line argument `--no-check-certificate` is saved to config - # Overview
Setting `--no-check-certificate` on the command line gets saved to the config so that all future runs no longer check certificates. And since we do not have a `--check-certificate` option (see #483), the only way to get phylum to start checking certificates again is to manually modify the config file. This is very similar to #582
# How To Reproduce
```
❯ grep 'ignore_certs' ~/.config/phylum/settings.yaml
ignore_certs: false
❯ phylum --no-check-certificate ping
[2022-09-02T15:12:10Z WARN phylum] Ignoring TLS server certificate verification per user request.
✅ alive!
❯ grep 'ignore_certs' ~/.config/phylum/settings.yaml
ignore_certs: true
```
# Expected Behavior
Config from command line arguments or environment variables should never be written out to the config file. | non_process | command line argument no check certificate is saved to config overview setting no check certificate on the command line gets saved to the config so that all future runs no longer check certificates and since we do not have a check certificate option see the only way to get phylum to start checking certificates again is to manually modify the config file this is very similar to how to reproduce ❯ grep ignore certs config phylum settings yaml ignore certs false ❯ phylum no check certificate ping ignoring tls server certificate verification per user request ✅ alive ❯ grep ignore certs config phylum settings yaml ignore certs true expected behavior config from command line arguments or environment variables should never be written out to the config file | 0 |
808 | 3,286,527,006 | IssuesEvent | 2015-10-29 03:25:59 | t3kt/vjzual2 | https://api.github.com/repos/t3kt/vjzual2 | closed | create sub-modules within the feedback module | enhancement video processing | it's basically just a shell that wraps a chain of effects | 1.0 | create sub-modules within the feedback module - it's basically just a shell that wraps a chain of effects | process | create sub modules within the feedback module it s basically just a shell that wraps a chain of effects | 1 |
276,276 | 20,976,956,388 | IssuesEvent | 2022-03-28 16:01:47 | devonfw-forge/devon4flutter | https://api.github.com/repos/devonfw-forge/devon4flutter | closed | Introduction to Flutter | documentation Campus_21_4_flutter | **Description**
Give a small introduction to Flutter.
**Acceptance Criteria**
- What you can do with Flutter
- What operating systems Flutter Applications run on
- How to get started in the installation
- What are the key points that one needs to know before developing
**Developer Hints**
- [Flutter](https://flutter.dev/)
- [Flutter install](https://docs.flutter.dev/get-started/install)
- [Flutter youtube tutorials](https://www.youtube.com/c/flutterdev)
- [Flutter Apprentice](https://www.raywenderlich.com/books/flutter-apprentice)
- [Java Documentation: Guide to the reader](https://docs.oracle.com/javase/7/docs/api/java/io/Reader.html) | 1.0 | Introduction to Flutter - **Description**
Give a small introduction to Flutter.
**Acceptance Criteria**
- What you can do with Flutter
- What operating systems Flutter Applications run on
- How to get started in the installation
- What are the key points that one needs to know before developing
**Developer Hints**
- [Flutter](https://flutter.dev/)
- [Flutter install](https://docs.flutter.dev/get-started/install)
- [Flutter youtube tutorials](https://www.youtube.com/c/flutterdev)
- [Flutter Apprentice](https://www.raywenderlich.com/books/flutter-apprentice)
- [Java Documentation: Guide to the reader](https://docs.oracle.com/javase/7/docs/api/java/io/Reader.html) | non_process | introduction to flutter description give a small introduction to flutter acceptance criteria what you can do with flutter what operating systems flutter applications run on how to get started in the installation what are the key points that one needs to know before developing developer hints | 0 |
182,140 | 6,667,471,594 | IssuesEvent | 2017-10-03 12:43:55 | zero-os/0-Disk | https://api.github.com/repos/zero-os/0-Disk | closed | add `zeroctl describe snapshot` command | priority_minor state_inprogress type_feature | The `zeroctl describe snapshot` command will be used to print out (to the STDOUT) all the information that can be given for a given snapshot, and will thus be heavily related to the import/export vdisk commands.
The output would look something like this:
```javascript
{
snapshotID: "mybackup", // required : ID of the snapshot (vdisk backup)
blockSize: 4096, // required: block size of the snapshot in bytes
size: 32768, // required: size of the snapshot in bytes (computed in runtime)
created: "2006-01-02T15:04:05Z07:00", // optional: creation (RFC3339) data, time and timezone
source: { // optional: info about the source vdisk
vdiskID: "foo", // optional: ID of the source vdisk
blockSize: 32768, // optional: block size of the source vdisk in bytes
size: 32768, // optional: block size of the source vdisk in bytes
},
}
```
This issue is part of issue #509. | 1.0 | add `zeroctl describe snapshot` command - The `zeroctl describe snapshot` command will be used to print out (to the STDOUT) all the information that can be given for a given snapshot, and will thus be heavily related to the import/export vdisk commands.
The output would look something like this:
```javascript
{
snapshotID: "mybackup", // required : ID of the snapshot (vdisk backup)
blockSize: 4096, // required: block size of the snapshot in bytes
size: 32768, // required: size of the snapshot in bytes (computed in runtime)
created: "2006-01-02T15:04:05Z07:00", // optional: creation (RFC3339) data, time and timezone
source: { // optional: info about the source vdisk
vdiskID: "foo", // optional: ID of the source vdisk
blockSize: 32768, // optional: block size of the source vdisk in bytes
size: 32768, // optional: block size of the source vdisk in bytes
},
}
```
This issue is part of issue #509. | non_process | add zeroctl describe snapshot command the zeroctl describe snapshot command will be used to print out to the stdout all the information that can be given for a given snapshot and will thus be heavily related to the import export vdisk commands the output would look something like this javascript snapshotid mybackup required id of the snapshot vdisk backup blocksize required block size of the snapshot in bytes size required size of the snapshot in bytes computed in runtime created optional creation data time and timezone source optional info about the source vdisk vdiskid foo optional id of the source vdisk blocksize optional block size of the source vdisk in bytes size optional block size of the source vdisk in bytes this issue is part of issue | 0 |
14,986 | 18,524,085,890 | IssuesEvent | 2021-10-20 18:13:54 | googleapis/python-bigtable | https://api.github.com/repos/googleapis/python-bigtable | closed | 'tableadmin_test.test_run_table_operations' sample fails with 503 UNAVAILABLE | api: bigtable type: process samples | From these failed Kokoro builds:
- https://source.cloud.google.com/results/invocations/5981cd7b-ad3b-47e6-81f4-4170b8e6a265/targets/github%2Fpython-bigtable%2Fsamples%2Ftableadmin/tests
- https://source.cloud.google.com/results/invocations/a5e95556-50cf-456e-952c-2ce0d1857586/targets/github%2Fpython-bigtable%2Fsamples%2Ftableadmin/tests
```python
Failed: google.api_core.exceptions.ServiceUnavailable: 503 The service is currently unavailable.
args = (name: "projects/python-docs-samples-tests/instances/bigtable-test/tables/tableadmin-test-7ab1db71"
modifications {
id: "cf2"
drop: true
}
,)
kwargs = {'metadata': [('x-goog-request-params', 'name=projects/python-docs-samples-tests/instances/bigtable-test/tables/tableadmin-test-7ab1db71'), ('x-goog-api-client', 'gl-python/3.6.13 grpc/1.39.0 gax/1.31.2')]}
@six.wraps(callable_)
def error_remapped_callable(*args, **kwargs):
try:
> return callable_(*args, **kwargs)
.nox/py-3-6/lib/python3.6/site-packages/google/api_core/grpc_helpers.py:67:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <grpc._channel._UnaryUnaryMultiCallable object at 0x7f73806a5160>
request = name: "projects/python-docs-samples-tests/instances/bigtable-test/tables/tableadmin-test-7ab1db71"
modifications {
id: "cf2"
drop: true
}
timeout = None
metadata = [('x-goog-request-params', 'name=projects/python-docs-samples-tests/instances/bigtable-test/tables/tableadmin-test-7ab1db71'), ('x-goog-api-client', 'gl-python/3.6.13 grpc/1.39.0 gax/1.31.2')]
credentials = None, wait_for_ready = None, compression = None
def __call__(self,
request,
timeout=None,
metadata=None,
credentials=None,
wait_for_ready=None,
compression=None):
state, call, = self._blocking(request, timeout, metadata, credentials,
wait_for_ready, compression)
> return _end_unary_response_blocking(state, call, False, None)
.nox/py-3-6/lib/python3.6/site-packages/grpc/_channel.py:946:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
state = <grpc._channel._RPCState object at 0x7f73806755f8>
call = <grpc._cython.cygrpc.SegregatedCall object at 0x7f737e5cb608>
with_call = False, deadline = None
def _end_unary_response_blocking(state, call, with_call, deadline):
if state.code is grpc.StatusCode.OK:
if with_call:
rendezvous = _MultiThreadedRendezvous(state, call, None, deadline)
return state.response, rendezvous
else:
return state.response
else:
> raise _InactiveRpcError(state)
E grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
E status = StatusCode.UNAVAILABLE
E details = "The service is currently unavailable."
E debug_error_string = "{"created":"@1630441021.581603795","description":"Error received from peer ipv4:173.194.202.95:443","file":"src/core/lib/surface/call.cc","file_line":1069,"grpc_message":"The service is currently unavailable.","grpc_status":14}"
E >
.nox/py-3-6/lib/python3.6/site-packages/grpc/_channel.py:849: _InactiveRpcError
The above exception was the direct cause of the following exception:
capsys = <_pytest.capture.CaptureFixture object at 0x7f7380720cc0>
def test_run_table_operations(capsys):
table_id = TABLE_ID_FORMAT.format(uuid.uuid4().hex[:8])
> run_table_operations(PROJECT, BIGTABLE_INSTANCE, table_id)
tableadmin_test.py:31:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
tableadmin.py:216: in run_table_operations
column_family2.delete()
../../google/cloud/bigtable/column_family.py:327: in delete
request={"name": self._table.name, "modifications": [modification]}
../../google/cloud/bigtable_admin_v2/services/bigtable_table_admin/client.py:984: in modify_column_families
response = rpc(request, retry=retry, timeout=timeout, metadata=metadata,)
.nox/py-3-6/lib/python3.6/site-packages/google/api_core/gapic_v1/method.py:145: in __call__
return wrapped_func(*args, **kwargs)
.nox/py-3-6/lib/python3.6/site-packages/google/api_core/grpc_helpers.py:69: in error_remapped_callable
six.raise_from(exceptions.from_grpc_error(exc), exc)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
value = None
from_value = <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = "The service is currently .../core/lib/surface/call.cc","file_line":1069,"grpc_message":"The service is currently unavailable.","grpc_status":14}"
>
> ???
E google.api_core.exceptions.ServiceUnavailable: 503 The service is currently unavailable.
<string>:3: ServiceUnavailable
``` | 1.0 | 'tableadmin_test.test_run_table_operations' sample fails with 503 UNAVAILABLE - From these failed Kokoro builds:
- https://source.cloud.google.com/results/invocations/5981cd7b-ad3b-47e6-81f4-4170b8e6a265/targets/github%2Fpython-bigtable%2Fsamples%2Ftableadmin/tests
- https://source.cloud.google.com/results/invocations/a5e95556-50cf-456e-952c-2ce0d1857586/targets/github%2Fpython-bigtable%2Fsamples%2Ftableadmin/tests
```python
Failed: google.api_core.exceptions.ServiceUnavailable: 503 The service is currently unavailable.
args = (name: "projects/python-docs-samples-tests/instances/bigtable-test/tables/tableadmin-test-7ab1db71"
modifications {
id: "cf2"
drop: true
}
,)
kwargs = {'metadata': [('x-goog-request-params', 'name=projects/python-docs-samples-tests/instances/bigtable-test/tables/tableadmin-test-7ab1db71'), ('x-goog-api-client', 'gl-python/3.6.13 grpc/1.39.0 gax/1.31.2')]}
@six.wraps(callable_)
def error_remapped_callable(*args, **kwargs):
try:
> return callable_(*args, **kwargs)
.nox/py-3-6/lib/python3.6/site-packages/google/api_core/grpc_helpers.py:67:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <grpc._channel._UnaryUnaryMultiCallable object at 0x7f73806a5160>
request = name: "projects/python-docs-samples-tests/instances/bigtable-test/tables/tableadmin-test-7ab1db71"
modifications {
id: "cf2"
drop: true
}
timeout = None
metadata = [('x-goog-request-params', 'name=projects/python-docs-samples-tests/instances/bigtable-test/tables/tableadmin-test-7ab1db71'), ('x-goog-api-client', 'gl-python/3.6.13 grpc/1.39.0 gax/1.31.2')]
credentials = None, wait_for_ready = None, compression = None
def __call__(self,
request,
timeout=None,
metadata=None,
credentials=None,
wait_for_ready=None,
compression=None):
state, call, = self._blocking(request, timeout, metadata, credentials,
wait_for_ready, compression)
> return _end_unary_response_blocking(state, call, False, None)
.nox/py-3-6/lib/python3.6/site-packages/grpc/_channel.py:946:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
state = <grpc._channel._RPCState object at 0x7f73806755f8>
call = <grpc._cython.cygrpc.SegregatedCall object at 0x7f737e5cb608>
with_call = False, deadline = None
def _end_unary_response_blocking(state, call, with_call, deadline):
if state.code is grpc.StatusCode.OK:
if with_call:
rendezvous = _MultiThreadedRendezvous(state, call, None, deadline)
return state.response, rendezvous
else:
return state.response
else:
> raise _InactiveRpcError(state)
E grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
E status = StatusCode.UNAVAILABLE
E details = "The service is currently unavailable."
E debug_error_string = "{"created":"@1630441021.581603795","description":"Error received from peer ipv4:173.194.202.95:443","file":"src/core/lib/surface/call.cc","file_line":1069,"grpc_message":"The service is currently unavailable.","grpc_status":14}"
E >
.nox/py-3-6/lib/python3.6/site-packages/grpc/_channel.py:849: _InactiveRpcError
The above exception was the direct cause of the following exception:
capsys = <_pytest.capture.CaptureFixture object at 0x7f7380720cc0>
def test_run_table_operations(capsys):
table_id = TABLE_ID_FORMAT.format(uuid.uuid4().hex[:8])
> run_table_operations(PROJECT, BIGTABLE_INSTANCE, table_id)
tableadmin_test.py:31:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
tableadmin.py:216: in run_table_operations
column_family2.delete()
../../google/cloud/bigtable/column_family.py:327: in delete
request={"name": self._table.name, "modifications": [modification]}
../../google/cloud/bigtable_admin_v2/services/bigtable_table_admin/client.py:984: in modify_column_families
response = rpc(request, retry=retry, timeout=timeout, metadata=metadata,)
.nox/py-3-6/lib/python3.6/site-packages/google/api_core/gapic_v1/method.py:145: in __call__
return wrapped_func(*args, **kwargs)
.nox/py-3-6/lib/python3.6/site-packages/google/api_core/grpc_helpers.py:69: in error_remapped_callable
six.raise_from(exceptions.from_grpc_error(exc), exc)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
value = None
from_value = <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = "The service is currently .../core/lib/surface/call.cc","file_line":1069,"grpc_message":"The service is currently unavailable.","grpc_status":14}"
>
> ???
E google.api_core.exceptions.ServiceUnavailable: 503 The service is currently unavailable.
<string>:3: ServiceUnavailable
``` | process | tableadmin test test run table operations sample fails with unavailable from these failed kokoro builds python failed google api core exceptions serviceunavailable the service is currently unavailable args name projects python docs samples tests instances bigtable test tables tableadmin test modifications id drop true kwargs metadata six wraps callable def error remapped callable args kwargs try return callable args kwargs nox py lib site packages google api core grpc helpers py self request name projects python docs samples tests instances bigtable test tables tableadmin test modifications id drop true timeout none metadata credentials none wait for ready none compression none def call self request timeout none metadata none credentials none wait for ready none compression none state call self blocking request timeout metadata credentials wait for ready compression return end unary response blocking state call false none nox py lib site packages grpc channel py state call with call false deadline none def end unary response blocking state call with call deadline if state code is grpc statuscode ok if with call rendezvous multithreadedrendezvous state call none deadline return state response rendezvous else return state response else raise inactiverpcerror state e grpc channel inactiverpcerror inactiverpcerror of rpc that terminated with e status statuscode unavailable e details the service is currently unavailable e debug error string created description error received from peer file src core lib surface call cc file line grpc message the service is currently unavailable grpc status e nox py lib site packages grpc channel py inactiverpcerror the above exception was the direct cause of the following exception capsys def test run table operations capsys table id table id format format uuid hex run table operations project bigtable instance table id tableadmin test py tableadmin py in run table operations column delete google cloud bigtable column family py in delete request name self table name modifications google cloud bigtable admin services bigtable table admin client py in modify column families response rpc request retry retry timeout timeout metadata metadata nox py lib site packages google api core gapic method py in call return wrapped func args kwargs nox py lib site packages google api core grpc helpers py in error remapped callable six raise from exceptions from grpc error exc exc value none from value inactiverpcerror of rpc that terminated with status statuscode unavailable details the service is currently core lib surface call cc file line grpc message the service is currently unavailable grpc status e google api core exceptions serviceunavailable the service is currently unavailable serviceunavailable | 1 |
21,423 | 29,359,592,568 | IssuesEvent | 2023-05-28 00:37:01 | devssa/onde-codar-em-salvador | https://api.github.com/repos/devssa/onde-codar-em-salvador | closed | [Hibrido / Belo Horizonte/MG] Backend Developer C# na Coodesh | SALVADOR BACK-END BANCO DE DADOS CSS3 MVC PLENO SQL GIT BOOTSTRAP WEB API ENTITY FRAMEWORK REQUISITOS ASP.NET PROCESSOS BACKEND GITHUB UMA C QUALIDADE METODOLOGIAS ÁGEIS MANUTENÇÃO ALOCADO Stale | ## Descrição da vaga:
Esta é uma vaga de um parceiro da plataforma Coodesh, ao candidatar-se você terá acesso as informações completas sobre a empresa e benefícios.
Fique atento ao redirecionamento que vai te levar para uma url [https://coodesh.com](https://coodesh.com/vagas/desenvolvedor-c-104634397?utm_source=github&utm_medium=devssa-onde-codar-em-salvador&modal=open) com o pop-up personalizado de candidatura. 👋
<p>A <strong>Revelar RH</strong> está em busca de <strong><ins>Backend Developer C#</ins></strong> para compor seu time!</p>
<p>Sediada em Belo Horizonte, criada em 2010, é uma Software House voltada para projetos especiais na área de Tecnologia da Informação.</p>
<p><strong>Responsabilidades:</strong></p>
<ul>
<li>Desenvolvimento e acompanhamento de manutenção evolutivas e corretivas em sistemas desenvolvidos em .NET;</li>
<li>Propor soluções e desenvolver novas tecnologias para melhoria dos sistemas;</li>
<li>Manter a qualidade do código, versionamento, testes, deploy e participação na priorização de funcionalidades.</li>
</ul>
## Revelar RH:
<p>A Revelar RH é uma empresa inovadora que busca alinhar os objetivos das Empresas que têm carência de profissionais qualificados, com os das pessoas que estão em busca de uma oportunidades no mercado de trabalho. Nosso trabalho visa o aprimoramento e racionalização de processos voltados à Gestão de Pessoas, sendo realizado de forma personalizada para cada cliente. Atualmente atendemos várias empresas de tecnologia e softwares house. </p>
</p>
## Habilidades:
- C#
- Asp.Net MVC
- CSS 3
## Local:
Belo Horizonte/MG
## Requisitos:
- Superior completo ou em curso de Análise e Desenvolvimento de Sistemas, Engenharia da computação ou áreas afins;
- Experiência e conhecimento correspondente ao perfil pleno/sênior;
- Banco de dados: SQL SERVER;
- Ferramenta de controle de Versão: GIT;
- Ser habituado com metodologias ágeis;
- Experiência com C#, ASP.NET MVC, Entity framework;
- Experiência com HTML5, CSS3, Bootstrap, WEB API.
## Benefícios:
- Plano de saúde;
- Plano odontológico;
- Seguro de vida;
- Cartão de benefícios Swile (alimentação, auxílio internet, desconto em academia).
## Como se candidatar:
Candidatar-se exclusivamente através da plataforma Coodesh no link a seguir: [Backend Developer C# na Revelar RH](https://coodesh.com/vagas/desenvolvedor-c-104634397?utm_source=github&utm_medium=devssa-onde-codar-em-salvador&modal=open)
Após candidatar-se via plataforma Coodesh e validar o seu login, você poderá acompanhar e receber todas as interações do processo por lá. Utilize a opção **Pedir Feedback** entre uma etapa e outra na vaga que se candidatou. Isso fará com que a pessoa **Recruiter** responsável pelo processo na empresa receba a notificação.
## Labels
#### Alocação
Alocado
#### Categoria
Back-End | 1.0 | [Hibrido / Belo Horizonte/MG] Backend Developer C# na Coodesh - ## Descrição da vaga:
Esta é uma vaga de um parceiro da plataforma Coodesh, ao candidatar-se você terá acesso as informações completas sobre a empresa e benefícios.
Fique atento ao redirecionamento que vai te levar para uma url [https://coodesh.com](https://coodesh.com/vagas/desenvolvedor-c-104634397?utm_source=github&utm_medium=devssa-onde-codar-em-salvador&modal=open) com o pop-up personalizado de candidatura. 👋
<p>A <strong>Revelar RH</strong> está em busca de <strong><ins>Backend Developer C#</ins></strong> para compor seu time!</p>
<p>Sediada em Belo Horizonte, criada em 2010, é uma Software House voltada para projetos especiais na área de Tecnologia da Informação.</p>
<p><strong>Responsabilidades:</strong></p>
<ul>
<li>Desenvolvimento e acompanhamento de manutenção evolutivas e corretivas em sistemas desenvolvidos em .NET;</li>
<li>Propor soluções e desenvolver novas tecnologias para melhoria dos sistemas;</li>
<li>Manter a qualidade do código, versionamento, testes, deploy e participação na priorização de funcionalidades.</li>
</ul>
## Revelar RH:
<p>A Revelar RH é uma empresa inovadora que busca alinhar os objetivos das Empresas que têm carência de profissionais qualificados, com os das pessoas que estão em busca de uma oportunidades no mercado de trabalho. Nosso trabalho visa o aprimoramento e racionalização de processos voltados à Gestão de Pessoas, sendo realizado de forma personalizada para cada cliente. Atualmente atendemos várias empresas de tecnologia e softwares house. </p>
</p>
## Habilidades:
- C#
- Asp.Net MVC
- CSS 3
## Local:
Belo Horizonte/MG
## Requisitos:
- Superior completo ou em curso de Análise e Desenvolvimento de Sistemas, Engenharia da computação ou áreas afins;
- Experiência e conhecimento correspondente ao perfil pleno/sênior;
- Banco de dados: SQL SERVER;
- Ferramenta de controle de Versão: GIT;
- Ser habituado com metodologias ágeis;
- Experiência com C#, ASP.NET MVC, Entity framework;
- Experiência com HTML5, CSS3, Bootstrap, WEB API.
## Benefícios:
- Plano de saúde;
- Plano odontológico;
- Seguro de vida;
- Cartão de benefícios Swile (alimentação, auxílio internet, desconto em academia).
## Como se candidatar:
Candidatar-se exclusivamente através da plataforma Coodesh no link a seguir: [Backend Developer C# na Revelar RH](https://coodesh.com/vagas/desenvolvedor-c-104634397?utm_source=github&utm_medium=devssa-onde-codar-em-salvador&modal=open)
Após candidatar-se via plataforma Coodesh e validar o seu login, você poderá acompanhar e receber todas as interações do processo por lá. Utilize a opção **Pedir Feedback** entre uma etapa e outra na vaga que se candidatou. Isso fará com que a pessoa **Recruiter** responsável pelo processo na empresa receba a notificação.
## Labels
#### Alocação
Alocado
#### Categoria
Back-End | process | backend developer c na coodesh descrição da vaga esta é uma vaga de um parceiro da plataforma coodesh ao candidatar se você terá acesso as informações completas sobre a empresa e benefícios fique atento ao redirecionamento que vai te levar para uma url com o pop up personalizado de candidatura 👋 a revelar rh está em busca de backend developer c para compor seu time sediada em belo horizonte criada em é uma software house voltada para projetos especiais na área de tecnologia da informação responsabilidades desenvolvimento e acompanhamento de manutenção evolutivas e corretivas em sistemas desenvolvidos em net propor soluções e desenvolver novas tecnologias para melhoria dos sistemas manter a qualidade do código versionamento testes deploy e participação na priorização de funcionalidades revelar rh a revelar rh é uma empresa inovadora que busca alinhar os objetivos das empresas que têm carência de profissionais qualificados com os das pessoas que estão em busca de uma oportunidades no mercado de trabalho nosso trabalho visa o aprimoramento e racionalização de processos voltados à gestão de pessoas sendo realizado de forma personalizada para cada cliente atualmente atendemos várias empresas de tecnologia e softwares house nbsp habilidades c asp net mvc css local belo horizonte mg requisitos superior completo ou em curso de análise e desenvolvimento de sistemas engenharia da computação ou áreas afins experiência e conhecimento correspondente ao perfil pleno sênior banco de dados sql server ferramenta de controle de versão git ser habituado com metodologias ágeis experiência com c asp net mvc entity framework experiência com bootstrap web api benefícios plano de saúde plano odontológico seguro de vida cartão de benefícios swile alimentação auxílio internet desconto em academia como se candidatar candidatar se exclusivamente através da plataforma coodesh no link a seguir após candidatar se via plataforma coodesh e validar o seu login você poderá acompanhar e receber todas as interações do processo por lá utilize a opção pedir feedback entre uma etapa e outra na vaga que se candidatou isso fará com que a pessoa recruiter responsável pelo processo na empresa receba a notificação labels alocação alocado categoria back end | 1 |
20,654 | 27,329,653,531 | IssuesEvent | 2023-02-25 13:07:44 | cse442-at-ub/project_s23-cinco | https://api.github.com/repos/cse442-at-ub/project_s23-cinco | closed | Create a guide showing how to download PHP as well as methods to connect to UB servers | Processing Task Sprint 1 | Test
1. Go to
https://docs.google.com/document/d/1s0OLPXXsEa-N_cE0BFlYoYBbPwZfH25x2ZHevvdn5jg/edit
2. Confirm that you can view the document
3. Look through the information and verify you are able to follow the instructions and download PHP as well as access UB servers | 1.0 | Create a guide showing how to download PHP as well as methods to connect to UB servers - Test
1. Go to
https://docs.google.com/document/d/1s0OLPXXsEa-N_cE0BFlYoYBbPwZfH25x2ZHevvdn5jg/edit
2. Confirm that you can view the document
3. Look through the information and verify you are able to follow the instructions and download PHP as well as access UB servers | process | create a guide showing how to download php as well as methods to connect to ub servers test go to confirm that you can view the document look through the information and verify you are able to follow the instructions and download php as well as access ub servers | 1 |
55,447 | 11,431,441,403 | IssuesEvent | 2020-02-04 12:09:28 | Regalis11/Barotrauma | https://api.github.com/repos/Regalis11/Barotrauma | closed | [0.9.702] Campaign Shop Filter does not work correctly | Bug Code | - [x] I have searched the issue tracker to check if the issue has already been reported.
**Description**
When typing items into the filter, it does not refresh the list of items to match the filter. Once you actually purchase something random, or another player with manage campaign does, the list then refreshes with the filter.
**Version**
0.9.702
| 1.0 | [0.9.702] Campaign Shop Filter does not work correctly - - [x] I have searched the issue tracker to check if the issue has already been reported.
**Description**
When typing items into the filter, it does not refresh the list of items to match the filter. Once you actually purchase something random, or another player with manage campaign does, the list then refreshes with the filter.
**Version**
0.9.702
| non_process | campaign shop filter does not work correctly i have searched the issue tracker to check if the issue has already been reported description when typing items into the filter it does not refresh the list of items to match the filter once you actually purchase something random or another player with manage campaign does the list then refreshes with the filter version | 0 |
4,141 | 7,097,115,387 | IssuesEvent | 2018-01-14 15:52:54 | bojanrajkovic/Volley | https://api.github.com/repos/bojanrajkovic/Volley | opened | Generate manifest file for homepage to pull artifacts from | Release Process | The manifest should include the artifact URL, a hash, and either a link to a detached signature or an indication that the artifact is "signed" internally (for RPM/DEB artifacts). | 1.0 | Generate manifest file for homepage to pull artifacts from - The manifest should include the artifact URL, a hash, and either a link to a detached signature or an indication that the artifact is "signed" internally (for RPM/DEB artifacts). | process | generate manifest file for homepage to pull artifacts from the manifest should include the artifact url a hash and either a link to a detached signature or an indication that the artifact is signed internally for rpm deb artifacts | 1 |
76,652 | 9,959,803,284 | IssuesEvent | 2019-07-06 10:32:06 | SpankChain/community | https://api.github.com/repos/SpankChain/community | opened | OBS Documentation | documentation enhancement good first issue help wanted | You can now use OBS on SPANK.live, but the documentation for it is swirling about the ether.
There should be something on Discord, but we need much more content.
This is a good issue for the community-created content. | 1.0 | OBS Documentation - You can now use OBS on SPANK.live, but the documentation for it is swirling about the ether.
There should be something on Discord, but we need much more content.
This is a good issue for the community-created content. | non_process | obs documentation you can now use obs on spank live but the documentation for it is swirling about the ether there should be something on discord but we need much more content this is a good issue for the community created content | 0 |
103,345 | 4,167,512,078 | IssuesEvent | 2016-06-20 09:48:15 | prometheus/alertmanager | https://api.github.com/repos/prometheus/alertmanager | closed | AM version 0.1.1 just dies without any reason | kind/bug priority/P0 | Guys, this is becoming a major issue.
Even under a very small load the service just stops ...
The only thing visible in the log is the below lines repeating themselves
{"level":"error","msg":"Error on notify: context deadline exceeded","source":"notify.go:152","time":"2016-04-27T10:37:09-04:00"}
{"level":"error","msg":"Notify for 3 alerts failed: context deadline exceeded","source":"dispatch.go:238","time":"2016-04-27T10:37:09-04:00"}
The only way to revive the service is to delete its db and restart it.
What can be done to debug this ?
| 1.0 | AM version 0.1.1 just dies without any reason - Guys, this is becoming a major issue.
Even under a very small load the service just stops ...
The only thing visible in the log is the below lines repeating themselves
{"level":"error","msg":"Error on notify: context deadline exceeded","source":"notify.go:152","time":"2016-04-27T10:37:09-04:00"}
{"level":"error","msg":"Notify for 3 alerts failed: context deadline exceeded","source":"dispatch.go:238","time":"2016-04-27T10:37:09-04:00"}
The only way to revive the service is to delete its db and restart it.
What can be done to debug this ?
| non_process | am version just dies without any reason guys this is becoming a major issue even under a very small load the service just stops the only thing visible in the log is the below lines repeating themselves level error msg error on notify context deadline exceeded source notify go time level error msg notify for alerts failed context deadline exceeded source dispatch go time the only way to revive the service is to delete its db and restart it what can be done to debug this | 0 |
17,702 | 23,580,113,157 | IssuesEvent | 2022-08-23 06:52:50 | streamnative/flink | https://api.github.com/repos/streamnative/flink | closed | [BUG] Pulsar Source StartCursor uses exclusive messageId by default, should change the implementation. | compute/data-processing type/bug | By default when pulsar consumer seek to messageId x, it will consume next messageId from x. Currently the pulsar source implementation assumes it will consume messageId x.
Expected behaviours: imagine there are 10 messages before subscription that is not acknowledged
when user use startCursor#earliest() : consume all 10 messages
when user use startCursor#latest(): consume 0 messages and start from next message
when user use startCursor#fromMessageId(x): e.g. MessageId(0, 1, -1), consumer should consume 9 messages instead of 8.
| 1.0 | [BUG] Pulsar Source StartCursor uses exclusive messageId by default, should change the implementation. - By default when pulsar consumer seek to messageId x, it will consume next messageId from x. Currently the pulsar source implementation assumes it will consume messageId x.
Expected behaviours: imagine there are 10 messages before subscription that is not acknowledged
when user use startCursor#earliest() : consume all 10 messages
when user use startCursor#latest(): consume 0 messages and start from next message
when user use startCursor#fromMessageId(x): e.g. MessageId(0, 1, -1), consumer should consume 9 messages instead of 8.
| process | pulsar source startcursor uses exclusive messageid by default should change the implementation by default when pulsar consumer seek to messageid x it will consume next messageid from x currently the pulsar source implementation assumes it will consume messageid x expected behaviours imagine there are messages before subscription that is not acknowledged when user use startcursor earliest consume all messages when user use startcursor latest consume messages and start from next message when user use startcursor frommessageid x e g messageid consumer should consume messages instead of | 1 |
47,434 | 5,892,492,337 | IssuesEvent | 2017-05-17 19:36:18 | elastic/logstash | https://api.github.com/repos/elastic/logstash | closed | Gradle/Java Tests are not Run as Part of the Unit-Tests? | tests-infra v5.5.0 v6.0.0 | Currently the rake task for the unit tests `test:core` does not execute the Java/Gradle unit-tests.
Also, the Gradle build is not documented in the Readme at all.
Shouldn't we run the Gradle UTs as part of `test:core` automatically (or if there is reasons not to do that at least document them in the Readme)? | 1.0 | Gradle/Java Tests are not Run as Part of the Unit-Tests? - Currently the rake task for the unit tests `test:core` does not execute the Java/Gradle unit-tests.
Also, the Gradle build is not documented in the Readme at all.
Shouldn't we run the Gradle UTs as part of `test:core` automatically (or if there is reasons not to do that at least document them in the Readme)? | non_process | gradle java tests are not run as part of the unit tests currently the rake task for the unit tests test core does not execute the java gradle unit tests also the gradle build is not documented in the readme at all shouldn t we run the gradle uts as part of test core automatically or if there is reasons not to do that at least document them in the readme | 0 |
15,518 | 11,571,503,214 | IssuesEvent | 2020-02-20 21:42:28 | enarx/enarx | https://api.github.com/repos/enarx/enarx | closed | Don't run tests in a container if not necessary | infrastructure | Our current CI setup runs all our tests inside a container, even when such tests don't require it. We should run those tests outside the container to speed things up. | 1.0 | Don't run tests in a container if not necessary - Our current CI setup runs all our tests inside a container, even when such tests don't require it. We should run those tests outside the container to speed things up. | non_process | don t run tests in a container if not necessary our current ci setup runs all our tests inside a container even when such tests don t require it we should run those tests outside the container to speed things up | 0 |
70,827 | 8,582,641,528 | IssuesEvent | 2018-11-13 17:29:00 | code-dot-org/dance-party | https://api.github.com/repos/code-dot-org/dance-party | closed | I can't customize the certificate on /congrats page | by design | I'm not seeing an option to customize / add my name on staging-studio.code/congrats
| 1.0 | I can't customize the certificate on /congrats page - I'm not seeing an option to customize / add my name on staging-studio.code/congrats
| non_process | i can t customize the certificate on congrats page i m not seeing an option to customize add my name on staging studio code congrats | 0 |
105,224 | 22,961,929,722 | IssuesEvent | 2022-07-19 16:03:21 | trezor/trezor-suite | https://api.github.com/repos/trezor/trezor-suite | closed | Fix handling asynchronicity of init process to prevent race conditions | code tor Team Connect | @szymonlesisz have noticed that the init process is no longer synchronous which may (and probably is) causing race conditions on application start.
Main purpose of suiteMiddleware was to control the initialization process correct order until all essential data/prerequisites are initialized:
1. SUITE.INIT (should be first action ever) ->
2. LOAD STORAGE ->
3. LOAD LOCALES ->
4. INIT CONNECT ->
... (for more steps see suiteMiddleware)
5. SUITE.READY -> initialization done, now suite app is ready to do other stuff like render, fetch etc
Currently there are multiple actions that are fired up immediately on first render without respecting that order (see components in suite-web/src/Main.tsx and suite-desktop/src/index.tsx)
Potential race conditions:
1. Autodetect component is accessing the reducer state before LOAD STORAGE action (this one is probably handled by checking state.suite.storageLoaded)
2. Protocol component > saveCoinProtocol action (writing to state) may be called before LOAD STORAGE > STORAGE LOADED
3. Tor component > updateTorStatus action (writing to state) may be called before LOAD STORAGE > STORAGE LOADED
4. DesktopUpdater component actions (fetch, desktopApi, writing to state) are called in parallel to initialization
It probably starts when Tor component was placed above Preloader and then more components followed that pattern
Possibly related to https://github.com/trezor/trezor-suite/issues/3438 (One of the components (updater? tor?) is trying to write to indexeddb in the middle of db migration process) | 1.0 | Fix handling asynchronicity of init process to prevent race conditions - @szymonlesisz have noticed that the init process is no longer synchronous which may (and probably is) causing race conditions on application start.
Main purpose of suiteMiddleware was to control the initialization process correct order until all essential data/prerequisites are initialized:
1. SUITE.INIT (should be first action ever) ->
2. LOAD STORAGE ->
3. LOAD LOCALES ->
4. INIT CONNECT ->
... (for more steps see suiteMiddleware)
5. SUITE.READY -> initialization done, now suite app is ready to do other stuff like render, fetch etc
Currently there are multiple actions that are fired up immediately on first render without respecting that order (see components in suite-web/src/Main.tsx and suite-desktop/src/index.tsx)
Potential race conditions:
1. Autodetect component is accessing the reducer state before LOAD STORAGE action (this one is probably handled by checking state.suite.storageLoaded)
2. Protocol component > saveCoinProtocol action (writing to state) may be called before LOAD STORAGE > STORAGE LOADED
3. Tor component > updateTorStatus action (writing to state) may be called before LOAD STORAGE > STORAGE LOADED
4. DesktopUpdater component actions (fetch, desktopApi, writing to state) are called in parallel to initialization
It probably starts when Tor component was placed above Preloader and then more components followed that pattern
Possibly related to https://github.com/trezor/trezor-suite/issues/3438 (One of the components (updater? tor?) is trying to write to indexeddb in the middle of db migration process) | non_process | fix handling asynchronicity of init process to prevent race conditions szymonlesisz have noticed that the init process is no longer synchronous which may and probably is causing race conditions on application start main purpose of suitemiddleware was to control the initialization process correct order until all essential data prerequisites are initialized suite init should be first action ever load storage load locales init connect for more steps see suitemiddleware suite ready initialization done now suite app is ready to do other stuff like render fetch etc currently there are multiple actions that are fired up immediately on first render without respecting that order see components in suite web src main tsx and suite desktop src index tsx potential race conditions autodetect component is accessing the reducer state before load storage action this one is probably handled by checking state suite storageloaded protocol component savecoinprotocol action writing to state may be called before load storage storage loaded tor component updatetorstatus action writing to state may be called before load storage storage loaded desktopupdater component actions fetch desktopapi writing to state are called in parallel to initialization it probably starts when tor component was placed above preloader and then more components followed that pattern possibly related to one of the components updater tor is trying to write to indexeddb in the middle of db migration process | 0 |
179,290 | 14,700,832,874 | IssuesEvent | 2021-01-04 10:50:30 | GitTools/GitVersion | https://api.github.com/repos/GitTools/GitVersion | opened | [Docs] Documentation references Deprecated version of GitVersionTask | documentation | Page at https://gitversion.net/docs/build-server-support/build-server/azure-devops references installing the GitVersionTask task here : [https://www.nuget.org/packages/GitVersionTask/ ](https://www.nuget.org/packages/GitVersionTask/ )
as well as a deprecated GitVersion Extension here:
[https://marketplace.visualstudio.com/items?itemName=gittools.usegitversion](https://marketplace.visualstudio.com/items?itemName=gittools.usegitversion)
The new versions of the tools don't' seem to work the same when following the existing documentation. | 1.0 | [Docs] Documentation references Deprecated version of GitVersionTask - Page at https://gitversion.net/docs/build-server-support/build-server/azure-devops references installing the GitVersionTask task here : [https://www.nuget.org/packages/GitVersionTask/ ](https://www.nuget.org/packages/GitVersionTask/ )
as well as a deprecated GitVersion Extension here:
[https://marketplace.visualstudio.com/items?itemName=gittools.usegitversion](https://marketplace.visualstudio.com/items?itemName=gittools.usegitversion)
The new versions of the tools don't' seem to work the same when following the existing documentation. | non_process | documentation references deprecated version of gitversiontask page at references installing the gitversiontask task here as well as a deprecated gitversion extension here the new versions of the tools don t seem to work the same when following the existing documentation | 0 |
17,873 | 23,817,262,113 | IssuesEvent | 2022-09-05 08:01:07 | Tencent/tdesign-miniprogram | https://api.github.com/repos/Tencent/tdesign-miniprogram | closed | [tabs] 希望事件能够获取label的名称 | enhancement good first issue in process | ### 这个功能解决了什么问题
现在只是单一的获取选项卡的值，label名称是获取不到的，如果在不用循环出tab panel时候，pannel中的内容是不一样的，所以需要获取更多值会更好一些
### 你建议的方案是什么
增加官方提供的属性的值，或则还能拓展data-x得值 | 1.0 | [tabs] 希望事件能够获取label的名称 - ### 这个功能解决了什么问题
现在只是单一的获取选项卡的值，label名称是获取不到的，如果在不用循环出tab panel时候，pannel中的内容是不一样的，所以需要获取更多值会更好一些
### 你建议的方案是什么
增加官方提供的属性的值，或则还能拓展data-x得值 | process | 希望事件能够获取label的名称 这个功能解决了什么问题 现在只是单一的获取选项卡的值，label名称是获取不到的，如果在不用循环出tab panel时候，pannel中的内容是不一样的，所以需要获取更多值会更好一些 你建议的方案是什么 增加官方提供的属性的值，或则还能拓展data x得值 | 1 |
7,654 | 10,739,753,181 | IssuesEvent | 2019-10-29 16:54:36 | openopps/openopps-platform | https://api.github.com/repos/openopps/openopps-platform | closed | Student apply process: Work experience should display newest to oldest | Apply Process Approved Requirements Ready State Dept. | Who: applicants
What: reviewing their work experience should display newest to oldest
Why: to be in line with the resume and USAJOBS
Acceptance Criteria:
Student application - work experience page: When a student applies, the work experience on the experience page should display newest to oldest like USAJOBS
| 1.0 | Student apply process: Work experience should display newest to oldest - Who: applicants
What: reviewing their work experience should display newest to oldest
Why: to be in line with the resume and USAJOBS
Acceptance Criteria:
Student application - work experience page: When a student applies, the work experience on the experience page should display newest to oldest like USAJOBS
| process | student apply process work experience should display newest to oldest who applicants what reviewing their work experience should display newest to oldest why to be in line with the resume and usajobs acceptance criteria student application work experience page when a student applies the work experience on the experience page should display newest to oldest like usajobs | 1 |
8,353 | 11,502,845,822 | IssuesEvent | 2020-02-12 19:53:40 | googleapis/python-storage | https://api.github.com/repos/googleapis/python-storage | opened | Add support for shared conformance tests | api: storage testing type: process | We need to add a test suite which exercises the cross-language tests in https://github.com/googleapis/conformance-tests/blob/master/storage/v1/proto/google/cloud/conformance/storage/v1/tests.proto, and fix anything where we don't pass.
/cc @frankyn | 1.0 | Add support for shared conformance tests - We need to add a test suite which exercises the cross-language tests in https://github.com/googleapis/conformance-tests/blob/master/storage/v1/proto/google/cloud/conformance/storage/v1/tests.proto, and fix anything where we don't pass.
/cc @frankyn | process | add support for shared conformance tests we need to add a test suite which exercises the cross language tests in and fix anything where we don t pass cc frankyn | 1 |
292,712 | 25,231,479,607 | IssuesEvent | 2022-11-14 20:13:31 | enioka-Haute-Couture/pyoupyou | https://api.github.com/repos/enioka-Haute-Couture/pyoupyou | closed | Create view test case | test | Ensure we test:
- home
- process creation
- process details
- interview minute (ro and w)
| 1.0 | Create view test case - Ensure we test:
- home
- process creation
- process details
- interview minute (ro and w)
| non_process | create view test case ensure we test home process creation process details interview minute ro and w | 0 |
22,521 | 31,567,883,266 | IssuesEvent | 2023-09-04 01:26:04 | tdwg/hc | https://api.github.com/repos/tdwg/hc | opened | New Term - targetHabitatScope | Term - add normative Process - under public review Class - Event | ## New term
* Submitter: Humboldt Extension Task Group
* Efficacy Justification (why is this term necessary?): Part of a package of terms in support of biological inventory data.
* Demand Justification (name at least two organizations that independently need this term): The Humboldt Extension Task Group proposing this term consists of numerous organizations.
* Stability Justification (what concerns are there that this might affect existing implementations?): None
* Implications for dwciri: namespace (does this change affect a dwciri term version)?: Needs ecoiri: equivalent.
Proposed attributes of the new term:
* Term name (in lowerCamelCase for properties, UpperCamelCase for classes): targetHabitatScope
* Term label (English, not normative): Target Habitat Scope
* Organized in Class (e.g., Occurrence, Event, Location, Taxon): Event
* Definition of the term (normative): The habitats targeted for sampling during the dwc:Event.
* Usage comments (recommendations regarding content, etc., not normative): Recommended best practice is to use a controlled vocabulary and separate the values in a list with space vertical bar space ( | ).
* Examples (not normative): `dunes`; `pine forest`; `riparian`; `scrub | grassland`
* Refines (identifier of the broader term this term refines; normative): None
* Replaces (identifier of the existing term that would be deprecated and replaced by this term; normative): None
* ABCD 2.06 (XPATH of the equivalent term in ABCD or EFG; not normative): not in ABCD
| 1.0 | New Term - targetHabitatScope - ## New term
* Submitter: Humboldt Extension Task Group
* Efficacy Justification (why is this term necessary?): Part of a package of terms in support of biological inventory data.
* Demand Justification (name at least two organizations that independently need this term): The Humboldt Extension Task Group proposing this term consists of numerous organizations.
* Stability Justification (what concerns are there that this might affect existing implementations?): None
* Implications for dwciri: namespace (does this change affect a dwciri term version)?: Needs ecoiri: equivalent.
Proposed attributes of the new term:
* Term name (in lowerCamelCase for properties, UpperCamelCase for classes): targetHabitatScope
* Term label (English, not normative): Target Habitat Scope
* Organized in Class (e.g., Occurrence, Event, Location, Taxon): Event
* Definition of the term (normative): The habitats targeted for sampling during the dwc:Event.
* Usage comments (recommendations regarding content, etc., not normative): Recommended best practice is to use a controlled vocabulary and separate the values in a list with space vertical bar space ( | ).
* Examples (not normative): `dunes`; `pine forest`; `riparian`; `scrub | grassland`
* Refines (identifier of the broader term this term refines; normative): None
* Replaces (identifier of the existing term that would be deprecated and replaced by this term; normative): None
* ABCD 2.06 (XPATH of the equivalent term in ABCD or EFG; not normative): not in ABCD
| process | new term targethabitatscope new term submitter humboldt extension task group efficacy justification why is this term necessary part of a package of terms in support of biological inventory data demand justification name at least two organizations that independently need this term the humboldt extension task group proposing this term consists of numerous organizations stability justification what concerns are there that this might affect existing implementations none implications for dwciri namespace does this change affect a dwciri term version needs ecoiri equivalent proposed attributes of the new term term name in lowercamelcase for properties uppercamelcase for classes targethabitatscope term label english not normative target habitat scope organized in class e g occurrence event location taxon event definition of the term normative the habitats targeted for sampling during the dwc event usage comments recommendations regarding content etc not normative recommended best practice is to use a controlled vocabulary and separate the values in a list with space vertical bar space examples not normative dunes pine forest riparian scrub grassland refines identifier of the broader term this term refines normative none replaces identifier of the existing term that would be deprecated and replaced by this term normative none abcd xpath of the equivalent term in abcd or efg not normative not in abcd | 1 |
8,120 | 11,303,180,180 | IssuesEvent | 2020-01-17 19:28:15 | bcgov/entity | https://api.github.com/repos/bcgov/entity | closed | Web update comms process | OCM_Int Processes | - [x] create process with Cameron & Genvieve
- [x] Simona to document process
- [ ] Genvieve review
- [ ] Cameron review
- [x] Katherine review | 1.0 | Web update comms process - - [x] create process with Cameron & Genvieve
- [x] Simona to document process
- [ ] Genvieve review
- [ ] Cameron review
- [x] Katherine review | process | web update comms process create process with cameron genvieve simona to document process genvieve review cameron review katherine review | 1 |
270,627 | 29,043,977,422 | IssuesEvent | 2023-05-13 10:06:25 | MatBenfield/news | https://api.github.com/repos/MatBenfield/news | closed | [SecurityWeek] 1 Million WordPress Sites Impacted by Exploited Plugin Vulnerability | SecurityWeek Stale |
Exploitation of a critical vulnerability in the Essential Addons for Elementor WordPress plugin started immediately after a patch was released.
The post [1 Million WordPress Sites Impacted by Exploited Plugin Vulnerability](https://www.securityweek.com/1-million-wordpress-sites-impacted-by-exploited-plugin-vulnerability/) appeared first on [SecurityWeek](https://www.securityweek.com).
<https://www.securityweek.com/1-million-wordpress-sites-impacted-by-exploited-plugin-vulnerability/>
| True | [SecurityWeek] 1 Million WordPress Sites Impacted by Exploited Plugin Vulnerability -
Exploitation of a critical vulnerability in the Essential Addons for Elementor WordPress plugin started immediately after a patch was released.
The post [1 Million WordPress Sites Impacted by Exploited Plugin Vulnerability](https://www.securityweek.com/1-million-wordpress-sites-impacted-by-exploited-plugin-vulnerability/) appeared first on [SecurityWeek](https://www.securityweek.com).
<https://www.securityweek.com/1-million-wordpress-sites-impacted-by-exploited-plugin-vulnerability/>
| non_process | million wordpress sites impacted by exploited plugin vulnerability exploitation of a critical vulnerability in the essential addons for elementor wordpress plugin started immediately after a patch was released the post appeared first on | 0 |
429,273 | 12,422,762,327 | IssuesEvent | 2020-05-24 00:27:09 | eclipse-ee4j/glassfish | https://api.github.com/repos/eclipse-ee4j/glassfish | closed | WSIT pipes may be cached | Component: jbi ERR: Assignee Priority: Minor Stale Type: Bug as91-na | HTTP BC uses the asynchronous transport so HTTP SOAP processing is asynchronous
by default. When WSIT policies are present, we expect to see synchronous
behavior.
However, once a WSIT feature is used in any JBI project (with SOAP request
processed by HTTP BC), all subsequent SOAP processing will fall back to sync
mode, even for projects with no WSIT policies defined.
Attached are two simple JBI projects: TestSyncApp has WSIT policies defined,
TestAsyncApplication does not.
In these projects, we use HTTP BC to receive SOAP requests and route them to
the BPEL engine. The BPEL process is a simple pass through. It logs a record in
a JMS queue everytime a new message arrives. A long "wait" activity is placed
to create a block on the response. Incoming requests will be blocked, i.e. not
put through to the BPEL process when processing is synchronous (all incoming
request processing threads are tied up waiting for the responses)
A test client project (HttpBCAsyncTester) is also attached here. The test
client will keep track of the number of SOAP requests posted to HTTP BC, and
the number of records logged in the JMS queue(which corresponds to the number
of message received in BPEL). If the number of messages sent matches the number
of JMS records, then it is asynchronous. If the number of messages sent is
greater than the JMS records, then that means the request processing is
synchronous.
The SOAP message the test client uses to post requests is also attached here
(inputdata.xml)
Steps to reproduce the issue:
1\. Install and start following JBI components:
HTTP BC, JMS BC, BPEL SE
2\. Right click on HTTP BC node in NetBeans JBI manager, select "properties",
set the "number of outbound threads" to 3
3\. Extract the attached project zip files
4\. Make sure the inputdata.xml is saved in the file system.
5\. Open the projects in NetBeans
6\. Right click on TestAsyncApplication project, select "Deploy Project".
7\. Right click on HttpBCAsyncTester project, select "Properties", select "Run",
select "AsyncTest" from the "Configuration" drop down list.
Make sure the last argument points to the file location of the input data.
(Note: the file location needs to be prefixed by "f://")
The other 2 arguments should not be changed.
8\. Right click on HttpBCAsyncTester project, select "Run"
9\. Observe the output on the HttpBCAsyncTester run window.
The number of messages sent should be 6\. The number of messages read from
the JMS queue should also be 6.
10\. Right click on TestAsyncApplication project, select "Undeploy Project"
11\. Right click on TestSyncApp project, select "Deploy project"
12\. Right click on HttpBCAsyncTester project, select "Properties",
select "Run", select "SyncTest" from the "Configuration" drop down list.
Make sure the last argument points to the file location of the input data.
(Note: the file location needs to be prefixed by "f://")
The other 2 arguments should not be changed.
13\. Right click on HttpBCAsyncTester project, select "Run"
14\. Observe the output on the HttpBCAsyncTester run window.
The number of sent message should be 6, but the number of messages read
from the JMS queue should be 3.
15\. Undeploy TestSyncApp, and deploy TestAsyncApplication again.
16\. Repeat step 7 & 8
The number of messages sent should be 6, but the number of message read
from the JMS queue should be 0.
#### Environment
Operating System: All
Platform: All | 1.0 | WSIT pipes may be cached - HTTP BC uses the asynchronous transport so HTTP SOAP processing is asynchronous
by default. When WSIT policies are present, we expect to see synchronous
behavior.
However, once a WSIT feature is used in any JBI project (with SOAP request
processed by HTTP BC), all subsequent SOAP processing will fall back to sync
mode, even for projects with no WSIT policies defined.
Attached are two simple JBI projects: TestSyncApp has WSIT policies defined,
TestAsyncApplication does not.
In these projects, we use HTTP BC to receive SOAP requests and route them to
the BPEL engine. The BPEL process is a simple pass through. It logs a record in
a JMS queue everytime a new message arrives. A long "wait" activity is placed
to create a block on the response. Incoming requests will be blocked, i.e. not
put through to the BPEL process when processing is synchronous (all incoming
request processing threads are tied up waiting for the responses)
A test client project (HttpBCAsyncTester) is also attached here. The test
client will keep track of the number of SOAP requests posted to HTTP BC, and
the number of records logged in the JMS queue(which corresponds to the number
of message received in BPEL). If the number of messages sent matches the number
of JMS records, then it is asynchronous. If the number of messages sent is
greater than the JMS records, then that means the request processing is
synchronous.
The SOAP message the test client uses to post requests is also attached here
(inputdata.xml)
Steps to reproduce the issue:
1\. Install and start following JBI components:
HTTP BC, JMS BC, BPEL SE
2\. Right click on HTTP BC node in NetBeans JBI manager, select "properties",
set the "number of outbound threads" to 3
3\. Extract the attached project zip files
4\. Make sure the inputdata.xml is saved in the file system.
5\. Open the projects in NetBeans
6\. Right click on TestAsyncApplication project, select "Deploy Project".
7\. Right click on HttpBCAsyncTester project, select "Properties", select "Run",
select "AsyncTest" from the "Configuration" drop down list.
Make sure the last argument points to the file location of the input data.
(Note: the file location needs to be prefixed by "f://")
The other 2 arguments should not be changed.
8\. Right click on HttpBCAsyncTester project, select "Run"
9\. Observe the output on the HttpBCAsyncTester run window.
The number of messages sent should be 6\. The number of messages read from
the JMS queue should also be 6.
10\. Right click on TestAsyncApplication project, select "Undeploy Project"
11\. Right click on TestSyncApp project, select "Deploy project"
12\. Right click on HttpBCAsyncTester project, select "Properties",
select "Run", select "SyncTest" from the "Configuration" drop down list.
Make sure the last argument points to the file location of the input data.
(Note: the file location needs to be prefixed by "f://")
The other 2 arguments should not be changed.
13\. Right click on HttpBCAsyncTester project, select "Run"
14\. Observe the output on the HttpBCAsyncTester run window.
The number of sent message should be 6, but the number of messages read
from the JMS queue should be 3.
15\. Undeploy TestSyncApp, and deploy TestAsyncApplication again.
16\. Repeat step 7 & 8
The number of messages sent should be 6, but the number of message read
from the JMS queue should be 0.
#### Environment
Operating System: All
Platform: All | non_process | wsit pipes may be cached http bc uses the asynchronous transport so http soap processing is asynchronous by default when wsit policies are present we expect to see synchronous behavior however once a wsit feature is used in any jbi project with soap request processed by http bc all subsequent soap processing will fall back to sync mode even for projects with no wsit policies defined attached are two simple jbi projects testsyncapp has wsit policies defined testasyncapplication does not in these projects we use http bc to receive soap requests and route them to the bpel engine the bpel process is a simple pass through it logs a record in a jms queue everytime a new message arrives a long wait activity is placed to create a block on the response incoming requests will be blocked i e not put through to the bpel process when processing is synchronous all incoming request processing threads are tied up waiting for the responses a test client project httpbcasynctester is also attached here the test client will keep track of the number of soap requests posted to http bc and the number of records logged in the jms queue which corresponds to the number of message received in bpel if the number of messages sent matches the number of jms records then it is asynchronous if the number of messages sent is greater than the jms records then that means the request processing is synchronous the soap message the test client uses to post requests is also attached here inputdata xml steps to reproduce the issue install and start following jbi components http bc jms bc bpel se right click on http bc node in netbeans jbi manager select properties set the number of outbound threads to extract the attached project zip files make sure the inputdata xml is saved in the file system open the projects in netbeans right click on testasyncapplication project select deploy project right click on httpbcasynctester project select properties select run select asynctest from the configuration drop down list make sure the last argument points to the file location of the input data note the file location needs to be prefixed by f the other arguments should not be changed right click on httpbcasynctester project select run observe the output on the httpbcasynctester run window the number of messages sent should be the number of messages read from the jms queue should also be right click on testasyncapplication project select undeploy project right click on testsyncapp project select deploy project right click on httpbcasynctester project select properties select run select synctest from the configuration drop down list make sure the last argument points to the file location of the input data note the file location needs to be prefixed by f the other arguments should not be changed right click on httpbcasynctester project select run observe the output on the httpbcasynctester run window the number of sent message should be but the number of messages read from the jms queue should be undeploy testsyncapp and deploy testasyncapplication again repeat step the number of messages sent should be but the number of message read from the jms queue should be environment operating system all platform all | 0 |
22,118 | 30,650,379,637 | IssuesEvent | 2023-07-25 08:30:34 | 0xPolygonMiden/miden-vm | https://api.github.com/repos/0xPolygonMiden/miden-vm | opened | Consider adding instructions to read memory of the parent context | enhancement instruction set processor | One of the consequences of #948, is that we would get access to the parent context ID via `prnt_ctx` column. This means, we would be able to execute operations which read values from (and even write values to) parent memory.
While writing values into parent context may lead to potential security issues, reading values should be OK in most cases, and it could simplify passing large amounts of data from the caller to the callee.
The instructions could be something like `pmem_load` and `pmem_loadw` (to mimic `mem_load` and `mem_loadw`). | 1.0 | Consider adding instructions to read memory of the parent context - One of the consequences of #948, is that we would get access to the parent context ID via `prnt_ctx` column. This means, we would be able to execute operations which read values from (and even write values to) parent memory.
While writing values into parent context may lead to potential security issues, reading values should be OK in most cases, and it could simplify passing large amounts of data from the caller to the callee.
The instructions could be something like `pmem_load` and `pmem_loadw` (to mimic `mem_load` and `mem_loadw`). | process | consider adding instructions to read memory of the parent context one of the consequences of is that we would get access to the parent context id via prnt ctx column this means we would be able to execute operations which read values from and even write values to parent memory while writing values into parent context may lead to potential security issues reading values should be ok in most cases and it could simplify passing large amounts of data from the caller to the callee the instructions could be something like pmem load and pmem loadw to mimic mem load and mem loadw | 1 |
18,863 | 24,787,139,190 | IssuesEvent | 2022-10-24 10:45:24 | goblint/analyzer | https://api.github.com/repos/goblint/analyzer | closed | Polish `__goblint_check` | cleanup testing preprocessing | In #278 all the `assert`s in tests were changed to `__goblint_check`, which is declared by a `goblint.h` header that we forcefully include into every analyzed file via `-include`. This makes the programs normally uncompilable and most of them still include `assert.h`, which now is excessive.
This situation should be improved:
- [x] Add explicit `#include <goblint.h>` to all tests using `__goblint_check`.
- [x] Remove excessive `#include <assert.h>` from such tests.
- [x] Add explicit `#include <goblint.h>` to all tests using `__goblint_assume_join`, `__goblint_split_begin` and `__goblint_split_end`.
- [x] Provide a dummy implementation for `goblint.h`, which wouldn't be used for analysis (they're handled as specials), but could be used for compiling the programs. It would also allow using Goblint function annotations in actual projects/stories.
- [x] Document `__goblint_check`, etc as function annotations like `__goblint_assume_join` is documented in #724.
- [x] Design a better structure for our `includes` directory: right now it contains a mix of various things and cannot be added to include paths of actual projects:
1. Goblint-specific headers: `goblint.h`, `linux/goblint_preconf.h`, `linuxlight.h`?
2. Goblint overrides of standard headers: `assert.h`.
3. Goblint stubs for standard functions: `stdlib.c`, `pthread.c`.
4. Goblint stubs for non-standard functions: `sv-comp.c`.
5. And eventually general stubs for Goblint-specific functions: `goblint.c`.
They should be split by these various types. Moreover, each of them should have standard structure (`include`, `src`, etc).
- [x] Rename `includes` to something better since it also contains various stub implementations. | 1.0 | Polish `__goblint_check` - In #278 all the `assert`s in tests were changed to `__goblint_check`, which is declared by a `goblint.h` header that we forcefully include into every analyzed file via `-include`. This makes the programs normally uncompilable and most of them still include `assert.h`, which now is excessive.
This situation should be improved:
- [x] Add explicit `#include <goblint.h>` to all tests using `__goblint_check`.
- [x] Remove excessive `#include <assert.h>` from such tests.
- [x] Add explicit `#include <goblint.h>` to all tests using `__goblint_assume_join`, `__goblint_split_begin` and `__goblint_split_end`.
- [x] Provide a dummy implementation for `goblint.h`, which wouldn't be used for analysis (they're handled as specials), but could be used for compiling the programs. It would also allow using Goblint function annotations in actual projects/stories.
- [x] Document `__goblint_check`, etc as function annotations like `__goblint_assume_join` is documented in #724.
- [x] Design a better structure for our `includes` directory: right now it contains a mix of various things and cannot be added to include paths of actual projects:
1. Goblint-specific headers: `goblint.h`, `linux/goblint_preconf.h`, `linuxlight.h`?
2. Goblint overrides of standard headers: `assert.h`.
3. Goblint stubs for standard functions: `stdlib.c`, `pthread.c`.
4. Goblint stubs for non-standard functions: `sv-comp.c`.
5. And eventually general stubs for Goblint-specific functions: `goblint.c`.
They should be split by these various types. Moreover, each of them should have standard structure (`include`, `src`, etc).
- [x] Rename `includes` to something better since it also contains various stub implementations. | process | polish goblint check in all the assert s in tests were changed to goblint check which is declared by a goblint h header that we forcefully include into every analyzed file via include this makes the programs normally uncompilable and most of them still include assert h which now is excessive this situation should be improved add explicit include to all tests using goblint check remove excessive include from such tests add explicit include to all tests using goblint assume join goblint split begin and goblint split end provide a dummy implementation for goblint h which wouldn t be used for analysis they re handled as specials but could be used for compiling the programs it would also allow using goblint function annotations in actual projects stories document goblint check etc as function annotations like goblint assume join is documented in design a better structure for our includes directory right now it contains a mix of various things and cannot be added to include paths of actual projects goblint specific headers goblint h linux goblint preconf h linuxlight h goblint overrides of standard headers assert h goblint stubs for standard functions stdlib c pthread c goblint stubs for non standard functions sv comp c and eventually general stubs for goblint specific functions goblint c they should be split by these various types moreover each of them should have standard structure include src etc rename includes to something better since it also contains various stub implementations | 1 |
703,419 | 24,158,312,550 | IssuesEvent | 2022-09-22 09:30:40 | younginnovations/iatipublisher | https://api.github.com/repos/younginnovations/iatipublisher | closed | Bug : Arrangement of label fields | type: bug type: UI/UX priority: high Frontend | - [x] **Issue 1: Iati- Identifier**
Actual Result
Expected Result
- Should be aligned in the same line
- [x] **Issue 2: Transactions**
Actual Result
Expected Result
- [x] **Issue 3 : Result**
Actual Result
Expected Result
- Should be aligned in the same line
- [x] **Issue 4 : Indicator**
Actual Result
Expected Result
- [x] **Issue 5 :organisation data >>organisation-identifier**
Actual Result
Expected Result
- Should be aligned in the same line | 1.0 | Bug : Arrangement of label fields - - [x] **Issue 1: Iati- Identifier**
Actual Result
Expected Result
- Should be aligned in the same line
- [x] **Issue 2: Transactions**
Actual Result
Expected Result
- [x] **Issue 3 : Result**
Actual Result
Expected Result
- Should be aligned in the same line
- [x] **Issue 4 : Indicator**
Actual Result
Expected Result
- [x] **Issue 5 :organisation data >>organisation-identifier**
Actual Result
Expected Result
- Should be aligned in the same line | non_process | bug arrangement of label fields issue iati identifier actual result expected result should be aligned in the same line issue transactions actual result expected result issue result actual result expected result should be aligned in the same line issue indicator actual result expected result issue organisation data organisation identifier actual result expected result should be aligned in the same line | 0 |
39,100 | 10,297,869,051 | IssuesEvent | 2019-08-28 08:54:26 | angular/angular-cli | https://api.github.com/repos/angular/angular-cli | opened | Subresource Integrity for lazy modules is broken when DL is enabled | comp: devkit/build-angular freq3: high severity5: regression type: bug/fix | <!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅
Oh hi there! 😄
To expedite issue processing please search open and closed issues before submitting a new one.
Existing issues often contain information about workarounds, resolution, or progress updates.
🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅-->
# 🐞 Bug report
### Command (mark with an `x`)
<!-- Can you pin-point the command or commands that are effected by this bug? -->
<!-- ✍️edit: -->
```
- [ ] new
- [X] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc
```
### Is this a regression?
Yes, this is caused by the downleveling process.
### Description
## 🔬 Minimal Reproduction
```
ng new lazy-loading-dl --routing
cd lazy-loading-dl
ng g m foo --module app.module --route foo
```
Add the below in `app.component.html`
```
<a [routerLink]="['/foo']" >
link to foo
</a>
```
```
ng build --prod --subresourceIntegrity
http-server dist/lazy-loading-dl
```
Open browser and click on the link
## 🔥 Exception or Error
<pre><code>
127.0.0.1/:1 Failed to find a valid digest in the 'integrity' attribute for resource 'http://127.0.0.1:8080/5-es2015.0914cd2e5d35cddfa66f.js' with computed SHA-256 integrity '9yuul7bmARNSj/M5wygxgYjfklmwN0bTD+8YGHdn5/I='. The resource has been blocked.
main-es2015.8ce6a89e85cdffc26eb1.js:1 ERROR Error: Uncaught (in promise): ChunkLoadError: Loading chunk 5 failed.
(error: http://127.0.0.1:8080/5-es2015.0914cd2e5d35cddfa66f.js)
ChunkLoadError: Loading chunk 5 failed.
(error: http://127.0.0.1:8080/5-es2015.0914cd2e5d35cddfa66f.js)
at Function.u.e (runtime-es2015.6b58afc9912521e9b6e5.js:1)
at w (main-es2015.8ce6a89e85cdffc26eb1.js:1)
at Rn.loadModuleFactory (main-es2015.8ce6a89e85cdffc26eb1.js:1)
at Rn.load (main-es2015.8ce6a89e85cdffc26eb1.js:1)
at c.project (main-es2015.8ce6a89e85cdffc26eb1.js:1)
at c._tryNext (main-es2015.8ce6a89e85cdffc26eb1.js:1)
at c._next (main-es2015.8ce6a89e85cdffc26eb1.js:1)
at c.next (main-es2015.8ce6a89e85cdffc26eb1.js:1)
at e._subscribe (main-es2015.8ce6a89e85cdffc26eb1.js:1)
at e._trySubscribe (main-es2015.8ce6a89e85cdffc26eb1.js:1)
at P (polyfills-es2015.fd917e7c3ed57f282ee5.js:1)
at P (polyfills-es2015.fd917e7c3ed57f282ee5.js:1)
at polyfills-es2015.fd917e7c3ed57f282ee5.js:1
at a.invokeTask (polyfills-es2015.fd917e7c3ed57f282ee5.js:1)
at Object.onInvokeTask (main-es2015.8ce6a89e85cdffc26eb1.js:1)
at a.invokeTask (polyfills-es2015.fd917e7c3ed57f282ee5.js:1)
at s.runTask (polyfills-es2015.fd917e7c3ed57f282ee5.js:1)
at _ (polyfills-es2015.fd917e7c3ed57f282ee5.js:1)
at c.invokeTask [as invoke] (polyfills-es2015.fd917e7c3ed57f282ee5.js:1)
at y (polyfills-es2015.fd917e7c3ed57f282ee5.js:1)
</code></pre>
## 🌍 Your Environment
<pre><code>
Angular CLI: 8.3.0
Node: 10.10.0
OS: win32 x64
Angular: 8.2.3
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Package Version
-----------------------------------------------------------
@angular-devkit/architect 0.803.0
@angular-devkit/build-angular 0.803.0
@angular-devkit/build-optimizer 0.803.0
@angular-devkit/build-webpack 0.803.0
@angular-devkit/core 8.3.0
@angular-devkit/schematics 8.3.0
@angular/cli 8.3.0
@ngtools/webpack 8.3.0
@schematics/angular 8.3.0
@schematics/update 0.803.0
rxjs 6.4.0
typescript 3.5.3
webpack 4.39.2
</code></pre>
**Anything else relevant?**
<!-- ✍️Is this a browser specific issue? If so, please specify the browser and version. -->
<!-- ✍️Do any of these matter: operating system, IDE, package manager, HTTP server, ...? If so, please mention it below. -->
| 1.0 | Subresource Integrity for lazy modules is broken when DL is enabled - <!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅
Oh hi there! 😄
To expedite issue processing please search open and closed issues before submitting a new one.
Existing issues often contain information about workarounds, resolution, or progress updates.
🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅-->
# 🐞 Bug report
### Command (mark with an `x`)
<!-- Can you pin-point the command or commands that are effected by this bug? -->
<!-- ✍️edit: -->
```
- [ ] new
- [X] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc
```
### Is this a regression?
Yes, this is caused by the downleveling process.
### Description
## 🔬 Minimal Reproduction
```
ng new lazy-loading-dl --routing
cd lazy-loading-dl
ng g m foo --module app.module --route foo
```
Add the below in `app.component.html`
```
<a [routerLink]="['/foo']" >
link to foo
</a>
```
```
ng build --prod --subresourceIntegrity
http-server dist/lazy-loading-dl
```
Open browser and click on the link
## 🔥 Exception or Error
<pre><code>
127.0.0.1/:1 Failed to find a valid digest in the 'integrity' attribute for resource 'http://127.0.0.1:8080/5-es2015.0914cd2e5d35cddfa66f.js' with computed SHA-256 integrity '9yuul7bmARNSj/M5wygxgYjfklmwN0bTD+8YGHdn5/I='. The resource has been blocked.
main-es2015.8ce6a89e85cdffc26eb1.js:1 ERROR Error: Uncaught (in promise): ChunkLoadError: Loading chunk 5 failed.
(error: http://127.0.0.1:8080/5-es2015.0914cd2e5d35cddfa66f.js)
ChunkLoadError: Loading chunk 5 failed.
(error: http://127.0.0.1:8080/5-es2015.0914cd2e5d35cddfa66f.js)
at Function.u.e (runtime-es2015.6b58afc9912521e9b6e5.js:1)
at w (main-es2015.8ce6a89e85cdffc26eb1.js:1)
at Rn.loadModuleFactory (main-es2015.8ce6a89e85cdffc26eb1.js:1)
at Rn.load (main-es2015.8ce6a89e85cdffc26eb1.js:1)
at c.project (main-es2015.8ce6a89e85cdffc26eb1.js:1)
at c._tryNext (main-es2015.8ce6a89e85cdffc26eb1.js:1)
at c._next (main-es2015.8ce6a89e85cdffc26eb1.js:1)
at c.next (main-es2015.8ce6a89e85cdffc26eb1.js:1)
at e._subscribe (main-es2015.8ce6a89e85cdffc26eb1.js:1)
at e._trySubscribe (main-es2015.8ce6a89e85cdffc26eb1.js:1)
at P (polyfills-es2015.fd917e7c3ed57f282ee5.js:1)
at P (polyfills-es2015.fd917e7c3ed57f282ee5.js:1)
at polyfills-es2015.fd917e7c3ed57f282ee5.js:1
at a.invokeTask (polyfills-es2015.fd917e7c3ed57f282ee5.js:1)
at Object.onInvokeTask (main-es2015.8ce6a89e85cdffc26eb1.js:1)
at a.invokeTask (polyfills-es2015.fd917e7c3ed57f282ee5.js:1)
at s.runTask (polyfills-es2015.fd917e7c3ed57f282ee5.js:1)
at _ (polyfills-es2015.fd917e7c3ed57f282ee5.js:1)
at c.invokeTask [as invoke] (polyfills-es2015.fd917e7c3ed57f282ee5.js:1)
at y (polyfills-es2015.fd917e7c3ed57f282ee5.js:1)
</code></pre>
## 🌍 Your Environment
<pre><code>
Angular CLI: 8.3.0
Node: 10.10.0
OS: win32 x64
Angular: 8.2.3
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Package Version
-----------------------------------------------------------
@angular-devkit/architect 0.803.0
@angular-devkit/build-angular 0.803.0
@angular-devkit/build-optimizer 0.803.0
@angular-devkit/build-webpack 0.803.0
@angular-devkit/core 8.3.0
@angular-devkit/schematics 8.3.0
@angular/cli 8.3.0
@ngtools/webpack 8.3.0
@schematics/angular 8.3.0
@schematics/update 0.803.0
rxjs 6.4.0
typescript 3.5.3
webpack 4.39.2
</code></pre>
**Anything else relevant?**
<!-- ✍️Is this a browser specific issue? If so, please specify the browser and version. -->
<!-- ✍️Do any of these matter: operating system, IDE, package manager, HTTP server, ...? If so, please mention it below. -->
| non_process | subresource integrity for lazy modules is broken when dl is enabled 🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅 oh hi there 😄 to expedite issue processing please search open and closed issues before submitting a new one existing issues often contain information about workarounds resolution or progress updates 🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅 🐞 bug report command mark with an x new build serve test generate add update lint run config help version doc is this a regression yes this is caused by the downleveling process description 🔬 minimal reproduction ng new lazy loading dl routing cd lazy loading dl ng g m foo module app module route foo add the below in app component html link to foo ng build prod subresourceintegrity http server dist lazy loading dl open browser and click on the link 🔥 exception or error failed to find a valid digest in the integrity attribute for resource with computed sha integrity i the resource has been blocked main js error error uncaught in promise chunkloaderror loading chunk failed error chunkloaderror loading chunk failed error at function u e runtime js at w main js at rn loadmodulefactory main js at rn load main js at c project main js at c trynext main js at c next main js at c next main js at e subscribe main js at e trysubscribe main js at p polyfills js at p polyfills js at polyfills js at a invoketask polyfills js at object oninvoketask main js at a invoketask polyfills js at s runtask polyfills js at polyfills js at c invoketask polyfills js at y polyfills js 🌍 your environment angular cli node os angular animations common compiler compiler cli core forms language service platform browser platform browser dynamic router package version angular devkit architect angular devkit build angular angular devkit build optimizer angular devkit build webpack angular devkit core angular devkit schematics angular cli ngtools webpack schematics angular schematics update rxjs typescript webpack anything else relevant | 0 |
772,647 | 27,130,809,096 | IssuesEvent | 2023-02-16 09:39:10 | GoogleCloudPlatform/java-docs-samples | https://api.github.com/repos/GoogleCloudPlatform/java-docs-samples | opened | CommuteSearchJobsTest: testCommuteSearchJobs failed | type: bug priority: p1 flakybot: issue | Note: #6610 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
----
commit: f3ac816370643d418b10e0fe93859e6a984bb44d
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/eb0701d2-5dc6-4a0a-b634-515b3facb6e3), [Sponge](http://sponge2/eb0701d2-5dc6-4a0a-b634-515b3facb6e3)
status: failed
<details><summary>Test output</summary><br><pre>com.google.api.gax.rpc.InternalException: io.grpc.StatusRuntimeException: INTERNAL: Encountered unexpected server errors, please try again later.. Request ID for tracking: ecf50ed1-b45e-4b25-904c-55ac050eafd4:APAb7IRmq92cygcFbtIqGnUTRPo1wPmNig==
at com.google.api.gax.rpc.ApiExceptionFactory.createException(ApiExceptionFactory.java:110)
at com.google.api.gax.rpc.ApiExceptionFactory.createException(ApiExceptionFactory.java:41)
at com.google.api.gax.grpc.GrpcApiExceptionFactory.create(GrpcApiExceptionFactory.java:86)
at com.google.api.gax.grpc.GrpcApiExceptionFactory.create(GrpcApiExceptionFactory.java:66)
at com.google.api.gax.grpc.GrpcExceptionCallable$ExceptionTransformingFuture.onFailure(GrpcExceptionCallable.java:97)
at com.google.api.core.ApiFutures$1.onFailure(ApiFutures.java:67)
at com.google.common.util.concurrent.Futures$CallbackListener.run(Futures.java:1132)
at com.google.common.util.concurrent.DirectExecutor.execute(DirectExecutor.java:31)
at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1270)
at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:1038)
at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:808)
at io.grpc.stub.ClientCalls$GrpcFuture.setException(ClientCalls.java:574)
at io.grpc.stub.ClientCalls$UnaryStreamToFuture.onClose(ClientCalls.java:544)
at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
at com.google.api.gax.grpc.ChannelPool$ReleasingClientCall$1.onClose(ChannelPool.java:535)
at io.grpc.internal.DelayedClientCall$DelayedListener$3.run(DelayedClientCall.java:471)
at io.grpc.internal.DelayedClientCall$DelayedListener.delayOrExecute(DelayedClientCall.java:435)
at io.grpc.internal.DelayedClientCall$DelayedListener.onClose(DelayedClientCall.java:468)
at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:563)
at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:70)
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:744)
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:723)
at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:133)
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:750)
Suppressed: com.google.api.gax.rpc.AsyncTaskException: Asynchronous task failed
at com.google.api.gax.rpc.ApiExceptions.callAndTranslateApiException(ApiExceptions.java:57)
at com.google.api.gax.rpc.UnaryCallable.call(UnaryCallable.java:112)
at com.google.cloud.talent.v4beta1.JobServiceClient.searchJobs(JobServiceClient.java:1595)
at com.example.jobs.CommuteSearchJobs.searchJobs(CommuteSearchJobs.java:85)
at CommuteSearchJobsTest.testCommuteSearchJobs(CommuteSearchJobsTest.java:44)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
Caused by: io.grpc.StatusRuntimeException: INTERNAL: Encountered unexpected server errors, please try again later.. Request ID for tracking: ecf50ed1-b45e-4b25-904c-55ac050eafd4:APAb7IRmq92cygcFbtIqGnUTRPo1wPmNig==
at io.grpc.Status.asRuntimeException(Status.java:539)
... 17 more
</pre></details> | 1.0 | CommuteSearchJobsTest: testCommuteSearchJobs failed - Note: #6610 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
----
commit: f3ac816370643d418b10e0fe93859e6a984bb44d
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/eb0701d2-5dc6-4a0a-b634-515b3facb6e3), [Sponge](http://sponge2/eb0701d2-5dc6-4a0a-b634-515b3facb6e3)
status: failed
<details><summary>Test output</summary><br><pre>com.google.api.gax.rpc.InternalException: io.grpc.StatusRuntimeException: INTERNAL: Encountered unexpected server errors, please try again later.. Request ID for tracking: ecf50ed1-b45e-4b25-904c-55ac050eafd4:APAb7IRmq92cygcFbtIqGnUTRPo1wPmNig==
at com.google.api.gax.rpc.ApiExceptionFactory.createException(ApiExceptionFactory.java:110)
at com.google.api.gax.rpc.ApiExceptionFactory.createException(ApiExceptionFactory.java:41)
at com.google.api.gax.grpc.GrpcApiExceptionFactory.create(GrpcApiExceptionFactory.java:86)
at com.google.api.gax.grpc.GrpcApiExceptionFactory.create(GrpcApiExceptionFactory.java:66)
at com.google.api.gax.grpc.GrpcExceptionCallable$ExceptionTransformingFuture.onFailure(GrpcExceptionCallable.java:97)
at com.google.api.core.ApiFutures$1.onFailure(ApiFutures.java:67)
at com.google.common.util.concurrent.Futures$CallbackListener.run(Futures.java:1132)
at com.google.common.util.concurrent.DirectExecutor.execute(DirectExecutor.java:31)
at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1270)
at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:1038)
at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:808)
at io.grpc.stub.ClientCalls$GrpcFuture.setException(ClientCalls.java:574)
at io.grpc.stub.ClientCalls$UnaryStreamToFuture.onClose(ClientCalls.java:544)
at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23)
at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40)
at com.google.api.gax.grpc.ChannelPool$ReleasingClientCall$1.onClose(ChannelPool.java:535)
at io.grpc.internal.DelayedClientCall$DelayedListener$3.run(DelayedClientCall.java:471)
at io.grpc.internal.DelayedClientCall$DelayedListener.delayOrExecute(DelayedClientCall.java:435)
at io.grpc.internal.DelayedClientCall$DelayedListener.onClose(DelayedClientCall.java:468)
at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:563)
at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:70)
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:744)
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:723)
at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:133)
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:750)
Suppressed: com.google.api.gax.rpc.AsyncTaskException: Asynchronous task failed
at com.google.api.gax.rpc.ApiExceptions.callAndTranslateApiException(ApiExceptions.java:57)
at com.google.api.gax.rpc.UnaryCallable.call(UnaryCallable.java:112)
at com.google.cloud.talent.v4beta1.JobServiceClient.searchJobs(JobServiceClient.java:1595)
at com.example.jobs.CommuteSearchJobs.searchJobs(CommuteSearchJobs.java:85)
at CommuteSearchJobsTest.testCommuteSearchJobs(CommuteSearchJobsTest.java:44)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
Caused by: io.grpc.StatusRuntimeException: INTERNAL: Encountered unexpected server errors, please try again later.. Request ID for tracking: ecf50ed1-b45e-4b25-904c-55ac050eafd4:APAb7IRmq92cygcFbtIqGnUTRPo1wPmNig==
at io.grpc.Status.asRuntimeException(Status.java:539)
... 17 more
</pre></details> | non_process | commutesearchjobstest testcommutesearchjobs failed note was also for this test but it was closed more than days ago so i didn t mark it flaky commit buildurl status failed test output com google api gax rpc internalexception io grpc statusruntimeexception internal encountered unexpected server errors please try again later request id for tracking at com google api gax rpc apiexceptionfactory createexception apiexceptionfactory java at com google api gax rpc apiexceptionfactory createexception apiexceptionfactory java at com google api gax grpc grpcapiexceptionfactory create grpcapiexceptionfactory java at com google api gax grpc grpcapiexceptionfactory create grpcapiexceptionfactory java at com google api gax grpc grpcexceptioncallable exceptiontransformingfuture onfailure grpcexceptioncallable java at com google api core apifutures onfailure apifutures java at com google common util concurrent futures callbacklistener run futures java at com google common util concurrent directexecutor execute directexecutor java at com google common util concurrent abstractfuture executelistener abstractfuture java at com google common util concurrent abstractfuture complete abstractfuture java at com google common util concurrent abstractfuture setexception abstractfuture java at io grpc stub clientcalls grpcfuture setexception clientcalls java at io grpc stub clientcalls unarystreamtofuture onclose clientcalls java at io grpc partialforwardingclientcalllistener onclose partialforwardingclientcalllistener java at io grpc forwardingclientcalllistener onclose forwardingclientcalllistener java at io grpc forwardingclientcalllistener simpleforwardingclientcalllistener onclose forwardingclientcalllistener java at com google api gax grpc channelpool releasingclientcall onclose channelpool java at io grpc internal delayedclientcall delayedlistener run delayedclientcall java at io grpc internal delayedclientcall delayedlistener delayorexecute delayedclientcall java at io grpc internal delayedclientcall delayedlistener onclose delayedclientcall java at io grpc internal clientcallimpl closeobserver clientcallimpl java at io grpc internal clientcallimpl access clientcallimpl java at io grpc internal clientcallimpl clientstreamlistenerimpl runinternal clientcallimpl java at io grpc internal clientcallimpl clientstreamlistenerimpl runincontext clientcallimpl java at io grpc internal contextrunnable run contextrunnable java at io grpc internal serializingexecutor run serializingexecutor java at java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java util concurrent threadpoolexecutor worker run threadpoolexecutor java at java lang thread run thread java suppressed com google api gax rpc asynctaskexception asynchronous task failed at com google api gax rpc apiexceptions callandtranslateapiexception apiexceptions java at com google api gax rpc unarycallable call unarycallable java at com google cloud talent jobserviceclient searchjobs jobserviceclient java at com example jobs commutesearchjobs searchjobs commutesearchjobs java at commutesearchjobstest testcommutesearchjobs commutesearchjobstest java at sun reflect nativemethodaccessorimpl native method at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org junit runners model frameworkmethod runreflectivecall frameworkmethod java at org junit internal runners model reflectivecallable run reflectivecallable java at org junit runners model frameworkmethod invokeexplosively frameworkmethod java at org junit internal runners statements invokemethod evaluate invokemethod java at org junit internal runners statements runbefores evaluate runbefores java at org junit internal runners statements runafters evaluate runafters java at org junit runners parentrunner evaluate parentrunner java at org junit runners evaluate java at org junit runners parentrunner runleaf parentrunner java at org junit runners runchild java at org junit runners runchild java at org junit runners parentrunner run parentrunner java at org junit runners parentrunner schedule parentrunner java at org junit runners parentrunner runchildren parentrunner java at org junit runners parentrunner access parentrunner java at org junit runners parentrunner evaluate parentrunner java at org junit runners parentrunner evaluate parentrunner java at org junit runners parentrunner run parentrunner java at org apache maven surefire execute java at org apache maven surefire executewithrerun java at org apache maven surefire executetestset java at org apache maven surefire invoke java at org apache maven surefire booter forkedbooter runsuitesinprocess forkedbooter java at org apache maven surefire booter forkedbooter execute forkedbooter java at org apache maven surefire booter forkedbooter run forkedbooter java at org apache maven surefire booter forkedbooter main forkedbooter java caused by io grpc statusruntimeexception internal encountered unexpected server errors please try again later request id for tracking at io grpc status asruntimeexception status java more | 0 |
25,484 | 3,933,127,800 | IssuesEvent | 2016-04-25 18:04:05 | mozilla/science.mozilla.org | https://api.github.com/repos/mozilla/science.mozilla.org | closed | Comps for Blog | design Epic | - [x] Individual page
- [x] List view of all blogs
Use Onesie! This should be generic enough to apply to other blogs.
**Individual Post**
Each post, no matter what site it lives on, will have...
* Title
* Date and time published & updated
* Author (and link to posts by that author)
* Full text
* List of tags (each linked to related articles)
* List of categories that it belongs to (each linked to category views)
* Discussion & comments section
* Social buttons? Share on Twitter, Fb, etc?
**List View**
Search field
Paginated list, ordered by reverse chron
* Hyperlinked title
* Date and time published/updated
* Author
* Truncated text | 1.0 | Comps for Blog - - [x] Individual page
- [x] List view of all blogs
Use Onesie! This should be generic enough to apply to other blogs.
**Individual Post**
Each post, no matter what site it lives on, will have...
* Title
* Date and time published & updated
* Author (and link to posts by that author)
* Full text
* List of tags (each linked to related articles)
* List of categories that it belongs to (each linked to category views)
* Discussion & comments section
* Social buttons? Share on Twitter, Fb, etc?
**List View**
Search field
Paginated list, ordered by reverse chron
* Hyperlinked title
* Date and time published/updated
* Author
* Truncated text | non_process | comps for blog individual page list view of all blogs use onesie this should be generic enough to apply to other blogs individual post each post no matter what site it lives on will have title date and time published updated author and link to posts by that author full text list of tags each linked to related articles list of categories that it belongs to each linked to category views discussion comments section social buttons share on twitter fb etc list view search field paginated list ordered by reverse chron hyperlinked title date and time published updated author truncated text | 0 |
162,299 | 20,178,667,886 | IssuesEvent | 2022-02-10 16:27:06 | vital-ws/empty | https://api.github.com/repos/vital-ws/empty | opened | CVE-2022-22816 (High) detected in Pillow-8.3.2-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | security vulnerability | ## CVE-2022-22816 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>Pillow-8.3.2-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl</b></p></summary>
<p>Python Imaging Library (Fork)</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/41/07/ecb2a0d55460385163c82a4bd65263a00510966dddbd54876796bd18857c/Pillow-8.3.2-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl">https://files.pythonhosted.org/packages/41/07/ecb2a0d55460385163c82a4bd65263a00510966dddbd54876796bd18857c/Pillow-8.3.2-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- PyAutoGUI-0.9.50.tar.gz (Root Library)
- MouseInfo-0.1.3.tar.gz
- :x: **Pillow-8.3.2-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vital-ws/empty/commit/a22b0de94d5c4e9c141f2b7c59bdf4ec92aee8b5">a22b0de94d5c4e9c141f2b7c59bdf4ec92aee8b5</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
path_getbbox in path.c in Pillow before 9.0.0 has a buffer over-read during initialization of ImagePath.Path.
<p>Publish Date: 2022-01-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22816>CVE-2022-22816</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-22816">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-22816</a></p>
<p>Release Date: 2022-01-10</p>
<p>Fix Resolution: Pillow - 9.0.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Python","packageName":"Pillow","packageVersion":"8.3.2","packageFilePaths":["/requirements.txt"],"isTransitiveDependency":true,"dependencyTree":"PyAutoGUI:0.9.50;MouseInfo:0.1.3;Pillow:8.3.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"Pillow - 9.0.0","isBinary":false}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2022-22816","vulnerabilityDetails":"path_getbbox in path.c in Pillow before 9.0.0 has a buffer over-read during initialization of ImagePath.Path.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22816","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2022-22816 (High) detected in Pillow-8.3.2-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl - ## CVE-2022-22816 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>Pillow-8.3.2-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl</b></p></summary>
<p>Python Imaging Library (Fork)</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/41/07/ecb2a0d55460385163c82a4bd65263a00510966dddbd54876796bd18857c/Pillow-8.3.2-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl">https://files.pythonhosted.org/packages/41/07/ecb2a0d55460385163c82a4bd65263a00510966dddbd54876796bd18857c/Pillow-8.3.2-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- PyAutoGUI-0.9.50.tar.gz (Root Library)
- MouseInfo-0.1.3.tar.gz
- :x: **Pillow-8.3.2-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vital-ws/empty/commit/a22b0de94d5c4e9c141f2b7c59bdf4ec92aee8b5">a22b0de94d5c4e9c141f2b7c59bdf4ec92aee8b5</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
path_getbbox in path.c in Pillow before 9.0.0 has a buffer over-read during initialization of ImagePath.Path.
<p>Publish Date: 2022-01-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22816>CVE-2022-22816</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-22816">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-22816</a></p>
<p>Release Date: 2022-01-10</p>
<p>Fix Resolution: Pillow - 9.0.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Python","packageName":"Pillow","packageVersion":"8.3.2","packageFilePaths":["/requirements.txt"],"isTransitiveDependency":true,"dependencyTree":"PyAutoGUI:0.9.50;MouseInfo:0.1.3;Pillow:8.3.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"Pillow - 9.0.0","isBinary":false}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2022-22816","vulnerabilityDetails":"path_getbbox in path.c in Pillow before 9.0.0 has a buffer over-read during initialization of ImagePath.Path.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22816","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_process | cve high detected in pillow manylinux whl cve high severity vulnerability vulnerable library pillow manylinux whl python imaging library fork library home page a href path to dependency file requirements txt path to vulnerable library requirements txt dependency hierarchy pyautogui tar gz root library mouseinfo tar gz x pillow manylinux whl vulnerable library found in head commit a href found in base branch main vulnerability details path getbbox in path c in pillow before has a buffer over read during initialization of imagepath path publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution pillow isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree pyautogui mouseinfo pillow isminimumfixversionavailable true minimumfixversion pillow isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails path getbbox in path c in pillow before has a buffer over read during initialization of imagepath path vulnerabilityurl | 0 |
75,677 | 9,308,559,213 | IssuesEvent | 2019-03-25 14:47:37 | iov-one/weave | https://api.github.com/repos/iov-one/weave | closed | Move `Memo` and `ChainID` to top level Tx codec | design | **Is your feature request related to a problem? Please describe.**
* `Memo` - is a free text field that can be used to submit extra information by the sender
* `ChainID` - is the name of the blockchain and used to prevent replay attacks
We should be on the safe side with replay attacks on all our messages. We should also enable custom metadata with every message to allow use cases that we have not planned for.
**Describe the solution you'd like**
By moving both fields to the top level Tx of [bns](https://github.com/iov-one/weave/blob/master/cmd/bnsd/app/codec.proto#L25) and [bcp](https://github.com/iov-one/weave/blob/master/cmd/bcpd/app/codec.proto#L22) we can achieve this with very small changes. The field validation should not be hard to integrate into the new [validation logic](https://github.com/iov-one/weave/issues/434).
**Describe alternatives you've considered**
Validation can also be done in a decorator to exit fast.
| 1.0 | Move `Memo` and `ChainID` to top level Tx codec - **Is your feature request related to a problem? Please describe.**
* `Memo` - is a free text field that can be used to submit extra information by the sender
* `ChainID` - is the name of the blockchain and used to prevent replay attacks
We should be on the safe side with replay attacks on all our messages. We should also enable custom metadata with every message to allow use cases that we have not planned for.
**Describe the solution you'd like**
By moving both fields to the top level Tx of [bns](https://github.com/iov-one/weave/blob/master/cmd/bnsd/app/codec.proto#L25) and [bcp](https://github.com/iov-one/weave/blob/master/cmd/bcpd/app/codec.proto#L22) we can achieve this with very small changes. The field validation should not be hard to integrate into the new [validation logic](https://github.com/iov-one/weave/issues/434).
**Describe alternatives you've considered**
Validation can also be done in a decorator to exit fast.
| non_process | move memo and chainid to top level tx codec is your feature request related to a problem please describe memo is a free text field that can be used to submit extra information by the sender chainid is the name of the blockchain and used to prevent replay attacks we should be on the safe side with replay attacks on all our messages we should also enable custom metadata with every message to allow use cases that we have not planned for describe the solution you d like by moving both fields to the top level tx of and we can achieve this with very small changes the field validation should not be hard to integrate into the new describe alternatives you ve considered validation can also be done in a decorator to exit fast | 0 |
41,644 | 10,552,668,312 | IssuesEvent | 2019-10-03 15:35:29 | jOOQ/jOOQ | https://api.github.com/repos/jOOQ/jOOQ | opened | Codegen throw NoClassDefFoundError on org/reactivestreams/Publisher | T: Defect | ### Expected behavior and actual behavior:
Expected behaviour would be the same as in the tutorial for jooq, as seen here:
https://www.jooq.org/doc/3.12/manual/getting-started/tutorials/jooq-in-7-steps/jooq-in-7-steps-step3/
ONLY difference is that I am using `mysql-connector-java-8.0.17.jar` instead of the bin. I have no idea where to get that bin from, so I am using the latest jar.
The output in cmd:
```bash
Okt 03, 2019 5:26:19 PM org.jooq.tools.JooqLogger info
INFORMATION: Initialising properties : library.xml
Okt 03, 2019 5:26:22 PM org.jooq.tools.JooqLogger info
INFORMATION: No <inputCatalog/> was provided. Generating ALL available catalogs instead.
Exception in thread "main" java.lang.NoClassDefFoundError: org/reactivestreams/Publisher
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.access$100(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at org.jooq.impl.DSL.using(DSL.java:601)
at org.jooq.meta.mysql.MySQLDatabase.create0(MySQLDatabase.java:527)
at org.jooq.meta.AbstractDatabase.create(AbstractDatabase.java:260)
at org.jooq.meta.AbstractDatabase.create(AbstractDatabase.java:249)
at org.jooq.meta.AbstractDatabase.setConnection(AbstractDatabase.java:239)
at org.jooq.codegen.GenerationTool.run0(GenerationTool.java:501)
at org.jooq.codegen.GenerationTool.run(GenerationTool.java:221)
at org.jooq.codegen.GenerationTool.generate(GenerationTool.java:216)
at org.jooq.codegen.GenerationTool.main(GenerationTool.java:188)
Caused by: java.lang.ClassNotFoundException: org.reactivestreams.Publisher
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
```
### Steps to reproduce the problem (if possible, create an MCVE:
Setup a project with a folder like in the tutorial, use `mysql-connector-java-8.0.17.jar`, call the command:
java -classpath jooq-3.12.1.jar;^
jooq-meta-3.12.1.jar;^
jooq-codegen-3.12.1.jar;^
mysql-connector-java-8.0.17.jar;. ^
org.jooq.codegen.GenerationTool library.xml
### Versions:
- jOOQ: 3.12.1
- Java: 1.8.0_202
- Database (include vendor): MySQL
- OS: Windows 10
- JDBC Driver (include name if inofficial driver):
| 1.0 | Codegen throw NoClassDefFoundError on org/reactivestreams/Publisher - ### Expected behavior and actual behavior:
Expected behaviour would be the same as in the tutorial for jooq, as seen here:
https://www.jooq.org/doc/3.12/manual/getting-started/tutorials/jooq-in-7-steps/jooq-in-7-steps-step3/
ONLY difference is that I am using `mysql-connector-java-8.0.17.jar` instead of the bin. I have no idea where to get that bin from, so I am using the latest jar.
The output in cmd:
```bash
Okt 03, 2019 5:26:19 PM org.jooq.tools.JooqLogger info
INFORMATION: Initialising properties : library.xml
Okt 03, 2019 5:26:22 PM org.jooq.tools.JooqLogger info
INFORMATION: No <inputCatalog/> was provided. Generating ALL available catalogs instead.
Exception in thread "main" java.lang.NoClassDefFoundError: org/reactivestreams/Publisher
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.access$100(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at org.jooq.impl.DSL.using(DSL.java:601)
at org.jooq.meta.mysql.MySQLDatabase.create0(MySQLDatabase.java:527)
at org.jooq.meta.AbstractDatabase.create(AbstractDatabase.java:260)
at org.jooq.meta.AbstractDatabase.create(AbstractDatabase.java:249)
at org.jooq.meta.AbstractDatabase.setConnection(AbstractDatabase.java:239)
at org.jooq.codegen.GenerationTool.run0(GenerationTool.java:501)
at org.jooq.codegen.GenerationTool.run(GenerationTool.java:221)
at org.jooq.codegen.GenerationTool.generate(GenerationTool.java:216)
at org.jooq.codegen.GenerationTool.main(GenerationTool.java:188)
Caused by: java.lang.ClassNotFoundException: org.reactivestreams.Publisher
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
```
### Steps to reproduce the problem (if possible, create an MCVE:
Setup a project with a folder like in the tutorial, use `mysql-connector-java-8.0.17.jar`, call the command:
java -classpath jooq-3.12.1.jar;^
jooq-meta-3.12.1.jar;^
jooq-codegen-3.12.1.jar;^
mysql-connector-java-8.0.17.jar;. ^
org.jooq.codegen.GenerationTool library.xml
### Versions:
- jOOQ: 3.12.1
- Java: 1.8.0_202
- Database (include vendor): MySQL
- OS: Windows 10
- JDBC Driver (include name if inofficial driver):
| non_process | codegen throw noclassdeffounderror on org reactivestreams publisher expected behavior and actual behavior expected behaviour would be the same as in the tutorial for jooq as seen here only difference is that i am using mysql connector java jar instead of the bin i have no idea where to get that bin from so i am using the latest jar the output in cmd bash okt pm org jooq tools jooqlogger info information initialising properties library xml okt pm org jooq tools jooqlogger info information no was provided generating all available catalogs instead exception in thread main java lang noclassdeffounderror org reactivestreams publisher at java lang classloader native method at java lang classloader defineclass unknown source at java security secureclassloader defineclass unknown source at java net urlclassloader defineclass unknown source at java net urlclassloader access unknown source at java net urlclassloader run unknown source at java net urlclassloader run unknown source at java security accesscontroller doprivileged native method at java net urlclassloader findclass unknown source at java lang classloader loadclass unknown source at sun misc launcher appclassloader loadclass unknown source at java lang classloader loadclass unknown source at org jooq impl dsl using dsl java at org jooq meta mysql mysqldatabase mysqldatabase java at org jooq meta abstractdatabase create abstractdatabase java at org jooq meta abstractdatabase create abstractdatabase java at org jooq meta abstractdatabase setconnection abstractdatabase java at org jooq codegen generationtool generationtool java at org jooq codegen generationtool run generationtool java at org jooq codegen generationtool generate generationtool java at org jooq codegen generationtool main generationtool java caused by java lang classnotfoundexception org reactivestreams publisher at java net urlclassloader findclass unknown source at java lang classloader loadclass unknown source at sun misc launcher appclassloader loadclass unknown source at java lang classloader loadclass unknown source steps to reproduce the problem if possible create an mcve setup a project with a folder like in the tutorial use mysql connector java jar call the command java classpath jooq jar jooq meta jar jooq codegen jar mysql connector java jar org jooq codegen generationtool library xml versions jooq java database include vendor mysql os windows jdbc driver include name if inofficial driver | 0 |
18,345 | 24,467,582,590 | IssuesEvent | 2022-10-07 16:23:21 | bondaleksey/credit-card-fraud-detection | https://api.github.com/repos/bondaleksey/credit-card-fraud-detection | opened | data preprocessing | work plan data preprocessing | - data cleaning, transformation, feature engineering,
- save results to HDFS,
- automate regular data preprocessing with AirFlow. | 1.0 | data preprocessing - - data cleaning, transformation, feature engineering,
- save results to HDFS,
- automate regular data preprocessing with AirFlow. | process | data preprocessing data cleaning transformation feature engineering save results to hdfs automate regular data preprocessing with airflow | 1 |
13,605 | 16,191,040,327 | IssuesEvent | 2021-05-04 08:31:43 | e4exp/paper_manager_abstract | https://api.github.com/repos/e4exp/paper_manager_abstract | opened | Entailment as Few-Shot Learner | 2021 Few Shot Learning Language Model Natural Language Processing |
事前に学習された大規模な言語モデル（LM）は，少数の学習者として優れた能力を発揮します．
しかし、その成功は、モデルのパラメータのスケーリングに大きく依存しているため、学習やサービスの提供が困難になっています。
この論文では、EFLと呼ばれる新しいアプローチを提案します。
このアプローチは、小さなLMをより優れた少数決学習者に変えることができます。
このアプローチの鍵となるアイデアは、潜在的なNLPタスクを関連性のあるタスクに再定式化し、わずか8つの例でモデルを微調整することである。
さらに、我々の提案する手法が以下のことを可能にすることを実証する。
さらに、我々の提案する手法は、
(i)教師なしの対照学習に基づくデータ増強法と自然に組み合わせることができる、
(ii)多言語の少数ショット学習に容易に拡張できる、ということを実証する。
18の標準的なNLPタスクを対象とした系統的な評価により、本手法は、既存のSOTA少数ショット学習法を12%改善し、GPT-3のような500倍の規模のモデルに匹敵する少数ショット性能を得ることができる。
| 1.0 | Entailment as Few-Shot Learner -
事前に学習された大規模な言語モデル（LM）は，少数の学習者として優れた能力を発揮します．
しかし、その成功は、モデルのパラメータのスケーリングに大きく依存しているため、学習やサービスの提供が困難になっています。
この論文では、EFLと呼ばれる新しいアプローチを提案します。
このアプローチは、小さなLMをより優れた少数決学習者に変えることができます。
このアプローチの鍵となるアイデアは、潜在的なNLPタスクを関連性のあるタスクに再定式化し、わずか8つの例でモデルを微調整することである。
さらに、我々の提案する手法が以下のことを可能にすることを実証する。
さらに、我々の提案する手法は、
(i)教師なしの対照学習に基づくデータ増強法と自然に組み合わせることができる、
(ii)多言語の少数ショット学習に容易に拡張できる、ということを実証する。
18の標準的なNLPタスクを対象とした系統的な評価により、本手法は、既存のSOTA少数ショット学習法を12%改善し、GPT-3のような500倍の規模のモデルに匹敵する少数ショット性能を得ることができる。
| process | entailment as few shot learner 事前に学習された大規模な言語モデル（lm）は，少数の学習者として優れた能力を発揮します． しかし、その成功は、モデルのパラメータのスケーリングに大きく依存しているため、学習やサービスの提供が困難になっています。 この論文では、eflと呼ばれる新しいアプローチを提案します。 このアプローチは、小さなlmをより優れた少数決学習者に変えることができます。 このアプローチの鍵となるアイデアは、潜在的なnlpタスクを関連性のあるタスクに再定式化し、 。 さらに、我々の提案する手法が以下のことを可能にすることを実証する。 さらに、我々の提案する手法は、 i 教師なしの対照学習に基づくデータ増強法と自然に組み合わせることができる、 ii 多言語の少数ショット学習に容易に拡張できる、ということを実証する。 、本手法は、 改善し、gpt 。 | 1 |
199,950 | 15,084,025,110 | IssuesEvent | 2021-02-05 16:36:09 | phetsims/isotopes-and-atomic-mass | https://api.github.com/repos/phetsims/isotopes-and-atomic-mass | opened | CT cannot read property globalToLocalPoint of undefined | type:automated-testing | ```
isotopes-and-atomic-mass : multitouch-fuzz : unbuilt
https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/isotopes-and-atomic-mass/isotopes-and-atomic-mass_en.html?continuousTest=%7B%22test%22%3A%5B%22isotopes-and-atomic-mass%22%2C%22multitouch-fuzz%22%2C%22unbuilt%22%5D%2C%22snapshotName%22%3A%22snapshot-1612485936684%22%2C%22timestamp%22%3A1612492121665%7D&brand=phet&ea&fuzz&fuzzPointers=2&memoryLimit=1000
Query: brand=phet&ea&fuzz&fuzzPointers=2&memoryLimit=1000
Uncaught TypeError: Cannot read property 'globalToLocalPoint' of undefined
TypeError: Cannot read property 'globalToLocalPoint' of undefined
at localViewToModel (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/shred/js/view/BucketDragListener.js:38:37)
at BucketDragListener.drag [as _dragListener] (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/shred/js/view/BucketDragListener.js:57:53)
at BucketDragListener.drag (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/scenery/js/listeners/PressListener.js:446:10)
at DragListener._dragAction.Action.parameters.name (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/scenery/js/listeners/DragListener.js:244:36)
at Action.execute (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/axon/js/Action.js:225:18)
at BucketDragListener.drag (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/scenery/js/listeners/DragListener.js:363:22)
at BucketDragListener.pointerMove (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/scenery/js/listeners/PressListener.js:809:14)
at Input.dispatchToListeners (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/scenery/js/input/Input.js:1832:25)
at Input.dispatchEvent (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/scenery/js/input/Input.js:1781:10)
at Input.branchChangeEvents (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/scenery/js/input/Input.js:1681:12)
id: Bayes Chrome
Snapshot from 2/4/2021, 5:45:36 PM
``` | 1.0 | CT cannot read property globalToLocalPoint of undefined - ```
isotopes-and-atomic-mass : multitouch-fuzz : unbuilt
https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/isotopes-and-atomic-mass/isotopes-and-atomic-mass_en.html?continuousTest=%7B%22test%22%3A%5B%22isotopes-and-atomic-mass%22%2C%22multitouch-fuzz%22%2C%22unbuilt%22%5D%2C%22snapshotName%22%3A%22snapshot-1612485936684%22%2C%22timestamp%22%3A1612492121665%7D&brand=phet&ea&fuzz&fuzzPointers=2&memoryLimit=1000
Query: brand=phet&ea&fuzz&fuzzPointers=2&memoryLimit=1000
Uncaught TypeError: Cannot read property 'globalToLocalPoint' of undefined
TypeError: Cannot read property 'globalToLocalPoint' of undefined
at localViewToModel (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/shred/js/view/BucketDragListener.js:38:37)
at BucketDragListener.drag [as _dragListener] (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/shred/js/view/BucketDragListener.js:57:53)
at BucketDragListener.drag (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/scenery/js/listeners/PressListener.js:446:10)
at DragListener._dragAction.Action.parameters.name (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/scenery/js/listeners/DragListener.js:244:36)
at Action.execute (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/axon/js/Action.js:225:18)
at BucketDragListener.drag (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/scenery/js/listeners/DragListener.js:363:22)
at BucketDragListener.pointerMove (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/scenery/js/listeners/PressListener.js:809:14)
at Input.dispatchToListeners (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/scenery/js/input/Input.js:1832:25)
at Input.dispatchEvent (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/scenery/js/input/Input.js:1781:10)
at Input.branchChangeEvents (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1612485936684/scenery/js/input/Input.js:1681:12)
id: Bayes Chrome
Snapshot from 2/4/2021, 5:45:36 PM
``` | non_process | ct cannot read property globaltolocalpoint of undefined isotopes and atomic mass multitouch fuzz unbuilt query brand phet ea fuzz fuzzpointers memorylimit uncaught typeerror cannot read property globaltolocalpoint of undefined typeerror cannot read property globaltolocalpoint of undefined at localviewtomodel at bucketdraglistener drag at bucketdraglistener drag at draglistener dragaction action parameters name at action execute at bucketdraglistener drag at bucketdraglistener pointermove at input dispatchtolisteners at input dispatchevent at input branchchangeevents id bayes chrome snapshot from pm | 0 |
352,120 | 25,048,033,099 | IssuesEvent | 2022-11-05 14:15:32 | vuetifyjs/vuetify | https://api.github.com/repos/vuetifyjs/vuetify | closed | [Documentation] `Invert Example Color` not working when Dark/System Followed Theme is Enabled | T: documentation | ### Environment
**Browsers:** Chrome 107.0.0.0
**OS:** Mac OS 10.15.7
### Steps to reproduce
Open any component page and Select either one of the following theme from Site settings
1. Dark
2. System
In case of any of above theme, the `Invert Example Color` button on the component preview will not work.
### Expected Behavior
In Dark / System theme mode, the dark themed components should be viewable with light theme with above mentioned toggle, which is not the case.
when same is done on light theme, the toggle works as expected
### Actual Behavior
When Dark / System theme is selected, the `Invert Example Color` toggle should let user toggle the theme of the component
### Reproduction Link
[https://vuetifyjs.com/en/components/expansion-panels/#advanced](https://vuetifyjs.com/en/components/expansion-panels/#advanced)
### Other comments
Video Demonstrating the same bug:
https://www.loom.com/share/61fc8b05968b4a23aaa3f282bf462568
<!-- generated by vuetify-issue-helper. DO NOT REMOVE --> | 1.0 | [Documentation] `Invert Example Color` not working when Dark/System Followed Theme is Enabled - ### Environment
**Browsers:** Chrome 107.0.0.0
**OS:** Mac OS 10.15.7
### Steps to reproduce
Open any component page and Select either one of the following theme from Site settings
1. Dark
2. System
In case of any of above theme, the `Invert Example Color` button on the component preview will not work.
### Expected Behavior
In Dark / System theme mode, the dark themed components should be viewable with light theme with above mentioned toggle, which is not the case.
when same is done on light theme, the toggle works as expected
### Actual Behavior
When Dark / System theme is selected, the `Invert Example Color` toggle should let user toggle the theme of the component
### Reproduction Link
[https://vuetifyjs.com/en/components/expansion-panels/#advanced](https://vuetifyjs.com/en/components/expansion-panels/#advanced)
### Other comments
Video Demonstrating the same bug:
https://www.loom.com/share/61fc8b05968b4a23aaa3f282bf462568
<!-- generated by vuetify-issue-helper. DO NOT REMOVE --> | non_process | invert example color not working when dark system followed theme is enabled environment browsers chrome os mac os steps to reproduce open any component page and select either one of the following theme from site settings dark system in case of any of above theme the invert example color button on the component preview will not work expected behavior in dark system theme mode the dark themed components should be viewable with light theme with above mentioned toggle which is not the case when same is done on light theme the toggle works as expected actual behavior when dark system theme is selected the invert example color toggle should let user toggle the theme of the component reproduction link other comments video demonstrating the same bug | 0 |
8,258 | 11,424,941,665 | IssuesEvent | 2020-02-03 18:48:24 | kubeflow/manifests | https://api.github.com/repos/kubeflow/manifests | closed | Update Metadata Docker images for Kubeflow 1.0? | area/metadata kind/process priority/p0 | Do we need to update the docker images used by metadata for 1.0 or are the images in
https://github.com/kubeflow/manifests/blob/master/metadata/base/kustomization.yaml
Up to date.
Once kubeflow/testing#587 we should be able to just add the requisite specs to that file to auto-build and update the docker images used by metadata.
/assign @zhenghuiwang
/cc @avdaredevil | 1.0 | Update Metadata Docker images for Kubeflow 1.0? - Do we need to update the docker images used by metadata for 1.0 or are the images in
https://github.com/kubeflow/manifests/blob/master/metadata/base/kustomization.yaml
Up to date.
Once kubeflow/testing#587 we should be able to just add the requisite specs to that file to auto-build and update the docker images used by metadata.
/assign @zhenghuiwang
/cc @avdaredevil | process | update metadata docker images for kubeflow do we need to update the docker images used by metadata for or are the images in up to date once kubeflow testing we should be able to just add the requisite specs to that file to auto build and update the docker images used by metadata assign zhenghuiwang cc avdaredevil | 1 |
5,353 | 8,180,316,187 | IssuesEvent | 2018-08-28 19:04:27 | yvesgoeleven/BasketLummen | https://api.github.com/repos/yvesgoeleven/BasketLummen | closed | Document Issue Tracking process | Size: M State: Backlog Type: Process Improvement | ## What is the problem?
Need to keep track of things to do, describe what problems are solved and how to approach them. Guidance is needed to learn how to maintain these issues over time.
## Discussion and conclusions
## Plan of attack
- [ ] Write document that describes the process | 1.0 | Document Issue Tracking process - ## What is the problem?
Need to keep track of things to do, describe what problems are solved and how to approach them. Guidance is needed to learn how to maintain these issues over time.
## Discussion and conclusions
## Plan of attack
- [ ] Write document that describes the process | process | document issue tracking process what is the problem need to keep track of things to do describe what problems are solved and how to approach them guidance is needed to learn how to maintain these issues over time discussion and conclusions plan of attack write document that describes the process | 1 |
163,639 | 25,851,324,250 | IssuesEvent | 2022-12-13 10:35:11 | atteneder/glTFast | https://api.github.com/repos/atteneder/glTFast | opened | Inconsistent Image Resolution | bug export design-time | When exporting to glTF from the Editor, sometimes the original texture (resolution) is exported and sometimes the texture import settings' Max Size resolution is used.
A first look showed that whether the original texture file is used (or the texture is re-encoded with a different size and format) can depend on whether the original format aligns with the desired output format (e.g. PNG to Jpeg conversion).
As a user, I might want to decide whether to
- Always stick to the original (format, resolution, color space?)
- Always use the overridden settings (to align with what an asset bundle export would produce)
But not a random mixture.
Runtime export is not affected.
- glTFast 5.0.0
- Unity Editor 2019
- Render Pipeline and version BiRP
- Platform: macOS | 1.0 | Inconsistent Image Resolution - When exporting to glTF from the Editor, sometimes the original texture (resolution) is exported and sometimes the texture import settings' Max Size resolution is used.
A first look showed that whether the original texture file is used (or the texture is re-encoded with a different size and format) can depend on whether the original format aligns with the desired output format (e.g. PNG to Jpeg conversion).
As a user, I might want to decide whether to
- Always stick to the original (format, resolution, color space?)
- Always use the overridden settings (to align with what an asset bundle export would produce)
But not a random mixture.
Runtime export is not affected.
- glTFast 5.0.0
- Unity Editor 2019
- Render Pipeline and version BiRP
- Platform: macOS | non_process | inconsistent image resolution when exporting to gltf from the editor sometimes the original texture resolution is exported and sometimes the texture import settings max size resolution is used a first look showed that whether the original texture file is used or the texture is re encoded with a different size and format can depend on whether the original format aligns with the desired output format e g png to jpeg conversion as a user i might want to decide whether to always stick to the original format resolution color space always use the overridden settings to align with what an asset bundle export would produce but not a random mixture runtime export is not affected gltfast unity editor render pipeline and version birp platform macos | 0 |
20,023 | 26,502,085,012 | IssuesEvent | 2023-01-18 11:03:02 | geneontology/go-ontology | https://api.github.com/repos/geneontology/go-ontology | closed | GO:0048478 replication fork protection | cell cycle and DNA processes obsoletion ready | GO:0048478 replication fork protection
This is currently a "regulation of process" term, based on parentage.
Really it's more like a collection of things including "replication restart" and "processing of collapsed replication forks"
Chatting with @pgaudet we thought this term, based on its position, and meaning, should probably be obsoleted.
30 EXP annotation
10 PomBase
10 SGD
7 UniProt
1 FlyBase
1 MGI
1 Complex Portal
For replacement consider:
GO:0031297 replication fork processing
or some other DNA metabolism term
Note that "replication fork protection complex" is unaffected
| 1.0 | GO:0048478 replication fork protection - GO:0048478 replication fork protection
This is currently a "regulation of process" term, based on parentage.
Really it's more like a collection of things including "replication restart" and "processing of collapsed replication forks"
Chatting with @pgaudet we thought this term, based on its position, and meaning, should probably be obsoleted.
30 EXP annotation
10 PomBase
10 SGD
7 UniProt
1 FlyBase
1 MGI
1 Complex Portal
For replacement consider:
GO:0031297 replication fork processing
or some other DNA metabolism term
Note that "replication fork protection complex" is unaffected
| process | go replication fork protection go replication fork protection this is currently a regulation of process term based on parentage really it s more like a collection of things including replication restart and processing of collapsed replication forks chatting with pgaudet we thought this term based on its position and meaning should probably be obsoleted exp annotation pombase sgd uniprot flybase mgi complex portal for replacement consider go replication fork processing or some other dna metabolism term note that replication fork protection complex is unaffected | 1 |
28,391 | 13,653,505,386 | IssuesEvent | 2020-09-27 13:05:45 | comunica/comunica | https://api.github.com/repos/comunica/comunica | closed | TEMP: This is a test issue | performance 🐌 | #### Issue type:
- :bug: Bug <!--Don't change this issue type!-->
____
#### Description:
Test issue
____
#### Environment:
<!--Output of the `comunica-sparql -v` command.-->
<!--If running in a development environment, this must be the output of `node ./packages/actor-init-sparql/bin/query.js -v`-->
#### Crash log:
<!--Only required for crashes.-->
<!--Don't paste contents here directly, but use something like http://pastebin.com/-->
| True | TEMP: This is a test issue - #### Issue type:
- :bug: Bug <!--Don't change this issue type!-->
____
#### Description:
Test issue
____
#### Environment:
<!--Output of the `comunica-sparql -v` command.-->
<!--If running in a development environment, this must be the output of `node ./packages/actor-init-sparql/bin/query.js -v`-->
#### Crash log:
<!--Only required for crashes.-->
<!--Don't paste contents here directly, but use something like http://pastebin.com/-->
| non_process | temp this is a test issue issue type bug bug description test issue environment crash log don t paste contents here directly but use something like | 0 |
359,516 | 25,242,144,516 | IssuesEvent | 2022-11-15 08:24:47 | confused-Techie/atom-backend | https://api.github.com/repos/confused-Techie/atom-backend | opened | Track Tests Against API Endpoints | documentation | This issue serves to track what endpoints have enough tests to consider complete written for them.
While more tests on a completed endpoint is never a bad thing, this can help use semi-determine the stability of the overall application, since these tests are full integration tests of the whole codebase.
* [ ] GET `/`
* [ ] GET ` /api/login`
* [ ] GET `/api/oauth`
* [ ] GET `/api/packages`
* [ ] POST `/api/packages`
* [ ] GET `/api/packages/featured`
* [ ] GET `/api/packages/search`
* [ ] GET `/api/packages/:packageName`
* [ ] DELETE `/api/packages/:packageName`
* [ ] POST `/api/packages/:packageName/star`
* [ ] DELETE `/api/packages/:packageName/star`
* [ ] GET `/api/packages/:packageName/stargazers`
* [ ] POST `/api/packages/:packageName/versions`
* [ ] GET `/api/packages/:packageName/versions/:versionName`
* [ ] GET `/api/packages/:packageName/versions/:versionName/tarball`
* [ ] DELETE `/api/packages/:packageName/versions/:versionName`
* [ ] POST `/api/packages/:packageName/versions/:versionName/events/uninstall`
* [ ] GET `/api/themes/featured`
* [ ] GET `/api/users/:login/stars`
* [ ] GET `/api/stars`
* [ ] GET `/api/updates` | 1.0 | Track Tests Against API Endpoints - This issue serves to track what endpoints have enough tests to consider complete written for them.
While more tests on a completed endpoint is never a bad thing, this can help use semi-determine the stability of the overall application, since these tests are full integration tests of the whole codebase.
* [ ] GET `/`
* [ ] GET ` /api/login`
* [ ] GET `/api/oauth`
* [ ] GET `/api/packages`
* [ ] POST `/api/packages`
* [ ] GET `/api/packages/featured`
* [ ] GET `/api/packages/search`
* [ ] GET `/api/packages/:packageName`
* [ ] DELETE `/api/packages/:packageName`
* [ ] POST `/api/packages/:packageName/star`
* [ ] DELETE `/api/packages/:packageName/star`
* [ ] GET `/api/packages/:packageName/stargazers`
* [ ] POST `/api/packages/:packageName/versions`
* [ ] GET `/api/packages/:packageName/versions/:versionName`
* [ ] GET `/api/packages/:packageName/versions/:versionName/tarball`
* [ ] DELETE `/api/packages/:packageName/versions/:versionName`
* [ ] POST `/api/packages/:packageName/versions/:versionName/events/uninstall`
* [ ] GET `/api/themes/featured`
* [ ] GET `/api/users/:login/stars`
* [ ] GET `/api/stars`
* [ ] GET `/api/updates` | non_process | track tests against api endpoints this issue serves to track what endpoints have enough tests to consider complete written for them while more tests on a completed endpoint is never a bad thing this can help use semi determine the stability of the overall application since these tests are full integration tests of the whole codebase get get api login get api oauth get api packages post api packages get api packages featured get api packages search get api packages packagename delete api packages packagename post api packages packagename star delete api packages packagename star get api packages packagename stargazers post api packages packagename versions get api packages packagename versions versionname get api packages packagename versions versionname tarball delete api packages packagename versions versionname post api packages packagename versions versionname events uninstall get api themes featured get api users login stars get api stars get api updates | 0 |
14,397 | 17,409,170,404 | IssuesEvent | 2021-08-03 10:01:33 | ESMValGroup/ESMValCore | https://api.github.com/repos/ESMValGroup/ESMValCore | closed | Remove os.walk from datafinder | preprocessor question | We are currently use to find data files python`os.walk` function. This means that we search recursively on all folders inside the path constructed from the drs.
I have experimented some problems because of it:
- Defined correctly the rootpath in JASMIN and forgetting to setup the drs led to search in all CMIP5/6 data, meaning that ESMValTool takes ages to fail.
- Experimented some problems in our internal storage when somebody (bad practice, I now) created a nested folder with interpolated data
I don't know if anybody is using the recursivity of `os.walk` to organize its data, but if it is not the case I think we should remove it and replace it with `glob.glob` (sorry @valeriupredoi ) | 1.0 | Remove os.walk from datafinder - We are currently use to find data files python`os.walk` function. This means that we search recursively on all folders inside the path constructed from the drs.
I have experimented some problems because of it:
- Defined correctly the rootpath in JASMIN and forgetting to setup the drs led to search in all CMIP5/6 data, meaning that ESMValTool takes ages to fail.
- Experimented some problems in our internal storage when somebody (bad practice, I now) created a nested folder with interpolated data
I don't know if anybody is using the recursivity of `os.walk` to organize its data, but if it is not the case I think we should remove it and replace it with `glob.glob` (sorry @valeriupredoi ) | process | remove os walk from datafinder we are currently use to find data files python os walk function this means that we search recursively on all folders inside the path constructed from the drs i have experimented some problems because of it defined correctly the rootpath in jasmin and forgetting to setup the drs led to search in all data meaning that esmvaltool takes ages to fail experimented some problems in our internal storage when somebody bad practice i now created a nested folder with interpolated data i don t know if anybody is using the recursivity of os walk to organize its data but if it is not the case i think we should remove it and replace it with glob glob sorry valeriupredoi | 1 |
41,148 | 5,341,771,851 | IssuesEvent | 2017-02-17 04:40:51 | Gallopsled/pwntools | https://api.github.com/repos/Gallopsled/pwntools | closed | Members missing from __all__ are not documented or tested | bug testing | In any module which has an `__all__` attribute, any functions or classes not exported are ignored by Sphinx `autodoc`, and subsequently also by Sphinx `doctest`. | 1.0 | Members missing from __all__ are not documented or tested - In any module which has an `__all__` attribute, any functions or classes not exported are ignored by Sphinx `autodoc`, and subsequently also by Sphinx `doctest`. | non_process | members missing from all are not documented or tested in any module which has an all attribute any functions or classes not exported are ignored by sphinx autodoc and subsequently also by sphinx doctest | 0 |
9,429 | 12,419,041,896 | IssuesEvent | 2020-05-23 03:33:29 | MicrosoftDocs/azure-docs | https://api.github.com/repos/MicrosoftDocs/azure-docs | closed | Add information on whether the jobs are run in parallel or not | Pri1 automation/svc cxp process-automation/subsvc product-question triaged | Hi,
This page doesn't explain if a Hybrid worker can run multiple jobs at the same time or not. Could you please clarify if a single hybrid worker can run multiple jobs in parallel or not?
Thanks,
Pranav
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 3092ee3a-3c57-cc53-186b-b454e7d9d190
* Version Independent ID: 6f6b5a07-397a-98a2-6091-941244a77837
* Content: [Overview of Hybrid Runbook Worker in Azure Automation](https://docs.microsoft.com/en-us/azure/automation/automation-hybrid-runbook-worker?view=sql-server-linux-ver15)
* Content Source: [articles/automation/automation-hybrid-runbook-worker.md](https://github.com/Microsoft/azure-docs/blob/master/articles/automation/automation-hybrid-runbook-worker.md)
* Service: **automation**
* Sub-service: **process-automation**
* GitHub Login: @MGoedtel
* Microsoft Alias: **magoedte** | 1.0 | Add information on whether the jobs are run in parallel or not - Hi,
This page doesn't explain if a Hybrid worker can run multiple jobs at the same time or not. Could you please clarify if a single hybrid worker can run multiple jobs in parallel or not?
Thanks,
Pranav
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 3092ee3a-3c57-cc53-186b-b454e7d9d190
* Version Independent ID: 6f6b5a07-397a-98a2-6091-941244a77837
* Content: [Overview of Hybrid Runbook Worker in Azure Automation](https://docs.microsoft.com/en-us/azure/automation/automation-hybrid-runbook-worker?view=sql-server-linux-ver15)
* Content Source: [articles/automation/automation-hybrid-runbook-worker.md](https://github.com/Microsoft/azure-docs/blob/master/articles/automation/automation-hybrid-runbook-worker.md)
* Service: **automation**
* Sub-service: **process-automation**
* GitHub Login: @MGoedtel
* Microsoft Alias: **magoedte** | process | add information on whether the jobs are run in parallel or not hi this page doesn t explain if a hybrid worker can run multiple jobs at the same time or not could you please clarify if a single hybrid worker can run multiple jobs in parallel or not thanks pranav document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service automation sub service process automation github login mgoedtel microsoft alias magoedte | 1 |
603,954 | 18,674,605,553 | IssuesEvent | 2021-10-31 10:42:16 | AY2122S1-CS2103T-W13-3/tp | https://api.github.com/repos/AY2122S1-CS2103T-W13-3/tp | closed | [PE-D] Bug in Add Command | bug priority.High Error messages | Incorrect Input Add Command
Steps:
* Start application
* Insert the following add command taken from the User Guide Provided:
Command: `add /g poker /s 100 /e 120 /date /dur /loc /tag`
Shows Command Success, however, I think an error should be thrown for empty input.
<!--session: 1635494546453-0bb1e96c-081c-4dbb-8298-119120db3d8f-->
<!--Version: Web v3.4.1-->
-------------
Labels: `severity.High` `type.FunctionalityBug`
original: Siddharth-Sid/ped#10 | 1.0 | [PE-D] Bug in Add Command - Incorrect Input Add Command
Steps:
* Start application
* Insert the following add command taken from the User Guide Provided:
Command: `add /g poker /s 100 /e 120 /date /dur /loc /tag`
Shows Command Success, however, I think an error should be thrown for empty input.
<!--session: 1635494546453-0bb1e96c-081c-4dbb-8298-119120db3d8f-->
<!--Version: Web v3.4.1-->
-------------
Labels: `severity.High` `type.FunctionalityBug`
original: Siddharth-Sid/ped#10 | non_process | bug in add command incorrect input add command steps start application insert the following add command taken from the user guide provided command add g poker s e date dur loc tag shows command success however i think an error should be thrown for empty input labels severity high type functionalitybug original siddharth sid ped | 0 |
127,583 | 18,013,633,270 | IssuesEvent | 2021-09-16 11:33:07 | artsking/linux-4.1.15_CVE-2021-33034_withPatch | https://api.github.com/repos/artsking/linux-4.1.15_CVE-2021-33034_withPatch | closed | CVE-2019-19060 (High) detected in linux-stable-rtv4.1.33 - autoclosed | security vulnerability | ## CVE-2019-19060 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/artsking/linux-4.1.15_CVE-2021-33034_withPatch/commit/4fc3c2edc3923bcf586fc85e60262c55df0508e8">4fc3c2edc3923bcf586fc85e60262c55df0508e8</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/iio/imu/adis_buffer.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A memory leak in the adis_update_scan_mode() function in drivers/iio/imu/adis_buffer.c in the Linux kernel before 5.3.9 allows attackers to cause a denial of service (memory consumption), aka CID-ab612b1daf41.
<p>Publish Date: 2019-11-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-19060>CVE-2019-19060</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19060">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19060</a></p>
<p>Release Date: 2019-11-18</p>
<p>Fix Resolution: v5.4-rc3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2019-19060 (High) detected in linux-stable-rtv4.1.33 - autoclosed - ## CVE-2019-19060 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/artsking/linux-4.1.15_CVE-2021-33034_withPatch/commit/4fc3c2edc3923bcf586fc85e60262c55df0508e8">4fc3c2edc3923bcf586fc85e60262c55df0508e8</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/iio/imu/adis_buffer.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A memory leak in the adis_update_scan_mode() function in drivers/iio/imu/adis_buffer.c in the Linux kernel before 5.3.9 allows attackers to cause a denial of service (memory consumption), aka CID-ab612b1daf41.
<p>Publish Date: 2019-11-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-19060>CVE-2019-19060</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19060">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19060</a></p>
<p>Release Date: 2019-11-18</p>
<p>Fix Resolution: v5.4-rc3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_process | cve high detected in linux stable autoclosed cve high severity vulnerability vulnerable library linux stable julia cartwright s fork of linux stable rt git library home page a href found in head commit a href found in base branch master vulnerable source files drivers iio imu adis buffer c vulnerability details a memory leak in the adis update scan mode function in drivers iio imu adis buffer c in the linux kernel before allows attackers to cause a denial of service memory consumption aka cid publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.