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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
149,102 | 19,565,302,096 | IssuesEvent | 2022-01-03 22:52:31 | ghc-dev/Ashley-Barrett | https://api.github.com/repos/ghc-dev/Ashley-Barrett | opened | WS-2018-0590 (High) detected in diff-1.3.2.tgz | security vulnerability | ## WS-2018-0590 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>diff-1.3.2.tgz</b></p></summary>
<p>A javascript text diff implementation.</p>
<p>Library home page: <a href="https://registry.npmjs.org/diff/-/diff-1.3.2.tgz">https://registry.npmjs.org/diff/-/diff-1.3.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/diff/package.json</p>
<p>
Dependency Hierarchy:
- grunt-autoprefixer-3.0.4.tgz (Root Library)
- :x: **diff-1.3.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/Ashley-Barrett/commit/2785ec46344553450b12c57f3fe8c94dfb74fdaa">2785ec46344553450b12c57f3fe8c94dfb74fdaa</a></p>
<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>
A vulnerability was found in diff before v3.5.0, the affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks.
<p>Publish Date: 2018-03-05
<p>URL: <a href=https://bugzilla.redhat.com/show_bug.cgi?id=1552148>WS-2018-0590</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>7.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/kpdecker/jsdiff/commit/2aec4298639bf30fb88a00b356bf404d3551b8c0">https://github.com/kpdecker/jsdiff/commit/2aec4298639bf30fb88a00b356bf404d3551b8c0</a></p>
<p>Release Date: 2018-03-05</p>
<p>Fix Resolution: 3.5.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"diff","packageVersion":"1.3.2","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-autoprefixer:3.0.4;diff:1.3.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"3.5.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2018-0590","vulnerabilityDetails":"A vulnerability was found in diff before v3.5.0, the affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks.","vulnerabilityUrl":"https://bugzilla.redhat.com/show_bug.cgi?id\u003d1552148","cvss2Severity":"high","cvss2Score":"7.0","extraData":{}}</REMEDIATE> --> | True | WS-2018-0590 (High) detected in diff-1.3.2.tgz - ## WS-2018-0590 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>diff-1.3.2.tgz</b></p></summary>
<p>A javascript text diff implementation.</p>
<p>Library home page: <a href="https://registry.npmjs.org/diff/-/diff-1.3.2.tgz">https://registry.npmjs.org/diff/-/diff-1.3.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/diff/package.json</p>
<p>
Dependency Hierarchy:
- grunt-autoprefixer-3.0.4.tgz (Root Library)
- :x: **diff-1.3.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/Ashley-Barrett/commit/2785ec46344553450b12c57f3fe8c94dfb74fdaa">2785ec46344553450b12c57f3fe8c94dfb74fdaa</a></p>
<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>
A vulnerability was found in diff before v3.5.0, the affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks.
<p>Publish Date: 2018-03-05
<p>URL: <a href=https://bugzilla.redhat.com/show_bug.cgi?id=1552148>WS-2018-0590</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>7.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/kpdecker/jsdiff/commit/2aec4298639bf30fb88a00b356bf404d3551b8c0">https://github.com/kpdecker/jsdiff/commit/2aec4298639bf30fb88a00b356bf404d3551b8c0</a></p>
<p>Release Date: 2018-03-05</p>
<p>Fix Resolution: 3.5.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"diff","packageVersion":"1.3.2","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-autoprefixer:3.0.4;diff:1.3.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"3.5.0","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"WS-2018-0590","vulnerabilityDetails":"A vulnerability was found in diff before v3.5.0, the affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks.","vulnerabilityUrl":"https://bugzilla.redhat.com/show_bug.cgi?id\u003d1552148","cvss2Severity":"high","cvss2Score":"7.0","extraData":{}}</REMEDIATE> --> | non_test | ws high detected in diff tgz ws high severity vulnerability vulnerable library diff tgz a javascript text diff implementation library home page a href path to dependency file package json path to vulnerable library node modules diff package json dependency hierarchy grunt autoprefixer tgz root library x diff tgz vulnerable library found in head commit a href found in base branch master vulnerability details a vulnerability was found in diff before the affected versions of this package are vulnerable to regular expression denial of service redos attacks publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree grunt autoprefixer diff isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier ws vulnerabilitydetails a vulnerability was found in diff before the affected versions of this package are vulnerable to regular expression denial of service redos attacks vulnerabilityurl | 0 |
81,275 | 10,115,945,383 | IssuesEvent | 2019-07-30 23:40:19 | microsoft/microsoft-ui-xaml | https://api.github.com/repos/microsoft/microsoft-ui-xaml | reopened | Proposal: Update hover visual | area-UIDesign feature proposal | ## Summary
Update the hover visual to align more with the depth model. When item is hovered over, the item is lifted. When you get closer to the item, the color becomes lighter.
## Rationale
* The button today indicates hover via grid border lines. Removed the border and using color is more coherent and consistent.
* Follows the other control updates being proposed. | 1.0 | Proposal: Update hover visual - ## Summary
Update the hover visual to align more with the depth model. When item is hovered over, the item is lifted. When you get closer to the item, the color becomes lighter.
## Rationale
* The button today indicates hover via grid border lines. Removed the border and using color is more coherent and consistent.
* Follows the other control updates being proposed. | non_test | proposal update hover visual summary update the hover visual to align more with the depth model when item is hovered over the item is lifted when you get closer to the item the color becomes lighter rationale the button today indicates hover via grid border lines removed the border and using color is more coherent and consistent follows the other control updates being proposed | 0 |
244,775 | 20,711,748,093 | IssuesEvent | 2022-03-12 02:24:09 | Uuvana-Studios/longvinter-windows-client | https://api.github.com/repos/Uuvana-Studios/longvinter-windows-client | opened | Shop Can't Be Closed | bug Not Tested | **Describe the bug**
A's Farming shop can't be closed
**To Reproduce**
Steps to reproduce the behavior:
1. Go to 'A's Farming Shop'
2. Click on the shop twice in quick succession
**Expected behavior**
The shop can't be closed even if you walk away.
**Screenshots**
**Desktop (please complete the following information):**
- OS: Windows
- Game Version 1.0.0
- Steam Version 020 | 1.0 | Shop Can't Be Closed - **Describe the bug**
A's Farming shop can't be closed
**To Reproduce**
Steps to reproduce the behavior:
1. Go to 'A's Farming Shop'
2. Click on the shop twice in quick succession
**Expected behavior**
The shop can't be closed even if you walk away.
**Screenshots**
**Desktop (please complete the following information):**
- OS: Windows
- Game Version 1.0.0
- Steam Version 020 | test | shop can t be closed describe the bug a s farming shop can t be closed to reproduce steps to reproduce the behavior go to a s farming shop click on the shop twice in quick succession expected behavior the shop can t be closed even if you walk away screenshots desktop please complete the following information os windows game version steam version | 1 |
61,479 | 7,471,331,007 | IssuesEvent | 2018-04-03 08:56:06 | rafgardom/ISPP-Makai | https://api.github.com/repos/rafgardom/ISPP-Makai | closed | No se tabula los textos muy grandes | design | Si se crea un texto muy grande y se visualiza, tienes que mover el navegador con el scrollback hacia el lado para poder ver todo el texto al completo.
Esto se puede comprobar por ejemplo cuando se visualiza una Request con una descripción muy grande.
| 1.0 | No se tabula los textos muy grandes - Si se crea un texto muy grande y se visualiza, tienes que mover el navegador con el scrollback hacia el lado para poder ver todo el texto al completo.
Esto se puede comprobar por ejemplo cuando se visualiza una Request con una descripción muy grande.
| non_test | no se tabula los textos muy grandes si se crea un texto muy grande y se visualiza tienes que mover el navegador con el scrollback hacia el lado para poder ver todo el texto al completo esto se puede comprobar por ejemplo cuando se visualiza una request con una descripción muy grande | 0 |
21,433 | 3,508,477,923 | IssuesEvent | 2016-01-08 18:02:11 | nikizkyl/z4root | https://api.github.com/repos/nikizkyl/z4root | closed | z4root download | auto-migrated Priority-Medium Type-Defect | ```
What steps will reproduce the problem?
1.
2.
3.
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Please provide any additional information below.
```
Original issue reported on code.google.com by `dennis.h...@gmail.com` on 28 Feb 2015 at 4:58 | 1.0 | z4root download - ```
What steps will reproduce the problem?
1.
2.
3.
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Please provide any additional information below.
```
Original issue reported on code.google.com by `dennis.h...@gmail.com` on 28 Feb 2015 at 4:58 | non_test | download what steps will reproduce the problem what is the expected output what do you see instead what version of the product are you using on what operating system please provide any additional information below original issue reported on code google com by dennis h gmail com on feb at | 0 |
298,142 | 25,792,906,729 | IssuesEvent | 2022-12-10 08:34:24 | notofonts/armenian | https://api.github.com/repos/notofonts/armenian | closed | Add test cases for Armenian GPOS/GSUB? | help wanted Script-Armenian TestSuite-Candidate A:Shaping | @marekjez86, in https://github.com/googlei18n/noto-fonts/pull/862#issuecomment-284557864 there was a concern that Noto Armenian may need contextual glyph substitution and positioning. Mind following up on this, and adding test cases to https://github.com/googlei18n/noto-source/tree/master/test/Armenian if needed? | 1.0 | Add test cases for Armenian GPOS/GSUB? - @marekjez86, in https://github.com/googlei18n/noto-fonts/pull/862#issuecomment-284557864 there was a concern that Noto Armenian may need contextual glyph substitution and positioning. Mind following up on this, and adding test cases to https://github.com/googlei18n/noto-source/tree/master/test/Armenian if needed? | test | add test cases for armenian gpos gsub in there was a concern that noto armenian may need contextual glyph substitution and positioning mind following up on this and adding test cases to if needed | 1 |
109,878 | 9,417,692,983 | IssuesEvent | 2019-04-10 17:21:33 | einsteinpy/einsteinpy | https://api.github.com/repos/einsteinpy/einsteinpy | closed | Remove all the unnecessary pytest.mark.parametrize | development good first issue tests | 🐞 **Problem**
Tests are currently parametrized on single set of values. `pytest.mark.parametrize` has a different essence. Remove the redundant test data from everywhere. Add pytest fixtures wherever required.
https://docs.pytest.org/en/latest/parametrize.html
🎯 **Goal**
<!--- Why is this change important to you? How would you use it? -->
<!--- How can it benefit other users? -->
💡 **Possible solutions**
<!--- Not obligatory, but suggest an idea for implementing addition or change -->
📋 **Steps to solve the problem**
* Comment below about what you've started working on.
* Add, commit, push your changes
* Submit a pull request and add this in comments - `Addresses #<put issue number here>`
* Ask for a review in comments section of pull request
* Celebrate your contribution to this project 🎉
| 1.0 | Remove all the unnecessary pytest.mark.parametrize - 🐞 **Problem**
Tests are currently parametrized on single set of values. `pytest.mark.parametrize` has a different essence. Remove the redundant test data from everywhere. Add pytest fixtures wherever required.
https://docs.pytest.org/en/latest/parametrize.html
🎯 **Goal**
<!--- Why is this change important to you? How would you use it? -->
<!--- How can it benefit other users? -->
💡 **Possible solutions**
<!--- Not obligatory, but suggest an idea for implementing addition or change -->
📋 **Steps to solve the problem**
* Comment below about what you've started working on.
* Add, commit, push your changes
* Submit a pull request and add this in comments - `Addresses #<put issue number here>`
* Ask for a review in comments section of pull request
* Celebrate your contribution to this project 🎉
| test | remove all the unnecessary pytest mark parametrize 🐞 problem tests are currently parametrized on single set of values pytest mark parametrize has a different essence remove the redundant test data from everywhere add pytest fixtures wherever required 🎯 goal 💡 possible solutions 📋 steps to solve the problem comment below about what you ve started working on add commit push your changes submit a pull request and add this in comments addresses ask for a review in comments section of pull request celebrate your contribution to this project 🎉 | 1 |
150,393 | 11,958,843,627 | IssuesEvent | 2020-04-04 19:36:19 | sqlalchemy/sqlalchemy | https://api.github.com/repos/sqlalchemy/sqlalchemy | opened | ComputedReflectionFixtureTest causes errors for dialects without schemas | bug tests | Current fixture assumes schema support. Discovered during testing re:
https://github.com/pauldex/sqlalchemy-firebird/issues/4 | 1.0 | ComputedReflectionFixtureTest causes errors for dialects without schemas - Current fixture assumes schema support. Discovered during testing re:
https://github.com/pauldex/sqlalchemy-firebird/issues/4 | test | computedreflectionfixturetest causes errors for dialects without schemas current fixture assumes schema support discovered during testing re | 1 |
33,291 | 14,046,221,810 | IssuesEvent | 2020-11-02 04:02:19 | vmware/singleton | https://api.github.com/repos/vmware/singleton | opened | [BUG] [Service]Add a switch for configuration (source.collect.locales) | area/service kind/bug priority/high | **Describe the bug**
A configuration item (source.collect.locales) is configured to define the locale of source collection.
Please add a switch to control this configuration.
**Expected behavior**
Add a switch for this configuraiton item.
| 1.0 | [BUG] [Service]Add a switch for configuration (source.collect.locales) - **Describe the bug**
A configuration item (source.collect.locales) is configured to define the locale of source collection.
Please add a switch to control this configuration.
**Expected behavior**
Add a switch for this configuraiton item.
| non_test | add a switch for configuration source collect locales describe the bug a configuration item source collect locales is configured to define the locale of source collection please add a switch to control this configuration expected behavior add a switch for this configuraiton item | 0 |
12,262 | 3,593,720,850 | IssuesEvent | 2016-02-01 20:49:13 | haffo/hit-iz-tool | https://api.github.com/repos/haffo/hit-iz-tool | closed | NIST Clarifications and Validation Guidelines Update | Documentation | Harold, please use the attached document for the release today.
[NIST-Clarifications-and-Validation-Guidelines.docx](https://github.com/haffo/hit-iz-tool/files/100847/NIST-Clarifications-and-Validation-Guidelines.docx)
| 1.0 | NIST Clarifications and Validation Guidelines Update - Harold, please use the attached document for the release today.
[NIST-Clarifications-and-Validation-Guidelines.docx](https://github.com/haffo/hit-iz-tool/files/100847/NIST-Clarifications-and-Validation-Guidelines.docx)
| non_test | nist clarifications and validation guidelines update harold please use the attached document for the release today | 0 |
372,791 | 11,028,288,391 | IssuesEvent | 2019-12-06 11:18:53 | balena-io/balena-supervisor | https://api.github.com/repos/balena-io/balena-supervisor | opened | The supervisor should throttle state endpoint patches | High priority | Currently (especially when downloading) the supervisor can hit the api fairly often. We should add a throttle to avoid hitting it so quickly and reduce bandwidth. | 1.0 | The supervisor should throttle state endpoint patches - Currently (especially when downloading) the supervisor can hit the api fairly often. We should add a throttle to avoid hitting it so quickly and reduce bandwidth. | non_test | the supervisor should throttle state endpoint patches currently especially when downloading the supervisor can hit the api fairly often we should add a throttle to avoid hitting it so quickly and reduce bandwidth | 0 |
117,443 | 9,935,426,063 | IssuesEvent | 2019-07-02 16:30:58 | rancher/rancher | https://api.github.com/repos/rancher/rancher | closed | Cluster with already expired certs shows an alert that it has expiring certs | [zube]: To Test area/ui kind/bug-qa team/az | **What kind of request is this (question/bug/enhancement/feature request):** bug
**Steps to reproduce (least amount of steps as possible):**
Have a cluster(DO cluster-3 nodes) in v2.2.4 - with custom image, giving 30 minutes of expiry for the cluster.
Upgrade to v2.2-head with UI tag 2.2.81.
Warning shown on the UI - This cluster has certs expiring in 30 days or less. Please rotate your certificates now.
Wait for the cluster to expire.
**Expected Result:**
The alert can be made to show a message stating the cluster has **expired** certs
**Actual Result:**
Alert shown on the UI - `This cluster has certs expiring in 30 days or less. Please rotate your certificates now.`
<img width="1088" alt="Screen Shot 2019-06-27 at 10 07 04 AM" src="https://user-images.githubusercontent.com/26032343/60288348-de2ec900-98c8-11e9-9625-e150606aa4e4.png">
**Other details that may be helpful:**
**Environment information**
- Rancher version (`rancher/rancher`/`rancher/server` image tag or shown bottom left in the UI): v2.2-head with UI tag `2.2.81`
- Installation option (single install/HA): single
<!--
If the reported issue is regarding a created cluster, please provide requested info below
-->
**Cluster information**
- Cluster type (Hosted/Infrastructure Provider/Custom/Imported): do
- Kubernetes version (use `kubectl version`):
```
1.13
```
| 1.0 | Cluster with already expired certs shows an alert that it has expiring certs - **What kind of request is this (question/bug/enhancement/feature request):** bug
**Steps to reproduce (least amount of steps as possible):**
Have a cluster(DO cluster-3 nodes) in v2.2.4 - with custom image, giving 30 minutes of expiry for the cluster.
Upgrade to v2.2-head with UI tag 2.2.81.
Warning shown on the UI - This cluster has certs expiring in 30 days or less. Please rotate your certificates now.
Wait for the cluster to expire.
**Expected Result:**
The alert can be made to show a message stating the cluster has **expired** certs
**Actual Result:**
Alert shown on the UI - `This cluster has certs expiring in 30 days or less. Please rotate your certificates now.`
<img width="1088" alt="Screen Shot 2019-06-27 at 10 07 04 AM" src="https://user-images.githubusercontent.com/26032343/60288348-de2ec900-98c8-11e9-9625-e150606aa4e4.png">
**Other details that may be helpful:**
**Environment information**
- Rancher version (`rancher/rancher`/`rancher/server` image tag or shown bottom left in the UI): v2.2-head with UI tag `2.2.81`
- Installation option (single install/HA): single
<!--
If the reported issue is regarding a created cluster, please provide requested info below
-->
**Cluster information**
- Cluster type (Hosted/Infrastructure Provider/Custom/Imported): do
- Kubernetes version (use `kubectl version`):
```
1.13
```
| test | cluster with already expired certs shows an alert that it has expiring certs what kind of request is this question bug enhancement feature request bug steps to reproduce least amount of steps as possible have a cluster do cluster nodes in with custom image giving minutes of expiry for the cluster upgrade to head with ui tag warning shown on the ui this cluster has certs expiring in days or less please rotate your certificates now wait for the cluster to expire expected result the alert can be made to show a message stating the cluster has expired certs actual result alert shown on the ui this cluster has certs expiring in days or less please rotate your certificates now img width alt screen shot at am src other details that may be helpful environment information rancher version rancher rancher rancher server image tag or shown bottom left in the ui head with ui tag installation option single install ha single if the reported issue is regarding a created cluster please provide requested info below cluster information cluster type hosted infrastructure provider custom imported do kubernetes version use kubectl version | 1 |
13,023 | 8,068,484,586 | IssuesEvent | 2018-08-05 21:03:21 | DedSecInside/TorBot | https://api.github.com/repos/DedSecInside/TorBot | closed | Switch to Twisted from requests | ENHANCEMENT MAJOR UPGRADE PERFORMANCE URGENT | We're currently using requests, which is a synchronous HTTP library. One of our features, which retrieves links and tests if the link is reachable via HTTP/HTTPS is extremely slow due to this. Switching to Twisted, which is asynchronous should provide a speed up as well as give us the ability to take advantage of the async nature of Twisted. | True | Switch to Twisted from requests - We're currently using requests, which is a synchronous HTTP library. One of our features, which retrieves links and tests if the link is reachable via HTTP/HTTPS is extremely slow due to this. Switching to Twisted, which is asynchronous should provide a speed up as well as give us the ability to take advantage of the async nature of Twisted. | non_test | switch to twisted from requests we re currently using requests which is a synchronous http library one of our features which retrieves links and tests if the link is reachable via http https is extremely slow due to this switching to twisted which is asynchronous should provide a speed up as well as give us the ability to take advantage of the async nature of twisted | 0 |
31,331 | 13,494,919,825 | IssuesEvent | 2020-09-11 22:30:52 | cityofaustin/atd-data-tech | https://api.github.com/repos/cityofaustin/atd-data-tech | opened | [RPP Back Office] Update and Re-Import Customer Spreadsheets | Product: Residential Parking Permit Digitization Service: Apps Type: Data Workgroup: PE | Reformat Customer Import Spreadsheets w/ notes, updated format, and catching data errors
- [ ] Blue
- [ ] Green
- [ ] Orange
- [ ] Pink
- [ ] Purple
- [ ] Red
- [ ] Teal
Import new Customer Spreadsheets with missing or corrected data
- [ ] Blue
- [ ] Green
- [ ] Orange
- [ ] Pink
- [ ] Purple
- [ ] Red
- [ ] Teal | 1.0 | [RPP Back Office] Update and Re-Import Customer Spreadsheets - Reformat Customer Import Spreadsheets w/ notes, updated format, and catching data errors
- [ ] Blue
- [ ] Green
- [ ] Orange
- [ ] Pink
- [ ] Purple
- [ ] Red
- [ ] Teal
Import new Customer Spreadsheets with missing or corrected data
- [ ] Blue
- [ ] Green
- [ ] Orange
- [ ] Pink
- [ ] Purple
- [ ] Red
- [ ] Teal | non_test | update and re import customer spreadsheets reformat customer import spreadsheets w notes updated format and catching data errors blue green orange pink purple red teal import new customer spreadsheets with missing or corrected data blue green orange pink purple red teal | 0 |
12,728 | 9,935,837,144 | IssuesEvent | 2019-07-02 17:33:43 | dart-lang/sdk | https://api.github.com/repos/dart-lang/sdk | closed | Pub hangs and is unkillable on windows | area-infrastructure os-windows p2-medium type-bug | The pub get command that is run for each package, is slow, and timing out. All of these pub get commands are remaining alive, and slow down the system, making all future ones time out too. We get about 50 unkillable pub processes running.
| 1.0 | Pub hangs and is unkillable on windows - The pub get command that is run for each package, is slow, and timing out. All of these pub get commands are remaining alive, and slow down the system, making all future ones time out too. We get about 50 unkillable pub processes running.
| non_test | pub hangs and is unkillable on windows the pub get command that is run for each package is slow and timing out all of these pub get commands are remaining alive and slow down the system making all future ones time out too we get about unkillable pub processes running | 0 |
811,783 | 30,299,842,648 | IssuesEvent | 2023-07-10 04:30:32 | gperftools/gperftools | https://api.github.com/repos/gperftools/gperftools | closed | can't compile google-perftools on AIX6.1 | Priority-Medium Type-Porting Status-New | Originally reported on Google Code with ID 419
```
the following is the issue:
1.downloaded gperftools-2.0.tar.gz from http://code.google.com/p/gperftools/downloads/list
which is updated as Feb 3rd
2.run configure after unzip and unpack, no error produced
3.run gmake and get errors which I put in the attachment gmake.log.zip
os: AIX 6.1 TL6
gcc: 4.4.6
the config.log and config.h are also i attached.
```
Reported by `happysalay` on 2012-03-18 08:04:30
<hr>
- _Attachment: [config.h.zip](https://storage.googleapis.com/google-code-attachments/gperftools/issue-419/comment-0/config.h.zip)_
- _Attachment: [config.log.zip](https://storage.googleapis.com/google-code-attachments/gperftools/issue-419/comment-0/config.log.zip)_
- _Attachment: [gmake.log.zip](https://storage.googleapis.com/google-code-attachments/gperftools/issue-419/comment-0/gmake.log.zip)_
| 1.0 | can't compile google-perftools on AIX6.1 - Originally reported on Google Code with ID 419
```
the following is the issue:
1.downloaded gperftools-2.0.tar.gz from http://code.google.com/p/gperftools/downloads/list
which is updated as Feb 3rd
2.run configure after unzip and unpack, no error produced
3.run gmake and get errors which I put in the attachment gmake.log.zip
os: AIX 6.1 TL6
gcc: 4.4.6
the config.log and config.h are also i attached.
```
Reported by `happysalay` on 2012-03-18 08:04:30
<hr>
- _Attachment: [config.h.zip](https://storage.googleapis.com/google-code-attachments/gperftools/issue-419/comment-0/config.h.zip)_
- _Attachment: [config.log.zip](https://storage.googleapis.com/google-code-attachments/gperftools/issue-419/comment-0/config.log.zip)_
- _Attachment: [gmake.log.zip](https://storage.googleapis.com/google-code-attachments/gperftools/issue-419/comment-0/gmake.log.zip)_
| non_test | can t compile google perftools on originally reported on google code with id the following is the issue downloaded gperftools tar gz from which is updated as feb run configure after unzip and unpack no error produced run gmake and get errors which i put in the attachment gmake log zip os aix gcc the config log and config h are also i attached reported by happysalay on attachment attachment attachment | 0 |
15,434 | 11,502,992,918 | IssuesEvent | 2020-02-12 20:11:10 | patternfly/patternfly-react | https://api.github.com/repos/patternfly/patternfly-react | closed | implement full clean target | infrastructure | List of files/dirs that the clean target should remove when called.
➜ patternfly-next git:(feat/size-report) git clean -ndfx
Would remove .cache/
Would remove .circleci/css-size-report/node_modules/
Would remove .circleci/css-size-report/package-lock.json
Would remove .circleci/css-size-report/report.html
Would remove .vscode/
Would remove allure-report/
Would remove coverage/
Would remove dist/
Would remove node_modules/
Would remove public/
Would remove src/icons/PfIcons/
Would remove static/assets/fontawesome/
Would remove static/assets/fonts/
Would remove static/assets/pficon/
Would remove workspace/ | 1.0 | implement full clean target - List of files/dirs that the clean target should remove when called.
➜ patternfly-next git:(feat/size-report) git clean -ndfx
Would remove .cache/
Would remove .circleci/css-size-report/node_modules/
Would remove .circleci/css-size-report/package-lock.json
Would remove .circleci/css-size-report/report.html
Would remove .vscode/
Would remove allure-report/
Would remove coverage/
Would remove dist/
Would remove node_modules/
Would remove public/
Would remove src/icons/PfIcons/
Would remove static/assets/fontawesome/
Would remove static/assets/fonts/
Would remove static/assets/pficon/
Would remove workspace/ | non_test | implement full clean target list of files dirs that the clean target should remove when called ➜ patternfly next git feat size report git clean ndfx would remove cache would remove circleci css size report node modules would remove circleci css size report package lock json would remove circleci css size report report html would remove vscode would remove allure report would remove coverage would remove dist would remove node modules would remove public would remove src icons pficons would remove static assets fontawesome would remove static assets fonts would remove static assets pficon would remove workspace | 0 |
780,968 | 27,416,622,449 | IssuesEvent | 2023-03-01 14:11:57 | brave/brave-browser | https://api.github.com/repos/brave/brave-browser | closed | Anr in rewards JSON Sanitize | crash feature/rewards priority/P2 QA/No release-notes/include OS/Android ANR | I found that crash stack in GPS in 1.48.160. We can try to move that task in the background thread as I don't see anything why it is in the main thread currently.
```
RELADDR FUNCTION FILE:LINE
000000000005c070 syscall+28 /apex/com.android.runtime/lib/bionic/libc.so
000000000014a873 art::ConditionVariable::WaitHoldingLocks(art::Thread*)+82 /apex/com.android.art/lib/libart.so
00000000002de46d art::JNI<false>::NewString(_JNIEnv*, unsigned short const*, int)+396 /apex/com.android.art/lib/libart.so
v------> _JNIEnv::NewString(unsigned short const*, int) ../../third_party/android_ndk/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/include/jni.h:828:14
v------> (anonymous namespace)::ConvertUTF16ToJavaStringImpl(_JNIEnv*, base::BasicStringPiece<char16_t, std::Cr::char_traits<char16_t>> const&) ../../base/android/jni_string.cc:17:25
00000000025f6079 base::android::ConvertUTF8ToJavaString(_JNIEnv*, base::BasicStringPiece<char, std::Cr::char_traits<char>> const&) ../../base/android/jni_string.cc:75:43
0000000001ba53bb data_decoder::JsonSanitizer::Sanitize(std::Cr::basic_string<char, std::Cr::char_traits<char>, std::Cr::allocator<char>> const&, base::OnceCallback<void (data_decoder::JsonSanitizer::Result)>) ../../services/data_decoder/public/cpp/json_sanitizer_android.cc:47:7
00000000044d2191 brave_rewards::RewardsServiceImpl::OnURLLoaderComplete(std::Cr::__list_iterator<std::Cr::unique_ptr<network::SimpleURLLoader, std::Cr::default_delete<network::SimpleURLLoader>>, void*>, base::OnceCallback<void (ledger::mojom::UrlResponse const&)>, std::Cr::unique_ptr<std::Cr::basic_string<char, std::Cr::char_traits<char>, std::Cr::allocator<char>>, std::Cr::default_delete<std::Cr::basic_string<char, std::Cr::char_traits<char>, std::Cr::allocator<char>>>>) ../../brave/components/brave_rewards/browser/rewards_service_impl.cc:1195:12
0000000001ae68b1 base::OnceCallback<void (std::Cr::unique_ptr<std::Cr::basic_string<char, std::Cr::char_traits<char>, std::Cr::allocator<char>>, std::Cr::default_delete<std::Cr::basic_string<char, std::Cr::char_traits<char>, std::Cr::allocator<char>>>>)>::Run(std::Cr::unique_ptr<std::Cr::basic_string<char, std::Cr::char_traits<char>, std::Cr::allocator<char>>, std::Cr::default_delete<std::Cr::basic_string<char, std::Cr::char_traits<char>, std::Cr::allocator<char>>>>) && ../../base/functional/callback.h:152:12
0000000002d7306b network::(anonymous namespace)::SimpleURLLoaderImpl::FinishWithResult(int) ../../services/network/public/cpp/simple_url_loader.cc:1630:18
00000000012ea44f network::mojom::URLLoaderClientStubDispatch::Accept(network::mojom::URLLoaderClient*, mojo::Message*) gen/services/network/public/mojom/url_loader.mojom.cc:1289:13
v------> mojo::InterfaceEndpointClient::HandleValidatedMessage(mojo::Message*) ../../mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:1007:54
000000000276d11b mojo::InterfaceEndpointClient::HandleIncomingMessageThunk::Accept(mojo::Message*) ../../mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:357:18
000000000276f4b3 mojo::MessageDispatcher::Accept(mojo::Message*) ../../mojo/public/cpp/bindings/lib/message_dispatcher.cc:43:19
000000000276df69 mojo::InterfaceEndpointClient::HandleIncomingMessage(mojo::Message*) ../../mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:694:20
0000000002770ab9 mojo::internal::MultiplexRouter::ProcessIncomingMessage(mojo::internal::MultiplexRouter::MessageWrapper*, mojo::internal::MultiplexRouter::ClientCallBehavior, base::SequencedTaskRunner*) ../../mojo/public/cpp/bindings/lib/multiplex_router.cc:1096:42
00000000027707f5 mojo::internal::MultiplexRouter::Accept(mojo::Message*) ../../mojo/public/cpp/bindings/lib/multiplex_router.cc:710:7
000000000276f4b3 mojo::MessageDispatcher::Accept(mojo::Message*) ../../mojo/public/cpp/bindings/lib/message_dispatcher.cc:43:19
000000000276baef mojo::Connector::DispatchMessage(mojo::ScopedHandleBase<mojo::MessageHandle>) ../../mojo/public/cpp/bindings/lib/connector.cc:542:49
000000000276bf23 mojo::Connector::ReadAllAvailableMessages() ../../mojo/public/cpp/bindings/lib/connector.cc:599:14
v------> base::OnceCallback<void ()>::Run() && ../../base/functional/callback.h:152:12
00000000025b76ad base::TaskAnnotator::RunTaskImpl(base::PendingTask&) ../../base/task/common/task_annotator.cc:157:32
v------> void base::TaskAnnotator::RunTask<base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl(base::LazyNow*)::$_0>(perfetto::StaticString, base::PendingTask&, base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl(base::LazyNow*)::$_0&&) ../../base/task/common/task_annotator.h:85:5
v------> base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl(base::LazyNow*) ../../base/task/sequence_manager/thread_controller_with_message_pump_impl.cc:484:23
00000000025c3a15 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork() ../../base/task/sequence_manager/thread_controller_with_message_pump_impl.cc:335:30
00000000025c4009 non-virtual thunk to base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork() ../../base/task/sequence_manager/thread_controller_with_message_pump_impl.cc:0:0
00000000025e6d01 base::MessagePumpForUI::DoNonDelayedLooperWork(bool) ../../base/message_loop/message_pump_android.cc:285:33
v------> base::MessagePumpForUI::OnNonDelayedLooperCallback() ../../base/message_loop/message_pump_android.cc:271:3
00000000025e6865 base::(anonymous namespace)::NonDelayedLooperCallback(int, int, void*) ../../base/message_loop/message_pump_android.cc:75:9
00000000000102dd android::Looper::pollInner(int)+692 /system/lib/libutils.so
000000000000ffcf android::Looper::pollOnce(int, int*, int*, void**)+62 /system/lib/libutils.so
00000000000e0c6b android::android_os_MessageQueue_nativePollOnce(_JNIEnv*, _jobject*, long long, int)+24 /system/lib/libandroid_runtime.so
``` | 1.0 | Anr in rewards JSON Sanitize - I found that crash stack in GPS in 1.48.160. We can try to move that task in the background thread as I don't see anything why it is in the main thread currently.
```
RELADDR FUNCTION FILE:LINE
000000000005c070 syscall+28 /apex/com.android.runtime/lib/bionic/libc.so
000000000014a873 art::ConditionVariable::WaitHoldingLocks(art::Thread*)+82 /apex/com.android.art/lib/libart.so
00000000002de46d art::JNI<false>::NewString(_JNIEnv*, unsigned short const*, int)+396 /apex/com.android.art/lib/libart.so
v------> _JNIEnv::NewString(unsigned short const*, int) ../../third_party/android_ndk/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/include/jni.h:828:14
v------> (anonymous namespace)::ConvertUTF16ToJavaStringImpl(_JNIEnv*, base::BasicStringPiece<char16_t, std::Cr::char_traits<char16_t>> const&) ../../base/android/jni_string.cc:17:25
00000000025f6079 base::android::ConvertUTF8ToJavaString(_JNIEnv*, base::BasicStringPiece<char, std::Cr::char_traits<char>> const&) ../../base/android/jni_string.cc:75:43
0000000001ba53bb data_decoder::JsonSanitizer::Sanitize(std::Cr::basic_string<char, std::Cr::char_traits<char>, std::Cr::allocator<char>> const&, base::OnceCallback<void (data_decoder::JsonSanitizer::Result)>) ../../services/data_decoder/public/cpp/json_sanitizer_android.cc:47:7
00000000044d2191 brave_rewards::RewardsServiceImpl::OnURLLoaderComplete(std::Cr::__list_iterator<std::Cr::unique_ptr<network::SimpleURLLoader, std::Cr::default_delete<network::SimpleURLLoader>>, void*>, base::OnceCallback<void (ledger::mojom::UrlResponse const&)>, std::Cr::unique_ptr<std::Cr::basic_string<char, std::Cr::char_traits<char>, std::Cr::allocator<char>>, std::Cr::default_delete<std::Cr::basic_string<char, std::Cr::char_traits<char>, std::Cr::allocator<char>>>>) ../../brave/components/brave_rewards/browser/rewards_service_impl.cc:1195:12
0000000001ae68b1 base::OnceCallback<void (std::Cr::unique_ptr<std::Cr::basic_string<char, std::Cr::char_traits<char>, std::Cr::allocator<char>>, std::Cr::default_delete<std::Cr::basic_string<char, std::Cr::char_traits<char>, std::Cr::allocator<char>>>>)>::Run(std::Cr::unique_ptr<std::Cr::basic_string<char, std::Cr::char_traits<char>, std::Cr::allocator<char>>, std::Cr::default_delete<std::Cr::basic_string<char, std::Cr::char_traits<char>, std::Cr::allocator<char>>>>) && ../../base/functional/callback.h:152:12
0000000002d7306b network::(anonymous namespace)::SimpleURLLoaderImpl::FinishWithResult(int) ../../services/network/public/cpp/simple_url_loader.cc:1630:18
00000000012ea44f network::mojom::URLLoaderClientStubDispatch::Accept(network::mojom::URLLoaderClient*, mojo::Message*) gen/services/network/public/mojom/url_loader.mojom.cc:1289:13
v------> mojo::InterfaceEndpointClient::HandleValidatedMessage(mojo::Message*) ../../mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:1007:54
000000000276d11b mojo::InterfaceEndpointClient::HandleIncomingMessageThunk::Accept(mojo::Message*) ../../mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:357:18
000000000276f4b3 mojo::MessageDispatcher::Accept(mojo::Message*) ../../mojo/public/cpp/bindings/lib/message_dispatcher.cc:43:19
000000000276df69 mojo::InterfaceEndpointClient::HandleIncomingMessage(mojo::Message*) ../../mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:694:20
0000000002770ab9 mojo::internal::MultiplexRouter::ProcessIncomingMessage(mojo::internal::MultiplexRouter::MessageWrapper*, mojo::internal::MultiplexRouter::ClientCallBehavior, base::SequencedTaskRunner*) ../../mojo/public/cpp/bindings/lib/multiplex_router.cc:1096:42
00000000027707f5 mojo::internal::MultiplexRouter::Accept(mojo::Message*) ../../mojo/public/cpp/bindings/lib/multiplex_router.cc:710:7
000000000276f4b3 mojo::MessageDispatcher::Accept(mojo::Message*) ../../mojo/public/cpp/bindings/lib/message_dispatcher.cc:43:19
000000000276baef mojo::Connector::DispatchMessage(mojo::ScopedHandleBase<mojo::MessageHandle>) ../../mojo/public/cpp/bindings/lib/connector.cc:542:49
000000000276bf23 mojo::Connector::ReadAllAvailableMessages() ../../mojo/public/cpp/bindings/lib/connector.cc:599:14
v------> base::OnceCallback<void ()>::Run() && ../../base/functional/callback.h:152:12
00000000025b76ad base::TaskAnnotator::RunTaskImpl(base::PendingTask&) ../../base/task/common/task_annotator.cc:157:32
v------> void base::TaskAnnotator::RunTask<base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl(base::LazyNow*)::$_0>(perfetto::StaticString, base::PendingTask&, base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl(base::LazyNow*)::$_0&&) ../../base/task/common/task_annotator.h:85:5
v------> base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl(base::LazyNow*) ../../base/task/sequence_manager/thread_controller_with_message_pump_impl.cc:484:23
00000000025c3a15 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork() ../../base/task/sequence_manager/thread_controller_with_message_pump_impl.cc:335:30
00000000025c4009 non-virtual thunk to base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork() ../../base/task/sequence_manager/thread_controller_with_message_pump_impl.cc:0:0
00000000025e6d01 base::MessagePumpForUI::DoNonDelayedLooperWork(bool) ../../base/message_loop/message_pump_android.cc:285:33
v------> base::MessagePumpForUI::OnNonDelayedLooperCallback() ../../base/message_loop/message_pump_android.cc:271:3
00000000025e6865 base::(anonymous namespace)::NonDelayedLooperCallback(int, int, void*) ../../base/message_loop/message_pump_android.cc:75:9
00000000000102dd android::Looper::pollInner(int)+692 /system/lib/libutils.so
000000000000ffcf android::Looper::pollOnce(int, int*, int*, void**)+62 /system/lib/libutils.so
00000000000e0c6b android::android_os_MessageQueue_nativePollOnce(_JNIEnv*, _jobject*, long long, int)+24 /system/lib/libandroid_runtime.so
``` | non_test | anr in rewards json sanitize i found that crash stack in gps in we can try to move that task in the background thread as i don t see anything why it is in the main thread currently reladdr function file line syscall apex com android runtime lib bionic libc so art conditionvariable waitholdinglocks art thread apex com android art lib libart so art jni newstring jnienv unsigned short const int apex com android art lib libart so v jnienv newstring unsigned short const int third party android ndk toolchains llvm prebuilt linux sysroot usr include jni h v anonymous namespace jnienv base basicstringpiece const base android jni string cc base android jnienv base basicstringpiece const base android jni string cc data decoder jsonsanitizer sanitize std cr basic string std cr allocator const base oncecallback services data decoder public cpp json sanitizer android cc brave rewards rewardsserviceimpl onurlloadercomplete std cr list iterator void base oncecallback std cr unique ptr std cr allocator std cr default delete std cr allocator brave components brave rewards browser rewards service impl cc base oncecallback std cr allocator std cr default delete std cr allocator run std cr unique ptr std cr allocator std cr default delete std cr allocator base functional callback h network anonymous namespace simpleurlloaderimpl finishwithresult int services network public cpp simple url loader cc network mojom urlloaderclientstubdispatch accept network mojom urlloaderclient mojo message gen services network public mojom url loader mojom cc v mojo interfaceendpointclient handlevalidatedmessage mojo message mojo public cpp bindings lib interface endpoint client cc mojo interfaceendpointclient handleincomingmessagethunk accept mojo message mojo public cpp bindings lib interface endpoint client cc mojo messagedispatcher accept mojo message mojo public cpp bindings lib message dispatcher cc mojo interfaceendpointclient handleincomingmessage mojo message mojo public cpp bindings lib interface endpoint client cc mojo internal multiplexrouter processincomingmessage mojo internal multiplexrouter messagewrapper mojo internal multiplexrouter clientcallbehavior base sequencedtaskrunner mojo public cpp bindings lib multiplex router cc mojo internal multiplexrouter accept mojo message mojo public cpp bindings lib multiplex router cc mojo messagedispatcher accept mojo message mojo public cpp bindings lib message dispatcher cc mojo connector dispatchmessage mojo scopedhandlebase mojo public cpp bindings lib connector cc mojo connector readallavailablemessages mojo public cpp bindings lib connector cc v base oncecallback run base functional callback h base taskannotator runtaskimpl base pendingtask base task common task annotator cc v void base taskannotator runtask perfetto staticstring base pendingtask base sequence manager internal threadcontrollerwithmessagepumpimpl doworkimpl base lazynow base task common task annotator h v base sequence manager internal threadcontrollerwithmessagepumpimpl doworkimpl base lazynow base task sequence manager thread controller with message pump impl cc base sequence manager internal threadcontrollerwithmessagepumpimpl dowork base task sequence manager thread controller with message pump impl cc non virtual thunk to base sequence manager internal threadcontrollerwithmessagepumpimpl dowork base task sequence manager thread controller with message pump impl cc base messagepumpforui donondelayedlooperwork bool base message loop message pump android cc v base messagepumpforui onnondelayedloopercallback base message loop message pump android cc base anonymous namespace nondelayedloopercallback int int void base message loop message pump android cc android looper pollinner int system lib libutils so android looper pollonce int int int void system lib libutils so android android os messagequeue nativepollonce jnienv jobject long long int system lib libandroid runtime so | 0 |
293,475 | 25,295,872,452 | IssuesEvent | 2022-11-17 06:34:50 | lowRISC/opentitan | https://api.github.com/repos/lowRISC/opentitan | closed | [test-triage] chip_sw_alert_handler_sleep_mode_pings | Component:TestTriage | ### Hierarchy of regression failure
Chip Level
### Failure Description
```
UVM_ERROR @ * us: (sw_logger_if.sv:522) [alert_handler_lpg_sleep_mode_pings_test_prog_sim_dv(sw/device/tests/alert_handler_lpg_sleep_mode_pings.c:447)] CHECK-fail: Phase #*: No new alerts has been fired after wakeup! has 1 failures:
Test chip_sw_alert_handler_lpg_sleep_mode_pings has 1 failures.
0.chip_sw_alert_handler_lpg_sleep_mode_pings.4264109033
Line 523, in log /container/opentitan-public/scratch/os_regression/chip_earlgrey_asic-sim-vcs/0.chip_sw_alert_handler_lpg_sleep_mode_pings/latest/run.log
UVM_ERROR @ 16636.958198 us: (sw_logger_if.sv:522) [alert_handler_lpg_sleep_mode_pings_test_prog_sim_dv(sw/device/tests/alert_handler_lpg_sleep_mode_pings.c:447)] CHECK-fail: Phase #2: No new alerts has been fired after wakeup!
UVM_INFO @ 16636.958198 us: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER]
--- UVM Report catcher Summary ---
```
This is related to PR #16062. It seems there was a problem with a few lines of the C code. Trying a fix on my local environment. Running with `reseed: 10` to make sure I get %100 coverage.
I will submit a new PR and update the issue.
### Steps to Reproduce
./util/dvsim/dvsim.py hw/top_earlgrey/dv/chip_sim_cfg.hjson -i chip_sw_alert_handler_lpg_sleep_mode_pings --waves fsdb
### Tests with similar or related failures
_No response_ | 1.0 | [test-triage] chip_sw_alert_handler_sleep_mode_pings - ### Hierarchy of regression failure
Chip Level
### Failure Description
```
UVM_ERROR @ * us: (sw_logger_if.sv:522) [alert_handler_lpg_sleep_mode_pings_test_prog_sim_dv(sw/device/tests/alert_handler_lpg_sleep_mode_pings.c:447)] CHECK-fail: Phase #*: No new alerts has been fired after wakeup! has 1 failures:
Test chip_sw_alert_handler_lpg_sleep_mode_pings has 1 failures.
0.chip_sw_alert_handler_lpg_sleep_mode_pings.4264109033
Line 523, in log /container/opentitan-public/scratch/os_regression/chip_earlgrey_asic-sim-vcs/0.chip_sw_alert_handler_lpg_sleep_mode_pings/latest/run.log
UVM_ERROR @ 16636.958198 us: (sw_logger_if.sv:522) [alert_handler_lpg_sleep_mode_pings_test_prog_sim_dv(sw/device/tests/alert_handler_lpg_sleep_mode_pings.c:447)] CHECK-fail: Phase #2: No new alerts has been fired after wakeup!
UVM_INFO @ 16636.958198 us: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER]
--- UVM Report catcher Summary ---
```
This is related to PR #16062. It seems there was a problem with a few lines of the C code. Trying a fix on my local environment. Running with `reseed: 10` to make sure I get %100 coverage.
I will submit a new PR and update the issue.
### Steps to Reproduce
./util/dvsim/dvsim.py hw/top_earlgrey/dv/chip_sim_cfg.hjson -i chip_sw_alert_handler_lpg_sleep_mode_pings --waves fsdb
### Tests with similar or related failures
_No response_ | test | chip sw alert handler sleep mode pings hierarchy of regression failure chip level failure description uvm error us sw logger if sv check fail phase no new alerts has been fired after wakeup has failures test chip sw alert handler lpg sleep mode pings has failures chip sw alert handler lpg sleep mode pings line in log container opentitan public scratch os regression chip earlgrey asic sim vcs chip sw alert handler lpg sleep mode pings latest run log uvm error us sw logger if sv check fail phase no new alerts has been fired after wakeup uvm info us uvm report catcher svh uvm report catcher summary this is related to pr it seems there was a problem with a few lines of the c code trying a fix on my local environment running with reseed to make sure i get coverage i will submit a new pr and update the issue steps to reproduce util dvsim dvsim py hw top earlgrey dv chip sim cfg hjson i chip sw alert handler lpg sleep mode pings waves fsdb tests with similar or related failures no response | 1 |
236,392 | 26,009,787,282 | IssuesEvent | 2022-12-20 23:47:35 | pferronMend/Case106160 | https://api.github.com/repos/pferronMend/Case106160 | opened | spring-boot-starter-cache-2.7.1.jar: 7 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>spring-boot-starter-cache-2.7.1.jar</b></p></summary>
<p></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/pferronMend/Case106160/commit/a030b9f00a71bb93777301cdeaa112613cc6f32c">a030b9f00a71bb93777301cdeaa112613cc6f32c</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (spring-boot-starter-cache version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-1471](https://www.mend.io/vulnerability-database/CVE-2022-1471) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | snakeyaml-1.30.jar | Transitive | N/A* | ❌ |
| [CVE-2022-25857](https://www.mend.io/vulnerability-database/CVE-2022-25857) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | snakeyaml-1.30.jar | Transitive | N/A* | ❌ |
| [CVE-2022-41854](https://www.mend.io/vulnerability-database/CVE-2022-41854) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | snakeyaml-1.30.jar | Transitive | N/A* | ❌ |
| [CVE-2022-38749](https://www.mend.io/vulnerability-database/CVE-2022-38749) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | snakeyaml-1.30.jar | Transitive | N/A* | ❌ |
| [CVE-2022-38752](https://www.mend.io/vulnerability-database/CVE-2022-38752) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | snakeyaml-1.30.jar | Transitive | N/A* | ❌ |
| [CVE-2022-38751](https://www.mend.io/vulnerability-database/CVE-2022-38751) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | snakeyaml-1.30.jar | Transitive | N/A* | ❌ |
| [CVE-2022-38750](https://www.mend.io/vulnerability-database/CVE-2022-38750) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.5 | snakeyaml-1.30.jar | Transitive | N/A* | ❌ |
<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-2022-1471</summary>
### Vulnerable Library - <b>snakeyaml-1.30.jar</b></p>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="https://bitbucket.org/snakeyaml/snakeyaml">https://bitbucket.org/snakeyaml/snakeyaml</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-cache-2.7.1.jar (Root Library)
- spring-boot-starter-2.7.1.jar
- :x: **snakeyaml-1.30.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/pferronMend/Case106160/commit/a030b9f00a71bb93777301cdeaa112613cc6f32c">a030b9f00a71bb93777301cdeaa112613cc6f32c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
SnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization. Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using SnakeYaml's SafeConsturctor when parsing untrusted content to restrict deserialization.
<p>Publish Date: 2022-12-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-1471>CVE-2022-1471</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://nvd.nist.gov/vuln/detail/CVE-2022-1471">https://nvd.nist.gov/vuln/detail/CVE-2022-1471</a></p>
<p>Release Date: 2022-12-01</p>
<p>Fix Resolution: org.yaml:snakeyaml - 1.31</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-25857</summary>
### Vulnerable Library - <b>snakeyaml-1.30.jar</b></p>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="https://bitbucket.org/snakeyaml/snakeyaml">https://bitbucket.org/snakeyaml/snakeyaml</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-cache-2.7.1.jar (Root Library)
- spring-boot-starter-2.7.1.jar
- :x: **snakeyaml-1.30.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/pferronMend/Case106160/commit/a030b9f00a71bb93777301cdeaa112613cc6f32c">a030b9f00a71bb93777301cdeaa112613cc6f32c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The package org.yaml:snakeyaml from 0 and before 1.31 are vulnerable to Denial of Service (DoS) due missing to nested depth limitation for collections.
<p>Publish Date: 2022-08-30
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-25857>CVE-2022-25857</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-2022-25857">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25857</a></p>
<p>Release Date: 2022-08-30</p>
<p>Fix Resolution: org.yaml:snakeyaml:1.31</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-41854</summary>
### Vulnerable Library - <b>snakeyaml-1.30.jar</b></p>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="https://bitbucket.org/snakeyaml/snakeyaml">https://bitbucket.org/snakeyaml/snakeyaml</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-cache-2.7.1.jar (Root Library)
- spring-boot-starter-2.7.1.jar
- :x: **snakeyaml-1.30.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/pferronMend/Case106160/commit/a030b9f00a71bb93777301cdeaa112613cc6f32c">a030b9f00a71bb93777301cdeaa112613cc6f32c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Those using Snakeyaml to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stack overflow. This effect may support a denial of service attack.
<p>Publish Date: 2022-11-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-41854>CVE-2022-41854</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- 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://bitbucket.org/snakeyaml/snakeyaml/issues/531/">https://bitbucket.org/snakeyaml/snakeyaml/issues/531/</a></p>
<p>Release Date: 2022-11-11</p>
<p>Fix Resolution: org.yaml:snakeyaml:1.32</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-38749</summary>
### Vulnerable Library - <b>snakeyaml-1.30.jar</b></p>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="https://bitbucket.org/snakeyaml/snakeyaml">https://bitbucket.org/snakeyaml/snakeyaml</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-cache-2.7.1.jar (Root Library)
- spring-boot-starter-2.7.1.jar
- :x: **snakeyaml-1.30.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/pferronMend/Case106160/commit/a030b9f00a71bb93777301cdeaa112613cc6f32c">a030b9f00a71bb93777301cdeaa112613cc6f32c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
<p>Publish Date: 2022-09-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-38749>CVE-2022-38749</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bitbucket.org/snakeyaml/snakeyaml/issues/526/stackoverflow-oss-fuzz-47027">https://bitbucket.org/snakeyaml/snakeyaml/issues/526/stackoverflow-oss-fuzz-47027</a></p>
<p>Release Date: 2022-09-05</p>
<p>Fix Resolution: org.yaml:snakeyaml:1.31</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-38752</summary>
### Vulnerable Library - <b>snakeyaml-1.30.jar</b></p>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="https://bitbucket.org/snakeyaml/snakeyaml">https://bitbucket.org/snakeyaml/snakeyaml</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-cache-2.7.1.jar (Root Library)
- spring-boot-starter-2.7.1.jar
- :x: **snakeyaml-1.30.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/pferronMend/Case106160/commit/a030b9f00a71bb93777301cdeaa112613cc6f32c">a030b9f00a71bb93777301cdeaa112613cc6f32c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stack-overflow.
<p>Publish Date: 2022-09-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-38752>CVE-2022-38752</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-9w3m-gqgf-c4p9">https://github.com/advisories/GHSA-9w3m-gqgf-c4p9</a></p>
<p>Release Date: 2022-09-05</p>
<p>Fix Resolution: org.yaml:snakeyaml:1.32
</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-38751</summary>
### Vulnerable Library - <b>snakeyaml-1.30.jar</b></p>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="https://bitbucket.org/snakeyaml/snakeyaml">https://bitbucket.org/snakeyaml/snakeyaml</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-cache-2.7.1.jar (Root Library)
- spring-boot-starter-2.7.1.jar
- :x: **snakeyaml-1.30.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/pferronMend/Case106160/commit/a030b9f00a71bb93777301cdeaa112613cc6f32c">a030b9f00a71bb93777301cdeaa112613cc6f32c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
<p>Publish Date: 2022-09-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-38751>CVE-2022-38751</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47039">https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47039</a></p>
<p>Release Date: 2022-09-05</p>
<p>Fix Resolution: org.yaml:snakeyaml:1.31</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-38750</summary>
### Vulnerable Library - <b>snakeyaml-1.30.jar</b></p>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="https://bitbucket.org/snakeyaml/snakeyaml">https://bitbucket.org/snakeyaml/snakeyaml</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-cache-2.7.1.jar (Root Library)
- spring-boot-starter-2.7.1.jar
- :x: **snakeyaml-1.30.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/pferronMend/Case106160/commit/a030b9f00a71bb93777301cdeaa112613cc6f32c">a030b9f00a71bb93777301cdeaa112613cc6f32c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
<p>Publish Date: 2022-09-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-38750>CVE-2022-38750</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- 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://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47027">https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47027</a></p>
<p>Release Date: 2022-09-05</p>
<p>Fix Resolution: org.yaml:snakeyaml:1.31</p>
</p>
<p></p>
</details> | True | spring-boot-starter-cache-2.7.1.jar: 7 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>spring-boot-starter-cache-2.7.1.jar</b></p></summary>
<p></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/pferronMend/Case106160/commit/a030b9f00a71bb93777301cdeaa112613cc6f32c">a030b9f00a71bb93777301cdeaa112613cc6f32c</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (spring-boot-starter-cache version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-1471](https://www.mend.io/vulnerability-database/CVE-2022-1471) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | snakeyaml-1.30.jar | Transitive | N/A* | ❌ |
| [CVE-2022-25857](https://www.mend.io/vulnerability-database/CVE-2022-25857) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | snakeyaml-1.30.jar | Transitive | N/A* | ❌ |
| [CVE-2022-41854](https://www.mend.io/vulnerability-database/CVE-2022-41854) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | snakeyaml-1.30.jar | Transitive | N/A* | ❌ |
| [CVE-2022-38749](https://www.mend.io/vulnerability-database/CVE-2022-38749) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | snakeyaml-1.30.jar | Transitive | N/A* | ❌ |
| [CVE-2022-38752](https://www.mend.io/vulnerability-database/CVE-2022-38752) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | snakeyaml-1.30.jar | Transitive | N/A* | ❌ |
| [CVE-2022-38751](https://www.mend.io/vulnerability-database/CVE-2022-38751) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | snakeyaml-1.30.jar | Transitive | N/A* | ❌ |
| [CVE-2022-38750](https://www.mend.io/vulnerability-database/CVE-2022-38750) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.5 | snakeyaml-1.30.jar | Transitive | N/A* | ❌ |
<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-2022-1471</summary>
### Vulnerable Library - <b>snakeyaml-1.30.jar</b></p>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="https://bitbucket.org/snakeyaml/snakeyaml">https://bitbucket.org/snakeyaml/snakeyaml</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-cache-2.7.1.jar (Root Library)
- spring-boot-starter-2.7.1.jar
- :x: **snakeyaml-1.30.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/pferronMend/Case106160/commit/a030b9f00a71bb93777301cdeaa112613cc6f32c">a030b9f00a71bb93777301cdeaa112613cc6f32c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
SnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization. Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using SnakeYaml's SafeConsturctor when parsing untrusted content to restrict deserialization.
<p>Publish Date: 2022-12-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-1471>CVE-2022-1471</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://nvd.nist.gov/vuln/detail/CVE-2022-1471">https://nvd.nist.gov/vuln/detail/CVE-2022-1471</a></p>
<p>Release Date: 2022-12-01</p>
<p>Fix Resolution: org.yaml:snakeyaml - 1.31</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-25857</summary>
### Vulnerable Library - <b>snakeyaml-1.30.jar</b></p>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="https://bitbucket.org/snakeyaml/snakeyaml">https://bitbucket.org/snakeyaml/snakeyaml</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-cache-2.7.1.jar (Root Library)
- spring-boot-starter-2.7.1.jar
- :x: **snakeyaml-1.30.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/pferronMend/Case106160/commit/a030b9f00a71bb93777301cdeaa112613cc6f32c">a030b9f00a71bb93777301cdeaa112613cc6f32c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The package org.yaml:snakeyaml from 0 and before 1.31 are vulnerable to Denial of Service (DoS) due missing to nested depth limitation for collections.
<p>Publish Date: 2022-08-30
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-25857>CVE-2022-25857</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-2022-25857">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25857</a></p>
<p>Release Date: 2022-08-30</p>
<p>Fix Resolution: org.yaml:snakeyaml:1.31</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-41854</summary>
### Vulnerable Library - <b>snakeyaml-1.30.jar</b></p>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="https://bitbucket.org/snakeyaml/snakeyaml">https://bitbucket.org/snakeyaml/snakeyaml</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-cache-2.7.1.jar (Root Library)
- spring-boot-starter-2.7.1.jar
- :x: **snakeyaml-1.30.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/pferronMend/Case106160/commit/a030b9f00a71bb93777301cdeaa112613cc6f32c">a030b9f00a71bb93777301cdeaa112613cc6f32c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Those using Snakeyaml to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stack overflow. This effect may support a denial of service attack.
<p>Publish Date: 2022-11-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-41854>CVE-2022-41854</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- 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://bitbucket.org/snakeyaml/snakeyaml/issues/531/">https://bitbucket.org/snakeyaml/snakeyaml/issues/531/</a></p>
<p>Release Date: 2022-11-11</p>
<p>Fix Resolution: org.yaml:snakeyaml:1.32</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-38749</summary>
### Vulnerable Library - <b>snakeyaml-1.30.jar</b></p>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="https://bitbucket.org/snakeyaml/snakeyaml">https://bitbucket.org/snakeyaml/snakeyaml</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-cache-2.7.1.jar (Root Library)
- spring-boot-starter-2.7.1.jar
- :x: **snakeyaml-1.30.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/pferronMend/Case106160/commit/a030b9f00a71bb93777301cdeaa112613cc6f32c">a030b9f00a71bb93777301cdeaa112613cc6f32c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
<p>Publish Date: 2022-09-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-38749>CVE-2022-38749</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bitbucket.org/snakeyaml/snakeyaml/issues/526/stackoverflow-oss-fuzz-47027">https://bitbucket.org/snakeyaml/snakeyaml/issues/526/stackoverflow-oss-fuzz-47027</a></p>
<p>Release Date: 2022-09-05</p>
<p>Fix Resolution: org.yaml:snakeyaml:1.31</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-38752</summary>
### Vulnerable Library - <b>snakeyaml-1.30.jar</b></p>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="https://bitbucket.org/snakeyaml/snakeyaml">https://bitbucket.org/snakeyaml/snakeyaml</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-cache-2.7.1.jar (Root Library)
- spring-boot-starter-2.7.1.jar
- :x: **snakeyaml-1.30.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/pferronMend/Case106160/commit/a030b9f00a71bb93777301cdeaa112613cc6f32c">a030b9f00a71bb93777301cdeaa112613cc6f32c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stack-overflow.
<p>Publish Date: 2022-09-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-38752>CVE-2022-38752</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-9w3m-gqgf-c4p9">https://github.com/advisories/GHSA-9w3m-gqgf-c4p9</a></p>
<p>Release Date: 2022-09-05</p>
<p>Fix Resolution: org.yaml:snakeyaml:1.32
</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-38751</summary>
### Vulnerable Library - <b>snakeyaml-1.30.jar</b></p>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="https://bitbucket.org/snakeyaml/snakeyaml">https://bitbucket.org/snakeyaml/snakeyaml</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-cache-2.7.1.jar (Root Library)
- spring-boot-starter-2.7.1.jar
- :x: **snakeyaml-1.30.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/pferronMend/Case106160/commit/a030b9f00a71bb93777301cdeaa112613cc6f32c">a030b9f00a71bb93777301cdeaa112613cc6f32c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
<p>Publish Date: 2022-09-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-38751>CVE-2022-38751</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47039">https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47039</a></p>
<p>Release Date: 2022-09-05</p>
<p>Fix Resolution: org.yaml:snakeyaml:1.31</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-38750</summary>
### Vulnerable Library - <b>snakeyaml-1.30.jar</b></p>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="https://bitbucket.org/snakeyaml/snakeyaml">https://bitbucket.org/snakeyaml/snakeyaml</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-cache-2.7.1.jar (Root Library)
- spring-boot-starter-2.7.1.jar
- :x: **snakeyaml-1.30.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/pferronMend/Case106160/commit/a030b9f00a71bb93777301cdeaa112613cc6f32c">a030b9f00a71bb93777301cdeaa112613cc6f32c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
<p>Publish Date: 2022-09-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-38750>CVE-2022-38750</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- 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://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47027">https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47027</a></p>
<p>Release Date: 2022-09-05</p>
<p>Fix Resolution: org.yaml:snakeyaml:1.31</p>
</p>
<p></p>
</details> | non_test | spring boot starter cache jar vulnerabilities highest severity is vulnerable library spring boot starter cache jar path to dependency file pom xml path to vulnerable library home wss scanner repository org yaml snakeyaml snakeyaml jar found in head commit a href vulnerabilities cve severity cvss dependency type fixed in spring boot starter cache version remediation available high snakeyaml jar transitive n a high snakeyaml jar transitive n a medium snakeyaml jar transitive n a medium snakeyaml jar transitive n a medium snakeyaml jar transitive n a medium snakeyaml jar transitive n a medium snakeyaml jar transitive n a 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 library snakeyaml jar yaml parser and emitter for java library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org yaml snakeyaml snakeyaml jar dependency hierarchy spring boot starter cache jar root library spring boot starter jar x snakeyaml jar vulnerable library found in head commit a href found in base branch main vulnerability details snakeyaml s constructor class does not restrict types which can be instantiated during deserialization deserializing yaml content provided by an attacker can lead to remote code execution we recommend using snakeyaml s safeconsturctor when parsing untrusted content to restrict deserialization publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org yaml snakeyaml cve vulnerable library snakeyaml jar yaml parser and emitter for java library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org yaml snakeyaml snakeyaml jar dependency hierarchy spring boot starter cache jar root library spring boot starter jar x snakeyaml jar vulnerable library found in head commit a href found in base branch main vulnerability details the package org yaml snakeyaml from and before are vulnerable to denial of service dos due missing to nested depth limitation for collections publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org yaml snakeyaml cve vulnerable library snakeyaml jar yaml parser and emitter for java library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org yaml snakeyaml snakeyaml jar dependency hierarchy spring boot starter cache jar root library spring boot starter jar x snakeyaml jar vulnerable library found in head commit a href found in base branch main vulnerability details those using snakeyaml to parse untrusted yaml files may be vulnerable to denial of service attacks dos if the parser is running on user supplied input an attacker may supply content that causes the parser to crash by stack overflow this effect may support a denial of service attack publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org yaml snakeyaml cve vulnerable library snakeyaml jar yaml parser and emitter for java library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org yaml snakeyaml snakeyaml jar dependency hierarchy spring boot starter cache jar root library spring boot starter jar x snakeyaml jar vulnerable library found in head commit a href found in base branch main vulnerability details using snakeyaml to parse untrusted yaml files may be vulnerable to denial of service attacks dos if the parser is running on user supplied input an attacker may supply content that causes the parser to crash by stackoverflow publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org yaml snakeyaml cve vulnerable library snakeyaml jar yaml parser and emitter for java library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org yaml snakeyaml snakeyaml jar dependency hierarchy spring boot starter cache jar root library spring boot starter jar x snakeyaml jar vulnerable library found in head commit a href found in base branch main vulnerability details using snakeyaml to parse untrusted yaml files may be vulnerable to denial of service attacks dos if the parser is running on user supplied input an attacker may supply content that causes the parser to crash by stack overflow publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org yaml snakeyaml cve vulnerable library snakeyaml jar yaml parser and emitter for java library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org yaml snakeyaml snakeyaml jar dependency hierarchy spring boot starter cache jar root library spring boot starter jar x snakeyaml jar vulnerable library found in head commit a href found in base branch main vulnerability details using snakeyaml to parse untrusted yaml files may be vulnerable to denial of service attacks dos if the parser is running on user supplied input an attacker may supply content that causes the parser to crash by stackoverflow publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org yaml snakeyaml cve vulnerable library snakeyaml jar yaml parser and emitter for java library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org yaml snakeyaml snakeyaml jar dependency hierarchy spring boot starter cache jar root library spring boot starter jar x snakeyaml jar vulnerable library found in head commit a href found in base branch main vulnerability details using snakeyaml to parse untrusted yaml files may be vulnerable to denial of service attacks dos if the parser is running on user supplied input an attacker may supply content that causes the parser to crash by stackoverflow 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 unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org yaml snakeyaml | 0 |
276,601 | 30,501,731,610 | IssuesEvent | 2023-07-18 14:20:40 | JoshRMendDemo/NoWhitesource | https://api.github.com/repos/JoshRMendDemo/NoWhitesource | opened | slf4j-log4j12-1.5.0.jar: 8 vulnerabilities (highest severity is: 9.8) | Mend: dependency security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>slf4j-log4j12-1.5.0.jar</b></p></summary>
<p></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.13/log4j-1.2.13.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/JoshRMendDemo/NoWhitesource/commit/11ccb995e003d01120a68be0d160ddf5d2809abf">11ccb995e003d01120a68be0d160ddf5d2809abf</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (slf4j-log4j12 version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-23305](https://www.mend.io/vulnerability-database/CVE-2022-23305) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | log4j-1.2.13.jar | Transitive | N/A* | ❌ |
| [CVE-2019-17571](https://www.mend.io/vulnerability-database/CVE-2019-17571) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | log4j-1.2.13.jar | Transitive | N/A* | ❌ |
| [CVE-2020-9493](https://www.mend.io/vulnerability-database/CVE-2020-9493) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | log4j-1.2.13.jar | Transitive | N/A* | ❌ |
| [CVE-2022-23307](https://www.mend.io/vulnerability-database/CVE-2022-23307) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.8 | log4j-1.2.13.jar | Transitive | N/A* | ❌ |
| [CVE-2022-23302](https://www.mend.io/vulnerability-database/CVE-2022-23302) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.8 | log4j-1.2.13.jar | Transitive | N/A* | ❌ |
| [CVE-2021-4104](https://www.mend.io/vulnerability-database/CVE-2021-4104) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | log4j-1.2.13.jar | Transitive | N/A* | ❌ |
| [CVE-2023-26464](https://www.mend.io/vulnerability-database/CVE-2023-26464) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | log4j-1.2.13.jar | Transitive | N/A* | ❌ |
| [CVE-2020-9488](https://www.mend.io/vulnerability-database/CVE-2020-9488) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> Low | 3.7 | log4j-1.2.13.jar | Transitive | N/A* | ❌ |
<p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> CVE-2022-23305</summary>
### Vulnerable Library - <b>log4j-1.2.13.jar</b></p>
<p>Log4j</p>
<p>Library home page: <a href="http://logging.apache.org/log4j/">http://logging.apache.org/log4j/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.13/log4j-1.2.13.jar</p>
<p>
Dependency Hierarchy:
- slf4j-log4j12-1.5.0.jar (Root Library)
- :x: **log4j-1.2.13.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/JoshRMendDemo/NoWhitesource/commit/11ccb995e003d01120a68be0d160ddf5d2809abf">11ccb995e003d01120a68be0d160ddf5d2809abf</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
<p>Publish Date: 2022-01-18
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23305>CVE-2022-23305</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://reload4j.qos.ch/">https://reload4j.qos.ch/</a></p>
<p>Release Date: 2022-01-18</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.2</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> CVE-2019-17571</summary>
### Vulnerable Library - <b>log4j-1.2.13.jar</b></p>
<p>Log4j</p>
<p>Library home page: <a href="http://logging.apache.org/log4j/">http://logging.apache.org/log4j/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.13/log4j-1.2.13.jar</p>
<p>
Dependency Hierarchy:
- slf4j-log4j12-1.5.0.jar (Root Library)
- :x: **log4j-1.2.13.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/JoshRMendDemo/NoWhitesource/commit/11ccb995e003d01120a68be0d160ddf5d2809abf">11ccb995e003d01120a68be0d160ddf5d2809abf</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.
<p>Publish Date: 2019-12-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-17571>CVE-2019-17571</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://lists.apache.org/thread.html/eea03d504b36e8f870e8321d908e1def1addda16adda04327fe7c125%40%3Cdev.logging.apache.org%3E">https://lists.apache.org/thread.html/eea03d504b36e8f870e8321d908e1def1addda16adda04327fe7c125%40%3Cdev.logging.apache.org%3E</a></p>
<p>Release Date: 2019-12-20</p>
<p>Fix Resolution: log4j-manual - 1.2.17-16;log4j-javadoc - 1.2.17-16;log4j - 1.2.17-16,1.2.17-16</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> CVE-2020-9493</summary>
### Vulnerable Library - <b>log4j-1.2.13.jar</b></p>
<p>Log4j</p>
<p>Library home page: <a href="http://logging.apache.org/log4j/">http://logging.apache.org/log4j/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.13/log4j-1.2.13.jar</p>
<p>
Dependency Hierarchy:
- slf4j-log4j12-1.5.0.jar (Root Library)
- :x: **log4j-1.2.13.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/JoshRMendDemo/NoWhitesource/commit/11ccb995e003d01120a68be0d160ddf5d2809abf">11ccb995e003d01120a68be0d160ddf5d2809abf</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A deserialization flaw was found in Apache Chainsaw versions prior to 2.1.0 which could lead to malicious code execution.
<p>Publish Date: 2021-06-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-9493>CVE-2020-9493</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.openwall.com/lists/oss-security/2021/06/16/1">https://www.openwall.com/lists/oss-security/2021/06/16/1</a></p>
<p>Release Date: 2021-06-16</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2022-23307</summary>
### Vulnerable Library - <b>log4j-1.2.13.jar</b></p>
<p>Log4j</p>
<p>Library home page: <a href="http://logging.apache.org/log4j/">http://logging.apache.org/log4j/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.13/log4j-1.2.13.jar</p>
<p>
Dependency Hierarchy:
- slf4j-log4j12-1.5.0.jar (Root Library)
- :x: **log4j-1.2.13.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/JoshRMendDemo/NoWhitesource/commit/11ccb995e003d01120a68be0d160ddf5d2809abf">11ccb995e003d01120a68be0d160ddf5d2809abf</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists.
<p>Publish Date: 2022-01-18
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23307>CVE-2022-23307</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-01-18</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2022-23302</summary>
### Vulnerable Library - <b>log4j-1.2.13.jar</b></p>
<p>Log4j</p>
<p>Library home page: <a href="http://logging.apache.org/log4j/">http://logging.apache.org/log4j/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.13/log4j-1.2.13.jar</p>
<p>
Dependency Hierarchy:
- slf4j-log4j12-1.5.0.jar (Root Library)
- :x: **log4j-1.2.13.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/JoshRMendDemo/NoWhitesource/commit/11ccb995e003d01120a68be0d160ddf5d2809abf">11ccb995e003d01120a68be0d160ddf5d2809abf</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
<p>Publish Date: 2022-01-18
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23302>CVE-2022-23302</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://reload4j.qos.ch/">https://reload4j.qos.ch/</a></p>
<p>Release Date: 2022-01-18</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2021-4104</summary>
### Vulnerable Library - <b>log4j-1.2.13.jar</b></p>
<p>Log4j</p>
<p>Library home page: <a href="http://logging.apache.org/log4j/">http://logging.apache.org/log4j/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.13/log4j-1.2.13.jar</p>
<p>
Dependency Hierarchy:
- slf4j-log4j12-1.5.0.jar (Root Library)
- :x: **log4j-1.2.13.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/JoshRMendDemo/NoWhitesource/commit/11ccb995e003d01120a68be0d160ddf5d2809abf">11ccb995e003d01120a68be0d160ddf5d2809abf</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
<p>Publish Date: 2021-12-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-4104>CVE-2021-4104</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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://nvd.nist.gov/vuln/detail/CVE-2021-4104">https://nvd.nist.gov/vuln/detail/CVE-2021-4104</a></p>
<p>Release Date: 2021-12-14</p>
<p>Fix Resolution: uom-parent - 1.0.3-3.module,1.0.3-3.module;uom-se-javadoc - 1.0.4-3.module;parfait-examples - 0.5.4-4.module;log4j-manual - 1.2.17-16;si-units-javadoc - 0.6.5-2.module;unit-api - 1.0-5.module,1.0-5.module;unit-api-javadoc - 1.0-5.module;parfait - 0.5.4-4.module,0.5.4-4.module;log4j-javadoc - 1.2.17-16;uom-systems-javadoc - 0.7-1.module;uom-lib-javadoc - 1.0.1-6.module;uom-systems - 0.7-1.module,0.7-1.module;log4j - 1.2.17-16,1.2.17-16;uom-se - 1.0.4-3.module,1.0.4-3.module;uom-lib - 1.0.1-6.module,1.0.1-6.module;parfait-javadoc - 0.5.4-4.module;pcp-parfait-agent - 0.5.4-4.module;si-units - 0.6.5-2.module,0.6.5-2.module</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2023-26464</summary>
### Vulnerable Library - <b>log4j-1.2.13.jar</b></p>
<p>Log4j</p>
<p>Library home page: <a href="http://logging.apache.org/log4j/">http://logging.apache.org/log4j/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.13/log4j-1.2.13.jar</p>
<p>
Dependency Hierarchy:
- slf4j-log4j12-1.5.0.jar (Root Library)
- :x: **log4j-1.2.13.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/JoshRMendDemo/NoWhitesource/commit/11ccb995e003d01120a68be0d160ddf5d2809abf">11ccb995e003d01120a68be0d160ddf5d2809abf</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
** UNSUPPORTED WHEN ASSIGNED **
When using the Chainsaw or SocketAppender components with Log4j 1.x on JRE less than 1.7, an attacker that manages to cause a logging entry involving a specially-crafted (ie, deeply nested)
hashmap or hashtable (depending on which logging component is in use) to be processed could exhaust the available memory in the virtual machine and achieve Denial of Service when the object is deserialized.
This issue affects Apache Log4j before 2. Affected users are recommended to update to Log4j 2.x.
NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
<p>Publish Date: 2023-03-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-26464>CVE-2023-26464</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-vp98-w2p3-mv35">https://github.com/advisories/GHSA-vp98-w2p3-mv35</a></p>
<p>Release Date: 2023-03-10</p>
<p>Fix Resolution: org.apache.logging.log4j:log4j-core:2.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> CVE-2020-9488</summary>
### Vulnerable Library - <b>log4j-1.2.13.jar</b></p>
<p>Log4j</p>
<p>Library home page: <a href="http://logging.apache.org/log4j/">http://logging.apache.org/log4j/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.13/log4j-1.2.13.jar</p>
<p>
Dependency Hierarchy:
- slf4j-log4j12-1.5.0.jar (Root Library)
- :x: **log4j-1.2.13.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/JoshRMendDemo/NoWhitesource/commit/11ccb995e003d01120a68be0d160ddf5d2809abf">11ccb995e003d01120a68be0d160ddf5d2809abf</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender. Fixed in Apache Log4j 2.12.3 and 2.13.1
<p>Publish Date: 2020-04-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-9488>CVE-2020-9488</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>3.7</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://reload4j.qos.ch/">https://reload4j.qos.ch/</a></p>
<p>Release Date: 2020-04-27</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.3</p>
</p>
<p></p>
</details> | True | slf4j-log4j12-1.5.0.jar: 8 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>slf4j-log4j12-1.5.0.jar</b></p></summary>
<p></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.13/log4j-1.2.13.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/JoshRMendDemo/NoWhitesource/commit/11ccb995e003d01120a68be0d160ddf5d2809abf">11ccb995e003d01120a68be0d160ddf5d2809abf</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (slf4j-log4j12 version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-23305](https://www.mend.io/vulnerability-database/CVE-2022-23305) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | log4j-1.2.13.jar | Transitive | N/A* | ❌ |
| [CVE-2019-17571](https://www.mend.io/vulnerability-database/CVE-2019-17571) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | log4j-1.2.13.jar | Transitive | N/A* | ❌ |
| [CVE-2020-9493](https://www.mend.io/vulnerability-database/CVE-2020-9493) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | log4j-1.2.13.jar | Transitive | N/A* | ❌ |
| [CVE-2022-23307](https://www.mend.io/vulnerability-database/CVE-2022-23307) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.8 | log4j-1.2.13.jar | Transitive | N/A* | ❌ |
| [CVE-2022-23302](https://www.mend.io/vulnerability-database/CVE-2022-23302) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.8 | log4j-1.2.13.jar | Transitive | N/A* | ❌ |
| [CVE-2021-4104](https://www.mend.io/vulnerability-database/CVE-2021-4104) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | log4j-1.2.13.jar | Transitive | N/A* | ❌ |
| [CVE-2023-26464](https://www.mend.io/vulnerability-database/CVE-2023-26464) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | log4j-1.2.13.jar | Transitive | N/A* | ❌ |
| [CVE-2020-9488](https://www.mend.io/vulnerability-database/CVE-2020-9488) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> Low | 3.7 | log4j-1.2.13.jar | Transitive | N/A* | ❌ |
<p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> CVE-2022-23305</summary>
### Vulnerable Library - <b>log4j-1.2.13.jar</b></p>
<p>Log4j</p>
<p>Library home page: <a href="http://logging.apache.org/log4j/">http://logging.apache.org/log4j/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.13/log4j-1.2.13.jar</p>
<p>
Dependency Hierarchy:
- slf4j-log4j12-1.5.0.jar (Root Library)
- :x: **log4j-1.2.13.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/JoshRMendDemo/NoWhitesource/commit/11ccb995e003d01120a68be0d160ddf5d2809abf">11ccb995e003d01120a68be0d160ddf5d2809abf</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
<p>Publish Date: 2022-01-18
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23305>CVE-2022-23305</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://reload4j.qos.ch/">https://reload4j.qos.ch/</a></p>
<p>Release Date: 2022-01-18</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.2</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> CVE-2019-17571</summary>
### Vulnerable Library - <b>log4j-1.2.13.jar</b></p>
<p>Log4j</p>
<p>Library home page: <a href="http://logging.apache.org/log4j/">http://logging.apache.org/log4j/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.13/log4j-1.2.13.jar</p>
<p>
Dependency Hierarchy:
- slf4j-log4j12-1.5.0.jar (Root Library)
- :x: **log4j-1.2.13.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/JoshRMendDemo/NoWhitesource/commit/11ccb995e003d01120a68be0d160ddf5d2809abf">11ccb995e003d01120a68be0d160ddf5d2809abf</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.
<p>Publish Date: 2019-12-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-17571>CVE-2019-17571</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://lists.apache.org/thread.html/eea03d504b36e8f870e8321d908e1def1addda16adda04327fe7c125%40%3Cdev.logging.apache.org%3E">https://lists.apache.org/thread.html/eea03d504b36e8f870e8321d908e1def1addda16adda04327fe7c125%40%3Cdev.logging.apache.org%3E</a></p>
<p>Release Date: 2019-12-20</p>
<p>Fix Resolution: log4j-manual - 1.2.17-16;log4j-javadoc - 1.2.17-16;log4j - 1.2.17-16,1.2.17-16</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> CVE-2020-9493</summary>
### Vulnerable Library - <b>log4j-1.2.13.jar</b></p>
<p>Log4j</p>
<p>Library home page: <a href="http://logging.apache.org/log4j/">http://logging.apache.org/log4j/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.13/log4j-1.2.13.jar</p>
<p>
Dependency Hierarchy:
- slf4j-log4j12-1.5.0.jar (Root Library)
- :x: **log4j-1.2.13.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/JoshRMendDemo/NoWhitesource/commit/11ccb995e003d01120a68be0d160ddf5d2809abf">11ccb995e003d01120a68be0d160ddf5d2809abf</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A deserialization flaw was found in Apache Chainsaw versions prior to 2.1.0 which could lead to malicious code execution.
<p>Publish Date: 2021-06-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-9493>CVE-2020-9493</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.openwall.com/lists/oss-security/2021/06/16/1">https://www.openwall.com/lists/oss-security/2021/06/16/1</a></p>
<p>Release Date: 2021-06-16</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2022-23307</summary>
### Vulnerable Library - <b>log4j-1.2.13.jar</b></p>
<p>Log4j</p>
<p>Library home page: <a href="http://logging.apache.org/log4j/">http://logging.apache.org/log4j/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.13/log4j-1.2.13.jar</p>
<p>
Dependency Hierarchy:
- slf4j-log4j12-1.5.0.jar (Root Library)
- :x: **log4j-1.2.13.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/JoshRMendDemo/NoWhitesource/commit/11ccb995e003d01120a68be0d160ddf5d2809abf">11ccb995e003d01120a68be0d160ddf5d2809abf</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists.
<p>Publish Date: 2022-01-18
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23307>CVE-2022-23307</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-01-18</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2022-23302</summary>
### Vulnerable Library - <b>log4j-1.2.13.jar</b></p>
<p>Log4j</p>
<p>Library home page: <a href="http://logging.apache.org/log4j/">http://logging.apache.org/log4j/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.13/log4j-1.2.13.jar</p>
<p>
Dependency Hierarchy:
- slf4j-log4j12-1.5.0.jar (Root Library)
- :x: **log4j-1.2.13.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/JoshRMendDemo/NoWhitesource/commit/11ccb995e003d01120a68be0d160ddf5d2809abf">11ccb995e003d01120a68be0d160ddf5d2809abf</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
<p>Publish Date: 2022-01-18
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23302>CVE-2022-23302</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://reload4j.qos.ch/">https://reload4j.qos.ch/</a></p>
<p>Release Date: 2022-01-18</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2021-4104</summary>
### Vulnerable Library - <b>log4j-1.2.13.jar</b></p>
<p>Log4j</p>
<p>Library home page: <a href="http://logging.apache.org/log4j/">http://logging.apache.org/log4j/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.13/log4j-1.2.13.jar</p>
<p>
Dependency Hierarchy:
- slf4j-log4j12-1.5.0.jar (Root Library)
- :x: **log4j-1.2.13.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/JoshRMendDemo/NoWhitesource/commit/11ccb995e003d01120a68be0d160ddf5d2809abf">11ccb995e003d01120a68be0d160ddf5d2809abf</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
<p>Publish Date: 2021-12-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-4104>CVE-2021-4104</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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://nvd.nist.gov/vuln/detail/CVE-2021-4104">https://nvd.nist.gov/vuln/detail/CVE-2021-4104</a></p>
<p>Release Date: 2021-12-14</p>
<p>Fix Resolution: uom-parent - 1.0.3-3.module,1.0.3-3.module;uom-se-javadoc - 1.0.4-3.module;parfait-examples - 0.5.4-4.module;log4j-manual - 1.2.17-16;si-units-javadoc - 0.6.5-2.module;unit-api - 1.0-5.module,1.0-5.module;unit-api-javadoc - 1.0-5.module;parfait - 0.5.4-4.module,0.5.4-4.module;log4j-javadoc - 1.2.17-16;uom-systems-javadoc - 0.7-1.module;uom-lib-javadoc - 1.0.1-6.module;uom-systems - 0.7-1.module,0.7-1.module;log4j - 1.2.17-16,1.2.17-16;uom-se - 1.0.4-3.module,1.0.4-3.module;uom-lib - 1.0.1-6.module,1.0.1-6.module;parfait-javadoc - 0.5.4-4.module;pcp-parfait-agent - 0.5.4-4.module;si-units - 0.6.5-2.module,0.6.5-2.module</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2023-26464</summary>
### Vulnerable Library - <b>log4j-1.2.13.jar</b></p>
<p>Log4j</p>
<p>Library home page: <a href="http://logging.apache.org/log4j/">http://logging.apache.org/log4j/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.13/log4j-1.2.13.jar</p>
<p>
Dependency Hierarchy:
- slf4j-log4j12-1.5.0.jar (Root Library)
- :x: **log4j-1.2.13.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/JoshRMendDemo/NoWhitesource/commit/11ccb995e003d01120a68be0d160ddf5d2809abf">11ccb995e003d01120a68be0d160ddf5d2809abf</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
** UNSUPPORTED WHEN ASSIGNED **
When using the Chainsaw or SocketAppender components with Log4j 1.x on JRE less than 1.7, an attacker that manages to cause a logging entry involving a specially-crafted (ie, deeply nested)
hashmap or hashtable (depending on which logging component is in use) to be processed could exhaust the available memory in the virtual machine and achieve Denial of Service when the object is deserialized.
This issue affects Apache Log4j before 2. Affected users are recommended to update to Log4j 2.x.
NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
<p>Publish Date: 2023-03-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-26464>CVE-2023-26464</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-vp98-w2p3-mv35">https://github.com/advisories/GHSA-vp98-w2p3-mv35</a></p>
<p>Release Date: 2023-03-10</p>
<p>Fix Resolution: org.apache.logging.log4j:log4j-core:2.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> CVE-2020-9488</summary>
### Vulnerable Library - <b>log4j-1.2.13.jar</b></p>
<p>Log4j</p>
<p>Library home page: <a href="http://logging.apache.org/log4j/">http://logging.apache.org/log4j/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/log4j/log4j/1.2.13/log4j-1.2.13.jar</p>
<p>
Dependency Hierarchy:
- slf4j-log4j12-1.5.0.jar (Root Library)
- :x: **log4j-1.2.13.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/JoshRMendDemo/NoWhitesource/commit/11ccb995e003d01120a68be0d160ddf5d2809abf">11ccb995e003d01120a68be0d160ddf5d2809abf</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender. Fixed in Apache Log4j 2.12.3 and 2.13.1
<p>Publish Date: 2020-04-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-9488>CVE-2020-9488</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>3.7</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://reload4j.qos.ch/">https://reload4j.qos.ch/</a></p>
<p>Release Date: 2020-04-27</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.3</p>
</p>
<p></p>
</details> | non_test | jar vulnerabilities highest severity is vulnerable library jar path to dependency file pom xml path to vulnerable library home wss scanner repository jar found in head commit a href vulnerabilities cve severity cvss dependency type fixed in version remediation available critical jar transitive n a critical jar transitive n a critical jar transitive n a high jar transitive n a high jar transitive n a high jar transitive n a high jar transitive n a low jar transitive n a for some transitive vulnerabilities there is no version of direct dependency with a fix check the details section below to see if there is a version of transitive dependency where vulnerability is fixed details cve vulnerable library jar library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository jar dependency hierarchy jar root library x jar vulnerable library found in head commit a href found in base branch master vulnerability details by design the jdbcappender in x accepts an sql statement as a configuration parameter where the values to be inserted are converters from patternlayout the message converter m is likely to always be included this allows attackers to manipulate the sql by entering crafted strings into input fields or headers of an application that are logged allowing unintended sql queries to be executed note this issue only affects x when specifically configured to use the jdbcappender which is not the default beginning in version the jdbcappender was re introduced with proper support for parameterized sql queries and further customization over the columns written to in logs apache reached end of life in august users should upgrade to as it addresses numerous other issues from the previous versions 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 ch qos cve vulnerable library jar library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository jar dependency hierarchy jar root library x jar vulnerable library found in head commit a href found in base branch master vulnerability details included in is a socketserver class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data this affects versions up to up to 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 manual javadoc cve vulnerable library jar library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository jar dependency hierarchy jar root library x jar vulnerable library found in head commit a href found in base branch master vulnerability details a deserialization flaw was found in apache chainsaw versions prior to which could lead to malicious code execution publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution ch qos cve vulnerable library jar library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository jar dependency hierarchy jar root library x jar vulnerable library found in head commit a href found in base branch master vulnerability details cve identified a deserialization issue that was present in apache chainsaw prior to chainsaw chainsaw was a component of apache x where the same issue exists publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version release date fix resolution ch qos cve vulnerable library jar library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository jar dependency hierarchy jar root library x jar vulnerable library found in head commit a href found in base branch master vulnerability details jmssink in all versions of x is vulnerable to deserialization of untrusted data when the attacker has write access to the configuration or if the configuration references an ldap service the attacker has access to the attacker can provide a topicconnectionfactorybindingname configuration causing jmssink to perform jndi requests that result in remote code execution in a similar fashion to cve note this issue only affects x when specifically configured to use jmssink which is not the default apache reached end of life in august users should upgrade to as it addresses numerous other issues from the previous versions publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution ch qos cve vulnerable library jar library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository jar dependency hierarchy jar root library x jar vulnerable library found in head commit a href found in base branch master vulnerability details jmsappender in is vulnerable to deserialization of untrusted data when the attacker has write access to the configuration the attacker can provide topicbindingname and topicconnectionfactorybindingname configurations causing jmsappender to perform jndi requests that result in remote code execution in a similar fashion to cve note this issue only affects when specifically configured to use jmsappender which is not the default apache reached end of life in august users should upgrade to as it addresses numerous other issues from the previous versions publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction none scope unchanged impact metrics confidentiality impact 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 uom parent module module uom se javadoc module parfait examples module manual si units javadoc module unit api module module unit api javadoc module parfait module module javadoc uom systems javadoc module uom lib javadoc module uom systems module module uom se module module uom lib module module parfait javadoc module pcp parfait agent module si units module module cve vulnerable library jar library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository jar dependency hierarchy jar root library x jar vulnerable library found in head commit a href found in base branch master vulnerability details unsupported when assigned when using the chainsaw or socketappender components with x on jre less than an attacker that manages to cause a logging entry involving a specially crafted ie deeply nested hashmap or hashtable depending on which logging component is in use to be processed could exhaust the available memory in the virtual machine and achieve denial of service when the object is deserialized this issue affects apache before affected users are recommended to update to x note this vulnerability only affects products that are no longer supported by the maintainer publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache logging core cve vulnerable library jar library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository jar dependency hierarchy jar root library x jar vulnerable library found in head commit a href found in base branch master vulnerability details improper validation of certificate with host mismatch in apache smtp appender this could allow an smtps connection to be intercepted by a man in the middle attack which could leak any log messages sent through that appender fixed in apache and publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution ch qos | 0 |
18,279 | 24,368,616,491 | IssuesEvent | 2022-10-03 17:12:37 | fadeoutsoftware/WASDI | https://api.github.com/repos/fadeoutsoftware/WASDI | closed | add a package manager for pip | enhancement P1 javascript java UI / frontend backend python launcher app / processor | enable CRUD operations on pip environment from the web-client.
addPackage
listPackages
getPackage
removePackage
upgradePackage | 1.0 | add a package manager for pip - enable CRUD operations on pip environment from the web-client.
addPackage
listPackages
getPackage
removePackage
upgradePackage | non_test | add a package manager for pip enable crud operations on pip environment from the web client addpackage listpackages getpackage removepackage upgradepackage | 0 |
179,133 | 13,836,642,579 | IssuesEvent | 2020-10-14 01:38:00 | elastic/kibana | https://api.github.com/repos/elastic/kibana | opened | Failing test: Chrome UI Functional Tests.test/functional/apps/dashboard/dashboard_state·js - dashboard app using legacy data dashboard state Tile map with no changes will update with visualization changes | failed-test | A test failed on a tracked branch
```
Error: Expected saveVisualization to respond with the saveMessage from the toast, got
at VisualizePage.saveVisualizationExpectSuccess (test/functional/page_objects/visualize_page.ts:334:15)
```
First failure: [Jenkins Build](https://kibana-ci.elastic.co/job/elastic+kibana+master/8883/)
<!-- kibanaCiData = {"failed-test":{"test.class":"Chrome UI Functional Tests.test/functional/apps/dashboard/dashboard_state·js","test.name":"dashboard app using legacy data dashboard state Tile map with no changes will update with visualization changes","test.failCount":1}} --> | 1.0 | Failing test: Chrome UI Functional Tests.test/functional/apps/dashboard/dashboard_state·js - dashboard app using legacy data dashboard state Tile map with no changes will update with visualization changes - A test failed on a tracked branch
```
Error: Expected saveVisualization to respond with the saveMessage from the toast, got
at VisualizePage.saveVisualizationExpectSuccess (test/functional/page_objects/visualize_page.ts:334:15)
```
First failure: [Jenkins Build](https://kibana-ci.elastic.co/job/elastic+kibana+master/8883/)
<!-- kibanaCiData = {"failed-test":{"test.class":"Chrome UI Functional Tests.test/functional/apps/dashboard/dashboard_state·js","test.name":"dashboard app using legacy data dashboard state Tile map with no changes will update with visualization changes","test.failCount":1}} --> | test | failing test chrome ui functional tests test functional apps dashboard dashboard state·js dashboard app using legacy data dashboard state tile map with no changes will update with visualization changes a test failed on a tracked branch error expected savevisualization to respond with the savemessage from the toast got at visualizepage savevisualizationexpectsuccess test functional page objects visualize page ts first failure | 1 |
190,441 | 14,545,859,702 | IssuesEvent | 2020-12-15 20:18:31 | DynamoRIO/dynamorio | https://api.github.com/repos/DynamoRIO/dynamorio | opened | CRASH in histogram.offline test on Server2016 | Bug-ToolCrash Component-DrCacheSim Component-Tests Hotlist-ContinuousIntegration OpSys-Windows | First seen on Appveyor: https://github.com/DynamoRIO/dynamorio/issues/4058#issuecomment-581161162
Details:
```
[00:13:53] 230/262 Test #231: code_api|tool.histogram.offline ..............................***Failed 1.34 sec
[00:13:53] Running cmd |C:/projects/dynamorio/build/build_debug-internal-32/bin32/drrun.exe;-s;180;-quiet;-debug;-use_dll;C:/projects/dynamorio/build/build_debug-internal-32/lib32/debug/dynamorio.dll;-exit0;-stderr_mask;0xC;-msgbox_mask;0;-dumpcore_mask;0x7d;-staged;-code_api;-t;drcachesim;-offline;-subdir_prefix;tool.histogram.offline;-trace_after_instrs;5K;-exit_after_tracing;50K;--;C:/projects/dynamorio/build/build_debug-internal-32/suite/tests/bin/client.winxfer.exe|
[00:13:53] Running postcmd |C:/projects/dynamorio/build/build_debug-internal-32/clients/bin32/drcachesim.exe;-indir;C:/projects/dynamorio/build/build_debug-internal-32/suite/tests/tool.histogram.offline.client.winxfer.exe.05676.5907.dir|
[00:13:53] CMake Error at C:/projects/dynamorio/suite/tests/runmulti.cmake:106 (message):
[00:13:53] *** postcmd failed (Access violation): ***
[00:13:53]
[00:13:53] Call Stack (most recent call first):
[00:13:53] C:/projects/dynamorio/suite/tests/runmulti.cmake:118 (process_cmdline)
```
But it continues to fail on GA. | 1.0 | CRASH in histogram.offline test on Server2016 - First seen on Appveyor: https://github.com/DynamoRIO/dynamorio/issues/4058#issuecomment-581161162
Details:
```
[00:13:53] 230/262 Test #231: code_api|tool.histogram.offline ..............................***Failed 1.34 sec
[00:13:53] Running cmd |C:/projects/dynamorio/build/build_debug-internal-32/bin32/drrun.exe;-s;180;-quiet;-debug;-use_dll;C:/projects/dynamorio/build/build_debug-internal-32/lib32/debug/dynamorio.dll;-exit0;-stderr_mask;0xC;-msgbox_mask;0;-dumpcore_mask;0x7d;-staged;-code_api;-t;drcachesim;-offline;-subdir_prefix;tool.histogram.offline;-trace_after_instrs;5K;-exit_after_tracing;50K;--;C:/projects/dynamorio/build/build_debug-internal-32/suite/tests/bin/client.winxfer.exe|
[00:13:53] Running postcmd |C:/projects/dynamorio/build/build_debug-internal-32/clients/bin32/drcachesim.exe;-indir;C:/projects/dynamorio/build/build_debug-internal-32/suite/tests/tool.histogram.offline.client.winxfer.exe.05676.5907.dir|
[00:13:53] CMake Error at C:/projects/dynamorio/suite/tests/runmulti.cmake:106 (message):
[00:13:53] *** postcmd failed (Access violation): ***
[00:13:53]
[00:13:53] Call Stack (most recent call first):
[00:13:53] C:/projects/dynamorio/suite/tests/runmulti.cmake:118 (process_cmdline)
```
But it continues to fail on GA. | test | crash in histogram offline test on first seen on appveyor details test code api tool histogram offline failed sec running cmd c projects dynamorio build build debug internal drrun exe s quiet debug use dll c projects dynamorio build build debug internal debug dynamorio dll stderr mask msgbox mask dumpcore mask staged code api t drcachesim offline subdir prefix tool histogram offline trace after instrs exit after tracing c projects dynamorio build build debug internal suite tests bin client winxfer exe running postcmd c projects dynamorio build build debug internal clients drcachesim exe indir c projects dynamorio build build debug internal suite tests tool histogram offline client winxfer exe dir cmake error at c projects dynamorio suite tests runmulti cmake message postcmd failed access violation call stack most recent call first c projects dynamorio suite tests runmulti cmake process cmdline but it continues to fail on ga | 1 |
234,353 | 19,144,406,975 | IssuesEvent | 2021-12-02 05:16:19 | boostcampwm-2021/iOS06-MateRunner | https://api.github.com/repos/boostcampwm-2021/iOS06-MateRunner | closed | [단위 테스트] HomeUseCase | 여훈 test | ## 🗣 설명
- 비즈니스 로직이 정상적으로 동작하는지 확인합니다.
```swift
protocol HomeUseCase {
var authorizationStatus: BehaviorSubject<LocationAuthorizationStatus?> { get set }
var userLocation: PublishSubject<CLLocation> { get set }
init(locationService: LocationService)
func checkAuthorization()
func observeUserLocation()
func stopUpdatingLocation()
}
```
## 📋 체크리스트
> 구현해야하는 이슈 체크리스트
- [ ] 단위 테스트 작성
| 1.0 | [단위 테스트] HomeUseCase - ## 🗣 설명
- 비즈니스 로직이 정상적으로 동작하는지 확인합니다.
```swift
protocol HomeUseCase {
var authorizationStatus: BehaviorSubject<LocationAuthorizationStatus?> { get set }
var userLocation: PublishSubject<CLLocation> { get set }
init(locationService: LocationService)
func checkAuthorization()
func observeUserLocation()
func stopUpdatingLocation()
}
```
## 📋 체크리스트
> 구현해야하는 이슈 체크리스트
- [ ] 단위 테스트 작성
| test | homeusecase 🗣 설명 비즈니스 로직이 정상적으로 동작하는지 확인합니다 swift protocol homeusecase var authorizationstatus behaviorsubject get set var userlocation publishsubject get set init locationservice locationservice func checkauthorization func observeuserlocation func stopupdatinglocation 📋 체크리스트 구현해야하는 이슈 체크리스트 단위 테스트 작성 | 1 |
523,620 | 15,186,440,210 | IssuesEvent | 2021-02-15 12:23:09 | 10up/component-navigation | https://api.github.com/repos/10up/component-navigation | closed | Ability to change `sub-menu` | Priority -- Low enhancement | **Is your feature request related to a problem? Please describe.**
I noticed there is hard coded `sub-menu` class used in the nav component. Could this be part of settings so it could be changed to something else.
This would enable changing `sub-menu` class to something else that fits better for chosen naming convention.
**Describe the solution you'd like**
`sub-menu` can be default but this could be overwritten via settings.
| 1.0 | Ability to change `sub-menu` - **Is your feature request related to a problem? Please describe.**
I noticed there is hard coded `sub-menu` class used in the nav component. Could this be part of settings so it could be changed to something else.
This would enable changing `sub-menu` class to something else that fits better for chosen naming convention.
**Describe the solution you'd like**
`sub-menu` can be default but this could be overwritten via settings.
| non_test | ability to change sub menu is your feature request related to a problem please describe i noticed there is hard coded sub menu class used in the nav component could this be part of settings so it could be changed to something else this would enable changing sub menu class to something else that fits better for chosen naming convention describe the solution you d like sub menu can be default but this could be overwritten via settings | 0 |
153,000 | 12,132,547,349 | IssuesEvent | 2020-04-23 07:29:03 | kwk/test-llvm-bz-import-5 | https://api.github.com/repos/kwk/test-llvm-bz-import-5 | closed | [testsuite] Allow executing programs multiple times with different args for a single test "run" | BZ-BUG-STATUS: RESOLVED BZ-RESOLUTION: WONTFIX Test Suite/Programs Tests dummy import from bugzilla | This issue was imported from Bugzilla https://bugs.llvm.org/show_bug.cgi?id=317. | 2.0 | [testsuite] Allow executing programs multiple times with different args for a single test "run" - This issue was imported from Bugzilla https://bugs.llvm.org/show_bug.cgi?id=317. | test | allow executing programs multiple times with different args for a single test run this issue was imported from bugzilla | 1 |
563,222 | 16,677,874,756 | IssuesEvent | 2021-06-07 18:39:36 | adirh3/Fluent-Search | https://api.github.com/repos/adirh3/Fluent-Search | opened | File results showing "?" instead of icons | Medium Priority UI/UX bug | **Describe the bug**
the thumbnail/icon for the first file result appears properly, but onwards it shows a '?' icon instead of the icons of the file types [not constant]
**To Reproduce**
Steps to reproduce the behavior:
1. Type a letter that invokes many results
2. Look at the icons
3. It may not be easy to reproduce as it's not constant
**Expected behavior**
Results will show the icon depending on the file type
**Screenshots**
most of the results below are pure file formats like pdf, mp4
**Desktop (please complete the following information):**
- Windows 10 Version: [21H1]
- Fluent Search Version [0.9.85.2] (facing it from a lot earlier)
| 1.0 | File results showing "?" instead of icons - **Describe the bug**
the thumbnail/icon for the first file result appears properly, but onwards it shows a '?' icon instead of the icons of the file types [not constant]
**To Reproduce**
Steps to reproduce the behavior:
1. Type a letter that invokes many results
2. Look at the icons
3. It may not be easy to reproduce as it's not constant
**Expected behavior**
Results will show the icon depending on the file type
**Screenshots**
most of the results below are pure file formats like pdf, mp4
**Desktop (please complete the following information):**
- Windows 10 Version: [21H1]
- Fluent Search Version [0.9.85.2] (facing it from a lot earlier)
| non_test | file results showing instead of icons describe the bug the thumbnail icon for the first file result appears properly but onwards it shows a icon instead of the icons of the file types to reproduce steps to reproduce the behavior type a letter that invokes many results look at the icons it may not be easy to reproduce as it s not constant expected behavior results will show the icon depending on the file type screenshots most of the results below are pure file formats like pdf desktop please complete the following information windows version fluent search version facing it from a lot earlier | 0 |
7,912 | 11,092,325,985 | IssuesEvent | 2019-12-15 18:14:27 | Jeffail/benthos | https://api.github.com/repos/Jeffail/benthos | closed | Add new `sync_response` processor | annoying enhancement processors | It would be useful to have a `sync_response` processor that would enable more customized behaviour for pipelines containing responses. This is going to be simple to implement but we need to add extra care that it won't introduce race conditions (post-buffer alterations). | 1.0 | Add new `sync_response` processor - It would be useful to have a `sync_response` processor that would enable more customized behaviour for pipelines containing responses. This is going to be simple to implement but we need to add extra care that it won't introduce race conditions (post-buffer alterations). | non_test | add new sync response processor it would be useful to have a sync response processor that would enable more customized behaviour for pipelines containing responses this is going to be simple to implement but we need to add extra care that it won t introduce race conditions post buffer alterations | 0 |
119,715 | 10,062,043,118 | IssuesEvent | 2019-07-22 23:24:40 | rancher/rancher | https://api.github.com/repos/rancher/rancher | closed | Rancher 2 cannot add custom project role where it says it already exists | [zube]: To Test internal kind/bug team/ui | **What kind of request is this (question/bug/enhancement/feature request):**
bug
**Steps to reproduce (least amount of steps as possible):**
Create two custom project roles. Go into the project and try to give a user the lower role (before custom) in the list.
**Result:**
Either defaults to the option above it or if the user already has the option above it, it will error saying it already exits.
**Other details that may be helpful:**
These custom roles are the same as the OOTB ones with just the create namespace removed.
**Environment information**
- Rancher version (`rancher/rancher`/`rancher/server` image tag or shown bottom left in the UI):
Rancher | v2.2.2
User Interface | v2.2.41
Helm | v2.10.0-rancher10
Machine | v0.15.0-rancher6-1
- Installation option (single install/HA):
HA
| 1.0 | Rancher 2 cannot add custom project role where it says it already exists - **What kind of request is this (question/bug/enhancement/feature request):**
bug
**Steps to reproduce (least amount of steps as possible):**
Create two custom project roles. Go into the project and try to give a user the lower role (before custom) in the list.
**Result:**
Either defaults to the option above it or if the user already has the option above it, it will error saying it already exits.
**Other details that may be helpful:**
These custom roles are the same as the OOTB ones with just the create namespace removed.
**Environment information**
- Rancher version (`rancher/rancher`/`rancher/server` image tag or shown bottom left in the UI):
Rancher | v2.2.2
User Interface | v2.2.41
Helm | v2.10.0-rancher10
Machine | v0.15.0-rancher6-1
- Installation option (single install/HA):
HA
| test | rancher cannot add custom project role where it says it already exists what kind of request is this question bug enhancement feature request bug steps to reproduce least amount of steps as possible create two custom project roles go into the project and try to give a user the lower role before custom in the list result either defaults to the option above it or if the user already has the option above it it will error saying it already exits other details that may be helpful these custom roles are the same as the ootb ones with just the create namespace removed environment information rancher version rancher rancher rancher server image tag or shown bottom left in the ui rancher user interface helm machine installation option single install ha ha | 1 |
240,252 | 20,019,618,739 | IssuesEvent | 2022-02-01 15:16:42 | SPiN-Lab/connPFM | https://api.github.com/repos/SPiN-Lab/connPFM | opened | Change OSF input data to spc | testing | <!--
This is a suggested issue template for connPFM.
If there is other information that would be helpful to include, please do not hesitate to add it!
Before submitting, please check to make sure that the issue is not already addressed; if there is a related issue, then please cross-reference it by #.
-->
<!--
Summarize the issue in 1-2 sentences, linking other issues if they are relevant
Note: simply typing # will prompt you for open issues to select from
-->
### Summary
OSF data input should be in signal percentage change (SPC) and we should also rerun the pipeline and modify the results in OSF for the debiasing
<!--
If needed, add additional detail for:
1. Recreating a bug/problem
2. Any additional context necessary to understand the issue
-->
### Additional Detail
<!--
If desired, add suggested next steps.
If you foresee them in a particular order or priority, please use numbering
-->
### Next Steps
- Change the input to SPC
- run the pipeline to obtain the new results
- upload everything to OSF
<!--
Thank you for submitting your issue!
If you do not receive a response within a calendar week, please post a comment on this issue to catch our attention.
Some issues may not be resolved right away due to the volunteer nature of the project; thank you for your patience!
-->
| 1.0 | Change OSF input data to spc - <!--
This is a suggested issue template for connPFM.
If there is other information that would be helpful to include, please do not hesitate to add it!
Before submitting, please check to make sure that the issue is not already addressed; if there is a related issue, then please cross-reference it by #.
-->
<!--
Summarize the issue in 1-2 sentences, linking other issues if they are relevant
Note: simply typing # will prompt you for open issues to select from
-->
### Summary
OSF data input should be in signal percentage change (SPC) and we should also rerun the pipeline and modify the results in OSF for the debiasing
<!--
If needed, add additional detail for:
1. Recreating a bug/problem
2. Any additional context necessary to understand the issue
-->
### Additional Detail
<!--
If desired, add suggested next steps.
If you foresee them in a particular order or priority, please use numbering
-->
### Next Steps
- Change the input to SPC
- run the pipeline to obtain the new results
- upload everything to OSF
<!--
Thank you for submitting your issue!
If you do not receive a response within a calendar week, please post a comment on this issue to catch our attention.
Some issues may not be resolved right away due to the volunteer nature of the project; thank you for your patience!
-->
| test | change osf input data to spc this is a suggested issue template for connpfm if there is other information that would be helpful to include please do not hesitate to add it before submitting please check to make sure that the issue is not already addressed if there is a related issue then please cross reference it by summarize the issue in sentences linking other issues if they are relevant note simply typing will prompt you for open issues to select from summary osf data input should be in signal percentage change spc and we should also rerun the pipeline and modify the results in osf for the debiasing if needed add additional detail for recreating a bug problem any additional context necessary to understand the issue additional detail if desired add suggested next steps if you foresee them in a particular order or priority please use numbering next steps change the input to spc run the pipeline to obtain the new results upload everything to osf thank you for submitting your issue if you do not receive a response within a calendar week please post a comment on this issue to catch our attention some issues may not be resolved right away due to the volunteer nature of the project thank you for your patience | 1 |
217,459 | 16,717,691,276 | IssuesEvent | 2021-06-10 00:32:36 | dankamongmen/notcurses | https://api.github.com/repos/dankamongmen/notcurses | opened | ensure a common cursor position after printing a sixel in direct mode | documentation enhancement | It looks like xterm leaves the cursor at the last line of the image, one past the last column, while Alacritty leaves it on the first column of the line after the image.
It sure would be nice if notcurses abstracted this difference away. :) | 1.0 | ensure a common cursor position after printing a sixel in direct mode - It looks like xterm leaves the cursor at the last line of the image, one past the last column, while Alacritty leaves it on the first column of the line after the image.
It sure would be nice if notcurses abstracted this difference away. :) | non_test | ensure a common cursor position after printing a sixel in direct mode it looks like xterm leaves the cursor at the last line of the image one past the last column while alacritty leaves it on the first column of the line after the image it sure would be nice if notcurses abstracted this difference away | 0 |
148,309 | 11,847,104,135 | IssuesEvent | 2020-03-24 11:23:45 | microsoft/vscode | https://api.github.com/repos/microsoft/vscode | opened | Test: Change view with screen reader | accessibility testplan-item | Refs: https://github.com/microsoft/vscode/issues/88695
- [ ] win
- [ ] anyOS
Complexity: 3
**Note**: if you are assigned windows, please use the NVDA screen reader. If you are assigned anyOS please either use macOS with VoiceOver or Linux with Orca screen reader.
We have improved our difference view with regards to accessibility. Have a git tracked repostiroy, some file with multiple changes in it and turn on your screen reader. Open the changes view of that file.
Verify:
* `F7` and `shift+F7` navigate you through all the diffs and the screen reader correctly reads the added and removed content
* When you enter the accessible Diff view screen reader mentions to use "Stage/unstage/revert selected ranges"
* As you navigte through the content, the content is first read out and at the end the line number is read out
* You can use "Stage/unstage/revert selected ranges" to stage / unstage/ revert the currently active diff
* Pressing `Esc` takes you out of this view and you are navigated to the regular changes view on the correct position with the right change selected
* The whole flow makes sense. And any feedback on improving this is very welcome
| 1.0 | Test: Change view with screen reader - Refs: https://github.com/microsoft/vscode/issues/88695
- [ ] win
- [ ] anyOS
Complexity: 3
**Note**: if you are assigned windows, please use the NVDA screen reader. If you are assigned anyOS please either use macOS with VoiceOver or Linux with Orca screen reader.
We have improved our difference view with regards to accessibility. Have a git tracked repostiroy, some file with multiple changes in it and turn on your screen reader. Open the changes view of that file.
Verify:
* `F7` and `shift+F7` navigate you through all the diffs and the screen reader correctly reads the added and removed content
* When you enter the accessible Diff view screen reader mentions to use "Stage/unstage/revert selected ranges"
* As you navigte through the content, the content is first read out and at the end the line number is read out
* You can use "Stage/unstage/revert selected ranges" to stage / unstage/ revert the currently active diff
* Pressing `Esc` takes you out of this view and you are navigated to the regular changes view on the correct position with the right change selected
* The whole flow makes sense. And any feedback on improving this is very welcome
| test | test change view with screen reader refs win anyos complexity note if you are assigned windows please use the nvda screen reader if you are assigned anyos please either use macos with voiceover or linux with orca screen reader we have improved our difference view with regards to accessibility have a git tracked repostiroy some file with multiple changes in it and turn on your screen reader open the changes view of that file verify and shift navigate you through all the diffs and the screen reader correctly reads the added and removed content when you enter the accessible diff view screen reader mentions to use stage unstage revert selected ranges as you navigte through the content the content is first read out and at the end the line number is read out you can use stage unstage revert selected ranges to stage unstage revert the currently active diff pressing esc takes you out of this view and you are navigated to the regular changes view on the correct position with the right change selected the whole flow makes sense and any feedback on improving this is very welcome | 1 |
76,299 | 9,418,636,409 | IssuesEvent | 2019-04-10 19:45:01 | Opentrons/opentrons | https://api.github.com/repos/Opentrons/opentrons | opened | V2 Labware: Labware Selection Modal Uses V2 otIds | feature medium protocol designer |
## Acceptance Criteria
- [ ] Labware Selection Modal uses V2 otIds
- [ ] Remove shim mapping in getLabwareDef | 1.0 | V2 Labware: Labware Selection Modal Uses V2 otIds -
## Acceptance Criteria
- [ ] Labware Selection Modal uses V2 otIds
- [ ] Remove shim mapping in getLabwareDef | non_test | labware labware selection modal uses otids acceptance criteria labware selection modal uses otids remove shim mapping in getlabwaredef | 0 |
434,191 | 12,515,375,107 | IssuesEvent | 2020-06-03 07:33:27 | canonical-web-and-design/build.snapcraft.io | https://api.github.com/repos/canonical-web-and-design/build.snapcraft.io | closed | Removing repo doesn't update in IE on Windows | Priority: Medium | Logged in on Windows 10 / IE 11 and tried to remove an old repo. When I hit the red remove button nothing appears to happen on screen. However if I visit the same dashboard in another browser I can see the repo has indeed been deleted.
 | 1.0 | Removing repo doesn't update in IE on Windows - Logged in on Windows 10 / IE 11 and tried to remove an old repo. When I hit the red remove button nothing appears to happen on screen. However if I visit the same dashboard in another browser I can see the repo has indeed been deleted.
 | non_test | removing repo doesn t update in ie on windows logged in on windows ie and tried to remove an old repo when i hit the red remove button nothing appears to happen on screen however if i visit the same dashboard in another browser i can see the repo has indeed been deleted | 0 |
102,992 | 8,873,065,787 | IssuesEvent | 2019-01-11 17:00:13 | pywbem/pywbem | https://api.github.com/repos/pywbem/pywbem | closed | End2end: Optimize non-reachable servers | area: test resolution: fixed type: enhancement | If a server is not reachable, every testcase currently tries again to reach it, which consumes a lot of time.
In the wbem_connection fixture, the information whether a server is usable, could be remembered.
There are two options:
* on the server_definition object
* using the pytest cache fixture | 1.0 | End2end: Optimize non-reachable servers - If a server is not reachable, every testcase currently tries again to reach it, which consumes a lot of time.
In the wbem_connection fixture, the information whether a server is usable, could be remembered.
There are two options:
* on the server_definition object
* using the pytest cache fixture | test | optimize non reachable servers if a server is not reachable every testcase currently tries again to reach it which consumes a lot of time in the wbem connection fixture the information whether a server is usable could be remembered there are two options on the server definition object using the pytest cache fixture | 1 |
318,401 | 27,301,275,175 | IssuesEvent | 2023-02-24 02:19:18 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | roachtest: lib/pq failed | C-test-failure O-robot O-roachtest branch-master T-sql-sessions | roachtest.lib/pq [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8740106?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8740106?buildTab=artifacts#/lib/pq) on master @ [7e2df35a2f6bf7a859bb0539c8ca43c4e72ed260](https://github.com/cockroachdb/cockroach/commits/7e2df35a2f6bf7a859bb0539c8ca43c4e72ed260):
```
test artifacts and logs in: /artifacts/lib/pq/run_1
(orm_helpers.go:201).summarizeFailed:
Tests run on Cockroach v23.1.0-alpha.2-405-g7e2df35a2f
Tests run against lib/pq v1.10.5
217 Total Tests Run
190 tests passed
27 tests failed
7 tests skipped
0 tests ignored
1 test passed unexpectedly
0 tests failed unexpectedly
0 tests expected failed but skipped
0 tests expected failed but not run
---
--- PASS: pq.TestCopyFromError - https://github.com/cockroachdb/cockroach/issues/5807 (unexpected)
For a full summary look at the lib/pq artifacts
An updated blocklist (libPQBlocklist) is available in the artifacts' lib/pq log
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=4</code>
, <code>ROACHTEST_encrypted=false</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/sql-sessions
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*lib/pq.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-24610 | 2.0 | roachtest: lib/pq failed - roachtest.lib/pq [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8740106?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/8740106?buildTab=artifacts#/lib/pq) on master @ [7e2df35a2f6bf7a859bb0539c8ca43c4e72ed260](https://github.com/cockroachdb/cockroach/commits/7e2df35a2f6bf7a859bb0539c8ca43c4e72ed260):
```
test artifacts and logs in: /artifacts/lib/pq/run_1
(orm_helpers.go:201).summarizeFailed:
Tests run on Cockroach v23.1.0-alpha.2-405-g7e2df35a2f
Tests run against lib/pq v1.10.5
217 Total Tests Run
190 tests passed
27 tests failed
7 tests skipped
0 tests ignored
1 test passed unexpectedly
0 tests failed unexpectedly
0 tests expected failed but skipped
0 tests expected failed but not run
---
--- PASS: pq.TestCopyFromError - https://github.com/cockroachdb/cockroach/issues/5807 (unexpected)
For a full summary look at the lib/pq artifacts
An updated blocklist (libPQBlocklist) is available in the artifacts' lib/pq log
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=4</code>
, <code>ROACHTEST_encrypted=false</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/sql-sessions
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*lib/pq.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-24610 | test | roachtest lib pq failed roachtest lib pq with on master test artifacts and logs in artifacts lib pq run orm helpers go summarizefailed tests run on cockroach alpha tests run against lib pq total tests run tests passed tests failed tests skipped tests ignored test passed unexpectedly tests failed unexpectedly tests expected failed but skipped tests expected failed but not run pass pq testcopyfromerror unexpected for a full summary look at the lib pq artifacts an updated blocklist libpqblocklist is available in the artifacts lib pq log parameters roachtest cloud gce roachtest cpu roachtest encrypted false roachtest ssd help see see cc cockroachdb sql sessions jira issue crdb | 1 |
170,564 | 13,193,204,285 | IssuesEvent | 2020-08-13 14:53:37 | w3f/polkadot-spec | https://api.github.com/repos/w3f/polkadot-spec | closed | kagome-adapter: Implement host-api fixture | testsuite | We currently only test host-api-legacy, kagome added most of the latest API by now and we should update the adapter to support that.
Work will be merged as part of #256. | 1.0 | kagome-adapter: Implement host-api fixture - We currently only test host-api-legacy, kagome added most of the latest API by now and we should update the adapter to support that.
Work will be merged as part of #256. | test | kagome adapter implement host api fixture we currently only test host api legacy kagome added most of the latest api by now and we should update the adapter to support that work will be merged as part of | 1 |
34,905 | 4,957,019,402 | IssuesEvent | 2016-12-02 02:04:05 | kubernetes/kubernetes | https://api.github.com/repos/kubernetes/kubernetes | closed | ci-kubernetes-e2e-gke-alpha-features-release-1.5: broken test run | kind/flake priority/P1 team/test-infra | https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gke-alpha-features-release-1.5/177/
Multiple broken tests:
Failed: [k8s.io] ESIPP [Slow][Feature:ExternalTrafficLocalOnly] should only target nodes with endpoints [Slow][Feature:ExternalTrafficLocalOnly] {Kubernetes e2e suite}
```
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:1253
Nov 30 08:24:20.846: Timeout waiting for service "external-local" to have a load balancer
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:2342
```
Issues about this test specifically: #36481
Failed: [k8s.io] ESIPP [Slow][Feature:ExternalTrafficLocalOnly] should work for type=LoadBalancer [Slow][Feature:ExternalTrafficLocalOnly] {Kubernetes e2e suite}
```
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:1167
Nov 30 08:44:51.544: Timeout waiting for service "external-local" to have a load balancer
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:2342
```
Issues about this test specifically: #36389
Failed: [k8s.io] ESIPP [Slow][Feature:ExternalTrafficLocalOnly] should handle updates to source ip annotation [Slow][Feature:ExternalTrafficLocalOnly] {Kubernetes e2e suite}
```
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:1404
Nov 30 09:05:02.660: Timeout waiting for service "external-local" to have a load balancer
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:2342
```
Issues about this test specifically: #35225 #35347
Failed: [k8s.io] ESIPP [Slow][Feature:ExternalTrafficLocalOnly] should work from pods [Slow][Feature:ExternalTrafficLocalOnly] {Kubernetes e2e suite}
```
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:1298
Nov 30 09:25:17.414: Timeout waiting for service "external-local" to have a load balancer
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:2342
```
| 1.0 | ci-kubernetes-e2e-gke-alpha-features-release-1.5: broken test run - https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gke-alpha-features-release-1.5/177/
Multiple broken tests:
Failed: [k8s.io] ESIPP [Slow][Feature:ExternalTrafficLocalOnly] should only target nodes with endpoints [Slow][Feature:ExternalTrafficLocalOnly] {Kubernetes e2e suite}
```
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:1253
Nov 30 08:24:20.846: Timeout waiting for service "external-local" to have a load balancer
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:2342
```
Issues about this test specifically: #36481
Failed: [k8s.io] ESIPP [Slow][Feature:ExternalTrafficLocalOnly] should work for type=LoadBalancer [Slow][Feature:ExternalTrafficLocalOnly] {Kubernetes e2e suite}
```
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:1167
Nov 30 08:44:51.544: Timeout waiting for service "external-local" to have a load balancer
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:2342
```
Issues about this test specifically: #36389
Failed: [k8s.io] ESIPP [Slow][Feature:ExternalTrafficLocalOnly] should handle updates to source ip annotation [Slow][Feature:ExternalTrafficLocalOnly] {Kubernetes e2e suite}
```
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:1404
Nov 30 09:05:02.660: Timeout waiting for service "external-local" to have a load balancer
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:2342
```
Issues about this test specifically: #35225 #35347
Failed: [k8s.io] ESIPP [Slow][Feature:ExternalTrafficLocalOnly] should work from pods [Slow][Feature:ExternalTrafficLocalOnly] {Kubernetes e2e suite}
```
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:1298
Nov 30 09:25:17.414: Timeout waiting for service "external-local" to have a load balancer
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:2342
```
| test | ci kubernetes gke alpha features release broken test run multiple broken tests failed esipp should only target nodes with endpoints kubernetes suite go src io kubernetes output dockerized go src io kubernetes test service go nov timeout waiting for service external local to have a load balancer go src io kubernetes output dockerized go src io kubernetes test service go issues about this test specifically failed esipp should work for type loadbalancer kubernetes suite go src io kubernetes output dockerized go src io kubernetes test service go nov timeout waiting for service external local to have a load balancer go src io kubernetes output dockerized go src io kubernetes test service go issues about this test specifically failed esipp should handle updates to source ip annotation kubernetes suite go src io kubernetes output dockerized go src io kubernetes test service go nov timeout waiting for service external local to have a load balancer go src io kubernetes output dockerized go src io kubernetes test service go issues about this test specifically failed esipp should work from pods kubernetes suite go src io kubernetes output dockerized go src io kubernetes test service go nov timeout waiting for service external local to have a load balancer go src io kubernetes output dockerized go src io kubernetes test service go | 1 |
113,826 | 17,154,176,588 | IssuesEvent | 2021-07-14 03:13:21 | atlslscsrv-app/atlslscsrv-app | https://api.github.com/repos/atlslscsrv-app/atlslscsrv-app | closed | WS-2018-0590 (High) detected in diff-3.2.0.tgz - autoclosed | security vulnerability | ## WS-2018-0590 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>diff-3.2.0.tgz</b></p></summary>
<p>A javascript text diff implementation.</p>
<p>Library home page: <a href="https://registry.npmjs.org/diff/-/diff-3.2.0.tgz">https://registry.npmjs.org/diff/-/diff-3.2.0.tgz</a></p>
<p>Path to dependency file: atlslscsrv-app/dist/resources/app/package.json</p>
<p>Path to vulnerable library: atlslscsrv-app/dist/resources/app/node_modules/diff/package.json,atlslscsrv-app/node_modules_native/node_modules_forked/node-pty/node_modules/diff/package.json</p>
<p>
Dependency Hierarchy:
- mocha-3.5.3.tgz (Root Library)
- :x: **diff-3.2.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/atlslscsrv-app/atlslscsrv-app/commit/9cd1d81ea40cec233263f3f83e4afad1985f0f0d">9cd1d81ea40cec233263f3f83e4afad1985f0f0d</a></p>
<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>
A vulnerability was found in diff before v3.5.0, the affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks.
<p>Publish Date: 2018-03-05
<p>URL: <a href=https://bugzilla.redhat.com/show_bug.cgi?id=1552148>WS-2018-0590</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>7.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/kpdecker/jsdiff/commit/2aec4298639bf30fb88a00b356bf404d3551b8c0">https://github.com/kpdecker/jsdiff/commit/2aec4298639bf30fb88a00b356bf404d3551b8c0</a></p>
<p>Release Date: 2019-06-11</p>
<p>Fix Resolution: 3.5.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 | WS-2018-0590 (High) detected in diff-3.2.0.tgz - autoclosed - ## WS-2018-0590 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>diff-3.2.0.tgz</b></p></summary>
<p>A javascript text diff implementation.</p>
<p>Library home page: <a href="https://registry.npmjs.org/diff/-/diff-3.2.0.tgz">https://registry.npmjs.org/diff/-/diff-3.2.0.tgz</a></p>
<p>Path to dependency file: atlslscsrv-app/dist/resources/app/package.json</p>
<p>Path to vulnerable library: atlslscsrv-app/dist/resources/app/node_modules/diff/package.json,atlslscsrv-app/node_modules_native/node_modules_forked/node-pty/node_modules/diff/package.json</p>
<p>
Dependency Hierarchy:
- mocha-3.5.3.tgz (Root Library)
- :x: **diff-3.2.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/atlslscsrv-app/atlslscsrv-app/commit/9cd1d81ea40cec233263f3f83e4afad1985f0f0d">9cd1d81ea40cec233263f3f83e4afad1985f0f0d</a></p>
<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>
A vulnerability was found in diff before v3.5.0, the affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks.
<p>Publish Date: 2018-03-05
<p>URL: <a href=https://bugzilla.redhat.com/show_bug.cgi?id=1552148>WS-2018-0590</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>7.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/kpdecker/jsdiff/commit/2aec4298639bf30fb88a00b356bf404d3551b8c0">https://github.com/kpdecker/jsdiff/commit/2aec4298639bf30fb88a00b356bf404d3551b8c0</a></p>
<p>Release Date: 2019-06-11</p>
<p>Fix Resolution: 3.5.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 | ws high detected in diff tgz autoclosed ws high severity vulnerability vulnerable library diff tgz a javascript text diff implementation library home page a href path to dependency file atlslscsrv app dist resources app package json path to vulnerable library atlslscsrv app dist resources app node modules diff package json atlslscsrv app node modules native node modules forked node pty node modules diff package json dependency hierarchy mocha tgz root library x diff tgz vulnerable library found in head commit a href found in base branch master vulnerability details a vulnerability was found in diff before the affected versions of this package are vulnerable to regular expression denial of service redos attacks publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
605,604 | 18,737,666,054 | IssuesEvent | 2021-11-04 09:46:58 | Adyen/adyen-magento2 | https://api.github.com/repos/Adyen/adyen-magento2 | closed | [PW-5668] Orders staying in Payment Review after OFFER_CLOSED since 7.0.1 -> 7.2.0 upgrade | Bug report Priority: high Issue: Confirmed Webhooks | **Describe the bug**
This has been occuring since upgrading to 7.2.0 from 7.0.1 - OFFER_CLOSED notifications should cancel the related order, however the order is staying in Payment Review.
Status history is added to the order RE the closed offer, however the order stays open.
Our downstream systems listen to the state of the M2 order and therefore we have a building list of orders that are pending in our ERP.
**To Reproduce**
Place order through Adyen, wait for OFFER_CLOSED, Magento accepts the notification but doesn't cancel the order.
**Expected behavior**
Order is to be cancelled with the acknowledgement of the OFFER_CLOSED notification.
**Magento version**
2.3.7-p1
**Plugin version**
7.2.0
**Screenshots**
| 1.0 | [PW-5668] Orders staying in Payment Review after OFFER_CLOSED since 7.0.1 -> 7.2.0 upgrade - **Describe the bug**
This has been occuring since upgrading to 7.2.0 from 7.0.1 - OFFER_CLOSED notifications should cancel the related order, however the order is staying in Payment Review.
Status history is added to the order RE the closed offer, however the order stays open.
Our downstream systems listen to the state of the M2 order and therefore we have a building list of orders that are pending in our ERP.
**To Reproduce**
Place order through Adyen, wait for OFFER_CLOSED, Magento accepts the notification but doesn't cancel the order.
**Expected behavior**
Order is to be cancelled with the acknowledgement of the OFFER_CLOSED notification.
**Magento version**
2.3.7-p1
**Plugin version**
7.2.0
**Screenshots**
| non_test | orders staying in payment review after offer closed since upgrade describe the bug this has been occuring since upgrading to from offer closed notifications should cancel the related order however the order is staying in payment review status history is added to the order re the closed offer however the order stays open our downstream systems listen to the state of the order and therefore we have a building list of orders that are pending in our erp to reproduce place order through adyen wait for offer closed magento accepts the notification but doesn t cancel the order expected behavior order is to be cancelled with the acknowledgement of the offer closed notification magento version plugin version screenshots | 0 |
16,226 | 3,510,839,088 | IssuesEvent | 2016-01-09 20:14:42 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | Failed tests (10918): TestReplicaCorruption | test-failure TestReplicaCorruption | The following test appears to have failed:
[#10918](https://circleci.com/gh/cockroachdb/cockroach/10918):
```
I0109 19:55:13.048885 915 storage/replica.go:1609 gossiping sentinel from store 1, range 1
I0109 19:55:13.049195 915 storage/replica.go:1615 gossiping first range from store 1, range 1
I0109 19:55:13.050417 915 storage/replica.go:1154 reproposing 1 commands after empty entry
E0109 19:55:13.052309 915 storage/replica.go:1249 error executing raft command: write too old: timestamp 0.000000000,12 <= 0.000000000,12
I0109 19:55:13.053591 915 storage/engine/rocksdb.go:137 closing in-memory rocksdb instance
--- FAIL: TestReplicaCorruption (0.01s)
replica_test.go:2971: unexpected error: %!s(<nil>)
=== RUN TestChangeReplicasDuplicateError
I0109 19:55:13.056533 915 raft/raft.go:446 [group 1] 1 became follower at term 5
I0109 19:55:13.056737 915 raft/raft.go:234 [group 1] newRaft 1 [peers: [1], term: 5, commit: 10, applied: 10, lastindex: 10, lastterm: 5]
I0109 19:55:13.056857 915 raft/raft.go:526 [group 1] 1 is starting a new election at term 5
I0109 19:55:13.056941 915 raft/raft.go:459 [group 1] 1 became candidate at term 6
I0109 19:55:13.057059 915 raft/raft.go:508 [group 1] 1 received vote from 1 at term 6
I0109 19:55:13.057180 915 raft/raft.go:487 [group 1] 1 became leader at term 6
I0109 19:55:13.058747 915 storage/replica.go:1600 gossiping cluster id test from store 1, range 1
I0109 19:55:13.059945 915 storage/replica_command.go:1192 range 1: new leader lease replica {1 1 1} 1970-01-01 00:00:00 +0000 UTC +1.000s
--
I0109 19:55:38.098695 915 storage/engine/rocksdb.go:137 closing in-memory rocksdb instance
--- PASS: TestLeaderAfterSplit (0.23s)
<autogenerated>:28: prior leak detected, leaktest disabled
=== RUN Example_rebalancing
--- PASS: Example_rebalancing (0.65s)
FAIL
FAIL github.com/cockroachdb/cockroach/storage 27.947s
=== RUN TestBatchBasics
I0109 19:55:40.758063 985 storage/engine/rocksdb.go:137 closing in-memory rocksdb instance
--- PASS: TestBatchBasics (0.01s)
=== RUN TestBatchGet
I0109 19:55:40.766002 985 storage/engine/rocksdb.go:137 closing in-memory rocksdb instance
--- PASS: TestBatchGet (0.02s)
=== RUN TestBatchMerge
I0109 19:55:40.789888 985 storage/engine/rocksdb.go:137 closing in-memory rocksdb instance
--- PASS: TestBatchMerge (0.01s)
=== RUN TestBatchProto
```
Please assign, take a look and update the issue accordingly. | 2.0 | Failed tests (10918): TestReplicaCorruption - The following test appears to have failed:
[#10918](https://circleci.com/gh/cockroachdb/cockroach/10918):
```
I0109 19:55:13.048885 915 storage/replica.go:1609 gossiping sentinel from store 1, range 1
I0109 19:55:13.049195 915 storage/replica.go:1615 gossiping first range from store 1, range 1
I0109 19:55:13.050417 915 storage/replica.go:1154 reproposing 1 commands after empty entry
E0109 19:55:13.052309 915 storage/replica.go:1249 error executing raft command: write too old: timestamp 0.000000000,12 <= 0.000000000,12
I0109 19:55:13.053591 915 storage/engine/rocksdb.go:137 closing in-memory rocksdb instance
--- FAIL: TestReplicaCorruption (0.01s)
replica_test.go:2971: unexpected error: %!s(<nil>)
=== RUN TestChangeReplicasDuplicateError
I0109 19:55:13.056533 915 raft/raft.go:446 [group 1] 1 became follower at term 5
I0109 19:55:13.056737 915 raft/raft.go:234 [group 1] newRaft 1 [peers: [1], term: 5, commit: 10, applied: 10, lastindex: 10, lastterm: 5]
I0109 19:55:13.056857 915 raft/raft.go:526 [group 1] 1 is starting a new election at term 5
I0109 19:55:13.056941 915 raft/raft.go:459 [group 1] 1 became candidate at term 6
I0109 19:55:13.057059 915 raft/raft.go:508 [group 1] 1 received vote from 1 at term 6
I0109 19:55:13.057180 915 raft/raft.go:487 [group 1] 1 became leader at term 6
I0109 19:55:13.058747 915 storage/replica.go:1600 gossiping cluster id test from store 1, range 1
I0109 19:55:13.059945 915 storage/replica_command.go:1192 range 1: new leader lease replica {1 1 1} 1970-01-01 00:00:00 +0000 UTC +1.000s
--
I0109 19:55:38.098695 915 storage/engine/rocksdb.go:137 closing in-memory rocksdb instance
--- PASS: TestLeaderAfterSplit (0.23s)
<autogenerated>:28: prior leak detected, leaktest disabled
=== RUN Example_rebalancing
--- PASS: Example_rebalancing (0.65s)
FAIL
FAIL github.com/cockroachdb/cockroach/storage 27.947s
=== RUN TestBatchBasics
I0109 19:55:40.758063 985 storage/engine/rocksdb.go:137 closing in-memory rocksdb instance
--- PASS: TestBatchBasics (0.01s)
=== RUN TestBatchGet
I0109 19:55:40.766002 985 storage/engine/rocksdb.go:137 closing in-memory rocksdb instance
--- PASS: TestBatchGet (0.02s)
=== RUN TestBatchMerge
I0109 19:55:40.789888 985 storage/engine/rocksdb.go:137 closing in-memory rocksdb instance
--- PASS: TestBatchMerge (0.01s)
=== RUN TestBatchProto
```
Please assign, take a look and update the issue accordingly. | test | failed tests testreplicacorruption the following test appears to have failed storage replica go gossiping sentinel from store range storage replica go gossiping first range from store range storage replica go reproposing commands after empty entry storage replica go error executing raft command write too old timestamp storage engine rocksdb go closing in memory rocksdb instance fail testreplicacorruption replica test go unexpected error s run testchangereplicasduplicateerror raft raft go became follower at term raft raft go newraft term commit applied lastindex lastterm raft raft go is starting a new election at term raft raft go became candidate at term raft raft go received vote from at term raft raft go became leader at term storage replica go gossiping cluster id test from store range storage replica command go range new leader lease replica utc storage engine rocksdb go closing in memory rocksdb instance pass testleaderaftersplit prior leak detected leaktest disabled run example rebalancing pass example rebalancing fail fail github com cockroachdb cockroach storage run testbatchbasics storage engine rocksdb go closing in memory rocksdb instance pass testbatchbasics run testbatchget storage engine rocksdb go closing in memory rocksdb instance pass testbatchget run testbatchmerge storage engine rocksdb go closing in memory rocksdb instance pass testbatchmerge run testbatchproto please assign take a look and update the issue accordingly | 1 |
106,666 | 9,178,901,564 | IssuesEvent | 2019-03-05 00:53:28 | OrcaPracticas/happy-shell | https://api.github.com/repos/OrcaPracticas/happy-shell | closed | [ISSUE] Crear utilidad que permite levantar la UI | ⚙️ Config 📝 Testing 🛠 Feature | **A Fin** de poder levantar cualquier **UI**
**Quiero** contar con el comando que simplifique todo el proceso
**Y** quiero poder levantar la ui en modo `DEBUG`
**Y** de manera normal
**Y** quiero poder indicar el valor de `CLUSTER_ENV`
**Y** en caso de no indicarlo que tome el valor por defecto de las variables globales.
___
## 📝Tareas adicionales
- [x] **Comentar la función**
- [x] **Agregar prueba de funcionalidad** | 1.0 | [ISSUE] Crear utilidad que permite levantar la UI - **A Fin** de poder levantar cualquier **UI**
**Quiero** contar con el comando que simplifique todo el proceso
**Y** quiero poder levantar la ui en modo `DEBUG`
**Y** de manera normal
**Y** quiero poder indicar el valor de `CLUSTER_ENV`
**Y** en caso de no indicarlo que tome el valor por defecto de las variables globales.
___
## 📝Tareas adicionales
- [x] **Comentar la función**
- [x] **Agregar prueba de funcionalidad** | test | crear utilidad que permite levantar la ui a fin de poder levantar cualquier ui quiero contar con el comando que simplifique todo el proceso y quiero poder levantar la ui en modo debug y de manera normal y quiero poder indicar el valor de cluster env y en caso de no indicarlo que tome el valor por defecto de las variables globales 📝tareas adicionales comentar la función agregar prueba de funcionalidad | 1 |
169,426 | 13,146,448,443 | IssuesEvent | 2020-08-08 09:56:01 | moodlebox/moodlebox | https://api.github.com/repos/moodlebox/moodlebox | closed | Refactor Ansible roles | Status: tests passed Type: enhancement | For modularity, we need to refactor Ansible roles, increasing granularity. | 1.0 | Refactor Ansible roles - For modularity, we need to refactor Ansible roles, increasing granularity. | test | refactor ansible roles for modularity we need to refactor ansible roles increasing granularity | 1 |
275,385 | 23,912,216,831 | IssuesEvent | 2022-09-09 09:16:32 | hotosm/galaxy-api | https://api.github.com/repos/hotosm/galaxy-api | closed | Feature : Add status filter on tasking manager validation stats | status:testing | Feature : Add status filter on tasking manager validation stats
Project endpoint should be filtering by project status.
_Originally posted by @kshitijrajsharma in https://github.com/hotosm/galaxy-api/issues/271#issuecomment-1210142049_ | 1.0 | Feature : Add status filter on tasking manager validation stats - Feature : Add status filter on tasking manager validation stats
Project endpoint should be filtering by project status.
_Originally posted by @kshitijrajsharma in https://github.com/hotosm/galaxy-api/issues/271#issuecomment-1210142049_ | test | feature add status filter on tasking manager validation stats feature add status filter on tasking manager validation stats project endpoint should be filtering by project status originally posted by kshitijrajsharma in | 1 |
139,932 | 11,299,554,183 | IssuesEvent | 2020-01-17 11:28:53 | prostomarkeloff/vk.py | https://api.github.com/repos/prostomarkeloff/vk.py | closed | Переработать MetaMixin | 1.0.0-release need-docs need-tests | Нужно переработать MetaMixin для более подробного и гибкого описания объектов. | 1.0 | Переработать MetaMixin - Нужно переработать MetaMixin для более подробного и гибкого описания объектов. | test | переработать metamixin нужно переработать metamixin для более подробного и гибкого описания объектов | 1 |
107,314 | 11,527,744,507 | IssuesEvent | 2020-02-16 00:05:10 | laurentlaurent/ShutterFeed-a-soen-341-repo | https://api.github.com/repos/laurentlaurent/ShutterFeed-a-soen-341-repo | closed | Create templates | documentation | <!-- ==== Template for User Story Checklist ====
1. Enter the name
2. Describe the feature or write the user story in a first-person point of view.
3. Write the acceptance test(s). Those are the validation tests that must be met to consider the issue to be closed.
4. Describe any related features or user stories. Doing so will help us create epics more easily.
5. List the tasks to be performed to complete the user story.
6. Label the issue
7. Add new user story to wiki
============================================-->
<!-- Choose the type: User Story or Task. Don't worry if the pipes don't line up-->
| Task | P | SP |
|:-----------------------|:-:|:--:|
| Create templates | 5 | 1 |
<!-- Write a Description Below -->
For Taxinomy on issue type to make into templates
<!-- Don't write anything near the line -->
------------------------------------------
## Task List
Create a template for:
- [x] User Story [#62]
- [x] Task
- [ ] For next meeting/Discussion
- [ ] Requesting help for feature
- [ ] Verify issue completion with Acceptance Test. Done!
<!--
Enter some tasks above
~~~~~~~HELPER~~~~
Use checkboxes like this:
- [ ] Task 1 (Add link to issue number if needed)
- [ ] Task 2 (@ people assigned to the task
~~~~~~~~~~~~~~~
-->
<!-- Don't write anything near the line -->
------------------------------------------
<!--
## Requirements
* List Requirements if there are any
-->
## Acceptance Tests
* Issue templates created
<!-- Don't write anything near the line -->
------------------------------------------
## Related features/user stories
<!--~~~~HELPER~~~~~
Use bullet points like this:
* Related feature [#A]
* Related issue number [#B]
~~~~~~~~~~~~~~~-->
## Additional context
The same way we now have a template for user stories, we should have one for these different types of issues. This will create a more homogeneous issue environment. | 1.0 | Create templates - <!-- ==== Template for User Story Checklist ====
1. Enter the name
2. Describe the feature or write the user story in a first-person point of view.
3. Write the acceptance test(s). Those are the validation tests that must be met to consider the issue to be closed.
4. Describe any related features or user stories. Doing so will help us create epics more easily.
5. List the tasks to be performed to complete the user story.
6. Label the issue
7. Add new user story to wiki
============================================-->
<!-- Choose the type: User Story or Task. Don't worry if the pipes don't line up-->
| Task | P | SP |
|:-----------------------|:-:|:--:|
| Create templates | 5 | 1 |
<!-- Write a Description Below -->
For Taxinomy on issue type to make into templates
<!-- Don't write anything near the line -->
------------------------------------------
## Task List
Create a template for:
- [x] User Story [#62]
- [x] Task
- [ ] For next meeting/Discussion
- [ ] Requesting help for feature
- [ ] Verify issue completion with Acceptance Test. Done!
<!--
Enter some tasks above
~~~~~~~HELPER~~~~
Use checkboxes like this:
- [ ] Task 1 (Add link to issue number if needed)
- [ ] Task 2 (@ people assigned to the task
~~~~~~~~~~~~~~~
-->
<!-- Don't write anything near the line -->
------------------------------------------
<!--
## Requirements
* List Requirements if there are any
-->
## Acceptance Tests
* Issue templates created
<!-- Don't write anything near the line -->
------------------------------------------
## Related features/user stories
<!--~~~~HELPER~~~~~
Use bullet points like this:
* Related feature [#A]
* Related issue number [#B]
~~~~~~~~~~~~~~~-->
## Additional context
The same way we now have a template for user stories, we should have one for these different types of issues. This will create a more homogeneous issue environment. | non_test | create templates template for user story checklist enter the name describe the feature or write the user story in a first person point of view write the acceptance test s those are the validation tests that must be met to consider the issue to be closed describe any related features or user stories doing so will help us create epics more easily list the tasks to be performed to complete the user story label the issue add new user story to wiki task p sp create templates for taxinomy on issue type to make into templates task list create a template for user story task for next meeting discussion requesting help for feature verify issue completion with acceptance test done enter some tasks above helper use checkboxes like this task add link to issue number if needed task people assigned to the task requirements list requirements if there are any acceptance tests issue templates created related features user stories helper use bullet points like this related feature related issue number additional context the same way we now have a template for user stories we should have one for these different types of issues this will create a more homogeneous issue environment | 0 |
109,960 | 9,421,299,995 | IssuesEvent | 2019-04-11 06:19:43 | CARTAvis/carta-backend | https://api.github.com/repos/CARTAvis/carta-backend | closed | [Test] CURSOR_Z_PROFILE.test.ts failed since commit 023ce6c | ICD test failure | Cannot get response after sending set cursor.
Currently this test is not included in CI test. | 1.0 | [Test] CURSOR_Z_PROFILE.test.ts failed since commit 023ce6c - Cannot get response after sending set cursor.
Currently this test is not included in CI test. | test | cursor z profile test ts failed since commit cannot get response after sending set cursor currently this test is not included in ci test | 1 |
80,317 | 9,994,337,053 | IssuesEvent | 2019-07-11 17:24:53 | mhmdtshref/portfolio | https://api.github.com/repos/mhmdtshref/portfolio | reopened | Create Projects page component for admin app | design feature technical | Should create projects component design like the one created in Figma. | 1.0 | Create Projects page component for admin app - Should create projects component design like the one created in Figma. | non_test | create projects page component for admin app should create projects component design like the one created in figma | 0 |
337,949 | 30,273,194,053 | IssuesEvent | 2023-07-07 17:06:56 | pandas-dev/pandas | https://api.github.com/repos/pandas-dev/pandas | closed | BUG: `Series.replace` doesn't update `CategoricalDtype` when `inplace=True` in pandas-2.0 | good first issue Needs Tests | ### 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
In [1]: import pandas as pd
In [2]: s = pd.Series(["one", "two", "three"], dtype="category")
In [3]: s
Out[3]:
0 one
1 two
2 three
dtype: category
Categories (3, object): ['one', 'three', 'two']
In [4]: new_s = s.replace(to_replace="one", value="two")
In [5]: new_s
Out[5]:
0 two
1 two
2 three
dtype: category
Categories (2, object): ['three', 'two']
In [6]: new_s.dtype
Out[6]: CategoricalDtype(categories=['three', 'two'], ordered=False) # Correct
In [7]: s.replace(to_replace="one", value="two", inplace=True)
In [8]: s
Out[8]:
0 two
1 two
2 three
dtype: category
Categories (2, object): ['three', 'two'] # Correct __repr__ output
In [9]: s.dtype
Out[9]: CategoricalDtype(categories=['one', 'three', 'two'], ordered=False). # BUG: Incorrect dtype, dtype used to be updated pre pandas-2.0
```
### Issue Description
When we replace values in a categorical Series, with `inplace=True`, the dtype is not being updated.
### Expected Behavior
```python
In [9]: s.dtype
Out[9]: CategoricalDtype(categories=['three', 'two'], ordered=False)
```
### Installed Versions
<details>
INSTALLED VERSIONS
------------------
commit : 37ea63d540fd27274cad6585082c91b1283f963d
python : 3.10.11.final.0
python-bits : 64
OS : Linux
OS-release : 4.15.0-76-generic
Version : #86-Ubuntu SMP Fri Jan 17 17:24:28 UTC 2020
machine : x86_64
processor : x86_64
byteorder : little
LC_ALL : None
LANG : en_US.UTF-8
LOCALE : en_US.UTF-8
pandas : 2.0.1
numpy : 1.23.5
pytz : 2023.3
dateutil : 2.8.2
setuptools : 67.7.2
pip : 23.1.2
Cython : 0.29.34
pytest : 7.3.1
hypothesis : 6.75.3
sphinx : 5.3.0
blosc : None
feather : None
xlsxwriter : None
lxml.etree : None
html5lib : None
pymysql : None
psycopg2 : None
jinja2 : 3.1.2
IPython : 8.13.2
pandas_datareader: None
bs4 : 4.12.2
bottleneck : None
brotli :
fastparquet : None
fsspec : 2023.5.0
gcsfs : None
matplotlib : None
numba : 0.56.4
numexpr : None
odfpy : None
openpyxl : None
pandas_gbq : None
pyarrow : 11.0.0
pyreadstat : None
pyxlsb : None
s3fs : 2023.5.0
scipy : 1.10.1
snappy :
sqlalchemy : 2.0.15
tables : None
tabulate : 0.9.0
xarray : None
xlrd : None
zstandard : None
tzdata : 2023.3
qtpy : None
pyqt5 : None
</details>
| 1.0 | BUG: `Series.replace` doesn't update `CategoricalDtype` when `inplace=True` in pandas-2.0 - ### 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
In [1]: import pandas as pd
In [2]: s = pd.Series(["one", "two", "three"], dtype="category")
In [3]: s
Out[3]:
0 one
1 two
2 three
dtype: category
Categories (3, object): ['one', 'three', 'two']
In [4]: new_s = s.replace(to_replace="one", value="two")
In [5]: new_s
Out[5]:
0 two
1 two
2 three
dtype: category
Categories (2, object): ['three', 'two']
In [6]: new_s.dtype
Out[6]: CategoricalDtype(categories=['three', 'two'], ordered=False) # Correct
In [7]: s.replace(to_replace="one", value="two", inplace=True)
In [8]: s
Out[8]:
0 two
1 two
2 three
dtype: category
Categories (2, object): ['three', 'two'] # Correct __repr__ output
In [9]: s.dtype
Out[9]: CategoricalDtype(categories=['one', 'three', 'two'], ordered=False). # BUG: Incorrect dtype, dtype used to be updated pre pandas-2.0
```
### Issue Description
When we replace values in a categorical Series, with `inplace=True`, the dtype is not being updated.
### Expected Behavior
```python
In [9]: s.dtype
Out[9]: CategoricalDtype(categories=['three', 'two'], ordered=False)
```
### Installed Versions
<details>
INSTALLED VERSIONS
------------------
commit : 37ea63d540fd27274cad6585082c91b1283f963d
python : 3.10.11.final.0
python-bits : 64
OS : Linux
OS-release : 4.15.0-76-generic
Version : #86-Ubuntu SMP Fri Jan 17 17:24:28 UTC 2020
machine : x86_64
processor : x86_64
byteorder : little
LC_ALL : None
LANG : en_US.UTF-8
LOCALE : en_US.UTF-8
pandas : 2.0.1
numpy : 1.23.5
pytz : 2023.3
dateutil : 2.8.2
setuptools : 67.7.2
pip : 23.1.2
Cython : 0.29.34
pytest : 7.3.1
hypothesis : 6.75.3
sphinx : 5.3.0
blosc : None
feather : None
xlsxwriter : None
lxml.etree : None
html5lib : None
pymysql : None
psycopg2 : None
jinja2 : 3.1.2
IPython : 8.13.2
pandas_datareader: None
bs4 : 4.12.2
bottleneck : None
brotli :
fastparquet : None
fsspec : 2023.5.0
gcsfs : None
matplotlib : None
numba : 0.56.4
numexpr : None
odfpy : None
openpyxl : None
pandas_gbq : None
pyarrow : 11.0.0
pyreadstat : None
pyxlsb : None
s3fs : 2023.5.0
scipy : 1.10.1
snappy :
sqlalchemy : 2.0.15
tables : None
tabulate : 0.9.0
xarray : None
xlrd : None
zstandard : None
tzdata : 2023.3
qtpy : None
pyqt5 : None
</details>
| test | bug series replace doesn t update categoricaldtype when inplace true in pandas 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 in import pandas as pd in s pd series dtype category in s out one two three dtype category categories object in new s s replace to replace one value two in new s out two two three dtype category categories object in new s dtype out categoricaldtype categories ordered false correct in s replace to replace one value two inplace true in s out two two three dtype category categories object correct repr output in s dtype out categoricaldtype categories ordered false bug incorrect dtype dtype used to be updated pre pandas issue description when we replace values in a categorical series with inplace true the dtype is not being updated expected behavior python in s dtype out categoricaldtype categories ordered false installed versions installed versions commit python final python bits os linux os release generic version ubuntu smp fri jan utc machine processor byteorder little lc all none lang en us utf locale en us utf pandas numpy pytz dateutil setuptools pip cython pytest hypothesis sphinx blosc none feather none xlsxwriter none lxml etree none none pymysql none none ipython pandas datareader none bottleneck none brotli fastparquet none fsspec gcsfs none matplotlib none numba numexpr none odfpy none openpyxl none pandas gbq none pyarrow pyreadstat none pyxlsb none scipy snappy sqlalchemy tables none tabulate xarray none xlrd none zstandard none tzdata qtpy none none | 1 |
316,399 | 27,161,700,877 | IssuesEvent | 2023-02-17 12:25:00 | wazuh/wazuh-qa | https://api.github.com/repos/wazuh/wazuh-qa | closed | Add coverage to new capabilities of the `sync-agent-groups-get` endpoint in `wazuh_db` | team/qa type/test-development role/qa-binary-beats subteam/qa-rainbow | | Target version | Related issue | Related PR/dev branch |
|--------------------|--------------------|-----------------|
| 4.4.0 | [#16196](https://github.com/wazuh/wazuh/issues/16196) | [#16202](https://github.com/wazuh/wazuh/pull/16202) |
## Description
With the new changes in wazuh_db's endpoint `sync-agent-groups-get`, the parameter `condition` is optional and now there is the possibility to also obtain the _groups global hash_ from that endpoint.
Integration tests `test_wazuh_db/test_sync_agent_groups_get.py` should be adapted to the new modifications, adding the new cases and changing the expected output of the **Test without condition** case where it was expected to fail and now it should work just fine.
## Proposed test cases
<details><summary>Sync agent groups get - condition is optional and group hash added</summary>
```Gherkin
Given a wazuh-manager with a wazuh-agent connected.
And the wazuh-agent is assigned to 3 groups.
When the query "<input>" is made to wazuh_db.
Then `wazuh_db` responds "<output>"
Examples:
| input | output |
| ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------ |
| `global sync-agent-groups-get {"get_global_hash": true}` | `[{"data": [], "hash": "1945e0d9718edae6897a8c8777ad805a4fe6c9cd"}]` |
| `global sync-agent-groups-get {}` | `[{"data": []}]` |
| `global sync-agent-groups-get {"condition": "sync_status", "get_global_hash": true}` | `[{"data": [{"id": 1, "groups": ["g0", "g1", "g2" ]}], "hash": "1945e0d9718edae6897a8c8777ad805a4fe6c9cd"}]` |
```
</details> | 1.0 | Add coverage to new capabilities of the `sync-agent-groups-get` endpoint in `wazuh_db` - | Target version | Related issue | Related PR/dev branch |
|--------------------|--------------------|-----------------|
| 4.4.0 | [#16196](https://github.com/wazuh/wazuh/issues/16196) | [#16202](https://github.com/wazuh/wazuh/pull/16202) |
## Description
With the new changes in wazuh_db's endpoint `sync-agent-groups-get`, the parameter `condition` is optional and now there is the possibility to also obtain the _groups global hash_ from that endpoint.
Integration tests `test_wazuh_db/test_sync_agent_groups_get.py` should be adapted to the new modifications, adding the new cases and changing the expected output of the **Test without condition** case where it was expected to fail and now it should work just fine.
## Proposed test cases
<details><summary>Sync agent groups get - condition is optional and group hash added</summary>
```Gherkin
Given a wazuh-manager with a wazuh-agent connected.
And the wazuh-agent is assigned to 3 groups.
When the query "<input>" is made to wazuh_db.
Then `wazuh_db` responds "<output>"
Examples:
| input | output |
| ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------ |
| `global sync-agent-groups-get {"get_global_hash": true}` | `[{"data": [], "hash": "1945e0d9718edae6897a8c8777ad805a4fe6c9cd"}]` |
| `global sync-agent-groups-get {}` | `[{"data": []}]` |
| `global sync-agent-groups-get {"condition": "sync_status", "get_global_hash": true}` | `[{"data": [{"id": 1, "groups": ["g0", "g1", "g2" ]}], "hash": "1945e0d9718edae6897a8c8777ad805a4fe6c9cd"}]` |
```
</details> | test | add coverage to new capabilities of the sync agent groups get endpoint in wazuh db target version related issue related pr dev branch description with the new changes in wazuh db s endpoint sync agent groups get the parameter condition is optional and now there is the possibility to also obtain the groups global hash from that endpoint integration tests test wazuh db test sync agent groups get py should be adapted to the new modifications adding the new cases and changing the expected output of the test without condition case where it was expected to fail and now it should work just fine proposed test cases sync agent groups get condition is optional and group hash added gherkin given a wazuh manager with a wazuh agent connected and the wazuh agent is assigned to groups when the query is made to wazuh db then wazuh db responds examples input output global sync agent groups get get global hash true hash global sync agent groups get global sync agent groups get condition sync status get global hash true hash | 1 |
175,545 | 27,878,583,815 | IssuesEvent | 2023-03-21 17:37:51 | WordPress/gutenberg | https://api.github.com/repos/WordPress/gutenberg | opened | Cover block: consolidate settings into one panel and remove Settings | [Type] Bug [Feature] Block API [Feature] Blocks [Feature] Design Tools | ### Description
With the addition of split settings https://github.com/WordPress/gutenberg/issues/40204 followed by the work to consolidate the settings when there's only an Advanced section https://github.com/WordPress/gutenberg/issues/47463, the Cover block shouldn't show split options. Right now, it does. Adding to 6.2 board since this was introduced in this release cycle.
### Step-by-step reproduction instructions
1. Add a cover block.
2. Notice that the settings are split but the settings tab only shows advanced section.
### Screenshots, screen recording, code snippet
<img width="1244" alt="Screen Shot 2023-03-21 at 10 35 33 AM" src="https://user-images.githubusercontent.com/26996883/226694817-ed45eca2-dc45-44ef-aaf6-2ed251bd2c54.png">
### Environment info
- WP 6.2 RC2
- No GB
### Please confirm that you have searched existing issues in the repo.
Yes
### Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes | 1.0 | Cover block: consolidate settings into one panel and remove Settings - ### Description
With the addition of split settings https://github.com/WordPress/gutenberg/issues/40204 followed by the work to consolidate the settings when there's only an Advanced section https://github.com/WordPress/gutenberg/issues/47463, the Cover block shouldn't show split options. Right now, it does. Adding to 6.2 board since this was introduced in this release cycle.
### Step-by-step reproduction instructions
1. Add a cover block.
2. Notice that the settings are split but the settings tab only shows advanced section.
### Screenshots, screen recording, code snippet
<img width="1244" alt="Screen Shot 2023-03-21 at 10 35 33 AM" src="https://user-images.githubusercontent.com/26996883/226694817-ed45eca2-dc45-44ef-aaf6-2ed251bd2c54.png">
### Environment info
- WP 6.2 RC2
- No GB
### Please confirm that you have searched existing issues in the repo.
Yes
### Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes | non_test | cover block consolidate settings into one panel and remove settings description with the addition of split settings followed by the work to consolidate the settings when there s only an advanced section the cover block shouldn t show split options right now it does adding to board since this was introduced in this release cycle step by step reproduction instructions add a cover block notice that the settings are split but the settings tab only shows advanced section screenshots screen recording code snippet img width alt screen shot at am src environment info wp no gb please confirm that you have searched existing issues in the repo yes please confirm that you have tested with all plugins deactivated except gutenberg yes | 0 |
717,663 | 24,686,281,711 | IssuesEvent | 2022-10-19 03:55:46 | wso2/product-microgateway | https://api.github.com/repos/wso2/product-microgateway | opened | Enable security for prototyped APIs | Type/Improvement Priority/Normal Choreo | ### Problem
Currently authentication is not required for APIs with prototyped lifecyclestatus within choreo connect. Since prototyped lifecycle state is changed to PreRelease, we need to enable authentication for those APIs.
### Solution
Currently auth filter is not engaged for prototyped APIs. We need to change that logic such that auth filter is engaged.
### Implementation
_No response_
### Related Issues
_No response_
### Suggested Labels
_No response_ | 1.0 | Enable security for prototyped APIs - ### Problem
Currently authentication is not required for APIs with prototyped lifecyclestatus within choreo connect. Since prototyped lifecycle state is changed to PreRelease, we need to enable authentication for those APIs.
### Solution
Currently auth filter is not engaged for prototyped APIs. We need to change that logic such that auth filter is engaged.
### Implementation
_No response_
### Related Issues
_No response_
### Suggested Labels
_No response_ | non_test | enable security for prototyped apis problem currently authentication is not required for apis with prototyped lifecyclestatus within choreo connect since prototyped lifecycle state is changed to prerelease we need to enable authentication for those apis solution currently auth filter is not engaged for prototyped apis we need to change that logic such that auth filter is engaged implementation no response related issues no response suggested labels no response | 0 |
63,431 | 17,648,563,625 | IssuesEvent | 2021-08-20 09:51:14 | vector-im/element-web | https://api.github.com/repos/vector-im/element-web | opened | Read Receipts are sent when a user is changing its own settings | T-Defect | ### Steps to reproduce
1. View a room
2. Open any modal, that will obstruct the room view (user settings, preferences, room settings, ...)
3. Wait for a new message to be received
### What happened?
The read receipt is sent directly and the notification count is decremented
### What did you expect?
For the notification count to remain the same and the read receipts to not be sent until the modal is closed and I can actually lay my eyes on the event
### Operating system
_No response_
### Browser information
_No response_
### URL for webapp
app.element.io
### Have you submitted a rageshake?
No | 1.0 | Read Receipts are sent when a user is changing its own settings - ### Steps to reproduce
1. View a room
2. Open any modal, that will obstruct the room view (user settings, preferences, room settings, ...)
3. Wait for a new message to be received
### What happened?
The read receipt is sent directly and the notification count is decremented
### What did you expect?
For the notification count to remain the same and the read receipts to not be sent until the modal is closed and I can actually lay my eyes on the event
### Operating system
_No response_
### Browser information
_No response_
### URL for webapp
app.element.io
### Have you submitted a rageshake?
No | non_test | read receipts are sent when a user is changing its own settings steps to reproduce view a room open any modal that will obstruct the room view user settings preferences room settings wait for a new message to be received what happened the read receipt is sent directly and the notification count is decremented what did you expect for the notification count to remain the same and the read receipts to not be sent until the modal is closed and i can actually lay my eyes on the event operating system no response browser information no response url for webapp app element io have you submitted a rageshake no | 0 |
213,876 | 16,542,409,163 | IssuesEvent | 2021-05-27 18:37:14 | hzi-braunschweig/SORMAS-Project | https://api.github.com/repos/hzi-braunschweig/SORMAS-Project | closed | Create the creation flow of person, contact, case, event, sample and task using the REST API | contacts e2e-tests events laboratory persons rest-api task tasks |
### Proposed Solution
Cover the basic creation of person, contact, case, event, sample and task using using the '/push' endpoint for each | 1.0 | Create the creation flow of person, contact, case, event, sample and task using the REST API -
### Proposed Solution
Cover the basic creation of person, contact, case, event, sample and task using using the '/push' endpoint for each | test | create the creation flow of person contact case event sample and task using the rest api proposed solution cover the basic creation of person contact case event sample and task using using the push endpoint for each | 1 |
16,778 | 9,527,270,682 | IssuesEvent | 2019-04-29 02:51:17 | MUMT-IT/mis2018 | https://api.github.com/repos/MUMT-IT/mis2018 | opened | Index ของ ComHealth เริ่มโหลดช้า | performance issue | น่าจะเป็นที่โหลดรายการทั้งหมดและต้อง filter ด้วย JavaScript ใน template ควรปรับให้ query ตัวเลขจำนวนโดยตรงจากฐานข้อมูลน่าจะทำให้การโหลดไวมากขึ้น | True | Index ของ ComHealth เริ่มโหลดช้า - น่าจะเป็นที่โหลดรายการทั้งหมดและต้อง filter ด้วย JavaScript ใน template ควรปรับให้ query ตัวเลขจำนวนโดยตรงจากฐานข้อมูลน่าจะทำให้การโหลดไวมากขึ้น | non_test | index ของ comhealth เริ่มโหลดช้า น่าจะเป็นที่โหลดรายการทั้งหมดและต้อง filter ด้วย javascript ใน template ควรปรับให้ query ตัวเลขจำนวนโดยตรงจากฐานข้อมูลน่าจะทำให้การโหลดไวมากขึ้น | 0 |
96,158 | 8,598,238,929 | IssuesEvent | 2018-11-15 21:09:47 | WikiWatershed/model-my-watershed | https://api.github.com/repos/WikiWatershed/model-my-watershed | closed | Unit Conversion: Set User Preferred Units | NSF Unit Conversion User Accounts tested/verified | Add a variable to the `user` object that is their preferred unit scheme, Metric or US Customary. Make it so that this is saved to the database, and read at load. Add a section in the User Account section to be able to set preferred units.
The default should be Metric. Users that are not logged in will not be able to change to US Customary. | 1.0 | Unit Conversion: Set User Preferred Units - Add a variable to the `user` object that is their preferred unit scheme, Metric or US Customary. Make it so that this is saved to the database, and read at load. Add a section in the User Account section to be able to set preferred units.
The default should be Metric. Users that are not logged in will not be able to change to US Customary. | test | unit conversion set user preferred units add a variable to the user object that is their preferred unit scheme metric or us customary make it so that this is saved to the database and read at load add a section in the user account section to be able to set preferred units the default should be metric users that are not logged in will not be able to change to us customary | 1 |
561,030 | 16,609,734,445 | IssuesEvent | 2021-06-02 09:58:51 | jina-ai/jina | https://api.github.com/repos/jina-ai/jina | closed | Connect Flow to existing running Pod | area/network epic/2.0 priority/important-soon type/feature-request | As a user of Jina I would like to connect a Flow to an existing Pod, as discussed [here], (https://jinaai.slack.com/archives/C018F60RBL5/p1622135612117500) right now, the Flow only spawns new Pods
| 1.0 | Connect Flow to existing running Pod - As a user of Jina I would like to connect a Flow to an existing Pod, as discussed [here], (https://jinaai.slack.com/archives/C018F60RBL5/p1622135612117500) right now, the Flow only spawns new Pods
| non_test | connect flow to existing running pod as a user of jina i would like to connect a flow to an existing pod as discussed right now the flow only spawns new pods | 0 |
38,228 | 5,169,894,105 | IssuesEvent | 2017-01-18 03:01:26 | bitshares/bitshares-core | https://api.github.com/repos/bitshares/bitshares-core | closed | If no valid, up to date, price feed then.... | needs testing | _From @vikramrajkumar on June 9, 2015 17:40_
> No new shorts No forced settling No margin calls.
>
> TODO: create test.
_Copied from original issue: cryptonomex/graphene#8_ | 1.0 | If no valid, up to date, price feed then.... - _From @vikramrajkumar on June 9, 2015 17:40_
> No new shorts No forced settling No margin calls.
>
> TODO: create test.
_Copied from original issue: cryptonomex/graphene#8_ | test | if no valid up to date price feed then from vikramrajkumar on june no new shorts no forced settling no margin calls todo create test copied from original issue cryptonomex graphene | 1 |
190,102 | 14,533,106,291 | IssuesEvent | 2020-12-14 23:47:53 | rancher/dashboard | https://api.github.com/repos/rancher/dashboard | closed | Scheduled scan's Config page does not show the values of the scheduled scan created | [zube]: To Test area/cis kind/bug product/cis | **On 2.5-head - commit id: `7e386ebab3f`**
- Deploy CIS v2
- Create a scheduled scan
<img width="1422" alt="Screen Shot 2020-12-04 at 2 01 38 PM" src="https://user-images.githubusercontent.com/26032343/101219691-3e3aaa80-3639-11eb-87e6-1313c479e205.png">
- Click on the scan to go to the Scan CR's details page, on the top right, click on Config.
<img width="1438" alt="Screen Shot 2020-12-04 at 2 01 57 PM" src="https://user-images.githubusercontent.com/26032343/101219718-498dd600-3639-11eb-8fd3-0f061079b380.png">
- Selected values while creating the scheduled scan are NOT available | 1.0 | Scheduled scan's Config page does not show the values of the scheduled scan created - **On 2.5-head - commit id: `7e386ebab3f`**
- Deploy CIS v2
- Create a scheduled scan
<img width="1422" alt="Screen Shot 2020-12-04 at 2 01 38 PM" src="https://user-images.githubusercontent.com/26032343/101219691-3e3aaa80-3639-11eb-87e6-1313c479e205.png">
- Click on the scan to go to the Scan CR's details page, on the top right, click on Config.
<img width="1438" alt="Screen Shot 2020-12-04 at 2 01 57 PM" src="https://user-images.githubusercontent.com/26032343/101219718-498dd600-3639-11eb-8fd3-0f061079b380.png">
- Selected values while creating the scheduled scan are NOT available | test | scheduled scan s config page does not show the values of the scheduled scan created on head commit id deploy cis create a scheduled scan img width alt screen shot at pm src click on the scan to go to the scan cr s details page on the top right click on config img width alt screen shot at pm src selected values while creating the scheduled scan are not available | 1 |
83,933 | 24,173,360,169 | IssuesEvent | 2022-09-22 21:33:18 | microsoft/onnxruntime | https://api.github.com/repos/microsoft/onnxruntime | opened | [Build] Onnxruntime C++ samples do not build off Cmake installed onnxruntime | build | ### Describe the issue
Build and install onnxruntime from source with `CMAKE_PREFIX` defined
Install it and trying building samples. Imagenet `main.cc` fails to include `cpu_provider.h` because it is not installed my cmake install process.
### Urgency
_No response_
### Target platform
Windows
### Build script
.\build.bat --build_dir .\cpu_build --config Debug --cmake_generator "Visual Studio 17 2022" --build_shared_lib --parallel 11 --skip_submodule_sync --cmake_extra_defines CMAKE_INSTALL_PREFIX=D:\dev\oss\onnxruntime_debug
### Error / output
1>D:\dev\onnxruntime-inference-examples\c_cxx\include\providers.h(5,10): fatal error C1083: Cannot open include file: 'cpu_provider_factory.h': No such file or directory
### Visual Studio Version
2022
### GCC / Compiler Version
_No response_ | 1.0 | [Build] Onnxruntime C++ samples do not build off Cmake installed onnxruntime - ### Describe the issue
Build and install onnxruntime from source with `CMAKE_PREFIX` defined
Install it and trying building samples. Imagenet `main.cc` fails to include `cpu_provider.h` because it is not installed my cmake install process.
### Urgency
_No response_
### Target platform
Windows
### Build script
.\build.bat --build_dir .\cpu_build --config Debug --cmake_generator "Visual Studio 17 2022" --build_shared_lib --parallel 11 --skip_submodule_sync --cmake_extra_defines CMAKE_INSTALL_PREFIX=D:\dev\oss\onnxruntime_debug
### Error / output
1>D:\dev\onnxruntime-inference-examples\c_cxx\include\providers.h(5,10): fatal error C1083: Cannot open include file: 'cpu_provider_factory.h': No such file or directory
### Visual Studio Version
2022
### GCC / Compiler Version
_No response_ | non_test | onnxruntime c samples do not build off cmake installed onnxruntime describe the issue build and install onnxruntime from source with cmake prefix defined install it and trying building samples imagenet main cc fails to include cpu provider h because it is not installed my cmake install process urgency no response target platform windows build script build bat build dir cpu build config debug cmake generator visual studio build shared lib parallel skip submodule sync cmake extra defines cmake install prefix d dev oss onnxruntime debug error output d dev onnxruntime inference examples c cxx include providers h fatal error cannot open include file cpu provider factory h no such file or directory visual studio version gcc compiler version no response | 0 |
82,019 | 7,810,175,336 | IssuesEvent | 2018-06-12 05:22:22 | jruby/jruby | https://api.github.com/repos/jruby/jruby | closed | AsciidoctorJ fails on JRuby 9.2.0.0 | java integration regression tests | ### Environment
JRuby 9.2.0.0
OS X: Darwin Roberts-MacBook-Air.local 17.5.0 Darwin Kernel Version 17.5.0: Fri Apr 13 19:32:32 PDT 2018; root:xnu-4570.51.2~1/RELEASE_X86_64 x86_64
### Expected Behavior
I tried upgrading the dependency in AsciidoctorJ to 9.2.0.0 and expected the build to run.
### Actual Behavior
As soon as the Asciidoctor instance is created, it fails with a java.lang.VerifyError:
```
java.lang.VerifyError: Bad return type
Exception Details:
Location:
org/jruby/gen/InterfaceImpl659984099.converters()Lorg/jruby/RubyArray; @45: areturn
Reason:
Type 'org/jruby/runtime/builtin/IRubyObject' (current frame, stack[0]) is not assignable to 'org/jruby/RubyArray' (from method signature)
Current Frame:
bci: @45
flags: { }
locals: { 'org/jruby/gen/InterfaceImpl659984099', 'org/jruby/runtime/builtin/IRubyObject', 'org/jruby/Ruby' }
stack: { 'org/jruby/runtime/builtin/IRubyObject' }
Bytecode:
0000000: 2ab4 0015 4c2b b900 1d01 004d b200 1f2b
0000010: 126e 126f b600 272c b600 2d2b 2bb9 0031
0000020: 0100 126f b200 73b2 003d b600 43b0
at java.base/java.lang.Class.getDeclaredConstructors0(Native Method)
at java.base/java.lang.Class.privateGetDeclaredConstructors(Class.java:3090)
at java.base/java.lang.Class.getConstructor0(Class.java:3295)
at java.base/java.lang.Class.getConstructor(Class.java:2110)
at org.jruby.javasupport.Java.newInterfaceImpl(Java.java:1352)
at org.jruby.java.proxies.JavaInterfaceTemplate.newInterfaceProxy(JavaInterfaceTemplate.java:285)
at org.jruby.java.proxies.JavaInterfaceTemplate.access$100(JavaInterfaceTemplate.java:34)
at org.jruby.java.proxies.JavaInterfaceTemplate$InterfaceProxyFactory.call(JavaInterfaceTemplate.java:233)
at org.jruby.internal.runtime.methods.DynamicMethod.call(DynamicMethod.java:194)
at org.jruby.RubyClass.finvoke(RubyClass.java:560)
at org.jruby.runtime.Helpers.invoke(Helpers.java:353)
at org.jruby.javasupport.JavaUtil.convertProcToInterface(JavaUtil.java:278)
at org.jruby.RubyBasicObject.defaultToJava(RubyBasicObject.java:898)
at org.jruby.RubyBasicObject.toJava(RubyBasicObject.java:876)
at org.jruby.javasupport.JavaEmbedUtils.rubyToJava(JavaEmbedUtils.java:247)
at org.asciidoctor.internal.RubyUtils.rubyToJava(RubyUtils.java:19)
at org.asciidoctor.internal.JRubyAsciidoctorModuleFactory.createAsciidoctorModule(JRubyAsciidoctorModuleFactory.java:27)
...
```
At the moment the "glue" between the Java API and the Asciidoctor Ruby implementation is moved to JRuby, by having a Java interface `AsciidoctorModule` [1] and a Ruby class `AsciidoctorModule`[2] and letting JRuby implement this interface for this Ruby class [3].
It looks like this fails now exactly where JRuby creates the proxy for this interface.
I created a test repository at https://github.com/robertpanzer/jruby92test where I also tried to reproduce the error with a simplified version, but there it succeeds.
The repo also contains a test with Asciidoctor though, and that one fails.
Maybe you have an idea if we did sth wrong in AsciidoctorJ or if this is a real bug.
For the future I am considering to remove the dynamic implementation of this interface anyway, so that I have a workaround (https://github.com/asciidoctor/asciidoctorj/pull/652), but it would still be nice to know to cause of this error.
[1] https://github.com/asciidoctor/asciidoctorj/blob/master/asciidoctorj-core/src/main/java/org/asciidoctor/internal/AsciidoctorModule.java
[2] https://github.com/asciidoctor/asciidoctorj/blob/master/asciidoctorj-core/src/main/resources/org/asciidoctor/internal/asciidoctorclass.rb
[3] https://github.com/asciidoctor/asciidoctorj/blob/master/asciidoctorj-core/src/main/java/org/asciidoctor/internal/JRubyAsciidoctorModuleFactory.java#L27
| 1.0 | AsciidoctorJ fails on JRuby 9.2.0.0 - ### Environment
JRuby 9.2.0.0
OS X: Darwin Roberts-MacBook-Air.local 17.5.0 Darwin Kernel Version 17.5.0: Fri Apr 13 19:32:32 PDT 2018; root:xnu-4570.51.2~1/RELEASE_X86_64 x86_64
### Expected Behavior
I tried upgrading the dependency in AsciidoctorJ to 9.2.0.0 and expected the build to run.
### Actual Behavior
As soon as the Asciidoctor instance is created, it fails with a java.lang.VerifyError:
```
java.lang.VerifyError: Bad return type
Exception Details:
Location:
org/jruby/gen/InterfaceImpl659984099.converters()Lorg/jruby/RubyArray; @45: areturn
Reason:
Type 'org/jruby/runtime/builtin/IRubyObject' (current frame, stack[0]) is not assignable to 'org/jruby/RubyArray' (from method signature)
Current Frame:
bci: @45
flags: { }
locals: { 'org/jruby/gen/InterfaceImpl659984099', 'org/jruby/runtime/builtin/IRubyObject', 'org/jruby/Ruby' }
stack: { 'org/jruby/runtime/builtin/IRubyObject' }
Bytecode:
0000000: 2ab4 0015 4c2b b900 1d01 004d b200 1f2b
0000010: 126e 126f b600 272c b600 2d2b 2bb9 0031
0000020: 0100 126f b200 73b2 003d b600 43b0
at java.base/java.lang.Class.getDeclaredConstructors0(Native Method)
at java.base/java.lang.Class.privateGetDeclaredConstructors(Class.java:3090)
at java.base/java.lang.Class.getConstructor0(Class.java:3295)
at java.base/java.lang.Class.getConstructor(Class.java:2110)
at org.jruby.javasupport.Java.newInterfaceImpl(Java.java:1352)
at org.jruby.java.proxies.JavaInterfaceTemplate.newInterfaceProxy(JavaInterfaceTemplate.java:285)
at org.jruby.java.proxies.JavaInterfaceTemplate.access$100(JavaInterfaceTemplate.java:34)
at org.jruby.java.proxies.JavaInterfaceTemplate$InterfaceProxyFactory.call(JavaInterfaceTemplate.java:233)
at org.jruby.internal.runtime.methods.DynamicMethod.call(DynamicMethod.java:194)
at org.jruby.RubyClass.finvoke(RubyClass.java:560)
at org.jruby.runtime.Helpers.invoke(Helpers.java:353)
at org.jruby.javasupport.JavaUtil.convertProcToInterface(JavaUtil.java:278)
at org.jruby.RubyBasicObject.defaultToJava(RubyBasicObject.java:898)
at org.jruby.RubyBasicObject.toJava(RubyBasicObject.java:876)
at org.jruby.javasupport.JavaEmbedUtils.rubyToJava(JavaEmbedUtils.java:247)
at org.asciidoctor.internal.RubyUtils.rubyToJava(RubyUtils.java:19)
at org.asciidoctor.internal.JRubyAsciidoctorModuleFactory.createAsciidoctorModule(JRubyAsciidoctorModuleFactory.java:27)
...
```
At the moment the "glue" between the Java API and the Asciidoctor Ruby implementation is moved to JRuby, by having a Java interface `AsciidoctorModule` [1] and a Ruby class `AsciidoctorModule`[2] and letting JRuby implement this interface for this Ruby class [3].
It looks like this fails now exactly where JRuby creates the proxy for this interface.
I created a test repository at https://github.com/robertpanzer/jruby92test where I also tried to reproduce the error with a simplified version, but there it succeeds.
The repo also contains a test with Asciidoctor though, and that one fails.
Maybe you have an idea if we did sth wrong in AsciidoctorJ or if this is a real bug.
For the future I am considering to remove the dynamic implementation of this interface anyway, so that I have a workaround (https://github.com/asciidoctor/asciidoctorj/pull/652), but it would still be nice to know to cause of this error.
[1] https://github.com/asciidoctor/asciidoctorj/blob/master/asciidoctorj-core/src/main/java/org/asciidoctor/internal/AsciidoctorModule.java
[2] https://github.com/asciidoctor/asciidoctorj/blob/master/asciidoctorj-core/src/main/resources/org/asciidoctor/internal/asciidoctorclass.rb
[3] https://github.com/asciidoctor/asciidoctorj/blob/master/asciidoctorj-core/src/main/java/org/asciidoctor/internal/JRubyAsciidoctorModuleFactory.java#L27
| test | asciidoctorj fails on jruby environment jruby os x darwin roberts macbook air local darwin kernel version fri apr pdt root xnu release expected behavior i tried upgrading the dependency in asciidoctorj to and expected the build to run actual behavior as soon as the asciidoctor instance is created it fails with a java lang verifyerror java lang verifyerror bad return type exception details location org jruby gen converters lorg jruby rubyarray areturn reason type org jruby runtime builtin irubyobject current frame stack is not assignable to org jruby rubyarray from method signature current frame bci flags locals org jruby gen org jruby runtime builtin irubyobject org jruby ruby stack org jruby runtime builtin irubyobject bytecode at java base java lang class native method at java base java lang class privategetdeclaredconstructors class java at java base java lang class class java at java base java lang class getconstructor class java at org jruby javasupport java newinterfaceimpl java java at org jruby java proxies javainterfacetemplate newinterfaceproxy javainterfacetemplate java at org jruby java proxies javainterfacetemplate access javainterfacetemplate java at org jruby java proxies javainterfacetemplate interfaceproxyfactory call javainterfacetemplate java at org jruby internal runtime methods dynamicmethod call dynamicmethod java at org jruby rubyclass finvoke rubyclass java at org jruby runtime helpers invoke helpers java at org jruby javasupport javautil convertproctointerface javautil java at org jruby rubybasicobject defaulttojava rubybasicobject java at org jruby rubybasicobject tojava rubybasicobject java at org jruby javasupport javaembedutils rubytojava javaembedutils java at org asciidoctor internal rubyutils rubytojava rubyutils java at org asciidoctor internal jrubyasciidoctormodulefactory createasciidoctormodule jrubyasciidoctormodulefactory java at the moment the glue between the java api and the asciidoctor ruby implementation is moved to jruby by having a java interface asciidoctormodule and a ruby class asciidoctormodule and letting jruby implement this interface for this ruby class it looks like this fails now exactly where jruby creates the proxy for this interface i created a test repository at where i also tried to reproduce the error with a simplified version but there it succeeds the repo also contains a test with asciidoctor though and that one fails maybe you have an idea if we did sth wrong in asciidoctorj or if this is a real bug for the future i am considering to remove the dynamic implementation of this interface anyway so that i have a workaround but it would still be nice to know to cause of this error | 1 |
193,350 | 6,884,142,412 | IssuesEvent | 2017-11-21 11:55:23 | ZeusWPI/MOZAIC | https://api.github.com/repos/ZeusWPI/MOZAIC | closed | Log format | botdriver discussion priority:medium | Now that we should try to decide on an universal logger interface, it is important to think about the logging format that we want to support.
As usual, being more restrictive will give the framework more power, but being permissive is just, well, generally being nice.
The most important considerations, according to me™:
- Do we force a line-based format
- Do we force a JSON-based format
- Do we force having a record for each turn played
| 1.0 | Log format - Now that we should try to decide on an universal logger interface, it is important to think about the logging format that we want to support.
As usual, being more restrictive will give the framework more power, but being permissive is just, well, generally being nice.
The most important considerations, according to me™:
- Do we force a line-based format
- Do we force a JSON-based format
- Do we force having a record for each turn played
| non_test | log format now that we should try to decide on an universal logger interface it is important to think about the logging format that we want to support as usual being more restrictive will give the framework more power but being permissive is just well generally being nice the most important considerations according to me™ do we force a line based format do we force a json based format do we force having a record for each turn played | 0 |
10,584 | 4,074,267,377 | IssuesEvent | 2016-05-28 09:55:08 | SleepyTrousers/EnderIO | https://api.github.com/repos/SleepyTrousers/EnderIO | closed | Insane Amounts of XP EnderIO -1.7.10-2.2.6.313_beta | bug Code Complete | When ever i manually put in any dusts to be smelted in the alloy smelter in furnace mode and then pick it up once it has smelted up - 3 ingots picked up == to 17 LEVELS.
XP gain increases the more ingots i pick up at in one go from the smelter
EDIT: Seems to be happening with any ore from thermal foundation even if it is directly smelted, | 1.0 | Insane Amounts of XP EnderIO -1.7.10-2.2.6.313_beta - When ever i manually put in any dusts to be smelted in the alloy smelter in furnace mode and then pick it up once it has smelted up - 3 ingots picked up == to 17 LEVELS.
XP gain increases the more ingots i pick up at in one go from the smelter
EDIT: Seems to be happening with any ore from thermal foundation even if it is directly smelted, | non_test | insane amounts of xp enderio beta when ever i manually put in any dusts to be smelted in the alloy smelter in furnace mode and then pick it up once it has smelted up ingots picked up to levels xp gain increases the more ingots i pick up at in one go from the smelter edit seems to be happening with any ore from thermal foundation even if it is directly smelted | 0 |
246,516 | 7,895,384,203 | IssuesEvent | 2018-06-29 02:55:48 | aowen87/BAR | https://api.github.com/repos/aowen87/BAR | closed | Add a parallel mxterm host profile to all the LLNL hosts it makes sense for. | Expected Use: 3 - Occasional Feature Impact: 3 - Medium OS: All Priority: Normal Support Group: Any | Add a parallel mxterm host profile to all the LLNL hosts it makes sense for.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. The following information
could not be accurately captured in the new ticket:
Original author: Eric Brugger
Original creation: 03/30/2015 07:24 pm
Original update: 03/30/2015 07:46 pm
Ticket number: 2195 | 1.0 | Add a parallel mxterm host profile to all the LLNL hosts it makes sense for. - Add a parallel mxterm host profile to all the LLNL hosts it makes sense for.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. The following information
could not be accurately captured in the new ticket:
Original author: Eric Brugger
Original creation: 03/30/2015 07:24 pm
Original update: 03/30/2015 07:46 pm
Ticket number: 2195 | non_test | add a parallel mxterm host profile to all the llnl hosts it makes sense for add a parallel mxterm host profile to all the llnl hosts it makes sense for redmine migration this ticket was migrated from redmine the following information could not be accurately captured in the new ticket original author eric brugger original creation pm original update pm ticket number | 0 |
365,794 | 25,552,105,953 | IssuesEvent | 2022-11-30 01:13:57 | saltstack/salt | https://api.github.com/repos/saltstack/salt | closed | [BUG] Latest available pygit2 from Debian 11 and Pypi break GitFS | Documentation | **Description**
The version of pygit2 included with Debian 11 (v1.4.0) only allows for RSA PEM keys (see [this issue](https://github.com/libgit2/pygit2/issues/1013)) and sends them with SHA-1 regardless of if they are SHA-256 or SHA-512 keys. GitHub has disabled all use of RSA SHA-1 keys.
As of today (3/15/2022), RSA SHA-1 keys are not allowed: https://github.blog/2021-09-01-improving-git-protocol-security-github/
**Setup**
(Please provide relevant configs and/or SLS files (be sure to remove sensitive info. There is no general set-up of Salt.)
Please be as specific as possible and give set-up details.
- [ ] on-prem machine
- [x] VM (Virtualbox, KVM, etc. please specify): VMWare
- [ ] VM running on a cloud service, please be explicit and add details
- [ ] container (Kubernetes, Docker, containerd, etc. please specify)
- [ ] or a combination, please be explicit
- [ ] jails if it is FreeBSD
**Steps to Reproduce the behavior**
1. First try a normal RSA key: `ssh-keygen -m PEM -t rsa -b 4096`
2. Also try a SHA-512 RSA key: `ssh-keygen -m PEM -t rsa -E sha512 -b 4096`
3. Also try a SHA-256 RSA key: `ssh-keygen -m PEM -t rsa -E sha256 -b 4096`
4. Also try an ed25519 key: `ssh-keygen -m PEM -a 100 -t ed25519 -E sha512`
5. Configure these keys as deploy keys for a private repo on GitHub
6. Configure a remote repo:
```yaml
fileserver_backend:
- gitfs
gitfs_provider: pygit2
gitfs_remotes:
- ssh://git@github.com/myorg/my-private-repo.git:
- base: main
- pubkey: /root/.ssh/id_my-key.pub
- privkey: /root/.ssh/id_my-key
```
7. Restart salt master
8. Try to pull `salt-run fileserver.update`
With any RSA key, you will see:
```
[ERROR ] Error occurred fetching gitfs remote 'ssh://git@github.com/myorg/my-private-repo.git': ERROR: You're using an RSA key with SHA-1, which is no longer allowed. Please use a newer client or a different key type.
Please see https://github.blog/2021-09-01-improving-git-protocol-security-github/ for more information.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/salt/utils/gitfs.py", line 1870, in _fetch
fetch_results = origin.fetch(**fetch_kwargs)
File "/usr/lib/python3/dist-packages/pygit2/remote.py", line 128, in fetch
payload.check_error(err)
File "/usr/lib/python3/dist-packages/pygit2/callbacks.py", line 93, in check_error
check_error(error_code)
File "/usr/lib/python3/dist-packages/pygit2/errors.py", line 65, in check_error
raise GitError(message)
_pygit2.GitError: ERROR: You're using an RSA key with SHA-1, which is no longer allowed. Please use a newer client or a different key type.
Please see https://github.blog/2021-09-01-improving-git-protocol-security-github/ for more information.
```
With any non-RSA key you will see:
```
[ERROR ] Error occurred fetching gitfs remote 'ssh://git@github.com/myorg/my-private-repo.git': callback failed to initialize SSH credentials
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/salt/utils/gitfs.py", line 1870, in _fetch
fetch_results = origin.fetch(**fetch_kwargs)
File "/usr/lib/python3/dist-packages/pygit2/remote.py", line 128, in fetch
payload.check_error(err)
File "/usr/lib/python3/dist-packages/pygit2/callbacks.py", line 93, in check_error
check_error(error_code)
File "/usr/lib/python3/dist-packages/pygit2/errors.py", line 65, in check_error
raise GitError(message)
_pygit2.GitError: callback failed to initialize SSH credentials
```
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Versions Report**
<details><summary>salt --versions-report</summary>
(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)
```yaml
Salt Version:
Salt: 3004
Dependency Versions:
cffi: Not Installed
cherrypy: Not Installed
dateutil: 2.8.1
docker-py: Not Installed
gitdb: 4.0.5
gitpython: 3.1.14
Jinja2: 2.11.3
libgit2: 1.1.0
M2Crypto: Not Installed
Mako: Not Installed
msgpack: 1.0.0
msgpack-pure: Not Installed
mysql-python: Not Installed
pycparser: Not Installed
pycrypto: Not Installed
pycryptodome: 3.9.7
pygit2: 1.4.0
Python: 3.9.2 (default, Feb 28 2021, 17:03:44)
python-gnupg: Not Installed
PyYAML: 5.3.1
PyZMQ: 20.0.0
smmap: 4.0.0
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.3.4
System Versions:
dist: debian 11 bullseye
locale: utf-8
machine: x86_64
release: 5.10.0-12-amd64
system: Linux
version: Debian GNU/Linux 11 bullseye
```
</details>
**Additional context**
Add any other context about the problem here.
| 1.0 | [BUG] Latest available pygit2 from Debian 11 and Pypi break GitFS - **Description**
The version of pygit2 included with Debian 11 (v1.4.0) only allows for RSA PEM keys (see [this issue](https://github.com/libgit2/pygit2/issues/1013)) and sends them with SHA-1 regardless of if they are SHA-256 or SHA-512 keys. GitHub has disabled all use of RSA SHA-1 keys.
As of today (3/15/2022), RSA SHA-1 keys are not allowed: https://github.blog/2021-09-01-improving-git-protocol-security-github/
**Setup**
(Please provide relevant configs and/or SLS files (be sure to remove sensitive info. There is no general set-up of Salt.)
Please be as specific as possible and give set-up details.
- [ ] on-prem machine
- [x] VM (Virtualbox, KVM, etc. please specify): VMWare
- [ ] VM running on a cloud service, please be explicit and add details
- [ ] container (Kubernetes, Docker, containerd, etc. please specify)
- [ ] or a combination, please be explicit
- [ ] jails if it is FreeBSD
**Steps to Reproduce the behavior**
1. First try a normal RSA key: `ssh-keygen -m PEM -t rsa -b 4096`
2. Also try a SHA-512 RSA key: `ssh-keygen -m PEM -t rsa -E sha512 -b 4096`
3. Also try a SHA-256 RSA key: `ssh-keygen -m PEM -t rsa -E sha256 -b 4096`
4. Also try an ed25519 key: `ssh-keygen -m PEM -a 100 -t ed25519 -E sha512`
5. Configure these keys as deploy keys for a private repo on GitHub
6. Configure a remote repo:
```yaml
fileserver_backend:
- gitfs
gitfs_provider: pygit2
gitfs_remotes:
- ssh://git@github.com/myorg/my-private-repo.git:
- base: main
- pubkey: /root/.ssh/id_my-key.pub
- privkey: /root/.ssh/id_my-key
```
7. Restart salt master
8. Try to pull `salt-run fileserver.update`
With any RSA key, you will see:
```
[ERROR ] Error occurred fetching gitfs remote 'ssh://git@github.com/myorg/my-private-repo.git': ERROR: You're using an RSA key with SHA-1, which is no longer allowed. Please use a newer client or a different key type.
Please see https://github.blog/2021-09-01-improving-git-protocol-security-github/ for more information.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/salt/utils/gitfs.py", line 1870, in _fetch
fetch_results = origin.fetch(**fetch_kwargs)
File "/usr/lib/python3/dist-packages/pygit2/remote.py", line 128, in fetch
payload.check_error(err)
File "/usr/lib/python3/dist-packages/pygit2/callbacks.py", line 93, in check_error
check_error(error_code)
File "/usr/lib/python3/dist-packages/pygit2/errors.py", line 65, in check_error
raise GitError(message)
_pygit2.GitError: ERROR: You're using an RSA key with SHA-1, which is no longer allowed. Please use a newer client or a different key type.
Please see https://github.blog/2021-09-01-improving-git-protocol-security-github/ for more information.
```
With any non-RSA key you will see:
```
[ERROR ] Error occurred fetching gitfs remote 'ssh://git@github.com/myorg/my-private-repo.git': callback failed to initialize SSH credentials
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/salt/utils/gitfs.py", line 1870, in _fetch
fetch_results = origin.fetch(**fetch_kwargs)
File "/usr/lib/python3/dist-packages/pygit2/remote.py", line 128, in fetch
payload.check_error(err)
File "/usr/lib/python3/dist-packages/pygit2/callbacks.py", line 93, in check_error
check_error(error_code)
File "/usr/lib/python3/dist-packages/pygit2/errors.py", line 65, in check_error
raise GitError(message)
_pygit2.GitError: callback failed to initialize SSH credentials
```
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Versions Report**
<details><summary>salt --versions-report</summary>
(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)
```yaml
Salt Version:
Salt: 3004
Dependency Versions:
cffi: Not Installed
cherrypy: Not Installed
dateutil: 2.8.1
docker-py: Not Installed
gitdb: 4.0.5
gitpython: 3.1.14
Jinja2: 2.11.3
libgit2: 1.1.0
M2Crypto: Not Installed
Mako: Not Installed
msgpack: 1.0.0
msgpack-pure: Not Installed
mysql-python: Not Installed
pycparser: Not Installed
pycrypto: Not Installed
pycryptodome: 3.9.7
pygit2: 1.4.0
Python: 3.9.2 (default, Feb 28 2021, 17:03:44)
python-gnupg: Not Installed
PyYAML: 5.3.1
PyZMQ: 20.0.0
smmap: 4.0.0
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.3.4
System Versions:
dist: debian 11 bullseye
locale: utf-8
machine: x86_64
release: 5.10.0-12-amd64
system: Linux
version: Debian GNU/Linux 11 bullseye
```
</details>
**Additional context**
Add any other context about the problem here.
| non_test | latest available from debian and pypi break gitfs description the version of included with debian only allows for rsa pem keys see and sends them with sha regardless of if they are sha or sha keys github has disabled all use of rsa sha keys as of today rsa sha keys are not allowed setup please provide relevant configs and or sls files be sure to remove sensitive info there is no general set up of salt please be as specific as possible and give set up details on prem machine vm virtualbox kvm etc please specify vmware vm running on a cloud service please be explicit and add details container kubernetes docker containerd etc please specify or a combination please be explicit jails if it is freebsd steps to reproduce the behavior first try a normal rsa key ssh keygen m pem t rsa b also try a sha rsa key ssh keygen m pem t rsa e b also try a sha rsa key ssh keygen m pem t rsa e b also try an key ssh keygen m pem a t e configure these keys as deploy keys for a private repo on github configure a remote repo yaml fileserver backend gitfs gitfs provider gitfs remotes ssh git github com myorg my private repo git base main pubkey root ssh id my key pub privkey root ssh id my key restart salt master try to pull salt run fileserver update with any rsa key you will see error occurred fetching gitfs remote ssh git github com myorg my private repo git error you re using an rsa key with sha which is no longer allowed please use a newer client or a different key type please see for more information traceback most recent call last file usr lib dist packages salt utils gitfs py line in fetch fetch results origin fetch fetch kwargs file usr lib dist packages remote py line in fetch payload check error err file usr lib dist packages callbacks py line in check error check error error code file usr lib dist packages errors py line in check error raise giterror message giterror error you re using an rsa key with sha which is no longer allowed please use a newer client or a different key type please see for more information with any non rsa key you will see error occurred fetching gitfs remote ssh git github com myorg my private repo git callback failed to initialize ssh credentials traceback most recent call last file usr lib dist packages salt utils gitfs py line in fetch fetch results origin fetch fetch kwargs file usr lib dist packages remote py line in fetch payload check error err file usr lib dist packages callbacks py line in check error check error error code file usr lib dist packages errors py line in check error raise giterror message giterror callback failed to initialize ssh credentials expected behavior a clear and concise description of what you expected to happen screenshots if applicable add screenshots to help explain your problem versions report salt versions report provided by running salt versions report please also mention any differences in master minion versions yaml salt version salt dependency versions cffi not installed cherrypy not installed dateutil docker py not installed gitdb gitpython not installed mako not installed msgpack msgpack pure not installed mysql python not installed pycparser not installed pycrypto not installed pycryptodome python default feb python gnupg not installed pyyaml pyzmq smmap timelib not installed tornado zmq system versions dist debian bullseye locale utf machine release system linux version debian gnu linux bullseye additional context add any other context about the problem here | 0 |
88,601 | 17,614,930,680 | IssuesEvent | 2021-08-18 08:33:07 | SAP/fundamental-ngx | https://api.github.com/repos/SAP/fundamental-ngx | opened | refactor(core,platform): table navigatable | code refactoring platform core table | #### Is this a bug, enhancement, or feature request?
Enhancement.
#### Briefly describe your proposal.
Navigatable feature of tables (core, platform) should be adjusted a bit
* In the core component, there is no ability to make row activable, hoverable if the row is not navigatable.
* In the platform component, there is no ability to make row navigatable without TS code, just from the template.
Also, one more feature requested
* Ability to trigger custom function on row navigation, not only go by the provided route.
#### Which versions of Angular and Fundamental Library for Angular are affected? (If this is a feature request, use current version.)
Latest
#### If this is a bug, please provide steps for reproducing it.
.
#### Please provide relevant source code if applicable.
.
#### Is there anything else we should know?
. | 1.0 | refactor(core,platform): table navigatable - #### Is this a bug, enhancement, or feature request?
Enhancement.
#### Briefly describe your proposal.
Navigatable feature of tables (core, platform) should be adjusted a bit
* In the core component, there is no ability to make row activable, hoverable if the row is not navigatable.
* In the platform component, there is no ability to make row navigatable without TS code, just from the template.
Also, one more feature requested
* Ability to trigger custom function on row navigation, not only go by the provided route.
#### Which versions of Angular and Fundamental Library for Angular are affected? (If this is a feature request, use current version.)
Latest
#### If this is a bug, please provide steps for reproducing it.
.
#### Please provide relevant source code if applicable.
.
#### Is there anything else we should know?
. | non_test | refactor core platform table navigatable is this a bug enhancement or feature request enhancement briefly describe your proposal navigatable feature of tables core platform should be adjusted a bit in the core component there is no ability to make row activable hoverable if the row is not navigatable in the platform component there is no ability to make row navigatable without ts code just from the template also one more feature requested ability to trigger custom function on row navigation not only go by the provided route which versions of angular and fundamental library for angular are affected if this is a feature request use current version latest if this is a bug please provide steps for reproducing it please provide relevant source code if applicable is there anything else we should know | 0 |
120,039 | 25,728,344,947 | IssuesEvent | 2022-12-07 18:14:36 | letsintegreat/Tagify | https://api.github.com/repos/letsintegreat/Tagify | closed | Improve Google Sign In | bug Codepeak22 | The google login option automatically uses the account last used by the user. It does not give the option to choose new account when signing out and logging in again.
Ask to be assigned in the comments below before starting to work on this issue. Stick to the contribution guidelines as mentioned in the README file. | 1.0 | Improve Google Sign In - The google login option automatically uses the account last used by the user. It does not give the option to choose new account when signing out and logging in again.
Ask to be assigned in the comments below before starting to work on this issue. Stick to the contribution guidelines as mentioned in the README file. | non_test | improve google sign in the google login option automatically uses the account last used by the user it does not give the option to choose new account when signing out and logging in again ask to be assigned in the comments below before starting to work on this issue stick to the contribution guidelines as mentioned in the readme file | 0 |
94,387 | 27,180,730,510 | IssuesEvent | 2023-02-18 15:47:33 | NixOS/nixpkgs | https://api.github.com/repos/NixOS/nixpkgs | closed | Build failure: `openimagedenoise` | 0.kind: build failure | ### Steps To Reproduce
Steps to reproduce the behavior:
1. build `openimagedenoise`
### Build log
```console
$ nix-channel --list
nixos https://nixos.org/channels/nixos-unstable
$ nix log /nix/store/2ay0ynwd7639msidi0f8xjbx518l7k4m-openimagedenoise-1.4.3.drv
@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking sources
unpacking source archive /nix/store/gjqcn7495q4sqd9cm6lg3fyy936dbsa7-source
source root is source
@nix { "action": "setPhase", "phase": "patchPhase" }
patching sources
@nix { "action": "setPhase", "phase": "configurePhase" }
configuring
fixing cmake files...
cmake flags: -DCMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTING=OFF -DCMAKE_INSTALL_LOCALEDIR=/nix/store/4p56q>
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /nix/store/l0fvy72hpfdpjjs3dk4112f57x7r3dlm-gcc-wrapper-12.2.0/bin/gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /nix/store/l0fvy72hpfdpjjs3dk4112f57x7r3dlm-gcc-wrapper-12.2.0/bin/g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PythonInterp: /nix/store/0pyymzxf7n0fzpaqnvwv92ab72v3jq8d-python3-3.10.9/bin/python (found version "3.10.9")
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Looking for TBB components tbb; ()
-- Found TBB version 2020.3 at /nix/store/6y5ms2chn50ksw6fbsig8jm62fimqspr-tbb-2020.3-dev
CMake Error at cmake/FindTBB.cmake:80 (message):
Cannot find required components: ;tbb
Call Stack (most recent call first):
cmake/FindTBB.cmake:487 (rk_tbb_error)
CMakeLists.txt:73 (find_package)
-- Configuring incomplete, errors occurred!
See also "/build/source/build/CMakeFiles/CMakeOutput.log".
```
### Additional context
Breaks `blender` since it depends on `openimagedenoise`
### Notify maintainers
<!--
Please @ people who are in the `meta.maintainers` list of the offending package or module.
If in doubt, check `git blame` for whoever last touched something.
-->
@LeshaInc (`openimagedenoise`); @thoughtpolice, @dizfer (`tbb`)
### Metadata
Please run `nix-shell -p nix-info --run "nix-info -m"` and paste the result.
```console
$ nix-shell -p nix-info --run "nix-info -m"
- system: `"x86_64-linux"`
- host os: `Linux 5.15.90, NixOS, 23.05 (Stoat), 23.05pre454549.545c7a31e5d`
- multi-user?: `yes`
- sandbox: `yes`
- version: `nix-env (Nix) 2.13.2`
- channels(USERNAME): `"home-manager"`
- channels(root): `"nixos"`
- nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`
```
| 1.0 | Build failure: `openimagedenoise` - ### Steps To Reproduce
Steps to reproduce the behavior:
1. build `openimagedenoise`
### Build log
```console
$ nix-channel --list
nixos https://nixos.org/channels/nixos-unstable
$ nix log /nix/store/2ay0ynwd7639msidi0f8xjbx518l7k4m-openimagedenoise-1.4.3.drv
@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking sources
unpacking source archive /nix/store/gjqcn7495q4sqd9cm6lg3fyy936dbsa7-source
source root is source
@nix { "action": "setPhase", "phase": "patchPhase" }
patching sources
@nix { "action": "setPhase", "phase": "configurePhase" }
configuring
fixing cmake files...
cmake flags: -DCMAKE_FIND_USE_SYSTEM_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTING=OFF -DCMAKE_INSTALL_LOCALEDIR=/nix/store/4p56q>
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /nix/store/l0fvy72hpfdpjjs3dk4112f57x7r3dlm-gcc-wrapper-12.2.0/bin/gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /nix/store/l0fvy72hpfdpjjs3dk4112f57x7r3dlm-gcc-wrapper-12.2.0/bin/g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PythonInterp: /nix/store/0pyymzxf7n0fzpaqnvwv92ab72v3jq8d-python3-3.10.9/bin/python (found version "3.10.9")
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Looking for TBB components tbb; ()
-- Found TBB version 2020.3 at /nix/store/6y5ms2chn50ksw6fbsig8jm62fimqspr-tbb-2020.3-dev
CMake Error at cmake/FindTBB.cmake:80 (message):
Cannot find required components: ;tbb
Call Stack (most recent call first):
cmake/FindTBB.cmake:487 (rk_tbb_error)
CMakeLists.txt:73 (find_package)
-- Configuring incomplete, errors occurred!
See also "/build/source/build/CMakeFiles/CMakeOutput.log".
```
### Additional context
Breaks `blender` since it depends on `openimagedenoise`
### Notify maintainers
<!--
Please @ people who are in the `meta.maintainers` list of the offending package or module.
If in doubt, check `git blame` for whoever last touched something.
-->
@LeshaInc (`openimagedenoise`); @thoughtpolice, @dizfer (`tbb`)
### Metadata
Please run `nix-shell -p nix-info --run "nix-info -m"` and paste the result.
```console
$ nix-shell -p nix-info --run "nix-info -m"
- system: `"x86_64-linux"`
- host os: `Linux 5.15.90, NixOS, 23.05 (Stoat), 23.05pre454549.545c7a31e5d`
- multi-user?: `yes`
- sandbox: `yes`
- version: `nix-env (Nix) 2.13.2`
- channels(USERNAME): `"home-manager"`
- channels(root): `"nixos"`
- nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`
```
| non_test | build failure openimagedenoise steps to reproduce steps to reproduce the behavior build openimagedenoise build log console nix channel list nixos nix log nix store openimagedenoise drv nix action setphase phase unpackphase unpacking sources unpacking source archive nix store source source root is source nix action setphase phase patchphase patching sources nix action setphase phase configurephase configuring fixing cmake files cmake flags dcmake find use system package registry off dcmake find use package registry off dcmake export no package registry on dcmake build type release dbuild testing off dcmake install localedir nix store the c compiler identification is gnu the cxx compiler identification is gnu detecting c compiler abi info detecting c compiler abi info done check for working c compiler nix store gcc wrapper bin gcc skipped detecting c compile features detecting c compile features done detecting cxx compiler abi info detecting cxx compiler abi info done check for working cxx compiler nix store gcc wrapper bin g skipped detecting cxx compile features detecting cxx compile features done found pythoninterp nix store bin python found version performing test cmake have libc pthread performing test cmake have libc pthread success found threads true looking for tbb components tbb found tbb version at nix store tbb dev cmake error at cmake findtbb cmake message cannot find required components tbb call stack most recent call first cmake findtbb cmake rk tbb error cmakelists txt find package configuring incomplete errors occurred see also build source build cmakefiles cmakeoutput log additional context breaks blender since it depends on openimagedenoise notify maintainers please people who are in the meta maintainers list of the offending package or module if in doubt check git blame for whoever last touched something leshainc openimagedenoise thoughtpolice dizfer tbb metadata please run nix shell p nix info run nix info m and paste the result console nix shell p nix info run nix info m system linux host os linux nixos stoat multi user yes sandbox yes version nix env nix channels username home manager channels root nixos nixpkgs nix var nix profiles per user root channels nixos | 0 |
89,905 | 8,216,718,404 | IssuesEvent | 2018-09-05 10:01:43 | humera987/HumTestData | https://api.github.com/repos/humera987/HumTestData | opened | project_test : ApiV1TestSuitesIdDeleteAnonymousInvalid | project_test | Project : project_test
Job : UAT
Env : UAT
Region : FXLabs/US_WEST_1
Result : fail
Status Code : 200
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], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Wed, 05 Sep 2018 10:01:42 GMT]}
Endpoint : http://13.56.210.25/api/v1/test-suites/g6nT9gU3
Request :
Response :
{
"requestId" : "None",
"requestTime" : "2018-09-05T10:01:42.804+0000",
"errors" : false,
"messages" : [ ],
"data" : null,
"totalPages" : 0,
"totalElements" : 0
}
Logs :
Assertion [@StatusCode != 200] failed, not expecting [200] but found [200]
--- FX Bot --- | 1.0 | project_test : ApiV1TestSuitesIdDeleteAnonymousInvalid - Project : project_test
Job : UAT
Env : UAT
Region : FXLabs/US_WEST_1
Result : fail
Status Code : 200
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], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Wed, 05 Sep 2018 10:01:42 GMT]}
Endpoint : http://13.56.210.25/api/v1/test-suites/g6nT9gU3
Request :
Response :
{
"requestId" : "None",
"requestTime" : "2018-09-05T10:01:42.804+0000",
"errors" : false,
"messages" : [ ],
"data" : null,
"totalPages" : 0,
"totalElements" : 0
}
Logs :
Assertion [@StatusCode != 200] failed, not expecting [200] but found [200]
--- FX Bot --- | test | project test project project test job uat env uat region fxlabs us west result fail status code headers x content type options x xss protection cache control pragma expires x frame options content type transfer encoding date endpoint request response requestid none requesttime errors false messages data null totalpages totalelements logs assertion failed not expecting but found fx bot | 1 |
20,296 | 10,700,293,889 | IssuesEvent | 2019-10-23 23:25:48 | becurrie/titandash | https://api.github.com/repos/becurrie/titandash | closed | Upgrade In Game Actions Implementation | enhancement major performance | Currently, actions in game are a bit complex code wise and can be easily brought out into their own specific configuration settings category...
We should ideally have the following actions settings configurations...
- Master Action Settings
- Hero Action Settings
- Skills Level Action Settings
- Skills Activate Action Settings
Users should be able to determine the interval between each one taking place as well as enabling/disabling each one as needed.
Users should be able to choose the level at which certain skills will stop being levelled up.
The functionality for all of these should not rely on going to the master panel (unless explicitly needed)...
We want to make this loop more efficient...
Levels of skills should be stored on a prestige/prestige basis... Only levelling them when they're available/need an upgrade.
Prestige should reset these variables.
Most things can remain as they are here, implementation wise, but the skill levelling process will need a complete re write, to remove it from the activation process. | True | Upgrade In Game Actions Implementation - Currently, actions in game are a bit complex code wise and can be easily brought out into their own specific configuration settings category...
We should ideally have the following actions settings configurations...
- Master Action Settings
- Hero Action Settings
- Skills Level Action Settings
- Skills Activate Action Settings
Users should be able to determine the interval between each one taking place as well as enabling/disabling each one as needed.
Users should be able to choose the level at which certain skills will stop being levelled up.
The functionality for all of these should not rely on going to the master panel (unless explicitly needed)...
We want to make this loop more efficient...
Levels of skills should be stored on a prestige/prestige basis... Only levelling them when they're available/need an upgrade.
Prestige should reset these variables.
Most things can remain as they are here, implementation wise, but the skill levelling process will need a complete re write, to remove it from the activation process. | non_test | upgrade in game actions implementation currently actions in game are a bit complex code wise and can be easily brought out into their own specific configuration settings category we should ideally have the following actions settings configurations master action settings hero action settings skills level action settings skills activate action settings users should be able to determine the interval between each one taking place as well as enabling disabling each one as needed users should be able to choose the level at which certain skills will stop being levelled up the functionality for all of these should not rely on going to the master panel unless explicitly needed we want to make this loop more efficient levels of skills should be stored on a prestige prestige basis only levelling them when they re available need an upgrade prestige should reset these variables most things can remain as they are here implementation wise but the skill levelling process will need a complete re write to remove it from the activation process | 0 |
198,435 | 15,709,440,104 | IssuesEvent | 2021-03-26 22:32:31 | garoque/crud-eng-software | https://api.github.com/repos/garoque/crud-eng-software | closed | Relatório Iteração 4 | documentation | ## Relatório Iteração 4
Relatório das atividades feitas durante a iteração 4, o que funcionou ou deu errado durante a iteração.
### Período da iteração
|Inicio:| 06/03/2021|
|-------|-----------|
| Fim: | 26/03/2021|
### Atividades planejadas
- Criação de testes.
- Desenvolvimento.
- Modelo de dados.
### Atividades realizadas
- [ ] ~~Criação de testes.~~
- [x] Desenvolvimento.
- [x] Modelo de dados.
### Atividades não realizadas
- [x] Criação de testes.
- [ ] ~~Desenvolvimento.~~
- [ ] ~~Modelo de dados.~~
_Lições aprendidas_
- Conseguimos compreender que em ambiente remoto as vezes traz dificuldade em compartilhar ideias e resolver problemas ao longo do desenvolvimento por se tratar de reuniões online em que até são difíceis de ter todos integrantes, assim atrasando coisas que seriam simples em um ambiente de convívio comum.
- E também faz falta de um programador experiente junto ao dia a dia de desenvolvimento para tirar dúvidas. | 1.0 | Relatório Iteração 4 - ## Relatório Iteração 4
Relatório das atividades feitas durante a iteração 4, o que funcionou ou deu errado durante a iteração.
### Período da iteração
|Inicio:| 06/03/2021|
|-------|-----------|
| Fim: | 26/03/2021|
### Atividades planejadas
- Criação de testes.
- Desenvolvimento.
- Modelo de dados.
### Atividades realizadas
- [ ] ~~Criação de testes.~~
- [x] Desenvolvimento.
- [x] Modelo de dados.
### Atividades não realizadas
- [x] Criação de testes.
- [ ] ~~Desenvolvimento.~~
- [ ] ~~Modelo de dados.~~
_Lições aprendidas_
- Conseguimos compreender que em ambiente remoto as vezes traz dificuldade em compartilhar ideias e resolver problemas ao longo do desenvolvimento por se tratar de reuniões online em que até são difíceis de ter todos integrantes, assim atrasando coisas que seriam simples em um ambiente de convívio comum.
- E também faz falta de um programador experiente junto ao dia a dia de desenvolvimento para tirar dúvidas. | non_test | relatório iteração relatório iteração relatório das atividades feitas durante a iteração o que funcionou ou deu errado durante a iteração período da iteração inicio fim atividades planejadas criação de testes desenvolvimento modelo de dados atividades realizadas criação de testes desenvolvimento modelo de dados atividades não realizadas criação de testes desenvolvimento modelo de dados lições aprendidas conseguimos compreender que em ambiente remoto as vezes traz dificuldade em compartilhar ideias e resolver problemas ao longo do desenvolvimento por se tratar de reuniões online em que até são difíceis de ter todos integrantes assim atrasando coisas que seriam simples em um ambiente de convívio comum e também faz falta de um programador experiente junto ao dia a dia de desenvolvimento para tirar dúvidas | 0 |
251,058 | 21,414,175,599 | IssuesEvent | 2022-04-22 09:16:25 | microsoft/AzureStorageExplorer | https://api.github.com/repos/microsoft/AzureStorageExplorer | opened | Fail to select more than one item under snapshots view when right clicking them | 🧪 testing :gear: blobs :computer: mac | **Storage Explorer Version**: 1.24.0
**Build Number**: 20220422.13
**Branch**: rel/1.24.0
**Platform/OS**: MacOS Monterey 12.3.1 (Apple M1 Pro)
**Architecture** x64
**How Found**: From running test cases
**Regression From**: Not a regression
## Steps to Reproduce ##
1. Expand one storage account -> Blob Containers.
2. Create a blob container -> Upload one blob.
3. Create snapshots for the blob.
4. Go to the snapshots view -> Click 'Select All -> Select All in Page/Cached'.
5. Right click the muti selection -> Check whether all items are still selected.
## Expected Experience ##
All items are still selected.
## Actual Experience ##
Only one snapshot is selected.
## Additional Context ##
1. This issue can't be reproduced consistently.
2. This issue only occurs on Mac.
3. We met this issue twice.
4. Here is the record:
https://user-images.githubusercontent.com/41351993/164666330-5a4e8e4c-7f39-47b2-a360-d01818e29e26.mov
| 1.0 | Fail to select more than one item under snapshots view when right clicking them - **Storage Explorer Version**: 1.24.0
**Build Number**: 20220422.13
**Branch**: rel/1.24.0
**Platform/OS**: MacOS Monterey 12.3.1 (Apple M1 Pro)
**Architecture** x64
**How Found**: From running test cases
**Regression From**: Not a regression
## Steps to Reproduce ##
1. Expand one storage account -> Blob Containers.
2. Create a blob container -> Upload one blob.
3. Create snapshots for the blob.
4. Go to the snapshots view -> Click 'Select All -> Select All in Page/Cached'.
5. Right click the muti selection -> Check whether all items are still selected.
## Expected Experience ##
All items are still selected.
## Actual Experience ##
Only one snapshot is selected.
## Additional Context ##
1. This issue can't be reproduced consistently.
2. This issue only occurs on Mac.
3. We met this issue twice.
4. Here is the record:
https://user-images.githubusercontent.com/41351993/164666330-5a4e8e4c-7f39-47b2-a360-d01818e29e26.mov
| test | fail to select more than one item under snapshots view when right clicking them storage explorer version build number branch rel platform os macos monterey apple pro architecture how found from running test cases regression from not a regression steps to reproduce expand one storage account blob containers create a blob container upload one blob create snapshots for the blob go to the snapshots view click select all select all in page cached right click the muti selection check whether all items are still selected expected experience all items are still selected actual experience only one snapshot is selected additional context this issue can t be reproduced consistently this issue only occurs on mac we met this issue twice here is the record | 1 |
136,346 | 19,765,893,351 | IssuesEvent | 2022-01-17 02:11:06 | hackforla/website | https://api.github.com/repos/hackforla/website | opened | DRAFT-Add paragraph classes 1-3 to codebase | Feature: Design system | ### Overview
As developers, we use reusable SCSS/CSS classes for styling Hack for LA webpages. For this issue, we will add the paragraph classes 1-3 defined in the [Design System](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=3464%3A3) to our codebase.
<details>
<summary>Paragraph Classes under Typography in the Design System in Figma</summary>
<img width="815" alt="paragraph-classes-in-design-system" src="https://user-images.githubusercontent.com/31293603/149689444-acc7016e-20e9-433e-aa83-596ce22e70f1.png">
</details>
### Action Items
- [ ] Locate the Paragraphs section under Typography in the [Design System](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=3464%3A3) in Figma
- [ ] Based on how each paragraph class is defined, add paragraph classes 1-3 to ______link for file to add it to_________ file
- [ ] When writing the SCSS/CSS classes in the code, the classes name should be lower case. For example, Paragraph1 in Figma should be `.paragraph1`
### Resources/Instructions
- [Design System](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=3464%3A3)
| 1.0 | DRAFT-Add paragraph classes 1-3 to codebase - ### Overview
As developers, we use reusable SCSS/CSS classes for styling Hack for LA webpages. For this issue, we will add the paragraph classes 1-3 defined in the [Design System](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=3464%3A3) to our codebase.
<details>
<summary>Paragraph Classes under Typography in the Design System in Figma</summary>
<img width="815" alt="paragraph-classes-in-design-system" src="https://user-images.githubusercontent.com/31293603/149689444-acc7016e-20e9-433e-aa83-596ce22e70f1.png">
</details>
### Action Items
- [ ] Locate the Paragraphs section under Typography in the [Design System](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=3464%3A3) in Figma
- [ ] Based on how each paragraph class is defined, add paragraph classes 1-3 to ______link for file to add it to_________ file
- [ ] When writing the SCSS/CSS classes in the code, the classes name should be lower case. For example, Paragraph1 in Figma should be `.paragraph1`
### Resources/Instructions
- [Design System](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=3464%3A3)
| non_test | draft add paragraph classes to codebase overview as developers we use reusable scss css classes for styling hack for la webpages for this issue we will add the paragraph classes defined in the to our codebase paragraph classes under typography in the design system in figma img width alt paragraph classes in design system src action items locate the paragraphs section under typography in the in figma based on how each paragraph class is defined add paragraph classes to link for file to add it to file when writing the scss css classes in the code the classes name should be lower case for example in figma should be resources instructions | 0 |
66,571 | 7,006,920,101 | IssuesEvent | 2017-12-19 10:18:17 | Kademi/kademi-dev | https://api.github.com/repos/Kademi/kademi-dev | closed | Login-as component | bug enhancement Ready to Test - Dev | We need a component which can be added to front end websites to make the "login-as" capability available.
For example, this is so that sales reps can view customers in their lead management site, and then login as a customer to a reward site.
Note that we need to be very careful with authorisation. Any request to generate a login-as link should check that the current user has WRITE_ACL permission to the user they're logging as. This priviledge should come from the UserAdministrator or Administrator roles
The component should allow selecting which website to login to. | 1.0 | Login-as component - We need a component which can be added to front end websites to make the "login-as" capability available.
For example, this is so that sales reps can view customers in their lead management site, and then login as a customer to a reward site.
Note that we need to be very careful with authorisation. Any request to generate a login-as link should check that the current user has WRITE_ACL permission to the user they're logging as. This priviledge should come from the UserAdministrator or Administrator roles
The component should allow selecting which website to login to. | test | login as component we need a component which can be added to front end websites to make the login as capability available for example this is so that sales reps can view customers in their lead management site and then login as a customer to a reward site note that we need to be very careful with authorisation any request to generate a login as link should check that the current user has write acl permission to the user they re logging as this priviledge should come from the useradministrator or administrator roles the component should allow selecting which website to login to | 1 |
263,962 | 23,093,372,831 | IssuesEvent | 2022-07-26 17:04:17 | Uuvana-Studios/longvinter-windows-client | https://api.github.com/repos/Uuvana-Studios/longvinter-windows-client | closed | [AU] Uuvanna 1 server dissapearing from server list | Bug Not Tested | **Describe the bug**
The AU1 server keeps dissapearing from the server list. It's been happening for 2 days now usually around this time. It was working fine earlier in the morning. It's 6pm at the time of posting so there should be more people online.
Maybe there's a bug where only 1 person can be online at a given time?
**To Reproduce**
Steps to reproduce the behavior:
1. Go to server list
2. Select "Oceania"
**Expected behavior**
AU Uuvanna 1 server shows up on server list.
**Screenshots**
**Desktop (please complete the following information):**
- OS: Windows
- Game Version 1.0.8
- Steam Version - latest
**Additional context**
The AU1 server also has been experiencing quite a lot of ping spikes this week. This may be related to the issue.
Others have also informed me of them experiencing this issue. | 1.0 | [AU] Uuvanna 1 server dissapearing from server list - **Describe the bug**
The AU1 server keeps dissapearing from the server list. It's been happening for 2 days now usually around this time. It was working fine earlier in the morning. It's 6pm at the time of posting so there should be more people online.
Maybe there's a bug where only 1 person can be online at a given time?
**To Reproduce**
Steps to reproduce the behavior:
1. Go to server list
2. Select "Oceania"
**Expected behavior**
AU Uuvanna 1 server shows up on server list.
**Screenshots**
**Desktop (please complete the following information):**
- OS: Windows
- Game Version 1.0.8
- Steam Version - latest
**Additional context**
The AU1 server also has been experiencing quite a lot of ping spikes this week. This may be related to the issue.
Others have also informed me of them experiencing this issue. | test | uuvanna server dissapearing from server list describe the bug the server keeps dissapearing from the server list it s been happening for days now usually around this time it was working fine earlier in the morning it s at the time of posting so there should be more people online maybe there s a bug where only person can be online at a given time to reproduce steps to reproduce the behavior go to server list select oceania expected behavior au uuvanna server shows up on server list screenshots desktop please complete the following information os windows game version steam version latest additional context the server also has been experiencing quite a lot of ping spikes this week this may be related to the issue others have also informed me of them experiencing this issue | 1 |
187,445 | 14,427,878,730 | IssuesEvent | 2020-12-06 06:45:40 | kalexmills/github-vet-tests-dec2020 | https://api.github.com/repos/kalexmills/github-vet-tests-dec2020 | closed | terraform-providers/terraform-provider-oci: oci/core_vcn_test.go; 16 LoC | fresh small test |
Found a possible issue in [terraform-providers/terraform-provider-oci](https://www.github.com/terraform-providers/terraform-provider-oci) at [oci/core_vcn_test.go](https://github.com/terraform-providers/terraform-provider-oci/blob/b79082228a6fabc06eb347d2a4a537e07f71b06f/oci/core_vcn_test.go#L303-L318)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> reference to vcnId is reassigned at line 307
[Click here to see the code in its original context.](https://github.com/terraform-providers/terraform-provider-oci/blob/b79082228a6fabc06eb347d2a4a537e07f71b06f/oci/core_vcn_test.go#L303-L318)
<details>
<summary>Click here to show the 16 line(s) of Go which triggered the analyzer.</summary>
```go
for _, vcnId := range vcnIds {
if ok := SweeperDefaultResourceId[vcnId]; !ok {
deleteVcnRequest := oci_core.DeleteVcnRequest{}
deleteVcnRequest.VcnId = &vcnId
deleteVcnRequest.RequestMetadata.RetryPolicy = getRetryPolicy(true, "core")
_, error := virtualNetworkClient.DeleteVcn(context.Background(), deleteVcnRequest)
if error != nil {
fmt.Printf("Error deleting Vcn %s %s, It is possible that the resource is already deleted. Please verify manually \n", vcnId, error)
continue
}
waitTillCondition(testAccProvider, &vcnId, vcnSweepWaitCondition, time.Duration(3*time.Minute),
vcnSweepResponseFetchOperation, "core", true)
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: b79082228a6fabc06eb347d2a4a537e07f71b06f
| 1.0 | terraform-providers/terraform-provider-oci: oci/core_vcn_test.go; 16 LoC -
Found a possible issue in [terraform-providers/terraform-provider-oci](https://www.github.com/terraform-providers/terraform-provider-oci) at [oci/core_vcn_test.go](https://github.com/terraform-providers/terraform-provider-oci/blob/b79082228a6fabc06eb347d2a4a537e07f71b06f/oci/core_vcn_test.go#L303-L318)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> reference to vcnId is reassigned at line 307
[Click here to see the code in its original context.](https://github.com/terraform-providers/terraform-provider-oci/blob/b79082228a6fabc06eb347d2a4a537e07f71b06f/oci/core_vcn_test.go#L303-L318)
<details>
<summary>Click here to show the 16 line(s) of Go which triggered the analyzer.</summary>
```go
for _, vcnId := range vcnIds {
if ok := SweeperDefaultResourceId[vcnId]; !ok {
deleteVcnRequest := oci_core.DeleteVcnRequest{}
deleteVcnRequest.VcnId = &vcnId
deleteVcnRequest.RequestMetadata.RetryPolicy = getRetryPolicy(true, "core")
_, error := virtualNetworkClient.DeleteVcn(context.Background(), deleteVcnRequest)
if error != nil {
fmt.Printf("Error deleting Vcn %s %s, It is possible that the resource is already deleted. Please verify manually \n", vcnId, error)
continue
}
waitTillCondition(testAccProvider, &vcnId, vcnSweepWaitCondition, time.Duration(3*time.Minute),
vcnSweepResponseFetchOperation, "core", true)
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: b79082228a6fabc06eb347d2a4a537e07f71b06f
| test | terraform providers terraform provider oci oci core vcn test go loc found a possible issue in at below is the message reported by the analyzer for this snippet of code beware that the analyzer only reports the first issue it finds so please do not limit your consideration to the contents of the below message reference to vcnid is reassigned at line click here to show the line s of go which triggered the analyzer go for vcnid range vcnids if ok sweeperdefaultresourceid ok deletevcnrequest oci core deletevcnrequest deletevcnrequest vcnid vcnid deletevcnrequest requestmetadata retrypolicy getretrypolicy true core error virtualnetworkclient deletevcn context background deletevcnrequest if error nil fmt printf error deleting vcn s s it is possible that the resource is already deleted please verify manually n vcnid error continue waittillcondition testaccprovider vcnid vcnsweepwaitcondition time duration time minute vcnsweepresponsefetchoperation core true leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id | 1 |
320,478 | 27,436,774,685 | IssuesEvent | 2023-03-02 08:07:30 | proarc/proarc-client | https://api.github.com/repos/proarc/proarc-client | closed | Import - nefunkční "převod stran" | 1 chyba 6 k testování 6c otestováno: KNAV | Funkce převodu stran na NDK strany a zpět je funkční v editaci v úložišti, ale ne v importu | 2.0 | Import - nefunkční "převod stran" - Funkce převodu stran na NDK strany a zpět je funkční v editaci v úložišti, ale ne v importu | test | import nefunkční převod stran funkce převodu stran na ndk strany a zpět je funkční v editaci v úložišti ale ne v importu | 1 |
184,613 | 14,289,809,303 | IssuesEvent | 2020-11-23 19:51:45 | github-vet/rangeclosure-findings | https://api.github.com/repos/github-vet/rangeclosure-findings | closed | uber/tchannel-go: init_test.go; 37 LoC | fresh small test |
Found a possible issue in [uber/tchannel-go](https://www.github.com/uber/tchannel-go) at [init_test.go](https://github.com/uber/tchannel-go/blob/0b71d5ed50c706c5a962d813a282981020440cac/init_test.go#L172-L208)
The below snippet of Go code triggered static analysis which searches for goroutines and/or defer statements
which capture loop variables.
[Click here to see the code in its original context.](https://github.com/uber/tchannel-go/blob/0b71d5ed50c706c5a962d813a282981020440cac/init_test.go#L172-L208)
<details>
<summary>Click here to show the 37 line(s) of Go which triggered the analyzer.</summary>
```go
for _, tt := range tests {
ln, err := net.Listen("tcp", "127.0.0.1:0")
require.NoError(t, err, "net.Listen failed")
defer ln.Close()
done := make(chan struct{})
go func() {
defer close(done)
ch, err := NewChannel("test", nil)
require.NoError(t, err)
defer ch.Close()
ctx, cancel := NewContext(time.Second)
defer cancel()
_, err = ch.Peers().GetOrAdd(ln.Addr().String()).GetConnection(ctx)
if !assert.Error(t, err, "Expected GetConnection to fail") {
return
}
assert.Equal(t, ErrCodeProtocol, GetSystemErrorCode(err), "Unexpected error code, got error: %v", err)
assert.Contains(t, err.Error(), tt.errMsg)
}()
conn, err := ln.Accept()
require.NoError(t, err, "Failed to accept connection")
// Read the frame and verify that it's an initReq.
f, err := readFrame(conn)
require.NoError(t, err, "read frame failed")
if !assert.Equal(t, messageTypeInitReq, f.messageType(), "Expected first message to be initReq") {
continue
}
// Write out the specified initRes wait for the channel to get an error.
assert.NoError(t, writeMessage(conn, tt.msg), "write initRes failed")
<-done
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 0b71d5ed50c706c5a962d813a282981020440cac
| 1.0 | uber/tchannel-go: init_test.go; 37 LoC -
Found a possible issue in [uber/tchannel-go](https://www.github.com/uber/tchannel-go) at [init_test.go](https://github.com/uber/tchannel-go/blob/0b71d5ed50c706c5a962d813a282981020440cac/init_test.go#L172-L208)
The below snippet of Go code triggered static analysis which searches for goroutines and/or defer statements
which capture loop variables.
[Click here to see the code in its original context.](https://github.com/uber/tchannel-go/blob/0b71d5ed50c706c5a962d813a282981020440cac/init_test.go#L172-L208)
<details>
<summary>Click here to show the 37 line(s) of Go which triggered the analyzer.</summary>
```go
for _, tt := range tests {
ln, err := net.Listen("tcp", "127.0.0.1:0")
require.NoError(t, err, "net.Listen failed")
defer ln.Close()
done := make(chan struct{})
go func() {
defer close(done)
ch, err := NewChannel("test", nil)
require.NoError(t, err)
defer ch.Close()
ctx, cancel := NewContext(time.Second)
defer cancel()
_, err = ch.Peers().GetOrAdd(ln.Addr().String()).GetConnection(ctx)
if !assert.Error(t, err, "Expected GetConnection to fail") {
return
}
assert.Equal(t, ErrCodeProtocol, GetSystemErrorCode(err), "Unexpected error code, got error: %v", err)
assert.Contains(t, err.Error(), tt.errMsg)
}()
conn, err := ln.Accept()
require.NoError(t, err, "Failed to accept connection")
// Read the frame and verify that it's an initReq.
f, err := readFrame(conn)
require.NoError(t, err, "read frame failed")
if !assert.Equal(t, messageTypeInitReq, f.messageType(), "Expected first message to be initReq") {
continue
}
// Write out the specified initRes wait for the channel to get an error.
assert.NoError(t, writeMessage(conn, tt.msg), "write initRes failed")
<-done
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 0b71d5ed50c706c5a962d813a282981020440cac
| test | uber tchannel go init test go loc found a possible issue in at the below snippet of go code triggered static analysis which searches for goroutines and or defer statements which capture loop variables click here to show the line s of go which triggered the analyzer go for tt range tests ln err net listen tcp require noerror t err net listen failed defer ln close done make chan struct go func defer close done ch err newchannel test nil require noerror t err defer ch close ctx cancel newcontext time second defer cancel err ch peers getoradd ln addr string getconnection ctx if assert error t err expected getconnection to fail return assert equal t errcodeprotocol getsystemerrorcode err unexpected error code got error v err assert contains t err error tt errmsg conn err ln accept require noerror t err failed to accept connection read the frame and verify that it s an initreq f err readframe conn require noerror t err read frame failed if assert equal t messagetypeinitreq f messagetype expected first message to be initreq continue write out the specified initres wait for the channel to get an error assert noerror t writemessage conn tt msg write initres failed done leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id | 1 |
133,330 | 10,817,650,346 | IssuesEvent | 2019-11-08 10:12:23 | microsoft/CCF | https://api.github.com/repos/microsoft/CCF | closed | Consortium-related functions should have their own class | enhancement hygiene testing | The `Network` class in `tests/infra/ccf.py` contains several functions related to member governance that should be moved to their own class (e.g. `Consortium`). | 1.0 | Consortium-related functions should have their own class - The `Network` class in `tests/infra/ccf.py` contains several functions related to member governance that should be moved to their own class (e.g. `Consortium`). | test | consortium related functions should have their own class the network class in tests infra ccf py contains several functions related to member governance that should be moved to their own class e g consortium | 1 |
270,114 | 28,960,414,209 | IssuesEvent | 2023-05-10 01:40:00 | praneethpanasala/linux | https://api.github.com/repos/praneethpanasala/linux | reopened | CVE-2020-25645 (High) detected in linuxlinux-4.19.6 | Mend: dependency security vulnerability | ## CVE-2020-25645 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.19.6</b></p></summary>
<p>
<p>Apache Software Foundation (ASF)</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://api.github.com/repos/praneethpanasala/linux/commits/d80c4f847c91020292cb280132b15e2ea147f1a3">d80c4f847c91020292cb280132b15e2ea147f1a3</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/net/geneve.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
A flaw was found in the Linux kernel in versions before 5.9-rc7. Traffic between two Geneve endpoints may be unencrypted when IPsec is configured to encrypt traffic for the specific UDP port used by the GENEVE tunnel allowing anyone between the two endpoints to read the traffic unencrypted. The main threat from this vulnerability is to data confidentiality.
<p>Publish Date: 2020-10-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-25645>CVE-2020-25645</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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://bugzilla.redhat.com/show_bug.cgi?id=1883988">https://bugzilla.redhat.com/show_bug.cgi?id=1883988</a></p>
<p>Release Date: 2020-10-13</p>
<p>Fix Resolution: v4.14.200,v4.19.148,v5.4.68,v5.8.12,v5.9-rc7</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-2020-25645 (High) detected in linuxlinux-4.19.6 - ## CVE-2020-25645 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.19.6</b></p></summary>
<p>
<p>Apache Software Foundation (ASF)</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://api.github.com/repos/praneethpanasala/linux/commits/d80c4f847c91020292cb280132b15e2ea147f1a3">d80c4f847c91020292cb280132b15e2ea147f1a3</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/net/geneve.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
A flaw was found in the Linux kernel in versions before 5.9-rc7. Traffic between two Geneve endpoints may be unencrypted when IPsec is configured to encrypt traffic for the specific UDP port used by the GENEVE tunnel allowing anyone between the two endpoints to read the traffic unencrypted. The main threat from this vulnerability is to data confidentiality.
<p>Publish Date: 2020-10-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-25645>CVE-2020-25645</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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://bugzilla.redhat.com/show_bug.cgi?id=1883988">https://bugzilla.redhat.com/show_bug.cgi?id=1883988</a></p>
<p>Release Date: 2020-10-13</p>
<p>Fix Resolution: v4.14.200,v4.19.148,v5.4.68,v5.8.12,v5.9-rc7</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 high detected in linuxlinux cve high severity vulnerability vulnerable library linuxlinux apache software foundation asf library home page a href found in head commit a href found in base branch master vulnerable source files drivers net geneve c vulnerability details a flaw was found in the linux kernel in versions before traffic between two geneve endpoints may be unencrypted when ipsec is configured to encrypt traffic for the specific udp port used by the geneve tunnel allowing anyone between the two endpoints to read the traffic unencrypted the main threat from this vulnerability is to data confidentiality publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
4,488 | 6,996,090,513 | IssuesEvent | 2017-12-15 22:20:24 | amcnulty/Whoop-It-Up | https://api.github.com/repos/amcnulty/Whoop-It-Up | closed | Insert new user into database | Requirement | Once a user is signed up their information needs to be stored into the database. | 1.0 | Insert new user into database - Once a user is signed up their information needs to be stored into the database. | non_test | insert new user into database once a user is signed up their information needs to be stored into the database | 0 |
337,066 | 30,237,552,281 | IssuesEvent | 2023-07-06 11:19:50 | WordPress/gutenberg | https://api.github.com/repos/WordPress/gutenberg | opened | [Flaky Test] Animation selector should appear if Behavior is Lightbox | [Type] Flaky Test | <!-- __META_DATA__:{} -->
**Flaky test detected. This is an auto-generated issue by GitHub Actions. Please do NOT edit this manually.**
## Test title
Animation selector should appear if Behavior is Lightbox
## Test path
`/test/e2e/specs/editor/blocks/image.spec.js`
## Errors
<!-- __TEST_RESULTS_LIST__ -->
<!-- __TEST_RESULT__ --><details>
<summary>
<time datetime="2023-07-06T11:19:49.664Z"><code>[2023-07-06T11:19:49.664Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/5474540301"><code>trunk</code></a>.
</summary>
```
Error: expect(received).toHaveAttribute(expected)
Expected pattern: /ef1a566f-630c-4735-9eac-0b759d9526c1/
Received string: "blob:http://localhost:8889/b02f81db-714b-4374-832d-6bff596adddc"
Call log:
- expect.toHaveAttribute with timeout 5000ms
- waiting for locator('role=document[name="Block: Image"i]').locator('role=img')
- locator resolved to <img alt="This image has an empty alt attribute" src=…/>
- unexpected value "blob:http://localhost:8889/b02f81db-714b-4374-832d-6bff596adddc"
- waiting for locator('role=document[name="Block: Image"i]').locator('role=img')
- locator resolved to <img alt="This image has an empty alt attribute" src=…/>
- unexpected value "blob:http://localhost:8889/b02f81db-714b-4374-832d-6bff596adddc"
- locator resolved to <img alt="This image has an empty alt attribute" src=…/>
- unexpected value "blob:http://localhost:8889/b02f81db-714b-4374-832d-6bff596adddc"
- locator resolved to <img alt="This image has an empty alt attribute" src=…/>
- unexpected value "blob:http://localhost:8889/b02f81db-714b-4374-832d-6bff596adddc"
- locator resolved to <img alt="This image has an empty alt attribute" src=…/>
- unexpected value "blob:http://localhost:8889/b02f81db-714b-4374-832d-6bff596adddc"
- locator resolved to <img alt="This image has an empty alt attribute" src=…/>
- unexpected value "blob:http://localhost:8889/b02f81db-714b-4374-832d-6bff596adddc"
- locator resolved to <img alt="This image has an empty alt attribute" src=…/>
- unexpected value "blob:http://localhost:8889/b02f81db-714b-4374-832d-6bff596adddc"
- locator resolved to <img alt="This image has an empty alt attribute" src=…/>
- unexpected value "blob:http://localhost:8889/b02f81db-714b-4374-832d-6bff596adddc"
- locator resolved to <img alt="This image has an empty alt attribute" src=…/>
- unexpected value "blob:http://localhost:8889/b02f81db-714b-4374-832d-6bff596adddc"
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/image.spec.js:789:26
```
</details><!-- /__TEST_RESULT__ -->
<!-- /__TEST_RESULTS_LIST__ -->
| 1.0 | [Flaky Test] Animation selector should appear if Behavior is Lightbox - <!-- __META_DATA__:{} -->
**Flaky test detected. This is an auto-generated issue by GitHub Actions. Please do NOT edit this manually.**
## Test title
Animation selector should appear if Behavior is Lightbox
## Test path
`/test/e2e/specs/editor/blocks/image.spec.js`
## Errors
<!-- __TEST_RESULTS_LIST__ -->
<!-- __TEST_RESULT__ --><details>
<summary>
<time datetime="2023-07-06T11:19:49.664Z"><code>[2023-07-06T11:19:49.664Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/5474540301"><code>trunk</code></a>.
</summary>
```
Error: expect(received).toHaveAttribute(expected)
Expected pattern: /ef1a566f-630c-4735-9eac-0b759d9526c1/
Received string: "blob:http://localhost:8889/b02f81db-714b-4374-832d-6bff596adddc"
Call log:
- expect.toHaveAttribute with timeout 5000ms
- waiting for locator('role=document[name="Block: Image"i]').locator('role=img')
- locator resolved to <img alt="This image has an empty alt attribute" src=…/>
- unexpected value "blob:http://localhost:8889/b02f81db-714b-4374-832d-6bff596adddc"
- waiting for locator('role=document[name="Block: Image"i]').locator('role=img')
- locator resolved to <img alt="This image has an empty alt attribute" src=…/>
- unexpected value "blob:http://localhost:8889/b02f81db-714b-4374-832d-6bff596adddc"
- locator resolved to <img alt="This image has an empty alt attribute" src=…/>
- unexpected value "blob:http://localhost:8889/b02f81db-714b-4374-832d-6bff596adddc"
- locator resolved to <img alt="This image has an empty alt attribute" src=…/>
- unexpected value "blob:http://localhost:8889/b02f81db-714b-4374-832d-6bff596adddc"
- locator resolved to <img alt="This image has an empty alt attribute" src=…/>
- unexpected value "blob:http://localhost:8889/b02f81db-714b-4374-832d-6bff596adddc"
- locator resolved to <img alt="This image has an empty alt attribute" src=…/>
- unexpected value "blob:http://localhost:8889/b02f81db-714b-4374-832d-6bff596adddc"
- locator resolved to <img alt="This image has an empty alt attribute" src=…/>
- unexpected value "blob:http://localhost:8889/b02f81db-714b-4374-832d-6bff596adddc"
- locator resolved to <img alt="This image has an empty alt attribute" src=…/>
- unexpected value "blob:http://localhost:8889/b02f81db-714b-4374-832d-6bff596adddc"
- locator resolved to <img alt="This image has an empty alt attribute" src=…/>
- unexpected value "blob:http://localhost:8889/b02f81db-714b-4374-832d-6bff596adddc"
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/image.spec.js:789:26
```
</details><!-- /__TEST_RESULT__ -->
<!-- /__TEST_RESULTS_LIST__ -->
| test | animation selector should appear if behavior is lightbox flaky test detected this is an auto generated issue by github actions please do not edit this manually test title animation selector should appear if behavior is lightbox test path test specs editor blocks image spec js errors test passed after failed attempt on a href error expect received tohaveattribute expected expected pattern received string blob call log expect tohaveattribute with timeout waiting for locator role document locator role img locator resolved to unexpected value blob waiting for locator role document locator role img locator resolved to unexpected value blob locator resolved to unexpected value blob locator resolved to unexpected value blob locator resolved to unexpected value blob locator resolved to unexpected value blob locator resolved to unexpected value blob locator resolved to unexpected value blob locator resolved to unexpected value blob at home runner work gutenberg gutenberg test specs editor blocks image spec js | 1 |
15,393 | 27,094,869,234 | IssuesEvent | 2023-02-15 01:23:10 | renovatebot/renovate | https://api.github.com/repos/renovatebot/renovate | opened | Read-Only Filesystem Support | type:feature status:requirements priority-5-triage | ### What would you like Renovate to be able to do?
For security compliance, we have a strong requirement to run any container in Kubernetes with a read-only filesystem. We can then mount some writeable volumes at some pre-defined filesystem locations (e.g.: /tmp)
For managers involving lockfiles, like Elixir/Python/Ruby/... managers, we're running into issues when configuring a read-only filesystem.
For example:
```
Command failed: install-tool erlang 24.3.4.0
tar: 24.3.4.0: Cannot mkdir: Read-only file system
tar: 24.3.4.0: Cannot mkdir: Read-only file system
tar: 24.3.4.0/misc: Cannot mkdir: No such file or directory
tar: 24.3.4.0: Cannot mkdir: Read-only file system
tar: 24.3.4.0/misc/format_man_pages: Cannot open: No such file or directory
tar: 24.3.4.0: Cannot mkdir: Read-only file system
tar: 24.3.4.0/misc/makewhatis: Cannot open: No such file or directory
tar: 24.3.4.0: Cannot mkdir: Read-only file system
tar: 24.3.4.0/activate.csh: Cannot open: No such file or directory
tar: 24.3.4.0: Cannot mkdir: Read-only file system
...
```
After investigating by running things locally, it seems that renovate is installing missing tools under `/opt/buildpack/tools`, and under `/opt/buildpack/tools/erlang` for erlang/mix in particular 🤔
Unfortunately, we can't make mount an entire emptyDir to /opt because the renovate binary is located under `/opt/buildpack/tools/renovate/34.108.0/bin/renovate`.
Even by mounting a writeable volume specifically for ``, we running into other cryptic errors:
```
Command failed: install-tool erlang 24.3.4.0
/usr/local/buildpack/utils/linking.sh: line 18: /usr/local/bin/erl: Read-only file system
```
Overall, the current filesystem structure/installation makes it very hard to find a proper configuration to make it work with a read-only filesystem.
### If you have any ideas on how this should be implemented, please tell us here.
Not fully sure, but one idea: install renovate and any strong dependency at location other than `/opt/buildpack/tools`. This would allow us to mount a kubernetes emptydir for the whole `/opt/buildpack/tools` directory without erasing any renovate binary.
### Is this a feature you are interested in implementing yourself?
Maybe | 1.0 | Read-Only Filesystem Support - ### What would you like Renovate to be able to do?
For security compliance, we have a strong requirement to run any container in Kubernetes with a read-only filesystem. We can then mount some writeable volumes at some pre-defined filesystem locations (e.g.: /tmp)
For managers involving lockfiles, like Elixir/Python/Ruby/... managers, we're running into issues when configuring a read-only filesystem.
For example:
```
Command failed: install-tool erlang 24.3.4.0
tar: 24.3.4.0: Cannot mkdir: Read-only file system
tar: 24.3.4.0: Cannot mkdir: Read-only file system
tar: 24.3.4.0/misc: Cannot mkdir: No such file or directory
tar: 24.3.4.0: Cannot mkdir: Read-only file system
tar: 24.3.4.0/misc/format_man_pages: Cannot open: No such file or directory
tar: 24.3.4.0: Cannot mkdir: Read-only file system
tar: 24.3.4.0/misc/makewhatis: Cannot open: No such file or directory
tar: 24.3.4.0: Cannot mkdir: Read-only file system
tar: 24.3.4.0/activate.csh: Cannot open: No such file or directory
tar: 24.3.4.0: Cannot mkdir: Read-only file system
...
```
After investigating by running things locally, it seems that renovate is installing missing tools under `/opt/buildpack/tools`, and under `/opt/buildpack/tools/erlang` for erlang/mix in particular 🤔
Unfortunately, we can't make mount an entire emptyDir to /opt because the renovate binary is located under `/opt/buildpack/tools/renovate/34.108.0/bin/renovate`.
Even by mounting a writeable volume specifically for ``, we running into other cryptic errors:
```
Command failed: install-tool erlang 24.3.4.0
/usr/local/buildpack/utils/linking.sh: line 18: /usr/local/bin/erl: Read-only file system
```
Overall, the current filesystem structure/installation makes it very hard to find a proper configuration to make it work with a read-only filesystem.
### If you have any ideas on how this should be implemented, please tell us here.
Not fully sure, but one idea: install renovate and any strong dependency at location other than `/opt/buildpack/tools`. This would allow us to mount a kubernetes emptydir for the whole `/opt/buildpack/tools` directory without erasing any renovate binary.
### Is this a feature you are interested in implementing yourself?
Maybe | non_test | read only filesystem support what would you like renovate to be able to do for security compliance we have a strong requirement to run any container in kubernetes with a read only filesystem we can then mount some writeable volumes at some pre defined filesystem locations e g tmp for managers involving lockfiles like elixir python ruby managers we re running into issues when configuring a read only filesystem for example command failed install tool erlang tar cannot mkdir read only file system tar cannot mkdir read only file system tar misc cannot mkdir no such file or directory tar cannot mkdir read only file system tar misc format man pages cannot open no such file or directory tar cannot mkdir read only file system tar misc makewhatis cannot open no such file or directory tar cannot mkdir read only file system tar activate csh cannot open no such file or directory tar cannot mkdir read only file system after investigating by running things locally it seems that renovate is installing missing tools under opt buildpack tools and under opt buildpack tools erlang for erlang mix in particular 🤔 unfortunately we can t make mount an entire emptydir to opt because the renovate binary is located under opt buildpack tools renovate bin renovate even by mounting a writeable volume specifically for we running into other cryptic errors command failed install tool erlang usr local buildpack utils linking sh line usr local bin erl read only file system overall the current filesystem structure installation makes it very hard to find a proper configuration to make it work with a read only filesystem if you have any ideas on how this should be implemented please tell us here not fully sure but one idea install renovate and any strong dependency at location other than opt buildpack tools this would allow us to mount a kubernetes emptydir for the whole opt buildpack tools directory without erasing any renovate binary is this a feature you are interested in implementing yourself maybe | 0 |
197,670 | 14,938,464,441 | IssuesEvent | 2021-01-25 15:48:24 | godotengine/godot | https://api.github.com/repos/godotengine/godot | closed | My gamepad d-pad is executing is_action_just_pressed twice | bug needs testing topic:input | **Godot version:**
3.2.3.stable
**OS/device including version:**
OpenSUSE Tumbleweed 20210120 kernel Linux 5.10.7-1
**Issue description:**
When I use the gamepad to control the sprite, it executes the function two times, on the keyboard and mouse button works well.
I found a similar issue here: https://github.com/godotengine/godot/issues/43492 but it's related to mouse, and my mouse is working, so maybe it's a different bug. I even set Input.set_use_accumulated_input(false) as one comment suggests, it don't work.
I created a video showing what happens:
https://www.youtube.com/watch?v=WuNF8gArbb8
Notice that the output prints the message twice when I use the gamepad
After that I discovered one more thing, it only happens on the D-Pad, I set to the analog and works correctly, and I set to the face buttons: up to Y, down to A, left to X and right to B and works well, so maybe it's a really specific bug to how it works with the D-Pad
**Steps to reproduce:**
1 - Open and run the project
2 - Start moving the player with the d-pad of gamepad
**Minimal reproduction project:**
[TesteInput2.zip](https://github.com/godotengine/godot/files/5866927/TesteInput2.zip)
It's a simple code if don't want to import the project, just put a sprite on the scene:
```gdscript
const TILE_SIZE = 64
func _ready():
Input.set_use_accumulated_input(false)
func _input(event):
if Input.is_action_just_pressed("ui_up"):
move_cursor( 0 , -1 )
print(Input)
elif Input.is_action_pressed("ui_down") and not event.is_echo():
move_cursor( 0 , 1 )
print(Input)
elif Input.is_action_just_pressed("ui_left") and event.is_pressed():
move_cursor( -1 , 0 )
print(Input)
elif Input.is_action_just_pressed("ui_right"):
move_cursor( 1 , 0 )
print(Input)
return
func move_cursor(x , y):
$Sprite.position += Vector2(x , y) * TILE_SIZE
```
| 1.0 | My gamepad d-pad is executing is_action_just_pressed twice - **Godot version:**
3.2.3.stable
**OS/device including version:**
OpenSUSE Tumbleweed 20210120 kernel Linux 5.10.7-1
**Issue description:**
When I use the gamepad to control the sprite, it executes the function two times, on the keyboard and mouse button works well.
I found a similar issue here: https://github.com/godotengine/godot/issues/43492 but it's related to mouse, and my mouse is working, so maybe it's a different bug. I even set Input.set_use_accumulated_input(false) as one comment suggests, it don't work.
I created a video showing what happens:
https://www.youtube.com/watch?v=WuNF8gArbb8
Notice that the output prints the message twice when I use the gamepad
After that I discovered one more thing, it only happens on the D-Pad, I set to the analog and works correctly, and I set to the face buttons: up to Y, down to A, left to X and right to B and works well, so maybe it's a really specific bug to how it works with the D-Pad
**Steps to reproduce:**
1 - Open and run the project
2 - Start moving the player with the d-pad of gamepad
**Minimal reproduction project:**
[TesteInput2.zip](https://github.com/godotengine/godot/files/5866927/TesteInput2.zip)
It's a simple code if don't want to import the project, just put a sprite on the scene:
```gdscript
const TILE_SIZE = 64
func _ready():
Input.set_use_accumulated_input(false)
func _input(event):
if Input.is_action_just_pressed("ui_up"):
move_cursor( 0 , -1 )
print(Input)
elif Input.is_action_pressed("ui_down") and not event.is_echo():
move_cursor( 0 , 1 )
print(Input)
elif Input.is_action_just_pressed("ui_left") and event.is_pressed():
move_cursor( -1 , 0 )
print(Input)
elif Input.is_action_just_pressed("ui_right"):
move_cursor( 1 , 0 )
print(Input)
return
func move_cursor(x , y):
$Sprite.position += Vector2(x , y) * TILE_SIZE
```
| test | my gamepad d pad is executing is action just pressed twice godot version stable os device including version opensuse tumbleweed kernel linux issue description when i use the gamepad to control the sprite it executes the function two times on the keyboard and mouse button works well i found a similar issue here but it s related to mouse and my mouse is working so maybe it s a different bug i even set input set use accumulated input false as one comment suggests it don t work i created a video showing what happens notice that the output prints the message twice when i use the gamepad after that i discovered one more thing it only happens on the d pad i set to the analog and works correctly and i set to the face buttons up to y down to a left to x and right to b and works well so maybe it s a really specific bug to how it works with the d pad steps to reproduce open and run the project start moving the player with the d pad of gamepad minimal reproduction project it s a simple code if don t want to import the project just put a sprite on the scene gdscript const tile size func ready input set use accumulated input false func input event if input is action just pressed ui up move cursor print input elif input is action pressed ui down and not event is echo move cursor print input elif input is action just pressed ui left and event is pressed move cursor print input elif input is action just pressed ui right move cursor print input return func move cursor x y sprite position x y tile size | 1 |
50,919 | 6,134,884,344 | IssuesEvent | 2017-06-26 02:19:56 | kubernetes/kubernetes | https://api.github.com/repos/kubernetes/kubernetes | closed | K8s compile script can not trigger some syntax errors | sig/testing | **Is this a BUG REPORT or FEATURE REQUEST?**: BUG REPORT
**What happened**:
I ran into a syntax error but script can not trigger it. #47225
**What you expected to happen**:
Script can show all the syntax errors
/kind bug | 1.0 | K8s compile script can not trigger some syntax errors - **Is this a BUG REPORT or FEATURE REQUEST?**: BUG REPORT
**What happened**:
I ran into a syntax error but script can not trigger it. #47225
**What you expected to happen**:
Script can show all the syntax errors
/kind bug | test | compile script can not trigger some syntax errors is this a bug report or feature request bug report what happened i ran into a syntax error but script can not trigger it what you expected to happen script can show all the syntax errors kind bug | 1 |
439,463 | 30,698,126,383 | IssuesEvent | 2023-07-26 20:22:08 | nindaba/seke-delivery | https://api.github.com/repos/nindaba/seke-delivery | opened | DS | DOC | Remove the subscription to pricing topic | documentation | The subscription to Pricing topic is not necessary for now
| 1.0 | DS | DOC | Remove the subscription to pricing topic - The subscription to Pricing topic is not necessary for now
| non_test | ds doc remove the subscription to pricing topic the subscription to pricing topic is not necessary for now | 0 |
218,135 | 16,750,366,602 | IssuesEvent | 2021-06-11 21:52:41 | damienbod/angular-auth-oidc-client | https://api.github.com/repos/damienbod/angular-auth-oidc-client | closed | [HELP] Example or documentation for Silent Renew Code Flow with PKCE with refresh tokens | enhancement documentation | **Is your feature request related to a problem? Please describe.**
I am trying to use Silent Renew Code Flow with PKCE with refresh tokens.
Using configuration below I notice that if I refresh the page then a silent renew periodic check begins, after this time a new access token is retrieved. I am trying to determine how I can get `id_token` JWT using the `access_token`.
```
oidcConfigService.withConfig({
stsServer: server,
authWellknownEndpoint: wellKnownEndpoint,
redirectUrl: window.location.origin,
postLogoutRedirectUri: window.location.origin,
clientId: clientId,
scope: 'openid profile email',
responseType: 'code',
useRefreshToken: true,
renewTimeBeforeTokenExpiresInSeconds: 10,
silentRenew: true,
silentRenewTimeoutInSeconds: 20,
logLevel: LogLevel.Debug,
postLoginRoute: knownUser ? 'home' : 'documentation'
});
```
**Describe the solution you'd like**
If there is any example or documentation about how the library suggest to use Silent Renew Code Flow with PKCE with refresh tokens it would be very helpful, on this page it does not have any example: https://github.com/damienbod/angular-auth-oidc-client/blob/main/docs/silent-renew.md#silent-renew-code-flow-with-pkce-with-refresh-tokens
**Describe alternatives you've considered**
I need ID token provided in every request to my back-end API, and I don't want the user to have to re-authenticate when the ID token expires. I considered using https://github.com/manfredsteyer/angular-oauth2-oidc library instead because documentation seems more thorough, but I would rather not have to re-do what is already working.
**Additional context**
The authentication server is PingID, please note I don't have access to `offline_access` scope and want to avoid iframe solutions. | 1.0 | [HELP] Example or documentation for Silent Renew Code Flow with PKCE with refresh tokens - **Is your feature request related to a problem? Please describe.**
I am trying to use Silent Renew Code Flow with PKCE with refresh tokens.
Using configuration below I notice that if I refresh the page then a silent renew periodic check begins, after this time a new access token is retrieved. I am trying to determine how I can get `id_token` JWT using the `access_token`.
```
oidcConfigService.withConfig({
stsServer: server,
authWellknownEndpoint: wellKnownEndpoint,
redirectUrl: window.location.origin,
postLogoutRedirectUri: window.location.origin,
clientId: clientId,
scope: 'openid profile email',
responseType: 'code',
useRefreshToken: true,
renewTimeBeforeTokenExpiresInSeconds: 10,
silentRenew: true,
silentRenewTimeoutInSeconds: 20,
logLevel: LogLevel.Debug,
postLoginRoute: knownUser ? 'home' : 'documentation'
});
```
**Describe the solution you'd like**
If there is any example or documentation about how the library suggest to use Silent Renew Code Flow with PKCE with refresh tokens it would be very helpful, on this page it does not have any example: https://github.com/damienbod/angular-auth-oidc-client/blob/main/docs/silent-renew.md#silent-renew-code-flow-with-pkce-with-refresh-tokens
**Describe alternatives you've considered**
I need ID token provided in every request to my back-end API, and I don't want the user to have to re-authenticate when the ID token expires. I considered using https://github.com/manfredsteyer/angular-oauth2-oidc library instead because documentation seems more thorough, but I would rather not have to re-do what is already working.
**Additional context**
The authentication server is PingID, please note I don't have access to `offline_access` scope and want to avoid iframe solutions. | non_test | example or documentation for silent renew code flow with pkce with refresh tokens is your feature request related to a problem please describe i am trying to use silent renew code flow with pkce with refresh tokens using configuration below i notice that if i refresh the page then a silent renew periodic check begins after this time a new access token is retrieved i am trying to determine how i can get id token jwt using the access token oidcconfigservice withconfig stsserver server authwellknownendpoint wellknownendpoint redirecturl window location origin postlogoutredirecturi window location origin clientid clientid scope openid profile email responsetype code userefreshtoken true renewtimebeforetokenexpiresinseconds silentrenew true silentrenewtimeoutinseconds loglevel loglevel debug postloginroute knownuser home documentation describe the solution you d like if there is any example or documentation about how the library suggest to use silent renew code flow with pkce with refresh tokens it would be very helpful on this page it does not have any example describe alternatives you ve considered i need id token provided in every request to my back end api and i don t want the user to have to re authenticate when the id token expires i considered using library instead because documentation seems more thorough but i would rather not have to re do what is already working additional context the authentication server is pingid please note i don t have access to offline access scope and want to avoid iframe solutions | 0 |
720,229 | 24,784,999,849 | IssuesEvent | 2022-10-24 09:03:44 | opensquare-network/statescan-v2 | https://api.github.com/repos/opensquare-network/statescan-v2 | closed | Add extrinsics tab on account detail page | priority:high working | Currently we only have transfers tab on account detail page, but we also need the extrinsics tag. Api endpoint: `/accounts/:address/extrinsics`.
| 1.0 | Add extrinsics tab on account detail page - Currently we only have transfers tab on account detail page, but we also need the extrinsics tag. Api endpoint: `/accounts/:address/extrinsics`.
| non_test | add extrinsics tab on account detail page currently we only have transfers tab on account detail page but we also need the extrinsics tag api endpoint accounts address extrinsics | 0 |
44,984 | 5,673,207,137 | IssuesEvent | 2017-04-12 05:21:17 | FlightControl-Master/MOOSE | https://api.github.com/repos/FlightControl-Master/MOOSE | closed | SPAWN:SpawnFromUnit will not spawn 'Late Activation' Units | bug fixed ready for testing | Due to a fix in Issue #97 (IsAlive() should not count late activation units) the SpawnFromUnit function will not spawn a 'Late Activation' units because it checks to see if the unit it is spawning from is alive.
Proposed solution: Add a function to the Units wrapper called IsLateActivation() that checks to see if the referenced unit is a Late Activation unit. How can we tell this? Because DCS:isActive() returns false AND the life of the unit is greater than (or equal to) 1.0 (Unit.getLife(Unit self) as defined in the ED DCS Lua Simulator Scripting Engine documentation (http://en.wiki.eagle.ru/wiki/Simulator_Scripting_Engine/DCS:_World/Part_2#Unit)). This proposed function would work the same as UNIT:IsAlive(). | 1.0 | SPAWN:SpawnFromUnit will not spawn 'Late Activation' Units - Due to a fix in Issue #97 (IsAlive() should not count late activation units) the SpawnFromUnit function will not spawn a 'Late Activation' units because it checks to see if the unit it is spawning from is alive.
Proposed solution: Add a function to the Units wrapper called IsLateActivation() that checks to see if the referenced unit is a Late Activation unit. How can we tell this? Because DCS:isActive() returns false AND the life of the unit is greater than (or equal to) 1.0 (Unit.getLife(Unit self) as defined in the ED DCS Lua Simulator Scripting Engine documentation (http://en.wiki.eagle.ru/wiki/Simulator_Scripting_Engine/DCS:_World/Part_2#Unit)). This proposed function would work the same as UNIT:IsAlive(). | test | spawn spawnfromunit will not spawn late activation units due to a fix in issue isalive should not count late activation units the spawnfromunit function will not spawn a late activation units because it checks to see if the unit it is spawning from is alive proposed solution add a function to the units wrapper called islateactivation that checks to see if the referenced unit is a late activation unit how can we tell this because dcs isactive returns false and the life of the unit is greater than or equal to unit getlife unit self as defined in the ed dcs lua simulator scripting engine documentation this proposed function would work the same as unit isalive | 1 |
188,221 | 14,441,598,274 | IssuesEvent | 2020-12-07 16:59:58 | frontendbr/forum | https://api.github.com/repos/frontendbr/forum | closed | Testes de Integração e Testes E2E | Testes | Na _issue_ #43, o @lnfnunes me perguntou o seguinte:
> @vitorbritto valeu pelos links!
> Por favor, poderia me explicar melhor qual a diferença (prática), entre:
>
> Testes de Integração: Pioneer
> Testes de E2E: DalekJS
>
> Me pareceu que com qualquer 1 dos dois eu consigo atingir o mesmo objetivo, então fiquei com essa dúvida do pq vc separou os dois em ferramentas diferentes.
> Seria a questão das sintaxes ou envolve outros detalhes? Como vc utiliza no seu workflow?
> Tks
Resolvi abrir uma _issue_ para não perdermos o foco da discussão sobre **testes de perfomance** na #43 e falarmos um pouco mais sobre testes de integração e E2E (aceitação). =]
---
@lnfnunes legal você perguntar isso! :+1:
Bom, alguns desenvolvedores confundem o princípio básico para os testes de integração e testes E2E.
Para mim, o **Teste de Integração** é realizado para cobrir o maior número possível de falhas entre componentes/módulos de um sistema. O princípio básico dos testes de integração é a verificação da estabilidade entre estes componentes em conjunto, bem como o fluxo apropriado dos dados entre eles. Você pode imaginar que um teste de integração é composto por vários testes unitários combinados entre sí, mas diferente dos testes unitários, os testes de integração fazem uso de qualquer meio necessário para comprovar que o código e o ambiente estejam adequados e seja candidato a ir para produção.
Já os **Testes E2E** são baseados em regras e/ou requisitos associados à uma ação do usuário. Você parte do princípio que deverão existir reações satisfatórias para determinadas ações na sua interface (sucesso em um redirecionamento a partir de um link clicado, a validação de um formulário, se o pagamento de um produto foi confirmado, se o produto foi adicionado ao carrinho corretamente, etc). Eu considero que os testes E2E estejam inseridos no contexto para os **Testes de Aceitação**.
E vocês? Utilizam ferramentas ou realizam testes de integração e aceitação também? =]
| 1.0 | Testes de Integração e Testes E2E - Na _issue_ #43, o @lnfnunes me perguntou o seguinte:
> @vitorbritto valeu pelos links!
> Por favor, poderia me explicar melhor qual a diferença (prática), entre:
>
> Testes de Integração: Pioneer
> Testes de E2E: DalekJS
>
> Me pareceu que com qualquer 1 dos dois eu consigo atingir o mesmo objetivo, então fiquei com essa dúvida do pq vc separou os dois em ferramentas diferentes.
> Seria a questão das sintaxes ou envolve outros detalhes? Como vc utiliza no seu workflow?
> Tks
Resolvi abrir uma _issue_ para não perdermos o foco da discussão sobre **testes de perfomance** na #43 e falarmos um pouco mais sobre testes de integração e E2E (aceitação). =]
---
@lnfnunes legal você perguntar isso! :+1:
Bom, alguns desenvolvedores confundem o princípio básico para os testes de integração e testes E2E.
Para mim, o **Teste de Integração** é realizado para cobrir o maior número possível de falhas entre componentes/módulos de um sistema. O princípio básico dos testes de integração é a verificação da estabilidade entre estes componentes em conjunto, bem como o fluxo apropriado dos dados entre eles. Você pode imaginar que um teste de integração é composto por vários testes unitários combinados entre sí, mas diferente dos testes unitários, os testes de integração fazem uso de qualquer meio necessário para comprovar que o código e o ambiente estejam adequados e seja candidato a ir para produção.
Já os **Testes E2E** são baseados em regras e/ou requisitos associados à uma ação do usuário. Você parte do princípio que deverão existir reações satisfatórias para determinadas ações na sua interface (sucesso em um redirecionamento a partir de um link clicado, a validação de um formulário, se o pagamento de um produto foi confirmado, se o produto foi adicionado ao carrinho corretamente, etc). Eu considero que os testes E2E estejam inseridos no contexto para os **Testes de Aceitação**.
E vocês? Utilizam ferramentas ou realizam testes de integração e aceitação também? =]
| test | testes de integração e testes na issue o lnfnunes me perguntou o seguinte vitorbritto valeu pelos links por favor poderia me explicar melhor qual a diferença prática entre testes de integração pioneer testes de dalekjs me pareceu que com qualquer dos dois eu consigo atingir o mesmo objetivo então fiquei com essa dúvida do pq vc separou os dois em ferramentas diferentes seria a questão das sintaxes ou envolve outros detalhes como vc utiliza no seu workflow tks resolvi abrir uma issue para não perdermos o foco da discussão sobre testes de perfomance na e falarmos um pouco mais sobre testes de integração e aceitação lnfnunes legal você perguntar isso bom alguns desenvolvedores confundem o princípio básico para os testes de integração e testes para mim o teste de integração é realizado para cobrir o maior número possível de falhas entre componentes módulos de um sistema o princípio básico dos testes de integração é a verificação da estabilidade entre estes componentes em conjunto bem como o fluxo apropriado dos dados entre eles você pode imaginar que um teste de integração é composto por vários testes unitários combinados entre sí mas diferente dos testes unitários os testes de integração fazem uso de qualquer meio necessário para comprovar que o código e o ambiente estejam adequados e seja candidato a ir para produção já os testes são baseados em regras e ou requisitos associados à uma ação do usuário você parte do princípio que deverão existir reações satisfatórias para determinadas ações na sua interface sucesso em um redirecionamento a partir de um link clicado a validação de um formulário se o pagamento de um produto foi confirmado se o produto foi adicionado ao carrinho corretamente etc eu considero que os testes estejam inseridos no contexto para os testes de aceitação e vocês utilizam ferramentas ou realizam testes de integração e aceitação também | 1 |
546,141 | 16,004,799,134 | IssuesEvent | 2021-04-20 00:41:29 | flexpool/frontend | https://api.github.com/repos/flexpool/frontend | closed | New miner without data issues | priority:moderate type:bug | 1) shows joined 51 years ago
Seems like the data is not coming in or is undefined | 1.0 | New miner without data issues - 1) shows joined 51 years ago
Seems like the data is not coming in or is undefined | non_test | new miner without data issues shows joined years ago seems like the data is not coming in or is undefined | 0 |
28,613 | 4,424,045,858 | IssuesEvent | 2016-08-16 10:55:01 | medic/medic-webapp | https://api.github.com/repos/medic/medic-webapp | closed | There is no link to medic-reporter in 2.x | 4 - Acceptance Testing Bug v0.4 features in 2.x | On a server with `medic-reported` installed and visible in dashboard, there is no in-app link to `medic-reporter`. It can be accessed directly at `/medic-reporter/_design/medic-reporter/_rewrite`. | 1.0 | There is no link to medic-reporter in 2.x - On a server with `medic-reported` installed and visible in dashboard, there is no in-app link to `medic-reporter`. It can be accessed directly at `/medic-reporter/_design/medic-reporter/_rewrite`. | test | there is no link to medic reporter in x on a server with medic reported installed and visible in dashboard there is no in app link to medic reporter it can be accessed directly at medic reporter design medic reporter rewrite | 1 |
29,624 | 11,764,517,206 | IssuesEvent | 2020-03-14 13:04:58 | uniquelyparticular/sync-stripe-to-zendesk | https://api.github.com/repos/uniquelyparticular/sync-stripe-to-zendesk | opened | WS-2020-0042 (High) detected in acorn-5.7.3.tgz, acorn-6.1.1.tgz | security vulnerability | ## WS-2020-0042 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>acorn-5.7.3.tgz</b>, <b>acorn-6.1.1.tgz</b></p></summary>
<p>
<details><summary><b>acorn-5.7.3.tgz</b></p></summary>
<p>ECMAScript parser</p>
<p>Library home page: <a href="https://registry.npmjs.org/acorn/-/acorn-5.7.3.tgz">https://registry.npmjs.org/acorn/-/acorn-5.7.3.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/sync-stripe-to-zendesk/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/sync-stripe-to-zendesk/node_modules/acorn/package.json</p>
<p>
Dependency Hierarchy:
- jest-24.8.0.tgz (Root Library)
- jest-cli-24.8.0.tgz
- jest-config-24.8.0.tgz
- jest-environment-jsdom-24.8.0.tgz
- jsdom-11.12.0.tgz
- :x: **acorn-5.7.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>acorn-6.1.1.tgz</b></p></summary>
<p>ECMAScript parser</p>
<p>Library home page: <a href="https://registry.npmjs.org/acorn/-/acorn-6.1.1.tgz">https://registry.npmjs.org/acorn/-/acorn-6.1.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/sync-stripe-to-zendesk/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/sync-stripe-to-zendesk/node_modules/acorn-globals/node_modules/acorn/package.json</p>
<p>
Dependency Hierarchy:
- jest-24.8.0.tgz (Root Library)
- jest-cli-24.8.0.tgz
- jest-config-24.8.0.tgz
- jest-environment-jsdom-24.8.0.tgz
- jsdom-11.12.0.tgz
- acorn-globals-4.3.2.tgz
- :x: **acorn-6.1.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/uniquelyparticular/sync-stripe-to-zendesk/commit/c455789b66d2278272d86c74f0d4b5970aee52d1">c455789b66d2278272d86c74f0d4b5970aee52d1</a></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>
acorn is vulnerable to REGEX DoS. A regex of the form /[x-\ud800]/u causes the parser to enter an infinite loop. attackers may leverage the vulnerability leading to a Denial of Service since the string is not valid UTF16 and it results in it being sanitized before reaching the parser.
<p>Publish Date: 2020-03-08
<p>URL: <a href=https://github.com/acornjs/acorn/commit/b5c17877ac0511e31579ea31e7650ba1a5871e51>WS-2020-0042</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1488">https://www.npmjs.com/advisories/1488</a></p>
<p>Release Date: 2020-03-08</p>
<p>Fix Resolution: 7.1.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2020-0042 (High) detected in acorn-5.7.3.tgz, acorn-6.1.1.tgz - ## WS-2020-0042 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>acorn-5.7.3.tgz</b>, <b>acorn-6.1.1.tgz</b></p></summary>
<p>
<details><summary><b>acorn-5.7.3.tgz</b></p></summary>
<p>ECMAScript parser</p>
<p>Library home page: <a href="https://registry.npmjs.org/acorn/-/acorn-5.7.3.tgz">https://registry.npmjs.org/acorn/-/acorn-5.7.3.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/sync-stripe-to-zendesk/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/sync-stripe-to-zendesk/node_modules/acorn/package.json</p>
<p>
Dependency Hierarchy:
- jest-24.8.0.tgz (Root Library)
- jest-cli-24.8.0.tgz
- jest-config-24.8.0.tgz
- jest-environment-jsdom-24.8.0.tgz
- jsdom-11.12.0.tgz
- :x: **acorn-5.7.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>acorn-6.1.1.tgz</b></p></summary>
<p>ECMAScript parser</p>
<p>Library home page: <a href="https://registry.npmjs.org/acorn/-/acorn-6.1.1.tgz">https://registry.npmjs.org/acorn/-/acorn-6.1.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/sync-stripe-to-zendesk/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/sync-stripe-to-zendesk/node_modules/acorn-globals/node_modules/acorn/package.json</p>
<p>
Dependency Hierarchy:
- jest-24.8.0.tgz (Root Library)
- jest-cli-24.8.0.tgz
- jest-config-24.8.0.tgz
- jest-environment-jsdom-24.8.0.tgz
- jsdom-11.12.0.tgz
- acorn-globals-4.3.2.tgz
- :x: **acorn-6.1.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/uniquelyparticular/sync-stripe-to-zendesk/commit/c455789b66d2278272d86c74f0d4b5970aee52d1">c455789b66d2278272d86c74f0d4b5970aee52d1</a></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>
acorn is vulnerable to REGEX DoS. A regex of the form /[x-\ud800]/u causes the parser to enter an infinite loop. attackers may leverage the vulnerability leading to a Denial of Service since the string is not valid UTF16 and it results in it being sanitized before reaching the parser.
<p>Publish Date: 2020-03-08
<p>URL: <a href=https://github.com/acornjs/acorn/commit/b5c17877ac0511e31579ea31e7650ba1a5871e51>WS-2020-0042</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1488">https://www.npmjs.com/advisories/1488</a></p>
<p>Release Date: 2020-03-08</p>
<p>Fix Resolution: 7.1.1</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 | ws high detected in acorn tgz acorn tgz ws high severity vulnerability vulnerable libraries acorn tgz acorn tgz acorn tgz ecmascript parser library home page a href path to dependency file tmp ws scm sync stripe to zendesk package json path to vulnerable library tmp ws scm sync stripe to zendesk node modules acorn package json dependency hierarchy jest tgz root library jest cli tgz jest config tgz jest environment jsdom tgz jsdom tgz x acorn tgz vulnerable library acorn tgz ecmascript parser library home page a href path to dependency file tmp ws scm sync stripe to zendesk package json path to vulnerable library tmp ws scm sync stripe to zendesk node modules acorn globals node modules acorn package json dependency hierarchy jest tgz root library jest cli tgz jest config tgz jest environment jsdom tgz jsdom tgz acorn globals tgz x acorn tgz vulnerable library found in head commit a href vulnerability details acorn is vulnerable to regex dos a regex of the form u causes the parser to enter an infinite loop attackers may leverage the vulnerability leading to a denial of service since the string is not valid and it results in it being sanitized before reaching the parser publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
327,604 | 28,072,829,763 | IssuesEvent | 2023-03-29 20:28:22 | solo-io/gloo | https://api.github.com/repos/solo-io/gloo | closed | E2E Suite Test Flakes (Dynamic Forward Proxy) | Type: Bug Type: CI Test Flake | ### Gloo Edge Version
1.14.x (beta)
### Kubernetes Version
None
### Describe the bug
logs
https://storage.googleapis.com/solo-public-build-logs/logs.html?buildid=6ffc68b6-601d-469b-8516-0940ef00f9bd
```
Step #1 - "run-tests": Step #8 - "run-e2e-tests": [38;5;9m[FAILED] Timed out after 10.037s.
Step #1 - "run-tests": Step #8 - "run-e2e-tests": The function passed to Eventually failed at /workspace/gloo/test/e2e/dynamic_forward_proxy_test.go:90 with:
Step #1 - "run-tests": Step #8 - "run-e2e-tests": Unexpected error: Get "http://localhost:11177/get": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Step #1 - "run-tests": Step #8 - "run-e2e-tests": <*url.Error | 0xc0088ddce0>: {
Step #1 - "run-tests": Step #8 - "run-e2e-tests": Op: "Get",
Step #1 - "run-tests": Step #8 - "run-e2e-tests": URL: "http://localhost:11177/get",
Step #1 - "run-tests": Step #8 - "run-e2e-tests": Err: <*http.httpError | 0xc00a311068>{
Step #1 - "run-tests": Step #8 - "run-e2e-tests": err: "context deadline exceeded (Client.Timeout exceeded while awaiting headers)",
Step #1 - "run-tests": Step #8 - "run-e2e-tests": timeout: true,
Step #1 - "run-tests": Step #8 - "run-e2e-tests": },
Step #1 - "run-tests": Step #8 - "run-e2e-tests": }[0m
Step #1 - "run-tests": Step #8 - "run-e2e-tests": [38;5;9mIn [1m[It][0m[38;5;9m at: [1m/workspace/gloo/test/e2e/dynamic_forward_proxy_test.go:94[0m [38;5;243m@ 03/28/23 13:53:17.629[0m
Step #1 - "run-tests": Step #8 - "run-e2e-tests":
Step #1 - "run-tests": Step #8 - "run-e2e-tests": [38;5;9mFull Stack Trace[0m
Step #1 - "run-tests": Step #8 - "run-e2e-tests": github.com/solo-io/gloo/test/e2e_test.glob..func11.5.2()
Step #1 - "run-tests": Step #8 - "run-e2e-tests": /workspace/gloo/test/e2e/dynamic_forward_proxy_test.go:94 +0x283
Step #1 - "run-tests": Step #8 - "run-e2e-tests": [38;5;243m------------------------------[0m
```
### Steps to reproduce the bug
Run in CI, you might get this
### Expected Behavior
Test to pass
### Additional Context
_No response_ | 1.0 | E2E Suite Test Flakes (Dynamic Forward Proxy) - ### Gloo Edge Version
1.14.x (beta)
### Kubernetes Version
None
### Describe the bug
logs
https://storage.googleapis.com/solo-public-build-logs/logs.html?buildid=6ffc68b6-601d-469b-8516-0940ef00f9bd
```
Step #1 - "run-tests": Step #8 - "run-e2e-tests": [38;5;9m[FAILED] Timed out after 10.037s.
Step #1 - "run-tests": Step #8 - "run-e2e-tests": The function passed to Eventually failed at /workspace/gloo/test/e2e/dynamic_forward_proxy_test.go:90 with:
Step #1 - "run-tests": Step #8 - "run-e2e-tests": Unexpected error: Get "http://localhost:11177/get": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Step #1 - "run-tests": Step #8 - "run-e2e-tests": <*url.Error | 0xc0088ddce0>: {
Step #1 - "run-tests": Step #8 - "run-e2e-tests": Op: "Get",
Step #1 - "run-tests": Step #8 - "run-e2e-tests": URL: "http://localhost:11177/get",
Step #1 - "run-tests": Step #8 - "run-e2e-tests": Err: <*http.httpError | 0xc00a311068>{
Step #1 - "run-tests": Step #8 - "run-e2e-tests": err: "context deadline exceeded (Client.Timeout exceeded while awaiting headers)",
Step #1 - "run-tests": Step #8 - "run-e2e-tests": timeout: true,
Step #1 - "run-tests": Step #8 - "run-e2e-tests": },
Step #1 - "run-tests": Step #8 - "run-e2e-tests": }[0m
Step #1 - "run-tests": Step #8 - "run-e2e-tests": [38;5;9mIn [1m[It][0m[38;5;9m at: [1m/workspace/gloo/test/e2e/dynamic_forward_proxy_test.go:94[0m [38;5;243m@ 03/28/23 13:53:17.629[0m
Step #1 - "run-tests": Step #8 - "run-e2e-tests":
Step #1 - "run-tests": Step #8 - "run-e2e-tests": [38;5;9mFull Stack Trace[0m
Step #1 - "run-tests": Step #8 - "run-e2e-tests": github.com/solo-io/gloo/test/e2e_test.glob..func11.5.2()
Step #1 - "run-tests": Step #8 - "run-e2e-tests": /workspace/gloo/test/e2e/dynamic_forward_proxy_test.go:94 +0x283
Step #1 - "run-tests": Step #8 - "run-e2e-tests": [38;5;243m------------------------------[0m
```
### Steps to reproduce the bug
Run in CI, you might get this
### Expected Behavior
Test to pass
### Additional Context
_No response_ | test | suite test flakes dynamic forward proxy gloo edge version x beta kubernetes version none describe the bug logs step run tests step run tests timed out after step run tests step run tests the function passed to eventually failed at workspace gloo test dynamic forward proxy test go with step run tests step run tests unexpected error get context deadline exceeded client timeout exceeded while awaiting headers step run tests step run tests step run tests step run tests op get step run tests step run tests url step run tests step run tests err step run tests step run tests err context deadline exceeded client timeout exceeded while awaiting headers step run tests step run tests timeout true step run tests step run tests step run tests step run tests step run tests step run tests at workspace gloo test dynamic forward proxy test go step run tests step run tests step run tests step run tests stack trace step run tests step run tests github com solo io gloo test test glob step run tests step run tests workspace gloo test dynamic forward proxy test go step run tests step run tests steps to reproduce the bug run in ci you might get this expected behavior test to pass additional context no response | 1 |
97,646 | 8,665,015,196 | IssuesEvent | 2018-11-28 21:55:58 | ONRR/doi-extractives-data | https://api.github.com/repos/ONRR/doi-extractives-data | closed | Even out padding on What's new section | Home Page bug:visual workflow:testing | There is unbalanced padding on the What's new section (more at the top than bottom). Let's even out the spacing.
| 1.0 | Even out padding on What's new section - There is unbalanced padding on the What's new section (more at the top than bottom). Let's even out the spacing.
| test | even out padding on what s new section there is unbalanced padding on the what s new section more at the top than bottom let s even out the spacing | 1 |
111,228 | 9,523,415,510 | IssuesEvent | 2019-04-27 17:03:55 | rootzoll/raspiblitz | https://api.github.com/repos/rootzoll/raspiblitz | closed | System/LND Scanning Rewrite | final testing | People get often stuck on the Lightning Scanning Process, seeing a ?/SOMENUMBER - which is done by 80scanLND.sh:
https://github.com/rootzoll/raspiblitz/issues/450
So the goal was to rewrite this part to try to get rid of this situation or at least to provide more info/help on this situations. | 1.0 | System/LND Scanning Rewrite - People get often stuck on the Lightning Scanning Process, seeing a ?/SOMENUMBER - which is done by 80scanLND.sh:
https://github.com/rootzoll/raspiblitz/issues/450
So the goal was to rewrite this part to try to get rid of this situation or at least to provide more info/help on this situations. | test | system lnd scanning rewrite people get often stuck on the lightning scanning process seeing a somenumber which is done by sh so the goal was to rewrite this part to try to get rid of this situation or at least to provide more info help on this situations | 1 |
818,480 | 30,691,085,886 | IssuesEvent | 2023-07-26 15:13:16 | GoogleChrome/lighthouse | https://api.github.com/repos/GoogleChrome/lighthouse | closed | Wrong viewport in screenshots with `headless: 'new'` | bug needs-priority | ### FAQ
- [X] Yes, my issue is not about [variability](https://github.com/GoogleChrome/lighthouse/blob/main/docs/variability.md) or [throttling](https://github.com/GoogleChrome/lighthouse/blob/main/docs/throttling.md).
- [X] Yes, my issue is not about a specific accessibility audit (file with [axe-core](https://github.com/dequelabs/axe-core) instead).
### URL
https://example.com
### What happened?
Since we switched to launch puppeteer with `headless: 'new'`, the viewport of the screenshot is wrong. It appears as if it would use the default window size instead of the emulated screen.
Repro: https://github.com/sokki/bug-new-headless-screenshot/blob/main/index.js
With `headless: 'new'`:
With `headless: true`:
### What did you expect?
Properly sized screenshot.
### What have you tried?
_No response_
### How were you running Lighthouse?
node
### Lighthouse Version
10.4.0
### Chrome Version
115.0.0.0
### Node Version
18
### OS
mac + linux
### Relevant log output
_No response_ | 1.0 | Wrong viewport in screenshots with `headless: 'new'` - ### FAQ
- [X] Yes, my issue is not about [variability](https://github.com/GoogleChrome/lighthouse/blob/main/docs/variability.md) or [throttling](https://github.com/GoogleChrome/lighthouse/blob/main/docs/throttling.md).
- [X] Yes, my issue is not about a specific accessibility audit (file with [axe-core](https://github.com/dequelabs/axe-core) instead).
### URL
https://example.com
### What happened?
Since we switched to launch puppeteer with `headless: 'new'`, the viewport of the screenshot is wrong. It appears as if it would use the default window size instead of the emulated screen.
Repro: https://github.com/sokki/bug-new-headless-screenshot/blob/main/index.js
With `headless: 'new'`:
With `headless: true`:
### What did you expect?
Properly sized screenshot.
### What have you tried?
_No response_
### How were you running Lighthouse?
node
### Lighthouse Version
10.4.0
### Chrome Version
115.0.0.0
### Node Version
18
### OS
mac + linux
### Relevant log output
_No response_ | non_test | wrong viewport in screenshots with headless new faq yes my issue is not about or yes my issue is not about a specific accessibility audit file with instead url what happened since we switched to launch puppeteer with headless new the viewport of the screenshot is wrong it appears as if it would use the default window size instead of the emulated screen repro with headless new with headless true what did you expect properly sized screenshot what have you tried no response how were you running lighthouse node lighthouse version chrome version node version os mac linux relevant log output no response | 0 |
1,096 | 14,006,839,267 | IssuesEvent | 2020-10-28 20:35:46 | AzureAD/microsoft-identity-web | https://api.github.com/repos/AzureAD/microsoft-identity-web | closed | [Investigate] developer experience when required`"SignUpSignInPolicyId": "",` is not included in configuration options | b2c investigate supportability | Currently, we detect B2C if the `"SignUpSignInPolicyId": "b2c_1_susi",` is present in the configuration. with the changes i've made to checking the required options parameters, if the above is not present, we assume it's AAD (this has not changed) and then we will throw a missing tenant-id error, as tenant-id is required for AAD but not B2C:
`System.ArgumentNullException: 'The TenantId parameter cannot be null or whitespace, and must be included in the configuration of the web app. For instance, in the appsettings.json file. (Parameter 'TenantId')'`
Need to investigate further the developer experience and decide if this is the best way to detect b2c or not...probably not a better way as b2c can have custom domains (we'll hit the same issue MSAL has today with detecting B2C).
PS. I'm not sure what happens today if the su-si policy is not present, will check and update here.
@jmprieur thoughts? | True | [Investigate] developer experience when required`"SignUpSignInPolicyId": "",` is not included in configuration options - Currently, we detect B2C if the `"SignUpSignInPolicyId": "b2c_1_susi",` is present in the configuration. with the changes i've made to checking the required options parameters, if the above is not present, we assume it's AAD (this has not changed) and then we will throw a missing tenant-id error, as tenant-id is required for AAD but not B2C:
`System.ArgumentNullException: 'The TenantId parameter cannot be null or whitespace, and must be included in the configuration of the web app. For instance, in the appsettings.json file. (Parameter 'TenantId')'`
Need to investigate further the developer experience and decide if this is the best way to detect b2c or not...probably not a better way as b2c can have custom domains (we'll hit the same issue MSAL has today with detecting B2C).
PS. I'm not sure what happens today if the su-si policy is not present, will check and update here.
@jmprieur thoughts? | non_test | developer experience when required signupsigninpolicyid is not included in configuration options currently we detect if the signupsigninpolicyid susi is present in the configuration with the changes i ve made to checking the required options parameters if the above is not present we assume it s aad this has not changed and then we will throw a missing tenant id error as tenant id is required for aad but not system argumentnullexception the tenantid parameter cannot be null or whitespace and must be included in the configuration of the web app for instance in the appsettings json file parameter tenantid need to investigate further the developer experience and decide if this is the best way to detect or not probably not a better way as can have custom domains we ll hit the same issue msal has today with detecting ps i m not sure what happens today if the su si policy is not present will check and update here jmprieur thoughts | 0 |
59,727 | 6,661,946,405 | IssuesEvent | 2017-10-02 10:56:08 | puikinsh/illdy | https://api.github.com/repos/puikinsh/illdy | closed | Parallax jumping on mobile | tested | I’m noticing a strange issue on a site I’ve built at fazeducation.com. On Chrome/Firefox in iOS, the background “jumps” or zooms upon scrolling. I have tried a few workarounds to no avail, and also see the same effect on the Shapely demo. Videos here for reference:
https://www.dropbox.com/s/6wmzsxcsgxp0pfy/shapely-demo.mov?dl=0
https://www.dropbox.com/s/lzs5py72ncbnig4/faz-education.mov?dl=0
https://colorlib.com/wp/forums/topic/parallax-image-jumping-effect-in-chromefirefox-ios/
| 1.0 | Parallax jumping on mobile - I’m noticing a strange issue on a site I’ve built at fazeducation.com. On Chrome/Firefox in iOS, the background “jumps” or zooms upon scrolling. I have tried a few workarounds to no avail, and also see the same effect on the Shapely demo. Videos here for reference:
https://www.dropbox.com/s/6wmzsxcsgxp0pfy/shapely-demo.mov?dl=0
https://www.dropbox.com/s/lzs5py72ncbnig4/faz-education.mov?dl=0
https://colorlib.com/wp/forums/topic/parallax-image-jumping-effect-in-chromefirefox-ios/
| test | parallax jumping on mobile i’m noticing a strange issue on a site i’ve built at fazeducation com on chrome firefox in ios the background “jumps” or zooms upon scrolling i have tried a few workarounds to no avail and also see the same effect on the shapely demo videos here for reference | 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.