Datasets:
karths
/
binary-10IQR-test

Dataset card Data Studio Files
xet
Community
1
Unnamed: 0
int64
0
832k
id
float64
2.49B
32.1B
type
stringclasses
1 value
created_at
stringlengths
19
19
repo
stringlengths
4
112
repo_url
stringlengths
33
141
action
stringclasses
3 values
title
stringlengths
1
1.02k
labels
stringlengths
4
1.54k
body
stringlengths
1
262k
index
stringclasses
17 values
text_combine
stringlengths
95
262k
label
stringclasses
2 values
text
stringlengths
96
252k
binary_label
int64
0
1
218,863
16,772,950,528
IssuesEvent
2021-06-14 16:57:51
spring-projects/spring-boot
https://api.github.com/repos/spring-projects/spring-boot
closed
Link to Jetty request log documentation is broken
status: blocked type: documentation
In section [9.3.11. Configure Access Logging](https://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#howto-configure-accesslogs) of the reference documentation the following Jetty link is broken: https://www.eclipse.org/jetty/documentation/9.4.25.v20191220/configuring-jetty-request-logs.html <!-- Thanks for raising a Spring Boot issue. Please take the time to review the following categories as some of them do not apply here. 🙅 "Please DO NOT Raise an Issue" Cases - Question STOP!! Please ask questions about how to use something, or to understand why something isn't working as you expect it to, on Stack Overflow using the spring-boot tag. - Security Vulnerability STOP!! Please don't raise security vulnerabilities here. Head over to https://pivotal.io/security to learn how to disclose them responsibly. - Managed Dependency Upgrade You DO NOT need to raise an issue for a managed dependency version upgrade as there's a semi-automatic process for checking managed dependencies for new versions before a release. BUT pull requests for upgrades that are more involved than just a version property change are still most welcome. - With an Immediate Pull Request An issue will be closed as a duplicate of the immediate pull request, so you don't have to raise an issue if you plan to create a pull request immediately. 🐞 Bug report (please don't include this emoji/text, just add your details) Please provide details of the problem, including the version of Spring Boot that you are using. If possible, please provide a test case or sample application that reproduces the problem. This makes it much easier for us to diagnose the problem and to verify that we have fixed it. 🎁 Enhancement (please don't include this emoji/text, just add your details) Please start by describing the problem that you are trying to solve. There may already be a solution, or there may be a way to solve it that you hadn't considered. TIP: You can always edit your issue if it isn't formatted correctly. See https://guides.github.com/features/mastering-markdown -->
1.0
Link to Jetty request log documentation is broken - In section [9.3.11. Configure Access Logging](https://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#howto-configure-accesslogs) of the reference documentation the following Jetty link is broken: https://www.eclipse.org/jetty/documentation/9.4.25.v20191220/configuring-jetty-request-logs.html <!-- Thanks for raising a Spring Boot issue. Please take the time to review the following categories as some of them do not apply here. 🙅 "Please DO NOT Raise an Issue" Cases - Question STOP!! Please ask questions about how to use something, or to understand why something isn't working as you expect it to, on Stack Overflow using the spring-boot tag. - Security Vulnerability STOP!! Please don't raise security vulnerabilities here. Head over to https://pivotal.io/security to learn how to disclose them responsibly. - Managed Dependency Upgrade You DO NOT need to raise an issue for a managed dependency version upgrade as there's a semi-automatic process for checking managed dependencies for new versions before a release. BUT pull requests for upgrades that are more involved than just a version property change are still most welcome. - With an Immediate Pull Request An issue will be closed as a duplicate of the immediate pull request, so you don't have to raise an issue if you plan to create a pull request immediately. 🐞 Bug report (please don't include this emoji/text, just add your details) Please provide details of the problem, including the version of Spring Boot that you are using. If possible, please provide a test case or sample application that reproduces the problem. This makes it much easier for us to diagnose the problem and to verify that we have fixed it. 🎁 Enhancement (please don't include this emoji/text, just add your details) Please start by describing the problem that you are trying to solve. There may already be a solution, or there may be a way to solve it that you hadn't considered. TIP: You can always edit your issue if it isn't formatted correctly. See https://guides.github.com/features/mastering-markdown -->
non_test
link to jetty request log documentation is broken in section of the reference documentation the following jetty link is broken thanks for raising a spring boot issue please take the time to review the following categories as some of them do not apply here 🙅 please do not raise an issue cases question stop please ask questions about how to use something or to understand why something isn t working as you expect it to on stack overflow using the spring boot tag security vulnerability stop please don t raise security vulnerabilities here head over to to learn how to disclose them responsibly managed dependency upgrade you do not need to raise an issue for a managed dependency version upgrade as there s a semi automatic process for checking managed dependencies for new versions before a release but pull requests for upgrades that are more involved than just a version property change are still most welcome with an immediate pull request an issue will be closed as a duplicate of the immediate pull request so you don t have to raise an issue if you plan to create a pull request immediately 🐞 bug report please don t include this emoji text just add your details please provide details of the problem including the version of spring boot that you are using if possible please provide a test case or sample application that reproduces the problem this makes it much easier for us to diagnose the problem and to verify that we have fixed it 🎁 enhancement please don t include this emoji text just add your details please start by describing the problem that you are trying to solve there may already be a solution or there may be a way to solve it that you hadn t considered tip you can always edit your issue if it isn t formatted correctly see
0
634,032
20,322,410,736
IssuesEvent
2022-02-18 00:34:02
comuwayit/CST438_Group4_Project01
https://api.github.com/repos/comuwayit/CST438_Group4_Project01
closed
Home Page
Top Priority
The page you arrive at when you login to your user or admin account. Should have space available for navigation or some combination of buttons to take you to different pages and a logout button. These do not have to function yet
1.0
Home Page - The page you arrive at when you login to your user or admin account. Should have space available for navigation or some combination of buttons to take you to different pages and a logout button. These do not have to function yet
non_test
home page the page you arrive at when you login to your user or admin account should have space available for navigation or some combination of buttons to take you to different pages and a logout button these do not have to function yet
0
25,567
7,726,704,776
IssuesEvent
2018-05-24 22:15:39
Microsoft/WSL
https://api.github.com/repos/Microsoft/WSL
closed
WSL resolv.conf populated with DNS servers from disconnected network
fixedininsiderbuilds
**Your Windows build number:** 10.0.16299.64 **What you're doing and what's happening:** 1. Enabled WSL, rebooted 1. Installed Ubuntu from the Store 1. Launched newly-installed Ubuntu 1. Ran a few sudo apt-get installs with no problems. 1. Left for a while, 1. Tried sudo apt-get update and unable to resolve security.ubuntu.com and archive.ubuntu.com 1. Did a bit of sleuthing 1. Ping to 8.8.8.8 works, resolving does not 1. resolv.conf has 3 DNS server entries - local firewall plus 2 servers at a client location I haven't been to for a couple weeks. 1. No active interfaces on Windows have those client servers as DNS (via ipconfig /all) 1. No interfaces that I checked (connected or disconnected) have static DNS entries at all (checking properties of the network adapters), including the Ethernet port and the disconnected SSTP VPN to that client. I did not actually check properties on all network interfaces before moving to the next step. 1. Searched the registry for one of the client site IP addresses, found it in HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\\{GUID} on the DhcpNameServer value 1. Searched the registry for the GUID, found it in HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\3 on the ServiceName value. Corresponding value for Description is "Intel(R) 82579LM Gigabit Network Connection" which would be the internal Ethernet on the laptop. Entirely feasible that the last time that was connected was at that client site, and it may have been a month or more since that time. **Special Note:** This computer was upgraded from Windows 7 Pro to Windows 10 Pro since the last time it was at that location or connected to a wired network. **What's wrong / what should be happening instead** Probably shouldn't be pulling DNS values for networks that aren't connected. Not clear exactly how it's getting the DNS server addresses, because in looking through the Interfaces section mentioned above I did find one additional name server address that was not added to resolv.conf, so I don't think it's just enumerating the interfaces from the registry.
1.0
WSL resolv.conf populated with DNS servers from disconnected network - **Your Windows build number:** 10.0.16299.64 **What you're doing and what's happening:** 1. Enabled WSL, rebooted 1. Installed Ubuntu from the Store 1. Launched newly-installed Ubuntu 1. Ran a few sudo apt-get installs with no problems. 1. Left for a while, 1. Tried sudo apt-get update and unable to resolve security.ubuntu.com and archive.ubuntu.com 1. Did a bit of sleuthing 1. Ping to 8.8.8.8 works, resolving does not 1. resolv.conf has 3 DNS server entries - local firewall plus 2 servers at a client location I haven't been to for a couple weeks. 1. No active interfaces on Windows have those client servers as DNS (via ipconfig /all) 1. No interfaces that I checked (connected or disconnected) have static DNS entries at all (checking properties of the network adapters), including the Ethernet port and the disconnected SSTP VPN to that client. I did not actually check properties on all network interfaces before moving to the next step. 1. Searched the registry for one of the client site IP addresses, found it in HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\\{GUID} on the DhcpNameServer value 1. Searched the registry for the GUID, found it in HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards\3 on the ServiceName value. Corresponding value for Description is "Intel(R) 82579LM Gigabit Network Connection" which would be the internal Ethernet on the laptop. Entirely feasible that the last time that was connected was at that client site, and it may have been a month or more since that time. **Special Note:** This computer was upgraded from Windows 7 Pro to Windows 10 Pro since the last time it was at that location or connected to a wired network. **What's wrong / what should be happening instead** Probably shouldn't be pulling DNS values for networks that aren't connected. Not clear exactly how it's getting the DNS server addresses, because in looking through the Interfaces section mentioned above I did find one additional name server address that was not added to resolv.conf, so I don't think it's just enumerating the interfaces from the registry.
non_test
wsl resolv conf populated with dns servers from disconnected network your windows build number what you re doing and what s happening enabled wsl rebooted installed ubuntu from the store launched newly installed ubuntu ran a few sudo apt get installs with no problems left for a while tried sudo apt get update and unable to resolve security ubuntu com and archive ubuntu com did a bit of sleuthing ping to works resolving does not resolv conf has dns server entries local firewall plus servers at a client location i haven t been to for a couple weeks no active interfaces on windows have those client servers as dns via ipconfig all no interfaces that i checked connected or disconnected have static dns entries at all checking properties of the network adapters including the ethernet port and the disconnected sstp vpn to that client i did not actually check properties on all network interfaces before moving to the next step searched the registry for one of the client site ip addresses found it in hklm system currentcontrolset services tcpip parameters interfaces guid on the dhcpnameserver value searched the registry for the guid found it in hklm software microsoft windows nt currentversion networkcards on the servicename value corresponding value for description is intel r gigabit network connection which would be the internal ethernet on the laptop entirely feasible that the last time that was connected was at that client site and it may have been a month or more since that time special note this computer was upgraded from windows pro to windows pro since the last time it was at that location or connected to a wired network what s wrong what should be happening instead probably shouldn t be pulling dns values for networks that aren t connected not clear exactly how it s getting the dns server addresses because in looking through the interfaces section mentioned above i did find one additional name server address that was not added to resolv conf so i don t think it s just enumerating the interfaces from the registry
0
235,184
19,306,401,035
IssuesEvent
2021-12-13 12:00:53
Kotlin/kotlinx.coroutines
https://api.github.com/repos/Kotlin/kotlinx.coroutines
closed
kotlinx-coroutines-test: why the name `runTest`?
test
I understand that `runBlockingTest` was no longer an appropriate name because it is not always like `runBlocking` anymore, due to the new JS backend support where we cannot block. But I find the `runTest` name a bit too vague for the uninitiated. I mean the difference between these 2 is unclear: ```kotlin @Test fun test() { // do stuff } @Test fun test() = runTest { // do stuff } ``` Because both of those "run a test". I feel like the name of `runTest` should somehow convey the idea that it's about running coroutines / suspending functions / async stuff, as opposed to "regular tests". Were names like `runSuspendingTest` or `runAsyncTest` considered? Is it because it's expected to have many usages, and shorter is better?
1.0
kotlinx-coroutines-test: why the name `runTest`? - I understand that `runBlockingTest` was no longer an appropriate name because it is not always like `runBlocking` anymore, due to the new JS backend support where we cannot block. But I find the `runTest` name a bit too vague for the uninitiated. I mean the difference between these 2 is unclear: ```kotlin @Test fun test() { // do stuff } @Test fun test() = runTest { // do stuff } ``` Because both of those "run a test". I feel like the name of `runTest` should somehow convey the idea that it's about running coroutines / suspending functions / async stuff, as opposed to "regular tests". Were names like `runSuspendingTest` or `runAsyncTest` considered? Is it because it's expected to have many usages, and shorter is better?
test
kotlinx coroutines test why the name runtest i understand that runblockingtest was no longer an appropriate name because it is not always like runblocking anymore due to the new js backend support where we cannot block but i find the runtest name a bit too vague for the uninitiated i mean the difference between these is unclear kotlin test fun test do stuff test fun test runtest do stuff because both of those run a test i feel like the name of runtest should somehow convey the idea that it s about running coroutines suspending functions async stuff as opposed to regular tests were names like runsuspendingtest or runasynctest considered is it because it s expected to have many usages and shorter is better
1
72,029
3,371,064,519
IssuesEvent
2015-11-23 17:30:43
angular/material
https://api.github.com/repos/angular/material
closed
md-list-item: 'md-2-line' and 'md-3-line' long paragraph deviate from material design spec
- Easy fix priority: low ui: CSS
According to the material design spec http://www.google.com/design/spec/components/lists.html#lists-specs: 'md-2-line' should have a height of 72px. Currently, this is 75px (tested with codepen demo example on chrome 43); 'md-3-line' when the long paragraph collapses should be 88px. Currently this is 96px; Also, the alignment with respect to the avatar seems a bit off, because the padding for text deviates from the spec.
1.0
md-list-item: 'md-2-line' and 'md-3-line' long paragraph deviate from material design spec - According to the material design spec http://www.google.com/design/spec/components/lists.html#lists-specs: 'md-2-line' should have a height of 72px. Currently, this is 75px (tested with codepen demo example on chrome 43); 'md-3-line' when the long paragraph collapses should be 88px. Currently this is 96px; Also, the alignment with respect to the avatar seems a bit off, because the padding for text deviates from the spec.
non_test
md list item md line and md line long paragraph deviate from material design spec according to the material design spec md line should have a height of currently this is tested with codepen demo example on chrome md line when the long paragraph collapses should be currently this is also the alignment with respect to the avatar seems a bit off because the padding for text deviates from the spec
0
507,845
14,682,088,637
IssuesEvent
2020-12-31 15:16:48
egeoffrey/egeoffrey-gui
https://api.github.com/repos/egeoffrey/egeoffrey-gui
closed
Clone should create the object in a disabled status
bug priority
**Describe the bug** Sensors and rules when cloned should be disabled
1.0
Clone should create the object in a disabled status - **Describe the bug** Sensors and rules when cloned should be disabled
non_test
clone should create the object in a disabled status describe the bug sensors and rules when cloned should be disabled
0
143,533
11,568,579,295
IssuesEvent
2020-02-20 16:05:50
department-of-veterans-affairs/caseflow
https://api.github.com/repos/department-of-veterans-affairs/caseflow
opened
[Flaky Test] Postpone hearing legacy appeal and reschedule on the same day
Flaky test tech-improvement
## Background/context/resources ``` Postpone hearing legacy appeal and reschedule on the same day - spec.feature.hearings.postpone_hearing_spec spec/feature/hearings/postpone_hearing_spec.rb Failure/Error: dropdown.sibling(".Select-menu-outer")&.text&.split("\n") || [] Capybara::ElementNotFound: Unable to find css ".Select-menu-outer" that is a sibling of visible css ".dropdown-regionalOffice .Select-control" ./spec/support/feature_helper.rb:105:in `dropdown_click' ./spec/support/feature_helper.rb:28:in `click_dropdown' ./spec/feature/hearings/postpone_hearing_spec.rb:110:in `block (3 levels) in <top (required)>' ``` - Circle CI Error: https://app.circleci.com/jobs/github/department-of-veterans-affairs/caseflow/76273 - Has the test already been skipped in the code? - [x] Skipped - [ ] Not Skipped - Related Flakes + <!-- list any suspected related flaky test GH issues / CI links --> ## Approach <!-- Has our agreed upon default approach for tackling flaky tests. --> Time box this investigation and fix. Remember that if a test has been skipped for a decent amount of time, it may no longer map to the exact code. If you reach the end of your time box and don't feel like the solution is in sight: - [ ] document the work you've done, including dead ends and research - [ ] skip the test in the code - [ ] file a follow on ticket - [ ] close this issue
1.0
[Flaky Test] Postpone hearing legacy appeal and reschedule on the same day - ## Background/context/resources ``` Postpone hearing legacy appeal and reschedule on the same day - spec.feature.hearings.postpone_hearing_spec spec/feature/hearings/postpone_hearing_spec.rb Failure/Error: dropdown.sibling(".Select-menu-outer")&.text&.split("\n") || [] Capybara::ElementNotFound: Unable to find css ".Select-menu-outer" that is a sibling of visible css ".dropdown-regionalOffice .Select-control" ./spec/support/feature_helper.rb:105:in `dropdown_click' ./spec/support/feature_helper.rb:28:in `click_dropdown' ./spec/feature/hearings/postpone_hearing_spec.rb:110:in `block (3 levels) in <top (required)>' ``` - Circle CI Error: https://app.circleci.com/jobs/github/department-of-veterans-affairs/caseflow/76273 - Has the test already been skipped in the code? - [x] Skipped - [ ] Not Skipped - Related Flakes + <!-- list any suspected related flaky test GH issues / CI links --> ## Approach <!-- Has our agreed upon default approach for tackling flaky tests. --> Time box this investigation and fix. Remember that if a test has been skipped for a decent amount of time, it may no longer map to the exact code. If you reach the end of your time box and don't feel like the solution is in sight: - [ ] document the work you've done, including dead ends and research - [ ] skip the test in the code - [ ] file a follow on ticket - [ ] close this issue
test
postpone hearing legacy appeal and reschedule on the same day background context resources postpone hearing legacy appeal and reschedule on the same day spec feature hearings postpone hearing spec spec feature hearings postpone hearing spec rb failure error dropdown sibling select menu outer text split n capybara elementnotfound unable to find css select menu outer that is a sibling of visible css dropdown regionaloffice select control spec support feature helper rb in dropdown click spec support feature helper rb in click dropdown spec feature hearings postpone hearing spec rb in block levels in circle ci error has the test already been skipped in the code skipped not skipped related flakes approach time box this investigation and fix remember that if a test has been skipped for a decent amount of time it may no longer map to the exact code if you reach the end of your time box and don t feel like the solution is in sight document the work you ve done including dead ends and research skip the test in the code file a follow on ticket close this issue
1
182,646
14,145,354,789
IssuesEvent
2020-11-10 17:37:33
istio/istio.io
https://api.github.com/repos/istio/istio.io
closed
[istio.io testing] Need test for Denials and White/Black Listing
area/test and release kind/docs kind/enhancement lifecycle/needs-triage
**Describe the feature request** We need to develop a test for the [Denials and White/Black Listing](https://preliminary.istio.io/docs/tasks/policy-enforcement/denial-and-list/) task in order to provide automated testing of the Istio.io website for future releases. Example tests and the documentation for the framework can be found here: https://github.com/istio/istio/tree/master/tests/integration/istioio A YouTube video describing the usage of the framework can be found here: https://www.youtube.com/watch?v=3y-z8NaVwr0 Please reach out to the Test and Release channel on the [Istio Slack](https://discuss.istio.io/t/istio-slack-channel/1527) or [Test and Release Discuss](https://discuss.istio.io/c/test-and-release) with any questions.
1.0
[istio.io testing] Need test for Denials and White/Black Listing - **Describe the feature request** We need to develop a test for the [Denials and White/Black Listing](https://preliminary.istio.io/docs/tasks/policy-enforcement/denial-and-list/) task in order to provide automated testing of the Istio.io website for future releases. Example tests and the documentation for the framework can be found here: https://github.com/istio/istio/tree/master/tests/integration/istioio A YouTube video describing the usage of the framework can be found here: https://www.youtube.com/watch?v=3y-z8NaVwr0 Please reach out to the Test and Release channel on the [Istio Slack](https://discuss.istio.io/t/istio-slack-channel/1527) or [Test and Release Discuss](https://discuss.istio.io/c/test-and-release) with any questions.
test
need test for denials and white black listing describe the feature request we need to develop a test for the task in order to provide automated testing of the istio io website for future releases example tests and the documentation for the framework can be found here a youtube video describing the usage of the framework can be found here please reach out to the test and release channel on the or with any questions
1
250,832
21,338,161,641
IssuesEvent
2022-04-18 17:00:12
mozilla-mobile/fenix
https://api.github.com/repos/mozilla-mobile/fenix
reopened
Intermittent UI test failure - <SearchTest.shortcutButtonTest>
eng:intermittent-test eng:ui-test
### Firebase Test Run: [Firebase link](https://console.firebase.google.com/u/0/project/moz-fenix/testlab/histories/bh.66b7091e15d53d45/matrices/6556112574874726927/executions/bs.2f403c131f2b70b0/testcases/1/test-cases) ### Stacktrace: java.lang.AssertionError: Assertion failed at org.mozilla.fenix.ui.robots.SearchRobotKt.assertSearchEngineResults(SearchRobot.kt:231) at org.mozilla.fenix.ui.robots.SearchRobotKt.access$assertSearchEngineResults(SearchRobot.kt:1) at org.mozilla.fenix.ui.robots.SearchRobot.verifySearchEngineResults(SearchRobot.kt:56) at org.mozilla.fenix.ui.SearchTest$shortcutButtonTest$7.invoke(SearchTest.kt:64) at org.mozilla.fenix.ui.SearchTest$shortcutButtonTest$7.invoke(SearchTest.kt:60) at org.mozilla.fenix.ui.robots.HomeScreenRobot$Transition.openSearch(HomeScreenRobot.kt:185) at org.mozilla.fenix.ui.SearchTest.shortcutButtonTest(SearchTest.kt:60) at java.lang.reflect.Method.invoke(Native Method) 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 androidx.test.rule.ActivityTestRule$ActivityStatement.evaluate(ActivityTestRule.java:531) 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.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:27) 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.junit.runner.JUnitCore.run(JUnitCore.java:137) at org.junit.runner.JUnitCore.run(JUnitCore.java:115) at androidx.test.internal.runner.TestExecutor.execute(TestExecutor.java:56) at androidx.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:395) at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:2145) ### Build: 8/23 Main
2.0
Intermittent UI test failure - <SearchTest.shortcutButtonTest> - ### Firebase Test Run: [Firebase link](https://console.firebase.google.com/u/0/project/moz-fenix/testlab/histories/bh.66b7091e15d53d45/matrices/6556112574874726927/executions/bs.2f403c131f2b70b0/testcases/1/test-cases) ### Stacktrace: java.lang.AssertionError: Assertion failed at org.mozilla.fenix.ui.robots.SearchRobotKt.assertSearchEngineResults(SearchRobot.kt:231) at org.mozilla.fenix.ui.robots.SearchRobotKt.access$assertSearchEngineResults(SearchRobot.kt:1) at org.mozilla.fenix.ui.robots.SearchRobot.verifySearchEngineResults(SearchRobot.kt:56) at org.mozilla.fenix.ui.SearchTest$shortcutButtonTest$7.invoke(SearchTest.kt:64) at org.mozilla.fenix.ui.SearchTest$shortcutButtonTest$7.invoke(SearchTest.kt:60) at org.mozilla.fenix.ui.robots.HomeScreenRobot$Transition.openSearch(HomeScreenRobot.kt:185) at org.mozilla.fenix.ui.SearchTest.shortcutButtonTest(SearchTest.kt:60) at java.lang.reflect.Method.invoke(Native Method) 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 androidx.test.rule.ActivityTestRule$ActivityStatement.evaluate(ActivityTestRule.java:531) 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.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:27) 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.junit.runner.JUnitCore.run(JUnitCore.java:137) at org.junit.runner.JUnitCore.run(JUnitCore.java:115) at androidx.test.internal.runner.TestExecutor.execute(TestExecutor.java:56) at androidx.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:395) at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:2145) ### Build: 8/23 Main
test
intermittent ui test failure firebase test run stacktrace java lang assertionerror assertion failed at org mozilla fenix ui robots searchrobotkt assertsearchengineresults searchrobot kt at org mozilla fenix ui robots searchrobotkt access assertsearchengineresults searchrobot kt at org mozilla fenix ui robots searchrobot verifysearchengineresults searchrobot kt at org mozilla fenix ui searchtest shortcutbuttontest invoke searchtest kt at org mozilla fenix ui searchtest shortcutbuttontest invoke searchtest kt at org mozilla fenix ui robots homescreenrobot transition opensearch homescreenrobot kt at org mozilla fenix ui searchtest shortcutbuttontest searchtest kt at java lang reflect method invoke native method 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 androidx test rule activitytestrule activitystatement evaluate activitytestrule 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 junit runners suite runchild suite java at org junit runners suite runchild suite 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 junit runner junitcore run junitcore java at org junit runner junitcore run junitcore java at androidx test internal runner testexecutor execute testexecutor java at androidx test runner androidjunitrunner onstart androidjunitrunner java at android app instrumentation instrumentationthread run instrumentation java build main
1
312,104
26,836,997,936
IssuesEvent
2023-02-02 20:23:12
golang/go
https://api.github.com/repos/golang/go
closed
runtime: TestCgoLockOSThreadExit failures with `sub thread still running`
Testing NeedsFix compiler/runtime
``` #!watchflakes post <- pkg == "runtime" && test == "TestCgoLockOSThreadExit" && `sub thread still running` ``` (Pulled out from https://github.com/golang/go/issues/57083#issuecomment-1403901300.)
1.0
runtime: TestCgoLockOSThreadExit failures with `sub thread still running` - ``` #!watchflakes post <- pkg == "runtime" && test == "TestCgoLockOSThreadExit" && `sub thread still running` ``` (Pulled out from https://github.com/golang/go/issues/57083#issuecomment-1403901300.)
test
runtime testcgolockosthreadexit failures with sub thread still running watchflakes post pkg runtime test testcgolockosthreadexit sub thread still running pulled out from
1
802,853
29,047,588,390
IssuesEvent
2023-05-13 19:19:02
exellian/rex
https://api.github.com/repos/exellian/rex
closed
DRAFT: Template rendering function design
draft priority: high
A really important problem which needs to be solved is the design of the rendering function of a template. This function should not only render an arbitrary string instead it should be able to be used also for hydration and rendering a template to different objects. Therefore the function must be generated in a way that is very generic. idea: A template is built out of tree structure called Nodes (Tags, VoidTags, Text and Expressions): ```html <div> { 0 + 3 } // Expression <div> //Tag with child nodes ... </div> this is the text of a text node </div> ``` So each node is either a leaf (TextNode, VoidTag, Expressions) or a Node with children (TagNodes, Expressions). The real problem is that an Expression can not only be a leaf but also a node in this tree. In the following the individual cases are shown were Expressions are nodes with children: ```html <div> { <div> hallo </div> } // Expression which contains a tag with children. // Type: Node { // Expression which contains a for loop // Type: Array<Node> for x in 0..10 { <div></div> } } { // Expression which contains a for loop // Type: Array<Array<Node>> for x in 0..10 { for x in 0..10 { <div></div> } } } { // Expression which has an if block // Type: Node if success { <div>success!</div> } else { 8 + 9 // Any other datatype which is not of type Node or Array<Node> gets automatically converted to a TextNode } } { (<div></div>) } // We could allow a Node inside a group, but this should probably discussed later on! { x.test } // ``` So basically an expression embedded directly into the template can only have the type Node, Array<Node>, Array<Array<Node>>, Array<Array<Array<Node>>>, ... Because we don't want to have different possible types of expressions the idea is to transform expressions in a way so that simply every expression has type Array<Node>. To do this we have to generate for every non Node expression a make_text_node statement, for every simply Node a make_vector_from_one_element statement, for every Array<Node> statement nothing and if we have a for loop expression, we have to perform a flat_map from Array<Array<Node>> to Array<Node>
1.0
DRAFT: Template rendering function design - A really important problem which needs to be solved is the design of the rendering function of a template. This function should not only render an arbitrary string instead it should be able to be used also for hydration and rendering a template to different objects. Therefore the function must be generated in a way that is very generic. idea: A template is built out of tree structure called Nodes (Tags, VoidTags, Text and Expressions): ```html <div> { 0 + 3 } // Expression <div> //Tag with child nodes ... </div> this is the text of a text node </div> ``` So each node is either a leaf (TextNode, VoidTag, Expressions) or a Node with children (TagNodes, Expressions). The real problem is that an Expression can not only be a leaf but also a node in this tree. In the following the individual cases are shown were Expressions are nodes with children: ```html <div> { <div> hallo </div> } // Expression which contains a tag with children. // Type: Node { // Expression which contains a for loop // Type: Array<Node> for x in 0..10 { <div></div> } } { // Expression which contains a for loop // Type: Array<Array<Node>> for x in 0..10 { for x in 0..10 { <div></div> } } } { // Expression which has an if block // Type: Node if success { <div>success!</div> } else { 8 + 9 // Any other datatype which is not of type Node or Array<Node> gets automatically converted to a TextNode } } { (<div></div>) } // We could allow a Node inside a group, but this should probably discussed later on! { x.test } // ``` So basically an expression embedded directly into the template can only have the type Node, Array<Node>, Array<Array<Node>>, Array<Array<Array<Node>>>, ... Because we don't want to have different possible types of expressions the idea is to transform expressions in a way so that simply every expression has type Array<Node>. To do this we have to generate for every non Node expression a make_text_node statement, for every simply Node a make_vector_from_one_element statement, for every Array<Node> statement nothing and if we have a for loop expression, we have to perform a flat_map from Array<Array<Node>> to Array<Node>
non_test
draft template rendering function design a really important problem which needs to be solved is the design of the rendering function of a template this function should not only render an arbitrary string instead it should be able to be used also for hydration and rendering a template to different objects therefore the function must be generated in a way that is very generic idea a template is built out of tree structure called nodes tags voidtags text and expressions html expression tag with child nodes this is the text of a text node so each node is either a leaf textnode voidtag expressions or a node with children tagnodes expressions the real problem is that an expression can not only be a leaf but also a node in this tree in the following the individual cases are shown were expressions are nodes with children html hallo expression which contains a tag with children type node expression which contains a for loop type array for x in expression which contains a for loop type array for x in for x in expression which has an if block type node if success success else any other datatype which is not of type node or array gets automatically converted to a textnode we could allow a node inside a group but this should probably discussed later on x test so basically an expression embedded directly into the template can only have the type node array array array because we don t want to have different possible types of expressions the idea is to transform expressions in a way so that simply every expression has type array to do this we have to generate for every non node expression a make text node statement for every simply node a make vector from one element statement for every array statement nothing and if we have a for loop expression we have to perform a flat map from array to array
0
264,027
23,097,138,437
IssuesEvent
2022-07-26 20:47:30
elastic/kibana
https://api.github.com/repos/elastic/kibana
opened
Failing test: Jest Tests.x-pack/plugins/triggers_actions_ui/public/application/sections/field_browser - FieldsBrowser updateSelectedCategoryIds should remove a selected category, which deletes the category badge
failed-test
A test failed on a tracked branch ``` Error: thrown: "Exceeded timeout of 5000 ms for a test. Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test." at /var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/x-pack/plugins/triggers_actions_ui/public/application/sections/field_browser/field_browser.test.tsx:68:5 at _dispatchDescribe (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/index.js:67:26) at describe (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/index.js:30:5) at /var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/x-pack/plugins/triggers_actions_ui/public/application/sections/field_browser/field_browser.test.tsx:49:3 at _dispatchDescribe (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/index.js:67:26) at describe (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/index.js:30:5) at Object.<anonymous> (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/x-pack/plugins/triggers_actions_ui/public/application/sections/field_browser/field_browser.test.tsx:25:1) at Runtime._execModule (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-runtime/build/index.js:1299:24) at Runtime._loadModule (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-runtime/build/index.js:898:12) at Runtime.requireModule (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-runtime/build/index.js:746:10) at jestAdapter (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:106:13) at runMicrotasks (<anonymous>) at processTicksAndRejections (node:internal/process/task_queues:96:5) at runTestInternal (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-runner/build/runTest.js:380:16) at runTest (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-runner/build/runTest.js:472:34) at Object.worker (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-runner/build/testWorker.js:133:12) ``` First failure: [CI Build - main](https://buildkite.com/elastic/kibana-on-merge/builds/18933#01823c1b-6c2d-4d4a-8326-cc94a071fef4) <!-- kibanaCiData = {"failed-test":{"test.class":"Jest Tests.x-pack/plugins/triggers_actions_ui/public/application/sections/field_browser","test.name":"FieldsBrowser updateSelectedCategoryIds should remove a selected category, which deletes the category badge","test.failCount":1}} -->
1.0
Failing test: Jest Tests.x-pack/plugins/triggers_actions_ui/public/application/sections/field_browser - FieldsBrowser updateSelectedCategoryIds should remove a selected category, which deletes the category badge - A test failed on a tracked branch ``` Error: thrown: "Exceeded timeout of 5000 ms for a test. Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test." at /var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/x-pack/plugins/triggers_actions_ui/public/application/sections/field_browser/field_browser.test.tsx:68:5 at _dispatchDescribe (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/index.js:67:26) at describe (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/index.js:30:5) at /var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/x-pack/plugins/triggers_actions_ui/public/application/sections/field_browser/field_browser.test.tsx:49:3 at _dispatchDescribe (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/index.js:67:26) at describe (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/index.js:30:5) at Object.<anonymous> (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/x-pack/plugins/triggers_actions_ui/public/application/sections/field_browser/field_browser.test.tsx:25:1) at Runtime._execModule (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-runtime/build/index.js:1299:24) at Runtime._loadModule (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-runtime/build/index.js:898:12) at Runtime.requireModule (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-runtime/build/index.js:746:10) at jestAdapter (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:106:13) at runMicrotasks (<anonymous>) at processTicksAndRejections (node:internal/process/task_queues:96:5) at runTestInternal (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-runner/build/runTest.js:380:16) at runTest (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-runner/build/runTest.js:472:34) at Object.worker (/var/lib/buildkite-agent/builds/kb-n2-4-spot-d00551d59c9479c3/elastic/kibana-on-merge/kibana/node_modules/jest-runner/build/testWorker.js:133:12) ``` First failure: [CI Build - main](https://buildkite.com/elastic/kibana-on-merge/builds/18933#01823c1b-6c2d-4d4a-8326-cc94a071fef4) <!-- kibanaCiData = {"failed-test":{"test.class":"Jest Tests.x-pack/plugins/triggers_actions_ui/public/application/sections/field_browser","test.name":"FieldsBrowser updateSelectedCategoryIds should remove a selected category, which deletes the category badge","test.failCount":1}} -->
test
failing test jest tests x pack plugins triggers actions ui public application sections field browser fieldsbrowser updateselectedcategoryids should remove a selected category which deletes the category badge a test failed on a tracked branch error thrown exceeded timeout of ms for a test use jest settimeout newtimeout to increase the timeout value if this is a long running test at var lib buildkite agent builds kb spot elastic kibana on merge kibana x pack plugins triggers actions ui public application sections field browser field browser test tsx at dispatchdescribe var lib buildkite agent builds kb spot elastic kibana on merge kibana node modules jest circus build index js at describe var lib buildkite agent builds kb spot elastic kibana on merge kibana node modules jest circus build index js at var lib buildkite agent builds kb spot elastic kibana on merge kibana x pack plugins triggers actions ui public application sections field browser field browser test tsx at dispatchdescribe var lib buildkite agent builds kb spot elastic kibana on merge kibana node modules jest circus build index js at describe var lib buildkite agent builds kb spot elastic kibana on merge kibana node modules jest circus build index js at object var lib buildkite agent builds kb spot elastic kibana on merge kibana x pack plugins triggers actions ui public application sections field browser field browser test tsx at runtime execmodule var lib buildkite agent builds kb spot elastic kibana on merge kibana node modules jest runtime build index js at runtime loadmodule var lib buildkite agent builds kb spot elastic kibana on merge kibana node modules jest runtime build index js at runtime requiremodule var lib buildkite agent builds kb spot elastic kibana on merge kibana node modules jest runtime build index js at jestadapter var lib buildkite agent builds kb spot elastic kibana on merge kibana node modules jest circus build legacy code todo rewrite jestadapter js at runmicrotasks at processticksandrejections node internal process task queues at runtestinternal var lib buildkite agent builds kb spot elastic kibana on merge kibana node modules jest runner build runtest js at runtest var lib buildkite agent builds kb spot elastic kibana on merge kibana node modules jest runner build runtest js at object worker var lib buildkite agent builds kb spot elastic kibana on merge kibana node modules jest runner build testworker js first failure
1
2,581
2,610,941,217
IssuesEvent
2015-02-26 23:28:48
niranjv/schedulr
https://api.github.com/repos/niranjv/schedulr
closed
Integrate project with coveralls.io to get code coverage info
Testing
* Read info at https://github.com/jimhester/covr (cover R package uses coveralls.io to calculate code coverage) * Add repo to coveralls.io acct * Edit Travis.yml file to call _covr_ R package to calculate coverage value
1.0
Integrate project with coveralls.io to get code coverage info - * Read info at https://github.com/jimhester/covr (cover R package uses coveralls.io to calculate code coverage) * Add repo to coveralls.io acct * Edit Travis.yml file to call _covr_ R package to calculate coverage value
test
integrate project with coveralls io to get code coverage info read info at cover r package uses coveralls io to calculate code coverage add repo to coveralls io acct edit travis yml file to call covr r package to calculate coverage value
1
262,124
27,853,404,393
IssuesEvent
2023-03-20 20:34:51
opensearch-project/opensearch-build-libraries
https://api.github.com/repos/opensearch-project/opensearch-build-libraries
opened
jenkins-core-2.332.3.jar: 20 vulnerabilities (highest severity is: 9.8)
Mend: dependency security vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p></summary> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p></details> ## Vulnerabilities | CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (jenkins-core version) | Remediation Available | | ------------- | ------------- | ----- | ----- | ----- | ------------- | --- | | [CVE-2022-22978](https://www.mend.io/vulnerability-database/CVE-2022-22978) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | spring-security-web-5.6.1.jar | Transitive | N/A* | &#10060; | | [CVE-2022-22965](https://www.mend.io/vulnerability-database/CVE-2022-22965) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | spring-beans-5.3.14.jar | Transitive | N/A* | &#10060; | | [CVE-2022-31692](https://www.mend.io/vulnerability-database/CVE-2022-31692) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | spring-security-web-5.6.1.jar | Transitive | N/A* | &#10060; | | [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.19.jar | Transitive | N/A* | &#10060; | | [CVE-2022-34174](https://www.mend.io/vulnerability-database/CVE-2022-34174) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | jenkins-core-2.332.3.jar | Direct | org.jenkins-ci.main:jenkins-core:2.356,2.332.4 | &#9989; | | [CVE-2023-27901](https://www.mend.io/vulnerability-database/CVE-2023-27901) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | jenkins-core-2.332.3.jar | Direct | org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394 | &#9989; | | [CVE-2023-24998](https://www.mend.io/vulnerability-database/CVE-2023-24998) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | commons-fileupload-1.4.jar | Transitive | N/A* | &#10060; | | [CVE-2023-27900](https://www.mend.io/vulnerability-database/CVE-2023-27900) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | jenkins-core-2.332.3.jar | Direct | org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394 | &#9989; | | [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.19.jar | Transitive | N/A* | &#10060; | | [CVE-2023-27899](https://www.mend.io/vulnerability-database/CVE-2023-27899) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.0 | jenkins-core-2.332.3.jar | Direct | org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394 | &#9989; | | [CVE-2022-22950](https://www.mend.io/vulnerability-database/CVE-2022-22950) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | spring-expression-5.3.14.jar | Transitive | N/A* | &#10060; | | [CVE-2022-34170](https://www.mend.io/vulnerability-database/CVE-2022-34170) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | jenkins-core-2.332.3.jar | Direct | org.jenkins-ci.main:jenkins-core:2.356,2.332.4,2.346.1 | &#9989; | | [CVE-2022-34171](https://www.mend.io/vulnerability-database/CVE-2022-34171) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | jenkins-core-2.332.3.jar | Direct | org.jenkins-ci.main:jenkins-core:2.356,2.332.4,2.346.1 | &#9989; | | [CVE-2023-27898](https://www.mend.io/vulnerability-database/CVE-2023-27898) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.4 | jenkins-core-2.332.3.jar | Direct | org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394 | &#9989; | | [CVE-2022-22968](https://www.mend.io/vulnerability-database/CVE-2022-22968) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | spring-context-5.3.14.jar | Transitive | N/A* | &#10060; | | [CVE-2022-22976](https://www.mend.io/vulnerability-database/CVE-2022-22976) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | spring-security-crypto-5.6.1.jar | Transitive | N/A* | &#10060; | | [CVE-2023-27904](https://www.mend.io/vulnerability-database/CVE-2023-27904) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | jenkins-core-2.332.3.jar | Direct | org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394 | &#9989; | | [CVE-2022-22970](https://www.mend.io/vulnerability-database/CVE-2022-22970) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | detected in multiple dependencies | Transitive | N/A* | &#10060; | | [CVE-2023-27903](https://www.mend.io/vulnerability-database/CVE-2023-27903) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 4.4 | jenkins-core-2.332.3.jar | Direct | org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394 | &#9989; | | [CVE-2023-27902](https://www.mend.io/vulnerability-database/CVE-2023-27902) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 4.3 | jenkins-core-2.332.3.jar | Direct | N/A | &#10060; | <p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.</p> ## Details <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-22978</summary> ### Vulnerable Library - <b>spring-security-web-5.6.1.jar</b></p> <p>Spring Security</p> <p>Library home page: <a href="https://spring.io/projects/spring-security">https://spring.io/projects/spring-security</a></p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework.security/spring-security-web/5.6.1/7c2a899cfa8c986170721fedf356a73f73ddcb23/spring-security-web-5.6.1.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - :x: **spring-security-web-5.6.1.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> In Spring Security versions 5.5.6 and 5.6.3 and older unsupported versions, RegexRequestMatcher can easily be misconfigured to be bypassed on some servlet containers. Applications using RegexRequestMatcher with `.` in the regular expression are possibly vulnerable to an authorization bypass <p>Publish Date: 2022-05-19 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22978>CVE-2022-22978</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://tanzu.vmware.com/security/cve-2022-22978">https://tanzu.vmware.com/security/cve-2022-22978</a></p> <p>Release Date: 2022-05-19</p> <p>Fix Resolution: org.springframework.security:spring-security-web:5.5.7,5.6.4</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-22965</summary> ### Vulnerable Library - <b>spring-beans-5.3.14.jar</b></p> <p>Spring Beans</p> <p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-beans/5.3.14/24cc27af89edc1581a57bb15bc160d2353f40a0e/spring-beans-5.3.14.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - spring-security-web-5.6.1.jar - :x: **spring-beans-5.3.14.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> A Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data binding. The specific exploit requires the application to run on Tomcat as a WAR deployment. If the application is deployed as a Spring Boot executable jar, i.e. the default, it is not vulnerable to the exploit. However, the nature of the vulnerability is more general, and there may be other ways to exploit it. <p>Publish Date: 2022-04-01 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22965>CVE-2022-22965</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://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement">https://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement</a></p> <p>Release Date: 2022-04-01</p> <p>Fix Resolution: org.springframework:spring-beans:5.2.20.RELEASE,5.3.18</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-31692</summary> ### Vulnerable Library - <b>spring-security-web-5.6.1.jar</b></p> <p>Spring Security</p> <p>Library home page: <a href="https://spring.io/projects/spring-security">https://spring.io/projects/spring-security</a></p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework.security/spring-security-web/5.6.1/7c2a899cfa8c986170721fedf356a73f73ddcb23/spring-security-web-5.6.1.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - :x: **spring-security-web-5.6.1.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Spring Security, versions 5.7 prior to 5.7.5 and 5.6 prior to 5.6.9 could be susceptible to authorization rules bypass via forward or include dispatcher types. Specifically, an application is vulnerable when all of the following are true: The application expects that Spring Security applies security to forward and include dispatcher types. The application uses the AuthorizationFilter either manually or via the authorizeHttpRequests() method. The application configures the FilterChainProxy to apply to forward and/or include requests (e.g. spring.security.filter.dispatcher-types = request, error, async, forward, include). The application may forward or include the request to a higher privilege-secured endpoint.The application configures Spring Security to apply to every dispatcher type via authorizeHttpRequests().shouldFilterAllDispatcherTypes(true) <p>Publish Date: 2022-10-31 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-31692>CVE-2022-31692</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://tanzu.vmware.com/security/cve-2022-31692">https://tanzu.vmware.com/security/cve-2022-31692</a></p> <p>Release Date: 2022-10-31</p> <p>Fix Resolution: org.springframework.security:spring-security-web:5.6.9,5.7.5</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-41966</summary> ### Vulnerable Library - <b>xstream-1.4.19.jar</b></p> <p></p> <p>Library home page: <a href="http://x-stream.github.io">http://x-stream.github.io</a></p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.thoughtworks.xstream/xstream/1.4.19/e0e581d812aa92ae12f07234f3398e06af74b112/xstream-1.4.19.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - :x: **xstream-1.4.19.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> XStream serializes Java objects to XML and back again. Versions prior to 1.4.20 may allow a remote attacker to terminate the application with a stack overflow error, resulting in a denial of service only via manipulation the processed input stream. The attack uses the hash code implementation for collections and maps to force recursive hash calculation causing a stack overflow. This issue is patched in version 1.4.20 which handles the stack overflow and raises an InputManipulationException instead. A potential workaround for users who only use HashMap or HashSet and whose XML refers these only as default map or set, is to change the default implementation of java.util.Map and java.util per the code example in the referenced advisory. However, this implies that your application does not care about the implementation of the map and all elements are comparable. <p>Publish Date: 2022-12-28 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-41966>CVE-2022-41966</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</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: 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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-j563-grx4-pjpv">https://github.com/advisories/GHSA-j563-grx4-pjpv</a></p> <p>Release Date: 2022-12-28</p> <p>Fix Resolution: com.thoughtworks.xstream:xstream:1.4.20</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-34174</summary> ### Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> Dependency Hierarchy: - :x: **jenkins-core-2.332.3.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> In Jenkins 2.355 and earlier, LTS 2.332.3 and earlier, an observable timing discrepancy on the login form allows distinguishing between login attempts with an invalid username, and login attempts with a valid username and wrong password, when using the Jenkins user database security realm. <p>Publish Date: 2022-06-23 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-34174>CVE-2022-34174</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</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: 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://www.jenkins.io/security/advisory/2022-06-22/#SECURITY-2781">https://www.jenkins.io/security/advisory/2022-06-22/#SECURITY-2781</a></p> <p>Release Date: 2022-06-23</p> <p>Fix Resolution: org.jenkins-ci.main:jenkins-core:2.356,2.332.4</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2023-27901</summary> ### Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> Dependency Hierarchy: - :x: **jenkins-core-2.332.3.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Jenkins 2.393 and earlier, LTS 2.375.3 and earlier uses the Apache Commons FileUpload library without specifying limits for the number of request parts introduced in version 1.5 for CVE-2023-24998 in org.kohsuke.stapler.RequestImpl, allowing attackers to trigger a denial of service. <p>Publish Date: 2023-03-10 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-27901>CVE-2023-27901</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</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: 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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-h76p-mc68-jv3p">https://github.com/advisories/GHSA-h76p-mc68-jv3p</a></p> <p>Release Date: 2023-03-10</p> <p>Fix Resolution: org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2023-24998</summary> ### Vulnerable Library - <b>commons-fileupload-1.4.jar</b></p> <p>The Apache Commons FileUpload component provides a simple yet flexible means of adding support for multipart file upload functionality to servlets and web applications.</p> <p>Library home page: <a href="http://commons.apache.org/proper/commons-fileupload/">http://commons.apache.org/proper/commons-fileupload/</a></p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/commons-fileupload/commons-fileupload/1.4/f95188e3d372e20e7328706c37ef366e5d7859b0/commons-fileupload-1.4.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - :x: **commons-fileupload-1.4.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Apache Commons FileUpload before 1.5 does not limit the number of request parts to be processed resulting in the possibility of an attacker triggering a DoS with a malicious upload or series of uploads. Note that, like all of the file upload limits, the new configuration option (FileUploadBase#setFileCountMax) is not enabled by default and must be explicitly configured. <p>Publish Date: 2023-02-20 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-24998>CVE-2023-24998</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</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: 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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://seclists.org/oss-sec/2023/q1/108">https://seclists.org/oss-sec/2023/q1/108</a></p> <p>Release Date: 2023-02-20</p> <p>Fix Resolution: commons-fileupload:commons-fileupload:1.5;org.apache.tomcat:tomcat-coyote:8.5.85,9.0.71,10.1.5</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2023-27900</summary> ### Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> Dependency Hierarchy: - :x: **jenkins-core-2.332.3.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Jenkins 2.393 and earlier, LTS 2.375.3 and earlier uses the Apache Commons FileUpload library without specifying limits for the number of request parts introduced in version 1.5 for CVE-2023-24998 in hudson.util.MultipartFormDataParser, allowing attackers to trigger a denial of service. <p>Publish Date: 2023-03-10 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-27900>CVE-2023-27900</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</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: 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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://www.jenkins.io/security/advisory/2023-03-08/#SECURITY-2120">https://www.jenkins.io/security/advisory/2023-03-08/#SECURITY-2120</a></p> <p>Release Date: 2023-03-10</p> <p>Fix Resolution: org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-40151</summary> ### Vulnerable Library - <b>xstream-1.4.19.jar</b></p> <p></p> <p>Library home page: <a href="http://x-stream.github.io">http://x-stream.github.io</a></p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.thoughtworks.xstream/xstream/1.4.19/e0e581d812aa92ae12f07234f3398e06af74b112/xstream-1.4.19.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - :x: **xstream-1.4.19.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Those using Xstream to seralize XML data may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow. This effect may support a denial of service attack. <p>Publish Date: 2022-09-16 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-40151>CVE-2022-40151</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</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: 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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-f8cc-g7j8-xxpm">https://github.com/advisories/GHSA-f8cc-g7j8-xxpm</a></p> <p>Release Date: 2022-09-16</p> <p>Fix Resolution: com.thoughtworks.xstream:xstream:1.4.20</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2023-27899</summary> ### Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> Dependency Hierarchy: - :x: **jenkins-core-2.332.3.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Jenkins 2.393 and earlier, LTS 2.375.3 and earlier creates a temporary file in the default temporary directory with the default permissions for newly created files when uploading a plugin for installation, potentially allowing attackers with access to the Jenkins controller file system to read and write the file before it is used, potentially resulting in arbitrary code execution. <p>Publish Date: 2023-03-10 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-27899>CVE-2023-27899</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.0</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: High - 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-hf9h-vv4m-2f33">https://github.com/advisories/GHSA-hf9h-vv4m-2f33</a></p> <p>Release Date: 2023-03-10</p> <p>Fix Resolution: org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-22950</summary> ### Vulnerable Library - <b>spring-expression-5.3.14.jar</b></p> <p>Spring Expression Language (SpEL)</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-expression/5.3.14/5cd4c568522b7084afac5d2ac6cb945b797b3f16/spring-expression-5.3.14.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - spring-security-web-5.6.1.jar - :x: **spring-expression-5.3.14.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> n Spring Framework versions 5.3.0 - 5.3.16 and older unsupported versions, it is possible for a user to provide a specially crafted SpEL expression that may cause a denial of service condition. <p>Publish Date: 2022-04-01 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22950>CVE-2022-22950</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.5</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: 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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://tanzu.vmware.com/security/cve-2022-22950">https://tanzu.vmware.com/security/cve-2022-22950</a></p> <p>Release Date: 2022-04-01</p> <p>Fix Resolution: org.springframework:spring-expression:5.2.20,5.3.17</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-34170</summary> ### Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> Dependency Hierarchy: - :x: **jenkins-core-2.332.3.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> In Jenkins 2.320 through 2.355 (both inclusive) and LTS 2.332.1 through LTS 2.332.3 (both inclusive) the help icon does not escape the feature name that is part of its tooltip, effectively undoing the fix for SECURITY-1955, resulting in a cross-site scripting (XSS) vulnerability exploitable by attackers with Job/Configure permission. <p>Publish Date: 2022-06-23 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-34170>CVE-2022-34170</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - 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://www.jenkins.io/security/advisory/2022-06-22/#SECURITY-2781">https://www.jenkins.io/security/advisory/2022-06-22/#SECURITY-2781</a></p> <p>Release Date: 2022-06-23</p> <p>Fix Resolution: org.jenkins-ci.main:jenkins-core:2.356,2.332.4,2.346.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-34171</summary> ### Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> Dependency Hierarchy: - :x: **jenkins-core-2.332.3.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> In Jenkins 2.321 through 2.355 (both inclusive) and LTS 2.332.1 through LTS 2.332.3 (both inclusive) the HTML output generated for new symbol-based SVG icons includes the 'title' attribute of 'l:ionicon' (until Jenkins 2.334) and 'alt' attribute of 'l:icon' (since Jenkins 2.335) without further escaping, resulting in a cross-site scripting (XSS) vulnerability. <p>Publish Date: 2022-06-23 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-34171>CVE-2022-34171</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - 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://www.jenkins.io/security/advisory/2022-06-22/#SECURITY-2781">https://www.jenkins.io/security/advisory/2022-06-22/#SECURITY-2781</a></p> <p>Release Date: 2022-06-23</p> <p>Fix Resolution: org.jenkins-ci.main:jenkins-core:2.356,2.332.4,2.346.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2023-27898</summary> ### Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> Dependency Hierarchy: - :x: **jenkins-core-2.332.3.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Jenkins 2.270 through 2.393 (both inclusive), LTS 2.277.1 through 2.375.3 (both inclusive) does not escape the Jenkins version a plugin depends on when rendering the error message stating its incompatibility with the current version of Jenkins, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to provide plugins to the configured update sites and have this message shown by Jenkins instances. <p>Publish Date: 2023-03-10 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-27898>CVE-2023-27898</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.4</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - 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://www.jenkins.io/security/advisory/2023-03-08/#SECURITY-3037">https://www.jenkins.io/security/advisory/2023-03-08/#SECURITY-3037</a></p> <p>Release Date: 2023-03-10</p> <p>Fix Resolution: org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-22968</summary> ### Vulnerable Library - <b>spring-context-5.3.14.jar</b></p> <p>Spring Context</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-context/5.3.14/ce6042492f042131f602bdc83fcb412b142bdac5/spring-context-5.3.14.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - spring-security-web-5.6.1.jar - :x: **spring-context-5.3.14.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> In Spring Framework versions 5.3.0 - 5.3.18, 5.2.0 - 5.2.20, and older unsupported versions, the patterns for disallowedFields on a DataBinder are case sensitive which means a field is not effectively protected unless it is listed with both upper and lower case for the first character of the field, including upper and lower case for the first character of all nested fields within the property path. <p>Publish Date: 2022-04-14 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22968>CVE-2022-22968</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.3</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: None - Integrity Impact: Low - 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://tanzu.vmware.com/security/cve-2022-22968">https://tanzu.vmware.com/security/cve-2022-22968</a></p> <p>Release Date: 2022-04-14</p> <p>Fix Resolution: org.springframework:spring-context:5.2.21,5.3.19</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-22976</summary> ### Vulnerable Library - <b>spring-security-crypto-5.6.1.jar</b></p> <p>Spring Security</p> <p>Library home page: <a href="https://spring.io/projects/spring-security">https://spring.io/projects/spring-security</a></p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework.security/spring-security-crypto/5.6.1/b9dc3cc09643c0451a35bdc9327e80c4f5dfd354/spring-security-crypto-5.6.1.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - spring-security-web-5.6.1.jar - spring-security-core-5.6.1.jar - :x: **spring-security-crypto-5.6.1.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Spring Security versions 5.5.x prior to 5.5.7, 5.6.x prior to 5.6.4, and earlier unsupported versions contain an integer overflow vulnerability. When using the BCrypt class with the maximum work factor (31), the encoder does not perform any salt rounds, due to an integer overflow error. The default settings are not affected by this CVE. <p>Publish Date: 2022-05-19 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22976>CVE-2022-22976</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.3</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: Low - 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://tanzu.vmware.com/security/cve-2022-22976">https://tanzu.vmware.com/security/cve-2022-22976</a></p> <p>Release Date: 2022-05-19</p> <p>Fix Resolution: org.springframework.security:spring-security-crypto:5.5.7,5.6.4</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2023-27904</summary> ### Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> Dependency Hierarchy: - :x: **jenkins-core-2.332.3.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Jenkins 2.393 and earlier, LTS 2.375.3 and earlier prints an error stack trace on agent-related pages when agent connections are broken, potentially revealing information about Jenkins configuration that is otherwise inaccessible to attackers. <p>Publish Date: 2023-03-10 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-27904>CVE-2023-27904</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.3</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: Low - 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://www.jenkins.io/security/advisory/2023-03-08/#SECURITY-2120">https://www.jenkins.io/security/advisory/2023-03-08/#SECURITY-2120</a></p> <p>Release Date: 2023-03-10</p> <p>Fix Resolution: org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-22970</summary> ### Vulnerable Libraries - <b>spring-core-5.3.14.jar</b>, <b>spring-beans-5.3.14.jar</b></p> <p> ### <b>spring-core-5.3.14.jar</b></p> <p>Spring Core</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-core/5.3.14/d87ad19f9d8b9a3f1a143db5a2be34c61751aaa2/spring-core-5.3.14.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - spring-security-web-5.6.1.jar - :x: **spring-core-5.3.14.jar** (Vulnerable Library) ### <b>spring-beans-5.3.14.jar</b></p> <p>Spring Beans</p> <p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-beans/5.3.14/24cc27af89edc1581a57bb15bc160d2353f40a0e/spring-beans-5.3.14.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - spring-security-web-5.6.1.jar - :x: **spring-beans-5.3.14.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> In spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, applications that handle file uploads are vulnerable to DoS attack if they rely on data binding to set a MultipartFile or javax.servlet.Part to a field in a model object. <p>Publish Date: 2022-05-12 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22970>CVE-2022-22970</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - 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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://tanzu.vmware.com/security/cve-2022-22970">https://tanzu.vmware.com/security/cve-2022-22970</a></p> <p>Release Date: 2022-05-12</p> <p>Fix Resolution: org.springframework:spring-beans:5.2.22,5.3.20;org.springframework:spring-core:5.2.22,5.3.20</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2023-27903</summary> ### Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> Dependency Hierarchy: - :x: **jenkins-core-2.332.3.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Jenkins 2.393 and earlier, LTS 2.375.3 and earlier creates a temporary file in the default temporary directory with the default permissions for newly created files when uploading a file parameter through the CLI, potentially allowing attackers with access to the Jenkins controller file system to read and write the file before it is used. <p>Publish Date: 2023-03-10 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-27903>CVE-2023-27903</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>4.4</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - 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/advisories/GHSA-584m-7r4m-8j6v"> https://github.com/advisories/GHSA-584m-7r4m-8j6v</a></p> <p>Release Date: 2023-03-10</p> <p>Fix Resolution: org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2023-27902</summary> ### Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> Dependency Hierarchy: - :x: **jenkins-core-2.332.3.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Jenkins 2.393 and earlier, LTS 2.375.3 and earlier shows temporary directories related to job workspaces, which allows attackers with Item/Workspace permission to access their contents. <p>Publish Date: 2023-03-10 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-27902>CVE-2023-27902</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>4.3</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: Low - 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> </details> *** <p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>
True
jenkins-core-2.332.3.jar: 20 vulnerabilities (highest severity is: 9.8) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p></summary> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p></details> ## Vulnerabilities | CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (jenkins-core version) | Remediation Available | | ------------- | ------------- | ----- | ----- | ----- | ------------- | --- | | [CVE-2022-22978](https://www.mend.io/vulnerability-database/CVE-2022-22978) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | spring-security-web-5.6.1.jar | Transitive | N/A* | &#10060; | | [CVE-2022-22965](https://www.mend.io/vulnerability-database/CVE-2022-22965) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | spring-beans-5.3.14.jar | Transitive | N/A* | &#10060; | | [CVE-2022-31692](https://www.mend.io/vulnerability-database/CVE-2022-31692) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | spring-security-web-5.6.1.jar | Transitive | N/A* | &#10060; | | [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.19.jar | Transitive | N/A* | &#10060; | | [CVE-2022-34174](https://www.mend.io/vulnerability-database/CVE-2022-34174) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | jenkins-core-2.332.3.jar | Direct | org.jenkins-ci.main:jenkins-core:2.356,2.332.4 | &#9989; | | [CVE-2023-27901](https://www.mend.io/vulnerability-database/CVE-2023-27901) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | jenkins-core-2.332.3.jar | Direct | org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394 | &#9989; | | [CVE-2023-24998](https://www.mend.io/vulnerability-database/CVE-2023-24998) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | commons-fileupload-1.4.jar | Transitive | N/A* | &#10060; | | [CVE-2023-27900](https://www.mend.io/vulnerability-database/CVE-2023-27900) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | jenkins-core-2.332.3.jar | Direct | org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394 | &#9989; | | [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.19.jar | Transitive | N/A* | &#10060; | | [CVE-2023-27899](https://www.mend.io/vulnerability-database/CVE-2023-27899) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.0 | jenkins-core-2.332.3.jar | Direct | org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394 | &#9989; | | [CVE-2022-22950](https://www.mend.io/vulnerability-database/CVE-2022-22950) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | spring-expression-5.3.14.jar | Transitive | N/A* | &#10060; | | [CVE-2022-34170](https://www.mend.io/vulnerability-database/CVE-2022-34170) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | jenkins-core-2.332.3.jar | Direct | org.jenkins-ci.main:jenkins-core:2.356,2.332.4,2.346.1 | &#9989; | | [CVE-2022-34171](https://www.mend.io/vulnerability-database/CVE-2022-34171) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | jenkins-core-2.332.3.jar | Direct | org.jenkins-ci.main:jenkins-core:2.356,2.332.4,2.346.1 | &#9989; | | [CVE-2023-27898](https://www.mend.io/vulnerability-database/CVE-2023-27898) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.4 | jenkins-core-2.332.3.jar | Direct | org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394 | &#9989; | | [CVE-2022-22968](https://www.mend.io/vulnerability-database/CVE-2022-22968) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | spring-context-5.3.14.jar | Transitive | N/A* | &#10060; | | [CVE-2022-22976](https://www.mend.io/vulnerability-database/CVE-2022-22976) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | spring-security-crypto-5.6.1.jar | Transitive | N/A* | &#10060; | | [CVE-2023-27904](https://www.mend.io/vulnerability-database/CVE-2023-27904) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | jenkins-core-2.332.3.jar | Direct | org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394 | &#9989; | | [CVE-2022-22970](https://www.mend.io/vulnerability-database/CVE-2022-22970) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | detected in multiple dependencies | Transitive | N/A* | &#10060; | | [CVE-2023-27903](https://www.mend.io/vulnerability-database/CVE-2023-27903) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 4.4 | jenkins-core-2.332.3.jar | Direct | org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394 | &#9989; | | [CVE-2023-27902](https://www.mend.io/vulnerability-database/CVE-2023-27902) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 4.3 | jenkins-core-2.332.3.jar | Direct | N/A | &#10060; | <p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.</p> ## Details <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-22978</summary> ### Vulnerable Library - <b>spring-security-web-5.6.1.jar</b></p> <p>Spring Security</p> <p>Library home page: <a href="https://spring.io/projects/spring-security">https://spring.io/projects/spring-security</a></p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework.security/spring-security-web/5.6.1/7c2a899cfa8c986170721fedf356a73f73ddcb23/spring-security-web-5.6.1.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - :x: **spring-security-web-5.6.1.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> In Spring Security versions 5.5.6 and 5.6.3 and older unsupported versions, RegexRequestMatcher can easily be misconfigured to be bypassed on some servlet containers. Applications using RegexRequestMatcher with `.` in the regular expression are possibly vulnerable to an authorization bypass <p>Publish Date: 2022-05-19 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22978>CVE-2022-22978</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://tanzu.vmware.com/security/cve-2022-22978">https://tanzu.vmware.com/security/cve-2022-22978</a></p> <p>Release Date: 2022-05-19</p> <p>Fix Resolution: org.springframework.security:spring-security-web:5.5.7,5.6.4</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-22965</summary> ### Vulnerable Library - <b>spring-beans-5.3.14.jar</b></p> <p>Spring Beans</p> <p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-beans/5.3.14/24cc27af89edc1581a57bb15bc160d2353f40a0e/spring-beans-5.3.14.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - spring-security-web-5.6.1.jar - :x: **spring-beans-5.3.14.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> A Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data binding. The specific exploit requires the application to run on Tomcat as a WAR deployment. If the application is deployed as a Spring Boot executable jar, i.e. the default, it is not vulnerable to the exploit. However, the nature of the vulnerability is more general, and there may be other ways to exploit it. <p>Publish Date: 2022-04-01 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22965>CVE-2022-22965</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://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement">https://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement</a></p> <p>Release Date: 2022-04-01</p> <p>Fix Resolution: org.springframework:spring-beans:5.2.20.RELEASE,5.3.18</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-31692</summary> ### Vulnerable Library - <b>spring-security-web-5.6.1.jar</b></p> <p>Spring Security</p> <p>Library home page: <a href="https://spring.io/projects/spring-security">https://spring.io/projects/spring-security</a></p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework.security/spring-security-web/5.6.1/7c2a899cfa8c986170721fedf356a73f73ddcb23/spring-security-web-5.6.1.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - :x: **spring-security-web-5.6.1.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Spring Security, versions 5.7 prior to 5.7.5 and 5.6 prior to 5.6.9 could be susceptible to authorization rules bypass via forward or include dispatcher types. Specifically, an application is vulnerable when all of the following are true: The application expects that Spring Security applies security to forward and include dispatcher types. The application uses the AuthorizationFilter either manually or via the authorizeHttpRequests() method. The application configures the FilterChainProxy to apply to forward and/or include requests (e.g. spring.security.filter.dispatcher-types = request, error, async, forward, include). The application may forward or include the request to a higher privilege-secured endpoint.The application configures Spring Security to apply to every dispatcher type via authorizeHttpRequests().shouldFilterAllDispatcherTypes(true) <p>Publish Date: 2022-10-31 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-31692>CVE-2022-31692</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://tanzu.vmware.com/security/cve-2022-31692">https://tanzu.vmware.com/security/cve-2022-31692</a></p> <p>Release Date: 2022-10-31</p> <p>Fix Resolution: org.springframework.security:spring-security-web:5.6.9,5.7.5</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-41966</summary> ### Vulnerable Library - <b>xstream-1.4.19.jar</b></p> <p></p> <p>Library home page: <a href="http://x-stream.github.io">http://x-stream.github.io</a></p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.thoughtworks.xstream/xstream/1.4.19/e0e581d812aa92ae12f07234f3398e06af74b112/xstream-1.4.19.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - :x: **xstream-1.4.19.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> XStream serializes Java objects to XML and back again. Versions prior to 1.4.20 may allow a remote attacker to terminate the application with a stack overflow error, resulting in a denial of service only via manipulation the processed input stream. The attack uses the hash code implementation for collections and maps to force recursive hash calculation causing a stack overflow. This issue is patched in version 1.4.20 which handles the stack overflow and raises an InputManipulationException instead. A potential workaround for users who only use HashMap or HashSet and whose XML refers these only as default map or set, is to change the default implementation of java.util.Map and java.util per the code example in the referenced advisory. However, this implies that your application does not care about the implementation of the map and all elements are comparable. <p>Publish Date: 2022-12-28 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-41966>CVE-2022-41966</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</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: 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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-j563-grx4-pjpv">https://github.com/advisories/GHSA-j563-grx4-pjpv</a></p> <p>Release Date: 2022-12-28</p> <p>Fix Resolution: com.thoughtworks.xstream:xstream:1.4.20</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-34174</summary> ### Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> Dependency Hierarchy: - :x: **jenkins-core-2.332.3.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> In Jenkins 2.355 and earlier, LTS 2.332.3 and earlier, an observable timing discrepancy on the login form allows distinguishing between login attempts with an invalid username, and login attempts with a valid username and wrong password, when using the Jenkins user database security realm. <p>Publish Date: 2022-06-23 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-34174>CVE-2022-34174</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</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: 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://www.jenkins.io/security/advisory/2022-06-22/#SECURITY-2781">https://www.jenkins.io/security/advisory/2022-06-22/#SECURITY-2781</a></p> <p>Release Date: 2022-06-23</p> <p>Fix Resolution: org.jenkins-ci.main:jenkins-core:2.356,2.332.4</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2023-27901</summary> ### Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> Dependency Hierarchy: - :x: **jenkins-core-2.332.3.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Jenkins 2.393 and earlier, LTS 2.375.3 and earlier uses the Apache Commons FileUpload library without specifying limits for the number of request parts introduced in version 1.5 for CVE-2023-24998 in org.kohsuke.stapler.RequestImpl, allowing attackers to trigger a denial of service. <p>Publish Date: 2023-03-10 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-27901>CVE-2023-27901</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</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: 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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-h76p-mc68-jv3p">https://github.com/advisories/GHSA-h76p-mc68-jv3p</a></p> <p>Release Date: 2023-03-10</p> <p>Fix Resolution: org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2023-24998</summary> ### Vulnerable Library - <b>commons-fileupload-1.4.jar</b></p> <p>The Apache Commons FileUpload component provides a simple yet flexible means of adding support for multipart file upload functionality to servlets and web applications.</p> <p>Library home page: <a href="http://commons.apache.org/proper/commons-fileupload/">http://commons.apache.org/proper/commons-fileupload/</a></p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/commons-fileupload/commons-fileupload/1.4/f95188e3d372e20e7328706c37ef366e5d7859b0/commons-fileupload-1.4.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - :x: **commons-fileupload-1.4.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Apache Commons FileUpload before 1.5 does not limit the number of request parts to be processed resulting in the possibility of an attacker triggering a DoS with a malicious upload or series of uploads. Note that, like all of the file upload limits, the new configuration option (FileUploadBase#setFileCountMax) is not enabled by default and must be explicitly configured. <p>Publish Date: 2023-02-20 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-24998>CVE-2023-24998</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</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: 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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://seclists.org/oss-sec/2023/q1/108">https://seclists.org/oss-sec/2023/q1/108</a></p> <p>Release Date: 2023-02-20</p> <p>Fix Resolution: commons-fileupload:commons-fileupload:1.5;org.apache.tomcat:tomcat-coyote:8.5.85,9.0.71,10.1.5</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2023-27900</summary> ### Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> Dependency Hierarchy: - :x: **jenkins-core-2.332.3.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Jenkins 2.393 and earlier, LTS 2.375.3 and earlier uses the Apache Commons FileUpload library without specifying limits for the number of request parts introduced in version 1.5 for CVE-2023-24998 in hudson.util.MultipartFormDataParser, allowing attackers to trigger a denial of service. <p>Publish Date: 2023-03-10 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-27900>CVE-2023-27900</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</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: 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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://www.jenkins.io/security/advisory/2023-03-08/#SECURITY-2120">https://www.jenkins.io/security/advisory/2023-03-08/#SECURITY-2120</a></p> <p>Release Date: 2023-03-10</p> <p>Fix Resolution: org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-40151</summary> ### Vulnerable Library - <b>xstream-1.4.19.jar</b></p> <p></p> <p>Library home page: <a href="http://x-stream.github.io">http://x-stream.github.io</a></p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.thoughtworks.xstream/xstream/1.4.19/e0e581d812aa92ae12f07234f3398e06af74b112/xstream-1.4.19.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - :x: **xstream-1.4.19.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Those using Xstream to seralize XML data may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow. This effect may support a denial of service attack. <p>Publish Date: 2022-09-16 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-40151>CVE-2022-40151</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</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: 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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-f8cc-g7j8-xxpm">https://github.com/advisories/GHSA-f8cc-g7j8-xxpm</a></p> <p>Release Date: 2022-09-16</p> <p>Fix Resolution: com.thoughtworks.xstream:xstream:1.4.20</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2023-27899</summary> ### Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> Dependency Hierarchy: - :x: **jenkins-core-2.332.3.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Jenkins 2.393 and earlier, LTS 2.375.3 and earlier creates a temporary file in the default temporary directory with the default permissions for newly created files when uploading a plugin for installation, potentially allowing attackers with access to the Jenkins controller file system to read and write the file before it is used, potentially resulting in arbitrary code execution. <p>Publish Date: 2023-03-10 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-27899>CVE-2023-27899</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.0</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: High - 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-hf9h-vv4m-2f33">https://github.com/advisories/GHSA-hf9h-vv4m-2f33</a></p> <p>Release Date: 2023-03-10</p> <p>Fix Resolution: org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-22950</summary> ### Vulnerable Library - <b>spring-expression-5.3.14.jar</b></p> <p>Spring Expression Language (SpEL)</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-expression/5.3.14/5cd4c568522b7084afac5d2ac6cb945b797b3f16/spring-expression-5.3.14.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - spring-security-web-5.6.1.jar - :x: **spring-expression-5.3.14.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> n Spring Framework versions 5.3.0 - 5.3.16 and older unsupported versions, it is possible for a user to provide a specially crafted SpEL expression that may cause a denial of service condition. <p>Publish Date: 2022-04-01 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22950>CVE-2022-22950</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.5</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: 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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://tanzu.vmware.com/security/cve-2022-22950">https://tanzu.vmware.com/security/cve-2022-22950</a></p> <p>Release Date: 2022-04-01</p> <p>Fix Resolution: org.springframework:spring-expression:5.2.20,5.3.17</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-34170</summary> ### Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> Dependency Hierarchy: - :x: **jenkins-core-2.332.3.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> In Jenkins 2.320 through 2.355 (both inclusive) and LTS 2.332.1 through LTS 2.332.3 (both inclusive) the help icon does not escape the feature name that is part of its tooltip, effectively undoing the fix for SECURITY-1955, resulting in a cross-site scripting (XSS) vulnerability exploitable by attackers with Job/Configure permission. <p>Publish Date: 2022-06-23 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-34170>CVE-2022-34170</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - 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://www.jenkins.io/security/advisory/2022-06-22/#SECURITY-2781">https://www.jenkins.io/security/advisory/2022-06-22/#SECURITY-2781</a></p> <p>Release Date: 2022-06-23</p> <p>Fix Resolution: org.jenkins-ci.main:jenkins-core:2.356,2.332.4,2.346.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-34171</summary> ### Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> Dependency Hierarchy: - :x: **jenkins-core-2.332.3.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> In Jenkins 2.321 through 2.355 (both inclusive) and LTS 2.332.1 through LTS 2.332.3 (both inclusive) the HTML output generated for new symbol-based SVG icons includes the 'title' attribute of 'l:ionicon' (until Jenkins 2.334) and 'alt' attribute of 'l:icon' (since Jenkins 2.335) without further escaping, resulting in a cross-site scripting (XSS) vulnerability. <p>Publish Date: 2022-06-23 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-34171>CVE-2022-34171</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - 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://www.jenkins.io/security/advisory/2022-06-22/#SECURITY-2781">https://www.jenkins.io/security/advisory/2022-06-22/#SECURITY-2781</a></p> <p>Release Date: 2022-06-23</p> <p>Fix Resolution: org.jenkins-ci.main:jenkins-core:2.356,2.332.4,2.346.1</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2023-27898</summary> ### Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> Dependency Hierarchy: - :x: **jenkins-core-2.332.3.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Jenkins 2.270 through 2.393 (both inclusive), LTS 2.277.1 through 2.375.3 (both inclusive) does not escape the Jenkins version a plugin depends on when rendering the error message stating its incompatibility with the current version of Jenkins, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to provide plugins to the configured update sites and have this message shown by Jenkins instances. <p>Publish Date: 2023-03-10 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-27898>CVE-2023-27898</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.4</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - 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://www.jenkins.io/security/advisory/2023-03-08/#SECURITY-3037">https://www.jenkins.io/security/advisory/2023-03-08/#SECURITY-3037</a></p> <p>Release Date: 2023-03-10</p> <p>Fix Resolution: org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-22968</summary> ### Vulnerable Library - <b>spring-context-5.3.14.jar</b></p> <p>Spring Context</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-context/5.3.14/ce6042492f042131f602bdc83fcb412b142bdac5/spring-context-5.3.14.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - spring-security-web-5.6.1.jar - :x: **spring-context-5.3.14.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> In Spring Framework versions 5.3.0 - 5.3.18, 5.2.0 - 5.2.20, and older unsupported versions, the patterns for disallowedFields on a DataBinder are case sensitive which means a field is not effectively protected unless it is listed with both upper and lower case for the first character of the field, including upper and lower case for the first character of all nested fields within the property path. <p>Publish Date: 2022-04-14 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22968>CVE-2022-22968</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.3</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: None - Integrity Impact: Low - 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://tanzu.vmware.com/security/cve-2022-22968">https://tanzu.vmware.com/security/cve-2022-22968</a></p> <p>Release Date: 2022-04-14</p> <p>Fix Resolution: org.springframework:spring-context:5.2.21,5.3.19</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-22976</summary> ### Vulnerable Library - <b>spring-security-crypto-5.6.1.jar</b></p> <p>Spring Security</p> <p>Library home page: <a href="https://spring.io/projects/spring-security">https://spring.io/projects/spring-security</a></p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework.security/spring-security-crypto/5.6.1/b9dc3cc09643c0451a35bdc9327e80c4f5dfd354/spring-security-crypto-5.6.1.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - spring-security-web-5.6.1.jar - spring-security-core-5.6.1.jar - :x: **spring-security-crypto-5.6.1.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Spring Security versions 5.5.x prior to 5.5.7, 5.6.x prior to 5.6.4, and earlier unsupported versions contain an integer overflow vulnerability. When using the BCrypt class with the maximum work factor (31), the encoder does not perform any salt rounds, due to an integer overflow error. The default settings are not affected by this CVE. <p>Publish Date: 2022-05-19 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22976>CVE-2022-22976</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.3</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: Low - 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://tanzu.vmware.com/security/cve-2022-22976">https://tanzu.vmware.com/security/cve-2022-22976</a></p> <p>Release Date: 2022-05-19</p> <p>Fix Resolution: org.springframework.security:spring-security-crypto:5.5.7,5.6.4</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2023-27904</summary> ### Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> Dependency Hierarchy: - :x: **jenkins-core-2.332.3.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Jenkins 2.393 and earlier, LTS 2.375.3 and earlier prints an error stack trace on agent-related pages when agent connections are broken, potentially revealing information about Jenkins configuration that is otherwise inaccessible to attackers. <p>Publish Date: 2023-03-10 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-27904>CVE-2023-27904</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.3</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: Low - 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://www.jenkins.io/security/advisory/2023-03-08/#SECURITY-2120">https://www.jenkins.io/security/advisory/2023-03-08/#SECURITY-2120</a></p> <p>Release Date: 2023-03-10</p> <p>Fix Resolution: org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-22970</summary> ### Vulnerable Libraries - <b>spring-core-5.3.14.jar</b>, <b>spring-beans-5.3.14.jar</b></p> <p> ### <b>spring-core-5.3.14.jar</b></p> <p>Spring Core</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-core/5.3.14/d87ad19f9d8b9a3f1a143db5a2be34c61751aaa2/spring-core-5.3.14.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - spring-security-web-5.6.1.jar - :x: **spring-core-5.3.14.jar** (Vulnerable Library) ### <b>spring-beans-5.3.14.jar</b></p> <p>Spring Beans</p> <p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-beans/5.3.14/24cc27af89edc1581a57bb15bc160d2353f40a0e/spring-beans-5.3.14.jar</p> <p> Dependency Hierarchy: - jenkins-core-2.332.3.jar (Root Library) - spring-security-web-5.6.1.jar - :x: **spring-beans-5.3.14.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> In spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, applications that handle file uploads are vulnerable to DoS attack if they rely on data binding to set a MultipartFile or javax.servlet.Part to a field in a model object. <p>Publish Date: 2022-05-12 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22970>CVE-2022-22970</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - 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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://tanzu.vmware.com/security/cve-2022-22970">https://tanzu.vmware.com/security/cve-2022-22970</a></p> <p>Release Date: 2022-05-12</p> <p>Fix Resolution: org.springframework:spring-beans:5.2.22,5.3.20;org.springframework:spring-core:5.2.22,5.3.20</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2023-27903</summary> ### Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> Dependency Hierarchy: - :x: **jenkins-core-2.332.3.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Jenkins 2.393 and earlier, LTS 2.375.3 and earlier creates a temporary file in the default temporary directory with the default permissions for newly created files when uploading a file parameter through the CLI, potentially allowing attackers with access to the Jenkins controller file system to read and write the file before it is used. <p>Publish Date: 2023-03-10 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-27903>CVE-2023-27903</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>4.4</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - 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/advisories/GHSA-584m-7r4m-8j6v"> https://github.com/advisories/GHSA-584m-7r4m-8j6v</a></p> <p>Release Date: 2023-03-10</p> <p>Fix Resolution: org.jenkins-ci.main:jenkins-core:2.375.4,2.387.1,2.394</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2023-27902</summary> ### Vulnerable Library - <b>jenkins-core-2.332.3.jar</b></p> <p>Jenkins core code and view files to render HTML.</p> <p>Path to dependency file: /build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jenkins-ci.main/jenkins-core/2.332.3/cc338a1f79bf926a95b7e3343c1334fb0c30cce2/jenkins-core-2.332.3.jar</p> <p> Dependency Hierarchy: - :x: **jenkins-core-2.332.3.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/opensearch-build-libraries/commit/26696d30ae3a174047ee21ec6573e9b8b0bc1d1e">26696d30ae3a174047ee21ec6573e9b8b0bc1d1e</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Jenkins 2.393 and earlier, LTS 2.375.3 and earlier shows temporary directories related to job workspaces, which allows attackers with Item/Workspace permission to access their contents. <p>Publish Date: 2023-03-10 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-27902>CVE-2023-27902</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>4.3</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: Low - 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> </details> *** <p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>
non_test
jenkins core jar vulnerabilities highest severity is vulnerable library jenkins core jar jenkins core code and view files to render html path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org jenkins ci main jenkins core jenkins core jar found in head commit a href vulnerabilities cve severity cvss dependency type fixed in jenkins core version remediation available high spring security web jar transitive n a high spring beans jar transitive n a high spring security web jar transitive n a high xstream jar transitive n a high jenkins core jar direct org jenkins ci main jenkins core high jenkins core jar direct org jenkins ci main jenkins core high commons fileupload jar transitive n a high jenkins core jar direct org jenkins ci main jenkins core high xstream jar transitive n a high jenkins core jar direct org jenkins ci main jenkins core medium spring expression jar transitive n a medium jenkins core jar direct org jenkins ci main jenkins core medium jenkins core jar direct org jenkins ci main jenkins core medium jenkins core jar direct org jenkins ci main jenkins core medium spring context jar transitive n a medium spring security crypto jar transitive n a medium jenkins core jar direct org jenkins ci main jenkins core medium detected in multiple dependencies transitive n a medium jenkins core jar direct org jenkins ci main jenkins core medium jenkins core jar direct n a for some transitive vulnerabilities there is no version of direct dependency with a fix check the details section below to see if there is a version of transitive dependency where vulnerability is fixed details cve vulnerable library spring security web jar spring security library home page a href path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org springframework security spring security web spring security web jar dependency hierarchy jenkins core jar root library x spring security web jar vulnerable library found in head commit a href found in base branch main vulnerability details in spring security versions and and older unsupported versions regexrequestmatcher can easily be misconfigured to be bypassed on some servlet containers applications using regexrequestmatcher with in the regular expression are possibly vulnerable to an authorization bypass 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 org springframework security spring security web cve vulnerable library spring beans jar spring beans library home page a href path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org springframework spring beans spring beans jar dependency hierarchy jenkins core jar root library spring security web jar x spring beans jar vulnerable library found in head commit a href found in base branch main vulnerability details a spring mvc or spring webflux application running on jdk may be vulnerable to remote code execution rce via data binding the specific exploit requires the application to run on tomcat as a war deployment if the application is deployed as a spring boot executable jar i e the default it is not vulnerable to the exploit however the nature of the vulnerability is more general and there may be other ways to exploit it 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 org springframework spring beans release cve vulnerable library spring security web jar spring security library home page a href path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org springframework security spring security web spring security web jar dependency hierarchy jenkins core jar root library x spring security web jar vulnerable library found in head commit a href found in base branch main vulnerability details spring security versions prior to and prior to could be susceptible to authorization rules bypass via forward or include dispatcher types specifically an application is vulnerable when all of the following are true the application expects that spring security applies security to forward and include dispatcher types the application uses the authorizationfilter either manually or via the authorizehttprequests method the application configures the filterchainproxy to apply to forward and or include requests e g spring security filter dispatcher types request error async forward include the application may forward or include the request to a higher privilege secured endpoint the application configures spring security to apply to every dispatcher type via authorizehttprequests shouldfilteralldispatchertypes true 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 org springframework security spring security web cve vulnerable library xstream jar library home page a href path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files com thoughtworks xstream xstream xstream jar dependency hierarchy jenkins core jar root library x xstream jar vulnerable library found in head commit a href found in base branch main vulnerability details xstream serializes java objects to xml and back again versions prior to may allow a remote attacker to terminate the application with a stack overflow error resulting in a denial of service only via manipulation the processed input stream the attack uses the hash code implementation for collections and maps to force recursive hash calculation causing a stack overflow this issue is patched in version which handles the stack overflow and raises an inputmanipulationexception instead a potential workaround for users who only use hashmap or hashset and whose xml refers these only as default map or set is to change the default implementation of java util map and java util per the code example in the referenced advisory however this implies that your application does not care about the implementation of the map and all elements are comparable 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 com thoughtworks xstream xstream cve vulnerable library jenkins core jar jenkins core code and view files to render html path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org jenkins ci main jenkins core jenkins core jar dependency hierarchy x jenkins core jar vulnerable library found in head commit a href found in base branch main vulnerability details in jenkins and earlier lts and earlier an observable timing discrepancy on the login form allows distinguishing between login attempts with an invalid username and login attempts with a valid username and wrong password when using the jenkins user database security realm 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 none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org jenkins ci main jenkins core rescue worker helmet automatic remediation is available for this issue cve vulnerable library jenkins core jar jenkins core code and view files to render html path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org jenkins ci main jenkins core jenkins core jar dependency hierarchy x jenkins core jar vulnerable library found in head commit a href found in base branch main vulnerability details jenkins and earlier lts and earlier uses the apache commons fileupload library without specifying limits for the number of request parts introduced in version for cve in org kohsuke stapler requestimpl allowing attackers to trigger a denial of service 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 org jenkins ci main jenkins core rescue worker helmet automatic remediation is available for this issue cve vulnerable library commons fileupload jar the apache commons fileupload component provides a simple yet flexible means of adding support for multipart file upload functionality to servlets and web applications library home page a href path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files commons fileupload commons fileupload commons fileupload jar dependency hierarchy jenkins core jar root library x commons fileupload jar vulnerable library found in head commit a href found in base branch main vulnerability details apache commons fileupload before does not limit the number of request parts to be processed resulting in the possibility of an attacker triggering a dos with a malicious upload or series of uploads note that like all of the file upload limits the new configuration option fileuploadbase setfilecountmax is not enabled by default and must be explicitly configured 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 commons fileupload commons fileupload org apache tomcat tomcat coyote cve vulnerable library jenkins core jar jenkins core code and view files to render html path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org jenkins ci main jenkins core jenkins core jar dependency hierarchy x jenkins core jar vulnerable library found in head commit a href found in base branch main vulnerability details jenkins and earlier lts and earlier uses the apache commons fileupload library without specifying limits for the number of request parts introduced in version for cve in hudson util multipartformdataparser allowing attackers to trigger a denial of service 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 org jenkins ci main jenkins core rescue worker helmet automatic remediation is available for this issue cve vulnerable library xstream jar library home page a href path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files com thoughtworks xstream xstream xstream jar dependency hierarchy jenkins core jar root library x xstream jar vulnerable library found in head commit a href found in base branch main vulnerability details those using xstream to seralize xml data may be vulnerable to denial of service attacks dos if the parser is running on user supplied input an attacker may supply content that causes the parser to crash by stackoverflow this effect may support a denial of service attack 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 com thoughtworks xstream xstream cve vulnerable library jenkins core jar jenkins core code and view files to render html path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org jenkins ci main jenkins core jenkins core jar dependency hierarchy x jenkins core jar vulnerable library found in head commit a href found in base branch main vulnerability details jenkins and earlier lts and earlier creates a temporary file in the default temporary directory with the default permissions for newly created files when uploading a plugin for installation potentially allowing attackers with access to the jenkins controller file system to read and write the file before it is used potentially resulting in arbitrary code execution publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high 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 org jenkins ci main jenkins core rescue worker helmet automatic remediation is available for this issue cve vulnerable library spring expression jar spring expression language spel path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org springframework spring expression spring expression jar dependency hierarchy jenkins core jar root library spring security web jar x spring expression jar vulnerable library found in head commit a href found in base branch main vulnerability details n spring framework versions and older unsupported versions it is possible for a user to provide a specially crafted spel expression that may cause a denial of service condition 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 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 org springframework spring expression cve vulnerable library jenkins core jar jenkins core code and view files to render html path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org jenkins ci main jenkins core jenkins core jar dependency hierarchy x jenkins core jar vulnerable library found in head commit a href found in base branch main vulnerability details in jenkins through both inclusive and lts through lts both inclusive the help icon does not escape the feature name that is part of its tooltip effectively undoing the fix for security resulting in a cross site scripting xss vulnerability exploitable by attackers with job configure permission publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org jenkins ci main jenkins core rescue worker helmet automatic remediation is available for this issue cve vulnerable library jenkins core jar jenkins core code and view files to render html path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org jenkins ci main jenkins core jenkins core jar dependency hierarchy x jenkins core jar vulnerable library found in head commit a href found in base branch main vulnerability details in jenkins through both inclusive and lts through lts both inclusive the html output generated for new symbol based svg icons includes the title attribute of l ionicon until jenkins and alt attribute of l icon since jenkins without further escaping resulting in a cross site scripting xss vulnerability publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org jenkins ci main jenkins core rescue worker helmet automatic remediation is available for this issue cve vulnerable library jenkins core jar jenkins core code and view files to render html path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org jenkins ci main jenkins core jenkins core jar dependency hierarchy x jenkins core jar vulnerable library found in head commit a href found in base branch main vulnerability details jenkins through both inclusive lts through both inclusive does not escape the jenkins version a plugin depends on when rendering the error message stating its incompatibility with the current version of jenkins resulting in a stored cross site scripting xss vulnerability exploitable by attackers able to provide plugins to the configured update sites and have this message shown by jenkins instances publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org jenkins ci main jenkins core rescue worker helmet automatic remediation is available for this issue cve vulnerable library spring context jar spring context path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org springframework spring context spring context jar dependency hierarchy jenkins core jar root library spring security web jar x spring context jar vulnerable library found in head commit a href found in base branch main vulnerability details in spring framework versions and older unsupported versions the patterns for disallowedfields on a databinder are case sensitive which means a field is not effectively protected unless it is listed with both upper and lower case for the first character of the field including upper and lower case for the first character of all nested fields within the property 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 none integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org springframework spring context cve vulnerable library spring security crypto jar spring security library home page a href path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org springframework security spring security crypto spring security crypto jar dependency hierarchy jenkins core jar root library spring security web jar spring security core jar x spring security crypto jar vulnerable library found in head commit a href found in base branch main vulnerability details spring security versions x prior to x prior to and earlier unsupported versions contain an integer overflow vulnerability when using the bcrypt class with the maximum work factor the encoder does not perform any salt rounds due to an integer overflow error the default settings are not affected by this cve 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 low 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 org springframework security spring security crypto cve vulnerable library jenkins core jar jenkins core code and view files to render html path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org jenkins ci main jenkins core jenkins core jar dependency hierarchy x jenkins core jar vulnerable library found in head commit a href found in base branch main vulnerability details jenkins and earlier lts and earlier prints an error stack trace on agent related pages when agent connections are broken potentially revealing information about jenkins configuration that is otherwise inaccessible to attackers 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 low 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 org jenkins ci main jenkins core rescue worker helmet automatic remediation is available for this issue cve vulnerable libraries spring core jar spring beans jar spring core jar spring core path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org springframework spring core spring core jar dependency hierarchy jenkins core jar root library spring security web jar x spring core jar vulnerable library spring beans jar spring beans library home page a href path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org springframework spring beans spring beans jar dependency hierarchy jenkins core jar root library spring security web jar x spring beans jar vulnerable library found in head commit a href found in base branch main vulnerability details in spring framework versions prior to and old unsupported versions applications that handle file uploads are vulnerable to dos attack if they rely on data binding to set a multipartfile or javax servlet part to a field in a model object 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 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 org springframework spring beans org springframework spring core cve vulnerable library jenkins core jar jenkins core code and view files to render html path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org jenkins ci main jenkins core jenkins core jar dependency hierarchy x jenkins core jar vulnerable library found in head commit a href found in base branch main vulnerability details jenkins and earlier lts and earlier creates a temporary file in the default temporary directory with the default permissions for newly created files when uploading a file parameter through the cli potentially allowing attackers with access to the jenkins controller file system to read and write the file before it is used 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 low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org jenkins ci main jenkins core rescue worker helmet automatic remediation is available for this issue cve vulnerable library jenkins core jar jenkins core code and view files to render html path to dependency file build gradle path to vulnerable library home wss scanner gradle caches modules files org jenkins ci main jenkins core jenkins core jar dependency hierarchy x jenkins core jar vulnerable library found in head commit a href found in base branch main vulnerability details jenkins and earlier lts and earlier shows temporary directories related to job workspaces which allows attackers with item workspace permission to access their contents 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 low integrity impact none availability impact none for more information on scores click a href rescue worker helmet automatic remediation is available for this issue
0
90,578
26,141,174,403
IssuesEvent
2022-12-29 18:42:07
ledger/ledger
https://api.github.com/repos/ledger/ledger
opened
GitHub Action fails for macOS
build
It seems the Mac Depencies step of the [macOS GitHub Actions build](https://github.com/ledger/ledger/actions/runs/3800872667/jobs/6464752682) has been failing with the following error recently: ``` Error: The `brew link` step did not complete successfully [324](https://github.com/ledger/ledger/actions/runs/3800872667/jobs/6464752682#step:4:325) The formula built, but is not symlinked into /usr/local [325](https://github.com/ledger/ledger/actions/runs/3800872667/jobs/6464752682#step:4:326) Could not symlink bin/2to3 [326](https://github.com/ledger/ledger/actions/runs/3800872667/jobs/6464752682#step:4:327) Target /usr/local/bin/2to3 [327](https://github.com/ledger/ledger/actions/runs/3800872667/jobs/6464752682#step:4:328) already exists. You may want to remove it: [328](https://github.com/ledger/ledger/actions/runs/3800872667/jobs/6464752682#step:4:329) rm '/usr/local/bin/2to3' ``` I've switch from homebrew to darwin-nix and nixpkgs for quite some time now and might hence be less suited to provide a proper solution to the issue… Yet [installing the dependencies](https://github.com/ledger/ledger/blob/master/.github/workflows/cmake.yml#L47) with the `--force` option: `brew install --force boost boost-python3 gmp mpfr gpgme` might seem a viable solution. Would appreciate if someone on macOS using homebrew could chime in on this.
1.0
GitHub Action fails for macOS - It seems the Mac Depencies step of the [macOS GitHub Actions build](https://github.com/ledger/ledger/actions/runs/3800872667/jobs/6464752682) has been failing with the following error recently: ``` Error: The `brew link` step did not complete successfully [324](https://github.com/ledger/ledger/actions/runs/3800872667/jobs/6464752682#step:4:325) The formula built, but is not symlinked into /usr/local [325](https://github.com/ledger/ledger/actions/runs/3800872667/jobs/6464752682#step:4:326) Could not symlink bin/2to3 [326](https://github.com/ledger/ledger/actions/runs/3800872667/jobs/6464752682#step:4:327) Target /usr/local/bin/2to3 [327](https://github.com/ledger/ledger/actions/runs/3800872667/jobs/6464752682#step:4:328) already exists. You may want to remove it: [328](https://github.com/ledger/ledger/actions/runs/3800872667/jobs/6464752682#step:4:329) rm '/usr/local/bin/2to3' ``` I've switch from homebrew to darwin-nix and nixpkgs for quite some time now and might hence be less suited to provide a proper solution to the issue… Yet [installing the dependencies](https://github.com/ledger/ledger/blob/master/.github/workflows/cmake.yml#L47) with the `--force` option: `brew install --force boost boost-python3 gmp mpfr gpgme` might seem a viable solution. Would appreciate if someone on macOS using homebrew could chime in on this.
non_test
github action fails for macos it seems the mac depencies step of the has been failing with the following error recently error the brew link step did not complete successfully the formula built but is not symlinked into usr local could not symlink bin target usr local bin already exists you may want to remove it rm usr local bin i ve switch from homebrew to darwin nix and nixpkgs for quite some time now and might hence be less suited to provide a proper solution to the issue… yet with the force option brew install force boost boost gmp mpfr gpgme might seem a viable solution would appreciate if someone on macos using homebrew could chime in on this
0
96,021
27,723,005,622
IssuesEvent
2023-03-14 22:28:24
lbl-srg/modelica-buildings
https://api.github.com/repos/lbl-srg/modelica-buildings
opened
Results different when running unit test with Dymola and OpenModelica
OpenBuildingControl
For blocks in `Buildings.Controls.OBC.CDL`, there are results difference when running unit test with `Dymola` and `OpenModelica`. For instance, results from the validation model `Buildings.Controls.OBC.CDL.Continuous.Validation.Greater` below ![Greater](https://user-images.githubusercontent.com/23491921/225154351-da2bfd04-1486-4130-bf49-f9a0f17327d4.png) - In simulation with Dymola, the output changes from `true` to `false` at moment `6.71429s`: ![Screenshot 2023-03-14 at 2 59 31 PM](https://user-images.githubusercontent.com/23491921/225154374-a2dfe073-ea78-4626-963b-f4033292dc21.jpeg) - In simulation with OpenModelica, the output changes from `true` to `false` at moment `7.0s`: ![greater-2](https://user-images.githubusercontent.com/23491921/225154403-18e9a23b-4435-49f9-b95c-86100a1e25d9.png) ------------------- Run unit test as `../bin/runUnitTests.py -s Buildings.Controls.OBC.CDL -t openmodelica -d`, we can see following verification errors: ``` Regression tests are only run for the following package: Buildings.Controls.OBC.CDL *** Error: Buildings_Controls_OBC_CDL_Logical_Sources_Validation_SampleTriggerPositiveStartTime.txt: Errors during result verification. Absolute error = 3.996e+00 at t = 1.0 for triggeredSampler.y *** Error: Buildings_Controls_OBC_CDL_Continuous_Validation_Hysteresis.txt: Errors during result verification. Absolute error = 9.990e-01 at t = 1.0 for hysteresis1.u Absolute error = 9.990e-01 at t = 1.0 for hysteresis2.u Absolute error = 9.990e-01 at t = 1.0 for hysteresis2.y *** Error: Buildings_Controls_OBC_CDL_Continuous_Validation_GreaterThreshold.txt: Errors during result verification. Absolute error = 9.990e-01 at t = 6.9 for gre.y Absolute error = 9.990e-01 at t = 7.2 for greHys.y *** Error: Buildings_Controls_OBC_CDL_Continuous_Validation_IntegratorWithReset.txt: Errors during result verification. Absolute error = 1.988e+00 at t = 0.0 for intDef.y Absolute error = 6.993e+00 at t = 0.0 for intWitRes1.y *** Error: Buildings_Controls_OBC_CDL_Continuous_Validation_Less.txt: Errors during result verification. Absolute error = 9.990e-01 at t = 6.2 for les.y Absolute error = 9.990e-01 at t = 3.2 for lesHys.y *** Error: Buildings_Controls_OBC_CDL_Continuous_Validation_Derivative.txt: Errors during result verification. Absolute error = 2.120e-04 at t = 6.8 for der1.y *** Error: Buildings_Controls_OBC_CDL_Continuous_Validation_LessThreshold.txt: Errors during result verification. Absolute error = 9.990e-01 at t = 2.2 for les.y Absolute error = 9.990e-01 at t = 3.2 for lesHys.y *** Error: Buildings_Controls_OBC_CDL_Continuous_Validation_Greater.txt: Errors during result verification. Absolute error = 9.990e-01 at t = 6.9 for gre.y Absolute error = 9.990e-01 at t = 7.2 for greHys.y Comparison files output by funnel are stored in the directory 'funnel_comp' of size 5.6 MB. Run 'python -c "import buildingspy.development.regressiontest as t; t.Tester(tool=\"openmodelica\").report()"' to access a summary of the comparison results. Script that runs unit tests had 0 warnings and 8 errors. ```
1.0
Results different when running unit test with Dymola and OpenModelica - For blocks in `Buildings.Controls.OBC.CDL`, there are results difference when running unit test with `Dymola` and `OpenModelica`. For instance, results from the validation model `Buildings.Controls.OBC.CDL.Continuous.Validation.Greater` below ![Greater](https://user-images.githubusercontent.com/23491921/225154351-da2bfd04-1486-4130-bf49-f9a0f17327d4.png) - In simulation with Dymola, the output changes from `true` to `false` at moment `6.71429s`: ![Screenshot 2023-03-14 at 2 59 31 PM](https://user-images.githubusercontent.com/23491921/225154374-a2dfe073-ea78-4626-963b-f4033292dc21.jpeg) - In simulation with OpenModelica, the output changes from `true` to `false` at moment `7.0s`: ![greater-2](https://user-images.githubusercontent.com/23491921/225154403-18e9a23b-4435-49f9-b95c-86100a1e25d9.png) ------------------- Run unit test as `../bin/runUnitTests.py -s Buildings.Controls.OBC.CDL -t openmodelica -d`, we can see following verification errors: ``` Regression tests are only run for the following package: Buildings.Controls.OBC.CDL *** Error: Buildings_Controls_OBC_CDL_Logical_Sources_Validation_SampleTriggerPositiveStartTime.txt: Errors during result verification. Absolute error = 3.996e+00 at t = 1.0 for triggeredSampler.y *** Error: Buildings_Controls_OBC_CDL_Continuous_Validation_Hysteresis.txt: Errors during result verification. Absolute error = 9.990e-01 at t = 1.0 for hysteresis1.u Absolute error = 9.990e-01 at t = 1.0 for hysteresis2.u Absolute error = 9.990e-01 at t = 1.0 for hysteresis2.y *** Error: Buildings_Controls_OBC_CDL_Continuous_Validation_GreaterThreshold.txt: Errors during result verification. Absolute error = 9.990e-01 at t = 6.9 for gre.y Absolute error = 9.990e-01 at t = 7.2 for greHys.y *** Error: Buildings_Controls_OBC_CDL_Continuous_Validation_IntegratorWithReset.txt: Errors during result verification. Absolute error = 1.988e+00 at t = 0.0 for intDef.y Absolute error = 6.993e+00 at t = 0.0 for intWitRes1.y *** Error: Buildings_Controls_OBC_CDL_Continuous_Validation_Less.txt: Errors during result verification. Absolute error = 9.990e-01 at t = 6.2 for les.y Absolute error = 9.990e-01 at t = 3.2 for lesHys.y *** Error: Buildings_Controls_OBC_CDL_Continuous_Validation_Derivative.txt: Errors during result verification. Absolute error = 2.120e-04 at t = 6.8 for der1.y *** Error: Buildings_Controls_OBC_CDL_Continuous_Validation_LessThreshold.txt: Errors during result verification. Absolute error = 9.990e-01 at t = 2.2 for les.y Absolute error = 9.990e-01 at t = 3.2 for lesHys.y *** Error: Buildings_Controls_OBC_CDL_Continuous_Validation_Greater.txt: Errors during result verification. Absolute error = 9.990e-01 at t = 6.9 for gre.y Absolute error = 9.990e-01 at t = 7.2 for greHys.y Comparison files output by funnel are stored in the directory 'funnel_comp' of size 5.6 MB. Run 'python -c "import buildingspy.development.regressiontest as t; t.Tester(tool=\"openmodelica\").report()"' to access a summary of the comparison results. Script that runs unit tests had 0 warnings and 8 errors. ```
non_test
results different when running unit test with dymola and openmodelica for blocks in buildings controls obc cdl there are results difference when running unit test with dymola and openmodelica for instance results from the validation model buildings controls obc cdl continuous validation greater below in simulation with dymola the output changes from true to false at moment in simulation with openmodelica the output changes from true to false at moment run unit test as bin rununittests py s buildings controls obc cdl t openmodelica d we can see following verification errors regression tests are only run for the following package buildings controls obc cdl error buildings controls obc cdl logical sources validation sampletriggerpositivestarttime txt errors during result verification absolute error at t for triggeredsampler y error buildings controls obc cdl continuous validation hysteresis txt errors during result verification absolute error at t for u absolute error at t for u absolute error at t for y error buildings controls obc cdl continuous validation greaterthreshold txt errors during result verification absolute error at t for gre y absolute error at t for grehys y error buildings controls obc cdl continuous validation integratorwithreset txt errors during result verification absolute error at t for intdef y absolute error at t for y error buildings controls obc cdl continuous validation less txt errors during result verification absolute error at t for les y absolute error at t for leshys y error buildings controls obc cdl continuous validation derivative txt errors during result verification absolute error at t for y error buildings controls obc cdl continuous validation lessthreshold txt errors during result verification absolute error at t for les y absolute error at t for leshys y error buildings controls obc cdl continuous validation greater txt errors during result verification absolute error at t for gre y absolute error at t for grehys y comparison files output by funnel are stored in the directory funnel comp of size mb run python c import buildingspy development regressiontest as t t tester tool openmodelica report to access a summary of the comparison results script that runs unit tests had warnings and errors
0
342,336
30,615,225,939
IssuesEvent
2023-07-24 02:05:32
Matheus-Azevedo/clinicadoidoso.com.br
https://api.github.com/repos/Matheus-Azevedo/clinicadoidoso.com.br
opened
Revisão e teste da Landing Page
Testing
- [ ] Realizar testes de funcionalidade - [ ] Realizar teste de responsividade em diferentes dispositivos
1.0
Revisão e teste da Landing Page - - [ ] Realizar testes de funcionalidade - [ ] Realizar teste de responsividade em diferentes dispositivos
test
revisão e teste da landing page realizar testes de funcionalidade realizar teste de responsividade em diferentes dispositivos
1
298,848
25,860,850,861
IssuesEvent
2022-12-13 16:50:15
eclipse-openj9/openj9
https://api.github.com/repos/eclipse-openj9/openj9
closed
[JDK18] AssertionError in TestIllegalLink.testTypeMismatch
comp:vm project:panama test excluded jdk18
### OpenJDK Test ``` TEST: java/foreign/TestIllegalLink.java ``` ### Error ``` [2021-11-17T19:30:22.991Z] test TestIllegalLink.testTypeMismatch(()void, (b32[abi/kind=INT])v, "Arity mismatch"): failure [2021-11-17T19:30:22.991Z] java.lang.AssertionError: expected [true] but found [false] [2021-11-17T19:30:22.991Z] at org.testng.Assert.fail(Assert.java:99) [2021-11-17T19:30:22.991Z] at org.testng.Assert.failNotEquals(Assert.java:1037) [2021-11-17T19:30:22.991Z] at org.testng.Assert.assertTrue(Assert.java:45) [2021-11-17T19:30:22.991Z] at org.testng.Assert.assertTrue(Assert.java:55) [2021-11-17T19:30:22.991Z] at TestIllegalLink.testTypeMismatch(TestIllegalLink.java:57) ``` Multiple failures with different type mismatches. Related: https://github.com/eclipse-openj9/openj9/issues/13946
1.0
[JDK18] AssertionError in TestIllegalLink.testTypeMismatch - ### OpenJDK Test ``` TEST: java/foreign/TestIllegalLink.java ``` ### Error ``` [2021-11-17T19:30:22.991Z] test TestIllegalLink.testTypeMismatch(()void, (b32[abi/kind=INT])v, "Arity mismatch"): failure [2021-11-17T19:30:22.991Z] java.lang.AssertionError: expected [true] but found [false] [2021-11-17T19:30:22.991Z] at org.testng.Assert.fail(Assert.java:99) [2021-11-17T19:30:22.991Z] at org.testng.Assert.failNotEquals(Assert.java:1037) [2021-11-17T19:30:22.991Z] at org.testng.Assert.assertTrue(Assert.java:45) [2021-11-17T19:30:22.991Z] at org.testng.Assert.assertTrue(Assert.java:55) [2021-11-17T19:30:22.991Z] at TestIllegalLink.testTypeMismatch(TestIllegalLink.java:57) ``` Multiple failures with different type mismatches. Related: https://github.com/eclipse-openj9/openj9/issues/13946
test
assertionerror in testillegallink testtypemismatch openjdk test test java foreign testillegallink java error test testillegallink testtypemismatch void v arity mismatch failure java lang assertionerror expected but found at org testng assert fail assert java at org testng assert failnotequals assert java at org testng assert asserttrue assert java at org testng assert asserttrue assert java at testillegallink testtypemismatch testillegallink java multiple failures with different type mismatches related
1
22,213
3,941,417,490
IssuesEvent
2016-04-27 07:37:30
jplusplus/detective.io
https://api.github.com/repos/jplusplus/detective.io
closed
Issue topic hostage : export doesn't work
bug need testing
ERROR: type should be string, got " https://www.detective.io/api/afp/hostage-project/v1/summary/export/\r\nUn token semble être généré et est affiché, mais rien ne se passe ensuite. \r\n\r\n\r\n---> Cela semble lié à un problème de date, j'ai trouvé un probleme quand on essaye d'afficher cette page là https://www.detective.io/afp/hostage-project/perpetratororganization/?page=2\r\n\r\nSouci : https://www.detective.io/api/afp/hostage-project/v1/perpetratororganization/\r\nPar contre je n'ai pas trouvé l'ID exact qui plante"
1.0
Issue topic hostage : export doesn't work - https://www.detective.io/api/afp/hostage-project/v1/summary/export/ Un token semble être généré et est affiché, mais rien ne se passe ensuite. ---> Cela semble lié à un problème de date, j'ai trouvé un probleme quand on essaye d'afficher cette page là https://www.detective.io/afp/hostage-project/perpetratororganization/?page=2 Souci : https://www.detective.io/api/afp/hostage-project/v1/perpetratororganization/ Par contre je n'ai pas trouvé l'ID exact qui plante
test
issue topic hostage export doesn t work un token semble être généré et est affiché mais rien ne se passe ensuite cela semble lié à un problème de date j ai trouvé un probleme quand on essaye d afficher cette page là souci par contre je n ai pas trouvé l id exact qui plante
1
140,412
11,320,261,132
IssuesEvent
2020-01-21 03:18:20
supercollider/supercollider
https://api.github.com/repos/supercollider/supercollider
closed
Unit tests fails
comp: test suite
Hello, When running the unit tests of SuperCollider with Guix (I'm packaging SuperCollider for it right now), they fail like: ``` Running tests... /gnu/store/6g4pfzgmgwpfkwix0p7r6j349hffh2gs-cmake-3.7.2/bin/ctest --force-new-ctest-process Test project /tmp/guix-build-supercollider-3.9.1.drv-0/build Start 1: buffer_manager_test_run 1/19 Test #1: buffer_manager_test_run ........................................................................................... Passed 0.03 sec Start 2: callback_interpreter_system_run 2/19 Test #2: callback_interpreter_system_run ................................................................................... Passed 0.02 sec Start 3: memory-pool_test_run 3/19 Test #3: memory-pool_test_run .............................................................................................. Passed 0.02 sec Start 4: server_dsp_thread_queue_test_run 4/19 Test #4: server_dsp_thread_queue_test_run .................................................................................. Passed 1.15 sec Start 5: server_dsp_thread_test_run 5/19 Test #5: server_dsp_thread_test_run ........................................................................................ Passed 4.78 sec Start 6: server_node_graph_test_run 6/19 Test #6: server_node_graph_test_run ........................................................................................ Passed 0.02 sec Start 7: server_scheduler_test_run 7/19 Test #7: server_scheduler_test_run ......................................................................................... Passed 0.47 sec Start 8: server_synth_factory_test_run 8/19 Test #8: server_synth_factory_test_run ..................................................................................... Passed 0.02 sec Start 9: server_test_run 9/19 Test #9: server_test_run ...................................................................................................***Exception: SegFault 0.29 sec SC FFT global init: cosTable initialised. Running 3 test cases... unknown location(0): fatal error: in "server_test_1": memory access violation at address: 0x00000000: no mapping at fault address /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/supernova/server_test.cpp(29): last checkpoint: "server_test_1" entry. *** 1 failure is detected in the test module "Master Test Suite" Start 10: simple_pool_test_run 10/19 Test #10: simple_pool_test_run .............................................................................................. Passed 0.02 sec Start 11: sized_array_test_run 11/19 Test #11: sized_array_test_run .............................................................................................. Passed 0.02 sec Start 12: sndfile_backend_test_run 12/19 Test #12: sndfile_backend_test_run .......................................................................................... Passed 1.02 sec Start 13: static_pool_test_run 13/19 Test #13: static_pool_test_run .............................................................................................. Passed 0.02 sec Start 14: timetag_test_run 14/19 Test #14: timetag_test_run .................................................................................................. Passed 0.02 sec Start 15: perf_counter_test_run 15/19 Test #15: perf_counter_test_run .............................................................................................***Failed 0.02 sec Running 1 test case... unknown location(0): fatal error: in "perf_count_test": std::exception: std::exception /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/supernova/perf_counter_test.cpp(6): last checkpoint: "perf_count_test" entry. *** 1 failure is detected in the test module "Master Test Suite" Start 16: /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_1.scd_run 16/19 Test #16: /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_1.scd_run ............***Exception: Other 0.35 sec /tmp/guix-build-supercollider-3.9.1.drv-0/build/lang/sclang: Relink `/gnu/store/b9ww6qv1ii9v6n45kin7543vkf6jfnd3-libpng-1.6.29/lib/libpng16.so.16' with `/gnu/store/n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25/lib/libpthread.so.0' for IFUNC symbol `longjmp' /tmp/guix-build-supercollider-3.9.1.drv-0/build/lang/sclang: Relink `/gnu/store/1jp44pfmqcj3zycclvmmva3xcwinyg7l-freetype-2.8/lib/libfreetype.so.6' with `/gnu/store/n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25/lib/libpthread.so.0' for IFUNC symbol `longjmp' SC FFT global init: cosTable initialised. Exception while parsing YAML config file: operator[] call on a scalar Exception while parsing YAML config file: operator[] call on a scalar compiling class library... QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/guix-build-supercollider-3.9.1.drv-0/runtime-nixbld' qt.qpa.screen: QXcbConnection: Could not connect to display Could not connect to any X display. terminate called without an active exception Start 17: /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_2.scd_run 17/19 Test #17: /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_2.scd_run ............***Exception: Other 0.20 sec /tmp/guix-build-supercollider-3.9.1.drv-0/build/lang/sclang: Relink `/gnu/store/b9ww6qv1ii9v6n45kin7543vkf6jfnd3-libpng-1.6.29/lib/libpng16.so.16' with `/gnu/store/n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25/lib/libpthread.so.0' for IFUNC symbol `longjmp' /tmp/guix-build-supercollider-3.9.1.drv-0/build/lang/sclang: Relink `/gnu/store/1jp44pfmqcj3zycclvmmva3xcwinyg7l-freetype-2.8/lib/libfreetype.so.6' with `/gnu/store/n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25/lib/libpthread.so.0' for IFUNC symbol `longjmp' SC FFT global init: cosTable initialised. Exception while parsing YAML config file: operator[] call on a scalar Exception while parsing YAML config file: operator[] call on a scalar compiling class library... QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/guix-build-supercollider-3.9.1.drv-0/runtime-nixbld' qt.qpa.screen: QXcbConnection: Could not connect to display Could not connect to any X display. terminate called without an active exception Start 18: /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_3.scd_run 18/19 Test #18: /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_3.scd_run ............***Exception: Other 0.20 sec /tmp/guix-build-supercollider-3.9.1.drv-0/build/lang/sclang: Relink `/gnu/store/b9ww6qv1ii9v6n45kin7543vkf6jfnd3-libpng-1.6.29/lib/libpng16.so.16' with `/gnu/store/n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25/lib/libpthread.so.0' for IFUNC symbol `longjmp' /tmp/guix-build-supercollider-3.9.1.drv-0/build/lang/sclang: Relink `/gnu/store/1jp44pfmqcj3zycclvmmva3xcwinyg7l-freetype-2.8/lib/libfreetype.so.6' with `/gnu/store/n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25/lib/libpthread.so.0' for IFUNC symbol `longjmp' SC FFT global init: cosTable initialised. Exception while parsing YAML config file: operator[] call on a scalar Exception while parsing YAML config file: operator[] call on a scalar compiling class library... QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/guix-build-supercollider-3.9.1.drv-0/runtime-nixbld' qt.qpa.screen: QXcbConnection: Could not connect to display Could not connect to any X display. terminate called without an active exception Start 19: /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_deprecated.scd_run 19/19 Test #19: /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_deprecated.scd_run ...***Exception: Other 0.20 sec /tmp/guix-build-supercollider-3.9.1.drv-0/build/lang/sclang: Relink `/gnu/store/b9ww6qv1ii9v6n45kin7543vkf6jfnd3-libpng-1.6.29/lib/libpng16.so.16' with `/gnu/store/n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25/lib/libpthread.so.0' for IFUNC symbol `longjmp' /tmp/guix-build-supercollider-3.9.1.drv-0/build/lang/sclang: Relink `/gnu/store/1jp44pfmqcj3zycclvmmva3xcwinyg7l-freetype-2.8/lib/libfreetype.so.6' with `/gnu/store/n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25/lib/libpthread.so.0' for IFUNC symbol `longjmp' SC FFT global init: cosTable initialised. Exception while parsing YAML config file: operator[] call on a scalar Exception while parsing YAML config file: operator[] call on a scalar compiling class library... QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/guix-build-supercollider-3.9.1.drv-0/runtime-nixbld' qt.qpa.screen: QXcbConnection: Could not connect to display Could not connect to any X display. terminate called without an active exception 68% tests passed, 6 tests failed out of 19 Total Test time (real) = 8.92 sec The following tests FAILED: 9 - server_test_run (SEGFAULT) 15 - perf_counter_test_run (Failed) 16 - /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_1.scd_run (OTHER_FAULT) 17 - /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_2.scd_run (OTHER_FAULT) 18 - /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_3.scd_run (OTHER_FAULT) 19 - /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_deprecated.scd_run (OTHER_FAULT) Errors while running CTest ``` Any ideas? Is this to be expected when running the tests in a containerized environment?
1.0
Unit tests fails - Hello, When running the unit tests of SuperCollider with Guix (I'm packaging SuperCollider for it right now), they fail like: ``` Running tests... /gnu/store/6g4pfzgmgwpfkwix0p7r6j349hffh2gs-cmake-3.7.2/bin/ctest --force-new-ctest-process Test project /tmp/guix-build-supercollider-3.9.1.drv-0/build Start 1: buffer_manager_test_run 1/19 Test #1: buffer_manager_test_run ........................................................................................... Passed 0.03 sec Start 2: callback_interpreter_system_run 2/19 Test #2: callback_interpreter_system_run ................................................................................... Passed 0.02 sec Start 3: memory-pool_test_run 3/19 Test #3: memory-pool_test_run .............................................................................................. Passed 0.02 sec Start 4: server_dsp_thread_queue_test_run 4/19 Test #4: server_dsp_thread_queue_test_run .................................................................................. Passed 1.15 sec Start 5: server_dsp_thread_test_run 5/19 Test #5: server_dsp_thread_test_run ........................................................................................ Passed 4.78 sec Start 6: server_node_graph_test_run 6/19 Test #6: server_node_graph_test_run ........................................................................................ Passed 0.02 sec Start 7: server_scheduler_test_run 7/19 Test #7: server_scheduler_test_run ......................................................................................... Passed 0.47 sec Start 8: server_synth_factory_test_run 8/19 Test #8: server_synth_factory_test_run ..................................................................................... Passed 0.02 sec Start 9: server_test_run 9/19 Test #9: server_test_run ...................................................................................................***Exception: SegFault 0.29 sec SC FFT global init: cosTable initialised. Running 3 test cases... unknown location(0): fatal error: in "server_test_1": memory access violation at address: 0x00000000: no mapping at fault address /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/supernova/server_test.cpp(29): last checkpoint: "server_test_1" entry. *** 1 failure is detected in the test module "Master Test Suite" Start 10: simple_pool_test_run 10/19 Test #10: simple_pool_test_run .............................................................................................. Passed 0.02 sec Start 11: sized_array_test_run 11/19 Test #11: sized_array_test_run .............................................................................................. Passed 0.02 sec Start 12: sndfile_backend_test_run 12/19 Test #12: sndfile_backend_test_run .......................................................................................... Passed 1.02 sec Start 13: static_pool_test_run 13/19 Test #13: static_pool_test_run .............................................................................................. Passed 0.02 sec Start 14: timetag_test_run 14/19 Test #14: timetag_test_run .................................................................................................. Passed 0.02 sec Start 15: perf_counter_test_run 15/19 Test #15: perf_counter_test_run .............................................................................................***Failed 0.02 sec Running 1 test case... unknown location(0): fatal error: in "perf_count_test": std::exception: std::exception /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/supernova/perf_counter_test.cpp(6): last checkpoint: "perf_count_test" entry. *** 1 failure is detected in the test module "Master Test Suite" Start 16: /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_1.scd_run 16/19 Test #16: /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_1.scd_run ............***Exception: Other 0.35 sec /tmp/guix-build-supercollider-3.9.1.drv-0/build/lang/sclang: Relink `/gnu/store/b9ww6qv1ii9v6n45kin7543vkf6jfnd3-libpng-1.6.29/lib/libpng16.so.16' with `/gnu/store/n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25/lib/libpthread.so.0' for IFUNC symbol `longjmp' /tmp/guix-build-supercollider-3.9.1.drv-0/build/lang/sclang: Relink `/gnu/store/1jp44pfmqcj3zycclvmmva3xcwinyg7l-freetype-2.8/lib/libfreetype.so.6' with `/gnu/store/n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25/lib/libpthread.so.0' for IFUNC symbol `longjmp' SC FFT global init: cosTable initialised. Exception while parsing YAML config file: operator[] call on a scalar Exception while parsing YAML config file: operator[] call on a scalar compiling class library... QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/guix-build-supercollider-3.9.1.drv-0/runtime-nixbld' qt.qpa.screen: QXcbConnection: Could not connect to display Could not connect to any X display. terminate called without an active exception Start 17: /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_2.scd_run 17/19 Test #17: /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_2.scd_run ............***Exception: Other 0.20 sec /tmp/guix-build-supercollider-3.9.1.drv-0/build/lang/sclang: Relink `/gnu/store/b9ww6qv1ii9v6n45kin7543vkf6jfnd3-libpng-1.6.29/lib/libpng16.so.16' with `/gnu/store/n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25/lib/libpthread.so.0' for IFUNC symbol `longjmp' /tmp/guix-build-supercollider-3.9.1.drv-0/build/lang/sclang: Relink `/gnu/store/1jp44pfmqcj3zycclvmmva3xcwinyg7l-freetype-2.8/lib/libfreetype.so.6' with `/gnu/store/n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25/lib/libpthread.so.0' for IFUNC symbol `longjmp' SC FFT global init: cosTable initialised. Exception while parsing YAML config file: operator[] call on a scalar Exception while parsing YAML config file: operator[] call on a scalar compiling class library... QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/guix-build-supercollider-3.9.1.drv-0/runtime-nixbld' qt.qpa.screen: QXcbConnection: Could not connect to display Could not connect to any X display. terminate called without an active exception Start 18: /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_3.scd_run 18/19 Test #18: /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_3.scd_run ............***Exception: Other 0.20 sec /tmp/guix-build-supercollider-3.9.1.drv-0/build/lang/sclang: Relink `/gnu/store/b9ww6qv1ii9v6n45kin7543vkf6jfnd3-libpng-1.6.29/lib/libpng16.so.16' with `/gnu/store/n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25/lib/libpthread.so.0' for IFUNC symbol `longjmp' /tmp/guix-build-supercollider-3.9.1.drv-0/build/lang/sclang: Relink `/gnu/store/1jp44pfmqcj3zycclvmmva3xcwinyg7l-freetype-2.8/lib/libfreetype.so.6' with `/gnu/store/n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25/lib/libpthread.so.0' for IFUNC symbol `longjmp' SC FFT global init: cosTable initialised. Exception while parsing YAML config file: operator[] call on a scalar Exception while parsing YAML config file: operator[] call on a scalar compiling class library... QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/guix-build-supercollider-3.9.1.drv-0/runtime-nixbld' qt.qpa.screen: QXcbConnection: Could not connect to display Could not connect to any X display. terminate called without an active exception Start 19: /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_deprecated.scd_run 19/19 Test #19: /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_deprecated.scd_run ...***Exception: Other 0.20 sec /tmp/guix-build-supercollider-3.9.1.drv-0/build/lang/sclang: Relink `/gnu/store/b9ww6qv1ii9v6n45kin7543vkf6jfnd3-libpng-1.6.29/lib/libpng16.so.16' with `/gnu/store/n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25/lib/libpthread.so.0' for IFUNC symbol `longjmp' /tmp/guix-build-supercollider-3.9.1.drv-0/build/lang/sclang: Relink `/gnu/store/1jp44pfmqcj3zycclvmmva3xcwinyg7l-freetype-2.8/lib/libfreetype.so.6' with `/gnu/store/n6nvxlk2j8ysffjh3jphn1k5silnakh6-glibc-2.25/lib/libpthread.so.0' for IFUNC symbol `longjmp' SC FFT global init: cosTable initialised. Exception while parsing YAML config file: operator[] call on a scalar Exception while parsing YAML config file: operator[] call on a scalar compiling class library... QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/guix-build-supercollider-3.9.1.drv-0/runtime-nixbld' qt.qpa.screen: QXcbConnection: Could not connect to display Could not connect to any X display. terminate called without an active exception 68% tests passed, 6 tests failed out of 19 Total Test time (real) = 8.92 sec The following tests FAILED: 9 - server_test_run (SEGFAULT) 15 - perf_counter_test_run (Failed) 16 - /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_1.scd_run (OTHER_FAULT) 17 - /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_2.scd_run (OTHER_FAULT) 18 - /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_3.scd_run (OTHER_FAULT) 19 - /tmp/guix-build-supercollider-3.9.1.drv-0/SuperCollider-Source/testsuite/sclang/sclang_crash_deprecated.scd_run (OTHER_FAULT) Errors while running CTest ``` Any ideas? Is this to be expected when running the tests in a containerized environment?
test
unit tests fails hello when running the unit tests of supercollider with guix i m packaging supercollider for it right now they fail like running tests gnu store cmake bin ctest force new ctest process test project tmp guix build supercollider drv build start buffer manager test run test buffer manager test run passed sec start callback interpreter system run test callback interpreter system run passed sec start memory pool test run test memory pool test run passed sec start server dsp thread queue test run test server dsp thread queue test run passed sec start server dsp thread test run test server dsp thread test run passed sec start server node graph test run test server node graph test run passed sec start server scheduler test run test server scheduler test run passed sec start server synth factory test run test server synth factory test run passed sec start server test run test server test run exception segfault sec sc fft global init costable initialised running test cases unknown location fatal error in server test memory access violation at address no mapping at fault address tmp guix build supercollider drv supercollider source testsuite supernova server test cpp last checkpoint server test entry failure is detected in the test module master test suite start simple pool test run test simple pool test run passed sec start sized array test run test sized array test run passed sec start sndfile backend test run test sndfile backend test run passed sec start static pool test run test static pool test run passed sec start timetag test run test timetag test run passed sec start perf counter test run test perf counter test run failed sec running test case unknown location fatal error in perf count test std exception std exception tmp guix build supercollider drv supercollider source testsuite supernova perf counter test cpp last checkpoint perf count test entry failure is detected in the test module master test suite start tmp guix build supercollider drv supercollider source testsuite sclang sclang crash scd run test tmp guix build supercollider drv supercollider source testsuite sclang sclang crash scd run exception other sec tmp guix build supercollider drv build lang sclang relink gnu store libpng lib so with gnu store glibc lib libpthread so for ifunc symbol longjmp tmp guix build supercollider drv build lang sclang relink gnu store freetype lib libfreetype so with gnu store glibc lib libpthread so for ifunc symbol longjmp sc fft global init costable initialised exception while parsing yaml config file operator call on a scalar exception while parsing yaml config file operator call on a scalar compiling class library qstandardpaths xdg runtime dir not set defaulting to tmp guix build supercollider drv runtime nixbld qt qpa screen qxcbconnection could not connect to display could not connect to any x display terminate called without an active exception start tmp guix build supercollider drv supercollider source testsuite sclang sclang crash scd run test tmp guix build supercollider drv supercollider source testsuite sclang sclang crash scd run exception other sec tmp guix build supercollider drv build lang sclang relink gnu store libpng lib so with gnu store glibc lib libpthread so for ifunc symbol longjmp tmp guix build supercollider drv build lang sclang relink gnu store freetype lib libfreetype so with gnu store glibc lib libpthread so for ifunc symbol longjmp sc fft global init costable initialised exception while parsing yaml config file operator call on a scalar exception while parsing yaml config file operator call on a scalar compiling class library qstandardpaths xdg runtime dir not set defaulting to tmp guix build supercollider drv runtime nixbld qt qpa screen qxcbconnection could not connect to display could not connect to any x display terminate called without an active exception start tmp guix build supercollider drv supercollider source testsuite sclang sclang crash scd run test tmp guix build supercollider drv supercollider source testsuite sclang sclang crash scd run exception other sec tmp guix build supercollider drv build lang sclang relink gnu store libpng lib so with gnu store glibc lib libpthread so for ifunc symbol longjmp tmp guix build supercollider drv build lang sclang relink gnu store freetype lib libfreetype so with gnu store glibc lib libpthread so for ifunc symbol longjmp sc fft global init costable initialised exception while parsing yaml config file operator call on a scalar exception while parsing yaml config file operator call on a scalar compiling class library qstandardpaths xdg runtime dir not set defaulting to tmp guix build supercollider drv runtime nixbld qt qpa screen qxcbconnection could not connect to display could not connect to any x display terminate called without an active exception start tmp guix build supercollider drv supercollider source testsuite sclang sclang crash deprecated scd run test tmp guix build supercollider drv supercollider source testsuite sclang sclang crash deprecated scd run exception other sec tmp guix build supercollider drv build lang sclang relink gnu store libpng lib so with gnu store glibc lib libpthread so for ifunc symbol longjmp tmp guix build supercollider drv build lang sclang relink gnu store freetype lib libfreetype so with gnu store glibc lib libpthread so for ifunc symbol longjmp sc fft global init costable initialised exception while parsing yaml config file operator call on a scalar exception while parsing yaml config file operator call on a scalar compiling class library qstandardpaths xdg runtime dir not set defaulting to tmp guix build supercollider drv runtime nixbld qt qpa screen qxcbconnection could not connect to display could not connect to any x display terminate called without an active exception tests passed tests failed out of total test time real sec the following tests failed server test run segfault perf counter test run failed tmp guix build supercollider drv supercollider source testsuite sclang sclang crash scd run other fault tmp guix build supercollider drv supercollider source testsuite sclang sclang crash scd run other fault tmp guix build supercollider drv supercollider source testsuite sclang sclang crash scd run other fault tmp guix build supercollider drv supercollider source testsuite sclang sclang crash deprecated scd run other fault errors while running ctest any ideas is this to be expected when running the tests in a containerized environment
1
808,328
30,055,698,912
IssuesEvent
2023-06-28 06:35:08
bigomics/omicsplayground
https://api.github.com/repos/bigomics/omicsplayground
opened
Improve styling of legends
bug high priority
we had correct legend styling usign the `.card-footer` class, but somehow it got lost.. <img width="1130" alt="image" src="https://github.com/bigomics/omicsplayground/assets/28757711/a55aeeb3-8468-4e4b-be97-af89c471237b">
1.0
Improve styling of legends - we had correct legend styling usign the `.card-footer` class, but somehow it got lost.. <img width="1130" alt="image" src="https://github.com/bigomics/omicsplayground/assets/28757711/a55aeeb3-8468-4e4b-be97-af89c471237b">
non_test
improve styling of legends we had correct legend styling usign the card footer class but somehow it got lost img width alt image src
0
305,826
23,132,586,659
IssuesEvent
2022-07-28 11:47:13
appsmithorg/appsmith
https://api.github.com/repos/appsmithorg/appsmith
closed
[Docs]: Adding first draft for inline editing to the docs
Documentation User Education Pod
Adding inline editing's first draft to the docs for now. Table widget will be updated with a new structure later
1.0
[Docs]: Adding first draft for inline editing to the docs - Adding inline editing's first draft to the docs for now. Table widget will be updated with a new structure later
non_test
adding first draft for inline editing to the docs adding inline editing s first draft to the docs for now table widget will be updated with a new structure later
0
268,082
23,343,309,002
IssuesEvent
2022-08-09 15:39:05
status-im/status-desktop
https://api.github.com/repos/status-im/status-desktop
closed
The place of the elements on the All members and Banned community tabs differs from the Design
Communities tested pixel-perfect-issues
# Bug Report ## Description <!-- Provide a short description describing the problem you are experiencing. --> ## Steps to reproduce 1. Create a community with some members 2. Open the community 3. Click 'Manage community' 4. Check the elements placed according to the Design: https://www.figma.com/file/17fc13UBFvInrLgNUKJJg5/Kuba%E2%8E%9CDesktop?node-id=3113%3A356327 5. The same for Banned tab #### Expected behavior <img width="935" alt="image" src="https://user-images.githubusercontent.com/14942081/182502108-3ecf1033-ac66-4677-b55e-51da97de03c2.png"> #### Actual behavior 1. All elements should be on the same level 2. The space between the elements and the edge of Secondary Nav tab should be bigger <img width="899" alt="image" src="https://user-images.githubusercontent.com/14942081/182501966-764a7f72-3c40-4b4f-9c37-fa2bbcf4408f.png"> ### Additional Information - Status desktop version: https://github.com/status-im/status-desktop/pull/6280 - Operating System: macOS Monterey
1.0
The place of the elements on the All members and Banned community tabs differs from the Design - # Bug Report ## Description <!-- Provide a short description describing the problem you are experiencing. --> ## Steps to reproduce 1. Create a community with some members 2. Open the community 3. Click 'Manage community' 4. Check the elements placed according to the Design: https://www.figma.com/file/17fc13UBFvInrLgNUKJJg5/Kuba%E2%8E%9CDesktop?node-id=3113%3A356327 5. The same for Banned tab #### Expected behavior <img width="935" alt="image" src="https://user-images.githubusercontent.com/14942081/182502108-3ecf1033-ac66-4677-b55e-51da97de03c2.png"> #### Actual behavior 1. All elements should be on the same level 2. The space between the elements and the edge of Secondary Nav tab should be bigger <img width="899" alt="image" src="https://user-images.githubusercontent.com/14942081/182501966-764a7f72-3c40-4b4f-9c37-fa2bbcf4408f.png"> ### Additional Information - Status desktop version: https://github.com/status-im/status-desktop/pull/6280 - Operating System: macOS Monterey
test
the place of the elements on the all members and banned community tabs differs from the design bug report description steps to reproduce create a community with some members open the community click manage community check the elements placed according to the design the same for banned tab expected behavior img width alt image src actual behavior all elements should be on the same level the space between the elements and the edge of secondary nav tab should be bigger img width alt image src additional information status desktop version operating system macos monterey
1
203,661
15,378,947,429
IssuesEvent
2021-03-02 18:59:48
microsoft/vscode
https://api.github.com/repos/microsoft/vscode
closed
Integration test failure in tasks
integration-test-failure
``` 1) vscode API - tasks Tasks CustomExecution task should start and shutdown successfully: AssertionError [ERR_ASSERTION] [ERR_ASSERTION]: 0 == 1 + expected - actual -0 +1 at D:\a\vscode\vscode\extensions\vscode-api-tests\src\singlefolder-tests\workspace.tasks.test.ts:58:13 at Emitter.fire (d:\a\vscode\vscode\out\vs\base\common\file:\D:\a\vscode\vscode\src\vs\base\common\event.ts:622:16) at ExtHostTerminalService.$acceptTerminalProcessData (d:\a\vscode\vscode\out\vs\workbench\api\common\file:\D:\a\vscode\vscode\src\vs\workbench\api\common\extHostTerminalService.ts:372:33) at RPCProtocol._doInvokeHandler (d:\a\vscode\vscode\out\vs\workbench\services\extensions\common\file:\D:\a\vscode\vscode\src\vs\workbench\services\extensions\common\rpcProtocol.ts:417:17) at RPCProtocol._invokeHandler (d:\a\vscode\vscode\out\vs\workbench\services\extensions\common\file:\D:\a\vscode\vscode\src\vs\workbench\services\extensions\common\rpcProtocol.ts:402:32) at RPCProtocol._receiveRequest (d:\a\vscode\vscode\out\vs\workbench\services\extensions\common\file:\D:\a\vscode\vscode\src\vs\workbench\services\extensions\common\rpcProtocol.ts:318:19) at RPCProtocol._receiveOneMessage (d:\a\vscode\vscode\out\vs\workbench\services\extensions\common\file:\D:\a\vscode\vscode\src\vs\workbench\services\extensions\common\rpcProtocol.ts:245:10) at d:\a\vscode\vscode\out\vs\workbench\services\extensions\common\file:\D:\a\vscode\vscode\src\vs\workbench\services\extensions\common\rpcProtocol.ts:110:42 at Emitter.fire (d:\a\vscode\vscode\out\vs\base\common\file:\D:\a\vscode\vscode\src\vs\base\common\event.ts:622:16) at BufferedEmitter.fire (d:\a\vscode\vscode\out\vs\base\parts\ipc\common\file:\D:\a\vscode\vscode\src\vs\base\parts\ipc\common\ipc.net.ts:468:19) at d:\a\vscode\vscode\out\vs\workbench\services\extensions\node\file:\D:\a\vscode\vscode\src\vs\workbench\services\extensions\node\extensionHostProcessSetup.ts:198:22 at Emitter.fire (d:\a\vscode\vscode\out\vs\base\common\file:\D:\a\vscode\vscode\src\vs\base\common\event.ts:622:16) at BufferedEmitter.fire (d:\a\vscode\vscode\out\vs\base\parts\ipc\common\file:\D:\a\vscode\vscode\src\vs\base\parts\ipc\common\ipc.net.ts:468:19) at PersistentProtocol._receiveMessage (d:\a\vscode\vscode\out\vs\base\parts\ipc\common\file:\D:\a\vscode\vscode\src\vs\base\parts\ipc\common\ipc.net.ts:821:22) at d:\a\vscode\vscode\out\vs\base\parts\ipc\common\file:\D:\a\vscode\vscode\src\vs\base\parts\ipc\common\ipc.net.ts:660:73 at Emitter.fire (d:\a\vscode\vscode\out\vs\base\common\file:\D:\a\vscode\vscode\src\vs\base\common\event.ts:622:16) at ProtocolReader.acceptChunk (d:\a\vscode\vscode\out\vs\base\parts\ipc\common\file:\D:\a\vscode\vscode\src\vs\base\parts\ipc\common\ipc.net.ts:241:21) at d:\a\vscode\vscode\out\vs\base\parts\ipc\common\file:\D:\a\vscode\vscode\src\vs\base\parts\ipc\common\ipc.net.ts:202:51 at Socket.listener (d:\a\vscode\vscode\out\vs\base\parts\ipc\node\file:\D:\a\vscode\vscode\src\vs\base\parts\ipc\node\ipc.net.ts:32:38) at addChunk (_stream_readable.js:295:12) at readableAddChunk (_stream_readable.js:271:9) at Socket.push (_stream_readable.js:212:10) at Pipe.onStreamRead (internal/stream_base_commons.js:186:23) ``` From: https://github.com/microsoft/vscode/runs/1963674590#step:15:448
1.0
Integration test failure in tasks - ``` 1) vscode API - tasks Tasks CustomExecution task should start and shutdown successfully: AssertionError [ERR_ASSERTION] [ERR_ASSERTION]: 0 == 1 + expected - actual -0 +1 at D:\a\vscode\vscode\extensions\vscode-api-tests\src\singlefolder-tests\workspace.tasks.test.ts:58:13 at Emitter.fire (d:\a\vscode\vscode\out\vs\base\common\file:\D:\a\vscode\vscode\src\vs\base\common\event.ts:622:16) at ExtHostTerminalService.$acceptTerminalProcessData (d:\a\vscode\vscode\out\vs\workbench\api\common\file:\D:\a\vscode\vscode\src\vs\workbench\api\common\extHostTerminalService.ts:372:33) at RPCProtocol._doInvokeHandler (d:\a\vscode\vscode\out\vs\workbench\services\extensions\common\file:\D:\a\vscode\vscode\src\vs\workbench\services\extensions\common\rpcProtocol.ts:417:17) at RPCProtocol._invokeHandler (d:\a\vscode\vscode\out\vs\workbench\services\extensions\common\file:\D:\a\vscode\vscode\src\vs\workbench\services\extensions\common\rpcProtocol.ts:402:32) at RPCProtocol._receiveRequest (d:\a\vscode\vscode\out\vs\workbench\services\extensions\common\file:\D:\a\vscode\vscode\src\vs\workbench\services\extensions\common\rpcProtocol.ts:318:19) at RPCProtocol._receiveOneMessage (d:\a\vscode\vscode\out\vs\workbench\services\extensions\common\file:\D:\a\vscode\vscode\src\vs\workbench\services\extensions\common\rpcProtocol.ts:245:10) at d:\a\vscode\vscode\out\vs\workbench\services\extensions\common\file:\D:\a\vscode\vscode\src\vs\workbench\services\extensions\common\rpcProtocol.ts:110:42 at Emitter.fire (d:\a\vscode\vscode\out\vs\base\common\file:\D:\a\vscode\vscode\src\vs\base\common\event.ts:622:16) at BufferedEmitter.fire (d:\a\vscode\vscode\out\vs\base\parts\ipc\common\file:\D:\a\vscode\vscode\src\vs\base\parts\ipc\common\ipc.net.ts:468:19) at d:\a\vscode\vscode\out\vs\workbench\services\extensions\node\file:\D:\a\vscode\vscode\src\vs\workbench\services\extensions\node\extensionHostProcessSetup.ts:198:22 at Emitter.fire (d:\a\vscode\vscode\out\vs\base\common\file:\D:\a\vscode\vscode\src\vs\base\common\event.ts:622:16) at BufferedEmitter.fire (d:\a\vscode\vscode\out\vs\base\parts\ipc\common\file:\D:\a\vscode\vscode\src\vs\base\parts\ipc\common\ipc.net.ts:468:19) at PersistentProtocol._receiveMessage (d:\a\vscode\vscode\out\vs\base\parts\ipc\common\file:\D:\a\vscode\vscode\src\vs\base\parts\ipc\common\ipc.net.ts:821:22) at d:\a\vscode\vscode\out\vs\base\parts\ipc\common\file:\D:\a\vscode\vscode\src\vs\base\parts\ipc\common\ipc.net.ts:660:73 at Emitter.fire (d:\a\vscode\vscode\out\vs\base\common\file:\D:\a\vscode\vscode\src\vs\base\common\event.ts:622:16) at ProtocolReader.acceptChunk (d:\a\vscode\vscode\out\vs\base\parts\ipc\common\file:\D:\a\vscode\vscode\src\vs\base\parts\ipc\common\ipc.net.ts:241:21) at d:\a\vscode\vscode\out\vs\base\parts\ipc\common\file:\D:\a\vscode\vscode\src\vs\base\parts\ipc\common\ipc.net.ts:202:51 at Socket.listener (d:\a\vscode\vscode\out\vs\base\parts\ipc\node\file:\D:\a\vscode\vscode\src\vs\base\parts\ipc\node\ipc.net.ts:32:38) at addChunk (_stream_readable.js:295:12) at readableAddChunk (_stream_readable.js:271:9) at Socket.push (_stream_readable.js:212:10) at Pipe.onStreamRead (internal/stream_base_commons.js:186:23) ``` From: https://github.com/microsoft/vscode/runs/1963674590#step:15:448
test
integration test failure in tasks vscode api tasks tasks customexecution task should start and shutdown successfully assertionerror expected actual at d a vscode vscode extensions vscode api tests src singlefolder tests workspace tasks test ts at emitter fire d a vscode vscode out vs base common file d a vscode vscode src vs base common event ts at exthostterminalservice acceptterminalprocessdata d a vscode vscode out vs workbench api common file d a vscode vscode src vs workbench api common exthostterminalservice ts at rpcprotocol doinvokehandler d a vscode vscode out vs workbench services extensions common file d a vscode vscode src vs workbench services extensions common rpcprotocol ts at rpcprotocol invokehandler d a vscode vscode out vs workbench services extensions common file d a vscode vscode src vs workbench services extensions common rpcprotocol ts at rpcprotocol receiverequest d a vscode vscode out vs workbench services extensions common file d a vscode vscode src vs workbench services extensions common rpcprotocol ts at rpcprotocol receiveonemessage d a vscode vscode out vs workbench services extensions common file d a vscode vscode src vs workbench services extensions common rpcprotocol ts at d a vscode vscode out vs workbench services extensions common file d a vscode vscode src vs workbench services extensions common rpcprotocol ts at emitter fire d a vscode vscode out vs base common file d a vscode vscode src vs base common event ts at bufferedemitter fire d a vscode vscode out vs base parts ipc common file d a vscode vscode src vs base parts ipc common ipc net ts at d a vscode vscode out vs workbench services extensions node file d a vscode vscode src vs workbench services extensions node extensionhostprocesssetup ts at emitter fire d a vscode vscode out vs base common file d a vscode vscode src vs base common event ts at bufferedemitter fire d a vscode vscode out vs base parts ipc common file d a vscode vscode src vs base parts ipc common ipc net ts at persistentprotocol receivemessage d a vscode vscode out vs base parts ipc common file d a vscode vscode src vs base parts ipc common ipc net ts at d a vscode vscode out vs base parts ipc common file d a vscode vscode src vs base parts ipc common ipc net ts at emitter fire d a vscode vscode out vs base common file d a vscode vscode src vs base common event ts at protocolreader acceptchunk d a vscode vscode out vs base parts ipc common file d a vscode vscode src vs base parts ipc common ipc net ts at d a vscode vscode out vs base parts ipc common file d a vscode vscode src vs base parts ipc common ipc net ts at socket listener d a vscode vscode out vs base parts ipc node file d a vscode vscode src vs base parts ipc node ipc net ts at addchunk stream readable js at readableaddchunk stream readable js at socket push stream readable js at pipe onstreamread internal stream base commons js from
1
482,999
13,917,189,450
IssuesEvent
2020-10-21 05:24:48
grpc/grpc
https://api.github.com/repos/grpc/grpc
opened
Clean up child policy handler
kind/internal cleanup lang/core priority/P2
Based on an internal thread. Posting discussion - Yash - `I was reading some of the lb policy code and came across this assert - https://github.com/grpc/grpc/blob/de90ff64d5001b64104b555e7bb28630fbb7dede/src/core/ext/filters/client_channel/lb_policy/child_policy_handler.cc#L230 It seems like there is some underlying assumption that CreateChildPolicy() can not be nullptr? Given that CreateLoadBalancingPolicy can potentially return a nullptr, it doesn't seem obvious why this assert exists. Am I missing something?` Mark - Yeah, this is probably a little sloppy. The normal case where CreateChildPolicy() could return null is when the named policy doesn't exist, but in that case we will have caught the problem earlier during config validation, so it shouldn't ever happen here. But there are other cases where a specific type of LB policy may have a prerequisite; for example, several of the xDS-related policies will return null if the xDS bootstrap file is not present or invalid (example from CDS policy). There are two possible approaches we could take here: 1. Change the ChildPolicyHandler code to handle the case where creating a new policy returns null. We could probably do this by just returning a TransientFailurePicker to the channel. 2. Require LB policy creation to always succeed. In the case of the xDS policies, if the bootstrap file is invalid, we could have them just return a TransientFailurePicker and not do anything else.
1.0
Clean up child policy handler - Based on an internal thread. Posting discussion - Yash - `I was reading some of the lb policy code and came across this assert - https://github.com/grpc/grpc/blob/de90ff64d5001b64104b555e7bb28630fbb7dede/src/core/ext/filters/client_channel/lb_policy/child_policy_handler.cc#L230 It seems like there is some underlying assumption that CreateChildPolicy() can not be nullptr? Given that CreateLoadBalancingPolicy can potentially return a nullptr, it doesn't seem obvious why this assert exists. Am I missing something?` Mark - Yeah, this is probably a little sloppy. The normal case where CreateChildPolicy() could return null is when the named policy doesn't exist, but in that case we will have caught the problem earlier during config validation, so it shouldn't ever happen here. But there are other cases where a specific type of LB policy may have a prerequisite; for example, several of the xDS-related policies will return null if the xDS bootstrap file is not present or invalid (example from CDS policy). There are two possible approaches we could take here: 1. Change the ChildPolicyHandler code to handle the case where creating a new policy returns null. We could probably do this by just returning a TransientFailurePicker to the channel. 2. Require LB policy creation to always succeed. In the case of the xDS policies, if the bootstrap file is invalid, we could have them just return a TransientFailurePicker and not do anything else.
non_test
clean up child policy handler based on an internal thread posting discussion yash i was reading some of the lb policy code and came across this assert it seems like there is some underlying assumption that createchildpolicy can not be nullptr given that createloadbalancingpolicy can potentially return a nullptr it doesn t seem obvious why this assert exists am i missing something mark yeah this is probably a little sloppy the normal case where createchildpolicy could return null is when the named policy doesn t exist but in that case we will have caught the problem earlier during config validation so it shouldn t ever happen here but there are other cases where a specific type of lb policy may have a prerequisite for example several of the xds related policies will return null if the xds bootstrap file is not present or invalid example from cds policy there are two possible approaches we could take here change the childpolicyhandler code to handle the case where creating a new policy returns null we could probably do this by just returning a transientfailurepicker to the channel require lb policy creation to always succeed in the case of the xds policies if the bootstrap file is invalid we could have them just return a transientfailurepicker and not do anything else
0
32,235
6,041,073,482
IssuesEvent
2017-06-10 20:28:03
opencv/opencv
https://api.github.com/repos/opencv/opencv
closed
Documentation error: gpu::reduce always outputs a row vector (OpenCV 2.4)
bug category: documentation
**Summary** The destination vector that [`gpu::reduce()`](http://docs.opencv.org/2.4.8/modules/gpu/doc/matrix_reductions.html#gpu-reduce) outputs is always a row vector. This was discovered when reading [Feng](https://stackoverflow.com/users/2429379/feng) & [jet47](https://stackoverflow.com/users/2451683/jet47)'s [discussion on Stack Overflow](https://stackoverflow.com/questions/21919990/possible-bug-in-opencv-matrix-reduction-of-gpumat/21926689#21926689) and demonstrated by the following tests on a rowsum operation: **Test 1 (fails)** ``` // CPU init double alpha = 1.8; double x[977][1]; // also fill x array with values, lines hidden cv::Mat alpha_h(977,60,DataType<double>::type,alpha); cv::Mat x_h(977,1,DataType<double>::type,x); // GPU init & upload gpu::GpuMat alpha_g(977,60,DataType<double>::type); gpu::GpuMat rowtotal_g(977,1,DataType<double>::type,0.0); gpu::GpuMat x_g(977,1,DataType<double>::type); alpha_g.upload(alpha_h); x_g.upload(x_h); // GPU operations gpu::reduce(alpha_g,rowtotal_g,1,CV_REDUCE_SUM,-1); // rowsum reduction gpu::add(rowtotal_g,x_g,rowtotal_g); // causes runtime error, see next line "OpenCV Error: Assertion failed (src2.type() == src1.type() && src2.size() == src1.size()) in add, file /.../opencv-2.4/modules/gpu/src/element_operations.cpp, line 423" ``` This is because the documentation says I should expect `rowtotal_g` to be a 977x1 column vector, however it's really a 1x977 row vector, so [`gpu::add()`](http://docs.opencv.org/2.4.8/modules/gpu/doc/per_element_operations.html#gpu-add) can't add it to the 977x1 `x_g` column vector. **Test 2 (succeeds)** But with these code changes making `x_g` a row vector solves it: ``` cv::Mat x_h(1,977,DataType<double>::type,x); gpu::GpuMat x_g(1,977,DataType<double>::type); ``` so that this line now runs fine `gpu::add(rowtotal_g,DKAOarraycorr_g,rowtotal_g); ` **Recommended documentation changes for the [`gpu::reduce`](http://docs.opencv.org/2.4.8/modules/gpu/doc/matrix_reductions.html#gpu-reduce) function** Note these changes will affect all docs.opencv.org/2.4.x.x subdirectories - "vec – Destination vector" _to_ "vec – Destination row vector" - "0 means that the matrix is reduced to a single row. 1 means that the matrix is reduced to a single column." _to_ "0 means that the matrix is reduced to a single **row** with size equal to the number of matrix columns. 1 means that the matrix is reduced to a single **row** with size equal to the number of matrix rows." - "performing the specified operation on the vectors until a single row/column is obtained" _to_ "performing the specified operation on the vectors until a single row is obtained" <!-- If you have a question rather than reporting a bug please go to http://answers.opencv.org where you get much faster responses. If you need further assistance please read [How To Contribute](https://github.com/opencv/opencv/wiki/How_to_contribute). This is a template helping you to create an issue which can be processed as quickly as possible. This is the bug reporting section for the OpenCV library. --> ##### System information (version) <!-- Example - OpenCV => 3.1 - Operating System / Platform => Windows 64 Bit - Compiler => Visual Studio 2015 --> - OpenCV => 2.4 - Operating System / Platform => Ubuntu 16.04 LTS 64 bit - Compiler => nvcc V8.0.61
1.0
Documentation error: gpu::reduce always outputs a row vector (OpenCV 2.4) - **Summary** The destination vector that [`gpu::reduce()`](http://docs.opencv.org/2.4.8/modules/gpu/doc/matrix_reductions.html#gpu-reduce) outputs is always a row vector. This was discovered when reading [Feng](https://stackoverflow.com/users/2429379/feng) & [jet47](https://stackoverflow.com/users/2451683/jet47)'s [discussion on Stack Overflow](https://stackoverflow.com/questions/21919990/possible-bug-in-opencv-matrix-reduction-of-gpumat/21926689#21926689) and demonstrated by the following tests on a rowsum operation: **Test 1 (fails)** ``` // CPU init double alpha = 1.8; double x[977][1]; // also fill x array with values, lines hidden cv::Mat alpha_h(977,60,DataType<double>::type,alpha); cv::Mat x_h(977,1,DataType<double>::type,x); // GPU init & upload gpu::GpuMat alpha_g(977,60,DataType<double>::type); gpu::GpuMat rowtotal_g(977,1,DataType<double>::type,0.0); gpu::GpuMat x_g(977,1,DataType<double>::type); alpha_g.upload(alpha_h); x_g.upload(x_h); // GPU operations gpu::reduce(alpha_g,rowtotal_g,1,CV_REDUCE_SUM,-1); // rowsum reduction gpu::add(rowtotal_g,x_g,rowtotal_g); // causes runtime error, see next line "OpenCV Error: Assertion failed (src2.type() == src1.type() && src2.size() == src1.size()) in add, file /.../opencv-2.4/modules/gpu/src/element_operations.cpp, line 423" ``` This is because the documentation says I should expect `rowtotal_g` to be a 977x1 column vector, however it's really a 1x977 row vector, so [`gpu::add()`](http://docs.opencv.org/2.4.8/modules/gpu/doc/per_element_operations.html#gpu-add) can't add it to the 977x1 `x_g` column vector. **Test 2 (succeeds)** But with these code changes making `x_g` a row vector solves it: ``` cv::Mat x_h(1,977,DataType<double>::type,x); gpu::GpuMat x_g(1,977,DataType<double>::type); ``` so that this line now runs fine `gpu::add(rowtotal_g,DKAOarraycorr_g,rowtotal_g); ` **Recommended documentation changes for the [`gpu::reduce`](http://docs.opencv.org/2.4.8/modules/gpu/doc/matrix_reductions.html#gpu-reduce) function** Note these changes will affect all docs.opencv.org/2.4.x.x subdirectories - "vec – Destination vector" _to_ "vec – Destination row vector" - "0 means that the matrix is reduced to a single row. 1 means that the matrix is reduced to a single column." _to_ "0 means that the matrix is reduced to a single **row** with size equal to the number of matrix columns. 1 means that the matrix is reduced to a single **row** with size equal to the number of matrix rows." - "performing the specified operation on the vectors until a single row/column is obtained" _to_ "performing the specified operation on the vectors until a single row is obtained" <!-- If you have a question rather than reporting a bug please go to http://answers.opencv.org where you get much faster responses. If you need further assistance please read [How To Contribute](https://github.com/opencv/opencv/wiki/How_to_contribute). This is a template helping you to create an issue which can be processed as quickly as possible. This is the bug reporting section for the OpenCV library. --> ##### System information (version) <!-- Example - OpenCV => 3.1 - Operating System / Platform => Windows 64 Bit - Compiler => Visual Studio 2015 --> - OpenCV => 2.4 - Operating System / Platform => Ubuntu 16.04 LTS 64 bit - Compiler => nvcc V8.0.61
non_test
documentation error gpu reduce always outputs a row vector opencv summary the destination vector that outputs is always a row vector this was discovered when reading and demonstrated by the following tests on a rowsum operation test fails cpu init double alpha double x also fill x array with values lines hidden cv mat alpha h datatype type alpha cv mat x h datatype type x gpu init upload gpu gpumat alpha g datatype type gpu gpumat rowtotal g datatype type gpu gpumat x g datatype type alpha g upload alpha h x g upload x h gpu operations gpu reduce alpha g rowtotal g cv reduce sum rowsum reduction gpu add rowtotal g x g rowtotal g causes runtime error see next line opencv error assertion failed type type size size in add file opencv modules gpu src element operations cpp line this is because the documentation says i should expect rowtotal g to be a column vector however it s really a row vector so can t add it to the x g column vector test succeeds but with these code changes making x g a row vector solves it cv mat x h datatype type x gpu gpumat x g datatype type so that this line now runs fine gpu add rowtotal g dkaoarraycorr g rowtotal g recommended documentation changes for the function note these changes will affect all docs opencv org x x subdirectories vec – destination vector to vec – destination row vector means that the matrix is reduced to a single row means that the matrix is reduced to a single column to means that the matrix is reduced to a single row with size equal to the number of matrix columns means that the matrix is reduced to a single row with size equal to the number of matrix rows performing the specified operation on the vectors until a single row column is obtained to performing the specified operation on the vectors until a single row is obtained if you have a question rather than reporting a bug please go to where you get much faster responses if you need further assistance please read this is a template helping you to create an issue which can be processed as quickly as possible this is the bug reporting section for the opencv library system information version example opencv operating system platform windows bit compiler visual studio opencv operating system platform ubuntu lts bit compiler nvcc
0
249,985
21,220,785,356
IssuesEvent
2022-04-11 11:44:19
dusk-network/wallet-cli
https://api.github.com/repos/dusk-network/wallet-cli
opened
Prevent interactive process from quitting on wallet execution errors
mark:testnet
**Describe what you want implemented** When using the interactive mode, the user should be able to select another option (or exit manually) when a command fails for whatever reason. **Describe "Why" this is needed** Right now the error gets propagated all the way to the top and the CLI stops. **Describe alternatives you've considered** N/A **Additional context** ``` ✔ What would you like to do? · Stake DUSK ✔ Select a spend key: · 0 ✔ Select a stake key: · 0 ✔ Introduce the amount of DUSK to stake: · 100 ✔ Introduce the gas limit for this transaction: · 500000000 ✔ Introduce the gas price for this transaction: · 0.000000001 > Stake key = 0 > Amount to stake = 100 DUSK > Max fee = 0.5 DUSK ✔ Transaction ready. Proceed? · Yes Staking is only allowed when you're running your own local Rusk instance (Tip: Point `rusk_addr` to "localhost" or "127.0.0.1") [PROGRAM EXITS] ```
1.0
Prevent interactive process from quitting on wallet execution errors - **Describe what you want implemented** When using the interactive mode, the user should be able to select another option (or exit manually) when a command fails for whatever reason. **Describe "Why" this is needed** Right now the error gets propagated all the way to the top and the CLI stops. **Describe alternatives you've considered** N/A **Additional context** ``` ✔ What would you like to do? · Stake DUSK ✔ Select a spend key: · 0 ✔ Select a stake key: · 0 ✔ Introduce the amount of DUSK to stake: · 100 ✔ Introduce the gas limit for this transaction: · 500000000 ✔ Introduce the gas price for this transaction: · 0.000000001 > Stake key = 0 > Amount to stake = 100 DUSK > Max fee = 0.5 DUSK ✔ Transaction ready. Proceed? · Yes Staking is only allowed when you're running your own local Rusk instance (Tip: Point `rusk_addr` to "localhost" or "127.0.0.1") [PROGRAM EXITS] ```
test
prevent interactive process from quitting on wallet execution errors describe what you want implemented when using the interactive mode the user should be able to select another option or exit manually when a command fails for whatever reason describe why this is needed right now the error gets propagated all the way to the top and the cli stops describe alternatives you ve considered n a additional context ✔ what would you like to do · stake dusk ✔ select a spend key · ✔ select a stake key · ✔ introduce the amount of dusk to stake · ✔ introduce the gas limit for this transaction · ✔ introduce the gas price for this transaction · stake key amount to stake dusk max fee dusk ✔ transaction ready proceed · yes staking is only allowed when you re running your own local rusk instance tip point rusk addr to localhost or
1
411,127
12,014,812,022
IssuesEvent
2020-04-10 12:29:37
DimensionDev/Maskbook
https://api.github.com/repos/DimensionDev/Maskbook
closed
[Bug] Empty name and empty password are not prohibited for Persona creation
Migrate to Jira Priority: P4 (Do when free) Type: Bug
# Bug Report ## Environment ### Maskbook - Maskbook Version: * - Installation: CI Artifact - Build Commit: a921183eb9988850fd90a62f548f94b75094845f ## Bug Info ### Expected Behavior Should show a tooltip-like alert at the input element which tells the user that: Language | String --- | --- en | Name cannot be empty zh | 名稱不能為空 ### Actual Behavior <img width="1055" alt="image" src="https://user-images.githubusercontent.com/2139261/78963552-617f7b00-7ae7-11ea-842b-5aa77f4eaaf1.png"> ### How To Reproduce Create a Persona with empty name.
1.0
[Bug] Empty name and empty password are not prohibited for Persona creation - # Bug Report ## Environment ### Maskbook - Maskbook Version: * - Installation: CI Artifact - Build Commit: a921183eb9988850fd90a62f548f94b75094845f ## Bug Info ### Expected Behavior Should show a tooltip-like alert at the input element which tells the user that: Language | String --- | --- en | Name cannot be empty zh | 名稱不能為空 ### Actual Behavior <img width="1055" alt="image" src="https://user-images.githubusercontent.com/2139261/78963552-617f7b00-7ae7-11ea-842b-5aa77f4eaaf1.png"> ### How To Reproduce Create a Persona with empty name.
non_test
empty name and empty password are not prohibited for persona creation bug report environment maskbook maskbook version installation ci artifact build commit bug info expected behavior should show a tooltip like alert at the input element which tells the user that language string en name cannot be empty zh 名稱不能為空 actual behavior img width alt image src how to reproduce create a persona with empty name
0
259,112
19,586,585,866
IssuesEvent
2022-01-05 07:51:48
Parsely/wp-parsely
https://api.github.com/repos/Parsely/wp-parsely
closed
Update screenshot for settings page
Type: Documentation [Status] In Progress
3.1.0 of the plugin organised the settings page into new sections. #552 fixed some strings on the settings page. We should update `.wordpress-org/screenshot-1.png` to show the new settings page look (but hack locally to show the version as `3.1.0` first!).
1.0
Update screenshot for settings page - 3.1.0 of the plugin organised the settings page into new sections. #552 fixed some strings on the settings page. We should update `.wordpress-org/screenshot-1.png` to show the new settings page look (but hack locally to show the version as `3.1.0` first!).
non_test
update screenshot for settings page of the plugin organised the settings page into new sections fixed some strings on the settings page we should update wordpress org screenshot png to show the new settings page look but hack locally to show the version as first
0
261,492
8,234,214,694
IssuesEvent
2018-09-08 11:43:31
inf3rno/e2e-testing
https://api.github.com/repos/inf3rno/e2e-testing
opened
Using a Symbol polyfill instead of a generated string id?
do: decide on: library priority 3: usual
We could use Symbols instead of the current id generator: https://dev.to/mildrenben/symbols-in-es6---a-quick-guide-dhm ```js var nextId = 1; module.exports = function (){ return "uid." + nextId++; }; ``` The current one is not the best. I mean we usually use something like microsecond timestamp + random value or these and an entropy source to generate a 128 bit or longer random string. There are even KDFs with many loops, but we don't need those in this case. I need to check what polyfills there are and whether it is worth the effort to use them. I'd like to have a wide browser support without too many polyfills. Btw we could use HashMaps and HashSets too, afaik. they are called WeakMap and WeakSet in js. There are polyfills for those too. It is relatively easy to polyfill them, all you need is an array, which checks duplication of value or key (by maps). The only drawback that there is no garbage collection for these except if you add a an expiration time or something like that, which we can consider.
1.0
Using a Symbol polyfill instead of a generated string id? - We could use Symbols instead of the current id generator: https://dev.to/mildrenben/symbols-in-es6---a-quick-guide-dhm ```js var nextId = 1; module.exports = function (){ return "uid." + nextId++; }; ``` The current one is not the best. I mean we usually use something like microsecond timestamp + random value or these and an entropy source to generate a 128 bit or longer random string. There are even KDFs with many loops, but we don't need those in this case. I need to check what polyfills there are and whether it is worth the effort to use them. I'd like to have a wide browser support without too many polyfills. Btw we could use HashMaps and HashSets too, afaik. they are called WeakMap and WeakSet in js. There are polyfills for those too. It is relatively easy to polyfill them, all you need is an array, which checks duplication of value or key (by maps). The only drawback that there is no garbage collection for these except if you add a an expiration time or something like that, which we can consider.
non_test
using a symbol polyfill instead of a generated string id we could use symbols instead of the current id generator js var nextid module exports function return uid nextid the current one is not the best i mean we usually use something like microsecond timestamp random value or these and an entropy source to generate a bit or longer random string there are even kdfs with many loops but we don t need those in this case i need to check what polyfills there are and whether it is worth the effort to use them i d like to have a wide browser support without too many polyfills btw we could use hashmaps and hashsets too afaik they are called weakmap and weakset in js there are polyfills for those too it is relatively easy to polyfill them all you need is an array which checks duplication of value or key by maps the only drawback that there is no garbage collection for these except if you add a an expiration time or something like that which we can consider
0
49,226
3,001,744,024
IssuesEvent
2015-07-24 13:30:13
centreon/centreon
https://api.github.com/repos/centreon/centreon
closed
Event Log Button "all"
Component: Affect Version Component: Resolution Priority: Normal Status: Rejected Tracker: Enhancement
--- Author Name: **christian evertz** (christian evertz) Original Redmine Issue: 1875, https://forge.centreon.com/issues/1875 Original Date: 2010-07-29 --- A button to check all presented hosts would be nice. A button to check all Message Types would be nice too.
1.0
Event Log Button "all" - --- Author Name: **christian evertz** (christian evertz) Original Redmine Issue: 1875, https://forge.centreon.com/issues/1875 Original Date: 2010-07-29 --- A button to check all presented hosts would be nice. A button to check all Message Types would be nice too.
non_test
event log button all author name christian evertz christian evertz original redmine issue original date a button to check all presented hosts would be nice a button to check all message types would be nice too
0
171,135
20,924,903,180
IssuesEvent
2022-03-24 21:26:49
opensearch-project/OpenSearch-Dashboards
https://api.github.com/repos/opensearch-project/OpenSearch-Dashboards
closed
CVE-2022-24433 (High) detected in simple-git-1.116.0.tgz
v2.0.0 security vulnerability high severity cve
## CVE-2022-24433 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>simple-git-1.116.0.tgz</b></p></summary> <p>Simple GIT interface for node.js</p> <p>Library home page: <a href="https://registry.npmjs.org/simple-git/-/simple-git-1.116.0.tgz">https://registry.npmjs.org/simple-git/-/simple-git-1.116.0.tgz</a></p> <p> Dependency Hierarchy: - :x: **simple-git-1.116.0.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/OpenSearch-Dashboards/commit/15e4bc2ff89cb54dae3e994c4f03479ab7b6d846">15e4bc2ff89cb54dae3e994c4f03479ab7b6d846</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> The package simple-git before 3.3.0 are vulnerable to Command Injection via argument injection. When calling the .fetch(remote, branch, handlerFn) function, both the remote and branch parameters are passed to the git fetch subcommand. By injecting some git options it was possible to get arbitrary command execution. <p>Publish Date: 2022-03-11 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24433>CVE-2022-24433</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://github.com/advisories/GHSA-3f95-r44v-8mrg">https://github.com/advisories/GHSA-3f95-r44v-8mrg</a></p> <p>Release Date: 2022-03-11</p> <p>Fix Resolution: simple-git - 3.3.0</p> </p> </details> <p></p> <!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"simple-git","packageVersion":"1.116.0","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"simple-git:1.116.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"simple-git - 3.3.0","isBinary":true}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2022-24433","vulnerabilityDetails":"The package simple-git before 3.3.0 are vulnerable to Command Injection via argument injection. When calling the .fetch(remote, branch, handlerFn) function, both the remote and branch parameters are passed to the git fetch subcommand. By injecting some git options it was possible to get arbitrary command execution.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24433","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-24433 (High) detected in simple-git-1.116.0.tgz - ## CVE-2022-24433 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>simple-git-1.116.0.tgz</b></p></summary> <p>Simple GIT interface for node.js</p> <p>Library home page: <a href="https://registry.npmjs.org/simple-git/-/simple-git-1.116.0.tgz">https://registry.npmjs.org/simple-git/-/simple-git-1.116.0.tgz</a></p> <p> Dependency Hierarchy: - :x: **simple-git-1.116.0.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/opensearch-project/OpenSearch-Dashboards/commit/15e4bc2ff89cb54dae3e994c4f03479ab7b6d846">15e4bc2ff89cb54dae3e994c4f03479ab7b6d846</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> The package simple-git before 3.3.0 are vulnerable to Command Injection via argument injection. When calling the .fetch(remote, branch, handlerFn) function, both the remote and branch parameters are passed to the git fetch subcommand. By injecting some git options it was possible to get arbitrary command execution. <p>Publish Date: 2022-03-11 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24433>CVE-2022-24433</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://github.com/advisories/GHSA-3f95-r44v-8mrg">https://github.com/advisories/GHSA-3f95-r44v-8mrg</a></p> <p>Release Date: 2022-03-11</p> <p>Fix Resolution: simple-git - 3.3.0</p> </p> </details> <p></p> <!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"simple-git","packageVersion":"1.116.0","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"simple-git:1.116.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"simple-git - 3.3.0","isBinary":true}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2022-24433","vulnerabilityDetails":"The package simple-git before 3.3.0 are vulnerable to Command Injection via argument injection. When calling the .fetch(remote, branch, handlerFn) function, both the remote and branch parameters are passed to the git fetch subcommand. By injecting some git options it was possible to get arbitrary command execution.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24433","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_test
cve high detected in simple git tgz cve high severity vulnerability vulnerable library simple git tgz simple git interface for node js library home page a href dependency hierarchy x simple git tgz vulnerable library found in head commit a href found in base branch main vulnerability details the package simple git before are vulnerable to command injection via argument injection when calling the fetch remote branch handlerfn function both the remote and branch parameters are passed to the git fetch subcommand by injecting some git options it was possible to get arbitrary command execution 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 simple git isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree simple git isminimumfixversionavailable true minimumfixversion simple git isbinary true basebranches vulnerabilityidentifier cve vulnerabilitydetails the package simple git before are vulnerable to command injection via argument injection when calling the fetch remote branch handlerfn function both the remote and branch parameters are passed to the git fetch subcommand by injecting some git options it was possible to get arbitrary command execution vulnerabilityurl
0
149,233
13,260,543,238
IssuesEvent
2020-08-20 18:21:03
mikecao/umami
https://api.github.com/repos/mikecao/umami
closed
[Feature request] Event tracking
documentation
First of all: beautiful tool. So happy for stumbling upon it. Would love to see event/click tracking.
1.0
[Feature request] Event tracking - First of all: beautiful tool. So happy for stumbling upon it. Would love to see event/click tracking.
non_test
event tracking first of all beautiful tool so happy for stumbling upon it would love to see event click tracking
0
637,706
20,675,995,050
IssuesEvent
2022-03-10 09:20:05
AY2122S2-CS2103-F09-2/tp
https://api.github.com/repos/AY2122S2-CS2103-F09-2/tp
closed
Delete friend
type.Story priority.High
As a user, I can remove friends I am no longer in contact with so that I can keep my friends list updated and remove irrelevant contact
1.0
Delete friend - As a user, I can remove friends I am no longer in contact with so that I can keep my friends list updated and remove irrelevant contact
non_test
delete friend as a user i can remove friends i am no longer in contact with so that i can keep my friends list updated and remove irrelevant contact
0
107,011
23,329,985,133
IssuesEvent
2022-08-09 03:29:55
jongracecox/anybadge
https://api.github.com/repos/jongracecox/anybadge
closed
Thoughts on splitting out into modules
code style
Hey! First of all, thanks for creating this! It's fantastic and is really simple to use / import. I also love the fact you included a webserver for it, ace! I wanted to ask, what your thoughts are on splitting out the single `anybadge.py` file into separate files? You'll see I've added PR #50 to support a new format called `GitLab Scoped`, and would like to add other formats in future. As the file will grow exponentially as a result, it seemed to me to be a good time to externalise the `Badge` class. We can then add other classes (e.g., `GitLabScopedBadge`) easily and import the class as needed, perhaps based on the `--style` flag. I don't want to set off and do that work though unless you're happy and the PR is likely to be accepted of course 🙂 Let me know what you think anyway. Cheers
1.0
Thoughts on splitting out into modules - Hey! First of all, thanks for creating this! It's fantastic and is really simple to use / import. I also love the fact you included a webserver for it, ace! I wanted to ask, what your thoughts are on splitting out the single `anybadge.py` file into separate files? You'll see I've added PR #50 to support a new format called `GitLab Scoped`, and would like to add other formats in future. As the file will grow exponentially as a result, it seemed to me to be a good time to externalise the `Badge` class. We can then add other classes (e.g., `GitLabScopedBadge`) easily and import the class as needed, perhaps based on the `--style` flag. I don't want to set off and do that work though unless you're happy and the PR is likely to be accepted of course 🙂 Let me know what you think anyway. Cheers
non_test
thoughts on splitting out into modules hey first of all thanks for creating this it s fantastic and is really simple to use import i also love the fact you included a webserver for it ace i wanted to ask what your thoughts are on splitting out the single anybadge py file into separate files you ll see i ve added pr to support a new format called gitlab scoped and would like to add other formats in future as the file will grow exponentially as a result it seemed to me to be a good time to externalise the badge class we can then add other classes e g gitlabscopedbadge easily and import the class as needed perhaps based on the style flag i don t want to set off and do that work though unless you re happy and the pr is likely to be accepted of course 🙂 let me know what you think anyway cheers
0
159,159
12,465,279,279
IssuesEvent
2020-05-28 13:49:17
zonemaster/zonemaster-engine
https://api.github.com/repos/zonemaster/zonemaster-engine
opened
Implementation of Consistency05 does not find names in subzone
A-TestCase T-Bug
Testing ".fr" results in error in Consistency05: > $ zonemaster-cli --show_module --raw --test consistency/consistency05 fr 18.80 ERROR CONSISTENCY CONSISTENCY:IN_BAILIWICK_ADDR_MISMATCH parent_addresses=d.nic.fr./194.0.9.1; d.nic.fr./2001:678:c::1; e.ext.nic.fr./193.176.144.22; e.ext.nic.fr./2a00:d78:0:102:193:176:144:22; f.ext.nic.fr./194.146.106.46; f.ext.nic.fr./2001:67c:1010:11::53; g.ext.nic.fr./194.0.36.1; g.ext.nic.fr./2001:678:4c::1; zone_addresses= Zonemaster looks for the address records of d.nic.fr, e.ext.nic.fr, f.ext.nic.fr and g.ext.nic.fr in the .fr zone, but they are not included in the zone (as authoritative data) since nic.fr is delegated to another set of nameservers. [Consistency05] says somewhere in the middle of the ordered description the following which is meant to cover that situation: ``` 3. Or, if the response is a delegation (referral) to a sub-zone of *Child Zone*, then: 1. Copy the adress query (A, AAAA) that gave the referral response. 2. Set the RD flag in the copied query (from unset to set). 3. Do a [DNS Lookup][terminology] of the the query. 4. If the lookup returns the relevant address record or records, A for A record query and AAAA for AAAA record query, and with the same owner name as in the query (i.e. CNAME should not be followed), then extract those and add to *Address Records From Child* with name and IP address or addresses. ``` The implementation of Consistency05 does not seem to follow these steps. (For an undelegated test, the steps above could be problematic.) [Consistency05]: https://github.com/zonemaster/zonemaster/blob/614d7af077d43d57212e949f883987df90dcb173/docs/specifications/tests/Consistency-TP/consistency05.md
1.0
Implementation of Consistency05 does not find names in subzone - Testing ".fr" results in error in Consistency05: > $ zonemaster-cli --show_module --raw --test consistency/consistency05 fr 18.80 ERROR CONSISTENCY CONSISTENCY:IN_BAILIWICK_ADDR_MISMATCH parent_addresses=d.nic.fr./194.0.9.1; d.nic.fr./2001:678:c::1; e.ext.nic.fr./193.176.144.22; e.ext.nic.fr./2a00:d78:0:102:193:176:144:22; f.ext.nic.fr./194.146.106.46; f.ext.nic.fr./2001:67c:1010:11::53; g.ext.nic.fr./194.0.36.1; g.ext.nic.fr./2001:678:4c::1; zone_addresses= Zonemaster looks for the address records of d.nic.fr, e.ext.nic.fr, f.ext.nic.fr and g.ext.nic.fr in the .fr zone, but they are not included in the zone (as authoritative data) since nic.fr is delegated to another set of nameservers. [Consistency05] says somewhere in the middle of the ordered description the following which is meant to cover that situation: ``` 3. Or, if the response is a delegation (referral) to a sub-zone of *Child Zone*, then: 1. Copy the adress query (A, AAAA) that gave the referral response. 2. Set the RD flag in the copied query (from unset to set). 3. Do a [DNS Lookup][terminology] of the the query. 4. If the lookup returns the relevant address record or records, A for A record query and AAAA for AAAA record query, and with the same owner name as in the query (i.e. CNAME should not be followed), then extract those and add to *Address Records From Child* with name and IP address or addresses. ``` The implementation of Consistency05 does not seem to follow these steps. (For an undelegated test, the steps above could be problematic.) [Consistency05]: https://github.com/zonemaster/zonemaster/blob/614d7af077d43d57212e949f883987df90dcb173/docs/specifications/tests/Consistency-TP/consistency05.md
test
implementation of does not find names in subzone testing fr results in error in zonemaster cli show module raw test consistency fr error consistency consistency in bailiwick addr mismatch parent addresses d nic fr d nic fr c e ext nic fr e ext nic fr f ext nic fr f ext nic fr g ext nic fr g ext nic fr zone addresses zonemaster looks for the address records of d nic fr e ext nic fr f ext nic fr and g ext nic fr in the fr zone but they are not included in the zone as authoritative data since nic fr is delegated to another set of nameservers says somewhere in the middle of the ordered description the following which is meant to cover that situation or if the response is a delegation referral to a sub zone of child zone then copy the adress query a aaaa that gave the referral response set the rd flag in the copied query from unset to set do a of the the query if the lookup returns the relevant address record or records a for a record query and aaaa for aaaa record query and with the same owner name as in the query i e cname should not be followed then extract those and add to address records from child with name and ip address or addresses the implementation of does not seem to follow these steps for an undelegated test the steps above could be problematic
1
296,447
25,551,065,722
IssuesEvent
2022-11-29 23:49:22
brave/brave-browser
https://api.github.com/repos/brave/brave-browser
opened
Brave News `Customize` dialog is blank
bug QA/Yes QA/Test-Plan-Specified regression OS/Desktop feature/brave-news
<!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue. PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE. INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED--> ## Description <!--Provide a brief description of the issue--> ## Steps to Reproduce <!--Please add a series of steps to reproduce the issue--> 1. install 1.48.15 2. launch Brave 3. load [theatlantic.com](http://theatlantic.com/) 4. click on the brand-new RSS-feed icon in the URL bar 5. click on Best of The Atlantic 6. click on Manage feeds… 7. click Turn on Brave News ## Actual result: <!--Please add screenshots if needed--> Blank `Customize Brave News` dialog #### Screencast: ![blank-page](https://user-images.githubusercontent.com/387249/204673431-ef145180-683c-4c00-856c-6b34218e48a2.gif) ## Expected result: `Customize Brave News` dialog, populated with `theatlantic.com` `Best of the Atlantic` feed shown under `Following` ## Reproduces how often: <!--[Easily reproduced/Intermittent issue/No steps to reproduce]--> 100% ## Brave version (brave://version info) <!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details--> Brave | 1.48.15 Chromium: 108.0.5359.62 (Official Build) nightly (x86_64) -- | -- Revision | 041930a89a990cfab0315a2d9f20d6429a4a67cf-refs/branch-heads/5359@{#938} OS | macOS Version 11.7.1 (Build 20G918) ## Version/Channel Information: <!--Does this issue happen on any other channels? Or is it specific to a certain channel?--> - Can you reproduce this issue with the current release? `No` - Can you reproduce this issue with the beta channel? `Unknown` - Can you reproduce this issue with the nightly channel? `Yes` /cc @fallaciousreasoning @petemill @mattmcalister @rebron @brave/qa-team
1.0
Brave News `Customize` dialog is blank - <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue. PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE. INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED--> ## Description <!--Provide a brief description of the issue--> ## Steps to Reproduce <!--Please add a series of steps to reproduce the issue--> 1. install 1.48.15 2. launch Brave 3. load [theatlantic.com](http://theatlantic.com/) 4. click on the brand-new RSS-feed icon in the URL bar 5. click on Best of The Atlantic 6. click on Manage feeds… 7. click Turn on Brave News ## Actual result: <!--Please add screenshots if needed--> Blank `Customize Brave News` dialog #### Screencast: ![blank-page](https://user-images.githubusercontent.com/387249/204673431-ef145180-683c-4c00-856c-6b34218e48a2.gif) ## Expected result: `Customize Brave News` dialog, populated with `theatlantic.com` `Best of the Atlantic` feed shown under `Following` ## Reproduces how often: <!--[Easily reproduced/Intermittent issue/No steps to reproduce]--> 100% ## Brave version (brave://version info) <!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details--> Brave | 1.48.15 Chromium: 108.0.5359.62 (Official Build) nightly (x86_64) -- | -- Revision | 041930a89a990cfab0315a2d9f20d6429a4a67cf-refs/branch-heads/5359@{#938} OS | macOS Version 11.7.1 (Build 20G918) ## Version/Channel Information: <!--Does this issue happen on any other channels? Or is it specific to a certain channel?--> - Can you reproduce this issue with the current release? `No` - Can you reproduce this issue with the beta channel? `Unknown` - Can you reproduce this issue with the nightly channel? `Yes` /cc @fallaciousreasoning @petemill @mattmcalister @rebron @brave/qa-team
test
brave news customize dialog is blank have you searched for similar issues before submitting this issue please check the open issues and add a note before logging a new issue please use the template below to provide information about the issue insufficient info will get the issue closed it will only be reopened after sufficient info is provided description steps to reproduce install launch brave load click on the brand new rss feed icon in the url bar click on best of the atlantic click on manage feeds… click turn on brave news actual result blank customize brave news dialog screencast expected result customize brave news dialog populated with theatlantic com best of the atlantic feed shown under following reproduces how often brave version brave version info brave chromium   official build  nightly  revision refs branch heads os macos version build version channel information can you reproduce this issue with the current release no can you reproduce this issue with the beta channel unknown can you reproduce this issue with the nightly channel yes cc fallaciousreasoning petemill mattmcalister rebron brave qa team
1
175,215
27,808,987,668
IssuesEvent
2023-03-17 23:58:58
chapel-lang/chapel
https://api.github.com/repos/chapel-lang/chapel
opened
Promote `--print-chpl-home` to a user flag and split it into multiple flags
type: Design area: Compiler user issue
In https://github.com/chapel-lang/chapel/issues/21622, it was pointed out that the definition of `CHPL_HOME` can be vague to a user making use of a `make install` version of Chapel. PR #21867 took a step toward making it better by updating the documentation to describe the interpretation of `CHPL_HOME` in these settings, but is the sort of documentation someone might forget, or never read (particularly if they are using an installation of Chapel). In this issue, I'm proposing addressing this by making `--print-chpl-home` into a user-facing flag so that it shows up in the `chpl --help` output and man page for someone trying to understand its value. I believe that these changes would be sufficient to close #21622. At present, the flag prints out not just `CHPL_HOME`, but also the path to `chpl` (after a tab) and — if `./configure --prefix` was used at any point in the repo and was not cleaned up afterwards — the configured prefix location (on its own line with a comment prefix). In this issue, I'm also proposing splitting this into multiple flags to clarify / simplify the output. Specifically: * `--print-chpl-home` will just print out $CHPL_HOME * `--print-chpl-loc` will print out the path to `chpl` * for now I'm not planning on preserving the query of the prefix because it's not something that I think I'd find useful as a user, and I couldn't find any tests or code that made use of it; we could always add it later as a user or developer flag if/when needed
1.0
Promote `--print-chpl-home` to a user flag and split it into multiple flags - In https://github.com/chapel-lang/chapel/issues/21622, it was pointed out that the definition of `CHPL_HOME` can be vague to a user making use of a `make install` version of Chapel. PR #21867 took a step toward making it better by updating the documentation to describe the interpretation of `CHPL_HOME` in these settings, but is the sort of documentation someone might forget, or never read (particularly if they are using an installation of Chapel). In this issue, I'm proposing addressing this by making `--print-chpl-home` into a user-facing flag so that it shows up in the `chpl --help` output and man page for someone trying to understand its value. I believe that these changes would be sufficient to close #21622. At present, the flag prints out not just `CHPL_HOME`, but also the path to `chpl` (after a tab) and — if `./configure --prefix` was used at any point in the repo and was not cleaned up afterwards — the configured prefix location (on its own line with a comment prefix). In this issue, I'm also proposing splitting this into multiple flags to clarify / simplify the output. Specifically: * `--print-chpl-home` will just print out $CHPL_HOME * `--print-chpl-loc` will print out the path to `chpl` * for now I'm not planning on preserving the query of the prefix because it's not something that I think I'd find useful as a user, and I couldn't find any tests or code that made use of it; we could always add it later as a user or developer flag if/when needed
non_test
promote print chpl home to a user flag and split it into multiple flags in it was pointed out that the definition of chpl home can be vague to a user making use of a make install version of chapel pr took a step toward making it better by updating the documentation to describe the interpretation of chpl home in these settings but is the sort of documentation someone might forget or never read particularly if they are using an installation of chapel in this issue i m proposing addressing this by making print chpl home into a user facing flag so that it shows up in the chpl help output and man page for someone trying to understand its value i believe that these changes would be sufficient to close at present the flag prints out not just chpl home but also the path to chpl after a tab and — if configure prefix was used at any point in the repo and was not cleaned up afterwards — the configured prefix location on its own line with a comment prefix in this issue i m also proposing splitting this into multiple flags to clarify simplify the output specifically print chpl home will just print out chpl home print chpl loc will print out the path to chpl for now i m not planning on preserving the query of the prefix because it s not something that i think i d find useful as a user and i couldn t find any tests or code that made use of it we could always add it later as a user or developer flag if when needed
0
26,600
12,439,082,085
IssuesEvent
2020-05-26 09:30:29
terraform-providers/terraform-provider-azurerm
https://api.github.com/repos/terraform-providers/terraform-provider-azurerm
closed
Azure RM 2.x "azurerm_linux_virtual_machine_scale_set" upgrade policy Manual doesn't work, rotates VMs each time
question service/vmss
<!--- Please note the following potential times when an issue might be in Terraform core: * [Configuration Language](https://www.terraform.io/docs/configuration/index.html) or resource ordering issues * [State](https://www.terraform.io/docs/state/index.html) and [State Backend](https://www.terraform.io/docs/backends/index.html) issues * [Provisioner](https://www.terraform.io/docs/provisioners/index.html) issues * [Registry](https://registry.terraform.io/) issues * Spans resources across multiple providers If you are running into one of these scenarios, we recommend opening an issue in the [Terraform core repository](https://github.com/hashicorp/terraform/) instead. ---> <!--- Please keep this note for the community ---> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request * Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request * If you are interested in working on this issue or have submitted a pull request, please leave a comment <!--- Thank you for keeping this note for the community ---> ### Terraform (and AzureRM Provider) Version Terraform v0.12.24 provider.azurerm v2.9.0 ### Affected Resource(s) azurerm_linux_virtual_machine_scale_set ### Terraform Configuration Files <!--- Information about code formatting: https://help.github.com/articles/basic-writing-and-formatting-syntax/#quoting-code ---> ```hcl resource "azurerm_linux_virtual_machine_scale_set" "set" { name = "${var.name}-${var.global_vars.environment}-set" resource_group_name = var.global_vars.resource_group location = var.global_vars.location sku = var.vm_size instances = var.number_of_servers zones = [1, 2, 3] upgrade_mode = "Manual" admin_username = "devops" admin_ssh_key { username = "devops" public_key = file("ssh_public_id_rsa.pub") } boot_diagnostics { storage_account_uri = var.global_vars.storage_blob_uri } source_image_id = var.source_image_id os_disk { storage_account_type = "StandardSSD_LRS" caching = "ReadWrite" disk_size_gb = var.disk_size_gb } network_interface { name = "${var.name}-${var.global_vars.environment}-nic" primary = true ip_configuration { name = "internal" primary = true subnet_id = var.subnet # Can pass here the application gateway backend pools to connect those instances to app gateway application_gateway_backend_address_pool_ids = length(var.app_gw_address_pool_ids) > 0 ? var.app_gw_address_pool_ids : null # Can connect to LB pool that was created above, as well, optional load_balancer_backend_address_pool_ids = var.create_lb ? [azurerm_lb_backend_address_pool.addresspool[0].id] : null } } custom_data = base64encode(templatefile("user_data.sh.tmpl", { environment = var.global_vars.environment host_type = var.name })) tags = var.tags } ``` ### Expected Behavior When upgrade_mode = "Manual" VMSS should not rotate the VMs when custom_data script changes ### Actual Behavior VMs rotated any time a custom_data script changes. ### Steps to Reproduce Create VMSS, put upgrade_mode=Manual, assign a custom_data script (some bash). Any time you update the bash script, VMs will be forced to be recreated/rebooted (I'm not sure what exactly happens under the hood but I end up with a clean VM each time, I guess it's recreated. Azure support technician says it's not the Azure side of the VMSS logic flaw that's recreating them on custom_data updates, but a "Terraform Plugin" entity logged as forcing the VMs to reboot/recreate o.O , how can I solve this? I want them to be recreated only on manual action.
1.0
Azure RM 2.x "azurerm_linux_virtual_machine_scale_set" upgrade policy Manual doesn't work, rotates VMs each time - <!--- Please note the following potential times when an issue might be in Terraform core: * [Configuration Language](https://www.terraform.io/docs/configuration/index.html) or resource ordering issues * [State](https://www.terraform.io/docs/state/index.html) and [State Backend](https://www.terraform.io/docs/backends/index.html) issues * [Provisioner](https://www.terraform.io/docs/provisioners/index.html) issues * [Registry](https://registry.terraform.io/) issues * Spans resources across multiple providers If you are running into one of these scenarios, we recommend opening an issue in the [Terraform core repository](https://github.com/hashicorp/terraform/) instead. ---> <!--- Please keep this note for the community ---> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request * Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request * If you are interested in working on this issue or have submitted a pull request, please leave a comment <!--- Thank you for keeping this note for the community ---> ### Terraform (and AzureRM Provider) Version Terraform v0.12.24 provider.azurerm v2.9.0 ### Affected Resource(s) azurerm_linux_virtual_machine_scale_set ### Terraform Configuration Files <!--- Information about code formatting: https://help.github.com/articles/basic-writing-and-formatting-syntax/#quoting-code ---> ```hcl resource "azurerm_linux_virtual_machine_scale_set" "set" { name = "${var.name}-${var.global_vars.environment}-set" resource_group_name = var.global_vars.resource_group location = var.global_vars.location sku = var.vm_size instances = var.number_of_servers zones = [1, 2, 3] upgrade_mode = "Manual" admin_username = "devops" admin_ssh_key { username = "devops" public_key = file("ssh_public_id_rsa.pub") } boot_diagnostics { storage_account_uri = var.global_vars.storage_blob_uri } source_image_id = var.source_image_id os_disk { storage_account_type = "StandardSSD_LRS" caching = "ReadWrite" disk_size_gb = var.disk_size_gb } network_interface { name = "${var.name}-${var.global_vars.environment}-nic" primary = true ip_configuration { name = "internal" primary = true subnet_id = var.subnet # Can pass here the application gateway backend pools to connect those instances to app gateway application_gateway_backend_address_pool_ids = length(var.app_gw_address_pool_ids) > 0 ? var.app_gw_address_pool_ids : null # Can connect to LB pool that was created above, as well, optional load_balancer_backend_address_pool_ids = var.create_lb ? [azurerm_lb_backend_address_pool.addresspool[0].id] : null } } custom_data = base64encode(templatefile("user_data.sh.tmpl", { environment = var.global_vars.environment host_type = var.name })) tags = var.tags } ``` ### Expected Behavior When upgrade_mode = "Manual" VMSS should not rotate the VMs when custom_data script changes ### Actual Behavior VMs rotated any time a custom_data script changes. ### Steps to Reproduce Create VMSS, put upgrade_mode=Manual, assign a custom_data script (some bash). Any time you update the bash script, VMs will be forced to be recreated/rebooted (I'm not sure what exactly happens under the hood but I end up with a clean VM each time, I guess it's recreated. Azure support technician says it's not the Azure side of the VMSS logic flaw that's recreating them on custom_data updates, but a "Terraform Plugin" entity logged as forcing the VMs to reboot/recreate o.O , how can I solve this? I want them to be recreated only on manual action.
non_test
azure rm x azurerm linux virtual machine scale set upgrade policy manual doesn t work rotates vms each time please note the following potential times when an issue might be in terraform core or resource ordering issues and issues issues issues spans resources across multiple providers if you are running into one of these scenarios we recommend opening an issue in the instead community note please vote on this issue by adding a 👍 to the original issue to help the community and maintainers prioritize this request please do not leave or me too comments they generate extra noise for issue followers and do not help prioritize the request if you are interested in working on this issue or have submitted a pull request please leave a comment terraform and azurerm provider version terraform provider azurerm affected resource s azurerm linux virtual machine scale set terraform configuration files hcl resource azurerm linux virtual machine scale set set name var name var global vars environment set resource group name var global vars resource group location var global vars location sku var vm size instances var number of servers zones upgrade mode manual admin username devops admin ssh key username devops public key file ssh public id rsa pub boot diagnostics storage account uri var global vars storage blob uri source image id var source image id os disk storage account type standardssd lrs caching readwrite disk size gb var disk size gb network interface name var name var global vars environment nic primary true ip configuration name internal primary true subnet id var subnet can pass here the application gateway backend pools to connect those instances to app gateway application gateway backend address pool ids length var app gw address pool ids var app gw address pool ids null can connect to lb pool that was created above as well optional load balancer backend address pool ids var create lb id null custom data templatefile user data sh tmpl environment var global vars environment host type var name tags var tags expected behavior when upgrade mode manual vmss should not rotate the vms when custom data script changes actual behavior vms rotated any time a custom data script changes steps to reproduce create vmss put upgrade mode manual assign a custom data script some bash any time you update the bash script vms will be forced to be recreated rebooted i m not sure what exactly happens under the hood but i end up with a clean vm each time i guess it s recreated azure support technician says it s not the azure side of the vmss logic flaw that s recreating them on custom data updates but a terraform plugin entity logged as forcing the vms to reboot recreate o o how can i solve this i want them to be recreated only on manual action
0
69,155
13,213,184,206
IssuesEvent
2020-08-16 11:27:35
devopsacademyau/2020-jun-project1-group2
https://api.github.com/repos/devopsacademyau/2020-jun-project1-group2
closed
RDS Aurora Database
application terraform-code
**Objectives:** - Create a RDS Aurora MySQL (5.7+) database to be used by Wordpress. Aurora can be Serverless. **Acceptance Criteria:** - All resources to be created using Terraform - RDS Aurora Mysql (version 5.7+) - Serverless version is recommended due to costs - No need for aurora replica - Use a random generated password and upload to SSM Parameter Store for future use - Use custom VPC from network stack (private subnets) - Backup just for one day retention is fine - Encryption enabled - No need for performance insights, enhanced monitoring and IAM authentication - Disable deletion protection - Database need to be accessible from public EC2 running on public subnets - GitHub can't have any secrets commited.
1.0
RDS Aurora Database - **Objectives:** - Create a RDS Aurora MySQL (5.7+) database to be used by Wordpress. Aurora can be Serverless. **Acceptance Criteria:** - All resources to be created using Terraform - RDS Aurora Mysql (version 5.7+) - Serverless version is recommended due to costs - No need for aurora replica - Use a random generated password and upload to SSM Parameter Store for future use - Use custom VPC from network stack (private subnets) - Backup just for one day retention is fine - Encryption enabled - No need for performance insights, enhanced monitoring and IAM authentication - Disable deletion protection - Database need to be accessible from public EC2 running on public subnets - GitHub can't have any secrets commited.
non_test
rds aurora database objectives create a rds aurora mysql database to be used by wordpress aurora can be serverless acceptance criteria all resources to be created using terraform rds aurora mysql version serverless version is recommended due to costs no need for aurora replica use a random generated password and upload to ssm parameter store for future use use custom vpc from network stack private subnets backup just for one day retention is fine encryption enabled no need for performance insights enhanced monitoring and iam authentication disable deletion protection database need to be accessible from public running on public subnets github can t have any secrets commited
0
323,689
27,747,245,483
IssuesEvent
2023-03-15 17:52:45
brave/brave-browser
https://api.github.com/repos/brave/brave-browser
closed
`Send a tip` tooltip is not shown for Reddit and Twitter publishers
bug polish feature/rewards priority/P4 QA/Yes QA/Test-Plan-Specified greaselion OS/Desktop
<!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue. PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE. INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED--> ## Description <!--Provide a brief description of the issue--> `Send a tip` tooltip is not shown for Reddit and Twitter publishers ## Actual result: <!--Please add screenshots if needed--> Reddit ![image](https://user-images.githubusercontent.com/38657976/191787863-201721c7-f1fe-47ef-a6be-0f51380052a8.png) Twitter ![image](https://user-images.githubusercontent.com/38657976/191788251-4852cd05-2a5a-43b1-98c3-3ae5850dbcd7.png) ## Expected result: discussed with @mkarolin As per the code the `Send a tip` tooltip should be shown for Twitter and reddit ![image](https://user-images.githubusercontent.com/38657976/191789689-c3a9a0eb-e0d6-4e08-b21e-d028ec601865.png) ## Reproduces how often: <!--[Easily reproduced/Intermittent issue/No steps to reproduce]--> Easy ## Brave version (brave://version info) <!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details--> Brave | 1.44.95 Chromium: 106.0.5249.40 (Official Build) (64-bit) -- | -- Revision | fab1d91915d2722d6339aaa7f4e9ce44f1e9b103-refs/branch-heads/5249@{#442} OS | Windows 10 Version 21H2 (Build 19044.2006) ## Version/Channel Information: <!--Does this issue happen on any other channels? Or is it specific to a certain channel?--> - Can you reproduce this issue with the current release? Yes - Can you reproduce this issue with the beta channel? Yes - Can you reproduce this issue with the nightly channel? Yes ## Other Additional Information: - Does the issue resolve itself when disabling Brave Shields? NA - Does the issue resolve itself when disabling Brave Rewards? NA - Is the issue reproducible on the latest version of Chrome? NA ## Miscellaneous Information: <!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue--> cc: @brave/qa-team @Miyayes
1.0
`Send a tip` tooltip is not shown for Reddit and Twitter publishers - <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue. PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE. INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED--> ## Description <!--Provide a brief description of the issue--> `Send a tip` tooltip is not shown for Reddit and Twitter publishers ## Actual result: <!--Please add screenshots if needed--> Reddit ![image](https://user-images.githubusercontent.com/38657976/191787863-201721c7-f1fe-47ef-a6be-0f51380052a8.png) Twitter ![image](https://user-images.githubusercontent.com/38657976/191788251-4852cd05-2a5a-43b1-98c3-3ae5850dbcd7.png) ## Expected result: discussed with @mkarolin As per the code the `Send a tip` tooltip should be shown for Twitter and reddit ![image](https://user-images.githubusercontent.com/38657976/191789689-c3a9a0eb-e0d6-4e08-b21e-d028ec601865.png) ## Reproduces how often: <!--[Easily reproduced/Intermittent issue/No steps to reproduce]--> Easy ## Brave version (brave://version info) <!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details--> Brave | 1.44.95 Chromium: 106.0.5249.40 (Official Build) (64-bit) -- | -- Revision | fab1d91915d2722d6339aaa7f4e9ce44f1e9b103-refs/branch-heads/5249@{#442} OS | Windows 10 Version 21H2 (Build 19044.2006) ## Version/Channel Information: <!--Does this issue happen on any other channels? Or is it specific to a certain channel?--> - Can you reproduce this issue with the current release? Yes - Can you reproduce this issue with the beta channel? Yes - Can you reproduce this issue with the nightly channel? Yes ## Other Additional Information: - Does the issue resolve itself when disabling Brave Shields? NA - Does the issue resolve itself when disabling Brave Rewards? NA - Is the issue reproducible on the latest version of Chrome? NA ## Miscellaneous Information: <!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue--> cc: @brave/qa-team @Miyayes
test
send a tip tooltip is not shown for reddit and twitter publishers have you searched for similar issues before submitting this issue please check the open issues and add a note before logging a new issue please use the template below to provide information about the issue insufficient info will get the issue closed it will only be reopened after sufficient info is provided description send a tip tooltip is not shown for reddit and twitter publishers actual result reddit twitter expected result discussed with mkarolin as per the code the send a tip tooltip should be shown for twitter and reddit reproduces how often easy brave version brave version info brave chromium   official build   bit revision refs branch heads os windows  version build version channel information can you reproduce this issue with the current release yes can you reproduce this issue with the beta channel yes can you reproduce this issue with the nightly channel yes other additional information does the issue resolve itself when disabling brave shields na does the issue resolve itself when disabling brave rewards na is the issue reproducible on the latest version of chrome na miscellaneous information cc brave qa team miyayes
1
54,661
13,915,834,000
IssuesEvent
2020-10-21 01:43:56
rvvergara/bookstore-react-redux-app
https://api.github.com/repos/rvvergara/bookstore-react-redux-app
opened
WS-2019-0424 (Medium) detected in elliptic-6.4.1.tgz
security vulnerability
## WS-2019-0424 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>elliptic-6.4.1.tgz</b></p></summary> <p>EC cryptography</p> <p>Library home page: <a href="https://registry.npmjs.org/elliptic/-/elliptic-6.4.1.tgz">https://registry.npmjs.org/elliptic/-/elliptic-6.4.1.tgz</a></p> <p>Path to dependency file: bookstore-react-redux-app/node_modules/elliptic/package.json</p> <p>Path to vulnerable library: bookstore-react-redux-app/node_modules/elliptic/package.json</p> <p> Dependency Hierarchy: - react-scripts-3.4.4.tgz (Root Library) - webpack-4.42.0.tgz - node-libs-browser-2.2.1.tgz - crypto-browserify-3.12.0.tgz - create-ecdh-4.0.3.tgz - :x: **elliptic-6.4.1.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/rvvergara/bookstore-react-redux-app/commit/01ffbd3dcc605308fae3822634c12ea63c7a51f8">01ffbd3dcc605308fae3822634c12ea63c7a51f8</a></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> all versions of elliptic are vulnerable to Timing Attack through side-channels. <p>Publish Date: 2019-11-13 <p>URL: <a href=https://github.com/indutny/elliptic/commit/ec735edde187a43693197f6fa3667ceade751a3a>WS-2019-0424</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.9</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Adjacent - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - 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> </details> <p></p> *** Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
True
WS-2019-0424 (Medium) detected in elliptic-6.4.1.tgz - ## WS-2019-0424 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>elliptic-6.4.1.tgz</b></p></summary> <p>EC cryptography</p> <p>Library home page: <a href="https://registry.npmjs.org/elliptic/-/elliptic-6.4.1.tgz">https://registry.npmjs.org/elliptic/-/elliptic-6.4.1.tgz</a></p> <p>Path to dependency file: bookstore-react-redux-app/node_modules/elliptic/package.json</p> <p>Path to vulnerable library: bookstore-react-redux-app/node_modules/elliptic/package.json</p> <p> Dependency Hierarchy: - react-scripts-3.4.4.tgz (Root Library) - webpack-4.42.0.tgz - node-libs-browser-2.2.1.tgz - crypto-browserify-3.12.0.tgz - create-ecdh-4.0.3.tgz - :x: **elliptic-6.4.1.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/rvvergara/bookstore-react-redux-app/commit/01ffbd3dcc605308fae3822634c12ea63c7a51f8">01ffbd3dcc605308fae3822634c12ea63c7a51f8</a></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> all versions of elliptic are vulnerable to Timing Attack through side-channels. <p>Publish Date: 2019-11-13 <p>URL: <a href=https://github.com/indutny/elliptic/commit/ec735edde187a43693197f6fa3667ceade751a3a>WS-2019-0424</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.9</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Adjacent - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - 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> </details> <p></p> *** Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
non_test
ws medium detected in elliptic tgz ws medium severity vulnerability vulnerable library elliptic tgz ec cryptography library home page a href path to dependency file bookstore react redux app node modules elliptic package json path to vulnerable library bookstore react redux app node modules elliptic package json dependency hierarchy react scripts tgz root library webpack tgz node libs browser tgz crypto browserify tgz create ecdh tgz x elliptic tgz vulnerable library found in head commit a href vulnerability details all versions of elliptic are vulnerable to timing attack through side channels publish date url a href cvss score details base score metrics exploitability metrics attack vector adjacent attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact high availability impact none for more information on scores click a href step up your open source security game with whitesource
0
661,041
22,038,984,033
IssuesEvent
2022-05-29 03:18:08
SmashPhil/Vehicles
https://api.github.com/repos/SmashPhil/Vehicles
closed
Game Over prompt when all unloaded pawns die.
Bug Low Priority Backlogged
Load 1 or more pawns into a vehicle. Kill off all remaining pawns. Receive game over prompt.
1.0
Game Over prompt when all unloaded pawns die. - Load 1 or more pawns into a vehicle. Kill off all remaining pawns. Receive game over prompt.
non_test
game over prompt when all unloaded pawns die load or more pawns into a vehicle kill off all remaining pawns receive game over prompt
0
146,286
11,731,215,773
IssuesEvent
2020-03-10 23:23:55
elastic/kibana
https://api.github.com/repos/elastic/kibana
closed
Failing test: X-Pack Saved Object API Integration Tests -- security_and_spaces.x-pack/test/saved_object_api_integration/security_and_spaces/apis/create·ts - saved objects security and spaces enabled create superuser within the default space should return 200 for a non space-aware type
failed-test
A test failed on a tracked branch ``` Error: ECONNREFUSED: Connection refused at Test.assert (/dev/shm/workspace/kibana/node_modules/supertest/lib/test.js:165:15) at assert (/dev/shm/workspace/kibana/node_modules/supertest/lib/test.js:131:12) at /dev/shm/workspace/kibana/node_modules/supertest/lib/test.js:128:5 at Test.Request.callback (/dev/shm/workspace/kibana/node_modules/superagent/lib/node/index.js:718:3) at ClientRequest.req.once.err (/dev/shm/workspace/kibana/node_modules/superagent/lib/node/index.js:646:10) at Socket.socketErrorListener (_http_client.js:392:9) at emitErrorNT (internal/streams/destroy.js:82:8) at emitErrorAndCloseNT (internal/streams/destroy.js:50:3) at process._tickCallback (internal/process/next_tick.js:63:19) ``` First failure: [Jenkins Build](https://kibana-ci.elastic.co/job/elastic+kibana+7.x/1111/) <!-- kibanaCiData = {"failed-test":{"test.class":"X-Pack Saved Object API Integration Tests -- security_and_spaces.x-pack/test/saved_object_api_integration/security_and_spaces/apis/create·ts","test.name":"saved objects security and spaces enabled create superuser within the default space should return 200 for a non space-aware type","test.failCount":1}} -->
1.0
Failing test: X-Pack Saved Object API Integration Tests -- security_and_spaces.x-pack/test/saved_object_api_integration/security_and_spaces/apis/create·ts - saved objects security and spaces enabled create superuser within the default space should return 200 for a non space-aware type - A test failed on a tracked branch ``` Error: ECONNREFUSED: Connection refused at Test.assert (/dev/shm/workspace/kibana/node_modules/supertest/lib/test.js:165:15) at assert (/dev/shm/workspace/kibana/node_modules/supertest/lib/test.js:131:12) at /dev/shm/workspace/kibana/node_modules/supertest/lib/test.js:128:5 at Test.Request.callback (/dev/shm/workspace/kibana/node_modules/superagent/lib/node/index.js:718:3) at ClientRequest.req.once.err (/dev/shm/workspace/kibana/node_modules/superagent/lib/node/index.js:646:10) at Socket.socketErrorListener (_http_client.js:392:9) at emitErrorNT (internal/streams/destroy.js:82:8) at emitErrorAndCloseNT (internal/streams/destroy.js:50:3) at process._tickCallback (internal/process/next_tick.js:63:19) ``` First failure: [Jenkins Build](https://kibana-ci.elastic.co/job/elastic+kibana+7.x/1111/) <!-- kibanaCiData = {"failed-test":{"test.class":"X-Pack Saved Object API Integration Tests -- security_and_spaces.x-pack/test/saved_object_api_integration/security_and_spaces/apis/create·ts","test.name":"saved objects security and spaces enabled create superuser within the default space should return 200 for a non space-aware type","test.failCount":1}} -->
test
failing test x pack saved object api integration tests security and spaces x pack test saved object api integration security and spaces apis create·ts saved objects security and spaces enabled create superuser within the default space should return for a non space aware type a test failed on a tracked branch error econnrefused connection refused at test assert dev shm workspace kibana node modules supertest lib test js at assert dev shm workspace kibana node modules supertest lib test js at dev shm workspace kibana node modules supertest lib test js at test request callback dev shm workspace kibana node modules superagent lib node index js at clientrequest req once err dev shm workspace kibana node modules superagent lib node index js at socket socketerrorlistener http client js at emiterrornt internal streams destroy js at emiterrorandclosent internal streams destroy js at process tickcallback internal process next tick js first failure
1
238,162
19,701,717,350
IssuesEvent
2022-01-12 17:15:35
elastic/kibana
https://api.github.com/repos/elastic/kibana
opened
Failing test: X-Pack Rule Registry Alerts Client API Integration Tests.x-pack/test/rule_registry/spaces_only/tests/trial/get_alert_by_id·ts - rule registry spaces only: trial Alerts - GET - RBAC "before all" hook for "should return a 404 when superuser accesses not-existent alert"
failed-test
A test failed on a tracked branch ``` ResponseError: illegal_argument_exception: [illegal_argument_exception] Reason: request [/.alerts-observability.apm.alerts] contains unrecognized parameter: [include_type_name] at onBody (/opt/local-ssd/buildkite/builds/kb-n2-4-659a9aa4dc1658d5/elastic/kibana-7-dot-latest-es-forward-compatibility/kibana/node_modules/@elastic/elasticsearch/lib/Transport.js:367:23) at IncomingMessage.onEnd (/opt/local-ssd/buildkite/builds/kb-n2-4-659a9aa4dc1658d5/elastic/kibana-7-dot-latest-es-forward-compatibility/kibana/node_modules/@elastic/elasticsearch/lib/Transport.js:291:11) at IncomingMessage.emit (node:events:402:35) at endReadableNT (node:internal/streams/readable:1343:12) at processTicksAndRejections (node:internal/process/task_queues:83:21) { meta: { body: { error: [Object], status: 400 }, statusCode: 400, headers: { 'x-elastic-product': 'Elasticsearch', 'content-type': 'application/json;charset=utf-8', 'content-length': '329' }, meta: { context: null, request: [Object], name: 'elasticsearch-js', connection: [Object], attempts: 0, aborted: false } } } ``` First failure: [CI Build - 7.17](https://buildkite.com/elastic/kibana-7-dot-latest-es-forward-compatibility/builds/1#6c032906-9be2-48c5-871c-ed0ecf8aa82e) <!-- kibanaCiData = {"failed-test":{"test.class":"X-Pack Rule Registry Alerts Client API Integration Tests.x-pack/test/rule_registry/spaces_only/tests/trial/get_alert_by_id·ts","test.name":"rule registry spaces only: trial Alerts - GET - RBAC \"before all\" hook for \"should return a 404 when superuser accesses not-existent alert\"","test.failCount":1}} -->
1.0
Failing test: X-Pack Rule Registry Alerts Client API Integration Tests.x-pack/test/rule_registry/spaces_only/tests/trial/get_alert_by_id·ts - rule registry spaces only: trial Alerts - GET - RBAC "before all" hook for "should return a 404 when superuser accesses not-existent alert" - A test failed on a tracked branch ``` ResponseError: illegal_argument_exception: [illegal_argument_exception] Reason: request [/.alerts-observability.apm.alerts] contains unrecognized parameter: [include_type_name] at onBody (/opt/local-ssd/buildkite/builds/kb-n2-4-659a9aa4dc1658d5/elastic/kibana-7-dot-latest-es-forward-compatibility/kibana/node_modules/@elastic/elasticsearch/lib/Transport.js:367:23) at IncomingMessage.onEnd (/opt/local-ssd/buildkite/builds/kb-n2-4-659a9aa4dc1658d5/elastic/kibana-7-dot-latest-es-forward-compatibility/kibana/node_modules/@elastic/elasticsearch/lib/Transport.js:291:11) at IncomingMessage.emit (node:events:402:35) at endReadableNT (node:internal/streams/readable:1343:12) at processTicksAndRejections (node:internal/process/task_queues:83:21) { meta: { body: { error: [Object], status: 400 }, statusCode: 400, headers: { 'x-elastic-product': 'Elasticsearch', 'content-type': 'application/json;charset=utf-8', 'content-length': '329' }, meta: { context: null, request: [Object], name: 'elasticsearch-js', connection: [Object], attempts: 0, aborted: false } } } ``` First failure: [CI Build - 7.17](https://buildkite.com/elastic/kibana-7-dot-latest-es-forward-compatibility/builds/1#6c032906-9be2-48c5-871c-ed0ecf8aa82e) <!-- kibanaCiData = {"failed-test":{"test.class":"X-Pack Rule Registry Alerts Client API Integration Tests.x-pack/test/rule_registry/spaces_only/tests/trial/get_alert_by_id·ts","test.name":"rule registry spaces only: trial Alerts - GET - RBAC \"before all\" hook for \"should return a 404 when superuser accesses not-existent alert\"","test.failCount":1}} -->
test
failing test x pack rule registry alerts client api integration tests x pack test rule registry spaces only tests trial get alert by id·ts rule registry spaces only trial alerts get rbac before all hook for should return a when superuser accesses not existent alert a test failed on a tracked branch responseerror illegal argument exception reason request contains unrecognized parameter at onbody opt local ssd buildkite builds kb elastic kibana dot latest es forward compatibility kibana node modules elastic elasticsearch lib transport js at incomingmessage onend opt local ssd buildkite builds kb elastic kibana dot latest es forward compatibility kibana node modules elastic elasticsearch lib transport js at incomingmessage emit node events at endreadablent node internal streams readable at processticksandrejections node internal process task queues meta body error status statuscode headers x elastic product elasticsearch content type application json charset utf content length meta context null request name elasticsearch js connection attempts aborted false first failure
1
198,865
15,007,409,971
IssuesEvent
2021-01-31 04:39:12
mozilla-mobile/firefox-ios
https://api.github.com/repos/mozilla-mobile/firefox-ios
opened
Pa4 web
eng:intermittent-test
### Bitrise Test Run: Provide a Bitrise test run report link here showcasing the problem ### Stacktrace: ### Build:
1.0
Pa4 web - ### Bitrise Test Run: Provide a Bitrise test run report link here showcasing the problem ### Stacktrace: ### Build:
test
web bitrise test run provide a bitrise test run report link here showcasing the problem stacktrace build
1
259,371
22,470,895,869
IssuesEvent
2022-06-22 08:01:48
gravitee-io/issues
https://api.github.com/repos/gravitee-io/issues
closed
[JEST test] create several plan flows and use them
type: technical project: APIM dark matter Test Automation
### Scenario the idea is to test that when we create several plan flows, it triggers the one expected regarding the call made to the gateway ### Additional information
1.0
[JEST test] create several plan flows and use them - ### Scenario the idea is to test that when we create several plan flows, it triggers the one expected regarding the call made to the gateway ### Additional information
test
create several plan flows and use them scenario the idea is to test that when we create several plan flows it triggers the one expected regarding the call made to the gateway additional information
1
46,052
2,945,362,146
IssuesEvent
2015-07-03 12:27:43
nextgis/ngm_clink_monitoring
https://api.github.com/repos/nextgis/ngm_clink_monitoring
opened
Ошибка при открытии карты
bug Low Priority
У Сергея на девайся воспроизводится стабильно Попросил установить тестовую сборку. Ждем репортов.
1.0
Ошибка при открытии карты - У Сергея на девайся воспроизводится стабильно Попросил установить тестовую сборку. Ждем репортов.
non_test
ошибка при открытии карты у сергея на девайся воспроизводится стабильно попросил установить тестовую сборку ждем репортов
0
116,225
24,884,523,559
IssuesEvent
2022-10-28 06:22:01
appsmithorg/appsmith
https://api.github.com/repos/appsmithorg/appsmith
closed
[Bug]: Internal server error when the evaluated value is of type ARRAY in MySQL
Bug Needs Triaging MySQL BE Coders Pod Datatype issue Data Platform Pod Integrations Pod
### Is there an existing issue for this? - [X] I have searched the existing issues ### Description #### Screenshot of Error ![bindingparameters_error_mysql_1](https://user-images.githubusercontent.com/3524599/196618603-e45f8d8d-d9ab-4b58-bb5a-d0a1224e5d7f.png) [Relevant thread on Slack](https://theappsmith.slack.com/archives/CGBPVEJ5C/p1666041302966259) [Relevant thread on Discord](https://discord.com/channels/725602949748752515/1031589632728645693) ### Steps To Reproduce - Create a multi-select widget - Create a MySQL table with a varchar column, say x - Try to insert the selected values from the multi-select into that varchar column x through the following query ` INSERT INTO my_table(x) VALUES({{MultiSelect.selectedOptionValues}});` - You will notice an internal server error ### RCA Let's say the selected options in the multi-select widget are `["x","y"]`. So the evaluated value of this binding `{{MultiSelect.selectedOptionValues}}` becomes `["x", "y"]`. For such a value the client side identifies the data type as an array. As MySQL doesn't have any support for array data type, we didn't add any support for the array data type in the MySQL plugin when we implemented the change required for **Datatype Handling V1** w.r.t. MySQL. We expected that the fallback data type i.e. the `StringType` would take over in such scenarios. But our assumption went wrong. The following code snippet is used to get the `AppsmithType` from the provided client-side data type and the evaluated value. ``` public static AppsmithType getAppsmithType(ClientDataType clientDataType, String value, Map<ClientDataType, List<AppsmithType>> pluginSpecificTypes) { for (AppsmithType currentType : pluginSpecificTypes.get(clientDataType)) { if (currentType.test(value)) { return currentType; } } //Ideally we shouldn't reach here but if we do then we will return the FallbackType return new FallbackType(); } ``` When `clientDataType` is of `ARRAY` the map called `pluginSpecificTypes` , provided by the respective plugin in our case which is MySQLPlugin, doesn't have any key for ARRAY. Thus `pluginSpecificTypes.get(clientDataType)` returns `null` and it throws a `NullPointerException` from the beginning of the for-loop. ### Current Workaround If the client side identifies the data type as an array then we cannot prevent it to happen. The gimmick is to take out the array notation from the evaluated value of that binding. And get the values of the multi-select widget without having any array notation through a JS object. It's a two steps method We are going to rewrite the following query `INSERT INTO my_table(x) VALUES({{MultiSelect.selectedOptionValues}});` Two-step process - Make the array notation part of your query i.e. take it out from the evaluated value ` INSERT INTO my_table(x) VALUES(CONCAT('[', {{JSObject.getValuesOfMultiSelect()}}, ']');` - Write the JSObject.getValuesOfMultiSelect() method ``` export default { getValuesOfMultiSelect: () => { var a = MultiSelect2.selectedOptionValues.join(); return a ? a : null; } } ``` Now the evaluated value of `{{JSObject.getValuesOfMultiSelect()}} `would be `x,y` for which the client-side data type is String. ### Permanent Solution The right solution would be either to add a `null` check on `pluginSpecificTypes.get(clientDataType)` or add `ARRAY` type in the `pluginSpecificTypes` map. #### More This is the current pluginSpecificTypes map of MySQLPlugin ``` pluginSpecificTypes.put(ClientDataType.NULL, List.of(new NullType())); pluginSpecificTypes.put(ClientDataType.BOOLEAN, List.of(new MySQLBooleanType())); pluginSpecificTypes.put(ClientDataType.NUMBER, List.of( new IntegerType(), new LongType(), new DoubleType(), new BigDecimalType() )); pluginSpecificTypes.put(ClientDataType.OBJECT, List.of(new JsonObjectType())); pluginSpecificTypes.put(ClientDataType.STRING, List.of( new TimeType(), new MySQLDateType(), new MySQLDateTimeType(), new StringType() )); ``` After adding the ARRAY type in the map it would look like ``` pluginSpecificTypes.put(ClientDataType.NULL, List.of(new NullType())); pluginSpecificTypes.put(ClientDataType.BOOLEAN, List.of(new MySQLBooleanType())); pluginSpecificTypes.put(ClientDataType.NUMBER, List.of( new IntegerType(), new LongType(), new DoubleType(), new BigDecimalType() )); pluginSpecificTypes.put(ClientDataType.OBJECT, List.of(new JsonObjectType())); pluginSpecificTypes.put(ClientDataType.STRING, List.of( new TimeType(), new MySQLDateType(), new MySQLDateTimeType(), new StringType() )); pluginSpecificTypes.put(ClientDataType.ARRAY, List.of(new StringType()); ``` ### Public Sample App _No response_ ### Version Self Hosted <img src="https://front.com/assets/img/favicons/favicon-32x32.png" height="16" width="16" alt="Front logo" /> [Front conversations](https://app.frontapp.com/open/top_5d6rw)
1.0
[Bug]: Internal server error when the evaluated value is of type ARRAY in MySQL - ### Is there an existing issue for this? - [X] I have searched the existing issues ### Description #### Screenshot of Error ![bindingparameters_error_mysql_1](https://user-images.githubusercontent.com/3524599/196618603-e45f8d8d-d9ab-4b58-bb5a-d0a1224e5d7f.png) [Relevant thread on Slack](https://theappsmith.slack.com/archives/CGBPVEJ5C/p1666041302966259) [Relevant thread on Discord](https://discord.com/channels/725602949748752515/1031589632728645693) ### Steps To Reproduce - Create a multi-select widget - Create a MySQL table with a varchar column, say x - Try to insert the selected values from the multi-select into that varchar column x through the following query ` INSERT INTO my_table(x) VALUES({{MultiSelect.selectedOptionValues}});` - You will notice an internal server error ### RCA Let's say the selected options in the multi-select widget are `["x","y"]`. So the evaluated value of this binding `{{MultiSelect.selectedOptionValues}}` becomes `["x", "y"]`. For such a value the client side identifies the data type as an array. As MySQL doesn't have any support for array data type, we didn't add any support for the array data type in the MySQL plugin when we implemented the change required for **Datatype Handling V1** w.r.t. MySQL. We expected that the fallback data type i.e. the `StringType` would take over in such scenarios. But our assumption went wrong. The following code snippet is used to get the `AppsmithType` from the provided client-side data type and the evaluated value. ``` public static AppsmithType getAppsmithType(ClientDataType clientDataType, String value, Map<ClientDataType, List<AppsmithType>> pluginSpecificTypes) { for (AppsmithType currentType : pluginSpecificTypes.get(clientDataType)) { if (currentType.test(value)) { return currentType; } } //Ideally we shouldn't reach here but if we do then we will return the FallbackType return new FallbackType(); } ``` When `clientDataType` is of `ARRAY` the map called `pluginSpecificTypes` , provided by the respective plugin in our case which is MySQLPlugin, doesn't have any key for ARRAY. Thus `pluginSpecificTypes.get(clientDataType)` returns `null` and it throws a `NullPointerException` from the beginning of the for-loop. ### Current Workaround If the client side identifies the data type as an array then we cannot prevent it to happen. The gimmick is to take out the array notation from the evaluated value of that binding. And get the values of the multi-select widget without having any array notation through a JS object. It's a two steps method We are going to rewrite the following query `INSERT INTO my_table(x) VALUES({{MultiSelect.selectedOptionValues}});` Two-step process - Make the array notation part of your query i.e. take it out from the evaluated value ` INSERT INTO my_table(x) VALUES(CONCAT('[', {{JSObject.getValuesOfMultiSelect()}}, ']');` - Write the JSObject.getValuesOfMultiSelect() method ``` export default { getValuesOfMultiSelect: () => { var a = MultiSelect2.selectedOptionValues.join(); return a ? a : null; } } ``` Now the evaluated value of `{{JSObject.getValuesOfMultiSelect()}} `would be `x,y` for which the client-side data type is String. ### Permanent Solution The right solution would be either to add a `null` check on `pluginSpecificTypes.get(clientDataType)` or add `ARRAY` type in the `pluginSpecificTypes` map. #### More This is the current pluginSpecificTypes map of MySQLPlugin ``` pluginSpecificTypes.put(ClientDataType.NULL, List.of(new NullType())); pluginSpecificTypes.put(ClientDataType.BOOLEAN, List.of(new MySQLBooleanType())); pluginSpecificTypes.put(ClientDataType.NUMBER, List.of( new IntegerType(), new LongType(), new DoubleType(), new BigDecimalType() )); pluginSpecificTypes.put(ClientDataType.OBJECT, List.of(new JsonObjectType())); pluginSpecificTypes.put(ClientDataType.STRING, List.of( new TimeType(), new MySQLDateType(), new MySQLDateTimeType(), new StringType() )); ``` After adding the ARRAY type in the map it would look like ``` pluginSpecificTypes.put(ClientDataType.NULL, List.of(new NullType())); pluginSpecificTypes.put(ClientDataType.BOOLEAN, List.of(new MySQLBooleanType())); pluginSpecificTypes.put(ClientDataType.NUMBER, List.of( new IntegerType(), new LongType(), new DoubleType(), new BigDecimalType() )); pluginSpecificTypes.put(ClientDataType.OBJECT, List.of(new JsonObjectType())); pluginSpecificTypes.put(ClientDataType.STRING, List.of( new TimeType(), new MySQLDateType(), new MySQLDateTimeType(), new StringType() )); pluginSpecificTypes.put(ClientDataType.ARRAY, List.of(new StringType()); ``` ### Public Sample App _No response_ ### Version Self Hosted <img src="https://front.com/assets/img/favicons/favicon-32x32.png" height="16" width="16" alt="Front logo" /> [Front conversations](https://app.frontapp.com/open/top_5d6rw)
non_test
internal server error when the evaluated value is of type array in mysql is there an existing issue for this i have searched the existing issues description screenshot of error steps to reproduce create a multi select widget create a mysql table with a varchar column say x try to insert the selected values from the multi select into that varchar column x through the following query insert into my table x values multiselect selectedoptionvalues you will notice an internal server error rca let s say the selected options in the multi select widget are so the evaluated value of this binding multiselect selectedoptionvalues becomes for such a value the client side identifies the data type as an array as mysql doesn t have any support for array data type we didn t add any support for the array data type in the mysql plugin when we implemented the change required for datatype handling w r t mysql we expected that the fallback data type i e the stringtype would take over in such scenarios but our assumption went wrong the following code snippet is used to get the appsmithtype from the provided client side data type and the evaluated value public static appsmithtype getappsmithtype clientdatatype clientdatatype string value map pluginspecifictypes for appsmithtype currenttype pluginspecifictypes get clientdatatype if currenttype test value return currenttype ideally we shouldn t reach here but if we do then we will return the fallbacktype return new fallbacktype when clientdatatype is of array the map called pluginspecifictypes provided by the respective plugin in our case which is mysqlplugin doesn t have any key for array thus pluginspecifictypes get clientdatatype returns null and it throws a nullpointerexception from the beginning of the for loop current workaround if the client side identifies the data type as an array then we cannot prevent it to happen the gimmick is to take out the array notation from the evaluated value of that binding and get the values of the multi select widget without having any array notation through a js object it s a two steps method we are going to rewrite the following query insert into my table x values multiselect selectedoptionvalues two step process make the array notation part of your query i e take it out from the evaluated value insert into my table x values concat write the jsobject getvaluesofmultiselect method export default getvaluesofmultiselect var a selectedoptionvalues join return a a null now the evaluated value of jsobject getvaluesofmultiselect would be x y for which the client side data type is string permanent solution the right solution would be either to add a null check on pluginspecifictypes get clientdatatype or add array type in the pluginspecifictypes map more this is the current pluginspecifictypes map of mysqlplugin pluginspecifictypes put clientdatatype null list of new nulltype pluginspecifictypes put clientdatatype boolean list of new mysqlbooleantype pluginspecifictypes put clientdatatype number list of new integertype new longtype new doubletype new bigdecimaltype pluginspecifictypes put clientdatatype object list of new jsonobjecttype pluginspecifictypes put clientdatatype string list of new timetype new mysqldatetype new mysqldatetimetype new stringtype after adding the array type in the map it would look like pluginspecifictypes put clientdatatype null list of new nulltype pluginspecifictypes put clientdatatype boolean list of new mysqlbooleantype pluginspecifictypes put clientdatatype number list of new integertype new longtype new doubletype new bigdecimaltype pluginspecifictypes put clientdatatype object list of new jsonobjecttype pluginspecifictypes put clientdatatype string list of new timetype new mysqldatetype new mysqldatetimetype new stringtype pluginspecifictypes put clientdatatype array list of new stringtype public sample app no response version self hosted
0
306,034
26,430,122,925
IssuesEvent
2023-01-14 18:04:16
gama-platform/gama
https://api.github.com/repos/gama-platform/gama
closed
GamaMap wrongly initialized when given a complex list of pairs
😱 Bug About GAML 👍 Fix to be tested
**Describe the bug** When initializing a map with a simple list of pairs (string keys and int values for example), it is composed as expected. But if it's done with a more complex list especially with unknown keys (let's say a mix of strings and agents) then you get a map strangely composed. For example: ``` write map('int_value'::1, 'tab'::[1, 2, 3]); ``` This code will print `map(['int_value'::1,'tab'::[1,2,3]])` which is correct, but if we add a new pair with an rgb key for example: ``` write map('int_value'::1, 'tab'::[1, 2, 3], rgb(1,2,3)::'some words'); ``` We get this: `map(['int_value'::'int_value'::1::1,'tab'::'tab'::[1,2,3]::[1,2,3],rgb (1, 2, 3, 255)::rgb (1, 2, 3, 255)::'some words'::'some words'])` which is clearly wrong.
1.0
GamaMap wrongly initialized when given a complex list of pairs - **Describe the bug** When initializing a map with a simple list of pairs (string keys and int values for example), it is composed as expected. But if it's done with a more complex list especially with unknown keys (let's say a mix of strings and agents) then you get a map strangely composed. For example: ``` write map('int_value'::1, 'tab'::[1, 2, 3]); ``` This code will print `map(['int_value'::1,'tab'::[1,2,3]])` which is correct, but if we add a new pair with an rgb key for example: ``` write map('int_value'::1, 'tab'::[1, 2, 3], rgb(1,2,3)::'some words'); ``` We get this: `map(['int_value'::'int_value'::1::1,'tab'::'tab'::[1,2,3]::[1,2,3],rgb (1, 2, 3, 255)::rgb (1, 2, 3, 255)::'some words'::'some words'])` which is clearly wrong.
test
gamamap wrongly initialized when given a complex list of pairs describe the bug when initializing a map with a simple list of pairs string keys and int values for example it is composed as expected but if it s done with a more complex list especially with unknown keys let s say a mix of strings and agents then you get a map strangely composed for example write map int value tab this code will print map which is correct but if we add a new pair with an rgb key for example write map int value tab rgb some words we get this map rgb rgb some words some words which is clearly wrong
1
91,945
15,856,779,155
IssuesEvent
2021-04-08 03:09:57
heholek/sheetjs
https://api.github.com/repos/heholek/sheetjs
opened
CVE-2020-24025 (Medium) detected in node-sass-4.14.1.tgz
security vulnerability
## CVE-2020-24025 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-sass-4.14.1.tgz</b></p></summary> <p>Wrapper around libsass</p> <p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz</a></p> <p>Path to dependency file: sheetjs/demos/angular2/package.json</p> <p>Path to vulnerable library: sheetjs/demos/angular2/node_modules/node-sass/package.json</p> <p> Dependency Hierarchy: - cli-1.7.4.tgz (Root Library) - :x: **node-sass-4.14.1.tgz** (Vulnerable Library) </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> Certificate validation in node-sass 2.0.0 to 4.14.1 is disabled when requesting binaries even if the user is not specifying an alternative download path. <p>Publish Date: 2021-01-11 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-24025>CVE-2020-24025</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.3</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: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </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-24025 (Medium) detected in node-sass-4.14.1.tgz - ## CVE-2020-24025 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-sass-4.14.1.tgz</b></p></summary> <p>Wrapper around libsass</p> <p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz</a></p> <p>Path to dependency file: sheetjs/demos/angular2/package.json</p> <p>Path to vulnerable library: sheetjs/demos/angular2/node_modules/node-sass/package.json</p> <p> Dependency Hierarchy: - cli-1.7.4.tgz (Root Library) - :x: **node-sass-4.14.1.tgz** (Vulnerable Library) </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> Certificate validation in node-sass 2.0.0 to 4.14.1 is disabled when requesting binaries even if the user is not specifying an alternative download path. <p>Publish Date: 2021-01-11 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-24025>CVE-2020-24025</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.3</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: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> *** Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
non_test
cve medium detected in node sass tgz cve medium severity vulnerability vulnerable library node sass tgz wrapper around libsass library home page a href path to dependency file sheetjs demos package json path to vulnerable library sheetjs demos node modules node sass package json dependency hierarchy cli tgz root library x node sass tgz vulnerable library vulnerability details certificate validation in node sass to is disabled when requesting binaries even if the user is not specifying an alternative download 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 none integrity impact low availability impact none for more information on scores click a href step up your open source security game with whitesource
0
735
3,062,062,934
IssuesEvent
2015-08-16 06:45:47
zalando/kontrolletti
https://api.github.com/repos/zalando/kontrolletti
closed
Get credentials from S3 bucket
in-progress service-logic
This is not necessary. Toupage provides 2 Environment variables that: ```sh APPLICATION_ID=kontrolletti APPLICATION_VERSION=2 CREDENTIALS_DIR=.... ``` In the credentials folder you wlil find: * `client.json` file * `user.json` file
1.0
Get credentials from S3 bucket - This is not necessary. Toupage provides 2 Environment variables that: ```sh APPLICATION_ID=kontrolletti APPLICATION_VERSION=2 CREDENTIALS_DIR=.... ``` In the credentials folder you wlil find: * `client.json` file * `user.json` file
non_test
get credentials from bucket this is not necessary toupage provides environment variables that sh application id kontrolletti application version credentials dir in the credentials folder you wlil find client json file user json file
0
196,032
14,790,085,985
IssuesEvent
2021-01-12 11:30:20
redwoodjs/redwood
https://api.github.com/repos/redwoodjs/redwood
closed
Provide a way to Mock user authentication in jest tests
kind/improvement topic: auth topic: testing
Allow a user to pass: ```js { auth: { currentUser: {}, isAuthenticated: {}, }} ``` to render in `@redwoodjs/testing` We will provide a default user and the hook will always be authenticated. /cc @RobertBroersma
1.0
Provide a way to Mock user authentication in jest tests - Allow a user to pass: ```js { auth: { currentUser: {}, isAuthenticated: {}, }} ``` to render in `@redwoodjs/testing` We will provide a default user and the hook will always be authenticated. /cc @RobertBroersma
test
provide a way to mock user authentication in jest tests allow a user to pass js auth currentuser isauthenticated to render in redwoodjs testing we will provide a default user and the hook will always be authenticated cc robertbroersma
1
196,999
14,899,455,007
IssuesEvent
2021-01-21 14:22:04
lcy960729/lcy960729.github.io
https://api.github.com/repos/lcy960729/lcy960729.github.io
opened
Spring Boot Controller Test - CY의 개발 블로그
Gitalk Spring Boot Controller Test
https://lcy960729.github.io/wordbook-project/2020/12/13/Spring-Boot-Controller-Test.html 2020-12-13 :: Spring Boot Controller TestSpring Boot에서 컨트롤러 테스트를 위해 여러 방법을 찾아보았다. 그중 하나를 설명하겠다.먼저 테스트 클래스 어노테이션이다 @RunWith(SpringRunner.class) JUnit ...
1.0
Spring Boot Controller Test - CY의 개발 블로그 - https://lcy960729.github.io/wordbook-project/2020/12/13/Spring-Boot-Controller-Test.html 2020-12-13 :: Spring Boot Controller TestSpring Boot에서 컨트롤러 테스트를 위해 여러 방법을 찾아보았다. 그중 하나를 설명하겠다.먼저 테스트 클래스 어노테이션이다 @RunWith(SpringRunner.class) JUnit ...
test
spring boot controller test cy의 개발 블로그 spring boot controller testspring boot에서 컨트롤러 테스트를 위해 여러 방법을 찾아보았다 그중 하나를 설명하겠다 먼저 테스트 클래스 어노테이션이다 runwith springrunner class junit
1
308,419
23,247,562,054
IssuesEvent
2022-08-03 21:59:24
fleetdm/fleet
https://api.github.com/repos/fleetdm/fleet
opened
Make sure Learn how to Use Fleet page is updated for Sandbox
:improve documentation #website
**Fleet version**: **Operating system**: **Web browser**: <hr/> ### 🧑‍💻  Expected behavior The page a user is redirected to in order to learn how to use fleet is updated with current information on how to succeed. ### 💥  Actual behavior The page is potentially out of date and could use a look before Sandbox launches. - As an example, removing or updating copy that mentions fleetctl preview. ### More info https://fleetdm.com/docs/using-fleet/learn-how-to-use-fleet Ticket generated from the UI/UX weekly call.
1.0
Make sure Learn how to Use Fleet page is updated for Sandbox - **Fleet version**: **Operating system**: **Web browser**: <hr/> ### 🧑‍💻  Expected behavior The page a user is redirected to in order to learn how to use fleet is updated with current information on how to succeed. ### 💥  Actual behavior The page is potentially out of date and could use a look before Sandbox launches. - As an example, removing or updating copy that mentions fleetctl preview. ### More info https://fleetdm.com/docs/using-fleet/learn-how-to-use-fleet Ticket generated from the UI/UX weekly call.
non_test
make sure learn how to use fleet page is updated for sandbox fleet version operating system web browser 🧑‍💻  expected behavior the page a user is redirected to in order to learn how to use fleet is updated with current information on how to succeed 💥  actual behavior the page is potentially out of date and could use a look before sandbox launches as an example removing or updating copy that mentions fleetctl preview more info ticket generated from the ui ux weekly call
0
783,656
27,540,104,630
IssuesEvent
2023-03-07 07:56:11
AY2223S2-CS2103T-W12-1/tp
https://api.github.com/repos/AY2223S2-CS2103T-W12-1/tp
closed
Display Volunteers and Elderly in the UI
type.Task priority.High
## Current Behaviour - Volunteers and Elderly are not being shown on the UI ## Desired Outcome - 3 boxes, showing the Volunteers, Elderly, and Pairs respectively - The find command should "filter" all 3 boxes
1.0
Display Volunteers and Elderly in the UI - ## Current Behaviour - Volunteers and Elderly are not being shown on the UI ## Desired Outcome - 3 boxes, showing the Volunteers, Elderly, and Pairs respectively - The find command should "filter" all 3 boxes
non_test
display volunteers and elderly in the ui current behaviour volunteers and elderly are not being shown on the ui desired outcome boxes showing the volunteers elderly and pairs respectively the find command should filter all boxes
0
203,636
15,377,853,884
IssuesEvent
2021-03-02 17:34:49
devosoft/Empirical
https://api.github.com/repos/devosoft/Empirical
closed
Measure test coverage of the source/web directory
Goal: Enhancement Topic: Testing
#183 will add test coverage metrics to all the parts of Empirical that can be compiled natively. The source/web directory is another kettle of fish and is currently being completely ignored by the test coverage. Measuring test coverage on it will require the development of substantial additional infrastructure, as we will need to link execution of Javascript lines back to the original C++ code that generated them. We should investigate whether anyone else has already addressed this problem, but I suspect no one has. A few thoughts: - Once we have everything in web set up to not throw errors when you compile it naively, we'll be able to at least stop excluding it from our other tests. This will enforce that it continues to be able to compile. - It's possible this won't be as bad as I think. If we can find an easy way to make connections between Javascript lines and C++ lines (which might already be lurking somewhere in Emscripten?), we can use existing Javascript coverage metrics (for which there are many good options) and then write a simple Python script to propagate them back to the C++ code.
1.0
Measure test coverage of the source/web directory - #183 will add test coverage metrics to all the parts of Empirical that can be compiled natively. The source/web directory is another kettle of fish and is currently being completely ignored by the test coverage. Measuring test coverage on it will require the development of substantial additional infrastructure, as we will need to link execution of Javascript lines back to the original C++ code that generated them. We should investigate whether anyone else has already addressed this problem, but I suspect no one has. A few thoughts: - Once we have everything in web set up to not throw errors when you compile it naively, we'll be able to at least stop excluding it from our other tests. This will enforce that it continues to be able to compile. - It's possible this won't be as bad as I think. If we can find an easy way to make connections between Javascript lines and C++ lines (which might already be lurking somewhere in Emscripten?), we can use existing Javascript coverage metrics (for which there are many good options) and then write a simple Python script to propagate them back to the C++ code.
test
measure test coverage of the source web directory will add test coverage metrics to all the parts of empirical that can be compiled natively the source web directory is another kettle of fish and is currently being completely ignored by the test coverage measuring test coverage on it will require the development of substantial additional infrastructure as we will need to link execution of javascript lines back to the original c code that generated them we should investigate whether anyone else has already addressed this problem but i suspect no one has a few thoughts once we have everything in web set up to not throw errors when you compile it naively we ll be able to at least stop excluding it from our other tests this will enforce that it continues to be able to compile it s possible this won t be as bad as i think if we can find an easy way to make connections between javascript lines and c lines which might already be lurking somewhere in emscripten we can use existing javascript coverage metrics for which there are many good options and then write a simple python script to propagate them back to the c code
1
63,623
6,876,788,145
IssuesEvent
2017-11-20 03:28:37
xcat2/xcat-core
https://api.github.com/repos/xcat2/xcat-core
closed
[fvt] update automation production environment to support performance test
component:test priority:high sprint1 type:feature
what to do: * [x] update all related new scripts to automation production environment * [x] setup performance test in automation production environment: generate a project to run performance test and put log into special directory. * [x] exclude the performance test result from the daily report
1.0
[fvt] update automation production environment to support performance test - what to do: * [x] update all related new scripts to automation production environment * [x] setup performance test in automation production environment: generate a project to run performance test and put log into special directory. * [x] exclude the performance test result from the daily report
test
update automation production environment to support performance test what to do update all related new scripts to automation production environment setup performance test in automation production environment generate a project to run performance test and put log into special directory exclude the performance test result from the daily report
1
542,086
15,838,546,495
IssuesEvent
2021-04-06 22:42:53
cytrus-re/cytrus-re
https://api.github.com/repos/cytrus-re/cytrus-re
opened
Add a Nightly/Beta branch
feature priority-2
This should allow more modifications without having regressions on latest Cytrus-RE; Consider adding a Nightly Branch for PRs for example.
1.0
Add a Nightly/Beta branch - This should allow more modifications without having regressions on latest Cytrus-RE; Consider adding a Nightly Branch for PRs for example.
non_test
add a nightly beta branch this should allow more modifications without having regressions on latest cytrus re consider adding a nightly branch for prs for example
0
170,252
13,180,826,581
IssuesEvent
2020-08-12 13:25:46
hazelcast/hazelcast
https://api.github.com/repos/hazelcast/hazelcast
closed
QueryCacheBasicTest failures
Source: Internal Team: Core Type: Test-Failure
- Fails on `Hazelcast-4.master-Windows-OracleJDK8` - Fails on [Build #164 (May 19, 2020 2:46:05 PM)](http://jenkins.hazelcast.com/view/Official%20Builds/job/Hazelcast-4.master-Windows-OracleJDK8/164/) - Failing cases ``` com.hazelcast.map.impl.querycache.QueryCacheBasicTest.entryRemoved_whenValueMatchesPredicate[includeValues: true, useQueryCacheFilteringStrategy: false, nearCache: true] com.hazelcast.map.impl.querycache.QueryCacheBasicTest.entryRemoved_whenValueMatchesPredicate[includeValues: true, useQueryCacheFilteringStrategy: false, nearCache: true] ``` - Sample Error ``` sequence ``` - Stacktrace ``` java.lang.IllegalArgumentException: sequence at com.hazelcast.internal.util.Preconditions.checkPositive(Preconditions.java:168) at com.hazelcast.map.impl.querycache.accumulator.DefaultCyclicBuffer.get(DefaultCyclicBuffer.java:88) at com.hazelcast.map.impl.querycache.accumulator.BasicAccumulator.readCurrentExpiredOrNull(BasicAccumulator.java:151) at com.hazelcast.map.impl.querycache.accumulator.BasicAccumulator.poll(BasicAccumulator.java:94) at com.hazelcast.map.impl.querycache.publisher.AccumulatorSweeper.flushAllAccumulators(AccumulatorSweeper.java:61) at com.hazelcast.map.impl.querycache.publisher.DefaultPublisherContext.flush(DefaultPublisherContext.java:125) at com.hazelcast.map.impl.querycache.NodeQueryCacheContext.lambda$flushPublishersOnNodeShutdown$0(NodeQueryCacheContext.java:91) at com.hazelcast.instance.impl.LifecycleServiceImpl.fireLifecycleEvent(LifecycleServiceImpl.java:72) at com.hazelcast.instance.impl.LifecycleServiceImpl.fireLifecycleEvent(LifecycleServiceImpl.java:66) at com.hazelcast.instance.impl.LifecycleServiceImpl.shutdown(LifecycleServiceImpl.java:94) at com.hazelcast.instance.impl.LifecycleServiceImpl.terminate(LifecycleServiceImpl.java:89) at com.hazelcast.test.mocknetwork.TestNodeRegistry.shutdown(TestNodeRegistry.java:123) at com.hazelcast.test.mocknetwork.TestNodeRegistry.terminate(TestNodeRegistry.java:113) at com.hazelcast.test.TestHazelcastInstanceFactory.terminateAll(TestHazelcastInstanceFactory.java:331) at com.hazelcast.test.HazelcastTestSupport.shutdownNodeFactory(HazelcastTestSupport.java:179) at sun.reflect.GeneratedMethodAccessor105.invoke(Unknown Source) 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:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at com.hazelcast.test.AbstractHazelcastClassRunner$ThreadDumpAwareRunAfters.evaluate(AbstractHazelcastClassRunner.java:404) at com.hazelcast.test.DumpBuildInfoOnFailureRule$1.evaluate(DumpBuildInfoOnFailureRule.java:37) at com.hazelcast.test.jitter.JitterRule$1.evaluate(JitterRule.java:104) at com.hazelcast.test.metrics.MetricsRule$1.evaluate(MetricsRule.java:62) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at com.hazelcast.test.HazelcastParallelClassRunner.access$301(HazelcastParallelClassRunner.java:49) at com.hazelcast.test.HazelcastParallelClassRunner$TestRunner.run(HazelcastParallelClassRunner.java:162) at java.lang.Thread.run(Thread.java:748) ``` kindly check
1.0
QueryCacheBasicTest failures - - Fails on `Hazelcast-4.master-Windows-OracleJDK8` - Fails on [Build #164 (May 19, 2020 2:46:05 PM)](http://jenkins.hazelcast.com/view/Official%20Builds/job/Hazelcast-4.master-Windows-OracleJDK8/164/) - Failing cases ``` com.hazelcast.map.impl.querycache.QueryCacheBasicTest.entryRemoved_whenValueMatchesPredicate[includeValues: true, useQueryCacheFilteringStrategy: false, nearCache: true] com.hazelcast.map.impl.querycache.QueryCacheBasicTest.entryRemoved_whenValueMatchesPredicate[includeValues: true, useQueryCacheFilteringStrategy: false, nearCache: true] ``` - Sample Error ``` sequence ``` - Stacktrace ``` java.lang.IllegalArgumentException: sequence at com.hazelcast.internal.util.Preconditions.checkPositive(Preconditions.java:168) at com.hazelcast.map.impl.querycache.accumulator.DefaultCyclicBuffer.get(DefaultCyclicBuffer.java:88) at com.hazelcast.map.impl.querycache.accumulator.BasicAccumulator.readCurrentExpiredOrNull(BasicAccumulator.java:151) at com.hazelcast.map.impl.querycache.accumulator.BasicAccumulator.poll(BasicAccumulator.java:94) at com.hazelcast.map.impl.querycache.publisher.AccumulatorSweeper.flushAllAccumulators(AccumulatorSweeper.java:61) at com.hazelcast.map.impl.querycache.publisher.DefaultPublisherContext.flush(DefaultPublisherContext.java:125) at com.hazelcast.map.impl.querycache.NodeQueryCacheContext.lambda$flushPublishersOnNodeShutdown$0(NodeQueryCacheContext.java:91) at com.hazelcast.instance.impl.LifecycleServiceImpl.fireLifecycleEvent(LifecycleServiceImpl.java:72) at com.hazelcast.instance.impl.LifecycleServiceImpl.fireLifecycleEvent(LifecycleServiceImpl.java:66) at com.hazelcast.instance.impl.LifecycleServiceImpl.shutdown(LifecycleServiceImpl.java:94) at com.hazelcast.instance.impl.LifecycleServiceImpl.terminate(LifecycleServiceImpl.java:89) at com.hazelcast.test.mocknetwork.TestNodeRegistry.shutdown(TestNodeRegistry.java:123) at com.hazelcast.test.mocknetwork.TestNodeRegistry.terminate(TestNodeRegistry.java:113) at com.hazelcast.test.TestHazelcastInstanceFactory.terminateAll(TestHazelcastInstanceFactory.java:331) at com.hazelcast.test.HazelcastTestSupport.shutdownNodeFactory(HazelcastTestSupport.java:179) at sun.reflect.GeneratedMethodAccessor105.invoke(Unknown Source) 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:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at com.hazelcast.test.AbstractHazelcastClassRunner$ThreadDumpAwareRunAfters.evaluate(AbstractHazelcastClassRunner.java:404) at com.hazelcast.test.DumpBuildInfoOnFailureRule$1.evaluate(DumpBuildInfoOnFailureRule.java:37) at com.hazelcast.test.jitter.JitterRule$1.evaluate(JitterRule.java:104) at com.hazelcast.test.metrics.MetricsRule$1.evaluate(MetricsRule.java:62) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at com.hazelcast.test.HazelcastParallelClassRunner.access$301(HazelcastParallelClassRunner.java:49) at com.hazelcast.test.HazelcastParallelClassRunner$TestRunner.run(HazelcastParallelClassRunner.java:162) at java.lang.Thread.run(Thread.java:748) ``` kindly check
test
querycachebasictest failures fails on hazelcast master windows fails on failing cases com hazelcast map impl querycache querycachebasictest entryremoved whenvaluematchespredicate com hazelcast map impl querycache querycachebasictest entryremoved whenvaluematchespredicate sample error sequence stacktrace java lang illegalargumentexception sequence at com hazelcast internal util preconditions checkpositive preconditions java at com hazelcast map impl querycache accumulator defaultcyclicbuffer get defaultcyclicbuffer java at com hazelcast map impl querycache accumulator basicaccumulator readcurrentexpiredornull basicaccumulator java at com hazelcast map impl querycache accumulator basicaccumulator poll basicaccumulator java at com hazelcast map impl querycache publisher accumulatorsweeper flushallaccumulators accumulatorsweeper java at com hazelcast map impl querycache publisher defaultpublishercontext flush defaultpublishercontext java at com hazelcast map impl querycache nodequerycachecontext lambda flushpublishersonnodeshutdown nodequerycachecontext java at com hazelcast instance impl lifecycleserviceimpl firelifecycleevent lifecycleserviceimpl java at com hazelcast instance impl lifecycleserviceimpl firelifecycleevent lifecycleserviceimpl java at com hazelcast instance impl lifecycleserviceimpl shutdown lifecycleserviceimpl java at com hazelcast instance impl lifecycleserviceimpl terminate lifecycleserviceimpl java at com hazelcast test mocknetwork testnoderegistry shutdown testnoderegistry java at com hazelcast test mocknetwork testnoderegistry terminate testnoderegistry java at com hazelcast test testhazelcastinstancefactory terminateall testhazelcastinstancefactory java at com hazelcast test hazelcasttestsupport shutdownnodefactory hazelcasttestsupport java at sun reflect invoke unknown source 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 com hazelcast test abstracthazelcastclassrunner threaddumpawarerunafters evaluate abstracthazelcastclassrunner java at com hazelcast test dumpbuildinfoonfailurerule evaluate dumpbuildinfoonfailurerule java at com hazelcast test jitter jitterrule evaluate jitterrule java at com hazelcast test metrics metricsrule evaluate metricsrule java at org junit rules runrules evaluate runrules java at org junit runners parentrunner runleaf parentrunner java at org junit runners runchild java at com hazelcast test hazelcastparallelclassrunner access hazelcastparallelclassrunner java at com hazelcast test hazelcastparallelclassrunner testrunner run hazelcastparallelclassrunner java at java lang thread run thread java kindly check
1
197,478
15,681,482,317
IssuesEvent
2021-03-25 05:27:36
microsoft/Windows-Containers
https://api.github.com/repos/microsoft/Windows-Containers
closed
Fix disconnect between Microsoft and Mirantis about the right way to install Docker on Windows Server
documentation
While the Microsoft documentation ([Prep Windows operating system containers | Microsoft Docs](https://docs.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=Windows-Server)) indicates that a OneGet PowerShell provider is the right way to install Docker on Windows Server, the Mirantis documentation ([Mirantis Documentation: Install Mirantis Container Runtime on Windows Servers](https://docs.mirantis.com/docker-enterprise/v3.1/dockeree-products/mcr/mcr-windows.html)) references their own scripts. When I tested this the last time, the OneGet provider gave me Docker EE 19.03.14 and the Mirantis Script did the same, but also installed containerd 1.3.9. The [previous iteration of the Mirantis documentation](https://docs.mirantis.com/docker-enterprise/v3.0/dockeree-products/mcr/windows.html) had the same description as in the current Microsoft documentation, so this seems to be a conscious change. What is the right way to install Docker on Windows Server?
1.0
Fix disconnect between Microsoft and Mirantis about the right way to install Docker on Windows Server - While the Microsoft documentation ([Prep Windows operating system containers | Microsoft Docs](https://docs.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=Windows-Server)) indicates that a OneGet PowerShell provider is the right way to install Docker on Windows Server, the Mirantis documentation ([Mirantis Documentation: Install Mirantis Container Runtime on Windows Servers](https://docs.mirantis.com/docker-enterprise/v3.1/dockeree-products/mcr/mcr-windows.html)) references their own scripts. When I tested this the last time, the OneGet provider gave me Docker EE 19.03.14 and the Mirantis Script did the same, but also installed containerd 1.3.9. The [previous iteration of the Mirantis documentation](https://docs.mirantis.com/docker-enterprise/v3.0/dockeree-products/mcr/windows.html) had the same description as in the current Microsoft documentation, so this seems to be a conscious change. What is the right way to install Docker on Windows Server?
non_test
fix disconnect between microsoft and mirantis about the right way to install docker on windows server while the microsoft documentation indicates that a oneget powershell provider is the right way to install docker on windows server the mirantis documentation references their own scripts when i tested this the last time the oneget provider gave me docker ee and the mirantis script did the same but also installed containerd the had the same description as in the current microsoft documentation so this seems to be a conscious change what is the right way to install docker on windows server
0
224,965
17,786,587,466
IssuesEvent
2021-08-31 11:50:55
trinodb/trino
https://api.github.com/repos/trinodb/trino
closed
Flaky io.trino.plugin.memory.TestMemoryConnectorTest.testCreateAndDropTable
test
``` 2021-08-30T16:11:41.0365211Z [ERROR] testCreateAndDropTable(io.trino.plugin.memory.TestMemoryConnectorTest) Time elapsed: 0.007 s <<< FAILURE! 2021-08-30T16:11:41.0370318Z java.lang.AssertionError: expected [7] but found [8] 2021-08-30T16:11:41.0374137Z at org.testng.Assert.fail(Assert.java:94) 2021-08-30T16:11:41.0399162Z at org.testng.Assert.failNotEquals(Assert.java:513) 2021-08-30T16:11:41.0404045Z at org.testng.Assert.assertEqualsImpl(Assert.java:135) 2021-08-30T16:11:41.0408727Z at org.testng.Assert.assertEquals(Assert.java:116) 2021-08-30T16:11:41.0413206Z at org.testng.Assert.assertEquals(Assert.java:389) 2021-08-30T16:11:41.0417648Z at org.testng.Assert.assertEquals(Assert.java:399) 2021-08-30T16:11:41.0426071Z at io.trino.plugin.memory.TestMemoryConnectorTest.testCreateAndDropTable(TestMemoryConnectorTest.java:125) 2021-08-30T16:11:41.0433699Z at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 2021-08-30T16:11:41.0441950Z at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 2021-08-30T16:11:41.0451108Z at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 2021-08-30T16:11:41.0457123Z at java.base/java.lang.reflect.Method.invoke(Method.java:566) 2021-08-30T16:11:41.0528685Z at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:104) 2021-08-30T16:11:41.0534737Z at org.testng.internal.Invoker.invokeMethod(Invoker.java:645) 2021-08-30T16:11:41.0540527Z at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:851) 2021-08-30T16:11:41.0546447Z at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1177) 2021-08-30T16:11:41.0553561Z at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129) 2021-08-30T16:11:41.0559901Z at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112) 2021-08-30T16:11:41.0567549Z at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) 2021-08-30T16:11:41.0626071Z at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) 2021-08-30T16:11:41.0628481Z at java.base/java.lang.Thread.run(Thread.java:829) ``` https://github.com/trinodb/trino/runs/3463395818?check_suite_focus=true
1.0
Flaky io.trino.plugin.memory.TestMemoryConnectorTest.testCreateAndDropTable - ``` 2021-08-30T16:11:41.0365211Z [ERROR] testCreateAndDropTable(io.trino.plugin.memory.TestMemoryConnectorTest) Time elapsed: 0.007 s <<< FAILURE! 2021-08-30T16:11:41.0370318Z java.lang.AssertionError: expected [7] but found [8] 2021-08-30T16:11:41.0374137Z at org.testng.Assert.fail(Assert.java:94) 2021-08-30T16:11:41.0399162Z at org.testng.Assert.failNotEquals(Assert.java:513) 2021-08-30T16:11:41.0404045Z at org.testng.Assert.assertEqualsImpl(Assert.java:135) 2021-08-30T16:11:41.0408727Z at org.testng.Assert.assertEquals(Assert.java:116) 2021-08-30T16:11:41.0413206Z at org.testng.Assert.assertEquals(Assert.java:389) 2021-08-30T16:11:41.0417648Z at org.testng.Assert.assertEquals(Assert.java:399) 2021-08-30T16:11:41.0426071Z at io.trino.plugin.memory.TestMemoryConnectorTest.testCreateAndDropTable(TestMemoryConnectorTest.java:125) 2021-08-30T16:11:41.0433699Z at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 2021-08-30T16:11:41.0441950Z at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 2021-08-30T16:11:41.0451108Z at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 2021-08-30T16:11:41.0457123Z at java.base/java.lang.reflect.Method.invoke(Method.java:566) 2021-08-30T16:11:41.0528685Z at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:104) 2021-08-30T16:11:41.0534737Z at org.testng.internal.Invoker.invokeMethod(Invoker.java:645) 2021-08-30T16:11:41.0540527Z at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:851) 2021-08-30T16:11:41.0546447Z at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1177) 2021-08-30T16:11:41.0553561Z at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129) 2021-08-30T16:11:41.0559901Z at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112) 2021-08-30T16:11:41.0567549Z at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) 2021-08-30T16:11:41.0626071Z at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) 2021-08-30T16:11:41.0628481Z at java.base/java.lang.Thread.run(Thread.java:829) ``` https://github.com/trinodb/trino/runs/3463395818?check_suite_focus=true
test
flaky io trino plugin memory testmemoryconnectortest testcreateanddroptable testcreateanddroptable io trino plugin memory testmemoryconnectortest time elapsed s failure java lang assertionerror expected but found at org testng assert fail assert java at org testng assert failnotequals assert java at org testng assert assertequalsimpl assert java at org testng assert assertequals assert java at org testng assert assertequals assert java at org testng assert assertequals assert java at io trino plugin memory testmemoryconnectortest testcreateanddroptable testmemoryconnectortest java at java base jdk internal reflect nativemethodaccessorimpl native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java base java lang reflect method invoke method java at org testng internal methodinvocationhelper invokemethod methodinvocationhelper java at org testng internal invoker invokemethod invoker java at org testng internal invoker invoketestmethod invoker java at org testng internal invoker invoketestmethods invoker java at org testng internal testmethodworker invoketestmethods testmethodworker java at org testng internal testmethodworker run testmethodworker java at java base java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java base java util concurrent threadpoolexecutor worker run threadpoolexecutor java at java base java lang thread run thread java
1
463,215
13,261,789,249
IssuesEvent
2020-08-20 20:32:11
modulz/stitches
https://api.github.com/repos/modulz/stitches
closed
Nest media queries
feature priority: 2
One thing to keep in mind, once we implement inline media queries (#67) is to have the ability to nest them. ```css @media (min-width: 400px) { @media (hover: hover) { // Colm's cool hover effect in dark mode } } ``` This should also work with predefined media (`screens`): ``` { medium: { hoverSupport: { // Colm's cool hover effect in dark mode } } } ``` Im setting this as a P2 because it's something that is currently achievable. With inline media queries you can rely on a single media query with the `and` operator. With the screens token, you can do the same 😄
1.0
Nest media queries - One thing to keep in mind, once we implement inline media queries (#67) is to have the ability to nest them. ```css @media (min-width: 400px) { @media (hover: hover) { // Colm's cool hover effect in dark mode } } ``` This should also work with predefined media (`screens`): ``` { medium: { hoverSupport: { // Colm's cool hover effect in dark mode } } } ``` Im setting this as a P2 because it's something that is currently achievable. With inline media queries you can rely on a single media query with the `and` operator. With the screens token, you can do the same 😄
non_test
nest media queries one thing to keep in mind once we implement inline media queries is to have the ability to nest them css media min width media hover hover colm s cool hover effect in dark mode this should also work with predefined media screens medium hoversupport colm s cool hover effect in dark mode im setting this as a because it s something that is currently achievable with inline media queries you can rely on a single media query with the and operator with the screens token you can do the same 😄
0
66,541
12,799,752,812
IssuesEvent
2020-07-02 15:53:19
Scholar-6/brillder
https://api.github.com/repos/Scholar-6/brillder
closed
Rename isPreview to isPhonePreview
Code TODO
https://github.com/Scholar-6/brillder/blob/development/src/components/play/brick/questionTypes/shortAnswer/ShortAnswer.tsx#L17 isPreview is used to display the answer when the component is in the phone preview on the investigation page. However there is also a /build/preview so this boolean is confusing. Just rename it and this will help anyone reviewing the code.
1.0
Rename isPreview to isPhonePreview - https://github.com/Scholar-6/brillder/blob/development/src/components/play/brick/questionTypes/shortAnswer/ShortAnswer.tsx#L17 isPreview is used to display the answer when the component is in the phone preview on the investigation page. However there is also a /build/preview so this boolean is confusing. Just rename it and this will help anyone reviewing the code.
non_test
rename ispreview to isphonepreview ispreview is used to display the answer when the component is in the phone preview on the investigation page however there is also a build preview so this boolean is confusing just rename it and this will help anyone reviewing the code
0
148,810
13,248,081,257
IssuesEvent
2020-08-19 18:20:40
zillow/luminaire
https://api.github.com/repos/zillow/luminaire
closed
Add documentation link to the "About" section of this repo
documentation
This is the one consistent location people usually find links to docs; we should link to it there as well.
1.0
Add documentation link to the "About" section of this repo - This is the one consistent location people usually find links to docs; we should link to it there as well.
non_test
add documentation link to the about section of this repo this is the one consistent location people usually find links to docs we should link to it there as well
0
41,176
5,313,585,971
IssuesEvent
2017-02-13 12:41:26
okfn/opendataday
https://api.github.com/repos/okfn/opendataday
closed
Create a new logo to Open Data Day
design enhancement
Current logo has the word Hackathon in it - ![image](https://cloud.githubusercontent.com/assets/3273659/20110199/503269e6-a5db-11e6-8544-2819f9046f57.png) OK Japan created this logo generator in the past - http://logo.odd.okfn.jp/ It will be nice to have the new logo for the International Open Data Day in the same spirit.
1.0
Create a new logo to Open Data Day - Current logo has the word Hackathon in it - ![image](https://cloud.githubusercontent.com/assets/3273659/20110199/503269e6-a5db-11e6-8544-2819f9046f57.png) OK Japan created this logo generator in the past - http://logo.odd.okfn.jp/ It will be nice to have the new logo for the International Open Data Day in the same spirit.
non_test
create a new logo to open data day current logo has the word hackathon in it ok japan created this logo generator in the past it will be nice to have the new logo for the international open data day in the same spirit
0
14,186
3,385,532,669
IssuesEvent
2015-11-27 12:06:31
e-government-ua/i
https://api.github.com/repos/e-government-ua/i
closed
На главном портале, при включенных "дополнительных админ-возможностях", отрабатывать дополнительные кнопки управления - описанием и сопровождением услуги (войдя в услугу, переключаясь между таб-ами)
active hi priority test _central-js
После реализации задачи: https://github.com/e-government-ua/i/issues/242 (оживив кнопки) 1) Кнопка "изменить содержание" и после ее нажатие переход в режим редактирования содержимого в HTML-редакторе, и возможностью сохранить изменения кнопкой "Сохранить" или отменить, кнопкой "Отмена" Сервис "setService" @Kiaba Бібліотека для вирішення задачі: http://textangular.com/
1.0
На главном портале, при включенных "дополнительных админ-возможностях", отрабатывать дополнительные кнопки управления - описанием и сопровождением услуги (войдя в услугу, переключаясь между таб-ами) - После реализации задачи: https://github.com/e-government-ua/i/issues/242 (оживив кнопки) 1) Кнопка "изменить содержание" и после ее нажатие переход в режим редактирования содержимого в HTML-редакторе, и возможностью сохранить изменения кнопкой "Сохранить" или отменить, кнопкой "Отмена" Сервис "setService" @Kiaba Бібліотека для вирішення задачі: http://textangular.com/
test
на главном портале при включенных дополнительных админ возможностях отрабатывать дополнительные кнопки управления описанием и сопровождением услуги войдя в услугу переключаясь между таб ами после реализации задачи оживив кнопки кнопка изменить содержание и после ее нажатие переход в режим редактирования содержимого в html редакторе и возможностью сохранить изменения кнопкой сохранить или отменить кнопкой отмена сервис setservice kiaba бібліотека для вирішення задачі
1
108,844
9,333,980,740
IssuesEvent
2019-03-28 15:25:56
cockroachdb/cockroach
https://api.github.com/repos/cockroachdb/cockroach
closed
teamcity: failed test: TestExecBuild
C-test-failure O-robot
The following tests appear to have failed on master (test): TestExecBuild/fakedist-opt: TestExecBuild/fakedist-opt/stats, TestExecBuild/fakedist-opt, TestExecBuild You may want to check [for open issues](https://github.com/cockroachdb/cockroach/issues?q=is%3Aissue+is%3Aopen+TestExecBuild). [#1203437](https://teamcity.cockroachdb.com/viewLog.html?buildId=1203437): ``` TestExecBuild/fakedist-opt: TestExecBuild/fakedist-opt/stats --- FAIL: test/TestExecBuild: TestExecBuild/fakedist-opt: TestExecBuild/fakedist-opt/stats (1.030s) ------- Stdout: ------- === PAUSE TestExecBuild/fakedist-opt/stats logic.go:2351: testdata/stats:23: EXPLAIN (VERBOSE) SELECT * FROM b WHERE u = 1 AND v = 1 expected: scan · · (u, v) · · table b@b_v_idx · · · spans /1-/2 · · · filter u = 1 · · but found (query options: "") : scan · · (u, v) · · table b@b_u_idx · · · spans /1-/2 · · · filter v = 1 · · logic.go:2383: testdata/stats:31: error while processing logic.go:2384: testdata/stats:31: too many errors encountered, skipping the rest of the input TestExecBuild --- FAIL: test/TestExecBuild (21.220s) ------- Stdout: ------- test_log_scope.go:81: test logs captured to: /tmp/logTestExecBuild902295129 test_log_scope.go:62: use -show-logs to present logs inline TestExecBuild/fakedist-opt --- FAIL: test/TestExecBuild: TestExecBuild/fakedist-opt (0.000s) ``` Please assign, take a look and update the issue accordingly.
1.0
teamcity: failed test: TestExecBuild - The following tests appear to have failed on master (test): TestExecBuild/fakedist-opt: TestExecBuild/fakedist-opt/stats, TestExecBuild/fakedist-opt, TestExecBuild You may want to check [for open issues](https://github.com/cockroachdb/cockroach/issues?q=is%3Aissue+is%3Aopen+TestExecBuild). [#1203437](https://teamcity.cockroachdb.com/viewLog.html?buildId=1203437): ``` TestExecBuild/fakedist-opt: TestExecBuild/fakedist-opt/stats --- FAIL: test/TestExecBuild: TestExecBuild/fakedist-opt: TestExecBuild/fakedist-opt/stats (1.030s) ------- Stdout: ------- === PAUSE TestExecBuild/fakedist-opt/stats logic.go:2351: testdata/stats:23: EXPLAIN (VERBOSE) SELECT * FROM b WHERE u = 1 AND v = 1 expected: scan · · (u, v) · · table b@b_v_idx · · · spans /1-/2 · · · filter u = 1 · · but found (query options: "") : scan · · (u, v) · · table b@b_u_idx · · · spans /1-/2 · · · filter v = 1 · · logic.go:2383: testdata/stats:31: error while processing logic.go:2384: testdata/stats:31: too many errors encountered, skipping the rest of the input TestExecBuild --- FAIL: test/TestExecBuild (21.220s) ------- Stdout: ------- test_log_scope.go:81: test logs captured to: /tmp/logTestExecBuild902295129 test_log_scope.go:62: use -show-logs to present logs inline TestExecBuild/fakedist-opt --- FAIL: test/TestExecBuild: TestExecBuild/fakedist-opt (0.000s) ``` Please assign, take a look and update the issue accordingly.
test
teamcity failed test testexecbuild the following tests appear to have failed on master test testexecbuild fakedist opt testexecbuild fakedist opt stats testexecbuild fakedist opt testexecbuild you may want to check testexecbuild fakedist opt testexecbuild fakedist opt stats fail test testexecbuild testexecbuild fakedist opt testexecbuild fakedist opt stats stdout pause testexecbuild fakedist opt stats logic go testdata stats explain verbose select from b where u and v expected scan · · u v · · table b b v idx · · · spans · · · filter u · · but found query options scan · · u v · · table b b u idx · · · spans · · · filter v · · logic go testdata stats error while processing logic go testdata stats too many errors encountered skipping the rest of the input testexecbuild fail test testexecbuild stdout test log scope go test logs captured to tmp test log scope go use show logs to present logs inline testexecbuild fakedist opt fail test testexecbuild testexecbuild fakedist opt please assign take a look and update the issue accordingly
1
5,861
3,293,850,847
IssuesEvent
2015-10-30 21:01:57
phetsims/bending-light
https://api.github.com/repos/phetsims/bending-light
closed
Incorrect type union in JSDoc
code-review
In a couple of places in the sim, I notice that params documented in the JSDoc with multiple types look like this: ```js @param {Polygon/Circle/SemiCircle} shape ``` I think the correct style for type union in JSDoc should be ```js @param {Polygon|Circle|SemiCircle} shape ``` using the | character. I could not find an example of this in the PhET developer overview, but that style is suggested here: http://usejsdoc.org/tags-type.html
1.0
Incorrect type union in JSDoc - In a couple of places in the sim, I notice that params documented in the JSDoc with multiple types look like this: ```js @param {Polygon/Circle/SemiCircle} shape ``` I think the correct style for type union in JSDoc should be ```js @param {Polygon|Circle|SemiCircle} shape ``` using the | character. I could not find an example of this in the PhET developer overview, but that style is suggested here: http://usejsdoc.org/tags-type.html
non_test
incorrect type union in jsdoc in a couple of places in the sim i notice that params documented in the jsdoc with multiple types look like this js param polygon circle semicircle shape i think the correct style for type union in jsdoc should be js param polygon circle semicircle shape using the character i could not find an example of this in the phet developer overview but that style is suggested here
0
19,794
10,423,204,328
IssuesEvent
2019-09-16 10:50:14
jesopo/bitbot
https://api.github.com/repos/jesopo/bitbot
opened
Restrict github/gitea webhook API keys to a specific organisation
enhancement security
anyone can send a webhook payload to bitbot if they have a valid API key and they can lie about the repository, which can cause bitbot to spam other channels that have hooks for other orgs/repos
True
Restrict github/gitea webhook API keys to a specific organisation - anyone can send a webhook payload to bitbot if they have a valid API key and they can lie about the repository, which can cause bitbot to spam other channels that have hooks for other orgs/repos
non_test
restrict github gitea webhook api keys to a specific organisation anyone can send a webhook payload to bitbot if they have a valid api key and they can lie about the repository which can cause bitbot to spam other channels that have hooks for other orgs repos
0
131,918
10,722,339,840
IssuesEvent
2019-10-27 11:15:58
kodiondemand/addon
https://api.github.com/repos/kodiondemand/addon
closed
animeleggendari.py
Test Canale
Documento Template per il Test del canale Specifica, dove possibile, il tipo di problema che incontri, anche se non è presente alcuna voce per indicarlo. Se hai **suggerimenti/consigli/dubbi sul test**...Proponili e/o Chiedi! Scrivendo un commento a questo stesso issue, che trovi in fondo, dopo questa pagina. **Avvertenze:** Per il test dei canali **DEVI**: - utilizzare la versione **[BETA](https://kodiondemand.github.io/repo/KoD-installer-BETA.zip)** di KOD! - **ABILITARE IL DEBUG PER I LOG** **Per eseguire il test, ricordati di titolarlo con il nome del canale da te scelto, e salvare la pagina cliccando sul bottone verde in basso "SUBMIT NEW ISSUE"** **Ogni volta che hai un ERRORE con avviso di LOG. Puoi scegliere se: ALLEGARE IMMEDIATAMENTE il file kodi.log nel punto, della pagina, in cui sei nel test Allegare il file kodi.log a fine pagina.** **Per poter scrivere o allegare file nella pagina devi:** - cliccare sui [ ... ] in alto a destra della scheda - Edit. Da questo momento puoi scrivere e/o inviare file. Dopodiché clicca sul bottone verde "Update comment" per continuare il test nel modo consueto o per terminarlo! Se hai problemi non previsti dal test, segnalali aggiungendoli in fondo al test. **SE VEDI I QUADRATINI MA NON RIESCI A CLICCARLI... DEVI CLICCARE SUL BOTTONE VERDE "SUBMIT NEW ISSUE"** *** I file relativi al canale li trovi: - su browser: [Apre la pagina dei Canali](https://github.com/kodiondemand/addon/tree/master/channels) - sul device: [nella specifica cartella](https://github.com/kodiondemand/addon/wiki/Percorsi-sui-diversi-S.O.) , .kodi/addons/channels. Per aprirli non servono programmi particolari un semplice editor di testo è sufficiente. **Test N.1**: Controllo del file .json Occorrente: file .json **1. Indica la coerenza delle voci presenti in "language" con i contenuti presenti sul sito:** valori: ita, sub-ita (sub-ita) - [x] coerenti - [ ] non coerenti Se non sono coerenti il test è FALLITO, continua comunque a revisionare il resto **2. Icone del canale** Controlla sia presente qualcosa, tra le " " di thumbnail e banner, e che le immagini appaiano su KoD **in thumbnail:** - [x] Presente - [ ] Assente **in banner:** - [x] Presente - [ ] Assente **3. Verifica la coerenza delle voci presenti in "categories" con i contenuti presenti sul sito:** Riepilogo voci: movie, tvshow, anime, documentary, vos, adult (se il sito contiene film e serie, devono esserci sia movie che tvshow, se contiene solo film, solo movie) - [x] Corrette - [ ] 1 o più Errata/e - [ ] Assenti - Non sono presenti voci in categories, in questo caso non puoi continuare il test. Se le voci sono: Assenti, dopo aver compilato la risposta, salva il test e **NON** proseguire. **TEST FALLITO** *** **Test su KOD.** Entra in KOD -> Canali. Nella lista accedi al canale che stai testando. **N.B.**: Il nome del canale è il campo **name** nel file .json. **Test N.2: Pagina Canale** **1. Cerca o Cerca Film...** Cerca un titolo a caso in KOD e lo stesso titolo sul sito. Confronta i risultati. - [ ] OK - indica il tipo di problema **Sezione FILM (se il sito non ha film elimina questa parte)** **TestN.3: Pagina dei Titoli** *Test da effettuare mentre sei dentro un menu del canale (film, serietv, in corso ecc..)*. Voci nel menu contestuale di KOD. Posizionati su di un titolo e controlla se hai le seguenti voci, nel menu contestuale (tasto c o tenendo enter premuto): **1. Aggiungi Film in videoteca** - [ ] Si - [ ] No **2. Scarica Film (devi avere il download abilitato)** - [ ] Si - [ ] No **Fine test menu contestuale** **Fondo pagina dei titoli** **3. Paginazione, controlla ci sia la voce "Successivo" (se non c'è controlla sul sito se è presente)** - [ ] Sì - [ ] NO **Dentro un titolo **4. Entra nella pagina del titolo e verifica ci sia almeno 1 server:** - [ ] Si - [ ] No **5. Eventuali problemi riscontrati** - scrivi qui il problema/i **Sezione Serie TV (se il sito non ha serietv elimina questa parte)** Test da effettuare mentre sei nella pagina dei titoli. Per ogni titolo verifica ci siano le voci nel menu contestuale. **1. Aggiungi Serie in videoteca** - [ ] Si - [ ] No **2. Scarica Stagione (devi avere il download abilitato)** - [ ] Si - [ ] No **3. Scarica Serie (devi avere il download abilitato)** - [ ] Si - [ ] No **4. Cerca o Cerca Serie...** Cerca un titolo a caso in KOD e lo stesso titolo sul sito. Confronta i risultati. - [ ] Ok - indica il tipo di problema **5. Entra nella pagina della serie, verifica che come ultima voce ci sia "Aggiungi in videoteca":** - [ ] Si, appare - [ ] Non appare **6. Entra nella pagina dell'episodio, **NON** deve apparire la voce "Aggiungi in videoteca":** - [ ] Si, appare - [ ] Non appare **7. Eventuali problemi riscontrati** - scrivi qui il problema/i **Sezione Anime (se il sito non ha anime elimina questa parte)** Test da effettuare mentre sei nella pagina dei titoli. Per ogni titolo verifica ci siano le voci nel menu contestuale. **1. Rinumerazione (se gli episodi non appaiono nella forma 1x01)** - [x] Si - [ ] No **2. Aggiungi Serie in videoteca** - [x] Si - [ ] No **3. Aggiungi 2-3 titoli in videoteca.** - [ ] Aggiunti correttamente - [Indica eventuali problemi] (copia-incolla per tutti i titoli con cui hai avuto il problema) - COPIA qui l'ERRORE dal LOG **4. Scarica Serie** - [ ] Si - [ ] No **5. Cerca o Cerca Serie...** Cerca un titolo a caso in KOD e lo stesso titolo sul sito. Confronta i risultati. - [ ] Ok - indica il tipo di problema **6. Entra nella pagina della serie, verifica che come ultima voce ci sia "Aggiungi in videoteca":** - [ ] Appare - [ ] Non appare **7. Entra nella pagina dell'episodio, NON ci deve essere la voce "Aggiungi in videoteca":** - [x] Non appare - [ ] Appare **8. Eventuali problemi riscontrati** - scrivi qui il problema/i ** TEST PER IL CONFRONTO TRA SITO E CANALE ** **TestN.4: Pagina Sito - Menu Canale** Occorrente: Browser, KOD! e il file canale.py ( da browser o da file ) Avviso: - Sul Browser disattiva eventuali componenti aggiuntivi che bloccano i JS (javascript), li riattivi alla fine del test. Entra in ogni menu e controlla che i risultati, delle prime 5-6 pagine, siano gli stessi che trovi sul sito, comprese le varie info (ita/sub-ita, qualità ecc..), inoltre entra, se ci sono, nei menu dei generi - anni - lettera, verifica che cliccando su una voce si visualizzino i titoli. *Copia questa sezione per ogni voce che presenta problemi:* - [ ] Voce menu ( del canale dove riscontri errori) Titoli non corrispondenti: - [ ] Il totale dei Titoli è diverso da quello del sito. Alcuni Titoli non compaiono. - [x] Appaiono titoli per pagine informative o link a siti esterni. Es: Avviso agli utenti. - [ ] La lingua, del titolo, è diversa da quella riportata dal sito - [ ] Non è indicato in 1 o più titoli che sono SUB-ITA - [ ] Cliccando su "Successivo" non si visualizzano titoli - [ ] Non è indicata la qualità: Hd-DVD/rip e altri, nonostante sul sito siano presenti - [ ] NO *Fine Copia* **Test.N5: Ricerca Globale** Per questo test ti consiglio di inserire come UNICO sito quello che stai testando, come canale incluso in: Ricerca Globale -> scegli i canali da includere Il test è già compilato con le spunte, dato che devi copiarlo solo in caso di errori. Togli la spunta dove funziona. Si consiglia di cercare almeno a fino 5 titoli. O perlomeno non fermarti al 1°. Cerca 5 FILM a tuo piacimento, se il titolo non esce controlla confrontando i risultati sul sito...: *Copia questa sezione per ogni voce che presenta problemi* controlla ci siano queste voci se titolo è un FILM: - [ ] inserisci il titolo cercato che da problemi - [x] Aggiungi in videoteca - [x] Scarica Film *Fine Copia* controlla ci siano queste voci se titolo è una SERIE/ANIME: *Copia questa sezione per ogni voce che presenta problemi* controlla ci siano queste voci se titolo è un FILM: - [ ] inserisci il titolo cercato che da problemi - [x] Aggiungi in videoteca - [x] Scarica Serie - [x] Scarica Stagione - [ ] inserisci il titolo cercato che da problemi *Fine Copia* Se il canale ha la parte Novità (questa stringa avvisa che NON è presente: "not_active": ["include_in_newest"]). **Test.N6: Novità.** Per questo test ti consiglio di inserire come UNICO sito quello che stai testando, come canale incluso in: Novità -> categoria (film, serie o altro ) - [ ] Descrivere il problema Fine TEST! Grazie mille da parte di tutto il team KoD!
1.0
animeleggendari.py - Documento Template per il Test del canale Specifica, dove possibile, il tipo di problema che incontri, anche se non è presente alcuna voce per indicarlo. Se hai **suggerimenti/consigli/dubbi sul test**...Proponili e/o Chiedi! Scrivendo un commento a questo stesso issue, che trovi in fondo, dopo questa pagina. **Avvertenze:** Per il test dei canali **DEVI**: - utilizzare la versione **[BETA](https://kodiondemand.github.io/repo/KoD-installer-BETA.zip)** di KOD! - **ABILITARE IL DEBUG PER I LOG** **Per eseguire il test, ricordati di titolarlo con il nome del canale da te scelto, e salvare la pagina cliccando sul bottone verde in basso "SUBMIT NEW ISSUE"** **Ogni volta che hai un ERRORE con avviso di LOG. Puoi scegliere se: ALLEGARE IMMEDIATAMENTE il file kodi.log nel punto, della pagina, in cui sei nel test Allegare il file kodi.log a fine pagina.** **Per poter scrivere o allegare file nella pagina devi:** - cliccare sui [ ... ] in alto a destra della scheda - Edit. Da questo momento puoi scrivere e/o inviare file. Dopodiché clicca sul bottone verde "Update comment" per continuare il test nel modo consueto o per terminarlo! Se hai problemi non previsti dal test, segnalali aggiungendoli in fondo al test. **SE VEDI I QUADRATINI MA NON RIESCI A CLICCARLI... DEVI CLICCARE SUL BOTTONE VERDE "SUBMIT NEW ISSUE"** *** I file relativi al canale li trovi: - su browser: [Apre la pagina dei Canali](https://github.com/kodiondemand/addon/tree/master/channels) - sul device: [nella specifica cartella](https://github.com/kodiondemand/addon/wiki/Percorsi-sui-diversi-S.O.) , .kodi/addons/channels. Per aprirli non servono programmi particolari un semplice editor di testo è sufficiente. **Test N.1**: Controllo del file .json Occorrente: file .json **1. Indica la coerenza delle voci presenti in "language" con i contenuti presenti sul sito:** valori: ita, sub-ita (sub-ita) - [x] coerenti - [ ] non coerenti Se non sono coerenti il test è FALLITO, continua comunque a revisionare il resto **2. Icone del canale** Controlla sia presente qualcosa, tra le " " di thumbnail e banner, e che le immagini appaiano su KoD **in thumbnail:** - [x] Presente - [ ] Assente **in banner:** - [x] Presente - [ ] Assente **3. Verifica la coerenza delle voci presenti in "categories" con i contenuti presenti sul sito:** Riepilogo voci: movie, tvshow, anime, documentary, vos, adult (se il sito contiene film e serie, devono esserci sia movie che tvshow, se contiene solo film, solo movie) - [x] Corrette - [ ] 1 o più Errata/e - [ ] Assenti - Non sono presenti voci in categories, in questo caso non puoi continuare il test. Se le voci sono: Assenti, dopo aver compilato la risposta, salva il test e **NON** proseguire. **TEST FALLITO** *** **Test su KOD.** Entra in KOD -> Canali. Nella lista accedi al canale che stai testando. **N.B.**: Il nome del canale è il campo **name** nel file .json. **Test N.2: Pagina Canale** **1. Cerca o Cerca Film...** Cerca un titolo a caso in KOD e lo stesso titolo sul sito. Confronta i risultati. - [ ] OK - indica il tipo di problema **Sezione FILM (se il sito non ha film elimina questa parte)** **TestN.3: Pagina dei Titoli** *Test da effettuare mentre sei dentro un menu del canale (film, serietv, in corso ecc..)*. Voci nel menu contestuale di KOD. Posizionati su di un titolo e controlla se hai le seguenti voci, nel menu contestuale (tasto c o tenendo enter premuto): **1. Aggiungi Film in videoteca** - [ ] Si - [ ] No **2. Scarica Film (devi avere il download abilitato)** - [ ] Si - [ ] No **Fine test menu contestuale** **Fondo pagina dei titoli** **3. Paginazione, controlla ci sia la voce "Successivo" (se non c'è controlla sul sito se è presente)** - [ ] Sì - [ ] NO **Dentro un titolo **4. Entra nella pagina del titolo e verifica ci sia almeno 1 server:** - [ ] Si - [ ] No **5. Eventuali problemi riscontrati** - scrivi qui il problema/i **Sezione Serie TV (se il sito non ha serietv elimina questa parte)** Test da effettuare mentre sei nella pagina dei titoli. Per ogni titolo verifica ci siano le voci nel menu contestuale. **1. Aggiungi Serie in videoteca** - [ ] Si - [ ] No **2. Scarica Stagione (devi avere il download abilitato)** - [ ] Si - [ ] No **3. Scarica Serie (devi avere il download abilitato)** - [ ] Si - [ ] No **4. Cerca o Cerca Serie...** Cerca un titolo a caso in KOD e lo stesso titolo sul sito. Confronta i risultati. - [ ] Ok - indica il tipo di problema **5. Entra nella pagina della serie, verifica che come ultima voce ci sia "Aggiungi in videoteca":** - [ ] Si, appare - [ ] Non appare **6. Entra nella pagina dell'episodio, **NON** deve apparire la voce "Aggiungi in videoteca":** - [ ] Si, appare - [ ] Non appare **7. Eventuali problemi riscontrati** - scrivi qui il problema/i **Sezione Anime (se il sito non ha anime elimina questa parte)** Test da effettuare mentre sei nella pagina dei titoli. Per ogni titolo verifica ci siano le voci nel menu contestuale. **1. Rinumerazione (se gli episodi non appaiono nella forma 1x01)** - [x] Si - [ ] No **2. Aggiungi Serie in videoteca** - [x] Si - [ ] No **3. Aggiungi 2-3 titoli in videoteca.** - [ ] Aggiunti correttamente - [Indica eventuali problemi] (copia-incolla per tutti i titoli con cui hai avuto il problema) - COPIA qui l'ERRORE dal LOG **4. Scarica Serie** - [ ] Si - [ ] No **5. Cerca o Cerca Serie...** Cerca un titolo a caso in KOD e lo stesso titolo sul sito. Confronta i risultati. - [ ] Ok - indica il tipo di problema **6. Entra nella pagina della serie, verifica che come ultima voce ci sia "Aggiungi in videoteca":** - [ ] Appare - [ ] Non appare **7. Entra nella pagina dell'episodio, NON ci deve essere la voce "Aggiungi in videoteca":** - [x] Non appare - [ ] Appare **8. Eventuali problemi riscontrati** - scrivi qui il problema/i ** TEST PER IL CONFRONTO TRA SITO E CANALE ** **TestN.4: Pagina Sito - Menu Canale** Occorrente: Browser, KOD! e il file canale.py ( da browser o da file ) Avviso: - Sul Browser disattiva eventuali componenti aggiuntivi che bloccano i JS (javascript), li riattivi alla fine del test. Entra in ogni menu e controlla che i risultati, delle prime 5-6 pagine, siano gli stessi che trovi sul sito, comprese le varie info (ita/sub-ita, qualità ecc..), inoltre entra, se ci sono, nei menu dei generi - anni - lettera, verifica che cliccando su una voce si visualizzino i titoli. *Copia questa sezione per ogni voce che presenta problemi:* - [ ] Voce menu ( del canale dove riscontri errori) Titoli non corrispondenti: - [ ] Il totale dei Titoli è diverso da quello del sito. Alcuni Titoli non compaiono. - [x] Appaiono titoli per pagine informative o link a siti esterni. Es: Avviso agli utenti. - [ ] La lingua, del titolo, è diversa da quella riportata dal sito - [ ] Non è indicato in 1 o più titoli che sono SUB-ITA - [ ] Cliccando su "Successivo" non si visualizzano titoli - [ ] Non è indicata la qualità: Hd-DVD/rip e altri, nonostante sul sito siano presenti - [ ] NO *Fine Copia* **Test.N5: Ricerca Globale** Per questo test ti consiglio di inserire come UNICO sito quello che stai testando, come canale incluso in: Ricerca Globale -> scegli i canali da includere Il test è già compilato con le spunte, dato che devi copiarlo solo in caso di errori. Togli la spunta dove funziona. Si consiglia di cercare almeno a fino 5 titoli. O perlomeno non fermarti al 1°. Cerca 5 FILM a tuo piacimento, se il titolo non esce controlla confrontando i risultati sul sito...: *Copia questa sezione per ogni voce che presenta problemi* controlla ci siano queste voci se titolo è un FILM: - [ ] inserisci il titolo cercato che da problemi - [x] Aggiungi in videoteca - [x] Scarica Film *Fine Copia* controlla ci siano queste voci se titolo è una SERIE/ANIME: *Copia questa sezione per ogni voce che presenta problemi* controlla ci siano queste voci se titolo è un FILM: - [ ] inserisci il titolo cercato che da problemi - [x] Aggiungi in videoteca - [x] Scarica Serie - [x] Scarica Stagione - [ ] inserisci il titolo cercato che da problemi *Fine Copia* Se il canale ha la parte Novità (questa stringa avvisa che NON è presente: "not_active": ["include_in_newest"]). **Test.N6: Novità.** Per questo test ti consiglio di inserire come UNICO sito quello che stai testando, come canale incluso in: Novità -> categoria (film, serie o altro ) - [ ] Descrivere il problema Fine TEST! Grazie mille da parte di tutto il team KoD!
test
animeleggendari py documento template per il test del canale specifica dove possibile il tipo di problema che incontri anche se non è presente alcuna voce per indicarlo se hai suggerimenti consigli dubbi sul test proponili e o chiedi scrivendo un commento a questo stesso issue che trovi in fondo dopo questa pagina avvertenze per il test dei canali devi utilizzare la versione di kod abilitare il debug per i log per eseguire il test ricordati di titolarlo con il nome del canale da te scelto e salvare la pagina cliccando sul bottone verde in basso submit new issue ogni volta che hai un errore con avviso di log puoi scegliere se allegare immediatamente il file kodi log nel punto della pagina in cui sei nel test allegare il file kodi log a fine pagina per poter scrivere o allegare file nella pagina devi cliccare sui in alto a destra della scheda edit da questo momento puoi scrivere e o inviare file dopodiché clicca sul bottone verde update comment per continuare il test nel modo consueto o per terminarlo se hai problemi non previsti dal test segnalali aggiungendoli in fondo al test se vedi i quadratini ma non riesci a cliccarli devi cliccare sul bottone verde submit new issue i file relativi al canale li trovi su browser sul device kodi addons channels per aprirli non servono programmi particolari un semplice editor di testo è sufficiente test n controllo del file json occorrente file json indica la coerenza delle voci presenti in language con i contenuti presenti sul sito valori ita sub ita sub ita coerenti non coerenti se non sono coerenti il test è fallito continua comunque a revisionare il resto icone del canale controlla sia presente qualcosa tra le di thumbnail e banner e che le immagini appaiano su kod in thumbnail presente assente in banner presente assente verifica la coerenza delle voci presenti in categories con i contenuti presenti sul sito riepilogo voci movie tvshow anime documentary vos adult se il sito contiene film e serie devono esserci sia movie che tvshow se contiene solo film solo movie corrette o più errata e assenti non sono presenti voci in categories in questo caso non puoi continuare il test se le voci sono assenti dopo aver compilato la risposta salva il test e non proseguire test fallito test su kod entra in kod canali nella lista accedi al canale che stai testando n b il nome del canale è il campo name nel file json test n pagina canale cerca o cerca film cerca un titolo a caso in kod e lo stesso titolo sul sito confronta i risultati ok indica il tipo di problema sezione film se il sito non ha film elimina questa parte testn pagina dei titoli test da effettuare mentre sei dentro un menu del canale film serietv in corso ecc voci nel menu contestuale di kod posizionati su di un titolo e controlla se hai le seguenti voci nel menu contestuale tasto c o tenendo enter premuto aggiungi film in videoteca si no scarica film devi avere il download abilitato si no fine test menu contestuale fondo pagina dei titoli paginazione controlla ci sia la voce successivo se non c è controlla sul sito se è presente sì no dentro un titolo entra nella pagina del titolo e verifica ci sia almeno server si no eventuali problemi riscontrati scrivi qui il problema i sezione serie tv se il sito non ha serietv elimina questa parte test da effettuare mentre sei nella pagina dei titoli per ogni titolo verifica ci siano le voci nel menu contestuale aggiungi serie in videoteca si no scarica stagione devi avere il download abilitato si no scarica serie devi avere il download abilitato si no cerca o cerca serie cerca un titolo a caso in kod e lo stesso titolo sul sito confronta i risultati ok indica il tipo di problema entra nella pagina della serie verifica che come ultima voce ci sia aggiungi in videoteca si appare non appare entra nella pagina dell episodio non deve apparire la voce aggiungi in videoteca si appare non appare eventuali problemi riscontrati scrivi qui il problema i sezione anime se il sito non ha anime elimina questa parte test da effettuare mentre sei nella pagina dei titoli per ogni titolo verifica ci siano le voci nel menu contestuale rinumerazione se gli episodi non appaiono nella forma si no aggiungi serie in videoteca si no aggiungi titoli in videoteca aggiunti correttamente copia incolla per tutti i titoli con cui hai avuto il problema copia qui l errore dal log scarica serie si no cerca o cerca serie cerca un titolo a caso in kod e lo stesso titolo sul sito confronta i risultati ok indica il tipo di problema entra nella pagina della serie verifica che come ultima voce ci sia aggiungi in videoteca appare non appare entra nella pagina dell episodio non ci deve essere la voce aggiungi in videoteca non appare appare eventuali problemi riscontrati scrivi qui il problema i test per il confronto tra sito e canale testn pagina sito menu canale occorrente browser kod e il file canale py da browser o da file avviso sul browser disattiva eventuali componenti aggiuntivi che bloccano i js javascript li riattivi alla fine del test entra in ogni menu e controlla che i risultati delle prime pagine siano gli stessi che trovi sul sito comprese le varie info ita sub ita qualità ecc inoltre entra se ci sono nei menu dei generi anni lettera verifica che cliccando su una voce si visualizzino i titoli copia questa sezione per ogni voce che presenta problemi voce menu del canale dove riscontri errori titoli non corrispondenti il totale dei titoli è diverso da quello del sito alcuni titoli non compaiono appaiono titoli per pagine informative o link a siti esterni es avviso agli utenti la lingua del titolo è diversa da quella riportata dal sito non è indicato in o più titoli che sono sub ita cliccando su successivo non si visualizzano titoli non è indicata la qualità hd dvd rip e altri nonostante sul sito siano presenti no fine copia test ricerca globale per questo test ti consiglio di inserire come unico sito quello che stai testando come canale incluso in ricerca globale scegli i canali da includere il test è già compilato con le spunte dato che devi copiarlo solo in caso di errori togli la spunta dove funziona si consiglia di cercare almeno a fino titoli o perlomeno non fermarti al ° cerca film a tuo piacimento se il titolo non esce controlla confrontando i risultati sul sito copia questa sezione per ogni voce che presenta problemi controlla ci siano queste voci se titolo è un film inserisci il titolo cercato che da problemi aggiungi in videoteca scarica film fine copia controlla ci siano queste voci se titolo è una serie anime copia questa sezione per ogni voce che presenta problemi controlla ci siano queste voci se titolo è un film inserisci il titolo cercato che da problemi aggiungi in videoteca scarica serie scarica stagione inserisci il titolo cercato che da problemi fine copia se il canale ha la parte novità questa stringa avvisa che non è presente not active test novità per questo test ti consiglio di inserire come unico sito quello che stai testando come canale incluso in novità categoria film serie o altro descrivere il problema fine test grazie mille da parte di tutto il team kod
1
175,051
13,530,375,149
IssuesEvent
2020-09-15 19:48:47
asgiom/cr8-brm-mobile-issues
https://api.github.com/repos/asgiom/cr8-brm-mobile-issues
closed
[BUG]Wallet crash during setup
bug test
**Describe the bug** If you switch out during the setup, the setup will show a screen "Incomplete Setup". I think that's because the wallet is trying to auto lock itself. **To Reproduce** Steps to reproduce the behavior: 1. Start setup 2. Switch to a different app 3. Come back 4. See error **Expected behavior** A clear and concise description of what you expected to happen. **Screenshots** If applicable, add screenshots to help explain your problem. **Smartphone (please complete the following information):** - Device: Note8 - OS: Android - OS Version 10 - App Version 0.5.3 **Additional context** Add any other context about the problem here.
1.0
[BUG]Wallet crash during setup - **Describe the bug** If you switch out during the setup, the setup will show a screen "Incomplete Setup". I think that's because the wallet is trying to auto lock itself. **To Reproduce** Steps to reproduce the behavior: 1. Start setup 2. Switch to a different app 3. Come back 4. See error **Expected behavior** A clear and concise description of what you expected to happen. **Screenshots** If applicable, add screenshots to help explain your problem. **Smartphone (please complete the following information):** - Device: Note8 - OS: Android - OS Version 10 - App Version 0.5.3 **Additional context** Add any other context about the problem here.
test
wallet crash during setup describe the bug if you switch out during the setup the setup will show a screen incomplete setup i think that s because the wallet is trying to auto lock itself to reproduce steps to reproduce the behavior start setup switch to a different app come back see error expected behavior a clear and concise description of what you expected to happen screenshots if applicable add screenshots to help explain your problem smartphone please complete the following information device os android os version app version additional context add any other context about the problem here
1
47,638
2,982,666,230
IssuesEvent
2015-07-17 13:01:29
threemoji/threemoji
https://api.github.com/repos/threemoji/threemoji
closed
Add ability to archive chats
priority.medium
Also implement archiving of chats where the partner has already deleted his profile
1.0
Add ability to archive chats - Also implement archiving of chats where the partner has already deleted his profile
non_test
add ability to archive chats also implement archiving of chats where the partner has already deleted his profile
0
617,112
19,343,129,815
IssuesEvent
2021-12-15 07:56:57
latteart-org/latteart
https://api.github.com/repos/latteart-org/latteart
opened
記録操作順に実行するスクリプト生成機能の提供
Type: Enhancement Priority: Should
**Is your feature request related to a problem? Please describe.** 現在の生成するスクリプトは画面網羅のシナリオであり、利用者が求めるシナリオと異なることがある。 その場合、利用者がスクリプトを加工する必要がある。 **Describe the solution you'd like** 利用者が実行した操作をそのまま、記録順に実行するスクリプトを生成する機能を生成オプションとして追加する **Additional context** 要件バグ一覧表No.100からの転記
1.0
記録操作順に実行するスクリプト生成機能の提供 - **Is your feature request related to a problem? Please describe.** 現在の生成するスクリプトは画面網羅のシナリオであり、利用者が求めるシナリオと異なることがある。 その場合、利用者がスクリプトを加工する必要がある。 **Describe the solution you'd like** 利用者が実行した操作をそのまま、記録順に実行するスクリプトを生成する機能を生成オプションとして追加する **Additional context** 要件バグ一覧表No.100からの転記
non_test
記録操作順に実行するスクリプト生成機能の提供 is your feature request related to a problem please describe 現在の生成するスクリプトは画面網羅のシナリオであり、利用者が求めるシナリオと異なることがある。 その場合、利用者がスクリプトを加工する必要がある。 describe the solution you d like 利用者が実行した操作をそのまま、記録順に実行するスクリプトを生成する機能を生成オプションとして追加する additional context 要件バグ一覧表no
0
418,880
12,215,003,360
IssuesEvent
2020-05-01 11:38:40
zeit/next.js
https://api.github.com/repos/zeit/next.js
closed
AMP - Mustache template syntax
good first issue help wanted priority: low
# Feature request ## Is your feature request related to a problem? Please describe. Just creating an issue to track his here. As raised by @alankent to use `amp-mustache` templates `dangerouslySetInnerHTML` currently has to be used, which is less ergonomic, also the user has to keep in mind that __html is actually not JSX so you have to write `class` instead of `className` which can cause confusion. ``` <template type="amp-mustache" dangerouslySetInnerHTML={{ __html: ` {{#stats.allCities}} <span class="travel-badge">All cities</span> {{/stats.allCities}} {{^stats.allCities}} {{#stats.cities}} {{#isSelected}} <span class="travel-badge green">{{name}}</span> {{/isSelected}} {{/stats.cities}} {{/stats.allCities}} `}}/> ``` ## Describe the solution you'd like Haven't decided yet, creating this issue to track it / discuss.
1.0
AMP - Mustache template syntax - # Feature request ## Is your feature request related to a problem? Please describe. Just creating an issue to track his here. As raised by @alankent to use `amp-mustache` templates `dangerouslySetInnerHTML` currently has to be used, which is less ergonomic, also the user has to keep in mind that __html is actually not JSX so you have to write `class` instead of `className` which can cause confusion. ``` <template type="amp-mustache" dangerouslySetInnerHTML={{ __html: ` {{#stats.allCities}} <span class="travel-badge">All cities</span> {{/stats.allCities}} {{^stats.allCities}} {{#stats.cities}} {{#isSelected}} <span class="travel-badge green">{{name}}</span> {{/isSelected}} {{/stats.cities}} {{/stats.allCities}} `}}/> ``` ## Describe the solution you'd like Haven't decided yet, creating this issue to track it / discuss.
non_test
amp mustache template syntax feature request is your feature request related to a problem please describe just creating an issue to track his here as raised by alankent to use amp mustache templates dangerouslysetinnerhtml currently has to be used which is less ergonomic also the user has to keep in mind that html is actually not jsx so you have to write class instead of classname which can cause confusion template type amp mustache dangerouslysetinnerhtml html stats allcities all cities stats allcities stats allcities stats cities isselected name isselected stats cities stats allcities describe the solution you d like haven t decided yet creating this issue to track it discuss
0
74,449
7,430,351,369
IssuesEvent
2018-03-25 00:28:48
Blockrazor/blockrazor
https://api.github.com/repos/Blockrazor/blockrazor
reopened
Problem: Proof of Stake category doesn't have a sub-category list of PoS algos available (Site wide problem not just Currency page.)
testing solution
## Problem: Proof of Stake category doesn't have a sub-category list of PoS algos available. (Site wide problem not just Currency page.) ### Steps to reproduce: * click on Cardano on the home page * click to edit the "Hash Algorithm" ### Expected behaviour * a drop down list of different algorithms appears, allowing the selection of PoS algos including `Ouroboros` (soon to be called `Ouroboros Praos`), the PoS used by Cardano. ### Actual behaviour * the value `7be44dviDMiuoShan` appears
1.0
Problem: Proof of Stake category doesn't have a sub-category list of PoS algos available (Site wide problem not just Currency page.) - ## Problem: Proof of Stake category doesn't have a sub-category list of PoS algos available. (Site wide problem not just Currency page.) ### Steps to reproduce: * click on Cardano on the home page * click to edit the "Hash Algorithm" ### Expected behaviour * a drop down list of different algorithms appears, allowing the selection of PoS algos including `Ouroboros` (soon to be called `Ouroboros Praos`), the PoS used by Cardano. ### Actual behaviour * the value `7be44dviDMiuoShan` appears
test
problem proof of stake category doesn t have a sub category list of pos algos available site wide problem not just currency page problem proof of stake category doesn t have a sub category list of pos algos available site wide problem not just currency page steps to reproduce click on cardano on the home page click to edit the hash algorithm expected behaviour a drop down list of different algorithms appears allowing the selection of pos algos including ouroboros soon to be called ouroboros praos the pos used by cardano actual behaviour the value appears
1
202,370
15,282,389,623
IssuesEvent
2021-02-23 09:30:06
Rello/analytics
https://api.github.com/repos/Rello/analytics
opened
Datasource: Excel
datasource testing
- [ ] Create new datasource - [ ] supported file types: xls, xlsx, ods ![Bildschirmfoto 2021-02-23 um 10 29 22](https://user-images.githubusercontent.com/13385119/108824433-000eb080-75c2-11eb-85f0-ddae4a80e687.png)
1.0
Datasource: Excel - - [ ] Create new datasource - [ ] supported file types: xls, xlsx, ods ![Bildschirmfoto 2021-02-23 um 10 29 22](https://user-images.githubusercontent.com/13385119/108824433-000eb080-75c2-11eb-85f0-ddae4a80e687.png)
test
datasource excel create new datasource supported file types xls xlsx ods
1
430,495
30,187,944,871
IssuesEvent
2023-07-04 13:22:40
mindsdb/mindsdb
https://api.github.com/repos/mindsdb/mindsdb
closed
[Docs] Update instructions for MySQL
help wanted good first issue documentation first-timers-only
## Instructions 1. Go to the `docs/data-integrations/mysql.mdx` file. 2. At the end of the `Implementation` chapter, add the following content: ``` <Tip> If you installed MindsDB locally via pip, you need to install all handler dependencies manually. To do so, go to the handler's folder (mindsdb/integrations/handlers/mysql_handler) and run this command: `pip install -r requirements.txt`. </Tip> ``` 3. Save your changes and create a PR. ## The https://github.com/mindsdb/mindsdb/labels/first-timers-only Label We are happy to welcome you on board! Please take a look at the rules below for first-time contributors. 1. You can solve only one issue labeled as https://github.com/mindsdb/mindsdb/labels/first-timers-only. After that, please look at other issues labeled as https://github.com/mindsdb/mindsdb/labels/good%20first%20issue, https://github.com/mindsdb/mindsdb/labels/help%20wanted, or https://github.com/mindsdb/mindsdb/labels/integration. 2. Please leave a comment on this issue and wait until you are assigned. Then you can create a PR. 3. After you create your first PR in the MindsDB repository, please sign our CLA to become a MindsDB contributor. You can do that by leaving a comment that contains the following: `I have read the CLA Document and I hereby sign the CLA` **Thank you for contributing to MindsDB!** **If you enjoy using MindsDB, we'd be happy if you could show your support by giving us a :star: on GitHub.**
1.0
[Docs] Update instructions for MySQL - ## Instructions 1. Go to the `docs/data-integrations/mysql.mdx` file. 2. At the end of the `Implementation` chapter, add the following content: ``` <Tip> If you installed MindsDB locally via pip, you need to install all handler dependencies manually. To do so, go to the handler's folder (mindsdb/integrations/handlers/mysql_handler) and run this command: `pip install -r requirements.txt`. </Tip> ``` 3. Save your changes and create a PR. ## The https://github.com/mindsdb/mindsdb/labels/first-timers-only Label We are happy to welcome you on board! Please take a look at the rules below for first-time contributors. 1. You can solve only one issue labeled as https://github.com/mindsdb/mindsdb/labels/first-timers-only. After that, please look at other issues labeled as https://github.com/mindsdb/mindsdb/labels/good%20first%20issue, https://github.com/mindsdb/mindsdb/labels/help%20wanted, or https://github.com/mindsdb/mindsdb/labels/integration. 2. Please leave a comment on this issue and wait until you are assigned. Then you can create a PR. 3. After you create your first PR in the MindsDB repository, please sign our CLA to become a MindsDB contributor. You can do that by leaving a comment that contains the following: `I have read the CLA Document and I hereby sign the CLA` **Thank you for contributing to MindsDB!** **If you enjoy using MindsDB, we'd be happy if you could show your support by giving us a :star: on GitHub.**
non_test
update instructions for mysql instructions go to the docs data integrations mysql mdx file at the end of the implementation chapter add the following content if you installed mindsdb locally via pip you need to install all handler dependencies manually to do so go to the handler s folder mindsdb integrations handlers mysql handler and run this command pip install r requirements txt save your changes and create a pr the label we are happy to welcome you on board please take a look at the rules below for first time contributors you can solve only one issue labeled as after that please look at other issues labeled as or please leave a comment on this issue and wait until you are assigned then you can create a pr after you create your first pr in the mindsdb repository please sign our cla to become a mindsdb contributor you can do that by leaving a comment that contains the following i have read the cla document and i hereby sign the cla thank you for contributing to mindsdb if you enjoy using mindsdb we d be happy if you could show your support by giving us a star on github
0
300,148
25,948,187,596
IssuesEvent
2022-12-17 07:51:36
michael-milette/moodle-local_contact
https://api.github.com/repos/michael-milette/moodle-local_contact
closed
Validation error with multi-select field
bug testing required
Hello, first I want to thank you for your contribution with this fantastic plugin. The problem that I have detected occurs when we have a multiple select element in the form. In your documentation, it is well reflected that the name of this field must end with []. But, no matter how many times I tested, I could not get the information of this field to appear in mails. Reviewing the code, in the function "sendmessage", when it begins to process the collected information, there is a conditional: `if (!in_array($key, array('sesskey', 'submit')) && trim($value) != '') {` The parameter provided to trim should be a string. But when a multi-select field is used in the form then it is an array. `PHP Warning: trim() expects parameter 1 to be string, array given in /sites/yoursite/files/local/contact/classes/local_contact.php on line 268` A solution could be to move this part of the code, before excluding the empty information fields. `// Join array of values. Example: <select multiple>. if (is_array($value)) { $value = join(', ', $value); }`
1.0
Validation error with multi-select field - Hello, first I want to thank you for your contribution with this fantastic plugin. The problem that I have detected occurs when we have a multiple select element in the form. In your documentation, it is well reflected that the name of this field must end with []. But, no matter how many times I tested, I could not get the information of this field to appear in mails. Reviewing the code, in the function "sendmessage", when it begins to process the collected information, there is a conditional: `if (!in_array($key, array('sesskey', 'submit')) && trim($value) != '') {` The parameter provided to trim should be a string. But when a multi-select field is used in the form then it is an array. `PHP Warning: trim() expects parameter 1 to be string, array given in /sites/yoursite/files/local/contact/classes/local_contact.php on line 268` A solution could be to move this part of the code, before excluding the empty information fields. `// Join array of values. Example: <select multiple>. if (is_array($value)) { $value = join(', ', $value); }`
test
validation error with multi select field hello first i want to thank you for your contribution with this fantastic plugin the problem that i have detected occurs when we have a multiple select element in the form in your documentation it is well reflected that the name of this field must end with but no matter how many times i tested i could not get the information of this field to appear in mails reviewing the code in the function sendmessage when it begins to process the collected information there is a conditional if in array key array sesskey submit trim value the parameter provided to trim should be a string but when a multi select field is used in the form then it is an array php warning trim expects parameter to be string array given in sites yoursite files local contact classes local contact php on line a solution could be to move this part of the code before excluding the empty information fields join array of values example if is array value value join value
1
85,188
7,963,483,532
IssuesEvent
2018-07-13 17:45:30
LLK/scratch-gui
https://api.github.com/repos/LLK/scratch-gui
opened
Issues found in Smoke Test on Friday 7/13
smoke-testing
Please file or mark as filed/won't file/duplicate/etc. each issue. * [ ] Using the test project, the monitors that appear using the Show / Hide blocks overlap. They appear on top of each other on the stage. @carljbowman * [ ] A chunk of the speech bubble gets chopped off in the renderer @kchadha * [ ] Speech bubble was cut off in all the blocks project (I think the one that said backdrop number: 2). The right rounded side was missing. I can’t repro @fsih * [ ] Adding a Sprite or Backdrop takes 3 taps to open the library. This is likely due to how Safari handles hovers as touch events. @carljbowman * [ ] Tutorial titles should wrap under thumbnails (for other languages) @chrisgarrity ![image7](https://user-images.githubusercontent.com/1088291/42705885-d26a5d84-86a2-11e8-921a-2e818d3ac00e.png) * [ ] Should this say close? Feels like remove might remove that tutorial permanently? @fsih ![image10](https://user-images.githubusercontent.com/1088291/42705905-e2acd424-86a2-11e8-910e-a9a2485e4294.png) Device | Browser | Name -- | -- | -- Windows | Chrome | Paul Mac | Chrome | Bryce iPad | Safari | Carl Chromebook | Chrome | Andrew Windows* | Firefox | DD Android Tablet | Chrome | Eric R Windows* | Edge |   Mac | Safari | Karishma Mac | Firefox | ChrisG
1.0
Issues found in Smoke Test on Friday 7/13 - Please file or mark as filed/won't file/duplicate/etc. each issue. * [ ] Using the test project, the monitors that appear using the Show / Hide blocks overlap. They appear on top of each other on the stage. @carljbowman * [ ] A chunk of the speech bubble gets chopped off in the renderer @kchadha * [ ] Speech bubble was cut off in all the blocks project (I think the one that said backdrop number: 2). The right rounded side was missing. I can’t repro @fsih * [ ] Adding a Sprite or Backdrop takes 3 taps to open the library. This is likely due to how Safari handles hovers as touch events. @carljbowman * [ ] Tutorial titles should wrap under thumbnails (for other languages) @chrisgarrity ![image7](https://user-images.githubusercontent.com/1088291/42705885-d26a5d84-86a2-11e8-921a-2e818d3ac00e.png) * [ ] Should this say close? Feels like remove might remove that tutorial permanently? @fsih ![image10](https://user-images.githubusercontent.com/1088291/42705905-e2acd424-86a2-11e8-910e-a9a2485e4294.png) Device | Browser | Name -- | -- | -- Windows | Chrome | Paul Mac | Chrome | Bryce iPad | Safari | Carl Chromebook | Chrome | Andrew Windows* | Firefox | DD Android Tablet | Chrome | Eric R Windows* | Edge |   Mac | Safari | Karishma Mac | Firefox | ChrisG
test
issues found in smoke test on friday please file or mark as filed won t file duplicate etc each issue using the test project the monitors that appear using the show hide blocks overlap they appear on top of each other on the stage carljbowman a chunk of the speech bubble gets chopped off in the renderer kchadha speech bubble was cut off in all the blocks project i think the one that said backdrop number the right rounded side was missing i can’t repro fsih adding a sprite or backdrop takes taps to open the library this is likely due to how safari handles hovers as touch events carljbowman tutorial titles should wrap under thumbnails for other languages chrisgarrity should this say close feels like remove might remove that tutorial permanently fsih device browser name windows chrome paul mac chrome bryce ipad safari carl chromebook chrome andrew windows firefox dd android tablet chrome eric r windows edge   mac safari karishma mac firefox chrisg
1
285,764
24,694,919,851
IssuesEvent
2022-10-19 11:21:26
zephyrproject-rtos/test_results
https://api.github.com/repos/zephyrproject-rtos/test_results
closed
tests-ci : arch: arm: irq_vector_table test No Console Output(Timeout)
bug area: Tests
**Describe the bug** irq_vector_table test is No Console Output(Timeout) on zephyr-v3.2.0-326-ge97e24e7a619 on mimxrt1170_evk_cm7 see logs for details **To Reproduce** 1. ``` scripts/twister --device-testing --device-serial /dev/ttyACM0 -p mimxrt1170_evk_cm7 --sub-test arch.arm ``` 2. See error **Expected behavior** test pass **Impact** **Logs and console output** ``` None ``` **Environment (please complete the following information):** - OS: (e.g. Linux ) - Toolchain (e.g Zephyr SDK) - Commit SHA or Version used: zephyr-v3.2.0-326-ge97e24e7a619
1.0
tests-ci : arch: arm: irq_vector_table test No Console Output(Timeout) - **Describe the bug** irq_vector_table test is No Console Output(Timeout) on zephyr-v3.2.0-326-ge97e24e7a619 on mimxrt1170_evk_cm7 see logs for details **To Reproduce** 1. ``` scripts/twister --device-testing --device-serial /dev/ttyACM0 -p mimxrt1170_evk_cm7 --sub-test arch.arm ``` 2. See error **Expected behavior** test pass **Impact** **Logs and console output** ``` None ``` **Environment (please complete the following information):** - OS: (e.g. Linux ) - Toolchain (e.g Zephyr SDK) - Commit SHA or Version used: zephyr-v3.2.0-326-ge97e24e7a619
test
tests ci arch arm irq vector table test no console output timeout describe the bug irq vector table test is no console output timeout on zephyr on evk see logs for details to reproduce scripts twister device testing device serial dev p evk sub test arch arm see error expected behavior test pass impact logs and console output none environment please complete the following information os e g linux toolchain e g zephyr sdk commit sha or version used zephyr
1
352,790
10,546,075,078
IssuesEvent
2019-10-02 20:36:08
googleapis/nodejs-firestore
https://api.github.com/repos/googleapis/nodejs-firestore
closed
Writing zero-length Buffer fails at GRPC
priority: p2 type: bug
Buffer is accepted as one of Firestore submitted field and would becomes `Blob`. For example this works when placed in a pure JS object to be set to Firestore document. : `Buffer.alloc(1)` Which it shows up as `AA==` in the Firestore console. However when using `Buffer.alloc(0)` to create a zero-length buffer as described in https://nodejs.org/api/buffer.html#buffer_class_method_buffer_alloc_size_fill_encoding this error is thrown on trying to set that value to Firestore : ``` Error: Cannot convert firestore.v1.Value with type unset. at Http2CallStream.call.on (node_modules/@grpc/grpc-js/build/src/client.js:96:45) ```
1.0
Writing zero-length Buffer fails at GRPC - Buffer is accepted as one of Firestore submitted field and would becomes `Blob`. For example this works when placed in a pure JS object to be set to Firestore document. : `Buffer.alloc(1)` Which it shows up as `AA==` in the Firestore console. However when using `Buffer.alloc(0)` to create a zero-length buffer as described in https://nodejs.org/api/buffer.html#buffer_class_method_buffer_alloc_size_fill_encoding this error is thrown on trying to set that value to Firestore : ``` Error: Cannot convert firestore.v1.Value with type unset. at Http2CallStream.call.on (node_modules/@grpc/grpc-js/build/src/client.js:96:45) ```
non_test
writing zero length buffer fails at grpc buffer is accepted as one of firestore submitted field and would becomes blob for example this works when placed in a pure js object to be set to firestore document buffer alloc which it shows up as aa in the firestore console however when using buffer alloc to create a zero length buffer as described in this error is thrown on trying to set that value to firestore error cannot convert firestore value with type unset at call on node modules grpc grpc js build src client js
0
351,223
25,018,737,857
IssuesEvent
2022-11-03 21:27:21
PacketFabric/terraform-provider-packetfabric
https://api.github.com/repos/PacketFabric/terraform-provider-packetfabric
closed
Use-case examples and Location Data Source links on the docs registry are broken
documentation
There are couple borken link in the v0.4.0 doc on the registry: 1. The link pointing to the Example Use Cases isn't working on the provider registry documentation: https://registry.terraform.io/providers/PacketFabric/packetfabric/latest/docs#using-with-other-terraform-providers ``` For examples on how to use a cloud's Terraform provider alongside PacketFabric, see [examples/use-cases](https://registry.terraform.io/providers/PacketFabric/packetfabric/latest/examples/use-cases). ``` Should be: ``` For examples on how to use a cloud's Terraform provider alongside PacketFabric, see [examples/use-cases](https://github.com/PacketFabric/terraform-provider-packetfabric/tree/main/examples/use-cases). ``` 2. On the same page: ``` data source. See [packetfabric_locations (Data Source)](https://registry.terraform.io/providers/PacketFabric/packetfabric/latest/docs/guides/docs/data-sources/packetfabric_locations). ``` should be ``` data source. See [packetfabric_locations (Data Source)](https://registry.terraform.io/providers/PacketFabric/packetfabric/latest/docs/data-sources/packetfabric_locations). ```
1.0
Use-case examples and Location Data Source links on the docs registry are broken - There are couple borken link in the v0.4.0 doc on the registry: 1. The link pointing to the Example Use Cases isn't working on the provider registry documentation: https://registry.terraform.io/providers/PacketFabric/packetfabric/latest/docs#using-with-other-terraform-providers ``` For examples on how to use a cloud's Terraform provider alongside PacketFabric, see [examples/use-cases](https://registry.terraform.io/providers/PacketFabric/packetfabric/latest/examples/use-cases). ``` Should be: ``` For examples on how to use a cloud's Terraform provider alongside PacketFabric, see [examples/use-cases](https://github.com/PacketFabric/terraform-provider-packetfabric/tree/main/examples/use-cases). ``` 2. On the same page: ``` data source. See [packetfabric_locations (Data Source)](https://registry.terraform.io/providers/PacketFabric/packetfabric/latest/docs/guides/docs/data-sources/packetfabric_locations). ``` should be ``` data source. See [packetfabric_locations (Data Source)](https://registry.terraform.io/providers/PacketFabric/packetfabric/latest/docs/data-sources/packetfabric_locations). ```
non_test
use case examples and location data source links on the docs registry are broken there are couple borken link in the doc on the registry the link pointing to the example use cases isn t working on the provider registry documentation for examples on how to use a cloud s terraform provider alongside packetfabric see should be for examples on how to use a cloud s terraform provider alongside packetfabric see on the same page data source see should be data source see
0
159,967
12,498,534,344
IssuesEvent
2020-06-01 18:27:50
microsoft/AzureStorageExplorer
https://api.github.com/repos/microsoft/AzureStorageExplorer
closed
The error detail is incorrect when changing one blob access tier to 'Archive' under Germany/China account
:gear: blobs :grey_question: external :heavy_check_mark: won't fix 🧪 testing
**Storage Explorer Version:** 1.13.0 **Build**: [20200410.14](https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=3633000) **Branch**: rel/1.13.0 **Platform/OS:** Windows 10/ Linux Ubuntu 18.04/ macOS High Sierra **Architecture**: ia32/x64 **Regression From:** Not a regression **Steps to reproduce:** 1. Sign in with one Germany account. 2. Expand one GPV2 account -> Blob Containers. 3. Create a new blob container -> Upload one block blob to it. 4. Change the blob access tier to 'Archive'. 5. Check the activity log. **Expect Experience:** The error detail is correct like below. ![image](https://user-images.githubusercontent.com/54055206/79112034-3e3b2100-7db0-11ea-8864-72c9fa6d9746.png) **Actual Experience:** The error detail is incorrect. `The value for one of the HTTP headers is not in the correct format` **More Info:** This issue also reproduces for one regular blob under China account.
1.0
The error detail is incorrect when changing one blob access tier to 'Archive' under Germany/China account - **Storage Explorer Version:** 1.13.0 **Build**: [20200410.14](https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=3633000) **Branch**: rel/1.13.0 **Platform/OS:** Windows 10/ Linux Ubuntu 18.04/ macOS High Sierra **Architecture**: ia32/x64 **Regression From:** Not a regression **Steps to reproduce:** 1. Sign in with one Germany account. 2. Expand one GPV2 account -> Blob Containers. 3. Create a new blob container -> Upload one block blob to it. 4. Change the blob access tier to 'Archive'. 5. Check the activity log. **Expect Experience:** The error detail is correct like below. ![image](https://user-images.githubusercontent.com/54055206/79112034-3e3b2100-7db0-11ea-8864-72c9fa6d9746.png) **Actual Experience:** The error detail is incorrect. `The value for one of the HTTP headers is not in the correct format` **More Info:** This issue also reproduces for one regular blob under China account.
test
the error detail is incorrect when changing one blob access tier to archive under germany china account storage explorer version build branch rel platform os windows linux ubuntu macos high sierra architecture regression from not a regression steps to reproduce sign in with one germany account expand one account blob containers create a new blob container upload one block blob to it change the blob access tier to archive check the activity log expect experience the error detail is correct like below actual experience the error detail is incorrect the value for one of the http headers is not in the correct format more info this issue also reproduces for one regular blob under china account
1
156,511
19,898,625,008
IssuesEvent
2022-01-25 04:00:20
Recidiviz/covid19-dashboard
https://api.github.com/repos/Recidiviz/covid19-dashboard
opened
Security Alert - Package: tar; Severity: HIGH; Vuln ID: GHSA-qq89-hq3f-393p
Subject: Security Subject: Vulnerability Severity: HIGH
--- due: 2022-02-24 --- A new vulnerability has been reported by Dependabot. The criticality of this vulnerability is HIGH. HIGH vulnerabilities have an SLA of 30 days according to our policy. Affected package: tar Ecosystem: NPM Affected version range: >= 6.0.0, < 6.1.9 Summary: Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links Description: ### Impact Arbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained two directories and a symlink with names containing unicode values that normalized to the same value. Additionally, on Windows systems, long path portions would resolve to the same file system entities as their 8.3 "short path" counterparts. A specially crafted tar archive could thus include directories with two forms of the path that resolve to the same file system entity, followed by a symbolic link with a name in the first form, lastly followed by a file using the second form. It led to bypassing node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. The v3 branch of `node-tar` has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of `node-tar`. If this is not possible, a workaround is available below. ### Patches 6.1.9 || 5.0.10 || 4.4.18 ### Workarounds Users may work around this vulnerability without upgrading by creating a custom filter method which prevents the extraction of symbolic links. ```js const tar = require('tar') tar.x({ file: 'archive.tgz', filter: (file, entry) => { if (entry.type === 'SymbolicLink') { return false } else { return true } } }) ``` Users are encouraged to upgrade to the latest patched versions, rather than attempt to sanitize tar input themselves. #### Fix The problem is addressed in the following ways, when comparing paths in the directory cache and path reservation systems: 1. The `String.normalize('NFKD')` method is used to first normalize all unicode to its maximally compatible and multi-code-point form. 2. All slashes are normalized to `/` on Windows systems (on posix systems, `\` is a valid filename character, and thus left intact). 3. When a symbolic link is encountered on Windows systems, the entire directory cache is cleared. Collisions related to use of 8.3 short names to replace directories with other (non-symlink) types of entries may make archives fail to extract properly, but will not result in arbitrary file writes. identifiers: [{'type': 'GHSA', 'value': 'GHSA-qq89-hq3f-393p'}, {'type': 'CVE', 'value': 'CVE-2021-37712'}] Fixed Version: 6.1.9 Created Date = January 25, 2022 ***Additional Context*** https://github.com/Recidiviz/covid19-dashboard/security/dependabot?q=is%3Aopen+sort%3Anewest
True
Security Alert - Package: tar; Severity: HIGH; Vuln ID: GHSA-qq89-hq3f-393p - --- due: 2022-02-24 --- A new vulnerability has been reported by Dependabot. The criticality of this vulnerability is HIGH. HIGH vulnerabilities have an SLA of 30 days according to our policy. Affected package: tar Ecosystem: NPM Affected version range: >= 6.0.0, < 6.1.9 Summary: Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links Description: ### Impact Arbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained two directories and a symlink with names containing unicode values that normalized to the same value. Additionally, on Windows systems, long path portions would resolve to the same file system entities as their 8.3 "short path" counterparts. A specially crafted tar archive could thus include directories with two forms of the path that resolve to the same file system entity, followed by a symbolic link with a name in the first form, lastly followed by a file using the second form. It led to bypassing node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. The v3 branch of `node-tar` has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of `node-tar`. If this is not possible, a workaround is available below. ### Patches 6.1.9 || 5.0.10 || 4.4.18 ### Workarounds Users may work around this vulnerability without upgrading by creating a custom filter method which prevents the extraction of symbolic links. ```js const tar = require('tar') tar.x({ file: 'archive.tgz', filter: (file, entry) => { if (entry.type === 'SymbolicLink') { return false } else { return true } } }) ``` Users are encouraged to upgrade to the latest patched versions, rather than attempt to sanitize tar input themselves. #### Fix The problem is addressed in the following ways, when comparing paths in the directory cache and path reservation systems: 1. The `String.normalize('NFKD')` method is used to first normalize all unicode to its maximally compatible and multi-code-point form. 2. All slashes are normalized to `/` on Windows systems (on posix systems, `\` is a valid filename character, and thus left intact). 3. When a symbolic link is encountered on Windows systems, the entire directory cache is cleared. Collisions related to use of 8.3 short names to replace directories with other (non-symlink) types of entries may make archives fail to extract properly, but will not result in arbitrary file writes. identifiers: [{'type': 'GHSA', 'value': 'GHSA-qq89-hq3f-393p'}, {'type': 'CVE', 'value': 'CVE-2021-37712'}] Fixed Version: 6.1.9 Created Date = January 25, 2022 ***Additional Context*** https://github.com/Recidiviz/covid19-dashboard/security/dependabot?q=is%3Aopen+sort%3Anewest
non_test
security alert package tar severity high vuln id ghsa due a new vulnerability has been reported by dependabot the criticality of this vulnerability is high high vulnerabilities have an sla of days according to our policy affected package tar ecosystem npm affected version range summary arbitrary file creation overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links description impact arbitrary file creation arbitrary file overwrite arbitrary code execution node tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted this is in part achieved by ensuring that extracted directories are not symlinks additionally in order to prevent unnecessary stat calls to determine whether a given path is a directory paths are cached when directories are created this logic was insufficient when extracting tar files that contained two directories and a symlink with names containing unicode values that normalized to the same value additionally on windows systems long path portions would resolve to the same file system entities as their short path counterparts a specially crafted tar archive could thus include directories with two forms of the path that resolve to the same file system entity followed by a symbolic link with a name in the first form lastly followed by a file using the second form it led to bypassing node tar symlink checks on directories essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location thus allowing arbitrary file creation and overwrite the branch of node tar has been deprecated and did not receive patches for these issues if you are still using a release we recommend you update to a more recent version of node tar if this is not possible a workaround is available below patches workarounds users may work around this vulnerability without upgrading by creating a custom filter method which prevents the extraction of symbolic links js const tar require tar tar x file archive tgz filter file entry if entry type symboliclink return false else return true users are encouraged to upgrade to the latest patched versions rather than attempt to sanitize tar input themselves fix the problem is addressed in the following ways when comparing paths in the directory cache and path reservation systems the string normalize nfkd method is used to first normalize all unicode to its maximally compatible and multi code point form all slashes are normalized to on windows systems on posix systems is a valid filename character and thus left intact when a symbolic link is encountered on windows systems the entire directory cache is cleared collisions related to use of short names to replace directories with other non symlink types of entries may make archives fail to extract properly but will not result in arbitrary file writes identifiers fixed version created date january additional context
0
80,896
15,589,376,302
IssuesEvent
2021-03-18 07:57:40
ros132/rosh123
https://api.github.com/repos/ros132/rosh123
opened
CVE-2013-7315 (Medium) detected in spring-web-3.1.1.RELEASE.jar
security vulnerability
## CVE-2013-7315 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-web-3.1.1.RELEASE.jar</b></p></summary> <p>Spring Framework Parent</p> <p>Path to dependency file: rosh123/pom.xml</p> <p>Path to vulnerable library: rosh123/Spring-MVC-LoginForm-1.0.0-BUILD-SNAPSHOT/META-INF/maven/com.spring/Spring-MVC-LoginForm/target/Spring-MVC-LoginForm-1.0.0-BUILD-SNAPSHOT/WEB-INF/lib/spring-web-3.1.1.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/3.1.1.RELEASE/spring-web-3.1.1.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/3.1.1.RELEASE/spring-web-3.1.1.RELEASE.jar,rosh123/target/Spring-MVC-LoginForm-1.0.0-BUILD-SNAPSHOT/WEB-INF/lib/spring-web-3.1.1.RELEASE.jar,rosh123/Spring-MVC-LoginForm-1.0.0-BUILD-SNAPSHOT/WEB-INF/lib/spring-web-3.1.1.RELEASE.jar</p> <p> Dependency Hierarchy: - :x: **spring-web-3.1.1.RELEASE.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/ros132/rosh123/commit/de130481baa5d49839c4e442b96a27d4a0b39c6d">de130481baa5d49839c4e442b96a27d4a0b39c6d</a></p> <p>Found in base branch: <b>main</b></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> The Spring MVC in Spring Framework before 3.2.4 and 4.0.0.M1 through 4.0.0.M2 does not disable external entity resolution for the StAX XMLInputFactory, which allows context-dependent attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via crafted XML with JAXB, aka an XML External Entity (XXE) issue, and a different vulnerability than CVE-2013-4152. NOTE: this issue was SPLIT from CVE-2013-4152 due to different affected versions. <p>Publish Date: 2014-01-23 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-7315>CVE-2013-7315</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>6.8</b>)</summary> <p> Base Score Metrics not available</p> </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-2013-7315">https://nvd.nist.gov/vuln/detail/CVE-2013-7315</a></p> <p>Release Date: 2014-01-23</p> <p>Fix Resolution: org.springframework:spring-web:3.2.4.RELEASE,org.springframework:spring-web:4.0.0.M3</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-2013-7315 (Medium) detected in spring-web-3.1.1.RELEASE.jar - ## CVE-2013-7315 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-web-3.1.1.RELEASE.jar</b></p></summary> <p>Spring Framework Parent</p> <p>Path to dependency file: rosh123/pom.xml</p> <p>Path to vulnerable library: rosh123/Spring-MVC-LoginForm-1.0.0-BUILD-SNAPSHOT/META-INF/maven/com.spring/Spring-MVC-LoginForm/target/Spring-MVC-LoginForm-1.0.0-BUILD-SNAPSHOT/WEB-INF/lib/spring-web-3.1.1.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/3.1.1.RELEASE/spring-web-3.1.1.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/3.1.1.RELEASE/spring-web-3.1.1.RELEASE.jar,rosh123/target/Spring-MVC-LoginForm-1.0.0-BUILD-SNAPSHOT/WEB-INF/lib/spring-web-3.1.1.RELEASE.jar,rosh123/Spring-MVC-LoginForm-1.0.0-BUILD-SNAPSHOT/WEB-INF/lib/spring-web-3.1.1.RELEASE.jar</p> <p> Dependency Hierarchy: - :x: **spring-web-3.1.1.RELEASE.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/ros132/rosh123/commit/de130481baa5d49839c4e442b96a27d4a0b39c6d">de130481baa5d49839c4e442b96a27d4a0b39c6d</a></p> <p>Found in base branch: <b>main</b></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> The Spring MVC in Spring Framework before 3.2.4 and 4.0.0.M1 through 4.0.0.M2 does not disable external entity resolution for the StAX XMLInputFactory, which allows context-dependent attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via crafted XML with JAXB, aka an XML External Entity (XXE) issue, and a different vulnerability than CVE-2013-4152. NOTE: this issue was SPLIT from CVE-2013-4152 due to different affected versions. <p>Publish Date: 2014-01-23 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-7315>CVE-2013-7315</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>6.8</b>)</summary> <p> Base Score Metrics not available</p> </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-2013-7315">https://nvd.nist.gov/vuln/detail/CVE-2013-7315</a></p> <p>Release Date: 2014-01-23</p> <p>Fix Resolution: org.springframework:spring-web:3.2.4.RELEASE,org.springframework:spring-web:4.0.0.M3</p> </p> </details> <p></p> *** Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
non_test
cve medium detected in spring web release jar cve medium severity vulnerability vulnerable library spring web release jar spring framework parent path to dependency file pom xml path to vulnerable library spring mvc loginform build snapshot meta inf maven com spring spring mvc loginform target spring mvc loginform build snapshot web inf lib spring web release jar home wss scanner repository org springframework spring web release spring web release jar home wss scanner repository org springframework spring web release spring web release jar target spring mvc loginform build snapshot web inf lib spring web release jar spring mvc loginform build snapshot web inf lib spring web release jar dependency hierarchy x spring web release jar vulnerable library found in head commit a href found in base branch main vulnerability details the spring mvc in spring framework before and through does not disable external entity resolution for the stax xmlinputfactory which allows context dependent attackers to read arbitrary files cause a denial of service and conduct csrf attacks via crafted xml with jaxb aka an xml external entity xxe issue and a different vulnerability than cve note this issue was split from cve due to different affected versions publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution org springframework spring web release org springframework spring web step up your open source security game with whitesource
0
112,815
11,779,986,566
IssuesEvent
2020-03-16 19:06:12
softeng-701-group-5/softeng-701-assignment-1
https://api.github.com/repos/softeng-701-group-5/softeng-701-assignment-1
closed
Add documentation for frontend testing procedure
APPROVED :+1: documentation
**User Story** <!--As a [user role], I'd like to [do something], so that [some goal].--> As a frontend developer, I'd like to define the process of unit testing on the frontend, so that new collaborators are comfortable with the process. **Acceptance Criteria** - Usage of Jest and Enzyme explained - Snapshot testing explained - How to run the tests, updating snapshots explained **Notes** (documentation should explain how to use, what each concept is and why we are using it). If you are not a merger, send the documentation to @Matteas-Eden and he can upload it for you.
1.0
Add documentation for frontend testing procedure - **User Story** <!--As a [user role], I'd like to [do something], so that [some goal].--> As a frontend developer, I'd like to define the process of unit testing on the frontend, so that new collaborators are comfortable with the process. **Acceptance Criteria** - Usage of Jest and Enzyme explained - Snapshot testing explained - How to run the tests, updating snapshots explained **Notes** (documentation should explain how to use, what each concept is and why we are using it). If you are not a merger, send the documentation to @Matteas-Eden and he can upload it for you.
non_test
add documentation for frontend testing procedure user story as a frontend developer i d like to define the process of unit testing on the frontend so that new collaborators are comfortable with the process acceptance criteria usage of jest and enzyme explained snapshot testing explained how to run the tests updating snapshots explained notes documentation should explain how to use what each concept is and why we are using it if you are not a merger send the documentation to matteas eden and he can upload it for you
0
110,192
9,438,798,446
IssuesEvent
2019-04-14 03:55:11
alkemann/stone_soup_cosplay
https://api.github.com/repos/alkemann/stone_soup_cosplay
closed
"Special Rule" field
testing
Occasionally I will want to have some deviation from the rules, like allowing an old version or letting the player switch gods. This should probably appear before the Cosplay Conduct Points header, with its own attention-getting header (coloured text?), but only when the special rule field is filled out. Alternately just having a general purpose field that appears there, where I can enter html, would be fine.
1.0
"Special Rule" field - Occasionally I will want to have some deviation from the rules, like allowing an old version or letting the player switch gods. This should probably appear before the Cosplay Conduct Points header, with its own attention-getting header (coloured text?), but only when the special rule field is filled out. Alternately just having a general purpose field that appears there, where I can enter html, would be fine.
test
special rule field occasionally i will want to have some deviation from the rules like allowing an old version or letting the player switch gods this should probably appear before the cosplay conduct points header with its own attention getting header coloured text but only when the special rule field is filled out alternately just having a general purpose field that appears there where i can enter html would be fine
1
3,506
6,559,856,291
IssuesEvent
2017-09-07 06:52:07
inasafe/inasafe-realtime
https://api.github.com/repos/inasafe/inasafe-realtime
closed
Realtime earthquake translation in Bahasa Indonesia
earthquake feature request in progress realtime processor web page
Problem Similar issue with InaSAFE Realtime flood translation (#3291), currently InaSAFE Realtime Earthquake in Bahasa Indonesia is not 100% translated yet. See original ticket at https://github.com/inasafe/inasafe/issues/3714 for further discussion.
1.0
Realtime earthquake translation in Bahasa Indonesia - Problem Similar issue with InaSAFE Realtime flood translation (#3291), currently InaSAFE Realtime Earthquake in Bahasa Indonesia is not 100% translated yet. See original ticket at https://github.com/inasafe/inasafe/issues/3714 for further discussion.
non_test
realtime earthquake translation in bahasa indonesia problem similar issue with inasafe realtime flood translation currently inasafe realtime earthquake in bahasa indonesia is not translated yet see original ticket at for further discussion
0
85,366
7,967,126,129
IssuesEvent
2018-07-15 10:06:06
lee61011/blog-comments
https://api.github.com/repos/lee61011/blog-comments
closed
test | lee61011
/2018/05/21/test/ Gitalk
https://lee61011.github.io/2018/05/21/test/ 20182018年4月1日 晴​ 又是犹豫的一天，这之前我已经犹豫了两三个月了，犹豫就像一潭死滞的淤泥，我感觉自己的生命在其中正以几十倍于从前的速度消耗着。这里说的从前是我没有产生那个想法的时候，是基延还没有商业化的时候。 ​ 从写字楼顶层的窗子望出去，城市在下面扩展开来，像一片被剖开的集成电路，我不过是那密密麻麻的纳米线路中奔跑的一个小电子，真的算不了什么，所以我做出的决定也算不了
1.0
test | lee61011 - https://lee61011.github.io/2018/05/21/test/ 20182018年4月1日 晴​ 又是犹豫的一天，这之前我已经犹豫了两三个月了，犹豫就像一潭死滞的淤泥，我感觉自己的生命在其中正以几十倍于从前的速度消耗着。这里说的从前是我没有产生那个想法的时候，是基延还没有商业化的时候。 ​ 从写字楼顶层的窗子望出去，城市在下面扩展开来，像一片被剖开的集成电路，我不过是那密密麻麻的纳米线路中奔跑的一个小电子，真的算不了什么，所以我做出的决定也算不了
test
test 晴​ 又是犹豫的一天，这之前我已经犹豫了两三个月了，犹豫就像一潭死滞的淤泥，我感觉自己的生命在其中正以几十倍于从前的速度消耗着。这里说的从前是我没有产生那个想法的时候，是基延还没有商业化的时候。 ​ 从写字楼顶层的窗子望出去，城市在下面扩展开来，像一片被剖开的集成电路，我不过是那密密麻麻的纳米线路中奔跑的一个小电子，真的算不了什么，所以我做出的决定也算不了
1
244,542
20,676,120,387
IssuesEvent
2022-03-10 09:26:59
treeverse/lakeFS
https://api.github.com/repos/treeverse/lakeFS
opened
Can't run runShellCommand func with terminal mode
bug area/testing
For some of our nessie tests, we would like to run a lakectl command on terminal mode, usually on cases where there's a difference in output when running the command in terminal mode (cat-sst command for example doesn't print headers when not running in terminal mode). Currently, there's a problem with running the `runShellCommand` function with the `isTerminal` flag as true
1.0
Can't run runShellCommand func with terminal mode - For some of our nessie tests, we would like to run a lakectl command on terminal mode, usually on cases where there's a difference in output when running the command in terminal mode (cat-sst command for example doesn't print headers when not running in terminal mode). Currently, there's a problem with running the `runShellCommand` function with the `isTerminal` flag as true
test
can t run runshellcommand func with terminal mode for some of our nessie tests we would like to run a lakectl command on terminal mode usually on cases where there s a difference in output when running the command in terminal mode cat sst command for example doesn t print headers when not running in terminal mode currently there s a problem with running the runshellcommand function with the isterminal flag as true
1
119,684
10,060,888,004
IssuesEvent
2019-07-22 19:58:04
kudobuilder/kudo
https://api.github.com/repos/kudobuilder/kudo
opened
control plane sometimes fails to start in integration tests
component/testing flaky test kind/bug
<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security sensitive, please disclose it privately to a security contact: https://github.com/kudobuilder/kudo/blob/master/SECURITY_CONTACTS --> **What happened**: https://circleci.com/gh/kudobuilder/kudo/3278?utm_campaign=workflow-failed&utm_medium=email&utm_source=notification ``` 2019/07/22 19:56:18 failed to start the controlplane. retried 5 times: timeout waiting for process etcd to start ``` Looks like I didn't quite get all of the edge cases yet.
2.0
control plane sometimes fails to start in integration tests - <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks! If the matter is security sensitive, please disclose it privately to a security contact: https://github.com/kudobuilder/kudo/blob/master/SECURITY_CONTACTS --> **What happened**: https://circleci.com/gh/kudobuilder/kudo/3278?utm_campaign=workflow-failed&utm_medium=email&utm_source=notification ``` 2019/07/22 19:56:18 failed to start the controlplane. retried 5 times: timeout waiting for process etcd to start ``` Looks like I didn't quite get all of the edge cases yet.
test
control plane sometimes fails to start in integration tests please use this template while reporting a bug and provide as much info as possible not doing so may result in your bug not being addressed in a timely manner thanks if the matter is security sensitive please disclose it privately to a security contact what happened failed to start the controlplane retried times timeout waiting for process etcd to start looks like i didn t quite get all of the edge cases yet
1
235,136
19,301,363,869
IssuesEvent
2021-12-13 06:12:10
pingcap/br
https://api.github.com/repos/pingcap/br
closed
Test br_log_restore fails
type/bug severity/minor component/test
1. What did you do? ``` [2021-03-04T03:44:40.272Z] + bin/cdc --ca /tmp/backup_restore_test/certs/ca.pem --cert /tmp/backup_restore_test/certs/ticdc.pem --key /tmp/backup_restore_test/certs/ticdc.key server --pd=https://127.0.0.1:2379 --log-file=ticdc.log --addr=0.0.0.0:18301 --advertise-addr=127.0.0.1:18301 [2021-03-04T03:44:40.272Z] + sleep 2 [2021-03-04T03:44:40.272Z] Error: run server: [CDC:ErrServeHTTP]listen tcp 0.0.0.0:18301: bind: address already in use ... [2021-03-04T03:46:06.162Z] [2021/03/04 11:46:05.928 +08:00] [ERROR] [restore.go:54] ["failed to restore"] [error="failed to read s3 file, file info: input.bucket='cdcs3', input.key='br_log_restore/log.meta': NoSuchKey: The specified key does not exist.\n\tstatus code: 404, request id: 166906EF39A903BE, host id: "] [errorVerbose="NoSuchKey: The specified key does not exist.\n\tstatus code: 404, request id: 166906EF39A903BE, host id: \nfailed to read s3 file, file info: input.bucket='cdcs3', input.key='br_log_restore/log.meta'\ngithub.com/pingcap/br/pkg/storage.(*S3Storage).ReadFile\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/pkg/storage/s3.go:344\ngithub.com/pingcap/br/pkg/restore.(*LogClient).RestoreLogData\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/pkg/restore/log_client.go:680\ngithub.com/pingcap/br/pkg/task.RunLogRestore\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/pkg/task/restore_log.go:136\ngithub.com/pingcap/br/cmd/br.runLogRestoreCommand\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/cmd/br/restore.go:53\ngithub.com/pingcap/br/cmd/br.newLogRestoreCommand.func1\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/cmd/br/restore.go:157\ngithub.com/spf13/cobra.(*Command).execute\n\t/go/pkg/mod/github.com/spf13/[email protected]/command.go:842\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\t/go/pkg/mod/github.com/spf13/[email protected]/command.go:950\ngithub.com/spf13/cobra.(*Command).Execute\n\t/go/pkg/mod/github.com/spf13/[email protected]/command.go:887\ngithub.com/pingcap/br/cmd/br.main\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/cmd/br/main.go:56\ngithub.com/pingcap/br/cmd/br.TestRunMain.func1\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/cmd/br/main_test.go:39\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1357"] [stack="github.com/pingcap/br/cmd/br.runLogRestoreCommand\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/cmd/br/restore.go:54\ngithub.com/pingcap/br/cmd/br.newLogRestoreCommand.func1\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/cmd/br/restore.go:157\ngithub.com/spf13/cobra.(*Command).execute\n\t/go/pkg/mod/github.com/spf13/[email protected]/command.go:842\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\t/go/pkg/mod/github.com/spf13/[email protected]/command.go:950\ngithub.com/spf13/cobra.(*Command).Execute\n\t/go/pkg/mod/github.com/spf13/[email protected]/command.go:887\ngithub.com/pingcap/br/cmd/br.main\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/cmd/br/main.go:56\ngithub.com/pingcap/br/cmd/br.TestRunMain.func1\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/cmd/br/main_test.go:39"] ``` https://internal.pingcap.net/idc-jenkins/blue/organizations/jenkins/br_ghpr_unit_and_integration_test/detail/br_ghpr_unit_and_integration_test/5295/pipeline#step-1431-log-77
1.0
Test br_log_restore fails - 1. What did you do? ``` [2021-03-04T03:44:40.272Z] + bin/cdc --ca /tmp/backup_restore_test/certs/ca.pem --cert /tmp/backup_restore_test/certs/ticdc.pem --key /tmp/backup_restore_test/certs/ticdc.key server --pd=https://127.0.0.1:2379 --log-file=ticdc.log --addr=0.0.0.0:18301 --advertise-addr=127.0.0.1:18301 [2021-03-04T03:44:40.272Z] + sleep 2 [2021-03-04T03:44:40.272Z] Error: run server: [CDC:ErrServeHTTP]listen tcp 0.0.0.0:18301: bind: address already in use ... [2021-03-04T03:46:06.162Z] [2021/03/04 11:46:05.928 +08:00] [ERROR] [restore.go:54] ["failed to restore"] [error="failed to read s3 file, file info: input.bucket='cdcs3', input.key='br_log_restore/log.meta': NoSuchKey: The specified key does not exist.\n\tstatus code: 404, request id: 166906EF39A903BE, host id: "] [errorVerbose="NoSuchKey: The specified key does not exist.\n\tstatus code: 404, request id: 166906EF39A903BE, host id: \nfailed to read s3 file, file info: input.bucket='cdcs3', input.key='br_log_restore/log.meta'\ngithub.com/pingcap/br/pkg/storage.(*S3Storage).ReadFile\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/pkg/storage/s3.go:344\ngithub.com/pingcap/br/pkg/restore.(*LogClient).RestoreLogData\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/pkg/restore/log_client.go:680\ngithub.com/pingcap/br/pkg/task.RunLogRestore\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/pkg/task/restore_log.go:136\ngithub.com/pingcap/br/cmd/br.runLogRestoreCommand\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/cmd/br/restore.go:53\ngithub.com/pingcap/br/cmd/br.newLogRestoreCommand.func1\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/cmd/br/restore.go:157\ngithub.com/spf13/cobra.(*Command).execute\n\t/go/pkg/mod/github.com/spf13/[email protected]/command.go:842\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\t/go/pkg/mod/github.com/spf13/[email protected]/command.go:950\ngithub.com/spf13/cobra.(*Command).Execute\n\t/go/pkg/mod/github.com/spf13/[email protected]/command.go:887\ngithub.com/pingcap/br/cmd/br.main\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/cmd/br/main.go:56\ngithub.com/pingcap/br/cmd/br.TestRunMain.func1\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/cmd/br/main_test.go:39\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1357"] [stack="github.com/pingcap/br/cmd/br.runLogRestoreCommand\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/cmd/br/restore.go:54\ngithub.com/pingcap/br/cmd/br.newLogRestoreCommand.func1\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/cmd/br/restore.go:157\ngithub.com/spf13/cobra.(*Command).execute\n\t/go/pkg/mod/github.com/spf13/[email protected]/command.go:842\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\t/go/pkg/mod/github.com/spf13/[email protected]/command.go:950\ngithub.com/spf13/cobra.(*Command).Execute\n\t/go/pkg/mod/github.com/spf13/[email protected]/command.go:887\ngithub.com/pingcap/br/cmd/br.main\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/cmd/br/main.go:56\ngithub.com/pingcap/br/cmd/br.TestRunMain.func1\n\t/home/jenkins/agent/workspace/br_ghpr_unit_and_integration_test/go/src/github.com/pingcap/br/cmd/br/main_test.go:39"] ``` https://internal.pingcap.net/idc-jenkins/blue/organizations/jenkins/br_ghpr_unit_and_integration_test/detail/br_ghpr_unit_and_integration_test/5295/pipeline#step-1431-log-77
test
test br log restore fails what did you do bin cdc ca tmp backup restore test certs ca pem cert tmp backup restore test certs ticdc pem key tmp backup restore test certs ticdc key server pd log file ticdc log addr advertise addr sleep error run server listen tcp bind address already in use
1
27,568
4,321,891,808
IssuesEvent
2016-07-25 12:10:01
ValveSoftware/csgo-osx-linux
https://api.github.com/repos/ValveSoftware/csgo-osx-linux
closed
The Professional achievement
Need Retest Need System Info Reviewed
Seems to be broken. Despite numerous victories in Arms Race & Demolition modes it doesn't seem to be registering them. Ok it is not a gamebreaker but it is nevertheless a bug.
1.0
The Professional achievement - Seems to be broken. Despite numerous victories in Arms Race & Demolition modes it doesn't seem to be registering them. Ok it is not a gamebreaker but it is nevertheless a bug.
test
the professional achievement seems to be broken despite numerous victories in arms race demolition modes it doesn t seem to be registering them ok it is not a gamebreaker but it is nevertheless a bug
1
211,337
16,196,975,144
IssuesEvent
2021-05-04 15:39:58
rstudio/rstudio
https://api.github.com/repos/rstudio/rstudio
closed
Realtime spelling decorations in Visual Mode will sometimes clear improperly
bug spellcheck test
### System details RStudio Edition : Desktop or Server RStudio Version : 1.4 OS Version : Any R Version : Any ### Steps to reproduce the problem 1. Type a misspelled word 2. Hit spacebar and see the underline show up 3. Hit backspace and notice it disappear ### Describe the problem in detail The logic behind clearing decorations is overly aggressive. This is also affecting the removal of Typo.js logic with how it does the initial focus decoration addition. ### Describe the behavior you expected Misspelled words are always underlined. - [x ] I have read the guide for [submitting good bug reports](https://github.com/rstudio/rstudio/wiki/Writing-Good-Bug-Reports). - [ x] I have installed the latest version of RStudio, and confirmed that the issue still persists. - [ x] If I am reporting an RStudio crash, I have included a [diagnostics report](https://support.rstudio.com/hc/en-us/articles/200321257-Running-a-Diagnostics-Report). - [ x] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
1.0
Realtime spelling decorations in Visual Mode will sometimes clear improperly - ### System details RStudio Edition : Desktop or Server RStudio Version : 1.4 OS Version : Any R Version : Any ### Steps to reproduce the problem 1. Type a misspelled word 2. Hit spacebar and see the underline show up 3. Hit backspace and notice it disappear ### Describe the problem in detail The logic behind clearing decorations is overly aggressive. This is also affecting the removal of Typo.js logic with how it does the initial focus decoration addition. ### Describe the behavior you expected Misspelled words are always underlined. - [x ] I have read the guide for [submitting good bug reports](https://github.com/rstudio/rstudio/wiki/Writing-Good-Bug-Reports). - [ x] I have installed the latest version of RStudio, and confirmed that the issue still persists. - [ x] If I am reporting an RStudio crash, I have included a [diagnostics report](https://support.rstudio.com/hc/en-us/articles/200321257-Running-a-Diagnostics-Report). - [ x] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
test
realtime spelling decorations in visual mode will sometimes clear improperly system details rstudio edition desktop or server rstudio version os version any r version any steps to reproduce the problem type a misspelled word hit spacebar and see the underline show up hit backspace and notice it disappear describe the problem in detail the logic behind clearing decorations is overly aggressive this is also affecting the removal of typo js logic with how it does the initial focus decoration addition describe the behavior you expected misspelled words are always underlined i have read the guide for i have installed the latest version of rstudio and confirmed that the issue still persists if i am reporting an rstudio crash i have included a i have done my best to include a minimal self contained set of instructions for consistently reproducing the issue
1
333,506
24,377,085,307
IssuesEvent
2022-10-04 02:45:10
NYU-Devops-2022-Order/orders
https://api.github.com/repos/NYU-Devops-2022-Order/orders
closed
Week 2 Zoom Meeting Minute
documentation
- Each one with the task of the table(scheme design) is supposed to raise one issue - **Order**(Ze), **Item**(Vidisha), **Customer**(Raksha), - Give a rough desc. and design - Next week(first-week `Sprint #1`), give more detailed designs and implementations. - Tanmay and Yintao first write the docs/dummy REST API (first-week `#Sprint 1`) - In `Sprint #0`, just choose the issues you want. - Everyone gives a rough estimate (individually) & labels each issue. - Assign an environment setup issue for yourself.
1.0
Week 2 Zoom Meeting Minute - - Each one with the task of the table(scheme design) is supposed to raise one issue - **Order**(Ze), **Item**(Vidisha), **Customer**(Raksha), - Give a rough desc. and design - Next week(first-week `Sprint #1`), give more detailed designs and implementations. - Tanmay and Yintao first write the docs/dummy REST API (first-week `#Sprint 1`) - In `Sprint #0`, just choose the issues you want. - Everyone gives a rough estimate (individually) & labels each issue. - Assign an environment setup issue for yourself.
non_test
week zoom meeting minute each one with the task of the table scheme design is supposed to raise one issue order ze item vidisha customer raksha give a rough desc and design next week first week sprint give more detailed designs and implementations tanmay and yintao first write the docs dummy rest api first week sprint in sprint just choose the issues you want everyone gives a rough estimate individually labels each issue assign an environment setup issue for yourself
0
328,869
28,138,305,255
IssuesEvent
2023-04-01 16:47:22
meandair/rweather-decoder
https://api.github.com/repos/meandair/rweather-decoder
closed
METAR: Add tests for plain daytime
wx: metar improvement test
Add tests for plain daytime decoding when the anchor time is not supplied.
1.0
METAR: Add tests for plain daytime - Add tests for plain daytime decoding when the anchor time is not supplied.
test
metar add tests for plain daytime add tests for plain daytime decoding when the anchor time is not supplied
1
528,152
15,360,960,322
IssuesEvent
2021-03-01 17:32:39
ntop/ntopng
https://api.github.com/repos/ntop/ntopng
closed
Add the ability to specify the interface to use for icmp ping
enhancement priority ticket
Currently it is not possible to specify the network interface to be used for icmp/icmp6 ping in active monitoring
1.0
Add the ability to specify the interface to use for icmp ping - Currently it is not possible to specify the network interface to be used for icmp/icmp6 ping in active monitoring
non_test
add the ability to specify the interface to use for icmp ping currently it is not possible to specify the network interface to be used for icmp ping in active monitoring
0
138,373
11,199,549,024
IssuesEvent
2020-01-03 19:03:29
mozilla/iris_firefox
https://api.github.com/repos/mozilla/iris_firefox
closed
Fix popup_windows_can_be_enabled
OS: All Priority: High Suite: prefs Target: Firefox Test: regression
Fix popup_windows_can_be_enabled Pop-up window wasn't blocked https://testrail.stage.mozaws.net/index.php?/cases/view/159259
1.0
Fix popup_windows_can_be_enabled - Fix popup_windows_can_be_enabled Pop-up window wasn't blocked https://testrail.stage.mozaws.net/index.php?/cases/view/159259
test
fix popup windows can be enabled fix popup windows can be enabled pop up window wasn t blocked
1
292,803
8,968,707,154
IssuesEvent
2019-01-29 08:54:27
netdata/netdata
https://api.github.com/repos/netdata/netdata
closed
move python module nvidia_smi to go.d
area/external new collector priority/medium
<!--- This is a generic issue template. We usually prefer contributors to use one of 3 other specific issue templates (bug report, feature request, question) to allow our automation classify those so you can get response faster. However if your issue doesn't fall into either one of those 3 categories use this generic template. ---> #### Summary Go has [bindings](https://github.com/mindprince/gonvml) for [NVIDIA Management Library (NVML) ](https://developer.nvidia.com/nvidia-management-library-nvml)which is a C-based API that can be used for monitoring NVIDIA GPU devices. It does not call the nvidia-smi binary. This is great improvement.
1.0
move python module nvidia_smi to go.d - <!--- This is a generic issue template. We usually prefer contributors to use one of 3 other specific issue templates (bug report, feature request, question) to allow our automation classify those so you can get response faster. However if your issue doesn't fall into either one of those 3 categories use this generic template. ---> #### Summary Go has [bindings](https://github.com/mindprince/gonvml) for [NVIDIA Management Library (NVML) ](https://developer.nvidia.com/nvidia-management-library-nvml)which is a C-based API that can be used for monitoring NVIDIA GPU devices. It does not call the nvidia-smi binary. This is great improvement.
non_test
move python module nvidia smi to go d this is a generic issue template we usually prefer contributors to use one of other specific issue templates bug report feature request question to allow our automation classify those so you can get response faster however if your issue doesn t fall into either one of those categories use this generic template summary go has for is a c based api that can be used for monitoring nvidia gpu devices it does not call the nvidia smi binary this is great improvement
0