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 1k | labels stringlengths 4 1.38k | body stringlengths 1 262k | index stringclasses 16
values | text_combine stringlengths 96 262k | label stringclasses 2
values | text stringlengths 96 252k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
410,851 | 12,002,809,334 | IssuesEvent | 2020-04-09 08:28:16 | OrangeJuice7/SDL-OpenGL-Game-Framework | https://api.github.com/repos/OrangeJuice7/SDL-OpenGL-Game-Framework | closed | Fix inter-entity collision resolution | area.Model priority.medium work.low | Current collision resolution pushes entities apart with a force proportionate to the depth of penetration between the two entities. This penetration may be large if at least one of the entities travels a large distance in one frame (either due to high velocity or low frame rate), resulting in inconsistent physics.
Force should be based on a transfer of momentum/velocity instead.
Ideally, the point of collision should be determined as well, but this might create complications in multi-entity collisions. | 1.0 | Fix inter-entity collision resolution - Current collision resolution pushes entities apart with a force proportionate to the depth of penetration between the two entities. This penetration may be large if at least one of the entities travels a large distance in one frame (either due to high velocity or low frame rate), resulting in inconsistent physics.
Force should be based on a transfer of momentum/velocity instead.
Ideally, the point of collision should be determined as well, but this might create complications in multi-entity collisions. | priority | fix inter entity collision resolution current collision resolution pushes entities apart with a force proportionate to the depth of penetration between the two entities this penetration may be large if at least one of the entities travels a large distance in one frame either due to high velocity or low frame rate resulting in inconsistent physics force should be based on a transfer of momentum velocity instead ideally the point of collision should be determined as well but this might create complications in multi entity collisions | 1 |
66,470 | 14,784,546,584 | IssuesEvent | 2021-01-12 00:27:43 | BryanLaura/Google-api-python-client | https://api.github.com/repos/BryanLaura/Google-api-python-client | closed | WS-2020-0208 (Medium) detected in highlight.js-10.3.1.tgz - autoclosed | security vulnerability | ## WS-2020-0208 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>highlight.js-10.3.1.tgz</b></p></summary>
<p>Syntax highlighting with language autodetection.</p>
<p>Library home page: <a href="https://registry.npmjs.org/highlight.js/-/highlight.js-10.3.1.tgz">https://registry.npmjs.org/highlight.js/-/highlight.js-10.3.1.tgz</a></p>
<p>Path to dependency file: Google-api-python-client/package.json</p>
<p>Path to vulnerable library: Google-api-python-client/node_modules/highlight.js/package.json</p>
<p>
Dependency Hierarchy:
- render-content-5.2.0.tgz (Root Library)
- hubdown-2.6.0.tgz
- rehype-highlight-3.1.0.tgz
- lowlight-1.16.0.tgz
- :x: **highlight.js-10.3.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/BryanLaura/Google-api-python-client/commit/4e6b7ecb9b39fc7d86c420ddb87c5c3712578339">4e6b7ecb9b39fc7d86c420ddb87c5c3712578339</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
If are you are using Highlight.js to highlight user-provided data you are possibly vulnerable. On the client-side (in a browser or Electron environment) risks could include lengthy freezes or crashes... On the server-side infinite freezes could occur... effectively preventing users from accessing your app or service (ie, Denial of Service). This is an issue with grammars shipped with the parser (and potentially 3rd party grammars also), not the parser itself. If you are using Highlight.js with any of the following grammars you are vulnerable. If you are using highlightAuto to detect the language (and have any of these grammars registered) you are vulnerable.
<p>Publish Date: 2020-12-04
<p>URL: <a href=https://github.com/highlightjs/highlight.js/commit/373b9d862401162e832ce77305e49b859e110f9c>WS-2020-0208</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: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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/highlightjs/highlight.js/tree/10.4.1">https://github.com/highlightjs/highlight.js/tree/10.4.1</a></p>
<p>Release Date: 2020-12-04</p>
<p>Fix Resolution: 10.4.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-0208 (Medium) detected in highlight.js-10.3.1.tgz - autoclosed - ## WS-2020-0208 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>highlight.js-10.3.1.tgz</b></p></summary>
<p>Syntax highlighting with language autodetection.</p>
<p>Library home page: <a href="https://registry.npmjs.org/highlight.js/-/highlight.js-10.3.1.tgz">https://registry.npmjs.org/highlight.js/-/highlight.js-10.3.1.tgz</a></p>
<p>Path to dependency file: Google-api-python-client/package.json</p>
<p>Path to vulnerable library: Google-api-python-client/node_modules/highlight.js/package.json</p>
<p>
Dependency Hierarchy:
- render-content-5.2.0.tgz (Root Library)
- hubdown-2.6.0.tgz
- rehype-highlight-3.1.0.tgz
- lowlight-1.16.0.tgz
- :x: **highlight.js-10.3.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/BryanLaura/Google-api-python-client/commit/4e6b7ecb9b39fc7d86c420ddb87c5c3712578339">4e6b7ecb9b39fc7d86c420ddb87c5c3712578339</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
If are you are using Highlight.js to highlight user-provided data you are possibly vulnerable. On the client-side (in a browser or Electron environment) risks could include lengthy freezes or crashes... On the server-side infinite freezes could occur... effectively preventing users from accessing your app or service (ie, Denial of Service). This is an issue with grammars shipped with the parser (and potentially 3rd party grammars also), not the parser itself. If you are using Highlight.js with any of the following grammars you are vulnerable. If you are using highlightAuto to detect the language (and have any of these grammars registered) you are vulnerable.
<p>Publish Date: 2020-12-04
<p>URL: <a href=https://github.com/highlightjs/highlight.js/commit/373b9d862401162e832ce77305e49b859e110f9c>WS-2020-0208</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: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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/highlightjs/highlight.js/tree/10.4.1">https://github.com/highlightjs/highlight.js/tree/10.4.1</a></p>
<p>Release Date: 2020-12-04</p>
<p>Fix Resolution: 10.4.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 highlight js tgz autoclosed ws medium severity vulnerability vulnerable library highlight js tgz syntax highlighting with language autodetection library home page a href path to dependency file google api python client package json path to vulnerable library google api python client node modules highlight js package json dependency hierarchy render content tgz root library hubdown tgz rehype highlight tgz lowlight tgz x highlight js tgz vulnerable library found in head commit a href found in base branch main vulnerability details if are you are using highlight js to highlight user provided data you are possibly vulnerable on the client side in a browser or electron environment risks could include lengthy freezes or crashes on the server side infinite freezes could occur effectively preventing users from accessing your app or service ie denial of service this is an issue with grammars shipped with the parser and potentially party grammars also not the parser itself if you are using highlight js with any of the following grammars you are vulnerable if you are using highlightauto to detect the language and have any of these grammars registered you are vulnerable publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
32,173 | 12,093,612,099 | IssuesEvent | 2020-04-19 20:20:42 | AOSC-Dev/aosc-os-abbs | https://api.github.com/repos/AOSC-Dev/aosc-os-abbs | closed | bind: security update to 9.12.4-P1 | security to-stable upgrade | <!-- Please remove items do not apply. -->
**CVE IDs:** CVE-2018-5743, CVE-2019-6467
**Other security advisory IDs:** USN-3956-1
**Descriptions:**
CVE-2018-5743: Limiting simultaneous TCP clients is ineffective
https://kb.isc.org/docs/cve-2018-5743
CVE-2019-6467: An error in the nxdomain redirect feature can cause
BIND to exit with an INSIST assertion failure in query.c
https://kb.isc.org/docs/cve-2019-6467
**Architectural progress:**
<!-- Please remove any architecture to which the security vulnerabilities do not apply. -->
- [x] AMD64 `amd64`
- [ ] AArch64 `arm64`
- [ ] ARMv7 `armel`
- [ ] PowerPC 64-bit BE `ppc64`
| True | bind: security update to 9.12.4-P1 - <!-- Please remove items do not apply. -->
**CVE IDs:** CVE-2018-5743, CVE-2019-6467
**Other security advisory IDs:** USN-3956-1
**Descriptions:**
CVE-2018-5743: Limiting simultaneous TCP clients is ineffective
https://kb.isc.org/docs/cve-2018-5743
CVE-2019-6467: An error in the nxdomain redirect feature can cause
BIND to exit with an INSIST assertion failure in query.c
https://kb.isc.org/docs/cve-2019-6467
**Architectural progress:**
<!-- Please remove any architecture to which the security vulnerabilities do not apply. -->
- [x] AMD64 `amd64`
- [ ] AArch64 `arm64`
- [ ] ARMv7 `armel`
- [ ] PowerPC 64-bit BE `ppc64`
| non_priority | bind security update to cve ids cve cve other security advisory ids usn descriptions cve limiting simultaneous tcp clients is ineffective cve an error in the nxdomain redirect feature can cause bind to exit with an insist assertion failure in query c architectural progress armel powerpc bit be | 0 |
655,752 | 21,707,697,349 | IssuesEvent | 2022-05-10 11:10:01 | ugent-library/biblio-backend | https://api.github.com/repos/ugent-library/biblio-backend | closed | license after embargo period cannot be added | enhancement publications priority_pilotgroup | **Describe the improvement**
When access level of a publication is set to UGent access or private access, the license field to select a CC license is not shown. Consequently, in case of embargo, if the access level is open after the embargo period, the user cannot select a CC license (but only "Other license").
When "Access level after embargo" is set to "Open access", the license field (for CC licenses) should appear.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
 | 1.0 | license after embargo period cannot be added - **Describe the improvement**
When access level of a publication is set to UGent access or private access, the license field to select a CC license is not shown. Consequently, in case of embargo, if the access level is open after the embargo period, the user cannot select a CC license (but only "Other license").
When "Access level after embargo" is set to "Open access", the license field (for CC licenses) should appear.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
 | priority | license after embargo period cannot be added describe the improvement when access level of a publication is set to ugent access or private access the license field to select a cc license is not shown consequently in case of embargo if the access level is open after the embargo period the user cannot select a cc license but only other license when access level after embargo is set to open access the license field for cc licenses should appear screenshots if applicable add screenshots to help explain your problem desktop please complete the following information | 1 |
