Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 5 112 | repo_url stringlengths 34 141 | action stringclasses 3 values | title stringlengths 1 844 | labels stringlengths 4 721 | body stringlengths 1 261k | index stringclasses 12 values | text_combine stringlengths 96 261k | label stringclasses 2 values | text stringlengths 96 248k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
59,005 | 16,997,804,754 | IssuesEvent | 2021-07-01 08:45:55 | vector-im/element-web | https://api.github.com/repos/vector-im/element-web | opened | RoomDirectory: can't access property "trim", this.state.filterString is null | T-Defect | ### Description
```
can't access property "trim", this.state.filterString is null
RoomDirectory.tsx:413
```
### Steps to reproduce
0. Be logged into Element Web.
1. Open "Explore rooms".
2. Type anything into the search. (This search term must not have any results on the server you switch to in step 3!)
3. Change the server in the Server dropdown.
4. Click the red X in the search term input.
Describe how what happens differs from what you expected.
A JavaScript error occurs and the "Explore rooms" modal closes itself.
<!-- Please send us logs for your bug report. They're very important for bugs
which are hard to reproduce. To do this, create this issue then go to your
account settings and click 'Submit Debug Logs' from the Help & About tab -->
Logs being sent: yes
<!-- Include screenshots if possible: you can drag and drop images below. -->
### Version information
<!-- IMPORTANT: please answer the following questions, to help us narrow down the problem -->
- **Platform**: web
For the web app:
- **Browser**: Mozilla Firefox Dev Edition 90.0b4
- **OS**: Manjaro Linux (Arch repo)
- **URL**: staging.element.io 1.7.32-rc.1
| 1.0 | RoomDirectory: can't access property "trim", this.state.filterString is null - ### Description
```
can't access property "trim", this.state.filterString is null
RoomDirectory.tsx:413
```
### Steps to reproduce
0. Be logged into Element Web.
1. Open "Explore rooms".
2. Type anything into the search. (This search term must not have any results on the server you switch to in step 3!)
3. Change the server in the Server dropdown.
4. Click the red X in the search term input.
Describe how what happens differs from what you expected.
A JavaScript error occurs and the "Explore rooms" modal closes itself.
<!-- Please send us logs for your bug report. They're very important for bugs
which are hard to reproduce. To do this, create this issue then go to your
account settings and click 'Submit Debug Logs' from the Help & About tab -->
Logs being sent: yes
<!-- Include screenshots if possible: you can drag and drop images below. -->
### Version information
<!-- IMPORTANT: please answer the following questions, to help us narrow down the problem -->
- **Platform**: web
For the web app:
- **Browser**: Mozilla Firefox Dev Edition 90.0b4
- **OS**: Manjaro Linux (Arch repo)
- **URL**: staging.element.io 1.7.32-rc.1
| non_priority | roomdirectory can t access property trim this state filterstring is null description can t access property trim this state filterstring is null roomdirectory tsx steps to reproduce be logged into element web open explore rooms type anything into the search this search term must not have any results on the server you switch to in step change the server in the server dropdown click the red x in the search term input describe how what happens differs from what you expected a javascript error occurs and the explore rooms modal closes itself please send us logs for your bug report they re very important for bugs which are hard to reproduce to do this create this issue then go to your account settings and click submit debug logs from the help about tab logs being sent yes version information platform web for the web app browser mozilla firefox dev edition os manjaro linux arch repo url staging element io rc | 0 |
261,441 | 27,809,769,785 | IssuesEvent | 2023-03-18 01:40:53 | madhans23/linux-4.1.15 | https://api.github.com/repos/madhans23/linux-4.1.15 | closed | CVE-2019-14821 (High) detected in linux-stable-rtv4.1.33 - autoclosed | Mend: dependency security vulnerability | ## CVE-2019-14821 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/madhans23/linux-4.1.15/commit/f9d19044b0eef1965f9bc412d7d9e579b74ec968">f9d19044b0eef1965f9bc412d7d9e579b74ec968</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (3)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/virt/kvm/coalesced_mmio.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/virt/kvm/coalesced_mmio.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/virt/kvm/coalesced_mmio.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>
An out-of-bounds access issue was found in the Linux kernel, all versions through 5.3, in the way Linux kernel's KVM hypervisor implements the Coalesced MMIO write operation. It operates on an MMIO ring buffer 'struct kvm_coalesced_mmio' object, wherein write indices 'ring->first' and 'ring->last' value could be supplied by a host user-space process. An unprivileged host user or process with access to '/dev/kvm' device could use this flaw to crash the host kernel, resulting in a denial of service or potentially escalating privileges on the system.
<p>Publish Date: 2019-09-19
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-14821>CVE-2019-14821</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>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14821">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14821</a></p>
<p>Release Date: 2019-09-19</p>
<p>Fix Resolution: v5.4-rc1</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-2019-14821 (High) detected in linux-stable-rtv4.1.33 - autoclosed - ## CVE-2019-14821 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/madhans23/linux-4.1.15/commit/f9d19044b0eef1965f9bc412d7d9e579b74ec968">f9d19044b0eef1965f9bc412d7d9e579b74ec968</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (3)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/virt/kvm/coalesced_mmio.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/virt/kvm/coalesced_mmio.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/virt/kvm/coalesced_mmio.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>
An out-of-bounds access issue was found in the Linux kernel, all versions through 5.3, in the way Linux kernel's KVM hypervisor implements the Coalesced MMIO write operation. It operates on an MMIO ring buffer 'struct kvm_coalesced_mmio' object, wherein write indices 'ring->first' and 'ring->last' value could be supplied by a host user-space process. An unprivileged host user or process with access to '/dev/kvm' device could use this flaw to crash the host kernel, resulting in a denial of service or potentially escalating privileges on the system.
<p>Publish Date: 2019-09-19
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-14821>CVE-2019-14821</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>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14821">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14821</a></p>
<p>Release Date: 2019-09-19</p>
<p>Fix Resolution: v5.4-rc1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in linux stable autoclosed cve high severity vulnerability vulnerable library linux stable julia cartwright s fork of linux stable rt git library home page a href found in head commit a href found in base branch master vulnerable source files virt kvm coalesced mmio c virt kvm coalesced mmio c virt kvm coalesced mmio c vulnerability details an out of bounds access issue was found in the linux kernel all versions through in the way linux kernel s kvm hypervisor implements the coalesced mmio write operation it operates on an mmio ring buffer struct kvm coalesced mmio object wherein write indices ring first and ring last value could be supplied by a host user space process an unprivileged host user or process with access to dev kvm device could use this flaw to crash the host kernel resulting in a denial of service or potentially escalating privileges on the system publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
87,954 | 11,013,274,616 | IssuesEvent | 2019-12-04 20:06:51 | cds-snc/notification-api | https://api.github.com/repos/cds-snc/notification-api | closed | Draw Sender task flows | Design | **Story**
When we add navigate and elements to Notify we need them to be grouped based on what a sender needs to accomplish so that they can easily find the things they need to complete their tasks.
**What?**
- by mindset, create tasks flows for how they would interact with the system
**Why?**
- We can haver a cohesive user experience that fits what tasks a particular sender needs to do. | 1.0 | Draw Sender task flows - **Story**
When we add navigate and elements to Notify we need them to be grouped based on what a sender needs to accomplish so that they can easily find the things they need to complete their tasks.
**What?**
- by mindset, create tasks flows for how they would interact with the system
**Why?**
- We can haver a cohesive user experience that fits what tasks a particular sender needs to do. | non_priority | draw sender task flows story when we add navigate and elements to notify we need them to be grouped based on what a sender needs to accomplish so that they can easily find the things they need to complete their tasks what by mindset create tasks flows for how they would interact with the system why we can haver a cohesive user experience that fits what tasks a particular sender needs to do | 0 |
2,227 | 4,365,350,422 | IssuesEvent | 2016-08-03 10:29:06 | jhipster/generator-jhipster | https://api.github.com/repos/jhipster/generator-jhipster | closed | Add a Zuul filter to cache HTTP requests with Memcached | feature request microservice | This is a follow-up to #3308
Before this ticket is done, we need to:
- Refactor the current Zuul filters (which are not totally consistent)
- Add a specific documentation section for Zuul filters (the rate limiting filter is not even documented)
This filter would allow to cache HTTP requests at the Zuul level:
- It would cache REST requests to microservices: GET/PUT/POST/DELETE requests will update the cache.
- That cache would use Memcached, so it could be hosted easily in the cloud
- There would be a `memcached.yml` Docker configuration, using the official Memcached image
- It would use the [Folsom client](https://github.com/spotify/folsom)
- When HTTP caching is enabled on the gateway, you have the option to generate a cache configuration per entity -> they would be generated when the entity is generated. That means some specific Java code generated on the gateway, which isn't the case today. This is necessary as you want fine-grained control over the cache.
- Some study must be done to see how Memcached failures should be handled. There should be some kind of circuit breaker for Memcached, so that if it fails we quickly stop using it. | 1.0 | Add a Zuul filter to cache HTTP requests with Memcached - This is a follow-up to #3308
Before this ticket is done, we need to:
- Refactor the current Zuul filters (which are not totally consistent)
- Add a specific documentation section for Zuul filters (the rate limiting filter is not even documented)
This filter would allow to cache HTTP requests at the Zuul level:
- It would cache REST requests to microservices: GET/PUT/POST/DELETE requests will update the cache.
- That cache would use Memcached, so it could be hosted easily in the cloud
- There would be a `memcached.yml` Docker configuration, using the official Memcached image
- It would use the [Folsom client](https://github.com/spotify/folsom)
- When HTTP caching is enabled on the gateway, you have the option to generate a cache configuration per entity -> they would be generated when the entity is generated. That means some specific Java code generated on the gateway, which isn't the case today. This is necessary as you want fine-grained control over the cache.
- Some study must be done to see how Memcached failures should be handled. There should be some kind of circuit breaker for Memcached, so that if it fails we quickly stop using it. | non_priority | add a zuul filter to cache http requests with memcached this is a follow up to before this ticket is done we need to refactor the current zuul filters which are not totally consistent add a specific documentation section for zuul filters the rate limiting filter is not even documented this filter would allow to cache http requests at the zuul level it would cache rest requests to microservices get put post delete requests will update the cache that cache would use memcached so it could be hosted easily in the cloud there would be a memcached yml docker configuration using the official memcached image it would use the when http caching is enabled on the gateway you have the option to generate a cache configuration per entity they would be generated when the entity is generated that means some specific java code generated on the gateway which isn t the case today this is necessary as you want fine grained control over the cache some study must be done to see how memcached failures should be handled there should be some kind of circuit breaker for memcached so that if it fails we quickly stop using it | 0 |
47,845 | 13,258,244,273 | IssuesEvent | 2020-08-20 15:07:49 | Mohib-hub/jwala | https://api.github.com/repos/Mohib-hub/jwala | opened | CVE-2019-10202 (High) detected in jackson-mapper-asl-1.4.2.jar | security vulnerability | ## CVE-2019-10202 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-mapper-asl-1.4.2.jar</b></p></summary>
<p>Data Mapper package is a high-performance data binding package
built on Jackson JSON processor</p>
<p>Path to vulnerable library: _depth_0/jwala/jwala-services/src/test/resources/get-resource-mime-type-test-files/war/WEB-INF/lib/jackson-mapper-asl-1.4.2.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-mapper-asl-1.4.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mohib-hub/jwala/commit/d8fb926264467022c2579c0b8ae59ef0b5ca5b87">d8fb926264467022c2579c0b8ae59ef0b5ca5b87</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A series of deserialization vulnerabilities have been discovered in Codehaus 1.9.x implemented in EAP 7. This CVE fixes CVE-2017-17485, CVE-2017-7525, CVE-2017-15095, CVE-2018-5968, CVE-2018-7489, CVE-2018-1000873, CVE-2019-12086 reported for FasterXML jackson-databind by implementing a whitelist approach that will mitigate these vulnerabilities and future ones alike.
<p>Publish Date: 2019-10-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10202>CVE-2019-10202</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://access.redhat.com/errata/RHSA-2019:2938">https://access.redhat.com/errata/RHSA-2019:2938</a></p>
<p>Release Date: 2019-10-01</p>
<p>Fix Resolution: JBoss Enterprise Application Platform - 7.2.4;com.fasterxml.jackson.core:jackson-databind:2.9.9</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.codehaus.jackson","packageName":"jackson-mapper-asl","packageVersion":"1.4.2","isTransitiveDependency":false,"dependencyTree":"org.codehaus.jackson:jackson-mapper-asl:1.4.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"JBoss Enterprise Application Platform - 7.2.4;com.fasterxml.jackson.core:jackson-databind:2.9.9"}],"vulnerabilityIdentifier":"CVE-2019-10202","vulnerabilityDetails":"A series of deserialization vulnerabilities have been discovered in Codehaus 1.9.x implemented in EAP 7. This CVE fixes CVE-2017-17485, CVE-2017-7525, CVE-2017-15095, CVE-2018-5968, CVE-2018-7489, CVE-2018-1000873, CVE-2019-12086 reported for FasterXML jackson-databind by implementing a whitelist approach that will mitigate these vulnerabilities and future ones alike.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10202","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2019-10202 (High) detected in jackson-mapper-asl-1.4.2.jar - ## CVE-2019-10202 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-mapper-asl-1.4.2.jar</b></p></summary>
<p>Data Mapper package is a high-performance data binding package
built on Jackson JSON processor</p>
<p>Path to vulnerable library: _depth_0/jwala/jwala-services/src/test/resources/get-resource-mime-type-test-files/war/WEB-INF/lib/jackson-mapper-asl-1.4.2.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-mapper-asl-1.4.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mohib-hub/jwala/commit/d8fb926264467022c2579c0b8ae59ef0b5ca5b87">d8fb926264467022c2579c0b8ae59ef0b5ca5b87</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A series of deserialization vulnerabilities have been discovered in Codehaus 1.9.x implemented in EAP 7. This CVE fixes CVE-2017-17485, CVE-2017-7525, CVE-2017-15095, CVE-2018-5968, CVE-2018-7489, CVE-2018-1000873, CVE-2019-12086 reported for FasterXML jackson-databind by implementing a whitelist approach that will mitigate these vulnerabilities and future ones alike.
<p>Publish Date: 2019-10-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10202>CVE-2019-10202</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://access.redhat.com/errata/RHSA-2019:2938">https://access.redhat.com/errata/RHSA-2019:2938</a></p>
<p>Release Date: 2019-10-01</p>
<p>Fix Resolution: JBoss Enterprise Application Platform - 7.2.4;com.fasterxml.jackson.core:jackson-databind:2.9.9</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.codehaus.jackson","packageName":"jackson-mapper-asl","packageVersion":"1.4.2","isTransitiveDependency":false,"dependencyTree":"org.codehaus.jackson:jackson-mapper-asl:1.4.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"JBoss Enterprise Application Platform - 7.2.4;com.fasterxml.jackson.core:jackson-databind:2.9.9"}],"vulnerabilityIdentifier":"CVE-2019-10202","vulnerabilityDetails":"A series of deserialization vulnerabilities have been discovered in Codehaus 1.9.x implemented in EAP 7. This CVE fixes CVE-2017-17485, CVE-2017-7525, CVE-2017-15095, CVE-2018-5968, CVE-2018-7489, CVE-2018-1000873, CVE-2019-12086 reported for FasterXML jackson-databind by implementing a whitelist approach that will mitigate these vulnerabilities and future ones alike.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10202","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in jackson mapper asl jar cve high severity vulnerability vulnerable library jackson mapper asl jar data mapper package is a high performance data binding package built on jackson json processor path to vulnerable library depth jwala jwala services src test resources get resource mime type test files war web inf lib jackson mapper asl jar dependency hierarchy x jackson mapper asl jar vulnerable library found in head commit a href vulnerability details a series of deserialization vulnerabilities have been discovered in codehaus x implemented in eap this cve fixes cve cve cve cve cve cve cve reported for fasterxml jackson databind by implementing a whitelist approach that will mitigate these vulnerabilities and future ones alike publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jboss enterprise application platform com fasterxml jackson core jackson databind isopenpronvulnerability true ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails a series of deserialization vulnerabilities have been discovered in codehaus x implemented in eap this cve fixes cve cve cve cve cve cve cve reported for fasterxml jackson databind by implementing a whitelist approach that will mitigate these vulnerabilities and future ones alike vulnerabilityurl | 0 |
179,214 | 30,196,281,073 | IssuesEvent | 2023-07-04 21:36:24 | PoliNetworkOrg/Rankings | https://api.github.com/repos/PoliNetworkOrg/Rankings | closed | [STYLE] Utilizzare il nome originale della fase nel breadcrumb | enhancement design | 
Nel breadcrumb possiamo mettere la versione del nome con gli spazi | 1.0 | [STYLE] Utilizzare il nome originale della fase nel breadcrumb - 
Nel breadcrumb possiamo mettere la versione del nome con gli spazi | non_priority | utilizzare il nome originale della fase nel breadcrumb nel breadcrumb possiamo mettere la versione del nome con gli spazi | 0 |
76,560 | 7,539,832,492 | IssuesEvent | 2018-04-17 02:48:46 | capitalone/cloud-custodian | https://api.github.com/repos/capitalone/cloud-custodian | opened | Investigate Azure Dev Test Labs for Functional Tests | area/test-infra cloud/azure | Azure Dev Test labs seems like it may provide useful benefits in automating the provisioning and cleanup of resources for recording test cassettes or live functional tests.
https://docs.microsoft.com/en-us/azure/devtest-lab/devtest-lab-overview
You'd define ARM templates to represent the test environments, but it helps with cleanly provisioning the environment for a test run and cleaning up afterward to control costs. It also knows how to read templates directly from source control and integrate with CI/CD pipelines.
My main priority right now is in the easiest way to ensure developers can reliably deploy environments to reproduce/record all our VCR tests (from their desks, not in automated build pipelines). This may be a cleaner approach than manually coding resource provisioning into tests. | 1.0 | Investigate Azure Dev Test Labs for Functional Tests - Azure Dev Test labs seems like it may provide useful benefits in automating the provisioning and cleanup of resources for recording test cassettes or live functional tests.
https://docs.microsoft.com/en-us/azure/devtest-lab/devtest-lab-overview
You'd define ARM templates to represent the test environments, but it helps with cleanly provisioning the environment for a test run and cleaning up afterward to control costs. It also knows how to read templates directly from source control and integrate with CI/CD pipelines.
My main priority right now is in the easiest way to ensure developers can reliably deploy environments to reproduce/record all our VCR tests (from their desks, not in automated build pipelines). This may be a cleaner approach than manually coding resource provisioning into tests. | non_priority | investigate azure dev test labs for functional tests azure dev test labs seems like it may provide useful benefits in automating the provisioning and cleanup of resources for recording test cassettes or live functional tests you d define arm templates to represent the test environments but it helps with cleanly provisioning the environment for a test run and cleaning up afterward to control costs it also knows how to read templates directly from source control and integrate with ci cd pipelines my main priority right now is in the easiest way to ensure developers can reliably deploy environments to reproduce record all our vcr tests from their desks not in automated build pipelines this may be a cleaner approach than manually coding resource provisioning into tests | 0 |
442,314 | 30,828,667,299 | IssuesEvent | 2023-08-01 22:36:48 | Agoric/agoric-sdk | https://api.github.com/repos/Agoric/agoric-sdk | opened | document x/vibc module | documentation agoric-cosmos | ## What is the Problem Being Solved?
The [cosmos/x/vibc](https://github.com/Agoric/agoric-sdk/tree/master/golang/cosmos/x/vibc) module lacks any sort of README.
## Description of the Design
much like [cosmos/x/vstorage/README.md](https://github.com/Agoric/agoric-sdk/blob/master/golang/cosmos/x/vstorage/README.md)
[cosmos/x/lien/spec/](https://github.com/Agoric/agoric-sdk/tree/master/golang/cosmos/x/lien/spec) is another possible source of inspiration.
_assigning to @gibson042 as discussed_
cc @michaelfig @JimLarson
| 1.0 | document x/vibc module - ## What is the Problem Being Solved?
The [cosmos/x/vibc](https://github.com/Agoric/agoric-sdk/tree/master/golang/cosmos/x/vibc) module lacks any sort of README.
## Description of the Design
much like [cosmos/x/vstorage/README.md](https://github.com/Agoric/agoric-sdk/blob/master/golang/cosmos/x/vstorage/README.md)
[cosmos/x/lien/spec/](https://github.com/Agoric/agoric-sdk/tree/master/golang/cosmos/x/lien/spec) is another possible source of inspiration.
_assigning to @gibson042 as discussed_
cc @michaelfig @JimLarson
| non_priority | document x vibc module what is the problem being solved the module lacks any sort of readme description of the design much like is another possible source of inspiration assigning to as discussed cc michaelfig jimlarson | 0 |
201,322 | 15,189,322,707 | IssuesEvent | 2021-02-15 16:15:20 | tendermint/tendermint | https://api.github.com/repos/tendermint/tendermint | opened | Allow MemoryConnection Buffer to be Configurable | C:p2p T:test good first issue | <!-- < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < ☺
v ✰ Thanks for opening an issue! ✰
v Before smashing the submit button please review the template.
v Word of caution: poorly thought-out proposals may be rejected
v without deliberation
☺ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -->
## Summary
ref: https://github.com/tendermint/tendermint/pull/5969#discussion_r573958714
Allow the ability to change the channel buffer sizes of `MemoryConnection` transport.
____
#### For Admin Use
- [ ] Not duplicate issue
- [ ] Appropriate labels applied
- [ ] Appropriate contributors tagged
- [ ] Contributor assigned/self-assigned
| 1.0 | Allow MemoryConnection Buffer to be Configurable - <!-- < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < ☺
v ✰ Thanks for opening an issue! ✰
v Before smashing the submit button please review the template.
v Word of caution: poorly thought-out proposals may be rejected
v without deliberation
☺ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -->
## Summary
ref: https://github.com/tendermint/tendermint/pull/5969#discussion_r573958714
Allow the ability to change the channel buffer sizes of `MemoryConnection` transport.
____
#### For Admin Use
- [ ] Not duplicate issue
- [ ] Appropriate labels applied
- [ ] Appropriate contributors tagged
- [ ] Contributor assigned/self-assigned
| non_priority | allow memoryconnection buffer to be configurable ☺ v ✰ thanks for opening an issue ✰ v before smashing the submit button please review the template v word of caution poorly thought out proposals may be rejected v without deliberation ☺ summary ref allow the ability to change the channel buffer sizes of memoryconnection transport for admin use not duplicate issue appropriate labels applied appropriate contributors tagged contributor assigned self assigned | 0 |
1,464 | 3,778,311,782 | IssuesEvent | 2016-03-17 23:44:35 | ViviTurtle/Speed-Rider | https://api.github.com/repos/ViviTurtle/Speed-Rider | closed | Low Level Design | Requirement | ~~- 5 page minimum~~
~~- break down component design information into details.~~
~~- Logic can be represented in pseudo code.~~
~~- Important note – you will likely need to do some research and prototyping of the different technology prior to completing this task.~~ | 1.0 | Low Level Design - ~~- 5 page minimum~~
~~- break down component design information into details.~~
~~- Logic can be represented in pseudo code.~~
~~- Important note – you will likely need to do some research and prototyping of the different technology prior to completing this task.~~ | non_priority | low level design page minimum break down component design information into details logic can be represented in pseudo code important note – you will likely need to do some research and prototyping of the different technology prior to completing this task | 0 |
409,516 | 27,741,324,377 | IssuesEvent | 2023-03-15 14:27:58 | anoma/namada-interface | https://api.github.com/repos/anoma/namada-interface | closed | Plan the refactor for using SDK | C - Documentation T - SDK | Subtask of https://github.com/anoma/namada-interface/issues/177
Currently, the Web Clients Rust interface exposes something that will likely have to change when introducing the SDK to the front end. What has to change could be planned ahead of development for a better "big picture" view.
This would need the definitions or documentation of the SDK that is an outcome of https://github.com/anoma/namada-interface/issues/178
Outcome:
* Create specific tasks in GH for exposing the various parts of the SDK to the web consumer. At least split by:
* accounts
* balances
* transfers
* POS | 1.0 | Plan the refactor for using SDK - Subtask of https://github.com/anoma/namada-interface/issues/177
Currently, the Web Clients Rust interface exposes something that will likely have to change when introducing the SDK to the front end. What has to change could be planned ahead of development for a better "big picture" view.
This would need the definitions or documentation of the SDK that is an outcome of https://github.com/anoma/namada-interface/issues/178
Outcome:
* Create specific tasks in GH for exposing the various parts of the SDK to the web consumer. At least split by:
* accounts
* balances
* transfers
* POS | non_priority | plan the refactor for using sdk subtask of currently the web clients rust interface exposes something that will likely have to change when introducing the sdk to the front end what has to change could be planned ahead of development for a better big picture view this would need the definitions or documentation of the sdk that is an outcome of outcome create specific tasks in gh for exposing the various parts of the sdk to the web consumer at least split by accounts balances transfers pos | 0 |
74,986 | 14,371,502,263 | IssuesEvent | 2020-12-01 12:40:25 | Regalis11/Barotrauma | https://api.github.com/repos/Regalis11/Barotrauma | closed | [Feature Request]: Some form of life monitor to monitor diver health | Code Design Feature request | - [x] I have searched the issue tracker to check if the issue has already been reported.
I believe there needs to be some form of a life monitor on the main sub, either as a control panel/handheld gizmo/etc..., that allows you to monitor the lifeline/health of a diver or many divers at once. Too many times I or other players have gone outside the sub to explore ruins and wrecks only to die and no one back on the sub to realize this turn of events. This often leads to painfully long periods where you wait in spectator mode for anyone still alive on the sub to realize the away-party has died and that they need to do something instead of just continuing to wait around. This is much, much worse when your game isn't respawn shuttle capable.
This problem is obviously not an issue when you're playing with friends as you can just notify them in Discord or something of your recent tragic passing, but purely public games tend to suffer from this in my experience. Of course this issue could be remedied mostly by having better teamwork but it's public games we're talking about here.
The key goal here is to prevent the issue of dead players having to agonizingly wait around when they're dead for everyone else to continue on with the mission.
| 1.0 | [Feature Request]: Some form of life monitor to monitor diver health - - [x] I have searched the issue tracker to check if the issue has already been reported.
I believe there needs to be some form of a life monitor on the main sub, either as a control panel/handheld gizmo/etc..., that allows you to monitor the lifeline/health of a diver or many divers at once. Too many times I or other players have gone outside the sub to explore ruins and wrecks only to die and no one back on the sub to realize this turn of events. This often leads to painfully long periods where you wait in spectator mode for anyone still alive on the sub to realize the away-party has died and that they need to do something instead of just continuing to wait around. This is much, much worse when your game isn't respawn shuttle capable.
This problem is obviously not an issue when you're playing with friends as you can just notify them in Discord or something of your recent tragic passing, but purely public games tend to suffer from this in my experience. Of course this issue could be remedied mostly by having better teamwork but it's public games we're talking about here.
The key goal here is to prevent the issue of dead players having to agonizingly wait around when they're dead for everyone else to continue on with the mission.
| non_priority | some form of life monitor to monitor diver health i have searched the issue tracker to check if the issue has already been reported i believe there needs to be some form of a life monitor on the main sub either as a control panel handheld gizmo etc that allows you to monitor the lifeline health of a diver or many divers at once too many times i or other players have gone outside the sub to explore ruins and wrecks only to die and no one back on the sub to realize this turn of events this often leads to painfully long periods where you wait in spectator mode for anyone still alive on the sub to realize the away party has died and that they need to do something instead of just continuing to wait around this is much much worse when your game isn t respawn shuttle capable this problem is obviously not an issue when you re playing with friends as you can just notify them in discord or something of your recent tragic passing but purely public games tend to suffer from this in my experience of course this issue could be remedied mostly by having better teamwork but it s public games we re talking about here the key goal here is to prevent the issue of dead players having to agonizingly wait around when they re dead for everyone else to continue on with the mission | 0 |
11,235 | 16,678,246,732 | IssuesEvent | 2021-06-07 19:08:54 | NASA-PDS/registry-api-service | https://api.github.com/repos/NASA-PDS/registry-api-service | opened | As a user, I want the end-point /api to return something useful | needs:triage requirement | <!--
For more information on how to populate this new feature request, see the PDS Wiki on User Story Development:
https://github.com/NASA-PDS/nasa-pds.github.io/wiki/Issue-Tracking#user-story-development
-->
## Motivation
...so that I know how to go on with the API.
## Additional Details
<!-- Please prove any additional details or information that could help provide some context for the user story. -->
For example https://pds-gamma.jpl.nasa.gov/api/ should redirect to https://pds-gamma.jpl.nasa.gov/api/swagger-ui.html
## Acceptance Criteria
**Given** <!-- a condition -->
**When I perform** <!-- an action -->
**Then I expect** <!-- the result -->
## Engineering Details
<!--
For dev team. Provide some design / implementation details and/or a sub-task checklist as needed.
Convert issue to Epic if estimate is outside the scope of 1 sprint.
-->
| 1.0 | As a user, I want the end-point /api to return something useful - <!--
For more information on how to populate this new feature request, see the PDS Wiki on User Story Development:
https://github.com/NASA-PDS/nasa-pds.github.io/wiki/Issue-Tracking#user-story-development
-->
## Motivation
...so that I know how to go on with the API.
## Additional Details
<!-- Please prove any additional details or information that could help provide some context for the user story. -->
For example https://pds-gamma.jpl.nasa.gov/api/ should redirect to https://pds-gamma.jpl.nasa.gov/api/swagger-ui.html
## Acceptance Criteria
**Given** <!-- a condition -->
**When I perform** <!-- an action -->
**Then I expect** <!-- the result -->
## Engineering Details
<!--
For dev team. Provide some design / implementation details and/or a sub-task checklist as needed.
Convert issue to Epic if estimate is outside the scope of 1 sprint.
-->
| non_priority | as a user i want the end point api to return something useful for more information on how to populate this new feature request see the pds wiki on user story development motivation so that i know how to go on with the api additional details for example should redirect to acceptance criteria given when i perform then i expect engineering details for dev team provide some design implementation details and or a sub task checklist as needed convert issue to epic if estimate is outside the scope of sprint | 0 |
174,740 | 21,300,420,045 | IssuesEvent | 2022-04-15 01:50:12 | vlaship/spark | https://api.github.com/repos/vlaship/spark | opened | CVE-2022-26612 (High) detected in hadoop-common-2.6.5.jar | security vulnerability | ## CVE-2022-26612 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hadoop-common-2.6.5.jar</b></p></summary>
<p>Apache Hadoop Common</p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /root/.gradle/caches/modules-2/files-2.1/org.apache.hadoop/hadoop-common/2.6.5/775c6ba9b08cf8ec42e27ea0730b69cc990c69ea/hadoop-common-2.6.5.jar,/root/.gradle/caches/modules-2/files-2.1/org.apache.hadoop/hadoop-common/2.6.5/775c6ba9b08cf8ec42e27ea0730b69cc990c69ea/hadoop-common-2.6.5.jar</p>
<p>
Dependency Hierarchy:
- spark-sql_2.12-2.4.4.jar (Root Library)
- spark-core_2.12-2.4.4.jar
- hadoop-client-2.6.5.jar
- :x: **hadoop-common-2.6.5.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Apache Hadoop, The unTar function uses unTarUsingJava function on Windows and the built-in tar utility on Unix and other OSes. As a result, a TAR entry may create a symlink under the expected extraction directory which points to an external directory. A subsequent TAR entry may extract an arbitrary file into the external directory using the symlink name. This however would be caught by the same targetDirPath check on Unix because of the getCanonicalPath call. However on Windows, getCanonicalPath doesn't resolve symbolic links, which bypasses the check. unpackEntries during TAR extraction follows symbolic links which allows writing outside expected base directory on Windows. This was addressed in Apache Hadoop 3.2.3
<p>Publish Date: 2022-04-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-26612>CVE-2022-26612</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: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2022-26612">https://nvd.nist.gov/vuln/detail/CVE-2022-26612</a></p>
<p>Release Date: 2022-04-07</p>
<p>Fix Resolution: org.apache.hadoop:hadoop-common - 2.7.5,0.23.9,2.6.5,2.1.0-beta,2.3.0,2.4.1,2.0.2-alpha,3.3.0,2.7.2,0.23.1,2.9.1,3.2.0,3.1.3,2.5.1,0.23.6,0.23.11,2.7.1;org.apache.servicemix.bundles:org.apache.servicemix.bundles.hadoop-client - 3.0.0_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 | CVE-2022-26612 (High) detected in hadoop-common-2.6.5.jar - ## CVE-2022-26612 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hadoop-common-2.6.5.jar</b></p></summary>
<p>Apache Hadoop Common</p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /root/.gradle/caches/modules-2/files-2.1/org.apache.hadoop/hadoop-common/2.6.5/775c6ba9b08cf8ec42e27ea0730b69cc990c69ea/hadoop-common-2.6.5.jar,/root/.gradle/caches/modules-2/files-2.1/org.apache.hadoop/hadoop-common/2.6.5/775c6ba9b08cf8ec42e27ea0730b69cc990c69ea/hadoop-common-2.6.5.jar</p>
<p>
Dependency Hierarchy:
- spark-sql_2.12-2.4.4.jar (Root Library)
- spark-core_2.12-2.4.4.jar
- hadoop-client-2.6.5.jar
- :x: **hadoop-common-2.6.5.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Apache Hadoop, The unTar function uses unTarUsingJava function on Windows and the built-in tar utility on Unix and other OSes. As a result, a TAR entry may create a symlink under the expected extraction directory which points to an external directory. A subsequent TAR entry may extract an arbitrary file into the external directory using the symlink name. This however would be caught by the same targetDirPath check on Unix because of the getCanonicalPath call. However on Windows, getCanonicalPath doesn't resolve symbolic links, which bypasses the check. unpackEntries during TAR extraction follows symbolic links which allows writing outside expected base directory on Windows. This was addressed in Apache Hadoop 3.2.3
<p>Publish Date: 2022-04-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-26612>CVE-2022-26612</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: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2022-26612">https://nvd.nist.gov/vuln/detail/CVE-2022-26612</a></p>
<p>Release Date: 2022-04-07</p>
<p>Fix Resolution: org.apache.hadoop:hadoop-common - 2.7.5,0.23.9,2.6.5,2.1.0-beta,2.3.0,2.4.1,2.0.2-alpha,3.3.0,2.7.2,0.23.1,2.9.1,3.2.0,3.1.3,2.5.1,0.23.6,0.23.11,2.7.1;org.apache.servicemix.bundles:org.apache.servicemix.bundles.hadoop-client - 3.0.0_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 | cve high detected in hadoop common jar cve high severity vulnerability vulnerable library hadoop common jar apache hadoop common path to dependency file build gradle path to vulnerable library root gradle caches modules files org apache hadoop hadoop common hadoop common jar root gradle caches modules files org apache hadoop hadoop common hadoop common jar dependency hierarchy spark sql jar root library spark core jar hadoop client jar x hadoop common jar vulnerable library vulnerability details in apache hadoop the untar function uses untarusingjava function on windows and the built in tar utility on unix and other oses as a result a tar entry may create a symlink under the expected extraction directory which points to an external directory a subsequent tar entry may extract an arbitrary file into the external directory using the symlink name this however would be caught by the same targetdirpath check on unix because of the getcanonicalpath call however on windows getcanonicalpath doesn t resolve symbolic links which bypasses the check unpackentries during tar extraction follows symbolic links which allows writing outside expected base directory on windows this was addressed in apache hadoop publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache hadoop hadoop common beta alpha org apache servicemix bundles org apache servicemix bundles hadoop client step up your open source security game with whitesource | 0 |
82,598 | 15,650,153,318 | IssuesEvent | 2021-03-23 08:36:56 | kyma-project/kyma | https://api.github.com/repos/kyma-project/kyma | closed | Deprecate node 10 runtime | area/security area/serverless | **Description**
Base image for Node 10 runtime is quite old. Its time to deprecate Node 10 and support never versions of node as the base alpine images for node 10 does not receive a lot of attention from maintainers anymore.
**AC**
- [x] node 10 is marked as deprecated in the serverless runtime documentation
- [x] node 10 is marked as deprecated in the UI in the dropdown : STRETCH
- [ ] when applying a function using node10 runtime via CLI I see a warning log about runtime depreciation
- [x] The release notes mention depreciation of node 10 runtime
- mention grace period (how long do we still build node 10 based function)
- mention [link](https://nodejs.org/tr/blog/uncategorized/10-lts-to-12-lts/) to incompatibilities
**Reasons**
[node:10.23.3-alpine3.11](https://hub.docker.com/_/node/?style=monday&tab=description) might not be supported anytime now and we will get into problems when security vulnerabilities will be discovered in those.
| True | Deprecate node 10 runtime - **Description**
Base image for Node 10 runtime is quite old. Its time to deprecate Node 10 and support never versions of node as the base alpine images for node 10 does not receive a lot of attention from maintainers anymore.
**AC**
- [x] node 10 is marked as deprecated in the serverless runtime documentation
- [x] node 10 is marked as deprecated in the UI in the dropdown : STRETCH
- [ ] when applying a function using node10 runtime via CLI I see a warning log about runtime depreciation
- [x] The release notes mention depreciation of node 10 runtime
- mention grace period (how long do we still build node 10 based function)
- mention [link](https://nodejs.org/tr/blog/uncategorized/10-lts-to-12-lts/) to incompatibilities
**Reasons**
[node:10.23.3-alpine3.11](https://hub.docker.com/_/node/?style=monday&tab=description) might not be supported anytime now and we will get into problems when security vulnerabilities will be discovered in those.
| non_priority | deprecate node runtime description base image for node runtime is quite old its time to deprecate node and support never versions of node as the base alpine images for node does not receive a lot of attention from maintainers anymore ac node is marked as deprecated in the serverless runtime documentation node is marked as deprecated in the ui in the dropdown stretch when applying a function using runtime via cli i see a warning log about runtime depreciation the release notes mention depreciation of node runtime mention grace period how long do we still build node based function mention to incompatibilities reasons might not be supported anytime now and we will get into problems when security vulnerabilities will be discovered in those | 0 |
180,678 | 30,544,445,756 | IssuesEvent | 2023-07-20 01:51:24 | subconsciousnetwork/subconscious | https://api.github.com/repos/subconsciousnetwork/subconscious | closed | Transclude appearance in dark mode is distracting | Enhancement Design | 
@gordonbrander:
> Transclude design in dark mode doesn’t hold up. Borders too faint creating distracting indented look.
> Should experiment with fill instead | 1.0 | Transclude appearance in dark mode is distracting - 
@gordonbrander:
> Transclude design in dark mode doesn’t hold up. Borders too faint creating distracting indented look.
> Should experiment with fill instead | non_priority | transclude appearance in dark mode is distracting gordonbrander transclude design in dark mode doesn’t hold up borders too faint creating distracting indented look should experiment with fill instead | 0 |
31,808 | 13,635,417,278 | IssuesEvent | 2020-09-25 02:48:55 | MicrosoftDocs/azure-docs | https://api.github.com/repos/MicrosoftDocs/azure-docs | closed | Fabrikam: Click Yes to switch Docker to Windows containers now. | Pri2 cxp product-bug service-fabric/svc triaged | The article says, "Click Yes to switch Docker to Windows containers now."
That may be an option in VS 2015 but in VS 2019 it is not. I think they meant:
Click on the Docker system tray icon and click "Switch to Windows containers"
[Enter feedback here]
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 57882c35-3894-f871-bea2-470e74f63c57
* Version Independent ID: 75dada9d-a6a5-c343-e3af-8dab59ad00cb
* Content: [Deploy a .NET app in a container to Azure Service Fabric - Azure Service Fabric](https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-host-app-in-a-container)
* Content Source: [articles/service-fabric/service-fabric-host-app-in-a-container.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/service-fabric/service-fabric-host-app-in-a-container.md)
* Service: **service-fabric**
* GitHub Login: @athinanthny
* Microsoft Alias: **atsenthi** | 1.0 | Fabrikam: Click Yes to switch Docker to Windows containers now. - The article says, "Click Yes to switch Docker to Windows containers now."
That may be an option in VS 2015 but in VS 2019 it is not. I think they meant:
Click on the Docker system tray icon and click "Switch to Windows containers"
[Enter feedback here]
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 57882c35-3894-f871-bea2-470e74f63c57
* Version Independent ID: 75dada9d-a6a5-c343-e3af-8dab59ad00cb
* Content: [Deploy a .NET app in a container to Azure Service Fabric - Azure Service Fabric](https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-host-app-in-a-container)
* Content Source: [articles/service-fabric/service-fabric-host-app-in-a-container.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/service-fabric/service-fabric-host-app-in-a-container.md)
* Service: **service-fabric**
* GitHub Login: @athinanthny
* Microsoft Alias: **atsenthi** | non_priority | fabrikam click yes to switch docker to windows containers now the article says click yes to switch docker to windows containers now that may be an option in vs but in vs it is not i think they meant click on the docker system tray icon and click switch to windows containers document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service service fabric github login athinanthny microsoft alias atsenthi | 0 |
168,952 | 20,827,976,503 | IssuesEvent | 2022-03-19 01:10:26 | billmcchesney1/get-hotel-avail-v2-sample-nodejs | https://api.github.com/repos/billmcchesney1/get-hotel-avail-v2-sample-nodejs | opened | CVE-2021-44906 (Medium) detected in minimist-0.0.8.tgz | security vulnerability | ## CVE-2021-44906 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>minimist-0.0.8.tgz</b></p></summary>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- eslint-3.19.0.tgz (Root Library)
- mkdirp-0.5.1.tgz
- :x: **minimist-0.0.8.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).
<p>Publish Date: 2022-03-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44906>CVE-2021-44906</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-44906">https://nvd.nist.gov/vuln/detail/CVE-2021-44906</a></p>
<p>Release Date: 2022-03-17</p>
<p>Fix Resolution: BumperLane.Public.Service.Contracts - 0.23.35.214-prerelease;cloudscribe.templates - 5.2.0;Virteom.Tenant.Mobile.Bluetooth - 0.21.29.159-prerelease;ShowingVault.DotNet.Sdk - 0.13.41.190-prerelease;Envisia.DotNet.Templates - 3.0.1;Yarnpkg.Yarn - 0.26.1;Virteom.Tenant.Mobile.Framework.UWP - 0.20.41.103-prerelease;Virteom.Tenant.Mobile.Framework.iOS - 0.20.41.103-prerelease;BumperLane.Public.Api.V2.ClientModule - 0.23.35.214-prerelease;VueJS.NetCore - 1.1.1;Dianoga - 4.0.0,3.0.0-RC02;Virteom.Tenant.Mobile.Bluetooth.iOS - 0.20.41.103-prerelease;Virteom.Public.Utilities - 0.23.37.212-prerelease;Indianadavy.VueJsWebAPITemplate.CSharp - 1.0.1;NorDroN.AngularTemplate - 0.1.6;Virteom.Tenant.Mobile.Framework - 0.21.29.159-prerelease;Virteom.Tenant.Mobile.Bluetooth.Android - 0.20.41.103-prerelease;z4a-dotnet-scaffold - 1.0.0.2;Raml.Parser - 1.0.7;CoreVueWebTest - 3.0.101;dotnetng.template - 1.0.0.4;SitecoreMaster.TrueDynamicPlaceholders - 1.0.3;Virteom.Tenant.Mobile.Framework.Android - 0.20.41.103-prerelease;Fable.Template.Elmish.React - 0.1.6;BlazorPolyfill.Build - 6.0.100.2;Fable.Snowpack.Template - 2.1.0;BumperLane.Public.Api.Client - 0.23.35.214-prerelease;Yarn.MSBuild - 0.22.0,0.24.6;Blazor.TailwindCSS.BUnit - 1.0.2;Bridge.AWS - 0.3.30.36;tslint - 5.6.0;SAFE.Template - 3.0.1;GR.PageRender.Razor - 1.8.0;MIDIator.WebClient - 1.0.105</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"0.0.8","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"eslint:3.19.0;mkdirp:0.5.1;minimist:0.0.8","isMinimumFixVersionAvailable":true,"minimumFixVersion":"BumperLane.Public.Service.Contracts - 0.23.35.214-prerelease;cloudscribe.templates - 5.2.0;Virteom.Tenant.Mobile.Bluetooth - 0.21.29.159-prerelease;ShowingVault.DotNet.Sdk - 0.13.41.190-prerelease;Envisia.DotNet.Templates - 3.0.1;Yarnpkg.Yarn - 0.26.1;Virteom.Tenant.Mobile.Framework.UWP - 0.20.41.103-prerelease;Virteom.Tenant.Mobile.Framework.iOS - 0.20.41.103-prerelease;BumperLane.Public.Api.V2.ClientModule - 0.23.35.214-prerelease;VueJS.NetCore - 1.1.1;Dianoga - 4.0.0,3.0.0-RC02;Virteom.Tenant.Mobile.Bluetooth.iOS - 0.20.41.103-prerelease;Virteom.Public.Utilities - 0.23.37.212-prerelease;Indianadavy.VueJsWebAPITemplate.CSharp - 1.0.1;NorDroN.AngularTemplate - 0.1.6;Virteom.Tenant.Mobile.Framework - 0.21.29.159-prerelease;Virteom.Tenant.Mobile.Bluetooth.Android - 0.20.41.103-prerelease;z4a-dotnet-scaffold - 1.0.0.2;Raml.Parser - 1.0.7;CoreVueWebTest - 3.0.101;dotnetng.template - 1.0.0.4;SitecoreMaster.TrueDynamicPlaceholders - 1.0.3;Virteom.Tenant.Mobile.Framework.Android - 0.20.41.103-prerelease;Fable.Template.Elmish.React - 0.1.6;BlazorPolyfill.Build - 6.0.100.2;Fable.Snowpack.Template - 2.1.0;BumperLane.Public.Api.Client - 0.23.35.214-prerelease;Yarn.MSBuild - 0.22.0,0.24.6;Blazor.TailwindCSS.BUnit - 1.0.2;Bridge.AWS - 0.3.30.36;tslint - 5.6.0;SAFE.Template - 3.0.1;GR.PageRender.Razor - 1.8.0;MIDIator.WebClient - 1.0.105","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-44906","vulnerabilityDetails":"Minimist \u003c\u003d1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44906","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"Required","AV":"Local","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2021-44906 (Medium) detected in minimist-0.0.8.tgz - ## CVE-2021-44906 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>minimist-0.0.8.tgz</b></p></summary>
<p>parse argument options</p>
<p>Library home page: <a href="https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz">https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/minimist/package.json</p>
<p>
Dependency Hierarchy:
- eslint-3.19.0.tgz (Root Library)
- mkdirp-0.5.1.tgz
- :x: **minimist-0.0.8.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).
<p>Publish Date: 2022-03-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44906>CVE-2021-44906</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-44906">https://nvd.nist.gov/vuln/detail/CVE-2021-44906</a></p>
<p>Release Date: 2022-03-17</p>
<p>Fix Resolution: BumperLane.Public.Service.Contracts - 0.23.35.214-prerelease;cloudscribe.templates - 5.2.0;Virteom.Tenant.Mobile.Bluetooth - 0.21.29.159-prerelease;ShowingVault.DotNet.Sdk - 0.13.41.190-prerelease;Envisia.DotNet.Templates - 3.0.1;Yarnpkg.Yarn - 0.26.1;Virteom.Tenant.Mobile.Framework.UWP - 0.20.41.103-prerelease;Virteom.Tenant.Mobile.Framework.iOS - 0.20.41.103-prerelease;BumperLane.Public.Api.V2.ClientModule - 0.23.35.214-prerelease;VueJS.NetCore - 1.1.1;Dianoga - 4.0.0,3.0.0-RC02;Virteom.Tenant.Mobile.Bluetooth.iOS - 0.20.41.103-prerelease;Virteom.Public.Utilities - 0.23.37.212-prerelease;Indianadavy.VueJsWebAPITemplate.CSharp - 1.0.1;NorDroN.AngularTemplate - 0.1.6;Virteom.Tenant.Mobile.Framework - 0.21.29.159-prerelease;Virteom.Tenant.Mobile.Bluetooth.Android - 0.20.41.103-prerelease;z4a-dotnet-scaffold - 1.0.0.2;Raml.Parser - 1.0.7;CoreVueWebTest - 3.0.101;dotnetng.template - 1.0.0.4;SitecoreMaster.TrueDynamicPlaceholders - 1.0.3;Virteom.Tenant.Mobile.Framework.Android - 0.20.41.103-prerelease;Fable.Template.Elmish.React - 0.1.6;BlazorPolyfill.Build - 6.0.100.2;Fable.Snowpack.Template - 2.1.0;BumperLane.Public.Api.Client - 0.23.35.214-prerelease;Yarn.MSBuild - 0.22.0,0.24.6;Blazor.TailwindCSS.BUnit - 1.0.2;Bridge.AWS - 0.3.30.36;tslint - 5.6.0;SAFE.Template - 3.0.1;GR.PageRender.Razor - 1.8.0;MIDIator.WebClient - 1.0.105</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"minimist","packageVersion":"0.0.8","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"eslint:3.19.0;mkdirp:0.5.1;minimist:0.0.8","isMinimumFixVersionAvailable":true,"minimumFixVersion":"BumperLane.Public.Service.Contracts - 0.23.35.214-prerelease;cloudscribe.templates - 5.2.0;Virteom.Tenant.Mobile.Bluetooth - 0.21.29.159-prerelease;ShowingVault.DotNet.Sdk - 0.13.41.190-prerelease;Envisia.DotNet.Templates - 3.0.1;Yarnpkg.Yarn - 0.26.1;Virteom.Tenant.Mobile.Framework.UWP - 0.20.41.103-prerelease;Virteom.Tenant.Mobile.Framework.iOS - 0.20.41.103-prerelease;BumperLane.Public.Api.V2.ClientModule - 0.23.35.214-prerelease;VueJS.NetCore - 1.1.1;Dianoga - 4.0.0,3.0.0-RC02;Virteom.Tenant.Mobile.Bluetooth.iOS - 0.20.41.103-prerelease;Virteom.Public.Utilities - 0.23.37.212-prerelease;Indianadavy.VueJsWebAPITemplate.CSharp - 1.0.1;NorDroN.AngularTemplate - 0.1.6;Virteom.Tenant.Mobile.Framework - 0.21.29.159-prerelease;Virteom.Tenant.Mobile.Bluetooth.Android - 0.20.41.103-prerelease;z4a-dotnet-scaffold - 1.0.0.2;Raml.Parser - 1.0.7;CoreVueWebTest - 3.0.101;dotnetng.template - 1.0.0.4;SitecoreMaster.TrueDynamicPlaceholders - 1.0.3;Virteom.Tenant.Mobile.Framework.Android - 0.20.41.103-prerelease;Fable.Template.Elmish.React - 0.1.6;BlazorPolyfill.Build - 6.0.100.2;Fable.Snowpack.Template - 2.1.0;BumperLane.Public.Api.Client - 0.23.35.214-prerelease;Yarn.MSBuild - 0.22.0,0.24.6;Blazor.TailwindCSS.BUnit - 1.0.2;Bridge.AWS - 0.3.30.36;tslint - 5.6.0;SAFE.Template - 3.0.1;GR.PageRender.Razor - 1.8.0;MIDIator.WebClient - 1.0.105","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-44906","vulnerabilityDetails":"Minimist \u003c\u003d1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-44906","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"Required","AV":"Local","I":"None"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in minimist tgz cve medium severity vulnerability vulnerable library minimist tgz parse argument options library home page a href path to dependency file package json path to vulnerable library node modules minimist package json dependency hierarchy eslint tgz root library mkdirp tgz x minimist tgz vulnerable library found in base branch master vulnerability details minimist is vulnerable to prototype pollution via file index js function setkey lines publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution bumperlane public service contracts prerelease cloudscribe templates virteom tenant mobile bluetooth prerelease showingvault dotnet sdk prerelease envisia dotnet templates yarnpkg yarn virteom tenant mobile framework uwp prerelease virteom tenant mobile framework ios prerelease bumperlane public api clientmodule prerelease vuejs netcore dianoga virteom tenant mobile bluetooth ios prerelease virteom public utilities prerelease indianadavy vuejswebapitemplate csharp nordron angulartemplate virteom tenant mobile framework prerelease virteom tenant mobile bluetooth android prerelease dotnet scaffold raml parser corevuewebtest dotnetng template sitecoremaster truedynamicplaceholders virteom tenant mobile framework android prerelease fable template elmish react blazorpolyfill build fable snowpack template bumperlane public api client prerelease yarn msbuild blazor tailwindcss bunit bridge aws tslint safe template gr pagerender razor midiator webclient isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree eslint mkdirp minimist isminimumfixversionavailable true minimumfixversion bumperlane public service contracts prerelease cloudscribe templates virteom tenant mobile bluetooth prerelease showingvault dotnet sdk prerelease envisia dotnet templates yarnpkg yarn virteom tenant mobile framework uwp prerelease virteom tenant mobile framework ios prerelease bumperlane public api clientmodule prerelease vuejs netcore dianoga virteom tenant mobile bluetooth ios prerelease virteom public utilities prerelease indianadavy vuejswebapitemplate csharp nordron angulartemplate virteom tenant mobile framework prerelease virteom tenant mobile bluetooth android prerelease dotnet scaffold raml parser corevuewebtest dotnetng template sitecoremaster truedynamicplaceholders virteom tenant mobile framework android prerelease fable template elmish react blazorpolyfill build fable snowpack template bumperlane public api client prerelease yarn msbuild blazor tailwindcss bunit bridge aws tslint safe template gr pagerender razor midiator webclient isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails minimist is vulnerable to prototype pollution via file index js function setkey lines vulnerabilityurl | 0 |
185,302 | 21,786,097,608 | IssuesEvent | 2022-05-14 06:31:22 | classicvalues/AA-ionic-login | https://api.github.com/repos/classicvalues/AA-ionic-login | closed | CVE-2021-43138 (High) detected in multiple libraries - autoclosed | security vulnerability | ## CVE-2021-43138 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>async-2.5.0.tgz</b>, <b>async-1.0.0.tgz</b>, <b>async-3.2.0.tgz</b>, <b>async-0.2.10.tgz</b>, <b>async-2.0.1.tgz</b>, <b>async-2.6.3.tgz</b>, <b>async-0.9.2.tgz</b></p></summary>
<p>
<details><summary><b>async-2.5.0.tgz</b></p></summary>
<p>Higher-order functions and common patterns for asynchronous code</p>
<p>Library home page: <a href="https://registry.npmjs.org/async/-/async-2.5.0.tgz">https://registry.npmjs.org/async/-/async-2.5.0.tgz</a></p>
<p>Path to dependency file: /Application/package.json</p>
<p>Path to vulnerable library: /Application/node_modules/sails/node_modules/async/package.json</p>
<p>
Dependency Hierarchy:
- sails-1.5.2.tgz (Root Library)
- :x: **async-2.5.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>async-1.0.0.tgz</b></p></summary>
<p>Higher-order functions and common patterns for asynchronous code</p>
<p>Library home page: <a href="https://registry.npmjs.org/async/-/async-1.0.0.tgz">https://registry.npmjs.org/async/-/async-1.0.0.tgz</a></p>
<p>Path to dependency file: /Application/package.json</p>
<p>Path to vulnerable library: /Application/node_modules/winston/node_modules/async/package.json</p>
<p>
Dependency Hierarchy:
- sails-1.5.2.tgz (Root Library)
- prompt-1.2.1.tgz
- winston-2.4.5.tgz
- :x: **async-1.0.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>async-3.2.0.tgz</b></p></summary>
<p>Higher-order functions and common patterns for asynchronous code</p>
<p>Library home page: <a href="https://registry.npmjs.org/async/-/async-3.2.0.tgz">https://registry.npmjs.org/async/-/async-3.2.0.tgz</a></p>
<p>Path to dependency file: /Application/package.json</p>
<p>Path to vulnerable library: /Application/node_modules/grunt-contrib-less/node_modules/async/package.json,/Application/node_modules/grunt-legacy-util/node_modules/async/package.json</p>
<p>
Dependency Hierarchy:
- grunt-contrib-less-3.0.0.tgz (Root Library)
- :x: **async-3.2.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>async-0.2.10.tgz</b></p></summary>
<p>Higher-order functions and common patterns for asynchronous code</p>
<p>Library home page: <a href="https://registry.npmjs.org/async/-/async-0.2.10.tgz">https://registry.npmjs.org/async/-/async-0.2.10.tgz</a></p>
<p>Path to dependency file: /Application/package.json</p>
<p>Path to vulnerable library: /Application/node_modules/@sailshq/nedb/node_modules/async/package.json</p>
<p>
Dependency Hierarchy:
- sails-disk-2.1.1.tgz (Root Library)
- nedb-1.8.1.tgz
- :x: **async-0.2.10.tgz** (Vulnerable Library)
</details>
<details><summary><b>async-2.0.1.tgz</b></p></summary>
<p>Higher-order functions and common patterns for asynchronous code</p>
<p>Library home page: <a href="https://registry.npmjs.org/async/-/async-2.0.1.tgz">https://registry.npmjs.org/async/-/async-2.0.1.tgz</a></p>
<p>Path to dependency file: /Application/package.json</p>
<p>Path to vulnerable library: /Application/node_modules/async/package.json</p>
<p>
Dependency Hierarchy:
- sails-disk-2.1.1.tgz (Root Library)
- :x: **async-2.0.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>async-2.6.3.tgz</b></p></summary>
<p>Higher-order functions and common patterns for asynchronous code</p>
<p>Library home page: <a href="https://registry.npmjs.org/async/-/async-2.6.3.tgz">https://registry.npmjs.org/async/-/async-2.6.3.tgz</a></p>
<p>Path to dependency file: /Application/package.json</p>
<p>Path to vulnerable library: /Application/node_modules/grunt-contrib-watch/node_modules/async/package.json,/Application/node_modules/grunt-contrib-clean/node_modules/async/package.json</p>
<p>
Dependency Hierarchy:
- grunt-contrib-watch-1.1.0.tgz (Root Library)
- :x: **async-2.6.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>async-0.9.2.tgz</b></p></summary>
<p>Higher-order functions and common patterns for asynchronous code</p>
<p>Library home page: <a href="https://registry.npmjs.org/async/-/async-0.9.2.tgz">https://registry.npmjs.org/async/-/async-0.9.2.tgz</a></p>
<p>Path to dependency file: /Application/package.json</p>
<p>Path to vulnerable library: /Application/node_modules/prompt/node_modules/async/package.json,/Application/node_modules/jake/node_modules/async/package.json</p>
<p>
Dependency Hierarchy:
- ejs-3.1.6.tgz (Root Library)
- jake-10.8.2.tgz
- :x: **async-0.9.2.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/classicvalues/AA-ionic-login/commit/d4f4480b7ddd8c520e4b02ea2008621ded4be6ab">d4f4480b7ddd8c520e4b02ea2008621ded4be6ab</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Async before 2.6.4 and 3.x before 3.2.2, a malicious user can obtain privileges via the mapValues() method, aka lib/internal/iterator.js createObjectIterator prototype pollution.
<p>Publish Date: 2022-04-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-43138>CVE-2021-43138</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://nvd.nist.gov/vuln/detail/CVE-2021-43138">https://nvd.nist.gov/vuln/detail/CVE-2021-43138</a></p>
<p>Release Date: 2022-04-06</p>
<p>Fix Resolution (async): 2.6.4</p>
<p>Direct dependency fix Resolution (ejs): 3.1.7</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-43138 (High) detected in multiple libraries - autoclosed - ## CVE-2021-43138 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>async-2.5.0.tgz</b>, <b>async-1.0.0.tgz</b>, <b>async-3.2.0.tgz</b>, <b>async-0.2.10.tgz</b>, <b>async-2.0.1.tgz</b>, <b>async-2.6.3.tgz</b>, <b>async-0.9.2.tgz</b></p></summary>
<p>
<details><summary><b>async-2.5.0.tgz</b></p></summary>
<p>Higher-order functions and common patterns for asynchronous code</p>
<p>Library home page: <a href="https://registry.npmjs.org/async/-/async-2.5.0.tgz">https://registry.npmjs.org/async/-/async-2.5.0.tgz</a></p>
<p>Path to dependency file: /Application/package.json</p>
<p>Path to vulnerable library: /Application/node_modules/sails/node_modules/async/package.json</p>
<p>
Dependency Hierarchy:
- sails-1.5.2.tgz (Root Library)
- :x: **async-2.5.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>async-1.0.0.tgz</b></p></summary>
<p>Higher-order functions and common patterns for asynchronous code</p>
<p>Library home page: <a href="https://registry.npmjs.org/async/-/async-1.0.0.tgz">https://registry.npmjs.org/async/-/async-1.0.0.tgz</a></p>
<p>Path to dependency file: /Application/package.json</p>
<p>Path to vulnerable library: /Application/node_modules/winston/node_modules/async/package.json</p>
<p>
Dependency Hierarchy:
- sails-1.5.2.tgz (Root Library)
- prompt-1.2.1.tgz
- winston-2.4.5.tgz
- :x: **async-1.0.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>async-3.2.0.tgz</b></p></summary>
<p>Higher-order functions and common patterns for asynchronous code</p>
<p>Library home page: <a href="https://registry.npmjs.org/async/-/async-3.2.0.tgz">https://registry.npmjs.org/async/-/async-3.2.0.tgz</a></p>
<p>Path to dependency file: /Application/package.json</p>
<p>Path to vulnerable library: /Application/node_modules/grunt-contrib-less/node_modules/async/package.json,/Application/node_modules/grunt-legacy-util/node_modules/async/package.json</p>
<p>
Dependency Hierarchy:
- grunt-contrib-less-3.0.0.tgz (Root Library)
- :x: **async-3.2.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>async-0.2.10.tgz</b></p></summary>
<p>Higher-order functions and common patterns for asynchronous code</p>
<p>Library home page: <a href="https://registry.npmjs.org/async/-/async-0.2.10.tgz">https://registry.npmjs.org/async/-/async-0.2.10.tgz</a></p>
<p>Path to dependency file: /Application/package.json</p>
<p>Path to vulnerable library: /Application/node_modules/@sailshq/nedb/node_modules/async/package.json</p>
<p>
Dependency Hierarchy:
- sails-disk-2.1.1.tgz (Root Library)
- nedb-1.8.1.tgz
- :x: **async-0.2.10.tgz** (Vulnerable Library)
</details>
<details><summary><b>async-2.0.1.tgz</b></p></summary>
<p>Higher-order functions and common patterns for asynchronous code</p>
<p>Library home page: <a href="https://registry.npmjs.org/async/-/async-2.0.1.tgz">https://registry.npmjs.org/async/-/async-2.0.1.tgz</a></p>
<p>Path to dependency file: /Application/package.json</p>
<p>Path to vulnerable library: /Application/node_modules/async/package.json</p>
<p>
Dependency Hierarchy:
- sails-disk-2.1.1.tgz (Root Library)
- :x: **async-2.0.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>async-2.6.3.tgz</b></p></summary>
<p>Higher-order functions and common patterns for asynchronous code</p>
<p>Library home page: <a href="https://registry.npmjs.org/async/-/async-2.6.3.tgz">https://registry.npmjs.org/async/-/async-2.6.3.tgz</a></p>
<p>Path to dependency file: /Application/package.json</p>
<p>Path to vulnerable library: /Application/node_modules/grunt-contrib-watch/node_modules/async/package.json,/Application/node_modules/grunt-contrib-clean/node_modules/async/package.json</p>
<p>
Dependency Hierarchy:
- grunt-contrib-watch-1.1.0.tgz (Root Library)
- :x: **async-2.6.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>async-0.9.2.tgz</b></p></summary>
<p>Higher-order functions and common patterns for asynchronous code</p>
<p>Library home page: <a href="https://registry.npmjs.org/async/-/async-0.9.2.tgz">https://registry.npmjs.org/async/-/async-0.9.2.tgz</a></p>
<p>Path to dependency file: /Application/package.json</p>
<p>Path to vulnerable library: /Application/node_modules/prompt/node_modules/async/package.json,/Application/node_modules/jake/node_modules/async/package.json</p>
<p>
Dependency Hierarchy:
- ejs-3.1.6.tgz (Root Library)
- jake-10.8.2.tgz
- :x: **async-0.9.2.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/classicvalues/AA-ionic-login/commit/d4f4480b7ddd8c520e4b02ea2008621ded4be6ab">d4f4480b7ddd8c520e4b02ea2008621ded4be6ab</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Async before 2.6.4 and 3.x before 3.2.2, a malicious user can obtain privileges via the mapValues() method, aka lib/internal/iterator.js createObjectIterator prototype pollution.
<p>Publish Date: 2022-04-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-43138>CVE-2021-43138</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://nvd.nist.gov/vuln/detail/CVE-2021-43138">https://nvd.nist.gov/vuln/detail/CVE-2021-43138</a></p>
<p>Release Date: 2022-04-06</p>
<p>Fix Resolution (async): 2.6.4</p>
<p>Direct dependency fix Resolution (ejs): 3.1.7</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in multiple libraries autoclosed cve high severity vulnerability vulnerable libraries async tgz async tgz async tgz async tgz async tgz async tgz async tgz async tgz higher order functions and common patterns for asynchronous code library home page a href path to dependency file application package json path to vulnerable library application node modules sails node modules async package json dependency hierarchy sails tgz root library x async tgz vulnerable library async tgz higher order functions and common patterns for asynchronous code library home page a href path to dependency file application package json path to vulnerable library application node modules winston node modules async package json dependency hierarchy sails tgz root library prompt tgz winston tgz x async tgz vulnerable library async tgz higher order functions and common patterns for asynchronous code library home page a href path to dependency file application package json path to vulnerable library application node modules grunt contrib less node modules async package json application node modules grunt legacy util node modules async package json dependency hierarchy grunt contrib less tgz root library x async tgz vulnerable library async tgz higher order functions and common patterns for asynchronous code library home page a href path to dependency file application package json path to vulnerable library application node modules sailshq nedb node modules async package json dependency hierarchy sails disk tgz root library nedb tgz x async tgz vulnerable library async tgz higher order functions and common patterns for asynchronous code library home page a href path to dependency file application package json path to vulnerable library application node modules async package json dependency hierarchy sails disk tgz root library x async tgz vulnerable library async tgz higher order functions and common patterns for asynchronous code library home page a href path to dependency file application package json path to vulnerable library application node modules grunt contrib watch node modules async package json application node modules grunt contrib clean node modules async package json dependency hierarchy grunt contrib watch tgz root library x async tgz vulnerable library async tgz higher order functions and common patterns for asynchronous code library home page a href path to dependency file application package json path to vulnerable library application node modules prompt node modules async package json application node modules jake node modules async package json dependency hierarchy ejs tgz root library jake tgz x async tgz vulnerable library found in head commit a href found in base branch master vulnerability details in async before and x before a malicious user can obtain privileges via the mapvalues method aka lib internal iterator js createobjectiterator prototype pollution 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 async direct dependency fix resolution ejs step up your open source security game with whitesource | 0 |
121,758 | 16,020,970,282 | IssuesEvent | 2021-04-20 23:13:55 | mozilla/foundation.mozilla.org | https://api.github.com/repos/mozilla/foundation.mozilla.org | opened | Make sure we are loading italic font styles from Google & update /style-guide to include examples | design engineering frontend | https://github.com/mozilla/foundation.mozilla.org/blob/master/network-api/networkapi/templates/pages/base.html#L33-L37
- [ ] It looks like we are only loading `300i` for both Nunito Sans and Zilla Slab. We should make sure italic styles are loaded for other font weights as well.
- [ ] Work with designer and add examples to /style-guide page to demonstrate italic style for body text. This can also help us capture regressions (via Percy) if italic style doesn't get loaded properly to the site.
/cc @sabrinang @danielfmiranda | 1.0 | Make sure we are loading italic font styles from Google & update /style-guide to include examples - https://github.com/mozilla/foundation.mozilla.org/blob/master/network-api/networkapi/templates/pages/base.html#L33-L37
- [ ] It looks like we are only loading `300i` for both Nunito Sans and Zilla Slab. We should make sure italic styles are loaded for other font weights as well.
- [ ] Work with designer and add examples to /style-guide page to demonstrate italic style for body text. This can also help us capture regressions (via Percy) if italic style doesn't get loaded properly to the site.
/cc @sabrinang @danielfmiranda | non_priority | make sure we are loading italic font styles from google update style guide to include examples it looks like we are only loading for both nunito sans and zilla slab we should make sure italic styles are loaded for other font weights as well work with designer and add examples to style guide page to demonstrate italic style for body text this can also help us capture regressions via percy if italic style doesn t get loaded properly to the site cc sabrinang danielfmiranda | 0 |
44,980 | 11,569,382,733 | IssuesEvent | 2020-02-20 17:26:59 | Scirra/Construct-3-bugs | https://api.github.com/repos/Scirra/Construct-3-bugs | closed | Whitelist plugin request | Build Service | Could you whitelist:
cordova-plugin-firebase-analytics@latest_version
cordova-plugin-facebook4@latest_version
cordova-plugin-inapppurchase-fixed@latest_version
onesignal-cordova-plugin@latest_version
cordova-plugin-wkwebview-engine@latest_version
cordova-plugin-vibration@latest_version
cordova-plugin-statusbar@latest_version
Thanks! 😀 | 1.0 | Whitelist plugin request - Could you whitelist:
cordova-plugin-firebase-analytics@latest_version
cordova-plugin-facebook4@latest_version
cordova-plugin-inapppurchase-fixed@latest_version
onesignal-cordova-plugin@latest_version
cordova-plugin-wkwebview-engine@latest_version
cordova-plugin-vibration@latest_version
cordova-plugin-statusbar@latest_version
Thanks! 😀 | non_priority | whitelist plugin request could you whitelist cordova plugin firebase analytics latest version cordova plugin latest version cordova plugin inapppurchase fixed latest version onesignal cordova plugin latest version cordova plugin wkwebview engine latest version cordova plugin vibration latest version cordova plugin statusbar latest version thanks 😀 | 0 |
51,468 | 6,160,773,314 | IssuesEvent | 2017-06-29 06:43:17 | Gizra/Municipality | https://api.github.com/repos/Gizra/Municipality | closed | Events links on homepage are incorrect [3h] | Bug Merged Test | The language Query string should come after the url.
http://test-municipality.pantheonsite.io/municipality-1/node/1?language=he
Wrong link examples on homepage:
http://test-municipality.pantheonsite.io/municipality-1?language=he/node/32
http://test-municipality.pantheonsite.io/municipality-1?language=he/node/29
| 1.0 | Events links on homepage are incorrect [3h] - The language Query string should come after the url.
http://test-municipality.pantheonsite.io/municipality-1/node/1?language=he
Wrong link examples on homepage:
http://test-municipality.pantheonsite.io/municipality-1?language=he/node/32
http://test-municipality.pantheonsite.io/municipality-1?language=he/node/29
| non_priority | events links on homepage are incorrect the language query string should come after the url wrong link examples on homepage | 0 |
32,643 | 8,908,423,126 | IssuesEvent | 2019-01-18 00:47:15 | ApolloAuto/apollo | https://api.github.com/repos/ApolloAuto/apollo | closed | bash apollo.sh build error！----file name too long | Module: Build Type: Help wanted | **Describe the bug**
When I executed bash apollo.sh build, an error occurred.
**Screenshots**
**Desktop (please complete the following information):**
- OS: ubuntu 16.04
- Browser google
**Additional context**
The same error occurs when apollo.sh build_cpu
| 1.0 | bash apollo.sh build error！----file name too long - **Describe the bug**
When I executed bash apollo.sh build, an error occurred.
**Screenshots**
**Desktop (please complete the following information):**
- OS: ubuntu 16.04
- Browser google
**Additional context**
The same error occurs when apollo.sh build_cpu
| non_priority | bash apollo sh build error！ file name too long describe the bug when i executed bash apollo sh build an error occurred screenshots desktop please complete the following information os ubuntu browser google additional context the same error occurs when apollo sh build cpu | 0 |
71,220 | 15,185,662,107 | IssuesEvent | 2021-02-15 11:14:49 | Neko7sora/github-slideshow | https://api.github.com/repos/Neko7sora/github-slideshow | opened | CVE-2020-11022 (Medium) detected in jquery-1.11.1.min.js | security vulnerability | ## CVE-2020-11022 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-1.11.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.11.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.11.1/jquery.min.js</a></p>
<p>Path to vulnerable library: github-slideshow/assets/js/jquery-1.11.1.min.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.11.1.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Neko7sora/github-slideshow/commit/8fc3587745ff93a1f1fa8c24067543cc601e781a">8fc3587745ff93a1f1fa8c24067543cc601e781a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML 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://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11022>CVE-2020-11022</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://blog.jquery.com/2020/04/10/jquery-3-5-0-released/">https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/</a></p>
<p>Release Date: 2020-04-29</p>
<p>Fix Resolution: jQuery - 3.5.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-11022 (Medium) detected in jquery-1.11.1.min.js - ## CVE-2020-11022 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-1.11.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.11.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.11.1/jquery.min.js</a></p>
<p>Path to vulnerable library: github-slideshow/assets/js/jquery-1.11.1.min.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.11.1.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Neko7sora/github-slideshow/commit/8fc3587745ff93a1f1fa8c24067543cc601e781a">8fc3587745ff93a1f1fa8c24067543cc601e781a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML 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://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11022>CVE-2020-11022</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://blog.jquery.com/2020/04/10/jquery-3-5-0-released/">https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/</a></p>
<p>Release Date: 2020-04-29</p>
<p>Fix Resolution: jQuery - 3.5.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_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 vulnerable library github slideshow assets js jquery min js dependency hierarchy x jquery min js vulnerable library found in head commit a href found in base branch master vulnerability details in jquery versions greater than or equal to and before passing html 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 step up your open source security game with whitesource | 0 |
8,838 | 3,009,983,484 | IssuesEvent | 2015-07-28 10:15:20 | oSoc15/educal | https://api.github.com/repos/oSoc15/educal | closed | As a parent, I can select which calendar I want to hide/show | 3 - Ready To Test | - [x] UI design
- [x] Multi-select in front end
- [x] Dropdown SVG arrow | 1.0 | As a parent, I can select which calendar I want to hide/show - - [x] UI design
- [x] Multi-select in front end
- [x] Dropdown SVG arrow | non_priority | as a parent i can select which calendar i want to hide show ui design multi select in front end dropdown svg arrow | 0 |
247,437 | 26,711,529,409 | IssuesEvent | 2023-01-28 01:02:05 | improbable/k8s-test-infra | https://api.github.com/repos/improbable/k8s-test-infra | closed | requests-2.27.1-py2.py3-none-any.whl: 1 vulnerabilities (highest severity is: 7.5) - autoclosed | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>requests-2.27.1-py2.py3-none-any.whl</b></p></summary>
<p></p>
<p>Path to dependency file: /hack/test_requirements.txt</p>
<p>Path to vulnerable library: /hack/test_requirements.txt</p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (requests version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-23491](https://www.mend.io/vulnerability-database/CVE-2022-23491) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | certifi-2022.5.18.1-py3-none-any.whl | Transitive | N/A* | ❌ |
<p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the section "Details" below to see if there is a version of transitive dependency where vulnerability is fixed.</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-23491</summary>
### Vulnerable Library - <b>certifi-2022.5.18.1-py3-none-any.whl</b></p>
<p>Python package for providing Mozilla's CA Bundle.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/11/dd/e015f3780f42dd9af62cf0107b44ea1298926627ecd70c17b0e484e95bcd/certifi-2022.5.18.1-py3-none-any.whl">https://files.pythonhosted.org/packages/11/dd/e015f3780f42dd9af62cf0107b44ea1298926627ecd70c17b0e484e95bcd/certifi-2022.5.18.1-py3-none-any.whl</a></p>
<p>Path to dependency file: /hack/test_requirements.txt</p>
<p>Path to vulnerable library: /hack/test_requirements.txt</p>
<p>
Dependency Hierarchy:
- requests-2.27.1-py2.py3-none-any.whl (Root Library)
- :x: **certifi-2022.5.18.1-py3-none-any.whl** (Vulnerable Library)
<p>Found in base branch: <b>improbable</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Certifi is a curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. Certifi 2022.12.07 removes root certificates from "TrustCor" from the root store. These are in the process of being removed from Mozilla's trust store. TrustCor's root certificates are being removed pursuant to an investigation prompted by media reporting that TrustCor's ownership also operated a business that produced spyware. Conclusions of Mozilla's investigation can be found in the linked google group discussion.
<p>Publish Date: 2022-12-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23491>CVE-2022-23491</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-23491">https://www.cve.org/CVERecord?id=CVE-2022-23491</a></p>
<p>Release Date: 2022-12-07</p>
<p>Fix Resolution: certifi - 2022.12.07</p>
</p>
<p></p>
</details> | True | requests-2.27.1-py2.py3-none-any.whl: 1 vulnerabilities (highest severity is: 7.5) - autoclosed - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>requests-2.27.1-py2.py3-none-any.whl</b></p></summary>
<p></p>
<p>Path to dependency file: /hack/test_requirements.txt</p>
<p>Path to vulnerable library: /hack/test_requirements.txt</p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (requests version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-23491](https://www.mend.io/vulnerability-database/CVE-2022-23491) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | certifi-2022.5.18.1-py3-none-any.whl | Transitive | N/A* | ❌ |
<p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the section "Details" below to see if there is a version of transitive dependency where vulnerability is fixed.</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-23491</summary>
### Vulnerable Library - <b>certifi-2022.5.18.1-py3-none-any.whl</b></p>
<p>Python package for providing Mozilla's CA Bundle.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/11/dd/e015f3780f42dd9af62cf0107b44ea1298926627ecd70c17b0e484e95bcd/certifi-2022.5.18.1-py3-none-any.whl">https://files.pythonhosted.org/packages/11/dd/e015f3780f42dd9af62cf0107b44ea1298926627ecd70c17b0e484e95bcd/certifi-2022.5.18.1-py3-none-any.whl</a></p>
<p>Path to dependency file: /hack/test_requirements.txt</p>
<p>Path to vulnerable library: /hack/test_requirements.txt</p>
<p>
Dependency Hierarchy:
- requests-2.27.1-py2.py3-none-any.whl (Root Library)
- :x: **certifi-2022.5.18.1-py3-none-any.whl** (Vulnerable Library)
<p>Found in base branch: <b>improbable</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Certifi is a curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. Certifi 2022.12.07 removes root certificates from "TrustCor" from the root store. These are in the process of being removed from Mozilla's trust store. TrustCor's root certificates are being removed pursuant to an investigation prompted by media reporting that TrustCor's ownership also operated a business that produced spyware. Conclusions of Mozilla's investigation can be found in the linked google group discussion.
<p>Publish Date: 2022-12-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23491>CVE-2022-23491</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-23491">https://www.cve.org/CVERecord?id=CVE-2022-23491</a></p>
<p>Release Date: 2022-12-07</p>
<p>Fix Resolution: certifi - 2022.12.07</p>
</p>
<p></p>
</details> | non_priority | requests none any whl vulnerabilities highest severity is autoclosed vulnerable library requests none any whl path to dependency file hack test requirements txt path to vulnerable library hack test requirements txt vulnerabilities cve severity cvss dependency type fixed in requests version remediation available high certifi none any whl transitive n a for some transitive vulnerabilities there is no version of direct dependency with a fix check the section details below to see if there is a version of transitive dependency where vulnerability is fixed details cve vulnerable library certifi none any whl python package for providing mozilla s ca bundle library home page a href path to dependency file hack test requirements txt path to vulnerable library hack test requirements txt dependency hierarchy requests none any whl root library x certifi none any whl vulnerable library found in base branch improbable vulnerability details certifi is a curated collection of root certificates for validating the trustworthiness of ssl certificates while verifying the identity of tls hosts certifi removes root certificates from trustcor from the root store these are in the process of being removed from mozilla s trust store trustcor s root certificates are being removed pursuant to an investigation prompted by media reporting that trustcor s ownership also operated a business that produced spyware conclusions of mozilla s investigation can be found in the linked google group discussion publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution certifi | 0 |
9,400 | 3,283,209,329 | IssuesEvent | 2015-10-28 11:23:48 | SwissTPH/openmalaria | https://api.github.com/repos/SwissTPH/openmalaria | closed | Adjust documentation for new timestep inputs (XML) | 1: high documentation from-OM_TODO | Adjust documentation to represent the current state of code:
1. check wiki has documentation on dates and timestep units
2. update examples on wiki / snippets to use dates or units
3. clarify what a timestep is:
Dates should refer to a particular day at midday; a timestep is the update between two dates (midday to midday, either one day or five).
Additionally, is this implemented? :
2: automatically determine start of simulation
Simulation (intervention period) should start with first survey.
No interventions should be allowed before this date.
| 1.0 | Adjust documentation for new timestep inputs (XML) - Adjust documentation to represent the current state of code:
1. check wiki has documentation on dates and timestep units
2. update examples on wiki / snippets to use dates or units
3. clarify what a timestep is:
Dates should refer to a particular day at midday; a timestep is the update between two dates (midday to midday, either one day or five).
Additionally, is this implemented? :
2: automatically determine start of simulation
Simulation (intervention period) should start with first survey.
No interventions should be allowed before this date.
| non_priority | adjust documentation for new timestep inputs xml adjust documentation to represent the current state of code check wiki has documentation on dates and timestep units update examples on wiki snippets to use dates or units clarify what a timestep is dates should refer to a particular day at midday a timestep is the update between two dates midday to midday either one day or five additionally is this implemented automatically determine start of simulation simulation intervention period should start with first survey no interventions should be allowed before this date | 0 |
133,543 | 29,269,547,230 | IssuesEvent | 2023-05-24 00:36:02 | cse110-sp23-group16/cse110-sp23-group16 | https://api.github.com/repos/cse110-sp23-group16/cse110-sp23-group16 | opened | Generate responses for each category | feature-dev-code | **Give a detailed description on the tasks and lay out each expectation for that task in a clear and concise manner**
_(description)_
Fixed number of responses 48 for each category
**ETA: give a rough time estimate to complete this issue**
1-2 hours
**Additional Information?**
| 1.0 | Generate responses for each category - **Give a detailed description on the tasks and lay out each expectation for that task in a clear and concise manner**
_(description)_
Fixed number of responses 48 for each category
**ETA: give a rough time estimate to complete this issue**
1-2 hours
**Additional Information?**
| non_priority | generate responses for each category give a detailed description on the tasks and lay out each expectation for that task in a clear and concise manner description fixed number of responses for each category eta give a rough time estimate to complete this issue hours additional information | 0 |
290,556 | 25,075,737,501 | IssuesEvent | 2022-11-07 15:21:57 | eclipse-openj9/openj9 | https://api.github.com/repos/eclipse-openj9/openj9 | opened | known but unhandled frame type com.ibm.j9ddr.vm29.pointer.U8Pointer @ 0x00000005 | comp:vm test failure | https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_special.system_s390x_linux_Personal_testList_0/85
MiniMix_3h_0
https://openj9-artifactory.osuosl.org/artifactory/ci-openj9/Test/Test_openjdk11_j9_special.system_s390x_linux_Personal_testList_0/85/system_test_output.tar.gz
Trying to look at stacks in the above core file, the following occurs.
```
!stack 0x01df3d00
<1df3d00> known but unhandled frame type com.ibm.j9ddr.vm29.pointer.U8Pointer @ 0x00000005
FAULT FAULT FAULT FAULT FAULT FAULT FAULT FAULT FAULT FAULT FAULT FAULT FAULT FAULT FAULT FAULT
...
``` | 1.0 | known but unhandled frame type com.ibm.j9ddr.vm29.pointer.U8Pointer @ 0x00000005 - https://openj9-jenkins.osuosl.org/job/Test_openjdk11_j9_special.system_s390x_linux_Personal_testList_0/85
MiniMix_3h_0
https://openj9-artifactory.osuosl.org/artifactory/ci-openj9/Test/Test_openjdk11_j9_special.system_s390x_linux_Personal_testList_0/85/system_test_output.tar.gz
Trying to look at stacks in the above core file, the following occurs.
```
!stack 0x01df3d00
<1df3d00> known but unhandled frame type com.ibm.j9ddr.vm29.pointer.U8Pointer @ 0x00000005
FAULT FAULT FAULT FAULT FAULT FAULT FAULT FAULT FAULT FAULT FAULT FAULT FAULT FAULT FAULT FAULT
...
``` | non_priority | known but unhandled frame type com ibm pointer minimix trying to look at stacks in the above core file the following occurs stack known but unhandled frame type com ibm pointer fault fault fault fault fault fault fault fault fault fault fault fault fault fault fault fault | 0 |
27,407 | 11,484,735,694 | IssuesEvent | 2020-02-11 05:00:42 | istio/istio | https://api.github.com/repos/istio/istio | closed | Build stand-alone Citadel | area/security kind/enhancement lifecycle/stale | **Describe the feature request**
Remove the dependency on Kubernetes API server from Citadel.
Such stand-alone Citadel is needed by our new test framework, which is able to run every component in local environment as a process.
https://github.com/istio/istio/issues/9177 | True | Build stand-alone Citadel - **Describe the feature request**
Remove the dependency on Kubernetes API server from Citadel.
Such stand-alone Citadel is needed by our new test framework, which is able to run every component in local environment as a process.
https://github.com/istio/istio/issues/9177 | non_priority | build stand alone citadel describe the feature request remove the dependency on kubernetes api server from citadel such stand alone citadel is needed by our new test framework which is able to run every component in local environment as a process | 0 |
2,382 | 2,725,362,897 | IssuesEvent | 2015-04-14 23:30:31 | NICMx/NAT64 | https://api.github.com/repos/NICMx/NAT64 | closed | `--session --display` can loop infinitely | Bug (non-critical) Coded (needs merge) | While sessions are being printed, sometimes a group of them will appear over and over again. This can be stopped by Ctrl+C'ing. Might cause a crash if it's done concurrently with a `--session --flush` (thankfully, this requires privileges).
It seems to happen at random, but only when there are enough sessions to not fit in a single Netlink message (200+). The more sessions, the more likely the bug will happen.
If a hunch I have is correct, this bug will have another consequence: [`--address-dependent-filtering`](http://jool.mx/usr-flags-global.html#address-dependent-filtering) ON will often behave as if it were OFF. Again, the more sessions, the more likely this will happen, though in this case it will be much, much more likely.
Stateful NAT64 only, 3.3.1 and 3.2.3.
Thanks to Edgar Rodríguez Bernal for reporting this. | 1.0 | `--session --display` can loop infinitely - While sessions are being printed, sometimes a group of them will appear over and over again. This can be stopped by Ctrl+C'ing. Might cause a crash if it's done concurrently with a `--session --flush` (thankfully, this requires privileges).
It seems to happen at random, but only when there are enough sessions to not fit in a single Netlink message (200+). The more sessions, the more likely the bug will happen.
If a hunch I have is correct, this bug will have another consequence: [`--address-dependent-filtering`](http://jool.mx/usr-flags-global.html#address-dependent-filtering) ON will often behave as if it were OFF. Again, the more sessions, the more likely this will happen, though in this case it will be much, much more likely.
Stateful NAT64 only, 3.3.1 and 3.2.3.
Thanks to Edgar Rodríguez Bernal for reporting this. | non_priority | session display can loop infinitely while sessions are being printed sometimes a group of them will appear over and over again this can be stopped by ctrl c ing might cause a crash if it s done concurrently with a session flush thankfully this requires privileges it seems to happen at random but only when there are enough sessions to not fit in a single netlink message the more sessions the more likely the bug will happen if a hunch i have is correct this bug will have another consequence on will often behave as if it were off again the more sessions the more likely this will happen though in this case it will be much much more likely stateful only and thanks to edgar rodríguez bernal for reporting this | 0 |
51,903 | 12,826,694,130 | IssuesEvent | 2020-07-06 17:01:33 | mozilla-mobile/fenix | https://api.github.com/repos/mozilla-mobile/fenix | closed | [Bug] beta fennec bustage | eng:automation eng:build needs:triage 🐞 bug | https://treeherder.mozilla.org/logviewer.html#?job_id=285659523&repo=fenix
This is from #7806 / https://github.com/mozilla-mobile/fenix/commit/02b4582c8d2c425b1bcf83fd0956d17425d5c7e0
[task 2020-01-20T18:09:00.228Z] > Task :app:processGeckoBetaFennecBetaResources
[task 2020-01-20T18:09:30.228Z] > Task :app:compileGeckoBetaFennecBetaKotlin
[task 2020-01-20T18:09:34.828Z] e: /builds/worker/checkouts/src/app/src/migration/java/org/mozilla/fenix/MigratingFenixApplication.kt: (58, 35): No value passed for parameter 'store'
[task 2020-01-20T18:09:34.828Z]
[task 2020-01-20T18:09:34.828Z] > Task :app:compileGeckoBetaFennecBetaKotlin FAILED | 1.0 | [Bug] beta fennec bustage - https://treeherder.mozilla.org/logviewer.html#?job_id=285659523&repo=fenix
This is from #7806 / https://github.com/mozilla-mobile/fenix/commit/02b4582c8d2c425b1bcf83fd0956d17425d5c7e0
[task 2020-01-20T18:09:00.228Z] > Task :app:processGeckoBetaFennecBetaResources
[task 2020-01-20T18:09:30.228Z] > Task :app:compileGeckoBetaFennecBetaKotlin
[task 2020-01-20T18:09:34.828Z] e: /builds/worker/checkouts/src/app/src/migration/java/org/mozilla/fenix/MigratingFenixApplication.kt: (58, 35): No value passed for parameter 'store'
[task 2020-01-20T18:09:34.828Z]
[task 2020-01-20T18:09:34.828Z] > Task :app:compileGeckoBetaFennecBetaKotlin FAILED | non_priority | beta fennec bustage this is from task app processgeckobetafennecbetaresources task app compilegeckobetafennecbetakotlin e builds worker checkouts src app src migration java org mozilla fenix migratingfenixapplication kt no value passed for parameter store task app compilegeckobetafennecbetakotlin failed | 0 |
259,108 | 22,390,816,581 | IssuesEvent | 2022-06-17 07:29:42 | proarc/proarc | https://api.github.com/repos/proarc/proarc | closed | Řazení titulů v úložišti - zaškrtávátko "zapamatovat" ve 3.6.1 nefunguje | 1 chyba 7 návrh na zavření 6 k testování Release-3.6.2 | Ve verzi 3.6.1 asi přestalo při hledání v úložišti fungovat zaškrtávátko "zapamatovat". Když zkusím změnit řazení vzestupně na sestupně ve verzi 3.6, volbu si po odhlášení pamatuje, ve 3.6.1 ale už ne.
V podstatě asi nechápu, proč vzestupně má tady přednost před sestupně (praktické využití vzestupného vidím jen u řazení podle abecedy při hledání podle názvu), většinou se ale myslím orientujeme podle data (vytvoření/změny), a tam má v 99% případů smysl sestupné řazení. Ale budiž, pokud si to bude pamatovat volbu. Jenže u verze 3.6.1 tohle asi vypadlo, pokud to teda není úmyslně.
Můžeš se na to Lukáši prosím mrknout? | 1.0 | Řazení titulů v úložišti - zaškrtávátko "zapamatovat" ve 3.6.1 nefunguje - Ve verzi 3.6.1 asi přestalo při hledání v úložišti fungovat zaškrtávátko "zapamatovat". Když zkusím změnit řazení vzestupně na sestupně ve verzi 3.6, volbu si po odhlášení pamatuje, ve 3.6.1 ale už ne.
V podstatě asi nechápu, proč vzestupně má tady přednost před sestupně (praktické využití vzestupného vidím jen u řazení podle abecedy při hledání podle názvu), většinou se ale myslím orientujeme podle data (vytvoření/změny), a tam má v 99% případů smysl sestupné řazení. Ale budiž, pokud si to bude pamatovat volbu. Jenže u verze 3.6.1 tohle asi vypadlo, pokud to teda není úmyslně.
Můžeš se na to Lukáši prosím mrknout? | non_priority | řazení titulů v úložišti zaškrtávátko zapamatovat ve nefunguje ve verzi asi přestalo při hledání v úložišti fungovat zaškrtávátko zapamatovat když zkusím změnit řazení vzestupně na sestupně ve verzi volbu si po odhlášení pamatuje ve ale už ne v podstatě asi nechápu proč vzestupně má tady přednost před sestupně praktické využití vzestupného vidím jen u řazení podle abecedy při hledání podle názvu většinou se ale myslím orientujeme podle data vytvoření změny a tam má v případů smysl sestupné řazení ale budiž pokud si to bude pamatovat volbu jenže u verze tohle asi vypadlo pokud to teda není úmyslně můžeš se na to lukáši prosím mrknout | 0 |
2,214 | 2,588,181,340 | IssuesEvent | 2015-02-17 23:10:22 | marklogic/RunDMC | https://api.github.com/repos/marklogic/RunDMC | closed | Body tags do not seem to be transforming correctly in page.xsl | test | We are seeing an issue in our dev site where Body tags from frame are not being transformed correctly. If you look at this page (using today's zip, although I don't think that matters):
/guide/temporal/temporal-quick-start#id_19340
You will see the problem. The text "JavaScript Example" is with the previous paragraph. The xml seems correct here:
```<h3>
<a href="#id_19340" class="sectionLink">
Create the Range Indexes for the Valid and System Axes
</a>
</h3>
<Body>
<a id="id_pgfId-1070770">
</a>
The valid and system axis each make use of
<code>
dateTime
</code>
range indexes that define the start and end times. For example, the following query creates the element range indexes to be used to create the valid and system axes.
</Body>
<Body>
<a id="id_pgfId-1074121">
</a>
JavaScript Example:
</Body>
<pre>
var admin = require("/MarkLogic/admin.xqy");
var config = admin.getConfiguration();
var dbid = xdmp.database("Documents");
var validStart = admin.databaseRangeElementIndex(
"dateTime", "", "validStart", "", fn.false() );
var validEnd = admin.databaseRangeElementIndex(
"dateTime", "", "validEnd", "", fn.false() );
var systemStart = admin.databaseRangeElementIndex(
"dateTime", "", "systemStart", "", fn.false() );
var systemEnd = admin.databaseRangeElementIndex(
"dateTime", "", "systemEnd", "", fn.false() );
config = admin.databaseAddRangeElementIndex(config, dbid, validStart);
config = admin.databaseAddRangeElementIndex(config, dbid, validEnd);
config = admin.databaseAddRangeElementIndex(config, dbid, systemStart);
config = admin.databaseAddRangeElementIndex(config, dbid, systemEnd);
admin.saveConfiguration(config);
</pre>```
Any idea what might be going wrong? This seems correct on the production code, so maybe it is something relative recent? | 1.0 | Body tags do not seem to be transforming correctly in page.xsl - We are seeing an issue in our dev site where Body tags from frame are not being transformed correctly. If you look at this page (using today's zip, although I don't think that matters):
/guide/temporal/temporal-quick-start#id_19340
You will see the problem. The text "JavaScript Example" is with the previous paragraph. The xml seems correct here:
```<h3>
<a href="#id_19340" class="sectionLink">
Create the Range Indexes for the Valid and System Axes
</a>
</h3>
<Body>
<a id="id_pgfId-1070770">
</a>
The valid and system axis each make use of
<code>
dateTime
</code>
range indexes that define the start and end times. For example, the following query creates the element range indexes to be used to create the valid and system axes.
</Body>
<Body>
<a id="id_pgfId-1074121">
</a>
JavaScript Example:
</Body>
<pre>
var admin = require("/MarkLogic/admin.xqy");
var config = admin.getConfiguration();
var dbid = xdmp.database("Documents");
var validStart = admin.databaseRangeElementIndex(
"dateTime", "", "validStart", "", fn.false() );
var validEnd = admin.databaseRangeElementIndex(
"dateTime", "", "validEnd", "", fn.false() );
var systemStart = admin.databaseRangeElementIndex(
"dateTime", "", "systemStart", "", fn.false() );
var systemEnd = admin.databaseRangeElementIndex(
"dateTime", "", "systemEnd", "", fn.false() );
config = admin.databaseAddRangeElementIndex(config, dbid, validStart);
config = admin.databaseAddRangeElementIndex(config, dbid, validEnd);
config = admin.databaseAddRangeElementIndex(config, dbid, systemStart);
config = admin.databaseAddRangeElementIndex(config, dbid, systemEnd);
admin.saveConfiguration(config);
</pre>```
Any idea what might be going wrong? This seems correct on the production code, so maybe it is something relative recent? | non_priority | body tags do not seem to be transforming correctly in page xsl we are seeing an issue in our dev site where body tags from frame are not being transformed correctly if you look at this page using today s zip although i don t think that matters guide temporal temporal quick start id you will see the problem the text javascript example is with the previous paragraph the xml seems correct here create the range indexes for the valid and system axes the valid and system axis each make use of datetime range indexes that define the start and end times for example the following query creates the element range indexes to be used to create the valid and system axes javascript example var admin require marklogic admin xqy var config admin getconfiguration var dbid xdmp database documents var validstart admin databaserangeelementindex datetime validstart fn false var validend admin databaserangeelementindex datetime validend fn false var systemstart admin databaserangeelementindex datetime systemstart fn false var systemend admin databaserangeelementindex datetime systemend fn false config admin databaseaddrangeelementindex config dbid validstart config admin databaseaddrangeelementindex config dbid validend config admin databaseaddrangeelementindex config dbid systemstart config admin databaseaddrangeelementindex config dbid systemend admin saveconfiguration config any idea what might be going wrong this seems correct on the production code so maybe it is something relative recent | 0 |
259,128 | 19,587,212,046 | IssuesEvent | 2022-01-05 08:40:12 | schmelto/abap | https://api.github.com/repos/schmelto/abap | opened | [Feat]: Change SAP Job | documentation enhancement | ### Feature request
Transaction: `SM37`
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct | 1.0 | [Feat]: Change SAP Job - ### Feature request
Transaction: `SM37`
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct | non_priority | change sap job feature request transaction code of conduct i agree to follow this project s code of conduct | 0 |
53,747 | 11,135,541,817 | IssuesEvent | 2019-12-20 14:36:40 | languagetool-org/languagetool | https://api.github.com/repos/languagetool-org/languagetool | opened | [en] EN_UNPAIRED_BRACKETS | English code/java enhancement | 
Rather than having 2 messages for unpaired symbols, could the rule be made to identify the first closing quote as incorrect and could the rule suggest the correct opening quote? | 1.0 | [en] EN_UNPAIRED_BRACKETS - 
Rather than having 2 messages for unpaired symbols, could the rule be made to identify the first closing quote as incorrect and could the rule suggest the correct opening quote? | non_priority | en unpaired brackets rather than having messages for unpaired symbols could the rule be made to identify the first closing quote as incorrect and could the rule suggest the correct opening quote | 0 |
78,137 | 22,151,500,295 | IssuesEvent | 2022-06-03 17:20:18 | apache/beam | https://api.github.com/repos/apache/beam | opened | Consider minimization on shaded jars | P3 improvement build-system | Some of our modules shade and relocate Guava as part of their build, this adds a considerable amount to their file size, even though they do not use every single class in Guava's jar.
maven shade-plugin solves this by minimization which only shades classes which are in use in the module into the jar.
There are a few issues with configuring minimzation for our shaded modules currently:
1. There is a bug in shade-plugin where if minimization is declared on a project with pom packaging it fails. I have created a [ticket](https://issues.apache.org/jira/browse/MSHADE-253) and [PR](https://github.com/apache/maven-plugins/pull/107) with a fix for this but could take a while before it is available to us (The fix has been merged but not released yet).
2. Minimization on all of our modules adds a significant amount of build time, which we wish to avoid. (Up from 02:30 mins for a build of the entire project (skipping tests) on a Macbook pro laptop to over 5 mins)
Imported from Jira [BEAM-1720](https://issues.apache.org/jira/browse/BEAM-1720). Original Jira may contain additional context.
Reported by: aviemzur. | 1.0 | Consider minimization on shaded jars - Some of our modules shade and relocate Guava as part of their build, this adds a considerable amount to their file size, even though they do not use every single class in Guava's jar.
maven shade-plugin solves this by minimization which only shades classes which are in use in the module into the jar.
There are a few issues with configuring minimzation for our shaded modules currently:
1. There is a bug in shade-plugin where if minimization is declared on a project with pom packaging it fails. I have created a [ticket](https://issues.apache.org/jira/browse/MSHADE-253) and [PR](https://github.com/apache/maven-plugins/pull/107) with a fix for this but could take a while before it is available to us (The fix has been merged but not released yet).
2. Minimization on all of our modules adds a significant amount of build time, which we wish to avoid. (Up from 02:30 mins for a build of the entire project (skipping tests) on a Macbook pro laptop to over 5 mins)
Imported from Jira [BEAM-1720](https://issues.apache.org/jira/browse/BEAM-1720). Original Jira may contain additional context.
Reported by: aviemzur. | non_priority | consider minimization on shaded jars some of our modules shade and relocate guava as part of their build this adds a considerable amount to their file size even though they do not use every single class in guava s jar maven shade plugin solves this by minimization which only shades classes which are in use in the module into the jar there are a few issues with configuring minimzation for our shaded modules currently there is a bug in shade plugin where if minimization is declared on a project with pom packaging it fails i have created a and with a fix for this but could take a while before it is available to us the fix has been merged but not released yet minimization on all of our modules adds a significant amount of build time which we wish to avoid up from mins for a build of the entire project skipping tests on a macbook pro laptop to over mins imported from jira original jira may contain additional context reported by aviemzur | 0 |
206,363 | 15,727,643,719 | IssuesEvent | 2021-03-29 12:56:05 | elastic/kibana | https://api.github.com/repos/elastic/kibana | closed | Failing test: X-Pack OpenID Connect API Integration Tests (Implicit Flow).x-pack/test/oidc_api_integration/apis/implicit_flow/oidc_auth·ts - apis OpenID Connect Implicit Flow authentication finishing handshake should succeed if both the OpenID Connect response and the cookie are provided | Team:Security failed-test skipped-test | A test failed on a tracked branch
```
Error: expected 302 "Found", got 401 "Unauthorized"
at Test._assertStatus (/var/lib/jenkins/workspace/elastic+kibana+7.x/JOB/x-pack-ciGroup6/node/linux-immutable/kibana/node_modules/supertest/lib/test.js:268:12)
at Test._assertFunction (/var/lib/jenkins/workspace/elastic+kibana+7.x/JOB/x-pack-ciGroup6/node/linux-immutable/kibana/node_modules/supertest/lib/test.js:283:11)
at Test.assert (/var/lib/jenkins/workspace/elastic+kibana+7.x/JOB/x-pack-ciGroup6/node/linux-immutable/kibana/node_modules/supertest/lib/test.js:173:18)
at assert (/var/lib/jenkins/workspace/elastic+kibana+7.x/JOB/x-pack-ciGroup6/node/linux-immutable/kibana/node_modules/supertest/lib/test.js:131:12)
at /var/lib/jenkins/workspace/elastic+kibana+7.x/JOB/x-pack-ciGroup6/node/linux-immutable/kibana/node_modules/supertest/lib/test.js:128:5
at Test.Request.callback (/var/lib/jenkins/workspace/elastic+kibana+7.x/JOB/x-pack-ciGroup6/node/linux-immutable/kibana/node_modules/superagent/lib/node/index.js:718:3)
at parser (/var/lib/jenkins/workspace/elastic+kibana+7.x/JOB/x-pack-ciGroup6/node/linux-immutable/kibana/node_modules/superagent/lib/node/index.js:906:18)
at IncomingMessage.res.on (/var/lib/jenkins/workspace/elastic+kibana+7.x/JOB/x-pack-ciGroup6/node/linux-immutable/kibana/node_modules/superagent/lib/node/parsers/json.js:19:7)
at endReadableNT (_stream_readable.js:1103:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
```
First failure: [Jenkins Build](https://kibana-ci.elastic.co/job/elastic+kibana+7.x/JOB=x-pack-ciGroup6,node=linux-immutable/1833/)
<!-- kibanaCiData = {"failed-test":{"test.class":"X-Pack OpenID Connect API Integration Tests (Implicit Flow).x-pack/test/oidc_api_integration/apis/implicit_flow/oidc_auth·ts","test.name":"apis OpenID Connect Implicit Flow authentication finishing handshake should succeed if both the OpenID Connect response and the cookie are provided","test.failCount":5}} --> | 2.0 | Failing test: X-Pack OpenID Connect API Integration Tests (Implicit Flow).x-pack/test/oidc_api_integration/apis/implicit_flow/oidc_auth·ts - apis OpenID Connect Implicit Flow authentication finishing handshake should succeed if both the OpenID Connect response and the cookie are provided - A test failed on a tracked branch
```
Error: expected 302 "Found", got 401 "Unauthorized"
at Test._assertStatus (/var/lib/jenkins/workspace/elastic+kibana+7.x/JOB/x-pack-ciGroup6/node/linux-immutable/kibana/node_modules/supertest/lib/test.js:268:12)
at Test._assertFunction (/var/lib/jenkins/workspace/elastic+kibana+7.x/JOB/x-pack-ciGroup6/node/linux-immutable/kibana/node_modules/supertest/lib/test.js:283:11)
at Test.assert (/var/lib/jenkins/workspace/elastic+kibana+7.x/JOB/x-pack-ciGroup6/node/linux-immutable/kibana/node_modules/supertest/lib/test.js:173:18)
at assert (/var/lib/jenkins/workspace/elastic+kibana+7.x/JOB/x-pack-ciGroup6/node/linux-immutable/kibana/node_modules/supertest/lib/test.js:131:12)
at /var/lib/jenkins/workspace/elastic+kibana+7.x/JOB/x-pack-ciGroup6/node/linux-immutable/kibana/node_modules/supertest/lib/test.js:128:5
at Test.Request.callback (/var/lib/jenkins/workspace/elastic+kibana+7.x/JOB/x-pack-ciGroup6/node/linux-immutable/kibana/node_modules/superagent/lib/node/index.js:718:3)
at parser (/var/lib/jenkins/workspace/elastic+kibana+7.x/JOB/x-pack-ciGroup6/node/linux-immutable/kibana/node_modules/superagent/lib/node/index.js:906:18)
at IncomingMessage.res.on (/var/lib/jenkins/workspace/elastic+kibana+7.x/JOB/x-pack-ciGroup6/node/linux-immutable/kibana/node_modules/superagent/lib/node/parsers/json.js:19:7)
at endReadableNT (_stream_readable.js:1103:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
```
First failure: [Jenkins Build](https://kibana-ci.elastic.co/job/elastic+kibana+7.x/JOB=x-pack-ciGroup6,node=linux-immutable/1833/)
<!-- kibanaCiData = {"failed-test":{"test.class":"X-Pack OpenID Connect API Integration Tests (Implicit Flow).x-pack/test/oidc_api_integration/apis/implicit_flow/oidc_auth·ts","test.name":"apis OpenID Connect Implicit Flow authentication finishing handshake should succeed if both the OpenID Connect response and the cookie are provided","test.failCount":5}} --> | non_priority | failing test x pack openid connect api integration tests implicit flow x pack test oidc api integration apis implicit flow oidc auth·ts apis openid connect implicit flow authentication finishing handshake should succeed if both the openid connect response and the cookie are provided a test failed on a tracked branch error expected found got unauthorized at test assertstatus var lib jenkins workspace elastic kibana x job x pack node linux immutable kibana node modules supertest lib test js at test assertfunction var lib jenkins workspace elastic kibana x job x pack node linux immutable kibana node modules supertest lib test js at test assert var lib jenkins workspace elastic kibana x job x pack node linux immutable kibana node modules supertest lib test js at assert var lib jenkins workspace elastic kibana x job x pack node linux immutable kibana node modules supertest lib test js at var lib jenkins workspace elastic kibana x job x pack node linux immutable kibana node modules supertest lib test js at test request callback var lib jenkins workspace elastic kibana x job x pack node linux immutable kibana node modules superagent lib node index js at parser var lib jenkins workspace elastic kibana x job x pack node linux immutable kibana node modules superagent lib node index js at incomingmessage res on var lib jenkins workspace elastic kibana x job x pack node linux immutable kibana node modules superagent lib node parsers json js at endreadablent stream readable js at process tickcallback internal process next tick js first failure | 0 |
10,768 | 7,303,463,937 | IssuesEvent | 2018-02-27 13:14:00 | JuliaReach/Reachability.jl | https://api.github.com/repos/JuliaReach/Reachability.jl | opened | Interval arithmetic implementation for 1D blocks | feature performance | This is both more efficient and sound.
Preliminary: first part of #73 | True | Interval arithmetic implementation for 1D blocks - This is both more efficient and sound.
Preliminary: first part of #73 | non_priority | interval arithmetic implementation for blocks this is both more efficient and sound preliminary first part of | 0 |
83,000 | 23,938,382,614 | IssuesEvent | 2022-09-11 15:02:25 | wxWidgets/wxWidgets | https://api.github.com/repos/wxWidgets/wxWidgets | closed | protocol\ftp.h doesn't compile (and needs object.h) | build | When building an application using Visual Studio I get errors like these where I've used protocol\ftp.h:
...\wx\sckaddr.h(30,1): error C2504: 'wxObject': base class undefined
...\wx\sckaddr.h(67,44): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
...\wx\sckaddr.h(67,44): warning C4183: 'wxDECLARE_ABSTRACT_CLASS': missing return type; assumed to be a member function returning 'int'
However, if I inlcude wx\object.h before wx\protocol\ftp.h it compiles fine.
**Platform and version information**
- wxWidgets 3.2.0
- Windows Version 10.0.19044 Build 19044
| 1.0 | protocol\ftp.h doesn't compile (and needs object.h) - When building an application using Visual Studio I get errors like these where I've used protocol\ftp.h:
...\wx\sckaddr.h(30,1): error C2504: 'wxObject': base class undefined
...\wx\sckaddr.h(67,44): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
...\wx\sckaddr.h(67,44): warning C4183: 'wxDECLARE_ABSTRACT_CLASS': missing return type; assumed to be a member function returning 'int'
However, if I inlcude wx\object.h before wx\protocol\ftp.h it compiles fine.
**Platform and version information**
- wxWidgets 3.2.0
- Windows Version 10.0.19044 Build 19044
| non_priority | protocol ftp h doesn t compile and needs object h when building an application using visual studio i get errors like these where i ve used protocol ftp h wx sckaddr h error wxobject base class undefined wx sckaddr h error missing type specifier int assumed note c does not support default int wx sckaddr h warning wxdeclare abstract class missing return type assumed to be a member function returning int however if i inlcude wx object h before wx protocol ftp h it compiles fine platform and version information wxwidgets windows version build | 0 |
97,174 | 10,982,349,375 | IssuesEvent | 2019-12-01 06:42:26 | Azure/OpenShift | https://api.github.com/repos/Azure/OpenShift | closed | Wrong documentation for internal Load Balancers | documentation | Not sure, if this is the right place for documentation feedback on the Red Hat side, but the [docs for creating an internal load balancer](https://docs.openshift.com/aro/getting_started/access_your_services.html#create-an-internal-only-tcp-service) have a mistake!
Instead of `service.beta.kubernetes.io/azure-load-balancer-internal: 0.0.0.0/0` it should be `service.beta.kubernetes.io/azure-load-balancer-internal: \"true\"`.
The requested change ist moving from this
```bash
$ oc expose dc httpd-example --type=LoadBalancer --name=internal-lb --dry-run -o yaml | awk '1;/metadata:/{ print " annotations:\n service.beta.kubernetes.io/azure-load-balancer-internal: 0.0.0.0/0" }' | oc create -f -
service/internal-lb exposed
```
to that
```bash
$ oc expose dc httpd-example --type=LoadBalancer --name=internal-lb --dry-run -o yaml | awk '1;/metadata:/{ print " annotations:\n service.beta.kubernetes.io/azure-load-balancer-internal: \"true\"" }' | oc create -f -
service/internal-lb exposed
```
If this is not the right place for that kind of feedback, can someone point me to the correct feedback channel? | 1.0 | Wrong documentation for internal Load Balancers - Not sure, if this is the right place for documentation feedback on the Red Hat side, but the [docs for creating an internal load balancer](https://docs.openshift.com/aro/getting_started/access_your_services.html#create-an-internal-only-tcp-service) have a mistake!
Instead of `service.beta.kubernetes.io/azure-load-balancer-internal: 0.0.0.0/0` it should be `service.beta.kubernetes.io/azure-load-balancer-internal: \"true\"`.
The requested change ist moving from this
```bash
$ oc expose dc httpd-example --type=LoadBalancer --name=internal-lb --dry-run -o yaml | awk '1;/metadata:/{ print " annotations:\n service.beta.kubernetes.io/azure-load-balancer-internal: 0.0.0.0/0" }' | oc create -f -
service/internal-lb exposed
```
to that
```bash
$ oc expose dc httpd-example --type=LoadBalancer --name=internal-lb --dry-run -o yaml | awk '1;/metadata:/{ print " annotations:\n service.beta.kubernetes.io/azure-load-balancer-internal: \"true\"" }' | oc create -f -
service/internal-lb exposed
```
If this is not the right place for that kind of feedback, can someone point me to the correct feedback channel? | non_priority | wrong documentation for internal load balancers not sure if this is the right place for documentation feedback on the red hat side but the have a mistake instead of service beta kubernetes io azure load balancer internal it should be service beta kubernetes io azure load balancer internal true the requested change ist moving from this bash oc expose dc httpd example type loadbalancer name internal lb dry run o yaml awk metadata print annotations n service beta kubernetes io azure load balancer internal oc create f service internal lb exposed to that bash oc expose dc httpd example type loadbalancer name internal lb dry run o yaml awk metadata print annotations n service beta kubernetes io azure load balancer internal true oc create f service internal lb exposed if this is not the right place for that kind of feedback can someone point me to the correct feedback channel | 0 |
100,036 | 30,602,065,129 | IssuesEvent | 2023-07-22 14:11:57 | chipsalliance/verible | https://api.github.com/repos/chipsalliance/verible | closed | fatal error: 'stdio_ext.h' file not found | build system | **Describe the bug**
```
$ CXXFLAGS="-sta=c++20" bazel build -c opt //... --cxxopt=-std=c++20
INFO: Build option --cxxopt has changed, discarding analysis cache.
WARNING: Download from https://mirror.bazel.build/github.com/westes/flex/releases/download/v2.6.4/flex-2.6.4.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
INFO: Analyzed 1893 targets (0 packages loaded, 6898 targets configured).
INFO: Found 1893 targets...
ERROR: /usr/home/yuri/.cache/bazel/_bazel_yuri/c8363c06afa4c26207790ac1c5fde5cb/external/m4_v1.4.18/gnulib/BUILD.bazel:205:11: Compiling gnulib/lib/close-stream.c [for host] failed: (Exit 1): clang failed: error executing command /usr/bin/clang -U_FORTIFY_SOURCE '-D_FORTIFY_SOURCE=1' -fstack-protector -Wall -fno-omit-frame-pointer -g0 -O2 -DNDEBUG -ffunction-sections -fdata-sections -MD -MF ... (remaining 22 arguments skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
In file included from external/m4_v1.4.18/gnulib/lib/close-stream.c:25:
external/m4_v1.4.18/gnulib/lib/fpending.h:24:11: fatal error: 'stdio_ext.h' file not found
# include <stdio_ext.h>
^~~~~~~~~~~~~
1 error generated.
INFO: Elapsed time: 92.447s, Critical Path: 25.33s
INFO: 503 processes: 232 internal, 271 processwrapper-sandbox.
FAILED: Build did NOT complete successfully
```
Where is ```stdio_ext.h``` described?
clang-14
bazel-5.3.0
FreeBSD 13.1
| 1.0 | fatal error: 'stdio_ext.h' file not found - **Describe the bug**
```
$ CXXFLAGS="-sta=c++20" bazel build -c opt //... --cxxopt=-std=c++20
INFO: Build option --cxxopt has changed, discarding analysis cache.
WARNING: Download from https://mirror.bazel.build/github.com/westes/flex/releases/download/v2.6.4/flex-2.6.4.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
INFO: Analyzed 1893 targets (0 packages loaded, 6898 targets configured).
INFO: Found 1893 targets...
ERROR: /usr/home/yuri/.cache/bazel/_bazel_yuri/c8363c06afa4c26207790ac1c5fde5cb/external/m4_v1.4.18/gnulib/BUILD.bazel:205:11: Compiling gnulib/lib/close-stream.c [for host] failed: (Exit 1): clang failed: error executing command /usr/bin/clang -U_FORTIFY_SOURCE '-D_FORTIFY_SOURCE=1' -fstack-protector -Wall -fno-omit-frame-pointer -g0 -O2 -DNDEBUG -ffunction-sections -fdata-sections -MD -MF ... (remaining 22 arguments skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
In file included from external/m4_v1.4.18/gnulib/lib/close-stream.c:25:
external/m4_v1.4.18/gnulib/lib/fpending.h:24:11: fatal error: 'stdio_ext.h' file not found
# include <stdio_ext.h>
^~~~~~~~~~~~~
1 error generated.
INFO: Elapsed time: 92.447s, Critical Path: 25.33s
INFO: 503 processes: 232 internal, 271 processwrapper-sandbox.
FAILED: Build did NOT complete successfully
```
Where is ```stdio_ext.h``` described?
clang-14
bazel-5.3.0
FreeBSD 13.1
| non_priority | fatal error stdio ext h file not found describe the bug cxxflags sta c bazel build c opt cxxopt std c info build option cxxopt has changed discarding analysis cache warning download from failed class java io filenotfoundexception get returned not found info analyzed targets packages loaded targets configured info found targets error usr home yuri cache bazel bazel yuri external gnulib build bazel compiling gnulib lib close stream c failed exit clang failed error executing command usr bin clang u fortify source d fortify source fstack protector wall fno omit frame pointer dndebug ffunction sections fdata sections md mf remaining arguments skipped use sandbox debug to see verbose messages from the sandbox and retain the sandbox build root for debugging in file included from external gnulib lib close stream c external gnulib lib fpending h fatal error stdio ext h file not found include error generated info elapsed time critical path info processes internal processwrapper sandbox failed build did not complete successfully where is stdio ext h described clang bazel freebsd | 0 |
112,101 | 24,233,560,388 | IssuesEvent | 2022-09-26 20:34:53 | robert-altom/test | https://api.github.com/repos/robert-altom/test | opened | Change class names to have prefix alt|altunity | bug in code review gitlab | <sub>You can find the original issue from GitLab [here](https://gitlab.com/altom/altunity/altunitytester/-/issues/240).</sub>
| 1.0 | Change class names to have prefix alt|altunity - <sub>You can find the original issue from GitLab [here](https://gitlab.com/altom/altunity/altunitytester/-/issues/240).</sub>
| non_priority | change class names to have prefix alt altunity you can find the original issue from gitlab | 0 |
110,360 | 9,442,681,267 | IssuesEvent | 2019-04-15 07:30:35 | PowerPointLabs/PowerPointLabs | https://api.github.com/repos/PowerPointLabs/PowerPointLabs | closed | ELL UT failing | a-Testing c.Bug f-eLearningLab | ## Bug Report
`IsTriggerBoxEnableChangeNotification` ELL Unit Test is failing.
#### Environment (e.g. version of Microsoft PowerPoint)
Visual Studio 2017, PPT 2016.
#### Action to fix:
Add `NotifyPropertyChanged(ELearningLabText.ExplanationItem_IsTriggerTypeComboBoxEnabled)` to `IsTriggerTypeComboBoxEnabled` , since the test modifies that value.
| 1.0 | ELL UT failing - ## Bug Report
`IsTriggerBoxEnableChangeNotification` ELL Unit Test is failing.
#### Environment (e.g. version of Microsoft PowerPoint)
Visual Studio 2017, PPT 2016.
#### Action to fix:
Add `NotifyPropertyChanged(ELearningLabText.ExplanationItem_IsTriggerTypeComboBoxEnabled)` to `IsTriggerTypeComboBoxEnabled` , since the test modifies that value.
| non_priority | ell ut failing bug report istriggerboxenablechangenotification ell unit test is failing environment e g version of microsoft powerpoint visual studio ppt action to fix add notifypropertychanged elearninglabtext explanationitem istriggertypecomboboxenabled to istriggertypecomboboxenabled since the test modifies that value | 0 |
178,911 | 13,803,794,173 | IssuesEvent | 2020-10-11 05:23:11 | ryanheise/audio_service | https://api.github.com/repos/ryanheise/audio_service | closed | AVAudioSession at start | 3 testing enhancement | <!--
PLEASE READ CAREFULLY!
FOR YOUR FEATURE REQUEST TO BE PROCESSED, YOU WILL NEED
TO FILL IN ALL SECTIONS BELOW. DON'T DELETE THE HEADINGS.
THANK YOU :-D
-->
**Is your feature request related to a problem? Please describe.**
IOS ONLY (so far)
My feature is related to an issue I am having. I start audio from another service like Spotify before I start myApp. As soon as I call start on AudioService the audio from Spotify gets paused. I believe it is due to the call to setup AVAudiosession in the plugin.
**Describe the solution you'd like**
I would like a way to override the settings of AVAudiosession setup. Or just dont set it up and provide a way to the user to provide some overrides. Perhaps as arguments to config
**Describe alternatives you've considered**
I tried to override it but it doesnt work as soon as start is called the audio from another service stops.
**Additional context**
Maybe I am doing something wrong and this is easy but any help would be greatly appreciated. I want audio to be allowed to play and mix in with audio from myApp without being stopped or paused in any way. I know the settings from AVAudioSession options but again I cant seem to find a way to make this work.
| 1.0 | AVAudioSession at start - <!--
PLEASE READ CAREFULLY!
FOR YOUR FEATURE REQUEST TO BE PROCESSED, YOU WILL NEED
TO FILL IN ALL SECTIONS BELOW. DON'T DELETE THE HEADINGS.
THANK YOU :-D
-->
**Is your feature request related to a problem? Please describe.**
IOS ONLY (so far)
My feature is related to an issue I am having. I start audio from another service like Spotify before I start myApp. As soon as I call start on AudioService the audio from Spotify gets paused. I believe it is due to the call to setup AVAudiosession in the plugin.
**Describe the solution you'd like**
I would like a way to override the settings of AVAudiosession setup. Or just dont set it up and provide a way to the user to provide some overrides. Perhaps as arguments to config
**Describe alternatives you've considered**
I tried to override it but it doesnt work as soon as start is called the audio from another service stops.
**Additional context**
Maybe I am doing something wrong and this is easy but any help would be greatly appreciated. I want audio to be allowed to play and mix in with audio from myApp without being stopped or paused in any way. I know the settings from AVAudioSession options but again I cant seem to find a way to make this work.
| non_priority | avaudiosession at start please read carefully for your feature request to be processed you will need to fill in all sections below don t delete the headings thank you d is your feature request related to a problem please describe ios only so far my feature is related to an issue i am having i start audio from another service like spotify before i start myapp as soon as i call start on audioservice the audio from spotify gets paused i believe it is due to the call to setup avaudiosession in the plugin describe the solution you d like i would like a way to override the settings of avaudiosession setup or just dont set it up and provide a way to the user to provide some overrides perhaps as arguments to config describe alternatives you ve considered i tried to override it but it doesnt work as soon as start is called the audio from another service stops additional context maybe i am doing something wrong and this is easy but any help would be greatly appreciated i want audio to be allowed to play and mix in with audio from myapp without being stopped or paused in any way i know the settings from avaudiosession options but again i cant seem to find a way to make this work | 0 |
4,854 | 3,466,192,398 | IssuesEvent | 2015-12-22 01:18:17 | WPN-XM/WPN-XM | https://api.github.com/repos/WPN-XM/WPN-XM | closed | create build toolchain for documentation | build tools documentation feature | The goal is, that the documentation for the stack, it's components and configuration is online and offline available.
"You can find the User Guide in the docs folder inside the WPN-XM directory and online."
**Create build toolchain for documentation**
- [x] `server\docs`
- Done: https://github.com/WPN-XM/WPN-XM/commit/5a0b0823105967450cb23624ca33e78f6dcb5d01
- [x] create new repository for documentation
- Done: https://github.com/WPN-XM/docs
- [x] find a tool and toolchain
- [x] Asciidoc?
- [ ] PanDoc?
- [ ] Sphinx? (see Symfony Framework)
- [x] I've decided for Asciidoctor
- [x] create a book project structure for a multi-language book
- [x] add docu generation to the build script
- [x] use book style for PDF
- [x] find a "nice" asciidoc style for rendering the HTML pages with TOC
- [x] support multiple formats
- [x] .html - `server\docs\index.html`
- http://wpn-xm.github.io/docs/manual/en/
- [ ] .chm - `server\docs\wpn-xm.chm`
- [x] .pdf
- http://wpn-xm.github.io/docs/manual/en/book.pdf
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/4843208-stack-documentation?utm_campaign=plugin&utm_content=tracker%2F164029&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F164029&utm_medium=issues&utm_source=github).
</bountysource-plugin> | 1.0 | create build toolchain for documentation - The goal is, that the documentation for the stack, it's components and configuration is online and offline available.
"You can find the User Guide in the docs folder inside the WPN-XM directory and online."
**Create build toolchain for documentation**
- [x] `server\docs`
- Done: https://github.com/WPN-XM/WPN-XM/commit/5a0b0823105967450cb23624ca33e78f6dcb5d01
- [x] create new repository for documentation
- Done: https://github.com/WPN-XM/docs
- [x] find a tool and toolchain
- [x] Asciidoc?
- [ ] PanDoc?
- [ ] Sphinx? (see Symfony Framework)
- [x] I've decided for Asciidoctor
- [x] create a book project structure for a multi-language book
- [x] add docu generation to the build script
- [x] use book style for PDF
- [x] find a "nice" asciidoc style for rendering the HTML pages with TOC
- [x] support multiple formats
- [x] .html - `server\docs\index.html`
- http://wpn-xm.github.io/docs/manual/en/
- [ ] .chm - `server\docs\wpn-xm.chm`
- [x] .pdf
- http://wpn-xm.github.io/docs/manual/en/book.pdf
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/4843208-stack-documentation?utm_campaign=plugin&utm_content=tracker%2F164029&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F164029&utm_medium=issues&utm_source=github).
</bountysource-plugin> | non_priority | create build toolchain for documentation the goal is that the documentation for the stack it s components and configuration is online and offline available you can find the user guide in the docs folder inside the wpn xm directory and online create build toolchain for documentation server docs done create new repository for documentation done find a tool and toolchain asciidoc pandoc sphinx see symfony framework i ve decided for asciidoctor create a book project structure for a multi language book add docu generation to the build script use book style for pdf find a nice asciidoc style for rendering the html pages with toc support multiple formats html server docs index html chm server docs wpn xm chm pdf want to back this issue we accept bounties via | 0 |
197,630 | 14,936,772,889 | IssuesEvent | 2021-01-25 13:49:29 | eclipse/openj9 | https://api.github.com/repos/eclipse/openj9 | opened | JDK16 java/foreign/TestNative.java - UnsatisfiedLinkError: jdk/internal/foreign/abi/ProgrammableInvoker.registerNatives()V | test failure | Failure link
------------
From an internal build `openjdk16-pipeline #3/jdk16-linux-x64-openj9 #1/Test_openjdk16_j9_sanity.openjdk_x86-64_linux #1/jdk_foreign_native_0`:
```
10:09:36 openjdk version "16" 2021-03-16
10:09:36 OpenJDK Runtime Environment AdoptOpenJDK (build 16+32-202101220448)
10:09:36 Eclipse OpenJ9 VM AdoptOpenJDK (build master-a1cfdc286, JRE 16 Linux amd64-64-Bit Compressed References 20210122_1 (JIT enabled, AOT enabled)
10:09:36 OpenJ9 - a1cfdc286
10:09:36 OMR - cf8c5aab9
10:09:36 JCL - eacf70634f based on jdk-16+32)
```
To rebuild the failed tests in <Jenkins URL>=https://hyc-runtimes-jenkins.swg-devops.com/job/Grinder, use the following links:
11:26:53 https://hyc-runtimes-jenkins.swg-devops.com/job/Grinder/parambuild/?JDK_VERSION=16&JDK_IMPL=openj9&BUILD_LIST=openjdk&PLATFORM=x86-64_linux&TARGET=jdk_foreign_native_0
Optional info
-------------
Failure output (captured from console output)
---------------------------------------------
```
[2021-01-22T16:23:35.757Z] Running test jdk_foreign_native_0 ...
[2021-01-22T16:23:35.757Z] ===============================================
[2021-01-22T16:23:47.622Z] [TestNG] Running:
[2021-01-22T16:23:47.622Z] java/foreign/TestNative.java
[2021-01-22T16:23:47.622Z]
[2021-01-22T16:23:47.622Z] test TestNative.testBadResize(): success
[2021-01-22T16:23:47.622Z] test TestNative.testDefaultAccessModes(): failure
[2021-01-22T16:23:47.630Z] java.lang.RuntimeException: java.lang.UnsatisfiedLinkError: jdk/internal/foreign/abi/ProgrammableInvoker.registerNatives()V
[2021-01-22T16:23:47.630Z] at jdk.incubator.foreign/jdk.internal.foreign.abi.SharedUtils.allocateMemoryInternal(SharedUtils.java:285)
[2021-01-22T16:23:47.630Z] at jdk.incubator.foreign/jdk.incubator.foreign.CLinker.allocateMemoryRestricted(CLinker.java:396)
[2021-01-22T16:23:47.630Z] at TestNative.allocate(TestNative.java:147)
[2021-01-22T16:23:47.630Z] at TestNative.testDefaultAccessModes(TestNative.java:176)
[2021-01-22T16:23:47.630Z] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[2021-01-22T16:23:47.630Z] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
[2021-01-22T16:23:47.630Z] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[2021-01-22T16:23:47.630Z] at java.base/java.lang.reflect.Method.invoke(Method.java:567)
[2021-01-22T16:23:47.630Z] at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:85)
[2021-01-22T16:23:47.630Z] at org.testng.internal.Invoker.invokeMethod(Invoker.java:639)
[2021-01-22T16:23:47.630Z] at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:821)
[2021-01-22T16:23:47.630Z] at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1131)
[2021-01-22T16:23:47.630Z] at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
[2021-01-22T16:23:47.632Z] at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
[2021-01-22T16:23:47.632Z] at org.testng.TestRunner.privateRun(TestRunner.java:773)
[2021-01-22T16:23:47.632Z] at org.testng.TestRunner.run(TestRunner.java:623)
[2021-01-22T16:23:47.632Z] at org.testng.SuiteRunner.runTest(SuiteRunner.java:357)
[2021-01-22T16:23:47.632Z] at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:352)
[2021-01-22T16:23:47.632Z] at org.testng.SuiteRunner.privateRun(SuiteRunner.java:310)
[2021-01-22T16:23:47.632Z] at org.testng.SuiteRunner.run(SuiteRunner.java:259)
[2021-01-22T16:23:47.632Z] at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
[2021-01-22T16:23:47.632Z] at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
[2021-01-22T16:23:47.632Z] at org.testng.TestNG.runSuitesSequentially(TestNG.java:1185)
[2021-01-22T16:23:47.632Z] at org.testng.TestNG.runSuitesLocally(TestNG.java:1110)
[2021-01-22T16:23:47.632Z] at org.testng.TestNG.run(TestNG.java:1018)
[2021-01-22T16:23:47.632Z] at com.sun.javatest.regtest.agent.TestNGRunner.main(TestNGRunner.java:94)
[2021-01-22T16:23:47.632Z] at com.sun.javatest.regtest.agent.TestNGRunner.main(TestNGRunner.java:54)
[2021-01-22T16:23:47.632Z] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[2021-01-22T16:23:47.632Z] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
[2021-01-22T16:23:47.632Z] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[2021-01-22T16:23:47.632Z] at java.base/java.lang.reflect.Method.invoke(Method.java:567)
[2021-01-22T16:23:47.632Z] at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
[2021-01-22T16:23:47.632Z] at java.base/java.lang.Thread.run(Thread.java:853)
[2021-01-22T16:23:47.632Z] Caused by: java.lang.UnsatisfiedLinkError: jdk/internal/foreign/abi/ProgrammableInvoker.registerNatives()V
[2021-01-22T16:23:47.632Z] at jdk.incubator.foreign/jdk.internal.foreign.abi.ProgrammableInvoker.<clinit>(ProgrammableInvoker.java:384)
[2021-01-22T16:23:47.632Z] at jdk.incubator.foreign/jdk.internal.foreign.abi.x64.sysv.CallArranger.arrangeDowncall(CallArranger.java:129)
[2021-01-22T16:23:47.632Z] at jdk.incubator.foreign/jdk.internal.foreign.abi.x64.sysv.SysVx64Linker.downcallHandle(SysVx64Linker.java:93)
[2021-01-22T16:23:47.632Z] at jdk.incubator.foreign/jdk.internal.foreign.abi.SharedUtils$AllocHolder.<clinit>(SharedUtils.java:272)
[2021-01-22T16:23:47.632Z] at jdk.incubator.foreign/jdk.internal.foreign.abi.SharedUtils.allocateMemoryInternal(SharedUtils.java:283)
[2021-01-22T16:23:47.632Z] ... 32 more
[2021-01-22T16:23:47.635Z] ===============================================
[2021-01-22T16:23:47.635Z] java/foreign/TestNative.java
[2021-01-22T16:23:47.635Z] Total tests run: 19, Failures: 3, Skips: 0
[2021-01-22T16:23:47.635Z] ===============================================
```
| 1.0 | JDK16 java/foreign/TestNative.java - UnsatisfiedLinkError: jdk/internal/foreign/abi/ProgrammableInvoker.registerNatives()V - Failure link
------------
From an internal build `openjdk16-pipeline #3/jdk16-linux-x64-openj9 #1/Test_openjdk16_j9_sanity.openjdk_x86-64_linux #1/jdk_foreign_native_0`:
```
10:09:36 openjdk version "16" 2021-03-16
10:09:36 OpenJDK Runtime Environment AdoptOpenJDK (build 16+32-202101220448)
10:09:36 Eclipse OpenJ9 VM AdoptOpenJDK (build master-a1cfdc286, JRE 16 Linux amd64-64-Bit Compressed References 20210122_1 (JIT enabled, AOT enabled)
10:09:36 OpenJ9 - a1cfdc286
10:09:36 OMR - cf8c5aab9
10:09:36 JCL - eacf70634f based on jdk-16+32)
```
To rebuild the failed tests in <Jenkins URL>=https://hyc-runtimes-jenkins.swg-devops.com/job/Grinder, use the following links:
11:26:53 https://hyc-runtimes-jenkins.swg-devops.com/job/Grinder/parambuild/?JDK_VERSION=16&JDK_IMPL=openj9&BUILD_LIST=openjdk&PLATFORM=x86-64_linux&TARGET=jdk_foreign_native_0
Optional info
-------------
Failure output (captured from console output)
---------------------------------------------
```
[2021-01-22T16:23:35.757Z] Running test jdk_foreign_native_0 ...
[2021-01-22T16:23:35.757Z] ===============================================
[2021-01-22T16:23:47.622Z] [TestNG] Running:
[2021-01-22T16:23:47.622Z] java/foreign/TestNative.java
[2021-01-22T16:23:47.622Z]
[2021-01-22T16:23:47.622Z] test TestNative.testBadResize(): success
[2021-01-22T16:23:47.622Z] test TestNative.testDefaultAccessModes(): failure
[2021-01-22T16:23:47.630Z] java.lang.RuntimeException: java.lang.UnsatisfiedLinkError: jdk/internal/foreign/abi/ProgrammableInvoker.registerNatives()V
[2021-01-22T16:23:47.630Z] at jdk.incubator.foreign/jdk.internal.foreign.abi.SharedUtils.allocateMemoryInternal(SharedUtils.java:285)
[2021-01-22T16:23:47.630Z] at jdk.incubator.foreign/jdk.incubator.foreign.CLinker.allocateMemoryRestricted(CLinker.java:396)
[2021-01-22T16:23:47.630Z] at TestNative.allocate(TestNative.java:147)
[2021-01-22T16:23:47.630Z] at TestNative.testDefaultAccessModes(TestNative.java:176)
[2021-01-22T16:23:47.630Z] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[2021-01-22T16:23:47.630Z] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
[2021-01-22T16:23:47.630Z] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[2021-01-22T16:23:47.630Z] at java.base/java.lang.reflect.Method.invoke(Method.java:567)
[2021-01-22T16:23:47.630Z] at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:85)
[2021-01-22T16:23:47.630Z] at org.testng.internal.Invoker.invokeMethod(Invoker.java:639)
[2021-01-22T16:23:47.630Z] at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:821)
[2021-01-22T16:23:47.630Z] at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1131)
[2021-01-22T16:23:47.630Z] at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
[2021-01-22T16:23:47.632Z] at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
[2021-01-22T16:23:47.632Z] at org.testng.TestRunner.privateRun(TestRunner.java:773)
[2021-01-22T16:23:47.632Z] at org.testng.TestRunner.run(TestRunner.java:623)
[2021-01-22T16:23:47.632Z] at org.testng.SuiteRunner.runTest(SuiteRunner.java:357)
[2021-01-22T16:23:47.632Z] at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:352)
[2021-01-22T16:23:47.632Z] at org.testng.SuiteRunner.privateRun(SuiteRunner.java:310)
[2021-01-22T16:23:47.632Z] at org.testng.SuiteRunner.run(SuiteRunner.java:259)
[2021-01-22T16:23:47.632Z] at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
[2021-01-22T16:23:47.632Z] at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
[2021-01-22T16:23:47.632Z] at org.testng.TestNG.runSuitesSequentially(TestNG.java:1185)
[2021-01-22T16:23:47.632Z] at org.testng.TestNG.runSuitesLocally(TestNG.java:1110)
[2021-01-22T16:23:47.632Z] at org.testng.TestNG.run(TestNG.java:1018)
[2021-01-22T16:23:47.632Z] at com.sun.javatest.regtest.agent.TestNGRunner.main(TestNGRunner.java:94)
[2021-01-22T16:23:47.632Z] at com.sun.javatest.regtest.agent.TestNGRunner.main(TestNGRunner.java:54)
[2021-01-22T16:23:47.632Z] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[2021-01-22T16:23:47.632Z] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
[2021-01-22T16:23:47.632Z] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[2021-01-22T16:23:47.632Z] at java.base/java.lang.reflect.Method.invoke(Method.java:567)
[2021-01-22T16:23:47.632Z] at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
[2021-01-22T16:23:47.632Z] at java.base/java.lang.Thread.run(Thread.java:853)
[2021-01-22T16:23:47.632Z] Caused by: java.lang.UnsatisfiedLinkError: jdk/internal/foreign/abi/ProgrammableInvoker.registerNatives()V
[2021-01-22T16:23:47.632Z] at jdk.incubator.foreign/jdk.internal.foreign.abi.ProgrammableInvoker.<clinit>(ProgrammableInvoker.java:384)
[2021-01-22T16:23:47.632Z] at jdk.incubator.foreign/jdk.internal.foreign.abi.x64.sysv.CallArranger.arrangeDowncall(CallArranger.java:129)
[2021-01-22T16:23:47.632Z] at jdk.incubator.foreign/jdk.internal.foreign.abi.x64.sysv.SysVx64Linker.downcallHandle(SysVx64Linker.java:93)
[2021-01-22T16:23:47.632Z] at jdk.incubator.foreign/jdk.internal.foreign.abi.SharedUtils$AllocHolder.<clinit>(SharedUtils.java:272)
[2021-01-22T16:23:47.632Z] at jdk.incubator.foreign/jdk.internal.foreign.abi.SharedUtils.allocateMemoryInternal(SharedUtils.java:283)
[2021-01-22T16:23:47.632Z] ... 32 more
[2021-01-22T16:23:47.635Z] ===============================================
[2021-01-22T16:23:47.635Z] java/foreign/TestNative.java
[2021-01-22T16:23:47.635Z] Total tests run: 19, Failures: 3, Skips: 0
[2021-01-22T16:23:47.635Z] ===============================================
```
| non_priority | java foreign testnative java unsatisfiedlinkerror jdk internal foreign abi programmableinvoker registernatives v failure link from an internal build pipeline linux test sanity openjdk linux jdk foreign native openjdk version openjdk runtime environment adoptopenjdk build eclipse vm adoptopenjdk build master jre linux bit compressed references jit enabled aot enabled omr jcl based on jdk to rebuild the failed tests in use the following links optional info failure output captured from console output running test jdk foreign native running java foreign testnative java test testnative testbadresize success test testnative testdefaultaccessmodes failure java lang runtimeexception java lang unsatisfiedlinkerror jdk internal foreign abi programmableinvoker registernatives v at jdk incubator foreign jdk internal foreign abi sharedutils allocatememoryinternal sharedutils java at jdk incubator foreign jdk incubator foreign clinker allocatememoryrestricted clinker java at testnative allocate testnative java at testnative testdefaultaccessmodes testnative java at java base jdk internal reflect nativemethodaccessorimpl native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java base java lang reflect method invoke method java at org testng internal methodinvocationhelper invokemethod methodinvocationhelper java at org testng internal invoker invokemethod invoker java at org testng internal invoker invoketestmethod invoker java at org testng internal invoker invoketestmethods invoker java at org testng internal testmethodworker invoketestmethods testmethodworker java at org testng internal testmethodworker run testmethodworker java at org testng testrunner privaterun testrunner java at org testng testrunner run testrunner java at org testng suiterunner runtest suiterunner java at org testng suiterunner runsequentially suiterunner java at org testng suiterunner privaterun suiterunner java at org testng suiterunner run suiterunner java at org testng suiterunnerworker runsuite suiterunnerworker java at org testng suiterunnerworker run suiterunnerworker java at org testng testng runsuitessequentially testng java at org testng testng runsuiteslocally testng java at org testng testng run testng java at com sun javatest regtest agent testngrunner main testngrunner java at com sun javatest regtest agent testngrunner main testngrunner java at java base jdk internal reflect nativemethodaccessorimpl native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java base java lang reflect method invoke method java at com sun javatest regtest agent mainwrapper mainthread run mainwrapper java at java base java lang thread run thread java caused by java lang unsatisfiedlinkerror jdk internal foreign abi programmableinvoker registernatives v at jdk incubator foreign jdk internal foreign abi programmableinvoker programmableinvoker java at jdk incubator foreign jdk internal foreign abi sysv callarranger arrangedowncall callarranger java at jdk incubator foreign jdk internal foreign abi sysv downcallhandle java at jdk incubator foreign jdk internal foreign abi sharedutils allocholder sharedutils java at jdk incubator foreign jdk internal foreign abi sharedutils allocatememoryinternal sharedutils java more java foreign testnative java total tests run failures skips | 0 |
89,372 | 25,768,093,005 | IssuesEvent | 2022-12-09 04:46:25 | ApolloAuto/apollo | https://api.github.com/repos/ApolloAuto/apollo | closed | Localisation msf arch64 build | Module: Build | I did a fresh build using arch64 docker dev environment and I hitting this error:
Execution platform: @local_config_platform//:host
In file included from ./modules/localization/msf/msf_localization.h:42:0,
from modules/localization/msf/msf_localization.cc:17:
./modules/localization/msf/local_integ/localization_integ.h:24:10: fatal error: localization_msf/gnss_struct.h: No such file or directory
#include "localization_msf/gnss_struct.h"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Checking on third party directory seems like it lacks the localization_msf includes and libs for arch64 (only x86_64 dir is in place).
Any idea why this is not present for arch64 and how I should install it or is there any way to avoid this ? | 1.0 | Localisation msf arch64 build - I did a fresh build using arch64 docker dev environment and I hitting this error:
Execution platform: @local_config_platform//:host
In file included from ./modules/localization/msf/msf_localization.h:42:0,
from modules/localization/msf/msf_localization.cc:17:
./modules/localization/msf/local_integ/localization_integ.h:24:10: fatal error: localization_msf/gnss_struct.h: No such file or directory
#include "localization_msf/gnss_struct.h"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Checking on third party directory seems like it lacks the localization_msf includes and libs for arch64 (only x86_64 dir is in place).
Any idea why this is not present for arch64 and how I should install it or is there any way to avoid this ? | non_priority | localisation msf build i did a fresh build using docker dev environment and i hitting this error execution platform local config platform host in file included from modules localization msf msf localization h from modules localization msf msf localization cc modules localization msf local integ localization integ h fatal error localization msf gnss struct h no such file or directory include localization msf gnss struct h checking on third party directory seems like it lacks the localization msf includes and libs for only dir is in place any idea why this is not present for and how i should install it or is there any way to avoid this | 0 |
7,628 | 5,097,589,376 | IssuesEvent | 2017-01-03 21:59:06 | pipelinedb/pipelinedb | https://api.github.com/repos/pipelinedb/pipelinedb | opened | Support for adding columns to continuous views | usability | This has come up quite a few times, and it's probably time to add built-in support for it. It doesn't make sense to support this at the syntax level (i.e. `ALTER CONTINUOUS VIEW`), just as this can't really be done with regular `VIEWs` via `ALTER VIEW`.
The right approach probably involves just exposing functionality that allows users to achieve the desired semantics in a simple, reliable way. One way to do this would be to expose a function for combining two continuous views:
SELECT combine_continuous_views('result_cv', 'temp_cv');
This would combine the `result_cv` and `temp_cv` CVs into `result_cv`, and we'd probably want to drop `temp_cv` after a successful combine. Obviously this requires that both CVs:
* Must have the same grouping
* Must `SELECT` from the same stream/relation
* Don't have any column name conflicts
* *Anything else?*
The reason I think that this approach would work well is because it's conducive to backfilling the new aggregates/columns separately in their own CV, until it's time to combine them, and it's easily transactional as well.
/cc @usmanm @schapirama | True | Support for adding columns to continuous views - This has come up quite a few times, and it's probably time to add built-in support for it. It doesn't make sense to support this at the syntax level (i.e. `ALTER CONTINUOUS VIEW`), just as this can't really be done with regular `VIEWs` via `ALTER VIEW`.
The right approach probably involves just exposing functionality that allows users to achieve the desired semantics in a simple, reliable way. One way to do this would be to expose a function for combining two continuous views:
SELECT combine_continuous_views('result_cv', 'temp_cv');
This would combine the `result_cv` and `temp_cv` CVs into `result_cv`, and we'd probably want to drop `temp_cv` after a successful combine. Obviously this requires that both CVs:
* Must have the same grouping
* Must `SELECT` from the same stream/relation
* Don't have any column name conflicts
* *Anything else?*
The reason I think that this approach would work well is because it's conducive to backfilling the new aggregates/columns separately in their own CV, until it's time to combine them, and it's easily transactional as well.
/cc @usmanm @schapirama | non_priority | support for adding columns to continuous views this has come up quite a few times and it s probably time to add built in support for it it doesn t make sense to support this at the syntax level i e alter continuous view just as this can t really be done with regular views via alter view the right approach probably involves just exposing functionality that allows users to achieve the desired semantics in a simple reliable way one way to do this would be to expose a function for combining two continuous views select combine continuous views result cv temp cv this would combine the result cv and temp cv cvs into result cv and we d probably want to drop temp cv after a successful combine obviously this requires that both cvs must have the same grouping must select from the same stream relation don t have any column name conflicts anything else the reason i think that this approach would work well is because it s conducive to backfilling the new aggregates columns separately in their own cv until it s time to combine them and it s easily transactional as well cc usmanm schapirama | 0 |
82,866 | 23,903,834,169 | IssuesEvent | 2022-09-08 21:35:49 | mautic/mautic | https://api.github.com/repos/mautic/mautic | closed | html-code is changed inside mj-raw component | bug stale builder-grapesjs | ### Mautic Version
4.0.0
### PHP version
7.4
### What browsers are you seeing the problem on?
Not relevant
### What happened?
You can add a "raw" component inside a WJML-theme.
We assume all html-content inside the <mj-raw>tag should be kept unchanged (that's why it's a **raw** component).
But when sending/previewing the e-mail, the code inside the <mj-raw> is changed - including inline styling, and sometimes even html-tags are missing.
### How can we reproduce this issue?
Step 1: Add an e-mail using the "Brienz" theme
Step 2: Add a raw-component
Step 3: Put the following content into the raw component: \<p style="color: #FF0000;"\>Test code\</p\>
Step 4: Save e-mail, and view the preview
Step 5: Inspect the code - you'll see the style-tag has disappeared, and the <p> is not colored red
### Relevant log output
_No response_
### Code of Conduct
- [X] I confirm that I have read and agree to follow this project's Code of Conduct
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://app.bountysource.com/issues/103347172-html-code-is-changed-inside-mj-raw-component?utm_campaign=plugin&utm_content=tracker%2F5355074&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://app.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F5355074&utm_medium=issues&utm_source=github).
</bountysource-plugin> | 1.0 | html-code is changed inside mj-raw component - ### Mautic Version
4.0.0
### PHP version
7.4
### What browsers are you seeing the problem on?
Not relevant
### What happened?
You can add a "raw" component inside a WJML-theme.
We assume all html-content inside the <mj-raw>tag should be kept unchanged (that's why it's a **raw** component).
But when sending/previewing the e-mail, the code inside the <mj-raw> is changed - including inline styling, and sometimes even html-tags are missing.
### How can we reproduce this issue?
Step 1: Add an e-mail using the "Brienz" theme
Step 2: Add a raw-component
Step 3: Put the following content into the raw component: \<p style="color: #FF0000;"\>Test code\</p\>
Step 4: Save e-mail, and view the preview
Step 5: Inspect the code - you'll see the style-tag has disappeared, and the <p> is not colored red
### Relevant log output
_No response_
### Code of Conduct
- [X] I confirm that I have read and agree to follow this project's Code of Conduct
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://app.bountysource.com/issues/103347172-html-code-is-changed-inside-mj-raw-component?utm_campaign=plugin&utm_content=tracker%2F5355074&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://app.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F5355074&utm_medium=issues&utm_source=github).
</bountysource-plugin> | non_priority | html code is changed inside mj raw component mautic version php version what browsers are you seeing the problem on not relevant what happened you can add a raw component inside a wjml theme we assume all html content inside the tag should be kept unchanged that s why it s a raw component but when sending previewing the e mail the code inside the is changed including inline styling and sometimes even html tags are missing how can we reproduce this issue step add an e mail using the brienz theme step add a raw component step put the following content into the raw component test code step save e mail and view the preview step inspect the code you ll see the style tag has disappeared and the is not colored red relevant log output no response code of conduct i confirm that i have read and agree to follow this project s code of conduct want to back this issue we accept bounties via | 0 |
78,149 | 27,340,498,898 | IssuesEvent | 2023-02-26 18:38:42 | scipy/scipy | https://api.github.com/repos/scipy/scipy | opened | BUG: find_peaks misses some peaks when working with long input arrays | defect | ### Describe your issue.
When I run `find_peaks` on an array of length `378834`, scipy misses a few peaks that it detects if I pass it only an excerpt of the array containing that missed peak.
```
import numpy as np
from scipy.signal import find_peaks
import matplotlib.pyplot as plt
y = np.load('./buggy_peaks.npy')
```
Then this:
```
s = slice(48407, 50407)
xvals = np.arange(len(y))
peaks_from_short_snippet, _ = find_peaks(y[s], width=(5, 750), distance=(25), prominence=0.398)
plt.plot(xvals[s], y[s])
plt.scatter(xvals[s][peaks_from_short_snippet], y[s][peaks_from_short_snippet])
print(1256 in peaks_from_short_snippet)
print(1306 in peaks_from_short_snippet)
```
gives `True; True` and
but this:
```
peaks_from_whole, _ = find_peaks(y, width=(5, 750), distance=(25), prominence=0.398)
plt.scatter(peaks_from_whole, y[peaks_from_whole])
plt.scatter(s.start + 1256, y[s.start + 1256], s=50, facecolors='none', edgecolors='r') # mark the missing peak
plt.plot(xvals[s], y[s])
plt.xlim([48450, 50250])
print((s.start + 1256) in peaks_from_whole)
print((s.start + 1306) in peaks_from_whole)
```
gives `False; True` and
I would love for the solution here to be that I'm using `find_peaks` wrong but my understanding is that the parameters apply on a peak-by-peak basis and so shouldn't be affected by adding in extra data. I've run many many many signals like this one through find_peaks before without any issues; I'm not sure what's special about this one.
I found some similar GH issues about not finding peaks when they're at the very edges of an array, but that isn't the case here. Let me know if you need more information / if you can reproduce. I ran this originally on a linux HPC with scipy 1.10, but it reproduces on my Mac running scipy 1.9 as well, so I don't think it's a hardware bug per se.
[buggy_peaks.npy.zip](https://github.com/scipy/scipy/files/10834402/buggy_peaks.npy.zip)
### Reproducing Code Example
```python
import numpy as np
from scipy.signal import find_peaks
import matplotlib.pyplot as plt
y = np.load('/n/groups/datta/Jonah/tmp/buggy_peaks.npy')
s = slice(48407, 50407)
xvals = np.arange(len(y))
peaks_from_short_snippet, _ = find_peaks(y[s], width=(5, 750), distance=(25), prominence=0.398)
plt.plot(xvals[s], y[s])
plt.scatter(xvals[s][peaks_from_short_snippet], y[s][peaks_from_short_snippet])
print(1256 in peaks_from_short_snippet)
print(1306 in peaks_from_short_snippet)
peaks_from_whole, _ = find_peaks(y, width=(5, 750), distance=(25), prominence=0.398)
plt.scatter(peaks_from_whole, y[peaks_from_whole])
plt.plot(xvals[s], y[s])
plt.xlim([48450, 50250])
plt.scatter(s.start + 1256, y[s.start + 1256], s=50, facecolors='none', edgecolors='r')
print((s.start + 1256) in peaks_from_whole)
print((s.start + 1306) in peaks_from_whole)
```
### Error message
```shell
N/a
```
### SciPy/NumPy/Python version information
1.10.0 1.23.5 sys.version_info(major=3, minor=9, micro=15, releaselevel='final', serial=0) | 1.0 | BUG: find_peaks misses some peaks when working with long input arrays - ### Describe your issue.
When I run `find_peaks` on an array of length `378834`, scipy misses a few peaks that it detects if I pass it only an excerpt of the array containing that missed peak.
```
import numpy as np
from scipy.signal import find_peaks
import matplotlib.pyplot as plt
y = np.load('./buggy_peaks.npy')
```
Then this:
```
s = slice(48407, 50407)
xvals = np.arange(len(y))
peaks_from_short_snippet, _ = find_peaks(y[s], width=(5, 750), distance=(25), prominence=0.398)
plt.plot(xvals[s], y[s])
plt.scatter(xvals[s][peaks_from_short_snippet], y[s][peaks_from_short_snippet])
print(1256 in peaks_from_short_snippet)
print(1306 in peaks_from_short_snippet)
```
gives `True; True` and
but this:
```
peaks_from_whole, _ = find_peaks(y, width=(5, 750), distance=(25), prominence=0.398)
plt.scatter(peaks_from_whole, y[peaks_from_whole])
plt.scatter(s.start + 1256, y[s.start + 1256], s=50, facecolors='none', edgecolors='r') # mark the missing peak
plt.plot(xvals[s], y[s])
plt.xlim([48450, 50250])
print((s.start + 1256) in peaks_from_whole)
print((s.start + 1306) in peaks_from_whole)
```
gives `False; True` and
I would love for the solution here to be that I'm using `find_peaks` wrong but my understanding is that the parameters apply on a peak-by-peak basis and so shouldn't be affected by adding in extra data. I've run many many many signals like this one through find_peaks before without any issues; I'm not sure what's special about this one.
I found some similar GH issues about not finding peaks when they're at the very edges of an array, but that isn't the case here. Let me know if you need more information / if you can reproduce. I ran this originally on a linux HPC with scipy 1.10, but it reproduces on my Mac running scipy 1.9 as well, so I don't think it's a hardware bug per se.
[buggy_peaks.npy.zip](https://github.com/scipy/scipy/files/10834402/buggy_peaks.npy.zip)
### Reproducing Code Example
```python
import numpy as np
from scipy.signal import find_peaks
import matplotlib.pyplot as plt
y = np.load('/n/groups/datta/Jonah/tmp/buggy_peaks.npy')
s = slice(48407, 50407)
xvals = np.arange(len(y))
peaks_from_short_snippet, _ = find_peaks(y[s], width=(5, 750), distance=(25), prominence=0.398)
plt.plot(xvals[s], y[s])
plt.scatter(xvals[s][peaks_from_short_snippet], y[s][peaks_from_short_snippet])
print(1256 in peaks_from_short_snippet)
print(1306 in peaks_from_short_snippet)
peaks_from_whole, _ = find_peaks(y, width=(5, 750), distance=(25), prominence=0.398)
plt.scatter(peaks_from_whole, y[peaks_from_whole])
plt.plot(xvals[s], y[s])
plt.xlim([48450, 50250])
plt.scatter(s.start + 1256, y[s.start + 1256], s=50, facecolors='none', edgecolors='r')
print((s.start + 1256) in peaks_from_whole)
print((s.start + 1306) in peaks_from_whole)
```
### Error message
```shell
N/a
```
### SciPy/NumPy/Python version information
1.10.0 1.23.5 sys.version_info(major=3, minor=9, micro=15, releaselevel='final', serial=0) | non_priority | bug find peaks misses some peaks when working with long input arrays describe your issue when i run find peaks on an array of length scipy misses a few peaks that it detects if i pass it only an excerpt of the array containing that missed peak import numpy as np from scipy signal import find peaks import matplotlib pyplot as plt y np load buggy peaks npy then this s slice xvals np arange len y peaks from short snippet find peaks y width distance prominence plt plot xvals y plt scatter xvals y print in peaks from short snippet print in peaks from short snippet gives true true and but this peaks from whole find peaks y width distance prominence plt scatter peaks from whole y plt scatter s start y s facecolors none edgecolors r mark the missing peak plt plot xvals y plt xlim print s start in peaks from whole print s start in peaks from whole gives false true and i would love for the solution here to be that i m using find peaks wrong but my understanding is that the parameters apply on a peak by peak basis and so shouldn t be affected by adding in extra data i ve run many many many signals like this one through find peaks before without any issues i m not sure what s special about this one i found some similar gh issues about not finding peaks when they re at the very edges of an array but that isn t the case here let me know if you need more information if you can reproduce i ran this originally on a linux hpc with scipy but it reproduces on my mac running scipy as well so i don t think it s a hardware bug per se reproducing code example python import numpy as np from scipy signal import find peaks import matplotlib pyplot as plt y np load n groups datta jonah tmp buggy peaks npy s slice xvals np arange len y peaks from short snippet find peaks y width distance prominence plt plot xvals y plt scatter xvals y print in peaks from short snippet print in peaks from short snippet peaks from whole find peaks y width distance prominence plt scatter peaks from whole y plt plot xvals y plt xlim plt scatter s start y s facecolors none edgecolors r print s start in peaks from whole print s start in peaks from whole error message shell n a scipy numpy python version information sys version info major minor micro releaselevel final serial | 0 |
160,764 | 13,796,579,264 | IssuesEvent | 2020-10-09 20:05:12 | LucasPilla/Sorting-Algorithms-Visualizer | https://api.github.com/repos/LucasPilla/Sorting-Algorithms-Visualizer | closed | Explaining algorithms - Wiki page | Hacktoberfest documentation good first issue help wanted | O intend to make a detailed Wiki page describing each algorithm and showing a visualization gif! I appreciate any help! | 1.0 | Explaining algorithms - Wiki page - O intend to make a detailed Wiki page describing each algorithm and showing a visualization gif! I appreciate any help! | non_priority | explaining algorithms wiki page o intend to make a detailed wiki page describing each algorithm and showing a visualization gif i appreciate any help | 0 |
250,789 | 18,907,891,278 | IssuesEvent | 2021-11-16 11:01:37 | tox-dev/py-filelock | https://api.github.com/repos/tox-dev/py-filelock | closed | poll_intervall is a misspelling | help-wanted documentation | poll_intervall should be spelled poll_interval (but leave the old one for compatibility!) | 1.0 | poll_intervall is a misspelling - poll_intervall should be spelled poll_interval (but leave the old one for compatibility!) | non_priority | poll intervall is a misspelling poll intervall should be spelled poll interval but leave the old one for compatibility | 0 |
136,996 | 11,094,780,690 | IssuesEvent | 2019-12-16 07:25:29 | kubeflow/pipelines | https://api.github.com/repos/kubeflow/pipelines | opened | [testing] Inverse proxy is flaky in test infra | area/engprod area/testing kind/bug | **What happened:**
In presubmit e2e tests, inverse proxy stucks at CrashLoopBackOff from time to time.
For example: https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/kubeflow_pipelines/2643/kubeflow-pipeline-e2e-test/1198909726310535169#1:build-log.txt%3A1177
**What did you expect to happen:**
It should not be flaky.
I briefly did some investigation and it seems when the first time inverse proxy runs, it gets an empty BACKEND_ID: https://github.com/kubeflow/pipelines/blob/master/proxy/attempt-register-vm-on-proxy.sh#L70 and saves it to the configmap.
Therefore, all future runs will try to connect to the empty BACKEND_ID and fails. I think we need some validation if generated configmap is sane before saving it.
| 1.0 | [testing] Inverse proxy is flaky in test infra - **What happened:**
In presubmit e2e tests, inverse proxy stucks at CrashLoopBackOff from time to time.
For example: https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/kubeflow_pipelines/2643/kubeflow-pipeline-e2e-test/1198909726310535169#1:build-log.txt%3A1177
**What did you expect to happen:**
It should not be flaky.
I briefly did some investigation and it seems when the first time inverse proxy runs, it gets an empty BACKEND_ID: https://github.com/kubeflow/pipelines/blob/master/proxy/attempt-register-vm-on-proxy.sh#L70 and saves it to the configmap.
Therefore, all future runs will try to connect to the empty BACKEND_ID and fails. I think we need some validation if generated configmap is sane before saving it.
| non_priority | inverse proxy is flaky in test infra what happened in presubmit tests inverse proxy stucks at crashloopbackoff from time to time for example what did you expect to happen it should not be flaky i briefly did some investigation and it seems when the first time inverse proxy runs it gets an empty backend id and saves it to the configmap therefore all future runs will try to connect to the empty backend id and fails i think we need some validation if generated configmap is sane before saving it | 0 |
71,922 | 30,929,368,245 | IssuesEvent | 2023-08-06 22:17:47 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | `UnsafeAccessor` and static classes | area-System.Runtime.CompilerServices untriaged | As per #81741:
```
For UnsafeAccessorKind.{Static}Method and UnsafeAccessorKind.{Static}Field, the type of the first argument of the annotated extern method identifies the owning type.
The value of the first argument is treated as @this pointer for instance fields and methods.
The first argument must be passed as ref for instance fields and methods on structs.
The value of the first argument is not used by the implementation for static fields and methods.
```
This requirement however makes `StaticMethod` and `StaticField` impossible to use with static classes, since you can't have a parameter of their type.
Is there any way to specify the type there today? If not, could the api maybe be changed to take a `typeof` in the attribute fields to allow specifying the type that way? | 1.0 | `UnsafeAccessor` and static classes - As per #81741:
```
For UnsafeAccessorKind.{Static}Method and UnsafeAccessorKind.{Static}Field, the type of the first argument of the annotated extern method identifies the owning type.
The value of the first argument is treated as @this pointer for instance fields and methods.
The first argument must be passed as ref for instance fields and methods on structs.
The value of the first argument is not used by the implementation for static fields and methods.
```
This requirement however makes `StaticMethod` and `StaticField` impossible to use with static classes, since you can't have a parameter of their type.
Is there any way to specify the type there today? If not, could the api maybe be changed to take a `typeof` in the attribute fields to allow specifying the type that way? | non_priority | unsafeaccessor and static classes as per for unsafeaccessorkind static method and unsafeaccessorkind static field the type of the first argument of the annotated extern method identifies the owning type the value of the first argument is treated as this pointer for instance fields and methods the first argument must be passed as ref for instance fields and methods on structs the value of the first argument is not used by the implementation for static fields and methods this requirement however makes staticmethod and staticfield impossible to use with static classes since you can t have a parameter of their type is there any way to specify the type there today if not could the api maybe be changed to take a typeof in the attribute fields to allow specifying the type that way | 0 |
27,775 | 12,703,518,953 | IssuesEvent | 2020-06-22 22:31:58 | Azure/azure-sdk-for-net | https://api.github.com/repos/Azure/azure-sdk-for-net | closed | Microsoft.Rest.ClientRuntime.Azure.Authentication prevents updating to the latest version of Microsoft.IdentityModel.Tokens | Authentication AutoRest Runtime Mgmt Service Attention customer-reported question | The IdentityModel Team has bumped version number to 6.5.0: https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet#note-about-650
But Microsoft.Rest.ClientRuntime.Azure.Authentication has dependency on Microsoft.IdentityModel.Tokens < 6.0.0: https://github.com/Azure/azure-sdk-for-net/blob/45cdad6bc3f20b36220d303a44f99895bdba28b7/sdk/mgmtcommon/Auth/Az.Auth/Az.Authentication/Microsoft.Rest.ClientRuntime.Azure.Authentication.csproj#L50
Is it is actually not compatible with Microsoft.IdentityModel.Tokens 6.5.0 or this restriction can just be removed? | 1.0 | Microsoft.Rest.ClientRuntime.Azure.Authentication prevents updating to the latest version of Microsoft.IdentityModel.Tokens - The IdentityModel Team has bumped version number to 6.5.0: https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet#note-about-650
But Microsoft.Rest.ClientRuntime.Azure.Authentication has dependency on Microsoft.IdentityModel.Tokens < 6.0.0: https://github.com/Azure/azure-sdk-for-net/blob/45cdad6bc3f20b36220d303a44f99895bdba28b7/sdk/mgmtcommon/Auth/Az.Auth/Az.Authentication/Microsoft.Rest.ClientRuntime.Azure.Authentication.csproj#L50
Is it is actually not compatible with Microsoft.IdentityModel.Tokens 6.5.0 or this restriction can just be removed? | non_priority | microsoft rest clientruntime azure authentication prevents updating to the latest version of microsoft identitymodel tokens the identitymodel team has bumped version number to but microsoft rest clientruntime azure authentication has dependency on microsoft identitymodel tokens is it is actually not compatible with microsoft identitymodel tokens or this restriction can just be removed | 0 |
256,480 | 27,561,678,631 | IssuesEvent | 2023-03-07 22:39:34 | samqws-marketing/box_mojito | https://api.github.com/repos/samqws-marketing/box_mojito | closed | CVE-2021-33623 (High) detected in trim-newlines-1.0.0.tgz - autoclosed | Mend: dependency security vulnerability | ## CVE-2021-33623 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>trim-newlines-1.0.0.tgz</b></p></summary>
<p>Trim newlines from the start and/or end of a string</p>
<p>Library home page: <a href="https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz">https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz</a></p>
<p>
Dependency Hierarchy:
- node-sass-4.13.1.tgz (Root Library)
- meow-3.7.0.tgz
- :x: **trim-newlines-1.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samqws-marketing/box_mojito/commit/65290aeb818102fa2443a637efdccebebfed1eb9">65290aeb818102fa2443a637efdccebebfed1eb9</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The trim-newlines package before 3.0.1 and 4.x before 4.0.1 for Node.js has an issue related to regular expression denial-of-service (ReDoS) for the .end() method.
<p>Publish Date: 2021-05-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-33623>CVE-2021-33623</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-2021-33623">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33623</a></p>
<p>Release Date: 2021-05-28</p>
<p>Fix Resolution (trim-newlines): 3.0.1</p>
<p>Direct dependency fix Resolution (node-sass): 6.0.1</p>
</p>
</details>
<p></p>
| True | CVE-2021-33623 (High) detected in trim-newlines-1.0.0.tgz - autoclosed - ## CVE-2021-33623 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>trim-newlines-1.0.0.tgz</b></p></summary>
<p>Trim newlines from the start and/or end of a string</p>
<p>Library home page: <a href="https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz">https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz</a></p>
<p>
Dependency Hierarchy:
- node-sass-4.13.1.tgz (Root Library)
- meow-3.7.0.tgz
- :x: **trim-newlines-1.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samqws-marketing/box_mojito/commit/65290aeb818102fa2443a637efdccebebfed1eb9">65290aeb818102fa2443a637efdccebebfed1eb9</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The trim-newlines package before 3.0.1 and 4.x before 4.0.1 for Node.js has an issue related to regular expression denial-of-service (ReDoS) for the .end() method.
<p>Publish Date: 2021-05-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-33623>CVE-2021-33623</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-2021-33623">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33623</a></p>
<p>Release Date: 2021-05-28</p>
<p>Fix Resolution (trim-newlines): 3.0.1</p>
<p>Direct dependency fix Resolution (node-sass): 6.0.1</p>
</p>
</details>
<p></p>
| non_priority | cve high detected in trim newlines tgz autoclosed cve high severity vulnerability vulnerable library trim newlines tgz trim newlines from the start and or end of a string library home page a href dependency hierarchy node sass tgz root library meow tgz x trim newlines tgz vulnerable library found in head commit a href found in base branch master vulnerability details the trim newlines package before and x before for node js has an issue related to regular expression denial of service redos for the end method 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 trim newlines direct dependency fix resolution node sass | 0 |
249,016 | 21,094,346,896 | IssuesEvent | 2022-04-04 08:54:26 | weaveworks/eksctl | https://api.github.com/repos/weaveworks/eksctl | closed | Add integration tests for running workloads on WindowsServer20H2CoreContainer | area/testing kind/improvement | As from the [PR ](https://github.com/weaveworks/eksctl/pull/4442/files) the section for WindowsServer20H2CoreContainer was removed, so we need to add tests for that.
We need to figure out how to make this test work, see PR description for more details
| 1.0 | Add integration tests for running workloads on WindowsServer20H2CoreContainer - As from the [PR ](https://github.com/weaveworks/eksctl/pull/4442/files) the section for WindowsServer20H2CoreContainer was removed, so we need to add tests for that.
We need to figure out how to make this test work, see PR description for more details
| non_priority | add integration tests for running workloads on as from the the section for was removed so we need to add tests for that we need to figure out how to make this test work see pr description for more details | 0 |
95,313 | 19,692,507,572 | IssuesEvent | 2022-01-12 08:45:34 | labspl/colors.js | https://api.github.com/repos/labspl/colors.js | closed | Missing semicolon. | codeReview Meta | ### [Codacy](https://app.codacy.com/gh/labspl/colors.js/commit?cid=612783687) detected an issue:
#### Message: `Missing semicolon.`
#### Occurred on:
+ **Commit**: 074a0f8ed0c31c35d13d28632bd8a049ff136fb6
+ **File**: [lib/index.js](https://github.com/labspl/colors.js/blob/074a0f8ed0c31c35d13d28632bd8a049ff136fb6/lib/index.js)
+ **LineNum**: [22](https://github.com/labspl/colors.js/blob/074a0f8ed0c31c35d13d28632bd8a049ff136fb6/lib/index.js#L22)
+ **Code**: `console.log('testing testing testing testing testing testing testing'.zalgo)`
#### Currently on:
+ **Commit**: 27c04b016c750cfd43201784ffc0f862ebee49c8
+ **File**: [lib/index.js](https://github.com/labspl/colors.js/blob/27c04b016c750cfd43201784ffc0f862ebee49c8/lib/index.js)
+ **LineNum**: [22](https://github.com/labspl/colors.js/blob/27c04b016c750cfd43201784ffc0f862ebee49c8/lib/index.js#L22)
| 1.0 | Missing semicolon. - ### [Codacy](https://app.codacy.com/gh/labspl/colors.js/commit?cid=612783687) detected an issue:
#### Message: `Missing semicolon.`
#### Occurred on:
+ **Commit**: 074a0f8ed0c31c35d13d28632bd8a049ff136fb6
+ **File**: [lib/index.js](https://github.com/labspl/colors.js/blob/074a0f8ed0c31c35d13d28632bd8a049ff136fb6/lib/index.js)
+ **LineNum**: [22](https://github.com/labspl/colors.js/blob/074a0f8ed0c31c35d13d28632bd8a049ff136fb6/lib/index.js#L22)
+ **Code**: `console.log('testing testing testing testing testing testing testing'.zalgo)`
#### Currently on:
+ **Commit**: 27c04b016c750cfd43201784ffc0f862ebee49c8
+ **File**: [lib/index.js](https://github.com/labspl/colors.js/blob/27c04b016c750cfd43201784ffc0f862ebee49c8/lib/index.js)
+ **LineNum**: [22](https://github.com/labspl/colors.js/blob/27c04b016c750cfd43201784ffc0f862ebee49c8/lib/index.js#L22)
| non_priority | missing semicolon detected an issue message missing semicolon occurred on commit file linenum code console log testing testing testing testing testing testing testing zalgo currently on commit file linenum | 0 |
227,196 | 25,031,833,210 | IssuesEvent | 2022-11-04 13:03:10 | sast-automation-dev/django-46 | https://api.github.com/repos/sast-automation-dev/django-46 | opened | bootstrap-3.2.0.js: 6 vulnerabilities (highest severity is: 6.1) | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bootstrap-3.2.0.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js</a></p>
<p>Path to vulnerable library: /taskManager/static/taskManager/js/bootstrap.js</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/django-46/commit/48bbf095553ae6f7a813a10b34f82e3f2d7317a5">48bbf095553ae6f7a813a10b34f82e3f2d7317a5</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (bootstrap version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2019-8331](https://www.mend.io/vulnerability-database/CVE-2019-8331) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.2.0.js | Direct | bootstrap - 3.4.1,4.3.1;bootstrap-sass - 3.4.1,4.3.1 | ❌ |
| [CVE-2018-14040](https://www.mend.io/vulnerability-database/CVE-2018-14040) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.2.0.js | Direct | org.webjars.npm:bootstrap:4.1.2,org.webjars:bootstrap:3.4.0 | ❌ |
| [CVE-2018-20677](https://www.mend.io/vulnerability-database/CVE-2018-20677) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.2.0.js | Direct | Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0 | ❌ |
| [CVE-2018-14042](https://www.mend.io/vulnerability-database/CVE-2018-14042) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.2.0.js | Direct | org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0 | ❌ |
| [CVE-2018-20676](https://www.mend.io/vulnerability-database/CVE-2018-20676) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.2.0.js | Direct | bootstrap - 3.4.0 | ❌ |
| [CVE-2016-10735](https://www.mend.io/vulnerability-database/CVE-2016-10735) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.2.0.js | Direct | 3.4.0 | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2019-8331</summary>
### Vulnerable Library - <b>bootstrap-3.2.0.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js</a></p>
<p>Path to vulnerable library: /taskManager/static/taskManager/js/bootstrap.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.2.0.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/django-46/commit/48bbf095553ae6f7a813a10b34f82e3f2d7317a5">48bbf095553ae6f7a813a10b34f82e3f2d7317a5</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 3.4.1 and 4.3.x before 4.3.1, XSS is possible in the tooltip or popover data-template attribute.
<p>Publish Date: 2019-02-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-8331>CVE-2019-8331</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2019-02-20</p>
<p>Fix Resolution: bootstrap - 3.4.1,4.3.1;bootstrap-sass - 3.4.1,4.3.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-14040</summary>
### Vulnerable Library - <b>bootstrap-3.2.0.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js</a></p>
<p>Path to vulnerable library: /taskManager/static/taskManager/js/bootstrap.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.2.0.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/django-46/commit/48bbf095553ae6f7a813a10b34f82e3f2d7317a5">48bbf095553ae6f7a813a10b34f82e3f2d7317a5</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 4.1.2, XSS is possible in the collapse data-parent attribute.
<p>Publish Date: 2018-07-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-14040>CVE-2018-14040</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2018-07-13</p>
<p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2,org.webjars:bootstrap:3.4.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-20677</summary>
### Vulnerable Library - <b>bootstrap-3.2.0.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js</a></p>
<p>Path to vulnerable library: /taskManager/static/taskManager/js/bootstrap.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.2.0.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/django-46/commit/48bbf095553ae6f7a813a10b34f82e3f2d7317a5">48bbf095553ae6f7a813a10b34f82e3f2d7317a5</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property.
<p>Publish Date: 2019-01-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-20677>CVE-2018-20677</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677</a></p>
<p>Release Date: 2019-01-09</p>
<p>Fix Resolution: Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-14042</summary>
### Vulnerable Library - <b>bootstrap-3.2.0.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js</a></p>
<p>Path to vulnerable library: /taskManager/static/taskManager/js/bootstrap.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.2.0.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/django-46/commit/48bbf095553ae6f7a813a10b34f82e3f2d7317a5">48bbf095553ae6f7a813a10b34f82e3f2d7317a5</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip.
<p>Publish Date: 2018-07-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-14042>CVE-2018-14042</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2018-07-13</p>
<p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-20676</summary>
### Vulnerable Library - <b>bootstrap-3.2.0.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js</a></p>
<p>Path to vulnerable library: /taskManager/static/taskManager/js/bootstrap.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.2.0.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/django-46/commit/48bbf095553ae6f7a813a10b34f82e3f2d7317a5">48bbf095553ae6f7a813a10b34f82e3f2d7317a5</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute.
<p>Publish Date: 2019-01-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-20676>CVE-2018-20676</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20676">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20676</a></p>
<p>Release Date: 2019-01-09</p>
<p>Fix Resolution: bootstrap - 3.4.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2016-10735</summary>
### Vulnerable Library - <b>bootstrap-3.2.0.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js</a></p>
<p>Path to vulnerable library: /taskManager/static/taskManager/js/bootstrap.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.2.0.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/django-46/commit/48bbf095553ae6f7a813a10b34f82e3f2d7317a5">48bbf095553ae6f7a813a10b34f82e3f2d7317a5</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap 3.x before 3.4.0 and 4.x-beta before 4.0.0-beta.2, XSS is possible in the data-target attribute, a different vulnerability than CVE-2018-14041.
<p>Publish Date: 2019-01-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-10735>CVE-2016-10735</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2019-01-09</p>
<p>Fix Resolution: 3.4.0</p>
</p>
<p></p>
</details> | True | bootstrap-3.2.0.js: 6 vulnerabilities (highest severity is: 6.1) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bootstrap-3.2.0.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js</a></p>
<p>Path to vulnerable library: /taskManager/static/taskManager/js/bootstrap.js</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/django-46/commit/48bbf095553ae6f7a813a10b34f82e3f2d7317a5">48bbf095553ae6f7a813a10b34f82e3f2d7317a5</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (bootstrap version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2019-8331](https://www.mend.io/vulnerability-database/CVE-2019-8331) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.2.0.js | Direct | bootstrap - 3.4.1,4.3.1;bootstrap-sass - 3.4.1,4.3.1 | ❌ |
| [CVE-2018-14040](https://www.mend.io/vulnerability-database/CVE-2018-14040) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.2.0.js | Direct | org.webjars.npm:bootstrap:4.1.2,org.webjars:bootstrap:3.4.0 | ❌ |
| [CVE-2018-20677](https://www.mend.io/vulnerability-database/CVE-2018-20677) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.2.0.js | Direct | Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0 | ❌ |
| [CVE-2018-14042](https://www.mend.io/vulnerability-database/CVE-2018-14042) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.2.0.js | Direct | org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0 | ❌ |
| [CVE-2018-20676](https://www.mend.io/vulnerability-database/CVE-2018-20676) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.2.0.js | Direct | bootstrap - 3.4.0 | ❌ |
| [CVE-2016-10735](https://www.mend.io/vulnerability-database/CVE-2016-10735) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.2.0.js | Direct | 3.4.0 | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2019-8331</summary>
### Vulnerable Library - <b>bootstrap-3.2.0.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js</a></p>
<p>Path to vulnerable library: /taskManager/static/taskManager/js/bootstrap.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.2.0.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/django-46/commit/48bbf095553ae6f7a813a10b34f82e3f2d7317a5">48bbf095553ae6f7a813a10b34f82e3f2d7317a5</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 3.4.1 and 4.3.x before 4.3.1, XSS is possible in the tooltip or popover data-template attribute.
<p>Publish Date: 2019-02-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-8331>CVE-2019-8331</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2019-02-20</p>
<p>Fix Resolution: bootstrap - 3.4.1,4.3.1;bootstrap-sass - 3.4.1,4.3.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-14040</summary>
### Vulnerable Library - <b>bootstrap-3.2.0.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js</a></p>
<p>Path to vulnerable library: /taskManager/static/taskManager/js/bootstrap.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.2.0.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/django-46/commit/48bbf095553ae6f7a813a10b34f82e3f2d7317a5">48bbf095553ae6f7a813a10b34f82e3f2d7317a5</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 4.1.2, XSS is possible in the collapse data-parent attribute.
<p>Publish Date: 2018-07-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-14040>CVE-2018-14040</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2018-07-13</p>
<p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2,org.webjars:bootstrap:3.4.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-20677</summary>
### Vulnerable Library - <b>bootstrap-3.2.0.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js</a></p>
<p>Path to vulnerable library: /taskManager/static/taskManager/js/bootstrap.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.2.0.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/django-46/commit/48bbf095553ae6f7a813a10b34f82e3f2d7317a5">48bbf095553ae6f7a813a10b34f82e3f2d7317a5</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property.
<p>Publish Date: 2019-01-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-20677>CVE-2018-20677</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677</a></p>
<p>Release Date: 2019-01-09</p>
<p>Fix Resolution: Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-14042</summary>
### Vulnerable Library - <b>bootstrap-3.2.0.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js</a></p>
<p>Path to vulnerable library: /taskManager/static/taskManager/js/bootstrap.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.2.0.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/django-46/commit/48bbf095553ae6f7a813a10b34f82e3f2d7317a5">48bbf095553ae6f7a813a10b34f82e3f2d7317a5</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip.
<p>Publish Date: 2018-07-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-14042>CVE-2018-14042</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2018-07-13</p>
<p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-20676</summary>
### Vulnerable Library - <b>bootstrap-3.2.0.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js</a></p>
<p>Path to vulnerable library: /taskManager/static/taskManager/js/bootstrap.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.2.0.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/django-46/commit/48bbf095553ae6f7a813a10b34f82e3f2d7317a5">48bbf095553ae6f7a813a10b34f82e3f2d7317a5</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute.
<p>Publish Date: 2019-01-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-20676>CVE-2018-20676</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20676">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20676</a></p>
<p>Release Date: 2019-01-09</p>
<p>Fix Resolution: bootstrap - 3.4.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2016-10735</summary>
### Vulnerable Library - <b>bootstrap-3.2.0.js</b></p>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/js/bootstrap.js</a></p>
<p>Path to vulnerable library: /taskManager/static/taskManager/js/bootstrap.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.2.0.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sast-automation-dev/django-46/commit/48bbf095553ae6f7a813a10b34f82e3f2d7317a5">48bbf095553ae6f7a813a10b34f82e3f2d7317a5</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Bootstrap 3.x before 3.4.0 and 4.x-beta before 4.0.0-beta.2, XSS is possible in the data-target attribute, a different vulnerability than CVE-2018-14041.
<p>Publish Date: 2019-01-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-10735>CVE-2016-10735</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2019-01-09</p>
<p>Fix Resolution: 3.4.0</p>
</p>
<p></p>
</details> | non_priority | bootstrap js vulnerabilities highest severity is vulnerable library bootstrap js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library taskmanager static taskmanager js bootstrap js found in head commit a href vulnerabilities cve severity cvss dependency type fixed in bootstrap version remediation available medium bootstrap js direct bootstrap bootstrap sass medium bootstrap js direct org webjars npm bootstrap org webjars bootstrap medium bootstrap js direct bootstrap nordron angulartemplate dynamic net express projecttemplates dotnetng template znxtapp core module theme beta jmeter medium bootstrap js direct org webjars npm bootstrap org webjars bootstrap medium bootstrap js direct bootstrap medium bootstrap js direct details cve vulnerable library bootstrap js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library taskmanager static taskmanager js bootstrap js dependency hierarchy x bootstrap js vulnerable library found in head commit a href found in base branch master vulnerability details in bootstrap before and x before xss is possible in the tooltip or popover data template attribute 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 release date fix resolution bootstrap bootstrap sass cve vulnerable library bootstrap js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library taskmanager static taskmanager js bootstrap js dependency hierarchy x bootstrap js vulnerable library found in head commit a href found in base branch master vulnerability details in bootstrap before xss is possible in the collapse data parent attribute 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 release date fix resolution org webjars npm bootstrap org webjars bootstrap cve vulnerable library bootstrap js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library taskmanager static taskmanager js bootstrap js dependency hierarchy x bootstrap js vulnerable library found in head commit a href found in base branch master vulnerability details in bootstrap before xss is possible in the affix configuration target property 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 bootstrap nordron angulartemplate dynamic net express projecttemplates dotnetng template znxtapp core module theme beta jmeter cve vulnerable library bootstrap js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library taskmanager static taskmanager js bootstrap js dependency hierarchy x bootstrap js vulnerable library found in head commit a href found in base branch master vulnerability details in bootstrap before xss is possible in the data container property of tooltip 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 release date fix resolution org webjars npm bootstrap org webjars bootstrap cve vulnerable library bootstrap js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library taskmanager static taskmanager js bootstrap js dependency hierarchy x bootstrap js vulnerable library found in head commit a href found in base branch master vulnerability details in bootstrap before xss is possible in the tooltip data viewport attribute 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 bootstrap cve vulnerable library bootstrap js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library taskmanager static taskmanager js bootstrap js dependency hierarchy x bootstrap js vulnerable library found in head commit a href found in base branch master vulnerability details in bootstrap x before and x beta before beta xss is possible in the data target attribute a different vulnerability than cve publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction 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 release date fix resolution | 0 |
195,302 | 22,307,945,744 | IssuesEvent | 2022-06-13 14:32:09 | ignatandrei/BlocklyAutomation | https://api.github.com/repos/ignatandrei/BlocklyAutomation | closed | CVE-2022-22970 (Medium) detected in spring-core-5.3.14.jar, spring-beans-5.3.14.jar | security vulnerability | ## CVE-2022-22970 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>spring-core-5.3.14.jar</b>, <b>spring-beans-5.3.14.jar</b></p></summary>
<p>
<details><summary><b>spring-core-5.3.14.jar</b></p></summary>
<p>Spring Core</p>
<p>Path to dependency file: /src/examples/java-swagger/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-core/5.3.14/spring-core-5.3.14.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-core/5.3.14/spring-core-5.3.14.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-2.6.2.jar (Root Library)
- :x: **spring-core-5.3.14.jar** (Vulnerable Library)
</details>
<details><summary><b>spring-beans-5.3.14.jar</b></p></summary>
<p>Spring Beans</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /src/examples/java-swagger/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-beans/5.3.14/spring-beans-5.3.14.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-beans/5.3.14/spring-beans-5.3.14.jar</p>
<p>
Dependency Hierarchy:
- springfox-swagger2-3.0.0.jar (Root Library)
- spring-plugin-core-2.0.0.RELEASE.jar
- :x: **spring-beans-5.3.14.jar** (Vulnerable Library)
</details>
<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>
In spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, applications that handle file uploads are vulnerable to DoS attack if they rely on data binding to set a MultipartFile or javax.servlet.Part to a field in a model object.
<p>Publish Date: 2022-05-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22970>CVE-2022-22970</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: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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://tanzu.vmware.com/security/cve-2022-22970">https://tanzu.vmware.com/security/cve-2022-22970</a></p>
<p>Release Date: 2022-05-12</p>
<p>Fix Resolution (org.springframework:spring-core): 5.3.20</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter): 2.6.8</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-22970 (Medium) detected in spring-core-5.3.14.jar, spring-beans-5.3.14.jar - ## CVE-2022-22970 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>spring-core-5.3.14.jar</b>, <b>spring-beans-5.3.14.jar</b></p></summary>
<p>
<details><summary><b>spring-core-5.3.14.jar</b></p></summary>
<p>Spring Core</p>
<p>Path to dependency file: /src/examples/java-swagger/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-core/5.3.14/spring-core-5.3.14.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-core/5.3.14/spring-core-5.3.14.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-2.6.2.jar (Root Library)
- :x: **spring-core-5.3.14.jar** (Vulnerable Library)
</details>
<details><summary><b>spring-beans-5.3.14.jar</b></p></summary>
<p>Spring Beans</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /src/examples/java-swagger/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-beans/5.3.14/spring-beans-5.3.14.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-beans/5.3.14/spring-beans-5.3.14.jar</p>
<p>
Dependency Hierarchy:
- springfox-swagger2-3.0.0.jar (Root Library)
- spring-plugin-core-2.0.0.RELEASE.jar
- :x: **spring-beans-5.3.14.jar** (Vulnerable Library)
</details>
<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>
In spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, applications that handle file uploads are vulnerable to DoS attack if they rely on data binding to set a MultipartFile or javax.servlet.Part to a field in a model object.
<p>Publish Date: 2022-05-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22970>CVE-2022-22970</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: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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://tanzu.vmware.com/security/cve-2022-22970">https://tanzu.vmware.com/security/cve-2022-22970</a></p>
<p>Release Date: 2022-05-12</p>
<p>Fix Resolution (org.springframework:spring-core): 5.3.20</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter): 2.6.8</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 spring core jar spring beans jar cve medium severity vulnerability vulnerable libraries spring core jar spring beans jar spring core jar spring core path to dependency file src examples java swagger pom xml path to vulnerable library home wss scanner repository org springframework spring core spring core jar home wss scanner repository org springframework spring core spring core jar dependency hierarchy spring boot starter jar root library x spring core jar vulnerable library spring beans jar spring beans library home page a href path to dependency file src examples java swagger pom xml path to vulnerable library home wss scanner repository org springframework spring beans spring beans jar home wss scanner repository org springframework spring beans spring beans jar dependency hierarchy springfox jar root library spring plugin core release jar x spring beans jar vulnerable library found in base branch main vulnerability details in spring framework versions prior to and old unsupported versions applications that handle file uploads are vulnerable to dos attack if they rely on data binding to set a multipartfile or javax servlet part to a field in a model object publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org springframework spring core direct dependency fix resolution org springframework boot spring boot starter step up your open source security game with mend | 0 |
32,470 | 8,868,564,045 | IssuesEvent | 2019-01-11 00:34:06 | spack/spack | https://api.github.com/repos/spack/spack | closed | Boost fails to build on ANL's Theta | build-error | I'm trying to install boost with spack on ANL's Theta machine, using the GNU compilers. I tried version 1.68.0 and 1.67.0. In both cases the build fails when calling `b2 --clean`. When I go in the the build directory and call `./b2 -- clean` myself, I get `Illegal instruction (core dumped)`.
The same happens with Intel compiler instead of GNU.
If I try to build boost manually (i.e. downloading the archive, running `./bootstrap.sh` with the libraries I want, then `./b2` and `./b2 install`) it works fine.
### Steps to reproduce the issue
```console
$ spack install boost
==> diffutils is already installed in /gpfs/mira-home/mdorier/spack/opt/spack/cray-cnl6-mic_knl/gcc-7.3.0/diffutils-3.6-hdksfzqzgtfwvwbvhu7s75u6f7tkudvz
==> bzip2 is already installed in /gpfs/mira-home/mdorier/spack/opt/spack/cray-cnl6-mic_knl/gcc-7.3.0/bzip2-1.0.6-m22cmmtaf36fnfmvwy36dssvltqfw73q
==> zlib is already installed in /gpfs/mira-home/mdorier/spack/opt/spack/cray-cnl6-mic_knl/gcc-7.3.0/zlib-1.2.11-yuj7ryis72kd6iwpq3qmvp627umsbymc
==> Installing boost
==> Fetching https://dl.bintray.com/boostorg/release/1.67.0/source/boost_1_67_0.tar.bz2
######################################################################## 100.0%
==> Staging archive: /gpfs/mira-home/mdorier/spack/var/spack/stage/boost-1.67.0-a5gxl76fce2fobsekfnhvrhsl5j6j6cw/boost_1_67_0.tar.bz2
==> Created stage in /gpfs/mira-home/mdorier/spack/var/spack/stage/boost-1.67.0-a5gxl76fce2fobsekfnhvrhsl5j6j6cw
==> Applied patch python_jam.patch
==> Building boost [Package]
==> Executing phase: 'install'
==> Error: ProcessError: Command exited with status -4:
'./b2' '--clean'
```
### Platform and user environment
```commandline
$ uname -a
Linux thetalogin6 4.4.103-6.38-default #1 SMP Mon Dec 25 20:44:33 UTC 2017 (e4b9067) x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -d
Description: SUSE Linux Enterprise Server 12 SP3
```
- `compilers.yaml`
```
compilers:
- compiler:
environment: {}
extra_rpaths: []
flags: {}
modules:
- PrgEnv-cray
- cce/8.7.3
operating_system: cnl6
paths:
cc: cc
cxx: CC
f77: ftn
fc: ftn
spec: cce@8.7.3
target: any
- compiler:
environment: {}
extra_rpaths: []
flags: {}
modules:
- PrgEnv-gnu
- gcc/7.3.0
operating_system: cnl6
paths:
cc: cc
cxx: CC
f77: ftn
fc: ftn
spec: gcc@7.3.0
target: any
- compiler:
environment: {}
extra_rpaths: []
flags: {}
modules: []
operating_system: cnl6
paths:
cc: /opt/cray/pe/craype/2.5.15/bin/cc
cxx: /opt/cray/pe/craype/2.5.15/bin/CC
f77: /opt/cray/pe/craype/2.5.15/bin/ftn
fc: /opt/cray/pe/craype/2.5.15/bin/ftn
spec: intel@18.0.2.199
target: any
``` | 1.0 | Boost fails to build on ANL's Theta - I'm trying to install boost with spack on ANL's Theta machine, using the GNU compilers. I tried version 1.68.0 and 1.67.0. In both cases the build fails when calling `b2 --clean`. When I go in the the build directory and call `./b2 -- clean` myself, I get `Illegal instruction (core dumped)`.
The same happens with Intel compiler instead of GNU.
If I try to build boost manually (i.e. downloading the archive, running `./bootstrap.sh` with the libraries I want, then `./b2` and `./b2 install`) it works fine.
### Steps to reproduce the issue
```console
$ spack install boost
==> diffutils is already installed in /gpfs/mira-home/mdorier/spack/opt/spack/cray-cnl6-mic_knl/gcc-7.3.0/diffutils-3.6-hdksfzqzgtfwvwbvhu7s75u6f7tkudvz
==> bzip2 is already installed in /gpfs/mira-home/mdorier/spack/opt/spack/cray-cnl6-mic_knl/gcc-7.3.0/bzip2-1.0.6-m22cmmtaf36fnfmvwy36dssvltqfw73q
==> zlib is already installed in /gpfs/mira-home/mdorier/spack/opt/spack/cray-cnl6-mic_knl/gcc-7.3.0/zlib-1.2.11-yuj7ryis72kd6iwpq3qmvp627umsbymc
==> Installing boost
==> Fetching https://dl.bintray.com/boostorg/release/1.67.0/source/boost_1_67_0.tar.bz2
######################################################################## 100.0%
==> Staging archive: /gpfs/mira-home/mdorier/spack/var/spack/stage/boost-1.67.0-a5gxl76fce2fobsekfnhvrhsl5j6j6cw/boost_1_67_0.tar.bz2
==> Created stage in /gpfs/mira-home/mdorier/spack/var/spack/stage/boost-1.67.0-a5gxl76fce2fobsekfnhvrhsl5j6j6cw
==> Applied patch python_jam.patch
==> Building boost [Package]
==> Executing phase: 'install'
==> Error: ProcessError: Command exited with status -4:
'./b2' '--clean'
```
### Platform and user environment
```commandline
$ uname -a
Linux thetalogin6 4.4.103-6.38-default #1 SMP Mon Dec 25 20:44:33 UTC 2017 (e4b9067) x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -d
Description: SUSE Linux Enterprise Server 12 SP3
```
- `compilers.yaml`
```
compilers:
- compiler:
environment: {}
extra_rpaths: []
flags: {}
modules:
- PrgEnv-cray
- cce/8.7.3
operating_system: cnl6
paths:
cc: cc
cxx: CC
f77: ftn
fc: ftn
spec: cce@8.7.3
target: any
- compiler:
environment: {}
extra_rpaths: []
flags: {}
modules:
- PrgEnv-gnu
- gcc/7.3.0
operating_system: cnl6
paths:
cc: cc
cxx: CC
f77: ftn
fc: ftn
spec: gcc@7.3.0
target: any
- compiler:
environment: {}
extra_rpaths: []
flags: {}
modules: []
operating_system: cnl6
paths:
cc: /opt/cray/pe/craype/2.5.15/bin/cc
cxx: /opt/cray/pe/craype/2.5.15/bin/CC
f77: /opt/cray/pe/craype/2.5.15/bin/ftn
fc: /opt/cray/pe/craype/2.5.15/bin/ftn
spec: intel@18.0.2.199
target: any
``` | non_priority | boost fails to build on anl s theta i m trying to install boost with spack on anl s theta machine using the gnu compilers i tried version and in both cases the build fails when calling clean when i go in the the build directory and call clean myself i get illegal instruction core dumped the same happens with intel compiler instead of gnu if i try to build boost manually i e downloading the archive running bootstrap sh with the libraries i want then and install it works fine steps to reproduce the issue console spack install boost diffutils is already installed in gpfs mira home mdorier spack opt spack cray mic knl gcc diffutils is already installed in gpfs mira home mdorier spack opt spack cray mic knl gcc zlib is already installed in gpfs mira home mdorier spack opt spack cray mic knl gcc zlib installing boost fetching staging archive gpfs mira home mdorier spack var spack stage boost boost tar created stage in gpfs mira home mdorier spack var spack stage boost applied patch python jam patch building boost executing phase install error processerror command exited with status clean platform and user environment commandline uname a linux default smp mon dec utc gnu linux lsb release d description suse linux enterprise server compilers yaml compilers compiler environment extra rpaths flags modules prgenv cray cce operating system paths cc cc cxx cc ftn fc ftn spec cce target any compiler environment extra rpaths flags modules prgenv gnu gcc operating system paths cc cc cxx cc ftn fc ftn spec gcc target any compiler environment extra rpaths flags modules operating system paths cc opt cray pe craype bin cc cxx opt cray pe craype bin cc opt cray pe craype bin ftn fc opt cray pe craype bin ftn spec intel target any | 0 |
226,825 | 18,044,207,054 | IssuesEvent | 2021-09-18 15:49:53 | logicmoo/logicmoo_workspace | https://api.github.com/repos/logicmoo/logicmoo_workspace | opened | logicmoo.pfc.test.sanity_base.NEG_01V JUnit | Test_9999 logicmoo.pfc.test.sanity_base unit_test NEG_01V | (cd /var/lib/jenkins/workspace/logicmoo_workspace/packs_sys/pfc/t/sanity_base ; timeout --foreground --preserve-status -s SIGKILL -k 10s 10s lmoo-clif neg_01v.pfc)
GH_MASTER_ISSUE_FINFO=
ISSUE_SEARCH: https://github.com/logicmoo/logicmoo_workspace/issues?q=is%3Aissue+label%3ANEG_01V
GITLAB: https://logicmoo.org:2082/gitlab/logicmoo/logicmoo_workspace/-/commit/869479bc8cf913ee2df5ebbe49363a2dad9c9fb3
https://gitlab.logicmoo.org/gitlab/logicmoo/logicmoo_workspace/-/blob/869479bc8cf913ee2df5ebbe49363a2dad9c9fb3/packs_sys/pfc/t/sanity_base/neg_01v.pfc
Latest: https://jenkins.logicmoo.org/job/logicmoo_workspace/lastBuild/testReport/logicmoo.pfc.test.sanity_base/NEG_01V/logicmoo_pfc_test_sanity_base_NEG_01V_JUnit/
This Build: https://jenkins.logicmoo.org/job/logicmoo_workspace/67/testReport/logicmoo.pfc.test.sanity_base/NEG_01V/logicmoo_pfc_test_sanity_base_NEG_01V_JUnit/
GITHUB: https://github.com/logicmoo/logicmoo_workspace/commit/869479bc8cf913ee2df5ebbe49363a2dad9c9fb3
https://github.com/logicmoo/logicmoo_workspace/blob/869479bc8cf913ee2df5ebbe49363a2dad9c9fb3/packs_sys/pfc/t/sanity_base/neg_01v.pfc
```
%
running('/var/lib/jenkins/workspace/logicmoo_workspace/packs_sys/pfc/t/sanity_base/neg_01v.pfc'),
%~ this_test_might_need( :-( use_module( library(logicmoo_plarkc))))
:- use_module(library(statistics)).
%:- mpred_notrace_exec.
% reset runtime counter
%:- mpred_notrace_exec.
% reset runtime counter
:- statistics(runtime,_Secs).
~path(X,X).
path(1,2).
path(2,3).
path(3,4).
path(1,1).
:- mpred_test(path(3, 4)).
%~ mpred_test("Test_0001_Line_0000__path_3",baseKB:path(3,4))
%~ FIlE: * https://logicmoo.org:2082/gitlab/logicmoo/logicmoo_workspace/-/blob/master/packs_sys/pfc/t/sanity_base/neg_01v.pfc#L20
/*~
%~ mpred_test("Test_0001_Line_0000__path_3",baseKB:path(3,4))
passed=info(why_was_true(baseKB:path(3,4)))
Justifications for path(3,4):
[36m 1.1 mfl4(_,baseKB,'* https://logicmoo.org:2082/gitlab/logicmoo/logicmoo_workspace/-/blob/master/packs_sys/pfc/t/sanity_base/neg_01v.pfc#L17 ',17) [0m
name ='logicmoo.pfc.test.sanity_base.NEG_01V-Test_0001_Line_0000__path_3'.
JUNIT_CLASSNAME ='logicmoo.pfc.test.sanity_base.NEG_01V'.
JUNIT_CMD ='timeout --foreground --preserve-status -s SIGKILL -k 10s 10s lmoo-clif neg_01v.pfc'.
% saving_junit: /var/lib/jenkins/workspace/logicmoo_workspace/test_results/jenkins/Report-logicmoo-junit-test-sanity_base-vSTARv0vSTARvvDOTvvSTARv-Units-logicmoo.pfc.test.sanity_base.NEG_01V-Test_0001_Line_0000__path_3-junit.xml
~*/
:- mpred_test(path(2, 3)).
%~ mpred_test("Test_0002_Line_0000__path_2",baseKB:path(2,3))
%~ FIlE: * https://logicmoo.org:2082/gitlab/logicmoo/logicmoo_workspace/-/blob/master/packs_sys/pfc/t/sanity_base/neg_01v.pfc#L21
/*~
%~ mpred_test("Test_0002_Line_0000__path_2",baseKB:path(2,3))
passed=info(why_was_true(baseKB:path(2,3)))
Justifications for path(2,3):
[36m 1.1 mfl4(_,baseKB,'* https://logicmoo.org:2082/gitlab/logicmoo/logicmoo_workspace/-/blob/master/packs_sys/pfc/t/sanity_base/neg_01v.pfc#L16 ',16) [0m
name ='logicmoo.pfc.test.sanity_base.NEG_01V-Test_0002_Line_0000__path_2'.
JUNIT_CLASSNAME ='logicmoo.pfc.test.sanity_base.NEG_01V'.
JUNIT_CMD ='timeout --foreground --preserve-status -s SIGKILL -k 10s 10s lmoo-clif neg_01v.pfc'.
% saving_junit: /var/lib/jenkins/workspace/logicmoo_workspace/test_results/jenkins/Report-logicmoo-junit-test-sanity_base-vSTARv0vSTARvvDOTvvSTARv-Units-logicmoo.pfc.test.sanity_base.NEG_01V-Test_0002_Line_0000__path_2-junit.xml
~*/
:- mpred_test(path(1, 2)).
%~ mpred_test("Test_0003_Line_0000__path_1",baseKB:path(1,2))
%~ FIlE: * https://logicmoo.org:2082/gitlab/logicmoo/logicmoo_workspace/-/blob/master/packs_sys/pfc/t/sanity_base/neg_01v.pfc#L22
/*~
%~ mpred_test("Test_0003_Line_0000__path_1",baseKB:path(1,2))
passed=info(why_was_true(baseKB:path(1,2)))
Justifications for path(1,2):
[36m 1.1 mfl4(_,baseKB,'* https://logicmoo.org:2082/gitlab/logicmoo/logicmoo_workspace/-/blob/master/packs_sys/pfc/t/sanity_base/neg_01v.pfc#L15 ',15) [0m
name ='logicmoo.pfc.test.sanity_base.NEG_01V-Test_0003_Line_0000__path_1'.
JUNIT_CLASSNAME ='logicmoo.pfc.test.sanity_base.NEG_01V'.
JUNIT_CMD ='timeout --foreground --preserve-status -s SIGKILL -k 10s 10s lmoo-clif neg_01v.pfc'.
% saving_junit: /var/lib/jenkins/workspace/logicmoo_workspace/test_results/jenkins/Report-logicmoo-junit-test-sanity_base-vSTARv0vSTARvvDOTvvSTARv-Units-logicmoo.pfc.test.sanity_base.NEG_01V-Test_0003_Line_0000__path_1-junit.xml
~*/
:- mpred_test(~path(1,1)).
%~ mpred_test("Test_0004_Line_0000__path_1",baseKB: ~path(1,1))
/*~
%~ mpred_test("Test_0004_Line_0000__path_1",baseKB: ~path(1,1))
^ Call: (68) [baseKB] ~path(1, 1)
^ Unify: (68) [baseKB] ~ (baseKB:path(1, 1))
^ Call: (75) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_in_code0(baseKB:path(1, 1)), info(pfc_lib:neg_in_code0(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, 1320, pfc_lib:trace_or_throw(looped(pfc_lib:neg_in_code0(baseKB:path(1, 1)))))
^ Unify: (75) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_in_code0(baseKB:path(1, 1)), info(pfc_lib:neg_in_code0(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, 1320, pfc_lib:trace_or_throw(looped(pfc_lib:neg_in_code0(baseKB:path(1, 1)))))
Call: (76) [system] set_prolog_flag(last_call_optimisation, false)
Exit: (76) [system] set_prolog_flag(last_call_optimisation, false)
^ Call: (76) [loop_check] prolog_frame_attribute(1320, parent_goal, loop_check_term_frame(_51782, info(pfc_lib:neg_in_code0(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, _51788, _51790))
^ Fail: (76) [loop_check] prolog_frame_attribute(1320, parent_goal, loop_check_term_frame(_51782, info(pfc_lib:neg_in_code0(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, _51788, _51790))
^ Redo: (75) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_in_code0(baseKB:path(1, 1)), info(pfc_lib:neg_in_code0(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, 1320, pfc_lib:trace_or_throw(looped(pfc_lib:neg_in_code0(baseKB:path(1, 1)))))
Call: (76) [pfc_lib] neg_in_code0(baseKB:path(1, 1))
Unify: (76) [pfc_lib] neg_in_code0(baseKB:path(1, 1))
^ Call: (82) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_may_naf(baseKB:path(1, 1)), info(pfc_lib:neg_may_naf(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, 1459, pfc_lib:trace_or_throw(looped(pfc_lib:neg_may_naf(baseKB:path(1, 1)))))
^ Unify: (82) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_may_naf(baseKB:path(1, 1)), info(pfc_lib:neg_may_naf(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, 1459, pfc_lib:trace_or_throw(looped(pfc_lib:neg_may_naf(baseKB:path(1, 1)))))
Call: (83) [system] set_prolog_flag(last_call_optimisation, false)
Exit: (83) [system] set_prolog_flag(last_call_optimisation, false)
^ Call: (83) [loop_check] prolog_frame_attribute(1459, parent_goal, loop_check_term_frame(_57506, info(pfc_lib:neg_may_naf(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, _57512, _57514))
^ Fail: (83) [loop_check] prolog_frame_attribute(1459, parent_goal, loop_check_term_frame(_57506, info(pfc_lib:neg_may_naf(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, _57512, _57514))
^ Redo: (82) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_may_naf(baseKB:path(1, 1)), info(pfc_lib:neg_may_naf(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, 1459, pfc_lib:trace_or_throw(looped(pfc_lib:neg_may_naf(baseKB:path(1, 1)))))
Call: (83) [pfc_lib] neg_may_naf(baseKB:path(1, 1))
Unify: (83) [pfc_lib] neg_may_naf(baseKB:path(1, 1))
^ Call: (87) [pfc_lib] hook_database:clause_i(pfc_lib:prologNegByFailure(path), true, _60838)
^ Unify: (87) [pfc_lib] hook_database:clause_i(pfc_lib:prologNegByFailure(path), true, _60838)
^ Call: (88) [system] clause(pfc_lib:prologNegByFailure(path), true, _60838)
^ Fail: (88) [system] clause(pfc_lib:prologNegByFailure(path), true, _60838)
^ Fail: (87) [pfc_lib] hook_database:clause_i(pfc_lib:prologNegByFailure(path), true, _60838)
Unify: (83) [pfc_lib] neg_may_naf(baseKB:path(1, 1))
^ Call: (84) [pfc_lib] ucatch:is_ftCompound(baseKB:path(1, 1))
^ Unify: (84) [pfc_lib] ucatch:is_ftCompound(baseKB:path(1, 1))
^ Call: (85) [pfc_lib] ucatch:is_ftVar(baseKB:path(1, 1))
^ Unify: (85) [pfc_lib] ucatch:is_ftVar(baseKB:path(1, 1))
^ Fail: (85) [pfc_lib] ucatch:is_ftVar(baseKB:path(1, 1))
^ Redo: (84) [pfc_lib] ucatch:is_ftCompound(baseKB:path(1, 1))
^ Exit: (84) [pfc_lib] ucatch:is_ftCompound(baseKB:path(1, 1))
^ Call: (88) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologHybrid), _69008), call(_69008)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))))
^ Unify: (88) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologHybrid), _69008), call(_69008)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))))
^ Call: (90) [hook_database] clause(mpred_prop(baseKB, path, 2, prologHybrid), _69008)
^ Fail: (90) [hook_database] clause(mpred_prop(baseKB, path, 2, prologHybrid), _69008)
Call: (90) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))
Unify: (90) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))
^ Call: (91) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologHybrid), _72794))
^ Unify: (91) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologHybrid), _72794))
^ Call: (92) [baseKB] clause(mpred_prop(baseKB, path, 2, prologHybrid), _72794)
^ Fail: (92) [baseKB] clause(mpred_prop(baseKB, path, 2, prologHybrid), _72794)
^ Fail: (91) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologHybrid), _72794))
Fail: (90) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))
^ Fail: (88) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologHybrid), _69008), call(_69008)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))))
^ Call: (87) [pfc_lib] baseKB:mpred_database_term(path, 2, _77214)
^ Unify: (87) [pfc_lib] baseKB:mpred_database_term(path, 2, syntaxic(_77784))
^ Call: (88) [pfc_lib] mpred_database_term_syntax(path, 2, _77784)
^ Fail: (88) [pfc_lib] mpred_database_term_syntax(path, 2, _77784)
^ Redo: (87) [pfc_lib] baseKB:mpred_database_term(path, 2, _79786)
^ Unify: (87) [pfc_lib] baseKB:mpred_database_term(path, 2, _80414)
^ Call: (88) [pfc_lib] mpred_core_database_term(path, 2, _80982)
^ Fail: (88) [pfc_lib] mpred_core_database_term(path, 2, _80982)
^ Fail: (87) [pfc_lib] baseKB:mpred_database_term(path, 2, _82356)
^ Call: (86) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologBuiltin), _82960), call(_82960)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))))
^ Unify: (86) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologBuiltin), _82960), call(_82960)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))))
^ Call: (88) [hook_database] clause(mpred_prop(baseKB, path, 2, prologBuiltin), _82960)
^ Fail: (88) [hook_database] clause(mpred_prop(baseKB, path, 2, prologBuiltin), _82960)
Call: (88) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))
Unify: (88) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))
^ Call: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologBuiltin), _86746))
^ Unify: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologBuiltin), _86746))
^ Call: (90) [baseKB] clause(mpred_prop(baseKB, path, 2, prologBuiltin), _86746)
^ Fail: (90) [baseKB] clause(mpred_prop(baseKB, path, 2, prologBuiltin), _86746)
^ Fail: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologBuiltin), _86746))
Fail: (88) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))
^ Fail: (86) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologBuiltin), _82960), call(_82960)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))))
^ Call: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(_91112, path, 2, prologHybrid), _91142), call(_91142)*->true;clause_b(baseKB:mpred_prop(_91112, path, 2, prologHybrid))))
^ Unify: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(_91112, path, 2, prologHybrid), _91142), call(_91142)*->true;clause_b(baseKB:mpred_prop(_91112, path, 2, prologHybrid))))
^ Call: (91) [hook_database] clause(mpred_prop(_91112, path, 2, prologHybrid), _91142)
^ Fail: (91) [hook_database] clause(mpred_prop(_91112, path, 2, prologHybrid), _91142)
Call: (91) [hook_database] clause_b(baseKB:mpred_prop(_91112, path, 2, prologHybrid))
Unify: (91) [hook_database] clause_b(baseKB:mpred_prop(_91112, path, 2, prologHybrid))
^ Call: (92) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(_91112, path, 2, prologHybrid), _94928))
^ Unify: (92) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(_91112, path, 2, prologHybrid), _94928))
^ Call: (93) [baseKB] clause(mpred_prop(_91112, path, 2, prologHybrid), _94928)
^ Fail: (93) [baseKB] clause(mpred_prop(_91112, path, 2, prologHybrid), _94928)
^ Fail: (92) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(_91112, path, 2, prologHybrid), _94928))
Fail: (91) [hook_database] clause_b(baseKB:mpred_prop(_91112, path, 2, prologHybrid))
^ Fail: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(_91112, path, 2, prologHybrid), _91142), call(_91142)*->true;clause_b(baseKB:mpred_prop(_91112, path, 2, prologHybrid))))
^ Call: (88) [pfc_lib] baseKB:mpred_database_term(path, 2, _99348)
^ Unify: (88) [pfc_lib] baseKB:mpred_database_term(path, 2, syntaxic(_99918))
^ Call: (89) [pfc_lib] mpred_database_term_syntax(path, 2, _99918)
^ Fail: (89) [pfc_lib] mpred_database_term_syntax(path, 2, _99918)
^ Redo: (88) [pfc_lib] baseKB:mpred_database_term(path, 2, _101920)
^ Unify: (88) [pfc_lib] baseKB:mpred_database_term(path, 2, _102548)
^ Call: (89) [pfc_lib] mpred_core_database_term(path, 2, _103116)
^ Fail: (89) [pfc_lib] mpred_core_database_term(path, 2, _103116)
^ Fail: (88) [pfc_lib] baseKB:mpred_database_term(path, 2, _104490)
Call: (98) [$autoload] leave_sandbox(_105088)
Unify: (98) [$autoload] leave_sandbox(_105088)
Exit: (98) [$autoload] leave_sandbox(false)
Call: (97) [$autoload] restore_sandbox(false)
Unify: (97) [$autoload] restore_sandbox(false)
Exit: (97) [$autoload] restore_sandbox(false)
Fail: (83) [pfc_lib] neg_may_naf(baseKB:path(1, 1))
^ Fail: (82) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_may_naf(baseKB:path(1, 1)), info(pfc_lib:neg_may_naf(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, 1459, pfc_lib:trace_or_throw(looped(pfc_lib:neg_may_naf(baseKB:path(1, 1)))))
Fail: (76) [pfc_lib] neg_in_code0(baseKB:path(1, 1))
^ Fail: (75) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_in_code0(baseKB:path(1, 1)), info(pfc_lib:neg_in_code0(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, 1320, pfc_lib:trace_or_throw(looped(pfc_lib:neg_in_code0(baseKB:path(1, 1)))))
^ Fail: (68) [baseKB] ~ (baseKB:path(1, 1))
^ Call: (68) [must_sanity] must_sanity:mquietly_if(true, rtrace:tAt_normal)
^ Unify: (68) [must_sanity] must_sanity:mquietly_if(true, rtrace:tAt_normal)
failure=info((why_was_true(baseKB:(\+ ~path(1,1))),rtrace(baseKB: ~path(1,1))))
no_proof_for(\+ ~path(1,1)).
no_proof_for(\+ ~path(1,1)).
no_proof_for(\+ ~path(1,1)).
name ='logicmoo.pfc.test.sanity_base.NEG_01V-Test_0004_Line_0000__path_1'.
JUNIT_CLASSNAME ='logicmoo.pfc.test.sanity_base.NEG_01V'.
JUNIT_CMD ='timeout --foreground --preserve-status -s SIGKILL -k 10s 10s lmoo-clif neg_01v.pfc'.
% saving_junit: /var/lib/jenkins/workspace/logicmoo_workspace/test_results/jenkins/Report-logicmoo-junit-test-sanity_base-vSTARv0vSTARvvDOTvvSTARv-Units-logicmoo.pfc.test.sanity_base.NEG_01V-Test_0004_Line_0000__path_1-junit.xml
~*/
:- mpred_test(~path(2,2)).
%~ /var/lib/jenkins/workspace/logicmoo_workspace/packs_sys/pfc/t/sanity_base/neg_01v.pfc:24
%~ mpred_test("Test_0005_Line_0000__path_2",baseKB: ~path(2,2))
/*~
%~ mpred_test("Test_0005_Line_0000__path_2",baseKB: ~path(2,2))
^ Call: (68) [baseKB] ~path(2, 2)
^ Unify: (68) [baseKB] ~ (baseKB:path(2, 2))
^ Call: (75) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_in_code0(baseKB:path(2, 2)), info(pfc_lib:neg_in_code0(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, 1189, pfc_lib:trace_or_throw(looped(pfc_lib:neg_in_code0(baseKB:path(2, 2)))))
^ Unify: (75) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_in_code0(baseKB:path(2, 2)), info(pfc_lib:neg_in_code0(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, 1189, pfc_lib:trace_or_throw(looped(pfc_lib:neg_in_code0(baseKB:path(2, 2)))))
Call: (76) [system] set_prolog_flag(last_call_optimisation, false)
Exit: (76) [system] set_prolog_flag(last_call_optimisation, false)
^ Call: (76) [loop_check] prolog_frame_attribute(1189, parent_goal, loop_check_term_frame(_93356, info(pfc_lib:neg_in_code0(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, _93362, _93364))
^ Fail: (76) [loop_check] prolog_frame_attribute(1189, parent_goal, loop_check_term_frame(_93356, info(pfc_lib:neg_in_code0(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, _93362, _93364))
^ Redo: (75) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_in_code0(baseKB:path(2, 2)), info(pfc_lib:neg_in_code0(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, 1189, pfc_lib:trace_or_throw(looped(pfc_lib:neg_in_code0(baseKB:path(2, 2)))))
Call: (76) [pfc_lib] neg_in_code0(baseKB:path(2, 2))
Unify: (76) [pfc_lib] neg_in_code0(baseKB:path(2, 2))
^ Call: (82) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_may_naf(baseKB:path(2, 2)), info(pfc_lib:neg_may_naf(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, 1328, pfc_lib:trace_or_throw(looped(pfc_lib:neg_may_naf(baseKB:path(2, 2)))))
^ Unify: (82) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_may_naf(baseKB:path(2, 2)), info(pfc_lib:neg_may_naf(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, 1328, pfc_lib:trace_or_throw(looped(pfc_lib:neg_may_naf(baseKB:path(2, 2)))))
Call: (83) [system] set_prolog_flag(last_call_optimisation, false)
Exit: (83) [system] set_prolog_flag(last_call_optimisation, false)
^ Call: (83) [loop_check] prolog_frame_attribute(1328, parent_goal, loop_check_term_frame(_99080, info(pfc_lib:neg_may_naf(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, _99086, _99088))
^ Fail: (83) [loop_check] prolog_frame_attribute(1328, parent_goal, loop_check_term_frame(_99080, info(pfc_lib:neg_may_naf(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, _99086, _99088))
^ Redo: (82) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_may_naf(baseKB:path(2, 2)), info(pfc_lib:neg_may_naf(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, 1328, pfc_lib:trace_or_throw(looped(pfc_lib:neg_may_naf(baseKB:path(2, 2)))))
Call: (83) [pfc_lib] neg_may_naf(baseKB:path(2, 2))
Unify: (83) [pfc_lib] neg_may_naf(baseKB:path(2, 2))
^ Call: (87) [pfc_lib] hook_database:clause_i(pfc_lib:prologNegByFailure(path), true, _102412)
^ Unify: (87) [pfc_lib] hook_database:clause_i(pfc_lib:prologNegByFailure(path), true, _102412)
^ Call: (88) [system] clause(pfc_lib:prologNegByFailure(path), true, _102412)
^ Fail: (88) [system] clause(pfc_lib:prologNegByFailure(path), true, _102412)
^ Fail: (87) [pfc_lib] hook_database:clause_i(pfc_lib:prologNegByFailure(path), true, _102412)
Unify: (83) [pfc_lib] neg_may_naf(baseKB:path(2, 2))
^ Call: (84) [pfc_lib] ucatch:is_ftCompound(baseKB:path(2, 2))
^ Unify: (84) [pfc_lib] ucatch:is_ftCompound(baseKB:path(2, 2))
^ Call: (85) [pfc_lib] ucatch:is_ftVar(baseKB:path(2, 2))
^ Unify: (85) [pfc_lib] ucatch:is_ftVar(baseKB:path(2, 2))
^ Fail: (85) [pfc_lib] ucatch:is_ftVar(baseKB:path(2, 2))
^ Redo: (84) [pfc_lib] ucatch:is_ftCompound(baseKB:path(2, 2))
^ Exit: (84) [pfc_lib] ucatch:is_ftCompound(baseKB:path(2, 2))
^ Call: (88) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologHybrid), _110582), call(_110582)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))))
^ Unify: (88) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologHybrid), _110582), call(_110582)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))))
^ Call: (90) [hook_database] clause(mpred_prop(baseKB, path, 2, prologHybrid), _110582)
^ Fail: (90) [hook_database] clause(mpred_prop(baseKB, path, 2, prologHybrid), _110582)
Call: (90) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))
Unify: (90) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))
^ Call: (91) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologHybrid), _114368))
^ Unify: (91) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologHybrid), _114368))
^ Call: (92) [baseKB] clause(mpred_prop(baseKB, path, 2, prologHybrid), _114368)
^ Fail: (92) [baseKB] clause(mpred_prop(baseKB, path, 2, prologHybrid), _114368)
^ Fail: (91) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologHybrid), _114368))
Fail: (90) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))
^ Fail: (88) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologHybrid), _110582), call(_110582)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))))
^ Call: (87) [pfc_lib] baseKB:mpred_database_term(path, 2, _118788)
^ Unify: (87) [pfc_lib] baseKB:mpred_database_term(path, 2, syntaxic(_119358))
^ Call: (88) [pfc_lib] mpred_database_term_syntax(path, 2, _119358)
^ Fail: (88) [pfc_lib] mpred_database_term_syntax(path, 2, _119358)
^ Redo: (87) [pfc_lib] baseKB:mpred_database_term(path, 2, _121360)
^ Unify: (87) [pfc_lib] baseKB:mpred_database_term(path, 2, _121988)
^ Call: (88) [pfc_lib] mpred_core_database_term(path, 2, _122556)
^ Fail: (88) [pfc_lib] mpred_core_database_term(path, 2, _122556)
^ Fail: (87) [pfc_lib] baseKB:mpred_database_term(path, 2, _123930)
^ Call: (86) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologBuiltin), _124534), call(_124534)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))))
^ Unify: (86) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologBuiltin), _124534), call(_124534)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))))
^ Call: (88) [hook_database] clause(mpred_prop(baseKB, path, 2, prologBuiltin), _124534)
^ Fail: (88) [hook_database] clause(mpred_prop(baseKB, path, 2, prologBuiltin), _124534)
Call: (88) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))
Unify: (88) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))
^ Call: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologBuiltin), _128320))
^ Unify: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologBuiltin), _128320))
^ Call: (90) [baseKB] clause(mpred_prop(baseKB, path, 2, prologBuiltin), _128320)
^ Fail: (90) [baseKB] clause(mpred_prop(baseKB, path, 2, prologBuiltin), _128320)
^ Fail: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologBuiltin), _128320))
Fail: (88) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))
^ Fail: (86) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologBuiltin), _124534), call(_124534)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))))
^ Call: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(_132686, path, 2, prologHybrid), _132716), call(_132716)*->true;clause_b(baseKB:mpred_prop(_132686, path, 2, prologHybrid))))
^ Unify: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(_132686, path, 2, prologHybrid), _132716), call(_132716)*->true;clause_b(baseKB:mpred_prop(_132686, path, 2, prologHybrid))))
^ Call: (91) [hook_database] clause(mpred_prop(_132686, path, 2, prologHybrid), _132716)
^ Fail: (91) [hook_database] clause(mpred_prop(_132686, path, 2, prologHybrid), _132716)
Call: (91) [hook_database] clause_b(baseKB:mpred_prop(_132686, path, 2, prologHybrid))
Unify: (91) [hook_database] clause_b(baseKB:mpred_prop(_132686, path, 2, prologHybrid))
^ Call: (92) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(_132686, path, 2, prologHybrid), _136502))
^ Unify: (92) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(_132686, path, 2, prologHybrid), _136502))
^ Call: (93) [baseKB] clause(mpred_prop(_132686, path, 2, prologHybrid), _136502)
^ Fail: (93) [baseKB] clause(mpred_prop(_132686, path, 2, prologHybrid), _136502)
^ Fail: (92) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(_132686, path, 2, prologHybrid), _136502))
Fail: (91) [hook_database] clause_b(baseKB:mpred_prop(_132686, path, 2, prologHybrid))
^ Fail: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(_132686, path, 2, prologHybrid), _132716), call(_132716)*->true;clause_b(baseKB:mpred_prop(_132686, path, 2, prologHybrid))))
^ Call: (88) [pfc_lib] baseKB:mpred_database_term(path, 2, _140922)
^ Unify: (88) [pfc_lib] baseKB:mpred_database_term(path, 2, syntaxic(_141492))
^ Call: (89) [pfc_lib] mpred_database_term_syntax(path, 2, _141492)
^ Fail: (89) [pfc_lib] mpred_database_term_syntax(path, 2, _141492)
^ Redo: (88) [pfc_lib] baseKB:mpred_database_term(path, 2, _143494)
^ Unify: (88) [pfc_lib] baseKB:mpred_database_term(path, 2, _144122)
^ Call: (89) [pfc_lib] mpred_core_database_term(path, 2, _144690)
^ Fail: (89) [pfc_lib] mpred_core_database_term(path, 2, _144690)
^ Fail: (88) [pfc_lib] baseKB:mpred_database_term(path, 2, _146064)
Call: (98) [$autoload] leave_sandbox(_146662)
Unify: (98) [$autoload] leave_sandbox(_146662)
Exit: (98) [$autoload] leave_sandbox(false)
Call: (97) [$autoload] restore_sandbox(false)
Unify: (97) [$autoload] restore_sandbox(false)
Exit: (97) [$autoload] restore_sandbox(false)
Fail: (83) [pfc_lib] neg_may_naf(baseKB:path(2, 2))
^ Fail: (82) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_may_naf(baseKB:path(2, 2)), info(pfc_lib:neg_may_naf(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, 1328, pfc_lib:trace_or_throw(looped(pfc_lib:neg_may_naf(baseKB:path(2, 2)))))
Fail: (76) [pfc_lib] neg_in_code0(baseKB:path(2, 2))
^ Fail: (75) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_in_code0(baseKB:path(2, 2)), info(pfc_lib:neg_in_code0(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, 1189, pfc_lib:trace_or_throw(looped(pfc_lib:neg_in_code0(baseKB:path(2, 2)))))
^ Fail: (68) [baseKB] ~ (baseKB:path(2, 2))
^ Call: (68) [must_sanity] must_sanity:mquietly_if(true, rtrace:tAt_normal)
^ Unify: (68) [must_sanity] must_sanity:mquietly_if(true, rtrace:tAt_normal)
failure=info((why_was_true(baseKB:(\+ ~path(2,2))),rtrace(baseKB: ~path(2,2))))
no_proof_for(\+ ~path(2,2)).
no_proof_for(\+ ~path(2,2)).
no_proof_for(\+ ~path(2,2)).
name ='logicmoo.pfc.test.sanity_base.NEG_01V-Test_0005_Line_0000__path_2'.
JUNIT_CLASSNAME ='logicmoo.pfc.test.sanity_base.NEG_01V'.
JUNIT_CMD ='timeout --foreground --preserve-status -s SIGKILL -k 10s 10s lmoo-clif neg_01v.pfc'.
% saving_junit: /var/lib/jenkins/workspace/logicmoo_workspace/test_results/jenkins/Report-logicmoo-junit-test-sanity_base-vSTARv0vSTARvvDOTvvSTARv-Units-logicmoo.pfc.test.sanity_base.NEG_01V-Test_0005_Line_0000__path_2-junit.xml
~*/
/*
:- mpred_test(\+path(1,1)).
:- mpred_test(\+path(2,2)).
*/
:- mpred_test(\+path(3,1)).
%~ /var/lib/jenkins/workspace/logicmoo_workspace/packs_sys/pfc/t/sanity_base/neg_01v.pfc:32
%~ mpred_test("Test_0006_Line_0000__naf_path_3",baseKB:(\+path(3,1)))
/*~
%~ mpred_test("Test_0006_Line_0000__naf_path_3",baseKB:(\+path(3,1)))
passed=info(why_was_true(baseKB:(\+path(3,1))))
no_proof_for(\+path(3,1)).
no_proof_for(\+path(3,1)).
no_proof_for(\+path(3,1)).
name ='logicmoo.pfc.test.sanity_base.NEG_01V-Test_0006_Line_0000__naf_path_3'.
JUNIT_CLASSNAME ='logicmoo.pfc.test.sanity_base.NEG_01V'.
JUNIT_CMD ='timeout --foreground --preserve-status -s SIGKILL -k 10s 10s lmoo-clif neg_01v.pfc'.
% saving_junit: /var/lib/jenkins/workspace/logicmoo_workspace/test_results/jenkins/Report-logicmoo-junit-test-sanity_base-vSTARv0vSTARvvDOTvvSTARv-Units-logicmoo.pfc.test.sanity_base.NEG_01V-Test_0006_Line_0000__naf_path_3-junit.xml
~*/
:- mpred_test(\+ ~path(1,5)).
%~ mpred_test("Test_0007_Line_0000__naf_path_1",baseKB:(\+ ~path(1,5)))
/*~
%~ mpred_test("Test_0007_Line_0000__naf_path_1",baseKB:(\+ ~path(1,5)))
passed=info(why_was_true(baseKB:(\+ ~path(1,5))))
no_proof_for(\+ ~path(1,5)).
no_proof_for(\+ ~path(1,5)).
no_proof_for(\+ ~path(1,5)).
name ='logicmoo.pfc.test.sanity_base.NEG_01V-Test_0007_Line_0000__naf_path_1'.
JUNIT_CLASSNAME ='logicmoo.pfc.test.sanity_base.NEG_01V'.
JUNIT_CMD ='timeout --foreground --preserve-status -s SIGKILL -k 10s 10s lmoo-clif neg_01v.pfc'.
% saving_junit: /var/lib/jenkins/workspace/logicmoo_workspace/test_results/jenkins/Report-logicmoo-junit-test-sanity_base-vSTARv0vSTARvvDOTvvSTARv-Units-logicmoo.pfc.test.sanity_base.NEG_01V-Test_0007_Line_0000__naf_path_1-junit.xml
~*/
:- break.
%~ skipped(blocks_on_input,break)
%~ unused(save_junit_results)
%~ test_completed_exit(6)
:- dynamic junit_prop/3.
:- dynamic junit_prop/3.
:- dynamic junit_prop/3.
```
totalTime=1
ISSUE_SEARCH: https://github.com/logicmoo/logicmoo_workspace/issues?q=is%3Aissue+label%3ANEG_01V
GITLAB: https://logicmoo.org:2082/gitlab/logicmoo/logicmoo_workspace/-/commit/869479bc8cf913ee2df5ebbe49363a2dad9c9fb3
https://gitlab.logicmoo.org/gitlab/logicmoo/logicmoo_workspace/-/blob/869479bc8cf913ee2df5ebbe49363a2dad9c9fb3/packs_sys/pfc/t/sanity_base/neg_01v.pfc
Latest: https://jenkins.logicmoo.org/job/logicmoo_workspace/lastBuild/testReport/logicmoo.pfc.test.sanity_base/NEG_01V/logicmoo_pfc_test_sanity_base_NEG_01V_JUnit/
This Build: https://jenkins.logicmoo.org/job/logicmoo_workspace/67/testReport/logicmoo.pfc.test.sanity_base/NEG_01V/logicmoo_pfc_test_sanity_base_NEG_01V_JUnit/
GITHUB: https://github.com/logicmoo/logicmoo_workspace/commit/869479bc8cf913ee2df5ebbe49363a2dad9c9fb3
https://github.com/logicmoo/logicmoo_workspace/blob/869479bc8cf913ee2df5ebbe49363a2dad9c9fb3/packs_sys/pfc/t/sanity_base/neg_01v.pfc
FAILED: /var/lib/jenkins/workspace/logicmoo_workspace/bin/lmoo-junit-minor -k neg_01v.pfc (returned 6)
| 3.0 | logicmoo.pfc.test.sanity_base.NEG_01V JUnit - (cd /var/lib/jenkins/workspace/logicmoo_workspace/packs_sys/pfc/t/sanity_base ; timeout --foreground --preserve-status -s SIGKILL -k 10s 10s lmoo-clif neg_01v.pfc)
GH_MASTER_ISSUE_FINFO=
ISSUE_SEARCH: https://github.com/logicmoo/logicmoo_workspace/issues?q=is%3Aissue+label%3ANEG_01V
GITLAB: https://logicmoo.org:2082/gitlab/logicmoo/logicmoo_workspace/-/commit/869479bc8cf913ee2df5ebbe49363a2dad9c9fb3
https://gitlab.logicmoo.org/gitlab/logicmoo/logicmoo_workspace/-/blob/869479bc8cf913ee2df5ebbe49363a2dad9c9fb3/packs_sys/pfc/t/sanity_base/neg_01v.pfc
Latest: https://jenkins.logicmoo.org/job/logicmoo_workspace/lastBuild/testReport/logicmoo.pfc.test.sanity_base/NEG_01V/logicmoo_pfc_test_sanity_base_NEG_01V_JUnit/
This Build: https://jenkins.logicmoo.org/job/logicmoo_workspace/67/testReport/logicmoo.pfc.test.sanity_base/NEG_01V/logicmoo_pfc_test_sanity_base_NEG_01V_JUnit/
GITHUB: https://github.com/logicmoo/logicmoo_workspace/commit/869479bc8cf913ee2df5ebbe49363a2dad9c9fb3
https://github.com/logicmoo/logicmoo_workspace/blob/869479bc8cf913ee2df5ebbe49363a2dad9c9fb3/packs_sys/pfc/t/sanity_base/neg_01v.pfc
```
%
running('/var/lib/jenkins/workspace/logicmoo_workspace/packs_sys/pfc/t/sanity_base/neg_01v.pfc'),
%~ this_test_might_need( :-( use_module( library(logicmoo_plarkc))))
:- use_module(library(statistics)).
%:- mpred_notrace_exec.
% reset runtime counter
%:- mpred_notrace_exec.
% reset runtime counter
:- statistics(runtime,_Secs).
~path(X,X).
path(1,2).
path(2,3).
path(3,4).
path(1,1).
:- mpred_test(path(3, 4)).
%~ mpred_test("Test_0001_Line_0000__path_3",baseKB:path(3,4))
%~ FIlE: * https://logicmoo.org:2082/gitlab/logicmoo/logicmoo_workspace/-/blob/master/packs_sys/pfc/t/sanity_base/neg_01v.pfc#L20
/*~
%~ mpred_test("Test_0001_Line_0000__path_3",baseKB:path(3,4))
passed=info(why_was_true(baseKB:path(3,4)))
Justifications for path(3,4):
[36m 1.1 mfl4(_,baseKB,'* https://logicmoo.org:2082/gitlab/logicmoo/logicmoo_workspace/-/blob/master/packs_sys/pfc/t/sanity_base/neg_01v.pfc#L17 ',17) [0m
name ='logicmoo.pfc.test.sanity_base.NEG_01V-Test_0001_Line_0000__path_3'.
JUNIT_CLASSNAME ='logicmoo.pfc.test.sanity_base.NEG_01V'.
JUNIT_CMD ='timeout --foreground --preserve-status -s SIGKILL -k 10s 10s lmoo-clif neg_01v.pfc'.
% saving_junit: /var/lib/jenkins/workspace/logicmoo_workspace/test_results/jenkins/Report-logicmoo-junit-test-sanity_base-vSTARv0vSTARvvDOTvvSTARv-Units-logicmoo.pfc.test.sanity_base.NEG_01V-Test_0001_Line_0000__path_3-junit.xml
~*/
:- mpred_test(path(2, 3)).
%~ mpred_test("Test_0002_Line_0000__path_2",baseKB:path(2,3))
%~ FIlE: * https://logicmoo.org:2082/gitlab/logicmoo/logicmoo_workspace/-/blob/master/packs_sys/pfc/t/sanity_base/neg_01v.pfc#L21
/*~
%~ mpred_test("Test_0002_Line_0000__path_2",baseKB:path(2,3))
passed=info(why_was_true(baseKB:path(2,3)))
Justifications for path(2,3):
[36m 1.1 mfl4(_,baseKB,'* https://logicmoo.org:2082/gitlab/logicmoo/logicmoo_workspace/-/blob/master/packs_sys/pfc/t/sanity_base/neg_01v.pfc#L16 ',16) [0m
name ='logicmoo.pfc.test.sanity_base.NEG_01V-Test_0002_Line_0000__path_2'.
JUNIT_CLASSNAME ='logicmoo.pfc.test.sanity_base.NEG_01V'.
JUNIT_CMD ='timeout --foreground --preserve-status -s SIGKILL -k 10s 10s lmoo-clif neg_01v.pfc'.
% saving_junit: /var/lib/jenkins/workspace/logicmoo_workspace/test_results/jenkins/Report-logicmoo-junit-test-sanity_base-vSTARv0vSTARvvDOTvvSTARv-Units-logicmoo.pfc.test.sanity_base.NEG_01V-Test_0002_Line_0000__path_2-junit.xml
~*/
:- mpred_test(path(1, 2)).
%~ mpred_test("Test_0003_Line_0000__path_1",baseKB:path(1,2))
%~ FIlE: * https://logicmoo.org:2082/gitlab/logicmoo/logicmoo_workspace/-/blob/master/packs_sys/pfc/t/sanity_base/neg_01v.pfc#L22
/*~
%~ mpred_test("Test_0003_Line_0000__path_1",baseKB:path(1,2))
passed=info(why_was_true(baseKB:path(1,2)))
Justifications for path(1,2):
[36m 1.1 mfl4(_,baseKB,'* https://logicmoo.org:2082/gitlab/logicmoo/logicmoo_workspace/-/blob/master/packs_sys/pfc/t/sanity_base/neg_01v.pfc#L15 ',15) [0m
name ='logicmoo.pfc.test.sanity_base.NEG_01V-Test_0003_Line_0000__path_1'.
JUNIT_CLASSNAME ='logicmoo.pfc.test.sanity_base.NEG_01V'.
JUNIT_CMD ='timeout --foreground --preserve-status -s SIGKILL -k 10s 10s lmoo-clif neg_01v.pfc'.
% saving_junit: /var/lib/jenkins/workspace/logicmoo_workspace/test_results/jenkins/Report-logicmoo-junit-test-sanity_base-vSTARv0vSTARvvDOTvvSTARv-Units-logicmoo.pfc.test.sanity_base.NEG_01V-Test_0003_Line_0000__path_1-junit.xml
~*/
:- mpred_test(~path(1,1)).
%~ mpred_test("Test_0004_Line_0000__path_1",baseKB: ~path(1,1))
/*~
%~ mpred_test("Test_0004_Line_0000__path_1",baseKB: ~path(1,1))
^ Call: (68) [baseKB] ~path(1, 1)
^ Unify: (68) [baseKB] ~ (baseKB:path(1, 1))
^ Call: (75) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_in_code0(baseKB:path(1, 1)), info(pfc_lib:neg_in_code0(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, 1320, pfc_lib:trace_or_throw(looped(pfc_lib:neg_in_code0(baseKB:path(1, 1)))))
^ Unify: (75) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_in_code0(baseKB:path(1, 1)), info(pfc_lib:neg_in_code0(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, 1320, pfc_lib:trace_or_throw(looped(pfc_lib:neg_in_code0(baseKB:path(1, 1)))))
Call: (76) [system] set_prolog_flag(last_call_optimisation, false)
Exit: (76) [system] set_prolog_flag(last_call_optimisation, false)
^ Call: (76) [loop_check] prolog_frame_attribute(1320, parent_goal, loop_check_term_frame(_51782, info(pfc_lib:neg_in_code0(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, _51788, _51790))
^ Fail: (76) [loop_check] prolog_frame_attribute(1320, parent_goal, loop_check_term_frame(_51782, info(pfc_lib:neg_in_code0(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, _51788, _51790))
^ Redo: (75) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_in_code0(baseKB:path(1, 1)), info(pfc_lib:neg_in_code0(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, 1320, pfc_lib:trace_or_throw(looped(pfc_lib:neg_in_code0(baseKB:path(1, 1)))))
Call: (76) [pfc_lib] neg_in_code0(baseKB:path(1, 1))
Unify: (76) [pfc_lib] neg_in_code0(baseKB:path(1, 1))
^ Call: (82) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_may_naf(baseKB:path(1, 1)), info(pfc_lib:neg_may_naf(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, 1459, pfc_lib:trace_or_throw(looped(pfc_lib:neg_may_naf(baseKB:path(1, 1)))))
^ Unify: (82) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_may_naf(baseKB:path(1, 1)), info(pfc_lib:neg_may_naf(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, 1459, pfc_lib:trace_or_throw(looped(pfc_lib:neg_may_naf(baseKB:path(1, 1)))))
Call: (83) [system] set_prolog_flag(last_call_optimisation, false)
Exit: (83) [system] set_prolog_flag(last_call_optimisation, false)
^ Call: (83) [loop_check] prolog_frame_attribute(1459, parent_goal, loop_check_term_frame(_57506, info(pfc_lib:neg_may_naf(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, _57512, _57514))
^ Fail: (83) [loop_check] prolog_frame_attribute(1459, parent_goal, loop_check_term_frame(_57506, info(pfc_lib:neg_may_naf(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, _57512, _57514))
^ Redo: (82) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_may_naf(baseKB:path(1, 1)), info(pfc_lib:neg_may_naf(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, 1459, pfc_lib:trace_or_throw(looped(pfc_lib:neg_may_naf(baseKB:path(1, 1)))))
Call: (83) [pfc_lib] neg_may_naf(baseKB:path(1, 1))
Unify: (83) [pfc_lib] neg_may_naf(baseKB:path(1, 1))
^ Call: (87) [pfc_lib] hook_database:clause_i(pfc_lib:prologNegByFailure(path), true, _60838)
^ Unify: (87) [pfc_lib] hook_database:clause_i(pfc_lib:prologNegByFailure(path), true, _60838)
^ Call: (88) [system] clause(pfc_lib:prologNegByFailure(path), true, _60838)
^ Fail: (88) [system] clause(pfc_lib:prologNegByFailure(path), true, _60838)
^ Fail: (87) [pfc_lib] hook_database:clause_i(pfc_lib:prologNegByFailure(path), true, _60838)
Unify: (83) [pfc_lib] neg_may_naf(baseKB:path(1, 1))
^ Call: (84) [pfc_lib] ucatch:is_ftCompound(baseKB:path(1, 1))
^ Unify: (84) [pfc_lib] ucatch:is_ftCompound(baseKB:path(1, 1))
^ Call: (85) [pfc_lib] ucatch:is_ftVar(baseKB:path(1, 1))
^ Unify: (85) [pfc_lib] ucatch:is_ftVar(baseKB:path(1, 1))
^ Fail: (85) [pfc_lib] ucatch:is_ftVar(baseKB:path(1, 1))
^ Redo: (84) [pfc_lib] ucatch:is_ftCompound(baseKB:path(1, 1))
^ Exit: (84) [pfc_lib] ucatch:is_ftCompound(baseKB:path(1, 1))
^ Call: (88) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologHybrid), _69008), call(_69008)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))))
^ Unify: (88) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologHybrid), _69008), call(_69008)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))))
^ Call: (90) [hook_database] clause(mpred_prop(baseKB, path, 2, prologHybrid), _69008)
^ Fail: (90) [hook_database] clause(mpred_prop(baseKB, path, 2, prologHybrid), _69008)
Call: (90) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))
Unify: (90) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))
^ Call: (91) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologHybrid), _72794))
^ Unify: (91) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologHybrid), _72794))
^ Call: (92) [baseKB] clause(mpred_prop(baseKB, path, 2, prologHybrid), _72794)
^ Fail: (92) [baseKB] clause(mpred_prop(baseKB, path, 2, prologHybrid), _72794)
^ Fail: (91) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologHybrid), _72794))
Fail: (90) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))
^ Fail: (88) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologHybrid), _69008), call(_69008)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))))
^ Call: (87) [pfc_lib] baseKB:mpred_database_term(path, 2, _77214)
^ Unify: (87) [pfc_lib] baseKB:mpred_database_term(path, 2, syntaxic(_77784))
^ Call: (88) [pfc_lib] mpred_database_term_syntax(path, 2, _77784)
^ Fail: (88) [pfc_lib] mpred_database_term_syntax(path, 2, _77784)
^ Redo: (87) [pfc_lib] baseKB:mpred_database_term(path, 2, _79786)
^ Unify: (87) [pfc_lib] baseKB:mpred_database_term(path, 2, _80414)
^ Call: (88) [pfc_lib] mpred_core_database_term(path, 2, _80982)
^ Fail: (88) [pfc_lib] mpred_core_database_term(path, 2, _80982)
^ Fail: (87) [pfc_lib] baseKB:mpred_database_term(path, 2, _82356)
^ Call: (86) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologBuiltin), _82960), call(_82960)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))))
^ Unify: (86) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologBuiltin), _82960), call(_82960)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))))
^ Call: (88) [hook_database] clause(mpred_prop(baseKB, path, 2, prologBuiltin), _82960)
^ Fail: (88) [hook_database] clause(mpred_prop(baseKB, path, 2, prologBuiltin), _82960)
Call: (88) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))
Unify: (88) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))
^ Call: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologBuiltin), _86746))
^ Unify: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologBuiltin), _86746))
^ Call: (90) [baseKB] clause(mpred_prop(baseKB, path, 2, prologBuiltin), _86746)
^ Fail: (90) [baseKB] clause(mpred_prop(baseKB, path, 2, prologBuiltin), _86746)
^ Fail: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologBuiltin), _86746))
Fail: (88) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))
^ Fail: (86) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologBuiltin), _82960), call(_82960)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))))
^ Call: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(_91112, path, 2, prologHybrid), _91142), call(_91142)*->true;clause_b(baseKB:mpred_prop(_91112, path, 2, prologHybrid))))
^ Unify: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(_91112, path, 2, prologHybrid), _91142), call(_91142)*->true;clause_b(baseKB:mpred_prop(_91112, path, 2, prologHybrid))))
^ Call: (91) [hook_database] clause(mpred_prop(_91112, path, 2, prologHybrid), _91142)
^ Fail: (91) [hook_database] clause(mpred_prop(_91112, path, 2, prologHybrid), _91142)
Call: (91) [hook_database] clause_b(baseKB:mpred_prop(_91112, path, 2, prologHybrid))
Unify: (91) [hook_database] clause_b(baseKB:mpred_prop(_91112, path, 2, prologHybrid))
^ Call: (92) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(_91112, path, 2, prologHybrid), _94928))
^ Unify: (92) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(_91112, path, 2, prologHybrid), _94928))
^ Call: (93) [baseKB] clause(mpred_prop(_91112, path, 2, prologHybrid), _94928)
^ Fail: (93) [baseKB] clause(mpred_prop(_91112, path, 2, prologHybrid), _94928)
^ Fail: (92) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(_91112, path, 2, prologHybrid), _94928))
Fail: (91) [hook_database] clause_b(baseKB:mpred_prop(_91112, path, 2, prologHybrid))
^ Fail: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(_91112, path, 2, prologHybrid), _91142), call(_91142)*->true;clause_b(baseKB:mpred_prop(_91112, path, 2, prologHybrid))))
^ Call: (88) [pfc_lib] baseKB:mpred_database_term(path, 2, _99348)
^ Unify: (88) [pfc_lib] baseKB:mpred_database_term(path, 2, syntaxic(_99918))
^ Call: (89) [pfc_lib] mpred_database_term_syntax(path, 2, _99918)
^ Fail: (89) [pfc_lib] mpred_database_term_syntax(path, 2, _99918)
^ Redo: (88) [pfc_lib] baseKB:mpred_database_term(path, 2, _101920)
^ Unify: (88) [pfc_lib] baseKB:mpred_database_term(path, 2, _102548)
^ Call: (89) [pfc_lib] mpred_core_database_term(path, 2, _103116)
^ Fail: (89) [pfc_lib] mpred_core_database_term(path, 2, _103116)
^ Fail: (88) [pfc_lib] baseKB:mpred_database_term(path, 2, _104490)
Call: (98) [$autoload] leave_sandbox(_105088)
Unify: (98) [$autoload] leave_sandbox(_105088)
Exit: (98) [$autoload] leave_sandbox(false)
Call: (97) [$autoload] restore_sandbox(false)
Unify: (97) [$autoload] restore_sandbox(false)
Exit: (97) [$autoload] restore_sandbox(false)
Fail: (83) [pfc_lib] neg_may_naf(baseKB:path(1, 1))
^ Fail: (82) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_may_naf(baseKB:path(1, 1)), info(pfc_lib:neg_may_naf(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, 1459, pfc_lib:trace_or_throw(looped(pfc_lib:neg_may_naf(baseKB:path(1, 1)))))
Fail: (76) [pfc_lib] neg_in_code0(baseKB:path(1, 1))
^ Fail: (75) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_in_code0(baseKB:path(1, 1)), info(pfc_lib:neg_in_code0(baseKB:path(1, 1)), 'mpred_core.pl':273), 1, 1320, pfc_lib:trace_or_throw(looped(pfc_lib:neg_in_code0(baseKB:path(1, 1)))))
^ Fail: (68) [baseKB] ~ (baseKB:path(1, 1))
^ Call: (68) [must_sanity] must_sanity:mquietly_if(true, rtrace:tAt_normal)
^ Unify: (68) [must_sanity] must_sanity:mquietly_if(true, rtrace:tAt_normal)
failure=info((why_was_true(baseKB:(\+ ~path(1,1))),rtrace(baseKB: ~path(1,1))))
no_proof_for(\+ ~path(1,1)).
no_proof_for(\+ ~path(1,1)).
no_proof_for(\+ ~path(1,1)).
name ='logicmoo.pfc.test.sanity_base.NEG_01V-Test_0004_Line_0000__path_1'.
JUNIT_CLASSNAME ='logicmoo.pfc.test.sanity_base.NEG_01V'.
JUNIT_CMD ='timeout --foreground --preserve-status -s SIGKILL -k 10s 10s lmoo-clif neg_01v.pfc'.
% saving_junit: /var/lib/jenkins/workspace/logicmoo_workspace/test_results/jenkins/Report-logicmoo-junit-test-sanity_base-vSTARv0vSTARvvDOTvvSTARv-Units-logicmoo.pfc.test.sanity_base.NEG_01V-Test_0004_Line_0000__path_1-junit.xml
~*/
:- mpred_test(~path(2,2)).
%~ /var/lib/jenkins/workspace/logicmoo_workspace/packs_sys/pfc/t/sanity_base/neg_01v.pfc:24
%~ mpred_test("Test_0005_Line_0000__path_2",baseKB: ~path(2,2))
/*~
%~ mpred_test("Test_0005_Line_0000__path_2",baseKB: ~path(2,2))
^ Call: (68) [baseKB] ~path(2, 2)
^ Unify: (68) [baseKB] ~ (baseKB:path(2, 2))
^ Call: (75) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_in_code0(baseKB:path(2, 2)), info(pfc_lib:neg_in_code0(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, 1189, pfc_lib:trace_or_throw(looped(pfc_lib:neg_in_code0(baseKB:path(2, 2)))))
^ Unify: (75) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_in_code0(baseKB:path(2, 2)), info(pfc_lib:neg_in_code0(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, 1189, pfc_lib:trace_or_throw(looped(pfc_lib:neg_in_code0(baseKB:path(2, 2)))))
Call: (76) [system] set_prolog_flag(last_call_optimisation, false)
Exit: (76) [system] set_prolog_flag(last_call_optimisation, false)
^ Call: (76) [loop_check] prolog_frame_attribute(1189, parent_goal, loop_check_term_frame(_93356, info(pfc_lib:neg_in_code0(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, _93362, _93364))
^ Fail: (76) [loop_check] prolog_frame_attribute(1189, parent_goal, loop_check_term_frame(_93356, info(pfc_lib:neg_in_code0(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, _93362, _93364))
^ Redo: (75) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_in_code0(baseKB:path(2, 2)), info(pfc_lib:neg_in_code0(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, 1189, pfc_lib:trace_or_throw(looped(pfc_lib:neg_in_code0(baseKB:path(2, 2)))))
Call: (76) [pfc_lib] neg_in_code0(baseKB:path(2, 2))
Unify: (76) [pfc_lib] neg_in_code0(baseKB:path(2, 2))
^ Call: (82) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_may_naf(baseKB:path(2, 2)), info(pfc_lib:neg_may_naf(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, 1328, pfc_lib:trace_or_throw(looped(pfc_lib:neg_may_naf(baseKB:path(2, 2)))))
^ Unify: (82) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_may_naf(baseKB:path(2, 2)), info(pfc_lib:neg_may_naf(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, 1328, pfc_lib:trace_or_throw(looped(pfc_lib:neg_may_naf(baseKB:path(2, 2)))))
Call: (83) [system] set_prolog_flag(last_call_optimisation, false)
Exit: (83) [system] set_prolog_flag(last_call_optimisation, false)
^ Call: (83) [loop_check] prolog_frame_attribute(1328, parent_goal, loop_check_term_frame(_99080, info(pfc_lib:neg_may_naf(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, _99086, _99088))
^ Fail: (83) [loop_check] prolog_frame_attribute(1328, parent_goal, loop_check_term_frame(_99080, info(pfc_lib:neg_may_naf(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, _99086, _99088))
^ Redo: (82) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_may_naf(baseKB:path(2, 2)), info(pfc_lib:neg_may_naf(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, 1328, pfc_lib:trace_or_throw(looped(pfc_lib:neg_may_naf(baseKB:path(2, 2)))))
Call: (83) [pfc_lib] neg_may_naf(baseKB:path(2, 2))
Unify: (83) [pfc_lib] neg_may_naf(baseKB:path(2, 2))
^ Call: (87) [pfc_lib] hook_database:clause_i(pfc_lib:prologNegByFailure(path), true, _102412)
^ Unify: (87) [pfc_lib] hook_database:clause_i(pfc_lib:prologNegByFailure(path), true, _102412)
^ Call: (88) [system] clause(pfc_lib:prologNegByFailure(path), true, _102412)
^ Fail: (88) [system] clause(pfc_lib:prologNegByFailure(path), true, _102412)
^ Fail: (87) [pfc_lib] hook_database:clause_i(pfc_lib:prologNegByFailure(path), true, _102412)
Unify: (83) [pfc_lib] neg_may_naf(baseKB:path(2, 2))
^ Call: (84) [pfc_lib] ucatch:is_ftCompound(baseKB:path(2, 2))
^ Unify: (84) [pfc_lib] ucatch:is_ftCompound(baseKB:path(2, 2))
^ Call: (85) [pfc_lib] ucatch:is_ftVar(baseKB:path(2, 2))
^ Unify: (85) [pfc_lib] ucatch:is_ftVar(baseKB:path(2, 2))
^ Fail: (85) [pfc_lib] ucatch:is_ftVar(baseKB:path(2, 2))
^ Redo: (84) [pfc_lib] ucatch:is_ftCompound(baseKB:path(2, 2))
^ Exit: (84) [pfc_lib] ucatch:is_ftCompound(baseKB:path(2, 2))
^ Call: (88) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologHybrid), _110582), call(_110582)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))))
^ Unify: (88) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologHybrid), _110582), call(_110582)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))))
^ Call: (90) [hook_database] clause(mpred_prop(baseKB, path, 2, prologHybrid), _110582)
^ Fail: (90) [hook_database] clause(mpred_prop(baseKB, path, 2, prologHybrid), _110582)
Call: (90) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))
Unify: (90) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))
^ Call: (91) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologHybrid), _114368))
^ Unify: (91) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologHybrid), _114368))
^ Call: (92) [baseKB] clause(mpred_prop(baseKB, path, 2, prologHybrid), _114368)
^ Fail: (92) [baseKB] clause(mpred_prop(baseKB, path, 2, prologHybrid), _114368)
^ Fail: (91) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologHybrid), _114368))
Fail: (90) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))
^ Fail: (88) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologHybrid), _110582), call(_110582)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologHybrid))))
^ Call: (87) [pfc_lib] baseKB:mpred_database_term(path, 2, _118788)
^ Unify: (87) [pfc_lib] baseKB:mpred_database_term(path, 2, syntaxic(_119358))
^ Call: (88) [pfc_lib] mpred_database_term_syntax(path, 2, _119358)
^ Fail: (88) [pfc_lib] mpred_database_term_syntax(path, 2, _119358)
^ Redo: (87) [pfc_lib] baseKB:mpred_database_term(path, 2, _121360)
^ Unify: (87) [pfc_lib] baseKB:mpred_database_term(path, 2, _121988)
^ Call: (88) [pfc_lib] mpred_core_database_term(path, 2, _122556)
^ Fail: (88) [pfc_lib] mpred_core_database_term(path, 2, _122556)
^ Fail: (87) [pfc_lib] baseKB:mpred_database_term(path, 2, _123930)
^ Call: (86) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologBuiltin), _124534), call(_124534)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))))
^ Unify: (86) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologBuiltin), _124534), call(_124534)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))))
^ Call: (88) [hook_database] clause(mpred_prop(baseKB, path, 2, prologBuiltin), _124534)
^ Fail: (88) [hook_database] clause(mpred_prop(baseKB, path, 2, prologBuiltin), _124534)
Call: (88) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))
Unify: (88) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))
^ Call: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologBuiltin), _128320))
^ Unify: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologBuiltin), _128320))
^ Call: (90) [baseKB] clause(mpred_prop(baseKB, path, 2, prologBuiltin), _128320)
^ Fail: (90) [baseKB] clause(mpred_prop(baseKB, path, 2, prologBuiltin), _128320)
^ Fail: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(baseKB, path, 2, prologBuiltin), _128320))
Fail: (88) [hook_database] clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))
^ Fail: (86) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(baseKB, path, 2, prologBuiltin), _124534), call(_124534)*->true;clause_b(baseKB:mpred_prop(baseKB, path, 2, prologBuiltin))))
^ Call: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(_132686, path, 2, prologHybrid), _132716), call(_132716)*->true;clause_b(baseKB:mpred_prop(_132686, path, 2, prologHybrid))))
^ Unify: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(_132686, path, 2, prologHybrid), _132716), call(_132716)*->true;clause_b(baseKB:mpred_prop(_132686, path, 2, prologHybrid))))
^ Call: (91) [hook_database] clause(mpred_prop(_132686, path, 2, prologHybrid), _132716)
^ Fail: (91) [hook_database] clause(mpred_prop(_132686, path, 2, prologHybrid), _132716)
Call: (91) [hook_database] clause_b(baseKB:mpred_prop(_132686, path, 2, prologHybrid))
Unify: (91) [hook_database] clause_b(baseKB:mpred_prop(_132686, path, 2, prologHybrid))
^ Call: (92) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(_132686, path, 2, prologHybrid), _136502))
^ Unify: (92) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(_132686, path, 2, prologHybrid), _136502))
^ Call: (93) [baseKB] clause(mpred_prop(_132686, path, 2, prologHybrid), _136502)
^ Fail: (93) [baseKB] clause(mpred_prop(_132686, path, 2, prologHybrid), _136502)
^ Fail: (92) [hook_database] hook_database:pfc_with_quiet_vars_lock(baseKB:clause(mpred_prop(_132686, path, 2, prologHybrid), _136502))
Fail: (91) [hook_database] clause_b(baseKB:mpred_prop(_132686, path, 2, prologHybrid))
^ Fail: (89) [hook_database] hook_database:pfc_with_quiet_vars_lock((clause(mpred_prop(_132686, path, 2, prologHybrid), _132716), call(_132716)*->true;clause_b(baseKB:mpred_prop(_132686, path, 2, prologHybrid))))
^ Call: (88) [pfc_lib] baseKB:mpred_database_term(path, 2, _140922)
^ Unify: (88) [pfc_lib] baseKB:mpred_database_term(path, 2, syntaxic(_141492))
^ Call: (89) [pfc_lib] mpred_database_term_syntax(path, 2, _141492)
^ Fail: (89) [pfc_lib] mpred_database_term_syntax(path, 2, _141492)
^ Redo: (88) [pfc_lib] baseKB:mpred_database_term(path, 2, _143494)
^ Unify: (88) [pfc_lib] baseKB:mpred_database_term(path, 2, _144122)
^ Call: (89) [pfc_lib] mpred_core_database_term(path, 2, _144690)
^ Fail: (89) [pfc_lib] mpred_core_database_term(path, 2, _144690)
^ Fail: (88) [pfc_lib] baseKB:mpred_database_term(path, 2, _146064)
Call: (98) [$autoload] leave_sandbox(_146662)
Unify: (98) [$autoload] leave_sandbox(_146662)
Exit: (98) [$autoload] leave_sandbox(false)
Call: (97) [$autoload] restore_sandbox(false)
Unify: (97) [$autoload] restore_sandbox(false)
Exit: (97) [$autoload] restore_sandbox(false)
Fail: (83) [pfc_lib] neg_may_naf(baseKB:path(2, 2))
^ Fail: (82) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_may_naf(baseKB:path(2, 2)), info(pfc_lib:neg_may_naf(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, 1328, pfc_lib:trace_or_throw(looped(pfc_lib:neg_may_naf(baseKB:path(2, 2)))))
Fail: (76) [pfc_lib] neg_in_code0(baseKB:path(2, 2))
^ Fail: (75) [loop_check] loop_check:loop_check_term_frame(pfc_lib:neg_in_code0(baseKB:path(2, 2)), info(pfc_lib:neg_in_code0(baseKB:path(2, 2)), 'mpred_core.pl':273), 1, 1189, pfc_lib:trace_or_throw(looped(pfc_lib:neg_in_code0(baseKB:path(2, 2)))))
^ Fail: (68) [baseKB] ~ (baseKB:path(2, 2))
^ Call: (68) [must_sanity] must_sanity:mquietly_if(true, rtrace:tAt_normal)
^ Unify: (68) [must_sanity] must_sanity:mquietly_if(true, rtrace:tAt_normal)
failure=info((why_was_true(baseKB:(\+ ~path(2,2))),rtrace(baseKB: ~path(2,2))))
no_proof_for(\+ ~path(2,2)).
no_proof_for(\+ ~path(2,2)).
no_proof_for(\+ ~path(2,2)).
name ='logicmoo.pfc.test.sanity_base.NEG_01V-Test_0005_Line_0000__path_2'.
JUNIT_CLASSNAME ='logicmoo.pfc.test.sanity_base.NEG_01V'.
JUNIT_CMD ='timeout --foreground --preserve-status -s SIGKILL -k 10s 10s lmoo-clif neg_01v.pfc'.
% saving_junit: /var/lib/jenkins/workspace/logicmoo_workspace/test_results/jenkins/Report-logicmoo-junit-test-sanity_base-vSTARv0vSTARvvDOTvvSTARv-Units-logicmoo.pfc.test.sanity_base.NEG_01V-Test_0005_Line_0000__path_2-junit.xml
~*/
/*
:- mpred_test(\+path(1,1)).
:- mpred_test(\+path(2,2)).
*/
:- mpred_test(\+path(3,1)).
%~ /var/lib/jenkins/workspace/logicmoo_workspace/packs_sys/pfc/t/sanity_base/neg_01v.pfc:32
%~ mpred_test("Test_0006_Line_0000__naf_path_3",baseKB:(\+path(3,1)))
/*~
%~ mpred_test("Test_0006_Line_0000__naf_path_3",baseKB:(\+path(3,1)))
passed=info(why_was_true(baseKB:(\+path(3,1))))
no_proof_for(\+path(3,1)).
no_proof_for(\+path(3,1)).
no_proof_for(\+path(3,1)).
name ='logicmoo.pfc.test.sanity_base.NEG_01V-Test_0006_Line_0000__naf_path_3'.
JUNIT_CLASSNAME ='logicmoo.pfc.test.sanity_base.NEG_01V'.
JUNIT_CMD ='timeout --foreground --preserve-status -s SIGKILL -k 10s 10s lmoo-clif neg_01v.pfc'.
% saving_junit: /var/lib/jenkins/workspace/logicmoo_workspace/test_results/jenkins/Report-logicmoo-junit-test-sanity_base-vSTARv0vSTARvvDOTvvSTARv-Units-logicmoo.pfc.test.sanity_base.NEG_01V-Test_0006_Line_0000__naf_path_3-junit.xml
~*/
:- mpred_test(\+ ~path(1,5)).
%~ mpred_test("Test_0007_Line_0000__naf_path_1",baseKB:(\+ ~path(1,5)))
/*~
%~ mpred_test("Test_0007_Line_0000__naf_path_1",baseKB:(\+ ~path(1,5)))
passed=info(why_was_true(baseKB:(\+ ~path(1,5))))
no_proof_for(\+ ~path(1,5)).
no_proof_for(\+ ~path(1,5)).
no_proof_for(\+ ~path(1,5)).
name ='logicmoo.pfc.test.sanity_base.NEG_01V-Test_0007_Line_0000__naf_path_1'.
JUNIT_CLASSNAME ='logicmoo.pfc.test.sanity_base.NEG_01V'.
JUNIT_CMD ='timeout --foreground --preserve-status -s SIGKILL -k 10s 10s lmoo-clif neg_01v.pfc'.
% saving_junit: /var/lib/jenkins/workspace/logicmoo_workspace/test_results/jenkins/Report-logicmoo-junit-test-sanity_base-vSTARv0vSTARvvDOTvvSTARv-Units-logicmoo.pfc.test.sanity_base.NEG_01V-Test_0007_Line_0000__naf_path_1-junit.xml
~*/
:- break.
%~ skipped(blocks_on_input,break)
%~ unused(save_junit_results)
%~ test_completed_exit(6)
:- dynamic junit_prop/3.
:- dynamic junit_prop/3.
:- dynamic junit_prop/3.
```
totalTime=1
ISSUE_SEARCH: https://github.com/logicmoo/logicmoo_workspace/issues?q=is%3Aissue+label%3ANEG_01V
GITLAB: https://logicmoo.org:2082/gitlab/logicmoo/logicmoo_workspace/-/commit/869479bc8cf913ee2df5ebbe49363a2dad9c9fb3
https://gitlab.logicmoo.org/gitlab/logicmoo/logicmoo_workspace/-/blob/869479bc8cf913ee2df5ebbe49363a2dad9c9fb3/packs_sys/pfc/t/sanity_base/neg_01v.pfc
Latest: https://jenkins.logicmoo.org/job/logicmoo_workspace/lastBuild/testReport/logicmoo.pfc.test.sanity_base/NEG_01V/logicmoo_pfc_test_sanity_base_NEG_01V_JUnit/
This Build: https://jenkins.logicmoo.org/job/logicmoo_workspace/67/testReport/logicmoo.pfc.test.sanity_base/NEG_01V/logicmoo_pfc_test_sanity_base_NEG_01V_JUnit/
GITHUB: https://github.com/logicmoo/logicmoo_workspace/commit/869479bc8cf913ee2df5ebbe49363a2dad9c9fb3
https://github.com/logicmoo/logicmoo_workspace/blob/869479bc8cf913ee2df5ebbe49363a2dad9c9fb3/packs_sys/pfc/t/sanity_base/neg_01v.pfc
FAILED: /var/lib/jenkins/workspace/logicmoo_workspace/bin/lmoo-junit-minor -k neg_01v.pfc (returned 6)
| non_priority | logicmoo pfc test sanity base neg junit cd var lib jenkins workspace logicmoo workspace packs sys pfc t sanity base timeout foreground preserve status s sigkill k lmoo clif neg pfc gh master issue finfo issue search gitlab latest this build github running var lib jenkins workspace logicmoo workspace packs sys pfc t sanity base neg pfc this test might need use module library logicmoo plarkc use module library statistics mpred notrace exec reset runtime counter mpred notrace exec reset runtime counter statistics runtime secs path x x path path path path mpred test path mpred test test line path basekb path file mpred test test line path basekb path passed info why was true basekb path justifications for path basekb name logicmoo pfc test sanity base neg test line path junit classname logicmoo pfc test sanity base neg junit cmd timeout foreground preserve status s sigkill k lmoo clif neg pfc saving junit var lib jenkins workspace logicmoo workspace test results jenkins report logicmoo junit test sanity base units logicmoo pfc test sanity base neg test line path junit xml mpred test path mpred test test line path basekb path file mpred test test line path basekb path passed info why was true basekb path justifications for path basekb name logicmoo pfc test sanity base neg test line path junit classname logicmoo pfc test sanity base neg junit cmd timeout foreground preserve status s sigkill k lmoo clif neg pfc saving junit var lib jenkins workspace logicmoo workspace test results jenkins report logicmoo junit test sanity base units logicmoo pfc test sanity base neg test line path junit xml mpred test path mpred test test line path basekb path file mpred test test line path basekb path passed info why was true basekb path justifications for path basekb name logicmoo pfc test sanity base neg test line path junit classname logicmoo pfc test sanity base neg junit cmd timeout foreground preserve status s sigkill k lmoo clif neg pfc saving junit var lib jenkins workspace logicmoo workspace test results jenkins report logicmoo junit test sanity base units logicmoo pfc test sanity base neg test line path junit xml mpred test path mpred test test line path basekb path mpred test test line path basekb path call path unify basekb path call loop check loop check term frame pfc lib neg in basekb path info pfc lib neg in basekb path mpred core pl pfc lib trace or throw looped pfc lib neg in basekb path unify loop check loop check term frame pfc lib neg in basekb path info pfc lib neg in basekb path mpred core pl pfc lib trace or throw looped pfc lib neg in basekb path call set prolog flag last call optimisation false exit set prolog flag last call optimisation false call prolog frame attribute parent goal loop check term frame info pfc lib neg in basekb path mpred core pl fail prolog frame attribute parent goal loop check term frame info pfc lib neg in basekb path mpred core pl redo loop check loop check term frame pfc lib neg in basekb path info pfc lib neg in basekb path mpred core pl pfc lib trace or throw looped pfc lib neg in basekb path call neg in basekb path unify neg in basekb path call loop check loop check term frame pfc lib neg may naf basekb path info pfc lib neg may naf basekb path mpred core pl pfc lib trace or throw looped pfc lib neg may naf basekb path unify loop check loop check term frame pfc lib neg may naf basekb path info pfc lib neg may naf basekb path mpred core pl pfc lib trace or throw looped pfc lib neg may naf basekb path call set prolog flag last call optimisation false exit set prolog flag last call optimisation false call prolog frame attribute parent goal loop check term frame info pfc lib neg may naf basekb path mpred core pl fail prolog frame attribute parent goal loop check term frame info pfc lib neg may naf basekb path mpred core pl redo loop check loop check term frame pfc lib neg may naf basekb path info pfc lib neg may naf basekb path mpred core pl pfc lib trace or throw looped pfc lib neg may naf basekb path call neg may naf basekb path unify neg may naf basekb path call hook database clause i pfc lib prolognegbyfailure path true unify hook database clause i pfc lib prolognegbyfailure path true call clause pfc lib prolognegbyfailure path true fail clause pfc lib prolognegbyfailure path true fail hook database clause i pfc lib prolognegbyfailure path true unify neg may naf basekb path call ucatch is ftcompound basekb path unify ucatch is ftcompound basekb path call ucatch is ftvar basekb path unify ucatch is ftvar basekb path fail ucatch is ftvar basekb path redo ucatch is ftcompound basekb path exit ucatch is ftcompound basekb path call hook database pfc with quiet vars lock clause mpred prop basekb path prologhybrid call true clause b basekb mpred prop basekb path prologhybrid unify hook database pfc with quiet vars lock clause mpred prop basekb path prologhybrid call true clause b basekb mpred prop basekb path prologhybrid call clause mpred prop basekb path prologhybrid fail clause mpred prop basekb path prologhybrid call clause b basekb mpred prop basekb path prologhybrid unify clause b basekb mpred prop basekb path prologhybrid call hook database pfc with quiet vars lock basekb clause mpred prop basekb path prologhybrid unify hook database pfc with quiet vars lock basekb clause mpred prop basekb path prologhybrid call clause mpred prop basekb path prologhybrid fail clause mpred prop basekb path prologhybrid fail hook database pfc with quiet vars lock basekb clause mpred prop basekb path prologhybrid fail clause b basekb mpred prop basekb path prologhybrid fail hook database pfc with quiet vars lock clause mpred prop basekb path prologhybrid call true clause b basekb mpred prop basekb path prologhybrid call basekb mpred database term path unify basekb mpred database term path syntaxic call mpred database term syntax path fail mpred database term syntax path redo basekb mpred database term path unify basekb mpred database term path call mpred core database term path fail mpred core database term path fail basekb mpred database term path call hook database pfc with quiet vars lock clause mpred prop basekb path prologbuiltin call true clause b basekb mpred prop basekb path prologbuiltin unify hook database pfc with quiet vars lock clause mpred prop basekb path prologbuiltin call true clause b basekb mpred prop basekb path prologbuiltin call clause mpred prop basekb path prologbuiltin fail clause mpred prop basekb path prologbuiltin call clause b basekb mpred prop basekb path prologbuiltin unify clause b basekb mpred prop basekb path prologbuiltin call hook database pfc with quiet vars lock basekb clause mpred prop basekb path prologbuiltin unify hook database pfc with quiet vars lock basekb clause mpred prop basekb path prologbuiltin call clause mpred prop basekb path prologbuiltin fail clause mpred prop basekb path prologbuiltin fail hook database pfc with quiet vars lock basekb clause mpred prop basekb path prologbuiltin fail clause b basekb mpred prop basekb path prologbuiltin fail hook database pfc with quiet vars lock clause mpred prop basekb path prologbuiltin call true clause b basekb mpred prop basekb path prologbuiltin call hook database pfc with quiet vars lock clause mpred prop path prologhybrid call true clause b basekb mpred prop path prologhybrid unify hook database pfc with quiet vars lock clause mpred prop path prologhybrid call true clause b basekb mpred prop path prologhybrid call clause mpred prop path prologhybrid fail clause mpred prop path prologhybrid call clause b basekb mpred prop path prologhybrid unify clause b basekb mpred prop path prologhybrid call hook database pfc with quiet vars lock basekb clause mpred prop path prologhybrid unify hook database pfc with quiet vars lock basekb clause mpred prop path prologhybrid call clause mpred prop path prologhybrid fail clause mpred prop path prologhybrid fail hook database pfc with quiet vars lock basekb clause mpred prop path prologhybrid fail clause b basekb mpred prop path prologhybrid fail hook database pfc with quiet vars lock clause mpred prop path prologhybrid call true clause b basekb mpred prop path prologhybrid call basekb mpred database term path unify basekb mpred database term path syntaxic call mpred database term syntax path fail mpred database term syntax path redo basekb mpred database term path unify basekb mpred database term path call mpred core database term path fail mpred core database term path fail basekb mpred database term path call leave sandbox unify leave sandbox exit leave sandbox false call restore sandbox false unify restore sandbox false exit restore sandbox false fail neg may naf basekb path fail loop check loop check term frame pfc lib neg may naf basekb path info pfc lib neg may naf basekb path mpred core pl pfc lib trace or throw looped pfc lib neg may naf basekb path fail neg in basekb path fail loop check loop check term frame pfc lib neg in basekb path info pfc lib neg in basekb path mpred core pl pfc lib trace or throw looped pfc lib neg in basekb path fail basekb path call must sanity mquietly if true rtrace tat normal unify must sanity mquietly if true rtrace tat normal failure info why was true basekb path rtrace basekb path no proof for path no proof for path no proof for path name logicmoo pfc test sanity base neg test line path junit classname logicmoo pfc test sanity base neg junit cmd timeout foreground preserve status s sigkill k lmoo clif neg pfc saving junit var lib jenkins workspace logicmoo workspace test results jenkins report logicmoo junit test sanity base units logicmoo pfc test sanity base neg test line path junit xml mpred test path var lib jenkins workspace logicmoo workspace packs sys pfc t sanity base neg pfc mpred test test line path basekb path mpred test test line path basekb path call path unify basekb path call loop check loop check term frame pfc lib neg in basekb path info pfc lib neg in basekb path mpred core pl pfc lib trace or throw looped pfc lib neg in basekb path unify loop check loop check term frame pfc lib neg in basekb path info pfc lib neg in basekb path mpred core pl pfc lib trace or throw looped pfc lib neg in basekb path call set prolog flag last call optimisation false exit set prolog flag last call optimisation false call prolog frame attribute parent goal loop check term frame info pfc lib neg in basekb path mpred core pl fail prolog frame attribute parent goal loop check term frame info pfc lib neg in basekb path mpred core pl redo loop check loop check term frame pfc lib neg in basekb path info pfc lib neg in basekb path mpred core pl pfc lib trace or throw looped pfc lib neg in basekb path call neg in basekb path unify neg in basekb path call loop check loop check term frame pfc lib neg may naf basekb path info pfc lib neg may naf basekb path mpred core pl pfc lib trace or throw looped pfc lib neg may naf basekb path unify loop check loop check term frame pfc lib neg may naf basekb path info pfc lib neg may naf basekb path mpred core pl pfc lib trace or throw looped pfc lib neg may naf basekb path call set prolog flag last call optimisation false exit set prolog flag last call optimisation false call prolog frame attribute parent goal loop check term frame info pfc lib neg may naf basekb path mpred core pl fail prolog frame attribute parent goal loop check term frame info pfc lib neg may naf basekb path mpred core pl redo loop check loop check term frame pfc lib neg may naf basekb path info pfc lib neg may naf basekb path mpred core pl pfc lib trace or throw looped pfc lib neg may naf basekb path call neg may naf basekb path unify neg may naf basekb path call hook database clause i pfc lib prolognegbyfailure path true unify hook database clause i pfc lib prolognegbyfailure path true call clause pfc lib prolognegbyfailure path true fail clause pfc lib prolognegbyfailure path true fail hook database clause i pfc lib prolognegbyfailure path true unify neg may naf basekb path call ucatch is ftcompound basekb path unify ucatch is ftcompound basekb path call ucatch is ftvar basekb path unify ucatch is ftvar basekb path fail ucatch is ftvar basekb path redo ucatch is ftcompound basekb path exit ucatch is ftcompound basekb path call hook database pfc with quiet vars lock clause mpred prop basekb path prologhybrid call true clause b basekb mpred prop basekb path prologhybrid unify hook database pfc with quiet vars lock clause mpred prop basekb path prologhybrid call true clause b basekb mpred prop basekb path prologhybrid call clause mpred prop basekb path prologhybrid fail clause mpred prop basekb path prologhybrid call clause b basekb mpred prop basekb path prologhybrid unify clause b basekb mpred prop basekb path prologhybrid call hook database pfc with quiet vars lock basekb clause mpred prop basekb path prologhybrid unify hook database pfc with quiet vars lock basekb clause mpred prop basekb path prologhybrid call clause mpred prop basekb path prologhybrid fail clause mpred prop basekb path prologhybrid fail hook database pfc with quiet vars lock basekb clause mpred prop basekb path prologhybrid fail clause b basekb mpred prop basekb path prologhybrid fail hook database pfc with quiet vars lock clause mpred prop basekb path prologhybrid call true clause b basekb mpred prop basekb path prologhybrid call basekb mpred database term path unify basekb mpred database term path syntaxic call mpred database term syntax path fail mpred database term syntax path redo basekb mpred database term path unify basekb mpred database term path call mpred core database term path fail mpred core database term path fail basekb mpred database term path call hook database pfc with quiet vars lock clause mpred prop basekb path prologbuiltin call true clause b basekb mpred prop basekb path prologbuiltin unify hook database pfc with quiet vars lock clause mpred prop basekb path prologbuiltin call true clause b basekb mpred prop basekb path prologbuiltin call clause mpred prop basekb path prologbuiltin fail clause mpred prop basekb path prologbuiltin call clause b basekb mpred prop basekb path prologbuiltin unify clause b basekb mpred prop basekb path prologbuiltin call hook database pfc with quiet vars lock basekb clause mpred prop basekb path prologbuiltin unify hook database pfc with quiet vars lock basekb clause mpred prop basekb path prologbuiltin call clause mpred prop basekb path prologbuiltin fail clause mpred prop basekb path prologbuiltin fail hook database pfc with quiet vars lock basekb clause mpred prop basekb path prologbuiltin fail clause b basekb mpred prop basekb path prologbuiltin fail hook database pfc with quiet vars lock clause mpred prop basekb path prologbuiltin call true clause b basekb mpred prop basekb path prologbuiltin call hook database pfc with quiet vars lock clause mpred prop path prologhybrid call true clause b basekb mpred prop path prologhybrid unify hook database pfc with quiet vars lock clause mpred prop path prologhybrid call true clause b basekb mpred prop path prologhybrid call clause mpred prop path prologhybrid fail clause mpred prop path prologhybrid call clause b basekb mpred prop path prologhybrid unify clause b basekb mpred prop path prologhybrid call hook database pfc with quiet vars lock basekb clause mpred prop path prologhybrid unify hook database pfc with quiet vars lock basekb clause mpred prop path prologhybrid call clause mpred prop path prologhybrid fail clause mpred prop path prologhybrid fail hook database pfc with quiet vars lock basekb clause mpred prop path prologhybrid fail clause b basekb mpred prop path prologhybrid fail hook database pfc with quiet vars lock clause mpred prop path prologhybrid call true clause b basekb mpred prop path prologhybrid call basekb mpred database term path unify basekb mpred database term path syntaxic call mpred database term syntax path fail mpred database term syntax path redo basekb mpred database term path unify basekb mpred database term path call mpred core database term path fail mpred core database term path fail basekb mpred database term path call leave sandbox unify leave sandbox exit leave sandbox false call restore sandbox false unify restore sandbox false exit restore sandbox false fail neg may naf basekb path fail loop check loop check term frame pfc lib neg may naf basekb path info pfc lib neg may naf basekb path mpred core pl pfc lib trace or throw looped pfc lib neg may naf basekb path fail neg in basekb path fail loop check loop check term frame pfc lib neg in basekb path info pfc lib neg in basekb path mpred core pl pfc lib trace or throw looped pfc lib neg in basekb path fail basekb path call must sanity mquietly if true rtrace tat normal unify must sanity mquietly if true rtrace tat normal failure info why was true basekb path rtrace basekb path no proof for path no proof for path no proof for path name logicmoo pfc test sanity base neg test line path junit classname logicmoo pfc test sanity base neg junit cmd timeout foreground preserve status s sigkill k lmoo clif neg pfc saving junit var lib jenkins workspace logicmoo workspace test results jenkins report logicmoo junit test sanity base units logicmoo pfc test sanity base neg test line path junit xml mpred test path mpred test path mpred test path var lib jenkins workspace logicmoo workspace packs sys pfc t sanity base neg pfc mpred test test line naf path basekb path mpred test test line naf path basekb path passed info why was true basekb path no proof for path no proof for path no proof for path name logicmoo pfc test sanity base neg test line naf path junit classname logicmoo pfc test sanity base neg junit cmd timeout foreground preserve status s sigkill k lmoo clif neg pfc saving junit var lib jenkins workspace logicmoo workspace test results jenkins report logicmoo junit test sanity base units logicmoo pfc test sanity base neg test line naf path junit xml mpred test path mpred test test line naf path basekb path mpred test test line naf path basekb path passed info why was true basekb path no proof for path no proof for path no proof for path name logicmoo pfc test sanity base neg test line naf path junit classname logicmoo pfc test sanity base neg junit cmd timeout foreground preserve status s sigkill k lmoo clif neg pfc saving junit var lib jenkins workspace logicmoo workspace test results jenkins report logicmoo junit test sanity base units logicmoo pfc test sanity base neg test line naf path junit xml break skipped blocks on input break unused save junit results test completed exit dynamic junit prop dynamic junit prop dynamic junit prop totaltime issue search gitlab latest this build github failed var lib jenkins workspace logicmoo workspace bin lmoo junit minor k neg pfc returned | 0 |
143,224 | 19,161,568,558 | IssuesEvent | 2021-12-03 01:12:11 | manishshanker/https-to-http-data-submission | https://api.github.com/repos/manishshanker/https-to-http-data-submission | opened | CVE-2019-10746 (High) detected in mixin-deep-1.3.1.tgz | security vulnerability | ## CVE-2019-10746 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mixin-deep-1.3.1.tgz</b></p></summary>
<p>Deeply mix the properties of objects into the first object. Like merge-deep, but doesn't clone.</p>
<p>Library home page: <a href="https://registry.npmjs.org/mixin-deep/-/mixin-deep-1.3.1.tgz">https://registry.npmjs.org/mixin-deep/-/mixin-deep-1.3.1.tgz</a></p>
<p>Path to dependency file: /https-to-http-data-submission/package.json</p>
<p>Path to vulnerable library: https-to-http-data-submission/node_modules/mixin-deep/package.json</p>
<p>
Dependency Hierarchy:
- serve-https-1.6.3.tgz (Root Library)
- livereload-0.5.0.tgz
- chokidar-1.7.0.tgz
- readdirp-2.2.1.tgz
- micromatch-3.1.10.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- :x: **mixin-deep-1.3.1.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
mixin-deep is vulnerable to Prototype Pollution in versions before 1.3.2 and version 2.0.0. The function mixin-deep could be tricked into adding or modifying properties of Object.prototype using a constructor payload.
<p>Publish Date: 2019-08-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10746>CVE-2019-10746</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/jonschlinkert/mixin-deep/commit/8f464c8ce9761a8c9c2b3457eaeee9d404fa7af9">https://github.com/jonschlinkert/mixin-deep/commit/8f464c8ce9761a8c9c2b3457eaeee9d404fa7af9</a></p>
<p>Release Date: 2019-08-23</p>
<p>Fix Resolution: 1.3.2,2.0.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 | CVE-2019-10746 (High) detected in mixin-deep-1.3.1.tgz - ## CVE-2019-10746 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mixin-deep-1.3.1.tgz</b></p></summary>
<p>Deeply mix the properties of objects into the first object. Like merge-deep, but doesn't clone.</p>
<p>Library home page: <a href="https://registry.npmjs.org/mixin-deep/-/mixin-deep-1.3.1.tgz">https://registry.npmjs.org/mixin-deep/-/mixin-deep-1.3.1.tgz</a></p>
<p>Path to dependency file: /https-to-http-data-submission/package.json</p>
<p>Path to vulnerable library: https-to-http-data-submission/node_modules/mixin-deep/package.json</p>
<p>
Dependency Hierarchy:
- serve-https-1.6.3.tgz (Root Library)
- livereload-0.5.0.tgz
- chokidar-1.7.0.tgz
- readdirp-2.2.1.tgz
- micromatch-3.1.10.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- :x: **mixin-deep-1.3.1.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
mixin-deep is vulnerable to Prototype Pollution in versions before 1.3.2 and version 2.0.0. The function mixin-deep could be tricked into adding or modifying properties of Object.prototype using a constructor payload.
<p>Publish Date: 2019-08-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10746>CVE-2019-10746</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/jonschlinkert/mixin-deep/commit/8f464c8ce9761a8c9c2b3457eaeee9d404fa7af9">https://github.com/jonschlinkert/mixin-deep/commit/8f464c8ce9761a8c9c2b3457eaeee9d404fa7af9</a></p>
<p>Release Date: 2019-08-23</p>
<p>Fix Resolution: 1.3.2,2.0.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 | cve high detected in mixin deep tgz cve high severity vulnerability vulnerable library mixin deep tgz deeply mix the properties of objects into the first object like merge deep but doesn t clone library home page a href path to dependency file https to http data submission package json path to vulnerable library https to http data submission node modules mixin deep package json dependency hierarchy serve https tgz root library livereload tgz chokidar tgz readdirp tgz micromatch tgz snapdragon tgz base tgz x mixin deep tgz vulnerable library vulnerability details mixin deep is vulnerable to prototype pollution in versions before and version the function mixin deep could be tricked into adding or modifying properties of object prototype using a constructor payload publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
16,816 | 9,533,021,098 | IssuesEvent | 2019-04-29 20:09:37 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | sql: RowFetcher.processValueSingle should produce EncDatumRows | C-performance | `EncDatum`s are designed to allow "tunneling" encoded values through distsql without unnecessary decoding and re-encoding.
`RowFetcher` should be modified to return `EncDatum`s instead of `Datum`s (see `readerBase.nextRow()`).
This will affect the regular SQL path so we need run benchmarks and make sure we don't cause regressions.
CC @paperstreet
| True | sql: RowFetcher.processValueSingle should produce EncDatumRows - `EncDatum`s are designed to allow "tunneling" encoded values through distsql without unnecessary decoding and re-encoding.
`RowFetcher` should be modified to return `EncDatum`s instead of `Datum`s (see `readerBase.nextRow()`).
This will affect the regular SQL path so we need run benchmarks and make sure we don't cause regressions.
CC @paperstreet
| non_priority | sql rowfetcher processvaluesingle should produce encdatumrows encdatum s are designed to allow tunneling encoded values through distsql without unnecessary decoding and re encoding rowfetcher should be modified to return encdatum s instead of datum s see readerbase nextrow this will affect the regular sql path so we need run benchmarks and make sure we don t cause regressions cc paperstreet | 0 |
302,070 | 26,121,044,355 | IssuesEvent | 2022-12-28 12:41:01 | Exiled-Team/EXILED | https://api.github.com/repos/Exiled-Team/EXILED | opened | [BUG] Crash until start | requires-testing | The server crashes before it has time to boot. Here are all the latest posts:
`[2022-12-28 04:40:16.523 -08:00] SCP: Secret Laboratory - LocalAdmin v. 2.5.8
[2022-12-28 04:40:16.524 -08:00]
[2022-12-28 04:40:16.525 -08:00] Licensed under The MIT License (use command "license" to get license text).
[2022-12-28 04:40:16.526 -08:00] Copyright by Łukasz "zabszk" Jurczyk and KernelError, 2019 - 2022
[2022-12-28 04:40:16.527 -08:00]
[2022-12-28 04:40:16.528 -08:00] Type 'help' to get list of available commands.
[2022-12-28 04:40:16.528 -08:00]
[2022-12-28 04:40:16.532 -08:00] Started new session on port 7777.
[2022-12-28 04:40:16.534 -08:00] Trying to start server...
[2022-12-28 04:40:16.536 -08:00] Executing: SCPSL.exe
[2022-12-28 04:40:31.430 -08:00] Game process exited and has been killed, no need to kill it.
[2022-12-28 04:40:31.434 -08:00] The game process has been terminated...
[2022-12-28 04:40:31.617 -08:00] Restarts limit exceeded.` | 1.0 | [BUG] Crash until start - The server crashes before it has time to boot. Here are all the latest posts:
`[2022-12-28 04:40:16.523 -08:00] SCP: Secret Laboratory - LocalAdmin v. 2.5.8
[2022-12-28 04:40:16.524 -08:00]
[2022-12-28 04:40:16.525 -08:00] Licensed under The MIT License (use command "license" to get license text).
[2022-12-28 04:40:16.526 -08:00] Copyright by Łukasz "zabszk" Jurczyk and KernelError, 2019 - 2022
[2022-12-28 04:40:16.527 -08:00]
[2022-12-28 04:40:16.528 -08:00] Type 'help' to get list of available commands.
[2022-12-28 04:40:16.528 -08:00]
[2022-12-28 04:40:16.532 -08:00] Started new session on port 7777.
[2022-12-28 04:40:16.534 -08:00] Trying to start server...
[2022-12-28 04:40:16.536 -08:00] Executing: SCPSL.exe
[2022-12-28 04:40:31.430 -08:00] Game process exited and has been killed, no need to kill it.
[2022-12-28 04:40:31.434 -08:00] The game process has been terminated...
[2022-12-28 04:40:31.617 -08:00] Restarts limit exceeded.` | non_priority | crash until start the server crashes before it has time to boot here are all the latest posts scp secret laboratory localadmin v licensed under the mit license use command license to get license text copyright by łukasz zabszk jurczyk and kernelerror type help to get list of available commands started new session on port trying to start server executing scpsl exe game process exited and has been killed no need to kill it the game process has been terminated restarts limit exceeded | 0 |
148,682 | 13,244,168,812 | IssuesEvent | 2020-08-19 12:39:34 | RoyMagnussen/CottonBox-Data-Centric-Version | https://api.github.com/repos/RoyMagnussen/CottonBox-Data-Centric-Version | closed | [CHANGE REQUEST] User stories | documentation enhancement | #### Describe the change wanted
- [ ] Add user stories to help provide insight into what users of E-Commerce sites would like to see implemented.
| 1.0 | [CHANGE REQUEST] User stories - #### Describe the change wanted
- [ ] Add user stories to help provide insight into what users of E-Commerce sites would like to see implemented.
| non_priority | user stories describe the change wanted add user stories to help provide insight into what users of e commerce sites would like to see implemented | 0 |
43,460 | 17,606,804,131 | IssuesEvent | 2021-08-17 18:11:59 | cityofaustin/atd-data-tech | https://api.github.com/repos/cityofaustin/atd-data-tech | opened | Create and send bike map (blowup) template to Sophia | Workgroup: ATSD Type: Map Request Service: Geo Project: Print Bike Map | Sophia is updating some of the art that overlays the blow up side of the bike map. She needs a template Illustrator file in which she can create art, and form which we can import into the main/parent document that combines infographics and map art. | 1.0 | Create and send bike map (blowup) template to Sophia - Sophia is updating some of the art that overlays the blow up side of the bike map. She needs a template Illustrator file in which she can create art, and form which we can import into the main/parent document that combines infographics and map art. | non_priority | create and send bike map blowup template to sophia sophia is updating some of the art that overlays the blow up side of the bike map she needs a template illustrator file in which she can create art and form which we can import into the main parent document that combines infographics and map art | 0 |
88,453 | 15,801,569,744 | IssuesEvent | 2021-04-03 05:32:39 | code4romania/de-urgenta-backend | https://api.github.com/repos/code4romania/de-urgenta-backend | closed | Configure Authorization for Hangfire | back-end bug :bug: research security | # in `DeUrgenta.RecurringJobs`
Hangfire Dashboard exposes sensitive information about your background jobs, including method names and serialized arguments as well as gives you an opportunity to manage them by performing different actions – retry, delete, trigger, etc. So it is really important to restrict access to the Dashboard.
To make it secure by default, only **local requests are allowed**, however you can change this!
More details here:
https://docs.hangfire.io/en/latest/configuration/using-dashboard.html#configuring-authorization
We want to be able to access the dashboard from a remote container, not just from the same server the app is runnnig on. | True | Configure Authorization for Hangfire - # in `DeUrgenta.RecurringJobs`
Hangfire Dashboard exposes sensitive information about your background jobs, including method names and serialized arguments as well as gives you an opportunity to manage them by performing different actions – retry, delete, trigger, etc. So it is really important to restrict access to the Dashboard.
To make it secure by default, only **local requests are allowed**, however you can change this!
More details here:
https://docs.hangfire.io/en/latest/configuration/using-dashboard.html#configuring-authorization
We want to be able to access the dashboard from a remote container, not just from the same server the app is runnnig on. | non_priority | configure authorization for hangfire in deurgenta recurringjobs hangfire dashboard exposes sensitive information about your background jobs including method names and serialized arguments as well as gives you an opportunity to manage them by performing different actions – retry delete trigger etc so it is really important to restrict access to the dashboard to make it secure by default only local requests are allowed however you can change this more details here we want to be able to access the dashboard from a remote container not just from the same server the app is runnnig on | 0 |
75,085 | 20,621,540,399 | IssuesEvent | 2022-03-07 17:54:13 | rstudio/rstudio | https://api.github.com/repos/rstudio/rstudio | opened | Unit test failures in renv, themes | builds automation | Unit test failures (in addition to the ones being tracked here: #10683):
`renv`:
```
[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-74)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-75)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-76)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-77)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-78)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-79)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-80)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-81)[2022-03-05T01:42:24.948Z]
/ | 0 | renv
/ | 0 | renv The following package(s) will be updated in the lockfile:
[2022-03-05T01:42:24.948Z]
[2022-03-05T01:42:24.948Z] # CRAN ===============================
[2022-03-05T01:42:24.948Z] - renv [* -> 0.15.3]
[2022-03-05T01:42:24.948Z]
[2022-03-05T01:42:29.110Z]
- | 1 0 | renv
x | 1 0 | renv [0.8s]
[2022-03-05T01:42:29.110Z] --------------------------------------------------------------------------------
[2022-03-05T01:42:29.110Z] Failure (test-renv.R:37:4): .rs.rpc.renv_init() preserves current repositories
[2022-03-05T01:42:29.110Z] as.list(lockfile$R$Repositories) not identical to list(RSPM = "https://packagemanager.rstudio.com/cran/latest[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-82)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-83)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-84)").
[2022-03-05T01:42:29.110Z] Names: 1 string mismatch
[2022-03-05T01:42:29.110Z] Length mismatch: comparison on first 1 components
[2022-03-05T01:42:29.110Z] Component 1: 1 string mismatch
```
`themes`:
```
[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-93)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-94)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-95)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-96)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-97)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-98)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-99)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-100)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-101)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-102)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-103)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-104)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-105)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-106)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-107)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-108)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-109)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-110)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-111)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-112)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-113)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-114)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-115)hemes
x | 1 1 564 | themes [34.5s]
[2022-03-05T01:43:00.926Z] --------------------------------------------------------------------------------
[2022-03-05T01:43:00.926Z] Warning (test-themes.R:1674:1): (code run outside of `test_that()`)
[2022-03-05T01:43:00.926Z] cannot remove file './themes/localInstall', reason 'Directory not empty'
[2022-03-05T01:43:00.926Z] Backtrace:
[2022-03-05T01:43:00.926Z] 1. test_that_wrapped(...)
[2022-03-05T01:43:00.926Z] at test-themes.R:1674:0
[2022-03-05T01:43:00.926Z] 2. AFTER_FUN()
[2022-03-05T01:43:00.926Z] at test-themes.R:254:6
[2022-03-05T01:43:00.926Z] 3. .rs.removeTheme(names(themes)[40], .rs.getThemes())
[2022-03-05T01:43:00.926Z] at test-themes.R:1689:3
[2022-03-05T01:43:00.926Z] 4. base::file.remove(filePath)
[2022-03-05T01:43:00.926Z]
[2022-03-05T01:43:00.926Z] Error (test-themes.R:1674:1): (code run outside of `test_that()`)
[2022-03-05T01:43:00.926Z] Error in `.rs.removeTheme(names(themes)[40], .rs.getThemes())`: Please check your file system permissions.
[2022-03-05T01:43:00.926Z] Backtrace:
[2022-03-05T01:43:00.926Z] 1. test_that_wrapped(...)
[2022-03-05T01:43:00.926Z] at test-themes.R:1674:0
[2022-03-05T01:43:00.926Z] 2. AFTER_FUN()
[2022-03-05T01:43:00.926Z] at test-themes.R:254:6
[2022-03-05T01:43:00.926Z] 3. .rs.removeTheme(names(themes)[40], .rs.getThemes())
[2022-03-05T01:43:00.926Z] at test-themes.R:1689:3
[2022-03-05T01:43:00.926Z] --------------------------------------------------------------------------------
[2022-03-05T01:43:00.926Z]
``` | 1.0 | Unit test failures in renv, themes - Unit test failures (in addition to the ones being tracked here: #10683):
`renv`:
```
[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-74)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-75)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-76)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-77)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-78)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-79)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-80)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-81)[2022-03-05T01:42:24.948Z]
/ | 0 | renv
/ | 0 | renv The following package(s) will be updated in the lockfile:
[2022-03-05T01:42:24.948Z]
[2022-03-05T01:42:24.948Z] # CRAN ===============================
[2022-03-05T01:42:24.948Z] - renv [* -> 0.15.3]
[2022-03-05T01:42:24.948Z]
[2022-03-05T01:42:29.110Z]
- | 1 0 | renv
x | 1 0 | renv [0.8s]
[2022-03-05T01:42:29.110Z] --------------------------------------------------------------------------------
[2022-03-05T01:42:29.110Z] Failure (test-renv.R:37:4): .rs.rpc.renv_init() preserves current repositories
[2022-03-05T01:42:29.110Z] as.list(lockfile$R$Repositories) not identical to list(RSPM = "https://packagemanager.rstudio.com/cran/latest[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-82)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-83)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-84)").
[2022-03-05T01:42:29.110Z] Names: 1 string mismatch
[2022-03-05T01:42:29.110Z] Length mismatch: comparison on first 1 components
[2022-03-05T01:42:29.110Z] Component 1: 1 string mismatch
```
`themes`:
```
[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-93)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-94)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-95)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-96)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-97)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-98)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-99)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-100)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-101)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-102)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-103)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-104)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-105)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-106)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-107)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-108)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-109)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-110)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-111)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-112)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-113)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-114)[](https://build.rstudioservices.com/blue/organizations/jenkins/IDE%2Fopen-source-pipeline/detail/main/963/pipeline/1449#step-1508-log-115)hemes
x | 1 1 564 | themes [34.5s]
[2022-03-05T01:43:00.926Z] --------------------------------------------------------------------------------
[2022-03-05T01:43:00.926Z] Warning (test-themes.R:1674:1): (code run outside of `test_that()`)
[2022-03-05T01:43:00.926Z] cannot remove file './themes/localInstall', reason 'Directory not empty'
[2022-03-05T01:43:00.926Z] Backtrace:
[2022-03-05T01:43:00.926Z] 1. test_that_wrapped(...)
[2022-03-05T01:43:00.926Z] at test-themes.R:1674:0
[2022-03-05T01:43:00.926Z] 2. AFTER_FUN()
[2022-03-05T01:43:00.926Z] at test-themes.R:254:6
[2022-03-05T01:43:00.926Z] 3. .rs.removeTheme(names(themes)[40], .rs.getThemes())
[2022-03-05T01:43:00.926Z] at test-themes.R:1689:3
[2022-03-05T01:43:00.926Z] 4. base::file.remove(filePath)
[2022-03-05T01:43:00.926Z]
[2022-03-05T01:43:00.926Z] Error (test-themes.R:1674:1): (code run outside of `test_that()`)
[2022-03-05T01:43:00.926Z] Error in `.rs.removeTheme(names(themes)[40], .rs.getThemes())`: Please check your file system permissions.
[2022-03-05T01:43:00.926Z] Backtrace:
[2022-03-05T01:43:00.926Z] 1. test_that_wrapped(...)
[2022-03-05T01:43:00.926Z] at test-themes.R:1674:0
[2022-03-05T01:43:00.926Z] 2. AFTER_FUN()
[2022-03-05T01:43:00.926Z] at test-themes.R:254:6
[2022-03-05T01:43:00.926Z] 3. .rs.removeTheme(names(themes)[40], .rs.getThemes())
[2022-03-05T01:43:00.926Z] at test-themes.R:1689:3
[2022-03-05T01:43:00.926Z] --------------------------------------------------------------------------------
[2022-03-05T01:43:00.926Z]
``` | non_priority | unit test failures in renv themes unit test failures in addition to the ones being tracked here renv renv renv the following package s will be updated in the lockfile cran renv renv x renv failure test renv r rs rpc renv init preserves current repositories as list lockfile r repositories not identical to list rspm names string mismatch length mismatch comparison on first components component string mismatch themes x themes warning test themes r code run outside of test that cannot remove file themes localinstall reason directory not empty backtrace test that wrapped at test themes r after fun at test themes r rs removetheme names themes rs getthemes at test themes r base file remove filepath error test themes r code run outside of test that error in rs removetheme names themes rs getthemes please check your file system permissions backtrace test that wrapped at test themes r after fun at test themes r rs removetheme names themes rs getthemes at test themes r | 0 |
117,941 | 17,569,795,251 | IssuesEvent | 2021-08-14 12:48:21 | edgexfoundry/edgex-go | https://api.github.com/repos/edgexfoundry/edgex-go | closed | [Security] Remove `curl` executable from secretstore-setup | enhancement security_audit | <!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅
Oh hi there! 😄
To expedite issue processing please search open and closed issues before submitting a new one.
Existing issues often contain information about workarounds, resolution, or progress updates.
🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅-->
# 🚀 Feature Request
### Relevant Package
<!-- Can you pin-point one or more EdgeX services the are relevant for this feature request? -->
<!-- ✍️edit: -->
This feature request is for `secretstore-setup`
### Description
<!-- ✍️-->
`curl` executable is not being used in service `secretstore-setup` and should be removed to reduce the maintenance and security vulnerability it may bring.
### Describe the solution you'd like
<!-- ✍️-->
Remove `curl` from the Dockerfile of `secretstore-setup`.
### Describe alternatives you've considered
<!-- ✍️--> Have you considered any alternative solutions or workarounds?
| True | [Security] Remove `curl` executable from secretstore-setup - <!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅
Oh hi there! 😄
To expedite issue processing please search open and closed issues before submitting a new one.
Existing issues often contain information about workarounds, resolution, or progress updates.
🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅-->
# 🚀 Feature Request
### Relevant Package
<!-- Can you pin-point one or more EdgeX services the are relevant for this feature request? -->
<!-- ✍️edit: -->
This feature request is for `secretstore-setup`
### Description
<!-- ✍️-->
`curl` executable is not being used in service `secretstore-setup` and should be removed to reduce the maintenance and security vulnerability it may bring.
### Describe the solution you'd like
<!-- ✍️-->
Remove `curl` from the Dockerfile of `secretstore-setup`.
### Describe alternatives you've considered
<!-- ✍️--> Have you considered any alternative solutions or workarounds?
| non_priority | remove curl executable from secretstore setup 🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅 oh hi there 😄 to expedite issue processing please search open and closed issues before submitting a new one existing issues often contain information about workarounds resolution or progress updates 🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅 🚀 feature request relevant package this feature request is for secretstore setup description curl executable is not being used in service secretstore setup and should be removed to reduce the maintenance and security vulnerability it may bring describe the solution you d like remove curl from the dockerfile of secretstore setup describe alternatives you ve considered have you considered any alternative solutions or workarounds | 0 |
116,088 | 17,358,342,187 | IssuesEvent | 2021-07-29 16:58:19 | Tim-sandbox/webgoat-trng | https://api.github.com/repos/Tim-sandbox/webgoat-trng | opened | CVE-2019-14900 (Medium) detected in hibernate-core-5.4.9.Final.jar | security vulnerability | ## CVE-2019-14900 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hibernate-core-5.4.9.Final.jar</b></p></summary>
<p>Hibernate's core ORM functionality</p>
<p>Library home page: <a href="http://hibernate.org/orm">http://hibernate.org/orm</a></p>
<p>Path to dependency file: webgoat-trng/webgoat-integration-tests/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/hibernate/hibernate-core/5.4.9.Final/hibernate-core-5.4.9.Final.jar</p>
<p>
Dependency Hierarchy:
- webwolf-v8.1.0.jar (Root Library)
- spring-boot-starter-data-jpa-2.2.2.RELEASE.jar
- :x: **hibernate-core-5.4.9.Final.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Tim-sandbox/webgoat-trng/commit/35c20cdfd5acad60536ca6b0402f619e18097690">35c20cdfd5acad60536ca6b0402f619e18097690</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>
A flaw was found in Hibernate ORM in versions before 5.3.18, 5.4.18 and 5.5.0.Beta1. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SELECT or GROUP BY parts of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks.
<p>Publish Date: 2020-07-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14900>CVE-2019-14900</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14900">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14900</a></p>
<p>Release Date: 2020-07-06</p>
<p>Fix Resolution: org.hibernate:hibernate-core:5.4.18.Final</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.hibernate","packageName":"hibernate-core","packageVersion":"5.4.9.Final","packageFilePaths":["/webgoat-integration-tests/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.owasp.webgoat:webwolf:v8.1.0;org.springframework.boot:spring-boot-starter-data-jpa:2.2.2.RELEASE;org.hibernate:hibernate-core:5.4.9.Final","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.hibernate:hibernate-core:5.4.18.Final"}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2019-14900","vulnerabilityDetails":"A flaw was found in Hibernate ORM in versions before 5.3.18, 5.4.18 and 5.5.0.Beta1. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SELECT or GROUP BY parts of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14900","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"Low","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2019-14900 (Medium) detected in hibernate-core-5.4.9.Final.jar - ## CVE-2019-14900 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hibernate-core-5.4.9.Final.jar</b></p></summary>
<p>Hibernate's core ORM functionality</p>
<p>Library home page: <a href="http://hibernate.org/orm">http://hibernate.org/orm</a></p>
<p>Path to dependency file: webgoat-trng/webgoat-integration-tests/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/hibernate/hibernate-core/5.4.9.Final/hibernate-core-5.4.9.Final.jar</p>
<p>
Dependency Hierarchy:
- webwolf-v8.1.0.jar (Root Library)
- spring-boot-starter-data-jpa-2.2.2.RELEASE.jar
- :x: **hibernate-core-5.4.9.Final.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Tim-sandbox/webgoat-trng/commit/35c20cdfd5acad60536ca6b0402f619e18097690">35c20cdfd5acad60536ca6b0402f619e18097690</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>
A flaw was found in Hibernate ORM in versions before 5.3.18, 5.4.18 and 5.5.0.Beta1. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SELECT or GROUP BY parts of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks.
<p>Publish Date: 2020-07-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14900>CVE-2019-14900</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14900">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14900</a></p>
<p>Release Date: 2020-07-06</p>
<p>Fix Resolution: org.hibernate:hibernate-core:5.4.18.Final</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.hibernate","packageName":"hibernate-core","packageVersion":"5.4.9.Final","packageFilePaths":["/webgoat-integration-tests/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.owasp.webgoat:webwolf:v8.1.0;org.springframework.boot:spring-boot-starter-data-jpa:2.2.2.RELEASE;org.hibernate:hibernate-core:5.4.9.Final","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.hibernate:hibernate-core:5.4.18.Final"}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2019-14900","vulnerabilityDetails":"A flaw was found in Hibernate ORM in versions before 5.3.18, 5.4.18 and 5.5.0.Beta1. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SELECT or GROUP BY parts of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14900","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"Low","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in hibernate core final jar cve medium severity vulnerability vulnerable library hibernate core final jar hibernate s core orm functionality library home page a href path to dependency file webgoat trng webgoat integration tests pom xml path to vulnerable library home wss scanner repository org hibernate hibernate core final hibernate core final jar dependency hierarchy webwolf jar root library spring boot starter data jpa release jar x hibernate core final jar vulnerable library found in head commit a href found in base branch main vulnerability details a flaw was found in hibernate orm in versions before and a sql injection in the implementation of the jpa criteria api can permit unsanitized literals when a literal is used in the select or group by parts of the query this flaw could allow an attacker to access unauthorized information or possibly conduct further attacks publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org hibernate hibernate core final isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree org owasp webgoat webwolf org springframework boot spring boot starter data jpa release org hibernate hibernate core final isminimumfixversionavailable true minimumfixversion org hibernate hibernate core final basebranches vulnerabilityidentifier cve vulnerabilitydetails a flaw was found in hibernate orm in versions before and a sql injection in the implementation of the jpa criteria api can permit unsanitized literals when a literal is used in the select or group by parts of the query this flaw could allow an attacker to access unauthorized information or possibly conduct further attacks vulnerabilityurl | 0 |
142,450 | 19,090,523,833 | IssuesEvent | 2021-11-29 11:33:43 | sultanabubaker/NuGet_Project_SDK_NonSDK | https://api.github.com/repos/sultanabubaker/NuGet_Project_SDK_NonSDK | opened | CVE-2020-1219 (High) detected in microsoft.chakracore.1.8.1.nupkg | security vulnerability | ## CVE-2020-1219 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>microsoft.chakracore.1.8.1.nupkg</b></p></summary>
<p>ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.chakracore.1.8.1.nupkg">https://api.nuget.org/packages/microsoft.chakracore.1.8.1.nupkg</a></p>
<p>Path to dependency file: NuGet_Project_SDK_NonSDK/SDK/SDK.csproj</p>
<p>Path to vulnerable library: crosoft.chakracore/1.8.1/microsoft.chakracore.1.8.1.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.chakracore.1.8.1.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sultanabubaker/NuGet_Project_SDK_NonSDK/commit/2cdcbe42d2efe636b5e9b1d4c29c9da6e2c9b927">2cdcbe42d2efe636b5e9b1d4c29c9da6e2c9b927</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A remote code execution vulnerability exists in the way that Microsoft browsers access objects in memory, aka 'Microsoft Browser Memory Corruption Vulnerability'.
<p>Publish Date: 2020-06-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-1219>CVE-2020-1219</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: High
- 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://github.com/Microsoft/ChakraCore/wiki/Roadmap#v11120">https://github.com/Microsoft/ChakraCore/wiki/Roadmap#v11120</a></p>
<p>Release Date: 2020-06-09</p>
<p>Fix Resolution: v1.11.20</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Nuget","packageName":"Microsoft.ChakraCore","packageVersion":"1.8.1","packageFilePaths":["/SDK/SDK.csproj"],"isTransitiveDependency":false,"dependencyTree":"Microsoft.ChakraCore:1.8.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"v1.11.20","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-1219","vulnerabilityDetails":"A remote code execution vulnerability exists in the way that Microsoft browsers access objects in memory, aka \u0027Microsoft Browser Memory Corruption Vulnerability\u0027.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-1219","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"Required","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-1219 (High) detected in microsoft.chakracore.1.8.1.nupkg - ## CVE-2020-1219 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>microsoft.chakracore.1.8.1.nupkg</b></p></summary>
<p>ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.chakracore.1.8.1.nupkg">https://api.nuget.org/packages/microsoft.chakracore.1.8.1.nupkg</a></p>
<p>Path to dependency file: NuGet_Project_SDK_NonSDK/SDK/SDK.csproj</p>
<p>Path to vulnerable library: crosoft.chakracore/1.8.1/microsoft.chakracore.1.8.1.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.chakracore.1.8.1.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sultanabubaker/NuGet_Project_SDK_NonSDK/commit/2cdcbe42d2efe636b5e9b1d4c29c9da6e2c9b927">2cdcbe42d2efe636b5e9b1d4c29c9da6e2c9b927</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A remote code execution vulnerability exists in the way that Microsoft browsers access objects in memory, aka 'Microsoft Browser Memory Corruption Vulnerability'.
<p>Publish Date: 2020-06-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-1219>CVE-2020-1219</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: High
- 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://github.com/Microsoft/ChakraCore/wiki/Roadmap#v11120">https://github.com/Microsoft/ChakraCore/wiki/Roadmap#v11120</a></p>
<p>Release Date: 2020-06-09</p>
<p>Fix Resolution: v1.11.20</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Nuget","packageName":"Microsoft.ChakraCore","packageVersion":"1.8.1","packageFilePaths":["/SDK/SDK.csproj"],"isTransitiveDependency":false,"dependencyTree":"Microsoft.ChakraCore:1.8.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"v1.11.20","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-1219","vulnerabilityDetails":"A remote code execution vulnerability exists in the way that Microsoft browsers access objects in memory, aka \u0027Microsoft Browser Memory Corruption Vulnerability\u0027.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-1219","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"Required","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in microsoft chakracore nupkg cve high severity vulnerability vulnerable library microsoft chakracore nupkg chakracore is the core part of the chakra javascript engine that powers microsoft edge library home page a href path to dependency file nuget project sdk nonsdk sdk sdk csproj path to vulnerable library crosoft chakracore microsoft chakracore nupkg dependency hierarchy x microsoft chakracore nupkg vulnerable library found in head commit a href found in base branch master vulnerability details a remote code execution vulnerability exists in the way that microsoft browsers access objects in memory aka microsoft browser memory corruption vulnerability publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high 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 rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree microsoft chakracore isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails a remote code execution vulnerability exists in the way that microsoft browsers access objects in memory aka browser memory corruption vulnerability vulnerabilityurl | 0 |
281,422 | 30,888,835,859 | IssuesEvent | 2023-08-04 01:53:45 | nidhi7598/linux-4.1.15_CVE-2019-10220 | https://api.github.com/repos/nidhi7598/linux-4.1.15_CVE-2019-10220 | reopened | CVE-2018-14613 (Medium) detected in linuxlinux-4.4.302 | Mend: dependency security vulnerability | ## CVE-2018-14613 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.4.302</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/nidhi7598/linux-4.1.15_CVE-2019-10220/commit/6a0d304d962ca933d73f507ce02157ef2791851c">6a0d304d962ca933d73f507ce02157ef2791851c</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/btrfs/extent-tree.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/btrfs/extent-tree.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in the Linux kernel through 4.17.10. There is an invalid pointer dereference in io_ctl_map_page() when mounting and operating a crafted btrfs image, because of a lack of block group item validation in check_leaf_item in fs/btrfs/tree-checker.c.
<p>Publish Date: 2018-07-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-14613>CVE-2018-14613</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-14613">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-14613</a></p>
<p>Release Date: 2018-07-27</p>
<p>Fix Resolution: v4.19-rc1</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-2018-14613 (Medium) detected in linuxlinux-4.4.302 - ## CVE-2018-14613 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.4.302</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/nidhi7598/linux-4.1.15_CVE-2019-10220/commit/6a0d304d962ca933d73f507ce02157ef2791851c">6a0d304d962ca933d73f507ce02157ef2791851c</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/btrfs/extent-tree.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/btrfs/extent-tree.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in the Linux kernel through 4.17.10. There is an invalid pointer dereference in io_ctl_map_page() when mounting and operating a crafted btrfs image, because of a lack of block group item validation in check_leaf_item in fs/btrfs/tree-checker.c.
<p>Publish Date: 2018-07-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-14613>CVE-2018-14613</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-14613">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-14613</a></p>
<p>Release Date: 2018-07-27</p>
<p>Fix Resolution: v4.19-rc1</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 linuxlinux cve medium severity vulnerability vulnerable library linuxlinux the linux kernel library home page a href found in head commit a href found in base branch master vulnerable source files fs btrfs extent tree c fs btrfs extent tree c vulnerability details an issue was discovered in the linux kernel through there is an invalid pointer dereference in io ctl map page when mounting and operating a crafted btrfs image because of a lack of block group item validation in check leaf item in fs btrfs tree checker c publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
156,069 | 19,809,438,928 | IssuesEvent | 2022-01-19 10:33:47 | benchmarkdebricked/angular | https://api.github.com/repos/benchmarkdebricked/angular | opened | CVE-2018-21270 (Medium) detected in stringstream-0.0.5.tgz | security vulnerability | ## CVE-2018-21270 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>stringstream-0.0.5.tgz</b></p></summary>
<p>Encode and decode streams into string streams</p>
<p>Library home page: <a href="https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz">https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz</a></p>
<p>
Dependency Hierarchy:
- protractor-5.1.2.tgz (Root Library)
- webdriver-manager-12.0.6.tgz
- request-2.83.0.tgz
- :x: **stringstream-0.0.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/benchmarkdebricked/angular/commit/d5d066ec5f183ee78b6a36dc6eaa6714647bc518">d5d066ec5f183ee78b6a36dc6eaa6714647bc518</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Versions less than 0.0.6 of the Node.js stringstream module are vulnerable to an out-of-bounds read because of allocation of uninitialized buffers when a number is passed in the input stream (when using Node.js 4.x).
<p>Publish Date: 2020-12-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-21270>CVE-2018-21270</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-21270">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-21270</a></p>
<p>Release Date: 2020-12-03</p>
<p>Fix Resolution: 0.0.6</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2018-21270 (Medium) detected in stringstream-0.0.5.tgz - ## CVE-2018-21270 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>stringstream-0.0.5.tgz</b></p></summary>
<p>Encode and decode streams into string streams</p>
<p>Library home page: <a href="https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz">https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz</a></p>
<p>
Dependency Hierarchy:
- protractor-5.1.2.tgz (Root Library)
- webdriver-manager-12.0.6.tgz
- request-2.83.0.tgz
- :x: **stringstream-0.0.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/benchmarkdebricked/angular/commit/d5d066ec5f183ee78b6a36dc6eaa6714647bc518">d5d066ec5f183ee78b6a36dc6eaa6714647bc518</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Versions less than 0.0.6 of the Node.js stringstream module are vulnerable to an out-of-bounds read because of allocation of uninitialized buffers when a number is passed in the input stream (when using Node.js 4.x).
<p>Publish Date: 2020-12-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-21270>CVE-2018-21270</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-21270">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-21270</a></p>
<p>Release Date: 2020-12-03</p>
<p>Fix Resolution: 0.0.6</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in stringstream tgz cve medium severity vulnerability vulnerable library stringstream tgz encode and decode streams into string streams library home page a href dependency hierarchy protractor tgz root library webdriver manager tgz request tgz x stringstream tgz vulnerable library found in head commit a href vulnerability details versions less than of the node js stringstream module are vulnerable to an out of bounds read because of allocation of uninitialized buffers when a number is passed in the input stream when using node js x publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact none availability impact 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 |
4,856 | 3,087,941,329 | IssuesEvent | 2015-08-25 14:26:42 | catapult-project/catapult | https://api.github.com/repos/catapult-project/catapult | closed | tr.ui.timeline_viewport_test.locationObj test is flaky | Bug Code Health P1 Trace Viewer | The [`TimelineViewport` tests](https://github.com/catapult-project/catapult/blob/7ed55e2e69b1e24dd21738d8e9bf069f5259e812/tracing/tracing/ui/timeline_viewport_test.html#L68-L142) violate testing best practices such as:
- Testing a single behavior in each test case
- Making any sense at all
I noticed this because the `locationObj` test is reliably failing on a clean checkout on my work desktop but not on others' computers. Trying to decipher why this is happening or the test's intent is darn near impossible: it could definitely use some lovin'. | 1.0 | tr.ui.timeline_viewport_test.locationObj test is flaky - The [`TimelineViewport` tests](https://github.com/catapult-project/catapult/blob/7ed55e2e69b1e24dd21738d8e9bf069f5259e812/tracing/tracing/ui/timeline_viewport_test.html#L68-L142) violate testing best practices such as:
- Testing a single behavior in each test case
- Making any sense at all
I noticed this because the `locationObj` test is reliably failing on a clean checkout on my work desktop but not on others' computers. Trying to decipher why this is happening or the test's intent is darn near impossible: it could definitely use some lovin'. | non_priority | tr ui timeline viewport test locationobj test is flaky the violate testing best practices such as testing a single behavior in each test case making any sense at all i noticed this because the locationobj test is reliably failing on a clean checkout on my work desktop but not on others computers trying to decipher why this is happening or the test s intent is darn near impossible it could definitely use some lovin | 0 |
11,564 | 8,410,206,491 | IssuesEvent | 2018-10-12 09:49:38 | zeppelinos/zos | https://api.github.com/repos/zeppelinos/zos | closed | Detect initial values in fields declarations and throw a warning | component:cli kind:enhancement topic:security | Setting an initial value for a field when declaring it does not work for proxies, since the value is set in the constructor (see https://github.com/zeppelinos/zos/issues/60 and https://github.com/zeppelinos/zos/pull/79 for more info).
```solidity
contract MyContract {
uint256 public hasInitialValue = 42;
}
```
Note that this is not a problem if the field is defined as `constant`.
We should detect these scenarios, in all contracts (plus their ancestors) and raise a warning. This warning should be run when ~adding~ pushing the contract. | True | Detect initial values in fields declarations and throw a warning - Setting an initial value for a field when declaring it does not work for proxies, since the value is set in the constructor (see https://github.com/zeppelinos/zos/issues/60 and https://github.com/zeppelinos/zos/pull/79 for more info).
```solidity
contract MyContract {
uint256 public hasInitialValue = 42;
}
```
Note that this is not a problem if the field is defined as `constant`.
We should detect these scenarios, in all contracts (plus their ancestors) and raise a warning. This warning should be run when ~adding~ pushing the contract. | non_priority | detect initial values in fields declarations and throw a warning setting an initial value for a field when declaring it does not work for proxies since the value is set in the constructor see and for more info solidity contract mycontract public hasinitialvalue note that this is not a problem if the field is defined as constant we should detect these scenarios in all contracts plus their ancestors and raise a warning this warning should be run when adding pushing the contract | 0 |
170,350 | 14,256,662,878 | IssuesEvent | 2020-11-20 01:34:17 | dafny-lang/dafny | https://api.github.com/repos/dafny-lang/dafny | closed | Feature request: access control to members of a class (private, public, protected) | documentation | To make sure that implementation details (namely internal state representation) are not exposed in the pre/post specifications of (public) operations of a class, it would be helpful to mark as private (or protected) the fields that represent the internal state, mark as public (but readonly) the state abstraction variables or functions, and mark as public the operations to be used by clients of the class.
Then Dafny should verify that explicit pre/post conditions of an operation (constructor, method, function or predicate) don't refer to members with less visibility.
| 1.0 | Feature request: access control to members of a class (private, public, protected) - To make sure that implementation details (namely internal state representation) are not exposed in the pre/post specifications of (public) operations of a class, it would be helpful to mark as private (or protected) the fields that represent the internal state, mark as public (but readonly) the state abstraction variables or functions, and mark as public the operations to be used by clients of the class.
Then Dafny should verify that explicit pre/post conditions of an operation (constructor, method, function or predicate) don't refer to members with less visibility.
| non_priority | feature request access control to members of a class private public protected to make sure that implementation details namely internal state representation are not exposed in the pre post specifications of public operations of a class it would be helpful to mark as private or protected the fields that represent the internal state mark as public but readonly the state abstraction variables or functions and mark as public the operations to be used by clients of the class then dafny should verify that explicit pre post conditions of an operation constructor method function or predicate don t refer to members with less visibility | 0 |
215,289 | 16,598,995,736 | IssuesEvent | 2021-06-01 16:41:25 | mbecker12/surface-rl-decoder | https://api.github.com/repos/mbecker12/surface-rl-decoder | opened | Create graphics for Q learning and PPO program structure | documentation | Depict different modules of the program
actors, replay memory, learner etc. | 1.0 | Create graphics for Q learning and PPO program structure - Depict different modules of the program
actors, replay memory, learner etc. | non_priority | create graphics for q learning and ppo program structure depict different modules of the program actors replay memory learner etc | 0 |
60,132 | 14,521,490,325 | IssuesEvent | 2020-12-14 07:27:55 | noobProgrammer35/ISPJ_BANK | https://api.github.com/repos/noobProgrammer35/ISPJ_BANK | opened | CVE-2018-14042 (Medium) detected in bootstrap-4.1.0.min.js, bootstrap-3.0.3.min.js | security vulnerability | ## CVE-2018-14042 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>bootstrap-4.1.0.min.js</b>, <b>bootstrap-3.0.3.min.js</b></p></summary>
<p>
<details><summary><b>bootstrap-4.1.0.min.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.1.0/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.1.0/js/bootstrap.min.js</a></p>
<p>Path to vulnerable library: ISPJ_BANK/static/js/bootstrap.min.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-4.1.0.min.js** (Vulnerable Library)
</details>
<details><summary><b>bootstrap-3.0.3.min.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.0.3/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.0.3/js/bootstrap.min.js</a></p>
<p>Path to dependency file: ISPJ_BANK/templates/cart.html</p>
<p>Path to vulnerable library: ISPJ_BANK/templates/cart.html</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.0.3.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/noobProgrammer35/ISPJ_BANK/commit/072c52986c61710d75853e3b4e49885e5c0df645">072c52986c61710d75853e3b4e49885e5c0df645</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip.
<p>Publish Date: 2018-07-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14042>CVE-2018-14042</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/twbs/bootstrap/pull/26630">https://github.com/twbs/bootstrap/pull/26630</a></p>
<p>Release Date: 2018-07-13</p>
<p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2018-14042 (Medium) detected in bootstrap-4.1.0.min.js, bootstrap-3.0.3.min.js - ## CVE-2018-14042 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>bootstrap-4.1.0.min.js</b>, <b>bootstrap-3.0.3.min.js</b></p></summary>
<p>
<details><summary><b>bootstrap-4.1.0.min.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.1.0/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.1.0/js/bootstrap.min.js</a></p>
<p>Path to vulnerable library: ISPJ_BANK/static/js/bootstrap.min.js</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-4.1.0.min.js** (Vulnerable Library)
</details>
<details><summary><b>bootstrap-3.0.3.min.js</b></p></summary>
<p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.0.3/js/bootstrap.min.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.0.3/js/bootstrap.min.js</a></p>
<p>Path to dependency file: ISPJ_BANK/templates/cart.html</p>
<p>Path to vulnerable library: ISPJ_BANK/templates/cart.html</p>
<p>
Dependency Hierarchy:
- :x: **bootstrap-3.0.3.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/noobProgrammer35/ISPJ_BANK/commit/072c52986c61710d75853e3b4e49885e5c0df645">072c52986c61710d75853e3b4e49885e5c0df645</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip.
<p>Publish Date: 2018-07-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14042>CVE-2018-14042</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/twbs/bootstrap/pull/26630">https://github.com/twbs/bootstrap/pull/26630</a></p>
<p>Release Date: 2018-07-13</p>
<p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in bootstrap min js bootstrap min js cve medium severity vulnerability vulnerable libraries bootstrap min js bootstrap min js bootstrap min js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library ispj bank static js bootstrap min js dependency hierarchy x bootstrap min js vulnerable library bootstrap min js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to dependency file ispj bank templates cart html path to vulnerable library ispj bank templates cart html dependency hierarchy x bootstrap min js vulnerable library found in head commit a href vulnerability details in bootstrap before xss is possible in the data container property of tooltip publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org webjars npm bootstrap org webjars bootstrap step up your open source security game with whitesource | 0 |
285,975 | 31,155,841,182 | IssuesEvent | 2023-08-16 13:05:10 | Trinadh465/linux-4.1.15_CVE-2018-5873 | https://api.github.com/repos/Trinadh465/linux-4.1.15_CVE-2018-5873 | closed | CVE-2016-4998 (High) detected in linuxlinux-4.1.52, linuxlinux-4.1.52 - autoclosed | Mend: dependency security vulnerability | ## CVE-2016-4998 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linuxlinux-4.1.52</b>, <b>linuxlinux-4.1.52</b></p></summary>
<p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
The IPT_SO_SET_REPLACE setsockopt implementation in the netfilter subsystem in the Linux kernel before 4.6 allows local users to cause a denial of service (out-of-bounds read) or possibly obtain sensitive information from kernel heap memory by leveraging in-container root access to provide a crafted offset value that leads to crossing a ruleset blob boundary.
<p>Publish Date: 2016-07-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-4998>CVE-2016-4998</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.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: 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://nvd.nist.gov/vuln/detail/CVE-2016-4998">https://nvd.nist.gov/vuln/detail/CVE-2016-4998</a></p>
<p>Release Date: 2016-07-03</p>
<p>Fix Resolution: 4.6</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-2016-4998 (High) detected in linuxlinux-4.1.52, linuxlinux-4.1.52 - autoclosed - ## CVE-2016-4998 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linuxlinux-4.1.52</b>, <b>linuxlinux-4.1.52</b></p></summary>
<p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
The IPT_SO_SET_REPLACE setsockopt implementation in the netfilter subsystem in the Linux kernel before 4.6 allows local users to cause a denial of service (out-of-bounds read) or possibly obtain sensitive information from kernel heap memory by leveraging in-container root access to provide a crafted offset value that leads to crossing a ruleset blob boundary.
<p>Publish Date: 2016-07-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-4998>CVE-2016-4998</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.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: 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://nvd.nist.gov/vuln/detail/CVE-2016-4998">https://nvd.nist.gov/vuln/detail/CVE-2016-4998</a></p>
<p>Release Date: 2016-07-03</p>
<p>Fix Resolution: 4.6</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in linuxlinux linuxlinux autoclosed cve high severity vulnerability vulnerable libraries linuxlinux linuxlinux vulnerability details the ipt so set replace setsockopt implementation in the netfilter subsystem in the linux kernel before allows local users to cause a denial of service out of bounds read or possibly obtain sensitive information from kernel heap memory by leveraging in container root access to provide a crafted offset value that leads to crossing a ruleset blob boundary publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
9,200 | 3,867,108,230 | IssuesEvent | 2016-04-09 02:25:07 | hyperledger/fabric | https://api.github.com/repos/hyperledger/fabric | closed | Chaincode - SIGNIFICANT API CHANGE - Run -> Invoke | Backlog chaincode | Today, the chaincode interface defines two functions.
```
// Chaincode is the standard chaincode callback interface that the chaincode developer needs to implement.
type Chaincode interface {
// Run method will be called during init and for every transaction
Run(stub *ChaincodeStub, function string, args []string) ([]byte, error)
// Query is to be used for read-only access to chaincode state
Query(stub *ChaincodeStub, function string, args []string) ([]byte, error)
}
```
There are two items we would like to change.
1. Documentation, the CLI, and the REST API use the term `Invoke` instead of `Run`. Therefore, we would like to rename the `Run` function to `Invoke`.
2. The existing `Run` function returns a `[]byte` which is mostly unused and causes confusion. We would like to remove this from the return value.
The new Chaincode interface will be
```
// Chaincode is the standard chaincode callback interface that the chaincode developer needs to implement.
type Chaincode interface {
// Invoke method will be called during init and for every transaction
Invoke(stub *ChaincodeStub, function string, args []string) (error)
// Query is to be used for read-only access to chaincode state
Query(stub *ChaincodeStub, function string, args []string) ([]byte, error)
}
```
This is a disruptive change, but the longer we wait, the harder it will be to make these types of changes. Please provide any thoughts and comments. | 1.0 | Chaincode - SIGNIFICANT API CHANGE - Run -> Invoke - Today, the chaincode interface defines two functions.
```
// Chaincode is the standard chaincode callback interface that the chaincode developer needs to implement.
type Chaincode interface {
// Run method will be called during init and for every transaction
Run(stub *ChaincodeStub, function string, args []string) ([]byte, error)
// Query is to be used for read-only access to chaincode state
Query(stub *ChaincodeStub, function string, args []string) ([]byte, error)
}
```
There are two items we would like to change.
1. Documentation, the CLI, and the REST API use the term `Invoke` instead of `Run`. Therefore, we would like to rename the `Run` function to `Invoke`.
2. The existing `Run` function returns a `[]byte` which is mostly unused and causes confusion. We would like to remove this from the return value.
The new Chaincode interface will be
```
// Chaincode is the standard chaincode callback interface that the chaincode developer needs to implement.
type Chaincode interface {
// Invoke method will be called during init and for every transaction
Invoke(stub *ChaincodeStub, function string, args []string) (error)
// Query is to be used for read-only access to chaincode state
Query(stub *ChaincodeStub, function string, args []string) ([]byte, error)
}
```
This is a disruptive change, but the longer we wait, the harder it will be to make these types of changes. Please provide any thoughts and comments. | non_priority | chaincode significant api change run invoke today the chaincode interface defines two functions chaincode is the standard chaincode callback interface that the chaincode developer needs to implement type chaincode interface run method will be called during init and for every transaction run stub chaincodestub function string args string byte error query is to be used for read only access to chaincode state query stub chaincodestub function string args string byte error there are two items we would like to change documentation the cli and the rest api use the term invoke instead of run therefore we would like to rename the run function to invoke the existing run function returns a byte which is mostly unused and causes confusion we would like to remove this from the return value the new chaincode interface will be chaincode is the standard chaincode callback interface that the chaincode developer needs to implement type chaincode interface invoke method will be called during init and for every transaction invoke stub chaincodestub function string args string error query is to be used for read only access to chaincode state query stub chaincodestub function string args string byte error this is a disruptive change but the longer we wait the harder it will be to make these types of changes please provide any thoughts and comments | 0 |
22,551 | 3,669,067,881 | IssuesEvent | 2016-02-21 00:29:49 | ironjan/klausurtool-ror | https://api.github.com/repos/ironjan/klausurtool-ror | closed | Internal server error when opening returning_form without parameters | defect help wanted | 1. Got to http://0.0.0.0:3000/ausleihe/returning_form
2. No parameters given, error page:
```
undefined method `map' for nil:NilClass Did you mean? tap
Extracted source (around line #146):
def returning_form
instances = params[:old_folder_instances]
.map { |id| OldFolderInstance.find_by_id(id) }
found_instances = instances.compact
if found_instances.count < instances.count
```
May also be the case for ```lending_form``` | 1.0 | Internal server error when opening returning_form without parameters - 1. Got to http://0.0.0.0:3000/ausleihe/returning_form
2. No parameters given, error page:
```
undefined method `map' for nil:NilClass Did you mean? tap
Extracted source (around line #146):
def returning_form
instances = params[:old_folder_instances]
.map { |id| OldFolderInstance.find_by_id(id) }
found_instances = instances.compact
if found_instances.count < instances.count
```
May also be the case for ```lending_form``` | non_priority | internal server error when opening returning form without parameters got to no parameters given error page undefined method map for nil nilclass did you mean tap extracted source around line def returning form instances params map id oldfolderinstance find by id id found instances instances compact if found instances count instances count may also be the case for lending form | 0 |
22,349 | 10,742,361,326 | IssuesEvent | 2019-10-29 22:22:40 | istio/istio.io | https://api.github.com/repos/istio/istio.io | opened | Need deprecation notice for RBAC policy | area/security | Release note draft claims
> Added the new Authorization Policy that deprecates the RBAC policy for access control in Istio.
We will need a deprecation announcement for this change | True | Need deprecation notice for RBAC policy - Release note draft claims
> Added the new Authorization Policy that deprecates the RBAC policy for access control in Istio.
We will need a deprecation announcement for this change | non_priority | need deprecation notice for rbac policy release note draft claims added the new authorization policy that deprecates the rbac policy for access control in istio we will need a deprecation announcement for this change | 0 |
202,891 | 15,306,250,670 | IssuesEvent | 2021-02-24 19:12:58 | zeek/spicy | https://api.github.com/repos/zeek/spicy | opened | Dockerfiles should not be setting ZEEK_PLUGIN_PATH | Testing / CI / Release | Doing so prevents other plugins from working that get installed through zkg.
It also shouldn't be necessary because the Spicy plugin installs itself into the right place. I just tried it with Ubuntu 20 and it works just fine without that environment variable.
| 1.0 | Dockerfiles should not be setting ZEEK_PLUGIN_PATH - Doing so prevents other plugins from working that get installed through zkg.
It also shouldn't be necessary because the Spicy plugin installs itself into the right place. I just tried it with Ubuntu 20 and it works just fine without that environment variable.
| non_priority | dockerfiles should not be setting zeek plugin path doing so prevents other plugins from working that get installed through zkg it also shouldn t be necessary because the spicy plugin installs itself into the right place i just tried it with ubuntu and it works just fine without that environment variable | 0 |
194,264 | 22,261,924,993 | IssuesEvent | 2022-06-10 01:51:42 | artsking/linux-4.19.72 | https://api.github.com/repos/artsking/linux-4.19.72 | reopened | CVE-2020-36386 (High) detected in linux-yoctov5.4.51 | security vulnerability | ## CVE-2020-36386 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yoctov5.4.51</b></p></summary>
<p>
<p>Yocto Linux Embedded kernel</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto>https://git.yoctoproject.org/git/linux-yocto</a></p>
<p>Found in HEAD commit: <a href="https://github.com/artsking/linux-4.19.72/commit/8519fe4185f1a7567a708f01b476f195b0f1046c">8519fe4185f1a7567a708f01b476f195b0f1046c</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>/net/bluetooth/hci_event.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>
An issue was discovered in the Linux kernel before 5.8.1. net/bluetooth/hci_event.c has a slab out-of-bounds read in hci_extended_inquiry_result_evt, aka CID-51c19bf3d5cf.
<p>Publish Date: 2021-06-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36386>CVE-2020-36386</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.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2020-36386">https://www.linuxkernelcves.com/cves/CVE-2020-36386</a></p>
<p>Release Date: 2021-06-07</p>
<p>Fix Resolution: v4.4.233, v4.9.233, v4.14.194, v4.19.139, v5.4.58, v5.7.15, v5.8.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 | CVE-2020-36386 (High) detected in linux-yoctov5.4.51 - ## CVE-2020-36386 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yoctov5.4.51</b></p></summary>
<p>
<p>Yocto Linux Embedded kernel</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto>https://git.yoctoproject.org/git/linux-yocto</a></p>
<p>Found in HEAD commit: <a href="https://github.com/artsking/linux-4.19.72/commit/8519fe4185f1a7567a708f01b476f195b0f1046c">8519fe4185f1a7567a708f01b476f195b0f1046c</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>/net/bluetooth/hci_event.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>
An issue was discovered in the Linux kernel before 5.8.1. net/bluetooth/hci_event.c has a slab out-of-bounds read in hci_extended_inquiry_result_evt, aka CID-51c19bf3d5cf.
<p>Publish Date: 2021-06-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36386>CVE-2020-36386</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.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2020-36386">https://www.linuxkernelcves.com/cves/CVE-2020-36386</a></p>
<p>Release Date: 2021-06-07</p>
<p>Fix Resolution: v4.4.233, v4.9.233, v4.14.194, v4.19.139, v5.4.58, v5.7.15, v5.8.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 | cve high detected in linux cve high severity vulnerability vulnerable library linux yocto linux embedded kernel library home page a href found in head commit a href found in base branch master vulnerable source files net bluetooth hci event c vulnerability details an issue was discovered in the linux kernel before net bluetooth hci event c has a slab out of bounds read in hci extended inquiry result evt aka cid publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
280,040 | 24,276,679,550 | IssuesEvent | 2022-09-28 14:19:13 | OpenLiberty/openliberty.io | https://api.github.com/repos/OpenLiberty/openliberty.io | closed | additional tests need for starter | test | Now we have an option to select
1. any MicroProfile Version when Java EE/Jakarta EE Version is selected as None
2. any Java EE/Jakarta EE Version when MicroProfile Version is selected as None
We'll need to add the following tests for starter to testOLStarterAllGradle.js & testOLStarterAllMaven.js:
Jakarta None - MP 4.1, 3.3, 2.2, 1.4
MicroProfile None - JKT 8.0, 7.0 | 1.0 | additional tests need for starter - Now we have an option to select
1. any MicroProfile Version when Java EE/Jakarta EE Version is selected as None
2. any Java EE/Jakarta EE Version when MicroProfile Version is selected as None
We'll need to add the following tests for starter to testOLStarterAllGradle.js & testOLStarterAllMaven.js:
Jakarta None - MP 4.1, 3.3, 2.2, 1.4
MicroProfile None - JKT 8.0, 7.0 | non_priority | additional tests need for starter now we have an option to select any microprofile version when java ee jakarta ee version is selected as none any java ee jakarta ee version when microprofile version is selected as none we ll need to add the following tests for starter to testolstarterallgradle js testolstarterallmaven js jakarta none mp microprofile none jkt | 0 |
32,127 | 8,797,871,443 | IssuesEvent | 2018-12-24 01:55:09 | DestinyItemManager/DIM | https://api.github.com/repos/DestinyItemManager/DIM | closed | Unable to search for a perk | Bug Feature: D2 Feature: Loadout Builder | In `D2 Loadout Builder` users are unable to actually type in the input box, even the placeholder text is absent. | 1.0 | Unable to search for a perk - In `D2 Loadout Builder` users are unable to actually type in the input box, even the placeholder text is absent. | non_priority | unable to search for a perk in loadout builder users are unable to actually type in the input box even the placeholder text is absent | 0 |
9,140 | 12,734,379,580 | IssuesEvent | 2020-06-25 13:49:30 | ISISScientificComputing/autoreduce | https://api.github.com/repos/ISISScientificComputing/autoreduce | opened | script_out and mantid_log Variable Initialisation and Location | 👤 Developer Requirement 🔑 Reduction | Issue raised by: developer
### What?
Move processes setting log location and the initialisation of script_out and mantid_log variables into sub-method.
### Where?
* queue_processors/autoreduction_processor/post_process_admin.py
* Lines to place in method: 206 - 209
### How?
A need to refactor the reduce method. This task has been broke down into many smaller tasks to make more manageable, decreasing the likelihood of breaking anything significantly.
## Additional Notes
Creation of sub-methods within reduce() should be done with extreme caution as it is hard to add unit tests at this stage.
### How to test the issue is resolved
This will be hard to test until methods are eventually moved outside of reduce().
* Code review
* Ensure System tests pass
| 1.0 | script_out and mantid_log Variable Initialisation and Location - Issue raised by: developer
### What?
Move processes setting log location and the initialisation of script_out and mantid_log variables into sub-method.
### Where?
* queue_processors/autoreduction_processor/post_process_admin.py
* Lines to place in method: 206 - 209
### How?
A need to refactor the reduce method. This task has been broke down into many smaller tasks to make more manageable, decreasing the likelihood of breaking anything significantly.
## Additional Notes
Creation of sub-methods within reduce() should be done with extreme caution as it is hard to add unit tests at this stage.
### How to test the issue is resolved
This will be hard to test until methods are eventually moved outside of reduce().
* Code review
* Ensure System tests pass
| non_priority | script out and mantid log variable initialisation and location issue raised by developer what move processes setting log location and the initialisation of script out and mantid log variables into sub method where queue processors autoreduction processor post process admin py lines to place in method how a need to refactor the reduce method this task has been broke down into many smaller tasks to make more manageable decreasing the likelihood of breaking anything significantly additional notes creation of sub methods within reduce should be done with extreme caution as it is hard to add unit tests at this stage how to test the issue is resolved this will be hard to test until methods are eventually moved outside of reduce code review ensure system tests pass | 0 |
213,144 | 16,511,871,031 | IssuesEvent | 2021-05-26 05:47:49 | dominikbraun/timetrace | https://api.github.com/repos/dominikbraun/timetrace | closed | Introduce "latest" or "last" alias for `edit record` command | documentation enhancement | Since the editing of records will probably often used for the last stopped record, I would propose to introduce an alias in a similar way as #30 for `edit record` .
If you like the idea @dominikbraun , you can assign me this issue :) | 1.0 | Introduce "latest" or "last" alias for `edit record` command - Since the editing of records will probably often used for the last stopped record, I would propose to introduce an alias in a similar way as #30 for `edit record` .
If you like the idea @dominikbraun , you can assign me this issue :) | non_priority | introduce latest or last alias for edit record command since the editing of records will probably often used for the last stopped record i would propose to introduce an alias in a similar way as for edit record if you like the idea dominikbraun you can assign me this issue | 0 |
308,142 | 23,234,201,050 | IssuesEvent | 2022-08-03 10:15:26 | wmo-im/wcmp2 | https://api.github.com/repos/wmo-im/wcmp2 | closed | add GitHub Action to build standard docx and pdf in gh-pages branch | documentation enhancement | We need a GitHub Action to build the pdf and docx representations on every push to the repository in `standard/**`
The resulting files should be in:
- https://wmo-im.github.io/wcmp2/standard/wcmp2-DRAFT.html
- https://wmo-im.github.io/wcmp2/standard/wcmp2-DRAFT.docx
- https://wmo-im.github.io/wcmp2/standard/wcmp2-DRAFT.pdf
cc @amilan17 | 1.0 | add GitHub Action to build standard docx and pdf in gh-pages branch - We need a GitHub Action to build the pdf and docx representations on every push to the repository in `standard/**`
The resulting files should be in:
- https://wmo-im.github.io/wcmp2/standard/wcmp2-DRAFT.html
- https://wmo-im.github.io/wcmp2/standard/wcmp2-DRAFT.docx
- https://wmo-im.github.io/wcmp2/standard/wcmp2-DRAFT.pdf
cc @amilan17 | non_priority | add github action to build standard docx and pdf in gh pages branch we need a github action to build the pdf and docx representations on every push to the repository in standard the resulting files should be in cc | 0 |
188,490 | 14,446,207,422 | IssuesEvent | 2020-12-08 00:42:13 | actool/eslint-plugin-actool | https://api.github.com/repos/actool/eslint-plugin-actool | closed | Add test coverage for rules | enhancement test | <!-- ✨ Thanks for feature suggesting! ➡️ Please don't ignore this template -->
## Related
<!-- Specify related rule / util / ... -->
- max-tags
- relevant-comments
## Description
<!--
Describe related problem / note, if you have
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
-->
## Solution
<!--
(optional) Describe desired solution
A clear and concise description of what you want to happen.
-->
## Additional context
<!--
(optional) Add any other context or screenshots
about the feature request here, maybe - alternatives you've considered.
-->
| 1.0 | Add test coverage for rules - <!-- ✨ Thanks for feature suggesting! ➡️ Please don't ignore this template -->
## Related
<!-- Specify related rule / util / ... -->
- max-tags
- relevant-comments
## Description
<!--
Describe related problem / note, if you have
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
-->
## Solution
<!--
(optional) Describe desired solution
A clear and concise description of what you want to happen.
-->
## Additional context
<!--
(optional) Add any other context or screenshots
about the feature request here, maybe - alternatives you've considered.
-->
| non_priority | add test coverage for rules related max tags relevant comments description describe related problem note if you have a clear and concise description of what the problem is ex i m always frustrated when solution optional describe desired solution a clear and concise description of what you want to happen additional context optional add any other context or screenshots about the feature request here maybe alternatives you ve considered | 0 |
31,781 | 13,632,099,523 | IssuesEvent | 2020-09-24 19:04:51 | wellcomecollection/platform | https://api.github.com/repos/wellcomecollection/platform | opened | If the bag tracker isn't available, the bag indexer drops the message | 🐛 Bug 📦 Storage service | Spotted in debugging https://github.com/wellcomecollection/platform/issues/4765
The bag indexer dropped several thousand messages tonight, all with a similar error:
> 18:59:54.357 [main-actor-system-akka.actor.default-dispatcher-6] ERROR u.a.w.p.a.i.e.IndexerWorker$$anon$1 - DeterministicFailure(akka.stream.StreamTcpException: Tcp command [Connect(storage-prod-bags-api.storage-prod:8080,None,List(),Some(10 seconds),true)] failed because of java.net.UnknownHostException: storage-prod-bags-api.storage-prod,None)
The bags API tasks all restarted earlier this evening, with at least one showing the error:
> java.lang.OutOfMemoryError: Java heap space
I suspect this was caused when the bag indexer tried to retrieve Chemist & Druggist.
The bag indexer shouldn't treat these errors as deterministic – it should return the message to the queue, and let it be retried. In most cases, the bag affected will be one that happened to arrive just after C&D, not C&D itself. | 1.0 | If the bag tracker isn't available, the bag indexer drops the message - Spotted in debugging https://github.com/wellcomecollection/platform/issues/4765
The bag indexer dropped several thousand messages tonight, all with a similar error:
> 18:59:54.357 [main-actor-system-akka.actor.default-dispatcher-6] ERROR u.a.w.p.a.i.e.IndexerWorker$$anon$1 - DeterministicFailure(akka.stream.StreamTcpException: Tcp command [Connect(storage-prod-bags-api.storage-prod:8080,None,List(),Some(10 seconds),true)] failed because of java.net.UnknownHostException: storage-prod-bags-api.storage-prod,None)
The bags API tasks all restarted earlier this evening, with at least one showing the error:
> java.lang.OutOfMemoryError: Java heap space
I suspect this was caused when the bag indexer tried to retrieve Chemist & Druggist.
The bag indexer shouldn't treat these errors as deterministic – it should return the message to the queue, and let it be retried. In most cases, the bag affected will be one that happened to arrive just after C&D, not C&D itself. | non_priority | if the bag tracker isn t available the bag indexer drops the message spotted in debugging the bag indexer dropped several thousand messages tonight all with a similar error error u a w p a i e indexerworker anon deterministicfailure akka stream streamtcpexception tcp command failed because of java net unknownhostexception storage prod bags api storage prod none the bags api tasks all restarted earlier this evening with at least one showing the error java lang outofmemoryerror java heap space i suspect this was caused when the bag indexer tried to retrieve chemist druggist the bag indexer shouldn t treat these errors as deterministic – it should return the message to the queue and let it be retried in most cases the bag affected will be one that happened to arrive just after c d not c d itself | 0 |
32,784 | 8,952,335,966 | IssuesEvent | 2019-01-25 16:16:22 | svigerske/ipopt-donotuse | https://api.github.com/repos/svigerske/ipopt-donotuse | closed | error: application could not be initialized correctly (0xc0000005) | Compilation Building mingw Ipopt defect | Issue created by migration from Trac.
Original creator: jens.schubert
Original creation time: 2010-05-04 06:14:20
Assignee: ipopt-team
Version: 3.8
CC: jens.schubert.1@googlemail.com
Dear all,
I am new with Ipopt, so i am not sure whether this is the right place to post my question. Please point me to the right place in case I should have asked else where.
To use and test ipopt I installed mingw (gcc4.5.0) and msys under windows vista. I could compile some other software. However, I have problems to get ipopt running.
I use Ipopt version 3.8.1 ( Ialso tried version 3.8.0).
I did a configure, make, and make test - but the test failed with the following error messages (4 times, i.e. one error message for each of the 4 tests):
Die Anwendung konnte nicht richtig initialisiert werden (0xc0000005). Klicken Sie auf "OK", um die Anwendung zu beenden.
[Translation: The application could not be initialized correctly (0xc0000005). Click "OK"-Button to end the application.]
Configure and make seems to run fine (as far as I can see from the output). I tried various things but I always get this error message for each of the examples.
What am I doing wrong?
Which info do you need to help me?
Thanks for any help in advance,
Jens | 1.0 | error: application could not be initialized correctly (0xc0000005) - Issue created by migration from Trac.
Original creator: jens.schubert
Original creation time: 2010-05-04 06:14:20
Assignee: ipopt-team
Version: 3.8
CC: jens.schubert.1@googlemail.com
Dear all,
I am new with Ipopt, so i am not sure whether this is the right place to post my question. Please point me to the right place in case I should have asked else where.
To use and test ipopt I installed mingw (gcc4.5.0) and msys under windows vista. I could compile some other software. However, I have problems to get ipopt running.
I use Ipopt version 3.8.1 ( Ialso tried version 3.8.0).
I did a configure, make, and make test - but the test failed with the following error messages (4 times, i.e. one error message for each of the 4 tests):
Die Anwendung konnte nicht richtig initialisiert werden (0xc0000005). Klicken Sie auf "OK", um die Anwendung zu beenden.
[Translation: The application could not be initialized correctly (0xc0000005). Click "OK"-Button to end the application.]
Configure and make seems to run fine (as far as I can see from the output). I tried various things but I always get this error message for each of the examples.
What am I doing wrong?
Which info do you need to help me?
Thanks for any help in advance,
Jens | non_priority | error application could not be initialized correctly issue created by migration from trac original creator jens schubert original creation time assignee ipopt team version cc jens schubert googlemail com dear all i am new with ipopt so i am not sure whether this is the right place to post my question please point me to the right place in case i should have asked else where to use and test ipopt i installed mingw and msys under windows vista i could compile some other software however i have problems to get ipopt running i use ipopt version ialso tried version i did a configure make and make test but the test failed with the following error messages times i e one error message for each of the tests die anwendung konnte nicht richtig initialisiert werden klicken sie auf ok um die anwendung zu beenden configure and make seems to run fine as far as i can see from the output i tried various things but i always get this error message for each of the examples what am i doing wrong which info do you need to help me thanks for any help in advance jens | 0 |
1,603 | 2,612,158,168 | IssuesEvent | 2015-02-27 12:19:13 | saltstack/salt | https://api.github.com/repos/saltstack/salt | closed | wrong file state link in ref/states/all/index.html | Documentation | Link on page http://salt.readthedocs.org/en/latest/ref/states/all/index.html for file state is pointing to python library documentation.
Should point to http://docs.saltstack.com/en/latest/ref/states/all/salt.states.file.html
In repository (230d64e) everything looks fine.
| 1.0 | wrong file state link in ref/states/all/index.html - Link on page http://salt.readthedocs.org/en/latest/ref/states/all/index.html for file state is pointing to python library documentation.
Should point to http://docs.saltstack.com/en/latest/ref/states/all/salt.states.file.html
In repository (230d64e) everything looks fine.
| non_priority | wrong file state link in ref states all index html link on page for file state is pointing to python library documentation should point to in repository everything looks fine | 0 |
6,108 | 4,155,293,816 | IssuesEvent | 2016-06-16 14:31:52 | sixeco/ProjectAlbatross | https://api.github.com/repos/sixeco/ProjectAlbatross | opened | Testkollektion aufbauen | usability user story | Als Usabiltiy - Fachmann möchte ich eine Testkollektion aufzubauen, um meine Suche systemzentriert an einem Testsystem evaluieren zu können. | True | Testkollektion aufbauen - Als Usabiltiy - Fachmann möchte ich eine Testkollektion aufzubauen, um meine Suche systemzentriert an einem Testsystem evaluieren zu können. | non_priority | testkollektion aufbauen als usabiltiy fachmann möchte ich eine testkollektion aufzubauen um meine suche systemzentriert an einem testsystem evaluieren zu können | 0 |
200,801 | 15,158,163,643 | IssuesEvent | 2021-02-12 00:28:50 | ESMCI/cime | https://api.github.com/repos/ESMCI/cime | closed | CIME issue with extra files that have ".nc" in the names during phase BASELINE | unit tests | Use a temp SCORPIO feature branch to reproduce this issue with a simple
E3SM test. The feature branch creates dummy "****.nc.xx" files in the test
run directory for testing.
Steps on a machine supported by E3SM:
```
git clone https://github.com/E3SM-Project/E3SM.git
cd E3SM
git submodule update --init
cd externals/scorpio
git checkout dqwu/create_dummy_files
cd ../../cime/scripts
./create_test SMS.f09_g16_a.IGELM_MLI -b master --baseline-root=specified_baseline_directory --compare
```
TestStatus.log has some messages like below:
```
File '****.mali.hist.am.0001-01-01_00000.nc.xx' had no compare counterpart in 'specified_baseline_directory/SMS.f09_g16_a.IGELM_MLI.<machine>_<compiler>' with suffix ''
File 'mali.hist.am.0001-01-01_00000.nc.base' had no original counterpart in 'specified_test_run_directory' with suffix ''
``` | 1.0 | CIME issue with extra files that have ".nc" in the names during phase BASELINE - Use a temp SCORPIO feature branch to reproduce this issue with a simple
E3SM test. The feature branch creates dummy "****.nc.xx" files in the test
run directory for testing.
Steps on a machine supported by E3SM:
```
git clone https://github.com/E3SM-Project/E3SM.git
cd E3SM
git submodule update --init
cd externals/scorpio
git checkout dqwu/create_dummy_files
cd ../../cime/scripts
./create_test SMS.f09_g16_a.IGELM_MLI -b master --baseline-root=specified_baseline_directory --compare
```
TestStatus.log has some messages like below:
```
File '****.mali.hist.am.0001-01-01_00000.nc.xx' had no compare counterpart in 'specified_baseline_directory/SMS.f09_g16_a.IGELM_MLI.<machine>_<compiler>' with suffix ''
File 'mali.hist.am.0001-01-01_00000.nc.base' had no original counterpart in 'specified_test_run_directory' with suffix ''
``` | non_priority | cime issue with extra files that have nc in the names during phase baseline use a temp scorpio feature branch to reproduce this issue with a simple test the feature branch creates dummy nc xx files in the test run directory for testing steps on a machine supported by git clone cd git submodule update init cd externals scorpio git checkout dqwu create dummy files cd cime scripts create test sms a igelm mli b master baseline root specified baseline directory compare teststatus log has some messages like below file mali hist am nc xx had no compare counterpart in specified baseline directory sms a igelm mli with suffix file mali hist am nc base had no original counterpart in specified test run directory with suffix | 0 |
186,293 | 14,394,659,967 | IssuesEvent | 2020-12-03 01:49:23 | github-vet/rangeclosure-findings | https://api.github.com/repos/github-vet/rangeclosure-findings | closed | bitleak/go-redis-pool: pool_test.go; 11 LoC | fresh small test |
Found a possible issue in [bitleak/go-redis-pool](https://www.github.com/bitleak/go-redis-pool) at [pool_test.go](https://github.com/bitleak/go-redis-pool/blob/bda28908d7017b20d869a5e6d07ba74f9f2efa91/pool_test.go#L467-L477)
The below snippet of Go code triggered static analysis which searches for goroutines and/or defer statements
which capture loop variables.
[Click here to see the code in its original context.](https://github.com/bitleak/go-redis-pool/blob/bda28908d7017b20d869a5e6d07ba74f9f2efa91/pool_test.go#L467-L477)
<details>
<summary>Click here to show the 11 line(s) of Go which triggered the analyzer.</summary>
```go
for _, pool := range pools {
go func() {
time.Sleep(100 * time.Millisecond)
pool.LPush(key, "e1", "e2")
}()
Expect(pool.BLPop(time.Second, key).Val()).To(Equal([]string{key, "e2"}))
Expect(pool.BLPop(time.Second, key).Val()).To(Equal([]string{key, "e1"}))
if pool == shardPool {
Expect(pool.BLPop(time.Second, key, noExistsKey).Err()).To(HaveOccurred())
}
}
```
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> range-loop variable pool used in defer or goroutine at line 470
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: bda28908d7017b20d869a5e6d07ba74f9f2efa91
| 1.0 | bitleak/go-redis-pool: pool_test.go; 11 LoC -
Found a possible issue in [bitleak/go-redis-pool](https://www.github.com/bitleak/go-redis-pool) at [pool_test.go](https://github.com/bitleak/go-redis-pool/blob/bda28908d7017b20d869a5e6d07ba74f9f2efa91/pool_test.go#L467-L477)
The below snippet of Go code triggered static analysis which searches for goroutines and/or defer statements
which capture loop variables.
[Click here to see the code in its original context.](https://github.com/bitleak/go-redis-pool/blob/bda28908d7017b20d869a5e6d07ba74f9f2efa91/pool_test.go#L467-L477)
<details>
<summary>Click here to show the 11 line(s) of Go which triggered the analyzer.</summary>
```go
for _, pool := range pools {
go func() {
time.Sleep(100 * time.Millisecond)
pool.LPush(key, "e1", "e2")
}()
Expect(pool.BLPop(time.Second, key).Val()).To(Equal([]string{key, "e2"}))
Expect(pool.BLPop(time.Second, key).Val()).To(Equal([]string{key, "e1"}))
if pool == shardPool {
Expect(pool.BLPop(time.Second, key, noExistsKey).Err()).To(HaveOccurred())
}
}
```
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> range-loop variable pool used in defer or goroutine at line 470
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: bda28908d7017b20d869a5e6d07ba74f9f2efa91
| non_priority | bitleak go redis pool pool test go loc found a possible issue in at the below snippet of go code triggered static analysis which searches for goroutines and or defer statements which capture loop variables click here to show the line s of go which triggered the analyzer go for pool range pools go func time sleep time millisecond pool lpush key expect pool blpop time second key val to equal string key expect pool blpop time second key val to equal string key if pool shardpool expect pool blpop time second key noexistskey err to haveoccurred below is the message reported by the analyzer for this snippet of code beware that the analyzer only reports the first issue it finds so please do not limit your consideration to the contents of the below message range loop variable pool used in defer or goroutine at line leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id | 0 |
160,808 | 20,118,881,605 | IssuesEvent | 2022-02-07 22:52:58 | TreyM-WSS/whitesource-demo-1 | https://api.github.com/repos/TreyM-WSS/whitesource-demo-1 | closed | CVE-2021-23343 (High) detected in path-parse-1.0.6.tgz - autoclosed | security vulnerability | ## CVE-2021-23343 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>path-parse-1.0.6.tgz</b></p></summary>
<p>Node.js path.parse() ponyfill</p>
<p>Library home page: <a href="https://registry.npmjs.org/path-parse/-/path-parse-1.0.6.tgz">https://registry.npmjs.org/path-parse/-/path-parse-1.0.6.tgz</a></p>
<p>
Dependency Hierarchy:
- rollup-plugin-node-resolve-5.2.0.tgz (Root Library)
- resolve-1.12.0.tgz
- :x: **path-parse-1.0.6.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/TreyM-WSS/whitesource-demo-1/commit/551e7e8a23ecb57fdb46f4d6702da4d7cff49f70">551e7e8a23ecb57fdb46f4d6702da4d7cff49f70</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
All versions of package path-parse are vulnerable to Regular Expression Denial of Service (ReDoS) via splitDeviceRe, splitTailRe, and splitPathRe regular expressions. ReDoS exhibits polynomial worst-case time complexity.
<p>Publish Date: 2021-05-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23343>CVE-2021-23343</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://github.com/jbgutierrez/path-parse/issues/8">https://github.com/jbgutierrez/path-parse/issues/8</a></p>
<p>Release Date: 2021-05-04</p>
<p>Fix Resolution: path-parse - 1.0.7</p>
</p>
</details>
<p></p>
| True | CVE-2021-23343 (High) detected in path-parse-1.0.6.tgz - autoclosed - ## CVE-2021-23343 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>path-parse-1.0.6.tgz</b></p></summary>
<p>Node.js path.parse() ponyfill</p>
<p>Library home page: <a href="https://registry.npmjs.org/path-parse/-/path-parse-1.0.6.tgz">https://registry.npmjs.org/path-parse/-/path-parse-1.0.6.tgz</a></p>
<p>
Dependency Hierarchy:
- rollup-plugin-node-resolve-5.2.0.tgz (Root Library)
- resolve-1.12.0.tgz
- :x: **path-parse-1.0.6.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/TreyM-WSS/whitesource-demo-1/commit/551e7e8a23ecb57fdb46f4d6702da4d7cff49f70">551e7e8a23ecb57fdb46f4d6702da4d7cff49f70</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
All versions of package path-parse are vulnerable to Regular Expression Denial of Service (ReDoS) via splitDeviceRe, splitTailRe, and splitPathRe regular expressions. ReDoS exhibits polynomial worst-case time complexity.
<p>Publish Date: 2021-05-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23343>CVE-2021-23343</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://github.com/jbgutierrez/path-parse/issues/8">https://github.com/jbgutierrez/path-parse/issues/8</a></p>
<p>Release Date: 2021-05-04</p>
<p>Fix Resolution: path-parse - 1.0.7</p>
</p>
</details>
<p></p>
| non_priority | cve high detected in path parse tgz autoclosed cve high severity vulnerability vulnerable library path parse tgz node js path parse ponyfill library home page a href dependency hierarchy rollup plugin node resolve tgz root library resolve tgz x path parse tgz vulnerable library found in head commit a href vulnerability details all versions of package path parse are vulnerable to regular expression denial of service redos via splitdevicere splittailre and splitpathre regular expressions redos exhibits polynomial worst case time complexity publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution path parse | 0 |
54,918 | 14,021,178,394 | IssuesEvent | 2020-10-29 20:51:19 | gitblit/gitblit | https://api.github.com/repos/gitblit/gitblit | closed | Gitblit ignores transport preference | Catg-Defect Status-CanNotReproduce | Steps to reproduce:
```
git.acceptedPushTransports = HTTP HTTPS SSH
git.sshBindInterface =
git.sshPort = 29418
git.daemonBindInterface = localhost
git.daemonPort = 9418
```
Set your transport preference to `HTTP` (default).
Now navigate to a repo and it will offer the ssh:// URL by default.
Gitblit 1.8.0.
| 1.0 | Gitblit ignores transport preference - Steps to reproduce:
```
git.acceptedPushTransports = HTTP HTTPS SSH
git.sshBindInterface =
git.sshPort = 29418
git.daemonBindInterface = localhost
git.daemonPort = 9418
```
Set your transport preference to `HTTP` (default).
Now navigate to a repo and it will offer the ssh:// URL by default.
Gitblit 1.8.0.
| non_priority | gitblit ignores transport preference steps to reproduce git acceptedpushtransports http https ssh git sshbindinterface git sshport git daemonbindinterface localhost git daemonport set your transport preference to http default now navigate to a repo and it will offer the ssh url by default gitblit | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.