character is inserted, thus no list is produced either. I add a screenshot, documenting my input of - test, with the WISIWIG editor enabled and disabled.
+3. More steps…
+
+
+
+### Outcome
+
+#### What did you expect?
+The enabled WISIWIG editor should not evaluate shift Carriage-Return as Carriage-Return
+the disabled WISIWIG editor should display a shift Carriage-Return as Carriage-Return and not as
+#### What happened instead?
+
+
+### Operating system
+
+macOS 12.6 (21G115)
+
+### Browser information
+
+Safari 16.0 (17614.1.25.9.10, 17614)
+
+### URL for webapp
+
+https://develop.element.io
+
+### Application version
+
+Version von Element: 5da11ae43654-react-0173e211294c-js-b44787192db1 Version von Olm: 3.2.12
+
+### Homeserver
+
+synod.im
+
+### Will you send logs?
+
+Yes",0,wisiwig editor cannot be used to enter a bulleted list steps to reproduce where are you starting what can you see i want to enter a message with a bulleted list included what do you click when i try to enter a newline with shift carriage return the input line is closed if the editor is active this is possible if the editor is not active then however a character is inserted thus no list is produced either i add a screenshot documenting my input of test with the wisiwig editor enabled and disabled more steps… outcome what did you expect the enabled wisiwig editor should not evaluate shift carriage return as carriage return the disabled wisiwig editor should display a shift carriage return as carriage return and not as what happened instead operating system macos browser information safari url for webapp application version version von element react js version von olm homeserver synod im will you send logs yes,0
+17834,12371791067.0,IssuesEvent,2020-05-18 19:11:59,godotengine/godot,https://api.github.com/repos/godotengine/godot,opened,Autocompletion spams errors on invalid get_child() index,bug topic:editor topic:gdscript usability,"**Godot version:**
+3.2.1
+
+**Steps to reproduce:**
+1. Create a new scene with root node
+2. Add script to root node
+3. Type `get_child(1).` in the script and press Ctrl + Space
+4. The console gets spammed with errors
+
+This is because the Script Editor tries to get the node from get_child() method, but the node doesn't exist. The editor should check index before calling get_child() and ignore it if it's invalid.",True,"Autocompletion spams errors on invalid get_child() index - **Godot version:**
+3.2.1
+
+**Steps to reproduce:**
+1. Create a new scene with root node
+2. Add script to root node
+3. Type `get_child(1).` in the script and press Ctrl + Space
+4. The console gets spammed with errors
+
+This is because the Script Editor tries to get the node from get_child() method, but the node doesn't exist. The editor should check index before calling get_child() and ignore it if it's invalid.",1,autocompletion spams errors on invalid get child index godot version steps to reproduce create a new scene with root node add script to root node type get child in the script and press ctrl space the console gets spammed with errors this is because the script editor tries to get the node from get child method but the node doesn t exist the editor should check index before calling get child and ignore it if it s invalid ,1
+157396,19957194841.0,IssuesEvent,2022-01-28 01:35:35,scottstientjes/snipe-it,https://api.github.com/repos/scottstientjes/snipe-it,opened,"CVE-2020-28469 (High) detected in glob-parent-3.1.0.tgz, glob-parent-2.0.0.tgz",security vulnerability,"## CVE-2020-28469 - High Severity Vulnerability
+
Vulnerable Libraries - glob-parent-3.1.0.tgz, glob-parent-2.0.0.tgz
+
+
+glob-parent-3.1.0.tgz
+
+Strips glob magic from a string to provide the parent directory path
+Library home page: https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz
+Path to dependency file: /package.json
+Path to vulnerable library: /node_modules/glob-parent/package.json
+
+
+Dependency Hierarchy:
+ - laravel-mix-2.1.11.tgz (Root Library)
+ - chokidar-2.0.3.tgz
+ - :x: **glob-parent-3.1.0.tgz** (Vulnerable Library)
+
+
glob-parent-2.0.0.tgz
+
+Strips glob magic from a string to provide the parent path
+Library home page: https://registry.npmjs.org/glob-parent/-/glob-parent-2.0.0.tgz
+Path to dependency file: /package.json
+Path to vulnerable library: /node_modules/glob-base/node_modules/glob-parent/package.json
+
+
+Dependency Hierarchy:
+ - laravel-mix-2.1.11.tgz (Root Library)
+ - webpack-dev-server-2.11.2.tgz
+ - http-proxy-middleware-0.17.4.tgz
+ - micromatch-2.3.11.tgz
+ - parse-glob-3.0.4.tgz
+ - glob-base-0.3.0.tgz
+ - :x: **glob-parent-2.0.0.tgz** (Vulnerable Library)
+
+
+
+
+
+
Vulnerability Details
+
+
+This affects the package glob-parent before 5.1.2. The enclosure regex used to check for strings ending in enclosure containing path separator.
+
+
Publish Date: 2021-06-03
+
URL: CVE-2020-28469
+
+
+
+
CVSS 3 Score Details (7.5)
+
+
+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 CVSS3 Scores, click here.
+
+
+
+
Suggested Fix
+
+
+
Type: Upgrade version
+Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28469
+Release Date: 2021-06-03
+Fix Resolution (glob-parent): 5.1.2
+Direct dependency fix Resolution (laravel-mix): 6.0.0-beta.15
Fix Resolution (glob-parent): 5.1.2
+Direct dependency fix Resolution (laravel-mix): 6.0.0-beta.15
+
+
+
+
+
+***
+Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2020-28469 (High) detected in glob-parent-3.1.0.tgz, glob-parent-2.0.0.tgz - ## CVE-2020-28469 - High Severity Vulnerability
+
Vulnerable Libraries - glob-parent-3.1.0.tgz, glob-parent-2.0.0.tgz
+
+
+glob-parent-3.1.0.tgz
+
+Strips glob magic from a string to provide the parent directory path
+Library home page: https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz
+Path to dependency file: /package.json
+Path to vulnerable library: /node_modules/glob-parent/package.json
+
+
+Dependency Hierarchy:
+ - laravel-mix-2.1.11.tgz (Root Library)
+ - chokidar-2.0.3.tgz
+ - :x: **glob-parent-3.1.0.tgz** (Vulnerable Library)
+
+
glob-parent-2.0.0.tgz
+
+Strips glob magic from a string to provide the parent path
+Library home page: https://registry.npmjs.org/glob-parent/-/glob-parent-2.0.0.tgz
+Path to dependency file: /package.json
+Path to vulnerable library: /node_modules/glob-base/node_modules/glob-parent/package.json
+
+
+Dependency Hierarchy:
+ - laravel-mix-2.1.11.tgz (Root Library)
+ - webpack-dev-server-2.11.2.tgz
+ - http-proxy-middleware-0.17.4.tgz
+ - micromatch-2.3.11.tgz
+ - parse-glob-3.0.4.tgz
+ - glob-base-0.3.0.tgz
+ - :x: **glob-parent-2.0.0.tgz** (Vulnerable Library)
+
+
+
+
+
+
Vulnerability Details
+
+
+This affects the package glob-parent before 5.1.2. The enclosure regex used to check for strings ending in enclosure containing path separator.
+
+
Publish Date: 2021-06-03
+
URL: CVE-2020-28469
+
+
+
+
CVSS 3 Score Details (7.5)
+
+
+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 CVSS3 Scores, click here.
+
+
+
+
Suggested Fix
+
+
+
Type: Upgrade version
+Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28469
+Release Date: 2021-06-03
+Fix Resolution (glob-parent): 5.1.2
+Direct dependency fix Resolution (laravel-mix): 6.0.0-beta.15
Fix Resolution (glob-parent): 5.1.2
+Direct dependency fix Resolution (laravel-mix): 6.0.0-beta.15
+
+
+
+
+
+***
+Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve high detected in glob parent tgz glob parent tgz cve high severity vulnerability vulnerable libraries glob parent tgz glob parent tgz glob parent tgz strips glob magic from a string to provide the parent directory path library home page a href path to dependency file package json path to vulnerable library node modules glob parent package json dependency hierarchy laravel mix tgz root library chokidar tgz x glob parent tgz vulnerable library glob parent tgz strips glob magic from a string to provide the parent path library home page a href path to dependency file package json path to vulnerable library node modules glob base node modules glob parent package json dependency hierarchy laravel mix tgz root library webpack dev server tgz http proxy middleware tgz micromatch tgz parse glob tgz glob base tgz x glob parent tgz vulnerable library vulnerability details this affects the package glob parent before the enclosure regex used to check for strings ending in enclosure containing path separator 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 glob parent direct dependency fix resolution laravel mix beta fix resolution glob parent direct dependency fix resolution laravel mix beta step up your open source security game with whitesource ,0
+231971,7647318745.0,IssuesEvent,2018-05-09 03:12:38,gravityview/GravityView,https://api.github.com/repos/gravityview/GravityView,opened,"Labels visible when ""Show label"" not checked",Bug Core: Templates Priority: High,Not template-specific; affecting the [1.x Map layout](https://demo.gravityview.co/view/map/) as well as the [2.0 List layout](https://demo.gravityview.co/view/list/).,1.0,"Labels visible when ""Show label"" not checked - Not template-specific; affecting the [1.x Map layout](https://demo.gravityview.co/view/map/) as well as the [2.0 List layout](https://demo.gravityview.co/view/list/).",0,labels visible when show label not checked not template specific affecting the as well as the ,0
+15182,9818594189.0,IssuesEvent,2019-06-13 19:40:10,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Ability for godot to remember collapsed items in input map editor panel.,enhancement topic:editor usability,"Godot v2.1.3
+
+[Low priority]
+
+Feature request:
+Currently collapsed items in input map editor panel always get expanded when editing the remaps.
+I'm asking the ability for godot to remember collapsed items in input map editor panel.
+
+Because my english sucks I've recorded a gif showing the current behavior.
+
+
+",True,"Ability for godot to remember collapsed items in input map editor panel. - Godot v2.1.3
+
+[Low priority]
+
+Feature request:
+Currently collapsed items in input map editor panel always get expanded when editing the remaps.
+I'm asking the ability for godot to remember collapsed items in input map editor panel.
+
+Because my english sucks I've recorded a gif showing the current behavior.
+
+
+",1,ability for godot to remember collapsed items in input map editor panel godot feature request currently collapsed items in input map editor panel always get expanded when editing the remaps i m asking the ability for godot to remember collapsed items in input map editor panel because my english sucks i ve recorded a gif showing the current behavior ,1
+504766,14620961687.0,IssuesEvent,2020-12-22 20:42:26,LBL-EESA/TECA,https://api.github.com/repos/LBL-EESA/TECA,opened,pressure from sea level pressure,1_high_priority,"For the IVT integral in highresmip, we should mask values that are below the ground surface. Most models have sea level pressure (variable name `psl`); with a surface elevation field, surface pressure can be estimated. The condition for valid data is then $p >= ps$, where `ps` is the surface pressure.
+
+A particular model has both ps and psl, which should facilitate testing:
+
+PSL:
+/global/cfs/cdirs/m3522/cmip6/CMIP6_hrmcol/HighResMIP/CMIP6/HighResMIP/ECMWF/ECMWF-IFS-HR/highresSST-present/r1i1p1f1/6hrPlevPt/psl/gr/v20170915/
+
+PS:
+/global/cfs/cdirs/m3522/cmip6/CMIP6_hrmcol/HighResMIP/CMIP6/HighResMIP/ECMWF/ECMWF-IFS-HR/highresSST-present/r1i1p1f1/Prim6hrPt/ps/gr/v20170915",1.0,"pressure from sea level pressure - For the IVT integral in highresmip, we should mask values that are below the ground surface. Most models have sea level pressure (variable name `psl`); with a surface elevation field, surface pressure can be estimated. The condition for valid data is then $p >= ps$, where `ps` is the surface pressure.
+
+A particular model has both ps and psl, which should facilitate testing:
+
+PSL:
+/global/cfs/cdirs/m3522/cmip6/CMIP6_hrmcol/HighResMIP/CMIP6/HighResMIP/ECMWF/ECMWF-IFS-HR/highresSST-present/r1i1p1f1/6hrPlevPt/psl/gr/v20170915/
+
+PS:
+/global/cfs/cdirs/m3522/cmip6/CMIP6_hrmcol/HighResMIP/CMIP6/HighResMIP/ECMWF/ECMWF-IFS-HR/highresSST-present/r1i1p1f1/Prim6hrPt/ps/gr/v20170915",0,pressure from sea level pressure for the ivt integral in highresmip we should mask values that are below the ground surface most models have sea level pressure variable name psl with a surface elevation field surface pressure can be estimated the condition for valid data is then p ps where ps is the surface pressure a particular model has both ps and psl which should facilitate testing psl global cfs cdirs hrmcol highresmip highresmip ecmwf ecmwf ifs hr highressst present psl gr ps global cfs cdirs hrmcol highresmip highresmip ecmwf ecmwf ifs hr highressst present ps gr ,0
+247982,26771142058.0,IssuesEvent,2023-01-31 14:12:48,samqws-test/juice-shop,https://api.github.com/repos/samqws-test/juice-shop,opened,sqlite3-5.0.9.tgz: 1 vulnerabilities (highest severity is: 5.3),security vulnerability,"
Vulnerable Library - sqlite3-5.0.9.tgz
+
+
+Path to dependency file: /package.json
+Path to vulnerable library: /node_modules/make-fetch-happen/node_modules/http-cache-semantics/package.json
+
+
+
+
Found in HEAD commit: dfe26338e450e8fc50a889a1c616f7c847cd3363
+
+## Vulnerabilities
+
+| CVE | Severity |
CVSS | Dependency | Type | Fixed in (sqlite3 version) | Remediation Available |
+| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
+| [CVE-2022-25881](https://www.mend.io/vulnerability-database/CVE-2022-25881) |
Medium | 5.3 | http-cache-semantics-4.1.0.tgz | Transitive | N/A* | ❌ |
+
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the section ""Details"" below to see if there is a version of transitive dependency where vulnerability is fixed.
+
+## Details
+
+
+
+ CVE-2022-25881
+
+
+### Vulnerable Library - http-cache-semantics-4.1.0.tgz
+
+Parses Cache-Control and other headers. Helps building correct HTTP caches and proxies
+Library home page: https://registry.npmjs.org/http-cache-semantics/-/http-cache-semantics-4.1.0.tgz
+Path to dependency file: /package.json
+Path to vulnerable library: /node_modules/make-fetch-happen/node_modules/http-cache-semantics/package.json
+
+
+Dependency Hierarchy:
+ - sqlite3-5.0.9.tgz (Root Library)
+ - node-gyp-8.4.1.tgz
+ - make-fetch-happen-9.1.0.tgz
+ - :x: **http-cache-semantics-4.1.0.tgz** (Vulnerable Library)
+
Found in HEAD commit: dfe26338e450e8fc50a889a1c616f7c847cd3363
+Found in base branch: main
+
+
+
+
+### Vulnerability Details
+
+
+This affects versions of the package http-cache-semantics before 4.1.1. The issue can be exploited via malicious request header values sent to a server, when that server reads the cache policy from the request using this library.
+
+
Publish Date: 2023-01-31
+
URL: CVE-2022-25881
+
+
+
+
+### CVSS 3 Score Details (5.3)
+
+
+Base Score Metrics:
+- Exploitability Metrics:
+ - Attack Vector: Network
+ - Attack Complexity: Low
+ - Privileges Required: None
+ - User Interaction: None
+ - Scope: Unchanged
+- Impact Metrics:
+ - Confidentiality Impact: None
+ - Integrity Impact: None
+ - Availability Impact: Low
+
+For more information on CVSS3 Scores, click here.
+
+
+
+
+### Suggested Fix
+
+
+
Type: Upgrade version
+Origin: https://www.cve.org/CVERecord?id=CVE-2022-25881
+Release Date: 2023-01-31
+Fix Resolution: http-cache-semantics - 4.1.1
+
+
+
+
+
+ ",True,"sqlite3-5.0.9.tgz: 1 vulnerabilities (highest severity is: 5.3) -
Vulnerable Library - sqlite3-5.0.9.tgz
+
+
+Path to dependency file: /package.json
+Path to vulnerable library: /node_modules/make-fetch-happen/node_modules/http-cache-semantics/package.json
+
+
+
+
Found in HEAD commit: dfe26338e450e8fc50a889a1c616f7c847cd3363
+
+## Vulnerabilities
+
+| CVE | Severity |
CVSS | Dependency | Type | Fixed in (sqlite3 version) | Remediation Available |
+| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
+| [CVE-2022-25881](https://www.mend.io/vulnerability-database/CVE-2022-25881) |
Medium | 5.3 | http-cache-semantics-4.1.0.tgz | Transitive | N/A* | ❌ |
+
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the section ""Details"" below to see if there is a version of transitive dependency where vulnerability is fixed.
+
+## Details
+
+
+
+ CVE-2022-25881
+
+
+### Vulnerable Library - http-cache-semantics-4.1.0.tgz
+
+Parses Cache-Control and other headers. Helps building correct HTTP caches and proxies
+Library home page: https://registry.npmjs.org/http-cache-semantics/-/http-cache-semantics-4.1.0.tgz
+Path to dependency file: /package.json
+Path to vulnerable library: /node_modules/make-fetch-happen/node_modules/http-cache-semantics/package.json
+
+
+Dependency Hierarchy:
+ - sqlite3-5.0.9.tgz (Root Library)
+ - node-gyp-8.4.1.tgz
+ - make-fetch-happen-9.1.0.tgz
+ - :x: **http-cache-semantics-4.1.0.tgz** (Vulnerable Library)
+
Found in HEAD commit: dfe26338e450e8fc50a889a1c616f7c847cd3363
+Found in base branch: main
+
+
+
+
+### Vulnerability Details
+
+
+This affects versions of the package http-cache-semantics before 4.1.1. The issue can be exploited via malicious request header values sent to a server, when that server reads the cache policy from the request using this library.
+
+
Publish Date: 2023-01-31
+
URL: CVE-2022-25881
+
+
+
+
+### CVSS 3 Score Details (5.3)
+
+
+Base Score Metrics:
+- Exploitability Metrics:
+ - Attack Vector: Network
+ - Attack Complexity: Low
+ - Privileges Required: None
+ - User Interaction: None
+ - Scope: Unchanged
+- Impact Metrics:
+ - Confidentiality Impact: None
+ - Integrity Impact: None
+ - Availability Impact: Low
+
+For more information on CVSS3 Scores, click here.
+
+
+
+
+### Suggested Fix
+
+
+
Type: Upgrade version
+Origin: https://www.cve.org/CVERecord?id=CVE-2022-25881
+Release Date: 2023-01-31
+Fix Resolution: http-cache-semantics - 4.1.1
+
+
+
+
+
+ ",0, tgz vulnerabilities highest severity is vulnerable library tgz path to dependency file package json path to vulnerable library node modules make fetch happen node modules http cache semantics package json found in head commit a href vulnerabilities cve severity cvss dependency type fixed in version remediation available medium http cache semantics tgz transitive n a for some transitive vulnerabilities there is no version of direct dependency with a fix check the section details below to see if there is a version of transitive dependency where vulnerability is fixed details cve vulnerable library http cache semantics tgz parses cache control and other headers helps building correct http caches and proxies library home page a href path to dependency file package json path to vulnerable library node modules make fetch happen node modules http cache semantics package json dependency hierarchy tgz root library node gyp tgz make fetch happen tgz x http cache semantics tgz vulnerable library found in head commit a href found in base branch main vulnerability details this affects versions of the package http cache semantics before the issue can be exploited via malicious request header values sent to a server when that server reads the cache policy from the request using this library publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution http cache semantics ,0
+23956,16719505240.0,IssuesEvent,2021-06-10 04:50:24,proplants/plantbook,https://api.github.com/repos/proplants/plantbook,closed,Добавить оповещения о PR и Review в наш чат,infrastructure task,"есть [action](https://github.com/marketplace/actions/notify-telegram)
+
+предлагаю внедрить в процесс, а то руками напоминать, что я вот сделайте ПР сделайте ревью плиз )",1.0,"Добавить оповещения о PR и Review в наш чат - есть [action](https://github.com/marketplace/actions/notify-telegram)
+
+предлагаю внедрить в процесс, а то руками напоминать, что я вот сделайте ПР сделайте ревью плиз )",0,добавить оповещения о pr и review в наш чат есть предлагаю внедрить в процесс а то руками напоминать что я вот сделайте пр сделайте ревью плиз ,0
+242308,26264668118.0,IssuesEvent,2023-01-06 11:18:45,TreyM-WSS/ember-href-to,https://api.github.com/repos/TreyM-WSS/ember-href-to,opened,CVE-2020-36049 (High) detected in socket.io-parser-3.3.0.tgz,security vulnerability,"## CVE-2020-36049 - High Severity Vulnerability
+
Vulnerable Library - socket.io-parser-3.3.0.tgz
+
+socket.io protocol parser
+Library home page: https://registry.npmjs.org/socket.io-parser/-/socket.io-parser-3.3.0.tgz
+Path to dependency file: /package.json
+Path to vulnerable library: /node_modules/socket.io-client/node_modules/socket.io-parser/package.json
+
+
+Dependency Hierarchy:
+ - ember-cli-3.20.2.tgz (Root Library)
+ - testem-3.2.0.tgz
+ - socket.io-2.3.0.tgz
+ - socket.io-client-2.3.0.tgz
+ - :x: **socket.io-parser-3.3.0.tgz** (Vulnerable Library)
+
Found in HEAD commit: cd1f7af6517dd7e004966e102deb42ac27c4e3ac
+Found in base branch: master
+
+
+
+
Vulnerability Details
+
+
+socket.io-parser before 3.4.1 allows attackers to cause a denial of service (memory consumption) via a large packet because a concatenation approach is used.
+
+
Publish Date: 2021-01-08
+
URL: CVE-2020-36049
+
+
+
+
CVSS 3 Score Details (7.5)
+
+
+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 CVSS3 Scores, click here.
+
+
+
+
Suggested Fix
+
+
+
Type: Upgrade version
+Origin: https://github.com/advisories/GHSA-xfhh-g9f5-x4m4
+Release Date: 2021-01-08
+Fix Resolution (socket.io-parser): 3.3.2
+Direct dependency fix Resolution (ember-cli): 3.21.0
+
+
+
+
+
+***
+:rescue_worker_helmet: Automatic Remediation is available for this issue",True,"CVE-2020-36049 (High) detected in socket.io-parser-3.3.0.tgz - ## CVE-2020-36049 - High Severity Vulnerability
+
Vulnerable Library - socket.io-parser-3.3.0.tgz
+
+socket.io protocol parser
+Library home page: https://registry.npmjs.org/socket.io-parser/-/socket.io-parser-3.3.0.tgz
+Path to dependency file: /package.json
+Path to vulnerable library: /node_modules/socket.io-client/node_modules/socket.io-parser/package.json
+
+
+Dependency Hierarchy:
+ - ember-cli-3.20.2.tgz (Root Library)
+ - testem-3.2.0.tgz
+ - socket.io-2.3.0.tgz
+ - socket.io-client-2.3.0.tgz
+ - :x: **socket.io-parser-3.3.0.tgz** (Vulnerable Library)
+
Found in HEAD commit: cd1f7af6517dd7e004966e102deb42ac27c4e3ac
+Found in base branch: master
+
+
+
+
Vulnerability Details
+
+
+socket.io-parser before 3.4.1 allows attackers to cause a denial of service (memory consumption) via a large packet because a concatenation approach is used.
+
+
Publish Date: 2021-01-08
+
URL: CVE-2020-36049
+
+
+
+
CVSS 3 Score Details (7.5)
+
+
+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 CVSS3 Scores, click here.
+
+
+
+
Suggested Fix
+
+
+
Type: Upgrade version
+Origin: https://github.com/advisories/GHSA-xfhh-g9f5-x4m4
+Release Date: 2021-01-08
+Fix Resolution (socket.io-parser): 3.3.2
+Direct dependency fix Resolution (ember-cli): 3.21.0
+
+
+
+
+
+***
+:rescue_worker_helmet: Automatic Remediation is available for this issue",0,cve high detected in socket io parser tgz cve high severity vulnerability vulnerable library socket io parser tgz socket io protocol parser library home page a href path to dependency file package json path to vulnerable library node modules socket io client node modules socket io parser package json dependency hierarchy ember cli tgz root library testem tgz socket io tgz socket io client tgz x socket io parser tgz vulnerable library found in head commit a href found in base branch master vulnerability details socket io parser before allows attackers to cause a denial of service memory consumption via a large packet because a concatenation approach is used 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 socket io parser direct dependency fix resolution ember cli rescue worker helmet automatic remediation is available for this issue,0
+5940,4077223909.0,IssuesEvent,2016-05-30 06:57:04,godotengine/godot,https://api.github.com/repos/godotengine/godot,opened,Changing the language directly in the project manager,enhancement topic:editor usability,"Because we can, and since we spawn a new process for the editor anyway, it would be the right time to select another language.
+
+In a more practical context, it would also make it very easy to find if we want to encourage people to make screenshots in English for bug reports, and not in their own locale.",True,"Changing the language directly in the project manager - Because we can, and since we spawn a new process for the editor anyway, it would be the right time to select another language.
+
+In a more practical context, it would also make it very easy to find if we want to encourage people to make screenshots in English for bug reports, and not in their own locale.",1,changing the language directly in the project manager because we can and since we spawn a new process for the editor anyway it would be the right time to select another language in a more practical context it would also make it very easy to find if we want to encourage people to make screenshots in english for bug reports and not in their own locale ,1
+356759,25176256426.0,IssuesEvent,2022-11-11 09:31:28,HakkaNgin/pe,https://api.github.com/repos/HakkaNgin/pe,opened,"The destroy (X) marker should be directly adjacent to the rectangle under AddTagCommand, instead of leaving a space",severity.VeryLow type.DocumentationBug,"
+
+
+
+
+",1.0,"The destroy (X) marker should be directly adjacent to the rectangle under AddTagCommand, instead of leaving a space - 
+
+
+
+
+",0,the destroy x marker should be directly adjacent to the rectangle under addtagcommand instead of leaving a space ,0
+740226,25740182166.0,IssuesEvent,2022-12-08 05:14:54,googleapis/nodejs-ai-platform,https://api.github.com/repos/googleapis/nodejs-ai-platform,closed,"AI platform entity type api samples test: ""after all"" hook: should delete the created featurestore for ""should delete the created entity type"" failed",type: bug priority: p1 samples flakybot: issue api: vertex-ai,"Note: #356 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
+
+----
+
+commit: 04f7c858217f1a3ce7b1072c7bf8946d39947532
+buildURL: [Build Status](https://source.cloud.google.com/results/invocations/2c1b5aae-a46c-4a7a-a474-79da01e686eb), [Sponge](http://sponge2/2c1b5aae-a46c-4a7a-a474-79da01e686eb)
+status: failed
+
Test output
7 PERMISSION_DENIED: Permission denied: Consumer 'project:undefined' has been suspended.
+Error: 7 PERMISSION_DENIED: Permission denied: Consumer 'project:undefined' has been suspended.
+ at Object.callErrorFromStatus (/workspace/node_modules/@grpc/grpc-js/build/src/call.js:31:19)
+ -> /workspace/node_modules/@grpc/grpc-js/src/call.ts:81:17
+ at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/client.js:195:52)
+ -> /workspace/node_modules/@grpc/grpc-js/src/client.ts:358:36
+ at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:365:141)
+ -> /workspace/node_modules/@grpc/grpc-js/src/client-interceptors.ts:462:34
+ at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:328:181)
+ -> /workspace/node_modules/@grpc/grpc-js/src/client-interceptors.ts:424:48
+ at /workspace/node_modules/@grpc/grpc-js/build/src/call-stream.js:188:78
+ -> /workspace/node_modules/@grpc/grpc-js/src/call-stream.ts:334:24
+ at processTicksAndRejections (internal/process/task_queues.js:79:11)
+for call at
+ at ServiceClientImpl.makeUnaryRequest (/workspace/node_modules/@grpc/grpc-js/build/src/client.js:163:34)
+ -> /workspace/node_modules/@grpc/grpc-js/src/client.ts:328:30
+ at ServiceClientImpl. (/workspace/node_modules/@grpc/grpc-js/build/src/make-client.js:105:19)
+ -> /workspace/node_modules/@grpc/grpc-js/src/make-client.ts:189:15
+ at /workspace/build/src/v1/featurestore_service_client.js:1180:29
+ -> /workspace/src/v1/featurestore_service_client.ts:1488:25
+ at /workspace/node_modules/google-gax/build/src/normalCalls/timeout.js:44:16
+ -> /workspace/node_modules/google-gax/src/normalCalls/timeout.ts:54:13
+ at LongrunningApiCaller._wrapOperation (/workspace/node_modules/google-gax/build/src/longRunningCalls/longRunningApiCaller.js:55:16)
+ -> /workspace/node_modules/google-gax/src/longRunningCalls/longRunningApiCaller.ts:80:12
+ at /workspace/node_modules/google-gax/build/src/longRunningCalls/longRunningApiCaller.js:46:25
+ -> /workspace/node_modules/google-gax/src/longRunningCalls/longRunningApiCaller.ts:64:19
+ at OngoingCallPromise.call (/workspace/node_modules/google-gax/build/src/call.js:67:27)
+ -> /workspace/node_modules/google-gax/src/call.ts:81:23
+ at LongrunningApiCaller.call (/workspace/node_modules/google-gax/build/src/longRunningCalls/longRunningApiCaller.js:45:19)
+ -> /workspace/node_modules/google-gax/src/longRunningCalls/longRunningApiCaller.ts:63:15
+ at /workspace/node_modules/google-gax/build/src/createApiCall.js:84:30
+ -> /workspace/node_modules/google-gax/src/createApiCall.ts:118:26
",1.0,"AI platform entity type api samples test: ""after all"" hook: should delete the created featurestore for ""should delete the created entity type"" failed - Note: #356 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
+
+----
+
+commit: 04f7c858217f1a3ce7b1072c7bf8946d39947532
+buildURL: [Build Status](https://source.cloud.google.com/results/invocations/2c1b5aae-a46c-4a7a-a474-79da01e686eb), [Sponge](http://sponge2/2c1b5aae-a46c-4a7a-a474-79da01e686eb)
+status: failed
+
Test output
7 PERMISSION_DENIED: Permission denied: Consumer 'project:undefined' has been suspended.
+Error: 7 PERMISSION_DENIED: Permission denied: Consumer 'project:undefined' has been suspended.
+ at Object.callErrorFromStatus (/workspace/node_modules/@grpc/grpc-js/build/src/call.js:31:19)
+ -> /workspace/node_modules/@grpc/grpc-js/src/call.ts:81:17
+ at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/client.js:195:52)
+ -> /workspace/node_modules/@grpc/grpc-js/src/client.ts:358:36
+ at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:365:141)
+ -> /workspace/node_modules/@grpc/grpc-js/src/client-interceptors.ts:462:34
+ at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:328:181)
+ -> /workspace/node_modules/@grpc/grpc-js/src/client-interceptors.ts:424:48
+ at /workspace/node_modules/@grpc/grpc-js/build/src/call-stream.js:188:78
+ -> /workspace/node_modules/@grpc/grpc-js/src/call-stream.ts:334:24
+ at processTicksAndRejections (internal/process/task_queues.js:79:11)
+for call at
+ at ServiceClientImpl.makeUnaryRequest (/workspace/node_modules/@grpc/grpc-js/build/src/client.js:163:34)
+ -> /workspace/node_modules/@grpc/grpc-js/src/client.ts:328:30
+ at ServiceClientImpl. (/workspace/node_modules/@grpc/grpc-js/build/src/make-client.js:105:19)
+ -> /workspace/node_modules/@grpc/grpc-js/src/make-client.ts:189:15
+ at /workspace/build/src/v1/featurestore_service_client.js:1180:29
+ -> /workspace/src/v1/featurestore_service_client.ts:1488:25
+ at /workspace/node_modules/google-gax/build/src/normalCalls/timeout.js:44:16
+ -> /workspace/node_modules/google-gax/src/normalCalls/timeout.ts:54:13
+ at LongrunningApiCaller._wrapOperation (/workspace/node_modules/google-gax/build/src/longRunningCalls/longRunningApiCaller.js:55:16)
+ -> /workspace/node_modules/google-gax/src/longRunningCalls/longRunningApiCaller.ts:80:12
+ at /workspace/node_modules/google-gax/build/src/longRunningCalls/longRunningApiCaller.js:46:25
+ -> /workspace/node_modules/google-gax/src/longRunningCalls/longRunningApiCaller.ts:64:19
+ at OngoingCallPromise.call (/workspace/node_modules/google-gax/build/src/call.js:67:27)
+ -> /workspace/node_modules/google-gax/src/call.ts:81:23
+ at LongrunningApiCaller.call (/workspace/node_modules/google-gax/build/src/longRunningCalls/longRunningApiCaller.js:45:19)
+ -> /workspace/node_modules/google-gax/src/longRunningCalls/longRunningApiCaller.ts:63:15
+ at /workspace/node_modules/google-gax/build/src/createApiCall.js:84:30
+ -> /workspace/node_modules/google-gax/src/createApiCall.ts:118:26
",0,ai platform entity type api samples test after all hook should delete the created featurestore for should delete the created entity type failed note was also for this test but it was closed more than days ago so i didn t mark it flaky commit buildurl status failed test output permission denied permission denied consumer project undefined has been suspended error permission denied permission denied consumer project undefined has been suspended at object callerrorfromstatus workspace node modules grpc grpc js build src call js workspace node modules grpc grpc js src call ts at object onreceivestatus workspace node modules grpc grpc js build src client js workspace node modules grpc grpc js src client ts at object onreceivestatus workspace node modules grpc grpc js build src client interceptors js workspace node modules grpc grpc js src client interceptors ts at object onreceivestatus workspace node modules grpc grpc js build src client interceptors js workspace node modules grpc grpc js src client interceptors ts at workspace node modules grpc grpc js build src call stream js workspace node modules grpc grpc js src call stream ts at processticksandrejections internal process task queues js for call at at serviceclientimpl makeunaryrequest workspace node modules grpc grpc js build src client js workspace node modules grpc grpc js src client ts at serviceclientimpl workspace node modules grpc grpc js build src make client js workspace node modules grpc grpc js src make client ts at workspace build src featurestore service client js workspace src featurestore service client ts at workspace node modules google gax build src normalcalls timeout js workspace node modules google gax src normalcalls timeout ts at longrunningapicaller wrapoperation workspace node modules google gax build src longrunningcalls longrunningapicaller js workspace node modules google gax src longrunningcalls longrunningapicaller ts at workspace node modules google gax build src longrunningcalls longrunningapicaller js workspace node modules google gax src longrunningcalls longrunningapicaller ts at ongoingcallpromise call workspace node modules google gax build src call js workspace node modules google gax src call ts at longrunningapicaller call workspace node modules google gax build src longrunningcalls longrunningapicaller js workspace node modules google gax src longrunningcalls longrunningapicaller ts at workspace node modules google gax build src createapicall js workspace node modules google gax src createapicall ts ,0
+13910,8723317697.0,IssuesEvent,2018-12-09 20:45:06,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Visual Shader Editor Duplicate bug,bug topic:editor usability,"
+**Godot version:**
+Godot 3.1
+
+
+**Issue description:**
+Create a Visual shader , Create more then 1 node in the Shader .. Select a node and press CTRL + D to duplicate that node , it duplicate all the nodes not only the selected one
+
+
+",True,"Visual Shader Editor Duplicate bug -
+**Godot version:**
+Godot 3.1
+
+
+**Issue description:**
+Create a Visual shader , Create more then 1 node in the Shader .. Select a node and press CTRL + D to duplicate that node , it duplicate all the nodes not only the selected one
+
+
+",1,visual shader editor duplicate bug godot version godot issue description create a visual shader create more then node in the shader select a node and press ctrl d to duplicate that node it duplicate all the nodes not only the selected one ,1
+328665,24194346097.0,IssuesEvent,2022-09-23 21:19:47,hashicorp/terraform-provider-google,https://api.github.com/repos/hashicorp/terraform-provider-google,closed,Cloud SQL disk_size and disk_autoresize documentation is misleading,documentation,"
+
+### Community Note
+
+* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request.
+* Please do not leave _+1_ or _me too_ comments, they generate extra noise for issue followers and do not help prioritize the request.
+* If you are interested in working on this issue or have submitted a pull request, please leave a comment.
+* If an issue is assigned to the `modular-magician` user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to `hashibot`, a community member has claimed the issue already.
+
+
+
+### Description
+
+The documentation for `disk_size` and `disk_autoresize` in https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance#disk_size seem to indicate that they are mutually exclusive (`disk_size` - ""If you want to set this field, set disk_autoresize to false.""). However in GCP, it's possible to enable both on a Cloud SQL instance -
+
+
![]()
+
+
+
+### Affected Resource(s)
+
+
+
+* [google_sql_database_instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance#disk_size)
+
+",1.0,"Cloud SQL disk_size and disk_autoresize documentation is misleading -
+
+### Community Note
+
+* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request.
+* Please do not leave _+1_ or _me too_ comments, they generate extra noise for issue followers and do not help prioritize the request.
+* If you are interested in working on this issue or have submitted a pull request, please leave a comment.
+* If an issue is assigned to the `modular-magician` user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to `hashibot`, a community member has claimed the issue already.
+
+
+
+### Description
+
+The documentation for `disk_size` and `disk_autoresize` in https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance#disk_size seem to indicate that they are mutually exclusive (`disk_size` - ""If you want to set this field, set disk_autoresize to false.""). However in GCP, it's possible to enable both on a Cloud SQL instance -
+
+
![]()
+
+
+
+### Affected Resource(s)
+
+
+
+* [google_sql_database_instance](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/sql_database_instance#disk_size)
+
+",0,cloud sql disk size and disk autoresize documentation is misleading community note please vote on this issue by adding a 👍 to the original issue to help the community and maintainers prioritize this request please do not leave or me too comments they generate extra noise for issue followers and do not help prioritize the request if you are interested in working on this issue or have submitted a pull request please leave a comment if an issue is assigned to the modular magician user it is either in the process of being autogenerated or is planned to be autogenerated soon if an issue is assigned to a user that user is claiming responsibility for the issue if an issue is assigned to hashibot a community member has claimed the issue already description the documentation for disk size and disk autoresize in seem to indicate that they are mutually exclusive disk size if you want to set this field set disk autoresize to false however in gcp it s possible to enable both on a cloud sql instance img width alt screen shot at src affected resource s ,0
+22909,20598177945.0,IssuesEvent,2022-03-05 21:05:48,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Cannot see inspector,bug topic:editor usability,"### Godot version
+
+Godot Engine v4.0.alpha3.official.256069eaf
+
+### System information
+
+mac
+
+### Issue description
+
+
![]()
+Inspector is blocked by options of scene view
+
+### Steps to reproduce
+
+create label, click on it
+
+### Minimal reproduction project
+
+_No response_",True,"Cannot see inspector - ### Godot version
+
+Godot Engine v4.0.alpha3.official.256069eaf
+
+### System information
+
+mac
+
+### Issue description
+
+
![]()
+Inspector is blocked by options of scene view
+
+### Steps to reproduce
+
+create label, click on it
+
+### Minimal reproduction project
+
+_No response_",1,cannot see inspector godot version godot engine official system information mac issue description img width alt screen shot at pm src inspector is blocked by options of scene view steps to reproduce create label click on it minimal reproduction project no response ,1
+19701,14474932383.0,IssuesEvent,2020-12-10 00:24:27,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Script editor: CTRL+Click on extends with relative path provide Errors,bug topic:editor topic:gdscript usability,"
+**Godot version:**
+Godot 3.1 f148e8eed, platform=x11 bits=64 target=release_debug tools=yes
+
+**OS/device including version:**
+Xubuntu 16.04.5 LTS x64, 4.4.0-135-lowlatency
+
+**Issue description:**
+When ctrl+click on extends with relative path(extends ""base.gd""), Godot generate errors:
+```
+ERROR: _load: No loader found for resource: res://b
+ At: core/io/resource_loader.cpp:192.
+ERROR: _load: No loader found for resource: res://ba
+ At: core/io/resource_loader.cpp:192.
+ERROR: _load: No loader found for resource: res://base
+ At: core/io/resource_loader.cpp:192.
+```
+
+**Steps to reproduce:**
+Open attached project and ctrl+click on ""base.gd""
+
+
+
+**Minimal reproduction project:**
+[click_on_extends.zip](https://github.com/godotengine/godot/files/2393866/click_on_extends.zip)
+
+",True,"Script editor: CTRL+Click on extends with relative path provide Errors -
+**Godot version:**
+Godot 3.1 f148e8eed, platform=x11 bits=64 target=release_debug tools=yes
+
+**OS/device including version:**
+Xubuntu 16.04.5 LTS x64, 4.4.0-135-lowlatency
+
+**Issue description:**
+When ctrl+click on extends with relative path(extends ""base.gd""), Godot generate errors:
+```
+ERROR: _load: No loader found for resource: res://b
+ At: core/io/resource_loader.cpp:192.
+ERROR: _load: No loader found for resource: res://ba
+ At: core/io/resource_loader.cpp:192.
+ERROR: _load: No loader found for resource: res://base
+ At: core/io/resource_loader.cpp:192.
+```
+
+**Steps to reproduce:**
+Open attached project and ctrl+click on ""base.gd""
+
+
+
+**Minimal reproduction project:**
+[click_on_extends.zip](https://github.com/godotengine/godot/files/2393866/click_on_extends.zip)
+
+",1,script editor ctrl click on extends with relative path provide errors godot version godot platform bits target release debug tools yes os device including version xubuntu lts lowlatency issue description when ctrl click on extends with relative path extends base gd godot generate errors error load no loader found for resource res b at core io resource loader cpp error load no loader found for resource res ba at core io resource loader cpp error load no loader found for resource res base at core io resource loader cpp steps to reproduce open attached project and ctrl click on base gd minimal reproduction project ,1
+415460,12129703827.0,IssuesEvent,2020-04-22 23:19:03,dgraph-io/dgraph,https://api.github.com/repos/dgraph-io/dgraph,closed,Dgraph v20.03.0 Regexp Not returning expected results,area/querylang/function priority/P0 status/accepted,"## SUMMARY
+
+Using a query like `regexp(name@en, /.*alien.*/i))` returns back an empty set. This was discovered in the dgraph tour: https://dgraph.io/tour/search/3/#
+
+## ENVIRONMENT
+
+* Version: docker image `dgraph/dgraph:v20.03.0`
+* System: Docker Desktop v2.2.0.5 6GB running on host Mac OS 10.14.6
+
+## STEPS
+
+### STEP 1 - Env
+
+```bash
+docker-compose up -d
+```
+
+Compose File
+```yaml
+version: ""3.2""
+services:
+ zero:
+ image: dgraph/dgraph:${DGRAPH_VERSION}
+ volumes:
+ - /tmp/data:/dgraph
+ ports:
+ - 5080:5080
+ - 6080:6080
+ restart: on-failure
+ command: dgraph zero --my=zero:5080
+ alpha:
+ image: dgraph/dgraph:${DGRAPH_VERSION}
+ volumes:
+ - /tmp/data:/dgraph
+ ports:
+ - 8080:8080
+ - 9080:9080
+ restart: on-failure
+ command: dgraph alpha --my=alpha:7080 --lru_mb=2048 --zero=zero:5080
+ ratel:
+ image: dgraph/dgraph:${DGRAPH_VERSION}
+ ports:
+ - 8000:8000
+ command: dgraph-ratel
+```
+
+
+### STEP 2 - Schema
+
+Apply the Schema in:
+* https://dgraph.io/tour/moredata/1/
+* https://dgraph.io/tour/moredata/2/
+
+### STEP 3 - Load Data
+
+```bash
+wget ""https://github.com/dgraph-io/tutorial/blob/master/resources/1million.rdf.gz?raw=true"" -O 1million.rdf.gz -q
+docker cp ./1million.rdf.gz dgraph_zero_1:/tmp
+docker exec -it dgraph_zero_1 dgraph live -f /tmp/1million.rdf.gz --alpha alpha:9080 --zero zero:5080 -c 1
+```
+
+### STEP 3 - Indexes
+
+Apply Indexes from: https://dgraph.io/tour/search/1/
+
+```
+name: string @index(term, fulltext, trigram) @lang .
+```
+
+### STEP 4 - Run query
+
+From: https://dgraph.io/tour/search/3/#
+
+```
+{
+ aliens(func: regexp(name@en, /.*alien.*/i)) @cascade {
+ name@en
+ ~genre {
+ name@en
+ starring {
+ performance.actor @filter(regexp(name@en,
+ /(.*ali.*e.*n.*)|(.*a.*lie.*n.*)|(.*a.*l.*ien.*)/i)) {
+ name@en
+ }
+ }
+ }
+ }
+}
+```
+
+## EXPECTED BEHAVIOR
+
+```javascript
+{
+ ""data"": {
+ ""aliens"": [
+ {
+ ""name@en"": ""Alien Film"",
+ ""~genre"": [
+ {
+ ""name@en"": ""Mars Attacks!"",
+ ""starring"": [
+ {
+ ""performance.actor"": [
+ {
+ ""name@en"": ""Natalie Portman""
+ }
+ ]
+ }
+ ]
+ }
+ ]
+ }
+ ]
+ }
+/* ... */
+}
+```
+
+## ACTUAL BEHAVIOR
+
+```javascript
+{
+ ""data"": {
+ ""aliens"": []
+ }
+/* ... */
+}
+```
+## WORKAROUND
+
+I modified the query and this worked:
+
+```
+{
+ aliens(func: regexp(name@en, /.*ali.*e.*n.*/i)) @cascade {
+ name@en
+ ~genre {
+ name@en
+ starring {
+ performance.actor @filter(regexp(name@en,
+ /(.*ali.*e.*n.*)|(.*a.*lie.*n.*)|(.*a.*l.*ien.*)/i)) {
+ name@en
+ }
+ }
+ }
+ }
+}
+```
+",1.0,"Dgraph v20.03.0 Regexp Not returning expected results - ## SUMMARY
+
+Using a query like `regexp(name@en, /.*alien.*/i))` returns back an empty set. This was discovered in the dgraph tour: https://dgraph.io/tour/search/3/#
+
+## ENVIRONMENT
+
+* Version: docker image `dgraph/dgraph:v20.03.0`
+* System: Docker Desktop v2.2.0.5 6GB running on host Mac OS 10.14.6
+
+## STEPS
+
+### STEP 1 - Env
+
+```bash
+docker-compose up -d
+```
+
+Compose File
+```yaml
+version: ""3.2""
+services:
+ zero:
+ image: dgraph/dgraph:${DGRAPH_VERSION}
+ volumes:
+ - /tmp/data:/dgraph
+ ports:
+ - 5080:5080
+ - 6080:6080
+ restart: on-failure
+ command: dgraph zero --my=zero:5080
+ alpha:
+ image: dgraph/dgraph:${DGRAPH_VERSION}
+ volumes:
+ - /tmp/data:/dgraph
+ ports:
+ - 8080:8080
+ - 9080:9080
+ restart: on-failure
+ command: dgraph alpha --my=alpha:7080 --lru_mb=2048 --zero=zero:5080
+ ratel:
+ image: dgraph/dgraph:${DGRAPH_VERSION}
+ ports:
+ - 8000:8000
+ command: dgraph-ratel
+```
+
+
+### STEP 2 - Schema
+
+Apply the Schema in:
+* https://dgraph.io/tour/moredata/1/
+* https://dgraph.io/tour/moredata/2/
+
+### STEP 3 - Load Data
+
+```bash
+wget ""https://github.com/dgraph-io/tutorial/blob/master/resources/1million.rdf.gz?raw=true"" -O 1million.rdf.gz -q
+docker cp ./1million.rdf.gz dgraph_zero_1:/tmp
+docker exec -it dgraph_zero_1 dgraph live -f /tmp/1million.rdf.gz --alpha alpha:9080 --zero zero:5080 -c 1
+```
+
+### STEP 3 - Indexes
+
+Apply Indexes from: https://dgraph.io/tour/search/1/
+
+```
+name: string @index(term, fulltext, trigram) @lang .
+```
+
+### STEP 4 - Run query
+
+From: https://dgraph.io/tour/search/3/#
+
+```
+{
+ aliens(func: regexp(name@en, /.*alien.*/i)) @cascade {
+ name@en
+ ~genre {
+ name@en
+ starring {
+ performance.actor @filter(regexp(name@en,
+ /(.*ali.*e.*n.*)|(.*a.*lie.*n.*)|(.*a.*l.*ien.*)/i)) {
+ name@en
+ }
+ }
+ }
+ }
+}
+```
+
+## EXPECTED BEHAVIOR
+
+```javascript
+{
+ ""data"": {
+ ""aliens"": [
+ {
+ ""name@en"": ""Alien Film"",
+ ""~genre"": [
+ {
+ ""name@en"": ""Mars Attacks!"",
+ ""starring"": [
+ {
+ ""performance.actor"": [
+ {
+ ""name@en"": ""Natalie Portman""
+ }
+ ]
+ }
+ ]
+ }
+ ]
+ }
+ ]
+ }
+/* ... */
+}
+```
+
+## ACTUAL BEHAVIOR
+
+```javascript
+{
+ ""data"": {
+ ""aliens"": []
+ }
+/* ... */
+}
+```
+## WORKAROUND
+
+I modified the query and this worked:
+
+```
+{
+ aliens(func: regexp(name@en, /.*ali.*e.*n.*/i)) @cascade {
+ name@en
+ ~genre {
+ name@en
+ starring {
+ performance.actor @filter(regexp(name@en,
+ /(.*ali.*e.*n.*)|(.*a.*lie.*n.*)|(.*a.*l.*ien.*)/i)) {
+ name@en
+ }
+ }
+ }
+ }
+}
+```
+",0,dgraph regexp not returning expected results summary using a query like regexp name en alien i returns back an empty set this was discovered in the dgraph tour environment version docker image dgraph dgraph system docker desktop running on host mac os steps step env bash docker compose up d compose file yaml version services zero image dgraph dgraph dgraph version volumes tmp data dgraph ports restart on failure command dgraph zero my zero alpha image dgraph dgraph dgraph version volumes tmp data dgraph ports restart on failure command dgraph alpha my alpha lru mb zero zero ratel image dgraph dgraph dgraph version ports command dgraph ratel step schema apply the schema in step load data bash wget o rdf gz q docker cp rdf gz dgraph zero tmp docker exec it dgraph zero dgraph live f tmp rdf gz alpha alpha zero zero c step indexes apply indexes from name string index term fulltext trigram lang step run query from aliens func regexp name en alien i cascade name en genre name en starring performance actor filter regexp name en ali e n a lie n a l ien i name en expected behavior javascript data aliens name en alien film genre name en mars attacks starring performance actor name en natalie portman actual behavior javascript data aliens workaround i modified the query and this worked aliens func regexp name en ali e n i cascade name en genre name en starring performance actor filter regexp name en ali e n a lie n a l ien i name en ,0
+443875,12800893973.0,IssuesEvent,2020-07-02 18:00:35,elixir-cloud-aai/foca,https://api.github.com/repos/elixir-cloud-aai/foca,closed,Generalization of the errors module,priority: low workload: hours,"Generalize the current behavior of the `errors` [module](https://github.com/elixir-cloud-aai/foca/tree/dev/foca/errors) by passing an error model to FOCA's `register_error_handlers()` function and then pass that model to the different handlers. Also find a way to pass actual error parameters (like the exact error message) to a single handler which will match it to the model. Lastly write unit tests for the same. In this way, :
+- only need a single handler
+- can define the model in each service according to how it is defined in the specs
+- don't require the service developer to overwrite error handlers one by one",1.0,"Generalization of the errors module - Generalize the current behavior of the `errors` [module](https://github.com/elixir-cloud-aai/foca/tree/dev/foca/errors) by passing an error model to FOCA's `register_error_handlers()` function and then pass that model to the different handlers. Also find a way to pass actual error parameters (like the exact error message) to a single handler which will match it to the model. Lastly write unit tests for the same. In this way, :
+- only need a single handler
+- can define the model in each service according to how it is defined in the specs
+- don't require the service developer to overwrite error handlers one by one",0,generalization of the errors module generalize the current behavior of the errors by passing an error model to foca s register error handlers function and then pass that model to the different handlers also find a way to pass actual error parameters like the exact error message to a single handler which will match it to the model lastly write unit tests for the same in this way only need a single handler can define the model in each service according to how it is defined in the specs don t require the service developer to overwrite error handlers one by one,0
+4883,7494378420.0,IssuesEvent,2018-04-07 08:55:24,FoxDenStudio/FoxGuard-Sponge,https://api.github.com/repos/FoxDenStudio/FoxGuard-Sponge,closed,Immortal Pixelmon mob spawn,compatibility,"Apologies for the lack of information here at the moment - literal 4 minutes before I need to run to work - but just flagging this as it seems like a basic clash.
+
+ FoxGuard region set to deny mob spawns - works fine, no spawning of mobs - pixelmon or natural MC - after a few minutes idle time compared to a dozen or so before the limit was enabled.
+
+Pixelmon spawn grass triggers battles fine. Walking or idling in it initiates a fight - but no pokemon are released for this. Or at least no models are displayed. The GUI switches into the battle display and all works fine, but there is no KO, just the fighting continuing as if there was still HP to deplete.
+
+Unsure of whom to send this to, so gifting it to you both ^_^
+
+
+Pixelmon 2.1.4
+FG:0.20.5 Hotfix367
+SpongeAPI 5.2.0 snapshot - a3257a0
+SForge 2281-Beta 2274
+MForge 12.18.3.2281.",True,"Immortal Pixelmon mob spawn - Apologies for the lack of information here at the moment - literal 4 minutes before I need to run to work - but just flagging this as it seems like a basic clash.
+
+ FoxGuard region set to deny mob spawns - works fine, no spawning of mobs - pixelmon or natural MC - after a few minutes idle time compared to a dozen or so before the limit was enabled.
+
+Pixelmon spawn grass triggers battles fine. Walking or idling in it initiates a fight - but no pokemon are released for this. Or at least no models are displayed. The GUI switches into the battle display and all works fine, but there is no KO, just the fighting continuing as if there was still HP to deplete.
+
+Unsure of whom to send this to, so gifting it to you both ^_^
+
+
+Pixelmon 2.1.4
+FG:0.20.5 Hotfix367
+SpongeAPI 5.2.0 snapshot - a3257a0
+SForge 2281-Beta 2274
+MForge 12.18.3.2281.",0,immortal pixelmon mob spawn apologies for the lack of information here at the moment literal minutes before i need to run to work but just flagging this as it seems like a basic clash foxguard region set to deny mob spawns works fine no spawning of mobs pixelmon or natural mc after a few minutes idle time compared to a dozen or so before the limit was enabled pixelmon spawn grass triggers battles fine walking or idling in it initiates a fight but no pokemon are released for this or at least no models are displayed the gui switches into the battle display and all works fine but there is no ko just the fighting continuing as if there was still hp to deplete unsure of whom to send this to so gifting it to you both pixelmon fg spongeapi snapshot sforge beta mforge ,0
+73269,19618837467.0,IssuesEvent,2022-01-07 01:52:53,tensorflow/tensorflow,https://api.github.com/repos/tensorflow/tensorflow,closed,tensorflow removed numpy 1.20.3,type:build/install TF 2.5,"So I built tensorflow 2.5.0 successfully, but when I installed the wheel it removed my numpy 1.20.3 and downgraded it to 1.19.5 instead.
+
+Is this version pin necessary?",1.0,"tensorflow removed numpy 1.20.3 - So I built tensorflow 2.5.0 successfully, but when I installed the wheel it removed my numpy 1.20.3 and downgraded it to 1.19.5 instead.
+
+Is this version pin necessary?",0,tensorflow removed numpy so i built tensorflow successfully but when i installed the wheel it removed my numpy and downgraded it to instead is this version pin necessary ,0
+17987,12466527090.0,IssuesEvent,2020-05-28 15:36:35,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Physics material name,feature proposal topic:editor topic:physics usability,"**Godot version:**
+Godot 3.1
+
+**Issue description:**
+in Physic material there is Friction , Rough , Bounce and Absorbent , but if you add Name for Example to define what type of this Physic material , for example is it Glass ? is it Metal ? or is it Concrete ? adding this variable will make it very easy to define what surface of that object
+this will make it very very easy to make Foot steps sounds maybe ?
+or bullets impacts on objects ?
+
+i know there is other ways to do this , but this way is the easier one , like Unreal Engine 4
+
+
+
+",True,"Physics material name - **Godot version:**
+Godot 3.1
+
+**Issue description:**
+in Physic material there is Friction , Rough , Bounce and Absorbent , but if you add Name for Example to define what type of this Physic material , for example is it Glass ? is it Metal ? or is it Concrete ? adding this variable will make it very easy to define what surface of that object
+this will make it very very easy to make Foot steps sounds maybe ?
+or bullets impacts on objects ?
+
+i know there is other ways to do this , but this way is the easier one , like Unreal Engine 4
+
+
+
+",1,physics material name godot version godot issue description in physic material there is friction rough bounce and absorbent but if you add name for example to define what type of this physic material for example is it glass is it metal or is it concrete adding this variable will make it very easy to define what surface of that object this will make it very very easy to make foot steps sounds maybe or bullets impacts on objects i know there is other ways to do this but this way is the easier one like unreal engine ,1
+139054,18836175744.0,IssuesEvent,2021-11-11 01:20:48,turkdevops/vue-cli,https://api.github.com/repos/turkdevops/vue-cli,opened,CVE-2021-41249 (Medium) detected in apollo-server-core-2.4.8.tgz,security vulnerability,"## CVE-2021-41249 - Medium Severity Vulnerability
+
Vulnerable Library - apollo-server-core-2.4.8.tgz
+
+Core engine for Apollo GraphQL server
+Library home page: https://registry.npmjs.org/apollo-server-core/-/apollo-server-core-2.4.8.tgz
+Path to dependency file: vue-cli/package.json
+Path to vulnerable library: vue-cli/node_modules/apollo-server-core
+
+
+Dependency Hierarchy:
+ - cli-ui-4.0.0-alpha.0.tgz (Root Library)
+ - vue-cli-plugin-apollo-0.19.2.tgz
+ - apollo-server-express-2.4.8.tgz
+ - :x: **apollo-server-core-2.4.8.tgz** (Vulnerable Library)
+
Found in base branch: fix-babel-core-js
+
+
+
+
Vulnerability Details
+
+
+GraphQL Playground is a GraphQL IDE for development of graphQL focused applications. All versions of graphql-playground-react older than graphql-playground-react@1.7.28 are vulnerable to compromised HTTP schema introspection responses or schema prop values with malicious GraphQL type names, exposing a dynamic XSS attack surface that can allow code injection on operation autocomplete. In order for the attack to take place, the user must load a malicious schema in graphql-playground. There are several ways this can occur, including by specifying the URL to a malicious schema in the endpoint query parameter. If a user clicks on a link to a GraphQL Playground installation that specifies a malicious server, arbitrary JavaScript can run in the user's browser, which can be used to exfiltrate user credentials or other harmful goals. If you are using graphql-playground-react directly in your client app, upgrade to version 1.7.28 or later.
+
+
Publish Date: 2021-11-04
+
URL: CVE-2021-41249
+
+
+
+
CVSS 3 Score Details (4.7)
+
+
+Base Score Metrics:
+- Exploitability Metrics:
+ - Attack Vector: Network
+ - Attack Complexity: High
+ - Privileges Required: None
+ - User Interaction: Required
+ - Scope: Changed
+- Impact Metrics:
+ - Confidentiality Impact: Low
+ - Integrity Impact: Low
+ - Availability Impact: None
+
+For more information on CVSS3 Scores, click here.
+
+
+
+
Suggested Fix
+
+
+
Type: Upgrade version
+Origin: https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7,https://github.com/apollographql/apollo-server/security/advisories/GHSA-qm7x-rc44-rrqw
+Release Date: 2021-11-04
+Fix Resolution: graphql-playground-react - 1.7.28, apollo-server - 2.25.3,3.4.1; apollo-server-core - 2.25.3,3.4.1
+
+
+
+
+
+***
+Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2021-41249 (Medium) detected in apollo-server-core-2.4.8.tgz - ## CVE-2021-41249 - Medium Severity Vulnerability
+
Vulnerable Library - apollo-server-core-2.4.8.tgz
+
+Core engine for Apollo GraphQL server
+Library home page: https://registry.npmjs.org/apollo-server-core/-/apollo-server-core-2.4.8.tgz
+Path to dependency file: vue-cli/package.json
+Path to vulnerable library: vue-cli/node_modules/apollo-server-core
+
+
+Dependency Hierarchy:
+ - cli-ui-4.0.0-alpha.0.tgz (Root Library)
+ - vue-cli-plugin-apollo-0.19.2.tgz
+ - apollo-server-express-2.4.8.tgz
+ - :x: **apollo-server-core-2.4.8.tgz** (Vulnerable Library)
+
Found in base branch: fix-babel-core-js
+
+
+
+
Vulnerability Details
+
+
+GraphQL Playground is a GraphQL IDE for development of graphQL focused applications. All versions of graphql-playground-react older than graphql-playground-react@1.7.28 are vulnerable to compromised HTTP schema introspection responses or schema prop values with malicious GraphQL type names, exposing a dynamic XSS attack surface that can allow code injection on operation autocomplete. In order for the attack to take place, the user must load a malicious schema in graphql-playground. There are several ways this can occur, including by specifying the URL to a malicious schema in the endpoint query parameter. If a user clicks on a link to a GraphQL Playground installation that specifies a malicious server, arbitrary JavaScript can run in the user's browser, which can be used to exfiltrate user credentials or other harmful goals. If you are using graphql-playground-react directly in your client app, upgrade to version 1.7.28 or later.
+
+
Publish Date: 2021-11-04
+
URL: CVE-2021-41249
+
+
+
+
CVSS 3 Score Details (4.7)
+
+
+Base Score Metrics:
+- Exploitability Metrics:
+ - Attack Vector: Network
+ - Attack Complexity: High
+ - Privileges Required: None
+ - User Interaction: Required
+ - Scope: Changed
+- Impact Metrics:
+ - Confidentiality Impact: Low
+ - Integrity Impact: Low
+ - Availability Impact: None
+
+For more information on CVSS3 Scores, click here.
+
+
+
+
Suggested Fix
+
+
+
Type: Upgrade version
+Origin: https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7,https://github.com/apollographql/apollo-server/security/advisories/GHSA-qm7x-rc44-rrqw
+Release Date: 2021-11-04
+Fix Resolution: graphql-playground-react - 1.7.28, apollo-server - 2.25.3,3.4.1; apollo-server-core - 2.25.3,3.4.1
+
+
+
+
+
+***
+Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve medium detected in apollo server core tgz cve medium severity vulnerability vulnerable library apollo server core tgz core engine for apollo graphql server library home page a href path to dependency file vue cli package json path to vulnerable library vue cli node modules apollo server core dependency hierarchy cli ui alpha tgz root library vue cli plugin apollo tgz apollo server express tgz x apollo server core tgz vulnerable library found in base branch fix babel core js vulnerability details graphql playground is a graphql ide for development of graphql focused applications all versions of graphql playground react older than graphql playground react are vulnerable to compromised http schema introspection responses or schema prop values with malicious graphql type names exposing a dynamic xss attack surface that can allow code injection on operation autocomplete in order for the attack to take place the user must load a malicious schema in graphql playground there are several ways this can occur including by specifying the url to a malicious schema in the endpoint query parameter if a user clicks on a link to a graphql playground installation that specifies a malicious server arbitrary javascript can run in the user s browser which can be used to exfiltrate user credentials or other harmful goals if you are using graphql playground react directly in your client app upgrade to version or later publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction required scope 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 graphql playground react apollo server apollo server core step up your open source security game with whitesource ,0
+122247,16095960448.0,IssuesEvent,2021-04-26 23:47:53,opengovsg/FormSG,https://api.github.com/repos/opengovsg/FormSG,opened,Competitive research for Date field validations,P2 design,"- [prioritize first] Exclude choice of: Mon, Tue, Wed, Thu, Fri, Sat, Sun, Public Holidays
+- Start Date and End Date
+- Any other validations? ",1.0,"Competitive research for Date field validations - - [prioritize first] Exclude choice of: Mon, Tue, Wed, Thu, Fri, Sat, Sun, Public Holidays
+- Start Date and End Date
+- Any other validations? ",0,competitive research for date field validations exclude choice of mon tue wed thu fri sat sun public holidays start date and end date any other validations ,0
+62720,7626168635.0,IssuesEvent,2018-05-04 01:30:21,dotnet/roslyn,https://api.github.com/repos/dotnet/roslyn,closed,C# Compiler is not consistent with the CLR for the underlying representation of bool,Area-Compilers Area-Language Design Documentation Feature Request,"### Issue
+
+Today the C# compiler does not emit code handling for `bool` that is consistent with the underlying representation of `bool` in the CLR.
+
+The C# specification states:
+> The bool type represents boolean logical quantities. The possible values of type bool are true and false.
+
+The spec also indicates that it is 1-byte. Specifically that the result of the `sizeof(bool)` expression is `1`.
+
+While the ECMA 335 specification states:
+> A CLI Boolean type occupies 1 byte in memory. A bit pattern of all zeroes denotes a value of
+false. A bit pattern with any one or more bits set (analogous to a non-zero integer) denotes a
+value of true. For the purpose of stack operations boolean values are treated as unsigned 1-byte
+integers (§III.1.1.1).
+
+This can lead to confusion about the handling and cause various inconsistencies in various edge cases (see https://github.com/dotnet/coreclr/pull/16138#discussion_r165256495, for such a thread).
+
+### Proposal
+
+It would be good to determine:
+* Should the spec be updated?
+ * The spec would explicitly list the expected values of `true`/`false` so that two implementations don't behave differently
+* Can the compiler be updated?
+ * Given that we are emitting for the CLR, we would make our handling match the expected representations for the two boolean values (`0`/`not 0`) of the underlying platform
+
+### Current Behavior
+
+The majority of the behaviors below actually match the CLR expectation that a `bool` can be more than just `0` or `1`. However some of the behaviors (such as `&&`) does not match this expectation and can cause issues when interoping with any code that would assume otherwise (generally this is some kind of interop or unsafe code).
+
+* `!value`
+```asm
+ldarg.1
+ldc.i4.0
+ceq
+```
+* `left == right`
+```asm
+ldarg.1
+ldarg.2
+ceq
+```
+* `left != right`
+```asm
+ldarg.1
+ldarg.2
+ceq
+ldc.i4.0
+ceq
+```
+* `left & right`
+```asm
+ldarg.1
+ldarg.2
+and
+```
+* `left | right`
+```asm
+ldarg.1
+ldarg.2
+or
+```
+* `left ^ right`
+```asm
+ldarg.1
+ldarg.2
+xor
+```
+* `left && right`
+```asm
+ldarg.1
+ldarg.2
+and
+```
+* `left || right`
+```asm
+ldarg.1
+ldarg.2
+or
+```
+* `value ? ""true"" : ""false""`
+```asm
+ldarg.1
+brtrue.s
+```",1.0,"C# Compiler is not consistent with the CLR for the underlying representation of bool - ### Issue
+
+Today the C# compiler does not emit code handling for `bool` that is consistent with the underlying representation of `bool` in the CLR.
+
+The C# specification states:
+> The bool type represents boolean logical quantities. The possible values of type bool are true and false.
+
+The spec also indicates that it is 1-byte. Specifically that the result of the `sizeof(bool)` expression is `1`.
+
+While the ECMA 335 specification states:
+> A CLI Boolean type occupies 1 byte in memory. A bit pattern of all zeroes denotes a value of
+false. A bit pattern with any one or more bits set (analogous to a non-zero integer) denotes a
+value of true. For the purpose of stack operations boolean values are treated as unsigned 1-byte
+integers (§III.1.1.1).
+
+This can lead to confusion about the handling and cause various inconsistencies in various edge cases (see https://github.com/dotnet/coreclr/pull/16138#discussion_r165256495, for such a thread).
+
+### Proposal
+
+It would be good to determine:
+* Should the spec be updated?
+ * The spec would explicitly list the expected values of `true`/`false` so that two implementations don't behave differently
+* Can the compiler be updated?
+ * Given that we are emitting for the CLR, we would make our handling match the expected representations for the two boolean values (`0`/`not 0`) of the underlying platform
+
+### Current Behavior
+
+The majority of the behaviors below actually match the CLR expectation that a `bool` can be more than just `0` or `1`. However some of the behaviors (such as `&&`) does not match this expectation and can cause issues when interoping with any code that would assume otherwise (generally this is some kind of interop or unsafe code).
+
+* `!value`
+```asm
+ldarg.1
+ldc.i4.0
+ceq
+```
+* `left == right`
+```asm
+ldarg.1
+ldarg.2
+ceq
+```
+* `left != right`
+```asm
+ldarg.1
+ldarg.2
+ceq
+ldc.i4.0
+ceq
+```
+* `left & right`
+```asm
+ldarg.1
+ldarg.2
+and
+```
+* `left | right`
+```asm
+ldarg.1
+ldarg.2
+or
+```
+* `left ^ right`
+```asm
+ldarg.1
+ldarg.2
+xor
+```
+* `left && right`
+```asm
+ldarg.1
+ldarg.2
+and
+```
+* `left || right`
+```asm
+ldarg.1
+ldarg.2
+or
+```
+* `value ? ""true"" : ""false""`
+```asm
+ldarg.1
+brtrue.s
+```",0,c compiler is not consistent with the clr for the underlying representation of bool issue today the c compiler does not emit code handling for bool that is consistent with the underlying representation of bool in the clr the c specification states the bool type represents boolean logical quantities the possible values of type bool are true and false the spec also indicates that it is byte specifically that the result of the sizeof bool expression is while the ecma specification states a cli boolean type occupies byte in memory a bit pattern of all zeroes denotes a value of false a bit pattern with any one or more bits set analogous to a non zero integer denotes a value of true for the purpose of stack operations boolean values are treated as unsigned byte integers §iii this can lead to confusion about the handling and cause various inconsistencies in various edge cases see for such a thread proposal it would be good to determine should the spec be updated the spec would explicitly list the expected values of true false so that two implementations don t behave differently can the compiler be updated given that we are emitting for the clr we would make our handling match the expected representations for the two boolean values not of the underlying platform current behavior the majority of the behaviors below actually match the clr expectation that a bool can be more than just or however some of the behaviors such as does not match this expectation and can cause issues when interoping with any code that would assume otherwise generally this is some kind of interop or unsafe code value asm ldarg ldc ceq left right asm ldarg ldarg ceq left right asm ldarg ldarg ceq ldc ceq left right asm ldarg ldarg and left right asm ldarg ldarg or left right asm ldarg ldarg xor left right asm ldarg ldarg and left right asm ldarg ldarg or value true false asm ldarg brtrue s ,0
+7798,5215812307.0,IssuesEvent,2017-01-26 07:42:21,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Remove Warning message when creating a new track in Animation window,enhancement junior job topic:editor usability,"In my opinion there's no reason why you would give a warning message every time you want to create a new track in your animation. As a graphics guy doing a lot of animations this warning message becomes really annoying. It's like asking in Photoshop ""if you really want to create a new layer.""
+
+If you accidentally hit the wrong key button when setting a keyframe, then you can easily remove the track from the animation, so it's hard to see the need for the warning message. ",True,"Remove Warning message when creating a new track in Animation window - In my opinion there's no reason why you would give a warning message every time you want to create a new track in your animation. As a graphics guy doing a lot of animations this warning message becomes really annoying. It's like asking in Photoshop ""if you really want to create a new layer.""
+
+If you accidentally hit the wrong key button when setting a keyframe, then you can easily remove the track from the animation, so it's hard to see the need for the warning message. ",1,remove warning message when creating a new track in animation window in my opinion there s no reason why you would give a warning message every time you want to create a new track in your animation as a graphics guy doing a lot of animations this warning message becomes really annoying it s like asking in photoshop if you really want to create a new layer if you accidentally hit the wrong key button when setting a keyframe then you can easily remove the track from the animation so it s hard to see the need for the warning message ,1
+18284,12733352172.0,IssuesEvent,2020-06-25 12:09:05,godotengine/godot,https://api.github.com/repos/godotengine/godot,opened,Child 2D gizmo does not update with animation,bug topic:editor usability,"
+
+**Godot version:**
+
+3.2.2 rc2
+
+**Issue description:**
+
+
+Notice the Node2D gizmo staying in place until you move cursor over viewport (which focuses the viewport and updates the gizmo only once).
+
+**Minimal reproduction project:**
+
+[ReproductionProject.zip](https://github.com/godotengine/godot/files/4831075/ReproductionProject.zip)
+",True,"Child 2D gizmo does not update with animation -
+
+**Godot version:**
+
+3.2.2 rc2
+
+**Issue description:**
+
+
+Notice the Node2D gizmo staying in place until you move cursor over viewport (which focuses the viewport and updates the gizmo only once).
+
+**Minimal reproduction project:**
+
+[ReproductionProject.zip](https://github.com/godotengine/godot/files/4831075/ReproductionProject.zip)
+",1,child gizmo does not update with animation please search existing issues for potential duplicates before filing yours godot version issue description notice the gizmo staying in place until you move cursor over viewport which focuses the viewport and updates the gizmo only once minimal reproduction project ,1
+17301,11873449381.0,IssuesEvent,2020-03-26 17:19:34,godotengine/godot,https://api.github.com/repos/godotengine/godot,opened,Windows always appear on first screen,bug topic:editor usability,"**Godot version:**
+5f1107aa3
+
+**OS/device including version:**
+Windows 10
+
+**Issue description:**
+Any new Window will appear on the first screen (monitor). IMO they should appear on the same screen as parent Window.
+
+**Steps to reproduce:**
+1. Open Godot editor
+2. Move it to second screen
+3. Add node
+4. Dialog appears on another screen :/",True,"Windows always appear on first screen - **Godot version:**
+5f1107aa3
+
+**OS/device including version:**
+Windows 10
+
+**Issue description:**
+Any new Window will appear on the first screen (monitor). IMO they should appear on the same screen as parent Window.
+
+**Steps to reproduce:**
+1. Open Godot editor
+2. Move it to second screen
+3. Add node
+4. Dialog appears on another screen :/",1,windows always appear on first screen godot version os device including version windows issue description any new window will appear on the first screen monitor imo they should appear on the same screen as parent window steps to reproduce open godot editor move it to second screen add node dialog appears on another screen ,1
+735171,25381995648.0,IssuesEvent,2022-11-21 18:20:41,status-im/status-desktop,https://api.github.com/repos/status-im/status-desktop,opened,Implement new delete message backend workflow,priority 2: medium E:Communities S:3,"Delete message had a breaking change on status-go, where the deleted message is no longer permanently deleted. https://github.com/status-im/status-go/pull/2922
+
+For now, we need to deal with int so that on a restart, we no longer see those deleted messages.
+
+We will do the front-end later where we let the user undo the deletion (probably part of https://github.com/status-im/status-desktop/issues/7632)",1.0,"Implement new delete message backend workflow - Delete message had a breaking change on status-go, where the deleted message is no longer permanently deleted. https://github.com/status-im/status-go/pull/2922
+
+For now, we need to deal with int so that on a restart, we no longer see those deleted messages.
+
+We will do the front-end later where we let the user undo the deletion (probably part of https://github.com/status-im/status-desktop/issues/7632)",0,implement new delete message backend workflow delete message had a breaking change on status go where the deleted message is no longer permanently deleted for now we need to deal with int so that on a restart we no longer see those deleted messages we will do the front end later where we let the user undo the deletion probably part of ,0
+267413,8388557166.0,IssuesEvent,2018-10-09 06:52:03,AnSyn/ansyn,https://api.github.com/repos/AnSyn/ansyn,closed,Bug- remove overlay from case and next/prev overlays,Bug Priority: High,"After an overlay is removed from the case (the previous overlay should be shown)
+and the navigation to next/prev overlay should be as always (from the active overlay).
+The current behavior- after an overlay is removed, there is no previous overlay- the navigation (next/prev) begins from the first overlay in the time line (regardless of when the removed overlay was). ",1.0,"Bug- remove overlay from case and next/prev overlays - After an overlay is removed from the case (the previous overlay should be shown)
+and the navigation to next/prev overlay should be as always (from the active overlay).
+The current behavior- after an overlay is removed, there is no previous overlay- the navigation (next/prev) begins from the first overlay in the time line (regardless of when the removed overlay was). ",0,bug remove overlay from case and next prev overlays after an overlay is removed from the case the previous overlay should be shown and the navigation to next prev overlay should be as always from the active overlay the current behavior after an overlay is removed there is no previous overlay the navigation next prev begins from the first overlay in the time line regardless of when the removed overlay was ,0
+90532,8247526074.0,IssuesEvent,2018-09-11 15:46:14,mozilla/iris,https://api.github.com/repos/mozilla/iris,opened,Fix web_developer_menu test case,test case,toolbars_window_controls/web_developer_menu consistently fails for me on all platforms. Please investigate and fix this test case failure.,1.0,Fix web_developer_menu test case - toolbars_window_controls/web_developer_menu consistently fails for me on all platforms. Please investigate and fix this test case failure.,0,fix web developer menu test case toolbars window controls web developer menu consistently fails for me on all platforms please investigate and fix this test case failure ,0
+72652,19401694451.0,IssuesEvent,2021-12-19 09:48:19,guardianproject/tor-android,https://api.github.com/repos/guardianproject/tor-android,closed,some build paths are still included in the binaries,help wanted reproducible builds,"When build paths are included in the binaries, reproducible builds requires a specific setup where all of the paths are the same. We do not need to have any build paths in the binaries, they should be removed whenever possible. Here are some example fixes:
+
+* c13c781dc1f8f4030fe284b886f25380a4f1fc50
+* 6ecaaf98fa8d55217d9ff2c924cd690dca2f956e
+
+This example _diffoscope_ output shows a number of build paths:
+[build-paths-example-diff.zip](https://github.com/guardianproject/tor-android/files/6700487/build-paths-example-diff.zip)
+
+These are the build paths that I know that still need fixing:
+
+### Android NDK
+
+
+### tor default config paths
+
+",1.0,"some build paths are still included in the binaries - When build paths are included in the binaries, reproducible builds requires a specific setup where all of the paths are the same. We do not need to have any build paths in the binaries, they should be removed whenever possible. Here are some example fixes:
+
+* c13c781dc1f8f4030fe284b886f25380a4f1fc50
+* 6ecaaf98fa8d55217d9ff2c924cd690dca2f956e
+
+This example _diffoscope_ output shows a number of build paths:
+[build-paths-example-diff.zip](https://github.com/guardianproject/tor-android/files/6700487/build-paths-example-diff.zip)
+
+These are the build paths that I know that still need fixing:
+
+### Android NDK
+
+
+### tor default config paths
+
+",0,some build paths are still included in the binaries when build paths are included in the binaries reproducible builds requires a specific setup where all of the paths are the same we do not need to have any build paths in the binaries they should be removed whenever possible here are some example fixes this example diffoscope output shows a number of build paths these are the build paths that i know that still need fixing android ndk tor default config paths ,0
+69363,9300792896.0,IssuesEvent,2019-03-23 16:36:35,brightcove/brine,https://api.github.com/repos/brightcove/brine,closed,Make header selection more obvious in docs,documentation,the |response_attribute| substitution doesn't seem to be working in the step reference and there' snot much information elsewhere.,1.0,Make header selection more obvious in docs - the |response_attribute| substitution doesn't seem to be working in the step reference and there' snot much information elsewhere.,0,make header selection more obvious in docs the response attribute substitution doesn t seem to be working in the step reference and there snot much information elsewhere ,0
+26757,27163372025.0,IssuesEvent,2023-02-17 13:41:15,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,"3-to-4 conversion renames all ""remove"" functions",enhancement topic:editor usability,"### Godot version
+
+v4.0.rc1.official [8843d9ad3]
+
+### System information
+
+Steam OS Holo, Steam Deck
+
+### Issue description
+
+The conversion rule renaming `remove` to `remove_at` for `Array` objects is applied to all functions named `remove`.
+
+### Steps to reproduce
+
+Create a 3.0 project with a function called ""remove"" in any script:
+```gdscript
+extends Node
+
+func remove():
+ pass
+```
+
+After converting to 4.0, the function will be called ""remove_at"":
+```gdscript
+extends Node
+
+func remove_at():
+ pass
+```
+
+### Minimal reproduction project
+
+N/A",True,"3-to-4 conversion renames all ""remove"" functions - ### Godot version
+
+v4.0.rc1.official [8843d9ad3]
+
+### System information
+
+Steam OS Holo, Steam Deck
+
+### Issue description
+
+The conversion rule renaming `remove` to `remove_at` for `Array` objects is applied to all functions named `remove`.
+
+### Steps to reproduce
+
+Create a 3.0 project with a function called ""remove"" in any script:
+```gdscript
+extends Node
+
+func remove():
+ pass
+```
+
+After converting to 4.0, the function will be called ""remove_at"":
+```gdscript
+extends Node
+
+func remove_at():
+ pass
+```
+
+### Minimal reproduction project
+
+N/A",1, to conversion renames all remove functions godot version official system information steam os holo steam deck issue description the conversion rule renaming remove to remove at for array objects is applied to all functions named remove steps to reproduce create a project with a function called remove in any script gdscript extends node func remove pass after converting to the function will be called remove at gdscript extends node func remove at pass minimal reproduction project n a,1
+117,2496986379.0,IssuesEvent,2015-01-06 23:58:25,syl20bnr/spacemacs,https://api.github.com/repos/syl20bnr/spacemacs,closed,error: The directory `~/.emacs.d/server' is unsafe,documentation :-> question,"On a fresh install of spacemacs, emacs `GNU Emacs 25.0.50.1 (x86_64-w64-mingw32) of 2014-10-08 on G75VW` reports:
+
+```
+Warning (initialization): An error occurred while loading `c:/Users/jkeyes/.emacs.d/init.el':
+
+error: The directory `~/.emacs.d/server' is unsafe
+
+To ensure normal operation, you should investigate and remove the
+cause of the error in your initialization file. Start Emacs with
+the `--debug-init' option to view a complete error backtrace.
+```
+
+",1.0,"error: The directory `~/.emacs.d/server' is unsafe - On a fresh install of spacemacs, emacs `GNU Emacs 25.0.50.1 (x86_64-w64-mingw32) of 2014-10-08 on G75VW` reports:
+
+```
+Warning (initialization): An error occurred while loading `c:/Users/jkeyes/.emacs.d/init.el':
+
+error: The directory `~/.emacs.d/server' is unsafe
+
+To ensure normal operation, you should investigate and remove the
+cause of the error in your initialization file. Start Emacs with
+the `--debug-init' option to view a complete error backtrace.
+```
+
+",0,error the directory emacs d server is unsafe on a fresh install of spacemacs emacs gnu emacs of on reports warning initialization an error occurred while loading c users jkeyes emacs d init el error the directory emacs d server is unsafe to ensure normal operation you should investigate and remove the cause of the error in your initialization file start emacs with the debug init option to view a complete error backtrace ,0
+86088,8020084312.0,IssuesEvent,2018-07-26 02:40:30,MetaMask/metamask-extension,https://api.github.com/repos/MetaMask/metamask-extension,closed,Write unit tests for the confirm-detail-row.component.js,L03.1-newUI/UAT L06-testing,"`metamask-extension/ui/app/components/confirm-page-container/confirm-detail-row/confirm-detail-row.component.js` needs unit tests.
+
+Use `metamask-extension/ui/app/components/send/send-content/send-row-wrapper/send-row-wrapper.component.js` and `metamask-extension/ui/app/components/send/send-content/send-row-wrapper/tests/send-row-wrapper-component.test.js` as an example to follow.
+
+Tests to include:
+- check that the outer div renders (get the div by its classname)
+- separate unit tests to check that each of `label`, `headerText`, `fiatText` and `ethText` rendered correctly and within the expected divs
+- check that the passed `fiatTextColor` gets set on the expected div
+- check that the `className` of the div that includes the `confirm-detail-row__header-text` class is as expected
+- check that `onHeaderClick()` gets called when `headerText` div gets clicked
+
+documentation that might be helpful:
+- http://airbnb.io/enzyme/
+- https://github.com/JedWatson/classnames
+
+",1.0,"Write unit tests for the confirm-detail-row.component.js - `metamask-extension/ui/app/components/confirm-page-container/confirm-detail-row/confirm-detail-row.component.js` needs unit tests.
+
+Use `metamask-extension/ui/app/components/send/send-content/send-row-wrapper/send-row-wrapper.component.js` and `metamask-extension/ui/app/components/send/send-content/send-row-wrapper/tests/send-row-wrapper-component.test.js` as an example to follow.
+
+Tests to include:
+- check that the outer div renders (get the div by its classname)
+- separate unit tests to check that each of `label`, `headerText`, `fiatText` and `ethText` rendered correctly and within the expected divs
+- check that the passed `fiatTextColor` gets set on the expected div
+- check that the `className` of the div that includes the `confirm-detail-row__header-text` class is as expected
+- check that `onHeaderClick()` gets called when `headerText` div gets clicked
+
+documentation that might be helpful:
+- http://airbnb.io/enzyme/
+- https://github.com/JedWatson/classnames
+
+",0,write unit tests for the confirm detail row component js metamask extension ui app components confirm page container confirm detail row confirm detail row component js needs unit tests use metamask extension ui app components send send content send row wrapper send row wrapper component js and metamask extension ui app components send send content send row wrapper tests send row wrapper component test js as an example to follow tests to include check that the outer div renders get the div by its classname separate unit tests to check that each of label headertext fiattext and ethtext rendered correctly and within the expected divs check that the passed fiattextcolor gets set on the expected div check that the classname of the div that includes the confirm detail row header text class is as expected check that onheaderclick gets called when headertext div gets clicked documentation that might be helpful ,0
+315432,27073070486.0,IssuesEvent,2023-02-14 08:39:37,keycloak/keycloak,https://api.github.com/repos/keycloak/keycloak,opened,Flaky test: org.keycloak.testsuite.model.UserSessionProviderTest#testRestartSession,kind/bug area/ci flaky-test,"## org.keycloak.testsuite.model.UserSessionProviderTest#testRestartSession
+[Keycloak CI - Base IT (6)](https://github.com/keycloak/keycloak/actions/runs/4146413917/jobs/7172154915) / [Pull Request #16876](https://github.com/keycloak/keycloak/pull/16876)
+
+```
+java.lang.AssertionError
+ at org.junit.Assert.fail(Assert.java:87)
+ at org.junit.Assert.assertTrue(Assert.java:42)
+ at org.junit.Assert.assertTrue(Assert.java:53)
+ at org.keycloak.testsuite.model.UserSessionProviderTest.assertSession(UserSessionProviderTest.java:844)
+...
+```
+
+```
+java.lang.AssertionError
+ at org.junit.Assert.fail(Assert.java:87)
+ at org.junit.Assert.assertTrue(Assert.java:42)
+ at org.junit.Assert.assertTrue(Assert.java:53)
+ at org.keycloak.testsuite.model.UserSessionProviderTest.assertSession(UserSessionProviderTest.java:844)
+...
+```
+",1.0,"Flaky test: org.keycloak.testsuite.model.UserSessionProviderTest#testRestartSession - ## org.keycloak.testsuite.model.UserSessionProviderTest#testRestartSession
+[Keycloak CI - Base IT (6)](https://github.com/keycloak/keycloak/actions/runs/4146413917/jobs/7172154915) / [Pull Request #16876](https://github.com/keycloak/keycloak/pull/16876)
+
+```
+java.lang.AssertionError
+ at org.junit.Assert.fail(Assert.java:87)
+ at org.junit.Assert.assertTrue(Assert.java:42)
+ at org.junit.Assert.assertTrue(Assert.java:53)
+ at org.keycloak.testsuite.model.UserSessionProviderTest.assertSession(UserSessionProviderTest.java:844)
+...
+```
+
+```
+java.lang.AssertionError
+ at org.junit.Assert.fail(Assert.java:87)
+ at org.junit.Assert.assertTrue(Assert.java:42)
+ at org.junit.Assert.assertTrue(Assert.java:53)
+ at org.keycloak.testsuite.model.UserSessionProviderTest.assertSession(UserSessionProviderTest.java:844)
+...
+```
+",0,flaky test org keycloak testsuite model usersessionprovidertest testrestartsession org keycloak testsuite model usersessionprovidertest testrestartsession java lang assertionerror at org junit assert fail assert java at org junit assert asserttrue assert java at org junit assert asserttrue assert java at org keycloak testsuite model usersessionprovidertest assertsession usersessionprovidertest java java lang assertionerror at org junit assert fail assert java at org junit assert asserttrue assert java at org junit assert asserttrue assert java at org keycloak testsuite model usersessionprovidertest assertsession usersessionprovidertest java ,0
+18834,13285066780.0,IssuesEvent,2020-08-24 07:28:46,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Autocompletion triggers on numbers,bug regression topic:editor topic:gdscript usability,"
+
+**Godot version:**
+
+3.2.3 rc4
+
+**Issue description:**
+
+I noticed that autocompletion is overzealous recently. When you type any standalone number, it will suggest some class containing this number in name. Which often leads to accidental inserting.
+
+
+",True,"Autocompletion triggers on numbers -
+
+**Godot version:**
+
+3.2.3 rc4
+
+**Issue description:**
+
+I noticed that autocompletion is overzealous recently. When you type any standalone number, it will suggest some class containing this number in name. Which often leads to accidental inserting.
+
+
+",1,autocompletion triggers on numbers please search existing issues for potential duplicates before filing yours godot version issue description i noticed that autocompletion is overzealous recently when you type any standalone number it will suggest some class containing this number in name which often leads to accidental inserting ,1
+78695,7658869473.0,IssuesEvent,2018-05-11 02:42:35,openworm/PyOpenWorm,https://api.github.com/repos/openworm/PyOpenWorm,closed,Fix code coverage reporting pipeline,ready testing,"Coveralls is failing for recent builds.
+
+Many people seem to have had this issue:
+https://github.com/lemurheavy/coveralls-public/issues/281",1.0,"Fix code coverage reporting pipeline - Coveralls is failing for recent builds.
+
+Many people seem to have had this issue:
+https://github.com/lemurheavy/coveralls-public/issues/281",0,fix code coverage reporting pipeline coveralls is failing for recent builds many people seem to have had this issue ,0
+3147,3354473276.0,IssuesEvent,2015-11-18 12:21:41,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,suggest to split script files and help reference,enhancement topic:editor usability,"I tested with commit 18e014a193840141911789aacf57b28a2e001724.
+I found help tab removed and can open many help reference.
+It looks good.
+But, I feel not comfortable to see all opened gdscript with help reference in one list.
+
+How about split list to show gdscript and reference separately?
+
+
+",True,"suggest to split script files and help reference - I tested with commit 18e014a193840141911789aacf57b28a2e001724.
+I found help tab removed and can open many help reference.
+It looks good.
+But, I feel not comfortable to see all opened gdscript with help reference in one list.
+
+How about split list to show gdscript and reference separately?
+
+
+",1,suggest to split script files and help reference i tested with commit i found help tab removed and can open many help reference it looks good but i feel not comfortable to see all opened gdscript with help reference in one list how about split list to show gdscript and reference separately ,1
+21040,16481385774.0,IssuesEvent,2021-05-24 12:10:39,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Tileset Editor Toolbar not shown unless tile clicked/selected,enhancement topic:editor usability,"
+
+3.2.2
+
+
+
+Win
+
+
+
+Create a tileset. Then attempt to edit the tileset. The GUI/UX is very odd. Selecting a picture shows the associated tile, but none of the edit tools or toolbar:
+
+
+
+Selecting the tile starts an edit, but also displays the associated edit toolbar:
+
+
+
+I think selecting the image, which causes the tile to display, should ALSO display the GUI",True,"Tileset Editor Toolbar not shown unless tile clicked/selected -
+
+3.2.2
+
+
+
+Win
+
+
+
+Create a tileset. Then attempt to edit the tileset. The GUI/UX is very odd. Selecting a picture shows the associated tile, but none of the edit tools or toolbar:
+
+
+
+Selecting the tile starts an edit, but also displays the associated edit toolbar:
+
+
+
+I think selecting the image, which causes the tile to display, should ALSO display the GUI",1,tileset editor toolbar not shown unless tile clicked selected please search existing issues for potential duplicates before filing yours win create a tileset then attempt to edit the tileset the gui ux is very odd selecting a picture shows the associated tile but none of the edit tools or toolbar selecting the tile starts an edit but also displays the associated edit toolbar i think selecting the image which causes the tile to display should also display the gui,1
+6180,4166480215.0,IssuesEvent,2016-06-20 03:39:23,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,GDscript overwriting does not works,bug topic:editor usability,"**Operating system or device:**
+Godot 2.0.2 win64 official release
+
+**Issue description** (what happened, and what was expected):
+When you click on the ""Edit/create the Node Script"" button into Scene panel, there is a ""Create Script for Node"" dialog box which appears.
+When you click the "".."" path button, an other dialog box appears.
+When you select a script that already exists, a confirmation box ask you if you want to overwrite it.
+If you reply ""OK"", the previous ""Create Script for Node"" dialog box refuses to overwrite it.
+
+**Steps to reproduce:**
+
+
+
+
+
+
+
+**Link to minimal example project** (optional but very welcome):
+",True,"GDscript overwriting does not works - **Operating system or device:**
+Godot 2.0.2 win64 official release
+
+**Issue description** (what happened, and what was expected):
+When you click on the ""Edit/create the Node Script"" button into Scene panel, there is a ""Create Script for Node"" dialog box which appears.
+When you click the "".."" path button, an other dialog box appears.
+When you select a script that already exists, a confirmation box ask you if you want to overwrite it.
+If you reply ""OK"", the previous ""Create Script for Node"" dialog box refuses to overwrite it.
+
+**Steps to reproduce:**
+
+
+
+
+
+
+
+**Link to minimal example project** (optional but very welcome):
+",1,gdscript overwriting does not works operating system or device godot official release issue description what happened and what was expected when you click on the edit create the node script button into scene panel there is a create script for node dialog box which appears when you click the path button an other dialog box appears when you select a script that already exists a confirmation box ask you if you want to overwrite it if you reply ok the previous create script for node dialog box refuses to overwrite it steps to reproduce link to minimal example project optional but very welcome ,1
+454234,13097105146.0,IssuesEvent,2020-08-03 16:50:12,department-of-veterans-affairs/caseflow,https://api.github.com/repos/department-of-veterans-affairs/caseflow,closed,Update case orders logic,Feature: auto-case-distribution Priority: High Product: caseflow-queue Stakeholder: BVA Team: Echo 🐬 Type: Enhancement User: Judge,"Update case distribution order to:
+1. Reduce backlog of legacy hearing cases tied to the judge to 30
+1. Continue with current algorithm
+
+
Newer old requirements
+
+User Story: When a Veteran Law Judge requests more cases, the case distribution logic should be as follows to ensure cases are worked in the correct order:
+
+1. Distribute non-priority cases tied to the judge
+ a. Legacy hearing cases tied to the judge - if the judge has more than 30 tied to them, fill their case order with only legacy hearing cases tied to them until the threshold of 30 has been hit or until their case order (batch size) has been met, whichever comes first. If the judge has <= 30 legacy hearing cases tied to them continue with the below. Creation of backlog [here](https://github.com/department-of-veterans-affairs/caseflow/issues/14543)
+ b. AMA hearing cases with affinity for the judge
+ c. Distribute non-priority cases that are general population based on docket proportions using stochastic rounding
+
+We no longer want Priority appeals to be distributed via the Request Cases logic, but instead be automatically distributed when they are ready #14604
+
+## Current
+We limit the number of priority appeals distributed in a distribution by ensuring we do not distribute more priority appeals than our priority target. [Priority target is calculated](https://github.com/department-of-veterans-affairs/caseflow/blob/5bbbe90117365a8689e3f894a3cc4223ea229569/app/models/concerns/ama_case_distribution.rb#L112) as the ratio of [sum of priority cases on all dockets](https://github.com/department-of-veterans-affairs/caseflow/blob/57e746e91b91c82c9b5f4edac343bde9688b68d9/app/models/docket_coordinator.rb#L88-L93) to [the total number of attorneys in caseflow * 3](https://github.com/department-of-veterans-affairs/caseflow/blob/57e746e91b91c82c9b5f4edac343bde9688b68d9/app/models/docket_coordinator.rb#L123-L125). This has lead to a steady increase in the number of priority appeals waiting to be distributed (`Distribution.statistics.priority_count` in [Nov 2018](http://query.prod.appeals.va.gov/question#eyJuYW1lIjpudWxsLCJkYXRhc2V0X3F1ZXJ5Ijp7ImRhdGFiYXNlIjoyLCJ0eXBlIjoicXVlcnkiLCJxdWVyeSI6eyJzb3VyY2UtdGFibGUiOjE1LCJvcmRlci1ieSI6W1siYXNjIixbImZpZWxkLWlkIiwyOTZdXV19fSwiZGlzcGxheSI6InRhYmxlIiwidmlzdWFsaXphdGlvbl9zZXR0aW5ncyI6e319) vs [now](http://query.prod.appeals.va.gov/question#eyJuYW1lIjpudWxsLCJkYXRhc2V0X3F1ZXJ5Ijp7ImRhdGFiYXNlIjoyLCJ0eXBlIjoicXVlcnkiLCJxdWVyeSI6eyJzb3VyY2UtdGFibGUiOjE1LCJvcmRlci1ieSI6W1siZGVzYyIsWyJmaWVsZC1pZCIsMjk2XV1dfX0sImRpc3BsYXkiOiJ0YWJsZSIsInZpc3VhbGl6YXRpb25fc2V0dGluZ3MiOnt9fQ==)).
+
+We also fill a distribution with legacy and ama hearing docket cases with [non priority cases associated with the judge](https://github.com/department-of-veterans-affairs/caseflow/blob/5bbbe90117365a8689e3f894a3cc4223ea229569/app/models/concerns/ama_case_distribution.rb#L30-L33) before we [distribute priority cases that are not associated with the judge](https://github.com/department-of-veterans-affairs/caseflow/blob/5bbbe90117365a8689e3f894a3cc4223ea229569/app/models/concerns/ama_case_distribution.rb#L38).
+
+Old requirements, now outdated
+After collecting stats on how the removal of this priority factor will affect other docket distributions and the go-ahead from the board, remove this priority target by replacing `priority_rem` with `@rem`.~
+
+```diff
+- # If we haven't yet met the priority target, distribute additional priority appeals.
+- priority_rem = (priority_target - @appeals.count(&:priority)).clamp(0, @rem)
+- oldest_priority_appeals_by_docket(priority_rem).each do |docket, n|
+- distribute_appeals(docket, n, priority: true)
+- end
++ # If we haven't yet filled the request order, distribute additional priority appeals.
++ oldest_priority_appeals_by_docket(@rem).each do |docket, n|
++ distribute_appeals(docket, n, priority: true)
++ end
+```
+The priority cases that are **not** associated with the judge should take precedence over the **non-priority** cases associated with the judge, so ensure we move this distribution to before we [distribute **non-priority** cases that are associated with the judge](https://github.com/department-of-veterans-affairs/caseflow/blob/5bbbe90117365a8689e3f894a3cc4223ea229569/app/models/concerns/ama_case_distribution.rb#L30-L33), but after we [distribute **priority** cases that are associated with the judge](https://github.com/department-of-veterans-affairs/caseflow/blob/5bbbe90117365a8689e3f894a3cc4223ea229569/app/models/concerns/ama_case_distribution.rb#L26-L28)
+
+
+## Acceptance Criteria
+ - [ ] Please put this work behind the feature toggle: Priority Case Auto-Distribution
+ - [ ] Every case order (distribution request) is filled with legacy hearing cases tied to the judge first. If the judge has more than 30 tied to them distribute their legacy hearing cases until the threshold of 30 has been hit or until their case order (batch size) has been met, whichever comes first
+ - [ ] Once the judge is down to 30 cases in their backlog, if they have more cases to fill in their request, fill the case order per the original algorithm rules
+
+### To reduce confusion
+Move these 3 lines https://github.com/department-of-veterans-affairs/caseflow/blob/6287312416efb2e55988a3d1bf5d69fbfefb235d/app/models/concerns/ama_case_distribution.rb#L32-L34
+
+to before these three lines. https://github.com/department-of-veterans-affairs/caseflow/blob/6287312416efb2e55988a3d1bf5d69fbfefb235d/app/models/concerns/ama_case_distribution.rb#L26-L28
+
+No other changes, do not remove priority",1.0,"Update case orders logic - Update case distribution order to:
+1. Reduce backlog of legacy hearing cases tied to the judge to 30
+1. Continue with current algorithm
+
+
Newer old requirements
+
+User Story: When a Veteran Law Judge requests more cases, the case distribution logic should be as follows to ensure cases are worked in the correct order:
+
+1. Distribute non-priority cases tied to the judge
+ a. Legacy hearing cases tied to the judge - if the judge has more than 30 tied to them, fill their case order with only legacy hearing cases tied to them until the threshold of 30 has been hit or until their case order (batch size) has been met, whichever comes first. If the judge has <= 30 legacy hearing cases tied to them continue with the below. Creation of backlog [here](https://github.com/department-of-veterans-affairs/caseflow/issues/14543)
+ b. AMA hearing cases with affinity for the judge
+ c. Distribute non-priority cases that are general population based on docket proportions using stochastic rounding
+
+We no longer want Priority appeals to be distributed via the Request Cases logic, but instead be automatically distributed when they are ready #14604
+
+## Current
+We limit the number of priority appeals distributed in a distribution by ensuring we do not distribute more priority appeals than our priority target. [Priority target is calculated](https://github.com/department-of-veterans-affairs/caseflow/blob/5bbbe90117365a8689e3f894a3cc4223ea229569/app/models/concerns/ama_case_distribution.rb#L112) as the ratio of [sum of priority cases on all dockets](https://github.com/department-of-veterans-affairs/caseflow/blob/57e746e91b91c82c9b5f4edac343bde9688b68d9/app/models/docket_coordinator.rb#L88-L93) to [the total number of attorneys in caseflow * 3](https://github.com/department-of-veterans-affairs/caseflow/blob/57e746e91b91c82c9b5f4edac343bde9688b68d9/app/models/docket_coordinator.rb#L123-L125). This has lead to a steady increase in the number of priority appeals waiting to be distributed (`Distribution.statistics.priority_count` in [Nov 2018](http://query.prod.appeals.va.gov/question#eyJuYW1lIjpudWxsLCJkYXRhc2V0X3F1ZXJ5Ijp7ImRhdGFiYXNlIjoyLCJ0eXBlIjoicXVlcnkiLCJxdWVyeSI6eyJzb3VyY2UtdGFibGUiOjE1LCJvcmRlci1ieSI6W1siYXNjIixbImZpZWxkLWlkIiwyOTZdXV19fSwiZGlzcGxheSI6InRhYmxlIiwidmlzdWFsaXphdGlvbl9zZXR0aW5ncyI6e319) vs [now](http://query.prod.appeals.va.gov/question#eyJuYW1lIjpudWxsLCJkYXRhc2V0X3F1ZXJ5Ijp7ImRhdGFiYXNlIjoyLCJ0eXBlIjoicXVlcnkiLCJxdWVyeSI6eyJzb3VyY2UtdGFibGUiOjE1LCJvcmRlci1ieSI6W1siZGVzYyIsWyJmaWVsZC1pZCIsMjk2XV1dfX0sImRpc3BsYXkiOiJ0YWJsZSIsInZpc3VhbGl6YXRpb25fc2V0dGluZ3MiOnt9fQ==)).
+
+We also fill a distribution with legacy and ama hearing docket cases with [non priority cases associated with the judge](https://github.com/department-of-veterans-affairs/caseflow/blob/5bbbe90117365a8689e3f894a3cc4223ea229569/app/models/concerns/ama_case_distribution.rb#L30-L33) before we [distribute priority cases that are not associated with the judge](https://github.com/department-of-veterans-affairs/caseflow/blob/5bbbe90117365a8689e3f894a3cc4223ea229569/app/models/concerns/ama_case_distribution.rb#L38).
+
+Old requirements, now outdated
+After collecting stats on how the removal of this priority factor will affect other docket distributions and the go-ahead from the board, remove this priority target by replacing `priority_rem` with `@rem`.~
+
+```diff
+- # If we haven't yet met the priority target, distribute additional priority appeals.
+- priority_rem = (priority_target - @appeals.count(&:priority)).clamp(0, @rem)
+- oldest_priority_appeals_by_docket(priority_rem).each do |docket, n|
+- distribute_appeals(docket, n, priority: true)
+- end
++ # If we haven't yet filled the request order, distribute additional priority appeals.
++ oldest_priority_appeals_by_docket(@rem).each do |docket, n|
++ distribute_appeals(docket, n, priority: true)
++ end
+```
+The priority cases that are **not** associated with the judge should take precedence over the **non-priority** cases associated with the judge, so ensure we move this distribution to before we [distribute **non-priority** cases that are associated with the judge](https://github.com/department-of-veterans-affairs/caseflow/blob/5bbbe90117365a8689e3f894a3cc4223ea229569/app/models/concerns/ama_case_distribution.rb#L30-L33), but after we [distribute **priority** cases that are associated with the judge](https://github.com/department-of-veterans-affairs/caseflow/blob/5bbbe90117365a8689e3f894a3cc4223ea229569/app/models/concerns/ama_case_distribution.rb#L26-L28)
+
+
+## Acceptance Criteria
+ - [ ] Please put this work behind the feature toggle: Priority Case Auto-Distribution
+ - [ ] Every case order (distribution request) is filled with legacy hearing cases tied to the judge first. If the judge has more than 30 tied to them distribute their legacy hearing cases until the threshold of 30 has been hit or until their case order (batch size) has been met, whichever comes first
+ - [ ] Once the judge is down to 30 cases in their backlog, if they have more cases to fill in their request, fill the case order per the original algorithm rules
+
+### To reduce confusion
+Move these 3 lines https://github.com/department-of-veterans-affairs/caseflow/blob/6287312416efb2e55988a3d1bf5d69fbfefb235d/app/models/concerns/ama_case_distribution.rb#L32-L34
+
+to before these three lines. https://github.com/department-of-veterans-affairs/caseflow/blob/6287312416efb2e55988a3d1bf5d69fbfefb235d/app/models/concerns/ama_case_distribution.rb#L26-L28
+
+No other changes, do not remove priority",0,update case orders logic update case distribution order to reduce backlog of legacy hearing cases tied to the judge to continue with current algorithm newer old requirements user story when a veteran law judge requests more cases the case distribution logic should be as follows to ensure cases are worked in the correct order distribute non priority cases tied to the judge a legacy hearing cases tied to the judge if the judge has more than tied to them fill their case order with only legacy hearing cases tied to them until the threshold of has been hit or until their case order batch size has been met whichever comes first if the judge has legacy hearing cases tied to them continue with the below creation of backlog b ama hearing cases with affinity for the judge c distribute non priority cases that are general population based on docket proportions using stochastic rounding we no longer want priority appeals to be distributed via the request cases logic but instead be automatically distributed when they are ready current we limit the number of priority appeals distributed in a distribution by ensuring we do not distribute more priority appeals than our priority target as the ratio of to this has lead to a steady increase in the number of priority appeals waiting to be distributed distribution statistics priority count in vs we also fill a distribution with legacy and ama hearing docket cases with before we old requirements now outdated after collecting stats on how the removal of this priority factor will affect other docket distributions and the go ahead from the board remove this priority target by replacing priority rem with rem diff if we haven t yet met the priority target distribute additional priority appeals priority rem priority target appeals count priority clamp rem oldest priority appeals by docket priority rem each do docket n distribute appeals docket n priority true end if we haven t yet filled the request order distribute additional priority appeals oldest priority appeals by docket rem each do docket n distribute appeals docket n priority true end the priority cases that are not associated with the judge should take precedence over the non priority cases associated with the judge so ensure we move this distribution to before we but after we acceptance criteria please put this work behind the feature toggle priority case auto distribution every case order distribution request is filled with legacy hearing cases tied to the judge first if the judge has more than tied to them distribute their legacy hearing cases until the threshold of has been hit or until their case order batch size has been met whichever comes first once the judge is down to cases in their backlog if they have more cases to fill in their request fill the case order per the original algorithm rules to reduce confusion move these lines to before these three lines no other changes do not remove priority,0
+563407,16683491028.0,IssuesEvent,2021-06-08 04:38:32,kubeapps/kubeapps,https://api.github.com/repos/kubeapps/kubeapps,closed,[kubeapps-apis] Investigate provision of chart Readme and values,component/apis-server kind/feature priority/high size/M,"### Description:
+
+The fluxv2 backend that we'll be using for the plugin does cache the index.yaml for a chart repository nicely, but given its gitops use-case, does not extract or otherwise provide access to other metadata usually presented to users when viewing details of a chart for potential installation. We want to investigate possible options here, such as extracting and caching when a specific chart (version) details are requested, rather than having to extract all and store in a db like is currently done for the existing helm support.
+
+@gfichtenholt Feel free to edit and fill in the details here, I'm just creating this so we can include it in the iteration plan (assuming it's going to be something you'll be working on).
+
+",1.0,"[kubeapps-apis] Investigate provision of chart Readme and values - ### Description:
+
+The fluxv2 backend that we'll be using for the plugin does cache the index.yaml for a chart repository nicely, but given its gitops use-case, does not extract or otherwise provide access to other metadata usually presented to users when viewing details of a chart for potential installation. We want to investigate possible options here, such as extracting and caching when a specific chart (version) details are requested, rather than having to extract all and store in a db like is currently done for the existing helm support.
+
+@gfichtenholt Feel free to edit and fill in the details here, I'm just creating this so we can include it in the iteration plan (assuming it's going to be something you'll be working on).
+
+",0, investigate provision of chart readme and values description the backend that we ll be using for the plugin does cache the index yaml for a chart repository nicely but given its gitops use case does not extract or otherwise provide access to other metadata usually presented to users when viewing details of a chart for potential installation we want to investigate possible options here such as extracting and caching when a specific chart version details are requested rather than having to extract all and store in a db like is currently done for the existing helm support gfichtenholt feel free to edit and fill in the details here i m just creating this so we can include it in the iteration plan assuming it s going to be something you ll be working on ,0
+6174,4165749986.0,IssuesEvent,2016-06-19 18:11:33,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Cant add second anchor point to first cotrol point in Path2D,enhancement topic:editor usability,There is no option to add second anchor point in the first point of Path2D - while it is possible to do it on Path3D. Also editing both is quite different and incoherent to me - including shortcuts for doing same things.,True,Cant add second anchor point to first cotrol point in Path2D - There is no option to add second anchor point in the first point of Path2D - while it is possible to do it on Path3D. Also editing both is quite different and incoherent to me - including shortcuts for doing same things.,1,cant add second anchor point to first cotrol point in there is no option to add second anchor point in the first point of while it is possible to do it on also editing both is quite different and incoherent to me including shortcuts for doing same things ,1
+221061,17288538674.0,IssuesEvent,2021-07-24 08:01:32,WoWManiaUK/Blackwing-Lair,https://api.github.com/repos/WoWManiaUK/Blackwing-Lair,closed,Missing Quest - All's Well (13924) - Ashenvale,Fixed in Dev - Confirmed by tester,"**Links:**
+
+https://www.wowhead.com/quest=13924/alls-well
+
+**What is happening:**
+Quest is not offered.
+
+
+**What should happen:**
+Upon completion of ""In the Hands of the Perverse"" (13922), The quest giver ""Averus Illwhisper"" (34335) sacrifices himself and the five ""Fallen Moonstone"" needed to complete the quest are deleted. He then becomes ""Averus the Redeemed"" (34358) and offers the quest ""All's Well"" (13924). Upon acceptance you are given ""Sanctified Moonstones"" to turn in to ""Pelturas Whitemoon"" (3894) which ends the quest chain to cure Relara Whitemoon of her sickness.
+**Is it crashing the server?:**
+
+**Other Information:**
+
+
+
+
+
+
+
+
+
+
+
+
+
+",1.0,"Missing Quest - All's Well (13924) - Ashenvale - **Links:**
+
+https://www.wowhead.com/quest=13924/alls-well
+
+**What is happening:**
+Quest is not offered.
+
+
+**What should happen:**
+Upon completion of ""In the Hands of the Perverse"" (13922), The quest giver ""Averus Illwhisper"" (34335) sacrifices himself and the five ""Fallen Moonstone"" needed to complete the quest are deleted. He then becomes ""Averus the Redeemed"" (34358) and offers the quest ""All's Well"" (13924). Upon acceptance you are given ""Sanctified Moonstones"" to turn in to ""Pelturas Whitemoon"" (3894) which ends the quest chain to cure Relara Whitemoon of her sickness.
+**Is it crashing the server?:**
+
+**Other Information:**
+
+
+
+
+
+
+
+
+
+
+
+
+
+",0,missing quest all s well ashenvale links what is happening quest is not offered what should happen upon completion of in the hands of the perverse the quest giver averus illwhisper sacrifices himself and the five fallen moonstone needed to complete the quest are deleted he then becomes averus the redeemed and offers the quest all s well upon acceptance you are given sanctified moonstones to turn in to pelturas whitemoon which ends the quest chain to cure relara whitemoon of her sickness is it crashing the server other information ,0
+18043,12504979604.0,IssuesEvent,2020-06-02 09:54:39,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Menu and mouse behavior enhancement suggestion,feature proposal topic:editor usability,"**Godot version:**
+v3.0.2 official *(but applies to all versions if i'm not mistaken).
+
+
+**OS/device including version:**
+macOS / Ubuntu *(but applies to all versions if i'm not mistaken).
+
+
+**Issue description:**
+Currently, to trigger a menu option with the mouse is necessary to open the menu (click! - _**release**_), point the option and trigger the option (click! - _**release**_).
+
+It would be possible to trigger them also opening the menu (click! and **hold**), point to the option an just then **release** the mouse button to trigger it? It is a common convention in most operating systems UI, and I really miss it.
+
+I understand it can be difficult to implement, but in my opinion it would make the Godot UI even better and enjoyable than it already is.
+
+**Minimal reproduction project:**
+1. Click and **hold** the mouse button over the 'Scene' main menu.
+2. Drag the mouse to 'New Scene'.
+3. **Release** the button. It won't create a new scene!
+
+Thank you.",True,"Menu and mouse behavior enhancement suggestion - **Godot version:**
+v3.0.2 official *(but applies to all versions if i'm not mistaken).
+
+
+**OS/device including version:**
+macOS / Ubuntu *(but applies to all versions if i'm not mistaken).
+
+
+**Issue description:**
+Currently, to trigger a menu option with the mouse is necessary to open the menu (click! - _**release**_), point the option and trigger the option (click! - _**release**_).
+
+It would be possible to trigger them also opening the menu (click! and **hold**), point to the option an just then **release** the mouse button to trigger it? It is a common convention in most operating systems UI, and I really miss it.
+
+I understand it can be difficult to implement, but in my opinion it would make the Godot UI even better and enjoyable than it already is.
+
+**Minimal reproduction project:**
+1. Click and **hold** the mouse button over the 'Scene' main menu.
+2. Drag the mouse to 'New Scene'.
+3. **Release** the button. It won't create a new scene!
+
+Thank you.",1,menu and mouse behavior enhancement suggestion godot version official but applies to all versions if i m not mistaken os device including version macos ubuntu but applies to all versions if i m not mistaken issue description currently to trigger a menu option with the mouse is necessary to open the menu click release point the option and trigger the option click release it would be possible to trigger them also opening the menu click and hold point to the option an just then release the mouse button to trigger it it is a common convention in most operating systems ui and i really miss it i understand it can be difficult to implement but in my opinion it would make the godot ui even better and enjoyable than it already is minimal reproduction project click and hold the mouse button over the scene main menu drag the mouse to new scene release the button it won t create a new scene thank you ,1
+16269,10719850202.0,IssuesEvent,2019-10-26 13:28:42,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Curve editor: add hint for RMB click,enhancement junior job topic:editor usability,"
+
+**Godot version:**
+
+current tip
+
+**OS/device including version:**
+
+Linux
+
+**Issue description:**
+
+It's not entirely clear what to do in an empty curve editor:
+
+
+
+Add a hint about using the RMB to insert the control points, similar to:
+
+
+
+",True,"Curve editor: add hint for RMB click -
+
+**Godot version:**
+
+current tip
+
+**OS/device including version:**
+
+Linux
+
+**Issue description:**
+
+It's not entirely clear what to do in an empty curve editor:
+
+
+
+Add a hint about using the RMB to insert the control points, similar to:
+
+
+
+",1,curve editor add hint for rmb click please search existing issues for potential duplicates before filing yours godot version current tip os device including version linux issue description it s not entirely clear what to do in an empty curve editor add a hint about using the rmb to insert the control points similar to ,1
+229485,18356410895.0,IssuesEvent,2021-10-08 18:52:49,iterative/dvc,https://api.github.com/repos/iterative/dvc,closed,test: tests need more love,p3-nice-to-have testing,"There are several issues with tests, which make them annoying and less efficient part of developer workflow (staging is fine). Here is a list:
+
+- [x] updater and analytics processes are started during tests
+- [ ] errors are wrapped in friendly messages, which bloats output
+- [x] debug log level bloats output
+- [x] temporary dirs not cleared #1770
+- [ ] tests are slow
+
+Some of this is either fine or must in staging environment, like DEBUG log level and tests being slow, however, this inhibits developers performance.
+
+On tests being slow. Ramdisk or mocked file system access might be used to speed them up in depeveloper environment, while running same as now on staging.
+",1.0,"test: tests need more love - There are several issues with tests, which make them annoying and less efficient part of developer workflow (staging is fine). Here is a list:
+
+- [x] updater and analytics processes are started during tests
+- [ ] errors are wrapped in friendly messages, which bloats output
+- [x] debug log level bloats output
+- [x] temporary dirs not cleared #1770
+- [ ] tests are slow
+
+Some of this is either fine or must in staging environment, like DEBUG log level and tests being slow, however, this inhibits developers performance.
+
+On tests being slow. Ramdisk or mocked file system access might be used to speed them up in depeveloper environment, while running same as now on staging.
+",0,test tests need more love there are several issues with tests which make them annoying and less efficient part of developer workflow staging is fine here is a list updater and analytics processes are started during tests errors are wrapped in friendly messages which bloats output debug log level bloats output temporary dirs not cleared tests are slow some of this is either fine or must in staging environment like debug log level and tests being slow however this inhibits developers performance on tests being slow ramdisk or mocked file system access might be used to speed them up in depeveloper environment while running same as now on staging ,0
+15236,9889033867.0,IssuesEvent,2019-06-25 12:58:33,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Grid Map node editing broken when transform is modified,bug confirmed topic:editor usability,"How to reproduce:
+Open 3D platformer demo stage.xml scene.
+Rotate Grid Map node.
+Try to paint-edit it.
+
+What happens: although pre-existing elements are deleted correctly new onea are added in wrong place, looks like they are added based on global not local space.
+",True,"Grid Map node editing broken when transform is modified - How to reproduce:
+Open 3D platformer demo stage.xml scene.
+Rotate Grid Map node.
+Try to paint-edit it.
+
+What happens: although pre-existing elements are deleted correctly new onea are added in wrong place, looks like they are added based on global not local space.
+",1,grid map node editing broken when transform is modified how to reproduce open platformer demo stage xml scene rotate grid map node try to paint edit it what happens although pre existing elements are deleted correctly new onea are added in wrong place looks like they are added based on global not local space ,1
+247744,7923151980.0,IssuesEvent,2018-07-05 13:16:29,0-complexity/openvcloud,https://api.github.com/repos/0-complexity/openvcloud,closed,disk type filter in /cloudapi/disks/list doesn't work,priority_major state_verification type_bug,"#### Detailed description
+disk type filter in /cloudapi/disks/list doesn't work
+
+
+
+#### Steps to reproduce
+- list disks with type **D**
+
+### current result
+disks with type **B** are listed
+
+### version
+```
+OpenvCloud
+Core: branch: master (feb194b) 7/3/2018, 11:01:52 AM
+G8VDC: tag: v2.4.0 (b085672) 3/16/2018, 5:09:29 PM
+Selfhealing: branch: master (b75d214) 7/2/2018, 4:41:42 PM
+````",1.0,"disk type filter in /cloudapi/disks/list doesn't work - #### Detailed description
+disk type filter in /cloudapi/disks/list doesn't work
+
+
+
+#### Steps to reproduce
+- list disks with type **D**
+
+### current result
+disks with type **B** are listed
+
+### version
+```
+OpenvCloud
+Core: branch: master (feb194b) 7/3/2018, 11:01:52 AM
+G8VDC: tag: v2.4.0 (b085672) 3/16/2018, 5:09:29 PM
+Selfhealing: branch: master (b75d214) 7/2/2018, 4:41:42 PM
+````",0,disk type filter in cloudapi disks list doesn t work detailed description disk type filter in cloudapi disks list doesn t work steps to reproduce list disks with type d current result disks with type b are listed version openvcloud core branch master am tag pm selfhealing branch master pm ,0
+84215,3655359098.0,IssuesEvent,2016-02-17 16:02:54,openshift/origin,https://api.github.com/repos/openshift/origin,closed,Create from image page changes background color at bottom,component/web kind/bug priority/P3,"This page has a gray background, but the bottom of the page is white. There is quite a lot of bottom padding here, too.
+
+To reproduce
+
+1. Click add to project
+1. Pick a builder image
+1. Click the advanced options link
+
+I believe this only happens at mobile widths.
+
+
+
+/cc @jwforres @sg00dwin
+",1.0,"Create from image page changes background color at bottom - This page has a gray background, but the bottom of the page is white. There is quite a lot of bottom padding here, too.
+
+To reproduce
+
+1. Click add to project
+1. Pick a builder image
+1. Click the advanced options link
+
+I believe this only happens at mobile widths.
+
+
+
+/cc @jwforres @sg00dwin
+",0,create from image page changes background color at bottom this page has a gray background but the bottom of the page is white there is quite a lot of bottom padding here too to reproduce click add to project pick a builder image click the advanced options link i believe this only happens at mobile widths cc jwforres ,0
+271984,8494420172.0,IssuesEvent,2018-10-28 21:19:50,ClinGen/clincoded,https://api.github.com/repos/ClinGen/clincoded,closed,Allow the addition of PMCIDs in addition to PMIDs,external colleague priority: low,Allow the entry of PMCIDs as well as PMIDs when adding literature to the database,1.0,Allow the addition of PMCIDs in addition to PMIDs - Allow the entry of PMCIDs as well as PMIDs when adding literature to the database,0,allow the addition of pmcids in addition to pmids allow the entry of pmcids as well as pmids when adding literature to the database,0
+6169,4165387066.0,IssuesEvent,2016-06-19 13:13:37,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Node Multi-Edit can't attach script to multiple nodes,bug confirmed topic:editor usability,"**Issue description** (what happened, and what was expected):
+I've tried to add same script to multiple nodes using multi-edit feature and properties editor. It didn't worked had to add them manually to each node :)
+
+**Steps to reproduce:**
+Create many nodes.
+Select them.
+Turn ON multi-edit/
+Go to properties and try to attach script to them.",True,"Node Multi-Edit can't attach script to multiple nodes - **Issue description** (what happened, and what was expected):
+I've tried to add same script to multiple nodes using multi-edit feature and properties editor. It didn't worked had to add them manually to each node :)
+
+**Steps to reproduce:**
+Create many nodes.
+Select them.
+Turn ON multi-edit/
+Go to properties and try to attach script to them.",1,node multi edit can t attach script to multiple nodes issue description what happened and what was expected i ve tried to add same script to multiple nodes using multi edit feature and properties editor it didn t worked had to add them manually to each node steps to reproduce create many nodes select them turn on multi edit go to properties and try to attach script to them ,1
+17947,12439819155.0,IssuesEvent,2020-05-26 10:48:30,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,A way to know in-editor if sub-resources are unique or not,feature proposal topic:editor usability,"Hi, if you duplicate for example an AnimationPlayer its sub-resources remain linked and on the editor there is no way to determine if the sub-resources are unique or not. The only way now is to check the .tscn file.
+So I was thinking that perhaps a good solution for this would be to show the list of sub-resources ids used by the node on the Inspector, I could try to implement this as well but I would like to know first if you agree with this or not :)
+",True,"A way to know in-editor if sub-resources are unique or not - Hi, if you duplicate for example an AnimationPlayer its sub-resources remain linked and on the editor there is no way to determine if the sub-resources are unique or not. The only way now is to check the .tscn file.
+So I was thinking that perhaps a good solution for this would be to show the list of sub-resources ids used by the node on the Inspector, I could try to implement this as well but I would like to know first if you agree with this or not :)
+",1,a way to know in editor if sub resources are unique or not hi if you duplicate for example an animationplayer its sub resources remain linked and on the editor there is no way to determine if the sub resources are unique or not the only way now is to check the tscn file so i was thinking that perhaps a good solution for this would be to show the list of sub resources ids used by the node on the inspector i could try to implement this as well but i would like to know first if you agree with this or not ,1
+132668,18268826797.0,IssuesEvent,2021-10-04 11:40:53,artsking/linux-3.0.35,https://api.github.com/repos/artsking/linux-3.0.35,opened,CVE-2014-4171 (Medium) detected in linux-stable-rtv3.8.6,security vulnerability,"## CVE-2014-4171 - Medium Severity Vulnerability
+
Vulnerable Library - linux-stable-rtv3.8.6
+
+
+
Julia Cartwright's fork of linux-stable-rt.git
+Library home page: https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git
+Found in HEAD commit: 5992fa81c6ac1b4e9db13f5408d914525c5b7875
+
+Found in base branch: master
+
+
+
Vulnerable Source Files (1)
+
+
+
+
+
+
+
+
+
+
Vulnerability Details
+
+
+mm/shmem.c in the Linux kernel through 3.15.1 does not properly implement the interaction between range notification and hole punching, which allows local users to cause a denial of service (i_mutex hold) by using the mmap system call to access a hole, as demonstrated by interfering with intended shmem activity by blocking completion of (1) an MADV_REMOVE madvise call or (2) an FALLOC_FL_PUNCH_HOLE fallocate call.
+
+
Publish Date: 2014-06-23
+
URL: CVE-2014-4171
+
+
+
+
CVSS 3 Score Details (5.5)
+
+
+Base Score Metrics:
+- Exploitability Metrics:
+ - Attack Vector: N/A
+ - Attack Complexity: N/A
+ - Privileges Required: N/A
+ - User Interaction: N/A
+ - Scope: N/A
+- Impact Metrics:
+ - Confidentiality Impact: N/A
+ - Integrity Impact: N/A
+ - Availability Impact: N/A
+
+For more information on CVSS3 Scores, click here.
+
+
+
+
Suggested Fix
+
+
+
Type: Upgrade version
+Origin: https://www.linuxkernelcves.com/cves/CVE-2014-4171
+Release Date: 2014-06-23
+Fix Resolution: v3.16-rc3,v3.12.26,v3.14.14,v3.2.62
+
+
+
+
+
+***
+Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2014-4171 (Medium) detected in linux-stable-rtv3.8.6 - ## CVE-2014-4171 - Medium Severity Vulnerability
+
Vulnerable Library - linux-stable-rtv3.8.6
+
+
+
Julia Cartwright's fork of linux-stable-rt.git
+Library home page: https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git
+Found in HEAD commit: 5992fa81c6ac1b4e9db13f5408d914525c5b7875
+
+Found in base branch: master
+
+
+
Vulnerable Source Files (1)
+
+
+
+
+
+
+
+
+
+
Vulnerability Details
+
+
+mm/shmem.c in the Linux kernel through 3.15.1 does not properly implement the interaction between range notification and hole punching, which allows local users to cause a denial of service (i_mutex hold) by using the mmap system call to access a hole, as demonstrated by interfering with intended shmem activity by blocking completion of (1) an MADV_REMOVE madvise call or (2) an FALLOC_FL_PUNCH_HOLE fallocate call.
+
+
Publish Date: 2014-06-23
+
URL: CVE-2014-4171
+
+
+
+
CVSS 3 Score Details (5.5)
+
+
+Base Score Metrics:
+- Exploitability Metrics:
+ - Attack Vector: N/A
+ - Attack Complexity: N/A
+ - Privileges Required: N/A
+ - User Interaction: N/A
+ - Scope: N/A
+- Impact Metrics:
+ - Confidentiality Impact: N/A
+ - Integrity Impact: N/A
+ - Availability Impact: N/A
+
+For more information on CVSS3 Scores, click here.
+
+
+
+
Suggested Fix
+
+
+
Type: Upgrade version
+Origin: https://www.linuxkernelcves.com/cves/CVE-2014-4171
+Release Date: 2014-06-23
+Fix Resolution: v3.16-rc3,v3.12.26,v3.14.14,v3.2.62
+
+
+
+
+
+***
+Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve medium detected in linux stable cve medium severity vulnerability vulnerable library linux stable julia cartwright s fork of linux stable rt git library home page a href found in head commit a href found in base branch master vulnerable source files vulnerability details mm shmem c in the linux kernel through does not properly implement the interaction between range notification and hole punching which allows local users to cause a denial of service i mutex hold by using the mmap system call to access a hole as demonstrated by interfering with intended shmem activity by blocking completion of an madv remove madvise call or an falloc fl punch hole fallocate call publish date url a href cvss score details base score metrics exploitability metrics attack vector n a attack complexity n a privileges required n a user interaction n a scope n a impact metrics confidentiality impact n a integrity impact n a availability impact n a for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource ,0
+543995,15888455678.0,IssuesEvent,2021-04-10 07:25:35,Domiii/dbux,https://api.github.com/repos/Domiii/dbux,opened,Improve `makeDefaultTraceLabel`,enhancement priority,"Goal: `makeDefaultTraceLabel` is not very useful for most types of expressions, since it only shows the expression itself, which often is the just the variable name. That is not useful when looking for specific interactions of a variable, especially in ""Object Traces"".
+
+* [ ] Instead, starting from staticTrace `t` keep going upward in the `staticTree` tree, to find the outer-most `staticTrace` whose `loc` fulfills these two conditions:
+ * It fully contains `t`'s `loc`
+ * It does not span more than one line
+ * (if `t` itself spans more than one line, then just return `t`)",1.0,"Improve `makeDefaultTraceLabel` - Goal: `makeDefaultTraceLabel` is not very useful for most types of expressions, since it only shows the expression itself, which often is the just the variable name. That is not useful when looking for specific interactions of a variable, especially in ""Object Traces"".
+
+* [ ] Instead, starting from staticTrace `t` keep going upward in the `staticTree` tree, to find the outer-most `staticTrace` whose `loc` fulfills these two conditions:
+ * It fully contains `t`'s `loc`
+ * It does not span more than one line
+ * (if `t` itself spans more than one line, then just return `t`)",0,improve makedefaulttracelabel goal makedefaulttracelabel is not very useful for most types of expressions since it only shows the expression itself which often is the just the variable name that is not useful when looking for specific interactions of a variable especially in object traces instead starting from statictrace t keep going upward in the statictree tree to find the outer most statictrace whose loc fulfills these two conditions it fully contains t s loc it does not span more than one line if t itself spans more than one line then just return t ,0
+15637,10198707235.0,IssuesEvent,2019-08-13 06:25:40,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Right-click menu deselects edits' content,bug topic:editor usability,"**Godot version:**
+v3.1.1.stable.official x64, Ubuntu
+
+**Issue description:**
+Editor issue.
+Right click menu on an edit field and the content of the edit gets deselected.
+
+
+**Steps to reproduce:**
+* Pick a parameter e.g. position.x in the Inspector.
+* Select the value.
+* Right click with the intention of doing ""Cut"" or ""Copy"".
+* The content of the edit field gets deselected, so cutting or copying doesn't do anything.
+CTRL+C / CTRL+X do work
+",True,"Right-click menu deselects edits' content - **Godot version:**
+v3.1.1.stable.official x64, Ubuntu
+
+**Issue description:**
+Editor issue.
+Right click menu on an edit field and the content of the edit gets deselected.
+
+
+**Steps to reproduce:**
+* Pick a parameter e.g. position.x in the Inspector.
+* Select the value.
+* Right click with the intention of doing ""Cut"" or ""Copy"".
+* The content of the edit field gets deselected, so cutting or copying doesn't do anything.
+CTRL+C / CTRL+X do work
+",1,right click menu deselects edits content godot version stable official ubuntu issue description editor issue right click menu on an edit field and the content of the edit gets deselected steps to reproduce pick a parameter e g position x in the inspector select the value right click with the intention of doing cut or copy the content of the edit field gets deselected so cutting or copying doesn t do anything ctrl c ctrl x do work ,1
+707780,24318621143.0,IssuesEvent,2022-09-30 08:44:53,webcompat/web-bugs,https://api.github.com/repos/webcompat/web-bugs,closed,login.cox.com - site is not usable,status-needsinfo browser-firefox priority-normal engine-gecko,"
+
+
+
+**URL**: https://login.cox.com/app/ccires_tveverywhere_1/exk1jha9awwp564kZ0h8/sso/saml?SAMLRequest=hVNdb9owFH3fr4j8TuKEUYFFUrGyakgdRZDuoS%2BV69wSr4nt%2BTp8%2FPsZCBlbt%2B7RR%2Fd8XB97fL2rq2ADFqVWKYlDSgJQQhdSrVPykN%2F2huQ6%2BzBGXleJYZPGlWoJPxpAF0wQwTrPu9EKmxrsCuxGCnhY3qWkdM4giyI0IfekkBf6GUKha49EB7VoNfl690aCBFMvLRV3xzxnlUqvpfLs3VGBGxMJIS3gk9uAD7%2FflmDhKY5g9xp%2FL%2FmIb7dmcPXx9ZGWwwhRHx1JcKutgOMOKXnhFQIJZtOU8GG%2FpDHvS7gqXsR6MJADWo5G%2FVKsYZj4GVxwRLmBXyzEBmYKHVcuJQlNkh4d9eI4TyiL%2B4yOwpjSRxIsrHZa6OqTVKcbbaximqNEpngNyJxgh3tgSUjZ82kI2Zc8X%2FQW96ucBN%2FOzSSHZnxXCtmpi%2Fe1TGtMslN17JjYXiq8L8DPzZCsq9Kzwjd9jqNLg%2Bz8Uj7vHKhDdMzGrrTG7dkS0GhV5LpNcYL%2FHeO8A4Od88PSFj3Drdv%2FP9Gfhlkb8vdYLTT3prPpQldS7KMOXQltfBnduX30YGfT7GY%2B7wQv8Q7syNFf%2Fk32Ew%3D%3D&RelayState=0cae8149-d774-46de-8629-d2caf32de358&SigAlg=http%3A%2F%2Fwww.w3.org%2F2000%2F09%2Fxmldsig%23rsa-sha1&Signature=lewLn5NgTIVFoWlbAeSjE6FuEQ3vEbgrNGTCXgsrxrZpHhZ4yFxwqNgKKG9KDDRHWuC8oPoGMhVLanbQW2obVcuuYmuhHbhd6qyD%2BY1Jmh87YNdBT2griOOb1paIgtqKRWdFl%2F2Q5YyLOhGecG9rXReTpqkMhmpQozYzHn4v8tt7MZONUXG36Hq0U4Thpmj5NnHQ7q1uj0WBDyq8EVB8hujhTEP%2FTjooEJVBk43zA7CUr0xYA87ZTMTfbpCj9JoLNqyW0Nt5XFOrUevNWhpcygFl%2FAdi8Kp27dMsrw6bI8JyrZp9frzBETKQ9v%2F60BR5EUDXS6dcqKEHxUGou1wDEw%3D%3D
+
+**Browser / Version**: Firefox 104.0
+**Operating System**: Mac OS X 10.15
+**Tested Another Browser**: Yes Chrome
+
+**Problem type**: Site is not usable
+**Description**: Unable to login
+**Steps to Reproduce**:
+COX
+403
+Access Forbidden
+
+You don't have permission to access this page.
+
+ View the screenshot
+ ![]()
+
+
+
+Browser Configuration
+
+
+
+_From [webcompat.com](https://webcompat.com/) with ❤️_",1.0,"login.cox.com - site is not usable -
+
+
+
+**URL**: https://login.cox.com/app/ccires_tveverywhere_1/exk1jha9awwp564kZ0h8/sso/saml?SAMLRequest=hVNdb9owFH3fr4j8TuKEUYFFUrGyakgdRZDuoS%2BV69wSr4nt%2BTp8%2FPsZCBlbt%2B7RR%2Fd8XB97fL2rq2ADFqVWKYlDSgJQQhdSrVPykN%2F2huQ6%2BzBGXleJYZPGlWoJPxpAF0wQwTrPu9EKmxrsCuxGCnhY3qWkdM4giyI0IfekkBf6GUKha49EB7VoNfl690aCBFMvLRV3xzxnlUqvpfLs3VGBGxMJIS3gk9uAD7%2FflmDhKY5g9xp%2FL%2FmIb7dmcPXx9ZGWwwhRHx1JcKutgOMOKXnhFQIJZtOU8GG%2FpDHvS7gqXsR6MJADWo5G%2FVKsYZj4GVxwRLmBXyzEBmYKHVcuJQlNkh4d9eI4TyiL%2B4yOwpjSRxIsrHZa6OqTVKcbbaximqNEpngNyJxgh3tgSUjZ82kI2Zc8X%2FQW96ucBN%2FOzSSHZnxXCtmpi%2Fe1TGtMslN17JjYXiq8L8DPzZCsq9Kzwjd9jqNLg%2Bz8Uj7vHKhDdMzGrrTG7dkS0GhV5LpNcYL%2FHeO8A4Od88PSFj3Drdv%2FP9Gfhlkb8vdYLTT3prPpQldS7KMOXQltfBnduX30YGfT7GY%2B7wQv8Q7syNFf%2Fk32Ew%3D%3D&RelayState=0cae8149-d774-46de-8629-d2caf32de358&SigAlg=http%3A%2F%2Fwww.w3.org%2F2000%2F09%2Fxmldsig%23rsa-sha1&Signature=lewLn5NgTIVFoWlbAeSjE6FuEQ3vEbgrNGTCXgsrxrZpHhZ4yFxwqNgKKG9KDDRHWuC8oPoGMhVLanbQW2obVcuuYmuhHbhd6qyD%2BY1Jmh87YNdBT2griOOb1paIgtqKRWdFl%2F2Q5YyLOhGecG9rXReTpqkMhmpQozYzHn4v8tt7MZONUXG36Hq0U4Thpmj5NnHQ7q1uj0WBDyq8EVB8hujhTEP%2FTjooEJVBk43zA7CUr0xYA87ZTMTfbpCj9JoLNqyW0Nt5XFOrUevNWhpcygFl%2FAdi8Kp27dMsrw6bI8JyrZp9frzBETKQ9v%2F60BR5EUDXS6dcqKEHxUGou1wDEw%3D%3D
+
+**Browser / Version**: Firefox 104.0
+**Operating System**: Mac OS X 10.15
+**Tested Another Browser**: Yes Chrome
+
+**Problem type**: Site is not usable
+**Description**: Unable to login
+**Steps to Reproduce**:
+COX
+403
+Access Forbidden
+
+You don't have permission to access this page.
+
+ View the screenshot
+ ![]()
+
+
+
+Browser Configuration
+
+
+
+_From [webcompat.com](https://webcompat.com/) with ❤️_",0,login cox com site is not usable url browser version firefox operating system mac os x tested another browser yes chrome problem type site is not usable description unable to login steps to reproduce cox access forbidden you don t have permission to access this page view the screenshot img alt screenshot src browser configuration none from with ❤️ ,0
+367620,10856029043.0,IssuesEvent,2019-11-13 19:41:09,kennyrkun/quantumjump,https://api.github.com/repos/kennyrkun/quantumjump,closed,FirstPersonController's velocity should be set to forward through teleports,bug: confirmed low priority,"When the first person controller is teleported, it's velocity remains the same. The way the teleport works is this: the player controller's position is set to the location of the teleport, and the player controller's rotation is set to the teleport location's rotation. So, if the had a rotation of 0 and is teleported to a rotation of 180, the player's velocity will effectively be in reverse. This means if you jump into a teleport, you will come out the other side flying backwards.",1.0,"FirstPersonController's velocity should be set to forward through teleports - When the first person controller is teleported, it's velocity remains the same. The way the teleport works is this: the player controller's position is set to the location of the teleport, and the player controller's rotation is set to the teleport location's rotation. So, if the had a rotation of 0 and is teleported to a rotation of 180, the player's velocity will effectively be in reverse. This means if you jump into a teleport, you will come out the other side flying backwards.",0,firstpersoncontroller s velocity should be set to forward through teleports when the first person controller is teleported it s velocity remains the same the way the teleport works is this the player controller s position is set to the location of the teleport and the player controller s rotation is set to the teleport location s rotation so if the had a rotation of and is teleported to a rotation of the player s velocity will effectively be in reverse this means if you jump into a teleport you will come out the other side flying backwards ,0
+10291,6664501367.0,IssuesEvent,2017-10-02 20:23:11,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Spot light gizmo always faces towards camera direction,bug topic:editor usability,"**Operating system or device, Godot version, GPU Model and driver (if graphics related):**
+59d1f96418540b6d1b8fec5892b3c1b7d1ae69e1
+
+**Issue description:**
+
+The spot light faces towards the camera
+
+
+
+
+**Steps to reproduce:**
+rotate the camera with a spot light on the scene
+
+",True,"Spot light gizmo always faces towards camera direction - **Operating system or device, Godot version, GPU Model and driver (if graphics related):**
+59d1f96418540b6d1b8fec5892b3c1b7d1ae69e1
+
+**Issue description:**
+
+The spot light faces towards the camera
+
+
+
+
+**Steps to reproduce:**
+rotate the camera with a spot light on the scene
+
+",1,spot light gizmo always faces towards camera direction operating system or device godot version gpu model and driver if graphics related issue description the spot light faces towards the camera steps to reproduce rotate the camera with a spot light on the scene ,1
+4049,3671735532.0,IssuesEvent,2016-02-22 09:16:39,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,2D Rotate tool always resets rotation to zero. ,bug topic:editor usability,"**Operating system or device:**
+Win 7, 64 bit. Godot 2.0 RC1. But I'm assuming it works this way for all platforms and all versions.
+
+**Issue description**
+When rotating nodes in the 2D viewport, the rotation always snaps back to zero first, which makes it confusing to use and nearly impossible to make small, precise changes.
+
+
+
+I expect it to add an offset to the current location based on your mouse position. (this is how the 3D rotate tool currently works.)
+
+_P.S. I like the new bug report template._ ",True,"2D Rotate tool always resets rotation to zero. - **Operating system or device:**
+Win 7, 64 bit. Godot 2.0 RC1. But I'm assuming it works this way for all platforms and all versions.
+
+**Issue description**
+When rotating nodes in the 2D viewport, the rotation always snaps back to zero first, which makes it confusing to use and nearly impossible to make small, precise changes.
+
+
+
+I expect it to add an offset to the current location based on your mouse position. (this is how the 3D rotate tool currently works.)
+
+_P.S. I like the new bug report template._ ",1, rotate tool always resets rotation to zero operating system or device win bit godot but i m assuming it works this way for all platforms and all versions issue description when rotating nodes in the viewport the rotation always snaps back to zero first which makes it confusing to use and nearly impossible to make small precise changes i expect it to add an offset to the current location based on your mouse position this is how the rotate tool currently works p s i like the new bug report template ,1
+324970,9915005945.0,IssuesEvent,2019-06-28 15:42:03,jenkins-x/jx,https://api.github.com/repos/jenkins-x/jx,closed,simplify the UX of `jx create cluster / jx install`,area/create-cluster area/install priority/important-soon,"right now the CLI asks way too many questions when not in batch mode.
+
+How about we move most of the questions into an `--advanced` mode so if folks really want they can tweak thing - but just use smart defaults for most questions.
+
+I guess we need to decide what are the minimal questions; I guess its
+
+* tekton v jenkins
+* domain
+* where to put the environment git repos
+
+thats probably about it?",1.0,"simplify the UX of `jx create cluster / jx install` - right now the CLI asks way too many questions when not in batch mode.
+
+How about we move most of the questions into an `--advanced` mode so if folks really want they can tweak thing - but just use smart defaults for most questions.
+
+I guess we need to decide what are the minimal questions; I guess its
+
+* tekton v jenkins
+* domain
+* where to put the environment git repos
+
+thats probably about it?",0,simplify the ux of jx create cluster jx install right now the cli asks way too many questions when not in batch mode how about we move most of the questions into an advanced mode so if folks really want they can tweak thing but just use smart defaults for most questions i guess we need to decide what are the minimal questions i guess its tekton v jenkins domain where to put the environment git repos thats probably about it ,0
+752063,26271907864.0,IssuesEvent,2023-01-06 17:49:30,CrowdDotDev/crowd.dev,https://api.github.com/repos/CrowdDotDev/crowd.dev,closed,[C-399] Merging members twice breaking the app,Bug High priority,"When merging a member through the dropdown option, the dialog won't close after a successful merge. So if the user merges the two members again the app will break
+
+
From [SyncLinear.com](https://synclinear.com) | [C-399](https://linear.app/crowddotdev/issue/C-399/merging-members-twice-breaking-the-app)",1.0,"[C-399] Merging members twice breaking the app - When merging a member through the dropdown option, the dialog won't close after a successful merge. So if the user merges the two members again the app will break
+
+
From [SyncLinear.com](https://synclinear.com) | [C-399](https://linear.app/crowddotdev/issue/C-399/merging-members-twice-breaking-the-app)",0, merging members twice breaking the app when merging a member through the dropdown option the dialog won t close after a successful merge so if the user merges the two members again the app will break from ,0
+268309,28565909482.0,IssuesEvent,2023-04-21 02:04:44,andygonzalez2010/store,https://api.github.com/repos/andygonzalez2010/store,closed,CVE-2022-38749 (Medium) detected in snakeyaml-1.23.jar - autoclosed,Mend: dependency security vulnerability,"## CVE-2022-38749 - Medium Severity Vulnerability
+
Vulnerable Library - snakeyaml-1.23.jar
+
+YAML 1.1 parser and emitter for Java
+Library home page: http://www.snakeyaml.org
+Path to dependency file: /pom.xml
+Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.23/snakeyaml-1.23.jar
+
+
+Dependency Hierarchy:
+ - liquibase-core-3.6.3.jar (Root Library)
+ - :x: **snakeyaml-1.23.jar** (Vulnerable Library)
+
Found in HEAD commit: 3f6d614029f4d6cfdddfcef8468949cb7822503c
+Found in base branch: master
+
+
+
+
Vulnerability Details
+
+
+Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
+
+
Publish Date: 2022-09-05
+
URL: CVE-2022-38749
+
+
+
+
CVSS 3 Score Details (6.5)
+
+
+Base Score Metrics:
+- Exploitability Metrics:
+ - Attack Vector: Network
+ - Attack Complexity: Low
+ - Privileges Required: Low
+ - User Interaction: None
+ - Scope: Unchanged
+- Impact Metrics:
+ - Confidentiality Impact: None
+ - Integrity Impact: None
+ - Availability Impact: High
+
+For more information on CVSS3 Scores, click here.
+
+
+
+
Suggested Fix
+
+
+
Type: Upgrade version
+Origin: https://bitbucket.org/snakeyaml/snakeyaml/issues/526/stackoverflow-oss-fuzz-47027
+Release Date: 2022-09-05
+Fix Resolution (org.yaml:snakeyaml): 1.31
+Direct dependency fix Resolution (org.liquibase:liquibase-core): 3.8.1
+
+
+
+
+
+***
+Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",True,"CVE-2022-38749 (Medium) detected in snakeyaml-1.23.jar - autoclosed - ## CVE-2022-38749 - Medium Severity Vulnerability
+
Vulnerable Library - snakeyaml-1.23.jar
+
+YAML 1.1 parser and emitter for Java
+Library home page: http://www.snakeyaml.org
+Path to dependency file: /pom.xml
+Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.23/snakeyaml-1.23.jar
+
+
+Dependency Hierarchy:
+ - liquibase-core-3.6.3.jar (Root Library)
+ - :x: **snakeyaml-1.23.jar** (Vulnerable Library)
+
Found in HEAD commit: 3f6d614029f4d6cfdddfcef8468949cb7822503c
+Found in base branch: master
+
+
+
+
Vulnerability Details
+
+
+Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
+
+
Publish Date: 2022-09-05
+
URL: CVE-2022-38749
+
+
+
+
CVSS 3 Score Details (6.5)
+
+
+Base Score Metrics:
+- Exploitability Metrics:
+ - Attack Vector: Network
+ - Attack Complexity: Low
+ - Privileges Required: Low
+ - User Interaction: None
+ - Scope: Unchanged
+- Impact Metrics:
+ - Confidentiality Impact: None
+ - Integrity Impact: None
+ - Availability Impact: High
+
+For more information on CVSS3 Scores, click here.
+
+
+
+
Suggested Fix
+
+
+
Type: Upgrade version
+Origin: https://bitbucket.org/snakeyaml/snakeyaml/issues/526/stackoverflow-oss-fuzz-47027
+Release Date: 2022-09-05
+Fix Resolution (org.yaml:snakeyaml): 1.31
+Direct dependency fix Resolution (org.liquibase:liquibase-core): 3.8.1
+
+
+
+
+
+***
+Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)",0,cve medium detected in snakeyaml jar autoclosed cve medium severity vulnerability vulnerable library snakeyaml jar yaml parser and emitter for java library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org yaml snakeyaml snakeyaml jar dependency hierarchy liquibase core jar root library x snakeyaml jar vulnerable library found in head commit a href found in base branch master vulnerability details using snakeyaml to parse untrusted yaml files may be vulnerable to denial of service attacks dos if the parser is running on user supplied input an attacker may supply content that causes the parser to crash by stackoverflow publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org yaml snakeyaml direct dependency fix resolution org liquibase liquibase core step up your open source security game with mend ,0
+11458,7244462998.0,IssuesEvent,2018-02-14 15:12:56,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Close bottom dock when pressing ESC,enhancement topic:editor usability,"A minor UX enhancement, could pressing Esc close the bottom dock if nothing else listens to that key?
+I was inspired by the way you can press Esc to close docks in QtCreator, and found myself mechanically press Esc to close those in Godot too, but was annoyed to have to take my mouse and close them manually.",True,"Close bottom dock when pressing ESC - A minor UX enhancement, could pressing Esc close the bottom dock if nothing else listens to that key?
+I was inspired by the way you can press Esc to close docks in QtCreator, and found myself mechanically press Esc to close those in Godot too, but was annoyed to have to take my mouse and close them manually.",1,close bottom dock when pressing esc a minor ux enhancement could pressing esc close the bottom dock if nothing else listens to that key i was inspired by the way you can press esc to close docks in qtcreator and found myself mechanically press esc to close those in godot too but was annoyed to have to take my mouse and close them manually ,1
+18213,12677919650.0,IssuesEvent,2020-06-19 08:45:43,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Button->ShortCut->InputEventKey in editor difficult to use,enhancement topic:editor usability,"**Godot version:**
+3.x (master)
+
+**Issue description:**
+Adding an InputEventKey to a ShortCut to a Button in the editor does not provide an easy way to set the key that will be used as the shortcut.
+
+The available fields where the character is set appear to be **scancode** or **unicode** but they are integer fields with no clear mapping to keyboard characters.
+
+It would be useful if the functionality was similar to that of Project->Project Settings->Input Map where you are given a ""press a key"" dialog that populates the shortcut.
+",True,"Button->ShortCut->InputEventKey in editor difficult to use - **Godot version:**
+3.x (master)
+
+**Issue description:**
+Adding an InputEventKey to a ShortCut to a Button in the editor does not provide an easy way to set the key that will be used as the shortcut.
+
+The available fields where the character is set appear to be **scancode** or **unicode** but they are integer fields with no clear mapping to keyboard characters.
+
+It would be useful if the functionality was similar to that of Project->Project Settings->Input Map where you are given a ""press a key"" dialog that populates the shortcut.
+",1,button shortcut inputeventkey in editor difficult to use godot version x master issue description adding an inputeventkey to a shortcut to a button in the editor does not provide an easy way to set the key that will be used as the shortcut the available fields where the character is set appear to be scancode or unicode but they are integer fields with no clear mapping to keyboard characters it would be useful if the functionality was similar to that of project project settings input map where you are given a press a key dialog that populates the shortcut ,1
+268246,23352930906.0,IssuesEvent,2022-08-10 03:17:07,Tencent/bk-ci,https://api.github.com/repos/Tencent/bk-ci,closed,bug:metrics第三方平台数据上报逻辑支持跨集群数据上报,kind/bug for gray for test area/ci/backend tested streams/for test streams/for gray streams/done,"**问题：** codecc和质量红线上报给某个集群的metrics服务的统计数据有可能是多个集群的数据，而存第三方平台上报数据的表又做了分库分表方案，这种场景会导致分库分表的分片规则中的集群名称出问题。
+
+**措施：** 第三方平台上报的数据属于哪个集群就交给哪个集群的metrics服务处理。",3.0,"bug:metrics第三方平台数据上报逻辑支持跨集群数据上报 - **问题：** codecc和质量红线上报给某个集群的metrics服务的统计数据有可能是多个集群的数据，而存第三方平台上报数据的表又做了分库分表方案，这种场景会导致分库分表的分片规则中的集群名称出问题。
+
+**措施：** 第三方平台上报的数据属于哪个集群就交给哪个集群的metrics服务处理。",0,bug metrics第三方平台数据上报逻辑支持跨集群数据上报 问题： codecc和质量红线上报给某个集群的metrics服务的统计数据有可能是多个集群的数据，而存第三方平台上报数据的表又做了分库分表方案，这种场景会导致分库分表的分片规则中的集群名称出问题。 措施： 第三方平台上报的数据属于哪个集群就交给哪个集群的metrics服务处理。,0
+190605,15252188127.0,IssuesEvent,2021-02-20 01:52:52,neuronsimulator/nrn,https://api.github.com/repos/neuronsimulator/nrn,opened,path issues in install.md,documentation,"If you look at install.md directly, it correctly shows the osx_installer_warning_solution image.
+
+However, when that's used for the readthedocs version, the path for that image incorrectly includes extra folders and should be: `https://nrn.readthedocs.io/en/latest/_static/osx_installer_warning_solution.png` (and thus the image doesn't show up on https://nrn.readthedocs.io/en/latest/install/install_instructions.html#mac-os)",1.0,"path issues in install.md - If you look at install.md directly, it correctly shows the osx_installer_warning_solution image.
+
+However, when that's used for the readthedocs version, the path for that image incorrectly includes extra folders and should be: `https://nrn.readthedocs.io/en/latest/_static/osx_installer_warning_solution.png` (and thus the image doesn't show up on https://nrn.readthedocs.io/en/latest/install/install_instructions.html#mac-os)",0,path issues in install md if you look at install md directly it correctly shows the osx installer warning solution image however when that s used for the readthedocs version the path for that image incorrectly includes extra folders and should be and thus the image doesn t show up on ,0
+20908,16191816674.0,IssuesEvent,2021-05-04 09:32:56,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,File with extension *.tscn and *.scn not generated previews in filesystem dock,enhancement topic:editor usability,"
+
+**Godot version:** Godot_v3.3-stable_win64
+
+
+
+**OS/device including version:** Win 10 pro 20H2 , AMD Ryzen 5 3500X , NVIDIA GeForce GTX 750 TI (2 Gb RAM), GLES3
+
+
+
+**Issue description:** *.tscn and *.scn not generated previews in filesystem dock. But generated in Godot_v3.0.6-stable_win64
+
+
+
+**Steps to reproduce:** Create and save any scene with Spatial node containing any Mesh (with or without Light source)
+
+
+
+**Minimal reproduction project:**
+[test_no_preview_issue.zip](https://github.com/godotengine/godot/files/6417405/test_no_preview_issue.zip)
+
+
+",True,"File with extension *.tscn and *.scn not generated previews in filesystem dock -
+
+**Godot version:** Godot_v3.3-stable_win64
+
+
+
+**OS/device including version:** Win 10 pro 20H2 , AMD Ryzen 5 3500X , NVIDIA GeForce GTX 750 TI (2 Gb RAM), GLES3
+
+
+
+**Issue description:** *.tscn and *.scn not generated previews in filesystem dock. But generated in Godot_v3.0.6-stable_win64
+
+
+
+**Steps to reproduce:** Create and save any scene with Spatial node containing any Mesh (with or without Light source)
+
+
+
+**Minimal reproduction project:**
+[test_no_preview_issue.zip](https://github.com/godotengine/godot/files/6417405/test_no_preview_issue.zip)
+
+
+",1,file with extension tscn and scn not generated previews in filesystem dock please search existing issues for potential duplicates before filing yours godot version godot stable os device including version win pro amd ryzen nvidia geforce gtx ti gb ram issue description tscn and scn not generated previews in filesystem dock but generated in godot stable steps to reproduce create and save any scene with spatial node containing any mesh with or without light source minimal reproduction project ,1
+6250,4194747596.0,IssuesEvent,2016-06-25 08:28:58,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Light icon in 3D view is low-resolution,confirmed enhancement topic:editor usability,"The light icon in the 3D view is low-resolution, which makes it ugly. I'm using a 1920×1080 screen. It also has visible clipping (because a non-fully transparent pixel touches the edge of the image).
+
+*Click on the image to enlarge it.*
+
+",True,"Light icon in 3D view is low-resolution - The light icon in the 3D view is low-resolution, which makes it ugly. I'm using a 1920×1080 screen. It also has visible clipping (because a non-fully transparent pixel touches the edge of the image).
+
+*Click on the image to enlarge it.*
+
+",1,light icon in view is low resolution the light icon in the view is low resolution which makes it ugly i m using a × screen it also has visible clipping because a non fully transparent pixel touches the edge of the image click on the image to enlarge it ,1
+26928,27384420829.0,IssuesEvent,2023-02-28 12:20:04,godotengine/godot,https://api.github.com/repos/godotengine/godot,opened,Can't copy text from editor help,bug topic:editor usability,"### Godot version
+
+4.0 rc6
+
+### System information
+
+Windows 10 x64
+
+### Issue description
+
+You can select text in editor help, but it can't be copied. Ctrl+C does not change clipboard.
+
+### Steps to reproduce
+
+1. F1
+2. Enter
+3. Select text
+4. Ctrl+C
+5. Ctrl+V somewhere
+
+### Minimal reproduction project
+
+N/A",True,"Can't copy text from editor help - ### Godot version
+
+4.0 rc6
+
+### System information
+
+Windows 10 x64
+
+### Issue description
+
+You can select text in editor help, but it can't be copied. Ctrl+C does not change clipboard.
+
+### Steps to reproduce
+
+1. F1
+2. Enter
+3. Select text
+4. Ctrl+C
+5. Ctrl+V somewhere
+
+### Minimal reproduction project
+
+N/A",1,can t copy text from editor help godot version system information windows issue description you can select text in editor help but it can t be copied ctrl c does not change clipboard steps to reproduce enter select text ctrl c ctrl v somewhere minimal reproduction project n a,1
+277889,30686947672.0,IssuesEvent,2023-07-26 12:57:57,meilisearch/heed,https://api.github.com/repos/meilisearch/heed,reopened,Implement Send for RoTxn,bug breaking security,"I wanted to make the write transactions `Send` but LMDB's documentation says:
+> A write [Transaction](https://lmdb.readthedocs.io/en/release/#lmdb.Transaction) may only be used from the thread it was created on.
+
+However, I think that making `RoTxn: Sync` with the `sync-read-txn` is not safe, but I may be mistaken. But, for sure, `RoTxn` should implement `Send`, since it can be moved to other threads safely.",True,"Implement Send for RoTxn - I wanted to make the write transactions `Send` but LMDB's documentation says:
+> A write [Transaction](https://lmdb.readthedocs.io/en/release/#lmdb.Transaction) may only be used from the thread it was created on.
+
+However, I think that making `RoTxn: Sync` with the `sync-read-txn` is not safe, but I may be mistaken. But, for sure, `RoTxn` should implement `Send`, since it can be moved to other threads safely.",0,implement send for rotxn i wanted to make the write transactions send but lmdb s documentation says a write may only be used from the thread it was created on however i think that making rotxn sync with the sync read txn is not safe but i may be mistaken but for sure rotxn should implement send since it can be moved to other threads safely ,0
+15339,9966613537.0,IssuesEvent,2019-07-08 11:40:16,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Search feature while assigning NodePaths,feature proposal topic:editor usability,"
+**Godot version:**
+ANY
+
+**OS/device including version:**
+ANY
+
+
+**Issue description:**
+As scene grow over the life of a project being able to search for a node in the tree while trying to assign one to a NodePath or any other such functions would become a wise thing to have.
+
+
+**Steps to reproduce:**
+just have a large scene tree and try to find a single node
+
+**Minimal reproduction project:**
+
+",True,"Search feature while assigning NodePaths -
+**Godot version:**
+ANY
+
+**OS/device including version:**
+ANY
+
+
+**Issue description:**
+As scene grow over the life of a project being able to search for a node in the tree while trying to assign one to a NodePath or any other such functions would become a wise thing to have.
+
+
+**Steps to reproduce:**
+just have a large scene tree and try to find a single node
+
+**Minimal reproduction project:**
+
+",1,search feature while assigning nodepaths godot version any os device including version any issue description as scene grow over the life of a project being able to search for a node in the tree while trying to assign one to a nodepath or any other such functions would become a wise thing to have steps to reproduce just have a large scene tree and try to find a single node minimal reproduction project ,1
+26414,4699600142.0,IssuesEvent,2016-10-12 16:06:00,ARM-DOE/pyart,https://api.github.com/repos/ARM-DOE/pyart,closed,Trouble converting Rainbow files to Cfradial,component: pyart.aux_io Defect,"I'm unsuccessfully trying to read some Rainbow format radar data into a radar structure (so that I can output cfradial files).
+
+In [1]: import pyart
+
+## You are using the Python ARM Radar Toolkit (Py-ART), an open source
+## library for working with weather radar data.
+##
+## If you use this software to prepare a publication, please cite:
+##
+## JJ Helmus and SM Collis, JORS 2016, doi: 10.5334/jors.119
+
+In [2]: file = '/home/disk/bob/olympex/xband/rainbowFiles/RAW_DOPVOL1_A/DBZ/2016011207500600dBZ.azi'
+
+In [3]: radar = pyart.aux_io.read_rainbow_wrl(file)
+---------------------------------------------------------------------------
+TypeError Traceback (most recent call last)
+
in ()
+----> 1 radar = pyart.aux_io.read_rainbow_wrl(file)
+
+/home/disk/shear2/brodzik/.local/lib/python2.7/site-packages/pyart/aux_io/rainbow_wrl.pyc in read_rainbow_wrl(filename, field_names, additional_metadata, file_field_names, exclude_fields, **kwargs)
+ 263 _range['data'] = np.linspace(
+ 264 start_range+r_res / 2., float(nbins - 1.) * r_res+r_res / 2.,
+--> 265 nbins, dtype='float32')
+ 266
+ 267 # containers for data
+
+TypeError: linspace() got an unexpected keyword argument 'dtype'
+
+I don't know why that line is causing trouble since dtype is a valid keyword argument for np.linspace and float32 is a valid option.
+
+Has anyone tried to do such a thing successfully? I've attached the rainbow file in question to this email in case someone wants to give it a try. (2016011207500600dBZ.zip)
+
+FYI, I'm using pyart v1.8.0.dev and numpy v1.8.2. The file in question is Rainbow v5.43.10 but I get the same error when trying to read in a Rainbow v5.34.16 file (which is supposedly supported by this version of pyart). I've attached this older file as well (2013070308340000dBuZ.zip).
+
+[2013070308340000dBuZ.zip](https://github.com/ARM-DOE/pyart/files/516980/2013070308340000dBuZ.zip)
+
+
+Thanks.
+
+Stacy
+[2016011207500600dBZ.zip](https://github.com/ARM-DOE/pyart/files/516975/2016011207500600dBZ.zip)
+
+",1.0,"Trouble converting Rainbow files to Cfradial - I'm unsuccessfully trying to read some Rainbow format radar data into a radar structure (so that I can output cfradial files).
+
+In [1]: import pyart
+
+## You are using the Python ARM Radar Toolkit (Py-ART), an open source
+## library for working with weather radar data.
+##
+## If you use this software to prepare a publication, please cite:
+##
+## JJ Helmus and SM Collis, JORS 2016, doi: 10.5334/jors.119
+
+In [2]: file = '/home/disk/bob/olympex/xband/rainbowFiles/RAW_DOPVOL1_A/DBZ/2016011207500600dBZ.azi'
+
+In [3]: radar = pyart.aux_io.read_rainbow_wrl(file)
+---------------------------------------------------------------------------
+TypeError Traceback (most recent call last)
+ in ()
+----> 1 radar = pyart.aux_io.read_rainbow_wrl(file)
+
+/home/disk/shear2/brodzik/.local/lib/python2.7/site-packages/pyart/aux_io/rainbow_wrl.pyc in read_rainbow_wrl(filename, field_names, additional_metadata, file_field_names, exclude_fields, **kwargs)
+ 263 _range['data'] = np.linspace(
+ 264 start_range+r_res / 2., float(nbins - 1.) * r_res+r_res / 2.,
+--> 265 nbins, dtype='float32')
+ 266
+ 267 # containers for data
+
+TypeError: linspace() got an unexpected keyword argument 'dtype'
+
+I don't know why that line is causing trouble since dtype is a valid keyword argument for np.linspace and float32 is a valid option.
+
+Has anyone tried to do such a thing successfully? I've attached the rainbow file in question to this email in case someone wants to give it a try. (2016011207500600dBZ.zip)
+
+FYI, I'm using pyart v1.8.0.dev and numpy v1.8.2. The file in question is Rainbow v5.43.10 but I get the same error when trying to read in a Rainbow v5.34.16 file (which is supposedly supported by this version of pyart). I've attached this older file as well (2013070308340000dBuZ.zip).
+
+[2013070308340000dBuZ.zip](https://github.com/ARM-DOE/pyart/files/516980/2013070308340000dBuZ.zip)
+
+
+Thanks.
+
+Stacy
+[2016011207500600dBZ.zip](https://github.com/ARM-DOE/pyart/files/516975/2016011207500600dBZ.zip)
+
+",0,trouble converting rainbow files to cfradial i m unsuccessfully trying to read some rainbow format radar data into a radar structure so that i can output cfradial files in import pyart you are using the python arm radar toolkit py art an open source library for working with weather radar data if you use this software to prepare a publication please cite jj helmus and sm collis jors doi jors in file home disk bob olympex xband rainbowfiles raw a dbz azi in radar pyart aux io read rainbow wrl file typeerror traceback most recent call last in radar pyart aux io read rainbow wrl file home disk brodzik local lib site packages pyart aux io rainbow wrl pyc in read rainbow wrl filename field names additional metadata file field names exclude fields kwargs range np linspace start range r res float nbins r res r res nbins dtype containers for data typeerror linspace got an unexpected keyword argument dtype i don t know why that line is causing trouble since dtype is a valid keyword argument for np linspace and is a valid option has anyone tried to do such a thing successfully i ve attached the rainbow file in question to this email in case someone wants to give it a try zip fyi i m using pyart dev and numpy the file in question is rainbow but i get the same error when trying to read in a rainbow file which is supposedly supported by this version of pyart i ve attached this older file as well zip thanks stacy ,0
+24657,24098046168.0,IssuesEvent,2022-09-19 20:44:33,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,AnimationTree can't replace one connection with another of the same type.,enhancement topic:editor usability topic:animation,"### Godot version
+
+4.0b1 mono
+
+### System information
+
+Windows 10, Nvidia gtx 1660Ti, latest drivers, Vulkan
+
+### Issue description
+
+In the animation tree if I add two animation nodes set their animations then connect one node to output, everything is ok but if I try to drag the other node's noodle to the output I get a warning as you can see in the image and here:
+`Unable to connect, port may be in use or connection may be invalid.`
+
+I'm not entirely sure if this is a bug but it does feel like one since the workaround is disconnecting the previous connection and connecting the second one which is just extra step which doesn't make much sense?
+
+
+
+
+### Steps to reproduce
+
+1. Create AnimationTree (set it up with an animation player if you need to)
+2. Create two or more animation nodes and set them up with some animation
+3. Connect first animation node to the Output
+4. Try connecting the second animation node to the output - this gives a warning and doesn't connect.
+
+### Minimal reproduction project
+
+-",True,"AnimationTree can't replace one connection with another of the same type. - ### Godot version
+
+4.0b1 mono
+
+### System information
+
+Windows 10, Nvidia gtx 1660Ti, latest drivers, Vulkan
+
+### Issue description
+
+In the animation tree if I add two animation nodes set their animations then connect one node to output, everything is ok but if I try to drag the other node's noodle to the output I get a warning as you can see in the image and here:
+`Unable to connect, port may be in use or connection may be invalid.`
+
+I'm not entirely sure if this is a bug but it does feel like one since the workaround is disconnecting the previous connection and connecting the second one which is just extra step which doesn't make much sense?
+
+
+
+
+### Steps to reproduce
+
+1. Create AnimationTree (set it up with an animation player if you need to)
+2. Create two or more animation nodes and set them up with some animation
+3. Connect first animation node to the Output
+4. Try connecting the second animation node to the output - this gives a warning and doesn't connect.
+
+### Minimal reproduction project
+
+-",1,animationtree can t replace one connection with another of the same type godot version mono system information windows nvidia gtx latest drivers vulkan issue description in the animation tree if i add two animation nodes set their animations then connect one node to output everything is ok but if i try to drag the other node s noodle to the output i get a warning as you can see in the image and here unable to connect port may be in use or connection may be invalid i m not entirely sure if this is a bug but it does feel like one since the workaround is disconnecting the previous connection and connecting the second one which is just extra step which doesn t make much sense steps to reproduce create animationtree set it up with an animation player if you need to create two or more animation nodes and set them up with some animation connect first animation node to the output try connecting the second animation node to the output this gives a warning and doesn t connect minimal reproduction project ,1
+424190,29045540425.0,IssuesEvent,2023-05-13 14:05:44,Cloud-native-engineering/sem01_aws,https://api.github.com/repos/Cloud-native-engineering/sem01_aws,closed,Schreiben der Einleitung,documentation enhancement,"## Beschreibung
+
+Die Leserinnen und Leser der Semesterarbeit sollen gut ins Thema geführt werden. Deshalb soll eine Einleitung geschrieben werden.
+
+## Akzeptanzkriterien
+
+- [x] Einleitung geschrieben
+- [x] Rechtschreibung korrigiert
+
+## Abhängigkeiten
+
+- keine
+
+---
+
+### Definition of Done
+
+- [x] Alle Akzeptanzkriterien erfüllt
+- [x] Review ist durchgeführt
+- [x] Keine bekannten Fehler
+",1.0,"Schreiben der Einleitung - ## Beschreibung
+
+Die Leserinnen und Leser der Semesterarbeit sollen gut ins Thema geführt werden. Deshalb soll eine Einleitung geschrieben werden.
+
+## Akzeptanzkriterien
+
+- [x] Einleitung geschrieben
+- [x] Rechtschreibung korrigiert
+
+## Abhängigkeiten
+
+- keine
+
+---
+
+### Definition of Done
+
+- [x] Alle Akzeptanzkriterien erfüllt
+- [x] Review ist durchgeführt
+- [x] Keine bekannten Fehler
+",0,schreiben der einleitung beschreibung die leserinnen und leser der semesterarbeit sollen gut ins thema geführt werden deshalb soll eine einleitung geschrieben werden akzeptanzkriterien einleitung geschrieben rechtschreibung korrigiert abhängigkeiten keine definition of done alle akzeptanzkriterien erfüllt review ist durchgeführt keine bekannten fehler ,0
+21711,17570901708.0,IssuesEvent,2021-08-14 17:16:23,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Some drop-down menus are hard to notice,enhancement topic:editor usability,"**Godot version:**
+3.1 stable
+
+**Issue description:**
+Some drop-down menus do not look like menus. The name of the node in the inspector, the ""tilemap"" at the top of the tilemap bar. Those ones.
+
+
+After a year using Godot, I just now learn that these can be clicked. This is not properly shown in the design, it is flat and looks like a title, causing much confusion for anyone who doesn't know otherwise.
+
+Other interactive elements in the editor are coloured differently, hinting at their press-able qualities. Just do that for those too. Important tools are hidden behind these invisible drop-downs.
+Just like this :
+
+And then no more confusion, everything is clear. Just make it the same as other similar buttons.
+",True,"Some drop-down menus are hard to notice - **Godot version:**
+3.1 stable
+
+**Issue description:**
+Some drop-down menus do not look like menus. The name of the node in the inspector, the ""tilemap"" at the top of the tilemap bar. Those ones.
+
+
+After a year using Godot, I just now learn that these can be clicked. This is not properly shown in the design, it is flat and looks like a title, causing much confusion for anyone who doesn't know otherwise.
+
+Other interactive elements in the editor are coloured differently, hinting at their press-able qualities. Just do that for those too. Important tools are hidden behind these invisible drop-downs.
+Just like this :
+
+And then no more confusion, everything is clear. Just make it the same as other similar buttons.
+",1,some drop down menus are hard to notice godot version stable issue description some drop down menus do not look like menus the name of the node in the inspector the tilemap at the top of the tilemap bar those ones after a year using godot i just now learn that these can be clicked this is not properly shown in the design it is flat and looks like a title causing much confusion for anyone who doesn t know otherwise other interactive elements in the editor are coloured differently hinting at their press able qualities just do that for those too important tools are hidden behind these invisible drop downs just like this and then no more confusion everything is clear just make it the same as other similar buttons ,1
+11517,7274532134.0,IssuesEvent,2018-02-21 10:20:14,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,The camera2D smoothing is always active even the Enabled is switching off,bug junior job topic:core usability,"
+The camera2D is always smoothing even the toggled is off, i can only set speed to 0 for terminating the camera smoothing",True,"The camera2D smoothing is always active even the Enabled is switching off - 
+The camera2D is always smoothing even the toggled is off, i can only set speed to 0 for terminating the camera smoothing",1,the smoothing is always active even the enabled is switching off the is always smoothing even the toggled is off i can only set speed to for terminating the camera smoothing,1
+19831,14617694443.0,IssuesEvent,2020-12-22 15:08:48,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,"Better name for ""Makes sure the objects children are not selectable"" + tooltip info",enhancement topic:editor usability,"Godot version: 3.0.4 stable
+OS/device including version: Win7
+
+Issue description:
+I've tried to assign the ""Makes sure the objects children are not selectable"" ui button a keyboard key.
+But I can't find it under editor setting -> shortcuts:
+
+
+How about disable child object movement or restrict object/node movement?
+Also it's used soooo much it needs a keyboard key and an easy way to find it.
+Here is how krita and almost every software does this:
+
+
+When hovering above an element/button there is a short description name, the shortkey is shown inside () and the user can find it without any problems to change the button if needed.
+
+This tooltip information is very very important I can't believe you haven't done this already.
+
+
+
+
+
+Steps to reproduce:
+Use the editor
+",True,"Better name for ""Makes sure the objects children are not selectable"" + tooltip info - Godot version: 3.0.4 stable
+OS/device including version: Win7
+
+Issue description:
+I've tried to assign the ""Makes sure the objects children are not selectable"" ui button a keyboard key.
+But I can't find it under editor setting -> shortcuts:
+
+
+How about disable child object movement or restrict object/node movement?
+Also it's used soooo much it needs a keyboard key and an easy way to find it.
+Here is how krita and almost every software does this:
+
+
+When hovering above an element/button there is a short description name, the shortkey is shown inside () and the user can find it without any problems to change the button if needed.
+
+This tooltip information is very very important I can't believe you haven't done this already.
+
+
+
+
+
+Steps to reproduce:
+Use the editor
+",1,better name for makes sure the objects children are not selectable tooltip info godot version stable os device including version issue description i ve tried to assign the makes sure the objects children are not selectable ui button a keyboard key but i can t find it under editor setting shortcuts how about disable child object movement or restrict object node movement also it s used soooo much it needs a keyboard key and an easy way to find it here is how krita and almost every software does this when hovering above an element button there is a short description name the shortkey is shown inside and the user can find it without any problems to change the button if needed this tooltip information is very very important i can t believe you haven t done this already steps to reproduce use the editor ,1
+18041,12504958733.0,IssuesEvent,2020-06-02 09:52:32,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Create a way to move all keyframes more easily (E.g Adding a keyframe at the numbers of the TimeLine),feature proposal topic:editor usability,"
+Godot 3.0.2 Stable
+
+Windows 10 Home 64 Bits
+
+**Issue description:**
+I would like to suggest to insert a keyframe in the TimeLine to move all keyframes at same row. Currently you have to drag to select all keyframes, and if you have a lot of keyframes this become troublesome:
+
+
+In DragonBones, a Skeleton Animation 2D tool, you can drag a keyframe at the timeline to move all keyframes of the same row:
+
+
+
+I worked in a long animation on Godot, and this feature would've helped a lot.
+",True,"Create a way to move all keyframes more easily (E.g Adding a keyframe at the numbers of the TimeLine) -
+Godot 3.0.2 Stable
+
+Windows 10 Home 64 Bits
+
+**Issue description:**
+I would like to suggest to insert a keyframe in the TimeLine to move all keyframes at same row. Currently you have to drag to select all keyframes, and if you have a lot of keyframes this become troublesome:
+
+
+In DragonBones, a Skeleton Animation 2D tool, you can drag a keyframe at the timeline to move all keyframes of the same row:
+
+
+
+I worked in a long animation on Godot, and this feature would've helped a lot.
+",1,create a way to move all keyframes more easily e g adding a keyframe at the numbers of the timeline godot stable windows home bits issue description i would like to suggest to insert a keyframe in the timeline to move all keyframes at same row currently you have to drag to select all keyframes and if you have a lot of keyframes this become troublesome in dragonbones a skeleton animation tool you can drag a keyframe at the timeline to move all keyframes of the same row i worked in a long animation on godot and this feature would ve helped a lot ,1
+3547,3485249494.0,IssuesEvent,2015-12-31 03:33:29,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,External resources and subresources are not sorted logically in 2.0 format,bug topic:core usability,"Here is an example of git diff output when converting a 1.1 scene to the 2.0 format:
+
+```
+-
+-
+-
+-
+-
+-
+-
+-
+-
+-
+-
++
++
++
++
++
++
++
++
++
++
++
+```
+
+The ext_resource index seems to be well computed, and I guess the XML scene header should list ext_resource sorted by their index too. The current order does not seem really logical.",True,"External resources and subresources are not sorted logically in 2.0 format - Here is an example of git diff output when converting a 1.1 scene to the 2.0 format:
+
+```
+-
+-
+-
+-
+-
+-
+-
+-
+-
+-
+-
++
++
++
++
++
++
++
++
++
++
++
+```
+
+The ext_resource index seems to be well computed, and I guess the XML scene header should list ext_resource sorted by their index too. The current order does not seem really logical.",1,external resources and subresources are not sorted logically in format here is an example of git diff output when converting a scene to the format the ext resource index seems to be well computed and i guess the xml scene header should list ext resource sorted by their index too the current order does not seem really logical ,1
+69744,22638285457.0,IssuesEvent,2022-06-30 21:32:09,idaholab/raven,https://api.github.com/repos/idaholab/raven,closed,[DEFECT] Documentation does not build on Windows,priority_normal defect,"### Thank you for the defect report
+
+- [X] I am using the latest version of `RAVEN`.
+- [X] I have read the [Wiki](https://github.com/idaholab/raven/wiki).
+- [X] I have created a [minimum, reproducible example](https://stackoverflow.com/help/minimal-reproducible-example)
+that demonstrates the defect.
+
+
+### Defect Description
+
+On Windows, the documentation is not generated when following the process described in the wiki. running the following does not generate the documentation:
+
+`C:\projects\raven\doc> ./make_docs.sh`
+
+### Steps to Reproduce
+
+Running the following does not generate the documentation:
+
+`C:\projects\raven\doc> ./make_docs.sh`
+
+### Expected Behavior
+
+All of the documentation should be built when running:
+
+`C:\projects\raven\doc> ./make_docs.sh`
+
+### Screenshots and Input Files
+
+_No response_
+
+### OS
+
+Windows
+
+### OS Version
+
+![]()
+
+
+### Dependency Manager
+
+CONDA
+
+### For Change Control Board: Issue Review
+
+- [X] Is it tagged with a type: defect or task?
+- [X] Is it tagged with a priority: critical, normal or minor?
+- [X] If it will impact requirements or requirements tests, is it tagged with requirements?
+- [X] If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
+- [X] Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)
+
+### For Change Control Board: Issue Closure
+
+- [x] If the issue is a defect, is the defect fixed?
+- [x] If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
+- [x] If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
+- [x] If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
+- [x] If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?",1.0,"[DEFECT] Documentation does not build on Windows - ### Thank you for the defect report
+
+- [X] I am using the latest version of `RAVEN`.
+- [X] I have read the [Wiki](https://github.com/idaholab/raven/wiki).
+- [X] I have created a [minimum, reproducible example](https://stackoverflow.com/help/minimal-reproducible-example)
+that demonstrates the defect.
+
+
+### Defect Description
+
+On Windows, the documentation is not generated when following the process described in the wiki. running the following does not generate the documentation:
+
+`C:\projects\raven\doc> ./make_docs.sh`
+
+### Steps to Reproduce
+
+Running the following does not generate the documentation:
+
+`C:\projects\raven\doc> ./make_docs.sh`
+
+### Expected Behavior
+
+All of the documentation should be built when running:
+
+`C:\projects\raven\doc> ./make_docs.sh`
+
+### Screenshots and Input Files
+
+_No response_
+
+### OS
+
+Windows
+
+### OS Version
+
+![]()
+
+
+### Dependency Manager
+
+CONDA
+
+### For Change Control Board: Issue Review
+
+- [X] Is it tagged with a type: defect or task?
+- [X] Is it tagged with a priority: critical, normal or minor?
+- [X] If it will impact requirements or requirements tests, is it tagged with requirements?
+- [X] If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
+- [X] Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)
+
+### For Change Control Board: Issue Closure
+
+- [x] If the issue is a defect, is the defect fixed?
+- [x] If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
+- [x] If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
+- [x] If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
+- [x] If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?",0, documentation does not build on windows thank you for the defect report i am using the latest version of raven i have read the i have created a that demonstrates the defect defect description on windows the documentation is not generated when following the process described in the wiki running the following does not generate the documentation c projects raven doc make docs sh steps to reproduce running the following does not generate the documentation c projects raven doc make docs sh expected behavior all of the documentation should be built when running c projects raven doc make docs sh screenshots and input files no response os windows os version img width alt doc error src dependency manager conda for change control board issue review is it tagged with a type defect or task is it tagged with a priority critical normal or minor if it will impact requirements or requirements tests is it tagged with requirements if it is a defect can it cause wrong results for users if so an email needs to be sent to the users is a rationale provided such as explaining why the improvement is needed or why current code is wrong for change control board issue closure if the issue is a defect is the defect fixed if the issue is a defect is the defect tested for in the regression test system if not explain why not if the issue can impact users has an email to the users group been written the email should specify if the defect impacts stable or master if the issue is a defect does it impact the latest release branch if yes is there any issue tagged with release create if needed if the issue is being closed without a pull request has an explanation of why it is being closed been provided ,0
+196457,6928237592.0,IssuesEvent,2017-12-01 03:25:46,kubernetes/kubernetes,https://api.github.com/repos/kubernetes/kubernetes,closed,should support AWS NVMe device,kind/bug milestone/needs-approval priority/critical-urgent sig/aws sig/storage,"**Is this a BUG REPORT or FEATURE REQUEST?**:
+BUG REPORT
+/kind bug
+
+**What happened**:
+AWS NVMe device path starts with `/dev/nvme` according to [doc](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/device_naming.html), it fails aws device probe [here](https://github.com/kubernetes/kubernetes/blob/master/pkg/cloudprovider/providers/aws/aws.go#L1429)
+```go
+ for _, blockDevice := range info.BlockDeviceMappings {
+ name := aws.StringValue(blockDevice.DeviceName)
+ if strings.HasPrefix(name, ""/dev/sd"") {
+ name = name[7:]
+ }
+ if strings.HasPrefix(name, ""/dev/xvd"") {
+ name = name[8:]
+ }
+ if len(name) < 1 || len(name) > 2 {
+ glog.Warningf(""Unexpected EBS DeviceName: %q"", aws.StringValue(blockDevice.DeviceName))
+ }
+ deviceMappings[mountDevice(name)] = awsVolumeID(aws.StringValue(blockDevice.Ebs.VolumeId))
+ }
+```
+
+
+**What you expected to happen**:
+NVMe device should be supported.
+**How to reproduce it (as minimally and precisely as possible)**:
+Code reading
+
+**Anything else we need to know?**:
+@kubernetes/sig-storage-bugs @kubernetes/sig-aws-misc
+
+**Environment**:
+- Kubernetes version (use `kubectl version`):
+- Cloud provider or hardware configuration: AWS
+- OS (e.g. from /etc/os-release):
+- Kernel (e.g. `uname -a`):
+- Install tools:
+- Others:
+",1.0,"should support AWS NVMe device - **Is this a BUG REPORT or FEATURE REQUEST?**:
+BUG REPORT
+/kind bug
+
+**What happened**:
+AWS NVMe device path starts with `/dev/nvme` according to [doc](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/device_naming.html), it fails aws device probe [here](https://github.com/kubernetes/kubernetes/blob/master/pkg/cloudprovider/providers/aws/aws.go#L1429)
+```go
+ for _, blockDevice := range info.BlockDeviceMappings {
+ name := aws.StringValue(blockDevice.DeviceName)
+ if strings.HasPrefix(name, ""/dev/sd"") {
+ name = name[7:]
+ }
+ if strings.HasPrefix(name, ""/dev/xvd"") {
+ name = name[8:]
+ }
+ if len(name) < 1 || len(name) > 2 {
+ glog.Warningf(""Unexpected EBS DeviceName: %q"", aws.StringValue(blockDevice.DeviceName))
+ }
+ deviceMappings[mountDevice(name)] = awsVolumeID(aws.StringValue(blockDevice.Ebs.VolumeId))
+ }
+```
+
+
+**What you expected to happen**:
+NVMe device should be supported.
+**How to reproduce it (as minimally and precisely as possible)**:
+Code reading
+
+**Anything else we need to know?**:
+@kubernetes/sig-storage-bugs @kubernetes/sig-aws-misc
+
+**Environment**:
+- Kubernetes version (use `kubectl version`):
+- Cloud provider or hardware configuration: AWS
+- OS (e.g. from /etc/os-release):
+- Kernel (e.g. `uname -a`):
+- Install tools:
+- Others:
+",0,should support aws nvme device is this a bug report or feature request bug report kind bug what happened aws nvme device path starts with dev nvme according to it fails aws device probe go for blockdevice range info blockdevicemappings name aws stringvalue blockdevice devicename if strings hasprefix name dev sd name name if strings hasprefix name dev xvd name name if len name glog warningf unexpected ebs devicename q aws stringvalue blockdevice devicename devicemappings awsvolumeid aws stringvalue blockdevice ebs volumeid what you expected to happen nvme device should be supported how to reproduce it as minimally and precisely as possible code reading anything else we need to know kubernetes sig storage bugs kubernetes sig aws misc environment kubernetes version use kubectl version cloud provider or hardware configuration aws os e g from etc os release kernel e g uname a install tools others ,0
+66917,16751456037.0,IssuesEvent,2021-06-12 00:51:27,spack/spack,https://api.github.com/repos/spack/spack,opened,Installation issue: mpfr,build-error,"
+
+### Steps to reproduce the issue
+
+
+```console
+$ spack install mpfr
+...
+```
+
+### Information on your system
+
+
+
+
+
+* **Spack:** 0.16.2-3107-177750b215
+* **Python:** 3.8.5
+* **Platform:** linux-ubuntu20.04-westmere
+* **Concretizer:** original
+
+
+### Additional information
+
+
+
+Salient error:
+`/tmp/pytest-of-wspear/pytest-2/mock-stage0/spack-stage-mpfr-4.1.0-6rrd4ugygkcolfme4qt2zq75cmmpc7xk/spack-src/missing: line 81: makeinfo: command not found`
+
+[spack-build-out.txt](https://github.com/spack/spack/files/6641402/spack-build-out.txt)
+[spack-build-env.txt](https://github.com/spack/spack/files/6641403/spack-build-env.txt)
+
+
+
+(No maintainers listed, but the two primary committers on this file.)
+
+@tgamblin
+@adamjstewart
+
+### General information
+
+
+- [x] I have run `spack debug report` and reported the version of Spack/Python/Platform
+- [x] I have run `spack maintainers ` and @mentioned any maintainers
+- [x] I have uploaded the build log and environment files
+- [x] I have searched the issues of this repo and believe this is not a duplicate
+",1.0,"Installation issue: mpfr -
+
+### Steps to reproduce the issue
+
+
+```console
+$ spack install mpfr
+...
+```
+
+### Information on your system
+
+
+
+
+
+* **Spack:** 0.16.2-3107-177750b215
+* **Python:** 3.8.5
+* **Platform:** linux-ubuntu20.04-westmere
+* **Concretizer:** original
+
+
+### Additional information
+
+
+
+Salient error:
+`/tmp/pytest-of-wspear/pytest-2/mock-stage0/spack-stage-mpfr-4.1.0-6rrd4ugygkcolfme4qt2zq75cmmpc7xk/spack-src/missing: line 81: makeinfo: command not found`
+
+[spack-build-out.txt](https://github.com/spack/spack/files/6641402/spack-build-out.txt)
+[spack-build-env.txt](https://github.com/spack/spack/files/6641403/spack-build-env.txt)
+
+
+
+(No maintainers listed, but the two primary committers on this file.)
+
+@tgamblin
+@adamjstewart
+
+### General information
+
+
+- [x] I have run `spack debug report` and reported the version of Spack/Python/Platform
+- [x] I have run `spack maintainers ` and @mentioned any maintainers
+- [x] I have uploaded the build log and environment files
+- [x] I have searched the issues of this repo and believe this is not a duplicate
+",0,installation issue mpfr thanks for taking the time to report this build failure to proceed with the report please title the issue installation issue provide the information required below we encourage you to try as much as possible to reduce your problem to the minimal example that still reproduces the issue that would help us a lot in fixing it quickly and effectively steps to reproduce the issue console spack install mpfr information on your system spack python platform linux westmere concretizer original additional information salient error tmp pytest of wspear pytest mock spack stage mpfr spack src missing line makeinfo command not found and mention them here if they exist no maintainers listed but the two primary committers on this file tgamblin adamjstewart general information i have run spack debug report and reported the version of spack python platform i have run spack maintainers and mentioned any maintainers i have uploaded the build log and environment files i have searched the issues of this repo and believe this is not a duplicate ,0
+209424,23720779551.0,IssuesEvent,2022-08-30 15:10:40,IMA-WorldHealth/bhima,https://api.github.com/repos/IMA-WorldHealth/bhima,opened,Improve error handling for stock exits for shipments,Bug security Stock,"If a user tries to do a stock exit for shipment there a couple of problems:
+
+- Assume the ""Activate the restriction of distribution depots"" flag in the stock settings is set to YES, and the user does NOT have permissions to access the destination depot. When that user tries to do a stock exit for that shipment, clicks on YES for the ""Do you have a shipment ready"" item in the depot selection modal, they will be able to select the shipment but the depot will not be filled in since they do not have permissions. A warning is needed to communicate that to the user.
+- If one does a stock exit for a shipment from the Shipments Registry action menu, it works regardless of the permission of the user. The code for that needs to be updated to respect the ""Activate the restriction of distribution depots"" flag.
+
+See also https://github.com/IMA-WorldHealth/bhima/issues/6793",True,"Improve error handling for stock exits for shipments - If a user tries to do a stock exit for shipment there a couple of problems:
+
+- Assume the ""Activate the restriction of distribution depots"" flag in the stock settings is set to YES, and the user does NOT have permissions to access the destination depot. When that user tries to do a stock exit for that shipment, clicks on YES for the ""Do you have a shipment ready"" item in the depot selection modal, they will be able to select the shipment but the depot will not be filled in since they do not have permissions. A warning is needed to communicate that to the user.
+- If one does a stock exit for a shipment from the Shipments Registry action menu, it works regardless of the permission of the user. The code for that needs to be updated to respect the ""Activate the restriction of distribution depots"" flag.
+
+See also https://github.com/IMA-WorldHealth/bhima/issues/6793",0,improve error handling for stock exits for shipments if a user tries to do a stock exit for shipment there a couple of problems assume the activate the restriction of distribution depots flag in the stock settings is set to yes and the user does not have permissions to access the destination depot when that user tries to do a stock exit for that shipment clicks on yes for the do you have a shipment ready item in the depot selection modal they will be able to select the shipment but the depot will not be filled in since they do not have permissions a warning is needed to communicate that to the user if one does a stock exit for a shipment from the shipments registry action menu it works regardless of the permission of the user the code for that needs to be updated to respect the activate the restriction of distribution depots flag see also ,0
+118670,15352815060.0,IssuesEvent,2021-03-01 07:39:17,CSCfi/metadata-submitter-frontend,https://api.github.com/repos/CSCfi/metadata-submitter-frontend,opened,Tackle Design issues,design,"#### Description
+
+
+
+Something that should be done with or before: https://github.com/CSCfi/metadata-submitter-frontend/issues/105
+It is also advisable to fix this properly to have uniform style guide.
+
+There are several issues with current design that we need to consider to make the application look and feel better:
+- `Create submission` vs `Create New folder` - button label vs wizard label don't correspond - e.g. `Submission` sounds better (as folder is part of a submission), and maybe reflect in the 2nd step of the wizard the name of the submission (by the name of the folder)
+
+- Links at the top point nowhere (submissions and Open submissions point nowhere and should point to submitted/published folders and draft folders)
+- Spacing between list of objects, form and list of submitted objects is odd, moreover title of the `fill form`, `upload xml file` and `choose from drafts` are inconsistent
+
+
+- objects list needs a new design both colors and highlighting elements as well as icons and small improvements such as the first element of the list does not need a border top
+
+- form buttons don't fit with the other buttons used in the application. Figure out a uniform button design to use:
+
+- subtitles are not visible, make them visible:
+
+- Some of the form elements are not correctly positioned (that part of the form does not expand full length it has available or at least if more contacts are added they should be added to the right not underneath ) also noticed the check box being too close to edge:
+
+- Other check boxes are not properly aligned:
+
+- Policy List of modifiers needs a new design as currently it does not display properly
+
+- make required fields more visible, as currently just a `*` is not enough
+- Drafts badge on each object is not 100% clear what it is about, consider showing maybe also 2 badges one for drafts and one for submitted objects or show just a badge for submitted objects and show a badge for drafts near `choose from drafts`
+
+
+
+Pretty sure there are other issues,
+
+#### DoD (Definition of Done)
+
+
+Fix design issues.
+
+#### Testing
+
+
+peer review and tests if possible.",1.0,"Tackle Design issues - #### Description
+
+
+
+Something that should be done with or before: https://github.com/CSCfi/metadata-submitter-frontend/issues/105
+It is also advisable to fix this properly to have uniform style guide.
+
+There are several issues with current design that we need to consider to make the application look and feel better:
+- `Create submission` vs `Create New folder` - button label vs wizard label don't correspond - e.g. `Submission` sounds better (as folder is part of a submission), and maybe reflect in the 2nd step of the wizard the name of the submission (by the name of the folder)
+
+- Links at the top point nowhere (submissions and Open submissions point nowhere and should point to submitted/published folders and draft folders)
+- Spacing between list of objects, form and list of submitted objects is odd, moreover title of the `fill form`, `upload xml file` and `choose from drafts` are inconsistent
+
+
+- objects list needs a new design both colors and highlighting elements as well as icons and small improvements such as the first element of the list does not need a border top
+
+- form buttons don't fit with the other buttons used in the application. Figure out a uniform button design to use:
+
+- subtitles are not visible, make them visible:
+
+- Some of the form elements are not correctly positioned (that part of the form does not expand full length it has available or at least if more contacts are added they should be added to the right not underneath ) also noticed the check box being too close to edge:
+
+- Other check boxes are not properly aligned:
+
+- Policy List of modifiers needs a new design as currently it does not display properly
+
+- make required fields more visible, as currently just a `*` is not enough
+- Drafts badge on each object is not 100% clear what it is about, consider showing maybe also 2 badges one for drafts and one for submitted objects or show just a badge for submitted objects and show a badge for drafts near `choose from drafts`
+
+
+
+Pretty sure there are other issues,
+
+#### DoD (Definition of Done)
+
+
+Fix design issues.
+
+#### Testing
+
+
+peer review and tests if possible.",0,tackle design issues description something that should be done with or before it is also advisable to fix this properly to have uniform style guide there are several issues with current design that we need to consider to make the application look and feel better create submission vs create new folder button label vs wizard label don t correspond e g submission sounds better as folder is part of a submission and maybe reflect in the step of the wizard the name of the submission by the name of the folder links at the top point nowhere submissions and open submissions point nowhere and should point to submitted published folders and draft folders spacing between list of objects form and list of submitted objects is odd moreover title of the fill form upload xml file and choose from drafts are inconsistent objects list needs a new design both colors and highlighting elements as well as icons and small improvements such as the first element of the list does not need a border top form buttons don t fit with the other buttons used in the application figure out a uniform button design to use subtitles are not visible make them visible some of the form elements are not correctly positioned that part of the form does not expand full length it has available or at least if more contacts are added they should be added to the right not underneath also noticed the check box being too close to edge other check boxes are not properly aligned policy list of modifiers needs a new design as currently it does not display properly make required fields more visible as currently just a is not enough drafts badge on each object is not clear what it is about consider showing maybe also badges one for drafts and one for submitted objects or show just a badge for submitted objects and show a badge for drafts near choose from drafts pretty sure there are other issues dod definition of done fix design issues testing peer review and tests if possible ,0
+10429,6718925944.0,IssuesEvent,2017-10-15 18:24:45,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,"export (float,min,max) clamps float to int",enhancement hacktoberfest topic:editor usability,"This issue: #539 still happens in godot 2.1.4.
+
+Code that I am using is:
+export(float, -100, 100) var variable = 0.0
+in inspector any number given is then rounded to int.
+
+In future should I comment on closed issue instead opening new one?",True,"export (float,min,max) clamps float to int - This issue: #539 still happens in godot 2.1.4.
+
+Code that I am using is:
+export(float, -100, 100) var variable = 0.0
+in inspector any number given is then rounded to int.
+
+In future should I comment on closed issue instead opening new one?",1,export float min max clamps float to int this issue still happens in godot code that i am using is export float var variable in inspector any number given is then rounded to int in future should i comment on closed issue instead opening new one ,1
+23596,22304360329.0,IssuesEvent,2022-06-13 11:41:56,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Animation editor creating only one track when multiple node are selected,bug topic:editor usability topic:animation,"### Godot version
+
+v4.0.alpha.custom_build [b9375ea7f]
+
+### System information
+
+MacOS
+
+### Issue description
+
+When multiple nodes are selected inserting a key creates tracks only for the node that was clicked last
+
+### Steps to reproduce
+
+Select a multiple nodes and try to create animation tracks for all
+
+### Minimal reproduction project
+
+_No response_
+
+*Bugsquad edit (keywords for easier searching): MultiNodeEdit*",True,"Animation editor creating only one track when multiple node are selected - ### Godot version
+
+v4.0.alpha.custom_build [b9375ea7f]
+
+### System information
+
+MacOS
+
+### Issue description
+
+When multiple nodes are selected inserting a key creates tracks only for the node that was clicked last
+
+### Steps to reproduce
+
+Select a multiple nodes and try to create animation tracks for all
+
+### Minimal reproduction project
+
+_No response_
+
+*Bugsquad edit (keywords for easier searching): MultiNodeEdit*",1,animation editor creating only one track when multiple node are selected godot version alpha custom build system information macos issue description when multiple nodes are selected inserting a key creates tracks only for the node that was clicked last steps to reproduce select a multiple nodes and try to create animation tracks for all minimal reproduction project no response bugsquad edit keywords for easier searching multinodeedit ,1
+15825,10317153971.0,IssuesEvent,2019-08-30 11:58:39,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Inspector dock changes size when selected,bug confirmed topic:editor usability,"
+
+**Godot version:**
+ 5b5db08
+
+
+**Issue description:**
+When clicking the Inspector dock, it will change its size. It only affects this dock alone, no matter its current location:
+",True,"Inspector dock changes size when selected -
+
+**Godot version:**
+ 5b5db08
+
+
+**Issue description:**
+When clicking the Inspector dock, it will change its size. It only affects this dock alone, no matter its current location:
+",1,inspector dock changes size when selected please search existing issues for potential duplicates before filing yours godot version issue description when clicking the inspector dock it will change its size it only affects this dock alone no matter its current location ,1
+13093,8251903517.0,IssuesEvent,2018-09-12 09:13:37,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Can't select child node by clicking on viewport,bug topic:editor usability,"
+
+**Godot version:**
+
+3.1.dev cb7fe2c79
+
+**OS/device including version:**
+
+
+
+**Issue description:**
+
+Can't select child node by clicking node on viewport when parent node is selected.
+it works fine with 3.0.2-official
+
+**Steps to reproduce:**
+
+[3.0.2-official]
+
+
+[3.1.dev]
+
+**Minimal reproduction project:**
+
+",True,"Can't select child node by clicking on viewport -
+
+**Godot version:**
+
+3.1.dev cb7fe2c79
+
+**OS/device including version:**
+
+
+
+**Issue description:**
+
+Can't select child node by clicking node on viewport when parent node is selected.
+it works fine with 3.0.2-official
+
+**Steps to reproduce:**
+
+[3.0.2-official]
+
+
+[3.1.dev]
+
+**Minimal reproduction project:**
+
+",1,can t select child node by clicking on viewport please search existing issues for potential duplicates before filing yours godot version dev os device including version issue description can t select child node by clicking node on viewport when parent node is selected it works fine with official steps to reproduce minimal reproduction project ,1
+591469,17840647223.0,IssuesEvent,2021-09-03 09:37:35,cloudskiff/driftctl,https://api.github.com/repos/cloudskiff/driftctl,closed,Display resource source in JSON output,priority/3 kind/maintenance,"**Description**
+We want to display resource source in JSON output
+
+**Example**
+```json
+""differences"": [
+ {
+ ""res"": {
+ ""id"": ""diff-id-1"",
+ ""type"": ""aws_diff_resource"",
+ ""source"": {
+ ""module"": ""module.dev_dynamodb_from_omaha_role"",
+ ""name"": ""main"",
+ ""state"": ""s3://terraform-state-bucket/accounts/foo.tfstate""
+ },
+ },
+```
+
+
+Blocked by https://github.com/cloudskiff/driftctl/issues/873",1.0,"Display resource source in JSON output - **Description**
+We want to display resource source in JSON output
+
+**Example**
+```json
+""differences"": [
+ {
+ ""res"": {
+ ""id"": ""diff-id-1"",
+ ""type"": ""aws_diff_resource"",
+ ""source"": {
+ ""module"": ""module.dev_dynamodb_from_omaha_role"",
+ ""name"": ""main"",
+ ""state"": ""s3://terraform-state-bucket/accounts/foo.tfstate""
+ },
+ },
+```
+
+
+Blocked by https://github.com/cloudskiff/driftctl/issues/873",0,display resource source in json output description we want to display resource source in json output example json differences res id diff id type aws diff resource source module module dev dynamodb from omaha role name main state terraform state bucket accounts foo tfstate blocked by ,0
+19775,14539518607.0,IssuesEvent,2020-12-15 12:00:17,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Default color for ruler text with light theme to dark,bug topic:editor usability,"**Godot version:**
+v3.2.3.stable
+
+**OS/device including version:**
+Windows 10
+
+**Issue description:**
+The text for the ruler position with light theme is nearly invisible. It needs an other default color.
+
+**Steps to reproduce:**
+Switch to light theme, open a new empty scene, move the ruler and look at the ruler text.
+
+
+related to #33523?",True,"Default color for ruler text with light theme to dark - **Godot version:**
+v3.2.3.stable
+
+**OS/device including version:**
+Windows 10
+
+**Issue description:**
+The text for the ruler position with light theme is nearly invisible. It needs an other default color.
+
+**Steps to reproduce:**
+Switch to light theme, open a new empty scene, move the ruler and look at the ruler text.
+
+
+related to #33523?",1,default color for ruler text with light theme to dark godot version stable os device including version windows issue description the text for the ruler position with light theme is nearly invisible it needs an other default color steps to reproduce switch to light theme open a new empty scene move the ruler and look at the ruler text related to ,1
+26714,4240721449.0,IssuesEvent,2016-07-06 14:18:40,part-up/part-up,https://api.github.com/repos/part-up/part-up,closed,Mixed content warning in browser,Acceptance test output bug chat,"On android you now get a 'not safe warning' in the browser. Looking at the js console, I see a mixed content warning (see example below).
+
+chrome-extension://fdjamakpfbbddfjaooikfcpapjohcfmg/content/contentScripts/kwift.CHROME.min.js:1 Mixed Content: The page at 'https://part-up.com/tribes/swarmorganizing/chat' was loaded over HTTPS, but requested an insecure image 'http://www.newworldcampus.nl/wp-content/uploads/logo-nwc.png'. This content should also be served over HTTPS.",1.0,"Mixed content warning in browser - On android you now get a 'not safe warning' in the browser. Looking at the js console, I see a mixed content warning (see example below).
+
+chrome-extension://fdjamakpfbbddfjaooikfcpapjohcfmg/content/contentScripts/kwift.CHROME.min.js:1 Mixed Content: The page at 'https://part-up.com/tribes/swarmorganizing/chat' was loaded over HTTPS, but requested an insecure image 'http://www.newworldcampus.nl/wp-content/uploads/logo-nwc.png'. This content should also be served over HTTPS.",0,mixed content warning in browser on android you now get a not safe warning in the browser looking at the js console i see a mixed content warning see example below chrome extension fdjamakpfbbddfjaooikfcpapjohcfmg content contentscripts kwift chrome min js mixed content the page at was loaded over https but requested an insecure image this content should also be served over https ,0
+40721,10140876248.0,IssuesEvent,2019-08-03 08:31:04,STEllAR-GROUP/hpx,https://api.github.com/repos/STEllAR-GROUP/hpx,closed,Refine `hpx::traits::is_bitwise_serializable`,category: serialization tag: wontfix type: defect,"`hpx::traits::is_bitwise_serializable` should be defined in terms of `std::is_trivially_copyable`. After merging #2152 some compilers had problems with that. We need to investigate further.
+",1.0,"Refine `hpx::traits::is_bitwise_serializable` - `hpx::traits::is_bitwise_serializable` should be defined in terms of `std::is_trivially_copyable`. After merging #2152 some compilers had problems with that. We need to investigate further.
+",0,refine hpx traits is bitwise serializable hpx traits is bitwise serializable should be defined in terms of std is trivially copyable after merging some compilers had problems with that we need to investigate further ,0
+523507,15184012680.0,IssuesEvent,2021-02-15 08:59:02,webcompat/web-bugs,https://api.github.com/repos/webcompat/web-bugs,closed,www.zee5.com - see bug description,browser-fenix engine-gecko ml-needsdiagnosis-false ml-probability-high priority-normal,"
+
+
+
+
+
+**URL**: https://www.zee5.com/tvshows/details/comedy-khiladigalu-championship-season-2/0-6-2871/comedy-khiladigalu-championship-season-2-february-06-2021/0-1-manual_7aoquorrgbd0
+
+**Browser / Version**: Firefox Mobile 87.0
+**Operating System**: Android 10
+**Tested Another Browser**: No
+
+**Problem type**: Something else
+**Description**: shows a warning to update the app when video starts to play
+**Steps to Reproduce**:
+When video starts to play, it shows update the app to continue
+
+
+Browser Configuration
+
+ - gfx.webrender.all: false
- gfx.webrender.blob-images: true
- gfx.webrender.enabled: false
- image.mem.shared: true
- buildID: 20210211092822
- channel: nightly
- hasTouchScreen: true
- mixed active content blocked: false
- mixed passive content blocked: false
- tracking content blocked: false
+
+
+
+_From [webcompat.com](https://webcompat.com/) with ❤️_",1.0,"www.zee5.com - see bug description -
+
+
+
+
+
+**URL**: https://www.zee5.com/tvshows/details/comedy-khiladigalu-championship-season-2/0-6-2871/comedy-khiladigalu-championship-season-2-february-06-2021/0-1-manual_7aoquorrgbd0
+
+**Browser / Version**: Firefox Mobile 87.0
+**Operating System**: Android 10
+**Tested Another Browser**: No
+
+**Problem type**: Something else
+**Description**: shows a warning to update the app when video starts to play
+**Steps to Reproduce**:
+When video starts to play, it shows update the app to continue
+
+
+Browser Configuration
+
+ - gfx.webrender.all: false
- gfx.webrender.blob-images: true
- gfx.webrender.enabled: false
- image.mem.shared: true
- buildID: 20210211092822
- channel: nightly
- hasTouchScreen: true
- mixed active content blocked: false
- mixed passive content blocked: false
- tracking content blocked: false
+
+
+
+_From [webcompat.com](https://webcompat.com/) with ❤️_",0, see bug description url browser version firefox mobile operating system android tested another browser no problem type something else description shows a warning to update the app when video starts to play steps to reproduce when video starts to play it shows update the app to continue browser configuration gfx webrender all false gfx webrender blob images true gfx webrender enabled false image mem shared true buildid channel nightly hastouchscreen true mixed active content blocked false mixed passive content blocked false tracking content blocked false from with ❤️ ,0
+62823,14656623608.0,IssuesEvent,2020-12-28 13:50:23,fu1771695yongxie/react-beautiful-dnd,https://api.github.com/repos/fu1771695yongxie/react-beautiful-dnd,opened,CVE-2020-7789 (Medium) detected in node-notifier-6.0.0.tgz,security vulnerability,"## CVE-2020-7789 - Medium Severity Vulnerability
+ Vulnerable Library - node-notifier-6.0.0.tgz
+
+A Node.js module for sending notifications on native Mac, Windows (post and pre 8) and Linux (or Growl as fallback)
+Library home page: https://registry.npmjs.org/node-notifier/-/node-notifier-6.0.0.tgz
+Path to dependency file: react-beautiful-dnd/package.json
+Path to vulnerable library: react-beautiful-dnd/node_modules/node-notifier/package.json
+
+
+Dependency Hierarchy:
+ - jest-25.5.4.tgz (Root Library)
+ - core-25.5.4.tgz
+ - reporters-25.5.1.tgz
+ - :x: **node-notifier-6.0.0.tgz** (Vulnerable Library)
+
Found in HEAD commit: 1b8fdade31513b58c89ac3536c50f4e9f6976477
+Found in base branch: master
+
+ Vulnerability Details
+
+
+This affects the package node-notifier before 9.0.0. It allows an attacker to run arbitrary commands on Linux machines due to the options params not being sanitised when being passed an array.
+
+
Publish Date: 2020-12-11
+
URL: CVE-2020-7789
+
+ CVSS 3 Score Details (5.6)
+
+
+Base Score Metrics:
+- Exploitability Metrics:
+ - Attack Vector: Network
+ - Attack Complexity: High
+ - Privileges Required: None
+ - User Interaction: None
+ - Scope: Unchanged
+- Impact Metrics:
+ - Confidentiality Impact: Low
+ - Integrity Impact: Low
+ - Availability Impact: Low
+
+For more information on CVSS3 Scores, click here.
+
+ Suggested Fix
+
+
+
Type: Upgrade version
+Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7789
+Release Date: 2020-12-11
+Fix Resolution: 9.0.0
+
+
+ Vulnerable Library - node-notifier-6.0.0.tgz
+
+A Node.js module for sending notifications on native Mac, Windows (post and pre 8) and Linux (or Growl as fallback)
+Library home page: https://registry.npmjs.org/node-notifier/-/node-notifier-6.0.0.tgz
+Path to dependency file: react-beautiful-dnd/package.json
+Path to vulnerable library: react-beautiful-dnd/node_modules/node-notifier/package.json
+
+
+Dependency Hierarchy:
+ - jest-25.5.4.tgz (Root Library)
+ - core-25.5.4.tgz
+ - reporters-25.5.1.tgz
+ - :x: **node-notifier-6.0.0.tgz** (Vulnerable Library)
+
Found in HEAD commit: 1b8fdade31513b58c89ac3536c50f4e9f6976477
+Found in base branch: master
+
+ Vulnerability Details
+
+
+This affects the package node-notifier before 9.0.0. It allows an attacker to run arbitrary commands on Linux machines due to the options params not being sanitised when being passed an array.
+
+
Publish Date: 2020-12-11
+
URL: CVE-2020-7789
+
+ CVSS 3 Score Details (5.6)
+
+
+Base Score Metrics:
+- Exploitability Metrics:
+ - Attack Vector: Network
+ - Attack Complexity: High
+ - Privileges Required: None
+ - User Interaction: None
+ - Scope: Unchanged
+- Impact Metrics:
+ - Confidentiality Impact: Low
+ - Integrity Impact: Low
+ - Availability Impact: Low
+
+For more information on CVSS3 Scores, click here.
+
+ Suggested Fix
+
+
+
Type: Upgrade version
+Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7789
+Release Date: 2020-12-11
+Fix Resolution: 9.0.0
+
+
+
+Browser Configuration
+
+
+
+
+_From [webcompat.com](https://webcompat.com/) with ❤️_",1.0,"www.google.com - video or audio doesn't play -
+
+
+
+**URL**: http://www.google.com
+
+**Browser / Version**: Chrome 72
+**Operating System**: Windows 11
+**Tested Another Browser**: Yes
+
+**Problem type**: Video or audio doesn't play
+**Description**: test
+**Steps to Reproduce**:
+steps
+
+
+Browser Configuration
+
+
+
+
+_From [webcompat.com](https://webcompat.com/) with ❤️_",0, video or audio doesn t play url browser version chrome operating system windows tested another browser yes problem type video or audio doesn t play description test steps to reproduce steps browser configuration none from with ❤️ ,0
+337253,24532272678.0,IssuesEvent,2022-10-11 17:28:47,OceanParcels/parcels,https://api.github.com/repos/OceanParcels/parcels,closed,[OVERVIEW] Follow-up issues from particle-particle interaction,documentation particle-particle interaction,"Please process / integrate this list of follow-up issues of particle-particle interaction in-order.
+
+1. [x] Fix smalldt - longruntime issue (#1055 )
+2. [ ] Handle State, Operation and Error codes in InteractionKernels (#1056 )
+3. [x] ~~Implement InteractionKernels for JIT on SoA (#1057 )~~
+4. [x] ~~Implement InteractionKernels for JIT and SciPy on AoS (#1058 )~~
+5. [x] ~~Implement InteractionKernels for JIT and SciPy on Nodes (#1059 )~~
+6. [x] ~~Implement MPI support for InteractionKernels (#1060 )~~
+7. [ ] Expand tests to cases for interaction kernels (#1061 )
+8. [ ] Jupyter notebook examples for InteractionKernel (#1062 ) ",1.0,"[OVERVIEW] Follow-up issues from particle-particle interaction - Please process / integrate this list of follow-up issues of particle-particle interaction in-order.
+
+1. [x] Fix smalldt - longruntime issue (#1055 )
+2. [ ] Handle State, Operation and Error codes in InteractionKernels (#1056 )
+3. [x] ~~Implement InteractionKernels for JIT on SoA (#1057 )~~
+4. [x] ~~Implement InteractionKernels for JIT and SciPy on AoS (#1058 )~~
+5. [x] ~~Implement InteractionKernels for JIT and SciPy on Nodes (#1059 )~~
+6. [x] ~~Implement MPI support for InteractionKernels (#1060 )~~
+7. [ ] Expand tests to cases for interaction kernels (#1061 )
+8. [ ] Jupyter notebook examples for InteractionKernel (#1062 ) ",0, follow up issues from particle particle interaction please process integrate this list of follow up issues of particle particle interaction in order fix smalldt longruntime issue handle state operation and error codes in interactionkernels implement interactionkernels for jit on soa implement interactionkernels for jit and scipy on aos implement interactionkernels for jit and scipy on nodes implement mpi support for interactionkernels expand tests to cases for interaction kernels jupyter notebook examples for interactionkernel ,0
+301013,26009643001.0,IssuesEvent,2022-12-20 23:33:08,project-chip/connectedhomeip,https://api.github.com/repos/project-chip/connectedhomeip,closed,[TE-7-Test-Harness] cli.sh available test cases are failing with Google Thermostat,testing stale TE7 cert v1.1,"Trying to use test-harness-7 tool to execute TE-7 test cases related to thermostat.
+
+**Steps followed :
+1. setup test-harness-7 on raspi
+2. Commissioned thermostat using test-harness-7's chip-tool [./chip-tool pairing onnetwork ]
+3. Edited wifi_config and dut_config in test-harness.config file as below.
+ubuntu@matter-te-7:~$ cat test-harness.config**
+{
+ ""logging"": {
+ ""path"": ""./logs"",
+ ""filename"": ""{time:YYYY-MM-DD}.log"",
+ ""level"": ""debug"",
+ ""rotation"": ""20 days"",
+ ""retention"": ""1 months"",
+ ""format"": ""{level: <8} | {time:YYYY-MM-DD HH:mm:ss.SSS} | {name}:{function}:{line} | {message}""
+ },
+ ""notifier"":{
+ ""enable_notifications"": false,
+ ""notifier_config"":{
+ ""username"": ""xiole.chip.test@gmail.com"",
+ ""password"": ""yntwdxwyofvehafg"",
+ ""to"": ""xiole.chip.test@gmail.com"",
+ ""subject"": ""CHIP Tool Crash Log""
+ }
+ },
+ ""network"":{
+ ""fabric_id"":""0"",
+ ""thread"": {
+ ""dataset"": {
+ ""channel"": ""15"",
+ ""panid"": ""0x1234"",
+ ""extpanid"": ""1111111122222222"",
+ ""masterkey"": ""00112233445566778899aabbccddeeff"",
+ ""networkname"": ""DEMO""
+ },
+ ""rcp_serial_path"": ""/dev/ttyACM0"",
+ ""rcp_baudrate"": 115200,
+ ""on_mesh_prefix"": ""fd11:22::/64"",
+ ""network_interface"": ""wlan0""
+ },
+ ""wifi"":{
+ ""ssid"": ""rkreddy"",
+ ""password"": ""adhyareddy""
+ }
+ },
+ ""dut_config"":{
+ ""pairing_mode"":""onnetwork"",
+ ""setup_code"":""12958229"",
+ ""discriminator"":""3840"",
+ ""ip_address"":""10.0.0.245"",
+ ""port"":""5540""
+ }
+}
+
+**4. from $cli, executed TC_DM_1.1 test case and i see below error
+command ---> [./cli.sh run-tests --selected-tests '{""chip_tool_tests"":{""FirstChipToolSuite"":{""TC_DM_1_1"":1}}}']**
+
+**Error**
+INFO | 2021-12-29 22:23:30.766 | Run Test Runner is Ready
+INFO | 2021-12-29 22:23:30.771 | Test Run Executing
+INFO | 2021-12-29 22:23:30.783 | Test Suite Executing: Test Suite run with chip-tool tests
+INFO | 2021-12-29 22:23:30.785 | Setting up chip_tool
+INFO | 2021-12-29 22:25:33.216 | Pair with DUT
+CHIPTOOL | 2021-12-29 22:25:33.218 | [1640816611.365406][8:8] CHIP:CTL: Generating NOC
+CHIPTOOL | 2021-12-29 22:25:33.219 | [1640816611.365756][8:8] CHIP:CTL: Generating ICAC
+CHIPTOOL | 2021-12-29 22:25:33.220 | [1640816611.366031][8:8] CHIP:CTL: Generating RCAC
+CHIPTOOL | 2021-12-29 22:25:33.222 | [1640816611.375033][8:8] CHIP:DL: AUDIT: ===== RANDOM NUMBER GENERATOR AUDIT START ====
+CHIPTOOL | 2021-12-29 22:25:33.223 | [1640816611.375077][8:8] CHIP:DL: AUDIT: * Validate buf1 and buf2 are <<>>
+CHIPTOOL | 2021-12-29 22:25:33.224 | [1640816611.375094][8:8] CHIP:DL: AUDIT: * Validate r1 and r2 are <<>>
+CHIPTOOL | 2021-12-29 22:25:33.226 | [1640816611.375111][8:8] CHIP:DL: AUDIT: * buf1: EC1BFAE170938194B9DD0C5EFE1523A1
+CHIPTOOL | 2021-12-29 22:25:33.228 | [1640816611.375126][8:8] CHIP:DL: AUDIT: * buf2: 7B8FD073A47F01AE4DB0313640184EF1
+CHIPTOOL | 2021-12-29 22:25:33.229 | [1640816611.375195][8:8] CHIP:DL: AUDIT: * r1: 0x6E6E3F1B r2: 0x1D0FA07B
+CHIPTOOL | 2021-12-29 22:25:33.230 | [1640816611.375212][8:8] CHIP:DL: AUDIT: ===== RANDOM NUMBER GENERATOR AUDIT END ====
+CHIPTOOL | 2021-12-29 22:25:33.231 | [1640816611.375671][8:8] CHIP:DL: writing settings to file (/tmp/chip_factory.ini-TpPVnN)
+CHIPTOOL | 2021-12-29 22:25:33.232 | [1640816611.375943][8:8] CHIP:DL: renamed tmp file to file (/tmp/chip_factory.ini)
+CHIPTOOL | 2021-12-29 22:25:33.233 | [1640816611.376364][8:8] CHIP:DL: writing settings to file (/tmp/chip_config.ini-C6VcDO)
+CHIPTOOL | 2021-12-29 22:25:33.234 | [1640816611.376568][8:8] CHIP:DL: renamed tmp file to file (/tmp/chip_config.ini)
+CHIPTOOL | 2021-12-29 22:25:33.236 | [1640816611.376973][8:8] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-lFsXUN)
+CHIPTOOL | 2021-12-29 22:25:33.237 | [1640816611.377170][8:8] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
+CHIPTOOL | 2021-12-29 22:25:33.239 | [1640816611.377510][8:8] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-Kz7SVP)
+CHIPTOOL | 2021-12-29 22:25:33.240 | [1640816611.378126][8:8] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
+CHIPTOOL | 2021-12-29 22:25:33.241 | [1640816611.378188][8:8] CHIP:DL: NVS set: chip-counters/reboot-count = 1 (0x1)
+CHIPTOOL | 2021-12-29 22:25:33.242 | [1640816611.378453][8:8] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-5krcRM)
+CHIPTOOL | 2021-12-29 22:25:33.243 | [1640816611.379111][8:8] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
+CHIPTOOL | 2021-12-29 22:25:33.245 | [1640816611.379179][8:8] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
+CHIPTOOL | 2021-12-29 22:25:33.246 | [1640816611.379481][8:8] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-DBzcoN)
+CHIPTOOL | 2021-12-29 22:25:33.248 | [1640816611.380121][8:8] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
+CHIPTOOL | 2021-12-29 22:25:33.249 | [1640816611.380183][8:8] CHIP:DL: NVS set: chip-counters/boot-reason = 0 (0x0)
+CHIPTOOL | 2021-12-29 22:25:33.250 | [1640816611.381117][8:8] CHIP:DL: Got Ethernet interface: eth0
+CHIPTOOL | 2021-12-29 22:25:33.251 | [1640816611.381718][8:8] CHIP:DL: Found the primary Ethernet interface:eth0
+CHIPTOOL | 2021-12-29 22:25:33.252 | [1640816611.382334][8:8] CHIP:DL: Got WiFi interface: wlan0
+CHIPTOOL | 2021-12-29 22:25:33.254 | [1640816611.384720][8:8] CHIP:DL: Found the primary WiFi interface:wlan0
+CHIPTOOL | 2021-12-29 22:25:33.255 | [1640816611.384796][8:8] CHIP:IN: UDP::Init bind&listen port=5541
+CHIPTOOL | 2021-12-29 22:25:33.256 | [1640816611.384907][8:8] CHIP:IN: UDP::Init bound to port=5541
+CHIPTOOL | 2021-12-29 22:25:33.261 | [1640816611.384935][8:8] CHIP:IN: UDP::Init bind&listen port=5541
+CHIPTOOL | 2021-12-29 22:25:33.263 | [1640816611.385026][8:8] CHIP:IN: UDP::Init bound to port=5541
+CHIPTOOL | 2021-12-29 22:25:33.264 | [1640816611.385043][8:8] CHIP:IN: TransportMgr initialized
+CHIPTOOL | 2021-12-29 22:25:33.265 | [1640816611.385102][8:8] CHIP:DIS: Init fabric pairing table with server storage
+CHIPTOOL | 2021-12-29 22:25:33.267 | [1640816611.385565][8:8] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-nMNKkM)
+CHIPTOOL | 2021-12-29 22:25:33.268 | [1640816611.386256][8:8] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
+CHIPTOOL | 2021-12-29 22:25:33.270 | [1640816611.386315][8:8] CHIP:DL: NVS set: chip-counters/GlobalMCTR = 1000 (0x3E8)
+CHIPTOOL | 2021-12-29 22:25:33.271 | [1640816611.386434][8:8] CHIP:CTL: System State Initialized...
+CHIPTOOL | 2021-12-29 22:25:33.272 | [1640816611.388509][8:8] CHIP:DL: MDNS failed to join multicast group on eth0 for address type IPv4: ../../third_party/connectedhomeip/src/inet/IPEndPointBasis.cpp:387: Inet Error 0x00000110: Address not found
+CHIPTOOL | 2021-12-29 22:25:33.274 | [1640816611.393028][8:8] CHIP:DL: MDNS failed to join multicast group on vethf47a1f6 for address type IPv4: ../../third_party/connectedhomeip/src/inet/IPEndPointBasis.cpp:387: Inet Error 0x00000110: Address not found
+CHIPTOOL | 2021-12-29 22:25:33.275 | [1640816611.394507][8:8] CHIP:DL: MDNS failed to join multicast group on vethff776cf for address type IPv4: ../../third_party/connectedhomeip/src/inet/IPEndPointBasis.cpp:387: Inet Error 0x00000110: Address not found
+CHIPTOOL | 2021-12-29 22:25:33.277 | [1640816611.396022][8:8] CHIP:DL: MDNS failed to join multicast group on veth2d9a590 for address type IPv4: ../../third_party/connectedhomeip/src/inet/IPEndPointBasis.cpp:387: Inet Error 0x00000110: Address not found
+CHIPTOOL | 2021-12-29 22:25:33.278 | [1640816611.397499][8:8] CHIP:DL: MDNS failed to join multicast group on vethd1c4227 for address type IPv4: ../../third_party/connectedhomeip/src/inet/IPEndPointBasis.cpp:387: Inet Error 0x00000110: Address not found
+CHIPTOOL | 2021-12-29 22:25:33.280 | [1640816611.397668][8:8] CHIP:ZCL: Using ZAP configuration...
+CHIPTOOL | 2021-12-29 22:25:33.281 | [1640816611.398348][8:8] CHIP:DIS: Verifying the received credentials
+CHIPTOOL | 2021-12-29 22:25:33.282 | [1640816611.400526][8:8] CHIP:DIS: Added new fabric at index: 1, Initialized: 1
+CHIPTOOL | 2021-12-29 22:25:33.283 | [1640816611.400568][8:8] CHIP:DIS: Assigned compressed fabric ID: 0x702D544ABC90021B, node ID: 0x000000000001B669
+CHIPTOOL | 2021-12-29 22:25:33.284 | [1640816611.400585][8:8] CHIP:CTL: Joined the fabric at index 1. Compressed fabric ID is: 0x702D544ABC90021B
+CHIPTOOL | 2021-12-29 22:25:33.285 | [1640816611.400943][8:18] CHIP:DL: CHIP task running
+CHIPTOOL | 2021-12-29 22:25:33.287 | [1640816611.401276][8:18] CHIP:DIS: Attempt to mDNS broadcast failed: ../../third_party/connectedhomeip/src/inet/IPEndPointBasis.cpp:687: OS Error 0x02000065: Network is unreachable
+CHIPTOOL | 2021-12-29 22:25:33.288 | [1640816611.402199][8:18] CHIP:DIS: Attempt to mDNS broadcast failed: ../../third_party/connectedhomeip/src/inet/IPEndPointBasis.cpp:687: OS Error 0x02000065: Network is unreachable
+CHIPTOOL | 2021-12-29 22:25:33.289 | [1640816731.401355][8:8] CHIP:-: ../../commands/common/CHIPCommand.cpp:125: CHIP Error 0x00000032: Timeout at ../../commands/common/CHIPCommand.cpp:84
+CHIPTOOL | 2021-12-29 22:25:33.290 | [1640816731.401441][8:8] CHIP:TOO: Run command failure: ../../commands/common/CHIPCommand.cpp:125: CHIP Error 0x00000032: Timeout
+CHIPTOOL | 2021-12-29 22:25:33.291 | [1640816731.527525][8:8] CHIP:CTL: Shutting down the System State, this will teardown the CHIP Stack
+CHIPTOOL | 2021-12-29 22:25:33.292 | [1640816731.528030][8:8] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-DnBWIO)
+CHIPTOOL | 2021-12-29 22:25:33.293 | [1640816731.528922][8:8] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
+CHIPTOOL | 2021-12-29 22:25:33.297 | [1640816731.529015][8:8] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
+CHIPTOOL | 2021-12-29 22:25:33.298 | [1640816731.529033][8:8] CHIP:DL: Inet Layer shutdown
+CHIPTOOL | 2021-12-29 22:25:33.299 | [1640816731.529500][8:8] CHIP:DL: BLE layer shutdown
+CHIPTOOL | 2021-12-29 22:25:33.300 | [1640816731.529523][8:8] CHIP:DL: System Layer shutdown
+ERROR | 2021-12-29 22:25:33.301 | Test Suite Error: Error occurred during setup of test suite.#FirstChipToolSuite. #Failed to pair with DUT
+INFO | 2021-12-29 22:25:33.345 | Cancel test case
+INFO | 2021-12-29 22:25:33.348 | Cancel test step
+INFO | 2021-12-29 22:25:33.350 | Cancel test step
+INFO | 2021-12-29 22:25:33.352 | Cancel test step
+INFO | 2021-12-29 22:25:33.355 | Cancel test step
+INFO | 2021-12-29 22:25:33.357 | Cancel test step
+INFO | 2021-12-29 22:25:33.359 | Cancel test step
+INFO | 2021-12-29 22:25:33.362 | Cancel test step
+INFO | 2021-12-29 22:25:33.364 | Cancel test step
+INFO | 2021-12-29 22:25:33.366 | Cancel test step
+INFO | 2021-12-29 22:25:33.369 | Cancel test step
+INFO | 2021-12-29 22:25:33.371 | Cancel test step
+INFO | 2021-12-29 22:25:33.373 | Cancel test step
+INFO | 2021-12-29 22:25:33.375 | Cancel test step
+INFO | 2021-12-29 22:25:33.377 | Cancel test step
+INFO | 2021-12-29 22:25:33.380 | Cancel test step
+INFO | 2021-12-29 22:25:33.385 | Cancel test step
+INFO | 2021-12-29 22:25:33.388 | Cancel test step
+INFO | 2021-12-29 22:25:33.390 | Cancel test step
+INFO | 2021-12-29 22:25:33.392 | Cancel test step
+INFO | 2021-12-29 22:25:33.395 | Stopping chip-tool container
+INFO | 2021-12-29 22:25:33.397 | Test Suite Completed [ERROR]: Test Suite run with chip-tool tests
+INFO | 2021-12-29 22:25:33.405 | Test Run Completed [ERROR]
+
+Issue :
+In test-harness.config file under dut_config I don't see these parameters (node_id and pin code) but I see TE-6 supported parameters (setup code, discriminatior, ip address, port).
+Is test-harness should be updated or need any extra parameters to be added?
+",1.0,"[TE-7-Test-Harness] cli.sh available test cases are failing with Google Thermostat - Trying to use test-harness-7 tool to execute TE-7 test cases related to thermostat.
+
+**Steps followed :
+1. setup test-harness-7 on raspi
+2. Commissioned thermostat using test-harness-7's chip-tool [./chip-tool pairing onnetwork ]
+3. Edited wifi_config and dut_config in test-harness.config file as below.
+ubuntu@matter-te-7:~$ cat test-harness.config**
+{
+ ""logging"": {
+ ""path"": ""./logs"",
+ ""filename"": ""{time:YYYY-MM-DD}.log"",
+ ""level"": ""debug"",
+ ""rotation"": ""20 days"",
+ ""retention"": ""1 months"",
+ ""format"": ""{level: <8} | {time:YYYY-MM-DD HH:mm:ss.SSS} | {name}:{function}:{line} | {message}""
+ },
+ ""notifier"":{
+ ""enable_notifications"": false,
+ ""notifier_config"":{
+ ""username"": ""xiole.chip.test@gmail.com"",
+ ""password"": ""yntwdxwyofvehafg"",
+ ""to"": ""xiole.chip.test@gmail.com"",
+ ""subject"": ""CHIP Tool Crash Log""
+ }
+ },
+ ""network"":{
+ ""fabric_id"":""0"",
+ ""thread"": {
+ ""dataset"": {
+ ""channel"": ""15"",
+ ""panid"": ""0x1234"",
+ ""extpanid"": ""1111111122222222"",
+ ""masterkey"": ""00112233445566778899aabbccddeeff"",
+ ""networkname"": ""DEMO""
+ },
+ ""rcp_serial_path"": ""/dev/ttyACM0"",
+ ""rcp_baudrate"": 115200,
+ ""on_mesh_prefix"": ""fd11:22::/64"",
+ ""network_interface"": ""wlan0""
+ },
+ ""wifi"":{
+ ""ssid"": ""rkreddy"",
+ ""password"": ""adhyareddy""
+ }
+ },
+ ""dut_config"":{
+ ""pairing_mode"":""onnetwork"",
+ ""setup_code"":""12958229"",
+ ""discriminator"":""3840"",
+ ""ip_address"":""10.0.0.245"",
+ ""port"":""5540""
+ }
+}
+
+**4. from $cli, executed TC_DM_1.1 test case and i see below error
+command ---> [./cli.sh run-tests --selected-tests '{""chip_tool_tests"":{""FirstChipToolSuite"":{""TC_DM_1_1"":1}}}']**
+
+**Error**
+INFO | 2021-12-29 22:23:30.766 | Run Test Runner is Ready
+INFO | 2021-12-29 22:23:30.771 | Test Run Executing
+INFO | 2021-12-29 22:23:30.783 | Test Suite Executing: Test Suite run with chip-tool tests
+INFO | 2021-12-29 22:23:30.785 | Setting up chip_tool
+INFO | 2021-12-29 22:25:33.216 | Pair with DUT
+CHIPTOOL | 2021-12-29 22:25:33.218 | [1640816611.365406][8:8] CHIP:CTL: Generating NOC
+CHIPTOOL | 2021-12-29 22:25:33.219 | [1640816611.365756][8:8] CHIP:CTL: Generating ICAC
+CHIPTOOL | 2021-12-29 22:25:33.220 | [1640816611.366031][8:8] CHIP:CTL: Generating RCAC
+CHIPTOOL | 2021-12-29 22:25:33.222 | [1640816611.375033][8:8] CHIP:DL: AUDIT: ===== RANDOM NUMBER GENERATOR AUDIT START ====
+CHIPTOOL | 2021-12-29 22:25:33.223 | [1640816611.375077][8:8] CHIP:DL: AUDIT: * Validate buf1 and buf2 are <<>>
+CHIPTOOL | 2021-12-29 22:25:33.224 | [1640816611.375094][8:8] CHIP:DL: AUDIT: * Validate r1 and r2 are <<>>
+CHIPTOOL | 2021-12-29 22:25:33.226 | [1640816611.375111][8:8] CHIP:DL: AUDIT: * buf1: EC1BFAE170938194B9DD0C5EFE1523A1
+CHIPTOOL | 2021-12-29 22:25:33.228 | [1640816611.375126][8:8] CHIP:DL: AUDIT: * buf2: 7B8FD073A47F01AE4DB0313640184EF1
+CHIPTOOL | 2021-12-29 22:25:33.229 | [1640816611.375195][8:8] CHIP:DL: AUDIT: * r1: 0x6E6E3F1B r2: 0x1D0FA07B
+CHIPTOOL | 2021-12-29 22:25:33.230 | [1640816611.375212][8:8] CHIP:DL: AUDIT: ===== RANDOM NUMBER GENERATOR AUDIT END ====
+CHIPTOOL | 2021-12-29 22:25:33.231 | [1640816611.375671][8:8] CHIP:DL: writing settings to file (/tmp/chip_factory.ini-TpPVnN)
+CHIPTOOL | 2021-12-29 22:25:33.232 | [1640816611.375943][8:8] CHIP:DL: renamed tmp file to file (/tmp/chip_factory.ini)
+CHIPTOOL | 2021-12-29 22:25:33.233 | [1640816611.376364][8:8] CHIP:DL: writing settings to file (/tmp/chip_config.ini-C6VcDO)
+CHIPTOOL | 2021-12-29 22:25:33.234 | [1640816611.376568][8:8] CHIP:DL: renamed tmp file to file (/tmp/chip_config.ini)
+CHIPTOOL | 2021-12-29 22:25:33.236 | [1640816611.376973][8:8] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-lFsXUN)
+CHIPTOOL | 2021-12-29 22:25:33.237 | [1640816611.377170][8:8] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
+CHIPTOOL | 2021-12-29 22:25:33.239 | [1640816611.377510][8:8] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-Kz7SVP)
+CHIPTOOL | 2021-12-29 22:25:33.240 | [1640816611.378126][8:8] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
+CHIPTOOL | 2021-12-29 22:25:33.241 | [1640816611.378188][8:8] CHIP:DL: NVS set: chip-counters/reboot-count = 1 (0x1)
+CHIPTOOL | 2021-12-29 22:25:33.242 | [1640816611.378453][8:8] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-5krcRM)
+CHIPTOOL | 2021-12-29 22:25:33.243 | [1640816611.379111][8:8] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
+CHIPTOOL | 2021-12-29 22:25:33.245 | [1640816611.379179][8:8] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
+CHIPTOOL | 2021-12-29 22:25:33.246 | [1640816611.379481][8:8] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-DBzcoN)
+CHIPTOOL | 2021-12-29 22:25:33.248 | [1640816611.380121][8:8] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
+CHIPTOOL | 2021-12-29 22:25:33.249 | [1640816611.380183][8:8] CHIP:DL: NVS set: chip-counters/boot-reason = 0 (0x0)
+CHIPTOOL | 2021-12-29 22:25:33.250 | [1640816611.381117][8:8] CHIP:DL: Got Ethernet interface: eth0
+CHIPTOOL | 2021-12-29 22:25:33.251 | [1640816611.381718][8:8] CHIP:DL: Found the primary Ethernet interface:eth0
+CHIPTOOL | 2021-12-29 22:25:33.252 | [1640816611.382334][8:8] CHIP:DL: Got WiFi interface: wlan0
+CHIPTOOL | 2021-12-29 22:25:33.254 | [1640816611.384720][8:8] CHIP:DL: Found the primary WiFi interface:wlan0
+CHIPTOOL | 2021-12-29 22:25:33.255 | [1640816611.384796][8:8] CHIP:IN: UDP::Init bind&listen port=5541
+CHIPTOOL | 2021-12-29 22:25:33.256 | [1640816611.384907][8:8] CHIP:IN: UDP::Init bound to port=5541
+CHIPTOOL | 2021-12-29 22:25:33.261 | [1640816611.384935][8:8] CHIP:IN: UDP::Init bind&listen port=5541
+CHIPTOOL | 2021-12-29 22:25:33.263 | [1640816611.385026][8:8] CHIP:IN: UDP::Init bound to port=5541
+CHIPTOOL | 2021-12-29 22:25:33.264 | [1640816611.385043][8:8] CHIP:IN: TransportMgr initialized
+CHIPTOOL | 2021-12-29 22:25:33.265 | [1640816611.385102][8:8] CHIP:DIS: Init fabric pairing table with server storage
+CHIPTOOL | 2021-12-29 22:25:33.267 | [1640816611.385565][8:8] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-nMNKkM)
+CHIPTOOL | 2021-12-29 22:25:33.268 | [1640816611.386256][8:8] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
+CHIPTOOL | 2021-12-29 22:25:33.270 | [1640816611.386315][8:8] CHIP:DL: NVS set: chip-counters/GlobalMCTR = 1000 (0x3E8)
+CHIPTOOL | 2021-12-29 22:25:33.271 | [1640816611.386434][8:8] CHIP:CTL: System State Initialized...
+CHIPTOOL | 2021-12-29 22:25:33.272 | [1640816611.388509][8:8] CHIP:DL: MDNS failed to join multicast group on eth0 for address type IPv4: ../../third_party/connectedhomeip/src/inet/IPEndPointBasis.cpp:387: Inet Error 0x00000110: Address not found
+CHIPTOOL | 2021-12-29 22:25:33.274 | [1640816611.393028][8:8] CHIP:DL: MDNS failed to join multicast group on vethf47a1f6 for address type IPv4: ../../third_party/connectedhomeip/src/inet/IPEndPointBasis.cpp:387: Inet Error 0x00000110: Address not found
+CHIPTOOL | 2021-12-29 22:25:33.275 | [1640816611.394507][8:8] CHIP:DL: MDNS failed to join multicast group on vethff776cf for address type IPv4: ../../third_party/connectedhomeip/src/inet/IPEndPointBasis.cpp:387: Inet Error 0x00000110: Address not found
+CHIPTOOL | 2021-12-29 22:25:33.277 | [1640816611.396022][8:8] CHIP:DL: MDNS failed to join multicast group on veth2d9a590 for address type IPv4: ../../third_party/connectedhomeip/src/inet/IPEndPointBasis.cpp:387: Inet Error 0x00000110: Address not found
+CHIPTOOL | 2021-12-29 22:25:33.278 | [1640816611.397499][8:8] CHIP:DL: MDNS failed to join multicast group on vethd1c4227 for address type IPv4: ../../third_party/connectedhomeip/src/inet/IPEndPointBasis.cpp:387: Inet Error 0x00000110: Address not found
+CHIPTOOL | 2021-12-29 22:25:33.280 | [1640816611.397668][8:8] CHIP:ZCL: Using ZAP configuration...
+CHIPTOOL | 2021-12-29 22:25:33.281 | [1640816611.398348][8:8] CHIP:DIS: Verifying the received credentials
+CHIPTOOL | 2021-12-29 22:25:33.282 | [1640816611.400526][8:8] CHIP:DIS: Added new fabric at index: 1, Initialized: 1
+CHIPTOOL | 2021-12-29 22:25:33.283 | [1640816611.400568][8:8] CHIP:DIS: Assigned compressed fabric ID: 0x702D544ABC90021B, node ID: 0x000000000001B669
+CHIPTOOL | 2021-12-29 22:25:33.284 | [1640816611.400585][8:8] CHIP:CTL: Joined the fabric at index 1. Compressed fabric ID is: 0x702D544ABC90021B
+CHIPTOOL | 2021-12-29 22:25:33.285 | [1640816611.400943][8:18] CHIP:DL: CHIP task running
+CHIPTOOL | 2021-12-29 22:25:33.287 | [1640816611.401276][8:18] CHIP:DIS: Attempt to mDNS broadcast failed: ../../third_party/connectedhomeip/src/inet/IPEndPointBasis.cpp:687: OS Error 0x02000065: Network is unreachable
+CHIPTOOL | 2021-12-29 22:25:33.288 | [1640816611.402199][8:18] CHIP:DIS: Attempt to mDNS broadcast failed: ../../third_party/connectedhomeip/src/inet/IPEndPointBasis.cpp:687: OS Error 0x02000065: Network is unreachable
+CHIPTOOL | 2021-12-29 22:25:33.289 | [1640816731.401355][8:8] CHIP:-: ../../commands/common/CHIPCommand.cpp:125: CHIP Error 0x00000032: Timeout at ../../commands/common/CHIPCommand.cpp:84
+CHIPTOOL | 2021-12-29 22:25:33.290 | [1640816731.401441][8:8] CHIP:TOO: Run command failure: ../../commands/common/CHIPCommand.cpp:125: CHIP Error 0x00000032: Timeout
+CHIPTOOL | 2021-12-29 22:25:33.291 | [1640816731.527525][8:8] CHIP:CTL: Shutting down the System State, this will teardown the CHIP Stack
+CHIPTOOL | 2021-12-29 22:25:33.292 | [1640816731.528030][8:8] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-DnBWIO)
+CHIPTOOL | 2021-12-29 22:25:33.293 | [1640816731.528922][8:8] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
+CHIPTOOL | 2021-12-29 22:25:33.297 | [1640816731.529015][8:8] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
+CHIPTOOL | 2021-12-29 22:25:33.298 | [1640816731.529033][8:8] CHIP:DL: Inet Layer shutdown
+CHIPTOOL | 2021-12-29 22:25:33.299 | [1640816731.529500][8:8] CHIP:DL: BLE layer shutdown
+CHIPTOOL | 2021-12-29 22:25:33.300 | [1640816731.529523][8:8] CHIP:DL: System Layer shutdown
+ERROR | 2021-12-29 22:25:33.301 | Test Suite Error: Error occurred during setup of test suite.#FirstChipToolSuite. #Failed to pair with DUT
+INFO | 2021-12-29 22:25:33.345 | Cancel test case
+INFO | 2021-12-29 22:25:33.348 | Cancel test step
+INFO | 2021-12-29 22:25:33.350 | Cancel test step
+INFO | 2021-12-29 22:25:33.352 | Cancel test step
+INFO | 2021-12-29 22:25:33.355 | Cancel test step
+INFO | 2021-12-29 22:25:33.357 | Cancel test step
+INFO | 2021-12-29 22:25:33.359 | Cancel test step
+INFO | 2021-12-29 22:25:33.362 | Cancel test step
+INFO | 2021-12-29 22:25:33.364 | Cancel test step
+INFO | 2021-12-29 22:25:33.366 | Cancel test step
+INFO | 2021-12-29 22:25:33.369 | Cancel test step
+INFO | 2021-12-29 22:25:33.371 | Cancel test step
+INFO | 2021-12-29 22:25:33.373 | Cancel test step
+INFO | 2021-12-29 22:25:33.375 | Cancel test step
+INFO | 2021-12-29 22:25:33.377 | Cancel test step
+INFO | 2021-12-29 22:25:33.380 | Cancel test step
+INFO | 2021-12-29 22:25:33.385 | Cancel test step
+INFO | 2021-12-29 22:25:33.388 | Cancel test step
+INFO | 2021-12-29 22:25:33.390 | Cancel test step
+INFO | 2021-12-29 22:25:33.392 | Cancel test step
+INFO | 2021-12-29 22:25:33.395 | Stopping chip-tool container
+INFO | 2021-12-29 22:25:33.397 | Test Suite Completed [ERROR]: Test Suite run with chip-tool tests
+INFO | 2021-12-29 22:25:33.405 | Test Run Completed [ERROR]
+
+Issue :
+In test-harness.config file under dut_config I don't see these parameters (node_id and pin code) but I see TE-6 supported parameters (setup code, discriminatior, ip address, port).
+Is test-harness should be updated or need any extra parameters to be added?
+",0, cli sh available test cases are failing with google thermostat trying to use test harness tool to execute te test cases related to thermostat steps followed setup test harness on raspi commissioned thermostat using test harness s chip tool edited wifi config and dut config in test harness config file as below ubuntu matter te cat test harness config logging path logs filename time yyyy mm dd log level debug rotation days retention months format level time yyyy mm dd hh mm ss sss name function line message notifier enable notifications false notifier config username xiole chip test gmail com password yntwdxwyofvehafg to xiole chip test gmail com subject chip tool crash log network fabric id thread dataset channel panid extpanid masterkey networkname demo rcp serial path dev rcp baudrate on mesh prefix network interface wifi ssid rkreddy password adhyareddy dut config pairing mode onnetwork setup code discriminator ip address port from cli executed tc dm test case and i see below error command error info run test runner is ready info test run executing info test suite executing test suite run with chip tool tests info setting up chip tool info pair with dut chiptool chip ctl generating noc chiptool chip ctl generating icac chiptool chip ctl generating rcac chiptool chip dl audit random number generator audit start chiptool chip dl audit validate and are chiptool chip dl audit validate and are chiptool chip dl audit chiptool chip dl audit chiptool chip dl audit chiptool chip dl audit random number generator audit end chiptool chip dl writing settings to file tmp chip factory ini tppvnn chiptool chip dl renamed tmp file to file tmp chip factory ini chiptool chip dl writing settings to file tmp chip config ini chiptool chip dl renamed tmp file to file tmp chip config ini chiptool chip dl writing settings to file tmp chip counters ini lfsxun chiptool chip dl renamed tmp file to file tmp chip counters ini chiptool chip dl writing settings to file tmp chip counters ini chiptool chip dl renamed tmp file to file tmp chip counters ini chiptool chip dl nvs set chip counters reboot count chiptool chip dl writing settings to file tmp chip counters ini chiptool chip dl renamed tmp file to file tmp chip counters ini chiptool chip dl nvs set chip counters total operational hours chiptool chip dl writing settings to file tmp chip counters ini dbzcon chiptool chip dl renamed tmp file to file tmp chip counters ini chiptool chip dl nvs set chip counters boot reason chiptool chip dl got ethernet interface chiptool chip dl found the primary ethernet interface chiptool chip dl got wifi interface chiptool chip dl found the primary wifi interface chiptool chip in udp init bind listen port chiptool chip in udp init bound to port chiptool chip in udp init bind listen port chiptool chip in udp init bound to port chiptool chip in transportmgr initialized chiptool chip dis init fabric pairing table with server storage chiptool chip dl writing settings to file tmp chip counters ini nmnkkm chiptool chip dl renamed tmp file to file tmp chip counters ini chiptool chip dl nvs set chip counters globalmctr chiptool chip ctl system state initialized chiptool chip dl mdns failed to join multicast group on for address type third party connectedhomeip src inet ipendpointbasis cpp inet error address not found chiptool chip dl mdns failed to join multicast group on for address type third party connectedhomeip src inet ipendpointbasis cpp inet error address not found chiptool chip dl mdns failed to join multicast group on for address type third party connectedhomeip src inet ipendpointbasis cpp inet error address not found chiptool chip dl mdns failed to join multicast group on for address type third party connectedhomeip src inet ipendpointbasis cpp inet error address not found chiptool chip dl mdns failed to join multicast group on for address type third party connectedhomeip src inet ipendpointbasis cpp inet error address not found chiptool chip zcl using zap configuration chiptool chip dis verifying the received credentials chiptool chip dis added new fabric at index initialized chiptool chip dis assigned compressed fabric id node id chiptool chip ctl joined the fabric at index compressed fabric id is chiptool chip dl chip task running chiptool chip dis attempt to mdns broadcast failed third party connectedhomeip src inet ipendpointbasis cpp os error network is unreachable chiptool chip dis attempt to mdns broadcast failed third party connectedhomeip src inet ipendpointbasis cpp os error network is unreachable chiptool chip commands common chipcommand cpp chip error timeout at commands common chipcommand cpp chiptool chip too run command failure commands common chipcommand cpp chip error timeout chiptool chip ctl shutting down the system state this will teardown the chip stack chiptool chip dl writing settings to file tmp chip counters ini dnbwio chiptool chip dl renamed tmp file to file tmp chip counters ini chiptool chip dl nvs set chip counters total operational hours chiptool chip dl inet layer shutdown chiptool chip dl ble layer shutdown chiptool chip dl system layer shutdown error test suite error error occurred during setup of test suite firstchiptoolsuite failed to pair with dut info cancel test case info cancel test step info cancel test step info cancel test step info cancel test step info cancel test step info cancel test step info cancel test step info cancel test step info cancel test step info cancel test step info cancel test step info cancel test step info cancel test step info cancel test step info cancel test step info cancel test step info cancel test step info cancel test step info cancel test step info stopping chip tool container info test suite completed test suite run with chip tool tests info test run completed issue in test harness config file under dut config i don t see these parameters node id and pin code but i see te supported parameters setup code discriminatior ip address port is test harness should be updated or need any extra parameters to be added ,0
+709493,24380029155.0,IssuesEvent,2022-10-04 06:56:25,zephyrproject-rtos/zephyr,https://api.github.com/repos/zephyrproject-rtos/zephyr,closed,Add overlay-bt-minimal.conf for smp_svr sample application,Enhancement priority: low area: Bluetooth area: mcumgr,"**Is your enhancement proposal related to a problem? Please describe.**
+At present, the smp_svr sample application will not build for constrained devices, and will only just fit some other devices e.g. nRF52832, whereby about 98% of the total RAM is used.
+
+**Describe the solution you'd like**
+There should therefore be a minimal bt configuration that can be used for these devices with reduced functionality or features but that can fit
+
+**Describe alternatives you've considered**
+Reduce the feature set for all devices, not good as it then places unwarranted limitations on more capable devices",1.0,"Add overlay-bt-minimal.conf for smp_svr sample application - **Is your enhancement proposal related to a problem? Please describe.**
+At present, the smp_svr sample application will not build for constrained devices, and will only just fit some other devices e.g. nRF52832, whereby about 98% of the total RAM is used.
+
+**Describe the solution you'd like**
+There should therefore be a minimal bt configuration that can be used for these devices with reduced functionality or features but that can fit
+
+**Describe alternatives you've considered**
+Reduce the feature set for all devices, not good as it then places unwarranted limitations on more capable devices",0,add overlay bt minimal conf for smp svr sample application is your enhancement proposal related to a problem please describe at present the smp svr sample application will not build for constrained devices and will only just fit some other devices e g whereby about of the total ram is used describe the solution you d like there should therefore be a minimal bt configuration that can be used for these devices with reduced functionality or features but that can fit describe alternatives you ve considered reduce the feature set for all devices not good as it then places unwarranted limitations on more capable devices,0
+203678,23169656551.0,IssuesEvent,2022-07-30 14:03:55,MatBenfield/news,https://api.github.com/repos/MatBenfield/news,closed,[SecurityWeek] Major Cybersecurity Breach of US Court System Comes to Light,SecurityWeek Stale,"
+
+**The US federal court system suffered a major cybersecurity breach in 2020, House Judiciary chairman Rep. Jerrold Nadler revealed in a public hearing on Thursday.**
+
+[read more](https://www.securityweek.com/major-cybersecurity-breach-us-court-system-comes-light)
+
+
+
+
+
+",True,"[SecurityWeek] Major Cybersecurity Breach of US Court System Comes to Light -
+
+**The US federal court system suffered a major cybersecurity breach in 2020, House Judiciary chairman Rep. Jerrold Nadler revealed in a public hearing on Thursday.**
+
+[read more](https://www.securityweek.com/major-cybersecurity-breach-us-court-system-comes-light)
+
+
+
+
+
+",0, major cybersecurity breach of us court system comes to light the us federal court system suffered a major cybersecurity breach in house judiciary chairman rep jerrold nadler revealed in a public hearing on thursday ,0
+3389,3436517617.0,IssuesEvent,2015-12-12 13:10:12,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Debugger closes after closing a running game.,enhancement topic:editor usability,"When the debugger is set to stay (in the script view, debug > show debugger), it'll always close after running and closing a game. It'd be ideal if it stayed open if explicitly set to show.",True,"Debugger closes after closing a running game. - When the debugger is set to stay (in the script view, debug > show debugger), it'll always close after running and closing a game. It'd be ideal if it stayed open if explicitly set to show.",1,debugger closes after closing a running game when the debugger is set to stay in the script view debug show debugger it ll always close after running and closing a game it d be ideal if it stayed open if explicitly set to show ,1
+12759,8068723328.0,IssuesEvent,2018-08-06 00:10:54,godotengine/godot,https://api.github.com/repos/godotengine/godot,reopened,Minimizing the editor shrinks all panels,platform:windows usability,"
+
+**Godot version:**
+3.1 6c569c9
+
+
+**OS/device including version:**
+Windows 10 x64
+
+
+**Issue description:**
+A short video demonstrating the problem: https://streamable.com/doj64
+
+
+**Steps to reproduce:**
+1. Open a project
+2. Resize any panel to whatever size
+3. Minimize the window
+4. Restore the window",True,"Minimizing the editor shrinks all panels -
+
+**Godot version:**
+3.1 6c569c9
+
+
+**OS/device including version:**
+Windows 10 x64
+
+
+**Issue description:**
+A short video demonstrating the problem: https://streamable.com/doj64
+
+
+**Steps to reproduce:**
+1. Open a project
+2. Resize any panel to whatever size
+3. Minimize the window
+4. Restore the window",1,minimizing the editor shrinks all panels please search existing issues for potential duplicates before filing yours godot version os device including version windows issue description a short video demonstrating the problem steps to reproduce open a project resize any panel to whatever size minimize the window restore the window,1
+15901,10369944881.0,IssuesEvent,2019-09-08 08:28:51,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Complex custom resources: workflow problems,enhancement topic:core topic:mono usability,"
+
+**Godot version:**
+
+488884178e773a6e80070663d92cc53cb820bff9
+
+**Issue description:**
+
+There are a number of open issues and comments surrounding the usage of custom resources in Godot, but I didn't find anything which comprehensively covers the problem, so I thought I'd create an issue on it here, since now the problems surrounding loading custom resources are resolved when using C#. The following text uses C# examples, but the same applies to GDScript.
+
+Consider we have the following hypothetical data structures saved into different scripts:
+```cs
+public class MonsterInfo : Resource
+{
+ [Export]
+ public Stats stats;
+ [Export]
+ public ElementalResistances resistances;
+ [Export]
+ public DropChance[] dropChances;
+ [Export]
+ ...
+}
+
+public class Stats : Resource
+{
+ [Export]
+ public int strength;
+ [Export]
+ public int defense;
+ [Export]
+ public int magic;
+ [Export]
+ public int resistance;
+ [Export]
+ ...
+}
+
+public class ElementalResistances : Resource
+{
+ [Export]
+ public int fire;
+ [Export]
+ public int water;
+ [Export]
+ public int holy;
+ [Export]
+ public int unholy;
+ [Export]
+ ...
+}
+
+public class DropChance : Resource
+{
+ [Export]
+ public Item item;
+ [Export]
+ public float chance;
+}
+```
+
+So, our `MonsterInfo` resource will hold various other resources which describe its make-up; we can save this to disk and have our own database editable right there in the editor. Great! But once you create a new `MonsterInfo` resource, you run into this problem: every property exported gives just a big list of resources to create from, none of which are what you really want:
+
+
+
+In order to assign something to these slots, it is required to create them first in the FileSystem, save them to disk, then drag and drop them into the slot. So your project winds up littered with all these extra resources that exist just to be placed into those slots, when what you really want is the ability to just create a resource right there and have them 'built-in' to the file, as you can do with other resources.
+
+This is especially egregious with `DropChance`: for every entry you'd like to create describing what items this monster will drop when killed, that's another resource you have to go through the process of creating.
+
+One proposed solution to this problem is to keep everything within the one resource:
+
+```cs
+class MonsterInfo : Resource{
+ [Export]
+ public int strength;
+ [Export]
+ public int defense;
+ ...
+ [Export]
+ public int fireRes;
+ [Export]
+ public int waterRes;
+ ...
+ [Export]
+ public Item itemA;
+ [Export]
+ public float itemADropChance;
+ [Export]
+ public Item itemB;
+ [Export]
+ public item itemBDropChance;
+ ...
+}
+```
+
+However, this introduces a problem where, if you have another resource of type `PlayableCharacterInfo`, which also uses `Stats`, `ElementalResistances` and so forth, you must copy/paste your code, or try to refactor it by introducing a base class, which can have its own problems (since multiple inheritance isn't a thing in either GDScript or C#.)
+
+Another possible solution (at least for `DropChance`) is to use a dictionary, where you manually define an entry that takes one resource (or path to a resource) and one float; however, dictionaries aren't really designed for this usage, and if you needed to introduce a 3rd variable, the problem gets even worse, where you now have to associate an array as the value to the dictionary which contains the rest of the info. This entire solution is unwieldy due to the fact that you don't have any guarantee of what's in these dictionaries or if the array is in the right order, so extra care must be given here and you must reference back to this resource when working with it in code to ensure you're accessing them properly, as there's no names associated with this data, nor any type safety; the same applies in the case of foregoing custom resources for, say, `Stats`, and just using an int array instead: you have to count how many entries you're adding, and you have to memorize the order in which they're meant to go, as there's no names to go by here either.
+
+A third solution is to just forego custom resources all together and use JSON or some other text format, which has the drawback of being more difficult to work with (no inspector, so none of the benefits which can come from it), and since you still have to figure out what to do with all your data once it's parsed, introducing more work on behalf of the developer; it's something which can break easily in ways that are hard to debug, as another developer who works in this manner has revealed to me. One could create an inspector of their own to work with all this data, but that's yet more work for each new resource introduced, not leveraging the power of Godot already present.
+
+Perhaps the most robust solution right now is to also forego custom resources but to instead define your data into one big script that contains just definitions; while less than ideal, as you still have much typing to do, you can at least be certain that you have a name associated with all your data, with type safety, and neatly organized into sub-objects which can just be associated with any data type of your choosing:
+
+```cs
+private static readonly Dictionary MonsterDefinitions = new Dictionary {
+...
+stats = new Stats {
+ strength = 381,
+ psionics = 412,
+ defense = 255,
+ resistance = 307,
+ ...
+},
+elements = new Elements {
+ sun = 2,
+ moon = 2,
+ ...
+},
+skills = new Skills {
+ trainer = 3,
+ smash = 3,
+ ...
+},
+...
+```
+And then there's the business where you create a plugin for this stuff, but that's also unwieldy and shrouded in mystery.
+
+In an ideal Godot, you would simply be able to create a resource of the exported type right there in the slot, and then modify the built-in entry that way; now you don't need to clutter up the project with possibly hundreds (or more, depending on the complexity of your data) of resources that do nothing but provide the makeup of other more complex resources (say, you have 100 different monsters in your game, each of which requires 5 other resources to describe it), or try to come up with some other less-than-ideal solution.
+
+Compare this situation to Unity3D's ScriptableObject/Serializable attribute, the parallel to Godot's custom resources:
+
+```cs
+public class MonsterInfo : ScriptableObject{
+ public Stats stats;
+ ...
+}
+
+[System.Serializable]
+public class Stats{
+ public int strength;
+ ...
+}
+```
+
+In this case, all the public values of `Stats` will just show up in the inspector when a `MonsterInfo` file is inspected, and can thus be assigned to right there, in its own collapsible menu; it makes creating complex data simple and intuitive, again, bringing all the benefits of the inspector with it.
+
+I think Godot can be just as easy and simple to work with data in this regard, but currently it is not.",True,"Complex custom resources: workflow problems -
+
+**Godot version:**
+
+488884178e773a6e80070663d92cc53cb820bff9
+
+**Issue description:**
+
+There are a number of open issues and comments surrounding the usage of custom resources in Godot, but I didn't find anything which comprehensively covers the problem, so I thought I'd create an issue on it here, since now the problems surrounding loading custom resources are resolved when using C#. The following text uses C# examples, but the same applies to GDScript.
+
+Consider we have the following hypothetical data structures saved into different scripts:
+```cs
+public class MonsterInfo : Resource
+{
+ [Export]
+ public Stats stats;
+ [Export]
+ public ElementalResistances resistances;
+ [Export]
+ public DropChance[] dropChances;
+ [Export]
+ ...
+}
+
+public class Stats : Resource
+{
+ [Export]
+ public int strength;
+ [Export]
+ public int defense;
+ [Export]
+ public int magic;
+ [Export]
+ public int resistance;
+ [Export]
+ ...
+}
+
+public class ElementalResistances : Resource
+{
+ [Export]
+ public int fire;
+ [Export]
+ public int water;
+ [Export]
+ public int holy;
+ [Export]
+ public int unholy;
+ [Export]
+ ...
+}
+
+public class DropChance : Resource
+{
+ [Export]
+ public Item item;
+ [Export]
+ public float chance;
+}
+```
+
+So, our `MonsterInfo` resource will hold various other resources which describe its make-up; we can save this to disk and have our own database editable right there in the editor. Great! But once you create a new `MonsterInfo` resource, you run into this problem: every property exported gives just a big list of resources to create from, none of which are what you really want:
+
+
+
+In order to assign something to these slots, it is required to create them first in the FileSystem, save them to disk, then drag and drop them into the slot. So your project winds up littered with all these extra resources that exist just to be placed into those slots, when what you really want is the ability to just create a resource right there and have them 'built-in' to the file, as you can do with other resources.
+
+This is especially egregious with `DropChance`: for every entry you'd like to create describing what items this monster will drop when killed, that's another resource you have to go through the process of creating.
+
+One proposed solution to this problem is to keep everything within the one resource:
+
+```cs
+class MonsterInfo : Resource{
+ [Export]
+ public int strength;
+ [Export]
+ public int defense;
+ ...
+ [Export]
+ public int fireRes;
+ [Export]
+ public int waterRes;
+ ...
+ [Export]
+ public Item itemA;
+ [Export]
+ public float itemADropChance;
+ [Export]
+ public Item itemB;
+ [Export]
+ public item itemBDropChance;
+ ...
+}
+```
+
+However, this introduces a problem where, if you have another resource of type `PlayableCharacterInfo`, which also uses `Stats`, `ElementalResistances` and so forth, you must copy/paste your code, or try to refactor it by introducing a base class, which can have its own problems (since multiple inheritance isn't a thing in either GDScript or C#.)
+
+Another possible solution (at least for `DropChance`) is to use a dictionary, where you manually define an entry that takes one resource (or path to a resource) and one float; however, dictionaries aren't really designed for this usage, and if you needed to introduce a 3rd variable, the problem gets even worse, where you now have to associate an array as the value to the dictionary which contains the rest of the info. This entire solution is unwieldy due to the fact that you don't have any guarantee of what's in these dictionaries or if the array is in the right order, so extra care must be given here and you must reference back to this resource when working with it in code to ensure you're accessing them properly, as there's no names associated with this data, nor any type safety; the same applies in the case of foregoing custom resources for, say, `Stats`, and just using an int array instead: you have to count how many entries you're adding, and you have to memorize the order in which they're meant to go, as there's no names to go by here either.
+
+A third solution is to just forego custom resources all together and use JSON or some other text format, which has the drawback of being more difficult to work with (no inspector, so none of the benefits which can come from it), and since you still have to figure out what to do with all your data once it's parsed, introducing more work on behalf of the developer; it's something which can break easily in ways that are hard to debug, as another developer who works in this manner has revealed to me. One could create an inspector of their own to work with all this data, but that's yet more work for each new resource introduced, not leveraging the power of Godot already present.
+
+Perhaps the most robust solution right now is to also forego custom resources but to instead define your data into one big script that contains just definitions; while less than ideal, as you still have much typing to do, you can at least be certain that you have a name associated with all your data, with type safety, and neatly organized into sub-objects which can just be associated with any data type of your choosing:
+
+```cs
+private static readonly Dictionary MonsterDefinitions = new Dictionary {
+...
+stats = new Stats {
+ strength = 381,
+ psionics = 412,
+ defense = 255,
+ resistance = 307,
+ ...
+},
+elements = new Elements {
+ sun = 2,
+ moon = 2,
+ ...
+},
+skills = new Skills {
+ trainer = 3,
+ smash = 3,
+ ...
+},
+...
+```
+And then there's the business where you create a plugin for this stuff, but that's also unwieldy and shrouded in mystery.
+
+In an ideal Godot, you would simply be able to create a resource of the exported type right there in the slot, and then modify the built-in entry that way; now you don't need to clutter up the project with possibly hundreds (or more, depending on the complexity of your data) of resources that do nothing but provide the makeup of other more complex resources (say, you have 100 different monsters in your game, each of which requires 5 other resources to describe it), or try to come up with some other less-than-ideal solution.
+
+Compare this situation to Unity3D's ScriptableObject/Serializable attribute, the parallel to Godot's custom resources:
+
+```cs
+public class MonsterInfo : ScriptableObject{
+ public Stats stats;
+ ...
+}
+
+[System.Serializable]
+public class Stats{
+ public int strength;
+ ...
+}
+```
+
+In this case, all the public values of `Stats` will just show up in the inspector when a `MonsterInfo` file is inspected, and can thus be assigned to right there, in its own collapsible menu; it makes creating complex data simple and intuitive, again, bringing all the benefits of the inspector with it.
+
+I think Godot can be just as easy and simple to work with data in this regard, but currently it is not.",1,complex custom resources workflow problems please search existing issues for potential duplicates before filing yours godot version issue description there are a number of open issues and comments surrounding the usage of custom resources in godot but i didn t find anything which comprehensively covers the problem so i thought i d create an issue on it here since now the problems surrounding loading custom resources are resolved when using c the following text uses c examples but the same applies to gdscript consider we have the following hypothetical data structures saved into different scripts cs public class monsterinfo resource public stats stats public elementalresistances resistances public dropchance dropchances public class stats resource public int strength public int defense public int magic public int resistance public class elementalresistances resource public int fire public int water public int holy public int unholy public class dropchance resource public item item public float chance so our monsterinfo resource will hold various other resources which describe its make up we can save this to disk and have our own database editable right there in the editor great but once you create a new monsterinfo resource you run into this problem every property exported gives just a big list of resources to create from none of which are what you really want in order to assign something to these slots it is required to create them first in the filesystem save them to disk then drag and drop them into the slot so your project winds up littered with all these extra resources that exist just to be placed into those slots when what you really want is the ability to just create a resource right there and have them built in to the file as you can do with other resources this is especially egregious with dropchance for every entry you d like to create describing what items this monster will drop when killed that s another resource you have to go through the process of creating one proposed solution to this problem is to keep everything within the one resource cs class monsterinfo resource public int strength public int defense public int fireres public int waterres public item itema public float itemadropchance public item itemb public item itembdropchance however this introduces a problem where if you have another resource of type playablecharacterinfo which also uses stats elementalresistances and so forth you must copy paste your code or try to refactor it by introducing a base class which can have its own problems since multiple inheritance isn t a thing in either gdscript or c another possible solution at least for dropchance is to use a dictionary where you manually define an entry that takes one resource or path to a resource and one float however dictionaries aren t really designed for this usage and if you needed to introduce a variable the problem gets even worse where you now have to associate an array as the value to the dictionary which contains the rest of the info this entire solution is unwieldy due to the fact that you don t have any guarantee of what s in these dictionaries or if the array is in the right order so extra care must be given here and you must reference back to this resource when working with it in code to ensure you re accessing them properly as there s no names associated with this data nor any type safety the same applies in the case of foregoing custom resources for say stats and just using an int array instead you have to count how many entries you re adding and you have to memorize the order in which they re meant to go as there s no names to go by here either a third solution is to just forego custom resources all together and use json or some other text format which has the drawback of being more difficult to work with no inspector so none of the benefits which can come from it and since you still have to figure out what to do with all your data once it s parsed introducing more work on behalf of the developer it s something which can break easily in ways that are hard to debug as another developer who works in this manner has revealed to me one could create an inspector of their own to work with all this data but that s yet more work for each new resource introduced not leveraging the power of godot already present perhaps the most robust solution right now is to also forego custom resources but to instead define your data into one big script that contains just definitions while less than ideal as you still have much typing to do you can at least be certain that you have a name associated with all your data with type safety and neatly organized into sub objects which can just be associated with any data type of your choosing cs private static readonly dictionary monsterdefinitions new dictionary stats new stats strength psionics defense resistance elements new elements sun moon skills new skills trainer smash and then there s the business where you create a plugin for this stuff but that s also unwieldy and shrouded in mystery in an ideal godot you would simply be able to create a resource of the exported type right there in the slot and then modify the built in entry that way now you don t need to clutter up the project with possibly hundreds or more depending on the complexity of your data of resources that do nothing but provide the makeup of other more complex resources say you have different monsters in your game each of which requires other resources to describe it or try to come up with some other less than ideal solution compare this situation to s scriptableobject serializable attribute the parallel to godot s custom resources cs public class monsterinfo scriptableobject public stats stats public class stats public int strength in this case all the public values of stats will just show up in the inspector when a monsterinfo file is inspected and can thus be assigned to right there in its own collapsible menu it makes creating complex data simple and intuitive again bringing all the benefits of the inspector with it i think godot can be just as easy and simple to work with data in this regard but currently it is not ,1
+16631,11161720215.0,IssuesEvent,2019-12-26 14:55:20,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Error log becomes unusable when it has many lines,bug confirmed topic:editor usability,"Godot 3.0 master
+
+One of my projects produced a lot of errors (1428), and I noticed the error list becomes extremely slow when I scroll down, even though only a few entries (10) are drawn.
+
+Clicking items in it also becomes very slow, I have to wait a few seconds before I can see the call stack.
+
+",True,"Error log becomes unusable when it has many lines - Godot 3.0 master
+
+One of my projects produced a lot of errors (1428), and I noticed the error list becomes extremely slow when I scroll down, even though only a few entries (10) are drawn.
+
+Clicking items in it also becomes very slow, I have to wait a few seconds before I can see the call stack.
+
+",1,error log becomes unusable when it has many lines godot master one of my projects produced a lot of errors and i noticed the error list becomes extremely slow when i scroll down even though only a few entries are drawn clicking items in it also becomes very slow i have to wait a few seconds before i can see the call stack ,1
+16003,10477116202.0,IssuesEvent,2019-09-23 20:09:43,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,"'Use Bezier Curves' option when adding rotation keyframe adds a standard keyframe track, not a curve",bug topic:editor usability,"
+
+**Godot version:**
+
+3.1 (Mac version)
+
+**OS/device including version:**
+
+Mac OS 10.14
+
+**Issue description:**
+
+Inserting keyframes and selecting 'Use Bezier Curves' does not work correctly for the rotation property. Instead it adds a regular key track **unless** you also add 'position' or 'scale' properties.
+
+**Steps to reproduce:**
+
+Only rotation selected:
+
+
+'Use Bezier Curves' is checked:
+
+
+It adds a standard keyframe track:
+
+
+Delete keyframe and select another property as well:
+
+
+Now it adds bezier curve tracks:
+
+",True,"'Use Bezier Curves' option when adding rotation keyframe adds a standard keyframe track, not a curve -
+
+**Godot version:**
+
+3.1 (Mac version)
+
+**OS/device including version:**
+
+Mac OS 10.14
+
+**Issue description:**
+
+Inserting keyframes and selecting 'Use Bezier Curves' does not work correctly for the rotation property. Instead it adds a regular key track **unless** you also add 'position' or 'scale' properties.
+
+**Steps to reproduce:**
+
+Only rotation selected:
+
+
+'Use Bezier Curves' is checked:
+
+
+It adds a standard keyframe track:
+
+
+Delete keyframe and select another property as well:
+
+
+Now it adds bezier curve tracks:
+
+",1, use bezier curves option when adding rotation keyframe adds a standard keyframe track not a curve please search existing issues for potential duplicates before filing yours godot version mac version os device including version mac os issue description inserting keyframes and selecting use bezier curves does not work correctly for the rotation property instead it adds a regular key track unless you also add position or scale properties steps to reproduce only rotation selected use bezier curves is checked it adds a standard keyframe track delete keyframe and select another property as well now it adds bezier curve tracks ,1
+26369,26765871341.0,IssuesEvent,2023-01-31 10:34:59,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,"""(Re)importing Assets"" dialog blocks screen making it difficult to do other things while waiting...",bug topic:editor usability topic:import,"### Godot version
+
+Godot 4, d1e5903c67956707948b1de370b807e3aad395b7
+
+### System information
+
+Arch Linux, Gnome Shell, Wayland
+
+### Issue description
+
+The ""(Re)importing Assets"" dialog blocks all other windows while importing is in progress. This window is always on top, immovable, and unhideable. For long import operations it makes using other applications on the system difficult.
+
+
+
+
+
+
+
+
+### Steps to reproduce
+
+Cause files to import, try to use other applications while import is in progress.
+
+### Minimal reproduction project
+
+N/A",True,"""(Re)importing Assets"" dialog blocks screen making it difficult to do other things while waiting... - ### Godot version
+
+Godot 4, d1e5903c67956707948b1de370b807e3aad395b7
+
+### System information
+
+Arch Linux, Gnome Shell, Wayland
+
+### Issue description
+
+The ""(Re)importing Assets"" dialog blocks all other windows while importing is in progress. This window is always on top, immovable, and unhideable. For long import operations it makes using other applications on the system difficult.
+
+
+
+
+
+
+
+
+### Steps to reproduce
+
+Cause files to import, try to use other applications while import is in progress.
+
+### Minimal reproduction project
+
+N/A",1, re importing assets dialog blocks screen making it difficult to do other things while waiting godot version godot system information arch linux gnome shell wayland issue description the re importing assets dialog blocks all other windows while importing is in progress this window is always on top immovable and unhideable for long import operations it makes using other applications on the system difficult steps to reproduce cause files to import try to use other applications while import is in progress minimal reproduction project n a,1
+426448,29519995378.0,IssuesEvent,2023-06-04 23:46:42,Arquisoft/lomap_en3a,https://api.github.com/repos/Arquisoft/lomap_en3a,closed,Section 7 - Deployment view,documentation,Technical infrastructure and mapping of building blocks to infrastructure elements,1.0,Section 7 - Deployment view - Technical infrastructure and mapping of building blocks to infrastructure elements,0,section deployment view technical infrastructure and mapping of building blocks to infrastructure elements,0
+24525,23873095677.0,IssuesEvent,2022-09-07 16:23:01,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Changing layer changes atlas source,bug topic:editor usability topic:2d,"### Godot version
+
+c2d55a4
+
+### System information
+
+Windows 10 x64
+
+### Issue description
+
+Another weird source interaction. Related to sorting (like in #58482)
+
+
+
+### Steps to reproduce
+
+1. Add TileMap with 2 tilesets (can be 2 icon.pngs)
+2. Change sorting to e.g. ID descending
+3. Add layer
+4. Pick some tile I think
+5. Change layer
+6. Your source is changed
+
+EDIT:
+Updated steps. You need TileMap with a couple of layers.
+1. Draw some tiles
+2. Change tile source sorting (make sure the new order is different from default)
+3. Pick any source (different than in 1.)
+4. Pick tiles from the scene. Your selected source is the same as in 1.
+5. Change layer. Your selected source is the same as in 3.
+
+### Minimal reproduction project
+
+_No response_",True,"Changing layer changes atlas source - ### Godot version
+
+c2d55a4
+
+### System information
+
+Windows 10 x64
+
+### Issue description
+
+Another weird source interaction. Related to sorting (like in #58482)
+
+
+
+### Steps to reproduce
+
+1. Add TileMap with 2 tilesets (can be 2 icon.pngs)
+2. Change sorting to e.g. ID descending
+3. Add layer
+4. Pick some tile I think
+5. Change layer
+6. Your source is changed
+
+EDIT:
+Updated steps. You need TileMap with a couple of layers.
+1. Draw some tiles
+2. Change tile source sorting (make sure the new order is different from default)
+3. Pick any source (different than in 1.)
+4. Pick tiles from the scene. Your selected source is the same as in 1.
+5. Change layer. Your selected source is the same as in 3.
+
+### Minimal reproduction project
+
+_No response_",1,changing layer changes atlas source godot version system information windows issue description another weird source interaction related to sorting like in steps to reproduce add tilemap with tilesets can be icon pngs change sorting to e g id descending add layer pick some tile i think change layer your source is changed edit updated steps you need tilemap with a couple of layers draw some tiles change tile source sorting make sure the new order is different from default pick any source different than in pick tiles from the scene your selected source is the same as in change layer your selected source is the same as in minimal reproduction project no response ,1
+132475,18724824951.0,IssuesEvent,2021-11-03 15:19:12,collect-nyc/collect_site,https://api.github.com/repos/collect-nyc/collect_site,opened,"Credits: Include support for line breaks, carriage returns, multiple entries per category",design,"Maintain line height from general style 13pt/18h
+![]()
+",1.0,"Credits: Include support for line breaks, carriage returns, multiple entries per category - Maintain line height from general style 13pt/18h
+![]()
+",0,credits include support for line breaks carriage returns multiple entries per category maintain line height from general style img width alt screen shot at am src ,0
+45228,7167187680.0,IssuesEvent,2018-01-29 19:41:54,STScI-JWST/jwst,https://api.github.com/repos/STScI-JWST/jwst,opened,Update jump step docs regarding saturation,documentation jump,According to https://jira.stsci.edu/browse/JP-147 the jump step documentation is not explicit enough about jump detection not taking place for data samples that are flagged as saturated. So we should make this more obvious.,1.0,Update jump step docs regarding saturation - According to https://jira.stsci.edu/browse/JP-147 the jump step documentation is not explicit enough about jump detection not taking place for data samples that are flagged as saturated. So we should make this more obvious.,0,update jump step docs regarding saturation according to the jump step documentation is not explicit enough about jump detection not taking place for data samples that are flagged as saturated so we should make this more obvious ,0
+75480,25866911546.0,IssuesEvent,2022-12-13 21:46:29,vector-im/element-web,https://api.github.com/repos/vector-im/element-web,closed,"""People"" metaspace shows favourite rooms",T-Defect S-Major A-Room-List A-Spaces O-Uncommon,"### Steps to reproduce
+
+1. Click on ""People"" metaspace
+
+### Outcome
+
+#### What did you expect?
+See only people listed in the left panel
+
+#### What happened instead?
+See rooms under ""Favourites"" listed in the left panel
+
+
+
+
+### Operating system
+
+_No response_
+
+### Browser information
+
+Chromium 107.0.5304.121 (Official Build) Arch Linux (64-bit)
+
+### URL for webapp
+
+develop.element.io
+
+### Application version
+
+Element version: cbf5c43ae79d-react-569a36493378-js-b318a77ecef1 Olm version: 3.2.12
+
+### Homeserver
+
+matrix.org
+
+### Will you send logs?
+
+No",1.0,"""People"" metaspace shows favourite rooms - ### Steps to reproduce
+
+1. Click on ""People"" metaspace
+
+### Outcome
+
+#### What did you expect?
+See only people listed in the left panel
+
+#### What happened instead?
+See rooms under ""Favourites"" listed in the left panel
+
+
+
+
+### Operating system
+
+_No response_
+
+### Browser information
+
+Chromium 107.0.5304.121 (Official Build) Arch Linux (64-bit)
+
+### URL for webapp
+
+develop.element.io
+
+### Application version
+
+Element version: cbf5c43ae79d-react-569a36493378-js-b318a77ecef1 Olm version: 3.2.12
+
+### Homeserver
+
+matrix.org
+
+### Will you send logs?
+
+No",0, people metaspace shows favourite rooms steps to reproduce click on people metaspace outcome what did you expect see only people listed in the left panel what happened instead see rooms under favourites listed in the left panel operating system no response browser information chromium official build arch linux bit url for webapp develop element io application version element version react js olm version homeserver matrix org will you send logs no,0
+11701,7371303435.0,IssuesEvent,2018-03-13 11:16:52,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Autocomplete not working properly with partially written paths and get_node() syntactic sugar ($),bug topic:editor usability,"
+(I search every issue containing ""autocomplete"". Sorry if I it a duplicate)
+
+**Godot version:**
+3.0rc1
+
+
+**OS/device including version:**
+Win7 64
+
+
+**Issue description:**
+If I have ""$path/to"" written somewhere and want to modify it to be ""$path/to/child"". If I start writing, the correct autocomplete candidate will be offered but upon pressing tab the whole path is appended rather than only the part needed. In this example rather than ""$path/to/child"" the autocomplete will write ""$path/to/path/to/child""
+This doesn't happen with paths between double quotes
+
+**Minimal reproduction project:**
+
+
+
+",True,"Autocomplete not working properly with partially written paths and get_node() syntactic sugar ($) -
+(I search every issue containing ""autocomplete"". Sorry if I it a duplicate)
+
+**Godot version:**
+3.0rc1
+
+
+**OS/device including version:**
+Win7 64
+
+
+**Issue description:**
+If I have ""$path/to"" written somewhere and want to modify it to be ""$path/to/child"". If I start writing, the correct autocomplete candidate will be offered but upon pressing tab the whole path is appended rather than only the part needed. In this example rather than ""$path/to/child"" the autocomplete will write ""$path/to/path/to/child""
+This doesn't happen with paths between double quotes
+
+**Minimal reproduction project:**
+
+
+
+",1,autocomplete not working properly with partially written paths and get node syntactic sugar please search existing issues for potential duplicates before filing yours i search every issue containing autocomplete sorry if i it a duplicate godot version os device including version issue description if i have path to written somewhere and want to modify it to be path to child if i start writing the correct autocomplete candidate will be offered but upon pressing tab the whole path is appended rather than only the part needed in this example rather than path to child the autocomplete will write path to path to child this doesn t happen with paths between double quotes minimal reproduction project ,1
+26705,27101344179.0,IssuesEvent,2023-02-15 08:54:48,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,AudioPlaybackTrack put an infinite length rectangle when the waveform cannot be read,bug topic:editor usability topic:audio topic:animation,"### Godot version
+
+4.0.rc
+
+### System information
+
+Any
+
+### Issue description
+
+Placing an empty AudioStream or a procedural AudioStream will cause AudioPlaybackTrack to place an infinite length rectangle. It is not useful and should at least be a diamond.
+
+
+
+
+### Steps to reproduce
+
+Put AudioStreamRandomizer or some procedural AudioStream on AudioPlaybackTrack
+
+### Minimal reproduction project
+
+N/A",True,"AudioPlaybackTrack put an infinite length rectangle when the waveform cannot be read - ### Godot version
+
+4.0.rc
+
+### System information
+
+Any
+
+### Issue description
+
+Placing an empty AudioStream or a procedural AudioStream will cause AudioPlaybackTrack to place an infinite length rectangle. It is not useful and should at least be a diamond.
+
+
+
+
+### Steps to reproduce
+
+Put AudioStreamRandomizer or some procedural AudioStream on AudioPlaybackTrack
+
+### Minimal reproduction project
+
+N/A",1,audioplaybacktrack put an infinite length rectangle when the waveform cannot be read godot version rc system information any issue description placing an empty audiostream or a procedural audiostream will cause audioplaybacktrack to place an infinite length rectangle it is not useful and should at least be a diamond steps to reproduce put audiostreamrandomizer or some procedural audiostream on audioplaybacktrack minimal reproduction project n a,1
+341490,30588921616.0,IssuesEvent,2023-07-21 15:23:07,WPChill/download-monitor,https://api.github.com/repos/WPChill/download-monitor,closed,Download does not exist & modal popup error.,Bug needs testing,"If the download does not exist and ""No Access Modal"" setting is on, clicking on a link returns a 403 Forbidden error in ajax and no popup with ""Download does not exist"" shows.
+
+To reproduce:
+1 .Create a guttenberg button and add the download link to an non existing download to it ( http://dlm.local?download=999999 )
+2. Activate the ""No Access Modal"" setting
+3. Click the button.",1.0,"Download does not exist & modal popup error. - If the download does not exist and ""No Access Modal"" setting is on, clicking on a link returns a 403 Forbidden error in ajax and no popup with ""Download does not exist"" shows.
+
+To reproduce:
+1 .Create a guttenberg button and add the download link to an non existing download to it ( http://dlm.local?download=999999 )
+2. Activate the ""No Access Modal"" setting
+3. Click the button.",0,download does not exist modal popup error if the download does not exist and no access modal setting is on clicking on a link returns a forbidden error in ajax and no popup with download does not exist shows to reproduce create a guttenberg button and add the download link to an non existing download to it activate the no access modal setting click the button ,0
+49432,6026106923.0,IssuesEvent,2017-06-08 10:22:33,DMPRoadmap/roadmap,https://api.github.com/repos/DMPRoadmap/roadmap,closed,Creating plans for funders without templates,DMPonline-test MVP-v0.3,"Hi, I created a plan for Hartstichting (Dutch Heart Foundation). They don't have a template yet but I was given the DCC generic template. I am told something has changed in the functionality so the programme logic now says that, if a funder doesn't have a template, user gets generic template. Was this intended?",1.0,"Creating plans for funders without templates - Hi, I created a plan for Hartstichting (Dutch Heart Foundation). They don't have a template yet but I was given the DCC generic template. I am told something has changed in the functionality so the programme logic now says that, if a funder doesn't have a template, user gets generic template. Was this intended?",0,creating plans for funders without templates hi i created a plan for hartstichting dutch heart foundation they don t have a template yet but i was given the dcc generic template i am told something has changed in the functionality so the programme logic now says that if a funder doesn t have a template user gets generic template was this intended ,0
+5872,4048669736.0,IssuesEvent,2016-05-23 11:17:17,godotengine/godot,https://api.github.com/repos/godotengine/godot,opened,[Tracker] Drag Drop related issues,enhancement topic:editor tracker usability,"This is a tracker for drag drop related issues:
+
+https://github.com/godotengine/godot/issues/3543 (feature request)
+https://github.com/godotengine/godot/issues/4712 (bug)
+https://github.com/godotengine/godot/issues/4628 (bug)
+https://github.com/godotengine/godot/issues/2505 (feature request)
+https://github.com/godotengine/godot/issues/1030 (feature request)
+",True,"[Tracker] Drag Drop related issues - This is a tracker for drag drop related issues:
+
+https://github.com/godotengine/godot/issues/3543 (feature request)
+https://github.com/godotengine/godot/issues/4712 (bug)
+https://github.com/godotengine/godot/issues/4628 (bug)
+https://github.com/godotengine/godot/issues/2505 (feature request)
+https://github.com/godotengine/godot/issues/1030 (feature request)
+",1, drag drop related issues this is a tracker for drag drop related issues feature request bug bug feature request feature request ,1
+13645,8632060817.0,IssuesEvent,2018-11-22 09:44:46,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,replaying an edited scene after a bug does not replay the former edited scene by default,enhancement topic:editor usability,"**Operating system or device - Godot version:**
+official 2.0.2stable win64
+
+**Issue description** (what happened, and what was expected):
+
+Lets say I have two scene opened into the editor. Scene A and B.
+
+When I work on Scene A and press the ""Play the edited scene"" (F6) and that a bug occurs into one of its scripts, the debugger appears and the ""Play the edited scene"" button is changed into a ""Replay"" button.
+
+If I edit Scene B and press the ""replay"" button, this is Scene B that is played instead of Scene A that should be replayed.
+
+**Steps to reproduce:**
+
+**Link to minimal example project** (optional but very welcome):
+",True,"replaying an edited scene after a bug does not replay the former edited scene by default - **Operating system or device - Godot version:**
+official 2.0.2stable win64
+
+**Issue description** (what happened, and what was expected):
+
+Lets say I have two scene opened into the editor. Scene A and B.
+
+When I work on Scene A and press the ""Play the edited scene"" (F6) and that a bug occurs into one of its scripts, the debugger appears and the ""Play the edited scene"" button is changed into a ""Replay"" button.
+
+If I edit Scene B and press the ""replay"" button, this is Scene B that is played instead of Scene A that should be replayed.
+
+**Steps to reproduce:**
+
+**Link to minimal example project** (optional but very welcome):
+",1,replaying an edited scene after a bug does not replay the former edited scene by default operating system or device godot version official issue description what happened and what was expected lets say i have two scene opened into the editor scene a and b when i work on scene a and press the play the edited scene and that a bug occurs into one of its scripts the debugger appears and the play the edited scene button is changed into a replay button if i edit scene b and press the replay button this is scene b that is played instead of scene a that should be replayed steps to reproduce link to minimal example project optional but very welcome ,1
+100217,8728004502.0,IssuesEvent,2018-12-10 16:18:59,remy/nodemon,https://api.github.com/repos/remy/nodemon,closed,Malware found in dependency (windows / upgrade didn't work fully),needs latest nodemon windows,"On windows machine.
+Xeon E5-2694 v4
+16.0 GB RAM
+Nodemon version: 1.18.7
+Found with Trend Micro OfficeScan
+
+
+### Malware location & description
+#### SHA ENCRYPTED
+- coinminer.win32.malbtc.aa
+- C:\Users\xxx\AppData\Roaming\npm-cache\_cacache\content-v2\sha512\94\0a\
+- b8b4b616(...)
+
+#### APPLICATION ROOT(?)
+- coinminer.js.malbtc.aa
+- C:\Users\xxx\AppData\Roaming\npm\node_modules\nodemon\node_modules\flatmap-stream\
+- index.min.js
+
+
+#### ?
+- coinminer.js.malbtc.aa.component
+- C:\Users\xxx\AppData\Roaming\npm\node_modules\nodemon\node_modules\flatmap-stream\test
+- data.js
+",1.0,"Malware found in dependency (windows / upgrade didn't work fully) - On windows machine.
+Xeon E5-2694 v4
+16.0 GB RAM
+Nodemon version: 1.18.7
+Found with Trend Micro OfficeScan
+
+
+### Malware location & description
+#### SHA ENCRYPTED
+- coinminer.win32.malbtc.aa
+- C:\Users\xxx\AppData\Roaming\npm-cache\_cacache\content-v2\sha512\94\0a\
+- b8b4b616(...)
+
+#### APPLICATION ROOT(?)
+- coinminer.js.malbtc.aa
+- C:\Users\xxx\AppData\Roaming\npm\node_modules\nodemon\node_modules\flatmap-stream\
+- index.min.js
+
+
+#### ?
+- coinminer.js.malbtc.aa.component
+- C:\Users\xxx\AppData\Roaming\npm\node_modules\nodemon\node_modules\flatmap-stream\test
+- data.js
+",0,malware found in dependency windows upgrade didn t work fully on windows machine xeon gb ram nodemon version found with trend micro officescan malware location description sha encrypted coinminer malbtc aa c users xxx appdata roaming npm cache cacache content application root coinminer js malbtc aa c users xxx appdata roaming npm node modules nodemon node modules flatmap stream index min js coinminer js malbtc aa component c users xxx appdata roaming npm node modules nodemon node modules flatmap stream test data js ,0
+77630,27085819763.0,IssuesEvent,2023-02-14 16:55:14,vector-im/element-web,https://api.github.com/repos/vector-im/element-web,opened,Confusing display of custom power level in room user list,T-Defect,"### Steps to reproduce
+
+1. Go to a room that was migrated from Gitter, e.g. https://app.gitter.im/#/room/#ADOdb_ADOdb:gitter.im
+2. In the room's People list, notice that users who previously were admins before Gitter migrated to Matrix, are now listed as *Mods*. However, @MadLittleMods informed me that they effectively are Admins, but with a Custom power level of **90** (see [discussion thread](https://matrix.to/#/!IxQMqGgyzZgHKssexF:gitter.im/$5OBWedojqUtnt-S18OT-WAspbZlRbCfxuL6beXvEOuU?via=gitter.im&via=matrix.org&via=aria-net.org)).
+4. Invite a new user, and make them *Moderator*
+6. In the user list, they are shown as **Mod** just like the old admins, but in reality their Power level is **50**
+
+
+
+
+
+
+### Outcome
+
+#### What did you expect?
+
+The People list should display the user's actual power level, and definitely **not** regroup custom power levels with standard ones, which is confusing (and misleading).
+
+#### What happened instead?
+
+Custom power level 90 is displayed as `Mod`
+
+
+### Operating system
+
+Windows
+
+### Browser information
+
+Firefox 102.4.0esr
+
+### URL for webapp
+
+app.gitter.im and app.element.io
+
+### Application version
+
+Version de Gitter : 1.11.23-rc.1 Version de Olm : 3.2.12 / Version de Element : 1.11.23 Version de Olm : 3.2.12
+
+### Homeserver
+
+gitter.im and matrix.org
+
+### Will you send logs?
+
+No",1.0,"Confusing display of custom power level in room user list - ### Steps to reproduce
+
+1. Go to a room that was migrated from Gitter, e.g. https://app.gitter.im/#/room/#ADOdb_ADOdb:gitter.im
+2. In the room's People list, notice that users who previously were admins before Gitter migrated to Matrix, are now listed as *Mods*. However, @MadLittleMods informed me that they effectively are Admins, but with a Custom power level of **90** (see [discussion thread](https://matrix.to/#/!IxQMqGgyzZgHKssexF:gitter.im/$5OBWedojqUtnt-S18OT-WAspbZlRbCfxuL6beXvEOuU?via=gitter.im&via=matrix.org&via=aria-net.org)).
+4. Invite a new user, and make them *Moderator*
+6. In the user list, they are shown as **Mod** just like the old admins, but in reality their Power level is **50**
+
+
+
+
+
+
+### Outcome
+
+#### What did you expect?
+
+The People list should display the user's actual power level, and definitely **not** regroup custom power levels with standard ones, which is confusing (and misleading).
+
+#### What happened instead?
+
+Custom power level 90 is displayed as `Mod`
+
+
+### Operating system
+
+Windows
+
+### Browser information
+
+Firefox 102.4.0esr
+
+### URL for webapp
+
+app.gitter.im and app.element.io
+
+### Application version
+
+Version de Gitter : 1.11.23-rc.1 Version de Olm : 3.2.12 / Version de Element : 1.11.23 Version de Olm : 3.2.12
+
+### Homeserver
+
+gitter.im and matrix.org
+
+### Will you send logs?
+
+No",0,confusing display of custom power level in room user list steps to reproduce go to a room that was migrated from gitter e g in the room s people list notice that users who previously were admins before gitter migrated to matrix are now listed as mods however madlittlemods informed me that they effectively are admins but with a custom power level of see invite a new user and make them moderator in the user list they are shown as mod just like the old admins but in reality their power level is outcome what did you expect the people list should display the user s actual power level and definitely not regroup custom power levels with standard ones which is confusing and misleading what happened instead custom power level is displayed as mod operating system windows browser information firefox url for webapp app gitter im and app element io application version version de gitter rc version de olm version de element version de olm homeserver gitter im and matrix org will you send logs no,0
+29924,11786085083.0,IssuesEvent,2020-03-17 11:33:40,scriptex/webpack-mpa-next,https://api.github.com/repos/scriptex/webpack-mpa-next,closed,CVE-2020-7598 (High) detected in multiple libraries,security vulnerability,"## CVE-2020-7598 - High Severity Vulnerability
+ Vulnerable Libraries - minimist-0.0.8.tgz, minimist-1.1.3.tgz, minimist-0.0.10.tgz, minimist-1.2.0.tgz
+
+
+minimist-0.0.8.tgz
+
+parse argument options
+Library home page: https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz
+Path to dependency file: /tmp/ws-scm/webpack-mpa-next/package.json
+Path to vulnerable library: /tmp/ws-scm/webpack-mpa-next/node_modules/mkdirp/node_modules/minimist/package.json
+
+
+Dependency Hierarchy:
+ - babel-loader-8.0.6.tgz (Root Library)
+ - mkdirp-0.5.1.tgz
+ - :x: **minimist-0.0.8.tgz** (Vulnerable Library)
+
minimist-1.1.3.tgz
+
+parse argument options
+Library home page: https://registry.npmjs.org/minimist/-/minimist-1.1.3.tgz
+Path to dependency file: /tmp/ws-scm/webpack-mpa-next/package.json
+Path to vulnerable library: /tmp/ws-scm/webpack-mpa-next/node_modules/gonzales-pe/node_modules/minimist/package.json
+
+
+Dependency Hierarchy:
+ - stylelint-13.2.1.tgz (Root Library)
+ - postcss-sass-0.4.2.tgz
+ - gonzales-pe-4.2.4.tgz
+ - :x: **minimist-1.1.3.tgz** (Vulnerable Library)
+
minimist-0.0.10.tgz
+
+parse argument options
+Library home page: https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz
+Path to dependency file: /tmp/ws-scm/webpack-mpa-next/package.json
+Path to vulnerable library: /tmp/ws-scm/webpack-mpa-next/node_modules/optimist/node_modules/minimist/package.json
+
+
+Dependency Hierarchy:
+ - webpack-spritesmith-1.1.0.tgz (Root Library)
+ - spritesheet-templates-10.5.0.tgz
+ - handlebars-4.7.3.tgz
+ - optimist-0.6.1.tgz
+ - :x: **minimist-0.0.10.tgz** (Vulnerable Library)
+
minimist-1.2.0.tgz
+
+parse argument options
+Library home page: https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz
+
+
+Dependency Hierarchy:
+ - browser-sync-2.26.7.tgz (Root Library)
+ - chokidar-2.1.8.tgz
+ - fsevents-1.2.11.tgz
+ - node-pre-gyp-0.14.0.tgz
+ - rc-1.2.8.tgz
+ - :x: **minimist-1.2.0.tgz** (Vulnerable Library)
+
Found in HEAD commit: ae3b121e2fab0097052d10d972f83d82dec89875
+
+
+
+ Vulnerability Details
+
+
+minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a ""constructor"" or ""__proto__"" payload.
+
+
Publish Date: 2020-03-11
+
URL: CVE-2020-7598
+
+ CVSS 3 Score Details (9.8)
+
+
+Base Score Metrics:
+- Exploitability Metrics:
+ - Attack Vector: Network
+ - Attack Complexity: Low
+ - Privileges Required: None
+ - User Interaction: None
+ - Scope: Unchanged
+- Impact Metrics:
+ - Confidentiality Impact: High
+ - Integrity Impact: High
+ - Availability Impact: High
+
+For more information on CVSS3 Scores, click here.
+
+ Suggested Fix
+
+
+
Type: Upgrade version
+Origin: https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94
+Release Date: 2020-03-11
+Fix Resolution: minimist - 0.2.1,1.2.2
+
+
+ Vulnerable Libraries - minimist-0.0.8.tgz, minimist-1.1.3.tgz, minimist-0.0.10.tgz, minimist-1.2.0.tgz
+
+
+minimist-0.0.8.tgz
+
+parse argument options
+Library home page: https://registry.npmjs.org/minimist/-/minimist-0.0.8.tgz
+Path to dependency file: /tmp/ws-scm/webpack-mpa-next/package.json
+Path to vulnerable library: /tmp/ws-scm/webpack-mpa-next/node_modules/mkdirp/node_modules/minimist/package.json
+
+
+Dependency Hierarchy:
+ - babel-loader-8.0.6.tgz (Root Library)
+ - mkdirp-0.5.1.tgz
+ - :x: **minimist-0.0.8.tgz** (Vulnerable Library)
+
minimist-1.1.3.tgz
+
+parse argument options
+Library home page: https://registry.npmjs.org/minimist/-/minimist-1.1.3.tgz
+Path to dependency file: /tmp/ws-scm/webpack-mpa-next/package.json
+Path to vulnerable library: /tmp/ws-scm/webpack-mpa-next/node_modules/gonzales-pe/node_modules/minimist/package.json
+
+
+Dependency Hierarchy:
+ - stylelint-13.2.1.tgz (Root Library)
+ - postcss-sass-0.4.2.tgz
+ - gonzales-pe-4.2.4.tgz
+ - :x: **minimist-1.1.3.tgz** (Vulnerable Library)
+
minimist-0.0.10.tgz
+
+parse argument options
+Library home page: https://registry.npmjs.org/minimist/-/minimist-0.0.10.tgz
+Path to dependency file: /tmp/ws-scm/webpack-mpa-next/package.json
+Path to vulnerable library: /tmp/ws-scm/webpack-mpa-next/node_modules/optimist/node_modules/minimist/package.json
+
+
+Dependency Hierarchy:
+ - webpack-spritesmith-1.1.0.tgz (Root Library)
+ - spritesheet-templates-10.5.0.tgz
+ - handlebars-4.7.3.tgz
+ - optimist-0.6.1.tgz
+ - :x: **minimist-0.0.10.tgz** (Vulnerable Library)
+
minimist-1.2.0.tgz
+
+parse argument options
+Library home page: https://registry.npmjs.org/minimist/-/minimist-1.2.0.tgz
+
+
+Dependency Hierarchy:
+ - browser-sync-2.26.7.tgz (Root Library)
+ - chokidar-2.1.8.tgz
+ - fsevents-1.2.11.tgz
+ - node-pre-gyp-0.14.0.tgz
+ - rc-1.2.8.tgz
+ - :x: **minimist-1.2.0.tgz** (Vulnerable Library)
+
Found in HEAD commit: ae3b121e2fab0097052d10d972f83d82dec89875
+
+
+
+ Vulnerability Details
+
+
+minimist before 1.2.2 could be tricked into adding or modifying properties of Object.prototype using a ""constructor"" or ""__proto__"" payload.
+
+
Publish Date: 2020-03-11
+
URL: CVE-2020-7598
+
+ CVSS 3 Score Details (9.8)
+
+
+Base Score Metrics:
+- Exploitability Metrics:
+ - Attack Vector: Network
+ - Attack Complexity: Low
+ - Privileges Required: None
+ - User Interaction: None
+ - Scope: Unchanged
+- Impact Metrics:
+ - Confidentiality Impact: High
+ - Integrity Impact: High
+ - Availability Impact: High
+
+For more information on CVSS3 Scores, click here.
+
+ Suggested Fix
+
+
+
Type: Upgrade version
+Origin: https://github.com/substack/minimist/commit/63e7ed05aa4b1889ec2f3b196426db4500cbda94
+Release Date: 2020-03-11
+Fix Resolution: minimist - 0.2.1,1.2.2
+
+
+
+ View the screenshot
+ ![]()
+
+
+
+Browser Configuration
+
+
+
+_From [webcompat.com](https://webcompat.com/) with ❤️_",1.0,"users.sch.gr - desktop site instead of mobile site -
+
+
+
+**URL**: http://users.sch.gr/kodulis/quizJS/testBrowsers.html
+
+**Browser / Version**: Firefox 83.0
+**Operating System**: Windows 10
+**Tested Another Browser**: Yes Chrome
+
+**Problem type**: Desktop site instead of mobile site
+**Description**: Desktop site instead of mobile site
+**Steps to Reproduce**:
+Flex box lost its functionality after 26 October 2020. Can not stretch two images INSIDE a flex div, they overflow OUTSIDE the box. See my special designed page which proudly demonstrated this functionality. A functionality no other browser supported.
+Until at least 26/10/2020 the 2 images (bull and Hopper) streched without distortion inside the blue flex box (anytimes I inserted them). Now unfortunately they overflow OUTSIDE the box. What is going on?
+
+ View the screenshot
+ ![]()
+
+
+
+Browser Configuration
+
+
+
+_From [webcompat.com](https://webcompat.com/) with ❤️_",0,users sch gr desktop site instead of mobile site url browser version firefox operating system windows tested another browser yes chrome problem type desktop site instead of mobile site description desktop site instead of mobile site steps to reproduce flex box lost its functionality after october can not stretch two images inside a flex div they overflow outside the box see my special designed page which proudly demonstrated this functionality a functionality no other browser supported until at least the images bull and hopper streched without distortion inside the blue flex box anytimes i inserted them now unfortunately they overflow outside the box what is going on view the screenshot img alt screenshot src browser configuration none from with ❤️ ,0
+59102,11944994694.0,IssuesEvent,2020-04-03 04:19:40,home-assistant/brands,https://api.github.com/repos/home-assistant/brands,closed,OpenTherm Gateway is missing brand images,has-codeowner has-config-flow,"
+
+## The problem
+
+
+The OpenTherm Gateway integration has missing brand images.
+
+We recently started this Brands repository, to create a centralized storage of all brand-related images. These images are used on our website and the Home Assistant frontend.
+
+The following images are missing and would ideally be added:
+
+- `src/opentherm_gw/logo.png`
+- `src/opentherm_gw/icon@2x.png`
+- `src/opentherm_gw/logo@2x.png`
+
+For image specifications and requirements, please see [README.md](https://github.com/home-assistant/brands/blob/master/README.md).
+
+## Additional information
+
+For more information about this repository, read the [README.md](https://github.com/home-assistant/brands/blob/master/README.md) file of this repository. It contains information on how this repository works, and image specification and requirements.
+
+
+## Codeowner mention
+
+Hi there, @mvn23! Mind taking a look at this issue as it is with an integration (opentherm_gw) you are listed as a [codeowner](https://github.com/home-assistant/core/blob/dev/homeassistant/components/opentherm_gw/manifest.json) for? Thanks!
+
+Resolving this issue is not limited to codeowners! If you want to help us out, feel free to resolve this issue! Thanks already!
+",1.0,"OpenTherm Gateway is missing brand images -
+
+## The problem
+
+
+The OpenTherm Gateway integration has missing brand images.
+
+We recently started this Brands repository, to create a centralized storage of all brand-related images. These images are used on our website and the Home Assistant frontend.
+
+The following images are missing and would ideally be added:
+
+- `src/opentherm_gw/logo.png`
+- `src/opentherm_gw/icon@2x.png`
+- `src/opentherm_gw/logo@2x.png`
+
+For image specifications and requirements, please see [README.md](https://github.com/home-assistant/brands/blob/master/README.md).
+
+## Additional information
+
+For more information about this repository, read the [README.md](https://github.com/home-assistant/brands/blob/master/README.md) file of this repository. It contains information on how this repository works, and image specification and requirements.
+
+
+## Codeowner mention
+
+Hi there, @mvn23! Mind taking a look at this issue as it is with an integration (opentherm_gw) you are listed as a [codeowner](https://github.com/home-assistant/core/blob/dev/homeassistant/components/opentherm_gw/manifest.json) for? Thanks!
+
+Resolving this issue is not limited to codeowners! If you want to help us out, feel free to resolve this issue! Thanks already!
+",0,opentherm gateway is missing brand images the problem the opentherm gateway integration has missing brand images we recently started this brands repository to create a centralized storage of all brand related images these images are used on our website and the home assistant frontend the following images are missing and would ideally be added src opentherm gw logo png src opentherm gw icon png src opentherm gw logo png for image specifications and requirements please see additional information for more information about this repository read the file of this repository it contains information on how this repository works and image specification and requirements codeowner mention hi there mind taking a look at this issue as it is with an integration opentherm gw you are listed as a for thanks resolving this issue is not limited to codeowners if you want to help us out feel free to resolve this issue thanks already ,0
+7699,5144880452.0,IssuesEvent,2017-01-12 19:56:02,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Option to change the default PascalCase/CamelCase into snake_case when adding Nodes,feature proposal junior job topic:editor usability,"I am blown away that I can't find an existing issue about this.
+Most people that I know, uses snake_case in all their Godot projects.
+I don't see why we couldn't implement an option to change the PascalCase into snake_case when adding them to the scene :)",True,"Option to change the default PascalCase/CamelCase into snake_case when adding Nodes - I am blown away that I can't find an existing issue about this.
+Most people that I know, uses snake_case in all their Godot projects.
+I don't see why we couldn't implement an option to change the PascalCase into snake_case when adding them to the scene :)",1,option to change the default pascalcase camelcase into snake case when adding nodes i am blown away that i can t find an existing issue about this most people that i know uses snake case in all their godot projects i don t see why we couldn t implement an option to change the pascalcase into snake case when adding them to the scene ,1
+17465,12059421106.0,IssuesEvent,2020-04-15 19:14:37,godotengine/godot,https://api.github.com/repos/godotengine/godot,closed,Node selection outline not shown in editor when node is locked,enhancement topic:editor usability,"**Godot version:**
+3.2
+**OS/device including version:**
+Win 10 1903
+**Issue description:**
+Node selection outline not shown when node is in locked state.
+**Steps to reproduce:**
+Add 2 control nodes to blank scene
+Lock one of the nodes
+The node that is locked will no longer display it's selection outline
+The other (not locked) still will
+**Minimal reproduction project:**
+Blank project with above steps
+
+If the locked layer could be outlined in grey, that would be great. It is helpful in scenarios where you want to better understand the layout of a UI.
+
+If someone would point me in the direction of the files which would deal with this issue, then I could potentially look at it. I tried having a look myself but am not sure where the interaction is between clicking the lock button and the editor display.",True,"Node selection outline not shown in editor when node is locked - **Godot version:**
+3.2
+**OS/device including version:**
+Win 10 1903
+**Issue description:**
+Node selection outline not shown when node is in locked state.
+**Steps to reproduce:**
+Add 2 control nodes to blank scene
+Lock one of the nodes
+The node that is locked will no longer display it's selection outline
+The other (not locked) still will
+**Minimal reproduction project:**
+Blank project with above steps
+
+If the locked layer could be outlined in grey, that would be great. It is helpful in scenarios where you want to better understand the layout of a UI.
+
+If someone would point me in the direction of the files which would deal with this issue, then I could potentially look at it. I tried having a look myself but am not sure where the interaction is between clicking the lock button and the editor display.",1,node selection outline not shown in editor when node is locked godot version os device including version win issue description node selection outline not shown when node is in locked state steps to reproduce add control nodes to blank scene lock one of the nodes the node that is locked will no longer display it s selection outline the other not locked still will minimal reproduction project blank project with above steps if the locked layer could be outlined in grey that would be great it is helpful in scenarios where you want to better understand the layout of a ui if someone would point me in the direction of the files which would deal with this issue then i could potentially look at it i tried having a look myself but am not sure where the interaction is between clicking the lock button and the editor display ,1
+101227,4110828874.0,IssuesEvent,2016-06-07 01:40:40,kubernetes/kubernetes,https://api.github.com/repos/kubernetes/kubernetes,closed,Deployment deployment should support rollover,kind/flake priority/P0 team/ux,"Same test as #22719 but different failure.
+
+https://console.cloud.google.com/storage/kubernetes-jenkins/logs/kubernetes-e2e-gke/7324/
+
+```
+[It] deployment should support rollover
+ /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/deployment.go:71
+May 19 12:53:53.784: INFO: Pod name rollover-pod: Found 0 pods out of 4
+May 19 12:53:58.790: INFO: Pod name rollover-pod: Found 4 pods out of 4
+STEP: ensuring each pod is running
+W0519 12:53:58.790804 4366 request.go:347] Field selector: v1 - pods - metadata.name - test-rollover-controller-1n0xm: need to check if this is versioned correctly.
+W0519 12:53:58.792935 4366 request.go:347] Field selector: v1 - pods - metadata.name - test-rollover-controller-gg7bu: need to check if this is versioned correctly.
+W0519 12:53:58.810121 4366 request.go:347] Field selector: v1 - pods - metadata.name - test-rollover-controller-psxi4: need to check if this is versioned correctly.
+W0519 12:53:59.044348 4366 request.go:347] Field selector: v1 - pods - metadata.name - test-rollover-controller-sbus0: need to check if this is versioned correctly.
+STEP: trying to dial each unique pod
+May 19 12:53:59.123: INFO: Controller rollover-pod: Got non-empty result from replica 1 [test-rollover-controller-1n0xm]: ""\n\n\nWelcome to nginx!\n\n\n\nWelcome to nginx!
\nIf you see this page, the nginx web server is successfully installed and\nworking. Further configuration is required.
\n\nFor online documentation and support please refer to\nnginx.org.
\nCommercial support is available at\nnginx.com.
\n\nThank you for using nginx.
\n\n\n"", 1 of 4 required successes so far
+May 19 12:53:59.220: INFO: Controller rollover-pod: Got non-empty result from replica 2 [test-rollover-controller-gg7bu]: ""\n\n\nWelcome to nginx!\n\n\n\nWelcome to nginx!
\nIf you see this page, the nginx web server is successfully installed and\nworking. Further configuration is required.
\n\nFor online documentation and support please refer to\nnginx.org.
\nCommercial support is available at\nnginx.com.
\n\nThank you for using nginx.
\n\n\n"", 2 of 4 required successes so far
+May 19 12:53:59.299: INFO: Controller rollover-pod: Got non-empty result from replica 3 [test-rollover-controller-psxi4]: ""\n\n\nWelcome to nginx!\n\n\n\nWelcome to nginx!
\nIf you see this page, the nginx web server is successfully installed and\nworking. Further configuration is required.
\n\nFor online documentation and support please refer to\nnginx.org.
\nCommercial support is available at\nnginx.com.
\n\nThank you for using nginx.
\n\n\n"", 3 of 4 required successes so far
+May 19 12:53:59.358: INFO: Controller rollover-pod: Got non-empty result from replica 4 [test-rollover-controller-sbus0]: ""\n\n\nWelcome to nginx!\n\n\n\nWelcome to nginx!
\nIf you see this page, the nginx web server is successfully installed and\nworking. Further configuration is required.
\n\nFor online documentation and support please refer to\nnginx.org.
\nCommercial support is available at\nnginx.com.
\n\nThank you for using nginx.
\n\n\n"", 4 of 4 required successes so far
+May 19 12:54:05.368: INFO: Creating deployment test-rollover-deployment
+May 19 12:54:07.440: INFO: Updating deployment test-rollover-deployment
+May 19 12:59:11.501: INFO: Deployment: kind:"""" apiVersion:"""" . Selector = matchLabels:
+May 19 12:59:11.501: INFO: All old ReplicaSets (1/2) of deployment test-rollover-deployment: kind:"""" apiVersion:"""" . Selector = matchLabels: matchLabels: matchLabels:
+May 19 12:59:11.502: INFO: All old ReplicaSets (2/2) of deployment test-rollover-deployment: kind:"""" apiVersion:"""" . Selector = matchLabels: matchLabels:
+May 19 12:59:11.502: INFO: New ReplicaSet of deployment test-rollover-deployment: kind:"""" apiVersion:"""" . Selector = matchLabels: matchLabels:
+May 19 12:59:11.509: INFO: Pod test-rollover-controller-1n0xm is available: {TypeMeta:{Kind: APIVersion:} ObjectMeta:{Name:test-rollover-controller-1n0xm GenerateName:test-rollover-controller- Namespace:e2e-tests-deployment-oybdc SelfLink:/api/v1/namespaces/e2e-tests-deployment-oybdc/pods/test-rollover-controller-1n0xm UID:6a549fe5-1dfb-11e6-a239-42010af0001e ResourceVersion:2148 Generation:0 CreationTimestamp:{Time:2016-05-19 12:53:53 -0700 PDT} DeletionTimestamp: DeletionGracePeriodSeconds: Labels:map[name:rollover-pod pod:nginx pod-template-hash:1321378927] Annotations:map[kubernetes.io/created-by:{""kind"":""SerializedReference"",""apiVersion"":""v1"",""reference"":{""kind"":""ReplicaSet"",""namespace"":""e2e-tests-deployment-oybdc"",""name"":""test-rollover-controller"",""uid"":""6a49adea-1dfb-11e6-a239-42010af0001e"",""apiVersion"":""extensions"",""resourceVersion"":""1451""}}
+] OwnerReferences:[] Finalizers:[]} Spec:{Volumes:[{Name:default-token-h8oc4 VolumeSource:{HostPath: EmptyDir: GCEPersistentDisk: AWSElasticBlockStore: GitRepo: Secret:0xc820bec7e0 NFS: ISCSI: Glusterfs: PersistentVolumeClaim: RBD: FlexVolume: Cinder: CephFS: Flocker: DownwardAPI: FC: AzureFile: ConfigMap:}}] InitContainers:[] Containers:[{Name:nginx Image:gcr.io/google_containers/nginx:1.7.9 Command:[] Args:[] WorkingDir: Ports:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-h8oc4 ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath:}] LivenessProbe: ReadinessProbe: Lifecycle: TerminationMessagePath:/dev/termination-log ImagePullPolicy:IfNotPresent SecurityContext: Stdin:false StdinOnce:false TTY:false}] RestartPolicy:Always TerminationGracePeriodSeconds:0xc820bec7f0 ActiveDeadlineSeconds: DNSPolicy:ClusterFirst NodeSelector:map[] ServiceAccountName:default NodeName:gke-jenkins-e2e-default-pool-b9f48651-3w70 SecurityContext:0xc820010bc0 ImagePullSecrets:[] Hostname: Subdomain:} Status:{Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:{Time:0001-01-01 00:00:00 +0000 UTC} LastTransitionTime:{Time:2016-05-19 12:53:53 -0700 PDT} Reason: Message:} {Type:Ready Status:True LastProbeTime:{Time:0001-01-01 00:00:00 +0000 UTC} LastTransitionTime:{Time:2016-05-19 12:53:56 -0700 PDT} Reason: Message:} {Type:PodScheduled Status:True LastProbeTime:{Time:0001-01-01 00:00:00 +0000 UTC} LastTransitionTime:{Time:2016-05-19 12:53:53 -0700 PDT} Reason: Message:}] Message: Reason: HostIP:10.240.0.5 PodIP:10.180.2.14 StartTime:2016-05-19T12:53:53-07:00 InitContainerStatuses:[] ContainerStatuses:[{Name:nginx State:{Waiting: Running:0xc820bebb80 Terminated:} LastTerminationState:{Waiting: Running: Terminated:} Ready:true RestartCount:0 Image:gcr.io/google_containers/nginx:1.7.9 ImageID:docker://7332861f06d0f1487265e8c3d99bb8800df8e6770e11ad1fe5a7c580362c2a80 ContainerID:docker://fda2a1e9ab67db66a4173a76f5cbc266981ecff08f096f188eff8cbfa04fae77}]}}
+May 19 12:59:11.510: INFO: Pod test-rollover-controller-gg7bu is available: {TypeMeta:{Kind: APIVersion:} ObjectMeta:{Name:test-rollover-controller-gg7bu GenerateName:test-rollover-controller- Namespace:e2e-tests-deployment-oybdc SelfLink:/api/v1/namespaces/e2e-tests-deployment-oybdc/pods/test-rollover-controller-gg7bu UID:6a505141-1dfb-11e6-a239-42010af0001e ResourceVersion:2151 Generation:0 CreationTimestamp:{Time:2016-05-19 12:53:53 -0700 PDT} DeletionTimestamp: DeletionGracePeriodSeconds: Labels:map[name:rollover-pod pod:nginx pod-template-hash:1321378927] Annotations:map[kubernetes.io/created-by:{""kind"":""SerializedReference"",""apiVersion"":""v1"",""reference"":{""kind"":""ReplicaSet"",""namespace"":""e2e-tests-deployment-oybdc"",""name"":""test-rollover-controller"",""uid"":""6a49adea-1dfb-11e6-a239-42010af0001e"",""apiVersion"":""extensions"",""resourceVersion"":""1451""}}
+] OwnerReferences:[] Finalizers:[]} Spec:{Volumes:[{Name:default-token-h8oc4 VolumeSource:{HostPath: EmptyDir: GCEPersistentDisk: AWSElasticBlockStore: GitRepo: Secret:0xc820bec800 NFS: ISCSI: Glusterfs: PersistentVolumeClaim: RBD: FlexVolume: Cinder: CephFS: Flocker: DownwardAPI: FC: AzureFile: ConfigMap:}}] InitContainers:[] Containers:[{Name:nginx Image:gcr.io/google_containers/nginx:1.7.9 Command:[] Args:[] WorkingDir: Ports:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-h8oc4 ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath:}] LivenessProbe: ReadinessProbe: Lifecycle: TerminationMessagePath:/dev/termination-log ImagePullPolicy:IfNotPresent SecurityContext: Stdin:false StdinOnce:false TTY:false}] RestartPolicy:Always TerminationGracePeriodSeconds:0xc820bec7f8 ActiveDeadlineSeconds: DNSPolicy:ClusterFirst NodeSelector:map[] ServiceAccountName:default NodeName:gke-jenkins-e2e-default-pool-b9f48651-wnyy SecurityContext:0xc820010dc0 ImagePullSecrets:[] Hostname: Subdomain:} Status:{Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:{Time:0001-01-01 00:00:00 +0000 UTC} LastTransitionTime:{Time:2016-05-19 12:53:53 -0700 PDT} Reason: Message:} {Type:Ready Status:True LastProbeTime:{Time:0001-01-01 00:00:00 +0000 UTC} LastTransitionTime:{Time:2016-05-19 12:53:58 -0700 PDT} Reason: Message:} {Type:PodScheduled Status:True LastProbeTime:{Time:0001-01-01 00:00:00 +0000 UTC} LastTransitionTime:{Time:2016-05-19 12:53:53 -0700 PDT} Reason: Message:}] Message: Reason: HostIP:10.240.0.4 PodIP:10.180.0.16 StartTime:2016-05-19T12:53:53-07:00 InitContainerStatuses:[] ContainerStatuses:[{Name:nginx State:{Waiting: Running:0xc820bebbc0 Terminated:} LastTerminationState:{Waiting: Running: Terminated:} Ready:true RestartCount:0 Image:gcr.io/google_containers/nginx:1.7.9 ImageID:docker://7332861f06d0f1487265e8c3d99bb8800df8e6770e11ad1fe5a7c580362c2a80 ContainerID:docker://11a24322c7705325a5aa508936368e67faa926c98220e459c91cb8f0450f217a}]}}
+May 19 12:59:11.510: INFO: Pod test-rollover-controller-sbus0 is available: {TypeMeta:{Kind: APIVersion:} ObjectMeta:{Name:test-rollover-controller-sbus0 GenerateName:test-rollover-controller- Namespace:e2e-tests-deployment-oybdc SelfLink:/api/v1/namespaces/e2e-tests-deployment-oybdc/pods/test-rollover-controller-sbus0 UID:6a54c8a3-1dfb-11e6-a239-42010af0001e ResourceVersion:2159 Generation:0 CreationTimestamp:{Time:2016-05-19 12:53:53 -0700 PDT} DeletionTimestamp: DeletionGracePeriodSeconds: Labels:map[pod:nginx pod-template-hash:1321378927 name:rollover-pod] Annotations:map[kubernetes.io/created-by:{""kind"":""SerializedReference"",""apiVersion"":""v1"",""reference"":{""kind"":""ReplicaSet"",""namespace"":""e2e-tests-deployment-oybdc"",""name"":""test-rollover-controller"",""uid"":""6a49adea-1dfb-11e6-a239-42010af0001e"",""apiVersion"":""extensions"",""resourceVersion"":""1451""}}
+] OwnerReferences:[] Finalizers:[]} Spec:{Volumes:[{Name:default-token-h8oc4 VolumeSource:{HostPath: EmptyDir: GCEPersistentDisk: AWSElasticBlockStore: GitRepo: Secret:0xc820bec810 NFS: ISCSI: Glusterfs: PersistentVolumeClaim: RBD: FlexVolume: Cinder: CephFS: Flocker: DownwardAPI: FC: AzureFile: ConfigMap:}}] InitContainers:[] Containers:[{Name:nginx Image:gcr.io/google_containers/nginx:1.7.9 Command:[] Args:[] WorkingDir: Ports:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-h8oc4 ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath:}] LivenessProbe: ReadinessProbe: Lifecycle: TerminationMessagePath:/dev/termination-log ImagePullPolicy:IfNotPresent SecurityContext: Stdin:false StdinOnce:false TTY:false}] RestartPolicy:Always TerminationGracePeriodSeconds:0xc820bec820 ActiveDeadlineSeconds: DNSPolicy:ClusterFirst NodeSelector:map[] ServiceAccountName:default NodeName:gke-jenkins-e2e-default-pool-b9f48651-07l9 SecurityContext:0xc8200110c0 ImagePullSecrets:[] Hostname: Subdomain:} Status:{Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:{Time:0001-01-01 00:00:00 +0000 UTC} LastTransitionTime:{Time:2016-05-19 12:53:53 -0700 PDT} Reason: Message:} {Type:Ready Status:True LastProbeTime:{Time:0001-01-01 00:00:00 +0000 UTC} LastTransitionTime:{Time:2016-05-19 12:53:55 -0700 PDT} Reason: Message:} {Type:PodScheduled Status:True LastProbeTime:{Time:0001-01-01 00:00:00 +0000 UTC} LastTransitionTime:{Time:2016-05-19 12:53:54 -0700 PDT} Reason: Message:}] Message: Reason: HostIP:10.240.0.6 PodIP:10.180.1.14 StartTime:2016-05-19T12:53:53-07:00 InitContainerStatuses:[] ContainerStatuses:[{Name:nginx State:{Waiting: Running:0xc820bebc00 Terminated:} LastTerminationState:{Waiting: Running: Terminated:} Ready:true RestartCount:0 Image:gcr.io/google_containers/nginx:1.7.9 ImageID:docker://7332861f06d0f1487265e8c3d99bb8800df8e6770e11ad1fe5a7c580362c2a80 ContainerID:docker://0c45e77b044e4a6afe13f5b4642ca5137baea3adcea14004e95000c080f61057}]}}
+May 19 12:59:11.510: INFO: Pod test-rollover-deployment-3104088211-a84by is available: {TypeMeta:{Kind: APIVersion:} ObjectMeta:{Name:test-rollover-deployment-3104088211-a84by GenerateName:test-rollover-deployment-3104088211- Namespace:e2e-tests-deployment-oybdc SelfLink:/api/v1/namespaces/e2e-tests-deployment-oybdc/pods/test-rollover-deployment-3104088211-a84by UID:81ca06e1-1dfb-11e6-a239-42010af0001e ResourceVersion:3211 Generation:0 CreationTimestamp:{Time:2016-05-19 12:54:33 -0700 PDT} DeletionTimestamp: DeletionGracePeriodSeconds: Labels:map[name:rollover-pod pod-template-hash:3104088211] Annotations:map[kubernetes.io/created-by:{""kind"":""SerializedReference"",""apiVersion"":""v1"",""reference"":{""kind"":""ReplicaSet"",""namespace"":""e2e-tests-deployment-oybdc"",""name"":""test-rollover-deployment-3104088211"",""uid"":""7273bd6e-1dfb-11e6-a239-42010af0001e"",""apiVersion"":""extensions"",""resourceVersion"":""3146""}}
+] OwnerReferences:[] Finalizers:[]} Spec:{Volumes:[{Name:default-token-h8oc4 VolumeSource:{HostPath: EmptyDir: GCEPersistentDisk: AWSElasticBlockStore: GitRepo: Secret:0xc8209a5ea0 NFS: ISCSI: Glusterfs: PersistentVolumeClaim: RBD: FlexVolume: Cinder: CephFS: Flocker: DownwardAPI: FC: AzureFile: ConfigMap:}}] InitContainers:[] Containers:[{Name:redis Image:gcr.io/google_containers/redis:e2e Command:[] Args:[] WorkingDir: Ports:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-h8oc4 ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath:}] LivenessProbe: ReadinessProbe: Lifecycle: TerminationMessagePath:/dev/termination-log ImagePullPolicy:IfNotPresent SecurityContext: Stdin:false StdinOnce:false TTY:false}] RestartPolicy:Always TerminationGracePeriodSeconds:0xc8209a5eb0 ActiveDeadlineSeconds: DNSPolicy:ClusterFirst NodeSelector:map[] ServiceAccountName:default NodeName:gke-jenkins-e2e-default-pool-b9f48651-3w70 SecurityContext:0xc820a50900 ImagePullSecrets:[] Hostname: Subdomain:} Status:{Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:{Time:0001-01-01 00:00:00 +0000 UTC} LastTransitionTime:{Time:2016-05-19 12:54:33 -0700 PDT} Reason: Message:} {Type:Ready Status:True LastProbeTime:{Time:0001-01-01 00:00:00 +0000 UTC} LastTransitionTime:{Time:2016-05-19 12:54:35 -0700 PDT} Reason: Message:} {Type:PodScheduled Status:True LastProbeTime:{Time:0001-01-01 00:00:00 +0000 UTC} LastTransitionTime:{Time:2016-05-19 12:54:33 -0700 PDT} Reason: Message:}] Message: Reason: HostIP:10.240.0.5 PodIP:10.180.2.3 StartTime:2016-05-19T12:54:33-07:00 InitContainerStatuses:[] ContainerStatuses:[{Name:redis State:{Waiting: Running:0xc820dd8980 Terminated:} LastTerminationState:{Waiting: Running: Terminated:} Ready:true RestartCount:0 Image:gcr.io/google_containers/redis:e2e ImageID:docker://e5f6c5a2b5646828f51e8e0d30a2987df7e8183ab2c3ed0ca19eaa03cc5db08c ContainerID:docker://8ccd03769c41cf2757c2eba728342d3ca0024db4c35627738f8ed141b445b47c}]}}
+May 19 12:59:11.510: INFO: Pod test-rollover-deployment-3104088211-cc8bz is available: {TypeMeta:{Kind: APIVersion:} ObjectMeta:{Name:test-rollover-deployment-3104088211-cc8bz GenerateName:test-rollover-deployment-3104088211- Namespace:e2e-tests-deployment-oybdc SelfLink:/api/v1/namespaces/e2e-tests-deployment-oybdc/pods/test-rollover-deployment-3104088211-cc8bz UID:72a1aa22-1dfb-11e6-a239-42010af0001e ResourceVersion:2399 Generation:0 CreationTimestamp:{Time:2016-05-19 12:54:07 -0700 PDT} DeletionTimestamp: DeletionGracePeriodSeconds: Labels:map[name:rollover-pod pod-template-hash:3104088211] Annotations:map[kubernetes.io/created-by:{""kind"":""SerializedReference"",""apiVersion"":""v1"",""reference"":{""kind"":""ReplicaSet"",""namespace"":""e2e-tests-deployment-oybdc"",""name"":""test-rollover-deployment-3104088211"",""uid"":""7273bd6e-1dfb-11e6-a239-42010af0001e"",""apiVersion"":""extensions"",""resourceVersion"":""2284""}}
+] OwnerReferences:[] Finalizers:[]} Spec:{Volumes:[{Name:default-token-h8oc4 VolumeSource:{HostPath: EmptyDir: GCEPersistentDisk: AWSElasticBlockStore: GitRepo: Secret:0xc8209a5ec0 NFS: ISCSI: Glusterfs: PersistentVolumeClaim: RBD: FlexVolume: Cinder: CephFS: Flocker: DownwardAPI: FC: AzureFile: ConfigMap:}}] InitContainers:[] Containers:[{Name:redis Image:gcr.io/google_containers/redis:e2e Command:[] Args:[] WorkingDir: Ports:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-h8oc4 ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath:}] LivenessProbe: ReadinessProbe: Lifecycle: TerminationMessagePath:/dev/termination-log ImagePullPolicy:IfNotPresent SecurityContext: Stdin:false StdinOnce:false TTY:false}] RestartPolicy:Always TerminationGracePeriodSeconds:0xc8209a5eb8 ActiveDeadlineSeconds: DNSPolicy:ClusterFirst NodeSelector:map[] ServiceAccountName:default NodeName:gke-jenkins-e2e-default-pool-b9f48651-wnyy SecurityContext:0xc820a50980 ImagePullSecrets:[] Hostname: Subdomain:} Status:{Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:{Time:0001-01-01 00:00:00 +0000 UTC} LastTransitionTime:{Time:2016-05-19 12:54:07 -0700 PDT} Reason: Message:} {Type:Ready Status:True LastProbeTime:{Time:0001-01-01 00:00:00 +0000 UTC} LastTransitionTime:{Time:2016-05-19 12:54:08 -0700 PDT} Reason: Message:} {Type:PodScheduled Status:True LastProbeTime:{Time:0001-01-01 00:00:00 +0000 UTC} LastTransitionTime:{Time:2016-05-19 12:54:07 -0700 PDT} Reason: Message:}] Message: Reason: HostIP:10.240.0.4 PodIP:10.180.0.15 StartTime:2016-05-19T12:54:07-07:00 InitContainerStatuses:[] ContainerStatuses:[{Name:redis State:{Waiting: Running:0xc820dd89c0 Terminated:} LastTerminationState:{Waiting: Running: Terminated:} Ready:true RestartCount:0 Image:gcr.io/google_containers/redis:e2e ImageID:docker://e5f6c5a2b5646828f51e8e0d30a2987df7e8183ab2c3ed0ca19eaa03cc5db08c ContainerID:docker://8acf88086bb1745f5172731e1f8c1c527c923c3fc0162632f0369e9fc1ec2f0e}]}}
+May 19 12:59:11.510: INFO: Pod test-rollover-deployment-3104088211-vme5t is available: {TypeMeta:{Kind: APIVersion:} ObjectMeta:{Name:test-rollover-deployment-3104088211-vme5t GenerateName:test-rollover-deployment-3104088211- Namespace:e2e-tests-deployment-oybdc SelfLink:/api/v1/namespaces/e2e-tests-deployment-oybdc/pods/test-rollover-deployment-3104088211-vme5t UID:72a285b7-1dfb-11e6-a239-42010af0001e ResourceVersion:3289 Generation:0 CreationTimestamp:{Time:2016-05-19 12:54:07 -0700 PDT} DeletionTimestamp: DeletionGracePeriodSeconds: Labels:map[pod-template-hash:3104088211 name:rollover-pod] Annotations:map[kubernetes.io/created-by:{""kind"":""SerializedReference"",""apiVersion"":""v1"",""reference"":{""kind"":""ReplicaSet"",""namespace"":""e2e-tests-deployment-oybdc"",""name"":""test-rollover-deployment-3104088211"",""uid"":""7273bd6e-1dfb-11e6-a239-42010af0001e"",""apiVersion"":""extensions"",""resourceVersion"":""2284""}}
+] OwnerReferences:[] Finalizers:[]} Spec:{Volumes:[{Name:default-token-h8oc4 VolumeSource:{HostPath: EmptyDir: GCEPersistentDisk: AWSElasticBlockStore: GitRepo: Secret:0xc8209a5ed0 NFS: ISCSI: Glusterfs: PersistentVolumeClaim: RBD: FlexVolume: Cinder: CephFS: Flocker: DownwardAPI: FC: AzureFile: ConfigMap:}}] InitContainers:[] Containers:[{Name:redis Image:gcr.io/google_containers/redis:e2e Command:[] Args:[] WorkingDir: Ports:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-h8oc4 ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath:}] LivenessProbe: ReadinessProbe: Lifecycle: TerminationMessagePath:/dev/termination-log ImagePullPolicy:IfNotPresent SecurityContext: Stdin:false StdinOnce:false TTY:false}] RestartPolicy:Always TerminationGracePeriodSeconds:0xc8209a5ee0 ActiveDeadlineSeconds: DNSPolicy:ClusterFirst NodeSelector:map[] ServiceAccountName:default NodeName:gke-jenkins-e2e-default-pool-b9f48651-07l9 SecurityContext:0xc820a50a00 ImagePullSecrets:[] Hostname: Subdomain:} Status:{Phase:Running Conditions:[{Type:Initialized Status:True LastProbeTime:{Time:0001-01-01 00:00:00 +0000 UTC} LastTransitionTime:{Time:2016-05-19 12:54:07 -0700 PDT} Reason: Message:} {Type:Ready Status:True LastProbeTime:{Time:0001-01-01 00:00:00 +0000 UTC} LastTransitionTime:{Time:2016-05-19 12:54:39 -0700 PDT} Reason: Message:} {Type:PodScheduled Status:True LastProbeTime:{Time:0001-01-01 00:00:00 +0000 UTC} LastTransitionTime:{Time:2016-05-19 12:54:07 -0700 PDT} Reason: Message:}] Message: Reason: HostIP:10.240.0.6 PodIP:10.180.1.12 StartTime:2016-05-19T12:54:07-07:00 InitContainerStatuses:[] ContainerStatuses:[{Name:redis State:{Waiting: Running:0xc820dd8a00 Terminated:} LastTerminationState:{Waiting: Running: Terminated:} Ready:true RestartCount:0 Image:gcr.io/google_containers/redis:e2e ImageID:docker://e5f6c5a2b5646828f51e8e0d30a2987df7e8183ab2c3ed0ca19eaa03cc5db08c ContainerID:docker://f9eb83c777573747dde4a51a7f06ac41958aa03e44e879118922313f19d45c44}]}}
+May 19 12:59:11.513: INFO: Deleting deployment test-rollover-deployment
+[AfterEach] [k8s.io] Deployment
+ /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:109
+STEP: Collecting events from namespace ""e2e-tests-deployment-oybdc"".
+May 19 13:00:11.603: INFO: At {2016-05-19 12:53:53 -0700 PDT} - event for test-rollover-controller: {replicaset-controller } SuccessfulCreate: Created pod: test-rollover-controller-sbus0
+May 19 13:00:11.603: INFO: At {2016-05-19 12:53:53 -0700 PDT} - event for test-rollover-controller: {replicaset-controller } SuccessfulCreate: Created pod: test-rollover-controller-1n0xm
+May 19 13:00:11.603: INFO: At {2016-05-19 12:53:53 -0700 PDT} - event for test-rollover-controller: {replicaset-controller } SuccessfulCreate: Created pod: test-rollover-controller-psxi4
+May 19 13:00:11.603: INFO: At {2016-05-19 12:53:53 -0700 PDT} - event for test-rollover-controller: {replicaset-controller } SuccessfulCreate: Created pod: test-rollover-controller-gg7bu
+May 19 13:00:11.603: INFO: At {2016-05-19 12:53:53 -0700 PDT} - event for test-rollover-controller-gg7bu: {default-scheduler } Scheduled: Successfully assigned test-rollover-controller-gg7bu to gke-jenkins-e2e-default-pool-b9f48651-wnyy
+May 19 13:00:11.603: INFO: At {2016-05-19 12:53:54 -0700 PDT} - event for test-rollover-controller-1n0xm: {default-scheduler } Scheduled: Successfully assigned test-rollover-controller-1n0xm to gke-jenkins-e2e-default-pool-b9f48651-3w70
+May 19 13:00:11.603: INFO: At {2016-05-19 12:53:54 -0700 PDT} - event for test-rollover-controller-psxi4: {default-scheduler } Scheduled: Successfully assigned test-rollover-controller-psxi4 to gke-jenkins-e2e-default-pool-b9f48651-wnyy
+May 19 13:00:11.603: INFO: At {2016-05-19 12:53:54 -0700 PDT} - event for test-rollover-controller-sbus0: {default-scheduler } Scheduled: Successfully assigned test-rollover-controller-sbus0 to gke-jenkins-e2e-default-pool-b9f48651-07l9
+May 19 13:00:11.603: INFO: At {2016-05-19 12:53:54 -0700 PDT} - event for test-rollover-controller-sbus0: {kubelet gke-jenkins-e2e-default-pool-b9f48651-07l9} Created: Created container with docker id 0c45e77b044e
+May 19 13:00:11.603: INFO: At {2016-05-19 12:53:54 -0700 PDT} - event for test-rollover-controller-sbus0: {kubelet gke-jenkins-e2e-default-pool-b9f48651-07l9} Pulled: Container image ""gcr.io/google_containers/nginx:1.7.9"" already present on machine
+May 19 13:00:11.603: INFO: At {2016-05-19 12:53:55 -0700 PDT} - event for test-rollover-controller-1n0xm: {kubelet gke-jenkins-e2e-default-pool-b9f48651-3w70} Pulled: Container image ""gcr.io/google_containers/nginx:1.7.9"" already present on machine
+May 19 13:00:11.603: INFO: At {2016-05-19 12:53:55 -0700 PDT} - event for test-rollover-controller-1n0xm: {kubelet gke-jenkins-e2e-default-pool-b9f48651-3w70} Created: Created container with docker id fda2a1e9ab67
+May 19 13:00:11.603: INFO: At {2016-05-19 12:53:55 -0700 PDT} - event for test-rollover-controller-gg7bu: {kubelet gke-jenkins-e2e-default-pool-b9f48651-wnyy} Created: Created container with docker id 11a24322c770
+May 19 13:00:11.603: INFO: At {2016-05-19 12:53:55 -0700 PDT} - event for test-rollover-controller-gg7bu: {kubelet gke-jenkins-e2e-default-pool-b9f48651-wnyy} Pulled: Container image ""gcr.io/google_containers/nginx:1.7.9"" already present on machine
+May 19 13:00:11.603: INFO: At {2016-05-19 12:53:55 -0700 PDT} - event for test-rollover-controller-psxi4: {kubelet gke-jenkins-e2e-default-pool-b9f48651-wnyy} Started: Started container with docker id 01cf0674457e
+May 19 13:00:11.603: INFO: At {2016-05-19 12:53:55 -0700 PDT} - event for test-rollover-controller-psxi4: {kubelet gke-jenkins-e2e-default-pool-b9f48651-wnyy} Pulled: Container image ""gcr.io/google_containers/nginx:1.7.9"" already present on machine
+May 19 13:00:11.603: INFO: At {2016-05-19 12:53:55 -0700 PDT} - event for test-rollover-controller-psxi4: {kubelet gke-jenkins-e2e-default-pool-b9f48651-wnyy} Created: Created container with docker id 01cf0674457e
+May 19 13:00:11.603: INFO: At {2016-05-19 12:53:55 -0700 PDT} - event for test-rollover-controller-sbus0: {kubelet gke-jenkins-e2e-default-pool-b9f48651-07l9} Started: Started container with docker id 0c45e77b044e
+May 19 13:00:11.603: INFO: At {2016-05-19 12:53:56 -0700 PDT} - event for test-rollover-controller-1n0xm: {kubelet gke-jenkins-e2e-default-pool-b9f48651-3w70} Started: Started container with docker id fda2a1e9ab67
+May 19 13:00:11.603: INFO: At {2016-05-19 12:53:56 -0700 PDT} - event for test-rollover-controller-gg7bu: {kubelet gke-jenkins-e2e-default-pool-b9f48651-wnyy} Started: Started container with docker id 11a24322c770
+May 19 13:00:11.603: INFO: At {2016-05-19 12:54:06 -0700 PDT} - event for test-rollover-controller: {replicaset-controller } SuccessfulDelete: Deleted pod: test-rollover-controller-psxi4
+May 19 13:00:11.603: INFO: At {2016-05-19 12:54:06 -0700 PDT} - event for test-rollover-deployment: {deployment-controller } ScalingReplicaSet: Scaled up replica set test-rollover-deployment-3098649686 to 2
+May 19 13:00:11.603: INFO: At {2016-05-19 12:54:06 -0700 PDT} - event for test-rollover-deployment: {deployment-controller } ScalingReplicaSet: Scaled up replica set test-rollover-deployment-3098649686 to 1
+May 19 13:00:11.603: INFO: At {2016-05-19 12:54:06 -0700 PDT} - event for test-rollover-deployment: {deployment-controller } ScalingReplicaSet: Scaled down replica set test-rollover-controller to 3
+May 19 13:00:11.603: INFO: At {2016-05-19 12:54:06 -0700 PDT} - event for test-rollover-deployment-3098649686: {replicaset-controller } SuccessfulCreate: Created pod: test-rollover-deployment-3098649686-izas7
+May 19 13:00:11.603: INFO: At {2016-05-19 12:54:06 -0700 PDT} - event for test-rollover-deployment-3098649686-izas7: {default-scheduler } Scheduled: Successfully assigned test-rollover-deployment-3098649686-izas7 to gke-jenkins-e2e-default-pool-b9f48651-3w70
+May 19 13:00:11.603: INFO: At {2016-05-19 12:54:07 -0700 PDT} - event for test-rollover-controller-psxi4: {kubelet gke-jenkins-e2e-default-pool-b9f48651-wnyy} Killing: Killing container with docker id 01cf0674457e: Need to kill pod.
+May 19 13:00:11.603: INFO: At {2016-05-19 12:54:07 -0700 PDT} - event for test-rollover-deployment: {deployment-controller } ScalingReplicaSet: Scaled up replica set test-rollover-deployment-3104088211 to 2
+May 19 13:00:11.603: INFO: At {2016-05-19 12:54:07 -0700 PDT} - event for test-rollover-deployment: {deployment-controller } ScalingReplicaSet: Scaled down replica set test-rollover-deployment-3098649686 to 0
+May 19 13:00:11.603: INFO: At {2016-05-19 12:54:07 -0700 PDT} - event for test-rollover-deployment-3098649686: {replicaset-controller } SuccessfulDelete: Deleted pod: test-rollover-deployment-3098649686-izas7
+May 19 13:00:11.603: INFO: At {2016-05-19 12:54:07 -0700 PDT} - event for test-rollover-deployment-3098649686: {replicaset-controller } SuccessfulDelete: Deleted pod: test-rollover-deployment-3098649686-nn9hp
+May 19 13:00:11.603: INFO: At {2016-05-19 12:54:07 -0700 PDT} - event for test-rollover-deployment-3098649686: {replicaset-controller } SuccessfulCreate: Created pod: test-rollover-deployment-3098649686-nn9hp
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:07 -0700 PDT} - event for test-rollover-deployment-3098649686-nn9hp: {default-scheduler } Scheduled: Successfully assigned test-rollover-deployment-3098649686-nn9hp to gke-jenkins-e2e-default-pool-b9f48651-wnyy
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:07 -0700 PDT} - event for test-rollover-deployment-3104088211: {replicaset-controller } SuccessfulCreate: Created pod: test-rollover-deployment-3104088211-vme5t
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:07 -0700 PDT} - event for test-rollover-deployment-3104088211: {replicaset-controller } SuccessfulCreate: Created pod: test-rollover-deployment-3104088211-cc8bz
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:07 -0700 PDT} - event for test-rollover-deployment-3104088211-cc8bz: {default-scheduler } Scheduled: Successfully assigned test-rollover-deployment-3104088211-cc8bz to gke-jenkins-e2e-default-pool-b9f48651-wnyy
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:07 -0700 PDT} - event for test-rollover-deployment-3104088211-vme5t: {default-scheduler } Scheduled: Successfully assigned test-rollover-deployment-3104088211-vme5t to gke-jenkins-e2e-default-pool-b9f48651-07l9
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:08 -0700 PDT} - event for test-rollover-deployment-3104088211-cc8bz: {kubelet gke-jenkins-e2e-default-pool-b9f48651-wnyy} Created: Created container with docker id 8acf88086bb1
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:08 -0700 PDT} - event for test-rollover-deployment-3104088211-cc8bz: {kubelet gke-jenkins-e2e-default-pool-b9f48651-wnyy} Started: Started container with docker id 8acf88086bb1
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:08 -0700 PDT} - event for test-rollover-deployment-3104088211-cc8bz: {kubelet gke-jenkins-e2e-default-pool-b9f48651-wnyy} Pulled: Container image ""gcr.io/google_containers/redis:e2e"" already present on machine
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:08 -0700 PDT} - event for test-rollover-deployment-3104088211-vme5t: {kubelet gke-jenkins-e2e-default-pool-b9f48651-07l9} Pulling: pulling image ""gcr.io/google_containers/redis:e2e""
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:14 -0700 PDT} - event for test-rollover-deployment-3098649686-izas7: {kubelet gke-jenkins-e2e-default-pool-b9f48651-3w70} Pulling: pulling image ""gcr.io/google_samples/gb-redisslave:v1""
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:14 -0700 PDT} - event for test-rollover-deployment-3098649686-nn9hp: {kubelet gke-jenkins-e2e-default-pool-b9f48651-wnyy} Pulling: pulling image ""gcr.io/google_samples/gb-redisslave:v1""
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:30 -0700 PDT} - event for test-rollover-deployment-3098649686-izas7: {kubelet gke-jenkins-e2e-default-pool-b9f48651-3w70} Pulled: Successfully pulled image ""gcr.io/google_samples/gb-redisslave:v1""
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:30 -0700 PDT} - event for test-rollover-deployment-3098649686-izas7: {kubelet gke-jenkins-e2e-default-pool-b9f48651-3w70} FailedSync: Error syncing pod, skipping: failed to ""StartContainer"" for ""redis-slave"" with RunContainerError: ""GenerateRunContainerOptions: impossible: cannot find the mounted volumes for pod \""test-rollover-deployment-3098649686-izas7_e2e-tests-deployment-oybdc(71ff315a-1dfb-11e6-a239-42010af0001e)\""""
+
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:33 -0700 PDT} - event for test-rollover-deployment: {deployment-controller } ScalingReplicaSet: Scaled down replica set test-rollover-controller to 2
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:33 -0700 PDT} - event for test-rollover-deployment: {deployment-controller } ScalingReplicaSet: Scaled up replica set test-rollover-deployment-3104088211 to 3
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:33 -0700 PDT} - event for test-rollover-deployment-3098649686-nn9hp: {kubelet gke-jenkins-e2e-default-pool-b9f48651-wnyy} FailedSync: Error syncing pod, skipping: failed to ""StartContainer"" for ""redis-slave"" with RunContainerError: ""GenerateRunContainerOptions: impossible: cannot find the mounted volumes for pod \""test-rollover-deployment-3098649686-nn9hp_e2e-tests-deployment-oybdc(72220963-1dfb-11e6-a239-42010af0001e)\""""
+
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:33 -0700 PDT} - event for test-rollover-deployment-3098649686-nn9hp: {kubelet gke-jenkins-e2e-default-pool-b9f48651-wnyy} Pulled: Successfully pulled image ""gcr.io/google_samples/gb-redisslave:v1""
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:33 -0700 PDT} - event for test-rollover-deployment-3104088211: {replicaset-controller } SuccessfulCreate: Created pod: test-rollover-deployment-3104088211-a84by
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:33 -0700 PDT} - event for test-rollover-deployment-3104088211-a84by: {kubelet gke-jenkins-e2e-default-pool-b9f48651-3w70} Pulled: Container image ""gcr.io/google_containers/redis:e2e"" already present on machine
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:33 -0700 PDT} - event for test-rollover-deployment-3104088211-a84by: {default-scheduler } Scheduled: Successfully assigned test-rollover-deployment-3104088211-a84by to gke-jenkins-e2e-default-pool-b9f48651-3w70
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:34 -0700 PDT} - event for test-rollover-deployment-3104088211-a84by: {kubelet gke-jenkins-e2e-default-pool-b9f48651-3w70} Started: Started container with docker id 8ccd03769c41
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:34 -0700 PDT} - event for test-rollover-deployment-3104088211-a84by: {kubelet gke-jenkins-e2e-default-pool-b9f48651-3w70} Created: Created container with docker id 8ccd03769c41
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:38 -0700 PDT} - event for test-rollover-deployment-3104088211-vme5t: {kubelet gke-jenkins-e2e-default-pool-b9f48651-07l9} Started: Started container with docker id f9eb83c77757
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:38 -0700 PDT} - event for test-rollover-deployment-3104088211-vme5t: {kubelet gke-jenkins-e2e-default-pool-b9f48651-07l9} Created: Created container with docker id f9eb83c77757
+May 19 13:00:11.604: INFO: At {2016-05-19 12:54:38 -0700 PDT} - event for test-rollover-deployment-3104088211-vme5t: {kubelet gke-jenkins-e2e-default-pool-b9f48651-07l9} Pulled: Successfully pulled image ""gcr.io/google_containers/redis:e2e""
+May 19 13:00:11.619: INFO: POD NODE PHASE GRACE CONDITIONS
+May 19 13:00:11.619: INFO: test-webserver-fef6df7b-1dfb-11e6-a46c-0242ac110003 gke-jenkins-e2e-default-pool-b9f48651-wnyy Running [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:58:03 -0700 PDT} } {Ready False {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:58:03 -0700 PDT} ContainersNotReady containers with unready status: [test-webserber]} {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:58:03 -0700 PDT} }]
+May 19 13:00:11.619: INFO: test-rollover-controller-1n0xm gke-jenkins-e2e-default-pool-b9f48651-3w70 Running [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:53 -0700 PDT} } {Ready True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:56 -0700 PDT} } {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:53 -0700 PDT} }]
+May 19 13:00:11.619: INFO: test-rollover-controller-gg7bu gke-jenkins-e2e-default-pool-b9f48651-wnyy Running [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:53 -0700 PDT} } {Ready True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:58 -0700 PDT} } {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:53 -0700 PDT} }]
+May 19 13:00:11.619: INFO: test-rollover-controller-sbus0 gke-jenkins-e2e-default-pool-b9f48651-07l9 Running [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:53 -0700 PDT} } {Ready True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:55 -0700 PDT} } {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:54 -0700 PDT} }]
+May 19 13:00:11.619: INFO: test-rollover-deployment-3104088211-a84by gke-jenkins-e2e-default-pool-b9f48651-3w70 Running [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:54:33 -0700 PDT} } {Ready True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:54:35 -0700 PDT} } {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:54:33 -0700 PDT} }]
+May 19 13:00:11.619: INFO: test-rollover-deployment-3104088211-cc8bz gke-jenkins-e2e-default-pool-b9f48651-wnyy Running [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:54:07 -0700 PDT} } {Ready True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:54:08 -0700 PDT} } {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:54:07 -0700 PDT} }]
+May 19 13:00:11.619: INFO: test-rollover-deployment-3104088211-vme5t gke-jenkins-e2e-default-pool-b9f48651-07l9 Running [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:54:07 -0700 PDT} } {Ready True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:54:39 -0700 PDT} } {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:54:07 -0700 PDT} }]
+May 19 13:00:11.619: INFO: foo-36hvx gke-jenkins-e2e-default-pool-b9f48651-3w70 Running [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:18 -0700 PDT} } {Ready True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:21 -0700 PDT} } {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:18 -0700 PDT} }]
+May 19 13:00:11.619: INFO: foo-bklsf gke-jenkins-e2e-default-pool-b9f48651-3w70 Running [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:18 -0700 PDT} } {Ready True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:21 -0700 PDT} } {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:18 -0700 PDT} }]
+May 19 13:00:11.619: INFO: foo-07p3z gke-jenkins-e2e-default-pool-b9f48651-07l9 Running [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:19 -0700 PDT} } {Ready True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:21 -0700 PDT} } {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:19 -0700 PDT} }]
+May 19 13:00:11.619: INFO: foo-b91ft gke-jenkins-e2e-default-pool-b9f48651-3w70 Running [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:19 -0700 PDT} } {Ready True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:22 -0700 PDT} } {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:19 -0700 PDT} }]
+May 19 13:00:11.619: INFO: scale-down-ug6k3 gke-jenkins-e2e-default-pool-b9f48651-3w70 Running 30s [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:59:20 -0700 PDT} } {Ready True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:59:21 -0700 PDT} } {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:59:21 -0700 PDT} }]
+May 19 13:00:11.619: INFO: fluentd-cloud-logging-gke-jenkins-e2e-default-pool-b9f48651-07l9 gke-jenkins-e2e-default-pool-b9f48651-07l9 Running [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:03 -0700 PDT} } {Ready True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:25 -0700 PDT} } {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:03 -0700 PDT} }]
+May 19 13:00:11.619: INFO: fluentd-cloud-logging-gke-jenkins-e2e-default-pool-b9f48651-3w70 gke-jenkins-e2e-default-pool-b9f48651-3w70 Running [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:03 -0700 PDT} } {Ready True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:25 -0700 PDT} } {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:03 -0700 PDT} }]
+May 19 13:00:11.620: INFO: fluentd-cloud-logging-gke-jenkins-e2e-default-pool-b9f48651-wnyy gke-jenkins-e2e-default-pool-b9f48651-wnyy Running [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:01 -0700 PDT} } {Ready True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:23 -0700 PDT} } {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:01 -0700 PDT} }]
+May 19 13:00:11.620: INFO: heapster-v1.1.0.beta1-2658213798-030gh gke-jenkins-e2e-default-pool-b9f48651-wnyy Running [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:32 -0700 PDT} } {Ready True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:37 -0700 PDT} } {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:32 -0700 PDT} }]
+May 19 13:00:11.620: INFO: kube-dns-v11-kjqw4 gke-jenkins-e2e-default-pool-b9f48651-07l9 Running [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:26 -0700 PDT} } {Ready True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:53:16 -0700 PDT} } {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:26 -0700 PDT} }]
+May 19 13:00:11.620: INFO: kube-proxy-gke-jenkins-e2e-default-pool-b9f48651-07l9 gke-jenkins-e2e-default-pool-b9f48651-07l9 Running [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:03 -0700 PDT} } {Ready True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:26 -0700 PDT} } {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:03 -0700 PDT} }]
+May 19 13:00:11.620: INFO: kube-proxy-gke-jenkins-e2e-default-pool-b9f48651-3w70 gke-jenkins-e2e-default-pool-b9f48651-3w70 Running [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:03 -0700 PDT} } {Ready True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:20 -0700 PDT} } {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:03 -0700 PDT} }]
+May 19 13:00:11.620: INFO: kube-proxy-gke-jenkins-e2e-default-pool-b9f48651-wnyy gke-jenkins-e2e-default-pool-b9f48651-wnyy Running [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:01 -0700 PDT} } {Ready True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:17 -0700 PDT} } {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:01 -0700 PDT} }]
+May 19 13:00:11.620: INFO: kubernetes-dashboard-v1.0.1-5fi9o gke-jenkins-e2e-default-pool-b9f48651-wnyy Running [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:25 -0700 PDT} } {Ready True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:29 -0700 PDT} } {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:25 -0700 PDT} }]
+May 19 13:00:11.620: INFO: l7-lb-controller-v0.6.0-0teyj gke-jenkins-e2e-default-pool-b9f48651-07l9 Running [{Initialized True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:26 -0700 PDT} } {Ready True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:41 -0700 PDT} } {PodScheduled True {0001-01-01 00:00:00 +0000 UTC} {2016-05-19 12:52:26 -0700 PDT} }]
+May 19 13:00:11.620: INFO:
+May 19 13:00:11.626: INFO:
+Logging node info for node gke-jenkins-e2e-default-pool-b9f48651-07l9
+May 19 13:00:11.630: INFO: Node Info: kind:"""" apiVersion:""""
+May 19 13:00:11.630: INFO:
+Logging kubelet events for node gke-jenkins-e2e-default-pool-b9f48651-07l9
+May 19 13:00:11.642: INFO:
+Logging pods the kubelet thinks is on node gke-jenkins-e2e-default-pool-b9f48651-07l9
+May 19 13:00:11.670: INFO: l7-lb-controller-v0.6.0-0teyj started at 2016-05-19T12:52:26-07:00 (0+2 container statuses recorded)
+May 19 13:00:11.670: INFO: Container default-http-backend ready: true, restart count 0
+May 19 13:00:11.670: INFO: Container l7-lb-controller ready: true, restart count 0
+May 19 13:00:11.670: INFO: foo-07p3z started at 2016-05-19T12:53:19-07:00 (0+1 container statuses recorded)
+May 19 13:00:11.670: INFO: Container c ready: true, restart count 0
+May 19 13:00:11.670: INFO: kube-dns-v11-kjqw4 started at 2016-05-19T12:52:26-07:00 (0+4 container statuses recorded)
+May 19 13:00:11.670: INFO: Container etcd ready: true, restart count 0
+May 19 13:00:11.670: INFO: Container healthz ready: true, restart count 0
+May 19 13:00:11.670: INFO: Container kube2sky ready: true, restart count 0
+May 19 13:00:11.670: INFO: Container skydns ready: true, restart count 0
+May 19 13:00:11.670: INFO: kube-proxy-gke-jenkins-e2e-default-pool-b9f48651-07l9 started at (0+0 container statuses recorded)
+May 19 13:00:11.670: INFO: test-rollover-controller-sbus0 started at 2016-05-19T12:53:53-07:00 (0+1 container statuses recorded)
+May 19 13:00:11.670: INFO: Container nginx ready: true, restart count 0
+May 19 13:00:11.670: INFO: fluentd-cloud-logging-gke-jenkins-e2e-default-pool-b9f48651-07l9 started at (0+0 container statuses recorded)
+May 19 13:00:11.670: INFO: test-rollover-deployment-3104088211-vme5t started at 2016-05-19T12:54:07-07:00 (0+1 container statuses recorded)
+May 19 13:00:11.670: INFO: Container redis ready: true, restart count 0
+W0519 13:00:11.687150 4366 metrics_grabber.go:74] Master node is not registered. Grabbing metrics from Scheduler and ControllerManager is disabled.
+May 19 13:00:11.867: INFO:
+Latency metrics for node gke-jenkins-e2e-default-pool-b9f48651-07l9
+May 19 13:00:11.867: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.99 Latency:1m32.575952s}
+May 19 13:00:11.867: INFO: {Operation: Method:pod_worker_start_latency_microseconds Quantile:0.99 Latency:1m10.010861s}
+May 19 13:00:11.867: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.9 Latency:42.670364s}
+May 19 13:00:11.867: INFO: {Operation:SyncPod Method:container_manager_latency_microseconds Quantile:0.99 Latency:38.910364s}
+May 19 13:00:11.867: INFO: {Operation:stop_container Method:docker_operations_latency_microseconds Quantile:0.99 Latency:30.45333s}
+May 19 13:00:11.867: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.99 Latency:29.760887s}
+May 19 13:00:11.867: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.5 Latency:22.422959s}
+May 19 13:00:11.867: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.99 Latency:22.422959s}
+May 19 13:00:11.867: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.9 Latency:22.422959s}
+May 19 13:00:11.867: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.9 Latency:11.43723s}
+May 19 13:00:11.867: INFO:
+Logging node info for node gke-jenkins-e2e-default-pool-b9f48651-3w70
+May 19 13:00:11.873: INFO: Node Info: kind:"""" apiVersion:""""
+May 19 13:00:11.873: INFO:
+Logging kubelet events for node gke-jenkins-e2e-default-pool-b9f48651-3w70
+May 19 13:00:11.886: INFO:
+Logging pods the kubelet thinks is on node gke-jenkins-e2e-default-pool-b9f48651-3w70
+May 19 13:00:11.897: INFO: fluentd-cloud-logging-gke-jenkins-e2e-default-pool-b9f48651-3w70 started at (0+0 container statuses recorded)
+May 19 13:00:11.897: INFO: test-rollover-controller-1n0xm started at 2016-05-19T12:53:53-07:00 (0+1 container statuses recorded)
+May 19 13:00:11.897: INFO: Container nginx ready: true, restart count 0
+May 19 13:00:11.897: INFO: kube-proxy-gke-jenkins-e2e-default-pool-b9f48651-3w70 started at (0+0 container statuses recorded)
+May 19 13:00:11.897: INFO: foo-bklsf started at 2016-05-19T12:53:18-07:00 (0+1 container statuses recorded)
+May 19 13:00:11.897: INFO: Container c ready: true, restart count 0
+May 19 13:00:11.897: INFO: foo-b91ft started at 2016-05-19T12:53:19-07:00 (0+1 container statuses recorded)
+May 19 13:00:11.897: INFO: Container c ready: true, restart count 0
+May 19 13:00:11.897: INFO: scale-down-ug6k3 started at 2016-05-19T12:59:20-07:00 (0+1 container statuses recorded)
+May 19 13:00:11.897: INFO: Container c ready: true, restart count 0
+May 19 13:00:11.897: INFO: test-rollover-deployment-3104088211-a84by started at 2016-05-19T12:54:33-07:00 (0+1 container statuses recorded)
+May 19 13:00:11.897: INFO: Container redis ready: true, restart count 0
+May 19 13:00:11.897: INFO: foo-36hvx started at 2016-05-19T12:53:18-07:00 (0+1 container statuses recorded)
+May 19 13:00:11.897: INFO: Container c ready: true, restart count 0
+W0519 13:00:11.903894 4366 metrics_grabber.go:74] Master node is not registered. Grabbing metrics from Scheduler and ControllerManager is disabled.
+May 19 13:00:12.121: INFO:
+Latency metrics for node gke-jenkins-e2e-default-pool-b9f48651-3w70
+May 19 13:00:12.121: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.99 Latency:1m31.570897s}
+May 19 13:00:12.121: INFO: {Operation: Method:pod_worker_start_latency_microseconds Quantile:0.99 Latency:1m10.012519s}
+May 19 13:00:12.121: INFO: {Operation:SyncPod Method:container_manager_latency_microseconds Quantile:0.99 Latency:44.421537s}
+May 19 13:00:12.121: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.9 Latency:39.769994s}
+May 19 13:00:12.121: INFO: {Operation:stop_container Method:docker_operations_latency_microseconds Quantile:0.99 Latency:30.087359s}
+May 19 13:00:12.121: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.99 Latency:28.185911s}
+May 19 13:00:12.121: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.9 Latency:15.531689s}
+May 19 13:00:12.121: INFO:
+Logging node info for node gke-jenkins-e2e-default-pool-b9f48651-wnyy
+May 19 13:00:12.126: INFO: Node Info: kind:"""" apiVersion:""""
+May 19 13:00:12.126: INFO:
+Logging kubelet events for node gke-jenkins-e2e-default-pool-b9f48651-wnyy
+May 19 13:00:12.132: INFO:
+Logging pods the kubelet thinks is on node gke-jenkins-e2e-default-pool-b9f48651-wnyy
+May 19 13:00:12.142: INFO: heapster-v1.1.0.beta1-2658213798-030gh started at 2016-05-19T12:52:32-07:00 (0+2 container statuses recorded)
+May 19 13:00:12.142: INFO: Container heapster ready: true, restart count 0
+May 19 13:00:12.142: INFO: Container heapster-nanny ready: true, restart count 0
+May 19 13:00:12.142: INFO: test-webserver-fef6df7b-1dfb-11e6-a46c-0242ac110003 started at 2016-05-19T12:58:03-07:00 (0+1 container statuses recorded)
+May 19 13:00:12.142: INFO: Container test-webserber ready: false, restart count 0
+May 19 13:00:12.142: INFO: test-rollover-deployment-3104088211-cc8bz started at 2016-05-19T12:54:07-07:00 (0+1 container statuses recorded)
+May 19 13:00:12.142: INFO: Container redis ready: true, restart count 0
+May 19 13:00:12.142: INFO: kube-proxy-gke-jenkins-e2e-default-pool-b9f48651-wnyy started at (0+0 container statuses recorded)
+May 19 13:00:12.142: INFO: kubernetes-dashboard-v1.0.1-5fi9o started at 2016-05-19T12:52:25-07:00 (0+1 container statuses recorded)
+May 19 13:00:12.142: INFO: Container kubernetes-dashboard ready: true, restart count 0
+May 19 13:00:12.142: INFO: test-rollover-controller-gg7bu started at 2016-05-19T12:53:53-07:00 (0+1 container statuses recorded)
+May 19 13:00:12.142: INFO: Container nginx ready: true, restart count 0
+May 19 13:00:12.142: INFO: fluentd-cloud-logging-gke-jenkins-e2e-default-pool-b9f48651-wnyy started at (0+0 container statuses recorded)
+W0519 13:00:12.147396 4366 metrics_grabber.go:74] Master node is not registered. Grabbing metrics from Scheduler and ControllerManager is disabled.
+May 19 13:00:12.248: INFO:
+Latency metrics for node gke-jenkins-e2e-default-pool-b9f48651-wnyy
+May 19 13:00:12.292: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.99 Latency:1m31.690529s}
+May 19 13:00:12.292: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.9 Latency:41.085503s}
+May 19 13:00:12.292: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.99 Latency:41.085503s}
+May 19 13:00:12.292: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.99 Latency:32.599948s}
+May 19 13:00:12.292: INFO: {Operation:stop_container Method:docker_operations_latency_microseconds Quantile:0.99 Latency:30.287445s}
+May 19 13:00:12.292: INFO: {Operation:SyncPod Method:container_manager_latency_microseconds Quantile:0.99 Latency:26.379942s}
+May 19 13:00:12.292: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.9 Latency:26.109318s}
+May 19 13:00:12.293: INFO: {Operation:pull_image Method:docker_operations_latency_microseconds Quantile:0.9 Latency:17.539384s}
+May 19 13:00:12.293: INFO: {Operation:create Method:pod_worker_latency_microseconds Quantile:0.5 Latency:10.652796s}
+May 19 13:00:12.293: INFO: Waiting up to 1m0s for all nodes to be ready
+STEP: Destroying namespace ""e2e-tests-deployment-oybdc"" for this suite.
+
+
+• Failure [383.992 seconds]
+[k8s.io] Deployment
+/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:508
+ deployment should support rollover [It]
+ /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/deployment.go:71
+
+ Expected error:
+ <*errors.errorString | 0xc8207e2040>: {
+ s: ""error waiting for deployment test-rollover-deployment status to match expectation: timed out waiting for the condition"",
+ }
+ error waiting for deployment test-rollover-deployment status to match expectation: timed out waiting for the condition
+ not to have occurred
+
+ /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/deployment.go:560
+```",1.0,"Deployment deployment should support rollover - Same test as #22719 but different failure.
+
+https://console.cloud.google.com/storage/kubernetes-jenkins/logs/kubernetes-e2e-gke/7324/
+
+```
+[It] deployment should support rollover
+ /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/deployment.go:71
+May 19 12:53:53.784: INFO: Pod name rollover-pod: Found 0 pods out of 4
+May 19 12:53:58.790: INFO: Pod name rollover-pod: Found 4 pods out of 4
+STEP: ensuring each pod is running
+W0519 12:53:58.790804 4366 request.go:347] Field selector: v1 - pods - metadata.name - test-rollover-controller-1n0xm: need to check if this is versioned correctly.
+W0519 12:53:58.792935 4366 request.go:347] Field selector: v1 - pods - metadata.name - test-rollover-controller-gg7bu: need to check if this is versioned correctly.
+W0519 12:53:58.810121 4366 request.go:347] Field selector: v1 - pods - metadata.name - test-rollover-controller-psxi4: need to check if this is versioned correctly.
+W0519 12:53:59.044348 4366 request.go:347] Field selector: v1 - pods - metadata.name - test-rollover-controller-sbus0: need to check if this is versioned correctly.
+STEP: trying to dial each unique pod
+May 19 12:53:59.123: INFO: Controller rollover-pod: Got non-empty result from replica 1 [test-rollover-controller-1n0xm]: ""\n\n\nWelcome to nginx!\n\n\n\nWelcome to nginx!
\nIf you see this page, the nginx web server is successfully installed and\nworking. Further configuration is required.
\n\nFor online documentation and support please refer to\nnginx.org.
\nCommercial support is available at\nnginx.com.
\n\nThank you for using nginx.
\n\n\n"", 1 of 4 required successes so far
+May 19 12:53:59.220: INFO: Controller rollover-pod: Got non-empty result from replica 2 [test-rollover-controller-gg7bu]: ""\n\n\nWelcome to nginx!\n\n\n\nWelcome to nginx!
\nIf you see this page, the nginx web server is successfully installed and\nworking. Further configuration is required.
\n\nFor online documentation and support please refer to\nnginx.org.
\nCommercial support is available at\nnginx.com.
\n\nThank you for using nginx.
\n\n\n"", 2 of 4 required successes so far
+May 19 12:53:59.299: INFO: Controller rollover-pod: Got non-empty result from replica 3 [test-rollover-controller-psxi4]: ""\n\n\nWelcome to nginx!\n\n\n\nWelcome to nginx!
\nIf you see this page, the nginx web server is successfully installed and\nworking. Further configuration is required.
\n\nFor online documentation and support please refer to\nnginx.org.
\nCommercial support is available at\nnginx.com.
\n\nThank you for using nginx.
\n\n\n"", 3 of 4 required successes so far
+May 19 12:53:59.358: INFO: Controller rollover-pod: Got non-empty result from replica 4 [test-rollover-controller-sbus0]: ""\n\n\nWelcome to nginx!\n\n\n\nWelcome to nginx!
\nIf you see this page, the nginx web server is successfully installed and\nworking. Further configuration is required.
\n\nFor online documentation and support please refer to\nnginx.org.
\nCommercial support is available at\nnginx.com.
\n\nThank you for using nginx.
\n\n\n"", 4 of 4 required successes so far
+May 19 12:54:05.368: INFO: Creating deployment test-rollover-deployment
+May 19 12:54:07.440: INFO: Updating deployment test-rollover-deployment
+May 19 12:59:11.501: INFO: Deployment: kind:"""" apiVersion:"""" . Selector = matchLabels:
+May 19 12:59:11.501: INFO: All old ReplicaSets (1/2) of deployment test-rollover-deployment: kind:"""" apiVersion:"""" . Selector = matchLabels: matchLabels: matchLabels:
+May 19 12:59:11.502: INFO: All old ReplicaSets (2/2) of deployment test-rollover-deployment: kind:"""" apiVersion:"""" . Selector = matchLabels: matchLabels:
+May 19 12:59:11.502: INFO: New ReplicaSet of deployment test-rollover-deployment: kind:"""" apiVersion:"""" . Selector = matchLabels: matchLabels:
+May 19 12:59:11.509: INFO: Pod test-rollover-controller-1n0xm is available: {TypeMeta:{Kind: APIVersion:} ObjectMeta:{Name:test-rollover-controller-1n0xm GenerateName:test-rollover-controller- Namespace:e2e-tests-deployment-oybdc SelfLink:/api/v1/namespaces/e2e-tests-deployment-oybdc/pods/test-rollover-controller-1n0xm UID:6a549fe5-1dfb-11e6-a239-42010af0001e ResourceVersion:2148 Generation:0 CreationTimestamp:{Time:2016-05-19 12:53:53 -0700 PDT} DeletionTimestamp: DeletionGracePeriodSeconds: Labels:map[name:rollover-pod pod:nginx pod-template-hash:1321378927] Annotations:map[kubernetes.io/created-by:{""kind"":""SerializedReference"",""apiVersion"":""v1"",""reference"":{""kind"":""ReplicaSet"",""namespace"":""e2e-tests-deployment-oybdc"",""name"":""test-rollover-controller"",""uid"":""6a49adea-1dfb-11e6-a239-42010af0001e"",""apiVersion"":""extensions"",""resourceVersion"":""1451""}}
+] OwnerReferences:[] Finalizers:[]} Spec:{Volumes:[{Name:default-token-h8oc4 VolumeSource:{HostPath: EmptyDir: GCEPersistentDisk: AWSElasticBlockStore: GitRepo: Secret:0xc820bec7e0 NFS: ISCSI: Glusterfs: PersistentVolumeClaim: RBD: FlexVolume: Cinder: CephFS: Flocker: DownwardAPI: FC: AzureFile: ConfigMap:}}] InitContainers:[] Containers:[{Name:nginx Image:gcr.io/google_containers/nginx:1.7.9 Command:[] Args:[] WorkingDir: Ports:[] Env:[] Resources:{Limits:map[] Requests:map[]} VolumeMounts:[{Name:default-token-h8oc4 ReadOnly:true MountPath:/var/run/secrets/kubernetes.io/serviceaccount SubPath:}] LivenessProbe: ReadinessProbe: Lifecycle:
/crypto/asn1/bio_ndef.c
+