130,903 | 27,787,198,967 | IssuesEvent | 2023-03-17 05:05:35 | MarkBind/markbind | https://api.github.com/repos/MarkBind/markbind | closed | Consider creating unified types for common variables | a-CodeQuality s.UnderDiscussion | As we continue with the TypeScript migration (#1913), we may want to create unified types to be used across common method arguments. One example could be creating a `Node` type that is used throughout different methods/classes when the `node` parameter is passed around.
We'll need to decide:
- When we want to do it — after we have fully migrated, or while the migration is currently underway, or if we even want to standardise these types at all
- What the types should be (e.g. for Node, `cheerio.Element & DomElement` could be an option)
- How to handle applying types across the whole codebase | 1.0 | Consider creating unified types for common variables - As we continue with the TypeScript migration (#1913), we may want to create unified types to be used across common method arguments. One example could be creating a `Node` type that is used throughout different methods/classes when the `node` parameter is passed around.
We'll need to decide:
- When we want to do it — after we have fully migrated, or while the migration is currently underway, or if we even want to standardise these types at all
- What the types should be (e.g. for Node, `cheerio.Element & DomElement` could be an option)
- How to handle applying types across the whole codebase | non_priority | consider creating unified types for common variables as we continue with the typescript migration we may want to create unified types to be used across common method arguments one example could be creating a node type that is used throughout different methods classes when the node parameter is passed around we ll need to decide when we want to do it — after we have fully migrated or while the migration is currently underway or if we even want to standardise these types at all what the types should be e g for node cheerio element domelement could be an option how to handle applying types across the whole codebase | 0 |
244,676 | 26,452,739,212 | IssuesEvent | 2023-01-16 12:27:15 | vital-ws/badge-2 | https://api.github.com/repos/vital-ws/badge-2 | closed | lodash-4.14.0.tgz: 7 vulnerabilities (highest severity is: 9.1) - autoclosed | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.14.0.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz">https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/lodash/package.json</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/vital-ws/badge-2/commit/04c700476eaa216484ee2dd91eaaea59c8f964cc">04c700476eaa216484ee2dd91eaaea59c8f964cc</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (lodash version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2019-10744](https://www.mend.io/vulnerability-database/CVE-2019-10744) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.1 | lodash-4.14.0.tgz | Direct | 4.17.12 | ✅ |
| [CVE-2020-8203](https://www.mend.io/vulnerability-database/CVE-2020-8203) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.4 | lodash-4.14.0.tgz | Direct | 4.17.9 | ✅ |
| [CVE-2021-23337](https://www.mend.io/vulnerability-database/CVE-2021-23337) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.2 | lodash-4.14.0.tgz | Direct | 4.17.21 | ✅ |
| [CVE-2019-1010266](https://www.mend.io/vulnerability-database/CVE-2019-1010266) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | lodash-4.14.0.tgz | Direct | 4.17.11 | ✅ |
| [CVE-2018-3721](https://www.mend.io/vulnerability-database/CVE-2018-3721) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | lodash-4.14.0.tgz | Direct | 4.17.5 | ✅ |
| [CVE-2018-16487](https://www.mend.io/vulnerability-database/CVE-2018-16487) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.6 | lodash-4.14.0.tgz | Direct | 4.17.11 | ✅ |
| [CVE-2020-28500](https://www.mend.io/vulnerability-database/CVE-2020-28500) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | lodash-4.14.0.tgz | Direct | 4.17.21 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-10744</summary>
### Vulnerable Library - <b>lodash-4.14.0.tgz</b></p>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz">https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- :x: **lodash-4.14.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vital-ws/badge-2/commit/04c700476eaa216484ee2dd91eaaea59c8f964cc">04c700476eaa216484ee2dd91eaaea59c8f964cc</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep could be tricked into adding or modifying properties of Object.prototype using a constructor payload.
<p>Publish Date: 2019-07-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-10744>CVE-2019-10744</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-jf85-cpcp-j695">https://github.com/advisories/GHSA-jf85-cpcp-j695</a></p>
<p>Release Date: 2019-07-26</p>
<p>Fix Resolution: 4.17.12</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-8203</summary>
### Vulnerable Library - <b>lodash-4.14.0.tgz</b></p>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz">https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- :x: **lodash-4.14.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vital-ws/badge-2/commit/04c700476eaa216484ee2dd91eaaea59c8f964cc">04c700476eaa216484ee2dd91eaaea59c8f964cc</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.
<p>Publish Date: 2020-07-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-8203>CVE-2020-8203</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.4</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1523">https://www.npmjs.com/advisories/1523</a></p>
<p>Release Date: 2020-07-15</p>
<p>Fix Resolution: 4.17.9</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-23337</summary>
### Vulnerable Library - <b>lodash-4.14.0.tgz</b></p>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz">https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- :x: **lodash-4.14.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vital-ws/badge-2/commit/04c700476eaa216484ee2dd91eaaea59c8f964cc">04c700476eaa216484ee2dd91eaaea59c8f964cc</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23337>CVE-2021-23337</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.2</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- 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-02-15</p>
<p>Fix Resolution: 4.17.21</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2019-1010266</summary>
### Vulnerable Library - <b>lodash-4.14.0.tgz</b></p>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz">https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- :x: **lodash-4.14.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vital-ws/badge-2/commit/04c700476eaa216484ee2dd91eaaea59c8f964cc">04c700476eaa216484ee2dd91eaaea59c8f964cc</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
lodash prior to 4.17.11 is affected by: CWE-400: Uncontrolled Resource Consumption. The impact is: Denial of service. The component is: Date handler. The attack vector is: Attacker provides very long strings, which the library attempts to match using a regular expression. The fixed version is: 4.17.11.
<p>Publish Date: 2019-07-17
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-1010266>CVE-2019-1010266</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1010266">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1010266</a></p>
<p>Release Date: 2019-07-17</p>
<p>Fix Resolution: 4.17.11</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-3721</summary>
### Vulnerable Library - <b>lodash-4.14.0.tgz</b></p>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz">https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- :x: **lodash-4.14.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vital-ws/badge-2/commit/04c700476eaa216484ee2dd91eaaea59c8f964cc">04c700476eaa216484ee2dd91eaaea59c8f964cc</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property that will exist on all objects.
<p>Publish Date: 2018-06-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-3721>CVE-2018-3721</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-3721">https://nvd.nist.gov/vuln/detail/CVE-2018-3721</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution: 4.17.5</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-16487</summary>
### Vulnerable Library - <b>lodash-4.14.0.tgz</b></p>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz">https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- :x: **lodash-4.14.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vital-ws/badge-2/commit/04c700476eaa216484ee2dd91eaaea59c8f964cc">04c700476eaa216484ee2dd91eaaea59c8f964cc</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A prototype pollution vulnerability was found in lodash <4.17.11 where the functions merge, mergeWith, and defaultsDeep can be tricked into adding or modifying properties of Object.prototype.
<p>Publish Date: 2019-02-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-16487>CVE-2018-16487</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.6</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16487">https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16487</a></p>
<p>Release Date: 2019-02-01</p>
<p>Fix Resolution: 4.17.11</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-28500</summary>
### Vulnerable Library - <b>lodash-4.14.0.tgz</b></p>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz">https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- :x: **lodash-4.14.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vital-ws/badge-2/commit/04c700476eaa216484ee2dd91eaaea59c8f964cc">04c700476eaa216484ee2dd91eaaea59c8f964cc</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.
Mend Note: After conducting further research, Mend has determined that CVE-2020-28500 only affects environments with versions 4.0.0 to 4.17.20 of Lodash.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-28500>CVE-2020-28500</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution: 4.17.21</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | True | lodash-4.14.0.tgz: 7 vulnerabilities (highest severity is: 9.1) - autoclosed - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.14.0.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz">https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/lodash/package.json</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/vital-ws/badge-2/commit/04c700476eaa216484ee2dd91eaaea59c8f964cc">04c700476eaa216484ee2dd91eaaea59c8f964cc</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (lodash version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2019-10744](https://www.mend.io/vulnerability-database/CVE-2019-10744) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.1 | lodash-4.14.0.tgz | Direct | 4.17.12 | ✅ |
| [CVE-2020-8203](https://www.mend.io/vulnerability-database/CVE-2020-8203) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.4 | lodash-4.14.0.tgz | Direct | 4.17.9 | ✅ |
| [CVE-2021-23337](https://www.mend.io/vulnerability-database/CVE-2021-23337) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.2 | lodash-4.14.0.tgz | Direct | 4.17.21 | ✅ |
| [CVE-2019-1010266](https://www.mend.io/vulnerability-database/CVE-2019-1010266) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | lodash-4.14.0.tgz | Direct | 4.17.11 | ✅ |
| [CVE-2018-3721](https://www.mend.io/vulnerability-database/CVE-2018-3721) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | lodash-4.14.0.tgz | Direct | 4.17.5 | ✅ |
| [CVE-2018-16487](https://www.mend.io/vulnerability-database/CVE-2018-16487) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.6 | lodash-4.14.0.tgz | Direct | 4.17.11 | ✅ |
| [CVE-2020-28500](https://www.mend.io/vulnerability-database/CVE-2020-28500) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | lodash-4.14.0.tgz | Direct | 4.17.21 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-10744</summary>
### Vulnerable Library - <b>lodash-4.14.0.tgz</b></p>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz">https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- :x: **lodash-4.14.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vital-ws/badge-2/commit/04c700476eaa216484ee2dd91eaaea59c8f964cc">04c700476eaa216484ee2dd91eaaea59c8f964cc</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep could be tricked into adding or modifying properties of Object.prototype using a constructor payload.
<p>Publish Date: 2019-07-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-10744>CVE-2019-10744</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-jf85-cpcp-j695">https://github.com/advisories/GHSA-jf85-cpcp-j695</a></p>
<p>Release Date: 2019-07-26</p>
<p>Fix Resolution: 4.17.12</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-8203</summary>
### Vulnerable Library - <b>lodash-4.14.0.tgz</b></p>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz">https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- :x: **lodash-4.14.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vital-ws/badge-2/commit/04c700476eaa216484ee2dd91eaaea59c8f964cc">04c700476eaa216484ee2dd91eaaea59c8f964cc</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.
<p>Publish Date: 2020-07-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-8203>CVE-2020-8203</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.4</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1523">https://www.npmjs.com/advisories/1523</a></p>
<p>Release Date: 2020-07-15</p>
<p>Fix Resolution: 4.17.9</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-23337</summary>
### Vulnerable Library - <b>lodash-4.14.0.tgz</b></p>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz">https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- :x: **lodash-4.14.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vital-ws/badge-2/commit/04c700476eaa216484ee2dd91eaaea59c8f964cc">04c700476eaa216484ee2dd91eaaea59c8f964cc</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23337>CVE-2021-23337</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.2</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- 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-02-15</p>
<p>Fix Resolution: 4.17.21</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2019-1010266</summary>
### Vulnerable Library - <b>lodash-4.14.0.tgz</b></p>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz">https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- :x: **lodash-4.14.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vital-ws/badge-2/commit/04c700476eaa216484ee2dd91eaaea59c8f964cc">04c700476eaa216484ee2dd91eaaea59c8f964cc</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
lodash prior to 4.17.11 is affected by: CWE-400: Uncontrolled Resource Consumption. The impact is: Denial of service. The component is: Date handler. The attack vector is: Attacker provides very long strings, which the library attempts to match using a regular expression. The fixed version is: 4.17.11.
<p>Publish Date: 2019-07-17
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-1010266>CVE-2019-1010266</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1010266">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1010266</a></p>
<p>Release Date: 2019-07-17</p>
<p>Fix Resolution: 4.17.11</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-3721</summary>
### Vulnerable Library - <b>lodash-4.14.0.tgz</b></p>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz">https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- :x: **lodash-4.14.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vital-ws/badge-2/commit/04c700476eaa216484ee2dd91eaaea59c8f964cc">04c700476eaa216484ee2dd91eaaea59c8f964cc</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property that will exist on all objects.
<p>Publish Date: 2018-06-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-3721>CVE-2018-3721</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-3721">https://nvd.nist.gov/vuln/detail/CVE-2018-3721</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution: 4.17.5</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-16487</summary>
### Vulnerable Library - <b>lodash-4.14.0.tgz</b></p>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz">https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- :x: **lodash-4.14.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vital-ws/badge-2/commit/04c700476eaa216484ee2dd91eaaea59c8f964cc">04c700476eaa216484ee2dd91eaaea59c8f964cc</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A prototype pollution vulnerability was found in lodash <4.17.11 where the functions merge, mergeWith, and defaultsDeep can be tricked into adding or modifying properties of Object.prototype.
<p>Publish Date: 2019-02-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-16487>CVE-2018-16487</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.6</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16487">https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16487</a></p>
<p>Release Date: 2019-02-01</p>
<p>Fix Resolution: 4.17.11</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-28500</summary>
### Vulnerable Library - <b>lodash-4.14.0.tgz</b></p>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz">https://registry.npmjs.org/lodash/-/lodash-4.14.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- :x: **lodash-4.14.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vital-ws/badge-2/commit/04c700476eaa216484ee2dd91eaaea59c8f964cc">04c700476eaa216484ee2dd91eaaea59c8f964cc</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.
Mend Note: After conducting further research, Mend has determined that CVE-2020-28500 only affects environments with versions 4.0.0 to 4.17.20 of Lodash.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-28500>CVE-2020-28500</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution: 4.17.21</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | non_priority | lodash tgz vulnerabilities highest severity is autoclosed vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file package json path to vulnerable library node modules lodash package json found in head commit a href vulnerabilities cve severity cvss dependency type fixed in lodash version remediation available high lodash tgz direct high lodash tgz direct high lodash tgz direct medium lodash tgz direct medium lodash tgz direct medium lodash tgz direct medium lodash tgz direct details cve vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file package json path to vulnerable library node modules lodash package json dependency hierarchy x lodash tgz vulnerable library found in head commit a href found in base branch main vulnerability details versions of lodash lower than are vulnerable to prototype pollution the function defaultsdeep could be tricked into adding or modifying properties of object prototype using a constructor payload publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file package json path to vulnerable library node modules lodash package json dependency hierarchy x lodash tgz vulnerable library found in head commit a href found in base branch main vulnerability details prototype pollution attack when using zipobjectdeep in lodash before 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 high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file package json path to vulnerable library node modules lodash package json dependency hierarchy x lodash tgz vulnerable library found in head commit a href found in base branch main vulnerability details lodash versions prior to are vulnerable to command injection via the template function publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required high user interaction none scope 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 rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file package json path to vulnerable library node modules lodash package json dependency hierarchy x lodash tgz vulnerable library found in head commit a href found in base branch main vulnerability details lodash prior to is affected by cwe uncontrolled resource consumption the impact is denial of service the component is date handler the attack vector is attacker provides very long strings which the library attempts to match using a regular expression the fixed version is publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file package json path to vulnerable library node modules lodash package json dependency hierarchy x lodash tgz vulnerable library found in head commit a href found in base branch main vulnerability details lodash node module before suffers from a modification of assumed immutable data maid vulnerability via defaultsdeep merge and mergewith functions which allows a malicious user to modify the prototype of object via proto causing the addition or modification of an existing property that will exist on all objects publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file package json path to vulnerable library node modules lodash package json dependency hierarchy x lodash tgz vulnerable library found in head commit a href found in base branch main vulnerability details a prototype pollution vulnerability was found in lodash where the functions merge mergewith and defaultsdeep can be tricked into adding or modifying properties of object prototype publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file package json path to vulnerable library node modules lodash package json dependency hierarchy x lodash tgz vulnerable library found in head commit a href found in base branch main vulnerability details lodash versions prior to are vulnerable to regular expression denial of service redos via the tonumber trim and trimend functions mend note after conducting further research mend has determined that cve only affects environments with versions to of lodash 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 origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue | 0 |
34,718 | 2,784,127,064 | IssuesEvent | 2015-05-07 07:26:21 | rrev/Pastebin | https://api.github.com/repos/rrev/Pastebin | closed | Muovere in un thread a parte la lettura dei trending pastes recenti dalla cache | enhancement priority-normal | Muovere in un thread a parte la lettura dei trending pastes recenti dalla cache | 1.0 | Muovere in un thread a parte la lettura dei trending pastes recenti dalla cache - Muovere in un thread a parte la lettura dei trending pastes recenti dalla cache | priority | muovere in un thread a parte la lettura dei trending pastes recenti dalla cache muovere in un thread a parte la lettura dei trending pastes recenti dalla cache | 1 |
555,464 | 16,455,169,500 | IssuesEvent | 2021-05-21 11:31:39 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | m.youtube.com - site is not usable | browser-fenix engine-gecko priority-critical | <!-- @browser: Firefox Mobile 89.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:89.0) Gecko/89.0 Firefox/89.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/74280 -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://m.youtube.com/watch?v=YmXFysxe48Y
**Browser / Version**: Firefox Mobile 89.0
**Operating System**: Android 9
**Tested Another Browser**: No
**Problem type**: Site is not usable
**Description**: Page not loading correctly
**Steps to Reproduce**:
YouTube said "Se ha recibido una respuesta que no es válida."
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2021/5/82515050-ee65-4454-8a11-e996c96de68d.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20210513185752</li><li>channel: beta</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2021/5/d11d61cd-0267-43bf-b9ed-17db88f6a141)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | m.youtube.com - site is not usable - <!-- @browser: Firefox Mobile 89.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:89.0) Gecko/89.0 Firefox/89.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/74280 -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://m.youtube.com/watch?v=YmXFysxe48Y
**Browser / Version**: Firefox Mobile 89.0
**Operating System**: Android 9
**Tested Another Browser**: No
**Problem type**: Site is not usable
**Description**: Page not loading correctly
**Steps to Reproduce**:
YouTube said "Se ha recibido una respuesta que no es válida."
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2021/5/82515050-ee65-4454-8a11-e996c96de68d.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20210513185752</li><li>channel: beta</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2021/5/d11d61cd-0267-43bf-b9ed-17db88f6a141)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | priority | m youtube com site is not usable url browser version firefox mobile operating system android tested another browser no problem type site is not usable description page not loading correctly steps to reproduce youtube said se ha recibido una respuesta que no es válida view the screenshot img alt screenshot src browser configuration gfx webrender all false gfx webrender blob images true gfx webrender enabled false image mem shared true buildid channel beta hastouchscreen true mixed active content blocked false mixed passive content blocked false tracking content blocked false from with ❤️ | 1 |
10,264 | 8,461,572,598 | IssuesEvent | 2018-10-22 22:19:06 | GoogleCloudPlatform/forseti-security | https://api.github.com/repos/GoogleCloudPlatform/forseti-security | closed | Data model is broken | module: infrastructure module: model priority: p1 triaged: yes | One of our customers reported the error, with ~1 million inventory objects
> Traceback (most recent call last):\n File \"/usr/local/lib/python2.7/dist-packages/forseti_security-2.1.0-py2.7.egg/google/cloud/forse
ti/services/model/importer/importer.py\", line 283, in run\n 1000\n File \"/usr/local/lib/python2.7/dist-packages/forseti_security-2.1.0-py2.7.eg
g/google/cloud/forseti/services/model/importer/importer.py\", line 332, in model_action_wrapper\n for idx, inventory_data in enumerate(inventory_i
terable, start=1):\n File \"/usr/local/lib/python2.7/dist-packages/forseti_security-2.1.0-py2.7.egg/google/cloud/forseti/services/inventory/storage.
py\", line 879, in iter\n for row in base_query.yield_per(PER_YIELD):\n File \"build/bdist.linux-x86_64/egg/sqlalchemy/orm/loading.py\", line 98,
in instances\n util.raise_from_cause(err)\n File \"build/bdist.linux-x86_64/egg/sqlalchemy/util/compat.py\", line 265, in raise_from_cause\n
reraise(type(exception), exception, tb=exc_tb, cause=cause)\n File \"build/bdist.linux-x86_64/egg/sqlalchemy/orm/loading.py\", line 71, in instances
\n fetch = cursor.fetchmany(query._yield_per)\n File \"build/bdist.linux-x86_64/egg/sqlalchemy/engine/result.py\", line 1166, in fetchmany\n s
elf.cursor, self.context)\n File \"build/bdist.linux-x86_64/egg/sqlalchemy/engine/base.py\", line 1413, in _handle_dbapi_exception\n exc_info\n
File \"build/bdist.linux-x86_64/egg/sqlalchemy/util/compat.py\", line 265, in raise_from_cause\n reraise(type(exception), exception, tb=exc_tb, ca
use=cause)\n File \"build/bdist.linux-x86_64/egg/sqlalchemy/engine/result.py\", line 1159, in fetchmany\n l = self.process_rows(self._fetchmany_i
mpl(size))\n File \"build/bdist.linux-x86_64/egg/sqlalchemy/engine/result.py\", line 1318, in _fetchmany_impl\n row = self._fetchone_impl()\n Fi
le \"build/bdist.linux-x86_64/egg/sqlalchemy/engine/result.py\", line 1308, in _fetchone_impl\n self.__buffer_rows()\n File \"build/bdist.linux-x
86_64/egg/sqlalchemy/engine/result.py\", line 1295, in __buffer_rows\n self.__rowbuffer = collections.deque(self.cursor.fetchmany(size))\n File \
"build/bdist.linux-x86_64/egg/MySQLdb/cursors.py\", line 441, in fetchmany\n r = self._fetch_row(size or self.arraysize)\n File \"build/bdist.lin
ux-x86_64/egg/MySQLdb/cursors.py\", line 327, in _fetch_row\n return self._result.fetch_row(size, self._fetch_type)\nOperationalError: (_mysql_exc
eptions.OperationalError) (2013, 'Lost connection to MySQL server during query') (Background on this error at: http://sqlalche.me/e/e3q8)\n",
"createdAt": "07 August 2018 - 11:11:11",
"description": "{\"pristine\": true, \"source\": \"inventory\", \"source_root\": \"organization/1234567891234\", \"gsuite_enabled\": false, \"source
_info\": {\"inventory_index_id\": 123456789123456789}}" | 1.0 | Data model is broken - One of our customers reported the error, with ~1 million inventory objects
> Traceback (most recent call last):\n File \"/usr/local/lib/python2.7/dist-packages/forseti_security-2.1.0-py2.7.egg/google/cloud/forse
ti/services/model/importer/importer.py\", line 283, in run\n 1000\n File \"/usr/local/lib/python2.7/dist-packages/forseti_security-2.1.0-py2.7.eg
g/google/cloud/forseti/services/model/importer/importer.py\", line 332, in model_action_wrapper\n for idx, inventory_data in enumerate(inventory_i
terable, start=1):\n File \"/usr/local/lib/python2.7/dist-packages/forseti_security-2.1.0-py2.7.egg/google/cloud/forseti/services/inventory/storage.
py\", line 879, in iter\n for row in base_query.yield_per(PER_YIELD):\n File \"build/bdist.linux-x86_64/egg/sqlalchemy/orm/loading.py\", line 98,
in instances\n util.raise_from_cause(err)\n File \"build/bdist.linux-x86_64/egg/sqlalchemy/util/compat.py\", line 265, in raise_from_cause\n
reraise(type(exception), exception, tb=exc_tb, cause=cause)\n File \"build/bdist.linux-x86_64/egg/sqlalchemy/orm/loading.py\", line 71, in instances
\n fetch = cursor.fetchmany(query._yield_per)\n File \"build/bdist.linux-x86_64/egg/sqlalchemy/engine/result.py\", line 1166, in fetchmany\n s
elf.cursor, self.context)\n File \"build/bdist.linux-x86_64/egg/sqlalchemy/engine/base.py\", line 1413, in _handle_dbapi_exception\n exc_info\n
File \"build/bdist.linux-x86_64/egg/sqlalchemy/util/compat.py\", line 265, in raise_from_cause\n reraise(type(exception), exception, tb=exc_tb, ca
use=cause)\n File \"build/bdist.linux-x86_64/egg/sqlalchemy/engine/result.py\", line 1159, in fetchmany\n l = self.process_rows(self._fetchmany_i
mpl(size))\n File \"build/bdist.linux-x86_64/egg/sqlalchemy/engine/result.py\", line 1318, in _fetchmany_impl\n row = self._fetchone_impl()\n Fi
le \"build/bdist.linux-x86_64/egg/sqlalchemy/engine/result.py\", line 1308, in _fetchone_impl\n self.__buffer_rows()\n File \"build/bdist.linux-x
86_64/egg/sqlalchemy/engine/result.py\", line 1295, in __buffer_rows\n self.__rowbuffer = collections.deque(self.cursor.fetchmany(size))\n File \
"build/bdist.linux-x86_64/egg/MySQLdb/cursors.py\", line 441, in fetchmany\n r = self._fetch_row(size or self.arraysize)\n File \"build/bdist.lin
ux-x86_64/egg/MySQLdb/cursors.py\", line 327, in _fetch_row\n return self._result.fetch_row(size, self._fetch_type)\nOperationalError: (_mysql_exc
eptions.OperationalError) (2013, 'Lost connection to MySQL server during query') (Background on this error at: http://sqlalche.me/e/e3q8)\n",
"createdAt": "07 August 2018 - 11:11:11",
"description": "{\"pristine\": true, \"source\": \"inventory\", \"source_root\": \"organization/1234567891234\", \"gsuite_enabled\": false, \"source
_info\": {\"inventory_index_id\": 123456789123456789}}" | non_priority | data model is broken one of our customers reported the error with million inventory objects traceback most recent call last n file usr local lib dist packages forseti security egg google cloud forse ti services model importer importer py line in run n n file usr local lib dist packages forseti security eg g google cloud forseti services model importer importer py line in model action wrapper n for idx inventory data in enumerate inventory i terable start n file usr local lib dist packages forseti security egg google cloud forseti services inventory storage py line in iter n for row in base query yield per per yield n file build bdist linux egg sqlalchemy orm loading py line in instances n util raise from cause err n file build bdist linux egg sqlalchemy util compat py line in raise from cause n reraise type exception exception tb exc tb cause cause n file build bdist linux egg sqlalchemy orm loading py line in instances n fetch cursor fetchmany query yield per n file build bdist linux egg sqlalchemy engine result py line in fetchmany n s elf cursor self context n file build bdist linux egg sqlalchemy engine base py line in handle dbapi exception n exc info n file build bdist linux egg sqlalchemy util compat py line in raise from cause n reraise type exception exception tb exc tb ca use cause n file build bdist linux egg sqlalchemy engine result py line in fetchmany n l self process rows self fetchmany i mpl size n file build bdist linux egg sqlalchemy engine result py line in fetchmany impl n row self fetchone impl n fi le build bdist linux egg sqlalchemy engine result py line in fetchone impl n self buffer rows n file build bdist linux x egg sqlalchemy engine result py line in buffer rows n self rowbuffer collections deque self cursor fetchmany size n file build bdist linux egg mysqldb cursors py line in fetchmany n r self fetch row size or self arraysize n file build bdist lin ux egg mysqldb cursors py line in fetch row n return self result fetch row size self fetch type noperationalerror mysql exc eptions operationalerror lost connection to mysql server during query background on this error at createdat august description pristine true source inventory source root organization gsuite enabled false source info inventory index id | 0 |
343,265 | 30,653,593,008 | IssuesEvent | 2023-07-25 10:31:28 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | closed | Fix paddle_manipulation.test_paddle_concat | Sub Task Failing Test Paddle Frontend | | | |
|---|---|
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5526767644/jobs/10081843138"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5526767644/jobs/10081843138"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5526767644/jobs/10081843138"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5526767644/jobs/10081843138"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5526767644/jobs/10081843138"><img src=https://img.shields.io/badge/-success-success></a>
| 1.0 | Fix paddle_manipulation.test_paddle_concat - | | |
|---|---|
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5526767644/jobs/10081843138"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5526767644/jobs/10081843138"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5526767644/jobs/10081843138"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5526767644/jobs/10081843138"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5526767644/jobs/10081843138"><img src=https://img.shields.io/badge/-success-success></a>
| non_priority | fix paddle manipulation test paddle concat torch a href src tensorflow a href src numpy a href src paddle a href src jax a href src | 0 |
178,282 | 13,771,408,897 | IssuesEvent | 2020-10-07 21:57:59 | mozilla-mobile/fenix | https://api.github.com/repos/mozilla-mobile/fenix | closed | Intermittent UI test failure - MediaNotificationTest | eng:ui-test intermittent-test needs:triage | ### Firebase Test Run:
https://console.firebase.google.com/project/moz-fenix/testlab/histories/bh.66b7091e15d53d45/matrices/4983241498387819676
### Stacktrace:
- See the results at the link for the tests:
- `audioPlaybackSystemNotificationTest`
- `mediaSystemNotificationInPrivateModeTest`
- `tabMediaControlButtonTest`
### Build:
- AC upgrade and prior: https://github.com/mozilla-mobile/fenix/pull/15734 | 2.0 | Intermittent UI test failure - MediaNotificationTest - ### Firebase Test Run:
https://console.firebase.google.com/project/moz-fenix/testlab/histories/bh.66b7091e15d53d45/matrices/4983241498387819676
### Stacktrace:
- See the results at the link for the tests:
- `audioPlaybackSystemNotificationTest`
- `mediaSystemNotificationInPrivateModeTest`
- `tabMediaControlButtonTest`
### Build:
- AC upgrade and prior: https://github.com/mozilla-mobile/fenix/pull/15734 | non_priority | intermittent ui test failure medianotificationtest firebase test run stacktrace see the results at the link for the tests audioplaybacksystemnotificationtest mediasystemnotificationinprivatemodetest tabmediacontrolbuttontest build ac upgrade and prior | 0 |
603,746 | 18,670,756,544 | IssuesEvent | 2021-10-30 17:04:37 | bounswe/2021SpringGroup6 | https://api.github.com/repos/bounswe/2021SpringGroup6 | closed | Write the Validation Check For Emails | Type: Feature Status: Complete Priority: Medium Back-End: Validation | Writing the validation check code with the selected Validation Library for emails. | 1.0 | Write the Validation Check For Emails - Writing the validation check code with the selected Validation Library for emails. | priority | write the validation check for emails writing the validation check code with the selected validation library for emails | 1 |
725,781 | 24,975,781,472 | IssuesEvent | 2022-11-02 07:39:04 | matrixorigin/matrixone | https://api.github.com/repos/matrixorigin/matrixone | closed | DISTINCT doesn't work in COUNT() | kind/bug priority/p0 triage/accepted | <!-- Please describe your issue in English. -->
#### Can be reproduced ?
Yes
#### Steps:
CREATE TABLE t2(product VARCHAR(32),country_id INTEGER NOT NULL,year INTEGER,profit INTEGER);
INSERT INTO t2 VALUES ( 'Computer', 2,2000, 1200),
( 'TV', 1, 1999, 150),
( 'Calculator', 1, 1999,50),
( 'Computer', 1, 1999,1500),
( 'Computer', 1, 2000,1500),
( 'TV', 1, 2000, 150),
( 'TV', 2, 2000, 100),
( 'TV', 2, 2000, 100),
( 'Calculator', 1, 2000,75),
( 'Calculator', 2, 2000,75),
( 'TV', 1, 1999, 100),
( 'Computer', 1, 1999,1200),
( 'Computer', 2, 2000,1500),
( 'Calculator', 2, 2000,75),
( 'Phone', 3, 2003,10);
SELECT product, country_id, COUNT(*), COUNT(distinct year) FROM t2 GROUP BY product, country_id order by product;
In MySQL the result is
#### Expected behavior:
#### Actual behavior:
#### Environment:
- Version or commit-id (e.g. v0.1.0 or 8b23a93): 3835f50655d37f4174b9bc4ef0d4a871a06f63e4
- Hardware parameters:
- OS type:
- Others:
#### Configuration file:
#### Additional context:
- Error message from client:
- Server log:
- Other information: | 1.0 | DISTINCT doesn't work in COUNT() - <!-- Please describe your issue in English. -->
#### Can be reproduced ?
Yes
#### Steps:
CREATE TABLE t2(product VARCHAR(32),country_id INTEGER NOT NULL,year INTEGER,profit INTEGER);
INSERT INTO t2 VALUES ( 'Computer', 2,2000, 1200),
( 'TV', 1, 1999, 150),
( 'Calculator', 1, 1999,50),
( 'Computer', 1, 1999,1500),
( 'Computer', 1, 2000,1500),
( 'TV', 1, 2000, 150),
( 'TV', 2, 2000, 100),
( 'TV', 2, 2000, 100),
( 'Calculator', 1, 2000,75),
( 'Calculator', 2, 2000,75),
( 'TV', 1, 1999, 100),
( 'Computer', 1, 1999,1200),
( 'Computer', 2, 2000,1500),
( 'Calculator', 2, 2000,75),
( 'Phone', 3, 2003,10);
SELECT product, country_id, COUNT(*), COUNT(distinct year) FROM t2 GROUP BY product, country_id order by product;
In MySQL the result is
#### Expected behavior:
#### Actual behavior:
#### Environment:
- Version or commit-id (e.g. v0.1.0 or 8b23a93): 3835f50655d37f4174b9bc4ef0d4a871a06f63e4
- Hardware parameters:
- OS type:
- Others:
#### Configuration file:
#### Additional context:
- Error message from client:
- Server log:
- Other information: | priority | distinct doesn t work in count can be reproduced yes steps create table product varchar country id integer not null year integer profit integer insert into values computer tv calculator computer computer tv tv tv calculator calculator tv computer computer calculator phone select product country id count count distinct year from group by product country id order by product in mysql the result is expected behavior actual behavior environment version or commit id e g or hardware parameters os type others configuration file additional context error message from client server log other information | 1 |
6,024 | 3,727,392,537 | IssuesEvent | 2016-03-06 08:08:40 | orbeon/orbeon-forms | https://api.github.com/repos/orbeon/orbeon-forms | opened | Previous/next navigation in Control Settings dialog | Form Builder RFE | Idea is to navigate between form controls without having to close/reopen the dialog.
Should also do this for Section/Grid Settings. | 1.0 | Previous/next navigation in Control Settings dialog - Idea is to navigate between form controls without having to close/reopen the dialog.
Should also do this for Section/Grid Settings. | non_priority | previous next navigation in control settings dialog idea is to navigate between form controls without having to close reopen the dialog should also do this for section grid settings | 0 |
127,382 | 12,321,579,183 | IssuesEvent | 2020-05-13 08:56:58 | OpenOrbis/OpenOrbis-PS4-Toolchain | https://api.github.com/repos/OpenOrbis/OpenOrbis-PS4-Toolchain | closed | Add changelog for historic purposes | documentation | Add a changelog containing changes from alpha as well as changes going forward. | 1.0 | Add changelog for historic purposes - Add a changelog containing changes from alpha as well as changes going forward. | non_priority | add changelog for historic purposes add a changelog containing changes from alpha as well as changes going forward | 0 |
152,523 | 13,459,101,342 | IssuesEvent | 2020-09-09 11:44:15 | Wikunia/Javis.jl | https://api.github.com/repos/Wikunia/Javis.jl | closed | Docstrings: structs | documentation | All structs even if internal should have a small docstring describing the fields and the usage. Maybe linking to main methods where the structure is used. | 1.0 | Docstrings: structs - All structs even if internal should have a small docstring describing the fields and the usage. Maybe linking to main methods where the structure is used. | non_priority | docstrings structs all structs even if internal should have a small docstring describing the fields and the usage maybe linking to main methods where the structure is used | 0 |
88,960 | 15,823,624,165 | IssuesEvent | 2021-04-06 01:14:05 | dpteam/RK3188_TABLET | https://api.github.com/repos/dpteam/RK3188_TABLET | opened | CVE-2019-19448 (High) detected in linuxv3.0 | security vulnerability | ## CVE-2019-19448 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxv3.0</b></p></summary>
<p>
<p>Linux kernel source tree</p>
<p>Library home page: <a href=https://github.com/verygreen/linux.git>https://github.com/verygreen/linux.git</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>RK3188_TABLET/fs/btrfs/free-space-cache.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>
In the Linux kernel 5.0.21 and 5.3.11, mounting a crafted btrfs filesystem image, performing some operations, and then making a syncfs system call can lead to a use-after-free in try_merge_free_space in fs/btrfs/free-space-cache.c because the pointer to a left data structure can be the same as the pointer to a right data structure.
<p>Publish Date: 2019-12-08
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-19448>CVE-2019-19448</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: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2019-19448">https://www.linuxkernelcves.com/cves/CVE-2019-19448</a></p>
<p>Release Date: 2020-11-02</p>
<p>Fix Resolution: v4.4.233, v4.9.233, v4.14.194, v4.19.141, v5.4.60, v5.7.17, v5.8.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2019-19448 (High) detected in linuxv3.0 - ## CVE-2019-19448 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxv3.0</b></p></summary>
<p>
<p>Linux kernel source tree</p>
<p>Library home page: <a href=https://github.com/verygreen/linux.git>https://github.com/verygreen/linux.git</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>RK3188_TABLET/fs/btrfs/free-space-cache.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>
In the Linux kernel 5.0.21 and 5.3.11, mounting a crafted btrfs filesystem image, performing some operations, and then making a syncfs system call can lead to a use-after-free in try_merge_free_space in fs/btrfs/free-space-cache.c because the pointer to a left data structure can be the same as the pointer to a right data structure.
<p>Publish Date: 2019-12-08
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-19448>CVE-2019-19448</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: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2019-19448">https://www.linuxkernelcves.com/cves/CVE-2019-19448</a></p>
<p>Release Date: 2020-11-02</p>
<p>Fix Resolution: v4.4.233, v4.9.233, v4.14.194, v4.19.141, v5.4.60, v5.7.17, v5.8.3</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 cve high severity vulnerability vulnerable library linux kernel source tree library home page a href found in base branch master vulnerable source files tablet fs btrfs free space cache c vulnerability details in the linux kernel and mounting a crafted btrfs filesystem image performing some operations and then making a syncfs system call can lead to a use after free in try merge free space in fs btrfs free space cache c because the pointer to a left data structure can be the same as the pointer to a right data structure publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact 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 |
12,326 | 19,661,245,092 | IssuesEvent | 2022-01-10 17:14:03 | renovatebot/renovate | https://api.github.com/repos/renovatebot/renovate | opened | Reactivating an ignored PR in Azure DevOps doesn't work when using the provided directions for renaming | type:bug status:requirements priority-5-triage | ### How are you running Renovate?
WhiteSource Renovate hosted app on github.com
### If you're self-hosting Renovate, tell us what version of Renovate you run.
_No response_
### Please select which platform you are using if self-hosting.
Azure DevOps (dev.azure.com)
### If you're self-hosting Renovate, tell us what version of the platform you run.
_No response_
### Describe the bug
I'm using the renovate CLI to scan dependencies and open PR's while using the Azure DevOps service.
This pipeline works great and creates all my PR's with changes.
## Abandoned (Closed) PR
I have a "stalebot" style tool cleaning up PR's that have been sitting idle.
I went to reactivate one but found that this won't work in Azure DevOps as the branch is removed as part of cleanup. Because of this I need to follow the directions it said below:
```
Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will ignore this upgrade
and you will not receive PRs for any future REPO digest updates.
Digest updates will resume if you update the specified tag at any time.
If this PR was closed by mistake or you changed your mind,
you can simply rename this PR and you will soon get a fresh replacement PR opened.
```
This is problematic in Azure DevOps because once a PR is merged or abandoned (their term for closed without merge) there is no ability to rename the PR, and you can't reopen if the branch no longer exists.
## Issue
This makes the current reopen option unviable.
I'd request a method so I can reopen an abandoned PR and for Azure DevOps ensure the closing message properly describes how to "UN-Ignore" the prior abandoned PR.
### Relevant debug logs
_No response_
### Have you created a minimal reproduction repository?
No reproduction repository | 1.0 | Reactivating an ignored PR in Azure DevOps doesn't work when using the provided directions for renaming - ### How are you running Renovate?
WhiteSource Renovate hosted app on github.com
### If you're self-hosting Renovate, tell us what version of Renovate you run.
_No response_
### Please select which platform you are using if self-hosting.
Azure DevOps (dev.azure.com)
### If you're self-hosting Renovate, tell us what version of the platform you run.
_No response_
### Describe the bug
I'm using the renovate CLI to scan dependencies and open PR's while using the Azure DevOps service.
This pipeline works great and creates all my PR's with changes.
## Abandoned (Closed) PR
I have a "stalebot" style tool cleaning up PR's that have been sitting idle.
I went to reactivate one but found that this won't work in Azure DevOps as the branch is removed as part of cleanup. Because of this I need to follow the directions it said below:
```
Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will ignore this upgrade
and you will not receive PRs for any future REPO digest updates.
Digest updates will resume if you update the specified tag at any time.
If this PR was closed by mistake or you changed your mind,
you can simply rename this PR and you will soon get a fresh replacement PR opened.
```
This is problematic in Azure DevOps because once a PR is merged or abandoned (their term for closed without merge) there is no ability to rename the PR, and you can't reopen if the branch no longer exists.
## Issue
This makes the current reopen option unviable.
I'd request a method so I can reopen an abandoned PR and for Azure DevOps ensure the closing message properly describes how to "UN-Ignore" the prior abandoned PR.
### Relevant debug logs
_No response_
### Have you created a minimal reproduction repository?
No reproduction repository | non_priority | reactivating an ignored pr in azure devops doesn t work when using the provided directions for renaming how are you running renovate whitesource renovate hosted app on github com if you re self hosting renovate tell us what version of renovate you run no response please select which platform you are using if self hosting azure devops dev azure com if you re self hosting renovate tell us what version of the platform you run no response describe the bug i m using the renovate cli to scan dependencies and open pr s while using the azure devops service this pipeline works great and creates all my pr s with changes abandoned closed pr i have a stalebot style tool cleaning up pr s that have been sitting idle i went to reactivate one but found that this won t work in azure devops as the branch is removed as part of cleanup because of this i need to follow the directions it said below renovate ignore notification as this pr has been closed unmerged renovate will ignore this upgrade and you will not receive prs for any future repo digest updates digest updates will resume if you update the specified tag at any time if this pr was closed by mistake or you changed your mind you can simply rename this pr and you will soon get a fresh replacement pr opened this is problematic in azure devops because once a pr is merged or abandoned their term for closed without merge there is no ability to rename the pr and you can t reopen if the branch no longer exists issue this makes the current reopen option unviable i d request a method so i can reopen an abandoned pr and for azure devops ensure the closing message properly describes how to un ignore the prior abandoned pr relevant debug logs no response have you created a minimal reproduction repository no reproduction repository | 0 |
84,801 | 10,564,311,688 | IssuesEvent | 2019-10-05 00:48:16 | QOSQOs/unkown | https://api.github.com/repos/QOSQOs/unkown | opened | Add a demo for authentication using tokens-JWT | design | **Is your feature request related to a problem? Please describe.**
<!--- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
The authentication is one of the most important features, therefore we need to create a proposal to authenticate a user in the system.
**Describe the solution you'd like**
<!--- A clear and concise description of what you want to happen -->
Try using tokens-JWT or similar libraries.
**Describe alternatives you've considered**
<!--- A clear and concise description of any alternative solutions or features you've considered. -->
Feel free to propose any other solution.
**Additional context**
<!--- Add any other context or screenshots about the feature request here -->
NONE | 1.0 | Add a demo for authentication using tokens-JWT - **Is your feature request related to a problem? Please describe.**
<!--- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
The authentication is one of the most important features, therefore we need to create a proposal to authenticate a user in the system.
**Describe the solution you'd like**
<!--- A clear and concise description of what you want to happen -->
Try using tokens-JWT or similar libraries.
**Describe alternatives you've considered**
<!--- A clear and concise description of any alternative solutions or features you've considered. -->
Feel free to propose any other solution.
**Additional context**
<!--- Add any other context or screenshots about the feature request here -->
NONE | non_priority | add a demo for authentication using tokens jwt is your feature request related to a problem please describe the authentication is one of the most important features therefore we need to create a proposal to authenticate a user in the system describe the solution you d like try using tokens jwt or similar libraries describe alternatives you ve considered feel free to propose any other solution additional context none | 0 |
799,322 | 28,304,431,719 | IssuesEvent | 2023-04-10 09:32:40 | AY2223S2-CS2103T-W15-2/tp | https://api.github.com/repos/AY2223S2-CS2103T-W15-2/tp | closed | As a home bakery owner, I can see the history of all my past orders | type.Story priority.Medium user.Orders | ... so that I can track my business growth over time | 1.0 | As a home bakery owner, I can see the history of all my past orders - ... so that I can track my business growth over time | priority | as a home bakery owner i can see the history of all my past orders so that i can track my business growth over time | 1 |
132,041 | 28,084,375,788 | IssuesEvent | 2023-03-30 08:48:22 | appsmithorg/appsmith | https://api.github.com/repos/appsmithorg/appsmith | closed | [Bug]: Misaligned error code in the error logs | Bug Low BE Coders Pod Data Platform Pod Error Handling | ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Description
When I get a 404 error from my server, the error log looks misaligned
### Steps To Reproduce
1. Create an API response which fails because of a 404 error.
2. Observe the error log.
### Public Sample App
https://app.appsmith.com/app/word-cloud/explore-63071d60bb6b2f2ee51115de/edit/widgets/fifz536dy1?branch=master
### Environment
Production
### Issue video log
_No response_
### Version
Cloud | 1.0 | [Bug]: Misaligned error code in the error logs - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Description
When I get a 404 error from my server, the error log looks misaligned
### Steps To Reproduce
1. Create an API response which fails because of a 404 error.
2. Observe the error log.
### Public Sample App
https://app.appsmith.com/app/word-cloud/explore-63071d60bb6b2f2ee51115de/edit/widgets/fifz536dy1?branch=master
### Environment
Production
### Issue video log
_No response_
### Version
Cloud | non_priority | misaligned error code in the error logs is there an existing issue for this i have searched the existing issues description when i get a error from my server the error log looks misaligned steps to reproduce create an api response which fails because of a error observe the error log public sample app environment production issue video log no response version cloud | 0 |
205,294 | 15,605,477,460 | IssuesEvent | 2021-03-19 06:17:22 | AOSC-Dev/aosc-os-abbs | https://api.github.com/repos/AOSC-Dev/aosc-os-abbs | closed | nghttp2: security update to 1.41.0 | security to-testing upgrade | <!-- Please remove items do not apply. -->
**CVE IDs:** CVE-2020-11080
**Other security advisory IDs:** RHSA-2020:2755-01
**Description:**
* nghttp2: overly large SETTINGS frames can lead to DoS (CVE-2020-11080)
**Patches:** N/A
**PoC(s):** <!-- Please list links to available PoCs (Proofs of Concept). -->
**Architectural progress (Mainline):**
<!-- Please remove any architecture to which the security vulnerabilities do not apply. -->
- [ ] AMD64 `amd64`
- [ ] AArch64 `arm64`
<!-- If the specified package is `noarch`, please use the stub below. -->
<!-- - [ ] Architecture-independent `noarch` -->
| 1.0 | nghttp2: security update to 1.41.0 - <!-- Please remove items do not apply. -->
**CVE IDs:** CVE-2020-11080
**Other security advisory IDs:** RHSA-2020:2755-01
**Description:**
* nghttp2: overly large SETTINGS frames can lead to DoS (CVE-2020-11080)
**Patches:** N/A
**PoC(s):** <!-- Please list links to available PoCs (Proofs of Concept). -->
**Architectural progress (Mainline):**
<!-- Please remove any architecture to which the security vulnerabilities do not apply. -->
- [ ] AMD64 `amd64`
- [ ] AArch64 `arm64`
<!-- If the specified package is `noarch`, please use the stub below. -->
<!-- - [ ] Architecture-independent `noarch` -->
| non_priority | security update to cve ids cve other security advisory ids rhsa description overly large settings frames can lead to dos cve patches n a poc s architectural progress mainline | 0 |
55,556 | 13,640,638,621 | IssuesEvent | 2020-09-25 13:03:36 | AdoptOpenJDK/openjdk-build | https://api.github.com/repos/AdoptOpenJDK/openjdk-build | closed | Job generators crashing due to invalid parseText() | bug buildbreak regeneration | **Platform:**
All
**Architecture:**
All
[This](https://github.com/AdoptOpenJDK/openjdk-build/commit/60054010502e7c3deb1b9520a7d6fd238c66af6e#diff-0bd2ec0f87e6c44d162becb466ed92df) commit broke the job regenerators by introducing a parseText outside of the main master node (not that should matter in Jenkins).
```
hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: groovy.json.JsonSlurper.parseText() is applicable for argument types: (org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper) values: [org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper@2bbbce24]
Possible solutions: parseText(java.lang.String), parse([B), parse([C), parse(java.io.File), parse(java.io.InputStream), parse(java.io.Reader)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:153)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:161)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:165)
at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)
at Script4.run(Script4.groovy:518)
at WorkflowScript.run(WorkflowScript:104)
at ___cps.transform___(Native Method)
at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:86)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:113)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:83)
at sun.reflect.GeneratedMethodAccessor145.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
at com.cloudbees.groovy.cps.impl.LocalVariableBlock$LocalVariable.get(LocalVariableBlock.java:39)
at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)
at com.cloudbees.groovy.cps.impl.LocalVariableBlock.evalLValue(LocalVariableBlock.java:28)
at com.cloudbees.groovy.cps.LValueBlock$BlockImpl.eval(LValueBlock.java:55)
at com.cloudbees.groovy.cps.LValueBlock.eval(LValueBlock.java:16)
at com.cloudbees.groovy.cps.Next.step(Next.java:83)
at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174)
at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)
at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:129)
at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:268)
at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:51)
at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:185)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:400)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$400(CpsThreadGroup.java:96)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:312)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:276)
at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:67)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
```
| 1.0 | Job generators crashing due to invalid parseText() - **Platform:**
All
**Architecture:**
All
[This](https://github.com/AdoptOpenJDK/openjdk-build/commit/60054010502e7c3deb1b9520a7d6fd238c66af6e#diff-0bd2ec0f87e6c44d162becb466ed92df) commit broke the job regenerators by introducing a parseText outside of the main master node (not that should matter in Jenkins).
```
hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: groovy.json.JsonSlurper.parseText() is applicable for argument types: (org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper) values: [org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper@2bbbce24]
Possible solutions: parseText(java.lang.String), parse([B), parse([C), parse(java.io.File), parse(java.io.InputStream), parse(java.io.Reader)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:153)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:161)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:165)
at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)
at Script4.run(Script4.groovy:518)
at WorkflowScript.run(WorkflowScript:104)
at ___cps.transform___(Native Method)
at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:86)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:113)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:83)
at sun.reflect.GeneratedMethodAccessor145.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
at com.cloudbees.groovy.cps.impl.LocalVariableBlock$LocalVariable.get(LocalVariableBlock.java:39)
at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)
at com.cloudbees.groovy.cps.impl.LocalVariableBlock.evalLValue(LocalVariableBlock.java:28)
at com.cloudbees.groovy.cps.LValueBlock$BlockImpl.eval(LValueBlock.java:55)
at com.cloudbees.groovy.cps.LValueBlock.eval(LValueBlock.java:16)
at com.cloudbees.groovy.cps.Next.step(Next.java:83)
at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174)
at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)
at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:129)
at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:268)
at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:51)
at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:185)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:400)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$400(CpsThreadGroup.java:96)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:312)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:276)
at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:67)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
```
| non_priority | job generators crashing due to invalid parsetext platform all architecture all commit broke the job regenerators by introducing a parsetext outside of the main master node not that should matter in jenkins hudson remoting proxyexception groovy lang missingmethodexception no signature of method groovy json jsonslurper parsetext is applicable for argument types org jenkinsci plugins workflow support steps build runwrapper values possible solutions parsetext java lang string parse b parse c parse java io file parse java io inputstream parse java io reader at org jenkinsci plugins scriptsecurity sandbox groovy sandboxinterceptor onmethodcall sandboxinterceptor java at org kohsuke groovy sandbox impl checker call checker java at org kohsuke groovy sandbox impl checker checkedcall checker java at com cloudbees groovy cps sandbox sandboxinvoker methodcall sandboxinvoker java at run groovy at workflowscript run workflowscript at cps transform native method at com cloudbees groovy cps impl continuationgroup methodcall continuationgroup java at com cloudbees groovy cps impl functioncallblock continuationimpl dispatchorarg functioncallblock java at com cloudbees groovy cps impl functioncallblock continuationimpl fixarg functioncallblock java at sun reflect invoke unknown source at sun reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at com cloudbees groovy cps impl continuationptr continuationimpl receive continuationptr java at com cloudbees groovy cps impl localvariableblock localvariable get localvariableblock java at com cloudbees groovy cps lvalueblock getadapter receive lvalueblock java at com cloudbees groovy cps impl localvariableblock evallvalue localvariableblock java at com cloudbees groovy cps lvalueblock blockimpl eval lvalueblock java at com cloudbees groovy cps lvalueblock eval lvalueblock java at com cloudbees groovy cps next step next java at com cloudbees groovy cps continuable call continuable java at com cloudbees groovy cps continuable call continuable java at org codehaus groovy runtime groovycategorysupport threadcategoryinfo use groovycategorysupport java at org codehaus groovy runtime groovycategorysupport use groovycategorysupport java at com cloudbees groovy cps continuable continuable java at org jenkinsci plugins workflow cps sandboxcontinuable access sandboxcontinuable java at org jenkinsci plugins workflow cps sandboxcontinuable sandboxcontinuable java at org jenkinsci plugins workflow cps cpsthread runnextchunk cpsthread java at org jenkinsci plugins workflow cps cpsthreadgroup run cpsthreadgroup java at org jenkinsci plugins workflow cps cpsthreadgroup access cpsthreadgroup java at org jenkinsci plugins workflow cps cpsthreadgroup call cpsthreadgroup java at org jenkinsci plugins workflow cps cpsthreadgroup call cpsthreadgroup java at org jenkinsci plugins workflow cps cpsvmexecutorservice call cpsvmexecutorservice java at java util concurrent futuretask run futuretask java at hudson remoting singlelaneexecutorservice run singlelaneexecutorservice java at jenkins util contextresettingexecutorservice run contextresettingexecutorservice java at jenkins security impersonatingexecutorservice run impersonatingexecutorservice java at java util concurrent executors runnableadapter call executors java at java util concurrent futuretask run futuretask java at java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java util concurrent threadpoolexecutor worker run threadpoolexecutor java at java lang thread run thread java | 0 |
51,214 | 6,500,350,485 | IssuesEvent | 2017-08-23 03:38:31 | jupyterlab/jupyterlab-google-drive | https://api.github.com/repos/jupyterlab/jupyterlab-google-drive | closed | Folder creation impatience bug | tag:Design and UX type:Bug | If you're an impatient person like myself, or you just forgot the difference between the breadcrumb (double click) and the new folder button (single click) you might accidentally double click the new folder button.
in doing so you will create two folders with the same name. Because they are the same name you can only select them together, and they are difficult to delete (i had to login to drive separately to do it). Sometimes they are easy to delete though. Only happens in google drive because it takes longer to make folders remotely.
Usually the first folder deletes, but yields an error in the pop-up box. then you have to delete the second folder.
| 1.0 | Folder creation impatience bug - If you're an impatient person like myself, or you just forgot the difference between the breadcrumb (double click) and the new folder button (single click) you might accidentally double click the new folder button.
in doing so you will create two folders with the same name. Because they are the same name you can only select them together, and they are difficult to delete (i had to login to drive separately to do it). Sometimes they are easy to delete though. Only happens in google drive because it takes longer to make folders remotely.
Usually the first folder deletes, but yields an error in the pop-up box. then you have to delete the second folder.
| non_priority | folder creation impatience bug if you re an impatient person like myself or you just forgot the difference between the breadcrumb double click and the new folder button single click you might accidentally double click the new folder button in doing so you will create two folders with the same name because they are the same name you can only select them together and they are difficult to delete i had to login to drive separately to do it sometimes they are easy to delete though only happens in google drive because it takes longer to make folders remotely usually the first folder deletes but yields an error in the pop up box then you have to delete the second folder | 0 |
32,156 | 2,744,200,714 | IssuesEvent | 2015-04-22 04:54:25 | ventuso/Fi-Test | https://api.github.com/repos/ventuso/Fi-Test | closed | HereNow and Featured feeds need to be shown on network home (default state) | android enhancement iOS Priority (FIX NOW) | On the Network Home Page, News feed is currently displaying too low and off screen.
Please shift elements higher up on the page to allow the news feed show a little bit on the default state.
Use the alignment comparison below as reference. I am mainly looking at iOS but I think this is an issue on Androids also.
 | 1.0 | HereNow and Featured feeds need to be shown on network home (default state) - On the Network Home Page, News feed is currently displaying too low and off screen.
Please shift elements higher up on the page to allow the news feed show a little bit on the default state.
Use the alignment comparison below as reference. I am mainly looking at iOS but I think this is an issue on Androids also.
 | priority | herenow and featured feeds need to be shown on network home default state on the network home page news feed is currently displaying too low and off screen please shift elements higher up on the page to allow the news feed show a little bit on the default state use the alignment comparison below as reference i am mainly looking at ios but i think this is an issue on androids also | 1 |
64,570 | 26,790,439,377 | IssuesEvent | 2023-02-01 08:03:11 | ballerina-platform/openapi-tools | https://api.github.com/repos/ballerina-platform/openapi-tools | closed | java.util.NoSuchElementException when trying to generate the service from the OAS | Type/Bug Service OpenAPIToBallerina | **Description:**
**Steps to reproduce:**
Command that executed
> bal openapi -i snowtooth_openapi.yaml --mode=service
Error
```
ballerina: Oh no, something really went wrong. Bad. Sad.
We appreciate it if you can report the code that broke Ballerina in
https://github.com/ballerina-platform/ballerina-lang/issues with the
log you get below and your sample code.
We thank you for helping make us better.
[2023-01-31 15:02:11,435] SEVERE {b7a.log.crash} - null
java.util.NoSuchElementException
at java.base/java.util.LinkedHashMap$LinkedHashIterator.nextNode(LinkedHashMap.java:721)
at java.base/java.util.LinkedHashMap$LinkedEntryIterator.next(LinkedHashMap.java:751)
at java.base/java.util.LinkedHashMap$LinkedEntryIterator.next(LinkedHashMap.java:749)
at io.ballerina.openapi.core.generators.service.ReturnTypeGenerator.getReturnTypeDescriptorNode(ReturnTypeGenerator.java:118)
at io.ballerina.openapi.core.generators.service.BallerinaServiceGenerator.getResourceFunction(BallerinaServiceGenerator.java:261)
at io.ballerina.openapi.core.generators.service.BallerinaServiceGenerator.applyFiltersForOperations(BallerinaServiceGenerator.java:206)
at io.ballerina.openapi.core.generators.service.BallerinaServiceGenerator.createResourceFunctions(BallerinaServiceGenerator.java:154)
at io.ballerina.openapi.core.generators.service.BallerinaServiceGenerator.generateSyntaxTree(BallerinaServiceGenerator.java:115)
at io.ballerina.openapi.cmd.BallerinaCodeGenerator.generateBallerinaService(BallerinaCodeGenerator.java:395)
at io.ballerina.openapi.cmd.BallerinaCodeGenerator.generateService(BallerinaCodeGenerator.java:220)
at io.ballerina.openapi.cmd.OpenApiCmd.generateServiceFile(OpenApiCmd.java:376)
at io.ballerina.openapi.cmd.OpenApiCmd.openApiToBallerina(OpenApiCmd.java:277)
at io.ballerina.openapi.cmd.OpenApiCmd.execute(OpenApiCmd.java:180)
at java.base/java.util.Optional.ifPresent(Optional.java:183)
at io.ballerina.cli.launcher.Main.main(Main.java:51)
```
Yaml that used:
```openapi
openapi: "3.0.0"
info:
version: 1.0.0
title: OpenApi Petstore
license:
name: MIT
servers:
- url: http://localhost:9090/petstore/v1
paths:
/pets:
get:
summary: List all pets
description: Show a list of pets in the system
operationId: listPets
tags:
- pets
- list
parameters:
- name: limit
in: query
description: How many items to return at one time (max 100)
required: false
schema:
type: integer
format: int32
responses: {}
```
**Affected Versions:**
2201.3.2
**OS, DB, other environment details and versions:**
**Related Issues (optional):**
<!-- Any related issues such as sub tasks, issues reported in other repositories (e.g component repositories), similar problems, etc. -->
**Suggested Labels (optional):**
<!-- Optional comma separated list of suggested labels. Non committers can’t assign labels to issues, so this will help issue creators who are not a committer to suggest possible labels-->
**Suggested Assignees (optional):**
<!--Optional comma separated list of suggested team members who should attend the issue. Non committers can’t assign issues to assignees, so this will help issue creators who are not a committer to suggest possible assignees-->
| 1.0 | java.util.NoSuchElementException when trying to generate the service from the OAS - **Description:**
**Steps to reproduce:**
Command that executed
> bal openapi -i snowtooth_openapi.yaml --mode=service
Error
```
ballerina: Oh no, something really went wrong. Bad. Sad.
We appreciate it if you can report the code that broke Ballerina in
https://github.com/ballerina-platform/ballerina-lang/issues with the
log you get below and your sample code.
We thank you for helping make us better.
[2023-01-31 15:02:11,435] SEVERE {b7a.log.crash} - null
java.util.NoSuchElementException
at java.base/java.util.LinkedHashMap$LinkedHashIterator.nextNode(LinkedHashMap.java:721)
at java.base/java.util.LinkedHashMap$LinkedEntryIterator.next(LinkedHashMap.java:751)
at java.base/java.util.LinkedHashMap$LinkedEntryIterator.next(LinkedHashMap.java:749)
at io.ballerina.openapi.core.generators.service.ReturnTypeGenerator.getReturnTypeDescriptorNode(ReturnTypeGenerator.java:118)
at io.ballerina.openapi.core.generators.service.BallerinaServiceGenerator.getResourceFunction(BallerinaServiceGenerator.java:261)
at io.ballerina.openapi.core.generators.service.BallerinaServiceGenerator.applyFiltersForOperations(BallerinaServiceGenerator.java:206)
at io.ballerina.openapi.core.generators.service.BallerinaServiceGenerator.createResourceFunctions(BallerinaServiceGenerator.java:154)
at io.ballerina.openapi.core.generators.service.BallerinaServiceGenerator.generateSyntaxTree(BallerinaServiceGenerator.java:115)
at io.ballerina.openapi.cmd.BallerinaCodeGenerator.generateBallerinaService(BallerinaCodeGenerator.java:395)
at io.ballerina.openapi.cmd.BallerinaCodeGenerator.generateService(BallerinaCodeGenerator.java:220)
at io.ballerina.openapi.cmd.OpenApiCmd.generateServiceFile(OpenApiCmd.java:376)
at io.ballerina.openapi.cmd.OpenApiCmd.openApiToBallerina(OpenApiCmd.java:277)
at io.ballerina.openapi.cmd.OpenApiCmd.execute(OpenApiCmd.java:180)
at java.base/java.util.Optional.ifPresent(Optional.java:183)
at io.ballerina.cli.launcher.Main.main(Main.java:51)
```
Yaml that used:
```openapi
openapi: "3.0.0"
info:
version: 1.0.0
title: OpenApi Petstore
license:
name: MIT
servers:
- url: http://localhost:9090/petstore/v1
paths:
/pets:
get:
summary: List all pets
description: Show a list of pets in the system
operationId: listPets
tags:
- pets
- list
parameters:
- name: limit
in: query
description: How many items to return at one time (max 100)
required: false
schema:
type: integer
format: int32
responses: {}
```
**Affected Versions:**
2201.3.2
**OS, DB, other environment details and versions:**
**Related Issues (optional):**
<!-- Any related issues such as sub tasks, issues reported in other repositories (e.g component repositories), similar problems, etc. -->
**Suggested Labels (optional):**
<!-- Optional comma separated list of suggested labels. Non committers can’t assign labels to issues, so this will help issue creators who are not a committer to suggest possible labels-->
**Suggested Assignees (optional):**
<!--Optional comma separated list of suggested team members who should attend the issue. Non committers can’t assign issues to assignees, so this will help issue creators who are not a committer to suggest possible assignees-->
| non_priority | java util nosuchelementexception when trying to generate the service from the oas description steps to reproduce command that executed bal openapi i snowtooth openapi yaml mode service error ballerina oh no something really went wrong bad sad we appreciate it if you can report the code that broke ballerina in with the log you get below and your sample code we thank you for helping make us better severe log crash null java util nosuchelementexception at java base java util linkedhashmap linkedhashiterator nextnode linkedhashmap java at java base java util linkedhashmap linkedentryiterator next linkedhashmap java at java base java util linkedhashmap linkedentryiterator next linkedhashmap java at io ballerina openapi core generators service returntypegenerator getreturntypedescriptornode returntypegenerator java at io ballerina openapi core generators service ballerinaservicegenerator getresourcefunction ballerinaservicegenerator java at io ballerina openapi core generators service ballerinaservicegenerator applyfiltersforoperations ballerinaservicegenerator java at io ballerina openapi core generators service ballerinaservicegenerator createresourcefunctions ballerinaservicegenerator java at io ballerina openapi core generators service ballerinaservicegenerator generatesyntaxtree ballerinaservicegenerator java at io ballerina openapi cmd ballerinacodegenerator generateballerinaservice ballerinacodegenerator java at io ballerina openapi cmd ballerinacodegenerator generateservice ballerinacodegenerator java at io ballerina openapi cmd openapicmd generateservicefile openapicmd java at io ballerina openapi cmd openapicmd openapitoballerina openapicmd java at io ballerina openapi cmd openapicmd execute openapicmd java at java base java util optional ifpresent optional java at io ballerina cli launcher main main main java yaml that used openapi openapi info version title openapi petstore license name mit servers url paths pets get summary list all pets description show a list of pets in the system operationid listpets tags pets list parameters name limit in query description how many items to return at one time max required false schema type integer format responses affected versions os db other environment details and versions related issues optional suggested labels optional suggested assignees optional | 0 |
411,045 | 12,013,591,707 | IssuesEvent | 2020-04-10 09:13:59 | Skatta/Aapoon-Support-Feedback-Tracker | https://api.github.com/repos/Skatta/Aapoon-Support-Feedback-Tracker | opened | Previously logged in user notifications are receiving to newly logged in user. When 2 users are using same device. | Android Messaging App Priority Medium bug | **Describe the bug**
User 1 has logged in the app and used the app after some time user 1 logged out from the app, User 2 try to do signup in the same device, at that time user 1 received some notifications that notifications are receiving to user 2 when user 2 doing signup.
**To Reproduce**
Steps to reproduce the behavior:
1. In 1 device login to an account.
2. use the app for 2 to 3 min.
3. Logout from the App.
4. Enter a new phone number on the registration page.
5. Register with the new number,
6. Complete phone verification.
7. Stay at phone verification.
8. Take another device.
9. Log in to another account i.e., 3rd one
10. Send messages from chit chat to user 1.
**Expected behavior**
Respective Notifications should receive to the respective user.
**Screenshots**
Please check the video reference.
https://drive.google.com/file/d/1N6155QQ90OQkYTD1x6VlUlauni3yT3gy/view?usp=sharing
**Smartphone (Android):**
- Device: [Mi A3]
- Version [9]
| 1.0 | Previously logged in user notifications are receiving to newly logged in user. When 2 users are using same device. - **Describe the bug**
User 1 has logged in the app and used the app after some time user 1 logged out from the app, User 2 try to do signup in the same device, at that time user 1 received some notifications that notifications are receiving to user 2 when user 2 doing signup.
**To Reproduce**
Steps to reproduce the behavior:
1. In 1 device login to an account.
2. use the app for 2 to 3 min.
3. Logout from the App.
4. Enter a new phone number on the registration page.
5. Register with the new number,
6. Complete phone verification.
7. Stay at phone verification.
8. Take another device.
9. Log in to another account i.e., 3rd one
10. Send messages from chit chat to user 1.
**Expected behavior**
Respective Notifications should receive to the respective user.
**Screenshots**
Please check the video reference.
https://drive.google.com/file/d/1N6155QQ90OQkYTD1x6VlUlauni3yT3gy/view?usp=sharing
**Smartphone (Android):**
- Device: [Mi A3]
- Version [9]
| priority | previously logged in user notifications are receiving to newly logged in user when users are using same device describe the bug user has logged in the app and used the app after some time user logged out from the app user try to do signup in the same device at that time user received some notifications that notifications are receiving to user when user doing signup to reproduce steps to reproduce the behavior in device login to an account use the app for to min logout from the app enter a new phone number on the registration page register with the new number complete phone verification stay at phone verification take another device log in to another account i e one send messages from chit chat to user expected behavior respective notifications should receive to the respective user screenshots please check the video reference smartphone android device version | 1 |
681,493 | 23,312,904,401 | IssuesEvent | 2022-08-08 09:51:30 | PenPow/Sentry | https://api.github.com/repos/PenPow/Sentry | closed | Refactor Commands to use DM Permission | refactor priority:medium semver:minor commands | # Overview
Discord allows us to set the DM permission on deployment, so we can use this to limit moderation commands to guilds! | 1.0 | Refactor Commands to use DM Permission - # Overview
Discord allows us to set the DM permission on deployment, so we can use this to limit moderation commands to guilds! | priority | refactor commands to use dm permission overview discord allows us to set the dm permission on deployment so we can use this to limit moderation commands to guilds | 1 |
130,228 | 5,112,157,871 | IssuesEvent | 2017-01-06 10:02:50 | MatchboxDorry/dorry-web | https://api.github.com/repos/MatchboxDorry/dorry-web | closed | 安装一个app成功的提示 | flag: fixed priority: 1 (urgent) | **Dorry UI Build Versin:**
Version: 0.1.６-alpha
**Operation System:**
Name: Mac mini Os X EI Capitan
Version: 10.11.6
**Browser:**
Browser name: Chrome
Browser version: 54.0.2840.98 (64-bit)
**What I want to do**
我想安装一个app
**Where I am**
market页面
**What I have done**
选择了一个app并安装了它
**What I expect:**
它显示安装中状态，安装成功后弹出操作成功提示
**What really happened**:
1、操作进行状态中只有动态图标，无”installing...”文字显示
2、操作成功的提示里，没有写app名字，只写了 “success,installed" | 1.0 | 安装一个app成功的提示 - **Dorry UI Build Versin:**
Version: 0.1.６-alpha
**Operation System:**
Name: Mac mini Os X EI Capitan
Version: 10.11.6
**Browser:**
Browser name: Chrome
Browser version: 54.0.2840.98 (64-bit)
**What I want to do**
我想安装一个app
**Where I am**
market页面
**What I have done**
选择了一个app并安装了它
**What I expect:**
它显示安装中状态，安装成功后弹出操作成功提示
**What really happened**:
1、操作进行状态中只有动态图标，无”installing...”文字显示
2、操作成功的提示里，没有写app名字，只写了 “success,installed" | priority | 安装一个app成功的提示 dorry ui build versin version alpha operation system name mac mini os x ei capitan version browser browser name chrome browser version bit what i want to do 我想安装一个app where i am market页面 what i have done 选择了一个app并安装了它 what i expect 它显示安装中状态，安装成功后弹出操作成功提示 what really happened 、操作进行状态中只有动态图标，无”installing ”文字显示 、操作成功的提示里，没有写app名字，只写了 “success installed | 1 |
314,724 | 23,534,540,602 | IssuesEvent | 2022-08-19 19:01:09 | JoeBussard/polywordleapi | https://api.github.com/repos/JoeBussard/polywordleapi | closed | Calculate runtimes | documentation | Calculate runtimes for guess-checking algorithms considering length of word could be variable input (n) | 1.0 | Calculate runtimes - Calculate runtimes for guess-checking algorithms considering length of word could be variable input (n) | non_priority | calculate runtimes calculate runtimes for guess checking algorithms considering length of word could be variable input n | 0 |
95,057 | 10,864,956,298 | IssuesEvent | 2019-11-14 17:56:18 | intel/mkl-dnn | https://api.github.com/repos/intel/mkl-dnn | opened | Binary distributions break copyright licensing | documentation | # Summary
The Binary distributions break licensing laws because they do not include the licenses of the 3rd party libraries that they use.
# Additional details
The Linux, Windows and macOS distributions are breaking copyright licensing laws because they do not include the text of the 3rd party licenses.
The `LICENSE` file included with the distributions reference the 3rd party libraries that it uses such as:
> DNNL includes components with separate copyright
> notices and license terms.
>
> XByak, 3-clause BSD license
> Copyright (c) 2007 MITSUNARI Shigeo
> See full copyright notice and license text in src/cpu/xbyak/COPYRIGHT
>
However the binary distributions do not actually include these 3rd party COPYRIGHT files, which breaks the 3rd Party license. In particular the following text from the COPYRIGHT files.
> Redistributions in binary form must reproduce the above copyright notice,
> this list of conditions and the following disclaimer in the documentation
> and/or other materials provided with the distribution.
In short the entire COPYRIGHT file of the 3rd Party Library needs to be included the binary distribution's LICENSE file or as separate files for the specific libraries.
| 1.0 | Binary distributions break copyright licensing - # Summary
The Binary distributions break licensing laws because they do not include the licenses of the 3rd party libraries that they use.
# Additional details
The Linux, Windows and macOS distributions are breaking copyright licensing laws because they do not include the text of the 3rd party licenses.
The `LICENSE` file included with the distributions reference the 3rd party libraries that it uses such as:
> DNNL includes components with separate copyright
> notices and license terms.
>
> XByak, 3-clause BSD license
> Copyright (c) 2007 MITSUNARI Shigeo
> See full copyright notice and license text in src/cpu/xbyak/COPYRIGHT
>
However the binary distributions do not actually include these 3rd party COPYRIGHT files, which breaks the 3rd Party license. In particular the following text from the COPYRIGHT files.
> Redistributions in binary form must reproduce the above copyright notice,
> this list of conditions and the following disclaimer in the documentation
> and/or other materials provided with the distribution.
In short the entire COPYRIGHT file of the 3rd Party Library needs to be included the binary distribution's LICENSE file or as separate files for the specific libraries.
| non_priority | binary distributions break copyright licensing summary the binary distributions break licensing laws because they do not include the licenses of the party libraries that they use additional details the linux windows and macos distributions are breaking copyright licensing laws because they do not include the text of the party licenses the license file included with the distributions reference the party libraries that it uses such as dnnl includes components with separate copyright notices and license terms xbyak clause bsd license copyright c mitsunari shigeo see full copyright notice and license text in src cpu xbyak copyright however the binary distributions do not actually include these party copyright files which breaks the party license in particular the following text from the copyright files redistributions in binary form must reproduce the above copyright notice this list of conditions and the following disclaimer in the documentation and or other materials provided with the distribution in short the entire copyright file of the party library needs to be included the binary distribution s license file or as separate files for the specific libraries | 0 |
458,984 | 13,184,680,828 | IssuesEvent | 2020-08-12 19:53:39 | zephyrproject-rtos/zephyr | https://api.github.com/repos/zephyrproject-rtos/zephyr | closed | STM32F407 I2C driver hangs | area: I2C bug platform: STM32 priority: low | The STM32F407 I2C driver hangs from time to time where it waits on the semaphore in the driver. When that happens the signal on the bus looks like this (SDA = yellow, SCL = green);
To work around it I added a timeout to the k_sem_take calls, but I have not found the real cause of the problem. On the scope is to see it must go wrong real early, because it generates a start-stop without any data.
This is on the 1.14 branch, but I cherry-picked most commits (like the new timeout handling) from master. The target is a STM32F407 so it uses the V1 driver. Also not using IRQ's but polling causes the problem to happen less but it still happens.
| 1.0 | STM32F407 I2C driver hangs - The STM32F407 I2C driver hangs from time to time where it waits on the semaphore in the driver. When that happens the signal on the bus looks like this (SDA = yellow, SCL = green);
To work around it I added a timeout to the k_sem_take calls, but I have not found the real cause of the problem. On the scope is to see it must go wrong real early, because it generates a start-stop without any data.
This is on the 1.14 branch, but I cherry-picked most commits (like the new timeout handling) from master. The target is a STM32F407 so it uses the V1 driver. Also not using IRQ's but polling causes the problem to happen less but it still happens.
| priority | driver hangs the driver hangs from time to time where it waits on the semaphore in the driver when that happens the signal on the bus looks like this sda yellow scl green to work around it i added a timeout to the k sem take calls but i have not found the real cause of the problem on the scope is to see it must go wrong real early because it generates a start stop without any data this is on the branch but i cherry picked most commits like the new timeout handling from master the target is a so it uses the driver also not using irq s but polling causes the problem to happen less but it still happens | 1 |
654,973 | 21,675,119,348 | IssuesEvent | 2022-05-08 15:35:19 | RestoneAGX/RTG_Demo | https://api.github.com/repos/RestoneAGX/RTG_Demo | opened | Debug Menu | enhancement Priority: Low | A menu to see information like Progression state, Enemy Stats, and most Data that the player won't or shouldn't see, but we should see to check if everything is working. | 1.0 | Debug Menu - A menu to see information like Progression state, Enemy Stats, and most Data that the player won't or shouldn't see, but we should see to check if everything is working. | priority | debug menu a menu to see information like progression state enemy stats and most data that the player won t or shouldn t see but we should see to check if everything is working | 1 |
101,373 | 31,073,585,814 | IssuesEvent | 2023-08-12 07:39:40 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | opened | [wasm] WBT `SatelliteAssembliesTests.CheckThatSatelliteAssembliesAreNotAOTed` failing | arch-wasm blocking-clean-ci area-Build-mono test-failure | Test failing with [rolling build](https://dev.azure.com/dnceng-public/public/_build/results?buildId=371479&view=results):
```
[4/5] System.Private.CoreLib.dll.bc -> System.Private.CoreLib.dll.o
WasmApp.Native.targets(379,5): error : Failed to compile /root/helix/work/workitem/e/wbt/ddpnbu30_we1/obj/Release/net8.0/browser-wasm/wasm/for-publish/aot-instances.dll.bc -> /root/helix/work/workitem/e/wbt/ddpnbu30_we1/obj/Release/net8.0/browser-wasm/wasm/for-publish/aot-instances.dll.o
WasmApp.Native.targets(379,5): error : emcc: warning: linker setting ignored during compilation: 'EXPORT_ES6' [-Wunused-command-line-argument]
WasmApp.Native.targets(379,5): error : Killed
```
`WasmApp.Native.targets(379,5): error : emcc: error: '/root/helix/work/workitem/e/dotnet-latest/packs/Microsoft.NET.Runtime.Emscripten.3.1.34.Sdk.linux-x64/8.0.0-rc.1.23411.1/tools/bin/clang++ -target wasm32-unknown-emscripten -fvisibility=default -mllvm -combiner-global-alias-analysis=false -mllvm -wasm-enable-sjlj -mllvm -disable-lsr -DEMSCRIPTEN --sysroot=/root/helix/work/workitem/e/dotnet-latest/packs/Microsoft.NET.Runtime.Emscripten.3.1.34.Cache.linux-x64/8.0.0-rc.1.23411.1/tools/emscripten/cache/sysroot -Xclang -iwithsysroot/include/fakesdl -Xclang -iwithsysroot/include/compat -msimd128 -O0 -g3 -fwasm-exceptions -c /root/helix/work/workitem/e/wbt/ddpnbu30_we1/obj/Release/net8.0/browser-wasm/wasm/for-publish/aot-instances.dll.bc -o /tmp/tmpeo8pzM.tmp' failed (returned 137) [took 128.818s] `
[Changes since last passing rolling build](https://github.com/dotnet/runtime/compare/64a67710163...55828b9aa91).
This includes commits from @pavelsavara @ivanpovazan | 1.0 | [wasm] WBT `SatelliteAssembliesTests.CheckThatSatelliteAssembliesAreNotAOTed` failing - Test failing with [rolling build](https://dev.azure.com/dnceng-public/public/_build/results?buildId=371479&view=results):
```
[4/5] System.Private.CoreLib.dll.bc -> System.Private.CoreLib.dll.o
WasmApp.Native.targets(379,5): error : Failed to compile /root/helix/work/workitem/e/wbt/ddpnbu30_we1/obj/Release/net8.0/browser-wasm/wasm/for-publish/aot-instances.dll.bc -> /root/helix/work/workitem/e/wbt/ddpnbu30_we1/obj/Release/net8.0/browser-wasm/wasm/for-publish/aot-instances.dll.o
WasmApp.Native.targets(379,5): error : emcc: warning: linker setting ignored during compilation: 'EXPORT_ES6' [-Wunused-command-line-argument]
WasmApp.Native.targets(379,5): error : Killed
```
`WasmApp.Native.targets(379,5): error : emcc: error: '/root/helix/work/workitem/e/dotnet-latest/packs/Microsoft.NET.Runtime.Emscripten.3.1.34.Sdk.linux-x64/8.0.0-rc.1.23411.1/tools/bin/clang++ -target wasm32-unknown-emscripten -fvisibility=default -mllvm -combiner-global-alias-analysis=false -mllvm -wasm-enable-sjlj -mllvm -disable-lsr -DEMSCRIPTEN --sysroot=/root/helix/work/workitem/e/dotnet-latest/packs/Microsoft.NET.Runtime.Emscripten.3.1.34.Cache.linux-x64/8.0.0-rc.1.23411.1/tools/emscripten/cache/sysroot -Xclang -iwithsysroot/include/fakesdl -Xclang -iwithsysroot/include/compat -msimd128 -O0 -g3 -fwasm-exceptions -c /root/helix/work/workitem/e/wbt/ddpnbu30_we1/obj/Release/net8.0/browser-wasm/wasm/for-publish/aot-instances.dll.bc -o /tmp/tmpeo8pzM.tmp' failed (returned 137) [took 128.818s] `
[Changes since last passing rolling build](https://github.com/dotnet/runtime/compare/64a67710163...55828b9aa91).
This includes commits from @pavelsavara @ivanpovazan | non_priority | wbt satelliteassembliestests checkthatsatelliteassembliesarenotaoted failing test failing with system private corelib dll bc system private corelib dll o wasmapp native targets error failed to compile root helix work workitem e wbt obj release browser wasm wasm for publish aot instances dll bc root helix work workitem e wbt obj release browser wasm wasm for publish aot instances dll o wasmapp native targets error emcc warning linker setting ignored during compilation export wasmapp native targets error killed wasmapp native targets error emcc error root helix work workitem e dotnet latest packs microsoft net runtime emscripten sdk linux rc tools bin clang target unknown emscripten fvisibility default mllvm combiner global alias analysis false mllvm wasm enable sjlj mllvm disable lsr demscripten sysroot root helix work workitem e dotnet latest packs microsoft net runtime emscripten cache linux rc tools emscripten cache sysroot xclang iwithsysroot include fakesdl xclang iwithsysroot include compat fwasm exceptions c root helix work workitem e wbt obj release browser wasm wasm for publish aot instances dll bc o tmp tmp failed returned this includes commits from pavelsavara ivanpovazan | 0 |
590,239 | 17,774,471,909 | IssuesEvent | 2021-08-30 17:21:33 | Warcraft-GoA-Development-Team/Warcraft-Guardians-of-Azeroth-2 | https://api.github.com/repos/Warcraft-GoA-Development-Team/Warcraft-Guardians-of-Azeroth-2 | opened | Goblin Burials | new feature :star: suggestion :question: lore :books: priority medium :grey_exclamation: | <!--
**DO NOT REMOVE PRE-EXISTING LINES**
------------------------------------------------------------------------------------------------------------
-->
**Describe your suggestion in full detail below:**
Goblins may have special burials (working like sky burials) where they spend a big part of their money to get piety and dynasty prestige.
https://wowpedia.fandom.com/wiki/Goblin#Beliefs | 1.0 | Goblin Burials - <!--
**DO NOT REMOVE PRE-EXISTING LINES**
------------------------------------------------------------------------------------------------------------
-->
**Describe your suggestion in full detail below:**
Goblins may have special burials (working like sky burials) where they spend a big part of their money to get piety and dynasty prestige.
https://wowpedia.fandom.com/wiki/Goblin#Beliefs | priority | goblin burials do not remove pre existing lines describe your suggestion in full detail below goblins may have special burials working like sky burials where they spend a big part of their money to get piety and dynasty prestige | 1 |
260,462 | 27,784,414,407 | IssuesEvent | 2023-03-17 01:06:09 | AlexRogalskiy/javascript-tools | https://api.github.com/repos/AlexRogalskiy/javascript-tools | opened | CVE-2020-11023 (Medium) detected in jquery-1.8.1.min.js | Mend: dependency security vulnerability | ## CVE-2020-11023 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-1.8.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.min.js</a></p>
<p>Path to dependency file: /node_modules/redeyed/examples/browser/index.html</p>
<p>Path to vulnerable library: /node_modules/redeyed/examples/browser/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.8.1.min.js** (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>
In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
<p>Publish Date: 2020-04-29
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-11023>CVE-2020-11023</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.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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/jquery/jquery/security/advisories/GHSA-jpcq-cgw6-v4j6,https://github.com/rails/jquery-rails/blob/master/CHANGELOG.md#440">https://github.com/jquery/jquery/security/advisories/GHSA-jpcq-cgw6-v4j6,https://github.com/rails/jquery-rails/blob/master/CHANGELOG.md#440</a></p>
<p>Release Date: 2020-04-29</p>
<p>Fix Resolution: jquery - 3.5.0;jquery-rails - 4.4.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 | CVE-2020-11023 (Medium) detected in jquery-1.8.1.min.js - ## CVE-2020-11023 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-1.8.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.min.js</a></p>
<p>Path to dependency file: /node_modules/redeyed/examples/browser/index.html</p>
<p>Path to vulnerable library: /node_modules/redeyed/examples/browser/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.8.1.min.js** (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>
In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
<p>Publish Date: 2020-04-29
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-11023>CVE-2020-11023</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.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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/jquery/jquery/security/advisories/GHSA-jpcq-cgw6-v4j6,https://github.com/rails/jquery-rails/blob/master/CHANGELOG.md#440">https://github.com/jquery/jquery/security/advisories/GHSA-jpcq-cgw6-v4j6,https://github.com/rails/jquery-rails/blob/master/CHANGELOG.md#440</a></p>
<p>Release Date: 2020-04-29</p>
<p>Fix Resolution: jquery - 3.5.0;jquery-rails - 4.4.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 | cve medium detected in jquery min js cve medium severity vulnerability vulnerable library jquery min js javascript library for dom operations library home page a href path to dependency file node modules redeyed examples browser index html path to vulnerable library node modules redeyed examples browser index html dependency hierarchy x jquery min js vulnerable library found in base branch master vulnerability details in jquery versions greater than or equal to and before passing html containing elements from untrusted sources even after sanitizing it to one of jquery s dom manipulation methods i e html append and others may execute untrusted code this problem is patched in jquery publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jquery jquery rails step up your open source security game with mend | 0 |
162,148 | 13,882,989,182 | IssuesEvent | 2020-10-18 09:48:09 | Project-Books/book-project | https://api.github.com/repos/Project-Books/book-project | opened | Add instructions for upstream | documentation | Add instructions to the contributing document that link to GitHub's documentation on creating an upstream remote so that contributors can keep their fork in sync with this repository | 1.0 | Add instructions for upstream - Add instructions to the contributing document that link to GitHub's documentation on creating an upstream remote so that contributors can keep their fork in sync with this repository | non_priority | add instructions for upstream add instructions to the contributing document that link to github s documentation on creating an upstream remote so that contributors can keep their fork in sync with this repository | 0 |
202,041 | 7,043,482,274 | IssuesEvent | 2017-12-31 07:00:47 | ChrisCScott/forecaster | https://api.github.com/repos/ChrisCScott/forecaster | closed | Implement spousal RRSPs | canada medium priority RRSP | It may be possible to do this without subclassing `RRSP`, or via a very limited subclass (simply by setting `contributor = owner.spouse`).
This hasn't been tested, so the first order of business is to implement some tests and see how the existing code works with the logic in `TransactionStrategy` and other classes. | 1.0 | Implement spousal RRSPs - It may be possible to do this without subclassing `RRSP`, or via a very limited subclass (simply by setting `contributor = owner.spouse`).
This hasn't been tested, so the first order of business is to implement some tests and see how the existing code works with the logic in `TransactionStrategy` and other classes. | priority | implement spousal rrsps it may be possible to do this without subclassing rrsp or via a very limited subclass simply by setting contributor owner spouse this hasn t been tested so the first order of business is to implement some tests and see how the existing code works with the logic in transactionstrategy and other classes | 1 |
146,306 | 5,615,156,045 | IssuesEvent | 2017-04-03 14:03:32 | laradock/laradock | https://api.github.com/repos/laradock/laradock | opened | CI integration to auto-generate the Hugo docs | Priority: Medium Type: Enhancement | Noticed the contributions to the docs became so slow, after moving to hugo... Would cool if anyone can find a good CI service to build the site automatically after each commit. This way users will only update the text in the markdown files without worrying about regenerating the site. | 1.0 | CI integration to auto-generate the Hugo docs - Noticed the contributions to the docs became so slow, after moving to hugo... Would cool if anyone can find a good CI service to build the site automatically after each commit. This way users will only update the text in the markdown files without worrying about regenerating the site. | priority | ci integration to auto generate the hugo docs noticed the contributions to the docs became so slow after moving to hugo would cool if anyone can find a good ci service to build the site automatically after each commit this way users will only update the text in the markdown files without worrying about regenerating the site | 1 |
181,408 | 6,659,422,343 | IssuesEvent | 2017-10-01 11:24:16 | angular/angular-cli | https://api.github.com/repos/angular/angular-cli | closed | Production build errors. | priority: 2 (required) severity4: regression |
```
- [x ] bug report -> please search issues before submitting
- [ ] feature request
```
### Versions.
@angular/cli: 1.0.4
node: 7.8.0
os: darwin x64
@angular/animations: 4.1.3
@angular/common: 4.0.1
@angular/compiler: 4.0.1
@angular/core: 4.0.1
@angular/flex-layout: 2.0.0-beta.7
@angular/forms: 4.0.1
@angular/http: 4.0.1
@angular/material: 2.0.0-beta.3
@angular/platform-browser: 4.0.1
@angular/platform-browser-dynamic: 4.0.1
@angular/router: 4.0.1
@angular/cli: 1.0.4
@angular/compiler-cli: 2.4.10
### Repro steps.
`ng build --prod` or `ng build --prod --aot`
### The log given by the failure.
```
ERROR in ./src/$$_gendir/~/angular2-token/lib/a2t-ui/a2t-update-password/a2t-update-password.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../../@angular/core' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/node_modules/angular2-token/lib/a2t-ui/a2t-update-password'
@ ./src/$$_gendir/~/angular2-token/lib/a2t-ui/a2t-update-password/a2t-update-password.component.ngfactory.ts 7:0-62
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/~/angular2-token/lib/a2t-ui/a2t-update-password/a2t-update-password.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../../@angular/router' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/node_modules/angular2-token/lib/a2t-ui/a2t-update-password'
@ ./src/$$_gendir/~/angular2-token/lib/a2t-ui/a2t-update-password/a2t-update-password.component.ngfactory.ts 17:0-65
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/core-module/components/navbar/navbar.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/core' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/core-module/components/navbar'
@ ./src/$$_gendir/app/core-module/components/navbar/navbar.component.ngfactory.ts 8:0-59
@ ./src/$$_gendir/app/not-found/not-found.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/core-module/components/navbar/navbar.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/material' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/core-module/components/navbar'
@ ./src/$$_gendir/app/core-module/components/navbar/navbar.component.ngfactory.ts 10:0-63
@ ./src/$$_gendir/app/not-found/not-found.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/core-module/components/navbar/navbar.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/router' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/core-module/components/navbar'
@ ./src/$$_gendir/app/core-module/components/navbar/navbar.component.ngfactory.ts 17:0-62
@ ./src/$$_gendir/app/not-found/not-found.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/core-module/components/navbar/navbar.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/common' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/core-module/components/navbar'
@ ./src/$$_gendir/app/core-module/components/navbar/navbar.component.ngfactory.ts 18:0-62
@ ./src/$$_gendir/app/not-found/not-found.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/core-module/components/footer/footer.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/core' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/core-module/components/footer'
@ ./src/$$_gendir/app/core-module/components/footer/footer.component.ngfactory.ts 8:0-59
@ ./src/$$_gendir/app/not-found/not-found.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/core-module/components/footer/footer.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/material' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/core-module/components/footer'
@ ./src/$$_gendir/app/core-module/components/footer/footer.component.ngfactory.ts 10:0-63
@ ./src/$$_gendir/app/not-found/not-found.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/front-module/components/category-navbar/category-navbar.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/core' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/front-module/components/category-navbar'
@ ./src/$$_gendir/app/front-module/components/category-navbar/category-navbar.component.ngfactory.ts 8:0-59
@ ./src/$$_gendir/app/front-module/containers/home/home.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/front-module/components/category-navbar/category-navbar.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/router' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/front-module/components/category-navbar'
@ ./src/$$_gendir/app/front-module/components/category-navbar/category-navbar.component.ngfactory.ts 9:0-61
@ ./src/$$_gendir/app/front-module/containers/home/home.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/front-module/components/category-navbar/category-navbar.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/common' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/front-module/components/category-navbar'
@ ./src/$$_gendir/app/front-module/components/category-navbar/category-navbar.component.ngfactory.ts 10:0-61
@ ./src/$$_gendir/app/front-module/containers/home/home.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/front-module/components/category-navbar/category-navbar.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/material' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/front-module/components/category-navbar'
@ ./src/$$_gendir/app/front-module/components/category-navbar/category-navbar.component.ngfactory.ts 13:0-63
@ ./src/$$_gendir/app/front-module/containers/home/home.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/front-module/components/most-recent-read/most-recent-read.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/core' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/front-module/components/most-recent-read'
@ ./src/$$_gendir/app/front-module/components/most-recent-read/most-recent-read.component.ngfactory.ts 8:0-59
@ ./src/$$_gendir/app/front-module/containers/category-articles/category-articles.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/front-module/components/most-recent-read/most-recent-read.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/router' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/front-module/components/most-recent-read'
@ ./src/$$_gendir/app/front-module/components/most-recent-read/most-recent-read.component.ngfactory.ts 9:0-61
@ ./src/$$_gendir/app/front-module/containers/category-articles/category-articles.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
```
I am getting hundreds of errors with either "module not found", "Property 'parent' does not exist on type 'AppModuleInjector'" and so on. The application works without problem with `ng build` and `ng serve`. Happens only when I add the `--prod` or `--aot` options.
| 1.0 | Production build errors. -
```
- [x ] bug report -> please search issues before submitting
- [ ] feature request
```
### Versions.
@angular/cli: 1.0.4
node: 7.8.0
os: darwin x64
@angular/animations: 4.1.3
@angular/common: 4.0.1
@angular/compiler: 4.0.1
@angular/core: 4.0.1
@angular/flex-layout: 2.0.0-beta.7
@angular/forms: 4.0.1
@angular/http: 4.0.1
@angular/material: 2.0.0-beta.3
@angular/platform-browser: 4.0.1
@angular/platform-browser-dynamic: 4.0.1
@angular/router: 4.0.1
@angular/cli: 1.0.4
@angular/compiler-cli: 2.4.10
### Repro steps.
`ng build --prod` or `ng build --prod --aot`
### The log given by the failure.
```
ERROR in ./src/$$_gendir/~/angular2-token/lib/a2t-ui/a2t-update-password/a2t-update-password.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../../@angular/core' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/node_modules/angular2-token/lib/a2t-ui/a2t-update-password'
@ ./src/$$_gendir/~/angular2-token/lib/a2t-ui/a2t-update-password/a2t-update-password.component.ngfactory.ts 7:0-62
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/~/angular2-token/lib/a2t-ui/a2t-update-password/a2t-update-password.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../../@angular/router' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/node_modules/angular2-token/lib/a2t-ui/a2t-update-password'
@ ./src/$$_gendir/~/angular2-token/lib/a2t-ui/a2t-update-password/a2t-update-password.component.ngfactory.ts 17:0-65
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/core-module/components/navbar/navbar.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/core' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/core-module/components/navbar'
@ ./src/$$_gendir/app/core-module/components/navbar/navbar.component.ngfactory.ts 8:0-59
@ ./src/$$_gendir/app/not-found/not-found.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/core-module/components/navbar/navbar.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/material' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/core-module/components/navbar'
@ ./src/$$_gendir/app/core-module/components/navbar/navbar.component.ngfactory.ts 10:0-63
@ ./src/$$_gendir/app/not-found/not-found.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/core-module/components/navbar/navbar.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/router' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/core-module/components/navbar'
@ ./src/$$_gendir/app/core-module/components/navbar/navbar.component.ngfactory.ts 17:0-62
@ ./src/$$_gendir/app/not-found/not-found.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/core-module/components/navbar/navbar.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/common' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/core-module/components/navbar'
@ ./src/$$_gendir/app/core-module/components/navbar/navbar.component.ngfactory.ts 18:0-62
@ ./src/$$_gendir/app/not-found/not-found.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/core-module/components/footer/footer.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/core' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/core-module/components/footer'
@ ./src/$$_gendir/app/core-module/components/footer/footer.component.ngfactory.ts 8:0-59
@ ./src/$$_gendir/app/not-found/not-found.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/core-module/components/footer/footer.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/material' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/core-module/components/footer'
@ ./src/$$_gendir/app/core-module/components/footer/footer.component.ngfactory.ts 10:0-63
@ ./src/$$_gendir/app/not-found/not-found.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/front-module/components/category-navbar/category-navbar.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/core' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/front-module/components/category-navbar'
@ ./src/$$_gendir/app/front-module/components/category-navbar/category-navbar.component.ngfactory.ts 8:0-59
@ ./src/$$_gendir/app/front-module/containers/home/home.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/front-module/components/category-navbar/category-navbar.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/router' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/front-module/components/category-navbar'
@ ./src/$$_gendir/app/front-module/components/category-navbar/category-navbar.component.ngfactory.ts 9:0-61
@ ./src/$$_gendir/app/front-module/containers/home/home.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/front-module/components/category-navbar/category-navbar.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/common' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/front-module/components/category-navbar'
@ ./src/$$_gendir/app/front-module/components/category-navbar/category-navbar.component.ngfactory.ts 10:0-61
@ ./src/$$_gendir/app/front-module/containers/home/home.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/front-module/components/category-navbar/category-navbar.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/material' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/front-module/components/category-navbar'
@ ./src/$$_gendir/app/front-module/components/category-navbar/category-navbar.component.ngfactory.ts 13:0-63
@ ./src/$$_gendir/app/front-module/containers/home/home.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/front-module/components/most-recent-read/most-recent-read.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/core' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/front-module/components/most-recent-read'
@ ./src/$$_gendir/app/front-module/components/most-recent-read/most-recent-read.component.ngfactory.ts 8:0-59
@ ./src/$$_gendir/app/front-module/containers/category-articles/category-articles.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
ERROR in ./src/$$_gendir/app/front-module/components/most-recent-read/most-recent-read.component.ngfactory.ts
Module not found: Error: Can't resolve '../../../../../../@angular/router' in '/Users/hgeorgiev/projects/angular 2/cms-client/src/$$_gendir/app/front-module/components/most-recent-read'
@ ./src/$$_gendir/app/front-module/components/most-recent-read/most-recent-read.component.ngfactory.ts 9:0-61
@ ./src/$$_gendir/app/front-module/containers/category-articles/category-articles.component.ngfactory.ts
@ ./src/$$_gendir/app/app.module.ngfactory.ts
@ ./src/main.ts
@ multi ./src/main.ts
```
I am getting hundreds of errors with either "module not found", "Property 'parent' does not exist on type 'AppModuleInjector'" and so on. The application works without problem with `ng build` and `ng serve`. Happens only when I add the `--prod` or `--aot` options.
| priority | production build errors bug report please search issues before submitting feature request versions angular cli node os darwin angular animations angular common angular compiler angular core angular flex layout beta angular forms angular http angular material beta angular platform browser angular platform browser dynamic angular router angular cli angular compiler cli repro steps ng build prod or ng build prod aot the log given by the failure error in src gendir token lib ui update password update password component ngfactory ts module not found error can t resolve angular core in users hgeorgiev projects angular cms client src gendir node modules token lib ui update password src gendir token lib ui update password update password component ngfactory ts src gendir app app module ngfactory ts src main ts multi src main ts error in src gendir token lib ui update password update password component ngfactory ts module not found error can t resolve angular router in users hgeorgiev projects angular cms client src gendir node modules token lib ui update password src gendir token lib ui update password update password component ngfactory ts src gendir app app module ngfactory ts src main ts multi src main ts error in src gendir app core module components navbar navbar component ngfactory ts module not found error can t resolve angular core in users hgeorgiev projects angular cms client src gendir app core module components navbar src gendir app core module components navbar navbar component ngfactory ts src gendir app not found not found component ngfactory ts src gendir app app module ngfactory ts src main ts multi src main ts error in src gendir app core module components navbar navbar component ngfactory ts module not found error can t resolve angular material in users hgeorgiev projects angular cms client src gendir app core module components navbar src gendir app core module components navbar navbar component ngfactory ts src gendir app not found not found component ngfactory ts src gendir app app module ngfactory ts src main ts multi src main ts error in src gendir app core module components navbar navbar component ngfactory ts module not found error can t resolve angular router in users hgeorgiev projects angular cms client src gendir app core module components navbar src gendir app core module components navbar navbar component ngfactory ts src gendir app not found not found component ngfactory ts src gendir app app module ngfactory ts src main ts multi src main ts error in src gendir app core module components navbar navbar component ngfactory ts module not found error can t resolve angular common in users hgeorgiev projects angular cms client src gendir app core module components navbar src gendir app core module components navbar navbar component ngfactory ts src gendir app not found not found component ngfactory ts src gendir app app module ngfactory ts src main ts multi src main ts error in src gendir app core module components footer footer component ngfactory ts module not found error can t resolve angular core in users hgeorgiev projects angular cms client src gendir app core module components footer src gendir app core module components footer footer component ngfactory ts src gendir app not found not found component ngfactory ts src gendir app app module ngfactory ts src main ts multi src main ts error in src gendir app core module components footer footer component ngfactory ts module not found error can t resolve angular material in users hgeorgiev projects angular cms client src gendir app core module components footer src gendir app core module components footer footer component ngfactory ts src gendir app not found not found component ngfactory ts src gendir app app module ngfactory ts src main ts multi src main ts error in src gendir app front module components category navbar category navbar component ngfactory ts module not found error can t resolve angular core in users hgeorgiev projects angular cms client src gendir app front module components category navbar src gendir app front module components category navbar category navbar component ngfactory ts src gendir app front module containers home home component ngfactory ts src gendir app app module ngfactory ts src main ts multi src main ts error in src gendir app front module components category navbar category navbar component ngfactory ts module not found error can t resolve angular router in users hgeorgiev projects angular cms client src gendir app front module components category navbar src gendir app front module components category navbar category navbar component ngfactory ts src gendir app front module containers home home component ngfactory ts src gendir app app module ngfactory ts src main ts multi src main ts error in src gendir app front module components category navbar category navbar component ngfactory ts module not found error can t resolve angular common in users hgeorgiev projects angular cms client src gendir app front module components category navbar src gendir app front module components category navbar category navbar component ngfactory ts src gendir app front module containers home home component ngfactory ts src gendir app app module ngfactory ts src main ts multi src main ts error in src gendir app front module components category navbar category navbar component ngfactory ts module not found error can t resolve angular material in users hgeorgiev projects angular cms client src gendir app front module components category navbar src gendir app front module components category navbar category navbar component ngfactory ts src gendir app front module containers home home component ngfactory ts src gendir app app module ngfactory ts src main ts multi src main ts error in src gendir app front module components most recent read most recent read component ngfactory ts module not found error can t resolve angular core in users hgeorgiev projects angular cms client src gendir app front module components most recent read src gendir app front module components most recent read most recent read component ngfactory ts src gendir app front module containers category articles category articles component ngfactory ts src gendir app app module ngfactory ts src main ts multi src main ts error in src gendir app front module components most recent read most recent read component ngfactory ts module not found error can t resolve angular router in users hgeorgiev projects angular cms client src gendir app front module components most recent read src gendir app front module components most recent read most recent read component ngfactory ts src gendir app front module containers category articles category articles component ngfactory ts src gendir app app module ngfactory ts src main ts multi src main ts i am getting hundreds of errors with either module not found property parent does not exist on type appmoduleinjector and so on the application works without problem with ng build and ng serve happens only when i add the prod or aot options | 1 |
61,278 | 7,457,351,751 | IssuesEvent | 2018-03-30 03:41:08 | aspnet/KestrelHttpServer | https://api.github.com/repos/aspnet/KestrelHttpServer | closed | Make Kestrel TryAdd when adding it's IServer implementation | 1 - Ready breaking-change enhancement needs design | For ANCM in-proc to work with scenarios like:
```c#
WebHostBuilder.CreateDefaultWebHostBuilder() // which calls UseKestrel() and UseIISIntegration();
.UseKestrel();
```
we need the call to UseIISIntegration to always add it's IServer implementation rather than Kestrel overriding it.
As we want out-of-proc and in-proc to work without code changes, we will need [Kestrel to TryAdd it's server implementation](https://github.com/aspnet/KestrelHttpServer/blob/dev/src/Kestrel/WebHostBuilderKestrelExtensions.cs#L35).
cc/ @davidfowl @pakrym @Tratcher | 1.0 | Make Kestrel TryAdd when adding it's IServer implementation - For ANCM in-proc to work with scenarios like:
```c#
WebHostBuilder.CreateDefaultWebHostBuilder() // which calls UseKestrel() and UseIISIntegration();
.UseKestrel();
```
we need the call to UseIISIntegration to always add it's IServer implementation rather than Kestrel overriding it.
As we want out-of-proc and in-proc to work without code changes, we will need [Kestrel to TryAdd it's server implementation](https://github.com/aspnet/KestrelHttpServer/blob/dev/src/Kestrel/WebHostBuilderKestrelExtensions.cs#L35).
cc/ @davidfowl @pakrym @Tratcher | non_priority | make kestrel tryadd when adding it s iserver implementation for ancm in proc to work with scenarios like c webhostbuilder createdefaultwebhostbuilder which calls usekestrel and useiisintegration usekestrel we need the call to useiisintegration to always add it s iserver implementation rather than kestrel overriding it as we want out of proc and in proc to work without code changes we will need cc davidfowl pakrym tratcher | 0 |
27,126 | 4,876,692,095 | IssuesEvent | 2016-11-16 13:41:01 | bridgedotnet/Bridge | https://api.github.com/repos/bridgedotnet/Bridge | closed | "fileName" option in bridge.json requires outputBy Project | defect | Reported on the [forum](http://forums.bridge.net/forum/bridge-net-pro/bugs/3061-filename-option-in-bridge-json-ignored-in-library-projects).
### Expected
**bridge.json**
```js
{
"fileName": "code.js",
}
```
Produces outputs that are equivalent to `"outputBy": "Project"`.
### Actual
**bridge.json**
```js
{
"fileName": "code.js"
}
```
Produces outputs that are equivalent to `"outputBy": "Namespace"`.
### Workaround
**bridge.json**
```js
{
"fileName": "code.js",
"outputBy": "Project"
}
```
| 1.0 | "fileName" option in bridge.json requires outputBy Project - Reported on the [forum](http://forums.bridge.net/forum/bridge-net-pro/bugs/3061-filename-option-in-bridge-json-ignored-in-library-projects).
### Expected
**bridge.json**
```js
{
"fileName": "code.js",
}
```
Produces outputs that are equivalent to `"outputBy": "Project"`.
### Actual
**bridge.json**
```js
{
"fileName": "code.js"
}
```
Produces outputs that are equivalent to `"outputBy": "Namespace"`.
### Workaround
**bridge.json**
```js
{
"fileName": "code.js",
"outputBy": "Project"
}
```
| non_priority | filename option in bridge json requires outputby project reported on the expected bridge json js filename code js produces outputs that are equivalent to outputby project actual bridge json js filename code js produces outputs that are equivalent to outputby namespace workaround bridge json js filename code js outputby project | 0 |
5,993 | 2,581,669,196 | IssuesEvent | 2015-02-14 09:07:59 | dartsim/dart | https://api.github.com/repos/dartsim/dart | closed | Bug in World->removeSkeleton() | Kind: Bug Priority: High | Hi, here a report on the following bug:
Function: removeSkeleton()
Location: dart/simulation/World.cpp (line 246)
Error: The function should delete the skeleton name from the mNameMgrForSkeletons, which is not currently being done.
Fix: Add the following 2 lines probably after line 265 for safe checks:
// Remove from name manager
mNameMgrForSkeletons.removeName( _skeleton->getName() );
I am using a program in which I constantly add/delete skeletons with the same name for some online object detection. I was getting SEGFAULTS after deleting an skeleton and then trying to add it later (the NameManager thought the object still existed, but the Skeleton had been already erased).
After adding the couple of lines mentioned above, the issue dissapared. | 1.0 | Bug in World->removeSkeleton() - Hi, here a report on the following bug:
Function: removeSkeleton()
Location: dart/simulation/World.cpp (line 246)
Error: The function should delete the skeleton name from the mNameMgrForSkeletons, which is not currently being done.
Fix: Add the following 2 lines probably after line 265 for safe checks:
// Remove from name manager
mNameMgrForSkeletons.removeName( _skeleton->getName() );
I am using a program in which I constantly add/delete skeletons with the same name for some online object detection. I was getting SEGFAULTS after deleting an skeleton and then trying to add it later (the NameManager thought the object still existed, but the Skeleton had been already erased).
After adding the couple of lines mentioned above, the issue dissapared. | priority | bug in world removeskeleton hi here a report on the following bug function removeskeleton location dart simulation world cpp line error the function should delete the skeleton name from the mnamemgrforskeletons which is not currently being done fix add the following lines probably after line for safe checks remove from name manager mnamemgrforskeletons removename skeleton getname i am using a program in which i constantly add delete skeletons with the same name for some online object detection i was getting segfaults after deleting an skeleton and then trying to add it later the namemanager thought the object still existed but the skeleton had been already erased after adding the couple of lines mentioned above the issue dissapared | 1 |
670,459 | 22,690,568,801 | IssuesEvent | 2022-07-04 19:33:51 | pytorch/pytorch | https://api.github.com/repos/pytorch/pytorch | closed | `kl_div` will crash in the backward pass on cuda | high priority module: crash module: autograd module: nn module: cuda triaged | ### 🐛 Describe the bug
`kl_div` will crash in the backward pass on cuda
```python
import torch
input = torch.rand([5, 5, 5], dtype=torch.float64, device='cuda', requires_grad=True)
target = torch.rand([5], dtype=torch.float64, device='cuda', requires_grad=True)
res = torch.nn.functional.kl_div(input, target)
print('forward')
res.sum().backward()
# crash
print('backward')
```
### Versions
pytorch: 1.11.0
cuda: 11.3
cc @ezyang @gchanan @zou3519 @albanD @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7 @mruberry @jbschlosser @walterddr @kshitij12345 @saketh-are @ngimel | 1.0 | `kl_div` will crash in the backward pass on cuda - ### 🐛 Describe the bug
`kl_div` will crash in the backward pass on cuda
```python
import torch
input = torch.rand([5, 5, 5], dtype=torch.float64, device='cuda', requires_grad=True)
target = torch.rand([5], dtype=torch.float64, device='cuda', requires_grad=True)
res = torch.nn.functional.kl_div(input, target)
print('forward')
res.sum().backward()
# crash
print('backward')
```
### Versions
pytorch: 1.11.0
cuda: 11.3
cc @ezyang @gchanan @zou3519 @albanD @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7 @mruberry @jbschlosser @walterddr @kshitij12345 @saketh-are @ngimel | priority | kl div will crash in the backward pass on cuda 🐛 describe the bug kl div will crash in the backward pass on cuda python import torch input torch rand dtype torch device cuda requires grad true target torch rand dtype torch device cuda requires grad true res torch nn functional kl div input target print forward res sum backward crash print backward versions pytorch cuda cc ezyang gchanan alband gqchen pearu nikitaved soulitzer lezcano mruberry jbschlosser walterddr saketh are ngimel | 1 |
187,840 | 6,761,564,907 | IssuesEvent | 2017-10-25 02:36:00 | opencollective/opencollective | https://api.github.com/repos/opencollective/opencollective | closed | Donation to buttercup failed | high priority |
Thank you for taking the time to report an issue 🙏
The easier it is for us to reproduce it, the faster we can solve it.
So please try to be as complete as possible when filing your issue.
***
URL: opencollective.com/buttercup/donate
Logged in as: unsure.
Error message if any: Cannot read property band of null
Expected result: make a donation
Browser:
Bonus point if you can add a screenshot :-)
<img width="1394" alt="pastedgraphic-1" src="https://user-images.githubusercontent.com/3671070/31959034-99e479ae-b8c1-11e7-8feb-54d3573c31ab.png">
Thank you and have a wonderful day/evening!
(and sorry for inconvenience! We'll do our best to solve this ASAP)
| 1.0 | Donation to buttercup failed -
Thank you for taking the time to report an issue 🙏
The easier it is for us to reproduce it, the faster we can solve it.
So please try to be as complete as possible when filing your issue.
***
URL: opencollective.com/buttercup/donate
Logged in as: unsure.
Error message if any: Cannot read property band of null
Expected result: make a donation
Browser:
Bonus point if you can add a screenshot :-)
<img width="1394" alt="pastedgraphic-1" src="https://user-images.githubusercontent.com/3671070/31959034-99e479ae-b8c1-11e7-8feb-54d3573c31ab.png">
Thank you and have a wonderful day/evening!
(and sorry for inconvenience! We'll do our best to solve this ASAP)
| priority | donation to buttercup failed thank you for taking the time to report an issue 🙏 the easier it is for us to reproduce it the faster we can solve it so please try to be as complete as possible when filing your issue url opencollective com buttercup donate logged in as unsure error message if any cannot read property band of null expected result make a donation browser bonus point if you can add a screenshot img width alt pastedgraphic src thank you and have a wonderful day evening and sorry for inconvenience we ll do our best to solve this asap | 1 |
333,385 | 10,121,270,725 | IssuesEvent | 2019-07-31 15:17:56 | inverse-inc/packetfence | https://api.github.com/repos/inverse-inc/packetfence | closed | Missing Custom LDAP/RADIUS attributes in the authentications rules. | Priority: High Type: Bug | Adding custom attributes for RADIUS/LDAP doesn't allow you to use them in authentications rules
**To Reproduce**
Steps to reproduce the behavior:
1. Go to 'Configuration -> System Configuration->Advanced'
2. Click on 'LDAP Attributes'
3. Add Zamattr
4. Go in 'Policies and access control->Authentication Sources->New internal source->LDAP'
5. Create a rule and search for Zamattr.
**Expected behavior**
We should be able to see the custom attribute Zamattr in the list.
**Desktop (please complete the following information):**
- OS: Ubuntu 18.04
- Browser Chrome
- Version Version 75.0.3770.100 (Build officiel) (64 bits)
| 1.0 | Missing Custom LDAP/RADIUS attributes in the authentications rules. - Adding custom attributes for RADIUS/LDAP doesn't allow you to use them in authentications rules
**To Reproduce**
Steps to reproduce the behavior:
1. Go to 'Configuration -> System Configuration->Advanced'
2. Click on 'LDAP Attributes'
3. Add Zamattr
4. Go in 'Policies and access control->Authentication Sources->New internal source->LDAP'
5. Create a rule and search for Zamattr.
**Expected behavior**
We should be able to see the custom attribute Zamattr in the list.
**Desktop (please complete the following information):**
- OS: Ubuntu 18.04
- Browser Chrome
- Version Version 75.0.3770.100 (Build officiel) (64 bits)
| priority | missing custom ldap radius attributes in the authentications rules adding custom attributes for radius ldap doesn t allow you to use them in authentications rules to reproduce steps to reproduce the behavior go to configuration system configuration advanced click on ldap attributes add zamattr go in policies and access control authentication sources new internal source ldap create a rule and search for zamattr expected behavior we should be able to see the custom attribute zamattr in the list desktop please complete the following information os ubuntu browser chrome version version build officiel bits | 1 |
1,401 | 2,603,847,185 | IssuesEvent | 2015-02-24 18:16:15 | chrsmith/nishazi6 | https://api.github.com/repos/chrsmith/nishazi6 | opened | 沈阳单纯疱疹怎么治 | auto-migrated Priority-Medium Type-Defect | ```
沈阳单纯疱疹怎么治〓沈陽軍區政治部醫院性病〓TEL：024-3102
3308〓成立于1946年，68年專注于性傳播疾病的研究和治療。位�
��沈陽市沈河區二緯路32號。是一所與新中國同建立共輝煌的�
��史悠久、設備精良、技術權威、專家云集，是預防、保健、
醫療、科研康復為一體的綜合性醫院。是國家首批公立甲等��
�隊醫院、全國首批醫療規范定點單位，是第四軍醫大學、東�
��大學等知名高等院校的教學醫院。曾被中國人民解放軍空軍
后勤部衛生部評為衛生工作先進單位，先后兩次榮立集體二��
�功。
```
-----
Original issue reported on code.google.com by `q964105...@gmail.com` on 4 Jun 2014 at 8:15 | 1.0 | 沈阳单纯疱疹怎么治 - ```
沈阳单纯疱疹怎么治〓沈陽軍區政治部醫院性病〓TEL：024-3102
3308〓成立于1946年，68年專注于性傳播疾病的研究和治療。位�
��沈陽市沈河區二緯路32號。是一所與新中國同建立共輝煌的�
��史悠久、設備精良、技術權威、專家云集，是預防、保健、
醫療、科研康復為一體的綜合性醫院。是國家首批公立甲等��
�隊醫院、全國首批醫療規范定點單位，是第四軍醫大學、東�
��大學等知名高等院校的教學醫院。曾被中國人民解放軍空軍
后勤部衛生部評為衛生工作先進單位，先后兩次榮立集體二��
�功。
```
-----
Original issue reported on code.google.com by `q964105...@gmail.com` on 4 Jun 2014 at 8:15 | non_priority | 沈阳单纯疱疹怎么治 沈阳单纯疱疹怎么治〓沈陽軍區政治部醫院性病〓tel： 〓 ， 。位� �� 。是一所與新中國同建立共輝煌的� ��史悠久、設備精良、技術權威、專家云集，是預防、保健、 醫療、科研康復為一體的綜合性醫院。是國家首批公立甲等�� �隊醫院、全國首批醫療規范定點單位，是第四軍醫大學、東� ��大學等知名高等院校的教學醫院。曾被中國人民解放軍空軍 后勤部衛生部評為衛生工作先進單位，先后兩次榮立集體二�� �功。 original issue reported on code google com by gmail com on jun at | 0 |
623,621 | 19,673,787,706 | IssuesEvent | 2022-01-11 10:11:28 | googleapis/java-firestore | https://api.github.com/repos/googleapis/java-firestore | opened | Synthesis failed for java-firestore | priority: p1 type: bug autosynth failure | Hello! Autosynth couldn't regenerate java-firestore. :broken_heart:
Please investigate and fix this issue within 5 business days. While it remains broken,
this library cannot be updated with changes to the java-firestore API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running `synth.py`:
```
ud-firestore-admin/src/test/java/com/google/cloud/firestore/v1/FirestoreAdminClientTest.java
M google-cloud-firestore-admin/src/test/java/com/google/cloud/firestore/v1/MockFirestoreAdminImpl.java
M grpc-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/FirestoreAdminGrpc.java
M proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/Field.java
M proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/FieldOrBuilder.java
M proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/FieldProto.java
M proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/FirestoreAdminProto.java
M proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/Index.java
M proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ListFieldsRequest.java
M proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ListFieldsRequestOrBuilder.java
M proto-google-cloud-firestore-admin-v1/src/main/proto/google/firestore/admin/v1/field.proto
M proto-google-cloud-firestore-admin-v1/src/main/proto/google/firestore/admin/v1/firestore_admin.proto
M proto-google-cloud-firestore-admin-v1/src/main/proto/google/firestore/admin/v1/index.proto
M proto-google-cloud-firestore-admin-v1/src/main/proto/google/firestore/admin/v1/location.proto
M proto-google-cloud-firestore-admin-v1/src/main/proto/google/firestore/admin/v1/operation.proto
M synth.metadata
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/Database.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/DatabaseOrBuilder.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/DatabaseProto.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/GetDatabaseRequest.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/GetDatabaseRequestOrBuilder.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ListDatabasesRequest.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ListDatabasesRequestOrBuilder.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ListDatabasesResponse.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ListDatabasesResponseOrBuilder.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ProjectName.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/UpdateDatabaseMetadata.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/UpdateDatabaseMetadataOrBuilder.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/UpdateDatabaseRequest.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/UpdateDatabaseRequestOrBuilder.java
?? proto-google-cloud-firestore-admin-v1/src/main/proto/google/firestore/admin/v1/database.proto
2022-01-11 02:11:22,265 autosynth [DEBUG] > Running: git log 6355638dfed614fe5977a06d59dc010370f88582 -1 --no-decorate --pretty=%s
2022-01-11 02:11:22,269 autosynth [DEBUG] > Running: git log 6355638dfed614fe5977a06d59dc010370f88582 -1 --no-decorate --pretty=%b%n%nSource-Author: %an <%ae>%nSource-Date: %ad
2022-01-11 02:11:22,273 autosynth [DEBUG] > Running: git add -A
2022-01-11 02:11:22,285 autosynth [DEBUG] > Running: git status --porcelain
2022-01-11 02:11:22,292 autosynth [DEBUG] > Running: git commit -m chore(java): update variable name to api_shortname in README template
* chore(java): update variable name to api_shortname in README template
* chore: fix test
* chore: fix test
Source-Author: Neenu Shaji <Neenu1995@users.noreply.github.com>
Source-Date: Mon Jan 10 20:41:34 2022 -0500
Source-Repo: googleapis/synthtool
Source-Sha: 6355638dfed614fe5977a06d59dc010370f88582
Source-Link: https://github.com/googleapis/synthtool/commit/6355638dfed614fe5977a06d59dc010370f88582
[autosynth-168 e3b0b65] chore(java): update variable name to api_shortname in README template
40 files changed, 8116 insertions(+), 227 deletions(-)
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/Database.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/DatabaseOrBuilder.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/DatabaseProto.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/GetDatabaseRequest.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/GetDatabaseRequestOrBuilder.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ListDatabasesRequest.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ListDatabasesRequestOrBuilder.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ListDatabasesResponse.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ListDatabasesResponseOrBuilder.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ProjectName.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/UpdateDatabaseMetadata.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/UpdateDatabaseMetadataOrBuilder.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/UpdateDatabaseRequest.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/UpdateDatabaseRequestOrBuilder.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/proto/google/firestore/admin/v1/database.proto
2022-01-11 02:11:22,323 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at e3b0b65 chore(java): update variable name to api_shortname in README template
2022-01-11 02:11:22,331 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2022-01-11 02:11:22,339 autosynth [DEBUG] > Running: git diff --binary HEAD..autosynth-168 -- . :(exclude)synth.metadata
2022-01-11 02:11:22,343 autosynth [DEBUG] > Running: git diff --binary HEAD autosynth-168
2022-01-11 02:11:22,348 autosynth [DEBUG] > Running: git apply /tmpfs/tmp/tmpzuy8pipl/autosynth-168.patch
2022-01-11 02:11:22,352 autosynth [DEBUG] > Running: git add -A
2022-01-11 02:11:22,359 autosynth [DEBUG] > Running: git status --porcelain
2022-01-11 02:11:22,367 autosynth [DEBUG] > Running: git commit -m chore(java): update variable name to api_shortname in README template
* chore(java): update variable name to api_shortname in README template
* chore: fix test
* chore: fix test
Source-Author: Neenu Shaji <Neenu1995@users.noreply.github.com>
Source-Date: Mon Jan 10 20:41:34 2022 -0500
Source-Repo: googleapis/synthtool
Source-Sha: 6355638dfed614fe5977a06d59dc010370f88582
Source-Link: https://github.com/googleapis/synthtool/commit/6355638dfed614fe5977a06d59dc010370f88582
[autosynth 59dddf5] chore(java): update variable name to api_shortname in README template
3 files changed, 25 insertions(+), 10 deletions(-)
2022-01-11 02:11:22,377 autosynth [DEBUG] > Running: git diff --binary autosynth-168..autosynth-170 -- . :(exclude)synth.metadata
2022-01-11 02:11:22,381 autosynth [DEBUG] > Running: git diff autosynth-168..autosynth-170 -- synth.metadata
2022-01-11 02:11:22,386 autosynth [DEBUG] > Running: git push --force origin autosynth
remote:
remote: Create a pull request for 'autosynth' on GitHub by visiting:
remote: https://github.com/googleapis/java-firestore/pull/new/autosynth
remote:
To https://github.com/googleapis/java-firestore.git
* [new branch] autosynth -> autosynth
2022-01-11 02:11:23,715 autosynth [DEBUG] > Running: git log -2 --pretty=%b
2022-01-11 02:11:26,121 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 359, in <module>
main()
File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 191, in main
return _inner_main(temp_dir)
File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 339, in _inner_main
commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 95, in synthesize_loop
synthesize_inner_loop(fork, synthesizer)
File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 139, in synthesize_inner_loop
synthesizer, len(toolbox.versions) - 1
File "/tmpfs/src/github/synthtool/autosynth/synth_toolbox.py", line 259, in synthesize_version_in_new_branch
synthesizer.synthesize(synth_log_path, self.environ)
File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
synth_proc.check_returncode() # Raise an exception.
File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.
```
Google internal developers can see the full log [here](http://sponge2/results/invocations/eab999e1-5d36-4d69-b658-32c468a5f5a9/targets/github%2Fsynthtool;config=default/tests;query=java-firestore;failed=false).
| 1.0 | Synthesis failed for java-firestore - Hello! Autosynth couldn't regenerate java-firestore. :broken_heart:
Please investigate and fix this issue within 5 business days. While it remains broken,
this library cannot be updated with changes to the java-firestore API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running `synth.py`:
```
ud-firestore-admin/src/test/java/com/google/cloud/firestore/v1/FirestoreAdminClientTest.java
M google-cloud-firestore-admin/src/test/java/com/google/cloud/firestore/v1/MockFirestoreAdminImpl.java
M grpc-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/FirestoreAdminGrpc.java
M proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/Field.java
M proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/FieldOrBuilder.java
M proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/FieldProto.java
M proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/FirestoreAdminProto.java
M proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/Index.java
M proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ListFieldsRequest.java
M proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ListFieldsRequestOrBuilder.java
M proto-google-cloud-firestore-admin-v1/src/main/proto/google/firestore/admin/v1/field.proto
M proto-google-cloud-firestore-admin-v1/src/main/proto/google/firestore/admin/v1/firestore_admin.proto
M proto-google-cloud-firestore-admin-v1/src/main/proto/google/firestore/admin/v1/index.proto
M proto-google-cloud-firestore-admin-v1/src/main/proto/google/firestore/admin/v1/location.proto
M proto-google-cloud-firestore-admin-v1/src/main/proto/google/firestore/admin/v1/operation.proto
M synth.metadata
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/Database.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/DatabaseOrBuilder.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/DatabaseProto.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/GetDatabaseRequest.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/GetDatabaseRequestOrBuilder.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ListDatabasesRequest.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ListDatabasesRequestOrBuilder.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ListDatabasesResponse.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ListDatabasesResponseOrBuilder.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ProjectName.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/UpdateDatabaseMetadata.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/UpdateDatabaseMetadataOrBuilder.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/UpdateDatabaseRequest.java
?? proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/UpdateDatabaseRequestOrBuilder.java
?? proto-google-cloud-firestore-admin-v1/src/main/proto/google/firestore/admin/v1/database.proto
2022-01-11 02:11:22,265 autosynth [DEBUG] > Running: git log 6355638dfed614fe5977a06d59dc010370f88582 -1 --no-decorate --pretty=%s
2022-01-11 02:11:22,269 autosynth [DEBUG] > Running: git log 6355638dfed614fe5977a06d59dc010370f88582 -1 --no-decorate --pretty=%b%n%nSource-Author: %an <%ae>%nSource-Date: %ad
2022-01-11 02:11:22,273 autosynth [DEBUG] > Running: git add -A
2022-01-11 02:11:22,285 autosynth [DEBUG] > Running: git status --porcelain
2022-01-11 02:11:22,292 autosynth [DEBUG] > Running: git commit -m chore(java): update variable name to api_shortname in README template
* chore(java): update variable name to api_shortname in README template
* chore: fix test
* chore: fix test
Source-Author: Neenu Shaji <Neenu1995@users.noreply.github.com>
Source-Date: Mon Jan 10 20:41:34 2022 -0500
Source-Repo: googleapis/synthtool
Source-Sha: 6355638dfed614fe5977a06d59dc010370f88582
Source-Link: https://github.com/googleapis/synthtool/commit/6355638dfed614fe5977a06d59dc010370f88582
[autosynth-168 e3b0b65] chore(java): update variable name to api_shortname in README template
40 files changed, 8116 insertions(+), 227 deletions(-)
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/Database.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/DatabaseOrBuilder.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/DatabaseProto.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/GetDatabaseRequest.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/GetDatabaseRequestOrBuilder.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ListDatabasesRequest.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ListDatabasesRequestOrBuilder.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ListDatabasesResponse.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ListDatabasesResponseOrBuilder.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/ProjectName.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/UpdateDatabaseMetadata.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/UpdateDatabaseMetadataOrBuilder.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/UpdateDatabaseRequest.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/java/com/google/firestore/admin/v1/UpdateDatabaseRequestOrBuilder.java
create mode 100644 proto-google-cloud-firestore-admin-v1/src/main/proto/google/firestore/admin/v1/database.proto
2022-01-11 02:11:22,323 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at e3b0b65 chore(java): update variable name to api_shortname in README template
2022-01-11 02:11:22,331 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2022-01-11 02:11:22,339 autosynth [DEBUG] > Running: git diff --binary HEAD..autosynth-168 -- . :(exclude)synth.metadata
2022-01-11 02:11:22,343 autosynth [DEBUG] > Running: git diff --binary HEAD autosynth-168
2022-01-11 02:11:22,348 autosynth [DEBUG] > Running: git apply /tmpfs/tmp/tmpzuy8pipl/autosynth-168.patch
2022-01-11 02:11:22,352 autosynth [DEBUG] > Running: git add -A
2022-01-11 02:11:22,359 autosynth [DEBUG] > Running: git status --porcelain
2022-01-11 02:11:22,367 autosynth [DEBUG] > Running: git commit -m chore(java): update variable name to api_shortname in README template
* chore(java): update variable name to api_shortname in README template
* chore: fix test
* chore: fix test
Source-Author: Neenu Shaji <Neenu1995@users.noreply.github.com>
Source-Date: Mon Jan 10 20:41:34 2022 -0500
Source-Repo: googleapis/synthtool
Source-Sha: 6355638dfed614fe5977a06d59dc010370f88582
Source-Link: https://github.com/googleapis/synthtool/commit/6355638dfed614fe5977a06d59dc010370f88582
[autosynth 59dddf5] chore(java): update variable name to api_shortname in README template
3 files changed, 25 insertions(+), 10 deletions(-)
2022-01-11 02:11:22,377 autosynth [DEBUG] > Running: git diff --binary autosynth-168..autosynth-170 -- . :(exclude)synth.metadata
2022-01-11 02:11:22,381 autosynth [DEBUG] > Running: git diff autosynth-168..autosynth-170 -- synth.metadata
2022-01-11 02:11:22,386 autosynth [DEBUG] > Running: git push --force origin autosynth
remote:
remote: Create a pull request for 'autosynth' on GitHub by visiting:
remote: https://github.com/googleapis/java-firestore/pull/new/autosynth
remote:
To https://github.com/googleapis/java-firestore.git
* [new branch] autosynth -> autosynth
2022-01-11 02:11:23,715 autosynth [DEBUG] > Running: git log -2 --pretty=%b
2022-01-11 02:11:26,121 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 359, in <module>
main()
File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 191, in main
return _inner_main(temp_dir)
File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 339, in _inner_main
commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 95, in synthesize_loop
synthesize_inner_loop(fork, synthesizer)
File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 139, in synthesize_inner_loop
synthesizer, len(toolbox.versions) - 1
File "/tmpfs/src/github/synthtool/autosynth/synth_toolbox.py", line 259, in synthesize_version_in_new_branch
synthesizer.synthesize(synth_log_path, self.environ)
File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
synth_proc.check_returncode() # Raise an exception.
File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.
```
Google internal developers can see the full log [here](http://sponge2/results/invocations/eab999e1-5d36-4d69-b658-32c468a5f5a9/targets/github%2Fsynthtool;config=default/tests;query=java-firestore;failed=false).
| priority | synthesis failed for java firestore hello autosynth couldn t regenerate java firestore broken heart please investigate and fix this issue within business days while it remains broken this library cannot be updated with changes to the java firestore api and the library grows stale see for trouble shooting tips here s the output from running synth py ud firestore admin src test java com google cloud firestore firestoreadminclienttest java m google cloud firestore admin src test java com google cloud firestore mockfirestoreadminimpl java m grpc google cloud firestore admin src main java com google firestore admin firestoreadmingrpc java m proto google cloud firestore admin src main java com google firestore admin field java m proto google cloud firestore admin src main java com google firestore admin fieldorbuilder java m proto google cloud firestore admin src main java com google firestore admin fieldproto java m proto google cloud firestore admin src main java com google firestore admin firestoreadminproto java m proto google cloud firestore admin src main java com google firestore admin index java m proto google cloud firestore admin src main java com google firestore admin listfieldsrequest java m proto google cloud firestore admin src main java com google firestore admin listfieldsrequestorbuilder java m proto google cloud firestore admin src main proto google firestore admin field proto m proto google cloud firestore admin src main proto google firestore admin firestore admin proto m proto google cloud firestore admin src main proto google firestore admin index proto m proto google cloud firestore admin src main proto google firestore admin location proto m proto google cloud firestore admin src main proto google firestore admin operation proto m synth metadata proto google cloud firestore admin src main java com google firestore admin database java proto google cloud firestore admin src main java com google firestore admin databaseorbuilder java proto google cloud firestore admin src main java com google firestore admin databaseproto java proto google cloud firestore admin src main java com google firestore admin getdatabaserequest java proto google cloud firestore admin src main java com google firestore admin getdatabaserequestorbuilder java proto google cloud firestore admin src main java com google firestore admin listdatabasesrequest java proto google cloud firestore admin src main java com google firestore admin listdatabasesrequestorbuilder java proto google cloud firestore admin src main java com google firestore admin listdatabasesresponse java proto google cloud firestore admin src main java com google firestore admin listdatabasesresponseorbuilder java proto google cloud firestore admin src main java com google firestore admin projectname java proto google cloud firestore admin src main java com google firestore admin updatedatabasemetadata java proto google cloud firestore admin src main java com google firestore admin updatedatabasemetadataorbuilder java proto google cloud firestore admin src main java com google firestore admin updatedatabaserequest java proto google cloud firestore admin src main java com google firestore admin updatedatabaserequestorbuilder java proto google cloud firestore admin src main proto google firestore admin database proto autosynth running git log no decorate pretty s autosynth running git log no decorate pretty b n nsource author an nsource date ad autosynth running git add a autosynth running git status porcelain autosynth running git commit m chore java update variable name to api shortname in readme template chore java update variable name to api shortname in readme template chore fix test chore fix test source author neenu shaji source date mon jan source repo googleapis synthtool source sha source link chore java update variable name to api shortname in readme template files changed insertions deletions create mode proto google cloud firestore admin src main java com google firestore admin database java create mode proto google cloud firestore admin src main java com google firestore admin databaseorbuilder java create mode proto google cloud firestore admin src main java com google firestore admin databaseproto java create mode proto google cloud firestore admin src main java com google firestore admin getdatabaserequest java create mode proto google cloud firestore admin src main java com google firestore admin getdatabaserequestorbuilder java create mode proto google cloud firestore admin src main java com google firestore admin listdatabasesrequest java create mode proto google cloud firestore admin src main java com google firestore admin listdatabasesrequestorbuilder java create mode proto google cloud firestore admin src main java com google firestore admin listdatabasesresponse java create mode proto google cloud firestore admin src main java com google firestore admin listdatabasesresponseorbuilder java create mode proto google cloud firestore admin src main java com google firestore admin projectname java create mode proto google cloud firestore admin src main java com google firestore admin updatedatabasemetadata java create mode proto google cloud firestore admin src main java com google firestore admin updatedatabasemetadataorbuilder java create mode proto google cloud firestore admin src main java com google firestore admin updatedatabaserequest java create mode proto google cloud firestore admin src main java com google firestore admin updatedatabaserequestorbuilder java create mode proto google cloud firestore admin src main proto google firestore admin database proto autosynth running git reset hard head head is now at chore java update variable name to api shortname in readme template autosynth running git checkout autosynth switched to branch autosynth autosynth running git diff binary head autosynth exclude synth metadata autosynth running git diff binary head autosynth autosynth running git apply tmpfs tmp autosynth patch autosynth running git add a autosynth running git status porcelain autosynth running git commit m chore java update variable name to api shortname in readme template chore java update variable name to api shortname in readme template chore fix test chore fix test source author neenu shaji source date mon jan source repo googleapis synthtool source sha source link chore java update variable name to api shortname in readme template files changed insertions deletions autosynth running git diff binary autosynth autosynth exclude synth metadata autosynth running git diff autosynth autosynth synth metadata autosynth running git push force origin autosynth remote remote create a pull request for autosynth on github by visiting remote remote to autosynth autosynth autosynth running git log pretty b autosynth running git clean fdx removing pycache traceback most recent call last file home kbuilder pyenv versions lib runpy py line in run module as main main mod spec file home kbuilder pyenv versions lib runpy py line in run code exec code run globals file tmpfs src github synthtool autosynth synth py line in main file tmpfs src github synthtool autosynth synth py line in main return inner main temp dir file tmpfs src github synthtool autosynth synth py line in inner main commit count synthesize loop x multiple prs change pusher synthesizer file tmpfs src github synthtool autosynth synth py line in synthesize loop synthesize inner loop fork synthesizer file tmpfs src github synthtool autosynth synth py line in synthesize inner loop synthesizer len toolbox versions file tmpfs src github synthtool autosynth synth toolbox py line in synthesize version in new branch synthesizer synthesize synth log path self environ file tmpfs src github synthtool autosynth synthesizer py line in synthesize synth proc check returncode raise an exception file home kbuilder pyenv versions lib subprocess py line in check returncode self stderr subprocess calledprocesserror command returned non zero exit status google internal developers can see the full log | 1 |
644,386 | 20,976,420,027 | IssuesEvent | 2022-03-28 15:35:15 | ucb-rit/coldfront | https://api.github.com/repos/ucb-rit/coldfront | opened | Address initial issues raised by pylint | low priority | After #386, pylint can be run on the codebase.
- [ ] Address major issues raised by it.
- [ ] Tune it so that irrelevant issues are ignored.
- [ ] Incorporate it into the code review process. | 1.0 | Address initial issues raised by pylint - After #386, pylint can be run on the codebase.
- [ ] Address major issues raised by it.
- [ ] Tune it so that irrelevant issues are ignored.
- [ ] Incorporate it into the code review process. | priority | address initial issues raised by pylint after pylint can be run on the codebase address major issues raised by it tune it so that irrelevant issues are ignored incorporate it into the code review process | 1 |
109,272 | 4,384,438,754 | IssuesEvent | 2016-08-08 02:35:02 | loomio/loomio | https://api.github.com/repos/loomio/loomio | closed | No space before unread count | Bug Priority: Trivial | 
I'd expect there to be a space between `Inbox` and `(32)`
I'd just create a pull request but I wanted to check if this was done intentionally.
Maybe this changed when you did the accessibility change @HSalmon? | 1.0 | No space before unread count - 
I'd expect there to be a space between `Inbox` and `(32)`
I'd just create a pull request but I wanted to check if this was done intentionally.
Maybe this changed when you did the accessibility change @HSalmon? | priority | no space before unread count i d expect there to be a space between inbox and i d just create a pull request but i wanted to check if this was done intentionally maybe this changed when you did the accessibility change hsalmon | 1 |
619,711 | 19,533,144,959 | IssuesEvent | 2021-12-30 21:32:44 | science356lab/OT2Control | https://api.github.com/repos/science356lab/OT2Control | opened | Initializing Wellpate Reagents | enhancement priority3 hour - | ET 1.
Currently, there is not a good way to initialize a well with volume because it requires mass. We should speak with Mark to decide if mass in this case should be interpreted as volume, or if this will ever be needed | 1.0 | Initializing Wellpate Reagents - ET 1.
Currently, there is not a good way to initialize a well with volume because it requires mass. We should speak with Mark to decide if mass in this case should be interpreted as volume, or if this will ever be needed | priority | initializing wellpate reagents et currently there is not a good way to initialize a well with volume because it requires mass we should speak with mark to decide if mass in this case should be interpreted as volume or if this will ever be needed | 1 |
260,513 | 27,784,485,685 | IssuesEvent | 2023-03-17 01:11:51 | Soontao/RSSHub | https://api.github.com/repos/Soontao/RSSHub | opened | twit-2.2.11.tgz: 1 vulnerabilities (highest severity is: 5.5) | Mend: dependency security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>twit-2.2.11.tgz</b></p></summary>
<p></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/request/package.json</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/Soontao/RSSHub/commit/05b41583ba25ff41304d8cc9722f6f88f1a7d021">05b41583ba25ff41304d8cc9722f6f88f1a7d021</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (twit version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2023-28155](https://www.mend.io/vulnerability-database/CVE-2023-28155) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.5 | request-2.88.2.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/medium_vul.png' width=19 height=20> CVE-2023-28155</summary>
### Vulnerable Library - <b>request-2.88.2.tgz</b></p>
<p>Simplified HTTP request client.</p>
<p>Library home page: <a href="https://registry.npmjs.org/request/-/request-2.88.2.tgz">https://registry.npmjs.org/request/-/request-2.88.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/request/package.json</p>
<p>
Dependency Hierarchy:
- twit-2.2.11.tgz (Root Library)
- :x: **request-2.88.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Soontao/RSSHub/commit/05b41583ba25ff41304d8cc9722f6f88f1a7d021">05b41583ba25ff41304d8cc9722f6f88f1a7d021</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
** UNSUPPORTED WHEN ASSIGNED ** The Request package through 2.88.1 for Node.js allows a bypass of SSRF mitigations via an attacker-controller server that does a cross-protocol redirect (HTTP to HTTPS, or HTTPS to HTTP). NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
<p>Publish Date: 2023-03-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-28155>CVE-2023-28155</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details> | True | twit-2.2.11.tgz: 1 vulnerabilities (highest severity is: 5.5) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>twit-2.2.11.tgz</b></p></summary>
<p></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/request/package.json</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/Soontao/RSSHub/commit/05b41583ba25ff41304d8cc9722f6f88f1a7d021">05b41583ba25ff41304d8cc9722f6f88f1a7d021</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (twit version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2023-28155](https://www.mend.io/vulnerability-database/CVE-2023-28155) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.5 | request-2.88.2.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/medium_vul.png' width=19 height=20> CVE-2023-28155</summary>
### Vulnerable Library - <b>request-2.88.2.tgz</b></p>
<p>Simplified HTTP request client.</p>
<p>Library home page: <a href="https://registry.npmjs.org/request/-/request-2.88.2.tgz">https://registry.npmjs.org/request/-/request-2.88.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/request/package.json</p>
<p>
Dependency Hierarchy:
- twit-2.2.11.tgz (Root Library)
- :x: **request-2.88.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Soontao/RSSHub/commit/05b41583ba25ff41304d8cc9722f6f88f1a7d021">05b41583ba25ff41304d8cc9722f6f88f1a7d021</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
** UNSUPPORTED WHEN ASSIGNED ** The Request package through 2.88.1 for Node.js allows a bypass of SSRF mitigations via an attacker-controller server that does a cross-protocol redirect (HTTP to HTTPS, or HTTPS to HTTP). NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
<p>Publish Date: 2023-03-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-28155>CVE-2023-28155</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details> | non_priority | twit tgz vulnerabilities highest severity is vulnerable library twit tgz path to dependency file package json path to vulnerable library node modules request package json found in head commit a href vulnerabilities cve severity cvss dependency type fixed in twit version remediation available medium request 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 request tgz simplified http request client library home page a href path to dependency file package json path to vulnerable library node modules request package json dependency hierarchy twit tgz root library x request tgz vulnerable library found in head commit a href found in base branch master vulnerability details unsupported when assigned the request package through for node js allows a bypass of ssrf mitigations via an attacker controller server that does a cross protocol redirect http to https or https to http note this vulnerability only affects products that are no longer supported by the maintainer publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href step up your open source security game with mend | 0 |
66,182 | 27,377,682,421 | IssuesEvent | 2023-02-28 07:41:41 | BHelpful/MealTime | https://api.github.com/repos/BHelpful/MealTime | closed | [Story]: Use secrets as a service | MAJOR Service | ### Priority
MAJOR
### Description
As a developer I would like to be able to have access to the client secrets of the app to be able to e.g. use google sign in
A possible solution could be https://www.vaultproject.io/ (selfhosted)
### Acceptance criteria
- [ ] Easy access to use client secrets for all developers (open source friendly)
### Comments / questions
https://blog.gitguardian.com/secrets-api-management/
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct | 1.0 | [Story]: Use secrets as a service - ### Priority
MAJOR
### Description
As a developer I would like to be able to have access to the client secrets of the app to be able to e.g. use google sign in
A possible solution could be https://www.vaultproject.io/ (selfhosted)
### Acceptance criteria
- [ ] Easy access to use client secrets for all developers (open source friendly)
### Comments / questions
https://blog.gitguardian.com/secrets-api-management/
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct | non_priority | use secrets as a service priority major description as a developer i would like to be able to have access to the client secrets of the app to be able to e g use google sign in a possible solution could be selfhosted acceptance criteria easy access to use client secrets for all developers open source friendly comments questions code of conduct i agree to follow this project s code of conduct | 0 |
104,401 | 13,065,742,167 | IssuesEvent | 2020-07-30 20:21:00 | harmony-one/harmony | https://api.github.com/repos/harmony-one/harmony | closed | [DISCUSS] Shall we move kernel env setting to harmony binary? | design | ## Description
This is the technical discussion about whether to move the `sysctl` kern parameter settings to harmony binary file. When I am doing the project `remove node.sh`, the following code block is currently in script `node.sh`.
```
function setup_env
{
check_root
### KERNEL TUNING ###
# Increase size of file handles and inode cache
sysctl -w fs.file-max=2097152
# Do less swapping
sysctl -w vm.swappiness=10
...
}
```
This code block is executed when user is running node.sh as root user to fine tune the Linux kernel parameters. However, there should be both advantage and disadvantages to move this code logic into the binary file:
### Advantage
1. Node operators does not need to know exactly what the kernel configuration is, and can achieve best performance as long as node operator use recommended instance configurations.
### Disadvantage
1. `harmony` binary is basically an application by nature. An application program shall never hijack kernel settings and do decisions that should be only made by human users.
2. If we write this logic to binary file, we are actually enforcing our kernel settings on the node operators' system. If user want to do some customized kernel settings which collides with our setting fields, users' settings will be overwritten every time the binary is started, which is a very bad idea.
3. Our parameters are only valid for a specific system and only optimized for our recommended configuration. However, the Golang binary is expected to be cross-platform.
So here are several solutions:
### Solution 1
Add os-wise kernel settings in harmony binary. If operating system is "linux" and the command is executed as root user, apply predefine kernel settings.
### Solution 2
Do not add kernel setting in harmony binary. Provide the kernel params tuning along with the recommended instance configuration. Leave it for users to configure it themselves.
> Note: node.sh can still be the running source for our hosting node and be shared with our users as an alternative to run node with all predefined kernel params.
Please let me know your idea about this topic. @rlan35 @LeoHChen @SebastianJ @gupadhyaya @Daniel-VDM
| 1.0 | [DISCUSS] Shall we move kernel env setting to harmony binary? - ## Description
This is the technical discussion about whether to move the `sysctl` kern parameter settings to harmony binary file. When I am doing the project `remove node.sh`, the following code block is currently in script `node.sh`.
```
function setup_env
{
check_root
### KERNEL TUNING ###
# Increase size of file handles and inode cache
sysctl -w fs.file-max=2097152
# Do less swapping
sysctl -w vm.swappiness=10
...
}
```
This code block is executed when user is running node.sh as root user to fine tune the Linux kernel parameters. However, there should be both advantage and disadvantages to move this code logic into the binary file:
### Advantage
1. Node operators does not need to know exactly what the kernel configuration is, and can achieve best performance as long as node operator use recommended instance configurations.
### Disadvantage
1. `harmony` binary is basically an application by nature. An application program shall never hijack kernel settings and do decisions that should be only made by human users.
2. If we write this logic to binary file, we are actually enforcing our kernel settings on the node operators' system. If user want to do some customized kernel settings which collides with our setting fields, users' settings will be overwritten every time the binary is started, which is a very bad idea.
3. Our parameters are only valid for a specific system and only optimized for our recommended configuration. However, the Golang binary is expected to be cross-platform.
So here are several solutions:
### Solution 1
Add os-wise kernel settings in harmony binary. If operating system is "linux" and the command is executed as root user, apply predefine kernel settings.
### Solution 2
Do not add kernel setting in harmony binary. Provide the kernel params tuning along with the recommended instance configuration. Leave it for users to configure it themselves.
> Note: node.sh can still be the running source for our hosting node and be shared with our users as an alternative to run node with all predefined kernel params.
Please let me know your idea about this topic. @rlan35 @LeoHChen @SebastianJ @gupadhyaya @Daniel-VDM
| non_priority | shall we move kernel env setting to harmony binary description this is the technical discussion about whether to move the sysctl kern parameter settings to harmony binary file when i am doing the project remove node sh the following code block is currently in script node sh function setup env check root kernel tuning increase size of file handles and inode cache sysctl w fs file max do less swapping sysctl w vm swappiness this code block is executed when user is running node sh as root user to fine tune the linux kernel parameters however there should be both advantage and disadvantages to move this code logic into the binary file advantage node operators does not need to know exactly what the kernel configuration is and can achieve best performance as long as node operator use recommended instance configurations disadvantage harmony binary is basically an application by nature an application program shall never hijack kernel settings and do decisions that should be only made by human users if we write this logic to binary file we are actually enforcing our kernel settings on the node operators system if user want to do some customized kernel settings which collides with our setting fields users settings will be overwritten every time the binary is started which is a very bad idea our parameters are only valid for a specific system and only optimized for our recommended configuration however the golang binary is expected to be cross platform so here are several solutions solution add os wise kernel settings in harmony binary if operating system is linux and the command is executed as root user apply predefine kernel settings solution do not add kernel setting in harmony binary provide the kernel params tuning along with the recommended instance configuration leave it for users to configure it themselves note node sh can still be the running source for our hosting node and be shared with our users as an alternative to run node with all predefined kernel params please let me know your idea about this topic leohchen sebastianj gupadhyaya daniel vdm | 0 |
118,447 | 9,990,892,249 | IssuesEvent | 2019-07-11 09:48:39 | owncloud/testing | https://api.github.com/repos/owncloud/testing | closed | Add new routes for handling trusted servers in owncloud | QA-team dev:acceptance-tests | Currently there is no API or OCC command to administrate trusted federation server in owncloud. So for the acceptance tests to be able to handle the trusted servers properly we need to add new routes to the testing api. That way we will have new testing api for adding removing and listing the trusted servers in owncloud.
Related issue https://github.com/owncloud/core/issues/34742 | 1.0 | Add new routes for handling trusted servers in owncloud - Currently there is no API or OCC command to administrate trusted federation server in owncloud. So for the acceptance tests to be able to handle the trusted servers properly we need to add new routes to the testing api. That way we will have new testing api for adding removing and listing the trusted servers in owncloud.
Related issue https://github.com/owncloud/core/issues/34742 | non_priority | add new routes for handling trusted servers in owncloud currently there is no api or occ command to administrate trusted federation server in owncloud so for the acceptance tests to be able to handle the trusted servers properly we need to add new routes to the testing api that way we will have new testing api for adding removing and listing the trusted servers in owncloud related issue | 0 |
113,882 | 11,825,988,883 | IssuesEvent | 2020-03-21 15:41:39 | nginx-proxy/docker-letsencrypt-nginx-proxy-companion | https://api.github.com/repos/nginx-proxy/docker-letsencrypt-nginx-proxy-companion | closed | How to use multiple subsubdomains on one cert subdomain certificat? | Documentation Update Question | Hi there,
I have a subdomain like sub.example.com. I'd like to use a subdomain like https://aaa.sub.example.com with sub.example.com certificate (Issued to sub.example.com). Is it possible?
| 1.0 | How to use multiple subsubdomains on one cert subdomain certificat? - Hi there,
I have a subdomain like sub.example.com. I'd like to use a subdomain like https://aaa.sub.example.com with sub.example.com certificate (Issued to sub.example.com). Is it possible?
| non_priority | how to use multiple subsubdomains on one cert subdomain certificat hi there i have a subdomain like sub example com i d like to use a subdomain like with sub example com certificate issued to sub example com is it possible | 0 |
189,502 | 15,190,286,170 | IssuesEvent | 2021-02-15 17:41:05 | ramses-antibiotics/ramses-package | https://api.github.com/repos/ramses-antibiotics/ramses-package | closed | Document transitive closure | data-modelling documentation | - [x] create a vignette/Rd explaining what therapy episodes are and the transitive closure process. Link this in the bridge_tbl functions.
- [x] explain what happens for [prescription_status] IN ('cancelled', 'draft', 'entered-in-error') (missing)
- [x] explain combinations with [prescription_status] NOT IN ('cancelled', 'draft', 'entered-in-error')
- [x] put paper 1 diagram somewhere in vignette
- [x] add a link to this documentation in roxygen chunk for .create_table_drug_prescriptions_edges(), create_therapy_episodes(), transitive_closure_control()
| 1.0 | Document transitive closure - - [x] create a vignette/Rd explaining what therapy episodes are and the transitive closure process. Link this in the bridge_tbl functions.
- [x] explain what happens for [prescription_status] IN ('cancelled', 'draft', 'entered-in-error') (missing)
- [x] explain combinations with [prescription_status] NOT IN ('cancelled', 'draft', 'entered-in-error')
- [x] put paper 1 diagram somewhere in vignette
- [x] add a link to this documentation in roxygen chunk for .create_table_drug_prescriptions_edges(), create_therapy_episodes(), transitive_closure_control()
| non_priority | document transitive closure create a vignette rd explaining what therapy episodes are and the transitive closure process link this in the bridge tbl functions explain what happens for in cancelled draft entered in error missing explain combinations with not in cancelled draft entered in error put paper diagram somewhere in vignette add a link to this documentation in roxygen chunk for create table drug prescriptions edges create therapy episodes transitive closure control | 0 |
16,952 | 6,310,414,203 | IssuesEvent | 2017-07-23 10:07:57 | openshift/origin | https://api.github.com/repos/openshift/origin | closed | Migration of prod cluster blocked on builds and build configs that fail Git URI validation | area/compatibility component/build priority/P2 | In a prod data set being tested on 3.6
```
error: -n XXXX buildconfigs/XXXXX: BuildConfig "XXXXX" is invalid: spec.source.git.uri: Invalid value: "git@github.com:REPO/NAME.git": uri is not a valid url
```
Our URI must support `git@SERVER:PATH`.
This blocks underlying migration of data in 3.6, and may have broken end users.
@jupierce @bparees we cannot promote 3.6 to prod without resolving this or determining it is not an issue. | 1.0 | Migration of prod cluster blocked on builds and build configs that fail Git URI validation - In a prod data set being tested on 3.6
```
error: -n XXXX buildconfigs/XXXXX: BuildConfig "XXXXX" is invalid: spec.source.git.uri: Invalid value: "git@github.com:REPO/NAME.git": uri is not a valid url
```
Our URI must support `git@SERVER:PATH`.
This blocks underlying migration of data in 3.6, and may have broken end users.
@jupierce @bparees we cannot promote 3.6 to prod without resolving this or determining it is not an issue. | non_priority | migration of prod cluster blocked on builds and build configs that fail git uri validation in a prod data set being tested on error n xxxx buildconfigs xxxxx buildconfig xxxxx is invalid spec source git uri invalid value git github com repo name git uri is not a valid url our uri must support git server path this blocks underlying migration of data in and may have broken end users jupierce bparees we cannot promote to prod without resolving this or determining it is not an issue | 0 |
49,007 | 25,939,931,214 | IssuesEvent | 2022-12-16 17:20:38 | conda-forge/status | https://api.github.com/repos/conda-forge/status | opened | Travis CI queue backed up | degraded performance | Have been seeing long queue times on Travis CI since yesterday. This can also be seen via [Travis CI's insight tab for the org]( https://app.travis-ci.com/github/conda-forge?tab=insights&timeInterval=week ). Travis CI has been notified of the issue. No ETA as of yet.
<details>
<img width="1840" alt="Screen Shot 2022-12-16 at 9 18 35 AM" src="https://user-images.githubusercontent.com/3019665/208153204-e6be612f-2832-4af8-a8ec-16af600a98b3.png">
</details> | True | Travis CI queue backed up - Have been seeing long queue times on Travis CI since yesterday. This can also be seen via [Travis CI's insight tab for the org]( https://app.travis-ci.com/github/conda-forge?tab=insights&timeInterval=week ). Travis CI has been notified of the issue. No ETA as of yet.
<details>
<img width="1840" alt="Screen Shot 2022-12-16 at 9 18 35 AM" src="https://user-images.githubusercontent.com/3019665/208153204-e6be612f-2832-4af8-a8ec-16af600a98b3.png">
</details> | non_priority | travis ci queue backed up have been seeing long queue times on travis ci since yesterday this can also be seen via travis ci has been notified of the issue no eta as of yet img width alt screen shot at am src | 0 |
475,085 | 13,686,674,593 | IssuesEvent | 2020-09-30 09:02:09 | wso2/product-is | https://api.github.com/repos/wso2/product-is | closed | Dev server gives runtime errors for Console Application | Component/Identity Apps Priority/High Severity/Major bug console dev-exp | **Describe the issue:**
When the console application is run in the dev mode, the app appears broken and the following error is available in the browser console.
<img width="348" alt="Screen Shot 2020-09-29 at 1 56 31 PM" src="https://user-images.githubusercontent.com/25959096/94661445-b082cc00-0324-11eb-9c2a-171d965841ca.png">
**How to reproduce:**
1. Open the console application in dev mode.
2. Navigate to `https://localhost:9443/console`
**Expected behavior:**
The app should work as expected.
**Environment information** (_Please complete the following information; remove any unnecessary fields_) **:**
- Product Version: IS 5.11.0 - Alpha 3
- OS: Mac
- Database: H2
- Userstore: LDAP | 1.0 | Dev server gives runtime errors for Console Application - **Describe the issue:**
When the console application is run in the dev mode, the app appears broken and the following error is available in the browser console.
<img width="348" alt="Screen Shot 2020-09-29 at 1 56 31 PM" src="https://user-images.githubusercontent.com/25959096/94661445-b082cc00-0324-11eb-9c2a-171d965841ca.png">
**How to reproduce:**
1. Open the console application in dev mode.
2. Navigate to `https://localhost:9443/console`
**Expected behavior:**
The app should work as expected.
**Environment information** (_Please complete the following information; remove any unnecessary fields_) **:**
- Product Version: IS 5.11.0 - Alpha 3
- OS: Mac
- Database: H2
- Userstore: LDAP | priority | dev server gives runtime errors for console application describe the issue when the console application is run in the dev mode the app appears broken and the following error is available in the browser console img width alt screen shot at pm src how to reproduce open the console application in dev mode navigate to expected behavior the app should work as expected environment information please complete the following information remove any unnecessary fields product version is alpha os mac database userstore ldap | 1 |
830,827 | 32,025,784,156 | IssuesEvent | 2023-09-22 08:44:27 | nikobatzi1990/fvgl_work-in-progress | https://api.github.com/repos/nikobatzi1990/fvgl_work-in-progress | closed | Add Delete button | enhancement priority | - [x] users should be able to delete a game from their list by clicking the button | 1.0 | Add Delete button - - [x] users should be able to delete a game from their list by clicking the button | priority | add delete button users should be able to delete a game from their list by clicking the button | 1 |
240,921 | 7,807,354,194 | IssuesEvent | 2018-06-11 16:34:59 | craftercms/craftercms | https://api.github.com/repos/craftercms/craftercms | opened | [studio] allow sandbox branch configuration per site | enhancement priority: high | ### Expected behavior
Admin should be able to configure the active branch of the sandbox on a per-site basis
### Actual behavior
Today, configuration is site wide.
### Steps to reproduce the problem
N/a
### Log/stack trace (use https://gist.github.com)
N/a
### Specs
#### Version
Studio Version Number: 3.0.14-SNAPSHOT-bb5185
Build Number: bb518515b875d7784bb698317a7d0d3f36e2cbe0
Build Date/Time: 06-08-2018 09:50:34 -0400
#### OS
#### Browser
N/a
| 1.0 | [studio] allow sandbox branch configuration per site - ### Expected behavior
Admin should be able to configure the active branch of the sandbox on a per-site basis
### Actual behavior
Today, configuration is site wide.
### Steps to reproduce the problem
N/a
### Log/stack trace (use https://gist.github.com)
N/a
### Specs
#### Version
Studio Version Number: 3.0.14-SNAPSHOT-bb5185
Build Number: bb518515b875d7784bb698317a7d0d3f36e2cbe0
Build Date/Time: 06-08-2018 09:50:34 -0400
#### OS
#### Browser
N/a
| priority | allow sandbox branch configuration per site expected behavior admin should be able to configure the active branch of the sandbox on a per site basis actual behavior today configuration is site wide steps to reproduce the problem n a log stack trace use n a specs version studio version number snapshot build number build date time os browser n a | 1 |
205,273 | 7,096,449,142 | IssuesEvent | 2018-01-14 07:17:00 | TMats/survey | https://api.github.com/repos/TMats/survey | opened | Deep Neural Networks as Gaussian Processes | Priority: High Statistical Learning Theory | https://arxiv.org/abs/1711.00165
- Jaehoon Lee, Yasaman Bahri, Roman Novak, Samuel S. Schoenholz, Jeffrey Pennington, Jascha Sohl-Dickstein
- Submitted on 1 Nov 2017 | 1.0 | Deep Neural Networks as Gaussian Processes - https://arxiv.org/abs/1711.00165
- Jaehoon Lee, Yasaman Bahri, Roman Novak, Samuel S. Schoenholz, Jeffrey Pennington, Jascha Sohl-Dickstein
- Submitted on 1 Nov 2017 | priority | deep neural networks as gaussian processes jaehoon lee yasaman bahri roman novak samuel s schoenholz jeffrey pennington jascha sohl dickstein submitted on nov | 1 |
149,118 | 13,257,091,395 | IssuesEvent | 2020-08-20 13:37:22 | cornellius-gp/gpytorch | https://api.github.com/repos/cornellius-gp/gpytorch | closed | [Question] | documentation | # 📚 Documentation/Examples
Hi,
In my problem, the outputs are constrained to [0,1]. I wonder if there's a way to impose this nonnegativity in gpytorch. Currently, the outputs I got expand to <0. Thank you very much.
** Is there documentation missing? **
<!-- Let us know what modules have missing or incomplete documentation -->
** Is documentation wrong? **
<!-- Let us know if you find a mistake in the documentation! -->
** Is there a feature that needs some example code? **
<!-- Let us know if we're missing any example notebooks -->
** Think you know how to fix the docs? ** (If so, we'd love a pull request from you!)
- Link to [GPyTorch documentation](https://gpytorch.readthedocs.io)
- Link to [GPyTorch examples](https://github.com/cornellius-gp/gpytorch/tree/master/examples)
| 1.0 | [Question] - # 📚 Documentation/Examples
Hi,
In my problem, the outputs are constrained to [0,1]. I wonder if there's a way to impose this nonnegativity in gpytorch. Currently, the outputs I got expand to <0. Thank you very much.
** Is there documentation missing? **
<!-- Let us know what modules have missing or incomplete documentation -->
** Is documentation wrong? **
<!-- Let us know if you find a mistake in the documentation! -->
** Is there a feature that needs some example code? **
<!-- Let us know if we're missing any example notebooks -->
** Think you know how to fix the docs? ** (If so, we'd love a pull request from you!)
- Link to [GPyTorch documentation](https://gpytorch.readthedocs.io)
- Link to [GPyTorch examples](https://github.com/cornellius-gp/gpytorch/tree/master/examples)
| non_priority | 📚 documentation examples hi in my problem the outputs are constrained to i wonder if there s a way to impose this nonnegativity in gpytorch currently the outputs i got expand to thank you very much is there documentation missing is documentation wrong is there a feature that needs some example code think you know how to fix the docs if so we d love a pull request from you link to link to | 0 |
300,013 | 9,206,060,451 | IssuesEvent | 2019-03-08 12:35:23 | pmem/issues | https://api.github.com/repos/pmem/issues | closed | Remote files removed from replica although pool is opened | Exposure: Medium OS: Linux Priority: 3 medium State: To be verified Type: Bug | $cat pool.set:
```
PMEMPOOLSET
15M /dev/shm/pool
REPLICA 192.168.0.182 rep.set
```
$cat rep.set:
```
PMEMPOOLSET
10M /dev/shm/rep.1
10M /dev/shm/rep.2
```
App:
```
int main() {
PMEMobjpool *pop = pmemobj_create("pool.set", NULL, 0, 0666);
assert(pop);
int ret = pmempool_rm("pool.set", 0);
printf("ret: %i\nerrno: %i", ret, errno);
pmemobj_close(pop);
return 0;
}
```
All local and remote pool files were created properly.
When pmempool_rm was called: ret = -1 and errno = 11, but remote pool files were removed from remote host.
Dbg.logs:
```
(...)
<libpmempool>: <4> [set.c:1686 util_poolset_parse] set file format correct (pool.set)
<libpmempool>: <3> [set.c:1186 util_poolset_check_options] set 0x69ae690
<libpmempool>: <3> [set.c:1202 util_poolset_set_size] set 0x69ae690
<libpmempool>: <3> [set.c:1238 util_poolset_set_size] pool size set to 15728640
<libpmempool>: <3> [file.c:590 util_unlink_flock] path "/dev/shm/pool"
<libpmempool>: <3> [file.c:503 util_file_open] path "/dev/shm/pool" size (nil) minsize 0 flags 0
<libpmempool>: <1> [file.c:518 util_file_open] flock "/dev/shm/pool": Resource temporarily unavailable
<libpmempool>: <2> [file.c:601 util_unlink_flock] failed to open file "/dev/shm/pool"
<libpmempool>: <1> [rm.c:94 rm_local] /dev/shm/pool: removing file failed
<librpmem>: <3> [rpmem.c:751 rpmem_remove] target 192.168.0.182, pool_set rep.set, flags 0
<librpmem>: <4> [rpmem_cmd.c:147 rpmem_cmd_log] executing command 'ssh -T -oBatchMode=yes 192.168.0.182 rpmemd --remove rep.set'
<libpmempool>: <3> [rm.c:129 rm_remote] 192.168.0.182/rep.set: removed
(...)
```
Found on 1.4-rc3-14-g53bdc41
| 1.0 | Remote files removed from replica although pool is opened - $cat pool.set:
```
PMEMPOOLSET
15M /dev/shm/pool
REPLICA 192.168.0.182 rep.set
```
$cat rep.set:
```
PMEMPOOLSET
10M /dev/shm/rep.1
10M /dev/shm/rep.2
```
App:
```
int main() {
PMEMobjpool *pop = pmemobj_create("pool.set", NULL, 0, 0666);
assert(pop);
int ret = pmempool_rm("pool.set", 0);
printf("ret: %i\nerrno: %i", ret, errno);
pmemobj_close(pop);
return 0;
}
```
All local and remote pool files were created properly.
When pmempool_rm was called: ret = -1 and errno = 11, but remote pool files were removed from remote host.
Dbg.logs:
```
(...)
<libpmempool>: <4> [set.c:1686 util_poolset_parse] set file format correct (pool.set)
<libpmempool>: <3> [set.c:1186 util_poolset_check_options] set 0x69ae690
<libpmempool>: <3> [set.c:1202 util_poolset_set_size] set 0x69ae690
<libpmempool>: <3> [set.c:1238 util_poolset_set_size] pool size set to 15728640
<libpmempool>: <3> [file.c:590 util_unlink_flock] path "/dev/shm/pool"
<libpmempool>: <3> [file.c:503 util_file_open] path "/dev/shm/pool" size (nil) minsize 0 flags 0
<libpmempool>: <1> [file.c:518 util_file_open] flock "/dev/shm/pool": Resource temporarily unavailable
<libpmempool>: <2> [file.c:601 util_unlink_flock] failed to open file "/dev/shm/pool"
<libpmempool>: <1> [rm.c:94 rm_local] /dev/shm/pool: removing file failed
<librpmem>: <3> [rpmem.c:751 rpmem_remove] target 192.168.0.182, pool_set rep.set, flags 0
<librpmem>: <4> [rpmem_cmd.c:147 rpmem_cmd_log] executing command 'ssh -T -oBatchMode=yes 192.168.0.182 rpmemd --remove rep.set'
<libpmempool>: <3> [rm.c:129 rm_remote] 192.168.0.182/rep.set: removed
(...)
```
Found on 1.4-rc3-14-g53bdc41
| priority | remote files removed from replica although pool is opened cat pool set pmempoolset dev shm pool replica rep set cat rep set pmempoolset dev shm rep dev shm rep app int main pmemobjpool pop pmemobj create pool set null assert pop int ret pmempool rm pool set printf ret i nerrno i ret errno pmemobj close pop return all local and remote pool files were created properly when pmempool rm was called ret and errno but remote pool files were removed from remote host dbg logs set file format correct pool set set set pool size set to path dev shm pool path dev shm pool size nil minsize flags flock dev shm pool resource temporarily unavailable failed to open file dev shm pool dev shm pool removing file failed target pool set rep set flags executing command ssh t obatchmode yes rpmemd remove rep set rep set removed found on | 1 |
165,727 | 14,008,995,606 | IssuesEvent | 2020-10-29 01:10:33 | w3c/aria-at | https://api.github.com/repos/w3c/aria-at | opened | Document repo and app permission management models | documentation | We have multiple GitHub teams in the aria-at and aria-at-app repos for managing roles and permissions across the project. It would be very helpful to have a wiki page that documents each team and its purpose. | 1.0 | Document repo and app permission management models - We have multiple GitHub teams in the aria-at and aria-at-app repos for managing roles and permissions across the project. It would be very helpful to have a wiki page that documents each team and its purpose. | non_priority | document repo and app permission management models we have multiple github teams in the aria at and aria at app repos for managing roles and permissions across the project it would be very helpful to have a wiki page that documents each team and its purpose | 0 |
743,311 | 25,894,456,705 | IssuesEvent | 2022-12-14 20:59:37 | az-digital/az_quickstart | https://api.github.com/repos/az-digital/az_quickstart | reopened | Remove dependency on Bootstrap Barrio ("fork barrio today") | enhancement high priority | ## Motivation
Increasingly we find ourselves needing to override, unset, or removed styles or functionality provided by the Bootstrap Barrio theme that our Arizona Barrio theme currently extends.
## Proposed Resolution
We should "fork" Bootstrap Barrio (i.e. remove Arizona Barrio's dependency on Bootstrap Barrio). This will require copying all of the base theme files/functionality provided by Bootstrap Barrio into Arizona Barrio.
### Describe alternatives you've considered
There have been several Quickstart issues we've merged PRs for that have added code to Arizona Barrio to unset stylesheets included in Bootstrap Barrio's `global-styling` library, e.g.:
- #795
- #852
- #251
- #438
## Additional context
Starting with Drupal 10.0.x, Drupal core no longer ships with any themes that are recommended for use as a `base theme` and instead now includes a "Starterkit theme generator" which is the new recommended best practice for creating new themes (see https://www.drupal.org/about/core/blog/new-starterkit-will-change-how-you-create-themes-in-drupal-10, https://www.drupal.org/node/3305674 and https://www.drupal.org/node/3309392).
### Original issue description (submitted by @camikazegreen 2021-04-27)
#### What is the problem that we want to solve?
There have been several choices made by the maintainer of Barrio that we did not agree with.
We should reconsider whether or not we want to fork Barrio. | 1.0 | Remove dependency on Bootstrap Barrio ("fork barrio today") - ## Motivation
Increasingly we find ourselves needing to override, unset, or removed styles or functionality provided by the Bootstrap Barrio theme that our Arizona Barrio theme currently extends.
## Proposed Resolution
We should "fork" Bootstrap Barrio (i.e. remove Arizona Barrio's dependency on Bootstrap Barrio). This will require copying all of the base theme files/functionality provided by Bootstrap Barrio into Arizona Barrio.
### Describe alternatives you've considered
There have been several Quickstart issues we've merged PRs for that have added code to Arizona Barrio to unset stylesheets included in Bootstrap Barrio's `global-styling` library, e.g.:
- #795
- #852
- #251
- #438
## Additional context
Starting with Drupal 10.0.x, Drupal core no longer ships with any themes that are recommended for use as a `base theme` and instead now includes a "Starterkit theme generator" which is the new recommended best practice for creating new themes (see https://www.drupal.org/about/core/blog/new-starterkit-will-change-how-you-create-themes-in-drupal-10, https://www.drupal.org/node/3305674 and https://www.drupal.org/node/3309392).
### Original issue description (submitted by @camikazegreen 2021-04-27)
#### What is the problem that we want to solve?
There have been several choices made by the maintainer of Barrio that we did not agree with.
We should reconsider whether or not we want to fork Barrio. | priority | remove dependency on bootstrap barrio fork barrio today motivation increasingly we find ourselves needing to override unset or removed styles or functionality provided by the bootstrap barrio theme that our arizona barrio theme currently extends proposed resolution we should fork bootstrap barrio i e remove arizona barrio s dependency on bootstrap barrio this will require copying all of the base theme files functionality provided by bootstrap barrio into arizona barrio describe alternatives you ve considered there have been several quickstart issues we ve merged prs for that have added code to arizona barrio to unset stylesheets included in bootstrap barrio s global styling library e g additional context starting with drupal x drupal core no longer ships with any themes that are recommended for use as a base theme and instead now includes a starterkit theme generator which is the new recommended best practice for creating new themes see and original issue description submitted by camikazegreen what is the problem that we want to solve there have been several choices made by the maintainer of barrio that we did not agree with we should reconsider whether or not we want to fork barrio | 1 |
25,892 | 2,684,028,934 | IssuesEvent | 2015-03-28 15:50:06 | ConEmu/old-issues | https://api.github.com/repos/ConEmu/old-issues | closed | PicView2 does not properly display BMP files (adds some kind of transparency to them) | 1 star bug imported invalid Priority-Medium | _From [sorin.sb...@gmail.com](https://code.google.com/u/107935209617580335268/) on November 10, 2011 05:53:08_
It seems that PicView2 has some issues displaying BMP files. I will attach both sample bmp and screenshot.
_Original issue: http://code.google.com/p/conemu-maximus5/issues/detail?id=453_ | 1.0 | PicView2 does not properly display BMP files (adds some kind of transparency to them) - _From [sorin.sb...@gmail.com](https://code.google.com/u/107935209617580335268/) on November 10, 2011 05:53:08_
It seems that PicView2 has some issues displaying BMP files. I will attach both sample bmp and screenshot.
_Original issue: http://code.google.com/p/conemu-maximus5/issues/detail?id=453_ | priority | does not properly display bmp files adds some kind of transparency to them from on november it seems that has some issues displaying bmp files i will attach both sample bmp and screenshot original issue | 1 |
174,017 | 21,192,957,759 | IssuesEvent | 2022-04-08 19:45:11 | xmidt-org/petasos | https://api.github.com/repos/xmidt-org/petasos | opened | CVE-2020-9283 (High) detected in github.com/hashicorp/consul-v1.7.0 | security vulnerability | ## CVE-2020-9283 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/hashicorp/consul-v1.7.0</b></p></summary>
<p>Consul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.</p>
<p>
Dependency Hierarchy:
- github.com/go-kit/kit-v0.10.0 (Root Library)
- :x: **github.com/hashicorp/consul-v1.7.0** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/xmidt-org/petasos/commit/d09bd31bc55e2d781858b9232d53bbc245c9ad6b">d09bd31bc55e2d781858b9232d53bbc245c9ad6b</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>
golang.org/x/crypto before v0.0.0-20200220183623-bac4c82f6975 for Go allows a panic during signature verification in the golang.org/x/crypto/ssh package. A client can attack an SSH server that accepts public keys. Also, a server can attack any SSH client.
<p>Publish Date: 2020-02-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9283>CVE-2020-9283</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9283">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9283</a></p>
<p>Release Date: 2020-02-20</p>
<p>Fix Resolution: github.com/golang/crypto - bac4c82f69751a6dd76e702d54b3ceb88adab236</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-9283 (High) detected in github.com/hashicorp/consul-v1.7.0 - ## CVE-2020-9283 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/hashicorp/consul-v1.7.0</b></p></summary>
<p>Consul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.</p>
<p>
Dependency Hierarchy:
- github.com/go-kit/kit-v0.10.0 (Root Library)
- :x: **github.com/hashicorp/consul-v1.7.0** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/xmidt-org/petasos/commit/d09bd31bc55e2d781858b9232d53bbc245c9ad6b">d09bd31bc55e2d781858b9232d53bbc245c9ad6b</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>
golang.org/x/crypto before v0.0.0-20200220183623-bac4c82f6975 for Go allows a panic during signature verification in the golang.org/x/crypto/ssh package. A client can attack an SSH server that accepts public keys. Also, a server can attack any SSH client.
<p>Publish Date: 2020-02-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9283>CVE-2020-9283</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9283">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9283</a></p>
<p>Release Date: 2020-02-20</p>
<p>Fix Resolution: github.com/golang/crypto - bac4c82f69751a6dd76e702d54b3ceb88adab236</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 github com hashicorp consul cve high severity vulnerability vulnerable library github com hashicorp consul consul is a distributed highly available and data center aware solution to connect and configure applications across dynamic distributed infrastructure dependency hierarchy github com go kit kit root library x github com hashicorp consul vulnerable library found in head commit a href found in base branch main vulnerability details golang org x crypto before for go allows a panic during signature verification in the golang org x crypto ssh package a client can attack an ssh server that accepts public keys also a server can attack any ssh client 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 github com golang crypto step up your open source security game with whitesource | 0 |
205,759 | 16,008,402,479 | IssuesEvent | 2021-04-20 07:30:27 | terraform-providers/terraform-provider-azurerm | https://api.github.com/repos/terraform-providers/terraform-provider-azurerm | closed | netapp dual protocol volume export policy does not allow to use of allow_root_access | bug documentation service/netapp | using
tf 14.10
hashicorp/azurerm 2.55.0
Create a dual protocol netapp volume.
Use example: https://github.com/terraform-providers/terraform-provider-azurerm/blob/master/examples/netapp/volume_dual_protocol/main.tf .
Add allow_root_access = yes to export policy block per documentation https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/netapp_volume#allow_root_access:
export_policy_rule {
rule_index = 1
allowed_clients = ["0.0.0.0/0"]
cifs_enabled = true
nfsv3_enabled = true
nfsv4_enabled = false
unix_read_write = true
allow_root_access = true
}
Error result is:
Error: Unsupported argument
on deploy.tf line 80, in resource "azurerm_netapp_volume" "ultra-aaa-volume021":
80: allow_root_access = true
An argument named "allow_root_access" is not expected here.
| 1.0 | netapp dual protocol volume export policy does not allow to use of allow_root_access - using
tf 14.10
hashicorp/azurerm 2.55.0
Create a dual protocol netapp volume.
Use example: https://github.com/terraform-providers/terraform-provider-azurerm/blob/master/examples/netapp/volume_dual_protocol/main.tf .
Add allow_root_access = yes to export policy block per documentation https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/netapp_volume#allow_root_access:
export_policy_rule {
rule_index = 1
allowed_clients = ["0.0.0.0/0"]
cifs_enabled = true
nfsv3_enabled = true
nfsv4_enabled = false
unix_read_write = true
allow_root_access = true
}
Error result is:
Error: Unsupported argument
on deploy.tf line 80, in resource "azurerm_netapp_volume" "ultra-aaa-volume021":
80: allow_root_access = true
An argument named "allow_root_access" is not expected here.
| non_priority | netapp dual protocol volume export policy does not allow to use of allow root access using tf hashicorp azurerm create a dual protocol netapp volume use example add allow root access yes to export policy block per documentation export policy rule rule index allowed clients cifs enabled true enabled true enabled false unix read write true allow root access true error result is error unsupported argument on deploy tf line in resource azurerm netapp volume ultra aaa allow root access true an argument named allow root access is not expected here | 0 |
22,453 | 10,757,562,619 | IssuesEvent | 2019-10-31 13:31:11 | TheThingsNetwork/lorawan-stack | https://api.github.com/repos/TheThingsNetwork/lorawan-stack | opened | NS and AS Device Registries do not check for _KEYS rights | bug c/application server c/network server security | <!--
Thanks for submitting a bug report. Please fill the template below,
otherwise we will not be able to process this bug report.
-->
#### Summary
<!-- Summarize the problem in a few sentences: -->
The device registry gRPC services in the Network Server and Application Server do not check for the `RIGHT_APPLICATION_DEVICES_READ_KEYS` and `RIGHT_APPLICATION_DEVICES_WRITE_KEYS` rights.
#### What do you see now?
<!--
Please paste terminal output, upload logs (as .txt) or upload screenshots.
-->
Only the Join Server checks: https://github.com/TheThingsNetwork/lorawan-stack/blob/master/pkg/joinserver/grpc_deviceregistry.go#L55-L56
#### What do you want to see instead?
<!-- Please add some examples or mock-ups if applicable. -->
The Network Server and Application Server need to check as well.
#### How do you propose to implement this?
<!-- Please think about how this could be fixed. -->
Field mask path magic and defer statements? | True | NS and AS Device Registries do not check for _KEYS rights - <!--
Thanks for submitting a bug report. Please fill the template below,
otherwise we will not be able to process this bug report.
-->
#### Summary
<!-- Summarize the problem in a few sentences: -->
The device registry gRPC services in the Network Server and Application Server do not check for the `RIGHT_APPLICATION_DEVICES_READ_KEYS` and `RIGHT_APPLICATION_DEVICES_WRITE_KEYS` rights.
#### What do you see now?
<!--
Please paste terminal output, upload logs (as .txt) or upload screenshots.
-->
Only the Join Server checks: https://github.com/TheThingsNetwork/lorawan-stack/blob/master/pkg/joinserver/grpc_deviceregistry.go#L55-L56
#### What do you want to see instead?
<!-- Please add some examples or mock-ups if applicable. -->
The Network Server and Application Server need to check as well.
#### How do you propose to implement this?
<!-- Please think about how this could be fixed. -->
Field mask path magic and defer statements? | non_priority | ns and as device registries do not check for keys rights thanks for submitting a bug report please fill the template below otherwise we will not be able to process this bug report summary the device registry grpc services in the network server and application server do not check for the right application devices read keys and right application devices write keys rights what do you see now please paste terminal output upload logs as txt or upload screenshots only the join server checks what do you want to see instead the network server and application server need to check as well how do you propose to implement this field mask path magic and defer statements | 0 |
150,937 | 5,793,997,801 | IssuesEvent | 2017-05-02 13:59:05 | hydroshare/hydroshare | https://api.github.com/repos/hydroshare/hydroshare | closed | Browsing for files to add to resources | Appearance enhancement in progress Low Priority | When browsing to add multiple files to a resource, the file names selected should be listed when there is more than one file.
List files selected rather than just indicating 2 files selected.
If a user browses again the files they select should be added to the list, rather than the list being replaced.
A user should be able to delete files from the files selected.
| 1.0 | Browsing for files to add to resources - When browsing to add multiple files to a resource, the file names selected should be listed when there is more than one file.
List files selected rather than just indicating 2 files selected.
If a user browses again the files they select should be added to the list, rather than the list being replaced.
A user should be able to delete files from the files selected.
| priority | browsing for files to add to resources when browsing to add multiple files to a resource the file names selected should be listed when there is more than one file list files selected rather than just indicating files selected if a user browses again the files they select should be added to the list rather than the list being replaced a user should be able to delete files from the files selected | 1 |
266,799 | 23,260,689,477 | IssuesEvent | 2022-08-04 13:16:54 | keycloak/keycloak | https://api.github.com/repos/keycloak/keycloak | opened | Quarkus testsuite should use storage=chm by default where it makes sense | area/testsuite kind/enhancement status/triage | ### Description
In order to improve startup times (see draft PR here: https://github.com/keycloak/keycloak/pull/13443 ) and not having to add `--storage=chm` for most tests where it should be used, we want the quarkus testsuite to use `--storage=chm` if not otherwise specified.
Also, it should be possible to use the legacy store "on demand", for example with a method-level annotation like `@WithLegacyStore` or a similar solution that uses dev-file instead of the new chm store when set (e.g. for the import / export tests).
### Discussion
_No response_
### Motivation
_No response_
### Details
_No response_ | 1.0 | Quarkus testsuite should use storage=chm by default where it makes sense - ### Description
In order to improve startup times (see draft PR here: https://github.com/keycloak/keycloak/pull/13443 ) and not having to add `--storage=chm` for most tests where it should be used, we want the quarkus testsuite to use `--storage=chm` if not otherwise specified.
Also, it should be possible to use the legacy store "on demand", for example with a method-level annotation like `@WithLegacyStore` or a similar solution that uses dev-file instead of the new chm store when set (e.g. for the import / export tests).
### Discussion
_No response_
### Motivation
_No response_
### Details
_No response_ | non_priority | quarkus testsuite should use storage chm by default where it makes sense description in order to improve startup times see draft pr here and not having to add storage chm for most tests where it should be used we want the quarkus testsuite to use storage chm if not otherwise specified also it should be possible to use the legacy store on demand for example with a method level annotation like withlegacystore or a similar solution that uses dev file instead of the new chm store when set e g for the import export tests discussion no response motivation no response details no response | 0 |
775,796 | 27,237,431,408 | IssuesEvent | 2023-02-21 17:21:10 | Baystation12/Baystation12 | https://api.github.com/repos/Baystation12/Baystation12 | closed | Unathi EC gloves have no sprites | Priority: Trivial Sprites Needs Reproduction | ### Description of issue
EC duty gloves don't show up on unathi sprites.
### Difference between expected and actual behaviour
Gloves should show up on unathi sprites
### Steps to reproduce
1. Join as Unathi EC
2. Vend departmental duty gloves
3. Wirecut departmental duty gloves
4. Put on departmental duty gloves
5. Despair as they don't show on your sprite
### Specific information for locating
_No response_
### Client version, server revision, & game ID
Client Version: 514
Server Revision: [3d08bbe23177026398d67e8a5c05b603d4a40b3d ](https://bay.ss13.me/github/commit/3d08bbe23177026398d67e8a5c05b603d4a40b3d) - dev - 2023-01-25
Game ID: cl6-bGXt
Current map: SEV Torch
### Issue bingo
- [X] Issue could be reproduced at least once
- [ ] Issue could be reproduced by different players
- [X] Issue could be reproduced in multiple rounds
- [X] Issue happened in a recent (less than 7 days ago) round
- [X] [Couldn't find an existing issue about this](https://github.com/Baystation12/Baystation12/issues) | 1.0 | Unathi EC gloves have no sprites - ### Description of issue
EC duty gloves don't show up on unathi sprites.
### Difference between expected and actual behaviour
Gloves should show up on unathi sprites
### Steps to reproduce
1. Join as Unathi EC
2. Vend departmental duty gloves
3. Wirecut departmental duty gloves
4. Put on departmental duty gloves
5. Despair as they don't show on your sprite
### Specific information for locating
_No response_
### Client version, server revision, & game ID
Client Version: 514
Server Revision: [3d08bbe23177026398d67e8a5c05b603d4a40b3d ](https://bay.ss13.me/github/commit/3d08bbe23177026398d67e8a5c05b603d4a40b3d) - dev - 2023-01-25
Game ID: cl6-bGXt
Current map: SEV Torch
### Issue bingo
- [X] Issue could be reproduced at least once
- [ ] Issue could be reproduced by different players
- [X] Issue could be reproduced in multiple rounds
- [X] Issue happened in a recent (less than 7 days ago) round
- [X] [Couldn't find an existing issue about this](https://github.com/Baystation12/Baystation12/issues) | priority | unathi ec gloves have no sprites description of issue ec duty gloves don t show up on unathi sprites difference between expected and actual behaviour gloves should show up on unathi sprites steps to reproduce join as unathi ec vend departmental duty gloves wirecut departmental duty gloves put on departmental duty gloves despair as they don t show on your sprite specific information for locating no response client version server revision game id client version server revision dev game id bgxt current map sev torch issue bingo issue could be reproduced at least once issue could be reproduced by different players issue could be reproduced in multiple rounds issue happened in a recent less than days ago round | 1 |
273,989 | 23,801,177,211 | IssuesEvent | 2022-09-03 10:09:17 | unitystation/unitystation | https://api.github.com/repos/unitystation/unitystation | closed | Mobs cannot be hit by thrown objects | Type: Bug System: Damage ValidForContest | <!-- Make sure to search existing issues first to avoid duplicates. -->
### Environment
- Game Version: 21060314
### Detailed description of bug
I tried throwing things at mobs and:
- items fly though friendly mobs
- items stop in front of hostile mobs as if they hit a wall
This is bad because there are actually throwable weapons, currently these can only be used on players/
| 1.0 | Mobs cannot be hit by thrown objects - <!-- Make sure to search existing issues first to avoid duplicates. -->
### Environment
- Game Version: 21060314
### Detailed description of bug
I tried throwing things at mobs and:
- items fly though friendly mobs
- items stop in front of hostile mobs as if they hit a wall
This is bad because there are actually throwable weapons, currently these can only be used on players/
| non_priority | mobs cannot be hit by thrown objects environment game version detailed description of bug i tried throwing things at mobs and items fly though friendly mobs items stop in front of hostile mobs as if they hit a wall this is bad because there are actually throwable weapons currently these can only be used on players | 0 |
570,771 | 17,023,178,465 | IssuesEvent | 2021-07-03 00:43:44 | tomhughes/trac-tickets | https://api.github.com/repos/tomhughes/trac-tickets | closed | Reprioritization of entries in the rendering queue | Component: osmarender Priority: minor Resolution: fixed Type: enhancement | **[Submitted to the original trac issue database at 9.08am, Wednesday, 19th September 2007]**
If a tile is requested with a low priority, and is rerequested with a high priority, it should (IMHO) be reprioritized and moved to the higher priority queue.
Currently, if a tile i rerequested, the new request will be just thrown away. This means that a higher priority user/system can be "starved" by a lower priority user/system. In a worst case scenario, one user may request the entire world and then nobody can get tiles that are being actively worked upon rendered for ages..
| 1.0 | Reprioritization of entries in the rendering queue - **[Submitted to the original trac issue database at 9.08am, Wednesday, 19th September 2007]**
If a tile is requested with a low priority, and is rerequested with a high priority, it should (IMHO) be reprioritized and moved to the higher priority queue.
Currently, if a tile i rerequested, the new request will be just thrown away. This means that a higher priority user/system can be "starved" by a lower priority user/system. In a worst case scenario, one user may request the entire world and then nobody can get tiles that are being actively worked upon rendered for ages..
| priority | reprioritization of entries in the rendering queue if a tile is requested with a low priority and is rerequested with a high priority it should imho be reprioritized and moved to the higher priority queue currently if a tile i rerequested the new request will be just thrown away this means that a higher priority user system can be starved by a lower priority user system in a worst case scenario one user may request the entire world and then nobody can get tiles that are being actively worked upon rendered for ages | 1 |
358,373 | 25,189,177,719 | IssuesEvent | 2022-11-11 21:43:15 | test-design-org/general-predicate-testing | https://api.github.com/repos/test-design-org/general-predicate-testing | opened | Create Docosaurus wiki | documentation | We could use [Docusaurus](https://docusaurus.io) to create a wiki for GPT.
We'd need:
- [ ] Docusaurus on a separate branch
- [ ] Deployed to Github Pages
- [ ] CI set up for automatic deployment to Github Pages | 1.0 | Create Docosaurus wiki - We could use [Docusaurus](https://docusaurus.io) to create a wiki for GPT.
We'd need:
- [ ] Docusaurus on a separate branch
- [ ] Deployed to Github Pages
- [ ] CI set up for automatic deployment to Github Pages | non_priority | create docosaurus wiki we could use to create a wiki for gpt we d need docusaurus on a separate branch deployed to github pages ci set up for automatic deployment to github pages | 0 |
9,371 | 2,615,146,139 | IssuesEvent | 2015-03-01 06:22:09 | chrsmith/html5rocks | https://api.github.com/repos/chrsmith/html5rocks | closed | Add globe to studio | auto-migrated Milestone-4 Priority-Medium Studio Type-Defect | ```
What steps will reproduce the problem?
1.
2.
3.
What is the expected output? What do you see instead?
Please use labels and text to provide additional information.
```
Original issue reported on code.google.com by `v...@google.com` on 15 Aug 2010 at 6:28 | 1.0 | Add globe to studio - ```
What steps will reproduce the problem?
1.
2.
3.
What is the expected output? What do you see instead?
Please use labels and text to provide additional information.
```
Original issue reported on code.google.com by `v...@google.com` on 15 Aug 2010 at 6:28 | non_priority | add globe to studio what steps will reproduce the problem what is the expected output what do you see instead please use labels and text to provide additional information original issue reported on code google com by v google com on aug at | 0 |
773,482 | 27,159,441,083 | IssuesEvent | 2023-02-17 10:36:22 | wso2/api-manager | https://api.github.com/repos/wso2/api-manager | closed | [4.2.0][Dependency Upgrade] Libthrift Version Upgrade | Type/Task Priority/Normal Component/APIM | ### Description
org.apache.thrift:libthrift version in APIM 4.2.0 needs to be upgraded. As of now there are two versions of libthrift available in APIM 4.2.0.
- 0.9.2
- 0.12.0
### Affected Component
APIM
### Version
4.2.0
### Related Issues
_No response_
### Suggested Labels
_No response_ | 1.0 | [4.2.0][Dependency Upgrade] Libthrift Version Upgrade - ### Description
org.apache.thrift:libthrift version in APIM 4.2.0 needs to be upgraded. As of now there are two versions of libthrift available in APIM 4.2.0.
- 0.9.2
- 0.12.0
### Affected Component
APIM
### Version
4.2.0
### Related Issues
_No response_
### Suggested Labels
_No response_ | priority | libthrift version upgrade description org apache thrift libthrift version in apim needs to be upgraded as of now there are two versions of libthrift available in apim affected component apim version related issues no response suggested labels no response | 1 |
82,754 | 7,852,182,964 | IssuesEvent | 2018-06-20 13:58:36 | gctools-outilsgc/design-system | https://api.github.com/repos/gctools-outilsgc/design-system | closed | Typography: Heading sizes (suggest multi-device testing) | review testing | Just a heads up that picking specific heading sizes can be a tricky venture. With regards to WET, we had to juggle the heading sizes a lot because of how they rendered across devices. The juggling was necessary because on certain devices the headings sizes were too similar making it very difficult to tell which heading level we were at, or whether to nearby headings were parent/child headings or sibling headings.
Suggest testing the heading sizes across devices and zoom levels to ensure they remain distinctive enough for users to visually understand their meaning (respective levels). | 1.0 | Typography: Heading sizes (suggest multi-device testing) - Just a heads up that picking specific heading sizes can be a tricky venture. With regards to WET, we had to juggle the heading sizes a lot because of how they rendered across devices. The juggling was necessary because on certain devices the headings sizes were too similar making it very difficult to tell which heading level we were at, or whether to nearby headings were parent/child headings or sibling headings.
Suggest testing the heading sizes across devices and zoom levels to ensure they remain distinctive enough for users to visually understand their meaning (respective levels). | non_priority | typography heading sizes suggest multi device testing just a heads up that picking specific heading sizes can be a tricky venture with regards to wet we had to juggle the heading sizes a lot because of how they rendered across devices the juggling was necessary because on certain devices the headings sizes were too similar making it very difficult to tell which heading level we were at or whether to nearby headings were parent child headings or sibling headings suggest testing the heading sizes across devices and zoom levels to ensure they remain distinctive enough for users to visually understand their meaning respective levels | 0 |
40,033 | 2,862,411,627 | IssuesEvent | 2015-06-04 04:14:51 | GoogleCloudPlatform/kubernetes | https://api.github.com/repos/GoogleCloudPlatform/kubernetes | closed | Kubectl should be smarter about the stop timeout | area/usability component/CLI priority/P2 team/UX | Currently kubectl has a hard timeout on the stop operation. This is often too low for large clusters. It can figure out a good timeout based on the replica count (for rcs) and the qps (which it will have to guess, or import as a const). I'm looking for a way to avoid confusion like: https://github.com/GoogleCloudPlatform/kubernetes/pull/8671
/ref https://github.com/GoogleCloudPlatform/kubernetes/issues/8572 | 1.0 | Kubectl should be smarter about the stop timeout - Currently kubectl has a hard timeout on the stop operation. This is often too low for large clusters. It can figure out a good timeout based on the replica count (for rcs) and the qps (which it will have to guess, or import as a const). I'm looking for a way to avoid confusion like: https://github.com/GoogleCloudPlatform/kubernetes/pull/8671
/ref https://github.com/GoogleCloudPlatform/kubernetes/issues/8572 | priority | kubectl should be smarter about the stop timeout currently kubectl has a hard timeout on the stop operation this is often too low for large clusters it can figure out a good timeout based on the replica count for rcs and the qps which it will have to guess or import as a const i m looking for a way to avoid confusion like ref | 1 |
330,910 | 24,282,974,373 | IssuesEvent | 2022-09-28 19:09:34 | jakipatryk/spark-persistent-homology | https://api.github.com/repos/jakipatryk/spark-persistent-homology | opened | Add README docs | documentation | Should contain:
- description WHY the project is needed
- how to install as dependency
- how to build/test
- API documentation
- short example usage tutorial (with code) | 1.0 | Add README docs - Should contain:
- description WHY the project is needed
- how to install as dependency
- how to build/test
- API documentation
- short example usage tutorial (with code) | non_priority | add readme docs should contain description why the project is needed how to install as dependency how to build test api documentation short example usage tutorial with code | 0 |
40,666 | 5,251,566,676 | IssuesEvent | 2017-02-02 00:10:41 | Data4Democracy/datafordemocracy.org | https://api.github.com/repos/Data4Democracy/datafordemocracy.org | closed | Site-wide header and paragraph styles | design | - Probably before we do individual page layouts, make some designs about how we'd like to present text and establish information hierarchy. It looks like this is sort of addressed by the theme, but could use a massage. :) | 1.0 | Site-wide header and paragraph styles - - Probably before we do individual page layouts, make some designs about how we'd like to present text and establish information hierarchy. It looks like this is sort of addressed by the theme, but could use a massage. :) | non_priority | site wide header and paragraph styles probably before we do individual page layouts make some designs about how we d like to present text and establish information hierarchy it looks like this is sort of addressed by the theme but could use a massage | 0 |
16,137 | 6,109,157,939 | IssuesEvent | 2017-06-21 12:27:01 | grafana/grafana | https://api.github.com/repos/grafana/grafana | closed | [Bug] init.d script grafana-server doesn't work on some systems | state: help wanted (PR) type: bug type: build & packaging | The new version of grafana init.d script doesn't work since the change: https://github.com/grafana/grafana/pull/4926
Because it uses a new function "action" to run the command. Unfortunately, this function doesn't support by all of the Linux systems. So it won't start/stop/status on some of the systems. the follow message show that why:
Debian and Ubuntu have /lib/lsb/init-functions ; SuSE has /etc/rc.status ; none of them are compatible with the others. In fact, some distributions don't use /etc/init.d at all, or use it in an incompatible way (Slackware and Arch occur to me off the top of my head; there are others)
I checked Debian 7 and SLE 11,12, both of them don't contain action function. So the init script won't work on Debian 7 and SLE 11, 12
| 1.0 | [Bug] init.d script grafana-server doesn't work on some systems - The new version of grafana init.d script doesn't work since the change: https://github.com/grafana/grafana/pull/4926
Because it uses a new function "action" to run the command. Unfortunately, this function doesn't support by all of the Linux systems. So it won't start/stop/status on some of the systems. the follow message show that why:
Debian and Ubuntu have /lib/lsb/init-functions ; SuSE has /etc/rc.status ; none of them are compatible with the others. In fact, some distributions don't use /etc/init.d at all, or use it in an incompatible way (Slackware and Arch occur to me off the top of my head; there are others)
I checked Debian 7 and SLE 11,12, both of them don't contain action function. So the init script won't work on Debian 7 and SLE 11, 12
| non_priority | init d script grafana server doesn t work on some systems the new version of grafana init d script doesn t work since the change because it uses a new function action to run the command unfortunately this function doesn t support by all of the linux systems so it won t start stop status on some of the systems the follow message show that why debian and ubuntu have lib lsb init functions suse has etc rc status none of them are compatible with the others in fact some distributions don t use etc init d at all or use it in an incompatible way slackware and arch occur to me off the top of my head there are others i checked debian and sle both of them don t contain action function so the init script won t work on debian and sle | 0 |
398,819 | 11,742,382,480 | IssuesEvent | 2020-03-12 00:35:02 | thaliawww/concrexit | https://api.github.com/repos/thaliawww/concrexit | closed | No max length for user description. | bug members priority: low | In GitLab by jeltesmits on Mar 20, 2018, 15:50
### One-sentence description
There is no maximum length for the user description
### Current behaviour
No error is given when making the user description insanely long
### Expected behaviour
It should give an error when trying to make a user description with more than *x* characters.
### Steps to reproduce
Just try it | 1.0 | No max length for user description. - In GitLab by jeltesmits on Mar 20, 2018, 15:50
### One-sentence description
There is no maximum length for the user description
### Current behaviour
No error is given when making the user description insanely long
### Expected behaviour
It should give an error when trying to make a user description with more than *x* characters.
### Steps to reproduce
Just try it | priority | no max length for user description in gitlab by jeltesmits on mar one sentence description there is no maximum length for the user description current behaviour no error is given when making the user description insanely long expected behaviour it should give an error when trying to make a user description with more than x characters steps to reproduce just try it | 1 |
775,254 | 27,225,230,346 | IssuesEvent | 2023-02-21 09:14:29 | matrixorigin/matrixone | https://api.github.com/repos/matrixorigin/matrixone | closed | [Feature Request]: Support to create system tables in sys account and read in other accounts | priority/p0 kind/feature triage/accepted source/on-demand | ### Is there an existing issue for the same feature request?
- [X] I have checked the existing issues.
### Is your feature request related to a problem?
_No response_
### Describe the feature you'd like
- Create a system table under sys account, which can be seen by other accounts
- Use the method with account id to insert the value, other accounts can only see the value that belongs only to their own account
### Describe implementation you've considered
_No response_
### Documentation, Adoption, Use Case, Migration Strategy
_No response_
### Additional information
_No response_ | 1.0 | [Feature Request]: Support to create system tables in sys account and read in other accounts - ### Is there an existing issue for the same feature request?
- [X] I have checked the existing issues.
### Is your feature request related to a problem?
_No response_
### Describe the feature you'd like
- Create a system table under sys account, which can be seen by other accounts
- Use the method with account id to insert the value, other accounts can only see the value that belongs only to their own account
### Describe implementation you've considered
_No response_
### Documentation, Adoption, Use Case, Migration Strategy
_No response_
### Additional information
_No response_ | priority | support to create system tables in sys account and read in other accounts is there an existing issue for the same feature request i have checked the existing issues is your feature request related to a problem no response describe the feature you d like create a system table under sys account which can be seen by other accounts use the method with account id to insert the value other accounts can only see the value that belongs only to their own account describe implementation you ve considered no response documentation adoption use case migration strategy no response additional information no response | 1 |
16,863 | 22,143,037,764 | IssuesEvent | 2022-06-03 08:58:05 | camunda/zeebe | https://api.github.com/repos/camunda/zeebe | closed | [EPIC] Refactor Elasticsearch Exporter Tests | kind/toil scope/broker kind/epic team/process-automation area/test | **Description**
The `elasticsearch-exporter` integration tests are currently quite convoluted. Historically, the `elasticsearch-exporter` tests used to depend on `zeebe-test` which was removed in https://github.com/camunda-cloud/zeebe/pull/8608. During the removal, some of the `zeebe-test` utilities ended up in the `elasticsearch-exporter` module where we also needed to add a lot of test scoped dependencies.
The main goals here were:
- Cover as much as possible via only unit tests. This gives us a faster feedback cycle when changing something - developers can focus on first fixing unit tests, which have smaller blast radius and faster execution, before even looking at integration tests.
- Narrow the scope of the integration tests as much as possible. This meant getting rid of the broker, workflow engine semantics, etc., and just testing the integration of the exporter instance with Elasticsearch.
In general, I wanted to keep the same coverage as before. I think the coverage is now higher, but that was not the original motivation.
**Breakdown**
- [x] #9162
- [x] #9315
- [x] #9316
- [x] #9317
- [x] #9318
- [x] #9319
- [x] #9320
- [x] #9321
- [x] Clean up ElasticsearchExporter test refactoring
| 1.0 | [EPIC] Refactor Elasticsearch Exporter Tests - **Description**
The `elasticsearch-exporter` integration tests are currently quite convoluted. Historically, the `elasticsearch-exporter` tests used to depend on `zeebe-test` which was removed in https://github.com/camunda-cloud/zeebe/pull/8608. During the removal, some of the `zeebe-test` utilities ended up in the `elasticsearch-exporter` module where we also needed to add a lot of test scoped dependencies.
The main goals here were:
- Cover as much as possible via only unit tests. This gives us a faster feedback cycle when changing something - developers can focus on first fixing unit tests, which have smaller blast radius and faster execution, before even looking at integration tests.
- Narrow the scope of the integration tests as much as possible. This meant getting rid of the broker, workflow engine semantics, etc., and just testing the integration of the exporter instance with Elasticsearch.
In general, I wanted to keep the same coverage as before. I think the coverage is now higher, but that was not the original motivation.
**Breakdown**
- [x] #9162
- [x] #9315
- [x] #9316
- [x] #9317
- [x] #9318
- [x] #9319
- [x] #9320
- [x] #9321
- [x] Clean up ElasticsearchExporter test refactoring
| non_priority | refactor elasticsearch exporter tests description the elasticsearch exporter integration tests are currently quite convoluted historically the elasticsearch exporter tests used to depend on zeebe test which was removed in during the removal some of the zeebe test utilities ended up in the elasticsearch exporter module where we also needed to add a lot of test scoped dependencies the main goals here were cover as much as possible via only unit tests this gives us a faster feedback cycle when changing something developers can focus on first fixing unit tests which have smaller blast radius and faster execution before even looking at integration tests narrow the scope of the integration tests as much as possible this meant getting rid of the broker workflow engine semantics etc and just testing the integration of the exporter instance with elasticsearch in general i wanted to keep the same coverage as before i think the coverage is now higher but that was not the original motivation breakdown clean up elasticsearchexporter test refactoring | 0 |
454,382 | 13,099,803,298 | IssuesEvent | 2020-08-03 22:31:47 | googleapis/google-cloud-ruby | https://api.github.com/repos/googleapis/google-cloud-ruby | closed | spanner: add support for custom timeout and retry options - Google::Gax::CallOptions | api: spanner priority: p2 type: feature request | Currently, the client lib does not allow users to provide custom timeout and retry options that overrides the gapic default settings.
`Google::Gax::CallOptions` is supported by the methods in spanner_client:
https://github.com/googleapis/google-cloud-ruby/blob/1b0545aef072289a5d88a42054f9bed582423067/google-cloud-spanner/lib/google/cloud/spanner/v1/spanner_client.rb#L829
However, the methods in `service.rb` do not accept `Google::Gax::CallOptions`:
https://github.com/googleapis/google-cloud-ruby/blob/1b0545aef072289a5d88a42054f9bed582423067/google-cloud-spanner/lib/google/cloud/spanner/service.rb#L304-L307
We can implement the following two features to allow overrides:
- Method-level: update the methods in `service.rb` to support CallOptions.
- Client-level: accept a hash/map (mapping a method name to a CallOptions) when initializing the service and update `default_options_from_session` to merge the custom CallOptions of a method.
The precedence of order:
gapic defaults < client-level < method-level
@jiren Do you have any thoughts on this? Thanks. | 1.0 | spanner: add support for custom timeout and retry options - Google::Gax::CallOptions - Currently, the client lib does not allow users to provide custom timeout and retry options that overrides the gapic default settings.
`Google::Gax::CallOptions` is supported by the methods in spanner_client:
https://github.com/googleapis/google-cloud-ruby/blob/1b0545aef072289a5d88a42054f9bed582423067/google-cloud-spanner/lib/google/cloud/spanner/v1/spanner_client.rb#L829
However, the methods in `service.rb` do not accept `Google::Gax::CallOptions`:
https://github.com/googleapis/google-cloud-ruby/blob/1b0545aef072289a5d88a42054f9bed582423067/google-cloud-spanner/lib/google/cloud/spanner/service.rb#L304-L307
We can implement the following two features to allow overrides:
- Method-level: update the methods in `service.rb` to support CallOptions.
- Client-level: accept a hash/map (mapping a method name to a CallOptions) when initializing the service and update `default_options_from_session` to merge the custom CallOptions of a method.
The precedence of order:
gapic defaults < client-level < method-level
@jiren Do you have any thoughts on this? Thanks. | priority | spanner add support for custom timeout and retry options google gax calloptions currently the client lib does not allow users to provide custom timeout and retry options that overrides the gapic default settings google gax calloptions is supported by the methods in spanner client however the methods in service rb do not accept google gax calloptions we can implement the following two features to allow overrides method level update the methods in service rb to support calloptions client level accept a hash map mapping a method name to a calloptions when initializing the service and update default options from session to merge the custom calloptions of a method the precedence of order gapic defaults client level method level jiren do you have any thoughts on this thanks | 1 |
470,512 | 13,539,355,685 | IssuesEvent | 2020-09-16 13:22:23 | buddyboss/buddyboss-platform | https://api.github.com/repos/buddyboss/buddyboss-platform | closed | BP REST Media Endpoint does not support additional REST fields | bug priority: medium | **Describe the bug**
Fields added to the 'bp_media' object type via `register_rest_field()` are not present in REST response.
The `prepare_item_for_response` function does not call `add_additional_fields_to_object()`
**To Reproduce**
Steps to reproduce the behavior:
1. Register a REST field for bp_media
2. Send request to endpoint
3. View response
**Expected behavior**
The registered REST field to be present in the REST response.
| 1.0 | BP REST Media Endpoint does not support additional REST fields - **Describe the bug**
Fields added to the 'bp_media' object type via `register_rest_field()` are not present in REST response.
The `prepare_item_for_response` function does not call `add_additional_fields_to_object()`
**To Reproduce**
Steps to reproduce the behavior:
1. Register a REST field for bp_media
2. Send request to endpoint
3. View response
**Expected behavior**
The registered REST field to be present in the REST response.
| priority | bp rest media endpoint does not support additional rest fields describe the bug fields added to the bp media object type via register rest field are not present in rest response the prepare item for response function does not call add additional fields to object to reproduce steps to reproduce the behavior register a rest field for bp media send request to endpoint view response expected behavior the registered rest field to be present in the rest response | 1 |
62,924 | 15,384,322,996 | IssuesEvent | 2021-03-03 04:28:04 | jackaudio/jack2 | https://api.github.com/repos/jackaudio/jack2 | closed | JackOSX memory leak? | OSX build un/install | Hello,
I'm using JackOSX 0.92_b3 on macOS 10.13.6 and 10.14.
Each time I start jack, either from command line or through JackPilot, the memory footprint of `coreaudiod` increases by ~120MB, and then by another ~50MB when closing jack (`coreaudiod` usually takes <10MB of memory). This memory footprint stays that way until `coreaudiod` or the system itself is restarted; at some point I had `coreaudiod` occupy 8GB of memory after multiple starts/stops of jack.
I know that JackOSX is not actively maintained, so I'm not sure what's the way forward. After reading different posts from @sletz I arrived at the [jackosx sourceforge repository](https://sourceforge.net/p/jackosx/code/) hoping to be able to maybe tinker with the source; this however seems to be outdated (looks like version 0.89?), not reflecting the "newest" JackOSX (0.92_b3). I'd appreciate any help on this. | 1.0 | JackOSX memory leak? - Hello,
I'm using JackOSX 0.92_b3 on macOS 10.13.6 and 10.14.
Each time I start jack, either from command line or through JackPilot, the memory footprint of `coreaudiod` increases by ~120MB, and then by another ~50MB when closing jack (`coreaudiod` usually takes <10MB of memory). This memory footprint stays that way until `coreaudiod` or the system itself is restarted; at some point I had `coreaudiod` occupy 8GB of memory after multiple starts/stops of jack.
I know that JackOSX is not actively maintained, so I'm not sure what's the way forward. After reading different posts from @sletz I arrived at the [jackosx sourceforge repository](https://sourceforge.net/p/jackosx/code/) hoping to be able to maybe tinker with the source; this however seems to be outdated (looks like version 0.89?), not reflecting the "newest" JackOSX (0.92_b3). I'd appreciate any help on this. | non_priority | jackosx memory leak hello i m using jackosx on macos and each time i start jack either from command line or through jackpilot the memory footprint of coreaudiod increases by and then by another when closing jack coreaudiod usually takes of memory this memory footprint stays that way until coreaudiod or the system itself is restarted at some point i had coreaudiod occupy of memory after multiple starts stops of jack i know that jackosx is not actively maintained so i m not sure what s the way forward after reading different posts from sletz i arrived at the hoping to be able to maybe tinker with the source this however seems to be outdated looks like version not reflecting the newest jackosx i d appreciate any help on this | 0 |
491,235 | 14,147,466,169 | IssuesEvent | 2020-11-10 20:51:27 | m-kr/pagexpress | https://api.github.com/repos/m-kr/pagexpress | opened | Inner components should not have drag icon | bug high priority :star: :star: | Inner components have an active drag icon, which allows dragging the whole parent component.
Hide icon till reorder inner components feature implementation. | 1.0 | Inner components should not have drag icon - Inner components have an active drag icon, which allows dragging the whole parent component.
Hide icon till reorder inner components feature implementation. | priority | inner components should not have drag icon inner components have an active drag icon which allows dragging the whole parent component hide icon till reorder inner components feature implementation | 1 |
65,934 | 14,761,966,996 | IssuesEvent | 2021-01-09 01:11:40 | TIBCOSoftware/bw-sample-for-amazon-sns | https://api.github.com/repos/TIBCOSoftware/bw-sample-for-amazon-sns | opened | CVE-2020-36189 (Medium) detected in jackson-databind-2.6.6.jar | security vulnerability | ## CVE-2020-36189 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.6.6.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to vulnerable library: bw-sample-for-amazon-sns/SNSTCI/SNSImpl/lib/jackson-databind-2.6.6.jar,bw-sample-for-amazon-sns/SNSTestSuite/SNSImpl/lib/jackson-databind-2.6.6.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.6.6.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to com.newrelic.agent.deps.ch.qos.logback.core.db.DriverManagerConnectionSource.
<p>Publish Date: 2021-01-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36189>CVE-2020-36189</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>4.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: Required
- 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>Origin: <a href="https://github.com/FasterXML/jackson-databind/issues/2996">https://github.com/FasterXML/jackson-databind/issues/2996</a></p>
<p>Release Date: 2021-01-06</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.8</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.fasterxml.jackson.core","packageName":"jackson-databind","packageVersion":"2.6.6","isTransitiveDependency":false,"dependencyTree":"com.fasterxml.jackson.core:jackson-databind:2.6.6","isMinimumFixVersionAvailable":true,"minimumFixVersion":"com.fasterxml.jackson.core:jackson-databind:2.9.10.8"}],"vulnerabilityIdentifier":"CVE-2020-36189","vulnerabilityDetails":"FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to com.newrelic.agent.deps.ch.qos.logback.core.db.DriverManagerConnectionSource.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36189","cvss3Severity":"medium","cvss3Score":"4.2","cvss3Metrics":{"A":"Low","AC":"High","PR":"Low","S":"Unchanged","C":"Low","UI":"Required","AV":"Local","I":"Low"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-36189 (Medium) detected in jackson-databind-2.6.6.jar - ## CVE-2020-36189 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.6.6.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to vulnerable library: bw-sample-for-amazon-sns/SNSTCI/SNSImpl/lib/jackson-databind-2.6.6.jar,bw-sample-for-amazon-sns/SNSTestSuite/SNSImpl/lib/jackson-databind-2.6.6.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.6.6.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to com.newrelic.agent.deps.ch.qos.logback.core.db.DriverManagerConnectionSource.
<p>Publish Date: 2021-01-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36189>CVE-2020-36189</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>4.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: Required
- 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>Origin: <a href="https://github.com/FasterXML/jackson-databind/issues/2996">https://github.com/FasterXML/jackson-databind/issues/2996</a></p>
<p>Release Date: 2021-01-06</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.8</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.fasterxml.jackson.core","packageName":"jackson-databind","packageVersion":"2.6.6","isTransitiveDependency":false,"dependencyTree":"com.fasterxml.jackson.core:jackson-databind:2.6.6","isMinimumFixVersionAvailable":true,"minimumFixVersion":"com.fasterxml.jackson.core:jackson-databind:2.9.10.8"}],"vulnerabilityIdentifier":"CVE-2020-36189","vulnerabilityDetails":"FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to com.newrelic.agent.deps.ch.qos.logback.core.db.DriverManagerConnectionSource.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36189","cvss3Severity":"medium","cvss3Score":"4.2","cvss3Metrics":{"A":"Low","AC":"High","PR":"Low","S":"Unchanged","C":"Low","UI":"Required","AV":"Local","I":"Low"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in jackson databind jar cve medium severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to vulnerable library bw sample for amazon sns snstci snsimpl lib jackson databind jar bw sample for amazon sns snstestsuite snsimpl lib jackson databind jar dependency hierarchy x jackson databind jar vulnerable library vulnerability details fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to com newrelic agent deps ch qos logback core db drivermanagerconnectionsource publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required low user interaction required 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 origin a href release date fix resolution com fasterxml jackson core jackson databind check this box to open an automated fix pr isopenpronvulnerability false ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to com newrelic agent deps ch qos logback core db drivermanagerconnectionsource vulnerabilityurl | 0 |
443,593 | 30,924,415,609 | IssuesEvent | 2023-08-06 10:02:12 | cmannett85/arg_router | https://api.github.com/repos/cmannett85/arg_router | opened | Doxyfile version update removes semi-colons from comments | bug documentation | For some bizarre reason updating the Doxyfile project version, by updating the CMakeLists.txt project version, casuses all the semi-colons in the Doxyfile's comments to be removed. | 1.0 | Doxyfile version update removes semi-colons from comments - For some bizarre reason updating the Doxyfile project version, by updating the CMakeLists.txt project version, casuses all the semi-colons in the Doxyfile's comments to be removed. | non_priority | doxyfile version update removes semi colons from comments for some bizarre reason updating the doxyfile project version by updating the cmakelists txt project version casuses all the semi colons in the doxyfile s comments to be removed | 0 |
38,451 | 5,187,824,948 | IssuesEvent | 2017-01-20 17:59:43 | docker/swarm | https://api.github.com/repos/docker/swarm | closed | Since docker 1.13 released, should we take docker 1.13 into integration test scope? | area/tests | like the topic, WDYT?
ping @dongluochen @nishanttotla | 1.0 | Since docker 1.13 released, should we take docker 1.13 into integration test scope? - like the topic, WDYT?
ping @dongluochen @nishanttotla | non_priority | since docker released should we take docker into integration test scope like the topic wdyt ping dongluochen nishanttotla | 0 |
156,305 | 5,967,039,474 | IssuesEvent | 2017-05-30 15:11:41 | DistrictDataLabs/yellowbrick | https://api.github.com/repos/DistrictDataLabs/yellowbrick | reopened | ConfusionMatrix classes: one label must be specified in y true. | priority: high type: bug | When trying to passes class names to the ConfusionMatrix, I'm getting the following error:
```
/usr/local/lib/python3.6/site-packages/sklearn/metrics/classification.py:248: FutureWarning: elementwise comparison failed; returning scalar instead, but in the future will perform elementwise comparison
if np.all([l not in y_true for l in labels]):
Traceback (most recent call last):
File "rc.py", line 63, in <module>
viz.score(X_test, y_test)
File "/Users/benjamin/Repos/ddl/yellowbrick/yellowbrick/classifier/confusion_matrix.py", line 107, in score
y, y_pred, labels=self.classes_, sample_weight=sample_weight
File "/usr/local/lib/python3.6/site-packages/sklearn/metrics/classification.py", line 249, in confusion_matrix
raise ValueError("At least one label specified must be in y_true")
ValueError: At least one label specified must be in y_true
```
This is do to the fact that the y_true vector is label encoded (e.g. ones and zeros) but that the labels are strings, e.g. "occupied" and "unoccupied".
Here is the code to produce the error:
```python
df = pd.read_csv('examples/data/occupancy/occupancy.csv')
features = ["temperature", "relative humidity", "light", "C02", "humidity"]
target = "occupancy"
X = df[features]
y = df[target]
classes = ["unoccupied", "occupied"]
X_train, X_test, y_train, y_test = tts(X, y, test_size=0.2)
viz = ConfusionMatrix(MultinomialNB(), classes=classes)
viz.fit(X_train, y_train)
viz.score(X_test, y_test)
viz.poof()
```
Note that:
```
viz = ConfusionMatrix(MultinomialNB())
```
Does not raise an exception. | 1.0 | ConfusionMatrix classes: one label must be specified in y true. - When trying to passes class names to the ConfusionMatrix, I'm getting the following error:
```
/usr/local/lib/python3.6/site-packages/sklearn/metrics/classification.py:248: FutureWarning: elementwise comparison failed; returning scalar instead, but in the future will perform elementwise comparison
if np.all([l not in y_true for l in labels]):
Traceback (most recent call last):
File "rc.py", line 63, in <module>
viz.score(X_test, y_test)
File "/Users/benjamin/Repos/ddl/yellowbrick/yellowbrick/classifier/confusion_matrix.py", line 107, in score
y, y_pred, labels=self.classes_, sample_weight=sample_weight
File "/usr/local/lib/python3.6/site-packages/sklearn/metrics/classification.py", line 249, in confusion_matrix
raise ValueError("At least one label specified must be in y_true")
ValueError: At least one label specified must be in y_true
```
This is do to the fact that the y_true vector is label encoded (e.g. ones and zeros) but that the labels are strings, e.g. "occupied" and "unoccupied".
Here is the code to produce the error:
```python
df = pd.read_csv('examples/data/occupancy/occupancy.csv')
features = ["temperature", "relative humidity", "light", "C02", "humidity"]
target = "occupancy"
X = df[features]
y = df[target]
classes = ["unoccupied", "occupied"]
X_train, X_test, y_train, y_test = tts(X, y, test_size=0.2)
viz = ConfusionMatrix(MultinomialNB(), classes=classes)
viz.fit(X_train, y_train)
viz.score(X_test, y_test)
viz.poof()
```
Note that:
```
viz = ConfusionMatrix(MultinomialNB())
```
Does not raise an exception. | priority | confusionmatrix classes one label must be specified in y true when trying to passes class names to the confusionmatrix i m getting the following error usr local lib site packages sklearn metrics classification py futurewarning elementwise comparison failed returning scalar instead but in the future will perform elementwise comparison if np all traceback most recent call last file rc py line in viz score x test y test file users benjamin repos ddl yellowbrick yellowbrick classifier confusion matrix py line in score y y pred labels self classes sample weight sample weight file usr local lib site packages sklearn metrics classification py line in confusion matrix raise valueerror at least one label specified must be in y true valueerror at least one label specified must be in y true this is do to the fact that the y true vector is label encoded e g ones and zeros but that the labels are strings e g occupied and unoccupied here is the code to produce the error python df pd read csv examples data occupancy occupancy csv features target occupancy x df y df classes x train x test y train y test tts x y test size viz confusionmatrix multinomialnb classes classes viz fit x train y train viz score x test y test viz poof note that viz confusionmatrix multinomialnb does not raise an exception | 1 |
437,271 | 12,566,487,980 | IssuesEvent | 2020-06-08 11:18:27 | pingcap/tidb-operator | https://api.github.com/repos/pingcap/tidb-operator | closed | PD Join member params bug | priority:P1 status/help-wanted type/bug | ## Bug Report
operator v1.1.0-rc.4
Failed case in stability test. Here are the steps to recreate the bug.
1. create tidbcluster with 3pd
2. delete pd-0 data to trigger failover
3. pd-0 become unhealthy and pd-3 created, failover success
4. delete pd-0 pod to recreate the pd-0
5. pd-0 receive the following start params:
```sh
/pd-server --data-dir=/var/lib/pd --name=cluster1-pd-0 --peer-urls=http://0.0.0.0:2380 --advertise-peer-urls=http://cluster1-pd-0.cluster1-pd-peer.ns1.svc:2380 --client-urls=http://0.0.0.0:2379 --advertise-client-urls=http://cluster1-pd-0.cluster1-pd-peer.ns1.svc:2379 --config=/etc/pd/pd.toml --join=http://cluster1-pd-3.cluster1-pd-peer.ns1.svc:2379,http://cluster1-pd-1.cluster1-pd-peer.ns1.svc:2379,http://cluster1-pd-2.cluster1-pd-peer.ns1.svc:2379
```
6. clear the failureMembers to make pd-3 vanish.
7. pd-0 start failed due to pd-3 has been deleted.
Here is the error log in pd-0:
```sh
2020/05/19 12:07:52.765 grpclog.go:60: [warning] grpc: addrConn.createTransport failed to connect to {http://cluster1-pd-3.cluster1-pd-peer.ns1.svc:2379 0 <nil>}. Err :connection error: desc = "transport: Error while dialing dial tcp: lookup cluster1-pd-3.cluster1-pd-peer.ns1.svc on 10.233.0.10:53: no such host". Reconnecting...
{"level":"warn","ts":"2020-05-19T12:07:52.770Z","caller":"clientv3/retry_interceptor.go:60","msg":"retrying of unary invoker failed","target":"endpoint://client-28434540-8250-4e9e-91bb-d0ec8c31d710/cluster1-pd-3.cluster1-pd-peer.ns1.svc:2379","attempt":0,"error":"rpc error: code = Unavailable desc = etcdserver: unhealthy cluster"}
2020/05/19 12:07:52.771 grpclog.go:60: [warning] Failed to dial http://cluster1-pd-3.cluster1-pd-peer.ns1.svc:2379: context canceled; please retry.
[2020/05/19 12:07:52.771 +00:00] [FATAL] [main.go:91] ["join meet error"] [error="etcdserver: unhealthy cluster"] [stack="github.com/pingcap/log.Fatal\n\t/home/jenkins/agent/workspace/release_tidb_3.0/go/pkg/mod/github.com/pingcap/log@v0.0.0-20190715063458-479153f07ebd/global.go:59\nmain.main\n\t/home/jenkins/agent/workspace/release_tidb_3.0/go/src/github.com/pingcap/pd/cmd/pd-server/main.go:91\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:200"]
``` | 1.0 | PD Join member params bug - ## Bug Report
operator v1.1.0-rc.4
Failed case in stability test. Here are the steps to recreate the bug.
1. create tidbcluster with 3pd
2. delete pd-0 data to trigger failover
3. pd-0 become unhealthy and pd-3 created, failover success
4. delete pd-0 pod to recreate the pd-0
5. pd-0 receive the following start params:
```sh
/pd-server --data-dir=/var/lib/pd --name=cluster1-pd-0 --peer-urls=http://0.0.0.0:2380 --advertise-peer-urls=http://cluster1-pd-0.cluster1-pd-peer.ns1.svc:2380 --client-urls=http://0.0.0.0:2379 --advertise-client-urls=http://cluster1-pd-0.cluster1-pd-peer.ns1.svc:2379 --config=/etc/pd/pd.toml --join=http://cluster1-pd-3.cluster1-pd-peer.ns1.svc:2379,http://cluster1-pd-1.cluster1-pd-peer.ns1.svc:2379,http://cluster1-pd-2.cluster1-pd-peer.ns1.svc:2379
```
6. clear the failureMembers to make pd-3 vanish.
7. pd-0 start failed due to pd-3 has been deleted.
Here is the error log in pd-0:
```sh
2020/05/19 12:07:52.765 grpclog.go:60: [warning] grpc: addrConn.createTransport failed to connect to {http://cluster1-pd-3.cluster1-pd-peer.ns1.svc:2379 0 <nil>}. Err :connection error: desc = "transport: Error while dialing dial tcp: lookup cluster1-pd-3.cluster1-pd-peer.ns1.svc on 10.233.0.10:53: no such host". Reconnecting...
{"level":"warn","ts":"2020-05-19T12:07:52.770Z","caller":"clientv3/retry_interceptor.go:60","msg":"retrying of unary invoker failed","target":"endpoint://client-28434540-8250-4e9e-91bb-d0ec8c31d710/cluster1-pd-3.cluster1-pd-peer.ns1.svc:2379","attempt":0,"error":"rpc error: code = Unavailable desc = etcdserver: unhealthy cluster"}
2020/05/19 12:07:52.771 grpclog.go:60: [warning] Failed to dial http://cluster1-pd-3.cluster1-pd-peer.ns1.svc:2379: context canceled; please retry.
[2020/05/19 12:07:52.771 +00:00] [FATAL] [main.go:91] ["join meet error"] [error="etcdserver: unhealthy cluster"] [stack="github.com/pingcap/log.Fatal\n\t/home/jenkins/agent/workspace/release_tidb_3.0/go/pkg/mod/github.com/pingcap/log@v0.0.0-20190715063458-479153f07ebd/global.go:59\nmain.main\n\t/home/jenkins/agent/workspace/release_tidb_3.0/go/src/github.com/pingcap/pd/cmd/pd-server/main.go:91\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:200"]
``` | priority | pd join member params bug bug report operator rc failed case in stability test here are the steps to recreate the bug create tidbcluster with delete pd data to trigger failover pd become unhealthy and pd created failover success delete pd pod to recreate the pd pd receive the following start params sh pd server data dir var lib pd name pd peer urls advertise peer urls client urls advertise client urls config etc pd pd toml join clear the failuremembers to make pd vanish pd start failed due to pd has been deleted here is the error log in pd sh grpclog go grpc addrconn createtransport failed to connect to err connection error desc transport error while dialing dial tcp lookup pd pd peer svc on no such host reconnecting level warn ts caller retry interceptor go msg retrying of unary invoker failed target endpoint client pd pd peer svc attempt error rpc error code unavailable desc etcdserver unhealthy cluster grpclog go failed to dial context canceled please retry | 1 |
321,459 | 27,531,667,350 | IssuesEvent | 2023-03-06 22:40:41 | roc-streaming/roc-toolkit | https://api.github.com/repos/roc-streaming/roc-toolkit | opened | netio test fails on Android emulator | tests portability | ```
+ python3 scripts/scons_helpers/run-with-timeout.py 300 adb shell LD_LIBRARY_PATH=/data/local/tmp/lib '/data/local/tmp/roc-test-netio -v'
WARNING | /etc/localtime does not point to zoneinfo-compatible timezone name
scripts/ci_checks/android/macos.sh: line 72: 58203 Terminated: 15 python3 scripts/scons_helpers/run-with-timeout.py 300 adb shell "LD_LIBRARY_PATH=${target_prefix}/lib" "${target_prefix}/${filename} -v" > "${logfile}" 2> /dev/null
+ error=143
+ tail -n 800 tests/x86_64-linux-android29/roc-test-netio.log
TEST(udp_ports, add_remove_add) - 557 ms
TEST(udp_ports, add_remove) - 343 ms
TEST(udp_ports, add_multicast_receiver_error) - 33 ms
TEST(udp_ports, add_multicast_receiver)
src/tests/roc_netio/test_udp_ports.cpp:203: error: Failure in TEST(udp_ports, add_multicast_receiver)
CHECK(add_udp_receiver(net_loop, rx_config, queue)) failed
- 18 ms
TEST(udp_ports, add_broadcast_sender)+ exit 143
```
https://github.com/roc-streaming/roc-toolkit/actions/runs/4348480297/jobs/7597064804 | 1.0 | netio test fails on Android emulator - ```
+ python3 scripts/scons_helpers/run-with-timeout.py 300 adb shell LD_LIBRARY_PATH=/data/local/tmp/lib '/data/local/tmp/roc-test-netio -v'
WARNING | /etc/localtime does not point to zoneinfo-compatible timezone name
scripts/ci_checks/android/macos.sh: line 72: 58203 Terminated: 15 python3 scripts/scons_helpers/run-with-timeout.py 300 adb shell "LD_LIBRARY_PATH=${target_prefix}/lib" "${target_prefix}/${filename} -v" > "${logfile}" 2> /dev/null
+ error=143
+ tail -n 800 tests/x86_64-linux-android29/roc-test-netio.log
TEST(udp_ports, add_remove_add) - 557 ms
TEST(udp_ports, add_remove) - 343 ms
TEST(udp_ports, add_multicast_receiver_error) - 33 ms
TEST(udp_ports, add_multicast_receiver)
src/tests/roc_netio/test_udp_ports.cpp:203: error: Failure in TEST(udp_ports, add_multicast_receiver)
CHECK(add_udp_receiver(net_loop, rx_config, queue)) failed
- 18 ms
TEST(udp_ports, add_broadcast_sender)+ exit 143
```
https://github.com/roc-streaming/roc-toolkit/actions/runs/4348480297/jobs/7597064804 | non_priority | netio test fails on android emulator scripts scons helpers run with timeout py adb shell ld library path data local tmp lib data local tmp roc test netio v warning etc localtime does not point to zoneinfo compatible timezone name scripts ci checks android macos sh line terminated scripts scons helpers run with timeout py adb shell ld library path target prefix lib target prefix filename v logfile dev null error tail n tests linux roc test netio log test udp ports add remove add ms test udp ports add remove ms test udp ports add multicast receiver error ms test udp ports add multicast receiver src tests roc netio test udp ports cpp error failure in test udp ports add multicast receiver check add udp receiver net loop rx config queue failed ms test udp ports add broadcast sender exit | 0 |
408,596 | 27,697,773,385 | IssuesEvent | 2023-03-14 04:38:42 | TBD54566975/ssi-service | https://api.github.com/repos/TBD54566975/ssi-service | closed | Publish OpenAPI Doc to GitHub Pages | documentation | 1. Create a gh-pages branch
2. Create an action on merge to main to run `mage spec` and generate the latest OpenAPI docs
3. Move files to the correct place, to surface the docs on gh pages | 1.0 | Publish OpenAPI Doc to GitHub Pages - 1. Create a gh-pages branch
2. Create an action on merge to main to run `mage spec` and generate the latest OpenAPI docs
3. Move files to the correct place, to surface the docs on gh pages | non_priority | publish openapi doc to github pages create a gh pages branch create an action on merge to main to run mage spec and generate the latest openapi docs move files to the correct place to surface the docs on gh pages | 0 |
758,159 | 26,544,911,313 | IssuesEvent | 2023-01-19 22:52:16 | obs-nebula/check-traces | https://api.github.com/repos/obs-nebula/check-traces | closed | Understand how to use the OTEL_SDK_DISABLED env var | Type: Research Priority: Low | https://github.com/open-telemetry/opentelemetry-js/tree/main/experimental/packages/opentelemetry-sdk-node#disable-the-sdk-from-the-environment
This is not disabling using this way:
( I don't know if that works for sdk-trace-node package )
```console
➜ check-traces git:(remove-declared-deps) set OTEL_SDK_DISABLED true
➜ check-traces git:(remove-declared-deps) npm start
> check-traces@1.0.0 start
> NODE_OPTIONS='--require ./tracing.js' node .
Example app listening on port 8080
^C⏎
➜ check-traces git:(remove-declared-deps) curl -s http://localhost:14269/metrics | grep "check-traces"
jaeger_spans_received_total{debug="false",format="proto",svc="check-traces",transport="grpc"} 19
jaeger_spans_saved_by_svc_total{debug="false",result="ok",svc="check-traces"} 19
jaeger_traces_received_total{debug="false",format="proto",sampler_type="unknown",svc="check-traces",transport="grpc"} 5
jaeger_traces_saved_by_svc_total{debug="false",result="ok",sampler_type="unknown",svc="check-traces"} 5
```
| 1.0 | Understand how to use the OTEL_SDK_DISABLED env var - https://github.com/open-telemetry/opentelemetry-js/tree/main/experimental/packages/opentelemetry-sdk-node#disable-the-sdk-from-the-environment
This is not disabling using this way:
( I don't know if that works for sdk-trace-node package )
```console
➜ check-traces git:(remove-declared-deps) set OTEL_SDK_DISABLED true
➜ check-traces git:(remove-declared-deps) npm start
> check-traces@1.0.0 start
> NODE_OPTIONS='--require ./tracing.js' node .
Example app listening on port 8080
^C⏎
➜ check-traces git:(remove-declared-deps) curl -s http://localhost:14269/metrics | grep "check-traces"
jaeger_spans_received_total{debug="false",format="proto",svc="check-traces",transport="grpc"} 19
jaeger_spans_saved_by_svc_total{debug="false",result="ok",svc="check-traces"} 19
jaeger_traces_received_total{debug="false",format="proto",sampler_type="unknown",svc="check-traces",transport="grpc"} 5
jaeger_traces_saved_by_svc_total{debug="false",result="ok",sampler_type="unknown",svc="check-traces"} 5
```
| priority | understand how to use the otel sdk disabled env var this is not disabling using this way i don t know if that works for sdk trace node package console ➜ check traces git remove declared deps set otel sdk disabled true ➜ check traces git remove declared deps npm start check traces start node options require tracing js node example app listening on port c⏎ ➜ check traces git remove declared deps curl s grep check traces jaeger spans received total debug false format proto svc check traces transport grpc jaeger spans saved by svc total debug false result ok svc check traces jaeger traces received total debug false format proto sampler type unknown svc check traces transport grpc jaeger traces saved by svc total debug false result ok sampler type unknown svc check traces | 1 |
8,355 | 3,725,467,868 | IssuesEvent | 2016-03-05 01:36:01 | phetsims/rutherford-scattering | https://api.github.com/repos/phetsims/rutherford-scattering | opened | significant duplication in ScreenView subtypes | dev:code-review | Related to #30 (code review).
There's significant duplication in RutherfordAtomScreenView and PlumPuddingScreenView. I ran out of time today to investigate further and make recommendations. Assign to myself to look at on 3/7/16. | 1.0 | significant duplication in ScreenView subtypes - Related to #30 (code review).
There's significant duplication in RutherfordAtomScreenView and PlumPuddingScreenView. I ran out of time today to investigate further and make recommendations. Assign to myself to look at on 3/7/16. | non_priority | significant duplication in screenview subtypes related to code review there s significant duplication in rutherfordatomscreenview and plumpuddingscreenview i ran out of time today to investigate further and make recommendations assign to myself to look at on | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.