Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 5 112 | repo_url stringlengths 34 141 | action stringclasses 3 values | title stringlengths 1 844 | labels stringlengths 4 721 | body stringlengths 1 261k | index stringclasses 12 values | text_combine stringlengths 96 261k | label stringclasses 2 values | text stringlengths 96 248k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
252,562 | 27,245,807,515 | IssuesEvent | 2023-02-22 01:50:18 | turkdevops/angular | https://api.github.com/repos/turkdevops/angular | closed | WS-2023-0004 (High) detected in jszip-3.3.0.tgz - autoclosed | security vulnerability | ## WS-2023-0004 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jszip-3.3.0.tgz</b></p></summary>
<p>Create, read and edit .zip files with JavaScript http://stuartk.com/jszip</p>
<p>Library home page: <a href="https://registry.npmjs.org/jszip/-/jszip-3.3.0.tgz">https://registry.npmjs.org/jszip/-/jszip-3.3.0.tgz</a></p>
<p>
Dependency Hierarchy:
- selenium-webdriver-3.5.0.tgz (Root Library)
- :x: **jszip-3.3.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>labs/router</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>
jszip before 3.8.0 does not sanitize filenames when files are loaded with `loadAsync`, which makes the library vunerable to zip-slip attack.
<p>Publish Date: 2023-01-04
<p>URL: <a href=https://github.com/Stuk/jszip/commit/2edab366119c9ee948357c02f1206c28566cdf15>WS-2023-0004</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.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</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>Release Date: 2023-01-04</p>
<p>Fix Resolution (jszip): 3.6.0</p>
<p>Direct dependency fix Resolution (selenium-webdriver): 3.6.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2023-0004 (High) detected in jszip-3.3.0.tgz - autoclosed - ## WS-2023-0004 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jszip-3.3.0.tgz</b></p></summary>
<p>Create, read and edit .zip files with JavaScript http://stuartk.com/jszip</p>
<p>Library home page: <a href="https://registry.npmjs.org/jszip/-/jszip-3.3.0.tgz">https://registry.npmjs.org/jszip/-/jszip-3.3.0.tgz</a></p>
<p>
Dependency Hierarchy:
- selenium-webdriver-3.5.0.tgz (Root Library)
- :x: **jszip-3.3.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>labs/router</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>
jszip before 3.8.0 does not sanitize filenames when files are loaded with `loadAsync`, which makes the library vunerable to zip-slip attack.
<p>Publish Date: 2023-01-04
<p>URL: <a href=https://github.com/Stuk/jszip/commit/2edab366119c9ee948357c02f1206c28566cdf15>WS-2023-0004</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.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</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>Release Date: 2023-01-04</p>
<p>Fix Resolution (jszip): 3.6.0</p>
<p>Direct dependency fix Resolution (selenium-webdriver): 3.6.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | ws high detected in jszip tgz autoclosed ws high severity vulnerability vulnerable library jszip tgz create read and edit zip files with javascript library home page a href dependency hierarchy selenium webdriver tgz root library x jszip tgz vulnerable library found in base branch labs router vulnerability details jszip before does not sanitize filenames when files are loaded with loadasync which makes the library vunerable to zip slip attack publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version release date fix resolution jszip direct dependency fix resolution selenium webdriver step up your open source security game with mend | 0 |
33,910 | 7,296,315,698 | IssuesEvent | 2018-02-26 10:21:05 | escape-llc/yet-another-chart-component | https://api.github.com/repos/escape-llc/yet-another-chart-component | opened | Layout throws ArgumentException | chart defect | # Summary
On phone, the demo application triggers an `ArgumentException` in the `Chart` during layout, when the `Padding` exceeds the actual dimensions.
This occurs when clicking to open the sidebar panel, because it "shrinks" the `Chart` in one dimension beyond its padding.
# Actual Behavior
Shrinking the `Chart` to a size where the `Rect` width and/or height becomes *less than zero* triggers an `ArgumentException` from the `Rect` constructor.
# Expected Behavior
Not.
# Additional Details
Precondition the constructor call. Specifically, ignore any padding when it would compromise the size of the `Chart` bounds. | 1.0 | Layout throws ArgumentException - # Summary
On phone, the demo application triggers an `ArgumentException` in the `Chart` during layout, when the `Padding` exceeds the actual dimensions.
This occurs when clicking to open the sidebar panel, because it "shrinks" the `Chart` in one dimension beyond its padding.
# Actual Behavior
Shrinking the `Chart` to a size where the `Rect` width and/or height becomes *less than zero* triggers an `ArgumentException` from the `Rect` constructor.
# Expected Behavior
Not.
# Additional Details
Precondition the constructor call. Specifically, ignore any padding when it would compromise the size of the `Chart` bounds. | non_priority | layout throws argumentexception summary on phone the demo application triggers an argumentexception in the chart during layout when the padding exceeds the actual dimensions this occurs when clicking to open the sidebar panel because it shrinks the chart in one dimension beyond its padding actual behavior shrinking the chart to a size where the rect width and or height becomes less than zero triggers an argumentexception from the rect constructor expected behavior not additional details precondition the constructor call specifically ignore any padding when it would compromise the size of the chart bounds | 0 |
51,890 | 7,735,659,529 | IssuesEvent | 2018-05-27 17:31:09 | hackoregon/civic-devops | https://api.github.com/repos/hackoregon/civic-devops | closed | Update all Travis repos to the new env var naming | documentation-needed | Once we PR the new env vars across the repos, we need to verify that the correctly-named env vars are populated in the corresponding Travis settings.
## Canonical set of env vars needed in each Travis repo
- AWS_ACCESS_KEY_ID
- AWS_DEFAULT_REGION
- AWS_SECRET_ACCESS_KEY
- DJANGO_SECRET_KEY
- DOCKER_IMAGE
- DOCKER_REPO
- DOCKER_REPO_NAMESPACE
- DOCKER_SERVICE
- ECS_CLUSTER
- ECS_SERVICE_NAME
- POSTGRES_HOST
- POSTGRES_NAME
- POSTGRES_PASSWORD
- POSTGRES_PORT
- POSTGRES_USER
## Projects to check
- [x] [disaster-resilience-backend](https://travis-ci.org/hackoregon/disaster-resilience-backend)
- [x] [elections-2018-backend](https://travis-ci.org/hackoregon/elections-2018-backend)
- [x] [housing-2018](https://travis-ci.org/hackoregon/housing-2018)
- [x] [neighborhoods-2018](https://travis-ci.org/hackoregon/neighborhoods-2018)
- [x] [transportation-systems-backend-2018](https://travis-ci.org/hackoregon/transportation-systems-backend-2018) | 1.0 | Update all Travis repos to the new env var naming - Once we PR the new env vars across the repos, we need to verify that the correctly-named env vars are populated in the corresponding Travis settings.
## Canonical set of env vars needed in each Travis repo
- AWS_ACCESS_KEY_ID
- AWS_DEFAULT_REGION
- AWS_SECRET_ACCESS_KEY
- DJANGO_SECRET_KEY
- DOCKER_IMAGE
- DOCKER_REPO
- DOCKER_REPO_NAMESPACE
- DOCKER_SERVICE
- ECS_CLUSTER
- ECS_SERVICE_NAME
- POSTGRES_HOST
- POSTGRES_NAME
- POSTGRES_PASSWORD
- POSTGRES_PORT
- POSTGRES_USER
## Projects to check
- [x] [disaster-resilience-backend](https://travis-ci.org/hackoregon/disaster-resilience-backend)
- [x] [elections-2018-backend](https://travis-ci.org/hackoregon/elections-2018-backend)
- [x] [housing-2018](https://travis-ci.org/hackoregon/housing-2018)
- [x] [neighborhoods-2018](https://travis-ci.org/hackoregon/neighborhoods-2018)
- [x] [transportation-systems-backend-2018](https://travis-ci.org/hackoregon/transportation-systems-backend-2018) | non_priority | update all travis repos to the new env var naming once we pr the new env vars across the repos we need to verify that the correctly named env vars are populated in the corresponding travis settings canonical set of env vars needed in each travis repo aws access key id aws default region aws secret access key django secret key docker image docker repo docker repo namespace docker service ecs cluster ecs service name postgres host postgres name postgres password postgres port postgres user projects to check | 0 |
234,310 | 19,142,363,038 | IssuesEvent | 2021-12-02 01:16:53 | boostcampwm-2021/iOS06-MateRunner | https://api.github.com/repos/boostcampwm-2021/iOS06-MateRunner | closed | [단위 테스트] RecordDetailUseCase | 유진 test | ## 🗣 설명
```swift
protocol RecordDetailUseCase {
var runningResult: RunningResult { get }
var nickname: String? { get }
}
```
## 📋 체크리스트
> 구현해야하는 이슈 체크리스트
- [ ] 단위테스트 작성
| 1.0 | [단위 테스트] RecordDetailUseCase - ## 🗣 설명
```swift
protocol RecordDetailUseCase {
var runningResult: RunningResult { get }
var nickname: String? { get }
}
```
## 📋 체크리스트
> 구현해야하는 이슈 체크리스트
- [ ] 단위테스트 작성
| non_priority | recorddetailusecase 🗣 설명 swift protocol recorddetailusecase var runningresult runningresult get var nickname string get 📋 체크리스트 구현해야하는 이슈 체크리스트 단위테스트 작성 | 0 |
80,453 | 10,014,143,169 | IssuesEvent | 2019-07-15 16:46:15 | phetsims/fluid-pressure-and-flow | https://api.github.com/repos/phetsims/fluid-pressure-and-flow | opened | Issues with friction representation on Flow screen | design:general | For #325
A user reported:
> To whom it may concern:
>
>I am a science content reviewer for resources which are posted on a web site for teachers: http://www.cpalms.org/resources/ResourceSearch.aspx
>
>In your simulation at:
http://phet.colorado.edu/en/simulation/fluid-pressure-and-flow
the “Flow” simulation when” friction” in added is wrong in the following sense. To have flow down a horizontal pipe when there is friction then a horizontal pressure gradient in the fluid must exist. That is, for example, the pressure at the opening of the pipe at the left must be greater, at the same level, than that at the pipe exit. The pressures in your “friction” simulation are only hydrostatic. For the simulated frictional flow there must be a constant, negative pressure gradient down the pipe.
>
>Please let me know if this site is ever modified as per the above comment.
Oliver replied 6/23/13
>We met on Thursday and agree that this issue will need to be fixed. We are planning to port this simulation to HTML5 and will fix this issue in the redesign. We estimate the port will be redesigned and released in the next year.
>
>Read more about our HTML5 conversion effort: http://phet.colorado.edu/2013/the-future-of-phet
>
>Thanks for pointing this issue out!
This seems like an issue that merits further discussion. As far as I can tell, no changes were made based on this user feedback. @kathy-phet @ariel-phet? | 1.0 | Issues with friction representation on Flow screen - For #325
A user reported:
> To whom it may concern:
>
>I am a science content reviewer for resources which are posted on a web site for teachers: http://www.cpalms.org/resources/ResourceSearch.aspx
>
>In your simulation at:
http://phet.colorado.edu/en/simulation/fluid-pressure-and-flow
the “Flow” simulation when” friction” in added is wrong in the following sense. To have flow down a horizontal pipe when there is friction then a horizontal pressure gradient in the fluid must exist. That is, for example, the pressure at the opening of the pipe at the left must be greater, at the same level, than that at the pipe exit. The pressures in your “friction” simulation are only hydrostatic. For the simulated frictional flow there must be a constant, negative pressure gradient down the pipe.
>
>Please let me know if this site is ever modified as per the above comment.
Oliver replied 6/23/13
>We met on Thursday and agree that this issue will need to be fixed. We are planning to port this simulation to HTML5 and will fix this issue in the redesign. We estimate the port will be redesigned and released in the next year.
>
>Read more about our HTML5 conversion effort: http://phet.colorado.edu/2013/the-future-of-phet
>
>Thanks for pointing this issue out!
This seems like an issue that merits further discussion. As far as I can tell, no changes were made based on this user feedback. @kathy-phet @ariel-phet? | non_priority | issues with friction representation on flow screen for a user reported to whom it may concern i am a science content reviewer for resources which are posted on a web site for teachers in your simulation at the “flow” simulation when” friction” in added is wrong in the following sense to have flow down a horizontal pipe when there is friction then a horizontal pressure gradient in the fluid must exist that is for example the pressure at the opening of the pipe at the left must be greater at the same level than that at the pipe exit the pressures in your “friction” simulation are only hydrostatic for the simulated frictional flow there must be a constant negative pressure gradient down the pipe please let me know if this site is ever modified as per the above comment oliver replied we met on thursday and agree that this issue will need to be fixed we are planning to port this simulation to and will fix this issue in the redesign we estimate the port will be redesigned and released in the next year read more about our conversion effort thanks for pointing this issue out this seems like an issue that merits further discussion as far as i can tell no changes were made based on this user feedback kathy phet ariel phet | 0 |
179,450 | 21,571,417,258 | IssuesEvent | 2022-05-02 08:40:35 | apache/bookkeeper | https://api.github.com/repos/apache/bookkeeper | closed | Add support for https in Vertx HTTP server | type/feature area/security area/http triage/week-4 | **FEATURE REQUEST**
1. Please describe the feature you are requesting.
Currently default http server (Vertx) do not start an https endpoint, we need such feature in order to be able to expose Booke endpoint with a minimal level of security.
2. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have).
Are you currently using any workarounds to address this issue?
must-have
3. Provide any additional detail on your proposed use case for this feature.
Configuration:
- keystore (PKCS12 format is enough, anyway just use the Verx config API)
- keystorePassword
- certificate chain (truststore)
- client auth (none, supported, required)
there is no need to enable automatic reload of the certificate | True | Add support for https in Vertx HTTP server - **FEATURE REQUEST**
1. Please describe the feature you are requesting.
Currently default http server (Vertx) do not start an https endpoint, we need such feature in order to be able to expose Booke endpoint with a minimal level of security.
2. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have).
Are you currently using any workarounds to address this issue?
must-have
3. Provide any additional detail on your proposed use case for this feature.
Configuration:
- keystore (PKCS12 format is enough, anyway just use the Verx config API)
- keystorePassword
- certificate chain (truststore)
- client auth (none, supported, required)
there is no need to enable automatic reload of the certificate | non_priority | add support for https in vertx http server feature request please describe the feature you are requesting currently default http server vertx do not start an https endpoint we need such feature in order to be able to expose booke endpoint with a minimal level of security indicate the importance of this issue to you blocker must have should have nice to have are you currently using any workarounds to address this issue must have provide any additional detail on your proposed use case for this feature configuration keystore format is enough anyway just use the verx config api keystorepassword certificate chain truststore client auth none supported required there is no need to enable automatic reload of the certificate | 0 |
4,899 | 2,755,144,353 | IssuesEvent | 2015-04-26 11:11:25 | PerlDancer/Dancer2 | https://api.github.com/repos/PerlDancer/Dancer2 | closed | Hooks for plugins not registered | Bug Testing | It's possible to register hook only for last included plugin.
I have modified test to demonstrate this issue.
Please take a look: https://github.com/e11it/Dancer2/commit/9ed2da3bd2d8c211e7fa11dad78c5715f32b21ea
Test fails with:
```
t/plugin_syntax.t ............ 1/? Invalid hook name `third_hook' at /Dancer2/Core/DSL.pm line 143.
# Child (hooks in plugins) exited without calling finalize()
# Failed test 'hooks in plugins'
# at /System/Library/Perl/5.16/Test/Builder.pm line 252.
# Tests were run but no plan was declared and done_testing() was not seen.
``` | 1.0 | Hooks for plugins not registered - It's possible to register hook only for last included plugin.
I have modified test to demonstrate this issue.
Please take a look: https://github.com/e11it/Dancer2/commit/9ed2da3bd2d8c211e7fa11dad78c5715f32b21ea
Test fails with:
```
t/plugin_syntax.t ............ 1/? Invalid hook name `third_hook' at /Dancer2/Core/DSL.pm line 143.
# Child (hooks in plugins) exited without calling finalize()
# Failed test 'hooks in plugins'
# at /System/Library/Perl/5.16/Test/Builder.pm line 252.
# Tests were run but no plan was declared and done_testing() was not seen.
``` | non_priority | hooks for plugins not registered it s possible to register hook only for last included plugin i have modified test to demonstrate this issue please take a look test fails with t plugin syntax t invalid hook name third hook at core dsl pm line child hooks in plugins exited without calling finalize failed test hooks in plugins at system library perl test builder pm line tests were run but no plan was declared and done testing was not seen | 0 |
6,183 | 13,887,822,895 | IssuesEvent | 2020-10-19 04:57:02 | freddy33/qsm-go | https://api.github.com/repos/freddy33/qsm-go | closed | Create a cache system on top of DB ids | architecture backend enhancement | PathNode for now needs to be dynamically loaded and than evicted based on size. A murmur based hashmap with size max will be helpful. Needs to be linked to the memory sync pool. | 1.0 | Create a cache system on top of DB ids - PathNode for now needs to be dynamically loaded and than evicted based on size. A murmur based hashmap with size max will be helpful. Needs to be linked to the memory sync pool. | non_priority | create a cache system on top of db ids pathnode for now needs to be dynamically loaded and than evicted based on size a murmur based hashmap with size max will be helpful needs to be linked to the memory sync pool | 0 |
188,045 | 14,437,108,037 | IssuesEvent | 2020-12-07 11:03:39 | iterative/dvc | https://api.github.com/repos/iterative/dvc | closed | remote: test webdav | good first issue help wanted p3-nice-to-have testing | Creating issue so that we do not forget this.
Webdav was implemented on https://github.com/iterative/dvc/pull/4256. | 1.0 | remote: test webdav - Creating issue so that we do not forget this.
Webdav was implemented on https://github.com/iterative/dvc/pull/4256. | non_priority | remote test webdav creating issue so that we do not forget this webdav was implemented on | 0 |
245,196 | 26,520,078,067 | IssuesEvent | 2023-01-19 01:15:37 | kapseliboi/ILIAS-Pegasus | https://api.github.com/repos/kapseliboi/ILIAS-Pegasus | opened | CVE-2022-25901 (Medium) detected in cookiejar-2.1.2.tgz | security vulnerability | ## CVE-2022-25901 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>cookiejar-2.1.2.tgz</b></p></summary>
<p>simple persistent cookiejar system</p>
<p>Library home page: <a href="https://registry.npmjs.org/cookiejar/-/cookiejar-2.1.2.tgz">https://registry.npmjs.org/cookiejar/-/cookiejar-2.1.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/cookiejar/package.json</p>
<p>
Dependency Hierarchy:
- cli-6.12.1.tgz (Root Library)
- superagent-5.3.1.tgz
- :x: **cookiejar-2.1.2.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Versions of the package cookiejar before 2.1.4 are vulnerable to Regular Expression Denial of Service (ReDoS) via the Cookie.parse function, which uses an insecure regular expression.
<p>Publish Date: 2023-01-18
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-25901>CVE-2022-25901</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</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>Release Date: 2023-01-18</p>
<p>Fix Resolution: cookiejar - 2.1.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-25901 (Medium) detected in cookiejar-2.1.2.tgz - ## CVE-2022-25901 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>cookiejar-2.1.2.tgz</b></p></summary>
<p>simple persistent cookiejar system</p>
<p>Library home page: <a href="https://registry.npmjs.org/cookiejar/-/cookiejar-2.1.2.tgz">https://registry.npmjs.org/cookiejar/-/cookiejar-2.1.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/cookiejar/package.json</p>
<p>
Dependency Hierarchy:
- cli-6.12.1.tgz (Root Library)
- superagent-5.3.1.tgz
- :x: **cookiejar-2.1.2.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Versions of the package cookiejar before 2.1.4 are vulnerable to Regular Expression Denial of Service (ReDoS) via the Cookie.parse function, which uses an insecure regular expression.
<p>Publish Date: 2023-01-18
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-25901>CVE-2022-25901</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</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>Release Date: 2023-01-18</p>
<p>Fix Resolution: cookiejar - 2.1.4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in cookiejar tgz cve medium severity vulnerability vulnerable library cookiejar tgz simple persistent cookiejar system library home page a href path to dependency file package json path to vulnerable library node modules cookiejar package json dependency hierarchy cli tgz root library superagent tgz x cookiejar tgz vulnerable library found in base branch master vulnerability details versions of the package cookiejar before are vulnerable to regular expression denial of service redos via the cookie parse function which uses an insecure regular expression 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 low for more information on scores click a href suggested fix type upgrade version release date fix resolution cookiejar step up your open source security game with mend | 0 |
64,530 | 7,811,048,197 | IssuesEvent | 2018-06-12 08:56:31 | locdb/locdb-frend | https://api.github.com/repos/locdb/locdb-frend | closed | Store Configuration of Agenda Filters | design feature usability | Currently, the agenda filters get reset to their default each time the agenda is accessed.
We should remember the filters (`OCR_PROCESSED`, ...) for the time of a single session.
- [x] First: check how this is best implemented. | 1.0 | Store Configuration of Agenda Filters - Currently, the agenda filters get reset to their default each time the agenda is accessed.
We should remember the filters (`OCR_PROCESSED`, ...) for the time of a single session.
- [x] First: check how this is best implemented. | non_priority | store configuration of agenda filters currently the agenda filters get reset to their default each time the agenda is accessed we should remember the filters ocr processed for the time of a single session first check how this is best implemented | 0 |
61,604 | 7,480,629,550 | IssuesEvent | 2018-04-04 18:00:48 | oracle/weblogic-deploy-tooling | https://api.github.com/repos/oracle/weblogic-deploy-tooling | opened | Resource messages from external projects need to be added to wlsdeploy_rb.properties file | design workaround | It looks like the way that things are currently designed, the new weblogic-deploy-testing project has to use the same wlsdeploy_rb.properties file as the weblogic-deploy-tooling project, in order to use Java or python classes in the weblogic-deploy-tooling project. This is because currently, it looks like PlatformLogger python wrapper only knows about a single bundle (xxx_rb.properties) file. It loads that when it's initialized, and will only resolve message IDs (e.g. WLSDPLY-09804) contained in that single bundle file.
This is not a bug. It's more of a design or implementation choice that was made, which can be worked around...hence the "design workaround" label. | 1.0 | Resource messages from external projects need to be added to wlsdeploy_rb.properties file - It looks like the way that things are currently designed, the new weblogic-deploy-testing project has to use the same wlsdeploy_rb.properties file as the weblogic-deploy-tooling project, in order to use Java or python classes in the weblogic-deploy-tooling project. This is because currently, it looks like PlatformLogger python wrapper only knows about a single bundle (xxx_rb.properties) file. It loads that when it's initialized, and will only resolve message IDs (e.g. WLSDPLY-09804) contained in that single bundle file.
This is not a bug. It's more of a design or implementation choice that was made, which can be worked around...hence the "design workaround" label. | non_priority | resource messages from external projects need to be added to wlsdeploy rb properties file it looks like the way that things are currently designed the new weblogic deploy testing project has to use the same wlsdeploy rb properties file as the weblogic deploy tooling project in order to use java or python classes in the weblogic deploy tooling project this is because currently it looks like platformlogger python wrapper only knows about a single bundle xxx rb properties file it loads that when it s initialized and will only resolve message ids e g wlsdply contained in that single bundle file this is not a bug it s more of a design or implementation choice that was made which can be worked around hence the design workaround label | 0 |
99,430 | 30,451,518,837 | IssuesEvent | 2023-07-16 11:05:59 | status-im/status-mobile | https://api.github.com/repos/status-im/status-mobile | reopened | No Android SDK available for Nix builds on Darwin aarch64 | android E:MobileBuild E:MDeveloperXP | When @Jonathansoufer tried to build on his Mac with M1 `aarch64` CPU it fails with:
```
No Android SDK tarballs are available for system architecture: aarch64-darwin
```
Which is caused by this `if` in Android SDK derivation:
```nix
{
# Determine the Android os identifier from Nix's system identifier
os = if stdenv.system == "x86_64-linux" then "linux"
else if stdenv.system == "x86_64-darwin" then "macosx"
else throw "No Android SDK tarballs are available for system architecture: ${stdenv.system}";
}
```
https://github.com/NixOS/nixpkgs/blob/65135081/pkgs/development/mobile/androidenv/compose-android-packages.nix#L31-L34
Since currently packages do not appear to include any `aarch64-darwin` builds:
https://github.com/NixOS/nixpkgs/blob/65135081/pkgs/development/mobile/androidenv/repo.json
__EDIT__: The current solution is to simply not use an `arm64` shell to run builds, but instead use the [Rosetta 2](https://en.wikipedia.org/wiki/Rosetta_(software)) dynamic binary translator through the `arch -x86_64` command or [`Terminal x86` application](https://www.notion.so/Run-x86-Apps-including-homebrew-in-the-Terminal-on-Apple-Silicon-8350b43d97de4ce690f283277e958602). | 1.0 | No Android SDK available for Nix builds on Darwin aarch64 - When @Jonathansoufer tried to build on his Mac with M1 `aarch64` CPU it fails with:
```
No Android SDK tarballs are available for system architecture: aarch64-darwin
```
Which is caused by this `if` in Android SDK derivation:
```nix
{
# Determine the Android os identifier from Nix's system identifier
os = if stdenv.system == "x86_64-linux" then "linux"
else if stdenv.system == "x86_64-darwin" then "macosx"
else throw "No Android SDK tarballs are available for system architecture: ${stdenv.system}";
}
```
https://github.com/NixOS/nixpkgs/blob/65135081/pkgs/development/mobile/androidenv/compose-android-packages.nix#L31-L34
Since currently packages do not appear to include any `aarch64-darwin` builds:
https://github.com/NixOS/nixpkgs/blob/65135081/pkgs/development/mobile/androidenv/repo.json
__EDIT__: The current solution is to simply not use an `arm64` shell to run builds, but instead use the [Rosetta 2](https://en.wikipedia.org/wiki/Rosetta_(software)) dynamic binary translator through the `arch -x86_64` command or [`Terminal x86` application](https://www.notion.so/Run-x86-Apps-including-homebrew-in-the-Terminal-on-Apple-Silicon-8350b43d97de4ce690f283277e958602). | non_priority | no android sdk available for nix builds on darwin when jonathansoufer tried to build on his mac with cpu it fails with no android sdk tarballs are available for system architecture darwin which is caused by this if in android sdk derivation nix determine the android os identifier from nix s system identifier os if stdenv system linux then linux else if stdenv system darwin then macosx else throw no android sdk tarballs are available for system architecture stdenv system since currently packages do not appear to include any darwin builds edit the current solution is to simply not use an shell to run builds but instead use the dynamic binary translator through the arch command or | 0 |
295,152 | 25,458,432,876 | IssuesEvent | 2022-11-24 16:06:50 | SAP/fundamental-ngx | https://api.github.com/repos/SAP/fundamental-ngx | closed | test(platform): file-uploader - add control-value-accessor tests | platform ariba unit tests | #### Is this a bug, enhancement, or feature request?
enhancement
#### Briefly describe your proposal.
there's no test coverage for control value accessor of `platform-file-uploader`. This can lead to not standardised behavior or even bugs
#### Which versions of Angular and Fundamental Library for Angular are affected? (If this is a feature request, use current version.)
fundamental-ngx@0.33
#### 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 | test(platform): file-uploader - add control-value-accessor tests - #### Is this a bug, enhancement, or feature request?
enhancement
#### Briefly describe your proposal.
there's no test coverage for control value accessor of `platform-file-uploader`. This can lead to not standardised behavior or even bugs
#### Which versions of Angular and Fundamental Library for Angular are affected? (If this is a feature request, use current version.)
fundamental-ngx@0.33
#### 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_priority | test platform file uploader add control value accessor tests is this a bug enhancement or feature request enhancement briefly describe your proposal there s no test coverage for control value accessor of platform file uploader this can lead to not standardised behavior or even bugs which versions of angular and fundamental library for angular are affected if this is a feature request use current version fundamental ngx 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 |
77,691 | 21,932,425,002 | IssuesEvent | 2022-05-23 10:56:43 | OpenAssetIO/OpenAssetIO | https://api.github.com/repos/OpenAssetIO/OpenAssetIO | closed | [Build] Better handling of `clean` CMake target | bug build | # What
Redesign CMake code, especially where `add_custom_command` is used, so that it behaves as expected when the `clean` target is executed. If feasible, ensure that `clean` followed by a build + test succeeds when offline.
# Why
In general `clean` has not been well considered in the CMake code up until this point, so there may be several issues.
In particular, the CMake code makes use of `add_custom_command` in several places, especially in the targets for running Python tests.
The `OUTPUT` of an `add_custom_command` is used to allow targets to depend on the presence of a command output (i.e. execute the command iff the `OUTPUT` file(s) is not found).
However, the `OUTPUT` file(s) are deleted when running the `clean` target. Our usage didn't consider that, so we can end up with e.g. a broken Python environment left around with no `pip` executable, after `clean`ing.
See #309 and https://github.com/TheFoundryVisionmongers/OpenAssetIO/pull/309#discussion_r842652391
# AC
- The `clean` target should revert the build tree only, leaving the installation untouched.
- ~Don't clean per-downloaded python _build_ deps in clean (eg: the `pip`, `setuptools`), do those a separate `clean-offline-cache` target.~ (Easy enough to do just removing the `build` dir)
- Move default `dist` to `build/dist` | 1.0 | [Build] Better handling of `clean` CMake target - # What
Redesign CMake code, especially where `add_custom_command` is used, so that it behaves as expected when the `clean` target is executed. If feasible, ensure that `clean` followed by a build + test succeeds when offline.
# Why
In general `clean` has not been well considered in the CMake code up until this point, so there may be several issues.
In particular, the CMake code makes use of `add_custom_command` in several places, especially in the targets for running Python tests.
The `OUTPUT` of an `add_custom_command` is used to allow targets to depend on the presence of a command output (i.e. execute the command iff the `OUTPUT` file(s) is not found).
However, the `OUTPUT` file(s) are deleted when running the `clean` target. Our usage didn't consider that, so we can end up with e.g. a broken Python environment left around with no `pip` executable, after `clean`ing.
See #309 and https://github.com/TheFoundryVisionmongers/OpenAssetIO/pull/309#discussion_r842652391
# AC
- The `clean` target should revert the build tree only, leaving the installation untouched.
- ~Don't clean per-downloaded python _build_ deps in clean (eg: the `pip`, `setuptools`), do those a separate `clean-offline-cache` target.~ (Easy enough to do just removing the `build` dir)
- Move default `dist` to `build/dist` | non_priority | better handling of clean cmake target what redesign cmake code especially where add custom command is used so that it behaves as expected when the clean target is executed if feasible ensure that clean followed by a build test succeeds when offline why in general clean has not been well considered in the cmake code up until this point so there may be several issues in particular the cmake code makes use of add custom command in several places especially in the targets for running python tests the output of an add custom command is used to allow targets to depend on the presence of a command output i e execute the command iff the output file s is not found however the output file s are deleted when running the clean target our usage didn t consider that so we can end up with e g a broken python environment left around with no pip executable after clean ing see and ac the clean target should revert the build tree only leaving the installation untouched don t clean per downloaded python build deps in clean eg the pip setuptools do those a separate clean offline cache target easy enough to do just removing the build dir move default dist to build dist | 0 |
73,913 | 15,286,452,947 | IssuesEvent | 2021-02-23 14:43:19 | wouter140/PortfolioSite | https://api.github.com/repos/wouter140/PortfolioSite | closed | CVE-2018-19826 (Medium) detected in portfolio-v1.0.0, node-sass-4.13.1.tgz | security vulnerability | ## CVE-2018-19826 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>node-sass-4.13.1.tgz</b></p></summary>
<p>
<details><summary><b>node-sass-4.13.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/PortfolioSite/package.json</p>
<p>Path to vulnerable library: /PortfolioSite/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.13.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/wouter140/PortfolioSite/commit/5e211947fdfe3701bd2dc55db9ed2cf44fc06c98">5e211947fdfe3701bd2dc55db9ed2cf44fc06c98</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
** DISPUTED ** In inspect.cpp in LibSass 3.5.5, a high memory footprint caused by an endless loop (containing a Sass::Inspect::operator()(Sass::String_Quoted*) stack frame) may cause a Denial of Service via crafted sass input files with stray '&' or '/' characters. NOTE: Upstream comments indicate this issue is closed as "won't fix" and "works as intended" by design.
<p>Publish Date: 2018-12-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19826>CVE-2018-19826</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>6.5</b>)</summary>
<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>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19826">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19826</a></p>
<p>Release Date: 2019-09-01</p>
<p>Fix Resolution: LibSass - 3.6.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2018-19826 (Medium) detected in portfolio-v1.0.0, node-sass-4.13.1.tgz - ## CVE-2018-19826 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>node-sass-4.13.1.tgz</b></p></summary>
<p>
<details><summary><b>node-sass-4.13.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/PortfolioSite/package.json</p>
<p>Path to vulnerable library: /PortfolioSite/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.13.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/wouter140/PortfolioSite/commit/5e211947fdfe3701bd2dc55db9ed2cf44fc06c98">5e211947fdfe3701bd2dc55db9ed2cf44fc06c98</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
** DISPUTED ** In inspect.cpp in LibSass 3.5.5, a high memory footprint caused by an endless loop (containing a Sass::Inspect::operator()(Sass::String_Quoted*) stack frame) may cause a Denial of Service via crafted sass input files with stray '&' or '/' characters. NOTE: Upstream comments indicate this issue is closed as "won't fix" and "works as intended" by design.
<p>Publish Date: 2018-12-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19826>CVE-2018-19826</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>6.5</b>)</summary>
<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>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19826">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19826</a></p>
<p>Release Date: 2019-09-01</p>
<p>Fix Resolution: LibSass - 3.6.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_priority | cve medium detected in portfolio node sass tgz cve medium severity vulnerability vulnerable libraries node sass tgz node sass tgz wrapper around libsass library home page a href path to dependency file tmp ws scm portfoliosite package json path to vulnerable library portfoliosite node modules node sass package json dependency hierarchy x node sass tgz vulnerable library found in head commit a href vulnerability details disputed in inspect cpp in libsass a high memory footprint caused by an endless loop containing a sass inspect operator sass string quoted stack frame may cause a denial of service via crafted sass input files with stray or characters note upstream comments indicate this issue is closed as won t fix and works as intended by design 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 libsass step up your open source security game with whitesource | 0 |
69,409 | 8,405,585,795 | IssuesEvent | 2018-10-11 15:36:22 | Opentrons/opentrons | https://api.github.com/repos/Opentrons/opentrons | opened | PD Liquids Management: Liquids Instructional Content | feature protocol designer | As a protocol designer, I would like instructions for what to do on the Liquids tab when I first get there.
## Acceptance Criteria
- [ ] Add instructional copy to right panel of liquids tab | 1.0 | PD Liquids Management: Liquids Instructional Content - As a protocol designer, I would like instructions for what to do on the Liquids tab when I first get there.
## Acceptance Criteria
- [ ] Add instructional copy to right panel of liquids tab | non_priority | pd liquids management liquids instructional content as a protocol designer i would like instructions for what to do on the liquids tab when i first get there acceptance criteria add instructional copy to right panel of liquids tab | 0 |
70,024 | 7,174,980,959 | IssuesEvent | 2018-01-31 02:32:12 | Microsoft/vscode | https://api.github.com/repos/Microsoft/vscode | closed | Test running a DebugAdapter inside the extension | debug testplan-item | Test for #40906:
Complexity: 3
- [x] Windows - **@roblourens**
- [x] OS X or Linux - **@isidorn**
For simple debug adapters that are implemented in JS/TS and are closely tied to the extension code it is an overkill and development hassle to run them as a separate process.
In this milestone I've explored a way to run the DA inside the extension.
Here is the necessary code for Mock debug (Embedded-DA branch):
https://github.com/Microsoft/vscode-mock-debug/blob/3ac4bde255a4eb51411011ea121b3a8df456f330/src/extension.ts#L59-L76
Verify for the Embedded-DA branch of Mock Debug:
- after pressing "F5" you can debug both the extension code and DA in a single debugger instance.
- after creating a packaged vsix and installing this into VS Code Mock Debug works as before (when running the DA separate from the extension). | 1.0 | Test running a DebugAdapter inside the extension - Test for #40906:
Complexity: 3
- [x] Windows - **@roblourens**
- [x] OS X or Linux - **@isidorn**
For simple debug adapters that are implemented in JS/TS and are closely tied to the extension code it is an overkill and development hassle to run them as a separate process.
In this milestone I've explored a way to run the DA inside the extension.
Here is the necessary code for Mock debug (Embedded-DA branch):
https://github.com/Microsoft/vscode-mock-debug/blob/3ac4bde255a4eb51411011ea121b3a8df456f330/src/extension.ts#L59-L76
Verify for the Embedded-DA branch of Mock Debug:
- after pressing "F5" you can debug both the extension code and DA in a single debugger instance.
- after creating a packaged vsix and installing this into VS Code Mock Debug works as before (when running the DA separate from the extension). | non_priority | test running a debugadapter inside the extension test for complexity windows roblourens os x or linux isidorn for simple debug adapters that are implemented in js ts and are closely tied to the extension code it is an overkill and development hassle to run them as a separate process in this milestone i ve explored a way to run the da inside the extension here is the necessary code for mock debug embedded da branch verify for the embedded da branch of mock debug after pressing you can debug both the extension code and da in a single debugger instance after creating a packaged vsix and installing this into vs code mock debug works as before when running the da separate from the extension | 0 |
168,174 | 14,141,153,892 | IssuesEvent | 2020-11-10 12:17:16 | tripu/faker.js | https://api.github.com/repos/tripu/faker.js | opened | Update all references (Marak → tripu) | bug documentation | * [ ] GH links
* [ ] Travis CI
* [ ] npm.js
* [ ] Badges
* [ ] Rawgit
* [ ] Sponsorship
* [ ] Copyright
* [ ] Metadata | 1.0 | Update all references (Marak → tripu) - * [ ] GH links
* [ ] Travis CI
* [ ] npm.js
* [ ] Badges
* [ ] Rawgit
* [ ] Sponsorship
* [ ] Copyright
* [ ] Metadata | non_priority | update all references marak → tripu gh links travis ci npm js badges rawgit sponsorship copyright metadata | 0 |
336,318 | 24,492,941,996 | IssuesEvent | 2022-10-10 05:25:27 | keptn-sandbox/datadog-service | https://api.github.com/repos/keptn-sandbox/datadog-service | closed | Add info about auto-signoff in the README | documentation good first issue | ## Summary
We have a DCO check which runs on every PR to check if the commit has been signed off.
Doing
```
git commit --amend --signoff
```
or something like
```
git rebase HEAD~2 --signoff
```
is inconvenient. Signing off can be automated by adding the following hook in the local `.git` folder:
```bash
#!/bin/sh
#
# An example hook script to prepare the commit log message.
# Called by "git commit" with the name of the file that has the
# commit message, followed by the description of the commit
# message's source. The hook's purpose is to edit the commit
# message file. If the hook fails with a non-zero status,
# the commit is aborted.
#
# To enable this hook, rename this file to "prepare-commit-msg".
# This hook includes three examples. The first comments out the
# "Conflicts:" part of a merge commit.
#
# The second includes the output of "git diff --name-status -r"
# into the message, just before the "git status" output. It is
# commented because it doesn't cope with --amend or with squashed
# commits.
#
# The third example adds a Signed-off-by line to the message, that can
# still be edited. This is rarely a good idea.
SOB=$(git var GIT_AUTHOR_IDENT | sed -n 's/^\(.*>\).*$/Signed-off-by: \1/p')
grep -qs "^$SOB" "$1" || echo "$SOB" >> "$1"
```
This needs be put in the `.git/hooks/prepare-commit-msg` file (you need to create a new file called `prepare-commit-msg`) and give it permission to execute using:
```
chmod +x .git/hooks/prepare-commit-msg
```
## TODO
- [ ] Add info about this in the README after https://github.com/keptn-sandbox/datadog-service#testing-cloud-events (create a heading called `Auto signoff commit messages`
- [ ] Raise a PR and get it merged
| 1.0 | Add info about auto-signoff in the README - ## Summary
We have a DCO check which runs on every PR to check if the commit has been signed off.
Doing
```
git commit --amend --signoff
```
or something like
```
git rebase HEAD~2 --signoff
```
is inconvenient. Signing off can be automated by adding the following hook in the local `.git` folder:
```bash
#!/bin/sh
#
# An example hook script to prepare the commit log message.
# Called by "git commit" with the name of the file that has the
# commit message, followed by the description of the commit
# message's source. The hook's purpose is to edit the commit
# message file. If the hook fails with a non-zero status,
# the commit is aborted.
#
# To enable this hook, rename this file to "prepare-commit-msg".
# This hook includes three examples. The first comments out the
# "Conflicts:" part of a merge commit.
#
# The second includes the output of "git diff --name-status -r"
# into the message, just before the "git status" output. It is
# commented because it doesn't cope with --amend or with squashed
# commits.
#
# The third example adds a Signed-off-by line to the message, that can
# still be edited. This is rarely a good idea.
SOB=$(git var GIT_AUTHOR_IDENT | sed -n 's/^\(.*>\).*$/Signed-off-by: \1/p')
grep -qs "^$SOB" "$1" || echo "$SOB" >> "$1"
```
This needs be put in the `.git/hooks/prepare-commit-msg` file (you need to create a new file called `prepare-commit-msg`) and give it permission to execute using:
```
chmod +x .git/hooks/prepare-commit-msg
```
## TODO
- [ ] Add info about this in the README after https://github.com/keptn-sandbox/datadog-service#testing-cloud-events (create a heading called `Auto signoff commit messages`
- [ ] Raise a PR and get it merged
| non_priority | add info about auto signoff in the readme summary we have a dco check which runs on every pr to check if the commit has been signed off doing git commit amend signoff or something like git rebase head signoff is inconvenient signing off can be automated by adding the following hook in the local git folder bash bin sh an example hook script to prepare the commit log message called by git commit with the name of the file that has the commit message followed by the description of the commit message s source the hook s purpose is to edit the commit message file if the hook fails with a non zero status the commit is aborted to enable this hook rename this file to prepare commit msg this hook includes three examples the first comments out the conflicts part of a merge commit the second includes the output of git diff name status r into the message just before the git status output it is commented because it doesn t cope with amend or with squashed commits the third example adds a signed off by line to the message that can still be edited this is rarely a good idea sob git var git author ident sed n s signed off by p grep qs sob echo sob this needs be put in the git hooks prepare commit msg file you need to create a new file called prepare commit msg and give it permission to execute using chmod x git hooks prepare commit msg todo add info about this in the readme after create a heading called auto signoff commit messages raise a pr and get it merged | 0 |
49,307 | 12,312,777,138 | IssuesEvent | 2020-05-12 14:24:18 | netlify/build | https://api.github.com/repos/netlify/build | closed | Report in the UI when some plugins fail without making the whole build fail | project/build-plugins-v1 type: feature | When plugins choose to fail, they can either:
- `utils.build.failBuild()`: make whole build fail
- `utils.build.failPlugin()`: make the plugin fail, but let other plugins and the whole build continue
I am not quite sure which approach we are encouraging. I am assuming the second is more lenient and might be a better DX (not sure what you think about this).
Either way, when plugins choose to use `utils.build.failPlugin()`, the build logs show the plugin error but the UI show the build as successful, so those error messages might be missed by the user.
Unlike the UI items related to error reporting from #711 and #735, this specific item requires additional work in `@netlify/build`. Failed builds and canceled builds (`failBuild()` and `cancelBuild()`) are handled in a top-level error handler and we have all error information to send to the API for the UI to display. But failed plugins (`failPlugin()`) are not aggregated by any top-level function, i.e. cannot be sent to the API for the UI to display at the moment. So `@netlify/build` first need to add some logic there to do this. | 1.0 | Report in the UI when some plugins fail without making the whole build fail - When plugins choose to fail, they can either:
- `utils.build.failBuild()`: make whole build fail
- `utils.build.failPlugin()`: make the plugin fail, but let other plugins and the whole build continue
I am not quite sure which approach we are encouraging. I am assuming the second is more lenient and might be a better DX (not sure what you think about this).
Either way, when plugins choose to use `utils.build.failPlugin()`, the build logs show the plugin error but the UI show the build as successful, so those error messages might be missed by the user.
Unlike the UI items related to error reporting from #711 and #735, this specific item requires additional work in `@netlify/build`. Failed builds and canceled builds (`failBuild()` and `cancelBuild()`) are handled in a top-level error handler and we have all error information to send to the API for the UI to display. But failed plugins (`failPlugin()`) are not aggregated by any top-level function, i.e. cannot be sent to the API for the UI to display at the moment. So `@netlify/build` first need to add some logic there to do this. | non_priority | report in the ui when some plugins fail without making the whole build fail when plugins choose to fail they can either utils build failbuild make whole build fail utils build failplugin make the plugin fail but let other plugins and the whole build continue i am not quite sure which approach we are encouraging i am assuming the second is more lenient and might be a better dx not sure what you think about this either way when plugins choose to use utils build failplugin the build logs show the plugin error but the ui show the build as successful so those error messages might be missed by the user unlike the ui items related to error reporting from and this specific item requires additional work in netlify build failed builds and canceled builds failbuild and cancelbuild are handled in a top level error handler and we have all error information to send to the api for the ui to display but failed plugins failplugin are not aggregated by any top level function i e cannot be sent to the api for the ui to display at the moment so netlify build first need to add some logic there to do this | 0 |
13,989 | 10,082,624,909 | IssuesEvent | 2019-07-25 11:45:20 | MicrosoftDocs/azure-docs | https://api.github.com/repos/MicrosoftDocs/azure-docs | closed | Supported locales ? | Pri2 bing-spell-check/subsvc cognitive-services/svc cxp product-question triaged | What is the actual supported `mkt` list for Bing spell checker? The list on this page is different from:
https://docs.microsoft.com/en-us/rest/api/cognitiveservices-bingsearch/bing-spell-check-api-v7-reference#market-codes
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: b6e03b67-8c6c-2749-7778-99f7dca069c6
* Version Independent ID: a6ee8911-2630-d6c4-81c7-28a5fdf4b767
* Content: [Language support - Bing Spell Check API - Azure Cognitive Services](https://docs.microsoft.com/en-us/azure/cognitive-services/bing-spell-check/language-support)
* Content Source: [articles/cognitive-services/Bing-Spell-Check/language-support.md](https://github.com/Microsoft/azure-docs/blob/master/articles/cognitive-services/Bing-Spell-Check/language-support.md)
* Service: **cognitive-services**
* Sub-service: **bing-spell-check**
* GitHub Login: @aahill
* Microsoft Alias: **aahi** | 1.0 | Supported locales ? - What is the actual supported `mkt` list for Bing spell checker? The list on this page is different from:
https://docs.microsoft.com/en-us/rest/api/cognitiveservices-bingsearch/bing-spell-check-api-v7-reference#market-codes
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: b6e03b67-8c6c-2749-7778-99f7dca069c6
* Version Independent ID: a6ee8911-2630-d6c4-81c7-28a5fdf4b767
* Content: [Language support - Bing Spell Check API - Azure Cognitive Services](https://docs.microsoft.com/en-us/azure/cognitive-services/bing-spell-check/language-support)
* Content Source: [articles/cognitive-services/Bing-Spell-Check/language-support.md](https://github.com/Microsoft/azure-docs/blob/master/articles/cognitive-services/Bing-Spell-Check/language-support.md)
* Service: **cognitive-services**
* Sub-service: **bing-spell-check**
* GitHub Login: @aahill
* Microsoft Alias: **aahi** | non_priority | supported locales what is the actual supported mkt list for bing spell checker the list on this page is different from document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service cognitive services sub service bing spell check github login aahill microsoft alias aahi | 0 |
13,321 | 22,628,349,825 | IssuesEvent | 2022-06-30 12:44:25 | AAFC-BICoE/dina-planning | https://api.github.com/repos/AAFC-BICoE/dina-planning | closed | Display Collection Number instead of the unique DB identifier in Collecting Event view | type: requirement | We've talked about this before but I just wanted to record it as the change hasn't been made yet.
Can we have the collection number displayed in big? And like we said before remove the DB generated unique number (or at least make it smaller?). It doesn't mean anything to us and really isn't helpful.
In the tab we would see the collection number also instead of the generated number.
| 1.0 | Display Collection Number instead of the unique DB identifier in Collecting Event view - We've talked about this before but I just wanted to record it as the change hasn't been made yet.
Can we have the collection number displayed in big? And like we said before remove the DB generated unique number (or at least make it smaller?). It doesn't mean anything to us and really isn't helpful.
In the tab we would see the collection number also instead of the generated number.
| non_priority | display collection number instead of the unique db identifier in collecting event view we ve talked about this before but i just wanted to record it as the change hasn t been made yet can we have the collection number displayed in big and like we said before remove the db generated unique number or at least make it smaller it doesn t mean anything to us and really isn t helpful in the tab we would see the collection number also instead of the generated number | 0 |
75 | 2,537,341,996 | IssuesEvent | 2015-01-26 19:55:17 | CloudCycle2/YAML_Transformer | https://api.github.com/repos/CloudCycle2/YAML_Transformer | opened | Console interface | p:normal s:new t:requirement | A console interface is needed to use our transformer as a standalone program.
It should take an argument of a YAML file and returns complete XML. User should be able to provide inputs which are required in the YAML document or he should be able to tell the program to use default values for the inputs.
Time: 24.02. to 03.03.
Assignees: Not known yet | 1.0 | Console interface - A console interface is needed to use our transformer as a standalone program.
It should take an argument of a YAML file and returns complete XML. User should be able to provide inputs which are required in the YAML document or he should be able to tell the program to use default values for the inputs.
Time: 24.02. to 03.03.
Assignees: Not known yet | non_priority | console interface a console interface is needed to use our transformer as a standalone program it should take an argument of a yaml file and returns complete xml user should be able to provide inputs which are required in the yaml document or he should be able to tell the program to use default values for the inputs time to assignees not known yet | 0 |
291,979 | 21,945,249,572 | IssuesEvent | 2022-05-23 23:18:56 | druxt/druxt.js | https://api.github.com/repos/druxt/druxt.js | closed | Add search to documentation | documentation enhancement | **Is your feature request related to a problem? Please describe.**
As a user I want the ability to search through the guide and API documentation
**Describe the solution you'd like**
- [ ] Decide on search provider
- [ ] Add search to documentation site
**Describe alternatives you've considered**
N/A
**Additional context**
- The current Umami demo uses the Lunr via the Drupal Search api: https://github.com/druxt/demo.druxtjs.org/blob/develop/modules/search-api-lunr.js
| 1.0 | Add search to documentation - **Is your feature request related to a problem? Please describe.**
As a user I want the ability to search through the guide and API documentation
**Describe the solution you'd like**
- [ ] Decide on search provider
- [ ] Add search to documentation site
**Describe alternatives you've considered**
N/A
**Additional context**
- The current Umami demo uses the Lunr via the Drupal Search api: https://github.com/druxt/demo.druxtjs.org/blob/develop/modules/search-api-lunr.js
| non_priority | add search to documentation is your feature request related to a problem please describe as a user i want the ability to search through the guide and api documentation describe the solution you d like decide on search provider add search to documentation site describe alternatives you ve considered n a additional context the current umami demo uses the lunr via the drupal search api | 0 |
76,265 | 14,592,413,965 | IssuesEvent | 2020-12-19 17:31:01 | eeeeaaii/vodka | https://api.github.com/repos/eeeeaaii/vodka | closed | code cleanup for EString and EError | code cleanup | EString and EError implemented an old-style "editor flow" that predated me creating the editor class. The code is pretty messy and there is dead code in there. These two classes need to be overhauled and the editing functionality needs to be moved over into a subclass of Editor. | 1.0 | code cleanup for EString and EError - EString and EError implemented an old-style "editor flow" that predated me creating the editor class. The code is pretty messy and there is dead code in there. These two classes need to be overhauled and the editing functionality needs to be moved over into a subclass of Editor. | non_priority | code cleanup for estring and eerror estring and eerror implemented an old style editor flow that predated me creating the editor class the code is pretty messy and there is dead code in there these two classes need to be overhauled and the editing functionality needs to be moved over into a subclass of editor | 0 |
170,850 | 27,021,570,209 | IssuesEvent | 2023-02-11 03:47:11 | mapasculturais/mapasculturais | https://api.github.com/repos/mapasculturais/mapasculturais | closed | URL pra compartilhar as singles | Melhoria Design / UX | ali na área de compartilhar as entidades onde temos os famigerados 3 botões sociais, podia ter a url bonitinha embaixo (tipo na parte de compartilhar os resultados da busca) | 1.0 | URL pra compartilhar as singles - ali na área de compartilhar as entidades onde temos os famigerados 3 botões sociais, podia ter a url bonitinha embaixo (tipo na parte de compartilhar os resultados da busca) | non_priority | url pra compartilhar as singles ali na área de compartilhar as entidades onde temos os famigerados botões sociais podia ter a url bonitinha embaixo tipo na parte de compartilhar os resultados da busca | 0 |
149,769 | 19,587,369,440 | IssuesEvent | 2022-01-05 08:51:35 | elastic/kibana | https://api.github.com/repos/elastic/kibana | closed | [Security Solution] Exception is imported even without click on "Overwrite existing exception lists" when import the rule with exception | bug triage_needed medium v8.0.0 Team: SecuritySolution | **Describe the bug**
Exception is imported even without click on "Overwrite existing exception lists" when import the rule with exception
**Build Details:**
```
Version: 8.0.0-SNAPSHOT
Commit: bacb608a62bbea2b732c5e704c450a1b40c66bc1
Build:48889
```
**Browser Details:**
N/A
**Preconditions**
1. Kibana should be running on 8.0.0 snapshot
2. Rule should be created with exception
**Steps to Reproduce**
1. Export the above created rule
2. Delete the exported rule and import the same
3. While import the rule do not select the "Overwrite existing exception lists"
4. Observe that error is displayed for exception which is expected.
5. Navigate to rule details page of exported rule.
6. Observe that exception is also imported and assign to old endpoint list id under exceptions tab
**Actual Result**
Exception is imported even without click on "Overwrite existing exception lists" when import the rule with exception
**Expected Result**
Exception should not be imported if not click on "Overwrite existing exception lists" when import the rule with exception
**What's Working**
- N/A
**What's Not Working**
- N/A
**Screen-Shot**
https://user-images.githubusercontent.com/61860752/148021425-7c4ba81c-2603-4c6d-85b7-c7a3e61cac61.mp4
| True | [Security Solution] Exception is imported even without click on "Overwrite existing exception lists" when import the rule with exception - **Describe the bug**
Exception is imported even without click on "Overwrite existing exception lists" when import the rule with exception
**Build Details:**
```
Version: 8.0.0-SNAPSHOT
Commit: bacb608a62bbea2b732c5e704c450a1b40c66bc1
Build:48889
```
**Browser Details:**
N/A
**Preconditions**
1. Kibana should be running on 8.0.0 snapshot
2. Rule should be created with exception
**Steps to Reproduce**
1. Export the above created rule
2. Delete the exported rule and import the same
3. While import the rule do not select the "Overwrite existing exception lists"
4. Observe that error is displayed for exception which is expected.
5. Navigate to rule details page of exported rule.
6. Observe that exception is also imported and assign to old endpoint list id under exceptions tab
**Actual Result**
Exception is imported even without click on "Overwrite existing exception lists" when import the rule with exception
**Expected Result**
Exception should not be imported if not click on "Overwrite existing exception lists" when import the rule with exception
**What's Working**
- N/A
**What's Not Working**
- N/A
**Screen-Shot**
https://user-images.githubusercontent.com/61860752/148021425-7c4ba81c-2603-4c6d-85b7-c7a3e61cac61.mp4
| non_priority | exception is imported even without click on overwrite existing exception lists when import the rule with exception describe the bug exception is imported even without click on overwrite existing exception lists when import the rule with exception build details version snapshot commit build browser details n a preconditions kibana should be running on snapshot rule should be created with exception steps to reproduce export the above created rule delete the exported rule and import the same while import the rule do not select the overwrite existing exception lists observe that error is displayed for exception which is expected navigate to rule details page of exported rule observe that exception is also imported and assign to old endpoint list id under exceptions tab actual result exception is imported even without click on overwrite existing exception lists when import the rule with exception expected result exception should not be imported if not click on overwrite existing exception lists when import the rule with exception what s working n a what s not working n a screen shot | 0 |
33,579 | 12,216,755,223 | IssuesEvent | 2020-05-01 15:47:10 | dhlinh98/juice-shop | https://api.github.com/repos/dhlinh98/juice-shop | opened | CVE-2019-20388 (High) detected in reactos-0.4.13-dev | security vulnerability | ## CVE-2019-20388 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>reactos0.4.13-dev</b></p></summary>
<p>
<p>A free Windows-compatible Operating System</p>
<p>Library home page: <a href=https://github.com/reactos/reactos.git>https://github.com/reactos/reactos.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/dhlinh98/juice-shop/commit/15b744adda384be966bd6bcc52d9830c8bab440a">15b744adda384be966bd6bcc52d9830c8bab440a</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Library Source Files (29)</summary>
<p></p>
<p> * The source files were matched to this source library based on a best effort match. Source libraries are selected from a list of probable public libraries.</p>
<p>
- /juice-shop/node_modules/libxmljs2/vendor/libxml/schematron.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xpointer.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xmlreader.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/include/libxml/tree.h
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xmlsave.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/SAX2.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/include/libxml/globals.h
- /juice-shop/node_modules/libxmljs2/vendor/libxml/parserInternals.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xinclude.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/HTMLtree.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/HTMLparser.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xmlstring.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/relaxng.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/c14n.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xmllint.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/encoding.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/include/libxml/xmlexports.h
- /juice-shop/node_modules/libxmljs2/vendor/libxml/entities.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xmlmodule.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xmlcatalog.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xmlschemas.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/uri.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/catalog.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xmlregexp.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xlink.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xmlschemastypes.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xzlib.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/parser.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/debugXML.c
</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>
xmlSchemaPreRun in xmlschemas.c in libxml2 2.9.10 allows an xmlSchemaValidateStream memory leak.
<p>Publish Date: 2020-01-21
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20388>CVE-2019-20388</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>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2019-20388 (High) detected in reactos-0.4.13-dev - ## CVE-2019-20388 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>reactos0.4.13-dev</b></p></summary>
<p>
<p>A free Windows-compatible Operating System</p>
<p>Library home page: <a href=https://github.com/reactos/reactos.git>https://github.com/reactos/reactos.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/dhlinh98/juice-shop/commit/15b744adda384be966bd6bcc52d9830c8bab440a">15b744adda384be966bd6bcc52d9830c8bab440a</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Library Source Files (29)</summary>
<p></p>
<p> * The source files were matched to this source library based on a best effort match. Source libraries are selected from a list of probable public libraries.</p>
<p>
- /juice-shop/node_modules/libxmljs2/vendor/libxml/schematron.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xpointer.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xmlreader.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/include/libxml/tree.h
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xmlsave.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/SAX2.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/include/libxml/globals.h
- /juice-shop/node_modules/libxmljs2/vendor/libxml/parserInternals.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xinclude.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/HTMLtree.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/HTMLparser.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xmlstring.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/relaxng.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/c14n.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xmllint.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/encoding.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/include/libxml/xmlexports.h
- /juice-shop/node_modules/libxmljs2/vendor/libxml/entities.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xmlmodule.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xmlcatalog.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xmlschemas.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/uri.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/catalog.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xmlregexp.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xlink.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xmlschemastypes.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/xzlib.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/parser.c
- /juice-shop/node_modules/libxmljs2/vendor/libxml/debugXML.c
</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>
xmlSchemaPreRun in xmlschemas.c in libxml2 2.9.10 allows an xmlSchemaValidateStream memory leak.
<p>Publish Date: 2020-01-21
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20388>CVE-2019-20388</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>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in reactos dev cve high severity vulnerability vulnerable library dev a free windows compatible operating system library home page a href found in head commit a href library source files the source files were matched to this source library based on a best effort match source libraries are selected from a list of probable public libraries juice shop node modules vendor libxml schematron c juice shop node modules vendor libxml xpointer c juice shop node modules vendor libxml xmlreader c juice shop node modules vendor libxml include libxml tree h juice shop node modules vendor libxml xmlsave c juice shop node modules vendor libxml c juice shop node modules vendor libxml include libxml globals h juice shop node modules vendor libxml parserinternals c juice shop node modules vendor libxml xinclude c juice shop node modules vendor libxml htmltree c juice shop node modules vendor libxml htmlparser c juice shop node modules vendor libxml xmlstring c juice shop node modules vendor libxml relaxng c juice shop node modules vendor libxml c juice shop node modules vendor libxml xmllint c juice shop node modules vendor libxml encoding c juice shop node modules vendor libxml include libxml xmlexports h juice shop node modules vendor libxml entities c juice shop node modules vendor libxml xmlmodule c juice shop node modules vendor libxml xmlcatalog c juice shop node modules vendor libxml xmlschemas c juice shop node modules vendor libxml uri c juice shop node modules vendor libxml catalog c juice shop node modules vendor libxml xmlregexp c juice shop node modules vendor libxml xlink c juice shop node modules vendor libxml xmlschemastypes c juice shop node modules vendor libxml xzlib c juice shop node modules vendor libxml parser c juice shop node modules vendor libxml debugxml c vulnerability details xmlschemaprerun in xmlschemas c in allows an xmlschemavalidatestream memory leak 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 step up your open source security game with whitesource | 0 |
146,637 | 13,187,370,501 | IssuesEvent | 2020-08-13 03:11:56 | icecube-trac/tix3 | https://api.github.com/repos/icecube-trac/tix3 | closed | Doxygen docs generation is broken (Trac #282) | Migrated from Trac documentation enhancement | The way we use doxygen to generate documentation is just "good enough".
Each project's documentation is generated separately, independent of its peer projects in a meta-project. This prevents cross-linking of 'objects' from other projects. For instance, I3Units::m can't be cross referenced in phys-services, because the I3Units namespace is defined in icetray.
This can probably be fixed by using CMake to generate a "doxygen hierarchy" which "make docs" will act on. This should then give the user a complete, cross-referenced set of documentation within their build space.
This will be very important when we move to [http://sphinx.pocoo.org/ sphinx] + [http://michaeljones.github.com/breathe/ breathe] as they're very dependent on doxygen's xml output.
<details>
<summary>_Migrated from https://code.icecube.wisc.edu/ticket/282
, reported by nega and owned by nega_</summary>
<p>
```json
{
"status": "closed",
"changetime": "2015-04-17T00:06:57",
"description": "The way we use doxygen to generate documentation is just \"good enough\".\n\nEach project's documentation is generated separately, independent of its peer projects in a meta-project. This prevents cross-linking of 'objects' from other projects. For instance, I3Units::m can't be cross referenced in phys-services, because the I3Units namespace is defined in icetray.\n\nThis can probably be fixed by using CMake to generate a \"doxygen hierarchy\" which \"make docs\" will act on. This should then give the user a complete, cross-referenced set of documentation within their build space.\n\nThis will be very important when we move to [http://sphinx.pocoo.org/ sphinx] + [http://michaeljones.github.com/breathe/ breathe] as they're very dependent on doxygen's xml output.",
"reporter": "nega",
"cc": "",
"resolution": "fixed",
"_ts": "1429229217989600",
"component": "documentation",
"summary": "Doxygen docs generation is broken",
"priority": "normal",
"keywords": "doxygen cmake",
"time": "2011-06-13T03:41:59",
"milestone": "",
"owner": "nega",
"type": "enhancement"
}
```
</p>
</details>
| 1.0 | Doxygen docs generation is broken (Trac #282) - The way we use doxygen to generate documentation is just "good enough".
Each project's documentation is generated separately, independent of its peer projects in a meta-project. This prevents cross-linking of 'objects' from other projects. For instance, I3Units::m can't be cross referenced in phys-services, because the I3Units namespace is defined in icetray.
This can probably be fixed by using CMake to generate a "doxygen hierarchy" which "make docs" will act on. This should then give the user a complete, cross-referenced set of documentation within their build space.
This will be very important when we move to [http://sphinx.pocoo.org/ sphinx] + [http://michaeljones.github.com/breathe/ breathe] as they're very dependent on doxygen's xml output.
<details>
<summary>_Migrated from https://code.icecube.wisc.edu/ticket/282
, reported by nega and owned by nega_</summary>
<p>
```json
{
"status": "closed",
"changetime": "2015-04-17T00:06:57",
"description": "The way we use doxygen to generate documentation is just \"good enough\".\n\nEach project's documentation is generated separately, independent of its peer projects in a meta-project. This prevents cross-linking of 'objects' from other projects. For instance, I3Units::m can't be cross referenced in phys-services, because the I3Units namespace is defined in icetray.\n\nThis can probably be fixed by using CMake to generate a \"doxygen hierarchy\" which \"make docs\" will act on. This should then give the user a complete, cross-referenced set of documentation within their build space.\n\nThis will be very important when we move to [http://sphinx.pocoo.org/ sphinx] + [http://michaeljones.github.com/breathe/ breathe] as they're very dependent on doxygen's xml output.",
"reporter": "nega",
"cc": "",
"resolution": "fixed",
"_ts": "1429229217989600",
"component": "documentation",
"summary": "Doxygen docs generation is broken",
"priority": "normal",
"keywords": "doxygen cmake",
"time": "2011-06-13T03:41:59",
"milestone": "",
"owner": "nega",
"type": "enhancement"
}
```
</p>
</details>
| non_priority | doxygen docs generation is broken trac the way we use doxygen to generate documentation is just good enough each project s documentation is generated separately independent of its peer projects in a meta project this prevents cross linking of objects from other projects for instance m can t be cross referenced in phys services because the namespace is defined in icetray this can probably be fixed by using cmake to generate a doxygen hierarchy which make docs will act on this should then give the user a complete cross referenced set of documentation within their build space this will be very important when we move to as they re very dependent on doxygen s xml output migrated from reported by nega and owned by nega json status closed changetime description the way we use doxygen to generate documentation is just good enough n neach project s documentation is generated separately independent of its peer projects in a meta project this prevents cross linking of objects from other projects for instance m can t be cross referenced in phys services because the namespace is defined in icetray n nthis can probably be fixed by using cmake to generate a doxygen hierarchy which make docs will act on this should then give the user a complete cross referenced set of documentation within their build space n nthis will be very important when we move to as they re very dependent on doxygen s xml output reporter nega cc resolution fixed ts component documentation summary doxygen docs generation is broken priority normal keywords doxygen cmake time milestone owner nega type enhancement | 0 |
343,260 | 24,766,317,590 | IssuesEvent | 2022-10-22 15:16:38 | PEC-CSS/Hacktoberfest-Leaderboard | https://api.github.com/repos/PEC-CSS/Hacktoberfest-Leaderboard | closed | Update the README | documentation good first issue hacktoberfest | Update the README according to the format used in other PEC-CSS repositories | 1.0 | Update the README - Update the README according to the format used in other PEC-CSS repositories | non_priority | update the readme update the readme according to the format used in other pec css repositories | 0 |
398,974 | 27,219,183,931 | IssuesEvent | 2023-02-21 02:41:42 | higress-group/higress-console | https://api.github.com/repos/higress-group/higress-console | opened | 请求协议转换支持：HTTP → Dubbo | documentation enhancement frontend level/normal backend | ## Why do you need it?
Higress 已经支持将 HTTP 请求转换为 Dubbo 请求转发给后端的 Dubbo 服务。故 Higress Console 需要支持配置此类路由。
## How could it be?
Higress 中的 Dubbo 协议转换功能参见文档：https://higress.io/zh-cn/docs/user/dubbo.html
这里需要支持用户配置路由目标和转换规则。
## Other related information
子任务列表：
- 后端数据模型、接口的设计与实现
- 前端页面设计与实现 | 1.0 | 请求协议转换支持：HTTP → Dubbo - ## Why do you need it?
Higress 已经支持将 HTTP 请求转换为 Dubbo 请求转发给后端的 Dubbo 服务。故 Higress Console 需要支持配置此类路由。
## How could it be?
Higress 中的 Dubbo 协议转换功能参见文档：https://higress.io/zh-cn/docs/user/dubbo.html
这里需要支持用户配置路由目标和转换规则。
## Other related information
子任务列表：
- 后端数据模型、接口的设计与实现
- 前端页面设计与实现 | non_priority | 请求协议转换支持：http → dubbo why do you need it higress 已经支持将 http 请求转换为 dubbo 请求转发给后端的 dubbo 服务。故 higress console 需要支持配置此类路由。 how could it be higress 中的 dubbo 协议转换功能参见文档： 这里需要支持用户配置路由目标和转换规则。 other related information 子任务列表： 后端数据模型、接口的设计与实现 前端页面设计与实现 | 0 |
2,998 | 10,963,394,490 | IssuesEvent | 2019-11-27 19:34:43 | pace/bricks | https://api.github.com/repos/pace/bricks | closed | Monitoring of go pg connection pool | S::Ready T::Maintainance | ### Problem
Postgres connections are expensive, having many causes issues. One can deploy pgbouncer/pgpool to defer the issue, but understanding the connections caused by the application remains an important issue.
### Solution
Having a go-routine that checks the pg pool stats and exposes them via metrics.
See https://github.com/go-pg/pg/blob/master/internal/pool/pool.go#L26
### Tasks
* [ ] Document the new metrics
* [ ] Expose all of the available metrics
* [ ] Implement watcher | True | Monitoring of go pg connection pool - ### Problem
Postgres connections are expensive, having many causes issues. One can deploy pgbouncer/pgpool to defer the issue, but understanding the connections caused by the application remains an important issue.
### Solution
Having a go-routine that checks the pg pool stats and exposes them via metrics.
See https://github.com/go-pg/pg/blob/master/internal/pool/pool.go#L26
### Tasks
* [ ] Document the new metrics
* [ ] Expose all of the available metrics
* [ ] Implement watcher | non_priority | monitoring of go pg connection pool problem postgres connections are expensive having many causes issues one can deploy pgbouncer pgpool to defer the issue but understanding the connections caused by the application remains an important issue solution having a go routine that checks the pg pool stats and exposes them via metrics see tasks document the new metrics expose all of the available metrics implement watcher | 0 |
168,049 | 14,137,618,932 | IssuesEvent | 2020-11-10 06:59:54 | Puffycheeses/iidx-lambda | https://api.github.com/repos/Puffycheeses/iidx-lambda | closed | Add a README | documentation | This readme should do the following
- Explain the goals of the project
- Explain the project layout
- Explain contributing guidelines | 1.0 | Add a README - This readme should do the following
- Explain the goals of the project
- Explain the project layout
- Explain contributing guidelines | non_priority | add a readme this readme should do the following explain the goals of the project explain the project layout explain contributing guidelines | 0 |
89,553 | 8,205,744,316 | IssuesEvent | 2018-09-03 11:10:26 | humera987/HumTestData | https://api.github.com/repos/humera987/HumTestData | closed | humz_proj_test : ApiV1IssueTrackersGetQueryParamEmptyValuePage | humz_proj_test | Project : humz_proj_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=[Mon, 03 Sep 2018 06:22:23 GMT]}
Endpoint : http://13.56.210.25/api/v1/issue-trackers?page=
Request :
Response :
{
"requestId" : "None",
"requestTime" : "2018-09-03T06:22:24.181+0000",
"errors" : false,
"messages" : [ ],
"data" : [ ],
"totalPages" : 0,
"totalElements" : 0
}
Logs :
Assertion [@StatusCode != 404] passed, not expecting [404] and found [200]Assertion [@StatusCode != 500] passed, not expecting [500] and found [200]Assertion [@StatusCode != 200] failed, not expecting [200] but found [200]Assertion [@StatusCode != 401] passed, not expecting [401] and found [200]
--- FX Bot --- | 1.0 | humz_proj_test : ApiV1IssueTrackersGetQueryParamEmptyValuePage - Project : humz_proj_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=[Mon, 03 Sep 2018 06:22:23 GMT]}
Endpoint : http://13.56.210.25/api/v1/issue-trackers?page=
Request :
Response :
{
"requestId" : "None",
"requestTime" : "2018-09-03T06:22:24.181+0000",
"errors" : false,
"messages" : [ ],
"data" : [ ],
"totalPages" : 0,
"totalElements" : 0
}
Logs :
Assertion [@StatusCode != 404] passed, not expecting [404] and found [200]Assertion [@StatusCode != 500] passed, not expecting [500] and found [200]Assertion [@StatusCode != 200] failed, not expecting [200] but found [200]Assertion [@StatusCode != 401] passed, not expecting [401] and found [200]
--- FX Bot --- | non_priority | humz proj test project humz proj 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 totalpages totalelements logs assertion passed not expecting and found assertion passed not expecting and found assertion failed not expecting but found assertion passed not expecting and found fx bot | 0 |
34,464 | 14,405,648,139 | IssuesEvent | 2020-12-03 19:01:26 | MicrosoftDocs/azure-docs | https://api.github.com/repos/MicrosoftDocs/azure-docs | closed | Inline script is missing an option if you want the workflow to succeed | Pri1 container-service/svc cxp doc-bug triaged | in the YAML file, the az command provided to upgrade os node image will ask a confirmation for the upgrade that will stop Github workflow waiting for an answer
instead of :
```
inlineScript: |
az aks upgrade -g ${{ secrets.RESOURCE_GROUP_NAME }} -n ${{ secrets.AKS_CLUSTER_NAME }} --node-image-only
```
you should you the same command with --yes at the end
```
inlineScript: |
az aks upgrade -g ${{ secrets.RESOURCE_GROUP_NAME }} -n ${{ secrets.AKS_CLUSTER_NAME }} --node-image-only --yes
```
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 9659eab1-b7f7-d163-ff0a-577b7496b5c8
* Version Independent ID: 0892de76-78f8-4c1c-c09c-60af3f275320
* Content: [Handle AKS node upgrades with GitHub Actions - Azure Kubernetes Service](https://docs.microsoft.com/en-us/azure/aks/node-upgrade-github-actions)
* Content Source: [articles/aks/node-upgrade-github-actions.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/aks/node-upgrade-github-actions.md)
* Service: **container-service**
* GitHub Login: @mlearned
* Microsoft Alias: **mlearned** | 1.0 | Inline script is missing an option if you want the workflow to succeed - in the YAML file, the az command provided to upgrade os node image will ask a confirmation for the upgrade that will stop Github workflow waiting for an answer
instead of :
```
inlineScript: |
az aks upgrade -g ${{ secrets.RESOURCE_GROUP_NAME }} -n ${{ secrets.AKS_CLUSTER_NAME }} --node-image-only
```
you should you the same command with --yes at the end
```
inlineScript: |
az aks upgrade -g ${{ secrets.RESOURCE_GROUP_NAME }} -n ${{ secrets.AKS_CLUSTER_NAME }} --node-image-only --yes
```
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 9659eab1-b7f7-d163-ff0a-577b7496b5c8
* Version Independent ID: 0892de76-78f8-4c1c-c09c-60af3f275320
* Content: [Handle AKS node upgrades with GitHub Actions - Azure Kubernetes Service](https://docs.microsoft.com/en-us/azure/aks/node-upgrade-github-actions)
* Content Source: [articles/aks/node-upgrade-github-actions.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/aks/node-upgrade-github-actions.md)
* Service: **container-service**
* GitHub Login: @mlearned
* Microsoft Alias: **mlearned** | non_priority | inline script is missing an option if you want the workflow to succeed in the yaml file the az command provided to upgrade os node image will ask a confirmation for the upgrade that will stop github workflow waiting for an answer instead of inlinescript az aks upgrade g secrets resource group name n secrets aks cluster name node image only you should you the same command with yes at the end inlinescript az aks upgrade g secrets resource group name n secrets aks cluster name node image only yes document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service container service github login mlearned microsoft alias mlearned | 0 |
38,728 | 19,527,708,837 | IssuesEvent | 2021-12-30 11:00:44 | LMAX-Exchange/disruptor | https://api.github.com/repos/LMAX-Exchange/disruptor | closed | Increased CPU Time caused by TimeoutBlockingWaitStrategy | performance | Hello, I have been using disruptor (3.3.x) with log4j (2.6) in my project.
Recently, I have upgraded to log4j 2.14 and disruptor 3.4.2. I am using default values.
After the upgrade, I have profiled my CPU cycles and found out that:
TimeoutBlockingWaitStrategy.waitFor() jumped from %0.1 to ~%8, roughly 80 times slower.
My best guess is, this is caused by the following commit:
https://github.com/LMAX-Exchange/disruptor/commit/a18f8198ab94590f0a5ec7c3378ba87f997ea670#diff-06ba76f327d4242a110faf85be993d61f45b9e1df4364fb193330980970423ad
Any suggestions or workaround to tackle this problem ?
Thanks a lot | True | Increased CPU Time caused by TimeoutBlockingWaitStrategy - Hello, I have been using disruptor (3.3.x) with log4j (2.6) in my project.
Recently, I have upgraded to log4j 2.14 and disruptor 3.4.2. I am using default values.
After the upgrade, I have profiled my CPU cycles and found out that:
TimeoutBlockingWaitStrategy.waitFor() jumped from %0.1 to ~%8, roughly 80 times slower.
My best guess is, this is caused by the following commit:
https://github.com/LMAX-Exchange/disruptor/commit/a18f8198ab94590f0a5ec7c3378ba87f997ea670#diff-06ba76f327d4242a110faf85be993d61f45b9e1df4364fb193330980970423ad
Any suggestions or workaround to tackle this problem ?
Thanks a lot | non_priority | increased cpu time caused by timeoutblockingwaitstrategy hello i have been using disruptor x with in my project recently i have upgraded to and disruptor i am using default values after the upgrade i have profiled my cpu cycles and found out that timeoutblockingwaitstrategy waitfor jumped from to roughly times slower my best guess is this is caused by the following commit any suggestions or workaround to tackle this problem thanks a lot | 0 |
48,342 | 5,954,251,372 | IssuesEvent | 2017-05-27 16:04:46 | Bars92/font-organizer | https://api.github.com/repos/Bars92/font-organizer | closed | Testing Version 2.1.0 | testing | ## Regression Checklist:
- [x] General Settings options saving and working.
- [ ] Upload fonts:
- [ ] Upload all supported formats.
- [ ] Upload more than 1 file.
- [ ] Upload non-normal font weight.
- [ ] Upload to an existing font name.
- [x] Available fonts:
- [x] List does not contain an used font.
- [x] Adding an available font is added to used fonts.
- [x] List is sorted.
- [x] Known Elements:
- [x] Known element is saving and working properly.
- [x] Known element are using the correct font weight.
- [x] Known element working as expected with 'Not Stated' font weight.
- [x] Custom Elements:
- [x] Custom elements is saving and working properly.
- [x] Custom elements is using the font weight.
- [x] Manage fonts:
- [x] Selecting a font displays all the correct information (urls, name, custom elements)
- [x] Delete font (Google & custom) delete the font from the database (usable font) and the file.
- [x] Editing custom elements in manage fonts is working as expected for all the fields.
- [x] Preview is displaying the font and text preview when selecting font and text.
- [x] All plugin links are working and redirecting to the desired address.
- [ ] Updating the plugin does update the necessary tables and working.
- [ ] Plugin readme.txt is set to the newest version and updated. | 1.0 | Testing Version 2.1.0 - ## Regression Checklist:
- [x] General Settings options saving and working.
- [ ] Upload fonts:
- [ ] Upload all supported formats.
- [ ] Upload more than 1 file.
- [ ] Upload non-normal font weight.
- [ ] Upload to an existing font name.
- [x] Available fonts:
- [x] List does not contain an used font.
- [x] Adding an available font is added to used fonts.
- [x] List is sorted.
- [x] Known Elements:
- [x] Known element is saving and working properly.
- [x] Known element are using the correct font weight.
- [x] Known element working as expected with 'Not Stated' font weight.
- [x] Custom Elements:
- [x] Custom elements is saving and working properly.
- [x] Custom elements is using the font weight.
- [x] Manage fonts:
- [x] Selecting a font displays all the correct information (urls, name, custom elements)
- [x] Delete font (Google & custom) delete the font from the database (usable font) and the file.
- [x] Editing custom elements in manage fonts is working as expected for all the fields.
- [x] Preview is displaying the font and text preview when selecting font and text.
- [x] All plugin links are working and redirecting to the desired address.
- [ ] Updating the plugin does update the necessary tables and working.
- [ ] Plugin readme.txt is set to the newest version and updated. | non_priority | testing version regression checklist general settings options saving and working upload fonts upload all supported formats upload more than file upload non normal font weight upload to an existing font name available fonts list does not contain an used font adding an available font is added to used fonts list is sorted known elements known element is saving and working properly known element are using the correct font weight known element working as expected with not stated font weight custom elements custom elements is saving and working properly custom elements is using the font weight manage fonts selecting a font displays all the correct information urls name custom elements delete font google custom delete the font from the database usable font and the file editing custom elements in manage fonts is working as expected for all the fields preview is displaying the font and text preview when selecting font and text all plugin links are working and redirecting to the desired address updating the plugin does update the necessary tables and working plugin readme txt is set to the newest version and updated | 0 |
89,882 | 8,216,653,088 | IssuesEvent | 2018-09-05 09:50:23 | humera987/HumTestData | https://api.github.com/repos/humera987/HumTestData | opened | project_test : api_v1_test-suites_search_keyword_get_auth_invalid | project_test | Project : project_test
Job : UAT
Env : UAT
Region : FXLabs/US_WEST_1
Result : fail
Status Code : 500
Headers : {}
Endpoint : http://13.56.210.25/api/v1/test-suites/search/{keyword}
Request :
Response :
Not enough variable values available to expand 'keyword'
Logs :
Assertion [@StatusCode == 401] failed, expected value [401] but found [500]
--- FX Bot --- | 1.0 | project_test : api_v1_test-suites_search_keyword_get_auth_invalid - Project : project_test
Job : UAT
Env : UAT
Region : FXLabs/US_WEST_1
Result : fail
Status Code : 500
Headers : {}
Endpoint : http://13.56.210.25/api/v1/test-suites/search/{keyword}
Request :
Response :
Not enough variable values available to expand 'keyword'
Logs :
Assertion [@StatusCode == 401] failed, expected value [401] but found [500]
--- FX Bot --- | non_priority | project test api test suites search keyword get auth invalid project project test job uat env uat region fxlabs us west result fail status code headers endpoint request response not enough variable values available to expand keyword logs assertion failed expected value but found fx bot | 0 |
263,699 | 28,048,142,086 | IssuesEvent | 2023-03-29 01:54:59 | L00171222/juice-shop | https://api.github.com/repos/L00171222/juice-shop | closed | check-dependencies-1.1.0.tgz: 1 vulnerabilities (highest severity is: 9.8) - autoclosed | Mend: dependency security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>check-dependencies-1.1.0.tgz</b></p></summary>
<p></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/set-value/package.json</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/L00171222/juice-shop/commit/375e5e831d83bd4fb00d2e72c038f31d4bc44e52">375e5e831d83bd4fb00d2e72c038f31d4bc44e52</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (check-dependencies version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2021-23440](https://www.mend.io/vulnerability-database/CVE-2021-23440) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | set-value-2.0.1.tgz | 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/high_vul.png' width=19 height=20> CVE-2021-23440</summary>
### Vulnerable Library - <b>set-value-2.0.1.tgz</b></p>
<p>Create nested values and any intermediaries using dot notation (`'a.b.c'`) paths.</p>
<p>Library home page: <a href="https://registry.npmjs.org/set-value/-/set-value-2.0.1.tgz">https://registry.npmjs.org/set-value/-/set-value-2.0.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/set-value/package.json</p>
<p>
Dependency Hierarchy:
- check-dependencies-1.1.0.tgz (Root Library)
- findup-sync-2.0.0.tgz
- micromatch-3.1.10.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- cache-base-1.0.1.tgz
- :x: **set-value-2.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/L00171222/juice-shop/commit/375e5e831d83bd4fb00d2e72c038f31d4bc44e52">375e5e831d83bd4fb00d2e72c038f31d4bc44e52</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
This affects the package set-value before <2.0.1, >=3.0.0 <4.0.1. A type confusion vulnerability can lead to a bypass of CVE-2019-10747 when the user-provided keys used in the path parameter are arrays.
Mend Note: After conducting further research, Mend has determined that all versions of set-value up to version 4.0.0 are vulnerable to CVE-2021-23440.
<p>Publish Date: 2021-09-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23440>CVE-2021-23440</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2021-09-12</p>
<p>Fix Resolution: set-value - 4.0.1
</p>
</p>
<p></p>
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details> | True | check-dependencies-1.1.0.tgz: 1 vulnerabilities (highest severity is: 9.8) - autoclosed - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>check-dependencies-1.1.0.tgz</b></p></summary>
<p></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/set-value/package.json</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/L00171222/juice-shop/commit/375e5e831d83bd4fb00d2e72c038f31d4bc44e52">375e5e831d83bd4fb00d2e72c038f31d4bc44e52</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (check-dependencies version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2021-23440](https://www.mend.io/vulnerability-database/CVE-2021-23440) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | set-value-2.0.1.tgz | 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/high_vul.png' width=19 height=20> CVE-2021-23440</summary>
### Vulnerable Library - <b>set-value-2.0.1.tgz</b></p>
<p>Create nested values and any intermediaries using dot notation (`'a.b.c'`) paths.</p>
<p>Library home page: <a href="https://registry.npmjs.org/set-value/-/set-value-2.0.1.tgz">https://registry.npmjs.org/set-value/-/set-value-2.0.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/set-value/package.json</p>
<p>
Dependency Hierarchy:
- check-dependencies-1.1.0.tgz (Root Library)
- findup-sync-2.0.0.tgz
- micromatch-3.1.10.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- cache-base-1.0.1.tgz
- :x: **set-value-2.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/L00171222/juice-shop/commit/375e5e831d83bd4fb00d2e72c038f31d4bc44e52">375e5e831d83bd4fb00d2e72c038f31d4bc44e52</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
This affects the package set-value before <2.0.1, >=3.0.0 <4.0.1. A type confusion vulnerability can lead to a bypass of CVE-2019-10747 when the user-provided keys used in the path parameter are arrays.
Mend Note: After conducting further research, Mend has determined that all versions of set-value up to version 4.0.0 are vulnerable to CVE-2021-23440.
<p>Publish Date: 2021-09-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23440>CVE-2021-23440</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2021-09-12</p>
<p>Fix Resolution: set-value - 4.0.1
</p>
</p>
<p></p>
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details> | non_priority | check dependencies tgz vulnerabilities highest severity is autoclosed vulnerable library check dependencies tgz path to dependency file package json path to vulnerable library node modules set value package json found in head commit a href vulnerabilities cve severity cvss dependency type fixed in check dependencies version remediation available high set value tgz 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 set value tgz create nested values and any intermediaries using dot notation a b c paths library home page a href path to dependency file package json path to vulnerable library node modules set value package json dependency hierarchy check dependencies tgz root library findup sync tgz micromatch tgz snapdragon tgz base tgz cache base tgz x set value tgz vulnerable library found in head commit a href found in base branch master vulnerability details this affects the package set value before a type confusion vulnerability can lead to a bypass of cve when the user provided keys used in the path parameter are arrays mend note after conducting further research mend has determined that all versions of set value up to version are vulnerable to cve publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version release date fix resolution set value step up your open source security game with mend | 0 |
285,968 | 21,559,998,129 | IssuesEvent | 2022-05-01 02:37:28 | DLR-RM/stable-baselines3 | https://api.github.com/repos/DLR-RM/stable-baselines3 | closed | Could anyone please help clarify batch_size, epochs concepts in the PPO algorithm? | documentation question | From the documentation on PPO algorithm:
- batch_size (int) – Minibatch size
- n_epochs (int) – Number of epoch when optimizing the surrogate loss
So my questions are:
1. the size of the batch should automatically be obtained from n_env*n_step. Then what is this "batch_size" argument for?
2. the number of epochs should automatically be obtained from total_timestep/(n_env*n_step). Then what is this "n_epochs" argument for?
Thank you | 1.0 | Could anyone please help clarify batch_size, epochs concepts in the PPO algorithm? - From the documentation on PPO algorithm:
- batch_size (int) – Minibatch size
- n_epochs (int) – Number of epoch when optimizing the surrogate loss
So my questions are:
1. the size of the batch should automatically be obtained from n_env*n_step. Then what is this "batch_size" argument for?
2. the number of epochs should automatically be obtained from total_timestep/(n_env*n_step). Then what is this "n_epochs" argument for?
Thank you | non_priority | could anyone please help clarify batch size epochs concepts in the ppo algorithm from the documentation on ppo algorithm batch size int – minibatch size n epochs int – number of epoch when optimizing the surrogate loss so my questions are the size of the batch should automatically be obtained from n env n step then what is this batch size argument for the number of epochs should automatically be obtained from total timestep n env n step then what is this n epochs argument for thank you | 0 |
97,161 | 28,114,429,545 | IssuesEvent | 2023-03-31 09:39:28 | App-vNext/Polly | https://api.github.com/repos/App-vNext/Polly | opened | Add Microsoft.CodeAnalysis.PublicApiAnalyzers | up-for-grabs CI/build v8 | Once we are nearer to code complete on Polly v8, we should add the [Microsoft.CodeAnalysis.PublicApiAnalyzers](https://github.com/dotnet/roslyn-analyzers/blob/main/src/PublicApiAnalyzers/PublicApiAnalyzers.Help.md) NuGet package into the build and configure the metadata files appropriately to "lock down" the API.
This then makes it easier going forward to identify potentially breaking changes to the API surface in future releases. We will also benefit from the built-in compatibility analysis that the package contains that might help identify any API usability issues we might inadvertently have created ahead of shipping.
| 1.0 | Add Microsoft.CodeAnalysis.PublicApiAnalyzers - Once we are nearer to code complete on Polly v8, we should add the [Microsoft.CodeAnalysis.PublicApiAnalyzers](https://github.com/dotnet/roslyn-analyzers/blob/main/src/PublicApiAnalyzers/PublicApiAnalyzers.Help.md) NuGet package into the build and configure the metadata files appropriately to "lock down" the API.
This then makes it easier going forward to identify potentially breaking changes to the API surface in future releases. We will also benefit from the built-in compatibility analysis that the package contains that might help identify any API usability issues we might inadvertently have created ahead of shipping.
| non_priority | add microsoft codeanalysis publicapianalyzers once we are nearer to code complete on polly we should add the nuget package into the build and configure the metadata files appropriately to lock down the api this then makes it easier going forward to identify potentially breaking changes to the api surface in future releases we will also benefit from the built in compatibility analysis that the package contains that might help identify any api usability issues we might inadvertently have created ahead of shipping | 0 |
148,071 | 13,224,739,675 | IssuesEvent | 2020-08-17 19:44:58 | Evitcani/mnemosync-api | https://api.github.com/repos/Evitcani/mnemosync-api | opened | Setup MnemoSync Test | api bot documentation enhancement | Need to finish setting up MnemoSync testing to put the test branches off of production. | 1.0 | Setup MnemoSync Test - Need to finish setting up MnemoSync testing to put the test branches off of production. | non_priority | setup mnemosync test need to finish setting up mnemosync testing to put the test branches off of production | 0 |
132,845 | 18,274,102,062 | IssuesEvent | 2021-10-04 16:41:50 | ghc-dev/bbbbb | https://api.github.com/repos/ghc-dev/bbbbb | closed | CVE-2016-10539 (High) detected in negotiator-0.5.3.tgz - autoclosed | security vulnerability | ## CVE-2016-10539 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>negotiator-0.5.3.tgz</b></p></summary>
<p>HTTP content negotiation</p>
<p>Library home page: <a href="https://registry.npmjs.org/negotiator/-/negotiator-0.5.3.tgz">https://registry.npmjs.org/negotiator/-/negotiator-0.5.3.tgz</a></p>
<p>Path to dependency file: bbbbb/package.json</p>
<p>Path to vulnerable library: bbbbb/node_modules/negotiator/package.json</p>
<p>
Dependency Hierarchy:
- express-4.13.4.tgz (Root Library)
- accepts-1.2.13.tgz
- :x: **negotiator-0.5.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/bbbbb/commit/ae233c606a93341e0c807a63f571de927fe2e0d9">ae233c606a93341e0c807a63f571de927fe2e0d9</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
negotiator is an HTTP content negotiator for Node.js and is used by many modules and frameworks including Express and Koa. The header for "Accept-Language", when parsed by negotiator 0.6.0 and earlier is vulnerable to Regular Expression Denial of Service via a specially crafted string.
<p>Publish Date: 2018-05-31
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-10539>CVE-2016-10539</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/106">https://www.npmjs.com/advisories/106</a></p>
<p>Release Date: 2018-05-31</p>
<p>Fix Resolution: 0.6.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"negotiator","packageVersion":"0.5.3","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"express:4.13.4;accepts:1.2.13;negotiator:0.5.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.6.1"}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2016-10539","vulnerabilityDetails":"negotiator is an HTTP content negotiator for Node.js and is used by many modules and frameworks including Express and Koa. The header for \"Accept-Language\", when parsed by negotiator 0.6.0 and earlier is vulnerable to Regular Expression Denial of Service via a specially crafted string.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-10539","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2016-10539 (High) detected in negotiator-0.5.3.tgz - autoclosed - ## CVE-2016-10539 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>negotiator-0.5.3.tgz</b></p></summary>
<p>HTTP content negotiation</p>
<p>Library home page: <a href="https://registry.npmjs.org/negotiator/-/negotiator-0.5.3.tgz">https://registry.npmjs.org/negotiator/-/negotiator-0.5.3.tgz</a></p>
<p>Path to dependency file: bbbbb/package.json</p>
<p>Path to vulnerable library: bbbbb/node_modules/negotiator/package.json</p>
<p>
Dependency Hierarchy:
- express-4.13.4.tgz (Root Library)
- accepts-1.2.13.tgz
- :x: **negotiator-0.5.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/bbbbb/commit/ae233c606a93341e0c807a63f571de927fe2e0d9">ae233c606a93341e0c807a63f571de927fe2e0d9</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
negotiator is an HTTP content negotiator for Node.js and is used by many modules and frameworks including Express and Koa. The header for "Accept-Language", when parsed by negotiator 0.6.0 and earlier is vulnerable to Regular Expression Denial of Service via a specially crafted string.
<p>Publish Date: 2018-05-31
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-10539>CVE-2016-10539</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/106">https://www.npmjs.com/advisories/106</a></p>
<p>Release Date: 2018-05-31</p>
<p>Fix Resolution: 0.6.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"negotiator","packageVersion":"0.5.3","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"express:4.13.4;accepts:1.2.13;negotiator:0.5.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.6.1"}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2016-10539","vulnerabilityDetails":"negotiator is an HTTP content negotiator for Node.js and is used by many modules and frameworks including Express and Koa. The header for \"Accept-Language\", when parsed by negotiator 0.6.0 and earlier is vulnerable to Regular Expression Denial of Service via a specially crafted string.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-10539","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in negotiator tgz autoclosed cve high severity vulnerability vulnerable library negotiator tgz http content negotiation library home page a href path to dependency file bbbbb package json path to vulnerable library bbbbb node modules negotiator package json dependency hierarchy express tgz root library accepts tgz x negotiator tgz vulnerable library found in head commit a href found in base branch main vulnerability details negotiator is an http content negotiator for node js and is used by many modules and frameworks including express and koa the header for accept language when parsed by negotiator and earlier is vulnerable to regular expression denial of service via a specially crafted string 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 isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree express accepts negotiator isminimumfixversionavailable true minimumfixversion basebranches vulnerabilityidentifier cve vulnerabilitydetails negotiator is an http content negotiator for node js and is used by many modules and frameworks including express and koa the header for accept language when parsed by negotiator and earlier is vulnerable to regular expression denial of service via a specially crafted string vulnerabilityurl | 0 |
23,054 | 7,273,494,281 | IssuesEvent | 2018-02-21 05:27:13 | ethereum/solidity | https://api.github.com/repos/ethereum/solidity | closed | Abort if Emscripten linking results in undefined symbols | build-system | From https://github.com/ethereum/solidity/pull/3491#issuecomment-365437236:
```
[100%] Linking CXX executable soljson.js
WARNING:root:not all asm.js optimizations are possible with ALLOW_MEMORY_GROWTH, disabling those. [-Walmost-asm]
warning: unresolved symbol: _ZNSt3__115basic_streambufIcNS_11char_traitsIcEEE5uflowEv
warning: unresolved symbol: _ZNSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEC1ERKS5_jjRKS4_
warning: unresolved symbol: _ZNSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEaSERKS5_
...
```
should be a build error.
Use the flag:
```
-s ERROR_ON_UNDEFINED_SYMBOLS=1
```
This is on by default in the CMake Emscripten module which we aren't using.
Ref:
- https://github.com/kripken/emscripten/blob/01fc56a092f8bf83528d6ee8d39db1cd49830f80/src/settings.js#L505-L511
- https://github.com/kripken/emscripten/blob/7f89560101843198787530731f40a65288f6f15f/cmake/Modules/Platform/Emscripten.cmake#L47-L49 | 1.0 | Abort if Emscripten linking results in undefined symbols - From https://github.com/ethereum/solidity/pull/3491#issuecomment-365437236:
```
[100%] Linking CXX executable soljson.js
WARNING:root:not all asm.js optimizations are possible with ALLOW_MEMORY_GROWTH, disabling those. [-Walmost-asm]
warning: unresolved symbol: _ZNSt3__115basic_streambufIcNS_11char_traitsIcEEE5uflowEv
warning: unresolved symbol: _ZNSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEC1ERKS5_jjRKS4_
warning: unresolved symbol: _ZNSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEaSERKS5_
...
```
should be a build error.
Use the flag:
```
-s ERROR_ON_UNDEFINED_SYMBOLS=1
```
This is on by default in the CMake Emscripten module which we aren't using.
Ref:
- https://github.com/kripken/emscripten/blob/01fc56a092f8bf83528d6ee8d39db1cd49830f80/src/settings.js#L505-L511
- https://github.com/kripken/emscripten/blob/7f89560101843198787530731f40a65288f6f15f/cmake/Modules/Platform/Emscripten.cmake#L47-L49 | non_priority | abort if emscripten linking results in undefined symbols from linking cxx executable soljson js warning root not all asm js optimizations are possible with allow memory growth disabling those warning unresolved symbol streambuficns warning unresolved symbol stringicns traitsiceens warning unresolved symbol stringicns traitsiceens should be a build error use the flag s error on undefined symbols this is on by default in the cmake emscripten module which we aren t using ref | 0 |
7,319 | 9,564,727,695 | IssuesEvent | 2019-05-05 06:39:48 | cryptape/cita | https://api.github.com/repos/cryptape/cita | closed | base_gas_required calculate problem | compatibility upgrade | ## base_gas_required calculate problem
Usually, before transaction executed in vm, some basic will be consumed firstly.
For example, if you send a transaction to create a contract, 53000 quotas will be consumed before this tx enters vm, so please ensure your gas > base_gas while sending transaction.
Base_gas calculation in ethereum:
> gas_prepare = 21000 + (68 or 4 per byte) + (32000 if tx.to == 0)
Implement in cita_vm as following:
```
pub fn get_gas_prepare(request: &InterpreterParams) -> u64 {
let mut gas_prepare: u64 = 0;
gas_prepare += G_TRANSACTION;
if request.is_create {
gas_prepare += G_CREATE
}
for i in &request.input {
if i == &0u8 {
gas_prepare += G_TX_DATA_ZERO
} else {
gas_prepare += G_TX_DATA_NON_ZERO
}
}
gas_prepare
}
```
Implement in cita_vm like this:
```
pub fn get_gas_prepare(request: &InterpreterParams) -> u64 {
let mut gas_prepare: u64 = 0;
gas_prepare += G_TRANSACTION;
if request.is_create {
gas_prepare += G_CREATE
}
gas_prepare
}
```
Did you find difference between above two calculation?
In CITA, we indeed have two related instructions `tx_data_zero_gas` and `tx_data_non_zero_gas`. However, we do nothing in basic gas calculation with code.
## Additional Information
#366
| True | base_gas_required calculate problem - ## base_gas_required calculate problem
Usually, before transaction executed in vm, some basic will be consumed firstly.
For example, if you send a transaction to create a contract, 53000 quotas will be consumed before this tx enters vm, so please ensure your gas > base_gas while sending transaction.
Base_gas calculation in ethereum:
> gas_prepare = 21000 + (68 or 4 per byte) + (32000 if tx.to == 0)
Implement in cita_vm as following:
```
pub fn get_gas_prepare(request: &InterpreterParams) -> u64 {
let mut gas_prepare: u64 = 0;
gas_prepare += G_TRANSACTION;
if request.is_create {
gas_prepare += G_CREATE
}
for i in &request.input {
if i == &0u8 {
gas_prepare += G_TX_DATA_ZERO
} else {
gas_prepare += G_TX_DATA_NON_ZERO
}
}
gas_prepare
}
```
Implement in cita_vm like this:
```
pub fn get_gas_prepare(request: &InterpreterParams) -> u64 {
let mut gas_prepare: u64 = 0;
gas_prepare += G_TRANSACTION;
if request.is_create {
gas_prepare += G_CREATE
}
gas_prepare
}
```
Did you find difference between above two calculation?
In CITA, we indeed have two related instructions `tx_data_zero_gas` and `tx_data_non_zero_gas`. However, we do nothing in basic gas calculation with code.
## Additional Information
#366
| non_priority | base gas required calculate problem base gas required calculate problem usually before transaction executed in vm some basic will be consumed firstly for example if you send a transaction to create a contract quotas will be consumed before this tx enters vm so please ensure your gas base gas while sending transaction base gas calculation in ethereum gas prepare or per byte if tx to implement in cita vm as following pub fn get gas prepare request interpreterparams let mut gas prepare gas prepare g transaction if request is create gas prepare g create for i in request input if i gas prepare g tx data zero else gas prepare g tx data non zero gas prepare implement in cita vm like this pub fn get gas prepare request interpreterparams let mut gas prepare gas prepare g transaction if request is create gas prepare g create gas prepare did you find difference between above two calculation in cita we indeed have two related instructions tx data zero gas and tx data non zero gas however we do nothing in basic gas calculation with code additional information | 0 |
18,381 | 10,949,080,682 | IssuesEvent | 2019-11-26 10:08:57 | Azure/azure-cli-extensions | https://api.github.com/repos/Azure/azure-cli-extensions | closed | az artifacts universal publish fails to download ArtifactTool_win10-x64_0.2.128 | Service Attention extension/devops |
### az artifacts universal publish fails to download ArtifactTool_win10-x64_0.2.128
Re-running the command attempts to download the tool again and fails midway.
## Describe the bug
**Command Name**
`az artifacts universal publish
Extension Name: azure-devops. Version: 0.10.0.`
**Errors:**
```
('Connection broken: OSError("(10054, \'WSAECONNRESET\')",)', OSError("(10054, 'WSAECONNRESET')",))
Traceback (most recent call last):
urllib3\urllib3\contrib\pyopenssl.py, ln 297, in recv_into
pip-install-ygnynjtx\pyOpenSSL\OpenSSL\SSL.py, ln 1822, in recv_into
pip-install-ygnynjtx\pyOpenSSL\OpenSSL\SSL.py, ln 1639, in _raise_ssl_error
OpenSSL.SSL.SysCallError: (10054, 'WSAECONNRESET')
...
for chunk in response.iter_content(chunk_size=1024 * 512):
pip-install-ygnynjtx\requests\requests\models.py, ln 753, in generate
requests.exceptions.ChunkedEncodingError: ('Connection broken: OSError("(10054, \'WSAECONNRESET\')",)', OSError("(10054, 'WSAECONNRESET')",))
```
## To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
- _Put any pre-requisite steps here..._
- `az artifacts universal publish --organization {} --feed {} -n {} -v {} --path {}`
## Expected Behavior
## Environment Summary
```
Windows-10-10.0.14393-SP0
Python 3.6.6
Shell: cmd.exe
azure-cli 2.0.66 *
Extensions:
azure-devops 0.10.0
```
## Additional Context
<!--Please don't remove this:-->
<!--auto-generated-->
| 1.0 | az artifacts universal publish fails to download ArtifactTool_win10-x64_0.2.128 -
### az artifacts universal publish fails to download ArtifactTool_win10-x64_0.2.128
Re-running the command attempts to download the tool again and fails midway.
## Describe the bug
**Command Name**
`az artifacts universal publish
Extension Name: azure-devops. Version: 0.10.0.`
**Errors:**
```
('Connection broken: OSError("(10054, \'WSAECONNRESET\')",)', OSError("(10054, 'WSAECONNRESET')",))
Traceback (most recent call last):
urllib3\urllib3\contrib\pyopenssl.py, ln 297, in recv_into
pip-install-ygnynjtx\pyOpenSSL\OpenSSL\SSL.py, ln 1822, in recv_into
pip-install-ygnynjtx\pyOpenSSL\OpenSSL\SSL.py, ln 1639, in _raise_ssl_error
OpenSSL.SSL.SysCallError: (10054, 'WSAECONNRESET')
...
for chunk in response.iter_content(chunk_size=1024 * 512):
pip-install-ygnynjtx\requests\requests\models.py, ln 753, in generate
requests.exceptions.ChunkedEncodingError: ('Connection broken: OSError("(10054, \'WSAECONNRESET\')",)', OSError("(10054, 'WSAECONNRESET')",))
```
## To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
- _Put any pre-requisite steps here..._
- `az artifacts universal publish --organization {} --feed {} -n {} -v {} --path {}`
## Expected Behavior
## Environment Summary
```
Windows-10-10.0.14393-SP0
Python 3.6.6
Shell: cmd.exe
azure-cli 2.0.66 *
Extensions:
azure-devops 0.10.0
```
## Additional Context
<!--Please don't remove this:-->
<!--auto-generated-->
| non_priority | az artifacts universal publish fails to download artifacttool az artifacts universal publish fails to download artifacttool re running the command attempts to download the tool again and fails midway describe the bug command name az artifacts universal publish extension name azure devops version errors connection broken oserror wsaeconnreset oserror wsaeconnreset traceback most recent call last contrib pyopenssl py ln in recv into pip install ygnynjtx pyopenssl openssl ssl py ln in recv into pip install ygnynjtx pyopenssl openssl ssl py ln in raise ssl error openssl ssl syscallerror wsaeconnreset for chunk in response iter content chunk size pip install ygnynjtx requests requests models py ln in generate requests exceptions chunkedencodingerror connection broken oserror wsaeconnreset oserror wsaeconnreset to reproduce steps to reproduce the behavior note that argument values have been redacted as they may contain sensitive information put any pre requisite steps here az artifacts universal publish organization feed n v path expected behavior environment summary windows python shell cmd exe azure cli extensions azure devops additional context | 0 |
40,652 | 5,246,449,890 | IssuesEvent | 2017-02-01 09:38:54 | sps-it15/DnD | https://api.github.com/repos/sps-it15/DnD | opened | Postava a levely | game design idea | Postavy by měly mít na začátku kolem 100 HP (záleží na rase/povolání). Maximální počet na jaký se dá vylevelovat by bylo kole 200-300 HP. To by ale mělo trvat docela dlouho a stále by pro začínajícího hráče mělo možné porazit hráče s vyšším levelem pokud bude mít štěstí. Pro levelup z levelu 1 na level 2 by bylo potřeba kolem 100 XP a na každý další 1.5x tolik (pro levelup 2-3 by bylo 150, 3-4 = 225, 4-5 = 337,5 atd...) (na testování hodnot je stránka zde: [odkaz](http://polakjan.cz/lvlcalc.html)). Za killnutí hráče by bylo kolem 100 až 200 XP, za killnutí NPC (barbara, atd...) 50 až 100 XP. Za splnění questu by byla odměna nejen Goldy ale i XP, ta by záležela na složitosti questu a jeho důležitosti v příběhu ostrova. Každý získaný level by přidal postavě 10-15 HP. Maximální level by byl kolem 20-30 levelu. | 1.0 | Postava a levely - Postavy by měly mít na začátku kolem 100 HP (záleží na rase/povolání). Maximální počet na jaký se dá vylevelovat by bylo kole 200-300 HP. To by ale mělo trvat docela dlouho a stále by pro začínajícího hráče mělo možné porazit hráče s vyšším levelem pokud bude mít štěstí. Pro levelup z levelu 1 na level 2 by bylo potřeba kolem 100 XP a na každý další 1.5x tolik (pro levelup 2-3 by bylo 150, 3-4 = 225, 4-5 = 337,5 atd...) (na testování hodnot je stránka zde: [odkaz](http://polakjan.cz/lvlcalc.html)). Za killnutí hráče by bylo kolem 100 až 200 XP, za killnutí NPC (barbara, atd...) 50 až 100 XP. Za splnění questu by byla odměna nejen Goldy ale i XP, ta by záležela na složitosti questu a jeho důležitosti v příběhu ostrova. Každý získaný level by přidal postavě 10-15 HP. Maximální level by byl kolem 20-30 levelu. | non_priority | postava a levely postavy by měly mít na začátku kolem hp záleží na rase povolání maximální počet na jaký se dá vylevelovat by bylo kole hp to by ale mělo trvat docela dlouho a stále by pro začínajícího hráče mělo možné porazit hráče s vyšším levelem pokud bude mít štěstí pro levelup z levelu na level by bylo potřeba kolem xp a na každý další tolik pro levelup by bylo atd na testování hodnot je stránka zde za killnutí hráče by bylo kolem až xp za killnutí npc barbara atd až xp za splnění questu by byla odměna nejen goldy ale i xp ta by záležela na složitosti questu a jeho důležitosti v příběhu ostrova každý získaný level by přidal postavě hp maximální level by byl kolem levelu | 0 |
166,693 | 12,968,081,577 | IssuesEvent | 2020-07-21 04:51:32 | groonga/grnxx | https://api.github.com/repos/groonga/grnxx | closed | 各種 DB の参照型を評価 | test | groonga, grnxxでは複数テーブルを連結するのに参照型を用いるため、「参照型の評価」
というタイトルにしましたが、要は各種DBにおいて複数テーブルを連結した場合の性能評価です。
| 1.0 | 各種 DB の参照型を評価 - groonga, grnxxでは複数テーブルを連結するのに参照型を用いるため、「参照型の評価」
というタイトルにしましたが、要は各種DBにおいて複数テーブルを連結した場合の性能評価です。
| non_priority | 各種 db の参照型を評価 groonga grnxxでは複数テーブルを連結するのに参照型を用いるため、「参照型の評価」 というタイトルにしましたが、要は各種dbにおいて複数テーブルを連結した場合の性能評価です。 | 0 |
130,503 | 12,438,427,685 | IssuesEvent | 2020-05-26 08:24:31 | dbwebb-se/oophp | https://api.github.com/repos/dbwebb-se/oophp | reopened | Installera phpdoc på Debian 10 med PHP 7.4 | documentation enhancement | Jag sitter med en nyinstallerad utvecklingsmiljö och vill få phpdoc att fungera.
1) I `me/redovisa` så kör jag `make install doc`. Jag får ett felmeddelande som innebär att bilder inte har skapats.
> Unable to find the `dot` command of the GraphViz package. Is GraphViz correctly installed and p
resent in your path?
Jag kan dock öppna katalogen `doc/api` i webbläsaren och se att api-dokumentationen är genererad, så delvis fungerar kommandot.
Jag löser felmeddelandet genom att installera kommandot `dot` som är en del av paketet `graphviz`.
```
sudo apt-get install graphviz
make doc
```
Nu kan jag även se bilder under menyvalet Charts.
Jag kan dubbelkolla vilken version av phpdoc jag använder.
```
$ .bin/phpdoc --version
phpDocumentor version v2.9.0
```
Jag kör på PHP 7.4 och får en hel del felutskrifter från kommandot, dock verkar det fungera så jag nöjer mig med det.
| 1.0 | Installera phpdoc på Debian 10 med PHP 7.4 - Jag sitter med en nyinstallerad utvecklingsmiljö och vill få phpdoc att fungera.
1) I `me/redovisa` så kör jag `make install doc`. Jag får ett felmeddelande som innebär att bilder inte har skapats.
> Unable to find the `dot` command of the GraphViz package. Is GraphViz correctly installed and p
resent in your path?
Jag kan dock öppna katalogen `doc/api` i webbläsaren och se att api-dokumentationen är genererad, så delvis fungerar kommandot.
Jag löser felmeddelandet genom att installera kommandot `dot` som är en del av paketet `graphviz`.
```
sudo apt-get install graphviz
make doc
```
Nu kan jag även se bilder under menyvalet Charts.
Jag kan dubbelkolla vilken version av phpdoc jag använder.
```
$ .bin/phpdoc --version
phpDocumentor version v2.9.0
```
Jag kör på PHP 7.4 och får en hel del felutskrifter från kommandot, dock verkar det fungera så jag nöjer mig med det.
| non_priority | installera phpdoc på debian med php jag sitter med en nyinstallerad utvecklingsmiljö och vill få phpdoc att fungera i me redovisa så kör jag make install doc jag får ett felmeddelande som innebär att bilder inte har skapats unable to find the dot command of the graphviz package is graphviz correctly installed and p resent in your path jag kan dock öppna katalogen doc api i webbläsaren och se att api dokumentationen är genererad så delvis fungerar kommandot jag löser felmeddelandet genom att installera kommandot dot som är en del av paketet graphviz sudo apt get install graphviz make doc nu kan jag även se bilder under menyvalet charts jag kan dubbelkolla vilken version av phpdoc jag använder bin phpdoc version phpdocumentor version jag kör på php och får en hel del felutskrifter från kommandot dock verkar det fungera så jag nöjer mig med det | 0 |
139,803 | 11,278,672,644 | IssuesEvent | 2020-01-15 07:29:44 | a2000-erp-team/WEBERP | https://api.github.com/repos/a2000-erp-team/WEBERP | opened | Warehouse->Stk Transaction->Stock Transfer (direct). The next line automatically comes out when accepting the line details. | WEB ERP Testing By Katrina | -Create IM transaction and accepts line item.
When accepts the line item, the next line automatically comes out.
| 1.0 | Warehouse->Stk Transaction->Stock Transfer (direct). The next line automatically comes out when accepting the line details. - -Create IM transaction and accepts line item.
When accepts the line item, the next line automatically comes out.
| non_priority | warehouse stk transaction stock transfer direct the next line automatically comes out when accepting the line details create im transaction and accepts line item when accepts the line item the next line automatically comes out | 0 |
223,033 | 17,535,814,899 | IssuesEvent | 2021-08-12 06:14:28 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | roachtest: backup/nodeShutdown/coordinator/n4cpu4 failed | C-test-failure O-robot O-roachtest release-blocker branch-release-21.1 | roachtest.backup/nodeShutdown/coordinator/n4cpu4 [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=3290967&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=3290967&tab=artifacts#/backup/nodeShutdown/coordinator/n4cpu4) on release-21.1 @ [c4d0e7baee3925541eed599ae771abb95c97732b](https://github.com/cockroachdb/cockroach/commits/c4d0e7baee3925541eed599ae771abb95c97732b):
```
The test failed on branch=release-21.1, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/backup/nodeShutdown/coordinator/n4cpu4/run_1
jobs.go:131,backup.go:132,test_runner.go:733: unexpectedly found job 683797475003269122 in state failed
(1) attached stack trace
-- stack trace:
| main.jobSurvivesNodeShutdown.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/jobs.go:79
| main.(*monitor).Go.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2666
| golang.org/x/sync/errgroup.(*Group).Go.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/golang.org/x/sync/errgroup/errgroup.go:57
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1371
Wraps: (2) unexpectedly found job 683797475003269122 in state failed
Error types: (1) *withstack.withStack (2) *errutil.leafError
cluster.go:1667,context.go:89,cluster.go:1656,test_runner.go:820: dead node detection: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod monitor teamcity-3290967-1628748601-01-n4cpu4 --oneshot --ignore-empty-nodes: exit status 1 2: dead (exit status 137)
4: 10659
3: 10607
1: 11767
Error: UNCLASSIFIED_PROBLEM: 2: dead (exit status 137)
(1) UNCLASSIFIED_PROBLEM
Wraps: (2) attached stack trace
-- stack trace:
| main.glob..func14
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:1147
| main.wrap.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:271
| github.com/spf13/cobra.(*Command).execute
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:830
| github.com/spf13/cobra.(*Command).ExecuteC
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:914
| github.com/spf13/cobra.(*Command).Execute
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:864
| main.main
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:1889
| runtime.main
| /usr/local/go/src/runtime/proc.go:225
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1371
Wraps: (3) 2: dead (exit status 137)
Error types: (1) errors.Unclassified (2) *withstack.withStack (3) *errutil.leafError
```
<details><summary>Reproduce</summary>
<p>
<p>To reproduce, try:
```bash
# From https://go.crdb.dev/p/roachstress, perhaps edited lightly.
caffeinate ./roachstress.sh backup/nodeShutdown/coordinator/n4cpu4
```
</p>
</p>
</details>
/cc @cockroachdb/bulk-io
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*backup/nodeShutdown/coordinator/n4cpu4.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| 2.0 | roachtest: backup/nodeShutdown/coordinator/n4cpu4 failed - roachtest.backup/nodeShutdown/coordinator/n4cpu4 [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=3290967&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=3290967&tab=artifacts#/backup/nodeShutdown/coordinator/n4cpu4) on release-21.1 @ [c4d0e7baee3925541eed599ae771abb95c97732b](https://github.com/cockroachdb/cockroach/commits/c4d0e7baee3925541eed599ae771abb95c97732b):
```
The test failed on branch=release-21.1, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/backup/nodeShutdown/coordinator/n4cpu4/run_1
jobs.go:131,backup.go:132,test_runner.go:733: unexpectedly found job 683797475003269122 in state failed
(1) attached stack trace
-- stack trace:
| main.jobSurvivesNodeShutdown.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/jobs.go:79
| main.(*monitor).Go.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2666
| golang.org/x/sync/errgroup.(*Group).Go.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/golang.org/x/sync/errgroup/errgroup.go:57
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1371
Wraps: (2) unexpectedly found job 683797475003269122 in state failed
Error types: (1) *withstack.withStack (2) *errutil.leafError
cluster.go:1667,context.go:89,cluster.go:1656,test_runner.go:820: dead node detection: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod monitor teamcity-3290967-1628748601-01-n4cpu4 --oneshot --ignore-empty-nodes: exit status 1 2: dead (exit status 137)
4: 10659
3: 10607
1: 11767
Error: UNCLASSIFIED_PROBLEM: 2: dead (exit status 137)
(1) UNCLASSIFIED_PROBLEM
Wraps: (2) attached stack trace
-- stack trace:
| main.glob..func14
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:1147
| main.wrap.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:271
| github.com/spf13/cobra.(*Command).execute
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:830
| github.com/spf13/cobra.(*Command).ExecuteC
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:914
| github.com/spf13/cobra.(*Command).Execute
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:864
| main.main
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:1889
| runtime.main
| /usr/local/go/src/runtime/proc.go:225
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1371
Wraps: (3) 2: dead (exit status 137)
Error types: (1) errors.Unclassified (2) *withstack.withStack (3) *errutil.leafError
```
<details><summary>Reproduce</summary>
<p>
<p>To reproduce, try:
```bash
# From https://go.crdb.dev/p/roachstress, perhaps edited lightly.
caffeinate ./roachstress.sh backup/nodeShutdown/coordinator/n4cpu4
```
</p>
</p>
</details>
/cc @cockroachdb/bulk-io
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*backup/nodeShutdown/coordinator/n4cpu4.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| non_priority | roachtest backup nodeshutdown coordinator failed roachtest backup nodeshutdown coordinator with on release the test failed on branch release cloud gce test artifacts and logs in home agent work go src github com cockroachdb cockroach artifacts backup nodeshutdown coordinator run jobs go backup go test runner go unexpectedly found job in state failed attached stack trace stack trace main jobsurvivesnodeshutdown home agent work go src github com cockroachdb cockroach pkg cmd roachtest jobs go main monitor go home agent work go src github com cockroachdb cockroach pkg cmd roachtest cluster go golang org x sync errgroup group go home agent work go src github com cockroachdb cockroach vendor golang org x sync errgroup errgroup go runtime goexit usr local go src runtime asm s wraps unexpectedly found job in state failed error types withstack withstack errutil leaferror cluster go context go cluster go test runner go dead node detection home agent work go src github com cockroachdb cockroach bin roachprod monitor teamcity oneshot ignore empty nodes exit status dead exit status error unclassified problem dead exit status unclassified problem wraps attached stack trace stack trace main glob home agent work go src github com cockroachdb cockroach pkg cmd roachprod main go main wrap home agent work go src github com cockroachdb cockroach pkg cmd roachprod main go github com cobra command execute home agent work go src github com cockroachdb cockroach vendor github com cobra command go github com cobra command executec home agent work go src github com cockroachdb cockroach vendor github com cobra command go github com cobra command execute home agent work go src github com cockroachdb cockroach vendor github com cobra command go main main home agent work go src github com cockroachdb cockroach pkg cmd roachprod main go runtime main usr local go src runtime proc go runtime goexit usr local go src runtime asm s wraps dead exit status error types errors unclassified withstack withstack errutil leaferror reproduce to reproduce try bash from perhaps edited lightly caffeinate roachstress sh backup nodeshutdown coordinator cc cockroachdb bulk io | 0 |
3,735 | 2,908,927,328 | IssuesEvent | 2015-06-20 06:47:22 | ipfs/go-ipfs | https://api.github.com/repos/ipfs/go-ipfs | closed | ipfs object patch help text incorrect | codereview | `ipfs object patch` help text says:
```
ipfs patch
```
multiple times | 1.0 | ipfs object patch help text incorrect - `ipfs object patch` help text says:
```
ipfs patch
```
multiple times | non_priority | ipfs object patch help text incorrect ipfs object patch help text says ipfs patch multiple times | 0 |
24,243 | 3,900,493,866 | IssuesEvent | 2016-04-18 06:26:13 | vincentaudebert/test-repo-from-init | https://api.github.com/repos/vincentaudebert/test-repo-from-init | opened | Objectives and strategy | 0 - Backlog BED Design FED Management Question | <a href="https://github.com/vincentaudebert"><img src="https://avatars.githubusercontent.com/u/3360430?v=3" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [vincentaudebert](https://github.com/vincentaudebert)**
_Sunday Apr 17, 2016 at 22:16 GMT_
_Originally opened as https://github.com/springload/template-discovery-phase/issues/1_
----
Establish the high level objectives of the project. If it suits, these can be expressed as an objective and a scope as per the classic ALA post “Never Get Involved In A Land War In Asia”. Doing this could mean:
- Facilitating stakeholder workshops.
- Recording and collating the stakeholder requirements.
- Prioritising stakeholder requirements.
- Converting stakeholder requirements into high level goals for project, prioritised, with a useful amount of detail and success criteria for each.
- Ratifying the prioritised list of project goals with stakeholders. Get them all to agree on it and have it in writing. Watch out for anyone on the client side or at Springload who “begrudgingly agrees” to this list and establish a plan for managing that.
**Checklist**
- [ ] Agree on the high level objectives of the project.
- [ ] Establish a strategy for meeting those objectives.
- [ ] Get written agreement on objectives and strategy from the client.
| 1.0 | Objectives and strategy - <a href="https://github.com/vincentaudebert"><img src="https://avatars.githubusercontent.com/u/3360430?v=3" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [vincentaudebert](https://github.com/vincentaudebert)**
_Sunday Apr 17, 2016 at 22:16 GMT_
_Originally opened as https://github.com/springload/template-discovery-phase/issues/1_
----
Establish the high level objectives of the project. If it suits, these can be expressed as an objective and a scope as per the classic ALA post “Never Get Involved In A Land War In Asia”. Doing this could mean:
- Facilitating stakeholder workshops.
- Recording and collating the stakeholder requirements.
- Prioritising stakeholder requirements.
- Converting stakeholder requirements into high level goals for project, prioritised, with a useful amount of detail and success criteria for each.
- Ratifying the prioritised list of project goals with stakeholders. Get them all to agree on it and have it in writing. Watch out for anyone on the client side or at Springload who “begrudgingly agrees” to this list and establish a plan for managing that.
**Checklist**
- [ ] Agree on the high level objectives of the project.
- [ ] Establish a strategy for meeting those objectives.
- [ ] Get written agreement on objectives and strategy from the client.
| non_priority | objectives and strategy issue by sunday apr at gmt originally opened as establish the high level objectives of the project if it suits these can be expressed as an objective and a scope as per the classic ala post “never get involved in a land war in asia” doing this could mean facilitating stakeholder workshops recording and collating the stakeholder requirements prioritising stakeholder requirements converting stakeholder requirements into high level goals for project prioritised with a useful amount of detail and success criteria for each ratifying the prioritised list of project goals with stakeholders get them all to agree on it and have it in writing watch out for anyone on the client side or at springload who “begrudgingly agrees” to this list and establish a plan for managing that checklist agree on the high level objectives of the project establish a strategy for meeting those objectives get written agreement on objectives and strategy from the client | 0 |
129,746 | 27,555,996,497 | IssuesEvent | 2023-03-07 17:58:18 | cmu-delphi/delphi-epidata | https://api.github.com/repos/cmu-delphi/delphi-epidata | closed | remove /covidcast/correlation endpoint | help wanted good first issue api change code health | since https://github.com/cmu-delphi/www-covidcast/pull/1058 removed it from the UI.
this work involves:
- [ ] editing https://github.com/cmu-delphi/delphi-epidata/blob/dev/src/server/endpoints/covidcast.py to remove the endpoint
- [ ] removing any related [unit](https://github.com/cmu-delphi/delphi-epidata/tree/dev/tests) or [integration tests](https://github.com/cmu-delphi/delphi-epidata/tree/dev/integrations) | 1.0 | remove /covidcast/correlation endpoint - since https://github.com/cmu-delphi/www-covidcast/pull/1058 removed it from the UI.
this work involves:
- [ ] editing https://github.com/cmu-delphi/delphi-epidata/blob/dev/src/server/endpoints/covidcast.py to remove the endpoint
- [ ] removing any related [unit](https://github.com/cmu-delphi/delphi-epidata/tree/dev/tests) or [integration tests](https://github.com/cmu-delphi/delphi-epidata/tree/dev/integrations) | non_priority | remove covidcast correlation endpoint since removed it from the ui this work involves editing to remove the endpoint removing any related or | 0 |
7,086 | 3,934,392,058 | IssuesEvent | 2016-04-25 22:29:03 | jens-maus/yam | https://api.github.com/repos/jens-maus/yam | closed | YAM ignores headerlines starting with "newline" | #major @undecided enhancement fixed MIME nightly build | **Originally by _mario@cattaneo.de_ on 2013-02-05 15:41:43 +0100**
___
I don't know if this is a bug, or fine due to definition, but YAM cannot/does not handle headerlines that start with newlines.
Eg.
SUBJECT:
This is a subject
Will be displayed with "empty subject", whereas
SUBJECT: This is a
subject
displays the complete string "This is a subject". | 1.0 | YAM ignores headerlines starting with "newline" - **Originally by _mario@cattaneo.de_ on 2013-02-05 15:41:43 +0100**
___
I don't know if this is a bug, or fine due to definition, but YAM cannot/does not handle headerlines that start with newlines.
Eg.
SUBJECT:
This is a subject
Will be displayed with "empty subject", whereas
SUBJECT: This is a
subject
displays the complete string "This is a subject". | non_priority | yam ignores headerlines starting with newline originally by mario cattaneo de on i don t know if this is a bug or fine due to definition but yam cannot does not handle headerlines that start with newlines eg subject this is a subject will be displayed with empty subject whereas subject this is a subject displays the complete string this is a subject | 0 |
178,885 | 14,684,074,702 | IssuesEvent | 2021-01-01 00:03:12 | GreenleafLab/ArchR | https://api.github.com/repos/GreenleafLab/ArchR | closed | addMotifAnnotations | documentation | Is it possible to run addMotifAnnotations on tilematrix instead of peakmatrix? | 1.0 | addMotifAnnotations - Is it possible to run addMotifAnnotations on tilematrix instead of peakmatrix? | non_priority | addmotifannotations is it possible to run addmotifannotations on tilematrix instead of peakmatrix | 0 |
103,805 | 12,973,710,673 | IssuesEvent | 2020-07-21 14:25:37 | elastic/kibana | https://api.github.com/repos/elastic/kibana | closed | [Ingest Manager] Improve unenroll agent UX | Team:Ingest Management [zube]: Inbox design | Related: https://github.com/elastic/beats/issues/18825
## Problem
Currently when asked to unenroll an agent, we don't provide any useful information about what this action means.
Things to figure out:
- what happens after you unenroll an agent? Does the agent still appear in Fleet or does it go away? Can you re-enroll? Do you get redirected? etc.
## Design
[Figma file](https://www.figma.com/file/k68l5ot8dxxT7MI5M8InCg/Ingest-Manager-Beta-1?node-id=3670%3A271)
[Prototype](https://www.figma.com/proto/k68l5ot8dxxT7MI5M8InCg/Ingest-Manager-Beta-1?node-id=3690%3A0&viewport=-3631%2C-7107%2C0.48691877722740173&scaling=min-zoom)
I added some additional information to the unenroll modal. Showing the agent ID in the title did not render well. Instead, I'm using a table to show both the Agent ID and Host Name for additional context. The same host could contain multiple agents, so showing the Agent ID is necessary, but the Host Name seems more meaningful.
| 1.0 | [Ingest Manager] Improve unenroll agent UX - Related: https://github.com/elastic/beats/issues/18825
## Problem
Currently when asked to unenroll an agent, we don't provide any useful information about what this action means.
Things to figure out:
- what happens after you unenroll an agent? Does the agent still appear in Fleet or does it go away? Can you re-enroll? Do you get redirected? etc.
## Design
[Figma file](https://www.figma.com/file/k68l5ot8dxxT7MI5M8InCg/Ingest-Manager-Beta-1?node-id=3670%3A271)
[Prototype](https://www.figma.com/proto/k68l5ot8dxxT7MI5M8InCg/Ingest-Manager-Beta-1?node-id=3690%3A0&viewport=-3631%2C-7107%2C0.48691877722740173&scaling=min-zoom)
I added some additional information to the unenroll modal. Showing the agent ID in the title did not render well. Instead, I'm using a table to show both the Agent ID and Host Name for additional context. The same host could contain multiple agents, so showing the Agent ID is necessary, but the Host Name seems more meaningful.
| non_priority | improve unenroll agent ux related problem currently when asked to unenroll an agent we don t provide any useful information about what this action means things to figure out what happens after you unenroll an agent does the agent still appear in fleet or does it go away can you re enroll do you get redirected etc design i added some additional information to the unenroll modal showing the agent id in the title did not render well instead i m using a table to show both the agent id and host name for additional context the same host could contain multiple agents so showing the agent id is necessary but the host name seems more meaningful | 0 |
55,776 | 23,597,086,068 | IssuesEvent | 2022-08-23 20:22:54 | cityofaustin/atd-data-tech | https://api.github.com/repos/cityofaustin/atd-data-tech | closed | MMC page is loading slowly, new "Active" filter at default start | Workgroup: AMD Type: Bug Report Impact: 3-Minor Service: Apps Type: Testing Product: AMD Data Tracker | <!-- Email -->
<!-- chris.sherrick@austintexas.gov -->
> What application are you using?
Data Tracker
> Describe the problem.
MMC as a whole has been experiencing sluggish load times. Seems to be more frequent and longer than usual. Just wanted to let you all know.
> Website Address
https://atd.knack.com/amd#mmc/
Internet Browser: Chrome
> Requested By
Chris S.
Request ID: DTS22-104910
| 1.0 | MMC page is loading slowly, new "Active" filter at default start - <!-- Email -->
<!-- chris.sherrick@austintexas.gov -->
> What application are you using?
Data Tracker
> Describe the problem.
MMC as a whole has been experiencing sluggish load times. Seems to be more frequent and longer than usual. Just wanted to let you all know.
> Website Address
https://atd.knack.com/amd#mmc/
Internet Browser: Chrome
> Requested By
Chris S.
Request ID: DTS22-104910
| non_priority | mmc page is loading slowly new active filter at default start what application are you using data tracker describe the problem mmc as a whole has been experiencing sluggish load times seems to be more frequent and longer than usual just wanted to let you all know website address internet browser chrome requested by chris s request id | 0 |
13,545 | 9,986,109,827 | IssuesEvent | 2019-07-10 18:15:37 | Azure/azure-sdk-for-node | https://api.github.com/repos/Azure/azure-sdk-for-node | closed | Incomplete response from provider.getAvailableStacks() call | App Services | The response from Azure when using the sdk does not include the majorVersions array that contains all the versions and display names available for web apps.
The expected response returns when making a call to this endpoint `https://management.azure.com/providers/Microsoft.Web/availableStacks?osTypeSelected=Linux&api-version=2018-02-01`. | 1.0 | Incomplete response from provider.getAvailableStacks() call - The response from Azure when using the sdk does not include the majorVersions array that contains all the versions and display names available for web apps.
The expected response returns when making a call to this endpoint `https://management.azure.com/providers/Microsoft.Web/availableStacks?osTypeSelected=Linux&api-version=2018-02-01`. | non_priority | incomplete response from provider getavailablestacks call the response from azure when using the sdk does not include the majorversions array that contains all the versions and display names available for web apps the expected response returns when making a call to this endpoint | 0 |
199,526 | 15,046,526,038 | IssuesEvent | 2021-02-03 07:32:21 | WordPress/gutenberg | https://api.github.com/repos/WordPress/gutenberg | closed | Latest Post block: Not able to select block after leaving and returning to the page. | [Block] Latest Posts [Status] In Progress [Type] Bug | ## Description
Not able to select Latest Post block after having saved the page it is located in.
## Step-by-step reproduction instructions
<!--
Please list the steps needed to reproduce the bug. For example:
1. Create some posts.
2. Go to a page and add the Latest Post block.
3. Save the page.
4. Refresh the page.
5. Click the Latest Post block (not selectable).
-->
## Expected behaviour
<!-- Please describe what you expected to happen. -->
I expected to be able to select the Latest Post block after having saved and refreshed the page.
## Actual behaviour
<!-- Please describe what actually happened. -->
Not able to select Latest post block after having saved and refreshed the page.
## Screenshots or screen recording (optional)
## WordPress information
- WordPress version: 5.6.0
- Gutenberg version: 9.8
- Are all plugins except Gutenberg deactivated? Yes
- Are you using a default theme (e.g. Twenty Twenty-One)? Yes (Twenty Twenty One)
## Device information
Local site using Desktop Server.
Chrome
Mac OSX 10.15.7
@ntsekouras Nik I believe you would like to know about this bug. | 1.0 | Latest Post block: Not able to select block after leaving and returning to the page. - ## Description
Not able to select Latest Post block after having saved the page it is located in.
## Step-by-step reproduction instructions
<!--
Please list the steps needed to reproduce the bug. For example:
1. Create some posts.
2. Go to a page and add the Latest Post block.
3. Save the page.
4. Refresh the page.
5. Click the Latest Post block (not selectable).
-->
## Expected behaviour
<!-- Please describe what you expected to happen. -->
I expected to be able to select the Latest Post block after having saved and refreshed the page.
## Actual behaviour
<!-- Please describe what actually happened. -->
Not able to select Latest post block after having saved and refreshed the page.
## Screenshots or screen recording (optional)
## WordPress information
- WordPress version: 5.6.0
- Gutenberg version: 9.8
- Are all plugins except Gutenberg deactivated? Yes
- Are you using a default theme (e.g. Twenty Twenty-One)? Yes (Twenty Twenty One)
## Device information
Local site using Desktop Server.
Chrome
Mac OSX 10.15.7
@ntsekouras Nik I believe you would like to know about this bug. | non_priority | latest post block not able to select block after leaving and returning to the page description not able to select latest post block after having saved the page it is located in step by step reproduction instructions please list the steps needed to reproduce the bug for example create some posts go to a page and add the latest post block save the page refresh the page click the latest post block not selectable expected behaviour i expected to be able to select the latest post block after having saved and refreshed the page actual behaviour not able to select latest post block after having saved and refreshed the page screenshots or screen recording optional wordpress information wordpress version gutenberg version are all plugins except gutenberg deactivated yes are you using a default theme e g twenty twenty one yes twenty twenty one device information local site using desktop server chrome mac osx ntsekouras nik i believe you would like to know about this bug | 0 |
189,492 | 22,047,052,166 | IssuesEvent | 2022-05-30 03:47:39 | madhans23/linux-4.1.15 | https://api.github.com/repos/madhans23/linux-4.1.15 | closed | CVE-2016-9794 (High) detected in linux-stable-rtv4.1.33 - autoclosed | security vulnerability | ## CVE-2016-9794 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/madhans23/linux-4.1.15/commit/f9d19044b0eef1965f9bc412d7d9e579b74ec968">f9d19044b0eef1965f9bc412d7d9e579b74ec968</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>/sound/core/pcm_lib.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>
Race condition in the snd_pcm_period_elapsed function in sound/core/pcm_lib.c in the ALSA subsystem in the Linux kernel before 4.7 allows local users to cause a denial of service (use-after-free) or possibly have unspecified other impact via a crafted SNDRV_PCM_TRIGGER_START command.
<p>Publish Date: 2016-12-28
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-9794>CVE-2016-9794</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.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-9794">https://nvd.nist.gov/vuln/detail/CVE-2016-9794</a></p>
<p>Release Date: 2016-12-28</p>
<p>Fix Resolution: 4.7</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2016-9794 (High) detected in linux-stable-rtv4.1.33 - autoclosed - ## CVE-2016-9794 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/madhans23/linux-4.1.15/commit/f9d19044b0eef1965f9bc412d7d9e579b74ec968">f9d19044b0eef1965f9bc412d7d9e579b74ec968</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>/sound/core/pcm_lib.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>
Race condition in the snd_pcm_period_elapsed function in sound/core/pcm_lib.c in the ALSA subsystem in the Linux kernel before 4.7 allows local users to cause a denial of service (use-after-free) or possibly have unspecified other impact via a crafted SNDRV_PCM_TRIGGER_START command.
<p>Publish Date: 2016-12-28
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-9794>CVE-2016-9794</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.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-9794">https://nvd.nist.gov/vuln/detail/CVE-2016-9794</a></p>
<p>Release Date: 2016-12-28</p>
<p>Fix Resolution: 4.7</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in linux stable autoclosed cve high severity vulnerability vulnerable library linux stable julia cartwright s fork of linux stable rt git library home page a href found in head commit a href found in base branch master vulnerable source files sound core pcm lib c vulnerability details race condition in the snd pcm period elapsed function in sound core pcm lib c in the alsa subsystem in the linux kernel before allows local users to cause a denial of service use after free or possibly have unspecified other impact via a crafted sndrv pcm trigger start command publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
84,484 | 10,542,032,862 | IssuesEvent | 2019-10-02 12:18:22 | microsoft/vscode | https://api.github.com/repos/microsoft/vscode | closed | Task CWD not changing, runs task in workspace root folder | *as-designed tasks |
Issue Type: <b>Bug</b>
I am attempting to run a task from a subfolder of the workspace, but no matter what I try, it runs everything in the $workspaceFolder root directory. Here is a simple task that reproduces the error for me:
```
{
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "2.0.0",
"tasks": [
{
"label": "echo",
"type": "shell",
"command": "echo ${cwd}",
"options": {
"cwd": "${workspaceFolder}/build/",
"shell": {
"executable": "tcsh",
"args": [
"-c"
]
}
}
}
]
}
```
VS Code version: Code 1.38.1 (b37e54c98e1a74ba89e03073e5a3761284e3ffb0, 2019-09-11T13:30:08.229Z)
OS version: Linux x64 3.10.0-957.27.2.el7.x86_64
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Intel(R) Xeon(R) CPU X5680 @ 3.33GHz (12 x 3324)|
|GPU Status|2d_canvas: unavailable_software<br>flash_3d: unavailable_off<br>flash_stage3d: unavailable_off<br>flash_stage3d_baseline: unavailable_off<br>gpu_compositing: unavailable_off<br>multiple_raster_threads: enabled_on<br>native_gpu_memory_buffers: disabled_software<br>oop_rasterization: unavailable_off<br>protected_video_decode: unavailable_off<br>rasterization: unavailable_off<br>skia_deferred_display_list: disabled_off<br>skia_renderer: disabled_off<br>surface_synchronization: enabled_on<br>video_decode: unavailable_off<br>viz_display_compositor: disabled_off<br>webgl: enabled_readback<br>webgl2: unavailable_off|
|Load (avg)|0, 1, 1|
|Memory (System)|157.40GB (144.84GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (2)</summary>
Extension|Author (truncated)|Version
---|---|---
vscode-emacs-friendly|lfs|0.9.0
veriloghdl|msh|1.0.3
</details>
<!-- generated by issue reporter --> | 1.0 | Task CWD not changing, runs task in workspace root folder -
Issue Type: <b>Bug</b>
I am attempting to run a task from a subfolder of the workspace, but no matter what I try, it runs everything in the $workspaceFolder root directory. Here is a simple task that reproduces the error for me:
```
{
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "2.0.0",
"tasks": [
{
"label": "echo",
"type": "shell",
"command": "echo ${cwd}",
"options": {
"cwd": "${workspaceFolder}/build/",
"shell": {
"executable": "tcsh",
"args": [
"-c"
]
}
}
}
]
}
```
VS Code version: Code 1.38.1 (b37e54c98e1a74ba89e03073e5a3761284e3ffb0, 2019-09-11T13:30:08.229Z)
OS version: Linux x64 3.10.0-957.27.2.el7.x86_64
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Intel(R) Xeon(R) CPU X5680 @ 3.33GHz (12 x 3324)|
|GPU Status|2d_canvas: unavailable_software<br>flash_3d: unavailable_off<br>flash_stage3d: unavailable_off<br>flash_stage3d_baseline: unavailable_off<br>gpu_compositing: unavailable_off<br>multiple_raster_threads: enabled_on<br>native_gpu_memory_buffers: disabled_software<br>oop_rasterization: unavailable_off<br>protected_video_decode: unavailable_off<br>rasterization: unavailable_off<br>skia_deferred_display_list: disabled_off<br>skia_renderer: disabled_off<br>surface_synchronization: enabled_on<br>video_decode: unavailable_off<br>viz_display_compositor: disabled_off<br>webgl: enabled_readback<br>webgl2: unavailable_off|
|Load (avg)|0, 1, 1|
|Memory (System)|157.40GB (144.84GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (2)</summary>
Extension|Author (truncated)|Version
---|---|---
vscode-emacs-friendly|lfs|0.9.0
veriloghdl|msh|1.0.3
</details>
<!-- generated by issue reporter --> | non_priority | task cwd not changing runs task in workspace root folder issue type bug i am attempting to run a task from a subfolder of the workspace but no matter what i try it runs everything in the workspacefolder root directory here is a simple task that reproduces the error for me see for the documentation about the tasks json format version tasks label echo type shell command echo cwd options cwd workspacefolder build shell executable tcsh args c vs code version code os version linux system info item value cpus intel r xeon r cpu x gpu status canvas unavailable software flash unavailable off flash unavailable off flash baseline unavailable off gpu compositing unavailable off multiple raster threads enabled on native gpu memory buffers disabled software oop rasterization unavailable off protected video decode unavailable off rasterization unavailable off skia deferred display list disabled off skia renderer disabled off surface synchronization enabled on video decode unavailable off viz display compositor disabled off webgl enabled readback unavailable off load avg memory system free process argv screen reader no vm extensions extension author truncated version vscode emacs friendly lfs veriloghdl msh | 0 |
77,222 | 21,703,033,012 | IssuesEvent | 2022-05-10 07:03:28 | sandboxie-plus/Sandboxie | https://api.github.com/repos/sandboxie-plus/Sandboxie | closed | TOR Browser does not work why ? | Known issue fixed in next build Workaround Firefox-related incompatibility | SBIE2203 Failed to communicate with the service Sandboxie: *GUIPROXY_00000002; MsgId: 13 - firefox.exe [C0000034]
SBIE2203 Failed to communicate with the service Sandboxie: *GUIPROXY_00000002; MsgId: 13 - firefox.exe [C0000034]
SBIE2203 Failed to communicate with the service Sandboxie: *GUIPROXY_00000002; MsgId: 13 - firefox.exe [C0000034]
err=41020897 ... str1= ... str2= DefaultBox
err=41020897 ... str1= ... str2= DefaultBox
err=41020897 ... str1= ... str2= DefaultBox
SBIE2203 Failed to communicate with the service Sandboxie: *GUIPROXY_00000002; MsgId: 15 - firefox.exe [C0000034]
SBIE2203 Failed to communicate with the service Sandboxie: *GUIPROXY_00000002; MsgId: 15 - firefox.exe [C0000034]
SBIE2203 Failed to communicate with the service Sandboxie: *GUIPROXY_00000002; MsgId: 6 - firefox.exe [C0000034]
err=41020897 ... str1= ... str2= DefaultBox
err=41020897 ... str1= ... str2= DefaultBox
err=41020897 ... str1= ... str2= DefaultBox
err=41020897 ... str1= ... str2= DefaultBox
err=41020897 ... str1= ... str2= DefaultBox
err=41020897 ... str1= ... str2= DefaultBox
SBIE2203 Failed to communicate with the service Sandboxie: request C0000037
SBIE2203 Failed to communicate with the service Sandboxie: *GUIPROXY_00000002; MsgId: 14 - SandboxieRpcSs.exe [C0000080]
| 1.0 | TOR Browser does not work why ? - SBIE2203 Failed to communicate with the service Sandboxie: *GUIPROXY_00000002; MsgId: 13 - firefox.exe [C0000034]
SBIE2203 Failed to communicate with the service Sandboxie: *GUIPROXY_00000002; MsgId: 13 - firefox.exe [C0000034]
SBIE2203 Failed to communicate with the service Sandboxie: *GUIPROXY_00000002; MsgId: 13 - firefox.exe [C0000034]
err=41020897 ... str1= ... str2= DefaultBox
err=41020897 ... str1= ... str2= DefaultBox
err=41020897 ... str1= ... str2= DefaultBox
SBIE2203 Failed to communicate with the service Sandboxie: *GUIPROXY_00000002; MsgId: 15 - firefox.exe [C0000034]
SBIE2203 Failed to communicate with the service Sandboxie: *GUIPROXY_00000002; MsgId: 15 - firefox.exe [C0000034]
SBIE2203 Failed to communicate with the service Sandboxie: *GUIPROXY_00000002; MsgId: 6 - firefox.exe [C0000034]
err=41020897 ... str1= ... str2= DefaultBox
err=41020897 ... str1= ... str2= DefaultBox
err=41020897 ... str1= ... str2= DefaultBox
err=41020897 ... str1= ... str2= DefaultBox
err=41020897 ... str1= ... str2= DefaultBox
err=41020897 ... str1= ... str2= DefaultBox
SBIE2203 Failed to communicate with the service Sandboxie: request C0000037
SBIE2203 Failed to communicate with the service Sandboxie: *GUIPROXY_00000002; MsgId: 14 - SandboxieRpcSs.exe [C0000080]
| non_priority | tor browser does not work why failed to communicate with the service sandboxie guiproxy msgid firefox exe failed to communicate with the service sandboxie guiproxy msgid firefox exe failed to communicate with the service sandboxie guiproxy msgid firefox exe err defaultbox err defaultbox err defaultbox failed to communicate with the service sandboxie guiproxy msgid firefox exe failed to communicate with the service sandboxie guiproxy msgid firefox exe failed to communicate with the service sandboxie guiproxy msgid firefox exe err defaultbox err defaultbox err defaultbox err defaultbox err defaultbox err defaultbox failed to communicate with the service sandboxie request failed to communicate with the service sandboxie guiproxy msgid sandboxierpcss exe | 0 |
81,356 | 10,232,255,898 | IssuesEvent | 2019-08-18 16:03:25 | ezeed/topics-of-stars | https://api.github.com/repos/ezeed/topics-of-stars | closed | Use graphql.macro for import graphql file | documentation | Use the `graphql.macro` to import query from different file.
Doc:
https://www.apollographql.com/docs/react/recipes/webpack/#create-react-app | 1.0 | Use graphql.macro for import graphql file - Use the `graphql.macro` to import query from different file.
Doc:
https://www.apollographql.com/docs/react/recipes/webpack/#create-react-app | non_priority | use graphql macro for import graphql file use the graphql macro to import query from different file doc | 0 |
5,770 | 3,994,274,055 | IssuesEvent | 2016-05-10 11:43:55 | Virtual-Labs/problem-solving-iiith | https://api.github.com/repos/Virtual-Labs/problem-solving-iiith | reopened | QA_Sequences_Experiment | Category :Usability Developed by:IIIT Hyd Severity :S3 Status :Differed Version Number: v1.2.2 | Defect Description:
In the experiment page when we click on 'no files selected', a file upload popup box is displaying on the screen to chose a file where no action should be performed when we click on 'no files selected
Actual Result:
In the experiment page when we click on 'no files selected', a file upload popup box is displaying on the screen to chose a file.
Environment :
OS: Windows 7, Ubuntu-16.04,Centos-6
Browsers: Firefox-42.0,Chrome-47.0,chromium-45.0
Bandwidth : 100Mbps
Hardware Configuration:8GBRAM ,
Processor:i5
Test Step Link:
https://github.com/Virtual-Labs/problem-solving-iiith/blob/master/test-cases/integration_test-cases/Sequences/Sequences_40_Experiment_p2%20.org
| True | QA_Sequences_Experiment - Defect Description:
In the experiment page when we click on 'no files selected', a file upload popup box is displaying on the screen to chose a file where no action should be performed when we click on 'no files selected
Actual Result:
In the experiment page when we click on 'no files selected', a file upload popup box is displaying on the screen to chose a file.
Environment :
OS: Windows 7, Ubuntu-16.04,Centos-6
Browsers: Firefox-42.0,Chrome-47.0,chromium-45.0
Bandwidth : 100Mbps
Hardware Configuration:8GBRAM ,
Processor:i5
Test Step Link:
https://github.com/Virtual-Labs/problem-solving-iiith/blob/master/test-cases/integration_test-cases/Sequences/Sequences_40_Experiment_p2%20.org
| non_priority | qa sequences experiment defect description in the experiment page when we click on no files selected a file upload popup box is displaying on the screen to chose a file where no action should be performed when we click on no files selected actual result in the experiment page when we click on no files selected a file upload popup box is displaying on the screen to chose a file environment os windows ubuntu centos browsers firefox chrome chromium bandwidth hardware configuration processor test step link | 0 |
72,768 | 15,243,745,819 | IssuesEvent | 2021-02-19 11:43:29 | AlexRogalskiy/github-action-screenshots | https://api.github.com/repos/AlexRogalskiy/github-action-screenshots | opened | WS-2020-0163 (Medium) detected in marked-0.7.0.tgz | security vulnerability | ## WS-2020-0163 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>marked-0.7.0.tgz</b></p></summary>
<p>A markdown parser built for speed</p>
<p>Library home page: <a href="https://registry.npmjs.org/marked/-/marked-0.7.0.tgz">https://registry.npmjs.org/marked/-/marked-0.7.0.tgz</a></p>
<p>Path to dependency file: github-action-screenshots/package.json</p>
<p>Path to vulnerable library: github-action-screenshots/node_modules/marked/package.json</p>
<p>
Dependency Hierarchy:
- semantic-release-15.14.0.tgz (Root Library)
- :x: **marked-0.7.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/github-action-screenshots/commit/92a602be7db136b19b96e35ca13e2c4c5f92b925">92a602be7db136b19b96e35ca13e2c4c5f92b925</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
marked before 1.1.1 is vulnerable to Regular Expression Denial of Service (REDoS). rules.js have multiple unused capture groups which can lead to a Denial of Service.
<p>Publish Date: 2020-07-02
<p>URL: <a href=https://github.com/markedjs/marked/commit/bd4f8c464befad2b304d51e33e89e567326e62e0>WS-2020-0163</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- 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://github.com/markedjs/marked/releases/tag/v1.1.1">https://github.com/markedjs/marked/releases/tag/v1.1.1</a></p>
<p>Release Date: 2020-07-02</p>
<p>Fix Resolution: marked - 1.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-0163 (Medium) detected in marked-0.7.0.tgz - ## WS-2020-0163 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>marked-0.7.0.tgz</b></p></summary>
<p>A markdown parser built for speed</p>
<p>Library home page: <a href="https://registry.npmjs.org/marked/-/marked-0.7.0.tgz">https://registry.npmjs.org/marked/-/marked-0.7.0.tgz</a></p>
<p>Path to dependency file: github-action-screenshots/package.json</p>
<p>Path to vulnerable library: github-action-screenshots/node_modules/marked/package.json</p>
<p>
Dependency Hierarchy:
- semantic-release-15.14.0.tgz (Root Library)
- :x: **marked-0.7.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/github-action-screenshots/commit/92a602be7db136b19b96e35ca13e2c4c5f92b925">92a602be7db136b19b96e35ca13e2c4c5f92b925</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
marked before 1.1.1 is vulnerable to Regular Expression Denial of Service (REDoS). rules.js have multiple unused capture groups which can lead to a Denial of Service.
<p>Publish Date: 2020-07-02
<p>URL: <a href=https://github.com/markedjs/marked/commit/bd4f8c464befad2b304d51e33e89e567326e62e0>WS-2020-0163</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- 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://github.com/markedjs/marked/releases/tag/v1.1.1">https://github.com/markedjs/marked/releases/tag/v1.1.1</a></p>
<p>Release Date: 2020-07-02</p>
<p>Fix Resolution: marked - 1.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_priority | ws medium detected in marked tgz ws medium severity vulnerability vulnerable library marked tgz a markdown parser built for speed library home page a href path to dependency file github action screenshots package json path to vulnerable library github action screenshots node modules marked package json dependency hierarchy semantic release tgz root library x marked tgz vulnerable library found in head commit a href found in base branch master vulnerability details marked before is vulnerable to regular expression denial of service redos rules js have multiple unused capture groups which can lead to a denial of service 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 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 marked step up your open source security game with whitesource | 0 |
65,016 | 8,784,236,163 | IssuesEvent | 2018-12-20 09:15:34 | mdrft/Blueqat | https://api.github.com/repos/mdrft/Blueqat | closed | The doc directory is incomplete to build sphinx style document | documentation | The doc directory seems to have api reference, but it isn't included in any toctree. Additionally it should provide an overview page for grabbing overview of the framework at a glance. | 1.0 | The doc directory is incomplete to build sphinx style document - The doc directory seems to have api reference, but it isn't included in any toctree. Additionally it should provide an overview page for grabbing overview of the framework at a glance. | non_priority | the doc directory is incomplete to build sphinx style document the doc directory seems to have api reference but it isn t included in any toctree additionally it should provide an overview page for grabbing overview of the framework at a glance | 0 |
271,416 | 23,603,339,487 | IssuesEvent | 2022-08-24 05:41:46 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | ccl/changefeedccl: TestChangefeedInitialScan failed | C-test-failure O-robot branch-master | ccl/changefeedccl.TestChangefeedInitialScan [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/6213858?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/6213858?buildTab=artifacts#/) on master @ [003c0360de8b64319b5f0f127b99be91dbdca8a3](https://github.com/cockroachdb/cockroach/commits/003c0360de8b64319b5f0f127b99be91dbdca8a3):
```
=== RUN TestChangefeedInitialScan
test_log_scope.go:162: test logs captured to: /artifacts/tmp/_tmp/a77002d7c9453d7cd2d382f907780e13/logTestChangefeedInitialScan4243794510
test_log_scope.go:80: use -show-logs to present logs inline
=== CONT TestChangefeedInitialScan
changefeed_test.go:869: -- test log scope end --
--- FAIL: TestChangefeedInitialScan (7.01s)
=== RUN TestChangefeedInitialScan/sinkless/no_cursor_-_no_initial_scan
changefeed_test.go:834: ERROR: context canceled (SQLSTATE XXUUU)
--- FAIL: TestChangefeedInitialScan/sinkless/no_cursor_-_no_initial_scan (1.40s)
=== RUN TestChangefeedInitialScan/sinkless
helpers_test.go:716: making server as system tenant
helpers_test.go:803: making sinkless feed factory
--- FAIL: TestChangefeedInitialScan/sinkless (6.81s)
```
<p>Parameters: <code>TAGS=bazel,gss,deadlock</code>
</p>
<details><summary>Help</summary>
<p>
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
</p>
</details>
/cc @cockroachdb/cdc
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestChangefeedInitialScan.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| 1.0 | ccl/changefeedccl: TestChangefeedInitialScan failed - ccl/changefeedccl.TestChangefeedInitialScan [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/6213858?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/6213858?buildTab=artifacts#/) on master @ [003c0360de8b64319b5f0f127b99be91dbdca8a3](https://github.com/cockroachdb/cockroach/commits/003c0360de8b64319b5f0f127b99be91dbdca8a3):
```
=== RUN TestChangefeedInitialScan
test_log_scope.go:162: test logs captured to: /artifacts/tmp/_tmp/a77002d7c9453d7cd2d382f907780e13/logTestChangefeedInitialScan4243794510
test_log_scope.go:80: use -show-logs to present logs inline
=== CONT TestChangefeedInitialScan
changefeed_test.go:869: -- test log scope end --
--- FAIL: TestChangefeedInitialScan (7.01s)
=== RUN TestChangefeedInitialScan/sinkless/no_cursor_-_no_initial_scan
changefeed_test.go:834: ERROR: context canceled (SQLSTATE XXUUU)
--- FAIL: TestChangefeedInitialScan/sinkless/no_cursor_-_no_initial_scan (1.40s)
=== RUN TestChangefeedInitialScan/sinkless
helpers_test.go:716: making server as system tenant
helpers_test.go:803: making sinkless feed factory
--- FAIL: TestChangefeedInitialScan/sinkless (6.81s)
```
<p>Parameters: <code>TAGS=bazel,gss,deadlock</code>
</p>
<details><summary>Help</summary>
<p>
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
</p>
</details>
/cc @cockroachdb/cdc
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestChangefeedInitialScan.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| non_priority | ccl changefeedccl testchangefeedinitialscan failed ccl changefeedccl testchangefeedinitialscan with on master run testchangefeedinitialscan test log scope go test logs captured to artifacts tmp tmp test log scope go use show logs to present logs inline cont testchangefeedinitialscan changefeed test go test log scope end fail testchangefeedinitialscan run testchangefeedinitialscan sinkless no cursor no initial scan changefeed test go error context canceled sqlstate xxuuu fail testchangefeedinitialscan sinkless no cursor no initial scan run testchangefeedinitialscan sinkless helpers test go making server as system tenant helpers test go making sinkless feed factory fail testchangefeedinitialscan sinkless parameters tags bazel gss deadlock help see also cc cockroachdb cdc | 0 |
104,662 | 8,996,776,646 | IssuesEvent | 2019-02-02 04:34:33 | sinhrks/daskperiment | https://api.github.com/repos/sinhrks/daskperiment | opened | TST: Add initialization tests | Test | Test whether instanciated Experinemt can load previous env info. | 1.0 | TST: Add initialization tests - Test whether instanciated Experinemt can load previous env info. | non_priority | tst add initialization tests test whether instanciated experinemt can load previous env info | 0 |
872 | 2,552,160,852 | IssuesEvent | 2015-02-02 15:31:51 | swagger-api/swagger-core | https://api.github.com/repos/swagger-api/swagger-core | opened | Fix javadocs for annotations | Documentation | The 1.3.10 javadocs for the annotations didn't get included in the 1.5.0-M1 release. Will be fixed for M2. | 1.0 | Fix javadocs for annotations - The 1.3.10 javadocs for the annotations didn't get included in the 1.5.0-M1 release. Will be fixed for M2. | non_priority | fix javadocs for annotations the javadocs for the annotations didn t get included in the release will be fixed for | 0 |
168,611 | 26,672,875,908 | IssuesEvent | 2023-01-26 11:54:45 | vaadin/docs | https://api.github.com/repos/vaadin/docs | closed | Documented NumberField.setStepButtonsVisible() doesn't exist in java API | design system | The setStepButtonsVisible() method mentioned in docs/articles/components/number-field/index.asciidoc doesn't seem to exist in java API. | 1.0 | Documented NumberField.setStepButtonsVisible() doesn't exist in java API - The setStepButtonsVisible() method mentioned in docs/articles/components/number-field/index.asciidoc doesn't seem to exist in java API. | non_priority | documented numberfield setstepbuttonsvisible doesn t exist in java api the setstepbuttonsvisible method mentioned in docs articles components number field index asciidoc doesn t seem to exist in java api | 0 |
127,935 | 10,500,676,576 | IssuesEvent | 2019-09-26 11:03:52 | Omeljusik/teenjob_development | https://api.github.com/repos/Omeljusik/teenjob_development | closed | [Admin_Org] При незаполнении любого из пунктов кроме описания, при попытке "опубликовать" сайт ломается. Одинаково для Волонтерство, Стажировки, Мероприятия. | critical ready to test | Запись экрана: https://drive.google.com/file/d/1D5lv_25HBIEiyR_GZ5hx7Kk95W2uj2SI/view?usp=sharing
## Как должно быть
- [ ] при незаполнении необходимого для заполнения поля высвечивается предупреждение "Заполните это поле"
- [ ] из стажировок/волонтерства убрать * с "Телефон*"
- [ ] дбавить * к названию, городу, возрасту, профобласти, описанию
- [ ] добавить обозначение "Описание" перед редакционной панелью
### Сделать редакционную панель в 2 раза длиннее
### Вместо заголовка "Новое объявление" при создании стажировки "Стажировка", при создании волонтерства "Волонтерство", при создании мероприятия "Мероприятие"
### Все макеты (исправленные):
Волонтерство/Стажировки https://www.figma.com/file/OD9PcqDHdfLJHDLJi34l3wAH/teenjob?node-id=1201%3A3
Мероприятия https://www.figma.com/file/OD9PcqDHdfLJHDLJi34l3wAH/teenjob?node-id=1205%3A5
| 1.0 | [Admin_Org] При незаполнении любого из пунктов кроме описания, при попытке "опубликовать" сайт ломается. Одинаково для Волонтерство, Стажировки, Мероприятия. - Запись экрана: https://drive.google.com/file/d/1D5lv_25HBIEiyR_GZ5hx7Kk95W2uj2SI/view?usp=sharing
## Как должно быть
- [ ] при незаполнении необходимого для заполнения поля высвечивается предупреждение "Заполните это поле"
- [ ] из стажировок/волонтерства убрать * с "Телефон*"
- [ ] дбавить * к названию, городу, возрасту, профобласти, описанию
- [ ] добавить обозначение "Описание" перед редакционной панелью
### Сделать редакционную панель в 2 раза длиннее
### Вместо заголовка "Новое объявление" при создании стажировки "Стажировка", при создании волонтерства "Волонтерство", при создании мероприятия "Мероприятие"
### Все макеты (исправленные):
Волонтерство/Стажировки https://www.figma.com/file/OD9PcqDHdfLJHDLJi34l3wAH/teenjob?node-id=1201%3A3
Мероприятия https://www.figma.com/file/OD9PcqDHdfLJHDLJi34l3wAH/teenjob?node-id=1205%3A5
| non_priority | при незаполнении любого из пунктов кроме описания при попытке опубликовать сайт ломается одинаково для волонтерство стажировки мероприятия запись экрана как должно быть при незаполнении необходимого для заполнения поля высвечивается предупреждение заполните это поле из стажировок волонтерства убрать с телефон дбавить к названию городу возрасту профобласти описанию добавить обозначение описание перед редакционной панелью сделать редакционную панель в раза длиннее вместо заголовка новое объявление при создании стажировки стажировка при создании волонтерства волонтерство при создании мероприятия мероприятие все макеты исправленные волонтерство стажировки мероприятия | 0 |
4,526 | 7,187,987,029 | IssuesEvent | 2018-02-02 08:24:11 | AdguardTeam/AdguardForAndroid | https://api.github.com/repos/AdguardTeam/AdguardForAndroid | closed | nl.rijksoverheid.digid.pub - HTTPS filtering issue | SSL compatibility | https://play.google.com/store/apps/details?id=nl.rijksoverheid.digid.pub&hl
> I didn't know I could disable HTTP filtering for specific apps. This indeed solved the problem (the app gave an error stating no connection could be made) and has no side effects as the app doesn't contain any ads. | True | nl.rijksoverheid.digid.pub - HTTPS filtering issue - https://play.google.com/store/apps/details?id=nl.rijksoverheid.digid.pub&hl
> I didn't know I could disable HTTP filtering for specific apps. This indeed solved the problem (the app gave an error stating no connection could be made) and has no side effects as the app doesn't contain any ads. | non_priority | nl rijksoverheid digid pub https filtering issue i didn t know i could disable http filtering for specific apps this indeed solved the problem the app gave an error stating no connection could be made and has no side effects as the app doesn t contain any ads | 0 |
107,177 | 9,203,721,548 | IssuesEvent | 2019-03-08 03:49:43 | carlwilson/eark-corpus-test | https://api.github.com/repos/carlwilson/eark-corpus-test | closed | CSIP12 Test Case Description | test case | **Specification:**
- **Name:** E-ARK CSIP
- **Version:** 2.0-DRAFT
- **URL:** http://earkcsip.dilcis.eu/
**Requirement:**
- **Id:** CSIP12
- **Link:** http://earkcsip.dilcis.eu/#CSIP12
**Error Level:** MUST
**Description:**
The type of the mandatory agent is “OTHER”.
| 1.0 | CSIP12 Test Case Description - **Specification:**
- **Name:** E-ARK CSIP
- **Version:** 2.0-DRAFT
- **URL:** http://earkcsip.dilcis.eu/
**Requirement:**
- **Id:** CSIP12
- **Link:** http://earkcsip.dilcis.eu/#CSIP12
**Error Level:** MUST
**Description:**
The type of the mandatory agent is “OTHER”.
| non_priority | test case description specification name e ark csip version draft url requirement id link error level must description the type of the mandatory agent is “other” | 0 |
81,789 | 10,186,147,768 | IssuesEvent | 2019-08-10 10:38:51 | nowakprojects/PersonalEducation | https://api.github.com/repos/nowakprojects/PersonalEducation | opened | Udi Dahan - Blog - DDD, CQRS | *Good* Blog Domain-Driven Design | - [ ] How to create fully encapsulated Domain Models
http://udidahan.com/2008/02/29/how-to-create-fully-encapsulated-domain-models/
- [ ] http://udidahan.com/2008/08/25/domain-events-take-2/
- [ ] http://udidahan.com/2009/06/14/domain-events-salvation/ | 1.0 | Udi Dahan - Blog - DDD, CQRS - - [ ] How to create fully encapsulated Domain Models
http://udidahan.com/2008/02/29/how-to-create-fully-encapsulated-domain-models/
- [ ] http://udidahan.com/2008/08/25/domain-events-take-2/
- [ ] http://udidahan.com/2009/06/14/domain-events-salvation/ | non_priority | udi dahan blog ddd cqrs how to create fully encapsulated domain models | 0 |
111,759 | 14,143,459,888 | IssuesEvent | 2020-11-10 15:18:00 | xr3ngine/xr3ngine | https://api.github.com/repos/xr3ngine/xr3ngine | closed | Admin Control Panel | client design server | Administrators should be able to edit everything in their server configuration and have it affect the whole cluster.
1. Set up React Admin in front end -- https://marmelab.com/react-admin/
2. If user is admin, add "Admin" option to user menu (dropdown from user name + icon in top right)
3. User view -- admin can list all users, or search by string, with a drop down for connected accounts (all, email, phone, github ID, etc)
Users can be banned, have their password reset, or their basic profile details changed -- admin can also view user's activity stream.
5. Create server-settings table to store server configuration values (server name, etc), seed with current config if values don't exist in database
6. UI Panel -- parse all config options and make them available for admin to manage | 1.0 | Admin Control Panel - Administrators should be able to edit everything in their server configuration and have it affect the whole cluster.
1. Set up React Admin in front end -- https://marmelab.com/react-admin/
2. If user is admin, add "Admin" option to user menu (dropdown from user name + icon in top right)
3. User view -- admin can list all users, or search by string, with a drop down for connected accounts (all, email, phone, github ID, etc)
Users can be banned, have their password reset, or their basic profile details changed -- admin can also view user's activity stream.
5. Create server-settings table to store server configuration values (server name, etc), seed with current config if values don't exist in database
6. UI Panel -- parse all config options and make them available for admin to manage | non_priority | admin control panel administrators should be able to edit everything in their server configuration and have it affect the whole cluster set up react admin in front end if user is admin add admin option to user menu dropdown from user name icon in top right user view admin can list all users or search by string with a drop down for connected accounts all email phone github id etc users can be banned have their password reset or their basic profile details changed admin can also view user s activity stream create server settings table to store server configuration values server name etc seed with current config if values don t exist in database ui panel parse all config options and make them available for admin to manage | 0 |
79,362 | 10,120,883,178 | IssuesEvent | 2019-07-31 14:34:52 | MagmaDNN/magmadnn | https://api.github.com/repos/MagmaDNN/magmadnn | closed | [DOCUMENTATION] Pipelines For Build and Linting | documentation | MagmaDNN needs a build and test pipeline for it newly committed features. A build pipeline will be difficult as a custom server will be needed to build and run GPU tests.
However, it should be fairly straightforward to set up an Azure pipeline to run the linter on the codebase to see if it passes style guidelines. | 1.0 | [DOCUMENTATION] Pipelines For Build and Linting - MagmaDNN needs a build and test pipeline for it newly committed features. A build pipeline will be difficult as a custom server will be needed to build and run GPU tests.
However, it should be fairly straightforward to set up an Azure pipeline to run the linter on the codebase to see if it passes style guidelines. | non_priority | pipelines for build and linting magmadnn needs a build and test pipeline for it newly committed features a build pipeline will be difficult as a custom server will be needed to build and run gpu tests however it should be fairly straightforward to set up an azure pipeline to run the linter on the codebase to see if it passes style guidelines | 0 |
334,106 | 29,820,353,396 | IssuesEvent | 2023-06-17 01:33:01 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | reopened | Fix layers.test_conv3d_layer | Sub Task Ivy Stateful API Failing Test | | | |
|---|---|
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5217726926/jobs/9417844157"><img src=https://img.shields.io/badge/-failure-red></a>
|numpy|<a href="null"><img src=https://img.shields.io/badge/-failure-red></a>
|tensorflow|<a href="null"><img src=https://img.shields.io/badge/-failure-red></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5217726926/jobs/9417844157"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5217726926/jobs/9417844157"><img src=https://img.shields.io/badge/-failure-red></a>
| 1.0 | Fix layers.test_conv3d_layer - | | |
|---|---|
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5217726926/jobs/9417844157"><img src=https://img.shields.io/badge/-failure-red></a>
|numpy|<a href="null"><img src=https://img.shields.io/badge/-failure-red></a>
|tensorflow|<a href="null"><img src=https://img.shields.io/badge/-failure-red></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5217726926/jobs/9417844157"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5217726926/jobs/9417844157"><img src=https://img.shields.io/badge/-failure-red></a>
| non_priority | fix layers test layer torch a href src numpy img src tensorflow img src jax a href src paddle a href src | 0 |
109,603 | 23,795,444,303 | IssuesEvent | 2022-09-02 19:04:26 | backstage/backstage | https://api.github.com/repos/backstage/backstage | closed | TechDocs: Cannot publish to S3 bucket | bug docs-like-code | <!---
Please use this template when reporting bugs. Thank you!
-->
## Expected Behavior
TechDocs should be able to use the S3 bucket
## Actual Behavior
I get the following error:
```
2022-09-02T18:45:49.348Z techdocs error Could not retrieve metadata about the AWS S3 bucket [bucket-name]. Make sure the bucket exists. Also make sure that authentication is setup either by explicitly defining credentials and region in techdocs.publisher.awsS3 in app config or by using environment variables. Refer to https://backstage.io/docs/features/techdocs/using-cloud-storage type=plugin
2022-09-02T18:45:49.349Z techdocs error from AWS client library Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1 type=plugin code=CredentialsError time=Fri Sep 02 2022 18:45:49 GMT+0000 (Coordinated Universal Time) requestId=a0482e95-a07a-450e-b424-6e8d6504dab8 statusCode=403 retryable=false retryDelay=97.85600385199255 originalError=[object Object] stack=CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
at Request.extractError (/app/node_modules/aws-sdk/lib/protocol/query.js:50:29)
at Request.callListeners (/app/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/app/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/app/node_modules/aws-sdk/lib/request.js:686:14)
at Request.transition (/app/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/app/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /app/node_modules/aws-sdk/lib/state_machine.js:26:10
```
## Your Environment
**ENV variables**:
```
AWS_DEFAULT_REGION=eu-west-1
AWS_REGION=eu-west-1
AWS_ROLE_ARN=arnRoleAssumedByEKSPod
AWS_WEB_IDENTITY_TOKEN_FILE=/var/run/secrets/eks.amazonaws.com/serviceaccount/token
AWS_STS_REGIONAL_ENDPOINTS=regional
```
*app-config.yaml*:
```
publisher:
type: 'awsS3' # Alternatives - 'googleGcs' or 'awsS3'. Read documentation for using alternatives.
awsS3:
bucketName: 'bucket-name'
region: ${AWS_REGION}
credentials:
roleArn: techDocsRoleArn
```
In AWS, `techDocsRoleArn` has the following statement so the pod can assume `techDocsRoleArn`:
```
Statement = [
{
Action = "sts:AssumeRole"
Effect = "Allow"
Sid = ""
Principal = {
AWS = "arnRoleAssumedByEKSPod"
}
}
]
```
and has attached this policy:
```
policy = jsonencode({
"Version" : "2012-10-17",
"Statement" : [
{
"Effect" : "Allow",
"Action" : ["s3:PutObject",
"s3:GetObject",
"s3:DeleteObjectVersion",
"s3:ListBucket",
"s3:DeleteObject",
"s3:PutObjectAcl"],
"Resource" : ["arn:aws:s3:::${var.techdocs_bucket_name}", "arn:aws:s3:::${var.techdocs_bucket_name}/*"]
}
]
})
``` | 1.0 | TechDocs: Cannot publish to S3 bucket - <!---
Please use this template when reporting bugs. Thank you!
-->
## Expected Behavior
TechDocs should be able to use the S3 bucket
## Actual Behavior
I get the following error:
```
2022-09-02T18:45:49.348Z techdocs error Could not retrieve metadata about the AWS S3 bucket [bucket-name]. Make sure the bucket exists. Also make sure that authentication is setup either by explicitly defining credentials and region in techdocs.publisher.awsS3 in app config or by using environment variables. Refer to https://backstage.io/docs/features/techdocs/using-cloud-storage type=plugin
2022-09-02T18:45:49.349Z techdocs error from AWS client library Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1 type=plugin code=CredentialsError time=Fri Sep 02 2022 18:45:49 GMT+0000 (Coordinated Universal Time) requestId=a0482e95-a07a-450e-b424-6e8d6504dab8 statusCode=403 retryable=false retryDelay=97.85600385199255 originalError=[object Object] stack=CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set AWS_SDK_LOAD_CONFIG=1
at Request.extractError (/app/node_modules/aws-sdk/lib/protocol/query.js:50:29)
at Request.callListeners (/app/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/app/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/app/node_modules/aws-sdk/lib/request.js:686:14)
at Request.transition (/app/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/app/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /app/node_modules/aws-sdk/lib/state_machine.js:26:10
```
## Your Environment
**ENV variables**:
```
AWS_DEFAULT_REGION=eu-west-1
AWS_REGION=eu-west-1
AWS_ROLE_ARN=arnRoleAssumedByEKSPod
AWS_WEB_IDENTITY_TOKEN_FILE=/var/run/secrets/eks.amazonaws.com/serviceaccount/token
AWS_STS_REGIONAL_ENDPOINTS=regional
```
*app-config.yaml*:
```
publisher:
type: 'awsS3' # Alternatives - 'googleGcs' or 'awsS3'. Read documentation for using alternatives.
awsS3:
bucketName: 'bucket-name'
region: ${AWS_REGION}
credentials:
roleArn: techDocsRoleArn
```
In AWS, `techDocsRoleArn` has the following statement so the pod can assume `techDocsRoleArn`:
```
Statement = [
{
Action = "sts:AssumeRole"
Effect = "Allow"
Sid = ""
Principal = {
AWS = "arnRoleAssumedByEKSPod"
}
}
]
```
and has attached this policy:
```
policy = jsonencode({
"Version" : "2012-10-17",
"Statement" : [
{
"Effect" : "Allow",
"Action" : ["s3:PutObject",
"s3:GetObject",
"s3:DeleteObjectVersion",
"s3:ListBucket",
"s3:DeleteObject",
"s3:PutObjectAcl"],
"Resource" : ["arn:aws:s3:::${var.techdocs_bucket_name}", "arn:aws:s3:::${var.techdocs_bucket_name}/*"]
}
]
})
``` | non_priority | techdocs cannot publish to bucket please use this template when reporting bugs thank you expected behavior techdocs should be able to use the bucket actual behavior i get the following error techdocs error could not retrieve metadata about the aws bucket make sure the bucket exists also make sure that authentication is setup either by explicitly defining credentials and region in techdocs publisher in app config or by using environment variables refer to type plugin techdocs error from aws client library missing credentials in config if using aws config file set aws sdk load config type plugin code credentialserror time fri sep gmt coordinated universal time requestid statuscode retryable false retrydelay originalerror stack credentialserror missing credentials in config if using aws config file set aws sdk load config at request extracterror app node modules aws sdk lib protocol query js at request calllisteners app node modules aws sdk lib sequential executor js at request emit app node modules aws sdk lib sequential executor js at request emit app node modules aws sdk lib request js at request transition app node modules aws sdk lib request js at acceptorstatemachine runto app node modules aws sdk lib state machine js at app node modules aws sdk lib state machine js your environment env variables aws default region eu west aws region eu west aws role arn arnroleassumedbyekspod aws web identity token file var run secrets eks amazonaws com serviceaccount token aws sts regional endpoints regional app config yaml publisher type alternatives googlegcs or read documentation for using alternatives bucketname bucket name region aws region credentials rolearn techdocsrolearn in aws techdocsrolearn has the following statement so the pod can assume techdocsrolearn statement action sts assumerole effect allow sid principal aws arnroleassumedbyekspod and has attached this policy policy jsonencode version statement effect allow action putobject getobject deleteobjectversion listbucket deleteobject putobjectacl resource | 0 |
104,554 | 13,097,574,400 | IssuesEvent | 2020-08-03 17:43:43 | near/near-explorer | https://api.github.com/repos/near/near-explorer | opened | "Nodes" stats on the Dashboard page should not be misleading | Item Design help wanted | 
"/" as it suggests that it is something out of the "total number", which is not the case here. It is 67 validation nodes / 57 nodes that report telemetry recently [a.k.a. "known to be online" since nodes may opt-out of sending telemetry data] | 1.0 | "Nodes" stats on the Dashboard page should not be misleading - 
"/" as it suggests that it is something out of the "total number", which is not the case here. It is 67 validation nodes / 57 nodes that report telemetry recently [a.k.a. "known to be online" since nodes may opt-out of sending telemetry data] | non_priority | nodes stats on the dashboard page should not be misleading as it suggests that it is something out of the total number which is not the case here it is validation nodes nodes that report telemetry recently | 0 |
240,019 | 19,987,826,920 | IssuesEvent | 2022-01-30 22:58:49 | solvcon/devenv | https://api.github.com/repos/solvcon/devenv | closed | [solvcon] CI fails | testing | We introduce https://github.com/solvcon/devenv/pull/97 for https://github.com/solvcon/devenv/issues/92 , and I believe the pull request fails SOLVCON built by devenv in the Action runs manually triggered by me again today:
- https://github.com/solvcon/devenv/runs/4594808783?check_suite_focus=true
- https://github.com/solvcon/solvcon/runs/4594813592?check_suite_focus=true | 1.0 | [solvcon] CI fails - We introduce https://github.com/solvcon/devenv/pull/97 for https://github.com/solvcon/devenv/issues/92 , and I believe the pull request fails SOLVCON built by devenv in the Action runs manually triggered by me again today:
- https://github.com/solvcon/devenv/runs/4594808783?check_suite_focus=true
- https://github.com/solvcon/solvcon/runs/4594813592?check_suite_focus=true | non_priority | ci fails we introduce for and i believe the pull request fails solvcon built by devenv in the action runs manually triggered by me again today | 0 |
260,731 | 27,784,706,474 | IssuesEvent | 2023-03-17 01:30:24 | michaeldotson/home-inventory-vue-app | https://api.github.com/repos/michaeldotson/home-inventory-vue-app | opened | CVE-2022-37598 (High) detected in uglify-js-3.4.10.tgz | Mend: dependency security vulnerability | ## CVE-2022-37598 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>uglify-js-3.4.10.tgz</b></p></summary>
<p>JavaScript parser, mangler/compressor and beautifier toolkit</p>
<p>Library home page: <a href="https://registry.npmjs.org/uglify-js/-/uglify-js-3.4.10.tgz">https://registry.npmjs.org/uglify-js/-/uglify-js-3.4.10.tgz</a></p>
<p>Path to dependency file: /home-inventory-vue-app/package.json</p>
<p>Path to vulnerable library: /node_modules/uglify-js/package.json</p>
<p>
Dependency Hierarchy:
- cli-service-3.5.1.tgz (Root Library)
- html-webpack-plugin-3.2.0.tgz
- html-minifier-3.5.21.tgz
- :x: **uglify-js-3.4.10.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
** DISPUTED ** Prototype pollution vulnerability in function DEFNODE in ast.js in mishoo UglifyJS 3.13.2 via the name variable in ast.js. NOTE: the vendor considers this an invalid report.
<p>Publish Date: 2022-10-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-37598>CVE-2022-37598</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-10-20</p>
<p>Fix Resolution: uglify-js - 3.13.10</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-37598 (High) detected in uglify-js-3.4.10.tgz - ## CVE-2022-37598 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>uglify-js-3.4.10.tgz</b></p></summary>
<p>JavaScript parser, mangler/compressor and beautifier toolkit</p>
<p>Library home page: <a href="https://registry.npmjs.org/uglify-js/-/uglify-js-3.4.10.tgz">https://registry.npmjs.org/uglify-js/-/uglify-js-3.4.10.tgz</a></p>
<p>Path to dependency file: /home-inventory-vue-app/package.json</p>
<p>Path to vulnerable library: /node_modules/uglify-js/package.json</p>
<p>
Dependency Hierarchy:
- cli-service-3.5.1.tgz (Root Library)
- html-webpack-plugin-3.2.0.tgz
- html-minifier-3.5.21.tgz
- :x: **uglify-js-3.4.10.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
** DISPUTED ** Prototype pollution vulnerability in function DEFNODE in ast.js in mishoo UglifyJS 3.13.2 via the name variable in ast.js. NOTE: the vendor considers this an invalid report.
<p>Publish Date: 2022-10-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-37598>CVE-2022-37598</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-10-20</p>
<p>Fix Resolution: uglify-js - 3.13.10</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in uglify js tgz cve high severity vulnerability vulnerable library uglify js tgz javascript parser mangler compressor and beautifier toolkit library home page a href path to dependency file home inventory vue app package json path to vulnerable library node modules uglify js package json dependency hierarchy cli service tgz root library html webpack plugin tgz html minifier tgz x uglify js tgz vulnerable library vulnerability details disputed prototype pollution vulnerability in function defnode in ast js in mishoo uglifyjs via the name variable in ast js note the vendor considers this an invalid report publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version release date fix resolution uglify js step up your open source security game with mend | 0 |
137,659 | 30,729,620,453 | IssuesEvent | 2023-07-27 23:28:48 | demergent-labs/azle | https://api.github.com/repos/demergent-labs/azle | closed | Replace CdkTryFromVmValueErrors with JsErrors | code cleanliness | Every time that we try to convert from a VM value into Rust, it means that we were just in a JS context and are thus able to throw an exception up to that JS layer if anything in the conversion goes wrong. That means we shouldn't create intermediate string representations of the errors, but should instead create native JsErrors. We encounter the same problem in Kybra.
Relates to https://github.com/demergent-labs/kybra/issues/392 | 1.0 | Replace CdkTryFromVmValueErrors with JsErrors - Every time that we try to convert from a VM value into Rust, it means that we were just in a JS context and are thus able to throw an exception up to that JS layer if anything in the conversion goes wrong. That means we shouldn't create intermediate string representations of the errors, but should instead create native JsErrors. We encounter the same problem in Kybra.
Relates to https://github.com/demergent-labs/kybra/issues/392 | non_priority | replace cdktryfromvmvalueerrors with jserrors every time that we try to convert from a vm value into rust it means that we were just in a js context and are thus able to throw an exception up to that js layer if anything in the conversion goes wrong that means we shouldn t create intermediate string representations of the errors but should instead create native jserrors we encounter the same problem in kybra relates to | 0 |
88,359 | 17,570,023,402 | IssuesEvent | 2021-08-14 13:44:30 | gitpod-io/gitpod | https://api.github.com/repos/gitpod-io/gitpod | closed | [Code] cannot download large files and folders | type: bug meta: stale editor: code | Trying to download a folder (right click > download) results in something like, no matter what folder I pick:
<img width="538" alt="Screenshot 2021-02-28 at 09 33 29" src="https://user-images.githubusercontent.com/372735/109412392-0a58f200-79a8-11eb-9137-d78d506c7df0.png">
| 1.0 | [Code] cannot download large files and folders - Trying to download a folder (right click > download) results in something like, no matter what folder I pick:
<img width="538" alt="Screenshot 2021-02-28 at 09 33 29" src="https://user-images.githubusercontent.com/372735/109412392-0a58f200-79a8-11eb-9137-d78d506c7df0.png">
| non_priority | cannot download large files and folders trying to download a folder right click download results in something like no matter what folder i pick img width alt screenshot at src | 0 |
278,146 | 30,702,213,239 | IssuesEvent | 2023-07-27 01:11:58 | snykiotcubedev/arangodb-3.7.6 | https://api.github.com/repos/snykiotcubedev/arangodb-3.7.6 | reopened | WS-2021-0152 (High) detected in color-string-1.5.3.tgz | Mend: dependency security vulnerability | ## WS-2021-0152 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>color-string-1.5.3.tgz</b></p></summary>
<p>Parser and generator for CSS color strings</p>
<p>Library home page: <a href="https://registry.npmjs.org/color-string/-/color-string-1.5.3.tgz">https://registry.npmjs.org/color-string/-/color-string-1.5.3.tgz</a></p>
<p>
Dependency Hierarchy:
- optimize-css-assets-webpack-plugin-5.0.1.tgz (Root Library)
- cssnano-4.1.10.tgz
- cssnano-preset-default-4.0.7.tgz
- postcss-colormin-4.0.3.tgz
- color-3.1.2.tgz
- :x: **color-string-1.5.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/snykiotcubedev/arangodb-3.7.6/commit/fce8f85f1c2f070c8e6a8e76d17210a2117d3833">fce8f85f1c2f070c8e6a8e76d17210a2117d3833</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
Regular Expression Denial of Service (ReDoS) was found in color-string before 1.5.5.
<p>Publish Date: 2021-03-12
<p>URL: <a href=https://github.com/Qix-/color-string/commit/0789e21284c33d89ebc4ab4ca6f759b9375ac9d3>WS-2021-0152</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>Release Date: 2021-03-12</p>
<p>Fix Resolution (color-string): 1.5.5</p>
<p>Direct dependency fix Resolution (optimize-css-assets-webpack-plugin): 5.0.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2021-0152 (High) detected in color-string-1.5.3.tgz - ## WS-2021-0152 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>color-string-1.5.3.tgz</b></p></summary>
<p>Parser and generator for CSS color strings</p>
<p>Library home page: <a href="https://registry.npmjs.org/color-string/-/color-string-1.5.3.tgz">https://registry.npmjs.org/color-string/-/color-string-1.5.3.tgz</a></p>
<p>
Dependency Hierarchy:
- optimize-css-assets-webpack-plugin-5.0.1.tgz (Root Library)
- cssnano-4.1.10.tgz
- cssnano-preset-default-4.0.7.tgz
- postcss-colormin-4.0.3.tgz
- color-3.1.2.tgz
- :x: **color-string-1.5.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/snykiotcubedev/arangodb-3.7.6/commit/fce8f85f1c2f070c8e6a8e76d17210a2117d3833">fce8f85f1c2f070c8e6a8e76d17210a2117d3833</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
Regular Expression Denial of Service (ReDoS) was found in color-string before 1.5.5.
<p>Publish Date: 2021-03-12
<p>URL: <a href=https://github.com/Qix-/color-string/commit/0789e21284c33d89ebc4ab4ca6f759b9375ac9d3>WS-2021-0152</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>Release Date: 2021-03-12</p>
<p>Fix Resolution (color-string): 1.5.5</p>
<p>Direct dependency fix Resolution (optimize-css-assets-webpack-plugin): 5.0.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | ws high detected in color string tgz ws high severity vulnerability vulnerable library color string tgz parser and generator for css color strings library home page a href dependency hierarchy optimize css assets webpack plugin tgz root library cssnano tgz cssnano preset default tgz postcss colormin tgz color tgz x color string tgz vulnerable library found in head commit a href found in base branch main vulnerability details regular expression denial of service redos was found in color string before publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version release date fix resolution color string direct dependency fix resolution optimize css assets webpack plugin step up your open source security game with mend | 0 |
105,051 | 22,832,341,291 | IssuesEvent | 2022-07-12 13:55:48 | sourcegraph/sourcegraph | https://api.github.com/repos/sourcegraph/sourcegraph | closed | [Accessibility]: `N/A` hard to understand when read aloud | team/code-intelligence accessibility team/frontend-platform wcag/2.1/fixing wcag/2.1 | ### Audit type
Screen reader navigation
### User journey audit issue
#33516, #33518
### Problem description
<img width="884" alt="n:a" src="https://user-images.githubusercontent.com/103087/167504500-6c228e31-688b-4262-ba26-14d18129ffd1.png">
I couldn't understand the text for `N/A` here.
### Expected behavior
Rename text or add an aria-label that can say `not applicable` or some other long-form version that can be understood.
### Additional details
_No response_
### Assigning labels
- [X] Please give this issue an estimate by applying a label like `estimate/Xd`, where X is the estimated number of days it will take to complete.
- [X] If this issue is specific to a specific Sourcegraph product, please assign the appropriate team label to this issue.
- [X] If this issue will require input from designers in order to complete, please assign the label `needs-design`.
- [X] If you are confident that this issue should be fixed by GitStart, please assign the label `gitstart`.
### Owner
This issue will be fixed by my team, I have assigned a relevant member to it, or I will do so in the near future. | 1.0 | [Accessibility]: `N/A` hard to understand when read aloud - ### Audit type
Screen reader navigation
### User journey audit issue
#33516, #33518
### Problem description
<img width="884" alt="n:a" src="https://user-images.githubusercontent.com/103087/167504500-6c228e31-688b-4262-ba26-14d18129ffd1.png">
I couldn't understand the text for `N/A` here.
### Expected behavior
Rename text or add an aria-label that can say `not applicable` or some other long-form version that can be understood.
### Additional details
_No response_
### Assigning labels
- [X] Please give this issue an estimate by applying a label like `estimate/Xd`, where X is the estimated number of days it will take to complete.
- [X] If this issue is specific to a specific Sourcegraph product, please assign the appropriate team label to this issue.
- [X] If this issue will require input from designers in order to complete, please assign the label `needs-design`.
- [X] If you are confident that this issue should be fixed by GitStart, please assign the label `gitstart`.
### Owner
This issue will be fixed by my team, I have assigned a relevant member to it, or I will do so in the near future. | non_priority | n a hard to understand when read aloud audit type screen reader navigation user journey audit issue problem description img width alt n a src i couldn t understand the text for n a here expected behavior rename text or add an aria label that can say not applicable or some other long form version that can be understood additional details no response assigning labels please give this issue an estimate by applying a label like estimate xd where x is the estimated number of days it will take to complete if this issue is specific to a specific sourcegraph product please assign the appropriate team label to this issue if this issue will require input from designers in order to complete please assign the label needs design if you are confident that this issue should be fixed by gitstart please assign the label gitstart owner this issue will be fixed by my team i have assigned a relevant member to it or i will do so in the near future | 0 |
35,215 | 4,968,848,572 | IssuesEvent | 2016-12-05 11:15:30 | bibbox/sys-bibbox-backend-liferay | https://api.github.com/repos/bibbox/sys-bibbox-backend-liferay | closed | Twice as much LOG lines as defined | bug enhancement Need Testing | The API for getting the latest X lines of an application log ( **BIBBOXDocker-portlet.get-instance-log** ) seems to have a bug where it always **returns twice as many lines as defined**. E.g. 20 lines instead of 10 | 1.0 | Twice as much LOG lines as defined - The API for getting the latest X lines of an application log ( **BIBBOXDocker-portlet.get-instance-log** ) seems to have a bug where it always **returns twice as many lines as defined**. E.g. 20 lines instead of 10 | non_priority | twice as much log lines as defined the api for getting the latest x lines of an application log bibboxdocker portlet get instance log seems to have a bug where it always returns twice as many lines as defined e g lines instead of | 0 |
24,355 | 7,480,396,766 | IssuesEvent | 2018-04-04 17:16:49 | zfsonlinux/zfs | https://api.github.com/repos/zfsonlinux/zfs | closed | Fedora 28: misc bounds check compiler warnings | Build Issue | ### System information
<!-- add version after "|" character -->
Type | Version/Name
--- | ---
Distribution Name | Fedora
Distribution Version | 28
Linux Kernel | 4.16
Architecture | x86-64
ZFS Version | master
SPL Version | master
### Describe the problem you're observing
Building ZFS under Fedora 28 produces a number of bounds check warnings. Fedora 28 comes with GCC 8.0.1.
### Describe how to reproduce the problem
make
### Include any warning/errors/backtraces from the system logs
Some samples:
```
CC lauxlib.lo
In file included from ../../include/sys/zfs_context.h:100,
from ../../module/zfs/zio.c:28:
In function ‘umem_cache_create.constprop’,
inlined from ‘zio_init’ at ../../module/zfs/zio.c:182:23:
../../lib/libspl/include/umem.h:149:3: warning: ‘strncpy’ output may be truncated copying 31 bytes from a string of length 35 [-Wstringop-truncation]
strncpy(cp->cache_name, name, UMEM_CACHE_NAMELEN);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In function ‘umem_cache_create.constprop’,
inlined from ‘zio_init’ at ../../module/zfs/zio.c:186:28:
../../lib/libspl/include/umem.h:149:3: warning: ‘strncpy’ output may be truncated copying 31 bytes from a string of length 35 [-Wstringop-truncation]
strncpy(cp->cache_name, name, UMEM_CACHE_NAMELEN);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CC lbaselib.lo
make[7]: Entering directory '/home/hutter/fedora28/tests/zfs-tests/tests/functional/cli_root/zfs_diff'
CC socket.o
socket.c: In function ‘main’:
socket.c:39:2: warning: ‘strncpy’ specified bound 108 equals destination size [-Wstringop-truncation]
strncpy(sock.sun_path, (char *)path, sizeof (sock.sun_path));
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CCLD socket
make[7]: Leaving directory '/home/hutter/fedora28/tests/zfs-tests/tests/functional/cli_root/zfs_diff'
Making all in zfs_get
make[5]: Entering directory '/home/hutter/fedora28/tests/zfs-tests/cmd/mkbusy'
CC mkbusy.o
mkbusy.c: In function ‘main’:
mkbusy.c:141:10: warning: ‘strncpy’ output truncated before terminating nul copying as many bytes from a string as its length [-Wstringop-truncation]
(void) strncpy(fpath, dname, dlen);
^~~~~~~~~~~~~~~~~~~~~~~~~~~
mkbusy.c:129:10: note: length computed here
dlen = strlen(dname);
^~~~~~~~~~~~~
mkbusy.c:143:10: warning: ‘strncat’ output truncated before terminating nul copying as many bytes from a string as its length [-Wstringop-truncation]
(void) strncat(fpath, fname, flen);
^~~~~~~~~~~~~~~~~~~~~~~~~~~
mkbusy.c:130:10: note: length computed here
flen = strlen(fname);
^~~~~~~~~~~~~
CCLD mkbusy
make[5]: Leaving directory '/home/hutter/fedora28/tests/zfs-tests/cmd/mkbusy'
Making all in zvol_id
make[3]: Entering directory '/home/hutter/fedora28/cmd/zvol_id'
CC zvol_id_main.o
zvol_id_main.c: In function ‘main’:
zvol_id_main.c:92:10: warning: ‘-part’ directive output may be truncated writing 5 bytes into a region of size between 1 and 256 [-Wformat-truncation=]
"%s-part%d", zvol_name, dev_part);
^~~~~
zvol_id_main.c:92:7: note: directive argument in the range [1, 15]
"%s-part%d", zvol_name, dev_part);
^~~~~~~~~~~
zvol_id_main.c:91:3: note: ‘snprintf’ output between 7 and 263 bytes into a destination of size 256
snprintf(zvol_name_part, ZFS_MAX_DATASET_NAME_LEN,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"%s-part%d", zvol_name, dev_part);
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CCLD zvol_id
make[3]: Leaving directory '/home/hutter/fedora28/cmd/zvol_id'
``` | 1.0 | Fedora 28: misc bounds check compiler warnings - ### System information
<!-- add version after "|" character -->
Type | Version/Name
--- | ---
Distribution Name | Fedora
Distribution Version | 28
Linux Kernel | 4.16
Architecture | x86-64
ZFS Version | master
SPL Version | master
### Describe the problem you're observing
Building ZFS under Fedora 28 produces a number of bounds check warnings. Fedora 28 comes with GCC 8.0.1.
### Describe how to reproduce the problem
make
### Include any warning/errors/backtraces from the system logs
Some samples:
```
CC lauxlib.lo
In file included from ../../include/sys/zfs_context.h:100,
from ../../module/zfs/zio.c:28:
In function ‘umem_cache_create.constprop’,
inlined from ‘zio_init’ at ../../module/zfs/zio.c:182:23:
../../lib/libspl/include/umem.h:149:3: warning: ‘strncpy’ output may be truncated copying 31 bytes from a string of length 35 [-Wstringop-truncation]
strncpy(cp->cache_name, name, UMEM_CACHE_NAMELEN);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In function ‘umem_cache_create.constprop’,
inlined from ‘zio_init’ at ../../module/zfs/zio.c:186:28:
../../lib/libspl/include/umem.h:149:3: warning: ‘strncpy’ output may be truncated copying 31 bytes from a string of length 35 [-Wstringop-truncation]
strncpy(cp->cache_name, name, UMEM_CACHE_NAMELEN);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CC lbaselib.lo
make[7]: Entering directory '/home/hutter/fedora28/tests/zfs-tests/tests/functional/cli_root/zfs_diff'
CC socket.o
socket.c: In function ‘main’:
socket.c:39:2: warning: ‘strncpy’ specified bound 108 equals destination size [-Wstringop-truncation]
strncpy(sock.sun_path, (char *)path, sizeof (sock.sun_path));
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CCLD socket
make[7]: Leaving directory '/home/hutter/fedora28/tests/zfs-tests/tests/functional/cli_root/zfs_diff'
Making all in zfs_get
make[5]: Entering directory '/home/hutter/fedora28/tests/zfs-tests/cmd/mkbusy'
CC mkbusy.o
mkbusy.c: In function ‘main’:
mkbusy.c:141:10: warning: ‘strncpy’ output truncated before terminating nul copying as many bytes from a string as its length [-Wstringop-truncation]
(void) strncpy(fpath, dname, dlen);
^~~~~~~~~~~~~~~~~~~~~~~~~~~
mkbusy.c:129:10: note: length computed here
dlen = strlen(dname);
^~~~~~~~~~~~~
mkbusy.c:143:10: warning: ‘strncat’ output truncated before terminating nul copying as many bytes from a string as its length [-Wstringop-truncation]
(void) strncat(fpath, fname, flen);
^~~~~~~~~~~~~~~~~~~~~~~~~~~
mkbusy.c:130:10: note: length computed here
flen = strlen(fname);
^~~~~~~~~~~~~
CCLD mkbusy
make[5]: Leaving directory '/home/hutter/fedora28/tests/zfs-tests/cmd/mkbusy'
Making all in zvol_id
make[3]: Entering directory '/home/hutter/fedora28/cmd/zvol_id'
CC zvol_id_main.o
zvol_id_main.c: In function ‘main’:
zvol_id_main.c:92:10: warning: ‘-part’ directive output may be truncated writing 5 bytes into a region of size between 1 and 256 [-Wformat-truncation=]
"%s-part%d", zvol_name, dev_part);
^~~~~
zvol_id_main.c:92:7: note: directive argument in the range [1, 15]
"%s-part%d", zvol_name, dev_part);
^~~~~~~~~~~
zvol_id_main.c:91:3: note: ‘snprintf’ output between 7 and 263 bytes into a destination of size 256
snprintf(zvol_name_part, ZFS_MAX_DATASET_NAME_LEN,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"%s-part%d", zvol_name, dev_part);
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CCLD zvol_id
make[3]: Leaving directory '/home/hutter/fedora28/cmd/zvol_id'
``` | non_priority | fedora misc bounds check compiler warnings system information type version name distribution name fedora distribution version linux kernel architecture zfs version master spl version master describe the problem you re observing building zfs under fedora produces a number of bounds check warnings fedora comes with gcc describe how to reproduce the problem make include any warning errors backtraces from the system logs some samples cc lauxlib lo in file included from include sys zfs context h from module zfs zio c in function ‘umem cache create constprop’ inlined from ‘zio init’ at module zfs zio c lib libspl include umem h warning ‘strncpy’ output may be truncated copying bytes from a string of length strncpy cp cache name name umem cache namelen in function ‘umem cache create constprop’ inlined from ‘zio init’ at module zfs zio c lib libspl include umem h warning ‘strncpy’ output may be truncated copying bytes from a string of length strncpy cp cache name name umem cache namelen cc lbaselib lo make entering directory home hutter tests zfs tests tests functional cli root zfs diff cc socket o socket c in function ‘main’ socket c warning ‘strncpy’ specified bound equals destination size strncpy sock sun path char path sizeof sock sun path ccld socket make leaving directory home hutter tests zfs tests tests functional cli root zfs diff making all in zfs get make entering directory home hutter tests zfs tests cmd mkbusy cc mkbusy o mkbusy c in function ‘main’ mkbusy c warning ‘strncpy’ output truncated before terminating nul copying as many bytes from a string as its length void strncpy fpath dname dlen mkbusy c note length computed here dlen strlen dname mkbusy c warning ‘strncat’ output truncated before terminating nul copying as many bytes from a string as its length void strncat fpath fname flen mkbusy c note length computed here flen strlen fname ccld mkbusy make leaving directory home hutter tests zfs tests cmd mkbusy making all in zvol id make entering directory home hutter cmd zvol id cc zvol id main o zvol id main c in function ‘main’ zvol id main c warning ‘ part’ directive output may be truncated writing bytes into a region of size between and s part d zvol name dev part zvol id main c note directive argument in the range s part d zvol name dev part zvol id main c note ‘snprintf’ output between and bytes into a destination of size snprintf zvol name part zfs max dataset name len s part d zvol name dev part ccld zvol id make leaving directory home hutter cmd zvol id | 0 |
163,847 | 12,747,491,493 | IssuesEvent | 2020-06-26 18:02:10 | enthought/pyface | https://api.github.com/repos/enthought/pyface | closed | Test Suite is using GuiToolAssistant as a way to check if toolkit is Qt | Testing | While I was working on https://github.com/enthought/pyface/pull/552, I realized skipping the Qt-specific test case using the `skipIf(toolkit_object.toolkit != "qt4", ...)` was not enough, I also had to add a `skipIf(GuiTestAssistant.__name__ == "Unimplemented", ...)`.
This suggests that tests that require Qt, e.g. because the test body contain Qt specific code, are skipped relying on the fact that `GuiTestAssistant` is only implemented for Qt. This is not ideal, because as soon as `GuiTestAssistant` is implemented for other toolkit (e.g. wx, see #266), these tests will be run erroneously, causing build errors.
| 1.0 | Test Suite is using GuiToolAssistant as a way to check if toolkit is Qt - While I was working on https://github.com/enthought/pyface/pull/552, I realized skipping the Qt-specific test case using the `skipIf(toolkit_object.toolkit != "qt4", ...)` was not enough, I also had to add a `skipIf(GuiTestAssistant.__name__ == "Unimplemented", ...)`.
This suggests that tests that require Qt, e.g. because the test body contain Qt specific code, are skipped relying on the fact that `GuiTestAssistant` is only implemented for Qt. This is not ideal, because as soon as `GuiTestAssistant` is implemented for other toolkit (e.g. wx, see #266), these tests will be run erroneously, causing build errors.
| non_priority | test suite is using guitoolassistant as a way to check if toolkit is qt while i was working on i realized skipping the qt specific test case using the skipif toolkit object toolkit was not enough i also had to add a skipif guitestassistant name unimplemented this suggests that tests that require qt e g because the test body contain qt specific code are skipped relying on the fact that guitestassistant is only implemented for qt this is not ideal because as soon as guitestassistant is implemented for other toolkit e g wx see these tests will be run erroneously causing build errors | 0 |
10,903 | 4,107,930,413 | IssuesEvent | 2016-06-06 14:38:14 | vintage-software/vstack-services | https://api.github.com/repos/vintage-software/vstack-services | reopened | using Select on children shows their excluded properties | bug code-cleanup | We should use a ContractResolver and eliminate RestConverter. | 1.0 | using Select on children shows their excluded properties - We should use a ContractResolver and eliminate RestConverter. | non_priority | using select on children shows their excluded properties we should use a contractresolver and eliminate restconverter | 0 |
74,161 | 24,980,345,452 | IssuesEvent | 2022-11-02 11:10:28 | vector-im/element-android | https://api.github.com/repos/vector-im/element-android | closed | Viewing Jitsi participant crashes the app | T-Defect Z-Crash Z-from rageshake A-Jitsi S-Major O-Occasional | Probably since Jitsi 5.0.2, incuded in Element 1.4.10
- Start a Jitsi call and join the conf
- Click on the three dot menu and on "Participants"
The app crashes.
On our side you can maybe disable this menu entry, but I guess the issue has to be fixed on the Jitsi library.
Stacktrace:
```
java.lang.NullPointerException: Attempt to invoke virtual method 'boolean com.facebook.react.uimanager.FabricViewStateManager.hasStateWrapper()' on a null object reference
at com.facebook.react.views.textinput.ReactEditText.updateCachedSpannable(ReactEditText.java:981)
at com.facebook.react.views.textinput.ReactEditText.access$300(ReactEditText.java:75)
at com.facebook.react.views.textinput.ReactEditText$TextWatcherDelegator.onTextChanged(ReactEditText.java:1092)
at android.widget.TextView.sendOnTextChanged(TextView.java:11631)
``` | 1.0 | Viewing Jitsi participant crashes the app - Probably since Jitsi 5.0.2, incuded in Element 1.4.10
- Start a Jitsi call and join the conf
- Click on the three dot menu and on "Participants"
The app crashes.
On our side you can maybe disable this menu entry, but I guess the issue has to be fixed on the Jitsi library.
Stacktrace:
```
java.lang.NullPointerException: Attempt to invoke virtual method 'boolean com.facebook.react.uimanager.FabricViewStateManager.hasStateWrapper()' on a null object reference
at com.facebook.react.views.textinput.ReactEditText.updateCachedSpannable(ReactEditText.java:981)
at com.facebook.react.views.textinput.ReactEditText.access$300(ReactEditText.java:75)
at com.facebook.react.views.textinput.ReactEditText$TextWatcherDelegator.onTextChanged(ReactEditText.java:1092)
at android.widget.TextView.sendOnTextChanged(TextView.java:11631)
``` | non_priority | viewing jitsi participant crashes the app probably since jitsi incuded in element start a jitsi call and join the conf click on the three dot menu and on participants the app crashes on our side you can maybe disable this menu entry but i guess the issue has to be fixed on the jitsi library stacktrace java lang nullpointerexception attempt to invoke virtual method boolean com facebook react uimanager fabricviewstatemanager hasstatewrapper on a null object reference at com facebook react views textinput reactedittext updatecachedspannable reactedittext java at com facebook react views textinput reactedittext access reactedittext java at com facebook react views textinput reactedittext textwatcherdelegator ontextchanged reactedittext java at android widget textview sendontextchanged textview java | 0 |
292,234 | 21,958,472,460 | IssuesEvent | 2022-05-24 14:00:57 | thecodingmachine/workadventure | https://api.github.com/repos/thecodingmachine/workadventure | closed | Missing documentation for "meetingRoomLabel" | documentation | The new "meetingRoomLabel" property (used by the Google Calendar plugin) is currently not documented.
We should probably add some documentation on that property in the "meeting rooms" doc in this repository. | 1.0 | Missing documentation for "meetingRoomLabel" - The new "meetingRoomLabel" property (used by the Google Calendar plugin) is currently not documented.
We should probably add some documentation on that property in the "meeting rooms" doc in this repository. | non_priority | missing documentation for meetingroomlabel the new meetingroomlabel property used by the google calendar plugin is currently not documented we should probably add some documentation on that property in the meeting rooms doc in this repository | 0 |
63,697 | 26,489,047,868 | IssuesEvent | 2023-01-17 20:44:31 | microsoft/vscode-cpptools | https://api.github.com/repos/microsoft/vscode-cpptools | closed | Function inlay hints don't work with std::string_literal arguments | bug Language Service fixed (release pending) Visual Studio Feature: Inlay Hint | Use C++ code
```cpp
#include <string>
using namespace std::string_literals;
void foo_i(int ii);
void foo_s(std::string aa);
int main()
{
foo_i(10); // inlay hints work
foo_s("s"s); // inlay hints don't work
}
```
Bug: Inlay hints don’t work for the function that takes a string_literal argument – with Debug bits several assertions are thrown.
Filed a VS bug at https://developercommunity.visualstudio.com/t/C-IntelliSense-function-inlay-hints-do/10184988 .
| 1.0 | Function inlay hints don't work with std::string_literal arguments - Use C++ code
```cpp
#include <string>
using namespace std::string_literals;
void foo_i(int ii);
void foo_s(std::string aa);
int main()
{
foo_i(10); // inlay hints work
foo_s("s"s); // inlay hints don't work
}
```
Bug: Inlay hints don’t work for the function that takes a string_literal argument – with Debug bits several assertions are thrown.
Filed a VS bug at https://developercommunity.visualstudio.com/t/C-IntelliSense-function-inlay-hints-do/10184988 .
| non_priority | function inlay hints don t work with std string literal arguments use c code cpp include using namespace std string literals void foo i int ii void foo s std string aa int main foo i inlay hints work foo s s s inlay hints don t work bug inlay hints don’t work for the function that takes a string literal argument – with debug bits several assertions are thrown filed a vs bug at | 0 |
142,289 | 21,710,167,933 | IssuesEvent | 2022-05-10 13:17:36 | nextcloud/deck | https://api.github.com/repos/nextcloud/deck | opened | Hard to scroll column on touch screen | bug design | <!--
Thanks for reporting issues back!
Guidelines for submitting issues:
* Please search the existing issues first, it's likely that your issue was already reported or even fixed.
* SECURITY: Report any potential security bug to us via our HackerOne page (https://hackerone.com/nextcloud) following our security policy (https://nextcloud.com/security/) instead of filing an issue in our bug tracker.
* The issues in other components should be reported in their respective repositories: You will find them in our GitHub Organization (https://github.com/nextcloud/)
* You can also use the Issue Template app to prefill most of the required information: https://apps.nextcloud.com/apps/issuetemplate
-->
<!--- Please keep this note for other contributors -->
### How to use GitHub
* Please use the 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to show that you are affected by the same issue.
* Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
* Subscribe to receive notifications on status change and new comments.
**Describe the bug**
Almost impossible to scroll a board column with a touch screen because:
1) either a card is under the cursor and it gets dragged at the same time as the column is scrolled
2) or the whole column is grabbed and moved
3) grabbing the very thin scrollbar doesn't work (Firefox 99.0.1)
**To Reproduce**
Steps to reproduce the behavior:
1. Create a board with two columns
2. Fill the second column with enough cards to make it scroll vertically
3. Using a touch screen, try scrolling up and down
**Expected behavior**
When touching a card and scrolling up down, scroll the viewport.
Only grab the card on long press ?
@jancborchardt
**Screenshots**
**Client details:**
- Browser Firefox
- Version 99.0.1
- Device: Dell XPS 13 laptop with touchscreen, running openSUSE Tumbleweed 20220426
<details>
<summary>Server details</summary>
<!--
You can use the Issue Template application to prefill most of the required information: https://apps.nextcloud.com/apps/issuetemplate
-->
**Nextcloud version:** c.nc.com
| 1.0 | Hard to scroll column on touch screen - <!--
Thanks for reporting issues back!
Guidelines for submitting issues:
* Please search the existing issues first, it's likely that your issue was already reported or even fixed.
* SECURITY: Report any potential security bug to us via our HackerOne page (https://hackerone.com/nextcloud) following our security policy (https://nextcloud.com/security/) instead of filing an issue in our bug tracker.
* The issues in other components should be reported in their respective repositories: You will find them in our GitHub Organization (https://github.com/nextcloud/)
* You can also use the Issue Template app to prefill most of the required information: https://apps.nextcloud.com/apps/issuetemplate
-->
<!--- Please keep this note for other contributors -->
### How to use GitHub
* Please use the 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to show that you are affected by the same issue.
* Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
* Subscribe to receive notifications on status change and new comments.
**Describe the bug**
Almost impossible to scroll a board column with a touch screen because:
1) either a card is under the cursor and it gets dragged at the same time as the column is scrolled
2) or the whole column is grabbed and moved
3) grabbing the very thin scrollbar doesn't work (Firefox 99.0.1)
**To Reproduce**
Steps to reproduce the behavior:
1. Create a board with two columns
2. Fill the second column with enough cards to make it scroll vertically
3. Using a touch screen, try scrolling up and down
**Expected behavior**
When touching a card and scrolling up down, scroll the viewport.
Only grab the card on long press ?
@jancborchardt
**Screenshots**
**Client details:**
- Browser Firefox
- Version 99.0.1
- Device: Dell XPS 13 laptop with touchscreen, running openSUSE Tumbleweed 20220426
<details>
<summary>Server details</summary>
<!--
You can use the Issue Template application to prefill most of the required information: https://apps.nextcloud.com/apps/issuetemplate
-->
**Nextcloud version:** c.nc.com
| non_priority | hard to scroll column on touch screen thanks for reporting issues back guidelines for submitting issues please search the existing issues first it s likely that your issue was already reported or even fixed security report any potential security bug to us via our hackerone page following our security policy instead of filing an issue in our bug tracker the issues in other components should be reported in their respective repositories you will find them in our github organization you can also use the issue template app to prefill most of the required information how to use github please use the 👍 to show that you are affected by the same issue please don t comment if you have no relevant information to add it s just extra noise for everyone subscribed to this issue subscribe to receive notifications on status change and new comments describe the bug almost impossible to scroll a board column with a touch screen because either a card is under the cursor and it gets dragged at the same time as the column is scrolled or the whole column is grabbed and moved grabbing the very thin scrollbar doesn t work firefox to reproduce steps to reproduce the behavior create a board with two columns fill the second column with enough cards to make it scroll vertically using a touch screen try scrolling up and down expected behavior when touching a card and scrolling up down scroll the viewport only grab the card on long press jancborchardt screenshots client details browser firefox version device dell xps laptop with touchscreen running opensuse tumbleweed server details you can use the issue template application to prefill most of the required information nextcloud version c nc com | 0 |
13,972 | 4,794,094,047 | IssuesEvent | 2016-10-31 20:01:44 | dotnet/coreclr | https://api.github.com/repos/dotnet/coreclr | opened | JIT: opportunities for improving async state machine codegen | CodeGen optimization | There are some idiomatic patterns in the async state machines created by the C# compiler that cause the jit to generate sub-optimal code.
A motivating example is the method `<RequestProcessingAsync>d__2[Context][Microsoft.AspNetCore.Hosting.Internal.HostingApplication+Context]:MoveNext():this` from Kestrel ([source code](https://github.com/aspnet/KestrelHttpServer/blob/dev/src/Microsoft.AspNetCore.Server.Kestrel/Internal/Http/FrameOfT.cs#L30)).
- The `MoveNext` method is a value class method that holds a pointer to the associated `Frame` class. Frame field references in `MoveNext` thus must go through one extra level of indirection. The JIT also spills the `this` pointer in `MoveNext`, leading to code sequences like the following:
```asm
G_M55243_IG09:
488B5510 mov rdx, bword ptr [rbp+10H] // RDX=this
488B12 mov rdx, gword ptr [rdx] // RDX=this.<>4__this (frame)
8B0A mov ecx, dword ptr [rdx] // null check (?)
488B4A58 mov rcx, gword ptr [rdx+88] // RCX = this.<>_this.somefield
488B5510 mov rdx, bword ptr [rbp+10H] // RDX = this
488B12 mov rdx, gword ptr [rdx] // RDX = this.<>4_this (frame)
488B9290010000 mov rdx, qword ptr [rdx+400]
488B4920 mov rcx, gword ptr [rcx+32]
```
The jit should be able to CSE some of these redundant loads. See #7903 for a small repro case. The C# compiler could help the jit by caching `<>4__this` in a local, and perhaps by inserting an early null check.
- The method is (roughly speaking) an outermost switch. Such methods can incur relatively high prolog costs from zero initializations in the prolog, and this method is a good example:
```asm
488DBD58FFFFFF lea rdi, [rbp-A8H]
B922000000 mov ecx, 34
33C0 xor rax, rax
F3AB rep stosd
```
Most of the zeroing comes from structs with GC references. Possible mitigation routes: more aggressive copy (and reverse-copy) prop of structs, tracking struct field lifetimes, or stack packing.
- Code layout: because this method has EH, cold code cannot be aggressively moved to the end of the method. It could however be moved to the end of the enclosing try regions. For instance, right after the first switch in the method there are a couple of throw blocks:
```asm
G_M55243_IG03:
....
FFE1 jmp rcx
G_M55243_IG04:
488BD3 mov rdx, rbx
48B92885A3C6FF7F0000 mov rcx, 0x7FFFC6A38528
E83E47B35E call CORINFO_HELP_ISINSTANCEOFCLASS
4885C0 test rax, rax
7508 jne SHORT G_M55243_IG05
488BCB mov rcx, rbx
E8A12FCE5E call CORINFO_HELP_THROW
G_M55243_IG05:
488BC8 mov rcx, rax
E84932505E call System.Runtime.ExceptionServices.ExceptionDispatchInfo:Capture(ref):ref
488BC8 mov rcx, rax
3909 cmp dword ptr [rcx], ecx
E88F32505E call System.Runtime.ExceptionServices.ExceptionDispatchInfo:Throw():this
```
- Inlining: there are some examples here where an `ALWAYS_INLINE` case pulls in a call to a method with an aggressive inlining attribute. We might want to reconsider such cases and force the profitability heuristics to kick in instead. For example:
```
[42 IL=0919 TR=001193 06001E56] [below ALWAYS_INLINE size] ConfiguredTaskAwaiter:GetResult():this
[43 IL=0006 TR=002148 06001E94] [below ALWAYS_INLINE size] System.Runtime.CompilerServices.TaskAwaiter:ValidateEnd(ref)
[44 IL=0001 TR=002154 06002271] [aggressive inline attribute] System.Threading.Tasks.Task:get_IsWaitNotificationEnabledOrNotRanToCompletion():bool:this
```
- Switch codegen: there are some degenerate switch cases that would be better expressed as if/then ladders. It would probably be worth surveying other async methods to see if this is a common occurence. For example:
```
IL_0008: switch (
IL_003b,
IL_003b,
IL_003b,
IL_003b,
IL_003b,
IL_003b,
IL_003b,
IL_0729)
```
Here there are only 3 targets and there's no interleaving.
More detailed notes and various jit artifacts can be found [on this gist](https://gist.github.com/AndyAyersMS/c3cee7b33a2967d2a31428eca40f4bdf). | 1.0 | JIT: opportunities for improving async state machine codegen - There are some idiomatic patterns in the async state machines created by the C# compiler that cause the jit to generate sub-optimal code.
A motivating example is the method `<RequestProcessingAsync>d__2[Context][Microsoft.AspNetCore.Hosting.Internal.HostingApplication+Context]:MoveNext():this` from Kestrel ([source code](https://github.com/aspnet/KestrelHttpServer/blob/dev/src/Microsoft.AspNetCore.Server.Kestrel/Internal/Http/FrameOfT.cs#L30)).
- The `MoveNext` method is a value class method that holds a pointer to the associated `Frame` class. Frame field references in `MoveNext` thus must go through one extra level of indirection. The JIT also spills the `this` pointer in `MoveNext`, leading to code sequences like the following:
```asm
G_M55243_IG09:
488B5510 mov rdx, bword ptr [rbp+10H] // RDX=this
488B12 mov rdx, gword ptr [rdx] // RDX=this.<>4__this (frame)
8B0A mov ecx, dword ptr [rdx] // null check (?)
488B4A58 mov rcx, gword ptr [rdx+88] // RCX = this.<>_this.somefield
488B5510 mov rdx, bword ptr [rbp+10H] // RDX = this
488B12 mov rdx, gword ptr [rdx] // RDX = this.<>4_this (frame)
488B9290010000 mov rdx, qword ptr [rdx+400]
488B4920 mov rcx, gword ptr [rcx+32]
```
The jit should be able to CSE some of these redundant loads. See #7903 for a small repro case. The C# compiler could help the jit by caching `<>4__this` in a local, and perhaps by inserting an early null check.
- The method is (roughly speaking) an outermost switch. Such methods can incur relatively high prolog costs from zero initializations in the prolog, and this method is a good example:
```asm
488DBD58FFFFFF lea rdi, [rbp-A8H]
B922000000 mov ecx, 34
33C0 xor rax, rax
F3AB rep stosd
```
Most of the zeroing comes from structs with GC references. Possible mitigation routes: more aggressive copy (and reverse-copy) prop of structs, tracking struct field lifetimes, or stack packing.
- Code layout: because this method has EH, cold code cannot be aggressively moved to the end of the method. It could however be moved to the end of the enclosing try regions. For instance, right after the first switch in the method there are a couple of throw blocks:
```asm
G_M55243_IG03:
....
FFE1 jmp rcx
G_M55243_IG04:
488BD3 mov rdx, rbx
48B92885A3C6FF7F0000 mov rcx, 0x7FFFC6A38528
E83E47B35E call CORINFO_HELP_ISINSTANCEOFCLASS
4885C0 test rax, rax
7508 jne SHORT G_M55243_IG05
488BCB mov rcx, rbx
E8A12FCE5E call CORINFO_HELP_THROW
G_M55243_IG05:
488BC8 mov rcx, rax
E84932505E call System.Runtime.ExceptionServices.ExceptionDispatchInfo:Capture(ref):ref
488BC8 mov rcx, rax
3909 cmp dword ptr [rcx], ecx
E88F32505E call System.Runtime.ExceptionServices.ExceptionDispatchInfo:Throw():this
```
- Inlining: there are some examples here where an `ALWAYS_INLINE` case pulls in a call to a method with an aggressive inlining attribute. We might want to reconsider such cases and force the profitability heuristics to kick in instead. For example:
```
[42 IL=0919 TR=001193 06001E56] [below ALWAYS_INLINE size] ConfiguredTaskAwaiter:GetResult():this
[43 IL=0006 TR=002148 06001E94] [below ALWAYS_INLINE size] System.Runtime.CompilerServices.TaskAwaiter:ValidateEnd(ref)
[44 IL=0001 TR=002154 06002271] [aggressive inline attribute] System.Threading.Tasks.Task:get_IsWaitNotificationEnabledOrNotRanToCompletion():bool:this
```
- Switch codegen: there are some degenerate switch cases that would be better expressed as if/then ladders. It would probably be worth surveying other async methods to see if this is a common occurence. For example:
```
IL_0008: switch (
IL_003b,
IL_003b,
IL_003b,
IL_003b,
IL_003b,
IL_003b,
IL_003b,
IL_0729)
```
Here there are only 3 targets and there's no interleaving.
More detailed notes and various jit artifacts can be found [on this gist](https://gist.github.com/AndyAyersMS/c3cee7b33a2967d2a31428eca40f4bdf). | non_priority | jit opportunities for improving async state machine codegen there are some idiomatic patterns in the async state machines created by the c compiler that cause the jit to generate sub optimal code a motivating example is the method d movenext this from kestrel the movenext method is a value class method that holds a pointer to the associated frame class frame field references in movenext thus must go through one extra level of indirection the jit also spills the this pointer in movenext leading to code sequences like the following asm g mov rdx bword ptr rdx this mov rdx gword ptr rdx this this frame mov ecx dword ptr null check mov rcx gword ptr rcx this this somefield mov rdx bword ptr rdx this mov rdx gword ptr rdx this this frame mov rdx qword ptr mov rcx gword ptr the jit should be able to cse some of these redundant loads see for a small repro case the c compiler could help the jit by caching this in a local and perhaps by inserting an early null check the method is roughly speaking an outermost switch such methods can incur relatively high prolog costs from zero initializations in the prolog and this method is a good example asm lea rdi mov ecx xor rax rax rep stosd most of the zeroing comes from structs with gc references possible mitigation routes more aggressive copy and reverse copy prop of structs tracking struct field lifetimes or stack packing code layout because this method has eh cold code cannot be aggressively moved to the end of the method it could however be moved to the end of the enclosing try regions for instance right after the first switch in the method there are a couple of throw blocks asm g jmp rcx g mov rdx rbx mov rcx call corinfo help isinstanceofclass test rax rax jne short g mov rcx rbx call corinfo help throw g mov rcx rax call system runtime exceptionservices exceptiondispatchinfo capture ref ref mov rcx rax cmp dword ptr ecx call system runtime exceptionservices exceptiondispatchinfo throw this inlining there are some examples here where an always inline case pulls in a call to a method with an aggressive inlining attribute we might want to reconsider such cases and force the profitability heuristics to kick in instead for example configuredtaskawaiter getresult this system runtime compilerservices taskawaiter validateend ref system threading tasks task get iswaitnotificationenabledornotrantocompletion bool this switch codegen there are some degenerate switch cases that would be better expressed as if then ladders it would probably be worth surveying other async methods to see if this is a common occurence for example il switch il il il il il il il il here there are only targets and there s no interleaving more detailed notes and various jit artifacts can be found | 0 |
80,780 | 23,303,328,915 | IssuesEvent | 2022-08-07 16:54:09 | SpacingBat3/WebCord | https://api.github.com/repos/SpacingBat3/WebCord | closed | Namespace 'NodeJS' has no exported member 'Architecture' | build | ### Acknowledgements ###
- [x] There's no other issue describing the same problem, regardless of its current state (i.e. including both closed and open issues).\*
- [x] There's no fix for my issue released to `master` branch.\*
- [ ] This issue has known workaround (write it below).
<sub>* Required</sub>
### Environment ###
<!--
Make sure you have entered details below to make it clean
what is your current environment
-->
- Platform: Arch Linux
- Architecture: `x86_64`
- Electron version: `v19.0.10`
- Application version: `v3.6.0`
- TypeScript compiler version: `4.7.4`
- Node.js package manager: `npm`
- Node.js package manger version: `8.15.1`
### Describe the problem ###
```
==> Starting build()...
sources/code/common/modules/agent.ts:8:26 - error TS2694: Namespace 'NodeJS' has no exported member 'Architecture'.
8 switch (arch as NodeJS.Architecture) {
~~~~~~~~~~~~
Found 1 error in sources/code/common/modules/agent.ts:8
==> ERROR: A failure occurred in build().
Aborting...
```
### To Reproduce ###
Steps to reproduce the behavior:
1. Clone `https://aur.archlinux.org/webcord.git` to a clean directory like `/tmp`
2. Change `pkgver` to `3.6.0`
3. Run `updpkgsums` to update checksums
4. Run `makepkg -fs`
### Expected behavior ###
No errors during build
### Screenshots ###
n/a
### Additional context ###
Change that causes this error was added in 5cd84c4a09159e15ef6eda261baaf8741da7437e; I don't really use nodejs and didn't investigate further
<!--
### Workarounds ###
Write any alternative method/s that can be reproduced to fix this issue until it will be fixed in code and/or releases.
--> | 1.0 | Namespace 'NodeJS' has no exported member 'Architecture' - ### Acknowledgements ###
- [x] There's no other issue describing the same problem, regardless of its current state (i.e. including both closed and open issues).\*
- [x] There's no fix for my issue released to `master` branch.\*
- [ ] This issue has known workaround (write it below).
<sub>* Required</sub>
### Environment ###
<!--
Make sure you have entered details below to make it clean
what is your current environment
-->
- Platform: Arch Linux
- Architecture: `x86_64`
- Electron version: `v19.0.10`
- Application version: `v3.6.0`
- TypeScript compiler version: `4.7.4`
- Node.js package manager: `npm`
- Node.js package manger version: `8.15.1`
### Describe the problem ###
```
==> Starting build()...
sources/code/common/modules/agent.ts:8:26 - error TS2694: Namespace 'NodeJS' has no exported member 'Architecture'.
8 switch (arch as NodeJS.Architecture) {
~~~~~~~~~~~~
Found 1 error in sources/code/common/modules/agent.ts:8
==> ERROR: A failure occurred in build().
Aborting...
```
### To Reproduce ###
Steps to reproduce the behavior:
1. Clone `https://aur.archlinux.org/webcord.git` to a clean directory like `/tmp`
2. Change `pkgver` to `3.6.0`
3. Run `updpkgsums` to update checksums
4. Run `makepkg -fs`
### Expected behavior ###
No errors during build
### Screenshots ###
n/a
### Additional context ###
Change that causes this error was added in 5cd84c4a09159e15ef6eda261baaf8741da7437e; I don't really use nodejs and didn't investigate further
<!--
### Workarounds ###
Write any alternative method/s that can be reproduced to fix this issue until it will be fixed in code and/or releases.
--> | non_priority | namespace nodejs has no exported member architecture acknowledgements there s no other issue describing the same problem regardless of its current state i e including both closed and open issues there s no fix for my issue released to master branch this issue has known workaround write it below required environment make sure you have entered details below to make it clean what is your current environment platform arch linux architecture electron version application version typescript compiler version node js package manager npm node js package manger version describe the problem starting build sources code common modules agent ts error namespace nodejs has no exported member architecture switch arch as nodejs architecture found error in sources code common modules agent ts error a failure occurred in build aborting to reproduce steps to reproduce the behavior clone to a clean directory like tmp change pkgver to run updpkgsums to update checksums run makepkg fs expected behavior no errors during build screenshots n a additional context change that causes this error was added in i don t really use nodejs and didn t investigate further workarounds write any alternative method s that can be reproduced to fix this issue until it will be fixed in code and or releases | 0 |
298,380 | 22,494,816,136 | IssuesEvent | 2022-06-23 06:30:02 | project-chip/connectedhomeip | https://api.github.com/repos/project-chip/connectedhomeip | closed | Need to display the QR code using the Github pages of CHIP repository | documentation enhancement p3 V1.X future | #### Problem
With PR #3242 we have added the support of displaying the QR code on a webpage. This will be helpful for devices that do not have a physical display (to scan/print the QR code). Currently, the page is under the Github pages of my personal Github fork. We need to move this to CHIP repository.
#### Proposed Solution
I think, the CHIP maintainers should enable Github pages (gh-pages) for the CHIP repository. Once that is done, we can merge the changes through a PR. | 1.0 | Need to display the QR code using the Github pages of CHIP repository - #### Problem
With PR #3242 we have added the support of displaying the QR code on a webpage. This will be helpful for devices that do not have a physical display (to scan/print the QR code). Currently, the page is under the Github pages of my personal Github fork. We need to move this to CHIP repository.
#### Proposed Solution
I think, the CHIP maintainers should enable Github pages (gh-pages) for the CHIP repository. Once that is done, we can merge the changes through a PR. | non_priority | need to display the qr code using the github pages of chip repository problem with pr we have added the support of displaying the qr code on a webpage this will be helpful for devices that do not have a physical display to scan print the qr code currently the page is under the github pages of my personal github fork we need to move this to chip repository proposed solution i think the chip maintainers should enable github pages gh pages for the chip repository once that is done we can merge the changes through a pr | 0 |
191,191 | 14,593,461,466 | IssuesEvent | 2020-12-19 22:58:31 | github-vet/rangeloop-pointer-findings | https://api.github.com/repos/github-vet/rangeloop-pointer-findings | closed | rkand4/vuejs: pkg/http/listener_test.go; 50 LoC | fresh small test |
Found a possible issue in [rkand4/vuejs](https://www.github.com/rkand4/vuejs) at [pkg/http/listener_test.go](https://github.com/rkand4/vuejs/blob/e790bf122760e516384839f20608d7b79b1d344a/pkg/http/listener_test.go#L567-L616)
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.
> range-loop variable i used in defer or goroutine at line 595
[Click here to see the code in its original context.](https://github.com/rkand4/vuejs/blob/e790bf122760e516384839f20608d7b79b1d344a/pkg/http/listener_test.go#L567-L616)
<details>
<summary>Click here to show the 50 line(s) of Go which triggered the analyzer.</summary>
```go
for i, testCase := range testCases {
listener, err := newHTTPListener(
testCase.serverAddrs,
testCase.tlsConfig,
time.Duration(0),
time.Duration(0),
time.Duration(0),
nil,
nil,
errorFunc,
)
if err != nil {
t.Fatalf("Test %d: error: expected = <nil>, got = %v", i+1, err)
}
for _, serverAddr := range testCase.serverAddrs {
conn, err := net.Dial("tcp", serverAddr)
if err != nil {
t.Fatalf("Test %d: error: expected = <nil>, got = %v", i+1, err)
}
if _, err = io.WriteString(conn, testCase.request); err != nil {
t.Fatalf("Test %d: request send: expected = <nil>, got = %v", i+1, err)
}
go func() {
serverConn, aerr := listener.Accept()
if aerr == nil {
t.Fatalf("Test %d: accept: expected = <error>, got = <nil>", i+1)
}
if serverConn != nil {
t.Fatalf("Test %d: accept: server expected = <nil>, got = %v", i+1, serverConn)
}
}()
buf := make([]byte, len(sslRequiredErrMsg))
n, err := io.ReadFull(conn, buf)
if err != nil {
t.Fatalf("Test %d: reply read: expected = <nil> got = %v", i+1, err)
} else if n != len(buf) {
t.Fatalf("Test %d: reply length: expected = %v got = %v", i+1, len(buf), n)
} else if !bytes.Equal(buf, sslRequiredErrMsg) {
t.Fatalf("Test %d: reply: expected = %v got = %v", i+1, string(sslRequiredErrMsg), string(buf))
}
conn.Close()
}
listener.Close()
}
```
</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: e790bf122760e516384839f20608d7b79b1d344a
| 1.0 | rkand4/vuejs: pkg/http/listener_test.go; 50 LoC -
Found a possible issue in [rkand4/vuejs](https://www.github.com/rkand4/vuejs) at [pkg/http/listener_test.go](https://github.com/rkand4/vuejs/blob/e790bf122760e516384839f20608d7b79b1d344a/pkg/http/listener_test.go#L567-L616)
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.
> range-loop variable i used in defer or goroutine at line 595
[Click here to see the code in its original context.](https://github.com/rkand4/vuejs/blob/e790bf122760e516384839f20608d7b79b1d344a/pkg/http/listener_test.go#L567-L616)
<details>
<summary>Click here to show the 50 line(s) of Go which triggered the analyzer.</summary>
```go
for i, testCase := range testCases {
listener, err := newHTTPListener(
testCase.serverAddrs,
testCase.tlsConfig,
time.Duration(0),
time.Duration(0),
time.Duration(0),
nil,
nil,
errorFunc,
)
if err != nil {
t.Fatalf("Test %d: error: expected = <nil>, got = %v", i+1, err)
}
for _, serverAddr := range testCase.serverAddrs {
conn, err := net.Dial("tcp", serverAddr)
if err != nil {
t.Fatalf("Test %d: error: expected = <nil>, got = %v", i+1, err)
}
if _, err = io.WriteString(conn, testCase.request); err != nil {
t.Fatalf("Test %d: request send: expected = <nil>, got = %v", i+1, err)
}
go func() {
serverConn, aerr := listener.Accept()
if aerr == nil {
t.Fatalf("Test %d: accept: expected = <error>, got = <nil>", i+1)
}
if serverConn != nil {
t.Fatalf("Test %d: accept: server expected = <nil>, got = %v", i+1, serverConn)
}
}()
buf := make([]byte, len(sslRequiredErrMsg))
n, err := io.ReadFull(conn, buf)
if err != nil {
t.Fatalf("Test %d: reply read: expected = <nil> got = %v", i+1, err)
} else if n != len(buf) {
t.Fatalf("Test %d: reply length: expected = %v got = %v", i+1, len(buf), n)
} else if !bytes.Equal(buf, sslRequiredErrMsg) {
t.Fatalf("Test %d: reply: expected = %v got = %v", i+1, string(sslRequiredErrMsg), string(buf))
}
conn.Close()
}
listener.Close()
}
```
</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: e790bf122760e516384839f20608d7b79b1d344a
| non_priority | vuejs pkg http listener 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 range loop variable i used in defer or goroutine at line click here to show the line s of go which triggered the analyzer go for i testcase range testcases listener err newhttplistener testcase serveraddrs testcase tlsconfig time duration time duration time duration nil nil errorfunc if err nil t fatalf test d error expected got v i err for serveraddr range testcase serveraddrs conn err net dial tcp serveraddr if err nil t fatalf test d error expected got v i err if err io writestring conn testcase request err nil t fatalf test d request send expected got v i err go func serverconn aerr listener accept if aerr nil t fatalf test d accept expected got i if serverconn nil t fatalf test d accept server expected got v i serverconn buf make byte len sslrequirederrmsg n err io readfull conn buf if err nil t fatalf test d reply read expected got v i err else if n len buf t fatalf test d reply length expected v got v i len buf n else if bytes equal buf sslrequirederrmsg t fatalf test d reply expected v got v i string sslrequirederrmsg string buf conn close listener close 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 | 0 |
442,889 | 30,862,152,927 | IssuesEvent | 2023-08-03 04:40:41 | Tinkoff/kora | https://api.github.com/repos/Tinkoff/kora | opened | Kora documentation update | documentation | Rewrite most of existing Kora documentation with up-to-date examples, features to Russian | 1.0 | Kora documentation update - Rewrite most of existing Kora documentation with up-to-date examples, features to Russian | non_priority | kora documentation update rewrite most of existing kora documentation with up to date examples features to russian | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.