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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
328,197 | 24,174,100,916 | IssuesEvent | 2022-09-22 22:28:12 | tacosontitan/Mauve | https://api.github.com/repos/tacosontitan/Mauve | opened | Add documentation for WithinRange to the Wiki | documentation help wanted good first issue | The wiki needs documentation for WithinRange usage. | 1.0 | Add documentation for WithinRange to the Wiki - The wiki needs documentation for WithinRange usage. | non_priority | add documentation for withinrange to the wiki the wiki needs documentation for withinrange usage | 0 |
48,779 | 13,398,619,189 | IssuesEvent | 2020-09-03 13:25:12 | mixellent/demo-app | https://api.github.com/repos/mixellent/demo-app | opened | CVE-2017-5647 (High) detected in tomcat-embed-core-8.5.4.jar | security vulnerability | ## CVE-2017-5647 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tomcat-embed-core-8.5.4.jar</b></p></summary>
<p>Core Tomcat implementation</p>
<p>Library home page: <a href="http://tomcat.apache.org/">http://tomcat.apache.org/</a></p>
<p>Path to dependency file: /tmp/ws-scm/demo-app/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.4/tomcat-embed-core-8.5.4.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-1.4.0.RELEASE.jar (Root Library)
- spring-boot-starter-tomcat-1.4.0.RELEASE.jar
- :x: **tomcat-embed-core-8.5.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/mixellent/demo-app/commit/e224ec4297971467bc3e91a705b785158ac67da0">e224ec4297971467bc3e91a705b785158ac67da0</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 bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12, 8.0.0.RC1 to 8.0.42, 7.0.0 to 7.0.76, and 6.0.0 to 6.0.52, when send file was used, results in the pipelined request being lost when send file processing of the previous request completed. This could result in responses appearing to be sent for the wrong request. For example, a user agent that sent requests A, B and C could see the correct response for request A, the response for request C for request B and no response for request C.
<p>Publish Date: 2017-04-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-5647>CVE-2017-5647</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5647">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5647</a></p>
<p>Release Date: 2017-04-17</p>
<p>Fix Resolution: org.apache.tomcat.embed:tomcat-embed-core:9.0.0.M19,8.5.13,8.0.43,7.0.77,org.apache.tomcat:tomcat-coyote:9.0.0.M19,8.5.13,8.0.43,7.0.77,org.apache.tomcat:coyote:6.0.53</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.apache.tomcat.embed","packageName":"tomcat-embed-core","packageVersion":"8.5.4","isTransitiveDependency":true,"dependencyTree":"org.springframework.boot:spring-boot-starter-web:1.4.0.RELEASE;org.springframework.boot:spring-boot-starter-tomcat:1.4.0.RELEASE;org.apache.tomcat.embed:tomcat-embed-core:8.5.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.apache.tomcat.embed:tomcat-embed-core:9.0.0.M19,8.5.13,8.0.43,7.0.77,org.apache.tomcat:tomcat-coyote:9.0.0.M19,8.5.13,8.0.43,7.0.77,org.apache.tomcat:coyote:6.0.53"}],"vulnerabilityIdentifier":"CVE-2017-5647","vulnerabilityDetails":"A bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12, 8.0.0.RC1 to 8.0.42, 7.0.0 to 7.0.76, and 6.0.0 to 6.0.52, when send file was used, results in the pipelined request being lost when send file processing of the previous request completed. This could result in responses appearing to be sent for the wrong request. For example, a user agent that sent requests A, B and C could see the correct response for request A, the response for request C for request B and no response for request C.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-5647","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2017-5647 (High) detected in tomcat-embed-core-8.5.4.jar - ## CVE-2017-5647 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tomcat-embed-core-8.5.4.jar</b></p></summary>
<p>Core Tomcat implementation</p>
<p>Library home page: <a href="http://tomcat.apache.org/">http://tomcat.apache.org/</a></p>
<p>Path to dependency file: /tmp/ws-scm/demo-app/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/8.5.4/tomcat-embed-core-8.5.4.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-1.4.0.RELEASE.jar (Root Library)
- spring-boot-starter-tomcat-1.4.0.RELEASE.jar
- :x: **tomcat-embed-core-8.5.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/mixellent/demo-app/commit/e224ec4297971467bc3e91a705b785158ac67da0">e224ec4297971467bc3e91a705b785158ac67da0</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 bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12, 8.0.0.RC1 to 8.0.42, 7.0.0 to 7.0.76, and 6.0.0 to 6.0.52, when send file was used, results in the pipelined request being lost when send file processing of the previous request completed. This could result in responses appearing to be sent for the wrong request. For example, a user agent that sent requests A, B and C could see the correct response for request A, the response for request C for request B and no response for request C.
<p>Publish Date: 2017-04-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-5647>CVE-2017-5647</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5647">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5647</a></p>
<p>Release Date: 2017-04-17</p>
<p>Fix Resolution: org.apache.tomcat.embed:tomcat-embed-core:9.0.0.M19,8.5.13,8.0.43,7.0.77,org.apache.tomcat:tomcat-coyote:9.0.0.M19,8.5.13,8.0.43,7.0.77,org.apache.tomcat:coyote:6.0.53</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.apache.tomcat.embed","packageName":"tomcat-embed-core","packageVersion":"8.5.4","isTransitiveDependency":true,"dependencyTree":"org.springframework.boot:spring-boot-starter-web:1.4.0.RELEASE;org.springframework.boot:spring-boot-starter-tomcat:1.4.0.RELEASE;org.apache.tomcat.embed:tomcat-embed-core:8.5.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.apache.tomcat.embed:tomcat-embed-core:9.0.0.M19,8.5.13,8.0.43,7.0.77,org.apache.tomcat:tomcat-coyote:9.0.0.M19,8.5.13,8.0.43,7.0.77,org.apache.tomcat:coyote:6.0.53"}],"vulnerabilityIdentifier":"CVE-2017-5647","vulnerabilityDetails":"A bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12, 8.0.0.RC1 to 8.0.42, 7.0.0 to 7.0.76, and 6.0.0 to 6.0.52, when send file was used, results in the pipelined request being lost when send file processing of the previous request completed. This could result in responses appearing to be sent for the wrong request. For example, a user agent that sent requests A, B and C could see the correct response for request A, the response for request C for request B and no response for request C.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-5647","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in tomcat embed core jar cve high severity vulnerability vulnerable library tomcat embed core jar core tomcat implementation library home page a href path to dependency file tmp ws scm demo app pom xml path to vulnerable library home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar dependency hierarchy spring boot starter web release jar root library spring boot starter tomcat release jar x tomcat embed core jar vulnerable library found in head commit a href vulnerability details a bug in the handling of the pipelined requests in apache tomcat to to to to and to when send file was used results in the pipelined request being lost when send file processing of the previous request completed this could result in responses appearing to be sent for the wrong request for example a user agent that sent requests a b and c could see the correct response for request a the response for request c for request b and no response for request c publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache tomcat embed tomcat embed core org apache tomcat tomcat coyote org apache tomcat coyote isopenpronvulnerability true ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails a bug in the handling of the pipelined requests in apache tomcat to to to to and to when send file was used results in the pipelined request being lost when send file processing of the previous request completed this could result in responses appearing to be sent for the wrong request for example a user agent that sent requests a b and c could see the correct response for request a the response for request c for request b and no response for request c vulnerabilityurl | 0 |
198,107 | 15,700,912,622 | IssuesEvent | 2021-03-26 10:28:36 | root-project/root | https://api.github.com/repos/root-project/root | opened | Documentation for the syntax of LinkDef files is missing | bug in:Documentation | - [X] Checked for duplicates
<!--
Please search in
* [GitHub](https://github.com/root-project/root/issues?q=is%3Aissue)
* AND [Jira](https://sft.its.cern.ch/jira/issues/?jql=project %3D ROOT)
for existing reports of your issue.
If you find one, you are very welcome to add to the existing report, for instance "issue still exists in today's master".
-->
Hi, I looked for documentation about the exact syntax of LinkDef files, including the meaning of `+` and `-`, the special pragmas that can be used there (e.g. `#pragma link off all globals;`), how globbing works exactly (I know you can use `ClassName::*` but I don't know what the grammar rules are or whether I can do more complex globbing, etc.) and what entities are supported (I know `#pragma link C++ class` and `#pragma link C++ namespace` are a thing, not sure about others).
Places where I looked include doxygen, `rootcling --help` and the manual. The manual has some information at https://root.cern/manual/interacting_with_shared_libraries/#selecting-dictionary-entries-linkdefh but
1. it is under "ROOT macros and shared libraries", which in principle does not have anything to do with I/O and dictionaries. A more appropriate place might be "Adding a class to ROOT"
2. it does not provide the information mentioned above | 1.0 | Documentation for the syntax of LinkDef files is missing - - [X] Checked for duplicates
<!--
Please search in
* [GitHub](https://github.com/root-project/root/issues?q=is%3Aissue)
* AND [Jira](https://sft.its.cern.ch/jira/issues/?jql=project %3D ROOT)
for existing reports of your issue.
If you find one, you are very welcome to add to the existing report, for instance "issue still exists in today's master".
-->
Hi, I looked for documentation about the exact syntax of LinkDef files, including the meaning of `+` and `-`, the special pragmas that can be used there (e.g. `#pragma link off all globals;`), how globbing works exactly (I know you can use `ClassName::*` but I don't know what the grammar rules are or whether I can do more complex globbing, etc.) and what entities are supported (I know `#pragma link C++ class` and `#pragma link C++ namespace` are a thing, not sure about others).
Places where I looked include doxygen, `rootcling --help` and the manual. The manual has some information at https://root.cern/manual/interacting_with_shared_libraries/#selecting-dictionary-entries-linkdefh but
1. it is under "ROOT macros and shared libraries", which in principle does not have anything to do with I/O and dictionaries. A more appropriate place might be "Adding a class to ROOT"
2. it does not provide the information mentioned above | non_priority | documentation for the syntax of linkdef files is missing checked for duplicates please search in and root for existing reports of your issue if you find one you are very welcome to add to the existing report for instance issue still exists in today s master hi i looked for documentation about the exact syntax of linkdef files including the meaning of and the special pragmas that can be used there e g pragma link off all globals how globbing works exactly i know you can use classname but i don t know what the grammar rules are or whether i can do more complex globbing etc and what entities are supported i know pragma link c class and pragma link c namespace are a thing not sure about others places where i looked include doxygen rootcling help and the manual the manual has some information at but it is under root macros and shared libraries which in principle does not have anything to do with i o and dictionaries a more appropriate place might be adding a class to root it does not provide the information mentioned above | 0 |
161,575 | 20,154,147,900 | IssuesEvent | 2022-02-09 15:03:21 | kapseliboi/OSMBuildings | https://api.github.com/repos/kapseliboi/OSMBuildings | opened | CVE-2020-28500 (Medium) detected in lodash-4.17.15.tgz | security vulnerability | ## CVE-2020-28500 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.17.15.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- documentation-5.5.0.tgz (Root Library)
- :x: **lodash-4.17.15.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kapseliboi/OSMBuildings/commit/dfd1435f55d83fa05bb3c8833d662571b61c72e8">dfd1435f55d83fa05bb3c8833d662571b61c72e8</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>
Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.
WhiteSource Note: After conducting further research, WhiteSource has determined that CVE-2020-28500 only affects environments with versions 4.0.0 to 4.17.20 of Lodash.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28500>CVE-2020-28500</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution (lodash): 4.17.21</p>
<p>Direct dependency fix Resolution (documentation): 6.0.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-28500 (Medium) detected in lodash-4.17.15.tgz - ## CVE-2020-28500 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.17.15.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- documentation-5.5.0.tgz (Root Library)
- :x: **lodash-4.17.15.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kapseliboi/OSMBuildings/commit/dfd1435f55d83fa05bb3c8833d662571b61c72e8">dfd1435f55d83fa05bb3c8833d662571b61c72e8</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>
Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.
WhiteSource Note: After conducting further research, WhiteSource has determined that CVE-2020-28500 only affects environments with versions 4.0.0 to 4.17.20 of Lodash.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28500>CVE-2020-28500</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28500</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution (lodash): 4.17.21</p>
<p>Direct dependency fix Resolution (documentation): 6.0.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 lodash tgz cve medium severity vulnerability vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file package json path to vulnerable library node modules lodash package json dependency hierarchy documentation tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details lodash versions prior to are vulnerable to regular expression denial of service redos via the tonumber trim and trimend functions whitesource note after conducting further research whitesource has determined that cve only affects environments with versions to of lodash publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash direct dependency fix resolution documentation step up your open source security game with whitesource | 0 |
81,545 | 7,785,501,485 | IssuesEvent | 2018-06-06 16:01:02 | semperfiwebdesign/all-in-one-seo-pack | https://api.github.com/repos/semperfiwebdesign/all-in-one-seo-pack | closed | Fatal error: Uncaught Error: [] operator in aioseop_class.php:4823 | Completed Testing | Fatal error when testing v2.7 of Pro:
Fatal error: Uncaught Error: [] operator not supported for strings in aioseop_class.php:4823
This is caused by the empty pair of brackets and is triggered when you disable Custom Post Type Settings. | 1.0 | Fatal error: Uncaught Error: [] operator in aioseop_class.php:4823 - Fatal error when testing v2.7 of Pro:
Fatal error: Uncaught Error: [] operator not supported for strings in aioseop_class.php:4823
This is caused by the empty pair of brackets and is triggered when you disable Custom Post Type Settings. | non_priority | fatal error uncaught error operator in aioseop class php fatal error when testing of pro fatal error uncaught error operator not supported for strings in aioseop class php this is caused by the empty pair of brackets and is triggered when you disable custom post type settings | 0 |
12,720 | 8,054,178,482 | IssuesEvent | 2018-08-02 03:37:33 | home-climate-control/dz | https://api.github.com/repos/home-climate-control/dz | opened | Replace XML master configuration with something more compact | configuration enhancement usability | Currently used XML configuration originated in year 2000 when XML was all the rage (and actually a novelty). It is now hopelessly obsolete.
Need to find a way to simplify it.
Candidates:
- JSON - simpler to implement, but still cryptic
- YAML - more difficult, but most end user friendly if done right | True | Replace XML master configuration with something more compact - Currently used XML configuration originated in year 2000 when XML was all the rage (and actually a novelty). It is now hopelessly obsolete.
Need to find a way to simplify it.
Candidates:
- JSON - simpler to implement, but still cryptic
- YAML - more difficult, but most end user friendly if done right | non_priority | replace xml master configuration with something more compact currently used xml configuration originated in year when xml was all the rage and actually a novelty it is now hopelessly obsolete need to find a way to simplify it candidates json simpler to implement but still cryptic yaml more difficult but most end user friendly if done right | 0 |
44,664 | 18,153,088,972 | IssuesEvent | 2021-09-26 15:59:55 | getferdi/ferdi | https://api.github.com/repos/getferdi/ferdi | closed | Slack "Sign in with Google" not working | bug service-specific | <!--
Please fill our form below, this way we can analyse and fix the problem as fast as possible.
Please keep in mind that any text inside "<!--" and "--\>" are comments from us and won't be
visible in your bug report, so please don't put any text in them.
-->
**Bug description:**
<!-- Add a clear and concise description of what the bug is -->
On a fresh install, trying to log into slack via "Sign in with Google" and it always goes back to the Sign in to XXXX page. Tried logging in with email, ended up on that same page again. Works in a browser.
**Steps to reproduce:**
<!-- Explain to us how we can reproduce your bug on our computer -->
1. Install the latest version
2. Add slack service
3. Try to login
4. See the Sign in to [workspace_name] page
**Expected behavior**
<!-- If applicable, add a description of what you expected to happen. -->
Expected it to sign me into slack.
**Screenshots**
<!-- If applicable, add screenshots to help explain your problem. -->
<!-- You can simply drag and drop any image file into the editor to add it to the report -->
**Environment:**
- Operating System: macOS Big Sur (ver 11.2.3)
- Ferdi Version: 5.5.0 (5.5.0.2116)
- Server: Using without an account
- Debug information:
Both Copy and Publish options aren't working
<!-- Please consider supporting Ferdi!
👉 https://github.com/sponsors/getferdi
👉 https://opencollective.com/getferdi/donate -->
| 1.0 | Slack "Sign in with Google" not working - <!--
Please fill our form below, this way we can analyse and fix the problem as fast as possible.
Please keep in mind that any text inside "<!--" and "--\>" are comments from us and won't be
visible in your bug report, so please don't put any text in them.
-->
**Bug description:**
<!-- Add a clear and concise description of what the bug is -->
On a fresh install, trying to log into slack via "Sign in with Google" and it always goes back to the Sign in to XXXX page. Tried logging in with email, ended up on that same page again. Works in a browser.
**Steps to reproduce:**
<!-- Explain to us how we can reproduce your bug on our computer -->
1. Install the latest version
2. Add slack service
3. Try to login
4. See the Sign in to [workspace_name] page
**Expected behavior**
<!-- If applicable, add a description of what you expected to happen. -->
Expected it to sign me into slack.
**Screenshots**
<!-- If applicable, add screenshots to help explain your problem. -->
<!-- You can simply drag and drop any image file into the editor to add it to the report -->
**Environment:**
- Operating System: macOS Big Sur (ver 11.2.3)
- Ferdi Version: 5.5.0 (5.5.0.2116)
- Server: Using without an account
- Debug information:
Both Copy and Publish options aren't working
<!-- Please consider supporting Ferdi!
👉 https://github.com/sponsors/getferdi
👉 https://opencollective.com/getferdi/donate -->
| non_priority | slack sign in with google not working please fill our form below this way we can analyse and fix the problem as fast as possible please keep in mind that any text inside are comments from us and won t be visible in your bug report so please don t put any text in them bug description on a fresh install trying to log into slack via sign in with google and it always goes back to the sign in to xxxx page tried logging in with email ended up on that same page again works in a browser steps to reproduce install the latest version add slack service try to login see the sign in to page expected behavior expected it to sign me into slack screenshots environment operating system macos big sur ver ferdi version server using without an account debug information both copy and publish options aren t working please consider supporting ferdi 👉 👉 | 0 |
90,667 | 11,424,803,538 | IssuesEvent | 2020-02-03 18:31:02 | flock-skate/Flock-app | https://api.github.com/repos/flock-skate/Flock-app | opened | Add the brand into the pattern library | design | This includes adding the colours and fonts, and styling the pattern library. | 1.0 | Add the brand into the pattern library - This includes adding the colours and fonts, and styling the pattern library. | non_priority | add the brand into the pattern library this includes adding the colours and fonts and styling the pattern library | 0 |
16,929 | 9,935,164,341 | IssuesEvent | 2019-07-02 15:54:54 | immersive-web/webxr | https://api.github.com/repos/immersive-web/webxr | closed | Required, optional, deferrable, and not-needed features | fixed by pending PR privacy-and-security | **[Disclaimer: This issue is one of several being filed to capture discussions that began either on #638, on #689, or at the most recent F2F]**
This one is sort a redux of a design exploration that @toji and I did many months back (see #433). At the time we were looking for a solution that would allow developers state at the time of session creation what features they absolutely need for it to be worth creating a session and which features would be really nice to have. The idea was to prevent users from having a session start only to have them be immediately told that the experience wouldn't work. Happily, this provided an opportunity for the User Agent to request user consent any of the features that the developer considered required.
I'm working on an updated concrete design proposal which shows how developers might communicate intent to use certain features yet, but in the process of putting it together, I have some questions for you all about what you'd like to see in response to that developer intent being communicated. For example:
1. Should developers be allowed to block session creation if particular "required" features are unsupported by the underlying platform?
2. If a "required" feature depends on user consent, should the User Agent prompt for consent at the time of session creation?
3. If a user does not consent to a "required" feature, should session creation be blocked?
4. If an "optional" feature depends on user consent, should the User Agent prompt for consent at the time of session creation?
| True | Required, optional, deferrable, and not-needed features - **[Disclaimer: This issue is one of several being filed to capture discussions that began either on #638, on #689, or at the most recent F2F]**
This one is sort a redux of a design exploration that @toji and I did many months back (see #433). At the time we were looking for a solution that would allow developers state at the time of session creation what features they absolutely need for it to be worth creating a session and which features would be really nice to have. The idea was to prevent users from having a session start only to have them be immediately told that the experience wouldn't work. Happily, this provided an opportunity for the User Agent to request user consent any of the features that the developer considered required.
I'm working on an updated concrete design proposal which shows how developers might communicate intent to use certain features yet, but in the process of putting it together, I have some questions for you all about what you'd like to see in response to that developer intent being communicated. For example:
1. Should developers be allowed to block session creation if particular "required" features are unsupported by the underlying platform?
2. If a "required" feature depends on user consent, should the User Agent prompt for consent at the time of session creation?
3. If a user does not consent to a "required" feature, should session creation be blocked?
4. If an "optional" feature depends on user consent, should the User Agent prompt for consent at the time of session creation?
| non_priority | required optional deferrable and not needed features this one is sort a redux of a design exploration that toji and i did many months back see at the time we were looking for a solution that would allow developers state at the time of session creation what features they absolutely need for it to be worth creating a session and which features would be really nice to have the idea was to prevent users from having a session start only to have them be immediately told that the experience wouldn t work happily this provided an opportunity for the user agent to request user consent any of the features that the developer considered required i m working on an updated concrete design proposal which shows how developers might communicate intent to use certain features yet but in the process of putting it together i have some questions for you all about what you d like to see in response to that developer intent being communicated for example should developers be allowed to block session creation if particular required features are unsupported by the underlying platform if a required feature depends on user consent should the user agent prompt for consent at the time of session creation if a user does not consent to a required feature should session creation be blocked if an optional feature depends on user consent should the user agent prompt for consent at the time of session creation | 0 |
321,037 | 23,836,768,862 | IssuesEvent | 2022-09-06 06:50:03 | Dargentinewulf/wolf-den-news | https://api.github.com/repos/Dargentinewulf/wolf-den-news | opened | Gaming for the evening | documentation enhancement | Research and programming for Games it's not hard to follow and or at all hard to learn. Just takes effort and some time's a bit of attitude, it goes hand in hand with work. The perks are the fun part not mainly the building on timed schedule. | 1.0 | Gaming for the evening - Research and programming for Games it's not hard to follow and or at all hard to learn. Just takes effort and some time's a bit of attitude, it goes hand in hand with work. The perks are the fun part not mainly the building on timed schedule. | non_priority | gaming for the evening research and programming for games it s not hard to follow and or at all hard to learn just takes effort and some time s a bit of attitude it goes hand in hand with work the perks are the fun part not mainly the building on timed schedule | 0 |
52,154 | 27,402,932,376 | IssuesEvent | 2023-03-01 03:02:30 | requests-cache/requests-cache | https://api.github.com/repos/requests-cache/requests-cache | closed | sqlite3.OperationalError: database is locked | bug performance | I recently ran into this error in version `0.9.8`, which I was able to produce pretty reliably with the following code (against the local `python -m http.server`):
```python
from requests_cache import CachedSession
from requests_cache.backends import SQLiteCache
from concurrent.futures import ThreadPoolExecutor, as_completed
backend = SQLiteCache(db_path="/tmp/wat.sqlite", fast_save=True)
session = CachedSession(expire_after=1, backend=backend)
def cache_get():
return session.get("http://127.0.0.1:8000")
futures = []
with ThreadPoolExecutor(max_workers=100) as e:
for i in range(10000):
future = e.submit(cache_get)
futures.append(future)
for future in as_completed(futures):
print(future.result())
```
This will yield one of two errors, either `sqlite3.OperationalError: database is locked`:
```python
Traceback (most recent call last):
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/session.py", line 212, in _resend
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/session.py", line 193, in _send_and_cache
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/backends/base.py", line 103, in save_response
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/backends/sqlite.py", line 268, in __setitem__
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/backends/sqlite.py", line 220, in __setitem__
sqlite3.OperationalError: database is locked
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/user/test.py", line 18, in <module>
File "/usr/lib/python3.10/concurrent/futures/_base.py", line 451, in result
File "/usr/lib/python3.10/concurrent/futures/_base.py", line 403, in __get_result
File "/usr/lib/python3.10/concurrent/futures/thread.py", line 58, in run
File "/home/user/test.py", line 9, in cache_get
File "/home/user/.local/lib/python3.10/site-packages/requests/sessions.py", line 600, in get
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/session.py", line 115, in request
File "/home/user/.local/lib/python3.10/site-packages/requests/sessions.py", line 587, in request
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/session.py", line 151, in send
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/session.py", line 214, in _resend
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/backends/base.py", line 176, in delete
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/backends/sqlite.py", line 247, in bulk_delete
sqlite3.OperationalError: database is locked
```
or `sqlite3.OperationalError: unable to open database file`:
```python
Traceback (most recent call last):
File "/home/user/test.py", line 18, in <module>
File "/usr/lib/python3.10/concurrent/futures/_base.py", line 451, in result
File "/usr/lib/python3.10/concurrent/futures/_base.py", line 403, in __get_result
File "/usr/lib/python3.10/concurrent/futures/thread.py", line 58, in run
File "/home/user/test.py", line 9, in cache_get
File "/home/user/.local/lib/python3.10/site-packages/requests/sessions.py", line 600, in get
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/session.py", line 115, in request
File "/home/user/.local/lib/python3.10/site-packages/requests/sessions.py", line 587, in request
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/session.py", line 141, in send
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/backends/base.py", line 80, in get_response
File "/usr/lib/python3.10/_collections_abc.py", line 824, in get
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/backends/sqlite.py", line 271, in __getitem__
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/backends/sqlite.py", line 211, in __getitem__
File "/usr/lib/python3.10/contextlib.py", line 135, in __enter__
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/backends/sqlite.py", line 168, in connection
sqlite3.OperationalError: unable to open database file
``` | True | sqlite3.OperationalError: database is locked - I recently ran into this error in version `0.9.8`, which I was able to produce pretty reliably with the following code (against the local `python -m http.server`):
```python
from requests_cache import CachedSession
from requests_cache.backends import SQLiteCache
from concurrent.futures import ThreadPoolExecutor, as_completed
backend = SQLiteCache(db_path="/tmp/wat.sqlite", fast_save=True)
session = CachedSession(expire_after=1, backend=backend)
def cache_get():
return session.get("http://127.0.0.1:8000")
futures = []
with ThreadPoolExecutor(max_workers=100) as e:
for i in range(10000):
future = e.submit(cache_get)
futures.append(future)
for future in as_completed(futures):
print(future.result())
```
This will yield one of two errors, either `sqlite3.OperationalError: database is locked`:
```python
Traceback (most recent call last):
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/session.py", line 212, in _resend
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/session.py", line 193, in _send_and_cache
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/backends/base.py", line 103, in save_response
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/backends/sqlite.py", line 268, in __setitem__
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/backends/sqlite.py", line 220, in __setitem__
sqlite3.OperationalError: database is locked
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/user/test.py", line 18, in <module>
File "/usr/lib/python3.10/concurrent/futures/_base.py", line 451, in result
File "/usr/lib/python3.10/concurrent/futures/_base.py", line 403, in __get_result
File "/usr/lib/python3.10/concurrent/futures/thread.py", line 58, in run
File "/home/user/test.py", line 9, in cache_get
File "/home/user/.local/lib/python3.10/site-packages/requests/sessions.py", line 600, in get
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/session.py", line 115, in request
File "/home/user/.local/lib/python3.10/site-packages/requests/sessions.py", line 587, in request
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/session.py", line 151, in send
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/session.py", line 214, in _resend
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/backends/base.py", line 176, in delete
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/backends/sqlite.py", line 247, in bulk_delete
sqlite3.OperationalError: database is locked
```
or `sqlite3.OperationalError: unable to open database file`:
```python
Traceback (most recent call last):
File "/home/user/test.py", line 18, in <module>
File "/usr/lib/python3.10/concurrent/futures/_base.py", line 451, in result
File "/usr/lib/python3.10/concurrent/futures/_base.py", line 403, in __get_result
File "/usr/lib/python3.10/concurrent/futures/thread.py", line 58, in run
File "/home/user/test.py", line 9, in cache_get
File "/home/user/.local/lib/python3.10/site-packages/requests/sessions.py", line 600, in get
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/session.py", line 115, in request
File "/home/user/.local/lib/python3.10/site-packages/requests/sessions.py", line 587, in request
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/session.py", line 141, in send
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/backends/base.py", line 80, in get_response
File "/usr/lib/python3.10/_collections_abc.py", line 824, in get
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/backends/sqlite.py", line 271, in __getitem__
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/backends/sqlite.py", line 211, in __getitem__
File "/usr/lib/python3.10/contextlib.py", line 135, in __enter__
File "/home/user/.local/lib/python3.10/site-packages/requests_cache/backends/sqlite.py", line 168, in connection
sqlite3.OperationalError: unable to open database file
``` | non_priority | operationalerror database is locked i recently ran into this error in version which i was able to produce pretty reliably with the following code against the local python m http server python from requests cache import cachedsession from requests cache backends import sqlitecache from concurrent futures import threadpoolexecutor as completed backend sqlitecache db path tmp wat sqlite fast save true session cachedsession expire after backend backend def cache get return session get futures with threadpoolexecutor max workers as e for i in range future e submit cache get futures append future for future in as completed futures print future result this will yield one of two errors either operationalerror database is locked python traceback most recent call last file home user local lib site packages requests cache session py line in resend file home user local lib site packages requests cache session py line in send and cache file home user local lib site packages requests cache backends base py line in save response file home user local lib site packages requests cache backends sqlite py line in setitem file home user local lib site packages requests cache backends sqlite py line in setitem operationalerror database is locked during handling of the above exception another exception occurred traceback most recent call last file home user test py line in file usr lib concurrent futures base py line in result file usr lib concurrent futures base py line in get result file usr lib concurrent futures thread py line in run file home user test py line in cache get file home user local lib site packages requests sessions py line in get file home user local lib site packages requests cache session py line in request file home user local lib site packages requests sessions py line in request file home user local lib site packages requests cache session py line in send file home user local lib site packages requests cache session py line in resend file home user local lib site packages requests cache backends base py line in delete file home user local lib site packages requests cache backends sqlite py line in bulk delete operationalerror database is locked or operationalerror unable to open database file python traceback most recent call last file home user test py line in file usr lib concurrent futures base py line in result file usr lib concurrent futures base py line in get result file usr lib concurrent futures thread py line in run file home user test py line in cache get file home user local lib site packages requests sessions py line in get file home user local lib site packages requests cache session py line in request file home user local lib site packages requests sessions py line in request file home user local lib site packages requests cache session py line in send file home user local lib site packages requests cache backends base py line in get response file usr lib collections abc py line in get file home user local lib site packages requests cache backends sqlite py line in getitem file home user local lib site packages requests cache backends sqlite py line in getitem file usr lib contextlib py line in enter file home user local lib site packages requests cache backends sqlite py line in connection operationalerror unable to open database file | 0 |
82,891 | 7,855,543,792 | IssuesEvent | 2018-06-21 02:28:23 | oasis-open/cti-interop | https://api.github.com/repos/oasis-open/cti-interop | closed | Marking Test Data Clarification | PART1 TESTDESCRIPTION | From Emmanuelle:
I had one additional comment on the “STIX v2 Interoperability Test Document Part 1” document. Essentially making it more constrained by saying something along these lines (extracted from section 2.5.2, changes in blue):
1. Producer allows a user or an administrator to apply object level markings to a variety of Indicators that are being shared.
2. Producer may provide TLP object level markings at any level.
a. Producer verifies that objects to be marked do exist in the bundle.
b. Producer must NOT mark Indicator objects with more than one TLP level markings.
3. The Producer creates the marking-definition object for the request:
a. For different objects, the user can apply different TLP levels including: tlp “green”; tlp “amber”; tlp “red”; tlp “white”.
b. The marking-definition must conform to its mandatory attributes including:
i. type is “marking-definition”
ii. id has a globally unique identifier in conformance with TLP Marking Object Type requirements
1. marking-definition--613f2e26-407d-48c7-9eca-b8e91df99dc9 if tlp “white”
2. marking-definition--34098fce-860f-48ae-8e50-ebd3cc5e41da if tlp “green”
3. marking-definition--f88d31f6-486f-44da-b317-01333bde0b82 if tlp “amber”
4. marking-definition--5e57c739-391a-4eb3-b6be-7d15ca92d5ed if tlp “red”
iii. created_by_ref points to the organization identity creating both the indicator object and the associated marking
iv. created and modified time at which the marking-definition was created
v. definition_type open-vocab with a value of “tlp”
vi. definition and the TLP level
4. The SDO object_marking_refs list of marking-definition is populated with markings created by Producer and the id that matches the intended TLP marking.
5. All marking-definitions are embedded in the Bundle.
Essentially, make sure that any TLP created has the ID mandated per the specification. | 1.0 | Marking Test Data Clarification - From Emmanuelle:
I had one additional comment on the “STIX v2 Interoperability Test Document Part 1” document. Essentially making it more constrained by saying something along these lines (extracted from section 2.5.2, changes in blue):
1. Producer allows a user or an administrator to apply object level markings to a variety of Indicators that are being shared.
2. Producer may provide TLP object level markings at any level.
a. Producer verifies that objects to be marked do exist in the bundle.
b. Producer must NOT mark Indicator objects with more than one TLP level markings.
3. The Producer creates the marking-definition object for the request:
a. For different objects, the user can apply different TLP levels including: tlp “green”; tlp “amber”; tlp “red”; tlp “white”.
b. The marking-definition must conform to its mandatory attributes including:
i. type is “marking-definition”
ii. id has a globally unique identifier in conformance with TLP Marking Object Type requirements
1. marking-definition--613f2e26-407d-48c7-9eca-b8e91df99dc9 if tlp “white”
2. marking-definition--34098fce-860f-48ae-8e50-ebd3cc5e41da if tlp “green”
3. marking-definition--f88d31f6-486f-44da-b317-01333bde0b82 if tlp “amber”
4. marking-definition--5e57c739-391a-4eb3-b6be-7d15ca92d5ed if tlp “red”
iii. created_by_ref points to the organization identity creating both the indicator object and the associated marking
iv. created and modified time at which the marking-definition was created
v. definition_type open-vocab with a value of “tlp”
vi. definition and the TLP level
4. The SDO object_marking_refs list of marking-definition is populated with markings created by Producer and the id that matches the intended TLP marking.
5. All marking-definitions are embedded in the Bundle.
Essentially, make sure that any TLP created has the ID mandated per the specification. | non_priority | marking test data clarification from emmanuelle i had one additional comment on the “stix interoperability test document part ” document essentially making it more constrained by saying something along these lines extracted from section changes in blue producer allows a user or an administrator to apply object level markings to a variety of indicators that are being shared producer may provide tlp object level markings at any level a producer verifies that objects to be marked do exist in the bundle b producer must not mark indicator objects with more than one tlp level markings the producer creates the marking definition object for the request a for different objects the user can apply different tlp levels including tlp “green” tlp “amber” tlp “red” tlp “white” b the marking definition must conform to its mandatory attributes including i type is “marking definition” ii id has a globally unique identifier in conformance with tlp marking object type requirements marking definition if tlp “white” marking definition if tlp “green” marking definition if tlp “amber” marking definition if tlp “red” iii created by ref points to the organization identity creating both the indicator object and the associated marking iv created and modified time at which the marking definition was created v definition type open vocab with a value of “tlp” vi definition and the tlp level the sdo object marking refs list of marking definition is populated with markings created by producer and the id that matches the intended tlp marking all marking definitions are embedded in the bundle essentially make sure that any tlp created has the id mandated per the specification | 0 |
74,484 | 20,176,452,685 | IssuesEvent | 2022-02-10 14:54:16 | tensorflow/tfjs | https://api.github.com/repos/tensorflow/tfjs | opened | Not able to install the Library | type:build/install | **System information**
- OS Platform and Distribution (e.g., Linux Ubuntu 16.04): windows 11
- TensorFlow.js installed from (npm or script link): npm i puppeteer-hcaptcha
**Any other info / logs**
npm v 6.9.0
node v12.0.0
yarn v 1.22.17
`npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm notice Beginning October 4, 2021, all connections to the npm registry - including for package installation - must use TLS 1.2 or higher. You are currently using plaintext http to connect. Please visit the GitHub blog for more information: https://github.blog/2021-08-23-npm-registry-deprecating-tls-1-0-tls-1-1/
@tensorflow/tfjs-node@3.13.0 install C:\projects\Repos\project\node_modules@tensorflow\tfjs-node
node scripts/install.js
CPU-windows-3.13.0.zip
Downloading libtensorflow
https://storage.googleapis.com/tensorflow/libtensorflow/libtensorflow-cpu-windows-x86_64-2.7.0.zip
[==============================] 631779/bps 100% 0.0s
Building TensorFlow Node.js bindings
node-pre-gyp install failed with error: Error: Command failed: node-pre-gyp install --fallback-to-build
node-pre-gyp ERR! install response status 404 Not Found on https://storage.googleapis.com/tf-builds/pre-built-binary/napi-v4/3.13.0/CPU-windows-3.13.0.zip
node-pre-gyp WARN Pre-built binaries not installable for @tensorflow/tfjs-node@3.13.0 and node@12.0.0 (node-v72 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp WARN Hit error response status 404 Not Found on https://storage.googleapis.com/tf-builds/pre-built-binary/napi-v4/3.13.0/CPU-windows-3.13.0.zip
gyp ERR! build error
gyp ERR! stack Error: C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (C:\ProgramData\nvm\v12.0.0\node_modules\npm\node_modules\node-gyp\lib\build.js:262:23)
gyp ERR! stack at ChildProcess.emit (events.js:196:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:256:12)
gyp ERR! System Windows_NT 10.0.22000
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\ProgramData\nvm\v12.0.0\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "build" "--fallback-to-build" "--module=C:\projects\Repos\project\node_modules\https://github.com/tensorflow\tfjs-node\lib\napi-v4\tfjs_binding.node" "--module_name=tfjs_binding" "--module_path=C:\projects\Repos\project\node_modules\https://github.com/tensorflow\tfjs-node\lib\napi-v4" "--napi_version=4" "--node_abi_napi=napi" "--napi_build_version=4" "--node_napi_label=napi-v4"
gyp ERR! cwd C:\projects\Repos\project\node_modules@tensorflow\tfjs-node
gyp ERR! node -v v12.0.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute 'C:\Program Files\nodejs\node.exe C:\ProgramData\nvm\v12.0.0\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js build --fallback-to-build --module=C:\projects\Repos\project\node_modules@tensorflow\tfjs-node\lib\napi-v4\tfjs_binding.node --module_name=tfjs_binding --module_path=C:\projects\Repos\project\node_modules@tensorflow\tfjs-node\lib\napi-v4 --napi_version=4 --node_abi_napi=napi --napi_build_version=4 --node_napi_label=napi-v4' (1)
node-pre-gyp ERR! stack at ChildProcess. (C:\projects\Repos\project\node_moduleshttps://github.com/mapbox\node-pre-gyp\lib\util\compile.js:89:23)
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:196:13)
node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:1000:16)
node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:267:5)
node-pre-gyp ERR! System Windows_NT 10.0.22000
node-pre-gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\projects\Repos\project\node_modules\@mapbox\node-pre-gyp\bin\node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd C:\projects\Repos\project\node_modules@tensorflow\tfjs-node
node-pre-gyp ERR! node -v v12.0.0
node-pre-gyp ERR! node-pre-gyp -v v1.0.4
node-pre-gyp ERR! not ok
npm WARN project@1.0.0 No description
npm WARN project@1.0.0 No repository field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @tensorflow/tfjs-node@3.13.0 install: node scripts/install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @tensorflow/tfjs-node@3.13.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\user\AppData\Roaming\npm-cache_logs\2022-02-08T21_53_29_638Z-debug.log` | 1.0 | Not able to install the Library - **System information**
- OS Platform and Distribution (e.g., Linux Ubuntu 16.04): windows 11
- TensorFlow.js installed from (npm or script link): npm i puppeteer-hcaptcha
**Any other info / logs**
npm v 6.9.0
node v12.0.0
yarn v 1.22.17
`npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm notice Beginning October 4, 2021, all connections to the npm registry - including for package installation - must use TLS 1.2 or higher. You are currently using plaintext http to connect. Please visit the GitHub blog for more information: https://github.blog/2021-08-23-npm-registry-deprecating-tls-1-0-tls-1-1/
@tensorflow/tfjs-node@3.13.0 install C:\projects\Repos\project\node_modules@tensorflow\tfjs-node
node scripts/install.js
CPU-windows-3.13.0.zip
Downloading libtensorflow
https://storage.googleapis.com/tensorflow/libtensorflow/libtensorflow-cpu-windows-x86_64-2.7.0.zip
[==============================] 631779/bps 100% 0.0s
Building TensorFlow Node.js bindings
node-pre-gyp install failed with error: Error: Command failed: node-pre-gyp install --fallback-to-build
node-pre-gyp ERR! install response status 404 Not Found on https://storage.googleapis.com/tf-builds/pre-built-binary/napi-v4/3.13.0/CPU-windows-3.13.0.zip
node-pre-gyp WARN Pre-built binaries not installable for @tensorflow/tfjs-node@3.13.0 and node@12.0.0 (node-v72 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp WARN Hit error response status 404 Not Found on https://storage.googleapis.com/tf-builds/pre-built-binary/napi-v4/3.13.0/CPU-windows-3.13.0.zip
gyp ERR! build error
gyp ERR! stack Error: C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (C:\ProgramData\nvm\v12.0.0\node_modules\npm\node_modules\node-gyp\lib\build.js:262:23)
gyp ERR! stack at ChildProcess.emit (events.js:196:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:256:12)
gyp ERR! System Windows_NT 10.0.22000
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\ProgramData\nvm\v12.0.0\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "build" "--fallback-to-build" "--module=C:\projects\Repos\project\node_modules\https://github.com/tensorflow\tfjs-node\lib\napi-v4\tfjs_binding.node" "--module_name=tfjs_binding" "--module_path=C:\projects\Repos\project\node_modules\https://github.com/tensorflow\tfjs-node\lib\napi-v4" "--napi_version=4" "--node_abi_napi=napi" "--napi_build_version=4" "--node_napi_label=napi-v4"
gyp ERR! cwd C:\projects\Repos\project\node_modules@tensorflow\tfjs-node
gyp ERR! node -v v12.0.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute 'C:\Program Files\nodejs\node.exe C:\ProgramData\nvm\v12.0.0\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js build --fallback-to-build --module=C:\projects\Repos\project\node_modules@tensorflow\tfjs-node\lib\napi-v4\tfjs_binding.node --module_name=tfjs_binding --module_path=C:\projects\Repos\project\node_modules@tensorflow\tfjs-node\lib\napi-v4 --napi_version=4 --node_abi_napi=napi --napi_build_version=4 --node_napi_label=napi-v4' (1)
node-pre-gyp ERR! stack at ChildProcess. (C:\projects\Repos\project\node_moduleshttps://github.com/mapbox\node-pre-gyp\lib\util\compile.js:89:23)
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:196:13)
node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:1000:16)
node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:267:5)
node-pre-gyp ERR! System Windows_NT 10.0.22000
node-pre-gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\projects\Repos\project\node_modules\@mapbox\node-pre-gyp\bin\node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd C:\projects\Repos\project\node_modules@tensorflow\tfjs-node
node-pre-gyp ERR! node -v v12.0.0
node-pre-gyp ERR! node-pre-gyp -v v1.0.4
node-pre-gyp ERR! not ok
npm WARN project@1.0.0 No description
npm WARN project@1.0.0 No repository field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @tensorflow/tfjs-node@3.13.0 install: node scripts/install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @tensorflow/tfjs-node@3.13.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\user\AppData\Roaming\npm-cache_logs\2022-02-08T21_53_29_638Z-debug.log` | non_priority | not able to install the library system information os platform and distribution e g linux ubuntu windows tensorflow js installed from npm or script link npm i puppeteer hcaptcha any other info logs npm v node yarn v npm warn deprecated request request has been deprecated see npm warn deprecated request promise native request promise native has been deprecated because it extends the now deprecated request package see npm warn deprecated har validator this library is no longer supported npm warn deprecated uuid please upgrade to version or higher older versions may use math random in certain circumstances which is known to be problematic see for details npm notice beginning october all connections to the npm registry including for package installation must use tls or higher you are currently using plaintext http to connect please visit the github blog for more information tensorflow tfjs node install c projects repos project node modules tensorflow tfjs node node scripts install js cpu windows zip downloading libtensorflow bps building tensorflow node js bindings node pre gyp install failed with error error command failed node pre gyp install fallback to build node pre gyp err install response status not found on node pre gyp warn pre built binaries not installable for tensorflow tfjs node and node node abi unknown falling back to source compile with node gyp node pre gyp warn hit error response status not found on gyp err build error gyp err stack error c windows microsoft net framework msbuild exe failed with exit code gyp err stack at childprocess onexit c programdata nvm node modules npm node modules node gyp lib build js gyp err stack at childprocess emit events js gyp err stack at process childprocess handle onexit internal child process js gyp err system windows nt gyp err command c program files nodejs node exe c programdata nvm node modules npm node modules node gyp bin node gyp js build fallback to build module c projects repos project node modules module name tfjs binding module path c projects repos project node modules napi version node abi napi napi napi build version node napi label napi gyp err cwd c projects repos project node modules tensorflow tfjs node gyp err node v gyp err node gyp v gyp err not ok node pre gyp err build error node pre gyp err stack error failed to execute c program files nodejs node exe c programdata nvm node modules npm node modules node gyp bin node gyp js build fallback to build module c projects repos project node modules tensorflow tfjs node lib napi tfjs binding node module name tfjs binding module path c projects repos project node modules tensorflow tfjs node lib napi napi version node abi napi napi napi build version node napi label napi node pre gyp err stack at childprocess c projects repos project node modules node pre gyp err stack at childprocess emit events js node pre gyp err stack at maybeclose internal child process js node pre gyp err stack at process childprocess handle onexit internal child process js node pre gyp err system windows nt node pre gyp err command c program files nodejs node exe c projects repos project node modules mapbox node pre gyp bin node pre gyp install fallback to build node pre gyp err cwd c projects repos project node modules tensorflow tfjs node node pre gyp err node v node pre gyp err node pre gyp v node pre gyp err not ok npm warn project no description npm warn project no repository field npm err code elifecycle npm err errno npm err tensorflow tfjs node install node scripts install js npm err exit status npm err npm err failed at the tensorflow tfjs node install script npm err this is probably not a problem with npm there is likely additional logging output above npm err a complete log of this run can be found in npm err c users user appdata roaming npm cache logs debug log | 0 |
257,404 | 22,159,429,348 | IssuesEvent | 2022-06-04 09:07:00 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | roachtest: tpccbench/nodes=12/cpu=16 failed | C-test-failure O-robot O-roachtest branch-master release-blocker | roachtest.tpccbench/nodes=12/cpu=16 [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestWeeklyBazel/5371447?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestWeeklyBazel/5371447?buildTab=artifacts#/tpccbench/nodes=12/cpu=16) on master @ [90b5db50e1e1cdb0315d8b094081d261e6dcb336](https://github.com/cockroachdb/cockroach/commits/90b5db50e1e1cdb0315d8b094081d261e6dcb336):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /artifacts/bazel-20220604-5371447/tpccbench/nodes=12/cpu=16/run_1
monitor.go:127,tpcc.go:1103,tpcc.go:938,test_runner.go:884: monitor failure: monitor task failed: Non-zero exit code: 1
(1) attached stack trace
-- stack trace:
| main.(*monitorImpl).WaitE
| main/pkg/cmd/roachtest/monitor.go:115
| main.(*monitorImpl).Wait
| main/pkg/cmd/roachtest/monitor.go:123
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.runTPCCBench
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/tpcc.go:1103
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerTPCCBenchSpec.func1
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/tpcc.go:938
| [...repeated from below...]
Wraps: (2) monitor failure
Wraps: (3) attached stack trace
-- stack trace:
| main.(*monitorImpl).wait.func2
| main/pkg/cmd/roachtest/monitor.go:171
| runtime.goexit
| GOROOT/src/runtime/asm_amd64.s:1581
Wraps: (4) monitor task failed
Wraps: (5) Non-zero exit code: 1
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) *errutil.withPrefix (5) *install.NonZeroExitCode
```
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/kv-triage
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*tpccbench/nodes=12/cpu=16.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| 2.0 | roachtest: tpccbench/nodes=12/cpu=16 failed - roachtest.tpccbench/nodes=12/cpu=16 [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestWeeklyBazel/5371447?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestWeeklyBazel/5371447?buildTab=artifacts#/tpccbench/nodes=12/cpu=16) on master @ [90b5db50e1e1cdb0315d8b094081d261e6dcb336](https://github.com/cockroachdb/cockroach/commits/90b5db50e1e1cdb0315d8b094081d261e6dcb336):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /artifacts/bazel-20220604-5371447/tpccbench/nodes=12/cpu=16/run_1
monitor.go:127,tpcc.go:1103,tpcc.go:938,test_runner.go:884: monitor failure: monitor task failed: Non-zero exit code: 1
(1) attached stack trace
-- stack trace:
| main.(*monitorImpl).WaitE
| main/pkg/cmd/roachtest/monitor.go:115
| main.(*monitorImpl).Wait
| main/pkg/cmd/roachtest/monitor.go:123
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.runTPCCBench
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/tpcc.go:1103
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerTPCCBenchSpec.func1
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/tpcc.go:938
| [...repeated from below...]
Wraps: (2) monitor failure
Wraps: (3) attached stack trace
-- stack trace:
| main.(*monitorImpl).wait.func2
| main/pkg/cmd/roachtest/monitor.go:171
| runtime.goexit
| GOROOT/src/runtime/asm_amd64.s:1581
Wraps: (4) monitor task failed
Wraps: (5) Non-zero exit code: 1
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) *errutil.withPrefix (5) *install.NonZeroExitCode
```
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
/cc @cockroachdb/kv-triage
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*tpccbench/nodes=12/cpu=16.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| non_priority | roachtest tpccbench nodes cpu failed roachtest tpccbench nodes cpu with on master the test failed on branch master cloud gce test artifacts and logs in artifacts bazel tpccbench nodes cpu run monitor go tpcc go tpcc go test runner go monitor failure monitor task failed non zero exit code attached stack trace stack trace main monitorimpl waite main pkg cmd roachtest monitor go main monitorimpl wait main pkg cmd roachtest monitor go github com cockroachdb cockroach pkg cmd roachtest tests runtpccbench github com cockroachdb cockroach pkg cmd roachtest tests tpcc go github com cockroachdb cockroach pkg cmd roachtest tests registertpccbenchspec github com cockroachdb cockroach pkg cmd roachtest tests tpcc go wraps monitor failure wraps attached stack trace stack trace main monitorimpl wait main pkg cmd roachtest monitor go runtime goexit goroot src runtime asm s wraps monitor task failed wraps non zero exit code error types withstack withstack errutil withprefix withstack withstack errutil withprefix install nonzeroexitcode help see see cc cockroachdb kv triage | 0 |
10,009 | 3,989,021,844 | IssuesEvent | 2016-05-09 12:30:03 | kevinpmcc/intro-game | https://api.github.com/repos/kevinpmcc/intro-game | closed | play-one-second | code review | As a player
In order to make the game challenging
I would like to hear a clip of length no longer than one second | 1.0 | play-one-second - As a player
In order to make the game challenging
I would like to hear a clip of length no longer than one second | non_priority | play one second as a player in order to make the game challenging i would like to hear a clip of length no longer than one second | 0 |
209,937 | 16,067,368,924 | IssuesEvent | 2021-04-23 21:38:21 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | roachtest: gorm failed | C-test-failure O-roachtest O-robot branch-master release-blocker | roachtest.gorm [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2917180&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=2917180&tab=artifacts#/gorm) on master @ [9e821aa456bfbe8b5ec3a8ef79ae3954d52cb675](https://github.com/cockroachdb/cockroach/commits/9e821aa456bfbe8b5ec3a8ef79ae3954d52cb675):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/gorm/run_1
test.go:298,assertions.go:262,assertions.go:1332,require.go:1035,gorm.go:103,test_runner.go:777:
Error Trace: gorm.go:103
test_runner.go:777
asm_amd64.s:1374
Error: Received unexpected error:
output in run_213727.401_n1_cockroach_sql: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod run teamcity-2917180-1619205254-41-n1cpu4:1 -- cockroach sql -e "CREATE DATABASE gorm" --insecure returned: exit status 20
(1) attached stack trace
-- stack trace:
| main.(*cluster).RunE
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2418
| main.registerGORM.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/gorm.go:102
| main.(*testRunner).runTest.func2
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/test_runner.go:777
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1374
Wraps: (2) output in run_213727.401_n1_cockroach_sql
Wraps: (3) /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod run teamcity-2917180-1619205254-41-n1cpu4:1 -- cockroach sql -e "CREATE DATABASE gorm" --insecure returned
| stderr:
| bash: cockroach: command not found
| Error: COMMAND_PROBLEM: exit status 127
| (1) COMMAND_PROBLEM
| Wraps: (2) Node 1. Command with error:
| | ``````
| | cockroach sql -e "CREATE DATABASE gorm" --insecure
| | ``````
| Wraps: (3) exit status 127
| Error types: (1) errors.Cmd (2) *hintdetail.withDetail (3) *exec.ExitError
|
| stdout:
Wraps: (4) exit status 20
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *main.withCommandDetails (4) *exec.ExitError
Test: gorm
```
<details><summary>Reproduce</summary>
<p>
<p>To reproduce, try:
```bash
# From https://go.crdb.dev/p/roachstress, perhaps edited lightly.
caffeinate ./roachstress.sh gorm
```
</p>
</p>
</details>
/cc @cockroachdb/sql-experience
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*gorm.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| 2.0 | roachtest: gorm failed - roachtest.gorm [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2917180&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=2917180&tab=artifacts#/gorm) on master @ [9e821aa456bfbe8b5ec3a8ef79ae3954d52cb675](https://github.com/cockroachdb/cockroach/commits/9e821aa456bfbe8b5ec3a8ef79ae3954d52cb675):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/gorm/run_1
test.go:298,assertions.go:262,assertions.go:1332,require.go:1035,gorm.go:103,test_runner.go:777:
Error Trace: gorm.go:103
test_runner.go:777
asm_amd64.s:1374
Error: Received unexpected error:
output in run_213727.401_n1_cockroach_sql: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod run teamcity-2917180-1619205254-41-n1cpu4:1 -- cockroach sql -e "CREATE DATABASE gorm" --insecure returned: exit status 20
(1) attached stack trace
-- stack trace:
| main.(*cluster).RunE
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2418
| main.registerGORM.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/gorm.go:102
| main.(*testRunner).runTest.func2
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/test_runner.go:777
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1374
Wraps: (2) output in run_213727.401_n1_cockroach_sql
Wraps: (3) /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod run teamcity-2917180-1619205254-41-n1cpu4:1 -- cockroach sql -e "CREATE DATABASE gorm" --insecure returned
| stderr:
| bash: cockroach: command not found
| Error: COMMAND_PROBLEM: exit status 127
| (1) COMMAND_PROBLEM
| Wraps: (2) Node 1. Command with error:
| | ``````
| | cockroach sql -e "CREATE DATABASE gorm" --insecure
| | ``````
| Wraps: (3) exit status 127
| Error types: (1) errors.Cmd (2) *hintdetail.withDetail (3) *exec.ExitError
|
| stdout:
Wraps: (4) exit status 20
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *main.withCommandDetails (4) *exec.ExitError
Test: gorm
```
<details><summary>Reproduce</summary>
<p>
<p>To reproduce, try:
```bash
# From https://go.crdb.dev/p/roachstress, perhaps edited lightly.
caffeinate ./roachstress.sh gorm
```
</p>
</p>
</details>
/cc @cockroachdb/sql-experience
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*gorm.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| non_priority | roachtest gorm failed roachtest gorm with on master the test failed on branch master cloud gce test artifacts and logs in home agent work go src github com cockroachdb cockroach artifacts gorm run test go assertions go assertions go require go gorm go test runner go error trace gorm go test runner go asm s error received unexpected error output in run cockroach sql home agent work go src github com cockroachdb cockroach bin roachprod run teamcity cockroach sql e create database gorm insecure returned exit status attached stack trace stack trace main cluster rune home agent work go src github com cockroachdb cockroach pkg cmd roachtest cluster go main registergorm home agent work go src github com cockroachdb cockroach pkg cmd roachtest gorm go main testrunner runtest home agent work go src github com cockroachdb cockroach pkg cmd roachtest test runner go runtime goexit usr local go src runtime asm s wraps output in run cockroach sql wraps home agent work go src github com cockroachdb cockroach bin roachprod run teamcity cockroach sql e create database gorm insecure returned stderr bash cockroach command not found error command problem exit status command problem wraps node command with error cockroach sql e create database gorm insecure wraps exit status error types errors cmd hintdetail withdetail exec exiterror stdout wraps exit status error types withstack withstack errutil withprefix main withcommanddetails exec exiterror test gorm reproduce to reproduce try bash from perhaps edited lightly caffeinate roachstress sh gorm cc cockroachdb sql experience | 0 |
33,996 | 4,876,680,297 | IssuesEvent | 2016-11-16 13:38:53 | vector-im/vector-android | https://api.github.com/repos/vector-im/vector-android | opened | DM marking disappear on particular circumstance | auto-test-required bug P1 | To reproduce:
- Have account 1 with no direct message tags at all
- Have account 2 with no direct message tags at all
- With a non direct message client (matrix console) create room and invite account 2
- With a non direct message client (matrix console) accetpte invitation with account 2
- Log these account on direct message compatible devices
- The room is tagged DM on both devices
- log out,restart app, log in on both devices (don't know if it's very necessary)
- Room is still DM on both devices
- Start chat from account 1 to account 2
The first room is no more tagged DM.
Logs: https://matrix.org/_matrix/media/v1/download/matrix.org/sxPdcBzjJNomDXFSuwsTnZkv
Version on both devices: 0.6.0-dev (40a2744)
| 1.0 | DM marking disappear on particular circumstance - To reproduce:
- Have account 1 with no direct message tags at all
- Have account 2 with no direct message tags at all
- With a non direct message client (matrix console) create room and invite account 2
- With a non direct message client (matrix console) accetpte invitation with account 2
- Log these account on direct message compatible devices
- The room is tagged DM on both devices
- log out,restart app, log in on both devices (don't know if it's very necessary)
- Room is still DM on both devices
- Start chat from account 1 to account 2
The first room is no more tagged DM.
Logs: https://matrix.org/_matrix/media/v1/download/matrix.org/sxPdcBzjJNomDXFSuwsTnZkv
Version on both devices: 0.6.0-dev (40a2744)
| non_priority | dm marking disappear on particular circumstance to reproduce have account with no direct message tags at all have account with no direct message tags at all with a non direct message client matrix console create room and invite account with a non direct message client matrix console accetpte invitation with account log these account on direct message compatible devices the room is tagged dm on both devices log out restart app log in on both devices don t know if it s very necessary room is still dm on both devices start chat from account to account the first room is no more tagged dm logs version on both devices dev | 0 |
192,484 | 22,215,960,010 | IssuesEvent | 2022-06-08 01:41:19 | madhans23/linux-4.1.15 | https://api.github.com/repos/madhans23/linux-4.1.15 | reopened | CVE-2019-20810 (Medium) detected in linux-stable-rtv4.1.33 | security vulnerability | ## CVE-2019-20810 - Medium 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 (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/media/usb/go7007/snd-go7007.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/media/usb/go7007/snd-go7007.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>
go7007_snd_init in drivers/media/usb/go7007/snd-go7007.c in the Linux kernel before 5.6 does not call snd_card_free for a failure path, which causes a memory leak, aka CID-9453264ef586.
<p>Publish Date: 2020-06-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20810>CVE-2019-20810</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20810">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20810</a></p>
<p>Release Date: 2020-06-03</p>
<p>Fix Resolution: v5.6-rc1</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-20810 (Medium) detected in linux-stable-rtv4.1.33 - ## CVE-2019-20810 - Medium 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 (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/media/usb/go7007/snd-go7007.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/media/usb/go7007/snd-go7007.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>
go7007_snd_init in drivers/media/usb/go7007/snd-go7007.c in the Linux kernel before 5.6 does not call snd_card_free for a failure path, which causes a memory leak, aka CID-9453264ef586.
<p>Publish Date: 2020-06-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20810>CVE-2019-20810</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20810">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20810</a></p>
<p>Release Date: 2020-06-03</p>
<p>Fix Resolution: v5.6-rc1</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 linux stable cve medium 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 drivers media usb snd c drivers media usb snd c vulnerability details snd init in drivers media usb snd c in the linux kernel before does not call snd card free for a failure path which causes a memory leak 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 none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
142,510 | 13,032,101,001 | IssuesEvent | 2020-07-28 03:14:56 | apache/pulsar | https://api.github.com/repos/apache/pulsar | closed | Documentation: skip-all versus clear-backlog | component/documentation triage/week-46 type/feature | **Is your feature request related to a problem? Please describe.**
Documentation shows [skip-all](https://pulsar.apache.org/docs/en/pulsar-admin/#skip-all) followed by [clear-backlog](https://pulsar.apache.org/docs/en/pulsar-admin/#clear-backlog-1), both at the topic with no description of what the difference is.
I don't know when it's appropriate to use one or the other.
Note: there is a separate [clear-backlog](https://pulsar.apache.org/docs/en/pulsar-admin/#clear-backlog) command documented at the namespace level (rather than the topic level)
UPDATE 1: pulsar-admin doesn't seem to recognise `topics skip-all` at all.
```
ubuntu@ldex-pulsar:~$ apache-pulsar-2.4.1/bin/pulsar-admin topics clear-backlog
The following option is required: -s, --subscription
Skip all the messages for the subscription
Usage: clear-backlog [options] persistent://tenant/namespace/topic
Options:
* -s, --subscription
Subscription to be cleared
ubuntu@ldex-pulsar:~$ apache-pulsar-2.4.1/bin/pulsar-admin topics skip-all
Expected a command, got skip-all
Exception in thread "main" com.beust.jcommander.ParameterException: Asking description for unknown command: null
at com.beust.jcommander.JCommander.getCommandDescription(JCommander.java:1003)
at com.beust.jcommander.JCommander.usage(JCommander.java:988)
at com.beust.jcommander.JCommander.usage(JCommander.java:980)
at com.beust.jcommander.JCommander.usage(JCommander.java:972)
at org.apache.pulsar.admin.cli.CmdBase.run(CmdBase.java:49)
at org.apache.pulsar.admin.cli.PulsarAdminTool.run(PulsarAdminTool.java:218)
at org.apache.pulsar.admin.cli.PulsarAdminTool.main(PulsarAdminTool.java:260)
^C
ubuntu@ldex-pulsar:~$ apache-pulsar-2.4.1/bin/pulsar-admin topics skip-all persistent://public/default/my-topic -s my-subscription
Expected a command, got skip-all
Exception in thread "main" com.beust.jcommander.ParameterException: Asking description for unknown command: null
at com.beust.jcommander.JCommander.getCommandDescription(JCommander.java:1003)
at com.beust.jcommander.JCommander.usage(JCommander.java:988)
at com.beust.jcommander.JCommander.usage(JCommander.java:980)
at com.beust.jcommander.JCommander.usage(JCommander.java:972)
at org.apache.pulsar.admin.cli.CmdBase.run(CmdBase.java:49)
at org.apache.pulsar.admin.cli.PulsarAdminTool.run(PulsarAdminTool.java:218)
at org.apache.pulsar.admin.cli.PulsarAdminTool.main(PulsarAdminTool.java:260)
^C
```
But there appears to be a test case for it in [pulsar-client-tools-test/src/test/java/org/apache/pulsar/admin/cli/PulsarAdminToolTest.java](https://github.com/apache/pulsar/blob/master/pulsar-client-tools-test/src/test/java/org/apache/pulsar/admin/cli/PulsarAdminToolTest.java#L714)
```
topics.run(split("skip-all persistent://myprop/clust/ns1/ds1 -s sub1"));
verify(mockTopics).skipAllMessages("persistent://myprop/clust/ns1/ds1", "sub1");
```
`clear-backlog` works at the topic+subscription level:
```
ubuntu@ldex-pulsar:~$ apache-pulsar-2.4.1/bin/pulsar-admin topics clear-backlog persistent://public/default/my-topic -s my-subscription
ubuntu@ldex-pulsar:~$
```
| 1.0 | Documentation: skip-all versus clear-backlog - **Is your feature request related to a problem? Please describe.**
Documentation shows [skip-all](https://pulsar.apache.org/docs/en/pulsar-admin/#skip-all) followed by [clear-backlog](https://pulsar.apache.org/docs/en/pulsar-admin/#clear-backlog-1), both at the topic with no description of what the difference is.
I don't know when it's appropriate to use one or the other.
Note: there is a separate [clear-backlog](https://pulsar.apache.org/docs/en/pulsar-admin/#clear-backlog) command documented at the namespace level (rather than the topic level)
UPDATE 1: pulsar-admin doesn't seem to recognise `topics skip-all` at all.
```
ubuntu@ldex-pulsar:~$ apache-pulsar-2.4.1/bin/pulsar-admin topics clear-backlog
The following option is required: -s, --subscription
Skip all the messages for the subscription
Usage: clear-backlog [options] persistent://tenant/namespace/topic
Options:
* -s, --subscription
Subscription to be cleared
ubuntu@ldex-pulsar:~$ apache-pulsar-2.4.1/bin/pulsar-admin topics skip-all
Expected a command, got skip-all
Exception in thread "main" com.beust.jcommander.ParameterException: Asking description for unknown command: null
at com.beust.jcommander.JCommander.getCommandDescription(JCommander.java:1003)
at com.beust.jcommander.JCommander.usage(JCommander.java:988)
at com.beust.jcommander.JCommander.usage(JCommander.java:980)
at com.beust.jcommander.JCommander.usage(JCommander.java:972)
at org.apache.pulsar.admin.cli.CmdBase.run(CmdBase.java:49)
at org.apache.pulsar.admin.cli.PulsarAdminTool.run(PulsarAdminTool.java:218)
at org.apache.pulsar.admin.cli.PulsarAdminTool.main(PulsarAdminTool.java:260)
^C
ubuntu@ldex-pulsar:~$ apache-pulsar-2.4.1/bin/pulsar-admin topics skip-all persistent://public/default/my-topic -s my-subscription
Expected a command, got skip-all
Exception in thread "main" com.beust.jcommander.ParameterException: Asking description for unknown command: null
at com.beust.jcommander.JCommander.getCommandDescription(JCommander.java:1003)
at com.beust.jcommander.JCommander.usage(JCommander.java:988)
at com.beust.jcommander.JCommander.usage(JCommander.java:980)
at com.beust.jcommander.JCommander.usage(JCommander.java:972)
at org.apache.pulsar.admin.cli.CmdBase.run(CmdBase.java:49)
at org.apache.pulsar.admin.cli.PulsarAdminTool.run(PulsarAdminTool.java:218)
at org.apache.pulsar.admin.cli.PulsarAdminTool.main(PulsarAdminTool.java:260)
^C
```
But there appears to be a test case for it in [pulsar-client-tools-test/src/test/java/org/apache/pulsar/admin/cli/PulsarAdminToolTest.java](https://github.com/apache/pulsar/blob/master/pulsar-client-tools-test/src/test/java/org/apache/pulsar/admin/cli/PulsarAdminToolTest.java#L714)
```
topics.run(split("skip-all persistent://myprop/clust/ns1/ds1 -s sub1"));
verify(mockTopics).skipAllMessages("persistent://myprop/clust/ns1/ds1", "sub1");
```
`clear-backlog` works at the topic+subscription level:
```
ubuntu@ldex-pulsar:~$ apache-pulsar-2.4.1/bin/pulsar-admin topics clear-backlog persistent://public/default/my-topic -s my-subscription
ubuntu@ldex-pulsar:~$
```
| non_priority | documentation skip all versus clear backlog is your feature request related to a problem please describe documentation shows followed by both at the topic with no description of what the difference is i don t know when it s appropriate to use one or the other note there is a separate command documented at the namespace level rather than the topic level update pulsar admin doesn t seem to recognise topics skip all at all ubuntu ldex pulsar apache pulsar bin pulsar admin topics clear backlog the following option is required s subscription skip all the messages for the subscription usage clear backlog persistent tenant namespace topic options s subscription subscription to be cleared ubuntu ldex pulsar apache pulsar bin pulsar admin topics skip all expected a command got skip all exception in thread main com beust jcommander parameterexception asking description for unknown command null at com beust jcommander jcommander getcommanddescription jcommander java at com beust jcommander jcommander usage jcommander java at com beust jcommander jcommander usage jcommander java at com beust jcommander jcommander usage jcommander java at org apache pulsar admin cli cmdbase run cmdbase java at org apache pulsar admin cli pulsaradmintool run pulsaradmintool java at org apache pulsar admin cli pulsaradmintool main pulsaradmintool java c ubuntu ldex pulsar apache pulsar bin pulsar admin topics skip all persistent public default my topic s my subscription expected a command got skip all exception in thread main com beust jcommander parameterexception asking description for unknown command null at com beust jcommander jcommander getcommanddescription jcommander java at com beust jcommander jcommander usage jcommander java at com beust jcommander jcommander usage jcommander java at com beust jcommander jcommander usage jcommander java at org apache pulsar admin cli cmdbase run cmdbase java at org apache pulsar admin cli pulsaradmintool run pulsaradmintool java at org apache pulsar admin cli pulsaradmintool main pulsaradmintool java c but there appears to be a test case for it in topics run split skip all persistent myprop clust s verify mocktopics skipallmessages persistent myprop clust clear backlog works at the topic subscription level ubuntu ldex pulsar apache pulsar bin pulsar admin topics clear backlog persistent public default my topic s my subscription ubuntu ldex pulsar | 0 |
122,901 | 17,771,622,367 | IssuesEvent | 2021-08-30 14:16:34 | Tim-sandbox/barista | https://api.github.com/repos/Tim-sandbox/barista | opened | CVE-2020-7753 (High) detected in trim-0.0.1.tgz | security vulnerability | ## CVE-2020-7753 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>trim-0.0.1.tgz</b></p></summary>
<p>Trim string whitespace</p>
<p>Library home page: <a href="https://registry.npmjs.org/trim/-/trim-0.0.1.tgz">https://registry.npmjs.org/trim/-/trim-0.0.1.tgz</a></p>
<p>Path to dependency file: barista/barista-docs/package.json</p>
<p>Path to vulnerable library: barista/barista-docs/node_modules/trim/package.json</p>
<p>
Dependency Hierarchy:
- preset-classic-2.0.0-beta.5.tgz (Root Library)
- theme-classic-2.0.0-beta.5.tgz
- mdx-1.6.22.tgz
- remark-parse-8.0.3.tgz
- :x: **trim-0.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Tim-sandbox/barista/commit/2b8e77b2ff0d688bfd2ffb44061287e82fa71967">2b8e77b2ff0d688bfd2ffb44061287e82fa71967</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>
All versions of package trim are vulnerable to Regular Expression Denial of Service (ReDoS) via trim().
<p>Publish Date: 2020-10-27
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7753>CVE-2020-7753</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/component/trim/pull/8">https://github.com/component/trim/pull/8</a></p>
<p>Release Date: 2020-10-27</p>
<p>Fix Resolution: trim - 0.0.3</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"trim","packageVersion":"0.0.1","packageFilePaths":["/barista-docs/package.json"],"isTransitiveDependency":true,"dependencyTree":"@docusaurus/preset-classic:2.0.0-beta.5;@docusaurus/theme-classic:2.0.0-beta.5;@mdx-js/mdx:1.6.22;remark-parse:8.0.3;trim:0.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"trim - 0.0.3"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-7753","vulnerabilityDetails":"All versions of package trim are vulnerable to Regular Expression Denial of Service (ReDoS) via trim().","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7753","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-7753 (High) detected in trim-0.0.1.tgz - ## CVE-2020-7753 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>trim-0.0.1.tgz</b></p></summary>
<p>Trim string whitespace</p>
<p>Library home page: <a href="https://registry.npmjs.org/trim/-/trim-0.0.1.tgz">https://registry.npmjs.org/trim/-/trim-0.0.1.tgz</a></p>
<p>Path to dependency file: barista/barista-docs/package.json</p>
<p>Path to vulnerable library: barista/barista-docs/node_modules/trim/package.json</p>
<p>
Dependency Hierarchy:
- preset-classic-2.0.0-beta.5.tgz (Root Library)
- theme-classic-2.0.0-beta.5.tgz
- mdx-1.6.22.tgz
- remark-parse-8.0.3.tgz
- :x: **trim-0.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Tim-sandbox/barista/commit/2b8e77b2ff0d688bfd2ffb44061287e82fa71967">2b8e77b2ff0d688bfd2ffb44061287e82fa71967</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>
All versions of package trim are vulnerable to Regular Expression Denial of Service (ReDoS) via trim().
<p>Publish Date: 2020-10-27
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7753>CVE-2020-7753</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/component/trim/pull/8">https://github.com/component/trim/pull/8</a></p>
<p>Release Date: 2020-10-27</p>
<p>Fix Resolution: trim - 0.0.3</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"trim","packageVersion":"0.0.1","packageFilePaths":["/barista-docs/package.json"],"isTransitiveDependency":true,"dependencyTree":"@docusaurus/preset-classic:2.0.0-beta.5;@docusaurus/theme-classic:2.0.0-beta.5;@mdx-js/mdx:1.6.22;remark-parse:8.0.3;trim:0.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"trim - 0.0.3"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-7753","vulnerabilityDetails":"All versions of package trim are vulnerable to Regular Expression Denial of Service (ReDoS) via trim().","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7753","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in trim tgz cve high severity vulnerability vulnerable library trim tgz trim string whitespace library home page a href path to dependency file barista barista docs package json path to vulnerable library barista barista docs node modules trim package json dependency hierarchy preset classic beta tgz root library theme classic beta tgz mdx tgz remark parse tgz x trim tgz vulnerable library found in head commit a href found in base branch master vulnerability details all versions of package trim are vulnerable to regular expression denial of service redos via trim 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 isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree docusaurus preset classic beta docusaurus theme classic beta mdx js mdx remark parse trim isminimumfixversionavailable true minimumfixversion trim basebranches vulnerabilityidentifier cve vulnerabilitydetails all versions of package trim are vulnerable to regular expression denial of service redos via trim vulnerabilityurl | 0 |
347,543 | 24,890,231,667 | IssuesEvent | 2022-10-28 11:19:37 | danialhbma/ICT2101-P2-10 | https://api.github.com/repos/danialhbma/ICT2101-P2-10 | closed | Report M2 - Section 2 | documentation | After receiving feedback for M1 Report, we need to standardise our requirements & add in new requirements for the new database actor. We also have to standardise the format of the requirements. | 1.0 | Report M2 - Section 2 - After receiving feedback for M1 Report, we need to standardise our requirements & add in new requirements for the new database actor. We also have to standardise the format of the requirements. | non_priority | report section after receiving feedback for report we need to standardise our requirements add in new requirements for the new database actor we also have to standardise the format of the requirements | 0 |
49,732 | 26,279,445,443 | IssuesEvent | 2023-01-07 05:46:15 | tailscale/tailscale | https://api.github.com/repos/tailscale/tailscale | closed | tailscale exit node breaks Happy Eyeballs on MacOS and iOS (rfc6555) | connectivity L5 All users P1 Nuisance T3 Performance/Debugging | When using a dual stacked exit node, tailscale breaks Happy Eyeballs (at least on the mac). A test that was used to fix iOS and MacOS's Happy Eyeballs implementation years ago is located here:
http://he.test-ipv6.com/
As you can see with my results from test-ipv6.com, I have IPv6 connectivity but MacOS isn't using it. It seems something you're doing with Magic DNS is causing the AAAA records to be delayed and the OS preferring IPv4.
[Test your IPv6_.pdf](https://github.com/tailscale/tailscale/files/6746041/Test.your.IPv6_.pdf)
[Test your Happy Eyeballs_.pdf](https://github.com/tailscale/tailscale/files/6746042/Test.your.Happy.Eyeballs_.pdf)
| True | tailscale exit node breaks Happy Eyeballs on MacOS and iOS (rfc6555) - When using a dual stacked exit node, tailscale breaks Happy Eyeballs (at least on the mac). A test that was used to fix iOS and MacOS's Happy Eyeballs implementation years ago is located here:
http://he.test-ipv6.com/
As you can see with my results from test-ipv6.com, I have IPv6 connectivity but MacOS isn't using it. It seems something you're doing with Magic DNS is causing the AAAA records to be delayed and the OS preferring IPv4.
[Test your IPv6_.pdf](https://github.com/tailscale/tailscale/files/6746041/Test.your.IPv6_.pdf)
[Test your Happy Eyeballs_.pdf](https://github.com/tailscale/tailscale/files/6746042/Test.your.Happy.Eyeballs_.pdf)
| non_priority | tailscale exit node breaks happy eyeballs on macos and ios when using a dual stacked exit node tailscale breaks happy eyeballs at least on the mac a test that was used to fix ios and macos s happy eyeballs implementation years ago is located here as you can see with my results from test com i have connectivity but macos isn t using it it seems something you re doing with magic dns is causing the aaaa records to be delayed and the os preferring | 0 |
53,462 | 28,136,798,797 | IssuesEvent | 2023-04-01 13:27:02 | vitejs/vite | https://api.github.com/repos/vitejs/vite | closed | Vite 2.7.x is about 1.9 to 6.2 times slower than 2.6.14 | has pr p4-important :exclamation: performance | ### Describe the bug
When upgrading from vite 2.6.14 to 2.7.x the development build performance is about 6.2 times slower on Windows and 1.9 times slower on Ubuntu 20.04 running in WSL2.
Results in seconds on Windows 10:
2.6.14: 12, 7, 7, 6, 6
2.7.1: 46, 47, 46, 47, 48
2.7 is about 6.2 times slower.
Results on Ubuntu 20.04 in WSL2:
2.6.14: 3, 4, 4, 4, 4
2.7.1: 7, 7, 8, 8, 6
2.7 is about 1.9 times slower.
> Times rounded to nearest second.
### Reproduction
Example repo: https://github.com/Lani/vite-2.7-slow
Steps to reproduce:
1. `npm i`
2. `npm run dev -- --force`
> Use --force to always start without the cache
### System Info
Windows
```shell
System:
OS: Windows 10 10.0.19042
CPU: (8) x64 Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
Memory: 20.85 GB / 39.75 GB
Binaries:
Node: 14.15.4 - C:\Tools\nodejs\node.EXE
npm: 6.14.10 - C:\Tools\nodejs\npm.CMD
Browsers:
Chrome: 96.0.4664.93
Edge: Spartan (44.19041.1266.0), Chromium (96.0.1054.43)
Internet Explorer: 11.0.19041.1202
npmPackages:
@vitejs/plugin-react: ^1.1.0 => 1.1.1
vite: ^2.7.1 => 2.7.1
```
Ubuntu:
```
System:
OS: Linux 4.19 Ubuntu 20.04.3 LTS (Focal Fossa)
CPU: (8) x64 Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
Memory: 30.14 GB / 31.17 GB
Container: Yes
Shell: 5.0.17 - /bin/bash
Binaries:
Node: 14.15.4 - ~/.nvm/versions/node/v14.15.4/bin/node
npm: 7.24.1 - ~/.nvm/versions/node/v14.15.4/bin/npm
npmPackages:
@vitejs/plugin-react: ^1.1.0 => 1.1.1
vite: ^2.7.1 => 2.7.1
```
### Used Package Manager
npm
> No notable difference when using pnpm instead of npm.
### Logs
Windows log:
```shell
vite:config bundled config file loaded in 425.78ms +0ms
vite:config using resolved config: {
vite:config plugins: [
vite:config 'vite:pre-alias',
vite:config 'alias',
vite:config 'vite:react-babel',
vite:config 'vite:react-refresh',
vite:config 'vite:react-jsx',
vite:config 'vite:modulepreload-polyfill',
vite:config 'vite:resolve',
vite:config 'vite:html-inline-script-proxy',
vite:config 'vite:css',
vite:config 'vite:esbuild',
vite:config 'vite:json',
vite:config 'vite:wasm',
vite:config 'vite:worker',
vite:config 'vite:asset',
vite:config 'vite:define',
vite:config 'vite:css-post',
vite:config 'vite:client-inject',
vite:config 'vite:import-analysis'
vite:config ],
vite:config server: { force: true, fs: { strict: true, allow: [Array], deny: [Array] } },
vite:config resolve: { dedupe: [ 'react', 'react-dom' ], alias: [ [Object], [Object] ] },
vite:config optimizeDeps: {
vite:config include: [ 'react/jsx-dev-runtime' ],
vite:config esbuildOptions: { keepNames: undefined, preserveSymlinks: undefined }
vite:config },
vite:config configFile: 'C:/code/_labs/vite-default/vite.config.ts',
vite:config configFileDependencies: [ 'vite.config.ts' ],
vite:config inlineConfig: {
vite:config root: undefined,
vite:config base: undefined,
vite:config mode: undefined,
vite:config configFile: undefined,
vite:config logLevel: undefined,
vite:config clearScreen: undefined,
vite:config server: { force: true, fs: [Object] }
vite:config },
vite:config root: 'C:/code/_labs/vite-default',
vite:config base: '/',
vite:config publicDir: 'C:\\code\\_labs\\vite-default\\public',
vite:config cacheDir: 'C:\\code\\_labs\\vite-default\\node_modules\\.vite',
vite:config command: 'serve',
vite:config mode: 'development',
vite:config isProduction: false,
vite:config build: {
vite:config target: [ 'es2019', 'edge88', 'firefox78', 'chrome87', 'safari13.1' ],
vite:config polyfillModulePreload: true,
vite:config outDir: 'C:\\code\\_labs\\vite-default\\dist',
vite:config assetsDir: 'assets',
vite:config assetsInlineLimit: 4096,
vite:config cssCodeSplit: true,
vite:config cssTarget: [ 'es2019', 'edge88', 'firefox78', 'chrome87', 'safari13.1' ],
vite:config sourcemap: false,
vite:config rollupOptions: { input: 'C:\\code\\_labs\\vite-default\\index.html' },
vite:config minify: 'esbuild',
vite:config terserOptions: {},
vite:config write: true,
vite:config emptyOutDir: null,
vite:config manifest: false,
vite:config lib: false,
vite:config ssr: false,
vite:config ssrManifest: false,
vite:config reportCompressedSize: true,
vite:config chunkSizeWarningLimit: 500,
vite:config watch: null,
vite:config commonjsOptions: { include: [Array], extensions: [Array] },
vite:config dynamicImportVarsOptions: { warnOnError: true, exclude: [Array] }
vite:config },
vite:config preview: {
vite:config port: undefined,
vite:config strictPort: undefined,
vite:config host: undefined,
vite:config https: undefined,
vite:config open: undefined,
vite:config proxy: undefined,
vite:config cors: undefined
vite:config },
vite:config env: { BASE_URL: '/', MODE: 'development', DEV: true, PROD: false },
vite:config assetsInclude: [Function: assetsInclude],
vite:config logger: {
vite:config hasWarned: false,
vite:config info: [Function: info],
vite:config warn: [Function: warn],
vite:config warnOnce: [Function: warnOnce],
vite:config error: [Function: error],
vite:config clearScreen: [Function: clearScreen],
vite:config hasErrorLogged: [Function: hasErrorLogged]
vite:config },
vite:config packageCache: Map(0) {},
vite:config createResolver: [Function: createResolver]
vite:config } +13ms
vite:deps Crawling dependencies using entries:
vite:deps C:\code\_labs\vite-default\index.html +0ms
vite:resolve 4.14ms C:\code\_labs\vite-default\index.html -> C:/code/_labs/vite-default/index.html +0ms
vite:resolve 1.17ms /src/main.tsx -> C:/code/_labs/vite-default/src/main.tsx +29ms
vite:resolve 7.34ms react -> C:/code/_labs/vite-default/node_modules/react/index.js +13ms
vite:resolve 5.92ms react-dom -> C:/code/_labs/vite-default/node_modules/react-dom/index.js +7ms
vite:resolve 2.83ms ./App -> C:/code/_labs/vite-default/src/App.tsx +16ms
vite:resolve 5.57ms @mui/material -> C:/code/_labs/vite-default/node_modules/@mui/material/index.js +10ms
vite:resolve 3.88ms @mui/icons-material -> C:/code/_labs/vite-default/node_modules/@mui/icons-material/esm/index.js +7ms
vite:resolve 4.01ms @mui/styles -> C:/code/_labs/vite-default/node_modules/@mui/styles/index.js +8ms
vite:deps Scan completed in 119.05ms: {
react: 'C:/code/_labs/vite-default/node_modules/react/index.js',
'react-dom': 'C:/code/_labs/vite-default/node_modules/react-dom/index.js',
'@mui/material': 'C:/code/_labs/vite-default/node_modules/@mui/material/index.js',
'@mui/icons-material': 'C:/code/_labs/vite-default/node_modules/@mui/icons-material/esm/index.js',
'@mui/styles': 'C:/code/_labs/vite-default/node_modules/@mui/styles/index.js'
} +118ms
vite:resolve 4.99ms react/jsx-dev-runtime -> C:/code/_labs/vite-default/node_modules/react/jsx-dev-runtime.js +0ms
Pre-bundling dependencies:
react
react-dom
@mui/material
@mui/icons-material
@mui/styles
(...and 1 more)
(this will be run only when your dependencies or config have changed)
vite:resolve 5.53ms @mui/utils -> C:/code/_labs/vite-default/node_modules/@mui/utils/esm/index.js +0ms
vite:resolve 5.85ms object-assign -> C:/code/_labs/vite-default/node_modules/object-assign/index.js +0ms
vite:resolve 13.07ms react -> C:/code/_labs/vite-default/node_modules/react/index.js +14ms
vite:resolve 13.49ms @mui/base -> C:/code/_labs/vite-default/node_modules/@mui/base/index.js +28ms
vite:resolve 7.06ms scheduler -> C:/code/_labs/vite-default/node_modules/scheduler/index.js +67ms
vite:resolve 36.15ms @mui/private-theming/useTheme -> C:/code/_labs/vite-default/node_modules/@mui/private-theming/useTheme/index.js +103ms
vite:resolve 36.49ms @babel/runtime/helpers/esm/extends -> C:/code/_labs/vite-default/node_modules/@babel/runtime/helpers/esm/extends.js +0ms
vite:resolve 36.84ms @mui/private-theming/ThemeProvider -> C:/code/_labs/vite-default/node_modules/@mui/private-theming/ThemeProvider/index.js +1ms
vite:resolve 37.34ms jss-plugin-rule-value-function -> C:/code/_labs/vite-default/node_modules/jss-plugin-rule-value-function/dist/jss-plugin-rule-value-function.esm.js +1ms
vite:resolve 64.19ms scheduler/tracing -> C:/code/_labs/vite-default/node_modules/scheduler/tracing.js +104ms
vite:resolve 64.44ms @babel/runtime/helpers/esm/objectWithoutPropertiesLoose -> C:/code/_labs/vite-default/node_modules/@babel/runtime/helpers/esm/objectWithoutPropertiesLoose.js +66ms
vite:resolve 27.35ms jss-plugin-global -> C:/code/_labs/vite-default/node_modules/jss-plugin-global/dist/jss-plugin-global.esm.js +29ms
vite:resolve 27.70ms react -> C:/code/_labs/vite-default/node_modules/react/index.js +0ms
vite:resolve 132.77ms prop-types -> C:/code/_labs/vite-default/node_modules/prop-types/index.js +136ms
vite:resolve 132.74ms react-is -> C:/code/_labs/vite-default/node_modules/@mui/utils/node_modules/react-is/index.js +1ms
vite:resolve 43.22ms jss-plugin-nested -> C:/code/_labs/vite-default/node_modules/jss-plugin-nested/dist/jss-plugin-nested.esm.js +49ms
vite:resolve 42.98ms hoist-non-react-statics -> C:/code/_labs/vite-default/node_modules/hoist-non-react-statics/dist/hoist-non-react-statics.cjs.js +1ms vite:resolve 43.09ms jss -> C:/code/_labs/vite-default/node_modules/jss/dist/jss.esm.js +0ms
vite:resolve 43.46ms react-is -> C:/code/_labs/vite-default/node_modules/react-is/index.js +218ms
vite:resolve 25.53ms clsx -> C:/code/_labs/vite-default/node_modules/clsx/dist/clsx.m.js +35ms
vite:resolve 26.06ms jss-plugin-camel-case -> C:/code/_labs/vite-default/node_modules/jss-plugin-camel-case/dist/jss-plugin-camel-case.esm.js +1ms
vite:resolve 21.24ms react/jsx-runtime -> C:/code/_labs/vite-default/node_modules/react/jsx-runtime.js +24ms
vite:resolve 23.80ms jss-plugin-default-unit -> C:/code/_labs/vite-default/node_modules/jss-plugin-default-unit/dist/jss-plugin-default-unit.esm.js +25ms
vite:resolve 285.33ms @mui/base/ModalUnstyled -> C:/code/_labs/vite-default/node_modules/@mui/base/ModalUnstyled/index.js +339ms
vite:resolve 284.60ms @mui/base/TextareaAutosize -> C:/code/_labs/vite-default/node_modules/@mui/base/TextareaAutosize/index.js +1ms
vite:resolve 284.97ms @mui/base/NoSsr -> C:/code/_labs/vite-default/node_modules/@mui/base/NoSsr/index.js +0ms
vite:resolve 284.94ms jss-plugin-vendor-prefixer -> C:/code/_labs/vite-default/node_modules/jss-plugin-vendor-prefixer/dist/jss-plugin-vendor-prefixer.esm.js +1ms
vite:resolve 284.71ms @mui/base/ClickAwayListener -> C:/code/_labs/vite-default/node_modules/@mui/base/ClickAwayListener/index.js +1ms
vite:resolve 284.78ms @mui/system -> C:/code/_labs/vite-default/node_modules/@mui/system/esm/index.js +1ms
vite:resolve 285.49ms @mui/base/AutocompleteUnstyled -> C:/code/_labs/vite-default/node_modules/@mui/base/AutocompleteUnstyled/index.js +1ms
vite:resolve 1053.37ms is-in-browser -> C:/code/_labs/vite-default/node_modules/is-in-browser/dist/module.js +1s
vite:resolve 1387.42ms jss-plugin-props-sort -> C:/code/_labs/vite-default/node_modules/jss-plugin-props-sort/dist/jss-plugin-props-sort.esm.js +1s
vite:resolve 1385.79ms @mui/styled-engine -> C:/code/_labs/vite-default/node_modules/@mui/styled-engine/index.js +2ms
vite:resolve 720.73ms tiny-warning -> C:/code/_labs/vite-default/node_modules/tiny-warning/dist/tiny-warning.esm.js +7s
vite:resolve 605.37ms react-dom -> C:/code/_labs/vite-default/node_modules/react-dom/index.js +610ms
vite:resolve 678.20ms css-vendor -> C:/code/_labs/vite-default/node_modules/css-vendor/dist/css-vendor.esm.js +3s
vite:resolve 678.36ms @mui/material/utils -> C:/code/_labs/vite-default/node_modules/@mui/material/utils/index.js +0ms
vite:resolve 687.91ms hyphenate-style-name -> C:/code/_labs/vite-default/node_modules/hyphenate-style-name/index.js +697ms
vite:resolve 602.13ms @emotion/styled -> C:/code/_labs/vite-default/node_modules/@emotion/styled/dist/emotion-styled.browser.esm.js +24s
vite:resolve 602.50ms @mui/private-theming -> C:/code/_labs/vite-default/node_modules/@mui/private-theming/index.js +1ms
vite:resolve 600.95ms @babel/runtime/helpers/esm/createClass -> C:/code/_labs/vite-default/node_modules/@babel/runtime/helpers/esm/createClass.js +1ms
vite:resolve 428.78ms react-is -> C:/code/_labs/vite-default/node_modules/@mui/material/node_modules/react-is/index.js +434ms
vite:resolve 429.25ms @mui/base/PopperUnstyled -> C:/code/_labs/vite-default/node_modules/@mui/base/PopperUnstyled/index.js +0ms
vite:resolve 578.98ms @emotion/react -> C:/code/_labs/vite-default/node_modules/@emotion/react/dist/emotion-react.browser.esm.js +584ms
vite:resolve 576.90ms @babel/runtime/helpers/esm/inheritsLoose -> C:/code/_labs/vite-default/node_modules/@babel/runtime/helpers/esm/inheritsLoose.js +1ms
vite:resolve 568.55ms react-is -> C:/code/_labs/vite-default/node_modules/@mui/base/node_modules/react-is/index.js +1ms
vite:resolve 568.97ms @popperjs/core -> C:/code/_labs/vite-default/node_modules/@popperjs/core/lib/index.js +1ms
vite:resolve 568.87ms react-transition-group -> C:/code/_labs/vite-default/node_modules/react-transition-group/esm/index.js +1ms
vite:resolve 509.42ms @babel/runtime/helpers/esm/assertThisInitialized -> C:/code/_labs/vite-default/node_modules/@babel/runtime/helpers/esm/assertThisInitialized.js +520ms
vite:resolve 506.83ms @mui/base/BackdropUnstyled -> C:/code/_labs/vite-default/node_modules/@mui/base/BackdropUnstyled/index.js +1ms
vite:resolve 40.92ms @babel/runtime/helpers/esm/toConsumableArray -> C:/code/_labs/vite-default/node_modules/@babel/runtime/helpers/esm/toConsumableArray.js +44ms
vite:resolve 41.43ms @babel/runtime/helpers/extends -> C:/code/_labs/vite-default/node_modules/@babel/runtime/helpers/esm/extends.js +1ms
vite:resolve 25.99ms @emotion/cache -> C:/code/_labs/vite-default/node_modules/@emotion/cache/dist/emotion-cache.browser.esm.js +638ms
vite:resolve 553.07ms @mui/base/BadgeUnstyled -> C:/code/_labs/vite-default/node_modules/@mui/base/BadgeUnstyled/index.js +556ms
vite:resolve 553.73ms @mui/base/SliderUnstyled -> C:/code/_labs/vite-default/node_modules/@mui/base/SliderUnstyled/index.js +1ms
vite:resolve 553.83ms @mui/base/composeClasses -> C:/code/_labs/vite-default/node_modules/@mui/base/composeClasses/index.js +1ms
vite:resolve 48.05ms @emotion/is-prop-valid -> C:/code/_labs/vite-default/node_modules/@emotion/is-prop-valid/dist/emotion-is-prop-valid.browser.esm.js
+50ms
vite:resolve 27.83ms @emotion/weak-memoize -> C:/code/_labs/vite-default/node_modules/@emotion/weak-memoize/dist/weak-memoize.browser.esm.js +491ms
vite:resolve 17.80ms @emotion/utils -> C:/code/_labs/vite-default/node_modules/@emotion/utils/dist/emotion-utils.browser.esm.js +334ms
vite:resolve 16.58ms @emotion/serialize -> C:/code/_labs/vite-default/node_modules/@emotion/serialize/dist/emotion-serialize.browser.esm.js +171ms
vite:resolve 17.06ms @emotion/sheet -> C:/code/_labs/vite-default/node_modules/@emotion/sheet/dist/emotion-sheet.browser.esm.js +0ms
vite:resolve 107.55ms dom-helpers/addClass -> C:/code/_labs/vite-default/node_modules/dom-helpers/esm/addClass.js +109ms
vite:resolve 42.02ms stylis -> C:/code/_labs/vite-default/node_modules/stylis/index.js +44ms
vite:resolve 42.49ms @emotion/memoize -> C:/code/_labs/vite-default/node_modules/@emotion/memoize/dist/emotion-memoize.browser.esm.js +1ms
vite:resolve 42.84ms @emotion/hash -> C:/code/_labs/vite-default/node_modules/@emotion/hash/dist/hash.browser.esm.js +0ms
vite:resolve 73.63ms dom-helpers/removeClass -> C:/code/_labs/vite-default/node_modules/dom-helpers/esm/removeClass.js +75ms
vite:resolve 19.93ms @emotion/unitless -> C:/code/_labs/vite-default/node_modules/@emotion/unitless/dist/unitless.browser.esm.js +22ms
vite:deps deps bundled in 44638.17ms +0ms
vite v2.7.1 dev server running at:
> Local: http://localhost:3000/
> Network: use `--host` to expose
ready in 45672ms.
```
```
### Validations
- [X] Follow our [Code of Conduct](https://github.com/vitejs/vite/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guidelines](https://github.com/vitejs/vite/blob/main/CONTRIBUTING.md).
- [X] Read the [docs](https://vitejs.dev/guide).
- [X] Check that there isn't [already an issue](https://github.com/vitejs/vite/issues) that reports the same bug to avoid creating a duplicate.
- [X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/vitejs/vite/discussions) or join our [Discord Chat Server](https://chat.vitejs.dev/).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.
``` | True | Vite 2.7.x is about 1.9 to 6.2 times slower than 2.6.14 - ### Describe the bug
When upgrading from vite 2.6.14 to 2.7.x the development build performance is about 6.2 times slower on Windows and 1.9 times slower on Ubuntu 20.04 running in WSL2.
Results in seconds on Windows 10:
2.6.14: 12, 7, 7, 6, 6
2.7.1: 46, 47, 46, 47, 48
2.7 is about 6.2 times slower.
Results on Ubuntu 20.04 in WSL2:
2.6.14: 3, 4, 4, 4, 4
2.7.1: 7, 7, 8, 8, 6
2.7 is about 1.9 times slower.
> Times rounded to nearest second.
### Reproduction
Example repo: https://github.com/Lani/vite-2.7-slow
Steps to reproduce:
1. `npm i`
2. `npm run dev -- --force`
> Use --force to always start without the cache
### System Info
Windows
```shell
System:
OS: Windows 10 10.0.19042
CPU: (8) x64 Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
Memory: 20.85 GB / 39.75 GB
Binaries:
Node: 14.15.4 - C:\Tools\nodejs\node.EXE
npm: 6.14.10 - C:\Tools\nodejs\npm.CMD
Browsers:
Chrome: 96.0.4664.93
Edge: Spartan (44.19041.1266.0), Chromium (96.0.1054.43)
Internet Explorer: 11.0.19041.1202
npmPackages:
@vitejs/plugin-react: ^1.1.0 => 1.1.1
vite: ^2.7.1 => 2.7.1
```
Ubuntu:
```
System:
OS: Linux 4.19 Ubuntu 20.04.3 LTS (Focal Fossa)
CPU: (8) x64 Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
Memory: 30.14 GB / 31.17 GB
Container: Yes
Shell: 5.0.17 - /bin/bash
Binaries:
Node: 14.15.4 - ~/.nvm/versions/node/v14.15.4/bin/node
npm: 7.24.1 - ~/.nvm/versions/node/v14.15.4/bin/npm
npmPackages:
@vitejs/plugin-react: ^1.1.0 => 1.1.1
vite: ^2.7.1 => 2.7.1
```
### Used Package Manager
npm
> No notable difference when using pnpm instead of npm.
### Logs
Windows log:
```shell
vite:config bundled config file loaded in 425.78ms +0ms
vite:config using resolved config: {
vite:config plugins: [
vite:config 'vite:pre-alias',
vite:config 'alias',
vite:config 'vite:react-babel',
vite:config 'vite:react-refresh',
vite:config 'vite:react-jsx',
vite:config 'vite:modulepreload-polyfill',
vite:config 'vite:resolve',
vite:config 'vite:html-inline-script-proxy',
vite:config 'vite:css',
vite:config 'vite:esbuild',
vite:config 'vite:json',
vite:config 'vite:wasm',
vite:config 'vite:worker',
vite:config 'vite:asset',
vite:config 'vite:define',
vite:config 'vite:css-post',
vite:config 'vite:client-inject',
vite:config 'vite:import-analysis'
vite:config ],
vite:config server: { force: true, fs: { strict: true, allow: [Array], deny: [Array] } },
vite:config resolve: { dedupe: [ 'react', 'react-dom' ], alias: [ [Object], [Object] ] },
vite:config optimizeDeps: {
vite:config include: [ 'react/jsx-dev-runtime' ],
vite:config esbuildOptions: { keepNames: undefined, preserveSymlinks: undefined }
vite:config },
vite:config configFile: 'C:/code/_labs/vite-default/vite.config.ts',
vite:config configFileDependencies: [ 'vite.config.ts' ],
vite:config inlineConfig: {
vite:config root: undefined,
vite:config base: undefined,
vite:config mode: undefined,
vite:config configFile: undefined,
vite:config logLevel: undefined,
vite:config clearScreen: undefined,
vite:config server: { force: true, fs: [Object] }
vite:config },
vite:config root: 'C:/code/_labs/vite-default',
vite:config base: '/',
vite:config publicDir: 'C:\\code\\_labs\\vite-default\\public',
vite:config cacheDir: 'C:\\code\\_labs\\vite-default\\node_modules\\.vite',
vite:config command: 'serve',
vite:config mode: 'development',
vite:config isProduction: false,
vite:config build: {
vite:config target: [ 'es2019', 'edge88', 'firefox78', 'chrome87', 'safari13.1' ],
vite:config polyfillModulePreload: true,
vite:config outDir: 'C:\\code\\_labs\\vite-default\\dist',
vite:config assetsDir: 'assets',
vite:config assetsInlineLimit: 4096,
vite:config cssCodeSplit: true,
vite:config cssTarget: [ 'es2019', 'edge88', 'firefox78', 'chrome87', 'safari13.1' ],
vite:config sourcemap: false,
vite:config rollupOptions: { input: 'C:\\code\\_labs\\vite-default\\index.html' },
vite:config minify: 'esbuild',
vite:config terserOptions: {},
vite:config write: true,
vite:config emptyOutDir: null,
vite:config manifest: false,
vite:config lib: false,
vite:config ssr: false,
vite:config ssrManifest: false,
vite:config reportCompressedSize: true,
vite:config chunkSizeWarningLimit: 500,
vite:config watch: null,
vite:config commonjsOptions: { include: [Array], extensions: [Array] },
vite:config dynamicImportVarsOptions: { warnOnError: true, exclude: [Array] }
vite:config },
vite:config preview: {
vite:config port: undefined,
vite:config strictPort: undefined,
vite:config host: undefined,
vite:config https: undefined,
vite:config open: undefined,
vite:config proxy: undefined,
vite:config cors: undefined
vite:config },
vite:config env: { BASE_URL: '/', MODE: 'development', DEV: true, PROD: false },
vite:config assetsInclude: [Function: assetsInclude],
vite:config logger: {
vite:config hasWarned: false,
vite:config info: [Function: info],
vite:config warn: [Function: warn],
vite:config warnOnce: [Function: warnOnce],
vite:config error: [Function: error],
vite:config clearScreen: [Function: clearScreen],
vite:config hasErrorLogged: [Function: hasErrorLogged]
vite:config },
vite:config packageCache: Map(0) {},
vite:config createResolver: [Function: createResolver]
vite:config } +13ms
vite:deps Crawling dependencies using entries:
vite:deps C:\code\_labs\vite-default\index.html +0ms
vite:resolve 4.14ms C:\code\_labs\vite-default\index.html -> C:/code/_labs/vite-default/index.html +0ms
vite:resolve 1.17ms /src/main.tsx -> C:/code/_labs/vite-default/src/main.tsx +29ms
vite:resolve 7.34ms react -> C:/code/_labs/vite-default/node_modules/react/index.js +13ms
vite:resolve 5.92ms react-dom -> C:/code/_labs/vite-default/node_modules/react-dom/index.js +7ms
vite:resolve 2.83ms ./App -> C:/code/_labs/vite-default/src/App.tsx +16ms
vite:resolve 5.57ms @mui/material -> C:/code/_labs/vite-default/node_modules/@mui/material/index.js +10ms
vite:resolve 3.88ms @mui/icons-material -> C:/code/_labs/vite-default/node_modules/@mui/icons-material/esm/index.js +7ms
vite:resolve 4.01ms @mui/styles -> C:/code/_labs/vite-default/node_modules/@mui/styles/index.js +8ms
vite:deps Scan completed in 119.05ms: {
react: 'C:/code/_labs/vite-default/node_modules/react/index.js',
'react-dom': 'C:/code/_labs/vite-default/node_modules/react-dom/index.js',
'@mui/material': 'C:/code/_labs/vite-default/node_modules/@mui/material/index.js',
'@mui/icons-material': 'C:/code/_labs/vite-default/node_modules/@mui/icons-material/esm/index.js',
'@mui/styles': 'C:/code/_labs/vite-default/node_modules/@mui/styles/index.js'
} +118ms
vite:resolve 4.99ms react/jsx-dev-runtime -> C:/code/_labs/vite-default/node_modules/react/jsx-dev-runtime.js +0ms
Pre-bundling dependencies:
react
react-dom
@mui/material
@mui/icons-material
@mui/styles
(...and 1 more)
(this will be run only when your dependencies or config have changed)
vite:resolve 5.53ms @mui/utils -> C:/code/_labs/vite-default/node_modules/@mui/utils/esm/index.js +0ms
vite:resolve 5.85ms object-assign -> C:/code/_labs/vite-default/node_modules/object-assign/index.js +0ms
vite:resolve 13.07ms react -> C:/code/_labs/vite-default/node_modules/react/index.js +14ms
vite:resolve 13.49ms @mui/base -> C:/code/_labs/vite-default/node_modules/@mui/base/index.js +28ms
vite:resolve 7.06ms scheduler -> C:/code/_labs/vite-default/node_modules/scheduler/index.js +67ms
vite:resolve 36.15ms @mui/private-theming/useTheme -> C:/code/_labs/vite-default/node_modules/@mui/private-theming/useTheme/index.js +103ms
vite:resolve 36.49ms @babel/runtime/helpers/esm/extends -> C:/code/_labs/vite-default/node_modules/@babel/runtime/helpers/esm/extends.js +0ms
vite:resolve 36.84ms @mui/private-theming/ThemeProvider -> C:/code/_labs/vite-default/node_modules/@mui/private-theming/ThemeProvider/index.js +1ms
vite:resolve 37.34ms jss-plugin-rule-value-function -> C:/code/_labs/vite-default/node_modules/jss-plugin-rule-value-function/dist/jss-plugin-rule-value-function.esm.js +1ms
vite:resolve 64.19ms scheduler/tracing -> C:/code/_labs/vite-default/node_modules/scheduler/tracing.js +104ms
vite:resolve 64.44ms @babel/runtime/helpers/esm/objectWithoutPropertiesLoose -> C:/code/_labs/vite-default/node_modules/@babel/runtime/helpers/esm/objectWithoutPropertiesLoose.js +66ms
vite:resolve 27.35ms jss-plugin-global -> C:/code/_labs/vite-default/node_modules/jss-plugin-global/dist/jss-plugin-global.esm.js +29ms
vite:resolve 27.70ms react -> C:/code/_labs/vite-default/node_modules/react/index.js +0ms
vite:resolve 132.77ms prop-types -> C:/code/_labs/vite-default/node_modules/prop-types/index.js +136ms
vite:resolve 132.74ms react-is -> C:/code/_labs/vite-default/node_modules/@mui/utils/node_modules/react-is/index.js +1ms
vite:resolve 43.22ms jss-plugin-nested -> C:/code/_labs/vite-default/node_modules/jss-plugin-nested/dist/jss-plugin-nested.esm.js +49ms
vite:resolve 42.98ms hoist-non-react-statics -> C:/code/_labs/vite-default/node_modules/hoist-non-react-statics/dist/hoist-non-react-statics.cjs.js +1ms vite:resolve 43.09ms jss -> C:/code/_labs/vite-default/node_modules/jss/dist/jss.esm.js +0ms
vite:resolve 43.46ms react-is -> C:/code/_labs/vite-default/node_modules/react-is/index.js +218ms
vite:resolve 25.53ms clsx -> C:/code/_labs/vite-default/node_modules/clsx/dist/clsx.m.js +35ms
vite:resolve 26.06ms jss-plugin-camel-case -> C:/code/_labs/vite-default/node_modules/jss-plugin-camel-case/dist/jss-plugin-camel-case.esm.js +1ms
vite:resolve 21.24ms react/jsx-runtime -> C:/code/_labs/vite-default/node_modules/react/jsx-runtime.js +24ms
vite:resolve 23.80ms jss-plugin-default-unit -> C:/code/_labs/vite-default/node_modules/jss-plugin-default-unit/dist/jss-plugin-default-unit.esm.js +25ms
vite:resolve 285.33ms @mui/base/ModalUnstyled -> C:/code/_labs/vite-default/node_modules/@mui/base/ModalUnstyled/index.js +339ms
vite:resolve 284.60ms @mui/base/TextareaAutosize -> C:/code/_labs/vite-default/node_modules/@mui/base/TextareaAutosize/index.js +1ms
vite:resolve 284.97ms @mui/base/NoSsr -> C:/code/_labs/vite-default/node_modules/@mui/base/NoSsr/index.js +0ms
vite:resolve 284.94ms jss-plugin-vendor-prefixer -> C:/code/_labs/vite-default/node_modules/jss-plugin-vendor-prefixer/dist/jss-plugin-vendor-prefixer.esm.js +1ms
vite:resolve 284.71ms @mui/base/ClickAwayListener -> C:/code/_labs/vite-default/node_modules/@mui/base/ClickAwayListener/index.js +1ms
vite:resolve 284.78ms @mui/system -> C:/code/_labs/vite-default/node_modules/@mui/system/esm/index.js +1ms
vite:resolve 285.49ms @mui/base/AutocompleteUnstyled -> C:/code/_labs/vite-default/node_modules/@mui/base/AutocompleteUnstyled/index.js +1ms
vite:resolve 1053.37ms is-in-browser -> C:/code/_labs/vite-default/node_modules/is-in-browser/dist/module.js +1s
vite:resolve 1387.42ms jss-plugin-props-sort -> C:/code/_labs/vite-default/node_modules/jss-plugin-props-sort/dist/jss-plugin-props-sort.esm.js +1s
vite:resolve 1385.79ms @mui/styled-engine -> C:/code/_labs/vite-default/node_modules/@mui/styled-engine/index.js +2ms
vite:resolve 720.73ms tiny-warning -> C:/code/_labs/vite-default/node_modules/tiny-warning/dist/tiny-warning.esm.js +7s
vite:resolve 605.37ms react-dom -> C:/code/_labs/vite-default/node_modules/react-dom/index.js +610ms
vite:resolve 678.20ms css-vendor -> C:/code/_labs/vite-default/node_modules/css-vendor/dist/css-vendor.esm.js +3s
vite:resolve 678.36ms @mui/material/utils -> C:/code/_labs/vite-default/node_modules/@mui/material/utils/index.js +0ms
vite:resolve 687.91ms hyphenate-style-name -> C:/code/_labs/vite-default/node_modules/hyphenate-style-name/index.js +697ms
vite:resolve 602.13ms @emotion/styled -> C:/code/_labs/vite-default/node_modules/@emotion/styled/dist/emotion-styled.browser.esm.js +24s
vite:resolve 602.50ms @mui/private-theming -> C:/code/_labs/vite-default/node_modules/@mui/private-theming/index.js +1ms
vite:resolve 600.95ms @babel/runtime/helpers/esm/createClass -> C:/code/_labs/vite-default/node_modules/@babel/runtime/helpers/esm/createClass.js +1ms
vite:resolve 428.78ms react-is -> C:/code/_labs/vite-default/node_modules/@mui/material/node_modules/react-is/index.js +434ms
vite:resolve 429.25ms @mui/base/PopperUnstyled -> C:/code/_labs/vite-default/node_modules/@mui/base/PopperUnstyled/index.js +0ms
vite:resolve 578.98ms @emotion/react -> C:/code/_labs/vite-default/node_modules/@emotion/react/dist/emotion-react.browser.esm.js +584ms
vite:resolve 576.90ms @babel/runtime/helpers/esm/inheritsLoose -> C:/code/_labs/vite-default/node_modules/@babel/runtime/helpers/esm/inheritsLoose.js +1ms
vite:resolve 568.55ms react-is -> C:/code/_labs/vite-default/node_modules/@mui/base/node_modules/react-is/index.js +1ms
vite:resolve 568.97ms @popperjs/core -> C:/code/_labs/vite-default/node_modules/@popperjs/core/lib/index.js +1ms
vite:resolve 568.87ms react-transition-group -> C:/code/_labs/vite-default/node_modules/react-transition-group/esm/index.js +1ms
vite:resolve 509.42ms @babel/runtime/helpers/esm/assertThisInitialized -> C:/code/_labs/vite-default/node_modules/@babel/runtime/helpers/esm/assertThisInitialized.js +520ms
vite:resolve 506.83ms @mui/base/BackdropUnstyled -> C:/code/_labs/vite-default/node_modules/@mui/base/BackdropUnstyled/index.js +1ms
vite:resolve 40.92ms @babel/runtime/helpers/esm/toConsumableArray -> C:/code/_labs/vite-default/node_modules/@babel/runtime/helpers/esm/toConsumableArray.js +44ms
vite:resolve 41.43ms @babel/runtime/helpers/extends -> C:/code/_labs/vite-default/node_modules/@babel/runtime/helpers/esm/extends.js +1ms
vite:resolve 25.99ms @emotion/cache -> C:/code/_labs/vite-default/node_modules/@emotion/cache/dist/emotion-cache.browser.esm.js +638ms
vite:resolve 553.07ms @mui/base/BadgeUnstyled -> C:/code/_labs/vite-default/node_modules/@mui/base/BadgeUnstyled/index.js +556ms
vite:resolve 553.73ms @mui/base/SliderUnstyled -> C:/code/_labs/vite-default/node_modules/@mui/base/SliderUnstyled/index.js +1ms
vite:resolve 553.83ms @mui/base/composeClasses -> C:/code/_labs/vite-default/node_modules/@mui/base/composeClasses/index.js +1ms
vite:resolve 48.05ms @emotion/is-prop-valid -> C:/code/_labs/vite-default/node_modules/@emotion/is-prop-valid/dist/emotion-is-prop-valid.browser.esm.js
+50ms
vite:resolve 27.83ms @emotion/weak-memoize -> C:/code/_labs/vite-default/node_modules/@emotion/weak-memoize/dist/weak-memoize.browser.esm.js +491ms
vite:resolve 17.80ms @emotion/utils -> C:/code/_labs/vite-default/node_modules/@emotion/utils/dist/emotion-utils.browser.esm.js +334ms
vite:resolve 16.58ms @emotion/serialize -> C:/code/_labs/vite-default/node_modules/@emotion/serialize/dist/emotion-serialize.browser.esm.js +171ms
vite:resolve 17.06ms @emotion/sheet -> C:/code/_labs/vite-default/node_modules/@emotion/sheet/dist/emotion-sheet.browser.esm.js +0ms
vite:resolve 107.55ms dom-helpers/addClass -> C:/code/_labs/vite-default/node_modules/dom-helpers/esm/addClass.js +109ms
vite:resolve 42.02ms stylis -> C:/code/_labs/vite-default/node_modules/stylis/index.js +44ms
vite:resolve 42.49ms @emotion/memoize -> C:/code/_labs/vite-default/node_modules/@emotion/memoize/dist/emotion-memoize.browser.esm.js +1ms
vite:resolve 42.84ms @emotion/hash -> C:/code/_labs/vite-default/node_modules/@emotion/hash/dist/hash.browser.esm.js +0ms
vite:resolve 73.63ms dom-helpers/removeClass -> C:/code/_labs/vite-default/node_modules/dom-helpers/esm/removeClass.js +75ms
vite:resolve 19.93ms @emotion/unitless -> C:/code/_labs/vite-default/node_modules/@emotion/unitless/dist/unitless.browser.esm.js +22ms
vite:deps deps bundled in 44638.17ms +0ms
vite v2.7.1 dev server running at:
> Local: http://localhost:3000/
> Network: use `--host` to expose
ready in 45672ms.
```
```
### Validations
- [X] Follow our [Code of Conduct](https://github.com/vitejs/vite/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guidelines](https://github.com/vitejs/vite/blob/main/CONTRIBUTING.md).
- [X] Read the [docs](https://vitejs.dev/guide).
- [X] Check that there isn't [already an issue](https://github.com/vitejs/vite/issues) that reports the same bug to avoid creating a duplicate.
- [X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/vitejs/vite/discussions) or join our [Discord Chat Server](https://chat.vitejs.dev/).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.
``` | non_priority | vite x is about to times slower than describe the bug when upgrading from vite to x the development build performance is about times slower on windows and times slower on ubuntu running in results in seconds on windows is about times slower results on ubuntu in is about times slower times rounded to nearest second reproduction example repo steps to reproduce npm i npm run dev force use force to always start without the cache system info windows shell system os windows cpu intel r core tm cpu memory gb gb binaries node c tools nodejs node exe npm c tools nodejs npm cmd browsers chrome edge spartan chromium internet explorer npmpackages vitejs plugin react vite ubuntu system os linux ubuntu lts focal fossa cpu intel r core tm cpu memory gb gb container yes shell bin bash binaries node nvm versions node bin node npm nvm versions node bin npm npmpackages vitejs plugin react vite used package manager npm no notable difference when using pnpm instead of npm logs windows log shell vite config bundled config file loaded in vite config using resolved config vite config plugins vite config vite pre alias vite config alias vite config vite react babel vite config vite react refresh vite config vite react jsx vite config vite modulepreload polyfill vite config vite resolve vite config vite html inline script proxy vite config vite css vite config vite esbuild vite config vite json vite config vite wasm vite config vite worker vite config vite asset vite config vite define vite config vite css post vite config vite client inject vite config vite import analysis vite config vite config server force true fs strict true allow deny vite config resolve dedupe alias vite config optimizedeps vite config include vite config esbuildoptions keepnames undefined preservesymlinks undefined vite config vite config configfile c code labs vite default vite config ts vite config configfiledependencies vite config inlineconfig vite config root undefined vite config base undefined vite config mode undefined vite config configfile undefined vite config loglevel undefined vite config clearscreen undefined vite config server force true fs vite config vite config root c code labs vite default vite config base vite config publicdir c code labs vite default public vite config cachedir c code labs vite default node modules vite vite config command serve vite config mode development vite config isproduction false vite config build vite config target vite config polyfillmodulepreload true vite config outdir c code labs vite default dist vite config assetsdir assets vite config assetsinlinelimit vite config csscodesplit true vite config csstarget vite config sourcemap false vite config rollupoptions input c code labs vite default index html vite config minify esbuild vite config terseroptions vite config write true vite config emptyoutdir null vite config manifest false vite config lib false vite config ssr false vite config ssrmanifest false vite config reportcompressedsize true vite config chunksizewarninglimit vite config watch null vite config commonjsoptions include extensions vite config dynamicimportvarsoptions warnonerror true exclude vite config vite config preview vite config port undefined vite config strictport undefined vite config host undefined vite config https undefined vite config open undefined vite config proxy undefined vite config cors undefined vite config vite config env base url mode development dev true prod false vite config assetsinclude vite config logger vite config haswarned false vite config info vite config warn vite config warnonce vite config error vite config clearscreen vite config haserrorlogged vite config vite config packagecache map vite config createresolver vite config vite deps crawling dependencies using entries vite deps c code labs vite default index html vite resolve c code labs vite default index html c code labs vite default index html vite resolve src main tsx c code labs vite default src main tsx vite resolve react c code labs vite default node modules react index js vite resolve react dom c code labs vite default node modules react dom index js vite resolve app c code labs vite default src app tsx vite resolve mui material c code labs vite default node modules mui material index js vite resolve mui icons material c code labs vite default node modules mui icons material esm index js vite resolve mui styles c code labs vite default node modules mui styles index js vite deps scan completed in react c code labs vite default node modules react index js react dom c code labs vite default node modules react dom index js mui material c code labs vite default node modules mui material index js mui icons material c code labs vite default node modules mui icons material esm index js mui styles c code labs vite default node modules mui styles index js vite resolve react jsx dev runtime c code labs vite default node modules react jsx dev runtime js pre bundling dependencies react react dom mui material mui icons material mui styles and more this will be run only when your dependencies or config have changed vite resolve mui utils c code labs vite default node modules mui utils esm index js vite resolve object assign c code labs vite default node modules object assign index js vite resolve react c code labs vite default node modules react index js vite resolve mui base c code labs vite default node modules mui base index js vite resolve scheduler c code labs vite default node modules scheduler index js vite resolve mui private theming usetheme c code labs vite default node modules mui private theming usetheme index js vite resolve babel runtime helpers esm extends c code labs vite default node modules babel runtime helpers esm extends js vite resolve mui private theming themeprovider c code labs vite default node modules mui private theming themeprovider index js vite resolve jss plugin rule value function c code labs vite default node modules jss plugin rule value function dist jss plugin rule value function esm js vite resolve scheduler tracing c code labs vite default node modules scheduler tracing js vite resolve babel runtime helpers esm objectwithoutpropertiesloose c code labs vite default node modules babel runtime helpers esm objectwithoutpropertiesloose js vite resolve jss plugin global c code labs vite default node modules jss plugin global dist jss plugin global esm js vite resolve react c code labs vite default node modules react index js vite resolve prop types c code labs vite default node modules prop types index js vite resolve react is c code labs vite default node modules mui utils node modules react is index js vite resolve jss plugin nested c code labs vite default node modules jss plugin nested dist jss plugin nested esm js vite resolve hoist non react statics c code labs vite default node modules hoist non react statics dist hoist non react statics cjs js vite resolve jss c code labs vite default node modules jss dist jss esm js vite resolve react is c code labs vite default node modules react is index js vite resolve clsx c code labs vite default node modules clsx dist clsx m js vite resolve jss plugin camel case c code labs vite default node modules jss plugin camel case dist jss plugin camel case esm js vite resolve react jsx runtime c code labs vite default node modules react jsx runtime js vite resolve jss plugin default unit c code labs vite default node modules jss plugin default unit dist jss plugin default unit esm js vite resolve mui base modalunstyled c code labs vite default node modules mui base modalunstyled index js vite resolve mui base textareaautosize c code labs vite default node modules mui base textareaautosize index js vite resolve mui base nossr c code labs vite default node modules mui base nossr index js vite resolve jss plugin vendor prefixer c code labs vite default node modules jss plugin vendor prefixer dist jss plugin vendor prefixer esm js vite resolve mui base clickawaylistener c code labs vite default node modules mui base clickawaylistener index js vite resolve mui system c code labs vite default node modules mui system esm index js vite resolve mui base autocompleteunstyled c code labs vite default node modules mui base autocompleteunstyled index js vite resolve is in browser c code labs vite default node modules is in browser dist module js vite resolve jss plugin props sort c code labs vite default node modules jss plugin props sort dist jss plugin props sort esm js vite resolve mui styled engine c code labs vite default node modules mui styled engine index js vite resolve tiny warning c code labs vite default node modules tiny warning dist tiny warning esm js vite resolve react dom c code labs vite default node modules react dom index js vite resolve css vendor c code labs vite default node modules css vendor dist css vendor esm js vite resolve mui material utils c code labs vite default node modules mui material utils index js vite resolve hyphenate style name c code labs vite default node modules hyphenate style name index js vite resolve emotion styled c code labs vite default node modules emotion styled dist emotion styled browser esm js vite resolve mui private theming c code labs vite default node modules mui private theming index js vite resolve babel runtime helpers esm createclass c code labs vite default node modules babel runtime helpers esm createclass js vite resolve react is c code labs vite default node modules mui material node modules react is index js vite resolve mui base popperunstyled c code labs vite default node modules mui base popperunstyled index js vite resolve emotion react c code labs vite default node modules emotion react dist emotion react browser esm js vite resolve babel runtime helpers esm inheritsloose c code labs vite default node modules babel runtime helpers esm inheritsloose js vite resolve react is c code labs vite default node modules mui base node modules react is index js vite resolve popperjs core c code labs vite default node modules popperjs core lib index js vite resolve react transition group c code labs vite default node modules react transition group esm index js vite resolve babel runtime helpers esm assertthisinitialized c code labs vite default node modules babel runtime helpers esm assertthisinitialized js vite resolve mui base backdropunstyled c code labs vite default node modules mui base backdropunstyled index js vite resolve babel runtime helpers esm toconsumablearray c code labs vite default node modules babel runtime helpers esm toconsumablearray js vite resolve babel runtime helpers extends c code labs vite default node modules babel runtime helpers esm extends js vite resolve emotion cache c code labs vite default node modules emotion cache dist emotion cache browser esm js vite resolve mui base badgeunstyled c code labs vite default node modules mui base badgeunstyled index js vite resolve mui base sliderunstyled c code labs vite default node modules mui base sliderunstyled index js vite resolve mui base composeclasses c code labs vite default node modules mui base composeclasses index js vite resolve emotion is prop valid c code labs vite default node modules emotion is prop valid dist emotion is prop valid browser esm js vite resolve emotion weak memoize c code labs vite default node modules emotion weak memoize dist weak memoize browser esm js vite resolve emotion utils c code labs vite default node modules emotion utils dist emotion utils browser esm js vite resolve emotion serialize c code labs vite default node modules emotion serialize dist emotion serialize browser esm js vite resolve emotion sheet c code labs vite default node modules emotion sheet dist emotion sheet browser esm js vite resolve dom helpers addclass c code labs vite default node modules dom helpers esm addclass js vite resolve stylis c code labs vite default node modules stylis index js vite resolve emotion memoize c code labs vite default node modules emotion memoize dist emotion memoize browser esm js vite resolve emotion hash c code labs vite default node modules emotion hash dist hash browser esm js vite resolve dom helpers removeclass c code labs vite default node modules dom helpers esm removeclass js vite resolve emotion unitless c code labs vite default node modules emotion unitless dist unitless browser esm js vite deps deps bundled in vite dev server running at local network use host to expose ready in validations follow our read the read the check that there isn t that reports the same bug to avoid creating a duplicate make sure this is a vite issue and not a framework specific issue for example if it s a vue sfc related bug it should likely be reported to instead check that this is a concrete bug for q a open a or join our the provided reproduction is a of the bug | 0 |
6,194 | 2,815,827,155 | IssuesEvent | 2015-05-19 07:57:53 | IDgis/geo-publisher-test | https://api.github.com/repos/IDgis/geo-publisher-test | closed | Verwijderen groep levert foutsituatie op | readyfortest | Om schoon te kunnen testen zijn de lagen en de groepen verwijdert. Hierbij wordt bij de systeemtaken een foutmelding weergeven:
service Groep
13-05-2015 06:49:17 : Foutsituatie (staging)
Als je dan in geoserver kijkt blijken er nog lagen aanwezig te zijn die in de groepen zaten. | 1.0 | Verwijderen groep levert foutsituatie op - Om schoon te kunnen testen zijn de lagen en de groepen verwijdert. Hierbij wordt bij de systeemtaken een foutmelding weergeven:
service Groep
13-05-2015 06:49:17 : Foutsituatie (staging)
Als je dan in geoserver kijkt blijken er nog lagen aanwezig te zijn die in de groepen zaten. | non_priority | verwijderen groep levert foutsituatie op om schoon te kunnen testen zijn de lagen en de groepen verwijdert hierbij wordt bij de systeemtaken een foutmelding weergeven service groep foutsituatie staging als je dan in geoserver kijkt blijken er nog lagen aanwezig te zijn die in de groepen zaten | 0 |
282,366 | 21,315,484,838 | IssuesEvent | 2022-04-16 07:37:56 | Benjykoh/pe | https://api.github.com/repos/Benjykoh/pe | opened | Incorrect format for the User Stories in Developer Guide | type.DocumentationBug severity.VeryLow | User story 3 is shown below. The formatting for the 4th column is wrong, as it read "So that I can my list my list will be reflective of who is currently in my class"
<!--session: 1650089476255-b9b23af6-0e3e-417c-a495-89e310a62f4a-->
<!--Version: Web v3.4.2--> | 1.0 | Incorrect format for the User Stories in Developer Guide - User story 3 is shown below. The formatting for the 4th column is wrong, as it read "So that I can my list my list will be reflective of who is currently in my class"
<!--session: 1650089476255-b9b23af6-0e3e-417c-a495-89e310a62f4a-->
<!--Version: Web v3.4.2--> | non_priority | incorrect format for the user stories in developer guide user story is shown below the formatting for the column is wrong as it read so that i can my list my list will be reflective of who is currently in my class | 0 |
5,470 | 5,002,642,251 | IssuesEvent | 2016-12-11 14:15:59 | MuckRock/muckrock | https://api.github.com/repos/MuckRock/muckrock | closed | Images are optimized in the request | performance | When an image is uploaded, it is losslessly optimized (#737) in the request cycle, which may slow it down to the point of crashing. This should be done out of cycle using celery.
Right now on upload, images go to heroku, get optimized, then go to S3. To do this out of cycle, we will go to heroku, S3, then from celery download from S3 to heroku, optimize, and upload back to S3. Other options would be looking into something like amazon lambda to do the optimizations (not sure if thats the right technology or if its even capable of doing something like this).
Also, right now, all images are optimized (news, avatars, project images, foia file images, everything). Do we want to be more selective about which images we are optimizing? (My guess would be yes, as if we switch to celery it won't be automatic like now, but require us to call out to celery to do the optimization on a new image upload)
| True | Images are optimized in the request - When an image is uploaded, it is losslessly optimized (#737) in the request cycle, which may slow it down to the point of crashing. This should be done out of cycle using celery.
Right now on upload, images go to heroku, get optimized, then go to S3. To do this out of cycle, we will go to heroku, S3, then from celery download from S3 to heroku, optimize, and upload back to S3. Other options would be looking into something like amazon lambda to do the optimizations (not sure if thats the right technology or if its even capable of doing something like this).
Also, right now, all images are optimized (news, avatars, project images, foia file images, everything). Do we want to be more selective about which images we are optimizing? (My guess would be yes, as if we switch to celery it won't be automatic like now, but require us to call out to celery to do the optimization on a new image upload)
| non_priority | images are optimized in the request when an image is uploaded it is losslessly optimized in the request cycle which may slow it down to the point of crashing this should be done out of cycle using celery right now on upload images go to heroku get optimized then go to to do this out of cycle we will go to heroku then from celery download from to heroku optimize and upload back to other options would be looking into something like amazon lambda to do the optimizations not sure if thats the right technology or if its even capable of doing something like this also right now all images are optimized news avatars project images foia file images everything do we want to be more selective about which images we are optimizing my guess would be yes as if we switch to celery it won t be automatic like now but require us to call out to celery to do the optimization on a new image upload | 0 |
33,703 | 9,200,632,988 | IssuesEvent | 2019-03-07 17:31:22 | trilinos/Trilinos | https://api.github.com/repos/trilinos/Trilinos | closed | Amesos2: Umfpack + Superlu compile failure when complex_double enabled | build pkg: Amesos2 resolved: duplicate | Reported by Sam Browne via email.
When compiling Trilinos with Amesos2 enabled and Umfpack and Superlu TPLs a compile error results. This is due to ambiguity in matching the templated class `ValueTypeConversionTraits` resulting in candidate specializations in both the Umfpack and Superlu TypeMaps.
Error:
```
/Users/ndellin/Research/trilinos/Trilinos/packages/amesos2/src/Amesos2_Details_registerLinearSolverFactory.cpp:102:1: required from here
/Users/ndellin/Research/trilinos/Trilinos/packages/teuchos/core/src/Teuchos_as.hpp:2830:61: error: ambiguous template instantiation for 'class Teuchos::ValueTypeConversionTraits<SLU::Z::doublecomplex, std::complex<double> >'
return ValueTypeConversionTraits<TypeTo,TypeFrom>::convert(t);
```
Fix is to add full specializations to the SuperLU TypeMap to prevent the ambiguity. PR coming in shortly.
<!---
Note that anything between these delimiters is a comment that will not appear
in the issue description once created. Click on the Preview tab to see what
everything will look like when you submit.
-->
<!---
Feel free to delete anything from this template that is not applicable to the
issue you are submitting.
-->
<!---
Replace <teamName> below with the appropriate Trilinos package/team name.
-->
@trilinos/amesos2
<!---
Assignees: If you know anyone who should likely tackle this issue, select them
from the Assignees drop-down on the right.
-->
<!---
Lables: Choose any applicable package names from the Labels drop-down on the
right. Additionally, choose a label to indicate the type of issue, for
instance, bug, build, documentation, enhancement, etc.
-->
| 1.0 | Amesos2: Umfpack + Superlu compile failure when complex_double enabled - Reported by Sam Browne via email.
When compiling Trilinos with Amesos2 enabled and Umfpack and Superlu TPLs a compile error results. This is due to ambiguity in matching the templated class `ValueTypeConversionTraits` resulting in candidate specializations in both the Umfpack and Superlu TypeMaps.
Error:
```
/Users/ndellin/Research/trilinos/Trilinos/packages/amesos2/src/Amesos2_Details_registerLinearSolverFactory.cpp:102:1: required from here
/Users/ndellin/Research/trilinos/Trilinos/packages/teuchos/core/src/Teuchos_as.hpp:2830:61: error: ambiguous template instantiation for 'class Teuchos::ValueTypeConversionTraits<SLU::Z::doublecomplex, std::complex<double> >'
return ValueTypeConversionTraits<TypeTo,TypeFrom>::convert(t);
```
Fix is to add full specializations to the SuperLU TypeMap to prevent the ambiguity. PR coming in shortly.
<!---
Note that anything between these delimiters is a comment that will not appear
in the issue description once created. Click on the Preview tab to see what
everything will look like when you submit.
-->
<!---
Feel free to delete anything from this template that is not applicable to the
issue you are submitting.
-->
<!---
Replace <teamName> below with the appropriate Trilinos package/team name.
-->
@trilinos/amesos2
<!---
Assignees: If you know anyone who should likely tackle this issue, select them
from the Assignees drop-down on the right.
-->
<!---
Lables: Choose any applicable package names from the Labels drop-down on the
right. Additionally, choose a label to indicate the type of issue, for
instance, bug, build, documentation, enhancement, etc.
-->
| non_priority | umfpack superlu compile failure when complex double enabled reported by sam browne via email when compiling trilinos with enabled and umfpack and superlu tpls a compile error results this is due to ambiguity in matching the templated class valuetypeconversiontraits resulting in candidate specializations in both the umfpack and superlu typemaps error users ndellin research trilinos trilinos packages src details registerlinearsolverfactory cpp required from here users ndellin research trilinos trilinos packages teuchos core src teuchos as hpp error ambiguous template instantiation for class teuchos valuetypeconversiontraits return valuetypeconversiontraits convert t fix is to add full specializations to the superlu typemap to prevent the ambiguity pr coming in shortly note that anything between these delimiters is a comment that will not appear in the issue description once created click on the preview tab to see what everything will look like when you submit feel free to delete anything from this template that is not applicable to the issue you are submitting replace below with the appropriate trilinos package team name trilinos assignees if you know anyone who should likely tackle this issue select them from the assignees drop down on the right lables choose any applicable package names from the labels drop down on the right additionally choose a label to indicate the type of issue for instance bug build documentation enhancement etc | 0 |
79,094 | 22,611,597,720 | IssuesEvent | 2022-06-29 17:42:36 | infernalstudios/Infernal-Expansion | https://api.github.com/repos/infernalstudios/Infernal-Expansion | closed | Glowstone Canyon spawn rate seems abnormally low when using Biomes O' Plenty and Terrablender in 1.18.2 | bug beta build 1.18 | ### Describe the Bug
The Glowstone Canyon biome seems to spawn much more rarely than intended when using Biomes O' Plenty and Terrablender.
### Reproduction Steps
Search for the biome in the Nether.
### Expected Result
The biome will generate much more commonly.
### Screenshots and Videos
_No response_
### Operating System
Linux Mint 20.3
### Mod Version
2.5 Beta 1
### Minecraft Version
1.18.2
### Forge Version
40.1.30
### Other Mods
Biomes O' Plenty, Terrablender.
### Additional Context
_No response_ | 1.0 | Glowstone Canyon spawn rate seems abnormally low when using Biomes O' Plenty and Terrablender in 1.18.2 - ### Describe the Bug
The Glowstone Canyon biome seems to spawn much more rarely than intended when using Biomes O' Plenty and Terrablender.
### Reproduction Steps
Search for the biome in the Nether.
### Expected Result
The biome will generate much more commonly.
### Screenshots and Videos
_No response_
### Operating System
Linux Mint 20.3
### Mod Version
2.5 Beta 1
### Minecraft Version
1.18.2
### Forge Version
40.1.30
### Other Mods
Biomes O' Plenty, Terrablender.
### Additional Context
_No response_ | non_priority | glowstone canyon spawn rate seems abnormally low when using biomes o plenty and terrablender in describe the bug the glowstone canyon biome seems to spawn much more rarely than intended when using biomes o plenty and terrablender reproduction steps search for the biome in the nether expected result the biome will generate much more commonly screenshots and videos no response operating system linux mint mod version beta minecraft version forge version other mods biomes o plenty terrablender additional context no response | 0 |
76,811 | 15,496,205,541 | IssuesEvent | 2021-03-11 02:15:10 | n-devs/full-stack-react-profile | https://api.github.com/repos/n-devs/full-stack-react-profile | opened | CVE-2020-13822 (High) detected in elliptic-6.5.0.tgz | security vulnerability | ## CVE-2020-13822 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>elliptic-6.5.0.tgz</b></p></summary>
<p>EC cryptography</p>
<p>Library home page: <a href="https://registry.npmjs.org/elliptic/-/elliptic-6.5.0.tgz">https://registry.npmjs.org/elliptic/-/elliptic-6.5.0.tgz</a></p>
<p>Path to dependency file: /full-stack-react-profile/package.json</p>
<p>Path to vulnerable library: full-stack-react-profile/node_modules/elliptic/package.json</p>
<p>
Dependency Hierarchy:
- webpack-4.35.2.tgz (Root Library)
- node-libs-browser-2.2.1.tgz
- crypto-browserify-3.12.0.tgz
- browserify-sign-4.0.4.tgz
- :x: **elliptic-6.5.0.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>
The Elliptic package 6.5.2 for Node.js allows ECDSA signature malleability via variations in encoding, leading '\0' bytes, or integer overflows. This could conceivably have a security-relevant impact if an application relied on a single canonical signature.
<p>Publish Date: 2020-06-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-13822>CVE-2020-13822</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.7</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: High
- Integrity Impact: High
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/indutny/elliptic/tree/v6.5.3">https://github.com/indutny/elliptic/tree/v6.5.3</a></p>
<p>Release Date: 2020-06-04</p>
<p>Fix Resolution: v6.5.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-13822 (High) detected in elliptic-6.5.0.tgz - ## CVE-2020-13822 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>elliptic-6.5.0.tgz</b></p></summary>
<p>EC cryptography</p>
<p>Library home page: <a href="https://registry.npmjs.org/elliptic/-/elliptic-6.5.0.tgz">https://registry.npmjs.org/elliptic/-/elliptic-6.5.0.tgz</a></p>
<p>Path to dependency file: /full-stack-react-profile/package.json</p>
<p>Path to vulnerable library: full-stack-react-profile/node_modules/elliptic/package.json</p>
<p>
Dependency Hierarchy:
- webpack-4.35.2.tgz (Root Library)
- node-libs-browser-2.2.1.tgz
- crypto-browserify-3.12.0.tgz
- browserify-sign-4.0.4.tgz
- :x: **elliptic-6.5.0.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>
The Elliptic package 6.5.2 for Node.js allows ECDSA signature malleability via variations in encoding, leading '\0' bytes, or integer overflows. This could conceivably have a security-relevant impact if an application relied on a single canonical signature.
<p>Publish Date: 2020-06-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-13822>CVE-2020-13822</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.7</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: High
- Integrity Impact: High
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/indutny/elliptic/tree/v6.5.3">https://github.com/indutny/elliptic/tree/v6.5.3</a></p>
<p>Release Date: 2020-06-04</p>
<p>Fix Resolution: v6.5.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in elliptic tgz cve high severity vulnerability vulnerable library elliptic tgz ec cryptography library home page a href path to dependency file full stack react profile package json path to vulnerable library full stack react profile node modules elliptic package json dependency hierarchy webpack tgz root library node libs browser tgz crypto browserify tgz browserify sign tgz x elliptic tgz vulnerable library vulnerability details the elliptic package for node js allows ecdsa signature malleability via variations in encoding leading bytes or integer overflows this could conceivably have a security relevant impact if an application relied on a single canonical signature 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 high integrity impact high availability impact low 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 |
40,219 | 8,752,947,546 | IssuesEvent | 2018-12-14 06:11:19 | eclipse/eclipse.jdt.ls | https://api.github.com/repos/eclipse/eclipse.jdt.ls | closed | Bulk accessor generation should ignore static fields | bug code-actions | Given a private static field:
```java
private static String DEFAULT_NAME = "World";
```
calling the `generate getters and setters` command generate its accessors:
```java
/**
* @return the dEFAULT_NAME
*/
public static String getDEFAULT_NAME() {
return DEFAULT_NAME;
}
/**
* @param dEFAULT_NAME the dEFAULT_NAME to set
*/
public static void setDEFAULT_NAME(String dEFAULT_NAME) {
DEFAULT_NAME = dEFAULT_NAME;
}
```
I'm pretty confident that's wrong in 99.99% of the cases
| 1.0 | Bulk accessor generation should ignore static fields - Given a private static field:
```java
private static String DEFAULT_NAME = "World";
```
calling the `generate getters and setters` command generate its accessors:
```java
/**
* @return the dEFAULT_NAME
*/
public static String getDEFAULT_NAME() {
return DEFAULT_NAME;
}
/**
* @param dEFAULT_NAME the dEFAULT_NAME to set
*/
public static void setDEFAULT_NAME(String dEFAULT_NAME) {
DEFAULT_NAME = dEFAULT_NAME;
}
```
I'm pretty confident that's wrong in 99.99% of the cases
| non_priority | bulk accessor generation should ignore static fields given a private static field java private static string default name world calling the generate getters and setters command generate its accessors java return the default name public static string getdefault name return default name param default name the default name to set public static void setdefault name string default name default name default name i m pretty confident that s wrong in of the cases | 0 |
322,025 | 27,574,031,767 | IssuesEvent | 2023-03-08 11:33:42 | TWiStErRob/net.twisterrob.inventory | https://api.github.com/repos/TWiStErRob/net.twisterrob.inventory | opened | ZippedXMLExporterTest.saveTempZip result is not closed | a:bug in:test | ```
I/TestRunner( 2733): finished: testDemoXmlTransformation(net.twisterrob.inventory.android.backup.xml.ZippedXMLExporterTest)
I/TestRunner( 2733): run finished: 185 tests, 0 failed, 6 ignored
I/MonitoringInstr( 2733): waitForActivitiesToComplete() took: 1ms
E/StrictMode( 2733): A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.
E/StrictMode( 2733): java.lang.Throwable: Explicit termination method 'close' not called
E/StrictMode( 2733): at dalvik.system.CloseGuard.open(CloseGuard.java:184)
E/StrictMode( 2733): at java.io.RandomAccessFile.<init>(RandomAccessFile.java:127)
E/StrictMode( 2733): at java.io.RandomAccessFile.<init>(RandomAccessFile.java:149)
E/StrictMode( 2733): at java.util.zip.ZipFile.<init>(ZipFile.java:158)
E/StrictMode( 2733): at java.util.zip.ZipFile.<init>(ZipFile.java:119)
E/StrictMode( 2733): at net.twisterrob.inventory.android.backup.xml.ZippedXMLExporterTest.saveTempZip(ZippedXMLExporterTest.java:141)
E/StrictMode( 2733): at net.twisterrob.inventory.android.backup.xml.ZippedXMLExporterTest.testDemoXmlTransformation(ZippedXMLExporterTest.java:126)
E/StrictMode( 2733): at java.lang.reflect.Method.invoke(Native Method)
E/StrictMode( 2733): at java.lang.reflect.Method.invoke(Method.java:372)
E/StrictMode( 2733): at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
E/StrictMode( 2733): at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
E/StrictMode( 2733): at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
E/StrictMode( 2733): at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
E/StrictMode( 2733): at androidx.test.internal.runner.junit4.statement.RunBefores.evaluate(RunBefores.java:80)
E/StrictMode( 2733): at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
E/StrictMode( 2733): at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
E/StrictMode( 2733): at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
E/StrictMode( 2733): at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
E/StrictMode( 2733): at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
E/StrictMode( 2733): at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
E/StrictMode( 2733): at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
E/StrictMode( 2733): at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
E/StrictMode( 2733): at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
E/StrictMode( 2733): at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
E/StrictMode( 2733): at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
E/StrictMode( 2733): at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
E/StrictMode( 2733): at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
E/StrictMode( 2733): at org.junit.runners.Suite.runChild(Suite.java:128)
E/StrictMode( 2733): at org.junit.runners.Suite.runChild(Suite.java:27)
E/StrictMode( 2733): at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
E/StrictMode( 2733): at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
E/StrictMode( 2733): at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
E/StrictMode( 2733): at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
E/StrictMode( 2733): at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
E/StrictMode( 2733): at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
E/StrictMode( 2733): at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
E/StrictMode( 2733): at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
E/StrictMode( 2733): at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
E/StrictMode( 2733): at androidx.test.internal.runner.TestExecutor.execute(TestExecutor.java:56)
E/StrictMode( 2733): at androidx.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:395)
E/StrictMode( 2733): at net.twisterrob.android.test.junit.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:82)
E/StrictMode( 2733): at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1837)
``` | 1.0 | ZippedXMLExporterTest.saveTempZip result is not closed - ```
I/TestRunner( 2733): finished: testDemoXmlTransformation(net.twisterrob.inventory.android.backup.xml.ZippedXMLExporterTest)
I/TestRunner( 2733): run finished: 185 tests, 0 failed, 6 ignored
I/MonitoringInstr( 2733): waitForActivitiesToComplete() took: 1ms
E/StrictMode( 2733): A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.
E/StrictMode( 2733): java.lang.Throwable: Explicit termination method 'close' not called
E/StrictMode( 2733): at dalvik.system.CloseGuard.open(CloseGuard.java:184)
E/StrictMode( 2733): at java.io.RandomAccessFile.<init>(RandomAccessFile.java:127)
E/StrictMode( 2733): at java.io.RandomAccessFile.<init>(RandomAccessFile.java:149)
E/StrictMode( 2733): at java.util.zip.ZipFile.<init>(ZipFile.java:158)
E/StrictMode( 2733): at java.util.zip.ZipFile.<init>(ZipFile.java:119)
E/StrictMode( 2733): at net.twisterrob.inventory.android.backup.xml.ZippedXMLExporterTest.saveTempZip(ZippedXMLExporterTest.java:141)
E/StrictMode( 2733): at net.twisterrob.inventory.android.backup.xml.ZippedXMLExporterTest.testDemoXmlTransformation(ZippedXMLExporterTest.java:126)
E/StrictMode( 2733): at java.lang.reflect.Method.invoke(Native Method)
E/StrictMode( 2733): at java.lang.reflect.Method.invoke(Method.java:372)
E/StrictMode( 2733): at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
E/StrictMode( 2733): at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
E/StrictMode( 2733): at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
E/StrictMode( 2733): at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
E/StrictMode( 2733): at androidx.test.internal.runner.junit4.statement.RunBefores.evaluate(RunBefores.java:80)
E/StrictMode( 2733): at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
E/StrictMode( 2733): at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
E/StrictMode( 2733): at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
E/StrictMode( 2733): at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
E/StrictMode( 2733): at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
E/StrictMode( 2733): at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
E/StrictMode( 2733): at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
E/StrictMode( 2733): at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
E/StrictMode( 2733): at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
E/StrictMode( 2733): at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
E/StrictMode( 2733): at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
E/StrictMode( 2733): at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
E/StrictMode( 2733): at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
E/StrictMode( 2733): at org.junit.runners.Suite.runChild(Suite.java:128)
E/StrictMode( 2733): at org.junit.runners.Suite.runChild(Suite.java:27)
E/StrictMode( 2733): at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
E/StrictMode( 2733): at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
E/StrictMode( 2733): at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
E/StrictMode( 2733): at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
E/StrictMode( 2733): at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
E/StrictMode( 2733): at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
E/StrictMode( 2733): at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
E/StrictMode( 2733): at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
E/StrictMode( 2733): at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
E/StrictMode( 2733): at androidx.test.internal.runner.TestExecutor.execute(TestExecutor.java:56)
E/StrictMode( 2733): at androidx.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:395)
E/StrictMode( 2733): at net.twisterrob.android.test.junit.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:82)
E/StrictMode( 2733): at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1837)
``` | non_priority | zippedxmlexportertest savetempzip result is not closed i testrunner finished testdemoxmltransformation net twisterrob inventory android backup xml zippedxmlexportertest i testrunner run finished tests failed ignored i monitoringinstr waitforactivitiestocomplete took e strictmode a resource was acquired at attached stack trace but never released see java io closeable for information on avoiding resource leaks e strictmode java lang throwable explicit termination method close not called e strictmode at dalvik system closeguard open closeguard java e strictmode at java io randomaccessfile randomaccessfile java e strictmode at java io randomaccessfile randomaccessfile java e strictmode at java util zip zipfile zipfile java e strictmode at java util zip zipfile zipfile java e strictmode at net twisterrob inventory android backup xml zippedxmlexportertest savetempzip zippedxmlexportertest java e strictmode at net twisterrob inventory android backup xml zippedxmlexportertest testdemoxmltransformation zippedxmlexportertest java e strictmode at java lang reflect method invoke native method e strictmode at java lang reflect method invoke method java e strictmode at org junit runners model frameworkmethod runreflectivecall frameworkmethod java e strictmode at org junit internal runners model reflectivecallable run reflectivecallable java e strictmode at org junit runners model frameworkmethod invokeexplosively frameworkmethod java e strictmode at org junit internal runners statements invokemethod evaluate invokemethod java e strictmode at androidx test internal runner statement runbefores evaluate runbefores java e strictmode at org junit rules externalresource evaluate externalresource java e strictmode at org junit runners parentrunner evaluate parentrunner java e strictmode at org junit runners evaluate java e strictmode at org junit runners parentrunner runleaf parentrunner java e strictmode at org junit runners runchild java e strictmode at org junit runners runchild java e strictmode at org junit runners parentrunner run parentrunner java e strictmode at org junit runners parentrunner schedule parentrunner java e strictmode at org junit runners parentrunner runchildren parentrunner java e strictmode at org junit runners parentrunner access parentrunner java e strictmode at org junit runners parentrunner evaluate parentrunner java e strictmode at org junit runners parentrunner evaluate parentrunner java e strictmode at org junit runners parentrunner run parentrunner java e strictmode at org junit runners suite runchild suite java e strictmode at org junit runners suite runchild suite java e strictmode at org junit runners parentrunner run parentrunner java e strictmode at org junit runners parentrunner schedule parentrunner java e strictmode at org junit runners parentrunner runchildren parentrunner java e strictmode at org junit runners parentrunner access parentrunner java e strictmode at org junit runners parentrunner evaluate parentrunner java e strictmode at org junit runners parentrunner evaluate parentrunner java e strictmode at org junit runners parentrunner run parentrunner java e strictmode at org junit runner junitcore run junitcore java e strictmode at org junit runner junitcore run junitcore java e strictmode at androidx test internal runner testexecutor execute testexecutor java e strictmode at androidx test runner androidjunitrunner onstart androidjunitrunner java e strictmode at net twisterrob android test junit androidjunitrunner onstart androidjunitrunner java e strictmode at android app instrumentation instrumentationthread run instrumentation java | 0 |
42,174 | 17,079,845,473 | IssuesEvent | 2021-07-08 02:23:47 | ctripcorp/apollo | https://api.github.com/repos/ctripcorp/apollo | closed | 服务外网访问场景下，如何安全访问apollo配置 | area/configservice area/security kind/question stale | **服务外网访问场景下，如何安全访问apollo配置**
在跨大区场景下公用apollo配置，需要暴露服务地址，导致知道appid情况下可以在任意地址获取到配置，又由于机器过多设置白名单工作繁重
希望增加基于应用Id的ak/sk机制 ，访问要加secret才可访问，另外apollo UI的在没有给用户赋予权限的情况下，依然可以查看，只是不能编辑新增，希望权限基于应用，没有赋权限时增删改查全部不予操作
**其它背景**
| 1.0 | 服务外网访问场景下，如何安全访问apollo配置 - **服务外网访问场景下，如何安全访问apollo配置**
在跨大区场景下公用apollo配置，需要暴露服务地址，导致知道appid情况下可以在任意地址获取到配置，又由于机器过多设置白名单工作繁重
希望增加基于应用Id的ak/sk机制 ，访问要加secret才可访问，另外apollo UI的在没有给用户赋予权限的情况下，依然可以查看，只是不能编辑新增，希望权限基于应用，没有赋权限时增删改查全部不予操作
**其它背景**
| non_priority | 服务外网访问场景下，如何安全访问apollo配置 服务外网访问场景下，如何安全访问apollo配置 在跨大区场景下公用apollo配置，需要暴露服务地址，导致知道appid情况下可以在任意地址获取到配置，又由于机器过多设置白名单工作繁重 希望增加基于应用id的ak sk机制 ，访问要加secret才可访问，另外apollo ui的在没有给用户赋予权限的情况下，依然可以查看，只是不能编辑新增，希望权限基于应用，没有赋权限时增删改查全部不予操作 其它背景 | 0 |
224,712 | 17,198,661,611 | IssuesEvent | 2021-07-16 22:06:43 | gladly-team/next-firebase-auth | https://api.github.com/repos/gladly-team/next-firebase-auth | opened | Add troubleshooting FAQ or additional info about PEM formatting | documentation | **Did you have difficulty using or understanding an aspect of `next-firebase-auth`?**
See confusion in #95. Related: #212
**What documentation would you like to add or change?**
Provide a section with various approaches to formatting/parsing the private key. Link to it from the troubleshooting FAQ.
**Version**
What version of `next-firebase-auth` are you using?
0.13.2 | 1.0 | Add troubleshooting FAQ or additional info about PEM formatting - **Did you have difficulty using or understanding an aspect of `next-firebase-auth`?**
See confusion in #95. Related: #212
**What documentation would you like to add or change?**
Provide a section with various approaches to formatting/parsing the private key. Link to it from the troubleshooting FAQ.
**Version**
What version of `next-firebase-auth` are you using?
0.13.2 | non_priority | add troubleshooting faq or additional info about pem formatting did you have difficulty using or understanding an aspect of next firebase auth see confusion in related what documentation would you like to add or change provide a section with various approaches to formatting parsing the private key link to it from the troubleshooting faq version what version of next firebase auth are you using | 0 |
113,847 | 11,825,402,578 | IssuesEvent | 2020-03-21 12:40:21 | OpenDev-Camp/odc-home | https://api.github.com/repos/OpenDev-Camp/odc-home | closed | Documentation: Update README.md for the Repository Rules | documentation | By doing so, this would allow the collaborators for this repository to know the rules in submitting an issue, pull request, and branching. | 1.0 | Documentation: Update README.md for the Repository Rules - By doing so, this would allow the collaborators for this repository to know the rules in submitting an issue, pull request, and branching. | non_priority | documentation update readme md for the repository rules by doing so this would allow the collaborators for this repository to know the rules in submitting an issue pull request and branching | 0 |
230,457 | 18,670,397,076 | IssuesEvent | 2021-10-30 15:48:37 | OllisGit/OctoPrint-PrintJobHistory | https://api.github.com/repos/OllisGit/OctoPrint-PrintJobHistory | closed | No dialog or recording of print jobs | type: bug status: waitingForTestFeedback | I have been waiting for the fix in 1.13, but even after upgrading to 1.13.2, I'm still no longer getting the print history dialog and it's not saving the history either. Last print job shows date of 4/19/2021 and I print on a near daily basis. Not sure what logs you might need, but happy to provide. | 1.0 | No dialog or recording of print jobs - I have been waiting for the fix in 1.13, but even after upgrading to 1.13.2, I'm still no longer getting the print history dialog and it's not saving the history either. Last print job shows date of 4/19/2021 and I print on a near daily basis. Not sure what logs you might need, but happy to provide. | non_priority | no dialog or recording of print jobs i have been waiting for the fix in but even after upgrading to i m still no longer getting the print history dialog and it s not saving the history either last print job shows date of and i print on a near daily basis not sure what logs you might need but happy to provide | 0 |
150,631 | 23,693,162,864 | IssuesEvent | 2022-08-29 12:40:03 | pulumi/pulumi-kubernetes | https://api.github.com/repos/pulumi/pulumi-kubernetes | closed | ComponentResourceOptions missing from Pulumi.Kubernetes.Helm.V3 | kind/bug resolution/by-design | ### What happened?
Attempting to use V3.Release but unable to utilise ComponentResourceOptions to configure a Provider. Only CustomResourceOptions listed?
Documentation stores that ComponentResourceOptions should be available on this class?
### Steps to reproduce
Produce a C# dotnet pulumi package, use the following package:
Pulumi.Kubernetes 3.21.0
Attempt to declare a V3 release and pass Component Options through.
### Expected Behavior
ComponentResourceOptions available like it is for V3.Chart and as per V3.Release documentation:
### Actual Behavior
ComponentResourceOptions not available. CustomResourceOptions instead.
### Output of `pulumi about`
_No response_
### Additional context
_No response_
### Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
| 1.0 | ComponentResourceOptions missing from Pulumi.Kubernetes.Helm.V3 - ### What happened?
Attempting to use V3.Release but unable to utilise ComponentResourceOptions to configure a Provider. Only CustomResourceOptions listed?
Documentation stores that ComponentResourceOptions should be available on this class?
### Steps to reproduce
Produce a C# dotnet pulumi package, use the following package:
Pulumi.Kubernetes 3.21.0
Attempt to declare a V3 release and pass Component Options through.
### Expected Behavior
ComponentResourceOptions available like it is for V3.Chart and as per V3.Release documentation:
### Actual Behavior
ComponentResourceOptions not available. CustomResourceOptions instead.
### Output of `pulumi about`
_No response_
### Additional context
_No response_
### Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
| non_priority | componentresourceoptions missing from pulumi kubernetes helm what happened attempting to use release but unable to utilise componentresourceoptions to configure a provider only customresourceoptions listed documentation stores that componentresourceoptions should be available on this class steps to reproduce produce a c dotnet pulumi package use the following package pulumi kubernetes attempt to declare a release and pass component options through expected behavior componentresourceoptions available like it is for chart and as per release documentation actual behavior componentresourceoptions not available customresourceoptions instead output of pulumi about no response additional context no response contributing vote on this issue by adding a 👍 reaction to contribute a fix for this issue leave a comment and link to your pull request if you ve opened one already | 0 |
200,001 | 15,085,818,282 | IssuesEvent | 2021-02-05 19:17:37 | ValveSoftware/SteamVR-for-Linux | https://api.github.com/repos/ValveSoftware/SteamVR-for-Linux | closed | [BUG] Overlays (and more) flicker a lot, especially in the left eye. | Need Retest bug | **Describe the bug**
When the SteamVR overlay is open, it will constantly flicker a lot in a very annoying way, especially in the left eye. This does not appear in the SteamVR VR View, but does in the headset itself. This also seems to happen in the mountain zone when launching SteamVR programs.
**To Reproduce**
Steps to reproduce the behavior:
1. Open SteamVR overlay.
2. If this does not work, click on a game in the main screen in SteamVR Home and click "show details. Bonus points if you play a video. This seems to make the flickering worse for me than just showing the desktop view (which seems to be broken for me, by the way, but that is an issue for another day).
3. In addition, simply launching any program seems to be able to create this issue as well, to a lesser extent, in the mountain space between launching programs. I usually do this close enough to the edge that the edge guard shows, so doing this may help.
**Expected behavior**
The overlay will open, and work perfectly.
**System Information (please complete the following information):**
- Distribution: Gentoo Linux, kernel 5.9.14-gentoo with the newest Mesa drivers pulled from Git and LXDE.
- SteamVR version: 1.16.6
- Steam client version: Dec 20 2020, 23:07:25
- Opted into Steam client beta?: For SteamVR, yes. If you mean Steam itself, no.
- Graphics driver version: [run `nvidia-settings` or `vulkaninfo | grep driverInfo`:
`Mesa 21.0.0-devel (git-ecac89b732) (ACO)`
- Gist for SteamVR System Information: https://gist.github.com/happysmash27/b0365a9032d5a2ca2c68517c990394b0
**Screenshots**
https://happysmash27.me/Upload/Screenshots/Videos/Bugs/SteamVR/VID_20210204_050848.webm | 1.0 | [BUG] Overlays (and more) flicker a lot, especially in the left eye. - **Describe the bug**
When the SteamVR overlay is open, it will constantly flicker a lot in a very annoying way, especially in the left eye. This does not appear in the SteamVR VR View, but does in the headset itself. This also seems to happen in the mountain zone when launching SteamVR programs.
**To Reproduce**
Steps to reproduce the behavior:
1. Open SteamVR overlay.
2. If this does not work, click on a game in the main screen in SteamVR Home and click "show details. Bonus points if you play a video. This seems to make the flickering worse for me than just showing the desktop view (which seems to be broken for me, by the way, but that is an issue for another day).
3. In addition, simply launching any program seems to be able to create this issue as well, to a lesser extent, in the mountain space between launching programs. I usually do this close enough to the edge that the edge guard shows, so doing this may help.
**Expected behavior**
The overlay will open, and work perfectly.
**System Information (please complete the following information):**
- Distribution: Gentoo Linux, kernel 5.9.14-gentoo with the newest Mesa drivers pulled from Git and LXDE.
- SteamVR version: 1.16.6
- Steam client version: Dec 20 2020, 23:07:25
- Opted into Steam client beta?: For SteamVR, yes. If you mean Steam itself, no.
- Graphics driver version: [run `nvidia-settings` or `vulkaninfo | grep driverInfo`:
`Mesa 21.0.0-devel (git-ecac89b732) (ACO)`
- Gist for SteamVR System Information: https://gist.github.com/happysmash27/b0365a9032d5a2ca2c68517c990394b0
**Screenshots**
https://happysmash27.me/Upload/Screenshots/Videos/Bugs/SteamVR/VID_20210204_050848.webm | non_priority | overlays and more flicker a lot especially in the left eye describe the bug when the steamvr overlay is open it will constantly flicker a lot in a very annoying way especially in the left eye this does not appear in the steamvr vr view but does in the headset itself this also seems to happen in the mountain zone when launching steamvr programs to reproduce steps to reproduce the behavior open steamvr overlay if this does not work click on a game in the main screen in steamvr home and click show details bonus points if you play a video this seems to make the flickering worse for me than just showing the desktop view which seems to be broken for me by the way but that is an issue for another day in addition simply launching any program seems to be able to create this issue as well to a lesser extent in the mountain space between launching programs i usually do this close enough to the edge that the edge guard shows so doing this may help expected behavior the overlay will open and work perfectly system information please complete the following information distribution gentoo linux kernel gentoo with the newest mesa drivers pulled from git and lxde steamvr version steam client version dec opted into steam client beta for steamvr yes if you mean steam itself no graphics driver version run nvidia settings or vulkaninfo grep driverinfo mesa devel git aco gist for steamvr system information screenshots | 0 |
64,013 | 12,412,258,208 | IssuesEvent | 2020-05-22 10:11:33 | fac19/week11-where-is-whippy | https://api.github.com/repos/fac19/week11-where-is-whippy | opened | Login in header.js | code review | I don't remember the details of your Figma prototype, but I couldn't get the login in the header.js.
It makes sense for the logout (but maybe you don't want it to be so prominent?).
| 1.0 | Login in header.js - I don't remember the details of your Figma prototype, but I couldn't get the login in the header.js.
It makes sense for the logout (but maybe you don't want it to be so prominent?).
| non_priority | login in header js i don t remember the details of your figma prototype but i couldn t get the login in the header js it makes sense for the logout but maybe you don t want it to be so prominent | 0 |
58,217 | 8,233,915,022 | IssuesEvent | 2018-09-08 07:38:44 | App-vNext/Polly | https://api.github.com/repos/App-vNext/Polly | closed | [DONE; update documentation] publish Polly v6.0.0 as strong-named only | breaking change documentation packaging | ## CONSIDER publishing Polly v6.0.0 as strong-named only
### Background
ASP.NET Core 2.1 is moving to consume Polly for `HttpClient` instances created through [`HttpClientFactory`](https://github.com/aspnet/HttpClientFactory). This will allow the easy application of Polly resilience strategies to outbound calls through `HttpClient`.
This will significantly increase consumption of Polly's strong-named package (currently labelled [Polly-Signed](https://www.nuget.org/packages/polly-Signed)). That however will [create conflicts](https://github.com/BrighterCommand/Brighter/issues/286) for packages or projects that currently consume non-strong-named Polly: [example](https://github.com/BrighterCommand/Brighter/issues/286); [longer discussion](https://github.com/aspnet/HttpClientFactory/issues/105).
_There is no easy answer to this problem_, as attested by discussion on _numerous_ projects: [octokit](https://github.com/octokit/octokit.net/issues/405) and the _many_ projects that reference that issue.
Options:
+ ~**Be purely non-strong-named**~: project cannot then be consumed in environments or by upstream packages mandating strong-naming; not an option for Polly due to ASP.NET Core.
+ **Offer both strong-named and not** (as Polly currently): but [creates conflicts](https://github.com/BrighterCommand/Brighter/issues/286) where a project ends up transiently referencing both.
Or:
## Publish only strong-named
Some consensus among high-consumption projects now is around this, the [NewtonSoft.Json strategy](https://github.com/aspnet/HttpClientFactory/issues/105#issuecomment-385527782), as the least of all evils. @jeremyskinner of FluentValidation [sums it up well here](https://github.com/JeremySkinner/FluentValidation/issues/482#issuecomment-323944469) as does @sharwell [elsewhere](https://github.com/restsharp/RestSharp/issues/216#issuecomment-39761855). I summarise also [here](https://github.com/aspnet/HttpClientFactory/issues/105#issuecomment-385527782).
**TL;DR** Switching to release Polly as strong-named only would be a _one-time hit_ breaking change for consumers of Polly. _But thereafter_, having _only_ the strong-named version of Polly in the market would _prevent/reduce [those conflicts](https://github.com/BrighterCommand/Brighter/issues/286)_ (strong-named versus not) _going forward_.
(edited: for typos)
---
_This is a **proposal** on which we would appreciate evidence-driven feedback._ Particularly any consumption scenarios we may not be aware of. The proposed change is driven by the HttpClientFactory ASP.NET Core integration, which will drive many more Polly users to the strong-named version. ASP.NET Core has prior decision to be strong-named and thus consume strong-named assemblies. | 1.0 | [DONE; update documentation] publish Polly v6.0.0 as strong-named only - ## CONSIDER publishing Polly v6.0.0 as strong-named only
### Background
ASP.NET Core 2.1 is moving to consume Polly for `HttpClient` instances created through [`HttpClientFactory`](https://github.com/aspnet/HttpClientFactory). This will allow the easy application of Polly resilience strategies to outbound calls through `HttpClient`.
This will significantly increase consumption of Polly's strong-named package (currently labelled [Polly-Signed](https://www.nuget.org/packages/polly-Signed)). That however will [create conflicts](https://github.com/BrighterCommand/Brighter/issues/286) for packages or projects that currently consume non-strong-named Polly: [example](https://github.com/BrighterCommand/Brighter/issues/286); [longer discussion](https://github.com/aspnet/HttpClientFactory/issues/105).
_There is no easy answer to this problem_, as attested by discussion on _numerous_ projects: [octokit](https://github.com/octokit/octokit.net/issues/405) and the _many_ projects that reference that issue.
Options:
+ ~**Be purely non-strong-named**~: project cannot then be consumed in environments or by upstream packages mandating strong-naming; not an option for Polly due to ASP.NET Core.
+ **Offer both strong-named and not** (as Polly currently): but [creates conflicts](https://github.com/BrighterCommand/Brighter/issues/286) where a project ends up transiently referencing both.
Or:
## Publish only strong-named
Some consensus among high-consumption projects now is around this, the [NewtonSoft.Json strategy](https://github.com/aspnet/HttpClientFactory/issues/105#issuecomment-385527782), as the least of all evils. @jeremyskinner of FluentValidation [sums it up well here](https://github.com/JeremySkinner/FluentValidation/issues/482#issuecomment-323944469) as does @sharwell [elsewhere](https://github.com/restsharp/RestSharp/issues/216#issuecomment-39761855). I summarise also [here](https://github.com/aspnet/HttpClientFactory/issues/105#issuecomment-385527782).
**TL;DR** Switching to release Polly as strong-named only would be a _one-time hit_ breaking change for consumers of Polly. _But thereafter_, having _only_ the strong-named version of Polly in the market would _prevent/reduce [those conflicts](https://github.com/BrighterCommand/Brighter/issues/286)_ (strong-named versus not) _going forward_.
(edited: for typos)
---
_This is a **proposal** on which we would appreciate evidence-driven feedback._ Particularly any consumption scenarios we may not be aware of. The proposed change is driven by the HttpClientFactory ASP.NET Core integration, which will drive many more Polly users to the strong-named version. ASP.NET Core has prior decision to be strong-named and thus consume strong-named assemblies. | non_priority | publish polly as strong named only consider publishing polly as strong named only background asp net core is moving to consume polly for httpclient instances created through this will allow the easy application of polly resilience strategies to outbound calls through httpclient this will significantly increase consumption of polly s strong named package currently labelled that however will for packages or projects that currently consume non strong named polly there is no easy answer to this problem as attested by discussion on numerous projects and the many projects that reference that issue options be purely non strong named project cannot then be consumed in environments or by upstream packages mandating strong naming not an option for polly due to asp net core offer both strong named and not as polly currently but where a project ends up transiently referencing both or publish only strong named some consensus among high consumption projects now is around this the as the least of all evils jeremyskinner of fluentvalidation as does sharwell i summarise also tl dr switching to release polly as strong named only would be a one time hit breaking change for consumers of polly but thereafter having only the strong named version of polly in the market would prevent reduce strong named versus not going forward edited for typos this is a proposal on which we would appreciate evidence driven feedback particularly any consumption scenarios we may not be aware of the proposed change is driven by the httpclientfactory asp net core integration which will drive many more polly users to the strong named version asp net core has prior decision to be strong named and thus consume strong named assemblies | 0 |
1,252 | 9,786,013,900 | IssuesEvent | 2019-06-09 13:10:06 | dessant/buster | https://api.github.com/repos/dessant/buster | closed | Auto click "I'm not robot" | wontfix-automation | Dear.
You can add functions / options that automatically click on the "I'm not robot" section. I think this is a necessary function, reducing unnecessary tasks.
I am currently using your addon with addon "I'm not a robot captcha clicker" (https://chrome.google.com/webstore/detail/im-not-robot-captcha-clic/ceipnlhmjohemhfpbjdgeigkababhmjc?utm_source= chrome-ntp-icon)
I feel perfect.
Thank you very much. | 1.0 | Auto click "I'm not robot" - Dear.
You can add functions / options that automatically click on the "I'm not robot" section. I think this is a necessary function, reducing unnecessary tasks.
I am currently using your addon with addon "I'm not a robot captcha clicker" (https://chrome.google.com/webstore/detail/im-not-robot-captcha-clic/ceipnlhmjohemhfpbjdgeigkababhmjc?utm_source= chrome-ntp-icon)
I feel perfect.
Thank you very much. | non_priority | auto click i m not robot dear you can add functions options that automatically click on the i m not robot section i think this is a necessary function reducing unnecessary tasks i am currently using your addon with addon i m not a robot captcha clicker chrome ntp icon i feel perfect thank you very much | 0 |
154,119 | 24,250,822,104 | IssuesEvent | 2022-09-27 14:05:20 | pythonbrasil/pybr2022-org | https://api.github.com/repos/pythonbrasil/pybr2022-org | closed | Cartaz para divulgação das Submissões | Designer | ### Campanha
Cartaz para divulgação das Submissões de palestra
### Peça/publicidade solicitada
Será adicionado em universidades/institutos
### Data prevista para uso da arte
- 02/06
### Quais informações devem aparecer na arte
"Python Brasil 2022 "O maior evento de python da america latina agora em MANAUS" "submeta sua palestra"
Podemos adicionar esse QR Code
### Quais formatos necessários
- Tamanho A3
> Ferramenta para verificar [acessibilidade das cores](https://www.toptal.com/designers/colorfilter/) em imagens.
**Para concluir essa atividade, comente com os links dos posts realizados nas redes sociais ou prints, quando divulgação realizada em outros meios**
| 1.0 | Cartaz para divulgação das Submissões - ### Campanha
Cartaz para divulgação das Submissões de palestra
### Peça/publicidade solicitada
Será adicionado em universidades/institutos
### Data prevista para uso da arte
- 02/06
### Quais informações devem aparecer na arte
"Python Brasil 2022 "O maior evento de python da america latina agora em MANAUS" "submeta sua palestra"
Podemos adicionar esse QR Code
### Quais formatos necessários
- Tamanho A3
> Ferramenta para verificar [acessibilidade das cores](https://www.toptal.com/designers/colorfilter/) em imagens.
**Para concluir essa atividade, comente com os links dos posts realizados nas redes sociais ou prints, quando divulgação realizada em outros meios**
| non_priority | cartaz para divulgação das submissões campanha cartaz para divulgação das submissões de palestra peça publicidade solicitada será adicionado em universidades institutos data prevista para uso da arte quais informações devem aparecer na arte python brasil o maior evento de python da america latina agora em manaus submeta sua palestra podemos adicionar esse qr code quais formatos necessários tamanho ferramenta para verificar em imagens para concluir essa atividade comente com os links dos posts realizados nas redes sociais ou prints quando divulgação realizada em outros meios | 0 |
6,175 | 3,348,263,224 | IssuesEvent | 2015-11-17 00:41:50 | CorfuDB/CorfuDB | https://api.github.com/repos/CorfuDB/CorfuDB | reopened | at what level should LogID and epoch be checked? | Code Review | we should probably check unique LogID match and epoch match at one layer, avoiding duplicating many times up the software stack | 1.0 | at what level should LogID and epoch be checked? - we should probably check unique LogID match and epoch match at one layer, avoiding duplicating many times up the software stack | non_priority | at what level should logid and epoch be checked we should probably check unique logid match and epoch match at one layer avoiding duplicating many times up the software stack | 0 |
188,290 | 22,046,282,615 | IssuesEvent | 2022-05-30 02:20:27 | gyungdal/cSync | https://api.github.com/repos/gyungdal/cSync | closed | CVE-2018-20060 (High) detected in requests-v2.9.1 - autoclosed | security vulnerability | ## CVE-2018-20060 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>requestsv2.9.1</b></p></summary>
<p>
<p>A simple, yet elegant HTTP library.</p>
<p>Library home page: <a href=https://github.com/kennethreitz/requests.git>https://github.com/kennethreitz/requests.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/gyungdal/cSync/commit/c8faca656439c1f8b6892f9b06aaeb3200af5c6e">c8faca656439c1f8b6892f9b06aaeb3200af5c6e</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Library Source Files (33)</summary>
<p></p>
<p> * The source files were matched to this source library based on a best effort match. Source libraries are selected from a list of probable public libraries.</p>
<p>
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/util/ssl_.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/utils.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/__init__.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/models.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/api.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/cookies.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/util/request.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/adapters.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/request.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/__init__.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/util/connection.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/util/retry.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/exceptions.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/util/response.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/hooks.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/sessions.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/auth.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/util/url.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/util/timeout.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/response.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/contrib/appengine.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/contrib/ntlmpool.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/poolmanager.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/contrib/pyopenssl.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/filepost.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/fields.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/exceptions.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/connection.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/status_codes.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/_collections.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/util/__init__.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/__init__.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/connectionpool.py
</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>
urllib3 before version 1.23 does not remove the Authorization HTTP header when following a cross-origin redirect (i.e., a redirect that differs in host, port, or scheme). This can allow for credentials in the Authorization header to be exposed to unintended hosts or transmitted in cleartext.
<p>Publish Date: 2018-12-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20060>CVE-2018-20060</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20060">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20060</a></p>
<p>Fix Resolution: 1.23</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-20060 (High) detected in requests-v2.9.1 - autoclosed - ## CVE-2018-20060 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>requestsv2.9.1</b></p></summary>
<p>
<p>A simple, yet elegant HTTP library.</p>
<p>Library home page: <a href=https://github.com/kennethreitz/requests.git>https://github.com/kennethreitz/requests.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/gyungdal/cSync/commit/c8faca656439c1f8b6892f9b06aaeb3200af5c6e">c8faca656439c1f8b6892f9b06aaeb3200af5c6e</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Library Source Files (33)</summary>
<p></p>
<p> * The source files were matched to this source library based on a best effort match. Source libraries are selected from a list of probable public libraries.</p>
<p>
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/util/ssl_.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/utils.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/__init__.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/models.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/api.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/cookies.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/util/request.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/adapters.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/request.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/__init__.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/util/connection.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/util/retry.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/exceptions.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/util/response.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/hooks.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/sessions.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/auth.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/util/url.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/util/timeout.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/response.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/contrib/appengine.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/contrib/ntlmpool.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/poolmanager.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/contrib/pyopenssl.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/filepost.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/fields.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/exceptions.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/connection.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/status_codes.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/_collections.py
- _depth_0/cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/util/__init__.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/__init__.py
- /cSync/reference/pi3dscan/agisoft_python_requests/requests/packages/urllib3/connectionpool.py
</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>
urllib3 before version 1.23 does not remove the Authorization HTTP header when following a cross-origin redirect (i.e., a redirect that differs in host, port, or scheme). This can allow for credentials in the Authorization header to be exposed to unintended hosts or transmitted in cleartext.
<p>Publish Date: 2018-12-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20060>CVE-2018-20060</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20060">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20060</a></p>
<p>Fix Resolution: 1.23</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 requests autoclosed cve high severity vulnerability vulnerable library a simple yet elegant http library library home page a href found in head commit a href library source files the source files were matched to this source library based on a best effort match source libraries are selected from a list of probable public libraries csync reference agisoft python requests requests packages util ssl py csync reference agisoft python requests requests utils py depth csync reference agisoft python requests requests packages init py csync reference agisoft python requests requests models py csync reference agisoft python requests requests api py csync reference agisoft python requests requests cookies py csync reference agisoft python requests requests packages util request py depth csync reference agisoft python requests requests adapters py depth csync reference agisoft python requests requests packages request py csync reference agisoft python requests requests init py csync reference agisoft python requests requests packages util connection py depth csync reference agisoft python requests requests packages util retry py csync reference agisoft python requests requests packages exceptions py depth csync reference agisoft python requests requests packages util response py depth csync reference agisoft python requests requests hooks py depth csync reference agisoft python requests requests sessions py csync reference agisoft python requests requests auth py depth csync reference agisoft python requests requests packages util url py csync reference agisoft python requests requests packages util timeout py depth csync reference agisoft python requests requests packages response py csync reference agisoft python requests requests packages contrib appengine py depth csync reference agisoft python requests requests packages contrib ntlmpool py csync reference agisoft python requests requests packages poolmanager py depth csync reference agisoft python requests requests packages contrib pyopenssl py depth csync reference agisoft python requests requests packages filepost py depth csync reference agisoft python requests requests packages fields py csync reference agisoft python requests requests exceptions py csync reference agisoft python requests requests packages connection py depth csync reference agisoft python requests requests status codes py depth csync reference agisoft python requests requests packages collections py depth csync reference agisoft python requests requests packages util init py csync reference agisoft python requests requests packages init py csync reference agisoft python requests requests packages connectionpool py vulnerability details before version does not remove the authorization http header when following a cross origin redirect i e a redirect that differs in host port or scheme this can allow for credentials in the authorization header to be exposed to unintended hosts or transmitted in cleartext 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 fix resolution step up your open source security game with whitesource | 0 |
43,984 | 7,088,632,843 | IssuesEvent | 2018-01-11 22:15:52 | gotham-rs/gotham | https://api.github.com/repos/gotham-rs/gotham | closed | API design to get hold of a Tokio handle within a handler | documentation feature | As discussed on Gitter with @bradleybeddoes, I'm missing the possibility to send new HTTP requests inside Gotham handlers because currently it's not possible to get a reference to the underlying Tokio event loop.
@bradleybeddoes pointed me to https://github.com/gotham-rs/gotham/blob/953c39b6d5d5134bbab5ab658f1aadc243a68806/src/handler/mod.rs#L151 where other framework state variables are initialized. Unfortunately, I don't see a way of accessing the tokio handle in that function. As a matter of fact the whole Gotham codebase is pretty much unaware of the whole Tokio stuff because the way Gotham apps seem to be started is that the handler is passed to Hyper's server API. Hyper will either create the Tokio core internally, or let you use an existing one (since https://github.com/gotham-rs/gotham/pull/66).
An alternative to having Gotham put the handle reference into the state object would be to use a middleware for that: https://github.com/ChristophWurst/gotham-middleware-tokio. You can find an example usage here: https://github.com/ChristophWurst/gotham-middleware-tokio/blob/master/examples/hyper_client.rs#L22
There seem to be a few problems though. I don't know whether we should use a `Handle`, a `Remote` or let the developer choose. `Handle` cannot be shared across threads. However, Hyper expects a `Handle` rather than a `Remote` for its client, making it a bit cumbersome to use. The remote object does have method to get a handle, [although it's not guaranteed to always get one](https://docs.rs/tokio-core/0.1.11/tokio_core/reactor/struct.Remote.html#method.handle).
This is somewhat related to https://github.com/hyperium/hyper/issues/1002
@bradleybeddoes @smangelsdorf thoughts on how to integrate this in Gotham?
| 1.0 | API design to get hold of a Tokio handle within a handler - As discussed on Gitter with @bradleybeddoes, I'm missing the possibility to send new HTTP requests inside Gotham handlers because currently it's not possible to get a reference to the underlying Tokio event loop.
@bradleybeddoes pointed me to https://github.com/gotham-rs/gotham/blob/953c39b6d5d5134bbab5ab658f1aadc243a68806/src/handler/mod.rs#L151 where other framework state variables are initialized. Unfortunately, I don't see a way of accessing the tokio handle in that function. As a matter of fact the whole Gotham codebase is pretty much unaware of the whole Tokio stuff because the way Gotham apps seem to be started is that the handler is passed to Hyper's server API. Hyper will either create the Tokio core internally, or let you use an existing one (since https://github.com/gotham-rs/gotham/pull/66).
An alternative to having Gotham put the handle reference into the state object would be to use a middleware for that: https://github.com/ChristophWurst/gotham-middleware-tokio. You can find an example usage here: https://github.com/ChristophWurst/gotham-middleware-tokio/blob/master/examples/hyper_client.rs#L22
There seem to be a few problems though. I don't know whether we should use a `Handle`, a `Remote` or let the developer choose. `Handle` cannot be shared across threads. However, Hyper expects a `Handle` rather than a `Remote` for its client, making it a bit cumbersome to use. The remote object does have method to get a handle, [although it's not guaranteed to always get one](https://docs.rs/tokio-core/0.1.11/tokio_core/reactor/struct.Remote.html#method.handle).
This is somewhat related to https://github.com/hyperium/hyper/issues/1002
@bradleybeddoes @smangelsdorf thoughts on how to integrate this in Gotham?
| non_priority | api design to get hold of a tokio handle within a handler as discussed on gitter with bradleybeddoes i m missing the possibility to send new http requests inside gotham handlers because currently it s not possible to get a reference to the underlying tokio event loop bradleybeddoes pointed me to where other framework state variables are initialized unfortunately i don t see a way of accessing the tokio handle in that function as a matter of fact the whole gotham codebase is pretty much unaware of the whole tokio stuff because the way gotham apps seem to be started is that the handler is passed to hyper s server api hyper will either create the tokio core internally or let you use an existing one since an alternative to having gotham put the handle reference into the state object would be to use a middleware for that you can find an example usage here there seem to be a few problems though i don t know whether we should use a handle a remote or let the developer choose handle cannot be shared across threads however hyper expects a handle rather than a remote for its client making it a bit cumbersome to use the remote object does have method to get a handle this is somewhat related to bradleybeddoes smangelsdorf thoughts on how to integrate this in gotham | 0 |
330,233 | 24,251,915,060 | IssuesEvent | 2022-09-27 14:46:28 | castor-software/deptrim | https://api.github.com/repos/castor-software/deptrim | closed | Draft README | documentation | Today it is not clear what the purpose of DepTrim is.
Therefore, it is necessary to decide on:
- Input/Output
- Architecture
- Usage
| 1.0 | Draft README - Today it is not clear what the purpose of DepTrim is.
Therefore, it is necessary to decide on:
- Input/Output
- Architecture
- Usage
| non_priority | draft readme today it is not clear what the purpose of deptrim is therefore it is necessary to decide on input output architecture usage | 0 |
58,565 | 14,435,175,232 | IssuesEvent | 2020-12-07 08:21:13 | Crocoblock/suggestions | https://api.github.com/repos/Crocoblock/suggestions | closed | JetWooBuilder Bundle - Custom Product Order in Grid aso. | Done JetWooBuilder Ready for release | Hey there, stumbling because there is no option to set custom order of product in grid, list aso. As Elementor itself offers the option to manipulate the posts elements query by Query ID I'm wondering if nobody else ever needet such an option?!?!
In my case I need to preorder the products based on three different meta fields what usually would be no problem if there would be such a functionality like QUERY ID in elementors posts element.
Best regards
Dominik | 1.0 | JetWooBuilder Bundle - Custom Product Order in Grid aso. - Hey there, stumbling because there is no option to set custom order of product in grid, list aso. As Elementor itself offers the option to manipulate the posts elements query by Query ID I'm wondering if nobody else ever needet such an option?!?!
In my case I need to preorder the products based on three different meta fields what usually would be no problem if there would be such a functionality like QUERY ID in elementors posts element.
Best regards
Dominik | non_priority | jetwoobuilder bundle custom product order in grid aso hey there stumbling because there is no option to set custom order of product in grid list aso as elementor itself offers the option to manipulate the posts elements query by query id i m wondering if nobody else ever needet such an option in my case i need to preorder the products based on three different meta fields what usually would be no problem if there would be such a functionality like query id in elementors posts element best regards dominik | 0 |
31,875 | 8,766,762,863 | IssuesEvent | 2018-12-17 17:42:11 | apache/trafficcontrol | https://api.github.com/repos/apache/trafficcontrol | closed | error building traffic_portal | Traffic Portal build | Running traffic_portal build in docker on mac, I got this error:
```
Step 7/11 : RUN gem install compass
...
ERROR: Error installing compass:
The last version of rb-inotify (>= 0.9) to support your Ruby & RubyGems was 0.9.10. Try installing it with `gem install rb-inotify -v 0.9.10` and then running the current command again
rb-inotify requires Ruby version >= 2.2. The current ruby version is .
```
| 1.0 | error building traffic_portal - Running traffic_portal build in docker on mac, I got this error:
```
Step 7/11 : RUN gem install compass
...
ERROR: Error installing compass:
The last version of rb-inotify (>= 0.9) to support your Ruby & RubyGems was 0.9.10. Try installing it with `gem install rb-inotify -v 0.9.10` and then running the current command again
rb-inotify requires Ruby version >= 2.2. The current ruby version is .
```
| non_priority | error building traffic portal running traffic portal build in docker on mac i got this error step run gem install compass error error installing compass the last version of rb inotify to support your ruby rubygems was try installing it with gem install rb inotify v and then running the current command again rb inotify requires ruby version the current ruby version is | 0 |
3,286 | 2,834,410,974 | IssuesEvent | 2015-05-26 04:20:31 | TelluriumCrystal/apcalculus | https://api.github.com/repos/TelluriumCrystal/apcalculus | closed | Data Display class has no comments | sloppy code | Please add comments to explain what the various classes do and what happens where. It will take me a lot longer to try reverse-engineer what you did than it will for you to go back and add comments to it. | 1.0 | Data Display class has no comments - Please add comments to explain what the various classes do and what happens where. It will take me a lot longer to try reverse-engineer what you did than it will for you to go back and add comments to it. | non_priority | data display class has no comments please add comments to explain what the various classes do and what happens where it will take me a lot longer to try reverse engineer what you did than it will for you to go back and add comments to it | 0 |
134,784 | 12,627,035,507 | IssuesEvent | 2020-06-14 19:27:51 | jamesjamail/TunnelQuestBot | https://api.github.com/repos/jamesjamail/TunnelQuestBot | closed | Help is inaccurate for some commands | bug documentation good first issue ready for review | The help text for some commands is missing arguments. For example:
`!end watch: <item> (ends a currently running watch)`
`!show watch: <item> (lists details for a watch for entered item - if no item is provided, lists details for all watches)`
These commands actually require a server as well.
This could be handled quickly for the current commands, or may also be closed as a result of #12. | 1.0 | Help is inaccurate for some commands - The help text for some commands is missing arguments. For example:
`!end watch: <item> (ends a currently running watch)`
`!show watch: <item> (lists details for a watch for entered item - if no item is provided, lists details for all watches)`
These commands actually require a server as well.
This could be handled quickly for the current commands, or may also be closed as a result of #12. | non_priority | help is inaccurate for some commands the help text for some commands is missing arguments for example end watch ends a currently running watch show watch lists details for a watch for entered item if no item is provided lists details for all watches these commands actually require a server as well this could be handled quickly for the current commands or may also be closed as a result of | 0 |
349,857 | 31,836,201,163 | IssuesEvent | 2023-09-14 13:40:13 | UtkinIvan/Laba3RPR | https://api.github.com/repos/UtkinIvan/Laba3RPR | closed | Список частей | test | Как: пользователь-капитан, хочу: видеть список частей, чтобы: добавлять части, изменять и удалять их
- [ ] добавлять части
- [ ] изменять части
- [ ] удалять части
| 1.0 | Список частей - Как: пользователь-капитан, хочу: видеть список частей, чтобы: добавлять части, изменять и удалять их
- [ ] добавлять части
- [ ] изменять части
- [ ] удалять части
| non_priority | список частей как пользователь капитан хочу видеть список частей чтобы добавлять части изменять и удалять их добавлять части изменять части удалять части | 0 |
54,723 | 7,920,145,410 | IssuesEvent | 2018-07-04 21:29:24 | mpostol/OPC-UA-OOI | https://api.github.com/repos/mpostol/OPC-UA-OOI | closed | Configuration/Networking/README.MD - broken link | Bug Documentation | Review the document online to fix all broken links.
| 1.0 | Configuration/Networking/README.MD - broken link - Review the document online to fix all broken links.
| non_priority | configuration networking readme md broken link review the document online to fix all broken links | 0 |
49,191 | 12,298,471,157 | IssuesEvent | 2020-05-11 10:34:04 | tsunamayo/Starship-EVO | https://api.github.com/repos/tsunamayo/Starship-EVO | reopened | [New build - DEFAULT] 20w20a: Starting Zone Tutorial | Build Release Note | Tutorial starting zones have been added to the game.
They are made using the game logic.
Changes:
- Preview for the starter block
- Tutorial zone added to the starting point
- Help message popup windows mode
- Help messages can use sprite
Bug Fixes:
#1991 Wrong Canopy hitbox.
#1993 Stronger player gravity field.
Collision for Bast and Trap door.
Secondary paint for Blast and Trap door.
Wrong 3d zone for the volumetric sensor | 1.0 | [New build - DEFAULT] 20w20a: Starting Zone Tutorial - Tutorial starting zones have been added to the game.
They are made using the game logic.
Changes:
- Preview for the starter block
- Tutorial zone added to the starting point
- Help message popup windows mode
- Help messages can use sprite
Bug Fixes:
#1991 Wrong Canopy hitbox.
#1993 Stronger player gravity field.
Collision for Bast and Trap door.
Secondary paint for Blast and Trap door.
Wrong 3d zone for the volumetric sensor | non_priority | starting zone tutorial tutorial starting zones have been added to the game they are made using the game logic changes preview for the starter block tutorial zone added to the starting point help message popup windows mode help messages can use sprite bug fixes wrong canopy hitbox stronger player gravity field collision for bast and trap door secondary paint for blast and trap door wrong zone for the volumetric sensor | 0 |
73,931 | 24,870,570,105 | IssuesEvent | 2022-10-27 14:57:12 | jOOQ/jOOQ | https://api.github.com/repos/jOOQ/jOOQ | opened | QOM.UnmodifiableList can leak internal modifiable lists when lists are nested | T: Defect C: Functionality P: Low E: All Editions | `QOM.UnmodifiableList` protects only its own elements from being modified, but if those elements are again supposed to be `QOM.UnmodifiableList`, they're not (nested lists) | 1.0 | QOM.UnmodifiableList can leak internal modifiable lists when lists are nested - `QOM.UnmodifiableList` protects only its own elements from being modified, but if those elements are again supposed to be `QOM.UnmodifiableList`, they're not (nested lists) | non_priority | qom unmodifiablelist can leak internal modifiable lists when lists are nested qom unmodifiablelist protects only its own elements from being modified but if those elements are again supposed to be qom unmodifiablelist they re not nested lists | 0 |
32,369 | 7,531,103,790 | IssuesEvent | 2018-04-15 00:39:54 | dahall/TaskScheduler | https://api.github.com/repos/dahall/TaskScheduler | closed | "StartWhenAvailable" not checked in Scheduler | codeplex-disc | Hey there,
First of all, thanks for making this Wrapper. It's amazing.
I need to change desktop background every day based on time user picks. If machine is not working I need this task to start after user logs on at some point.
This is the code that I have at the moment :
using (TaskService taskSer = new TaskService())
{
TaskDefinition td = taskSer.NewTask();
DailyTrigger dt = new DailyTrigger();
dt.StartBoundary = new DateTime(DateTime.Now.Year, DateTime.Now.Month, DateTime.Now.Day, startHour.Hours, startHour.Minutes, startHour.Seconds);
taskSer.AddTask("Task", dt, new ExecAction(execPath));
td.Settings.StartWhenAvailable = true;
td.Settings.Compatibility = TaskCompatibility.V2_3;
td.Settings.RestartInterval = TimeSpan.Zero;
}
However, when I go to Task Scheduler, Settings tab, checkbox for starting the task after missing it, is not checked.
How can I set "StartWhenAvailable" checkbox marked through the code ?
I did check Discussions and only found [one](https://taskscheduler.codeplex.com/discussions/398027) topic which covered this question, but it doesn't apply to me as I tried already to set RestartInterval to TimeInterval.Zero. I need this task to be infinite, so I'm not sure how would I set EndBoundry in that case ?
Thanks,
S. M.
Originally posted: 2016-04-07T16:28:58 | 1.0 | "StartWhenAvailable" not checked in Scheduler - Hey there,
First of all, thanks for making this Wrapper. It's amazing.
I need to change desktop background every day based on time user picks. If machine is not working I need this task to start after user logs on at some point.
This is the code that I have at the moment :
using (TaskService taskSer = new TaskService())
{
TaskDefinition td = taskSer.NewTask();
DailyTrigger dt = new DailyTrigger();
dt.StartBoundary = new DateTime(DateTime.Now.Year, DateTime.Now.Month, DateTime.Now.Day, startHour.Hours, startHour.Minutes, startHour.Seconds);
taskSer.AddTask("Task", dt, new ExecAction(execPath));
td.Settings.StartWhenAvailable = true;
td.Settings.Compatibility = TaskCompatibility.V2_3;
td.Settings.RestartInterval = TimeSpan.Zero;
}
However, when I go to Task Scheduler, Settings tab, checkbox for starting the task after missing it, is not checked.
How can I set "StartWhenAvailable" checkbox marked through the code ?
I did check Discussions and only found [one](https://taskscheduler.codeplex.com/discussions/398027) topic which covered this question, but it doesn't apply to me as I tried already to set RestartInterval to TimeInterval.Zero. I need this task to be infinite, so I'm not sure how would I set EndBoundry in that case ?
Thanks,
S. M.
Originally posted: 2016-04-07T16:28:58 | non_priority | startwhenavailable not checked in scheduler hey there first of all thanks for making this wrapper it s amazing i need to change desktop background every day based on time user picks if machine is not working i need this task to start after user logs on at some point this is the code that i have at the moment using taskservice taskser new taskservice taskdefinition td taskser newtask dailytrigger dt new dailytrigger dt startboundary new datetime datetime now year datetime now month datetime now day starthour hours starthour minutes starthour seconds taskser addtask quot task quot dt new execaction execpath td settings startwhenavailable true td settings compatibility taskcompatibility td settings restartinterval timespan zero however when i go to task scheduler settings tab checkbox for starting the task after missing it is not checked how can i set startwhenavailable checkbox marked through the code i did check discussions and only found topic which covered this question but it doesn t apply to me as i tried already to set restartinterval to timeinterval zero i need this task to be infinite so i m not sure how would i set endboundry in that case thanks s m originally posted | 0 |
240,315 | 20,022,404,904 | IssuesEvent | 2022-02-01 17:35:04 | trilinos/Trilinos | https://api.github.com/repos/trilinos/Trilinos | closed | Trilinos PR Testing is down! | type: bug impacting: tests system: gpu autotester | ## Bug Report
@trilinos/developers
### Description
Trilinos PR testing is not flowing smoothly due to capacity problems on one machine. Admins are working on it. | 2.0 | Trilinos PR Testing is down! - ## Bug Report
@trilinos/developers
### Description
Trilinos PR testing is not flowing smoothly due to capacity problems on one machine. Admins are working on it. | non_priority | trilinos pr testing is down bug report trilinos developers description trilinos pr testing is not flowing smoothly due to capacity problems on one machine admins are working on it | 0 |
101,750 | 16,528,033,950 | IssuesEvent | 2021-05-26 23:32:14 | alpersonalwebsite/cards | https://api.github.com/repos/alpersonalwebsite/cards | opened | WS-2019-0307 (Medium) detected in mem-1.1.0.tgz | security vulnerability | ## WS-2019-0307 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mem-1.1.0.tgz</b></p></summary>
<p>Memoize functions - An optimization used to speed up consecutive function calls by caching the result of calls with identical input</p>
<p>Library home page: <a href="https://registry.npmjs.org/mem/-/mem-1.1.0.tgz">https://registry.npmjs.org/mem/-/mem-1.1.0.tgz</a></p>
<p>Path to dependency file: cards/package.json</p>
<p>Path to vulnerable library: cards/node_modules/mem</p>
<p>
Dependency Hierarchy:
- jest-expo-32.0.1.tgz (Root Library)
- jest-23.6.0.tgz
- jest-cli-23.6.0.tgz
- yargs-11.1.0.tgz
- os-locale-2.1.0.tgz
- :x: **mem-1.1.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/alpersonalwebsite/cards/commit/959053f33fb963a3ec04cdb4be3c6f705f0312c6">959053f33fb963a3ec04cdb4be3c6f705f0312c6</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 'mem' before v4.0.0 there is a Denial of Service (DoS) vulnerability as a result of a failure in removal old values from the cache.
<p>Publish Date: 2018-08-27
<p>URL: <a href=https://github.com/sindresorhus/mem/commit/da4e4398cb27b602de3bd55f746efa9b4a31702b>WS-2019-0307</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.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1084">https://www.npmjs.com/advisories/1084</a></p>
<p>Release Date: 2019-12-01</p>
<p>Fix Resolution: mem - 4.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2019-0307 (Medium) detected in mem-1.1.0.tgz - ## WS-2019-0307 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mem-1.1.0.tgz</b></p></summary>
<p>Memoize functions - An optimization used to speed up consecutive function calls by caching the result of calls with identical input</p>
<p>Library home page: <a href="https://registry.npmjs.org/mem/-/mem-1.1.0.tgz">https://registry.npmjs.org/mem/-/mem-1.1.0.tgz</a></p>
<p>Path to dependency file: cards/package.json</p>
<p>Path to vulnerable library: cards/node_modules/mem</p>
<p>
Dependency Hierarchy:
- jest-expo-32.0.1.tgz (Root Library)
- jest-23.6.0.tgz
- jest-cli-23.6.0.tgz
- yargs-11.1.0.tgz
- os-locale-2.1.0.tgz
- :x: **mem-1.1.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/alpersonalwebsite/cards/commit/959053f33fb963a3ec04cdb4be3c6f705f0312c6">959053f33fb963a3ec04cdb4be3c6f705f0312c6</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 'mem' before v4.0.0 there is a Denial of Service (DoS) vulnerability as a result of a failure in removal old values from the cache.
<p>Publish Date: 2018-08-27
<p>URL: <a href=https://github.com/sindresorhus/mem/commit/da4e4398cb27b602de3bd55f746efa9b4a31702b>WS-2019-0307</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.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1084">https://www.npmjs.com/advisories/1084</a></p>
<p>Release Date: 2019-12-01</p>
<p>Fix Resolution: mem - 4.0.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 | ws medium detected in mem tgz ws medium severity vulnerability vulnerable library mem tgz memoize functions an optimization used to speed up consecutive function calls by caching the result of calls with identical input library home page a href path to dependency file cards package json path to vulnerable library cards node modules mem dependency hierarchy jest expo tgz root library jest tgz jest cli tgz yargs tgz os locale tgz x mem tgz vulnerable library found in head commit a href vulnerability details in mem before there is a denial of service dos vulnerability as a result of a failure in removal old values from the cache publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution mem step up your open source security game with whitesource | 0 |
54,725 | 6,402,466,461 | IssuesEvent | 2017-08-06 09:46:48 | FlightControl-Master/MOOSE | https://api.github.com/repos/FlightControl-Master/MOOSE | closed | AI_A2A_GCICAP: - Planes spawn at a very low alititude (causes issues if close to coast and ridges are near by) | enhancement implemented ready for testing | Observed several AI planes spawn fly for 20 seconds and then crash straight into hillside
They spawned at Gelendzhik and after maybe 10-20 seconds crashed into ridge to NE of this airport
Witnessed this several times
REQUEST: - Make the default ALT to spawn AI aircraft to be 1000m above the airfield
thanks | 1.0 | AI_A2A_GCICAP: - Planes spawn at a very low alititude (causes issues if close to coast and ridges are near by) - Observed several AI planes spawn fly for 20 seconds and then crash straight into hillside
They spawned at Gelendzhik and after maybe 10-20 seconds crashed into ridge to NE of this airport
Witnessed this several times
REQUEST: - Make the default ALT to spawn AI aircraft to be 1000m above the airfield
thanks | non_priority | ai gcicap planes spawn at a very low alititude causes issues if close to coast and ridges are near by observed several ai planes spawn fly for seconds and then crash straight into hillside they spawned at gelendzhik and after maybe seconds crashed into ridge to ne of this airport witnessed this several times request make the default alt to spawn ai aircraft to be above the airfield thanks | 0 |
29,001 | 8,248,310,343 | IssuesEvent | 2018-09-11 18:03:32 | idris-lang/Idris-dev | https://api.github.com/repos/idris-lang/Idris-dev | closed | pow broken with C backend? | C-Low Hanging Fruit G-C Backend S-Normal U-Build System W-Debugging | When I compile the following code
``` idris
module Main
main : IO ()
main = do
print $ (pow 2 200)
```
with `idris test.idr -o test` then all I get is
``` shell
# ./test
0
#
```
| 1.0 | pow broken with C backend? - When I compile the following code
``` idris
module Main
main : IO ()
main = do
print $ (pow 2 200)
```
with `idris test.idr -o test` then all I get is
``` shell
# ./test
0
#
```
| non_priority | pow broken with c backend when i compile the following code idris module main main io main do print pow with idris test idr o test then all i get is shell test | 0 |
12,746 | 8,712,141,490 | IssuesEvent | 2018-12-06 21:19:01 | tuxtof/calm | https://api.github.com/repos/tuxtof/calm | closed | WS-2018-0125 Medium Severity Vulnerability detected by WhiteSource | security vulnerability | ## WS-2018-0125 - Medium Severity Vulnerability
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-core-2.6.5.jar</b></p></summary>
<p>Core Jackson abstractions, basic JSON streaming API implementation</p>
<p>path: /calm/blueprint/wildfly/demo/petclinic/WEB-INF/lib/jackson-core-2.6.5.jar</p>
<p>
<p>Library home page: <a href=https://github.com/FasterXML/jackson-core>https://github.com/FasterXML/jackson-core</a></p>
Dependency Hierarchy:
- :x: **jackson-core-2.6.5.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
OutOfMemoryError when writing BigDecimal In Jackson Core before version 2.7.6.
When enabled the WRITE_BIGDECIMAL_AS_PLAIN setting, Jackson will attempt to write out the whole number, no matter how large the exponent.
<p>Publish Date: 2018-06-24
<p>URL: <a href=>WS-2018-0125</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Change files</p>
<p>Origin: <a href="https://github.com/FasterXML/jackson-core/commit/96642978dcf1b69cba68ec72cb2f652d59a8b5be">https://github.com/FasterXML/jackson-core/commit/96642978dcf1b69cba68ec72cb2f652d59a8b5be</a></p>
<p>Release Date: 2016-08-25</p>
<p>Fix Resolution: Replace or update the following files: GeneratorBase.java, WriterBasedJsonGenerator.java, TestJsonGeneratorFeatures.java, UTF8JsonGenerator.java, VERSION</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2018-0125 Medium Severity Vulnerability detected by WhiteSource - ## WS-2018-0125 - Medium Severity Vulnerability
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-core-2.6.5.jar</b></p></summary>
<p>Core Jackson abstractions, basic JSON streaming API implementation</p>
<p>path: /calm/blueprint/wildfly/demo/petclinic/WEB-INF/lib/jackson-core-2.6.5.jar</p>
<p>
<p>Library home page: <a href=https://github.com/FasterXML/jackson-core>https://github.com/FasterXML/jackson-core</a></p>
Dependency Hierarchy:
- :x: **jackson-core-2.6.5.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
OutOfMemoryError when writing BigDecimal In Jackson Core before version 2.7.6.
When enabled the WRITE_BIGDECIMAL_AS_PLAIN setting, Jackson will attempt to write out the whole number, no matter how large the exponent.
<p>Publish Date: 2018-06-24
<p>URL: <a href=>WS-2018-0125</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Change files</p>
<p>Origin: <a href="https://github.com/FasterXML/jackson-core/commit/96642978dcf1b69cba68ec72cb2f652d59a8b5be">https://github.com/FasterXML/jackson-core/commit/96642978dcf1b69cba68ec72cb2f652d59a8b5be</a></p>
<p>Release Date: 2016-08-25</p>
<p>Fix Resolution: Replace or update the following files: GeneratorBase.java, WriterBasedJsonGenerator.java, TestJsonGeneratorFeatures.java, UTF8JsonGenerator.java, VERSION</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | ws medium severity vulnerability detected by whitesource ws medium severity vulnerability vulnerable library jackson core jar core jackson abstractions basic json streaming api implementation path calm blueprint wildfly demo petclinic web inf lib jackson core jar library home page a href dependency hierarchy x jackson core jar vulnerable library vulnerability details outofmemoryerror when writing bigdecimal in jackson core before version when enabled the write bigdecimal as plain setting jackson will attempt to write out the whole number no matter how large the exponent publish date url ws cvss score details base score metrics not available suggested fix type change files origin a href release date fix resolution replace or update the following files generatorbase java writerbasedjsongenerator java testjsongeneratorfeatures java java version step up your open source security game with whitesource | 0 |
55,673 | 6,489,290,224 | IssuesEvent | 2017-08-21 00:36:10 | FireFly-WoW/FireFly-IssueTracker | https://api.github.com/repos/FireFly-WoW/FireFly-IssueTracker | closed | feralas midsummer festival fire | Status: Needs Testing | **Description:**
CHANGEME: Describe the issue here
**Current behaviour:**
CHANGEME: Explain to us (if/how) it currently works.
**Expected behaviour:**
CHANGEME: Explain to us how the issue is supposed to work.
**Steps to reproduce the problem:**
1. Step 1
2. Step 2
3. Step 3
**Screenshots:**
url...
url...
url...
| 1.0 | feralas midsummer festival fire - **Description:**
CHANGEME: Describe the issue here
**Current behaviour:**
CHANGEME: Explain to us (if/how) it currently works.
**Expected behaviour:**
CHANGEME: Explain to us how the issue is supposed to work.
**Steps to reproduce the problem:**
1. Step 1
2. Step 2
3. Step 3
**Screenshots:**
url...
url...
url...
| non_priority | feralas midsummer festival fire description changeme describe the issue here current behaviour changeme explain to us if how it currently works expected behaviour changeme explain to us how the issue is supposed to work steps to reproduce the problem step step step screenshots url url url | 0 |
3,382 | 4,381,385,876 | IssuesEvent | 2016-08-06 06:35:35 | zcash/zcash | https://api.github.com/repos/zcash/zcash | closed | Select feasible Equihash Parameters | performance PoW and mining SECURITY | We're using reduced parameters at the moment because of an unoptimized implementation. | True | Select feasible Equihash Parameters - We're using reduced parameters at the moment because of an unoptimized implementation. | non_priority | select feasible equihash parameters we re using reduced parameters at the moment because of an unoptimized implementation | 0 |
286,951 | 31,800,780,802 | IssuesEvent | 2023-09-13 10:57:30 | Trinadh465/external_tcpdump_CVE-2018-14879 | https://api.github.com/repos/Trinadh465/external_tcpdump_CVE-2018-14879 | opened | CVE-2018-14461 (High) detected in platform_external_tcpdumpandroid-mainline-12.0.0_r17 | Mend: dependency security vulnerability | ## CVE-2018-14461 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>platform_external_tcpdumpandroid-mainline-12.0.0_r17</b></p></summary>
<p>
<p>Library home page: <a href=https://github.com/aosp-mirror/platform_external_tcpdump.git>https://github.com/aosp-mirror/platform_external_tcpdump.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Trinadh465/external_tcpdump_CVE-2018-14879/commit/5d281056614b8b3c7c812b3ac3ad7b4911424849">5d281056614b8b3c7c812b3ac3ad7b4911424849</a></p>
<p>Found in base branch: <b>main</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>/print-ldp.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>
The LDP parser in tcpdump before 4.9.3 has a buffer over-read in print-ldp.c:ldp_tlv_print().
<p>Publish Date: 2019-10-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-14461>CVE-2018-14461</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-2018-14461">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14461</a></p>
<p>Release Date: 2019-10-03</p>
<p>Fix Resolution: 4.9.3</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-14461 (High) detected in platform_external_tcpdumpandroid-mainline-12.0.0_r17 - ## CVE-2018-14461 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>platform_external_tcpdumpandroid-mainline-12.0.0_r17</b></p></summary>
<p>
<p>Library home page: <a href=https://github.com/aosp-mirror/platform_external_tcpdump.git>https://github.com/aosp-mirror/platform_external_tcpdump.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Trinadh465/external_tcpdump_CVE-2018-14879/commit/5d281056614b8b3c7c812b3ac3ad7b4911424849">5d281056614b8b3c7c812b3ac3ad7b4911424849</a></p>
<p>Found in base branch: <b>main</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>/print-ldp.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>
The LDP parser in tcpdump before 4.9.3 has a buffer over-read in print-ldp.c:ldp_tlv_print().
<p>Publish Date: 2019-10-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-14461>CVE-2018-14461</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-2018-14461">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14461</a></p>
<p>Release Date: 2019-10-03</p>
<p>Fix Resolution: 4.9.3</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 platform external tcpdumpandroid mainline cve high severity vulnerability vulnerable library platform external tcpdumpandroid mainline library home page a href found in head commit a href found in base branch main vulnerable source files print ldp c vulnerability details the ldp parser in tcpdump before has a buffer over read in print ldp c ldp tlv print publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
33,285 | 7,083,852,295 | IssuesEvent | 2018-01-11 02:51:45 | cakephp/cakephp | https://api.github.com/repos/cakephp/cakephp | closed | InstanceConfigTrait triggers TreeBehavior errors | Defect On hold behaviors | This is a (multiple allowed):
* [x] bug
* [ ] enhancement
* [ ] feature-discussion (RFC)
```bash
sdustinh@sdustinh:~/github/cakephp/app$ php --version
PHP 7.1.12-3+ubuntu16.04.1+deb.sury.org+1 (cli) (built: Dec 14 2017 15:37:13) ( NTS )
Copyright (c) 1997-2017 The PHP Group
Zend Engine v3.1.0, Copyright (c) 1998-2017 Zend Technologies
with Zend OPcache v7.1.12-3+ubuntu16.04.1+deb.sury.org+1, Copyright (c) 1999-2017, by Zend Technologies
with Xdebug v2.5.5, Copyright (c) 2002-2017, by Derick Rethans
sdustinh@sdustinh:~/github/cakephp/app$ mysql --version
mysql Ver 14.14 Distrib 5.7.20, for Linux (x86_64) using EditLine wrapper
sdustinh@sdustinh:~/github/cakephp/app$ composer show cakephp/*
cakephp/bake 1.5.4 Bake plugin for CakePHP 3
cakephp/cakephp 3.5.6 The CakePHP framework
cakephp/cakephp-codesniffer 3.0.1 CakePHP CodeSniffer Standards
cakephp/chronos 1.1.2 A simple API extension for DateTime.
cakephp/debug_kit 3.11.2 CakePHP Debug Kit
cakephp/elastic-search 0.3.5 An Elastic Search datasource and data mapper for CakePHP 3.0
cakephp/migrations 1.7.1 Database Migration plugin for CakePHP 3.0 based on Phinx
cakephp/plugin-installer 1.0.0 A composer installer for CakePHP 3.0+ plugins.
```
### What you did
```php
public function afterSave(Event $event, EntityInterface $entity, ArrayObject $options)
{
// Remove the scope from the tree behavior
$this->behaviors()->get('Tree')->setConfig('scope', null);
}
public function beforeSave(Event $event, EntityInterface $entity, ArrayObject $options)
{
// Scope the tree behavior
$this->behaviors()->get('Tree')->setConfig(
'scope',
function ($query) use ($entity) {
return $query->where([$query->repository()->aliasField('name') => $entity->get('root_id')]);
}
);
}
```
### What happened
The `InstanceConfigTrait` does not allow resetting a configuration property with a default value if that value was `null`. It actually deletes the property which causes a bunch of errors for code that does not use `$this->getConfig()` directly. This will cause the `TreeBehavior` to trigger many warnings that the configuration does not exist. I'm not really sure if this should be considered a bug with the `InstanceConfigTrait` or if the `TreeBehavior` should be udated to use `$this->getConfig('scope')` instead of reading from a `$config`. I would imagine the latter is easier, but I don't know if it really solves the problem globally. | 1.0 | InstanceConfigTrait triggers TreeBehavior errors - This is a (multiple allowed):
* [x] bug
* [ ] enhancement
* [ ] feature-discussion (RFC)
```bash
sdustinh@sdustinh:~/github/cakephp/app$ php --version
PHP 7.1.12-3+ubuntu16.04.1+deb.sury.org+1 (cli) (built: Dec 14 2017 15:37:13) ( NTS )
Copyright (c) 1997-2017 The PHP Group
Zend Engine v3.1.0, Copyright (c) 1998-2017 Zend Technologies
with Zend OPcache v7.1.12-3+ubuntu16.04.1+deb.sury.org+1, Copyright (c) 1999-2017, by Zend Technologies
with Xdebug v2.5.5, Copyright (c) 2002-2017, by Derick Rethans
sdustinh@sdustinh:~/github/cakephp/app$ mysql --version
mysql Ver 14.14 Distrib 5.7.20, for Linux (x86_64) using EditLine wrapper
sdustinh@sdustinh:~/github/cakephp/app$ composer show cakephp/*
cakephp/bake 1.5.4 Bake plugin for CakePHP 3
cakephp/cakephp 3.5.6 The CakePHP framework
cakephp/cakephp-codesniffer 3.0.1 CakePHP CodeSniffer Standards
cakephp/chronos 1.1.2 A simple API extension for DateTime.
cakephp/debug_kit 3.11.2 CakePHP Debug Kit
cakephp/elastic-search 0.3.5 An Elastic Search datasource and data mapper for CakePHP 3.0
cakephp/migrations 1.7.1 Database Migration plugin for CakePHP 3.0 based on Phinx
cakephp/plugin-installer 1.0.0 A composer installer for CakePHP 3.0+ plugins.
```
### What you did
```php
public function afterSave(Event $event, EntityInterface $entity, ArrayObject $options)
{
// Remove the scope from the tree behavior
$this->behaviors()->get('Tree')->setConfig('scope', null);
}
public function beforeSave(Event $event, EntityInterface $entity, ArrayObject $options)
{
// Scope the tree behavior
$this->behaviors()->get('Tree')->setConfig(
'scope',
function ($query) use ($entity) {
return $query->where([$query->repository()->aliasField('name') => $entity->get('root_id')]);
}
);
}
```
### What happened
The `InstanceConfigTrait` does not allow resetting a configuration property with a default value if that value was `null`. It actually deletes the property which causes a bunch of errors for code that does not use `$this->getConfig()` directly. This will cause the `TreeBehavior` to trigger many warnings that the configuration does not exist. I'm not really sure if this should be considered a bug with the `InstanceConfigTrait` or if the `TreeBehavior` should be udated to use `$this->getConfig('scope')` instead of reading from a `$config`. I would imagine the latter is easier, but I don't know if it really solves the problem globally. | non_priority | instanceconfigtrait triggers treebehavior errors this is a multiple allowed bug enhancement feature discussion rfc bash sdustinh sdustinh github cakephp app php version php deb sury org cli built dec nts copyright c the php group zend engine copyright c zend technologies with zend opcache deb sury org copyright c by zend technologies with xdebug copyright c by derick rethans sdustinh sdustinh github cakephp app mysql version mysql ver distrib for linux using editline wrapper sdustinh sdustinh github cakephp app composer show cakephp cakephp bake bake plugin for cakephp cakephp cakephp the cakephp framework cakephp cakephp codesniffer cakephp codesniffer standards cakephp chronos a simple api extension for datetime cakephp debug kit cakephp debug kit cakephp elastic search an elastic search datasource and data mapper for cakephp cakephp migrations database migration plugin for cakephp based on phinx cakephp plugin installer a composer installer for cakephp plugins what you did php public function aftersave event event entityinterface entity arrayobject options remove the scope from the tree behavior this behaviors get tree setconfig scope null public function beforesave event event entityinterface entity arrayobject options scope the tree behavior this behaviors get tree setconfig scope function query use entity return query where what happened the instanceconfigtrait does not allow resetting a configuration property with a default value if that value was null it actually deletes the property which causes a bunch of errors for code that does not use this getconfig directly this will cause the treebehavior to trigger many warnings that the configuration does not exist i m not really sure if this should be considered a bug with the instanceconfigtrait or if the treebehavior should be udated to use this getconfig scope instead of reading from a config i would imagine the latter is easier but i don t know if it really solves the problem globally | 0 |
5,614 | 28,095,918,784 | IssuesEvent | 2023-03-30 15:46:51 | bazelbuild/intellij | https://api.github.com/repos/bazelbuild/intellij | closed | Import incorrect package name prevents 221 build //aswb:aswb_bazel_zip failure | type: bug product: Android Studio awaiting-maintainer | ### Description of the bug:
`bazel build //aswb:aswb_bazel_zip --define=ij_product=android-studio-2022.1` fails because of the import being incorrectly specified in the [DeploymentTimingReporterTask.java](https://github.com/bazelbuild/intellij/blob/master/aswb/sdkcompat/as221/com/google/idea/blaze/android/run/binary/DeploymentTimingReporterTask.java#L18) file
`import com.android.tool.idea.BaseAsCompat;` should be `import com.android.tools.idea.BaseAsCompat;`
### What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
attempt to build using the `bazel build //aswb:aswb_bazel_zip --define=ij_product=android-studio-2022.1`
### Which Intellij IDE are you using? Please provide the specific version.
2022.1
### What programming languages and tools are you using? Please provide specific versions.
Java
### What Bazel plugin version are you using?
_No response_
### Have you found anything relevant by searching the web?
_No response_
### Any other information, logs, or outputs that you want to share?
_No response_ | True | Import incorrect package name prevents 221 build //aswb:aswb_bazel_zip failure - ### Description of the bug:
`bazel build //aswb:aswb_bazel_zip --define=ij_product=android-studio-2022.1` fails because of the import being incorrectly specified in the [DeploymentTimingReporterTask.java](https://github.com/bazelbuild/intellij/blob/master/aswb/sdkcompat/as221/com/google/idea/blaze/android/run/binary/DeploymentTimingReporterTask.java#L18) file
`import com.android.tool.idea.BaseAsCompat;` should be `import com.android.tools.idea.BaseAsCompat;`
### What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
attempt to build using the `bazel build //aswb:aswb_bazel_zip --define=ij_product=android-studio-2022.1`
### Which Intellij IDE are you using? Please provide the specific version.
2022.1
### What programming languages and tools are you using? Please provide specific versions.
Java
### What Bazel plugin version are you using?
_No response_
### Have you found anything relevant by searching the web?
_No response_
### Any other information, logs, or outputs that you want to share?
_No response_ | non_priority | import incorrect package name prevents build aswb aswb bazel zip failure description of the bug bazel build aswb aswb bazel zip define ij product android studio fails because of the import being incorrectly specified in the file import com android tool idea baseascompat should be import com android tools idea baseascompat what s the simplest easiest way to reproduce this bug please provide a minimal example if possible attempt to build using the bazel build aswb aswb bazel zip define ij product android studio which intellij ide are you using please provide the specific version what programming languages and tools are you using please provide specific versions java what bazel plugin version are you using no response have you found anything relevant by searching the web no response any other information logs or outputs that you want to share no response | 0 |
143,333 | 22,032,889,374 | IssuesEvent | 2022-05-28 05:31:17 | towhee-io/towhee | https://api.github.com/repos/towhee-io/towhee | closed | [DesignProposal]: towhee command line tool for pipeline serve | stale kind/design-proposal | ### Background and Motivation
There are many predefined pipelines and operators on towhee hub. The users may want to deploy the pipelines and operators to cloud platforms.
### Design
Provide a command-line tool for pipeline/operator serving:
```shell
$ towhee serve -h 127.0.0.1 -p 8080 -r /app/myop towhee/image-embedding
```
towhee serve [-h host] [-p port] [-r route] [-D arg=val -D arg=val] pipeline/operator_name
### Pros and Cons
_No response_
### Anything else? (Additional Context)
_No response_ | 1.0 | [DesignProposal]: towhee command line tool for pipeline serve - ### Background and Motivation
There are many predefined pipelines and operators on towhee hub. The users may want to deploy the pipelines and operators to cloud platforms.
### Design
Provide a command-line tool for pipeline/operator serving:
```shell
$ towhee serve -h 127.0.0.1 -p 8080 -r /app/myop towhee/image-embedding
```
towhee serve [-h host] [-p port] [-r route] [-D arg=val -D arg=val] pipeline/operator_name
### Pros and Cons
_No response_
### Anything else? (Additional Context)
_No response_ | non_priority | towhee command line tool for pipeline serve background and motivation there are many predefined pipelines and operators on towhee hub the users may want to deploy the pipelines and operators to cloud platforms design provide a command line tool for pipeline operator serving shell towhee serve h p r app myop towhee image embedding towhee serve pipeline operator name pros and cons no response anything else additional context no response | 0 |
16,710 | 10,555,026,901 | IssuesEvent | 2019-10-03 20:50:39 | NetsBlox/NetsBlox | https://api.github.com/repos/NetsBlox/NetsBlox | closed | Add Games, Science, and Climate categories | enhancement services | As categorizing services is now supported (as of #2505), we should add categories for Games, Science, and Climate. | 1.0 | Add Games, Science, and Climate categories - As categorizing services is now supported (as of #2505), we should add categories for Games, Science, and Climate. | non_priority | add games science and climate categories as categorizing services is now supported as of we should add categories for games science and climate | 0 |
82,013 | 23,643,026,142 | IssuesEvent | 2022-08-25 18:59:55 | microsoft/fluentui | https://api.github.com/repos/microsoft/fluentui | closed | [Bug]: package.json 8.72.0 missing DirectionalHint and ThemeProvider exports | Area: Build System Needs: Discussion Help Wanted ✨ Fluent UI react (v8) | ### Library
React / v8 (@fluentui/react)
### System Info
```shell
System:
OS: Windows 10 10.0.19044
CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
Memory: 9.52 GB / 31.88 GB
Browsers:
Edge: Spartan (44.19041.1266.0), Chromium (102.0.1245.30)
Internet Explorer: 11.0.19041.1566
```
### Are you reporting Accessibility issue?
no
### Reproduction
https://aka.ms/fluentpen
### Bug Description
## Actual Behavior
```
import { ThemeProvider } from "@fluentui/react/lib/utilities/ThemeProvider";
import { DirectionalHint } from "@fluentui/react/lib/common/DirectionalHint";
```
WebPack 5 claims these are not exported at build time
## Expected Behavior
Build should work.
## Correction seems to be in package.json by adding:
```
"./lib/common/DirectionalHint": {
"types": "./lib/common/DirectionalHint.d.ts",
"import": "./lib/common/DirectionalHint.js",
"require": "./lib-commonjs/common/DirectionalHint.js"
},
"./lib/utilities/ThemeProvider": {
"types": "./lib/utilities/ThemeProvider/ThemeProvider.d.ts",
"import": "./lib/utilities/ThemeProvider/ThemeProvider.js",
"require": "./lib-commonjs/utilities/ThemeProvider/ThemeProvider.js"
},
```
to this list of exports.
### Logs
```shell
ERROR in ./src/components/OrderBilling/OrderSummary.tsx 41:26-79
Module not found: Error: Package path ./lib/common/DirectionalHint is not exported from package C:\...\node_modules\@fluentui\react (see exports field in C:\...\node_modules\@fluentui\react\package.json)
ERROR in ./src/taskpane/index.tsx 45:24-78
Module not found: Error: Package path ./lib/utilities/ThemeProvider is not exported from package C:\...\node_modules\@fluentui\react (see exports field in C:\...\node_modules\@fluentui\react\package.json)
```
### Requested priority
Normal
### Products/sites affected
_No response_
### Are you willing to submit a PR to fix?
no
### Validations
- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- [X] The provided reproduction is a minimal reproducible example of the bug. | 1.0 | [Bug]: package.json 8.72.0 missing DirectionalHint and ThemeProvider exports - ### Library
React / v8 (@fluentui/react)
### System Info
```shell
System:
OS: Windows 10 10.0.19044
CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
Memory: 9.52 GB / 31.88 GB
Browsers:
Edge: Spartan (44.19041.1266.0), Chromium (102.0.1245.30)
Internet Explorer: 11.0.19041.1566
```
### Are you reporting Accessibility issue?
no
### Reproduction
https://aka.ms/fluentpen
### Bug Description
## Actual Behavior
```
import { ThemeProvider } from "@fluentui/react/lib/utilities/ThemeProvider";
import { DirectionalHint } from "@fluentui/react/lib/common/DirectionalHint";
```
WebPack 5 claims these are not exported at build time
## Expected Behavior
Build should work.
## Correction seems to be in package.json by adding:
```
"./lib/common/DirectionalHint": {
"types": "./lib/common/DirectionalHint.d.ts",
"import": "./lib/common/DirectionalHint.js",
"require": "./lib-commonjs/common/DirectionalHint.js"
},
"./lib/utilities/ThemeProvider": {
"types": "./lib/utilities/ThemeProvider/ThemeProvider.d.ts",
"import": "./lib/utilities/ThemeProvider/ThemeProvider.js",
"require": "./lib-commonjs/utilities/ThemeProvider/ThemeProvider.js"
},
```
to this list of exports.
### Logs
```shell
ERROR in ./src/components/OrderBilling/OrderSummary.tsx 41:26-79
Module not found: Error: Package path ./lib/common/DirectionalHint is not exported from package C:\...\node_modules\@fluentui\react (see exports field in C:\...\node_modules\@fluentui\react\package.json)
ERROR in ./src/taskpane/index.tsx 45:24-78
Module not found: Error: Package path ./lib/utilities/ThemeProvider is not exported from package C:\...\node_modules\@fluentui\react (see exports field in C:\...\node_modules\@fluentui\react\package.json)
```
### Requested priority
Normal
### Products/sites affected
_No response_
### Are you willing to submit a PR to fix?
no
### Validations
- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- [X] The provided reproduction is a minimal reproducible example of the bug. | non_priority | package json missing directionalhint and themeprovider exports library react fluentui react system info shell system os windows cpu intel r core tm cpu memory gb gb browsers edge spartan chromium internet explorer are you reporting accessibility issue no reproduction bug description actual behavior import themeprovider from fluentui react lib utilities themeprovider import directionalhint from fluentui react lib common directionalhint webpack claims these are not exported at build time expected behavior build should work correction seems to be in package json by adding lib common directionalhint types lib common directionalhint d ts import lib common directionalhint js require lib commonjs common directionalhint js lib utilities themeprovider types lib utilities themeprovider themeprovider d ts import lib utilities themeprovider themeprovider js require lib commonjs utilities themeprovider themeprovider js to this list of exports logs shell error in src components orderbilling ordersummary tsx module not found error package path lib common directionalhint is not exported from package c node modules fluentui react see exports field in c node modules fluentui react package json error in src taskpane index tsx module not found error package path lib utilities themeprovider is not exported from package c node modules fluentui react see exports field in c node modules fluentui react package json requested priority normal products sites affected no response are you willing to submit a pr to fix no validations check that there isn t already an issue that reports the same bug to avoid creating a duplicate the provided reproduction is a minimal reproducible example of the bug | 0 |
339,378 | 30,444,141,003 | IssuesEvent | 2023-07-15 12:52:38 | WiIIiam278/HuskHomes | https://api.github.com/repos/WiIIiam278/HuskHomes | closed | Marks of HuskHomes are not showing in BlueMap on Fabric | type: bug status: needs testing type: hook platform: fabric | It appears that warps and public homes of HuskHomes are not showing in BlueMap under the Fabric platform, and there is no related information in the backend log. I'm sure they are all turned on in the configuration file. I will provide more tests and screenshots later.
<html>
<body>
<!--StartFragment-->
environment | version
-- | --
Java | azul/prime:17
HuskHomes | 4.4.1
Fabric | 0.14.21
Minecraft | 1.20.1
BlueMap | 3.14
<!--EndFragment-->
</body>
</html> | 1.0 | Marks of HuskHomes are not showing in BlueMap on Fabric - It appears that warps and public homes of HuskHomes are not showing in BlueMap under the Fabric platform, and there is no related information in the backend log. I'm sure they are all turned on in the configuration file. I will provide more tests and screenshots later.
<html>
<body>
<!--StartFragment-->
environment | version
-- | --
Java | azul/prime:17
HuskHomes | 4.4.1
Fabric | 0.14.21
Minecraft | 1.20.1
BlueMap | 3.14
<!--EndFragment-->
</body>
</html> | non_priority | marks of huskhomes are not showing in bluemap on fabric it appears that warps and public homes of huskhomes are not showing in bluemap under the fabric platform and there is no related information in the backend log i m sure they are all turned on in the configuration file i will provide more tests and screenshots later environment version java azul prime huskhomes fabric minecraft bluemap | 0 |
78,926 | 15,094,899,120 | IssuesEvent | 2021-02-07 08:43:43 | joomla/joomla-cms | https://api.github.com/repos/joomla/joomla-cms | closed | [4b6] Override created message twice | No Code Attached Yet good first issue | ### Steps to reproduce the issue
Create an override in Joomla 4 admin
### Expected result
"Override created in /templates/cassiopeia/html/mod_banners"
### Actual result
Two messages - one is enough!
<img width="1031" alt="Screenshot 2021-01-08 at 14 28 36" src="https://user-images.githubusercontent.com/400092/104026432-ce7e8900-51bd-11eb-9fec-3d288783b081.png">
| 1.0 | [4b6] Override created message twice - ### Steps to reproduce the issue
Create an override in Joomla 4 admin
### Expected result
"Override created in /templates/cassiopeia/html/mod_banners"
### Actual result
Two messages - one is enough!
<img width="1031" alt="Screenshot 2021-01-08 at 14 28 36" src="https://user-images.githubusercontent.com/400092/104026432-ce7e8900-51bd-11eb-9fec-3d288783b081.png">
| non_priority | override created message twice steps to reproduce the issue create an override in joomla admin expected result override created in templates cassiopeia html mod banners actual result two messages one is enough img width alt screenshot at src | 0 |
13,303 | 8,180,577,024 | IssuesEvent | 2018-08-28 19:55:37 | pmem/pmemkv | https://api.github.com/repos/pmem/pmemkv | opened | Remove ExistsLike operation | Type: Performance | Rather than have this as an explicit operation, let's do this through #117 (ExistsLike == CountLike with limit 1) | True | Remove ExistsLike operation - Rather than have this as an explicit operation, let's do this through #117 (ExistsLike == CountLike with limit 1) | non_priority | remove existslike operation rather than have this as an explicit operation let s do this through existslike countlike with limit | 0 |
38,098 | 8,662,888,767 | IssuesEvent | 2018-11-28 16:02:53 | primefaces/primefaces | https://api.github.com/repos/primefaces/primefaces | closed | TextEditor: Text justify not work | defect |
## 1) Environment
- PrimeFaces version: 6.2
- Does it work on the newest released PrimeFaces version? Version? No
- Does it work on the newest sources in GitHub? (Build by source -> https://github.com/primefaces/primefaces/wiki/Building-From-Source) Not tested.
- Application server + version: Tomcat 9
- Affected browsers: All
## 2) Expected behavior
## 3) Actual behavior
## 4) Steps to reproduce
Just use primefaces showcase and primefaces extension
## 5) Sample XHTML
Just use primefaces showcase and primefaces extension
## 6) Sample bean
Not used.
| 1.0 | TextEditor: Text justify not work -
## 1) Environment
- PrimeFaces version: 6.2
- Does it work on the newest released PrimeFaces version? Version? No
- Does it work on the newest sources in GitHub? (Build by source -> https://github.com/primefaces/primefaces/wiki/Building-From-Source) Not tested.
- Application server + version: Tomcat 9
- Affected browsers: All
## 2) Expected behavior
## 3) Actual behavior
## 4) Steps to reproduce
Just use primefaces showcase and primefaces extension
## 5) Sample XHTML
Just use primefaces showcase and primefaces extension
## 6) Sample bean
Not used.
| non_priority | texteditor text justify not work environment primefaces version does it work on the newest released primefaces version version no does it work on the newest sources in github build by source not tested application server version tomcat affected browsers all expected behavior actual behavior steps to reproduce just use primefaces showcase and primefaces extension sample xhtml just use primefaces showcase and primefaces extension sample bean not used | 0 |
13,342 | 10,213,534,767 | IssuesEvent | 2019-08-14 22:33:05 | dotnet/core-setup | https://api.github.com/repos/dotnet/core-setup | opened | VS insertion federation: manufacture and push MSI insertion nupkgs for 2.1/2.2 | area-Infrastructure | Port https://github.com/dotnet/core-setup/pull/6913 to 2.1/2.2.
@dleeapho, @MichaelSimons, this tracks the work to port MSI nupkg creation back to `release/2.1` and `release/2.2`. We'll have to figure out when to make this happen.
/cc @wtgodbe
(Core-Setup tracking issue for https://github.com/dotnet/core-sdk/issues/2148 and https://github.com/dotnet/core-sdk/issues/2150.) | 1.0 | VS insertion federation: manufacture and push MSI insertion nupkgs for 2.1/2.2 - Port https://github.com/dotnet/core-setup/pull/6913 to 2.1/2.2.
@dleeapho, @MichaelSimons, this tracks the work to port MSI nupkg creation back to `release/2.1` and `release/2.2`. We'll have to figure out when to make this happen.
/cc @wtgodbe
(Core-Setup tracking issue for https://github.com/dotnet/core-sdk/issues/2148 and https://github.com/dotnet/core-sdk/issues/2150.) | non_priority | vs insertion federation manufacture and push msi insertion nupkgs for port to dleeapho michaelsimons this tracks the work to port msi nupkg creation back to release and release we ll have to figure out when to make this happen cc wtgodbe core setup tracking issue for and | 0 |
123,581 | 26,277,889,680 | IssuesEvent | 2023-01-07 01:25:28 | nice-people-frontend-community/nice-js-leetcode | https://api.github.com/repos/nice-people-frontend-community/nice-js-leetcode | opened | [2023-01-07]1658. 将 x 减到 0 的最小操作数👋数组👋哈希表👋二分查找👋前缀和👋滑动窗口 | LeetCode每日一题 | 题目链接: https://leetcode-cn.com/problems/minimum-operations-to-reduce-x-to-zero
难度: <code>Medium</code>
标签: <code>数组</code> <code>哈希表</code> <code>二分查找</code> <code>前缀和</code> <code>滑动窗口</code> | 1.0 | [2023-01-07]1658. 将 x 减到 0 的最小操作数👋数组👋哈希表👋二分查找👋前缀和👋滑动窗口 - 题目链接: https://leetcode-cn.com/problems/minimum-operations-to-reduce-x-to-zero
难度: <code>Medium</code>
标签: <code>数组</code> <code>哈希表</code> <code>二分查找</code> <code>前缀和</code> <code>滑动窗口</code> | non_priority | 将 x 减到 的最小操作数👋数组👋哈希表👋二分查找👋前缀和👋滑动窗口 题目链接 难度 medium 标签 数组 哈希表 二分查找 前缀和 滑动窗口 | 0 |
79,684 | 22,957,837,916 | IssuesEvent | 2022-07-19 13:08:37 | GSS-Cogs/dd-cms | https://api.github.com/repos/GSS-Cogs/dd-cms | opened | Publisher wants to use increased amount of series/categories without warning message | climate change 2 chart builder capability | Although it is a warning and does not stop publisher completely, we should review the limits currently set and consider allowing publisher to use a higher number with better UX
Feedback from Bec 19/07 | 1.0 | Publisher wants to use increased amount of series/categories without warning message - Although it is a warning and does not stop publisher completely, we should review the limits currently set and consider allowing publisher to use a higher number with better UX
Feedback from Bec 19/07 | non_priority | publisher wants to use increased amount of series categories without warning message although it is a warning and does not stop publisher completely we should review the limits currently set and consider allowing publisher to use a higher number with better ux feedback from bec | 0 |
31,223 | 4,698,422,201 | IssuesEvent | 2016-10-12 12:55:43 | FluentLenium/FluentLenium | https://api.github.com/repos/FluentLenium/FluentLenium | opened | PiTest extension to examine our testware | tests | As a improvement of our tests we would like to add PiTest (mutation testing) to our project. | 1.0 | PiTest extension to examine our testware - As a improvement of our tests we would like to add PiTest (mutation testing) to our project. | non_priority | pitest extension to examine our testware as a improvement of our tests we would like to add pitest mutation testing to our project | 0 |
182,017 | 14,896,940,299 | IssuesEvent | 2021-01-21 11:03:41 | aerokube/moon | https://api.github.com/repos/aerokube/moon | opened | Document Ingress configuration | documentation | How to configure with Helm and which annotations are important. | 1.0 | Document Ingress configuration - How to configure with Helm and which annotations are important. | non_priority | document ingress configuration how to configure with helm and which annotations are important | 0 |
232,190 | 18,849,362,115 | IssuesEvent | 2021-11-11 18:41:31 | GEOSX/GEOSX | https://api.github.com/repos/GEOSX/GEOSX | opened | [Feature] Move Nightly CI Tests from Bamboo to Gitlab | type: testing type: dev environment | Bamboo will be going down Jan. 17, 2022 as LC moves to supporting gitlab ([LC Gitlab link](https://lc.llnl.gov/gitlab/users/sign_in))
- [ ] Setup mirroring from Github to gitlab. LC Guide: https://lc.llnl.gov/confluence/pages/viewpage.action?pageId=662832265
- [ ] Move bamboo scripts and setup to gitlab
- [ ] Reconfigure scripts on gitlab to push updates to nightlyTests repo | 1.0 | [Feature] Move Nightly CI Tests from Bamboo to Gitlab - Bamboo will be going down Jan. 17, 2022 as LC moves to supporting gitlab ([LC Gitlab link](https://lc.llnl.gov/gitlab/users/sign_in))
- [ ] Setup mirroring from Github to gitlab. LC Guide: https://lc.llnl.gov/confluence/pages/viewpage.action?pageId=662832265
- [ ] Move bamboo scripts and setup to gitlab
- [ ] Reconfigure scripts on gitlab to push updates to nightlyTests repo | non_priority | move nightly ci tests from bamboo to gitlab bamboo will be going down jan as lc moves to supporting gitlab setup mirroring from github to gitlab lc guide move bamboo scripts and setup to gitlab reconfigure scripts on gitlab to push updates to nightlytests repo | 0 |
16,168 | 5,222,400,854 | IssuesEvent | 2017-01-27 08:04:36 | Microsoft/vscode | https://api.github.com/repos/Microsoft/vscode | closed | go to definition doesn't work for certain module patterns | code-navigation javascript upstream | - VSCode Version: 1.7.1
- OS Version: windows 10
Steps to Reproduce:
1. Write a module in a certain way
2. Import the module and try to go to definition on a function.
Sample module A
```
exports.myFunction = function () {
};
```
Sample module B
```
var myModule = {};
myModule.myFunction = function() {
};
exports = myModule;
```
```
//app code
var myModule = require('./myModule');
myModule.myFunction(); //go to definition doesn't work if you use sample module B, it works with module A
```
Full repo that reproduces issue https://github.com/barisusakli/vs-code-intellisense-test.
It seems like it only works if you set properties directly on `exports`.
| 1.0 | go to definition doesn't work for certain module patterns - - VSCode Version: 1.7.1
- OS Version: windows 10
Steps to Reproduce:
1. Write a module in a certain way
2. Import the module and try to go to definition on a function.
Sample module A
```
exports.myFunction = function () {
};
```
Sample module B
```
var myModule = {};
myModule.myFunction = function() {
};
exports = myModule;
```
```
//app code
var myModule = require('./myModule');
myModule.myFunction(); //go to definition doesn't work if you use sample module B, it works with module A
```
Full repo that reproduces issue https://github.com/barisusakli/vs-code-intellisense-test.
It seems like it only works if you set properties directly on `exports`.
| non_priority | go to definition doesn t work for certain module patterns vscode version os version windows steps to reproduce write a module in a certain way import the module and try to go to definition on a function sample module a exports myfunction function sample module b var mymodule mymodule myfunction function exports mymodule app code var mymodule require mymodule mymodule myfunction go to definition doesn t work if you use sample module b it works with module a full repo that reproduces issue it seems like it only works if you set properties directly on exports | 0 |
422,363 | 28,436,028,473 | IssuesEvent | 2023-04-15 10:17:59 | lafkpages/Nodeval | https://api.github.com/repos/lafkpages/Nodeval | opened | Add instructions on how to connect to Nodeval | documentation | Umm yes, that. Screenshots of the debug pane would be nice. | 1.0 | Add instructions on how to connect to Nodeval - Umm yes, that. Screenshots of the debug pane would be nice. | non_priority | add instructions on how to connect to nodeval umm yes that screenshots of the debug pane would be nice | 0 |
234,305 | 25,823,662,144 | IssuesEvent | 2022-12-12 11:21:01 | uthir/Linux-4.19.72 | https://api.github.com/repos/uthir/Linux-4.19.72 | opened | CVE-2019-1125 (Medium) detected in linuxlinux-4.19.268 | security vulnerability | ## CVE-2019-1125 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.19.268</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/uthir/Linux-4.19.72/commit/d93bc5e75a1ee9b6af24441370aba4a4afb05598">d93bc5e75a1ee9b6af24441370aba4a4afb05598</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>/tools/arch/x86/include/asm/cpufeatures.h</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 information disclosure vulnerability exists when certain central processing units (CPU) speculatively access memory, aka 'Windows Kernel Information Disclosure Vulnerability'. This CVE ID is unique from CVE-2019-1071, CVE-2019-1073.
<p>Publish Date: 2019-09-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-1125>CVE-2019-1125</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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://www.linuxkernelcves.com/cves/CVE-2019-1125">https://www.linuxkernelcves.com/cves/CVE-2019-1125</a></p>
<p>Release Date: 2020-08-24</p>
<p>Fix Resolution: v5.3-rc4,v3.16.72,v4.14.137,v4.19.65,v4.4.189,v4.9.189,v5.2.7</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-1125 (Medium) detected in linuxlinux-4.19.268 - ## CVE-2019-1125 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.19.268</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/uthir/Linux-4.19.72/commit/d93bc5e75a1ee9b6af24441370aba4a4afb05598">d93bc5e75a1ee9b6af24441370aba4a4afb05598</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>/tools/arch/x86/include/asm/cpufeatures.h</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 information disclosure vulnerability exists when certain central processing units (CPU) speculatively access memory, aka 'Windows Kernel Information Disclosure Vulnerability'. This CVE ID is unique from CVE-2019-1071, CVE-2019-1073.
<p>Publish Date: 2019-09-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-1125>CVE-2019-1125</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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://www.linuxkernelcves.com/cves/CVE-2019-1125">https://www.linuxkernelcves.com/cves/CVE-2019-1125</a></p>
<p>Release Date: 2020-08-24</p>
<p>Fix Resolution: v5.3-rc4,v3.16.72,v4.14.137,v4.19.65,v4.4.189,v4.9.189,v5.2.7</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 tools arch include asm cpufeatures h vulnerability details an information disclosure vulnerability exists when certain central processing units cpu speculatively access memory aka windows kernel information disclosure vulnerability this cve id is unique from cve cve 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 none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
237,113 | 26,078,803,851 | IssuesEvent | 2022-12-25 01:16:52 | thecodeorigin/nest-template | https://api.github.com/repos/thecodeorigin/nest-template | opened | CVE-2022-23541 (Medium) detected in jsonwebtoken-8.5.1.tgz | security vulnerability | ## CVE-2022-23541 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jsonwebtoken-8.5.1.tgz</b></p></summary>
<p>JSON Web Token implementation (symmetric and asymmetric)</p>
<p>Library home page: <a href="https://registry.npmjs.org/jsonwebtoken/-/jsonwebtoken-8.5.1.tgz">https://registry.npmjs.org/jsonwebtoken/-/jsonwebtoken-8.5.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/jsonwebtoken/package.json</p>
<p>
Dependency Hierarchy:
- passport-jwt-4.0.0.tgz (Root Library)
- :x: **jsonwebtoken-8.5.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/thecodeorigin/nest-template/commit/2359bd3c0ccc2623a654758aca77d8f8bc59e6a9">2359bd3c0ccc2623a654758aca77d8f8bc59e6a9</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>
jsonwebtoken is an implementation of JSON Web Tokens. Versions `<= 8.5.1` of `jsonwebtoken` library can be misconfigured so that passing a poorly implemented key retrieval function referring to the `secretOrPublicKey` argument from the readme link will result in incorrect verification of tokens. There is a possibility of using a different algorithm and key combination in verification, other than the one that was used to sign the tokens. Specifically, tokens signed with an asymmetric public key could be verified with a symmetric HS256 algorithm. This can lead to successful validation of forged tokens. If your application is supporting usage of both symmetric key and asymmetric key in jwt.verify() implementation with the same key retrieval function. This issue has been patched, please update to version 9.0.0.
<p>Publish Date: 2022-12-22
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23541>CVE-2022-23541</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.0</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: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/auth0/node-jsonwebtoken/security/advisories/GHSA-hjrf-2m68-5959">https://github.com/auth0/node-jsonwebtoken/security/advisories/GHSA-hjrf-2m68-5959</a></p>
<p>Release Date: 2022-12-22</p>
<p>Fix Resolution: jsonwebtoken - 9.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-23541 (Medium) detected in jsonwebtoken-8.5.1.tgz - ## CVE-2022-23541 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jsonwebtoken-8.5.1.tgz</b></p></summary>
<p>JSON Web Token implementation (symmetric and asymmetric)</p>
<p>Library home page: <a href="https://registry.npmjs.org/jsonwebtoken/-/jsonwebtoken-8.5.1.tgz">https://registry.npmjs.org/jsonwebtoken/-/jsonwebtoken-8.5.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/jsonwebtoken/package.json</p>
<p>
Dependency Hierarchy:
- passport-jwt-4.0.0.tgz (Root Library)
- :x: **jsonwebtoken-8.5.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/thecodeorigin/nest-template/commit/2359bd3c0ccc2623a654758aca77d8f8bc59e6a9">2359bd3c0ccc2623a654758aca77d8f8bc59e6a9</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>
jsonwebtoken is an implementation of JSON Web Tokens. Versions `<= 8.5.1` of `jsonwebtoken` library can be misconfigured so that passing a poorly implemented key retrieval function referring to the `secretOrPublicKey` argument from the readme link will result in incorrect verification of tokens. There is a possibility of using a different algorithm and key combination in verification, other than the one that was used to sign the tokens. Specifically, tokens signed with an asymmetric public key could be verified with a symmetric HS256 algorithm. This can lead to successful validation of forged tokens. If your application is supporting usage of both symmetric key and asymmetric key in jwt.verify() implementation with the same key retrieval function. This issue has been patched, please update to version 9.0.0.
<p>Publish Date: 2022-12-22
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23541>CVE-2022-23541</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.0</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: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/auth0/node-jsonwebtoken/security/advisories/GHSA-hjrf-2m68-5959">https://github.com/auth0/node-jsonwebtoken/security/advisories/GHSA-hjrf-2m68-5959</a></p>
<p>Release Date: 2022-12-22</p>
<p>Fix Resolution: jsonwebtoken - 9.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in jsonwebtoken tgz cve medium severity vulnerability vulnerable library jsonwebtoken tgz json web token implementation symmetric and asymmetric library home page a href path to dependency file package json path to vulnerable library node modules jsonwebtoken package json dependency hierarchy passport jwt tgz root library x jsonwebtoken tgz vulnerable library found in head commit a href found in base branch master vulnerability details jsonwebtoken is an implementation of json web tokens versions of jsonwebtoken library can be misconfigured so that passing a poorly implemented key retrieval function referring to the secretorpublickey argument from the readme link will result in incorrect verification of tokens there is a possibility of using a different algorithm and key combination in verification other than the one that was used to sign the tokens specifically tokens signed with an asymmetric public key could be verified with a symmetric algorithm this can lead to successful validation of forged tokens if your application is supporting usage of both symmetric key and asymmetric key in jwt verify implementation with the same key retrieval function this issue has been patched please update to version 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 low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jsonwebtoken step up your open source security game with mend | 0 |
145,965 | 11,716,191,470 | IssuesEvent | 2020-03-09 15:16:47 | rust-lang/rust | https://api.github.com/repos/rust-lang/rust | closed | Compiler panic when yielding array element from non-generator | A-generators C-bug E-needstest F-generators I-ICE T-compiler requires-nightly | Steps to reproduce:
1. Run `cargo new --lib crash`.
2. Replace `src/lib.rs` with this content:
```
#![feature(generators)]
pub fn crash(arr: [usize; 1]) {
yield arr[0];
}
```
3. Run `RUST_BACKTRACE=full cargo +nightly build --verbose` to get this output:
```
Compiling crash v0.1.0 (/Users/waleedk/Workspace/rust/crash)
Running `rustc --edition=2018 --crate-name crash src/lib.rs --color never --crate-type lib --emit=dep-info,metadata,link -C debuginfo=2 -C metadata=23cf916e5f69a1d5 -C extra-filename=-23cf916e5f69a1d5 --out-dir /Users/waleedk/Workspace/rust/crash/target/debug/deps -C incremental=/Users/waleedk/Workspace/rust/crash/target/debug/incremental -L dependency=/Users/waleedk/Workspace/rust/crash/target/debug/deps`
error[E0627]: yield statement outside of generator literal
--> src/lib.rs:4:5
|
4 | yield arr[0];
| ^^^^^^^^^^^^
error: internal compiler error: src/librustc/ty/context.rs:513: node_type: no type for node `expr arr (hir_id=HirId { owner: DefIndex(12), local_id: 4 })`
thread 'rustc' panicked at 'Box<Any>', src/librustc_errors/lib.rs:643:9
stack backtrace:
0: 0x106073185 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h407a883469cc9aea
1: 0x1060a9e40 - core::fmt::write::h0fac5bdf1ffbd343
2: 0x1060667db - std::io::Write::write_fmt::h29f6e9a4453f8e64
3: 0x1060774ca - std::panicking::default_hook::{{closure}}::h514976ca44017853
4: 0x1060771d5 - std::panicking::default_hook::h0cf5e5649c498611
5: 0x106e23a72 - rustc_driver::report_ice::h6ba72ba240c53ce3
6: 0x106077d02 - std::panicking::rust_panic_with_hook::hb89fa56b0e453398
7: 0x10894e321 - std::panicking::begin_panic::hce94a994785bd80a
8: 0x108962a11 - rustc_errors::Handler::bug::h265e236e59364186
9: 0x10827b7eb - rustc::util::bug::opt_span_bug_fmt::{{closure}}::h1866a473633f70cb
10: 0x108275f86 - rustc::ty::context::tls::with_opt::{{closure}}::h8e08a01f090121d8
11: 0x108275c84 - rustc::ty::context::tls::with_context_opt::hdad39dbafc5ec58d
12: 0x108275cb2 - rustc::ty::context::tls::with_opt::h32448c650a990704
13: 0x10827b708 - rustc::util::bug::opt_span_bug_fmt::h7d1e0412534498f1
14: 0x10827b65b - rustc::util::bug::bug_fmt::h15b5afa17bb8a885
15: 0x10846a6af - rustc::ty::context::TypeckTables::node_type::{{closure}}::h5cee46e2a7fddad1
16: 0x10846af7f - rustc::ty::context::TypeckTables::expr_ty_adjusted::h9a1a0498668f933a
17: 0x107349b61 - <rustc_typeck::check::writeback::WritebackCx as rustc::hir::intravisit::Visitor>::visit_expr::hfabfed1d580fd434
18: 0x107349d37 - <rustc_typeck::check::writeback::WritebackCx as rustc::hir::intravisit::Visitor>::visit_expr::hfabfed1d580fd434
19: 0x10749985f - rustc::hir::intravisit::walk_expr::hce3981a7cb93dce2
20: 0x107349d37 - <rustc_typeck::check::writeback::WritebackCx as rustc::hir::intravisit::Visitor>::visit_expr::hfabfed1d580fd434
21: 0x1072ef7d7 - rustc_typeck::check::writeback::<impl rustc_typeck::check::FnCtxt>::resolve_type_vars_in_body::hc3f47a3d49d6def3
22: 0x1074787a2 - rustc::ty::context::GlobalCtxt::enter_local::h699d9d6b520150c4
23: 0x10731d5ac - rustc_typeck::check::typeck_tables_of::h0349fdf1b9f7c1ea
24: 0x10736878a - rustc::ty::query::__query_compute::typeck_tables_of::he96adad9f8508347
25: 0x1073f245b - rustc::ty::query::<impl rustc::ty::query::config::QueryAccessors for rustc::ty::query::queries::typeck_tables_of>::compute::hc066a0e8be7ccc2d
26: 0x10739e9e9 - rustc::dep_graph::graph::DepGraph::with_task_impl::hbd4ef70d845d9338
27: 0x107415aa0 - rustc::ty::query::plumbing::<impl rustc::ty::context::TyCtxt>::get_query::h2ce71490153de00b
28: 0x1073ef260 - rustc::ty::<impl rustc::ty::context::TyCtxt>::par_body_owners::hc4ce32a0430f92a7
29: 0x10731d0a5 - rustc_typeck::check::typeck_item_bodies::h2b11ae34f5facd7b
30: 0x107368b92 - rustc::ty::query::__query_compute::typeck_item_bodies::h18343492cac5f4ec
31: 0x10739689b - rustc::dep_graph::graph::DepGraph::with_task_impl::h550c64cb66ef5c2a
32: 0x107470ca8 - rustc::ty::query::plumbing::<impl rustc::ty::context::TyCtxt>::get_query::hffc3b386c637fd84
33: 0x10736bd65 - rustc::util::common::time::h7c6cc64b93fbb8e0
34: 0x1075166dc - rustc_typeck::check_crate::h1976021c3c35cace
35: 0x106ebc862 - rustc_interface::passes::analysis::h58e38d87b942506f
36: 0x106dd024e - rustc::ty::query::__query_compute::analysis::hddfd24a5907dd9e0
37: 0x106dd12d9 - rustc::ty::query::plumbing::<impl rustc::ty::context::TyCtxt>::get_query::h190aae50181d7543
38: 0x106df116c - rustc_interface::passes::BoxedGlobalCtxt::access::{{closure}}::h5a27bf8f9540381c
39: 0x106f2ec9b - rustc_interface::passes::create_global_ctxt::{{closure}}::h9c5444345f4c2293
40: 0x106df3622 - rustc_interface::interface::run_compiler_in_existing_thread_pool::hfc3311be21f2f27a
41: 0x106e255e4 - std::thread::local::LocalKey<T>::with::h188788fcd090e799
42: 0x106e2a0e2 - scoped_tls::ScopedKey<T>::set::h999b3fc3ad485797
43: 0x106e43235 - syntax::with_globals::h3db29ff7d66827a3
44: 0x106dcb1fd - std::sys_common::backtrace::__rust_begin_short_backtrace::h1f76ce0ab4ce564e
45: 0x106086faf - __rust_maybe_catch_panic
46: 0x106de7407 - core::ops::function::FnOnce::call_once{{vtable.shim}}::h45a83671da86e5b7
47: 0x10605902e - <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once::h9c2e02a877751d79
48: 0x106085dbe - std::sys::unix::thread::Thread::new::thread_start::h48a214a3a7467592
49: 0x7fff5d2ee2eb - _pthread_body
50: 0x7fff5d2f1249 - _pthread_start
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
note: rustc 1.39.0-nightly (eceec57f7 2019-09-18) running on x86_64-apple-darwin
note: compiler flags: -C debuginfo=2 -C incremental --crate-type lib
note: some of the compiler flags provided by cargo are hidden
query stack during panic:
#0 [typeck_tables_of] processing `crash`
#1 [typeck_item_bodies] type-checking all item bodies
#2 [analysis] running analysis passes on this crate
end of query stack
error: aborting due to 2 previous errors
error: Could not compile `crash`.
Caused by:
process didn't exit successfully: `rustc --edition=2018 --crate-name crash src/lib.rs --color never --crate-type lib --emit=dep-info,metadata,link -C debuginfo=2 -C metadata=23cf916e5f69a1d5 -C extra-filename=-23cf916e5f69a1d5 --out-dir /Users/waleedk/Workspace/rust/crash/target/debug/deps -C incremental=/Users/waleedk/Workspace/rust/crash/target/debug/incremental -L dependency=/Users/waleedk/Workspace/rust/crash/target/debug/deps` (exit code: 101)
``` | 1.0 | Compiler panic when yielding array element from non-generator - Steps to reproduce:
1. Run `cargo new --lib crash`.
2. Replace `src/lib.rs` with this content:
```
#![feature(generators)]
pub fn crash(arr: [usize; 1]) {
yield arr[0];
}
```
3. Run `RUST_BACKTRACE=full cargo +nightly build --verbose` to get this output:
```
Compiling crash v0.1.0 (/Users/waleedk/Workspace/rust/crash)
Running `rustc --edition=2018 --crate-name crash src/lib.rs --color never --crate-type lib --emit=dep-info,metadata,link -C debuginfo=2 -C metadata=23cf916e5f69a1d5 -C extra-filename=-23cf916e5f69a1d5 --out-dir /Users/waleedk/Workspace/rust/crash/target/debug/deps -C incremental=/Users/waleedk/Workspace/rust/crash/target/debug/incremental -L dependency=/Users/waleedk/Workspace/rust/crash/target/debug/deps`
error[E0627]: yield statement outside of generator literal
--> src/lib.rs:4:5
|
4 | yield arr[0];
| ^^^^^^^^^^^^
error: internal compiler error: src/librustc/ty/context.rs:513: node_type: no type for node `expr arr (hir_id=HirId { owner: DefIndex(12), local_id: 4 })`
thread 'rustc' panicked at 'Box<Any>', src/librustc_errors/lib.rs:643:9
stack backtrace:
0: 0x106073185 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h407a883469cc9aea
1: 0x1060a9e40 - core::fmt::write::h0fac5bdf1ffbd343
2: 0x1060667db - std::io::Write::write_fmt::h29f6e9a4453f8e64
3: 0x1060774ca - std::panicking::default_hook::{{closure}}::h514976ca44017853
4: 0x1060771d5 - std::panicking::default_hook::h0cf5e5649c498611
5: 0x106e23a72 - rustc_driver::report_ice::h6ba72ba240c53ce3
6: 0x106077d02 - std::panicking::rust_panic_with_hook::hb89fa56b0e453398
7: 0x10894e321 - std::panicking::begin_panic::hce94a994785bd80a
8: 0x108962a11 - rustc_errors::Handler::bug::h265e236e59364186
9: 0x10827b7eb - rustc::util::bug::opt_span_bug_fmt::{{closure}}::h1866a473633f70cb
10: 0x108275f86 - rustc::ty::context::tls::with_opt::{{closure}}::h8e08a01f090121d8
11: 0x108275c84 - rustc::ty::context::tls::with_context_opt::hdad39dbafc5ec58d
12: 0x108275cb2 - rustc::ty::context::tls::with_opt::h32448c650a990704
13: 0x10827b708 - rustc::util::bug::opt_span_bug_fmt::h7d1e0412534498f1
14: 0x10827b65b - rustc::util::bug::bug_fmt::h15b5afa17bb8a885
15: 0x10846a6af - rustc::ty::context::TypeckTables::node_type::{{closure}}::h5cee46e2a7fddad1
16: 0x10846af7f - rustc::ty::context::TypeckTables::expr_ty_adjusted::h9a1a0498668f933a
17: 0x107349b61 - <rustc_typeck::check::writeback::WritebackCx as rustc::hir::intravisit::Visitor>::visit_expr::hfabfed1d580fd434
18: 0x107349d37 - <rustc_typeck::check::writeback::WritebackCx as rustc::hir::intravisit::Visitor>::visit_expr::hfabfed1d580fd434
19: 0x10749985f - rustc::hir::intravisit::walk_expr::hce3981a7cb93dce2
20: 0x107349d37 - <rustc_typeck::check::writeback::WritebackCx as rustc::hir::intravisit::Visitor>::visit_expr::hfabfed1d580fd434
21: 0x1072ef7d7 - rustc_typeck::check::writeback::<impl rustc_typeck::check::FnCtxt>::resolve_type_vars_in_body::hc3f47a3d49d6def3
22: 0x1074787a2 - rustc::ty::context::GlobalCtxt::enter_local::h699d9d6b520150c4
23: 0x10731d5ac - rustc_typeck::check::typeck_tables_of::h0349fdf1b9f7c1ea
24: 0x10736878a - rustc::ty::query::__query_compute::typeck_tables_of::he96adad9f8508347
25: 0x1073f245b - rustc::ty::query::<impl rustc::ty::query::config::QueryAccessors for rustc::ty::query::queries::typeck_tables_of>::compute::hc066a0e8be7ccc2d
26: 0x10739e9e9 - rustc::dep_graph::graph::DepGraph::with_task_impl::hbd4ef70d845d9338
27: 0x107415aa0 - rustc::ty::query::plumbing::<impl rustc::ty::context::TyCtxt>::get_query::h2ce71490153de00b
28: 0x1073ef260 - rustc::ty::<impl rustc::ty::context::TyCtxt>::par_body_owners::hc4ce32a0430f92a7
29: 0x10731d0a5 - rustc_typeck::check::typeck_item_bodies::h2b11ae34f5facd7b
30: 0x107368b92 - rustc::ty::query::__query_compute::typeck_item_bodies::h18343492cac5f4ec
31: 0x10739689b - rustc::dep_graph::graph::DepGraph::with_task_impl::h550c64cb66ef5c2a
32: 0x107470ca8 - rustc::ty::query::plumbing::<impl rustc::ty::context::TyCtxt>::get_query::hffc3b386c637fd84
33: 0x10736bd65 - rustc::util::common::time::h7c6cc64b93fbb8e0
34: 0x1075166dc - rustc_typeck::check_crate::h1976021c3c35cace
35: 0x106ebc862 - rustc_interface::passes::analysis::h58e38d87b942506f
36: 0x106dd024e - rustc::ty::query::__query_compute::analysis::hddfd24a5907dd9e0
37: 0x106dd12d9 - rustc::ty::query::plumbing::<impl rustc::ty::context::TyCtxt>::get_query::h190aae50181d7543
38: 0x106df116c - rustc_interface::passes::BoxedGlobalCtxt::access::{{closure}}::h5a27bf8f9540381c
39: 0x106f2ec9b - rustc_interface::passes::create_global_ctxt::{{closure}}::h9c5444345f4c2293
40: 0x106df3622 - rustc_interface::interface::run_compiler_in_existing_thread_pool::hfc3311be21f2f27a
41: 0x106e255e4 - std::thread::local::LocalKey<T>::with::h188788fcd090e799
42: 0x106e2a0e2 - scoped_tls::ScopedKey<T>::set::h999b3fc3ad485797
43: 0x106e43235 - syntax::with_globals::h3db29ff7d66827a3
44: 0x106dcb1fd - std::sys_common::backtrace::__rust_begin_short_backtrace::h1f76ce0ab4ce564e
45: 0x106086faf - __rust_maybe_catch_panic
46: 0x106de7407 - core::ops::function::FnOnce::call_once{{vtable.shim}}::h45a83671da86e5b7
47: 0x10605902e - <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once::h9c2e02a877751d79
48: 0x106085dbe - std::sys::unix::thread::Thread::new::thread_start::h48a214a3a7467592
49: 0x7fff5d2ee2eb - _pthread_body
50: 0x7fff5d2f1249 - _pthread_start
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
note: rustc 1.39.0-nightly (eceec57f7 2019-09-18) running on x86_64-apple-darwin
note: compiler flags: -C debuginfo=2 -C incremental --crate-type lib
note: some of the compiler flags provided by cargo are hidden
query stack during panic:
#0 [typeck_tables_of] processing `crash`
#1 [typeck_item_bodies] type-checking all item bodies
#2 [analysis] running analysis passes on this crate
end of query stack
error: aborting due to 2 previous errors
error: Could not compile `crash`.
Caused by:
process didn't exit successfully: `rustc --edition=2018 --crate-name crash src/lib.rs --color never --crate-type lib --emit=dep-info,metadata,link -C debuginfo=2 -C metadata=23cf916e5f69a1d5 -C extra-filename=-23cf916e5f69a1d5 --out-dir /Users/waleedk/Workspace/rust/crash/target/debug/deps -C incremental=/Users/waleedk/Workspace/rust/crash/target/debug/incremental -L dependency=/Users/waleedk/Workspace/rust/crash/target/debug/deps` (exit code: 101)
``` | non_priority | compiler panic when yielding array element from non generator steps to reproduce run cargo new lib crash replace src lib rs with this content pub fn crash arr yield arr run rust backtrace full cargo nightly build verbose to get this output compiling crash users waleedk workspace rust crash running rustc edition crate name crash src lib rs color never crate type lib emit dep info metadata link c debuginfo c metadata c extra filename out dir users waleedk workspace rust crash target debug deps c incremental users waleedk workspace rust crash target debug incremental l dependency users waleedk workspace rust crash target debug deps error yield statement outside of generator literal src lib rs yield arr error internal compiler error src librustc ty context rs node type no type for node expr arr hir id hirid owner defindex local id thread rustc panicked at box src librustc errors lib rs stack backtrace fmt core fmt write std io write write fmt std panicking default hook closure std panicking default hook rustc driver report ice std panicking rust panic with hook std panicking begin panic rustc errors handler bug rustc util bug opt span bug fmt closure rustc ty context tls with opt closure rustc ty context tls with context opt rustc ty context tls with opt rustc util bug opt span bug fmt rustc util bug bug fmt rustc ty context typecktables node type closure rustc ty context typecktables expr ty adjusted visit expr visit expr rustc hir intravisit walk expr visit expr rustc typeck check writeback resolve type vars in body rustc ty context globalctxt enter local rustc typeck check typeck tables of rustc ty query query compute typeck tables of rustc ty query compute rustc dep graph graph depgraph with task impl rustc ty query plumbing get query rustc ty par body owners rustc typeck check typeck item bodies rustc ty query query compute typeck item bodies rustc dep graph graph depgraph with task impl rustc ty query plumbing get query rustc util common time rustc typeck check crate rustc interface passes analysis rustc ty query query compute analysis rustc ty query plumbing get query rustc interface passes boxedglobalctxt access closure rustc interface passes create global ctxt closure rustc interface interface run compiler in existing thread pool std thread local localkey with scoped tls scopedkey set syntax with globals std sys common backtrace rust begin short backtrace rust maybe catch panic core ops function fnonce call once vtable shim as core ops function fnonce call once std sys unix thread thread new thread start pthread body pthread start note the compiler unexpectedly panicked this is a bug note we would appreciate a bug report note rustc nightly running on apple darwin note compiler flags c debuginfo c incremental crate type lib note some of the compiler flags provided by cargo are hidden query stack during panic processing crash type checking all item bodies running analysis passes on this crate end of query stack error aborting due to previous errors error could not compile crash caused by process didn t exit successfully rustc edition crate name crash src lib rs color never crate type lib emit dep info metadata link c debuginfo c metadata c extra filename out dir users waleedk workspace rust crash target debug deps c incremental users waleedk workspace rust crash target debug incremental l dependency users waleedk workspace rust crash target debug deps exit code | 0 |
150,031 | 23,589,872,175 | IssuesEvent | 2022-08-23 14:26:04 | scholokov/long-travel-2 | https://api.github.com/repos/scholokov/long-travel-2 | opened | The Figma block road Eindhoven-Киев NO FLAGS | Bug Design Middle prio | Steps To Reproduce:
1. Open the page https://www.figma.com/file/mh7iDnG6ec7yiC0SCGad7L/Long-Travel?node-id=986%3A7
2. Pay attention to block road Eindhoven
Actual result: there are **no flags** of Netherlands and Ukraine on the opposite side of the travel points
Expected result: there are flags of the Netherlands and Ukraine on the opposite side of the travel points
<img width="1440" alt="Снимок экрана 2022-08-23 в 5 20 15 PM" src="https://user-images.githubusercontent.com/110661667/186183757-f3f004b6-ded4-4f8a-9964-14c8df20d08b.png">
<img width="1440" alt="Снимок экрана 2022-08-23 в 5 24 34 PM" src="https://user-images.githubusercontent.com/110661667/186183926-69e18ec6-afc9-4222-a9a1-0403373a6d9b.png">
| 1.0 | The Figma block road Eindhoven-Киев NO FLAGS - Steps To Reproduce:
1. Open the page https://www.figma.com/file/mh7iDnG6ec7yiC0SCGad7L/Long-Travel?node-id=986%3A7
2. Pay attention to block road Eindhoven
Actual result: there are **no flags** of Netherlands and Ukraine on the opposite side of the travel points
Expected result: there are flags of the Netherlands and Ukraine on the opposite side of the travel points
<img width="1440" alt="Снимок экрана 2022-08-23 в 5 20 15 PM" src="https://user-images.githubusercontent.com/110661667/186183757-f3f004b6-ded4-4f8a-9964-14c8df20d08b.png">
<img width="1440" alt="Снимок экрана 2022-08-23 в 5 24 34 PM" src="https://user-images.githubusercontent.com/110661667/186183926-69e18ec6-afc9-4222-a9a1-0403373a6d9b.png">
| non_priority | the figma block road eindhoven киев no flags steps to reproduce open the page pay attention to block road eindhoven actual result there are no flags of netherlands and ukraine on the opposite side of the travel points expected result there are flags of the netherlands and ukraine on the opposite side of the travel points img width alt снимок экрана в pm src img width alt снимок экрана в pm src | 0 |
194,326 | 14,675,776,472 | IssuesEvent | 2020-12-30 18:26:57 | chartjs/chartjs-plugin-datalabels | https://api.github.com/repos/chartjs/chartjs-plugin-datalabels | closed | Persistent labels when interacting with chart | needs test case | When I disable one bar in a bar chart the label is still in the same position and as the bar fills over that location you can see the label of the bar that is disabled.
Normal:
Disabled first bar:
Disabled second bar:
 | 1.0 | Persistent labels when interacting with chart - When I disable one bar in a bar chart the label is still in the same position and as the bar fills over that location you can see the label of the bar that is disabled.
Normal:
Disabled first bar:
Disabled second bar:
 | non_priority | persistent labels when interacting with chart when i disable one bar in a bar chart the label is still in the same position and as the bar fills over that location you can see the label of the bar that is disabled normal disabled first bar disabled second bar | 0 |
4,687 | 7,307,456,822 | IssuesEvent | 2018-02-28 02:52:21 | Convolvr/convolvr | https://api.github.com/repos/Convolvr/convolvr | opened | Refactor space partitioning to be more flexible | Compatibility Core System enhancement | ## 2 partitioning modes:
- euclidean
- recursive
### Euclidean
How it is currently.
### Recursive
The server splits voxels into an octree, once more than a threshold number of entities is reached.
Default octree levels should be configurable, as well as octree settings for each voxel:
- ```classification: string``` (Building, Planet, etc)
- ```name: string``` (Laudro Mart, Earth, etc)
- ```splitThreshold: int``` (number of entities before splitting)
- ```parent: Voxel```
- ```bounds: { from: [3]int, to: [3]int }``` (manually set bounds if not set by server)
- ```grid: boolean``` (only available for root node; creates adjacent voxels of size ```bounds```)
| True | Refactor space partitioning to be more flexible - ## 2 partitioning modes:
- euclidean
- recursive
### Euclidean
How it is currently.
### Recursive
The server splits voxels into an octree, once more than a threshold number of entities is reached.
Default octree levels should be configurable, as well as octree settings for each voxel:
- ```classification: string``` (Building, Planet, etc)
- ```name: string``` (Laudro Mart, Earth, etc)
- ```splitThreshold: int``` (number of entities before splitting)
- ```parent: Voxel```
- ```bounds: { from: [3]int, to: [3]int }``` (manually set bounds if not set by server)
- ```grid: boolean``` (only available for root node; creates adjacent voxels of size ```bounds```)
| non_priority | refactor space partitioning to be more flexible partitioning modes euclidean recursive euclidean how it is currently recursive the server splits voxels into an octree once more than a threshold number of entities is reached default octree levels should be configurable as well as octree settings for each voxel classification string building planet etc name string laudro mart earth etc splitthreshold int number of entities before splitting parent voxel bounds from int to int manually set bounds if not set by server grid boolean only available for root node creates adjacent voxels of size bounds | 0 |
138,802 | 31,031,493,532 | IssuesEvent | 2023-08-10 12:46:23 | FerretDB/dance | https://api.github.com/repos/FerretDB/dance | closed | Extend all the examples | code/chore | This is to unify all examples and also add more commands to have more coverage.
```[tasklist]
### Tasks
- [ ] https://github.com/FerretDB/dotnet-example/pull/5
- [ ] https://github.com/FerretDB/java-example/pull/3
- [ ] https://github.com/FerretDB/python-example/pull/2
```
| 1.0 | Extend all the examples - This is to unify all examples and also add more commands to have more coverage.
```[tasklist]
### Tasks
- [ ] https://github.com/FerretDB/dotnet-example/pull/5
- [ ] https://github.com/FerretDB/java-example/pull/3
- [ ] https://github.com/FerretDB/python-example/pull/2
```
| non_priority | extend all the examples this is to unify all examples and also add more commands to have more coverage tasks | 0 |
66,430 | 16,612,447,667 | IssuesEvent | 2021-06-02 13:10:19 | trilinos/Trilinos | https://api.github.com/repos/trilinos/Trilinos | closed | Error linking ThyraEpetraAdapters_TestThyraDebugHang.exe | CLOSED_DUE_TO_INACTIVITY MARKED_FOR_CLOSURE impacting: build pkg: Epetra pkg: Thyra | <!--- Provide a general summary of the issue in the Title above. -->
<!---
Note that anything between these delimiters is a comment that will not appear
in the issue description once created. Click on the Preview tab to see what
everything will look like when you submit.
-->
<!---
Feel free to delete anything from this template that is not applicable to the
issue you are submitting.
-->
<!---
Replace <teamName> below with the appropriate Trilinos package/team name.
-->
@mhoemmen
<!---
Assignees: If you know anyone who should likely tackle this issue, select them
from the Assignees drop-down on the right.
-->
<!---
Lables: Choose any applicable package names from the Labels drop-down on the
right. Additionally, choose a label to indicate the type of issue, for
instance, bug, build, documentation, enhancement, etc.
-->
## Expectations
<!---
Tell us what you think should happen, how you think things should work, what
you would like to see in the documentation, etc.
-->
I am trying to build Trilinos with the options listed [here](https://peridigm.sandia.gov/content/trilinos) on a Fedora Linux VM (gcc 7.2.1).
## Current Behavior
<!---
Tell us how the current behavior fails to meet your expectations in some way.
-->
While linking ThyraEpetraAdapters_TestThyraDebugHang.exe I get the following error:
```
[ 86%] Linking CXX executable ThyraEpetraAdapters_TestThyraDebugHang.exe
CMakeFiles/ThyraEpetraAdapters_TestThyraDebugHang.dir/TestThyraDebugHang.cpp.o: In function `ThyraEpetraMultiVector_HangingInParallelDebug_UnitTest::runUnitTestImpl(Teuchos::basic_FancyOStream<char, std::char_traits<char> >&, bool&) const':
TestThyraDebugHang.cpp:(.text+0xad3): undefined reference to `Thyra::DefaultSpmdVectorSpace<double>::initialize(Teuchos::RCP<Teuchos::Comm<long> const> const&, long, long, bool)'
collect2: error: ld returned 1 exit status
```
| 1.0 | Error linking ThyraEpetraAdapters_TestThyraDebugHang.exe - <!--- Provide a general summary of the issue in the Title above. -->
<!---
Note that anything between these delimiters is a comment that will not appear
in the issue description once created. Click on the Preview tab to see what
everything will look like when you submit.
-->
<!---
Feel free to delete anything from this template that is not applicable to the
issue you are submitting.
-->
<!---
Replace <teamName> below with the appropriate Trilinos package/team name.
-->
@mhoemmen
<!---
Assignees: If you know anyone who should likely tackle this issue, select them
from the Assignees drop-down on the right.
-->
<!---
Lables: Choose any applicable package names from the Labels drop-down on the
right. Additionally, choose a label to indicate the type of issue, for
instance, bug, build, documentation, enhancement, etc.
-->
## Expectations
<!---
Tell us what you think should happen, how you think things should work, what
you would like to see in the documentation, etc.
-->
I am trying to build Trilinos with the options listed [here](https://peridigm.sandia.gov/content/trilinos) on a Fedora Linux VM (gcc 7.2.1).
## Current Behavior
<!---
Tell us how the current behavior fails to meet your expectations in some way.
-->
While linking ThyraEpetraAdapters_TestThyraDebugHang.exe I get the following error:
```
[ 86%] Linking CXX executable ThyraEpetraAdapters_TestThyraDebugHang.exe
CMakeFiles/ThyraEpetraAdapters_TestThyraDebugHang.dir/TestThyraDebugHang.cpp.o: In function `ThyraEpetraMultiVector_HangingInParallelDebug_UnitTest::runUnitTestImpl(Teuchos::basic_FancyOStream<char, std::char_traits<char> >&, bool&) const':
TestThyraDebugHang.cpp:(.text+0xad3): undefined reference to `Thyra::DefaultSpmdVectorSpace<double>::initialize(Teuchos::RCP<Teuchos::Comm<long> const> const&, long, long, bool)'
collect2: error: ld returned 1 exit status
```
| non_priority | error linking thyraepetraadapters testthyradebughang exe note that anything between these delimiters is a comment that will not appear in the issue description once created click on the preview tab to see what everything will look like when you submit feel free to delete anything from this template that is not applicable to the issue you are submitting replace below with the appropriate trilinos package team name mhoemmen assignees if you know anyone who should likely tackle this issue select them from the assignees drop down on the right lables choose any applicable package names from the labels drop down on the right additionally choose a label to indicate the type of issue for instance bug build documentation enhancement etc expectations tell us what you think should happen how you think things should work what you would like to see in the documentation etc i am trying to build trilinos with the options listed on a fedora linux vm gcc current behavior tell us how the current behavior fails to meet your expectations in some way while linking thyraepetraadapters testthyradebughang exe i get the following error linking cxx executable thyraepetraadapters testthyradebughang exe cmakefiles thyraepetraadapters testthyradebughang dir testthyradebughang cpp o in function thyraepetramultivector hanginginparalleldebug unittest rununittestimpl teuchos basic fancyostream bool const testthyradebughang cpp text undefined reference to thyra defaultspmdvectorspace initialize teuchos rcp const const long long bool error ld returned exit status | 0 |
233,907 | 17,911,927,250 | IssuesEvent | 2021-09-09 06:50:52 | ocbe-uio/cellmigRation | https://api.github.com/repos/ocbe-uio/cellmigRation | opened | Document differences between cellmigRation and cellMAPtracer | documentation | I suggest a small paragraph linking this package with the one for cellMAPtracer, explaining the difference between the two softwares (which I often forget).
| 1.0 | Document differences between cellmigRation and cellMAPtracer - I suggest a small paragraph linking this package with the one for cellMAPtracer, explaining the difference between the two softwares (which I often forget).
| non_priority | document differences between cellmigration and cellmaptracer i suggest a small paragraph linking this package with the one for cellmaptracer explaining the difference between the two softwares which i often forget | 0 |
260,124 | 27,765,186,304 | IssuesEvent | 2023-03-16 10:59:16 | lightbend/kalix-jvm-sdk | https://api.github.com/repos/lightbend/kalix-jvm-sdk | closed | Add FOSSA license and dependency checks | kalix-proxy Security | In other projects we use FOSSA to help verify we don't depend on libraries whose license doesn't permit it, and to check none of the dependencies have known outstanding CVE's.
We should probably set this up here, too. Do we want to put it in GitHub Actions (like our other open source repo's) or CircleCI (like our other Akkaserverless repo's)? | True | Add FOSSA license and dependency checks - In other projects we use FOSSA to help verify we don't depend on libraries whose license doesn't permit it, and to check none of the dependencies have known outstanding CVE's.
We should probably set this up here, too. Do we want to put it in GitHub Actions (like our other open source repo's) or CircleCI (like our other Akkaserverless repo's)? | non_priority | add fossa license and dependency checks in other projects we use fossa to help verify we don t depend on libraries whose license doesn t permit it and to check none of the dependencies have known outstanding cve s we should probably set this up here too do we want to put it in github actions like our other open source repo s or circleci like our other akkaserverless repo s | 0 |
116,243 | 14,938,574,164 | IssuesEvent | 2021-01-25 15:55:52 | WordPress/gutenberg | https://api.github.com/repos/WordPress/gutenberg | opened | Enable the user to switch which entity is being previewed in the template editor | Needs Design Feedback [Feature] Full Site Editing | The existing flow from editing a post to editing the post template creates a view where the user is editing a template with a specific entity loaded in to provide context.
In the site editor it is also currently possible to edit a template without any context, and see placeholder content in lieu of actual post data.
Since all the pieces exist to do so, we should consider allowing the user to switch which entity is being previewed while editing a template. This will be a useful tool to ensure that any template edits in the current session will play nicely with a variety of compatible entires.
We can utilise the "View" menu (proposed in #27847) to contain this affordance.
Because the organisation of content can get quite complicated on larger sites, we might use the drilldown pattern from the site editor navigation to keep this menu simple:
https://user-images.githubusercontent.com/846565/105729744-710c6b00-5f25-11eb-9cfb-5c3fcf9e8212.mp4
It is (hopefully) quite easy to imagine different sections for different content types.
Once content is selected, an interstitial indicates which blocks are looking up post data. | 1.0 | Enable the user to switch which entity is being previewed in the template editor - The existing flow from editing a post to editing the post template creates a view where the user is editing a template with a specific entity loaded in to provide context.
In the site editor it is also currently possible to edit a template without any context, and see placeholder content in lieu of actual post data.
Since all the pieces exist to do so, we should consider allowing the user to switch which entity is being previewed while editing a template. This will be a useful tool to ensure that any template edits in the current session will play nicely with a variety of compatible entires.
We can utilise the "View" menu (proposed in #27847) to contain this affordance.
Because the organisation of content can get quite complicated on larger sites, we might use the drilldown pattern from the site editor navigation to keep this menu simple:
https://user-images.githubusercontent.com/846565/105729744-710c6b00-5f25-11eb-9cfb-5c3fcf9e8212.mp4
It is (hopefully) quite easy to imagine different sections for different content types.
Once content is selected, an interstitial indicates which blocks are looking up post data. | non_priority | enable the user to switch which entity is being previewed in the template editor the existing flow from editing a post to editing the post template creates a view where the user is editing a template with a specific entity loaded in to provide context in the site editor it is also currently possible to edit a template without any context and see placeholder content in lieu of actual post data since all the pieces exist to do so we should consider allowing the user to switch which entity is being previewed while editing a template this will be a useful tool to ensure that any template edits in the current session will play nicely with a variety of compatible entires we can utilise the view menu proposed in to contain this affordance because the organisation of content can get quite complicated on larger sites we might use the drilldown pattern from the site editor navigation to keep this menu simple it is hopefully quite easy to imagine different sections for different content types once content is selected an interstitial indicates which blocks are looking up post data | 0 |
126,868 | 12,301,134,798 | IssuesEvent | 2020-05-11 14:58:49 | inmanta/inmanta | https://api.github.com/repos/inmanta/inmanta | closed | agent incomplete in glossary? | documentation | It appears the description for agent in the glossary is not complete. It reads "Agents group resources This grouping is free to choose by the designer of a resource, however this determines". | 1.0 | agent incomplete in glossary? - It appears the description for agent in the glossary is not complete. It reads "Agents group resources This grouping is free to choose by the designer of a resource, however this determines". | non_priority | agent incomplete in glossary it appears the description for agent in the glossary is not complete it reads agents group resources this grouping is free to choose by the designer of a resource however this determines | 0 |
112,456 | 17,089,627,634 | IssuesEvent | 2021-07-08 15:45:16 | turkdevops/atom | https://api.github.com/repos/turkdevops/atom | closed | CVE-2021-23358 (High) detected in multiple libraries - autoclosed | security vulnerability | ## CVE-2021-23358 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>underscore-1.9.1.tgz</b>, <b>underscore-1.6.0.tgz</b>, <b>underscore-1.8.3.tgz</b></p></summary>
<p>
<details><summary><b>underscore-1.9.1.tgz</b></p></summary>
<p>JavaScript's functional programming helper library.</p>
<p>Library home page: <a href="https://registry.npmjs.org/underscore/-/underscore-1.9.1.tgz">https://registry.npmjs.org/underscore/-/underscore-1.9.1.tgz</a></p>
<p>Path to dependency file: atom/script/package.json</p>
<p>Path to vulnerable library: atom/script/node_modules/underscore/package.json,atom/node_modules/underscore/package.json</p>
<p>
Dependency Hierarchy:
- donna-1.0.16.tgz (Root Library)
- :x: **underscore-1.9.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>underscore-1.6.0.tgz</b></p></summary>
<p>JavaScript's functional programming helper library.</p>
<p>Library home page: <a href="https://registry.npmjs.org/underscore/-/underscore-1.6.0.tgz">https://registry.npmjs.org/underscore/-/underscore-1.6.0.tgz</a></p>
<p>Path to dependency file: atom/package.json</p>
<p>Path to vulnerable library: atom/node_modules/roaster/node_modules/underscore/package.json,atom/script/node_modules/legal-eagle/node_modules/underscore/package.json,atom/script/node_modules/tello/node_modules/underscore/package.json,atom/spec/fixtures/git/repo-with-submodules/You-Dont-Need-jQuery/node_modules/underscore/package.json</p>
<p>
Dependency Hierarchy:
- isparta-4.1.1.tgz (Root Library)
- nomnomnomnom-2.0.1.tgz
- :x: **underscore-1.6.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>underscore-1.8.3.tgz</b></p></summary>
<p>JavaScript's functional programming helper library.</p>
<p>Library home page: <a href="https://registry.npmjs.org/underscore/-/underscore-1.8.3.tgz">https://registry.npmjs.org/underscore/-/underscore-1.8.3.tgz</a></p>
<p>Path to dependency file: atom/script/package.json</p>
<p>Path to vulnerable library: atom/script/node_modules/underscore-plus/node_modules/underscore/package.json</p>
<p>
Dependency Hierarchy:
- season-5.3.0.tgz (Root Library)
- fs-plus-2.10.1.tgz
- underscore-plus-1.6.8.tgz
- :x: **underscore-1.8.3.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/atom/commit/0dd3ca131788e5d5aeaf0e095ce6ca46d6df0b9f">0dd3ca131788e5d5aeaf0e095ce6ca46d6df0b9f</a></p>
<p>Found in base branch: <b>electron-upgrade</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 package underscore from 1.13.0-0 and before 1.13.0-2, from 1.3.2 and before 1.12.1 are vulnerable to Arbitrary Code Injection via the template function, particularly when a variable property is passed as an argument as it is not sanitized.
<p>Publish Date: 2021-03-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23358>CVE-2021-23358</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.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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-23358">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23358</a></p>
<p>Release Date: 2021-03-29</p>
<p>Fix Resolution: underscore - 1.12.1,1.13.0-2</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-23358 (High) detected in multiple libraries - autoclosed - ## CVE-2021-23358 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>underscore-1.9.1.tgz</b>, <b>underscore-1.6.0.tgz</b>, <b>underscore-1.8.3.tgz</b></p></summary>
<p>
<details><summary><b>underscore-1.9.1.tgz</b></p></summary>
<p>JavaScript's functional programming helper library.</p>
<p>Library home page: <a href="https://registry.npmjs.org/underscore/-/underscore-1.9.1.tgz">https://registry.npmjs.org/underscore/-/underscore-1.9.1.tgz</a></p>
<p>Path to dependency file: atom/script/package.json</p>
<p>Path to vulnerable library: atom/script/node_modules/underscore/package.json,atom/node_modules/underscore/package.json</p>
<p>
Dependency Hierarchy:
- donna-1.0.16.tgz (Root Library)
- :x: **underscore-1.9.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>underscore-1.6.0.tgz</b></p></summary>
<p>JavaScript's functional programming helper library.</p>
<p>Library home page: <a href="https://registry.npmjs.org/underscore/-/underscore-1.6.0.tgz">https://registry.npmjs.org/underscore/-/underscore-1.6.0.tgz</a></p>
<p>Path to dependency file: atom/package.json</p>
<p>Path to vulnerable library: atom/node_modules/roaster/node_modules/underscore/package.json,atom/script/node_modules/legal-eagle/node_modules/underscore/package.json,atom/script/node_modules/tello/node_modules/underscore/package.json,atom/spec/fixtures/git/repo-with-submodules/You-Dont-Need-jQuery/node_modules/underscore/package.json</p>
<p>
Dependency Hierarchy:
- isparta-4.1.1.tgz (Root Library)
- nomnomnomnom-2.0.1.tgz
- :x: **underscore-1.6.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>underscore-1.8.3.tgz</b></p></summary>
<p>JavaScript's functional programming helper library.</p>
<p>Library home page: <a href="https://registry.npmjs.org/underscore/-/underscore-1.8.3.tgz">https://registry.npmjs.org/underscore/-/underscore-1.8.3.tgz</a></p>
<p>Path to dependency file: atom/script/package.json</p>
<p>Path to vulnerable library: atom/script/node_modules/underscore-plus/node_modules/underscore/package.json</p>
<p>
Dependency Hierarchy:
- season-5.3.0.tgz (Root Library)
- fs-plus-2.10.1.tgz
- underscore-plus-1.6.8.tgz
- :x: **underscore-1.8.3.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/atom/commit/0dd3ca131788e5d5aeaf0e095ce6ca46d6df0b9f">0dd3ca131788e5d5aeaf0e095ce6ca46d6df0b9f</a></p>
<p>Found in base branch: <b>electron-upgrade</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 package underscore from 1.13.0-0 and before 1.13.0-2, from 1.3.2 and before 1.12.1 are vulnerable to Arbitrary Code Injection via the template function, particularly when a variable property is passed as an argument as it is not sanitized.
<p>Publish Date: 2021-03-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23358>CVE-2021-23358</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.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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-23358">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23358</a></p>
<p>Release Date: 2021-03-29</p>
<p>Fix Resolution: underscore - 1.12.1,1.13.0-2</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 underscore tgz underscore tgz underscore tgz underscore tgz javascript s functional programming helper library library home page a href path to dependency file atom script package json path to vulnerable library atom script node modules underscore package json atom node modules underscore package json dependency hierarchy donna tgz root library x underscore tgz vulnerable library underscore tgz javascript s functional programming helper library library home page a href path to dependency file atom package json path to vulnerable library atom node modules roaster node modules underscore package json atom script node modules legal eagle node modules underscore package json atom script node modules tello node modules underscore package json atom spec fixtures git repo with submodules you dont need jquery node modules underscore package json dependency hierarchy isparta tgz root library nomnomnomnom tgz x underscore tgz vulnerable library underscore tgz javascript s functional programming helper library library home page a href path to dependency file atom script package json path to vulnerable library atom script node modules underscore plus node modules underscore package json dependency hierarchy season tgz root library fs plus tgz underscore plus tgz x underscore tgz vulnerable library found in head commit a href found in base branch electron upgrade vulnerability details the package underscore from and before from and before are vulnerable to arbitrary code injection via the template function particularly when a variable property is passed as an argument as it is not sanitized publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required high user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution underscore step up your open source security game with whitesource | 0 |
65,211 | 16,137,302,514 | IssuesEvent | 2021-04-29 13:25:42 | NOAA-EMC/UFS_UTILS | https://api.github.com/repos/NOAA-EMC/UFS_UTILS | closed | Update to the official hpc stack v1.1.0 | build | Currently, UFS_UTILS is built with a beta version (v1.0.0) of the hpc stack on Jet, Hera, Dell and Orion. Update to the official version (v1.1.0) to be consistent with other repositories (such as the global workflow). | 1.0 | Update to the official hpc stack v1.1.0 - Currently, UFS_UTILS is built with a beta version (v1.0.0) of the hpc stack on Jet, Hera, Dell and Orion. Update to the official version (v1.1.0) to be consistent with other repositories (such as the global workflow). | non_priority | update to the official hpc stack currently ufs utils is built with a beta version of the hpc stack on jet hera dell and orion update to the official version to be consistent with other repositories such as the global workflow | 0 |
47,893 | 5,919,917,969 | IssuesEvent | 2017-05-22 18:55:55 | StackIQ/stacki | https://api.github.com/repos/StackIQ/stacki | closed | "stack report attrfile" fails | bug needs testing | When you execute:
stack report attrfile
You'll get:
stack.commands.report.attrfile: AttributeError -- DatabaseConnection instance has no attribute 'getHostAttrs' | 1.0 | "stack report attrfile" fails - When you execute:
stack report attrfile
You'll get:
stack.commands.report.attrfile: AttributeError -- DatabaseConnection instance has no attribute 'getHostAttrs' | non_priority | stack report attrfile fails when you execute stack report attrfile you ll get stack commands report attrfile attributeerror databaseconnection instance has no attribute gethostattrs | 0 |
28,951 | 13,003,996,820 | IssuesEvent | 2020-07-24 08:03:37 | terraform-providers/terraform-provider-azurerm | https://api.github.com/repos/terraform-providers/terraform-provider-azurerm | closed | Updating `azurerm_automation_runbook` configuration removes `azurerm_automation_job_schedule` and needs to be recreated | bug service/automation | <!--- Please keep this note for the community --->
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
### Terraform 0.12.25 and AzureRM Provider Version 2.11
### Affected Resource(s)
<!--- Please list the affected resources and data sources. --->
* `azurerm_automation_job_schedule`
* `azurerm_automation_runbook`
### Terraform Configuration Files
```terraform
resource "azurerm_automation_runbook" "disk_snapshot" {
name = "DiskSnapshots"
location = azurerm_resource_group.backup_rsg.location
resource_group_name = azurerm_resource_group.backup_rsg.name
automation_account_name = azurerm_automation_account.backup_automation.name
log_verbose = "true"
log_progress = "true"
description = "Snapshot disk runbook"
runbook_type = "PowerShell"
content = file("./DiskSnapshot.ps1")
publish_content_link{
uri = ""
}
}
resource "azurerm_automation_schedule" "daily_schedule" {
name = "Daily"
resource_group_name = azurerm_resource_group.backup_rsg.name
automation_account_name = azurerm_automation_account.backup_automation.name
frequency = "Day"
interval = 1
timezone = "UTC"
start_time = "2020-05-29T18:00:00Z"
description = "Daily Schedule"
}
resource "azurerm_automation_job_schedule" "daily_job" {
resource_group_name = azurerm_resource_group.backup_rsg.name
automation_account_name = azurerm_automation_account.backup_automation.name
schedule_name = azurerm_automation_schedule.daily_schedule.name
runbook_name = azurerm_automation_runbook.disk_snapshot.name
parameters = {
retentionindays = 14
}
}
```
### Description of Issue
All of the resources are managed by `Terraform`, on first `create` everything works as expected. Then when one updates `azurerm_automation_runbook` configuration then applying it, this works as expected. The problem arises in next subsequent `terraform apply` because it tries to create
`azurerm_automation_job_schedule` again, but it already exists correctly in `Azure`.
### Expected Behavior
`azurerm_automation_job_schedule` resources are kept in state and do not need to be created again when `azurerm_automation_runbook` was updated in-place.
### Actual Behavior
`terraform apply` after updating `azurerm_automation_runbook`
```terraform
# azurerm_automation_job_schedule.daily_job will be created
+ resource "azurerm_automation_job_schedule" "daily_job" {
+ automation_account_name = "automation-account"
+ id = (known after apply)
+ job_schedule_id = (known after apply)
+ parameters = {
+ "retentionindays" = "14"
+ "snapshotfrequencytag" = "Daily"
}
+ resource_group_name = "disk-backups"
+ runbook_name = "DiskSnapshots"
+ schedule_name = "Daily"
}
```
Agree to the changes then error is thrown sometime during the run:
```
azurerm_automation_job_schedule.daily_job: Creating...
Error: automation.JobScheduleClient#Create: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="A job schedule for the specified runbook and schedule already exists."
on runbook.tf line 71, in resource "azurerm_automation_job_schedule" "daily_job":
71: resource "azurerm_automation_job_schedule" "daily_job" {
```
### Steps to Reproduce
<!--- Please list the steps required to reproduce the issue. --->
1. Update configuration and/or `content` of `azurerm_automation_runbook` resource
1. `terraform apply`, you will see it works as expected to update runbook resource
1. `terraform apply` again you will see that `azurerm_automation_job_schedule` needs to be created.
1. Cannot apply because `azurerm_automation_job_schedule` resources already/still exist in `Azure`
### References
Maybe related #6466 #4851 | 1.0 | Updating `azurerm_automation_runbook` configuration removes `azurerm_automation_job_schedule` and needs to be recreated - <!--- Please keep this note for the community --->
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
### Terraform 0.12.25 and AzureRM Provider Version 2.11
### Affected Resource(s)
<!--- Please list the affected resources and data sources. --->
* `azurerm_automation_job_schedule`
* `azurerm_automation_runbook`
### Terraform Configuration Files
```terraform
resource "azurerm_automation_runbook" "disk_snapshot" {
name = "DiskSnapshots"
location = azurerm_resource_group.backup_rsg.location
resource_group_name = azurerm_resource_group.backup_rsg.name
automation_account_name = azurerm_automation_account.backup_automation.name
log_verbose = "true"
log_progress = "true"
description = "Snapshot disk runbook"
runbook_type = "PowerShell"
content = file("./DiskSnapshot.ps1")
publish_content_link{
uri = ""
}
}
resource "azurerm_automation_schedule" "daily_schedule" {
name = "Daily"
resource_group_name = azurerm_resource_group.backup_rsg.name
automation_account_name = azurerm_automation_account.backup_automation.name
frequency = "Day"
interval = 1
timezone = "UTC"
start_time = "2020-05-29T18:00:00Z"
description = "Daily Schedule"
}
resource "azurerm_automation_job_schedule" "daily_job" {
resource_group_name = azurerm_resource_group.backup_rsg.name
automation_account_name = azurerm_automation_account.backup_automation.name
schedule_name = azurerm_automation_schedule.daily_schedule.name
runbook_name = azurerm_automation_runbook.disk_snapshot.name
parameters = {
retentionindays = 14
}
}
```
### Description of Issue
All of the resources are managed by `Terraform`, on first `create` everything works as expected. Then when one updates `azurerm_automation_runbook` configuration then applying it, this works as expected. The problem arises in next subsequent `terraform apply` because it tries to create
`azurerm_automation_job_schedule` again, but it already exists correctly in `Azure`.
### Expected Behavior
`azurerm_automation_job_schedule` resources are kept in state and do not need to be created again when `azurerm_automation_runbook` was updated in-place.
### Actual Behavior
`terraform apply` after updating `azurerm_automation_runbook`
```terraform
# azurerm_automation_job_schedule.daily_job will be created
+ resource "azurerm_automation_job_schedule" "daily_job" {
+ automation_account_name = "automation-account"
+ id = (known after apply)
+ job_schedule_id = (known after apply)
+ parameters = {
+ "retentionindays" = "14"
+ "snapshotfrequencytag" = "Daily"
}
+ resource_group_name = "disk-backups"
+ runbook_name = "DiskSnapshots"
+ schedule_name = "Daily"
}
```
Agree to the changes then error is thrown sometime during the run:
```
azurerm_automation_job_schedule.daily_job: Creating...
Error: automation.JobScheduleClient#Create: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="A job schedule for the specified runbook and schedule already exists."
on runbook.tf line 71, in resource "azurerm_automation_job_schedule" "daily_job":
71: resource "azurerm_automation_job_schedule" "daily_job" {
```
### Steps to Reproduce
<!--- Please list the steps required to reproduce the issue. --->
1. Update configuration and/or `content` of `azurerm_automation_runbook` resource
1. `terraform apply`, you will see it works as expected to update runbook resource
1. `terraform apply` again you will see that `azurerm_automation_job_schedule` needs to be created.
1. Cannot apply because `azurerm_automation_job_schedule` resources already/still exist in `Azure`
### References
Maybe related #6466 #4851 | non_priority | updating azurerm automation runbook configuration removes azurerm automation job schedule and needs to be recreated community note please vote on this issue by adding a 👍 to the original issue to help the community and maintainers prioritize this request please do not leave or me too comments they generate extra noise for issue followers and do not help prioritize the request if you are interested in working on this issue or have submitted a pull request please leave a comment terraform and azurerm provider version affected resource s azurerm automation job schedule azurerm automation runbook terraform configuration files terraform resource azurerm automation runbook disk snapshot name disksnapshots location azurerm resource group backup rsg location resource group name azurerm resource group backup rsg name automation account name azurerm automation account backup automation name log verbose true log progress true description snapshot disk runbook runbook type powershell content file disksnapshot publish content link uri resource azurerm automation schedule daily schedule name daily resource group name azurerm resource group backup rsg name automation account name azurerm automation account backup automation name frequency day interval timezone utc start time description daily schedule resource azurerm automation job schedule daily job resource group name azurerm resource group backup rsg name automation account name azurerm automation account backup automation name schedule name azurerm automation schedule daily schedule name runbook name azurerm automation runbook disk snapshot name parameters retentionindays description of issue all of the resources are managed by terraform on first create everything works as expected then when one updates azurerm automation runbook configuration then applying it this works as expected the problem arises in next subsequent terraform apply because it tries to create azurerm automation job schedule again but it already exists correctly in azure expected behavior azurerm automation job schedule resources are kept in state and do not need to be created again when azurerm automation runbook was updated in place actual behavior terraform apply after updating azurerm automation runbook terraform azurerm automation job schedule daily job will be created resource azurerm automation job schedule daily job automation account name automation account id known after apply job schedule id known after apply parameters retentionindays snapshotfrequencytag daily resource group name disk backups runbook name disksnapshots schedule name daily agree to the changes then error is thrown sometime during the run azurerm automation job schedule daily job creating error automation jobscheduleclient create failure responding to request statuscode original error autorest azure service returned an error status code badrequest message a job schedule for the specified runbook and schedule already exists on runbook tf line in resource azurerm automation job schedule daily job resource azurerm automation job schedule daily job steps to reproduce update configuration and or content of azurerm automation runbook resource terraform apply you will see it works as expected to update runbook resource terraform apply again you will see that azurerm automation job schedule needs to be created cannot apply because azurerm automation job schedule resources already still exist in azure references maybe related | 0 |
443,401 | 30,888,202,513 | IssuesEvent | 2023-08-04 00:59:42 | open-metadata/OpenMetadata | https://api.github.com/repos/open-metadata/OpenMetadata | closed | OpenMetadata JAVA is not using env proxy variables. | documentation | Hello,
I have OpenMetadata instance installed in Kubernetes cluster. I want to set SSO with Keycloak, We also have KeyCloak instance in another K8S cluster. We followed official documentation and created secret and set URLs for publicKeys, authority, callbackUrl and clientId.
After log in to OpenMetadata GUI, put KeyCloak user we are redirected to OpenMetadata, but we receive this error message:
`An exception with message [No key found in with kid PIZjaqGKkYQ7_li7PUo6AfTaQ_r4Hx335oGs9znZM_A] was thrown while processing request.`
In logs from openmetadata container, its showing error message, that it can't resolve my KeyCloak domain:
` Suppressed: com.auth0.jwk.NetworkException: Cannot obtain jwks from url https://MY_DOMAIN/auth/realms/xxx/protocol/openid-connect/certs
at com.auth0.jwk.UrlJwkProvider.getJwks(UrlJwkProvider.java:139)
at com.auth0.jwk.UrlJwkProvider.getAll(UrlJwkProvider.java:145)
at com.auth0.jwk.UrlJwkProvider.get(UrlJwkProvider.java:163)
at org.openmetadata.service.security.MultiUrlJwkProvider.get(MultiUrlJwkProvider.java:37)
... 66 common frames omitted
Caused by: java.net.UnknownHostException: MY_DOMAIN
`
The thing is, I set env variables for proxy for that container and from the container I can reach and recieve that publickeys with curl command from the exact URL.
It seems that JAVA is not using env variables with proxy settings. Is here some way how to use proxy settings for JAVA in Open-Metadata ?
| 1.0 | OpenMetadata JAVA is not using env proxy variables. - Hello,
I have OpenMetadata instance installed in Kubernetes cluster. I want to set SSO with Keycloak, We also have KeyCloak instance in another K8S cluster. We followed official documentation and created secret and set URLs for publicKeys, authority, callbackUrl and clientId.
After log in to OpenMetadata GUI, put KeyCloak user we are redirected to OpenMetadata, but we receive this error message:
`An exception with message [No key found in with kid PIZjaqGKkYQ7_li7PUo6AfTaQ_r4Hx335oGs9znZM_A] was thrown while processing request.`
In logs from openmetadata container, its showing error message, that it can't resolve my KeyCloak domain:
` Suppressed: com.auth0.jwk.NetworkException: Cannot obtain jwks from url https://MY_DOMAIN/auth/realms/xxx/protocol/openid-connect/certs
at com.auth0.jwk.UrlJwkProvider.getJwks(UrlJwkProvider.java:139)
at com.auth0.jwk.UrlJwkProvider.getAll(UrlJwkProvider.java:145)
at com.auth0.jwk.UrlJwkProvider.get(UrlJwkProvider.java:163)
at org.openmetadata.service.security.MultiUrlJwkProvider.get(MultiUrlJwkProvider.java:37)
... 66 common frames omitted
Caused by: java.net.UnknownHostException: MY_DOMAIN
`
The thing is, I set env variables for proxy for that container and from the container I can reach and recieve that publickeys with curl command from the exact URL.
It seems that JAVA is not using env variables with proxy settings. Is here some way how to use proxy settings for JAVA in Open-Metadata ?
| non_priority | openmetadata java is not using env proxy variables hello i have openmetadata instance installed in kubernetes cluster i want to set sso with keycloak we also have keycloak instance in another cluster we followed official documentation and created secret and set urls for publickeys authority callbackurl and clientid after log in to openmetadata gui put keycloak user we are redirected to openmetadata but we receive this error message an exception with message was thrown while processing request in logs from openmetadata container its showing error message that it can t resolve my keycloak domain suppressed com jwk networkexception cannot obtain jwks from url at com jwk urljwkprovider getjwks urljwkprovider java at com jwk urljwkprovider getall urljwkprovider java at com jwk urljwkprovider get urljwkprovider java at org openmetadata service security multiurljwkprovider get multiurljwkprovider java common frames omitted caused by java net unknownhostexception my domain the thing is i set env variables for proxy for that container and from the container i can reach and recieve that publickeys with curl command from the exact url it seems that java is not using env variables with proxy settings is here some way how to use proxy settings for java in open metadata | 0 |
40,909 | 10,592,810,827 | IssuesEvent | 2019-10-09 13:47:32 | elastic/elasticsearch | https://api.github.com/repos/elastic/elasticsearch | opened | Make it easier to get started with building ES and importing it to the IDE | :Core/Infra/Build | Right now we require multiple `JAVA<n>_HOME` env variables to be present despite the fact that we have the ability to provision JDKs ourselves.
We are also lacking some validation in case one of these is not configured correct ( e.x. set to a missing folder or set to a JRE instead of a JDK ).
We should revisit this to make sure that we don't really need anything else than running Gradle with a supported version of the JDK. | 1.0 | Make it easier to get started with building ES and importing it to the IDE - Right now we require multiple `JAVA<n>_HOME` env variables to be present despite the fact that we have the ability to provision JDKs ourselves.
We are also lacking some validation in case one of these is not configured correct ( e.x. set to a missing folder or set to a JRE instead of a JDK ).
We should revisit this to make sure that we don't really need anything else than running Gradle with a supported version of the JDK. | non_priority | make it easier to get started with building es and importing it to the ide right now we require multiple java home env variables to be present despite the fact that we have the ability to provision jdks ourselves we are also lacking some validation in case one of these is not configured correct e x set to a missing folder or set to a jre instead of a jdk we should revisit this to make sure that we don t really need anything else than running gradle with a supported version of the jdk | 0 |
33,398 | 7,704,404,780 | IssuesEvent | 2018-05-21 12:09:33 | CleverRaven/Cataclysm-DDA | https://api.github.com/repos/CleverRaven/Cataclysm-DDA | closed | The game won't launch on a 1GB RAM system | Code: Performance Info / User Interface SDL: Tiles / Sound | After double-clicking at `cataclysm-tiles.exe`, a white blank window appears. About half a minute has past, it is still pure white. Then, suddenly, the process disappears.
I traced it under GDB:
On MSDN documentation [(here)](https://msdn.microsoft.com/en-us/library/cc704588(d=lightweight,l=en-us,v=PROT.10).aspx) exception code `0xc0000017` seems to represent something like _out of memory_.
| 0xC0000017 |
|-|
| STATUS_NO_MEMORY |
| {Not Enough Quota} Not enough virtual memory or paging file quota is available to complete the specified operation. |
----
So the reason is that when loading the default tileset `ChestHole`, there's no enough memory, while `retrodays10` works fine. But the problem is, for a fresh unzipped CDDA, there's no way to avoid the program to load `ChestHole` unless manually copy `options.json` from another computer. | 1.0 | The game won't launch on a 1GB RAM system - After double-clicking at `cataclysm-tiles.exe`, a white blank window appears. About half a minute has past, it is still pure white. Then, suddenly, the process disappears.
I traced it under GDB:
On MSDN documentation [(here)](https://msdn.microsoft.com/en-us/library/cc704588(d=lightweight,l=en-us,v=PROT.10).aspx) exception code `0xc0000017` seems to represent something like _out of memory_.
| 0xC0000017 |
|-|
| STATUS_NO_MEMORY |
| {Not Enough Quota} Not enough virtual memory or paging file quota is available to complete the specified operation. |
----
So the reason is that when loading the default tileset `ChestHole`, there's no enough memory, while `retrodays10` works fine. But the problem is, for a fresh unzipped CDDA, there's no way to avoid the program to load `ChestHole` unless manually copy `options.json` from another computer. | non_priority | the game won t launch on a ram system after double clicking at cataclysm tiles exe a white blank window appears about half a minute has past it is still pure white then suddenly the process disappears i traced it under gdb on msdn documentation exception code seems to represent something like out of memory status no memory not enough quota not enough virtual memory or paging file quota is available to complete the specified operation so the reason is that when loading the default tileset chesthole there s no enough memory while works fine but the problem is for a fresh unzipped cdda there s no way to avoid the program to load chesthole unless manually copy options json from another computer | 0 |
14,412 | 10,164,260,188 | IssuesEvent | 2019-08-07 11:13:37 | invertase/react-native-firebase | https://api.github.com/repos/invertase/react-native-firebase | closed | [v6] Database pod not installed | Service: Database Version: 6.x.x | <!---
Hello there you awesome person;
Please note that the issue list of this repo is exclusively for bug reports;
1) For feature requests please visit our [Feature Request Board](https://boards.invertase.io/react-native-firebase).
2) For questions and support please use our Discord chat: https://discord.gg/C9aK28N or Stack Overflow: https://stackoverflow.com/questions/tagged/react-native-firebase
3) If this is a setup issue then please make sure you've correctly followed the setup guides, most setup issues such as 'duplicate dex files', 'default app has not been initialized' etc are all down to an incorrect setup as the guides haven't been correctly followed.
-->
<!-- NOTE: You can change any of the `[ ]` to `[x]` to mark an option(s) as selected -->
<!-- PLEASE DO NOT REMOVE ANY SECTIONS FROM THIS ISSUE TEMPLATE -->
<!-- Leave them as they are even if they're irrelevant to your issue -->
## Issue
<!-- Please describe your issue here --^ and provide as much detail as you can. -->
<!-- Include code snippets that show your usages of the library in the context of your project. -->
<!-- Snippets that also show how and where the library is imported in JS are useful to debug issues relating to importing or methods not found issues -->
After linking Database package and running pod install, the FirebaseDatabase pod does not get installed.
It happens because of a missing dependency in packages/database/RNFBDatabase.podspec
Once you add `s.dependency 'Firebase/Database', '~> 6.5.0'` the pod get installed
---
## Project Files
<!-- Provide the contents of key project files which will help to debug -->
<!-- For Example: -->
<!-- - iOS: `Podfile` contents. -->
<!-- - Android: `android/build.gradle` contents. -->
<!-- - Android: `android/app/build.gradle` contents. -->
<!-- - Android: `AndroidManifest.xml` contents. -->
<!-- ADD THE CONTENTS OF THE FILES IN THE PROVIDED CODE BLOCKS BELOW -->
### iOS
<details><summary>Click To Expand</summary>
<p>
#### `ios/Podfile`:
- [ ] I'm not using Pods
- [x] I'm using Pods and my Podfile looks like:
```ruby
install! 'cocoapods', :deterministic_uuids => false
platform :ios, '9.0'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
target 'App' do
# Pods for App
pod 'React', :path => '../node_modules/react-native/'
pod 'React-Core', :path => '../node_modules/react-native/React'
pod 'React-DevSupport', :path => '../node_modules/react-native/React'
pod 'React-fishhook', :path => '../node_modules/react-native/Libraries/fishhook'
pod 'React-RCTActionSheet', :path => '../node_modules/react-native/Libraries/ActionSheetIOS'
pod 'React-RCTAnimation', :path => '../node_modules/react-native/Libraries/NativeAnimation'
pod 'React-RCTBlob', :path => '../node_modules/react-native/Libraries/Blob'
pod 'React-RCTImage', :path => '../node_modules/react-native/Libraries/Image'
pod 'React-RCTLinking', :path => '../node_modules/react-native/Libraries/LinkingIOS'
pod 'React-RCTNetwork', :path => '../node_modules/react-native/Libraries/Network'
pod 'React-RCTSettings', :path => '../node_modules/react-native/Libraries/Settings'
pod 'React-RCTText', :path => '../node_modules/react-native/Libraries/Text'
pod 'React-RCTVibration', :path => '../node_modules/react-native/Libraries/Vibration'
pod 'React-RCTWebSocket', :path => '../node_modules/react-native/Libraries/WebSocket'
pod 'React-cxxreact', :path => '../node_modules/react-native/ReactCommon/cxxreact'
pod 'React-jsi', :path => '../node_modules/react-native/ReactCommon/jsi'
pod 'React-jsiexecutor', :path => '../node_modules/react-native/ReactCommon/jsiexecutor'
pod 'React-jsinspector', :path => '../node_modules/react-native/ReactCommon/jsinspector'
pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'
pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'
pod 'RNSVG', :path => '../node_modules/react-native-svg'
pod 'RNVectorIcons', :path => '../node_modules/react-native-vector-icons'
pod 'ReactNativeNavigation', :path => '../node_modules/react-native-navigation'
pod 'RNFBApp', :path => '../node_modules/@react-native-firebase/app'
pod 'RNFBStorage', :path => '../node_modules/@react-native-firebase/storage'
pod 'RNFBMessaging', :path => '../node_modules/@react-native-firebase/messaging'
pod 'RNFBCrashlytics', :path => '../node_modules/@react-native-firebase/crashlytics'
pod 'RNFBDatabase', :path => '../node_modules/@react-native-firebase/database'
pod 'RNFBFirestore', :path => '../node_modules/@react-native-firebase/firestore'
pod 'RNFBAuth', :path => '../node_modules/@react-native-firebase/auth'
pod 'RNFBFunctions', :path => '../node_modules/@react-native-firebase/functions'
target 'AppTests' do
inherit! :search_paths
# Pods for testing
end
# use_native_modules!
end
target 'App-tvOS' do
# Pods for App-tvOS
target 'App-tvOSTests' do
inherit! :search_paths
# Pods for testing
end
end
```
#### `AppDelegate.m`:
```objc
// N/A
```
</p>
</details>
---
### Android
<details><summary>Click To Expand</summary>
<p>
#### Have you converted to AndroidX?
<!--- Mark any options that apply below -->
- [ ] my application is an AndroidX application?
- [ ] I am using `android/gradle.settings` `jetifier=true` for Android compatibility?
- [ ] I am using the NPM package `jetifier` for react-native compatibility?
#### `android/build.gradle`:
```groovy
// N/A
```
#### `android/app/build.gradle`:
```groovy
// N/A
```
#### `android/settings.gradle`:
```groovy
// N/A
```
#### `MainApplication.java`:
```java
// N/A
```
#### `AndroidManifest.xml`:
```xml
<!-- N/A -->
```
</p>
</details>
---
## Environment
<details><summary>Click To Expand</summary>
<p>
**`react-native info` output:**
<!-- Please run `react-native info` on your terminal and paste the contents into the code block below -->
```
System:
OS: macOS 10.14.5
CPU: (8) x64 Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
Memory: 9.70 GB / 64.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.16.0 - /usr/local/opt/node@10/bin/node
Yarn: 1.16.0 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/opt/node@10/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.4, macOS 10.14, tvOS 12.4, watchOS 5.3
Android SDK:
API Levels: 23, 24, 26, 27, 28
Build Tools: 23.0.1, 26.0.3, 27.0.3, 28.0.0, 28.0.2, 28.0.3
System Images: android-23 | Intel x86 Atom_64, android-23 | Google APIs Intel x86 Atom_64, android-26 | Google APIs Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.4 AI-183.6156.11.34.5692245
Xcode: 10.3/10G8 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.6 => 16.8.6
react-native: 0.60.3 => 0.60.3
npmGlobalPackages:
```
<!-- change `[ ]` to `[x]` to select an option(s) -->
- **Platform that you're experiencing the issue on**:
- [X] iOS
- [ ] Android
- [ ] **iOS** but have not tested behavior on Android
- [ ] **Android** but have not tested behavior on iOS
- [ ] Both
- **`react-native-firebase` version you're using that has this issue:**
- `0.1.2`
- **`Firebase` module(s) you're using that has the issue:**
- `Database`
- **Are you using `TypeScript`?**
- `N`
</p>
</details>
<!-- Thanks for reading this far down ❤️ -->
<!-- High quality, detailed issues are much easier to triage for maintainers -->
<!-- For bonus points, if you put a 🔥 (:fire:) emojii at the start of the issue title we'll know -->
<!-- that you took the time to fill this out correctly, or, at least read this far -->
---
Think `react-native-firebase` is great? Please consider supporting all of the project maintainers and contributors by donating via our [Open Collective](https://opencollective.com/react-native-firebase/donate) where all contributors can submit expenses. [[Learn More]](https://invertase.io/oss/react-native-firebase/contributing/donations-expenses)
- 👉 Check out [`React Native Firebase`](https://twitter.com/rnfirebase) and [`Invertase`](https://twitter.com/invertaseio) on Twitter for updates on the library.
| 1.0 | [v6] Database pod not installed - <!---
Hello there you awesome person;
Please note that the issue list of this repo is exclusively for bug reports;
1) For feature requests please visit our [Feature Request Board](https://boards.invertase.io/react-native-firebase).
2) For questions and support please use our Discord chat: https://discord.gg/C9aK28N or Stack Overflow: https://stackoverflow.com/questions/tagged/react-native-firebase
3) If this is a setup issue then please make sure you've correctly followed the setup guides, most setup issues such as 'duplicate dex files', 'default app has not been initialized' etc are all down to an incorrect setup as the guides haven't been correctly followed.
-->
<!-- NOTE: You can change any of the `[ ]` to `[x]` to mark an option(s) as selected -->
<!-- PLEASE DO NOT REMOVE ANY SECTIONS FROM THIS ISSUE TEMPLATE -->
<!-- Leave them as they are even if they're irrelevant to your issue -->
## Issue
<!-- Please describe your issue here --^ and provide as much detail as you can. -->
<!-- Include code snippets that show your usages of the library in the context of your project. -->
<!-- Snippets that also show how and where the library is imported in JS are useful to debug issues relating to importing or methods not found issues -->
After linking Database package and running pod install, the FirebaseDatabase pod does not get installed.
It happens because of a missing dependency in packages/database/RNFBDatabase.podspec
Once you add `s.dependency 'Firebase/Database', '~> 6.5.0'` the pod get installed
---
## Project Files
<!-- Provide the contents of key project files which will help to debug -->
<!-- For Example: -->
<!-- - iOS: `Podfile` contents. -->
<!-- - Android: `android/build.gradle` contents. -->
<!-- - Android: `android/app/build.gradle` contents. -->
<!-- - Android: `AndroidManifest.xml` contents. -->
<!-- ADD THE CONTENTS OF THE FILES IN THE PROVIDED CODE BLOCKS BELOW -->
### iOS
<details><summary>Click To Expand</summary>
<p>
#### `ios/Podfile`:
- [ ] I'm not using Pods
- [x] I'm using Pods and my Podfile looks like:
```ruby
install! 'cocoapods', :deterministic_uuids => false
platform :ios, '9.0'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
target 'App' do
# Pods for App
pod 'React', :path => '../node_modules/react-native/'
pod 'React-Core', :path => '../node_modules/react-native/React'
pod 'React-DevSupport', :path => '../node_modules/react-native/React'
pod 'React-fishhook', :path => '../node_modules/react-native/Libraries/fishhook'
pod 'React-RCTActionSheet', :path => '../node_modules/react-native/Libraries/ActionSheetIOS'
pod 'React-RCTAnimation', :path => '../node_modules/react-native/Libraries/NativeAnimation'
pod 'React-RCTBlob', :path => '../node_modules/react-native/Libraries/Blob'
pod 'React-RCTImage', :path => '../node_modules/react-native/Libraries/Image'
pod 'React-RCTLinking', :path => '../node_modules/react-native/Libraries/LinkingIOS'
pod 'React-RCTNetwork', :path => '../node_modules/react-native/Libraries/Network'
pod 'React-RCTSettings', :path => '../node_modules/react-native/Libraries/Settings'
pod 'React-RCTText', :path => '../node_modules/react-native/Libraries/Text'
pod 'React-RCTVibration', :path => '../node_modules/react-native/Libraries/Vibration'
pod 'React-RCTWebSocket', :path => '../node_modules/react-native/Libraries/WebSocket'
pod 'React-cxxreact', :path => '../node_modules/react-native/ReactCommon/cxxreact'
pod 'React-jsi', :path => '../node_modules/react-native/ReactCommon/jsi'
pod 'React-jsiexecutor', :path => '../node_modules/react-native/ReactCommon/jsiexecutor'
pod 'React-jsinspector', :path => '../node_modules/react-native/ReactCommon/jsinspector'
pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'
pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'
pod 'RNSVG', :path => '../node_modules/react-native-svg'
pod 'RNVectorIcons', :path => '../node_modules/react-native-vector-icons'
pod 'ReactNativeNavigation', :path => '../node_modules/react-native-navigation'
pod 'RNFBApp', :path => '../node_modules/@react-native-firebase/app'
pod 'RNFBStorage', :path => '../node_modules/@react-native-firebase/storage'
pod 'RNFBMessaging', :path => '../node_modules/@react-native-firebase/messaging'
pod 'RNFBCrashlytics', :path => '../node_modules/@react-native-firebase/crashlytics'
pod 'RNFBDatabase', :path => '../node_modules/@react-native-firebase/database'
pod 'RNFBFirestore', :path => '../node_modules/@react-native-firebase/firestore'
pod 'RNFBAuth', :path => '../node_modules/@react-native-firebase/auth'
pod 'RNFBFunctions', :path => '../node_modules/@react-native-firebase/functions'
target 'AppTests' do
inherit! :search_paths
# Pods for testing
end
# use_native_modules!
end
target 'App-tvOS' do
# Pods for App-tvOS
target 'App-tvOSTests' do
inherit! :search_paths
# Pods for testing
end
end
```
#### `AppDelegate.m`:
```objc
// N/A
```
</p>
</details>
---
### Android
<details><summary>Click To Expand</summary>
<p>
#### Have you converted to AndroidX?
<!--- Mark any options that apply below -->
- [ ] my application is an AndroidX application?
- [ ] I am using `android/gradle.settings` `jetifier=true` for Android compatibility?
- [ ] I am using the NPM package `jetifier` for react-native compatibility?
#### `android/build.gradle`:
```groovy
// N/A
```
#### `android/app/build.gradle`:
```groovy
// N/A
```
#### `android/settings.gradle`:
```groovy
// N/A
```
#### `MainApplication.java`:
```java
// N/A
```
#### `AndroidManifest.xml`:
```xml
<!-- N/A -->
```
</p>
</details>
---
## Environment
<details><summary>Click To Expand</summary>
<p>
**`react-native info` output:**
<!-- Please run `react-native info` on your terminal and paste the contents into the code block below -->
```
System:
OS: macOS 10.14.5
CPU: (8) x64 Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
Memory: 9.70 GB / 64.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.16.0 - /usr/local/opt/node@10/bin/node
Yarn: 1.16.0 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/opt/node@10/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.4, macOS 10.14, tvOS 12.4, watchOS 5.3
Android SDK:
API Levels: 23, 24, 26, 27, 28
Build Tools: 23.0.1, 26.0.3, 27.0.3, 28.0.0, 28.0.2, 28.0.3
System Images: android-23 | Intel x86 Atom_64, android-23 | Google APIs Intel x86 Atom_64, android-26 | Google APIs Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.4 AI-183.6156.11.34.5692245
Xcode: 10.3/10G8 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.6 => 16.8.6
react-native: 0.60.3 => 0.60.3
npmGlobalPackages:
```
<!-- change `[ ]` to `[x]` to select an option(s) -->
- **Platform that you're experiencing the issue on**:
- [X] iOS
- [ ] Android
- [ ] **iOS** but have not tested behavior on Android
- [ ] **Android** but have not tested behavior on iOS
- [ ] Both
- **`react-native-firebase` version you're using that has this issue:**
- `0.1.2`
- **`Firebase` module(s) you're using that has the issue:**
- `Database`
- **Are you using `TypeScript`?**
- `N`
</p>
</details>
<!-- Thanks for reading this far down ❤️ -->
<!-- High quality, detailed issues are much easier to triage for maintainers -->
<!-- For bonus points, if you put a 🔥 (:fire:) emojii at the start of the issue title we'll know -->
<!-- that you took the time to fill this out correctly, or, at least read this far -->
---
Think `react-native-firebase` is great? Please consider supporting all of the project maintainers and contributors by donating via our [Open Collective](https://opencollective.com/react-native-firebase/donate) where all contributors can submit expenses. [[Learn More]](https://invertase.io/oss/react-native-firebase/contributing/donations-expenses)
- 👉 Check out [`React Native Firebase`](https://twitter.com/rnfirebase) and [`Invertase`](https://twitter.com/invertaseio) on Twitter for updates on the library.
| non_priority | database pod not installed hello there you awesome person please note that the issue list of this repo is exclusively for bug reports for feature requests please visit our for questions and support please use our discord chat or stack overflow if this is a setup issue then please make sure you ve correctly followed the setup guides most setup issues such as duplicate dex files default app has not been initialized etc are all down to an incorrect setup as the guides haven t been correctly followed issue after linking database package and running pod install the firebasedatabase pod does not get installed it happens because of a missing dependency in packages database rnfbdatabase podspec once you add s dependency firebase database the pod get installed project files ios click to expand ios podfile i m not using pods i m using pods and my podfile looks like ruby install cocoapods deterministic uuids false platform ios require relative node modules react native community cli platform ios native modules target app do pods for app pod react path node modules react native pod react core path node modules react native react pod react devsupport path node modules react native react pod react fishhook path node modules react native libraries fishhook pod react rctactionsheet path node modules react native libraries actionsheetios pod react rctanimation path node modules react native libraries nativeanimation pod react rctblob path node modules react native libraries blob pod react rctimage path node modules react native libraries image pod react rctlinking path node modules react native libraries linkingios pod react rctnetwork path node modules react native libraries network pod react rctsettings path node modules react native libraries settings pod react rcttext path node modules react native libraries text pod react rctvibration path node modules react native libraries vibration pod react rctwebsocket path node modules react native libraries websocket pod react cxxreact path node modules react native reactcommon cxxreact pod react jsi path node modules react native reactcommon jsi pod react jsiexecutor path node modules react native reactcommon jsiexecutor pod react jsinspector path node modules react native reactcommon jsinspector pod yoga path node modules react native reactcommon yoga pod doubleconversion podspec node modules react native third party podspecs doubleconversion podspec pod glog podspec node modules react native third party podspecs glog podspec pod folly podspec node modules react native third party podspecs folly podspec pod rnsvg path node modules react native svg pod rnvectoricons path node modules react native vector icons pod reactnativenavigation path node modules react native navigation pod rnfbapp path node modules react native firebase app pod rnfbstorage path node modules react native firebase storage pod rnfbmessaging path node modules react native firebase messaging pod rnfbcrashlytics path node modules react native firebase crashlytics pod rnfbdatabase path node modules react native firebase database pod rnfbfirestore path node modules react native firebase firestore pod rnfbauth path node modules react native firebase auth pod rnfbfunctions path node modules react native firebase functions target apptests do inherit search paths pods for testing end use native modules end target app tvos do pods for app tvos target app tvostests do inherit search paths pods for testing end end appdelegate m objc n a android click to expand have you converted to androidx my application is an androidx application i am using android gradle settings jetifier true for android compatibility i am using the npm package jetifier for react native compatibility android build gradle groovy n a android app build gradle groovy n a android settings gradle groovy n a mainapplication java java n a androidmanifest xml xml environment click to expand react native info output system os macos cpu intel r core tm cpu memory gb gb shell bin bash binaries node usr local opt node bin node yarn usr local bin yarn npm usr local opt node bin npm watchman usr local bin watchman sdks ios sdk platforms ios macos tvos watchos android sdk api levels build tools system images android intel atom android google apis intel atom android google apis intel atom android google apis intel atom ides android studio ai xcode usr bin xcodebuild npmpackages react react native npmglobalpackages platform that you re experiencing the issue on ios android ios but have not tested behavior on android android but have not tested behavior on ios both react native firebase version you re using that has this issue firebase module s you re using that has the issue database are you using typescript n think react native firebase is great please consider supporting all of the project maintainers and contributors by donating via our where all contributors can submit expenses 👉 check out and on twitter for updates on the library | 0 |
5,535 | 3,237,780,286 | IssuesEvent | 2015-10-14 13:38:50 | breaker1/collectionjson-validationsarrayextension | https://api.github.com/repos/breaker1/collectionjson-validationsarrayextension | closed | [Insight] Text files should end with a newline character - in phpunit.xml.dist, line 13 | code quality | **[in phpunit.xml.dist, line 13](https://github.com/breaker1/collectionjson-validationsarrayextension/blob/11f9924c0e4889b691a3f46a1aa6937d41177645/phpunit.xml.dist#L13)**
> This file ends with no newline character. It won't render properly on a terminal, and it's considered a bad practice. Add a simple line feed as the last character to fix it.
```
<testsuite name="all"><directory>test</directory></testsuite></testsuites></phpunit>
```
---------------------
_Posted from [SensioLabsInsight](https://insight.sensiolabs.com/projects/b82db368-2f12-47ab-a6aa-1859f9b8c460/analyses/1)_ | 1.0 | [Insight] Text files should end with a newline character - in phpunit.xml.dist, line 13 - **[in phpunit.xml.dist, line 13](https://github.com/breaker1/collectionjson-validationsarrayextension/blob/11f9924c0e4889b691a3f46a1aa6937d41177645/phpunit.xml.dist#L13)**
> This file ends with no newline character. It won't render properly on a terminal, and it's considered a bad practice. Add a simple line feed as the last character to fix it.
```
<testsuite name="all"><directory>test</directory></testsuite></testsuites></phpunit>
```
---------------------
_Posted from [SensioLabsInsight](https://insight.sensiolabs.com/projects/b82db368-2f12-47ab-a6aa-1859f9b8c460/analyses/1)_ | non_priority | text files should end with a newline character in phpunit xml dist line this file ends with no newline character it won t render properly on a terminal and it s considered a bad practice add a simple line feed as the last character to fix it test posted from | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.