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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
551,038 | 16,136,458,091 | IssuesEvent | 2021-04-29 12:29:56 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.picuki.com - video or audio doesn't play | browser-firefox engine-gecko os-ios priority-normal | <!-- @browser: Firefox iOS 33.0 -->
<!-- @ua_header: Mozilla/5.0 (iPhone; CPU OS 14_4_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) FxiOS/33.0 Mobile/15E148 Safari/605.1.15 -->
<!-- @reported_with: mobile-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/72286 -->
**URL**: https://www.picuki.com/media/2561938428708822141
**Browser / Version**: Firefox iOS 33.0
**Operating System**: iOS 14.4.2
**Tested Another Browser**: Yes Safari
**Problem type**: Video or audio doesn't play
**Description**: The video or audio does not play
**Steps to Reproduce**:
Films and picuki stories dont play
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.picuki.com - video or audio doesn't play - <!-- @browser: Firefox iOS 33.0 -->
<!-- @ua_header: Mozilla/5.0 (iPhone; CPU OS 14_4_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) FxiOS/33.0 Mobile/15E148 Safari/605.1.15 -->
<!-- @reported_with: mobile-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/72286 -->
**URL**: https://www.picuki.com/media/2561938428708822141
**Browser / Version**: Firefox iOS 33.0
**Operating System**: iOS 14.4.2
**Tested Another Browser**: Yes Safari
**Problem type**: Video or audio doesn't play
**Description**: The video or audio does not play
**Steps to Reproduce**:
Films and picuki stories dont play
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_test | video or audio doesn t play url browser version firefox ios operating system ios tested another browser yes safari problem type video or audio doesn t play description the video or audio does not play steps to reproduce films and picuki stories dont play browser configuration none from with ❤️ | 0 |
799,366 | 28,305,021,818 | IssuesEvent | 2023-04-10 10:06:34 | AY2223S2-CS2103T-T13-2/tp | https://api.github.com/repos/AY2223S2-CS2103T-T13-2/tp | closed | V1.4: Populate sample recipes with ingredient substitutions - Load Testing | priority.Low severity.Low Fixed | Each member to come up with 10 recipes with > 6 non-trivial ingredients and >6 non-trivial steps, in a JSON file. | 1.0 | V1.4: Populate sample recipes with ingredient substitutions - Load Testing - Each member to come up with 10 recipes with > 6 non-trivial ingredients and >6 non-trivial steps, in a JSON file. | non_test | populate sample recipes with ingredient substitutions load testing each member to come up with recipes with non trivial ingredients and non trivial steps in a json file | 0 |
61,100 | 8,488,603,389 | IssuesEvent | 2018-10-26 17:10:06 | dotnet/machinelearning | https://api.github.com/repos/dotnet/machinelearning | opened | Matrix Factorization Needs Documentation | documentation | The newly added module only has a test but we definitely need a user-facing document. Users may not read through my test code. | 1.0 | Matrix Factorization Needs Documentation - The newly added module only has a test but we definitely need a user-facing document. Users may not read through my test code. | non_test | matrix factorization needs documentation the newly added module only has a test but we definitely need a user facing document users may not read through my test code | 0 |
286,712 | 24,775,053,513 | IssuesEvent | 2022-10-23 16:22:47 | quarkusio/quarkus | https://api.github.com/repos/quarkusio/quarkus | closed | quarkus-arquillian does call @Before unless @RunAsClient is present | kind/bug area/testing | Arquillian processes all @Before annotations (org.junit.Before) when
@RunAsClient annotation (org.jboss.arquillian.container.test.api.RunAsClient)
is not present and when present. quarkus-arquillian only processes the
@Before annotation when @RunAsClient is present.
Test AsyncPostProcessingTest has @Before and no @RunAsClient. Test fails
because client is null. The method is never called.
@Before
public void init() {
client = (ResteasyClient)ClientBuilder.newClient();
}
Test JaxrsAsyncServletTest has the @Before and @RunAsClient annotations and
the same method definition as above client is assigned.
Project shows issue. https://github.com/rsearls/quarkus-Before-annotation.git
See setup directions in project README
Execution env.
jdk 11.0.2
mvn 3.6.0
quarkus 1.2.0.Final
| 1.0 | quarkus-arquillian does call @Before unless @RunAsClient is present - Arquillian processes all @Before annotations (org.junit.Before) when
@RunAsClient annotation (org.jboss.arquillian.container.test.api.RunAsClient)
is not present and when present. quarkus-arquillian only processes the
@Before annotation when @RunAsClient is present.
Test AsyncPostProcessingTest has @Before and no @RunAsClient. Test fails
because client is null. The method is never called.
@Before
public void init() {
client = (ResteasyClient)ClientBuilder.newClient();
}
Test JaxrsAsyncServletTest has the @Before and @RunAsClient annotations and
the same method definition as above client is assigned.
Project shows issue. https://github.com/rsearls/quarkus-Before-annotation.git
See setup directions in project README
Execution env.
jdk 11.0.2
mvn 3.6.0
quarkus 1.2.0.Final
| test | quarkus arquillian does call before unless runasclient is present arquillian processes all before annotations org junit before when runasclient annotation org jboss arquillian container test api runasclient is not present and when present quarkus arquillian only processes the before annotation when runasclient is present test asyncpostprocessingtest has before and no runasclient test fails because client is null the method is never called before public void init client resteasyclient clientbuilder newclient test jaxrsasyncservlettest has the before and runasclient annotations and the same method definition as above client is assigned project shows issue see setup directions in project readme execution env jdk mvn quarkus final | 1 |
29,208 | 4,479,093,683 | IssuesEvent | 2016-08-27 11:35:46 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | Failed tests (21860): TestSplitSnapshotRace_SplitWins | test-failure | https://circleci.com/gh/cockroachdb/cockroach/21860
```
I160827 11:25:20.251358 util/log/trace.go:64 reply error Increment ["a",/Min): key range "a"-"a\x00" could not be located within a range on store
W160827 11:25:20.251571 kv/dist_sender.go:816 key range "a"-"a\x00" could not be located within a range on store
I160827 11:25:20.253728 kv/dist_sender.go:1035 application error: key range "a"-"a\x00" could not be located within a range on store
I160827 11:25:20.253868 util/log/trace.go:64 reply error Increment ["a",/Min): key range "a"-"a\x00" could not be located within a range on store
W160827 11:25:20.254101 kv/dist_sender.go:816 key range "a"-"a\x00" could not be located within a range on store
panic: test timed out after 5m0s
``` | 1.0 | Failed tests (21860): TestSplitSnapshotRace_SplitWins - https://circleci.com/gh/cockroachdb/cockroach/21860
```
I160827 11:25:20.251358 util/log/trace.go:64 reply error Increment ["a",/Min): key range "a"-"a\x00" could not be located within a range on store
W160827 11:25:20.251571 kv/dist_sender.go:816 key range "a"-"a\x00" could not be located within a range on store
I160827 11:25:20.253728 kv/dist_sender.go:1035 application error: key range "a"-"a\x00" could not be located within a range on store
I160827 11:25:20.253868 util/log/trace.go:64 reply error Increment ["a",/Min): key range "a"-"a\x00" could not be located within a range on store
W160827 11:25:20.254101 kv/dist_sender.go:816 key range "a"-"a\x00" could not be located within a range on store
panic: test timed out after 5m0s
``` | test | failed tests testsplitsnapshotrace splitwins util log trace go reply error increment a min key range a a could not be located within a range on store kv dist sender go key range a a could not be located within a range on store kv dist sender go application error key range a a could not be located within a range on store util log trace go reply error increment a min key range a a could not be located within a range on store kv dist sender go key range a a could not be located within a range on store panic test timed out after | 1 |
171,381 | 6,487,735,214 | IssuesEvent | 2017-08-20 10:54:23 | GoogleCloudPlatform/google-cloud-eclipse | https://api.github.com/repos/GoogleCloudPlatform/google-cloud-eclipse | opened | Endpoints v2 support | enhancement high priority question | @lesv @patflynn
What should we do about Endpoints v2? Should we add it to the list of available libraries or replace the current endpoints v1?
It appears to run on App Engine Standard Java 7.
| 1.0 | Endpoints v2 support - @lesv @patflynn
What should we do about Endpoints v2? Should we add it to the list of available libraries or replace the current endpoints v1?
It appears to run on App Engine Standard Java 7.
| non_test | endpoints support lesv patflynn what should we do about endpoints should we add it to the list of available libraries or replace the current endpoints it appears to run on app engine standard java | 0 |
134,998 | 30,224,709,780 | IssuesEvent | 2023-07-05 22:48:08 | h4sh5/pypi-auto-scanner | https://api.github.com/repos/h4sh5/pypi-auto-scanner | opened | datadog-checks-dev 22.0.0 has 1 GuardDog issues | guarddog code-execution | https://pypi.org/project/datadog-checks-dev
https://inspector.pypi.io/project/datadog-checks-dev
```{
"dependency": "datadog-checks-dev",
"version": "22.0.0",
"result": {
"issues": 1,
"errors": {},
"results": {
"code-execution": [
{
"location": "datadog_checks_dev-22.0.0/datadog_checks/dev/tooling/commands/ci/setup.py:66",
"code": " subprocess.run(cmd, shell=True, check=True)",
"message": "This package is executing OS commands in the setup.py file"
}
]
},
"path": "/tmp/tmpzdwzoonf/datadog-checks-dev"
}
}``` | 1.0 | datadog-checks-dev 22.0.0 has 1 GuardDog issues - https://pypi.org/project/datadog-checks-dev
https://inspector.pypi.io/project/datadog-checks-dev
```{
"dependency": "datadog-checks-dev",
"version": "22.0.0",
"result": {
"issues": 1,
"errors": {},
"results": {
"code-execution": [
{
"location": "datadog_checks_dev-22.0.0/datadog_checks/dev/tooling/commands/ci/setup.py:66",
"code": " subprocess.run(cmd, shell=True, check=True)",
"message": "This package is executing OS commands in the setup.py file"
}
]
},
"path": "/tmp/tmpzdwzoonf/datadog-checks-dev"
}
}``` | non_test | datadog checks dev has guarddog issues dependency datadog checks dev version result issues errors results code execution location datadog checks dev datadog checks dev tooling commands ci setup py code subprocess run cmd shell true check true message this package is executing os commands in the setup py file path tmp tmpzdwzoonf datadog checks dev | 0 |
334,868 | 29,994,206,518 | IssuesEvent | 2023-06-26 03:07:12 | pandas-dev/pandas | https://api.github.com/repos/pandas-dev/pandas | closed | BUG: `TestDataFrameSetItem.test_setitem_dtype[uint64]` and `TestSeriesNLargestNSmallest.test_nlargest_nullable[UInt8]` fail on aarch64 | Unreliable Test ARM | ### Pandas version checks
- [X] I have checked that this issue has not already been reported.
- [X] I have confirmed this bug exists on the [latest version](https://pandas.pydata.org/docs/whatsnew/index.html) of pandas.
- [ ] I have confirmed this bug exists on the [main branch](https://pandas.pydata.org/docs/dev/getting_started/install.html#installing-the-development-version-of-pandas) of pandas.
### Reproducible Example
```python
Run tests on openSUSE Tumbleweed aarch64
```
### Issue Description
`TestDataFrameSetItem.test_setitem_dtype[uint64]` and `TestSeriesNLargestNSmallest.test_nlargest_nullable[UInt8]` fail on aarch64:
```
[ 7109s] =================================== FAILURES ===================================
[ 7109s] _______________ TestDataFrameSetItem.test_setitem_dtype[uint64] ________________
[ 7109s] [gw1] linux -- Python 3.11.3 /usr/bin/python3.11
[ 7109s]
[ 7109s] self = <pandas.tests.frame.indexing.test_setitem.TestDataFrameSetItem object at 0xffff55491b50>
[ 7109s] dtype = 'uint64'
[ 7109s] float_frame = A B C D
[ 7109s] Pn96zxFOj3 -0.530699 0.350158 -0.311547 0.707319
[ 7109s] 2cjtkii5Zw -0.41....252126 1.341911
[ 7109s] ts3SGMnjfe -0.077150 2.134881 1.451667 -0.589377
[ 7109s] 43mi5CIWi3 -0.751679 1.275031 -0.521072 0.631581
[ 7109s]
[ 7109s] @pytest.mark.parametrize(
[ 7109s] "dtype", ["int32", "int64", "uint32", "uint64", "float32", "float64"]
[ 7109s] )
[ 7109s] def test_setitem_dtype(self, dtype, float_frame):
[ 7109s] arr = np.random.randn(len(float_frame))
[ 7109s]
[ 7109s] > float_frame[dtype] = np.array(arr, dtype=dtype)
[ 7109s] E RuntimeWarning: invalid value encountered in cast
[ 7109s]
[ 7109s] pandas/tests/frame/indexing/test_setitem.py:66: RuntimeWarning
[ 7109s] __________ TestSeriesNLargestNSmallest.test_nlargest_nullable[UInt8] ___________
[ 7109s] [gw1] linux -- Python 3.11.3 /usr/bin/python3.11
[ 7109s]
[ 7109s] self = <pandas.tests.series.methods.test_nlargest.TestSeriesNLargestNSmallest object at 0xffff3ed83b10>
[ 7109s] any_numeric_ea_dtype = 'UInt8'
[ 7109s]
[ 7109s] def test_nlargest_nullable(self, any_numeric_ea_dtype):
[ 7109s] # GH#42816
[ 7109s] dtype = any_numeric_ea_dtype
[ 7109s] > arr = np.random.randn(10).astype(dtype.lower(), copy=False)
[ 7109s] E RuntimeWarning: invalid value encountered in cast
[ 7109s]
[ 7109s] pandas/tests/series/methods/test_nlargest.py:220: RuntimeWarning
```
### Expected Behavior
Tests should pass.
### Installed Versions
2.0.2 from openSUSE Tumbleweed package | 1.0 | BUG: `TestDataFrameSetItem.test_setitem_dtype[uint64]` and `TestSeriesNLargestNSmallest.test_nlargest_nullable[UInt8]` fail on aarch64 - ### Pandas version checks
- [X] I have checked that this issue has not already been reported.
- [X] I have confirmed this bug exists on the [latest version](https://pandas.pydata.org/docs/whatsnew/index.html) of pandas.
- [ ] I have confirmed this bug exists on the [main branch](https://pandas.pydata.org/docs/dev/getting_started/install.html#installing-the-development-version-of-pandas) of pandas.
### Reproducible Example
```python
Run tests on openSUSE Tumbleweed aarch64
```
### Issue Description
`TestDataFrameSetItem.test_setitem_dtype[uint64]` and `TestSeriesNLargestNSmallest.test_nlargest_nullable[UInt8]` fail on aarch64:
```
[ 7109s] =================================== FAILURES ===================================
[ 7109s] _______________ TestDataFrameSetItem.test_setitem_dtype[uint64] ________________
[ 7109s] [gw1] linux -- Python 3.11.3 /usr/bin/python3.11
[ 7109s]
[ 7109s] self = <pandas.tests.frame.indexing.test_setitem.TestDataFrameSetItem object at 0xffff55491b50>
[ 7109s] dtype = 'uint64'
[ 7109s] float_frame = A B C D
[ 7109s] Pn96zxFOj3 -0.530699 0.350158 -0.311547 0.707319
[ 7109s] 2cjtkii5Zw -0.41....252126 1.341911
[ 7109s] ts3SGMnjfe -0.077150 2.134881 1.451667 -0.589377
[ 7109s] 43mi5CIWi3 -0.751679 1.275031 -0.521072 0.631581
[ 7109s]
[ 7109s] @pytest.mark.parametrize(
[ 7109s] "dtype", ["int32", "int64", "uint32", "uint64", "float32", "float64"]
[ 7109s] )
[ 7109s] def test_setitem_dtype(self, dtype, float_frame):
[ 7109s] arr = np.random.randn(len(float_frame))
[ 7109s]
[ 7109s] > float_frame[dtype] = np.array(arr, dtype=dtype)
[ 7109s] E RuntimeWarning: invalid value encountered in cast
[ 7109s]
[ 7109s] pandas/tests/frame/indexing/test_setitem.py:66: RuntimeWarning
[ 7109s] __________ TestSeriesNLargestNSmallest.test_nlargest_nullable[UInt8] ___________
[ 7109s] [gw1] linux -- Python 3.11.3 /usr/bin/python3.11
[ 7109s]
[ 7109s] self = <pandas.tests.series.methods.test_nlargest.TestSeriesNLargestNSmallest object at 0xffff3ed83b10>
[ 7109s] any_numeric_ea_dtype = 'UInt8'
[ 7109s]
[ 7109s] def test_nlargest_nullable(self, any_numeric_ea_dtype):
[ 7109s] # GH#42816
[ 7109s] dtype = any_numeric_ea_dtype
[ 7109s] > arr = np.random.randn(10).astype(dtype.lower(), copy=False)
[ 7109s] E RuntimeWarning: invalid value encountered in cast
[ 7109s]
[ 7109s] pandas/tests/series/methods/test_nlargest.py:220: RuntimeWarning
```
### Expected Behavior
Tests should pass.
### Installed Versions
2.0.2 from openSUSE Tumbleweed package | test | bug testdataframesetitem test setitem dtype and testseriesnlargestnsmallest test nlargest nullable fail on pandas version checks i have checked that this issue has not already been reported i have confirmed this bug exists on the of pandas i have confirmed this bug exists on the of pandas reproducible example python run tests on opensuse tumbleweed issue description testdataframesetitem test setitem dtype and testseriesnlargestnsmallest test nlargest nullable fail on failures testdataframesetitem test setitem dtype linux python usr bin self dtype float frame a b c d pytest mark parametrize dtype def test setitem dtype self dtype float frame arr np random randn len float frame float frame np array arr dtype dtype e runtimewarning invalid value encountered in cast pandas tests frame indexing test setitem py runtimewarning testseriesnlargestnsmallest test nlargest nullable linux python usr bin self any numeric ea dtype def test nlargest nullable self any numeric ea dtype gh dtype any numeric ea dtype arr np random randn astype dtype lower copy false e runtimewarning invalid value encountered in cast pandas tests series methods test nlargest py runtimewarning expected behavior tests should pass installed versions from opensuse tumbleweed package | 1 |
254,433 | 21,786,168,001 | IssuesEvent | 2022-05-14 06:46:51 | momentum-mod/game | https://api.github.com/repos/momentum-mod/game | closed | Running zonmaker with a BSP completely locks up my system | Type: Bug Blocked: Needs testing & verification | ### Describe the bug
Trying to pass a BSP to zonmaker has it start reading it, but after a while my machine will go entirely unresponsive
### How To Reproduce
1. Open a command prompt window at `Momentum Mod\bin\win64\`
2. Pass `zonmaker.exe <BSP of your choice>`
3. Zonmaker should start reading and will crash your computer soon afterwards
### Expected Behavior
A check for a valid file type should be placed to avoid these issues. Zonmaker shouldn't cause a lock-up like this in any case
### Operating System
Windows 10 21H2
### Renderer
DX9 (Legacy) | 1.0 | Running zonmaker with a BSP completely locks up my system - ### Describe the bug
Trying to pass a BSP to zonmaker has it start reading it, but after a while my machine will go entirely unresponsive
### How To Reproduce
1. Open a command prompt window at `Momentum Mod\bin\win64\`
2. Pass `zonmaker.exe <BSP of your choice>`
3. Zonmaker should start reading and will crash your computer soon afterwards
### Expected Behavior
A check for a valid file type should be placed to avoid these issues. Zonmaker shouldn't cause a lock-up like this in any case
### Operating System
Windows 10 21H2
### Renderer
DX9 (Legacy) | test | running zonmaker with a bsp completely locks up my system describe the bug trying to pass a bsp to zonmaker has it start reading it but after a while my machine will go entirely unresponsive how to reproduce open a command prompt window at momentum mod bin pass zonmaker exe zonmaker should start reading and will crash your computer soon afterwards expected behavior a check for a valid file type should be placed to avoid these issues zonmaker shouldn t cause a lock up like this in any case operating system windows renderer legacy | 1 |
619,064 | 19,514,841,963 | IssuesEvent | 2021-12-29 08:25:15 | obsproject/obs-websocket | https://api.github.com/repos/obsproject/obs-websocket | closed | Feature Request: Machine Readable Protocol Description | Medium Priority Issue: Feature Request | ##### Issue type
- Feature request
##### Description
While developing my [Java Client Library](https://github.com/harm27/obs-java-client) for OBS Websocket, quickly noticed a lot of overhead in coding every event and request manualy, what would increase the time in getting changes in existing or new Events or Requests added to my Client Library.
To solve that, i wrote a Maven plugin for my Library that uses the [comments.json](https://github.com/Palakis/obs-websocket/blob/4.x-current/docs/generated/comments.json) file of the current main branch to generate a lot of the classes so that when a new OBS Websocket version would be released, it would require less work to get a new client library version released, so that a user of my library would have a new version available quickly.
But the current solution has some flaws, since the comments.json file isn't designed for this use case, but also some other problems:
- Mix of naming styles (Already on the list for 5.0 i saw).
- Categories like Recording, Streaming, etc. are not in one array in that file so that i need to add them one by one.
- Multi-layered objects sometimes are mentioned on there own and as part of there sub properties and sometimes only as part of there sub properties. (Mightly some what solved by transforming multi-level JSON into single-level, that is on the list for 5.0)
- Missing info about Base-Event, -Request and -Response
And when the HTTP Endpoint becomes available, it would be nice if that would also have a Machine Readable Protocol Description.
Or when other message solutions then JSON would become available like MessagePack i saw being mentioned, that there would be a Machine Readable Protocol Description. | 1.0 | Feature Request: Machine Readable Protocol Description - ##### Issue type
- Feature request
##### Description
While developing my [Java Client Library](https://github.com/harm27/obs-java-client) for OBS Websocket, quickly noticed a lot of overhead in coding every event and request manualy, what would increase the time in getting changes in existing or new Events or Requests added to my Client Library.
To solve that, i wrote a Maven plugin for my Library that uses the [comments.json](https://github.com/Palakis/obs-websocket/blob/4.x-current/docs/generated/comments.json) file of the current main branch to generate a lot of the classes so that when a new OBS Websocket version would be released, it would require less work to get a new client library version released, so that a user of my library would have a new version available quickly.
But the current solution has some flaws, since the comments.json file isn't designed for this use case, but also some other problems:
- Mix of naming styles (Already on the list for 5.0 i saw).
- Categories like Recording, Streaming, etc. are not in one array in that file so that i need to add them one by one.
- Multi-layered objects sometimes are mentioned on there own and as part of there sub properties and sometimes only as part of there sub properties. (Mightly some what solved by transforming multi-level JSON into single-level, that is on the list for 5.0)
- Missing info about Base-Event, -Request and -Response
And when the HTTP Endpoint becomes available, it would be nice if that would also have a Machine Readable Protocol Description.
Or when other message solutions then JSON would become available like MessagePack i saw being mentioned, that there would be a Machine Readable Protocol Description. | non_test | feature request machine readable protocol description issue type feature request description while developing my for obs websocket quickly noticed a lot of overhead in coding every event and request manualy what would increase the time in getting changes in existing or new events or requests added to my client library to solve that i wrote a maven plugin for my library that uses the file of the current main branch to generate a lot of the classes so that when a new obs websocket version would be released it would require less work to get a new client library version released so that a user of my library would have a new version available quickly but the current solution has some flaws since the comments json file isn t designed for this use case but also some other problems mix of naming styles already on the list for i saw categories like recording streaming etc are not in one array in that file so that i need to add them one by one multi layered objects sometimes are mentioned on there own and as part of there sub properties and sometimes only as part of there sub properties mightly some what solved by transforming multi level json into single level that is on the list for missing info about base event request and response and when the http endpoint becomes available it would be nice if that would also have a machine readable protocol description or when other message solutions then json would become available like messagepack i saw being mentioned that there would be a machine readable protocol description | 0 |
32,599 | 8,896,272,178 | IssuesEvent | 2019-01-16 10:58:48 | bbc/simorgh | https://api.github.com/repos/bbc/simorgh | opened | Lighthouse randomly fails the build | Refinement Needed alpha-3 bug build-pipeline | **Describe the bug**
Lighthouse tests run on Travis. Occasionally, Lighthouse returns `null` instead of a performance value (e.g. `82.4`). This fails the build.
**To Reproduce**
1. Re-run Travis on `latest`
2. ...several times....
3. ...it will eventually fail because of Lighthouse
**Expected behavior**
The build should consistently pass.
**Additional context**
Suggestion: we could try re-running the Lighthouse tests continually until a non-null value is returned.
- [x] Initially labelled with ["bug"](https://github.com/BBC-News/simorgh/labels/bug)
| 1.0 | Lighthouse randomly fails the build - **Describe the bug**
Lighthouse tests run on Travis. Occasionally, Lighthouse returns `null` instead of a performance value (e.g. `82.4`). This fails the build.
**To Reproduce**
1. Re-run Travis on `latest`
2. ...several times....
3. ...it will eventually fail because of Lighthouse
**Expected behavior**
The build should consistently pass.
**Additional context**
Suggestion: we could try re-running the Lighthouse tests continually until a non-null value is returned.
- [x] Initially labelled with ["bug"](https://github.com/BBC-News/simorgh/labels/bug)
| non_test | lighthouse randomly fails the build describe the bug lighthouse tests run on travis occasionally lighthouse returns null instead of a performance value e g this fails the build to reproduce re run travis on latest several times it will eventually fail because of lighthouse expected behavior the build should consistently pass additional context suggestion we could try re running the lighthouse tests continually until a non null value is returned initially labelled with | 0 |
197,938 | 14,950,405,234 | IssuesEvent | 2021-01-26 13:02:37 | fetchai/agents-aea | https://api.github.com/repos/fetchai/agents-aea | closed | Add protobuf linter | enhancement test | **Is your feature request related to a problem? Please describe.**
Currently, protobuf files are not linted.
**Describe the solution you'd like**
Add https://github.com/yoheimuta/protolint | 1.0 | Add protobuf linter - **Is your feature request related to a problem? Please describe.**
Currently, protobuf files are not linted.
**Describe the solution you'd like**
Add https://github.com/yoheimuta/protolint | test | add protobuf linter is your feature request related to a problem please describe currently protobuf files are not linted describe the solution you d like add | 1 |
1,801 | 6,575,923,403 | IssuesEvent | 2017-09-11 17:51:04 | ansible/ansible-modules-core | https://api.github.com/repos/ansible/ansible-modules-core | closed | mysql_user host_all arguments conversion string formatting error | affects_2.1 bug_report waiting_on_maintainer | <!--- Verify first that your issue/request is not already reported in GitHub -->
##### ISSUE TYPE
<!--- Pick one below and delete the rest: -->
- Bug Report
##### COMPONENT NAME
<!--- Name of the plugin/module/task -->
mysql_user
##### ANSIBLE VERSION
<!--- Paste verbatim output from “ansible --version” between quotes below -->
```
ansible 2.1.1.0
config file = /etc/ansible/ansible.cfg
configured module search path = Default w/o overrides
```
##### CONFIGURATION
<!---
Mention any settings you have changed/added/removed in ansible.cfg
(or using the ANSIBLE_* environment variables).
-->
##### OS / ENVIRONMENT
<!---
Mention the OS you are running Ansible from, and the OS you are
managing, or say “N/A” for anything that is not platform-specific.
-->
Ubuntu Trusty/Xenial
##### SUMMARY
Attempting to use the mysql_user module to change the password for the root user while using the 'host_all: yes' instead of iterating all hosts with 'host: "{{ item }}"' + 'with_items' results in error "not all arguments converted during string formatting"
##### STEPS TO REPRODUCE
<!---
For bugs, show exactly how to reproduce the problem.
For new features, show how the feature would be used.
-->
<!--- Paste example playbooks or commands between quotes below -->
```
- name: Change password
mysql_user:
login_user: "root"
login_password: "abc"
name: "root"
password: "xyz"
host_all: yes
```
or
```
- name: Change password
mysql_user:
name: "root"
password: "xyz"
host_all: yes
```
<!--- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- What did you expect to happen when running the steps above? -->
The mysql_user should be able to iterate through mysql hosts and change the password of the root user against hosts in mysql similar to when using the 'host: "{{ item }}"' + 'with_items'
##### ACTUAL RESULTS
<!--- What actually happened? If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes below -->
```
fatal: [192.168.1.127]: FAILED! => {"changed": false, "failed": true, "invocation": {"module_name": "mysql_user"}, "module_stderr": "OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 19: Applying options for *\r\ndebug1: auto-mux: Trying existing master\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug2: mux_client_hello_exchange: master version 4\r\ndebug3: mux_client_forwards: request forwardings: 0 local, 0 remote\r\ndebug3: mux_client_request_session: entering\r\ndebug3: mux_client_request_alive: entering\r\ndebug3: mux_client_request_alive: done pid = 27404\r\ndebug3: mux_client_request_session: session request sent\r\ndebug1: mux_client_request_session: master session id: 2\r\ndebug3: mux_client_read_packet: read header failed: Broken pipe\r\ndebug2: Received exit status from master 0\r\nShared connection to 192.168.1.127 closed.\r\n", "module_stdout": "\r\nTraceback (most recent call last):\r\n File \"/tmp/ansible_BJCDub/ansible_module_mysql_user.py\", line 582, in <module>\r\n main()\r\n File \"/tmp/ansible_BJCDub/ansible_module_mysql_user.py\", line 554, in main\r\n if user_exists(cursor, user, host, host_all):\r\n File \"/tmp/ansible_BJCDub/ansible_module_mysql_user.py\", line 216, in user_exists\r\n cursor.execute(\"SELECT count(*) FROM user WHERE user = %s\", user)\r\n File \"/usr/local/lib/python2.7/dist-packages/MySQLdb/cursors.py\", line 187, in execute\r\n query = query % tuple([db.literal(item) for item in args])\r\nTypeError: not all arguments converted during string formatting\r\n", "msg": "MODULE FAILURE", "parsed": false}
```
| True | mysql_user host_all arguments conversion string formatting error - <!--- Verify first that your issue/request is not already reported in GitHub -->
##### ISSUE TYPE
<!--- Pick one below and delete the rest: -->
- Bug Report
##### COMPONENT NAME
<!--- Name of the plugin/module/task -->
mysql_user
##### ANSIBLE VERSION
<!--- Paste verbatim output from “ansible --version” between quotes below -->
```
ansible 2.1.1.0
config file = /etc/ansible/ansible.cfg
configured module search path = Default w/o overrides
```
##### CONFIGURATION
<!---
Mention any settings you have changed/added/removed in ansible.cfg
(or using the ANSIBLE_* environment variables).
-->
##### OS / ENVIRONMENT
<!---
Mention the OS you are running Ansible from, and the OS you are
managing, or say “N/A” for anything that is not platform-specific.
-->
Ubuntu Trusty/Xenial
##### SUMMARY
Attempting to use the mysql_user module to change the password for the root user while using the 'host_all: yes' instead of iterating all hosts with 'host: "{{ item }}"' + 'with_items' results in error "not all arguments converted during string formatting"
##### STEPS TO REPRODUCE
<!---
For bugs, show exactly how to reproduce the problem.
For new features, show how the feature would be used.
-->
<!--- Paste example playbooks or commands between quotes below -->
```
- name: Change password
mysql_user:
login_user: "root"
login_password: "abc"
name: "root"
password: "xyz"
host_all: yes
```
or
```
- name: Change password
mysql_user:
name: "root"
password: "xyz"
host_all: yes
```
<!--- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- What did you expect to happen when running the steps above? -->
The mysql_user should be able to iterate through mysql hosts and change the password of the root user against hosts in mysql similar to when using the 'host: "{{ item }}"' + 'with_items'
##### ACTUAL RESULTS
<!--- What actually happened? If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes below -->
```
fatal: [192.168.1.127]: FAILED! => {"changed": false, "failed": true, "invocation": {"module_name": "mysql_user"}, "module_stderr": "OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 19: Applying options for *\r\ndebug1: auto-mux: Trying existing master\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug2: mux_client_hello_exchange: master version 4\r\ndebug3: mux_client_forwards: request forwardings: 0 local, 0 remote\r\ndebug3: mux_client_request_session: entering\r\ndebug3: mux_client_request_alive: entering\r\ndebug3: mux_client_request_alive: done pid = 27404\r\ndebug3: mux_client_request_session: session request sent\r\ndebug1: mux_client_request_session: master session id: 2\r\ndebug3: mux_client_read_packet: read header failed: Broken pipe\r\ndebug2: Received exit status from master 0\r\nShared connection to 192.168.1.127 closed.\r\n", "module_stdout": "\r\nTraceback (most recent call last):\r\n File \"/tmp/ansible_BJCDub/ansible_module_mysql_user.py\", line 582, in <module>\r\n main()\r\n File \"/tmp/ansible_BJCDub/ansible_module_mysql_user.py\", line 554, in main\r\n if user_exists(cursor, user, host, host_all):\r\n File \"/tmp/ansible_BJCDub/ansible_module_mysql_user.py\", line 216, in user_exists\r\n cursor.execute(\"SELECT count(*) FROM user WHERE user = %s\", user)\r\n File \"/usr/local/lib/python2.7/dist-packages/MySQLdb/cursors.py\", line 187, in execute\r\n query = query % tuple([db.literal(item) for item in args])\r\nTypeError: not all arguments converted during string formatting\r\n", "msg": "MODULE FAILURE", "parsed": false}
```
| non_test | mysql user host all arguments conversion string formatting error issue type bug report component name mysql user ansible version ansible config file etc ansible ansible cfg configured module search path default w o overrides configuration mention any settings you have changed added removed in ansible cfg or using the ansible environment variables os environment mention the os you are running ansible from and the os you are managing or say “n a” for anything that is not platform specific ubuntu trusty xenial summary attempting to use the mysql user module to change the password for the root user while using the host all yes instead of iterating all hosts with host item with items results in error not all arguments converted during string formatting steps to reproduce for bugs show exactly how to reproduce the problem for new features show how the feature would be used name change password mysql user login user root login password abc name root password xyz host all yes or name change password mysql user name root password xyz host all yes expected results the mysql user should be able to iterate through mysql hosts and change the password of the root user against hosts in mysql similar to when using the host item with items actual results fatal failed changed false failed true invocation module name mysql user module stderr openssh openssl jan r reading configuration data etc ssh ssh config r etc ssh ssh config line applying options for r auto mux trying existing master r fd setting o nonblock r mux client hello exchange master version r mux client forwards request forwardings local remote r mux client request session entering r mux client request alive entering r mux client request alive done pid r mux client request session session request sent r mux client request session master session id r mux client read packet read header failed broken pipe r received exit status from master r nshared connection to closed r n module stdout r ntraceback most recent call last r n file tmp ansible bjcdub ansible module mysql user py line in r n main r n file tmp ansible bjcdub ansible module mysql user py line in main r n if user exists cursor user host host all r n file tmp ansible bjcdub ansible module mysql user py line in user exists r n cursor execute select count from user where user s user r n file usr local lib dist packages mysqldb cursors py line in execute r n query query tuple r ntypeerror not all arguments converted during string formatting r n msg module failure parsed false | 0 |
486,801 | 14,014,647,219 | IssuesEvent | 2020-10-29 12:14:14 | AY2021S1-CS2103T-W16-3/tp | https://api.github.com/repos/AY2021S1-CS2103T-W16-3/tp | opened | Add clear command confirmation | priority.medium :2nd_place_medal: type.enhancement :+1: | Currently the `clear` command will immediately wipe all data from the finance tracker, which may be annoying if the user has already accumulated some expense and income data and accidentally enters the command.
Clearing the finance tracker should take at least two actions from the user to confirm their intentions, perhaps either with a popup dialog or requiring the command to be entered twice. | 1.0 | Add clear command confirmation - Currently the `clear` command will immediately wipe all data from the finance tracker, which may be annoying if the user has already accumulated some expense and income data and accidentally enters the command.
Clearing the finance tracker should take at least two actions from the user to confirm their intentions, perhaps either with a popup dialog or requiring the command to be entered twice. | non_test | add clear command confirmation currently the clear command will immediately wipe all data from the finance tracker which may be annoying if the user has already accumulated some expense and income data and accidentally enters the command clearing the finance tracker should take at least two actions from the user to confirm their intentions perhaps either with a popup dialog or requiring the command to be entered twice | 0 |
98,251 | 8,675,388,041 | IssuesEvent | 2018-11-30 10:43:54 | humera987/FXLabs-Test-Automation | https://api.github.com/repos/humera987/FXLabs-Test-Automation | reopened | FXLabs Testing 30 : ApiV1TestSuitesIdTestSuiteSearchGetQueryParamCategoryEmptyValue | FXLabs Testing 30 | Project : FXLabs Testing 30
Job : UAT 1
Env : UAT 1
Region : US_WEST
Result : fail
Status Code : 404
Headers : {X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Set-Cookie=[SESSION=NDY2MTVkMzQtY2E2MS00MDRiLWFhYTktMDdlMDAwZGJlNWQ4; Path=/; HttpOnly], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Fri, 30 Nov 2018 10:39:29 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/test-suites/QQIrMicr/test-suite/search?category=
Request :
Response :
{
"timestamp" : "2018-11-30T10:39:30.630+0000",
"status" : 404,
"error" : "Not Found",
"message" : "No message available",
"path" : "/api/v1/api/v1/test-suites/QQIrMicr/test-suite/search"
}
Logs :
Assertion [@StatusCode != 401] resolved-to [404 != 401] result [Passed]Assertion [@StatusCode != 500] resolved-to [404 != 500] result [Passed]Assertion [@StatusCode != 404] resolved-to [404 != 404] result [Failed]Assertion [@StatusCode != 200] resolved-to [404 != 200] result [Passed]
--- FX Bot --- | 1.0 | FXLabs Testing 30 : ApiV1TestSuitesIdTestSuiteSearchGetQueryParamCategoryEmptyValue - Project : FXLabs Testing 30
Job : UAT 1
Env : UAT 1
Region : US_WEST
Result : fail
Status Code : 404
Headers : {X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Set-Cookie=[SESSION=NDY2MTVkMzQtY2E2MS00MDRiLWFhYTktMDdlMDAwZGJlNWQ4; Path=/; HttpOnly], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Fri, 30 Nov 2018 10:39:29 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/test-suites/QQIrMicr/test-suite/search?category=
Request :
Response :
{
"timestamp" : "2018-11-30T10:39:30.630+0000",
"status" : 404,
"error" : "Not Found",
"message" : "No message available",
"path" : "/api/v1/api/v1/test-suites/QQIrMicr/test-suite/search"
}
Logs :
Assertion [@StatusCode != 401] resolved-to [404 != 401] result [Passed]Assertion [@StatusCode != 500] resolved-to [404 != 500] result [Passed]Assertion [@StatusCode != 404] resolved-to [404 != 404] result [Failed]Assertion [@StatusCode != 200] resolved-to [404 != 200] result [Passed]
--- FX Bot --- | test | fxlabs testing project fxlabs testing job uat env uat region us west result fail status code headers x content type options x xss protection cache control pragma expires x frame options set cookie content type transfer encoding date endpoint request response timestamp status error not found message no message available path api api test suites qqirmicr test suite search logs assertion resolved to result assertion resolved to result assertion resolved to result assertion resolved to result fx bot | 1 |
301,196 | 26,026,318,020 | IssuesEvent | 2022-12-21 16:38:27 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | roachtest: ledger/nodes=6/multi-az failed | C-test-failure O-robot O-roachtest branch-master release-blocker | roachtest.ledger/nodes=6/multi-az [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8046095?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8046095?buildTab=artifacts#/ledger/nodes=6/multi-az) on master @ [10266a323f94c3cf397d5de590e512d987e63e22](https://github.com/cockroachdb/cockroach/commits/10266a323f94c3cf397d5de590e512d987e63e22):
```
test artifacts and logs in: /artifacts/ledger/nodes=6/multi-az/run_1
(test_impl.go:291).Fatal: output in run_163643.333865619_n7_workload_run_ledger: ./workload run ledger --init --histograms=perf/stats.json --concurrency=192 --duration=10m {pgurl:1-2} returned: COMMAND_PROBLEM: exit status 1
(test_impl.go:291).Fatal: monitor failure: monitor task failed: t.Fatal() was called
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=16</code>
, <code>ROACHTEST_encrypted=false</code>
, <code>ROACHTEST_fs=ext4</code>
, <code>ROACHTEST_localSSD=true</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/kv-triage
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*ledger/nodes=6/multi-az.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| 2.0 | roachtest: ledger/nodes=6/multi-az failed - roachtest.ledger/nodes=6/multi-az [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8046095?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8046095?buildTab=artifacts#/ledger/nodes=6/multi-az) on master @ [10266a323f94c3cf397d5de590e512d987e63e22](https://github.com/cockroachdb/cockroach/commits/10266a323f94c3cf397d5de590e512d987e63e22):
```
test artifacts and logs in: /artifacts/ledger/nodes=6/multi-az/run_1
(test_impl.go:291).Fatal: output in run_163643.333865619_n7_workload_run_ledger: ./workload run ledger --init --histograms=perf/stats.json --concurrency=192 --duration=10m {pgurl:1-2} returned: COMMAND_PROBLEM: exit status 1
(test_impl.go:291).Fatal: monitor failure: monitor task failed: t.Fatal() was called
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=16</code>
, <code>ROACHTEST_encrypted=false</code>
, <code>ROACHTEST_fs=ext4</code>
, <code>ROACHTEST_localSSD=true</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/kv-triage
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*ledger/nodes=6/multi-az.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| test | roachtest ledger nodes multi az failed roachtest ledger nodes multi az with on master test artifacts and logs in artifacts ledger nodes multi az run test impl go fatal output in run workload run ledger workload run ledger init histograms perf stats json concurrency duration pgurl returned command problem exit status test impl go fatal monitor failure monitor task failed t fatal was called parameters roachtest cloud gce roachtest cpu roachtest encrypted false roachtest fs roachtest localssd true roachtest ssd help see see cc cockroachdb kv triage | 1 |
76,450 | 7,529,585,092 | IssuesEvent | 2018-04-14 06:53:58 | amawai/android-wikipedia-390 | https://api.github.com/repos/amawai/android-wikipedia-390 | closed | Article Search by Image | search-by-image story test | As a user, I would like to be able to search for an article based on an image capture my camera.
- [x] [#96] Addition camera icon + open camera on click
- [x] [#97] Send picture taken by user through google api
- [x] [#98] Interpret results from api and redirect to relevant articles (show user list of suggested/most relevant articles)
- [x] Unit/UI Tests
[Story Points: 8 points]
[Risk: High] - see task issues for specific risk assessment
[Priority: High] - same for all tasks
| 1.0 | Article Search by Image - As a user, I would like to be able to search for an article based on an image capture my camera.
- [x] [#96] Addition camera icon + open camera on click
- [x] [#97] Send picture taken by user through google api
- [x] [#98] Interpret results from api and redirect to relevant articles (show user list of suggested/most relevant articles)
- [x] Unit/UI Tests
[Story Points: 8 points]
[Risk: High] - see task issues for specific risk assessment
[Priority: High] - same for all tasks
| test | article search by image as a user i would like to be able to search for an article based on an image capture my camera addition camera icon open camera on click send picture taken by user through google api interpret results from api and redirect to relevant articles show user list of suggested most relevant articles unit ui tests see task issues for specific risk assessment same for all tasks | 1 |
165,890 | 14,014,555,808 | IssuesEvent | 2020-10-29 12:05:59 | molgenis/data-transform-vkgl | https://api.github.com/repos/molgenis/data-transform-vkgl | closed | Missing documentation for hgvs translator flags | documentation | Documentation is missing for the `keep_left_anchor` query string parameter.
Documentation might be missing for other flags as well. | 1.0 | Missing documentation for hgvs translator flags - Documentation is missing for the `keep_left_anchor` query string parameter.
Documentation might be missing for other flags as well. | non_test | missing documentation for hgvs translator flags documentation is missing for the keep left anchor query string parameter documentation might be missing for other flags as well | 0 |
631,945 | 20,165,552,455 | IssuesEvent | 2022-02-10 03:41:42 | choderalab/perses | https://api.github.com/repos/choderalab/perses | opened | perses app that uses any MultiStateSampler (including ReplicaExchangeSampler and subclasses) should minimize before simulation | bug :bug: priority: high effort: low | Right now, none of the perses apps that use`ReplicaExchangeSampler` and friends call `sampler.minmize()` before they start simulation. We should change this, since it is essential for ensuring stability of the resulting simulations.
Minimization should occur by default, but should be something we can override via the API or YAML. | 1.0 | perses app that uses any MultiStateSampler (including ReplicaExchangeSampler and subclasses) should minimize before simulation - Right now, none of the perses apps that use`ReplicaExchangeSampler` and friends call `sampler.minmize()` before they start simulation. We should change this, since it is essential for ensuring stability of the resulting simulations.
Minimization should occur by default, but should be something we can override via the API or YAML. | non_test | perses app that uses any multistatesampler including replicaexchangesampler and subclasses should minimize before simulation right now none of the perses apps that use replicaexchangesampler and friends call sampler minmize before they start simulation we should change this since it is essential for ensuring stability of the resulting simulations minimization should occur by default but should be something we can override via the api or yaml | 0 |
218,286 | 7,331,037,696 | IssuesEvent | 2018-03-05 12:04:52 | montera34/globalrec | https://api.github.com/repos/montera34/globalrec | opened | Problems in WAW submit form in Spanish | bug priority question | When submitting a new organization in Spanish (http://globalrec.org/es/rem/anade-organizacion/), something is not working and returns "har".
Code available at https://github.com/montera34/globalrec/blob/master/functions.php#L2054
What is the code below doing?
```
if ( !array_key_exists('globalrec-form-waw-submit', $_POST) ) {
globalrec_waw_form();
return;
} elseif ( sanitize_text_field( $_POST['globalrec-form-waw-submit'] ) != 'Send' ) {
globalrec_waw_form();
echo "har";
return;
}
``` | 1.0 | Problems in WAW submit form in Spanish - When submitting a new organization in Spanish (http://globalrec.org/es/rem/anade-organizacion/), something is not working and returns "har".
Code available at https://github.com/montera34/globalrec/blob/master/functions.php#L2054
What is the code below doing?
```
if ( !array_key_exists('globalrec-form-waw-submit', $_POST) ) {
globalrec_waw_form();
return;
} elseif ( sanitize_text_field( $_POST['globalrec-form-waw-submit'] ) != 'Send' ) {
globalrec_waw_form();
echo "har";
return;
}
``` | non_test | problems in waw submit form in spanish when submitting a new organization in spanish something is not working and returns har code available at what is the code below doing if array key exists globalrec form waw submit post globalrec waw form return elseif sanitize text field post send globalrec waw form echo har return | 0 |
183,111 | 14,929,990,295 | IssuesEvent | 2021-01-25 01:32:07 | ernieIzde8ski/ratbot | https://api.github.com/repos/ernieIzde8ski/ratbot | opened | Change The README.md | documentation | IDK Man . I Feel Like I Can Only Read It Because I Am The Writer. Consider Making It Not Informal As All Hell. Or Not Because It's Kinda Still Ratbot Doe | 1.0 | Change The README.md - IDK Man . I Feel Like I Can Only Read It Because I Am The Writer. Consider Making It Not Informal As All Hell. Or Not Because It's Kinda Still Ratbot Doe | non_test | change the readme md idk man i feel like i can only read it because i am the writer consider making it not informal as all hell or not because it s kinda still ratbot doe | 0 |
373,951 | 26,093,293,439 | IssuesEvent | 2022-12-26 14:52:42 | FuelLabs/fuel-indexer | https://api.github.com/repos/FuelLabs/fuel-indexer | closed | Create a fuel-indexer architecture diagram | documentation good first issue | - There is little to no documentation for the fuel-indexer project.
- We'd like to create an architecture diagram that shows new/existing users how the fuel-indexer service is architected | 1.0 | Create a fuel-indexer architecture diagram - - There is little to no documentation for the fuel-indexer project.
- We'd like to create an architecture diagram that shows new/existing users how the fuel-indexer service is architected | non_test | create a fuel indexer architecture diagram there is little to no documentation for the fuel indexer project we d like to create an architecture diagram that shows new existing users how the fuel indexer service is architected | 0 |
18,054 | 3,372,734,106 | IssuesEvent | 2015-11-24 01:27:38 | mozilla/webmaker-browser | https://api.github.com/repos/mozilla/webmaker-browser | closed | Post promo guidelines for Webmaker.org to build.webmaker.org | design | Webmaker.org includes a spot for promotion of partners and activities. We have some draft guidelines (https://github.com/mozilla/webmaker-desktop/issues/68#issuecomment-108458057) that should be finalized and posted to build.webmaker.org for posterity. | 1.0 | Post promo guidelines for Webmaker.org to build.webmaker.org - Webmaker.org includes a spot for promotion of partners and activities. We have some draft guidelines (https://github.com/mozilla/webmaker-desktop/issues/68#issuecomment-108458057) that should be finalized and posted to build.webmaker.org for posterity. | non_test | post promo guidelines for webmaker org to build webmaker org webmaker org includes a spot for promotion of partners and activities we have some draft guidelines that should be finalized and posted to build webmaker org for posterity | 0 |
362,150 | 10,723,518,725 | IssuesEvent | 2019-10-27 19:20:11 | nuriu/cemiyet-backend | https://api.github.com/repos/nuriu/cemiyet-backend | closed | Create database context for application. | Priority: High Project: Persistence Status: In Progress Type: Epic | - [x] ~#4~
- [x] ~#5~
- [x] ~#6~
- [x] Implement custom entity type configuration classes for both entities.
- [x] #3
- [x] At startup; ensure it creates database if it doesn't exists and applies any migrations that didn't applied. | 1.0 | Create database context for application. - - [x] ~#4~
- [x] ~#5~
- [x] ~#6~
- [x] Implement custom entity type configuration classes for both entities.
- [x] #3
- [x] At startup; ensure it creates database if it doesn't exists and applies any migrations that didn't applied. | non_test | create database context for application implement custom entity type configuration classes for both entities at startup ensure it creates database if it doesn t exists and applies any migrations that didn t applied | 0 |
180,452 | 13,932,266,959 | IssuesEvent | 2020-10-22 06:58:05 | OpenMined/PySyft | https://api.github.com/repos/OpenMined/PySyft | closed | Add torch.Tensor.sub_ to allowlist and test suite | Priority: 2 - High :cold_sweat: Severity: 3 - Medium :unamused: Status: Available :wave: Type: New Feature :heavy_plus_sign: Type: Testing :test_tube: |
# Description
This issue is a part of Syft 0.3.0 Epic 2: https://github.com/OpenMined/PySyft/issues/3696
In this issue, you will be adding support for remote execution of the torch.Tensor.sub_
method or property. This might be a really small project (literally a one-liner) or
it might require adding significant functionality to PySyft OR to the testing suite
in order to make sure the feature is both functional and tested.
## Step 0: Run tests and ./scripts/pre_commit.sh
Before you get started with this project, let's make sure you have everything building and testing
correctly. Clone the codebase and run:
```pip uninstall syft```
followed by
```pip install -e .```
Then run the pre-commit file (which will also run the tests)
```./scripts/pre_commit.sh```
If all of these tests pass, continue on. If not, make sure you have all the
dependencies in requirements.txt installed, etc.
## Step 1: Uncomment your method in the allowlist.py file
Inside [allowlist.py](https://github.com/OpenMined/PySyft/blob/syft_0.3.0/src/syft/lib/torch/allowlist.py) you will find a huge dictionary of methods. Find your method and uncomment the line its on. At the time
of writing this Issue (WARNING: THIS MAY HAVE CHANGED) the dictionary maps from the
string name of the method (in your case 'torch.Tensor.sub_') to the string representation
of the type the method returns.
## Step 2: Run Unit Tests
Run the following:
```python setup.py test```
And wait to see if some of the tests fail. Why might the tests fail now? I'm so glad you asked!
https://github.com/OpenMined/PySyft/blob/syft_0.3.0/tests/syft/lib/torch/tensor/tensor_remote_method_api_suite_test.py
In this file you'll find the torch method test suite. It AUTOMATICALLY loads all methods
from the allowlist.py file you modified in the previous step. It attempts to test them.
# Step 3: If you get a Failing Test
If you get a failing test, this could be for one of a few reasons:
### Reason 1 - The testing suite passed in non-compatible arguments
The testing suite is pretty dumb. It literally just has a permutation of possible
arguments to pass into every method on torch tensors. So, if one of those permutations
doesn't work for your method (aka... perhaps it tries to call your method without
any arguments but torch.Tensor.sub_ actually requires some) then the test will
fail if the error hasn't been seen before.
If this happens - don't worry! Just look inside the only test in that file and look
for the huge lists of error types to ignore. Add your error to the list and keep
going!!!
*WARNING:* make sure that the testing suite actually tests your method via remote
execution once you've gotten all the tests passing. Aka - if the testing suite
doesn't have ANY matching argument permutations for your method, then you're
literally creating a bunch of unit tests that do absolutely nothing. If this is the
case, then ADD MORE ARGUMENT TYPES TO THE TESTING SUITE so that your argument
gets run via remote execution. DO NOT CLOSE THIS ISSUE until you can verify that
torch.Tensor.sub_ is actually executed remotely inside of a unit tests (and not
skipped). Aka - at least one of the test_all_allowlisted_tensor_methods_work_remotely_on_all_types
unit tests with your method should run ALL THE WAY TO THE END (instead of skipping
the last part.)
*Note:* adding another argument type might require some serialization work if
we don't support arguments of that type yet. If so, this is your job to add it
to the protobuf files in order to close this issue!
### Reason 2 - torch.Tensor.sub_ returns a non-supported type
If this happens, you've got a little bit of work in front of you. We don't have
pointer objects to very many remote object types. So, if your method returns anything
other than a single tensor, you probably need to add support for the type it returns
(Such as a bool, None, int, or other types).
*IMPORTANT:* do NOT return the value itself to the end user!!! Return a pointer object
to that type!
*NOTE:* at the time of writing - there are several core pieces of Syft not yet working
to allow you to return any type other than a torch tensor. If you're not comfortable
investigating what those might be - skip this issue and try again later once
someone else has solved these issues.
### Reason 3 - There's something else broken
Chase those stack traces! Talk to friends in Slack. Look at how other methods are supported.
This is a challenging project in a fast moving codebase!
And don't forget - if this project seems to complex - there are plenty of others that
might be easier.
| 2.0 | Add torch.Tensor.sub_ to allowlist and test suite -
# Description
This issue is a part of Syft 0.3.0 Epic 2: https://github.com/OpenMined/PySyft/issues/3696
In this issue, you will be adding support for remote execution of the torch.Tensor.sub_
method or property. This might be a really small project (literally a one-liner) or
it might require adding significant functionality to PySyft OR to the testing suite
in order to make sure the feature is both functional and tested.
## Step 0: Run tests and ./scripts/pre_commit.sh
Before you get started with this project, let's make sure you have everything building and testing
correctly. Clone the codebase and run:
```pip uninstall syft```
followed by
```pip install -e .```
Then run the pre-commit file (which will also run the tests)
```./scripts/pre_commit.sh```
If all of these tests pass, continue on. If not, make sure you have all the
dependencies in requirements.txt installed, etc.
## Step 1: Uncomment your method in the allowlist.py file
Inside [allowlist.py](https://github.com/OpenMined/PySyft/blob/syft_0.3.0/src/syft/lib/torch/allowlist.py) you will find a huge dictionary of methods. Find your method and uncomment the line its on. At the time
of writing this Issue (WARNING: THIS MAY HAVE CHANGED) the dictionary maps from the
string name of the method (in your case 'torch.Tensor.sub_') to the string representation
of the type the method returns.
## Step 2: Run Unit Tests
Run the following:
```python setup.py test```
And wait to see if some of the tests fail. Why might the tests fail now? I'm so glad you asked!
https://github.com/OpenMined/PySyft/blob/syft_0.3.0/tests/syft/lib/torch/tensor/tensor_remote_method_api_suite_test.py
In this file you'll find the torch method test suite. It AUTOMATICALLY loads all methods
from the allowlist.py file you modified in the previous step. It attempts to test them.
# Step 3: If you get a Failing Test
If you get a failing test, this could be for one of a few reasons:
### Reason 1 - The testing suite passed in non-compatible arguments
The testing suite is pretty dumb. It literally just has a permutation of possible
arguments to pass into every method on torch tensors. So, if one of those permutations
doesn't work for your method (aka... perhaps it tries to call your method without
any arguments but torch.Tensor.sub_ actually requires some) then the test will
fail if the error hasn't been seen before.
If this happens - don't worry! Just look inside the only test in that file and look
for the huge lists of error types to ignore. Add your error to the list and keep
going!!!
*WARNING:* make sure that the testing suite actually tests your method via remote
execution once you've gotten all the tests passing. Aka - if the testing suite
doesn't have ANY matching argument permutations for your method, then you're
literally creating a bunch of unit tests that do absolutely nothing. If this is the
case, then ADD MORE ARGUMENT TYPES TO THE TESTING SUITE so that your argument
gets run via remote execution. DO NOT CLOSE THIS ISSUE until you can verify that
torch.Tensor.sub_ is actually executed remotely inside of a unit tests (and not
skipped). Aka - at least one of the test_all_allowlisted_tensor_methods_work_remotely_on_all_types
unit tests with your method should run ALL THE WAY TO THE END (instead of skipping
the last part.)
*Note:* adding another argument type might require some serialization work if
we don't support arguments of that type yet. If so, this is your job to add it
to the protobuf files in order to close this issue!
### Reason 2 - torch.Tensor.sub_ returns a non-supported type
If this happens, you've got a little bit of work in front of you. We don't have
pointer objects to very many remote object types. So, if your method returns anything
other than a single tensor, you probably need to add support for the type it returns
(Such as a bool, None, int, or other types).
*IMPORTANT:* do NOT return the value itself to the end user!!! Return a pointer object
to that type!
*NOTE:* at the time of writing - there are several core pieces of Syft not yet working
to allow you to return any type other than a torch tensor. If you're not comfortable
investigating what those might be - skip this issue and try again later once
someone else has solved these issues.
### Reason 3 - There's something else broken
Chase those stack traces! Talk to friends in Slack. Look at how other methods are supported.
This is a challenging project in a fast moving codebase!
And don't forget - if this project seems to complex - there are plenty of others that
might be easier.
| test | add torch tensor sub to allowlist and test suite description this issue is a part of syft epic in this issue you will be adding support for remote execution of the torch tensor sub method or property this might be a really small project literally a one liner or it might require adding significant functionality to pysyft or to the testing suite in order to make sure the feature is both functional and tested step run tests and scripts pre commit sh before you get started with this project let s make sure you have everything building and testing correctly clone the codebase and run pip uninstall syft followed by pip install e then run the pre commit file which will also run the tests scripts pre commit sh if all of these tests pass continue on if not make sure you have all the dependencies in requirements txt installed etc step uncomment your method in the allowlist py file inside you will find a huge dictionary of methods find your method and uncomment the line its on at the time of writing this issue warning this may have changed the dictionary maps from the string name of the method in your case torch tensor sub to the string representation of the type the method returns step run unit tests run the following python setup py test and wait to see if some of the tests fail why might the tests fail now i m so glad you asked in this file you ll find the torch method test suite it automatically loads all methods from the allowlist py file you modified in the previous step it attempts to test them step if you get a failing test if you get a failing test this could be for one of a few reasons reason the testing suite passed in non compatible arguments the testing suite is pretty dumb it literally just has a permutation of possible arguments to pass into every method on torch tensors so if one of those permutations doesn t work for your method aka perhaps it tries to call your method without any arguments but torch tensor sub actually requires some then the test will fail if the error hasn t been seen before if this happens don t worry just look inside the only test in that file and look for the huge lists of error types to ignore add your error to the list and keep going warning make sure that the testing suite actually tests your method via remote execution once you ve gotten all the tests passing aka if the testing suite doesn t have any matching argument permutations for your method then you re literally creating a bunch of unit tests that do absolutely nothing if this is the case then add more argument types to the testing suite so that your argument gets run via remote execution do not close this issue until you can verify that torch tensor sub is actually executed remotely inside of a unit tests and not skipped aka at least one of the test all allowlisted tensor methods work remotely on all types unit tests with your method should run all the way to the end instead of skipping the last part note adding another argument type might require some serialization work if we don t support arguments of that type yet if so this is your job to add it to the protobuf files in order to close this issue reason torch tensor sub returns a non supported type if this happens you ve got a little bit of work in front of you we don t have pointer objects to very many remote object types so if your method returns anything other than a single tensor you probably need to add support for the type it returns such as a bool none int or other types important do not return the value itself to the end user return a pointer object to that type note at the time of writing there are several core pieces of syft not yet working to allow you to return any type other than a torch tensor if you re not comfortable investigating what those might be skip this issue and try again later once someone else has solved these issues reason there s something else broken chase those stack traces talk to friends in slack look at how other methods are supported this is a challenging project in a fast moving codebase and don t forget if this project seems to complex there are plenty of others that might be easier | 1 |
34,603 | 12,294,658,044 | IssuesEvent | 2020-05-11 01:00:45 | LevyForchh/mindmeld | https://api.github.com/repos/LevyForchh/mindmeld | opened | WS-2020-0068 (High) detected in yargs-parser-10.1.0.tgz, yargs-parser-11.1.1.tgz | security vulnerability | ## WS-2020-0068 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>yargs-parser-10.1.0.tgz</b>, <b>yargs-parser-11.1.1.tgz</b></p></summary>
<p>
<details><summary><b>yargs-parser-10.1.0.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-10.1.0.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-10.1.0.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/mindmeld/mindmeld-ui/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/mindmeld/mindmeld-ui/node_modules/webpack-dev-server/node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-3.0.1.tgz (Root Library)
- webpack-dev-server-3.2.1.tgz
- yargs-12.0.2.tgz
- :x: **yargs-parser-10.1.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>yargs-parser-11.1.1.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-11.1.1.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-11.1.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/mindmeld/mindmeld-ui/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/mindmeld/mindmeld-ui/node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-3.0.1.tgz (Root Library)
- jest-24.7.1.tgz
- jest-cli-24.8.0.tgz
- yargs-12.0.5.tgz
- :x: **yargs-parser-11.1.1.tgz** (Vulnerable Library)
</details>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Affected versions of yargs-parser are vulnerable to prototype pollution. Arguments are not properly sanitized, allowing an attacker to modify the prototype of Object, causing the addition or modification of an existing property that will exist on all objects. Parsing the argument --foo.__proto__.bar baz' adds a bar property with value baz to all objects. This is only exploitable if attackers have control over the arguments being passed to yargs-parser.
<p>Publish Date: 2020-05-01
<p>URL: <a href=https://www.npmjs.com/advisories/1500>WS-2020-0068</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Adjacent
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/package/yargs-parser">https://www.npmjs.com/package/yargs-parser</a></p>
<p>Release Date: 2020-05-04</p>
<p>Fix Resolution: https://www.npmjs.com/package/yargs-parser/v/18.1.2,https://www.npmjs.com/package/yargs-parser/v/15.0.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"yargs-parser","packageVersion":"10.1.0","isTransitiveDependency":true,"dependencyTree":"react-scripts:3.0.1;webpack-dev-server:3.2.1;yargs:12.0.2;yargs-parser:10.1.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"https://www.npmjs.com/package/yargs-parser/v/18.1.2,https://www.npmjs.com/package/yargs-parser/v/15.0.1"},{"packageType":"javascript/Node.js","packageName":"yargs-parser","packageVersion":"11.1.1","isTransitiveDependency":true,"dependencyTree":"react-scripts:3.0.1;jest:24.7.1;jest-cli:24.8.0;yargs:12.0.5;yargs-parser:11.1.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"https://www.npmjs.com/package/yargs-parser/v/18.1.2,https://www.npmjs.com/package/yargs-parser/v/15.0.1"}],"vulnerabilityIdentifier":"WS-2020-0068","vulnerabilityDetails":"Affected versions of yargs-parser are vulnerable to prototype pollution. Arguments are not properly sanitized, allowing an attacker to modify the prototype of Object, causing the addition or modification of an existing property that will exist on all objects. Parsing the argument --foo.__proto__.bar baz\u0027 adds a bar property with value baz to all objects. This is only exploitable if attackers have control over the arguments being passed to yargs-parser.","vulnerabilityUrl":"https://www.npmjs.com/advisories/1500","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Adjacent","I":"High"},"extraData":{}}</REMEDIATE> --> | True | WS-2020-0068 (High) detected in yargs-parser-10.1.0.tgz, yargs-parser-11.1.1.tgz - ## WS-2020-0068 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>yargs-parser-10.1.0.tgz</b>, <b>yargs-parser-11.1.1.tgz</b></p></summary>
<p>
<details><summary><b>yargs-parser-10.1.0.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-10.1.0.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-10.1.0.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/mindmeld/mindmeld-ui/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/mindmeld/mindmeld-ui/node_modules/webpack-dev-server/node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-3.0.1.tgz (Root Library)
- webpack-dev-server-3.2.1.tgz
- yargs-12.0.2.tgz
- :x: **yargs-parser-10.1.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>yargs-parser-11.1.1.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-11.1.1.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-11.1.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/mindmeld/mindmeld-ui/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/mindmeld/mindmeld-ui/node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-3.0.1.tgz (Root Library)
- jest-24.7.1.tgz
- jest-cli-24.8.0.tgz
- yargs-12.0.5.tgz
- :x: **yargs-parser-11.1.1.tgz** (Vulnerable Library)
</details>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Affected versions of yargs-parser are vulnerable to prototype pollution. Arguments are not properly sanitized, allowing an attacker to modify the prototype of Object, causing the addition or modification of an existing property that will exist on all objects. Parsing the argument --foo.__proto__.bar baz' adds a bar property with value baz to all objects. This is only exploitable if attackers have control over the arguments being passed to yargs-parser.
<p>Publish Date: 2020-05-01
<p>URL: <a href=https://www.npmjs.com/advisories/1500>WS-2020-0068</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Adjacent
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/package/yargs-parser">https://www.npmjs.com/package/yargs-parser</a></p>
<p>Release Date: 2020-05-04</p>
<p>Fix Resolution: https://www.npmjs.com/package/yargs-parser/v/18.1.2,https://www.npmjs.com/package/yargs-parser/v/15.0.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"yargs-parser","packageVersion":"10.1.0","isTransitiveDependency":true,"dependencyTree":"react-scripts:3.0.1;webpack-dev-server:3.2.1;yargs:12.0.2;yargs-parser:10.1.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"https://www.npmjs.com/package/yargs-parser/v/18.1.2,https://www.npmjs.com/package/yargs-parser/v/15.0.1"},{"packageType":"javascript/Node.js","packageName":"yargs-parser","packageVersion":"11.1.1","isTransitiveDependency":true,"dependencyTree":"react-scripts:3.0.1;jest:24.7.1;jest-cli:24.8.0;yargs:12.0.5;yargs-parser:11.1.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"https://www.npmjs.com/package/yargs-parser/v/18.1.2,https://www.npmjs.com/package/yargs-parser/v/15.0.1"}],"vulnerabilityIdentifier":"WS-2020-0068","vulnerabilityDetails":"Affected versions of yargs-parser are vulnerable to prototype pollution. Arguments are not properly sanitized, allowing an attacker to modify the prototype of Object, causing the addition or modification of an existing property that will exist on all objects. Parsing the argument --foo.__proto__.bar baz\u0027 adds a bar property with value baz to all objects. This is only exploitable if attackers have control over the arguments being passed to yargs-parser.","vulnerabilityUrl":"https://www.npmjs.com/advisories/1500","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Adjacent","I":"High"},"extraData":{}}</REMEDIATE> --> | non_test | ws high detected in yargs parser tgz yargs parser tgz ws high severity vulnerability vulnerable libraries yargs parser tgz yargs parser tgz yargs parser tgz the mighty option parser used by yargs library home page a href path to dependency file tmp ws scm mindmeld mindmeld ui package json path to vulnerable library tmp ws scm mindmeld mindmeld ui node modules webpack dev server node modules yargs parser package json dependency hierarchy react scripts tgz root library webpack dev server tgz yargs tgz x yargs parser tgz vulnerable library yargs parser tgz the mighty option parser used by yargs library home page a href path to dependency file tmp ws scm mindmeld mindmeld ui package json path to vulnerable library tmp ws scm mindmeld mindmeld ui node modules yargs parser package json dependency hierarchy react scripts tgz root library jest tgz jest cli tgz yargs tgz x yargs parser tgz vulnerable library vulnerability details affected versions of yargs parser are vulnerable to prototype pollution arguments are not properly sanitized allowing an attacker to modify the prototype of object causing the addition or modification of an existing property that will exist on all objects parsing the argument foo proto bar baz adds a bar property with value baz to all objects this is only exploitable if attackers have control over the arguments being passed to yargs parser 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 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 isopenpronvulnerability false ispackagebased true isdefaultbranch true packages vulnerabilityidentifier ws vulnerabilitydetails affected versions of yargs parser are vulnerable to prototype pollution arguments are not properly sanitized allowing an attacker to modify the prototype of object causing the addition or modification of an existing property that will exist on all objects parsing the argument foo proto bar baz adds a bar property with value baz to all objects this is only exploitable if attackers have control over the arguments being passed to yargs parser vulnerabilityurl | 0 |
692,717 | 23,747,061,252 | IssuesEvent | 2022-08-31 16:54:21 | GAPP-Intelligence/gappblockssite | https://api.github.com/repos/GAPP-Intelligence/gappblockssite | closed | Screenshots for Finder app | priority | Finder:
- Homepage
- Earnings page
- Screenshot of an order
Make sure the currency is US Dollar "$" | 1.0 | Screenshots for Finder app - Finder:
- Homepage
- Earnings page
- Screenshot of an order
Make sure the currency is US Dollar "$" | non_test | screenshots for finder app finder homepage earnings page screenshot of an order make sure the currency is us dollar | 0 |
1,151 | 5,008,930,381 | IssuesEvent | 2016-12-12 20:55:23 | ansible/ansible-modules-extras | https://api.github.com/repos/ansible/ansible-modules-extras | closed | Make authorize in ASA more user friendly | affects_2.3 bug_report networking waiting_on_maintainer | Saw this a few days ago. I hope to find time to fix it, but haven't yet.
##### ISSUE TYPE
- Bug Report
- Feature Idea
##### COMPONENT NAME
- asa_acl
- asa_config
- asa_command
##### ANSIBLE VERSION
```
$ ansible --version
ansible 2.3.0 (devel 38d0f77a0f) last updated 2016/10/18 18:39:48 (GMT +200)
lib/ansible/modules/core: (devel ecc4029753) last updated 2016/10/18 18:41:14 (GMT +200)
lib/ansible/modules/extras: (devel 3f77bb6857) last updated 2016/10/18 18:41:28 (GMT +200)
config file = /Users/patrick/src/tests/ansible-asa/ansible.cfg
configured module search path = Default w/o overrides
```
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
N/A
##### SUMMARY
Unlike Cisco IOS the Cisco ASA cli doesn't ignore the `enable` command if the user already is in enable mode.
```
ns2903-asa-02# enable
^
ERROR: % Invalid input detected at '^' marker.
ns2903-asa-02#
```
##### STEPS TO REPRODUCE
Code in ASA
```
aaa authentication ssh console LOCAL
aaa authentication enable console LOCAL
aaa authorization exec LOCAL auto-enable
username cisco password 3USUcOPFUiMCO4Jk encrypted privilege 15
```
Playbook:
```
---
- hosts: firewall
connection: local
gather_facts: false
tasks:
- name: Show version
asa_command:
host: "{{ inventory_hostname }}"
auth_pass: cisco
username: cisco
password: cisco
authorize: yes
commands:
- show run
```
##### EXPECTED RESULTS
It would be more userfriendly if [asa.py](https://github.com/ansible/ansible/blob/devel/lib/ansible/module_utils/asa.py) either looked at the prompt first and didn't run `enable` if the prompt ended with `#` instead of `>`, another option would be to ignore the warning when this command was issued.
##### ACTUAL RESULTS
```
$ ansible-playbook -i hosts asa-sanity.yml
PLAY [firewall] ****************************************************************
TASK [Show version] ************************************************************
fatal: [172.29.50.2]: FAILED! => {"changed": false, "failed": true, "msg": "matched error in response: enable\r\n ^\r\nERROR: % Invalid input detected at '^' marker.\r\n"}
```
| True | Make authorize in ASA more user friendly - Saw this a few days ago. I hope to find time to fix it, but haven't yet.
##### ISSUE TYPE
- Bug Report
- Feature Idea
##### COMPONENT NAME
- asa_acl
- asa_config
- asa_command
##### ANSIBLE VERSION
```
$ ansible --version
ansible 2.3.0 (devel 38d0f77a0f) last updated 2016/10/18 18:39:48 (GMT +200)
lib/ansible/modules/core: (devel ecc4029753) last updated 2016/10/18 18:41:14 (GMT +200)
lib/ansible/modules/extras: (devel 3f77bb6857) last updated 2016/10/18 18:41:28 (GMT +200)
config file = /Users/patrick/src/tests/ansible-asa/ansible.cfg
configured module search path = Default w/o overrides
```
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
N/A
##### SUMMARY
Unlike Cisco IOS the Cisco ASA cli doesn't ignore the `enable` command if the user already is in enable mode.
```
ns2903-asa-02# enable
^
ERROR: % Invalid input detected at '^' marker.
ns2903-asa-02#
```
##### STEPS TO REPRODUCE
Code in ASA
```
aaa authentication ssh console LOCAL
aaa authentication enable console LOCAL
aaa authorization exec LOCAL auto-enable
username cisco password 3USUcOPFUiMCO4Jk encrypted privilege 15
```
Playbook:
```
---
- hosts: firewall
connection: local
gather_facts: false
tasks:
- name: Show version
asa_command:
host: "{{ inventory_hostname }}"
auth_pass: cisco
username: cisco
password: cisco
authorize: yes
commands:
- show run
```
##### EXPECTED RESULTS
It would be more userfriendly if [asa.py](https://github.com/ansible/ansible/blob/devel/lib/ansible/module_utils/asa.py) either looked at the prompt first and didn't run `enable` if the prompt ended with `#` instead of `>`, another option would be to ignore the warning when this command was issued.
##### ACTUAL RESULTS
```
$ ansible-playbook -i hosts asa-sanity.yml
PLAY [firewall] ****************************************************************
TASK [Show version] ************************************************************
fatal: [172.29.50.2]: FAILED! => {"changed": false, "failed": true, "msg": "matched error in response: enable\r\n ^\r\nERROR: % Invalid input detected at '^' marker.\r\n"}
```
| non_test | make authorize in asa more user friendly saw this a few days ago i hope to find time to fix it but haven t yet issue type bug report feature idea component name asa acl asa config asa command ansible version ansible version ansible devel last updated gmt lib ansible modules core devel last updated gmt lib ansible modules extras devel last updated gmt config file users patrick src tests ansible asa ansible cfg configured module search path default w o overrides configuration n a os environment n a summary unlike cisco ios the cisco asa cli doesn t ignore the enable command if the user already is in enable mode asa enable error invalid input detected at marker asa steps to reproduce code in asa aaa authentication ssh console local aaa authentication enable console local aaa authorization exec local auto enable username cisco password encrypted privilege playbook hosts firewall connection local gather facts false tasks name show version asa command host inventory hostname auth pass cisco username cisco password cisco authorize yes commands show run expected results it would be more userfriendly if either looked at the prompt first and didn t run enable if the prompt ended with instead of another option would be to ignore the warning when this command was issued actual results ansible playbook i hosts asa sanity yml play task fatal failed changed false failed true msg matched error in response enable r n r nerror invalid input detected at marker r n | 0 |
347,973 | 31,390,356,737 | IssuesEvent | 2023-08-26 08:57:42 | LyQuocCuong/eShopOnlineApi | https://api.github.com/repos/LyQuocCuong/eShopOnlineApi | closed | [SOA-050][Testing] Writing the UnitTest for validating Creation/Update models (after applying FluentValidation). | [Level] Medium [Type] Testing [Note] New [Note] Lesson | =====BEFORE=====
**Which part do you want to test ?**
- Checking the validation in UnitTests **`(currently NOT)`**
- **`Link is UnitTest for Auto Validation but I use Manual Validation`**: [UnitTest for Auto Validation](https://code-maze.com/testing-repository-pattern-entity-framework)
=====AFTER=====
**Are there any NEW (technical, code,...) ?**
**Are there any challenges?**
**Any notes?**
| 1.0 | [SOA-050][Testing] Writing the UnitTest for validating Creation/Update models (after applying FluentValidation). - =====BEFORE=====
**Which part do you want to test ?**
- Checking the validation in UnitTests **`(currently NOT)`**
- **`Link is UnitTest for Auto Validation but I use Manual Validation`**: [UnitTest for Auto Validation](https://code-maze.com/testing-repository-pattern-entity-framework)
=====AFTER=====
**Are there any NEW (technical, code,...) ?**
**Are there any challenges?**
**Any notes?**
| test | writing the unittest for validating creation update models after applying fluentvalidation before which part do you want to test checking the validation in unittests currently not link is unittest for auto validation but i use manual validation after are there any new technical code are there any challenges any notes | 1 |
77,714 | 7,600,663,524 | IssuesEvent | 2018-04-28 04:52:24 | rancher/rancher | https://api.github.com/repos/rancher/rancher | closed | Creating cluster using private registry fails as kubelet fails to pull the image rancher/pause-amd64:3.0 | area/ui kind/bug priority/0 status/to-test | **Rancher versions:**
rancher/rancher:vv2.0.0-rc1
**Steps to Reproduce:**
1. Push all images to a private registry
2. Create a custom cluster using the private registry in UI
kubelet, kube-proxy and all the components get pulled from the registry successfully on the host. kubelet is running but fails to pull the rancher/pause-amd64:3.0 image from the private registry
kubelet does not have the information to pull from the private registry.
kubelet logs below:
```
E0426 22:22:59.122859 13648 pod_workers.go:186] Error syncing pod 1775a30e-499c-11e8-8aac-962f3e87879d ("rke-network-plugin-deploy-job-nkcdr_kube-system(1775a30e-499c-11e8-8aac-962f3e87879d)"), skipping: failed to "CreatePodSandbox" for "rke-network-plugin-deploy-job-nkcdr_kube-system(1775a30e-499c-11e8-8aac-962f3e87879d)" with CreatePodSandboxError: "CreatePodSandbox for pod \"rke-network-plugin-deploy-job-nkcdr_kube-system(1775a30e-499c-11e8-8aac-962f3e87879d)\" failed: rpc error: code = Unknown desc = failed pulling image \"registrytest:5000/rancher/pause-amd64:3.0\": Error: image rancher/pause-amd64:3.0 not found"
W0426 22:23:02.563059 13648 cni.go:171] Unable to update cni config: No networks found in /etc/cni/net.d
E0426 22:23:02.563322 13648 kubelet.go:2120] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
I0426 22:23:03.090067 13648 kuberuntime_manager.go:385] No sandbox for pod "rke-kubedns-addon-deploy-job-7rjds_kube-system(50594e38-499c-11e8-8aac-962f3e87879d)" can be found. Need to start a new one
I0426 22:23:03.121792 13648 kube_docker_client.go:348] Stop pulling image "registrytest:5000/rancher/pause-amd64:3.0": "Pulling repository registrytest:5000/rancher/pause-amd64"
E0426 22:23:03.121862 13648 remote_runtime.go:92] RunPodSandbox from runtime service failed: rpc error: code = Unknown desc = failed pulling image "registrytest:5000/rancher/pause-amd64:3.0": Error: image rancher/pause-amd64:3.0 not found
E0426 22:23:03.121913 13648 kuberuntime_sandbox.go:54] CreatePodSandbox for pod "rke-kubedns-addon-deploy-job-7rjds_kube-system(50594e38-499c-11e8-8aac-962f3e87879d)" failed: rpc error: code = Unknown desc = failed pulling image "registrytest:5000/rancher/pause-amd64:3.0": Error: image rancher/pause-amd64:3.0 not found
E0426 22:23:03.121954 13648 kuberuntime_manager.go:647] createPodSandbox for pod "rke-kubedns-addon-deploy-job-7rjds_kube-system(50594e38-499c-11e8-8aac-962f3e87879d)" failed: rpc error: code = Unknown desc = failed pulling image "registrytest:5000/rancher/pause-amd64:3.0": Error: image rancher/pause-amd64:3.0 not found
E0426 22:23:03.122113 13648 pod_workers.go:186] Error syncing pod 50594e38-499c-11e8-8aac-962f3e87879d ("rke-kubedns-addon-deploy-job-7rjds_kube-system(50594e38-499c-11e8-8aac-962f3e87879d)"), skipping: failed to "CreatePodSandbox" for "rke-kubedns-addon-deploy-job-7rjds_kube-system(50594e38-499c-11e8-8aac-962f3e87879d)" with CreatePodSandboxError: "CreatePodSandbox for pod \"rke-kubedns-addon-deploy-job-7rjds_kube-system(50594e38-499c-11e8-8aac-962f3e87879d)\" failed: rpc error: code = Unknown desc = failed pulling image \"registrytest:5000/rancher/pause-amd64:3.0\": Error: image rancher/pause-amd64:3.0 not found"
```
The node is in unavailable state as the network plugin is not ready
<img width="1300" alt="screen shot 2018-04-26 at 3 41 51 pm" src="https://user-images.githubusercontent.com/18536626/39335567-67b9714a-4968-11e8-8e82-4b9968a535e3.png">
| 1.0 | Creating cluster using private registry fails as kubelet fails to pull the image rancher/pause-amd64:3.0 - **Rancher versions:**
rancher/rancher:vv2.0.0-rc1
**Steps to Reproduce:**
1. Push all images to a private registry
2. Create a custom cluster using the private registry in UI
kubelet, kube-proxy and all the components get pulled from the registry successfully on the host. kubelet is running but fails to pull the rancher/pause-amd64:3.0 image from the private registry
kubelet does not have the information to pull from the private registry.
kubelet logs below:
```
E0426 22:22:59.122859 13648 pod_workers.go:186] Error syncing pod 1775a30e-499c-11e8-8aac-962f3e87879d ("rke-network-plugin-deploy-job-nkcdr_kube-system(1775a30e-499c-11e8-8aac-962f3e87879d)"), skipping: failed to "CreatePodSandbox" for "rke-network-plugin-deploy-job-nkcdr_kube-system(1775a30e-499c-11e8-8aac-962f3e87879d)" with CreatePodSandboxError: "CreatePodSandbox for pod \"rke-network-plugin-deploy-job-nkcdr_kube-system(1775a30e-499c-11e8-8aac-962f3e87879d)\" failed: rpc error: code = Unknown desc = failed pulling image \"registrytest:5000/rancher/pause-amd64:3.0\": Error: image rancher/pause-amd64:3.0 not found"
W0426 22:23:02.563059 13648 cni.go:171] Unable to update cni config: No networks found in /etc/cni/net.d
E0426 22:23:02.563322 13648 kubelet.go:2120] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
I0426 22:23:03.090067 13648 kuberuntime_manager.go:385] No sandbox for pod "rke-kubedns-addon-deploy-job-7rjds_kube-system(50594e38-499c-11e8-8aac-962f3e87879d)" can be found. Need to start a new one
I0426 22:23:03.121792 13648 kube_docker_client.go:348] Stop pulling image "registrytest:5000/rancher/pause-amd64:3.0": "Pulling repository registrytest:5000/rancher/pause-amd64"
E0426 22:23:03.121862 13648 remote_runtime.go:92] RunPodSandbox from runtime service failed: rpc error: code = Unknown desc = failed pulling image "registrytest:5000/rancher/pause-amd64:3.0": Error: image rancher/pause-amd64:3.0 not found
E0426 22:23:03.121913 13648 kuberuntime_sandbox.go:54] CreatePodSandbox for pod "rke-kubedns-addon-deploy-job-7rjds_kube-system(50594e38-499c-11e8-8aac-962f3e87879d)" failed: rpc error: code = Unknown desc = failed pulling image "registrytest:5000/rancher/pause-amd64:3.0": Error: image rancher/pause-amd64:3.0 not found
E0426 22:23:03.121954 13648 kuberuntime_manager.go:647] createPodSandbox for pod "rke-kubedns-addon-deploy-job-7rjds_kube-system(50594e38-499c-11e8-8aac-962f3e87879d)" failed: rpc error: code = Unknown desc = failed pulling image "registrytest:5000/rancher/pause-amd64:3.0": Error: image rancher/pause-amd64:3.0 not found
E0426 22:23:03.122113 13648 pod_workers.go:186] Error syncing pod 50594e38-499c-11e8-8aac-962f3e87879d ("rke-kubedns-addon-deploy-job-7rjds_kube-system(50594e38-499c-11e8-8aac-962f3e87879d)"), skipping: failed to "CreatePodSandbox" for "rke-kubedns-addon-deploy-job-7rjds_kube-system(50594e38-499c-11e8-8aac-962f3e87879d)" with CreatePodSandboxError: "CreatePodSandbox for pod \"rke-kubedns-addon-deploy-job-7rjds_kube-system(50594e38-499c-11e8-8aac-962f3e87879d)\" failed: rpc error: code = Unknown desc = failed pulling image \"registrytest:5000/rancher/pause-amd64:3.0\": Error: image rancher/pause-amd64:3.0 not found"
```
The node is in unavailable state as the network plugin is not ready
<img width="1300" alt="screen shot 2018-04-26 at 3 41 51 pm" src="https://user-images.githubusercontent.com/18536626/39335567-67b9714a-4968-11e8-8e82-4b9968a535e3.png">
| test | creating cluster using private registry fails as kubelet fails to pull the image rancher pause rancher versions rancher rancher steps to reproduce push all images to a private registry create a custom cluster using the private registry in ui kubelet kube proxy and all the components get pulled from the registry successfully on the host kubelet is running but fails to pull the rancher pause image from the private registry kubelet does not have the information to pull from the private registry kubelet logs below pod workers go error syncing pod rke network plugin deploy job nkcdr kube system skipping failed to createpodsandbox for rke network plugin deploy job nkcdr kube system with createpodsandboxerror createpodsandbox for pod rke network plugin deploy job nkcdr kube system failed rpc error code unknown desc failed pulling image registrytest rancher pause error image rancher pause not found cni go unable to update cni config no networks found in etc cni net d kubelet go container runtime network not ready networkready false reason networkpluginnotready message docker network plugin is not ready cni config uninitialized kuberuntime manager go no sandbox for pod rke kubedns addon deploy job kube system can be found need to start a new one kube docker client go stop pulling image registrytest rancher pause pulling repository registrytest rancher pause remote runtime go runpodsandbox from runtime service failed rpc error code unknown desc failed pulling image registrytest rancher pause error image rancher pause not found kuberuntime sandbox go createpodsandbox for pod rke kubedns addon deploy job kube system failed rpc error code unknown desc failed pulling image registrytest rancher pause error image rancher pause not found kuberuntime manager go createpodsandbox for pod rke kubedns addon deploy job kube system failed rpc error code unknown desc failed pulling image registrytest rancher pause error image rancher pause not found pod workers go error syncing pod rke kubedns addon deploy job kube system skipping failed to createpodsandbox for rke kubedns addon deploy job kube system with createpodsandboxerror createpodsandbox for pod rke kubedns addon deploy job kube system failed rpc error code unknown desc failed pulling image registrytest rancher pause error image rancher pause not found the node is in unavailable state as the network plugin is not ready img width alt screen shot at pm src | 1 |
17,496 | 24,122,597,453 | IssuesEvent | 2022-09-20 20:10:50 | lipefl/swade-tools | https://api.github.com/repos/lipefl/swade-tools | closed | Seems to be mainly not working in FVTT v10 | compatibility | Sadly, the module seems to be mainly not working in FVTT v10
E.g., the initial dialog for a melee weapon attack is shown with the attack and damage button, and the rolls are shown in chat
But it's not picking up the target details, so no calculation versus Parry, and subsequent damage versus Toughness 😭
Any plans on a update to FVTT v10 ?
... really hoping the answer is "due to release very soon" 😄 | True | Seems to be mainly not working in FVTT v10 - Sadly, the module seems to be mainly not working in FVTT v10
E.g., the initial dialog for a melee weapon attack is shown with the attack and damage button, and the rolls are shown in chat
But it's not picking up the target details, so no calculation versus Parry, and subsequent damage versus Toughness 😭
Any plans on a update to FVTT v10 ?
... really hoping the answer is "due to release very soon" 😄 | non_test | seems to be mainly not working in fvtt sadly the module seems to be mainly not working in fvtt e g the initial dialog for a melee weapon attack is shown with the attack and damage button and the rolls are shown in chat but it s not picking up the target details so no calculation versus parry and subsequent damage versus toughness 😭 any plans on a update to fvtt really hoping the answer is due to release very soon 😄 | 0 |
253,035 | 21,648,482,777 | IssuesEvent | 2022-05-06 06:38:13 | stores-cedcommerce/Ninjamo-Store-Dev | https://api.github.com/repos/stores-cedcommerce/Ninjamo-Store-Dev | closed | Pagination & arrows disappearing in search page | Search page Ready to test fixed | The numbers are invisible in search page pagination & also on hover the text & arrows are disappearing.
Video: https://www.awesomescreenshot.com/video/8749063?key=4a835a5aa2107c11312fa75020443908 | 1.0 | Pagination & arrows disappearing in search page - The numbers are invisible in search page pagination & also on hover the text & arrows are disappearing.
Video: https://www.awesomescreenshot.com/video/8749063?key=4a835a5aa2107c11312fa75020443908 | test | pagination arrows disappearing in search page the numbers are invisible in search page pagination also on hover the text arrows are disappearing video | 1 |
71,686 | 3,367,446,765 | IssuesEvent | 2015-11-22 06:05:17 | Tribes2-SCP/Torque3D | https://api.github.com/repos/Tribes2-SCP/Torque3D | opened | getControlObjectSpeed | Low Priority Missing Functionality | Torque3D is missing getControlObjectSpeed which returns the total speed that the current control object is moving at as a single float. This is a clientside function that is to be invoked as such:
%speed = getControlObjectSpeed();
| 1.0 | getControlObjectSpeed - Torque3D is missing getControlObjectSpeed which returns the total speed that the current control object is moving at as a single float. This is a clientside function that is to be invoked as such:
%speed = getControlObjectSpeed();
| non_test | getcontrolobjectspeed is missing getcontrolobjectspeed which returns the total speed that the current control object is moving at as a single float this is a clientside function that is to be invoked as such speed getcontrolobjectspeed | 0 |
171,400 | 13,231,814,627 | IssuesEvent | 2020-08-18 12:21:26 | filecoin-project/oni | https://api.github.com/repos/filecoin-project/oni | closed | CI integration in `filecoin-project/lotus` | workstream/vm-conformance-tests | Once we have #221 and #222, we should set up a Circle CI job in `filecoin-project/lotus` that does the following:
1. Does a shallow clone of the `filecoin/vm-tests` repo.
- Lock in a concrete tag/branch/commit in a `.vmtests.toml` config file at the root of the repo.
- This has many benefits:
- Explicitly declares which version of the corpus this VM implementation complies with.
- Future-proof: allows us to conduct change management / evolution cleanly without incurring in false, noisy breakage. Removes volatility.
2. Exercises the Lotus VM against the test vectors using the test driver.
3. Populate a JUnit XML file via `gotestsum` so CircleCI can populate the Tests tab. | 1.0 | CI integration in `filecoin-project/lotus` - Once we have #221 and #222, we should set up a Circle CI job in `filecoin-project/lotus` that does the following:
1. Does a shallow clone of the `filecoin/vm-tests` repo.
- Lock in a concrete tag/branch/commit in a `.vmtests.toml` config file at the root of the repo.
- This has many benefits:
- Explicitly declares which version of the corpus this VM implementation complies with.
- Future-proof: allows us to conduct change management / evolution cleanly without incurring in false, noisy breakage. Removes volatility.
2. Exercises the Lotus VM against the test vectors using the test driver.
3. Populate a JUnit XML file via `gotestsum` so CircleCI can populate the Tests tab. | test | ci integration in filecoin project lotus once we have and we should set up a circle ci job in filecoin project lotus that does the following does a shallow clone of the filecoin vm tests repo lock in a concrete tag branch commit in a vmtests toml config file at the root of the repo this has many benefits explicitly declares which version of the corpus this vm implementation complies with future proof allows us to conduct change management evolution cleanly without incurring in false noisy breakage removes volatility exercises the lotus vm against the test vectors using the test driver populate a junit xml file via gotestsum so circleci can populate the tests tab | 1 |
243,502 | 20,405,624,702 | IssuesEvent | 2022-02-23 04:49:05 | Azure/sonic-mgmt | https://api.github.com/repos/Azure/sonic-mgmt | closed | [dualToR] Add test to cover the scenario of a port being set to admin down | Test gap | <!--
If you are reporting a new issue, make sure that we do not have any duplicates
already open. You can ensure this by searching the issue list for this
repository. If there is a duplicate, please close your issue and add a comment
to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to
include the BUG REPORT INFORMATION shown below. If you fail to provide this
information within 7 days, we cannot debug your issue and will close it. We
will, however, reopen it if you later provide the information.
For more information about reporting issues, see
https://github.com/Azure/SONiC/wiki#report-issues
---------------------------------------------------
GENERAL SUPPORT INFORMATION
---------------------------------------------------
The GitHub issue tracker is for bug reports and feature requests.
General support can be found at the following locations:
- SONiC Support Forums - https://groups.google.com/forum/#!forum/sonicproject
---------------------------------------------------
BUG REPORT INFORMATION
---------------------------------------------------
Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST
-->
**Description**
<!--
Briefly describe the problem you are having in a few paragraphs.
-->
We want to add a dualToR test to cover the scenario of ports being disabled.
**Expected behavior**
The end state of ports being disabled will be "standby".
**How to verify?**
* Verify traffic correctness. Please check [dualtor/data_plane_utils.py](https://github.com/Azure/sonic-mgmt/blob/master/tests/common/dualtor/data_plane_utils.py)
* Verify values in APP_DB and STATE_DB. Please check [dualtor/control_plane_utils.py](https://github.com/Azure/sonic-mgmt/blob/master/tests/common/dualtor/control_plane_utils.py).
Please feel free to use any dualtor_io test as example.
| 1.0 | [dualToR] Add test to cover the scenario of a port being set to admin down - <!--
If you are reporting a new issue, make sure that we do not have any duplicates
already open. You can ensure this by searching the issue list for this
repository. If there is a duplicate, please close your issue and add a comment
to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to
include the BUG REPORT INFORMATION shown below. If you fail to provide this
information within 7 days, we cannot debug your issue and will close it. We
will, however, reopen it if you later provide the information.
For more information about reporting issues, see
https://github.com/Azure/SONiC/wiki#report-issues
---------------------------------------------------
GENERAL SUPPORT INFORMATION
---------------------------------------------------
The GitHub issue tracker is for bug reports and feature requests.
General support can be found at the following locations:
- SONiC Support Forums - https://groups.google.com/forum/#!forum/sonicproject
---------------------------------------------------
BUG REPORT INFORMATION
---------------------------------------------------
Use the commands below to provide key information from your environment:
You do NOT have to include this information if this is a FEATURE REQUEST
-->
**Description**
<!--
Briefly describe the problem you are having in a few paragraphs.
-->
We want to add a dualToR test to cover the scenario of ports being disabled.
**Expected behavior**
The end state of ports being disabled will be "standby".
**How to verify?**
* Verify traffic correctness. Please check [dualtor/data_plane_utils.py](https://github.com/Azure/sonic-mgmt/blob/master/tests/common/dualtor/data_plane_utils.py)
* Verify values in APP_DB and STATE_DB. Please check [dualtor/control_plane_utils.py](https://github.com/Azure/sonic-mgmt/blob/master/tests/common/dualtor/control_plane_utils.py).
Please feel free to use any dualtor_io test as example.
| test | add test to cover the scenario of a port being set to admin down if you are reporting a new issue make sure that we do not have any duplicates already open you can ensure this by searching the issue list for this repository if there is a duplicate please close your issue and add a comment to the existing issue instead if you suspect your issue is a bug please edit your issue description to include the bug report information shown below if you fail to provide this information within days we cannot debug your issue and will close it we will however reopen it if you later provide the information for more information about reporting issues see general support information the github issue tracker is for bug reports and feature requests general support can be found at the following locations sonic support forums bug report information use the commands below to provide key information from your environment you do not have to include this information if this is a feature request description briefly describe the problem you are having in a few paragraphs we want to add a dualtor test to cover the scenario of ports being disabled expected behavior the end state of ports being disabled will be standby how to verify verify traffic correctness please check verify values in app db and state db please check please feel free to use any dualtor io test as example | 1 |
85,539 | 3,691,443,875 | IssuesEvent | 2016-02-26 00:03:55 | Apollo-Community/ApolloStation | https://api.github.com/repos/Apollo-Community/ApolloStation | closed | IPC can't charge if more than one on station | bug priority: low | I don't know if it's just me, or what. But Whenever there is more than one IPC on the station, (Mainly if I'm not the first.) I can't Siphon off energy for nutrition. Nor can I give off some Energy to the APCs.
Edit: Forgot to note that whenever another IPC charges, When they stop charging, I get a message stating; "You rip your fingers out of the APC!" as if I were the one who was charging. | 1.0 | IPC can't charge if more than one on station - I don't know if it's just me, or what. But Whenever there is more than one IPC on the station, (Mainly if I'm not the first.) I can't Siphon off energy for nutrition. Nor can I give off some Energy to the APCs.
Edit: Forgot to note that whenever another IPC charges, When they stop charging, I get a message stating; "You rip your fingers out of the APC!" as if I were the one who was charging. | non_test | ipc can t charge if more than one on station i don t know if it s just me or what but whenever there is more than one ipc on the station mainly if i m not the first i can t siphon off energy for nutrition nor can i give off some energy to the apcs edit forgot to note that whenever another ipc charges when they stop charging i get a message stating you rip your fingers out of the apc as if i were the one who was charging | 0 |
352,573 | 25,073,105,885 | IssuesEvent | 2022-11-07 13:40:39 | q191201771/lalext | https://api.github.com/repos/q191201771/lalext | opened | 重要概念收集 | documentation | > 重要概念 展示地址： https://pengrl.com/lal/#/concept
> 重要概念 文档存放地址：github [lalext项目](https://github.com/q191201771/lalext) 的 [lal_website/concept.md](https://github.com/q191201771/lalext/blob/master/lal_website/concept.md)
>
> 欢迎大家添加自己的问题，或者自问自答，或者回答文档里最下面待整理的问题。
>
> 参与方式，可以提PR修改文档 [lal_website/concept.md](https://github.com/q191201771/lalext/blob/master/lal_website/concept.md)，也可以到这个 [issue](https://github.com/q191201771/lalext/issues/5) 里直接跟帖。
| 1.0 | 重要概念收集 - > 重要概念 展示地址： https://pengrl.com/lal/#/concept
> 重要概念 文档存放地址：github [lalext项目](https://github.com/q191201771/lalext) 的 [lal_website/concept.md](https://github.com/q191201771/lalext/blob/master/lal_website/concept.md)
>
> 欢迎大家添加自己的问题，或者自问自答，或者回答文档里最下面待整理的问题。
>
> 参与方式，可以提PR修改文档 [lal_website/concept.md](https://github.com/q191201771/lalext/blob/master/lal_website/concept.md)，也可以到这个 [issue](https://github.com/q191201771/lalext/issues/5) 里直接跟帖。
| non_test | 重要概念收集 重要概念 展示地址： 重要概念 文档存放地址：github 的 欢迎大家添加自己的问题，或者自问自答，或者回答文档里最下面待整理的问题。 参与方式，可以提pr修改文档 里直接跟帖。 | 0 |
194,598 | 6,896,768,882 | IssuesEvent | 2017-11-23 20:06:11 | department-of-veterans-affairs/caseflow-efolder | https://api.github.com/repos/department-of-veterans-affairs/caseflow-efolder | opened | CalculateStatsJob | The job causes 100s of User lookups | bug-medium-priority whiskey | # Description
When CalculateStatsJob runs. It's doing 200+ requests per second to the database to lookup users.
Does it need to run that often? We have a ton of users now so it's inefficient.
## Reproduction Steps
**Scenario 1 -**
1. Go to eFolder logs
1. Watch the job run
1. Get a an enormous logdump
**Validated in the following Environment(s)**
- [ ] Dev
- [X] UAT
- [ ] Preprod
- [X] Prod
## Logs:
- After watching logs for about 15 seconds
```
cat eFolderWorker.out | grep 'User Load (1.1ms)' | wc -l
7843
```
**_Engineering_**
https://github.com/department-of-veterans-affairs/appeals-deployment/issues/1022 | 1.0 | CalculateStatsJob | The job causes 100s of User lookups - # Description
When CalculateStatsJob runs. It's doing 200+ requests per second to the database to lookup users.
Does it need to run that often? We have a ton of users now so it's inefficient.
## Reproduction Steps
**Scenario 1 -**
1. Go to eFolder logs
1. Watch the job run
1. Get a an enormous logdump
**Validated in the following Environment(s)**
- [ ] Dev
- [X] UAT
- [ ] Preprod
- [X] Prod
## Logs:
- After watching logs for about 15 seconds
```
cat eFolderWorker.out | grep 'User Load (1.1ms)' | wc -l
7843
```
**_Engineering_**
https://github.com/department-of-veterans-affairs/appeals-deployment/issues/1022 | non_test | calculatestatsjob the job causes of user lookups description when calculatestatsjob runs it s doing requests per second to the database to lookup users does it need to run that often we have a ton of users now so it s inefficient reproduction steps scenario go to efolder logs watch the job run get a an enormous logdump validated in the following environment s dev uat preprod prod logs after watching logs for about seconds cat efolderworker out grep user load wc l engineering | 0 |
391,171 | 11,570,090,013 | IssuesEvent | 2020-02-20 18:50:42 | greeneteenee/tinyclothesshopping | https://api.github.com/repos/greeneteenee/tinyclothesshopping | closed | Create login page | enhancement high priority | After users have been registered, allow them to login with username and password
If users are not logged in, show link to register and login
If users are logged in, hide register/login and show logout link | 1.0 | Create login page - After users have been registered, allow them to login with username and password
If users are not logged in, show link to register and login
If users are logged in, hide register/login and show logout link | non_test | create login page after users have been registered allow them to login with username and password if users are not logged in show link to register and login if users are logged in hide register login and show logout link | 0 |
309,604 | 9,477,521,217 | IssuesEvent | 2019-04-19 18:55:32 | zulip/zulip-electron | https://api.github.com/repos/zulip/zulip-electron | closed | Make capitalization in menus consistent | Priority: High in progress | Capitalization is inconsistent in the File/Edit/etc. menus; we should probably be consistently using the "Keyboard shortcuts" style of capitalization that we use throughout the app. So e.g. "Hard Reload" should become "Hard reload"
| 1.0 | Make capitalization in menus consistent - Capitalization is inconsistent in the File/Edit/etc. menus; we should probably be consistently using the "Keyboard shortcuts" style of capitalization that we use throughout the app. So e.g. "Hard Reload" should become "Hard reload"
| non_test | make capitalization in menus consistent capitalization is inconsistent in the file edit etc menus we should probably be consistently using the keyboard shortcuts style of capitalization that we use throughout the app so e g hard reload should become hard reload | 0 |
588,803 | 17,671,990,434 | IssuesEvent | 2021-08-23 07:35:39 | nestjs/nest | https://api.github.com/repos/nestjs/nest | closed | Add Debug Level Logs during provider resolution | type: enhancement :wolf: type: feature :tada: scope: core effort1: hours priority: low (4) | ## Feature Request
## Is your feature request related to a problem? Please describe.
Often times new users to the framework are confused about where the dependency resolution is coming from with the server startup and how dependencies end up getting injected into each dependency.
## Describe the solution you'd like
I'd like to see logs at a `debug` or `verbose` level that can be turned on and off (hence the level) to help describe why dependencies are being injected, where they are pulled from, and what is attempted to be looked at for the dependencies. Ideally something like
```
Resolving dependencies for FooService
Resolving BarService
Searching in FooModule for BarService
Searching in BarModule's exports for BarService
BarService found in BarModule's exports.
BarService Resovled
Resolving BazService
...
```
This may be a bit more verbose than absolutely necessary, and might be a good split between just debug and verbose levels.
## Teachability, Documentation, Adoption, Migration Strategy
It should be pretty easy to make a mention about this in the docs. And it would be pretty opt-in so it shouldn't harm anyone
## What is the motivation / use case for changing the behavior?
I feel like this will help newcomers and veterans of the framework see how Nest resolves dependencies better and give developers more confidence about what is happening under the covers.
I'm more than happy to work on this, already started with a bit of code actually, but will need some pointers about determining what module the current dependency belongs to. I think I can follow most the rest of the code though. | 1.0 | Add Debug Level Logs during provider resolution - ## Feature Request
## Is your feature request related to a problem? Please describe.
Often times new users to the framework are confused about where the dependency resolution is coming from with the server startup and how dependencies end up getting injected into each dependency.
## Describe the solution you'd like
I'd like to see logs at a `debug` or `verbose` level that can be turned on and off (hence the level) to help describe why dependencies are being injected, where they are pulled from, and what is attempted to be looked at for the dependencies. Ideally something like
```
Resolving dependencies for FooService
Resolving BarService
Searching in FooModule for BarService
Searching in BarModule's exports for BarService
BarService found in BarModule's exports.
BarService Resovled
Resolving BazService
...
```
This may be a bit more verbose than absolutely necessary, and might be a good split between just debug and verbose levels.
## Teachability, Documentation, Adoption, Migration Strategy
It should be pretty easy to make a mention about this in the docs. And it would be pretty opt-in so it shouldn't harm anyone
## What is the motivation / use case for changing the behavior?
I feel like this will help newcomers and veterans of the framework see how Nest resolves dependencies better and give developers more confidence about what is happening under the covers.
I'm more than happy to work on this, already started with a bit of code actually, but will need some pointers about determining what module the current dependency belongs to. I think I can follow most the rest of the code though. | non_test | add debug level logs during provider resolution feature request is your feature request related to a problem please describe often times new users to the framework are confused about where the dependency resolution is coming from with the server startup and how dependencies end up getting injected into each dependency describe the solution you d like i d like to see logs at a debug or verbose level that can be turned on and off hence the level to help describe why dependencies are being injected where they are pulled from and what is attempted to be looked at for the dependencies ideally something like resolving dependencies for fooservice resolving barservice searching in foomodule for barservice searching in barmodule s exports for barservice barservice found in barmodule s exports barservice resovled resolving bazservice this may be a bit more verbose than absolutely necessary and might be a good split between just debug and verbose levels teachability documentation adoption migration strategy it should be pretty easy to make a mention about this in the docs and it would be pretty opt in so it shouldn t harm anyone what is the motivation use case for changing the behavior i feel like this will help newcomers and veterans of the framework see how nest resolves dependencies better and give developers more confidence about what is happening under the covers i m more than happy to work on this already started with a bit of code actually but will need some pointers about determining what module the current dependency belongs to i think i can follow most the rest of the code though | 0 |
244,169 | 20,614,162,892 | IssuesEvent | 2022-03-07 11:32:38 | mapeditor/rs-tiled | https://api.github.com/repos/mapeditor/rs-tiled | closed | Add tests for external asset sources | enhancement tests | After seeing all the complex code related to paths, there's bound to be an error somewhere. We should check if parsing tileset/image/etc references in nested directories as well as parent directories works correctly. | 1.0 | Add tests for external asset sources - After seeing all the complex code related to paths, there's bound to be an error somewhere. We should check if parsing tileset/image/etc references in nested directories as well as parent directories works correctly. | test | add tests for external asset sources after seeing all the complex code related to paths there s bound to be an error somewhere we should check if parsing tileset image etc references in nested directories as well as parent directories works correctly | 1 |
743,456 | 25,899,720,590 | IssuesEvent | 2022-12-15 03:48:45 | julianmichael/debate | https://api.github.com/repos/julianmichael/debate | closed | Fix intermittent websocket disconnects | bug high priority | * Happened to one person using Firefox and Chrome but not others. Not sure if we can reliably reproduce but putting the issue here for further reference in case we reproduce it.
* It's possible we need to add heartbeats. I don't think it's necessary though?
* The likely fix will be getting the client to seamlessly auto-reconnect. | 1.0 | Fix intermittent websocket disconnects - * Happened to one person using Firefox and Chrome but not others. Not sure if we can reliably reproduce but putting the issue here for further reference in case we reproduce it.
* It's possible we need to add heartbeats. I don't think it's necessary though?
* The likely fix will be getting the client to seamlessly auto-reconnect. | non_test | fix intermittent websocket disconnects happened to one person using firefox and chrome but not others not sure if we can reliably reproduce but putting the issue here for further reference in case we reproduce it it s possible we need to add heartbeats i don t think it s necessary though the likely fix will be getting the client to seamlessly auto reconnect | 0 |
258,147 | 22,286,657,898 | IssuesEvent | 2022-06-11 18:40:47 | tiekoetter/vodafone-stoerungsstatistiken | https://api.github.com/repos/tiekoetter/vodafone-stoerungsstatistiken | closed | 🛑 home.tiekoetter.com is down | status home-tiekoetter-com test | In [`d1a8190`](https://github.com/tiekoetter/vodafone-stoerungsstatistiken/commit/d1a8190e6ee6a0cb16ef69865ec9cd32788dfe01
), home.tiekoetter.com (https://home.tiekoetter.com) was **down**:
- HTTP code: 0
- Response time: 0 ms
| 1.0 | 🛑 home.tiekoetter.com is down - In [`d1a8190`](https://github.com/tiekoetter/vodafone-stoerungsstatistiken/commit/d1a8190e6ee6a0cb16ef69865ec9cd32788dfe01
), home.tiekoetter.com (https://home.tiekoetter.com) was **down**:
- HTTP code: 0
- Response time: 0 ms
| test | 🛑 home tiekoetter com is down in home tiekoetter com was down http code response time ms | 1 |
24,461 | 17,287,096,510 | IssuesEvent | 2021-07-24 00:26:41 | dotnet/roslyn | https://api.github.com/repos/dotnet/roslyn | closed | CloudCachePersistentStorageTests.TestReadChecksumProducesLastWrittenChecksum1 failed in CI: Pipelines - Run 20210715.30 (azure.com) | Area-Infrastructure Bug | https://dev.azure.com/dnceng/public/_build/results?buildId=1240966&view=ms.vss-test-web.build-test-results-tab&runId=36910020&resultId=215221&paneView=debug
According to infra, this has failed 4 times in the last 30 days.
Failure is:
```
Assert.False() Failure
Expected: False
Actual: True
```
The code for this is here:
https://github.com/dotnet/roslyn/blob/dc3d67460c5632f9ea75df8ed098dc319630ec62/src/VisualStudio/CSharp/Test/PersistentStorage/AbstractPersistentStorageTests.cs#L378-L394
So we're in a state where we're overwriting an existing checksum with a null checksum. However, very rarely there seems to be a race and reading the checksum back out again returns the original that should have been wiped. | 1.0 | CloudCachePersistentStorageTests.TestReadChecksumProducesLastWrittenChecksum1 failed in CI: Pipelines - Run 20210715.30 (azure.com) - https://dev.azure.com/dnceng/public/_build/results?buildId=1240966&view=ms.vss-test-web.build-test-results-tab&runId=36910020&resultId=215221&paneView=debug
According to infra, this has failed 4 times in the last 30 days.
Failure is:
```
Assert.False() Failure
Expected: False
Actual: True
```
The code for this is here:
https://github.com/dotnet/roslyn/blob/dc3d67460c5632f9ea75df8ed098dc319630ec62/src/VisualStudio/CSharp/Test/PersistentStorage/AbstractPersistentStorageTests.cs#L378-L394
So we're in a state where we're overwriting an existing checksum with a null checksum. However, very rarely there seems to be a race and reading the checksum back out again returns the original that should have been wiped. | non_test | cloudcachepersistentstoragetests failed in ci pipelines run azure com according to infra this has failed times in the last days failure is assert false failure expected false actual true the code for this is here so we re in a state where we re overwriting an existing checksum with a null checksum however very rarely there seems to be a race and reading the checksum back out again returns the original that should have been wiped | 0 |
268,418 | 23,367,776,973 | IssuesEvent | 2022-08-10 16:51:38 | apache/pulsar | https://api.github.com/repos/apache/pulsar | opened | Flaky-test: AdminApi2Test.testDeleteTenant | component/test flaky-tests | ### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
### Example failure
https://github.com/apache/pulsar/runs/7767603609?check_suite_focus=true
### Exception stacktrace
Error: Tests run: 145, Failures: 42, Errors: 0, Skipped: 85, Time elapsed: 143.728 s <<< FAILURE! - in org.apache.pulsar.broker.admin.AdminApi2Test
Error: testDeleteTenant(org.apache.pulsar.broker.admin.AdminApi2Test) Time elapsed: 0.322 s <<< FAILURE!
org.apache.pulsar.client.admin.PulsarAdminException$ServerSideErrorException:
--- An unexpected error occurred in the server ---
Message: org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode = Directory not empty for /managed-ledgers/test-tenant-1/test-ns-1/persistent
Stacktrace:
org.apache.pulsar.metadata.api.MetadataStoreException: org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode = Directory not empty for /managed-ledgers/test-tenant-1/test-ns-1/persistent
at org.apache.pulsar.metadata.impl.ZKMetadataStore.getException(ZKMetadataStore.java:444)
at org.apache.pulsar.metadata.impl.ZKMetadataStore.handleDeleteResult(ZKMetadataStore.java:274)
at org.apache.pulsar.metadata.impl.ZKMetadataStore.lambda$batchOperation$6(ZKMetadataStore.java:186)
at org.apache.zookeeper.MockZooKeeper.multi(MockZooKeeper.java:1009)
at org.apache.pulsar.metadata.impl.ZKMetadataStore.batchOperation(ZKMetadataStore.java:160)
at org.apache.pulsar.metadata.impl.batching.AbstractBatchedMetadataStore.flush(AbstractBatchedMetadataStore.java:117)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode = Directory not empty for /managed-ledgers/test-tenant-1/test-ns-1/persistent
at org.apache.zookeeper.KeeperException.create(KeeperException.java:132)
at org.apache.zookeeper.KeeperException.create(KeeperException.java:54)
at org.apache.pulsar.metadata.impl.ZKMetadataStore.getException(ZKMetadataStore.java:434)
... 12 more
at org.apache.pulsar.client.admin.PulsarAdminException.wrap(PulsarAdminException.java:252)
at org.apache.pulsar.client.admin.internal.BaseResource.sync(BaseResource.java:316)
at org.apache.pulsar.client.admin.internal.NamespacesImpl.deleteNamespace(NamespacesImpl.java:230)
at org.apache.pulsar.broker.admin.AdminApi2Test.testDeleteTenant(AdminApi2Test.java:1370)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:132)
at org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:45)
at org.testng.internal.InvokeMethodRunnable.call(InvokeMethodRunnable.java:73)
at org.testng.internal.InvokeMethodRunnable.call(InvokeMethodRunnable.java:11)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
Suppressed: org.apache.pulsar.client.admin.PulsarAdminException$ServerSideErrorException:
--- An unexpected error occurred in the server ---
Message: org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode = Directory not empty for /managed-ledgers/test-tenant-1/test-ns-1/persistent
Stacktrace:
org.apache.pulsar.metadata.api.MetadataStoreException: org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode = Directory not empty for /managed-ledgers/test-tenant-1/test-ns-1/persistent
at org.apache.pulsar.metadata.impl.ZKMetadataStore.getException(ZKMetadataStore.java:444)
at org.apache.pulsar.metadata.impl.ZKMetadataStore.handleDeleteResult(ZKMetadataStore.java:274)
at org.apache.pulsar.metadata.impl.ZKMetadataStore.lambda$batchOperation$6(ZKMetadataStore.java:186)
at org.apache.zookeeper.MockZooKeeper.multi(MockZooKeeper.java:1009)
at org.apache.pulsar.metadata.impl.ZKMetadataStore.batchOperation(ZKMetadataStore.java:160)
at org.apache.pulsar.metadata.impl.batching.AbstractBatchedMetadataStore.flush(AbstractBatchedMetadataStore.java:117)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode = Directory not empty for /managed-ledgers/test-tenant-1/test-ns-1/persistent
at org.apache.zookeeper.KeeperException.create(KeeperException.java:132)
at org.apache.zookeeper.KeeperException.create(KeeperException.java:54)
at org.apache.pulsar.metadata.impl.ZKMetadataStore.getException(ZKMetadataStore.java:434)
... 12 more
at org.apache.pulsar.client.admin.internal.BaseResource.getApiException(BaseResource.java:237)
at org.apache.pulsar.client.admin.internal.BaseResource$3.failed(BaseResource.java:202)
at org.glassfish.jersey.client.JerseyInvocation$1.failed(JerseyInvocation.java:882)
at org.glassfish.jersey.client.JerseyInvocation$1.completed(JerseyInvocation.java:863)
at org.glassfish.jersey.client.ClientRuntime.processResponse(ClientRuntime.java:229)
at org.glassfish.jersey.client.ClientRuntime.access$200(ClientRuntime.java:62)
at org.glassfish.jersey.client.ClientRuntime$2.lambda$response$0(ClientRuntime.java:173)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:248)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:244)
at org.glassfish.jersey.internal.Errors.process(Errors.java:292)
at org.glassfish.jersey.internal.Errors.process(Errors.java:274)
at org.glassfish.jersey.internal.Errors.process(Errors.java:244)
at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:288)
at org.glassfish.jersey.client.ClientRuntime$2.response(ClientRuntime.java:173)
at org.apache.pulsar.client.admin.internal.http.AsyncHttpConnector.lambda$apply$1(AsyncHttpConnector.java:246)
at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863)
at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:841)
at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2147)
at org.apache.pulsar.client.admin.internal.http.AsyncHttpConnector.lambda$retryOperation$4(AsyncHttpConnector.java:288)
at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863)
at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:841)
at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2147)
at org.asynchttpclient.netty.NettyResponseFuture.loadContent(NettyResponseFuture.java:222)
at org.asynchttpclient.netty.NettyResponseFuture.done(NettyResponseFuture.java:257)
at org.asynchttpclient.netty.handler.AsyncHttpClientHandler.finishUpdate(AsyncHttpClientHandler.java:241)
at org.asynchttpclient.netty.handler.HttpHandler.handleChunk(HttpHandler.java:114)
at org.asynchttpclient.netty.handler.HttpHandler.handleRead(HttpHandler.java:143)
at org.asynchttpclient.netty.handler.AsyncHttpClientHandler.channelRead(AsyncHttpClientHandler.java:78)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:436)
at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:327)
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:299)
at io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:251)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:[1410](https://github.com/apache/pulsar/runs/7767603609?check_suite_focus=true#step:10:1411))
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:722)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:658)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:584)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:496)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:995)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
... 1 more
Caused by: javax.ws.rs.InternalServerErrorException: HTTP 500 org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode = Directory not empty for /managed-ledgers/test-tenant-1/test-ns-1/persistent
at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:960)
at org.glassfish.jersey.client.JerseyInvocation.access$700(JerseyInvocation.java:82)
... 54 more
Caused by: [CIRCULAR REFERENCE: javax.ws.rs.InternalServerErrorException: HTTP 500 org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode = Directory not empty for /managed-ledgers/test-tenant-1/test-ns-1/persistent]
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR! | 2.0 | Flaky-test: AdminApi2Test.testDeleteTenant - ### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
### Example failure
https://github.com/apache/pulsar/runs/7767603609?check_suite_focus=true
### Exception stacktrace
Error: Tests run: 145, Failures: 42, Errors: 0, Skipped: 85, Time elapsed: 143.728 s <<< FAILURE! - in org.apache.pulsar.broker.admin.AdminApi2Test
Error: testDeleteTenant(org.apache.pulsar.broker.admin.AdminApi2Test) Time elapsed: 0.322 s <<< FAILURE!
org.apache.pulsar.client.admin.PulsarAdminException$ServerSideErrorException:
--- An unexpected error occurred in the server ---
Message: org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode = Directory not empty for /managed-ledgers/test-tenant-1/test-ns-1/persistent
Stacktrace:
org.apache.pulsar.metadata.api.MetadataStoreException: org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode = Directory not empty for /managed-ledgers/test-tenant-1/test-ns-1/persistent
at org.apache.pulsar.metadata.impl.ZKMetadataStore.getException(ZKMetadataStore.java:444)
at org.apache.pulsar.metadata.impl.ZKMetadataStore.handleDeleteResult(ZKMetadataStore.java:274)
at org.apache.pulsar.metadata.impl.ZKMetadataStore.lambda$batchOperation$6(ZKMetadataStore.java:186)
at org.apache.zookeeper.MockZooKeeper.multi(MockZooKeeper.java:1009)
at org.apache.pulsar.metadata.impl.ZKMetadataStore.batchOperation(ZKMetadataStore.java:160)
at org.apache.pulsar.metadata.impl.batching.AbstractBatchedMetadataStore.flush(AbstractBatchedMetadataStore.java:117)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode = Directory not empty for /managed-ledgers/test-tenant-1/test-ns-1/persistent
at org.apache.zookeeper.KeeperException.create(KeeperException.java:132)
at org.apache.zookeeper.KeeperException.create(KeeperException.java:54)
at org.apache.pulsar.metadata.impl.ZKMetadataStore.getException(ZKMetadataStore.java:434)
... 12 more
at org.apache.pulsar.client.admin.PulsarAdminException.wrap(PulsarAdminException.java:252)
at org.apache.pulsar.client.admin.internal.BaseResource.sync(BaseResource.java:316)
at org.apache.pulsar.client.admin.internal.NamespacesImpl.deleteNamespace(NamespacesImpl.java:230)
at org.apache.pulsar.broker.admin.AdminApi2Test.testDeleteTenant(AdminApi2Test.java:1370)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:132)
at org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:45)
at org.testng.internal.InvokeMethodRunnable.call(InvokeMethodRunnable.java:73)
at org.testng.internal.InvokeMethodRunnable.call(InvokeMethodRunnable.java:11)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
Suppressed: org.apache.pulsar.client.admin.PulsarAdminException$ServerSideErrorException:
--- An unexpected error occurred in the server ---
Message: org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode = Directory not empty for /managed-ledgers/test-tenant-1/test-ns-1/persistent
Stacktrace:
org.apache.pulsar.metadata.api.MetadataStoreException: org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode = Directory not empty for /managed-ledgers/test-tenant-1/test-ns-1/persistent
at org.apache.pulsar.metadata.impl.ZKMetadataStore.getException(ZKMetadataStore.java:444)
at org.apache.pulsar.metadata.impl.ZKMetadataStore.handleDeleteResult(ZKMetadataStore.java:274)
at org.apache.pulsar.metadata.impl.ZKMetadataStore.lambda$batchOperation$6(ZKMetadataStore.java:186)
at org.apache.zookeeper.MockZooKeeper.multi(MockZooKeeper.java:1009)
at org.apache.pulsar.metadata.impl.ZKMetadataStore.batchOperation(ZKMetadataStore.java:160)
at org.apache.pulsar.metadata.impl.batching.AbstractBatchedMetadataStore.flush(AbstractBatchedMetadataStore.java:117)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode = Directory not empty for /managed-ledgers/test-tenant-1/test-ns-1/persistent
at org.apache.zookeeper.KeeperException.create(KeeperException.java:132)
at org.apache.zookeeper.KeeperException.create(KeeperException.java:54)
at org.apache.pulsar.metadata.impl.ZKMetadataStore.getException(ZKMetadataStore.java:434)
... 12 more
at org.apache.pulsar.client.admin.internal.BaseResource.getApiException(BaseResource.java:237)
at org.apache.pulsar.client.admin.internal.BaseResource$3.failed(BaseResource.java:202)
at org.glassfish.jersey.client.JerseyInvocation$1.failed(JerseyInvocation.java:882)
at org.glassfish.jersey.client.JerseyInvocation$1.completed(JerseyInvocation.java:863)
at org.glassfish.jersey.client.ClientRuntime.processResponse(ClientRuntime.java:229)
at org.glassfish.jersey.client.ClientRuntime.access$200(ClientRuntime.java:62)
at org.glassfish.jersey.client.ClientRuntime$2.lambda$response$0(ClientRuntime.java:173)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:248)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:244)
at org.glassfish.jersey.internal.Errors.process(Errors.java:292)
at org.glassfish.jersey.internal.Errors.process(Errors.java:274)
at org.glassfish.jersey.internal.Errors.process(Errors.java:244)
at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:288)
at org.glassfish.jersey.client.ClientRuntime$2.response(ClientRuntime.java:173)
at org.apache.pulsar.client.admin.internal.http.AsyncHttpConnector.lambda$apply$1(AsyncHttpConnector.java:246)
at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863)
at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:841)
at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2147)
at org.apache.pulsar.client.admin.internal.http.AsyncHttpConnector.lambda$retryOperation$4(AsyncHttpConnector.java:288)
at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863)
at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:841)
at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2147)
at org.asynchttpclient.netty.NettyResponseFuture.loadContent(NettyResponseFuture.java:222)
at org.asynchttpclient.netty.NettyResponseFuture.done(NettyResponseFuture.java:257)
at org.asynchttpclient.netty.handler.AsyncHttpClientHandler.finishUpdate(AsyncHttpClientHandler.java:241)
at org.asynchttpclient.netty.handler.HttpHandler.handleChunk(HttpHandler.java:114)
at org.asynchttpclient.netty.handler.HttpHandler.handleRead(HttpHandler.java:143)
at org.asynchttpclient.netty.handler.AsyncHttpClientHandler.channelRead(AsyncHttpClientHandler.java:78)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:436)
at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:327)
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:299)
at io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:251)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:[1410](https://github.com/apache/pulsar/runs/7767603609?check_suite_focus=true#step:10:1411))
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:722)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:658)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:584)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:496)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:995)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
... 1 more
Caused by: javax.ws.rs.InternalServerErrorException: HTTP 500 org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode = Directory not empty for /managed-ledgers/test-tenant-1/test-ns-1/persistent
at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:960)
at org.glassfish.jersey.client.JerseyInvocation.access$700(JerseyInvocation.java:82)
... 54 more
Caused by: [CIRCULAR REFERENCE: javax.ws.rs.InternalServerErrorException: HTTP 500 org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode = Directory not empty for /managed-ledgers/test-tenant-1/test-ns-1/persistent]
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR! | test | flaky test testdeletetenant search before asking i searched in the and found nothing similar example failure exception stacktrace error tests run failures errors skipped time elapsed s failure in org apache pulsar broker admin error testdeletetenant org apache pulsar broker admin time elapsed s failure org apache pulsar client admin pulsaradminexception serversideerrorexception an unexpected error occurred in the server message org apache zookeeper keeperexception notemptyexception keepererrorcode directory not empty for managed ledgers test tenant test ns persistent stacktrace org apache pulsar metadata api metadatastoreexception org apache zookeeper keeperexception notemptyexception keepererrorcode directory not empty for managed ledgers test tenant test ns persistent at org apache pulsar metadata impl zkmetadatastore getexception zkmetadatastore java at org apache pulsar metadata impl zkmetadatastore handledeleteresult zkmetadatastore java at org apache pulsar metadata impl zkmetadatastore lambda batchoperation zkmetadatastore java at org apache zookeeper mockzookeeper multi mockzookeeper java at org apache pulsar metadata impl zkmetadatastore batchoperation zkmetadatastore java at org apache pulsar metadata impl batching abstractbatchedmetadatastore flush abstractbatchedmetadatastore java at java base java util concurrent executors runnableadapter call executors java at java base java util concurrent futuretask runandreset futuretask java at java base java util concurrent scheduledthreadpoolexecutor scheduledfuturetask run scheduledthreadpoolexecutor java at java base java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java base java util concurrent threadpoolexecutor worker run threadpoolexecutor java at io netty util concurrent fastthreadlocalrunnable run fastthreadlocalrunnable java at java base java lang thread run thread java caused by org apache zookeeper keeperexception notemptyexception keepererrorcode directory not empty for managed ledgers test tenant test ns persistent at org apache zookeeper keeperexception create keeperexception java at org apache zookeeper keeperexception create keeperexception java at org apache pulsar metadata impl zkmetadatastore getexception zkmetadatastore java more at org apache pulsar client admin pulsaradminexception wrap pulsaradminexception java at org apache pulsar client admin internal baseresource sync baseresource java at org apache pulsar client admin internal namespacesimpl deletenamespace namespacesimpl java at org apache pulsar broker admin testdeletetenant 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 invokemethodrunnable runone invokemethodrunnable java at org testng internal invokemethodrunnable call invokemethodrunnable java at org testng internal invokemethodrunnable call invokemethodrunnable java at java base java util concurrent futuretask run futuretask 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 suppressed org apache pulsar client admin pulsaradminexception serversideerrorexception an unexpected error occurred in the server message org apache zookeeper keeperexception notemptyexception keepererrorcode directory not empty for managed ledgers test tenant test ns persistent stacktrace org apache pulsar metadata api metadatastoreexception org apache zookeeper keeperexception notemptyexception keepererrorcode directory not empty for managed ledgers test tenant test ns persistent at org apache pulsar metadata impl zkmetadatastore getexception zkmetadatastore java at org apache pulsar metadata impl zkmetadatastore handledeleteresult zkmetadatastore java at org apache pulsar metadata impl zkmetadatastore lambda batchoperation zkmetadatastore java at org apache zookeeper mockzookeeper multi mockzookeeper java at org apache pulsar metadata impl zkmetadatastore batchoperation zkmetadatastore java at org apache pulsar metadata impl batching abstractbatchedmetadatastore flush abstractbatchedmetadatastore java at java base java util concurrent executors runnableadapter call executors java at java base java util concurrent futuretask runandreset futuretask java at java base java util concurrent scheduledthreadpoolexecutor scheduledfuturetask run scheduledthreadpoolexecutor java at java base java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java base java util concurrent threadpoolexecutor worker run threadpoolexecutor java at io netty util concurrent fastthreadlocalrunnable run fastthreadlocalrunnable java at java base java lang thread run thread java caused by org apache zookeeper keeperexception notemptyexception keepererrorcode directory not empty for managed ledgers test tenant test ns persistent at org apache zookeeper keeperexception create keeperexception java at org apache zookeeper keeperexception create keeperexception java at org apache pulsar metadata impl zkmetadatastore getexception zkmetadatastore java more at org apache pulsar client admin internal baseresource getapiexception baseresource java at org apache pulsar client admin internal baseresource failed baseresource java at org glassfish jersey client jerseyinvocation failed jerseyinvocation java at org glassfish jersey client jerseyinvocation completed jerseyinvocation java at org glassfish jersey client clientruntime processresponse clientruntime java at org glassfish jersey client clientruntime access clientruntime java at org glassfish jersey client clientruntime lambda response clientruntime java at org glassfish jersey internal errors call errors java at org glassfish jersey internal errors call errors java at org glassfish jersey internal errors process errors java at org glassfish jersey internal errors process errors java at org glassfish jersey internal errors process errors java at org glassfish jersey process internal requestscope runinscope requestscope java at org glassfish jersey client clientruntime response clientruntime java at org apache pulsar client admin internal http asynchttpconnector lambda apply asynchttpconnector java at java base java util concurrent completablefuture uniwhencomplete completablefuture java at java base java util concurrent completablefuture uniwhencomplete tryfire completablefuture java at java base java util concurrent completablefuture postcomplete completablefuture java at java base java util concurrent completablefuture complete completablefuture java at org apache pulsar client admin internal http asynchttpconnector lambda retryoperation asynchttpconnector java at java base java util concurrent completablefuture uniwhencomplete completablefuture java at java base java util concurrent completablefuture uniwhencomplete tryfire completablefuture java at java base java util concurrent completablefuture postcomplete completablefuture java at java base java util concurrent completablefuture complete completablefuture java at org asynchttpclient netty nettyresponsefuture loadcontent nettyresponsefuture java at org asynchttpclient netty nettyresponsefuture done nettyresponsefuture java at org asynchttpclient netty handler asynchttpclienthandler finishupdate asynchttpclienthandler java at org asynchttpclient netty handler httphandler handlechunk httphandler java at org asynchttpclient netty handler httphandler handleread httphandler java at org asynchttpclient netty handler asynchttpclienthandler channelread asynchttpclienthandler java at io netty channel abstractchannelhandlercontext invokechannelread abstractchannelhandlercontext java at io netty channel abstractchannelhandlercontext invokechannelread abstractchannelhandlercontext java at io netty channel abstractchannelhandlercontext firechannelread abstractchannelhandlercontext java at io netty handler codec messagetomessagedecoder channelread messagetomessagedecoder java at io netty channel abstractchannelhandlercontext invokechannelread abstractchannelhandlercontext java at io netty channel abstractchannelhandlercontext invokechannelread abstractchannelhandlercontext java at io netty channel abstractchannelhandlercontext firechannelread abstractchannelhandlercontext java at io netty channel combinedchannelduplexhandler delegatingchannelhandlercontext firechannelread combinedchannelduplexhandler java at io netty handler codec bytetomessagedecoder firechannelread bytetomessagedecoder java at io netty handler codec bytetomessagedecoder channelread bytetomessagedecoder java at io netty channel combinedchannelduplexhandler channelread combinedchannelduplexhandler java at io netty channel abstractchannelhandlercontext invokechannelread abstractchannelhandlercontext java at io netty channel abstractchannelhandlercontext invokechannelread abstractchannelhandlercontext java at io netty channel abstractchannelhandlercontext firechannelread abstractchannelhandlercontext java at io netty channel defaultchannelpipeline headcontext channelread defaultchannelpipeline java at io netty channel abstractchannelhandlercontext invokechannelread abstractchannelhandlercontext java at io netty channel abstractchannelhandlercontext invokechannelread abstractchannelhandlercontext java at io netty channel defaultchannelpipeline firechannelread defaultchannelpipeline java at io netty channel nio abstractniobytechannel niobyteunsafe read abstractniobytechannel java at io netty channel nio nioeventloop processselectedkey nioeventloop java at io netty channel nio nioeventloop processselectedkeysoptimized nioeventloop java at io netty channel nio nioeventloop processselectedkeys nioeventloop java at io netty channel nio nioeventloop run nioeventloop java at io netty util concurrent singlethreadeventexecutor run singlethreadeventexecutor java at io netty util internal threadexecutormap run threadexecutormap java at io netty util concurrent fastthreadlocalrunnable run fastthreadlocalrunnable java more caused by javax ws rs internalservererrorexception http org apache zookeeper keeperexception notemptyexception keepererrorcode directory not empty for managed ledgers test tenant test ns persistent at org glassfish jersey client jerseyinvocation converttoexception jerseyinvocation java at org glassfish jersey client jerseyinvocation access jerseyinvocation java more caused by are you willing to submit a pr i m willing to submit a pr | 1 |
252,316 | 21,570,039,947 | IssuesEvent | 2022-05-02 06:58:07 | mozilla-mobile/focus-android | https://api.github.com/repos/mozilla-mobile/focus-android | closed | Intermittent UI test failure - < SwitchContextTest.switchFromSettingsToFocusTest> | eng:ui-test eng:intermittent-test | ### Firebase Test Run: [Firebase link](https://console.firebase.google.com/u/0/project/moz-focus-android/testlab/histories/bh.2189b040bbce6d5a/matrices/7628676476349676692/executions/bs.e1b4a1120887bb24/testcases/1)
### Stacktrace:
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at org.mozilla.focus.activity.robots.NotificationRobot.verifySystemNotificationExists(NotificationRobot.kt:51)
at org.mozilla.focus.activity.SwitchContextTest$switchFromSettingsToFocusTest$3.invoke(SwitchContextTest.kt:145)
at org.mozilla.focus.activity.SwitchContextTest$switchFromSettingsToFocusTest$3.invoke(SwitchContextTest.kt:144)
at org.mozilla.focus.activity.robots.NotificationRobotKt.notificationTray(NotificationRobot.kt:128)
at org.mozilla.focus.activity.SwitchContextTest.switchFromSettingsToFocusTest(SwitchContextTest.kt:144)
### Build: 3/15 Main
| 2.0 | Intermittent UI test failure - < SwitchContextTest.switchFromSettingsToFocusTest> - ### Firebase Test Run: [Firebase link](https://console.firebase.google.com/u/0/project/moz-focus-android/testlab/histories/bh.2189b040bbce6d5a/matrices/7628676476349676692/executions/bs.e1b4a1120887bb24/testcases/1)
### Stacktrace:
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at org.mozilla.focus.activity.robots.NotificationRobot.verifySystemNotificationExists(NotificationRobot.kt:51)
at org.mozilla.focus.activity.SwitchContextTest$switchFromSettingsToFocusTest$3.invoke(SwitchContextTest.kt:145)
at org.mozilla.focus.activity.SwitchContextTest$switchFromSettingsToFocusTest$3.invoke(SwitchContextTest.kt:144)
at org.mozilla.focus.activity.robots.NotificationRobotKt.notificationTray(NotificationRobot.kt:128)
at org.mozilla.focus.activity.SwitchContextTest.switchFromSettingsToFocusTest(SwitchContextTest.kt:144)
### Build: 3/15 Main
| test | intermittent ui test failure firebase test run stacktrace java lang assertionerror at org junit assert fail assert java at org junit assert asserttrue assert java at org junit assert asserttrue assert java at org mozilla focus activity robots notificationrobot verifysystemnotificationexists notificationrobot kt at org mozilla focus activity switchcontexttest switchfromsettingstofocustest invoke switchcontexttest kt at org mozilla focus activity switchcontexttest switchfromsettingstofocustest invoke switchcontexttest kt at org mozilla focus activity robots notificationrobotkt notificationtray notificationrobot kt at org mozilla focus activity switchcontexttest switchfromsettingstofocustest switchcontexttest kt build main | 1 |
4,288 | 2,546,830,552 | IssuesEvent | 2015-01-30 04:53:05 | mmisw/mmiorr | https://api.github.com/repos/mmisw/mmiorr | opened | update AllegroGraph | enhancement ont Priority-High triplestore | We've been using AG 4.11 for a good while now. In general, not too bad (at least compared with previous releases we used, #281), but we have recently started to note some memory issues (lots of consumed memory that required a restart of the AG server). Also, during some of the work with the [orr-ont](https://github.com/mmisw/orr-ont) prototype, we have noted issues with the AG HTTP endpoint. So, seems about time to do an update, not to mention the many bug fixes described in the [AG release notes](http://franz.com/agraph/support/documentation/5.0/release-notes.html). So, the request here is to update the AG server to v5.0, as well as the corresponding libraries used by the Ont code. | 1.0 | update AllegroGraph - We've been using AG 4.11 for a good while now. In general, not too bad (at least compared with previous releases we used, #281), but we have recently started to note some memory issues (lots of consumed memory that required a restart of the AG server). Also, during some of the work with the [orr-ont](https://github.com/mmisw/orr-ont) prototype, we have noted issues with the AG HTTP endpoint. So, seems about time to do an update, not to mention the many bug fixes described in the [AG release notes](http://franz.com/agraph/support/documentation/5.0/release-notes.html). So, the request here is to update the AG server to v5.0, as well as the corresponding libraries used by the Ont code. | non_test | update allegrograph we ve been using ag for a good while now in general not too bad at least compared with previous releases we used but we have recently started to note some memory issues lots of consumed memory that required a restart of the ag server also during some of the work with the prototype we have noted issues with the ag http endpoint so seems about time to do an update not to mention the many bug fixes described in the so the request here is to update the ag server to as well as the corresponding libraries used by the ont code | 0 |
248,043 | 20,990,896,819 | IssuesEvent | 2022-03-29 09:12:02 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | ccl/backupccl: TestBackupRestoreDataDriven failed | C-test-failure O-robot T-bulkio T-kv branch-release-22.1 | ccl/backupccl.TestBackupRestoreDataDriven [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=4605274&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=4605274&tab=artifacts#/) on release-22.1 @ [d7252106b166f23d791a4d677afdbc46b6b059ae](https://github.com/cockroachdb/cockroach/commits/d7252106b166f23d791a4d677afdbc46b6b059ae):
```
exec-sql [0 args]
CREATE TABLE cfs (a INT PRIMARY KEY, b STRING, c STRING, d STRING, FAMILY (b), FAMILY (c));
----
backup_test.go:283:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3160/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/cockroach/pkg/ccl/backupccl/testdata/backup-restore/column-families:16:
exec-sql [0 args]
INSERT INTO cfs SELECT x, repeat('abc', 100), repeat('abc', 100) FROM generate_series(0, 3) AS x;
----
backup_test.go:283:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3160/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/cockroach/pkg/ccl/backupccl/testdata/backup-restore/column-families:20:
exec-sql [0 args]
ALTER TABLE cfs SPLIT AT SELECT a FROM cfs;
----
backup_test.go:283:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3160/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/cockroach/pkg/ccl/backupccl/testdata/backup-restore/column-families:24:
exec-sql [0 args]
-- Split the output files very small to catch output SSTs mid-row.
SET CLUSTER SETTING bulkio.backup.file_size = '1';
SET CLUSTER SETTING kv.bulk_sst.target_size = '1';
SET CLUSTER SETTING bulkio.backup.merge_file_buffer_size = '1MiB';
----
backup_test.go:283:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3160/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/cockroach/pkg/ccl/backupccl/testdata/backup-restore/column-families:31:
exec-sql [0 args]
BACKUP cfs TO 'nodelocal://1/foo';
----
backup_test.go:283:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3160/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/cockroach/pkg/ccl/backupccl/testdata/backup-restore/column-families:35:
exec-sql [0 args]
CREATE DATABASE r1;
----
backup_test.go:283:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3160/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/cockroach/pkg/ccl/backupccl/testdata/backup-restore/column-families:39:
exec-sql [0 args]
RESTORE cfs FROM 'nodelocal://1/foo' WITH into_db='r1';
----
backup_test.go:283:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3160/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/cockroach/pkg/ccl/backupccl/testdata/backup-restore/column-families:43:
query-sql [0 args]
SELECT max(length(start_key)) FROM [SHOW RANGES FROM TABLE orig.cfs];
----
2
backup_test.go:283:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3160/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/cockroach/pkg/ccl/backupccl/testdata/backup-restore/column-families:52: SELECT max(length(start_key)) FROM [SHOW RANGES FROM TABLE r1.cfs];
expected:
2
found:
<nil>
--- FAIL: TestBackupRestoreDataDriven/column-families (4.64s)
```
<details><summary>Help</summary>
<p>
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
Parameters in this failure:
- TAGS=bazel,gss
</p>
</details>
<details><summary>Same failure on other branches</summary>
<p>
- #77264 ccl/backupccl: TestBackupRestoreDataDriven failed [C-test-failure O-robot T-bulkio branch-master]
</p>
</details>
/cc @cockroachdb/bulk-io
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestBackupRestoreDataDriven.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-13947 | 1.0 | ccl/backupccl: TestBackupRestoreDataDriven failed - ccl/backupccl.TestBackupRestoreDataDriven [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=4605274&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=4605274&tab=artifacts#/) on release-22.1 @ [d7252106b166f23d791a4d677afdbc46b6b059ae](https://github.com/cockroachdb/cockroach/commits/d7252106b166f23d791a4d677afdbc46b6b059ae):
```
exec-sql [0 args]
CREATE TABLE cfs (a INT PRIMARY KEY, b STRING, c STRING, d STRING, FAMILY (b), FAMILY (c));
----
backup_test.go:283:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3160/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/cockroach/pkg/ccl/backupccl/testdata/backup-restore/column-families:16:
exec-sql [0 args]
INSERT INTO cfs SELECT x, repeat('abc', 100), repeat('abc', 100) FROM generate_series(0, 3) AS x;
----
backup_test.go:283:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3160/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/cockroach/pkg/ccl/backupccl/testdata/backup-restore/column-families:20:
exec-sql [0 args]
ALTER TABLE cfs SPLIT AT SELECT a FROM cfs;
----
backup_test.go:283:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3160/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/cockroach/pkg/ccl/backupccl/testdata/backup-restore/column-families:24:
exec-sql [0 args]
-- Split the output files very small to catch output SSTs mid-row.
SET CLUSTER SETTING bulkio.backup.file_size = '1';
SET CLUSTER SETTING kv.bulk_sst.target_size = '1';
SET CLUSTER SETTING bulkio.backup.merge_file_buffer_size = '1MiB';
----
backup_test.go:283:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3160/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/cockroach/pkg/ccl/backupccl/testdata/backup-restore/column-families:31:
exec-sql [0 args]
BACKUP cfs TO 'nodelocal://1/foo';
----
backup_test.go:283:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3160/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/cockroach/pkg/ccl/backupccl/testdata/backup-restore/column-families:35:
exec-sql [0 args]
CREATE DATABASE r1;
----
backup_test.go:283:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3160/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/cockroach/pkg/ccl/backupccl/testdata/backup-restore/column-families:39:
exec-sql [0 args]
RESTORE cfs FROM 'nodelocal://1/foo' WITH into_db='r1';
----
backup_test.go:283:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3160/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/cockroach/pkg/ccl/backupccl/testdata/backup-restore/column-families:43:
query-sql [0 args]
SELECT max(length(start_key)) FROM [SHOW RANGES FROM TABLE orig.cfs];
----
2
backup_test.go:283:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3160/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/cockroach/pkg/ccl/backupccl/testdata/backup-restore/column-families:52: SELECT max(length(start_key)) FROM [SHOW RANGES FROM TABLE r1.cfs];
expected:
2
found:
<nil>
--- FAIL: TestBackupRestoreDataDriven/column-families (4.64s)
```
<details><summary>Help</summary>
<p>
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
Parameters in this failure:
- TAGS=bazel,gss
</p>
</details>
<details><summary>Same failure on other branches</summary>
<p>
- #77264 ccl/backupccl: TestBackupRestoreDataDriven failed [C-test-failure O-robot T-bulkio branch-master]
</p>
</details>
/cc @cockroachdb/bulk-io
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestBackupRestoreDataDriven.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-13947 | test | ccl backupccl testbackuprestoredatadriven failed ccl backupccl testbackuprestoredatadriven with on release exec sql create table cfs a int primary key b string c string d string family b family c backup test go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg ccl backupccl backupccl test backupccl test runfiles cockroach pkg ccl backupccl testdata backup restore column families exec sql insert into cfs select x repeat abc repeat abc from generate series as x backup test go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg ccl backupccl backupccl test backupccl test runfiles cockroach pkg ccl backupccl testdata backup restore column families exec sql alter table cfs split at select a from cfs backup test go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg ccl backupccl backupccl test backupccl test runfiles cockroach pkg ccl backupccl testdata backup restore column families exec sql split the output files very small to catch output ssts mid row set cluster setting bulkio backup file size set cluster setting kv bulk sst target size set cluster setting bulkio backup merge file buffer size backup test go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg ccl backupccl backupccl test backupccl test runfiles cockroach pkg ccl backupccl testdata backup restore column families exec sql backup cfs to nodelocal foo backup test go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg ccl backupccl backupccl test backupccl test runfiles cockroach pkg ccl backupccl testdata backup restore column families exec sql create database backup test go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg ccl backupccl backupccl test backupccl test runfiles cockroach pkg ccl backupccl testdata backup restore column families exec sql restore cfs from nodelocal foo with into db backup test go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg ccl backupccl backupccl test backupccl test runfiles cockroach pkg ccl backupccl testdata backup restore column families query sql select max length start key from backup test go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg ccl backupccl backupccl test backupccl test runfiles cockroach pkg ccl backupccl testdata backup restore column families select max length start key from expected found fail testbackuprestoredatadriven column families help see also parameters in this failure tags bazel gss same failure on other branches ccl backupccl testbackuprestoredatadriven failed cc cockroachdb bulk io jira issue crdb | 1 |
49,866 | 12,421,456,258 | IssuesEvent | 2020-05-23 16:57:12 | supercollider/supercollider | https://api.github.com/repos/supercollider/supercollider | closed | scsynth throws seg fault on system < 10.10.5 being compiled on 10.10.5 / Xcode 7.2 | bug comp: build | I compiled SC on an OS X 10.10.5 system w/ Xcode 7.2 with a deployment target of 10.7.
Launching scsynth on my main system w/ 10.9.5 it crashes with a segmentation fault.
I recompiled with:
cmake -G Xcode -DCMAKE_BUILD_TYPE="Debug" -DCMAKE_OSX_DEPLOYMENT_TARGET="10.7" -DCMAKE_PREFIX_PATH=$(brew --prefix qt5) -DSUPERNOVA=ON .. && cmake --build . --target install --config Debug
sent lldb on the hunt before launching scsynth from within the IDE:
```
$ lldb
(lldb) process attach --name scsynth --waitfor
Process 19414 stopped
Executable module set to "/Users/mz/dev/sc3.git/SuperCollider-debug/SuperCollider.app/Contents/Resources/../MacOS/scsynth".
Architecture set to: x86_64-apple-macosx.
(lldb) process continue
Process 19414 resuming
Process 19414 stopped
* thread #1: tid = 0x82ab6, 0x000000010f159950, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x10f159950)
frame #0: 0x000000010f159950
error: memory read failed for 0x10f159800
(lldb) thread backtrace all
* thread #1: tid = 0x82ab6, 0x000000010f159950, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x10f159950)
* frame #0: 0x000000010f159950
frame #1: 0x00007fff89f12978 Foundation`+[NSURL(NSURL) allocWithZone:] + 32
frame #2: 0x00007fff89f20bea Foundation`+[NSURL(NSURL) fileURLWithPath:isDirectory:] + 28
frame #3: 0x000000010d52399b scsynth`sc_ResolveIfAlias(char const*, char*, bool&, int) + 235
frame #4: 0x000000010d524340 scsynth`sc_ReadDir(SC_DirHandle*, char const*, char*, bool&) + 416
frame #5: 0x000000010d55d0c1 scsynth`PlugIn_LoadDir(char const*, bool) + 225
frame #6: 0x000000010d55ced8 scsynth`initialize_library(char const*) + 712
frame #7: 0x000000010d5746df scsynth`World_New + 63
frame #8: 0x000000010d51cb53 scsynth`main + 4723
frame #9: 0x000000010d51b7e4 scsynth`start + 52
thread #2: tid = 0x82af5, 0x00007fff8d923e6a libsystem_kernel.dylib`__workq_kernreturn + 10
frame #0: 0x00007fff8d923e6a libsystem_kernel.dylib`__workq_kernreturn + 10
frame #1: 0x00007fff885d1f08 libsystem_pthread.dylib`_pthread_wqthread + 330
frame #2: 0x00007fff885d4fb9 libsystem_pthread.dylib`start_wqthread + 13
thread #3: tid = 0x82af6, 0x00007fff8d924662 libsystem_kernel.dylib`kevent64 + 10, queue = 'com.apple.libdispatch-manager'
frame #0: 0x00007fff8d924662 libsystem_kernel.dylib`kevent64 + 10
frame #1: 0x00007fff873ab421 libdispatch.dylib`_dispatch_mgr_invoke + 239
frame #2: 0x00007fff873ab136 libdispatch.dylib`_dispatch_mgr_thread + 52
thread #4: tid = 0x82af7, 0x00007fff8d923e6a libsystem_kernel.dylib`__workq_kernreturn + 10
frame #0: 0x00007fff8d923e6a libsystem_kernel.dylib`__workq_kernreturn + 10
frame #1: 0x00007fff885d1f08 libsystem_pthread.dylib`_pthread_wqthread + 330
frame #2: 0x00007fff885d4fb9 libsystem_pthread.dylib`start_wqthread + 13
thread #5: tid = 0x82af8, 0x00007fff8d923716 libsystem_kernel.dylib`__psynch_cvwait + 10
frame #0: 0x00007fff8d923716 libsystem_kernel.dylib`__psynch_cvwait + 10
frame #1: 0x00007fff885d2c3b libsystem_pthread.dylib`_pthread_cond_wait + 727
frame #2: 0x00007fff8bc0dd43 libc++.1.dylib`std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
frame #3: 0x000000010ecc7b49 DiskIO_UGens.scx`void std::__1::condition_variable_any::wait<std::__1::unique_lock<std::__1::mutex> >(std::__1::unique_lock<std::__1::mutex>&) + 585
frame #4: 0x000000010ecc785a DiskIO_UGens.scx`SC_SyncCondition::WaitEach() + 122
frame #5: 0x000000010ecc5158 DiskIO_UGens.scx`(anonymous namespace)::DiskIOThread::ioThreadFunc() + 152
frame #6: 0x000000010ecc6528 DiskIO_UGens.scx`void* std::__1::__thread_proxy<std::__1::tuple<std::__1::__bind<void ((anonymous namespace)::DiskIOThread::*)(), (anonymous namespace)::DiskIOThread*> > >(void*) + 616
frame #7: 0x00007fff885d0899 libsystem_pthread.dylib`_pthread_body + 138
frame #8: 0x00007fff885d072a libsystem_pthread.dylib`_pthread_start + 137
frame #9: 0x00007fff885d4fc9 libsystem_pthread.dylib`thread_start + 13
thread #6: tid = 0x82afc, 0x00007fff94bd34c5 CoreFoundation`_parseComponents + 213
frame #0: 0x00007fff94bd34c5 CoreFoundation`_parseComponents + 213
frame #1: 0x00007fff94bd334a CoreFoundation`_CFURLInitWithURLString + 1354
frame #2: 0x00007fff94bdb578 CoreFoundation`CFURLCreateWithString + 152
frame #3: 0x00007fff94bdb65f CoreFoundation`___CFBundleCopyInfoDictionaryInDirectoryWithVersion_block_invoke + 191
frame #4: 0x00007fff94bd8994 CoreFoundation`_CFIterateDirectory + 212
frame #5: 0x00007fff94bdb273 CoreFoundation`_CFBundleCopyInfoDictionaryInDirectoryWithVersion + 627
frame #6: 0x00007fff94bdaedd CoreFoundation`CFBundleGetInfoDictionary + 141
frame #7: 0x00007fff94bd772b CoreFoundation`_CFBundleCreate + 827
frame #8: 0x00007fff94c1ba89 CoreFoundation`_CFBundleEnsureBundleExistsForImagePath + 89
frame #9: 0x00007fff94c1b773 CoreFoundation`CFBundleGetBundleWithIdentifier + 115
frame #10: 0x00007fff947ea0a6 HIToolbox`HLTBGetBundle + 28
frame #11: 0x00007fff947e9fd2 HIToolbox`HIGetScaleFactor + 95
frame #12: 0x00007fff94814479 HIToolbox`GetMBarHeightInPixels + 30
frame #13: 0x00007fff94814452 HIToolbox`_HIMenuGetMenuBarHeight + 32
frame #14: 0x00007fff912a7cf5 AppKit`_NSMenuBarHeight + 14
frame #15: 0x00007fff912a7c7f AppKit`-[NSScreen _saveVisibleFrameAtIndex:] + 96
frame #16: 0x00007fff912a7bb8 AppKit`+[NSScreen _updateSavedFramesLocked] + 191
frame #17: 0x00007fff912a7a17 AppKit`+[NSScreen _resetScreensLocked] + 1412
frame #18: 0x00007fff912a72e4 AppKit`+[NSScreen _screensLocked] + 301
frame #19: 0x00007fff912a916b AppKit`+[NSScreen _zeroScreenHeight] + 73
frame #20: 0x00007fff9136ba48 AppKit`+[NSEvent mouseLocation] + 48
frame #21: 0x000000010f092da9 UIUGens.scx`gstate_update_func() + 89
frame #22: 0x000000010f094d36 UIUGens.scx`void* std::__1::__thread_proxy<std::__1::tuple<void (*)()> >(void*) + 390
frame #23: 0x00007fff885d0899 libsystem_pthread.dylib`_pthread_body + 138
frame #24: 0x00007fff885d072a libsystem_pthread.dylib`_pthread_start + 137
frame #25: 0x00007fff885d4fc9 libsystem_pthread.dylib`thread_start + 13
(lldb)
```
(I hope that's useful info - for me that's completely uncharted territory here)
Since the IDE's post window only returns "ERROR: server failed to start" I launched the server from the shell to realise the seg fault.
Doing so I noticed that scsynth won't crash when located outside the package.
i.e.:
```
cox:~ mz$ pwd
/Users/mz
cox:~ mz$ /Users/mz/dev/sc3.git/SuperCollider-debug/SuperCollider.app/Contents/MacOS/scsynth -u 57110
Segmentation fault: 11
cox:~ mz$ /Users/mz/Desktop/scsynth -u 57110
Faust: supercollider.cpp: sc_api_version = 2
Faust: FaustGreyholeRaw numControls=7
Faust: supercollider.cpp: sc_api_version = 2
Faust: FaustJPverbRaw numControls=11
Found 0 LADSPA plugins
exception in GrafDef_Load: UGen 'WhiteNoise' not installed.
while reading file '/Users/mz/Library/Application Support/SuperCollider/synthdefs/bped_noise.scsyndef'
exception in GrafDef_Load: UGen 'Control' not installed.
while reading file '/Users/mz/Library/Application Support/SuperCollider/synthdefs/fsynth.scsyndef'
exception in GrafDef_Load: UGen 'Control' not installed.
while reading file '/Users/mz/Library/Application Support/SuperCollider/synthdefs/Help-SynthDef.scsyndef'
exception in GrafDef_Load: UGen 'Control' not installed.
while reading file '/Users/mz/Library/Application Support/SuperCollider/synthdefs/rec-ins.scsyndef'
exception in GrafDef_Load: UGen 'ExpRand' not installed.
while reading file '/Users/mz/Library/Application Support/SuperCollider/synthdefs/sincluster.scsyndef'
Number of Devices: 5
0 : "Built-in Microph"
1 : "Built-in Input"
2 : "Built-in Output"
3 : "Soundflower (2ch)"
4 : "Soundflower (64ch)"
"Built-in Input" Input Device
Streams: 1
0 channels 2
"Built-in Output" Output Device
Streams: 1
0 channels 2
SC_AudioDriver: sample rate = 96000.000000, driver's block size = 512
PublishPortToRendezvous 0 5855
SuperCollider 3 server ready (debug build).
```
This behaviour is reproducible.
Of course I recompiled with target 10.9 which doesn't help.
The very same binary runs o.k. on the 10.10.5 system where it's been compiled on.
The very same source tree compiles and runs o.k. on 10.9.5 / Xcode 6.2.
AFAIK travis compiles on 10.9.5 for a target of 10.7 - w/o problems, so far.
sclang and supernova are apparently fine, AFAICT.
| 1.0 | scsynth throws seg fault on system < 10.10.5 being compiled on 10.10.5 / Xcode 7.2 - I compiled SC on an OS X 10.10.5 system w/ Xcode 7.2 with a deployment target of 10.7.
Launching scsynth on my main system w/ 10.9.5 it crashes with a segmentation fault.
I recompiled with:
cmake -G Xcode -DCMAKE_BUILD_TYPE="Debug" -DCMAKE_OSX_DEPLOYMENT_TARGET="10.7" -DCMAKE_PREFIX_PATH=$(brew --prefix qt5) -DSUPERNOVA=ON .. && cmake --build . --target install --config Debug
sent lldb on the hunt before launching scsynth from within the IDE:
```
$ lldb
(lldb) process attach --name scsynth --waitfor
Process 19414 stopped
Executable module set to "/Users/mz/dev/sc3.git/SuperCollider-debug/SuperCollider.app/Contents/Resources/../MacOS/scsynth".
Architecture set to: x86_64-apple-macosx.
(lldb) process continue
Process 19414 resuming
Process 19414 stopped
* thread #1: tid = 0x82ab6, 0x000000010f159950, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x10f159950)
frame #0: 0x000000010f159950
error: memory read failed for 0x10f159800
(lldb) thread backtrace all
* thread #1: tid = 0x82ab6, 0x000000010f159950, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x10f159950)
* frame #0: 0x000000010f159950
frame #1: 0x00007fff89f12978 Foundation`+[NSURL(NSURL) allocWithZone:] + 32
frame #2: 0x00007fff89f20bea Foundation`+[NSURL(NSURL) fileURLWithPath:isDirectory:] + 28
frame #3: 0x000000010d52399b scsynth`sc_ResolveIfAlias(char const*, char*, bool&, int) + 235
frame #4: 0x000000010d524340 scsynth`sc_ReadDir(SC_DirHandle*, char const*, char*, bool&) + 416
frame #5: 0x000000010d55d0c1 scsynth`PlugIn_LoadDir(char const*, bool) + 225
frame #6: 0x000000010d55ced8 scsynth`initialize_library(char const*) + 712
frame #7: 0x000000010d5746df scsynth`World_New + 63
frame #8: 0x000000010d51cb53 scsynth`main + 4723
frame #9: 0x000000010d51b7e4 scsynth`start + 52
thread #2: tid = 0x82af5, 0x00007fff8d923e6a libsystem_kernel.dylib`__workq_kernreturn + 10
frame #0: 0x00007fff8d923e6a libsystem_kernel.dylib`__workq_kernreturn + 10
frame #1: 0x00007fff885d1f08 libsystem_pthread.dylib`_pthread_wqthread + 330
frame #2: 0x00007fff885d4fb9 libsystem_pthread.dylib`start_wqthread + 13
thread #3: tid = 0x82af6, 0x00007fff8d924662 libsystem_kernel.dylib`kevent64 + 10, queue = 'com.apple.libdispatch-manager'
frame #0: 0x00007fff8d924662 libsystem_kernel.dylib`kevent64 + 10
frame #1: 0x00007fff873ab421 libdispatch.dylib`_dispatch_mgr_invoke + 239
frame #2: 0x00007fff873ab136 libdispatch.dylib`_dispatch_mgr_thread + 52
thread #4: tid = 0x82af7, 0x00007fff8d923e6a libsystem_kernel.dylib`__workq_kernreturn + 10
frame #0: 0x00007fff8d923e6a libsystem_kernel.dylib`__workq_kernreturn + 10
frame #1: 0x00007fff885d1f08 libsystem_pthread.dylib`_pthread_wqthread + 330
frame #2: 0x00007fff885d4fb9 libsystem_pthread.dylib`start_wqthread + 13
thread #5: tid = 0x82af8, 0x00007fff8d923716 libsystem_kernel.dylib`__psynch_cvwait + 10
frame #0: 0x00007fff8d923716 libsystem_kernel.dylib`__psynch_cvwait + 10
frame #1: 0x00007fff885d2c3b libsystem_pthread.dylib`_pthread_cond_wait + 727
frame #2: 0x00007fff8bc0dd43 libc++.1.dylib`std::__1::condition_variable::wait(std::__1::unique_lock<std::__1::mutex>&) + 47
frame #3: 0x000000010ecc7b49 DiskIO_UGens.scx`void std::__1::condition_variable_any::wait<std::__1::unique_lock<std::__1::mutex> >(std::__1::unique_lock<std::__1::mutex>&) + 585
frame #4: 0x000000010ecc785a DiskIO_UGens.scx`SC_SyncCondition::WaitEach() + 122
frame #5: 0x000000010ecc5158 DiskIO_UGens.scx`(anonymous namespace)::DiskIOThread::ioThreadFunc() + 152
frame #6: 0x000000010ecc6528 DiskIO_UGens.scx`void* std::__1::__thread_proxy<std::__1::tuple<std::__1::__bind<void ((anonymous namespace)::DiskIOThread::*)(), (anonymous namespace)::DiskIOThread*> > >(void*) + 616
frame #7: 0x00007fff885d0899 libsystem_pthread.dylib`_pthread_body + 138
frame #8: 0x00007fff885d072a libsystem_pthread.dylib`_pthread_start + 137
frame #9: 0x00007fff885d4fc9 libsystem_pthread.dylib`thread_start + 13
thread #6: tid = 0x82afc, 0x00007fff94bd34c5 CoreFoundation`_parseComponents + 213
frame #0: 0x00007fff94bd34c5 CoreFoundation`_parseComponents + 213
frame #1: 0x00007fff94bd334a CoreFoundation`_CFURLInitWithURLString + 1354
frame #2: 0x00007fff94bdb578 CoreFoundation`CFURLCreateWithString + 152
frame #3: 0x00007fff94bdb65f CoreFoundation`___CFBundleCopyInfoDictionaryInDirectoryWithVersion_block_invoke + 191
frame #4: 0x00007fff94bd8994 CoreFoundation`_CFIterateDirectory + 212
frame #5: 0x00007fff94bdb273 CoreFoundation`_CFBundleCopyInfoDictionaryInDirectoryWithVersion + 627
frame #6: 0x00007fff94bdaedd CoreFoundation`CFBundleGetInfoDictionary + 141
frame #7: 0x00007fff94bd772b CoreFoundation`_CFBundleCreate + 827
frame #8: 0x00007fff94c1ba89 CoreFoundation`_CFBundleEnsureBundleExistsForImagePath + 89
frame #9: 0x00007fff94c1b773 CoreFoundation`CFBundleGetBundleWithIdentifier + 115
frame #10: 0x00007fff947ea0a6 HIToolbox`HLTBGetBundle + 28
frame #11: 0x00007fff947e9fd2 HIToolbox`HIGetScaleFactor + 95
frame #12: 0x00007fff94814479 HIToolbox`GetMBarHeightInPixels + 30
frame #13: 0x00007fff94814452 HIToolbox`_HIMenuGetMenuBarHeight + 32
frame #14: 0x00007fff912a7cf5 AppKit`_NSMenuBarHeight + 14
frame #15: 0x00007fff912a7c7f AppKit`-[NSScreen _saveVisibleFrameAtIndex:] + 96
frame #16: 0x00007fff912a7bb8 AppKit`+[NSScreen _updateSavedFramesLocked] + 191
frame #17: 0x00007fff912a7a17 AppKit`+[NSScreen _resetScreensLocked] + 1412
frame #18: 0x00007fff912a72e4 AppKit`+[NSScreen _screensLocked] + 301
frame #19: 0x00007fff912a916b AppKit`+[NSScreen _zeroScreenHeight] + 73
frame #20: 0x00007fff9136ba48 AppKit`+[NSEvent mouseLocation] + 48
frame #21: 0x000000010f092da9 UIUGens.scx`gstate_update_func() + 89
frame #22: 0x000000010f094d36 UIUGens.scx`void* std::__1::__thread_proxy<std::__1::tuple<void (*)()> >(void*) + 390
frame #23: 0x00007fff885d0899 libsystem_pthread.dylib`_pthread_body + 138
frame #24: 0x00007fff885d072a libsystem_pthread.dylib`_pthread_start + 137
frame #25: 0x00007fff885d4fc9 libsystem_pthread.dylib`thread_start + 13
(lldb)
```
(I hope that's useful info - for me that's completely uncharted territory here)
Since the IDE's post window only returns "ERROR: server failed to start" I launched the server from the shell to realise the seg fault.
Doing so I noticed that scsynth won't crash when located outside the package.
i.e.:
```
cox:~ mz$ pwd
/Users/mz
cox:~ mz$ /Users/mz/dev/sc3.git/SuperCollider-debug/SuperCollider.app/Contents/MacOS/scsynth -u 57110
Segmentation fault: 11
cox:~ mz$ /Users/mz/Desktop/scsynth -u 57110
Faust: supercollider.cpp: sc_api_version = 2
Faust: FaustGreyholeRaw numControls=7
Faust: supercollider.cpp: sc_api_version = 2
Faust: FaustJPverbRaw numControls=11
Found 0 LADSPA plugins
exception in GrafDef_Load: UGen 'WhiteNoise' not installed.
while reading file '/Users/mz/Library/Application Support/SuperCollider/synthdefs/bped_noise.scsyndef'
exception in GrafDef_Load: UGen 'Control' not installed.
while reading file '/Users/mz/Library/Application Support/SuperCollider/synthdefs/fsynth.scsyndef'
exception in GrafDef_Load: UGen 'Control' not installed.
while reading file '/Users/mz/Library/Application Support/SuperCollider/synthdefs/Help-SynthDef.scsyndef'
exception in GrafDef_Load: UGen 'Control' not installed.
while reading file '/Users/mz/Library/Application Support/SuperCollider/synthdefs/rec-ins.scsyndef'
exception in GrafDef_Load: UGen 'ExpRand' not installed.
while reading file '/Users/mz/Library/Application Support/SuperCollider/synthdefs/sincluster.scsyndef'
Number of Devices: 5
0 : "Built-in Microph"
1 : "Built-in Input"
2 : "Built-in Output"
3 : "Soundflower (2ch)"
4 : "Soundflower (64ch)"
"Built-in Input" Input Device
Streams: 1
0 channels 2
"Built-in Output" Output Device
Streams: 1
0 channels 2
SC_AudioDriver: sample rate = 96000.000000, driver's block size = 512
PublishPortToRendezvous 0 5855
SuperCollider 3 server ready (debug build).
```
This behaviour is reproducible.
Of course I recompiled with target 10.9 which doesn't help.
The very same binary runs o.k. on the 10.10.5 system where it's been compiled on.
The very same source tree compiles and runs o.k. on 10.9.5 / Xcode 6.2.
AFAIK travis compiles on 10.9.5 for a target of 10.7 - w/o problems, so far.
sclang and supernova are apparently fine, AFAICT.
| non_test | scsynth throws seg fault on system being compiled on xcode i compiled sc on an os x system w xcode with a deployment target of launching scsynth on my main system w it crashes with a segmentation fault i recompiled with cmake g xcode dcmake build type debug dcmake osx deployment target dcmake prefix path brew prefix dsupernova on cmake build target install config debug sent lldb on the hunt before launching scsynth from within the ide lldb lldb process attach name scsynth waitfor process stopped executable module set to users mz dev git supercollider debug supercollider app contents resources macos scsynth architecture set to apple macosx lldb process continue process resuming process stopped thread tid queue com apple main thread stop reason exc bad access code address frame error memory read failed for lldb thread backtrace all thread tid queue com apple main thread stop reason exc bad access code address frame frame foundation frame foundation frame scsynth sc resolveifalias char const char bool int frame scsynth sc readdir sc dirhandle char const char bool frame scsynth plugin loaddir char const bool frame scsynth initialize library char const frame scsynth world new frame scsynth main frame scsynth start thread tid libsystem kernel dylib workq kernreturn frame libsystem kernel dylib workq kernreturn frame libsystem pthread dylib pthread wqthread frame libsystem pthread dylib start wqthread thread tid libsystem kernel dylib queue com apple libdispatch manager frame libsystem kernel dylib frame libdispatch dylib dispatch mgr invoke frame libdispatch dylib dispatch mgr thread thread tid libsystem kernel dylib workq kernreturn frame libsystem kernel dylib workq kernreturn frame libsystem pthread dylib pthread wqthread frame libsystem pthread dylib start wqthread thread tid libsystem kernel dylib psynch cvwait frame libsystem kernel dylib psynch cvwait frame libsystem pthread dylib pthread cond wait frame libc dylib std condition variable wait std unique lock frame diskio ugens scx void std condition variable any wait std unique lock frame diskio ugens scx sc synccondition waiteach frame diskio ugens scx anonymous namespace diskiothread iothreadfunc frame diskio ugens scx void std thread proxy void frame libsystem pthread dylib pthread body frame libsystem pthread dylib pthread start frame libsystem pthread dylib thread start thread tid corefoundation parsecomponents frame corefoundation parsecomponents frame corefoundation cfurlinitwithurlstring frame corefoundation cfurlcreatewithstring frame corefoundation cfbundlecopyinfodictionaryindirectorywithversion block invoke frame corefoundation cfiteratedirectory frame corefoundation cfbundlecopyinfodictionaryindirectorywithversion frame corefoundation cfbundlegetinfodictionary frame corefoundation cfbundlecreate frame corefoundation cfbundleensurebundleexistsforimagepath frame corefoundation cfbundlegetbundlewithidentifier frame hitoolbox hltbgetbundle frame hitoolbox higetscalefactor frame hitoolbox getmbarheightinpixels frame hitoolbox himenugetmenubarheight frame appkit nsmenubarheight frame appkit frame appkit frame appkit frame appkit frame appkit frame appkit frame uiugens scx gstate update func frame uiugens scx void std thread proxy void frame libsystem pthread dylib pthread body frame libsystem pthread dylib pthread start frame libsystem pthread dylib thread start lldb i hope that s useful info for me that s completely uncharted territory here since the ide s post window only returns error server failed to start i launched the server from the shell to realise the seg fault doing so i noticed that scsynth won t crash when located outside the package i e cox mz pwd users mz cox mz users mz dev git supercollider debug supercollider app contents macos scsynth u segmentation fault cox mz users mz desktop scsynth u faust supercollider cpp sc api version faust faustgreyholeraw numcontrols faust supercollider cpp sc api version faust faustjpverbraw numcontrols found ladspa plugins exception in grafdef load ugen whitenoise not installed while reading file users mz library application support supercollider synthdefs bped noise scsyndef exception in grafdef load ugen control not installed while reading file users mz library application support supercollider synthdefs fsynth scsyndef exception in grafdef load ugen control not installed while reading file users mz library application support supercollider synthdefs help synthdef scsyndef exception in grafdef load ugen control not installed while reading file users mz library application support supercollider synthdefs rec ins scsyndef exception in grafdef load ugen exprand not installed while reading file users mz library application support supercollider synthdefs sincluster scsyndef number of devices built in microph built in input built in output soundflower soundflower built in input input device streams channels built in output output device streams channels sc audiodriver sample rate driver s block size publishporttorendezvous supercollider server ready debug build this behaviour is reproducible of course i recompiled with target which doesn t help the very same binary runs o k on the system where it s been compiled on the very same source tree compiles and runs o k on xcode afaik travis compiles on for a target of w o problems so far sclang and supernova are apparently fine afaict | 0 |
354,891 | 10,574,304,553 | IssuesEvent | 2019-10-07 13:46:28 | cr-ste-justine/clin-project | https://api.github.com/repos/cr-ste-justine/clin-project | opened | [CLIN] Set-up Gabriel | Priority: High | - [ ] Access Card CHUSJ
- [ ] Key for Room CHUSJ
- [ ] HR Key Re-assignement (Sylvie Julien)
- [ ] HR Seat Re-assignement (Sylvie Julien)
- [ ] Wi-Fi CHUSJ
- [ ] Intranet CHUSJ
- [ ] Email CHUSJ
- [ ] VM Windows Intranet CHUSJ
- [ ] Intranet Pay System CHUSJ
- [ ] Set-up Computer
- [ ] Github Access | 1.0 | [CLIN] Set-up Gabriel - - [ ] Access Card CHUSJ
- [ ] Key for Room CHUSJ
- [ ] HR Key Re-assignement (Sylvie Julien)
- [ ] HR Seat Re-assignement (Sylvie Julien)
- [ ] Wi-Fi CHUSJ
- [ ] Intranet CHUSJ
- [ ] Email CHUSJ
- [ ] VM Windows Intranet CHUSJ
- [ ] Intranet Pay System CHUSJ
- [ ] Set-up Computer
- [ ] Github Access | non_test | set up gabriel access card chusj key for room chusj hr key re assignement sylvie julien hr seat re assignement sylvie julien wi fi chusj intranet chusj email chusj vm windows intranet chusj intranet pay system chusj set up computer github access | 0 |
14,674 | 3,414,011,838 | IssuesEvent | 2015-12-07 02:00:17 | d3athrow/vgstation13 | https://api.github.com/repos/d3athrow/vgstation13 | closed | Round Start Spawn Not working | Bug Feature Loss Needs Moar Testing | (WEB REPORT BY: infoman567 REMOTE: 158.69.55.2:7777)
>Revision (Should be above if you're viewing this from ingame!)
>General description of the issue
At the start of the round, even though set ready. Was not spawned into the game. This has happened more than once.
>What you expected to happen
Spawn at Roundstart
>What actually happened
Did not spawn at roundstart and forced to pick unwanted roles
>Steps to reproduce if possible | 1.0 | Round Start Spawn Not working - (WEB REPORT BY: infoman567 REMOTE: 158.69.55.2:7777)
>Revision (Should be above if you're viewing this from ingame!)
>General description of the issue
At the start of the round, even though set ready. Was not spawned into the game. This has happened more than once.
>What you expected to happen
Spawn at Roundstart
>What actually happened
Did not spawn at roundstart and forced to pick unwanted roles
>Steps to reproduce if possible | test | round start spawn not working web report by remote revision should be above if you re viewing this from ingame general description of the issue at the start of the round even though set ready was not spawned into the game this has happened more than once what you expected to happen spawn at roundstart what actually happened did not spawn at roundstart and forced to pick unwanted roles steps to reproduce if possible | 1 |
63,624 | 6,876,796,329 | IssuesEvent | 2017-11-20 03:32:24 | xcat2/xcat-core | https://api.github.com/repos/xcat2/xcat-core | closed | [FVT] xcattest treats all nonexistent test cases as `Passed` | component:test sprint1 status:pending type:bug | Currently, `xcattest` treats all nonexistent test cases as `Passed`. Which is not good. Since there may be misspelling in the bundle files. In that case, misspelled test cases will be counted as `Passed`.
I suggest, treats all nonexistent test cases as `No Run`.
# xcattest -t nonexistent_test_case,blah,foo,bar,baz,quux
xCAT automated test started at Thu Jul 6 02:23:02 2017
******************************
loading test cases
******************************
To run:
nonexistent_test_case
blah
foo
bar
baz
quux
******************************
Start to run test cases
******************************
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1163.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1163.
------START::::Time:Thu Jul 6 02:23:02 2017------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1167.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1300.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1300.
------END::::Passed::Time:Thu Jul 6 02:23:02 2017 ::Duration::0 sec------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1163.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1163.
------START::::Time:Thu Jul 6 02:23:02 2017------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1167.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1300.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1300.
------END::::Passed::Time:Thu Jul 6 02:23:02 2017 ::Duration::0 sec------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1163.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1163.
------START::::Time:Thu Jul 6 02:23:02 2017------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1167.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1300.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1300.
------END::::Passed::Time:Thu Jul 6 02:23:02 2017 ::Duration::0 sec------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1163.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1163.
------START::::Time:Thu Jul 6 02:23:02 2017------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1167.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1300.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1300.
------END::::Passed::Time:Thu Jul 6 02:23:02 2017 ::Duration::0 sec------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1163.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1163.
------START::::Time:Thu Jul 6 02:23:02 2017------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1167.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1300.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1300.
------END::::Passed::Time:Thu Jul 6 02:23:02 2017 ::Duration::0 sec------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1163.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1163.
------START::::Time:Thu Jul 6 02:23:02 2017------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1167.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1300.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1300.
------END::::Passed::Time:Thu Jul 6 02:23:02 2017 ::Duration::0 sec------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1301.
------Total: 6 , Failed: 0------
xCAT automated test finished atThu Jul 6 02:23:02 2017
Please check results in the /opt/xcat/bin/../share/xcat/tools/autotest/result/,
and see /opt/xcat/bin/../share/xcat/tools/autotest/result//failedcases.20170706022302 file for failed cases.
see /opt/xcat/bin/../share/xcat/tools/autotest/result//performance.report.20170706022302 file for time consumption
| 1.0 | [FVT] xcattest treats all nonexistent test cases as `Passed` - Currently, `xcattest` treats all nonexistent test cases as `Passed`. Which is not good. Since there may be misspelling in the bundle files. In that case, misspelled test cases will be counted as `Passed`.
I suggest, treats all nonexistent test cases as `No Run`.
# xcattest -t nonexistent_test_case,blah,foo,bar,baz,quux
xCAT automated test started at Thu Jul 6 02:23:02 2017
******************************
loading test cases
******************************
To run:
nonexistent_test_case
blah
foo
bar
baz
quux
******************************
Start to run test cases
******************************
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1163.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1163.
------START::::Time:Thu Jul 6 02:23:02 2017------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1167.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1300.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1300.
------END::::Passed::Time:Thu Jul 6 02:23:02 2017 ::Duration::0 sec------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1163.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1163.
------START::::Time:Thu Jul 6 02:23:02 2017------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1167.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1300.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1300.
------END::::Passed::Time:Thu Jul 6 02:23:02 2017 ::Duration::0 sec------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1163.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1163.
------START::::Time:Thu Jul 6 02:23:02 2017------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1167.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1300.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1300.
------END::::Passed::Time:Thu Jul 6 02:23:02 2017 ::Duration::0 sec------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1163.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1163.
------START::::Time:Thu Jul 6 02:23:02 2017------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1167.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1300.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1300.
------END::::Passed::Time:Thu Jul 6 02:23:02 2017 ::Duration::0 sec------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1163.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1163.
------START::::Time:Thu Jul 6 02:23:02 2017------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1167.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1300.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1300.
------END::::Passed::Time:Thu Jul 6 02:23:02 2017 ::Duration::0 sec------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1163.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1163.
------START::::Time:Thu Jul 6 02:23:02 2017------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1164.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1165.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1167.
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1300.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1300.
------END::::Passed::Time:Thu Jul 6 02:23:02 2017 ::Duration::0 sec------
Use of uninitialized value in array element at /opt/xcat/bin/xcattest line 1301.
Use of uninitialized value in concatenation (.) or string at /opt/xcat/bin/xcattest line 1301.
------Total: 6 , Failed: 0------
xCAT automated test finished atThu Jul 6 02:23:02 2017
Please check results in the /opt/xcat/bin/../share/xcat/tools/autotest/result/,
and see /opt/xcat/bin/../share/xcat/tools/autotest/result//failedcases.20170706022302 file for failed cases.
see /opt/xcat/bin/../share/xcat/tools/autotest/result//performance.report.20170706022302 file for time consumption
| test | xcattest treats all nonexistent test cases as passed currently xcattest treats all nonexistent test cases as passed which is not good since there may be misspelling in the bundle files in that case misspelled test cases will be counted as passed i suggest treats all nonexistent test cases as no run xcattest t nonexistent test case blah foo bar baz quux xcat automated test started at thu jul loading test cases to run nonexistent test case blah foo bar baz quux start to run test cases use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line start time thu jul use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line end passed time thu jul duration sec use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line start time thu jul use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line end passed time thu jul duration sec use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line start time thu jul use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line end passed time thu jul duration sec use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line start time thu jul use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line end passed time thu jul duration sec use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line start time thu jul use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line end passed time thu jul duration sec use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line start time thu jul use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line end passed time thu jul duration sec use of uninitialized value in array element at opt xcat bin xcattest line use of uninitialized value in concatenation or string at opt xcat bin xcattest line total failed xcat automated test finished atthu jul please check results in the opt xcat bin share xcat tools autotest result and see opt xcat bin share xcat tools autotest result failedcases file for failed cases see opt xcat bin share xcat tools autotest result performance report file for time consumption | 1 |
9,649 | 3,062,092,401 | IssuesEvent | 2015-08-16 07:41:22 | zeusjs/widgets | https://api.github.com/repos/zeusjs/widgets | closed | Unit tests for zs_text | unit tests | Test coverage for zs_text is about 88%. Lets improve this. See [Coveralls Report](https://coveralls.io/builds/3297425 "Coverage report on coveralls.io") for more details. | 1.0 | Unit tests for zs_text - Test coverage for zs_text is about 88%. Lets improve this. See [Coveralls Report](https://coveralls.io/builds/3297425 "Coverage report on coveralls.io") for more details. | test | unit tests for zs text test coverage for zs text is about lets improve this see coverage report on coveralls io for more details | 1 |
58,496 | 6,601,683,715 | IssuesEvent | 2017-09-18 03:08:36 | smap-consulting/smapserver | https://api.github.com/repos/smap-consulting/smapserver | closed | BUG - TASKs start always in edition mode | enhancement In Test | ### SmapServer
### Expected Behaviour: start to fill a Task should behave as fill a Form
### Actual Behaviour: Tasks starts in edition mode:
### Steps to reproduce the problem
| 1.0 | BUG - TASKs start always in edition mode - ### SmapServer
### Expected Behaviour: start to fill a Task should behave as fill a Form
### Actual Behaviour: Tasks starts in edition mode:
### Steps to reproduce the problem
| test | bug tasks start always in edition mode smapserver expected behaviour start to fill a task should behave as fill a form actual behaviour tasks starts in edition mode steps to reproduce the problem | 1 |
499,339 | 14,445,350,458 | IssuesEvent | 2020-12-07 22:48:51 | airbytehq/airbyte | https://api.github.com/repos/airbytehq/airbyte | reopened | Add Incremental to the UI | area/frontend incremental priority/high type/enhancement | Mockups: https://www.figma.com/file/AODY4oi15iI5l0fbxHvobt/Daxtarity?node-id=11542%3A1349
* Adds ability to configure incremental for each stream in the UI.
* Adds ability to reset data in the UI.
The new terminology for incremental is explained [here](https://github.com/airbytehq/airbyte/blob/master/docs/architecture/incremental.md) and [here](https://github.com/airbytehq/airbyte/blob/master/docs/architecture/catalog.md).
logic for what should be present in the dropdown:
* Each stream in the AirbyteCatalog now contains a `supportedSyncModes` field. If the value is empty assume the only supported sync mode is FULL_REFRESH. Otherwise it supports whatever sync modes are present.
* If INCREMENTAL is included in the supported sync modes...
* If `source_defined_cursor` in `AirbyteStream` is true, then the source determines the cursor field internally. It cannot be overriden by the user. In the dropdown for the stream in the UI, we should just have one row for incremental it should say "incremental - source-defined cursor". If `source_defined_cursor` is not true...
* Then any column in the stream can be used as the cursor. The list of columns should appear in the dropdown just like they appear in the mockup
* If `default_cursor_field` in `AirbyteStream` is set, then the field specified in there should be at the top of the list and have the word "(default)" next to it (as seen in the mockups) | 1.0 | Add Incremental to the UI - Mockups: https://www.figma.com/file/AODY4oi15iI5l0fbxHvobt/Daxtarity?node-id=11542%3A1349
* Adds ability to configure incremental for each stream in the UI.
* Adds ability to reset data in the UI.
The new terminology for incremental is explained [here](https://github.com/airbytehq/airbyte/blob/master/docs/architecture/incremental.md) and [here](https://github.com/airbytehq/airbyte/blob/master/docs/architecture/catalog.md).
logic for what should be present in the dropdown:
* Each stream in the AirbyteCatalog now contains a `supportedSyncModes` field. If the value is empty assume the only supported sync mode is FULL_REFRESH. Otherwise it supports whatever sync modes are present.
* If INCREMENTAL is included in the supported sync modes...
* If `source_defined_cursor` in `AirbyteStream` is true, then the source determines the cursor field internally. It cannot be overriden by the user. In the dropdown for the stream in the UI, we should just have one row for incremental it should say "incremental - source-defined cursor". If `source_defined_cursor` is not true...
* Then any column in the stream can be used as the cursor. The list of columns should appear in the dropdown just like they appear in the mockup
* If `default_cursor_field` in `AirbyteStream` is set, then the field specified in there should be at the top of the list and have the word "(default)" next to it (as seen in the mockups) | non_test | add incremental to the ui mockups adds ability to configure incremental for each stream in the ui adds ability to reset data in the ui the new terminology for incremental is explained and logic for what should be present in the dropdown each stream in the airbytecatalog now contains a supportedsyncmodes field if the value is empty assume the only supported sync mode is full refresh otherwise it supports whatever sync modes are present if incremental is included in the supported sync modes if source defined cursor in airbytestream is true then the source determines the cursor field internally it cannot be overriden by the user in the dropdown for the stream in the ui we should just have one row for incremental it should say incremental source defined cursor if source defined cursor is not true then any column in the stream can be used as the cursor the list of columns should appear in the dropdown just like they appear in the mockup if default cursor field in airbytestream is set then the field specified in there should be at the top of the list and have the word default next to it as seen in the mockups | 0 |
180,473 | 13,932,994,445 | IssuesEvent | 2020-10-22 08:05:47 | Tribler/py-ipv8 | https://api.github.com/repos/Tribler/py-ipv8 | opened | Add shortcuts for node attributes in TestBase | enhancement tests | In many tests we assert that attributes of nodes change in a certain way (mostly their `overlay` attribute). We can adopt the style of `test_identity.py` in `TestBase` to provide convenient shortcuts:
https://github.com/Tribler/py-ipv8/blob/4843ff33b5eaf04c2315d04a1f40c5197fae0a11/ipv8/test/attestation/identity/test_identity.py#L21-L28
A before-and-after example:
```python
# Before
self.nodes[3].overlay.send_to(Peer(self.nodes[4].my_peer.public_key.key_to_bin(), self.nodes[4].endpoint.wan_address), 3)
self.assertEqual(3, self.nodes[4].overlay.something)
# After
self.overlay(3).send_to(self.peer(4), 3)
self.assertEqual(3, self.overlay(4).something)
``` | 1.0 | Add shortcuts for node attributes in TestBase - In many tests we assert that attributes of nodes change in a certain way (mostly their `overlay` attribute). We can adopt the style of `test_identity.py` in `TestBase` to provide convenient shortcuts:
https://github.com/Tribler/py-ipv8/blob/4843ff33b5eaf04c2315d04a1f40c5197fae0a11/ipv8/test/attestation/identity/test_identity.py#L21-L28
A before-and-after example:
```python
# Before
self.nodes[3].overlay.send_to(Peer(self.nodes[4].my_peer.public_key.key_to_bin(), self.nodes[4].endpoint.wan_address), 3)
self.assertEqual(3, self.nodes[4].overlay.something)
# After
self.overlay(3).send_to(self.peer(4), 3)
self.assertEqual(3, self.overlay(4).something)
``` | test | add shortcuts for node attributes in testbase in many tests we assert that attributes of nodes change in a certain way mostly their overlay attribute we can adopt the style of test identity py in testbase to provide convenient shortcuts a before and after example python before self nodes overlay send to peer self nodes my peer public key key to bin self nodes endpoint wan address self assertequal self nodes overlay something after self overlay send to self peer self assertequal self overlay something | 1 |
13,643 | 3,351,262,910 | IssuesEvent | 2015-11-17 17:49:17 | rancher/rancher | https://api.github.com/repos/rancher/rancher | closed | cadvisor is using 15-25% CPU with 54 containers | kind/enhancement status/resolved status/to-test | Watching `top` on my Docker host, the `.cadvisor` process is using anywhere between 15 to 25% CPU all the time. I have 54 containers, not very active.
I notice that the [version of cadvisor](https://github.com/rancher/cattle/blob/master/resources/content/cattle-global.properties) used by rancher is quite old -- version 0.4.0 released September 2014. The latest version is 0.18.0, released September 2015. I don't know how much performance has improved, but it may be worth a look.
I'm guessing that rancher is also using the default sampling interval of 1 second. For demo purposes this is nice and shows a pretty graph, but for production an interval of 5 or 10 seconds would have less overhead. It should be possible to configure the sampling interval in the Rancher UI. | 1.0 | cadvisor is using 15-25% CPU with 54 containers - Watching `top` on my Docker host, the `.cadvisor` process is using anywhere between 15 to 25% CPU all the time. I have 54 containers, not very active.
I notice that the [version of cadvisor](https://github.com/rancher/cattle/blob/master/resources/content/cattle-global.properties) used by rancher is quite old -- version 0.4.0 released September 2014. The latest version is 0.18.0, released September 2015. I don't know how much performance has improved, but it may be worth a look.
I'm guessing that rancher is also using the default sampling interval of 1 second. For demo purposes this is nice and shows a pretty graph, but for production an interval of 5 or 10 seconds would have less overhead. It should be possible to configure the sampling interval in the Rancher UI. | test | cadvisor is using cpu with containers watching top on my docker host the cadvisor process is using anywhere between to cpu all the time i have containers not very active i notice that the used by rancher is quite old version released september the latest version is released september i don t know how much performance has improved but it may be worth a look i m guessing that rancher is also using the default sampling interval of second for demo purposes this is nice and shows a pretty graph but for production an interval of or seconds would have less overhead it should be possible to configure the sampling interval in the rancher ui | 1 |
281,698 | 24,413,214,660 | IssuesEvent | 2022-10-05 14:00:40 | apache/beam | https://api.github.com/repos/apache/beam | closed | SpannerChangeStreamOrderedWithinKeyGloballyIT and SpannerChangeStreamOrderedWithinKeyIT fail on Direct Runner | runners direct P1 bug test-failures | Like BEAM-14151, it seems as though DirectRunner fails on these tests pretty consistently:
```
org.apache.beam.sdk.io.gcp.spanner.changestreams.it.SpannerChangeStreamOrderedWithinKeyGloballyIT.testOrderedWithinKey
org.apache.beam.sdk.io.gcp.spanner.changestreams.it.SpannerChangeStreamOrderedWithinKeyIT.testOrderedWithinKey
```
This has been failing for a few days, occassionally it passes but that could be a fluke that the direct runner executed it in the order that was expected.
Example failure: https://ci-beam.apache.org/job/beam_PostCommit_Java/8776/
Imported from Jira [BEAM-14193](https://issues.apache.org/jira/browse/BEAM-14193). Original Jira may contain additional context.
Reported by: lcwik. | 1.0 | SpannerChangeStreamOrderedWithinKeyGloballyIT and SpannerChangeStreamOrderedWithinKeyIT fail on Direct Runner - Like BEAM-14151, it seems as though DirectRunner fails on these tests pretty consistently:
```
org.apache.beam.sdk.io.gcp.spanner.changestreams.it.SpannerChangeStreamOrderedWithinKeyGloballyIT.testOrderedWithinKey
org.apache.beam.sdk.io.gcp.spanner.changestreams.it.SpannerChangeStreamOrderedWithinKeyIT.testOrderedWithinKey
```
This has been failing for a few days, occassionally it passes but that could be a fluke that the direct runner executed it in the order that was expected.
Example failure: https://ci-beam.apache.org/job/beam_PostCommit_Java/8776/
Imported from Jira [BEAM-14193](https://issues.apache.org/jira/browse/BEAM-14193). Original Jira may contain additional context.
Reported by: lcwik. | test | spannerchangestreamorderedwithinkeygloballyit and spannerchangestreamorderedwithinkeyit fail on direct runner like beam it seems as though directrunner fails on these tests pretty consistently org apache beam sdk io gcp spanner changestreams it spannerchangestreamorderedwithinkeygloballyit testorderedwithinkey org apache beam sdk io gcp spanner changestreams it spannerchangestreamorderedwithinkeyit testorderedwithinkey this has been failing for a few days occassionally it passes but that could be a fluke that the direct runner executed it in the order that was expected example failure imported from jira original jira may contain additional context reported by lcwik | 1 |
3,030 | 2,658,101,156 | IssuesEvent | 2015-03-18 13:54:31 | GijsTimmers/kotnetcli | https://api.github.com/repos/GijsTimmers/kotnetcli | closed | Create separate classes for separate tasks in the app, just like in the compurter program. | @low app software-design working on it | We should have at least:
- `AppBrowser()`
- `AppCredentials()`
- `AppCommunicator()`
and to make everything work together smoothly, our beloved `AppWorker()`.
As much as I'd like the app to just import everything it needs from the 'normal' `browser.py`, `fabriek.py`, etcetera, this is not possible at the moment: the compiled APK file crashes when run on mobile devices. That's why we have to re-write everything we need into the app file. | 1.0 | Create separate classes for separate tasks in the app, just like in the compurter program. - We should have at least:
- `AppBrowser()`
- `AppCredentials()`
- `AppCommunicator()`
and to make everything work together smoothly, our beloved `AppWorker()`.
As much as I'd like the app to just import everything it needs from the 'normal' `browser.py`, `fabriek.py`, etcetera, this is not possible at the moment: the compiled APK file crashes when run on mobile devices. That's why we have to re-write everything we need into the app file. | non_test | create separate classes for separate tasks in the app just like in the compurter program we should have at least appbrowser appcredentials appcommunicator and to make everything work together smoothly our beloved appworker as much as i d like the app to just import everything it needs from the normal browser py fabriek py etcetera this is not possible at the moment the compiled apk file crashes when run on mobile devices that s why we have to re write everything we need into the app file | 0 |
246,157 | 7,893,198,886 | IssuesEvent | 2018-06-28 17:15:14 | visit-dav/issues-test | https://api.github.com/repos/visit-dav/issues-test | closed | 2D transfer functions not saved | Bug Likelihood: 3 - Occasional OS: All Priority: Normal Severity: 2 - Minor Irritation Support Group: Any version: 2.2.0 | In the volume plot window, when 2D transfer function is enabled (SLIVR method). Save/Load buttons are enabled, but the 2D function is not saved.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. The following information
could not be accurately captured in the new ticket:
Original author: Kathleen Biagas
Original creation: 04/11/2011 04:21 pm
Original update: 07/12/2011 05:35 pm
Ticket number: 682 | 1.0 | 2D transfer functions not saved - In the volume plot window, when 2D transfer function is enabled (SLIVR method). Save/Load buttons are enabled, but the 2D function is not saved.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. The following information
could not be accurately captured in the new ticket:
Original author: Kathleen Biagas
Original creation: 04/11/2011 04:21 pm
Original update: 07/12/2011 05:35 pm
Ticket number: 682 | non_test | transfer functions not saved in the volume plot window when transfer function is enabled slivr method save load buttons are enabled but the function is not saved redmine migration this ticket was migrated from redmine the following information could not be accurately captured in the new ticket original author kathleen biagas original creation pm original update pm ticket number | 0 |
276,241 | 20,975,548,574 | IssuesEvent | 2022-03-28 14:56:23 | microsoft/DSynth | https://api.github.com/repos/microsoft/DSynth | closed | The example image output link in docs/Template-Formats.md is a dead link | documentation | There's a link to an example image in the image template format example but [the link](https://github.com/microsoft/DSynth/blob/main/.attachments/image-7dbc1ca7-45d3-4fff-ad3f-14137fafa048.png) is dead/there isn't an image. | 1.0 | The example image output link in docs/Template-Formats.md is a dead link - There's a link to an example image in the image template format example but [the link](https://github.com/microsoft/DSynth/blob/main/.attachments/image-7dbc1ca7-45d3-4fff-ad3f-14137fafa048.png) is dead/there isn't an image. | non_test | the example image output link in docs template formats md is a dead link there s a link to an example image in the image template format example but is dead there isn t an image | 0 |
9,390 | 3,038,822,366 | IssuesEvent | 2015-08-07 02:10:18 | mosspilot/cs361projectb | https://api.github.com/repos/mosspilot/cs361projectb | closed | T28 Logout & browser history navigation | bug test case | > User hits back button <after clicking on the log out button after logging in successfully>
Result: User is directed to previous page while still not logged in. Not able to add or perform any actions, but able to navigate some of site and many errors pop up. | 1.0 | T28 Logout & browser history navigation - > User hits back button <after clicking on the log out button after logging in successfully>
Result: User is directed to previous page while still not logged in. Not able to add or perform any actions, but able to navigate some of site and many errors pop up. | test | logout browser history navigation user hits back button result user is directed to previous page while still not logged in not able to add or perform any actions but able to navigate some of site and many errors pop up | 1 |
180,285 | 13,928,891,987 | IssuesEvent | 2020-10-21 22:21:50 | DuongTyler/haachama-coco | https://api.github.com/repos/DuongTyler/haachama-coco | opened | Frontend Tests | Future Tests frontend good first issue | Test from the front end to determine whether something horrendous has happened to the frontend.
Preferably mocks data, but same tests should also be usable for e2e testing. | 1.0 | Frontend Tests - Test from the front end to determine whether something horrendous has happened to the frontend.
Preferably mocks data, but same tests should also be usable for e2e testing. | test | frontend tests test from the front end to determine whether something horrendous has happened to the frontend preferably mocks data but same tests should also be usable for testing | 1 |
76,190 | 21,216,419,270 | IssuesEvent | 2022-04-11 07:48:43 | chaotic-aur/packages | https://api.github.com/repos/chaotic-aur/packages | opened | [Outdated] all Firefox(s) with appmenu are outdated; FF extensions possibly need manual intervention | request:rebuild-pkg | ### If available, link to the latest build
https://builds.garudalinux.org/repos/chaotic-aur/logs/firefox-appmenu-bin.log
https://builds.garudalinux.org/repos/chaotic-aur/logs/firefox-extension-plasma-integration.log
https://builds.garudalinux.org/repos/chaotic-aur/logs/firefox-extension-flagfox.log
https://builds.garudalinux.org/repos/chaotic-aur/logs/firefox-kde-opensuse-rpm.log
### Package name
firefox-appmenu-bin
### Latest build
98.0.2-1
### Latest version available
99.0-1
### Have you tested if the package builds in a clean chroot?
- [ ] Yes
### More information
Thanks for maintaining these Firefox packages. However, I noticed a few issues:
1) Firefox 99 has been released for about a week, and most variants have already been updated. However, the binary versions with the global app menu patch have not been updated on the repo.
According to the build server logs, it did complete the `firefox-appmenu-bin` build or at least attempted it. But, there is an error:
`==> ERROR: A package has already been built. (use -f to overwrite)`
I'm guessing this is because _chaotic-aur_ is fetching the binary versions from the AUR's _"-bin"_ packages rather than building them from source. Therefore, it's only a link to AUR binaries and if those maintainers don't update, then nothing gets built because the previous package version already exists? In that case, I'm mistaken, and it isn't technically outdated but still a bit disappointing.
2) Upon reviewing build logs, I've come across recent firefox extension builds which also ended with this error and therefore haven't been updated to the repo. This issue appears to have only come up recently, as older packages seem to be unaffected (i.e. `plasma-integration` is up-to-date even with this error, but `flagfox` is outdated). I haven't checked all the extensions, but I posted links to the two builds with errors I found. It's probably a similar issue with retrieving whatever the AUR has linked without downloading the newest extension versions from Mozilla servers.
```
[?25h==> ERROR: A package has already been built. (use -f to overwrite)
Container pkg5f237c1a8d3 failed with error code 13.
```
3) `firefox-kde-opensuse` also contains the appmenu patch and `firefox-kde-opensuse-rpm` is the binary built by OpenSUSE. I'm not sure why _chaotic-aur_ also tries to build this, but it's failing due to what looks like a dependency error:
`error: target not found: kmozillahelper`
I don't know the difference between this package and the one OpenSUSE builds, and if it is the same, then this is redundant and possibly a waste of resources. Therefore, it may be best if someone removed this, especially if we're not willing to also keep up its dependent helper.
https://aur.archlinux.org/packages/firefox-kde-opensuse-rpm
Unfortunately, the AUR maintainer hasn't updated the PKGBUILD, and its RPM download URL fails, so I haven't tested this either. Moreover, this particular binary package **doesn't include the global app menu patch** like the source version does, so I'm confused about what it offers as opposed to just using baseline `firefox` releases with `firefox-extension-plasma-integration` since my reason for using these is for the appmenu support.
Also of interest to this issue is `firefox-ubuntu-bin` as all these global menu Firefox variants seem to rely on `unity-menubar.patch` which comes from Ubuntu. It would be great if we consolidated these packages, which basically do the same thing, without having to rely on Ubuntu's slow build servers.
If AUR maintainers aren't willing to rebuild these binaries in a timely manner, please consider using chaotic-aur to automate builds of Firefox with the relevant patches enabled. The source versions on the AUR are more up-to-date and probably do work, but I would really appreciate if at least one binary of Firefox with appmenu support gets built.
Thanks again to everyone maintaining these packages. I hope the automated builds work again.
| 1.0 | [Outdated] all Firefox(s) with appmenu are outdated; FF extensions possibly need manual intervention - ### If available, link to the latest build
https://builds.garudalinux.org/repos/chaotic-aur/logs/firefox-appmenu-bin.log
https://builds.garudalinux.org/repos/chaotic-aur/logs/firefox-extension-plasma-integration.log
https://builds.garudalinux.org/repos/chaotic-aur/logs/firefox-extension-flagfox.log
https://builds.garudalinux.org/repos/chaotic-aur/logs/firefox-kde-opensuse-rpm.log
### Package name
firefox-appmenu-bin
### Latest build
98.0.2-1
### Latest version available
99.0-1
### Have you tested if the package builds in a clean chroot?
- [ ] Yes
### More information
Thanks for maintaining these Firefox packages. However, I noticed a few issues:
1) Firefox 99 has been released for about a week, and most variants have already been updated. However, the binary versions with the global app menu patch have not been updated on the repo.
According to the build server logs, it did complete the `firefox-appmenu-bin` build or at least attempted it. But, there is an error:
`==> ERROR: A package has already been built. (use -f to overwrite)`
I'm guessing this is because _chaotic-aur_ is fetching the binary versions from the AUR's _"-bin"_ packages rather than building them from source. Therefore, it's only a link to AUR binaries and if those maintainers don't update, then nothing gets built because the previous package version already exists? In that case, I'm mistaken, and it isn't technically outdated but still a bit disappointing.
2) Upon reviewing build logs, I've come across recent firefox extension builds which also ended with this error and therefore haven't been updated to the repo. This issue appears to have only come up recently, as older packages seem to be unaffected (i.e. `plasma-integration` is up-to-date even with this error, but `flagfox` is outdated). I haven't checked all the extensions, but I posted links to the two builds with errors I found. It's probably a similar issue with retrieving whatever the AUR has linked without downloading the newest extension versions from Mozilla servers.
```
[?25h==> ERROR: A package has already been built. (use -f to overwrite)
Container pkg5f237c1a8d3 failed with error code 13.
```
3) `firefox-kde-opensuse` also contains the appmenu patch and `firefox-kde-opensuse-rpm` is the binary built by OpenSUSE. I'm not sure why _chaotic-aur_ also tries to build this, but it's failing due to what looks like a dependency error:
`error: target not found: kmozillahelper`
I don't know the difference between this package and the one OpenSUSE builds, and if it is the same, then this is redundant and possibly a waste of resources. Therefore, it may be best if someone removed this, especially if we're not willing to also keep up its dependent helper.
https://aur.archlinux.org/packages/firefox-kde-opensuse-rpm
Unfortunately, the AUR maintainer hasn't updated the PKGBUILD, and its RPM download URL fails, so I haven't tested this either. Moreover, this particular binary package **doesn't include the global app menu patch** like the source version does, so I'm confused about what it offers as opposed to just using baseline `firefox` releases with `firefox-extension-plasma-integration` since my reason for using these is for the appmenu support.
Also of interest to this issue is `firefox-ubuntu-bin` as all these global menu Firefox variants seem to rely on `unity-menubar.patch` which comes from Ubuntu. It would be great if we consolidated these packages, which basically do the same thing, without having to rely on Ubuntu's slow build servers.
If AUR maintainers aren't willing to rebuild these binaries in a timely manner, please consider using chaotic-aur to automate builds of Firefox with the relevant patches enabled. The source versions on the AUR are more up-to-date and probably do work, but I would really appreciate if at least one binary of Firefox with appmenu support gets built.
Thanks again to everyone maintaining these packages. I hope the automated builds work again.
| non_test | all firefox s with appmenu are outdated ff extensions possibly need manual intervention if available link to the latest build package name firefox appmenu bin latest build latest version available have you tested if the package builds in a clean chroot yes more information thanks for maintaining these firefox packages however i noticed a few issues firefox has been released for about a week and most variants have already been updated however the binary versions with the global app menu patch have not been updated on the repo according to the build server logs it did complete the firefox appmenu bin build or at least attempted it but there is an error error a package has already been built use f to overwrite i m guessing this is because chaotic aur is fetching the binary versions from the aur s bin packages rather than building them from source therefore it s only a link to aur binaries and if those maintainers don t update then nothing gets built because the previous package version already exists in that case i m mistaken and it isn t technically outdated but still a bit disappointing upon reviewing build logs i ve come across recent firefox extension builds which also ended with this error and therefore haven t been updated to the repo this issue appears to have only come up recently as older packages seem to be unaffected i e plasma integration is up to date even with this error but flagfox is outdated i haven t checked all the extensions but i posted links to the two builds with errors i found it s probably a similar issue with retrieving whatever the aur has linked without downloading the newest extension versions from mozilla servers error a package has already been built use f to overwrite container failed with error code firefox kde opensuse also contains the appmenu patch and firefox kde opensuse rpm is the binary built by opensuse i m not sure why chaotic aur also tries to build this but it s failing due to what looks like a dependency error error target not found kmozillahelper i don t know the difference between this package and the one opensuse builds and if it is the same then this is redundant and possibly a waste of resources therefore it may be best if someone removed this especially if we re not willing to also keep up its dependent helper unfortunately the aur maintainer hasn t updated the pkgbuild and its rpm download url fails so i haven t tested this either moreover this particular binary package doesn t include the global app menu patch like the source version does so i m confused about what it offers as opposed to just using baseline firefox releases with firefox extension plasma integration since my reason for using these is for the appmenu support also of interest to this issue is firefox ubuntu bin as all these global menu firefox variants seem to rely on unity menubar patch which comes from ubuntu it would be great if we consolidated these packages which basically do the same thing without having to rely on ubuntu s slow build servers if aur maintainers aren t willing to rebuild these binaries in a timely manner please consider using chaotic aur to automate builds of firefox with the relevant patches enabled the source versions on the aur are more up to date and probably do work but i would really appreciate if at least one binary of firefox with appmenu support gets built thanks again to everyone maintaining these packages i hope the automated builds work again | 0 |
42,262 | 5,430,280,212 | IssuesEvent | 2017-03-03 20:46:08 | raulir/bccms | https://api.github.com/repos/raulir/bccms | closed | CMS panel settings for list page | business logic feature system testing | Add cms panel settings into definition file under "settings" when list item panel is used on list item page
| 1.0 | CMS panel settings for list page - Add cms panel settings into definition file under "settings" when list item panel is used on list item page
| test | cms panel settings for list page add cms panel settings into definition file under settings when list item panel is used on list item page | 1 |
262,926 | 8,272,612,976 | IssuesEvent | 2018-09-16 22:07:07 | javaee/glassfish | https://api.github.com/repos/javaee/glassfish | closed | container-common has hard dependency on JPA and JTA | Component: other ERR: Assignee Priority: Major Type: Improvement | While experimenting the idea of a light weight web container distribution for GF, I noticed that "container common" module depends on JTA and JPA. This may have been done as a first attempt to modularize the system, but we should fix this now.
#### Affected Versions
[3.1] | 1.0 | container-common has hard dependency on JPA and JTA - While experimenting the idea of a light weight web container distribution for GF, I noticed that "container common" module depends on JTA and JPA. This may have been done as a first attempt to modularize the system, but we should fix this now.
#### Affected Versions
[3.1] | non_test | container common has hard dependency on jpa and jta while experimenting the idea of a light weight web container distribution for gf i noticed that container common module depends on jta and jpa this may have been done as a first attempt to modularize the system but we should fix this now affected versions | 0 |
276,772 | 24,017,279,269 | IssuesEvent | 2022-09-15 02:51:21 | redpanda-data/redpanda | https://api.github.com/repos/redpanda-data/redpanda | closed | CI failure: PartitionBalancerTest.test_fuzz_admin_ops hits an i/o timeout in getting topic metadata | kind/bug area/redpanda area/tests ci-failure | ```
FAIL test: PartitionBalancerTest.test_fuzz_admin_ops (1/24 runs)
failure at 2022-08-16T17:10:39.695Z: RpkException('command /var/lib/buildkite-agent/builds/buildkite-amd64-xfs-builders-i-094550a461782c38b-1/redpanda/redpanda/vbuild/release/clang/dist/local/redpanda/bin/rpk topic --brokers docker-rp-11:9092,docker-rp-20:9092,docker-rp-13:9092,docker-rp-12:9092,docker-rp-14:9092 describe fuzzy-operator-9442-EVlhkr -c returned 1, output: ', 'unable to request topic metadata: read tcp 172.16.16.27:55232->172.16.16.22:9092: i/o timeout\n')
in job https://buildkite.com/redpanda/redpanda/builds/14221#0182a72f-baed-4813-8903-ef58f5c7d4e6
```
Stack trace:
```
====================================================================================================
test_id: rptest.tests.partition_balancer_test.PartitionBalancerTest.test_fuzz_admin_ops
status: FAIL
run time: 9 minutes 56.706 seconds
RpkException('command /var/lib/buildkite-agent/builds/buildkite-amd64-xfs-builders-i-094550a461782c38b-1/redpanda/redpanda/vbuild/release/clang/dist/local/redpanda/bin/rpk topic --brokers docker-rp-11:9092,docker-rp-20:9092,docker-rp-13:9092,docker-rp-12:9092,docker-rp-14:9092 describe fuzzy-operator-9442-EVlhkr -c returned 1, output: ', 'unable to request topic metadata: read tcp 172.16.16.27:55232->172.16.16.22:9092: i/o timeout\n')
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/ducktape/tests/runner_client.py", line 135, in run
data = self.run_test()
File "/usr/local/lib/python3.10/dist-packages/ducktape/tests/runner_client.py", line 227, in run_test
return self.test_context.function(self.test)
File "/root/tests/rptest/services/cluster.py", line 35, in wrapped
r = f(self, *args, **kwargs)
File "/root/tests/rptest/tests/partition_balancer_test.py", line 372, in test_fuzz_admin_ops
admin_fuzz.wait(count=10, timeout=240)
File "/root/tests/rptest/services/admin_ops_fuzzer.py", line 558, in wait
wait_until(check, timeout_sec=timeout, backoff_sec=2)
File "/usr/local/lib/python3.10/dist-packages/ducktape/utils/util.py", line 53, in wait_until
raise e
File "/usr/local/lib/python3.10/dist-packages/ducktape/utils/util.py", line 44, in wait_until
if condition():
File "/root/tests/rptest/services/admin_ops_fuzzer.py", line 547, in check
raise self.error
File "/root/tests/rptest/services/admin_ops_fuzzer.py", line 469, in thread_loop
if self.execute_with_retries(op_type, op):
File "/root/tests/rptest/services/admin_ops_fuzzer.py", line 507, in execute_with_retries
raise error
File "/root/tests/rptest/services/admin_ops_fuzzer.py", line 498, in execute_with_retries
if op.validate(self.redpanda):
File "/root/tests/rptest/services/admin_ops_fuzzer.py", line 181, in validate
desc = rpk.describe_topic_configs(self.topic)
File "/root/tests/rptest/clients/rpk.py", line 282, in describe_topic_configs
output = self._run_topic(cmd)
File "/root/tests/rptest/clients/rpk.py", line 502, in _run_topic
return self._execute(cmd, stdin=stdin, timeout=timeout)
File "/root/tests/rptest/clients/rpk.py", line 618, in _execute
raise RpkException(
rptest.clients.rpk.RpkException: RpkException<command /var/lib/buildkite-agent/builds/buildkite-amd64-xfs-builders-i-094550a461782c38b-1/redpanda/redpanda/vbuild/release/clang/dist/local/redpanda/bin/rpk topic --brokers docker-rp-11:9092,docker-rp-20:9092,docker-rp-13:9092,docker-rp-12:9092,docker-rp-14:9092 describe fuzzy-operator-9442-EVlhkr -c returned 1, output: error: unable to request topic metadata: read tcp 172.16.16.27:55232->172.16.16.22:9092: i/o timeout
>
``` | 1.0 | CI failure: PartitionBalancerTest.test_fuzz_admin_ops hits an i/o timeout in getting topic metadata - ```
FAIL test: PartitionBalancerTest.test_fuzz_admin_ops (1/24 runs)
failure at 2022-08-16T17:10:39.695Z: RpkException('command /var/lib/buildkite-agent/builds/buildkite-amd64-xfs-builders-i-094550a461782c38b-1/redpanda/redpanda/vbuild/release/clang/dist/local/redpanda/bin/rpk topic --brokers docker-rp-11:9092,docker-rp-20:9092,docker-rp-13:9092,docker-rp-12:9092,docker-rp-14:9092 describe fuzzy-operator-9442-EVlhkr -c returned 1, output: ', 'unable to request topic metadata: read tcp 172.16.16.27:55232->172.16.16.22:9092: i/o timeout\n')
in job https://buildkite.com/redpanda/redpanda/builds/14221#0182a72f-baed-4813-8903-ef58f5c7d4e6
```
Stack trace:
```
====================================================================================================
test_id: rptest.tests.partition_balancer_test.PartitionBalancerTest.test_fuzz_admin_ops
status: FAIL
run time: 9 minutes 56.706 seconds
RpkException('command /var/lib/buildkite-agent/builds/buildkite-amd64-xfs-builders-i-094550a461782c38b-1/redpanda/redpanda/vbuild/release/clang/dist/local/redpanda/bin/rpk topic --brokers docker-rp-11:9092,docker-rp-20:9092,docker-rp-13:9092,docker-rp-12:9092,docker-rp-14:9092 describe fuzzy-operator-9442-EVlhkr -c returned 1, output: ', 'unable to request topic metadata: read tcp 172.16.16.27:55232->172.16.16.22:9092: i/o timeout\n')
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/ducktape/tests/runner_client.py", line 135, in run
data = self.run_test()
File "/usr/local/lib/python3.10/dist-packages/ducktape/tests/runner_client.py", line 227, in run_test
return self.test_context.function(self.test)
File "/root/tests/rptest/services/cluster.py", line 35, in wrapped
r = f(self, *args, **kwargs)
File "/root/tests/rptest/tests/partition_balancer_test.py", line 372, in test_fuzz_admin_ops
admin_fuzz.wait(count=10, timeout=240)
File "/root/tests/rptest/services/admin_ops_fuzzer.py", line 558, in wait
wait_until(check, timeout_sec=timeout, backoff_sec=2)
File "/usr/local/lib/python3.10/dist-packages/ducktape/utils/util.py", line 53, in wait_until
raise e
File "/usr/local/lib/python3.10/dist-packages/ducktape/utils/util.py", line 44, in wait_until
if condition():
File "/root/tests/rptest/services/admin_ops_fuzzer.py", line 547, in check
raise self.error
File "/root/tests/rptest/services/admin_ops_fuzzer.py", line 469, in thread_loop
if self.execute_with_retries(op_type, op):
File "/root/tests/rptest/services/admin_ops_fuzzer.py", line 507, in execute_with_retries
raise error
File "/root/tests/rptest/services/admin_ops_fuzzer.py", line 498, in execute_with_retries
if op.validate(self.redpanda):
File "/root/tests/rptest/services/admin_ops_fuzzer.py", line 181, in validate
desc = rpk.describe_topic_configs(self.topic)
File "/root/tests/rptest/clients/rpk.py", line 282, in describe_topic_configs
output = self._run_topic(cmd)
File "/root/tests/rptest/clients/rpk.py", line 502, in _run_topic
return self._execute(cmd, stdin=stdin, timeout=timeout)
File "/root/tests/rptest/clients/rpk.py", line 618, in _execute
raise RpkException(
rptest.clients.rpk.RpkException: RpkException<command /var/lib/buildkite-agent/builds/buildkite-amd64-xfs-builders-i-094550a461782c38b-1/redpanda/redpanda/vbuild/release/clang/dist/local/redpanda/bin/rpk topic --brokers docker-rp-11:9092,docker-rp-20:9092,docker-rp-13:9092,docker-rp-12:9092,docker-rp-14:9092 describe fuzzy-operator-9442-EVlhkr -c returned 1, output: error: unable to request topic metadata: read tcp 172.16.16.27:55232->172.16.16.22:9092: i/o timeout
>
``` | test | ci failure partitionbalancertest test fuzz admin ops hits an i o timeout in getting topic metadata fail test partitionbalancertest test fuzz admin ops runs failure at rpkexception command var lib buildkite agent builds buildkite xfs builders i redpanda redpanda vbuild release clang dist local redpanda bin rpk topic brokers docker rp docker rp docker rp docker rp docker rp describe fuzzy operator evlhkr c returned output unable to request topic metadata read tcp i o timeout n in job stack trace test id rptest tests partition balancer test partitionbalancertest test fuzz admin ops status fail run time minutes seconds rpkexception command var lib buildkite agent builds buildkite xfs builders i redpanda redpanda vbuild release clang dist local redpanda bin rpk topic brokers docker rp docker rp docker rp docker rp docker rp describe fuzzy operator evlhkr c returned output unable to request topic metadata read tcp i o timeout n traceback most recent call last file usr local lib dist packages ducktape tests runner client py line in run data self run test file usr local lib dist packages ducktape tests runner client py line in run test return self test context function self test file root tests rptest services cluster py line in wrapped r f self args kwargs file root tests rptest tests partition balancer test py line in test fuzz admin ops admin fuzz wait count timeout file root tests rptest services admin ops fuzzer py line in wait wait until check timeout sec timeout backoff sec file usr local lib dist packages ducktape utils util py line in wait until raise e file usr local lib dist packages ducktape utils util py line in wait until if condition file root tests rptest services admin ops fuzzer py line in check raise self error file root tests rptest services admin ops fuzzer py line in thread loop if self execute with retries op type op file root tests rptest services admin ops fuzzer py line in execute with retries raise error file root tests rptest services admin ops fuzzer py line in execute with retries if op validate self redpanda file root tests rptest services admin ops fuzzer py line in validate desc rpk describe topic configs self topic file root tests rptest clients rpk py line in describe topic configs output self run topic cmd file root tests rptest clients rpk py line in run topic return self execute cmd stdin stdin timeout timeout file root tests rptest clients rpk py line in execute raise rpkexception rptest clients rpk rpkexception rpkexception i o timeout | 1 |
579,787 | 17,198,745,201 | IssuesEvent | 2021-07-16 22:18:41 | bcgov/ols-devkit | https://api.github.com/repos/bcgov/ols-devkit | closed | In Address List Editor, compute CHSA when geocoding addresses | address list editor enhancement estimate needed high priority | Use the BCGW mapservice to do the point in polygon test against the CHSA coverage. Here's an example request:
https://openmaps.gov.bc.ca/geo/pub/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=pub%3AWHSE_ADMIN_BOUNDARIES.BCHA_CMNTY_HEALTH_SERV_AREA_SP&srsname=EPSG:4326&cql_filter=INTERSECTS(SHAPE,POINT(1224584.57951%20469989.94624))&propertyName=CMNTY_HLTH_SERV_AREA_NAME,LOCAL_HLTH_AREA_NAME,HLTH_SERVICE_DLVR_AREA_NAME,HLTH_AUTHORITY_NAME&outputFormat=application%2Fjson | 1.0 | In Address List Editor, compute CHSA when geocoding addresses - Use the BCGW mapservice to do the point in polygon test against the CHSA coverage. Here's an example request:
https://openmaps.gov.bc.ca/geo/pub/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=pub%3AWHSE_ADMIN_BOUNDARIES.BCHA_CMNTY_HEALTH_SERV_AREA_SP&srsname=EPSG:4326&cql_filter=INTERSECTS(SHAPE,POINT(1224584.57951%20469989.94624))&propertyName=CMNTY_HLTH_SERV_AREA_NAME,LOCAL_HLTH_AREA_NAME,HLTH_SERVICE_DLVR_AREA_NAME,HLTH_AUTHORITY_NAME&outputFormat=application%2Fjson | non_test | in address list editor compute chsa when geocoding addresses use the bcgw mapservice to do the point in polygon test against the chsa coverage here s an example request | 0 |
81,849 | 15,630,177,281 | IssuesEvent | 2021-03-22 01:35:33 | maban/bookmarkbot | https://api.github.com/repos/maban/bookmarkbot | opened | CVE-2020-14001 (High) detected in kramdown-1.17.0.gem | security vulnerability | ## CVE-2020-14001 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>kramdown-1.17.0.gem</b></p></summary>
<p>kramdown is yet-another-markdown-parser but fast, pure Ruby,
using a strict syntax definition and supporting several common extensions.
</p>
<p>Library home page: <a href="https://rubygems.org/gems/kramdown-1.17.0.gem">https://rubygems.org/gems/kramdown-1.17.0.gem</a></p>
<p>Path to dependency file: bookmarkbot/Gemfile.lock</p>
<p>Path to vulnerable library: /var/lib/gems/2.5.0/cache/kramdown-1.17.0.gem</p>
<p>
Dependency Hierarchy:
- minima-2.5.1.gem (Root Library)
- jekyll-feed-0.11.0.gem
- jekyll-3.6.3.gem
- :x: **kramdown-1.17.0.gem** (Vulnerable Library)
</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 kramdown gem before 2.3.0 for Ruby processes the template option inside Kramdown documents by default, which allows unintended read access (such as template="/etc/passwd") or unintended embedded Ruby code execution (such as a string that begins with template="string://<%= `). NOTE: kramdown is used in Jekyll, GitLab Pages, GitHub Pages, and Thredded Forum.
<p>Publish Date: 2020-07-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-14001>CVE-2020-14001</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14001">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14001</a></p>
<p>Release Date: 2020-07-17</p>
<p>Fix Resolution: kramdown - 2.3.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-14001 (High) detected in kramdown-1.17.0.gem - ## CVE-2020-14001 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>kramdown-1.17.0.gem</b></p></summary>
<p>kramdown is yet-another-markdown-parser but fast, pure Ruby,
using a strict syntax definition and supporting several common extensions.
</p>
<p>Library home page: <a href="https://rubygems.org/gems/kramdown-1.17.0.gem">https://rubygems.org/gems/kramdown-1.17.0.gem</a></p>
<p>Path to dependency file: bookmarkbot/Gemfile.lock</p>
<p>Path to vulnerable library: /var/lib/gems/2.5.0/cache/kramdown-1.17.0.gem</p>
<p>
Dependency Hierarchy:
- minima-2.5.1.gem (Root Library)
- jekyll-feed-0.11.0.gem
- jekyll-3.6.3.gem
- :x: **kramdown-1.17.0.gem** (Vulnerable Library)
</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 kramdown gem before 2.3.0 for Ruby processes the template option inside Kramdown documents by default, which allows unintended read access (such as template="/etc/passwd") or unintended embedded Ruby code execution (such as a string that begins with template="string://<%= `). NOTE: kramdown is used in Jekyll, GitLab Pages, GitHub Pages, and Thredded Forum.
<p>Publish Date: 2020-07-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-14001>CVE-2020-14001</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14001">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14001</a></p>
<p>Release Date: 2020-07-17</p>
<p>Fix Resolution: kramdown - 2.3.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_test | cve high detected in kramdown gem cve high severity vulnerability vulnerable library kramdown gem kramdown is yet another markdown parser but fast pure ruby using a strict syntax definition and supporting several common extensions library home page a href path to dependency file bookmarkbot gemfile lock path to vulnerable library var lib gems cache kramdown gem dependency hierarchy minima gem root library jekyll feed gem jekyll gem x kramdown gem vulnerable library vulnerability details the kramdown gem before for ruby processes the template option inside kramdown documents by default which allows unintended read access such as template etc passwd or unintended embedded ruby code execution such as a string that begins with template string note kramdown is used in jekyll gitlab pages github pages and thredded forum 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 kramdown step up your open source security game with whitesource | 0 |
255,798 | 27,504,346,178 | IssuesEvent | 2023-03-06 01:10:46 | panasalap/linux-4.19.72_1 | https://api.github.com/repos/panasalap/linux-4.19.72_1 | opened | CVE-2022-36280 (Medium) detected in linux-yoctov5.4.51 | security vulnerability | ## CVE-2022-36280 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yoctov5.4.51</b></p></summary>
<p>
<p>Yocto Linux Embedded kernel</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto>https://git.yoctoproject.org/git/linux-yocto</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An out-of-bounds(OOB) memory access vulnerability was found in vmwgfx driver in drivers/gpu/vmxgfx/vmxgfx_kms.c in GPU component in the Linux kernel with device file '/dev/dri/renderD128 (or Dxxx)'. This flaw allows a local attacker with a user account on the system to gain privilege, causing a denial of service(DoS).
<p>Publish Date: 2022-09-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-36280>CVE-2022-36280</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2022-36280">https://www.linuxkernelcves.com/cves/CVE-2022-36280</a></p>
<p>Release Date: 2022-09-09</p>
<p>Fix Resolution: v4.9.337,v4.14.303,v4.19.270,v5.4.229,v5.10.163,v5.15.87,v6.0.18,v6.1.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-36280 (Medium) detected in linux-yoctov5.4.51 - ## CVE-2022-36280 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yoctov5.4.51</b></p></summary>
<p>
<p>Yocto Linux Embedded kernel</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto>https://git.yoctoproject.org/git/linux-yocto</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An out-of-bounds(OOB) memory access vulnerability was found in vmwgfx driver in drivers/gpu/vmxgfx/vmxgfx_kms.c in GPU component in the Linux kernel with device file '/dev/dri/renderD128 (or Dxxx)'. This flaw allows a local attacker with a user account on the system to gain privilege, causing a denial of service(DoS).
<p>Publish Date: 2022-09-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-36280>CVE-2022-36280</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2022-36280">https://www.linuxkernelcves.com/cves/CVE-2022-36280</a></p>
<p>Release Date: 2022-09-09</p>
<p>Fix Resolution: v4.9.337,v4.14.303,v4.19.270,v5.4.229,v5.10.163,v5.15.87,v6.0.18,v6.1.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_test | cve medium detected in linux cve medium severity vulnerability vulnerable library linux yocto linux embedded kernel library home page a href found in base branch master vulnerable source files drivers gpu drm vmwgfx vmwgfx kms c drivers gpu drm vmwgfx vmwgfx kms c vulnerability details an out of bounds oob memory access vulnerability was found in vmwgfx driver in drivers gpu vmxgfx vmxgfx kms c in gpu component in the linux kernel with device file dev dri or dxxx this flaw allows a local attacker with a user account on the system to gain privilege causing a denial of service dos publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
181,221 | 14,009,338,273 | IssuesEvent | 2020-10-29 02:06:33 | microsoft/STL | https://api.github.com/repos/microsoft/STL | opened | Test "core" headers | test work in progress | See: https://github.com/microsoft/STL/wiki/The-Difference-Between-Core-And-Non-Core-Headers
During the development of #1370, I damaged the "core" header `<type_traits>` by including `<cstdint>` (which we found just before merging). I didn't even check `<cstdint>` because it was "obviously safe" - it just includes `<stdint.h>` and has using-declarations for typedefs. However, it was also including `<yvals.h>` (having predated the "core"/"non-core" split), which contains the STL's `#pragma detect_mismatch` directives:
https://github.com/microsoft/STL/blob/5f736efd868f0cc32dd4c89d43f8ad9923742647/stl/inc/cstdint#L9
We should have a test that includes all of the headers we expect to be "core", and verifies that they are. | 1.0 | Test "core" headers - See: https://github.com/microsoft/STL/wiki/The-Difference-Between-Core-And-Non-Core-Headers
During the development of #1370, I damaged the "core" header `<type_traits>` by including `<cstdint>` (which we found just before merging). I didn't even check `<cstdint>` because it was "obviously safe" - it just includes `<stdint.h>` and has using-declarations for typedefs. However, it was also including `<yvals.h>` (having predated the "core"/"non-core" split), which contains the STL's `#pragma detect_mismatch` directives:
https://github.com/microsoft/STL/blob/5f736efd868f0cc32dd4c89d43f8ad9923742647/stl/inc/cstdint#L9
We should have a test that includes all of the headers we expect to be "core", and verifies that they are. | test | test core headers see during the development of i damaged the core header by including which we found just before merging i didn t even check because it was obviously safe it just includes and has using declarations for typedefs however it was also including having predated the core non core split which contains the stl s pragma detect mismatch directives we should have a test that includes all of the headers we expect to be core and verifies that they are | 1 |
1,377 | 2,595,665,423 | IssuesEvent | 2015-02-20 15:46:08 | OraOpenSource/Logger | https://api.github.com/repos/OraOpenSource/Logger | reopened | Improve documentation regarding "PROTECT_ADMIN_PROCS" | Documentation Not Implemented | _From @martindsouza on May 14, 2013 20:48_
_Copied from original issue: tmuth/Logger---A-PL-SQL-Logging-Utility#22_ | 1.0 | Improve documentation regarding "PROTECT_ADMIN_PROCS" - _From @martindsouza on May 14, 2013 20:48_
_Copied from original issue: tmuth/Logger---A-PL-SQL-Logging-Utility#22_ | non_test | improve documentation regarding protect admin procs from martindsouza on may copied from original issue tmuth logger a pl sql logging utility | 0 |
60,028 | 6,669,441,212 | IssuesEvent | 2017-10-03 19:21:49 | servo/servo | https://api.github.com/repos/servo/servo | closed | assertion failed: !self.contains(&sheet) | A-layout/uncategorized C-has-manual-testcase I-panic | Found with domato.
```html
<style>
* { display: none}
</style>
```
```gdb
assertion failed: !self.contains(&sheet) (thread LayoutThread PipelineId { namespace_id: PipelineNamespaceId(0), index: PipelineIndex(NonZero(1)) }, at /shared/dev/rust/servo/components/style/stylesheet_set.rs:330)
stack backtrace:
0: 0x5650a7c91884 - backtrace::backtrace::libunwind::trace
at /shared/dev/rust/servo/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.2/src/backtrace/libunwind.rs:53
- backtrace::backtrace::trace<closure>
at /shared/dev/rust/servo/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.2/src/backtrace/mod.rs:42
1: 0x5650a7c849ef - backtrace::capture::{{impl}}::new
at /shared/dev/rust/servo/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.2/src/capture.rs:64
2: 0x5650a128a78e - servo::main::{{closure}}
at /shared/dev/rust/servo/ports/servo/main.rs:130
3: 0x5650a7f6a456 - std::panicking::rust_panic_with_hook
at /checkout/src/libstd/panicking.rs:578
4: 0x5650a6a95955 - std::panicking::begin_panic<&str>
at /checkout/src/libstd/panicking.rs:538
5: 0x5650a6b8c047 - style::stylesheet_set::{{impl}}::append<style::stylesheets::stylesheet::DocumentStyleSheet>
at /shared/dev/rust/servo/components/style/stylesheet_set.rs:330
6: 0x5650a6b8c762 - style::stylesheet_set::{{impl}}::append_stylesheet<style::stylesheets::stylesheet::DocumentStyleSheet>
at /shared/dev/rust/servo/components/style/stylesheet_set.rs:441
7: 0x5650a70c6cea - style::stylist::{{impl}}::append_stylesheet
at /shared/dev/rust/servo/components/style/stylist.rs:601
8: 0x5650a1ba82c1 - layout_thread::{{impl}}::handle_reflow
at /shared/dev/rust/servo/components/layout_thread/lib.rs:1189
9: 0x5650a1ba316d - layout_thread::{{impl}}::handle_request_helper::{{closure}}
at /shared/dev/rust/servo/components/layout_thread/lib.rs:700
10: 0x5650a1a49f53 - profile_traits::time::profile<(),closure>
at /shared/dev/rust/servo/components/profile_traits/time.rs:124
11: 0x5650a1ba1d6e - layout_thread::{{impl}}::handle_request_helper
at /shared/dev/rust/servo/components/layout_thread/lib.rs:697
12: 0x5650a1ba0b0b - layout_thread::{{impl}}::handle_request
at /shared/dev/rust/servo/components/layout_thread/lib.rs:644
13: 0x5650a1b9fe23 - layout_thread::{{impl}}::start
at /shared/dev/rust/servo/components/layout_thread/lib.rs:557
14: 0x5650a1c51829 - layout_thread::{{impl}}::create::{{closure}}::{{closure}}
at /shared/dev/rust/servo/components/layout_thread/lib.rs:316
15: 0x5650a1bc3284 - profile_traits::mem::{{impl}}::run_with_memory_reporting<closure,fn(profile_traits::mem::ReportsChan) -> script_layout_interface::message::Msg,script_layout_interface::message::Msg,std::sync::mpsc::Sender<script_layout_interface::message::Msg>>
at /shared/dev/rust/servo/components/profile_traits/mem.rs:63
16: 0x5650a1ea34a3 - layout_thread::{{impl}}::create::{{closure}}
at /shared/dev/rust/servo/components/layout_thread/lib.rs:315
17: 0x5650a1de2a2a - std::sys_common::backtrace::__rust_begin_short_backtrace<closure,()>
at /checkout/src/libstd/sys_common/backtrace.rs:136
18: 0x5650a1de4883 - std::thread::{{impl}}::spawn::{{closure}}::{{closure}}<closure,()>
at /checkout/src/libstd/thread/mod.rs:394
19: 0x5650a1d8931a - std::panic::{{impl}}::call_once<(),closure>
at /checkout/src/libstd/panic.rs:296
20: 0x5650a1a815e2 - std::panicking::try::do_call<std::panic::AssertUnwindSafe<closure>,()>
at /checkout/src/libstd/panicking.rs:480
21: 0x5650a7f715ec - panic_unwind::__rust_maybe_catch_panic
at /checkout/src/libpanic_unwind/lib.rs:99
22: 0x5650a1a807dc - std::panicking::try<(),std::panic::AssertUnwindSafe<closure>>
at /checkout/src/libstd/panicking.rs:459
23: 0x5650a1de3af5 - std::panic::catch_unwind<std::panic::AssertUnwindSafe<closure>,()>
at /checkout/src/libstd/panic.rs:361
24: 0x5650a1de46ab - std::thread::{{impl}}::spawn::{{closure}}<closure,()>
at /checkout/src/libstd/thread/mod.rs:393
25: 0x5650a1e25ce3 - alloc::boxed::{{impl}}::call_box<(),closure>
at /checkout/src/liballoc/boxed.rs:728
26: 0x5650a7f690db - alloc::boxed::{{impl}}::call_once<(),()>
at /checkout/src/liballoc/boxed.rs:738
- std::sys_common::thread::start_thread
at /checkout/src/libstd/sys_common/thread.rs:24
- std::sys::imp::thread::{{impl}}::new::thread_start
at /checkout/src/libstd/sys/unix/thread.rs:90
27: 0x7fdca4609493 - start_thread
28: 0x7fdca4136abe - __clone
29: 0x0 - <unknown>
ERROR:servo: assertion failed: !self.contains(&sheet)
``` | 1.0 | assertion failed: !self.contains(&sheet) - Found with domato.
```html
<style>
* { display: none}
</style>
```
```gdb
assertion failed: !self.contains(&sheet) (thread LayoutThread PipelineId { namespace_id: PipelineNamespaceId(0), index: PipelineIndex(NonZero(1)) }, at /shared/dev/rust/servo/components/style/stylesheet_set.rs:330)
stack backtrace:
0: 0x5650a7c91884 - backtrace::backtrace::libunwind::trace
at /shared/dev/rust/servo/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.2/src/backtrace/libunwind.rs:53
- backtrace::backtrace::trace<closure>
at /shared/dev/rust/servo/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.2/src/backtrace/mod.rs:42
1: 0x5650a7c849ef - backtrace::capture::{{impl}}::new
at /shared/dev/rust/servo/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.2/src/capture.rs:64
2: 0x5650a128a78e - servo::main::{{closure}}
at /shared/dev/rust/servo/ports/servo/main.rs:130
3: 0x5650a7f6a456 - std::panicking::rust_panic_with_hook
at /checkout/src/libstd/panicking.rs:578
4: 0x5650a6a95955 - std::panicking::begin_panic<&str>
at /checkout/src/libstd/panicking.rs:538
5: 0x5650a6b8c047 - style::stylesheet_set::{{impl}}::append<style::stylesheets::stylesheet::DocumentStyleSheet>
at /shared/dev/rust/servo/components/style/stylesheet_set.rs:330
6: 0x5650a6b8c762 - style::stylesheet_set::{{impl}}::append_stylesheet<style::stylesheets::stylesheet::DocumentStyleSheet>
at /shared/dev/rust/servo/components/style/stylesheet_set.rs:441
7: 0x5650a70c6cea - style::stylist::{{impl}}::append_stylesheet
at /shared/dev/rust/servo/components/style/stylist.rs:601
8: 0x5650a1ba82c1 - layout_thread::{{impl}}::handle_reflow
at /shared/dev/rust/servo/components/layout_thread/lib.rs:1189
9: 0x5650a1ba316d - layout_thread::{{impl}}::handle_request_helper::{{closure}}
at /shared/dev/rust/servo/components/layout_thread/lib.rs:700
10: 0x5650a1a49f53 - profile_traits::time::profile<(),closure>
at /shared/dev/rust/servo/components/profile_traits/time.rs:124
11: 0x5650a1ba1d6e - layout_thread::{{impl}}::handle_request_helper
at /shared/dev/rust/servo/components/layout_thread/lib.rs:697
12: 0x5650a1ba0b0b - layout_thread::{{impl}}::handle_request
at /shared/dev/rust/servo/components/layout_thread/lib.rs:644
13: 0x5650a1b9fe23 - layout_thread::{{impl}}::start
at /shared/dev/rust/servo/components/layout_thread/lib.rs:557
14: 0x5650a1c51829 - layout_thread::{{impl}}::create::{{closure}}::{{closure}}
at /shared/dev/rust/servo/components/layout_thread/lib.rs:316
15: 0x5650a1bc3284 - profile_traits::mem::{{impl}}::run_with_memory_reporting<closure,fn(profile_traits::mem::ReportsChan) -> script_layout_interface::message::Msg,script_layout_interface::message::Msg,std::sync::mpsc::Sender<script_layout_interface::message::Msg>>
at /shared/dev/rust/servo/components/profile_traits/mem.rs:63
16: 0x5650a1ea34a3 - layout_thread::{{impl}}::create::{{closure}}
at /shared/dev/rust/servo/components/layout_thread/lib.rs:315
17: 0x5650a1de2a2a - std::sys_common::backtrace::__rust_begin_short_backtrace<closure,()>
at /checkout/src/libstd/sys_common/backtrace.rs:136
18: 0x5650a1de4883 - std::thread::{{impl}}::spawn::{{closure}}::{{closure}}<closure,()>
at /checkout/src/libstd/thread/mod.rs:394
19: 0x5650a1d8931a - std::panic::{{impl}}::call_once<(),closure>
at /checkout/src/libstd/panic.rs:296
20: 0x5650a1a815e2 - std::panicking::try::do_call<std::panic::AssertUnwindSafe<closure>,()>
at /checkout/src/libstd/panicking.rs:480
21: 0x5650a7f715ec - panic_unwind::__rust_maybe_catch_panic
at /checkout/src/libpanic_unwind/lib.rs:99
22: 0x5650a1a807dc - std::panicking::try<(),std::panic::AssertUnwindSafe<closure>>
at /checkout/src/libstd/panicking.rs:459
23: 0x5650a1de3af5 - std::panic::catch_unwind<std::panic::AssertUnwindSafe<closure>,()>
at /checkout/src/libstd/panic.rs:361
24: 0x5650a1de46ab - std::thread::{{impl}}::spawn::{{closure}}<closure,()>
at /checkout/src/libstd/thread/mod.rs:393
25: 0x5650a1e25ce3 - alloc::boxed::{{impl}}::call_box<(),closure>
at /checkout/src/liballoc/boxed.rs:728
26: 0x5650a7f690db - alloc::boxed::{{impl}}::call_once<(),()>
at /checkout/src/liballoc/boxed.rs:738
- std::sys_common::thread::start_thread
at /checkout/src/libstd/sys_common/thread.rs:24
- std::sys::imp::thread::{{impl}}::new::thread_start
at /checkout/src/libstd/sys/unix/thread.rs:90
27: 0x7fdca4609493 - start_thread
28: 0x7fdca4136abe - __clone
29: 0x0 - <unknown>
ERROR:servo: assertion failed: !self.contains(&sheet)
``` | test | assertion failed self contains sheet found with domato html display none gdb assertion failed self contains sheet thread layoutthread pipelineid namespace id pipelinenamespaceid index pipelineindex nonzero at shared dev rust servo components style stylesheet set rs stack backtrace backtrace backtrace libunwind trace at shared dev rust servo cargo registry src github com backtrace src backtrace libunwind rs backtrace backtrace trace at shared dev rust servo cargo registry src github com backtrace src backtrace mod rs backtrace capture impl new at shared dev rust servo cargo registry src github com backtrace src capture rs servo main closure at shared dev rust servo ports servo main rs std panicking rust panic with hook at checkout src libstd panicking rs std panicking begin panic at checkout src libstd panicking rs style stylesheet set impl append at shared dev rust servo components style stylesheet set rs style stylesheet set impl append stylesheet at shared dev rust servo components style stylesheet set rs style stylist impl append stylesheet at shared dev rust servo components style stylist rs layout thread impl handle reflow at shared dev rust servo components layout thread lib rs layout thread impl handle request helper closure at shared dev rust servo components layout thread lib rs profile traits time profile at shared dev rust servo components profile traits time rs layout thread impl handle request helper at shared dev rust servo components layout thread lib rs layout thread impl handle request at shared dev rust servo components layout thread lib rs layout thread impl start at shared dev rust servo components layout thread lib rs layout thread impl create closure closure at shared dev rust servo components layout thread lib rs profile traits mem impl run with memory reporting script layout interface message msg script layout interface message msg std sync mpsc sender at shared dev rust servo components profile traits mem rs layout thread impl create closure at shared dev rust servo components layout thread lib rs std sys common backtrace rust begin short backtrace at checkout src libstd sys common backtrace rs std thread impl spawn closure closure at checkout src libstd thread mod rs std panic impl call once at checkout src libstd panic rs std panicking try do call at checkout src libstd panicking rs panic unwind rust maybe catch panic at checkout src libpanic unwind lib rs std panicking try at checkout src libstd panicking rs std panic catch unwind at checkout src libstd panic rs std thread impl spawn closure at checkout src libstd thread mod rs alloc boxed impl call box at checkout src liballoc boxed rs alloc boxed impl call once at checkout src liballoc boxed rs std sys common thread start thread at checkout src libstd sys common thread rs std sys imp thread impl new thread start at checkout src libstd sys unix thread rs start thread clone error servo assertion failed self contains sheet | 1 |
181,514 | 6,661,449,638 | IssuesEvent | 2017-10-02 08:40:04 | CS2103AUG2017-T14-B4/main | https://api.github.com/repos/CS2103AUG2017-T14-B4/main | opened | I think we need to brainstorm more user stories | help wanted priority.high status.ongoing | .. and then meet up some time before tutorial to decide which one we want in v2.0. | 1.0 | I think we need to brainstorm more user stories - .. and then meet up some time before tutorial to decide which one we want in v2.0. | non_test | i think we need to brainstorm more user stories and then meet up some time before tutorial to decide which one we want in | 0 |
279,083 | 21,110,823,678 | IssuesEvent | 2022-04-05 01:12:53 | filipgraniczny/trip-tracker-csci201 | https://api.github.com/repos/filipgraniczny/trip-tracker-csci201 | closed | Design: Tripline Logo | documentation frontend | Design of the Tripline logo, which will be featured on the front-end and the repo.
Color palette:
- White Base with Green (#34945c) accent | 1.0 | Design: Tripline Logo - Design of the Tripline logo, which will be featured on the front-end and the repo.
Color palette:
- White Base with Green (#34945c) accent | non_test | design tripline logo design of the tripline logo which will be featured on the front end and the repo color palette white base with green accent | 0 |
521,368 | 15,108,415,849 | IssuesEvent | 2021-02-08 16:36:26 | zephyrproject-rtos/zephyr | https://api.github.com/repos/zephyrproject-rtos/zephyr | closed | build error with llvm: samples/subsys/fs/littlefs | bug priority: low | **Describe the bug**
When building with llvm:
```
ccache /usr/lib64/ccache/clang -DBUILD_VERSION=v2.5.0-rc3-3-ge620568d6dc0 -DKERNEL -D_POSIX_C_SOURCE=200809 -D_XOPEN_SOURCE=600 -D_XOPEN_SOURCE_EXTENDED -D__ZEPHYR__=1 -I/home/nashif/Work/zephyrproject/zephyr/subsys/fs -I/home/nashif/Work/zephyrproject/zephyr/include -Izephyr/include/generated -I/home/nashif/Work/zephyrproject/zephyr/soc/posix/inf_clock -I/home/nashif/Work/zephyrproject/zephyr/boards/posix/native_posix -I/home/nashif/Work/zephyrproject/modules/fs/littlefs -Og -imacros /dev/shm/twister-out/native_posix/samples/subsys/fs/littlefs/sample.filesystem.littlefs/zephyr/include/generated/autoconf.h -ffreestanding -fno-common -g -imacros /home/nashif/Work/zephyrproject/zephyr/include/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-main -Wno-typedef-redefinition -Wno-pointer-sign -Wpointer-arith -Wno-sometimes-uninitialized -Wno-shift-overflow -Wno-missing-braces -Wno-self-assign -Wno-address-of-packed-member -Wno-unused-function -Wno-initializer-overrides -Wno-section -Wno-unknown-warning-option -Wno-unused-variable -Wno-format-invalid-specifier -Wno-gnu -Wno-tautological-compare -Werror=implicit-int -Werror -fno-asynchronous-unwind-tables -fno-pie -fno-pic -fno-strict-overflow -fmacro-prefix-map=/home/nashif/Work/zephyrproject/zephyr/samples/subsys/fs/littlefs=CMAKE_SOURCE_DIR -fmacro-prefix-map=/home/nashif/Work/zephyrproject/zephyr=ZEPHYR_BASE -fmacro-prefix-map=/home/nashif/Work/zephyrproject=WEST_TOPDIR -ffunction-sections -fdata-sections -m32 -include /home/nashif/Work/zephyrproject/zephyr/arch/posix/include/posix_cheats.h -std=c11 -MD -MT zephyr/subsys/fs/CMakeFiles/subsys__fs.dir/littlefs_fs.c.obj -MF zephyr/subsys/fs/CMakeFiles/subsys__fs.dir/littlefs_fs.c.obj.d -o zephyr/subsys/fs/CMakeFiles/subsys__fs.dir/littlefs_fs.c.obj -c /home/nashif/Work/zephyrproject/zephyr/subsys/fs/littlefs_fs.c
/home/nashif/Work/zephyrproject/zephyr/subsys/fs/littlefs_fs.c:47:5: error: macro expansion producing 'defined' has undefined behavior [-Werror,-Wexpansion-to-defined]
#if FC_ON_HEAP
^
/home/nashif/Work/zephyrproject/zephyr/subsys/fs/littlefs_fs.c:44:20: note: expanded from macro 'FC_ON_HEAP'
#define FC_ON_HEAP defined(CONFIG_FS_LITTLEFS_FC_MEM_POOL) \
^
/home/nashif/Work/zephyrproject/zephyr/subsys/fs/littlefs_fs.c:88:5: error: macro expansion producing 'defined' has undefined behavior [-Werror,-Wexpansion-to-defined]
#if FC_ON_HEAP
^
/home/nashif/Work/zephyrproject/zephyr/subsys/fs/littlefs_fs.c:44:20: note: expanded from macro 'FC_ON_HEAP'
#define FC_ON_HEAP defined(CONFIG_FS_LITTLEFS_FC_MEM_POOL) \
^
/home/nashif/Work/zephyrproject/zephyr/subsys/fs/littlefs_fs.c:104:5: error: macro expansion producing 'defined' has undefine
d behavior [-Werror,-Wexpansion-to-defined]
#if FC_ON_HEAP
^
/home/nashif/Work/zephyrproject/zephyr/subsys/fs/littlefs_fs.c:44:20: note: expanded from macro 'FC_ON_HEAP'
#define FC_ON_HEAP defined(CONFIG_FS_LITTLEFS_FC_MEM_POOL) \
^
3 errors generated.
```
**To Reproduce**
Steps to reproduce the behavior:
1. export ZEPHYR_TOOLCHAIN_VARIANT=llvm
2. twister -T samples/subsys/fs/littlefs -p native_posix
**Expected behavior**
build is successful
*
**Environment (please complete the following information):**
- OS: Linux
- Toolchain LLVM 11
- Commit SHA or Version used
| 1.0 | build error with llvm: samples/subsys/fs/littlefs - **Describe the bug**
When building with llvm:
```
ccache /usr/lib64/ccache/clang -DBUILD_VERSION=v2.5.0-rc3-3-ge620568d6dc0 -DKERNEL -D_POSIX_C_SOURCE=200809 -D_XOPEN_SOURCE=600 -D_XOPEN_SOURCE_EXTENDED -D__ZEPHYR__=1 -I/home/nashif/Work/zephyrproject/zephyr/subsys/fs -I/home/nashif/Work/zephyrproject/zephyr/include -Izephyr/include/generated -I/home/nashif/Work/zephyrproject/zephyr/soc/posix/inf_clock -I/home/nashif/Work/zephyrproject/zephyr/boards/posix/native_posix -I/home/nashif/Work/zephyrproject/modules/fs/littlefs -Og -imacros /dev/shm/twister-out/native_posix/samples/subsys/fs/littlefs/sample.filesystem.littlefs/zephyr/include/generated/autoconf.h -ffreestanding -fno-common -g -imacros /home/nashif/Work/zephyrproject/zephyr/include/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wno-main -Wno-typedef-redefinition -Wno-pointer-sign -Wpointer-arith -Wno-sometimes-uninitialized -Wno-shift-overflow -Wno-missing-braces -Wno-self-assign -Wno-address-of-packed-member -Wno-unused-function -Wno-initializer-overrides -Wno-section -Wno-unknown-warning-option -Wno-unused-variable -Wno-format-invalid-specifier -Wno-gnu -Wno-tautological-compare -Werror=implicit-int -Werror -fno-asynchronous-unwind-tables -fno-pie -fno-pic -fno-strict-overflow -fmacro-prefix-map=/home/nashif/Work/zephyrproject/zephyr/samples/subsys/fs/littlefs=CMAKE_SOURCE_DIR -fmacro-prefix-map=/home/nashif/Work/zephyrproject/zephyr=ZEPHYR_BASE -fmacro-prefix-map=/home/nashif/Work/zephyrproject=WEST_TOPDIR -ffunction-sections -fdata-sections -m32 -include /home/nashif/Work/zephyrproject/zephyr/arch/posix/include/posix_cheats.h -std=c11 -MD -MT zephyr/subsys/fs/CMakeFiles/subsys__fs.dir/littlefs_fs.c.obj -MF zephyr/subsys/fs/CMakeFiles/subsys__fs.dir/littlefs_fs.c.obj.d -o zephyr/subsys/fs/CMakeFiles/subsys__fs.dir/littlefs_fs.c.obj -c /home/nashif/Work/zephyrproject/zephyr/subsys/fs/littlefs_fs.c
/home/nashif/Work/zephyrproject/zephyr/subsys/fs/littlefs_fs.c:47:5: error: macro expansion producing 'defined' has undefined behavior [-Werror,-Wexpansion-to-defined]
#if FC_ON_HEAP
^
/home/nashif/Work/zephyrproject/zephyr/subsys/fs/littlefs_fs.c:44:20: note: expanded from macro 'FC_ON_HEAP'
#define FC_ON_HEAP defined(CONFIG_FS_LITTLEFS_FC_MEM_POOL) \
^
/home/nashif/Work/zephyrproject/zephyr/subsys/fs/littlefs_fs.c:88:5: error: macro expansion producing 'defined' has undefined behavior [-Werror,-Wexpansion-to-defined]
#if FC_ON_HEAP
^
/home/nashif/Work/zephyrproject/zephyr/subsys/fs/littlefs_fs.c:44:20: note: expanded from macro 'FC_ON_HEAP'
#define FC_ON_HEAP defined(CONFIG_FS_LITTLEFS_FC_MEM_POOL) \
^
/home/nashif/Work/zephyrproject/zephyr/subsys/fs/littlefs_fs.c:104:5: error: macro expansion producing 'defined' has undefine
d behavior [-Werror,-Wexpansion-to-defined]
#if FC_ON_HEAP
^
/home/nashif/Work/zephyrproject/zephyr/subsys/fs/littlefs_fs.c:44:20: note: expanded from macro 'FC_ON_HEAP'
#define FC_ON_HEAP defined(CONFIG_FS_LITTLEFS_FC_MEM_POOL) \
^
3 errors generated.
```
**To Reproduce**
Steps to reproduce the behavior:
1. export ZEPHYR_TOOLCHAIN_VARIANT=llvm
2. twister -T samples/subsys/fs/littlefs -p native_posix
**Expected behavior**
build is successful
*
**Environment (please complete the following information):**
- OS: Linux
- Toolchain LLVM 11
- Commit SHA or Version used
| non_test | build error with llvm samples subsys fs littlefs describe the bug when building with llvm ccache usr ccache clang dbuild version dkernel d posix c source d xopen source d xopen source extended d zephyr i home nashif work zephyrproject zephyr subsys fs i home nashif work zephyrproject zephyr include izephyr include generated i home nashif work zephyrproject zephyr soc posix inf clock i home nashif work zephyrproject zephyr boards posix native posix i home nashif work zephyrproject modules fs littlefs og imacros dev shm twister out native posix samples subsys fs littlefs sample filesystem littlefs zephyr include generated autoconf h ffreestanding fno common g imacros home nashif work zephyrproject zephyr include toolchain zephyr stdint h wall wformat wformat security wno format zero length wno main wno typedef redefinition wno pointer sign wpointer arith wno sometimes uninitialized wno shift overflow wno missing braces wno self assign wno address of packed member wno unused function wno initializer overrides wno section wno unknown warning option wno unused variable wno format invalid specifier wno gnu wno tautological compare werror implicit int werror fno asynchronous unwind tables fno pie fno pic fno strict overflow fmacro prefix map home nashif work zephyrproject zephyr samples subsys fs littlefs cmake source dir fmacro prefix map home nashif work zephyrproject zephyr zephyr base fmacro prefix map home nashif work zephyrproject west topdir ffunction sections fdata sections include home nashif work zephyrproject zephyr arch posix include posix cheats h std md mt zephyr subsys fs cmakefiles subsys fs dir littlefs fs c obj mf zephyr subsys fs cmakefiles subsys fs dir littlefs fs c obj d o zephyr subsys fs cmakefiles subsys fs dir littlefs fs c obj c home nashif work zephyrproject zephyr subsys fs littlefs fs c home nashif work zephyrproject zephyr subsys fs littlefs fs c error macro expansion producing defined has undefined behavior if fc on heap home nashif work zephyrproject zephyr subsys fs littlefs fs c note expanded from macro fc on heap define fc on heap defined config fs littlefs fc mem pool home nashif work zephyrproject zephyr subsys fs littlefs fs c error macro expansion producing defined has undefined behavior if fc on heap home nashif work zephyrproject zephyr subsys fs littlefs fs c note expanded from macro fc on heap define fc on heap defined config fs littlefs fc mem pool home nashif work zephyrproject zephyr subsys fs littlefs fs c error macro expansion producing defined has undefine d behavior if fc on heap home nashif work zephyrproject zephyr subsys fs littlefs fs c note expanded from macro fc on heap define fc on heap defined config fs littlefs fc mem pool errors generated to reproduce steps to reproduce the behavior export zephyr toolchain variant llvm twister t samples subsys fs littlefs p native posix expected behavior build is successful environment please complete the following information os linux toolchain llvm commit sha or version used | 0 |
155,788 | 12,270,300,066 | IssuesEvent | 2020-05-07 15:18:00 | pytorch/pytorch | https://api.github.com/repos/pytorch/pytorch | opened | DISABLED test_barrier_group_cuda (__main__.TestDistBackend) | module: distributed topic: flaky-tests triaged | https://app.circleci.com/pipelines/github/pytorch/pytorch/165903/workflows/5805cf41-ee8c-4a5d-bf4d-512b57b0b9b0/jobs/5383911/steps
```
May 07 08:33:15 ======================================================================
May 07 08:33:15 FAIL [0.206s]: test_barrier_group_cuda (__main__.TestDistBackend)
May 07 08:33:15 ----------------------------------------------------------------------
May 07 08:33:15 Traceback (most recent call last):
May 07 08:33:15 File "/opt/conda/lib/python3.6/site-packages/torch/testing/_internal/common_distributed.py", line 173, in wrapper
May 07 08:33:15 self._join_processes(fn)
May 07 08:33:15 File "/opt/conda/lib/python3.6/site-packages/torch/testing/_internal/common_distributed.py", line 275, in _join_processes
May 07 08:33:15 self._check_return_codes(elapsed_time)
May 07 08:33:15 File "/opt/conda/lib/python3.6/site-packages/torch/testing/_internal/common_distributed.py", line 327, in _check_return_codes
May 07 08:33:15 "Expected zero exit code but got {}".format(first_process.exitcode)
May 07 08:33:15 File "/opt/conda/lib/python3.6/site-packages/torch/testing/_internal/common_utils.py", line 973, in assertEqual
May 07 08:33:15 super().assertLessEqual(abs(x - y), atol, message)
May 07 08:33:15 AssertionError: 77 not less than or equal to 1e-05 : Expected zero exit code but got 77
``` | 1.0 | DISABLED test_barrier_group_cuda (__main__.TestDistBackend) - https://app.circleci.com/pipelines/github/pytorch/pytorch/165903/workflows/5805cf41-ee8c-4a5d-bf4d-512b57b0b9b0/jobs/5383911/steps
```
May 07 08:33:15 ======================================================================
May 07 08:33:15 FAIL [0.206s]: test_barrier_group_cuda (__main__.TestDistBackend)
May 07 08:33:15 ----------------------------------------------------------------------
May 07 08:33:15 Traceback (most recent call last):
May 07 08:33:15 File "/opt/conda/lib/python3.6/site-packages/torch/testing/_internal/common_distributed.py", line 173, in wrapper
May 07 08:33:15 self._join_processes(fn)
May 07 08:33:15 File "/opt/conda/lib/python3.6/site-packages/torch/testing/_internal/common_distributed.py", line 275, in _join_processes
May 07 08:33:15 self._check_return_codes(elapsed_time)
May 07 08:33:15 File "/opt/conda/lib/python3.6/site-packages/torch/testing/_internal/common_distributed.py", line 327, in _check_return_codes
May 07 08:33:15 "Expected zero exit code but got {}".format(first_process.exitcode)
May 07 08:33:15 File "/opt/conda/lib/python3.6/site-packages/torch/testing/_internal/common_utils.py", line 973, in assertEqual
May 07 08:33:15 super().assertLessEqual(abs(x - y), atol, message)
May 07 08:33:15 AssertionError: 77 not less than or equal to 1e-05 : Expected zero exit code but got 77
``` | test | disabled test barrier group cuda main testdistbackend may may fail test barrier group cuda main testdistbackend may may traceback most recent call last may file opt conda lib site packages torch testing internal common distributed py line in wrapper may self join processes fn may file opt conda lib site packages torch testing internal common distributed py line in join processes may self check return codes elapsed time may file opt conda lib site packages torch testing internal common distributed py line in check return codes may expected zero exit code but got format first process exitcode may file opt conda lib site packages torch testing internal common utils py line in assertequal may super assertlessequal abs x y atol message may assertionerror not less than or equal to expected zero exit code but got | 1 |
151,523 | 5,823,740,872 | IssuesEvent | 2017-05-07 05:16:52 | broadinstitute/gatk | https://api.github.com/repos/broadinstitute/gatk | closed | Why SGA, the currently used assembler for SV pipeline, generates slightly diff results on different runs. | PRIORITY_LOW question SV | SGA, when run with exactly the same parameters on the same machine,
yields slightly different results
- "SNP" between the contigs, or
- slightly different assembled contig lengths
| 1.0 | Why SGA, the currently used assembler for SV pipeline, generates slightly diff results on different runs. - SGA, when run with exactly the same parameters on the same machine,
yields slightly different results
- "SNP" between the contigs, or
- slightly different assembled contig lengths
| non_test | why sga the currently used assembler for sv pipeline generates slightly diff results on different runs sga when run with exactly the same parameters on the same machine yields slightly different results snp between the contigs or slightly different assembled contig lengths | 0 |
108,776 | 9,332,065,650 | IssuesEvent | 2019-03-28 11:14:40 | DivanteLtd/storefront-ui | https://api.github.com/repos/DivanteLtd/storefront-ui | closed | [ Mobile ] Create Header mobile view | 1: Easy styling tests | 
**Proposed api**
- slot left
- slot right
- slot center
- default slot
**How to find on designs**
See designs: https://www.figma.com/file/hrwE3VsMBHgdJoS86rVr4W/Desktop-%26-Mobile-Vue-Storefront?node-id=291%3A1461
Under "components" tab on bottom left corner find "mobile components -> top bar"
| 1.0 | [ Mobile ] Create Header mobile view - 
**Proposed api**
- slot left
- slot right
- slot center
- default slot
**How to find on designs**
See designs: https://www.figma.com/file/hrwE3VsMBHgdJoS86rVr4W/Desktop-%26-Mobile-Vue-Storefront?node-id=291%3A1461
Under "components" tab on bottom left corner find "mobile components -> top bar"
| test | create header mobile view proposed api slot left slot right slot center default slot how to find on designs see designs under components tab on bottom left corner find mobile components top bar | 1 |
66,256 | 6,994,398,763 | IssuesEvent | 2017-12-15 15:14:41 | atlasmap/atlasmap | https://api.github.com/repos/atlasmap/atlasmap | closed | Establish e2e tests in AtlasMap | module/tests module/ui | |<img src="https://avatars2.githubusercontent.com/u/265462?v=4" valign="middle" width="22px"></img> @igarashitm | [2017-11-09](https://github.com/atlasmap/atlasmap-ui/issues/126) | test |
|-|-|-|
Generate mapping definition from browser automation kind of thing via AtlasMap UI, retrieve saved mapping file and let camel-atlasmap consume that mapping file, and verify all the mappings works as expected. | 1.0 | Establish e2e tests in AtlasMap - |<img src="https://avatars2.githubusercontent.com/u/265462?v=4" valign="middle" width="22px"></img> @igarashitm | [2017-11-09](https://github.com/atlasmap/atlasmap-ui/issues/126) | test |
|-|-|-|
Generate mapping definition from browser automation kind of thing via AtlasMap UI, retrieve saved mapping file and let camel-atlasmap consume that mapping file, and verify all the mappings works as expected. | test | establish tests in atlasmap igarashitm test generate mapping definition from browser automation kind of thing via atlasmap ui retrieve saved mapping file and let camel atlasmap consume that mapping file and verify all the mappings works as expected | 1 |
49,821 | 6,041,231,754 | IssuesEvent | 2017-06-10 22:07:56 | syscoin/blockmarket-desktop-public | https://api.github.com/repos/syscoin/blockmarket-desktop-public | closed | right clicking after highlighting does not work | bug highpriority retest in beta3 | originally submitted by @sebastien1234
when trying to right click on highlighted text, nothing appears, should have the option to copy, CTRL-C works but most will not know to use that.
| 1.0 | right clicking after highlighting does not work - originally submitted by @sebastien1234
when trying to right click on highlighted text, nothing appears, should have the option to copy, CTRL-C works but most will not know to use that.
| test | right clicking after highlighting does not work originally submitted by when trying to right click on highlighted text nothing appears should have the option to copy ctrl c works but most will not know to use that | 1 |
2,210 | 7,809,001,983 | IssuesEvent | 2018-06-11 22:12:34 | react-navigation/react-navigation | https://api.github.com/repos/react-navigation/react-navigation | closed | navigation.goBack() to previous page is impossible if that page was on another stackNavigator | needs response from maintainer related: goBack | Update: added snack and example
### Your Environment
| software | version
| ---------------- | -------
| react-navigation | 2.0.x
| react-native | expo 27
| node | 9.11.1
| npm or yarn | yarn 1.7
```
tab:
stack1:
screen1,
detailScreen1
(default route screen1)
stack2:
screen2,
detailScreen2
(default route screen2)
```
so, for eg, from Screen1 i call
`navigation.navigate('detailScreen2')`
using on detailScreen2
` headerLeft: <GoBack onPress={() => navigation.goBack(null)} />`
move me to Screen2 instead of screen1 .
In fact, goBack call stack2 (who call screen2 as default screen for the stack).
How to fix this? Because if i call `navigation.navigate('screen1')`, the screen stack will be still full, so when i will press on stack2 tab icon, the new screen will be detailScreen2 instead of screen2 (because of the old opened screen on stack2)
Update:
[snack](https://snack.expo.io/ryuU43bg7)
Easy example made from navigation playground.
On home Tab go to Profile page, after go to notification, then go back.
The back will move you to the true parent (settings screen) instead to the previous page (profile screen).
| True | navigation.goBack() to previous page is impossible if that page was on another stackNavigator - Update: added snack and example
### Your Environment
| software | version
| ---------------- | -------
| react-navigation | 2.0.x
| react-native | expo 27
| node | 9.11.1
| npm or yarn | yarn 1.7
```
tab:
stack1:
screen1,
detailScreen1
(default route screen1)
stack2:
screen2,
detailScreen2
(default route screen2)
```
so, for eg, from Screen1 i call
`navigation.navigate('detailScreen2')`
using on detailScreen2
` headerLeft: <GoBack onPress={() => navigation.goBack(null)} />`
move me to Screen2 instead of screen1 .
In fact, goBack call stack2 (who call screen2 as default screen for the stack).
How to fix this? Because if i call `navigation.navigate('screen1')`, the screen stack will be still full, so when i will press on stack2 tab icon, the new screen will be detailScreen2 instead of screen2 (because of the old opened screen on stack2)
Update:
[snack](https://snack.expo.io/ryuU43bg7)
Easy example made from navigation playground.
On home Tab go to Profile page, after go to notification, then go back.
The back will move you to the true parent (settings screen) instead to the previous page (profile screen).
| non_test | navigation goback to previous page is impossible if that page was on another stacknavigator update added snack and example your environment software version react navigation x react native expo node npm or yarn yarn tab default route default route so for eg from i call navigation navigate using on headerleft navigation goback null move me to instead of in fact goback call who call as default screen for the stack how to fix this because if i call navigation navigate the screen stack will be still full so when i will press on tab icon the new screen will be instead of because of the old opened screen on update easy example made from navigation playground on home tab go to profile page after go to notification then go back the back will move you to the true parent settings screen instead to the previous page profile screen | 0 |
563,322 | 16,680,182,784 | IssuesEvent | 2021-06-07 22:05:39 | bounswe/2021SpringGroup10 | https://api.github.com/repos/bounswe/2021SpringGroup10 | closed | Adding Home Page for Practice App | Coding: Frontend Platform: Web Priority: High | Every team member has prepared a demo application to learn and practice about API logic with Flask. To stage every different app we need to have one main Home Page which performs a bridge utility. | 1.0 | Adding Home Page for Practice App - Every team member has prepared a demo application to learn and practice about API logic with Flask. To stage every different app we need to have one main Home Page which performs a bridge utility. | non_test | adding home page for practice app every team member has prepared a demo application to learn and practice about api logic with flask to stage every different app we need to have one main home page which performs a bridge utility | 0 |
244,595 | 20,678,691,369 | IssuesEvent | 2022-03-10 11:47:55 | woocommerce/woocommerce-gutenberg-products-block | https://api.github.com/repos/woocommerce/woocommerce-gutenberg-products-block | closed | Critical flows: Shopper → Cart → Can remove product | type: enhancement ◼️ block: cart category: tests | ### Story
As a shopper, I want to be able to remove a product, in case I accidentally added an unwanted product to the cart.
### File
`tests/e2e/specs/shopper/cart-products.test.js`
### Test
1. Go to the product page.
2. Add a product to the cart.
3. Go to the cart page.
4. Remove the product.
5. Verify that the cart is empty. | 1.0 | Critical flows: Shopper → Cart → Can remove product - ### Story
As a shopper, I want to be able to remove a product, in case I accidentally added an unwanted product to the cart.
### File
`tests/e2e/specs/shopper/cart-products.test.js`
### Test
1. Go to the product page.
2. Add a product to the cart.
3. Go to the cart page.
4. Remove the product.
5. Verify that the cart is empty. | test | critical flows shopper → cart → can remove product story as a shopper i want to be able to remove a product in case i accidentally added an unwanted product to the cart file tests specs shopper cart products test js test go to the product page add a product to the cart go to the cart page remove the product verify that the cart is empty | 1 |
257,304 | 27,563,701,036 | IssuesEvent | 2023-03-08 01:00:33 | mendts-workshop/josh202231080 | https://api.github.com/repos/mendts-workshop/josh202231080 | opened | forever-2.0.0.tgz: 18 vulnerabilities (highest severity is: 9.8) | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>forever-2.0.0.tgz</b></p></summary>
<p></p>
<p>Path to dependency file: /package.json</p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (forever version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2019-10747](https://www.mend.io/vulnerability-database/CVE-2019-10747) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | detected in multiple dependencies | Transitive | 3.0.0 | ✅ |
| [CVE-2019-10746](https://www.mend.io/vulnerability-database/CVE-2019-10746) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | mixin-deep-1.3.1.tgz | Transitive | 3.0.0 | ✅ |
| [CVE-2021-44906](https://www.mend.io/vulnerability-database/CVE-2021-44906) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | detected in multiple dependencies | Transitive | 3.0.0 | ✅ |
| [CVE-2020-7788](https://www.mend.io/vulnerability-database/CVE-2020-7788) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | ini-1.3.5.tgz | Transitive | 3.0.0 | ✅ |
| [CVE-2021-23440](https://www.mend.io/vulnerability-database/CVE-2021-23440) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | detected in multiple dependencies | Transitive | N/A* | ❌ |
| [CVE-2020-7774](https://www.mend.io/vulnerability-database/CVE-2020-7774) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | y18n-3.2.1.tgz | Transitive | 3.0.0 | ✅ |
| [CVE-2021-37701](https://www.mend.io/vulnerability-database/CVE-2021-37701) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.6 | tar-4.4.8.tgz | Transitive | 3.0.0 | ❌ |
| [CVE-2021-37712](https://www.mend.io/vulnerability-database/CVE-2021-37712) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.6 | tar-4.4.8.tgz | Transitive | 3.0.0 | ❌ |
| [CVE-2021-37713](https://www.mend.io/vulnerability-database/CVE-2021-37713) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.6 | tar-4.4.8.tgz | Transitive | 3.0.0 | ❌ |
| [CVE-2021-32804](https://www.mend.io/vulnerability-database/CVE-2021-32804) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.1 | tar-4.4.8.tgz | Transitive | 3.0.0 | ❌ |
| [CVE-2021-32803](https://www.mend.io/vulnerability-database/CVE-2021-32803) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.1 | tar-4.4.8.tgz | Transitive | 3.0.0 | ❌ |
| [CVE-2019-20149](https://www.mend.io/vulnerability-database/CVE-2019-20149) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | kind-of-6.0.2.tgz | Transitive | 3.0.0 | ✅ |
| [CVE-2020-28469](https://www.mend.io/vulnerability-database/CVE-2020-28469) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | glob-parent-3.1.0.tgz | Transitive | N/A* | ❌ |
| [WS-2018-0148](https://hackerone.com/reports/321701) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | detected in multiple dependencies | Transitive | N/A* | ❌ |
| [CVE-2022-3517](https://www.mend.io/vulnerability-database/CVE-2022-3517) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | minimatch-3.0.4.tgz | Transitive | N/A* | ❌ |
| [CVE-2022-21803](https://www.mend.io/vulnerability-database/CVE-2022-21803) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | detected in multiple dependencies | Transitive | 4.0.0 | ✅ |
| [CVE-2022-38900](https://www.mend.io/vulnerability-database/CVE-2022-38900) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | decode-uri-component-0.2.0.tgz | Transitive | 3.0.0 | ✅ |
| [CVE-2021-3820](https://www.mend.io/vulnerability-database/CVE-2021-3820) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | i-0.3.6.tgz | Transitive | 3.0.0 | ✅ |
<p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the section "Details" 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-2019-10747</summary>
### Vulnerable Libraries - <b>set-value-0.4.3.tgz</b>, <b>set-value-2.0.0.tgz</b></p>
<p>
### <b>set-value-0.4.3.tgz</b></p>
<p>Create nested values and any intermediaries using dot notation (`'a.b.c'`) paths.</p>
<p>Library home page: <a href="https://registry.npmjs.org/set-value/-/set-value-0.4.3.tgz">https://registry.npmjs.org/set-value/-/set-value-0.4.3.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/union-value/node_modules/set-value/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- cache-base-1.0.1.tgz
- union-value-1.0.0.tgz
- :x: **set-value-0.4.3.tgz** (Vulnerable Library)
### <b>set-value-2.0.0.tgz</b></p>
<p>Create nested values and any intermediaries using dot notation (`'a.b.c'`) paths.</p>
<p>Library home page: <a href="https://registry.npmjs.org/set-value/-/set-value-2.0.0.tgz">https://registry.npmjs.org/set-value/-/set-value-2.0.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/set-value/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- cache-base-1.0.1.tgz
- :x: **set-value-2.0.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
set-value is vulnerable to Prototype Pollution in versions lower than 3.0.1. The function mixin-deep could be tricked into adding or modifying properties of Object.prototype using any of the constructor, prototype and _proto_ payloads.
<p>Publish Date: 2019-08-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-10747>CVE-2019-10747</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>Release Date: 2019-10-29</p>
<p>Fix Resolution (set-value): 2.0.1</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p><p>Fix Resolution (set-value): 2.0.1</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-10746</summary>
### Vulnerable Library - <b>mixin-deep-1.3.1.tgz</b></p>
<p>Deeply mix the properties of objects into the first object. Like merge-deep, but doesn't clone.</p>
<p>Library home page: <a href="https://registry.npmjs.org/mixin-deep/-/mixin-deep-1.3.1.tgz">https://registry.npmjs.org/mixin-deep/-/mixin-deep-1.3.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/mixin-deep/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- :x: **mixin-deep-1.3.1.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
mixin-deep is vulnerable to Prototype Pollution in versions before 1.3.2 and version 2.0.0. The function mixin-deep could be tricked into adding or modifying properties of Object.prototype using a constructor payload.
<p>Publish Date: 2019-08-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-10746>CVE-2019-10746</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>Release Date: 2019-08-23</p>
<p>Fix Resolution (mixin-deep): 1.3.2</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-44906</summary>
### Vulnerable Libraries - <b>minimist-1.2.0.tgz</b>, <b>minimist-0.0.10.tgz</b>, <b>minimist-1.2.5.tgz</b>, <b>minimist-0.0.8.tgz</b></p>
<p>
### <b>minimist-1.2.0.tgz</b></p>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz">https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz</a></p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- rc-1.2.8.tgz
- :x: **minimist-1.2.0.tgz** (Vulnerable Library)
### <b>minimist-0.0.10.tgz</b></p>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- optimist-0.6.1.tgz
- :x: **minimist-0.0.10.tgz** (Vulnerable Library)
### <b>minimist-1.2.5.tgz</b></p>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz">https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/prettyjson/node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- prettyjson-1.2.1.tgz
- :x: **minimist-1.2.5.tgz** (Vulnerable Library)
### <b>minimist-0.0.8.tgz</b></p>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz</a></p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- mkdirp-0.5.1.tgz
- :x: **minimist-0.0.8.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).
<p>Publish Date: 2022-03-17
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-44906>CVE-2021-44906</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>Release Date: 2022-03-17</p>
<p>Fix Resolution (minimist): 1.2.6</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p><p>Fix Resolution (minimist): 1.2.6</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-7788</summary>
### Vulnerable Library - <b>ini-1.3.5.tgz</b></p>
<p>An ini encoder/decoder for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/ini/-/ini-1.3.5.tgz">https://registry.npmjs.org/ini/-/ini-1.3.5.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/ini/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- rc-1.2.8.tgz
- :x: **ini-1.3.5.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
This affects the package ini before 1.3.6. If an attacker submits a malicious INI file to an application that parses it with ini.parse, they will pollute the prototype on the application. This can be exploited further depending on the context.
<p>Publish Date: 2020-12-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-7788>CVE-2020-7788</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7788">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7788</a></p>
<p>Release Date: 2020-12-11</p>
<p>Fix Resolution (ini): 1.3.6</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-23440</summary>
### Vulnerable Libraries - <b>set-value-2.0.0.tgz</b>, <b>set-value-0.4.3.tgz</b></p>
<p>
### <b>set-value-2.0.0.tgz</b></p>
<p>Create nested values and any intermediaries using dot notation (`'a.b.c'`) paths.</p>
<p>Library home page: <a href="https://registry.npmjs.org/set-value/-/set-value-2.0.0.tgz">https://registry.npmjs.org/set-value/-/set-value-2.0.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/set-value/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- cache-base-1.0.1.tgz
- :x: **set-value-2.0.0.tgz** (Vulnerable Library)
### <b>set-value-0.4.3.tgz</b></p>
<p>Create nested values and any intermediaries using dot notation (`'a.b.c'`) paths.</p>
<p>Library home page: <a href="https://registry.npmjs.org/set-value/-/set-value-0.4.3.tgz">https://registry.npmjs.org/set-value/-/set-value-0.4.3.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/union-value/node_modules/set-value/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- cache-base-1.0.1.tgz
- union-value-1.0.0.tgz
- :x: **set-value-0.4.3.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
This affects the package set-value before <2.0.1, >=3.0.0 <4.0.1. A type confusion vulnerability can lead to a bypass of CVE-2019-10747 when the user-provided keys used in the path parameter are arrays.
Mend Note: After conducting further research, Mend has determined that all versions of set-value up to version 4.0.0 are vulnerable to CVE-2021-23440.
<p>Publish Date: 2021-09-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23440>CVE-2021-23440</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>Release Date: 2021-09-12</p>
<p>Fix Resolution: set-value - 4.0.1
</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-7774</summary>
### Vulnerable Library - <b>y18n-3.2.1.tgz</b></p>
<p>the bare-bones internationalization library used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/y18n/-/y18n-3.2.1.tgz">https://registry.npmjs.org/y18n/-/y18n-3.2.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/y18n/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- nconf-0.10.0.tgz
- yargs-3.32.0.tgz
- :x: **y18n-3.2.1.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The package y18n before 3.2.2, 4.0.1 and 5.0.5, is vulnerable to Prototype Pollution.
<p>Publish Date: 2020-11-17
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-7774>CVE-2020-7774</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://www.npmjs.com/advisories/1654">https://www.npmjs.com/advisories/1654</a></p>
<p>Release Date: 2020-11-17</p>
<p>Fix Resolution (y18n): 3.2.2</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-37701</summary>
### Vulnerable Library - <b>tar-4.4.8.tgz</b></p>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-4.4.8.tgz">https://registry.npmjs.org/tar/-/tar-4.4.8.tgz</a></p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- :x: **tar-4.4.8.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The npm package "tar" (aka node-tar) before versions 4.4.16, 5.0.8, and 6.1.7 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. 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 both a directory and a symlink with the same name as the directory, where the symlink and directory names in the archive entry used backslashes as a path separator on posix systems. The cache checking logic used both `\` and `/` characters as path separators, however `\` is a valid filename character on posix systems. By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass 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. Additionally, a similar confusion could arise on case-insensitive filesystems. If a tar archive contained a directory at `FOO`, followed by a symbolic link named `foo`, then on case-insensitive file systems, the creation of the symbolic link would remove the directory from the filesystem, but _not_ from the internal directory cache, as it would not be treated as a cache hit. A subsequent file entry within the `FOO` directory would then be placed in the target of the symbolic link, thinking that the directory had already been created. These issues were addressed in releases 4.4.16, 5.0.8 and 6.1.7. 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 in the referenced GHSA-9r2w-394v-53qc.
<p>Publish Date: 2021-08-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-37701>CVE-2021-37701</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.6</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/npm/node-tar/security/advisories/GHSA-9r2w-394v-53qc">https://github.com/npm/node-tar/security/advisories/GHSA-9r2w-394v-53qc</a></p>
<p>Release Date: 2021-08-31</p>
<p>Fix Resolution (tar): 4.4.16</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-37712</summary>
### Vulnerable Library - <b>tar-4.4.8.tgz</b></p>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-4.4.8.tgz">https://registry.npmjs.org/tar/-/tar-4.4.8.tgz</a></p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- :x: **tar-4.4.8.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The npm package "tar" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. 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 both a directory 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 a directory with one form of the path, followed by a symbolic link with a different string that resolves to the same file system entity, followed by a file using the first form. By first creating a directory, and then replacing that directory with a symlink that had a different apparent name that resolved to the same entry in the filesystem, it was thus possible to bypass 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. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. 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 in the referenced GHSA-qq89-hq3f-393p.
<p>Publish Date: 2021-08-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-37712>CVE-2021-37712</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.6</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/npm/node-tar/security/advisories/GHSA-qq89-hq3f-393p">https://github.com/npm/node-tar/security/advisories/GHSA-qq89-hq3f-393p</a></p>
<p>Release Date: 2021-08-31</p>
<p>Fix Resolution (tar): 4.4.18</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-37713</summary>
### Vulnerable Library - <b>tar-4.4.8.tgz</b></p>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-4.4.8.tgz">https://registry.npmjs.org/tar/-/tar-4.4.8.tgz</a></p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- :x: **tar-4.4.8.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The npm package "tar" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory. This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\path`. If the drive letter does not match the extraction target, for example `D:\extraction\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory. Additionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path. This only affects users of `node-tar` on Windows systems. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. 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. There is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does. Users are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.
<p>Publish Date: 2021-08-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-37713>CVE-2021-37713</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.6</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/npm/node-tar/security/advisories/GHSA-5955-9wpr-37jh">https://github.com/npm/node-tar/security/advisories/GHSA-5955-9wpr-37jh</a></p>
<p>Release Date: 2021-08-31</p>
<p>Fix Resolution (tar): 4.4.18</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-32804</summary>
### Vulnerable Library - <b>tar-4.4.8.tgz</b></p>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-4.4.8.tgz">https://registry.npmjs.org/tar/-/tar-4.4.8.tgz</a></p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- :x: **tar-4.4.8.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The npm package "tar" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.
<p>Publish Date: 2021-08-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-32804>CVE-2021-32804</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- 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/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9">https://github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9</a></p>
<p>Release Date: 2021-08-03</p>
<p>Fix Resolution (tar): 4.4.14</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-32803</summary>
### Vulnerable Library - <b>tar-4.4.8.tgz</b></p>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-4.4.8.tgz">https://registry.npmjs.org/tar/-/tar-4.4.8.tgz</a></p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- :x: **tar-4.4.8.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The npm package "tar" (aka node-tar) before versions 6.1.2, 5.0.7, 4.4.15, and 3.2.3 has an arbitrary File Creation/Overwrite vulnerability via insufficient symlink protection. `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 both a directory and a symlink with the same name as the directory. This order of operations resulted in the directory being created and added to the `node-tar` directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where `node-tar` checks for symlinks occur. By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass `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. This issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.
<p>Publish Date: 2021-08-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-32803>CVE-2021-32803</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- 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/npm/node-tar/security/advisories/GHSA-r628-mhmh-qjhw">https://github.com/npm/node-tar/security/advisories/GHSA-r628-mhmh-qjhw</a></p>
<p>Release Date: 2021-08-03</p>
<p>Fix Resolution (tar): 4.4.15</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-20149</summary>
### Vulnerable Library - <b>kind-of-6.0.2.tgz</b></p>
<p>Get the native type of a value.</p>
<p>Library home page: <a href="https://registry.npmjs.org/kind-of/-/kind-of-6.0.2.tgz">https://registry.npmjs.org/kind-of/-/kind-of-6.0.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/base/node_modules/kind-of/package.json,/node_modules/extglob/node_modules/kind-of/package.json,/node_modules/nanomatch/node_modules/kind-of/package.json,/node_modules/micromatch/node_modules/kind-of/package.json,/node_modules/snapdragon-node/node_modules/kind-of/package.json,/node_modules/define-property/node_modules/kind-of/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- readdirp-2.2.1.tgz
- micromatch-3.1.10.tgz
- :x: **kind-of-6.0.2.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
ctorName in index.js in kind-of v6.0.2 allows external user input to overwrite certain internal attributes via a conflicting name, as demonstrated by 'constructor': {'name':'Symbol'}. Hence, a crafted payload can overwrite this builtin attribute to manipulate the type detection result.
<p>Publish Date: 2019-12-30
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-20149>CVE-2019-20149</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: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20149">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20149</a></p>
<p>Release Date: 2019-12-30</p>
<p>Fix Resolution (kind-of): 6.0.3</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-28469</summary>
### Vulnerable Library - <b>glob-parent-3.1.0.tgz</b></p>
<p>Strips glob magic from a string to provide the parent directory path</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/glob-parent/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- :x: **glob-parent-3.1.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
This affects the package glob-parent before 5.1.2. The enclosure regex used to check for strings ending in enclosure containing path separator.
<p>Publish Date: 2021-06-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-28469>CVE-2020-28469</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28469">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28469</a></p>
<p>Release Date: 2021-06-03</p>
<p>Fix Resolution: glob-parent - 5.1.2</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2018-0148</summary>
### Vulnerable Libraries - <b>utile-0.3.0.tgz</b>, <b>utile-0.2.1.tgz</b></p>
<p>
### <b>utile-0.3.0.tgz</b></p>
<p>A drop-in replacement for `util` with some additional advantageous functions</p>
<p>Library home page: <a href="https://registry.npmjs.org/utile/-/utile-0.3.0.tgz">https://registry.npmjs.org/utile/-/utile-0.3.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/utile/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- :x: **utile-0.3.0.tgz** (Vulnerable Library)
### <b>utile-0.2.1.tgz</b></p>
<p>A drop-in replacement for `util` with some additional advantageous functions</p>
<p>Library home page: <a href="https://registry.npmjs.org/utile/-/utile-0.2.1.tgz">https://registry.npmjs.org/utile/-/utile-0.2.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/broadway/node_modules/utile/package.json,/node_modules/prompt/node_modules/utile/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- broadway-0.3.6.tgz
- :x: **utile-0.2.1.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The `utile` npm module, version 0.3.0, allows to extract sensitive data from uninitialized memory or to cause a DoS by passing in a large number, in setups where typed user input can be passed (e.g. from JSON).
<p>Publish Date: 2018-07-16
<p>URL: <a href=https://hackerone.com/reports/321701>WS-2018-0148</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://nvd.nist.gov/vuln/detail/WS-2018-0148">https://nvd.nist.gov/vuln/detail/WS-2018-0148</a></p>
<p>Release Date: 2018-01-16</p>
<p>Fix Resolution: JetBrains.Rider.Frontend5 - 213.0.20211008.154703-eap03</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-3517</summary>
### Vulnerable Library - <b>minimatch-3.0.4.tgz</b></p>
<p>a glob matcher in javascript</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimatch/-/minimatch-3.0.4.tgz">https://registry.npmjs.org/minimatch/-/minimatch-3.0.4.tgz</a></p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- :x: **minimatch-3.0.4.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A vulnerability was found in the minimatch package. This flaw allows a Regular Expression Denial of Service (ReDoS) when calling the braceExpand function with specific arguments, resulting in a Denial of Service.
<p>Publish Date: 2022-10-17
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-3517>CVE-2022-3517</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>Release Date: 2022-10-17</p>
<p>Fix Resolution: minimatch - 3.0.5</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-21803</summary>
### Vulnerable Libraries - <b>nconf-0.6.9.tgz</b>, <b>nconf-0.10.0.tgz</b></p>
<p>
### <b>nconf-0.6.9.tgz</b></p>
<p>Hierarchical node.js configuration with files, environment variables, command-line arguments, and atomic object merging.</p>
<p>Library home page: <a href="https://registry.npmjs.org/nconf/-/nconf-0.6.9.tgz">https://registry.npmjs.org/nconf/-/nconf-0.6.9.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/broadway/node_modules/nconf/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- broadway-0.3.6.tgz
- :x: **nconf-0.6.9.tgz** (Vulnerable Library)
### <b>nconf-0.10.0.tgz</b></p>
<p>Hierarchical node.js configuration with files, environment variables, command-line arguments, and atomic object merging.</p>
<p>Library home page: <a href="https://registry.npmjs.org/nconf/-/nconf-0.10.0.tgz">https://registry.npmjs.org/nconf/-/nconf-0.10.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/nconf/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- :x: **nconf-0.10.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
This affects the package nconf before 0.11.4. When using the memory engine, it is possible to store a nested JSON representation of the configuration. The .set() function, that is responsible for setting the configuration properties, is vulnerable to Prototype Pollution. By providing a crafted property, it is possible to modify the properties on the Object.prototype.
<p>Publish Date: 2022-04-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-21803>CVE-2022-21803</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: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21803">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21803</a></p>
<p>Release Date: 2022-04-12</p>
<p>Fix Resolution (nconf): 0.11.4</p>
<p>Direct dependency fix Resolution (forever): 4.0.0</p><p>Fix Resolution (nconf): 0.11.4</p>
<p>Direct dependency fix Resolution (forever): 4.0.0</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-38900</summary>
### Vulnerable Library - <b>decode-uri-component-0.2.0.tgz</b></p>
<p>A better decodeURIComponent</p>
<p>Library home page: <a href="https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz">https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/decode-uri-component/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- source-map-resolve-0.5.2.tgz
- :x: **decode-uri-component-0.2.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
decode-uri-component 0.2.0 is vulnerable to Improper Input Validation resulting in DoS.
<p>Publish Date: 2022-11-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-38900>CVE-2022-38900</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-w573-4hg7-7wgq">https://github.com/advisories/GHSA-w573-4hg7-7wgq</a></p>
<p>Release Date: 2022-11-28</p>
<p>Fix Resolution (decode-uri-component): 0.2.1</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-3820</summary>
### Vulnerable Library - <b>i-0.3.6.tgz</b></p>
<p>custom inflections for nodejs</p>
<p>Library home page: <a href="https://registry.npmjs.org/i/-/i-0.3.6.tgz">https://registry.npmjs.org/i/-/i-0.3.6.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/i/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- utile-0.3.0.tgz
- :x: **i-0.3.6.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
inflect is vulnerable to Inefficient Regular Expression Complexity
<p>Publish Date: 2021-09-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-3820>CVE-2021-3820</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3820">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3820</a></p>
<p>Release Date: 2021-09-27</p>
<p>Fix Resolution (i): 0.3.7</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details>
***
<p>In order to enable automatic remediation for this issue, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p> | True | forever-2.0.0.tgz: 18 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>forever-2.0.0.tgz</b></p></summary>
<p></p>
<p>Path to dependency file: /package.json</p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (forever version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2019-10747](https://www.mend.io/vulnerability-database/CVE-2019-10747) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | detected in multiple dependencies | Transitive | 3.0.0 | ✅ |
| [CVE-2019-10746](https://www.mend.io/vulnerability-database/CVE-2019-10746) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | mixin-deep-1.3.1.tgz | Transitive | 3.0.0 | ✅ |
| [CVE-2021-44906](https://www.mend.io/vulnerability-database/CVE-2021-44906) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | detected in multiple dependencies | Transitive | 3.0.0 | ✅ |
| [CVE-2020-7788](https://www.mend.io/vulnerability-database/CVE-2020-7788) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | ini-1.3.5.tgz | Transitive | 3.0.0 | ✅ |
| [CVE-2021-23440](https://www.mend.io/vulnerability-database/CVE-2021-23440) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | detected in multiple dependencies | Transitive | N/A* | ❌ |
| [CVE-2020-7774](https://www.mend.io/vulnerability-database/CVE-2020-7774) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | y18n-3.2.1.tgz | Transitive | 3.0.0 | ✅ |
| [CVE-2021-37701](https://www.mend.io/vulnerability-database/CVE-2021-37701) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.6 | tar-4.4.8.tgz | Transitive | 3.0.0 | ❌ |
| [CVE-2021-37712](https://www.mend.io/vulnerability-database/CVE-2021-37712) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.6 | tar-4.4.8.tgz | Transitive | 3.0.0 | ❌ |
| [CVE-2021-37713](https://www.mend.io/vulnerability-database/CVE-2021-37713) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.6 | tar-4.4.8.tgz | Transitive | 3.0.0 | ❌ |
| [CVE-2021-32804](https://www.mend.io/vulnerability-database/CVE-2021-32804) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.1 | tar-4.4.8.tgz | Transitive | 3.0.0 | ❌ |
| [CVE-2021-32803](https://www.mend.io/vulnerability-database/CVE-2021-32803) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.1 | tar-4.4.8.tgz | Transitive | 3.0.0 | ❌ |
| [CVE-2019-20149](https://www.mend.io/vulnerability-database/CVE-2019-20149) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | kind-of-6.0.2.tgz | Transitive | 3.0.0 | ✅ |
| [CVE-2020-28469](https://www.mend.io/vulnerability-database/CVE-2020-28469) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | glob-parent-3.1.0.tgz | Transitive | N/A* | ❌ |
| [WS-2018-0148](https://hackerone.com/reports/321701) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | detected in multiple dependencies | Transitive | N/A* | ❌ |
| [CVE-2022-3517](https://www.mend.io/vulnerability-database/CVE-2022-3517) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | minimatch-3.0.4.tgz | Transitive | N/A* | ❌ |
| [CVE-2022-21803](https://www.mend.io/vulnerability-database/CVE-2022-21803) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | detected in multiple dependencies | Transitive | 4.0.0 | ✅ |
| [CVE-2022-38900](https://www.mend.io/vulnerability-database/CVE-2022-38900) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | decode-uri-component-0.2.0.tgz | Transitive | 3.0.0 | ✅ |
| [CVE-2021-3820](https://www.mend.io/vulnerability-database/CVE-2021-3820) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | i-0.3.6.tgz | Transitive | 3.0.0 | ✅ |
<p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the section "Details" 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-2019-10747</summary>
### Vulnerable Libraries - <b>set-value-0.4.3.tgz</b>, <b>set-value-2.0.0.tgz</b></p>
<p>
### <b>set-value-0.4.3.tgz</b></p>
<p>Create nested values and any intermediaries using dot notation (`'a.b.c'`) paths.</p>
<p>Library home page: <a href="https://registry.npmjs.org/set-value/-/set-value-0.4.3.tgz">https://registry.npmjs.org/set-value/-/set-value-0.4.3.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/union-value/node_modules/set-value/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- cache-base-1.0.1.tgz
- union-value-1.0.0.tgz
- :x: **set-value-0.4.3.tgz** (Vulnerable Library)
### <b>set-value-2.0.0.tgz</b></p>
<p>Create nested values and any intermediaries using dot notation (`'a.b.c'`) paths.</p>
<p>Library home page: <a href="https://registry.npmjs.org/set-value/-/set-value-2.0.0.tgz">https://registry.npmjs.org/set-value/-/set-value-2.0.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/set-value/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- cache-base-1.0.1.tgz
- :x: **set-value-2.0.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
set-value is vulnerable to Prototype Pollution in versions lower than 3.0.1. The function mixin-deep could be tricked into adding or modifying properties of Object.prototype using any of the constructor, prototype and _proto_ payloads.
<p>Publish Date: 2019-08-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-10747>CVE-2019-10747</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>Release Date: 2019-10-29</p>
<p>Fix Resolution (set-value): 2.0.1</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p><p>Fix Resolution (set-value): 2.0.1</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-10746</summary>
### Vulnerable Library - <b>mixin-deep-1.3.1.tgz</b></p>
<p>Deeply mix the properties of objects into the first object. Like merge-deep, but doesn't clone.</p>
<p>Library home page: <a href="https://registry.npmjs.org/mixin-deep/-/mixin-deep-1.3.1.tgz">https://registry.npmjs.org/mixin-deep/-/mixin-deep-1.3.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/mixin-deep/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- :x: **mixin-deep-1.3.1.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
mixin-deep is vulnerable to Prototype Pollution in versions before 1.3.2 and version 2.0.0. The function mixin-deep could be tricked into adding or modifying properties of Object.prototype using a constructor payload.
<p>Publish Date: 2019-08-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-10746>CVE-2019-10746</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>Release Date: 2019-08-23</p>
<p>Fix Resolution (mixin-deep): 1.3.2</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-44906</summary>
### Vulnerable Libraries - <b>minimist-1.2.0.tgz</b>, <b>minimist-0.0.10.tgz</b>, <b>minimist-1.2.5.tgz</b>, <b>minimist-0.0.8.tgz</b></p>
<p>
### <b>minimist-1.2.0.tgz</b></p>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz">https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz</a></p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- rc-1.2.8.tgz
- :x: **minimist-1.2.0.tgz** (Vulnerable Library)
### <b>minimist-0.0.10.tgz</b></p>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- optimist-0.6.1.tgz
- :x: **minimist-0.0.10.tgz** (Vulnerable Library)
### <b>minimist-1.2.5.tgz</b></p>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz">https://registry.npmjs.org/minimist/-/minimist-1.2.5.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/prettyjson/node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- prettyjson-1.2.1.tgz
- :x: **minimist-1.2.5.tgz** (Vulnerable Library)
### <b>minimist-0.0.8.tgz</b></p>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz</a></p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- mkdirp-0.5.1.tgz
- :x: **minimist-0.0.8.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).
<p>Publish Date: 2022-03-17
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-44906>CVE-2021-44906</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>Release Date: 2022-03-17</p>
<p>Fix Resolution (minimist): 1.2.6</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p><p>Fix Resolution (minimist): 1.2.6</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-7788</summary>
### Vulnerable Library - <b>ini-1.3.5.tgz</b></p>
<p>An ini encoder/decoder for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/ini/-/ini-1.3.5.tgz">https://registry.npmjs.org/ini/-/ini-1.3.5.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/ini/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- rc-1.2.8.tgz
- :x: **ini-1.3.5.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
This affects the package ini before 1.3.6. If an attacker submits a malicious INI file to an application that parses it with ini.parse, they will pollute the prototype on the application. This can be exploited further depending on the context.
<p>Publish Date: 2020-12-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-7788>CVE-2020-7788</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7788">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7788</a></p>
<p>Release Date: 2020-12-11</p>
<p>Fix Resolution (ini): 1.3.6</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-23440</summary>
### Vulnerable Libraries - <b>set-value-2.0.0.tgz</b>, <b>set-value-0.4.3.tgz</b></p>
<p>
### <b>set-value-2.0.0.tgz</b></p>
<p>Create nested values and any intermediaries using dot notation (`'a.b.c'`) paths.</p>
<p>Library home page: <a href="https://registry.npmjs.org/set-value/-/set-value-2.0.0.tgz">https://registry.npmjs.org/set-value/-/set-value-2.0.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/set-value/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- cache-base-1.0.1.tgz
- :x: **set-value-2.0.0.tgz** (Vulnerable Library)
### <b>set-value-0.4.3.tgz</b></p>
<p>Create nested values and any intermediaries using dot notation (`'a.b.c'`) paths.</p>
<p>Library home page: <a href="https://registry.npmjs.org/set-value/-/set-value-0.4.3.tgz">https://registry.npmjs.org/set-value/-/set-value-0.4.3.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/union-value/node_modules/set-value/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- cache-base-1.0.1.tgz
- union-value-1.0.0.tgz
- :x: **set-value-0.4.3.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
This affects the package set-value before <2.0.1, >=3.0.0 <4.0.1. A type confusion vulnerability can lead to a bypass of CVE-2019-10747 when the user-provided keys used in the path parameter are arrays.
Mend Note: After conducting further research, Mend has determined that all versions of set-value up to version 4.0.0 are vulnerable to CVE-2021-23440.
<p>Publish Date: 2021-09-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23440>CVE-2021-23440</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>Release Date: 2021-09-12</p>
<p>Fix Resolution: set-value - 4.0.1
</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-7774</summary>
### Vulnerable Library - <b>y18n-3.2.1.tgz</b></p>
<p>the bare-bones internationalization library used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/y18n/-/y18n-3.2.1.tgz">https://registry.npmjs.org/y18n/-/y18n-3.2.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/y18n/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- nconf-0.10.0.tgz
- yargs-3.32.0.tgz
- :x: **y18n-3.2.1.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The package y18n before 3.2.2, 4.0.1 and 5.0.5, is vulnerable to Prototype Pollution.
<p>Publish Date: 2020-11-17
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-7774>CVE-2020-7774</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://www.npmjs.com/advisories/1654">https://www.npmjs.com/advisories/1654</a></p>
<p>Release Date: 2020-11-17</p>
<p>Fix Resolution (y18n): 3.2.2</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-37701</summary>
### Vulnerable Library - <b>tar-4.4.8.tgz</b></p>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-4.4.8.tgz">https://registry.npmjs.org/tar/-/tar-4.4.8.tgz</a></p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- :x: **tar-4.4.8.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The npm package "tar" (aka node-tar) before versions 4.4.16, 5.0.8, and 6.1.7 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. 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 both a directory and a symlink with the same name as the directory, where the symlink and directory names in the archive entry used backslashes as a path separator on posix systems. The cache checking logic used both `\` and `/` characters as path separators, however `\` is a valid filename character on posix systems. By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass 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. Additionally, a similar confusion could arise on case-insensitive filesystems. If a tar archive contained a directory at `FOO`, followed by a symbolic link named `foo`, then on case-insensitive file systems, the creation of the symbolic link would remove the directory from the filesystem, but _not_ from the internal directory cache, as it would not be treated as a cache hit. A subsequent file entry within the `FOO` directory would then be placed in the target of the symbolic link, thinking that the directory had already been created. These issues were addressed in releases 4.4.16, 5.0.8 and 6.1.7. 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 in the referenced GHSA-9r2w-394v-53qc.
<p>Publish Date: 2021-08-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-37701>CVE-2021-37701</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.6</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/npm/node-tar/security/advisories/GHSA-9r2w-394v-53qc">https://github.com/npm/node-tar/security/advisories/GHSA-9r2w-394v-53qc</a></p>
<p>Release Date: 2021-08-31</p>
<p>Fix Resolution (tar): 4.4.16</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-37712</summary>
### Vulnerable Library - <b>tar-4.4.8.tgz</b></p>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-4.4.8.tgz">https://registry.npmjs.org/tar/-/tar-4.4.8.tgz</a></p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- :x: **tar-4.4.8.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The npm package "tar" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. 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 both a directory 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 a directory with one form of the path, followed by a symbolic link with a different string that resolves to the same file system entity, followed by a file using the first form. By first creating a directory, and then replacing that directory with a symlink that had a different apparent name that resolved to the same entry in the filesystem, it was thus possible to bypass 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. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. 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 in the referenced GHSA-qq89-hq3f-393p.
<p>Publish Date: 2021-08-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-37712>CVE-2021-37712</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.6</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/npm/node-tar/security/advisories/GHSA-qq89-hq3f-393p">https://github.com/npm/node-tar/security/advisories/GHSA-qq89-hq3f-393p</a></p>
<p>Release Date: 2021-08-31</p>
<p>Fix Resolution (tar): 4.4.18</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-37713</summary>
### Vulnerable Library - <b>tar-4.4.8.tgz</b></p>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-4.4.8.tgz">https://registry.npmjs.org/tar/-/tar-4.4.8.tgz</a></p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- :x: **tar-4.4.8.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The npm package "tar" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory. This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\path`. If the drive letter does not match the extraction target, for example `D:\extraction\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory. Additionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path. This only affects users of `node-tar` on Windows systems. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. 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. There is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does. Users are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.
<p>Publish Date: 2021-08-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-37713>CVE-2021-37713</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.6</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/npm/node-tar/security/advisories/GHSA-5955-9wpr-37jh">https://github.com/npm/node-tar/security/advisories/GHSA-5955-9wpr-37jh</a></p>
<p>Release Date: 2021-08-31</p>
<p>Fix Resolution (tar): 4.4.18</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-32804</summary>
### Vulnerable Library - <b>tar-4.4.8.tgz</b></p>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-4.4.8.tgz">https://registry.npmjs.org/tar/-/tar-4.4.8.tgz</a></p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- :x: **tar-4.4.8.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The npm package "tar" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.
<p>Publish Date: 2021-08-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-32804>CVE-2021-32804</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- 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/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9">https://github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9</a></p>
<p>Release Date: 2021-08-03</p>
<p>Fix Resolution (tar): 4.4.14</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-32803</summary>
### Vulnerable Library - <b>tar-4.4.8.tgz</b></p>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-4.4.8.tgz">https://registry.npmjs.org/tar/-/tar-4.4.8.tgz</a></p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- fsevents-1.2.9.tgz
- node-pre-gyp-0.12.0.tgz
- :x: **tar-4.4.8.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The npm package "tar" (aka node-tar) before versions 6.1.2, 5.0.7, 4.4.15, and 3.2.3 has an arbitrary File Creation/Overwrite vulnerability via insufficient symlink protection. `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 both a directory and a symlink with the same name as the directory. This order of operations resulted in the directory being created and added to the `node-tar` directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where `node-tar` checks for symlinks occur. By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass `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. This issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.
<p>Publish Date: 2021-08-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-32803>CVE-2021-32803</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- 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/npm/node-tar/security/advisories/GHSA-r628-mhmh-qjhw">https://github.com/npm/node-tar/security/advisories/GHSA-r628-mhmh-qjhw</a></p>
<p>Release Date: 2021-08-03</p>
<p>Fix Resolution (tar): 4.4.15</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-20149</summary>
### Vulnerable Library - <b>kind-of-6.0.2.tgz</b></p>
<p>Get the native type of a value.</p>
<p>Library home page: <a href="https://registry.npmjs.org/kind-of/-/kind-of-6.0.2.tgz">https://registry.npmjs.org/kind-of/-/kind-of-6.0.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/base/node_modules/kind-of/package.json,/node_modules/extglob/node_modules/kind-of/package.json,/node_modules/nanomatch/node_modules/kind-of/package.json,/node_modules/micromatch/node_modules/kind-of/package.json,/node_modules/snapdragon-node/node_modules/kind-of/package.json,/node_modules/define-property/node_modules/kind-of/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- readdirp-2.2.1.tgz
- micromatch-3.1.10.tgz
- :x: **kind-of-6.0.2.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
ctorName in index.js in kind-of v6.0.2 allows external user input to overwrite certain internal attributes via a conflicting name, as demonstrated by 'constructor': {'name':'Symbol'}. Hence, a crafted payload can overwrite this builtin attribute to manipulate the type detection result.
<p>Publish Date: 2019-12-30
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-20149>CVE-2019-20149</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: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20149">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20149</a></p>
<p>Release Date: 2019-12-30</p>
<p>Fix Resolution (kind-of): 6.0.3</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-28469</summary>
### Vulnerable Library - <b>glob-parent-3.1.0.tgz</b></p>
<p>Strips glob magic from a string to provide the parent directory path</p>
<p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/glob-parent/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- :x: **glob-parent-3.1.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
This affects the package glob-parent before 5.1.2. The enclosure regex used to check for strings ending in enclosure containing path separator.
<p>Publish Date: 2021-06-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-28469>CVE-2020-28469</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28469">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28469</a></p>
<p>Release Date: 2021-06-03</p>
<p>Fix Resolution: glob-parent - 5.1.2</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2018-0148</summary>
### Vulnerable Libraries - <b>utile-0.3.0.tgz</b>, <b>utile-0.2.1.tgz</b></p>
<p>
### <b>utile-0.3.0.tgz</b></p>
<p>A drop-in replacement for `util` with some additional advantageous functions</p>
<p>Library home page: <a href="https://registry.npmjs.org/utile/-/utile-0.3.0.tgz">https://registry.npmjs.org/utile/-/utile-0.3.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/utile/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- :x: **utile-0.3.0.tgz** (Vulnerable Library)
### <b>utile-0.2.1.tgz</b></p>
<p>A drop-in replacement for `util` with some additional advantageous functions</p>
<p>Library home page: <a href="https://registry.npmjs.org/utile/-/utile-0.2.1.tgz">https://registry.npmjs.org/utile/-/utile-0.2.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/broadway/node_modules/utile/package.json,/node_modules/prompt/node_modules/utile/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- broadway-0.3.6.tgz
- :x: **utile-0.2.1.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The `utile` npm module, version 0.3.0, allows to extract sensitive data from uninitialized memory or to cause a DoS by passing in a large number, in setups where typed user input can be passed (e.g. from JSON).
<p>Publish Date: 2018-07-16
<p>URL: <a href=https://hackerone.com/reports/321701>WS-2018-0148</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://nvd.nist.gov/vuln/detail/WS-2018-0148">https://nvd.nist.gov/vuln/detail/WS-2018-0148</a></p>
<p>Release Date: 2018-01-16</p>
<p>Fix Resolution: JetBrains.Rider.Frontend5 - 213.0.20211008.154703-eap03</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-3517</summary>
### Vulnerable Library - <b>minimatch-3.0.4.tgz</b></p>
<p>a glob matcher in javascript</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimatch/-/minimatch-3.0.4.tgz">https://registry.npmjs.org/minimatch/-/minimatch-3.0.4.tgz</a></p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- :x: **minimatch-3.0.4.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A vulnerability was found in the minimatch package. This flaw allows a Regular Expression Denial of Service (ReDoS) when calling the braceExpand function with specific arguments, resulting in a Denial of Service.
<p>Publish Date: 2022-10-17
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-3517>CVE-2022-3517</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>Release Date: 2022-10-17</p>
<p>Fix Resolution: minimatch - 3.0.5</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-21803</summary>
### Vulnerable Libraries - <b>nconf-0.6.9.tgz</b>, <b>nconf-0.10.0.tgz</b></p>
<p>
### <b>nconf-0.6.9.tgz</b></p>
<p>Hierarchical node.js configuration with files, environment variables, command-line arguments, and atomic object merging.</p>
<p>Library home page: <a href="https://registry.npmjs.org/nconf/-/nconf-0.6.9.tgz">https://registry.npmjs.org/nconf/-/nconf-0.6.9.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/broadway/node_modules/nconf/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- broadway-0.3.6.tgz
- :x: **nconf-0.6.9.tgz** (Vulnerable Library)
### <b>nconf-0.10.0.tgz</b></p>
<p>Hierarchical node.js configuration with files, environment variables, command-line arguments, and atomic object merging.</p>
<p>Library home page: <a href="https://registry.npmjs.org/nconf/-/nconf-0.10.0.tgz">https://registry.npmjs.org/nconf/-/nconf-0.10.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/nconf/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- :x: **nconf-0.10.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
This affects the package nconf before 0.11.4. When using the memory engine, it is possible to store a nested JSON representation of the configuration. The .set() function, that is responsible for setting the configuration properties, is vulnerable to Prototype Pollution. By providing a crafted property, it is possible to modify the properties on the Object.prototype.
<p>Publish Date: 2022-04-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-21803>CVE-2022-21803</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: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21803">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21803</a></p>
<p>Release Date: 2022-04-12</p>
<p>Fix Resolution (nconf): 0.11.4</p>
<p>Direct dependency fix Resolution (forever): 4.0.0</p><p>Fix Resolution (nconf): 0.11.4</p>
<p>Direct dependency fix Resolution (forever): 4.0.0</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-38900</summary>
### Vulnerable Library - <b>decode-uri-component-0.2.0.tgz</b></p>
<p>A better decodeURIComponent</p>
<p>Library home page: <a href="https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz">https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/decode-uri-component/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- forever-monitor-2.0.0.tgz
- chokidar-2.1.8.tgz
- braces-2.3.2.tgz
- snapdragon-0.8.2.tgz
- source-map-resolve-0.5.2.tgz
- :x: **decode-uri-component-0.2.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
decode-uri-component 0.2.0 is vulnerable to Improper Input Validation resulting in DoS.
<p>Publish Date: 2022-11-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-38900>CVE-2022-38900</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-w573-4hg7-7wgq">https://github.com/advisories/GHSA-w573-4hg7-7wgq</a></p>
<p>Release Date: 2022-11-28</p>
<p>Fix Resolution (decode-uri-component): 0.2.1</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-3820</summary>
### Vulnerable Library - <b>i-0.3.6.tgz</b></p>
<p>custom inflections for nodejs</p>
<p>Library home page: <a href="https://registry.npmjs.org/i/-/i-0.3.6.tgz">https://registry.npmjs.org/i/-/i-0.3.6.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/i/package.json</p>
<p>
Dependency Hierarchy:
- forever-2.0.0.tgz (Root Library)
- utile-0.3.0.tgz
- :x: **i-0.3.6.tgz** (Vulnerable Library)
<p>Found in base branch: <b>nodegoat</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
inflect is vulnerable to Inefficient Regular Expression Complexity
<p>Publish Date: 2021-09-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-3820>CVE-2021-3820</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3820">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3820</a></p>
<p>Release Date: 2021-09-27</p>
<p>Fix Resolution (i): 0.3.7</p>
<p>Direct dependency fix Resolution (forever): 3.0.0</p>
</p>
<p></p>
<p>In order to enable automatic remediation, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p>
</details>
***
<p>In order to enable automatic remediation for this issue, please create <a target="_blank" href="https://docs.mend.io/bundle/integrations/page/mend_for_github_com.html#MendforGitHub.com-RemediateSettings(remediateSettings)">workflow rules</a></p> | non_test | forever tgz vulnerabilities highest severity is vulnerable library forever tgz path to dependency file package json vulnerabilities cve severity cvss dependency type fixed in forever version remediation available high detected in multiple dependencies transitive high mixin deep tgz transitive high detected in multiple dependencies transitive high ini tgz transitive high detected in multiple dependencies transitive n a high tgz transitive high tar tgz transitive high tar tgz transitive high tar tgz transitive high tar tgz transitive high tar tgz transitive high kind of tgz transitive high glob parent tgz transitive n a high detected in multiple dependencies transitive n a high minimatch tgz transitive n a high detected in multiple dependencies transitive high decode uri component tgz transitive high i tgz transitive for some transitive vulnerabilities there is no version of direct dependency with a fix check the section details below to see if there is a version of transitive dependency where vulnerability is fixed details cve vulnerable libraries set value tgz set value tgz set value tgz create nested values and any intermediaries using dot notation a b c paths library home page a href path to dependency file package json path to vulnerable library node modules union value node modules set value package json dependency hierarchy forever tgz root library forever monitor tgz chokidar tgz braces tgz snapdragon tgz base tgz cache base tgz union value tgz x set value tgz vulnerable library set value tgz create nested values and any intermediaries using dot notation a b c paths library home page a href path to dependency file package json path to vulnerable library node modules set value package json dependency hierarchy forever tgz root library forever monitor tgz chokidar tgz braces tgz snapdragon tgz base tgz cache base tgz x set value tgz vulnerable library found in base branch nodegoat vulnerability details set value is vulnerable to prototype pollution in versions lower than the function mixin deep could be tricked into adding or modifying properties of object prototype using any of the constructor prototype and proto payloads 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 release date fix resolution set value direct dependency fix resolution forever fix resolution set value direct dependency fix resolution forever in order to enable automatic remediation please create cve vulnerable library mixin deep tgz deeply mix the properties of objects into the first object like merge deep but doesn t clone library home page a href path to dependency file package json path to vulnerable library node modules mixin deep package json dependency hierarchy forever tgz root library forever monitor tgz chokidar tgz braces tgz snapdragon tgz base tgz x mixin deep tgz vulnerable library found in base branch nodegoat vulnerability details mixin deep is vulnerable to prototype pollution in versions before and version the function mixin deep could be tricked into adding or modifying properties of object prototype using a constructor payload 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 release date fix resolution mixin deep direct dependency fix resolution forever in order to enable automatic remediation please create cve vulnerable libraries minimist tgz minimist tgz minimist tgz minimist tgz minimist tgz parse argument options library home page a href dependency hierarchy forever tgz root library forever monitor tgz chokidar tgz fsevents tgz node pre gyp tgz rc tgz x minimist tgz vulnerable library minimist tgz parse argument options library home page a href path to dependency file package json path to vulnerable library node modules minimist package json dependency hierarchy forever tgz root library optimist tgz x minimist tgz vulnerable library minimist tgz parse argument options library home page a href path to dependency file package json path to vulnerable library node modules prettyjson node modules minimist package json dependency hierarchy forever tgz root library prettyjson tgz x minimist tgz vulnerable library minimist tgz parse argument options library home page a href dependency hierarchy forever tgz root library forever monitor tgz chokidar tgz fsevents tgz node pre gyp tgz mkdirp tgz x minimist tgz vulnerable library found in base branch nodegoat vulnerability details minimist is vulnerable to prototype pollution via file index js function setkey lines 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 release date fix resolution minimist direct dependency fix resolution forever fix resolution minimist direct dependency fix resolution forever in order to enable automatic remediation please create cve vulnerable library ini tgz an ini encoder decoder for node library home page a href path to dependency file package json path to vulnerable library node modules ini package json dependency hierarchy forever tgz root library forever monitor tgz chokidar tgz fsevents tgz node pre gyp tgz rc tgz x ini tgz vulnerable library found in base branch nodegoat vulnerability details this affects the package ini before if an attacker submits a malicious ini file to an application that parses it with ini parse they will pollute the prototype on the application this can be exploited further depending on the context 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 ini direct dependency fix resolution forever in order to enable automatic remediation please create cve vulnerable libraries set value tgz set value tgz set value tgz create nested values and any intermediaries using dot notation a b c paths library home page a href path to dependency file package json path to vulnerable library node modules set value package json dependency hierarchy forever tgz root library forever monitor tgz chokidar tgz braces tgz snapdragon tgz base tgz cache base tgz x set value tgz vulnerable library set value tgz create nested values and any intermediaries using dot notation a b c paths library home page a href path to dependency file package json path to vulnerable library node modules union value node modules set value package json dependency hierarchy forever tgz root library forever monitor tgz chokidar tgz braces tgz snapdragon tgz base tgz cache base tgz union value tgz x set value tgz vulnerable library found in base branch nodegoat vulnerability details this affects the package set value before a type confusion vulnerability can lead to a bypass of cve when the user provided keys used in the path parameter are arrays mend note after conducting further research mend has determined that all versions of set value up to version are vulnerable to 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 high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version release date fix resolution set value cve vulnerable library tgz the bare bones internationalization library used by yargs library home page a href path to dependency file package json path to vulnerable library node modules package json dependency hierarchy forever tgz root library nconf tgz yargs tgz x tgz vulnerable library found in base branch nodegoat vulnerability details the package before and is vulnerable to prototype pollution 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 direct dependency fix resolution forever in order to enable automatic remediation please create cve vulnerable library tar tgz tar for node library home page a href dependency hierarchy forever tgz root library forever monitor tgz chokidar tgz fsevents tgz node pre gyp tgz x tar tgz vulnerable library found in base branch nodegoat vulnerability details the npm package tar aka node tar before versions and has an arbitrary file creation overwrite and arbitrary code execution vulnerability 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 both a directory and a symlink with the same name as the directory where the symlink and directory names in the archive entry used backslashes as a path separator on posix systems the cache checking logic used both and characters as path separators however is a valid filename character on posix systems by first creating a directory and then replacing that directory with a symlink it was thus possible to bypass 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 additionally a similar confusion could arise on case insensitive filesystems if a tar archive contained a directory at foo followed by a symbolic link named foo then on case insensitive file systems the creation of the symbolic link would remove the directory from the filesystem but not from the internal directory cache as it would not be treated as a cache hit a subsequent file entry within the foo directory would then be placed in the target of the symbolic link thinking that the directory had already been created these issues were addressed in releases and 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 in the referenced ghsa publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution tar direct dependency fix resolution forever cve vulnerable library tar tgz tar for node library home page a href dependency hierarchy forever tgz root library forever monitor tgz chokidar tgz fsevents tgz node pre gyp tgz x tar tgz vulnerable library found in base branch nodegoat vulnerability details the npm package tar aka node tar before versions and has an arbitrary file creation overwrite and arbitrary code execution vulnerability 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 both a directory 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 a directory with one form of the path followed by a symbolic link with a different string that resolves to the same file system entity followed by a file using the first form by first creating a directory and then replacing that directory with a symlink that had a different apparent name that resolved to the same entry in the filesystem it was thus possible to bypass 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 these issues were addressed in releases and 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 in the referenced ghsa publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution tar direct dependency fix resolution forever cve vulnerable library tar tgz tar for node library home page a href dependency hierarchy forever tgz root library forever monitor tgz chokidar tgz fsevents tgz node pre gyp tgz x tar tgz vulnerable library found in base branch nodegoat vulnerability details the npm package tar aka node tar before versions and has an arbitrary file creation overwrite and arbitrary code execution vulnerability node tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted this is in part accomplished by sanitizing absolute paths of entries within the archive skipping archive entries that contain path portions and resolving the sanitized paths against the extraction target directory this logic was insufficient on windows systems when extracting tar files that contained a path that was not an absolute path but specified a drive letter different from the extraction target such as c some path if the drive letter does not match the extraction target for example d extraction dir then the result of path resolve extractiondirectory entrypath would resolve against the current working directory on the c drive rather than the extraction target directory additionally a portion of the path could occur immediately after the drive letter such as c foo and was not properly sanitized by the logic that checked for within the normalized and split portions of the path this only affects users of node tar on windows systems these issues were addressed in releases and 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 there is no reasonable way to work around this issue without performing the same path normalization procedures that node tar now does users are encouraged to upgrade to the latest patched versions of node tar rather than attempt to sanitize paths themselves publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution tar direct dependency fix resolution forever cve vulnerable library tar tgz tar for node library home page a href dependency hierarchy forever tgz root library forever monitor tgz chokidar tgz fsevents tgz node pre gyp tgz x tar tgz vulnerable library found in base branch nodegoat vulnerability details the npm package tar aka node tar before versions and has a arbitrary file creation overwrite vulnerability due to insufficient absolute path sanitization node tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the preservepaths flag is not set to true this is achieved by stripping the absolute path root from any absolute file paths contained in a tar file for example home user bashrc would turn into home user bashrc this logic was insufficient when file paths contained repeated path roots such as home user bashrc node tar would only strip a single path root from such paths when given an absolute file path with repeating path roots the resulting path e g home user bashrc would still resolve to an absolute path thus allowing arbitrary file creation and overwrite this issue was addressed in releases and users may work around this vulnerability without upgrading by creating a custom onentry method which sanitizes the entry path or a filter method which removes entries with absolute paths see referenced github advisory for details be aware of cve which fixes a similar bug in later versions of tar 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 unchanged impact metrics confidentiality impact none 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 tar direct dependency fix resolution forever cve vulnerable library tar tgz tar for node library home page a href dependency hierarchy forever tgz root library forever monitor tgz chokidar tgz fsevents tgz node pre gyp tgz x tar tgz vulnerable library found in base branch nodegoat vulnerability details the npm package tar aka node tar before versions and has an arbitrary file creation overwrite vulnerability via insufficient symlink protection 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 both a directory and a symlink with the same name as the directory this order of operations resulted in the directory being created and added to the node tar directory cache when a directory is present in the directory cache subsequent calls to mkdir for that directory are skipped however this is also where node tar checks for symlinks occur by first creating a directory and then replacing that directory with a symlink it was thus possible to bypass 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 this issue was addressed in releases and 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 unchanged impact metrics confidentiality impact none 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 tar direct dependency fix resolution forever cve vulnerable library kind of tgz get the native type of a value library home page a href path to dependency file package json path to vulnerable library node modules base node modules kind of package json node modules extglob node modules kind of package json node modules nanomatch node modules kind of package json node modules micromatch node modules kind of package json node modules snapdragon node node modules kind of package json node modules define property node modules kind of package json dependency hierarchy forever tgz root library forever monitor tgz chokidar tgz readdirp tgz micromatch tgz x kind of tgz vulnerable library found in base branch nodegoat vulnerability details ctorname in index js in kind of allows external user input to overwrite certain internal attributes via a conflicting name as demonstrated by constructor name symbol hence a crafted payload can overwrite this builtin attribute to manipulate the type detection result 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 high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution kind of direct dependency fix resolution forever in order to enable automatic remediation please create cve vulnerable library glob parent tgz strips glob magic from a string to provide the parent directory path library home page a href path to dependency file package json path to vulnerable library node modules glob parent package json dependency hierarchy forever tgz root library forever monitor tgz chokidar tgz x glob parent tgz vulnerable library found in base branch nodegoat vulnerability details this affects the package glob parent before the enclosure regex used to check for strings ending in enclosure containing path separator 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 glob parent ws vulnerable libraries utile tgz utile tgz utile tgz a drop in replacement for util with some additional advantageous functions library home page a href path to dependency file package json path to vulnerable library node modules utile package json dependency hierarchy forever tgz root library x utile tgz vulnerable library utile tgz a drop in replacement for util with some additional advantageous functions library home page a href path to dependency file package json path to vulnerable library node modules broadway node modules utile package json node modules prompt node modules utile package json dependency hierarchy forever tgz root library forever monitor tgz broadway tgz x utile tgz vulnerable library found in base branch nodegoat vulnerability details the utile npm module version allows to extract sensitive data from uninitialized memory or to cause a dos by passing in a large number in setups where typed user input can be passed e g from json publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact 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 jetbrains rider cve vulnerable library minimatch tgz a glob matcher in javascript library home page a href dependency hierarchy forever tgz root library forever monitor tgz x minimatch tgz vulnerable library found in base branch nodegoat vulnerability details a vulnerability was found in the minimatch package this flaw allows a regular expression denial of service redos when calling the braceexpand function with specific arguments resulting in 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 release date fix resolution minimatch cve vulnerable libraries nconf tgz nconf tgz nconf tgz hierarchical node js configuration with files environment variables command line arguments and atomic object merging library home page a href path to dependency file package json path to vulnerable library node modules broadway node modules nconf package json dependency hierarchy forever tgz root library forever monitor tgz broadway tgz x nconf tgz vulnerable library nconf tgz hierarchical node js configuration with files environment variables command line arguments and atomic object merging library home page a href path to dependency file package json path to vulnerable library node modules nconf package json dependency hierarchy forever tgz root library x nconf tgz vulnerable library found in base branch nodegoat vulnerability details this affects the package nconf before when using the memory engine it is possible to store a nested json representation of the configuration the set function that is responsible for setting the configuration properties is vulnerable to prototype pollution by providing a crafted property it is possible to modify the properties on the object prototype 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 high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution nconf direct dependency fix resolution forever fix resolution nconf direct dependency fix resolution forever in order to enable automatic remediation please create cve vulnerable library decode uri component tgz a better decodeuricomponent library home page a href path to dependency file package json path to vulnerable library node modules decode uri component package json dependency hierarchy forever tgz root library forever monitor tgz chokidar tgz braces tgz snapdragon tgz source map resolve tgz x decode uri component tgz vulnerable library found in base branch nodegoat vulnerability details decode uri component is vulnerable to improper input validation resulting in dos 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 decode uri component direct dependency fix resolution forever in order to enable automatic remediation please create cve vulnerable library i tgz custom inflections for nodejs library home page a href path to dependency file package json path to vulnerable library node modules i package json dependency hierarchy forever tgz root library utile tgz x i tgz vulnerable library found in base branch nodegoat vulnerability details inflect is vulnerable to inefficient regular expression complexity 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 i direct dependency fix resolution forever in order to enable automatic remediation please create in order to enable automatic remediation for this issue please create | 0 |
472,348 | 13,622,932,585 | IssuesEvent | 2020-09-24 05:05:01 | eXpandFramework/eXpand | https://api.github.com/repos/eXpandFramework/eXpand | closed | SequenceGenerator Error when connection is not by SSPI | Bug Priority SequenceGenerator Standalone_XAF_Modules ❤ Sponsor | If I connect ta Database with a connectionstring not based on SSPI I got an Error on SequenceGeneratorService.cs:Zeile 277
If you connect with SSPI there is no error. Maybe the password in the connectionstring is lost?
SequenceGeneratorService.cs:
public static IObservable<IDataLayer> SequenceGeneratorDatalayer(this IObjectSpaceProvider objectSpaceProvider)
=> Observable.Defer(() => XpoDefault.GetDataLayer(objectSpaceProvider.GetConnectionString(),
((TypesInfo) objectSpaceProvider.TypesInfo).EntityStores.OfType<XpoTypeInfoSource>().First().XPDictionary, AutoCreateOption.None
).ReturnObservable()).SubscribeReplay()
.TraceSequenceGeneratorModule();
The error occurred:
Type: UnableToOpenDatabaseException
Message: Fehler beim Öffnen der Datenbank. Verbindungszeichenfolge: 'Data Source=172.16.0.36;Initial Catalog=eJHCRS;User ID=eJHCRS;Pooling=False;'; Fehler: 'System.Data.SqlClient.SqlException (0x80131904): Fehler bei der Anmeldung für den Benutzer "eJHCRS".
bei System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling, SqlAuthenticationProviderManager sqlAuthProviderManager)
bei System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
bei System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
bei System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
bei System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
bei System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
bei System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
bei System.Data.SqlClient.SqlConnection.Open()
bei DevExpress.Xpo.DB.MSSqlConnectionProvider.CreateDataBase(IDbConnection conn)
ClientConnectionId:d455f5f8-d7c7-42bc-877a-fd42829af5ef
Fehlernummer (Error Number):18456,Status (State):1,Klasse (Class):14'
Data: 0 entries
Stack trace:
bei DevExpress.Xpo.DB.MSSqlConnectionProvider.CreateDataBase(IDbConnection conn)
bei DevExpress.Xpo.DB.MSSqlConnectionProvider.CreateDataBase()
bei DevExpress.Xpo.DB.ConnectionProviderSql..ctor(IDbConnection connection, AutoCreateOption autoCreateOption)
bei DevExpress.Xpo.DB.MSSqlConnectionProvider..ctor(IDbConnection connection, AutoCreateOption autoCreateOption)
bei DevExpress.Xpo.DB.MSSqlConnectionProvider.CreateProviderFromString(String connectionString, AutoCreateOption autoCreateOption, IDisposable[]& objectsToDisposeOnDisconnect)
bei DevExpress.Xpo.XpoDefault.GetConnectionProvider(String connectionString, AutoCreateOption defaultAutoCreateOption, IDisposable[]& objectsToDisposeOnDisconnect)
bei DevExpress.Xpo.XpoDefault.GetDataLayer(String connectionString, XPDictionary dictionary, AutoCreateOption defaultAutoCreateOption, IDisposable[]& objectsToDisposeOnDisconnect)
bei DevExpress.Xpo.XpoDefault.GetDataLayer(String connectionString, XPDictionary dictionary, AutoCreateOption defaultAutoCreateOption)
bei Xpand.XAF.Modules.SequenceGenerator.SequenceGeneratorService.<>c__DisplayClass34_0.<SequenceGeneratorDatalayer>b__0() in D:\a\1\s\src\Modules\SequenceGenerator\SequenceGeneratorService.cs:Zeile 277.
bei System.Reactive.Linq.ObservableImpl.Defer`1._.Run() in /_/Rx.NET/Source/src/System.Reactive/Linq/Observable/Defer.cs:Zeile 38.
| 1.0 | SequenceGenerator Error when connection is not by SSPI - If I connect ta Database with a connectionstring not based on SSPI I got an Error on SequenceGeneratorService.cs:Zeile 277
If you connect with SSPI there is no error. Maybe the password in the connectionstring is lost?
SequenceGeneratorService.cs:
public static IObservable<IDataLayer> SequenceGeneratorDatalayer(this IObjectSpaceProvider objectSpaceProvider)
=> Observable.Defer(() => XpoDefault.GetDataLayer(objectSpaceProvider.GetConnectionString(),
((TypesInfo) objectSpaceProvider.TypesInfo).EntityStores.OfType<XpoTypeInfoSource>().First().XPDictionary, AutoCreateOption.None
).ReturnObservable()).SubscribeReplay()
.TraceSequenceGeneratorModule();
The error occurred:
Type: UnableToOpenDatabaseException
Message: Fehler beim Öffnen der Datenbank. Verbindungszeichenfolge: 'Data Source=172.16.0.36;Initial Catalog=eJHCRS;User ID=eJHCRS;Pooling=False;'; Fehler: 'System.Data.SqlClient.SqlException (0x80131904): Fehler bei der Anmeldung für den Benutzer "eJHCRS".
bei System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling, SqlAuthenticationProviderManager sqlAuthProviderManager)
bei System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
bei System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
bei System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
bei System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
bei System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
bei System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
bei System.Data.SqlClient.SqlConnection.Open()
bei DevExpress.Xpo.DB.MSSqlConnectionProvider.CreateDataBase(IDbConnection conn)
ClientConnectionId:d455f5f8-d7c7-42bc-877a-fd42829af5ef
Fehlernummer (Error Number):18456,Status (State):1,Klasse (Class):14'
Data: 0 entries
Stack trace:
bei DevExpress.Xpo.DB.MSSqlConnectionProvider.CreateDataBase(IDbConnection conn)
bei DevExpress.Xpo.DB.MSSqlConnectionProvider.CreateDataBase()
bei DevExpress.Xpo.DB.ConnectionProviderSql..ctor(IDbConnection connection, AutoCreateOption autoCreateOption)
bei DevExpress.Xpo.DB.MSSqlConnectionProvider..ctor(IDbConnection connection, AutoCreateOption autoCreateOption)
bei DevExpress.Xpo.DB.MSSqlConnectionProvider.CreateProviderFromString(String connectionString, AutoCreateOption autoCreateOption, IDisposable[]& objectsToDisposeOnDisconnect)
bei DevExpress.Xpo.XpoDefault.GetConnectionProvider(String connectionString, AutoCreateOption defaultAutoCreateOption, IDisposable[]& objectsToDisposeOnDisconnect)
bei DevExpress.Xpo.XpoDefault.GetDataLayer(String connectionString, XPDictionary dictionary, AutoCreateOption defaultAutoCreateOption, IDisposable[]& objectsToDisposeOnDisconnect)
bei DevExpress.Xpo.XpoDefault.GetDataLayer(String connectionString, XPDictionary dictionary, AutoCreateOption defaultAutoCreateOption)
bei Xpand.XAF.Modules.SequenceGenerator.SequenceGeneratorService.<>c__DisplayClass34_0.<SequenceGeneratorDatalayer>b__0() in D:\a\1\s\src\Modules\SequenceGenerator\SequenceGeneratorService.cs:Zeile 277.
bei System.Reactive.Linq.ObservableImpl.Defer`1._.Run() in /_/Rx.NET/Source/src/System.Reactive/Linq/Observable/Defer.cs:Zeile 38.
| non_test | sequencegenerator error when connection is not by sspi if i connect ta database with a connectionstring not based on sspi i got an error on sequencegeneratorservice cs zeile if you connect with sspi there is no error maybe the password in the connectionstring is lost sequencegeneratorservice cs public static iobservable sequencegeneratordatalayer this iobjectspaceprovider objectspaceprovider observable defer xpodefault getdatalayer objectspaceprovider getconnectionstring typesinfo objectspaceprovider typesinfo entitystores oftype first xpdictionary autocreateoption none returnobservable subscribereplay tracesequencegeneratormodule the error occurred type unabletoopendatabaseexception message fehler beim öffnen der datenbank verbindungszeichenfolge data source initial catalog ejhcrs user id ejhcrs pooling false fehler system data sqlclient sqlexception fehler bei der anmeldung für den benutzer ejhcrs bei system data sqlclient sqlinternalconnectiontds ctor dbconnectionpoolidentity identity sqlconnectionstring connectionoptions sqlcredential credential object providerinfo string newpassword securestring newsecurepassword boolean redirecteduserinstance sqlconnectionstring userconnectionoptions sessiondata reconnectsessiondata dbconnectionpool pool string accesstoken boolean applytransientfaulthandling sqlauthenticationprovidermanager sqlauthprovidermanager bei system data sqlclient sqlconnectionfactory createconnection dbconnectionoptions options dbconnectionpoolkey poolkey object poolgroupproviderinfo dbconnectionpool pool dbconnection owningconnection dbconnectionoptions useroptions bei system data providerbase dbconnectionfactory createnonpooledconnection dbconnection owningconnection dbconnectionpoolgroup poolgroup dbconnectionoptions useroptions bei system data providerbase dbconnectionfactory trygetconnection dbconnection owningconnection taskcompletionsource retry dbconnectionoptions useroptions dbconnectioninternal oldconnection dbconnectioninternal connection bei system data providerbase dbconnectioninternal tryopenconnectioninternal dbconnection outerconnection dbconnectionfactory connectionfactory taskcompletionsource retry dbconnectionoptions useroptions bei system data sqlclient sqlconnection tryopeninner taskcompletionsource retry bei system data sqlclient sqlconnection tryopen taskcompletionsource retry bei system data sqlclient sqlconnection open bei devexpress xpo db mssqlconnectionprovider createdatabase idbconnection conn clientconnectionid fehlernummer error number status state klasse class data entries stack trace bei devexpress xpo db mssqlconnectionprovider createdatabase idbconnection conn bei devexpress xpo db mssqlconnectionprovider createdatabase bei devexpress xpo db connectionprovidersql ctor idbconnection connection autocreateoption autocreateoption bei devexpress xpo db mssqlconnectionprovider ctor idbconnection connection autocreateoption autocreateoption bei devexpress xpo db mssqlconnectionprovider createproviderfromstring string connectionstring autocreateoption autocreateoption idisposable objectstodisposeondisconnect bei devexpress xpo xpodefault getconnectionprovider string connectionstring autocreateoption defaultautocreateoption idisposable objectstodisposeondisconnect bei devexpress xpo xpodefault getdatalayer string connectionstring xpdictionary dictionary autocreateoption defaultautocreateoption idisposable objectstodisposeondisconnect bei devexpress xpo xpodefault getdatalayer string connectionstring xpdictionary dictionary autocreateoption defaultautocreateoption bei xpand xaf modules sequencegenerator sequencegeneratorservice c b in d a s src modules sequencegenerator sequencegeneratorservice cs zeile bei system reactive linq observableimpl defer run in rx net source src system reactive linq observable defer cs zeile | 0 |
61,277 | 6,731,927,599 | IssuesEvent | 2017-10-18 09:30:00 | dealii/dealii | https://api.github.com/repos/dealii/dealii | opened | Boost 1.65.1 serialization issues | Tests | Anyone builds with Boost `1.65.1`, specifically when boost is compiled with mpi and python libraries? I recently upgraded the Spack tester to this latest version and see several new failing tests: https://cdash.kyomu.43-1.org/viewTest.php?onlyfailed&buildid=12246
At least `sharedtria/tria_load_01` fails with segmentation fault in Boost:
```
Thread 1 "tria_load_01.de" received signal SIGSEGV, Segmentation fault.
0x00007fffeda1b52f in boost::serialization::typeid_system::extended_type_info_typeid_0::type_unregister() ()
from /home/davydden/spack/opt/spack/linux-ubuntu16.04-x86_64/gcc-5.4.0/boost-1.65.1-f4in3tnorl5ptcrnrjxstzzitoxbboic/lib/libboost_serialization.so.1.65.1
```
`1.64` is known to be unstable when built with both `mpi` and `python` parts https://github.com/LLNL/spack/issues/3963 . Although `make_array` issues discussed there are gone, it could be that something else is still wrong with `boost`...
p.s. backtrace was not useful in this case as I did not keep the build folder of boost:
```
(gdb) bt
#0 0x00007fffeda1b52f in boost::serialization::typeid_system::extended_type_info_typeid_0::type_unregister() ()
from /home/davydden/spack/opt/spack/linux-ubuntu16.04-x86_64/gcc-5.4.0/boost-1.65.1-f4in3tnorl5ptcrnrjxstzzitoxbboic/lib/libboost_serialization.so.1.65.1
#1 0x00000000004f0715 in boost::serialization::extended_type_info_typeid<std::vector<unsigned int, std::allocator<unsigned int> > >::~extended_type_info_typeid (
this=0x575200 <boost::serialization::singleton<boost::serialization::extended_type_info_typeid<std::vector<unsigned int, std::allocator<unsigned int> > > >::get_instance()::t>, __in_chrg=<optimized out>)
at /home/davydden/spack/opt/spack/linux-ubuntu16.04-x86_64/gcc-5.4.0/boost-1.65.1-f4in3tnorl5ptcrnrjxstzzitoxbboic/include/boost/serialization/extended_type_info_typeid.hpp:96
#2 boost::serialization::singleton<boost::serialization::extended_type_info_typeid<std::vector<unsigned int, std::allocator<unsigned int> > > >::get_instance()::singleton_wrapper::~singleton_wrapper() (
this=0x575200 <boost::serialization::singleton<boost::serialization::extended_type_info_typeid<std::vector<unsigned int, std::allocator<unsigned int> > > >::get_instance()::t>, __in_chrg=<optimized out>)
at /home/davydden/spack/opt/spack/linux-ubuntu16.04-x86_64/gcc-5.4.0/boost-1.65.1-f4in3tnorl5ptcrnrjxstzzitoxbboic/include/boost/serialization/singleton.hpp:117
#3 0x00007fffeb4b8ff8 in __run_exit_handlers (status=0, listp=0x7fffeb8435f8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#4 0x00007fffeb4b9045 in __GI_exit (status=<optimized out>) at exit.c:104
#5 0x00007fffeb49f837 in __libc_start_main (main=0x4e6f8b <main(int, char**)>, argc=1, argv=0x7fffffffcad8, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fffffffcac8) at ../csu/libc-start.c:325
#6 0x00000000004e4639 in _start ()
```
| 1.0 | Boost 1.65.1 serialization issues - Anyone builds with Boost `1.65.1`, specifically when boost is compiled with mpi and python libraries? I recently upgraded the Spack tester to this latest version and see several new failing tests: https://cdash.kyomu.43-1.org/viewTest.php?onlyfailed&buildid=12246
At least `sharedtria/tria_load_01` fails with segmentation fault in Boost:
```
Thread 1 "tria_load_01.de" received signal SIGSEGV, Segmentation fault.
0x00007fffeda1b52f in boost::serialization::typeid_system::extended_type_info_typeid_0::type_unregister() ()
from /home/davydden/spack/opt/spack/linux-ubuntu16.04-x86_64/gcc-5.4.0/boost-1.65.1-f4in3tnorl5ptcrnrjxstzzitoxbboic/lib/libboost_serialization.so.1.65.1
```
`1.64` is known to be unstable when built with both `mpi` and `python` parts https://github.com/LLNL/spack/issues/3963 . Although `make_array` issues discussed there are gone, it could be that something else is still wrong with `boost`...
p.s. backtrace was not useful in this case as I did not keep the build folder of boost:
```
(gdb) bt
#0 0x00007fffeda1b52f in boost::serialization::typeid_system::extended_type_info_typeid_0::type_unregister() ()
from /home/davydden/spack/opt/spack/linux-ubuntu16.04-x86_64/gcc-5.4.0/boost-1.65.1-f4in3tnorl5ptcrnrjxstzzitoxbboic/lib/libboost_serialization.so.1.65.1
#1 0x00000000004f0715 in boost::serialization::extended_type_info_typeid<std::vector<unsigned int, std::allocator<unsigned int> > >::~extended_type_info_typeid (
this=0x575200 <boost::serialization::singleton<boost::serialization::extended_type_info_typeid<std::vector<unsigned int, std::allocator<unsigned int> > > >::get_instance()::t>, __in_chrg=<optimized out>)
at /home/davydden/spack/opt/spack/linux-ubuntu16.04-x86_64/gcc-5.4.0/boost-1.65.1-f4in3tnorl5ptcrnrjxstzzitoxbboic/include/boost/serialization/extended_type_info_typeid.hpp:96
#2 boost::serialization::singleton<boost::serialization::extended_type_info_typeid<std::vector<unsigned int, std::allocator<unsigned int> > > >::get_instance()::singleton_wrapper::~singleton_wrapper() (
this=0x575200 <boost::serialization::singleton<boost::serialization::extended_type_info_typeid<std::vector<unsigned int, std::allocator<unsigned int> > > >::get_instance()::t>, __in_chrg=<optimized out>)
at /home/davydden/spack/opt/spack/linux-ubuntu16.04-x86_64/gcc-5.4.0/boost-1.65.1-f4in3tnorl5ptcrnrjxstzzitoxbboic/include/boost/serialization/singleton.hpp:117
#3 0x00007fffeb4b8ff8 in __run_exit_handlers (status=0, listp=0x7fffeb8435f8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#4 0x00007fffeb4b9045 in __GI_exit (status=<optimized out>) at exit.c:104
#5 0x00007fffeb49f837 in __libc_start_main (main=0x4e6f8b <main(int, char**)>, argc=1, argv=0x7fffffffcad8, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fffffffcac8) at ../csu/libc-start.c:325
#6 0x00000000004e4639 in _start ()
```
| test | boost serialization issues anyone builds with boost specifically when boost is compiled with mpi and python libraries i recently upgraded the spack tester to this latest version and see several new failing tests at least sharedtria tria load fails with segmentation fault in boost thread tria load de received signal sigsegv segmentation fault in boost serialization typeid system extended type info typeid type unregister from home davydden spack opt spack linux gcc boost lib libboost serialization so is known to be unstable when built with both mpi and python parts although make array issues discussed there are gone it could be that something else is still wrong with boost p s backtrace was not useful in this case as i did not keep the build folder of boost gdb bt in boost serialization typeid system extended type info typeid type unregister from home davydden spack opt spack linux gcc boost lib libboost serialization so in boost serialization extended type info typeid extended type info typeid this get instance t in chrg at home davydden spack opt spack linux gcc boost include boost serialization extended type info typeid hpp boost serialization singleton get instance singleton wrapper singleton wrapper this get instance t in chrg at home davydden spack opt spack linux gcc boost include boost serialization singleton hpp in run exit handlers status listp run list atexit run list atexit entry true at exit c in gi exit status at exit c in libc start main main argc argv init fini rtld fini stack end at csu libc start c in start | 1 |
51,578 | 7,717,100,688 | IssuesEvent | 2018-05-23 12:50:38 | processing/p5.js | https://api.github.com/repos/processing/p5.js | closed | Old saveCanvas() Safari behaviour described on reference page | area:documentation good first issue | The reference describe that in Safari, [`saveCanvas()`](https://p5js.org/reference/#/p5/saveCanvas) will open the saved image in a new window and the user need to rename upon save as. However when I tested `saveCanvas()` on Safari 11.1 (ie. latest) it is no longer behaving like that, probably because of the blobing change. It nows simply save the image directly to the downloads folder.
I have no idea how far back this behaviour goes but I think the reference can potentially remove that description because if may not affect that much Safari users anymore? Instead just keep the general browsers' behaviour description as it now also applies to Safari. | 1.0 | Old saveCanvas() Safari behaviour described on reference page - The reference describe that in Safari, [`saveCanvas()`](https://p5js.org/reference/#/p5/saveCanvas) will open the saved image in a new window and the user need to rename upon save as. However when I tested `saveCanvas()` on Safari 11.1 (ie. latest) it is no longer behaving like that, probably because of the blobing change. It nows simply save the image directly to the downloads folder.
I have no idea how far back this behaviour goes but I think the reference can potentially remove that description because if may not affect that much Safari users anymore? Instead just keep the general browsers' behaviour description as it now also applies to Safari. | non_test | old savecanvas safari behaviour described on reference page the reference describe that in safari will open the saved image in a new window and the user need to rename upon save as however when i tested savecanvas on safari ie latest it is no longer behaving like that probably because of the blobing change it nows simply save the image directly to the downloads folder i have no idea how far back this behaviour goes but i think the reference can potentially remove that description because if may not affect that much safari users anymore instead just keep the general browsers behaviour description as it now also applies to safari | 0 |
91,112 | 26,277,277,438 | IssuesEvent | 2023-01-07 00:06:41 | expo/expo | https://api.github.com/repos/expo/expo | closed | Black Status Bar after setting sticky-immersive | needs review incomplete issue: missing or invalid repro Development Builds | ### Summary
After setting `androidNavigationBar: { visible:'sticky-immersive' }` in my app.json file a black bar replaces the Status Bar.
### Managed or bare workflow?
managed
### What platform(s) does this occur on?
Android
### Package versions
_No response_
### Environment
expo-env-info 1.0.5 environment info:
System:
OS: Windows 10 10.0.22000
Binaries:
Node: 16.15.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - C:\Program Files\nodejs\yarn.CMD
npm: 6.14.16 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: Version 2021.1.0.0 AI-211.7628.21.2111.8309675
npmPackages:
expo: ~44.0.0 => 44.0.6
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: 0.64.3 => 0.64.3
react-native-web: 0.17.1 => 0.17.1
Expo Workflow: managed
### Reproducible demo
`app.json` file
```
{
"expo": {
"name": "testing-app",
"slug": "testing-app",
"version": "1.0.0",
"orientation": "portrait",
"icon": "./assets/icon.png",
"splash": {
"image": "./assets/splash.png",
"resizeMode": "contain",
"backgroundColor": "#ffffff"
},
"updates": {
"fallbackToCacheTimeout": 0
},
"assetBundlePatterns": [
"**/*"
],
"ios": {
"supportsTablet": true
},
"android": {
"adaptiveIcon": {
"foregroundImage": "./assets/adaptive-icon.png",
"backgroundColor": "#FFFFFF"
}
},
"androidNavigationBar" : {
"visible":"sticky-immersive"
},
"web": {
"favicon": "./assets/favicon.png"
}
}
}
```
` App.js` file
```
import { StatusBar } from 'expo-status-bar';
import { StyleSheet, Text, View } from 'react-native';
export default function App() {
return (
<View style={styles.container}>
<Text>Black bar on top!</Text>
<StatusBar style="auto" />
</View>
);
}
const styles = StyleSheet.create({
container: {
flex: 1,
backgroundColor: '#fff',
alignItems: 'center',
justifyContent: 'center',
},
});
```
### Stacktrace (if a crash is involved)
_No response_ | 1.0 | Black Status Bar after setting sticky-immersive - ### Summary
After setting `androidNavigationBar: { visible:'sticky-immersive' }` in my app.json file a black bar replaces the Status Bar.
### Managed or bare workflow?
managed
### What platform(s) does this occur on?
Android
### Package versions
_No response_
### Environment
expo-env-info 1.0.5 environment info:
System:
OS: Windows 10 10.0.22000
Binaries:
Node: 16.15.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - C:\Program Files\nodejs\yarn.CMD
npm: 6.14.16 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: Version 2021.1.0.0 AI-211.7628.21.2111.8309675
npmPackages:
expo: ~44.0.0 => 44.0.6
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: 0.64.3 => 0.64.3
react-native-web: 0.17.1 => 0.17.1
Expo Workflow: managed
### Reproducible demo
`app.json` file
```
{
"expo": {
"name": "testing-app",
"slug": "testing-app",
"version": "1.0.0",
"orientation": "portrait",
"icon": "./assets/icon.png",
"splash": {
"image": "./assets/splash.png",
"resizeMode": "contain",
"backgroundColor": "#ffffff"
},
"updates": {
"fallbackToCacheTimeout": 0
},
"assetBundlePatterns": [
"**/*"
],
"ios": {
"supportsTablet": true
},
"android": {
"adaptiveIcon": {
"foregroundImage": "./assets/adaptive-icon.png",
"backgroundColor": "#FFFFFF"
}
},
"androidNavigationBar" : {
"visible":"sticky-immersive"
},
"web": {
"favicon": "./assets/favicon.png"
}
}
}
```
` App.js` file
```
import { StatusBar } from 'expo-status-bar';
import { StyleSheet, Text, View } from 'react-native';
export default function App() {
return (
<View style={styles.container}>
<Text>Black bar on top!</Text>
<StatusBar style="auto" />
</View>
);
}
const styles = StyleSheet.create({
container: {
flex: 1,
backgroundColor: '#fff',
alignItems: 'center',
justifyContent: 'center',
},
});
```
### Stacktrace (if a crash is involved)
_No response_ | non_test | black status bar after setting sticky immersive summary after setting androidnavigationbar visible sticky immersive in my app json file a black bar replaces the status bar managed or bare workflow managed what platform s does this occur on android package versions no response environment expo env info environment info system os windows binaries node c program files nodejs node exe yarn c program files nodejs yarn cmd npm c program files nodejs npm cmd ides android studio version ai npmpackages expo react react dom react native react native web expo workflow managed reproducible demo app json file expo name testing app slug testing app version orientation portrait icon assets icon png splash image assets splash png resizemode contain backgroundcolor ffffff updates fallbacktocachetimeout assetbundlepatterns ios supportstablet true android adaptiveicon foregroundimage assets adaptive icon png backgroundcolor ffffff androidnavigationbar visible sticky immersive web favicon assets favicon png app js file import statusbar from expo status bar import stylesheet text view from react native export default function app return black bar on top const styles stylesheet create container flex backgroundcolor fff alignitems center justifycontent center stacktrace if a crash is involved no response | 0 |
728,251 | 25,073,001,343 | IssuesEvent | 2022-11-07 13:36:13 | VocaDB/vocadb | https://api.github.com/repos/VocaDB/vocadb | closed | Song details page: popups are no longer draggable | Priority: Low songs frontend | It used to be possible to move the popups on song details page by dragging the title. For example "add to custom list", "report an error" and "edit tags" dialogs. | 1.0 | Song details page: popups are no longer draggable - It used to be possible to move the popups on song details page by dragging the title. For example "add to custom list", "report an error" and "edit tags" dialogs. | non_test | song details page popups are no longer draggable it used to be possible to move the popups on song details page by dragging the title for example add to custom list report an error and edit tags dialogs | 0 |
293,930 | 22,100,383,957 | IssuesEvent | 2022-06-01 13:21:57 | DataCloud-project/SIM-PIPE | https://api.github.com/repos/DataCloud-project/SIM-PIPE | opened | Finalize simulation example | documentation | Finalize example used in running your first data pipeline simulation. | 1.0 | Finalize simulation example - Finalize example used in running your first data pipeline simulation. | non_test | finalize simulation example finalize example used in running your first data pipeline simulation | 0 |
294,738 | 9,040,109,825 | IssuesEvent | 2019-02-10 13:38:32 | ccs-computing-w19/tetris_ai | https://api.github.com/repos/ccs-computing-w19/tetris_ai | closed | Counterclockwise Rotation | Priority: 1 (High) Topic: Engine | Create method in Tetris which allows the active tile to be rotated counterclockwise. | 1.0 | Counterclockwise Rotation - Create method in Tetris which allows the active tile to be rotated counterclockwise. | non_test | counterclockwise rotation create method in tetris which allows the active tile to be rotated counterclockwise | 0 |
163,393 | 6,197,768,655 | IssuesEvent | 2017-07-05 17:35:55 | hhanesand/softmaker-android-issues | https://api.github.com/repos/hhanesand/softmaker-android-issues | opened | autofill issue in username field on login (uncertain if caused by password manager) | enhancement low priority | When prefilling the username of the user that was last logged in on the log in screen, the cursor should be moved to the password field underneath, so the user does not have to press the field. | 1.0 | autofill issue in username field on login (uncertain if caused by password manager) - When prefilling the username of the user that was last logged in on the log in screen, the cursor should be moved to the password field underneath, so the user does not have to press the field. | non_test | autofill issue in username field on login uncertain if caused by password manager when prefilling the username of the user that was last logged in on the log in screen the cursor should be moved to the password field underneath so the user does not have to press the field | 0 |
2,800 | 2,644,837,632 | IssuesEvent | 2015-03-12 19:05:34 | vinnyg/LittleMouse | https://api.github.com/repos/vinnyg/LittleMouse | opened | Mouse class: GetState(int* x, int* y) | design non-essential | Provide private members x, y.
GetPosition will return the position of the mouse.
GetState(int* x, int* y) will be refactored to GetState() and will no longer return a position, only the state of its buttons. | 1.0 | Mouse class: GetState(int* x, int* y) - Provide private members x, y.
GetPosition will return the position of the mouse.
GetState(int* x, int* y) will be refactored to GetState() and will no longer return a position, only the state of its buttons. | non_test | mouse class getstate int x int y provide private members x y getposition will return the position of the mouse getstate int x int y will be refactored to getstate and will no longer return a position only the state of its buttons | 0 |
18,550 | 3,696,626,200 | IssuesEvent | 2016-02-27 03:44:54 | softlayer/sl-ember-components | https://api.github.com/repos/softlayer/sl-ember-components | closed | Unit | Component | sl progress bar: There are no references to Ember.$, $ or jQuery | ready sl-progress-bar tests | ```
not ok 567 PhantomJS 1.9 - Unit | Component | sl progress bar: There are no references to Ember.$, $ or jQuery
---
actual: >
null
message: >
Died on test #1 at test (http://localhost:7357/assets/test-support.js:3025)
at testWrapper (http://localhost:7357/assets/test-support.js:6192)
at test (http://localhost:7357/assets/test-support.js:6205)
at http://localhost:7357/assets/tests.js:25920
at http://localhost:7357/assets/vendor.js:152
at tryFinally (http://localhost:7357/assets/vendor.js:33)
at http://localhost:7357/assets/vendor.js:158
at http://localhost:7357/assets/test-loader.js:60
at http://localhost:7357/assets/test-loader.js:51
at http://localhost:7357/assets/test-loader.js:82
at http://localhost:7357/assets/test-support.js:6024: Attempted to wrap $ which is already wrapped
Log: |
...
``` | 1.0 | Unit | Component | sl progress bar: There are no references to Ember.$, $ or jQuery - ```
not ok 567 PhantomJS 1.9 - Unit | Component | sl progress bar: There are no references to Ember.$, $ or jQuery
---
actual: >
null
message: >
Died on test #1 at test (http://localhost:7357/assets/test-support.js:3025)
at testWrapper (http://localhost:7357/assets/test-support.js:6192)
at test (http://localhost:7357/assets/test-support.js:6205)
at http://localhost:7357/assets/tests.js:25920
at http://localhost:7357/assets/vendor.js:152
at tryFinally (http://localhost:7357/assets/vendor.js:33)
at http://localhost:7357/assets/vendor.js:158
at http://localhost:7357/assets/test-loader.js:60
at http://localhost:7357/assets/test-loader.js:51
at http://localhost:7357/assets/test-loader.js:82
at http://localhost:7357/assets/test-support.js:6024: Attempted to wrap $ which is already wrapped
Log: |
...
``` | test | unit component sl progress bar there are no references to ember or jquery not ok phantomjs unit component sl progress bar there are no references to ember or jquery actual null message died on test at test at testwrapper at test at at at tryfinally at at at at at attempted to wrap which is already wrapped log | 1 |
147,279 | 19,512,580,863 | IssuesEvent | 2021-12-29 02:40:03 | AlexRogalskiy/AlexRogalskiy | https://api.github.com/repos/AlexRogalskiy/AlexRogalskiy | opened | CVE-2019-25009 (High) detected in http-0.1.21.crate | security vulnerability | ## CVE-2019-25009 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>http-0.1.21.crate</b></p></summary>
<p>A set of types for representing HTTP requests and responses.
</p>
<p>Library home page: <a href="https://crates.io/api/v1/crates/http/0.1.21/download">https://crates.io/api/v1/crates/http/0.1.21/download</a></p>
<p>
Dependency Hierarchy:
- rss-1.9.0.crate (Root Library)
- reqwest-0.9.24.crate
- hyper-0.12.35.crate
- http-body-0.1.0.crate
- :x: **http-0.1.21.crate** (Vulnerable Library)
<p>Found in base branch: <b>master</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>
An issue was discovered in the http crate before 0.1.20 for Rust. The HeaderMap::Drain API can use a raw pointer, defeating soundness.
<p>Publish Date: 2020-12-31
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-25009>CVE-2019-25009</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/hyperium/http/releases/tag/v0.1.21">https://github.com/hyperium/http/releases/tag/v0.1.21</a></p>
<p>Release Date: 2020-12-31</p>
<p>Fix Resolution: v0.1.21</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2019-25009 (High) detected in http-0.1.21.crate - ## CVE-2019-25009 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>http-0.1.21.crate</b></p></summary>
<p>A set of types for representing HTTP requests and responses.
</p>
<p>Library home page: <a href="https://crates.io/api/v1/crates/http/0.1.21/download">https://crates.io/api/v1/crates/http/0.1.21/download</a></p>
<p>
Dependency Hierarchy:
- rss-1.9.0.crate (Root Library)
- reqwest-0.9.24.crate
- hyper-0.12.35.crate
- http-body-0.1.0.crate
- :x: **http-0.1.21.crate** (Vulnerable Library)
<p>Found in base branch: <b>master</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>
An issue was discovered in the http crate before 0.1.20 for Rust. The HeaderMap::Drain API can use a raw pointer, defeating soundness.
<p>Publish Date: 2020-12-31
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-25009>CVE-2019-25009</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/hyperium/http/releases/tag/v0.1.21">https://github.com/hyperium/http/releases/tag/v0.1.21</a></p>
<p>Release Date: 2020-12-31</p>
<p>Fix Resolution: v0.1.21</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 high detected in http crate cve high severity vulnerability vulnerable library http crate a set of types for representing http requests and responses library home page a href dependency hierarchy rss crate root library reqwest crate hyper crate http body crate x http crate vulnerable library found in base branch master vulnerability details an issue was discovered in the http crate before for rust the headermap drain api can use a raw pointer defeating soundness 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 step up your open source security game with whitesource | 0 |
376,808 | 11,157,051,720 | IssuesEvent | 2019-12-25 10:23:39 | incognitochain/incognito-wallet | https://api.github.com/repos/incognitochain/incognito-wallet | closed | No message when withdraw reward from staking | Priority: Low Type: Enhancement | At this moment, there is no message/ pop up when we withdraw the reward from Virtual Node to our wallet.
I think we should give a short message/ pop up here to make it clear.
| 1.0 | No message when withdraw reward from staking - At this moment, there is no message/ pop up when we withdraw the reward from Virtual Node to our wallet.
I think we should give a short message/ pop up here to make it clear.
| non_test | no message when withdraw reward from staking at this moment there is no message pop up when we withdraw the reward from virtual node to our wallet i think we should give a short message pop up here to make it clear | 0 |
160,874 | 25,247,921,969 | IssuesEvent | 2022-11-15 12:35:19 | Regalis11/Barotrauma | https://api.github.com/repos/Regalis11/Barotrauma | closed | [UNSTABLE] Substantial Deusizine dosage can kill the Defense Bot | Bug Design | ### Disclaimers
- [X] I have searched the issue tracker to check if the issue has already been reported.
- [ ] My issue happened while using mods.
### What happened?
The inflammation (burn damage) Deusizine causes will deplete the Defense Bot's health as though it is poisoned. The chances of someone using Deusizine on a Defense Bot is absurdly low so perhaps this can be overlooked.
Also, the squishy/fleshy injection sound when hitting the drone with a syringe can be misleading. Perhaps a shattering sound should be in place when hitting a metal target? There are now technically three targets in the game that deflect syringe darts.
Deusizine can also kill the Fractal Guardian but don't ask how much it takes.
### Reproduction steps
1: Inject Defense Bot with Deusizine
2: Continue injecting a substantial amount of Deusizine into the Defense Bot
### Bug prevalence
Happens every time I play
### Version
0.20.5.0 (Unstable)
### -
_No response_
### Which operating system did you encounter this bug on?
Windows
### Relevant error messages and crash reports
_No response_ | 1.0 | [UNSTABLE] Substantial Deusizine dosage can kill the Defense Bot - ### Disclaimers
- [X] I have searched the issue tracker to check if the issue has already been reported.
- [ ] My issue happened while using mods.
### What happened?
The inflammation (burn damage) Deusizine causes will deplete the Defense Bot's health as though it is poisoned. The chances of someone using Deusizine on a Defense Bot is absurdly low so perhaps this can be overlooked.
Also, the squishy/fleshy injection sound when hitting the drone with a syringe can be misleading. Perhaps a shattering sound should be in place when hitting a metal target? There are now technically three targets in the game that deflect syringe darts.
Deusizine can also kill the Fractal Guardian but don't ask how much it takes.
### Reproduction steps
1: Inject Defense Bot with Deusizine
2: Continue injecting a substantial amount of Deusizine into the Defense Bot
### Bug prevalence
Happens every time I play
### Version
0.20.5.0 (Unstable)
### -
_No response_
### Which operating system did you encounter this bug on?
Windows
### Relevant error messages and crash reports
_No response_ | non_test | substantial deusizine dosage can kill the defense bot disclaimers i have searched the issue tracker to check if the issue has already been reported my issue happened while using mods what happened the inflammation burn damage deusizine causes will deplete the defense bot s health as though it is poisoned the chances of someone using deusizine on a defense bot is absurdly low so perhaps this can be overlooked also the squishy fleshy injection sound when hitting the drone with a syringe can be misleading perhaps a shattering sound should be in place when hitting a metal target there are now technically three targets in the game that deflect syringe darts deusizine can also kill the fractal guardian but don t ask how much it takes reproduction steps inject defense bot with deusizine continue injecting a substantial amount of deusizine into the defense bot bug prevalence happens every time i play version unstable no response which operating system did you encounter this bug on windows relevant error messages and crash reports no response | 0 |
258,022 | 22,270,863,743 | IssuesEvent | 2022-06-10 12:13:26 | keycloak/keycloak | https://api.github.com/repos/keycloak/keycloak | closed | ClientClientScopesTest failures in the test pipeline | area/testsuite kind/bug area/admin/ui | ### Describe the bug
After adding the `acr` parameter to the Keycloak, some admin tests are failing due to this.
```
Expected: [email, profile, roles, web-origins], was: [acr, email, profile, roles, web-origins]: array lengths differed, expected.length=4 actual.length=5; arrays first differed at element [0]; expected:<[email]> but was:<[acr]>
at org.junit.internal.ComparisonCriteria.arrayEquals(ComparisonCriteria.java:78)
at org.junit.internal.ComparisonCriteria.arrayEquals(ComparisonCriteria.java:28)
at org.junit.Assert.internalArrayEquals(Assert.java:534)
at org.junit.Assert.assertArrayEquals(Assert.java:285)
at org.keycloak.testsuite.Assert.assertNames(Assert.java:56)
at org.keycloak.testsuite.console.clients.ClientClientScopesTest.testEvaluateClientScopes(ClientClientScopesTest.java:127)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at org.jboss.arquillian.junit.Arquillian$8$1.invokeMethod(Arquillian.java:325)
at org.jboss.arquillian.junit.MethodInvoker$1.invoke(MethodInvoker.java:18)
at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:57)
at org.keycloak.testsuite.arquillian.ModelTestExecutor.execute(ModelTestExecutor.java:49)
at sun.reflect.GeneratedMethodAccessor427.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:62)
at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:50)
at sun.reflect.GeneratedMethodAccessor426.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:128)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:118)
at sun.reflect.GeneratedMethodAccessor425.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:116)
at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:83)
at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:69)
at sun.reflect.GeneratedMethodAccessor32.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:139)
at org.jboss.arquillian.junit.MethodInvoker.invoke(MethodInvoker.java:15)
at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:332)
at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:204)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:350)
at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54)
at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:215)
at org.jboss.arquillian.junit.Arquillian$7$1.invoke(Arquillian.java:279)
at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:88)
at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:66)
at sun.reflect.GeneratedMethodAccessor62.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:128)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:114)
at sun.reflect.GeneratedMethodAccessor60.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:116)
at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:83)
at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:69)
at sun.reflect.GeneratedMethodAccessor32.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.fireCustomLifecycle(EventTestRunnerAdaptor.java:159)
at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:273)
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.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:166)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:350)
at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54)
at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:177)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:115)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
Caused by: org.junit.ComparisonFailure: expected:<[email]> but was:<[acr]>
at org.junit.Assert.assertEquals(Assert.java:117)
at org.junit.Assert.assertEquals(Assert.java:146)
at org.junit.internal.ExactComparisonCriteria.assertElementsEqual(ExactComparisonCriteria.java:8)
at org.junit.internal.ComparisonCriteria.arrayEquals(ComparisonCriteria.java:76)
... 127 more
```
### Version
999
### Expected behavior
_No response_
### Actual behavior
_No response_
### How to Reproduce?
_No response_
### Anything else?
_No response_ | 1.0 | ClientClientScopesTest failures in the test pipeline - ### Describe the bug
After adding the `acr` parameter to the Keycloak, some admin tests are failing due to this.
```
Expected: [email, profile, roles, web-origins], was: [acr, email, profile, roles, web-origins]: array lengths differed, expected.length=4 actual.length=5; arrays first differed at element [0]; expected:<[email]> but was:<[acr]>
at org.junit.internal.ComparisonCriteria.arrayEquals(ComparisonCriteria.java:78)
at org.junit.internal.ComparisonCriteria.arrayEquals(ComparisonCriteria.java:28)
at org.junit.Assert.internalArrayEquals(Assert.java:534)
at org.junit.Assert.assertArrayEquals(Assert.java:285)
at org.keycloak.testsuite.Assert.assertNames(Assert.java:56)
at org.keycloak.testsuite.console.clients.ClientClientScopesTest.testEvaluateClientScopes(ClientClientScopesTest.java:127)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at org.jboss.arquillian.junit.Arquillian$8$1.invokeMethod(Arquillian.java:325)
at org.jboss.arquillian.junit.MethodInvoker$1.invoke(MethodInvoker.java:18)
at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:57)
at org.keycloak.testsuite.arquillian.ModelTestExecutor.execute(ModelTestExecutor.java:49)
at sun.reflect.GeneratedMethodAccessor427.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:62)
at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:50)
at sun.reflect.GeneratedMethodAccessor426.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:128)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:118)
at sun.reflect.GeneratedMethodAccessor425.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:116)
at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:83)
at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:69)
at sun.reflect.GeneratedMethodAccessor32.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:139)
at org.jboss.arquillian.junit.MethodInvoker.invoke(MethodInvoker.java:15)
at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:332)
at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:204)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:350)
at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54)
at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:215)
at org.jboss.arquillian.junit.Arquillian$7$1.invoke(Arquillian.java:279)
at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:88)
at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:66)
at sun.reflect.GeneratedMethodAccessor62.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:103)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:90)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:128)
at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:114)
at sun.reflect.GeneratedMethodAccessor60.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:116)
at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:83)
at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:69)
at sun.reflect.GeneratedMethodAccessor32.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:86)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:95)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:133)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:105)
at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.fireCustomLifecycle(EventTestRunnerAdaptor.java:159)
at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:273)
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.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:166)
at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:350)
at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54)
at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:177)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:115)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
Caused by: org.junit.ComparisonFailure: expected:<[email]> but was:<[acr]>
at org.junit.Assert.assertEquals(Assert.java:117)
at org.junit.Assert.assertEquals(Assert.java:146)
at org.junit.internal.ExactComparisonCriteria.assertElementsEqual(ExactComparisonCriteria.java:8)
at org.junit.internal.ComparisonCriteria.arrayEquals(ComparisonCriteria.java:76)
... 127 more
```
### Version
999
### Expected behavior
_No response_
### Actual behavior
_No response_
### How to Reproduce?
_No response_
### Anything else?
_No response_ | test | clientclientscopestest failures in the test pipeline describe the bug after adding the acr parameter to the keycloak some admin tests are failing due to this expected was array lengths differed expected length actual length arrays first differed at element expected but was at org junit internal comparisoncriteria arrayequals comparisoncriteria java at org junit internal comparisoncriteria arrayequals comparisoncriteria java at org junit assert internalarrayequals assert java at org junit assert assertarrayequals assert java at org keycloak testsuite assert assertnames assert java at org keycloak testsuite console clients clientclientscopestest testevaluateclientscopes clientclientscopestest java at sun reflect nativemethodaccessorimpl native method at sun reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org junit runners model frameworkmethod runreflectivecall frameworkmethod java at org junit internal runners model reflectivecallable run reflectivecallable java at org junit runners model frameworkmethod invokeexplosively frameworkmethod java at org jboss arquillian junit arquillian invokemethod arquillian java at org jboss arquillian junit methodinvoker invoke methodinvoker java at org jboss arquillian container test impl execution localtestexecuter execute localtestexecuter java at org keycloak testsuite arquillian modeltestexecutor execute modeltestexecutor java at sun reflect invoke unknown source at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org jboss arquillian core impl observerimpl invoke observerimpl java at org jboss arquillian core impl eventcontextimpl invokeobservers eventcontextimpl java at org jboss arquillian core impl eventcontextimpl proceed eventcontextimpl java at org jboss arquillian core impl managerimpl fire managerimpl java at org jboss arquillian core impl managerimpl fire managerimpl java at org jboss arquillian core impl eventimpl fire eventimpl java at org jboss arquillian container test impl execution clienttestexecuter execute clienttestexecuter java at sun reflect invoke unknown source at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org jboss arquillian core impl observerimpl invoke observerimpl java at org jboss arquillian core impl eventcontextimpl invokeobservers eventcontextimpl java at org jboss arquillian core impl eventcontextimpl proceed eventcontextimpl java at org jboss arquillian container test impl client containereventcontroller createcontext containereventcontroller java at org jboss arquillian container test impl client containereventcontroller createtestcontext containereventcontroller java at sun reflect invoke unknown source at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org jboss arquillian core impl observerimpl invoke observerimpl java at org jboss arquillian core impl eventcontextimpl proceed eventcontextimpl java at org jboss arquillian test impl testcontexthandler createtestcontext testcontexthandler java at sun reflect invoke unknown source at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org jboss arquillian core impl observerimpl invoke observerimpl java at org jboss arquillian core impl eventcontextimpl proceed eventcontextimpl java at org jboss arquillian test impl testcontexthandler createclasscontext testcontexthandler java at sun reflect invoke unknown source at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org jboss arquillian core impl observerimpl invoke observerimpl java at org jboss arquillian core impl eventcontextimpl proceed eventcontextimpl java at org jboss arquillian test impl testcontexthandler createsuitecontext testcontexthandler java at sun reflect invoke unknown source at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org jboss arquillian core impl observerimpl invoke observerimpl java at org jboss arquillian core impl eventcontextimpl proceed eventcontextimpl java at org jboss arquillian core impl managerimpl fire managerimpl java at org jboss arquillian test impl eventtestrunneradaptor test eventtestrunneradaptor java at org jboss arquillian junit methodinvoker invoke methodinvoker java at org jboss arquillian junit arquillian evaluate arquillian java at org jboss arquillian junit arquillian evaluate arquillian java at org jboss arquillian junit arquillian multiexecute arquillian java at org jboss arquillian junit arquillian access arquillian java at org jboss arquillian junit arquillian evaluate arquillian java at org jboss arquillian junit arquillian invoke arquillian java at org jboss arquillian container test impl execution clientbeforeafterlifecycleeventexecuter execute clientbeforeafterlifecycleeventexecuter java at org jboss arquillian container test impl execution clientbeforeafterlifecycleeventexecuter on clientbeforeafterlifecycleeventexecuter java at sun reflect invoke unknown source at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org jboss arquillian core impl observerimpl invoke observerimpl java at org jboss arquillian core impl eventcontextimpl invokeobservers eventcontextimpl java at org jboss arquillian core impl eventcontextimpl proceed eventcontextimpl java at org jboss arquillian container test impl client containereventcontroller createcontext containereventcontroller java at org jboss arquillian container test impl client containereventcontroller createbeforecontext containereventcontroller java at sun reflect invoke unknown source at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org jboss arquillian core impl observerimpl invoke observerimpl java at org jboss arquillian core impl eventcontextimpl proceed eventcontextimpl java at org jboss arquillian test impl testcontexthandler createtestcontext testcontexthandler java at sun reflect invoke unknown source at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org jboss arquillian core impl observerimpl invoke observerimpl java at org jboss arquillian core impl eventcontextimpl proceed eventcontextimpl java at org jboss arquillian test impl testcontexthandler createclasscontext testcontexthandler java at sun reflect invoke unknown source at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org jboss arquillian core impl observerimpl invoke observerimpl java at org jboss arquillian core impl eventcontextimpl proceed eventcontextimpl java at org jboss arquillian test impl testcontexthandler createsuitecontext testcontexthandler java at sun reflect invoke unknown source at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at org jboss arquillian core impl observerimpl invoke observerimpl java at org jboss arquillian core impl eventcontextimpl proceed eventcontextimpl java at org jboss arquillian core impl managerimpl fire managerimpl java at org jboss arquillian core impl managerimpl fire managerimpl java at org jboss arquillian test impl eventtestrunneradaptor firecustomlifecycle eventtestrunneradaptor java at org jboss arquillian junit arquillian evaluate arquillian 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 jboss arquillian junit arquillian evaluate arquillian java at org jboss arquillian junit arquillian multiexecute arquillian java at org jboss arquillian junit arquillian access arquillian java at org jboss arquillian junit arquillian evaluate arquillian java at org junit runners parentrunner evaluate parentrunner java at org junit runners parentrunner run parentrunner java at org jboss arquillian junit arquillian run arquillian java at org apache maven surefire execute java at org apache maven surefire executewithrerun java at org apache maven surefire executetestset java at org apache maven surefire invoke java at org apache maven surefire booter forkedbooter runsuitesinprocess forkedbooter java at org apache maven surefire booter forkedbooter execute forkedbooter java at org apache maven surefire booter forkedbooter run forkedbooter java at org apache maven surefire booter forkedbooter main forkedbooter java caused by org junit comparisonfailure expected but was at org junit assert assertequals assert java at org junit assert assertequals assert java at org junit internal exactcomparisoncriteria assertelementsequal exactcomparisoncriteria java at org junit internal comparisoncriteria arrayequals comparisoncriteria java more version expected behavior no response actual behavior no response how to reproduce no response anything else no response | 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.