Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 4 112 | repo_url stringlengths 33 141 | action stringclasses 3 values | title stringlengths 1 1.02k | labels stringlengths 4 1.54k | body stringlengths 1 262k | index stringclasses 17 values | text_combine stringlengths 95 262k | label stringclasses 2 values | text stringlengths 96 252k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
119,851 | 10,075,489,365 | IssuesEvent | 2019-07-24 14:21:33 | Ericsson/CodeCheckerEclipsePlugin | https://api.github.com/repos/Ericsson/CodeCheckerEclipsePlugin | opened | Extend the the test matrix with other target platfom configurations | enhancement test | The current setup of the compilation, we only test for one target platform. We can't be sure the plugin works on older releases, even though we won't use newer features.
Create a deeper test matrix with separate, older (newer) target platforms, for Travis. | 1.0 | Extend the the test matrix with other target platfom configurations - The current setup of the compilation, we only test for one target platform. We can't be sure the plugin works on older releases, even though we won't use newer features.
Create a deeper test matrix with separate, older (newer) target platforms, for Travis. | test | extend the the test matrix with other target platfom configurations the current setup of the compilation we only test for one target platform we can t be sure the plugin works on older releases even though we won t use newer features create a deeper test matrix with separate older newer target platforms for travis | 1 |
63,348 | 26,362,801,238 | IssuesEvent | 2023-01-11 14:33:33 | cityofaustin/atd-data-tech | https://api.github.com/repos/cityofaustin/atd-data-tech | closed | Off-boarding Alan | Workgroup: DTS Service: Geo Type: Operations | **Accounts/Access**
- [x] Slack
>deactivated account
- [x] AGOL
- [x] Knack - set to "Inactive"
- [x] Signs and Markings - was Supervisor, GIS QA roles
- [x] Data Tracker - was Viewer
- [x] DTS Portal - was Admin
- [x] HR Portal - System already deactivated and deleted his user role
- [x] GitHub
- [x] Miro
>Was a guest, "deleted from team"
- [x] Google Account
>Removed access to the ATD DTS folder
- [x] Separated Employee Request Form (SERF) - Submitted 12/12 - `REQ0129989`
- [ ] Request GIS Database Connections - access removed
| 1.0 | Off-boarding Alan - **Accounts/Access**
- [x] Slack
>deactivated account
- [x] AGOL
- [x] Knack - set to "Inactive"
- [x] Signs and Markings - was Supervisor, GIS QA roles
- [x] Data Tracker - was Viewer
- [x] DTS Portal - was Admin
- [x] HR Portal - System already deactivated and deleted his user role
- [x] GitHub
- [x] Miro
>Was a guest, "deleted from team"
- [x] Google Account
>Removed access to the ATD DTS folder
- [x] Separated Employee Request Form (SERF) - Submitted 12/12 - `REQ0129989`
- [ ] Request GIS Database Connections - access removed
| non_test | off boarding alan accounts access slack deactivated account agol knack set to inactive signs and markings was supervisor gis qa roles data tracker was viewer dts portal was admin hr portal system already deactivated and deleted his user role github miro was a guest deleted from team google account removed access to the atd dts folder separated employee request form serf submitted request gis database connections access removed | 0 |
128,455 | 27,262,860,778 | IssuesEvent | 2023-02-22 15:59:43 | WISE-Community/WISE-Client | https://api.github.com/repos/WISE-Community/WISE-Client | opened | refactor(UtilService): Move wordCount() to StudentDataService | Code Quality | This function is only used in StudentDataService. Move it there. Does it need to be a function, or can it be inline? | 1.0 | refactor(UtilService): Move wordCount() to StudentDataService - This function is only used in StudentDataService. Move it there. Does it need to be a function, or can it be inline? | non_test | refactor utilservice move wordcount to studentdataservice this function is only used in studentdataservice move it there does it need to be a function or can it be inline | 0 |
215,586 | 16,679,854,188 | IssuesEvent | 2021-06-07 21:30:08 | dbrownukk/EFD_v2 | https://api.github.com/repos/dbrownukk/EFD_v2 | closed | OHEA: Modeling - Unable to run Change Scenario for a particular Village | For Testing bug | Instance: Testing
App: OHEA Modelling
Change Scenario: Modelling Extensions Test
LZ: Katakwi - Fishing & Livestock Zone
Village: Ku
1. In Livelihhods Modelling module, select this change Scenario
2. Click Report menu bar button
3. Select village 'Ku'
4. Click Run
> ERROR Impossible to execute Run action: null
I have inspected the Community record and the others in the LZ (which all run fine), but i can't spot the faulty data - and i guess that's what it is. | 1.0 | OHEA: Modeling - Unable to run Change Scenario for a particular Village - Instance: Testing
App: OHEA Modelling
Change Scenario: Modelling Extensions Test
LZ: Katakwi - Fishing & Livestock Zone
Village: Ku
1. In Livelihhods Modelling module, select this change Scenario
2. Click Report menu bar button
3. Select village 'Ku'
4. Click Run
> ERROR Impossible to execute Run action: null
I have inspected the Community record and the others in the LZ (which all run fine), but i can't spot the faulty data - and i guess that's what it is. | test | ohea modeling unable to run change scenario for a particular village instance testing app ohea modelling change scenario modelling extensions test lz katakwi fishing livestock zone village ku in livelihhods modelling module select this change scenario click report menu bar button select village ku click run error impossible to execute run action null i have inspected the community record and the others in the lz which all run fine but i can t spot the faulty data and i guess that s what it is | 1 |
326,372 | 24,081,296,675 | IssuesEvent | 2022-09-19 06:52:58 | lisphilar/covid19-sir | https://api.github.com/repos/lisphilar/covid19-sir | closed | [Docs] fix terms in glossary list: trend analysis -> change point analysis | documentation | ## What we need to document?
Terms will be replaced.
- trend analysis -> change point analysis | 1.0 | [Docs] fix terms in glossary list: trend analysis -> change point analysis - ## What we need to document?
Terms will be replaced.
- trend analysis -> change point analysis | non_test | fix terms in glossary list trend analysis change point analysis what we need to document terms will be replaced trend analysis change point analysis | 0 |
317,019 | 23,660,470,097 | IssuesEvent | 2022-08-26 15:06:12 | Pradumnasaraf/LinkFree-CLI | https://api.github.com/repos/Pradumnasaraf/LinkFree-CLI | closed | [Bug + Docs] add note, that cli tool is only usable in the Linkfree repo / folder + Final prompt message | documentation | ### Description
it should be clear that the CLI shlould only be ran in a forked linkfree folder.
Further the `wohooo`-messages imo is displayed to early and not shown if such an error is thrown. (https://github.com/Pradumnasaraf/LinkFree-CLI/blob/main/src/index.js#L45)
### Screenshots
| 1.0 | [Bug + Docs] add note, that cli tool is only usable in the Linkfree repo / folder + Final prompt message - ### Description
it should be clear that the CLI shlould only be ran in a forked linkfree folder.
Further the `wohooo`-messages imo is displayed to early and not shown if such an error is thrown. (https://github.com/Pradumnasaraf/LinkFree-CLI/blob/main/src/index.js#L45)
### Screenshots
| non_test | add note that cli tool is only usable in the linkfree repo folder final prompt message description it should be clear that the cli shlould only be ran in a forked linkfree folder further the wohooo messages imo is displayed to early and not shown if such an error is thrown screenshots | 0 |
27,567 | 12,651,366,408 | IssuesEvent | 2020-06-17 00:05:32 | pascalopitz/unoffical-sonos-controller-for-linux | https://api.github.com/repos/pascalopitz/unoffical-sonos-controller-for-linux | closed | plex integration | music services | Running Ubuntu 16.04 with Gnome
Unofficial Sonos Controller version 0.1.2
I connected my plex account successfully to the client, but once I select the plex music service, I get an empty list. When I look into the developer console, it generates the following error:
```
TypeError: Cannot create property 'serviceClient' on string 'PMS|:PMS/7c62c345691ea62fefd87f491dc5d21b:NONE#cw0v'
at state.items._lodash2.default.map.i (BrowserListActions.js:373)
at /opt/sonos-controller-unofficial/resources/app.asar/node_modules/lodash/lodash.js:3554
at /opt/sonos-controller-unofficial/resources/app.asar/node_modules/lodash/lodash.js:4944
at baseForOwn (/opt/sonos-controller-unofficial/resources/app.asar/node_modules/lodash/lodash.js:3001)
at /opt/sonos-controller-unofficial/resources/app.asar/node_modules/lodash/lodash.js:4913
at baseMap (/opt/sonos-controller-unofficial/resources/app.asar/node_modules/lodash/lodash.js:3553)
at Function.map (/opt/sonos-controller-unofficial/resources/app.asar/node_modules/lodash/lodash.js:9571)
at exports.select (BrowserListActions.js:372)
at <anonymous>
action.payload.action.payload.catch.err @ index.js:30
``` | 1.0 | plex integration - Running Ubuntu 16.04 with Gnome
Unofficial Sonos Controller version 0.1.2
I connected my plex account successfully to the client, but once I select the plex music service, I get an empty list. When I look into the developer console, it generates the following error:
```
TypeError: Cannot create property 'serviceClient' on string 'PMS|:PMS/7c62c345691ea62fefd87f491dc5d21b:NONE#cw0v'
at state.items._lodash2.default.map.i (BrowserListActions.js:373)
at /opt/sonos-controller-unofficial/resources/app.asar/node_modules/lodash/lodash.js:3554
at /opt/sonos-controller-unofficial/resources/app.asar/node_modules/lodash/lodash.js:4944
at baseForOwn (/opt/sonos-controller-unofficial/resources/app.asar/node_modules/lodash/lodash.js:3001)
at /opt/sonos-controller-unofficial/resources/app.asar/node_modules/lodash/lodash.js:4913
at baseMap (/opt/sonos-controller-unofficial/resources/app.asar/node_modules/lodash/lodash.js:3553)
at Function.map (/opt/sonos-controller-unofficial/resources/app.asar/node_modules/lodash/lodash.js:9571)
at exports.select (BrowserListActions.js:372)
at <anonymous>
action.payload.action.payload.catch.err @ index.js:30
``` | non_test | plex integration running ubuntu with gnome unofficial sonos controller version i connected my plex account successfully to the client but once i select the plex music service i get an empty list when i look into the developer console it generates the following error typeerror cannot create property serviceclient on string pms pms none at state items default map i browserlistactions js at opt sonos controller unofficial resources app asar node modules lodash lodash js at opt sonos controller unofficial resources app asar node modules lodash lodash js at baseforown opt sonos controller unofficial resources app asar node modules lodash lodash js at opt sonos controller unofficial resources app asar node modules lodash lodash js at basemap opt sonos controller unofficial resources app asar node modules lodash lodash js at function map opt sonos controller unofficial resources app asar node modules lodash lodash js at exports select browserlistactions js at action payload action payload catch err index js | 0 |
103,183 | 8,882,571,345 | IssuesEvent | 2019-01-14 13:36:32 | linkedpipes/etl | https://api.github.com/repos/linkedpipes/etl | closed | Add "Skip on Error" to t-tabular | enhancement test | t-tabular currently fails on first bad input file. For cases where we have a bunch of files, some of them not even CSVs, we need an option to skip them. | 1.0 | Add "Skip on Error" to t-tabular - t-tabular currently fails on first bad input file. For cases where we have a bunch of files, some of them not even CSVs, we need an option to skip them. | test | add skip on error to t tabular t tabular currently fails on first bad input file for cases where we have a bunch of files some of them not even csvs we need an option to skip them | 1 |
350,843 | 31,932,491,384 | IssuesEvent | 2023-09-19 08:22:48 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | reopened | Fix general.test_gather | Sub Task Failing Test | | | |
|---|---|
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/6158828384"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/6158828384"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/6158828384"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/6158828384"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/6158828384"><img src=https://img.shields.io/badge/-failure-red></a>
| 1.0 | Fix general.test_gather - | | |
|---|---|
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/6158828384"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/6158828384"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/6158828384"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/6158828384"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/6158828384"><img src=https://img.shields.io/badge/-failure-red></a>
| test | fix general test gather jax a href src numpy a href src torch a href src tensorflow a href src paddle a href src | 1 |
157,490 | 19,957,437,508 | IssuesEvent | 2022-01-28 02:04:25 | GeertHauwaerts/exabgp-voipbl | https://api.github.com/repos/GeertHauwaerts/exabgp-voipbl | opened | CVE-2020-11023 (Medium) detected in multiple libraries | security vulnerability | ## CVE-2020-11023 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>phpunit/php-code-coverage-7.0.14</b>, <b>jquery-1.11.0.min.js</b>, <b>jquery-3.4.1.min.js</b>, <b>jquery-1.7.1.min.js</b></p></summary>
<p>
<details><summary><b>phpunit/php-code-coverage-7.0.14</b></p></summary>
<p>Library that provides collection, processing, and rendering functionality for PHP code coverage information.</p>
<p>Library home page: <a href="https://api.github.com/repos/sebastianbergmann/php-code-coverage/zipball/bb7c9a210c72e4709cdde67f8b7362f672f2225c">https://api.github.com/repos/sebastianbergmann/php-code-coverage/zipball/bb7c9a210c72e4709cdde67f8b7362f672f2225c</a></p>
<p>
Dependency Hierarchy:
</details>
<details><summary><b>jquery-1.11.0.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.11.0/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.11.0/jquery.min.js</a></p>
<p>Path to vulnerable library: /exabgp-voipbl/vendor/phpdocumentor/phpdocumentor/data/templates/clean/js/jquery-1.11.0.min.js</p>
<p>
Dependency Hierarchy:
</details>
<details><summary><b>jquery-3.4.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.4.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/3.4.1/jquery.min.js</a></p>
<p>Path to vulnerable library: /exabgp-voipbl/vendor/phpunit/php-code-coverage/src/Report/Html/Renderer/Template/js/jquery.min.js</p>
<p>
Dependency Hierarchy:
</details>
<details><summary><b>jquery-1.7.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.1/jquery.min.js</a></p>
<p>Path to dependency file: /vendor/phpdocumentor/phpdocumentor/data/templates/responsive/graph.html</p>
<p>Path to vulnerable library: /exabgp-voipbl/vendor/phpdocumentor/phpdocumentor/data/templates/responsive/graph.html</p>
<p>
Dependency Hierarchy:
</details>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
<p>Publish Date: 2020-04-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11023>CVE-2020-11023</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/jquery/jquery/security/advisories/GHSA-jpcq-cgw6-v4j6,https://github.com/rails/jquery-rails/blob/master/CHANGELOG.md#440">https://github.com/jquery/jquery/security/advisories/GHSA-jpcq-cgw6-v4j6,https://github.com/rails/jquery-rails/blob/master/CHANGELOG.md#440</a></p>
<p>Release Date: 2020-04-29</p>
<p>Fix Resolution: jquery - 3.5.0;jquery-rails - 4.4.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-11023 (Medium) detected in multiple libraries - ## CVE-2020-11023 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>phpunit/php-code-coverage-7.0.14</b>, <b>jquery-1.11.0.min.js</b>, <b>jquery-3.4.1.min.js</b>, <b>jquery-1.7.1.min.js</b></p></summary>
<p>
<details><summary><b>phpunit/php-code-coverage-7.0.14</b></p></summary>
<p>Library that provides collection, processing, and rendering functionality for PHP code coverage information.</p>
<p>Library home page: <a href="https://api.github.com/repos/sebastianbergmann/php-code-coverage/zipball/bb7c9a210c72e4709cdde67f8b7362f672f2225c">https://api.github.com/repos/sebastianbergmann/php-code-coverage/zipball/bb7c9a210c72e4709cdde67f8b7362f672f2225c</a></p>
<p>
Dependency Hierarchy:
</details>
<details><summary><b>jquery-1.11.0.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.11.0/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.11.0/jquery.min.js</a></p>
<p>Path to vulnerable library: /exabgp-voipbl/vendor/phpdocumentor/phpdocumentor/data/templates/clean/js/jquery-1.11.0.min.js</p>
<p>
Dependency Hierarchy:
</details>
<details><summary><b>jquery-3.4.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.4.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/3.4.1/jquery.min.js</a></p>
<p>Path to vulnerable library: /exabgp-voipbl/vendor/phpunit/php-code-coverage/src/Report/Html/Renderer/Template/js/jquery.min.js</p>
<p>
Dependency Hierarchy:
</details>
<details><summary><b>jquery-1.7.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.1/jquery.min.js</a></p>
<p>Path to dependency file: /vendor/phpdocumentor/phpdocumentor/data/templates/responsive/graph.html</p>
<p>Path to vulnerable library: /exabgp-voipbl/vendor/phpdocumentor/phpdocumentor/data/templates/responsive/graph.html</p>
<p>
Dependency Hierarchy:
</details>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
<p>Publish Date: 2020-04-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11023>CVE-2020-11023</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/jquery/jquery/security/advisories/GHSA-jpcq-cgw6-v4j6,https://github.com/rails/jquery-rails/blob/master/CHANGELOG.md#440">https://github.com/jquery/jquery/security/advisories/GHSA-jpcq-cgw6-v4j6,https://github.com/rails/jquery-rails/blob/master/CHANGELOG.md#440</a></p>
<p>Release Date: 2020-04-29</p>
<p>Fix Resolution: jquery - 3.5.0;jquery-rails - 4.4.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_test | cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries phpunit php code coverage jquery min js jquery min js jquery min js phpunit php code coverage library that provides collection processing and rendering functionality for php code coverage information library home page a href dependency hierarchy jquery min js javascript library for dom operations library home page a href path to vulnerable library exabgp voipbl vendor phpdocumentor phpdocumentor data templates clean js jquery min js dependency hierarchy jquery min js javascript library for dom operations library home page a href path to vulnerable library exabgp voipbl vendor phpunit php code coverage src report html renderer template js jquery min js dependency hierarchy jquery min js javascript library for dom operations library home page a href path to dependency file vendor phpdocumentor phpdocumentor data templates responsive graph html path to vulnerable library exabgp voipbl vendor phpdocumentor phpdocumentor data templates responsive graph html dependency hierarchy found in base branch master vulnerability details in jquery versions greater than or equal to and before passing html containing elements from untrusted sources even after sanitizing it to one of jquery s dom manipulation methods i e html append and others may execute untrusted code this problem is patched in jquery publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jquery jquery rails step up your open source security game with whitesource | 0 |
265,524 | 23,174,557,397 | IssuesEvent | 2022-07-31 08:08:41 | jhipster/jhipster-lite | https://api.github.com/repos/jhipster/jhipster-lite | closed | Rename cucumber modules | server: spring boot area: refactoring theme: tests | here the different names:
- cucumber-jwt-authentication
- cucumber-oauth2-authentication
- springboot-cucumber
The names should be consistent, maybe:
- cucumber-jwt-authentication -> springboot-cucumber-jwt-authentication
- cucumber-oauth2-authentication -> springboot-cucumber-oauth2-authentication
What do you think, @DamnClin ? | 1.0 | Rename cucumber modules - here the different names:
- cucumber-jwt-authentication
- cucumber-oauth2-authentication
- springboot-cucumber
The names should be consistent, maybe:
- cucumber-jwt-authentication -> springboot-cucumber-jwt-authentication
- cucumber-oauth2-authentication -> springboot-cucumber-oauth2-authentication
What do you think, @DamnClin ? | test | rename cucumber modules here the different names cucumber jwt authentication cucumber authentication springboot cucumber the names should be consistent maybe cucumber jwt authentication springboot cucumber jwt authentication cucumber authentication springboot cucumber authentication what do you think damnclin | 1 |
20,273 | 3,800,850,756 | IssuesEvent | 2016-03-23 20:36:04 | TerraME/terrame | https://api.github.com/repos/TerraME/terrame | closed | UnitTest:assertFile with a log directory | enhancement Test | Currently, `UnitTest:assertFile` only checks if the file exists and then remove it. Allow packages to have a log directory where signatures for such files could be stored in the same way of `assertSnapshot`, with the difference that `assertFile` should accept only an exact copy of the log file. | 1.0 | UnitTest:assertFile with a log directory - Currently, `UnitTest:assertFile` only checks if the file exists and then remove it. Allow packages to have a log directory where signatures for such files could be stored in the same way of `assertSnapshot`, with the difference that `assertFile` should accept only an exact copy of the log file. | test | unittest assertfile with a log directory currently unittest assertfile only checks if the file exists and then remove it allow packages to have a log directory where signatures for such files could be stored in the same way of assertsnapshot with the difference that assertfile should accept only an exact copy of the log file | 1 |
571,702 | 17,023,349,137 | IssuesEvent | 2021-07-03 01:33:46 | tomhughes/trac-tickets | https://api.github.com/repos/tomhughes/trac-tickets | closed | Public Libraries should show in Mapnik | Component: mapnik Priority: minor Resolution: fixed Type: enhancement | **[Submitted to the original trac issue database at 10.53pm, Tuesday, 13th January 2009]**
Libraries (specifically a node with amenity=library) show on osmarender but not mapnik.
Examples:
Forbes Library is the public library of Northampton, MA, USA:
http://openstreetmap.org/?lat=42.31708&lon=-72.63611&zoom=17&layers=B000FTFT
There are many libraries here (Boston, MA, USA): http://openstreetmap.org/?lat=42.33889&lon=-71.09373&zoom=17&layers=0B00FTF
The Reed Free Library in Surry, NH, USA even has the ref parameter set: http://openstreetmap.org/?lat=43.01949&lon=-72.32138&zoom=17&layers=0B00FTFT | 1.0 | Public Libraries should show in Mapnik - **[Submitted to the original trac issue database at 10.53pm, Tuesday, 13th January 2009]**
Libraries (specifically a node with amenity=library) show on osmarender but not mapnik.
Examples:
Forbes Library is the public library of Northampton, MA, USA:
http://openstreetmap.org/?lat=42.31708&lon=-72.63611&zoom=17&layers=B000FTFT
There are many libraries here (Boston, MA, USA): http://openstreetmap.org/?lat=42.33889&lon=-71.09373&zoom=17&layers=0B00FTF
The Reed Free Library in Surry, NH, USA even has the ref parameter set: http://openstreetmap.org/?lat=43.01949&lon=-72.32138&zoom=17&layers=0B00FTFT | non_test | public libraries should show in mapnik libraries specifically a node with amenity library show on osmarender but not mapnik examples forbes library is the public library of northampton ma usa there are many libraries here boston ma usa the reed free library in surry nh usa even has the ref parameter set | 0 |
302,439 | 26,144,174,698 | IssuesEvent | 2022-12-30 00:20:54 | longhorn/longhorn | https://api.github.com/repos/longhorn/longhorn | opened | [TEST] Create a testing guidance for feature testing | kind/test priority/0 | ## What's the test to develop? Please describe
Usually, QA will rely on the test cases provided by engineering to do the feature testing or bug regression testing. However, it's the potential to ignore unhappy paths.
We should provide a non-programming framework or guidance to let QA members follow up on how to test a new feature or regression bug, not only rely on the test cases provided by engineering but also base on them and cover possible unhappy paths, especially involuntary factors/events like network partition, node reboot, node deletion, kubelet restart, etc. The framework and guidance can be like a cheat sheet.
## Describe the items of the test development (DoD, definition of done) you'd like
- [ ] Create a cheat sheet/framework/guidance doc for QA to guide them on how to test a feature or bug regression.
## Additional context
cc @longhorn/qa
| 1.0 | [TEST] Create a testing guidance for feature testing - ## What's the test to develop? Please describe
Usually, QA will rely on the test cases provided by engineering to do the feature testing or bug regression testing. However, it's the potential to ignore unhappy paths.
We should provide a non-programming framework or guidance to let QA members follow up on how to test a new feature or regression bug, not only rely on the test cases provided by engineering but also base on them and cover possible unhappy paths, especially involuntary factors/events like network partition, node reboot, node deletion, kubelet restart, etc. The framework and guidance can be like a cheat sheet.
## Describe the items of the test development (DoD, definition of done) you'd like
- [ ] Create a cheat sheet/framework/guidance doc for QA to guide them on how to test a feature or bug regression.
## Additional context
cc @longhorn/qa
| test | create a testing guidance for feature testing what s the test to develop please describe usually qa will rely on the test cases provided by engineering to do the feature testing or bug regression testing however it s the potential to ignore unhappy paths we should provide a non programming framework or guidance to let qa members follow up on how to test a new feature or regression bug not only rely on the test cases provided by engineering but also base on them and cover possible unhappy paths especially involuntary factors events like network partition node reboot node deletion kubelet restart etc the framework and guidance can be like a cheat sheet describe the items of the test development dod definition of done you d like create a cheat sheet framework guidance doc for qa to guide them on how to test a feature or bug regression additional context cc longhorn qa | 1 |
11,628 | 9,424,524,793 | IssuesEvent | 2019-04-11 14:16:48 | Microsoft/vscode-cpptools | https://api.github.com/repos/Microsoft/vscode-cpptools | closed | Template Variable Specialization Error: "variable xx has already been initialized" | Language Service Visual Studio bug fixed (release pending) | **Type: LanguageService**
<!----- Input information below ----->
<!--
**Please review existing issues and our documentation at https://github.com/Microsoft/vscode-cpptools/tree/master/Documentation prior to filing an issue.**
-->
**Describe the bug**
- OS and Version: macOS 10.14.12
- VS Code Version: 1.30.2
- C/C++ Extension Version: 0.21.0
- Other extensions you installed (and if the issue persists after disabling them):
* C#
* C# XML Documentation
* CMake
* Debugger for Unity
* LaTeX Workshop
* One Dark Pro
* Pola Code
* Verilog HDL/SystemVerilog
* vscode-icons
* x86 and x86_64 Assembly
- A clear and concise description of what the bug is.
In the json parser that I am working on, I am using template variables as a part of my parser so that my parser would work with all types of `char`s in C++. The file that's causing the problem looks like the following snippet, but with a lot more template variables.
```cpp
template<typename CharT>
inline constexpr CharT beginObject{};
template<>
inline constexpr char beginObject<char>{ '{' };
```
The clang++ compiler that I have on my mac (Apple LLVM version 10.0.0 (clang-1000.11.45.5)) compiles the code just fine, but vs code produces the following error:
```
variable "beginObject [with CharT=char]" has already been initialized
```
**To Reproduce**
<!-- Steps to reproduce the behavior: -->
<!-- *The most actionable issue reports include a code sample including configuration files such as c_cpp_properties.json* -->
0. Set `settings.json` as follows
```json
{
"C_Cpp.default.cppStandard": "c++17"
}
```
1. Create a main.cpp file;
2. Copy and paste the following into the main file
```cpp
// #include "gtest/gtest.h"
#include <iostream>
template<typename CharT>
CharT letter{};
template<>
char letter<char>{ 'a' };
int main(int argc, char **argv)
{
std::cout << letter<char> << std::endl;
// testing::InitGoogleTest(&argc, argv);
// return RUN_ALL_TESTS();
return 0;
}
```
3. After the red flame goes off, the error should occur;
4. To compile, use the following compiler flags (clang)
```
-std=c++17
```
(The actual project file that's causing the error looks very similar to this, but with a lot more template variables used in the json parser and does not have the main function. I am happy to provide the source code if needed.)
**Expected behavior**
<!-- A clear and concise description of what you expected to happen. -->
There should be no errors from the plugin, as the compiler compiles the code just fine.
**Screenshots**
<!-- If applicable, add screenshots to help explain your problem. -->
<img width="381" alt="screen shot 2019-01-29 at 00 31 59" src="https://user-images.githubusercontent.com/31496190/51888871-58304580-235d-11e9-934f-b727aee33cf9.png">
<img width="552" alt="screen shot 2019-01-29 at 00 32 50" src="https://user-images.githubusercontent.com/31496190/51888901-7302ba00-235d-11e9-9582-750cff8be6d3.png">
**Additional context**
<!--
* Call Stacks: For bugs like crashes, deadlocks, infinite loops, etc. that we are not able to repro and for which the call stack may be useful, please attach a debugger and/or create a dmp and provide the call stacks. Windows binaries have symbols available in VS Code by setting your "symbolSearchPath" to "https://msdl.microsoft.com/download/symbols".
* Add any other context about the problem here including log messages in your Output window ("C_Cpp.loggingLevel": "Debug" in settings.json).
--> | 1.0 | Template Variable Specialization Error: "variable xx has already been initialized" - **Type: LanguageService**
<!----- Input information below ----->
<!--
**Please review existing issues and our documentation at https://github.com/Microsoft/vscode-cpptools/tree/master/Documentation prior to filing an issue.**
-->
**Describe the bug**
- OS and Version: macOS 10.14.12
- VS Code Version: 1.30.2
- C/C++ Extension Version: 0.21.0
- Other extensions you installed (and if the issue persists after disabling them):
* C#
* C# XML Documentation
* CMake
* Debugger for Unity
* LaTeX Workshop
* One Dark Pro
* Pola Code
* Verilog HDL/SystemVerilog
* vscode-icons
* x86 and x86_64 Assembly
- A clear and concise description of what the bug is.
In the json parser that I am working on, I am using template variables as a part of my parser so that my parser would work with all types of `char`s in C++. The file that's causing the problem looks like the following snippet, but with a lot more template variables.
```cpp
template<typename CharT>
inline constexpr CharT beginObject{};
template<>
inline constexpr char beginObject<char>{ '{' };
```
The clang++ compiler that I have on my mac (Apple LLVM version 10.0.0 (clang-1000.11.45.5)) compiles the code just fine, but vs code produces the following error:
```
variable "beginObject [with CharT=char]" has already been initialized
```
**To Reproduce**
<!-- Steps to reproduce the behavior: -->
<!-- *The most actionable issue reports include a code sample including configuration files such as c_cpp_properties.json* -->
0. Set `settings.json` as follows
```json
{
"C_Cpp.default.cppStandard": "c++17"
}
```
1. Create a main.cpp file;
2. Copy and paste the following into the main file
```cpp
// #include "gtest/gtest.h"
#include <iostream>
template<typename CharT>
CharT letter{};
template<>
char letter<char>{ 'a' };
int main(int argc, char **argv)
{
std::cout << letter<char> << std::endl;
// testing::InitGoogleTest(&argc, argv);
// return RUN_ALL_TESTS();
return 0;
}
```
3. After the red flame goes off, the error should occur;
4. To compile, use the following compiler flags (clang)
```
-std=c++17
```
(The actual project file that's causing the error looks very similar to this, but with a lot more template variables used in the json parser and does not have the main function. I am happy to provide the source code if needed.)
**Expected behavior**
<!-- A clear and concise description of what you expected to happen. -->
There should be no errors from the plugin, as the compiler compiles the code just fine.
**Screenshots**
<!-- If applicable, add screenshots to help explain your problem. -->
<img width="381" alt="screen shot 2019-01-29 at 00 31 59" src="https://user-images.githubusercontent.com/31496190/51888871-58304580-235d-11e9-934f-b727aee33cf9.png">
<img width="552" alt="screen shot 2019-01-29 at 00 32 50" src="https://user-images.githubusercontent.com/31496190/51888901-7302ba00-235d-11e9-9582-750cff8be6d3.png">
**Additional context**
<!--
* Call Stacks: For bugs like crashes, deadlocks, infinite loops, etc. that we are not able to repro and for which the call stack may be useful, please attach a debugger and/or create a dmp and provide the call stacks. Windows binaries have symbols available in VS Code by setting your "symbolSearchPath" to "https://msdl.microsoft.com/download/symbols".
* Add any other context about the problem here including log messages in your Output window ("C_Cpp.loggingLevel": "Debug" in settings.json).
--> | non_test | template variable specialization error variable xx has already been initialized type languageservice please review existing issues and our documentation at prior to filing an issue describe the bug os and version macos vs code version c c extension version other extensions you installed and if the issue persists after disabling them c c xml documentation cmake debugger for unity latex workshop one dark pro pola code verilog hdl systemverilog vscode icons and assembly a clear and concise description of what the bug is in the json parser that i am working on i am using template variables as a part of my parser so that my parser would work with all types of char s in c the file that s causing the problem looks like the following snippet but with a lot more template variables cpp template inline constexpr chart beginobject template inline constexpr char beginobject the clang compiler that i have on my mac apple llvm version clang compiles the code just fine but vs code produces the following error variable beginobject has already been initialized to reproduce set settings json as follows json c cpp default cppstandard c create a main cpp file copy and paste the following into the main file cpp include gtest gtest h include template chart letter template char letter a int main int argc char argv std cout std endl testing initgoogletest argc argv return run all tests return after the red flame goes off the error should occur to compile use the following compiler flags clang std c the actual project file that s causing the error looks very similar to this but with a lot more template variables used in the json parser and does not have the main function i am happy to provide the source code if needed expected behavior there should be no errors from the plugin as the compiler compiles the code just fine screenshots img width alt screen shot at src img width alt screen shot at src additional context call stacks for bugs like crashes deadlocks infinite loops etc that we are not able to repro and for which the call stack may be useful please attach a debugger and or create a dmp and provide the call stacks windows binaries have symbols available in vs code by setting your symbolsearchpath to add any other context about the problem here including log messages in your output window c cpp logginglevel debug in settings json | 0 |
336,735 | 30,219,293,346 | IssuesEvent | 2023-07-05 18:00:41 | OpenLiberty/open-liberty | https://api.github.com/repos/OpenLiberty/open-liberty | closed | File default.log exists after ServerEnvTest runs. | test bug | The ServerEnvTest sets the LOG_FILE variable in server.env and changes the name of the log file. It attempts to rename that to console.log at the end of each test. The rename is failing because the server is still running at that point.
There are several other tests that are failing because console.log does not exist. I don't think ServerEnvTest is the cause of the other tests failing, because console.log should be created every time the server is started. But to remove any doubt, the ServerEnvTest can be modified to use another means of testing besides changing the log file name. | 1.0 | File default.log exists after ServerEnvTest runs. - The ServerEnvTest sets the LOG_FILE variable in server.env and changes the name of the log file. It attempts to rename that to console.log at the end of each test. The rename is failing because the server is still running at that point.
There are several other tests that are failing because console.log does not exist. I don't think ServerEnvTest is the cause of the other tests failing, because console.log should be created every time the server is started. But to remove any doubt, the ServerEnvTest can be modified to use another means of testing besides changing the log file name. | test | file default log exists after serverenvtest runs the serverenvtest sets the log file variable in server env and changes the name of the log file it attempts to rename that to console log at the end of each test the rename is failing because the server is still running at that point there are several other tests that are failing because console log does not exist i don t think serverenvtest is the cause of the other tests failing because console log should be created every time the server is started but to remove any doubt the serverenvtest can be modified to use another means of testing besides changing the log file name | 1 |
38,055 | 5,165,256,541 | IssuesEvent | 2017-01-17 13:11:54 | difi/move-integrasjonspunkt | https://api.github.com/repos/difi/move-integrasjonspunkt | closed | Logging av SOAP fault hvor Spring WS template brukes | enhancement test | Vi bruker Spring WS template mot arkivsystemene. Det er en quick win og få til samme feilhåndtering slik vi gjorde med PTV feilhåndtering/logging.
På denne måten får vi lettere feilsøkt dersom det skulle oppstå problemer mot arkivsystemet.
| 1.0 | Logging av SOAP fault hvor Spring WS template brukes - Vi bruker Spring WS template mot arkivsystemene. Det er en quick win og få til samme feilhåndtering slik vi gjorde med PTV feilhåndtering/logging.
På denne måten får vi lettere feilsøkt dersom det skulle oppstå problemer mot arkivsystemet.
| test | logging av soap fault hvor spring ws template brukes vi bruker spring ws template mot arkivsystemene det er en quick win og få til samme feilhåndtering slik vi gjorde med ptv feilhåndtering logging på denne måten får vi lettere feilsøkt dersom det skulle oppstå problemer mot arkivsystemet | 1 |
117,727 | 15,168,698,975 | IssuesEvent | 2021-02-12 19:51:03 | mozilla/foundation.mozilla.org | https://api.github.com/repos/mozilla/foundation.mozilla.org | closed | [Google Analytics] V-day dashboard | design | **Background:**
PNI V-Day is coming up! Let's do a GA dashboard session with Lindsay and Audrey so we can create a dashboard together with the metrics they think are the most relevant.
**To do:**
- [x] Consult them to ask if they would like to do a dashboard-building session together
- [x] Create a doc to ask for their input on the most relevant metrics for V-day in terms of Analytics
- [x] Do some thinking and create the "skeleton" so the session goes smoothly
- [x] Schedule the workshop
- [x] Do the workshop. From it, a nice dashboard should emerge
- [x] Do any final tweaks
- [x] Ship it | 1.0 | [Google Analytics] V-day dashboard - **Background:**
PNI V-Day is coming up! Let's do a GA dashboard session with Lindsay and Audrey so we can create a dashboard together with the metrics they think are the most relevant.
**To do:**
- [x] Consult them to ask if they would like to do a dashboard-building session together
- [x] Create a doc to ask for their input on the most relevant metrics for V-day in terms of Analytics
- [x] Do some thinking and create the "skeleton" so the session goes smoothly
- [x] Schedule the workshop
- [x] Do the workshop. From it, a nice dashboard should emerge
- [x] Do any final tweaks
- [x] Ship it | non_test | v day dashboard background pni v day is coming up let s do a ga dashboard session with lindsay and audrey so we can create a dashboard together with the metrics they think are the most relevant to do consult them to ask if they would like to do a dashboard building session together create a doc to ask for their input on the most relevant metrics for v day in terms of analytics do some thinking and create the skeleton so the session goes smoothly schedule the workshop do the workshop from it a nice dashboard should emerge do any final tweaks ship it | 0 |
118,932 | 17,602,827,592 | IssuesEvent | 2021-08-17 13:49:30 | harrinry/nifi | https://api.github.com/repos/harrinry/nifi | opened | CVE-2018-15756 (High) detected in spring-web-4.3.19.RELEASE.jar | security vulnerability | ## CVE-2018-15756 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-web-4.3.19.RELEASE.jar</b></p></summary>
<p>Spring Web</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to vulnerable library: nifi-nar-bundles/nifi-framework-bundle/nifi-framework-nar/target/classes/META-INF/bundled-dependencies/spring-web-4.3.19.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- :x: **spring-web-4.3.19.RELEASE.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/harrinry/nifi/commit/0484b1d281ed1df9c5682361286dee2ca6c634fe">0484b1d281ed1df9c5682361286dee2ca6c634fe</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>
Spring Framework, version 5.1, versions 5.0.x prior to 5.0.10, versions 4.3.x prior to 4.3.20, and older unsupported versions on the 4.2.x branch provide support for range requests when serving static resources through the ResourceHttpRequestHandler, or starting in 5.0 when an annotated controller returns an org.springframework.core.io.Resource. A malicious user (or attacker) can add a range header with a high number of ranges, or with wide ranges that overlap, or both, for a denial of service attack. This vulnerability affects applications that depend on either spring-webmvc or spring-webflux. Such applications must also have a registration for serving static resources (e.g. JS, CSS, images, and others), or have an annotated controller that returns an org.springframework.core.io.Resource. Spring Boot applications that depend on spring-boot-starter-web or spring-boot-starter-webflux are ready to serve static resources out of the box and are therefore vulnerable.
<p>Publish Date: 2018-10-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-15756>CVE-2018-15756</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://pivotal.io/security/cve-2018-15756">https://pivotal.io/security/cve-2018-15756</a></p>
<p>Release Date: 2018-10-18</p>
<p>Fix Resolution: 4.3.20,5.0.10,5.1.1</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.springframework","packageName":"spring-web","packageVersion":"4.3.19.RELEASE","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"org.springframework:spring-web:4.3.19.RELEASE","isMinimumFixVersionAvailable":true,"minimumFixVersion":"4.3.20,5.0.10,5.1.1"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-15756","vulnerabilityDetails":"Spring Framework, version 5.1, versions 5.0.x prior to 5.0.10, versions 4.3.x prior to 4.3.20, and older unsupported versions on the 4.2.x branch provide support for range requests when serving static resources through the ResourceHttpRequestHandler, or starting in 5.0 when an annotated controller returns an org.springframework.core.io.Resource. A malicious user (or attacker) can add a range header with a high number of ranges, or with wide ranges that overlap, or both, for a denial of service attack. This vulnerability affects applications that depend on either spring-webmvc or spring-webflux. Such applications must also have a registration for serving static resources (e.g. JS, CSS, images, and others), or have an annotated controller that returns an org.springframework.core.io.Resource. Spring Boot applications that depend on spring-boot-starter-web or spring-boot-starter-webflux are ready to serve static resources out of the box and are therefore vulnerable.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-15756","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-2018-15756 (High) detected in spring-web-4.3.19.RELEASE.jar - ## CVE-2018-15756 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-web-4.3.19.RELEASE.jar</b></p></summary>
<p>Spring Web</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to vulnerable library: nifi-nar-bundles/nifi-framework-bundle/nifi-framework-nar/target/classes/META-INF/bundled-dependencies/spring-web-4.3.19.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- :x: **spring-web-4.3.19.RELEASE.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/harrinry/nifi/commit/0484b1d281ed1df9c5682361286dee2ca6c634fe">0484b1d281ed1df9c5682361286dee2ca6c634fe</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>
Spring Framework, version 5.1, versions 5.0.x prior to 5.0.10, versions 4.3.x prior to 4.3.20, and older unsupported versions on the 4.2.x branch provide support for range requests when serving static resources through the ResourceHttpRequestHandler, or starting in 5.0 when an annotated controller returns an org.springframework.core.io.Resource. A malicious user (or attacker) can add a range header with a high number of ranges, or with wide ranges that overlap, or both, for a denial of service attack. This vulnerability affects applications that depend on either spring-webmvc or spring-webflux. Such applications must also have a registration for serving static resources (e.g. JS, CSS, images, and others), or have an annotated controller that returns an org.springframework.core.io.Resource. Spring Boot applications that depend on spring-boot-starter-web or spring-boot-starter-webflux are ready to serve static resources out of the box and are therefore vulnerable.
<p>Publish Date: 2018-10-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-15756>CVE-2018-15756</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://pivotal.io/security/cve-2018-15756">https://pivotal.io/security/cve-2018-15756</a></p>
<p>Release Date: 2018-10-18</p>
<p>Fix Resolution: 4.3.20,5.0.10,5.1.1</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.springframework","packageName":"spring-web","packageVersion":"4.3.19.RELEASE","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"org.springframework:spring-web:4.3.19.RELEASE","isMinimumFixVersionAvailable":true,"minimumFixVersion":"4.3.20,5.0.10,5.1.1"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-15756","vulnerabilityDetails":"Spring Framework, version 5.1, versions 5.0.x prior to 5.0.10, versions 4.3.x prior to 4.3.20, and older unsupported versions on the 4.2.x branch provide support for range requests when serving static resources through the ResourceHttpRequestHandler, or starting in 5.0 when an annotated controller returns an org.springframework.core.io.Resource. A malicious user (or attacker) can add a range header with a high number of ranges, or with wide ranges that overlap, or both, for a denial of service attack. This vulnerability affects applications that depend on either spring-webmvc or spring-webflux. Such applications must also have a registration for serving static resources (e.g. JS, CSS, images, and others), or have an annotated controller that returns an org.springframework.core.io.Resource. Spring Boot applications that depend on spring-boot-starter-web or spring-boot-starter-webflux are ready to serve static resources out of the box and are therefore vulnerable.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-15756","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_test | cve high detected in spring web release jar cve high severity vulnerability vulnerable library spring web release jar spring web library home page a href path to vulnerable library nifi nar bundles nifi framework bundle nifi framework nar target classes meta inf bundled dependencies spring web release jar dependency hierarchy x spring web release jar vulnerable library found in head commit a href found in base branch master vulnerability details spring framework version versions x prior to versions x prior to and older unsupported versions on the x branch provide support for range requests when serving static resources through the resourcehttprequesthandler or starting in when an annotated controller returns an org springframework core io resource a malicious user or attacker can add a range header with a high number of ranges or with wide ranges that overlap or both for a denial of service attack this vulnerability affects applications that depend on either spring webmvc or spring webflux such applications must also have a registration for serving static resources e g js css images and others or have an annotated controller that returns an org springframework core io resource spring boot applications that depend on spring boot starter web or spring boot starter webflux are ready to serve static resources out of the box and are therefore vulnerable publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact 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 check this box to open an automated fix pr isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree org springframework spring web release isminimumfixversionavailable true minimumfixversion basebranches vulnerabilityidentifier cve vulnerabilitydetails spring framework version versions x prior to versions x prior to and older unsupported versions on the x branch provide support for range requests when serving static resources through the resourcehttprequesthandler or starting in when an annotated controller returns an org springframework core io resource a malicious user or attacker can add a range header with a high number of ranges or with wide ranges that overlap or both for a denial of service attack this vulnerability affects applications that depend on either spring webmvc or spring webflux such applications must also have a registration for serving static resources e g js css images and others or have an annotated controller that returns an org springframework core io resource spring boot applications that depend on spring boot starter web or spring boot starter webflux are ready to serve static resources out of the box and are therefore vulnerable vulnerabilityurl | 0 |
178,432 | 13,779,484,620 | IssuesEvent | 2020-10-08 13:49:18 | WordPress/twentytwentyone | https://api.github.com/repos/WordPress/twentytwentyone | closed | Test the updated list block | Needs testing [Component] Default blocks [Type] Task | **Describe the bug**
In comparison to WordPress 5.5, the list block in Gutenberg now has background and text color options.
The block needs to be tested with Gutenberg installed and with the themes color options.
We also need to check if any extra padding is needed when there is a background color.
| 1.0 | Test the updated list block - **Describe the bug**
In comparison to WordPress 5.5, the list block in Gutenberg now has background and text color options.
The block needs to be tested with Gutenberg installed and with the themes color options.
We also need to check if any extra padding is needed when there is a background color.
| test | test the updated list block describe the bug in comparison to wordpress the list block in gutenberg now has background and text color options the block needs to be tested with gutenberg installed and with the themes color options we also need to check if any extra padding is needed when there is a background color | 1 |
348,821 | 31,721,616,519 | IssuesEvent | 2023-09-10 13:24:42 | mozilla/pdf.js | https://api.github.com/repos/mozilla/pdf.js | opened | Fix integration test "Copy and paste all text must check that we've all the contents on copy/paste" | test | Introduction date: April 15, 2023
Introduction PR: https://github.com/mozilla/pdf.js/commit/ca54ea12b3d8fa2de690129dac3da6c2bf203dc2 (/cc @calixteman)
Type: intermittent (sometimes it works, indicating a possible timing/waiting issue)
OS: Windows
Logs: http://54.193.163.58:8877/248efa3bf526b9a/output.txt
Traceback:
```
Failures:
1) Copy and paste all text must check that we've all the contents on copy/paste
Message:
[31m In firefox: Expected false to equal true.[0m
Stack:
at <Jasmine>
at C:\pdfjs\botio-files-pdfjs\private\248efa3bf526b9a\test\integration\copy_paste_spec.js:54:59
at runNextTicks (node:internal/process/task_queues:60:5)
at process.processImmediate (node:internal/timers:447:9)
at async Promise.all (index 0)
Message:
[31m TypeError: Cannot read properties of null (reading 'includes')[0m
Stack:
at C:\pdfjs\botio-files-pdfjs\private\248efa3bf526b9a\test\integration\copy_paste_spec.js:55:23
at runNextTicks (node:internal/process/task_queues:60:5)
at process.processImmediate (node:internal/timers:447:9)
at async Promise.all (index 0)
at async UserContext.<anonymous> (C:\pdfjs\botio-files-pdfjs\private\248efa3bf526b9a\test\integration\copy_paste_spec.js:32:7)
```
Additional note: https://github.com/mozilla/pdf.js/blob/5f936380451c8d0076901d123a9cf200d62c9768/test/integration/copy_paste_spec.js#L131 contains two suites and tests with the exact same name, which makes it hard to disambiguate them and only worked here because of the line numbers in the traceback. The suites/tests should get a unique name. | 1.0 | Fix integration test "Copy and paste all text must check that we've all the contents on copy/paste" - Introduction date: April 15, 2023
Introduction PR: https://github.com/mozilla/pdf.js/commit/ca54ea12b3d8fa2de690129dac3da6c2bf203dc2 (/cc @calixteman)
Type: intermittent (sometimes it works, indicating a possible timing/waiting issue)
OS: Windows
Logs: http://54.193.163.58:8877/248efa3bf526b9a/output.txt
Traceback:
```
Failures:
1) Copy and paste all text must check that we've all the contents on copy/paste
Message:
[31m In firefox: Expected false to equal true.[0m
Stack:
at <Jasmine>
at C:\pdfjs\botio-files-pdfjs\private\248efa3bf526b9a\test\integration\copy_paste_spec.js:54:59
at runNextTicks (node:internal/process/task_queues:60:5)
at process.processImmediate (node:internal/timers:447:9)
at async Promise.all (index 0)
Message:
[31m TypeError: Cannot read properties of null (reading 'includes')[0m
Stack:
at C:\pdfjs\botio-files-pdfjs\private\248efa3bf526b9a\test\integration\copy_paste_spec.js:55:23
at runNextTicks (node:internal/process/task_queues:60:5)
at process.processImmediate (node:internal/timers:447:9)
at async Promise.all (index 0)
at async UserContext.<anonymous> (C:\pdfjs\botio-files-pdfjs\private\248efa3bf526b9a\test\integration\copy_paste_spec.js:32:7)
```
Additional note: https://github.com/mozilla/pdf.js/blob/5f936380451c8d0076901d123a9cf200d62c9768/test/integration/copy_paste_spec.js#L131 contains two suites and tests with the exact same name, which makes it hard to disambiguate them and only worked here because of the line numbers in the traceback. The suites/tests should get a unique name. | test | fix integration test copy and paste all text must check that we ve all the contents on copy paste introduction date april introduction pr cc calixteman type intermittent sometimes it works indicating a possible timing waiting issue os windows logs traceback failures copy and paste all text must check that we ve all the contents on copy paste message in firefox expected false to equal true stack at at c pdfjs botio files pdfjs private test integration copy paste spec js at runnextticks node internal process task queues at process processimmediate node internal timers at async promise all index message typeerror cannot read properties of null reading includes stack at c pdfjs botio files pdfjs private test integration copy paste spec js at runnextticks node internal process task queues at process processimmediate node internal timers at async promise all index at async usercontext c pdfjs botio files pdfjs private test integration copy paste spec js additional note contains two suites and tests with the exact same name which makes it hard to disambiguate them and only worked here because of the line numbers in the traceback the suites tests should get a unique name | 1 |
147,211 | 23,181,598,291 | IssuesEvent | 2022-08-01 03:06:57 | zuri-training/Team-118-Col-Films | https://api.github.com/repos/zuri-training/Team-118-Col-Films | opened | build the landing page wireframes | design | - build the landing pages for the project
- build the lo-fi
- build the hi-fi | 1.0 | build the landing page wireframes - - build the landing pages for the project
- build the lo-fi
- build the hi-fi | non_test | build the landing page wireframes build the landing pages for the project build the lo fi build the hi fi | 0 |
239,939 | 19,982,015,020 | IssuesEvent | 2022-01-30 02:59:43 | NickMazey/3D-Game-Physics-Engine-Alpha | https://api.github.com/repos/NickMazey/3D-Game-Physics-Engine-Alpha | closed | Make sure the tests pass in the action | testing | As the last part of this sprint, I need to make sure the tests all pass in the action on GitHub | 1.0 | Make sure the tests pass in the action - As the last part of this sprint, I need to make sure the tests all pass in the action on GitHub | test | make sure the tests pass in the action as the last part of this sprint i need to make sure the tests all pass in the action on github | 1 |
150,839 | 11,986,503,212 | IssuesEvent | 2020-04-07 19:26:20 | magento/magento2-phpstorm-plugin | https://api.github.com/repos/magento/magento2-phpstorm-plugin | closed | Tests. Add tests on PHP classes completion for the source_model attribute and tag | Award: advanced Award: test coverage Partner: Smile release-1.0.0 | **Preconditions (*)**
Tests should be added to the completion for the "source_model" XML tag and XML attribute of an XML file (system.xml for "source_model" XML tag and widget.xml for "source_model" XML attribute).
It is functional test coverage for the PR #91
**Expected result (*)**
Tests are written and works fine for "source_model" XML tag and XML attribute completion.
| 1.0 | Tests. Add tests on PHP classes completion for the source_model attribute and tag - **Preconditions (*)**
Tests should be added to the completion for the "source_model" XML tag and XML attribute of an XML file (system.xml for "source_model" XML tag and widget.xml for "source_model" XML attribute).
It is functional test coverage for the PR #91
**Expected result (*)**
Tests are written and works fine for "source_model" XML tag and XML attribute completion.
| test | tests add tests on php classes completion for the source model attribute and tag preconditions tests should be added to the completion for the source model xml tag and xml attribute of an xml file system xml for source model xml tag and widget xml for source model xml attribute it is functional test coverage for the pr expected result tests are written and works fine for source model xml tag and xml attribute completion | 1 |
216,685 | 16,665,484,985 | IssuesEvent | 2021-06-07 02:27:30 | stonier/ueye_cam | https://api.github.com/repos/stonier/ueye_cam | closed | README - Guidelines on how/when to use the IDS SDK | component:driver type:documentation | It's confusing for someone new. Key points:
* Don't need them if you're just building - this will fetch libraries and headers on-the-fly, but won't make them available in the runtime - licensing and you need more than these for the runtime anyway (need the daemon for camera discovery)
* Where to get the IDS SDK for the runtime
* You must have these on the same subnet as the node
* First steps with the IDS SDK tools for configuring the cameras | 1.0 | README - Guidelines on how/when to use the IDS SDK - It's confusing for someone new. Key points:
* Don't need them if you're just building - this will fetch libraries and headers on-the-fly, but won't make them available in the runtime - licensing and you need more than these for the runtime anyway (need the daemon for camera discovery)
* Where to get the IDS SDK for the runtime
* You must have these on the same subnet as the node
* First steps with the IDS SDK tools for configuring the cameras | non_test | readme guidelines on how when to use the ids sdk it s confusing for someone new key points don t need them if you re just building this will fetch libraries and headers on the fly but won t make them available in the runtime licensing and you need more than these for the runtime anyway need the daemon for camera discovery where to get the ids sdk for the runtime you must have these on the same subnet as the node first steps with the ids sdk tools for configuring the cameras | 0 |
300,952 | 26,005,502,985 | IssuesEvent | 2022-12-20 18:57:26 | Exiled-Team/EXILED | https://api.github.com/repos/Exiled-Team/EXILED | closed | [BUG] Lockers property does not contain all lockers | requires-testing | **The list of lockers of Map does not contain all lockers**
The `Lockers` property of `Exiled.API.Features.Map` does not contain all lockers!
indeed if you call this method `UnityEngine.Object.FindObjectsOfType<Locker>()` when the round is in lunched, you get more locker than the property.
**To Reproduce**
Steps to reproduce the behavior:
1. create a plugin with a method attached to RoundStarted Event.
Get the Lockers by `UnityEngine.Object.FindObjectsOfType<Locker>();`
Get the Lockers by `Exiled.API.Features.Map.Lockers;`
- The attach method Server.RoundStarted
```cs
var lockerFindObjects = UnityEngine.Object.FindObjectsOfType<Locker>();
Log.Send("Lockers by UnityEngine.Object------------", Discord.LogLevel.Debug, ConsoleColor.Blue);
foreach (var locker in lockerFindObjects)
{
Log.Debug(locker);
}
Log.Debug("Lockers by Exiled------------------------", Discord.LogLevel.Debug, ConsoleColor.Blue);
foreach (var locker in Map.Lockers)
{
Log.Debug(locker);
}
```
2. Start the serveur with the plugin...
3. Start round...
4. See the log
**Expected behavior**
Same value in `Lockers` and the value of `UnityEngine.Object.FindObjectsOfType<Locker>()`
**Server logs**
[Log.txt](https://github.com/Exiled-Team/EXILED/files/9914805/Log.txt)
**EXILED Version ("latest" is not a version):**
Exiled.Loader - Version 5.3.0
**Results of `show plugins` command in console:**
```
[2022-11-02 01:29:38.116 +01:00] Total number of plugins: 7
Enabled plugins: 7
Disabled plugins: 0
Exiled.Events:
- Author: Exiled Team
- Version: 5.3.0.0
- Required Exiled Version: 5.3.0.0
- Prefix: exiled_events
- Priority: Highest
TestLocker:
- Author: VT
- Version: 1.0.0
- Required Exiled Version: 5.3.0.0
- Prefix: test_locker
- Priority: Medium
Exiled.Updater:
- Author: Exiled.Updater
- Version: 3.1.1.0
- Required Exiled Version: 5.3.0.0
- Prefix: exiled_updater
- Priority: Medium
Exiled.Permissions:
- Author: Exiled Team
- Version: 5.3.0.0
- Required Exiled Version: 5.3.0.0
- Prefix: exiled_permissions
- Priority: Medium
Exiled.CreditTags:
- Author: Babyboucher20 & iRebbok & Exiled Team
- Version: 5.3.0.0
- Required Exiled Version: 5.3.0.0
- Prefix: exiled_credits
- Priority: Medium
Exiled.CustomRoles:
- Author: Exiled Team
- Version: 5.3.0.0
- Required Exiled Version: 5.3.0.0
- Prefix: exiled_custom_roles
- Priority: Medium
Exiled.CustomItems:
- Author: Exiled Team
- Version: 5.3.0.0
- Required Exiled Version: 5.3.0.0
- Prefix: exiled_custom_items
- Priority: Medium
```
| 1.0 | [BUG] Lockers property does not contain all lockers - **The list of lockers of Map does not contain all lockers**
The `Lockers` property of `Exiled.API.Features.Map` does not contain all lockers!
indeed if you call this method `UnityEngine.Object.FindObjectsOfType<Locker>()` when the round is in lunched, you get more locker than the property.
**To Reproduce**
Steps to reproduce the behavior:
1. create a plugin with a method attached to RoundStarted Event.
Get the Lockers by `UnityEngine.Object.FindObjectsOfType<Locker>();`
Get the Lockers by `Exiled.API.Features.Map.Lockers;`
- The attach method Server.RoundStarted
```cs
var lockerFindObjects = UnityEngine.Object.FindObjectsOfType<Locker>();
Log.Send("Lockers by UnityEngine.Object------------", Discord.LogLevel.Debug, ConsoleColor.Blue);
foreach (var locker in lockerFindObjects)
{
Log.Debug(locker);
}
Log.Debug("Lockers by Exiled------------------------", Discord.LogLevel.Debug, ConsoleColor.Blue);
foreach (var locker in Map.Lockers)
{
Log.Debug(locker);
}
```
2. Start the serveur with the plugin...
3. Start round...
4. See the log
**Expected behavior**
Same value in `Lockers` and the value of `UnityEngine.Object.FindObjectsOfType<Locker>()`
**Server logs**
[Log.txt](https://github.com/Exiled-Team/EXILED/files/9914805/Log.txt)
**EXILED Version ("latest" is not a version):**
Exiled.Loader - Version 5.3.0
**Results of `show plugins` command in console:**
```
[2022-11-02 01:29:38.116 +01:00] Total number of plugins: 7
Enabled plugins: 7
Disabled plugins: 0
Exiled.Events:
- Author: Exiled Team
- Version: 5.3.0.0
- Required Exiled Version: 5.3.0.0
- Prefix: exiled_events
- Priority: Highest
TestLocker:
- Author: VT
- Version: 1.0.0
- Required Exiled Version: 5.3.0.0
- Prefix: test_locker
- Priority: Medium
Exiled.Updater:
- Author: Exiled.Updater
- Version: 3.1.1.0
- Required Exiled Version: 5.3.0.0
- Prefix: exiled_updater
- Priority: Medium
Exiled.Permissions:
- Author: Exiled Team
- Version: 5.3.0.0
- Required Exiled Version: 5.3.0.0
- Prefix: exiled_permissions
- Priority: Medium
Exiled.CreditTags:
- Author: Babyboucher20 & iRebbok & Exiled Team
- Version: 5.3.0.0
- Required Exiled Version: 5.3.0.0
- Prefix: exiled_credits
- Priority: Medium
Exiled.CustomRoles:
- Author: Exiled Team
- Version: 5.3.0.0
- Required Exiled Version: 5.3.0.0
- Prefix: exiled_custom_roles
- Priority: Medium
Exiled.CustomItems:
- Author: Exiled Team
- Version: 5.3.0.0
- Required Exiled Version: 5.3.0.0
- Prefix: exiled_custom_items
- Priority: Medium
```
| test | lockers property does not contain all lockers the list of lockers of map does not contain all lockers the lockers property of exiled api features map does not contain all lockers indeed if you call this method unityengine object findobjectsoftype when the round is in lunched you get more locker than the property to reproduce steps to reproduce the behavior create a plugin with a method attached to roundstarted event get the lockers by unityengine object findobjectsoftype get the lockers by exiled api features map lockers the attach method server roundstarted cs var lockerfindobjects unityengine object findobjectsoftype log send lockers by unityengine object discord loglevel debug consolecolor blue foreach var locker in lockerfindobjects log debug locker log debug lockers by exiled discord loglevel debug consolecolor blue foreach var locker in map lockers log debug locker start the serveur with the plugin start round see the log expected behavior same value in lockers and the value of unityengine object findobjectsoftype server logs exiled version latest is not a version exiled loader version results of show plugins command in console total number of plugins enabled plugins disabled plugins exiled events author exiled team version required exiled version prefix exiled events priority highest testlocker author vt version required exiled version prefix test locker priority medium exiled updater author exiled updater version required exiled version prefix exiled updater priority medium exiled permissions author exiled team version required exiled version prefix exiled permissions priority medium exiled credittags author irebbok exiled team version required exiled version prefix exiled credits priority medium exiled customroles author exiled team version required exiled version prefix exiled custom roles priority medium exiled customitems author exiled team version required exiled version prefix exiled custom items priority medium | 1 |
14,377 | 3,392,833,492 | IssuesEvent | 2015-11-30 21:20:30 | mapbox/mapbox-gl-native | https://api.github.com/repos/mapbox/mapbox-gl-native | opened | Telemetry logging | feature iOS telemetry tests | The iOS SDK should have a debug mode that writes the following information to a file accessible via iTunes:
* Each launch due to a background location update
* Each request the SDK makes against the events API
This will help us better diagnose and verify fixes for bugs such as #1792.
/cc @incanus @friedbunny @bleege | 1.0 | Telemetry logging - The iOS SDK should have a debug mode that writes the following information to a file accessible via iTunes:
* Each launch due to a background location update
* Each request the SDK makes against the events API
This will help us better diagnose and verify fixes for bugs such as #1792.
/cc @incanus @friedbunny @bleege | test | telemetry logging the ios sdk should have a debug mode that writes the following information to a file accessible via itunes each launch due to a background location update each request the sdk makes against the events api this will help us better diagnose and verify fixes for bugs such as cc incanus friedbunny bleege | 1 |
112,805 | 17,102,307,143 | IssuesEvent | 2021-07-09 13:03:13 | brogers588/Java_Demo | https://api.github.com/repos/brogers588/Java_Demo | opened | CVE-2020-25638 (High) detected in hibernate-core-5.4.17.Final.jar | security vulnerability | ## CVE-2020-25638 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hibernate-core-5.4.17.Final.jar</b></p></summary>
<p>Hibernate's core ORM functionality</p>
<p>Library home page: <a href="http://hibernate.org/orm">http://hibernate.org/orm</a></p>
<p>Path to dependency file: Java_Demo/api/jdbc/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/hibernate/hibernate-core/5.4.17.Final/hibernate-core-5.4.17.Final.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-jpa-2.3.1.RELEASE.jar (Root Library)
- :x: **hibernate-core-5.4.17.Final.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/brogers588/Java_Demo/commit/f341ea6098abba6c53071f92d152fa5436b8a790">f341ea6098abba6c53071f92d152fa5436b8a790</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A flaw was found in hibernate-core in versions prior to and including 5.4.23.Final. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SQL comments of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks. The highest threat from this vulnerability is to data confidentiality and integrity.
<p>Publish Date: 2020-12-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-25638>CVE-2020-25638</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.4</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: 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://in.relation.to/2020/11/19/hibernate-orm-5424-final-release/">https://in.relation.to/2020/11/19/hibernate-orm-5424-final-release/</a></p>
<p>Release Date: 2020-12-02</p>
<p>Fix Resolution: org.hibernate:hibernate-core:5.3.20.Final,5.4.24.Final</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.hibernate","packageName":"hibernate-core","packageVersion":"5.4.17.Final","packageFilePaths":["/api/jdbc/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.springframework.boot:spring-boot-starter-data-jpa:2.3.1.RELEASE;org.hibernate:hibernate-core:5.4.17.Final","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.hibernate:hibernate-core:5.3.20.Final,5.4.24.Final"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-25638","vulnerabilityDetails":"A flaw was found in hibernate-core in versions prior to and including 5.4.23.Final. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SQL comments of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks. The highest threat from this vulnerability is to data confidentiality and integrity.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-25638","cvss3Severity":"high","cvss3Score":"7.4","cvss3Metrics":{"A":"None","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-25638 (High) detected in hibernate-core-5.4.17.Final.jar - ## CVE-2020-25638 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hibernate-core-5.4.17.Final.jar</b></p></summary>
<p>Hibernate's core ORM functionality</p>
<p>Library home page: <a href="http://hibernate.org/orm">http://hibernate.org/orm</a></p>
<p>Path to dependency file: Java_Demo/api/jdbc/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/hibernate/hibernate-core/5.4.17.Final/hibernate-core-5.4.17.Final.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-jpa-2.3.1.RELEASE.jar (Root Library)
- :x: **hibernate-core-5.4.17.Final.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/brogers588/Java_Demo/commit/f341ea6098abba6c53071f92d152fa5436b8a790">f341ea6098abba6c53071f92d152fa5436b8a790</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A flaw was found in hibernate-core in versions prior to and including 5.4.23.Final. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SQL comments of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks. The highest threat from this vulnerability is to data confidentiality and integrity.
<p>Publish Date: 2020-12-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-25638>CVE-2020-25638</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.4</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: 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://in.relation.to/2020/11/19/hibernate-orm-5424-final-release/">https://in.relation.to/2020/11/19/hibernate-orm-5424-final-release/</a></p>
<p>Release Date: 2020-12-02</p>
<p>Fix Resolution: org.hibernate:hibernate-core:5.3.20.Final,5.4.24.Final</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.hibernate","packageName":"hibernate-core","packageVersion":"5.4.17.Final","packageFilePaths":["/api/jdbc/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.springframework.boot:spring-boot-starter-data-jpa:2.3.1.RELEASE;org.hibernate:hibernate-core:5.4.17.Final","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.hibernate:hibernate-core:5.3.20.Final,5.4.24.Final"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-25638","vulnerabilityDetails":"A flaw was found in hibernate-core in versions prior to and including 5.4.23.Final. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SQL comments of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks. The highest threat from this vulnerability is to data confidentiality and integrity.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-25638","cvss3Severity":"high","cvss3Score":"7.4","cvss3Metrics":{"A":"None","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_test | cve high detected in hibernate core final jar cve high severity vulnerability vulnerable library hibernate core final jar hibernate s core orm functionality library home page a href path to dependency file java demo api jdbc pom xml path to vulnerable library home wss scanner repository org hibernate hibernate core final hibernate core final jar dependency hierarchy spring boot starter data jpa release jar root library x hibernate core final jar vulnerable library found in head commit a href found in base branch master vulnerability details a flaw was found in hibernate core in versions prior to and including final a sql injection in the implementation of the jpa criteria api can permit unsanitized literals when a literal is used in the sql comments of the query this flaw could allow an attacker to access unauthorized information or possibly conduct further attacks the highest threat from this vulnerability is to data confidentiality and integrity 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 none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org hibernate hibernate core final final isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree org springframework boot spring boot starter data jpa release org hibernate hibernate core final isminimumfixversionavailable true minimumfixversion org hibernate hibernate core final final basebranches vulnerabilityidentifier cve vulnerabilitydetails a flaw was found in hibernate core in versions prior to and including final a sql injection in the implementation of the jpa criteria api can permit unsanitized literals when a literal is used in the sql comments of the query this flaw could allow an attacker to access unauthorized information or possibly conduct further attacks the highest threat from this vulnerability is to data confidentiality and integrity vulnerabilityurl | 0 |
115,138 | 9,781,901,900 | IssuesEvent | 2019-06-07 21:15:00 | rancher/rancher | https://api.github.com/repos/rancher/rancher | closed | Istio - Error message misleading when attempting to edit service mesh without permissions | [zube]: To Test alpha area/istio area/ui kind/bug-qa | rancher/rancher:master 1c18dda3 6/6
When attempting to edit service mesh configuration without the correct permissions, the current error message is: `
Only users who have System project access can view this page.`
The message should be updated to read: `You do not have permission to configure service mesh.` as is in monitoring configuration. | 1.0 | Istio - Error message misleading when attempting to edit service mesh without permissions - rancher/rancher:master 1c18dda3 6/6
When attempting to edit service mesh configuration without the correct permissions, the current error message is: `
Only users who have System project access can view this page.`
The message should be updated to read: `You do not have permission to configure service mesh.` as is in monitoring configuration. | test | istio error message misleading when attempting to edit service mesh without permissions rancher rancher master when attempting to edit service mesh configuration without the correct permissions the current error message is only users who have system project access can view this page the message should be updated to read you do not have permission to configure service mesh as is in monitoring configuration | 1 |
131,917 | 10,722,271,796 | IssuesEvent | 2019-10-27 10:42:35 | wix/stylable | https://api.github.com/repos/wix/stylable | closed | Create documentation for StylableDOMUtils test-kit | docs tests | Document the features and API of the test-kit with examples
[stylable-dom-util.ts](https://github.com/wix/stylable/blob/master/tests/utils/stylable-dom-util.ts) | 1.0 | Create documentation for StylableDOMUtils test-kit - Document the features and API of the test-kit with examples
[stylable-dom-util.ts](https://github.com/wix/stylable/blob/master/tests/utils/stylable-dom-util.ts) | test | create documentation for stylabledomutils test kit document the features and api of the test kit with examples | 1 |
11,904 | 3,237,348,330 | IssuesEvent | 2015-10-14 11:22:16 | kubernetes/kubernetes | https://api.github.com/repos/kubernetes/kubernetes | closed | hack/verify-godeps.sh is failing on release-1.1 branch | kind/bug priority/P1 team/test-infra | ```
package github.com/aws/aws-sdk-go/internal/apierr
imports github.com/aws/aws-sdk-go/internal/apierr
imports github.com/aws/aws-sdk-go/internal/apierr: cannot find package "github.com/aws/aws-sdk-go/internal/apierr" in any of:
/root/.gvm/gos/go1.4/src/github.com/aws/aws-sdk-go/internal/apierr (from $GOROOT)
/tmp/gopath.JUrP0w/src/github.com/aws/aws-sdk-go/internal/apierr (from $GOPATH)
godep: restore: exit status 1
package github.com/google/google-api-go-client/cloudmonitoring/v2beta2
imports github.com/google/google-api-go-client/cloudmonitoring/v2beta2
imports github.com/google/google-api-go-client/cloudmonitoring/v2beta2: code in directory /tmp/gopath.JUrP0w/src/github.com/google/google-api-go-client/cloudmonitoring/v2beta2 expects import "google.golang.org/api/cloudmonitoring/v2beta2"
godep: restore: exit status 1
!!! Error in ./hack/verify-godeps.sh:69
'"${GODEP}" restore' exited with status 1
Call stack:
1: ./hack/verify-godeps.sh:69 main(...)
Exiting with status 1
``` | 1.0 | hack/verify-godeps.sh is failing on release-1.1 branch - ```
package github.com/aws/aws-sdk-go/internal/apierr
imports github.com/aws/aws-sdk-go/internal/apierr
imports github.com/aws/aws-sdk-go/internal/apierr: cannot find package "github.com/aws/aws-sdk-go/internal/apierr" in any of:
/root/.gvm/gos/go1.4/src/github.com/aws/aws-sdk-go/internal/apierr (from $GOROOT)
/tmp/gopath.JUrP0w/src/github.com/aws/aws-sdk-go/internal/apierr (from $GOPATH)
godep: restore: exit status 1
package github.com/google/google-api-go-client/cloudmonitoring/v2beta2
imports github.com/google/google-api-go-client/cloudmonitoring/v2beta2
imports github.com/google/google-api-go-client/cloudmonitoring/v2beta2: code in directory /tmp/gopath.JUrP0w/src/github.com/google/google-api-go-client/cloudmonitoring/v2beta2 expects import "google.golang.org/api/cloudmonitoring/v2beta2"
godep: restore: exit status 1
!!! Error in ./hack/verify-godeps.sh:69
'"${GODEP}" restore' exited with status 1
Call stack:
1: ./hack/verify-godeps.sh:69 main(...)
Exiting with status 1
``` | test | hack verify godeps sh is failing on release branch package github com aws aws sdk go internal apierr imports github com aws aws sdk go internal apierr imports github com aws aws sdk go internal apierr cannot find package github com aws aws sdk go internal apierr in any of root gvm gos src github com aws aws sdk go internal apierr from goroot tmp gopath src github com aws aws sdk go internal apierr from gopath godep restore exit status package github com google google api go client cloudmonitoring imports github com google google api go client cloudmonitoring imports github com google google api go client cloudmonitoring code in directory tmp gopath src github com google google api go client cloudmonitoring expects import google golang org api cloudmonitoring godep restore exit status error in hack verify godeps sh godep restore exited with status call stack hack verify godeps sh main exiting with status | 1 |
5,431 | 2,610,187,466 | IssuesEvent | 2015-02-26 18:59:26 | chrsmith/quchuseban | https://api.github.com/repos/chrsmith/quchuseban | opened | 详解脸上的色斑怎么能消除 | auto-migrated Priority-Medium Type-Defect | ```
《摘要》
化妆是女性的必修课，但是化妆品内的重金属成分会使肌肤��
�到损害，清晰不彻底会沉淀在肌肤表层形成色斑。所以，选�
��化妆品是一定要挑选合格的适合自己肤质的产品，并且要把
彩妆彻底清洁干净。脸上的色斑怎么能消除，
《客户案例》
我脸上的色斑是总是熬夜上网长出来的，刚开始很多人��
�诉我维生素e祛斑效果挺好的，还能抗衰老永葆
青春，美白护肤，总之说的那个天花乱坠，就差返老还童了��
�当时我也没经得住诱惑就去买了一大瓶，每天都很虔诚的服�
��，希望我脸上的色斑能快点离我而去。可坚持使用了三个月
之久，脸上的色斑是纹丝不
动，就像要在我脸上安营扎寨了，我忍不住对这个维生素e祛�
��的效果产生了怀疑，就忍不住查了下百度百科，百科告诉我
们：<br>
维生素e能促进人体新陈代谢，增强机体耐力，提高免疫�
��。此外，维生素e是一种高效抗氧化剂，能保护
生物膜免于遭受过氧化物的损害，起着改善皮肤血液循环，��
�强肌肤细胞活力及延缓衰老的作用。缺乏它
，会产生皮肤发干、粗糙、过度老化等不良后果。成人的维��
�素e供给量为15毫克/日。富含维生素e的主
要是坚果类食物，如花生、核桃、芝麻以及瘦肉、乳类、蛋��
�、麦芽等。<br>
看到了没，压根和祛斑都不怎么沾边，这下我痛定思痛��
�我这斑再不去都没法见人了，我果断的订购了两个周期的「�
��芙薇尔精华液」，你要问了，为什么我要买这个，呵呵，我
同事告诉的，结果用完第一个周期的时候就感觉斑有些变淡��
�皮肤也好像变白了，用完第二个周期，该死的色斑终于消失�
��见了，皮肤也白嫩了很多，我这下终于放心了。<br>
通过我的亲身经历给那些用维生素e祛斑的姐妹一个提醒�
��这个还是不要太认真的为好。
阅读了脸上的色斑怎么能消除，再看脸上容易长斑的原因：
《色斑形成原因》
内部因素
一、压力
当人受到压力时，就会分泌肾上腺素，为对付压力而做��
�备。如果长期受到压力，人体新陈代谢的平衡就会遭到破坏�
��皮肤所需的营养供应趋于缓慢，色素母细胞就会变得很活跃
。
二、荷尔蒙分泌失调
避孕药里所含的女性荷尔蒙雌激素，会刺激麦拉宁细胞��
�分泌而形成不均匀的斑点，因避孕药而形成的斑点，虽然在�
��药中断后会停止，但仍会在皮肤上停留很长一段时间。怀孕
中因女性荷尔蒙雌激素的增加，从怀孕4—5个月开始会容易出
现斑，这时候出现的斑点在产后大部分会消失。可是，新陈��
�谢不正常、肌肤裸露在强烈的紫外线下、精神上受到压力等�
��因，都会使斑加深。有时新长出的斑，产后也不会消失，所
以需要更加注意。
三、新陈代谢缓慢
肝的新陈代谢功能不正常或卵巢功能减退时也会出现斑��
�因为新陈代谢不顺畅、或内分泌失调，使身体处于敏感状态�
��，从而加剧色素问题。我们常说的便秘会形成斑，其实就是
内分泌失调导致过敏体质而形成的。另外，身体状态不正常��
�时候，紫外线的照射也会加速斑的形成。
四、错误的使用化妆品
使用了不适合自己皮肤的化妆品，会导致皮肤过敏。在��
�疗的过程中如过量照射到紫外线，皮肤会为了抵御外界的侵�
��，在有炎症的部位聚集麦拉宁色素，这样会出现色素沉着的
问题。
外部因素
一、紫外线
照射紫外线的时候，人体为了保护皮肤，会在基底层产��
�很多麦拉宁色素。所以为了保护皮肤，会在敏感部位聚集更�
��的色素。经常裸露在强烈的阳光底下不仅促进皮肤的老化，
还会引起黑斑、雀斑等色素沉着的皮肤疾患。
二、不良的清洁习惯
因强烈的清洁习惯使皮肤变得敏感，这样会刺激皮肤。��
�皮肤敏感时，人体为了保护皮肤，黑色素细胞会分泌很多麦�
��宁色素，当色素过剩时就出现了斑、瑕疵等皮肤色素沉着的
问题。
三、遗传基因
父母中有长斑的，则本人长斑的概率就很高，这种情况��
�一定程度上就可判定是遗传基因的作用。所以家里特别是长�
��有长斑的人，要注意避免引发长斑的重要因素之一——紫外
线照射，这是预防斑必须注意的。
《有疑问帮你解决》
1,黛芙薇尔精华液真的有效果吗?真的可以把脸上的黄褐��
�去掉吗?
答：黛芙薇尔精华液DNA精华能够有效的修复周围难以触��
�的色斑，其独有的纳豆成分为皮肤的美白与靓丽，提供了必�
��可少的营养物质，可以有效的去除黄褐斑，黄褐斑，黄褐斑
，蝴蝶斑，晒斑、妊娠斑等。它它完全突破了传统的美肤时��
�，宛如在皮肤中注入了一杯兼具活化、再生、滋养等功效的�
��尾酒，同时为脸部提供大量有机维生素精华，脸部的改变显
而易见。自产品上市以来，老顾客纷纷介绍新顾客，71%的新��
�客都是通过老顾客介绍而来，口碑由此而来!
2，服用黛芙薇尔美白，会伤身体吗?有副作用吗?
答：黛芙薇尔精华液应用了精纯复合配方和领先的分类��
�斑科技，并将“DNA美肤系统”疗法应用到了该产品中，能彻�
��祛除黄褐斑，蝴蝶斑，妊娠斑，晒斑，黄褐斑，老年斑，有
效淡化黄褐斑至接近肤色。黛芙薇尔通过法国、美国、台湾��
�地的专家通力协作，超过10年的研究以全新的DNA肌肤修复技��
�，挑战传统化学护肤理念，不懈追寻发现破译大自然的美丽�
��迹，令每一位爱美的女性都能享受到科技创新所带来的自然
之美。
专为亚洲女性肤质研制，精心呵护女性美丽，多年来，为数��
�百万计的女性解除了黄褐斑困扰。深得广大女性朋友的信赖!
3，去除黄褐斑之后，会反弹吗?
答：很多曾经长了黄褐斑的人士，自从选择了黛芙薇尔��
�白，就一劳永逸。这款祛斑产品是经过数十位权威祛斑专家�
��据斑的形成原因精心研制而成用事实说话，让消费者打分。
树立权威品牌!我们的很多新客户都是老客户介绍而来，请问�
��如果效果不好，会有客户转介绍吗?
4，你们的价格有点贵，能不能便宜一点?
答：如果您使用西药最少需要2000元，煎服的药最少需要3
000元，做手术最少是5000元，而这些毫无疑问，不会对彻底去�
��你的斑点有任何帮助!一分价钱，一份价值，我们现在做的��
�是一个口碑，一个品牌，价钱并不高。如果花这点钱把你的�
��褐斑彻底去除，你还会觉得贵吗?你还会再去花那么多冤枉��
�，不但斑没去掉，还把自己的皮肤弄的越来越糟吗
5，我适合用黛芙薇尔精华液吗?
答：黛芙薇尔适用人群：
1、生理紊乱引起的黄褐斑人群
2、生育引起的妊娠斑人群
3、年纪增长引起的老年斑人群
4、化妆品色素沉积、辐射斑人群
5、长期日照引起的日晒斑人群
6、肌肤暗淡急需美白的人群
《祛斑小方法》
脸上的色斑怎么能消除，同时为您分享祛斑小方法
1、葛根羹
原料：葛粉9克，葡萄干9粒。
做法：将葛粉、葡萄干放入碗中，加少量饮用净水调匀，再��
�沸水冲泡。边冲边搅拌成糊状即可
2、葛根小排汤
原料：葛根100克，山药50克，猪小排250克，食盐2克。
做法：将小排洗净、过水，再放入煮沸的汤水中，加葛根、��
�药同煮，先用旺火再改用文火煲1小时，加入食盐调味即成
以上就是简单介绍了如何美容祛斑，这只能淡化色斑，要想��
�底祛斑还是中药内调好。
```
-----
Original issue reported on code.google.com by `additive...@gmail.com` on 1 Jul 2014 at 4:12 | 1.0 | 详解脸上的色斑怎么能消除 - ```
《摘要》
化妆是女性的必修课，但是化妆品内的重金属成分会使肌肤��
�到损害，清晰不彻底会沉淀在肌肤表层形成色斑。所以，选�
��化妆品是一定要挑选合格的适合自己肤质的产品，并且要把
彩妆彻底清洁干净。脸上的色斑怎么能消除，
《客户案例》
我脸上的色斑是总是熬夜上网长出来的，刚开始很多人��
�诉我维生素e祛斑效果挺好的，还能抗衰老永葆
青春，美白护肤，总之说的那个天花乱坠，就差返老还童了��
�当时我也没经得住诱惑就去买了一大瓶，每天都很虔诚的服�
��，希望我脸上的色斑能快点离我而去。可坚持使用了三个月
之久，脸上的色斑是纹丝不
动，就像要在我脸上安营扎寨了，我忍不住对这个维生素e祛�
��的效果产生了怀疑，就忍不住查了下百度百科，百科告诉我
们：<br>
维生素e能促进人体新陈代谢，增强机体耐力，提高免疫�
��。此外，维生素e是一种高效抗氧化剂，能保护
生物膜免于遭受过氧化物的损害，起着改善皮肤血液循环，��
�强肌肤细胞活力及延缓衰老的作用。缺乏它
，会产生皮肤发干、粗糙、过度老化等不良后果。成人的维��
�素e供给量为15毫克/日。富含维生素e的主
要是坚果类食物，如花生、核桃、芝麻以及瘦肉、乳类、蛋��
�、麦芽等。<br>
看到了没，压根和祛斑都不怎么沾边，这下我痛定思痛��
�我这斑再不去都没法见人了，我果断的订购了两个周期的「�
��芙薇尔精华液」，你要问了，为什么我要买这个，呵呵，我
同事告诉的，结果用完第一个周期的时候就感觉斑有些变淡��
�皮肤也好像变白了，用完第二个周期，该死的色斑终于消失�
��见了，皮肤也白嫩了很多，我这下终于放心了。<br>
通过我的亲身经历给那些用维生素e祛斑的姐妹一个提醒�
��这个还是不要太认真的为好。
阅读了脸上的色斑怎么能消除，再看脸上容易长斑的原因：
《色斑形成原因》
内部因素
一、压力
当人受到压力时，就会分泌肾上腺素，为对付压力而做��
�备。如果长期受到压力，人体新陈代谢的平衡就会遭到破坏�
��皮肤所需的营养供应趋于缓慢，色素母细胞就会变得很活跃
。
二、荷尔蒙分泌失调
避孕药里所含的女性荷尔蒙雌激素，会刺激麦拉宁细胞��
�分泌而形成不均匀的斑点，因避孕药而形成的斑点，虽然在�
��药中断后会停止，但仍会在皮肤上停留很长一段时间。怀孕
中因女性荷尔蒙雌激素的增加，从怀孕4—5个月开始会容易出
现斑，这时候出现的斑点在产后大部分会消失。可是，新陈��
�谢不正常、肌肤裸露在强烈的紫外线下、精神上受到压力等�
��因，都会使斑加深。有时新长出的斑，产后也不会消失，所
以需要更加注意。
三、新陈代谢缓慢
肝的新陈代谢功能不正常或卵巢功能减退时也会出现斑��
�因为新陈代谢不顺畅、或内分泌失调，使身体处于敏感状态�
��，从而加剧色素问题。我们常说的便秘会形成斑，其实就是
内分泌失调导致过敏体质而形成的。另外，身体状态不正常��
�时候，紫外线的照射也会加速斑的形成。
四、错误的使用化妆品
使用了不适合自己皮肤的化妆品，会导致皮肤过敏。在��
�疗的过程中如过量照射到紫外线，皮肤会为了抵御外界的侵�
��，在有炎症的部位聚集麦拉宁色素，这样会出现色素沉着的
问题。
外部因素
一、紫外线
照射紫外线的时候，人体为了保护皮肤，会在基底层产��
�很多麦拉宁色素。所以为了保护皮肤，会在敏感部位聚集更�
��的色素。经常裸露在强烈的阳光底下不仅促进皮肤的老化，
还会引起黑斑、雀斑等色素沉着的皮肤疾患。
二、不良的清洁习惯
因强烈的清洁习惯使皮肤变得敏感，这样会刺激皮肤。��
�皮肤敏感时，人体为了保护皮肤，黑色素细胞会分泌很多麦�
��宁色素，当色素过剩时就出现了斑、瑕疵等皮肤色素沉着的
问题。
三、遗传基因
父母中有长斑的，则本人长斑的概率就很高，这种情况��
�一定程度上就可判定是遗传基因的作用。所以家里特别是长�
��有长斑的人，要注意避免引发长斑的重要因素之一——紫外
线照射，这是预防斑必须注意的。
《有疑问帮你解决》
1,黛芙薇尔精华液真的有效果吗?真的可以把脸上的黄褐��
�去掉吗?
答：黛芙薇尔精华液DNA精华能够有效的修复周围难以触��
�的色斑，其独有的纳豆成分为皮肤的美白与靓丽，提供了必�
��可少的营养物质，可以有效的去除黄褐斑，黄褐斑，黄褐斑
，蝴蝶斑，晒斑、妊娠斑等。它它完全突破了传统的美肤时��
�，宛如在皮肤中注入了一杯兼具活化、再生、滋养等功效的�
��尾酒，同时为脸部提供大量有机维生素精华，脸部的改变显
而易见。自产品上市以来，老顾客纷纷介绍新顾客，71%的新��
�客都是通过老顾客介绍而来，口碑由此而来!
2，服用黛芙薇尔美白，会伤身体吗?有副作用吗?
答：黛芙薇尔精华液应用了精纯复合配方和领先的分类��
�斑科技，并将“DNA美肤系统”疗法应用到了该产品中，能彻�
��祛除黄褐斑，蝴蝶斑，妊娠斑，晒斑，黄褐斑，老年斑，有
效淡化黄褐斑至接近肤色。黛芙薇尔通过法国、美国、台湾��
�地的专家通力协作，超过10年的研究以全新的DNA肌肤修复技��
�，挑战传统化学护肤理念，不懈追寻发现破译大自然的美丽�
��迹，令每一位爱美的女性都能享受到科技创新所带来的自然
之美。
专为亚洲女性肤质研制，精心呵护女性美丽，多年来，为数��
�百万计的女性解除了黄褐斑困扰。深得广大女性朋友的信赖!
3，去除黄褐斑之后，会反弹吗?
答：很多曾经长了黄褐斑的人士，自从选择了黛芙薇尔��
�白，就一劳永逸。这款祛斑产品是经过数十位权威祛斑专家�
��据斑的形成原因精心研制而成用事实说话，让消费者打分。
树立权威品牌!我们的很多新客户都是老客户介绍而来，请问�
��如果效果不好，会有客户转介绍吗?
4，你们的价格有点贵，能不能便宜一点?
答：如果您使用西药最少需要2000元，煎服的药最少需要3
000元，做手术最少是5000元，而这些毫无疑问，不会对彻底去�
��你的斑点有任何帮助!一分价钱，一份价值，我们现在做的��
�是一个口碑，一个品牌，价钱并不高。如果花这点钱把你的�
��褐斑彻底去除，你还会觉得贵吗?你还会再去花那么多冤枉��
�，不但斑没去掉，还把自己的皮肤弄的越来越糟吗
5，我适合用黛芙薇尔精华液吗?
答：黛芙薇尔适用人群：
1、生理紊乱引起的黄褐斑人群
2、生育引起的妊娠斑人群
3、年纪增长引起的老年斑人群
4、化妆品色素沉积、辐射斑人群
5、长期日照引起的日晒斑人群
6、肌肤暗淡急需美白的人群
《祛斑小方法》
脸上的色斑怎么能消除，同时为您分享祛斑小方法
1、葛根羹
原料：葛粉9克，葡萄干9粒。
做法：将葛粉、葡萄干放入碗中，加少量饮用净水调匀，再��
�沸水冲泡。边冲边搅拌成糊状即可
2、葛根小排汤
原料：葛根100克，山药50克，猪小排250克，食盐2克。
做法：将小排洗净、过水，再放入煮沸的汤水中，加葛根、��
�药同煮，先用旺火再改用文火煲1小时，加入食盐调味即成
以上就是简单介绍了如何美容祛斑，这只能淡化色斑，要想��
�底祛斑还是中药内调好。
```
-----
Original issue reported on code.google.com by `additive...@gmail.com` on 1 Jul 2014 at 4:12 | non_test | 详解脸上的色斑怎么能消除 《摘要》 化妆是女性的必修课，但是化妆品内的重金属成分会使肌肤�� �到损害，清晰不彻底会沉淀在肌肤表层形成色斑。所以，选� ��化妆品是一定要挑选合格的适合自己肤质的产品，并且要把 彩妆彻底清洁干净。脸上的色斑怎么能消除， 《客户案例》 我脸上的色斑是总是熬夜上网长出来的，刚开始很多人�� �诉我维生素e祛斑效果挺好的，还能抗衰老永葆 青春，美白护肤，总之说的那个天花乱坠，就差返老还童了�� �当时我也没经得住诱惑就去买了一大瓶，每天都很虔诚的服� ��，希望我脸上的色斑能快点离我而去。可坚持使用了三个月 之久，脸上的色斑是纹丝不 动，就像要在我脸上安营扎寨了，我忍不住对这个维生素e祛� ��的效果产生了怀疑，就忍不住查了下百度百科，百科告诉我 们： 维生素e能促进人体新陈代谢，增强机体耐力，提高免疫� ��。此外，维生素e是一种高效抗氧化剂，能保护 生物膜免于遭受过氧化物的损害，起着改善皮肤血液循环，�� �强肌肤细胞活力及延缓衰老的作用。缺乏它 ，会产生皮肤发干、粗糙、过度老化等不良后果。成人的维�� � 日。富含维生素e的主 要是坚果类食物，如花生、核桃、芝麻以及瘦肉、乳类、蛋�� �、麦芽等。 看到了没，压根和祛斑都不怎么沾边，这下我痛定思痛�� �我这斑再不去都没法见人了，我果断的订购了两个周期的「� ��芙薇尔精华液」，你要问了，为什么我要买这个，呵呵，我 同事告诉的，结果用完第一个周期的时候就感觉斑有些变淡�� �皮肤也好像变白了，用完第二个周期，该死的色斑终于消失� ��见了，皮肤也白嫩了很多，我这下终于放心了。 通过我的亲身经历给那些用维生素e祛斑的姐妹一个提醒� ��这个还是不要太认真的为好。 阅读了脸上的色斑怎么能消除，再看脸上容易长斑的原因： 《色斑形成原因》 内部因素 一、压力 当人受到压力时，就会分泌肾上腺素，为对付压力而做�� �备。如果长期受到压力，人体新陈代谢的平衡就会遭到破坏� ��皮肤所需的营养供应趋于缓慢，色素母细胞就会变得很活跃 。 二、荷尔蒙分泌失调 避孕药里所含的女性荷尔蒙雌激素，会刺激麦拉宁细胞�� �分泌而形成不均匀的斑点，因避孕药而形成的斑点，虽然在� ��药中断后会停止，但仍会在皮肤上停留很长一段时间。怀孕 中因女性荷尔蒙雌激素的增加， — 现斑，这时候出现的斑点在产后大部分会消失。可是，新陈�� �谢不正常、肌肤裸露在强烈的紫外线下、精神上受到压力等� ��因，都会使斑加深。有时新长出的斑，产后也不会消失，所 以需要更加注意。 三、新陈代谢缓慢 肝的新陈代谢功能不正常或卵巢功能减退时也会出现斑�� �因为新陈代谢不顺畅、或内分泌失调，使身体处于敏感状态� ��，从而加剧色素问题。我们常说的便秘会形成斑，其实就是 内分泌失调导致过敏体质而形成的。另外，身体状态不正常�� �时候，紫外线的照射也会加速斑的形成。 四、错误的使用化妆品 使用了不适合自己皮肤的化妆品，会导致皮肤过敏。在�� �疗的过程中如过量照射到紫外线，皮肤会为了抵御外界的侵� ��，在有炎症的部位聚集麦拉宁色素，这样会出现色素沉着的 问题。 外部因素 一、紫外线 照射紫外线的时候，人体为了保护皮肤，会在基底层产�� �很多麦拉宁色素。所以为了保护皮肤，会在敏感部位聚集更� ��的色素。经常裸露在强烈的阳光底下不仅促进皮肤的老化， 还会引起黑斑、雀斑等色素沉着的皮肤疾患。 二、不良的清洁习惯 因强烈的清洁习惯使皮肤变得敏感，这样会刺激皮肤。�� �皮肤敏感时，人体为了保护皮肤，黑色素细胞会分泌很多麦� ��宁色素，当色素过剩时就出现了斑、瑕疵等皮肤色素沉着的 问题。 三、遗传基因 父母中有长斑的，则本人长斑的概率就很高，这种情况�� �一定程度上就可判定是遗传基因的作用。所以家里特别是长� ��有长斑的人，要注意避免引发长斑的重要因素之一——紫外 线照射，这是预防斑必须注意的。 《有疑问帮你解决》 黛芙薇尔精华液真的有效果吗 真的可以把脸上的黄褐�� �去掉吗 答：黛芙薇尔精华液dna精华能够有效的修复周围难以触�� �的色斑，其独有的纳豆成分为皮肤的美白与靓丽，提供了必� ��可少的营养物质，可以有效的去除黄褐斑，黄褐斑，黄褐斑 ，蝴蝶斑，晒斑、妊娠斑等。它它完全突破了传统的美肤时�� �，宛如在皮肤中注入了一杯兼具活化、再生、滋养等功效的� ��尾酒，同时为脸部提供大量有机维生素精华，脸部的改变显 而易见。自产品上市以来，老顾客纷纷介绍新顾客， 的新�� �客都是通过老顾客介绍而来，口碑由此而来 ，服用黛芙薇尔美白，会伤身体吗 有副作用吗 答：黛芙薇尔精华液应用了精纯复合配方和领先的分类�� �斑科技，并将“dna美肤系统”疗法应用到了该产品中，能彻� ��祛除黄褐斑，蝴蝶斑，妊娠斑，晒斑，黄褐斑，老年斑，有 效淡化黄褐斑至接近肤色。黛芙薇尔通过法国、美国、台湾�� �地的专家通力协作， �� �，挑战传统化学护肤理念，不懈追寻发现破译大自然的美丽� ��迹，令每一位爱美的女性都能享受到科技创新所带来的自然 之美。 专为亚洲女性肤质研制，精心呵护女性美丽，多年来，为数�� �百万计的女性解除了黄褐斑困扰。深得广大女性朋友的信赖 ，去除黄褐斑之后，会反弹吗 答：很多曾经长了黄褐斑的人士，自从选择了黛芙薇尔�� �白，就一劳永逸。这款祛斑产品是经过数十位权威祛斑专家� ��据斑的形成原因精心研制而成用事实说话，让消费者打分。 树立权威品牌 我们的很多新客户都是老客户介绍而来，请问� ��如果效果不好，会有客户转介绍吗 ，你们的价格有点贵，能不能便宜一点 答： ， ， ，而这些毫无疑问，不会对彻底去� ��你的斑点有任何帮助 一分价钱，一份价值，我们现在做的�� �是一个口碑，一个品牌，价钱并不高。如果花这点钱把你的� ��褐斑彻底去除，你还会觉得贵吗 你还会再去花那么多冤枉�� �，不但斑没去掉，还把自己的皮肤弄的越来越糟吗 ，我适合用黛芙薇尔精华液吗 答：黛芙薇尔适用人群： 、生理紊乱引起的黄褐斑人群 、生育引起的妊娠斑人群 、年纪增长引起的老年斑人群 、化妆品色素沉积、辐射斑人群 、长期日照引起的日晒斑人群 、肌肤暗淡急需美白的人群 《祛斑小方法》 脸上的色斑怎么能消除，同时为您分享祛斑小方法 、葛根羹 原料： ， 。 做法：将葛粉、葡萄干放入碗中，加少量饮用净水调匀，再�� �沸水冲泡。边冲边搅拌成糊状即可 、葛根小排汤 原料： ， ， ， 。 做法：将小排洗净、过水，再放入煮沸的汤水中，加葛根、�� �药同煮， ，加入食盐调味即成 以上就是简单介绍了如何美容祛斑，这只能淡化色斑，要想�� �底祛斑还是中药内调好。 original issue reported on code google com by additive gmail com on jul at | 0 |
124,820 | 26,544,760,080 | IssuesEvent | 2023-01-19 22:41:53 | pacific-hake/hake-assessment | https://api.github.com/repos/pacific-hake/hake-assessment | opened | Include U.S. discards and ensure all bycatch landings are included | type: enhancement topic: data topic: R code file: hake_data.ss topic: document improvement: code | Canada includes bycatch and discards but the U.S. catches may only include landed bycatch if it is easily seen in PacFIN. I am not entirely sure how to get this information if there are bycatch data from other fisheries like the crab fishery or things that are not in pcatch. Ensure also that the caption for Table a is updated when this is solidified. As well as other places in the document that will need updated. | 2.0 | Include U.S. discards and ensure all bycatch landings are included - Canada includes bycatch and discards but the U.S. catches may only include landed bycatch if it is easily seen in PacFIN. I am not entirely sure how to get this information if there are bycatch data from other fisheries like the crab fishery or things that are not in pcatch. Ensure also that the caption for Table a is updated when this is solidified. As well as other places in the document that will need updated. | non_test | include u s discards and ensure all bycatch landings are included canada includes bycatch and discards but the u s catches may only include landed bycatch if it is easily seen in pacfin i am not entirely sure how to get this information if there are bycatch data from other fisheries like the crab fishery or things that are not in pcatch ensure also that the caption for table a is updated when this is solidified as well as other places in the document that will need updated | 0 |
155,095 | 12,238,481,329 | IssuesEvent | 2020-05-04 19:53:18 | jorandmol/DP2-G7 | https://api.github.com/repos/jorandmol/DP2-G7 | closed | T23 - Editar Treatment | ui testing | Como veterinario quiero poder editar los datos de un tratamiento para solucionar posibles errores o actualizarlo. | 1.0 | T23 - Editar Treatment - Como veterinario quiero poder editar los datos de un tratamiento para solucionar posibles errores o actualizarlo. | test | editar treatment como veterinario quiero poder editar los datos de un tratamiento para solucionar posibles errores o actualizarlo | 1 |
140,483 | 21,103,921,909 | IssuesEvent | 2022-04-04 16:49:33 | asyncapi/infra | https://api.github.com/repos/asyncapi/infra | closed | Update README with new logo banner | enhancement good first issue area/design | #### Reason/Context
This is to replace the old AsyncAPI logo in this repo's README with the banner attached below that represents the new branding.
**Here are a few guidelines for this change as well:**
1. Make sure you are using [Markdown syntax](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) only
2. Be sure to remove the old logo as well as the old title of the repo as this image will replace both elements
3. Make sure you link this image to the website: `https://www.asyncapi.com`
4. If there is any description text below the repo title, let's make it left-aligned if it isn't already, so as to match the left-alignment of the content in the new banner image
**Download the image file:**
[github-repobanner-infra.png.zip](https://github.com/asyncapi/infra/files/8233196/github-repobanner-infra.png.zip)
------
#### Banner preview
_Please note that this is only a preview of the image, the contributor should download and use the above zip file_
<img width="830" alt="github-repobanner-infra" src="https://user-images.githubusercontent.com/60163079/157896997-2c4410bd-5766-4e7f-ac07-4f256c66e719.png">
| 1.0 | Update README with new logo banner - #### Reason/Context
This is to replace the old AsyncAPI logo in this repo's README with the banner attached below that represents the new branding.
**Here are a few guidelines for this change as well:**
1. Make sure you are using [Markdown syntax](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) only
2. Be sure to remove the old logo as well as the old title of the repo as this image will replace both elements
3. Make sure you link this image to the website: `https://www.asyncapi.com`
4. If there is any description text below the repo title, let's make it left-aligned if it isn't already, so as to match the left-alignment of the content in the new banner image
**Download the image file:**
[github-repobanner-infra.png.zip](https://github.com/asyncapi/infra/files/8233196/github-repobanner-infra.png.zip)
------
#### Banner preview
_Please note that this is only a preview of the image, the contributor should download and use the above zip file_
<img width="830" alt="github-repobanner-infra" src="https://user-images.githubusercontent.com/60163079/157896997-2c4410bd-5766-4e7f-ac07-4f256c66e719.png">
| non_test | update readme with new logo banner reason context this is to replace the old asyncapi logo in this repo s readme with the banner attached below that represents the new branding here are a few guidelines for this change as well make sure you are using only be sure to remove the old logo as well as the old title of the repo as this image will replace both elements make sure you link this image to the website if there is any description text below the repo title let s make it left aligned if it isn t already so as to match the left alignment of the content in the new banner image download the image file banner preview please note that this is only a preview of the image the contributor should download and use the above zip file img width alt github repobanner infra src | 0 |
30,154 | 11,800,353,582 | IssuesEvent | 2020-03-18 17:23:49 | jgeraigery/kraft-heinz-merger | https://api.github.com/repos/jgeraigery/kraft-heinz-merger | opened | WS-2018-0076 (Medium) detected in tunnel-agent-0.4.3.tgz | security vulnerability | ## WS-2018-0076 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tunnel-agent-0.4.3.tgz</b></p></summary>
<p>HTTP proxy tunneling agent. Formerly part of mikeal/request, now a standalone module.</p>
<p>Library home page: <a href="https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.3.tgz">https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.3.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/kraft-heinz-merger/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/kraft-heinz-merger/node_modules/bower-registry-client/node_modules/tunnel-agent/package.json</p>
<p>
Dependency Hierarchy:
- debowerify-1.5.0.tgz (Root Library)
- bower-1.3.12.tgz
- request-2.42.0.tgz
- :x: **tunnel-agent-0.4.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/jgeraigery/kraft-heinz-merger/commit/72632c58d3cc93458a56d547f4fc315bfa457ab5">72632c58d3cc93458a56d547f4fc315bfa457ab5</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Versions of tunnel-agent before 0.6.0 are vulnerable to memory exposure.
This is exploitable if user supplied input is provided to the auth value and is a number.
<p>Publish Date: 2018-04-25
<p>URL: <a href=https://github.com/request/tunnel-agent/commit/9ca95ec7219daface8a6fc2674000653de0922c0>WS-2018-0076</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nodesecurity.io/advisories/598">https://nodesecurity.io/advisories/598</a></p>
<p>Release Date: 2018-01-27</p>
<p>Fix Resolution: 0.6.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"tunnel-agent","packageVersion":"0.4.3","isTransitiveDependency":true,"dependencyTree":"debowerify:1.5.0;bower:1.3.12;request:2.42.0;tunnel-agent:0.4.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.6.0"}],"vulnerabilityIdentifier":"WS-2018-0076","vulnerabilityDetails":"Versions of tunnel-agent before 0.6.0 are vulnerable to memory exposure.\n\nThis is exploitable if user supplied input is provided to the auth value and is a number.","vulnerabilityUrl":"https://github.com/request/tunnel-agent/commit/9ca95ec7219daface8a6fc2674000653de0922c0","cvss2Severity":"medium","cvss2Score":"5.0","extraData":{}}</REMEDIATE> --> | True | WS-2018-0076 (Medium) detected in tunnel-agent-0.4.3.tgz - ## WS-2018-0076 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tunnel-agent-0.4.3.tgz</b></p></summary>
<p>HTTP proxy tunneling agent. Formerly part of mikeal/request, now a standalone module.</p>
<p>Library home page: <a href="https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.3.tgz">https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.4.3.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/kraft-heinz-merger/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/kraft-heinz-merger/node_modules/bower-registry-client/node_modules/tunnel-agent/package.json</p>
<p>
Dependency Hierarchy:
- debowerify-1.5.0.tgz (Root Library)
- bower-1.3.12.tgz
- request-2.42.0.tgz
- :x: **tunnel-agent-0.4.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/jgeraigery/kraft-heinz-merger/commit/72632c58d3cc93458a56d547f4fc315bfa457ab5">72632c58d3cc93458a56d547f4fc315bfa457ab5</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Versions of tunnel-agent before 0.6.0 are vulnerable to memory exposure.
This is exploitable if user supplied input is provided to the auth value and is a number.
<p>Publish Date: 2018-04-25
<p>URL: <a href=https://github.com/request/tunnel-agent/commit/9ca95ec7219daface8a6fc2674000653de0922c0>WS-2018-0076</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nodesecurity.io/advisories/598">https://nodesecurity.io/advisories/598</a></p>
<p>Release Date: 2018-01-27</p>
<p>Fix Resolution: 0.6.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"tunnel-agent","packageVersion":"0.4.3","isTransitiveDependency":true,"dependencyTree":"debowerify:1.5.0;bower:1.3.12;request:2.42.0;tunnel-agent:0.4.3","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.6.0"}],"vulnerabilityIdentifier":"WS-2018-0076","vulnerabilityDetails":"Versions of tunnel-agent before 0.6.0 are vulnerable to memory exposure.\n\nThis is exploitable if user supplied input is provided to the auth value and is a number.","vulnerabilityUrl":"https://github.com/request/tunnel-agent/commit/9ca95ec7219daface8a6fc2674000653de0922c0","cvss2Severity":"medium","cvss2Score":"5.0","extraData":{}}</REMEDIATE> --> | non_test | ws medium detected in tunnel agent tgz ws medium severity vulnerability vulnerable library tunnel agent tgz http proxy tunneling agent formerly part of mikeal request now a standalone module library home page a href path to dependency file tmp ws scm kraft heinz merger package json path to vulnerable library tmp ws scm kraft heinz merger node modules bower registry client node modules tunnel agent package json dependency hierarchy debowerify tgz root library bower tgz request tgz x tunnel agent tgz vulnerable library found in head commit a href vulnerability details versions of tunnel agent before are vulnerable to memory exposure this is exploitable if user supplied input is provided to the auth value and is a number publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution isopenpronvulnerability false ispackagebased true isdefaultbranch true packages vulnerabilityidentifier ws vulnerabilitydetails versions of tunnel agent before are vulnerable to memory exposure n nthis is exploitable if user supplied input is provided to the auth value and is a number vulnerabilityurl | 0 |
152,154 | 12,093,269,905 | IssuesEvent | 2020-04-19 18:57:00 | gisellemartel/CONPASS | https://api.github.com/repos/gisellemartel/CONPASS | opened | AT-25 - (US5B - As a user, I want to get map directions to external points of interest.) | Acceptance Test (SPRINT 4) | 1. Launch application
2. Select a building that supports indoor mode such as Hall and enter indoor mode by clicking on the building
3. Click on the direction button on the bottom right hand corner (blue button)
4. Enter a starting point (as you are inside)
5. Enter a destination outside like a local Tim Hortons | 1.0 | AT-25 - (US5B - As a user, I want to get map directions to external points of interest.) - 1. Launch application
2. Select a building that supports indoor mode such as Hall and enter indoor mode by clicking on the building
3. Click on the direction button on the bottom right hand corner (blue button)
4. Enter a starting point (as you are inside)
5. Enter a destination outside like a local Tim Hortons | test | at as a user i want to get map directions to external points of interest launch application select a building that supports indoor mode such as hall and enter indoor mode by clicking on the building click on the direction button on the bottom right hand corner blue button enter a starting point as you are inside enter a destination outside like a local tim hortons | 1 |
313,490 | 9,562,146,871 | IssuesEvent | 2019-05-04 06:06:15 | nooraniali17/BusMe | https://api.github.com/repos/nooraniali17/BusMe | closed | Create reset feature on Database | high priority | The Database should automatically make all the stops it has saved set to a total of 0 people waiting at midnight. | 1.0 | Create reset feature on Database - The Database should automatically make all the stops it has saved set to a total of 0 people waiting at midnight. | non_test | create reset feature on database the database should automatically make all the stops it has saved set to a total of people waiting at midnight | 0 |
191,888 | 15,306,511,371 | IssuesEvent | 2021-02-24 19:34:51 | wearerequired/lint-action | https://api.github.com/repos/wearerequired/lint-action | closed | Linter formats package-lock.json as well | documentation question | It seems that it's committing every file change after running eslint . --fix which doesn't actually affect package-lock.json, but affects the package-lock.json | 1.0 | Linter formats package-lock.json as well - It seems that it's committing every file change after running eslint . --fix which doesn't actually affect package-lock.json, but affects the package-lock.json | non_test | linter formats package lock json as well it seems that it s committing every file change after running eslint fix which doesn t actually affect package lock json but affects the package lock json | 0 |
83,681 | 7,879,378,839 | IssuesEvent | 2018-06-26 13:16:05 | OpenSCAP/openscap | https://api.github.com/repos/OpenSCAP/openscap | closed | Some tests fail if CMake build type is Release | BLOCKER bug test | If build type is Release, it defines NDEBUG, which means that `assert()` calls in some of our tests do nothing, and then the test is not performed, and some results are not generated.
An example could be https://github.com/OpenSCAP/openscap/blob/master/tests/API/XCCDF/unittests/test_xccdf_overrides.c test, which uses `assert()`. If the build type is release, it defines NDEBUG, which means that those `assert()` macros are compiled tobasically no operation. Please see `man 3 assert`.
That means that the checks are not performed. Moreover, in this example the file `test_xccdf_overrides.xml.out` is not created, because it is created iside an assert, and therefore the test fails without any report. The reason for that is that in bash test the test checks if the file exists. Please check https://github.com/OpenSCAP/openscap/blob/master/tests/API/XCCDF/unittests/test_xccdf_overrides.sh#L12
I have set CMake build type on Jenkins openscap-master job to Debug as temporary workaround.
This is the most serious problem, because some of the tests won't test anything with the released version.
Does anybody have any idea how to solve this issue? | 1.0 | Some tests fail if CMake build type is Release - If build type is Release, it defines NDEBUG, which means that `assert()` calls in some of our tests do nothing, and then the test is not performed, and some results are not generated.
An example could be https://github.com/OpenSCAP/openscap/blob/master/tests/API/XCCDF/unittests/test_xccdf_overrides.c test, which uses `assert()`. If the build type is release, it defines NDEBUG, which means that those `assert()` macros are compiled tobasically no operation. Please see `man 3 assert`.
That means that the checks are not performed. Moreover, in this example the file `test_xccdf_overrides.xml.out` is not created, because it is created iside an assert, and therefore the test fails without any report. The reason for that is that in bash test the test checks if the file exists. Please check https://github.com/OpenSCAP/openscap/blob/master/tests/API/XCCDF/unittests/test_xccdf_overrides.sh#L12
I have set CMake build type on Jenkins openscap-master job to Debug as temporary workaround.
This is the most serious problem, because some of the tests won't test anything with the released version.
Does anybody have any idea how to solve this issue? | test | some tests fail if cmake build type is release if build type is release it defines ndebug which means that assert calls in some of our tests do nothing and then the test is not performed and some results are not generated an example could be test which uses assert if the build type is release it defines ndebug which means that those assert macros are compiled tobasically no operation please see man assert that means that the checks are not performed moreover in this example the file test xccdf overrides xml out is not created because it is created iside an assert and therefore the test fails without any report the reason for that is that in bash test the test checks if the file exists please check i have set cmake build type on jenkins openscap master job to debug as temporary workaround this is the most serious problem because some of the tests won t test anything with the released version does anybody have any idea how to solve this issue | 1 |
68,892 | 13,194,343,061 | IssuesEvent | 2020-08-13 16:39:57 | dotnet/roslyn | https://api.github.com/repos/dotnet/roslyn | closed | IDE0044 "Make field readonly" false positive when used in ref return | Area-IDE Bug IDE-CodeStyle Resolution-Fixed | **Version Used**:
16.0.0 Preview 2.0
**Steps to Reproduce**:
```csharp
public class C
{
private int a, b; // IDE0044
private ref int select(bool c) => ref (c ? ref a : ref b);
public void Test() => select(true) = 3;
}
```
**Expected Behavior**:
The members are mutated. Marking them readonly breaks the code, so IDE0044 shouldn't trigger.
**Actual Behavior**:
IDE0044 is falsely triggered. | 1.0 | IDE0044 "Make field readonly" false positive when used in ref return - **Version Used**:
16.0.0 Preview 2.0
**Steps to Reproduce**:
```csharp
public class C
{
private int a, b; // IDE0044
private ref int select(bool c) => ref (c ? ref a : ref b);
public void Test() => select(true) = 3;
}
```
**Expected Behavior**:
The members are mutated. Marking them readonly breaks the code, so IDE0044 shouldn't trigger.
**Actual Behavior**:
IDE0044 is falsely triggered. | non_test | make field readonly false positive when used in ref return version used preview steps to reproduce csharp public class c private int a b private ref int select bool c ref c ref a ref b public void test select true expected behavior the members are mutated marking them readonly breaks the code so shouldn t trigger actual behavior is falsely triggered | 0 |
47,216 | 7,310,781,768 | IssuesEvent | 2018-02-28 15:55:01 | aurelia/router | https://api.github.com/repos/aurelia/router | closed | doc outline | documentation | Can we get an outline of the topics to cover in the Router: Basics doc? Thank you!
| 1.0 | doc outline - Can we get an outline of the topics to cover in the Router: Basics doc? Thank you!
| non_test | doc outline can we get an outline of the topics to cover in the router basics doc thank you | 0 |
223,329 | 17,593,716,663 | IssuesEvent | 2021-08-17 00:01:50 | pysat/pysat | https://api.github.com/repos/pysat/pysat | closed | STY/TST: caplog usage in unit tests | testing style | **Is your feature request related to a problem? Please describe.**
We currently have multiple styles of perusing the logs in the unit tests.
**Describe the solution you'd like**
Consistency is key. Ideally, the logs would be temporarily turned on and not permanently set. Example:
```
def test_download_recent_data(self, caplog):
with caplog.at_level(logging.INFO, logger='pysat'):
self.testInst.download()
```
**Describe alternatives you've considered**
There may be a cleaner method. Should make sure that we don't inundate the test logs with comments.
**Additional context**
Affects:
- [x] test_custom.py::TestLogging
- [x] test_instrument.py::TestBasics::test_download_updated_files
- [x] test_instrument.py::TestBasics::test_download_recent_data
- [x] test_instrument.py::TestBasics:: test_instrument_partial_function_keywords
- [x] test_instrument.py::TestBasics::test_instrument_partial_keywords_liveness
- [x] test_utils_coords.py:: TestLonSLT:: test_calc_solar_local_time_inconsistent_keywords
| 1.0 | STY/TST: caplog usage in unit tests - **Is your feature request related to a problem? Please describe.**
We currently have multiple styles of perusing the logs in the unit tests.
**Describe the solution you'd like**
Consistency is key. Ideally, the logs would be temporarily turned on and not permanently set. Example:
```
def test_download_recent_data(self, caplog):
with caplog.at_level(logging.INFO, logger='pysat'):
self.testInst.download()
```
**Describe alternatives you've considered**
There may be a cleaner method. Should make sure that we don't inundate the test logs with comments.
**Additional context**
Affects:
- [x] test_custom.py::TestLogging
- [x] test_instrument.py::TestBasics::test_download_updated_files
- [x] test_instrument.py::TestBasics::test_download_recent_data
- [x] test_instrument.py::TestBasics:: test_instrument_partial_function_keywords
- [x] test_instrument.py::TestBasics::test_instrument_partial_keywords_liveness
- [x] test_utils_coords.py:: TestLonSLT:: test_calc_solar_local_time_inconsistent_keywords
| test | sty tst caplog usage in unit tests is your feature request related to a problem please describe we currently have multiple styles of perusing the logs in the unit tests describe the solution you d like consistency is key ideally the logs would be temporarily turned on and not permanently set example def test download recent data self caplog with caplog at level logging info logger pysat self testinst download describe alternatives you ve considered there may be a cleaner method should make sure that we don t inundate the test logs with comments additional context affects test custom py testlogging test instrument py testbasics test download updated files test instrument py testbasics test download recent data test instrument py testbasics test instrument partial function keywords test instrument py testbasics test instrument partial keywords liveness test utils coords py testlonslt test calc solar local time inconsistent keywords | 1 |
105,734 | 9,100,470,064 | IssuesEvent | 2019-02-20 08:38:53 | humera987/FXLabs-Test-Automation | https://api.github.com/repos/humera987/FXLabs-Test-Automation | opened | Test : ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2 | test | Project : Test
Job : Default
Env : Default
Category : ABAC_Level2
Tags : [FX Top 10 - API Vulnerability, Data_Access_Control]
Severity : Major
Region : US_WEST
Result : fail
Status Code : 401
Headers : {WWW-Authenticate=[Basic realm="Realm", Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Length=[0], Date=[Wed, 20 Feb 2019 08:38:50 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/abac/
Request :
Response :
Logs :
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2] : URL [http://13.56.210.25/api/v1/api/v1/abac/batch]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2] : Method [POST]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2] : Request [[ {
"assertions" : [ "vaAfesuj" ],
"assertionsText" : "vaAfesuj",
"auth" : "vaAfesuj",
"authors" : [ "vaAfesuj" ],
"authorsText" : "vaAfesuj",
"autoGenerated" : false,
"category" : "NoSQL_Injection",
"cleanup" : [ "vaAfesuj" ],
"cleanupText" : "vaAfesuj",
"createdBy" : "",
"createdDate" : "",
"description" : "vaAfesuj",
"endpoint" : "vaAfesuj",
"headers" : [ "vaAfesuj" ],
"headersText" : "vaAfesuj",
"id" : "",
"inactive" : false,
"init" : [ "vaAfesuj" ],
"initText" : "vaAfesuj",
"method" : "HEAD",
"modifiedBy" : "",
"modifiedDate" : "",
"name" : "vaAfesuj",
"parent" : "vaAfesuj",
"path" : "vaAfesuj",
"policies" : {
"cleanupExec" : "vaAfesuj",
"initExec" : "vaAfesuj",
"logger" : "vaAfesuj",
"repeat" : "141617282",
"repeatDelay" : "141617282",
"repeatModule" : "vaAfesuj",
"repeatOnFailure" : "141617282",
"timeoutSeconds" : "141617282"
},
"project" : {
"createdBy" : "",
"createdDate" : "",
"id" : "",
"inactive" : false,
"modifiedBy" : "",
"modifiedDate" : "",
"name" : "vaAfesuj",
"org" : {
"createdBy" : "",
"createdDate" : "",
"id" : "",
"inactive" : false,
"modifiedBy" : "",
"modifiedDate" : "",
"name" : "vaAfesuj",
"version" : ""
},
"version" : ""
},
"props" : null,
"publishToMarketplace" : false,
"severity" : "Trivial",
"tags" : [ "vaAfesuj" ],
"tagsText" : "vaAfesuj",
"testCases" : [ {
"body" : "vaAfesuj",
"id" : "",
"inactive" : false
} ],
"type" : "Suite",
"version" : "",
"yaml" : "vaAfesuj"
} ]]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2] : Request-Headers [{Content-Type=[application/json], Accept=[application/json], Authorization=[Basic dXNlckFAZnhsYWJzLmlvOnVzZXJB]}]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2] : Response []
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2] : Response-Headers [{WWW-Authenticate=[Basic realm="Realm", Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Length=[0], Date=[Wed, 20 Feb 2019 08:38:50 GMT]}]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2] : StatusCode [401]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2] : Time [432]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2] : Size [0]
2019-02-20 08:38:50 ERROR [null] : Assertion [@StatusCode == 200 OR @StatusCode == 201] resolved-to [401 == 200 OR 401 == 201] result [Failed]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2_Headers] : Headers [{WWW-Authenticate=[Basic realm="Realm", Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Length=[0], Date=[Wed, 20 Feb 2019 08:38:50 GMT]}]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2_Headers] : Headers [{WWW-Authenticate=[Basic realm="Realm", Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Length=[0], Date=[Wed, 20 Feb 2019 08:38:50 GMT]}]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2_Headers[2]] : Headers [{WWW-Authenticate=[Basic realm="Realm", Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Length=[0], Date=[Wed, 20 Feb 2019 08:38:50 GMT]}]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2_Headers[2]] : Headers [{WWW-Authenticate=[Basic realm="Realm", Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Length=[0], Date=[Wed, 20 Feb 2019 08:38:50 GMT]}]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2] : URL [http://13.56.210.25/api/v1/api/v1/abac/]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2] : Method [DELETE]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2] : Request []
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2] : Request-Headers [{Content-Type=[application/json], Accept=[application/json], Authorization=[Basic dXNlckJAZnhsYWJzLmlvOnVzZXJC]}]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2] : Response []
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2] : Response-Headers [{WWW-Authenticate=[Basic realm="Realm", Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Length=[0], Date=[Wed, 20 Feb 2019 08:38:50 GMT]}]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2] : StatusCode [401]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2] : Time [697]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2] : Size [0]
2019-02-20 08:38:51 INFO [ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2] : Assertion [@StatusCode == 401 OR @StatusCode == 403 OR @Response.errors == true] resolved-to [401 == 401 OR 401 == 403 OR == true] result [Passed]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7AbstractAbact2] : URL [http://13.56.210.25/api/v1/api/v1/abac/]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7AbstractAbact2] : Method [DELETE]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7AbstractAbact2] : Request [null]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7AbstractAbact2] : Request-Headers [{Content-Type=[application/json], Accept=[application/json], Authorization=[Basic dXNlckFAZnhsYWJzLmlvOnVzZXJB]}]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7AbstractAbact2] : Response []
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7AbstractAbact2] : Response-Headers [{WWW-Authenticate=[Basic realm="Realm", Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Length=[0], Date=[Wed, 20 Feb 2019 08:38:51 GMT]}]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7AbstractAbact2] : StatusCode [401]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7AbstractAbact2] : Time [317]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7AbstractAbact2] : Size [0]
2019-02-20 08:38:51 ERROR [null] : Assertion [@StatusCode == 200] resolved-to [401 == 200] result [Failed]
--- FX Bot --- | 1.0 | Test : ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2 - Project : Test
Job : Default
Env : Default
Category : ABAC_Level2
Tags : [FX Top 10 - API Vulnerability, Data_Access_Control]
Severity : Major
Region : US_WEST
Result : fail
Status Code : 401
Headers : {WWW-Authenticate=[Basic realm="Realm", Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Length=[0], Date=[Wed, 20 Feb 2019 08:38:50 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/abac/
Request :
Response :
Logs :
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2] : URL [http://13.56.210.25/api/v1/api/v1/abac/batch]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2] : Method [POST]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2] : Request [[ {
"assertions" : [ "vaAfesuj" ],
"assertionsText" : "vaAfesuj",
"auth" : "vaAfesuj",
"authors" : [ "vaAfesuj" ],
"authorsText" : "vaAfesuj",
"autoGenerated" : false,
"category" : "NoSQL_Injection",
"cleanup" : [ "vaAfesuj" ],
"cleanupText" : "vaAfesuj",
"createdBy" : "",
"createdDate" : "",
"description" : "vaAfesuj",
"endpoint" : "vaAfesuj",
"headers" : [ "vaAfesuj" ],
"headersText" : "vaAfesuj",
"id" : "",
"inactive" : false,
"init" : [ "vaAfesuj" ],
"initText" : "vaAfesuj",
"method" : "HEAD",
"modifiedBy" : "",
"modifiedDate" : "",
"name" : "vaAfesuj",
"parent" : "vaAfesuj",
"path" : "vaAfesuj",
"policies" : {
"cleanupExec" : "vaAfesuj",
"initExec" : "vaAfesuj",
"logger" : "vaAfesuj",
"repeat" : "141617282",
"repeatDelay" : "141617282",
"repeatModule" : "vaAfesuj",
"repeatOnFailure" : "141617282",
"timeoutSeconds" : "141617282"
},
"project" : {
"createdBy" : "",
"createdDate" : "",
"id" : "",
"inactive" : false,
"modifiedBy" : "",
"modifiedDate" : "",
"name" : "vaAfesuj",
"org" : {
"createdBy" : "",
"createdDate" : "",
"id" : "",
"inactive" : false,
"modifiedBy" : "",
"modifiedDate" : "",
"name" : "vaAfesuj",
"version" : ""
},
"version" : ""
},
"props" : null,
"publishToMarketplace" : false,
"severity" : "Trivial",
"tags" : [ "vaAfesuj" ],
"tagsText" : "vaAfesuj",
"testCases" : [ {
"body" : "vaAfesuj",
"id" : "",
"inactive" : false
} ],
"type" : "Suite",
"version" : "",
"yaml" : "vaAfesuj"
} ]]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2] : Request-Headers [{Content-Type=[application/json], Accept=[application/json], Authorization=[Basic dXNlckFAZnhsYWJzLmlvOnVzZXJB]}]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2] : Response []
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2] : Response-Headers [{WWW-Authenticate=[Basic realm="Realm", Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Length=[0], Date=[Wed, 20 Feb 2019 08:38:50 GMT]}]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2] : StatusCode [401]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2] : Time [432]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2] : Size [0]
2019-02-20 08:38:50 ERROR [null] : Assertion [@StatusCode == 200 OR @StatusCode == 201] resolved-to [401 == 200 OR 401 == 201] result [Failed]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2_Headers] : Headers [{WWW-Authenticate=[Basic realm="Realm", Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Length=[0], Date=[Wed, 20 Feb 2019 08:38:50 GMT]}]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2_Headers] : Headers [{WWW-Authenticate=[Basic realm="Realm", Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Length=[0], Date=[Wed, 20 Feb 2019 08:38:50 GMT]}]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2_Headers[2]] : Headers [{WWW-Authenticate=[Basic realm="Realm", Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Length=[0], Date=[Wed, 20 Feb 2019 08:38:50 GMT]}]
2019-02-20 08:38:50 DEBUG [BatchCategoryAbacLevel7CreateUserAInitAbact2_Headers[2]] : Headers [{WWW-Authenticate=[Basic realm="Realm", Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Length=[0], Date=[Wed, 20 Feb 2019 08:38:50 GMT]}]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2] : URL [http://13.56.210.25/api/v1/api/v1/abac/]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2] : Method [DELETE]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2] : Request []
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2] : Request-Headers [{Content-Type=[application/json], Accept=[application/json], Authorization=[Basic dXNlckJAZnhsYWJzLmlvOnVzZXJC]}]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2] : Response []
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2] : Response-Headers [{WWW-Authenticate=[Basic realm="Realm", Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Length=[0], Date=[Wed, 20 Feb 2019 08:38:50 GMT]}]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2] : StatusCode [401]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2] : Time [697]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2] : Size [0]
2019-02-20 08:38:51 INFO [ApiV1AbacIdDeleteBatchcategoryabaclevel7UserbDisallowAbact2] : Assertion [@StatusCode == 401 OR @StatusCode == 403 OR @Response.errors == true] resolved-to [401 == 401 OR 401 == 403 OR == true] result [Passed]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7AbstractAbact2] : URL [http://13.56.210.25/api/v1/api/v1/abac/]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7AbstractAbact2] : Method [DELETE]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7AbstractAbact2] : Request [null]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7AbstractAbact2] : Request-Headers [{Content-Type=[application/json], Accept=[application/json], Authorization=[Basic dXNlckFAZnhsYWJzLmlvOnVzZXJB]}]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7AbstractAbact2] : Response []
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7AbstractAbact2] : Response-Headers [{WWW-Authenticate=[Basic realm="Realm", Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Length=[0], Date=[Wed, 20 Feb 2019 08:38:51 GMT]}]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7AbstractAbact2] : StatusCode [401]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7AbstractAbact2] : Time [317]
2019-02-20 08:38:51 DEBUG [ApiV1AbacIdDeleteBatchcategoryabaclevel7AbstractAbact2] : Size [0]
2019-02-20 08:38:51 ERROR [null] : Assertion [@StatusCode == 200] resolved-to [401 == 200] result [Failed]
--- FX Bot --- | test | test project test job default env default category abac tags severity major region us west result fail status code headers www authenticate x content type options x xss protection cache control pragma expires x frame options content length date endpoint request response logs debug url debug method debug request assertions assertionstext vaafesuj auth vaafesuj authors authorstext vaafesuj autogenerated false category nosql injection cleanup cleanuptext vaafesuj createdby createddate description vaafesuj endpoint vaafesuj headers headerstext vaafesuj id inactive false init inittext vaafesuj method head modifiedby modifieddate name vaafesuj parent vaafesuj path vaafesuj policies cleanupexec vaafesuj initexec vaafesuj logger vaafesuj repeat repeatdelay repeatmodule vaafesuj repeatonfailure timeoutseconds project createdby createddate id inactive false modifiedby modifieddate name vaafesuj org createdby createddate id inactive false modifiedby modifieddate name vaafesuj version version props null publishtomarketplace false severity trivial tags tagstext vaafesuj testcases body vaafesuj id inactive false type suite version yaml vaafesuj debug request headers accept authorization debug response debug response headers x content type options x xss protection cache control pragma expires x frame options content length date debug statuscode debug time debug size error assertion resolved to result debug headers x content type options x xss protection cache control pragma expires x frame options content length date debug headers x content type options x xss protection cache control pragma expires x frame options content length date debug headers x content type options x xss protection cache control pragma expires x frame options content length date debug headers x content type options x xss protection cache control pragma expires x frame options content length date debug url debug method debug request debug request headers accept authorization debug response debug response headers x content type options x xss protection cache control pragma expires x frame options content length date debug statuscode debug time debug size info assertion resolved to result debug url debug method debug request debug request headers accept authorization debug response debug response headers x content type options x xss protection cache control pragma expires x frame options content length date debug statuscode debug time debug size error assertion resolved to result fx bot | 1 |
25,578 | 4,396,587,779 | IssuesEvent | 2016-08-10 03:07:31 | NREL/EnergyPlus | https://api.github.com/repos/NREL/EnergyPlus | closed | Movable Insulation Not Affecting LW Radiation Exchange Between Surfaces | Defect EnergyPlus | Issue overview
--------------
In working with another issue in movable insulation, it was discovered that the current code affects the interior thermal absorption correctly for radiation from internal gains after a recent fix. However, upon testing, it was discovered that when using the test suite test case for interior movable insulation that the results did not change when the movable insulation absorptivity was changed. Upon further review, it appears that the interior radiant exchange algorithm does not look at the movable insulation absorptivity when it establishes emissivity at all. The interior radiant exchange algorithm does its initial calculations based on the base surface and never updates this. Updating is done for blinds and shades on the interior side, but a similar updating is not done for movable insulation. This needs to be corrected.
### Details
Some additional details for this issue (if relevant):
Happens in the current version of EnergyPlus (V8.5)
### Checklist
Add to this list or remove from it as applicable. This is a simple templated set of guidelines.
- [ x ] Defect file added (no additional file needed--existing interior movable insulation file in the test suite will show the error if one run is done with the file as is and one is done with a modified absorptivity for the movable insulation layer--those two files should produce different outputs and currently they do not)
- [ x ] Ticket added to Pivotal for defect (development team task) | 1.0 | Movable Insulation Not Affecting LW Radiation Exchange Between Surfaces - Issue overview
--------------
In working with another issue in movable insulation, it was discovered that the current code affects the interior thermal absorption correctly for radiation from internal gains after a recent fix. However, upon testing, it was discovered that when using the test suite test case for interior movable insulation that the results did not change when the movable insulation absorptivity was changed. Upon further review, it appears that the interior radiant exchange algorithm does not look at the movable insulation absorptivity when it establishes emissivity at all. The interior radiant exchange algorithm does its initial calculations based on the base surface and never updates this. Updating is done for blinds and shades on the interior side, but a similar updating is not done for movable insulation. This needs to be corrected.
### Details
Some additional details for this issue (if relevant):
Happens in the current version of EnergyPlus (V8.5)
### Checklist
Add to this list or remove from it as applicable. This is a simple templated set of guidelines.
- [ x ] Defect file added (no additional file needed--existing interior movable insulation file in the test suite will show the error if one run is done with the file as is and one is done with a modified absorptivity for the movable insulation layer--those two files should produce different outputs and currently they do not)
- [ x ] Ticket added to Pivotal for defect (development team task) | non_test | movable insulation not affecting lw radiation exchange between surfaces issue overview in working with another issue in movable insulation it was discovered that the current code affects the interior thermal absorption correctly for radiation from internal gains after a recent fix however upon testing it was discovered that when using the test suite test case for interior movable insulation that the results did not change when the movable insulation absorptivity was changed upon further review it appears that the interior radiant exchange algorithm does not look at the movable insulation absorptivity when it establishes emissivity at all the interior radiant exchange algorithm does its initial calculations based on the base surface and never updates this updating is done for blinds and shades on the interior side but a similar updating is not done for movable insulation this needs to be corrected details some additional details for this issue if relevant happens in the current version of energyplus checklist add to this list or remove from it as applicable this is a simple templated set of guidelines defect file added no additional file needed existing interior movable insulation file in the test suite will show the error if one run is done with the file as is and one is done with a modified absorptivity for the movable insulation layer those two files should produce different outputs and currently they do not ticket added to pivotal for defect development team task | 0 |
131,309 | 27,871,566,384 | IssuesEvent | 2023-03-21 13:46:59 | trezor/trezor-suite | https://api.github.com/repos/trezor/trezor-suite | closed | Optimise blockfilters (coinjoin) discovery process | code coinjoin | discovery of [vpub5Yme8...Q3CTZM9](https://tbtc1.trezor.io/xpub/vpub5Yme8cvVDuECgS5vuY8rYyVMrnSvDaUwbDeKLNhh3BKZYe3fpKKapVQUFAEVpyBbwaUhZLeZLcwcoRMweSfRtFxB6MenWh3NweXrQ3CTZM9) (~600k blocks, ~540 txs) over Tor now takes approx. 43 minutes
- filters could be fetched faster, independently on blocks/transactions
- remove the need of fetching txs by two requests (block + every relevant tx in it)
- fetch all mempool txs with one request (from coordinator, not blockbook)
- store fetched filters for later usage (e.g. discovering another account) | 1.0 | Optimise blockfilters (coinjoin) discovery process - discovery of [vpub5Yme8...Q3CTZM9](https://tbtc1.trezor.io/xpub/vpub5Yme8cvVDuECgS5vuY8rYyVMrnSvDaUwbDeKLNhh3BKZYe3fpKKapVQUFAEVpyBbwaUhZLeZLcwcoRMweSfRtFxB6MenWh3NweXrQ3CTZM9) (~600k blocks, ~540 txs) over Tor now takes approx. 43 minutes
- filters could be fetched faster, independently on blocks/transactions
- remove the need of fetching txs by two requests (block + every relevant tx in it)
- fetch all mempool txs with one request (from coordinator, not blockbook)
- store fetched filters for later usage (e.g. discovering another account) | non_test | optimise blockfilters coinjoin discovery process discovery of blocks txs over tor now takes approx minutes filters could be fetched faster independently on blocks transactions remove the need of fetching txs by two requests block every relevant tx in it fetch all mempool txs with one request from coordinator not blockbook store fetched filters for later usage e g discovering another account | 0 |
189,579 | 14,514,777,512 | IssuesEvent | 2020-12-13 09:49:01 | submariner-io/submariner | https://api.github.com/repos/submariner-io/submariner | closed | CI test failure debug: GlobalNet connectivity - From Netshoot pod To Nginx service by its Global IP: | QE testing | Testing GlobalNet connectivity - From Netshoot pod netshoot-cl-a (IP 169.254.5.30) on cluster A
To Nginx service on cluster B, by its Global IP:
curl: (28) Connection timed out after 30000 milliseconds
command terminated with exit code 28
from this job : https://qe-jenkins-csb-skynet.cloud.paas.psi.redhat.com/job/Submariner-OSP-AWS-Globalnet/37/Test-Report/
I dont see the service cluster ip actually :
[r@r20 submariner_ci]$ kubectl get service --all-namespaces|grep 8080
openshift-monitoring cluster-monitoring-operator ClusterIP None <none> 8080/TCP 28d
openshift-monitoring prometheus-operator ClusterIP None <none> 8080/TCP 28d
submariner-operator submariner-engine-metrics ClusterIP 100.96.115.107 <none> 8080/TCP 28h
test-submariner-headless nginx-cl-b ClusterIP None <none> 8080/TCP 4h9m
test-submariner nginx-cl-b ClusterIP 100.96.13.240 <none> 8080/TCP 4h19m
pkomarov 4 minutes ago
supposed to be 169.254.33.173, | 1.0 | CI test failure debug: GlobalNet connectivity - From Netshoot pod To Nginx service by its Global IP: - Testing GlobalNet connectivity - From Netshoot pod netshoot-cl-a (IP 169.254.5.30) on cluster A
To Nginx service on cluster B, by its Global IP:
curl: (28) Connection timed out after 30000 milliseconds
command terminated with exit code 28
from this job : https://qe-jenkins-csb-skynet.cloud.paas.psi.redhat.com/job/Submariner-OSP-AWS-Globalnet/37/Test-Report/
I dont see the service cluster ip actually :
[r@r20 submariner_ci]$ kubectl get service --all-namespaces|grep 8080
openshift-monitoring cluster-monitoring-operator ClusterIP None <none> 8080/TCP 28d
openshift-monitoring prometheus-operator ClusterIP None <none> 8080/TCP 28d
submariner-operator submariner-engine-metrics ClusterIP 100.96.115.107 <none> 8080/TCP 28h
test-submariner-headless nginx-cl-b ClusterIP None <none> 8080/TCP 4h9m
test-submariner nginx-cl-b ClusterIP 100.96.13.240 <none> 8080/TCP 4h19m
pkomarov 4 minutes ago
supposed to be 169.254.33.173, | test | ci test failure debug globalnet connectivity from netshoot pod to nginx service by its global ip testing globalnet connectivity from netshoot pod netshoot cl a ip on cluster a to nginx service on cluster b by its global ip curl connection timed out after milliseconds command terminated with exit code from this job i dont see the service cluster ip actually kubectl get service all namespaces grep openshift monitoring cluster monitoring operator clusterip none tcp openshift monitoring prometheus operator clusterip none tcp submariner operator submariner engine metrics clusterip tcp test submariner headless nginx cl b clusterip none tcp test submariner nginx cl b clusterip tcp pkomarov minutes ago supposed to be | 1 |
28,403 | 4,396,216,563 | IssuesEvent | 2016-08-10 00:45:18 | Homebrew/ruby-macho | https://api.github.com/repos/Homebrew/ruby-macho | opened | Expanding Makefile/build system to create inconsistent fat binaries | question test-suite | I'm currently looking at the [Makefile](https://github.com/Homebrew/ruby-macho/blob/master/test/src/Makefile) to see what our best approach is to creating inconsistent fat binaries (i.e., the kind that will trigger the new behavior in #55).
In order to `lipo` together two inconsistent binaries of different architectures, we need a fat-only target that can generically depend on two single-arch-only targets. That's not possible with the current layout of the `Makefile`, and probably won't be without some significant changes.
For the time being, it might be worthwhile to externalize this process to a shell script, one that's called by the makefile at the very end of the `all:` chain. With a few minor tweaks, I can provide that script with the information it needs to access the correct single-arch directories and drop the `lipo`'d results in the correct fat-arch directories. | 1.0 | Expanding Makefile/build system to create inconsistent fat binaries - I'm currently looking at the [Makefile](https://github.com/Homebrew/ruby-macho/blob/master/test/src/Makefile) to see what our best approach is to creating inconsistent fat binaries (i.e., the kind that will trigger the new behavior in #55).
In order to `lipo` together two inconsistent binaries of different architectures, we need a fat-only target that can generically depend on two single-arch-only targets. That's not possible with the current layout of the `Makefile`, and probably won't be without some significant changes.
For the time being, it might be worthwhile to externalize this process to a shell script, one that's called by the makefile at the very end of the `all:` chain. With a few minor tweaks, I can provide that script with the information it needs to access the correct single-arch directories and drop the `lipo`'d results in the correct fat-arch directories. | test | expanding makefile build system to create inconsistent fat binaries i m currently looking at the to see what our best approach is to creating inconsistent fat binaries i e the kind that will trigger the new behavior in in order to lipo together two inconsistent binaries of different architectures we need a fat only target that can generically depend on two single arch only targets that s not possible with the current layout of the makefile and probably won t be without some significant changes for the time being it might be worthwhile to externalize this process to a shell script one that s called by the makefile at the very end of the all chain with a few minor tweaks i can provide that script with the information it needs to access the correct single arch directories and drop the lipo d results in the correct fat arch directories | 1 |
91,704 | 8,317,007,855 | IssuesEvent | 2018-09-25 10:42:34 | shahkhan40/shantestrep | https://api.github.com/repos/shahkhan40/shantestrep | opened | prepodtestproject : ApiV1SkillsType@randomGetOtherRbac | prepodtestproject | Project : prepodtestproject
Job : uatpreprod
Env : uatpreprod
Region : FXLabs/US_WEST_1
Result : fail
Status Code : 401
Headers : {WWW-Authenticate=[Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Tue, 25 Sep 2018 10:42:31 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/skills/type/F8lbbf8N
Request :
Response :
{
"timestamp" : "2018-09-25T10:42:32.170+0000",
"status" : 401,
"error" : "Unauthorized",
"message" : "Unauthorized",
"path" : "/api/v1/api/v1/skills/type/F8lbbf8N"
}
Logs :
Assertion [@StatusCode == 403] resolved-to [401 == 403] result [Failed]
--- FX Bot --- | 1.0 | prepodtestproject : ApiV1SkillsType@randomGetOtherRbac - Project : prepodtestproject
Job : uatpreprod
Env : uatpreprod
Region : FXLabs/US_WEST_1
Result : fail
Status Code : 401
Headers : {WWW-Authenticate=[Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Tue, 25 Sep 2018 10:42:31 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/skills/type/F8lbbf8N
Request :
Response :
{
"timestamp" : "2018-09-25T10:42:32.170+0000",
"status" : 401,
"error" : "Unauthorized",
"message" : "Unauthorized",
"path" : "/api/v1/api/v1/skills/type/F8lbbf8N"
}
Logs :
Assertion [@StatusCode == 403] resolved-to [401 == 403] result [Failed]
--- FX Bot --- | test | prepodtestproject randomgetotherrbac project prepodtestproject job uatpreprod env uatpreprod region fxlabs us west result fail status code headers www authenticate x content type options x xss protection cache control pragma expires x frame options content type transfer encoding date endpoint request response timestamp status error unauthorized message unauthorized path api api skills type logs assertion resolved to result fx bot | 1 |
350,065 | 31,849,848,303 | IssuesEvent | 2023-09-15 00:03:00 | WordPress/gutenberg | https://api.github.com/repos/WordPress/gutenberg | closed | [Flaky Test] does not show group option in the options toolbar if Grouping block is disabled | [Status] Stale [Type] Flaky Test | <!-- __META_DATA__:{} -->
**Flaky test detected. This is an auto-generated issue by GitHub Actions. Please do NOT edit this manually.**
## Test title
does not show group option in the options toolbar if Grouping block is disabled
## Test path
`specs/editor/various/block-grouping.test.js`
## Errors
<!-- __TEST_RESULTS_LIST__ -->
<!-- __TEST_RESULT__ --><time datetime="2023-03-07T12:01:51.727Z"><code>[2023-03-07T12:01:51.727Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4353563197"><code>try/dedicated-block-controls-filter</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-05-10T11:51:59.498Z"><code>[2023-05-10T11:51:59.498Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4936273823"><code>add/inserter-sorting</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-05-11T11:11:30.347Z"><code>[2023-05-11T11:11:30.347Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4946242913"><code>add/inserter-sorting</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-05-11T12:57:13.696Z"><code>[2023-05-11T12:57:13.696Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4946242913"><code>add/inserter-sorting</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-06-15T06:30:29.605Z"><code>[2023-06-15T06:30:29.605Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/5265161903"><code>add/back-to-top</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><details>
<summary>
<time datetime="2023-08-14T18:45:44.786Z"><code>[2023-08-14T18:45:44.786Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/5855815793"><code>feat/async-block-loading</code></a>.
</summary>
```
● Block Grouping › Grouping Block availability › does not show group option in the options toolbar if Grouping block is disabled
Node is detached from document
at ElementHandle._scrollIntoViewIfNeeded (../../node_modules/puppeteer-core/src/common/JSHandle.ts:477:22)
at runMicrotasks (<anonymous>)
at ElementHandle.click (../../node_modules/puppeteer-core/src/common/JSHandle.ts:619:5)
at insertFromGlobalInserter (../e2e-test-utils/build/@wordpress/e2e-test-utils/src/inserter.js:260:2)
at insertBlock (../e2e-test-utils/build/@wordpress/e2e-test-utils/src/inserter.js:330:2)
at insertBlocksOfMultipleTypes (specs/editor/various/block-grouping.test.js:32:2)
at Object.<anonymous> (specs/editor/various/block-grouping.test.js:172:4)
```
</details><!-- /__TEST_RESULT__ -->
<!-- /__TEST_RESULTS_LIST__ -->
| 1.0 | [Flaky Test] does not show group option in the options toolbar if Grouping block is disabled - <!-- __META_DATA__:{} -->
**Flaky test detected. This is an auto-generated issue by GitHub Actions. Please do NOT edit this manually.**
## Test title
does not show group option in the options toolbar if Grouping block is disabled
## Test path
`specs/editor/various/block-grouping.test.js`
## Errors
<!-- __TEST_RESULTS_LIST__ -->
<!-- __TEST_RESULT__ --><time datetime="2023-03-07T12:01:51.727Z"><code>[2023-03-07T12:01:51.727Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4353563197"><code>try/dedicated-block-controls-filter</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-05-10T11:51:59.498Z"><code>[2023-05-10T11:51:59.498Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4936273823"><code>add/inserter-sorting</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-05-11T11:11:30.347Z"><code>[2023-05-11T11:11:30.347Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4946242913"><code>add/inserter-sorting</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-05-11T12:57:13.696Z"><code>[2023-05-11T12:57:13.696Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/4946242913"><code>add/inserter-sorting</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><time datetime="2023-06-15T06:30:29.605Z"><code>[2023-06-15T06:30:29.605Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/5265161903"><code>add/back-to-top</code></a>.<!-- /__TEST_RESULT__ -->
<br/>
<!-- __TEST_RESULT__ --><details>
<summary>
<time datetime="2023-08-14T18:45:44.786Z"><code>[2023-08-14T18:45:44.786Z]</code></time> Test passed after 1 failed attempt on <a href="https://github.com/WordPress/gutenberg/actions/runs/5855815793"><code>feat/async-block-loading</code></a>.
</summary>
```
● Block Grouping › Grouping Block availability › does not show group option in the options toolbar if Grouping block is disabled
Node is detached from document
at ElementHandle._scrollIntoViewIfNeeded (../../node_modules/puppeteer-core/src/common/JSHandle.ts:477:22)
at runMicrotasks (<anonymous>)
at ElementHandle.click (../../node_modules/puppeteer-core/src/common/JSHandle.ts:619:5)
at insertFromGlobalInserter (../e2e-test-utils/build/@wordpress/e2e-test-utils/src/inserter.js:260:2)
at insertBlock (../e2e-test-utils/build/@wordpress/e2e-test-utils/src/inserter.js:330:2)
at insertBlocksOfMultipleTypes (specs/editor/various/block-grouping.test.js:32:2)
at Object.<anonymous> (specs/editor/various/block-grouping.test.js:172:4)
```
</details><!-- /__TEST_RESULT__ -->
<!-- /__TEST_RESULTS_LIST__ -->
| test | does not show group option in the options toolbar if grouping block is disabled flaky test detected this is an auto generated issue by github actions please do not edit this manually test title does not show group option in the options toolbar if grouping block is disabled test path specs editor various block grouping test js errors test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on test passed after failed attempt on a href ● block grouping › grouping block availability › does not show group option in the options toolbar if grouping block is disabled node is detached from document at elementhandle scrollintoviewifneeded node modules puppeteer core src common jshandle ts at runmicrotasks at elementhandle click node modules puppeteer core src common jshandle ts at insertfromglobalinserter test utils build wordpress test utils src inserter js at insertblock test utils build wordpress test utils src inserter js at insertblocksofmultipletypes specs editor various block grouping test js at object specs editor various block grouping test js | 1 |
632,220 | 20,187,569,647 | IssuesEvent | 2022-02-11 00:25:42 | lowRISC/opentitan | https://api.github.com/repos/lowRISC/opentitan | closed | [kmac] fatal and recoverable alerts seem to be mixed up | Priority:P1 Type:Bug Component:RTL IP:kmac Milestone:D2S | While having a look at KMAC it seems like the fatal and recoverable alerts got mixed up in https://github.com/lowRISC/opentitan/pull/7439
In [kmac.sv lines 1131-1163](https://github.com/eunchan/opentitan/blob/78b1e671fcabb21a64ccbd57986716273928b6b2/hw/ip/kmac/rtl/kmac.sv#L1131-L1163) it states:
```
assign alert_test = {
reg2hw.alert_test.recov_operation_err.q
& reg2hw.alert_test.recov_operation_err.qe, // [1]
reg2hw.alert_test.fatal_fault_err.q
& reg2hw.alert_test.fatal_fault_err.qe // [0]
};
assign alerts = {
alert_recov_operation, // Alerts[1]
alert_fatal // Alerts[0]
};
assign alert_recov_operation = shadowed_update_err;
assign alert_fatal = shadowed_storage_err
| alert_intg_err
;
for (genvar i = 0; i < NumAlerts; i++) begin : gen_alert_tx
prim_alert_sender #(
.AsyncOn(AlertAsyncOn[i]),
.IsFatal(i)
) u_prim_alert_sender (
.clk_i,
.rst_ni,
.alert_test_i ( alert_test[i] ),
.alert_req_i ( alerts[i] ),
.alert_ack_o ( ),
.alert_state_o ( ),
.alert_rx_i ( alert_rx_i[i] ),
.alert_tx_o ( alert_tx_o[i] )
);
end
```
`IsFatal(i)` is true for `i=1`, but the fatal alert is declared to be `[0]`. Do I miss here something related to vector and arrays?
Anyways, if in doubt, this should be rewritten in a more intuitive way | 1.0 | [kmac] fatal and recoverable alerts seem to be mixed up - While having a look at KMAC it seems like the fatal and recoverable alerts got mixed up in https://github.com/lowRISC/opentitan/pull/7439
In [kmac.sv lines 1131-1163](https://github.com/eunchan/opentitan/blob/78b1e671fcabb21a64ccbd57986716273928b6b2/hw/ip/kmac/rtl/kmac.sv#L1131-L1163) it states:
```
assign alert_test = {
reg2hw.alert_test.recov_operation_err.q
& reg2hw.alert_test.recov_operation_err.qe, // [1]
reg2hw.alert_test.fatal_fault_err.q
& reg2hw.alert_test.fatal_fault_err.qe // [0]
};
assign alerts = {
alert_recov_operation, // Alerts[1]
alert_fatal // Alerts[0]
};
assign alert_recov_operation = shadowed_update_err;
assign alert_fatal = shadowed_storage_err
| alert_intg_err
;
for (genvar i = 0; i < NumAlerts; i++) begin : gen_alert_tx
prim_alert_sender #(
.AsyncOn(AlertAsyncOn[i]),
.IsFatal(i)
) u_prim_alert_sender (
.clk_i,
.rst_ni,
.alert_test_i ( alert_test[i] ),
.alert_req_i ( alerts[i] ),
.alert_ack_o ( ),
.alert_state_o ( ),
.alert_rx_i ( alert_rx_i[i] ),
.alert_tx_o ( alert_tx_o[i] )
);
end
```
`IsFatal(i)` is true for `i=1`, but the fatal alert is declared to be `[0]`. Do I miss here something related to vector and arrays?
Anyways, if in doubt, this should be rewritten in a more intuitive way | non_test | fatal and recoverable alerts seem to be mixed up while having a look at kmac it seems like the fatal and recoverable alerts got mixed up in in it states assign alert test alert test recov operation err q alert test recov operation err qe alert test fatal fault err q alert test fatal fault err qe assign alerts alert recov operation alerts alert fatal alerts assign alert recov operation shadowed update err assign alert fatal shadowed storage err alert intg err for genvar i i numalerts i begin gen alert tx prim alert sender asyncon alertasyncon isfatal i u prim alert sender clk i rst ni alert test i alert test alert req i alerts alert ack o alert state o alert rx i alert rx i alert tx o alert tx o end isfatal i is true for i but the fatal alert is declared to be do i miss here something related to vector and arrays anyways if in doubt this should be rewritten in a more intuitive way | 0 |
144,067 | 13,095,006,280 | IssuesEvent | 2020-08-03 13:25:55 | hyperspy/hyperspy | https://api.github.com/repos/hyperspy/hyperspy | closed | Ambiguity on "Power Law" vs "Powerlaw" | affects: documentation release: next patch type: bug | `s.remove_background` takes the `background_type="Power Law"` argument and default value. However, its docstring suggests that "PowerLaw" is correct, and the _model_ docs ([model](http://hyperspy.org/hyperspy-doc/current/user_guide/model.html) and [eels](http://hyperspy.org/hyperspy-doc/current/user_guide/eels.html)) refer to `PowerLaw` not `Power Law` in both component and attribute names.
This is confusing, particularly so for new users, so i suggest we change it to be consistent. "Power Law" is the only component that includes a space in its name, so unless anyone feels strongly about it, I suggest we make it "PowerLaw", not "Power Law". | 1.0 | Ambiguity on "Power Law" vs "Powerlaw" - `s.remove_background` takes the `background_type="Power Law"` argument and default value. However, its docstring suggests that "PowerLaw" is correct, and the _model_ docs ([model](http://hyperspy.org/hyperspy-doc/current/user_guide/model.html) and [eels](http://hyperspy.org/hyperspy-doc/current/user_guide/eels.html)) refer to `PowerLaw` not `Power Law` in both component and attribute names.
This is confusing, particularly so for new users, so i suggest we change it to be consistent. "Power Law" is the only component that includes a space in its name, so unless anyone feels strongly about it, I suggest we make it "PowerLaw", not "Power Law". | non_test | ambiguity on power law vs powerlaw s remove background takes the background type power law argument and default value however its docstring suggests that powerlaw is correct and the model docs and refer to powerlaw not power law in both component and attribute names this is confusing particularly so for new users so i suggest we change it to be consistent power law is the only component that includes a space in its name so unless anyone feels strongly about it i suggest we make it powerlaw not power law | 0 |
281,434 | 24,392,691,623 | IssuesEvent | 2022-10-04 16:26:19 | MTES-MCT/histologe | https://api.github.com/repos/MTES-MCT/histologe | closed | [BO - Stats] Revoir les stats territoire | A tester Feedback Stats / carto | En tant qu'utilisateur du BO, je veux pouvoir afficher les statistiques sur les signalements en fonction de mon rôle.
[Détails sur le wiki](https://github.com/MTES-MCT/histologe/wiki/Statistiques)
[Maquette dispo ici](https://xd.adobe.com/view/5d841ce9-b073-4721-95b8-1ea0d318a576-08d7/) | 1.0 | [BO - Stats] Revoir les stats territoire - En tant qu'utilisateur du BO, je veux pouvoir afficher les statistiques sur les signalements en fonction de mon rôle.
[Détails sur le wiki](https://github.com/MTES-MCT/histologe/wiki/Statistiques)
[Maquette dispo ici](https://xd.adobe.com/view/5d841ce9-b073-4721-95b8-1ea0d318a576-08d7/) | test | revoir les stats territoire en tant qu utilisateur du bo je veux pouvoir afficher les statistiques sur les signalements en fonction de mon rôle | 1 |
450,083 | 12,980,050,294 | IssuesEvent | 2020-07-22 04:01:03 | a2000-erp-team/WEBERP | https://api.github.com/repos/a2000-erp-team/WEBERP | opened | A2000ERP Login Page - [When a POS user login credential is entered, it should direct the page to POS directly instead of manually go to Sales menu and go to POS sub-menu to login again.] | ADRIAN High Priority | 
102. When a POS user login credential is entered, it should direct the page to POS directly instead of manually go to Sales menu and go to POS sub-menu to login again. | 1.0 | A2000ERP Login Page - [When a POS user login credential is entered, it should direct the page to POS directly instead of manually go to Sales menu and go to POS sub-menu to login again.] - 
102. When a POS user login credential is entered, it should direct the page to POS directly instead of manually go to Sales menu and go to POS sub-menu to login again. | non_test | login page when a pos user login credential is entered it should direct the page to pos directly instead of manually go to sales menu and go to pos sub menu to login again | 0 |
333,107 | 29,508,136,242 | IssuesEvent | 2023-06-03 15:19:47 | kiransingh99/gurbani_analysis | https://api.github.com/repos/kiransingh99/gurbani_analysis | closed | Fix copyright check | bug good first issue test | It shouldn't force which month is in the notice. Just give a regex choice of all 12 months | 1.0 | Fix copyright check - It shouldn't force which month is in the notice. Just give a regex choice of all 12 months | test | fix copyright check it shouldn t force which month is in the notice just give a regex choice of all months | 1 |
490,172 | 14,116,309,575 | IssuesEvent | 2020-11-08 02:14:18 | formium/formik | https://api.github.com/repos/formium/formik | closed | Form Validation onChange not working on v2.2.2 | Priority: High Type: Bug | ## 🐛 Bug report
### Current Behavior
Form not validating on change, instead it only validates on blur. Even with the validateOnChange prop.
### Expected behavior
Fields should be validating on change
### Reproducible example
CodeSandbox link: https://codesandbox.io/s/frosty-mountain-tyifi?file=/src/index.js
### Additional context
This is only occurring on v2.2.2, I have tested with v2.2.1 and it does correctly validate on change on the older version.
Using Yup for validation.
### Your environment
| Software | Version(s) |
| ---------------- | ---------- |
| Formik | 2.2.2
| React | 17.0.0
| 1.0 | Form Validation onChange not working on v2.2.2 - ## 🐛 Bug report
### Current Behavior
Form not validating on change, instead it only validates on blur. Even with the validateOnChange prop.
### Expected behavior
Fields should be validating on change
### Reproducible example
CodeSandbox link: https://codesandbox.io/s/frosty-mountain-tyifi?file=/src/index.js
### Additional context
This is only occurring on v2.2.2, I have tested with v2.2.1 and it does correctly validate on change on the older version.
Using Yup for validation.
### Your environment
| Software | Version(s) |
| ---------------- | ---------- |
| Formik | 2.2.2
| React | 17.0.0
| non_test | form validation onchange not working on 🐛 bug report current behavior form not validating on change instead it only validates on blur even with the validateonchange prop expected behavior fields should be validating on change reproducible example codesandbox link additional context this is only occurring on i have tested with and it does correctly validate on change on the older version using yup for validation your environment software version s formik react | 0 |
22,210 | 11,518,669,292 | IssuesEvent | 2020-02-14 11:00:20 | DivanteLtd/vsf-capybara | https://api.github.com/repos/DivanteLtd/vsf-capybara | closed | Add WEBP support for static images on home page | Performance | ## What is the motivation for adding/enhancing this feature?
This main problem returned by Google Page Speed tool on home page. By adding .webp support for these images we can improve page loading speed.
## What are the acceptance criteria?
- [ ] Static images on the home page should be served in .webp format
- [ ] There should be support for browsers which not support .webp images
## Can you complete this feature request by yourself?
- [x] YES
- [ ] NO
## Additional information
Related #104
| True | Add WEBP support for static images on home page - ## What is the motivation for adding/enhancing this feature?
This main problem returned by Google Page Speed tool on home page. By adding .webp support for these images we can improve page loading speed.
## What are the acceptance criteria?
- [ ] Static images on the home page should be served in .webp format
- [ ] There should be support for browsers which not support .webp images
## Can you complete this feature request by yourself?
- [x] YES
- [ ] NO
## Additional information
Related #104
| non_test | add webp support for static images on home page what is the motivation for adding enhancing this feature this main problem returned by google page speed tool on home page by adding webp support for these images we can improve page loading speed what are the acceptance criteria static images on the home page should be served in webp format there should be support for browsers which not support webp images can you complete this feature request by yourself yes no additional information related | 0 |
15,426 | 5,961,084,632 | IssuesEvent | 2017-05-29 15:59:00 | neocotic/qrious | https://api.github.com/repos/neocotic/qrious | opened | Drop support for Node.js < 4 | build documentation | The current build contains unnecessary complexity as it tries to support Node.js 0.10 and 0.12 to some degree. I'd like to drop that support and simplify our build and contributor guidelines in the progress. | 1.0 | Drop support for Node.js < 4 - The current build contains unnecessary complexity as it tries to support Node.js 0.10 and 0.12 to some degree. I'd like to drop that support and simplify our build and contributor guidelines in the progress. | non_test | drop support for node js the current build contains unnecessary complexity as it tries to support node js and to some degree i d like to drop that support and simplify our build and contributor guidelines in the progress | 0 |
107,012 | 23,329,997,729 | IssuesEvent | 2022-08-09 03:31:11 | apache/incubator-eventmesh | https://api.github.com/repos/apache/incubator-eventmesh | closed | QuickStart is not quick | documentation enhancement help wanted summer of code | When a newbie reaches to EventMesh, it is difficult to quick start from the scratch. I would like to be a such man to try to experience the optimized document. Please opt here:-)
| 1.0 | QuickStart is not quick - When a newbie reaches to EventMesh, it is difficult to quick start from the scratch. I would like to be a such man to try to experience the optimized document. Please opt here:-)
| non_test | quickstart is not quick when a newbie reaches to eventmesh it is difficult to quick start from the scratch i would like to be a such man to try to experience the optimized document please opt here | 0 |
444,704 | 31,143,226,840 | IssuesEvent | 2023-08-16 03:02:42 | liatrio/liatrio-otel-collector | https://api.github.com/repos/liatrio/liatrio-otel-collector | closed | Add ability to search within the organization to prune down information | documentation enhancement go | # Overview
With large orgs there's the potential for not being able to actually grab all the data. For example, we've seen some orgs with 15,000+ repositories. Thus it'd be performant and ideal to be able to additionally prune down the search in those cases, such that you can search for the things you want.
## Acceptance Criteria
* tested
* documentation updated
* configuration optional
* allows for searching by topic, team, or repo name | 1.0 | Add ability to search within the organization to prune down information - # Overview
With large orgs there's the potential for not being able to actually grab all the data. For example, we've seen some orgs with 15,000+ repositories. Thus it'd be performant and ideal to be able to additionally prune down the search in those cases, such that you can search for the things you want.
## Acceptance Criteria
* tested
* documentation updated
* configuration optional
* allows for searching by topic, team, or repo name | non_test | add ability to search within the organization to prune down information overview with large orgs there s the potential for not being able to actually grab all the data for example we ve seen some orgs with repositories thus it d be performant and ideal to be able to additionally prune down the search in those cases such that you can search for the things you want acceptance criteria tested documentation updated configuration optional allows for searching by topic team or repo name | 0 |
675,458 | 23,095,247,288 | IssuesEvent | 2022-07-26 18:51:41 | yugabyte/yugabyte-db | https://api.github.com/repos/yugabyte/yugabyte-db | closed | yb-master fails to restart after errors during first run | kind/bug area/docdb priority/medium | Jira Link: [DB-1889](https://yugabyte.atlassian.net/browse/DB-1889)
Repro: Start yb-master with an incorrect master_addresses on first run, see it crash, fix the master_addresses and restart the master, it will not start up properly. This is similar to #4866 but a different failure point.
------------------
During yb-master startup, we create the instance file early in the fs manager init and then use the presence of this marker file to guide initialization of the sys catalog raft metadata. This is kind of broken because there are steps that can fail in between the instance file creation and the sys catalog metadata initialization.
This issue is to track the proper fix to all these kinds of issues. We need to fix the sys catalog Load/Create code to either do a LoadOrCreate or maybe have a marker to make sure it has gotten out of the "first run" phase successfully at least once.
Details
-------------------
```
sanketh@varahi:~/code/yugabyte-db$ ~/yugabyte-2.1.8.2/bin/yb-master --fs_data_dirs=/tmp/testcrash1 --rpc_bind_addresses=127.0.0.1:7100 --master_addresses=127.0.0.2:7100 --replication_factor=1
F0730 20:43:44.338073 17057 master_main.cc:120] Illegal state (yb/master/catalog_manager.cc:1273): Unable to initialize catalog manager: Failed to initialize sys tables async: None of the local addresses are present in master_addresses 127.0.0.2:7100.
Fatal failure details written to /tmp/testcrash1/yb-data/master/logs/yb-master.FATAL.details.2020-07-30T20_43_44.pid17057.txt
F20200730 20:43:44 ../../src/yb/master/master_main.cc:120] Illegal state (yb/master/catalog_manager.cc:1273): Unable to initialize catalog manager: Failed to initialize sys tables async: None of the local addresses are present in master_addresses 127.0.0.2:7100.
@ 0x7fb07a43cc0c yb::LogFatalHandlerSink::send()
@ 0x7fb079624346 google::LogMessage::SendToLog()
@ 0x7fb0796217aa google::LogMessage::Flush()
@ 0x7fb079624879 google::LogMessageFatal::~LogMessageFatal()
@ 0x408fb4 yb::master::MasterMain()
@ 0x7fb075283825 __libc_start_main
@ 0x408369 _start
@ (nil) (unknown)
*** Check failure stack trace: ***
@ 0x7fb07a43aff1 yb::(anonymous namespace)::DumpStackTraceAndExit()
@ 0x7fb079621c5d google::LogMessage::Fail()
@ 0x7fb079623dcd google::LogMessage::SendToLog()
@ 0x7fb0796217aa google::LogMessage::Flush()
@ 0x7fb079624879 google::LogMessageFatal::~LogMessageFatal()
@ 0x408fb4 yb::master::MasterMain()
@ 0x7fb075283825 __libc_start_main
@ 0x408369 _start
@ (nil) (unknown)
Aborted (core dumped)
sanketh@varahi:~/code/yugabyte-db$ ~/yugabyte-2.1.8.2/bin/yb-master --fs_data_dirs=/tmp/testcrash1 --rpc_bind_addresses=127.0.0.1:7100 --master_addresses=127.0.0.1:7100 --replication_factor=1
F0730 20:43:48.776080 17094 master_main.cc:120] Not found (yb/util/env_posix.cc:1482): Unable to initialize catalog manager: Failed to initialize sys tables async: Could not load Raft group metadata from /tmp/testcrash1/yb-data/master/tablet-meta/00000000000000000000000000000000: /tmp/testcrash1/yb-data/master/tablet-meta/00000000000000000000000000000000: No such file or directory (system error 2)
Fatal failure details written to /tmp/testcrash1/yb-data/master/logs/yb-master.FATAL.details.2020-07-30T20_43_48.pid17094.txt
F20200730 20:43:48 ../../src/yb/master/master_main.cc:120] Not found (yb/util/env_posix.cc:1482): Unable to initialize catalog manager: Failed to initialize sys tables async: Could not load Raft group metadata from /tmp/testcrash1/yb-data/master/tablet-meta/00000000000000000000000000000000: /tmp/testcrash1/yb-data/master/tablet-meta/00000000000000000000000000000000: No such file or directory (system error 2)
@ 0x7fc4c87f9c0c yb::LogFatalHandlerSink::send()
@ 0x7fc4c79e1346 google::LogMessage::SendToLog()
@ 0x7fc4c79de7aa google::LogMessage::Flush()
@ 0x7fc4c79e1879 google::LogMessageFatal::~LogMessageFatal()
@ 0x408fb4 yb::master::MasterMain()
@ 0x7fc4c3640825 __libc_start_main
@ 0x408369 _start
@ (nil) (unknown)
*** Check failure stack trace: ***
@ 0x7fc4c87f7ff1 yb::(anonymous namespace)::DumpStackTraceAndExit()
@ 0x7fc4c79dec5d google::LogMessage::Fail()
@ 0x7fc4c79e0dcd google::LogMessage::SendToLog()
@ 0x7fc4c79de7aa google::LogMessage::Flush()
@ 0x7fc4c79e1879 google::LogMessageFatal::~LogMessageFatal()
@ 0x408fb4 yb::master::MasterMain()
@ 0x7fc4c3640825 __libc_start_main
@ 0x408369 _start
@ (nil) (unknown)
Aborted (core dumped)
```
| 1.0 | yb-master fails to restart after errors during first run - Jira Link: [DB-1889](https://yugabyte.atlassian.net/browse/DB-1889)
Repro: Start yb-master with an incorrect master_addresses on first run, see it crash, fix the master_addresses and restart the master, it will not start up properly. This is similar to #4866 but a different failure point.
------------------
During yb-master startup, we create the instance file early in the fs manager init and then use the presence of this marker file to guide initialization of the sys catalog raft metadata. This is kind of broken because there are steps that can fail in between the instance file creation and the sys catalog metadata initialization.
This issue is to track the proper fix to all these kinds of issues. We need to fix the sys catalog Load/Create code to either do a LoadOrCreate or maybe have a marker to make sure it has gotten out of the "first run" phase successfully at least once.
Details
-------------------
```
sanketh@varahi:~/code/yugabyte-db$ ~/yugabyte-2.1.8.2/bin/yb-master --fs_data_dirs=/tmp/testcrash1 --rpc_bind_addresses=127.0.0.1:7100 --master_addresses=127.0.0.2:7100 --replication_factor=1
F0730 20:43:44.338073 17057 master_main.cc:120] Illegal state (yb/master/catalog_manager.cc:1273): Unable to initialize catalog manager: Failed to initialize sys tables async: None of the local addresses are present in master_addresses 127.0.0.2:7100.
Fatal failure details written to /tmp/testcrash1/yb-data/master/logs/yb-master.FATAL.details.2020-07-30T20_43_44.pid17057.txt
F20200730 20:43:44 ../../src/yb/master/master_main.cc:120] Illegal state (yb/master/catalog_manager.cc:1273): Unable to initialize catalog manager: Failed to initialize sys tables async: None of the local addresses are present in master_addresses 127.0.0.2:7100.
@ 0x7fb07a43cc0c yb::LogFatalHandlerSink::send()
@ 0x7fb079624346 google::LogMessage::SendToLog()
@ 0x7fb0796217aa google::LogMessage::Flush()
@ 0x7fb079624879 google::LogMessageFatal::~LogMessageFatal()
@ 0x408fb4 yb::master::MasterMain()
@ 0x7fb075283825 __libc_start_main
@ 0x408369 _start
@ (nil) (unknown)
*** Check failure stack trace: ***
@ 0x7fb07a43aff1 yb::(anonymous namespace)::DumpStackTraceAndExit()
@ 0x7fb079621c5d google::LogMessage::Fail()
@ 0x7fb079623dcd google::LogMessage::SendToLog()
@ 0x7fb0796217aa google::LogMessage::Flush()
@ 0x7fb079624879 google::LogMessageFatal::~LogMessageFatal()
@ 0x408fb4 yb::master::MasterMain()
@ 0x7fb075283825 __libc_start_main
@ 0x408369 _start
@ (nil) (unknown)
Aborted (core dumped)
sanketh@varahi:~/code/yugabyte-db$ ~/yugabyte-2.1.8.2/bin/yb-master --fs_data_dirs=/tmp/testcrash1 --rpc_bind_addresses=127.0.0.1:7100 --master_addresses=127.0.0.1:7100 --replication_factor=1
F0730 20:43:48.776080 17094 master_main.cc:120] Not found (yb/util/env_posix.cc:1482): Unable to initialize catalog manager: Failed to initialize sys tables async: Could not load Raft group metadata from /tmp/testcrash1/yb-data/master/tablet-meta/00000000000000000000000000000000: /tmp/testcrash1/yb-data/master/tablet-meta/00000000000000000000000000000000: No such file or directory (system error 2)
Fatal failure details written to /tmp/testcrash1/yb-data/master/logs/yb-master.FATAL.details.2020-07-30T20_43_48.pid17094.txt
F20200730 20:43:48 ../../src/yb/master/master_main.cc:120] Not found (yb/util/env_posix.cc:1482): Unable to initialize catalog manager: Failed to initialize sys tables async: Could not load Raft group metadata from /tmp/testcrash1/yb-data/master/tablet-meta/00000000000000000000000000000000: /tmp/testcrash1/yb-data/master/tablet-meta/00000000000000000000000000000000: No such file or directory (system error 2)
@ 0x7fc4c87f9c0c yb::LogFatalHandlerSink::send()
@ 0x7fc4c79e1346 google::LogMessage::SendToLog()
@ 0x7fc4c79de7aa google::LogMessage::Flush()
@ 0x7fc4c79e1879 google::LogMessageFatal::~LogMessageFatal()
@ 0x408fb4 yb::master::MasterMain()
@ 0x7fc4c3640825 __libc_start_main
@ 0x408369 _start
@ (nil) (unknown)
*** Check failure stack trace: ***
@ 0x7fc4c87f7ff1 yb::(anonymous namespace)::DumpStackTraceAndExit()
@ 0x7fc4c79dec5d google::LogMessage::Fail()
@ 0x7fc4c79e0dcd google::LogMessage::SendToLog()
@ 0x7fc4c79de7aa google::LogMessage::Flush()
@ 0x7fc4c79e1879 google::LogMessageFatal::~LogMessageFatal()
@ 0x408fb4 yb::master::MasterMain()
@ 0x7fc4c3640825 __libc_start_main
@ 0x408369 _start
@ (nil) (unknown)
Aborted (core dumped)
```
| non_test | yb master fails to restart after errors during first run jira link repro start yb master with an incorrect master addresses on first run see it crash fix the master addresses and restart the master it will not start up properly this is similar to but a different failure point during yb master startup we create the instance file early in the fs manager init and then use the presence of this marker file to guide initialization of the sys catalog raft metadata this is kind of broken because there are steps that can fail in between the instance file creation and the sys catalog metadata initialization this issue is to track the proper fix to all these kinds of issues we need to fix the sys catalog load create code to either do a loadorcreate or maybe have a marker to make sure it has gotten out of the first run phase successfully at least once details sanketh varahi code yugabyte db yugabyte bin yb master fs data dirs tmp rpc bind addresses master addresses replication factor master main cc illegal state yb master catalog manager cc unable to initialize catalog manager failed to initialize sys tables async none of the local addresses are present in master addresses fatal failure details written to tmp yb data master logs yb master fatal details txt src yb master master main cc illegal state yb master catalog manager cc unable to initialize catalog manager failed to initialize sys tables async none of the local addresses are present in master addresses yb logfatalhandlersink send google logmessage sendtolog google logmessage flush google logmessagefatal logmessagefatal yb master mastermain libc start main start nil unknown check failure stack trace yb anonymous namespace dumpstacktraceandexit google logmessage fail google logmessage sendtolog google logmessage flush google logmessagefatal logmessagefatal yb master mastermain libc start main start nil unknown aborted core dumped sanketh varahi code yugabyte db yugabyte bin yb master fs data dirs tmp rpc bind addresses master addresses replication factor master main cc not found yb util env posix cc unable to initialize catalog manager failed to initialize sys tables async could not load raft group metadata from tmp yb data master tablet meta tmp yb data master tablet meta no such file or directory system error fatal failure details written to tmp yb data master logs yb master fatal details txt src yb master master main cc not found yb util env posix cc unable to initialize catalog manager failed to initialize sys tables async could not load raft group metadata from tmp yb data master tablet meta tmp yb data master tablet meta no such file or directory system error yb logfatalhandlersink send google logmessage sendtolog google logmessage flush google logmessagefatal logmessagefatal yb master mastermain libc start main start nil unknown check failure stack trace yb anonymous namespace dumpstacktraceandexit google logmessage fail google logmessage sendtolog google logmessage flush google logmessagefatal logmessagefatal yb master mastermain libc start main start nil unknown aborted core dumped | 0 |
94,113 | 8,470,753,940 | IssuesEvent | 2018-10-24 06:05:41 | NKCR-INPROVE/evidence.periodik | https://api.github.com/repos/NKCR-INPROVE/evidence.periodik | closed | Chybné exempláře VKOL | ready for test | únor-duben 1936:
únor 2650480929 (objevuje se pouze 1. 2. 1936, zbytek chybí)
březen 2650480903 (chybí úplně)
duben 2650480904 (objevuje se pouze 1. 4. 1936, zbytek chybí)
červenec-září 1936:
vedle odpovídajícího čárového kodu 2650481625 (ČVC-ZÁŘÍ) je uváděn i čárový kod předešlého časového úseku 2650481623 (KVĚT-ČVN)
září neodpovídá čárový kod, má být 2650481625
říjen-prosinec 1936:
říjen 2650365268 (odpovídající čárový kod uveden pouze u 1. 10. 1936, zbytek měsíce neodpovídá, použit 2650481623 (KVĚT-ČVN))
listopad 2650481624 (uveden chybný čárový kod 2650481623 (KVĚT-ČVN))
prosinec 2650482449 (odpovídající čárový kod uveden pouze u 1. 12. 1936, zbytek měsíce neodpovídá, použit 2650481623 (KVĚT-ČVN))
| 1.0 | Chybné exempláře VKOL - únor-duben 1936:
únor 2650480929 (objevuje se pouze 1. 2. 1936, zbytek chybí)
březen 2650480903 (chybí úplně)
duben 2650480904 (objevuje se pouze 1. 4. 1936, zbytek chybí)
červenec-září 1936:
vedle odpovídajícího čárového kodu 2650481625 (ČVC-ZÁŘÍ) je uváděn i čárový kod předešlého časového úseku 2650481623 (KVĚT-ČVN)
září neodpovídá čárový kod, má být 2650481625
říjen-prosinec 1936:
říjen 2650365268 (odpovídající čárový kod uveden pouze u 1. 10. 1936, zbytek měsíce neodpovídá, použit 2650481623 (KVĚT-ČVN))
listopad 2650481624 (uveden chybný čárový kod 2650481623 (KVĚT-ČVN))
prosinec 2650482449 (odpovídající čárový kod uveden pouze u 1. 12. 1936, zbytek měsíce neodpovídá, použit 2650481623 (KVĚT-ČVN))
| test | chybné exempláře vkol únor duben únor objevuje se pouze zbytek chybí březen chybí úplně duben objevuje se pouze zbytek chybí červenec září vedle odpovídajícího čárového kodu čvc září je uváděn i čárový kod předešlého časového úseku květ čvn září neodpovídá čárový kod má být říjen prosinec říjen odpovídající čárový kod uveden pouze u zbytek měsíce neodpovídá použit květ čvn listopad uveden chybný čárový kod květ čvn prosinec odpovídající čárový kod uveden pouze u zbytek měsíce neodpovídá použit květ čvn | 1 |
57,577 | 6,550,931,529 | IssuesEvent | 2017-09-05 13:07:23 | imona/adendum | https://api.github.com/repos/imona/adendum | closed | Tüm Katılımcı/Sözleşmeler için XIRR Hesaplatılması (API) (Due: 25.08.2017) | API EKRAN enhancement test | Bir emeklilik şirketinin müşterisi durumundaki tüm katılımcılar için ve bu katılımcıların tüm sözleşmeleri için;
- [x] XIRR hesaplatılması,
- [x] Hesaplama sonuçlarının "Özet Raporlama Tabloları"na yazdırılması | 1.0 | Tüm Katılımcı/Sözleşmeler için XIRR Hesaplatılması (API) (Due: 25.08.2017) - Bir emeklilik şirketinin müşterisi durumundaki tüm katılımcılar için ve bu katılımcıların tüm sözleşmeleri için;
- [x] XIRR hesaplatılması,
- [x] Hesaplama sonuçlarının "Özet Raporlama Tabloları"na yazdırılması | test | tüm katılımcı sözleşmeler için xirr hesaplatılması api due bir emeklilik şirketinin müşterisi durumundaki tüm katılımcılar için ve bu katılımcıların tüm sözleşmeleri için xirr hesaplatılması hesaplama sonuçlarının özet raporlama tabloları na yazdırılması | 1 |
37,002 | 5,097,657,791 | IssuesEvent | 2017-01-03 22:12:35 | servo/servo | https://api.github.com/repos/servo/servo | opened | Missing borders in table with border-collapse | A-layout/table C-has-test I-wrong | The following table renders incorrectly in Servo. The top and left borders are missing.
```
<table style="border-collapse: collapse;">
<tr>
<td style="border: 1px solid black;">test</td>
</tr>
</table>
``` | 1.0 | Missing borders in table with border-collapse - The following table renders incorrectly in Servo. The top and left borders are missing.
```
<table style="border-collapse: collapse;">
<tr>
<td style="border: 1px solid black;">test</td>
</tr>
</table>
``` | test | missing borders in table with border collapse the following table renders incorrectly in servo the top and left borders are missing test | 1 |
73,895 | 7,363,065,134 | IssuesEvent | 2018-03-12 00:50:50 | GeoDaCenter/geoda | https://api.github.com/repos/GeoDaCenter/geoda | closed | K-Means crash | fixed: verify! to be tested | GeoDa 1.12.1.71
Windows 8
GeoDa freezes when running Guerry file through K-Means (screenshot below).
Also freezes when there are fewer variables selected.
| 1.0 | K-Means crash - GeoDa 1.12.1.71
Windows 8
GeoDa freezes when running Guerry file through K-Means (screenshot below).
Also freezes when there are fewer variables selected.
| test | k means crash geoda windows geoda freezes when running guerry file through k means screenshot below also freezes when there are fewer variables selected | 1 |
18,428 | 10,114,248,311 | IssuesEvent | 2019-07-30 18:42:43 | influxdata/influxdb | https://api.github.com/repos/influxdata/influxdb | closed | Use ffjson to improve JSON encoding/mashalling performance | 1.x area/queries performance wontfix | On my (small) test system I see the generation of the result set dominating the query time. I suspect this is substantially due to JSON encoding speed (about 90% of total query time)
ffjson is an attempt to offer a drop-in replacement for json.Marshall, claims 2-3x performance improvement. It doesn't necessarily require adding an additional dependency as it generates static code.
https://github.com/pquerna/ffjson
Thanks if you can consider this - might be a quick performance win?
| True | Use ffjson to improve JSON encoding/mashalling performance - On my (small) test system I see the generation of the result set dominating the query time. I suspect this is substantially due to JSON encoding speed (about 90% of total query time)
ffjson is an attempt to offer a drop-in replacement for json.Marshall, claims 2-3x performance improvement. It doesn't necessarily require adding an additional dependency as it generates static code.
https://github.com/pquerna/ffjson
Thanks if you can consider this - might be a quick performance win?
| non_test | use ffjson to improve json encoding mashalling performance on my small test system i see the generation of the result set dominating the query time i suspect this is substantially due to json encoding speed about of total query time ffjson is an attempt to offer a drop in replacement for json marshall claims performance improvement it doesn t necessarily require adding an additional dependency as it generates static code thanks if you can consider this might be a quick performance win | 0 |
210,358 | 16,097,691,276 | IssuesEvent | 2021-04-27 04:02:15 | cypress-io/cypress | https://api.github.com/repos/cypress-io/cypress | opened | vite-dev-server: when opening a spec on windows it hangs forever | OS: windows component testing | <!-- 👋 Use the template below to report a bug. Fill in as much info as possible.
Have a question? Start a new discussion 👉 https://github.com/cypress-io/cypress/discussions
As an open source project with a small maintainer team, it may take some time for your issue to be addressed. Please be patient and we will respond as soon as we can. 🙏 -->
### Current behavior
Open a cypress/vite-dev-server on windows. Open a spec, you will not get a result.
Instead, you get the following error:
### Desired behavior
To be able to run cypress on windows
### Test code to reproduce
clone https://github.com/elevatebart/cy-ds-test
open on windows
open a spec
### Versions
vite-dev-server 1.2.4
| 1.0 | vite-dev-server: when opening a spec on windows it hangs forever - <!-- 👋 Use the template below to report a bug. Fill in as much info as possible.
Have a question? Start a new discussion 👉 https://github.com/cypress-io/cypress/discussions
As an open source project with a small maintainer team, it may take some time for your issue to be addressed. Please be patient and we will respond as soon as we can. 🙏 -->
### Current behavior
Open a cypress/vite-dev-server on windows. Open a spec, you will not get a result.
Instead, you get the following error:
### Desired behavior
To be able to run cypress on windows
### Test code to reproduce
clone https://github.com/elevatebart/cy-ds-test
open on windows
open a spec
### Versions
vite-dev-server 1.2.4
| test | vite dev server when opening a spec on windows it hangs forever 👋 use the template below to report a bug fill in as much info as possible have a question start a new discussion 👉 as an open source project with a small maintainer team it may take some time for your issue to be addressed please be patient and we will respond as soon as we can 🙏 current behavior open a cypress vite dev server on windows open a spec you will not get a result instead you get the following error desired behavior to be able to run cypress on windows test code to reproduce clone open on windows open a spec versions vite dev server | 1 |
182,752 | 14,148,655,376 | IssuesEvent | 2020-11-10 22:59:48 | rust-lang/rust-clippy | https://api.github.com/repos/rust-lang/rust-clippy | closed | #[allow(clippy::option_option)] not working when paired with #[serde(deserialize_with)] | P-needs-test T-macros good first issue hacktoberfest | Using: VS Code with RLS, Windows
This produces clippy warning on `option_option`:
#[allow(clippy::option_option)]
#[serde(deserialize_with = "func")]
#[serde(skip_serializing_if = "Option::is_none")]
#[serde(default)]
#[serde(borrow)]
foo: Option<Option<Cow<'a, str>>>,
~~~
consider using `Option<T>` instead of `Option<Option<T>>` or a custom enum if you need to distinguish all 3 cases.
~~~
However, removing `#[serde(deserialize_with ... )]` makes it work:
#[allow(clippy::option_option)]
#[serde(skip_serializing_if = "Option::is_none")]
#[serde(default)]
#[serde(borrow)]
foo: Option<Option<Cow<'a, str>>>,
I suspect `#[serde(serialize_with ...)]` will also trip up this feature. So something about `serde`'s `serialize_with` and `deserialize_with` attributes conflict with `option_option`.
| 1.0 | #[allow(clippy::option_option)] not working when paired with #[serde(deserialize_with)] - Using: VS Code with RLS, Windows
This produces clippy warning on `option_option`:
#[allow(clippy::option_option)]
#[serde(deserialize_with = "func")]
#[serde(skip_serializing_if = "Option::is_none")]
#[serde(default)]
#[serde(borrow)]
foo: Option<Option<Cow<'a, str>>>,
~~~
consider using `Option<T>` instead of `Option<Option<T>>` or a custom enum if you need to distinguish all 3 cases.
~~~
However, removing `#[serde(deserialize_with ... )]` makes it work:
#[allow(clippy::option_option)]
#[serde(skip_serializing_if = "Option::is_none")]
#[serde(default)]
#[serde(borrow)]
foo: Option<Option<Cow<'a, str>>>,
I suspect `#[serde(serialize_with ...)]` will also trip up this feature. So something about `serde`'s `serialize_with` and `deserialize_with` attributes conflict with `option_option`.
| test | not working when paired with using vs code with rls windows this produces clippy warning on option option foo option consider using option instead of option or a custom enum if you need to distinguish all cases however removing makes it work foo option i suspect will also trip up this feature so something about serde s serialize with and deserialize with attributes conflict with option option | 1 |
65,106 | 26,978,090,958 | IssuesEvent | 2023-02-09 11:01:28 | Ocelot-Social-Community/Ocelot-Social | https://api.github.com/repos/Ocelot-Social-Community/Ocelot-Social | closed | 🐛 [Bug] Yunite Color of Group tags | bug service: webapp project: yunite | <!-- You can find the latest issue templates here https://github.com/ulfgebhardt/issue-templates -->
## 🐛 Bugreport
<!-- Describe your issue in detail. Include screenshots if needed. Give us as much information as possible. Use a clear and concise description of what the bug is.-->
Yunite Color of Group tags.
Group Tags have the wrong color on Yunite.
- [x] Fix the color
- [x] Do the same on the group profile
- [x] Figure out why this is not changed before - too many color definitions?
<img width="1646" alt="215031214-0c70619e-daa9-452a-9f81-70093d324917" src="https://user-images.githubusercontent.com/25344101/215741929-39c97a2f-4adc-4b35-97a6-58a700df150b.png">
| 1.0 | 🐛 [Bug] Yunite Color of Group tags - <!-- You can find the latest issue templates here https://github.com/ulfgebhardt/issue-templates -->
## 🐛 Bugreport
<!-- Describe your issue in detail. Include screenshots if needed. Give us as much information as possible. Use a clear and concise description of what the bug is.-->
Yunite Color of Group tags.
Group Tags have the wrong color on Yunite.
- [x] Fix the color
- [x] Do the same on the group profile
- [x] Figure out why this is not changed before - too many color definitions?
<img width="1646" alt="215031214-0c70619e-daa9-452a-9f81-70093d324917" src="https://user-images.githubusercontent.com/25344101/215741929-39c97a2f-4adc-4b35-97a6-58a700df150b.png">
| non_test | 🐛 yunite color of group tags 🐛 bugreport yunite color of group tags group tags have the wrong color on yunite fix the color do the same on the group profile figure out why this is not changed before too many color definitions img width alt src | 0 |
379,999 | 26,397,602,278 | IssuesEvent | 2023-01-12 21:00:36 | JaimePSantos/QWAK | https://api.github.com/repos/JaimePSantos/QWAK | closed | Complete documentation of the QWAK class. | documentation enhancement good first issue | ## Enhancement proposal
<!-- Add a clear and concise description of your enhancement proposal. -->
There are some functions in the [QWAK](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK) class that have no documentation yet:
- [ ] [Constructor](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK): Needs description of time and timelist.
- [ ] [runWalk](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK.runWalk): Add error types.
- [ ] [setAdjacency](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK.setAdjacencyMatrix): Needs full docs.
- [ ] [getAdjacencyMatrix](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK.getAdjacencyMatrix): Needs full docs.
- [ ] [checkPST](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK.checkPST): Needs full docs.
- [ ] [getMean](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK.getMean): Needs full docs.
- [ ] [getSndMoment](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK.getSndMoment): Needs full docs.
- [ ] [getStDev](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK.getStDev): Needs full docs.
- [ ] [getInversePartRatio](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK.getInversePartRatio): Needs full docs.
- [ ] [getTransportEfficiency](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK.getTransportEfficiency): Needs full docs.
- [ ] [runMultipleWalks](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK): Needs full docs.
- [ ] [getProbDistList](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK): Needs full docs.
- [ ] [getProbVecList](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK): Needs full docs.
- [ ] [getWalkList](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK): Needs full docs.
- [ ] [getAmpVecList](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK): Needs full docs.
- [ ] [setTimeList](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK): Needs full docs.
- [ ] [getTimeList](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK): Needs full docs.
## Additional comments
<!-- Add further context that you think might be relevant. -->
There are many instances of double return types and im not really sure why.
| 1.0 | Complete documentation of the QWAK class. - ## Enhancement proposal
<!-- Add a clear and concise description of your enhancement proposal. -->
There are some functions in the [QWAK](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK) class that have no documentation yet:
- [ ] [Constructor](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK): Needs description of time and timelist.
- [ ] [runWalk](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK.runWalk): Add error types.
- [ ] [setAdjacency](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK.setAdjacencyMatrix): Needs full docs.
- [ ] [getAdjacencyMatrix](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK.getAdjacencyMatrix): Needs full docs.
- [ ] [checkPST](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK.checkPST): Needs full docs.
- [ ] [getMean](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK.getMean): Needs full docs.
- [ ] [getSndMoment](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK.getSndMoment): Needs full docs.
- [ ] [getStDev](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK.getStDev): Needs full docs.
- [ ] [getInversePartRatio](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK.getInversePartRatio): Needs full docs.
- [ ] [getTransportEfficiency](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK.getTransportEfficiency): Needs full docs.
- [ ] [runMultipleWalks](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK): Needs full docs.
- [ ] [getProbDistList](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK): Needs full docs.
- [ ] [getProbVecList](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK): Needs full docs.
- [ ] [getWalkList](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK): Needs full docs.
- [ ] [getAmpVecList](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK): Needs full docs.
- [ ] [setTimeList](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK): Needs full docs.
- [ ] [getTimeList](https://jaimepsantos.github.io/QWAK/qwak.html#qwak.qwak.QWAK): Needs full docs.
## Additional comments
<!-- Add further context that you think might be relevant. -->
There are many instances of double return types and im not really sure why.
| non_test | complete documentation of the qwak class enhancement proposal there are some functions in the class that have no documentation yet needs description of time and timelist add error types needs full docs needs full docs needs full docs needs full docs needs full docs needs full docs needs full docs needs full docs needs full docs needs full docs needs full docs needs full docs needs full docs needs full docs needs full docs additional comments there are many instances of double return types and im not really sure why | 0 |
74,204 | 25,008,315,764 | IssuesEvent | 2022-11-03 13:34:38 | vector-im/element-call | https://api.github.com/repos/vector-im/element-call | opened | Safari fails on re-entering call with USB webcam | T-Defect | ### Steps to reproduce
1. Use USB webcam for both audio and video capture (on the mac)
2. Join call from some other device
3. Join call from Safari
4. Leave call in Safari
5. Rejoin call in Safari
### Outcome
#### What did you expect?
Rejoins calls
#### What happened instead?
EC/Safari end up in some kind of loop where Safari keeps opening and closing the camera (the light on the camera keeps turning on and off and if you're playing music, it ducks the music which happens whenever a page in Safari gets an audio stream). EC doesn't appear to be calling getUserMedia in a loop though. If you leave it looping for too long, any application will hang as soon as it tries to play any audio and you'll have to restart your mac to play audio again.
* Doesn't happen if there are no other users in the call
* Doesn't happen using the built-in Facetime camera & mic
### Operating system
macOS
### Browser information
Safari 16.1
### URL for webapp
_No response_
### Will you send logs?
No | 1.0 | Safari fails on re-entering call with USB webcam - ### Steps to reproduce
1. Use USB webcam for both audio and video capture (on the mac)
2. Join call from some other device
3. Join call from Safari
4. Leave call in Safari
5. Rejoin call in Safari
### Outcome
#### What did you expect?
Rejoins calls
#### What happened instead?
EC/Safari end up in some kind of loop where Safari keeps opening and closing the camera (the light on the camera keeps turning on and off and if you're playing music, it ducks the music which happens whenever a page in Safari gets an audio stream). EC doesn't appear to be calling getUserMedia in a loop though. If you leave it looping for too long, any application will hang as soon as it tries to play any audio and you'll have to restart your mac to play audio again.
* Doesn't happen if there are no other users in the call
* Doesn't happen using the built-in Facetime camera & mic
### Operating system
macOS
### Browser information
Safari 16.1
### URL for webapp
_No response_
### Will you send logs?
No | non_test | safari fails on re entering call with usb webcam steps to reproduce use usb webcam for both audio and video capture on the mac join call from some other device join call from safari leave call in safari rejoin call in safari outcome what did you expect rejoins calls what happened instead ec safari end up in some kind of loop where safari keeps opening and closing the camera the light on the camera keeps turning on and off and if you re playing music it ducks the music which happens whenever a page in safari gets an audio stream ec doesn t appear to be calling getusermedia in a loop though if you leave it looping for too long any application will hang as soon as it tries to play any audio and you ll have to restart your mac to play audio again doesn t happen if there are no other users in the call doesn t happen using the built in facetime camera mic operating system macos browser information safari url for webapp no response will you send logs no | 0 |
146,717 | 11,746,807,639 | IssuesEvent | 2020-03-12 12:29:54 | tikv/tikv | https://api.github.com/repos/tikv/tikv | opened | test raftstore::test_snap::test_node_cf_snapshot ... thread 'test-pd-worker' panicked | component/test-bench | raftstore::test_snap::test_node_cf_snapshot
https://internal.pingcap.net/idc-jenkins/blue/organizations/jenkins/tikv_ghpr_test/detail/tikv_ghpr_test/18544/pipeline/226 Integration Part13
```
[2020-03-12T09:18:31.658Z] test raftstore::test_snap::test_node_cf_snapshot ... thread 'test-pd-worker' panicked at 'called `Option::unwrap()` on a `None` value', /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libcore/macros/mod.rs:15:40
[2020-03-12T09:18:31.658Z] stack backtrace:
[2020-03-12T09:18:32.227Z] 0: backtrace::backtrace::libunwind::trace
[2020-03-12T09:18:32.227Z] at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88
[2020-03-12T09:18:32.227Z] 1: backtrace::backtrace::trace_unsynchronized
[2020-03-12T09:18:32.227Z] at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66
[2020-03-12T09:18:32.227Z] 2: std::sys_common::backtrace::_print_fmt
[2020-03-12T09:18:32.227Z] at src/libstd/sys_common/backtrace.rs:84
[2020-03-12T09:18:32.227Z] 3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
[2020-03-12T09:18:32.227Z] at src/libstd/sys_common/backtrace.rs:61
[2020-03-12T09:18:32.227Z] 4: core::fmt::write
[2020-03-12T09:18:32.227Z] at src/libcore/fmt/mod.rs:1025
[2020-03-12T09:18:32.227Z] 5: std::io::Write::write_fmt
[2020-03-12T09:18:32.227Z] at src/libstd/io/mod.rs:1426
[2020-03-12T09:18:32.227Z] 6: std::sys_common::backtrace::_print
[2020-03-12T09:18:32.227Z] at src/libstd/sys_common/backtrace.rs:65
[2020-03-12T09:18:32.227Z] 7: std::sys_common::backtrace::print
[2020-03-12T09:18:32.227Z] at src/libstd/sys_common/backtrace.rs:50
[2020-03-12T09:18:32.227Z] 8: std::panicking::default_hook::{{closure}}
[2020-03-12T09:18:32.227Z] at src/libstd/panicking.rs:193
[2020-03-12T09:18:32.227Z] 9: std::panicking::default_hook
[2020-03-12T09:18:32.227Z] at src/libstd/panicking.rs:210
[2020-03-12T09:18:32.227Z] 10: std::panicking::rust_panic_with_hook
[2020-03-12T09:18:32.227Z] at src/libstd/panicking.rs:471
[2020-03-12T09:18:32.227Z] 11: rust_begin_unwind
[2020-03-12T09:18:32.227Z] at src/libstd/panicking.rs:375
[2020-03-12T09:18:32.227Z] 12: core::panicking::panic_fmt
[2020-03-12T09:18:32.227Z] at src/libcore/panicking.rs:84
[2020-03-12T09:18:32.227Z] 13: core::panicking::panic
[2020-03-12T09:18:32.227Z] at src/libcore/panicking.rs:51
[2020-03-12T09:18:32.227Z] 14: core::option::Option<T>::unwrap
[2020-03-12T09:18:32.227Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libcore/macros/mod.rs:15
[2020-03-12T09:18:32.227Z] 15: <test_raftstore::pd::TestPdClient as pd_client::PdClient>::handle_region_heartbeat_response
[2020-03-12T09:18:32.227Z] at components/test_raftstore/src/pd.rs:1091
[2020-03-12T09:18:32.227Z] 16: raftstore::store::worker::pd::Runner<T>::schedule_heartbeat_receiver
[2020-03-12T09:18:32.227Z] at ./components/raftstore/src/store/worker/pd.rs:705
[2020-03-12T09:18:32.227Z] 17: <raftstore::store::worker::pd::Runner<T> as tikv_util::worker::future::Runnable<raftstore::store::worker::pd::Task>>::run
[2020-03-12T09:18:32.227Z] at ./components/raftstore/src/store/worker/pd.rs:847
[2020-03-12T09:18:32.227Z] 18: tikv_util::worker::future::poll::{{closure}}
[2020-03-12T09:18:32.227Z] at ./components/tikv_util/src/worker/future.rs:108
[2020-03-12T09:18:32.227Z] 19: <futures::stream::for_each::ForEach<S,F,U> as futures::future::Future>::poll
[2020-03-12T09:18:32.227Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/stream/for_each.rs:46
[2020-03-12T09:18:32.227Z] 20: futures::task_impl::Spawn<T>::poll_future_notify::{{closure}}
[2020-03-12T09:18:32.227Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/mod.rs:329
[2020-03-12T09:18:32.227Z] 21: futures::task_impl::Spawn<T>::enter::{{closure}}
[2020-03-12T09:18:32.227Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/mod.rs:399
[2020-03-12T09:18:32.227Z] 22: futures::task_impl::std::set
[2020-03-12T09:18:32.227Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/std/mod.rs:83
[2020-03-12T09:18:32.227Z] 23: futures::task_impl::Spawn<T>::enter
[2020-03-12T09:18:32.227Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/mod.rs:399
[2020-03-12T09:18:32.227Z] 24: futures::task_impl::Spawn<T>::poll_fn_notify
[2020-03-12T09:18:32.227Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/mod.rs:291
[2020-03-12T09:18:32.228Z] 25: futures::task_impl::Spawn<T>::poll_future_notify
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/mod.rs:329
[2020-03-12T09:18:32.228Z] 26: tokio_core::reactor::Core::run::{{closure}}::{{closure}}::{{closure}}::{{closure}}::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-core-0.1.17/src/reactor/mod.rs:236
[2020-03-12T09:18:32.228Z] 27: futures::future::lazy::Lazy<F,R>::get
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/future/lazy.rs:64
[2020-03-12T09:18:32.228Z] 28: <futures::future::lazy::Lazy<F,R> as futures::future::Future>::poll
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/future/lazy.rs:82
[2020-03-12T09:18:32.228Z] 29: futures::task_impl::Spawn<T>::poll_future_notify::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/mod.rs:329
[2020-03-12T09:18:32.228Z] 30: futures::task_impl::Spawn<T>::enter::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/mod.rs:399
[2020-03-12T09:18:32.228Z] 31: futures::task_impl::std::set
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/std/mod.rs:83
[2020-03-12T09:18:32.228Z] 32: futures::task_impl::Spawn<T>::enter
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/mod.rs:399
[2020-03-12T09:18:32.228Z] 33: futures::task_impl::Spawn<T>::poll_fn_notify
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/mod.rs:291
[2020-03-12T09:18:32.228Z] 34: futures::task_impl::Spawn<T>::poll_future_notify
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/mod.rs:329
[2020-03-12T09:18:32.228Z] 35: tokio_current_thread::Entered<P>::block_on::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-current-thread-0.1.6/src/lib.rs:494
[2020-03-12T09:18:32.228Z] 36: tokio_current_thread::Borrow<U>::enter::{{closure}}::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-current-thread-0.1.6/src/lib.rs:788
[2020-03-12T09:18:32.228Z] 37: tokio_current_thread::CurrentRunner::set_spawn
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-current-thread-0.1.6/src/lib.rs:825
[2020-03-12T09:18:32.228Z] 38: tokio_current_thread::Borrow<U>::enter::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-current-thread-0.1.6/src/lib.rs:788
[2020-03-12T09:18:32.228Z] 39: std::thread::local::LocalKey<T>::try_with
[2020-03-12T09:18:32.228Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/thread/local.rs:262
[2020-03-12T09:18:32.228Z] 40: std::thread::local::LocalKey<T>::with
[2020-03-12T09:18:32.228Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/thread/local.rs:239
[2020-03-12T09:18:32.228Z] 41: tokio_current_thread::Borrow<U>::enter
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-current-thread-0.1.6/src/lib.rs:786
[2020-03-12T09:18:32.228Z] 42: tokio_current_thread::Entered<P>::block_on
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-current-thread-0.1.6/src/lib.rs:491
[2020-03-12T09:18:32.228Z] 43: tokio_core::reactor::Core::run::{{closure}}::{{closure}}::{{closure}}::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-core-0.1.17/src/reactor/mod.rs:234
[2020-03-12T09:18:32.228Z] 44: tokio_timer::timer::handle::with_default::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-timer-0.2.11/src/timer/handle.rs:101
[2020-03-12T09:18:32.228Z] 45: std::thread::local::LocalKey<T>::try_with
[2020-03-12T09:18:32.228Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/thread/local.rs:262
[2020-03-12T09:18:32.228Z] 46: std::thread::local::LocalKey<T>::with
[2020-03-12T09:18:32.228Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/thread/local.rs:239
[2020-03-12T09:18:32.228Z] 47: tokio_timer::timer::handle::with_default
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-timer-0.2.11/src/timer/handle.rs:84
[2020-03-12T09:18:32.228Z] 48: tokio_core::reactor::Core::run::{{closure}}::{{closure}}::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-core-0.1.17/src/reactor/mod.rs:233
[2020-03-12T09:18:32.228Z] 49: tokio_executor::global::with_default::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-executor-0.1.8/src/global.rs:209
[2020-03-12T09:18:32.228Z] 50: std::thread::local::LocalKey<T>::try_with
[2020-03-12T09:18:32.228Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/thread/local.rs:262
[2020-03-12T09:18:32.228Z] 51: std::thread::local::LocalKey<T>::with
[2020-03-12T09:18:32.228Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/thread/local.rs:239
[2020-03-12T09:18:32.228Z] 52: tokio_executor::global::with_default
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-executor-0.1.8/src/global.rs:178
[2020-03-12T09:18:32.228Z] 53: tokio_core::reactor::Core::run::{{closure}}::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-core-0.1.17/src/reactor/mod.rs:232
[2020-03-12T09:18:32.228Z] 54: tokio_reactor::with_default::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-reactor-0.1.9/src/lib.rs:237
[2020-03-12T09:18:32.228Z] 55: std::thread::local::LocalKey<T>::try_with
[2020-03-12T09:18:32.228Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/thread/local.rs:262
[2020-03-12T09:18:32.228Z] 56: std::thread::local::LocalKey<T>::with
[2020-03-12T09:18:32.228Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/thread/local.rs:239
[2020-03-12T09:18:32.228Z] 57: tokio_reactor::with_default
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-reactor-0.1.9/src/lib.rs:217
[2020-03-12T09:18:32.228Z] 58: tokio_core::reactor::Core::run::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-core-0.1.17/src/reactor/mod.rs:231
[2020-03-12T09:18:32.228Z] 59: scoped_tls::ScopedKey<T>::set
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/scoped-tls-0.1.2/src/lib.rs:155
[2020-03-12T09:18:32.228Z] 60: tokio_core::reactor::Core::run
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-core-0.1.17/src/reactor/mod.rs:230
[2020-03-12T09:18:32.228Z] 61: tikv_util::worker::future::poll
[2020-03-12T09:18:32.228Z] at ./components/tikv_util/src/worker/future.rs:114
[2020-03-12T09:18:32.228Z] 62: tikv_util::worker::future::Worker<T>::start::{{closure}}
[2020-03-12T09:18:32.228Z] at ./components/tikv_util/src/worker/future.rs:145
[2020-03-12T09:18:32.228Z] note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
```
| 1.0 | test raftstore::test_snap::test_node_cf_snapshot ... thread 'test-pd-worker' panicked - raftstore::test_snap::test_node_cf_snapshot
https://internal.pingcap.net/idc-jenkins/blue/organizations/jenkins/tikv_ghpr_test/detail/tikv_ghpr_test/18544/pipeline/226 Integration Part13
```
[2020-03-12T09:18:31.658Z] test raftstore::test_snap::test_node_cf_snapshot ... thread 'test-pd-worker' panicked at 'called `Option::unwrap()` on a `None` value', /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libcore/macros/mod.rs:15:40
[2020-03-12T09:18:31.658Z] stack backtrace:
[2020-03-12T09:18:32.227Z] 0: backtrace::backtrace::libunwind::trace
[2020-03-12T09:18:32.227Z] at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88
[2020-03-12T09:18:32.227Z] 1: backtrace::backtrace::trace_unsynchronized
[2020-03-12T09:18:32.227Z] at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66
[2020-03-12T09:18:32.227Z] 2: std::sys_common::backtrace::_print_fmt
[2020-03-12T09:18:32.227Z] at src/libstd/sys_common/backtrace.rs:84
[2020-03-12T09:18:32.227Z] 3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
[2020-03-12T09:18:32.227Z] at src/libstd/sys_common/backtrace.rs:61
[2020-03-12T09:18:32.227Z] 4: core::fmt::write
[2020-03-12T09:18:32.227Z] at src/libcore/fmt/mod.rs:1025
[2020-03-12T09:18:32.227Z] 5: std::io::Write::write_fmt
[2020-03-12T09:18:32.227Z] at src/libstd/io/mod.rs:1426
[2020-03-12T09:18:32.227Z] 6: std::sys_common::backtrace::_print
[2020-03-12T09:18:32.227Z] at src/libstd/sys_common/backtrace.rs:65
[2020-03-12T09:18:32.227Z] 7: std::sys_common::backtrace::print
[2020-03-12T09:18:32.227Z] at src/libstd/sys_common/backtrace.rs:50
[2020-03-12T09:18:32.227Z] 8: std::panicking::default_hook::{{closure}}
[2020-03-12T09:18:32.227Z] at src/libstd/panicking.rs:193
[2020-03-12T09:18:32.227Z] 9: std::panicking::default_hook
[2020-03-12T09:18:32.227Z] at src/libstd/panicking.rs:210
[2020-03-12T09:18:32.227Z] 10: std::panicking::rust_panic_with_hook
[2020-03-12T09:18:32.227Z] at src/libstd/panicking.rs:471
[2020-03-12T09:18:32.227Z] 11: rust_begin_unwind
[2020-03-12T09:18:32.227Z] at src/libstd/panicking.rs:375
[2020-03-12T09:18:32.227Z] 12: core::panicking::panic_fmt
[2020-03-12T09:18:32.227Z] at src/libcore/panicking.rs:84
[2020-03-12T09:18:32.227Z] 13: core::panicking::panic
[2020-03-12T09:18:32.227Z] at src/libcore/panicking.rs:51
[2020-03-12T09:18:32.227Z] 14: core::option::Option<T>::unwrap
[2020-03-12T09:18:32.227Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libcore/macros/mod.rs:15
[2020-03-12T09:18:32.227Z] 15: <test_raftstore::pd::TestPdClient as pd_client::PdClient>::handle_region_heartbeat_response
[2020-03-12T09:18:32.227Z] at components/test_raftstore/src/pd.rs:1091
[2020-03-12T09:18:32.227Z] 16: raftstore::store::worker::pd::Runner<T>::schedule_heartbeat_receiver
[2020-03-12T09:18:32.227Z] at ./components/raftstore/src/store/worker/pd.rs:705
[2020-03-12T09:18:32.227Z] 17: <raftstore::store::worker::pd::Runner<T> as tikv_util::worker::future::Runnable<raftstore::store::worker::pd::Task>>::run
[2020-03-12T09:18:32.227Z] at ./components/raftstore/src/store/worker/pd.rs:847
[2020-03-12T09:18:32.227Z] 18: tikv_util::worker::future::poll::{{closure}}
[2020-03-12T09:18:32.227Z] at ./components/tikv_util/src/worker/future.rs:108
[2020-03-12T09:18:32.227Z] 19: <futures::stream::for_each::ForEach<S,F,U> as futures::future::Future>::poll
[2020-03-12T09:18:32.227Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/stream/for_each.rs:46
[2020-03-12T09:18:32.227Z] 20: futures::task_impl::Spawn<T>::poll_future_notify::{{closure}}
[2020-03-12T09:18:32.227Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/mod.rs:329
[2020-03-12T09:18:32.227Z] 21: futures::task_impl::Spawn<T>::enter::{{closure}}
[2020-03-12T09:18:32.227Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/mod.rs:399
[2020-03-12T09:18:32.227Z] 22: futures::task_impl::std::set
[2020-03-12T09:18:32.227Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/std/mod.rs:83
[2020-03-12T09:18:32.227Z] 23: futures::task_impl::Spawn<T>::enter
[2020-03-12T09:18:32.227Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/mod.rs:399
[2020-03-12T09:18:32.227Z] 24: futures::task_impl::Spawn<T>::poll_fn_notify
[2020-03-12T09:18:32.227Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/mod.rs:291
[2020-03-12T09:18:32.228Z] 25: futures::task_impl::Spawn<T>::poll_future_notify
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/mod.rs:329
[2020-03-12T09:18:32.228Z] 26: tokio_core::reactor::Core::run::{{closure}}::{{closure}}::{{closure}}::{{closure}}::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-core-0.1.17/src/reactor/mod.rs:236
[2020-03-12T09:18:32.228Z] 27: futures::future::lazy::Lazy<F,R>::get
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/future/lazy.rs:64
[2020-03-12T09:18:32.228Z] 28: <futures::future::lazy::Lazy<F,R> as futures::future::Future>::poll
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/future/lazy.rs:82
[2020-03-12T09:18:32.228Z] 29: futures::task_impl::Spawn<T>::poll_future_notify::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/mod.rs:329
[2020-03-12T09:18:32.228Z] 30: futures::task_impl::Spawn<T>::enter::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/mod.rs:399
[2020-03-12T09:18:32.228Z] 31: futures::task_impl::std::set
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/std/mod.rs:83
[2020-03-12T09:18:32.228Z] 32: futures::task_impl::Spawn<T>::enter
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/mod.rs:399
[2020-03-12T09:18:32.228Z] 33: futures::task_impl::Spawn<T>::poll_fn_notify
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/mod.rs:291
[2020-03-12T09:18:32.228Z] 34: futures::task_impl::Spawn<T>::poll_future_notify
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/futures-0.1.29/src/task_impl/mod.rs:329
[2020-03-12T09:18:32.228Z] 35: tokio_current_thread::Entered<P>::block_on::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-current-thread-0.1.6/src/lib.rs:494
[2020-03-12T09:18:32.228Z] 36: tokio_current_thread::Borrow<U>::enter::{{closure}}::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-current-thread-0.1.6/src/lib.rs:788
[2020-03-12T09:18:32.228Z] 37: tokio_current_thread::CurrentRunner::set_spawn
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-current-thread-0.1.6/src/lib.rs:825
[2020-03-12T09:18:32.228Z] 38: tokio_current_thread::Borrow<U>::enter::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-current-thread-0.1.6/src/lib.rs:788
[2020-03-12T09:18:32.228Z] 39: std::thread::local::LocalKey<T>::try_with
[2020-03-12T09:18:32.228Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/thread/local.rs:262
[2020-03-12T09:18:32.228Z] 40: std::thread::local::LocalKey<T>::with
[2020-03-12T09:18:32.228Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/thread/local.rs:239
[2020-03-12T09:18:32.228Z] 41: tokio_current_thread::Borrow<U>::enter
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-current-thread-0.1.6/src/lib.rs:786
[2020-03-12T09:18:32.228Z] 42: tokio_current_thread::Entered<P>::block_on
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-current-thread-0.1.6/src/lib.rs:491
[2020-03-12T09:18:32.228Z] 43: tokio_core::reactor::Core::run::{{closure}}::{{closure}}::{{closure}}::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-core-0.1.17/src/reactor/mod.rs:234
[2020-03-12T09:18:32.228Z] 44: tokio_timer::timer::handle::with_default::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-timer-0.2.11/src/timer/handle.rs:101
[2020-03-12T09:18:32.228Z] 45: std::thread::local::LocalKey<T>::try_with
[2020-03-12T09:18:32.228Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/thread/local.rs:262
[2020-03-12T09:18:32.228Z] 46: std::thread::local::LocalKey<T>::with
[2020-03-12T09:18:32.228Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/thread/local.rs:239
[2020-03-12T09:18:32.228Z] 47: tokio_timer::timer::handle::with_default
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-timer-0.2.11/src/timer/handle.rs:84
[2020-03-12T09:18:32.228Z] 48: tokio_core::reactor::Core::run::{{closure}}::{{closure}}::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-core-0.1.17/src/reactor/mod.rs:233
[2020-03-12T09:18:32.228Z] 49: tokio_executor::global::with_default::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-executor-0.1.8/src/global.rs:209
[2020-03-12T09:18:32.228Z] 50: std::thread::local::LocalKey<T>::try_with
[2020-03-12T09:18:32.228Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/thread/local.rs:262
[2020-03-12T09:18:32.228Z] 51: std::thread::local::LocalKey<T>::with
[2020-03-12T09:18:32.228Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/thread/local.rs:239
[2020-03-12T09:18:32.228Z] 52: tokio_executor::global::with_default
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-executor-0.1.8/src/global.rs:178
[2020-03-12T09:18:32.228Z] 53: tokio_core::reactor::Core::run::{{closure}}::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-core-0.1.17/src/reactor/mod.rs:232
[2020-03-12T09:18:32.228Z] 54: tokio_reactor::with_default::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-reactor-0.1.9/src/lib.rs:237
[2020-03-12T09:18:32.228Z] 55: std::thread::local::LocalKey<T>::try_with
[2020-03-12T09:18:32.228Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/thread/local.rs:262
[2020-03-12T09:18:32.228Z] 56: std::thread::local::LocalKey<T>::with
[2020-03-12T09:18:32.228Z] at /rustc/0de96d37fbcc54978458c18f5067cd9817669bc8/src/libstd/thread/local.rs:239
[2020-03-12T09:18:32.228Z] 57: tokio_reactor::with_default
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-reactor-0.1.9/src/lib.rs:217
[2020-03-12T09:18:32.228Z] 58: tokio_core::reactor::Core::run::{{closure}}
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-core-0.1.17/src/reactor/mod.rs:231
[2020-03-12T09:18:32.228Z] 59: scoped_tls::ScopedKey<T>::set
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/scoped-tls-0.1.2/src/lib.rs:155
[2020-03-12T09:18:32.228Z] 60: tokio_core::reactor::Core::run
[2020-03-12T09:18:32.228Z] at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-core-0.1.17/src/reactor/mod.rs:230
[2020-03-12T09:18:32.228Z] 61: tikv_util::worker::future::poll
[2020-03-12T09:18:32.228Z] at ./components/tikv_util/src/worker/future.rs:114
[2020-03-12T09:18:32.228Z] 62: tikv_util::worker::future::Worker<T>::start::{{closure}}
[2020-03-12T09:18:32.228Z] at ./components/tikv_util/src/worker/future.rs:145
[2020-03-12T09:18:32.228Z] note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
```
| test | test raftstore test snap test node cf snapshot thread test pd worker panicked raftstore test snap test node cf snapshot integration test raftstore test snap test node cf snapshot thread test pd worker panicked at called option unwrap on a none value rustc src libcore macros mod rs stack backtrace backtrace backtrace libunwind trace at cargo registry src github com backtrace src backtrace libunwind rs backtrace backtrace trace unsynchronized at cargo registry src github com backtrace src backtrace mod rs std sys common backtrace print fmt at src libstd sys common backtrace rs fmt at src libstd sys common backtrace rs core fmt write at src libcore fmt mod rs std io write write fmt at src libstd io mod rs std sys common backtrace print at src libstd sys common backtrace rs std sys common backtrace print at src libstd sys common backtrace rs std panicking default hook closure at src libstd panicking rs std panicking default hook at src libstd panicking rs std panicking rust panic with hook at src libstd panicking rs rust begin unwind at src libstd panicking rs core panicking panic fmt at src libcore panicking rs core panicking panic at src libcore panicking rs core option option unwrap at rustc src libcore macros mod rs handle region heartbeat response at components test raftstore src pd rs raftstore store worker pd runner schedule heartbeat receiver at components raftstore src store worker pd rs as tikv util worker future runnable run at components raftstore src store worker pd rs tikv util worker future poll closure at components tikv util src worker future rs as futures future future poll at rust registry src github com futures src stream for each rs futures task impl spawn poll future notify closure at rust registry src github com futures src task impl mod rs futures task impl spawn enter closure at rust registry src github com futures src task impl mod rs futures task impl std set at rust registry src github com futures src task impl std mod rs futures task impl spawn enter at rust registry src github com futures src task impl mod rs futures task impl spawn poll fn notify at rust registry src github com futures src task impl mod rs futures task impl spawn poll future notify at rust registry src github com futures src task impl mod rs tokio core reactor core run closure closure closure closure closure at rust registry src github com tokio core src reactor mod rs futures future lazy lazy get at rust registry src github com futures src future lazy rs as futures future future poll at rust registry src github com futures src future lazy rs futures task impl spawn poll future notify closure at rust registry src github com futures src task impl mod rs futures task impl spawn enter closure at rust registry src github com futures src task impl mod rs futures task impl std set at rust registry src github com futures src task impl std mod rs futures task impl spawn enter at rust registry src github com futures src task impl mod rs futures task impl spawn poll fn notify at rust registry src github com futures src task impl mod rs futures task impl spawn poll future notify at rust registry src github com futures src task impl mod rs tokio current thread entered block on closure at rust registry src github com tokio current thread src lib rs tokio current thread borrow enter closure closure at rust registry src github com tokio current thread src lib rs tokio current thread currentrunner set spawn at rust registry src github com tokio current thread src lib rs tokio current thread borrow enter closure at rust registry src github com tokio current thread src lib rs std thread local localkey try with at rustc src libstd thread local rs std thread local localkey with at rustc src libstd thread local rs tokio current thread borrow enter at rust registry src github com tokio current thread src lib rs tokio current thread entered block on at rust registry src github com tokio current thread src lib rs tokio core reactor core run closure closure closure closure at rust registry src github com tokio core src reactor mod rs tokio timer timer handle with default closure at rust registry src github com tokio timer src timer handle rs std thread local localkey try with at rustc src libstd thread local rs std thread local localkey with at rustc src libstd thread local rs tokio timer timer handle with default at rust registry src github com tokio timer src timer handle rs tokio core reactor core run closure closure closure at rust registry src github com tokio core src reactor mod rs tokio executor global with default closure at rust registry src github com tokio executor src global rs std thread local localkey try with at rustc src libstd thread local rs std thread local localkey with at rustc src libstd thread local rs tokio executor global with default at rust registry src github com tokio executor src global rs tokio core reactor core run closure closure at rust registry src github com tokio core src reactor mod rs tokio reactor with default closure at rust registry src github com tokio reactor src lib rs std thread local localkey try with at rustc src libstd thread local rs std thread local localkey with at rustc src libstd thread local rs tokio reactor with default at rust registry src github com tokio reactor src lib rs tokio core reactor core run closure at rust registry src github com tokio core src reactor mod rs scoped tls scopedkey set at rust registry src github com scoped tls src lib rs tokio core reactor core run at rust registry src github com tokio core src reactor mod rs tikv util worker future poll at components tikv util src worker future rs tikv util worker future worker start closure at components tikv util src worker future rs note some details are omitted run with rust backtrace full for a verbose backtrace | 1 |
321,725 | 27,550,000,117 | IssuesEvent | 2023-03-07 14:22:31 | bit-team/backintime | https://api.github.com/repos/bit-team/backintime | closed | backintime-cli fails unit tests (Gtk-WARNING ... Theme parsing error) | Qt Distro-Specific External Cosmetics Testing | Attempting to install v1.3.3-3
Both backintime and backintime-cli fail with the same test failure.
OS: Arch/Xfce
```
======================================================================
FAIL: test_local_snapshot_is_successful (test.test_backintime.TestBackInTime)
end to end test - from BIT initialization through snapshot
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/kaibutsux/.cache/yay/backintime/src/backintime-1.3.3/common/test/test_backintime.py", line 147, in test_local_snapshot_is_successful
self.assertRegex(filtered_log_output, re.compile(r'''INFO: Lock
AssertionError: Regex didn't match: 'INFO: Lock\nINFO: Take a new snapshot. Profile: 1 Main profile\nINFO: Call rsync to take the snapshot\nINFO: Save config file\nINFO: Save permissions\nINFO: Create info file\nINFO: Unlock\n' not found in "INFO: Lock\nINFO: Take a new snapshot. Profile: 1 Main profile\nINFO: Call rsync to take the snapshot\nINFO: Save config file\nINFO: Save permissions\nINFO: Create info file\n\n(python:2194333): Gtk-WARNING **: 10:20:50.946: Theme parsing error: gtk.css:4419:85: '/*' in comment block\n\n(python:2194333): Gtk-WARNING **: 10:20:50.946: Theme parsing error: gtk.css:4512:64: '/*' in comment block\nINFO: Unlock\n"
----------------------------------------------------------------------
Ran 3 tests in 3.388s
FAILED (failures=1, skipped=1)
make: *** [Makefile:570: unittest] Error 1
==> ERROR: A failure occurred in check().
Aborting...
-> error making: backintime (backintime-cli backintime)
``` | 1.0 | backintime-cli fails unit tests (Gtk-WARNING ... Theme parsing error) - Attempting to install v1.3.3-3
Both backintime and backintime-cli fail with the same test failure.
OS: Arch/Xfce
```
======================================================================
FAIL: test_local_snapshot_is_successful (test.test_backintime.TestBackInTime)
end to end test - from BIT initialization through snapshot
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/kaibutsux/.cache/yay/backintime/src/backintime-1.3.3/common/test/test_backintime.py", line 147, in test_local_snapshot_is_successful
self.assertRegex(filtered_log_output, re.compile(r'''INFO: Lock
AssertionError: Regex didn't match: 'INFO: Lock\nINFO: Take a new snapshot. Profile: 1 Main profile\nINFO: Call rsync to take the snapshot\nINFO: Save config file\nINFO: Save permissions\nINFO: Create info file\nINFO: Unlock\n' not found in "INFO: Lock\nINFO: Take a new snapshot. Profile: 1 Main profile\nINFO: Call rsync to take the snapshot\nINFO: Save config file\nINFO: Save permissions\nINFO: Create info file\n\n(python:2194333): Gtk-WARNING **: 10:20:50.946: Theme parsing error: gtk.css:4419:85: '/*' in comment block\n\n(python:2194333): Gtk-WARNING **: 10:20:50.946: Theme parsing error: gtk.css:4512:64: '/*' in comment block\nINFO: Unlock\n"
----------------------------------------------------------------------
Ran 3 tests in 3.388s
FAILED (failures=1, skipped=1)
make: *** [Makefile:570: unittest] Error 1
==> ERROR: A failure occurred in check().
Aborting...
-> error making: backintime (backintime-cli backintime)
``` | test | backintime cli fails unit tests gtk warning theme parsing error attempting to install both backintime and backintime cli fail with the same test failure os arch xfce fail test local snapshot is successful test test backintime testbackintime end to end test from bit initialization through snapshot traceback most recent call last file home kaibutsux cache yay backintime src backintime common test test backintime py line in test local snapshot is successful self assertregex filtered log output re compile r info lock assertionerror regex didn t match info lock ninfo take a new snapshot profile main profile ninfo call rsync to take the snapshot ninfo save config file ninfo save permissions ninfo create info file ninfo unlock n not found in info lock ninfo take a new snapshot profile main profile ninfo call rsync to take the snapshot ninfo save config file ninfo save permissions ninfo create info file n n python gtk warning theme parsing error gtk css in comment block n n python gtk warning theme parsing error gtk css in comment block ninfo unlock n ran tests in failed failures skipped make error error a failure occurred in check aborting error making backintime backintime cli backintime | 1 |
229,531 | 25,362,269,579 | IssuesEvent | 2022-11-21 01:01:46 | YauheniPo/PDF-Parser-HTTPS-client | https://api.github.com/repos/YauheniPo/PDF-Parser-HTTPS-client | closed | CVE-2020-9488 (Low) detected in log4j-core-2.11.1.jar - autoclosed | security vulnerability | ## CVE-2020-9488 - Low Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>log4j-core-2.11.1.jar</b></p></summary>
<p>The Apache Log4j Implementation</p>
<p>Library home page: <a href="https://logging.apache.org/log4j/2.x/">https://logging.apache.org/log4j/2.x/</a></p>
<p>Path to dependency file: PDF-Parser-HTTPS-client/pom.xml</p>
<p>Path to vulnerable library: canner/.m2/repository/org/apache/logging/log4j/log4j-core/2.11.1/log4j-core-2.11.1.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-core-2.11.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/YauheniPo/PDF-Parser-HTTPS-client/commit/95bb8dd5e9e08337986bf37c5ebd0d2c52ddab94">95bb8dd5e9e08337986bf37c5ebd0d2c52ddab94</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender.
<p>Publish Date: 2020-04-27
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9488>CVE-2020-9488</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>3.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: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://issues.apache.org/jira/browse/LOG4J2-2819">https://issues.apache.org/jira/browse/LOG4J2-2819</a></p>
<p>Release Date: 2020-04-27</p>
<p>Fix Resolution: org.apache.logging.log4j:log4j-core:2.13.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-2020-9488 (Low) detected in log4j-core-2.11.1.jar - autoclosed - ## CVE-2020-9488 - Low Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>log4j-core-2.11.1.jar</b></p></summary>
<p>The Apache Log4j Implementation</p>
<p>Library home page: <a href="https://logging.apache.org/log4j/2.x/">https://logging.apache.org/log4j/2.x/</a></p>
<p>Path to dependency file: PDF-Parser-HTTPS-client/pom.xml</p>
<p>Path to vulnerable library: canner/.m2/repository/org/apache/logging/log4j/log4j-core/2.11.1/log4j-core-2.11.1.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-core-2.11.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/YauheniPo/PDF-Parser-HTTPS-client/commit/95bb8dd5e9e08337986bf37c5ebd0d2c52ddab94">95bb8dd5e9e08337986bf37c5ebd0d2c52ddab94</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender.
<p>Publish Date: 2020-04-27
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9488>CVE-2020-9488</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>3.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: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://issues.apache.org/jira/browse/LOG4J2-2819">https://issues.apache.org/jira/browse/LOG4J2-2819</a></p>
<p>Release Date: 2020-04-27</p>
<p>Fix Resolution: org.apache.logging.log4j:log4j-core:2.13.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_test | cve low detected in core jar autoclosed cve low severity vulnerability vulnerable library core jar the apache implementation library home page a href path to dependency file pdf parser https client pom xml path to vulnerable library canner repository org apache logging core core jar dependency hierarchy x core jar vulnerable library found in head commit a href found in base branch master vulnerability details improper validation of certificate with host mismatch in apache smtp appender this could allow an smtps connection to be intercepted by a man in the middle attack which could leak any log messages sent through that appender publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache logging core step up your open source security game with whitesource | 0 |
39,380 | 12,663,424,120 | IssuesEvent | 2020-06-18 01:18:49 | phytomichael/KSA | https://api.github.com/repos/phytomichael/KSA | opened | CVE-2019-20445 (High) detected in netty-all-4.0.33.Final.jar | security vulnerability | ## CVE-2019-20445 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>netty-all-4.0.33.Final.jar</b></p></summary>
<p>Netty is an asynchronous event-driven network application framework for
rapid development of maintainable high performance protocol servers and
clients.</p>
<p>Library home page: <a href="http://netty.io/">http://netty.io/</a></p>
<p>Path to dependency file: /KSA/ksa/ksa/ksa-web-root/ksa-finance-web/pom.xml</p>
<p>Path to vulnerable library: 2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,/KSA/ksa/ksa/ksa-web-root/ksa-web/target/ROOT/WEB-INF/lib/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar</p>
<p>
Dependency Hierarchy:
- :x: **netty-all-4.0.33.Final.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
HttpObjectDecoder.java in Netty before 4.1.44 allows a Content-Length header to be accompanied by a second Content-Length header, or by a Transfer-Encoding header.
<p>Publish Date: 2020-01-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20445>CVE-2019-20445</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.1</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: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20445">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20445</a></p>
<p>Release Date: 2020-01-29</p>
<p>Fix Resolution: io.netty:netty-codec-http:4.1.44</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"io.netty","packageName":"netty-all","packageVersion":"4.0.33.Final","isTransitiveDependency":false,"dependencyTree":"io.netty:netty-all:4.0.33.Final","isMinimumFixVersionAvailable":true,"minimumFixVersion":"io.netty:netty-codec-http:4.1.44"}],"vulnerabilityIdentifier":"CVE-2019-20445","vulnerabilityDetails":"HttpObjectDecoder.java in Netty before 4.1.44 allows a Content-Length header to be accompanied by a second Content-Length header, or by a Transfer-Encoding header.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20445","cvss3Severity":"high","cvss3Score":"9.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2019-20445 (High) detected in netty-all-4.0.33.Final.jar - ## CVE-2019-20445 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>netty-all-4.0.33.Final.jar</b></p></summary>
<p>Netty is an asynchronous event-driven network application framework for
rapid development of maintainable high performance protocol servers and
clients.</p>
<p>Library home page: <a href="http://netty.io/">http://netty.io/</a></p>
<p>Path to dependency file: /KSA/ksa/ksa/ksa-web-root/ksa-finance-web/pom.xml</p>
<p>Path to vulnerable library: 2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,/KSA/ksa/ksa/ksa-web-root/ksa-web/target/ROOT/WEB-INF/lib/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar,2/repository/io/netty/netty-all/4.0.33.Final/netty-all-4.0.33.Final.jar</p>
<p>
Dependency Hierarchy:
- :x: **netty-all-4.0.33.Final.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
HttpObjectDecoder.java in Netty before 4.1.44 allows a Content-Length header to be accompanied by a second Content-Length header, or by a Transfer-Encoding header.
<p>Publish Date: 2020-01-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20445>CVE-2019-20445</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.1</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: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20445">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20445</a></p>
<p>Release Date: 2020-01-29</p>
<p>Fix Resolution: io.netty:netty-codec-http:4.1.44</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"io.netty","packageName":"netty-all","packageVersion":"4.0.33.Final","isTransitiveDependency":false,"dependencyTree":"io.netty:netty-all:4.0.33.Final","isMinimumFixVersionAvailable":true,"minimumFixVersion":"io.netty:netty-codec-http:4.1.44"}],"vulnerabilityIdentifier":"CVE-2019-20445","vulnerabilityDetails":"HttpObjectDecoder.java in Netty before 4.1.44 allows a Content-Length header to be accompanied by a second Content-Length header, or by a Transfer-Encoding header.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20445","cvss3Severity":"high","cvss3Score":"9.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_test | cve high detected in netty all final jar cve high severity vulnerability vulnerable library netty all final jar netty is an asynchronous event driven network application framework for rapid development of maintainable high performance protocol servers and clients library home page a href path to dependency file ksa ksa ksa ksa web root ksa finance web pom xml path to vulnerable library repository io netty netty all final netty all final jar repository io netty netty all final netty all final jar repository io netty netty all final netty all final jar ksa ksa ksa ksa web root ksa web target root web inf lib netty all final jar repository io netty netty all final netty all final jar repository io netty netty all final netty all final jar repository io netty netty all final netty all final jar repository io netty netty all final netty all final jar repository io netty netty all final netty all final jar repository io netty netty all final netty all final jar repository io netty netty all final netty all final jar repository io netty netty all final netty all final jar repository io netty netty all final netty all final jar repository io netty netty all final netty all final jar repository io netty netty all final netty all final jar repository io netty netty all final netty all final jar repository io netty netty all final netty all final jar repository io netty netty all final netty all final jar repository io netty netty all final netty all final jar repository io netty netty all final netty all final jar dependency hierarchy x netty all final jar vulnerable library vulnerability details httpobjectdecoder java in netty before allows a content length header to be accompanied by a second content length header or by a transfer encoding header 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 none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution io netty netty codec http check this box to open an automated fix pr isopenpronvulnerability false ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails httpobjectdecoder java in netty before allows a content length header to be accompanied by a second content length header or by a transfer encoding header vulnerabilityurl | 0 |
100,441 | 8,743,507,748 | IssuesEvent | 2018-12-12 19:22:15 | brave/brave-browser | https://api.github.com/repos/brave/brave-browser | opened | Unable to refresh or open the inbox, if a PDF file is already opened in another tab. | QA/Test-Plan-Specified QA/Yes bug | <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue.
PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->
## Description
Unable to refresh or open the inbox,if a PDF file is already opened in another tab.
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
1. Launch brave with clean profile and open gmail.com
2. Open a PDF file attached in an email
3. Click on `Print` icon and PDF gets opened in another tab
4. Do refresh on the tab where gmail.com is opened (Refresh either by clicking on browser refresh button or page re-load)
## Actual result:
It will never reload the inbox, keeps showing the message `Gmail Loading`. Inbox will not open until you close PDF file which is opened in another tab
## Expected result:
Should reload the gmail inbox page
## Reproduces how often:
Always
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->
Brave | 0.58.11 Chromium: 71.0.3578.80 (Official Build) beta (64-bit)
-- | --
Revision | 2ac50e7249fbd55e6f517a28131605c9fb9fe897-refs/branch-heads/3578@{#860}
OS | Windows
### Reproducible on current release: NO
- Does it reproduce on brave-browser dev/beta builds? Yes
### Website problems only:
- Does the issue resolve itself when disabling Brave Shields? No
- Is the issue reproducible on the latest version of Chrome? No
### Additional Information
<!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue-->
| 1.0 | Unable to refresh or open the inbox, if a PDF file is already opened in another tab. - <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue.
PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->
## Description
Unable to refresh or open the inbox,if a PDF file is already opened in another tab.
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
1. Launch brave with clean profile and open gmail.com
2. Open a PDF file attached in an email
3. Click on `Print` icon and PDF gets opened in another tab
4. Do refresh on the tab where gmail.com is opened (Refresh either by clicking on browser refresh button or page re-load)
## Actual result:
It will never reload the inbox, keeps showing the message `Gmail Loading`. Inbox will not open until you close PDF file which is opened in another tab
## Expected result:
Should reload the gmail inbox page
## Reproduces how often:
Always
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->
Brave | 0.58.11 Chromium: 71.0.3578.80 (Official Build) beta (64-bit)
-- | --
Revision | 2ac50e7249fbd55e6f517a28131605c9fb9fe897-refs/branch-heads/3578@{#860}
OS | Windows
### Reproducible on current release: NO
- Does it reproduce on brave-browser dev/beta builds? Yes
### Website problems only:
- Does the issue resolve itself when disabling Brave Shields? No
- Is the issue reproducible on the latest version of Chrome? No
### Additional Information
<!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue-->
| test | unable to refresh or open the inbox if a pdf file is already opened in another tab have you searched for similar issues before submitting this issue please check the open issues and add a note before logging a new issue please use the template below to provide information about the issue insufficient info will get the issue closed it will only be reopened after sufficient info is provided description unable to refresh or open the inbox if a pdf file is already opened in another tab steps to reproduce launch brave with clean profile and open gmail com open a pdf file attached in an email click on print icon and pdf gets opened in another tab do refresh on the tab where gmail com is opened refresh either by clicking on browser refresh button or page re load actual result it will never reload the inbox keeps showing the message gmail loading inbox will not open until you close pdf file which is opened in another tab expected result should reload the gmail inbox page reproduces how often always brave version brave version info brave chromium official build beta bit revision refs branch heads os windows reproducible on current release no does it reproduce on brave browser dev beta builds yes website problems only does the issue resolve itself when disabling brave shields no is the issue reproducible on the latest version of chrome no additional information | 1 |
274,925 | 23,880,443,130 | IssuesEvent | 2022-09-08 00:30:28 | Azure/azure-sdk-tools | https://api.github.com/repos/Azure/azure-sdk-tools | opened | GitStore forces a single git command to run in each auto-cloned assets repo | Central-EngSys Asset-Sync Test-Proxy | [If you check the errors here](https://dev.azure.com/azure-sdk/public/_build/results?buildId=1836810&view=logs&j=f8949c67-9d21-53bc-b8db-079dc324f468&t=51108116-18f2-5b30-589b-19b2eea88829)
Here is a snipped error:
```text
2022-09-08T00:01:10.6730087Z Connection id "0HMKH5KHHNGUS", Request id "0HMKH5KHHNGUS:00000002": An unhandled exception was thrown by the application.
2022-09-08T00:01:10.6731217Z Azure.Sdk.Tools.TestProxy.Common.Exceptions.HttpException: Invocation of "git -c advice.detachedHead=false checkout 6260a536f81a057b8cf9586f1b5c18815b7f94b1" had a non-zero exit code -1.
2022-09-08T00:01:10.6732019Z StdOut:
2022-09-08T00:01:10.6732890Z StdErr: fatal: Unable to create '/mnt/vss/_work/1/s/.assets/Azure-azure-sdk-assets/B50E7AFDE01613960F4F7F18F60FB7250F8E2C6D/.git/index.lock': File exists.
2022-09-08T00:01:10.6733507Z
2022-09-08T00:01:10.6733943Z Another git process seems to be running in this repository, e.g.
2022-09-08T00:01:10.6734629Z an editor opened by 'git commit'. Please make sure all processes
2022-09-08T00:01:10.6735178Z are terminated then try again. If it still fails, a git process
2022-09-08T00:01:10.6735683Z may have crashed in this repository earlier:
2022-09-08T00:01:10.6736147Z remove the file manually to continue.
```
So we need to account for this. | 1.0 | GitStore forces a single git command to run in each auto-cloned assets repo - [If you check the errors here](https://dev.azure.com/azure-sdk/public/_build/results?buildId=1836810&view=logs&j=f8949c67-9d21-53bc-b8db-079dc324f468&t=51108116-18f2-5b30-589b-19b2eea88829)
Here is a snipped error:
```text
2022-09-08T00:01:10.6730087Z Connection id "0HMKH5KHHNGUS", Request id "0HMKH5KHHNGUS:00000002": An unhandled exception was thrown by the application.
2022-09-08T00:01:10.6731217Z Azure.Sdk.Tools.TestProxy.Common.Exceptions.HttpException: Invocation of "git -c advice.detachedHead=false checkout 6260a536f81a057b8cf9586f1b5c18815b7f94b1" had a non-zero exit code -1.
2022-09-08T00:01:10.6732019Z StdOut:
2022-09-08T00:01:10.6732890Z StdErr: fatal: Unable to create '/mnt/vss/_work/1/s/.assets/Azure-azure-sdk-assets/B50E7AFDE01613960F4F7F18F60FB7250F8E2C6D/.git/index.lock': File exists.
2022-09-08T00:01:10.6733507Z
2022-09-08T00:01:10.6733943Z Another git process seems to be running in this repository, e.g.
2022-09-08T00:01:10.6734629Z an editor opened by 'git commit'. Please make sure all processes
2022-09-08T00:01:10.6735178Z are terminated then try again. If it still fails, a git process
2022-09-08T00:01:10.6735683Z may have crashed in this repository earlier:
2022-09-08T00:01:10.6736147Z remove the file manually to continue.
```
So we need to account for this. | test | gitstore forces a single git command to run in each auto cloned assets repo here is a snipped error text connection id request id an unhandled exception was thrown by the application azure sdk tools testproxy common exceptions httpexception invocation of git c advice detachedhead false checkout had a non zero exit code stdout stderr fatal unable to create mnt vss work s assets azure azure sdk assets git index lock file exists another git process seems to be running in this repository e g an editor opened by git commit please make sure all processes are terminated then try again if it still fails a git process may have crashed in this repository earlier remove the file manually to continue so we need to account for this | 1 |
88,967 | 8,182,615,231 | IssuesEvent | 2018-08-29 06:05:44 | humera987/HumTestData | https://api.github.com/repos/humera987/HumTestData | opened | Humera_Test_Proj : team_user_signup_valid | Humera_Test_Proj | Project : Humera_Test_Proj
Job : Stg
Env : Stg
Region : FXLabs/US_WEST_1
Result : fail
Status Code : 500
Headers : {}
Endpoint : http://13.57.51.56/users/team-sign-up
Request :
{
"name" : "first name",
"email" : "tQIorG@fxlabs.io",
"password" : "12345678",
"company" : "6dENOKN4U"
}
Response :
I/O error on POST request for "http://13.57.51.56/users/team-sign-up": Connect to 13.57.51.56:80 [/13.57.51.56] failed: Connection refused (Connection refused); nested exception is org.apache.http.conn.HttpHostConnectException: Connect to 13.57.51.56:80 [/13.57.51.56] failed: Connection refused (Connection refused)
Logs :
Assertion [@Response.errors == false] failed, expected value [false] but found []Assertion [@StatusCode == 200] failed, expected value [200] but found [500]
--- FX Bot --- | 1.0 | Humera_Test_Proj : team_user_signup_valid - Project : Humera_Test_Proj
Job : Stg
Env : Stg
Region : FXLabs/US_WEST_1
Result : fail
Status Code : 500
Headers : {}
Endpoint : http://13.57.51.56/users/team-sign-up
Request :
{
"name" : "first name",
"email" : "tQIorG@fxlabs.io",
"password" : "12345678",
"company" : "6dENOKN4U"
}
Response :
I/O error on POST request for "http://13.57.51.56/users/team-sign-up": Connect to 13.57.51.56:80 [/13.57.51.56] failed: Connection refused (Connection refused); nested exception is org.apache.http.conn.HttpHostConnectException: Connect to 13.57.51.56:80 [/13.57.51.56] failed: Connection refused (Connection refused)
Logs :
Assertion [@Response.errors == false] failed, expected value [false] but found []Assertion [@StatusCode == 200] failed, expected value [200] but found [500]
--- FX Bot --- | test | humera test proj team user signup valid project humera test proj job stg env stg region fxlabs us west result fail status code headers endpoint request name first name email tqiorg fxlabs io password company response i o error on post request for connect to failed connection refused connection refused nested exception is org apache http conn httphostconnectexception connect to failed connection refused connection refused logs assertion failed expected value but found assertion failed expected value but found fx bot | 1 |
162,042 | 13,881,374,064 | IssuesEvent | 2020-10-17 23:53:58 | FEUP-ESOF-2020-21/open-cx-t3g3-404datanotfound | https://api.github.com/repos/FEUP-ESOF-2020-21/open-cx-t3g3-404datanotfound | opened | Use Case Diagram | documentation | **Finish Use Case Diagram:**
*I was talking to Abel at the end, and maybe what makes more sense is to have the sponsor with all the basic features, then the other roles inherit the rest and add their specifics, like start a conversation or moderate.* - João Matos | 1.0 | Use Case Diagram - **Finish Use Case Diagram:**
*I was talking to Abel at the end, and maybe what makes more sense is to have the sponsor with all the basic features, then the other roles inherit the rest and add their specifics, like start a conversation or moderate.* - João Matos | non_test | use case diagram finish use case diagram i was talking to abel at the end and maybe what makes more sense is to have the sponsor with all the basic features then the other roles inherit the rest and add their specifics like start a conversation or moderate joão matos | 0 |
6,544 | 2,850,285,981 | IssuesEvent | 2015-05-31 12:55:34 | Atlantic777/mpudp | https://api.github.com/repos/Atlantic777/mpudp | closed | Get ethernet frame length | feature test | Get ethernet frame length. Additional fields in eth_frame_t may be needed. | 1.0 | Get ethernet frame length - Get ethernet frame length. Additional fields in eth_frame_t may be needed. | test | get ethernet frame length get ethernet frame length additional fields in eth frame t may be needed | 1 |
16,611 | 3,546,816,689 | IssuesEvent | 2016-01-20 05:40:11 | tgstation/-tg-station | https://api.github.com/repos/tgstation/-tg-station | closed | Vents set to a different frequency are still available to all air alarms. | Atmos Bug Tested / Reproduced | They cannot be controlled but are still listed in the individual vent control section. | 1.0 | Vents set to a different frequency are still available to all air alarms. - They cannot be controlled but are still listed in the individual vent control section. | test | vents set to a different frequency are still available to all air alarms they cannot be controlled but are still listed in the individual vent control section | 1 |
283,925 | 8,727,997,835 | IssuesEvent | 2018-12-10 16:18:05 | craftercms/craftercms | https://api.github.com/repos/craftercms/craftercms | closed | [sutdio-ui] S3 browse datasources should not have a Type field | bug priority: medium | The S3 browse datasources:
- `S3-repo`
- `image-S3-repo`
- `video-S3-repo`
Should not have the `Type` field. The type parameter should be sent according to the DS type, eg. `type=image` or `type=video`.
| 1.0 | [sutdio-ui] S3 browse datasources should not have a Type field - The S3 browse datasources:
- `S3-repo`
- `image-S3-repo`
- `video-S3-repo`
Should not have the `Type` field. The type parameter should be sent according to the DS type, eg. `type=image` or `type=video`.
| non_test | browse datasources should not have a type field the browse datasources repo image repo video repo should not have the type field the type parameter should be sent according to the ds type eg type image or type video | 0 |
202,874 | 15,305,191,154 | IssuesEvent | 2021-02-24 17:48:29 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | roachtest: tpccbench/nodes=9/cpu=4/chaos/partition failed | C-test-failure O-roachtest O-robot branch-release-20.2 release-blocker | [(roachtest).tpccbench/nodes=9/cpu=4/chaos/partition failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2657161&tab=buildLog) on [release-20.2@8c79e2bc4b35d36c8527f4c40c974f03d9034f46](https://github.com/cockroachdb/cockroach/commits/8c79e2bc4b35d36c8527f4c40c974f03d9034f46):
```
The test failed on branch=release-20.2, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/tpccbench/nodes=9/cpu=4/chaos/partition/run_1
cluster.go:2654,tpcc.go:735,tpcc.go:576,test_runner.go:755: monitor failure: monitor task failed: failed with output "./workload: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by ./workload)\nError: COMMAND_PROBLEM: exit status 1\n(1) COMMAND_PROBLEM\nWraps: (2) Node 10. Command with error:\n | ```\n | ./workload run tpcc --warehouses=2000 --workers=2000 --max-rate=1000 --wait=false --duration=16m0s --scatter --tolerate-errors {pgurl:1-9}\n | ```\nWraps: (3) exit status 1\nError types: (1) errors.Cmd (2) *hintdetail.withDetail (3) *exec.ExitError\n": /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod run teamcity-2657161-1612856692-131-n10cpu4:10 -- ./workload run tpcc --warehouses=2000 --workers=2000 --max-rate=1000 --wait=false --duration=16m0s --scatter --tolerate-errors {pgurl:1-9}: exit status 20
(1) attached stack trace
-- stack trace:
| main.(*monitor).WaitE
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2642
| main.(*monitor).Wait
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2650
| main.runTPCCBench
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tpcc.go:735
| main.registerTPCCBenchSpec.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tpcc.go:576
| main.(*testRunner).runTest.func2
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/test_runner.go:755
Wraps: (2) monitor failure
Wraps: (3) attached stack trace
-- stack trace:
| main.(*monitor).wait.func2
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2698
Wraps: (4) monitor task failed
Wraps: (5) attached stack trace
-- stack trace:
| main.loadTPCCBench
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tpcc.go:663
| [...repeated from below...]
Wraps: (6) failed with output "./workload: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by ./workload)\nError: COMMAND_PROBLEM: exit status 1\n(1) COMMAND_PROBLEM\nWraps: (2) Node 10. Command with error:\n | ```\n | ./workload run tpcc --warehouses=2000 --workers=2000 --max-rate=1000 --wait=false --duration=16m0s --scatter --tolerate-errors {pgurl:1-9}\n | ```\nWraps: (3) exit status 1\nError types: (1) errors.Cmd (2) *hintdetail.withDetail (3) *exec.ExitError\n"
Wraps: (7) attached stack trace
-- stack trace:
| main.execCmdWithBuffer
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:564
| main.(*cluster).RunWithBuffer
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2311
| main.loadTPCCBench
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tpcc.go:662
| main.runTPCCBench.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tpcc.go:733
| main.(*monitor).Go.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2632
| golang.org/x/sync/errgroup.(*Group).Go.func1
| /home/agent/work/.go/pkg/mod/golang.org/x/sync@v0.0.0-20190911185100-cd5d95a43a6e/errgroup/errgroup.go:57
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1374
Wraps: (8) /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod run teamcity-2657161-1612856692-131-n10cpu4:10 -- ./workload run tpcc --warehouses=2000 --workers=2000 --max-rate=1000 --wait=false --duration=16m0s --scatter --tolerate-errors {pgurl:1-9}
Wraps: (9) exit status 20
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) *errutil.withPrefix (5) *withstack.withStack (6) *errutil.withPrefix (7) *withstack.withStack (8) *errutil.withPrefix (9) *exec.ExitError
```
<details><summary>More</summary><p>
Artifacts: [/tpccbench/nodes=9/cpu=4/chaos/partition](https://teamcity.cockroachdb.com/viewLog.html?buildId=2657161&tab=artifacts#/tpccbench/nodes=9/cpu=4/chaos/partition)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Atpccbench%2Fnodes%3D9%2Fcpu%3D4%2Fchaos%2Fpartition.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
| 2.0 | roachtest: tpccbench/nodes=9/cpu=4/chaos/partition failed - [(roachtest).tpccbench/nodes=9/cpu=4/chaos/partition failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2657161&tab=buildLog) on [release-20.2@8c79e2bc4b35d36c8527f4c40c974f03d9034f46](https://github.com/cockroachdb/cockroach/commits/8c79e2bc4b35d36c8527f4c40c974f03d9034f46):
```
The test failed on branch=release-20.2, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/tpccbench/nodes=9/cpu=4/chaos/partition/run_1
cluster.go:2654,tpcc.go:735,tpcc.go:576,test_runner.go:755: monitor failure: monitor task failed: failed with output "./workload: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by ./workload)\nError: COMMAND_PROBLEM: exit status 1\n(1) COMMAND_PROBLEM\nWraps: (2) Node 10. Command with error:\n | ```\n | ./workload run tpcc --warehouses=2000 --workers=2000 --max-rate=1000 --wait=false --duration=16m0s --scatter --tolerate-errors {pgurl:1-9}\n | ```\nWraps: (3) exit status 1\nError types: (1) errors.Cmd (2) *hintdetail.withDetail (3) *exec.ExitError\n": /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod run teamcity-2657161-1612856692-131-n10cpu4:10 -- ./workload run tpcc --warehouses=2000 --workers=2000 --max-rate=1000 --wait=false --duration=16m0s --scatter --tolerate-errors {pgurl:1-9}: exit status 20
(1) attached stack trace
-- stack trace:
| main.(*monitor).WaitE
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2642
| main.(*monitor).Wait
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2650
| main.runTPCCBench
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tpcc.go:735
| main.registerTPCCBenchSpec.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tpcc.go:576
| main.(*testRunner).runTest.func2
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/test_runner.go:755
Wraps: (2) monitor failure
Wraps: (3) attached stack trace
-- stack trace:
| main.(*monitor).wait.func2
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2698
Wraps: (4) monitor task failed
Wraps: (5) attached stack trace
-- stack trace:
| main.loadTPCCBench
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tpcc.go:663
| [...repeated from below...]
Wraps: (6) failed with output "./workload: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by ./workload)\nError: COMMAND_PROBLEM: exit status 1\n(1) COMMAND_PROBLEM\nWraps: (2) Node 10. Command with error:\n | ```\n | ./workload run tpcc --warehouses=2000 --workers=2000 --max-rate=1000 --wait=false --duration=16m0s --scatter --tolerate-errors {pgurl:1-9}\n | ```\nWraps: (3) exit status 1\nError types: (1) errors.Cmd (2) *hintdetail.withDetail (3) *exec.ExitError\n"
Wraps: (7) attached stack trace
-- stack trace:
| main.execCmdWithBuffer
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:564
| main.(*cluster).RunWithBuffer
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2311
| main.loadTPCCBench
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tpcc.go:662
| main.runTPCCBench.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tpcc.go:733
| main.(*monitor).Go.func1
| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2632
| golang.org/x/sync/errgroup.(*Group).Go.func1
| /home/agent/work/.go/pkg/mod/golang.org/x/sync@v0.0.0-20190911185100-cd5d95a43a6e/errgroup/errgroup.go:57
| runtime.goexit
| /usr/local/go/src/runtime/asm_amd64.s:1374
Wraps: (8) /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod run teamcity-2657161-1612856692-131-n10cpu4:10 -- ./workload run tpcc --warehouses=2000 --workers=2000 --max-rate=1000 --wait=false --duration=16m0s --scatter --tolerate-errors {pgurl:1-9}
Wraps: (9) exit status 20
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) *errutil.withPrefix (5) *withstack.withStack (6) *errutil.withPrefix (7) *withstack.withStack (8) *errutil.withPrefix (9) *exec.ExitError
```
<details><summary>More</summary><p>
Artifacts: [/tpccbench/nodes=9/cpu=4/chaos/partition](https://teamcity.cockroachdb.com/viewLog.html?buildId=2657161&tab=artifacts#/tpccbench/nodes=9/cpu=4/chaos/partition)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Atpccbench%2Fnodes%3D9%2Fcpu%3D4%2Fchaos%2Fpartition.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
| test | roachtest tpccbench nodes cpu chaos partition failed on the test failed on branch release cloud gce test artifacts and logs in home agent work go src github com cockroachdb cockroach artifacts tpccbench nodes cpu chaos partition run cluster go tpcc go tpcc go test runner go monitor failure monitor task failed failed with output workload lib linux gnu libm so version glibc not found required by workload nerror command problem exit status n command problem nwraps node command with error n n workload run tpcc warehouses workers max rate wait false duration scatter tolerate errors pgurl n nwraps exit status nerror types errors cmd hintdetail withdetail exec exiterror n home agent work go src github com cockroachdb cockroach bin roachprod run teamcity workload run tpcc warehouses workers max rate wait false duration scatter tolerate errors pgurl exit status attached stack trace stack trace main monitor waite home agent work go src github com cockroachdb cockroach pkg cmd roachtest cluster go main monitor wait home agent work go src github com cockroachdb cockroach pkg cmd roachtest cluster go main runtpccbench home agent work go src github com cockroachdb cockroach pkg cmd roachtest tpcc go main registertpccbenchspec home agent work go src github com cockroachdb cockroach pkg cmd roachtest tpcc go main testrunner runtest home agent work go src github com cockroachdb cockroach pkg cmd roachtest test runner go wraps monitor failure wraps attached stack trace stack trace main monitor wait home agent work go src github com cockroachdb cockroach pkg cmd roachtest cluster go wraps monitor task failed wraps attached stack trace stack trace main loadtpccbench home agent work go src github com cockroachdb cockroach pkg cmd roachtest tpcc go wraps failed with output workload lib linux gnu libm so version glibc not found required by workload nerror command problem exit status n command problem nwraps node command with error n n workload run tpcc warehouses workers max rate wait false duration scatter tolerate errors pgurl n nwraps exit status nerror types errors cmd hintdetail withdetail exec exiterror n wraps attached stack trace stack trace main execcmdwithbuffer home agent work go src github com cockroachdb cockroach pkg cmd roachtest cluster go main cluster runwithbuffer home agent work go src github com cockroachdb cockroach pkg cmd roachtest cluster go main loadtpccbench home agent work go src github com cockroachdb cockroach pkg cmd roachtest tpcc go main runtpccbench home agent work go src github com cockroachdb cockroach pkg cmd roachtest tpcc go main monitor go home agent work go src github com cockroachdb cockroach pkg cmd roachtest cluster go golang org x sync errgroup group go home agent work go pkg mod golang org x sync errgroup errgroup go runtime goexit usr local go src runtime asm s wraps home agent work go src github com cockroachdb cockroach bin roachprod run teamcity workload run tpcc warehouses workers max rate wait false duration scatter tolerate errors pgurl wraps exit status error types withstack withstack errutil withprefix withstack withstack errutil withprefix withstack withstack errutil withprefix withstack withstack errutil withprefix exec exiterror more artifacts powered by | 1 |
24,947 | 12,195,640,716 | IssuesEvent | 2020-04-29 17:42:56 | terraform-providers/terraform-provider-aws | https://api.github.com/repos/terraform-providers/terraform-provider-aws | closed | Consider failing when name is used instead of name_prefix and create_before_destroy is true. | enhancement service/autoscaling stale upstream-terraform | ### Terraform Version
0.10+
### Affected Resource(s)
I've run into this with security groups and ASGs. I suspect there are others as well that I've just not run across.
### Terraform Configuration Files
This is from the https://github.com/terraform-community-modules/tf_aws_ecs module:
```
resource "aws_autoscaling_group" "ecs" {
name = "asg-${aws_launch_configuration.ecs.name}"
vpc_zone_identifier = ["${var.subnet_id}"]
launch_configuration = "${aws_launch_configuration.ecs.name}"
min_size = "${var.min_servers}"
max_size = "${var.max_servers}"
desired_capacity = "${var.servers}"
termination_policies = ["OldestLaunchConfiguration", "ClosestToNextInstanceHour", "Default"]
tags = [{
key = "Name"
value = "${var.name} ${var.tagName}"
propagate_at_launch = true
}]
tags = ["${var.extra_tags}"]
lifecycle {
create_before_destroy = true
}
}
```
### Expected Behavior
I expect an ASG is created before destroying the existing one. Sadly, some resources (it seems older ones) rely on a unique name.
### Actual Behavior
When TF runs it tries to create an ASG with the same name as the existing resource, which results in a failed TF run.
It seems that when `name` and `create_before_destroy = true` are used in combination TF does things that are not super great. You're either left with ASGs being destroyed before the new ones are created _or_ switching to `name_prefix` anyways. I suspect very few people actually want to destroy their existing ASGs _before_ the new ones are created.
Perhaps another option would be to set the name to something random and then update it's name after the old one is destroyed? | 1.0 | Consider failing when name is used instead of name_prefix and create_before_destroy is true. - ### Terraform Version
0.10+
### Affected Resource(s)
I've run into this with security groups and ASGs. I suspect there are others as well that I've just not run across.
### Terraform Configuration Files
This is from the https://github.com/terraform-community-modules/tf_aws_ecs module:
```
resource "aws_autoscaling_group" "ecs" {
name = "asg-${aws_launch_configuration.ecs.name}"
vpc_zone_identifier = ["${var.subnet_id}"]
launch_configuration = "${aws_launch_configuration.ecs.name}"
min_size = "${var.min_servers}"
max_size = "${var.max_servers}"
desired_capacity = "${var.servers}"
termination_policies = ["OldestLaunchConfiguration", "ClosestToNextInstanceHour", "Default"]
tags = [{
key = "Name"
value = "${var.name} ${var.tagName}"
propagate_at_launch = true
}]
tags = ["${var.extra_tags}"]
lifecycle {
create_before_destroy = true
}
}
```
### Expected Behavior
I expect an ASG is created before destroying the existing one. Sadly, some resources (it seems older ones) rely on a unique name.
### Actual Behavior
When TF runs it tries to create an ASG with the same name as the existing resource, which results in a failed TF run.
It seems that when `name` and `create_before_destroy = true` are used in combination TF does things that are not super great. You're either left with ASGs being destroyed before the new ones are created _or_ switching to `name_prefix` anyways. I suspect very few people actually want to destroy their existing ASGs _before_ the new ones are created.
Perhaps another option would be to set the name to something random and then update it's name after the old one is destroyed? | non_test | consider failing when name is used instead of name prefix and create before destroy is true terraform version affected resource s i ve run into this with security groups and asgs i suspect there are others as well that i ve just not run across terraform configuration files this is from the module resource aws autoscaling group ecs name asg aws launch configuration ecs name vpc zone identifier launch configuration aws launch configuration ecs name min size var min servers max size var max servers desired capacity var servers termination policies tags key name value var name var tagname propagate at launch true tags lifecycle create before destroy true expected behavior i expect an asg is created before destroying the existing one sadly some resources it seems older ones rely on a unique name actual behavior when tf runs it tries to create an asg with the same name as the existing resource which results in a failed tf run it seems that when name and create before destroy true are used in combination tf does things that are not super great you re either left with asgs being destroyed before the new ones are created or switching to name prefix anyways i suspect very few people actually want to destroy their existing asgs before the new ones are created perhaps another option would be to set the name to something random and then update it s name after the old one is destroyed | 0 |
3,472 | 3,179,826,173 | IssuesEvent | 2015-09-25 05:31:54 | rackt/react-router | https://api.github.com/repos/rackt/react-router | closed | Run examples using HTML5 history | build | In order to get the best URLs we should run the examples using HTML5 history. `webpack-dev-server` has a `--history-api-fallback` flag that we should be able to use to do this. We're [already using it in the `history` library](https://github.com/rackt/history/blob/15811a02cafc7b3a777f2e63d7fe1cc99f64f902/package.json#L15). | 1.0 | Run examples using HTML5 history - In order to get the best URLs we should run the examples using HTML5 history. `webpack-dev-server` has a `--history-api-fallback` flag that we should be able to use to do this. We're [already using it in the `history` library](https://github.com/rackt/history/blob/15811a02cafc7b3a777f2e63d7fe1cc99f64f902/package.json#L15). | non_test | run examples using history in order to get the best urls we should run the examples using history webpack dev server has a history api fallback flag that we should be able to use to do this we re | 0 |
693,940 | 23,795,424,343 | IssuesEvent | 2022-09-02 19:02:59 | DCS-LCSR/ASL-DAI | https://api.github.com/repos/DCS-LCSR/ASL-DAI | closed | small request and a couple of questions | low priority | 1) Carey is not able to log into his account in the dev1 server. He seems to have forgotten his password. Could you please reset it?
2) We are about to have some SignStream files with 1 video rather than 3. Will any adjustments need to be made to accommodate that?
3) We should at some point return to the question about what happens in a collection when an utterance has been deleted -- to make sure that such material doesn't get uploaded to the DAI (i.e., if it is hidden from SignStream users but still present in the file).
4) At some point, we should return to the issue of representing the translation of compounds from the ASLLVD and allowing us to enter translations for any new compounds imported into the Sign Bank from the continuous signing data.
Just so these things don't get forgotten :-)
Thanks so much !!
| 1.0 | small request and a couple of questions - 1) Carey is not able to log into his account in the dev1 server. He seems to have forgotten his password. Could you please reset it?
2) We are about to have some SignStream files with 1 video rather than 3. Will any adjustments need to be made to accommodate that?
3) We should at some point return to the question about what happens in a collection when an utterance has been deleted -- to make sure that such material doesn't get uploaded to the DAI (i.e., if it is hidden from SignStream users but still present in the file).
4) At some point, we should return to the issue of representing the translation of compounds from the ASLLVD and allowing us to enter translations for any new compounds imported into the Sign Bank from the continuous signing data.
Just so these things don't get forgotten :-)
Thanks so much !!
| non_test | small request and a couple of questions carey is not able to log into his account in the server he seems to have forgotten his password could you please reset it we are about to have some signstream files with video rather than will any adjustments need to be made to accommodate that we should at some point return to the question about what happens in a collection when an utterance has been deleted to make sure that such material doesn t get uploaded to the dai i e if it is hidden from signstream users but still present in the file at some point we should return to the issue of representing the translation of compounds from the asllvd and allowing us to enter translations for any new compounds imported into the sign bank from the continuous signing data just so these things don t get forgotten thanks so much | 0 |
22,850 | 3,974,089,291 | IssuesEvent | 2016-05-04 20:54:54 | omeka/plugin-Geolocation | https://api.github.com/repos/omeka/plugin-Geolocation | closed | Test for 2.2.4 release | Testing | In particular, look at searches using "Geographic Address" from the items advanced search.
Otherwise this is just a sanity check to make sure nothing looks wrong or broken. | 1.0 | Test for 2.2.4 release - In particular, look at searches using "Geographic Address" from the items advanced search.
Otherwise this is just a sanity check to make sure nothing looks wrong or broken. | test | test for release in particular look at searches using geographic address from the items advanced search otherwise this is just a sanity check to make sure nothing looks wrong or broken | 1 |
492,688 | 14,217,674,446 | IssuesEvent | 2020-11-17 10:41:20 | bounswe/bounswe2020group4 | https://api.github.com/repos/bounswe/bounswe2020group4 | closed | (AND) Finalize the Project Plan | Android Effort: Medium Priority: High Status: Needs Review Task: Assignment | Android team will update the Project Plan to shape it into its final form.
Deadline: 19/11/20 | 1.0 | (AND) Finalize the Project Plan - Android team will update the Project Plan to shape it into its final form.
Deadline: 19/11/20 | non_test | and finalize the project plan android team will update the project plan to shape it into its final form deadline | 0 |
145,185 | 11,661,371,805 | IssuesEvent | 2020-03-03 06:34:44 | ECLK/Nomination | https://api.github.com/repos/ECLK/Nomination | closed | Party User: No logout option for party user | ICTA TEST - Priority 01 |
Party User: No logout option for party users. when user doesn't have any election to proceed. Use get stuck on the screen.
| 1.0 | Party User: No logout option for party user -
Party User: No logout option for party users. when user doesn't have any election to proceed. Use get stuck on the screen.
| test | party user no logout option for party user party user no logout option for party users when user doesn t have any election to proceed use get stuck on the screen | 1 |
276,738 | 8,608,872,689 | IssuesEvent | 2018-11-18 16:11:55 | fhstp/highlighter-webapp | https://api.github.com/repos/fhstp/highlighter-webapp | closed | Restructure viz | enhancement high priority styling | Make the viz site more responsive and restructure it a bit. Also use the space better. | 1.0 | Restructure viz - Make the viz site more responsive and restructure it a bit. Also use the space better. | non_test | restructure viz make the viz site more responsive and restructure it a bit also use the space better | 0 |
262,349 | 22,835,010,381 | IssuesEvent | 2022-07-12 15:52:56 | microsoft/msquic | https://api.github.com/repos/microsoft/msquic | opened | Failure in Down Level Test | Area: Testing Bug: Test/Tool | ### Describe the bug
https://github.com/microsoft/msquic/runs/7304802896?check_suite_focus=true
```
[----------] 1 test from ParameterValidation/WithValidateStreamEventArgs
[ RUN ] ParameterValidation/WithValidateStreamEventArgs.ValidateStreamEvents/2
C:\__w\1\s\src\test\lib\EventTest.cpp(33): error: StreamEventValidator: Expected 1. Actual 3
C:\__w\1\s\src\test\lib\EventTest.cpp(8[56](https://github.com/microsoft/msquic/runs/7304802896?check_suite_focus=true#step:9:57)): error: Client.Complete.WaitTimeout(2000) not true
C:\__w\1\s\src\test\lib\EventTest.cpp(33): error: StreamEventValidator: Expected 3. Actual 6
C:\__w\1\s\src\test\lib\EventTest.cpp(33): error: StreamEventValidator: Expected 6. Actual 7
C:\__w\1\s\src\test\lib\EventTest.cpp(33): error: StreamEventValidator: Expected 1. Actual 7
C:\__w\1\s\src\test\lib\EventTest.cpp(128): error: ConnEventValidator: Expected 2. Actual 3
[ FAILED ] ParameterValidation/WithValidateStreamEventArgs.ValidateStreamEvents/2, where GetParam() = 2 (2240 ms)
[----------] 1 test from ParameterValidation/WithValidateStreamEventArgs (2240 ms total)
```
The test god `QUIC_STREAM_EVENT_PEER_SEND_SHUTDOWN` instead of the `QUIC_STREAM_EVENT_RECEIVE` event?
And no logs were collected.
### Affected OS
- [ ] All
- [X] Windows Server 2022
- [ ] Windows 11, version 22H2
- [ ] Windows 11, version 21H2
- [ ] Windows Insider Preview (specify affected build below)
- [ ] Ubuntu
- [ ] Debian
- [ ] Other (specify below)
### Additional OS information
_No response_
### MsQuic version
main
### Steps taken to reproduce bug
Create a PR that triggers downlevel tests to run.
### Expected behavior
The tests should pass.
### Actual outcome
Sometimes they fail because of a timing issue.
### Additional details
_No response_ | 2.0 | Failure in Down Level Test - ### Describe the bug
https://github.com/microsoft/msquic/runs/7304802896?check_suite_focus=true
```
[----------] 1 test from ParameterValidation/WithValidateStreamEventArgs
[ RUN ] ParameterValidation/WithValidateStreamEventArgs.ValidateStreamEvents/2
C:\__w\1\s\src\test\lib\EventTest.cpp(33): error: StreamEventValidator: Expected 1. Actual 3
C:\__w\1\s\src\test\lib\EventTest.cpp(8[56](https://github.com/microsoft/msquic/runs/7304802896?check_suite_focus=true#step:9:57)): error: Client.Complete.WaitTimeout(2000) not true
C:\__w\1\s\src\test\lib\EventTest.cpp(33): error: StreamEventValidator: Expected 3. Actual 6
C:\__w\1\s\src\test\lib\EventTest.cpp(33): error: StreamEventValidator: Expected 6. Actual 7
C:\__w\1\s\src\test\lib\EventTest.cpp(33): error: StreamEventValidator: Expected 1. Actual 7
C:\__w\1\s\src\test\lib\EventTest.cpp(128): error: ConnEventValidator: Expected 2. Actual 3
[ FAILED ] ParameterValidation/WithValidateStreamEventArgs.ValidateStreamEvents/2, where GetParam() = 2 (2240 ms)
[----------] 1 test from ParameterValidation/WithValidateStreamEventArgs (2240 ms total)
```
The test god `QUIC_STREAM_EVENT_PEER_SEND_SHUTDOWN` instead of the `QUIC_STREAM_EVENT_RECEIVE` event?
And no logs were collected.
### Affected OS
- [ ] All
- [X] Windows Server 2022
- [ ] Windows 11, version 22H2
- [ ] Windows 11, version 21H2
- [ ] Windows Insider Preview (specify affected build below)
- [ ] Ubuntu
- [ ] Debian
- [ ] Other (specify below)
### Additional OS information
_No response_
### MsQuic version
main
### Steps taken to reproduce bug
Create a PR that triggers downlevel tests to run.
### Expected behavior
The tests should pass.
### Actual outcome
Sometimes they fail because of a timing issue.
### Additional details
_No response_ | test | failure in down level test describe the bug test from parametervalidation withvalidatestreameventargs parametervalidation withvalidatestreameventargs validatestreamevents c w s src test lib eventtest cpp error streameventvalidator expected actual c w s src test lib eventtest cpp error client complete waittimeout not true c w s src test lib eventtest cpp error streameventvalidator expected actual c w s src test lib eventtest cpp error streameventvalidator expected actual c w s src test lib eventtest cpp error streameventvalidator expected actual c w s src test lib eventtest cpp error conneventvalidator expected actual parametervalidation withvalidatestreameventargs validatestreamevents where getparam ms test from parametervalidation withvalidatestreameventargs ms total the test god quic stream event peer send shutdown instead of the quic stream event receive event and no logs were collected affected os all windows server windows version windows version windows insider preview specify affected build below ubuntu debian other specify below additional os information no response msquic version main steps taken to reproduce bug create a pr that triggers downlevel tests to run expected behavior the tests should pass actual outcome sometimes they fail because of a timing issue additional details no response | 1 |
169,876 | 14,234,980,882 | IssuesEvent | 2020-11-18 14:17:12 | jsonresume/resume-schema | https://api.github.com/repos/jsonresume/resume-schema | closed | Document that JSON Resume is available on SchemaStore.org | Documentation | Document this in README and on homepage
| 1.0 | Document that JSON Resume is available on SchemaStore.org - Document this in README and on homepage
| non_test | document that json resume is available on schemastore org document this in readme and on homepage | 0 |
170,255 | 13,180,888,718 | IssuesEvent | 2020-08-12 13:31:17 | microsoft/botbuilder-python | https://api.github.com/repos/microsoft/botbuilder-python | closed | [PORT] [CI-PR Pipelines] Skip tests in Debug builds | ci-test-steps image | > Port this change from botbuilder-dotnet/master branch:
https://github.com/microsoft/botbuilder-dotnet/pull/4416
## Description
This PR updates the [ci-test-steps](https://github.com/microsoft/botbuilder-dotnet/blob/master/build/yaml/ci-test-steps.yml) yaml file to skip the test and coverage steps in the Debug builds.
Also, it fixes an issue found on the API Compat job matrix that caused that the _Microsoft.Bot.Builder.Integration.ApplicationInsights.Core_ library wasn't getting compared.
## Specific Changes
- **ci-test-steps yaml**:
- Removed the test steps for Debug 2.1 and Debug 3.1 jobs
- Added a condition to execute the coverage steps only for Release builds.
- **botbuilder-dotnet-ci.yml**:
- Updated the PowerShell script to create the matrix for the API Compat job including all the libraries.
- Updated the Powershell script to run all API Compat validation on Manual builds fixing an error.
## Testing
The following image shows the test and coverage steps being skipped on the Debug build, releasing the agent that executes the Debug job about 4 minutes earlier.
| 1.0 | [PORT] [CI-PR Pipelines] Skip tests in Debug builds - > Port this change from botbuilder-dotnet/master branch:
https://github.com/microsoft/botbuilder-dotnet/pull/4416
## Description
This PR updates the [ci-test-steps](https://github.com/microsoft/botbuilder-dotnet/blob/master/build/yaml/ci-test-steps.yml) yaml file to skip the test and coverage steps in the Debug builds.
Also, it fixes an issue found on the API Compat job matrix that caused that the _Microsoft.Bot.Builder.Integration.ApplicationInsights.Core_ library wasn't getting compared.
## Specific Changes
- **ci-test-steps yaml**:
- Removed the test steps for Debug 2.1 and Debug 3.1 jobs
- Added a condition to execute the coverage steps only for Release builds.
- **botbuilder-dotnet-ci.yml**:
- Updated the PowerShell script to create the matrix for the API Compat job including all the libraries.
- Updated the Powershell script to run all API Compat validation on Manual builds fixing an error.
## Testing
The following image shows the test and coverage steps being skipped on the Debug build, releasing the agent that executes the Debug job about 4 minutes earlier.
| test | skip tests in debug builds port this change from botbuilder dotnet master branch description this pr updates the yaml file to skip the test and coverage steps in the debug builds also it fixes an issue found on the api compat job matrix that caused that the microsoft bot builder integration applicationinsights core library wasn t getting compared specific changes ci test steps yaml removed the test steps for debug and debug jobs added a condition to execute the coverage steps only for release builds botbuilder dotnet ci yml updated the powershell script to create the matrix for the api compat job including all the libraries updated the powershell script to run all api compat validation on manual builds fixing an error testing the following image shows the test and coverage steps being skipped on the debug build releasing the agent that executes the debug job about minutes earlier | 1 |
135,722 | 19,654,998,111 | IssuesEvent | 2022-01-10 11:31:55 | Joystream/atlas | https://api.github.com/repos/Joystream/atlas | opened | Update top navigation to include notifications | design design-system | ### Description
I need an updated version of top navigation that includes "Notifications" button in 2 states: With and without unread notifications:
The indicator shows only the notifications that have appeared since the last click on the button. They don't have to be read or unread.
Top Navigation:
https://www.figma.com/file/Pf31tuYpozYmpq163U2ho8/Web-Components?node-id=3173%3A135755
Button:
https://www.figma.com/file/Pf31tuYpozYmpq163U2ho8/Web-Components?node-id=216%3A6243
Badge:
https://www.figma.com/file/Pf31tuYpozYmpq163U2ho8/Web-Components?node-id=4284%3A141647
Icon:
https://www.figma.com/file/2tlBY1JQtRMoyjmjJQ9jam/Icons?node-id=304%3A2547
### Figma link
https://www.figma.com/file/Pf31tuYpozYmpq163U2ho8/Web-Components?node-id=3173%3A135755
### How urgent this is?
This will block me soon | 2.0 | Update top navigation to include notifications - ### Description
I need an updated version of top navigation that includes "Notifications" button in 2 states: With and without unread notifications:
The indicator shows only the notifications that have appeared since the last click on the button. They don't have to be read or unread.
Top Navigation:
https://www.figma.com/file/Pf31tuYpozYmpq163U2ho8/Web-Components?node-id=3173%3A135755
Button:
https://www.figma.com/file/Pf31tuYpozYmpq163U2ho8/Web-Components?node-id=216%3A6243
Badge:
https://www.figma.com/file/Pf31tuYpozYmpq163U2ho8/Web-Components?node-id=4284%3A141647
Icon:
https://www.figma.com/file/2tlBY1JQtRMoyjmjJQ9jam/Icons?node-id=304%3A2547
### Figma link
https://www.figma.com/file/Pf31tuYpozYmpq163U2ho8/Web-Components?node-id=3173%3A135755
### How urgent this is?
This will block me soon | non_test | update top navigation to include notifications description i need an updated version of top navigation that includes notifications button in states with and without unread notifications the indicator shows only the notifications that have appeared since the last click on the button they don t have to be read or unread top navigation button badge icon figma link how urgent this is this will block me soon | 0 |
99,576 | 8,704,813,079 | IssuesEvent | 2018-12-05 20:30:05 | Princeton-CDH/ppa-django | https://api.github.com/repos/Princeton-CDH/ppa-django | closed | As a content editor, I want to be able to add and order multiple authors to an editorial so I can correctly attribute work. | awaiting testing | ## notes for development
- create a new `person` [snippet model](https://docs.wagtail.io/en/v2.3/topics/snippets.html)
- I think for now, we should just include a name field and an optional URL (we can add more fields later if we determine we need them or want to adapt/reuse the same snippet for the contributor page)
- add a new [streamfield](https://docs.wagtail.io/en/v2.3/topics/streamfield.html) to EditorialPage - it should have one snippet chooser block, which only allows selecting person snippets; streamfield should handle single or multiple and ordering for us
- update editorial list and detail display to show author names in the order they are listed, with links if they are present
## notes for testing
- You can now add authors to an editorial page in the Wagtail CMS. From the editorial page, there is now an Authors field, and it allows you to create People snippets with a display name and a url associated with them (if desired, i.e. their social media profile, ORCID id, etc.).
- To test, create two.
They should be:
- [x] displayed on the editorial index page and on the byline of the editorial -
- [x] separated by commas,
- [x] in the order you have moved them. (You can use arrows in the upper right of each block to order them in the CMS admin)
- [x] If you add a url, the name should be a link ONLY on the editorial page itself, not the index page. | 1.0 | As a content editor, I want to be able to add and order multiple authors to an editorial so I can correctly attribute work. - ## notes for development
- create a new `person` [snippet model](https://docs.wagtail.io/en/v2.3/topics/snippets.html)
- I think for now, we should just include a name field and an optional URL (we can add more fields later if we determine we need them or want to adapt/reuse the same snippet for the contributor page)
- add a new [streamfield](https://docs.wagtail.io/en/v2.3/topics/streamfield.html) to EditorialPage - it should have one snippet chooser block, which only allows selecting person snippets; streamfield should handle single or multiple and ordering for us
- update editorial list and detail display to show author names in the order they are listed, with links if they are present
## notes for testing
- You can now add authors to an editorial page in the Wagtail CMS. From the editorial page, there is now an Authors field, and it allows you to create People snippets with a display name and a url associated with them (if desired, i.e. their social media profile, ORCID id, etc.).
- To test, create two.
They should be:
- [x] displayed on the editorial index page and on the byline of the editorial -
- [x] separated by commas,
- [x] in the order you have moved them. (You can use arrows in the upper right of each block to order them in the CMS admin)
- [x] If you add a url, the name should be a link ONLY on the editorial page itself, not the index page. | test | as a content editor i want to be able to add and order multiple authors to an editorial so i can correctly attribute work notes for development create a new person i think for now we should just include a name field and an optional url we can add more fields later if we determine we need them or want to adapt reuse the same snippet for the contributor page add a new to editorialpage it should have one snippet chooser block which only allows selecting person snippets streamfield should handle single or multiple and ordering for us update editorial list and detail display to show author names in the order they are listed with links if they are present notes for testing you can now add authors to an editorial page in the wagtail cms from the editorial page there is now an authors field and it allows you to create people snippets with a display name and a url associated with them if desired i e their social media profile orcid id etc to test create two they should be displayed on the editorial index page and on the byline of the editorial separated by commas in the order you have moved them you can use arrows in the upper right of each block to order them in the cms admin if you add a url the name should be a link only on the editorial page itself not the index page | 1 |
45,017 | 18,298,178,628 | IssuesEvent | 2021-10-05 22:49:25 | microsoft/vscode-cpptools | https://api.github.com/repos/microsoft/vscode-cpptools | closed | Class keyword is not highlighted when hovering over the name of a templated class. | Language Service external Feature: Colorization | Bug type: Language Service
<!-- Prior to creating a bug report, please review:
📝 Existing issues at https://github.com/Microsoft/vscode-cpptools/issues
📜 Our documentation at https://code.visualstudio.com/docs/languages/cpp
📙 FAQs at https://code.visualstudio.com/docs/cpp/faq-cpp
-->
**Describe the bug**
- OS and Version: Windows 10 x64 1909
- VS Code Version: 1.58.2
- C/C++ Extension Version: 1.5.1
- Other extensions you installed (and if the issue persists after disabling them): C++ Syntax (issue still persists)
When you hover over a class name with a template, the `class` keyword is not highlighted.
**Steps to reproduce**
<!-- Provide clear steps to reproduce the bug: -->
1. Create an empty class called `clazz`.
2. Hover over `clazz`; the `class` keyword is highlighted.
3. Create an empty class called `clazz_generic` that uses a template.
4. Hover over `clazz_generic`; the `class` keyword before the class name is not highlighted but the `template` and `class` keyword before the type parameter are highlighted correctly.
**Expected behavior**
The `class` keyword before the class name is highlighted correctly.
**Code sample and logs**
```cpp
- Code sample
/**
* @brief Highlighted correctly
*/
class clazz
{
};
/**
* @brief Highlighted incorrectly
*/
template <typename T>
class clazz_generic
{
};
```
- Configurations in `c_cpp_properties.json`
```json
{
"configurations": [
{
"name": "Win32",
"includePath": [
"${workspaceFolder}/src"
],
"defines": [
"_DEBUG",
"UNICODE",
"_UNICODE"
],
"windowsSdkVersion": "10.0.19041.0",
"cStandard": "c17",
"compilerPath": "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.28.29910/bin/Hostx64/x64/cl.exe",
"intelliSenseMode": "windows-msvc-x64",
"cppStandard": "c++20"
}
],
"version": 4
}
```
- Logs from running `C/C++: Log Diagnostics` from the VS Code command palette (doesn't help)
- Logs from [the language server logging](https://code.visualstudio.com/docs/cpp/enable-logging-cpp#_enable-logging-for-the-language-server) (doesn't help)
**Screenshots**
<!-- If applicable, add screenshots to help explain your problem. -->
**Additional context**
<!--
Providing call stacks:
For bugs like crashes, deadlocks, infinite loops, etc. that we are not able to repro and for which the call stack may be useful, please attach a debugger and/or create a dmp and provide the call stacks. Windows binaries have symbols available in VS Code by setting your "symbolSearchPath" to "https://msdl.microsoft.com/download/symbols".
Instructions for attaching debugger to language service process:
https://github.com/microsoft/vscode-cpptools/wiki/Attaching-debugger-to-cpptools-or-cpptools%E2%80%90srv.
Performance analysis:
For a performance issue see instructions at https://github.com/microsoft/vscode-cpptools/wiki/Troubleshooting-Performance-Issues.
-->
None
| 1.0 | Class keyword is not highlighted when hovering over the name of a templated class. - Bug type: Language Service
<!-- Prior to creating a bug report, please review:
📝 Existing issues at https://github.com/Microsoft/vscode-cpptools/issues
📜 Our documentation at https://code.visualstudio.com/docs/languages/cpp
📙 FAQs at https://code.visualstudio.com/docs/cpp/faq-cpp
-->
**Describe the bug**
- OS and Version: Windows 10 x64 1909
- VS Code Version: 1.58.2
- C/C++ Extension Version: 1.5.1
- Other extensions you installed (and if the issue persists after disabling them): C++ Syntax (issue still persists)
When you hover over a class name with a template, the `class` keyword is not highlighted.
**Steps to reproduce**
<!-- Provide clear steps to reproduce the bug: -->
1. Create an empty class called `clazz`.
2. Hover over `clazz`; the `class` keyword is highlighted.
3. Create an empty class called `clazz_generic` that uses a template.
4. Hover over `clazz_generic`; the `class` keyword before the class name is not highlighted but the `template` and `class` keyword before the type parameter are highlighted correctly.
**Expected behavior**
The `class` keyword before the class name is highlighted correctly.
**Code sample and logs**
```cpp
- Code sample
/**
* @brief Highlighted correctly
*/
class clazz
{
};
/**
* @brief Highlighted incorrectly
*/
template <typename T>
class clazz_generic
{
};
```
- Configurations in `c_cpp_properties.json`
```json
{
"configurations": [
{
"name": "Win32",
"includePath": [
"${workspaceFolder}/src"
],
"defines": [
"_DEBUG",
"UNICODE",
"_UNICODE"
],
"windowsSdkVersion": "10.0.19041.0",
"cStandard": "c17",
"compilerPath": "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.28.29910/bin/Hostx64/x64/cl.exe",
"intelliSenseMode": "windows-msvc-x64",
"cppStandard": "c++20"
}
],
"version": 4
}
```
- Logs from running `C/C++: Log Diagnostics` from the VS Code command palette (doesn't help)
- Logs from [the language server logging](https://code.visualstudio.com/docs/cpp/enable-logging-cpp#_enable-logging-for-the-language-server) (doesn't help)
**Screenshots**
<!-- If applicable, add screenshots to help explain your problem. -->
**Additional context**
<!--
Providing call stacks:
For bugs like crashes, deadlocks, infinite loops, etc. that we are not able to repro and for which the call stack may be useful, please attach a debugger and/or create a dmp and provide the call stacks. Windows binaries have symbols available in VS Code by setting your "symbolSearchPath" to "https://msdl.microsoft.com/download/symbols".
Instructions for attaching debugger to language service process:
https://github.com/microsoft/vscode-cpptools/wiki/Attaching-debugger-to-cpptools-or-cpptools%E2%80%90srv.
Performance analysis:
For a performance issue see instructions at https://github.com/microsoft/vscode-cpptools/wiki/Troubleshooting-Performance-Issues.
-->
None
| non_test | class keyword is not highlighted when hovering over the name of a templated class bug type language service prior to creating a bug report please review 📝 existing issues at 📜 our documentation at 📙 faqs at describe the bug os and version windows vs code version c c extension version other extensions you installed and if the issue persists after disabling them c syntax issue still persists when you hover over a class name with a template the class keyword is not highlighted steps to reproduce create an empty class called clazz hover over clazz the class keyword is highlighted create an empty class called clazz generic that uses a template hover over clazz generic the class keyword before the class name is not highlighted but the template and class keyword before the type parameter are highlighted correctly expected behavior the class keyword before the class name is highlighted correctly code sample and logs cpp code sample brief highlighted correctly class clazz brief highlighted incorrectly template class clazz generic configurations in c cpp properties json json configurations name includepath workspacefolder src defines debug unicode unicode windowssdkversion cstandard compilerpath c program files microsoft visual studio community vc tools msvc bin cl exe intellisensemode windows msvc cppstandard c version logs from running c c log diagnostics from the vs code command palette doesn t help logs from doesn t help screenshots additional context providing call stacks for bugs like crashes deadlocks infinite loops etc that we are not able to repro and for which the call stack may be useful please attach a debugger and or create a dmp and provide the call stacks windows binaries have symbols available in vs code by setting your symbolsearchpath to instructions for attaching debugger to language service process performance analysis for a performance issue see instructions at none | 0 |
7,743 | 2,925,606,493 | IssuesEvent | 2015-06-26 07:28:37 | e-government-ua/i | https://api.github.com/repos/e-government-ua/i | closed | На главном портале, при заходе в профиль услуге, и выбора места, отрисовывать только те методы авторизации, которые перечислены в поле asAuth, сущности ServiceData | test | например значение: "BankID,EDS"
- будет допускать и кнопку авторизации по БанкИД и по ЭЦП
в то время как значение: "BankID"
- только БанкИД
если этого поля в сущности нет, или оно налл-овое, то считать что допустимы все методы авторизации | 1.0 | На главном портале, при заходе в профиль услуге, и выбора места, отрисовывать только те методы авторизации, которые перечислены в поле asAuth, сущности ServiceData - например значение: "BankID,EDS"
- будет допускать и кнопку авторизации по БанкИД и по ЭЦП
в то время как значение: "BankID"
- только БанкИД
если этого поля в сущности нет, или оно налл-овое, то считать что допустимы все методы авторизации | test | на главном портале при заходе в профиль услуге и выбора места отрисовывать только те методы авторизации которые перечислены в поле asauth сущности servicedata например значение bankid eds будет допускать и кнопку авторизации по банкид и по эцп в то время как значение bankid только банкид если этого поля в сущности нет или оно налл овое то считать что допустимы все методы авторизации | 1 |
108,243 | 13,608,826,648 | IssuesEvent | 2020-09-23 03:28:09 | elementary/switchboard-plug-useraccounts | https://api.github.com/repos/elementary/switchboard-plug-useraccounts | opened | Lean on Initial Setup for creating a new user? | Needs Design Priority: Wishlist | Would it be possible/make sense to lean on Initial Setup for creating new users? Whether that means opening Initial Setup in the current user session, or somehow opening the greeter in an Initial Setup context.
I feel like that'd be nice so that we don't have to try to keep this workflow in sync, and automatically get new features like https://github.com/elementary/initial-setup/pull/84. | 1.0 | Lean on Initial Setup for creating a new user? - Would it be possible/make sense to lean on Initial Setup for creating new users? Whether that means opening Initial Setup in the current user session, or somehow opening the greeter in an Initial Setup context.
I feel like that'd be nice so that we don't have to try to keep this workflow in sync, and automatically get new features like https://github.com/elementary/initial-setup/pull/84. | non_test | lean on initial setup for creating a new user would it be possible make sense to lean on initial setup for creating new users whether that means opening initial setup in the current user session or somehow opening the greeter in an initial setup context i feel like that d be nice so that we don t have to try to keep this workflow in sync and automatically get new features like | 0 |
145,123 | 11,659,578,933 | IssuesEvent | 2020-03-03 00:28:43 | rancher/rancher | https://api.github.com/repos/rancher/rancher | closed | Panic seen in rancher server logs on master | [zube]: To Test kind/bug-qa | **What kind of request is this (question/bug/enhancement/feature request):** bug
**Steps to reproduce (least amount of steps as possible):**
- Bring up a master-head.
- Deploy an AWS rke cluster - 7 nodes - 3 etcd, 2 control planes and 2 worker nodes.
- Panic is seen in the rancher server logs
```
2020/02/25 18:54:25 [INFO] [node-controller-rancher-machine] Copying certs to the remote machine...
2020/02/25 18:56:29 [INFO] [node-controller-rancher-machine] Setting Docker configuration on the remote daemon...
2020/02/25 18:56:29 [INFO] [node-controller-rancher-machine] Setting Docker configuration on the remote daemon...
2020/02/25 18:56:29 [INFO] [node-controller-rancher-machine] Setting Docker configuration on the remote daemon...
2020/02/25 18:56:29 [INFO] [node-controller-rancher-machine] Setting Docker configuration on the remote daemon...
2020/02/25 18:56:29 [INFO] [node-controller-rancher-machine] Setting Docker configuration on the remote daemon...
2020/02/25 18:56:30 [INFO] [node-controller-rancher-machine] Setting Docker configuration on the remote daemon...
2020/02/25 18:56:30 [INFO] [node-controller-rancher-machine] Setting Docker configuration on the remote daemon...
E0225 18:57:42.886737 25 watcher.go:214] watch chan error: etcdserver: mvcc: required revision has been compacted
2020/02/25 18:58:14 [INFO] [node-controller-rancher-machine] Checking connection to Docker...
2020/02/25 18:58:15 [INFO] [node-controller-rancher-machine] Checking connection to Docker...
2020/02/25 18:58:15 [INFO] [node-controller-rancher-machine] Checking connection to Docker...
2020/02/25 18:58:15 [INFO] [node-controller-rancher-machine] Checking connection to Docker...
2020/02/25 18:58:15 [INFO] [node-controller-rancher-machine] Checking connection to Docker...
2020/02/25 18:58:16 [INFO] [node-controller-rancher-machine] Checking connection to Docker...
2020/02/25 18:58:16 [INFO] [node-controller-rancher-machine] Checking connection to Docker...
2020/02/25 18:58:55 [INFO] [node-controller-rancher-machine] Docker is up and running!
I0225 18:58:55.770509 25 controller.go:606] quota admission added evaluator for: clusterregistrationtokens.management.cattle.io
2020/02/25 18:58:55 [INFO] [node-controller-rancher-machine] Docker is up and running!
2020/02/25 18:58:56 [INFO] [node-controller-rancher-machine] Docker is up and running!
2020/02/25 18:58:56 [INFO] [node-controller-rancher-machine] Docker is up and running!
2020/02/25 18:58:56 [INFO] [node-controller-rancher-machine] Docker is up and running!
2020/02/25 18:58:56 [INFO] [node-controller-rancher-machine] Docker is up and running!
2020/02/25 18:58:57 [INFO] [node-controller-rancher-machine] Docker is up and running!
2020-02-25 18:59:00.912986 I | mvcc: store.index: compact 18818
2020-02-25 18:59:00.938969 I | mvcc: finished scheduled compaction at 18818 (took 24.852888ms)
2020/02/25 18:59:44 [INFO] Provisioning node sowmya-etcd-master-1 done
2020/02/25 18:59:44 [INFO] Generating and uploading node config sowmya-etcd-master-1
2020/02/25 18:59:44 [INFO] Provisioning node sowmya-worker-master-2 done
2020/02/25 18:59:44 [INFO] Generating and uploading node config sowmya-worker-master-2
2020/02/25 18:59:44 [INFO] Provisioning node sowmya-etcd-master-2 done
2020/02/25 18:59:44 [INFO] Generating and uploading node config sowmya-etcd-master-2
2020/02/25 18:59:44 [INFO] Creating jail for c-lcwlv
2020/02/25 18:59:44 [INFO] Generating and uploading node config
2020/02/25 18:59:44 [INFO] Provisioning node sowmya-ctrl-master-1 done
2020/02/25 18:59:44 [INFO] Generating and uploading node config sowmya-ctrl-master-1
2020/02/25 18:59:44 [INFO] Creating jail for c-lcwlv
2020/02/25 18:59:44 [INFO] Provisioning node sowmya-etcd-master-3 done
2020/02/25 18:59:44 [INFO] Generating and uploading node config sowmya-etcd-master-3
2020/02/25 18:59:44 [INFO] Generating and uploading node config
2020/02/25 18:59:44 [INFO] Creating jail for c-lcwlv
2020/02/25 18:59:44 [INFO] Generating and uploading node config
2020/02/25 18:59:44 [INFO] Provisioning node sowmya-worker-master-1 done
2020/02/25 18:59:44 [INFO] Generating and uploading node config sowmya-worker-master-1
2020/02/25 18:59:44 [INFO] Creating jail for c-lcwlv
2020/02/25 18:59:44 [INFO] Generating and uploading node config
2020/02/25 18:59:44 [INFO] Provisioning node sowmya-ctrl-master-2 done
2020/02/25 18:59:44 [INFO] Generating and uploading node config sowmya-ctrl-master-2
2020/02/25 18:59:44 [INFO] Creating jail for c-lcwlv
2020/02/25 18:59:44 [INFO] Generating and uploading node config
2020/02/25 18:59:44 [INFO] Provisioning cluster [c-lcwlv]
2020/02/25 18:59:44 [INFO] Creating cluster [c-lcwlv]
2020/02/25 18:59:44 [INFO] Handling backend connection request [c-lcwlv:m-w6tbj]
2020/02/25 18:59:44 [INFO] Handling backend connection request [c-lcwlv:m-jvgsg]
2020/02/25 18:59:44 [INFO] Handling backend connection request [c-lcwlv:m-h654g]
fatal error: concurrent map writes
goroutine 24443 [running]:
runtime.throw(0x3d09a84, 0x15)
/usr/local/go/src/runtime/panic.go:774 +0x72 fp=0xc003ffb660 sp=0xc003ffb630 pc=0x42fb12
runtime.mapassign(0x34400e0, 0xc0036f9020, 0xc003ffb758, 0x12)
/usr/local/go/src/runtime/map.go:588 +0x5c3 fp=0xc003ffb6e8 sp=0xc003ffb660 pc=0x40eb93
github.com/rancher/rancher/vendor/github.com/rancher/rke/metadata.initK8sRKESystemImages(0xc0036d5e30, 0xc0036f85a0, 0xc0036f85d0, 0xc0036f8ab0, 0xc0036f8ae0, 0xc0036f8b40, 0xc0036f8b70, 0xc0036f8ba0, 0xc0036f8db0, 0xc0036f8de0)
/go/src/github.com/rancher/rancher/vendor/github.com/rancher/rke/metadata/metadata.go:129 +0x41a fp=0xc003ffc2a8 sp=0xc003ffb6e8 pc=0x1fef27a
github.com/rancher/rancher/vendor/github.com/rancher/rke/metadata.InitMetadata(0x453e780, 0xc0036d51a0, 0x0, 0x0)
/go/src/github.com/rancher/rancher/vendor/github.com/rancher/rke/metadata/metadata.go:46 +0xf8 fp=0xc003ffc468 sp=0xc003ffc2a8 pc=0x1fee5e8
github.com/rancher/rancher/vendor/github.com/rancher/rke/cluster.InitClusterObject(0x453e780, 0xc0036d51a0, 0xc003ffcfc8, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/go/src/github.com/rancher/rancher/vendor/github.com/rancher/rke/cluster/cluster.go:587 +0x8c3 fp=0xc003ffc540 sp=0xc003ffc468 pc=0x20b72b3
github.com/rancher/rancher/vendor/github.com/rancher/rke/cluster.GeneratePlan(0x453e780, 0xc0036d51a0, 0xc002166fc8, 0xc0036d5710, 0xc0036d58c0, 0x0, 0x7f86002e2200, 0x69db7c0, 0x12, 0x198)
/go/src/github.com/rancher/rancher/vendor/github.com/rancher/rke/cluster/plan.go:74 +0x95 fp=0xc003ffcf78 sp=0xc003ffc540 pc=0x20cfbb5
github.com/rancher/rancher/pkg/librke.(*rke).GeneratePlan(0x0, 0x453e780, 0xc0036d51a0, 0xc0022cf000, 0xc0036d5710, 0xc0036d58c0, 0x0, 0x0, 0x39059a0, 0xc004a90900, ...)
/go/src/github.com/rancher/rancher/pkg/librke/rke.go:25 +0x82 fp=0xc003ffd7a8 sp=0xc003ffcf78 pc=0x221dce2
github.com/rancher/rancher/pkg/rkenodeconfigserver.(*RKENodeConfigServer).nonWorkerConfig(0xc0010ac720, 0x453e780, 0xc0036d51a0, 0xc003d52100, 0xc004a90900, 0x0, 0x10, 0x32d8ce0)
/go/src/github.com/rancher/rancher/pkg/rkenodeconfigserver/nodeserver.go:147 +0x28f fp=0xc003ffd970 sp=0xc003ffd7a8 pc=0x2bbdd7f
github.com/rancher/rancher/pkg/rkenodeconfigserver.(*RKENodeConfigServer).ServeHTTP(0xc0010ac720, 0x451da40, 0xc00153acb8, 0xc0026c9500)
/go/src/github.com/rancher/rancher/pkg/rkenodeconfigserver/nodeserver.go:95 +0x190 fp=0xc003ffda60 sp=0xc003ffd970 pc=0x2bbd4d0
github.com/rancher/rancher/server/responsewriter.ContentTypeOptions.func1(0x451da40, 0xc00153acb8, 0xc0026c9500)
/go/src/github.com/rancher/rancher/server/responsewriter/cache.go:47 +0x131 fp=0xc003ffdac8 sp=0xc003ffda60 pc=0x19375a1
net/http.HandlerFunc.ServeHTTP(0xc00262fe80, 0x451da40, 0xc00153acb8, 0xc0026c9500)
/usr/local/go/src/net/http/server.go:2007 +0x44 fp=0xc003ffdaf0 sp=0xc003ffdac8 pc=0x6fd104
github.com/rancher/rancher/vendor/github.com/gorilla/mux.(*Router).ServeHTTP(0xc000a1e000, 0x451da40, 0xc00153acb8, 0xc0026c9300)
/go/src/github.com/rancher/rancher/vendor/github.com/gorilla/mux/mux.go:212 +0xe2 fp=0xc003ffdc20 sp=0xc003ffdaf0 pc=0x192cbc2
github.com/rancher/rancher/vendor/github.com/rancher/dynamiclistener/server.wrapHandler.func1(0x451da40, 0xc00153acb8, 0xc0026c9300)
/go/src/github.com/rancher/rancher/vendor/github.com/rancher/dynamiclistener/server/server.go:187 +0x95 fp=0xc003ffdc60 sp=0xc003ffdc20 pc=0x259cdf5
net/http.HandlerFunc.ServeHTTP(0xc001e2a510, 0x451da40, 0xc00153acb8, 0xc0026c9300)
/usr/local/go/src/net/http/server.go:2007 +0x44 fp=0xc003ffdc88 sp=0xc003ffdc60 pc=0x6fd104
github.com/rancher/rancher/vendor/github.com/rancher/dynamiclistener.HTTPRedirect.func1(0x451da40, 0xc00153acb8, 0xc0026c9300)
/go/src/github.com/rancher/rancher/vendor/github.com/rancher/dynamiclistener/redirect.go:20 +0x221 fp=0xc003ffdd00 sp=0xc003ffdc88 pc=0x257af31
net/http.HandlerFunc.ServeHTTP(0xc001e131a0, 0x451da40, 0xc00153acb8, 0xc0026c9300)
/usr/local/go/src/net/http/server.go:2007 +0x44 fp=0xc003ffdd28 sp=0xc003ffdd00 pc=0x6fd104
net/http.serverHandler.ServeHTTP(0xc000151b20, 0x451da40, 0xc00153acb8, 0xc0026c9300)
/usr/local/go/src/net/http/server.go:2802 +0xa4 fp=0xc003ffdd58 sp=0xc003ffdd28 pc=0x700554
net/http.initNPNRequest.ServeHTTP(0x453e780, 0xc003741bf0, 0xc0032a4a80, 0xc000151b20, 0x451da40, 0xc00153acb8, 0xc0026c9300)
/usr/local/go/src/net/http/server.go:3365 +0x8d fp=0xc003ffded0 sp=0xc003ffdd58 pc=0x702e6d
net/http.(*initNPNRequest).ServeHTTP(0xc000d42a40, 0x451da40, 0xc00153acb8, 0xc0026c9300)
<autogenerated>:1 +0x75 fp=0xc003ffdf18 sp=0xc003ffded0 pc=0x72b915
net/http.Handler.ServeHTTP-fm(0x451da40, 0xc00153acb8, 0xc0026c9300)
/usr/local/go/src/net/http/server.go:86 +0x4d fp=0xc003ffdf48 sp=0xc003ffdf18 pc=0x72c56d
net/http.(*http2serverConn).runHandler(0xc004026600, 0xc00153acb8, 0xc0026c9300, 0xc00262fe20)
/usr/local/go/src/net/http/h2_bundle.go:5713 +0x9f fp=0xc003ffdfc0 sp=0xc003ffdf48 pc=0x6d4abf
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1357 +0x1 fp=0xc003ffdfc8 sp=0xc003ffdfc0 pc=0x45f7a1
created by net/http.(*http2serverConn).processHeaders
/usr/local/go/src/net/http/h2_bundle.go:5447 +0x4eb
goroutine 1 [chan receive, 75 minutes]:
github.com/rancher/rancher/pkg/tls.ListenAndServe(0x453e6c0, 0xc0011684c0, 0xc000dc6af0, 0x44a9a60, 0xc000a1e000, 0x1bb, 0x50, 0x0, 0x0, 0x0, ...)
/go/src/github.com/rancher/rancher/pkg/tls/tls.go:54 +0x29a
github.com/rancher/rancher/app.(*Rancher).ListenAndServe(0xc000d4a460, 0x453e6c0, 0xc0011684c0, 0xc00076adc0, 0xc001425348)
/go/src/github.com/rancher/rancher/app/app.go:73 +0xdd
main.run(0xc000d489a0, 0x0, 0x0, 0x0, 0x3cd54ee, 0x4, 0x1, 0x50, 0x1bb, 0x3cd54ee, ...)
/go/src/github.com/rancher/rancher/main.go:227 +0x3fd
main.main.func1(0xc000d489a0, 0x0, 0xc000f3a310)
/go/src/github.com/rancher/rancher/main.go:170 +0x130
github.com/rancher/rancher/vendor/github.com/urfave/cli.HandleAction(0x32fce00, 0xc0002b5fc0, 0xc000d489a0, 0xc000d489a0, 0x0)
/go/src/github.com/rancher/rancher/vendor/github.com/urfave/cli/app.go:523 +0xbe
github.com/rancher/rancher/vendor/github.com/urfave/cli.(*App).Run(0xc000b52380, 0xc00004c080, 0x8, 0x8, 0x0, 0x0)
/go/src/github.com/rancher/rancher/vendor/github.com/urfave/cli/app.go:285 +0x5ec
main.main()
```
**Actual Result:**
- Panic is seen in the logs.
- Rancher server seems to have restarted after.
**Expected Result:**
No panic should be seen in the rancher server
**Other details that may be helpful:**
**Environment information**
- Rancher version (`rancher/rancher`/`rancher/server` image tag or shown bottom left in the UI): master-head - commit id: `6085a90e2`
- Installation option (single install/HA): single
<!--
If the reported issue is regarding a created cluster, please provide requested info below
-->
**Cluster information**
- Cluster type (Hosted/Infrastructure Provider/Custom/Imported): rke AWS
- Kubernetes version (use `kubectl version`):
```
1.17
```
| 1.0 | Panic seen in rancher server logs on master - **What kind of request is this (question/bug/enhancement/feature request):** bug
**Steps to reproduce (least amount of steps as possible):**
- Bring up a master-head.
- Deploy an AWS rke cluster - 7 nodes - 3 etcd, 2 control planes and 2 worker nodes.
- Panic is seen in the rancher server logs
```
2020/02/25 18:54:25 [INFO] [node-controller-rancher-machine] Copying certs to the remote machine...
2020/02/25 18:56:29 [INFO] [node-controller-rancher-machine] Setting Docker configuration on the remote daemon...
2020/02/25 18:56:29 [INFO] [node-controller-rancher-machine] Setting Docker configuration on the remote daemon...
2020/02/25 18:56:29 [INFO] [node-controller-rancher-machine] Setting Docker configuration on the remote daemon...
2020/02/25 18:56:29 [INFO] [node-controller-rancher-machine] Setting Docker configuration on the remote daemon...
2020/02/25 18:56:29 [INFO] [node-controller-rancher-machine] Setting Docker configuration on the remote daemon...
2020/02/25 18:56:30 [INFO] [node-controller-rancher-machine] Setting Docker configuration on the remote daemon...
2020/02/25 18:56:30 [INFO] [node-controller-rancher-machine] Setting Docker configuration on the remote daemon...
E0225 18:57:42.886737 25 watcher.go:214] watch chan error: etcdserver: mvcc: required revision has been compacted
2020/02/25 18:58:14 [INFO] [node-controller-rancher-machine] Checking connection to Docker...
2020/02/25 18:58:15 [INFO] [node-controller-rancher-machine] Checking connection to Docker...
2020/02/25 18:58:15 [INFO] [node-controller-rancher-machine] Checking connection to Docker...
2020/02/25 18:58:15 [INFO] [node-controller-rancher-machine] Checking connection to Docker...
2020/02/25 18:58:15 [INFO] [node-controller-rancher-machine] Checking connection to Docker...
2020/02/25 18:58:16 [INFO] [node-controller-rancher-machine] Checking connection to Docker...
2020/02/25 18:58:16 [INFO] [node-controller-rancher-machine] Checking connection to Docker...
2020/02/25 18:58:55 [INFO] [node-controller-rancher-machine] Docker is up and running!
I0225 18:58:55.770509 25 controller.go:606] quota admission added evaluator for: clusterregistrationtokens.management.cattle.io
2020/02/25 18:58:55 [INFO] [node-controller-rancher-machine] Docker is up and running!
2020/02/25 18:58:56 [INFO] [node-controller-rancher-machine] Docker is up and running!
2020/02/25 18:58:56 [INFO] [node-controller-rancher-machine] Docker is up and running!
2020/02/25 18:58:56 [INFO] [node-controller-rancher-machine] Docker is up and running!
2020/02/25 18:58:56 [INFO] [node-controller-rancher-machine] Docker is up and running!
2020/02/25 18:58:57 [INFO] [node-controller-rancher-machine] Docker is up and running!
2020-02-25 18:59:00.912986 I | mvcc: store.index: compact 18818
2020-02-25 18:59:00.938969 I | mvcc: finished scheduled compaction at 18818 (took 24.852888ms)
2020/02/25 18:59:44 [INFO] Provisioning node sowmya-etcd-master-1 done
2020/02/25 18:59:44 [INFO] Generating and uploading node config sowmya-etcd-master-1
2020/02/25 18:59:44 [INFO] Provisioning node sowmya-worker-master-2 done
2020/02/25 18:59:44 [INFO] Generating and uploading node config sowmya-worker-master-2
2020/02/25 18:59:44 [INFO] Provisioning node sowmya-etcd-master-2 done
2020/02/25 18:59:44 [INFO] Generating and uploading node config sowmya-etcd-master-2
2020/02/25 18:59:44 [INFO] Creating jail for c-lcwlv
2020/02/25 18:59:44 [INFO] Generating and uploading node config
2020/02/25 18:59:44 [INFO] Provisioning node sowmya-ctrl-master-1 done
2020/02/25 18:59:44 [INFO] Generating and uploading node config sowmya-ctrl-master-1
2020/02/25 18:59:44 [INFO] Creating jail for c-lcwlv
2020/02/25 18:59:44 [INFO] Provisioning node sowmya-etcd-master-3 done
2020/02/25 18:59:44 [INFO] Generating and uploading node config sowmya-etcd-master-3
2020/02/25 18:59:44 [INFO] Generating and uploading node config
2020/02/25 18:59:44 [INFO] Creating jail for c-lcwlv
2020/02/25 18:59:44 [INFO] Generating and uploading node config
2020/02/25 18:59:44 [INFO] Provisioning node sowmya-worker-master-1 done
2020/02/25 18:59:44 [INFO] Generating and uploading node config sowmya-worker-master-1
2020/02/25 18:59:44 [INFO] Creating jail for c-lcwlv
2020/02/25 18:59:44 [INFO] Generating and uploading node config
2020/02/25 18:59:44 [INFO] Provisioning node sowmya-ctrl-master-2 done
2020/02/25 18:59:44 [INFO] Generating and uploading node config sowmya-ctrl-master-2
2020/02/25 18:59:44 [INFO] Creating jail for c-lcwlv
2020/02/25 18:59:44 [INFO] Generating and uploading node config
2020/02/25 18:59:44 [INFO] Provisioning cluster [c-lcwlv]
2020/02/25 18:59:44 [INFO] Creating cluster [c-lcwlv]
2020/02/25 18:59:44 [INFO] Handling backend connection request [c-lcwlv:m-w6tbj]
2020/02/25 18:59:44 [INFO] Handling backend connection request [c-lcwlv:m-jvgsg]
2020/02/25 18:59:44 [INFO] Handling backend connection request [c-lcwlv:m-h654g]
fatal error: concurrent map writes
goroutine 24443 [running]:
runtime.throw(0x3d09a84, 0x15)
/usr/local/go/src/runtime/panic.go:774 +0x72 fp=0xc003ffb660 sp=0xc003ffb630 pc=0x42fb12
runtime.mapassign(0x34400e0, 0xc0036f9020, 0xc003ffb758, 0x12)
/usr/local/go/src/runtime/map.go:588 +0x5c3 fp=0xc003ffb6e8 sp=0xc003ffb660 pc=0x40eb93
github.com/rancher/rancher/vendor/github.com/rancher/rke/metadata.initK8sRKESystemImages(0xc0036d5e30, 0xc0036f85a0, 0xc0036f85d0, 0xc0036f8ab0, 0xc0036f8ae0, 0xc0036f8b40, 0xc0036f8b70, 0xc0036f8ba0, 0xc0036f8db0, 0xc0036f8de0)
/go/src/github.com/rancher/rancher/vendor/github.com/rancher/rke/metadata/metadata.go:129 +0x41a fp=0xc003ffc2a8 sp=0xc003ffb6e8 pc=0x1fef27a
github.com/rancher/rancher/vendor/github.com/rancher/rke/metadata.InitMetadata(0x453e780, 0xc0036d51a0, 0x0, 0x0)
/go/src/github.com/rancher/rancher/vendor/github.com/rancher/rke/metadata/metadata.go:46 +0xf8 fp=0xc003ffc468 sp=0xc003ffc2a8 pc=0x1fee5e8
github.com/rancher/rancher/vendor/github.com/rancher/rke/cluster.InitClusterObject(0x453e780, 0xc0036d51a0, 0xc003ffcfc8, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/go/src/github.com/rancher/rancher/vendor/github.com/rancher/rke/cluster/cluster.go:587 +0x8c3 fp=0xc003ffc540 sp=0xc003ffc468 pc=0x20b72b3
github.com/rancher/rancher/vendor/github.com/rancher/rke/cluster.GeneratePlan(0x453e780, 0xc0036d51a0, 0xc002166fc8, 0xc0036d5710, 0xc0036d58c0, 0x0, 0x7f86002e2200, 0x69db7c0, 0x12, 0x198)
/go/src/github.com/rancher/rancher/vendor/github.com/rancher/rke/cluster/plan.go:74 +0x95 fp=0xc003ffcf78 sp=0xc003ffc540 pc=0x20cfbb5
github.com/rancher/rancher/pkg/librke.(*rke).GeneratePlan(0x0, 0x453e780, 0xc0036d51a0, 0xc0022cf000, 0xc0036d5710, 0xc0036d58c0, 0x0, 0x0, 0x39059a0, 0xc004a90900, ...)
/go/src/github.com/rancher/rancher/pkg/librke/rke.go:25 +0x82 fp=0xc003ffd7a8 sp=0xc003ffcf78 pc=0x221dce2
github.com/rancher/rancher/pkg/rkenodeconfigserver.(*RKENodeConfigServer).nonWorkerConfig(0xc0010ac720, 0x453e780, 0xc0036d51a0, 0xc003d52100, 0xc004a90900, 0x0, 0x10, 0x32d8ce0)
/go/src/github.com/rancher/rancher/pkg/rkenodeconfigserver/nodeserver.go:147 +0x28f fp=0xc003ffd970 sp=0xc003ffd7a8 pc=0x2bbdd7f
github.com/rancher/rancher/pkg/rkenodeconfigserver.(*RKENodeConfigServer).ServeHTTP(0xc0010ac720, 0x451da40, 0xc00153acb8, 0xc0026c9500)
/go/src/github.com/rancher/rancher/pkg/rkenodeconfigserver/nodeserver.go:95 +0x190 fp=0xc003ffda60 sp=0xc003ffd970 pc=0x2bbd4d0
github.com/rancher/rancher/server/responsewriter.ContentTypeOptions.func1(0x451da40, 0xc00153acb8, 0xc0026c9500)
/go/src/github.com/rancher/rancher/server/responsewriter/cache.go:47 +0x131 fp=0xc003ffdac8 sp=0xc003ffda60 pc=0x19375a1
net/http.HandlerFunc.ServeHTTP(0xc00262fe80, 0x451da40, 0xc00153acb8, 0xc0026c9500)
/usr/local/go/src/net/http/server.go:2007 +0x44 fp=0xc003ffdaf0 sp=0xc003ffdac8 pc=0x6fd104
github.com/rancher/rancher/vendor/github.com/gorilla/mux.(*Router).ServeHTTP(0xc000a1e000, 0x451da40, 0xc00153acb8, 0xc0026c9300)
/go/src/github.com/rancher/rancher/vendor/github.com/gorilla/mux/mux.go:212 +0xe2 fp=0xc003ffdc20 sp=0xc003ffdaf0 pc=0x192cbc2
github.com/rancher/rancher/vendor/github.com/rancher/dynamiclistener/server.wrapHandler.func1(0x451da40, 0xc00153acb8, 0xc0026c9300)
/go/src/github.com/rancher/rancher/vendor/github.com/rancher/dynamiclistener/server/server.go:187 +0x95 fp=0xc003ffdc60 sp=0xc003ffdc20 pc=0x259cdf5
net/http.HandlerFunc.ServeHTTP(0xc001e2a510, 0x451da40, 0xc00153acb8, 0xc0026c9300)
/usr/local/go/src/net/http/server.go:2007 +0x44 fp=0xc003ffdc88 sp=0xc003ffdc60 pc=0x6fd104
github.com/rancher/rancher/vendor/github.com/rancher/dynamiclistener.HTTPRedirect.func1(0x451da40, 0xc00153acb8, 0xc0026c9300)
/go/src/github.com/rancher/rancher/vendor/github.com/rancher/dynamiclistener/redirect.go:20 +0x221 fp=0xc003ffdd00 sp=0xc003ffdc88 pc=0x257af31
net/http.HandlerFunc.ServeHTTP(0xc001e131a0, 0x451da40, 0xc00153acb8, 0xc0026c9300)
/usr/local/go/src/net/http/server.go:2007 +0x44 fp=0xc003ffdd28 sp=0xc003ffdd00 pc=0x6fd104
net/http.serverHandler.ServeHTTP(0xc000151b20, 0x451da40, 0xc00153acb8, 0xc0026c9300)
/usr/local/go/src/net/http/server.go:2802 +0xa4 fp=0xc003ffdd58 sp=0xc003ffdd28 pc=0x700554
net/http.initNPNRequest.ServeHTTP(0x453e780, 0xc003741bf0, 0xc0032a4a80, 0xc000151b20, 0x451da40, 0xc00153acb8, 0xc0026c9300)
/usr/local/go/src/net/http/server.go:3365 +0x8d fp=0xc003ffded0 sp=0xc003ffdd58 pc=0x702e6d
net/http.(*initNPNRequest).ServeHTTP(0xc000d42a40, 0x451da40, 0xc00153acb8, 0xc0026c9300)
<autogenerated>:1 +0x75 fp=0xc003ffdf18 sp=0xc003ffded0 pc=0x72b915
net/http.Handler.ServeHTTP-fm(0x451da40, 0xc00153acb8, 0xc0026c9300)
/usr/local/go/src/net/http/server.go:86 +0x4d fp=0xc003ffdf48 sp=0xc003ffdf18 pc=0x72c56d
net/http.(*http2serverConn).runHandler(0xc004026600, 0xc00153acb8, 0xc0026c9300, 0xc00262fe20)
/usr/local/go/src/net/http/h2_bundle.go:5713 +0x9f fp=0xc003ffdfc0 sp=0xc003ffdf48 pc=0x6d4abf
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1357 +0x1 fp=0xc003ffdfc8 sp=0xc003ffdfc0 pc=0x45f7a1
created by net/http.(*http2serverConn).processHeaders
/usr/local/go/src/net/http/h2_bundle.go:5447 +0x4eb
goroutine 1 [chan receive, 75 minutes]:
github.com/rancher/rancher/pkg/tls.ListenAndServe(0x453e6c0, 0xc0011684c0, 0xc000dc6af0, 0x44a9a60, 0xc000a1e000, 0x1bb, 0x50, 0x0, 0x0, 0x0, ...)
/go/src/github.com/rancher/rancher/pkg/tls/tls.go:54 +0x29a
github.com/rancher/rancher/app.(*Rancher).ListenAndServe(0xc000d4a460, 0x453e6c0, 0xc0011684c0, 0xc00076adc0, 0xc001425348)
/go/src/github.com/rancher/rancher/app/app.go:73 +0xdd
main.run(0xc000d489a0, 0x0, 0x0, 0x0, 0x3cd54ee, 0x4, 0x1, 0x50, 0x1bb, 0x3cd54ee, ...)
/go/src/github.com/rancher/rancher/main.go:227 +0x3fd
main.main.func1(0xc000d489a0, 0x0, 0xc000f3a310)
/go/src/github.com/rancher/rancher/main.go:170 +0x130
github.com/rancher/rancher/vendor/github.com/urfave/cli.HandleAction(0x32fce00, 0xc0002b5fc0, 0xc000d489a0, 0xc000d489a0, 0x0)
/go/src/github.com/rancher/rancher/vendor/github.com/urfave/cli/app.go:523 +0xbe
github.com/rancher/rancher/vendor/github.com/urfave/cli.(*App).Run(0xc000b52380, 0xc00004c080, 0x8, 0x8, 0x0, 0x0)
/go/src/github.com/rancher/rancher/vendor/github.com/urfave/cli/app.go:285 +0x5ec
main.main()
```
**Actual Result:**
- Panic is seen in the logs.
- Rancher server seems to have restarted after.
**Expected Result:**
No panic should be seen in the rancher server
**Other details that may be helpful:**
**Environment information**
- Rancher version (`rancher/rancher`/`rancher/server` image tag or shown bottom left in the UI): master-head - commit id: `6085a90e2`
- Installation option (single install/HA): single
<!--
If the reported issue is regarding a created cluster, please provide requested info below
-->
**Cluster information**
- Cluster type (Hosted/Infrastructure Provider/Custom/Imported): rke AWS
- Kubernetes version (use `kubectl version`):
```
1.17
```
| test | panic seen in rancher server logs on master what kind of request is this question bug enhancement feature request bug steps to reproduce least amount of steps as possible bring up a master head deploy an aws rke cluster nodes etcd control planes and worker nodes panic is seen in the rancher server logs copying certs to the remote machine setting docker configuration on the remote daemon setting docker configuration on the remote daemon setting docker configuration on the remote daemon setting docker configuration on the remote daemon setting docker configuration on the remote daemon setting docker configuration on the remote daemon setting docker configuration on the remote daemon watcher go watch chan error etcdserver mvcc required revision has been compacted checking connection to docker checking connection to docker checking connection to docker checking connection to docker checking connection to docker checking connection to docker checking connection to docker docker is up and running controller go quota admission added evaluator for clusterregistrationtokens management cattle io docker is up and running docker is up and running docker is up and running docker is up and running docker is up and running docker is up and running i mvcc store index compact i mvcc finished scheduled compaction at took provisioning node sowmya etcd master done generating and uploading node config sowmya etcd master provisioning node sowmya worker master done generating and uploading node config sowmya worker master provisioning node sowmya etcd master done generating and uploading node config sowmya etcd master creating jail for c lcwlv generating and uploading node config provisioning node sowmya ctrl master done generating and uploading node config sowmya ctrl master creating jail for c lcwlv provisioning node sowmya etcd master done generating and uploading node config sowmya etcd master generating and uploading node config creating jail for c lcwlv generating and uploading node config provisioning node sowmya worker master done generating and uploading node config sowmya worker master creating jail for c lcwlv generating and uploading node config provisioning node sowmya ctrl master done generating and uploading node config sowmya ctrl master creating jail for c lcwlv generating and uploading node config provisioning cluster creating cluster handling backend connection request handling backend connection request handling backend connection request fatal error concurrent map writes goroutine runtime throw usr local go src runtime panic go fp sp pc runtime mapassign usr local go src runtime map go fp sp pc github com rancher rancher vendor github com rancher rke metadata go src github com rancher rancher vendor github com rancher rke metadata metadata go fp sp pc github com rancher rancher vendor github com rancher rke metadata initmetadata go src github com rancher rancher vendor github com rancher rke metadata metadata go fp sp pc github com rancher rancher vendor github com rancher rke cluster initclusterobject go src github com rancher rancher vendor github com rancher rke cluster cluster go fp sp pc github com rancher rancher vendor github com rancher rke cluster generateplan go src github com rancher rancher vendor github com rancher rke cluster plan go fp sp pc github com rancher rancher pkg librke rke generateplan go src github com rancher rancher pkg librke rke go fp sp pc github com rancher rancher pkg rkenodeconfigserver rkenodeconfigserver nonworkerconfig go src github com rancher rancher pkg rkenodeconfigserver nodeserver go fp sp pc github com rancher rancher pkg rkenodeconfigserver rkenodeconfigserver servehttp go src github com rancher rancher pkg rkenodeconfigserver nodeserver go fp sp pc github com rancher rancher server responsewriter contenttypeoptions go src github com rancher rancher server responsewriter cache go fp sp pc net http handlerfunc servehttp usr local go src net http server go fp sp pc github com rancher rancher vendor github com gorilla mux router servehttp go src github com rancher rancher vendor github com gorilla mux mux go fp sp pc github com rancher rancher vendor github com rancher dynamiclistener server wraphandler go src github com rancher rancher vendor github com rancher dynamiclistener server server go fp sp pc net http handlerfunc servehttp usr local go src net http server go fp sp pc github com rancher rancher vendor github com rancher dynamiclistener httpredirect go src github com rancher rancher vendor github com rancher dynamiclistener redirect go fp sp pc net http handlerfunc servehttp usr local go src net http server go fp sp pc net http serverhandler servehttp usr local go src net http server go fp sp pc net http initnpnrequest servehttp usr local go src net http server go fp sp pc net http initnpnrequest servehttp fp sp pc net http handler servehttp fm usr local go src net http server go fp sp pc net http runhandler usr local go src net http bundle go fp sp pc runtime goexit usr local go src runtime asm s fp sp pc created by net http processheaders usr local go src net http bundle go goroutine github com rancher rancher pkg tls listenandserve go src github com rancher rancher pkg tls tls go github com rancher rancher app rancher listenandserve go src github com rancher rancher app app go main run go src github com rancher rancher main go main main go src github com rancher rancher main go github com rancher rancher vendor github com urfave cli handleaction go src github com rancher rancher vendor github com urfave cli app go github com rancher rancher vendor github com urfave cli app run go src github com rancher rancher vendor github com urfave cli app go main main actual result panic is seen in the logs rancher server seems to have restarted after expected result no panic should be seen in the rancher server other details that may be helpful environment information rancher version rancher rancher rancher server image tag or shown bottom left in the ui master head commit id installation option single install ha single if the reported issue is regarding a created cluster please provide requested info below cluster information cluster type hosted infrastructure provider custom imported rke aws kubernetes version use kubectl version | 1 |
813,294 | 30,452,572,694 | IssuesEvent | 2023-07-16 13:35:49 | Laravel-Backpack/demo | https://api.github.com/repos/Laravel-Backpack/demo | closed | v6 Demo doesn't have many new features. | enhancement Priority: SHOULD Size: M | Live v6 Demo doesn't have many new features:
Few :
- [Show Operation Tabs](https://backpackforlaravel.com/docs/5.x/crud-operation-show#tabs-display-columns-in-tabs)
- Repeatable Column
- Dropzone Column
- etc.
We should review the demo.
- [x] List missing features, columns, and fields.
- [ ] Showcase them in [Monster](https://demo-v6.backpackforlaravel.com/admin/monster)
| 1.0 | v6 Demo doesn't have many new features. - Live v6 Demo doesn't have many new features:
Few :
- [Show Operation Tabs](https://backpackforlaravel.com/docs/5.x/crud-operation-show#tabs-display-columns-in-tabs)
- Repeatable Column
- Dropzone Column
- etc.
We should review the demo.
- [x] List missing features, columns, and fields.
- [ ] Showcase them in [Monster](https://demo-v6.backpackforlaravel.com/admin/monster)
| non_test | demo doesn t have many new features live demo doesn t have many new features few repeatable column dropzone column etc we should review the demo list missing features columns and fields showcase them in | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.