Unnamed: 0
int64 0
832k
| id
float64 2.49B
32.1B
| type
stringclasses 1
value | created_at
stringlengths 19
19
| repo
stringlengths 4
112
| repo_url
stringlengths 33
141
| action
stringclasses 3
values | title
stringlengths 1
1.02k
| labels
stringlengths 4
1.54k
| body
stringlengths 1
262k
| index
stringclasses 17
values | text_combine
stringlengths 95
262k
| label
stringclasses 2
values | text
stringlengths 96
252k
| binary_label
int64 0
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
22,770
| 6,290,929,728
|
IssuesEvent
|
2017-07-19 22:52:29
|
certbot/certbot
|
https://api.github.com/repos/certbot/certbot
|
reopened
|
Print deprecation warning on experimental systems in certbot-auto
|
area: certbot-auto area: code health area: pkging has pr
|
We have a number of systems where we have "experimental" bootstrap support but we have OS packages available. We should print a deprecation warning for these systems telling users that support is going away including how to install the OS packages. We will be removing support completely for these systems in a few months. The current experimental systems are:
* Mageia
* Manjaro
* Gentoo
* FreeBSD
* macOS
* Amazon Linux
* Joyent SmartOS Zone
At the very least, Gentoo, FreeBSD, and macOS have other options but we should check out other systems as well.
|
1.0
|
Print deprecation warning on experimental systems in certbot-auto - We have a number of systems where we have "experimental" bootstrap support but we have OS packages available. We should print a deprecation warning for these systems telling users that support is going away including how to install the OS packages. We will be removing support completely for these systems in a few months. The current experimental systems are:
* Mageia
* Manjaro
* Gentoo
* FreeBSD
* macOS
* Amazon Linux
* Joyent SmartOS Zone
At the very least, Gentoo, FreeBSD, and macOS have other options but we should check out other systems as well.
|
non_test
|
print deprecation warning on experimental systems in certbot auto we have a number of systems where we have experimental bootstrap support but we have os packages available we should print a deprecation warning for these systems telling users that support is going away including how to install the os packages we will be removing support completely for these systems in a few months the current experimental systems are mageia manjaro gentoo freebsd macos amazon linux joyent smartos zone at the very least gentoo freebsd and macos have other options but we should check out other systems as well
| 0
|
62,941
| 17,266,146,965
|
IssuesEvent
|
2021-07-22 14:01:24
|
decentraland/unity-renderer
|
https://api.github.com/repos/decentraland/unity-renderer
|
closed
|
BIW: the blue light button smart item is not working correctly between builder <> biw
|
defect
|
When you put the blue light button smart item in the scene, the scene is not converting correctly between both formats, sometimes it doesn't load ( in builder) and some times it loads but you are unable to assign parameters to the smart item (in builder)
In order to test this correctly, we will need to add the smart item to zone so we can read the manifest generated by builder in the kernel
|
1.0
|
BIW: the blue light button smart item is not working correctly between builder <> biw - When you put the blue light button smart item in the scene, the scene is not converting correctly between both formats, sometimes it doesn't load ( in builder) and some times it loads but you are unable to assign parameters to the smart item (in builder)
In order to test this correctly, we will need to add the smart item to zone so we can read the manifest generated by builder in the kernel
|
non_test
|
biw the blue light button smart item is not working correctly between builder biw when you put the blue light button smart item in the scene the scene is not converting correctly between both formats sometimes it doesn t load in builder and some times it loads but you are unable to assign parameters to the smart item in builder in order to test this correctly we will need to add the smart item to zone so we can read the manifest generated by builder in the kernel
| 0
|
237,762
| 26,085,321,433
|
IssuesEvent
|
2022-12-26 01:31:37
|
AlexRogalskiy/kotlin-patterns
|
https://api.github.com/repos/AlexRogalskiy/kotlin-patterns
|
opened
|
CVE-2022-46175 (High) detected in json5-2.2.0.tgz, json5-1.0.1.tgz
|
security vulnerability
|
## CVE-2022-46175 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>json5-2.2.0.tgz</b>, <b>json5-1.0.1.tgz</b></p></summary>
<p>
<details><summary><b>json5-2.2.0.tgz</b></p></summary>
<p>JSON for humans.</p>
<p>Library home page: <a href="https://registry.npmjs.org/json5/-/json5-2.2.0.tgz">https://registry.npmjs.org/json5/-/json5-2.2.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/json5/package.json</p>
<p>
Dependency Hierarchy:
- remark-cli-9.0.0.tgz (Root Library)
- unified-args-8.1.0.tgz
- :x: **json5-2.2.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>json5-1.0.1.tgz</b></p></summary>
<p>JSON for humans.</p>
<p>Library home page: <a href="https://registry.npmjs.org/json5/-/json5-1.0.1.tgz">https://registry.npmjs.org/json5/-/json5-1.0.1.tgz</a></p>
<p>Path to dependency file: /tilt_modules/tilt_inspector/package.json</p>
<p>Path to vulnerable library: /tilt_modules/tilt_inspector/node_modules/json5/package.json</p>
<p>
Dependency Hierarchy:
- tilt-inspector-0.1.8.tgz (Root Library)
- next-11.1.2.tgz
- styled-jsx-4.0.1.tgz
- loader-utils-1.2.3.tgz
- :x: **json5-1.0.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/kotlin-patterns/commit/3486fcb6c3b18f46c01920b0b8d0dea6f23684d8">3486fcb6c3b18f46c01920b0b8d0dea6f23684d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
JSON5 is an extension to the popular JSON file format that aims to be easier to write and maintain by hand (e.g. for config files). The `parse` method of the JSON5 library before and including version `2.2.1` does not restrict parsing of keys named `__proto__`, allowing specially crafted strings to pollute the prototype of the resulting object. This vulnerability pollutes the prototype of the object returned by `JSON5.parse` and not the global Object prototype, which is the commonly understood definition of Prototype Pollution. However, polluting the prototype of a single object can have significant security impact for an application if the object is later used in trusted operations. This vulnerability could allow an attacker to set arbitrary and unexpected keys on the object returned from `JSON5.parse`. The actual impact will depend on how applications utilize the returned object and how they filter unwanted keys, but could include denial of service, cross-site scripting, elevation of privilege, and in extreme cases, remote code execution. `JSON5.parse` should restrict parsing of `__proto__` keys when parsing JSON strings to objects. As a point of reference, the `JSON.parse` method included in JavaScript ignores `__proto__` keys. Simply changing `JSON5.parse` to `JSON.parse` in the examples above mitigates this vulnerability. This vulnerability is patched in json5 version 2.2.2 and later.
<p>Publish Date: 2022-12-24
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-46175>CVE-2022-46175</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: Low
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-46175">https://www.cve.org/CVERecord?id=CVE-2022-46175</a></p>
<p>Release Date: 2022-12-24</p>
<p>Fix Resolution: json5 - 2.2.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2022-46175 (High) detected in json5-2.2.0.tgz, json5-1.0.1.tgz - ## CVE-2022-46175 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>json5-2.2.0.tgz</b>, <b>json5-1.0.1.tgz</b></p></summary>
<p>
<details><summary><b>json5-2.2.0.tgz</b></p></summary>
<p>JSON for humans.</p>
<p>Library home page: <a href="https://registry.npmjs.org/json5/-/json5-2.2.0.tgz">https://registry.npmjs.org/json5/-/json5-2.2.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/json5/package.json</p>
<p>
Dependency Hierarchy:
- remark-cli-9.0.0.tgz (Root Library)
- unified-args-8.1.0.tgz
- :x: **json5-2.2.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>json5-1.0.1.tgz</b></p></summary>
<p>JSON for humans.</p>
<p>Library home page: <a href="https://registry.npmjs.org/json5/-/json5-1.0.1.tgz">https://registry.npmjs.org/json5/-/json5-1.0.1.tgz</a></p>
<p>Path to dependency file: /tilt_modules/tilt_inspector/package.json</p>
<p>Path to vulnerable library: /tilt_modules/tilt_inspector/node_modules/json5/package.json</p>
<p>
Dependency Hierarchy:
- tilt-inspector-0.1.8.tgz (Root Library)
- next-11.1.2.tgz
- styled-jsx-4.0.1.tgz
- loader-utils-1.2.3.tgz
- :x: **json5-1.0.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/kotlin-patterns/commit/3486fcb6c3b18f46c01920b0b8d0dea6f23684d8">3486fcb6c3b18f46c01920b0b8d0dea6f23684d8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
JSON5 is an extension to the popular JSON file format that aims to be easier to write and maintain by hand (e.g. for config files). The `parse` method of the JSON5 library before and including version `2.2.1` does not restrict parsing of keys named `__proto__`, allowing specially crafted strings to pollute the prototype of the resulting object. This vulnerability pollutes the prototype of the object returned by `JSON5.parse` and not the global Object prototype, which is the commonly understood definition of Prototype Pollution. However, polluting the prototype of a single object can have significant security impact for an application if the object is later used in trusted operations. This vulnerability could allow an attacker to set arbitrary and unexpected keys on the object returned from `JSON5.parse`. The actual impact will depend on how applications utilize the returned object and how they filter unwanted keys, but could include denial of service, cross-site scripting, elevation of privilege, and in extreme cases, remote code execution. `JSON5.parse` should restrict parsing of `__proto__` keys when parsing JSON strings to objects. As a point of reference, the `JSON.parse` method included in JavaScript ignores `__proto__` keys. Simply changing `JSON5.parse` to `JSON.parse` in the examples above mitigates this vulnerability. This vulnerability is patched in json5 version 2.2.2 and later.
<p>Publish Date: 2022-12-24
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-46175>CVE-2022-46175</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: Low
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-46175">https://www.cve.org/CVERecord?id=CVE-2022-46175</a></p>
<p>Release Date: 2022-12-24</p>
<p>Fix Resolution: json5 - 2.2.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve high detected in tgz tgz cve high severity vulnerability vulnerable libraries tgz tgz tgz json for humans library home page a href path to dependency file package json path to vulnerable library node modules package json dependency hierarchy remark cli tgz root library unified args tgz x tgz vulnerable library tgz json for humans library home page a href path to dependency file tilt modules tilt inspector package json path to vulnerable library tilt modules tilt inspector node modules package json dependency hierarchy tilt inspector tgz root library next tgz styled jsx tgz loader utils tgz x tgz vulnerable library found in head commit a href found in base branch master vulnerability details is an extension to the popular json file format that aims to be easier to write and maintain by hand e g for config files the parse method of the library before and including version does not restrict parsing of keys named proto allowing specially crafted strings to pollute the prototype of the resulting object this vulnerability pollutes the prototype of the object returned by parse and not the global object prototype which is the commonly understood definition of prototype pollution however polluting the prototype of a single object can have significant security impact for an application if the object is later used in trusted operations this vulnerability could allow an attacker to set arbitrary and unexpected keys on the object returned from parse the actual impact will depend on how applications utilize the returned object and how they filter unwanted keys but could include denial of service cross site scripting elevation of privilege and in extreme cases remote code execution parse should restrict parsing of proto keys when parsing json strings to objects as a point of reference the json parse method included in javascript ignores proto keys simply changing parse to json parse in the examples above mitigates this vulnerability this vulnerability is patched in version and later publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact low availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend
| 0
|
415,848
| 28,055,209,669
|
IssuesEvent
|
2023-03-29 08:56:21
|
KusionStack/kpm
|
https://api.github.com/repos/KusionStack/kpm
|
closed
|
[Enhancement] KCL import algorithm and file structure of the package downloaded from kpm.
|
documentation coming soon
|
The file structure of the package downloaded from kpm is related to the algorithm of KCL import. This issue is the solution of kpm package file structure.
KCL import:
https://kcl-lang.io/docs/reference/lang/tour/#module
A bug for KCL import now:
https://github.com/KusionStack/KCLVM/issues/223
|
1.0
|
[Enhancement] KCL import algorithm and file structure of the package downloaded from kpm. - The file structure of the package downloaded from kpm is related to the algorithm of KCL import. This issue is the solution of kpm package file structure.
KCL import:
https://kcl-lang.io/docs/reference/lang/tour/#module
A bug for KCL import now:
https://github.com/KusionStack/KCLVM/issues/223
|
non_test
|
kcl import algorithm and file structure of the package downloaded from kpm the file structure of the package downloaded from kpm is related to the algorithm of kcl import this issue is the solution of kpm package file structure kcl import a bug for kcl import now
| 0
|
1,999
| 4,818,389,008
|
IssuesEvent
|
2016-11-04 16:14:10
|
bbcarchdev/anansi
|
https://api.github.com/repos/bbcarchdev/anansi
|
opened
|
UTF8 resources can not be added to the queue
|
bug processor:rdf
|
They all result in a parsing error. These are the errors generated when adding dbpedia:Cardiff to the queue:
`anansi_1 | crawld[1]: %ANANSI-E-2001: failed to parse URI <http://dbpedia.org/resource/Cardiff_Blues_vs_Leicester_Tigers_(2008–09_Heineken_Cup)>
anansi_1 | crawld[1]: %ANANSI-E-2001: failed to parse URI <http://ja.dbpedia.org/resource/カーディフ>
anansi_1 | crawld[1]: %ANANSI-E-2001: failed to parse URI <http://ko.dbpedia.org/resource/카디프>
anansi_1 | crawld[1]: %ANANSI-E-2001: failed to parse URI <http://el.dbpedia.org/resource/Κάρντιφ>
anansi_1 | crawld[1]: %ANANSI-E-2001: failed to parse URI <http://dbpedia.org/resource/Tŷ_Pont_Haearn>
anansi_1 | crawld[1]: %ANANSI-E-2001: failed to parse URI <http://dbpedia.org/resource/6/6/00_–_Cardiff,_Wales>
`
|
1.0
|
UTF8 resources can not be added to the queue - They all result in a parsing error. These are the errors generated when adding dbpedia:Cardiff to the queue:
`anansi_1 | crawld[1]: %ANANSI-E-2001: failed to parse URI <http://dbpedia.org/resource/Cardiff_Blues_vs_Leicester_Tigers_(2008–09_Heineken_Cup)>
anansi_1 | crawld[1]: %ANANSI-E-2001: failed to parse URI <http://ja.dbpedia.org/resource/カーディフ>
anansi_1 | crawld[1]: %ANANSI-E-2001: failed to parse URI <http://ko.dbpedia.org/resource/카디프>
anansi_1 | crawld[1]: %ANANSI-E-2001: failed to parse URI <http://el.dbpedia.org/resource/Κάρντιφ>
anansi_1 | crawld[1]: %ANANSI-E-2001: failed to parse URI <http://dbpedia.org/resource/Tŷ_Pont_Haearn>
anansi_1 | crawld[1]: %ANANSI-E-2001: failed to parse URI <http://dbpedia.org/resource/6/6/00_–_Cardiff,_Wales>
`
|
non_test
|
resources can not be added to the queue they all result in a parsing error these are the errors generated when adding dbpedia cardiff to the queue anansi crawld anansi e failed to parse uri anansi crawld anansi e failed to parse uri anansi crawld anansi e failed to parse uri anansi crawld anansi e failed to parse uri anansi crawld anansi e failed to parse uri anansi crawld anansi e failed to parse uri
| 0
|
664,340
| 22,266,358,569
|
IssuesEvent
|
2022-06-10 07:51:41
|
CirclesUBI/circles-myxogastria
|
https://api.github.com/repos/CirclesUBI/circles-myxogastria
|
closed
|
Remove the circle around the balance in dashboard
|
priority ★★★ Big Iteration 22
|
It looks bad when balance grows to large numbers
|
1.0
|
Remove the circle around the balance in dashboard - It looks bad when balance grows to large numbers
|
non_test
|
remove the circle around the balance in dashboard it looks bad when balance grows to large numbers
| 0
|
55,268
| 23,432,496,999
|
IssuesEvent
|
2022-08-15 05:22:32
|
networkupstools/nut
|
https://api.github.com/repos/networkupstools/nut
|
closed
|
Driver service instance (on Solaris/illumos with NDE) started on boot before /var/run/nut appeared
|
bug solaris service/daemon start/stop
|
By itself it was not a problem for the driver, but a PID file was not created. When the USB device disconnected and a reconnection did not occur, the next instance of the driver (started by my custom crontab job calling https://github.com/networkupstools/nut/blob/master/scripts/Solaris/reset-ups-usb-solaris.sh.sample from PR #1417) could not start it because it did not know of an older PID to kill off.
From SMF log of the instance:
````
...
[ Aug 11 19:17:09 Enabled. ]
[ Aug 11 19:17:49 Enabled. ]
[ Aug 11 19:17:59 Executing start method ("/sbin/sh -c 'NUTDEV="`/usr/libexec/nut-driver-enumerator.sh --get-device-for-service innotech`" && [ -n "$NUTDEV" ] || { echo "FATAL: Could not find a NUT device section for service unit innotech" >&2 ; exit 1 ; } ; /usr/sbin/upsdrvctl start "$NUTDEV"'"). ]
0.000000 [D1] debug level is '6'
0.000972 writepid: fopen /var/run/nut/nutdrv_qx-innotech.pid: No such file or directory
0.001076 [D5] send_to_all: SETINFO device.type "ups"
0.001164 [D1] upsdrv_initups...
...
````
|
1.0
|
Driver service instance (on Solaris/illumos with NDE) started on boot before /var/run/nut appeared - By itself it was not a problem for the driver, but a PID file was not created. When the USB device disconnected and a reconnection did not occur, the next instance of the driver (started by my custom crontab job calling https://github.com/networkupstools/nut/blob/master/scripts/Solaris/reset-ups-usb-solaris.sh.sample from PR #1417) could not start it because it did not know of an older PID to kill off.
From SMF log of the instance:
````
...
[ Aug 11 19:17:09 Enabled. ]
[ Aug 11 19:17:49 Enabled. ]
[ Aug 11 19:17:59 Executing start method ("/sbin/sh -c 'NUTDEV="`/usr/libexec/nut-driver-enumerator.sh --get-device-for-service innotech`" && [ -n "$NUTDEV" ] || { echo "FATAL: Could not find a NUT device section for service unit innotech" >&2 ; exit 1 ; } ; /usr/sbin/upsdrvctl start "$NUTDEV"'"). ]
0.000000 [D1] debug level is '6'
0.000972 writepid: fopen /var/run/nut/nutdrv_qx-innotech.pid: No such file or directory
0.001076 [D5] send_to_all: SETINFO device.type "ups"
0.001164 [D1] upsdrv_initups...
...
````
|
non_test
|
driver service instance on solaris illumos with nde started on boot before var run nut appeared by itself it was not a problem for the driver but a pid file was not created when the usb device disconnected and a reconnection did not occur the next instance of the driver started by my custom crontab job calling from pr could not start it because it did not know of an older pid to kill off from smf log of the instance echo fatal could not find a nut device section for service unit innotech exit usr sbin upsdrvctl start nutdev debug level is writepid fopen var run nut nutdrv qx innotech pid no such file or directory send to all setinfo device type ups upsdrv initups
| 0
|
221,902
| 24,669,034,755
|
IssuesEvent
|
2022-10-18 12:32:59
|
Gal-Doron/issuetype
|
https://api.github.com/repos/Gal-Doron/issuetype
|
closed
|
CVE-2022-22965 (High) detected in spring-beans-5.3.0.jar - autoclosed
|
security vulnerability
|
## CVE-2022-22965 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-beans-5.3.0.jar</b></p></summary>
<p>Spring Beans</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /repository/org/springframework/spring-beans/5.3.0/spring-beans-5.3.0.jar</p>
<p>
Dependency Hierarchy:
- :x: **spring-beans-5.3.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Gal-Doron/issuetype/commit/5ed6bdcc097e5d56d4c9dbd28b51ef907d8892fb">5ed6bdcc097e5d56d4c9dbd28b51ef907d8892fb</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data binding. The specific exploit requires the application to run on Tomcat as a WAR deployment. If the application is deployed as a Spring Boot executable jar, i.e. the default, it is not vulnerable to the exploit. However, the nature of the vulnerability is more general, and there may be other ways to exploit it.
<p>Publish Date: 2022-04-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22965>CVE-2022-22965</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement">https://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement</a></p>
<p>Release Date: 2022-04-01</p>
<p>Fix Resolution: 5.3.18</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
|
True
|
CVE-2022-22965 (High) detected in spring-beans-5.3.0.jar - autoclosed - ## CVE-2022-22965 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-beans-5.3.0.jar</b></p></summary>
<p>Spring Beans</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /repository/org/springframework/spring-beans/5.3.0/spring-beans-5.3.0.jar</p>
<p>
Dependency Hierarchy:
- :x: **spring-beans-5.3.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Gal-Doron/issuetype/commit/5ed6bdcc097e5d56d4c9dbd28b51ef907d8892fb">5ed6bdcc097e5d56d4c9dbd28b51ef907d8892fb</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data binding. The specific exploit requires the application to run on Tomcat as a WAR deployment. If the application is deployed as a Spring Boot executable jar, i.e. the default, it is not vulnerable to the exploit. However, the nature of the vulnerability is more general, and there may be other ways to exploit it.
<p>Publish Date: 2022-04-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22965>CVE-2022-22965</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement">https://spring.io/blog/2022/03/31/spring-framework-rce-early-announcement</a></p>
<p>Release Date: 2022-04-01</p>
<p>Fix Resolution: 5.3.18</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
|
non_test
|
cve high detected in spring beans jar autoclosed cve high severity vulnerability vulnerable library spring beans jar spring beans library home page a href path to dependency file pom xml path to vulnerable library repository org springframework spring beans spring beans jar dependency hierarchy x spring beans jar vulnerable library found in head commit a href found in base branch main vulnerability details a spring mvc or spring webflux application running on jdk may be vulnerable to remote code execution rce via data binding the specific exploit requires the application to run on tomcat as a war deployment if the application is deployed as a spring boot executable jar i e the default it is not vulnerable to the exploit however the nature of the vulnerability is more general and there may be other ways to exploit it publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue
| 0
|
94,381
| 3,925,129,300
|
IssuesEvent
|
2016-04-22 17:46:21
|
kubernetes/kubernetes
|
https://api.github.com/repos/kubernetes/kubernetes
|
closed
|
e2e flake: Pod in waiting, expected running
|
kind/flake priority/P1 team/node
|
[logs](https://console.cloud.google.com/storage/browser/kubernetes-jenkins/logs/kubernetes-e2e-gce/15221)
>
09:30:17 • Failure [263.986 seconds]
09:30:17 [k8s.io] Kubectl client
09:30:17 /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:426
09:30:17 [k8s.io] Kubectl describe
09:30:17 /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:426
09:30:17 should check if kubectl describe prints relevant information for rc and pods [Conformance] [It]
09:30:17 /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl.go:713
09:30:17
09:30:17 Apr 21 09:27:23.903: Failed to find 1 Running in Pods Status: 0 Running / 1 Waiting / 0 Succeeded / 0 Failed
09:30:17
09:30:17 /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl.go:1206
|
1.0
|
e2e flake: Pod in waiting, expected running - [logs](https://console.cloud.google.com/storage/browser/kubernetes-jenkins/logs/kubernetes-e2e-gce/15221)
>
09:30:17 • Failure [263.986 seconds]
09:30:17 [k8s.io] Kubectl client
09:30:17 /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:426
09:30:17 [k8s.io] Kubectl describe
09:30:17 /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:426
09:30:17 should check if kubectl describe prints relevant information for rc and pods [Conformance] [It]
09:30:17 /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl.go:713
09:30:17
09:30:17 Apr 21 09:27:23.903: Failed to find 1 Running in Pods Status: 0 Running / 1 Waiting / 0 Succeeded / 0 Failed
09:30:17
09:30:17 /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl.go:1206
|
non_test
|
flake pod in waiting expected running • failure kubectl client go src io kubernetes output dockerized go src io kubernetes test framework framework go kubectl describe go src io kubernetes output dockerized go src io kubernetes test framework framework go should check if kubectl describe prints relevant information for rc and pods go src io kubernetes output dockerized go src io kubernetes test kubectl go apr failed to find running in pods status running waiting succeeded failed go src io kubernetes output dockerized go src io kubernetes test kubectl go
| 0
|
213,390
| 16,516,049,650
|
IssuesEvent
|
2021-05-26 09:47:52
|
trinodb/trino
|
https://api.github.com/repos/trinodb/trino
|
closed
|
TestOAuth2WebUiAuthenticationFilter.setup is flaky
|
bug test
|
```
021-03-03T19:51:16.0690425Z Unable to create injector, see the following errors:
2021-03-03T19:51:16.0690893Z
2021-03-03T19:51:16.0695891Z 1) Error in custom provider, java.lang.NullPointerException
2021-03-03T19:51:16.0710245Z at io.airlift.discovery.client.DiscoveryBinder.bindServiceAnnouncement(DiscoveryBinder.java:79) (via modules: io.trino.server.ServerMainModule -> io.trino.server.CoordinatorModule)
2021-03-03T19:51:16.0719185Z while locating io.airlift.discovery.client.ServiceAnnouncement annotated with @com.google.inject.internal.Element(setName=,uniqueId=1870, type=MULTIBINDER, keyType=)
2021-03-03T19:51:16.0723513Z while locating java.util.Set<io.airlift.discovery.client.ServiceAnnouncement>
2021-03-03T19:51:16.0729486Z for the 2nd parameter of io.airlift.discovery.client.Announcer.<init>(Announcer.java:68)
2021-03-03T19:51:16.0737655Z at io.airlift.discovery.client.testing.TestingDiscoveryModule.configure(TestingDiscoveryModule.java:49)
2021-03-03T19:51:16.0739954Z while locating io.airlift.discovery.client.Announcer
2021-03-03T19:51:16.0752822Z for the 2nd parameter of io.airlift.discovery.client.testing.TestingDiscoveryModule.createMergingServiceSelectorFactory(TestingDiscoveryModule.java:69)
2021-03-03T19:51:16.0760715Z at io.airlift.discovery.client.testing.TestingDiscoveryModule.createMergingServiceSelectorFactory(TestingDiscoveryModule.java:69)
2021-03-03T19:51:16.0764574Z while locating io.airlift.discovery.client.MergingServiceSelectorFactory
2021-03-03T19:51:16.0772135Z at io.airlift.discovery.client.testing.TestingDiscoveryModule.configure(TestingDiscoveryModule.java:55)
2021-03-03T19:51:16.0775631Z while locating io.airlift.discovery.client.ServiceSelectorFactory
2021-03-03T19:51:16.0785857Z for the 1st parameter of io.airlift.discovery.client.ServiceSelectorProvider.setServiceSelectorFactory(ServiceSelectorProvider.java:50)
2021-03-03T19:51:16.0788811Z at io.trino.server.ServerMainModule.setup(ServerMainModule.java:232)
2021-03-03T19:51:16.0792826Z Caused by: java.lang.NullPointerException
2021-03-03T19:51:16.0799113Z at io.airlift.discovery.client.DiscoveryBinder$HttpAnnouncementProvider.get(DiscoveryBinder.java:128)
2021-03-03T19:51:16.0805716Z at io.airlift.discovery.client.DiscoveryBinder$HttpAnnouncementProvider.get(DiscoveryBinder.java:108)
2021-03-03T19:51:16.0812674Z at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:85)
2021-03-03T19:51:16.0821851Z at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:57)
2021-03-03T19:51:16.0825264Z at com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:66)
2021-03-03T19:51:16.0832364Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
2021-03-03T19:51:16.0837399Z at io.airlift.bootstrap.LifeCycleModule.provision(LifeCycleModule.java:54)
2021-03-03T19:51:16.0846880Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:120)
2021-03-03T19:51:16.0854943Z at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:66)
2021-03-03T19:51:16.0861923Z at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:61)
2021-03-03T19:51:16.0871499Z at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:47)
2021-03-03T19:51:16.0878621Z at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:42)
2021-03-03T19:51:16.0882264Z at com.google.inject.internal.RealMultibinder$RealMultibinderProvider.doProvision(RealMultibinder.java:198)
2021-03-03T19:51:16.0886928Z at com.google.inject.internal.RealMultibinder$RealMultibinderProvider.doProvision(RealMultibinder.java:151)
2021-03-03T19:51:16.0938576Z at com.google.inject.internal.InternalProviderInstanceBindingImpl$Factory$1.call(InternalProviderInstanceBindingImpl.java:120)
2021-03-03T19:51:16.0942063Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
2021-03-03T19:51:16.0944593Z at io.airlift.bootstrap.LifeCycleModule.provision(LifeCycleModule.java:54)
2021-03-03T19:51:16.0947395Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:120)
2021-03-03T19:51:16.0950831Z at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:66)
2021-03-03T19:51:16.0954386Z at com.google.inject.internal.InternalProviderInstanceBindingImpl$Factory.get(InternalProviderInstanceBindingImpl.java:115)
2021-03-03T19:51:16.0957522Z at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:42)
2021-03-03T19:51:16.0960204Z at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:65)
2021-03-03T19:51:16.0962780Z at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:113)
2021-03-03T19:51:16.0965142Z at com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
2021-03-03T19:51:16.0967274Z at com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:98)
2021-03-03T19:51:16.0969868Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
2021-03-03T19:51:16.0972399Z at io.airlift.bootstrap.LifeCycleModule.provision(LifeCycleModule.java:54)
2021-03-03T19:51:16.0974933Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:120)
2021-03-03T19:51:16.0978462Z at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:66)
2021-03-03T19:51:16.0981456Z at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:93)
2021-03-03T19:51:16.0983831Z at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:306)
2021-03-03T19:51:16.0986679Z at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
2021-03-03T19:51:16.0989186Z at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:168)
2021-03-03T19:51:16.0991687Z at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:39)
2021-03-03T19:51:16.0994735Z at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:42)
2021-03-03T19:51:16.0997400Z at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:65)
2021-03-03T19:51:16.0999844Z at com.google.inject.internal.ProviderMethod.doProvision(ProviderMethod.java:173)
2021-03-03T19:51:16.1002886Z at com.google.inject.internal.InternalProviderInstanceBindingImpl$CyclicFactory.provision(InternalProviderInstanceBindingImpl.java:185)
2021-03-03T19:51:16.1006695Z at com.google.inject.internal.InternalProviderInstanceBindingImpl$CyclicFactory.access$300(InternalProviderInstanceBindingImpl.java:139)
2021-03-03T19:51:16.1010382Z at com.google.inject.internal.InternalProviderInstanceBindingImpl$CyclicFactory$1.call(InternalProviderInstanceBindingImpl.java:169)
2021-03-03T19:51:16.1013827Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
2021-03-03T19:51:16.1045032Z at io.airlift.bootstrap.LifeCycleModule.provision(LifeCycleModule.java:54)
2021-03-03T19:51:16.1047610Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:120)
2021-03-03T19:51:16.1050957Z at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:66)
2021-03-03T19:51:16.1054561Z at com.google.inject.internal.InternalProviderInstanceBindingImpl$CyclicFactory.get(InternalProviderInstanceBindingImpl.java:164)
2021-03-03T19:51:16.1058656Z at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
2021-03-03T19:51:16.1061165Z at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:168)
2021-03-03T19:51:16.1063700Z at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:39)
2021-03-03T19:51:16.1066287Z at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:62)
2021-03-03T19:51:16.1068886Z at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
2021-03-03T19:51:16.1071430Z at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:168)
2021-03-03T19:51:16.1073941Z at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:39)
2021-03-03T19:51:16.1077011Z at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:42)
2021-03-03T19:51:16.1079697Z at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:65)
2021-03-03T19:51:16.1082208Z at com.google.inject.internal.SingleMethodInjector.inject(SingleMethodInjector.java:82)
2021-03-03T19:51:16.1084806Z at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:147)
2021-03-03T19:51:16.1087609Z at com.google.inject.internal.MembersInjectorImpl.injectAndNotify(MembersInjectorImpl.java:101)
2021-03-03T19:51:16.1089950Z at com.google.inject.internal.Initializer$InjectableReference.get(Initializer.java:245)
2021-03-03T19:51:16.1091741Z at com.google.inject.internal.Initializer.injectAll(Initializer.java:140)
2021-03-03T19:51:16.1094338Z at com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:178)
2021-03-03T19:51:16.1097415Z at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:111)
2021-03-03T19:51:16.1099389Z at com.google.inject.Guice.createInjector(Guice.java:87)
2021-03-03T19:51:16.1100764Z at io.airlift.bootstrap.Bootstrap.initialize(Bootstrap.java:276)
2021-03-03T19:51:16.1102450Z at io.trino.server.testing.TestingTrinoServer.<init>(TestingTrinoServer.java:271)
2021-03-03T19:51:16.1104301Z at io.trino.server.testing.TestingTrinoServer$Builder.build(TestingTrinoServer.java:641)
2021-03-03T19:51:16.1107355Z at io.trino.server.security.oauth2.TestOAuth2WebUiAuthenticationFilter.setup(TestOAuth2WebUiAuthenticationFilter.java:153)
2021-03-03T19:51:16.1110505Z at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2021-03-03T19:51:16.1112856Z at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2021-03-03T19:51:16.1115608Z at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2021-03-03T19:51:16.1117632Z at java.base/java.lang.reflect.Method.invoke(Method.java:566)
2021-03-03T19:51:16.1119484Z at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:104)
2021-03-03T19:51:16.1121820Z at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:515)
2021-03-03T19:51:16.1123697Z at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:217)
2021-03-03T19:51:16.1125450Z at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:144)
2021-03-03T19:51:16.1127702Z at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:169)
2021-03-03T19:51:16.1129996Z at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
2021-03-03T19:51:16.1131787Z at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
2021-03-03T19:51:16.1133871Z at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
2021-03-03T19:51:16.1135181Z at java.base/java.lang.Thread.run(Thread.java:834)
2021-03-03T19:51:16.1216441Z
2021-03-03T19:51:16.1217329Z 2) Error injecting constructor, java.io.UncheckedIOException: Failed to bind to localhost/127.0.0.1:46629
2021-03-03T19:51:16.1218754Z at io.airlift.http.server.HttpServerInfo.<init>(HttpServerInfo.java:48)
2021-03-03T19:51:16.1221066Z at io.airlift.http.server.testing.TestingHttpServerModule.configure(TestingHttpServerModule.java:65)
2021-03-03T19:51:16.1223214Z while locating io.airlift.http.server.HttpServerInfo
2021-03-03T19:51:16.1225641Z for the 1st parameter of io.airlift.http.server.LocalAnnouncementHttpServerInfo.<init>(LocalAnnouncementHttpServerInfo.java:31)
2021-03-03T19:51:16.1228002Z while locating io.airlift.http.server.LocalAnnouncementHttpServerInfo
2021-03-03T19:51:16.1229841Z while locating io.airlift.discovery.client.AnnouncementHttpServerInfo
2021-03-03T19:51:16.1232629Z for the 1st parameter of io.airlift.discovery.client.DiscoveryBinder$HttpAnnouncementProvider.setAnnouncementHttpServerInfo(DiscoveryBinder.java:122)
2021-03-03T19:51:16.1237413Z at io.airlift.discovery.client.DiscoveryBinder.bindServiceAnnouncement(DiscoveryBinder.java:79) (via modules: io.trino.server.ServerMainModule -> io.trino.server.CoordinatorModule)
2021-03-03T19:51:16.1240189Z Caused by: java.io.UncheckedIOException: Failed to bind to localhost/127.0.0.1:46629
2021-03-03T19:51:16.1241797Z at io.airlift.http.server.HttpServerInfo.createChannel(HttpServerInfo.java:164)
2021-03-03T19:51:16.1339838Z at io.airlift.http.server.HttpServerInfo.<init>(HttpServerInfo.java:61)
2021-03-03T19:51:16.1341480Z at io.airlift.http.server.HttpServerInfo$$FastClassByGuice$$bd4c327f.newInstance(<generated>)
2021-03-03T19:51:16.1344092Z at com.google.inject.internal.DefaultConstructionProxyFactory$FastClassProxy.newInstance(DefaultConstructionProxyFactory.java:89)
2021-03-03T19:51:16.1347052Z at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:114)
2021-03-03T19:51:16.1349441Z at com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
2021-03-03T19:51:16.1351572Z at com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:98)
2021-03-03T19:51:16.1354175Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
2021-03-03T19:51:16.1356709Z at io.airlift.bootstrap.LifeCycleModule.provision(LifeCycleModule.java:54)
2021-03-03T19:51:16.1359255Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:120)
2021-03-03T19:51:16.1362613Z at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:66)
2021-03-03T19:51:16.1365651Z at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:93)
2021-03-03T19:51:16.1367991Z at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:306)
2021-03-03T19:51:16.1370835Z at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
2021-03-03T19:51:16.1373337Z at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:168)
2021-03-03T19:51:16.1375968Z at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:39)
2021-03-03T19:51:16.1378987Z at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:42)
2021-03-03T19:51:16.1381669Z at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:65)
2021-03-03T19:51:16.1384233Z at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:113)
2021-03-03T19:51:16.1386610Z at com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
2021-03-03T19:51:16.1388755Z at com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:98)
2021-03-03T19:51:16.1391337Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
2021-03-03T19:51:16.1394207Z at io.airlift.bootstrap.LifeCycleModule.provision(LifeCycleModule.java:54)
2021-03-03T19:51:16.1396748Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:120)
2021-03-03T19:51:16.1400177Z at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:66)
2021-03-03T19:51:16.1403262Z at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:93)
2021-03-03T19:51:16.1405639Z at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:306)
2021-03-03T19:51:16.1407574Z at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:62)
2021-03-03T19:51:16.1409739Z at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:42)
2021-03-03T19:51:16.1412371Z at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:65)
2021-03-03T19:51:16.1415053Z at com.google.inject.internal.SingleMethodInjector.inject(SingleMethodInjector.java:82)
2021-03-03T19:51:16.1448314Z at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:147)
2021-03-03T19:51:16.1450921Z at com.google.inject.internal.MembersInjectorImpl.injectAndNotify(MembersInjectorImpl.java:101)
2021-03-03T19:51:16.1453356Z at com.google.inject.internal.Initializer$InjectableReference.get(Initializer.java:245)
2021-03-03T19:51:16.1455036Z at com.google.inject.internal.Initializer.injectAll(Initializer.java:140)
2021-03-03T19:51:16.1457506Z at com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:178)
2021-03-03T19:51:16.1460294Z at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:111)
2021-03-03T19:51:16.1462084Z at com.google.inject.Guice.createInjector(Guice.java:87)
2021-03-03T19:51:16.1463565Z at io.airlift.bootstrap.Bootstrap.initialize(Bootstrap.java:276)
2021-03-03T19:51:16.1465215Z at io.trino.server.testing.TestingTrinoServer.<init>(TestingTrinoServer.java:271)
2021-03-03T19:51:16.1467077Z at io.trino.server.testing.TestingTrinoServer$Builder.build(TestingTrinoServer.java:641)
2021-03-03T19:51:16.1470118Z at io.trino.server.security.oauth2.TestOAuth2WebUiAuthenticationFilter.setup(TestOAuth2WebUiAuthenticationFilter.java:153)
2021-03-03T19:51:16.1473204Z at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2021-03-03T19:51:16.1475582Z at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2021-03-03T19:51:16.1478318Z at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2021-03-03T19:51:16.1480348Z at java.base/java.lang.reflect.Method.invoke(Method.java:566)
2021-03-03T19:51:16.1482190Z at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:104)
2021-03-03T19:51:16.1484483Z at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:515)
2021-03-03T19:51:16.1486352Z at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:217)
2021-03-03T19:51:16.1488091Z at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:144)
2021-03-03T19:51:16.1490335Z at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:169)
2021-03-03T19:51:16.1492559Z at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
2021-03-03T19:51:16.1494457Z at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
2021-03-03T19:51:16.1496540Z at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
2021-03-03T19:51:16.1497832Z at java.base/java.lang.Thread.run(Thread.java:834)
2021-03-03T19:51:16.1498671Z Caused by: java.net.BindException: Address already in use
2021-03-03T19:51:16.1499505Z at java.base/sun.nio.ch.Net.bind0(Native Method)
2021-03-03T19:51:16.1500415Z at java.base/sun.nio.ch.Net.bind(Net.java:455)
2021-03-03T19:51:16.1501123Z at java.base/sun.nio.ch.Net.bind(Net.java:447)
2021-03-03T19:51:16.1502407Z at java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:227)
2021-03-03T19:51:16.1504147Z at java.base/sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:80)
2021-03-03T19:51:16.1505987Z at io.airlift.http.server.HttpServerInfo.createChannel(HttpServerInfo.java:160)
2021-03-03T19:51:16.1507199Z ... 54 more
2021-03-03T19:51:16.1507503Z
2021-03-03T19:51:16.1508322Z 3) Error injecting constructor, java.io.UncheckedIOException: Failed to bind to localhost/127.0.0.1:46629
2021-03-03T19:51:16.1509719Z at io.airlift.http.server.HttpServerInfo.<init>(HttpServerInfo.java:48)
2021-03-03T19:51:16.1512018Z at io.airlift.http.server.testing.TestingHttpServerModule.configure(TestingHttpServerModule.java:65)
2021-03-03T19:51:16.1514170Z while locating io.airlift.http.server.HttpServerInfo
2021-03-03T19:51:16.1516333Z for the 1st parameter of io.airlift.http.server.LocalAnnouncementHttpServerInfo.<init>(LocalAnnouncementHttpServerInfo.java:31)
2021-03-03T19:51:16.1518865Z while locating io.airlift.http.server.LocalAnnouncementHttpServerInfo
2021-03-03T19:51:16.1520849Z while locating io.airlift.discovery.client.AnnouncementHttpServerInfo
2021-03-03T19:51:16.1656366Z for the 1st parameter of io.airlift.discovery.client.DiscoveryBinder$HttpAnnouncementProvider.setAnnouncementHttpServerInfo(DiscoveryBinder.java:122)
2021-03-03T19:51:16.1659822Z at io.airlift.discovery.client.DiscoveryBinder.bindServiceAnnouncement(DiscoveryBinder.java:79)
2021-03-03T19:51:16.1661869Z Caused by: java.io.UncheckedIOException (same stack trace as error #2)
2021-03-03T19:51:16.1662583Z 3 errors
2021-03-03T19:51:16.1664266Z at com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:554)
2021-03-03T19:51:16.1667451Z at com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:180)
2021-03-03T19:51:16.1670441Z at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:111)
2021-03-03T19:51:16.1672392Z at com.google.inject.Guice.createInjector(Guice.java:87)
2021-03-03T19:51:16.1673771Z at io.airlift.bootstrap.Bootstrap.initialize(Bootstrap.java:276)
2021-03-03T19:51:16.1675406Z at io.trino.server.testing.TestingTrinoServer.<init>(TestingTrinoServer.java:271)
2021-03-03T19:51:16.1677270Z at io.trino.server.testing.TestingTrinoServer$Builder.build(TestingTrinoServer.java:641)
2021-03-03T19:51:16.1680374Z at io.trino.server.security.oauth2.TestOAuth2WebUiAuthenticationFilter.setup(TestOAuth2WebUiAuthenticationFilter.java:153)
2021-03-03T19:51:16.1683790Z at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2021-03-03T19:51:16.1686122Z at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2021-03-03T19:51:16.1688869Z at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2021-03-03T19:51:16.1690880Z at java.base/java.lang.reflect.Method.invoke(Method.java:566)
2021-03-03T19:51:16.1692763Z at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:104)
2021-03-03T19:51:16.1695046Z at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:515)
2021-03-03T19:51:16.1697123Z at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:217)
2021-03-03T19:51:16.1698863Z at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:144)
2021-03-03T19:51:16.1701123Z at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:169)
2021-03-03T19:51:16.1703302Z at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
2021-03-03T19:51:16.1705188Z at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
2021-03-03T19:51:16.1707189Z at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
2021-03-03T19:51:16.1708779Z at java.base/java.lang.Thread.run(Thread.java:834)
2021-03-03T19:51:16.1709253Z
2021-03-03T19:51:16.5994681Z [INFO]
2021-03-03T19:51:16.5997484Z [INFO] Results:
2021-03-03T19:51:16.5999356Z [INFO]
2021-03-03T19:51:16.6002425Z [ERROR] Failures:
2021-03-03T19:51:16.6038605Z [ERROR] TestOAuth2WebUiAuthenticationFilter.setup:153 » Creation Unable to create inje...
2021-03-03T19:51:16.6041644Z [INFO]
```
|
1.0
|
TestOAuth2WebUiAuthenticationFilter.setup is flaky - ```
021-03-03T19:51:16.0690425Z Unable to create injector, see the following errors:
2021-03-03T19:51:16.0690893Z
2021-03-03T19:51:16.0695891Z 1) Error in custom provider, java.lang.NullPointerException
2021-03-03T19:51:16.0710245Z at io.airlift.discovery.client.DiscoveryBinder.bindServiceAnnouncement(DiscoveryBinder.java:79) (via modules: io.trino.server.ServerMainModule -> io.trino.server.CoordinatorModule)
2021-03-03T19:51:16.0719185Z while locating io.airlift.discovery.client.ServiceAnnouncement annotated with @com.google.inject.internal.Element(setName=,uniqueId=1870, type=MULTIBINDER, keyType=)
2021-03-03T19:51:16.0723513Z while locating java.util.Set<io.airlift.discovery.client.ServiceAnnouncement>
2021-03-03T19:51:16.0729486Z for the 2nd parameter of io.airlift.discovery.client.Announcer.<init>(Announcer.java:68)
2021-03-03T19:51:16.0737655Z at io.airlift.discovery.client.testing.TestingDiscoveryModule.configure(TestingDiscoveryModule.java:49)
2021-03-03T19:51:16.0739954Z while locating io.airlift.discovery.client.Announcer
2021-03-03T19:51:16.0752822Z for the 2nd parameter of io.airlift.discovery.client.testing.TestingDiscoveryModule.createMergingServiceSelectorFactory(TestingDiscoveryModule.java:69)
2021-03-03T19:51:16.0760715Z at io.airlift.discovery.client.testing.TestingDiscoveryModule.createMergingServiceSelectorFactory(TestingDiscoveryModule.java:69)
2021-03-03T19:51:16.0764574Z while locating io.airlift.discovery.client.MergingServiceSelectorFactory
2021-03-03T19:51:16.0772135Z at io.airlift.discovery.client.testing.TestingDiscoveryModule.configure(TestingDiscoveryModule.java:55)
2021-03-03T19:51:16.0775631Z while locating io.airlift.discovery.client.ServiceSelectorFactory
2021-03-03T19:51:16.0785857Z for the 1st parameter of io.airlift.discovery.client.ServiceSelectorProvider.setServiceSelectorFactory(ServiceSelectorProvider.java:50)
2021-03-03T19:51:16.0788811Z at io.trino.server.ServerMainModule.setup(ServerMainModule.java:232)
2021-03-03T19:51:16.0792826Z Caused by: java.lang.NullPointerException
2021-03-03T19:51:16.0799113Z at io.airlift.discovery.client.DiscoveryBinder$HttpAnnouncementProvider.get(DiscoveryBinder.java:128)
2021-03-03T19:51:16.0805716Z at io.airlift.discovery.client.DiscoveryBinder$HttpAnnouncementProvider.get(DiscoveryBinder.java:108)
2021-03-03T19:51:16.0812674Z at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:85)
2021-03-03T19:51:16.0821851Z at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:57)
2021-03-03T19:51:16.0825264Z at com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:66)
2021-03-03T19:51:16.0832364Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
2021-03-03T19:51:16.0837399Z at io.airlift.bootstrap.LifeCycleModule.provision(LifeCycleModule.java:54)
2021-03-03T19:51:16.0846880Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:120)
2021-03-03T19:51:16.0854943Z at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:66)
2021-03-03T19:51:16.0861923Z at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:61)
2021-03-03T19:51:16.0871499Z at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:47)
2021-03-03T19:51:16.0878621Z at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:42)
2021-03-03T19:51:16.0882264Z at com.google.inject.internal.RealMultibinder$RealMultibinderProvider.doProvision(RealMultibinder.java:198)
2021-03-03T19:51:16.0886928Z at com.google.inject.internal.RealMultibinder$RealMultibinderProvider.doProvision(RealMultibinder.java:151)
2021-03-03T19:51:16.0938576Z at com.google.inject.internal.InternalProviderInstanceBindingImpl$Factory$1.call(InternalProviderInstanceBindingImpl.java:120)
2021-03-03T19:51:16.0942063Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
2021-03-03T19:51:16.0944593Z at io.airlift.bootstrap.LifeCycleModule.provision(LifeCycleModule.java:54)
2021-03-03T19:51:16.0947395Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:120)
2021-03-03T19:51:16.0950831Z at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:66)
2021-03-03T19:51:16.0954386Z at com.google.inject.internal.InternalProviderInstanceBindingImpl$Factory.get(InternalProviderInstanceBindingImpl.java:115)
2021-03-03T19:51:16.0957522Z at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:42)
2021-03-03T19:51:16.0960204Z at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:65)
2021-03-03T19:51:16.0962780Z at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:113)
2021-03-03T19:51:16.0965142Z at com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
2021-03-03T19:51:16.0967274Z at com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:98)
2021-03-03T19:51:16.0969868Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
2021-03-03T19:51:16.0972399Z at io.airlift.bootstrap.LifeCycleModule.provision(LifeCycleModule.java:54)
2021-03-03T19:51:16.0974933Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:120)
2021-03-03T19:51:16.0978462Z at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:66)
2021-03-03T19:51:16.0981456Z at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:93)
2021-03-03T19:51:16.0983831Z at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:306)
2021-03-03T19:51:16.0986679Z at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
2021-03-03T19:51:16.0989186Z at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:168)
2021-03-03T19:51:16.0991687Z at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:39)
2021-03-03T19:51:16.0994735Z at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:42)
2021-03-03T19:51:16.0997400Z at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:65)
2021-03-03T19:51:16.0999844Z at com.google.inject.internal.ProviderMethod.doProvision(ProviderMethod.java:173)
2021-03-03T19:51:16.1002886Z at com.google.inject.internal.InternalProviderInstanceBindingImpl$CyclicFactory.provision(InternalProviderInstanceBindingImpl.java:185)
2021-03-03T19:51:16.1006695Z at com.google.inject.internal.InternalProviderInstanceBindingImpl$CyclicFactory.access$300(InternalProviderInstanceBindingImpl.java:139)
2021-03-03T19:51:16.1010382Z at com.google.inject.internal.InternalProviderInstanceBindingImpl$CyclicFactory$1.call(InternalProviderInstanceBindingImpl.java:169)
2021-03-03T19:51:16.1013827Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
2021-03-03T19:51:16.1045032Z at io.airlift.bootstrap.LifeCycleModule.provision(LifeCycleModule.java:54)
2021-03-03T19:51:16.1047610Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:120)
2021-03-03T19:51:16.1050957Z at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:66)
2021-03-03T19:51:16.1054561Z at com.google.inject.internal.InternalProviderInstanceBindingImpl$CyclicFactory.get(InternalProviderInstanceBindingImpl.java:164)
2021-03-03T19:51:16.1058656Z at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
2021-03-03T19:51:16.1061165Z at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:168)
2021-03-03T19:51:16.1063700Z at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:39)
2021-03-03T19:51:16.1066287Z at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:62)
2021-03-03T19:51:16.1068886Z at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
2021-03-03T19:51:16.1071430Z at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:168)
2021-03-03T19:51:16.1073941Z at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:39)
2021-03-03T19:51:16.1077011Z at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:42)
2021-03-03T19:51:16.1079697Z at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:65)
2021-03-03T19:51:16.1082208Z at com.google.inject.internal.SingleMethodInjector.inject(SingleMethodInjector.java:82)
2021-03-03T19:51:16.1084806Z at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:147)
2021-03-03T19:51:16.1087609Z at com.google.inject.internal.MembersInjectorImpl.injectAndNotify(MembersInjectorImpl.java:101)
2021-03-03T19:51:16.1089950Z at com.google.inject.internal.Initializer$InjectableReference.get(Initializer.java:245)
2021-03-03T19:51:16.1091741Z at com.google.inject.internal.Initializer.injectAll(Initializer.java:140)
2021-03-03T19:51:16.1094338Z at com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:178)
2021-03-03T19:51:16.1097415Z at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:111)
2021-03-03T19:51:16.1099389Z at com.google.inject.Guice.createInjector(Guice.java:87)
2021-03-03T19:51:16.1100764Z at io.airlift.bootstrap.Bootstrap.initialize(Bootstrap.java:276)
2021-03-03T19:51:16.1102450Z at io.trino.server.testing.TestingTrinoServer.<init>(TestingTrinoServer.java:271)
2021-03-03T19:51:16.1104301Z at io.trino.server.testing.TestingTrinoServer$Builder.build(TestingTrinoServer.java:641)
2021-03-03T19:51:16.1107355Z at io.trino.server.security.oauth2.TestOAuth2WebUiAuthenticationFilter.setup(TestOAuth2WebUiAuthenticationFilter.java:153)
2021-03-03T19:51:16.1110505Z at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2021-03-03T19:51:16.1112856Z at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2021-03-03T19:51:16.1115608Z at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2021-03-03T19:51:16.1117632Z at java.base/java.lang.reflect.Method.invoke(Method.java:566)
2021-03-03T19:51:16.1119484Z at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:104)
2021-03-03T19:51:16.1121820Z at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:515)
2021-03-03T19:51:16.1123697Z at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:217)
2021-03-03T19:51:16.1125450Z at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:144)
2021-03-03T19:51:16.1127702Z at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:169)
2021-03-03T19:51:16.1129996Z at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
2021-03-03T19:51:16.1131787Z at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
2021-03-03T19:51:16.1133871Z at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
2021-03-03T19:51:16.1135181Z at java.base/java.lang.Thread.run(Thread.java:834)
2021-03-03T19:51:16.1216441Z
2021-03-03T19:51:16.1217329Z 2) Error injecting constructor, java.io.UncheckedIOException: Failed to bind to localhost/127.0.0.1:46629
2021-03-03T19:51:16.1218754Z at io.airlift.http.server.HttpServerInfo.<init>(HttpServerInfo.java:48)
2021-03-03T19:51:16.1221066Z at io.airlift.http.server.testing.TestingHttpServerModule.configure(TestingHttpServerModule.java:65)
2021-03-03T19:51:16.1223214Z while locating io.airlift.http.server.HttpServerInfo
2021-03-03T19:51:16.1225641Z for the 1st parameter of io.airlift.http.server.LocalAnnouncementHttpServerInfo.<init>(LocalAnnouncementHttpServerInfo.java:31)
2021-03-03T19:51:16.1228002Z while locating io.airlift.http.server.LocalAnnouncementHttpServerInfo
2021-03-03T19:51:16.1229841Z while locating io.airlift.discovery.client.AnnouncementHttpServerInfo
2021-03-03T19:51:16.1232629Z for the 1st parameter of io.airlift.discovery.client.DiscoveryBinder$HttpAnnouncementProvider.setAnnouncementHttpServerInfo(DiscoveryBinder.java:122)
2021-03-03T19:51:16.1237413Z at io.airlift.discovery.client.DiscoveryBinder.bindServiceAnnouncement(DiscoveryBinder.java:79) (via modules: io.trino.server.ServerMainModule -> io.trino.server.CoordinatorModule)
2021-03-03T19:51:16.1240189Z Caused by: java.io.UncheckedIOException: Failed to bind to localhost/127.0.0.1:46629
2021-03-03T19:51:16.1241797Z at io.airlift.http.server.HttpServerInfo.createChannel(HttpServerInfo.java:164)
2021-03-03T19:51:16.1339838Z at io.airlift.http.server.HttpServerInfo.<init>(HttpServerInfo.java:61)
2021-03-03T19:51:16.1341480Z at io.airlift.http.server.HttpServerInfo$$FastClassByGuice$$bd4c327f.newInstance(<generated>)
2021-03-03T19:51:16.1344092Z at com.google.inject.internal.DefaultConstructionProxyFactory$FastClassProxy.newInstance(DefaultConstructionProxyFactory.java:89)
2021-03-03T19:51:16.1347052Z at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:114)
2021-03-03T19:51:16.1349441Z at com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
2021-03-03T19:51:16.1351572Z at com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:98)
2021-03-03T19:51:16.1354175Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
2021-03-03T19:51:16.1356709Z at io.airlift.bootstrap.LifeCycleModule.provision(LifeCycleModule.java:54)
2021-03-03T19:51:16.1359255Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:120)
2021-03-03T19:51:16.1362613Z at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:66)
2021-03-03T19:51:16.1365651Z at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:93)
2021-03-03T19:51:16.1367991Z at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:306)
2021-03-03T19:51:16.1370835Z at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
2021-03-03T19:51:16.1373337Z at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:168)
2021-03-03T19:51:16.1375968Z at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:39)
2021-03-03T19:51:16.1378987Z at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:42)
2021-03-03T19:51:16.1381669Z at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:65)
2021-03-03T19:51:16.1384233Z at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:113)
2021-03-03T19:51:16.1386610Z at com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
2021-03-03T19:51:16.1388755Z at com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:98)
2021-03-03T19:51:16.1391337Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
2021-03-03T19:51:16.1394207Z at io.airlift.bootstrap.LifeCycleModule.provision(LifeCycleModule.java:54)
2021-03-03T19:51:16.1396748Z at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:120)
2021-03-03T19:51:16.1400177Z at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:66)
2021-03-03T19:51:16.1403262Z at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:93)
2021-03-03T19:51:16.1405639Z at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:306)
2021-03-03T19:51:16.1407574Z at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:62)
2021-03-03T19:51:16.1409739Z at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:42)
2021-03-03T19:51:16.1412371Z at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:65)
2021-03-03T19:51:16.1415053Z at com.google.inject.internal.SingleMethodInjector.inject(SingleMethodInjector.java:82)
2021-03-03T19:51:16.1448314Z at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:147)
2021-03-03T19:51:16.1450921Z at com.google.inject.internal.MembersInjectorImpl.injectAndNotify(MembersInjectorImpl.java:101)
2021-03-03T19:51:16.1453356Z at com.google.inject.internal.Initializer$InjectableReference.get(Initializer.java:245)
2021-03-03T19:51:16.1455036Z at com.google.inject.internal.Initializer.injectAll(Initializer.java:140)
2021-03-03T19:51:16.1457506Z at com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:178)
2021-03-03T19:51:16.1460294Z at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:111)
2021-03-03T19:51:16.1462084Z at com.google.inject.Guice.createInjector(Guice.java:87)
2021-03-03T19:51:16.1463565Z at io.airlift.bootstrap.Bootstrap.initialize(Bootstrap.java:276)
2021-03-03T19:51:16.1465215Z at io.trino.server.testing.TestingTrinoServer.<init>(TestingTrinoServer.java:271)
2021-03-03T19:51:16.1467077Z at io.trino.server.testing.TestingTrinoServer$Builder.build(TestingTrinoServer.java:641)
2021-03-03T19:51:16.1470118Z at io.trino.server.security.oauth2.TestOAuth2WebUiAuthenticationFilter.setup(TestOAuth2WebUiAuthenticationFilter.java:153)
2021-03-03T19:51:16.1473204Z at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2021-03-03T19:51:16.1475582Z at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2021-03-03T19:51:16.1478318Z at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2021-03-03T19:51:16.1480348Z at java.base/java.lang.reflect.Method.invoke(Method.java:566)
2021-03-03T19:51:16.1482190Z at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:104)
2021-03-03T19:51:16.1484483Z at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:515)
2021-03-03T19:51:16.1486352Z at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:217)
2021-03-03T19:51:16.1488091Z at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:144)
2021-03-03T19:51:16.1490335Z at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:169)
2021-03-03T19:51:16.1492559Z at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
2021-03-03T19:51:16.1494457Z at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
2021-03-03T19:51:16.1496540Z at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
2021-03-03T19:51:16.1497832Z at java.base/java.lang.Thread.run(Thread.java:834)
2021-03-03T19:51:16.1498671Z Caused by: java.net.BindException: Address already in use
2021-03-03T19:51:16.1499505Z at java.base/sun.nio.ch.Net.bind0(Native Method)
2021-03-03T19:51:16.1500415Z at java.base/sun.nio.ch.Net.bind(Net.java:455)
2021-03-03T19:51:16.1501123Z at java.base/sun.nio.ch.Net.bind(Net.java:447)
2021-03-03T19:51:16.1502407Z at java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:227)
2021-03-03T19:51:16.1504147Z at java.base/sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:80)
2021-03-03T19:51:16.1505987Z at io.airlift.http.server.HttpServerInfo.createChannel(HttpServerInfo.java:160)
2021-03-03T19:51:16.1507199Z ... 54 more
2021-03-03T19:51:16.1507503Z
2021-03-03T19:51:16.1508322Z 3) Error injecting constructor, java.io.UncheckedIOException: Failed to bind to localhost/127.0.0.1:46629
2021-03-03T19:51:16.1509719Z at io.airlift.http.server.HttpServerInfo.<init>(HttpServerInfo.java:48)
2021-03-03T19:51:16.1512018Z at io.airlift.http.server.testing.TestingHttpServerModule.configure(TestingHttpServerModule.java:65)
2021-03-03T19:51:16.1514170Z while locating io.airlift.http.server.HttpServerInfo
2021-03-03T19:51:16.1516333Z for the 1st parameter of io.airlift.http.server.LocalAnnouncementHttpServerInfo.<init>(LocalAnnouncementHttpServerInfo.java:31)
2021-03-03T19:51:16.1518865Z while locating io.airlift.http.server.LocalAnnouncementHttpServerInfo
2021-03-03T19:51:16.1520849Z while locating io.airlift.discovery.client.AnnouncementHttpServerInfo
2021-03-03T19:51:16.1656366Z for the 1st parameter of io.airlift.discovery.client.DiscoveryBinder$HttpAnnouncementProvider.setAnnouncementHttpServerInfo(DiscoveryBinder.java:122)
2021-03-03T19:51:16.1659822Z at io.airlift.discovery.client.DiscoveryBinder.bindServiceAnnouncement(DiscoveryBinder.java:79)
2021-03-03T19:51:16.1661869Z Caused by: java.io.UncheckedIOException (same stack trace as error #2)
2021-03-03T19:51:16.1662583Z 3 errors
2021-03-03T19:51:16.1664266Z at com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:554)
2021-03-03T19:51:16.1667451Z at com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:180)
2021-03-03T19:51:16.1670441Z at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:111)
2021-03-03T19:51:16.1672392Z at com.google.inject.Guice.createInjector(Guice.java:87)
2021-03-03T19:51:16.1673771Z at io.airlift.bootstrap.Bootstrap.initialize(Bootstrap.java:276)
2021-03-03T19:51:16.1675406Z at io.trino.server.testing.TestingTrinoServer.<init>(TestingTrinoServer.java:271)
2021-03-03T19:51:16.1677270Z at io.trino.server.testing.TestingTrinoServer$Builder.build(TestingTrinoServer.java:641)
2021-03-03T19:51:16.1680374Z at io.trino.server.security.oauth2.TestOAuth2WebUiAuthenticationFilter.setup(TestOAuth2WebUiAuthenticationFilter.java:153)
2021-03-03T19:51:16.1683790Z at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2021-03-03T19:51:16.1686122Z at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2021-03-03T19:51:16.1688869Z at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2021-03-03T19:51:16.1690880Z at java.base/java.lang.reflect.Method.invoke(Method.java:566)
2021-03-03T19:51:16.1692763Z at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:104)
2021-03-03T19:51:16.1695046Z at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:515)
2021-03-03T19:51:16.1697123Z at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:217)
2021-03-03T19:51:16.1698863Z at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:144)
2021-03-03T19:51:16.1701123Z at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:169)
2021-03-03T19:51:16.1703302Z at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
2021-03-03T19:51:16.1705188Z at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
2021-03-03T19:51:16.1707189Z at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
2021-03-03T19:51:16.1708779Z at java.base/java.lang.Thread.run(Thread.java:834)
2021-03-03T19:51:16.1709253Z
2021-03-03T19:51:16.5994681Z [INFO]
2021-03-03T19:51:16.5997484Z [INFO] Results:
2021-03-03T19:51:16.5999356Z [INFO]
2021-03-03T19:51:16.6002425Z [ERROR] Failures:
2021-03-03T19:51:16.6038605Z [ERROR] TestOAuth2WebUiAuthenticationFilter.setup:153 » Creation Unable to create inje...
2021-03-03T19:51:16.6041644Z [INFO]
```
|
test
|
setup is flaky unable to create injector see the following errors error in custom provider java lang nullpointerexception at io airlift discovery client discoverybinder bindserviceannouncement discoverybinder java via modules io trino server servermainmodule io trino server coordinatormodule while locating io airlift discovery client serviceannouncement annotated with com google inject internal element setname uniqueid type multibinder keytype while locating java util set for the parameter of io airlift discovery client announcer announcer java at io airlift discovery client testing testingdiscoverymodule configure testingdiscoverymodule java while locating io airlift discovery client announcer for the parameter of io airlift discovery client testing testingdiscoverymodule createmergingserviceselectorfactory testingdiscoverymodule java at io airlift discovery client testing testingdiscoverymodule createmergingserviceselectorfactory testingdiscoverymodule java while locating io airlift discovery client mergingserviceselectorfactory at io airlift discovery client testing testingdiscoverymodule configure testingdiscoverymodule java while locating io airlift discovery client serviceselectorfactory for the parameter of io airlift discovery client serviceselectorprovider setserviceselectorfactory serviceselectorprovider java at io trino server servermainmodule setup servermainmodule java caused by java lang nullpointerexception at io airlift discovery client discoverybinder httpannouncementprovider get discoverybinder java at io airlift discovery client discoverybinder httpannouncementprovider get discoverybinder java at com google inject internal providerinternalfactory provision providerinternalfactory java at com google inject internal internalfactorytoinitializableadapter provision internalfactorytoinitializableadapter java at com google inject internal providerinternalfactory call providerinternalfactory java at com google inject internal provisionlistenerstackcallback provision provision provisionlistenerstackcallback java at io airlift bootstrap lifecyclemodule provision lifecyclemodule java at com google inject internal provisionlistenerstackcallback provision provision provisionlistenerstackcallback java at com google inject internal provisionlistenerstackcallback provision provisionlistenerstackcallback java at com google inject internal providerinternalfactory circularget providerinternalfactory java at com google inject internal internalfactorytoinitializableadapter get internalfactorytoinitializableadapter java at com google inject internal singleparameterinjector inject singleparameterinjector java at com google inject internal realmultibinder realmultibinderprovider doprovision realmultibinder java at com google inject internal realmultibinder realmultibinderprovider doprovision realmultibinder java at com google inject internal internalproviderinstancebindingimpl factory call internalproviderinstancebindingimpl java at com google inject internal provisionlistenerstackcallback provision provision provisionlistenerstackcallback java at io airlift bootstrap lifecyclemodule provision lifecyclemodule java at com google inject internal provisionlistenerstackcallback provision provision provisionlistenerstackcallback java at com google inject internal provisionlistenerstackcallback provision provisionlistenerstackcallback java at com google inject internal internalproviderinstancebindingimpl factory get internalproviderinstancebindingimpl java at com google inject internal singleparameterinjector inject singleparameterinjector java at com google inject internal singleparameterinjector getall singleparameterinjector java at com google inject internal constructorinjector provision constructorinjector java at com google inject internal constructorinjector access constructorinjector java at com google inject internal constructorinjector call constructorinjector java at com google inject internal provisionlistenerstackcallback provision provision provisionlistenerstackcallback java at io airlift bootstrap lifecyclemodule provision lifecyclemodule java at com google inject internal provisionlistenerstackcallback provision provision provisionlistenerstackcallback java at com google inject internal provisionlistenerstackcallback provision provisionlistenerstackcallback java at com google inject internal constructorinjector construct constructorinjector java at com google inject internal constructorbindingimpl factory get constructorbindingimpl java at com google inject internal providertointernalfactoryadapter get providertointernalfactoryadapter java at com google inject internal singletonscope get singletonscope java at com google inject internal internalfactorytoprovideradapter get internalfactorytoprovideradapter java at com google inject internal singleparameterinjector inject singleparameterinjector java at com google inject internal singleparameterinjector getall singleparameterinjector java at com google inject internal providermethod doprovision providermethod java at com google inject internal internalproviderinstancebindingimpl cyclicfactory provision internalproviderinstancebindingimpl java at com google inject internal internalproviderinstancebindingimpl cyclicfactory access internalproviderinstancebindingimpl java at com google inject internal internalproviderinstancebindingimpl cyclicfactory call internalproviderinstancebindingimpl java at com google inject internal provisionlistenerstackcallback provision provision provisionlistenerstackcallback java at io airlift bootstrap lifecyclemodule provision lifecyclemodule java at com google inject internal provisionlistenerstackcallback provision provision provisionlistenerstackcallback java at com google inject internal provisionlistenerstackcallback provision provisionlistenerstackcallback java at com google inject internal internalproviderinstancebindingimpl cyclicfactory get internalproviderinstancebindingimpl java at com google inject internal providertointernalfactoryadapter get providertointernalfactoryadapter java at com google inject internal singletonscope get singletonscope java at com google inject internal internalfactorytoprovideradapter get internalfactorytoprovideradapter java at com google inject internal factoryproxy get factoryproxy java at com google inject internal providertointernalfactoryadapter get providertointernalfactoryadapter java at com google inject internal singletonscope get singletonscope java at com google inject internal internalfactorytoprovideradapter get internalfactorytoprovideradapter java at com google inject internal singleparameterinjector inject singleparameterinjector java at com google inject internal singleparameterinjector getall singleparameterinjector java at com google inject internal singlemethodinjector inject singlemethodinjector java at com google inject internal membersinjectorimpl injectmembers membersinjectorimpl java at com google inject internal membersinjectorimpl injectandnotify membersinjectorimpl java at com google inject internal initializer injectablereference get initializer java at com google inject internal initializer injectall initializer java at com google inject internal internalinjectorcreator injectdynamically internalinjectorcreator java at com google inject internal internalinjectorcreator build internalinjectorcreator java at com google inject guice createinjector guice java at io airlift bootstrap bootstrap initialize bootstrap java at io trino server testing testingtrinoserver testingtrinoserver java at io trino server testing testingtrinoserver builder build testingtrinoserver java at io trino server security setup java at java base jdk internal reflect nativemethodaccessorimpl native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java base java lang reflect method invoke method java at org testng internal methodinvocationhelper invokemethod methodinvocationhelper java at org testng internal invoker invokeconfigurationmethod invoker java at org testng internal invoker invokeconfigurations invoker java at org testng internal invoker invokeconfigurations invoker java at org testng internal testmethodworker invokebeforeclassmethods testmethodworker java at org testng internal testmethodworker run testmethodworker java at java base java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java base java util concurrent threadpoolexecutor worker run threadpoolexecutor java at java base java lang thread run thread java error injecting constructor java io uncheckedioexception failed to bind to localhost at io airlift http server httpserverinfo httpserverinfo java at io airlift http server testing testinghttpservermodule configure testinghttpservermodule java while locating io airlift http server httpserverinfo for the parameter of io airlift http server localannouncementhttpserverinfo localannouncementhttpserverinfo java while locating io airlift http server localannouncementhttpserverinfo while locating io airlift discovery client announcementhttpserverinfo for the parameter of io airlift discovery client discoverybinder httpannouncementprovider setannouncementhttpserverinfo discoverybinder java at io airlift discovery client discoverybinder bindserviceannouncement discoverybinder java via modules io trino server servermainmodule io trino server coordinatormodule caused by java io uncheckedioexception failed to bind to localhost at io airlift http server httpserverinfo createchannel httpserverinfo java at io airlift http server httpserverinfo httpserverinfo java at io airlift http server httpserverinfo fastclassbyguice newinstance at com google inject internal defaultconstructionproxyfactory fastclassproxy newinstance defaultconstructionproxyfactory java at com google inject internal constructorinjector provision constructorinjector java at com google inject internal constructorinjector access constructorinjector java at com google inject internal constructorinjector call constructorinjector java at com google inject internal provisionlistenerstackcallback provision provision provisionlistenerstackcallback java at io airlift bootstrap lifecyclemodule provision lifecyclemodule java at com google inject internal provisionlistenerstackcallback provision provision provisionlistenerstackcallback java at com google inject internal provisionlistenerstackcallback provision provisionlistenerstackcallback java at com google inject internal constructorinjector construct constructorinjector java at com google inject internal constructorbindingimpl factory get constructorbindingimpl java at com google inject internal providertointernalfactoryadapter get providertointernalfactoryadapter java at com google inject internal singletonscope get singletonscope java at com google inject internal internalfactorytoprovideradapter get internalfactorytoprovideradapter java at com google inject internal singleparameterinjector inject singleparameterinjector java at com google inject internal singleparameterinjector getall singleparameterinjector java at com google inject internal constructorinjector provision constructorinjector java at com google inject internal constructorinjector access constructorinjector java at com google inject internal constructorinjector call constructorinjector java at com google inject internal provisionlistenerstackcallback provision provision provisionlistenerstackcallback java at io airlift bootstrap lifecyclemodule provision lifecyclemodule java at com google inject internal provisionlistenerstackcallback provision provision provisionlistenerstackcallback java at com google inject internal provisionlistenerstackcallback provision provisionlistenerstackcallback java at com google inject internal constructorinjector construct constructorinjector java at com google inject internal constructorbindingimpl factory get constructorbindingimpl java at com google inject internal factoryproxy get factoryproxy java at com google inject internal singleparameterinjector inject singleparameterinjector java at com google inject internal singleparameterinjector getall singleparameterinjector java at com google inject internal singlemethodinjector inject singlemethodinjector java at com google inject internal membersinjectorimpl injectmembers membersinjectorimpl java at com google inject internal membersinjectorimpl injectandnotify membersinjectorimpl java at com google inject internal initializer injectablereference get initializer java at com google inject internal initializer injectall initializer java at com google inject internal internalinjectorcreator injectdynamically internalinjectorcreator java at com google inject internal internalinjectorcreator build internalinjectorcreator java at com google inject guice createinjector guice java at io airlift bootstrap bootstrap initialize bootstrap java at io trino server testing testingtrinoserver testingtrinoserver java at io trino server testing testingtrinoserver builder build testingtrinoserver java at io trino server security setup java at java base jdk internal reflect nativemethodaccessorimpl native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java base java lang reflect method invoke method java at org testng internal methodinvocationhelper invokemethod methodinvocationhelper java at org testng internal invoker invokeconfigurationmethod invoker java at org testng internal invoker invokeconfigurations invoker java at org testng internal invoker invokeconfigurations invoker java at org testng internal testmethodworker invokebeforeclassmethods testmethodworker java at org testng internal testmethodworker run testmethodworker java at java base java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java base java util concurrent threadpoolexecutor worker run threadpoolexecutor java at java base java lang thread run thread java caused by java net bindexception address already in use at java base sun nio ch net native method at java base sun nio ch net bind net java at java base sun nio ch net bind net java at java base sun nio ch serversocketchannelimpl bind serversocketchannelimpl java at java base sun nio ch serversocketadaptor bind serversocketadaptor java at io airlift http server httpserverinfo createchannel httpserverinfo java more error injecting constructor java io uncheckedioexception failed to bind to localhost at io airlift http server httpserverinfo httpserverinfo java at io airlift http server testing testinghttpservermodule configure testinghttpservermodule java while locating io airlift http server httpserverinfo for the parameter of io airlift http server localannouncementhttpserverinfo localannouncementhttpserverinfo java while locating io airlift http server localannouncementhttpserverinfo while locating io airlift discovery client announcementhttpserverinfo for the parameter of io airlift discovery client discoverybinder httpannouncementprovider setannouncementhttpserverinfo discoverybinder java at io airlift discovery client discoverybinder bindserviceannouncement discoverybinder java caused by java io uncheckedioexception same stack trace as error errors at com google inject internal errors throwcreationexceptioniferrorsexist errors java at com google inject internal internalinjectorcreator injectdynamically internalinjectorcreator java at com google inject internal internalinjectorcreator build internalinjectorcreator java at com google inject guice createinjector guice java at io airlift bootstrap bootstrap initialize bootstrap java at io trino server testing testingtrinoserver testingtrinoserver java at io trino server testing testingtrinoserver builder build testingtrinoserver java at io trino server security setup java at java base jdk internal reflect nativemethodaccessorimpl native method at java base jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at java base jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java base java lang reflect method invoke method java at org testng internal methodinvocationhelper invokemethod methodinvocationhelper java at org testng internal invoker invokeconfigurationmethod invoker java at org testng internal invoker invokeconfigurations invoker java at org testng internal invoker invokeconfigurations invoker java at org testng internal testmethodworker invokebeforeclassmethods testmethodworker java at org testng internal testmethodworker run testmethodworker java at java base java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java base java util concurrent threadpoolexecutor worker run threadpoolexecutor java at java base java lang thread run thread java results failures setup » creation unable to create inje
| 1
|
76,071
| 7,517,464,911
|
IssuesEvent
|
2018-04-12 03:43:56
|
shilpashreelc/ProjectToTest
|
https://api.github.com/repos/shilpashreelc/ProjectToTest
|
opened
|
[Coverity CID:183484] Null pointer dereferences in /tests/net/checksum_offload/src/main.c
|
Coverity area: Tests bug
|
Static code scan issues seen in File: /tests/net/checksum_offload/src/main.c
Category: Null pointer dereferences
Function: recv_cb_offload_disabled
Component: Tests
CID: 183484
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996
|
1.0
|
[Coverity CID:183484] Null pointer dereferences in /tests/net/checksum_offload/src/main.c - Static code scan issues seen in File: /tests/net/checksum_offload/src/main.c
Category: Null pointer dereferences
Function: recv_cb_offload_disabled
Component: Tests
CID: 183484
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996
|
test
|
null pointer dereferences in tests net checksum offload src main c static code scan issues seen in file tests net checksum offload src main c category null pointer dereferences function recv cb offload disabled component tests cid please fix or provide comments to square it off in coverity in the link
| 1
|
329,494
| 28,262,235,563
|
IssuesEvent
|
2023-04-07 01:02:35
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
closed
|
upgrade/upgrades: TestUpgradeSchemaChangerElements failed
|
C-test-failure O-robot branch-master T-sql-schema
|
upgrade/upgrades.TestUpgradeSchemaChangerElements [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/8940378?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/8940378?buildTab=artifacts#/) on master @ [1d4feea096e9714b083cca5cda8b89706ef9e35b](https://github.com/cockroachdb/cockroach/commits/1d4feea096e9714b083cca5cda8b89706ef9e35b):
Fatal error:
```
panic: test timed out after 14m55s
```
Stack:
```
goroutine 293683 [running]:
testing.(*M).startAlarm.func1()
GOROOT/src/testing/testing.go:2036 +0x88
created by time.goFunc
GOROOT/src/time/sleep.go:176 +0x38
```
<details><summary>Log preceding fatal error</summary>
<p>
```
=== RUN TestUpgradeSchemaChangerElements
test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/3538dab3e8bcdb43d30e6320ed019d4d/logTestUpgradeSchemaChangerElements1322792266
test_log_scope.go:79: use -show-logs to present logs inline
=== RUN TestUpgradeSchemaChangerElements/running_schema_change_that_will_have_a_deprecated_waitForSchemaChangerElementMigration_element
```
</p>
</details>
<details><summary>Help</summary>
<p>
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
</p>
</details>
/cc @cockroachdb/sql-schema
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestUpgradeSchemaChangerElements.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-25059
|
1.0
|
upgrade/upgrades: TestUpgradeSchemaChangerElements failed - upgrade/upgrades.TestUpgradeSchemaChangerElements [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/8940378?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/8940378?buildTab=artifacts#/) on master @ [1d4feea096e9714b083cca5cda8b89706ef9e35b](https://github.com/cockroachdb/cockroach/commits/1d4feea096e9714b083cca5cda8b89706ef9e35b):
Fatal error:
```
panic: test timed out after 14m55s
```
Stack:
```
goroutine 293683 [running]:
testing.(*M).startAlarm.func1()
GOROOT/src/testing/testing.go:2036 +0x88
created by time.goFunc
GOROOT/src/time/sleep.go:176 +0x38
```
<details><summary>Log preceding fatal error</summary>
<p>
```
=== RUN TestUpgradeSchemaChangerElements
test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/3538dab3e8bcdb43d30e6320ed019d4d/logTestUpgradeSchemaChangerElements1322792266
test_log_scope.go:79: use -show-logs to present logs inline
=== RUN TestUpgradeSchemaChangerElements/running_schema_change_that_will_have_a_deprecated_waitForSchemaChangerElementMigration_element
```
</p>
</details>
<details><summary>Help</summary>
<p>
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
</p>
</details>
/cc @cockroachdb/sql-schema
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestUpgradeSchemaChangerElements.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-25059
|
test
|
upgrade upgrades testupgradeschemachangerelements failed upgrade upgrades testupgradeschemachangerelements with on master fatal error panic test timed out after stack goroutine testing m startalarm goroot src testing testing go created by time gofunc goroot src time sleep go log preceding fatal error run testupgradeschemachangerelements test log scope go test logs captured to artifacts tmp tmp test log scope go use show logs to present logs inline run testupgradeschemachangerelements running schema change that will have a deprecated waitforschemachangerelementmigration element help see also cc cockroachdb sql schema jira issue crdb
| 1
|
310,268
| 26,708,651,910
|
IssuesEvent
|
2023-01-27 20:48:29
|
onmax/issue-form-parser
|
https://api.github.com/repos/onmax/issue-form-parser
|
closed
|
Issue form template
|
test-action
|
### Name
Max
### Lastname
G
### How do you know about us?
Just texting!
### Languages
Spanish, English, German
|
1.0
|
Issue form template - ### Name
Max
### Lastname
G
### How do you know about us?
Just texting!
### Languages
Spanish, English, German
|
test
|
issue form template name max lastname g how do you know about us just texting languages spanish english german
| 1
|
65,214
| 14,708,533,562
|
IssuesEvent
|
2021-01-04 23:57:53
|
mauriciolauffer/NodeGoat
|
https://api.github.com/repos/mauriciolauffer/NodeGoat
|
opened
|
CVE-2020-7788 (High) detected in ini-1.3.5.tgz, ini-1.3.4.tgz
|
security vulnerability
|
## CVE-2020-7788 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>ini-1.3.5.tgz</b>, <b>ini-1.3.4.tgz</b></p></summary>
<p>
<details><summary><b>ini-1.3.5.tgz</b></p></summary>
<p>An ini encoder/decoder for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/ini/-/ini-1.3.5.tgz">https://registry.npmjs.org/ini/-/ini-1.3.5.tgz</a></p>
<p>Path to dependency file: NodeGoat/package.json</p>
<p>Path to vulnerable library: NodeGoat/node_modules/ini/package.json</p>
<p>
Dependency Hierarchy:
- grunt-env-1.0.1.tgz (Root Library)
- :x: **ini-1.3.5.tgz** (Vulnerable Library)
</details>
<details><summary><b>ini-1.3.4.tgz</b></p></summary>
<p>An ini encoder/decoder for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/ini/-/ini-1.3.4.tgz">https://registry.npmjs.org/ini/-/ini-1.3.4.tgz</a></p>
<p>Path to dependency file: NodeGoat/package.json</p>
<p>Path to vulnerable library: NodeGoat/node_modules/npm/node_modules/ini/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- :x: **ini-1.3.4.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/mauriciolauffer/NodeGoat/commit/7e4baae75a2e9024fd12261d8d99f91cc913a308">7e4baae75a2e9024fd12261d8d99f91cc913a308</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
This affects the package ini before 1.3.6. If an attacker submits a malicious INI file to an application that parses it with ini.parse, they will pollute the prototype on the application. This can be exploited further depending on the context.
<p>Publish Date: 2020-12-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7788>CVE-2020-7788</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7788">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7788</a></p>
<p>Release Date: 2020-12-11</p>
<p>Fix Resolution: v1.3.6</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2020-7788 (High) detected in ini-1.3.5.tgz, ini-1.3.4.tgz - ## CVE-2020-7788 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>ini-1.3.5.tgz</b>, <b>ini-1.3.4.tgz</b></p></summary>
<p>
<details><summary><b>ini-1.3.5.tgz</b></p></summary>
<p>An ini encoder/decoder for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/ini/-/ini-1.3.5.tgz">https://registry.npmjs.org/ini/-/ini-1.3.5.tgz</a></p>
<p>Path to dependency file: NodeGoat/package.json</p>
<p>Path to vulnerable library: NodeGoat/node_modules/ini/package.json</p>
<p>
Dependency Hierarchy:
- grunt-env-1.0.1.tgz (Root Library)
- :x: **ini-1.3.5.tgz** (Vulnerable Library)
</details>
<details><summary><b>ini-1.3.4.tgz</b></p></summary>
<p>An ini encoder/decoder for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/ini/-/ini-1.3.4.tgz">https://registry.npmjs.org/ini/-/ini-1.3.4.tgz</a></p>
<p>Path to dependency file: NodeGoat/package.json</p>
<p>Path to vulnerable library: NodeGoat/node_modules/npm/node_modules/ini/package.json</p>
<p>
Dependency Hierarchy:
- grunt-npm-install-0.3.1.tgz (Root Library)
- npm-3.10.10.tgz
- :x: **ini-1.3.4.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/mauriciolauffer/NodeGoat/commit/7e4baae75a2e9024fd12261d8d99f91cc913a308">7e4baae75a2e9024fd12261d8d99f91cc913a308</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
This affects the package ini before 1.3.6. If an attacker submits a malicious INI file to an application that parses it with ini.parse, they will pollute the prototype on the application. This can be exploited further depending on the context.
<p>Publish Date: 2020-12-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7788>CVE-2020-7788</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7788">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7788</a></p>
<p>Release Date: 2020-12-11</p>
<p>Fix Resolution: v1.3.6</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve high detected in ini tgz ini tgz cve high severity vulnerability vulnerable libraries ini tgz ini tgz ini tgz an ini encoder decoder for node library home page a href path to dependency file nodegoat package json path to vulnerable library nodegoat node modules ini package json dependency hierarchy grunt env tgz root library x ini tgz vulnerable library ini tgz an ini encoder decoder for node library home page a href path to dependency file nodegoat package json path to vulnerable library nodegoat node modules npm node modules ini package json dependency hierarchy grunt npm install tgz root library npm tgz x ini tgz vulnerable library found in head commit a href found in base branch master vulnerability details this affects the package ini before if an attacker submits a malicious ini file to an application that parses it with ini parse they will pollute the prototype on the application this can be exploited further depending on the context publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
| 0
|
10,533
| 8,616,091,449
|
IssuesEvent
|
2018-11-19 22:42:10
|
regal/regal
|
https://api.github.com/repos/regal/regal
|
closed
|
Research bundling solution
|
infrastructure research
|
## Overview
Bundling JavaScript packages is an important problem for which there doesn't seem to be a single clear answer. Regarding the Regal Framework, there are two immediate and distinct ways bundling will be used:
1. To distribute the Regal Game Library itself so it can be used by game developers to make Regal games.
2. To package Regal games via a bundling service into a self-contained artifact that can be run on multiple platforms via a common API.
These two functions will be implemented separately, but the concepts behind implementing them should be largely the same. The plan for implementing function one (bundling the Regal Game Library) is described at the bottom of this issue, and function two (the game-bundling script) is included in issue #41.
## Background
A non-trivial amount of research went into deciding on a bundling solution. To preserve that effort, the notes I took are listed below. I don't have a ton of experience in bundling JS packages, so I'm basing much of my decision-making off of what the successful libraries are doing.
### Bundling Options
* [Webpack](https://webpack.js.org/)
* [Rollup](https://rollupjs.org/guide/en)
* [Parcel](https://parceljs.org/)
*Helpful link for comparing the three can be found [here](https://medium.com/js-imaginea/comparing-bundlers-webpack-rollup-parcel-f8f5dc609cfd)
### Distribution Structures used by Popular Libraries
* Angular
* Appears to use Webpack
* Has multiple packages that makeup components of the app
* Appears that there is a *test* and a normal (production) variant of the source
* Each package has separate directories for each platform
* `bundles`
* Contains bundled source files, including all comments
* These are the `umd` bundles
* For source types `<pkgname>` and `<pkgname>-testing`, there are the following files:
* `<srctype>.umd.js`
* `<srctype>.umd.js.map`
* `<srctype>.umd.min.js`
* `<srctype>.umd.min.js.map`
* `esm5`
* Has the following structure:
* `src`
* `testing`
* `core.js`
* `index.js`
* `public_api.js`
* Each file has a sourcemap string at the end of it
* It looks like this source maintains its original directory structure
* `esm2015`
* Similar to `esm5`, with an extra file `core.externs.js` that doesn't seem too relevant
* `fesm5`
* Bundled, but not minified. Contains the following files for `<core>` and `<testing>`:
* `<srctype>.js`
* `<srctype>.js.map`
* `fesm2015`
* Same structure as `fesm5`
* `src`
* Types for non-test source, seems to be following original directory structure
* `testing`
* Same as `src`, but for test environment
* Top level of the package directory also contains `core.d.ts`, `index.d.ts`, `testing.d.ts`, and a few other files that are all pretty intuitive given the structure seen already
* Each package has fields in the `package.json` that correspond to each build platform (`es2015`, `esm2015`, `esm5`, etc.)
* See explanation [here](https://github.com/angular/angular/issues/21260).
* Apparently these are used by webpack and the cli
* Notably, `main` points to `./bundles/core.umd.js` and `module` points to `./fesm5/core.js`.
* Redux
* Uses rollup
* Has the following chunk in `package.json` (annotated by a [blog post](https://babeljs.io/blog/2018/06/26/on-consuming-and-publishing-es2015+-packages) on babel):
```
// redux package.json
{
...
"main": "lib/redux.js", // ES5 + Common JS
"module": "es/redux.js", // ES5 + JS Modules
}
```
* Looking at the [rollup file](https://github.com/reduxjs/redux/blob/master/rollup.config.js), they also export:
* A compressed `es`-format file to `es/redux.mjs` with the comment "ES for Browsers"
* A bundled `umd` file (with `process.env.NODE_ENV` replaced with `development`) to `dist/redux.js` and the comment "UMD Development"
* A bundled `umd` file like above except for `production` exported to `dist/redux.min.js`
* The `package.json` file also includes `"unpkg": "dist/redux.js"`. Unpkg is a CDN.
* Has an `index.d.ts` file, but it looks like this was made manually
* React
* Uses some form of rollup
* Build directory structure (all of the following files are bundled, and some minified):
* `cjs`
* `react.development.js`
* `react.production.min.js`
* `umd`
* `react.development.js`
* `react.production.min.js`
* `react.profiling.min.js`
* `package.json` only has `main`, which points to `index.js` (which itself points to the `cjs` directory)
* Rollup
* Has `dist` with the following files:
* `rollup.browser.js` - looks like minified UMD
* `rollup.d.ts`
* `rollup.es.js` - bundled but not minified
* `rollup.js`- CJS bundled but not minified
* `package.json` has the following properties:
* `"main": "dist/rollup.js"`
* `"module": "dist/rollup.es.js"`
* `"jsnext:main": "dist/rollup.es.js"`
* `rollup.config.js` also has a command for generating `dist/rollup.browser.mjs` in `es` instead of `umd`.
* Vue
* Uses Rollup
* Exports to `umd`, `cjs`, and `esm`. [See explanation here.](https://github.com/vuejs/vue/tree/dev/dist)
### Output Formats
* `umd`
* `cjs`
* `esm`/`mjs`
* Rollup's justification for using `esm` in conjunction with `pkg.module` can be found [here](https://github.com/rollup/rollup/wiki/pkg.module).
* `amd`
### Useful Links
https://webpack.js.org/guides/typescript/
https://webpack.js.org/guides/author-libraries/
https://github.com/rollup/rollup-plugin-typescript
https://rollupjs.org/guide/en#faqs
## Description
**Requirement 1. Distribution Structure**
Based on the research above, it seems the optimal way to distribute the Regal Game Library is in the following structure (note that all of these files will be inside one `dist` folder):
* `regal.umd.min.js`: Bundled and minified `umd` format to run in the browser.<sup>1</sup>
* `regal.cjs.js`: Bundled CommonJS format to use with older module loaders.
* `regal.esm.js`: Bundled ES format to use with newer module loaders (especially desired by Rollup).<sup>2</sup>
* `types`: Directory containing all `*.d.ts` files, in their original project structure.<sup>3</sup>
<sup>1</sup>*Note that `regal-bundler` (#41) will not be able to bundle projects that use Regal as a `umd` dependency, but this format is included to allow maximum portability of the library.*
<sup>2</sup>*While generating an experimental `.mjs` file was considered, that doesn't seem to be a priority at this point. Once the format becomes more standard, it will be easy to add-on in the future.*
<sup>3</sup>*At the moment, there doesn't seem to be a way to bundle declaration files intuitively.*
**Requirement 2. Automatic Builds**
The distribution directory should be generated simply by running `npm run build`.
**Requirement 3. Comment Management**
This isn't a strict requirement, but ideally the file-level comments from each of the source files will be removed (as they have a lot of repeated information), and a single comment with a description of the library, copyright information, and the license will be placed on the top of the bundle.
### Bundler Choice
Based on everything above, I'm deciding to go with Rollup as the bundling tool for the Regal Game Library. If circumstances change in the future, other options may be reevaluated.
|
1.0
|
Research bundling solution - ## Overview
Bundling JavaScript packages is an important problem for which there doesn't seem to be a single clear answer. Regarding the Regal Framework, there are two immediate and distinct ways bundling will be used:
1. To distribute the Regal Game Library itself so it can be used by game developers to make Regal games.
2. To package Regal games via a bundling service into a self-contained artifact that can be run on multiple platforms via a common API.
These two functions will be implemented separately, but the concepts behind implementing them should be largely the same. The plan for implementing function one (bundling the Regal Game Library) is described at the bottom of this issue, and function two (the game-bundling script) is included in issue #41.
## Background
A non-trivial amount of research went into deciding on a bundling solution. To preserve that effort, the notes I took are listed below. I don't have a ton of experience in bundling JS packages, so I'm basing much of my decision-making off of what the successful libraries are doing.
### Bundling Options
* [Webpack](https://webpack.js.org/)
* [Rollup](https://rollupjs.org/guide/en)
* [Parcel](https://parceljs.org/)
*Helpful link for comparing the three can be found [here](https://medium.com/js-imaginea/comparing-bundlers-webpack-rollup-parcel-f8f5dc609cfd)
### Distribution Structures used by Popular Libraries
* Angular
* Appears to use Webpack
* Has multiple packages that makeup components of the app
* Appears that there is a *test* and a normal (production) variant of the source
* Each package has separate directories for each platform
* `bundles`
* Contains bundled source files, including all comments
* These are the `umd` bundles
* For source types `<pkgname>` and `<pkgname>-testing`, there are the following files:
* `<srctype>.umd.js`
* `<srctype>.umd.js.map`
* `<srctype>.umd.min.js`
* `<srctype>.umd.min.js.map`
* `esm5`
* Has the following structure:
* `src`
* `testing`
* `core.js`
* `index.js`
* `public_api.js`
* Each file has a sourcemap string at the end of it
* It looks like this source maintains its original directory structure
* `esm2015`
* Similar to `esm5`, with an extra file `core.externs.js` that doesn't seem too relevant
* `fesm5`
* Bundled, but not minified. Contains the following files for `<core>` and `<testing>`:
* `<srctype>.js`
* `<srctype>.js.map`
* `fesm2015`
* Same structure as `fesm5`
* `src`
* Types for non-test source, seems to be following original directory structure
* `testing`
* Same as `src`, but for test environment
* Top level of the package directory also contains `core.d.ts`, `index.d.ts`, `testing.d.ts`, and a few other files that are all pretty intuitive given the structure seen already
* Each package has fields in the `package.json` that correspond to each build platform (`es2015`, `esm2015`, `esm5`, etc.)
* See explanation [here](https://github.com/angular/angular/issues/21260).
* Apparently these are used by webpack and the cli
* Notably, `main` points to `./bundles/core.umd.js` and `module` points to `./fesm5/core.js`.
* Redux
* Uses rollup
* Has the following chunk in `package.json` (annotated by a [blog post](https://babeljs.io/blog/2018/06/26/on-consuming-and-publishing-es2015+-packages) on babel):
```
// redux package.json
{
...
"main": "lib/redux.js", // ES5 + Common JS
"module": "es/redux.js", // ES5 + JS Modules
}
```
* Looking at the [rollup file](https://github.com/reduxjs/redux/blob/master/rollup.config.js), they also export:
* A compressed `es`-format file to `es/redux.mjs` with the comment "ES for Browsers"
* A bundled `umd` file (with `process.env.NODE_ENV` replaced with `development`) to `dist/redux.js` and the comment "UMD Development"
* A bundled `umd` file like above except for `production` exported to `dist/redux.min.js`
* The `package.json` file also includes `"unpkg": "dist/redux.js"`. Unpkg is a CDN.
* Has an `index.d.ts` file, but it looks like this was made manually
* React
* Uses some form of rollup
* Build directory structure (all of the following files are bundled, and some minified):
* `cjs`
* `react.development.js`
* `react.production.min.js`
* `umd`
* `react.development.js`
* `react.production.min.js`
* `react.profiling.min.js`
* `package.json` only has `main`, which points to `index.js` (which itself points to the `cjs` directory)
* Rollup
* Has `dist` with the following files:
* `rollup.browser.js` - looks like minified UMD
* `rollup.d.ts`
* `rollup.es.js` - bundled but not minified
* `rollup.js`- CJS bundled but not minified
* `package.json` has the following properties:
* `"main": "dist/rollup.js"`
* `"module": "dist/rollup.es.js"`
* `"jsnext:main": "dist/rollup.es.js"`
* `rollup.config.js` also has a command for generating `dist/rollup.browser.mjs` in `es` instead of `umd`.
* Vue
* Uses Rollup
* Exports to `umd`, `cjs`, and `esm`. [See explanation here.](https://github.com/vuejs/vue/tree/dev/dist)
### Output Formats
* `umd`
* `cjs`
* `esm`/`mjs`
* Rollup's justification for using `esm` in conjunction with `pkg.module` can be found [here](https://github.com/rollup/rollup/wiki/pkg.module).
* `amd`
### Useful Links
https://webpack.js.org/guides/typescript/
https://webpack.js.org/guides/author-libraries/
https://github.com/rollup/rollup-plugin-typescript
https://rollupjs.org/guide/en#faqs
## Description
**Requirement 1. Distribution Structure**
Based on the research above, it seems the optimal way to distribute the Regal Game Library is in the following structure (note that all of these files will be inside one `dist` folder):
* `regal.umd.min.js`: Bundled and minified `umd` format to run in the browser.<sup>1</sup>
* `regal.cjs.js`: Bundled CommonJS format to use with older module loaders.
* `regal.esm.js`: Bundled ES format to use with newer module loaders (especially desired by Rollup).<sup>2</sup>
* `types`: Directory containing all `*.d.ts` files, in their original project structure.<sup>3</sup>
<sup>1</sup>*Note that `regal-bundler` (#41) will not be able to bundle projects that use Regal as a `umd` dependency, but this format is included to allow maximum portability of the library.*
<sup>2</sup>*While generating an experimental `.mjs` file was considered, that doesn't seem to be a priority at this point. Once the format becomes more standard, it will be easy to add-on in the future.*
<sup>3</sup>*At the moment, there doesn't seem to be a way to bundle declaration files intuitively.*
**Requirement 2. Automatic Builds**
The distribution directory should be generated simply by running `npm run build`.
**Requirement 3. Comment Management**
This isn't a strict requirement, but ideally the file-level comments from each of the source files will be removed (as they have a lot of repeated information), and a single comment with a description of the library, copyright information, and the license will be placed on the top of the bundle.
### Bundler Choice
Based on everything above, I'm deciding to go with Rollup as the bundling tool for the Regal Game Library. If circumstances change in the future, other options may be reevaluated.
|
non_test
|
research bundling solution overview bundling javascript packages is an important problem for which there doesn t seem to be a single clear answer regarding the regal framework there are two immediate and distinct ways bundling will be used to distribute the regal game library itself so it can be used by game developers to make regal games to package regal games via a bundling service into a self contained artifact that can be run on multiple platforms via a common api these two functions will be implemented separately but the concepts behind implementing them should be largely the same the plan for implementing function one bundling the regal game library is described at the bottom of this issue and function two the game bundling script is included in issue background a non trivial amount of research went into deciding on a bundling solution to preserve that effort the notes i took are listed below i don t have a ton of experience in bundling js packages so i m basing much of my decision making off of what the successful libraries are doing bundling options helpful link for comparing the three can be found distribution structures used by popular libraries angular appears to use webpack has multiple packages that makeup components of the app appears that there is a test and a normal production variant of the source each package has separate directories for each platform bundles contains bundled source files including all comments these are the umd bundles for source types and testing there are the following files umd js umd js map umd min js umd min js map has the following structure src testing core js index js public api js each file has a sourcemap string at the end of it it looks like this source maintains its original directory structure similar to with an extra file core externs js that doesn t seem too relevant bundled but not minified contains the following files for and js js map same structure as src types for non test source seems to be following original directory structure testing same as src but for test environment top level of the package directory also contains core d ts index d ts testing d ts and a few other files that are all pretty intuitive given the structure seen already each package has fields in the package json that correspond to each build platform etc see explanation apparently these are used by webpack and the cli notably main points to bundles core umd js and module points to core js redux uses rollup has the following chunk in package json annotated by a on babel redux package json main lib redux js common js module es redux js js modules looking at the they also export a compressed es format file to es redux mjs with the comment es for browsers a bundled umd file with process env node env replaced with development to dist redux js and the comment umd development a bundled umd file like above except for production exported to dist redux min js the package json file also includes unpkg dist redux js unpkg is a cdn has an index d ts file but it looks like this was made manually react uses some form of rollup build directory structure all of the following files are bundled and some minified cjs react development js react production min js umd react development js react production min js react profiling min js package json only has main which points to index js which itself points to the cjs directory rollup has dist with the following files rollup browser js looks like minified umd rollup d ts rollup es js bundled but not minified rollup js cjs bundled but not minified package json has the following properties main dist rollup js module dist rollup es js jsnext main dist rollup es js rollup config js also has a command for generating dist rollup browser mjs in es instead of umd vue uses rollup exports to umd cjs and esm output formats umd cjs esm mjs rollup s justification for using esm in conjunction with pkg module can be found amd useful links description requirement distribution structure based on the research above it seems the optimal way to distribute the regal game library is in the following structure note that all of these files will be inside one dist folder regal umd min js bundled and minified umd format to run in the browser regal cjs js bundled commonjs format to use with older module loaders regal esm js bundled es format to use with newer module loaders especially desired by rollup types directory containing all d ts files in their original project structure note that regal bundler will not be able to bundle projects that use regal as a umd dependency but this format is included to allow maximum portability of the library while generating an experimental mjs file was considered that doesn t seem to be a priority at this point once the format becomes more standard it will be easy to add on in the future at the moment there doesn t seem to be a way to bundle declaration files intuitively requirement automatic builds the distribution directory should be generated simply by running npm run build requirement comment management this isn t a strict requirement but ideally the file level comments from each of the source files will be removed as they have a lot of repeated information and a single comment with a description of the library copyright information and the license will be placed on the top of the bundle bundler choice based on everything above i m deciding to go with rollup as the bundling tool for the regal game library if circumstances change in the future other options may be reevaluated
| 0
|
412,124
| 12,035,554,202
|
IssuesEvent
|
2020-04-13 18:05:57
|
MaelSemler/mini-cap
|
https://api.github.com/repos/MaelSemler/mini-cap
|
closed
|
DEV-13 Move Compass To a Different Place
|
Priority 3
|
**Description**
As part of maps, there exists a compass icon that reorients the view to North when pressed.
**Acceptance Criteria**
- [ ] Removed Google's built-in compass icon
- [ ] Instantiate a new icon
- [ ] Icon should reorient view to the North when clicked
|
1.0
|
DEV-13 Move Compass To a Different Place - **Description**
As part of maps, there exists a compass icon that reorients the view to North when pressed.
**Acceptance Criteria**
- [ ] Removed Google's built-in compass icon
- [ ] Instantiate a new icon
- [ ] Icon should reorient view to the North when clicked
|
non_test
|
dev move compass to a different place description as part of maps there exists a compass icon that reorients the view to north when pressed acceptance criteria removed google s built in compass icon instantiate a new icon icon should reorient view to the north when clicked
| 0
|
67,983
| 21,391,538,343
|
IssuesEvent
|
2022-04-21 07:38:39
|
matrix-org/matrix-synapse-ldap3
|
https://api.github.com/repos/matrix-org/matrix-synapse-ldap3
|
closed
|
In Synapse 1.57.0 Docker image: module 'ldap_auth_provider' has no attribute 'LdapAuthProviderModule'
|
T-defect
|
**Describe the bug**
Using module ldap_auth_provider.LdapAuthProviderModule (as suggested by the README) in a Docker installation of Matrix Synapse using Docker image v1.57.0 causes an error:
```
AttributeError: module 'ldap_auth_provider' has no attribute 'LdapAuthProviderModule'
```
This error did not show up on Docker image v1.56.0 and earlier, but started to show up in v1.57.0. Downgrading to v1.56.0 fixes the issue.
**To Reproduce**
Steps to reproduce the behavior:
1. Use module: "ldap_auth_provider.LdapAuthProviderModule" in your Synapse homeserver
2. Run Synapse
**Expected behavior**
Synapse should run
**Synapse Installed on:**
- OS: Using the Synapse Docker image
- Version: v1.57.0
**Additional context**
Full error:
```
Traceback (most recent call last):
File "/usr/local/lib/python3.9/runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/local/lib/python3.9/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/usr/local/lib/python3.9/site-packages/synapse/app/homeserver.py", line 460, in <module>
main()
File "/usr/local/lib/python3.9/site-packages/synapse/app/homeserver.py", line 450, in main
hs = setup(sys.argv[1:])
File "/usr/local/lib/python3.9/site-packages/synapse/app/homeserver.py", line 326, in setup
config = HomeServerConfig.load_or_generate_config(
File "/usr/local/lib/python3.9/site-packages/synapse/config/_base.py", line 697, in load_or_generate_config
obj.parse_config_dict(
File "/usr/local/lib/python3.9/site-packages/synapse/config/_base.py", line 718, in parse_config_dict
self.invoke_all(
File "/usr/local/lib/python3.9/site-packages/synapse/config/_base.py", line 347, in invoke_all
res[config_class.section] = getattr(config, func_name)(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/synapse/config/modules.py", line 33, in read_config
self.loaded_modules.append(load_module(module, config_path))
File "/usr/local/lib/python3.9/site-packages/synapse/util/module_loader.py", line 50, in load_module
provider_class = getattr(module, clz)
AttributeError: module 'ldap_auth_provider' has no attribute 'LdapAuthProviderModule'
```
|
1.0
|
In Synapse 1.57.0 Docker image: module 'ldap_auth_provider' has no attribute 'LdapAuthProviderModule' - **Describe the bug**
Using module ldap_auth_provider.LdapAuthProviderModule (as suggested by the README) in a Docker installation of Matrix Synapse using Docker image v1.57.0 causes an error:
```
AttributeError: module 'ldap_auth_provider' has no attribute 'LdapAuthProviderModule'
```
This error did not show up on Docker image v1.56.0 and earlier, but started to show up in v1.57.0. Downgrading to v1.56.0 fixes the issue.
**To Reproduce**
Steps to reproduce the behavior:
1. Use module: "ldap_auth_provider.LdapAuthProviderModule" in your Synapse homeserver
2. Run Synapse
**Expected behavior**
Synapse should run
**Synapse Installed on:**
- OS: Using the Synapse Docker image
- Version: v1.57.0
**Additional context**
Full error:
```
Traceback (most recent call last):
File "/usr/local/lib/python3.9/runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/local/lib/python3.9/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/usr/local/lib/python3.9/site-packages/synapse/app/homeserver.py", line 460, in <module>
main()
File "/usr/local/lib/python3.9/site-packages/synapse/app/homeserver.py", line 450, in main
hs = setup(sys.argv[1:])
File "/usr/local/lib/python3.9/site-packages/synapse/app/homeserver.py", line 326, in setup
config = HomeServerConfig.load_or_generate_config(
File "/usr/local/lib/python3.9/site-packages/synapse/config/_base.py", line 697, in load_or_generate_config
obj.parse_config_dict(
File "/usr/local/lib/python3.9/site-packages/synapse/config/_base.py", line 718, in parse_config_dict
self.invoke_all(
File "/usr/local/lib/python3.9/site-packages/synapse/config/_base.py", line 347, in invoke_all
res[config_class.section] = getattr(config, func_name)(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/synapse/config/modules.py", line 33, in read_config
self.loaded_modules.append(load_module(module, config_path))
File "/usr/local/lib/python3.9/site-packages/synapse/util/module_loader.py", line 50, in load_module
provider_class = getattr(module, clz)
AttributeError: module 'ldap_auth_provider' has no attribute 'LdapAuthProviderModule'
```
|
non_test
|
in synapse docker image module ldap auth provider has no attribute ldapauthprovidermodule describe the bug using module ldap auth provider ldapauthprovidermodule as suggested by the readme in a docker installation of matrix synapse using docker image causes an error attributeerror module ldap auth provider has no attribute ldapauthprovidermodule this error did not show up on docker image and earlier but started to show up in downgrading to fixes the issue to reproduce steps to reproduce the behavior use module ldap auth provider ldapauthprovidermodule in your synapse homeserver run synapse expected behavior synapse should run synapse installed on os using the synapse docker image version additional context full error traceback most recent call last file usr local lib runpy py line in run module as main return run code code main globals none file usr local lib runpy py line in run code exec code run globals file usr local lib site packages synapse app homeserver py line in main file usr local lib site packages synapse app homeserver py line in main hs setup sys argv file usr local lib site packages synapse app homeserver py line in setup config homeserverconfig load or generate config file usr local lib site packages synapse config base py line in load or generate config obj parse config dict file usr local lib site packages synapse config base py line in parse config dict self invoke all file usr local lib site packages synapse config base py line in invoke all res getattr config func name args kwargs file usr local lib site packages synapse config modules py line in read config self loaded modules append load module module config path file usr local lib site packages synapse util module loader py line in load module provider class getattr module clz attributeerror module ldap auth provider has no attribute ldapauthprovidermodule
| 0
|
153,272
| 12,138,786,547
|
IssuesEvent
|
2020-04-23 17:48:50
|
aces/Loris
|
https://api.github.com/repos/aces/Loris
|
closed
|
[Dashboard] Investigate discrepancies for total displayed for "Incomplete Forms" and "Violated Scans" in Dashboard
|
23.0.0-testing Bug
|
Please investigate discrepancies found in dashboard display for Incomplete Forms and MRI Violation.
Violated scans - Total displayed 10,828. Total in MRI Violated Scans module = 16,834, minus 5,953 for phantom scans, minus 32 for non-phantom DCC entries = 10,859. Unsure of where difference of 31 scans is coming from.
Migrated from: https://redmine.cbrain.mcgill.ca/issues/14106
|
1.0
|
[Dashboard] Investigate discrepancies for total displayed for "Incomplete Forms" and "Violated Scans" in Dashboard - Please investigate discrepancies found in dashboard display for Incomplete Forms and MRI Violation.
Violated scans - Total displayed 10,828. Total in MRI Violated Scans module = 16,834, minus 5,953 for phantom scans, minus 32 for non-phantom DCC entries = 10,859. Unsure of where difference of 31 scans is coming from.
Migrated from: https://redmine.cbrain.mcgill.ca/issues/14106
|
test
|
investigate discrepancies for total displayed for incomplete forms and violated scans in dashboard please investigate discrepancies found in dashboard display for incomplete forms and mri violation violated scans total displayed total in mri violated scans module minus for phantom scans minus for non phantom dcc entries unsure of where difference of scans is coming from migrated from
| 1
|
182,399
| 14,913,786,671
|
IssuesEvent
|
2021-01-22 14:36:12
|
BlackIQ/Hello-World
|
https://api.github.com/repos/BlackIQ/Hello-World
|
closed
|
Put profile picture of the user who added lang before its name
|
documentation
|
Hello ,
We have a script that add creator and link after lang . But how about put the picture before !?
Example :
- Assembly - [Assembly](/Assembly) - Added By <img src="https://avatars.githubusercontent.com/u/42321156?s=460&u=7003d9df79e8b8b1bf0f277308ba03a173491f94&v=4" width="20" height="20"> [Taha Farahani](https://github.com/tahacodes)
Thanks .
May the force be with you .
Amir .
|
1.0
|
Put profile picture of the user who added lang before its name - Hello ,
We have a script that add creator and link after lang . But how about put the picture before !?
Example :
- Assembly - [Assembly](/Assembly) - Added By <img src="https://avatars.githubusercontent.com/u/42321156?s=460&u=7003d9df79e8b8b1bf0f277308ba03a173491f94&v=4" width="20" height="20"> [Taha Farahani](https://github.com/tahacodes)
Thanks .
May the force be with you .
Amir .
|
non_test
|
put profile picture of the user who added lang before its name hello we have a script that add creator and link after lang but how about put the picture before example assembly assembly added by thanks may the force be with you amir
| 0
|
11,752
| 3,222,866,833
|
IssuesEvent
|
2015-10-09 05:44:21
|
imixs/imixs-workflow
|
https://api.github.com/repos/imixs/imixs-workflow
|
closed
|
WorkflowController - process did not remove action atribute
|
bug testing
|
because of new implementation of WorkflowService
workitem.removeItem("action");
did no longer work
need to be replaced with
workitem.replaceItemvalue("action","");
|
1.0
|
WorkflowController - process did not remove action atribute - because of new implementation of WorkflowService
workitem.removeItem("action");
did no longer work
need to be replaced with
workitem.replaceItemvalue("action","");
|
test
|
workflowcontroller process did not remove action atribute because of new implementation of workflowservice workitem removeitem action did no longer work need to be replaced with workitem replaceitemvalue action
| 1
|
271,593
| 23,616,671,976
|
IssuesEvent
|
2022-08-24 16:27:17
|
hzi-braunschweig/SORMAS-Project
|
https://api.github.com/repos/hzi-braunschweig/SORMAS-Project
|
closed
|
Investigate regression failures for German environment
|
testing task e2e-tests
|
On today's regression we found tests failing randomly due to wrongly set language for German environment.
Debug tests dependency and order by following Process ID from logs file and identify test or action which is changing the language.
|
2.0
|
Investigate regression failures for German environment - On today's regression we found tests failing randomly due to wrongly set language for German environment.
Debug tests dependency and order by following Process ID from logs file and identify test or action which is changing the language.
|
test
|
investigate regression failures for german environment on today s regression we found tests failing randomly due to wrongly set language for german environment debug tests dependency and order by following process id from logs file and identify test or action which is changing the language
| 1
|
304,796
| 26,334,892,843
|
IssuesEvent
|
2023-01-10 13:39:44
|
EddieHubCommunity/LinkFree
|
https://api.github.com/repos/EddieHubCommunity/LinkFree
|
closed
|
New Testimonial for Eddie Jaoude
|
testimonial
|
### Name
eddiejaoude
### Title
God of OSS
### Description
As I like to say, Eddie is the god of open source and community. Eddie is the best and devrel and content creation 😍 Eddie's mentoring via their Twitter and Github is such a good addition to my life
|
1.0
|
New Testimonial for Eddie Jaoude - ### Name
eddiejaoude
### Title
God of OSS
### Description
As I like to say, Eddie is the god of open source and community. Eddie is the best and devrel and content creation 😍 Eddie's mentoring via their Twitter and Github is such a good addition to my life
|
test
|
new testimonial for eddie jaoude name eddiejaoude title god of oss description as i like to say eddie is the god of open source and community eddie is the best and devrel and content creation 😍 eddie s mentoring via their twitter and github is such a good addition to my life
| 1
|
48,129
| 5,946,280,050
|
IssuesEvent
|
2017-05-26 02:41:06
|
kubernetes/kubernetes
|
https://api.github.com/repos/kubernetes/kubernetes
|
closed
|
ResourceUsageGatherer panics in scalability tests
|
priority/failing-test sig/scalability
|
Example:
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-scalability/2405
```
I0521 22:50:08.062] May 21 22:50:08.061: INFO: Closing worker for e2e-scalability-minion-group-hjmj
I0521 22:50:08.062] E0521 22:50:08.061857 6620 runtime.go:66] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
I0521 22:50:08.062] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:72
I0521 22:50:08.062] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:65
I0521 22:50:08.062] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:51
I0521 22:50:08.062] /usr/local/go_k8s_patched/src/runtime/asm_amd64.s:514
I0521 22:50:08.062] /usr/local/go_k8s_patched/src/runtime/panic.go:489
I0521 22:50:08.063] /usr/local/go_k8s_patched/src/runtime/panic.go:63
I0521 22:50:08.063] /usr/local/go_k8s_patched/src/runtime/signal_unix.go:290
I0521 22:50:08.063] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/kubelet_stats.go:373
I0521 22:50:08.063] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/kubelet_stats.go:397
I0521 22:50:08.063] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/resource_usage_gatherer.go:159
I0521 22:50:08.063] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/resource_usage_gatherer.go:182
I0521 22:50:08.063] /usr/local/go_k8s_patched/src/runtime/asm_amd64.s:2197
I0521 22:50:08.064] panic: runtime error: invalid memory address or nil pointer dereference [recovered]
I0521 22:50:08.064] panic: runtime error: invalid memory address or nil pointer dereference
I0521 22:50:08.064] [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x230c29a]
I0521 22:50:08.065]
I0521 22:50:08.065] goroutine 180 [running]:
I0521 22:50:08.065] k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0, 0x0, 0x0)
I0521 22:50:08.065] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:58 +0x126
I0521 22:50:08.065] panic(0x2f40340, 0x4f7c940)
I0521 22:50:08.066] /usr/local/go_k8s_patched/src/runtime/panic.go:489 +0x2cf
I0521 22:50:08.066] k8s.io/kubernetes/test/e2e/framework.getOneTimeResourceUsageOnNode.func1(0xc4248d4960, 0x2e, 0xc424711620, 0x348b8ce)
I0521 22:50:08.066] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/kubelet_stats.go:373 +0x2a
I0521 22:50:08.066] k8s.io/kubernetes/test/e2e/framework.getOneTimeResourceUsageOnNode(0x4fde720, 0xc4211e7680, 0xc4207a0e70, 0x21, 0x37e11d600, 0xc424753d58, 0xc420e97ed8, 0xc420a1f5c0, 0xc4226f8480)
I0521 22:50:08.066] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/kubelet_stats.go:397 +0x4d0
I0521 22:50:08.066] k8s.io/kubernetes/test/e2e/framework.(*resourceGatherWorker).singleProbe(0xc4211e93e8)
I0521 22:50:08.066] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/resource_usage_gatherer.go:159 +0x38c
I0521 22:50:08.066] k8s.io/kubernetes/test/e2e/framework.(*resourceGatherWorker).gather(0xc4211e93e8, 0x6c706bafd)
I0521 22:50:08.066] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/resource_usage_gatherer.go:182 +0x2b4
I0521 22:50:08.067] created by k8s.io/kubernetes/test/e2e/framework.(*containerResourceGatherer).getKubeSystemContainersResourceUsage
I0521 22:50:08.067] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/resource_usage_gatherer.go:199 +0xa2
I0521 22:50:08.080]
```
@kubernetes/sig-scalability-bugs
|
1.0
|
ResourceUsageGatherer panics in scalability tests - Example:
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-scalability/2405
```
I0521 22:50:08.062] May 21 22:50:08.061: INFO: Closing worker for e2e-scalability-minion-group-hjmj
I0521 22:50:08.062] E0521 22:50:08.061857 6620 runtime.go:66] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
I0521 22:50:08.062] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:72
I0521 22:50:08.062] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:65
I0521 22:50:08.062] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:51
I0521 22:50:08.062] /usr/local/go_k8s_patched/src/runtime/asm_amd64.s:514
I0521 22:50:08.062] /usr/local/go_k8s_patched/src/runtime/panic.go:489
I0521 22:50:08.063] /usr/local/go_k8s_patched/src/runtime/panic.go:63
I0521 22:50:08.063] /usr/local/go_k8s_patched/src/runtime/signal_unix.go:290
I0521 22:50:08.063] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/kubelet_stats.go:373
I0521 22:50:08.063] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/kubelet_stats.go:397
I0521 22:50:08.063] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/resource_usage_gatherer.go:159
I0521 22:50:08.063] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/resource_usage_gatherer.go:182
I0521 22:50:08.063] /usr/local/go_k8s_patched/src/runtime/asm_amd64.s:2197
I0521 22:50:08.064] panic: runtime error: invalid memory address or nil pointer dereference [recovered]
I0521 22:50:08.064] panic: runtime error: invalid memory address or nil pointer dereference
I0521 22:50:08.064] [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x230c29a]
I0521 22:50:08.065]
I0521 22:50:08.065] goroutine 180 [running]:
I0521 22:50:08.065] k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0, 0x0, 0x0)
I0521 22:50:08.065] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:58 +0x126
I0521 22:50:08.065] panic(0x2f40340, 0x4f7c940)
I0521 22:50:08.066] /usr/local/go_k8s_patched/src/runtime/panic.go:489 +0x2cf
I0521 22:50:08.066] k8s.io/kubernetes/test/e2e/framework.getOneTimeResourceUsageOnNode.func1(0xc4248d4960, 0x2e, 0xc424711620, 0x348b8ce)
I0521 22:50:08.066] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/kubelet_stats.go:373 +0x2a
I0521 22:50:08.066] k8s.io/kubernetes/test/e2e/framework.getOneTimeResourceUsageOnNode(0x4fde720, 0xc4211e7680, 0xc4207a0e70, 0x21, 0x37e11d600, 0xc424753d58, 0xc420e97ed8, 0xc420a1f5c0, 0xc4226f8480)
I0521 22:50:08.066] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/kubelet_stats.go:397 +0x4d0
I0521 22:50:08.066] k8s.io/kubernetes/test/e2e/framework.(*resourceGatherWorker).singleProbe(0xc4211e93e8)
I0521 22:50:08.066] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/resource_usage_gatherer.go:159 +0x38c
I0521 22:50:08.066] k8s.io/kubernetes/test/e2e/framework.(*resourceGatherWorker).gather(0xc4211e93e8, 0x6c706bafd)
I0521 22:50:08.066] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/resource_usage_gatherer.go:182 +0x2b4
I0521 22:50:08.067] created by k8s.io/kubernetes/test/e2e/framework.(*containerResourceGatherer).getKubeSystemContainersResourceUsage
I0521 22:50:08.067] /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/resource_usage_gatherer.go:199 +0xa2
I0521 22:50:08.080]
```
@kubernetes/sig-scalability-bugs
|
test
|
resourceusagegatherer panics in scalability tests example may info closing worker for scalability minion group hjmj runtime go observed a panic invalid memory address or nil pointer dereference runtime error invalid memory address or nil pointer dereference go src io kubernetes output dockerized go src io kubernetes vendor io apimachinery pkg util runtime runtime go go src io kubernetes output dockerized go src io kubernetes vendor io apimachinery pkg util runtime runtime go go src io kubernetes output dockerized go src io kubernetes vendor io apimachinery pkg util runtime runtime go usr local go patched src runtime asm s usr local go patched src runtime panic go usr local go patched src runtime panic go usr local go patched src runtime signal unix go go src io kubernetes output dockerized go src io kubernetes test framework kubelet stats go go src io kubernetes output dockerized go src io kubernetes test framework kubelet stats go go src io kubernetes output dockerized go src io kubernetes test framework resource usage gatherer go go src io kubernetes output dockerized go src io kubernetes test framework resource usage gatherer go usr local go patched src runtime asm s panic runtime error invalid memory address or nil pointer dereference panic runtime error invalid memory address or nil pointer dereference goroutine io kubernetes vendor io apimachinery pkg util runtime handlecrash go src io kubernetes output dockerized go src io kubernetes vendor io apimachinery pkg util runtime runtime go panic usr local go patched src runtime panic go io kubernetes test framework getonetimeresourceusageonnode go src io kubernetes output dockerized go src io kubernetes test framework kubelet stats go io kubernetes test framework getonetimeresourceusageonnode go src io kubernetes output dockerized go src io kubernetes test framework kubelet stats go io kubernetes test framework resourcegatherworker singleprobe go src io kubernetes output dockerized go src io kubernetes test framework resource usage gatherer go io kubernetes test framework resourcegatherworker gather go src io kubernetes output dockerized go src io kubernetes test framework resource usage gatherer go created by io kubernetes test framework containerresourcegatherer getkubesystemcontainersresourceusage go src io kubernetes output dockerized go src io kubernetes test framework resource usage gatherer go kubernetes sig scalability bugs
| 1
|
135,986
| 11,032,055,612
|
IssuesEvent
|
2019-12-06 19:14:59
|
tektoncd/triggers
|
https://api.github.com/repos/tektoncd/triggers
|
opened
|
Split out Test_NewResources into smaller tests
|
area/testing
|
template/event_test.go contains a Test_NewResources function that tests both ResolveParams and ResolveResources. So, there is quite a bit of setup required to test each function.
We should separate it out into smaller tests that test each of those two exported functions separately
|
1.0
|
Split out Test_NewResources into smaller tests - template/event_test.go contains a Test_NewResources function that tests both ResolveParams and ResolveResources. So, there is quite a bit of setup required to test each function.
We should separate it out into smaller tests that test each of those two exported functions separately
|
test
|
split out test newresources into smaller tests template event test go contains a test newresources function that tests both resolveparams and resolveresources so there is quite a bit of setup required to test each function we should separate it out into smaller tests that test each of those two exported functions separately
| 1
|
18,568
| 13,044,096,193
|
IssuesEvent
|
2020-07-29 03:35:12
|
dueapp/Due-macOS
|
https://api.github.com/repos/dueapp/Due-macOS
|
closed
|
Show Preferences icon in side bar when Show icon in: Menu Bar Only
|
usability
|
https://twitter.com/tarrkid/status/1288108129989931009
Currently we show the settings cog when the app is docked to the menu bar. However, it appears that many have switched Show Icon In: to Menu Bar Only, without attaching Due to the menu bar icon.
This means they have no way to access menu bar Due > Preferences to switch it back.
I suggest we always show the settings cog whenever the user is in menu bar only mode, regardless of the docking status.
|
True
|
Show Preferences icon in side bar when Show icon in: Menu Bar Only - https://twitter.com/tarrkid/status/1288108129989931009
Currently we show the settings cog when the app is docked to the menu bar. However, it appears that many have switched Show Icon In: to Menu Bar Only, without attaching Due to the menu bar icon.
This means they have no way to access menu bar Due > Preferences to switch it back.
I suggest we always show the settings cog whenever the user is in menu bar only mode, regardless of the docking status.
|
non_test
|
show preferences icon in side bar when show icon in menu bar only currently we show the settings cog when the app is docked to the menu bar however it appears that many have switched show icon in to menu bar only without attaching due to the menu bar icon this means they have no way to access menu bar due preferences to switch it back i suggest we always show the settings cog whenever the user is in menu bar only mode regardless of the docking status
| 0
|
13,052
| 10,092,546,643
|
IssuesEvent
|
2019-07-26 16:59:17
|
aspnet/AspNetCore
|
https://api.github.com/repos/aspnet/AspNetCore
|
closed
|
Building the repo fails on a clean repo
|
area-infrastructure
|
Running the following fails for me on a clean repo
```
.\restore.cmd
.\build.cmd
```
```
Microsoft (R) Build Engine version 16.0.452+g01bae6224c for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.
Skipping project "C:\git\aspnet\AspNetCore\src\**\*.vcxproj" because it was not found.
C:\git\aspnet\AspNetCore\.dotnet\buildtools\korebuild\3.0.0-build-20190314.2\modules\projectbuild\module.targets(90,5):
error MSB3202: The project file "C:\git\aspnet\AspNetCore\src\**\*.vcxproj" was not found. [C:\git\aspnet\AspNetCore\.
dotnet\buildtools\korebuild\3.0.0-build-20190314.2\KoreBuild.proj]
Build FAILED.
C:\git\aspnet\AspNetCore\.dotnet\buildtools\korebuild\3.0.0-build-20190314.2\modules\projectbuild\module.targets(90,5):
error MSB3202: The project file "C:\git\aspnet\AspNetCore\src\**\*.vcxproj" was not found. [C:\git\aspnet\AspNetCore\.
dotnet\buildtools\korebuild\3.0.0-build-20190314.2\KoreBuild.proj]
0 Warning(s)
1 Error(s)
Time Elapsed 00:00:16.33
msbuild.exe failed with exit code: 1
(AspNetCore) C:\git\aspnet\AspNetCore [rynowak/routing-middleware]>
```
|
1.0
|
Building the repo fails on a clean repo - Running the following fails for me on a clean repo
```
.\restore.cmd
.\build.cmd
```
```
Microsoft (R) Build Engine version 16.0.452+g01bae6224c for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.
Skipping project "C:\git\aspnet\AspNetCore\src\**\*.vcxproj" because it was not found.
C:\git\aspnet\AspNetCore\.dotnet\buildtools\korebuild\3.0.0-build-20190314.2\modules\projectbuild\module.targets(90,5):
error MSB3202: The project file "C:\git\aspnet\AspNetCore\src\**\*.vcxproj" was not found. [C:\git\aspnet\AspNetCore\.
dotnet\buildtools\korebuild\3.0.0-build-20190314.2\KoreBuild.proj]
Build FAILED.
C:\git\aspnet\AspNetCore\.dotnet\buildtools\korebuild\3.0.0-build-20190314.2\modules\projectbuild\module.targets(90,5):
error MSB3202: The project file "C:\git\aspnet\AspNetCore\src\**\*.vcxproj" was not found. [C:\git\aspnet\AspNetCore\.
dotnet\buildtools\korebuild\3.0.0-build-20190314.2\KoreBuild.proj]
0 Warning(s)
1 Error(s)
Time Elapsed 00:00:16.33
msbuild.exe failed with exit code: 1
(AspNetCore) C:\git\aspnet\AspNetCore [rynowak/routing-middleware]>
```
|
non_test
|
building the repo fails on a clean repo running the following fails for me on a clean repo restore cmd build cmd microsoft r build engine version for net framework copyright c microsoft corporation all rights reserved skipping project c git aspnet aspnetcore src vcxproj because it was not found c git aspnet aspnetcore dotnet buildtools korebuild build modules projectbuild module targets error the project file c git aspnet aspnetcore src vcxproj was not found c git aspnet aspnetcore dotnet buildtools korebuild build korebuild proj build failed c git aspnet aspnetcore dotnet buildtools korebuild build modules projectbuild module targets error the project file c git aspnet aspnetcore src vcxproj was not found c git aspnet aspnetcore dotnet buildtools korebuild build korebuild proj warning s error s time elapsed msbuild exe failed with exit code aspnetcore c git aspnet aspnetcore
| 0
|
189,964
| 14,529,525,414
|
IssuesEvent
|
2020-12-14 17:56:14
|
GreyMatteOr/Crate
|
https://api.github.com/repos/GreyMatteOr/Crate
|
closed
|
TEST TEST TEST
|
back_end extension testing
|
Once MVP is finished and tested, test additional endpoints that weren't written by us
|
1.0
|
TEST TEST TEST - Once MVP is finished and tested, test additional endpoints that weren't written by us
|
test
|
test test test once mvp is finished and tested test additional endpoints that weren t written by us
| 1
|
785,779
| 27,624,904,452
|
IssuesEvent
|
2023-03-10 05:31:07
|
ballerina-platform/ballerina-lang
|
https://api.github.com/repos/ballerina-platform/ballerina-lang
|
closed
|
[Improvement]: Implement changes required for deprecating Ballerina packages
|
Type/Improvement Priority/High Area/ProjectAPI userCategory/Central
|
### Description
As discussed in https://github.com/ballerina-platform/ballerina-spec/issues/1127, we need to implement the following to support deprecating Ballerina packages.
- `bal pull` : print a warning when pulling a deprecated package
- `bal push` : print error when trying to push a package with a deprecated dependency.
- introduce `bal deprecate` command
### Describe your problem(s)
_No response_
### Describe your solution(s)
_No response_
### Related area
-> Compilation
### Related issue(s) (optional)
_No response_
### Suggested label(s) (optional)
_No response_
### Suggested assignee(s) (optional)
_No response_
|
1.0
|
[Improvement]: Implement changes required for deprecating Ballerina packages - ### Description
As discussed in https://github.com/ballerina-platform/ballerina-spec/issues/1127, we need to implement the following to support deprecating Ballerina packages.
- `bal pull` : print a warning when pulling a deprecated package
- `bal push` : print error when trying to push a package with a deprecated dependency.
- introduce `bal deprecate` command
### Describe your problem(s)
_No response_
### Describe your solution(s)
_No response_
### Related area
-> Compilation
### Related issue(s) (optional)
_No response_
### Suggested label(s) (optional)
_No response_
### Suggested assignee(s) (optional)
_No response_
|
non_test
|
implement changes required for deprecating ballerina packages description as discussed in we need to implement the following to support deprecating ballerina packages bal pull print a warning when pulling a deprecated package bal push print error when trying to push a package with a deprecated dependency introduce bal deprecate command describe your problem s no response describe your solution s no response related area compilation related issue s optional no response suggested label s optional no response suggested assignee s optional no response
| 0
|
216,520
| 16,768,309,811
|
IssuesEvent
|
2021-06-14 11:50:30
|
mennaelkashef/eShop
|
https://api.github.com/repos/mennaelkashef/eShop
|
opened
|
No description entered by the user.
|
DOES-NOT-CONTAIN-STRING Hello! RULE-GOT-APPLIED Rule-works-on-convert-to-bug instabug test
|
# :clipboard: Bug Details
>No description entered by the user.
key | value
--|--
Reported At | 2021-06-14 11:48:23 UTC
Email | imohamady@instabug.com
Categories | Report a bug, Cat 2
Tags | test, Hello!, RULE-GOT-APPLIED, DOES-NOT-CONTAIN-STRING, Rule-works-on-convert-to-bug, instabug
App Version | 1.0-kotlin (1)
Session Duration | 10
Device | Google AOSP on IA Emulator, OS Level 28
Display | 1080x2220 (xhdpi)
Location | Cairo, Egypt (en)
## :point_right: [View Full Bug Report on Instabug](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7942?utm_source=github&utm_medium=integrations) :point_left:
___
# :iphone: View Hierarchy
This bug was reported from **com.example.app.main.MainFragment**
Find its interactive view hierarchy with all its subviews here: :point_right: **[Check View Hierarchy](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7942?show-hierarchy-view=true&utm_source=github&utm_medium=integrations)** :point_left:
___
# :chart_with_downwards_trend: Session Profiler
Here is what the app was doing right before the bug was reported:
Key | Value
--|--
Used Memory | 56.5% - 0.82/1.46 GB
Used Storage | 9.9% - 0.58/5.81 GB
Connectivity | no_connection
Battery | 100% - unplugged
Orientation | portrait
Find all the changes that happened in the parameters mentioned above during the last 60 seconds before the bug was reported here: :point_right: **[View Full Session Profiler](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7942?show-session-profiler=true&utm_source=github&utm_medium=integrations)** :point_left:
___
# :bust_in_silhouette: User Info
### User Attributes
```
key_name -1394358796: key value bla bla bla la
key_name 1733924589: key value bla bla bla la
key_name -934011477: key value bla bla bla la
key_name -848543674: key value bla bla bla la
key_name -1286539345: key value bla bla bla la
```
___
# :mag_right: Logs
### User Steps
Here are the last 10 steps done by the user right before the bug was reported:
```
11:48:14 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was started.
11:48:14 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was resumed.
11:48:14 com.example.app.main.MainActivity was resumed.
11:48:15 com.example.app.splash.SplashActivity was stopped.
11:48:15 com.example.app.splash.SplashActivity was destroyed.
11:48:19 Tap in "Sdk version: 10..." of type "androidx.appcompat.widget.AppCompatTextView" in "com.example.app.main.MainActivity"
11:48:19 com.example.app.main.MainActivity was paused.
11:48:19 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was paused.
11:48:21 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
11:48:22 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
```
Find all the user steps done by the user throughout the session here: :point_right: **[View All User Steps](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7942?show-logs=user_steps&utm_source=github&utm_medium=integrations)** :point_left:
### Console Log
Here are the last 10 console logs logged right before the bug was reported:
```
11:48:25 D/IB-ActivityViewInspector( 5285): bug ! null,converting>json started
11:48:25 D/IB-ActivityViewInspector( 5285): bug ! null,converting>json ended
11:48:25 D/IB-ActivityViewInspector( 5285): bug ! null,set inspection state
11:48:25 D/IB-BaseReportingPresenter( 5285): receive a view hierarchy inspection action, action value: COMPLETED
11:48:25 D/IB-BaseReportingPresenter( 5285): receive a view hierarchy inspection action, action value: COMPLETED
11:48:25 D/EGL_emulation( 5285): eglMakeCurrent: 0xdb0acb60: ver 3 0 (tinfo 0xe2cdcc50)
11:48:25 D/IB-BaseReportingPresenter( 5285): checkUserEmailValid :imohamady@instabug.com
11:48:25 V/IB-PoolProvider( 5285): postTask
11:48:25 D/IB-ActionsOrchestrator( 5285): runAction
11:48:26 D/IB-AttachmentsUtility( 5285): encryptAttachments
```
Find all the logged console logs throughout the session here: :point_right: **[View All Console Log](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7942?show-logs=console_log&utm_source=github&utm_medium=integrations)** :point_left:
___
# :camera: Images
[](https://d38gnqwzxziyyy.cloudfront.net/attachments/bugs/15934827/60cfa0517e12de5bd3e2b22649fb3323_original/21330737/bug_1623671299835_.jpg?Expires=4779345029&Signature=B0nDki419GwWe52UpnaLPfKm8kS9HhksiJM7GMa6Kf59jDTgCKzbVRsxHPmjaxmx7rrNfkoz9AVEp4MYQSOeBKxdhdV3~SGk1Jsc~Y7LZGWixKlGakkakLN1AKdWopYX6P02uFnz2NdWi7ViSjvqresgDXVpdTa1yCSh45NX6A9yGnQEqvwyh5fqr1uSAgZ61h-88~eR53nhPW28udJzt7PXW2EKDjOdu-J7OH11O~cWXaREpApeutDg9K5PoMpdbiDazbgkR-ILeiFuuZ2hB6X6SKho87KVHKbifudGn6zAS5I5BTALlTIaUZ09tDx-AXPFpMrK6EngDwP~ctu2bg__&Key-Pair-Id=APKAIXAG65U6UUX7JAQQ)
___
# :warning: Looking for More Details?
1. **Network Log**: we are unable to capture your network requests automatically. If you are using HttpUrlConnection or Okhttp requests, [**check the details mentioned here**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations#section-network-logs).
2. **User Events**: start capturing custom User Events to send them along with each report. [**Find all the details in the docs**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations).
3. **Instabug Log**: start adding Instabug logs to see them right inside each report you receive. [**Find all the details in the docs**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations).
|
1.0
|
No description entered by the user. - # :clipboard: Bug Details
>No description entered by the user.
key | value
--|--
Reported At | 2021-06-14 11:48:23 UTC
Email | imohamady@instabug.com
Categories | Report a bug, Cat 2
Tags | test, Hello!, RULE-GOT-APPLIED, DOES-NOT-CONTAIN-STRING, Rule-works-on-convert-to-bug, instabug
App Version | 1.0-kotlin (1)
Session Duration | 10
Device | Google AOSP on IA Emulator, OS Level 28
Display | 1080x2220 (xhdpi)
Location | Cairo, Egypt (en)
## :point_right: [View Full Bug Report on Instabug](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7942?utm_source=github&utm_medium=integrations) :point_left:
___
# :iphone: View Hierarchy
This bug was reported from **com.example.app.main.MainFragment**
Find its interactive view hierarchy with all its subviews here: :point_right: **[Check View Hierarchy](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7942?show-hierarchy-view=true&utm_source=github&utm_medium=integrations)** :point_left:
___
# :chart_with_downwards_trend: Session Profiler
Here is what the app was doing right before the bug was reported:
Key | Value
--|--
Used Memory | 56.5% - 0.82/1.46 GB
Used Storage | 9.9% - 0.58/5.81 GB
Connectivity | no_connection
Battery | 100% - unplugged
Orientation | portrait
Find all the changes that happened in the parameters mentioned above during the last 60 seconds before the bug was reported here: :point_right: **[View Full Session Profiler](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7942?show-session-profiler=true&utm_source=github&utm_medium=integrations)** :point_left:
___
# :bust_in_silhouette: User Info
### User Attributes
```
key_name -1394358796: key value bla bla bla la
key_name 1733924589: key value bla bla bla la
key_name -934011477: key value bla bla bla la
key_name -848543674: key value bla bla bla la
key_name -1286539345: key value bla bla bla la
```
___
# :mag_right: Logs
### User Steps
Here are the last 10 steps done by the user right before the bug was reported:
```
11:48:14 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was started.
11:48:14 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was resumed.
11:48:14 com.example.app.main.MainActivity was resumed.
11:48:15 com.example.app.splash.SplashActivity was stopped.
11:48:15 com.example.app.splash.SplashActivity was destroyed.
11:48:19 Tap in "Sdk version: 10..." of type "androidx.appcompat.widget.AppCompatTextView" in "com.example.app.main.MainActivity"
11:48:19 com.example.app.main.MainActivity was paused.
11:48:19 In activity com.example.app.main.MainActivity: fragment com.example.app.main.MainFragment was paused.
11:48:21 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
11:48:22 Tap in "androidx.constraintlayout.widget.ConstraintLayout" in "com.example.app.main.MainActivity"
```
Find all the user steps done by the user throughout the session here: :point_right: **[View All User Steps](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7942?show-logs=user_steps&utm_source=github&utm_medium=integrations)** :point_left:
### Console Log
Here are the last 10 console logs logged right before the bug was reported:
```
11:48:25 D/IB-ActivityViewInspector( 5285): bug ! null,converting>json started
11:48:25 D/IB-ActivityViewInspector( 5285): bug ! null,converting>json ended
11:48:25 D/IB-ActivityViewInspector( 5285): bug ! null,set inspection state
11:48:25 D/IB-BaseReportingPresenter( 5285): receive a view hierarchy inspection action, action value: COMPLETED
11:48:25 D/IB-BaseReportingPresenter( 5285): receive a view hierarchy inspection action, action value: COMPLETED
11:48:25 D/EGL_emulation( 5285): eglMakeCurrent: 0xdb0acb60: ver 3 0 (tinfo 0xe2cdcc50)
11:48:25 D/IB-BaseReportingPresenter( 5285): checkUserEmailValid :imohamady@instabug.com
11:48:25 V/IB-PoolProvider( 5285): postTask
11:48:25 D/IB-ActionsOrchestrator( 5285): runAction
11:48:26 D/IB-AttachmentsUtility( 5285): encryptAttachments
```
Find all the logged console logs throughout the session here: :point_right: **[View All Console Log](https://dashboard.instabug.com/applications/android-sample/beta/bugs/7942?show-logs=console_log&utm_source=github&utm_medium=integrations)** :point_left:
___
# :camera: Images
[](https://d38gnqwzxziyyy.cloudfront.net/attachments/bugs/15934827/60cfa0517e12de5bd3e2b22649fb3323_original/21330737/bug_1623671299835_.jpg?Expires=4779345029&Signature=B0nDki419GwWe52UpnaLPfKm8kS9HhksiJM7GMa6Kf59jDTgCKzbVRsxHPmjaxmx7rrNfkoz9AVEp4MYQSOeBKxdhdV3~SGk1Jsc~Y7LZGWixKlGakkakLN1AKdWopYX6P02uFnz2NdWi7ViSjvqresgDXVpdTa1yCSh45NX6A9yGnQEqvwyh5fqr1uSAgZ61h-88~eR53nhPW28udJzt7PXW2EKDjOdu-J7OH11O~cWXaREpApeutDg9K5PoMpdbiDazbgkR-ILeiFuuZ2hB6X6SKho87KVHKbifudGn6zAS5I5BTALlTIaUZ09tDx-AXPFpMrK6EngDwP~ctu2bg__&Key-Pair-Id=APKAIXAG65U6UUX7JAQQ)
___
# :warning: Looking for More Details?
1. **Network Log**: we are unable to capture your network requests automatically. If you are using HttpUrlConnection or Okhttp requests, [**check the details mentioned here**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations#section-network-logs).
2. **User Events**: start capturing custom User Events to send them along with each report. [**Find all the details in the docs**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations).
3. **Instabug Log**: start adding Instabug logs to see them right inside each report you receive. [**Find all the details in the docs**](https://docs.instabug.com/docs/android-logging?utm_source=github&utm_medium=integrations).
|
test
|
no description entered by the user clipboard bug details no description entered by the user key value reported at utc email imohamady instabug com categories report a bug cat tags test hello rule got applied does not contain string rule works on convert to bug instabug app version kotlin session duration device google aosp on ia emulator os level display xhdpi location cairo egypt en point right point left iphone view hierarchy this bug was reported from com example app main mainfragment find its interactive view hierarchy with all its subviews here point right point left chart with downwards trend session profiler here is what the app was doing right before the bug was reported key value used memory gb used storage gb connectivity no connection battery unplugged orientation portrait find all the changes that happened in the parameters mentioned above during the last seconds before the bug was reported here point right point left bust in silhouette user info user attributes key name key value bla bla bla la key name key value bla bla bla la key name key value bla bla bla la key name key value bla bla bla la key name key value bla bla bla la mag right logs user steps here are the last steps done by the user right before the bug was reported in activity com example app main mainactivity fragment com example app main mainfragment was started in activity com example app main mainactivity fragment com example app main mainfragment was resumed com example app main mainactivity was resumed com example app splash splashactivity was stopped com example app splash splashactivity was destroyed tap in sdk version of type androidx appcompat widget appcompattextview in com example app main mainactivity com example app main mainactivity was paused in activity com example app main mainactivity fragment com example app main mainfragment was paused tap in androidx constraintlayout widget constraintlayout in com example app main mainactivity tap in androidx constraintlayout widget constraintlayout in com example app main mainactivity find all the user steps done by the user throughout the session here point right point left console log here are the last console logs logged right before the bug was reported d ib activityviewinspector bug null converting json started d ib activityviewinspector bug null converting json ended d ib activityviewinspector bug null set inspection state d ib basereportingpresenter receive a view hierarchy inspection action action value completed d ib basereportingpresenter receive a view hierarchy inspection action action value completed d egl emulation eglmakecurrent ver tinfo d ib basereportingpresenter checkuseremailvalid imohamady instabug com v ib poolprovider posttask d ib actionsorchestrator runaction d ib attachmentsutility encryptattachments find all the logged console logs throughout the session here point right point left camera images warning looking for more details network log we are unable to capture your network requests automatically if you are using httpurlconnection or okhttp requests user events start capturing custom user events to send them along with each report instabug log start adding instabug logs to see them right inside each report you receive
| 1
|
45,480
| 5,717,792,861
|
IssuesEvent
|
2017-04-19 18:03:33
|
omeka-s-modules/CSVImport
|
https://api.github.com/repos/omeka-s-modules/CSVImport
|
closed
|
Test #65 (and regression)
|
testing
|
Big thing here is #65. It also involved moving a lot around, and there have been other changes lately, so some regression checking that old CSV import files are still happy might be in order. Especially important is the combination of different media imports (html, youtube, oembed, etc), and multivalue imports for the new resource relations option.
Use develop branch of omeka-s, and branch resource-reference of CSVImport.
The Resource Reference option actually goes beyond the original request, including all Resources, not just Items. Thus, the IDs could refer to Items, Item Sets, or Media (or other Resources if something adds them, which I don't think we do yet). Thus, the possible interpretations of property values is a little wider open than the admin interface, which only has options for Item and Item Set.
The "Import as Omeka S Resource ID" option is new under the property selector.
|
1.0
|
Test #65 (and regression) - Big thing here is #65. It also involved moving a lot around, and there have been other changes lately, so some regression checking that old CSV import files are still happy might be in order. Especially important is the combination of different media imports (html, youtube, oembed, etc), and multivalue imports for the new resource relations option.
Use develop branch of omeka-s, and branch resource-reference of CSVImport.
The Resource Reference option actually goes beyond the original request, including all Resources, not just Items. Thus, the IDs could refer to Items, Item Sets, or Media (or other Resources if something adds them, which I don't think we do yet). Thus, the possible interpretations of property values is a little wider open than the admin interface, which only has options for Item and Item Set.
The "Import as Omeka S Resource ID" option is new under the property selector.
|
test
|
test and regression big thing here is it also involved moving a lot around and there have been other changes lately so some regression checking that old csv import files are still happy might be in order especially important is the combination of different media imports html youtube oembed etc and multivalue imports for the new resource relations option use develop branch of omeka s and branch resource reference of csvimport the resource reference option actually goes beyond the original request including all resources not just items thus the ids could refer to items item sets or media or other resources if something adds them which i don t think we do yet thus the possible interpretations of property values is a little wider open than the admin interface which only has options for item and item set the import as omeka s resource id option is new under the property selector
| 1
|
351,939
| 10,525,703,534
|
IssuesEvent
|
2019-09-30 15:33:42
|
forceworkbench/forceworkbench
|
https://api.github.com/repos/forceworkbench/forceworkbench
|
closed
|
Serializable Field Mappings
|
Component-Put Priority-Low Scheduled-Backlog enhancement imported
|
_Original author: banderso...@gmail.com (July 14, 2011 15:06:36)_
<b>1. Summary of the feature request:</b>
Ability to save mappings like DataLoader
<b>2. Typical scenerio where this feature would be used:</b>
Any insert, update, upsert scenario
<b>3. Reason current features do not meet needs:</b>
May have to repeat something many times and mapping each time is time consuming
<b>4. How soon would you like to see this feature implemented?</b>
Next API Release
<b>5. Would you like to contribute to the development of this feature?</b>
I would help
_Original issue: http://code.google.com/p/forceworkbench/issues/detail?id=480_
|
1.0
|
Serializable Field Mappings - _Original author: banderso...@gmail.com (July 14, 2011 15:06:36)_
<b>1. Summary of the feature request:</b>
Ability to save mappings like DataLoader
<b>2. Typical scenerio where this feature would be used:</b>
Any insert, update, upsert scenario
<b>3. Reason current features do not meet needs:</b>
May have to repeat something many times and mapping each time is time consuming
<b>4. How soon would you like to see this feature implemented?</b>
Next API Release
<b>5. Would you like to contribute to the development of this feature?</b>
I would help
_Original issue: http://code.google.com/p/forceworkbench/issues/detail?id=480_
|
non_test
|
serializable field mappings original author banderso gmail com july summary of the feature request ability to save mappings like dataloader typical scenerio where this feature would be used any insert update upsert scenario reason current features do not meet needs may have to repeat something many times and mapping each time is time consuming how soon would you like to see this feature implemented next api release would you like to contribute to the development of this feature i would help original issue
| 0
|
28,171
| 31,989,220,855
|
IssuesEvent
|
2023-09-21 03:38:04
|
DynamoRIO/drmemory
|
https://api.github.com/repos/DynamoRIO/drmemory
|
opened
|
DWARF5 is not supported by drsyms, resulting in no line numbers with gcc 11+
|
Usability
|
Building Dr. Memory on a system with gcc 12.2, the tests fail b/c they can't get line numbers:
```
Error #1: UNADDRESSABLE ACCESS beyond heap bounds: reading 0x00007f796fc01223-0x00007f796fc01224 1 byte(s)
# 0 main (0x00007f796fbfb33a <malloc+0x133a>)
??:0
```
It's because the test binary has DWARF5:
```
$ readelf --debug-dump=info tests/malloc | grep -A 2 'Compilation Unit @'
Compilation Unit @ offset 0:
Length: 0x78d (32-bit)
Version: 5
```
Dr. Memory uses DynamoRIO's drsyms library, and it uses elftoolchain, picked due to its BSD instead of GPL license. However, it is not kept up to date these days and lacks DWARF5 support: https://sourceforge.net/p/elftoolchain/tickets/611.
This is filed in the DynamoRIO tracker as DynamoRIO/dynamorio#5926.
Adding -gdwarf-4: the test works.
|
True
|
DWARF5 is not supported by drsyms, resulting in no line numbers with gcc 11+ - Building Dr. Memory on a system with gcc 12.2, the tests fail b/c they can't get line numbers:
```
Error #1: UNADDRESSABLE ACCESS beyond heap bounds: reading 0x00007f796fc01223-0x00007f796fc01224 1 byte(s)
# 0 main (0x00007f796fbfb33a <malloc+0x133a>)
??:0
```
It's because the test binary has DWARF5:
```
$ readelf --debug-dump=info tests/malloc | grep -A 2 'Compilation Unit @'
Compilation Unit @ offset 0:
Length: 0x78d (32-bit)
Version: 5
```
Dr. Memory uses DynamoRIO's drsyms library, and it uses elftoolchain, picked due to its BSD instead of GPL license. However, it is not kept up to date these days and lacks DWARF5 support: https://sourceforge.net/p/elftoolchain/tickets/611.
This is filed in the DynamoRIO tracker as DynamoRIO/dynamorio#5926.
Adding -gdwarf-4: the test works.
|
non_test
|
is not supported by drsyms resulting in no line numbers with gcc building dr memory on a system with gcc the tests fail b c they can t get line numbers error unaddressable access beyond heap bounds reading byte s main it s because the test binary has readelf debug dump info tests malloc grep a compilation unit compilation unit offset length bit version dr memory uses dynamorio s drsyms library and it uses elftoolchain picked due to its bsd instead of gpl license however it is not kept up to date these days and lacks support this is filed in the dynamorio tracker as dynamorio dynamorio adding gdwarf the test works
| 0
|
51,131
| 12,680,861,515
|
IssuesEvent
|
2020-06-19 14:25:47
|
Scirra/Construct-3-bugs
|
https://api.github.com/repos/Scirra/Construct-3-bugs
|
closed
|
Signed release apk Key password missing
|
Build Service
|
<!-- You must use this template or your issue will be closed without investigation. Please see the guidelines. -->
## Problem description
When exporting a signed release apk, in the newest stable version R204 you removed the "key password". Since that, all of my builds fail and it throws an error "wrong password..."
## Attach a .c3p
doesn't matter what project you use, it's just a signing error.
## Steps to reproduce
Open any project.
Go to Export -> signed release apk -> fill in your key (key password missing)
At the end of the build -> error (see error log below)
## Observed result
build error
## Expected result
normal build
## More details
**Affected browsers/platforms:** Android
**First affected release:** r204
## System details
<!-- If you see a crash report dialog, please copy and paste it to where it says "PASTE HERE" below. -->
<!-- Otherwise please go to Menu > About > Platform information and paste that information there instead. -->
<details><summary>View details</summary>
Error log:
Error: Failed to load signer "signer #1"
java.io.IOException: Failed to obtain key with alias "upload" from tmp/918f060a-d711-49c3-983c-1c234283ce7f. Wrong password?
at com.android.apksigner.ApkSignerTool$SignerParams.loadPrivateKeyAndCertsFromKeyStore(ApkSignerTool.java:690)
at com.android.apksigner.ApkSignerTool$SignerParams.loadPrivateKeyAndCerts(ApkSignerTool.java:555)
at com.android.apksigner.ApkSignerTool$SignerParams.access$200(ApkSignerTool.java:509)
at com.android.apksigner.ApkSignerTool.sign(ApkSignerTool.java:215)
at com.android.apksigner.ApkSignerTool.main(ApkSignerTool.java:89)
Caused by: java.security.UnrecoverableKeyException: Cannot recover key
at sun.security.provider.KeyProtector.recover(KeyProtector.java:315)
at sun.security.provider.JavaKeyStore.engineGetKey(JavaKeyStore.java:143)
at sun.security.provider.JavaKeyStore$JKS.engineGetKey(JavaKeyStore.java:57)
at sun.security.provider.KeyStoreDelegator.engineGetKey(KeyStoreDelegator.java:96)
at sun.security.provider.JavaKeyStore$DualFormatJKS.engineGetKey(JavaKeyStore.java:71)
at java.security.KeyStore.getKey(KeyStore.java:1023)
at com.android.apksigner.ApkSignerTool$SignerParams.loadPrivateKeyAndCertsFromKeyStore(ApkSignerTool.java:663)
... 4 more
</details>
|
1.0
|
Signed release apk Key password missing - <!-- You must use this template or your issue will be closed without investigation. Please see the guidelines. -->
## Problem description
When exporting a signed release apk, in the newest stable version R204 you removed the "key password". Since that, all of my builds fail and it throws an error "wrong password..."
## Attach a .c3p
doesn't matter what project you use, it's just a signing error.
## Steps to reproduce
Open any project.
Go to Export -> signed release apk -> fill in your key (key password missing)
At the end of the build -> error (see error log below)
## Observed result
build error
## Expected result
normal build
## More details
**Affected browsers/platforms:** Android
**First affected release:** r204
## System details
<!-- If you see a crash report dialog, please copy and paste it to where it says "PASTE HERE" below. -->
<!-- Otherwise please go to Menu > About > Platform information and paste that information there instead. -->
<details><summary>View details</summary>
Error log:
Error: Failed to load signer "signer #1"
java.io.IOException: Failed to obtain key with alias "upload" from tmp/918f060a-d711-49c3-983c-1c234283ce7f. Wrong password?
at com.android.apksigner.ApkSignerTool$SignerParams.loadPrivateKeyAndCertsFromKeyStore(ApkSignerTool.java:690)
at com.android.apksigner.ApkSignerTool$SignerParams.loadPrivateKeyAndCerts(ApkSignerTool.java:555)
at com.android.apksigner.ApkSignerTool$SignerParams.access$200(ApkSignerTool.java:509)
at com.android.apksigner.ApkSignerTool.sign(ApkSignerTool.java:215)
at com.android.apksigner.ApkSignerTool.main(ApkSignerTool.java:89)
Caused by: java.security.UnrecoverableKeyException: Cannot recover key
at sun.security.provider.KeyProtector.recover(KeyProtector.java:315)
at sun.security.provider.JavaKeyStore.engineGetKey(JavaKeyStore.java:143)
at sun.security.provider.JavaKeyStore$JKS.engineGetKey(JavaKeyStore.java:57)
at sun.security.provider.KeyStoreDelegator.engineGetKey(KeyStoreDelegator.java:96)
at sun.security.provider.JavaKeyStore$DualFormatJKS.engineGetKey(JavaKeyStore.java:71)
at java.security.KeyStore.getKey(KeyStore.java:1023)
at com.android.apksigner.ApkSignerTool$SignerParams.loadPrivateKeyAndCertsFromKeyStore(ApkSignerTool.java:663)
... 4 more
</details>
|
non_test
|
signed release apk key password missing problem description when exporting a signed release apk in the newest stable version you removed the key password since that all of my builds fail and it throws an error wrong password attach a doesn t matter what project you use it s just a signing error steps to reproduce open any project go to export signed release apk fill in your key key password missing at the end of the build error see error log below observed result build error expected result normal build more details affected browsers platforms android first affected release system details about platform information and paste that information there instead view details error log error failed to load signer signer java io ioexception failed to obtain key with alias upload from tmp wrong password at com android apksigner apksignertool signerparams loadprivatekeyandcertsfromkeystore apksignertool java at com android apksigner apksignertool signerparams loadprivatekeyandcerts apksignertool java at com android apksigner apksignertool signerparams access apksignertool java at com android apksigner apksignertool sign apksignertool java at com android apksigner apksignertool main apksignertool java caused by java security unrecoverablekeyexception cannot recover key at sun security provider keyprotector recover keyprotector java at sun security provider javakeystore enginegetkey javakeystore java at sun security provider javakeystore jks enginegetkey javakeystore java at sun security provider keystoredelegator enginegetkey keystoredelegator java at sun security provider javakeystore dualformatjks enginegetkey javakeystore java at java security keystore getkey keystore java at com android apksigner apksignertool signerparams loadprivatekeyandcertsfromkeystore apksignertool java more
| 0
|
710,215
| 24,411,232,355
|
IssuesEvent
|
2022-10-05 12:33:50
|
OpenRefine/CommonsExtension
|
https://api.github.com/repos/OpenRefine/CommonsExtension
|
closed
|
Allow people to remove Commons categories from the selected list, while listing desired categories to retrieve files from
|
enhancement UX high priority
|
When I start the Commons extension, and I am listing the Commons categories I am interested in retrieving files from, I sometimes makes mistakes. I may have listed several categories (and their depth) but then may want to remove one or more of them again (because I changed my mind, I mistyped, etc)
E.g. in the example below:
<img width="1265" alt="image" src="https://user-images.githubusercontent.com/9881645/188638378-1d478d2d-ecbe-4034-b1f8-4b3052983587.png">
_Oops! I absolutely do NOT want to load files from the Category:Sculptures in Amsterdam. Why would I? Sculptures in Rotterdam and Delft are way cooler._
It would be great to add the option to remove categories here, by adding a cross at the end of each line (behind the category depth field). If the user clicks that cross, the line will be deleted and files from the category will not be retrieved anymore.
We already use such a 'removing cross' in various other places in OpenRefine's interface, e.g. in the selection of (and removal of) reconciliation services:
<img width="313" alt="Screenshot 2022-09-06 at 14 42 03" src="https://user-images.githubusercontent.com/9881645/188638746-4daa51ac-5187-4441-8117-93a652bd059c.png">
|
1.0
|
Allow people to remove Commons categories from the selected list, while listing desired categories to retrieve files from - When I start the Commons extension, and I am listing the Commons categories I am interested in retrieving files from, I sometimes makes mistakes. I may have listed several categories (and their depth) but then may want to remove one or more of them again (because I changed my mind, I mistyped, etc)
E.g. in the example below:
<img width="1265" alt="image" src="https://user-images.githubusercontent.com/9881645/188638378-1d478d2d-ecbe-4034-b1f8-4b3052983587.png">
_Oops! I absolutely do NOT want to load files from the Category:Sculptures in Amsterdam. Why would I? Sculptures in Rotterdam and Delft are way cooler._
It would be great to add the option to remove categories here, by adding a cross at the end of each line (behind the category depth field). If the user clicks that cross, the line will be deleted and files from the category will not be retrieved anymore.
We already use such a 'removing cross' in various other places in OpenRefine's interface, e.g. in the selection of (and removal of) reconciliation services:
<img width="313" alt="Screenshot 2022-09-06 at 14 42 03" src="https://user-images.githubusercontent.com/9881645/188638746-4daa51ac-5187-4441-8117-93a652bd059c.png">
|
non_test
|
allow people to remove commons categories from the selected list while listing desired categories to retrieve files from when i start the commons extension and i am listing the commons categories i am interested in retrieving files from i sometimes makes mistakes i may have listed several categories and their depth but then may want to remove one or more of them again because i changed my mind i mistyped etc e g in the example below img width alt image src oops i absolutely do not want to load files from the category sculptures in amsterdam why would i sculptures in rotterdam and delft are way cooler it would be great to add the option to remove categories here by adding a cross at the end of each line behind the category depth field if the user clicks that cross the line will be deleted and files from the category will not be retrieved anymore we already use such a removing cross in various other places in openrefine s interface e g in the selection of and removal of reconciliation services img width alt screenshot at src
| 0
|
158,509
| 12,417,744,641
|
IssuesEvent
|
2020-05-22 21:33:07
|
IntellectualSites/PlotSquared
|
https://api.github.com/repos/IntellectualSites/PlotSquared
|
closed
|
plot home error
|
[?] Testing Required
| ERROR: type should be string, got "\r\nhttps://www.athion.net/ISPaster/paste/view/3313f5e44efc4c6bb16548b5fa712925\r\n\r\nPaper 1.12.2\r\nMinecraft 1.12,2\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\nType /p home or /p h \r\n\r\n\r\n"
|
1.0
|
plot home error -
https://www.athion.net/ISPaster/paste/view/3313f5e44efc4c6bb16548b5fa712925
Paper 1.12.2
Minecraft 1.12,2
Type /p home or /p h
|
test
|
plot home error paper minecraft type p home or p h
| 1
|
139,932
| 20,983,550,971
|
IssuesEvent
|
2022-03-28 22:57:43
|
mozilla/foundation.mozilla.org
|
https://api.github.com/repos/mozilla/foundation.mozilla.org
|
closed
|
[What you can do page] updates on page type
|
design Fo'Mo
|
**Background:**
Pomax suggested we update the "What you can do" page type to match the other pages, since it is causing some update issues.
**To do:**
- [ ] Build a [doc with pros and cons](https://docs.google.com/document/d/130iAeCXsqHglPBUulaNKn5-YtOkRwU_nM2caZ-lyuVU/edit?usp=sharing) related to this update from a UX, Visual Design and Engineering perspective. It will allow us to reveal blind spots and requirements if we decide to create a new page.
@sabrinang @natalieworth @nancyt1 @kristinashu please add your points to this list - once we have some solid points from the design perpective I'll share it with Pomax and Engineers to get theirs too.
|
1.0
|
[What you can do page] updates on page type - **Background:**
Pomax suggested we update the "What you can do" page type to match the other pages, since it is causing some update issues.
**To do:**
- [ ] Build a [doc with pros and cons](https://docs.google.com/document/d/130iAeCXsqHglPBUulaNKn5-YtOkRwU_nM2caZ-lyuVU/edit?usp=sharing) related to this update from a UX, Visual Design and Engineering perspective. It will allow us to reveal blind spots and requirements if we decide to create a new page.
@sabrinang @natalieworth @nancyt1 @kristinashu please add your points to this list - once we have some solid points from the design perpective I'll share it with Pomax and Engineers to get theirs too.
|
non_test
|
updates on page type background pomax suggested we update the what you can do page type to match the other pages since it is causing some update issues to do build a related to this update from a ux visual design and engineering perspective it will allow us to reveal blind spots and requirements if we decide to create a new page sabrinang natalieworth kristinashu please add your points to this list once we have some solid points from the design perpective i ll share it with pomax and engineers to get theirs too
| 0
|
140,855
| 18,924,237,050
|
IssuesEvent
|
2021-11-17 07:38:25
|
yknx4/MongoDBRest
|
https://api.github.com/repos/yknx4/MongoDBRest
|
closed
|
CVE-2020-11023 (Medium) detected in jquery-1.7.2.min.js
|
security vulnerability stale
|
## CVE-2020-11023 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-1.7.2.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js</a></p>
<p>Path to dependency file: MongoDBRest/node_modules/jmespath/index.html</p>
<p>Path to vulnerable library: /node_modules/jmespath/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.7.2.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/yknx4/MongoDBRest/commit/fd8940b3548133438d50e52b7437dac7aa6a274f">fd8940b3548133438d50e52b7437dac7aa6a274f</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
<p>Publish Date: 2020-04-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11023>CVE-2020-11023</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/jquery/jquery/security/advisories/GHSA-jpcq-cgw6-v4j6,https://github.com/rails/jquery-rails/blob/master/CHANGELOG.md#440">https://github.com/jquery/jquery/security/advisories/GHSA-jpcq-cgw6-v4j6,https://github.com/rails/jquery-rails/blob/master/CHANGELOG.md#440</a></p>
<p>Release Date: 2020-04-29</p>
<p>Fix Resolution: jquery - 3.5.0;jquery-rails - 4.4.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2020-11023 (Medium) detected in jquery-1.7.2.min.js - ## CVE-2020-11023 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-1.7.2.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js</a></p>
<p>Path to dependency file: MongoDBRest/node_modules/jmespath/index.html</p>
<p>Path to vulnerable library: /node_modules/jmespath/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.7.2.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/yknx4/MongoDBRest/commit/fd8940b3548133438d50e52b7437dac7aa6a274f">fd8940b3548133438d50e52b7437dac7aa6a274f</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
<p>Publish Date: 2020-04-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11023>CVE-2020-11023</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/jquery/jquery/security/advisories/GHSA-jpcq-cgw6-v4j6,https://github.com/rails/jquery-rails/blob/master/CHANGELOG.md#440">https://github.com/jquery/jquery/security/advisories/GHSA-jpcq-cgw6-v4j6,https://github.com/rails/jquery-rails/blob/master/CHANGELOG.md#440</a></p>
<p>Release Date: 2020-04-29</p>
<p>Fix Resolution: jquery - 3.5.0;jquery-rails - 4.4.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve medium detected in jquery min js cve medium severity vulnerability vulnerable library jquery min js javascript library for dom operations library home page a href path to dependency file mongodbrest node modules jmespath index html path to vulnerable library node modules jmespath index html dependency hierarchy x jquery min js vulnerable library found in head commit a href found in base branch main vulnerability details in jquery versions greater than or equal to and before passing html containing elements from untrusted sources even after sanitizing it to one of jquery s dom manipulation methods i e html append and others may execute untrusted code this problem is patched in jquery publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jquery jquery rails step up your open source security game with whitesource
| 0
|
297,711
| 22,389,190,716
|
IssuesEvent
|
2022-06-17 05:23:49
|
nueramic/mathml
|
https://api.github.com/repos/nueramic/mathml
|
closed
|
Classification
|
documentation algorithms
|
# LogisticRegressionRBF
- [x] class
- [x] tests
# LogisticRegression
- [x] class
- [x] tests
# SVM
- [x] class
- [x] tests
- [x] fix bugs
# Metrics
- [x] move from archive all metrics and add some basic metrics
|
1.0
|
Classification - # LogisticRegressionRBF
- [x] class
- [x] tests
# LogisticRegression
- [x] class
- [x] tests
# SVM
- [x] class
- [x] tests
- [x] fix bugs
# Metrics
- [x] move from archive all metrics and add some basic metrics
|
non_test
|
classification logisticregressionrbf class tests logisticregression class tests svm class tests fix bugs metrics move from archive all metrics and add some basic metrics
| 0
|
599,354
| 18,271,889,145
|
IssuesEvent
|
2021-10-04 14:35:12
|
cloudnativedaysjp/reviewapp-operator
|
https://api.github.com/repos/cloudnativedaysjp/reviewapp-operator
|
opened
|
baseimage に distroless を使う
|
medium priority
|
現状 `alpine:3.13.6` を利用しているのを、 `gcr.io/distroless/static:nonroot` を使うようにしたい。
### 以降のために必要なこと
* gateways/gitcommand/command.go で git コマンドを os.exec で実行してるのをやめる必要がある
* git クライアントを使うために現状 alpine を利用
|
1.0
|
baseimage に distroless を使う - 現状 `alpine:3.13.6` を利用しているのを、 `gcr.io/distroless/static:nonroot` を使うようにしたい。
### 以降のために必要なこと
* gateways/gitcommand/command.go で git コマンドを os.exec で実行してるのをやめる必要がある
* git クライアントを使うために現状 alpine を利用
|
non_test
|
baseimage に distroless を使う 現状 alpine を利用しているのを、 gcr io distroless static nonroot を使うようにしたい。 以降のために必要なこと gateways gitcommand command go で git コマンドを os exec で実行してるのをやめる必要がある git クライアントを使うために現状 alpine を利用
| 0
|
313,591
| 23,483,704,270
|
IssuesEvent
|
2022-08-17 12:51:16
|
Namchee/windgraph
|
https://api.github.com/repos/Namchee/windgraph
|
closed
|
docs: update documentation to match new template requirement
|
documentation
|
## Overview
Due to a change introduced in #17, requests must include `template` query string to use templates or they will be rendered as `blank`s.
This creates an undesirable behavior for the example, as all the example image uses the `hero` image template. To fix this, add `template=hero` to all example requests.
|
1.0
|
docs: update documentation to match new template requirement - ## Overview
Due to a change introduced in #17, requests must include `template` query string to use templates or they will be rendered as `blank`s.
This creates an undesirable behavior for the example, as all the example image uses the `hero` image template. To fix this, add `template=hero` to all example requests.
|
non_test
|
docs update documentation to match new template requirement overview due to a change introduced in requests must include template query string to use templates or they will be rendered as blank s this creates an undesirable behavior for the example as all the example image uses the hero image template to fix this add template hero to all example requests
| 0
|
20,724
| 27,424,771,250
|
IssuesEvent
|
2023-03-01 19:22:55
|
geneontology/go-ontology
|
https://api.github.com/repos/geneontology/go-ontology
|
closed
|
NTR: [egg deposition]
|
New term request organism-level process
|
Please provide as much information as you can:
* **Suggested term label:**
egg deposition
* **Definition (free text)**
The multicellular organismal reproductive process that results in the movement of an egg from within an organism into the external environment.
* **Reference, in format PMID:#######**
PMID:31164023
PMID:18050396
* **Gene product name and ID to be annotated to this term**
unc-54 (WBGene00006789)
* **Parent term(s)**
is_a multicellular organismal reproductive process (GO:0048609), part_of oviposition/egg-laying behavior (GO:0018991)
* **Children terms (if applicable)** Should any existing terms that should be moved underneath this new proposed term?
* **Synonyms (please specify, EXACT, BROAD, NARROW or RELATED)**
* **Cross-references**
* For enzymes, please provide RHEA and/or EC numbers.
* Can also provide MetaCyc, KEGG, Wikipedia, and other links.
* **Any other information**
Proposed to delineate nervous system processes involved egg-laying behavior (GO:0018991) from the mechanics of egg deposition.
|
1.0
|
NTR: [egg deposition] - Please provide as much information as you can:
* **Suggested term label:**
egg deposition
* **Definition (free text)**
The multicellular organismal reproductive process that results in the movement of an egg from within an organism into the external environment.
* **Reference, in format PMID:#######**
PMID:31164023
PMID:18050396
* **Gene product name and ID to be annotated to this term**
unc-54 (WBGene00006789)
* **Parent term(s)**
is_a multicellular organismal reproductive process (GO:0048609), part_of oviposition/egg-laying behavior (GO:0018991)
* **Children terms (if applicable)** Should any existing terms that should be moved underneath this new proposed term?
* **Synonyms (please specify, EXACT, BROAD, NARROW or RELATED)**
* **Cross-references**
* For enzymes, please provide RHEA and/or EC numbers.
* Can also provide MetaCyc, KEGG, Wikipedia, and other links.
* **Any other information**
Proposed to delineate nervous system processes involved egg-laying behavior (GO:0018991) from the mechanics of egg deposition.
|
non_test
|
ntr please provide as much information as you can suggested term label egg deposition definition free text the multicellular organismal reproductive process that results in the movement of an egg from within an organism into the external environment reference in format pmid pmid pmid gene product name and id to be annotated to this term unc parent term s is a multicellular organismal reproductive process go part of oviposition egg laying behavior go children terms if applicable should any existing terms that should be moved underneath this new proposed term synonyms please specify exact broad narrow or related cross references for enzymes please provide rhea and or ec numbers can also provide metacyc kegg wikipedia and other links any other information proposed to delineate nervous system processes involved egg laying behavior go from the mechanics of egg deposition
| 0
|
72,358
| 8,723,647,115
|
IssuesEvent
|
2018-12-09 23:43:55
|
ServiceInnovationLab/PresenceChecker
|
https://api.github.com/repos/ServiceInnovationLab/PresenceChecker
|
closed
|
Confirm applicant details
|
design development question
|
As Contact Center Staff or a Citizenship Officer
I need to see the Applicants details in the 'Presence Checker'
So I can confirm the passport details are a match
A/C
- By entering the passport number in the Enter details screen I can see the applicants identity details:
- Confirmation passport #
- Surname
- First name(s)
- Second name(s)
- Third name(s)
- Date of birth
- Nationality
- Button 'Next'
- Button 'Enter new ID'
|
1.0
|
Confirm applicant details - As Contact Center Staff or a Citizenship Officer
I need to see the Applicants details in the 'Presence Checker'
So I can confirm the passport details are a match
A/C
- By entering the passport number in the Enter details screen I can see the applicants identity details:
- Confirmation passport #
- Surname
- First name(s)
- Second name(s)
- Third name(s)
- Date of birth
- Nationality
- Button 'Next'
- Button 'Enter new ID'
|
non_test
|
confirm applicant details as contact center staff or a citizenship officer i need to see the applicants details in the presence checker so i can confirm the passport details are a match a c by entering the passport number in the enter details screen i can see the applicants identity details confirmation passport surname first name s second name s third name s date of birth nationality button next button enter new id
| 0
|
139,566
| 11,273,908,153
|
IssuesEvent
|
2020-01-14 17:26:27
|
streamnative/pulsar
|
https://api.github.com/repos/streamnative/pulsar
|
closed
|
ISSUE-3774: [go client] add go related tests and checks in jenkins
|
component/go component/test triage/week-35 type/task
|
Original Issue: apache/pulsar#3774
---
**Is your feature request related to a problem? Please describe.**
At present, Jenkins does not check the unit tests and code specifications related to go. When we modify the unit test of go or add new code, we can only check it locally. For some code formats and specifications, we have no way. Do a good job of specification and unification
**Describe the solution you'd like**
Regarding the check of the go code format, the more mature tool in the community is [gometalinter](https://github.com/alecthomas/gometalinter)
**Additional context**
check.sh
```
#!/bin/bash
# The script does automatic checking on a Go package and its sub-packages, including:
# 1. gofmt (http://golang.org/cmd/gofmt/)
# 2. golint (https://github.com/golang/lint)
# 3. go vet (http://golang.org/cmd/vet)
# 4. gosimple (https://github.com/dominikh/go-simple)
# 5. unconvert (https://github.com/mdempsky/unconvert)
#
# gometalinter (github.com/alecthomas/gometalinter) is used to run each static
# checker.
set -ex
# Make sure gometalinter is installed and $GOPATH/bin is in your path.
# $ go get -v github.com/alecthomas/gometalinter"
# $ gometalinter --install"
if [ ! -x "$(type -p gometalinter.v2)" ]; then
exit 1
fi
linter_targets=$(go list ./...)
# Automatic checks
test -z "$(gometalinter.v2 -j 4 --disable-all \
--enable=gofmt \
--enable=golint \
--enable=vet \
--enable=gosimple \
--enable=unconvert \
--deadline=10m $linter_targets 2>&1 | grep -v 'ALL_CAPS\|OP_' 2>&1 | tee /dev/stderr)"
GO111MODULE=on go test $linter_targets
```
|
1.0
|
ISSUE-3774: [go client] add go related tests and checks in jenkins - Original Issue: apache/pulsar#3774
---
**Is your feature request related to a problem? Please describe.**
At present, Jenkins does not check the unit tests and code specifications related to go. When we modify the unit test of go or add new code, we can only check it locally. For some code formats and specifications, we have no way. Do a good job of specification and unification
**Describe the solution you'd like**
Regarding the check of the go code format, the more mature tool in the community is [gometalinter](https://github.com/alecthomas/gometalinter)
**Additional context**
check.sh
```
#!/bin/bash
# The script does automatic checking on a Go package and its sub-packages, including:
# 1. gofmt (http://golang.org/cmd/gofmt/)
# 2. golint (https://github.com/golang/lint)
# 3. go vet (http://golang.org/cmd/vet)
# 4. gosimple (https://github.com/dominikh/go-simple)
# 5. unconvert (https://github.com/mdempsky/unconvert)
#
# gometalinter (github.com/alecthomas/gometalinter) is used to run each static
# checker.
set -ex
# Make sure gometalinter is installed and $GOPATH/bin is in your path.
# $ go get -v github.com/alecthomas/gometalinter"
# $ gometalinter --install"
if [ ! -x "$(type -p gometalinter.v2)" ]; then
exit 1
fi
linter_targets=$(go list ./...)
# Automatic checks
test -z "$(gometalinter.v2 -j 4 --disable-all \
--enable=gofmt \
--enable=golint \
--enable=vet \
--enable=gosimple \
--enable=unconvert \
--deadline=10m $linter_targets 2>&1 | grep -v 'ALL_CAPS\|OP_' 2>&1 | tee /dev/stderr)"
GO111MODULE=on go test $linter_targets
```
|
test
|
issue add go related tests and checks in jenkins original issue apache pulsar is your feature request related to a problem please describe at present jenkins does not check the unit tests and code specifications related to go when we modify the unit test of go or add new code we can only check it locally for some code formats and specifications we have no way do a good job of specification and unification describe the solution you d like regarding the check of the go code format the more mature tool in the community is additional context check sh bin bash the script does automatic checking on a go package and its sub packages including gofmt golint go vet gosimple unconvert gometalinter github com alecthomas gometalinter is used to run each static checker set ex make sure gometalinter is installed and gopath bin is in your path go get v github com alecthomas gometalinter gometalinter install if then exit fi linter targets go list automatic checks test z gometalinter j disable all enable gofmt enable golint enable vet enable gosimple enable unconvert deadline linter targets grep v all caps op tee dev stderr on go test linter targets
| 1
|
374,258
| 11,082,811,024
|
IssuesEvent
|
2019-12-13 13:04:45
|
incognitochain/incognito-wallet
|
https://api.github.com/repos/incognitochain/incognito-wallet
|
closed
|
Cannot withdraw when clicking max amount
|
Priority: Medium Type: Bug
|
Steps:
1. Go to Ptoken
2. Select withdraw
3. Input all data
4. Click max amount
**Actual result:** The error message is shown. Max amount always shows 0.
**Expected result:** The error message is NOT shown. Max amount should be shown max amount
|
1.0
|
Cannot withdraw when clicking max amount - Steps:
1. Go to Ptoken
2. Select withdraw
3. Input all data
4. Click max amount
**Actual result:** The error message is shown. Max amount always shows 0.
**Expected result:** The error message is NOT shown. Max amount should be shown max amount
|
non_test
|
cannot withdraw when clicking max amount steps go to ptoken select withdraw input all data click max amount actual result the error message is shown max amount always shows expected result the error message is not shown max amount should be shown max amount
| 0
|
496,181
| 14,342,090,725
|
IssuesEvent
|
2020-11-28 01:05:25
|
enwikipedia-acc/waca
|
https://api.github.com/repos/enwikipedia-acc/waca
|
opened
|
Preform proper security testing
|
Priority: Medium
|
Right now #574 is about to be approved. We should be going through and properly testing access to the new ban functions and any other testing that needs to be updated. There also may be sensitive areas we aren't testing.
|
1.0
|
Preform proper security testing - Right now #574 is about to be approved. We should be going through and properly testing access to the new ban functions and any other testing that needs to be updated. There also may be sensitive areas we aren't testing.
|
non_test
|
preform proper security testing right now is about to be approved we should be going through and properly testing access to the new ban functions and any other testing that needs to be updated there also may be sensitive areas we aren t testing
| 0
|
285,249
| 31,144,938,985
|
IssuesEvent
|
2023-08-16 05:23:26
|
nexmo-community/rapporteur-workshop
|
https://api.github.com/repos/nexmo-community/rapporteur-workshop
|
opened
|
tornado-4.5.3.tar.gz: 2 vulnerabilities (highest severity is: 6.1)
|
Mend: dependency security vulnerability
|
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tornado-4.5.3.tar.gz</b></p></summary>
<p>Tornado is a Python web framework and asynchronous networking library, originally developed at FriendFeed.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/e3/7b/e29ab3d51c8df66922fea216e2bddfcb6430fb29620e5165b16a216e0d3c/tornado-4.5.3.tar.gz">https://files.pythonhosted.org/packages/e3/7b/e29ab3d51c8df66922fea216e2bddfcb6430fb29620e5165b16a216e0d3c/tornado-4.5.3.tar.gz</a></p>
<p>Path to dependency file: /Pipfile</p>
<p>Path to vulnerable library: /Pipfile</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/rapporteur-workshop/commit/0ba4ea6c992d5f8c4aae74e64a717948b70d27a2">0ba4ea6c992d5f8c4aae74e64a717948b70d27a2</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (tornado version) | Remediation Possible** |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2023-28370](https://www.mend.io/vulnerability-database/CVE-2023-28370) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.1 | tornado-4.5.3.tar.gz | Direct | 6.3.2 | ✅ |
| [WS-2023-0296](https://github.com/tornadoweb/tornado/commit/b7a5dd29bb02950303ae96055082c12a1ea0a4fe) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.5 | tornado-4.5.3.tar.gz | Direct | tornado - 6.3.3 | ✅ |
<p>**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2023-28370</summary>
### Vulnerable Library - <b>tornado-4.5.3.tar.gz</b></p>
<p>Tornado is a Python web framework and asynchronous networking library, originally developed at FriendFeed.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/e3/7b/e29ab3d51c8df66922fea216e2bddfcb6430fb29620e5165b16a216e0d3c/tornado-4.5.3.tar.gz">https://files.pythonhosted.org/packages/e3/7b/e29ab3d51c8df66922fea216e2bddfcb6430fb29620e5165b16a216e0d3c/tornado-4.5.3.tar.gz</a></p>
<p>Path to dependency file: /Pipfile</p>
<p>Path to vulnerable library: /Pipfile</p>
<p>
Dependency Hierarchy:
- :x: **tornado-4.5.3.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/rapporteur-workshop/commit/0ba4ea6c992d5f8c4aae74e64a717948b70d27a2">0ba4ea6c992d5f8c4aae74e64a717948b70d27a2</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Open redirect vulnerability in Tornado versions 6.3.1 and earlier allows a remote unauthenticated attacker to redirect a user to an arbitrary web site and conduct a phishing attack by having user access a specially crafted URL.
<p>Publish Date: 2023-05-25
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-28370>CVE-2023-28370</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2023-05-25</p>
<p>Fix Resolution: 6.3.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> WS-2023-0296</summary>
### Vulnerable Library - <b>tornado-4.5.3.tar.gz</b></p>
<p>Tornado is a Python web framework and asynchronous networking library, originally developed at FriendFeed.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/e3/7b/e29ab3d51c8df66922fea216e2bddfcb6430fb29620e5165b16a216e0d3c/tornado-4.5.3.tar.gz">https://files.pythonhosted.org/packages/e3/7b/e29ab3d51c8df66922fea216e2bddfcb6430fb29620e5165b16a216e0d3c/tornado-4.5.3.tar.gz</a></p>
<p>Path to dependency file: /Pipfile</p>
<p>Path to vulnerable library: /Pipfile</p>
<p>
Dependency Hierarchy:
- :x: **tornado-4.5.3.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/rapporteur-workshop/commit/0ba4ea6c992d5f8c4aae74e64a717948b70d27a2">0ba4ea6c992d5f8c4aae74e64a717948b70d27a2</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Tornado vulnerable to HTTP request smuggling via improper parsing of `Content-Length` fields and chunk lengths
<p>Publish Date: 2023-08-15
<p>URL: <a href=https://github.com/tornadoweb/tornado/commit/b7a5dd29bb02950303ae96055082c12a1ea0a4fe>WS-2023-0296</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-qppv-j76h-2rpx">https://github.com/advisories/GHSA-qppv-j76h-2rpx</a></p>
<p>Release Date: 2023-08-15</p>
<p>Fix Resolution: tornado - 6.3.3</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details>
***
<p>:rescue_worker_helmet:Automatic Remediation will be attempted for this issue.</p>
|
True
|
tornado-4.5.3.tar.gz: 2 vulnerabilities (highest severity is: 6.1) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tornado-4.5.3.tar.gz</b></p></summary>
<p>Tornado is a Python web framework and asynchronous networking library, originally developed at FriendFeed.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/e3/7b/e29ab3d51c8df66922fea216e2bddfcb6430fb29620e5165b16a216e0d3c/tornado-4.5.3.tar.gz">https://files.pythonhosted.org/packages/e3/7b/e29ab3d51c8df66922fea216e2bddfcb6430fb29620e5165b16a216e0d3c/tornado-4.5.3.tar.gz</a></p>
<p>Path to dependency file: /Pipfile</p>
<p>Path to vulnerable library: /Pipfile</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/rapporteur-workshop/commit/0ba4ea6c992d5f8c4aae74e64a717948b70d27a2">0ba4ea6c992d5f8c4aae74e64a717948b70d27a2</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (tornado version) | Remediation Possible** |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2023-28370](https://www.mend.io/vulnerability-database/CVE-2023-28370) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.1 | tornado-4.5.3.tar.gz | Direct | 6.3.2 | ✅ |
| [WS-2023-0296](https://github.com/tornadoweb/tornado/commit/b7a5dd29bb02950303ae96055082c12a1ea0a4fe) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.5 | tornado-4.5.3.tar.gz | Direct | tornado - 6.3.3 | ✅ |
<p>**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2023-28370</summary>
### Vulnerable Library - <b>tornado-4.5.3.tar.gz</b></p>
<p>Tornado is a Python web framework and asynchronous networking library, originally developed at FriendFeed.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/e3/7b/e29ab3d51c8df66922fea216e2bddfcb6430fb29620e5165b16a216e0d3c/tornado-4.5.3.tar.gz">https://files.pythonhosted.org/packages/e3/7b/e29ab3d51c8df66922fea216e2bddfcb6430fb29620e5165b16a216e0d3c/tornado-4.5.3.tar.gz</a></p>
<p>Path to dependency file: /Pipfile</p>
<p>Path to vulnerable library: /Pipfile</p>
<p>
Dependency Hierarchy:
- :x: **tornado-4.5.3.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/rapporteur-workshop/commit/0ba4ea6c992d5f8c4aae74e64a717948b70d27a2">0ba4ea6c992d5f8c4aae74e64a717948b70d27a2</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Open redirect vulnerability in Tornado versions 6.3.1 and earlier allows a remote unauthenticated attacker to redirect a user to an arbitrary web site and conduct a phishing attack by having user access a specially crafted URL.
<p>Publish Date: 2023-05-25
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-28370>CVE-2023-28370</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2023-05-25</p>
<p>Fix Resolution: 6.3.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> WS-2023-0296</summary>
### Vulnerable Library - <b>tornado-4.5.3.tar.gz</b></p>
<p>Tornado is a Python web framework and asynchronous networking library, originally developed at FriendFeed.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/e3/7b/e29ab3d51c8df66922fea216e2bddfcb6430fb29620e5165b16a216e0d3c/tornado-4.5.3.tar.gz">https://files.pythonhosted.org/packages/e3/7b/e29ab3d51c8df66922fea216e2bddfcb6430fb29620e5165b16a216e0d3c/tornado-4.5.3.tar.gz</a></p>
<p>Path to dependency file: /Pipfile</p>
<p>Path to vulnerable library: /Pipfile</p>
<p>
Dependency Hierarchy:
- :x: **tornado-4.5.3.tar.gz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/rapporteur-workshop/commit/0ba4ea6c992d5f8c4aae74e64a717948b70d27a2">0ba4ea6c992d5f8c4aae74e64a717948b70d27a2</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Tornado vulnerable to HTTP request smuggling via improper parsing of `Content-Length` fields and chunk lengths
<p>Publish Date: 2023-08-15
<p>URL: <a href=https://github.com/tornadoweb/tornado/commit/b7a5dd29bb02950303ae96055082c12a1ea0a4fe>WS-2023-0296</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-qppv-j76h-2rpx">https://github.com/advisories/GHSA-qppv-j76h-2rpx</a></p>
<p>Release Date: 2023-08-15</p>
<p>Fix Resolution: tornado - 6.3.3</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.
</details>
***
<p>:rescue_worker_helmet:Automatic Remediation will be attempted for this issue.</p>
|
non_test
|
tornado tar gz vulnerabilities highest severity is vulnerable library tornado tar gz tornado is a python web framework and asynchronous networking library originally developed at friendfeed library home page a href path to dependency file pipfile path to vulnerable library pipfile found in head commit a href vulnerabilities cve severity cvss dependency type fixed in tornado version remediation possible medium tornado tar gz direct medium tornado tar gz direct tornado in some cases remediation pr cannot be created automatically for a vulnerability despite the availability of remediation details cve vulnerable library tornado tar gz tornado is a python web framework and asynchronous networking library originally developed at friendfeed library home page a href path to dependency file pipfile path to vulnerable library pipfile dependency hierarchy x tornado tar gz vulnerable library found in head commit a href found in base branch main vulnerability details open redirect vulnerability in tornado versions and earlier allows a remote unauthenticated attacker to redirect a user to an arbitrary web site and conduct a phishing attack by having user access a specially crafted url publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version release date fix resolution rescue worker helmet automatic remediation will be attempted for this issue ws vulnerable library tornado tar gz tornado is a python web framework and asynchronous networking library originally developed at friendfeed library home page a href path to dependency file pipfile path to vulnerable library pipfile dependency hierarchy x tornado tar gz vulnerable library found in head commit a href found in base branch main vulnerability details tornado vulnerable to http request smuggling via improper parsing of content length fields and chunk lengths publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution tornado rescue worker helmet automatic remediation will be attempted for this issue rescue worker helmet automatic remediation will be attempted for this issue
| 0
|
172,168
| 13,264,675,813
|
IssuesEvent
|
2020-08-21 04:25:53
|
IntellectualSites/FastAsyncWorldEdit
|
https://api.github.com/repos/IntellectualSites/FastAsyncWorldEdit
|
closed
|
Unable to copy entities
|
Requires Testing
|
Unable to copy entities Whether the command is //copy or //copy -e
plugin version is FastAsyncWorldEdit-1.16-313
paper-131
|
1.0
|
Unable to copy entities - Unable to copy entities Whether the command is //copy or //copy -e
plugin version is FastAsyncWorldEdit-1.16-313
paper-131
|
test
|
unable to copy entities unable to copy entities whether the command is copy or copy e plugin version is fastasyncworldedit paper
| 1
|
258,163
| 8,161,245,571
|
IssuesEvent
|
2018-08-24 06:36:53
|
coingecko/cryptoexchange
|
https://api.github.com/repos/coingecko/cryptoexchange
|
closed
|
Set timestamp to nil for exchanges that don't return timestamp
|
help wanted priority
|
1. Look for all instances of `ticker.timestamp = Time.now.to_i`
e.g. https://github.com/coingecko/cryptoexchange/blob/6532d18fc36043da26d837cc068752c3a3f4ae92/lib/cryptoexchange/exchanges/qbtc/services/market.rb#L44
1. Verify that exchange still does not support timestamp
1. If exchange supports already, implement it
1. If exchange still does not support timestamp, set timestamp to `nil`
|
1.0
|
Set timestamp to nil for exchanges that don't return timestamp - 1. Look for all instances of `ticker.timestamp = Time.now.to_i`
e.g. https://github.com/coingecko/cryptoexchange/blob/6532d18fc36043da26d837cc068752c3a3f4ae92/lib/cryptoexchange/exchanges/qbtc/services/market.rb#L44
1. Verify that exchange still does not support timestamp
1. If exchange supports already, implement it
1. If exchange still does not support timestamp, set timestamp to `nil`
|
non_test
|
set timestamp to nil for exchanges that don t return timestamp look for all instances of ticker timestamp time now to i e g verify that exchange still does not support timestamp if exchange supports already implement it if exchange still does not support timestamp set timestamp to nil
| 0
|
754,165
| 26,374,291,746
|
IssuesEvent
|
2023-01-12 00:08:00
|
openantz/antz
|
https://api.github.com/repos/openantz/antz
|
closed
|
Camera re-targets active node when switching cams
|
bug A priority
|
The camera re-targets the active node when switching cams or loading a dataset. The camera position should stay fixed on its existing target when changing cams and only re-target when the camera is active and a new node is picked.
|
1.0
|
Camera re-targets active node when switching cams - The camera re-targets the active node when switching cams or loading a dataset. The camera position should stay fixed on its existing target when changing cams and only re-target when the camera is active and a new node is picked.
|
non_test
|
camera re targets active node when switching cams the camera re targets the active node when switching cams or loading a dataset the camera position should stay fixed on its existing target when changing cams and only re target when the camera is active and a new node is picked
| 0
|
809,574
| 30,199,032,103
|
IssuesEvent
|
2023-07-05 02:39:26
|
channel-io/bezier-react
|
https://api.github.com/repos/channel-io/bezier-react
|
closed
|
Implement Container Context for `Overlay`, `Tooltip` inside `Modal`
|
enhancement priority:A
|
### Description
Modal 내부에 위치하는 Overlay, Tooltip 에 컨텍스트를 통해 `ModalContent` 의 DOM node를 `container` 로 전달하는 기능을 구현합니다.
### Reasons for suggestion
Modal은 기본적으로 radix-ui의 modal Dialog이기 때문에 외부 엘리먼트와 인터랙션이 불가능합니다.
> The modality of the dialog. When set to true, interaction with outside elements will be disabled and only dialog content will be visible to screen readers. ([Radix UI - Dialog](https://www.radix-ui.com/docs/primitives/components/dialog))
Modal 내부에 Overlay나 Tooltip(클릭 가능한 콘텐츠가 있는)이 위치할 경우, 즉 위에 쌓여 있는 형태일 경우 Overlay와 Tootlip에 별도의 `container` 지정없이는 인터랙션이 불가능합니다.
- 이유: Modal, Overlay, Tootlip의 `container` 의 기본값이 모두 `document.body` 이므로 Modal과 같은 위계가 됩니다. 따라서 Modal 외부에 위치하게 되고, radix-ui modal Dialog 동작에 의해 인터랙션이 차단됩니다.
Modal 내부의 Overlay/Tootlip에 인터랙션이 불가능한건 의도된 동작이 아닙니다. 동작을 수정하기 위해 별도의 `container` 지정이 모든 사용처에서 필요한 상황입니다.
사용처에서 이 동작을 신경쓰지 않고, 선언적으로 UI를 잘 구현할 수 있도록 Modal의 컨텍스트 내부에 Overlay/Tooltip이 위치한다면 `container` 에 `ModalContent` 의 node가 주입되면 좋겠습니다.
### Proposed solution
```tsx
<Modal>
<ModalContent>
<div>
<Overlay /> // container = DOM node of ModalContent
</div>
</ModalContent>
</Modal>
```
`container` 의 우선순위는 다음과 같이 결정되면 좋겠습니다.
1. `container` 속성 직접 주입
2. Modal 내부에 있을 경우, Overlay와 Tooltip의 `container` 기본값은 `ModalContent` 의 DOM node
3. 기본값 - document.body
- Overlay의 경우, 현재 구현으론 Modal 내부에 있을 때 `keepInContainer` 속성 사용이 불가능하므로 강제로 비활성화하는 기능이 구현되면 좋겠습니다.
### References
없음
|
1.0
|
Implement Container Context for `Overlay`, `Tooltip` inside `Modal` - ### Description
Modal 내부에 위치하는 Overlay, Tooltip 에 컨텍스트를 통해 `ModalContent` 의 DOM node를 `container` 로 전달하는 기능을 구현합니다.
### Reasons for suggestion
Modal은 기본적으로 radix-ui의 modal Dialog이기 때문에 외부 엘리먼트와 인터랙션이 불가능합니다.
> The modality of the dialog. When set to true, interaction with outside elements will be disabled and only dialog content will be visible to screen readers. ([Radix UI - Dialog](https://www.radix-ui.com/docs/primitives/components/dialog))
Modal 내부에 Overlay나 Tooltip(클릭 가능한 콘텐츠가 있는)이 위치할 경우, 즉 위에 쌓여 있는 형태일 경우 Overlay와 Tootlip에 별도의 `container` 지정없이는 인터랙션이 불가능합니다.
- 이유: Modal, Overlay, Tootlip의 `container` 의 기본값이 모두 `document.body` 이므로 Modal과 같은 위계가 됩니다. 따라서 Modal 외부에 위치하게 되고, radix-ui modal Dialog 동작에 의해 인터랙션이 차단됩니다.
Modal 내부의 Overlay/Tootlip에 인터랙션이 불가능한건 의도된 동작이 아닙니다. 동작을 수정하기 위해 별도의 `container` 지정이 모든 사용처에서 필요한 상황입니다.
사용처에서 이 동작을 신경쓰지 않고, 선언적으로 UI를 잘 구현할 수 있도록 Modal의 컨텍스트 내부에 Overlay/Tooltip이 위치한다면 `container` 에 `ModalContent` 의 node가 주입되면 좋겠습니다.
### Proposed solution
```tsx
<Modal>
<ModalContent>
<div>
<Overlay /> // container = DOM node of ModalContent
</div>
</ModalContent>
</Modal>
```
`container` 의 우선순위는 다음과 같이 결정되면 좋겠습니다.
1. `container` 속성 직접 주입
2. Modal 내부에 있을 경우, Overlay와 Tooltip의 `container` 기본값은 `ModalContent` 의 DOM node
3. 기본값 - document.body
- Overlay의 경우, 현재 구현으론 Modal 내부에 있을 때 `keepInContainer` 속성 사용이 불가능하므로 강제로 비활성화하는 기능이 구현되면 좋겠습니다.
### References
없음
|
non_test
|
implement container context for overlay tooltip inside modal description modal 내부에 위치하는 overlay tooltip 에 컨텍스트를 통해 modalcontent 의 dom node를 container 로 전달하는 기능을 구현합니다 reasons for suggestion modal은 기본적으로 radix ui의 modal dialog이기 때문에 외부 엘리먼트와 인터랙션이 불가능합니다 the modality of the dialog when set to true interaction with outside elements will be disabled and only dialog content will be visible to screen readers modal 내부에 overlay나 tooltip 클릭 가능한 콘텐츠가 있는 이 위치할 경우 즉 위에 쌓여 있는 형태일 경우 overlay와 tootlip에 별도의 container 지정없이는 인터랙션이 불가능합니다 이유 modal overlay tootlip의 container 의 기본값이 모두 document body 이므로 modal과 같은 위계가 됩니다 따라서 modal 외부에 위치하게 되고 radix ui modal dialog 동작에 의해 인터랙션이 차단됩니다 modal 내부의 overlay tootlip에 인터랙션이 불가능한건 의도된 동작이 아닙니다 동작을 수정하기 위해 별도의 container 지정이 모든 사용처에서 필요한 상황입니다 사용처에서 이 동작을 신경쓰지 않고 선언적으로 ui를 잘 구현할 수 있도록 modal의 컨텍스트 내부에 overlay tooltip이 위치한다면 container 에 modalcontent 의 node가 주입되면 좋겠습니다 proposed solution tsx container dom node of modalcontent container 의 우선순위는 다음과 같이 결정되면 좋겠습니다 container 속성 직접 주입 modal 내부에 있을 경우 overlay와 tooltip의 container 기본값은 modalcontent 의 dom node 기본값 document body overlay의 경우 현재 구현으론 modal 내부에 있을 때 keepincontainer 속성 사용이 불가능하므로 강제로 비활성화하는 기능이 구현되면 좋겠습니다 references 없음
| 0
|
479
| 2,502,213,050
|
IssuesEvent
|
2015-01-09 05:21:49
|
fossology/fossology
|
https://api.github.com/repos/fossology/fossology
|
opened
|
ignore URLs/e-mail addresses in one of the example.{com|net|org} domains
|
Category: Copyright Component: Rank Component: Tester Priority: Normal Status: New Tracker: Enhancement
|
---
Author Name: **armijn hemel**
Original Redmine Issue: 5433, http://www.fossology.org/issues/5433
Original Date: 2013/07/07
---
The copyright agent currently reports URLs and e-mail addresses that include example.com, example.net and example.org domains. These are test domains defined in RFCs as test domains, so 100% bogus data for determining copyrights. By filtering these out data quality can be a lot better.
|
1.0
|
ignore URLs/e-mail addresses in one of the example.{com|net|org} domains - ---
Author Name: **armijn hemel**
Original Redmine Issue: 5433, http://www.fossology.org/issues/5433
Original Date: 2013/07/07
---
The copyright agent currently reports URLs and e-mail addresses that include example.com, example.net and example.org domains. These are test domains defined in RFCs as test domains, so 100% bogus data for determining copyrights. By filtering these out data quality can be a lot better.
|
test
|
ignore urls e mail addresses in one of the example com net org domains author name armijn hemel original redmine issue original date the copyright agent currently reports urls and e mail addresses that include example com example net and example org domains these are test domains defined in rfcs as test domains so bogus data for determining copyrights by filtering these out data quality can be a lot better
| 1
|
137,494
| 11,139,015,683
|
IssuesEvent
|
2019-12-21 01:14:37
|
rancher/rancher
|
https://api.github.com/repos/rancher/rancher
|
closed
|
Forward port: Permissions are not updated in cluster when a cluster role is modified
|
[zube]: To Test team/ca
|
Forward port of: https://github.com/rancher/rancher/issues/23292
Addressed by https://github.com/rancher/rancher/pull/24661/commits/6dee0d8cae16a5020f752e7de5526614e520850c
|
1.0
|
Forward port: Permissions are not updated in cluster when a cluster role is modified - Forward port of: https://github.com/rancher/rancher/issues/23292
Addressed by https://github.com/rancher/rancher/pull/24661/commits/6dee0d8cae16a5020f752e7de5526614e520850c
|
test
|
forward port permissions are not updated in cluster when a cluster role is modified forward port of addressed by
| 1
|
345,294
| 30,797,292,508
|
IssuesEvent
|
2023-07-31 20:59:50
|
QubesOS/updates-status
|
https://api.github.com/repos/QubesOS/updates-status
|
closed
|
core-admin-linux v4.2.12 (r4.2)
|
r4.2-host-cur-test
|
Update of core-admin-linux to v4.2.12 for Qubes OS r4.2, see comments below for details and build status.
From commit: https://github.com/QubesOS/qubes-core-admin-linux/commit/02654fc40a3c94286b094bd77772ccbaa58bbe40
[Changes since previous version](https://github.com/QubesOS/qubes-core-admin-linux/compare/v4.2.11...v4.2.12):
QubesOS/qubes-core-admin-linux@02654fc version 4.2.12
QubesOS/qubes-core-admin-linux@6c3ccdd Merge remote-tracking branch 'origin/pr/132'
QubesOS/qubes-core-admin-linux@34ef3f5 Make qubes.repos.* work when called as non-root too
QubesOS/qubes-core-admin-linux@e400a34 qubes-vm-update: do not update last-updates-check if checking updates fails
QubesOS/qubes-core-admin-linux@99b4b4d Merge remote-tracking branch 'origin/pr/129'
QubesOS/qubes-core-admin-linux@ed993aa Merge remote-tracking branch 'origin/pr/128'
QubesOS/qubes-core-admin-linux@30d9475 qubes-vm-update: refactor
QubesOS/qubes-core-admin-linux@c18eb25 qubes-vm-update: skip double selecting of templates
QubesOS/qubes-core-admin-linux@9f3ac5c qubes-vm-update: do not report updates check if service.qubes-update-check is disabled
QubesOS/qubes-core-admin-linux@a5a1623 qubes-vm-update: dom0 update features
Referenced issues:
QubesOS/qubes-issues#8162
QubesOS/qubes-issues#8349
If you're release manager, you can issue GPG-inline signed command:
* `Upload-component r4.2 core-admin-linux 02654fc40a3c94286b094bd77772ccbaa58bbe40 current all` (available 5 days from now)
* `Upload-component r4.2 core-admin-linux 02654fc40a3c94286b094bd77772ccbaa58bbe40 security-testing`
You can choose subset of distributions like:
* `Upload-component r4.2 core-admin-linux 02654fc40a3c94286b094bd77772ccbaa58bbe40 current vm-bookworm,vm-fc37` (available 5 days from now)
Above commands will work only if packages in current-testing repository were built from given commit (i.e. no new version superseded it).
For more information on how to test this update, please take a look at https://www.qubes-os.org/doc/testing/#updates.
|
1.0
|
core-admin-linux v4.2.12 (r4.2) - Update of core-admin-linux to v4.2.12 for Qubes OS r4.2, see comments below for details and build status.
From commit: https://github.com/QubesOS/qubes-core-admin-linux/commit/02654fc40a3c94286b094bd77772ccbaa58bbe40
[Changes since previous version](https://github.com/QubesOS/qubes-core-admin-linux/compare/v4.2.11...v4.2.12):
QubesOS/qubes-core-admin-linux@02654fc version 4.2.12
QubesOS/qubes-core-admin-linux@6c3ccdd Merge remote-tracking branch 'origin/pr/132'
QubesOS/qubes-core-admin-linux@34ef3f5 Make qubes.repos.* work when called as non-root too
QubesOS/qubes-core-admin-linux@e400a34 qubes-vm-update: do not update last-updates-check if checking updates fails
QubesOS/qubes-core-admin-linux@99b4b4d Merge remote-tracking branch 'origin/pr/129'
QubesOS/qubes-core-admin-linux@ed993aa Merge remote-tracking branch 'origin/pr/128'
QubesOS/qubes-core-admin-linux@30d9475 qubes-vm-update: refactor
QubesOS/qubes-core-admin-linux@c18eb25 qubes-vm-update: skip double selecting of templates
QubesOS/qubes-core-admin-linux@9f3ac5c qubes-vm-update: do not report updates check if service.qubes-update-check is disabled
QubesOS/qubes-core-admin-linux@a5a1623 qubes-vm-update: dom0 update features
Referenced issues:
QubesOS/qubes-issues#8162
QubesOS/qubes-issues#8349
If you're release manager, you can issue GPG-inline signed command:
* `Upload-component r4.2 core-admin-linux 02654fc40a3c94286b094bd77772ccbaa58bbe40 current all` (available 5 days from now)
* `Upload-component r4.2 core-admin-linux 02654fc40a3c94286b094bd77772ccbaa58bbe40 security-testing`
You can choose subset of distributions like:
* `Upload-component r4.2 core-admin-linux 02654fc40a3c94286b094bd77772ccbaa58bbe40 current vm-bookworm,vm-fc37` (available 5 days from now)
Above commands will work only if packages in current-testing repository were built from given commit (i.e. no new version superseded it).
For more information on how to test this update, please take a look at https://www.qubes-os.org/doc/testing/#updates.
|
test
|
core admin linux update of core admin linux to for qubes os see comments below for details and build status from commit qubesos qubes core admin linux version qubesos qubes core admin linux merge remote tracking branch origin pr qubesos qubes core admin linux make qubes repos work when called as non root too qubesos qubes core admin linux qubes vm update do not update last updates check if checking updates fails qubesos qubes core admin linux merge remote tracking branch origin pr qubesos qubes core admin linux merge remote tracking branch origin pr qubesos qubes core admin linux qubes vm update refactor qubesos qubes core admin linux qubes vm update skip double selecting of templates qubesos qubes core admin linux qubes vm update do not report updates check if service qubes update check is disabled qubesos qubes core admin linux qubes vm update update features referenced issues qubesos qubes issues qubesos qubes issues if you re release manager you can issue gpg inline signed command upload component core admin linux current all available days from now upload component core admin linux security testing you can choose subset of distributions like upload component core admin linux current vm bookworm vm available days from now above commands will work only if packages in current testing repository were built from given commit i e no new version superseded it for more information on how to test this update please take a look at
| 1
|
181,689
| 14,074,297,169
|
IssuesEvent
|
2020-11-04 07:01:34
|
OpenMined/PySyft
|
https://api.github.com/repos/OpenMined/PySyft
|
closed
|
Add torch.Tensor.bmm to allowlist and test suite
|
Priority: 2 - High :cold_sweat: Severity: 3 - Medium :unamused: Status: Available :wave: Type: New Feature :heavy_plus_sign: Type: Testing :test_tube:
|
# Description
This issue is a part of Syft 0.3.0 Epic 2: https://github.com/OpenMined/PySyft/issues/3696
In this issue, you will be adding support for remote execution of the torch.Tensor.bmm
method or property. This might be a really small project (literally a one-liner) or
it might require adding significant functionality to PySyft OR to the testing suite
in order to make sure the feature is both functional and tested.
## Step 0: Run tests and ./scripts/pre_commit.sh
Before you get started with this project, let's make sure you have everything building and testing
correctly. Clone the codebase and run:
```pip uninstall syft```
followed by
```pip install -e .```
Then run the pre-commit file (which will also run the tests)
```./scripts/pre_commit.sh```
If all of these tests pass, continue on. If not, make sure you have all the
dependencies in requirements.txt installed, etc.
## Step 1: Uncomment your method in the allowlist.py file
Inside [allowlist.py](https://github.com/OpenMined/PySyft/blob/syft_0.3.0/src/syft/lib/torch/allowlist.py) you will find a huge dictionary of methods. Find your method and uncomment the line its on. At the time
of writing this Issue (WARNING: THIS MAY HAVE CHANGED) the dictionary maps from the
string name of the method (in your case 'torch.Tensor.bmm') to the string representation
of the type the method returns.
## Step 2: Run Unit Tests
Run the following:
```python setup.py test```
And wait to see if some of the tests fail. Why might the tests fail now? I'm so glad you asked!
https://github.com/OpenMined/PySyft/blob/syft_0.3.0/tests/syft/lib/torch/tensor/tensor_remote_method_api_suite_test.py
In this file you'll find the torch method test suite. It AUTOMATICALLY loads all methods
from the allowlist.py file you modified in the previous step. It attempts to test them.
# Step 3: If you get a Failing Test
If you get a failing test, this could be for one of a few reasons:
### Reason 1 - The testing suite passed in non-compatible arguments
The testing suite is pretty dumb. It literally just has a permutation of possible
arguments to pass into every method on torch tensors. So, if one of those permutations
doesn't work for your method (aka... perhaps it tries to call your method without
any arguments but torch.Tensor.bmm actually requires some) then the test will
fail if the error hasn't been seen before.
If this happens - don't worry! Just look inside the only test in that file and look
for the huge lists of error types to ignore. Add your error to the list and keep
going!!!
*WARNING:* make sure that the testing suite actually tests your method via remote
execution once you've gotten all the tests passing. Aka - if the testing suite
doesn't have ANY matching argument permutations for your method, then you're
literally creating a bunch of unit tests that do absolutely nothing. If this is the
case, then ADD MORE ARGUMENT TYPES TO THE TESTING SUITE so that your argument
gets run via remote execution. DO NOT CLOSE THIS ISSUE until you can verify that
torch.Tensor.bmm is actually executed remotely inside of a unit tests (and not
skipped). Aka - at least one of the test_all_allowlisted_tensor_methods_work_remotely_on_all_types
unit tests with your method should run ALL THE WAY TO THE END (instead of skipping
the last part.)
*Note:* adding another argument type might require some serialization work if
we don't support arguments of that type yet. If so, this is your job to add it
to the protobuf files in order to close this issue!
### Reason 2 - torch.Tensor.bmm returns a non-supported type
If this happens, you've got a little bit of work in front of you. We don't have
pointer objects to very many remote object types. So, if your method returns anything
other than a single tensor, you probably need to add support for the type it returns
(Such as a bool, None, int, or other types).
*IMPORTANT:* do NOT return the value itself to the end user!!! Return a pointer object
to that type!
*NOTE:* at the time of writing - there are several core pieces of Syft not yet working
to allow you to return any type other than a torch tensor. If you're not comfortable
investigating what those might be - skip this issue and try again later once
someone else has solved these issues.
### Reason 3 - There's something else broken
Chase those stack traces! Talk to friends in Slack. Look at how other methods are supported.
This is a challenging project in a fast moving codebase!
And don't forget - if this project seems to complex - there are plenty of others that
might be easier.
|
2.0
|
Add torch.Tensor.bmm to allowlist and test suite -
# Description
This issue is a part of Syft 0.3.0 Epic 2: https://github.com/OpenMined/PySyft/issues/3696
In this issue, you will be adding support for remote execution of the torch.Tensor.bmm
method or property. This might be a really small project (literally a one-liner) or
it might require adding significant functionality to PySyft OR to the testing suite
in order to make sure the feature is both functional and tested.
## Step 0: Run tests and ./scripts/pre_commit.sh
Before you get started with this project, let's make sure you have everything building and testing
correctly. Clone the codebase and run:
```pip uninstall syft```
followed by
```pip install -e .```
Then run the pre-commit file (which will also run the tests)
```./scripts/pre_commit.sh```
If all of these tests pass, continue on. If not, make sure you have all the
dependencies in requirements.txt installed, etc.
## Step 1: Uncomment your method in the allowlist.py file
Inside [allowlist.py](https://github.com/OpenMined/PySyft/blob/syft_0.3.0/src/syft/lib/torch/allowlist.py) you will find a huge dictionary of methods. Find your method and uncomment the line its on. At the time
of writing this Issue (WARNING: THIS MAY HAVE CHANGED) the dictionary maps from the
string name of the method (in your case 'torch.Tensor.bmm') to the string representation
of the type the method returns.
## Step 2: Run Unit Tests
Run the following:
```python setup.py test```
And wait to see if some of the tests fail. Why might the tests fail now? I'm so glad you asked!
https://github.com/OpenMined/PySyft/blob/syft_0.3.0/tests/syft/lib/torch/tensor/tensor_remote_method_api_suite_test.py
In this file you'll find the torch method test suite. It AUTOMATICALLY loads all methods
from the allowlist.py file you modified in the previous step. It attempts to test them.
# Step 3: If you get a Failing Test
If you get a failing test, this could be for one of a few reasons:
### Reason 1 - The testing suite passed in non-compatible arguments
The testing suite is pretty dumb. It literally just has a permutation of possible
arguments to pass into every method on torch tensors. So, if one of those permutations
doesn't work for your method (aka... perhaps it tries to call your method without
any arguments but torch.Tensor.bmm actually requires some) then the test will
fail if the error hasn't been seen before.
If this happens - don't worry! Just look inside the only test in that file and look
for the huge lists of error types to ignore. Add your error to the list and keep
going!!!
*WARNING:* make sure that the testing suite actually tests your method via remote
execution once you've gotten all the tests passing. Aka - if the testing suite
doesn't have ANY matching argument permutations for your method, then you're
literally creating a bunch of unit tests that do absolutely nothing. If this is the
case, then ADD MORE ARGUMENT TYPES TO THE TESTING SUITE so that your argument
gets run via remote execution. DO NOT CLOSE THIS ISSUE until you can verify that
torch.Tensor.bmm is actually executed remotely inside of a unit tests (and not
skipped). Aka - at least one of the test_all_allowlisted_tensor_methods_work_remotely_on_all_types
unit tests with your method should run ALL THE WAY TO THE END (instead of skipping
the last part.)
*Note:* adding another argument type might require some serialization work if
we don't support arguments of that type yet. If so, this is your job to add it
to the protobuf files in order to close this issue!
### Reason 2 - torch.Tensor.bmm returns a non-supported type
If this happens, you've got a little bit of work in front of you. We don't have
pointer objects to very many remote object types. So, if your method returns anything
other than a single tensor, you probably need to add support for the type it returns
(Such as a bool, None, int, or other types).
*IMPORTANT:* do NOT return the value itself to the end user!!! Return a pointer object
to that type!
*NOTE:* at the time of writing - there are several core pieces of Syft not yet working
to allow you to return any type other than a torch tensor. If you're not comfortable
investigating what those might be - skip this issue and try again later once
someone else has solved these issues.
### Reason 3 - There's something else broken
Chase those stack traces! Talk to friends in Slack. Look at how other methods are supported.
This is a challenging project in a fast moving codebase!
And don't forget - if this project seems to complex - there are plenty of others that
might be easier.
|
test
|
add torch tensor bmm to allowlist and test suite description this issue is a part of syft epic in this issue you will be adding support for remote execution of the torch tensor bmm method or property this might be a really small project literally a one liner or it might require adding significant functionality to pysyft or to the testing suite in order to make sure the feature is both functional and tested step run tests and scripts pre commit sh before you get started with this project let s make sure you have everything building and testing correctly clone the codebase and run pip uninstall syft followed by pip install e then run the pre commit file which will also run the tests scripts pre commit sh if all of these tests pass continue on if not make sure you have all the dependencies in requirements txt installed etc step uncomment your method in the allowlist py file inside you will find a huge dictionary of methods find your method and uncomment the line its on at the time of writing this issue warning this may have changed the dictionary maps from the string name of the method in your case torch tensor bmm to the string representation of the type the method returns step run unit tests run the following python setup py test and wait to see if some of the tests fail why might the tests fail now i m so glad you asked in this file you ll find the torch method test suite it automatically loads all methods from the allowlist py file you modified in the previous step it attempts to test them step if you get a failing test if you get a failing test this could be for one of a few reasons reason the testing suite passed in non compatible arguments the testing suite is pretty dumb it literally just has a permutation of possible arguments to pass into every method on torch tensors so if one of those permutations doesn t work for your method aka perhaps it tries to call your method without any arguments but torch tensor bmm actually requires some then the test will fail if the error hasn t been seen before if this happens don t worry just look inside the only test in that file and look for the huge lists of error types to ignore add your error to the list and keep going warning make sure that the testing suite actually tests your method via remote execution once you ve gotten all the tests passing aka if the testing suite doesn t have any matching argument permutations for your method then you re literally creating a bunch of unit tests that do absolutely nothing if this is the case then add more argument types to the testing suite so that your argument gets run via remote execution do not close this issue until you can verify that torch tensor bmm is actually executed remotely inside of a unit tests and not skipped aka at least one of the test all allowlisted tensor methods work remotely on all types unit tests with your method should run all the way to the end instead of skipping the last part note adding another argument type might require some serialization work if we don t support arguments of that type yet if so this is your job to add it to the protobuf files in order to close this issue reason torch tensor bmm returns a non supported type if this happens you ve got a little bit of work in front of you we don t have pointer objects to very many remote object types so if your method returns anything other than a single tensor you probably need to add support for the type it returns such as a bool none int or other types important do not return the value itself to the end user return a pointer object to that type note at the time of writing there are several core pieces of syft not yet working to allow you to return any type other than a torch tensor if you re not comfortable investigating what those might be skip this issue and try again later once someone else has solved these issues reason there s something else broken chase those stack traces talk to friends in slack look at how other methods are supported this is a challenging project in a fast moving codebase and don t forget if this project seems to complex there are plenty of others that might be easier
| 1
|
278,937
| 24,186,752,595
|
IssuesEvent
|
2022-09-23 13:55:17
|
WeCanWebserv/Webserv
|
https://api.github.com/repos/WeCanWebserv/Webserv
|
closed
|
[TEST] Parser, Request, Response 연결하여 siege 부하 테스트
|
feat test
|
## Description
- GET 요청에 대한 부하 테스트
## TO DO
- [ ] ...
|
1.0
|
[TEST] Parser, Request, Response 연결하여 siege 부하 테스트 - ## Description
- GET 요청에 대한 부하 테스트
## TO DO
- [ ] ...
|
test
|
parser request response 연결하여 siege 부하 테스트 description get 요청에 대한 부하 테스트 to do
| 1
|
231,593
| 18,780,575,255
|
IssuesEvent
|
2021-11-08 05:51:27
|
microsoft/AzureStorageExplorer
|
https://api.github.com/repos/microsoft/AzureStorageExplorer
|
closed
|
It would be better to disable the action 'Clone and Rehydrate…' when selecting an archived blob and a folder
|
🧪 testing :gear: blobs
|
**Storage Explorer Version:** 1.22.0-dev
**Build Number:** 20211102.7
**Branch:** main
**Platform/OS:** Windows 10/Linux Ubuntu 20.04/MacOS Big Sur 11.5
**Architecture:** ia32\x64
**How Found:** Ad-hoc testing
**Regression From:** Not a regression
## Bug Description ##
An error occurs when executing the action 'Clone and Rehydrate…' if selecting an archived blob and a folder, and this action is disabled when selecting two archived blobs/one folder.
## Steps to Reproduce ##
1. Expand one non-ADLS Gen2 storage account -> Blob Containers.
2. Create a blob container -> Upload one blob -> Change the blob's access tier to 'Archive'.
3. Create a new folder -> Upload a blob to it.
4. Click 'Back -> Select All -> Select All in Page' -> Right click them.
5. Check whether the action 'Clone and Rehydrate…' is disabled.
## Expected Experience ##
The action 'Clone and Rehydrate…' is disabled.
## Actual Experience ##
The action 'Clone and Rehydrate…' is enabled.
## Additional Context ##
1. An error occurs when executing the action 'Clone and Rehydrate…'.
2. Error details:
```
"name": "RestError",
"message": "The specified blob does not exist.\n."
```
|
1.0
|
It would be better to disable the action 'Clone and Rehydrate…' when selecting an archived blob and a folder - **Storage Explorer Version:** 1.22.0-dev
**Build Number:** 20211102.7
**Branch:** main
**Platform/OS:** Windows 10/Linux Ubuntu 20.04/MacOS Big Sur 11.5
**Architecture:** ia32\x64
**How Found:** Ad-hoc testing
**Regression From:** Not a regression
## Bug Description ##
An error occurs when executing the action 'Clone and Rehydrate…' if selecting an archived blob and a folder, and this action is disabled when selecting two archived blobs/one folder.
## Steps to Reproduce ##
1. Expand one non-ADLS Gen2 storage account -> Blob Containers.
2. Create a blob container -> Upload one blob -> Change the blob's access tier to 'Archive'.
3. Create a new folder -> Upload a blob to it.
4. Click 'Back -> Select All -> Select All in Page' -> Right click them.
5. Check whether the action 'Clone and Rehydrate…' is disabled.
## Expected Experience ##
The action 'Clone and Rehydrate…' is disabled.
## Actual Experience ##
The action 'Clone and Rehydrate…' is enabled.
## Additional Context ##
1. An error occurs when executing the action 'Clone and Rehydrate…'.
2. Error details:
```
"name": "RestError",
"message": "The specified blob does not exist.\n."
```
|
test
|
it would be better to disable the action clone and rehydrate… when selecting an archived blob and a folder storage explorer version dev build number branch main platform os windows linux ubuntu macos big sur architecture how found ad hoc testing regression from not a regression bug description an error occurs when executing the action clone and rehydrate… if selecting an archived blob and a folder and this action is disabled when selecting two archived blobs one folder steps to reproduce expand one non adls storage account blob containers create a blob container upload one blob change the blob s access tier to archive create a new folder upload a blob to it click back select all select all in page right click them check whether the action clone and rehydrate… is disabled expected experience the action clone and rehydrate… is disabled actual experience the action clone and rehydrate… is enabled additional context an error occurs when executing the action clone and rehydrate… error details name resterror message the specified blob does not exist n
| 1
|
88,091
| 11,031,709,148
|
IssuesEvent
|
2019-12-06 18:23:55
|
napari/napari
|
https://api.github.com/repos/napari/napari
|
closed
|
Display total number of slices on right end of corresponding slider
|
design feature
|
## 🚀 Feature
From my colleague @VolkerH who was trying out napari on his (oddly-shaped due to IO issues) data: it would be nice if the max value of each slider was shown e.g. at the right end of that slider, so that you could at a glance tell the shape of your data.
|
1.0
|
Display total number of slices on right end of corresponding slider - ## 🚀 Feature
From my colleague @VolkerH who was trying out napari on his (oddly-shaped due to IO issues) data: it would be nice if the max value of each slider was shown e.g. at the right end of that slider, so that you could at a glance tell the shape of your data.
|
non_test
|
display total number of slices on right end of corresponding slider 🚀 feature from my colleague volkerh who was trying out napari on his oddly shaped due to io issues data it would be nice if the max value of each slider was shown e g at the right end of that slider so that you could at a glance tell the shape of your data
| 0
|
145,591
| 5,578,364,376
|
IssuesEvent
|
2017-03-28 12:13:28
|
w3c/wai-people-use-web
|
https://api.github.com/repos/w3c/wai-people-use-web
|
closed
|
[Browsing] Audio Descriptions
|
High Priority
|
From Judy Brewer:
> "Audio Descriptions" is also referred to as "Video Description" and "Described Video." I suggest listing the alternates in parentheses.
|
1.0
|
[Browsing] Audio Descriptions - From Judy Brewer:
> "Audio Descriptions" is also referred to as "Video Description" and "Described Video." I suggest listing the alternates in parentheses.
|
non_test
|
audio descriptions from judy brewer audio descriptions is also referred to as video description and described video i suggest listing the alternates in parentheses
| 0
|
111,898
| 17,048,557,706
|
IssuesEvent
|
2021-07-06 05:28:29
|
vishalgoyal16444/mslearn-tailspin-spacegame-web
|
https://api.github.com/repos/vishalgoyal16444/mslearn-tailspin-spacegame-web
|
opened
|
CVE-2018-19838 (Medium) detected in node-sass-4.14.1.tgz, node-sass3.5.5
|
security vulnerability
|
## CVE-2018-19838 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>node-sass-4.14.1.tgz</b>, <b>node-sass3.5.5</b></p></summary>
<p>
<details><summary><b>node-sass-4.14.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz</a></p>
<p>Path to dependency file: mslearn-tailspin-spacegame-web/package.json</p>
<p>Path to vulnerable library: mslearn-tailspin-spacegame-web/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.14.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/vishalgoyal16444/mslearn-tailspin-spacegame-web/commit/9dc0cb3749919e1417005d8857fa536e6b1e0d2f">9dc0cb3749919e1417005d8857fa536e6b1e0d2f</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In LibSass prior to 3.5.5, functions inside ast.cpp for IMPLEMENT_AST_OPERATORS expansion allow attackers to cause a denial-of-service resulting from stack consumption via a crafted sass file, as demonstrated by recursive calls involving clone(), cloneChildren(), and copy().
<p>Publish Date: 2018-12-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19838>CVE-2018-19838</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/sass/libsass/issues/2660">https://github.com/sass/libsass/issues/2660</a></p>
<p>Release Date: 2018-12-04</p>
<p>Fix Resolution: libsass - 3.6.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2018-19838 (Medium) detected in node-sass-4.14.1.tgz, node-sass3.5.5 - ## CVE-2018-19838 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>node-sass-4.14.1.tgz</b>, <b>node-sass3.5.5</b></p></summary>
<p>
<details><summary><b>node-sass-4.14.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz</a></p>
<p>Path to dependency file: mslearn-tailspin-spacegame-web/package.json</p>
<p>Path to vulnerable library: mslearn-tailspin-spacegame-web/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.14.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/vishalgoyal16444/mslearn-tailspin-spacegame-web/commit/9dc0cb3749919e1417005d8857fa536e6b1e0d2f">9dc0cb3749919e1417005d8857fa536e6b1e0d2f</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In LibSass prior to 3.5.5, functions inside ast.cpp for IMPLEMENT_AST_OPERATORS expansion allow attackers to cause a denial-of-service resulting from stack consumption via a crafted sass file, as demonstrated by recursive calls involving clone(), cloneChildren(), and copy().
<p>Publish Date: 2018-12-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19838>CVE-2018-19838</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/sass/libsass/issues/2660">https://github.com/sass/libsass/issues/2660</a></p>
<p>Release Date: 2018-12-04</p>
<p>Fix Resolution: libsass - 3.6.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve medium detected in node sass tgz node cve medium severity vulnerability vulnerable libraries node sass tgz node node sass tgz wrapper around libsass library home page a href path to dependency file mslearn tailspin spacegame web package json path to vulnerable library mslearn tailspin spacegame web node modules node sass package json dependency hierarchy x node sass tgz vulnerable library found in head commit a href found in base branch master vulnerability details in libsass prior to functions inside ast cpp for implement ast operators expansion allow attackers to cause a denial of service resulting from stack consumption via a crafted sass file as demonstrated by recursive calls involving clone clonechildren and copy publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope 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 libsass step up your open source security game with whitesource
| 0
|
297,643
| 25,750,320,199
|
IssuesEvent
|
2022-12-08 12:47:44
|
sourcegraph/sourcegraph
|
https://api.github.com/repos/sourcegraph/sourcegraph
|
closed
|
Scaletesting: [IAM] Reproducing an existing customer environment to hunt bugs
|
team/devx team/iam devx/q3b1/scaletesting devx/q3b1/scaletesting/testing-data devx/q3b1/scaletesting/teams devx/q4b1/scaletesting
|
- In order to reproduce _customer_ issues, we need to have:
- [x] #43051
- [x] #43052
/cc @sourcegraph/iam
|
5.0
|
Scaletesting: [IAM] Reproducing an existing customer environment to hunt bugs - - In order to reproduce _customer_ issues, we need to have:
- [x] #43051
- [x] #43052
/cc @sourcegraph/iam
|
test
|
scaletesting reproducing an existing customer environment to hunt bugs in order to reproduce customer issues we need to have cc sourcegraph iam
| 1
|
41,942
| 12,865,412,613
|
IssuesEvent
|
2020-07-10 00:13:45
|
Watemlifts/redash
|
https://api.github.com/repos/Watemlifts/redash
|
opened
|
CVE-2019-14862 (Medium) detected in knockout-min-3.2.0.js
|
security vulnerability
|
## CVE-2019-14862 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>knockout-min-3.2.0.js</b></p></summary>
<p>Knockout makes it easier to create rich, responsive UIs with JavaScript</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/knockout/3.2.0/knockout-min.js">https://cdnjs.cloudflare.com/ajax/libs/knockout/3.2.0/knockout-min.js</a></p>
<p>Path to dependency file: /tmp/ws-scm/redash/node_modules/gridstack/demo/rtl.html</p>
<p>Path to vulnerable library: /redash/node_modules/gridstack/demo/rtl.html</p>
<p>
Dependency Hierarchy:
- :x: **knockout-min-3.2.0.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Watemlifts/redash/commit/909e24bab5278add575ba347a005348ae6c8a711">909e24bab5278add575ba347a005348ae6c8a711</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
There is a vulnerability in knockout before version 3.5.0-beta, where after escaping the context of the web application, the web application delivers data to its users along with other trusted dynamic content, without validating it.
<p>Publish Date: 2020-01-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14862>CVE-2019-14862</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/knockout/knockout/tree/v3.5.0-rc">https://github.com/knockout/knockout/tree/v3.5.0-rc</a></p>
<p>Release Date: 2020-01-02</p>
<p>Fix Resolution: v3.5.0-rc</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2019-14862 (Medium) detected in knockout-min-3.2.0.js - ## CVE-2019-14862 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>knockout-min-3.2.0.js</b></p></summary>
<p>Knockout makes it easier to create rich, responsive UIs with JavaScript</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/knockout/3.2.0/knockout-min.js">https://cdnjs.cloudflare.com/ajax/libs/knockout/3.2.0/knockout-min.js</a></p>
<p>Path to dependency file: /tmp/ws-scm/redash/node_modules/gridstack/demo/rtl.html</p>
<p>Path to vulnerable library: /redash/node_modules/gridstack/demo/rtl.html</p>
<p>
Dependency Hierarchy:
- :x: **knockout-min-3.2.0.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Watemlifts/redash/commit/909e24bab5278add575ba347a005348ae6c8a711">909e24bab5278add575ba347a005348ae6c8a711</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
There is a vulnerability in knockout before version 3.5.0-beta, where after escaping the context of the web application, the web application delivers data to its users along with other trusted dynamic content, without validating it.
<p>Publish Date: 2020-01-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14862>CVE-2019-14862</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/knockout/knockout/tree/v3.5.0-rc">https://github.com/knockout/knockout/tree/v3.5.0-rc</a></p>
<p>Release Date: 2020-01-02</p>
<p>Fix Resolution: v3.5.0-rc</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve medium detected in knockout min js cve medium severity vulnerability vulnerable library knockout min js knockout makes it easier to create rich responsive uis with javascript library home page a href path to dependency file tmp ws scm redash node modules gridstack demo rtl html path to vulnerable library redash node modules gridstack demo rtl html dependency hierarchy x knockout min js vulnerable library found in head commit a href vulnerability details there is a vulnerability in knockout before version beta where after escaping the context of the web application the web application delivers data to its users along with other trusted dynamic content without validating it publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rc step up your open source security game with whitesource
| 0
|
17,280
| 23,077,976,594
|
IssuesEvent
|
2022-07-26 02:52:54
|
maticnetwork/miden
|
https://api.github.com/repos/maticnetwork/miden
|
closed
|
Remove `EQW` instruction set from the VM and emulate it using other instruction in assembly
|
assembly instruction set processor
|
Theoretically, we can afford operations which is of degree 5, but @bobbinth feels it's not worth it for `EQW`.
Therefore this issue can be broken down into 3 separate task:
- Remove `EQW` instruction from the VM.
- Emulate `EQW` operation using other VM instruction in the assembly.
- Update the docs/ cycle count of the impacted operations.
|
1.0
|
Remove `EQW` instruction set from the VM and emulate it using other instruction in assembly - Theoretically, we can afford operations which is of degree 5, but @bobbinth feels it's not worth it for `EQW`.
Therefore this issue can be broken down into 3 separate task:
- Remove `EQW` instruction from the VM.
- Emulate `EQW` operation using other VM instruction in the assembly.
- Update the docs/ cycle count of the impacted operations.
|
non_test
|
remove eqw instruction set from the vm and emulate it using other instruction in assembly theoretically we can afford operations which is of degree but bobbinth feels it s not worth it for eqw therefore this issue can be broken down into separate task remove eqw instruction from the vm emulate eqw operation using other vm instruction in the assembly update the docs cycle count of the impacted operations
| 0
|
42,766
| 5,474,690,383
|
IssuesEvent
|
2017-03-11 02:34:29
|
perl6/whateverable
|
https://api.github.com/repos/perl6/whateverable
|
closed
|
Allow comma to separate custom good and bad revisions
|
bisectable LHF testneeded
|
See this: http://irclog.perlgeek.de/perl6/2016-09-09#i_13180322
It did not understand the query because there is a comma. It does say which starting points it is using, so it is transparent enough and in theory the user should be able to spot the issue. But there is no reason we cannot accept a comma as well.
|
1.0
|
Allow comma to separate custom good and bad revisions - See this: http://irclog.perlgeek.de/perl6/2016-09-09#i_13180322
It did not understand the query because there is a comma. It does say which starting points it is using, so it is transparent enough and in theory the user should be able to spot the issue. But there is no reason we cannot accept a comma as well.
|
test
|
allow comma to separate custom good and bad revisions see this it did not understand the query because there is a comma it does say which starting points it is using so it is transparent enough and in theory the user should be able to spot the issue but there is no reason we cannot accept a comma as well
| 1
|
349,805
| 31,832,446,124
|
IssuesEvent
|
2023-09-14 11:30:51
|
mantidproject/mantid
|
https://api.github.com/repos/mantidproject/mantid
|
opened
|
Algorithm help opens behind algorithm dialog
|
Bug macOS Only ISIS Team: Core Linux Only Manual Tests
|
**Describe the bug**
When clicking the help button on an algorithm dialog, the help window opens behind the algorithm dialog. Appears to be only the algorithm help on Linux.
**To Reproduce**
On Linux, open an algorithm dialog and click the help button.
**Expected behavior**
Should open on top.
**Platform/Version (please complete the following information):**
- OS: Linux, macOS
- Mantid Version: was present in 6.7
|
1.0
|
Algorithm help opens behind algorithm dialog - **Describe the bug**
When clicking the help button on an algorithm dialog, the help window opens behind the algorithm dialog. Appears to be only the algorithm help on Linux.
**To Reproduce**
On Linux, open an algorithm dialog and click the help button.
**Expected behavior**
Should open on top.
**Platform/Version (please complete the following information):**
- OS: Linux, macOS
- Mantid Version: was present in 6.7
|
test
|
algorithm help opens behind algorithm dialog describe the bug when clicking the help button on an algorithm dialog the help window opens behind the algorithm dialog appears to be only the algorithm help on linux to reproduce on linux open an algorithm dialog and click the help button expected behavior should open on top platform version please complete the following information os linux macos mantid version was present in
| 1
|
25,355
| 4,306,653,898
|
IssuesEvent
|
2016-07-21 04:47:46
|
kraigs-android/kraigsandroid
|
https://api.github.com/repos/kraigs-android/kraigsandroid
|
closed
|
Keyboard doesn't work correctly in time dialog
|
auto-migrated Priority-Medium Type-Defect
|
```
The keyboard entry functionality in the time dialog is fairly broken. Replace
it with something better.
One bug report:
I think i found a bug, when you go to make a new alarm, the screen pops out and
you click on the minutes field to set it by the keyboard instead of using the
+/- buttons, when finished you press the back bitton to remove the keyboard
with digits and press OK button to confirm the alarm, the minutes dont change
to the new time you have changed, but stay as before to the current that had
been when you pressed 'new alarm'.
```
Original issue reported on code.google.com by `kraigs.a...@gmail.com` on 11 Aug 2010 at 2:02
|
1.0
|
Keyboard doesn't work correctly in time dialog - ```
The keyboard entry functionality in the time dialog is fairly broken. Replace
it with something better.
One bug report:
I think i found a bug, when you go to make a new alarm, the screen pops out and
you click on the minutes field to set it by the keyboard instead of using the
+/- buttons, when finished you press the back bitton to remove the keyboard
with digits and press OK button to confirm the alarm, the minutes dont change
to the new time you have changed, but stay as before to the current that had
been when you pressed 'new alarm'.
```
Original issue reported on code.google.com by `kraigs.a...@gmail.com` on 11 Aug 2010 at 2:02
|
non_test
|
keyboard doesn t work correctly in time dialog the keyboard entry functionality in the time dialog is fairly broken replace it with something better one bug report i think i found a bug when you go to make a new alarm the screen pops out and you click on the minutes field to set it by the keyboard instead of using the buttons when finished you press the back bitton to remove the keyboard with digits and press ok button to confirm the alarm the minutes dont change to the new time you have changed but stay as before to the current that had been when you pressed new alarm original issue reported on code google com by kraigs a gmail com on aug at
| 0
|
262,507
| 22,908,343,115
|
IssuesEvent
|
2022-07-16 00:17:59
|
godotengine/godot
|
https://api.github.com/repos/godotengine/godot
|
closed
|
Godot 4.0 doesn't allow us to edit label color
|
needs testing topic:gui
|
### Godot version
4.0 alpha 11
### System information
KDE neon 5.25
### Issue description
You can't change the color of a label in a theme.
### Steps to reproduce
- Create a theme resource
- Add label
- Goto color tab and see there is nothing.
### Minimal reproduction project
[AstroWars.zip](https://github.com/godotengine/godot/files/9124034/AstroWars.zip)
|
1.0
|
Godot 4.0 doesn't allow us to edit label color - ### Godot version
4.0 alpha 11
### System information
KDE neon 5.25
### Issue description
You can't change the color of a label in a theme.
### Steps to reproduce
- Create a theme resource
- Add label
- Goto color tab and see there is nothing.
### Minimal reproduction project
[AstroWars.zip](https://github.com/godotengine/godot/files/9124034/AstroWars.zip)
|
test
|
godot doesn t allow us to edit label color godot version alpha system information kde neon issue description you can t change the color of a label in a theme steps to reproduce create a theme resource add label goto color tab and see there is nothing minimal reproduction project
| 1
|
9,520
| 12,499,511,769
|
IssuesEvent
|
2020-06-01 20:18:21
|
googleapis/google-cloud-cpp
|
https://api.github.com/repos/googleapis/google-cloud-cpp
|
closed
|
Update README.md in old repo to say the project moved
|
api: spanner type: process
|
Update README.md in the OLD repo to LOUDLY document the new location for the code. (is there any type of redirect we can/should put up here?)
|
1.0
|
Update README.md in old repo to say the project moved - Update README.md in the OLD repo to LOUDLY document the new location for the code. (is there any type of redirect we can/should put up here?)
|
non_test
|
update readme md in old repo to say the project moved update readme md in the old repo to loudly document the new location for the code is there any type of redirect we can should put up here
| 0
|
791,100
| 27,850,420,392
|
IssuesEvent
|
2023-03-20 18:14:58
|
KinsonDigital/Velaptor
|
https://api.github.com/repos/KinsonDigital/Velaptor
|
closed
|
🚧Remove dependabot
|
♻️cicd medium priority preview
|
### Complete The Item Below
- [X] I have updated the title without removing the 🚧 emoji.
### Description
The organization plans to use another service, so dependabot.yml needs to be removed from all repos in the organization.
### Acceptance Criteria
- [ ] dependabot.yml removed
### ToDo Items
- [X] Change type labels added to this issue. Refer to the _**Change Type Labels**_ section below.
- [X] Priority label added to this issue. Refer to the _**Priority Type Labels**_ section below.
- [X] Issue linked to the correct project _(if applicable)_.
- [X] Issue linked to the correct milestone _(if applicable)_.
- [x] Draft pull request created and linked to this issue _(only required with code changes)_.
### Issue Dependencies
_No response_
### Related Work
_No response_
### Additional Information:
**_<details closed><summary>Change Type Labels</summary>_**
| Change Type | Label |
|---------------------|----------------------|
| Bug Fixes | `🐛bug` |
| Breaking Changes | `🧨breaking changes` |
| New Feature | `✨new feature` |
| CICD Changes | `♻️cicd` |
| Code Doc Changes | `🗒️documentation/code` |
| Product Doc Changes | `📝documentation/product` |
</details>
**_<details closed><summary>Priority Type Labels</summary>_**
| Priority Type | Label |
|---------------------|-------------------|
| Low Priority | `low priority` |
| Medium Priority | `medium priority` |
| High Priority | `high priority` |
</details>
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct.
|
1.0
|
🚧Remove dependabot - ### Complete The Item Below
- [X] I have updated the title without removing the 🚧 emoji.
### Description
The organization plans to use another service, so dependabot.yml needs to be removed from all repos in the organization.
### Acceptance Criteria
- [ ] dependabot.yml removed
### ToDo Items
- [X] Change type labels added to this issue. Refer to the _**Change Type Labels**_ section below.
- [X] Priority label added to this issue. Refer to the _**Priority Type Labels**_ section below.
- [X] Issue linked to the correct project _(if applicable)_.
- [X] Issue linked to the correct milestone _(if applicable)_.
- [x] Draft pull request created and linked to this issue _(only required with code changes)_.
### Issue Dependencies
_No response_
### Related Work
_No response_
### Additional Information:
**_<details closed><summary>Change Type Labels</summary>_**
| Change Type | Label |
|---------------------|----------------------|
| Bug Fixes | `🐛bug` |
| Breaking Changes | `🧨breaking changes` |
| New Feature | `✨new feature` |
| CICD Changes | `♻️cicd` |
| Code Doc Changes | `🗒️documentation/code` |
| Product Doc Changes | `📝documentation/product` |
</details>
**_<details closed><summary>Priority Type Labels</summary>_**
| Priority Type | Label |
|---------------------|-------------------|
| Low Priority | `low priority` |
| Medium Priority | `medium priority` |
| High Priority | `high priority` |
</details>
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct.
|
non_test
|
🚧remove dependabot complete the item below i have updated the title without removing the 🚧 emoji description the organization plans to use another service so dependabot yml needs to be removed from all repos in the organization acceptance criteria dependabot yml removed todo items change type labels added to this issue refer to the change type labels section below priority label added to this issue refer to the priority type labels section below issue linked to the correct project if applicable issue linked to the correct milestone if applicable draft pull request created and linked to this issue only required with code changes issue dependencies no response related work no response additional information change type labels change type label bug fixes 🐛bug breaking changes 🧨breaking changes new feature ✨new feature cicd changes ♻️cicd code doc changes 🗒️documentation code product doc changes 📝documentation product priority type labels priority type label low priority low priority medium priority medium priority high priority high priority code of conduct i agree to follow this project s code of conduct
| 0
|
35,461
| 7,953,503,423
|
IssuesEvent
|
2018-07-12 01:58:49
|
IQSS/dataverse
|
https://api.github.com/repos/IQSS/dataverse
|
closed
|
Standard Naming of DvObject types
|
Feature: Code Infrastructure Type: Suggestion
|
The project has 4 different naming conventions for the same object types. Even if the number of naming conventions is not reduced, static variables should be used across the project. (It would help to cut it to 2 or at least 3 naming conventions)
It is easy to make programming errors when comparing objects types across postgres, solr results, etc.
| Postgres dtype (db value and DvObject.java) | Solr Index Names (SearchConstants.java) | Search API (SearchConstants.java) | Web UI as facets (SearchConstants.java) |
| --- | --- | --- | --- |
| Dataverse | dataverses | dataverse | Dataverses |
| Dataset | datasets | dataset | Datasets |
| DataFile | files | file | Files |
Note: In addition, the static variables for the strings above are not always used. Ther are many instances of simply using strings.
This is a side effect of the 'rapid development' in the winter
### Some examples of using strings
Dataverses.java
``` java
jab.add( Json.createObjectBuilder().add("type", "dataverse")
```
Index.java
``` java
if (type.equals("dataverses")) {
```
DataTagsAPI.java
``` java
JsonObject jsonInfo = endpoint.queryParam("repositoryName", "Dataverse")
```
IndexServiceBean.java
``` java
solrInputDocument.addField(SearchFields.TYPE, "dataverses");
```
SearchServiceBean.java
``` java
if (type.equals("dataverses")) {
```
(etc, etc, etc)
|
1.0
|
Standard Naming of DvObject types - The project has 4 different naming conventions for the same object types. Even if the number of naming conventions is not reduced, static variables should be used across the project. (It would help to cut it to 2 or at least 3 naming conventions)
It is easy to make programming errors when comparing objects types across postgres, solr results, etc.
| Postgres dtype (db value and DvObject.java) | Solr Index Names (SearchConstants.java) | Search API (SearchConstants.java) | Web UI as facets (SearchConstants.java) |
| --- | --- | --- | --- |
| Dataverse | dataverses | dataverse | Dataverses |
| Dataset | datasets | dataset | Datasets |
| DataFile | files | file | Files |
Note: In addition, the static variables for the strings above are not always used. Ther are many instances of simply using strings.
This is a side effect of the 'rapid development' in the winter
### Some examples of using strings
Dataverses.java
``` java
jab.add( Json.createObjectBuilder().add("type", "dataverse")
```
Index.java
``` java
if (type.equals("dataverses")) {
```
DataTagsAPI.java
``` java
JsonObject jsonInfo = endpoint.queryParam("repositoryName", "Dataverse")
```
IndexServiceBean.java
``` java
solrInputDocument.addField(SearchFields.TYPE, "dataverses");
```
SearchServiceBean.java
``` java
if (type.equals("dataverses")) {
```
(etc, etc, etc)
|
non_test
|
standard naming of dvobject types the project has different naming conventions for the same object types even if the number of naming conventions is not reduced static variables should be used across the project it would help to cut it to or at least naming conventions it is easy to make programming errors when comparing objects types across postgres solr results etc postgres dtype db value and dvobject java solr index names searchconstants java search api searchconstants java web ui as facets searchconstants java dataverse dataverses dataverse dataverses dataset datasets dataset datasets datafile files file files note in addition the static variables for the strings above are not always used ther are many instances of simply using strings this is a side effect of the rapid development in the winter some examples of using strings dataverses java java jab add json createobjectbuilder add type dataverse index java java if type equals dataverses datatagsapi java java jsonobject jsoninfo endpoint queryparam repositoryname dataverse indexservicebean java java solrinputdocument addfield searchfields type dataverses searchservicebean java java if type equals dataverses etc etc etc
| 0
|
77,710
| 7,600,621,134
|
IssuesEvent
|
2018-04-28 04:16:26
|
Microsoft/vsts-tasks
|
https://api.github.com/repos/Microsoft/vsts-tasks
|
closed
|
Starting Http listener in VS Test fails with AccessDenied
|
Area: Test
|
We have a test which brings up a Owin Selfhost. The test fails with access denied when running it through the VS Test Task.
Error message
Initialization method VolumeResourceManager.Test.VolumeResourceManagerTest.TestSetup threw exception. System.Net.HttpListenerException: Access is denied.
Stack trace
at System.Net.HttpListener.AddAllPrefixes()
at System.Net.HttpListener.Start()
at Microsoft.Owin.Host.HttpListener.OwinHttpListener.Start(HttpListener listener, Func`2 appFunc, IList`1 addresses, IDictionary`2 capabilities, Func`2 loggerFactory)
at Microsoft.Owin.Host.HttpListener.OwinServerFactory.Create(Func`2 app, IDictionary`2 properties)
https://msazure.visualstudio.com/One/Service%20Fabric/_build/index?buildId=12478884&_a=summary&tab=ms.vss-test-web.test-result-details
I am guessing this is because the tests are run with lower privilege. I couldn't find an option in VS Test task to run it with higher privilege. Any idea on how to fix this?
|
1.0
|
Starting Http listener in VS Test fails with AccessDenied - We have a test which brings up a Owin Selfhost. The test fails with access denied when running it through the VS Test Task.
Error message
Initialization method VolumeResourceManager.Test.VolumeResourceManagerTest.TestSetup threw exception. System.Net.HttpListenerException: Access is denied.
Stack trace
at System.Net.HttpListener.AddAllPrefixes()
at System.Net.HttpListener.Start()
at Microsoft.Owin.Host.HttpListener.OwinHttpListener.Start(HttpListener listener, Func`2 appFunc, IList`1 addresses, IDictionary`2 capabilities, Func`2 loggerFactory)
at Microsoft.Owin.Host.HttpListener.OwinServerFactory.Create(Func`2 app, IDictionary`2 properties)
https://msazure.visualstudio.com/One/Service%20Fabric/_build/index?buildId=12478884&_a=summary&tab=ms.vss-test-web.test-result-details
I am guessing this is because the tests are run with lower privilege. I couldn't find an option in VS Test task to run it with higher privilege. Any idea on how to fix this?
|
test
|
starting http listener in vs test fails with accessdenied we have a test which brings up a owin selfhost the test fails with access denied when running it through the vs test task error message initialization method volumeresourcemanager test volumeresourcemanagertest testsetup threw exception system net httplistenerexception access is denied stack trace at system net httplistener addallprefixes at system net httplistener start at microsoft owin host httplistener owinhttplistener start httplistener listener func appfunc ilist addresses idictionary capabilities func loggerfactory at microsoft owin host httplistener owinserverfactory create func app idictionary properties i am guessing this is because the tests are run with lower privilege i couldn t find an option in vs test task to run it with higher privilege any idea on how to fix this
| 1
|
197,844
| 22,607,307,478
|
IssuesEvent
|
2022-06-29 14:14:29
|
elikkatzgit/TestingPOM
|
https://api.github.com/repos/elikkatzgit/TestingPOM
|
opened
|
CVE-2019-18797 (Medium) detected in node-sass-4.12.0.tgz
|
security vulnerability
|
## CVE-2019-18797 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-sass-4.12.0.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.12.0.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.12.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.12.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>dev</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
LibSass 3.6.1 has uncontrolled recursion in Sass::Eval::operator()(Sass::Binary_Expression*) in eval.cpp.
<p>Publish Date: 2019-11-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-18797>CVE-2019-18797</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2019-18797">https://nvd.nist.gov/vuln/detail/CVE-2019-18797</a></p>
<p>Release Date: 2019-11-08</p>
<p>Fix Resolution: 4.14.0</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
|
True
|
CVE-2019-18797 (Medium) detected in node-sass-4.12.0.tgz - ## CVE-2019-18797 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-sass-4.12.0.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.12.0.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.12.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.12.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>dev</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
LibSass 3.6.1 has uncontrolled recursion in Sass::Eval::operator()(Sass::Binary_Expression*) in eval.cpp.
<p>Publish Date: 2019-11-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-18797>CVE-2019-18797</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2019-18797">https://nvd.nist.gov/vuln/detail/CVE-2019-18797</a></p>
<p>Release Date: 2019-11-08</p>
<p>Fix Resolution: 4.14.0</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
|
non_test
|
cve medium detected in node sass tgz cve medium severity vulnerability vulnerable library node sass tgz wrapper around libsass library home page a href path to dependency file package json path to vulnerable library node modules node sass package json dependency hierarchy x node sass tgz vulnerable library found in base branch dev vulnerability details libsass has uncontrolled recursion in sass eval operator sass binary expression in eval cpp publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue
| 0
|
59,237
| 11,951,599,405
|
IssuesEvent
|
2020-04-03 17:10:50
|
samdenty/gqless
|
https://api.github.com/repos/samdenty/gqless
|
closed
|
Quick start not working: "globby not found"
|
bug codegen help wanted
|
I followed the [quickstart](https://gqless.dev/docs/getting-started) in the docs. When trying to run the script to generate the code, I got an error:
```
(node:85825) [MODULE_NOT_FOUND] Error Plugin: @gqless/cli: Cannot find module 'globby'
module: @oclif/config@1.14.0
task: not loading commands, globby not found
plugin: @gqless/cli
```
I was able to work around by running `npm install globby`, but it seems like this should be a dependency of the package itself.
```
"@gqless/cli": "0.0.1-alpha.30"
"gqless": "0.0.1-alpha.28"
```
|
1.0
|
Quick start not working: "globby not found" - I followed the [quickstart](https://gqless.dev/docs/getting-started) in the docs. When trying to run the script to generate the code, I got an error:
```
(node:85825) [MODULE_NOT_FOUND] Error Plugin: @gqless/cli: Cannot find module 'globby'
module: @oclif/config@1.14.0
task: not loading commands, globby not found
plugin: @gqless/cli
```
I was able to work around by running `npm install globby`, but it seems like this should be a dependency of the package itself.
```
"@gqless/cli": "0.0.1-alpha.30"
"gqless": "0.0.1-alpha.28"
```
|
non_test
|
quick start not working globby not found i followed the in the docs when trying to run the script to generate the code i got an error node error plugin gqless cli cannot find module globby module oclif config task not loading commands globby not found plugin gqless cli i was able to work around by running npm install globby but it seems like this should be a dependency of the package itself gqless cli alpha gqless alpha
| 0
|
232,949
| 18,926,377,565
|
IssuesEvent
|
2021-11-17 09:58:57
|
ethereumjs/ethereumjs-monorepo
|
https://api.github.com/repos/ethereumjs/ethereumjs-monorepo
|
opened
|
VM, Tx: Run Code Examples in CI
|
type: tests prio: P4 nice-to-have type: enhancement type: CI package: tx package: vm
|
We have code examples included in various packages. These are somewhat neglected respectively forgotten right now and there is a somewhat higher chance that these break over time with nobody noticing.
This should be changed by adding these examples to CI being run with GitHub actions, optimally in a (somewhat) standardized/unified way, but also without too much custom code on the examples itself (we'll see how it goes).
Following packages contain relevant examples (client + devp2p examples should likely be omitted, too complex, too diverse):
- VM: [examples](https://github.com/ethereumjs/ethereumjs-monorepo/tree/master/packages/vm/examples) folder
- Tx: [examples](https://github.com/ethereumjs/ethereumjs-monorepo/tree/master/packages/tx/examples) folder
Just to mention here: these examples could generally need some love ❤️ and it would make sense to modernize and also think about new relevant (and also: a bit more exciting!) use cases, e.g. creating a L2 tx with the Transaction library, I am sure there will be others. Other libraries like `Block` or `Blockchain` would likely also benefit from a - small - examples collection.
|
1.0
|
VM, Tx: Run Code Examples in CI - We have code examples included in various packages. These are somewhat neglected respectively forgotten right now and there is a somewhat higher chance that these break over time with nobody noticing.
This should be changed by adding these examples to CI being run with GitHub actions, optimally in a (somewhat) standardized/unified way, but also without too much custom code on the examples itself (we'll see how it goes).
Following packages contain relevant examples (client + devp2p examples should likely be omitted, too complex, too diverse):
- VM: [examples](https://github.com/ethereumjs/ethereumjs-monorepo/tree/master/packages/vm/examples) folder
- Tx: [examples](https://github.com/ethereumjs/ethereumjs-monorepo/tree/master/packages/tx/examples) folder
Just to mention here: these examples could generally need some love ❤️ and it would make sense to modernize and also think about new relevant (and also: a bit more exciting!) use cases, e.g. creating a L2 tx with the Transaction library, I am sure there will be others. Other libraries like `Block` or `Blockchain` would likely also benefit from a - small - examples collection.
|
test
|
vm tx run code examples in ci we have code examples included in various packages these are somewhat neglected respectively forgotten right now and there is a somewhat higher chance that these break over time with nobody noticing this should be changed by adding these examples to ci being run with github actions optimally in a somewhat standardized unified way but also without too much custom code on the examples itself we ll see how it goes following packages contain relevant examples client examples should likely be omitted too complex too diverse vm folder tx folder just to mention here these examples could generally need some love ❤️ and it would make sense to modernize and also think about new relevant and also a bit more exciting use cases e g creating a tx with the transaction library i am sure there will be others other libraries like block or blockchain would likely also benefit from a small examples collection
| 1
|
38,326
| 2,845,733,352
|
IssuesEvent
|
2015-05-29 06:27:40
|
GoogleCloudPlatform/kubernetes
|
https://api.github.com/repos/GoogleCloudPlatform/kubernetes
|
closed
|
Block access to link-local addresses from containers by default
|
area/networking area/security priority/P2 team/cluster
|
GCE and AWS expose local metadata servers on a link-local address (169.254.169.254). This compromises isolation of containers from hosts and from the cluster. As with host ports, host networking, host paths, etc., we shouldn't expose these addresses by default. Authorization should be required.
Sadly, Google API clients apparently require metadata access currently, as reported in #8512.
cc @thockin @erictune @evandbrown
|
1.0
|
Block access to link-local addresses from containers by default - GCE and AWS expose local metadata servers on a link-local address (169.254.169.254). This compromises isolation of containers from hosts and from the cluster. As with host ports, host networking, host paths, etc., we shouldn't expose these addresses by default. Authorization should be required.
Sadly, Google API clients apparently require metadata access currently, as reported in #8512.
cc @thockin @erictune @evandbrown
|
non_test
|
block access to link local addresses from containers by default gce and aws expose local metadata servers on a link local address this compromises isolation of containers from hosts and from the cluster as with host ports host networking host paths etc we shouldn t expose these addresses by default authorization should be required sadly google api clients apparently require metadata access currently as reported in cc thockin erictune evandbrown
| 0
|
39,683
| 5,242,157,502
|
IssuesEvent
|
2017-01-31 17:20:52
|
phetsims/color-vision
|
https://api.github.com/repos/phetsims/color-vision
|
opened
|
Automated Testing Build Error (1/31/2017 10:00 AM)
|
type:automated-testing
|
From https://github.com/phetsims/color-vision/commit/40a93ad1d117fd9854865a24185472fc9b7ab7b0
```
Running "eslint:allFiles" (eslint) task
/home/mendeleev/git/color-vision/js/singlebulb/view/SingleBulbScreenView.js
25:3 error Mismatched require statement values, FlashlightWireNode !== StopSignNode require-statement-match
✖ 1 problem (1 error, 0 warnings)
Warning: Task "eslint:allFiles" failed. Use --force to continue.
Aborted due to warnings.
```
|
1.0
|
Automated Testing Build Error (1/31/2017 10:00 AM) - From https://github.com/phetsims/color-vision/commit/40a93ad1d117fd9854865a24185472fc9b7ab7b0
```
Running "eslint:allFiles" (eslint) task
/home/mendeleev/git/color-vision/js/singlebulb/view/SingleBulbScreenView.js
25:3 error Mismatched require statement values, FlashlightWireNode !== StopSignNode require-statement-match
✖ 1 problem (1 error, 0 warnings)
Warning: Task "eslint:allFiles" failed. Use --force to continue.
Aborted due to warnings.
```
|
test
|
automated testing build error am from running eslint allfiles eslint task home mendeleev git color vision js singlebulb view singlebulbscreenview js error mismatched require statement values flashlightwirenode stopsignnode require statement match ✖ problem error warnings warning task eslint allfiles failed use force to continue aborted due to warnings
| 1
|
637,290
| 20,624,918,892
|
IssuesEvent
|
2022-03-07 21:22:21
|
Craftinators/Borealis
|
https://api.github.com/repos/Craftinators/Borealis
|
opened
|
Add support for variable declaration and usage
|
priority: critical type: feature
|
Variables should be able to be able to be declared and used in expressions, parsing their value into their place such as so:
```js
let a = 5
a + 2 // returns 7
```
Using new `NameExpression` and `AssignmentExpression` syntaxes to parse the expected tokens correctly.
|
1.0
|
Add support for variable declaration and usage - Variables should be able to be able to be declared and used in expressions, parsing their value into their place such as so:
```js
let a = 5
a + 2 // returns 7
```
Using new `NameExpression` and `AssignmentExpression` syntaxes to parse the expected tokens correctly.
|
non_test
|
add support for variable declaration and usage variables should be able to be able to be declared and used in expressions parsing their value into their place such as so js let a a returns using new nameexpression and assignmentexpression syntaxes to parse the expected tokens correctly
| 0
|
94,820
| 27,300,184,148
|
IssuesEvent
|
2023-02-24 00:49:03
|
dotnet/project-system
|
https://api.github.com/repos/dotnet/project-system
|
closed
|
Build Acceleration with netstandard
|
Feature-Build-Acceleration
|
## Visual Studio Version
Version 17.5.0
## Summary
I was going to try and see if we could use build acceleration at my workplace, however I couldn't make it trigger and it always built all my project dependencies when I made a simple edit in one of the source files at one of our core libraries. Eventually I discovered that if I changed the target framework to net6.0 from netstandard2.0 it worked as expected.
I can understand there might be some technical reason netstandard projects doesn't get build acceleration, not sure if that is the case, but if it is it should probably be listed as a prerequisite, which AFAICT it is not https://github.com/dotnet/project-system/blob/main/docs/build-acceleration.md#validate-builds-are-accelerated
## Steps to Reproduce
Using [this](https://github.com/dotnet/project-system/blob/main/docs/build-acceleration.md#example) as an example.. If Library 3 has target framework netstandard2.0, and I make a change to to Library 3, it will trigger all 4 MSBuild calls instead of being called once like it states in the link. If I change to net6.0 it works as expected, it also works if I multi-target `<TargetFrameworks>netstandard2.0;net6.0</TargetFrameworks>`.
## Expected Behavior
I would expect projects with netstandard to support build acceleration as I can't see any documentation that states otherwise, or I would expect the documentation to make target framework demands more clear.
## Actual Behavior
Build acceleration doesn't trigger when I make a simple change in one of my core libraries, instead the entire source gets built like it always did. Documentation doesn't mention any target framework requirements
## User Impact
We have a very large codebase that we're working on migrating to net6.0, however the majority of the codebase will have to continue to build to netstandard until we we can rid ourselves of all legacy demands which will take along time. Without netstandard support we cannot use this feature which otherwise looks excellent.
|
1.0
|
Build Acceleration with netstandard - ## Visual Studio Version
Version 17.5.0
## Summary
I was going to try and see if we could use build acceleration at my workplace, however I couldn't make it trigger and it always built all my project dependencies when I made a simple edit in one of the source files at one of our core libraries. Eventually I discovered that if I changed the target framework to net6.0 from netstandard2.0 it worked as expected.
I can understand there might be some technical reason netstandard projects doesn't get build acceleration, not sure if that is the case, but if it is it should probably be listed as a prerequisite, which AFAICT it is not https://github.com/dotnet/project-system/blob/main/docs/build-acceleration.md#validate-builds-are-accelerated
## Steps to Reproduce
Using [this](https://github.com/dotnet/project-system/blob/main/docs/build-acceleration.md#example) as an example.. If Library 3 has target framework netstandard2.0, and I make a change to to Library 3, it will trigger all 4 MSBuild calls instead of being called once like it states in the link. If I change to net6.0 it works as expected, it also works if I multi-target `<TargetFrameworks>netstandard2.0;net6.0</TargetFrameworks>`.
## Expected Behavior
I would expect projects with netstandard to support build acceleration as I can't see any documentation that states otherwise, or I would expect the documentation to make target framework demands more clear.
## Actual Behavior
Build acceleration doesn't trigger when I make a simple change in one of my core libraries, instead the entire source gets built like it always did. Documentation doesn't mention any target framework requirements
## User Impact
We have a very large codebase that we're working on migrating to net6.0, however the majority of the codebase will have to continue to build to netstandard until we we can rid ourselves of all legacy demands which will take along time. Without netstandard support we cannot use this feature which otherwise looks excellent.
|
non_test
|
build acceleration with netstandard visual studio version version summary i was going to try and see if we could use build acceleration at my workplace however i couldn t make it trigger and it always built all my project dependencies when i made a simple edit in one of the source files at one of our core libraries eventually i discovered that if i changed the target framework to from it worked as expected i can understand there might be some technical reason netstandard projects doesn t get build acceleration not sure if that is the case but if it is it should probably be listed as a prerequisite which afaict it is not steps to reproduce using as an example if library has target framework and i make a change to to library it will trigger all msbuild calls instead of being called once like it states in the link if i change to it works as expected it also works if i multi target expected behavior i would expect projects with netstandard to support build acceleration as i can t see any documentation that states otherwise or i would expect the documentation to make target framework demands more clear actual behavior build acceleration doesn t trigger when i make a simple change in one of my core libraries instead the entire source gets built like it always did documentation doesn t mention any target framework requirements user impact we have a very large codebase that we re working on migrating to however the majority of the codebase will have to continue to build to netstandard until we we can rid ourselves of all legacy demands which will take along time without netstandard support we cannot use this feature which otherwise looks excellent
| 0
|
43,806
| 5,561,763,201
|
IssuesEvent
|
2017-03-25 00:02:21
|
dotnet/corefx
|
https://api.github.com/repos/dotnet/corefx
|
closed
|
OuterLoop_Windows10_release: Test "System.Numerics.Tests.divremTest.RunDivRemTests" failed with "System.Exception"
|
area-System.Numerics blocking-clean-ci test bug test-run-core
|
Failed test: System.Numerics.Tests.divremTest.RunDivRemTests
Detail: https://ci.dot.net/job/dotnet_corefx/job/master/job/outerloop_win10_release/77/
Message:
~~~
System.Exception : VerifyDivRemString failed: make 92 125 192 198 117 183 180 87 56 15 18 178 228 7 181 238 94 7 185 165 233 141 178 201 200 177 252 196 42 81 206 148 34 113 177 endmake make 102 173 213 220 61 239 134 134 176 47 135 119 32 155 128 132 229 113 135 207 203 246 253 195 187 239 44 230 64 125 144 endmake bDivRem Xunit.Sdk.EqualException: Assert.Equal() Failure
Expected: 0
Actual: 31122745322556859589923417330907291586
~~~
Stack Trace:
~~~
at Xunit.Assert.Equal[T](T expected, T actual, IEqualityComparer`1 comparer) in C:\BuildAgent\work\cb37e9acf085d108\src\xunit.assert\Asserts\EqualityAsserts.cs:line 35
at System.Numerics.Tests.StackCalc.VerifyOutParameter() in D:\j\workspace\outerloop_win---6835b088\src\System.Runtime.Numerics\tests\BigInteger\stackcalculator.cs:line 252
at System.Numerics.Tests.divremTest.VerifyDivRemString(String opstring) in D:\j\workspace\outerloop_win---6835b088\src\System.Runtime.Numerics\tests\BigInteger\divrem.cs:line 187
---- Assert.Equal() Failure
Expected: 0
Actual: 31122745322556859589923417330907291586
~~~
Configuration:
OuterLoop_Windows10_release (build#77)
|
2.0
|
OuterLoop_Windows10_release: Test "System.Numerics.Tests.divremTest.RunDivRemTests" failed with "System.Exception" - Failed test: System.Numerics.Tests.divremTest.RunDivRemTests
Detail: https://ci.dot.net/job/dotnet_corefx/job/master/job/outerloop_win10_release/77/
Message:
~~~
System.Exception : VerifyDivRemString failed: make 92 125 192 198 117 183 180 87 56 15 18 178 228 7 181 238 94 7 185 165 233 141 178 201 200 177 252 196 42 81 206 148 34 113 177 endmake make 102 173 213 220 61 239 134 134 176 47 135 119 32 155 128 132 229 113 135 207 203 246 253 195 187 239 44 230 64 125 144 endmake bDivRem Xunit.Sdk.EqualException: Assert.Equal() Failure
Expected: 0
Actual: 31122745322556859589923417330907291586
~~~
Stack Trace:
~~~
at Xunit.Assert.Equal[T](T expected, T actual, IEqualityComparer`1 comparer) in C:\BuildAgent\work\cb37e9acf085d108\src\xunit.assert\Asserts\EqualityAsserts.cs:line 35
at System.Numerics.Tests.StackCalc.VerifyOutParameter() in D:\j\workspace\outerloop_win---6835b088\src\System.Runtime.Numerics\tests\BigInteger\stackcalculator.cs:line 252
at System.Numerics.Tests.divremTest.VerifyDivRemString(String opstring) in D:\j\workspace\outerloop_win---6835b088\src\System.Runtime.Numerics\tests\BigInteger\divrem.cs:line 187
---- Assert.Equal() Failure
Expected: 0
Actual: 31122745322556859589923417330907291586
~~~
Configuration:
OuterLoop_Windows10_release (build#77)
|
test
|
outerloop release test system numerics tests divremtest rundivremtests failed with system exception failed test system numerics tests divremtest rundivremtests detail message system exception verifydivremstring failed make endmake make endmake bdivrem xunit sdk equalexception assert equal failure expected actual stack trace at xunit assert equal t expected t actual iequalitycomparer comparer in c buildagent work src xunit assert asserts equalityasserts cs line at system numerics tests stackcalc verifyoutparameter in d j workspace outerloop win src system runtime numerics tests biginteger stackcalculator cs line at system numerics tests divremtest verifydivremstring string opstring in d j workspace outerloop win src system runtime numerics tests biginteger divrem cs line assert equal failure expected actual configuration outerloop release build
| 1
|
307,380
| 26,527,297,878
|
IssuesEvent
|
2023-01-19 09:45:11
|
pyxem/pyxem
|
https://api.github.com/repos/pyxem/pyxem
|
closed
|
test failure with scikit-learn 1.1.0rc1
|
tests
|
from https://github.com/hyperspy/hyperspy-extensions-list/pull/22
```python
_________________ TestLearningSegment.test_learning_ncc_matrix _________________
self = <pyxem.tests.signals.test_segments.TestLearningSegment object at 0x7f5c2e79f3d0>
learning_segment = <pyxem.signals.segments.LearningSegment object at 0x7f5c17c1bfa0>
def test_learning_ncc_matrix(self, learning_segment):
ncc = learning_segment.get_ncc_matrix()
ans = np.array(
[
[
[1.0, -0.26413543, -0.50636968, 0.61237256, 0.0],
[-0.26413543, 1.0, -0.40125028, -0.43133[109](https://github.com/hyperspy/hyperspy-extensions-list/runs/6272585445?check_suite_focus=true#step:15:109), 0.0],
[-0.50636968, -0.40125028, 1.0, -0.31008684, 0.0],
[0.61237256, -0.43133109, -0.31008684, 1.0, 0.0],
[0.0, 0.0, 0.0, 0.0, 1.0],
],
[
[1.0, -0.0588285, -0.07313363, -0.04087783, 0.0],
[-0.0588285, 1.0, -0.07312725, -0.04099601, 0.0],
[-0.07313363, -0.07312725, 1.0, -0.05096472, 0.0],
[-0.04087783, -0.04099601, -0.05096472, 1.0, 0.0],
[0.0, 0.0, 0.0, 0.0, 1.0],
],
]
)
> np.testing.assert_almost_equal(ncc.data, ans)
E AssertionError:
E Arrays are not almost equal to 7 decimals
E
E Mismatched elements: 12 / 50 (24%)
E Max absolute difference: 0.00049256
E Max relative difference: 0.01204947
E x: array([[[ 1.0000000e+00, -2.6413860e-01, -5.0636968e-01, 6.1237492e-01,
E 0.0000000e+00],
E [-2.6413860e-01, 1.0000000e+00, -4.0125023e-01, -4.3133[112](https://github.com/hyperspy/hyperspy-extensions-list/runs/6272585445?check_suite_focus=true#step:15:112)e-01,...
E y: array([[[ 1. , -0.2641354, -0.5063697, 0.6[123](https://github.com/hyperspy/hyperspy-extensions-list/runs/6272585445?check_suite_focus=true#step:15:123)726, 0. ],
E [-0.2641354, 1. , -0.40[125](https://github.com/hyperspy/hyperspy-extensions-list/runs/6272585445?check_suite_focus=true#step:15:125)03, -0.43[133](https://github.com/hyperspy/hyperspy-extensions-list/runs/6272585445?check_suite_focus=true#step:15:133)11, 0. ],
E [-0.5063697, -0.4012503, 1. , -0.3100868, 0. ],...
/usr/share/miniconda3/lib/python3.9/site-packages/pyxem/tests/signals/test_segments.py:94: AssertionError
---------------------------- Captured stdout setup -----------------------------
Decomposition info:
normalize_poissonian_noise=False
algorithm=NMF
output_dimension=5
centre=None
scikit-learn estimator:
NMF(n_components=5)
```
|
1.0
|
test failure with scikit-learn 1.1.0rc1 - from https://github.com/hyperspy/hyperspy-extensions-list/pull/22
```python
_________________ TestLearningSegment.test_learning_ncc_matrix _________________
self = <pyxem.tests.signals.test_segments.TestLearningSegment object at 0x7f5c2e79f3d0>
learning_segment = <pyxem.signals.segments.LearningSegment object at 0x7f5c17c1bfa0>
def test_learning_ncc_matrix(self, learning_segment):
ncc = learning_segment.get_ncc_matrix()
ans = np.array(
[
[
[1.0, -0.26413543, -0.50636968, 0.61237256, 0.0],
[-0.26413543, 1.0, -0.40125028, -0.43133[109](https://github.com/hyperspy/hyperspy-extensions-list/runs/6272585445?check_suite_focus=true#step:15:109), 0.0],
[-0.50636968, -0.40125028, 1.0, -0.31008684, 0.0],
[0.61237256, -0.43133109, -0.31008684, 1.0, 0.0],
[0.0, 0.0, 0.0, 0.0, 1.0],
],
[
[1.0, -0.0588285, -0.07313363, -0.04087783, 0.0],
[-0.0588285, 1.0, -0.07312725, -0.04099601, 0.0],
[-0.07313363, -0.07312725, 1.0, -0.05096472, 0.0],
[-0.04087783, -0.04099601, -0.05096472, 1.0, 0.0],
[0.0, 0.0, 0.0, 0.0, 1.0],
],
]
)
> np.testing.assert_almost_equal(ncc.data, ans)
E AssertionError:
E Arrays are not almost equal to 7 decimals
E
E Mismatched elements: 12 / 50 (24%)
E Max absolute difference: 0.00049256
E Max relative difference: 0.01204947
E x: array([[[ 1.0000000e+00, -2.6413860e-01, -5.0636968e-01, 6.1237492e-01,
E 0.0000000e+00],
E [-2.6413860e-01, 1.0000000e+00, -4.0125023e-01, -4.3133[112](https://github.com/hyperspy/hyperspy-extensions-list/runs/6272585445?check_suite_focus=true#step:15:112)e-01,...
E y: array([[[ 1. , -0.2641354, -0.5063697, 0.6[123](https://github.com/hyperspy/hyperspy-extensions-list/runs/6272585445?check_suite_focus=true#step:15:123)726, 0. ],
E [-0.2641354, 1. , -0.40[125](https://github.com/hyperspy/hyperspy-extensions-list/runs/6272585445?check_suite_focus=true#step:15:125)03, -0.43[133](https://github.com/hyperspy/hyperspy-extensions-list/runs/6272585445?check_suite_focus=true#step:15:133)11, 0. ],
E [-0.5063697, -0.4012503, 1. , -0.3100868, 0. ],...
/usr/share/miniconda3/lib/python3.9/site-packages/pyxem/tests/signals/test_segments.py:94: AssertionError
---------------------------- Captured stdout setup -----------------------------
Decomposition info:
normalize_poissonian_noise=False
algorithm=NMF
output_dimension=5
centre=None
scikit-learn estimator:
NMF(n_components=5)
```
|
test
|
test failure with scikit learn from python testlearningsegment test learning ncc matrix self learning segment def test learning ncc matrix self learning segment ncc learning segment get ncc matrix ans np array np testing assert almost equal ncc data ans e assertionerror e arrays are not almost equal to decimals e e mismatched elements e max absolute difference e max relative difference e x array e e e y array e e usr share lib site packages pyxem tests signals test segments py assertionerror captured stdout setup decomposition info normalize poissonian noise false algorithm nmf output dimension centre none scikit learn estimator nmf n components
| 1
|
82,576
| 3,614,868,652
|
IssuesEvent
|
2016-02-06 09:47:45
|
Optiboot/optiboot
|
https://api.github.com/repos/Optiboot/optiboot
|
opened
|
Link troubles with Atmel toolset (avr-gcc 4.9.x)
|
Component-Makefiles help wanted Priority-Medium Regression
|
The structure of the avr-libc libraries has apparently changed in the atmel toolchain containing 4.9.x, and the "-lc" at the end of the link command no longer allows optiboot builds with eeprom support to find the eeprom_xxx_byte() functions (they moved from lib/avrN/libc.a to lib/avrN/lib<chipname>.a)
|
1.0
|
Link troubles with Atmel toolset (avr-gcc 4.9.x) - The structure of the avr-libc libraries has apparently changed in the atmel toolchain containing 4.9.x, and the "-lc" at the end of the link command no longer allows optiboot builds with eeprom support to find the eeprom_xxx_byte() functions (they moved from lib/avrN/libc.a to lib/avrN/lib<chipname>.a)
|
non_test
|
link troubles with atmel toolset avr gcc x the structure of the avr libc libraries has apparently changed in the atmel toolchain containing x and the lc at the end of the link command no longer allows optiboot builds with eeprom support to find the eeprom xxx byte functions they moved from lib avrn libc a to lib avrn lib a
| 0
|
44,483
| 23,651,188,800
|
IssuesEvent
|
2022-08-26 06:49:28
|
clj-commons/aleph
|
https://api.github.com/repos/clj-commons/aleph
|
closed
|
Improve wrap-future
|
performance good first issue
|
This was uncovered in the process of reviewing #608. See my comments there for more.
In short, `wrap-future` checks `.isSuccess` on a future, when it really means to check `.isDone`. If it succeeded, it creates an immediate success-deferred. If not, it attaches handlers. In the case of a failed/canceled future, it does a lot of unnecessary work before immediately invoking the handler: fn thread frame binding, handler object creation, and scheduling the handlers to run (potentially) on another thread. This is also kind of confusing because we're checking the wrong condition.
To do:
- [ ] Switch to `.isDone` from `.isSuccess` in `wrap-future`
- [ ] If `.isDone`, choose between returning success- and error-deferreds based on the future's status. For consistency, we can reuse the `operation-complete` handler, but add a flag to tell it to use/ignore executors (so we can run it on the current thread)
- [ ] Verify all tests still work, `test-classloader` in particular
|
True
|
Improve wrap-future - This was uncovered in the process of reviewing #608. See my comments there for more.
In short, `wrap-future` checks `.isSuccess` on a future, when it really means to check `.isDone`. If it succeeded, it creates an immediate success-deferred. If not, it attaches handlers. In the case of a failed/canceled future, it does a lot of unnecessary work before immediately invoking the handler: fn thread frame binding, handler object creation, and scheduling the handlers to run (potentially) on another thread. This is also kind of confusing because we're checking the wrong condition.
To do:
- [ ] Switch to `.isDone` from `.isSuccess` in `wrap-future`
- [ ] If `.isDone`, choose between returning success- and error-deferreds based on the future's status. For consistency, we can reuse the `operation-complete` handler, but add a flag to tell it to use/ignore executors (so we can run it on the current thread)
- [ ] Verify all tests still work, `test-classloader` in particular
|
non_test
|
improve wrap future this was uncovered in the process of reviewing see my comments there for more in short wrap future checks issuccess on a future when it really means to check isdone if it succeeded it creates an immediate success deferred if not it attaches handlers in the case of a failed canceled future it does a lot of unnecessary work before immediately invoking the handler fn thread frame binding handler object creation and scheduling the handlers to run potentially on another thread this is also kind of confusing because we re checking the wrong condition to do switch to isdone from issuccess in wrap future if isdone choose between returning success and error deferreds based on the future s status for consistency we can reuse the operation complete handler but add a flag to tell it to use ignore executors so we can run it on the current thread verify all tests still work test classloader in particular
| 0
|
9,999
| 3,081,384,980
|
IssuesEvent
|
2015-08-22 17:25:52
|
tntim96/JSCover
|
https://api.github.com/repos/tntim96/JSCover
|
closed
|
Make js (-fs option) code instrumentation multithreaded
|
enhancement Fix applied - please re-test
|
For big projects it takes noticeable time to instrument entire codebase. Run code instrumentation in several threads to complete it faster.
|
1.0
|
Make js (-fs option) code instrumentation multithreaded - For big projects it takes noticeable time to instrument entire codebase. Run code instrumentation in several threads to complete it faster.
|
test
|
make js fs option code instrumentation multithreaded for big projects it takes noticeable time to instrument entire codebase run code instrumentation in several threads to complete it faster
| 1
|
151,298
| 12,030,822,897
|
IssuesEvent
|
2020-04-13 08:14:46
|
microsoft/azure-tools-for-java
|
https://api.github.com/repos/microsoft/azure-tools-for-java
|
closed
|
There is no scroll wheel function to browse the instance
|
Internal Test
|
#### Environment:
```
OS: WIN/Mac
Plugins Version: Azure java toolkit for IntelliJ: 3.34.0
IDE Version: IU19.3.4 - jre11/IC19.3 - jre8
```
#### Repro Steps:
1. Add spring cloud dependency
2. Run deploy configuration with 20 instances.
3. Right click to open "show properties".
#### Result:
**There is no scroll wheel function to browse the instance
and can not show all instance even if the window is maximized.**
|
1.0
|
There is no scroll wheel function to browse the instance - #### Environment:
```
OS: WIN/Mac
Plugins Version: Azure java toolkit for IntelliJ: 3.34.0
IDE Version: IU19.3.4 - jre11/IC19.3 - jre8
```
#### Repro Steps:
1. Add spring cloud dependency
2. Run deploy configuration with 20 instances.
3. Right click to open "show properties".
#### Result:
**There is no scroll wheel function to browse the instance
and can not show all instance even if the window is maximized.**
|
test
|
there is no scroll wheel function to browse the instance environment os win mac plugins version azure java toolkit for intellij ide version repro steps add spring cloud dependency run deploy configuration with instances right click to open show properties result there is no scroll wheel function to browse the instance and can not show all instance even if the window is maximized
| 1
|
265,176
| 28,244,741,240
|
IssuesEvent
|
2023-04-06 09:51:19
|
hshivhare67/platform_packages_apps_settings_AOSP10_r33
|
https://api.github.com/repos/hshivhare67/platform_packages_apps_settings_AOSP10_r33
|
closed
|
CVE-2020-0416 (High) detected in Settingsandroid-10.0.0_r44 - autoclosed
|
Mend: dependency security vulnerability
|
## CVE-2020-0416 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>Settingsandroid-10.0.0_r44</b></p></summary>
<p>
<p>Library home page: <a href=https://android.googlesource.com/platform/packages/apps/Settings>https://android.googlesource.com/platform/packages/apps/Settings</a></p>
<p>Found in HEAD commit: <a href="https://github.com/hshivhare67/platform_packages_apps_settings_AOSP10_r33/commit/7291ac75aa6d2751664c7e2230a19c28c6e54cc8">7291ac75aa6d2751664c7e2230a19c28c6e54cc8</a></p>
<p>Found in base branch: <b>main</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/src/com/android/settings/widget/AppSwitchPreference.java</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In multiple settings screens, there are possible tapjacking attacks due to an insecure default value. This could lead to local escalation of privilege and permissions with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-9 Android-10 Android-11 Android-8.0 Android-8.1Android ID: A-155288585
<p>Publish Date: 2020-10-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-0416>CVE-2020-0416</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2020-0416 (High) detected in Settingsandroid-10.0.0_r44 - autoclosed - ## CVE-2020-0416 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>Settingsandroid-10.0.0_r44</b></p></summary>
<p>
<p>Library home page: <a href=https://android.googlesource.com/platform/packages/apps/Settings>https://android.googlesource.com/platform/packages/apps/Settings</a></p>
<p>Found in HEAD commit: <a href="https://github.com/hshivhare67/platform_packages_apps_settings_AOSP10_r33/commit/7291ac75aa6d2751664c7e2230a19c28c6e54cc8">7291ac75aa6d2751664c7e2230a19c28c6e54cc8</a></p>
<p>Found in base branch: <b>main</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/src/com/android/settings/widget/AppSwitchPreference.java</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In multiple settings screens, there are possible tapjacking attacks due to an insecure default value. This could lead to local escalation of privilege and permissions with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-9 Android-10 Android-11 Android-8.0 Android-8.1Android ID: A-155288585
<p>Publish Date: 2020-10-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-0416>CVE-2020-0416</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve high detected in settingsandroid autoclosed cve high severity vulnerability vulnerable library settingsandroid library home page a href found in head commit a href found in base branch main vulnerable source files src com android settings widget appswitchpreference java vulnerability details in multiple settings screens there are possible tapjacking attacks due to an insecure default value this could lead to local escalation of privilege and permissions with no additional execution privileges needed user interaction is needed for exploitation product androidversions android android android android android id a publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href step up your open source security game with mend
| 0
|
287,696
| 24,853,065,043
|
IssuesEvent
|
2022-10-26 22:05:38
|
AWAH-SIP/AWAH-SIP_Codec
|
https://api.github.com/repos/AWAH-SIP/AWAH-SIP_Codec
|
closed
|
application crashes with pjsua_call_get_info: Assertion
|
bug critical to test
|
reason unknown: probably caused by call inspector
pjsua_call_get_info: Assertion
|
1.0
|
application crashes with pjsua_call_get_info: Assertion - reason unknown: probably caused by call inspector
pjsua_call_get_info: Assertion
|
test
|
application crashes with pjsua call get info assertion reason unknown probably caused by call inspector pjsua call get info assertion
| 1
|
310,057
| 26,697,009,226
|
IssuesEvent
|
2023-01-27 11:13:49
|
dusk-network/rusk
|
https://api.github.com/repos/dusk-network/rusk
|
closed
|
Use `tar` to handle state's compression instead of `zip`
|
good first issue mark:testnet
|
#### Summary
Our servers are *nix base and there is no reason to use `zip` instead of `tarball` files, plus the ergonomics of the tar crates is better than zip crates.
#### Possible solution design or implementation
See:
https://rust-lang-nursery.github.io/rust-cookbook/compression/tar.html#compress-a-directory-into-tarball
https://docs.rs/zip/0.6.2/zip/struct.ZipArchive.html
#### Additional context
The `zip` crates requires more verbose code and additional external crates to handle directory properly.
However this change needs to be done together with the server action that creates the `zip`.
|
1.0
|
Use `tar` to handle state's compression instead of `zip` - #### Summary
Our servers are *nix base and there is no reason to use `zip` instead of `tarball` files, plus the ergonomics of the tar crates is better than zip crates.
#### Possible solution design or implementation
See:
https://rust-lang-nursery.github.io/rust-cookbook/compression/tar.html#compress-a-directory-into-tarball
https://docs.rs/zip/0.6.2/zip/struct.ZipArchive.html
#### Additional context
The `zip` crates requires more verbose code and additional external crates to handle directory properly.
However this change needs to be done together with the server action that creates the `zip`.
|
test
|
use tar to handle state s compression instead of zip summary our servers are nix base and there is no reason to use zip instead of tarball files plus the ergonomics of the tar crates is better than zip crates possible solution design or implementation see additional context the zip crates requires more verbose code and additional external crates to handle directory properly however this change needs to be done together with the server action that creates the zip
| 1
|
468,904
| 13,492,519,089
|
IssuesEvent
|
2020-09-11 18:10:17
|
cds-snc/report-a-cybercrime
|
https://api.github.com/repos/cds-snc/report-a-cybercrime
|
closed
|
Update What Was Affected Form
|
high priority suggestion
|
Update WhatWasAffectedForm.js to use Formik, Yup, and Bootstrap as documented in issue #2136. These changes have been made to HowDidItStartForm.js, you can them here - .
This form similar to HowDidItStartForm.js except it does not have any conditional elements to display. See PR #2138 for details.
|
1.0
|
Update What Was Affected Form - Update WhatWasAffectedForm.js to use Formik, Yup, and Bootstrap as documented in issue #2136. These changes have been made to HowDidItStartForm.js, you can them here - .
This form similar to HowDidItStartForm.js except it does not have any conditional elements to display. See PR #2138 for details.
|
non_test
|
update what was affected form update whatwasaffectedform js to use formik yup and bootstrap as documented in issue these changes have been made to howdiditstartform js you can them here this form similar to howdiditstartform js except it does not have any conditional elements to display see pr for details
| 0
|
254,134
| 21,730,673,696
|
IssuesEvent
|
2022-05-11 11:44:06
|
INSPIRE-MIF/helpdesk-validator
|
https://api.github.com/repos/INSPIRE-MIF/helpdesk-validator
|
reopened
|
Statistical Units Vector - geometry test for GM_MultiSurface is too strict
|
ready for testing requires change in TG
|
Hi,
currently the validation of GML in the data theme Statistical Unit (Vector) fails when "gml:Surface" is used to characterize the area, i.e. the test "su-vector-as.b.2: Area Statistical Units" fails with the message "Check that the reference geometry of an area statistical units is a GM_MultiSurface.".
According to the specification for Statistical Unit ( https://inspire.ec.europa.eu/documents/Data_Specifications/INSPIRE_DataSpecification_SU_v3.0.pdf ) the UML class diagram for "Vector package" (figure 7 in section 5.3.1.2.3) suggests that GM_Object is allowed to describe the geometry.
I think the validation test is to strict and should allow gml:Surface.
Link to the data file: https://fbinter.stadt-berlin.de/fb/atom/SU/SU_BLK.zip
Link to the test report: [SU_BLK_2021_06_29_Test.zip](https://github.com/INSPIRE-MIF/helpdesk-validator/files/8133486/SU_BLK_2021_06_29_Test.zip)
Best regards and many thanks
Damian
|
1.0
|
Statistical Units Vector - geometry test for GM_MultiSurface is too strict - Hi,
currently the validation of GML in the data theme Statistical Unit (Vector) fails when "gml:Surface" is used to characterize the area, i.e. the test "su-vector-as.b.2: Area Statistical Units" fails with the message "Check that the reference geometry of an area statistical units is a GM_MultiSurface.".
According to the specification for Statistical Unit ( https://inspire.ec.europa.eu/documents/Data_Specifications/INSPIRE_DataSpecification_SU_v3.0.pdf ) the UML class diagram for "Vector package" (figure 7 in section 5.3.1.2.3) suggests that GM_Object is allowed to describe the geometry.
I think the validation test is to strict and should allow gml:Surface.
Link to the data file: https://fbinter.stadt-berlin.de/fb/atom/SU/SU_BLK.zip
Link to the test report: [SU_BLK_2021_06_29_Test.zip](https://github.com/INSPIRE-MIF/helpdesk-validator/files/8133486/SU_BLK_2021_06_29_Test.zip)
Best regards and many thanks
Damian
|
test
|
statistical units vector geometry test for gm multisurface is too strict hi currently the validation of gml in the data theme statistical unit vector fails when gml surface is used to characterize the area i e the test su vector as b area statistical units fails with the message check that the reference geometry of an area statistical units is a gm multisurface according to the specification for statistical unit the uml class diagram for vector package figure in section suggests that gm object is allowed to describe the geometry i think the validation test is to strict and should allow gml surface link to the data file link to the test report best regards and many thanks damian
| 1
|
79,196
| 7,698,234,730
|
IssuesEvent
|
2018-05-18 22:05:17
|
nodejs/node-chakracore
|
https://api.github.com/repos/nodejs/node-chakracore
|
opened
|
Test failure `parallel/test-fs-append-file` due to missing Promise.finally method
|
test
|
<!--
Thank you for reporting an issue.
This issue tracker is for bugs and issues found within Node.js core.
If you require more general support please file an issue on our help
repo. https://github.com/nodejs/help
Please fill in as much of the template below as you're able.
Version: output of `node -v`
Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)
Subsystem: if known, please specify affected core module name
If possible, please provide code that demonstrates the problem, keeping it as
simple and free of external dependencies as you are able.
-->
* **Version**: master
* **Platform**: all
* **Subsystem**: fs
<!-- Enter your issue details below this comment. -->
not ok 510 parallel/test-fs-append-file
---
duration_ms: 0.431
severity: fail
exitcode: 1
stack: |-
(node:4308) ExperimentalWarning: The fs.promises API is experimental
E:\GitHub\node-chakracore5\test\parallel\test-fs-append-file.js:45
const throwNextTick = (e) => { process.nextTick(() => { throw e; }); };
^
TypeError: Object doesn't support property or method 'finally'
at writeFile (internal/fs/promises.js:452:3)
at Generator.prototype.next (native code)
…
Re-enable this test once #540 is resolved.
|
1.0
|
Test failure `parallel/test-fs-append-file` due to missing Promise.finally method - <!--
Thank you for reporting an issue.
This issue tracker is for bugs and issues found within Node.js core.
If you require more general support please file an issue on our help
repo. https://github.com/nodejs/help
Please fill in as much of the template below as you're able.
Version: output of `node -v`
Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)
Subsystem: if known, please specify affected core module name
If possible, please provide code that demonstrates the problem, keeping it as
simple and free of external dependencies as you are able.
-->
* **Version**: master
* **Platform**: all
* **Subsystem**: fs
<!-- Enter your issue details below this comment. -->
not ok 510 parallel/test-fs-append-file
---
duration_ms: 0.431
severity: fail
exitcode: 1
stack: |-
(node:4308) ExperimentalWarning: The fs.promises API is experimental
E:\GitHub\node-chakracore5\test\parallel\test-fs-append-file.js:45
const throwNextTick = (e) => { process.nextTick(() => { throw e; }); };
^
TypeError: Object doesn't support property or method 'finally'
at writeFile (internal/fs/promises.js:452:3)
at Generator.prototype.next (native code)
…
Re-enable this test once #540 is resolved.
|
test
|
test failure parallel test fs append file due to missing promise finally method thank you for reporting an issue this issue tracker is for bugs and issues found within node js core if you require more general support please file an issue on our help repo please fill in as much of the template below as you re able version output of node v platform output of uname a unix or version and or bit windows subsystem if known please specify affected core module name if possible please provide code that demonstrates the problem keeping it as simple and free of external dependencies as you are able version master platform all subsystem fs not ok parallel test fs append file duration ms severity fail exitcode stack node experimentalwarning the fs promises api is experimental e github node test parallel test fs append file js const thrownexttick e process nexttick throw e typeerror object doesn t support property or method finally at writefile internal fs promises js at generator prototype next native code … re enable this test once is resolved
| 1
|
51,821
| 13,649,899,698
|
IssuesEvent
|
2020-09-26 16:32:19
|
directoryxx/Belajar-Microservice-1
|
https://api.github.com/repos/directoryxx/Belajar-Microservice-1
|
opened
|
CVE-2020-7608 (Medium) detected in yargs-parser-11.1.1.tgz
|
security vulnerability
|
## CVE-2020-7608 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>yargs-parser-11.1.1.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-11.1.1.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-11.1.1.tgz</a></p>
<p>Path to dependency file: Belajar-Microservice-1/front/package.json</p>
<p>Path to vulnerable library: Belajar-Microservice-1/front/node_modules/webpack-dev-server/node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-3.4.0.tgz (Root Library)
- webpack-dev-server-3.10.2.tgz
- yargs-12.0.5.tgz
- :x: **yargs-parser-11.1.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/directoryxx/Belajar-Microservice-1/commit/c97644d6b43aeac51b991265a91ba44b964d9eee">c97644d6b43aeac51b991265a91ba44b964d9eee</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
yargs-parser could be tricked into adding or modifying properties of Object.prototype using a "__proto__" payload.
<p>Publish Date: 2020-03-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7608>CVE-2020-7608</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7608">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7608</a></p>
<p>Release Date: 2020-03-16</p>
<p>Fix Resolution: v18.1.1;13.1.2;15.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2020-7608 (Medium) detected in yargs-parser-11.1.1.tgz - ## CVE-2020-7608 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>yargs-parser-11.1.1.tgz</b></p></summary>
<p>the mighty option parser used by yargs</p>
<p>Library home page: <a href="https://registry.npmjs.org/yargs-parser/-/yargs-parser-11.1.1.tgz">https://registry.npmjs.org/yargs-parser/-/yargs-parser-11.1.1.tgz</a></p>
<p>Path to dependency file: Belajar-Microservice-1/front/package.json</p>
<p>Path to vulnerable library: Belajar-Microservice-1/front/node_modules/webpack-dev-server/node_modules/yargs-parser/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-3.4.0.tgz (Root Library)
- webpack-dev-server-3.10.2.tgz
- yargs-12.0.5.tgz
- :x: **yargs-parser-11.1.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/directoryxx/Belajar-Microservice-1/commit/c97644d6b43aeac51b991265a91ba44b964d9eee">c97644d6b43aeac51b991265a91ba44b964d9eee</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
yargs-parser could be tricked into adding or modifying properties of Object.prototype using a "__proto__" payload.
<p>Publish Date: 2020-03-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7608>CVE-2020-7608</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7608">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7608</a></p>
<p>Release Date: 2020-03-16</p>
<p>Fix Resolution: v18.1.1;13.1.2;15.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve medium detected in yargs parser tgz cve medium severity vulnerability vulnerable library yargs parser tgz the mighty option parser used by yargs library home page a href path to dependency file belajar microservice front package json path to vulnerable library belajar microservice front node modules webpack dev server node modules yargs parser package json dependency hierarchy react scripts tgz root library webpack dev server tgz yargs tgz x yargs parser tgz vulnerable library found in head commit a href found in base branch master vulnerability details yargs parser could be tricked into adding or modifying properties of object prototype using a proto payload publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
| 0
|
584,853
| 17,465,750,172
|
IssuesEvent
|
2021-08-06 16:32:44
|
CCAFS/MARLO
|
https://api.github.com/repos/CCAFS/MARLO
|
opened
|
[KT] (AICCRA) Lessons learn
|
Priority - Medium Type - Enhancement AICCRA
|
Leason learn
- [ ] Improvements needed in the adopted M&E Platform:
We decided to compile our progress to our performance indicator targets and write this mid-year report in a systemic way using the adopted M&E system called MARLO-AICCRA (https://aiccra.marlo.cgiar.org/), and despite the AICCRA data management team carried out a series of activities to adjust the existing system to the needs of AICCRA (see progress report and roadmap), we have identified a number of improvements needed to do it better in future reports.
The following are some areas of improvements to take into consideration for the next round:
- [ ] when asking for the narratives explaining the cluster's contribution to 2021 targets, if no target contribution is expected in 2021 but there has been working towards achieving targets in the following years, it should be clear where to write this.
- [ ] In relation to gender, some indicators such as IPI 3.4: Discussions in Africa-wide and regional events informed by AICCRA funded project outputs (number) (gender and social inclusion dimension indicated) would need a box to explain contribution in relation to gender and social inclusion.
- [ ] There is still some redundancy that we need to address, for example in IPI 3.5: Policy and investment decisions influenced by engagement and information dissemination by AICCRA funded partnerships and capacity building activities (number), the narrative explaining the cluster's contribution to 2021 targets and the section on naming the likely policy and investment decisions to be reported this year end could become repetitive.
- [ ] Improvements needed in indicators:
In relation to the indicators, we would like to improve some of them:
- [ ]For IPI 2.2: Partnerships launched/ strengthened between AICCRA-funded CGIAR and NARS scientists, universities, public sector stakeholders, farmer organizations, NGOs and private sector, we don’t think we should be reporting on launching partnerships. We should be reporting on deep and strengthened partnerships that are delivering mutually beneficial activities and outcomes. As a result, we suggest modifying the indicator to make it stronger and including clear criteria that define the type of partnerships that we would like to report. Likewise, for reporting activities in relation to capacity building, we would like to provide a clear definition of the type of capacity-building activities that should be reported.
- [ ] For IPI 3.4: Discussions in Africa-wide and regional events informed by AICCRA funded project outputs, we need to clarify if global events count. In this case, if we do have global events, we would need to have a very clear statement that many African participants were in the event.
|
1.0
|
[KT] (AICCRA) Lessons learn - Leason learn
- [ ] Improvements needed in the adopted M&E Platform:
We decided to compile our progress to our performance indicator targets and write this mid-year report in a systemic way using the adopted M&E system called MARLO-AICCRA (https://aiccra.marlo.cgiar.org/), and despite the AICCRA data management team carried out a series of activities to adjust the existing system to the needs of AICCRA (see progress report and roadmap), we have identified a number of improvements needed to do it better in future reports.
The following are some areas of improvements to take into consideration for the next round:
- [ ] when asking for the narratives explaining the cluster's contribution to 2021 targets, if no target contribution is expected in 2021 but there has been working towards achieving targets in the following years, it should be clear where to write this.
- [ ] In relation to gender, some indicators such as IPI 3.4: Discussions in Africa-wide and regional events informed by AICCRA funded project outputs (number) (gender and social inclusion dimension indicated) would need a box to explain contribution in relation to gender and social inclusion.
- [ ] There is still some redundancy that we need to address, for example in IPI 3.5: Policy and investment decisions influenced by engagement and information dissemination by AICCRA funded partnerships and capacity building activities (number), the narrative explaining the cluster's contribution to 2021 targets and the section on naming the likely policy and investment decisions to be reported this year end could become repetitive.
- [ ] Improvements needed in indicators:
In relation to the indicators, we would like to improve some of them:
- [ ]For IPI 2.2: Partnerships launched/ strengthened between AICCRA-funded CGIAR and NARS scientists, universities, public sector stakeholders, farmer organizations, NGOs and private sector, we don’t think we should be reporting on launching partnerships. We should be reporting on deep and strengthened partnerships that are delivering mutually beneficial activities and outcomes. As a result, we suggest modifying the indicator to make it stronger and including clear criteria that define the type of partnerships that we would like to report. Likewise, for reporting activities in relation to capacity building, we would like to provide a clear definition of the type of capacity-building activities that should be reported.
- [ ] For IPI 3.4: Discussions in Africa-wide and regional events informed by AICCRA funded project outputs, we need to clarify if global events count. In this case, if we do have global events, we would need to have a very clear statement that many African participants were in the event.
|
non_test
|
aiccra lessons learn leason learn improvements needed in the adopted m e platform we decided to compile our progress to our performance indicator targets and write this mid year report in a systemic way using the adopted m e system called marlo aiccra and despite the aiccra data management team carried out a series of activities to adjust the existing system to the needs of aiccra see progress report and roadmap we have identified a number of improvements needed to do it better in future reports the following are some areas of improvements to take into consideration for the next round when asking for the narratives explaining the cluster s contribution to targets if no target contribution is expected in but there has been working towards achieving targets in the following years it should be clear where to write this in relation to gender some indicators such as ipi discussions in africa wide and regional events informed by aiccra funded project outputs number gender and social inclusion dimension indicated would need a box to explain contribution in relation to gender and social inclusion there is still some redundancy that we need to address for example in ipi policy and investment decisions influenced by engagement and information dissemination by aiccra funded partnerships and capacity building activities number the narrative explaining the cluster s contribution to targets and the section on naming the likely policy and investment decisions to be reported this year end could become repetitive improvements needed in indicators in relation to the indicators we would like to improve some of them for ipi partnerships launched strengthened between aiccra funded cgiar and nars scientists universities public sector stakeholders farmer organizations ngos and private sector we don’t think we should be reporting on launching partnerships we should be reporting on deep and strengthened partnerships that are delivering mutually beneficial activities and outcomes as a result we suggest modifying the indicator to make it stronger and including clear criteria that define the type of partnerships that we would like to report likewise for reporting activities in relation to capacity building we would like to provide a clear definition of the type of capacity building activities that should be reported for ipi discussions in africa wide and regional events informed by aiccra funded project outputs we need to clarify if global events count in this case if we do have global events we would need to have a very clear statement that many african participants were in the event
| 0
|
99,803
| 30,558,421,253
|
IssuesEvent
|
2023-07-20 13:12:08
|
microsoft/fluentui
|
https://api.github.com/repos/microsoft/fluentui
|
reopened
|
api-extractor & build issue: Internal Error: The "MenuTrigger" symbol has a ts.SyntaxKind.Identifier declaration which is not (yet?) supported by API Extractor
|
Area: Build System Status: Fixed
|
### Describe the issue:
While migrating `react-components` suite to new DX (https://github.com/microsoft/fluentui/pull/19040), an interesting error appeared both on local and CI:
> Error: Internal Error: The "MenuTrigger" symbol has a ts.SyntaxKind.Identifier declaration which is not (yet?) supported by API Extractor
#### Actual behavior:
#### Expected behavior:
`api-extractor` task should succeed
---
### Troubleshooting
I was able to find 2 similar kind of issue on api-extractor repo:
- https://github.com/microsoft/rushstack/issues/1460
- https://github.com/microsoft/rushstack/issues/1455
Although none of those were exact match to this issue, so I dig deeper.
**After reverse engineering api-extractor source I was able to find the issue:**
The issue surfaced only now, because `react-components` re-exports multiple packages from N packages, which is not happening per narrowed package scope.
To better understand lets check following visualization of how `build` task is being executed (in simplified manner):
the build was failing while running `api-extractor` task, with aforementioned error `Error: Internal Error: The "MenuTrigger" symbol has a ts.SyntaxKind.Identifier declaration which is not (yet?) supported by API Extractor`...
Why is that happening ?
IF take a look at `MenuTrigger` implementation
```tsx
export const MenuTrigger: React.FC<MenuTriggerProps> = props => {
const state = useMenuTrigger(props);
return renderMenuTrigger(state);
};
MenuTrigger.displayName = 'MenuTrigger';
```
There is nothing suspicious right? If we remove `MenuTrigger.displayName = 'MenuTrigger';` the error will go away. Most of other component is using `forwardRef` so probably that's where the problem lies ?
NOPE
The problem is `ts.SyntaxKind.Identifier` which means, parser has issues with `const`. Which brings us to -> wait why is api-extractor parsing implementation files instead of declaration types ?
> Note: based on api-extractor docs, it stops parsing external packages completely
After many hours :D , I finally found the culprit:
- our new DX is leveraging TS path aliases, so thats what is happening when executing API-extractor.
- lets check the workflow that showcases the issue:
**How to fix this ?**
- `just-scripts` scope:
- we'll need to provide similar processing like we do for `ts` task execution ( which is aware if package is using new DX thus turns off path aliases )
- `local:build` scope:
- we'll need to provide similar logic to just-scripts for `api-extractor.local.json` overrides for `react-components` initially, later on for all vNext packages
|
1.0
|
api-extractor & build issue: Internal Error: The "MenuTrigger" symbol has a ts.SyntaxKind.Identifier declaration which is not (yet?) supported by API Extractor - ### Describe the issue:
While migrating `react-components` suite to new DX (https://github.com/microsoft/fluentui/pull/19040), an interesting error appeared both on local and CI:
> Error: Internal Error: The "MenuTrigger" symbol has a ts.SyntaxKind.Identifier declaration which is not (yet?) supported by API Extractor
#### Actual behavior:
#### Expected behavior:
`api-extractor` task should succeed
---
### Troubleshooting
I was able to find 2 similar kind of issue on api-extractor repo:
- https://github.com/microsoft/rushstack/issues/1460
- https://github.com/microsoft/rushstack/issues/1455
Although none of those were exact match to this issue, so I dig deeper.
**After reverse engineering api-extractor source I was able to find the issue:**
The issue surfaced only now, because `react-components` re-exports multiple packages from N packages, which is not happening per narrowed package scope.
To better understand lets check following visualization of how `build` task is being executed (in simplified manner):
the build was failing while running `api-extractor` task, with aforementioned error `Error: Internal Error: The "MenuTrigger" symbol has a ts.SyntaxKind.Identifier declaration which is not (yet?) supported by API Extractor`...
Why is that happening ?
IF take a look at `MenuTrigger` implementation
```tsx
export const MenuTrigger: React.FC<MenuTriggerProps> = props => {
const state = useMenuTrigger(props);
return renderMenuTrigger(state);
};
MenuTrigger.displayName = 'MenuTrigger';
```
There is nothing suspicious right? If we remove `MenuTrigger.displayName = 'MenuTrigger';` the error will go away. Most of other component is using `forwardRef` so probably that's where the problem lies ?
NOPE
The problem is `ts.SyntaxKind.Identifier` which means, parser has issues with `const`. Which brings us to -> wait why is api-extractor parsing implementation files instead of declaration types ?
> Note: based on api-extractor docs, it stops parsing external packages completely
After many hours :D , I finally found the culprit:
- our new DX is leveraging TS path aliases, so thats what is happening when executing API-extractor.
- lets check the workflow that showcases the issue:
**How to fix this ?**
- `just-scripts` scope:
- we'll need to provide similar processing like we do for `ts` task execution ( which is aware if package is using new DX thus turns off path aliases )
- `local:build` scope:
- we'll need to provide similar logic to just-scripts for `api-extractor.local.json` overrides for `react-components` initially, later on for all vNext packages
|
non_test
|
api extractor build issue internal error the menutrigger symbol has a ts syntaxkind identifier declaration which is not yet supported by api extractor describe the issue while migrating react components suite to new dx an interesting error appeared both on local and ci error internal error the menutrigger symbol has a ts syntaxkind identifier declaration which is not yet supported by api extractor actual behavior expected behavior api extractor task should succeed troubleshooting i was able to find similar kind of issue on api extractor repo although none of those were exact match to this issue so i dig deeper after reverse engineering api extractor source i was able to find the issue the issue surfaced only now because react components re exports multiple packages from n packages which is not happening per narrowed package scope to better understand lets check following visualization of how build task is being executed in simplified manner the build was failing while running api extractor task with aforementioned error error internal error the menutrigger symbol has a ts syntaxkind identifier declaration which is not yet supported by api extractor why is that happening if take a look at menutrigger implementation tsx export const menutrigger react fc props const state usemenutrigger props return rendermenutrigger state menutrigger displayname menutrigger there is nothing suspicious right if we remove menutrigger displayname menutrigger the error will go away most of other component is using forwardref so probably that s where the problem lies nope the problem is ts syntaxkind identifier which means parser has issues with const which brings us to wait why is api extractor parsing implementation files instead of declaration types note based on api extractor docs it stops parsing external packages completely after many hours d i finally found the culprit our new dx is leveraging ts path aliases so thats what is happening when executing api extractor lets check the workflow that showcases the issue how to fix this just scripts scope we ll need to provide similar processing like we do for ts task execution which is aware if package is using new dx thus turns off path aliases local build scope we ll need to provide similar logic to just scripts for api extractor local json overrides for react components initially later on for all vnext packages
| 0
|
66,467
| 8,017,701,891
|
IssuesEvent
|
2018-07-25 16:42:23
|
MozillaReality/FirefoxReality
|
https://api.github.com/repos/MozillaReality/FirefoxReality
|
closed
|
Change Focus Mode - Resize Mode Back button to checkmark
|
Design
|
Hardware: Oculus Go
REPRODUCE: Home > Click on Focus Mode Button > Click on Resize Mode Button
CURRENT BEHAVIOR: Back button is an arrow pointing back ← . Slightly confusing and not as satisfying to interact with
EXPECTATION: A button indicating that we are “Finished” resizing
RECOMMENDATION: Change the ← Button to ✓
[Bug-14 Focus Mode Back Button Icon_001.pdf](https://github.com/MozillaReality/FirefoxReality/files/2214772/Bug-14.Focus.Mode.Back.Button.Icon_001.pdf)
|
1.0
|
Change Focus Mode - Resize Mode Back button to checkmark - Hardware: Oculus Go
REPRODUCE: Home > Click on Focus Mode Button > Click on Resize Mode Button
CURRENT BEHAVIOR: Back button is an arrow pointing back ← . Slightly confusing and not as satisfying to interact with
EXPECTATION: A button indicating that we are “Finished” resizing
RECOMMENDATION: Change the ← Button to ✓
[Bug-14 Focus Mode Back Button Icon_001.pdf](https://github.com/MozillaReality/FirefoxReality/files/2214772/Bug-14.Focus.Mode.Back.Button.Icon_001.pdf)
|
non_test
|
change focus mode resize mode back button to checkmark hardware oculus go reproduce home click on focus mode button click on resize mode button current behavior back button is an arrow pointing back ← slightly confusing and not as satisfying to interact with expectation a button indicating that we are “finished” resizing recommendation change the ← button to ✓
| 0
|
101,530
| 8,789,602,990
|
IssuesEvent
|
2018-12-21 04:43:53
|
humera987/FXLabs-Test-Automation
|
https://api.github.com/repos/humera987/FXLabs-Test-Automation
|
closed
|
demo testing 21 : ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound
|
demo testing 21
|
Project : demo testing 21
Job : UAT
Env : UAT
Region : US_WEST
Result : fail
Status Code : 404
Headers : {X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Set-Cookie=[SESSION=ZWFlMzE2MWQtZDZjMi00OTJmLWIwNjEtYmRjNDJhN2ZlYWE4; Path=/; HttpOnly], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Fri, 21 Dec 2018 04:33:20 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/orgs/
Request :
Response :
{
"timestamp" : "2018-12-21T04:33:20.808+0000",
"status" : 404,
"error" : "Not Found",
"message" : "No message available",
"path" : "/api/v1/api/v1/orgs/"
}
Logs :
2018-12-21 04:33:20 ERROR [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : No module found with the name [FXLabs/Common/MongoDB-TimeBound-SQL_Injection_Strings] defined in Fxfile.yaml
2018-12-21 04:33:20 DEBUG [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : URL [http://13.56.210.25/api/v1/api/v1/orgs/]
2018-12-21 04:33:20 DEBUG [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : Method [GET]
2018-12-21 04:33:20 DEBUG [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : Request []
2018-12-21 04:33:20 DEBUG [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : Request-Headers [{Content-Type=[application/json], Accept=[application/json], Authorization=[Basic SHVtZXJhLy9odW1lcmFAZnhsYWJzLmlvOmh1bWVyYTEyMyQ=]}]
2018-12-21 04:33:20 DEBUG [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : Response [{
"timestamp" : "2018-12-21T04:33:20.808+0000",
"status" : 404,
"error" : "Not Found",
"message" : "No message available",
"path" : "/api/v1/api/v1/orgs/"
}]
2018-12-21 04:33:20 DEBUG [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : Response-Headers [{X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Set-Cookie=[SESSION=ZWFlMzE2MWQtZDZjMi00OTJmLWIwNjEtYmRjNDJhN2ZlYWE4; Path=/; HttpOnly], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Fri, 21 Dec 2018 04:33:20 GMT]}]
2018-12-21 04:33:20 DEBUG [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : StatusCode [404]
2018-12-21 04:33:20 DEBUG [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : Time [474]
2018-12-21 04:33:20 DEBUG [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : Size [140]
2018-12-21 04:33:20 INFO [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : Assertion [@ResponseTime < 7000 OR @ResponseTime > 10000] resolved-to [474 < 7000 OR 474 > 10000] result [Passed]
2018-12-21 04:33:20 ERROR [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : Assertion [@StatusCode != 404] resolved-to [404 != 404] result [Failed]
--- FX Bot ---
|
1.0
|
demo testing 21 : ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound - Project : demo testing 21
Job : UAT
Env : UAT
Region : US_WEST
Result : fail
Status Code : 404
Headers : {X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Set-Cookie=[SESSION=ZWFlMzE2MWQtZDZjMi00OTJmLWIwNjEtYmRjNDJhN2ZlYWE4; Path=/; HttpOnly], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Fri, 21 Dec 2018 04:33:20 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/orgs/
Request :
Response :
{
"timestamp" : "2018-12-21T04:33:20.808+0000",
"status" : 404,
"error" : "Not Found",
"message" : "No message available",
"path" : "/api/v1/api/v1/orgs/"
}
Logs :
2018-12-21 04:33:20 ERROR [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : No module found with the name [FXLabs/Common/MongoDB-TimeBound-SQL_Injection_Strings] defined in Fxfile.yaml
2018-12-21 04:33:20 DEBUG [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : URL [http://13.56.210.25/api/v1/api/v1/orgs/]
2018-12-21 04:33:20 DEBUG [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : Method [GET]
2018-12-21 04:33:20 DEBUG [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : Request []
2018-12-21 04:33:20 DEBUG [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : Request-Headers [{Content-Type=[application/json], Accept=[application/json], Authorization=[Basic SHVtZXJhLy9odW1lcmFAZnhsYWJzLmlvOmh1bWVyYTEyMyQ=]}]
2018-12-21 04:33:20 DEBUG [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : Response [{
"timestamp" : "2018-12-21T04:33:20.808+0000",
"status" : 404,
"error" : "Not Found",
"message" : "No message available",
"path" : "/api/v1/api/v1/orgs/"
}]
2018-12-21 04:33:20 DEBUG [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : Response-Headers [{X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Set-Cookie=[SESSION=ZWFlMzE2MWQtZDZjMi00OTJmLWIwNjEtYmRjNDJhN2ZlYWE4; Path=/; HttpOnly], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Fri, 21 Dec 2018 04:33:20 GMT]}]
2018-12-21 04:33:20 DEBUG [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : StatusCode [404]
2018-12-21 04:33:20 DEBUG [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : Time [474]
2018-12-21 04:33:20 DEBUG [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : Size [140]
2018-12-21 04:33:20 INFO [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : Assertion [@ResponseTime < 7000 OR @ResponseTime > 10000] resolved-to [474 < 7000 OR 474 > 10000] result [Passed]
2018-12-21 04:33:20 ERROR [ApiV1OrgsIdGetPathParamIdMongodbNoSqlInjectionTimebound] : Assertion [@StatusCode != 404] resolved-to [404 != 404] result [Failed]
--- FX Bot ---
|
test
|
demo testing project demo testing job uat env uat region us west result fail status code headers x content type options x xss protection cache control pragma expires x frame options set cookie content type transfer encoding date endpoint request response timestamp status error not found message no message available path api api orgs logs error no module found with the name defined in fxfile yaml debug url debug method debug request debug request headers accept authorization debug response timestamp status error not found message no message available path api api orgs debug response headers x xss protection cache control pragma expires x frame options set cookie content type transfer encoding date debug statuscode debug time debug size info assertion resolved to result error assertion resolved to result fx bot
| 1
|
260,407
| 22,618,119,329
|
IssuesEvent
|
2022-06-30 01:44:47
|
radiasoft/sirepo
|
https://api.github.com/repos/radiasoft/sirepo
|
closed
|
make conftest.py _subprocess_start more robust
|
test
|
We could kill processes at startup. The ports should be fixed/configured so they don't collide with existing processes. Make it so if the process crashes for any signal, it stops the supervisor and uwsgi
|
1.0
|
make conftest.py _subprocess_start more robust - We could kill processes at startup. The ports should be fixed/configured so they don't collide with existing processes. Make it so if the process crashes for any signal, it stops the supervisor and uwsgi
|
test
|
make conftest py subprocess start more robust we could kill processes at startup the ports should be fixed configured so they don t collide with existing processes make it so if the process crashes for any signal it stops the supervisor and uwsgi
| 1
|
87,877
| 8,124,777,392
|
IssuesEvent
|
2018-08-16 18:40:23
|
BaristaLabs/BaristaCore
|
https://api.github.com/repos/BaristaLabs/BaristaCore
|
closed
|
Use Coverlet over MSBuild based Code Coverage
|
unit tests
|
The VSTS/MSBuild teams have stated that code coverage is only supported in Visual Studio enterprise despite being a fundamental development necessity.
Use Coverlet(https://github.com/tonerdo/coverlet) in build scripts to generate and submit code coverage to coveralls.
|
1.0
|
Use Coverlet over MSBuild based Code Coverage - The VSTS/MSBuild teams have stated that code coverage is only supported in Visual Studio enterprise despite being a fundamental development necessity.
Use Coverlet(https://github.com/tonerdo/coverlet) in build scripts to generate and submit code coverage to coveralls.
|
test
|
use coverlet over msbuild based code coverage the vsts msbuild teams have stated that code coverage is only supported in visual studio enterprise despite being a fundamental development necessity use coverlet in build scripts to generate and submit code coverage to coveralls
| 1
|
136,685
| 11,072,537,756
|
IssuesEvent
|
2019-12-12 10:29:40
|
scylladb/scylla
|
https://api.github.com/repos/scylladb/scylla
|
closed
|
big_table_with_ttls_test AssertionError: Expected 100000 rows in the big partition, but received 98974
|
dtest
|
Scylla version b4cf429aab0407422818460f7714eef3232714b2
Seen in [next/1190/testReport/junit/migration_test/TTLWithMigrate/big_table_with_ttls_test](https://jenkins.scylladb.com/view/master/job/scylla-master/job/next/1190/testReport/junit/migration_test/TTLWithMigrate/big_table_with_ttls_test):
```
Error Message
Expected 100000 rows in the big partition, but received 98974
Stacktrace
Traceback (most recent call last):
File "/usr/lib64/python2.7/unittest/case.py", line 367, in run
testMethod()
File "/jenkins/workspace/scylla-master/next/scylla-dtest/migration_test.py", line 933, in big_table_with_ttls_test
'{scylla_big_partition_count}'.format(**locals()))
File "/usr/lib64/python2.7/unittest/case.py", line 460, in assertTrue
raise self.failureException(msg)
AssertionError: Expected 100000 rows in the big partition, but received 98974
```
|
1.0
|
big_table_with_ttls_test AssertionError: Expected 100000 rows in the big partition, but received 98974 - Scylla version b4cf429aab0407422818460f7714eef3232714b2
Seen in [next/1190/testReport/junit/migration_test/TTLWithMigrate/big_table_with_ttls_test](https://jenkins.scylladb.com/view/master/job/scylla-master/job/next/1190/testReport/junit/migration_test/TTLWithMigrate/big_table_with_ttls_test):
```
Error Message
Expected 100000 rows in the big partition, but received 98974
Stacktrace
Traceback (most recent call last):
File "/usr/lib64/python2.7/unittest/case.py", line 367, in run
testMethod()
File "/jenkins/workspace/scylla-master/next/scylla-dtest/migration_test.py", line 933, in big_table_with_ttls_test
'{scylla_big_partition_count}'.format(**locals()))
File "/usr/lib64/python2.7/unittest/case.py", line 460, in assertTrue
raise self.failureException(msg)
AssertionError: Expected 100000 rows in the big partition, but received 98974
```
|
test
|
big table with ttls test assertionerror expected rows in the big partition but received scylla version seen in error message expected rows in the big partition but received stacktrace traceback most recent call last file usr unittest case py line in run testmethod file jenkins workspace scylla master next scylla dtest migration test py line in big table with ttls test scylla big partition count format locals file usr unittest case py line in asserttrue raise self failureexception msg assertionerror expected rows in the big partition but received
| 1
|
18,875
| 3,728,804,218
|
IssuesEvent
|
2016-03-07 02:55:23
|
QubesOS/qubes-issues
|
https://api.github.com/repos/QubesOS/qubes-issues
|
closed
|
Create mechanism for plugging tests from the outside of core-admin repository
|
C: core C: tests task
|
It is really convenient to have a single test runner to launch all the Qubes tests. But some of them are barely related to `core-admin` repository (for example split GPG). Additionally (especially for qubes-app-*) it would be useful to have the same test running on any Qubes version (supported by such component).
This means that we need some API to allow tests from other repositories to be plugged into test runner (`qubes.tests.run` module). As discussed in #1368 we've settled on using entry points for that and providing some minimal stable API for creating VMs for the test purposes.
## The API
External test case needs to expose entry point(s). Currently supported two of them:
- `qubes.tests.extra` - test should be instantiated once
- `qubes.tests.extra.for_template` - test should be instantiated for every template (generally should be used to testing some VM software)
Each of those entry points should be a function, which will return a list of classes derived from `unittest.TestCase`. This class will be mixed with Qubes-version specific class providing basic API for handling VMs:
- `create_vms(names)` - create AppVMs with names given as a parameter (iterable of names); return list of created objects
- `enable_network()` - created VMs should have access to the network (if available on the host)
- `qrexec_policy(service, source, destination)` - allow qrexec calls described by parameters
- `shutdown_and_wait(vm, timeout=60)` - ask given VM (VM object) to shutdown and wait for it to finish
- `remove_vms(vms)` - remove VMs (list of VM objects)
- `save_and_reload_db()` - ensure the changes are written to the disk (`create_vms` and `remove_vms` call it automatically, but if you make any additional changes, you need to call it on your own)
Additionally some useful functions are available:
- `wait_for_window(title, timeout=30, show=True)` - wait for given window to show (or hide if `show=False`)
- `enter_keys_in_window(title, keys)` - enter given keys into given window
Test case should take care of any other API compatibility on its own. In case of not supported API detected, it should call `self.skipTest` with appropriate message. For example:
```
try:
vm.some_core_dependent_function(or_, core, dependent, params)
except (AttributeError, TypeError):
self.skip('core API mismatch')
```
|
1.0
|
Create mechanism for plugging tests from the outside of core-admin repository - It is really convenient to have a single test runner to launch all the Qubes tests. But some of them are barely related to `core-admin` repository (for example split GPG). Additionally (especially for qubes-app-*) it would be useful to have the same test running on any Qubes version (supported by such component).
This means that we need some API to allow tests from other repositories to be plugged into test runner (`qubes.tests.run` module). As discussed in #1368 we've settled on using entry points for that and providing some minimal stable API for creating VMs for the test purposes.
## The API
External test case needs to expose entry point(s). Currently supported two of them:
- `qubes.tests.extra` - test should be instantiated once
- `qubes.tests.extra.for_template` - test should be instantiated for every template (generally should be used to testing some VM software)
Each of those entry points should be a function, which will return a list of classes derived from `unittest.TestCase`. This class will be mixed with Qubes-version specific class providing basic API for handling VMs:
- `create_vms(names)` - create AppVMs with names given as a parameter (iterable of names); return list of created objects
- `enable_network()` - created VMs should have access to the network (if available on the host)
- `qrexec_policy(service, source, destination)` - allow qrexec calls described by parameters
- `shutdown_and_wait(vm, timeout=60)` - ask given VM (VM object) to shutdown and wait for it to finish
- `remove_vms(vms)` - remove VMs (list of VM objects)
- `save_and_reload_db()` - ensure the changes are written to the disk (`create_vms` and `remove_vms` call it automatically, but if you make any additional changes, you need to call it on your own)
Additionally some useful functions are available:
- `wait_for_window(title, timeout=30, show=True)` - wait for given window to show (or hide if `show=False`)
- `enter_keys_in_window(title, keys)` - enter given keys into given window
Test case should take care of any other API compatibility on its own. In case of not supported API detected, it should call `self.skipTest` with appropriate message. For example:
```
try:
vm.some_core_dependent_function(or_, core, dependent, params)
except (AttributeError, TypeError):
self.skip('core API mismatch')
```
|
test
|
create mechanism for plugging tests from the outside of core admin repository it is really convenient to have a single test runner to launch all the qubes tests but some of them are barely related to core admin repository for example split gpg additionally especially for qubes app it would be useful to have the same test running on any qubes version supported by such component this means that we need some api to allow tests from other repositories to be plugged into test runner qubes tests run module as discussed in we ve settled on using entry points for that and providing some minimal stable api for creating vms for the test purposes the api external test case needs to expose entry point s currently supported two of them qubes tests extra test should be instantiated once qubes tests extra for template test should be instantiated for every template generally should be used to testing some vm software each of those entry points should be a function which will return a list of classes derived from unittest testcase this class will be mixed with qubes version specific class providing basic api for handling vms create vms names create appvms with names given as a parameter iterable of names return list of created objects enable network created vms should have access to the network if available on the host qrexec policy service source destination allow qrexec calls described by parameters shutdown and wait vm timeout ask given vm vm object to shutdown and wait for it to finish remove vms vms remove vms list of vm objects save and reload db ensure the changes are written to the disk create vms and remove vms call it automatically but if you make any additional changes you need to call it on your own additionally some useful functions are available wait for window title timeout show true wait for given window to show or hide if show false enter keys in window title keys enter given keys into given window test case should take care of any other api compatibility on its own in case of not supported api detected it should call self skiptest with appropriate message for example try vm some core dependent function or core dependent params except attributeerror typeerror self skip core api mismatch
| 1
|
23,590
| 3,857,685,175
|
IssuesEvent
|
2016-04-07 07:30:44
|
narendra-addweb/SwitchedOn
|
https://api.github.com/repos/narendra-addweb/SwitchedOn
|
closed
|
Testimonial
|
Design Pending
|
Responsive iPad(Landscape & Portrait) Browser : Safari
1. The banner content is colliding with the image .
|
1.0
|
Testimonial - Responsive iPad(Landscape & Portrait) Browser : Safari
1. The banner content is colliding with the image .
|
non_test
|
testimonial responsive ipad landscape portrait browser safari the banner content is colliding with the image
| 0
|
129
| 2,533,633,116
|
IssuesEvent
|
2015-01-24 02:04:51
|
IroncladGames/SinsOfADarkAge
|
https://api.github.com/repos/IroncladGames/SinsOfADarkAge
|
closed
|
Virtual vs. Exclusive Performance Issues
|
Performance
|
Virtual Fullscreen for me cuts 15-30 FPS for me.
In Virtual, my FPS varies from 30-46
.
.
.
In Exclusive my FPS varies from 52-58
I'm going to try the Setting Folder fix and see if that affects Virtual's performance. (Same FPS numbers with new Setting Folder.)
(Water, shadows, aa turned off on both.)
|
True
|
Virtual vs. Exclusive Performance Issues - Virtual Fullscreen for me cuts 15-30 FPS for me.
In Virtual, my FPS varies from 30-46
.
.
.
In Exclusive my FPS varies from 52-58
I'm going to try the Setting Folder fix and see if that affects Virtual's performance. (Same FPS numbers with new Setting Folder.)
(Water, shadows, aa turned off on both.)
|
non_test
|
virtual vs exclusive performance issues virtual fullscreen for me cuts fps for me in virtual my fps varies from in exclusive my fps varies from i m going to try the setting folder fix and see if that affects virtual s performance same fps numbers with new setting folder water shadows aa turned off on both
| 0
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.