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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2,452
| 2,732,059,658
|
IssuesEvent
|
2015-04-17 01:01:41
|
winjs/winjs
|
https://api.github.com/repos/winjs/winjs
|
closed
|
AutoSuggestBox: Update suggestion flyout positioning logic when IME is open
|
..pri: 1 .kind: codebug feature: autosuggestbox
|
The current logic for position the flyout is:
```js
if (ime.width > ime.height) {
// Push down
} else {
// Push right
}
```
The new logic should be:
```js
if (ime.width < 0.45 * asb.width) {
// Push right
} else {
// Push down
}
|
1.0
|
AutoSuggestBox: Update suggestion flyout positioning logic when IME is open - The current logic for position the flyout is:
```js
if (ime.width > ime.height) {
// Push down
} else {
// Push right
}
```
The new logic should be:
```js
if (ime.width < 0.45 * asb.width) {
// Push right
} else {
// Push down
}
|
non_test
|
autosuggestbox update suggestion flyout positioning logic when ime is open the current logic for position the flyout is js if ime width ime height push down else push right the new logic should be js if ime width asb width push right else push down
| 0
|
193,460
| 14,653,577,361
|
IssuesEvent
|
2020-12-28 06:23:01
|
sebastianbergmann/phpunit
|
https://api.github.com/repos/sebastianbergmann/phpunit
|
closed
|
symbolicly linked phpunit.xml is not handled properly
|
feature/test-runner type/bug
|
ORIGINAL ISSUE WAS CLOSED: https://github.com/sebastianbergmann/phpunit/issues/4428
<!--
- Please do not report an issue for a version of PHPUnit that is no longer supported. A list of currently supported versions of PHPUnit is available at https://phpunit.de/supported-versions.html.
- Please do not report an issue if you are using a version of PHP that is not supported by the version of PHPUnit you are using. A list that shows which version of PHP is supported by which version of PHPUnit is available at https://phpunit.de/supported-versions.html.
- Please fill in this template according to your issue.
- Please keep the table shown below at the top of your issue.
- Please include the output of "composer info | sort" if you installed PHPUnit using Composer.
- Please post code as text (using proper markup). Do not post screenshots of code.
- Visit https://phpunit.de/support.html if you are looking for support.
- Please remove this comment before submitting your issue.
-->
| Q | A
| --------------------| ---------------
| PHPUnit version | 9.3.7 (tested against 8.5.8 too with same results)
| PHP version | 7.4.9
| Installation Method | Composer
```
$ composer info | sort | grep phpunit
phpunit/php-code-coverage 9.1.4 Library that provides collection, processing, and rendering functionality for PHP code coverage...
phpunit/php-file-iterator 3.0.4 FilterIterator implementation that filters files based on a list of suffixes.
phpunit/php-invoker 3.1.0 Invoke callables with a timeout
phpunit/php-text-template 2.0.2 Simple template engine.
phpunit/php-timer 5.0.1 Utility class for timing
phpunit/phpunit 9.3.7 The PHP Unit Testing framework.
```
#### Summary
When phpunit.xml is a symbolic link, phpunit follows the link to the source, and tries to execute from the source location.
#### Current behavior
Below is the file structure.
```
/
home/
arderyp/
phpunit/
shared/
phpunit.xml
repo/
phpunit.xml -> /var/www/shared/phpunit.xml
```
This is a common structure used by many deployment systems, including [PHP Deployer](https://deployer.org/). When trying to execute phpunit from `/var/www/repo`, it fails because it looks for `/var/www/shared/vendor/autoload.php` instead of `/var/www/repo/vendor/autoload.php`. The problem is resolved by swapping the real file in for the symbolic link:
```
cd /home/arderyp/phpunit/repo
rm phpunit.xml && cp ../shared/phpunit.xml .
```
#### How to reproduce
```
## phpunit.xml content, we reference this later in the process
<?xml version="1.0" encoding="UTF-8"?>
<!-- https://phpunit.de/manual/current/en/appendixes.configuration.html -->
<phpunit xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="https://schema.phpunit.de/9.3/phpunit.xsd" backupGlobals="false" colors="true" bootstrap="vendor/autoload.php">
<coverage>
<include>
<directory>./src/</directory>
</include>
</coverage>
<php>
<ini force="true" name="error_reporting" value="-1"/>
</php>
<testsuites>
<testsuite name="symbolic link fails demo">
<directory>tests/</directory>
</testsuite>
</testsuites>
</phpunit>
## Reproduce the issue
$ mkdir phpunit
$ mkdir phpunit/shared
$ mkdir phpunit/repo
$ cd phpunit/repo
$ composer init
...
$ composer require phpunit/phpunit
...
# create phpunit.xml using the example block above
$ vendor/bin/phpunit
PHPUnit 9.3.7 by Sebastian Bergmann and contributors.
No tests executed!
$ mv phpunit.xml ../shared && ln -s ../shared/phpunit.xml .
$ vendor/bin/phpunit
PHPUnit 9.3.7 by Sebastian Bergmann and contributors.
Cannot open file "/home/arderyp/phpunit/shared/vendor/autoload.php".
```
#### Expected behavior
Execute phpunit from location of `phpunit.xml` (even if it is a link). Just trust the found location of `phpunit.xml`, and don't follow to its target location if it is link.
|
1.0
|
symbolicly linked phpunit.xml is not handled properly - ORIGINAL ISSUE WAS CLOSED: https://github.com/sebastianbergmann/phpunit/issues/4428
<!--
- Please do not report an issue for a version of PHPUnit that is no longer supported. A list of currently supported versions of PHPUnit is available at https://phpunit.de/supported-versions.html.
- Please do not report an issue if you are using a version of PHP that is not supported by the version of PHPUnit you are using. A list that shows which version of PHP is supported by which version of PHPUnit is available at https://phpunit.de/supported-versions.html.
- Please fill in this template according to your issue.
- Please keep the table shown below at the top of your issue.
- Please include the output of "composer info | sort" if you installed PHPUnit using Composer.
- Please post code as text (using proper markup). Do not post screenshots of code.
- Visit https://phpunit.de/support.html if you are looking for support.
- Please remove this comment before submitting your issue.
-->
| Q | A
| --------------------| ---------------
| PHPUnit version | 9.3.7 (tested against 8.5.8 too with same results)
| PHP version | 7.4.9
| Installation Method | Composer
```
$ composer info | sort | grep phpunit
phpunit/php-code-coverage 9.1.4 Library that provides collection, processing, and rendering functionality for PHP code coverage...
phpunit/php-file-iterator 3.0.4 FilterIterator implementation that filters files based on a list of suffixes.
phpunit/php-invoker 3.1.0 Invoke callables with a timeout
phpunit/php-text-template 2.0.2 Simple template engine.
phpunit/php-timer 5.0.1 Utility class for timing
phpunit/phpunit 9.3.7 The PHP Unit Testing framework.
```
#### Summary
When phpunit.xml is a symbolic link, phpunit follows the link to the source, and tries to execute from the source location.
#### Current behavior
Below is the file structure.
```
/
home/
arderyp/
phpunit/
shared/
phpunit.xml
repo/
phpunit.xml -> /var/www/shared/phpunit.xml
```
This is a common structure used by many deployment systems, including [PHP Deployer](https://deployer.org/). When trying to execute phpunit from `/var/www/repo`, it fails because it looks for `/var/www/shared/vendor/autoload.php` instead of `/var/www/repo/vendor/autoload.php`. The problem is resolved by swapping the real file in for the symbolic link:
```
cd /home/arderyp/phpunit/repo
rm phpunit.xml && cp ../shared/phpunit.xml .
```
#### How to reproduce
```
## phpunit.xml content, we reference this later in the process
<?xml version="1.0" encoding="UTF-8"?>
<!-- https://phpunit.de/manual/current/en/appendixes.configuration.html -->
<phpunit xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="https://schema.phpunit.de/9.3/phpunit.xsd" backupGlobals="false" colors="true" bootstrap="vendor/autoload.php">
<coverage>
<include>
<directory>./src/</directory>
</include>
</coverage>
<php>
<ini force="true" name="error_reporting" value="-1"/>
</php>
<testsuites>
<testsuite name="symbolic link fails demo">
<directory>tests/</directory>
</testsuite>
</testsuites>
</phpunit>
## Reproduce the issue
$ mkdir phpunit
$ mkdir phpunit/shared
$ mkdir phpunit/repo
$ cd phpunit/repo
$ composer init
...
$ composer require phpunit/phpunit
...
# create phpunit.xml using the example block above
$ vendor/bin/phpunit
PHPUnit 9.3.7 by Sebastian Bergmann and contributors.
No tests executed!
$ mv phpunit.xml ../shared && ln -s ../shared/phpunit.xml .
$ vendor/bin/phpunit
PHPUnit 9.3.7 by Sebastian Bergmann and contributors.
Cannot open file "/home/arderyp/phpunit/shared/vendor/autoload.php".
```
#### Expected behavior
Execute phpunit from location of `phpunit.xml` (even if it is a link). Just trust the found location of `phpunit.xml`, and don't follow to its target location if it is link.
|
test
|
symbolicly linked phpunit xml is not handled properly original issue was closed please do not report an issue for a version of phpunit that is no longer supported a list of currently supported versions of phpunit is available at please do not report an issue if you are using a version of php that is not supported by the version of phpunit you are using a list that shows which version of php is supported by which version of phpunit is available at please fill in this template according to your issue please keep the table shown below at the top of your issue please include the output of composer info sort if you installed phpunit using composer please post code as text using proper markup do not post screenshots of code visit if you are looking for support please remove this comment before submitting your issue q a phpunit version tested against too with same results php version installation method composer composer info sort grep phpunit phpunit php code coverage library that provides collection processing and rendering functionality for php code coverage phpunit php file iterator filteriterator implementation that filters files based on a list of suffixes phpunit php invoker invoke callables with a timeout phpunit php text template simple template engine phpunit php timer utility class for timing phpunit phpunit the php unit testing framework summary when phpunit xml is a symbolic link phpunit follows the link to the source and tries to execute from the source location current behavior below is the file structure home arderyp phpunit shared phpunit xml repo phpunit xml var www shared phpunit xml this is a common structure used by many deployment systems including when trying to execute phpunit from var www repo it fails because it looks for var www shared vendor autoload php instead of var www repo vendor autoload php the problem is resolved by swapping the real file in for the symbolic link cd home arderyp phpunit repo rm phpunit xml cp shared phpunit xml how to reproduce phpunit xml content we reference this later in the process src tests reproduce the issue mkdir phpunit mkdir phpunit shared mkdir phpunit repo cd phpunit repo composer init composer require phpunit phpunit create phpunit xml using the example block above vendor bin phpunit phpunit by sebastian bergmann and contributors no tests executed mv phpunit xml shared ln s shared phpunit xml vendor bin phpunit phpunit by sebastian bergmann and contributors cannot open file home arderyp phpunit shared vendor autoload php expected behavior execute phpunit from location of phpunit xml even if it is a link just trust the found location of phpunit xml and don t follow to its target location if it is link
| 1
|
226,063
| 17,937,553,020
|
IssuesEvent
|
2021-09-10 17:20:55
|
apache/trafficcontrol
|
https://api.github.com/repos/apache/trafficcontrol
|
closed
|
TO API Tests GHA still starts Riak container
|
Traffic Ops tests improvement automation
|
<!--
************ STOP!! ************
If this issue identifies a security vulnerability, DO NOT submit it! Instead, contact
the Apache Traffic Control Security Team at security@trafficcontrol.apache.org and follow the
guidelines at https://www.apache.org/security/ regarding vulnerability disclosure.
- For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack (https://s.apache.org/slack-invite)
or Traffic Control mailing lists (https://trafficcontrol.apache.org/mailing_lists).
- Before submitting, please **SEARCH GITHUB** for a similar issue or PR.
-->
## I'm submitting a ...
<!-- delete all those that don't apply -->
<!--- security vulnerability (STOP!! - see above)-->
- improvement request (usability, performance, tech debt, etc.)
## Traffic Control components affected ...
<!-- delete all those that don't apply -->
- GitHub Actions
## Current behavior:
<!-- Describe how the current features are insufficient. -->
The *to-integration-tests* GitHub Action starts but does not use a Riak Docker container.
## New behavior:
<!-- Describe how the feature would improve Traffic Control -->
The Riak container should be removed.
## Minimal reproduction of the problem with instructions:
<!--
If you can illustrate your feature request better with an example, please
provide the *STEPS TO REPRODUCE* and include the applicable TC version.
If not, feel free to delete this section.
-->
https://github.com/apache/trafficcontrol/blob/295c31e3467d13163ec4a3f87fac5450389801ec/.github/actions/to-integration-tests/entrypoint.sh#L87-L92
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
https://apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
|
1.0
|
TO API Tests GHA still starts Riak container - <!--
************ STOP!! ************
If this issue identifies a security vulnerability, DO NOT submit it! Instead, contact
the Apache Traffic Control Security Team at security@trafficcontrol.apache.org and follow the
guidelines at https://www.apache.org/security/ regarding vulnerability disclosure.
- For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack (https://s.apache.org/slack-invite)
or Traffic Control mailing lists (https://trafficcontrol.apache.org/mailing_lists).
- Before submitting, please **SEARCH GITHUB** for a similar issue or PR.
-->
## I'm submitting a ...
<!-- delete all those that don't apply -->
<!--- security vulnerability (STOP!! - see above)-->
- improvement request (usability, performance, tech debt, etc.)
## Traffic Control components affected ...
<!-- delete all those that don't apply -->
- GitHub Actions
## Current behavior:
<!-- Describe how the current features are insufficient. -->
The *to-integration-tests* GitHub Action starts but does not use a Riak Docker container.
## New behavior:
<!-- Describe how the feature would improve Traffic Control -->
The Riak container should be removed.
## Minimal reproduction of the problem with instructions:
<!--
If you can illustrate your feature request better with an example, please
provide the *STEPS TO REPRODUCE* and include the applicable TC version.
If not, feel free to delete this section.
-->
https://github.com/apache/trafficcontrol/blob/295c31e3467d13163ec4a3f87fac5450389801ec/.github/actions/to-integration-tests/entrypoint.sh#L87-L92
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
https://apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
|
test
|
to api tests gha still starts riak container stop if this issue identifies a security vulnerability do not submit it instead contact the apache traffic control security team at security trafficcontrol apache org and follow the guidelines at regarding vulnerability disclosure for support questions use the traffic control channel on the asf slack or traffic control mailing lists before submitting please search github for a similar issue or pr i m submitting a improvement request usability performance tech debt etc traffic control components affected github actions current behavior the to integration tests github action starts but does not use a riak docker container new behavior the riak container should be removed minimal reproduction of the problem with instructions if you can illustrate your feature request better with an example please provide the steps to reproduce and include the applicable tc version if not feel free to delete this section licensed to the apache software foundation asf under one or more contributor license agreements see the notice file distributed with this work for additional information regarding copyright ownership the asf licenses this file to you under the apache license version the license you may not use this file except in compliance with the license you may obtain a copy of the license at unless required by applicable law or agreed to in writing software distributed under the license is distributed on an as is basis without warranties or conditions of any kind either express or implied see the license for the specific language governing permissions and limitations under the license
| 1
|
291,675
| 25,165,969,191
|
IssuesEvent
|
2022-11-10 20:53:04
|
onc-healthit/onc-certification-g10-test-kit
|
https://api.github.com/repos/onc-healthit/onc-certification-g10-test-kit
|
closed
|
Search Parameter Validation for Date Parameters is Too Strict (FI-1738)
|
us-core-test-kit v3.2.0
|
As part of the US Core 3.1.1 test cases, Inferno validates that the server supports required search parameters. For date search parameters, Inferno validates that the returned search results matches the provided search criteria (e.g. searching for date=gt2022-09-17 doesn't return results where date = 2010-01-01).
For cases where the server returns date only elements (e.g. 2022-09-16) with no time portion, Inferno uses midnight UTC for subsequent search parameter validation (e.g. 2022-09-17T00:00:00+00:00). This may trigger test case failures, even though the results are expected.
For example, our FHIR server is returning the attached search results for Procedures - one with a performedDateTime of 2022-09-18, and another with a performedDateTime of 2022-09-16. On test case 4.26.02 (Procedure search by patient + date), Inferno is querying the server for Procedure?patient=<...>&date=gt2022-09-17T00:00:00+00:00. Our server responds to this search with both Procedures, as 2022-09-16 in server time zone (central time) is within the specified range. However, Inferno throws an error in this scenario:
{
"resourceType": "Bundle",
"type": "searchset",
"total": 2,
"link": [
{
"relation": "self",
"url": https://connectathon.epic.com/Interconnect-FHIR-OAuth/api/FHIR/R4/Procedure?date=gt2022-09-17T00:00:00%2B00:00&patient=eO6oPEoiC084jCETqSU7y-w3
}
],
"entry": [
{
"link": [
{
"relation": "self",
"url": https://connectathon.epic.com/Interconnect-FHIR-OAuth/api/FHIR/R4/Procedure/f8Pl7wa5Xi.4P-cmG1ErpsMjfAmN29s-jQtlK9onxUIM4
}
],
"fullUrl": https://connectathon.epic.com/Interconnect-FHIR-OAuth/api/FHIR/R4/Procedure/f8Pl7wa5Xi.4P-cmG1ErpsMjfAmN29s-jQtlK9onxUIM4,
"resource": {
"resourceType": "Procedure",
"id": "f8Pl7wa5Xi.4P-cmG1ErpsMjfAmN29s-jQtlK9onxUIM4",
"identifier": [
{
"use": "usual",
"type": {
"text": "ORD"
},
"system": "urn:oid:1.2.840.114350.1.13.1.1.7.2.798268",
"value": "1000295574"
},
{
"use": "usual",
"type": {
"text": "EAP"
},
"system": "urn:oid:1.2.840.114350.1.13.1.1.7.2.696580",
"value": "10118"
}
],
"status": "completed",
"category": {
"coding": [
{
"system": http://snomed.info/sct,
"code": "103693007",
"display": "Diagnostic procedure"
}
],
"text": "Ordered Procedures"
},
"code": {
"coding": [
{
"system": "urn:oid:2.16.840.1.113883.6.14",
"code": "G0047",
"display": "PET FOLLOW STRESS ECG MULT"
}
],
"text": "PET FOLLOW STRESS ECG MULT"
},
"subject": {
"reference": "Patient/eO6oPEoiC084jCETqSU7y-w3",
"display": "Kid, Aiden Jr."
},
"encounter": {
"reference": "Encounter/e1QDDhX1HbcvEGeAksCj1qA3",
"identifier": {
"use": "usual",
"system": "urn:oid:1.2.840.114350.1.13.1.1.7.3.698084.8",
"value": "2"
},
"display": "Office Visit"
},
"performedDateTime": "2022-09-18",
"recorder": {
"reference": "Practitioner/eQ.c9ZqRHPt1hds3Heosjxg3",
"type": "Practitioner",
"display": "Dr. A Adams"
},
"asserter": {
"reference": "Practitioner/eQ.c9ZqRHPt1hds3Heosjxg3",
"type": "Practitioner",
"display": "Dr. A Adams"
},
"report": [
{
"reference": "DiagnosticReport/e3CfO45auMOlOrF5Pg3Jzz447ePL9TW5BLyx5fxWuyj03",
"type": "DiagnosticReport",
"display": "PET FOLLOW STRESS ECG MULT"
}
]
},
"search": {
"mode": "match"
}
},
{
"link": [
{
"relation": "self",
"url": https://connectathon.epic.com/Interconnect-FHIR-OAuth/api/FHIR/R4/Procedure/fuNg6J-rBwdUADpGaRCWm-eyYufR0gPMmO1G8qw1TCTs4
}
],
"fullUrl": https://connectathon.epic.com/Interconnect-FHIR-OAuth/api/FHIR/R4/Procedure/fuNg6J-rBwdUADpGaRCWm-eyYufR0gPMmO1G8qw1TCTs4,
"resource": {
"resourceType": "Procedure",
"id": "fuNg6J-rBwdUADpGaRCWm-eyYufR0gPMmO1G8qw1TCTs4",
"identifier": [
{
"use": "usual",
"type": {
"text": "ORD"
},
"system": "urn:oid:1.2.840.114350.1.13.1.1.7.2.798268",
"value": "1000295569"
},
{
"use": "usual",
"type": {
"text": "EAP"
},
"system": "urn:oid:1.2.840.114350.1.13.1.1.7.2.696580",
"value": "5532"
}
],
"status": "completed",
"category": {
"coding": [
{
"system": http://snomed.info/sct,
"code": "103693007",
"display": "Diagnostic procedure"
}
],
"text": "Ordered Procedures"
},
"code": {
"coding": [
{
"system": http://www.ama-assn.org/go/cpt,
"code": "73560",
"display": "X-RAY KNEE 1 OR 2 VIEW"
}
],
"text": "X-RAY KNEE 2 VW"
},
"subject": {
"reference": "Patient/eO6oPEoiC084jCETqSU7y-w3",
"display": "Kid, Aiden Jr."
},
"encounter": {
"reference": "Encounter/e1QDDhX1HbcvEGeAksCj1qA3",
"identifier": {
"use": "usual",
"system": "urn:oid:1.2.840.114350.1.13.1.1.7.3.698084.8",
"value": "2"
},
"display": "Office Visit"
},
"performedDateTime": "2022-09-16",
"recorder": {
"reference": "Practitioner/euJOUNeZyX6mofWELWG0Ibg3",
"type": "Practitioner",
"display": "Dr. S Provider"
},
"asserter": {
"reference": "Practitioner/euJOUNeZyX6mofWELWG0Ibg3",
"type": "Practitioner",
"display": "Dr. S Provider"
},
"report": [
{
"reference": "DiagnosticReport/eFHRJNokw1YYrLudlWiHIBTGppy7tmBr6EF63aOWt1io3",
"type": "DiagnosticReport",
"display": "X-RAY KNEE 2 VW"
}
]
},
"search": {
"mode": "match"
}
},
{
"fullUrl": "urn:uuid:00000000-0000-2526-6a7d-d67bc0b3e258",
"resource": {
"resourceType": "OperationOutcome",
"issue": [
{
"severity": "warning",
"code": "suppressed",
"details": {
"coding": [
{
"system": "urn:oid:1.2.840.114350.1.13.1.1.7.2.657369",
"code": "59204",
"display": "The authenticated client's search request applies to a sub-resource that the client is not authorized for. Results of this sub-type will not be returned."
}
],
"text": "The authenticated client's search request applies to a sub-resource that the client is not authorized for. Results of this sub-type will not be returned."
},
"diagnostics": "Client not authorized for Procedure - Patient-Reported Surgical History. Search results of this type have not been included."
},
{
"severity": "warning",
"code": "processing",
"details": {
"coding": [
{
"system": "urn:oid:1.2.840.114350.1.13.1.1.7.2.657369",
"code": "4119",
"display": "This response includes information available to the authorized user at the time of the request. It may not contain the entire record available in the system."
}
],
"text": "This response includes information available to the authorized user at the time of the request. It may not contain the entire record available in the system."
}
}
]
},
"search": {
"mode": "outcome"
}
}
]
}
|
1.0
|
Search Parameter Validation for Date Parameters is Too Strict (FI-1738) - As part of the US Core 3.1.1 test cases, Inferno validates that the server supports required search parameters. For date search parameters, Inferno validates that the returned search results matches the provided search criteria (e.g. searching for date=gt2022-09-17 doesn't return results where date = 2010-01-01).
For cases where the server returns date only elements (e.g. 2022-09-16) with no time portion, Inferno uses midnight UTC for subsequent search parameter validation (e.g. 2022-09-17T00:00:00+00:00). This may trigger test case failures, even though the results are expected.
For example, our FHIR server is returning the attached search results for Procedures - one with a performedDateTime of 2022-09-18, and another with a performedDateTime of 2022-09-16. On test case 4.26.02 (Procedure search by patient + date), Inferno is querying the server for Procedure?patient=<...>&date=gt2022-09-17T00:00:00+00:00. Our server responds to this search with both Procedures, as 2022-09-16 in server time zone (central time) is within the specified range. However, Inferno throws an error in this scenario:
{
"resourceType": "Bundle",
"type": "searchset",
"total": 2,
"link": [
{
"relation": "self",
"url": https://connectathon.epic.com/Interconnect-FHIR-OAuth/api/FHIR/R4/Procedure?date=gt2022-09-17T00:00:00%2B00:00&patient=eO6oPEoiC084jCETqSU7y-w3
}
],
"entry": [
{
"link": [
{
"relation": "self",
"url": https://connectathon.epic.com/Interconnect-FHIR-OAuth/api/FHIR/R4/Procedure/f8Pl7wa5Xi.4P-cmG1ErpsMjfAmN29s-jQtlK9onxUIM4
}
],
"fullUrl": https://connectathon.epic.com/Interconnect-FHIR-OAuth/api/FHIR/R4/Procedure/f8Pl7wa5Xi.4P-cmG1ErpsMjfAmN29s-jQtlK9onxUIM4,
"resource": {
"resourceType": "Procedure",
"id": "f8Pl7wa5Xi.4P-cmG1ErpsMjfAmN29s-jQtlK9onxUIM4",
"identifier": [
{
"use": "usual",
"type": {
"text": "ORD"
},
"system": "urn:oid:1.2.840.114350.1.13.1.1.7.2.798268",
"value": "1000295574"
},
{
"use": "usual",
"type": {
"text": "EAP"
},
"system": "urn:oid:1.2.840.114350.1.13.1.1.7.2.696580",
"value": "10118"
}
],
"status": "completed",
"category": {
"coding": [
{
"system": http://snomed.info/sct,
"code": "103693007",
"display": "Diagnostic procedure"
}
],
"text": "Ordered Procedures"
},
"code": {
"coding": [
{
"system": "urn:oid:2.16.840.1.113883.6.14",
"code": "G0047",
"display": "PET FOLLOW STRESS ECG MULT"
}
],
"text": "PET FOLLOW STRESS ECG MULT"
},
"subject": {
"reference": "Patient/eO6oPEoiC084jCETqSU7y-w3",
"display": "Kid, Aiden Jr."
},
"encounter": {
"reference": "Encounter/e1QDDhX1HbcvEGeAksCj1qA3",
"identifier": {
"use": "usual",
"system": "urn:oid:1.2.840.114350.1.13.1.1.7.3.698084.8",
"value": "2"
},
"display": "Office Visit"
},
"performedDateTime": "2022-09-18",
"recorder": {
"reference": "Practitioner/eQ.c9ZqRHPt1hds3Heosjxg3",
"type": "Practitioner",
"display": "Dr. A Adams"
},
"asserter": {
"reference": "Practitioner/eQ.c9ZqRHPt1hds3Heosjxg3",
"type": "Practitioner",
"display": "Dr. A Adams"
},
"report": [
{
"reference": "DiagnosticReport/e3CfO45auMOlOrF5Pg3Jzz447ePL9TW5BLyx5fxWuyj03",
"type": "DiagnosticReport",
"display": "PET FOLLOW STRESS ECG MULT"
}
]
},
"search": {
"mode": "match"
}
},
{
"link": [
{
"relation": "self",
"url": https://connectathon.epic.com/Interconnect-FHIR-OAuth/api/FHIR/R4/Procedure/fuNg6J-rBwdUADpGaRCWm-eyYufR0gPMmO1G8qw1TCTs4
}
],
"fullUrl": https://connectathon.epic.com/Interconnect-FHIR-OAuth/api/FHIR/R4/Procedure/fuNg6J-rBwdUADpGaRCWm-eyYufR0gPMmO1G8qw1TCTs4,
"resource": {
"resourceType": "Procedure",
"id": "fuNg6J-rBwdUADpGaRCWm-eyYufR0gPMmO1G8qw1TCTs4",
"identifier": [
{
"use": "usual",
"type": {
"text": "ORD"
},
"system": "urn:oid:1.2.840.114350.1.13.1.1.7.2.798268",
"value": "1000295569"
},
{
"use": "usual",
"type": {
"text": "EAP"
},
"system": "urn:oid:1.2.840.114350.1.13.1.1.7.2.696580",
"value": "5532"
}
],
"status": "completed",
"category": {
"coding": [
{
"system": http://snomed.info/sct,
"code": "103693007",
"display": "Diagnostic procedure"
}
],
"text": "Ordered Procedures"
},
"code": {
"coding": [
{
"system": http://www.ama-assn.org/go/cpt,
"code": "73560",
"display": "X-RAY KNEE 1 OR 2 VIEW"
}
],
"text": "X-RAY KNEE 2 VW"
},
"subject": {
"reference": "Patient/eO6oPEoiC084jCETqSU7y-w3",
"display": "Kid, Aiden Jr."
},
"encounter": {
"reference": "Encounter/e1QDDhX1HbcvEGeAksCj1qA3",
"identifier": {
"use": "usual",
"system": "urn:oid:1.2.840.114350.1.13.1.1.7.3.698084.8",
"value": "2"
},
"display": "Office Visit"
},
"performedDateTime": "2022-09-16",
"recorder": {
"reference": "Practitioner/euJOUNeZyX6mofWELWG0Ibg3",
"type": "Practitioner",
"display": "Dr. S Provider"
},
"asserter": {
"reference": "Practitioner/euJOUNeZyX6mofWELWG0Ibg3",
"type": "Practitioner",
"display": "Dr. S Provider"
},
"report": [
{
"reference": "DiagnosticReport/eFHRJNokw1YYrLudlWiHIBTGppy7tmBr6EF63aOWt1io3",
"type": "DiagnosticReport",
"display": "X-RAY KNEE 2 VW"
}
]
},
"search": {
"mode": "match"
}
},
{
"fullUrl": "urn:uuid:00000000-0000-2526-6a7d-d67bc0b3e258",
"resource": {
"resourceType": "OperationOutcome",
"issue": [
{
"severity": "warning",
"code": "suppressed",
"details": {
"coding": [
{
"system": "urn:oid:1.2.840.114350.1.13.1.1.7.2.657369",
"code": "59204",
"display": "The authenticated client's search request applies to a sub-resource that the client is not authorized for. Results of this sub-type will not be returned."
}
],
"text": "The authenticated client's search request applies to a sub-resource that the client is not authorized for. Results of this sub-type will not be returned."
},
"diagnostics": "Client not authorized for Procedure - Patient-Reported Surgical History. Search results of this type have not been included."
},
{
"severity": "warning",
"code": "processing",
"details": {
"coding": [
{
"system": "urn:oid:1.2.840.114350.1.13.1.1.7.2.657369",
"code": "4119",
"display": "This response includes information available to the authorized user at the time of the request. It may not contain the entire record available in the system."
}
],
"text": "This response includes information available to the authorized user at the time of the request. It may not contain the entire record available in the system."
}
}
]
},
"search": {
"mode": "outcome"
}
}
]
}
|
test
|
search parameter validation for date parameters is too strict fi as part of the us core test cases inferno validates that the server supports required search parameters for date search parameters inferno validates that the returned search results matches the provided search criteria e g searching for date doesn t return results where date for cases where the server returns date only elements e g with no time portion inferno uses midnight utc for subsequent search parameter validation e g this may trigger test case failures even though the results are expected for example our fhir server is returning the attached search results for procedures one with a performeddatetime of and another with a performeddatetime of on test case procedure search by patient date inferno is querying the server for procedure patient date our server responds to this search with both procedures as in server time zone central time is within the specified range however inferno throws an error in this scenario resourcetype bundle type searchset total link relation self url entry link relation self url fullurl resource resourcetype procedure id identifier use usual type text ord system urn oid value use usual type text eap system urn oid value status completed category coding system code display diagnostic procedure text ordered procedures code coding system urn oid code display pet follow stress ecg mult text pet follow stress ecg mult subject reference patient display kid aiden jr encounter reference encounter identifier use usual system urn oid value display office visit performeddatetime recorder reference practitioner eq type practitioner display dr a adams asserter reference practitioner eq type practitioner display dr a adams report reference diagnosticreport type diagnosticreport display pet follow stress ecg mult search mode match link relation self url fullurl resource resourcetype procedure id rbwduadpgarcwm identifier use usual type text ord system urn oid value use usual type text eap system urn oid value status completed category coding system code display diagnostic procedure text ordered procedures code coding system code display x ray knee or view text x ray knee vw subject reference patient display kid aiden jr encounter reference encounter identifier use usual system urn oid value display office visit performeddatetime recorder reference practitioner type practitioner display dr s provider asserter reference practitioner type practitioner display dr s provider report reference diagnosticreport type diagnosticreport display x ray knee vw search mode match fullurl urn uuid resource resourcetype operationoutcome issue severity warning code suppressed details coding system urn oid code display the authenticated client s search request applies to a sub resource that the client is not authorized for results of this sub type will not be returned text the authenticated client s search request applies to a sub resource that the client is not authorized for results of this sub type will not be returned diagnostics client not authorized for procedure patient reported surgical history search results of this type have not been included severity warning code processing details coding system urn oid code display this response includes information available to the authorized user at the time of the request it may not contain the entire record available in the system text this response includes information available to the authorized user at the time of the request it may not contain the entire record available in the system search mode outcome
| 1
|
584,370
| 17,422,513,929
|
IssuesEvent
|
2021-08-04 04:25:48
|
DimensionDev/Maskbook
|
https://api.github.com/repos/DimensionDev/Maskbook
|
closed
|
[Bug] Plugin will not be rendered in timeline if post tweet without mask compose
|
Priority: P2 (Important) Type: Bug
|
## Bug Info
### How to reproduce?
<img width="605" alt="截屏2021-07-31 12 38 29" src="https://user-images.githubusercontent.com/2582974/127728773-c8cb7813-d286-429a-8fd1-7e89c52877c7.png">
1. Send url: https://app.pooltogether.com/ via tweeter publisher without mask compose
2. Check the tweet in timeline
### What happened?
Pooltogether plugin will not be rendered.
### What should happen?
## Environment
### Mask Version:
- [x] (Browser) Installed from the extension store (version: )
- [ ] (App) Installed from the app store (version: )
- [ ] master branch
- [ ] Build of version/commit hash:
(Please write down build command/flags if there is anything special)
### System
<!-- Correct the version if it is not the case -->
- [ ] Windows 10
- [x] Mac OS X Catalina
- [ ] Linux: <!-- What distro? -->
### Platform/Browser
<!-- Correct the version if it is not the case -->
- [x] Latest Chrome (stable channel)
- [ ] Latest Firefox (stable channel)
- [ ] Android 11
- [ ] iOS 14
|
1.0
|
[Bug] Plugin will not be rendered in timeline if post tweet without mask compose - ## Bug Info
### How to reproduce?
<img width="605" alt="截屏2021-07-31 12 38 29" src="https://user-images.githubusercontent.com/2582974/127728773-c8cb7813-d286-429a-8fd1-7e89c52877c7.png">
1. Send url: https://app.pooltogether.com/ via tweeter publisher without mask compose
2. Check the tweet in timeline
### What happened?
Pooltogether plugin will not be rendered.
### What should happen?
## Environment
### Mask Version:
- [x] (Browser) Installed from the extension store (version: )
- [ ] (App) Installed from the app store (version: )
- [ ] master branch
- [ ] Build of version/commit hash:
(Please write down build command/flags if there is anything special)
### System
<!-- Correct the version if it is not the case -->
- [ ] Windows 10
- [x] Mac OS X Catalina
- [ ] Linux: <!-- What distro? -->
### Platform/Browser
<!-- Correct the version if it is not the case -->
- [x] Latest Chrome (stable channel)
- [ ] Latest Firefox (stable channel)
- [ ] Android 11
- [ ] iOS 14
|
non_test
|
plugin will not be rendered in timeline if post tweet without mask compose bug info how to reproduce img width alt src send url via tweeter publisher without mask compose check the tweet in timeline what happened pooltogether plugin will not be rendered what should happen environment mask version browser installed from the extension store version app installed from the app store version master branch build of version commit hash please write down build command flags if there is anything special system windows mac os x catalina linux platform browser latest chrome stable channel latest firefox stable channel android ios
| 0
|
283,697
| 21,328,392,202
|
IssuesEvent
|
2022-04-18 04:04:09
|
qi116/iOSApp
|
https://api.github.com/repos/qi116/iOSApp
|
closed
|
Basic interface
|
documentation
|
From the highest priority to the lowest:
- [x] User login page
- - [x] Login **button**
- - [x] Username **textfield**
- - [x] Password **textfield**
- [x] User register page
- - [x] Email **textfield**
- - [x] Username **textfield**
- - [x] Password **textfield**
- - [x] Confirm password **textfield**
- - [x] Phone number optional **textfield**
- [x] Items list page
- - [x] Item **tablecell**
- - [x] Items **tableview**
- [x] Vendors list page
- - [x] Vendors **tablecell**
- - [x] Vendors **tableview**
|
1.0
|
Basic interface - From the highest priority to the lowest:
- [x] User login page
- - [x] Login **button**
- - [x] Username **textfield**
- - [x] Password **textfield**
- [x] User register page
- - [x] Email **textfield**
- - [x] Username **textfield**
- - [x] Password **textfield**
- - [x] Confirm password **textfield**
- - [x] Phone number optional **textfield**
- [x] Items list page
- - [x] Item **tablecell**
- - [x] Items **tableview**
- [x] Vendors list page
- - [x] Vendors **tablecell**
- - [x] Vendors **tableview**
|
non_test
|
basic interface from the highest priority to the lowest user login page login button username textfield password textfield user register page email textfield username textfield password textfield confirm password textfield phone number optional textfield items list page item tablecell items tableview vendors list page vendors tablecell vendors tableview
| 0
|
96,790
| 10,963,193,597
|
IssuesEvent
|
2019-11-27 19:04:20
|
dankamongmen/notcurses
|
https://api.github.com/repos/dankamongmen/notcurses
|
opened
|
Render AVFrames
|
documentation enhancement
|
Now that we're able to extract AVFrames from video and images, it's time to render them down. We're first looking for the quality level of e.g. `mpv -vo tct`, but then we ought be able to use better drawing characters, better palette matching, and better dithering to improve on it.
|
1.0
|
Render AVFrames - Now that we're able to extract AVFrames from video and images, it's time to render them down. We're first looking for the quality level of e.g. `mpv -vo tct`, but then we ought be able to use better drawing characters, better palette matching, and better dithering to improve on it.
|
non_test
|
render avframes now that we re able to extract avframes from video and images it s time to render them down we re first looking for the quality level of e g mpv vo tct but then we ought be able to use better drawing characters better palette matching and better dithering to improve on it
| 0
|
235,200
| 19,307,583,322
|
IssuesEvent
|
2021-12-13 13:13:08
|
ory/keto
|
https://api.github.com/repos/ory/keto
|
closed
|
List API: namespace should not be required anymore
|
help wanted good first issue docs tests
|
**Describe the bug**
The namespace parameter is marked as required in the API spec. Also, we need a test to ensure that queries across namespaces actually work.
**Expected behavior**
Make the namespace parameter not required anymore. Make sure that all docs are updated accordingly.
|
1.0
|
List API: namespace should not be required anymore - **Describe the bug**
The namespace parameter is marked as required in the API spec. Also, we need a test to ensure that queries across namespaces actually work.
**Expected behavior**
Make the namespace parameter not required anymore. Make sure that all docs are updated accordingly.
|
test
|
list api namespace should not be required anymore describe the bug the namespace parameter is marked as required in the api spec also we need a test to ensure that queries across namespaces actually work expected behavior make the namespace parameter not required anymore make sure that all docs are updated accordingly
| 1
|
56,236
| 31,815,295,802
|
IssuesEvent
|
2023-09-13 19:58:18
|
crossplane/crossplane
|
https://api.github.com/repos/crossplane/crossplane
|
closed
|
Reduce "object has been modified" errors
|
enhancement performance exempt-from-stale
|
<!--
Thank you for helping to improve Crossplane!
Please be sure to search for open issues before raising a new one. We use issues
for bug reports and feature requests. Please find us at https://slack.crossplane.io
for questions, support, and discussion.
-->
### What problem are you facing?
<!--
Please tell us a little about your use case - it's okay if it's hypothetical!
Leading with this context helps frame the feature request so we can ensure we
implement it sensibly.
--->
Crossplane controllers - particularly the composition controllers - tend to hit a lot of "object has been modified" errors. These errors are returned by the API server when we attempt to mutate a resource with a stale resource version. I believe they're HTTP 409 Conflict errors.
Here's an example of a resource claim that hit three of these errors in a matter of seconds.
```
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning BindCompositeResource 13s offered/compositeresourcedefinition.apiextensions.crossplane.io cannot update object: Operation cannot be fulfilled on postgresqlinstances.database.example.org "my-db": the object has been modified; please apply your changes to the latest version and try again
Normal ConfigureCompositeResource 13s (x3 over 13s) offered/compositeresourcedefinition.apiextensions.crossplane.io Successfully applied composite resource
Normal ConfigureCompositeResource 13s (x5 over 13s) offered/compositeresourcedefinition.apiextensions.crossplane.io Successfully applied composite resource
Warning BindCompositeResource 13s offered/compositeresourcedefinition.apiextensions.crossplane.io cannot update composite resource claim: Operation cannot be fulfilled on postgresqlinstances.database.example.org "my-db": the object has been modified; please apply your changes to the latest version and try again
Normal BindCompositeResource 13s (x3 over 13s) offered/compositeresourcedefinition.apiextensions.crossplane.io Composite resource is not yet ready
Warning BindCompositeResource 13s offered/compositeresourcedefinition.apiextensions.crossplane.io cannot update composite resource: Operation cannot be fulfilled on compositepostgresqlinstances.database.example.org "my-db-58hhn": the object has been modified; please apply your changes to the latest version and try again
Normal BindCompositeResource 13s (x3 over 13s) offered/compositeresourcedefinition.apiextensions.crossplane.io Composite resource is not yet ready
```
I'm surprised by how many of these we hit, especially for resources like claims that are mutated by only a single controller. They don't really get in the way of anything working, but I do suspect they're leading to us hitting the API server more than we need to (i.e. multiple requeues resulting in multiple failed writes).
### How could Crossplane help solve your problem?
<!--
Let us know how you think Crossplane could help with your use case.
-->
I'd like to understand why we're seeing so many of these, and if possible reduce them.
|
True
|
Reduce "object has been modified" errors - <!--
Thank you for helping to improve Crossplane!
Please be sure to search for open issues before raising a new one. We use issues
for bug reports and feature requests. Please find us at https://slack.crossplane.io
for questions, support, and discussion.
-->
### What problem are you facing?
<!--
Please tell us a little about your use case - it's okay if it's hypothetical!
Leading with this context helps frame the feature request so we can ensure we
implement it sensibly.
--->
Crossplane controllers - particularly the composition controllers - tend to hit a lot of "object has been modified" errors. These errors are returned by the API server when we attempt to mutate a resource with a stale resource version. I believe they're HTTP 409 Conflict errors.
Here's an example of a resource claim that hit three of these errors in a matter of seconds.
```
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning BindCompositeResource 13s offered/compositeresourcedefinition.apiextensions.crossplane.io cannot update object: Operation cannot be fulfilled on postgresqlinstances.database.example.org "my-db": the object has been modified; please apply your changes to the latest version and try again
Normal ConfigureCompositeResource 13s (x3 over 13s) offered/compositeresourcedefinition.apiextensions.crossplane.io Successfully applied composite resource
Normal ConfigureCompositeResource 13s (x5 over 13s) offered/compositeresourcedefinition.apiextensions.crossplane.io Successfully applied composite resource
Warning BindCompositeResource 13s offered/compositeresourcedefinition.apiextensions.crossplane.io cannot update composite resource claim: Operation cannot be fulfilled on postgresqlinstances.database.example.org "my-db": the object has been modified; please apply your changes to the latest version and try again
Normal BindCompositeResource 13s (x3 over 13s) offered/compositeresourcedefinition.apiextensions.crossplane.io Composite resource is not yet ready
Warning BindCompositeResource 13s offered/compositeresourcedefinition.apiextensions.crossplane.io cannot update composite resource: Operation cannot be fulfilled on compositepostgresqlinstances.database.example.org "my-db-58hhn": the object has been modified; please apply your changes to the latest version and try again
Normal BindCompositeResource 13s (x3 over 13s) offered/compositeresourcedefinition.apiextensions.crossplane.io Composite resource is not yet ready
```
I'm surprised by how many of these we hit, especially for resources like claims that are mutated by only a single controller. They don't really get in the way of anything working, but I do suspect they're leading to us hitting the API server more than we need to (i.e. multiple requeues resulting in multiple failed writes).
### How could Crossplane help solve your problem?
<!--
Let us know how you think Crossplane could help with your use case.
-->
I'd like to understand why we're seeing so many of these, and if possible reduce them.
|
non_test
|
reduce object has been modified errors thank you for helping to improve crossplane please be sure to search for open issues before raising a new one we use issues for bug reports and feature requests please find us at for questions support and discussion what problem are you facing please tell us a little about your use case it s okay if it s hypothetical leading with this context helps frame the feature request so we can ensure we implement it sensibly crossplane controllers particularly the composition controllers tend to hit a lot of object has been modified errors these errors are returned by the api server when we attempt to mutate a resource with a stale resource version i believe they re http conflict errors here s an example of a resource claim that hit three of these errors in a matter of seconds events type reason age from message warning bindcompositeresource offered compositeresourcedefinition apiextensions crossplane io cannot update object operation cannot be fulfilled on postgresqlinstances database example org my db the object has been modified please apply your changes to the latest version and try again normal configurecompositeresource over offered compositeresourcedefinition apiextensions crossplane io successfully applied composite resource normal configurecompositeresource over offered compositeresourcedefinition apiextensions crossplane io successfully applied composite resource warning bindcompositeresource offered compositeresourcedefinition apiextensions crossplane io cannot update composite resource claim operation cannot be fulfilled on postgresqlinstances database example org my db the object has been modified please apply your changes to the latest version and try again normal bindcompositeresource over offered compositeresourcedefinition apiextensions crossplane io composite resource is not yet ready warning bindcompositeresource offered compositeresourcedefinition apiextensions crossplane io cannot update composite resource operation cannot be fulfilled on compositepostgresqlinstances database example org my db the object has been modified please apply your changes to the latest version and try again normal bindcompositeresource over offered compositeresourcedefinition apiextensions crossplane io composite resource is not yet ready i m surprised by how many of these we hit especially for resources like claims that are mutated by only a single controller they don t really get in the way of anything working but i do suspect they re leading to us hitting the api server more than we need to i e multiple requeues resulting in multiple failed writes how could crossplane help solve your problem let us know how you think crossplane could help with your use case i d like to understand why we re seeing so many of these and if possible reduce them
| 0
|
148
| 2,541,386,201
|
IssuesEvent
|
2015-01-28 08:11:34
|
projectdanube/xdi2
|
https://api.github.com/repos/projectdanube/xdi2
|
opened
|
Signature validation fails if a message contains BOTH a signature and a secret token
|
bug security
|
Given the following message:
[+]!:uuid:8888[$msg]!:uuid:1234/$is()/([+]!:uuid:8888)
[+]!:uuid:8888[$msg]!:uuid:1234/$do/([+]!:uuid:8888/[+]!:uuid:8888)$do
([+]!:uuid:8888[$msg]!:uuid:1234$do/$set)([=]!:uuid:1234)<$xdi><$uri>&/&/"....."
[+]!:uuid:8888[$msg]!:uuid:1234<$secret><$token>&/&/"....."
[+]!:uuid:8888[$msg]!:uuid:1234<$sig>&/&/"....."
[+]!:uuid:8888[$msg]!:uuid:1234<$sig>/$is#/$sha$256$rsa$2048
When the secret token is validated, a "virtual" statement is added to the incoming message, e.g.:
[+]!:uuid:8888[$msg]!:uuid:1234<$secret><$token><$valid>&/&/true
This will subsequently make signature validation fail, since the normalized context node has the additional statement that is not covered by the signature.
These "virtual" statements should therefore be handled differently and not included in the signature validation process.
Workarounds:
1. Don't send messages that contain both a secret token and a signature.
2. In the messaging target's configuration, place the AuthenticationSecretTokenInterceptor AFTER the AuthenticationSignatureInterceptor.
|
True
|
Signature validation fails if a message contains BOTH a signature and a secret token - Given the following message:
[+]!:uuid:8888[$msg]!:uuid:1234/$is()/([+]!:uuid:8888)
[+]!:uuid:8888[$msg]!:uuid:1234/$do/([+]!:uuid:8888/[+]!:uuid:8888)$do
([+]!:uuid:8888[$msg]!:uuid:1234$do/$set)([=]!:uuid:1234)<$xdi><$uri>&/&/"....."
[+]!:uuid:8888[$msg]!:uuid:1234<$secret><$token>&/&/"....."
[+]!:uuid:8888[$msg]!:uuid:1234<$sig>&/&/"....."
[+]!:uuid:8888[$msg]!:uuid:1234<$sig>/$is#/$sha$256$rsa$2048
When the secret token is validated, a "virtual" statement is added to the incoming message, e.g.:
[+]!:uuid:8888[$msg]!:uuid:1234<$secret><$token><$valid>&/&/true
This will subsequently make signature validation fail, since the normalized context node has the additional statement that is not covered by the signature.
These "virtual" statements should therefore be handled differently and not included in the signature validation process.
Workarounds:
1. Don't send messages that contain both a secret token and a signature.
2. In the messaging target's configuration, place the AuthenticationSecretTokenInterceptor AFTER the AuthenticationSignatureInterceptor.
|
non_test
|
signature validation fails if a message contains both a signature and a secret token given the following message uuid uuid is uuid uuid uuid do uuid uuid do uuid uuid do set uuid uuid uuid uuid uuid uuid uuid is sha rsa when the secret token is validated a virtual statement is added to the incoming message e g uuid uuid true this will subsequently make signature validation fail since the normalized context node has the additional statement that is not covered by the signature these virtual statements should therefore be handled differently and not included in the signature validation process workarounds don t send messages that contain both a secret token and a signature in the messaging target s configuration place the authenticationsecrettokeninterceptor after the authenticationsignatureinterceptor
| 0
|
69,721
| 7,158,025,145
|
IssuesEvent
|
2018-01-26 22:18:34
|
angular/angular
|
https://api.github.com/repos/angular/angular
|
closed
|
ComponentFixture autoDetectChanges, whenStable and isStable should throw an exception if there is no NgZone present
|
comp: testing
|
It is possible to being up TestComponentBuilder with an NgZone by providing a true value for token ComponentFixtureNoNgZone.
In that case the APIs in Component Fixture that depend upon NgZone to function properly - autoDetectChanges, whenStable, isStable should throw an exception if called without the NgZone being present.
|
1.0
|
ComponentFixture autoDetectChanges, whenStable and isStable should throw an exception if there is no NgZone present - It is possible to being up TestComponentBuilder with an NgZone by providing a true value for token ComponentFixtureNoNgZone.
In that case the APIs in Component Fixture that depend upon NgZone to function properly - autoDetectChanges, whenStable, isStable should throw an exception if called without the NgZone being present.
|
test
|
componentfixture autodetectchanges whenstable and isstable should throw an exception if there is no ngzone present it is possible to being up testcomponentbuilder with an ngzone by providing a true value for token componentfixturenongzone in that case the apis in component fixture that depend upon ngzone to function properly autodetectchanges whenstable isstable should throw an exception if called without the ngzone being present
| 1
|
83,979
| 24,187,220,846
|
IssuesEvent
|
2022-09-23 14:16:19
|
neovim/neovim
|
https://api.github.com/repos/neovim/neovim
|
closed
|
build: cmake warning: argument named "true" appears in a conditional
|
bug build test ci
|
```
CMake Warning (dev) at /home/runner/work/neovim/neovim/cmake/RunTests.cmake:87 (if):
-- Tests exited non-zero: 1
if given arguments:
-- Output to stderr:
"true"
An argument named "true" appears in a conditional statement. Policy
CMP0012 is not set: if() recognizes numbers and boolean constants. Run
"cmake --help-policy CMP0012" for policy details. Use the cmake_policy
command to set the policy and suppress this warning.
```
|
1.0
|
build: cmake warning: argument named "true" appears in a conditional - ```
CMake Warning (dev) at /home/runner/work/neovim/neovim/cmake/RunTests.cmake:87 (if):
-- Tests exited non-zero: 1
if given arguments:
-- Output to stderr:
"true"
An argument named "true" appears in a conditional statement. Policy
CMP0012 is not set: if() recognizes numbers and boolean constants. Run
"cmake --help-policy CMP0012" for policy details. Use the cmake_policy
command to set the policy and suppress this warning.
```
|
non_test
|
build cmake warning argument named true appears in a conditional cmake warning dev at home runner work neovim neovim cmake runtests cmake if tests exited non zero if given arguments output to stderr true an argument named true appears in a conditional statement policy is not set if recognizes numbers and boolean constants run cmake help policy for policy details use the cmake policy command to set the policy and suppress this warning
| 0
|
7,126
| 24,288,550,178
|
IssuesEvent
|
2022-09-29 02:14:48
|
DevExpress/testcafe
|
https://api.github.com/repos/DevExpress/testcafe
|
closed
|
t.click() on some selectors not working on Firefox 85 or newer
|
TYPE: bug SYSTEM: automations FREQUENCY: level 1 STATE: Stale
|
### What is your Test Scenario?
Since Firefox 85 we've been experiencing issues with selectors, we currently test on safari, chrome, Edge, Opera on several different OS and the issue is only experienced on Firefox since version 85.
Example: Fifrefox 85 and further is not able to click this selector:
await t.click(userMenu);
User menu is defined like this.
Selector('button').find('span').withAttribute('aria-label', 'User Menu');
### What is the Current behavior?
Testcafe times out while trying to find and click the the user menu.
### What is the Expected behavior?
Testcafe should find and click the selector.
### What is your web application and your TestCafe test code?
https://admin-demo.intouchstaging.com/
Authorization and credentials have been provided privately to Alex Skorkin.
Code has been shared in the past via StackOverflow but the issue seems to be independent of it.
### Steps to Reproduce:
<!-- Describe what we should do to reproduce the behavior you encountered. -->
1. Go to my website https://admin-demo.intouchstaging.com/
2. Log with the credentials provided for askorkin, it should drive you to a user table.
3. Execute this command:
let userMenu = Selector('button').find('span').withAttribute('aria-label', 'User Menu');
await t.click(userMenu);
(Its the button on the upper right corner of the website)
4. See the error: Timeout
### Your Environment details:
(will update this soon, not on my working computer right now. It shouldn't matter.)
* testcafe version: 1.15.0
* node.js version: v15.10.0
* command-line arguments: ./node_modules/.bin/testcafe firefox test.js --env XXX --test-meta TRID=XXXXXX
* browser name and version: Firefox >= 85
* platform and version: Ubuntu 20.04 / MacOs Big Sur /Windows 10
|
1.0
|
t.click() on some selectors not working on Firefox 85 or newer - ### What is your Test Scenario?
Since Firefox 85 we've been experiencing issues with selectors, we currently test on safari, chrome, Edge, Opera on several different OS and the issue is only experienced on Firefox since version 85.
Example: Fifrefox 85 and further is not able to click this selector:
await t.click(userMenu);
User menu is defined like this.
Selector('button').find('span').withAttribute('aria-label', 'User Menu');
### What is the Current behavior?
Testcafe times out while trying to find and click the the user menu.
### What is the Expected behavior?
Testcafe should find and click the selector.
### What is your web application and your TestCafe test code?
https://admin-demo.intouchstaging.com/
Authorization and credentials have been provided privately to Alex Skorkin.
Code has been shared in the past via StackOverflow but the issue seems to be independent of it.
### Steps to Reproduce:
<!-- Describe what we should do to reproduce the behavior you encountered. -->
1. Go to my website https://admin-demo.intouchstaging.com/
2. Log with the credentials provided for askorkin, it should drive you to a user table.
3. Execute this command:
let userMenu = Selector('button').find('span').withAttribute('aria-label', 'User Menu');
await t.click(userMenu);
(Its the button on the upper right corner of the website)
4. See the error: Timeout
### Your Environment details:
(will update this soon, not on my working computer right now. It shouldn't matter.)
* testcafe version: 1.15.0
* node.js version: v15.10.0
* command-line arguments: ./node_modules/.bin/testcafe firefox test.js --env XXX --test-meta TRID=XXXXXX
* browser name and version: Firefox >= 85
* platform and version: Ubuntu 20.04 / MacOs Big Sur /Windows 10
|
non_test
|
t click on some selectors not working on firefox or newer what is your test scenario since firefox we ve been experiencing issues with selectors we currently test on safari chrome edge opera on several different os and the issue is only experienced on firefox since version example fifrefox and further is not able to click this selector await t click usermenu user menu is defined like this selector button find span withattribute aria label user menu what is the current behavior testcafe times out while trying to find and click the the user menu what is the expected behavior testcafe should find and click the selector what is your web application and your testcafe test code authorization and credentials have been provided privately to alex skorkin code has been shared in the past via stackoverflow but the issue seems to be independent of it steps to reproduce go to my website log with the credentials provided for askorkin it should drive you to a user table execute this command let usermenu selector button find span withattribute aria label user menu await t click usermenu its the button on the upper right corner of the website see the error timeout your environment details will update this soon not on my working computer right now it shouldn t matter testcafe version node js version command line arguments node modules bin testcafe firefox test js env xxx test meta trid xxxxxx browser name and version firefox platform and version ubuntu macos big sur windows
| 0
|
35,572
| 31,841,155,404
|
IssuesEvent
|
2023-09-14 16:24:19
|
dotnet/dotnet-docker
|
https://api.github.com/repos/dotnet/dotnet-docker
|
opened
|
Make VerifyComplexAppSample Test a [Theory]
|
bug area-infrastructure
|
Looking at the VerifyComplexAppSample test, there are two concerns:
1. The `complexapp` sample Dockerfile uses the multi-platform tags and therefore won't build on Windows in .NET 8 due to https://github.com/dotnet/dotnet-docker/issues/4492:
https://github.com/dotnet/dotnet-docker/blob/c09ce8b720090c91933e4bd380bd1baa3c89f3d3/samples/complexapp/Dockerfile#L1-L3
2. The test is a `[Fact]`, and therefore runs once per leg but uses only one base image, the multi-platform image, which is Debian. The Dockerfile should be amended to support multiple different images and the test should be amended to test across supported operating systems like the other sample tests.
https://github.com/dotnet/dotnet-docker/blob/c09ce8b720090c91933e4bd380bd1baa3c89f3d3/tests/Microsoft.DotNet.Docker.Tests/SampleImageTests.cs#L92-L93
|
1.0
|
Make VerifyComplexAppSample Test a [Theory] -
Looking at the VerifyComplexAppSample test, there are two concerns:
1. The `complexapp` sample Dockerfile uses the multi-platform tags and therefore won't build on Windows in .NET 8 due to https://github.com/dotnet/dotnet-docker/issues/4492:
https://github.com/dotnet/dotnet-docker/blob/c09ce8b720090c91933e4bd380bd1baa3c89f3d3/samples/complexapp/Dockerfile#L1-L3
2. The test is a `[Fact]`, and therefore runs once per leg but uses only one base image, the multi-platform image, which is Debian. The Dockerfile should be amended to support multiple different images and the test should be amended to test across supported operating systems like the other sample tests.
https://github.com/dotnet/dotnet-docker/blob/c09ce8b720090c91933e4bd380bd1baa3c89f3d3/tests/Microsoft.DotNet.Docker.Tests/SampleImageTests.cs#L92-L93
|
non_test
|
make verifycomplexappsample test a looking at the verifycomplexappsample test there are two concerns the complexapp sample dockerfile uses the multi platform tags and therefore won t build on windows in net due to the test is a and therefore runs once per leg but uses only one base image the multi platform image which is debian the dockerfile should be amended to support multiple different images and the test should be amended to test across supported operating systems like the other sample tests
| 0
|
100,372
| 8,737,507,305
|
IssuesEvent
|
2018-12-11 22:49:37
|
freeCodeCamp/freeCodeCamp
|
https://api.github.com/repos/freeCodeCamp/freeCodeCamp
|
opened
|
Testing non-english challenges
|
scope: tests scope: translation status: discussing
|
Maybe I'm misreading the code, but it looks like we're running the curriculum tests only over the English version, as no locale is specified for travis.
https://github.com/freeCodeCamp/freeCodeCamp/blob/5aa27ee364ea9567c86476caf59b6f217be9563c/curriculum/test/test-challenges.js#L28
With #30709 in mind, the tests should do some introspection first to see which language needs testing in the first place. Unfortunately in some cases PRs fix tests in all languages, so it would ideally need to loop and test all.
|
1.0
|
Testing non-english challenges - Maybe I'm misreading the code, but it looks like we're running the curriculum tests only over the English version, as no locale is specified for travis.
https://github.com/freeCodeCamp/freeCodeCamp/blob/5aa27ee364ea9567c86476caf59b6f217be9563c/curriculum/test/test-challenges.js#L28
With #30709 in mind, the tests should do some introspection first to see which language needs testing in the first place. Unfortunately in some cases PRs fix tests in all languages, so it would ideally need to loop and test all.
|
test
|
testing non english challenges maybe i m misreading the code but it looks like we re running the curriculum tests only over the english version as no locale is specified for travis with in mind the tests should do some introspection first to see which language needs testing in the first place unfortunately in some cases prs fix tests in all languages so it would ideally need to loop and test all
| 1
|
260,107
| 22,591,844,331
|
IssuesEvent
|
2022-06-28 20:45:13
|
microsoft/FluidFramework
|
https://api.github.com/repos/microsoft/FluidFramework
|
closed
|
Need UT coverage for RunWhileConnectedCoordinator
|
area: tests area: runtime: summarizer ado
|
Would appreciate help here :)
This issue is opened in context of https://github.com/microsoft/FluidFramework/pull/7321/ & https://github.com/microsoft/FluidFramework/issues/7311
|
1.0
|
Need UT coverage for RunWhileConnectedCoordinator - Would appreciate help here :)
This issue is opened in context of https://github.com/microsoft/FluidFramework/pull/7321/ & https://github.com/microsoft/FluidFramework/issues/7311
|
test
|
need ut coverage for runwhileconnectedcoordinator would appreciate help here this issue is opened in context of
| 1
|
224,262
| 17,685,543,601
|
IssuesEvent
|
2021-08-24 00:36:20
|
backend-br/vagas
|
https://api.github.com/repos/backend-br/vagas
|
closed
|
[REMOTO] Nodejs Developer @ Zup Innovation
|
CLT Pleno NodeJS Remoto AWS TypeScript Testes Unitários Rest startup Stale
|
## Nossa empresa
Nós criamos tecnologia!
Desenvolvemos uma stack de tecnologia para melhorar a developer experience, facilitando e diminuindo o tempo entre a concepção de uma ideia e o código em produção. Trazendo ainda mais eficiência para profissionais de desenvolvimento e times de tecnologia.
O sucesso de qualquer empresa no mundo digital, seja uma startup ou de grande porte, está ligado com a sua capacidade em ser ágil para colocar produtos no ar, pivotar uma estratégia, adicionar features e atender bem seu cliente, e é claro mantendo a segurança necessária.
Nosso foco é desenvolver tecnologia para apoiar nossos clientes com essas estratégias. Mais do que isso, nosso propósito é transformar o Brasil em um polo de tecnologia global.
## Descrição da vaga
Atuação em projeto com Nodejs.
## Local
Remoto
## Requisitos
**Obrigatórios:**
Experiência em Typescript;
Testes Unitários;
API Rest;
AWS (Lambda, API Gateway, EC2)
## Benefícios
💰 - PLR
💊 - Plano de Saúde SulAmérica
🦷 - Plano Odontológico SulAmérica
🍝 - VR/VA Flash R$1045,00
📚 - Capacitação anual (Ajuda de custo)
📱 - Plano de celular
🏡 - Auxílio Home Office
👶 - Auxílio creche
⭐ - Seguro de vida
💪 - Gympass
💵 - Bônus por indicação
🏖️ - Liberdade para trabalhar de onde quiser
🍻 - Happy Hours e Confraternizações
🔀 - Trilha de Carreira em W
👨🦽 - Diversidade e Inclusão
✅ - Telavita (psicólogo online)
## Contratação
CLT
## Como se candidatar
Podem me chamar no LinkedIn: https://www.linkedin.com/in/vit%C3%B3ria-gomes-santos/ ou enviar CV para vitoria.santos@zup.com.br
## Tempo médio de feedbacks
Costumamos enviar feedbacks em até 7 dias úteis após cada processo.
#### Regime
- CLT
#### Nível
- Pleno
- Sênior
|
1.0
|
[REMOTO] Nodejs Developer @ Zup Innovation - ## Nossa empresa
Nós criamos tecnologia!
Desenvolvemos uma stack de tecnologia para melhorar a developer experience, facilitando e diminuindo o tempo entre a concepção de uma ideia e o código em produção. Trazendo ainda mais eficiência para profissionais de desenvolvimento e times de tecnologia.
O sucesso de qualquer empresa no mundo digital, seja uma startup ou de grande porte, está ligado com a sua capacidade em ser ágil para colocar produtos no ar, pivotar uma estratégia, adicionar features e atender bem seu cliente, e é claro mantendo a segurança necessária.
Nosso foco é desenvolver tecnologia para apoiar nossos clientes com essas estratégias. Mais do que isso, nosso propósito é transformar o Brasil em um polo de tecnologia global.
## Descrição da vaga
Atuação em projeto com Nodejs.
## Local
Remoto
## Requisitos
**Obrigatórios:**
Experiência em Typescript;
Testes Unitários;
API Rest;
AWS (Lambda, API Gateway, EC2)
## Benefícios
💰 - PLR
💊 - Plano de Saúde SulAmérica
🦷 - Plano Odontológico SulAmérica
🍝 - VR/VA Flash R$1045,00
📚 - Capacitação anual (Ajuda de custo)
📱 - Plano de celular
🏡 - Auxílio Home Office
👶 - Auxílio creche
⭐ - Seguro de vida
💪 - Gympass
💵 - Bônus por indicação
🏖️ - Liberdade para trabalhar de onde quiser
🍻 - Happy Hours e Confraternizações
🔀 - Trilha de Carreira em W
👨🦽 - Diversidade e Inclusão
✅ - Telavita (psicólogo online)
## Contratação
CLT
## Como se candidatar
Podem me chamar no LinkedIn: https://www.linkedin.com/in/vit%C3%B3ria-gomes-santos/ ou enviar CV para vitoria.santos@zup.com.br
## Tempo médio de feedbacks
Costumamos enviar feedbacks em até 7 dias úteis após cada processo.
#### Regime
- CLT
#### Nível
- Pleno
- Sênior
|
test
|
nodejs developer zup innovation nossa empresa nós criamos tecnologia desenvolvemos uma stack de tecnologia para melhorar a developer experience facilitando e diminuindo o tempo entre a concepção de uma ideia e o código em produção trazendo ainda mais eficiência para profissionais de desenvolvimento e times de tecnologia o sucesso de qualquer empresa no mundo digital seja uma startup ou de grande porte está ligado com a sua capacidade em ser ágil para colocar produtos no ar pivotar uma estratégia adicionar features e atender bem seu cliente e é claro mantendo a segurança necessária nosso foco é desenvolver tecnologia para apoiar nossos clientes com essas estratégias mais do que isso nosso propósito é transformar o brasil em um polo de tecnologia global descrição da vaga atuação em projeto com nodejs local remoto requisitos obrigatórios experiência em typescript testes unitários api rest aws lambda api gateway benefícios 💰 plr 💊 plano de saúde sulamérica 🦷 plano odontológico sulamérica 🍝 vr va flash r 📚 capacitação anual ajuda de custo 📱 plano de celular 🏡 auxílio home office 👶 auxílio creche ⭐ seguro de vida 💪 gympass 💵 bônus por indicação 🏖️ liberdade para trabalhar de onde quiser 🍻 happy hours e confraternizações 🔀 trilha de carreira em w 👨🦽 diversidade e inclusão ✅ telavita psicólogo online contratação clt como se candidatar podem me chamar no linkedin ou enviar cv para vitoria santos zup com br tempo médio de feedbacks costumamos enviar feedbacks em até dias úteis após cada processo regime clt nível pleno sênior
| 1
|
24,380
| 4,076,441,921
|
IssuesEvent
|
2016-05-29 22:17:58
|
EasyRPG/Player
|
https://api.github.com/repos/EasyRPG/Player
|
closed
|
Ara Fell: Saving with RPG_RT in the KeyRoom and loading in EasyRPG doesn't place the key "below hero"
|
Patch available Savegames Testcase available
|
In Ara Fell you can't pickup the key in the key room when you load a RPG_RT save in EasyRPG.
The key must be "below the hero" but it is "same Level" instead, making the game unplayable until reloading the room. The reason could be also that there is a 2nd event with "same Level" called "sparkle" above the key.
RPG_RT savegame is attached. [Save05.zip](https://github.com/EasyRPG/Player/files/254099/Save05.zip)
|
1.0
|
Ara Fell: Saving with RPG_RT in the KeyRoom and loading in EasyRPG doesn't place the key "below hero" - In Ara Fell you can't pickup the key in the key room when you load a RPG_RT save in EasyRPG.
The key must be "below the hero" but it is "same Level" instead, making the game unplayable until reloading the room. The reason could be also that there is a 2nd event with "same Level" called "sparkle" above the key.
RPG_RT savegame is attached. [Save05.zip](https://github.com/EasyRPG/Player/files/254099/Save05.zip)
|
test
|
ara fell saving with rpg rt in the keyroom and loading in easyrpg doesn t place the key below hero in ara fell you can t pickup the key in the key room when you load a rpg rt save in easyrpg the key must be below the hero but it is same level instead making the game unplayable until reloading the room the reason could be also that there is a event with same level called sparkle above the key rpg rt savegame is attached
| 1
|
167,828
| 13,044,324,855
|
IssuesEvent
|
2020-07-29 04:19:28
|
OllisGit/OctoPrint-SpoolManager
|
https://api.github.com/repos/OllisGit/OctoPrint-SpoolManager
|
closed
|
Feature Request: Checkbox to show/hide empty spools within the list
|
status: waitingForTestFeedback type: enhancement
|
I keep track of empty spools too.
This allows me to later lookup filaments I already used and re-order.
The field "purchased from" and "purchase data" that your plugin has is already awesome :ok_hand:.
I would find a checkbox that hides empty spools from the spool list very useful.
|
1.0
|
Feature Request: Checkbox to show/hide empty spools within the list - I keep track of empty spools too.
This allows me to later lookup filaments I already used and re-order.
The field "purchased from" and "purchase data" that your plugin has is already awesome :ok_hand:.
I would find a checkbox that hides empty spools from the spool list very useful.
|
test
|
feature request checkbox to show hide empty spools within the list i keep track of empty spools too this allows me to later lookup filaments i already used and re order the field purchased from and purchase data that your plugin has is already awesome ok hand i would find a checkbox that hides empty spools from the spool list very useful
| 1
|
192,580
| 14,620,553,181
|
IssuesEvent
|
2020-12-22 19:56:36
|
github-vet/rangeloop-pointer-findings
|
https://api.github.com/repos/github-vet/rangeloop-pointer-findings
|
closed
|
pbolla0818/oci_terraform: oci/core_ipsec_test.go; 16 LoC
|
fresh small test
|
Found a possible issue in [pbolla0818/oci_terraform](https://www.github.com/pbolla0818/oci_terraform) at [oci/core_ipsec_test.go](https://github.com/pbolla0818/oci_terraform/blob/c233d54c5fe32f12c234d6dceefba0a9b4ab3022/oci/core_ipsec_test.go#L284-L299)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> reference to ipSecConnectionId is reassigned at line 288
[Click here to see the code in its original context.](https://github.com/pbolla0818/oci_terraform/blob/c233d54c5fe32f12c234d6dceefba0a9b4ab3022/oci/core_ipsec_test.go#L284-L299)
<details>
<summary>Click here to show the 16 line(s) of Go which triggered the analyzer.</summary>
```go
for _, ipSecConnectionId := range ipSecConnectionIds {
if ok := SweeperDefaultResourceId[ipSecConnectionId]; !ok {
deleteIPSecConnectionRequest := oci_core.DeleteIPSecConnectionRequest{}
deleteIPSecConnectionRequest.IpscId = &ipSecConnectionId
deleteIPSecConnectionRequest.RequestMetadata.RetryPolicy = getRetryPolicy(true, "core")
_, error := virtualNetworkClient.DeleteIPSecConnection(context.Background(), deleteIPSecConnectionRequest)
if error != nil {
fmt.Printf("Error deleting IpSecConnection %s %s, It is possible that the resource is already deleted. Please verify manually \n", ipSecConnectionId, error)
continue
}
waitTillCondition(testAccProvider, &ipSecConnectionId, ipSecConnectionSweepWaitCondition, time.Duration(3*time.Minute),
ipSecConnectionSweepResponseFetchOperation, "core", true)
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: c233d54c5fe32f12c234d6dceefba0a9b4ab3022
|
1.0
|
pbolla0818/oci_terraform: oci/core_ipsec_test.go; 16 LoC -
Found a possible issue in [pbolla0818/oci_terraform](https://www.github.com/pbolla0818/oci_terraform) at [oci/core_ipsec_test.go](https://github.com/pbolla0818/oci_terraform/blob/c233d54c5fe32f12c234d6dceefba0a9b4ab3022/oci/core_ipsec_test.go#L284-L299)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> reference to ipSecConnectionId is reassigned at line 288
[Click here to see the code in its original context.](https://github.com/pbolla0818/oci_terraform/blob/c233d54c5fe32f12c234d6dceefba0a9b4ab3022/oci/core_ipsec_test.go#L284-L299)
<details>
<summary>Click here to show the 16 line(s) of Go which triggered the analyzer.</summary>
```go
for _, ipSecConnectionId := range ipSecConnectionIds {
if ok := SweeperDefaultResourceId[ipSecConnectionId]; !ok {
deleteIPSecConnectionRequest := oci_core.DeleteIPSecConnectionRequest{}
deleteIPSecConnectionRequest.IpscId = &ipSecConnectionId
deleteIPSecConnectionRequest.RequestMetadata.RetryPolicy = getRetryPolicy(true, "core")
_, error := virtualNetworkClient.DeleteIPSecConnection(context.Background(), deleteIPSecConnectionRequest)
if error != nil {
fmt.Printf("Error deleting IpSecConnection %s %s, It is possible that the resource is already deleted. Please verify manually \n", ipSecConnectionId, error)
continue
}
waitTillCondition(testAccProvider, &ipSecConnectionId, ipSecConnectionSweepWaitCondition, time.Duration(3*time.Minute),
ipSecConnectionSweepResponseFetchOperation, "core", true)
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: c233d54c5fe32f12c234d6dceefba0a9b4ab3022
|
test
|
oci terraform oci core ipsec test go loc found a possible issue in at below is the message reported by the analyzer for this snippet of code beware that the analyzer only reports the first issue it finds so please do not limit your consideration to the contents of the below message reference to ipsecconnectionid is reassigned at line click here to show the line s of go which triggered the analyzer go for ipsecconnectionid range ipsecconnectionids if ok sweeperdefaultresourceid ok deleteipsecconnectionrequest oci core deleteipsecconnectionrequest deleteipsecconnectionrequest ipscid ipsecconnectionid deleteipsecconnectionrequest requestmetadata retrypolicy getretrypolicy true core error virtualnetworkclient deleteipsecconnection context background deleteipsecconnectionrequest if error nil fmt printf error deleting ipsecconnection s s it is possible that the resource is already deleted please verify manually n ipsecconnectionid error continue waittillcondition testaccprovider ipsecconnectionid ipsecconnectionsweepwaitcondition time duration time minute ipsecconnectionsweepresponsefetchoperation core true leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id
| 1
|
161,835
| 6,137,101,326
|
IssuesEvent
|
2017-06-26 11:17:32
|
ProgrammingLife2017/Desoxyribonucleinezuur
|
https://api.github.com/repos/ProgrammingLife2017/Desoxyribonucleinezuur
|
closed
|
Implement method for dynamically moving / zooming (load new nodes as needed)
|
enhancement priority: A time:40
|
User story: #68
part of: #127
prerequisite: #140
Should allow moving and loading new nodes on one side and discarding them on the other side
|
1.0
|
Implement method for dynamically moving / zooming (load new nodes as needed) - User story: #68
part of: #127
prerequisite: #140
Should allow moving and loading new nodes on one side and discarding them on the other side
|
non_test
|
implement method for dynamically moving zooming load new nodes as needed user story part of prerequisite should allow moving and loading new nodes on one side and discarding them on the other side
| 0
|
97,873
| 16,254,166,082
|
IssuesEvent
|
2021-05-08 01:03:38
|
sandrinesuire/project_8
|
https://api.github.com/repos/sandrinesuire/project_8
|
opened
|
CVE-2021-32052 (Medium) detected in Django-2.2.4.tar.gz
|
security vulnerability
|
## CVE-2021-32052 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>Django-2.2.4.tar.gz</b></p></summary>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/19/11/3449a2071df9427e7a5c4dddee2462e88840dd968a9b0c161097154fcb0c/Django-2.2.4.tar.gz">https://files.pythonhosted.org/packages/19/11/3449a2071df9427e7a5c4dddee2462e88840dd968a9b0c161097154fcb0c/Django-2.2.4.tar.gz</a></p>
<p>Path to dependency file: project_8/requirements.txt</p>
<p>Path to vulnerable library: project_8/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-2.2.4.tar.gz** (Vulnerable Library)
</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 Django 2.2 before 2.2.22, 3.1 before 3.1.10, and 3.2 before 3.2.2 (with Python 3.9.5+), URLValidator does not prohibit newlines and tabs (unless the URLField form field is used). If an application uses values with newlines in an HTTP response, header injection can occur. Django itself is unaffected because HttpResponse prohibits newlines in HTTP headers.
<p>Publish Date: 2021-05-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-32052>CVE-2021-32052</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32052">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32052</a></p>
<p>Release Date: 2021-05-06</p>
<p>Fix Resolution: Django - 2.2.22,3.1.10,3.2.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2021-32052 (Medium) detected in Django-2.2.4.tar.gz - ## CVE-2021-32052 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>Django-2.2.4.tar.gz</b></p></summary>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/19/11/3449a2071df9427e7a5c4dddee2462e88840dd968a9b0c161097154fcb0c/Django-2.2.4.tar.gz">https://files.pythonhosted.org/packages/19/11/3449a2071df9427e7a5c4dddee2462e88840dd968a9b0c161097154fcb0c/Django-2.2.4.tar.gz</a></p>
<p>Path to dependency file: project_8/requirements.txt</p>
<p>Path to vulnerable library: project_8/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-2.2.4.tar.gz** (Vulnerable Library)
</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 Django 2.2 before 2.2.22, 3.1 before 3.1.10, and 3.2 before 3.2.2 (with Python 3.9.5+), URLValidator does not prohibit newlines and tabs (unless the URLField form field is used). If an application uses values with newlines in an HTTP response, header injection can occur. Django itself is unaffected because HttpResponse prohibits newlines in HTTP headers.
<p>Publish Date: 2021-05-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-32052>CVE-2021-32052</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32052">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32052</a></p>
<p>Release Date: 2021-05-06</p>
<p>Fix Resolution: Django - 2.2.22,3.1.10,3.2.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve medium detected in django tar gz cve medium severity vulnerability vulnerable library django tar gz a high level python web framework that encourages rapid development and clean pragmatic design library home page a href path to dependency file project requirements txt path to vulnerable library project requirements txt dependency hierarchy x django tar gz vulnerable library vulnerability details in django before before and before with python urlvalidator does not prohibit newlines and tabs unless the urlfield form field is used if an application uses values with newlines in an http response header injection can occur django itself is unaffected because httpresponse prohibits newlines in http headers 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 none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution django step up your open source security game with whitesource
| 0
|
300,604
| 22,688,548,049
|
IssuesEvent
|
2022-07-04 16:35:05
|
jw5374/DunderDB_p1
|
https://api.github.com/repos/jw5374/DunderDB_p1
|
opened
|
Flesh out README
|
documentation
|
Should progressively work to flesh out the readme as our documentation for the project
- [ ] List of features
- [ ] Project setup instructions for other users
- [ ] Annotation list and use case descriptions
- [ ] Method list and use case descriptions
- [ ] Tech stack
|
1.0
|
Flesh out README - Should progressively work to flesh out the readme as our documentation for the project
- [ ] List of features
- [ ] Project setup instructions for other users
- [ ] Annotation list and use case descriptions
- [ ] Method list and use case descriptions
- [ ] Tech stack
|
non_test
|
flesh out readme should progressively work to flesh out the readme as our documentation for the project list of features project setup instructions for other users annotation list and use case descriptions method list and use case descriptions tech stack
| 0
|
141,273
| 11,410,694,806
|
IssuesEvent
|
2020-02-01 00:28:44
|
elastic/elasticsearch
|
https://api.github.com/repos/elastic/elasticsearch
|
closed
|
[CI] LoggingOutputStreamTests fails on Windows
|
:Core/Infra/Logging >test-failure
|
The following tests fail in 7.x Windows builds:
```
org.elasticsearch.common.logging.LoggingOutputStreamTests testBufferExtension
org.elasticsearch.common.logging.LoggingOutputStreamTests testEmptyLine
org.elasticsearch.common.logging.LoggingOutputStreamTests testFlushOnNewline
org.elasticsearch.common.logging.LoggingOutputStreamTests testMaxBuffer
org.elasticsearch.common.logging.LoggingOutputStreamTests testThreadIsolation
```
An example is https://gradle-enterprise.elastic.co/s/yiooghd5t4ai4 (but every 7.x Windows build is failing for this reason).
The errors are all along the lines of this:
```
Expected: iterable containing ["pjsQsvUyoViFJjlUeCGSsMwFyERKKNZexDFEkobYKBmMuiqRUjqKIGjFAIojNnJgIZAqCaewZeaiaIqRupTDLXQhPmAdaRTzNPLYypRYxiVeZQOycAVicOazPvUQifDNMOqaXIJJRAOrlndMd", "OVERFLOW"]
but: item 1: was "\r"
```
It seems like the CRLF Windows line endings are messing up the line splitting.
|
1.0
|
[CI] LoggingOutputStreamTests fails on Windows - The following tests fail in 7.x Windows builds:
```
org.elasticsearch.common.logging.LoggingOutputStreamTests testBufferExtension
org.elasticsearch.common.logging.LoggingOutputStreamTests testEmptyLine
org.elasticsearch.common.logging.LoggingOutputStreamTests testFlushOnNewline
org.elasticsearch.common.logging.LoggingOutputStreamTests testMaxBuffer
org.elasticsearch.common.logging.LoggingOutputStreamTests testThreadIsolation
```
An example is https://gradle-enterprise.elastic.co/s/yiooghd5t4ai4 (but every 7.x Windows build is failing for this reason).
The errors are all along the lines of this:
```
Expected: iterable containing ["pjsQsvUyoViFJjlUeCGSsMwFyERKKNZexDFEkobYKBmMuiqRUjqKIGjFAIojNnJgIZAqCaewZeaiaIqRupTDLXQhPmAdaRTzNPLYypRYxiVeZQOycAVicOazPvUQifDNMOqaXIJJRAOrlndMd", "OVERFLOW"]
but: item 1: was "\r"
```
It seems like the CRLF Windows line endings are messing up the line splitting.
|
test
|
loggingoutputstreamtests fails on windows the following tests fail in x windows builds org elasticsearch common logging loggingoutputstreamtests testbufferextension org elasticsearch common logging loggingoutputstreamtests testemptyline org elasticsearch common logging loggingoutputstreamtests testflushonnewline org elasticsearch common logging loggingoutputstreamtests testmaxbuffer org elasticsearch common logging loggingoutputstreamtests testthreadisolation an example is but every x windows build is failing for this reason the errors are all along the lines of this expected iterable containing but item was r it seems like the crlf windows line endings are messing up the line splitting
| 1
|
299,758
| 25,925,411,450
|
IssuesEvent
|
2022-12-16 03:41:14
|
pytorch/pytorch
|
https://api.github.com/repos/pytorch/pytorch
|
closed
|
DISABLED test_module_and_optimizer_ids (__main__.TestTorchTidyProfiler)
|
module: flaky-tests skipped oncall: profiler
|
Platforms: linux, win, windows
This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_module_and_optimizer_ids&suite=TestTorchTidyProfiler) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/9057443471).
Over the past 3 hours, it has been determined flaky in 4 workflow(s) with 4 failures and 4 successes.
**Debugging instructions (after clicking on the recent samples link):**
DO NOT BE ALARMED IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_module_and_optimizer_ids`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.
cc @robieta @chaekit @aaronenyeshi @ngimel @nbcsm @guotuofeng @guyang3532 @gaoteng-git @tiffzhaofb
|
1.0
|
DISABLED test_module_and_optimizer_ids (__main__.TestTorchTidyProfiler) - Platforms: linux, win, windows
This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_module_and_optimizer_ids&suite=TestTorchTidyProfiler) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/9057443471).
Over the past 3 hours, it has been determined flaky in 4 workflow(s) with 4 failures and 4 successes.
**Debugging instructions (after clicking on the recent samples link):**
DO NOT BE ALARMED IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_module_and_optimizer_ids`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.
cc @robieta @chaekit @aaronenyeshi @ngimel @nbcsm @guotuofeng @guyang3532 @gaoteng-git @tiffzhaofb
|
test
|
disabled test module and optimizer ids main testtorchtidyprofiler platforms linux win windows this test was disabled because it is failing in ci see and the most recent trunk over the past hours it has been determined flaky in workflow s with failures and successes debugging instructions after clicking on the recent samples link do not be alarmed if the ci is green we now shield flaky tests from developers so ci will thus be green but it will be harder to parse the logs to find relevant log snippets click on the workflow logs linked above click on the test step of the job so that it is expanded otherwise the grepping will not work grep for test module and optimizer ids there should be several instances run as flaky tests are rerun in ci from which you can study the logs cc robieta chaekit aaronenyeshi ngimel nbcsm guotuofeng gaoteng git tiffzhaofb
| 1
|
787,515
| 27,720,212,879
|
IssuesEvent
|
2023-03-14 19:59:22
|
svthalia/concrexit
|
https://api.github.com/repos/svthalia/concrexit
|
closed
|
[THALIA] Notification about your registration for Template Broken
|
priority: medium bug
|
### Describe the bug
The email notification template about that you left the queue and are now registerted for the event is broken. The email is missing at the end.
### How to reproduce
Steps to reproduce the behaviour:
1. Sign up for event get in to the queue
2. Wait until you leave the queue
3. Get email notification
4. See error
### Expected behaviour
I expect the email to have the email of who I should contact in there.
### Screenshots
|
1.0
|
[THALIA] Notification about your registration for Template Broken - ### Describe the bug
The email notification template about that you left the queue and are now registerted for the event is broken. The email is missing at the end.
### How to reproduce
Steps to reproduce the behaviour:
1. Sign up for event get in to the queue
2. Wait until you leave the queue
3. Get email notification
4. See error
### Expected behaviour
I expect the email to have the email of who I should contact in there.
### Screenshots
|
non_test
|
notification about your registration for template broken describe the bug the email notification template about that you left the queue and are now registerted for the event is broken the email is missing at the end how to reproduce steps to reproduce the behaviour sign up for event get in to the queue wait until you leave the queue get email notification see error expected behaviour i expect the email to have the email of who i should contact in there screenshots
| 0
|
71,076
| 15,174,133,802
|
IssuesEvent
|
2021-02-13 17:07:57
|
Kites-Foundation/hellomunnar-api
|
https://api.github.com/repos/Kites-Foundation/hellomunnar-api
|
opened
|
CVE-2020-11023 (Medium) detected in jquery-3.2.1.min.js
|
security vulnerability
|
## CVE-2020-11023 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-3.2.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.2.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/3.2.1/jquery.min.js</a></p>
<p>Path to dependency file: hellomunnar-api/node_modules/superagent/docs/tail.html</p>
<p>Path to vulnerable library: hellomunnar-api/node_modules/superagent/docs/tail.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-3.2.1.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Kites-Foundation/hellomunnar-api/commit/9615db119bbf2eeadbfeea4303c4f38c80c3793c">9615db119bbf2eeadbfeea4303c4f38c80c3793c</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11023">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11023</a></p>
<p>Release Date: 2020-04-29</p>
<p>Fix Resolution: jquery - 3.5.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2020-11023 (Medium) detected in jquery-3.2.1.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-3.2.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.2.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/3.2.1/jquery.min.js</a></p>
<p>Path to dependency file: hellomunnar-api/node_modules/superagent/docs/tail.html</p>
<p>Path to vulnerable library: hellomunnar-api/node_modules/superagent/docs/tail.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-3.2.1.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Kites-Foundation/hellomunnar-api/commit/9615db119bbf2eeadbfeea4303c4f38c80c3793c">9615db119bbf2eeadbfeea4303c4f38c80c3793c</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11023">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11023</a></p>
<p>Release Date: 2020-04-29</p>
<p>Fix Resolution: jquery - 3.5.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_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 hellomunnar api node modules superagent docs tail html path to vulnerable library hellomunnar api node modules superagent docs tail 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 step up your open source security game with whitesource
| 0
|
305,606
| 23,122,864,371
|
IssuesEvent
|
2022-07-28 00:20:28
|
datafuselabs/databend
|
https://api.github.com/repos/datafuselabs/databend
|
opened
|
blog: introduce how to load data to databend
|
C-documentation
|
**Summary**
It would be nice to have a new blog post about how to(/how many ways) ingest data to databend.
Load data reference:
https://databend.rs/doc/load-data
|
1.0
|
blog: introduce how to load data to databend - **Summary**
It would be nice to have a new blog post about how to(/how many ways) ingest data to databend.
Load data reference:
https://databend.rs/doc/load-data
|
non_test
|
blog introduce how to load data to databend summary it would be nice to have a new blog post about how to how many ways ingest data to databend load data reference
| 0
|
301,605
| 26,078,175,211
|
IssuesEvent
|
2022-12-24 22:24:53
|
Stiefel1234eu/upptime
|
https://api.github.com/repos/Stiefel1234eu/upptime
|
opened
|
🛑 Speedtest is down
|
status speedtest
|
In [`e018e77`](https://github.com/Stiefel1234eu/upptime/commit/e018e772e800928351a477669f14eac913c50239
), Speedtest ($SITE_SPEEDTEST) was **down**:
- HTTP code: 0
- Response time: 0 ms
|
1.0
|
🛑 Speedtest is down - In [`e018e77`](https://github.com/Stiefel1234eu/upptime/commit/e018e772e800928351a477669f14eac913c50239
), Speedtest ($SITE_SPEEDTEST) was **down**:
- HTTP code: 0
- Response time: 0 ms
|
test
|
🛑 speedtest is down in speedtest site speedtest was down http code response time ms
| 1
|
690,468
| 23,661,139,131
|
IssuesEvent
|
2022-08-26 15:41:10
|
webcompat/web-bugs
|
https://api.github.com/repos/webcompat/web-bugs
|
closed
|
seamagik24.cda-development.co.uk - The page does not finish loading
|
browser-firefox priority-normal severity-critical engine-gecko diagnosis-priority-p2
|
<!-- @browser: Firefox 102.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Firefox/102.0 -->
<!-- @reported_with: unknown -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/107734 -->
**URL**: https://seamagik24.cda-development.co.uk/
**Browser / Version**: Firefox 102.0
**Operating System**: Windows 10
**Tested Another Browser**: Yes Edge
**Problem type**: Site is not usable
**Description**: Page not loading correctly
**Steps to Reproduce**:
Just loading without any response
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
2.0
|
seamagik24.cda-development.co.uk - The page does not finish loading - <!-- @browser: Firefox 102.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Firefox/102.0 -->
<!-- @reported_with: unknown -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/107734 -->
**URL**: https://seamagik24.cda-development.co.uk/
**Browser / Version**: Firefox 102.0
**Operating System**: Windows 10
**Tested Another Browser**: Yes Edge
**Problem type**: Site is not usable
**Description**: Page not loading correctly
**Steps to Reproduce**:
Just loading without any response
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_
|
non_test
|
cda development co uk the page does not finish loading url browser version firefox operating system windows tested another browser yes edge problem type site is not usable description page not loading correctly steps to reproduce just loading without any response browser configuration none from with ❤️
| 0
|
180,580
| 30,529,997,293
|
IssuesEvent
|
2023-07-19 13:45:08
|
Expensify/App
|
https://api.github.com/repos/Expensify/App
|
closed
|
Chat - Emojis used from 4 suggested are not displayed in frequently used
|
Daily Design Bug
|
If you haven’t already, check out our [contributing guidelines](https://github.com/Expensify/ReactNativeChat/blob/main/contributingGuides/CONTRIBUTING.md) for onboarding and email contributors@expensify.com to request to join our Slack channel!
___
## Action Performed:
1. Go to https://staging.new.expensify.com/
2. Tap plus icon
3. Tap new chat
4. Select a user
5. Send a message
6. Long press the message
7. Pick emoticons from 4 listed
8. Long press the message
9. Tap emoticon plus
10. Search and select any emoticon
## Expected Result:
All used emoticons must be displayed in frequently used on opening emoticons plus section
## Actual Result:
Only emoticons used from emoticon plus section is displayed in frequently used but emoticons used from 4 suggested are not displayed in frequently used
## Workaround:
Unknown
## Platforms:
<!---
Check off any platforms that are affected by this issue
--->
Which of our officially supported platforms is this issue occurring on?
- [x] Android / native
- [x] Android / Chrome
- [x] iOS / native
- [x] iOS / Safari
- [x] MacOS / Chrome / Safari
- [x] MacOS / Desktop
**Version Number:** 1.3.33-3
**Reproducible in staging?:** Yes
**Reproducible in production?:** Yes
**If this was caught during regression testing, add the test name, ID and link from TestRail:**
**Email or phone of affected tester (no customers):**
**Logs:** https://stackoverflow.com/c/expensify/questions/4856
**Notes/Photos/Videos:** Any additional supporting documentation
https://github.com/Expensify/App/assets/78819774/15aba9de-ff9f-48b9-b16b-957904372016
**Issue reported by:** Applause - Internal Team
**Slack conversation:**
[View all open jobs on GitHub](https://github.com/Expensify/App/issues?q=is%3Aopen+is%3Aissue+label%3A%22Help+Wanted%22)
|
1.0
|
Chat - Emojis used from 4 suggested are not displayed in frequently used - If you haven’t already, check out our [contributing guidelines](https://github.com/Expensify/ReactNativeChat/blob/main/contributingGuides/CONTRIBUTING.md) for onboarding and email contributors@expensify.com to request to join our Slack channel!
___
## Action Performed:
1. Go to https://staging.new.expensify.com/
2. Tap plus icon
3. Tap new chat
4. Select a user
5. Send a message
6. Long press the message
7. Pick emoticons from 4 listed
8. Long press the message
9. Tap emoticon plus
10. Search and select any emoticon
## Expected Result:
All used emoticons must be displayed in frequently used on opening emoticons plus section
## Actual Result:
Only emoticons used from emoticon plus section is displayed in frequently used but emoticons used from 4 suggested are not displayed in frequently used
## Workaround:
Unknown
## Platforms:
<!---
Check off any platforms that are affected by this issue
--->
Which of our officially supported platforms is this issue occurring on?
- [x] Android / native
- [x] Android / Chrome
- [x] iOS / native
- [x] iOS / Safari
- [x] MacOS / Chrome / Safari
- [x] MacOS / Desktop
**Version Number:** 1.3.33-3
**Reproducible in staging?:** Yes
**Reproducible in production?:** Yes
**If this was caught during regression testing, add the test name, ID and link from TestRail:**
**Email or phone of affected tester (no customers):**
**Logs:** https://stackoverflow.com/c/expensify/questions/4856
**Notes/Photos/Videos:** Any additional supporting documentation
https://github.com/Expensify/App/assets/78819774/15aba9de-ff9f-48b9-b16b-957904372016
**Issue reported by:** Applause - Internal Team
**Slack conversation:**
[View all open jobs on GitHub](https://github.com/Expensify/App/issues?q=is%3Aopen+is%3Aissue+label%3A%22Help+Wanted%22)
|
non_test
|
chat emojis used from suggested are not displayed in frequently used if you haven’t already check out our for onboarding and email contributors expensify com to request to join our slack channel action performed go to tap plus icon tap new chat select a user send a message long press the message pick emoticons from listed long press the message tap emoticon plus search and select any emoticon expected result all used emoticons must be displayed in frequently used on opening emoticons plus section actual result only emoticons used from emoticon plus section is displayed in frequently used but emoticons used from suggested are not displayed in frequently used workaround unknown platforms check off any platforms that are affected by this issue which of our officially supported platforms is this issue occurring on android native android chrome ios native ios safari macos chrome safari macos desktop version number reproducible in staging yes reproducible in production yes if this was caught during regression testing add the test name id and link from testrail email or phone of affected tester no customers logs notes photos videos any additional supporting documentation issue reported by applause internal team slack conversation
| 0
|
394,401
| 11,643,261,628
|
IssuesEvent
|
2020-02-29 12:28:31
|
kubernetes/kubernetes
|
https://api.github.com/repos/kubernetes/kubernetes
|
closed
|
Refactor hack/make-rules to use legacyflags
|
do-not-merge/hold kind/feature lifecycle/rotten priority/important-longterm wg/component-standard
|
**What would you like to be added**:
Refactor hack/make-rules to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg component-standard
/priority important-longterm
/cc @stealthybox
|
1.0
|
Refactor hack/make-rules to use legacyflags - **What would you like to be added**:
Refactor hack/make-rules to use https://github.com/kubernetes-sigs/legacyflag
**Why is this needed**:
This is part of a refactoring initiative run by @kubernetes/wg-component-standard to address the pain-points of backwards-compatible ComponentConfig migration.
/wg component-standard
/priority important-longterm
/cc @stealthybox
|
non_test
|
refactor hack make rules to use legacyflags what would you like to be added refactor hack make rules to use why is this needed this is part of a refactoring initiative run by kubernetes wg component standard to address the pain points of backwards compatible componentconfig migration wg component standard priority important longterm cc stealthybox
| 0
|
198,769
| 14,996,731,899
|
IssuesEvent
|
2021-01-29 15:58:12
|
BlueWallet/BlueWallet
|
https://api.github.com/repos/BlueWallet/BlueWallet
|
closed
|
e2e: watch-only -> receive (& receive with amount)
|
help wanted tests
|
can be part of `can import zpub as watch-only and create PSBT`
|
1.0
|
e2e: watch-only -> receive (& receive with amount) - can be part of `can import zpub as watch-only and create PSBT`
|
test
|
watch only receive receive with amount can be part of can import zpub as watch only and create psbt
| 1
|
193,927
| 22,261,587,636
|
IssuesEvent
|
2022-06-10 01:24:51
|
panasalap/linux-4.19.72_test1
|
https://api.github.com/repos/panasalap/linux-4.19.72_test1
|
reopened
|
CVE-2020-16120 (Medium) detected in linux-yoctov5.4.51
|
security vulnerability
|
## CVE-2020-16120 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yoctov5.4.51</b></p></summary>
<p>
<p>Yocto Linux Embedded kernel</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto>https://git.yoctoproject.org/git/linux-yocto</a></p>
<p>Found in HEAD commit: <a href="https://github.com/panasalap/linux-4.19.72/commit/f1b7c617b9b8f4135ab2f75a0c407cc44d43683f">f1b7c617b9b8f4135ab2f75a0c407cc44d43683f</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/overlayfs/readdir.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/overlayfs/readdir.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Overlayfs did not properly perform permission checking when copying up files in an overlayfs and could be exploited from within a user namespace, if, for example, unprivileged user namespaces were allowed. It was possible to have a file not readable by an unprivileged user to be copied to a mountpoint controlled by the user, like a removable device. This was introduced in kernel version 4.19 by commit d1d04ef ("ovl: stack file ops"). This was fixed in kernel version 5.8 by commits 56230d9 ("ovl: verify permissions in ovl_path_open()"), 48bd024 ("ovl: switch to mounter creds in readdir") and 05acefb ("ovl: check permission to open real file"). Additionally, commits 130fdbc ("ovl: pass correct flags for opening real directory") and 292f902 ("ovl: call secutiry hook in ovl_real_ioctl()") in kernel 5.8 might also be desired or necessary. These additional commits introduced a regression in overlay mounts within user namespaces which prevented access to files with ownership outside of the user namespace. This regression was mitigated by subsequent commit b6650da ("ovl: do not fail because of O_NOATIMEi") in kernel 5.11.
<p>Publish Date: 2021-02-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-16120>CVE-2020-16120</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>4.4</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2020-16120">https://www.linuxkernelcves.com/cves/CVE-2020-16120</a></p>
<p>Release Date: 2021-02-10</p>
<p>Fix Resolution: v5.8-rc1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2020-16120 (Medium) detected in linux-yoctov5.4.51 - ## CVE-2020-16120 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yoctov5.4.51</b></p></summary>
<p>
<p>Yocto Linux Embedded kernel</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto>https://git.yoctoproject.org/git/linux-yocto</a></p>
<p>Found in HEAD commit: <a href="https://github.com/panasalap/linux-4.19.72/commit/f1b7c617b9b8f4135ab2f75a0c407cc44d43683f">f1b7c617b9b8f4135ab2f75a0c407cc44d43683f</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/overlayfs/readdir.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/overlayfs/readdir.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Overlayfs did not properly perform permission checking when copying up files in an overlayfs and could be exploited from within a user namespace, if, for example, unprivileged user namespaces were allowed. It was possible to have a file not readable by an unprivileged user to be copied to a mountpoint controlled by the user, like a removable device. This was introduced in kernel version 4.19 by commit d1d04ef ("ovl: stack file ops"). This was fixed in kernel version 5.8 by commits 56230d9 ("ovl: verify permissions in ovl_path_open()"), 48bd024 ("ovl: switch to mounter creds in readdir") and 05acefb ("ovl: check permission to open real file"). Additionally, commits 130fdbc ("ovl: pass correct flags for opening real directory") and 292f902 ("ovl: call secutiry hook in ovl_real_ioctl()") in kernel 5.8 might also be desired or necessary. These additional commits introduced a regression in overlay mounts within user namespaces which prevented access to files with ownership outside of the user namespace. This regression was mitigated by subsequent commit b6650da ("ovl: do not fail because of O_NOATIMEi") in kernel 5.11.
<p>Publish Date: 2021-02-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-16120>CVE-2020-16120</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>4.4</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2020-16120">https://www.linuxkernelcves.com/cves/CVE-2020-16120</a></p>
<p>Release Date: 2021-02-10</p>
<p>Fix Resolution: v5.8-rc1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve medium detected in linux cve medium severity vulnerability vulnerable library linux yocto linux embedded kernel library home page a href found in head commit a href found in base branch master vulnerable source files fs overlayfs readdir c fs overlayfs readdir c vulnerability details overlayfs did not properly perform permission checking when copying up files in an overlayfs and could be exploited from within a user namespace if for example unprivileged user namespaces were allowed it was possible to have a file not readable by an unprivileged user to be copied to a mountpoint controlled by the user like a removable device this was introduced in kernel version by commit ovl stack file ops this was fixed in kernel version by commits ovl verify permissions in ovl path open ovl switch to mounter creds in readdir and ovl check permission to open real file additionally commits ovl pass correct flags for opening real directory and ovl call secutiry hook in ovl real ioctl in kernel might also be desired or necessary these additional commits introduced a regression in overlay mounts within user namespaces which prevented access to files with ownership outside of the user namespace this regression was mitigated by subsequent commit ovl do not fail because of o noatimei in kernel publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required high user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
| 0
|
789,436
| 27,789,688,096
|
IssuesEvent
|
2023-03-17 07:51:56
|
hotosm/odkconvert
|
https://api.github.com/repos/hotosm/odkconvert
|
closed
|
Update logging throughout codebase
|
enhancement Priority: Should have
|
The logger needs to be instantiated using:
`log = logging.getLogger(__name__)`
in all modules, to allow this to be hooked by upstream loggers.
The logging still needs to work when odkconvert is used standalone and when it's incorporated into fmtm.
The code above will make it work with upstream fmtm, but to make it work standalone we need to create a basicLogger (https://github.com/hotosm/fmtm/blob/14a917952596cab53a7cb8bfc426551dd4a0068c/src/backend/main.py#L44) instance in the modules that will be called.
CSVDump.py and odk_client.py are called standalone and need the logger defined first. I will need to check if there are any other modules. Input from @rsavoye would be great if possible!
|
1.0
|
Update logging throughout codebase - The logger needs to be instantiated using:
`log = logging.getLogger(__name__)`
in all modules, to allow this to be hooked by upstream loggers.
The logging still needs to work when odkconvert is used standalone and when it's incorporated into fmtm.
The code above will make it work with upstream fmtm, but to make it work standalone we need to create a basicLogger (https://github.com/hotosm/fmtm/blob/14a917952596cab53a7cb8bfc426551dd4a0068c/src/backend/main.py#L44) instance in the modules that will be called.
CSVDump.py and odk_client.py are called standalone and need the logger defined first. I will need to check if there are any other modules. Input from @rsavoye would be great if possible!
|
non_test
|
update logging throughout codebase the logger needs to be instantiated using log logging getlogger name in all modules to allow this to be hooked by upstream loggers the logging still needs to work when odkconvert is used standalone and when it s incorporated into fmtm the code above will make it work with upstream fmtm but to make it work standalone we need to create a basiclogger instance in the modules that will be called csvdump py and odk client py are called standalone and need the logger defined first i will need to check if there are any other modules input from rsavoye would be great if possible
| 0
|
69,634
| 17,782,399,966
|
IssuesEvent
|
2021-08-31 06:59:33
|
Crocoblock/suggestions
|
https://api.github.com/repos/Crocoblock/suggestions
|
closed
|
Custom Fields in Jet Engine Display on Products Grid
|
JetWooBuilder Pending
|
Hi Crocoblock Team,
Would it be possible to add the option of adding custom fields created in jetengine to display on the jetwoo products grid. In my case I am creating a bookshop ecommerce site. The book title and price are displayed but I would like to also show the name of the author of said book.
|
1.0
|
Custom Fields in Jet Engine Display on Products Grid - Hi Crocoblock Team,
Would it be possible to add the option of adding custom fields created in jetengine to display on the jetwoo products grid. In my case I am creating a bookshop ecommerce site. The book title and price are displayed but I would like to also show the name of the author of said book.
|
non_test
|
custom fields in jet engine display on products grid hi crocoblock team would it be possible to add the option of adding custom fields created in jetengine to display on the jetwoo products grid in my case i am creating a bookshop ecommerce site the book title and price are displayed but i would like to also show the name of the author of said book
| 0
|
184,055
| 14,268,684,149
|
IssuesEvent
|
2020-11-20 23:02:19
|
cyberark/conjur-oss-suite-release
|
https://api.github.com/repos/cyberark/conjur-oss-suite-release
|
closed
|
Fix broken unit tests
|
component/suite kind/failing-test
|
There have been some changes to GitHub actions that leave our UTs in this project in a broken state. See [here](https://github.com/cyberark/conjur-oss-suite-release/actions/runs/375225374) for an example.
|
1.0
|
Fix broken unit tests - There have been some changes to GitHub actions that leave our UTs in this project in a broken state. See [here](https://github.com/cyberark/conjur-oss-suite-release/actions/runs/375225374) for an example.
|
test
|
fix broken unit tests there have been some changes to github actions that leave our uts in this project in a broken state see for an example
| 1
|
294,443
| 25,372,037,217
|
IssuesEvent
|
2022-11-21 11:17:18
|
mozilla-mobile/focus-android
|
https://api.github.com/repos/mozilla-mobile/focus-android
|
closed
|
Intermittent UI test failure - EnhancedTrackingProtectionSettingsTest.blockAnalyticsTrackersTest
|
eng:ui-test eng:intermittent-test eng:disabled-test
|
Was disabled along with other tests, see https://github.com/mozilla-mobile/focus-android/issues/6812, but not mentioned in the issue, so it was missed when 6812 was fixed.
|
3.0
|
Intermittent UI test failure - EnhancedTrackingProtectionSettingsTest.blockAnalyticsTrackersTest - Was disabled along with other tests, see https://github.com/mozilla-mobile/focus-android/issues/6812, but not mentioned in the issue, so it was missed when 6812 was fixed.
|
test
|
intermittent ui test failure enhancedtrackingprotectionsettingstest blockanalyticstrackerstest was disabled along with other tests see but not mentioned in the issue so it was missed when was fixed
| 1
|
297,902
| 25,771,549,284
|
IssuesEvent
|
2022-12-09 08:25:51
|
hzi-braunschweig/SORMAS-Project
|
https://api.github.com/repos/hzi-braunschweig/SORMAS-Project
|
opened
|
Inverse API response checks in automated tests
|
testing task e2e-tests
|
Currently we're checking first response message then status code.
Please inverse order of check, to expose first the status of the call so we can determine faster if there are server side failures.
|
2.0
|
Inverse API response checks in automated tests - Currently we're checking first response message then status code.
Please inverse order of check, to expose first the status of the call so we can determine faster if there are server side failures.
|
test
|
inverse api response checks in automated tests currently we re checking first response message then status code please inverse order of check to expose first the status of the call so we can determine faster if there are server side failures
| 1
|
81,597
| 7,787,573,215
|
IssuesEvent
|
2018-06-06 23:10:54
|
medic/medic-webapp
|
https://api.github.com/repos/medic/medic-webapp
|
closed
|
Exporting reports causes API to stop
|
Priority: 1 - High Reports Status: 4 - Acceptance testing Type: Bug
|
When attempting to export all reports (no filters selected) on beta-old.dev, the file starts downloading but stops and never completes. It also causes API to stop with no errors in the logs. This is working properly on standard.dev which is also on the same version but has fewer reports.
**Steps to reproduce**:
- Log into beta-old.dev as admin
- Go to the reports page
- Click Export
**What should happen**:
- CSV should download that contains all reports, all fields
**What actually happens**:
- CSV starts downloading but doesn't finish - it stops at 251 KB each time
- API stops with no errors in the logs
https://beta-old.dev.medicmobile.org/medic/_design/medic/_rewrite/#/reports/
I couldn't find anything in the logs, but here are the results from `top` - lots of CPU usage.
```
Mem: 3325280K used, 337604K free, 4376K shrd, 72540K buff, 2421808K cached
CPU: 97.7% usr 2.2% sys 0.0% nic 0.0% idle 0.0% io 0.0% irq 0.0% sirq
Load average: 1.32 0.60 0.37 3/177 12014
```
| PID | PPID | USER | STAT | VSZ | %VSZ | CPU | %CPU | COMMAND |
| ---- | ------ | ------- | ------ | ---- | -------- | ----- | -------- | -------------- |
| 11845 | 11266 | vm | R | 11292 | 0.3 | 0 | 0.2 | top |
| 11265 | 11052 | vm | S | 21172 | 0.5 | 0 | 0.0 | sshd: vm@pts/0 |
| 8105 | 1 | vm | S | 12860 | 0.3 | 0 | 0.0 | {screen} SCREEN -R |
| 8106 | 8105 | vm | S | 11292 | 0.3 | 0 | 0.0 | /bin/sh |
| 11266 | 11265 | vm | S | 11292 | 0.3 | 0 | 0.0 | -sh |
**Environment**:
- Instance: beta-old.dev
- Browser: Chrome
- Client platform: MacOS
- App: webapp
- Version: 2.15.0-beta.15
**Other**:
API is definitely stopping because restarting services brings it back up and the instance starts working again. Probably worth investigating whether there is something specific wrong with the beta-old instance or if this is happening elsewhere as well. I did make sure to delete API and Sentinel before upgrading to the latest beta but maybe there is something else going on. Since this is working fine on standard.dev, it could be a server issue. It was also weird that the export from standard.dev was exactly 250 KB and the export from beta-old.dev stops at exactly 251 KB each time.
|
1.0
|
Exporting reports causes API to stop - When attempting to export all reports (no filters selected) on beta-old.dev, the file starts downloading but stops and never completes. It also causes API to stop with no errors in the logs. This is working properly on standard.dev which is also on the same version but has fewer reports.
**Steps to reproduce**:
- Log into beta-old.dev as admin
- Go to the reports page
- Click Export
**What should happen**:
- CSV should download that contains all reports, all fields
**What actually happens**:
- CSV starts downloading but doesn't finish - it stops at 251 KB each time
- API stops with no errors in the logs
https://beta-old.dev.medicmobile.org/medic/_design/medic/_rewrite/#/reports/
I couldn't find anything in the logs, but here are the results from `top` - lots of CPU usage.
```
Mem: 3325280K used, 337604K free, 4376K shrd, 72540K buff, 2421808K cached
CPU: 97.7% usr 2.2% sys 0.0% nic 0.0% idle 0.0% io 0.0% irq 0.0% sirq
Load average: 1.32 0.60 0.37 3/177 12014
```
| PID | PPID | USER | STAT | VSZ | %VSZ | CPU | %CPU | COMMAND |
| ---- | ------ | ------- | ------ | ---- | -------- | ----- | -------- | -------------- |
| 11845 | 11266 | vm | R | 11292 | 0.3 | 0 | 0.2 | top |
| 11265 | 11052 | vm | S | 21172 | 0.5 | 0 | 0.0 | sshd: vm@pts/0 |
| 8105 | 1 | vm | S | 12860 | 0.3 | 0 | 0.0 | {screen} SCREEN -R |
| 8106 | 8105 | vm | S | 11292 | 0.3 | 0 | 0.0 | /bin/sh |
| 11266 | 11265 | vm | S | 11292 | 0.3 | 0 | 0.0 | -sh |
**Environment**:
- Instance: beta-old.dev
- Browser: Chrome
- Client platform: MacOS
- App: webapp
- Version: 2.15.0-beta.15
**Other**:
API is definitely stopping because restarting services brings it back up and the instance starts working again. Probably worth investigating whether there is something specific wrong with the beta-old instance or if this is happening elsewhere as well. I did make sure to delete API and Sentinel before upgrading to the latest beta but maybe there is something else going on. Since this is working fine on standard.dev, it could be a server issue. It was also weird that the export from standard.dev was exactly 250 KB and the export from beta-old.dev stops at exactly 251 KB each time.
|
test
|
exporting reports causes api to stop when attempting to export all reports no filters selected on beta old dev the file starts downloading but stops and never completes it also causes api to stop with no errors in the logs this is working properly on standard dev which is also on the same version but has fewer reports steps to reproduce log into beta old dev as admin go to the reports page click export what should happen csv should download that contains all reports all fields what actually happens csv starts downloading but doesn t finish it stops at kb each time api stops with no errors in the logs i couldn t find anything in the logs but here are the results from top lots of cpu usage mem used free shrd buff cached cpu usr sys nic idle io irq sirq load average pid ppid user stat vsz vsz cpu cpu command vm r top vm s sshd vm pts vm s screen screen r vm s bin sh vm s sh environment instance beta old dev browser chrome client platform macos app webapp version beta other api is definitely stopping because restarting services brings it back up and the instance starts working again probably worth investigating whether there is something specific wrong with the beta old instance or if this is happening elsewhere as well i did make sure to delete api and sentinel before upgrading to the latest beta but maybe there is something else going on since this is working fine on standard dev it could be a server issue it was also weird that the export from standard dev was exactly kb and the export from beta old dev stops at exactly kb each time
| 1
|
325,798
| 27,963,137,780
|
IssuesEvent
|
2023-03-24 17:08:37
|
swarmion/swarmion
|
https://api.github.com/repos/swarmion/swarmion
|
closed
|
`syncEnvVarType` is broken
|
bug @swarmion/integration-tests
|
When I use `@swarmion/integration-tests` on Canopia the `syncEnvVarType` util is broken:
```
yarn sls deploy
Error while trying to sync config types: [TypeError] (0 , import_traverse.default) is not a function
```
This is the problem of compatibility between @babel/traverse and ESM: https://github.com/babel/babel/issues/13855
I suppose, it worked on Canopia before because the package was bundled with the old method (babel + cjs first).
Now `@swarmion/integration-tests` is bundled with tsup and is ESM first
=> I suppose node load the package as ESM when I run `sls deploy`
Versions:
- Node: `14.18.1`
- Sls framework: `3.25.0`
- `@swarmion/integration-tests`: `0.26.0-alpha.0`
|
1.0
|
`syncEnvVarType` is broken - When I use `@swarmion/integration-tests` on Canopia the `syncEnvVarType` util is broken:
```
yarn sls deploy
Error while trying to sync config types: [TypeError] (0 , import_traverse.default) is not a function
```
This is the problem of compatibility between @babel/traverse and ESM: https://github.com/babel/babel/issues/13855
I suppose, it worked on Canopia before because the package was bundled with the old method (babel + cjs first).
Now `@swarmion/integration-tests` is bundled with tsup and is ESM first
=> I suppose node load the package as ESM when I run `sls deploy`
Versions:
- Node: `14.18.1`
- Sls framework: `3.25.0`
- `@swarmion/integration-tests`: `0.26.0-alpha.0`
|
test
|
syncenvvartype is broken when i use swarmion integration tests on canopia the syncenvvartype util is broken yarn sls deploy error while trying to sync config types import traverse default is not a function this is the problem of compatibility between babel traverse and esm i suppose it worked on canopia before because the package was bundled with the old method babel cjs first now swarmion integration tests is bundled with tsup and is esm first i suppose node load the package as esm when i run sls deploy versions node sls framework swarmion integration tests alpha
| 1
|
94,108
| 3,919,170,120
|
IssuesEvent
|
2016-04-21 14:56:08
|
twosigma/beaker-notebook
|
https://api.github.com/repos/twosigma/beaker-notebook
|
closed
|
default notebook should be read every time.
|
Bug Core Server Priority High
|
it seems the default notebook is only read from disk once.
it should be read every time so the user can change it and get feedback without rebooting beaker.
|
1.0
|
default notebook should be read every time. - it seems the default notebook is only read from disk once.
it should be read every time so the user can change it and get feedback without rebooting beaker.
|
non_test
|
default notebook should be read every time it seems the default notebook is only read from disk once it should be read every time so the user can change it and get feedback without rebooting beaker
| 0
|
272,684
| 23,696,016,236
|
IssuesEvent
|
2022-08-29 14:42:42
|
cockroachdb/cockroach
|
https://api.github.com/repos/cockroachdb/cockroach
|
closed
|
ccl/changefeedccl: TestChangefeedNemeses failed
|
C-test-failure O-robot branch-master release-blocker T-cdc
|
ccl/changefeedccl.TestChangefeedNemeses [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/5658870?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/5658870?buildTab=artifacts#/) on master @ [33d70998719051ee058bc9e516afa238ea7b7451](https://github.com/cockroachdb/cockroach/commits/33d70998719051ee058bc9e516afa238ea7b7451):
```
=== RUN TestChangefeedNemeses
test_log_scope.go:79: test logs captured to: /artifacts/tmp/_tmp/a77002d7c9453d7cd2d382f907780e13/logTestChangefeedNemeses755396176
test_log_scope.go:80: use -show-logs to present logs inline
=== CONT TestChangefeedNemeses
nemeses_test.go:59: -- test log scope end --
--- FAIL: TestChangefeedNemeses (4.76s)
=== RUN TestChangefeedNemeses/cloudstorage
helpers_test.go:678: making server as system tenant
helpers_test.go:765: making cloudstorage feed factory
nemeses_test.go:40: topic foo partition : saw new row timestamp 1657085602994720146.0000000000 after 1657085603125890405.0000000000 was seen
nemeses_test.go:40: fingerprints did not match at 1657085602915039067.0000000000: EMPTY vs -4371770392475824696
nemeses_test.go:40: fingerprints did not match at 1657085602936527623.0000000000: EMPTY vs -4371770392475824696
nemeses_test.go:40: fingerprints did not match at 1657085602994720145.2147483647: EMPTY vs -4371770392475824696
nemeses_test.go:40: fingerprints did not match at 1657085602994720146.0000000000: -8696398075016565150 vs 4901158821878539178
nemeses_test.go:40: fingerprints did not match at 1657085603018493714.0000000000: -8696398075016565150 vs 4901158821878539178
nemeses_test.go:40: fingerprints did not match at 1657085603125890404.2147483647: -8696398075016565150 vs 4901158821878539178
nemeses_test.go:40: fingerprints did not match at 1657085603125890405.0000000000: -8696398075016565150 vs 4901158821878539178
nemeses_test.go:40: fingerprints did not match at 1657085603137258302.2147483647: -8696398075016565150 vs 4901158821878539178
nemeses_test.go:40: fingerprints did not match at 1657085603137258302.2147483647: -8696398075016565150 vs 4901158821878539178
nemeses_test.go:40: fingerprints did not match at 1657085603137258303.0000000000: 3202056503709913342 vs -1208191130819928778
nemeses_test.go:40: fingerprints did not match at 1657085603538971071.0000000000: 3202056503709913342 vs -1208191130819928778
nemeses_test.go:40: fingerprints did not match at 1657085603739546738.0000000000: 3202056503709913342 vs -1208191130819928778
nemeses_test.go:40: fingerprints did not match at 1657085603939901732.0000000000: 3202056503709913342 vs -1208191130819928778
nemeses_test.go:40: fingerprints did not match at 1657085604056173068.2147483647: 3202056503709913342 vs -1208191130819928778
nemeses_test.go:40: fingerprints did not match at 1657085604056173069.0000000000: 3202056503709913342 vs -1208191130819928778
nemeses_test.go:40: fingerprints did not match at 1657085604061878208.2147483647: 3202056503709913342 vs -1208191130819928778
nemeses_test.go:40: fingerprints did not match at 1657085604061878208.2147483647: 3202056503709913342 vs -1208191130819928778
nemeses_test.go:40: fingerprints did not match at 1657085604061878209.0000000000: -2441903359552905246 vs 2110152103965790762
nemeses_test.go:40: fingerprints did not match at 1657085604341564517.0000000000: -2441903359552905246 vs 2110152103965790762
--- FAIL: TestChangefeedNemeses/cloudstorage (4.68s)
```
<p>Parameters: <code>TAGS=bazel,gss</code>
</p>
<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/cdc
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestChangefeedNemeses.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-17328
|
1.0
|
ccl/changefeedccl: TestChangefeedNemeses failed - ccl/changefeedccl.TestChangefeedNemeses [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/5658870?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/5658870?buildTab=artifacts#/) on master @ [33d70998719051ee058bc9e516afa238ea7b7451](https://github.com/cockroachdb/cockroach/commits/33d70998719051ee058bc9e516afa238ea7b7451):
```
=== RUN TestChangefeedNemeses
test_log_scope.go:79: test logs captured to: /artifacts/tmp/_tmp/a77002d7c9453d7cd2d382f907780e13/logTestChangefeedNemeses755396176
test_log_scope.go:80: use -show-logs to present logs inline
=== CONT TestChangefeedNemeses
nemeses_test.go:59: -- test log scope end --
--- FAIL: TestChangefeedNemeses (4.76s)
=== RUN TestChangefeedNemeses/cloudstorage
helpers_test.go:678: making server as system tenant
helpers_test.go:765: making cloudstorage feed factory
nemeses_test.go:40: topic foo partition : saw new row timestamp 1657085602994720146.0000000000 after 1657085603125890405.0000000000 was seen
nemeses_test.go:40: fingerprints did not match at 1657085602915039067.0000000000: EMPTY vs -4371770392475824696
nemeses_test.go:40: fingerprints did not match at 1657085602936527623.0000000000: EMPTY vs -4371770392475824696
nemeses_test.go:40: fingerprints did not match at 1657085602994720145.2147483647: EMPTY vs -4371770392475824696
nemeses_test.go:40: fingerprints did not match at 1657085602994720146.0000000000: -8696398075016565150 vs 4901158821878539178
nemeses_test.go:40: fingerprints did not match at 1657085603018493714.0000000000: -8696398075016565150 vs 4901158821878539178
nemeses_test.go:40: fingerprints did not match at 1657085603125890404.2147483647: -8696398075016565150 vs 4901158821878539178
nemeses_test.go:40: fingerprints did not match at 1657085603125890405.0000000000: -8696398075016565150 vs 4901158821878539178
nemeses_test.go:40: fingerprints did not match at 1657085603137258302.2147483647: -8696398075016565150 vs 4901158821878539178
nemeses_test.go:40: fingerprints did not match at 1657085603137258302.2147483647: -8696398075016565150 vs 4901158821878539178
nemeses_test.go:40: fingerprints did not match at 1657085603137258303.0000000000: 3202056503709913342 vs -1208191130819928778
nemeses_test.go:40: fingerprints did not match at 1657085603538971071.0000000000: 3202056503709913342 vs -1208191130819928778
nemeses_test.go:40: fingerprints did not match at 1657085603739546738.0000000000: 3202056503709913342 vs -1208191130819928778
nemeses_test.go:40: fingerprints did not match at 1657085603939901732.0000000000: 3202056503709913342 vs -1208191130819928778
nemeses_test.go:40: fingerprints did not match at 1657085604056173068.2147483647: 3202056503709913342 vs -1208191130819928778
nemeses_test.go:40: fingerprints did not match at 1657085604056173069.0000000000: 3202056503709913342 vs -1208191130819928778
nemeses_test.go:40: fingerprints did not match at 1657085604061878208.2147483647: 3202056503709913342 vs -1208191130819928778
nemeses_test.go:40: fingerprints did not match at 1657085604061878208.2147483647: 3202056503709913342 vs -1208191130819928778
nemeses_test.go:40: fingerprints did not match at 1657085604061878209.0000000000: -2441903359552905246 vs 2110152103965790762
nemeses_test.go:40: fingerprints did not match at 1657085604341564517.0000000000: -2441903359552905246 vs 2110152103965790762
--- FAIL: TestChangefeedNemeses/cloudstorage (4.68s)
```
<p>Parameters: <code>TAGS=bazel,gss</code>
</p>
<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/cdc
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestChangefeedNemeses.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-17328
|
test
|
ccl changefeedccl testchangefeednemeses failed ccl changefeedccl testchangefeednemeses with on master run testchangefeednemeses test log scope go test logs captured to artifacts tmp tmp test log scope go use show logs to present logs inline cont testchangefeednemeses nemeses test go test log scope end fail testchangefeednemeses run testchangefeednemeses cloudstorage helpers test go making server as system tenant helpers test go making cloudstorage feed factory nemeses test go topic foo partition saw new row timestamp after was seen nemeses test go fingerprints did not match at empty vs nemeses test go fingerprints did not match at empty vs nemeses test go fingerprints did not match at empty vs nemeses test go fingerprints did not match at vs nemeses test go fingerprints did not match at vs nemeses test go fingerprints did not match at vs nemeses test go fingerprints did not match at vs nemeses test go fingerprints did not match at vs nemeses test go fingerprints did not match at vs nemeses test go fingerprints did not match at vs nemeses test go fingerprints did not match at vs nemeses test go fingerprints did not match at vs nemeses test go fingerprints did not match at vs nemeses test go fingerprints did not match at vs nemeses test go fingerprints did not match at vs nemeses test go fingerprints did not match at vs nemeses test go fingerprints did not match at vs nemeses test go fingerprints did not match at vs nemeses test go fingerprints did not match at vs fail testchangefeednemeses cloudstorage parameters tags bazel gss help see also cc cockroachdb cdc jira issue crdb
| 1
|
75,513
| 9,276,503,791
|
IssuesEvent
|
2019-03-20 03:13:19
|
franceme/rigorityj
|
https://api.github.com/repos/franceme/rigorityj
|
opened
|
Design Maven Plugin (Spike)
|
Needs: Design Priority: Low Status: Pending Type: Enhancement
|
Determine the requirements for creating the requirements to make a maven plugin.
|
1.0
|
Design Maven Plugin (Spike) - Determine the requirements for creating the requirements to make a maven plugin.
|
non_test
|
design maven plugin spike determine the requirements for creating the requirements to make a maven plugin
| 0
|
149,739
| 19,585,540,903
|
IssuesEvent
|
2022-01-05 06:08:49
|
dotnet/aspnetcore
|
https://api.github.com/repos/dotnet/aspnetcore
|
closed
|
IClaimsTransformation TransformAsync not called in Firefox (asp.net core 6.0 razor pages web app)
|
Needs: Author Feedback area-security
|
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Describe the bug
The Claims Transformer's constructor is called as expected, but TransformAsync is not in latest Firefox 95.0.2. Start page is not showing.
TransformAsync is called in latest Chrome, MS Edge and Opera. Start page is showing correctly.
### Expected Behavior
TransformAsync is called in all browsers. Start page is showing correctly.
### Steps To Reproduce
1. Create new ASP.NET Core 6.0 Web App from a template, set Authentification Type to Windows.
2. Add simple ClaimsTransformer class
```
public class ClaimsTransformer : IClaimsTransformation
{
private readonly IHttpContextAccessor _accessor;
public ClaimsTransformer(IHttpContextAccessor accessor)
{
_accessor = accessor;
}
public Task<ClaimsPrincipal> TransformAsync(ClaimsPrincipal principal)
{
return Task.FromResult(principal);
}
}
```
3. Add HttpContextAccessor and ClaimsTransformer to services
```
builder.Services.AddAuthentication(NegotiateDefaults.AuthenticationScheme)
.AddNegotiate();
builder.Services.AddAuthorization(options =>
{
// By default, all incoming requests will be authorized according to the default policy.
options.FallbackPolicy = options.DefaultPolicy;
});
builder.Services.AddHttpContextAccessor();
builder.Services.AddScoped<IClaimsTransformation, ClaimsTransformer>();
builder.Services.AddRazorPages();
var app = builder.Build();
```
4. Run app - the Claims Transformer's constructor is called as expected, but TransformAsync is not in latest Firefox 95.0.2
This reproduces on Windows 10 1909, Windows 10 21H2 and Windows 11.
sample repo - https://github.com/bairog/ClaimsTransformerTest
### Exceptions (if any)
_No response_
### .NET Version
6.0.101
### Anything else?
ASP.NET Core version - 6.0
The IDE Visual Studio 2022 Pro 17.0.4
dotnet --info
.NET Core SDK (reflecting any global.json):
Version: 6.0.101
Commit: ef49f6213a
Runtime Environment:
OS Name: Windows
OS Version: 10.0.18363
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\6.0.101\
Host (useful for support):
Version: 6.0.1
Commit: 3a25a7f1cc
.NET SDKs installed:
5.0.101 [C:\Program Files\dotnet\sdk]
5.0.404 [C:\Program Files\dotnet\sdk]
6.0.101 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.All 2.1.26 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.26 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.22 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.13 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.26 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.22 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.13 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.1.22 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.13 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
|
True
|
IClaimsTransformation TransformAsync not called in Firefox (asp.net core 6.0 razor pages web app) - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Describe the bug
The Claims Transformer's constructor is called as expected, but TransformAsync is not in latest Firefox 95.0.2. Start page is not showing.
TransformAsync is called in latest Chrome, MS Edge and Opera. Start page is showing correctly.
### Expected Behavior
TransformAsync is called in all browsers. Start page is showing correctly.
### Steps To Reproduce
1. Create new ASP.NET Core 6.0 Web App from a template, set Authentification Type to Windows.
2. Add simple ClaimsTransformer class
```
public class ClaimsTransformer : IClaimsTransformation
{
private readonly IHttpContextAccessor _accessor;
public ClaimsTransformer(IHttpContextAccessor accessor)
{
_accessor = accessor;
}
public Task<ClaimsPrincipal> TransformAsync(ClaimsPrincipal principal)
{
return Task.FromResult(principal);
}
}
```
3. Add HttpContextAccessor and ClaimsTransformer to services
```
builder.Services.AddAuthentication(NegotiateDefaults.AuthenticationScheme)
.AddNegotiate();
builder.Services.AddAuthorization(options =>
{
// By default, all incoming requests will be authorized according to the default policy.
options.FallbackPolicy = options.DefaultPolicy;
});
builder.Services.AddHttpContextAccessor();
builder.Services.AddScoped<IClaimsTransformation, ClaimsTransformer>();
builder.Services.AddRazorPages();
var app = builder.Build();
```
4. Run app - the Claims Transformer's constructor is called as expected, but TransformAsync is not in latest Firefox 95.0.2
This reproduces on Windows 10 1909, Windows 10 21H2 and Windows 11.
sample repo - https://github.com/bairog/ClaimsTransformerTest
### Exceptions (if any)
_No response_
### .NET Version
6.0.101
### Anything else?
ASP.NET Core version - 6.0
The IDE Visual Studio 2022 Pro 17.0.4
dotnet --info
.NET Core SDK (reflecting any global.json):
Version: 6.0.101
Commit: ef49f6213a
Runtime Environment:
OS Name: Windows
OS Version: 10.0.18363
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\6.0.101\
Host (useful for support):
Version: 6.0.1
Commit: 3a25a7f1cc
.NET SDKs installed:
5.0.101 [C:\Program Files\dotnet\sdk]
5.0.404 [C:\Program Files\dotnet\sdk]
6.0.101 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.All 2.1.26 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.26 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.22 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.13 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.26 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.22 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.13 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.1.22 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.13 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
|
non_test
|
iclaimstransformation transformasync not called in firefox asp net core razor pages web app is there an existing issue for this i have searched the existing issues describe the bug the claims transformer s constructor is called as expected but transformasync is not in latest firefox start page is not showing transformasync is called in latest chrome ms edge and opera start page is showing correctly expected behavior transformasync is called in all browsers start page is showing correctly steps to reproduce create new asp net core web app from a template set authentification type to windows add simple claimstransformer class public class claimstransformer iclaimstransformation private readonly ihttpcontextaccessor accessor public claimstransformer ihttpcontextaccessor accessor accessor accessor public task transformasync claimsprincipal principal return task fromresult principal add httpcontextaccessor and claimstransformer to services builder services addauthentication negotiatedefaults authenticationscheme addnegotiate builder services addauthorization options by default all incoming requests will be authorized according to the default policy options fallbackpolicy options defaultpolicy builder services addhttpcontextaccessor builder services addscoped builder services addrazorpages var app builder build run app the claims transformer s constructor is called as expected but transformasync is not in latest firefox this reproduces on windows windows and windows sample repo exceptions if any no response net version anything else asp net core version the ide visual studio pro dotnet info net core sdk reflecting any global json version commit runtime environment os name windows os version os platform windows rid base path c program files dotnet sdk host useful for support version commit net sdks installed net runtimes installed microsoft aspnetcore all microsoft aspnetcore app microsoft aspnetcore app microsoft aspnetcore app microsoft aspnetcore app microsoft aspnetcore app microsoft netcore app microsoft netcore app microsoft netcore app microsoft netcore app microsoft netcore app microsoft windowsdesktop app microsoft windowsdesktop app microsoft windowsdesktop app microsoft windowsdesktop app
| 0
|
4,713
| 2,741,670,128
|
IssuesEvent
|
2015-04-21 12:44:43
|
alexreisner/geocoder
|
https://api.github.com/repos/alexreisner/geocoder
|
closed
|
Silence Test Warnings
|
testing
|
Currently several tests are producing irrelevant warnings. These should be silenced for clean test output.
|
1.0
|
Silence Test Warnings - Currently several tests are producing irrelevant warnings. These should be silenced for clean test output.
|
test
|
silence test warnings currently several tests are producing irrelevant warnings these should be silenced for clean test output
| 1
|
235,782
| 19,428,750,118
|
IssuesEvent
|
2021-12-21 09:28:48
|
kyma-project/kyma
|
https://api.github.com/repos/kyma-project/kyma
|
closed
|
Test upgrade paths
|
area/ci area/cli test-failing
|
**Description**
The Kyma CI should contain pipelines that verify:
- [x] upgrade from the previous minor release to the current release branch used for patch releases (version 1.24.8 -> release-2.0 branch)
- [x] upgrade from the previous minor release to the main branch (release 2.0.0 -> main branch)
The upgrades should run on:
- [x] k3s
- [x] Gardender cluster
|
1.0
|
Test upgrade paths - **Description**
The Kyma CI should contain pipelines that verify:
- [x] upgrade from the previous minor release to the current release branch used for patch releases (version 1.24.8 -> release-2.0 branch)
- [x] upgrade from the previous minor release to the main branch (release 2.0.0 -> main branch)
The upgrades should run on:
- [x] k3s
- [x] Gardender cluster
|
test
|
test upgrade paths description the kyma ci should contain pipelines that verify upgrade from the previous minor release to the current release branch used for patch releases version release branch upgrade from the previous minor release to the main branch release main branch the upgrades should run on gardender cluster
| 1
|
104,526
| 16,616,856,691
|
IssuesEvent
|
2021-06-02 17:51:18
|
Dima2021/t-vault
|
https://api.github.com/repos/Dima2021/t-vault
|
opened
|
CVE-2018-19827 (High) detected in node-sass-4.14.1.tgz, opennmsopennms-source-26.0.0-1
|
security vulnerability
|
## CVE-2018-19827 - High 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>opennmsopennms-source-26.0.0-1</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: t-vault/tvaultuiv2/package.json</p>
<p>Path to vulnerable library: t-vault/tvaultuiv2/node_modules/node-sass/package.json,t-vault/tvaultui/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- gulp-sass-3.1.0.tgz (Root Library)
- :x: **node-sass-4.14.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/Dima2021/t-vault/commit/259885b704776a5554c5d008b51b19c9b0ea9fd5">259885b704776a5554c5d008b51b19c9b0ea9fd5</a></p>
<p>Found in base branch: <b>dev</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In LibSass 3.5.5, a use-after-free vulnerability exists in the SharedPtr class in SharedPtr.cpp (or SharedPtr.hpp) that may cause a denial of service (application crash) or possibly have unspecified other impact.
<p>Publish Date: 2018-12-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19827>CVE-2018-19827</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>
<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/pull/2784">https://github.com/sass/libsass/pull/2784</a></p>
<p>Release Date: 2019-08-29</p>
<p>Fix Resolution: LibSass - 3.6.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"node-sass","packageVersion":"4.14.1","packageFilePaths":["/tvaultuiv2/package.json","/tvaultui/package.json"],"isTransitiveDependency":true,"dependencyTree":"gulp-sass:3.1.0;node-sass:4.14.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"LibSass - 3.6.0"}],"baseBranches":["dev"],"vulnerabilityIdentifier":"CVE-2018-19827","vulnerabilityDetails":"In LibSass 3.5.5, a use-after-free vulnerability exists in the SharedPtr class in SharedPtr.cpp (or SharedPtr.hpp) that may cause a denial of service (application crash) or possibly have unspecified other impact.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19827","cvss3Severity":"high","cvss3Score":"8.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"Required","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2018-19827 (High) detected in node-sass-4.14.1.tgz, opennmsopennms-source-26.0.0-1 - ## CVE-2018-19827 - High 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>opennmsopennms-source-26.0.0-1</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: t-vault/tvaultuiv2/package.json</p>
<p>Path to vulnerable library: t-vault/tvaultuiv2/node_modules/node-sass/package.json,t-vault/tvaultui/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- gulp-sass-3.1.0.tgz (Root Library)
- :x: **node-sass-4.14.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/Dima2021/t-vault/commit/259885b704776a5554c5d008b51b19c9b0ea9fd5">259885b704776a5554c5d008b51b19c9b0ea9fd5</a></p>
<p>Found in base branch: <b>dev</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In LibSass 3.5.5, a use-after-free vulnerability exists in the SharedPtr class in SharedPtr.cpp (or SharedPtr.hpp) that may cause a denial of service (application crash) or possibly have unspecified other impact.
<p>Publish Date: 2018-12-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19827>CVE-2018-19827</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>
<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/pull/2784">https://github.com/sass/libsass/pull/2784</a></p>
<p>Release Date: 2019-08-29</p>
<p>Fix Resolution: LibSass - 3.6.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"node-sass","packageVersion":"4.14.1","packageFilePaths":["/tvaultuiv2/package.json","/tvaultui/package.json"],"isTransitiveDependency":true,"dependencyTree":"gulp-sass:3.1.0;node-sass:4.14.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"LibSass - 3.6.0"}],"baseBranches":["dev"],"vulnerabilityIdentifier":"CVE-2018-19827","vulnerabilityDetails":"In LibSass 3.5.5, a use-after-free vulnerability exists in the SharedPtr class in SharedPtr.cpp (or SharedPtr.hpp) that may cause a denial of service (application crash) or possibly have unspecified other impact.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19827","cvss3Severity":"high","cvss3Score":"8.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"Required","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->
|
non_test
|
cve high detected in node sass tgz opennmsopennms source cve high severity vulnerability vulnerable libraries node sass tgz opennmsopennms source node sass tgz wrapper around libsass library home page a href path to dependency file t vault package json path to vulnerable library t vault node modules node sass package json t vault tvaultui node modules node sass package json dependency hierarchy gulp sass tgz root library x node sass tgz vulnerable library found in head commit a href found in base branch dev vulnerability details in libsass a use after free vulnerability exists in the sharedptr class in sharedptr cpp or sharedptr hpp that may cause a denial of service application crash or possibly have unspecified other impact 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 suggested fix type upgrade version origin a href release date fix resolution libsass isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree gulp sass node sass isminimumfixversionavailable true minimumfixversion libsass basebranches vulnerabilityidentifier cve vulnerabilitydetails in libsass a use after free vulnerability exists in the sharedptr class in sharedptr cpp or sharedptr hpp that may cause a denial of service application crash or possibly have unspecified other impact vulnerabilityurl
| 0
|
563,071
| 16,675,625,874
|
IssuesEvent
|
2021-06-07 15:50:18
|
qtile/qtile
|
https://api.github.com/repos/qtile/qtile
|
closed
|
Brave "edit bookmark" menu unclickable
|
bug priority
|
When bookmarking a page in the Brave browser, left clicks pass through the "Bookmark added"/"Edit bookmark" menu. So, if there is a link under the menu, trying to click on the menu will end up clicking on the link instead. Middle and right clicks still work as expected.
The layout also seems to matter. This issue occurs in the MonadTall and Floating layouts, but Max seems to work fine.
I'm running QTile v0.15.1, and Brave 1.10.97 on Arch Linux.
|
1.0
|
Brave "edit bookmark" menu unclickable - When bookmarking a page in the Brave browser, left clicks pass through the "Bookmark added"/"Edit bookmark" menu. So, if there is a link under the menu, trying to click on the menu will end up clicking on the link instead. Middle and right clicks still work as expected.
The layout also seems to matter. This issue occurs in the MonadTall and Floating layouts, but Max seems to work fine.
I'm running QTile v0.15.1, and Brave 1.10.97 on Arch Linux.
|
non_test
|
brave edit bookmark menu unclickable when bookmarking a page in the brave browser left clicks pass through the bookmark added edit bookmark menu so if there is a link under the menu trying to click on the menu will end up clicking on the link instead middle and right clicks still work as expected the layout also seems to matter this issue occurs in the monadtall and floating layouts but max seems to work fine i m running qtile and brave on arch linux
| 0
|
526,935
| 15,305,178,687
|
IssuesEvent
|
2021-02-24 17:47:31
|
lowRISC/opentitan
|
https://api.github.com/repos/lowRISC/opentitan
|
opened
|
[dif/spi_device] To get SRAM size from parameter
|
Component:SW Priority:P3 Type:Enhancement
|
as discussed in #5145 and implemented in #5264, SPI_DEVICE HWIP now defines SRAM size in the module parameter. This issue is to follow up the change in the software (DIF). Currently, SRAM size in dif_spi_device is hard-coded. It will be more flexible if dif also use the parameter.
CC: @tjaychen
|
1.0
|
[dif/spi_device] To get SRAM size from parameter - as discussed in #5145 and implemented in #5264, SPI_DEVICE HWIP now defines SRAM size in the module parameter. This issue is to follow up the change in the software (DIF). Currently, SRAM size in dif_spi_device is hard-coded. It will be more flexible if dif also use the parameter.
CC: @tjaychen
|
non_test
|
to get sram size from parameter as discussed in and implemented in spi device hwip now defines sram size in the module parameter this issue is to follow up the change in the software dif currently sram size in dif spi device is hard coded it will be more flexible if dif also use the parameter cc tjaychen
| 0
|
132,394
| 10,745,295,142
|
IssuesEvent
|
2019-10-30 08:43:13
|
EnMasseProject/enmasse
|
https://api.github.com/repos/EnMasseProject/enmasse
|
closed
|
Enable mqtt tests for authentication service tests
|
component/mqtt component/systemtests test development
|
The mqtt client in AuthenticationServiceTest systemtest is disabled due to topic functionality being unstable in systemtests.
|
2.0
|
Enable mqtt tests for authentication service tests - The mqtt client in AuthenticationServiceTest systemtest is disabled due to topic functionality being unstable in systemtests.
|
test
|
enable mqtt tests for authentication service tests the mqtt client in authenticationservicetest systemtest is disabled due to topic functionality being unstable in systemtests
| 1
|
1,919
| 3,427,357,497
|
IssuesEvent
|
2015-12-10 01:05:45
|
dotnet/roslyn
|
https://api.github.com/repos/dotnet/roslyn
|
reopened
|
Contributors should be able to clone, Open Roslyn.sln and build
|
Area-Infrastructure Feature Request
|
This issue is tracking the following story:
> Contributors should be able to clone github.com/dotnet/roslyn, Open Roslyn.sln, build and everything should just work
- [x] Stop failing design-time builds if packages are not restored. Owner: __@Pilchie__ Resolved in #6298.
- [ ] Make sure all projects either directly or indirectly depend on the toolset packages
- [ ] Don't show downstream errors in ErrorList if root projects fail (ie avoid ~100,000 errors in Error List). Owner __@jasonmalinowski__
- [ ] Make sure end-to-end works on clean machine (try Azure VM with preinstall VS)
- [ ] Update wiki
|
1.0
|
Contributors should be able to clone, Open Roslyn.sln and build - This issue is tracking the following story:
> Contributors should be able to clone github.com/dotnet/roslyn, Open Roslyn.sln, build and everything should just work
- [x] Stop failing design-time builds if packages are not restored. Owner: __@Pilchie__ Resolved in #6298.
- [ ] Make sure all projects either directly or indirectly depend on the toolset packages
- [ ] Don't show downstream errors in ErrorList if root projects fail (ie avoid ~100,000 errors in Error List). Owner __@jasonmalinowski__
- [ ] Make sure end-to-end works on clean machine (try Azure VM with preinstall VS)
- [ ] Update wiki
|
non_test
|
contributors should be able to clone open roslyn sln and build this issue is tracking the following story contributors should be able to clone github com dotnet roslyn open roslyn sln build and everything should just work stop failing design time builds if packages are not restored owner pilchie resolved in make sure all projects either directly or indirectly depend on the toolset packages don t show downstream errors in errorlist if root projects fail ie avoid errors in error list owner jasonmalinowski make sure end to end works on clean machine try azure vm with preinstall vs update wiki
| 0
|
171,794
| 6,494,526,585
|
IssuesEvent
|
2017-08-21 22:17:52
|
chartjs/Chart.js
|
https://api.github.com/repos/chartjs/Chart.js
|
closed
|
startAngle on radar chart value out of chart
|
Category: Bug Help wanted Needs Investigation Priority: p2
|
i try to rotate my chart using startAnlge by 90 the value mark is running out the chart. Not sure it is i miss out any option setting to the chart but i did some google unable find any soultion to it.
|
1.0
|
startAngle on radar chart value out of chart - i try to rotate my chart using startAnlge by 90 the value mark is running out the chart. Not sure it is i miss out any option setting to the chart but i did some google unable find any soultion to it.
|
non_test
|
startangle on radar chart value out of chart i try to rotate my chart using startanlge by the value mark is running out the chart not sure it is i miss out any option setting to the chart but i did some google unable find any soultion to it
| 0
|
119,452
| 10,053,933,967
|
IssuesEvent
|
2019-07-21 21:02:47
|
NMGRL/pychron
|
https://api.github.com/repos/NMGRL/pychron
|
closed
|
Spectrum reseting age scale when changing spectrum preferences
|
Bug Data Presentation Enhancement Tested OK Testing Required
|
When I change the Y axis (apparent age) for the spectrum, then change the prefences (specifically adding Y error to K/Ca and 40Ar), the apparent age resets to the default.
|
2.0
|
Spectrum reseting age scale when changing spectrum preferences - When I change the Y axis (apparent age) for the spectrum, then change the prefences (specifically adding Y error to K/Ca and 40Ar), the apparent age resets to the default.
|
test
|
spectrum reseting age scale when changing spectrum preferences when i change the y axis apparent age for the spectrum then change the prefences specifically adding y error to k ca and the apparent age resets to the default
| 1
|
227,350
| 18,058,049,807
|
IssuesEvent
|
2021-09-20 10:47:03
|
kyma-project/kyma
|
https://api.github.com/repos/kyma-project/kyma
|
closed
|
Fast-integration test pipelines fail on deployment of central-application-gateway
|
area/application-connector test-failing
|
<!-- Thank you for your contribution. Before you submit the issue:
1. Search open and closed issues for duplicates.
2. Read the contributing guidelines.
-->
**Description**
The pipeline fails on fast-integration tests with the error:
```
Upgrade test preparation
Error: Waiting for deployment central-application-gateway timeout (90000 ms)
at Timeout._onTimeout (/home/prow/go/src/github.com/kyma-project/kyma/tests/fast-integration/utils/index.js:380:18)
at listOnTimeout (internal/timers.js:557:17)
at processTimers (internal/timers.js:500:7)
1) CommerceMock test fixture should be ready
✓ Helm Broker test fixture should be ready (34567ms)
1 passing (5m)
1 failing
1) Upgrade test preparation
CommerceMock test fixture should be ready:
Error: Waiting for deployment central-application-gateway timeout (90000 ms)
at Timeout._onTimeout (utils/index.js:380:18)
at listOnTimeout (internal/timers.js:557:17)
at processTimers (internal/timers.js:500:7)
```
<!-- Provide a clear and concise description of the problem.
Describe where it appears, when it occurred, and what it affects. -->
<!-- Provide relevant technical details such as the Kubernetes version, the cluster name and provider, the Kyma version, the browser name and version, or the operating system. -->
**Expected result**
<!-- Describe what you expect to happen. -->
Pipeline works
**Actual result**
Pipeline does not work
<!-- Describe what happens instead. -->
**Steps to reproduce**
<!-- List the steps to follow to reproduce the bug. Attach any files, links, code samples, or screenshots that could help in investigating the problem. -->
**Links**
https://status.build.kyma-project.io/view/gs/kyma-prow-logs/logs/kyma-upgrade-gardener-kyma-to-kyma2/1435271788148822016
https://status.build.kyma-project.io/view/gs/kyma-prow-logs/logs/kyma-upgrade-gardener-kyma-to-kyma2/1435271788148822016
https://status.build.kyma-project.io/view/gs/kyma-prow-logs/logs/skr-azure-lite-integration-dev/1435771334989713408
https://status.build.kyma-project.io/view/gs/kyma-prow-logs/logs/skr-trial-integration-dev/1435665637434200064
|
1.0
|
Fast-integration test pipelines fail on deployment of central-application-gateway - <!-- Thank you for your contribution. Before you submit the issue:
1. Search open and closed issues for duplicates.
2. Read the contributing guidelines.
-->
**Description**
The pipeline fails on fast-integration tests with the error:
```
Upgrade test preparation
Error: Waiting for deployment central-application-gateway timeout (90000 ms)
at Timeout._onTimeout (/home/prow/go/src/github.com/kyma-project/kyma/tests/fast-integration/utils/index.js:380:18)
at listOnTimeout (internal/timers.js:557:17)
at processTimers (internal/timers.js:500:7)
1) CommerceMock test fixture should be ready
✓ Helm Broker test fixture should be ready (34567ms)
1 passing (5m)
1 failing
1) Upgrade test preparation
CommerceMock test fixture should be ready:
Error: Waiting for deployment central-application-gateway timeout (90000 ms)
at Timeout._onTimeout (utils/index.js:380:18)
at listOnTimeout (internal/timers.js:557:17)
at processTimers (internal/timers.js:500:7)
```
<!-- Provide a clear and concise description of the problem.
Describe where it appears, when it occurred, and what it affects. -->
<!-- Provide relevant technical details such as the Kubernetes version, the cluster name and provider, the Kyma version, the browser name and version, or the operating system. -->
**Expected result**
<!-- Describe what you expect to happen. -->
Pipeline works
**Actual result**
Pipeline does not work
<!-- Describe what happens instead. -->
**Steps to reproduce**
<!-- List the steps to follow to reproduce the bug. Attach any files, links, code samples, or screenshots that could help in investigating the problem. -->
**Links**
https://status.build.kyma-project.io/view/gs/kyma-prow-logs/logs/kyma-upgrade-gardener-kyma-to-kyma2/1435271788148822016
https://status.build.kyma-project.io/view/gs/kyma-prow-logs/logs/kyma-upgrade-gardener-kyma-to-kyma2/1435271788148822016
https://status.build.kyma-project.io/view/gs/kyma-prow-logs/logs/skr-azure-lite-integration-dev/1435771334989713408
https://status.build.kyma-project.io/view/gs/kyma-prow-logs/logs/skr-trial-integration-dev/1435665637434200064
|
test
|
fast integration test pipelines fail on deployment of central application gateway thank you for your contribution before you submit the issue search open and closed issues for duplicates read the contributing guidelines description the pipeline fails on fast integration tests with the error upgrade test preparation error waiting for deployment central application gateway timeout ms at timeout ontimeout home prow go src github com kyma project kyma tests fast integration utils index js at listontimeout internal timers js at processtimers internal timers js commercemock test fixture should be ready ✓ helm broker test fixture should be ready passing failing upgrade test preparation commercemock test fixture should be ready error waiting for deployment central application gateway timeout ms at timeout ontimeout utils index js at listontimeout internal timers js at processtimers internal timers js provide a clear and concise description of the problem describe where it appears when it occurred and what it affects expected result pipeline works actual result pipeline does not work steps to reproduce links
| 1
|
153,624
| 12,154,491,745
|
IssuesEvent
|
2020-04-25 08:35:19
|
elastic/kibana
|
https://api.github.com/repos/elastic/kibana
|
opened
|
Failing test: Jest Integration Tests.packages/kbn-es/src/integration_tests - #installSnapshot() awaits installSnapshot() promise and returns { installPath }
|
failed-test
|
A test failed on a tracked branch
```
Error: Caught error after test environment was torn down
Http server is not setup up yet
at HttpServer.start (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/src/core/server/http/http_server.ts:117:13)
at HttpService.start (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/src/core/server/http/http_service.ts:110:29)
```
First failure: [Jenkins Build](https://kibana-ci.elastic.co/job/elastic+kibana+7.x/4640/)
<!-- kibanaCiData = {"failed-test":{"test.class":"Jest Integration Tests.packages/kbn-es/src/integration_tests","test.name":"#installSnapshot() awaits installSnapshot() promise and returns { installPath }","test.failCount":1}} -->
|
1.0
|
Failing test: Jest Integration Tests.packages/kbn-es/src/integration_tests - #installSnapshot() awaits installSnapshot() promise and returns { installPath } - A test failed on a tracked branch
```
Error: Caught error after test environment was torn down
Http server is not setup up yet
at HttpServer.start (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/src/core/server/http/http_server.ts:117:13)
at HttpService.start (/var/lib/jenkins/workspace/elastic+kibana+7.x/kibana/src/core/server/http/http_service.ts:110:29)
```
First failure: [Jenkins Build](https://kibana-ci.elastic.co/job/elastic+kibana+7.x/4640/)
<!-- kibanaCiData = {"failed-test":{"test.class":"Jest Integration Tests.packages/kbn-es/src/integration_tests","test.name":"#installSnapshot() awaits installSnapshot() promise and returns { installPath }","test.failCount":1}} -->
|
test
|
failing test jest integration tests packages kbn es src integration tests installsnapshot awaits installsnapshot promise and returns installpath a test failed on a tracked branch error caught error after test environment was torn down http server is not setup up yet at httpserver start var lib jenkins workspace elastic kibana x kibana src core server http http server ts at httpservice start var lib jenkins workspace elastic kibana x kibana src core server http http service ts first failure
| 1
|
136,610
| 5,286,340,308
|
IssuesEvent
|
2017-02-08 09:01:54
|
metasfresh/metasfresh-webui-frontend
|
https://api.github.com/repos/metasfresh/metasfresh-webui-frontend
|
closed
|
Implement document field device support
|
High priority
|
Take following example of an element layout definition:
```
{
"caption": "WeightGross",
"description": "",
"widgetType": "Number",
"fields": [
{
"field": "WeightGross",
"emptyText": "none",
"devices": [
{
"deviceId": "mettler-MOCKED-WeightGross-GetGrossWeighRequest",
"caption": "m",
"websocketEndpoint": "/devices/mettler-MOCKED-WeightGross-GetGrossWeighRequest"
}
]
}
]
}
```
Remark the "devices" entry. There can be an array of "device" definitions.
For each each "device" we shall render a small button on the right side of our widget.
The frontend shall subscribe to given "websocketEndpoint" to fetch the device current value. Details about this will come later.
When the user presses on the button, the correct PATCH method shall be called in order to set the device's value to corresponding field (in the example above the field is WeightGross").
About device's websocket endpoint: when somebody is subscribing to a device endpoint, that endpoint will continuously serve the current device value, using following format, e.g.
```
{
"deviceId":"mettler-MOCKED-WeightGross-GetGrossWeighRequest",
"value":"463.00",
"timestampMillis":1485542915186
}
```
|
1.0
|
Implement document field device support - Take following example of an element layout definition:
```
{
"caption": "WeightGross",
"description": "",
"widgetType": "Number",
"fields": [
{
"field": "WeightGross",
"emptyText": "none",
"devices": [
{
"deviceId": "mettler-MOCKED-WeightGross-GetGrossWeighRequest",
"caption": "m",
"websocketEndpoint": "/devices/mettler-MOCKED-WeightGross-GetGrossWeighRequest"
}
]
}
]
}
```
Remark the "devices" entry. There can be an array of "device" definitions.
For each each "device" we shall render a small button on the right side of our widget.
The frontend shall subscribe to given "websocketEndpoint" to fetch the device current value. Details about this will come later.
When the user presses on the button, the correct PATCH method shall be called in order to set the device's value to corresponding field (in the example above the field is WeightGross").
About device's websocket endpoint: when somebody is subscribing to a device endpoint, that endpoint will continuously serve the current device value, using following format, e.g.
```
{
"deviceId":"mettler-MOCKED-WeightGross-GetGrossWeighRequest",
"value":"463.00",
"timestampMillis":1485542915186
}
```
|
non_test
|
implement document field device support take following example of an element layout definition caption weightgross description widgettype number fields field weightgross emptytext none devices deviceid mettler mocked weightgross getgrossweighrequest caption m websocketendpoint devices mettler mocked weightgross getgrossweighrequest remark the devices entry there can be an array of device definitions for each each device we shall render a small button on the right side of our widget the frontend shall subscribe to given websocketendpoint to fetch the device current value details about this will come later when the user presses on the button the correct patch method shall be called in order to set the device s value to corresponding field in the example above the field is weightgross about device s websocket endpoint when somebody is subscribing to a device endpoint that endpoint will continuously serve the current device value using following format e g deviceid mettler mocked weightgross getgrossweighrequest value timestampmillis
| 0
|
276,357
| 23,988,100,159
|
IssuesEvent
|
2022-09-13 21:07:08
|
osmosis-labs/osmosis
|
https://api.github.com/repos/osmosis-labs/osmosis
|
closed
|
test(twap): getSpotPrices function
|
T:tests C:x/twap
|
<!-- < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < ☺
v ✰ Thanks for creating an issue! ✰
☺ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -->
## Background
`getSpotPrices` function is missing unit tests. We should add them
## Acceptance Criteria
- tests added
- coverage is maximized
- utilize `AmmInterface` mock if applicable
|
1.0
|
test(twap): getSpotPrices function - <!-- < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < ☺
v ✰ Thanks for creating an issue! ✰
☺ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -->
## Background
`getSpotPrices` function is missing unit tests. We should add them
## Acceptance Criteria
- tests added
- coverage is maximized
- utilize `AmmInterface` mock if applicable
|
test
|
test twap getspotprices function ☺ v ✰ thanks for creating an issue ✰ ☺ background getspotprices function is missing unit tests we should add them acceptance criteria tests added coverage is maximized utilize amminterface mock if applicable
| 1
|
292,230
| 25,206,500,692
|
IssuesEvent
|
2022-11-13 18:50:22
|
MinhazMurks/Bannerlord.Tweaks
|
https://api.github.com/repos/MinhazMurks/Bannerlord.Tweaks
|
opened
|
Test All Two-Handed Weapons Cut Through
|
testing
|
Test to see if tweak: "All Two-Handed Weapons Cut Through" works
|
1.0
|
Test All Two-Handed Weapons Cut Through - Test to see if tweak: "All Two-Handed Weapons Cut Through" works
|
test
|
test all two handed weapons cut through test to see if tweak all two handed weapons cut through works
| 1
|
62,035
| 14,656,421,194
|
IssuesEvent
|
2020-12-28 13:23:18
|
fu1771695yongxie/vue
|
https://api.github.com/repos/fu1771695yongxie/vue
|
opened
|
CVE-2019-10775 (High) detected in ecstatic-3.3.2.tgz
|
security vulnerability
|
## CVE-2019-10775 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ecstatic-3.3.2.tgz</b></p></summary>
<p>A simple static file server middleware</p>
<p>Library home page: <a href="https://registry.npmjs.org/ecstatic/-/ecstatic-3.3.2.tgz">https://registry.npmjs.org/ecstatic/-/ecstatic-3.3.2.tgz</a></p>
<p>Path to dependency file: vue/package.json</p>
<p>Path to vulnerable library: vue/node_modules/ecstatic/package.json</p>
<p>
Dependency Hierarchy:
- http-server-0.12.3.tgz (Root Library)
- :x: **ecstatic-3.3.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/fu1771695yongxie/vue/commit/9bdc4db8eccb6aa48ad481758b90f55a71fbef9b">9bdc4db8eccb6aa48ad481758b90f55a71fbef9b</a></p>
<p>Found in base branch: <b>dev</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>
ecstatic have a denial of service vulnerability. Successful exploitation could lead to crash of an application.
<p>Publish Date: 2020-01-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10775>CVE-2019-10775</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/jfhbrook/node-ecstatic/tree/4.1.3">https://github.com/jfhbrook/node-ecstatic/tree/4.1.3</a></p>
<p>Release Date: 2020-01-02</p>
<p>Fix Resolution: 4.1.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2019-10775 (High) detected in ecstatic-3.3.2.tgz - ## CVE-2019-10775 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ecstatic-3.3.2.tgz</b></p></summary>
<p>A simple static file server middleware</p>
<p>Library home page: <a href="https://registry.npmjs.org/ecstatic/-/ecstatic-3.3.2.tgz">https://registry.npmjs.org/ecstatic/-/ecstatic-3.3.2.tgz</a></p>
<p>Path to dependency file: vue/package.json</p>
<p>Path to vulnerable library: vue/node_modules/ecstatic/package.json</p>
<p>
Dependency Hierarchy:
- http-server-0.12.3.tgz (Root Library)
- :x: **ecstatic-3.3.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/fu1771695yongxie/vue/commit/9bdc4db8eccb6aa48ad481758b90f55a71fbef9b">9bdc4db8eccb6aa48ad481758b90f55a71fbef9b</a></p>
<p>Found in base branch: <b>dev</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>
ecstatic have a denial of service vulnerability. Successful exploitation could lead to crash of an application.
<p>Publish Date: 2020-01-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10775>CVE-2019-10775</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/jfhbrook/node-ecstatic/tree/4.1.3">https://github.com/jfhbrook/node-ecstatic/tree/4.1.3</a></p>
<p>Release Date: 2020-01-02</p>
<p>Fix Resolution: 4.1.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
non_test
|
cve high detected in ecstatic tgz cve high severity vulnerability vulnerable library ecstatic tgz a simple static file server middleware library home page a href path to dependency file vue package json path to vulnerable library vue node modules ecstatic package json dependency hierarchy http server tgz root library x ecstatic tgz vulnerable library found in head commit a href found in base branch dev vulnerability details ecstatic have a denial of service vulnerability successful exploitation could lead to crash of an application publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
| 0
|
14,298
| 17,193,420,635
|
IssuesEvent
|
2021-07-16 14:08:04
|
thedarkcolour/Future-MC
|
https://api.github.com/repos/thedarkcolour/Future-MC
|
closed
|
[1.12.2] OTG Biome Bundle O Plenty compatible?
|
compatibility enhancement
|
I've been testing for a few hours if FMC works with OTG/Open Terrain Generator. I have this test going on:
Seed: -4562547876164380000
```
S:"Bee Nest Biome Spawns" <
biomesoplenty:eucalyptus_forest:100.00
```
I've noticed the mod works well in Biomes O Plenty, but not yet in OTG.
I would like to know if there are some limits where bees can spawn (like that forest). And if it's possible to just select all biomes in one easy way (like saying: *:*:50.00) or (*:*forest*:50.00). That way, it's a bit easier to configure that bees need to spawn more to get a decent chance to find the cute fella's.
Looking forward to your reply :)
|
True
|
[1.12.2] OTG Biome Bundle O Plenty compatible? - I've been testing for a few hours if FMC works with OTG/Open Terrain Generator. I have this test going on:
Seed: -4562547876164380000
```
S:"Bee Nest Biome Spawns" <
biomesoplenty:eucalyptus_forest:100.00
```
I've noticed the mod works well in Biomes O Plenty, but not yet in OTG.
I would like to know if there are some limits where bees can spawn (like that forest). And if it's possible to just select all biomes in one easy way (like saying: *:*:50.00) or (*:*forest*:50.00). That way, it's a bit easier to configure that bees need to spawn more to get a decent chance to find the cute fella's.
Looking forward to your reply :)
|
non_test
|
otg biome bundle o plenty compatible i ve been testing for a few hours if fmc works with otg open terrain generator i have this test going on seed s bee nest biome spawns biomesoplenty eucalyptus forest i ve noticed the mod works well in biomes o plenty but not yet in otg i would like to know if there are some limits where bees can spawn like that forest and if it s possible to just select all biomes in one easy way like saying or forest that way it s a bit easier to configure that bees need to spawn more to get a decent chance to find the cute fella s looking forward to your reply
| 0
|
144,246
| 11,599,246,911
|
IssuesEvent
|
2020-02-25 01:36:22
|
brave/brave-browser
|
https://api.github.com/repos/brave/brave-browser
|
closed
|
Manual test run on OS X for 1.4.x - Release
|
OS/macOS QA/Yes release-notes/exclude tests
|
## Per release specialty tests
### Installer
- [x] Check signature: If OS Run `spctl --assess --verbose /Applications/Brave-Browser-Beta.app/` and make sure it returns `accepted`. If Windows right click on the `brave_installer-x64.exe` and go to Properties, go to the Digital Signatures tab and double click on the signature. Make sure it says "The digital signature is OK" in the popup window
### Data(Upgrade from previous release)
- [ ] Make sure that data from the last version appears in the new version OK
- [ ] With data from the last version, verify that
- [ ] bookmarks on the bookmark toolbar and bookmark folders can be opened
- [ ] cookies are preserved
- [ ] installed extensions are retained and work correctly
- [ ] opened tabs can be reloaded
- [ ] stored passwords are preserved
- [ ] unpinned tabs can be pinned
## Extensions/Plugins tests
- [x] Verify one item from Brave Update server is installable (Example: Ad-block DAT file on fresh extension)
- [x] Verify one item from Google Update server is installable (Example: Extensions from CWS)
- [x] Verify PDFJS, Torrent viewer extensions are installed automatically on fresh profile and cannot be disabled
- [x] Verify magnet links and .torrent files loads Torrent viewer page and able to download torrent
### CWS
- [x] Verify installing ABP from CWS shows warning message `NOT A RECOMMENDED BRAVE EXTENSION!` but still allows to install the extension
- [x] Verify installing LastPass from CWS doesn't show any warning message
### PDF
- [x] Test that PDF is loaded over HTTPS at https://basicattentiontoken.org/BasicAttentionTokenWhitePaper-4.pdf
- [x] Test that PDF is loaded over HTTP at http://www.pdf995.com/samples/pdf.pdf
### Widevine
- [x] Verify `Widevine Notification` is shown when you visit Netflix for the first time
- [x] Test that you can stream on Netflix on a fresh profile after installing Widevine
### Bravery settings
- [x] Verify that HTTPS Everywhere works by loading http://https-everywhere.badssl.com/
- [x] Turning HTTPS Everywhere off and shields off both disable the redirect to https://https-everywhere.badssl.com/
- [x] Verify that toggling `Ads and trackers blocked` works as expected
- [x] Visit https://testsafebrowsing.appspot.com/s/phishing.html, verify that Safe Browsing (via our Proxy) works for all the listed items
- [x] Visit https://brianbondy.com/ and then turn on script blocking, page should not load. Allow it from the script blocking UI in the URL bar and it should load the page correctly
- [x] Test that 3rd party storage results are blank at https://jsfiddle.net/7ke9r14a/9/ when 3rd party cookies are blocked and not blank when 3rd party cookies are unblocked
### Fingerprint Tests
- [x] Visit https://jsfiddle.net/bkf50r8v/13/, ensure 3 blocked items are listed in shields. Result window should show `got canvas fingerprint 0` and `got webgl fingerprint 00`
- [x] Test that audio fingerprint is blocked at https://audiofingerprint.openwpm.com/ only when `Block all fingerprinting protection` is on
- [x] Test that Brave browser isn't detected on https://extensions.inrialpes.fr/brave/
- [x] Test that https://diafygi.github.io/webrtc-ips/ doesn't leak IP address when `Block all fingerprinting protection` is on
### Rewards
- [x] Verify wallet is auto created after enabling rewards
- [ ] Verify account balance shows correct BAT and USD value
- [ ] Verify you are able to restore a wallet
- [x] Verify wallet address matches the QR code that is generated under `Add funds`
- [ ] Verify actions taken (claiming grant, tipping, auto-contribute) display in wallet panel
- [ ] Verify adding funds via any of the currencies flows into wallet after specified amount of time
- [ ] Verify adding funds to an existing wallet with amount, adjusts the BAT value appropriately
- [ ] Verify monthly budget shows correct BAT and USD value
- [ ] Verify you are able to exclude a publisher from the auto-contribute table by clicking on the `x` in auto-contribute table and popup list of sites
- [ ] Verify you are able to exclude a publisher by using the toggle on the Rewards Panel
- [ ] Verify when you click on the BR panel while on a site, the panel displays site specific information (site favicon, domain, attention %)
- [ ] Verify when you click on `Send a tip`, the custom tip banner displays
- [ ] Verify you are able to make one-time tip and they display in tips panel
- [ ] Verify you are able to make recurring tip and they display in tips panel
- [ ] Verify you can tip a verified publisher
- [ ] Verify you can tip a verified YouTube creator
- [ ] Verify tip panel shows a verified checkmark for a verified publisher/verified YouTube creator
- [ ] Verify tip panel shows a message about unverified publisher
- [ ] Verify BR panel shows message about an unverified publisher
- [ ] Verify you are able to perform a contribution
- [ ] Verify if you disable auto-contribute you are still able to tip regular sites and YouTube creators
- [ ] Verify that disabling Rewards and enabling it again does not lose state
- [ ] Verify that disabling auto-contribute and enabling it again does not lose state
- [ ] Adjust min visit/time in settings. Visit some sites and YouTube channels to verify they are added to the table after the specified settings
- [ ] Upgrade from older version
- [ ] Verify the wallet balance is retained and wallet backup code isn't corrupted
- [ ] Verify auto-contribute list is not lost after upgrade
- [ ] Verify tips list is not lost after upgrade
- [ ] Verify wallet panel transactions list is not lost after upgrade
### Ads Upgrade Tests:
- [x] Install 0.62.51 and enable Rewards (Ads are not available on this version). Update on `test` channel to the hotfix version. Verify Ads are off by default, should get a BAT logo notification to alert you that Ads are available.
- [x] Install 0.64.77 and enable Rewards. Ads are on by default. View an Ad. Update on `test` channel to the hotfix version. Verify Ads are still on after update, Ads panel information was not lost after upgrade, no BAT logo notification.
- [x] Install 0.64.77 and enable Rewards. Disable Ads. Update on `test` channel to the hotfix version. Verify Ads are still off after update, no BAT logo notification.
- [x] Install 1.3.118 and enable Rewards. Ads are on by default. View an ad. Update on `test` channel to the hotfix version. Verify Ads are still on after update, Ads panel information was not lost after upgrade, no BAT logo notification.
- [x] install 1.3.118 and enable Rewards. Disable Ads. Update on `test` channel to the hotfix version. Verify Ads are still off after update, no BAT logo notification.
### Tor Tabs
- [x] Visit https://check.torproject.org in a Tor window, ensure its shows success message for using a Tor exit node
- [x] Visit https://check.torproject.org in a Tor window, note down exit node IP address. Do a hard refresh (Ctrl+Shift+R/Cmd+Shift+R), ensure exit IP changes after page reloads
- [x] Visit https://protonirockerxow.onion/ in a Tor window, ensure login page is shown
- [x] Visit https://browserleaks.com/geo in a Tor window, ensure location isn't shown
### Session storage
- [x] Temporarily move away your browser profile and test that a new profile is created when browser is launched
- macOS - `~/Library/Application\ Support/BraveSoftware/`
- Windows - `%userprofile%\appdata\Local\BraveSoftware\`
- Linux(Ubuntu) - `~/.config/BraveSoftware/`
- [x] Test that windows and tabs restore when closed, including active tab
- [x] Ensure that the tabs in the above session are being lazy loaded when the session is restored
## Update tests
- [x] Verify visiting `brave://settings/help` triggers update check
- [x] Verify once update is downloaded, prompts to `Relaunch` to install update
## Chromium upgrade tests
- [x] Verify `brave://gpu` on Brave and `chrome://gpu` on Chrome are similar for the same Chromium version on both browsers
#### Adblock
- [x] Verify referrer blocking works properly for TLD+1. Visit `https://technology.slashdot.org/` and verify adblock works properly similar to `https://slashdot.org/`
#### Components
- [x] Delete Adblock folder from browser profile and restart browser. Visit `brave://components` and verify `Brave Ad Block Updater` downloads and update the component. Repeat for all Brave components
## Crypto Wallets
- [x] ensure that you can create a new wallet without any issues
- [x] ensure that you can restore a previous CW wallet without any issues
- [x] ensure that you can restore a previous MM wallet without any issues
- [x] ensure that you can create a transaction (sending crypto) with a CW wallet
- [x] ensure that you can create a transaction (sending crypto) using a restored MM wallet
|
1.0
|
Manual test run on OS X for 1.4.x - Release - ## Per release specialty tests
### Installer
- [x] Check signature: If OS Run `spctl --assess --verbose /Applications/Brave-Browser-Beta.app/` and make sure it returns `accepted`. If Windows right click on the `brave_installer-x64.exe` and go to Properties, go to the Digital Signatures tab and double click on the signature. Make sure it says "The digital signature is OK" in the popup window
### Data(Upgrade from previous release)
- [ ] Make sure that data from the last version appears in the new version OK
- [ ] With data from the last version, verify that
- [ ] bookmarks on the bookmark toolbar and bookmark folders can be opened
- [ ] cookies are preserved
- [ ] installed extensions are retained and work correctly
- [ ] opened tabs can be reloaded
- [ ] stored passwords are preserved
- [ ] unpinned tabs can be pinned
## Extensions/Plugins tests
- [x] Verify one item from Brave Update server is installable (Example: Ad-block DAT file on fresh extension)
- [x] Verify one item from Google Update server is installable (Example: Extensions from CWS)
- [x] Verify PDFJS, Torrent viewer extensions are installed automatically on fresh profile and cannot be disabled
- [x] Verify magnet links and .torrent files loads Torrent viewer page and able to download torrent
### CWS
- [x] Verify installing ABP from CWS shows warning message `NOT A RECOMMENDED BRAVE EXTENSION!` but still allows to install the extension
- [x] Verify installing LastPass from CWS doesn't show any warning message
### PDF
- [x] Test that PDF is loaded over HTTPS at https://basicattentiontoken.org/BasicAttentionTokenWhitePaper-4.pdf
- [x] Test that PDF is loaded over HTTP at http://www.pdf995.com/samples/pdf.pdf
### Widevine
- [x] Verify `Widevine Notification` is shown when you visit Netflix for the first time
- [x] Test that you can stream on Netflix on a fresh profile after installing Widevine
### Bravery settings
- [x] Verify that HTTPS Everywhere works by loading http://https-everywhere.badssl.com/
- [x] Turning HTTPS Everywhere off and shields off both disable the redirect to https://https-everywhere.badssl.com/
- [x] Verify that toggling `Ads and trackers blocked` works as expected
- [x] Visit https://testsafebrowsing.appspot.com/s/phishing.html, verify that Safe Browsing (via our Proxy) works for all the listed items
- [x] Visit https://brianbondy.com/ and then turn on script blocking, page should not load. Allow it from the script blocking UI in the URL bar and it should load the page correctly
- [x] Test that 3rd party storage results are blank at https://jsfiddle.net/7ke9r14a/9/ when 3rd party cookies are blocked and not blank when 3rd party cookies are unblocked
### Fingerprint Tests
- [x] Visit https://jsfiddle.net/bkf50r8v/13/, ensure 3 blocked items are listed in shields. Result window should show `got canvas fingerprint 0` and `got webgl fingerprint 00`
- [x] Test that audio fingerprint is blocked at https://audiofingerprint.openwpm.com/ only when `Block all fingerprinting protection` is on
- [x] Test that Brave browser isn't detected on https://extensions.inrialpes.fr/brave/
- [x] Test that https://diafygi.github.io/webrtc-ips/ doesn't leak IP address when `Block all fingerprinting protection` is on
### Rewards
- [x] Verify wallet is auto created after enabling rewards
- [ ] Verify account balance shows correct BAT and USD value
- [ ] Verify you are able to restore a wallet
- [x] Verify wallet address matches the QR code that is generated under `Add funds`
- [ ] Verify actions taken (claiming grant, tipping, auto-contribute) display in wallet panel
- [ ] Verify adding funds via any of the currencies flows into wallet after specified amount of time
- [ ] Verify adding funds to an existing wallet with amount, adjusts the BAT value appropriately
- [ ] Verify monthly budget shows correct BAT and USD value
- [ ] Verify you are able to exclude a publisher from the auto-contribute table by clicking on the `x` in auto-contribute table and popup list of sites
- [ ] Verify you are able to exclude a publisher by using the toggle on the Rewards Panel
- [ ] Verify when you click on the BR panel while on a site, the panel displays site specific information (site favicon, domain, attention %)
- [ ] Verify when you click on `Send a tip`, the custom tip banner displays
- [ ] Verify you are able to make one-time tip and they display in tips panel
- [ ] Verify you are able to make recurring tip and they display in tips panel
- [ ] Verify you can tip a verified publisher
- [ ] Verify you can tip a verified YouTube creator
- [ ] Verify tip panel shows a verified checkmark for a verified publisher/verified YouTube creator
- [ ] Verify tip panel shows a message about unverified publisher
- [ ] Verify BR panel shows message about an unverified publisher
- [ ] Verify you are able to perform a contribution
- [ ] Verify if you disable auto-contribute you are still able to tip regular sites and YouTube creators
- [ ] Verify that disabling Rewards and enabling it again does not lose state
- [ ] Verify that disabling auto-contribute and enabling it again does not lose state
- [ ] Adjust min visit/time in settings. Visit some sites and YouTube channels to verify they are added to the table after the specified settings
- [ ] Upgrade from older version
- [ ] Verify the wallet balance is retained and wallet backup code isn't corrupted
- [ ] Verify auto-contribute list is not lost after upgrade
- [ ] Verify tips list is not lost after upgrade
- [ ] Verify wallet panel transactions list is not lost after upgrade
### Ads Upgrade Tests:
- [x] Install 0.62.51 and enable Rewards (Ads are not available on this version). Update on `test` channel to the hotfix version. Verify Ads are off by default, should get a BAT logo notification to alert you that Ads are available.
- [x] Install 0.64.77 and enable Rewards. Ads are on by default. View an Ad. Update on `test` channel to the hotfix version. Verify Ads are still on after update, Ads panel information was not lost after upgrade, no BAT logo notification.
- [x] Install 0.64.77 and enable Rewards. Disable Ads. Update on `test` channel to the hotfix version. Verify Ads are still off after update, no BAT logo notification.
- [x] Install 1.3.118 and enable Rewards. Ads are on by default. View an ad. Update on `test` channel to the hotfix version. Verify Ads are still on after update, Ads panel information was not lost after upgrade, no BAT logo notification.
- [x] install 1.3.118 and enable Rewards. Disable Ads. Update on `test` channel to the hotfix version. Verify Ads are still off after update, no BAT logo notification.
### Tor Tabs
- [x] Visit https://check.torproject.org in a Tor window, ensure its shows success message for using a Tor exit node
- [x] Visit https://check.torproject.org in a Tor window, note down exit node IP address. Do a hard refresh (Ctrl+Shift+R/Cmd+Shift+R), ensure exit IP changes after page reloads
- [x] Visit https://protonirockerxow.onion/ in a Tor window, ensure login page is shown
- [x] Visit https://browserleaks.com/geo in a Tor window, ensure location isn't shown
### Session storage
- [x] Temporarily move away your browser profile and test that a new profile is created when browser is launched
- macOS - `~/Library/Application\ Support/BraveSoftware/`
- Windows - `%userprofile%\appdata\Local\BraveSoftware\`
- Linux(Ubuntu) - `~/.config/BraveSoftware/`
- [x] Test that windows and tabs restore when closed, including active tab
- [x] Ensure that the tabs in the above session are being lazy loaded when the session is restored
## Update tests
- [x] Verify visiting `brave://settings/help` triggers update check
- [x] Verify once update is downloaded, prompts to `Relaunch` to install update
## Chromium upgrade tests
- [x] Verify `brave://gpu` on Brave and `chrome://gpu` on Chrome are similar for the same Chromium version on both browsers
#### Adblock
- [x] Verify referrer blocking works properly for TLD+1. Visit `https://technology.slashdot.org/` and verify adblock works properly similar to `https://slashdot.org/`
#### Components
- [x] Delete Adblock folder from browser profile and restart browser. Visit `brave://components` and verify `Brave Ad Block Updater` downloads and update the component. Repeat for all Brave components
## Crypto Wallets
- [x] ensure that you can create a new wallet without any issues
- [x] ensure that you can restore a previous CW wallet without any issues
- [x] ensure that you can restore a previous MM wallet without any issues
- [x] ensure that you can create a transaction (sending crypto) with a CW wallet
- [x] ensure that you can create a transaction (sending crypto) using a restored MM wallet
|
test
|
manual test run on os x for x release per release specialty tests installer check signature if os run spctl assess verbose applications brave browser beta app and make sure it returns accepted if windows right click on the brave installer exe and go to properties go to the digital signatures tab and double click on the signature make sure it says the digital signature is ok in the popup window data upgrade from previous release make sure that data from the last version appears in the new version ok with data from the last version verify that bookmarks on the bookmark toolbar and bookmark folders can be opened cookies are preserved installed extensions are retained and work correctly opened tabs can be reloaded stored passwords are preserved unpinned tabs can be pinned extensions plugins tests verify one item from brave update server is installable example ad block dat file on fresh extension verify one item from google update server is installable example extensions from cws verify pdfjs torrent viewer extensions are installed automatically on fresh profile and cannot be disabled verify magnet links and torrent files loads torrent viewer page and able to download torrent cws verify installing abp from cws shows warning message not a recommended brave extension but still allows to install the extension verify installing lastpass from cws doesn t show any warning message pdf test that pdf is loaded over https at test that pdf is loaded over http at widevine verify widevine notification is shown when you visit netflix for the first time test that you can stream on netflix on a fresh profile after installing widevine bravery settings verify that https everywhere works by loading turning https everywhere off and shields off both disable the redirect to verify that toggling ads and trackers blocked works as expected visit verify that safe browsing via our proxy works for all the listed items visit and then turn on script blocking page should not load allow it from the script blocking ui in the url bar and it should load the page correctly test that party storage results are blank at when party cookies are blocked and not blank when party cookies are unblocked fingerprint tests visit ensure blocked items are listed in shields result window should show got canvas fingerprint and got webgl fingerprint test that audio fingerprint is blocked at only when block all fingerprinting protection is on test that brave browser isn t detected on test that doesn t leak ip address when block all fingerprinting protection is on rewards verify wallet is auto created after enabling rewards verify account balance shows correct bat and usd value verify you are able to restore a wallet verify wallet address matches the qr code that is generated under add funds verify actions taken claiming grant tipping auto contribute display in wallet panel verify adding funds via any of the currencies flows into wallet after specified amount of time verify adding funds to an existing wallet with amount adjusts the bat value appropriately verify monthly budget shows correct bat and usd value verify you are able to exclude a publisher from the auto contribute table by clicking on the x in auto contribute table and popup list of sites verify you are able to exclude a publisher by using the toggle on the rewards panel verify when you click on the br panel while on a site the panel displays site specific information site favicon domain attention verify when you click on send a tip the custom tip banner displays verify you are able to make one time tip and they display in tips panel verify you are able to make recurring tip and they display in tips panel verify you can tip a verified publisher verify you can tip a verified youtube creator verify tip panel shows a verified checkmark for a verified publisher verified youtube creator verify tip panel shows a message about unverified publisher verify br panel shows message about an unverified publisher verify you are able to perform a contribution verify if you disable auto contribute you are still able to tip regular sites and youtube creators verify that disabling rewards and enabling it again does not lose state verify that disabling auto contribute and enabling it again does not lose state adjust min visit time in settings visit some sites and youtube channels to verify they are added to the table after the specified settings upgrade from older version verify the wallet balance is retained and wallet backup code isn t corrupted verify auto contribute list is not lost after upgrade verify tips list is not lost after upgrade verify wallet panel transactions list is not lost after upgrade ads upgrade tests install and enable rewards ads are not available on this version update on test channel to the hotfix version verify ads are off by default should get a bat logo notification to alert you that ads are available install and enable rewards ads are on by default view an ad update on test channel to the hotfix version verify ads are still on after update ads panel information was not lost after upgrade no bat logo notification install and enable rewards disable ads update on test channel to the hotfix version verify ads are still off after update no bat logo notification install and enable rewards ads are on by default view an ad update on test channel to the hotfix version verify ads are still on after update ads panel information was not lost after upgrade no bat logo notification install and enable rewards disable ads update on test channel to the hotfix version verify ads are still off after update no bat logo notification tor tabs visit in a tor window ensure its shows success message for using a tor exit node visit in a tor window note down exit node ip address do a hard refresh ctrl shift r cmd shift r ensure exit ip changes after page reloads visit in a tor window ensure login page is shown visit in a tor window ensure location isn t shown session storage temporarily move away your browser profile and test that a new profile is created when browser is launched macos library application support bravesoftware windows userprofile appdata local bravesoftware linux ubuntu config bravesoftware test that windows and tabs restore when closed including active tab ensure that the tabs in the above session are being lazy loaded when the session is restored update tests verify visiting brave settings help triggers update check verify once update is downloaded prompts to relaunch to install update chromium upgrade tests verify brave gpu on brave and chrome gpu on chrome are similar for the same chromium version on both browsers adblock verify referrer blocking works properly for tld visit and verify adblock works properly similar to components delete adblock folder from browser profile and restart browser visit brave components and verify brave ad block updater downloads and update the component repeat for all brave components crypto wallets ensure that you can create a new wallet without any issues ensure that you can restore a previous cw wallet without any issues ensure that you can restore a previous mm wallet without any issues ensure that you can create a transaction sending crypto with a cw wallet ensure that you can create a transaction sending crypto using a restored mm wallet
| 1
|
419,562
| 28,147,972,684
|
IssuesEvent
|
2023-04-02 17:59:07
|
AmanNegi/AgroMillets
|
https://api.github.com/repos/AmanNegi/AgroMillets
|
closed
|
[docs] Update URL in Readme.md
|
documentation help wanted good first issue
|
# Issue
We recently updated our documentation folder from `doc` to `docs` in #14. This invalidates the path of some links provided in `Readme.md`. We require you to update the URL to the valid path.
(PS: The `Contribute to AgroMillets` link is invalid)
|
1.0
|
[docs] Update URL in Readme.md - # Issue
We recently updated our documentation folder from `doc` to `docs` in #14. This invalidates the path of some links provided in `Readme.md`. We require you to update the URL to the valid path.
(PS: The `Contribute to AgroMillets` link is invalid)
|
non_test
|
update url in readme md issue we recently updated our documentation folder from doc to docs in this invalidates the path of some links provided in readme md we require you to update the url to the valid path ps the contribute to agromillets link is invalid
| 0
|
121,108
| 17,644,558,331
|
IssuesEvent
|
2021-08-20 02:45:45
|
SmartBear/ready-msazure-plugin
|
https://api.github.com/repos/SmartBear/ready-msazure-plugin
|
closed
|
CVE-2015-1796 (Medium) detected in opensaml-2.5.1-1.jar - autoclosed
|
security vulnerability
|
## CVE-2015-1796 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>opensaml-2.5.1-1.jar</b></p></summary>
<p>The OpenSAML-J library provides tools to support developers working with the Security Assertion Markup Language
(SAML).</p>
<p>Path to dependency file: ready-msazure-plugin/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/opensaml/opensaml/2.5.1-1/opensaml-2.5.1-1.jar</p>
<p>
Dependency Hierarchy:
- ready-api-soapui-pro-1.3.0.jar (Root Library)
- ready-api-soapui-1.3.0.jar
- wss4j-1.6.14.jar
- :x: **opensaml-2.5.1-1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/SmartBear/ready-msazure-plugin/commit/6da360f7efcb6c16cd8cd38894e0c0c71403d439">6da360f7efcb6c16cd8cd38894e0c0c71403d439</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>
The PKIX trust engines in Shibboleth Identity Provider before 2.4.4 and OpenSAML Java (OpenSAML-J) before 2.6.5 trust candidate X.509 credentials when no trusted names are available for the entityID, which allows remote attackers to impersonate an entity via a certificate issued by a shibmd:KeyAuthority trust anchor.
<p>Publish Date: 2015-07-08
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-1796>CVE-2015-1796</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>4.3</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1796">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1796</a></p>
<p>Release Date: 2015-07-08</p>
<p>Fix Resolution: 2.6.5</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.opensaml","packageName":"opensaml","packageVersion":"2.5.1-1","packageFilePaths":["/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"com.smartbear:ready-api-soapui-pro:1.3.0;com.smartbear:ready-api-soapui:1.3.0;org.apache.ws.security:wss4j:1.6.14;org.opensaml:opensaml:2.5.1-1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.6.5"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2015-1796","vulnerabilityDetails":"The PKIX trust engines in Shibboleth Identity Provider before 2.4.4 and OpenSAML Java (OpenSAML-J) before 2.6.5 trust candidate X.509 credentials when no trusted names are available for the entityID, which allows remote attackers to impersonate an entity via a certificate issued by a shibmd:KeyAuthority trust anchor.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-1796","cvss2Severity":"medium","cvss2Score":"4.3","extraData":{}}</REMEDIATE> -->
|
True
|
CVE-2015-1796 (Medium) detected in opensaml-2.5.1-1.jar - autoclosed - ## CVE-2015-1796 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>opensaml-2.5.1-1.jar</b></p></summary>
<p>The OpenSAML-J library provides tools to support developers working with the Security Assertion Markup Language
(SAML).</p>
<p>Path to dependency file: ready-msazure-plugin/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/opensaml/opensaml/2.5.1-1/opensaml-2.5.1-1.jar</p>
<p>
Dependency Hierarchy:
- ready-api-soapui-pro-1.3.0.jar (Root Library)
- ready-api-soapui-1.3.0.jar
- wss4j-1.6.14.jar
- :x: **opensaml-2.5.1-1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/SmartBear/ready-msazure-plugin/commit/6da360f7efcb6c16cd8cd38894e0c0c71403d439">6da360f7efcb6c16cd8cd38894e0c0c71403d439</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>
The PKIX trust engines in Shibboleth Identity Provider before 2.4.4 and OpenSAML Java (OpenSAML-J) before 2.6.5 trust candidate X.509 credentials when no trusted names are available for the entityID, which allows remote attackers to impersonate an entity via a certificate issued by a shibmd:KeyAuthority trust anchor.
<p>Publish Date: 2015-07-08
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-1796>CVE-2015-1796</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>4.3</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1796">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1796</a></p>
<p>Release Date: 2015-07-08</p>
<p>Fix Resolution: 2.6.5</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.opensaml","packageName":"opensaml","packageVersion":"2.5.1-1","packageFilePaths":["/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"com.smartbear:ready-api-soapui-pro:1.3.0;com.smartbear:ready-api-soapui:1.3.0;org.apache.ws.security:wss4j:1.6.14;org.opensaml:opensaml:2.5.1-1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.6.5"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2015-1796","vulnerabilityDetails":"The PKIX trust engines in Shibboleth Identity Provider before 2.4.4 and OpenSAML Java (OpenSAML-J) before 2.6.5 trust candidate X.509 credentials when no trusted names are available for the entityID, which allows remote attackers to impersonate an entity via a certificate issued by a shibmd:KeyAuthority trust anchor.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-1796","cvss2Severity":"medium","cvss2Score":"4.3","extraData":{}}</REMEDIATE> -->
|
non_test
|
cve medium detected in opensaml jar autoclosed cve medium severity vulnerability vulnerable library opensaml jar the opensaml j library provides tools to support developers working with the security assertion markup language saml path to dependency file ready msazure plugin pom xml path to vulnerable library home wss scanner repository org opensaml opensaml opensaml jar dependency hierarchy ready api soapui pro jar root library ready api soapui jar jar x opensaml jar vulnerable library found in head commit a href found in base branch master vulnerability details the pkix trust engines in shibboleth identity provider before and opensaml java opensaml j before trust candidate x credentials when no trusted names are available for the entityid which allows remote attackers to impersonate an entity via a certificate issued by a shibmd keyauthority trust anchor publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree com smartbear ready api soapui pro com smartbear ready api soapui org apache ws security org opensaml opensaml isminimumfixversionavailable true minimumfixversion basebranches vulnerabilityidentifier cve vulnerabilitydetails the pkix trust engines in shibboleth identity provider before and opensaml java opensaml j before trust candidate x credentials when no trusted names are available for the entityid which allows remote attackers to impersonate an entity via a certificate issued by a shibmd keyauthority trust anchor vulnerabilityurl
| 0
|
39,332
| 19,831,006,406
|
IssuesEvent
|
2022-01-20 11:59:39
|
appsmithorg/appsmith
|
https://api.github.com/repos/appsmithorg/appsmith
|
opened
|
[Bug]: Table flickers on page load, when there are multiple dependent fields from a table
|
Bug Table Widget Performance Needs Triaging
|
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current Behavior
When a table has multiple dependent widgets like multiple dropdowns which update the table's data. The table is refreshed multiple times on page load. A user on discord also reported this.
### Steps To Reproduce
1. Open the [A-force app](https://app.appsmith.com/applications/61cd5be2a4437918c01f87af/pages/61cd8575a4437918c01f89b2)
2. Observe how the table flickers multiple times before loading the data.
https://user-images.githubusercontent.com/19730984/150334346-dd4ed67f-8886-4926-8df7-37507fcf80bb.mov
### Environment
Production
### Version
Cloud
|
True
|
[Bug]: Table flickers on page load, when there are multiple dependent fields from a table - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current Behavior
When a table has multiple dependent widgets like multiple dropdowns which update the table's data. The table is refreshed multiple times on page load. A user on discord also reported this.
### Steps To Reproduce
1. Open the [A-force app](https://app.appsmith.com/applications/61cd5be2a4437918c01f87af/pages/61cd8575a4437918c01f89b2)
2. Observe how the table flickers multiple times before loading the data.
https://user-images.githubusercontent.com/19730984/150334346-dd4ed67f-8886-4926-8df7-37507fcf80bb.mov
### Environment
Production
### Version
Cloud
|
non_test
|
table flickers on page load when there are multiple dependent fields from a table is there an existing issue for this i have searched the existing issues current behavior when a table has multiple dependent widgets like multiple dropdowns which update the table s data the table is refreshed multiple times on page load a user on discord also reported this steps to reproduce open the observe how the table flickers multiple times before loading the data environment production version cloud
| 0
|
26,733
| 5,283,785,143
|
IssuesEvent
|
2017-02-07 22:17:04
|
spring-cloud-stream-app-starters/jdbc
|
https://api.github.com/repos/spring-cloud-stream-app-starters/jdbc
|
closed
|
Default table name for jdbc sink doesn't match docs
|
bug documentation in pr
|
_From @trisberg on June 9, 2016 20:22_
The docs say that the default table name is "stream-name" while the actual name of the table created was "messages".
```
tableName
String (String, default: <stream name)
```
_Copied from original issue: spring-cloud/spring-cloud-stream-app-starters#120_
|
1.0
|
Default table name for jdbc sink doesn't match docs - _From @trisberg on June 9, 2016 20:22_
The docs say that the default table name is "stream-name" while the actual name of the table created was "messages".
```
tableName
String (String, default: <stream name)
```
_Copied from original issue: spring-cloud/spring-cloud-stream-app-starters#120_
|
non_test
|
default table name for jdbc sink doesn t match docs from trisberg on june the docs say that the default table name is stream name while the actual name of the table created was messages tablename string string default stream name copied from original issue spring cloud spring cloud stream app starters
| 0
|
89,598
| 8,209,521,999
|
IssuesEvent
|
2018-09-04 07:53:28
|
edenlabllc/ehealth.web
|
https://api.github.com/repos/edenlabllc/ehealth.web
|
closed
|
place all pop-ups in the center
|
FE epic/cabinet in progress status/test
|
place all pop-ups in the center
repo steps
- login to cabinet
- goto "РОЗІРВАТИ ДЕКЛАРАЦІЮ"
Actual result - pop up is behind the screen (see pic)
expected result - pop up is in the centre so I can see all popup and press any button
<img width="1439" alt="google chrome_2018-08-31 16-29-58 2x" src="https://user-images.githubusercontent.com/30794602/44915283-48bfb880-ad3b-11e8-8cbd-838e00b75e33.png">
|
1.0
|
place all pop-ups in the center - place all pop-ups in the center
repo steps
- login to cabinet
- goto "РОЗІРВАТИ ДЕКЛАРАЦІЮ"
Actual result - pop up is behind the screen (see pic)
expected result - pop up is in the centre so I can see all popup and press any button
<img width="1439" alt="google chrome_2018-08-31 16-29-58 2x" src="https://user-images.githubusercontent.com/30794602/44915283-48bfb880-ad3b-11e8-8cbd-838e00b75e33.png">
|
test
|
place all pop ups in the center place all pop ups in the center repo steps login to cabinet goto розірвати декларацію actual result pop up is behind the screen see pic expected result pop up is in the centre so i can see all popup and press any button img width alt google chrome src
| 1
|
98,795
| 8,685,468,464
|
IssuesEvent
|
2018-12-03 07:51:34
|
humera987/FXLabs-Test-Automation
|
https://api.github.com/repos/humera987/FXLabs-Test-Automation
|
closed
|
FX Testing 3 : ApiV1RunsIdTestSuiteSummaryGetQueryParamPagesizeEmptyValue
|
FX Testing 3
|
Project : FX Testing 3
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=ZmRmMWFhY2UtNWI5ZC00ZGMzLWI2MjUtYzZlNjBhODhjZDky; Path=/; HttpOnly], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Mon, 03 Dec 2018 04:40:20 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/runs/lUHPBYNy/test-suite-summary?pageSize=
Request :
Response :
{
"timestamp" : "2018-12-03T04:40:20.879+0000",
"status" : 404,
"error" : "Not Found",
"message" : "No message available",
"path" : "/api/v1/api/v1/runs/lUHPBYNy/test-suite-summary"
}
Logs :
Assertion [@StatusCode != 401] resolved-to [404 != 401] result [Passed]Assertion [@StatusCode != 500] resolved-to [404 != 500] result [Passed]Assertion [@StatusCode != 404] resolved-to [404 != 404] result [Failed]Assertion [@StatusCode != 200] resolved-to [404 != 200] result [Passed]
--- FX Bot ---
|
1.0
|
FX Testing 3 : ApiV1RunsIdTestSuiteSummaryGetQueryParamPagesizeEmptyValue - Project : FX Testing 3
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=ZmRmMWFhY2UtNWI5ZC00ZGMzLWI2MjUtYzZlNjBhODhjZDky; Path=/; HttpOnly], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Mon, 03 Dec 2018 04:40:20 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/runs/lUHPBYNy/test-suite-summary?pageSize=
Request :
Response :
{
"timestamp" : "2018-12-03T04:40:20.879+0000",
"status" : 404,
"error" : "Not Found",
"message" : "No message available",
"path" : "/api/v1/api/v1/runs/lUHPBYNy/test-suite-summary"
}
Logs :
Assertion [@StatusCode != 401] resolved-to [404 != 401] result [Passed]Assertion [@StatusCode != 500] resolved-to [404 != 500] result [Passed]Assertion [@StatusCode != 404] resolved-to [404 != 404] result [Failed]Assertion [@StatusCode != 200] resolved-to [404 != 200] result [Passed]
--- FX Bot ---
|
test
|
fx testing project fx 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 runs luhpbyny test suite summary logs assertion resolved to result assertion resolved to result assertion resolved to result assertion resolved to result fx bot
| 1
|
321,528
| 27,536,709,644
|
IssuesEvent
|
2023-03-07 04:24:59
|
kevinbowen777/django-start
|
https://api.github.com/repos/kevinbowen777/django-start
|
closed
|
Add contact form tests to pages/tests/test_forms.py
|
testing
|
Create `pages/tests/tests_forms.py` and add the following:
```
from django.test import SimpleTestCase
from django.urls import reverse
class ContactFormTests(SimpleTestCase):
def setUp(self):
url = reverse("contact")
self.response = self.client.get(url)
self.form_data = {
"from_email": "joe@example.com",
"subject": "Test Email",
"message": "This is a test email",
}
def test_contact_page_form_is_valid(self):
response = self.client.post(
"/contact/",
data={
"from_email": "joe@example.com",
"subject": "Test Email",
"message": "This is a test email",
},
)
self.assertEqual(response.status_code, 302)
```
|
1.0
|
Add contact form tests to pages/tests/test_forms.py - Create `pages/tests/tests_forms.py` and add the following:
```
from django.test import SimpleTestCase
from django.urls import reverse
class ContactFormTests(SimpleTestCase):
def setUp(self):
url = reverse("contact")
self.response = self.client.get(url)
self.form_data = {
"from_email": "joe@example.com",
"subject": "Test Email",
"message": "This is a test email",
}
def test_contact_page_form_is_valid(self):
response = self.client.post(
"/contact/",
data={
"from_email": "joe@example.com",
"subject": "Test Email",
"message": "This is a test email",
},
)
self.assertEqual(response.status_code, 302)
```
|
test
|
add contact form tests to pages tests test forms py create pages tests tests forms py and add the following from django test import simpletestcase from django urls import reverse class contactformtests simpletestcase def setup self url reverse contact self response self client get url self form data from email joe example com subject test email message this is a test email def test contact page form is valid self response self client post contact data from email joe example com subject test email message this is a test email self assertequal response status code
| 1
|
22,730
| 20,048,368,070
|
IssuesEvent
|
2022-02-03 01:09:51
|
mosaicml/composer
|
https://api.github.com/repos/mosaicml/composer
|
closed
|
Move composer.algorithms.functional -> composer.functional
|
usability/API
|
Simple file move based on functional API discussion.
|
True
|
Move composer.algorithms.functional -> composer.functional - Simple file move based on functional API discussion.
|
non_test
|
move composer algorithms functional composer functional simple file move based on functional api discussion
| 0
|
245,539
| 18,786,895,272
|
IssuesEvent
|
2021-11-08 13:07:25
|
sannesofie/sanne-ux-ui
|
https://api.github.com/repos/sannesofie/sanne-ux-ui
|
opened
|
open-ended ideation
|
documentation ui/ux planning
|
Sketch up a few wireframes for your partner's home page with no regard for your their programming ability, time constraints, technical constraints, or any other practical considerations.
How are the designs different? How does each one serve your partner differently?
-->
- [Sanne's Homepage](https://www.figma.com/file/6gMup79OfrAupqwIsn4pn4/Sanne's-homepage?node-id=0%3A1)
- ...
|
1.0
|
open-ended ideation - Sketch up a few wireframes for your partner's home page with no regard for your their programming ability, time constraints, technical constraints, or any other practical considerations.
How are the designs different? How does each one serve your partner differently?
-->
- [Sanne's Homepage](https://www.figma.com/file/6gMup79OfrAupqwIsn4pn4/Sanne's-homepage?node-id=0%3A1)
- ...
|
non_test
|
open ended ideation sketch up a few wireframes for your partner s home page with no regard for your their programming ability time constraints technical constraints or any other practical considerations how are the designs different how does each one serve your partner differently
| 0
|
86,924
| 17,104,754,412
|
IssuesEvent
|
2021-07-09 15:59:06
|
ArctosDB/arctos
|
https://api.github.com/repos/ArctosDB/arctos
|
closed
|
Problem Formations need clean-up
|
Function-CodeTables Priority-Normal
|
I am going to use this issue to list problematic formations as I work to clean up the [lithostratigraphic_formation code table](https://arctos.database.museum/info/ctDocumentation.cfm?table=ctlithostratigraphic_formation).
<!-- probot = {"768919":{"who":"Jegelewicz","what":"work on this","when":"2020-08-03T15:00:00.000Z"}} -->
|
1.0
|
Problem Formations need clean-up - I am going to use this issue to list problematic formations as I work to clean up the [lithostratigraphic_formation code table](https://arctos.database.museum/info/ctDocumentation.cfm?table=ctlithostratigraphic_formation).
<!-- probot = {"768919":{"who":"Jegelewicz","what":"work on this","when":"2020-08-03T15:00:00.000Z"}} -->
|
non_test
|
problem formations need clean up i am going to use this issue to list problematic formations as i work to clean up the
| 0
|
201,380
| 15,192,462,179
|
IssuesEvent
|
2021-02-15 22:06:07
|
cyfronet-fid/sat4envi
|
https://api.github.com/repos/cyfronet-fid/sat4envi
|
opened
|
[FIX] Url parameters after go back from data search
|
bug dev-env-test pre-prod-test
|
Tested on instance SOK version
SOK version v17.2.1
**Steps:**
1. Log as zkAdmin
2. Click the button "Szukaj danych"
3. Check product "Sentinel 1"
4. Click "Szukaj" - data is displayed
5. Click the button "Powrot do formularza"
6. Click "Zdjecia Satelitarne", return to map view
**What happens?**
Url is dane.sat4envi.imgw.pl/map/products?zoom=6¢erx=2115070.325072198¢ery=6800125.454397307&visible_sent=Sentinel-1.metadata.v1.json&selected_sent=Sentinel-1.metadata.v1.json&page=0&searchParams={"common":{"sortBy":"sensingTime","order":"DESC"},"Sentinel-1.metadata.v1.json":{"productType":"Sentinel-1-GRDH"},"Sentinel-2.metadata.v1.json":{},"MSG.metadata.v1.json":{},"MSG_Raw.metadata.v1.json":{},"Sentinel-3_Raw.metadata.v1.json":{}}
**What was expected to happen?**
Url is dane.sat4envi.imgw.pl/map/products?zoom=6¢erx=2115070.325072198¢ery=6800125.454397307
|
2.0
|
[FIX] Url parameters after go back from data search - Tested on instance SOK version
SOK version v17.2.1
**Steps:**
1. Log as zkAdmin
2. Click the button "Szukaj danych"
3. Check product "Sentinel 1"
4. Click "Szukaj" - data is displayed
5. Click the button "Powrot do formularza"
6. Click "Zdjecia Satelitarne", return to map view
**What happens?**
Url is dane.sat4envi.imgw.pl/map/products?zoom=6¢erx=2115070.325072198¢ery=6800125.454397307&visible_sent=Sentinel-1.metadata.v1.json&selected_sent=Sentinel-1.metadata.v1.json&page=0&searchParams={"common":{"sortBy":"sensingTime","order":"DESC"},"Sentinel-1.metadata.v1.json":{"productType":"Sentinel-1-GRDH"},"Sentinel-2.metadata.v1.json":{},"MSG.metadata.v1.json":{},"MSG_Raw.metadata.v1.json":{},"Sentinel-3_Raw.metadata.v1.json":{}}
**What was expected to happen?**
Url is dane.sat4envi.imgw.pl/map/products?zoom=6¢erx=2115070.325072198¢ery=6800125.454397307
|
test
|
url parameters after go back from data search tested on instance sok version sok version steps log as zkadmin click the button szukaj danych check product sentinel click szukaj data is displayed click the button powrot do formularza click zdjecia satelitarne return to map view what happens url is dane imgw pl map products zoom centerx centery visible sent sentinel metadata json selected sent sentinel metadata json page searchparams common sortby sensingtime order desc sentinel metadata json producttype sentinel grdh sentinel metadata json msg metadata json msg raw metadata json sentinel raw metadata json what was expected to happen url is dane imgw pl map products zoom centerx centery
| 1
|
60,924
| 8,475,534,696
|
IssuesEvent
|
2018-10-24 19:11:50
|
scheebeek/arnold
|
https://api.github.com/repos/scheebeek/arnold
|
opened
|
Write documentation
|
type: documentation
|
Update the README
- project description
- development
- deployment
- ...
|
1.0
|
Write documentation - Update the README
- project description
- development
- deployment
- ...
|
non_test
|
write documentation update the readme project description development deployment
| 0
|
770,860
| 27,058,825,678
|
IssuesEvent
|
2023-02-13 18:04:59
|
union-platform/union-mobile-app
|
https://api.github.com/repos/union-platform/union-mobile-app
|
opened
|
Project manager wants to respond to the application to the project, since the project participants has made a decision about the candidate
|
priority: high type: feature
|
**Scope of action:** Project Participants Screen
**Precondition:** The user or team has submitted an application to the project
**Design:** https://www.figma.com/file/2St3zSul4fHnLffqy3WK7P/union-mobile?node-id=5659%3A45746
## Use cases:
1. The project manager clicks on the "accept" button
(a):
1. The project manager clicks on the "reject" button
2. The system rejects the user's (or team's) request
3. The system prohibits the user (or team) from submitting an application to the project (adding is possible only by invitation)
2. The system adds a user (or team) to the project
-----
**Область действия:** Экран участников проекта
**Предусловие:** Пользователь или команда подали заявку в проект
**Дизайн:** https://www.figma.com/file/2St3zSul4fHnLffqy3WK7P/union-mobile?node-id=5659%3A45746
## Сценарий:
1. Руководитель проекта нажимает на кнопку "принять"
(а):
1. Руководитель проекта нажимает на кнопку "отклонить"
2. Система отклоняет заявку пользователя или команды
3. Система запрещает пользователю или команде подавать заявку в проект (добавление возможно только по приглашению)
2. Система добавляет пользователя или команду в проект
|
1.0
|
Project manager wants to respond to the application to the project, since the project participants has made a decision about the candidate - **Scope of action:** Project Participants Screen
**Precondition:** The user or team has submitted an application to the project
**Design:** https://www.figma.com/file/2St3zSul4fHnLffqy3WK7P/union-mobile?node-id=5659%3A45746
## Use cases:
1. The project manager clicks on the "accept" button
(a):
1. The project manager clicks on the "reject" button
2. The system rejects the user's (or team's) request
3. The system prohibits the user (or team) from submitting an application to the project (adding is possible only by invitation)
2. The system adds a user (or team) to the project
-----
**Область действия:** Экран участников проекта
**Предусловие:** Пользователь или команда подали заявку в проект
**Дизайн:** https://www.figma.com/file/2St3zSul4fHnLffqy3WK7P/union-mobile?node-id=5659%3A45746
## Сценарий:
1. Руководитель проекта нажимает на кнопку "принять"
(а):
1. Руководитель проекта нажимает на кнопку "отклонить"
2. Система отклоняет заявку пользователя или команды
3. Система запрещает пользователю или команде подавать заявку в проект (добавление возможно только по приглашению)
2. Система добавляет пользователя или команду в проект
|
non_test
|
project manager wants to respond to the application to the project since the project participants has made a decision about the candidate scope of action project participants screen precondition the user or team has submitted an application to the project design use cases the project manager clicks on the accept button a the project manager clicks on the reject button the system rejects the user s or team s request the system prohibits the user or team from submitting an application to the project adding is possible only by invitation the system adds a user or team to the project область действия экран участников проекта предусловие пользователь или команда подали заявку в проект дизайн сценарий руководитель проекта нажимает на кнопку принять а руководитель проекта нажимает на кнопку отклонить система отклоняет заявку пользователя или команды система запрещает пользователю или команде подавать заявку в проект добавление возможно только по приглашению система добавляет пользователя или команду в проект
| 0
|
88,792
| 11,149,845,646
|
IssuesEvent
|
2019-12-23 20:11:03
|
vector-im/riot-web
|
https://api.github.com/repos/vector-im/riot-web
|
closed
|
Transparent avatars on the LLP are green now (when selected)
|
bug cosmetic minor needs-design p2 type:avatar type:llp
|
<!-- This is a bug report template. By following the instructions below and
filling out the sections with your information, you will help the us to get all
the necessary data to fix your issue.
You can also preview your report before submitting it. You may remove sections
that aren't relevant to your particular case.
Text between <!-- and --> marks will be invisible in the report.
-->
### Description
They used to be white.
### Version information
<!-- IMPORTANT: please answer the following questions, to help us narrow down the problem -->
- **Platform**: web (in-browser)
- **Browser**: Chrome 64
- **OS**: Windows 10
- **URL**: riot.im/develop
|
1.0
|
Transparent avatars on the LLP are green now (when selected) - <!-- This is a bug report template. By following the instructions below and
filling out the sections with your information, you will help the us to get all
the necessary data to fix your issue.
You can also preview your report before submitting it. You may remove sections
that aren't relevant to your particular case.
Text between <!-- and --> marks will be invisible in the report.
-->
### Description
They used to be white.
### Version information
<!-- IMPORTANT: please answer the following questions, to help us narrow down the problem -->
- **Platform**: web (in-browser)
- **Browser**: Chrome 64
- **OS**: Windows 10
- **URL**: riot.im/develop
|
non_test
|
transparent avatars on the llp are green now when selected this is a bug report template by following the instructions below and filling out the sections with your information you will help the us to get all the necessary data to fix your issue you can also preview your report before submitting it you may remove sections that aren t relevant to your particular case text between marks will be invisible in the report description they used to be white version information platform web in browser browser chrome os windows url riot im develop
| 0
|
298,470
| 22,500,767,180
|
IssuesEvent
|
2022-06-23 11:37:30
|
PharmaLedger-IMI/fgt-workspace
|
https://api.github.com/repos/PharmaLedger-IMI/fgt-workspace
|
closed
|
Deploy v0.9.6 to v0.9.7 to DEV without loosing blockchain contents
|
documentation
|
Pre-requirements: the tag is created and pushed into master. master points to v0.9.7. blockchain-hf-workspace is running on DEV.
```sh
pharmaledger@fgt-dev-pl:~/fgt-workspace/docker/api$ docker-compose down --rmi local
WARNING: The SIMPLE variable is not set. Defaulting to a blank string.
WARNING: The DOMAIN variable is not set. Defaulting to a blank string.
WARNING: The PROTOCOL variable is not set. Defaulting to a blank string.
WARNING: The SWAGGER variable is not set. Defaulting to a blank string.
Stopping pha-zuellig ... done
Stopping pha1 ... done
Stopping pha2 ... done
Stopping whs2 ... done
Stopping whs-takeda ... done
Stopping whs1 ... done
Stopping mah-pfizer ... done
Stopping mah-bayer ... done
Stopping mah-sanofi ... done
Stopping mah-novo-nordisk ... done
Stopping mah-takeda ... done
Stopping mah-msd ... done
Stopping mah-gsk ... done
Stopping mah-roche ... done
Stopping fgt-workspace ... done
Stopping traefik-logrotate ... done
Stopping traefik ... done
Removing pha-zuellig ... done
Removing pha1 ... done
Removing pha2 ... done
Removing whs2 ... done
Removing whs-takeda ... done
Removing whs1 ... done
Removing mah-pfizer ... done
Removing mah-bayer ... done
Removing mah-sanofi ... done
Removing mah-novo-nordisk ... done
Removing mah-takeda ... done
Removing mah-msd ... done
Removing mah-gsk ... done
Removing mah-roche ... done
Removing fgt-workspace ... done
Removing traefik-logrotate ... done
Removing traefik ... done
Removing network traceability-net
Removing network api_default
Removing image api_fgt-workspace
Removing image api_mah-roche
Removing image api_mah-bayer
Removing image api_mah-gsk
Removing image api_mah-msd
Removing image api_mah-novo-nordisk
Removing image api_mah-pfizer
Removing image api_mah-takeda
Removing image api_mah-sanofi
Removing image api_whs-1
Removing image api_whs-2
Removing image api_whs-takeda
Removing image api_pha-1
Removing image api_pha-2
Removing image api_pha-zuellig
pharmaledger@fgt-dev-pl:~/fgt-workspace/docker/api$ git pull
pharmaledger@fgt-dev-pl:~/fgt-workspace/docker/api$ ./bootCompose.sh eth-dev
```
|
1.0
|
Deploy v0.9.6 to v0.9.7 to DEV without loosing blockchain contents - Pre-requirements: the tag is created and pushed into master. master points to v0.9.7. blockchain-hf-workspace is running on DEV.
```sh
pharmaledger@fgt-dev-pl:~/fgt-workspace/docker/api$ docker-compose down --rmi local
WARNING: The SIMPLE variable is not set. Defaulting to a blank string.
WARNING: The DOMAIN variable is not set. Defaulting to a blank string.
WARNING: The PROTOCOL variable is not set. Defaulting to a blank string.
WARNING: The SWAGGER variable is not set. Defaulting to a blank string.
Stopping pha-zuellig ... done
Stopping pha1 ... done
Stopping pha2 ... done
Stopping whs2 ... done
Stopping whs-takeda ... done
Stopping whs1 ... done
Stopping mah-pfizer ... done
Stopping mah-bayer ... done
Stopping mah-sanofi ... done
Stopping mah-novo-nordisk ... done
Stopping mah-takeda ... done
Stopping mah-msd ... done
Stopping mah-gsk ... done
Stopping mah-roche ... done
Stopping fgt-workspace ... done
Stopping traefik-logrotate ... done
Stopping traefik ... done
Removing pha-zuellig ... done
Removing pha1 ... done
Removing pha2 ... done
Removing whs2 ... done
Removing whs-takeda ... done
Removing whs1 ... done
Removing mah-pfizer ... done
Removing mah-bayer ... done
Removing mah-sanofi ... done
Removing mah-novo-nordisk ... done
Removing mah-takeda ... done
Removing mah-msd ... done
Removing mah-gsk ... done
Removing mah-roche ... done
Removing fgt-workspace ... done
Removing traefik-logrotate ... done
Removing traefik ... done
Removing network traceability-net
Removing network api_default
Removing image api_fgt-workspace
Removing image api_mah-roche
Removing image api_mah-bayer
Removing image api_mah-gsk
Removing image api_mah-msd
Removing image api_mah-novo-nordisk
Removing image api_mah-pfizer
Removing image api_mah-takeda
Removing image api_mah-sanofi
Removing image api_whs-1
Removing image api_whs-2
Removing image api_whs-takeda
Removing image api_pha-1
Removing image api_pha-2
Removing image api_pha-zuellig
pharmaledger@fgt-dev-pl:~/fgt-workspace/docker/api$ git pull
pharmaledger@fgt-dev-pl:~/fgt-workspace/docker/api$ ./bootCompose.sh eth-dev
```
|
non_test
|
deploy to to dev without loosing blockchain contents pre requirements the tag is created and pushed into master master points to blockchain hf workspace is running on dev sh pharmaledger fgt dev pl fgt workspace docker api docker compose down rmi local warning the simple variable is not set defaulting to a blank string warning the domain variable is not set defaulting to a blank string warning the protocol variable is not set defaulting to a blank string warning the swagger variable is not set defaulting to a blank string stopping pha zuellig done stopping done stopping done stopping done stopping whs takeda done stopping done stopping mah pfizer done stopping mah bayer done stopping mah sanofi done stopping mah novo nordisk done stopping mah takeda done stopping mah msd done stopping mah gsk done stopping mah roche done stopping fgt workspace done stopping traefik logrotate done stopping traefik done removing pha zuellig done removing done removing done removing done removing whs takeda done removing done removing mah pfizer done removing mah bayer done removing mah sanofi done removing mah novo nordisk done removing mah takeda done removing mah msd done removing mah gsk done removing mah roche done removing fgt workspace done removing traefik logrotate done removing traefik done removing network traceability net removing network api default removing image api fgt workspace removing image api mah roche removing image api mah bayer removing image api mah gsk removing image api mah msd removing image api mah novo nordisk removing image api mah pfizer removing image api mah takeda removing image api mah sanofi removing image api whs removing image api whs removing image api whs takeda removing image api pha removing image api pha removing image api pha zuellig pharmaledger fgt dev pl fgt workspace docker api git pull pharmaledger fgt dev pl fgt workspace docker api bootcompose sh eth dev
| 0
|
377,606
| 11,177,045,188
|
IssuesEvent
|
2019-12-30 09:23:21
|
swash99/ims
|
https://api.github.com/repos/swash99/ims
|
closed
|
Ability to display notifications to user
|
Low Priority feature
|
A very useful feature would be the ability to communicate notifications to the user similar to how Facebook would display notifications with their icon and bubble display (when you click on icon). Ideally this would be a small button/icon which shows a bubble display when clicked -- it could also take you to another notifications page similar to Messages but that might be overkill.
|
1.0
|
Ability to display notifications to user - A very useful feature would be the ability to communicate notifications to the user similar to how Facebook would display notifications with their icon and bubble display (when you click on icon). Ideally this would be a small button/icon which shows a bubble display when clicked -- it could also take you to another notifications page similar to Messages but that might be overkill.
|
non_test
|
ability to display notifications to user a very useful feature would be the ability to communicate notifications to the user similar to how facebook would display notifications with their icon and bubble display when you click on icon ideally this would be a small button icon which shows a bubble display when clicked it could also take you to another notifications page similar to messages but that might be overkill
| 0
|
139,875
| 31,802,087,503
|
IssuesEvent
|
2023-09-13 11:49:06
|
h4sh5/pypi-auto-scanner
|
https://api.github.com/repos/h4sh5/pypi-auto-scanner
|
opened
|
gpaw 23.9.0 has 2 GuardDog issues
|
guarddog code-execution exec-base64
|
https://pypi.org/project/gpaw
https://inspector.pypi.io/project/gpaw
```{
"dependency": "gpaw",
"version": "23.9.0",
"result": {
"issues": 2,
"errors": {},
"results": {
"code-execution": [
{
"location": "gpaw-23.9.0/setup.py:135",
"code": " and run(['which', 'mpicc'],\n capture_output=True).returncode == 0):",
"message": "This package is executing OS commands in the setup.py file"
}
],
"exec-base64": [
{
"location": "gpaw-23.9.0/gpaw/test/crontab.py:35",
"code": " p = subprocess.run(cmds2, shell=True)",
"message": "This package contains a call to the `eval` function with a `base64` encoded string as argument.\nThis is a common method used to hide a malicious payload in a module as static analysis will not decode the\nstring.\n"
}
]
},
"path": "/tmp/tmp7_v6hv2q/gpaw"
}
}```
|
1.0
|
gpaw 23.9.0 has 2 GuardDog issues - https://pypi.org/project/gpaw
https://inspector.pypi.io/project/gpaw
```{
"dependency": "gpaw",
"version": "23.9.0",
"result": {
"issues": 2,
"errors": {},
"results": {
"code-execution": [
{
"location": "gpaw-23.9.0/setup.py:135",
"code": " and run(['which', 'mpicc'],\n capture_output=True).returncode == 0):",
"message": "This package is executing OS commands in the setup.py file"
}
],
"exec-base64": [
{
"location": "gpaw-23.9.0/gpaw/test/crontab.py:35",
"code": " p = subprocess.run(cmds2, shell=True)",
"message": "This package contains a call to the `eval` function with a `base64` encoded string as argument.\nThis is a common method used to hide a malicious payload in a module as static analysis will not decode the\nstring.\n"
}
]
},
"path": "/tmp/tmp7_v6hv2q/gpaw"
}
}```
|
non_test
|
gpaw has guarddog issues dependency gpaw version result issues errors results code execution location gpaw setup py code and run n capture output true returncode message this package is executing os commands in the setup py file exec location gpaw gpaw test crontab py code p subprocess run shell true message this package contains a call to the eval function with a encoded string as argument nthis is a common method used to hide a malicious payload in a module as static analysis will not decode the nstring n path tmp gpaw
| 0
|
142,299
| 11,463,211,917
|
IssuesEvent
|
2020-02-07 15:35:34
|
redhat-developer/s2i-dotnetcore
|
https://api.github.com/repos/redhat-developer/s2i-dotnetcore
|
closed
|
Automate imagestream testing
|
test
|
Our tests are docker and image centric.
It would be nice to also automate testing of imagestreams/templates.
Perhaps we can use `minishift` to facilitate running these tests locally.
CC @RheaAyase @aslicerh
|
1.0
|
Automate imagestream testing - Our tests are docker and image centric.
It would be nice to also automate testing of imagestreams/templates.
Perhaps we can use `minishift` to facilitate running these tests locally.
CC @RheaAyase @aslicerh
|
test
|
automate imagestream testing our tests are docker and image centric it would be nice to also automate testing of imagestreams templates perhaps we can use minishift to facilitate running these tests locally cc rheaayase aslicerh
| 1
|
254,634
| 21,801,920,424
|
IssuesEvent
|
2022-05-16 06:35:41
|
keycloak/keycloak
|
https://api.github.com/repos/keycloak/keycloak
|
closed
|
Include WebAuthn tests to GH Actions
|
area/testsuite kind/enhancement area/authentication/webauthn
|
### Description
It'd be great to include WebAuthn tests to the GH actions flow in order to ensure the changes related to WebAuthn don't cause some failures.
See: https://issues.redhat.com/browse/KEYCLOAK-19493
|
1.0
|
Include WebAuthn tests to GH Actions - ### Description
It'd be great to include WebAuthn tests to the GH actions flow in order to ensure the changes related to WebAuthn don't cause some failures.
See: https://issues.redhat.com/browse/KEYCLOAK-19493
|
test
|
include webauthn tests to gh actions description it d be great to include webauthn tests to the gh actions flow in order to ensure the changes related to webauthn don t cause some failures see
| 1
|
257,842
| 19,532,961,969
|
IssuesEvent
|
2021-12-30 21:04:01
|
vincent-picaud/NLS_Solver.jl
|
https://api.github.com/repos/vincent-picaud/NLS_Solver.jl
|
closed
|
New version v0.4.1
|
documentation
|
@JuliaRegistrator register
- mostly a documentation effort
- `Abstract_Solver_Result` and sub-types are now public
|
1.0
|
New version v0.4.1 - @JuliaRegistrator register
- mostly a documentation effort
- `Abstract_Solver_Result` and sub-types are now public
|
non_test
|
new version juliaregistrator register mostly a documentation effort abstract solver result and sub types are now public
| 0
|
702,519
| 24,124,452,667
|
IssuesEvent
|
2022-09-20 22:07:53
|
IDAES/idaes-pse
|
https://api.github.com/repos/IDAES/idaes-pse
|
closed
|
Grid Integration/PySMO Errors From Pandas Version Update
|
Priority:High
|
Four hours ago, `pandas` released version 1.5 which broke several tests using DataFrame indexing. We should either resolve the issues, and/or temporarily pin `pandas` to the prior stable version 1.4.4.
|
1.0
|
Grid Integration/PySMO Errors From Pandas Version Update - Four hours ago, `pandas` released version 1.5 which broke several tests using DataFrame indexing. We should either resolve the issues, and/or temporarily pin `pandas` to the prior stable version 1.4.4.
|
non_test
|
grid integration pysmo errors from pandas version update four hours ago pandas released version which broke several tests using dataframe indexing we should either resolve the issues and or temporarily pin pandas to the prior stable version
| 0
|
91,728
| 8,317,368,485
|
IssuesEvent
|
2018-09-25 11:53:49
|
edenlabllc/ehealth.web
|
https://api.github.com/repos/edenlabllc/ehealth.web
|
closed
|
nhs legacy admin auth error
|
FE bug epic/NHS_admin_portal status/test
|
- [x] In case token has expired there is no redirect to sign in page. As for now empty screen is shown
- [x] in case token is not valid also should be redirect to sign in page
|
1.0
|
nhs legacy admin auth error - - [x] In case token has expired there is no redirect to sign in page. As for now empty screen is shown
- [x] in case token is not valid also should be redirect to sign in page
|
test
|
nhs legacy admin auth error in case token has expired there is no redirect to sign in page as for now empty screen is shown in case token is not valid also should be redirect to sign in page
| 1
|
264,834
| 23,142,455,068
|
IssuesEvent
|
2022-07-28 19:57:06
|
microsoft/playwright
|
https://api.github.com/repos/microsoft/playwright
|
closed
|
[BUG] Setting the use.trace option to `undefined` causes TypeError: Cannot read property 'mode' of undefined
|
feature-test-runner v1.25
|
## Context:
- Playwright Version: 1.22.2
- Operating System: Windows
- Node.js version: 14.18
- Browser: All
## Code Snippet
### Test file
```ts
// tests/example.test.ts
import { test } from '@playwright/test'
test('test', async () => {})
```
### Playwright Config
```ts
// playwright.config.ts
import { PlaywrightTestConfig } from "@playwright/test";
const playwrightTestConfig: PlaywrightTestConfig = {
use: {
trace: undefined,
},
};
export default playwrightTestConfig;
```
**Describe the bug**
Running the above throws this error:
```
Running 1 test using 1 worker
✘ test/example.test.ts:4:1 › test (4ms)
1) test/example.test.ts:4:1 › test ==================================================================
TypeError: Cannot read property 'mode' of undefined
1 failed
test/example.test.ts:4:1 › test ===================================================================
```
This is caused by having `use,trace` as undefined in the playwright config.
This used to work with Playwright `v1.19`, and given the types of the option (`trace?: ...`), it should be allowed.
_After_ you figure out what the problem actually is, it is not a big deal as you can simply set the option to `off` instead of `undefined`. But it did take me a while to find that the trace option was causing it, as there is no stack trace in the error.
I got this right after upgrading to `v1.21`, and the reason the option is undefined is that I was setting it conditionally.
|
1.0
|
[BUG] Setting the use.trace option to `undefined` causes TypeError: Cannot read property 'mode' of undefined - ## Context:
- Playwright Version: 1.22.2
- Operating System: Windows
- Node.js version: 14.18
- Browser: All
## Code Snippet
### Test file
```ts
// tests/example.test.ts
import { test } from '@playwright/test'
test('test', async () => {})
```
### Playwright Config
```ts
// playwright.config.ts
import { PlaywrightTestConfig } from "@playwright/test";
const playwrightTestConfig: PlaywrightTestConfig = {
use: {
trace: undefined,
},
};
export default playwrightTestConfig;
```
**Describe the bug**
Running the above throws this error:
```
Running 1 test using 1 worker
✘ test/example.test.ts:4:1 › test (4ms)
1) test/example.test.ts:4:1 › test ==================================================================
TypeError: Cannot read property 'mode' of undefined
1 failed
test/example.test.ts:4:1 › test ===================================================================
```
This is caused by having `use,trace` as undefined in the playwright config.
This used to work with Playwright `v1.19`, and given the types of the option (`trace?: ...`), it should be allowed.
_After_ you figure out what the problem actually is, it is not a big deal as you can simply set the option to `off` instead of `undefined`. But it did take me a while to find that the trace option was causing it, as there is no stack trace in the error.
I got this right after upgrading to `v1.21`, and the reason the option is undefined is that I was setting it conditionally.
|
test
|
setting the use trace option to undefined causes typeerror cannot read property mode of undefined context playwright version operating system windows node js version browser all code snippet test file ts tests example test ts import test from playwright test test test async playwright config ts playwright config ts import playwrighttestconfig from playwright test const playwrighttestconfig playwrighttestconfig use trace undefined export default playwrighttestconfig describe the bug running the above throws this error running test using worker ✘ test example test ts › test test example test ts › test typeerror cannot read property mode of undefined failed test example test ts › test this is caused by having use trace as undefined in the playwright config this used to work with playwright and given the types of the option trace it should be allowed after you figure out what the problem actually is it is not a big deal as you can simply set the option to off instead of undefined but it did take me a while to find that the trace option was causing it as there is no stack trace in the error i got this right after upgrading to and the reason the option is undefined is that i was setting it conditionally
| 1
|
137,153
| 12,746,763,540
|
IssuesEvent
|
2020-06-26 16:32:57
|
Ameelio/letters-api
|
https://api.github.com/repos/Ameelio/letters-api
|
closed
|
Add example Request and example Response bodies to User endpoints
|
documentation
|
The following endpoints need example Request and/or Response bodies in the API Documentation Wiki page.
GET /api/user
GET /api/user/{id}
GET /api/users/contacts
GET /api/users/letters
GET /api/users/org
|
1.0
|
Add example Request and example Response bodies to User endpoints - The following endpoints need example Request and/or Response bodies in the API Documentation Wiki page.
GET /api/user
GET /api/user/{id}
GET /api/users/contacts
GET /api/users/letters
GET /api/users/org
|
non_test
|
add example request and example response bodies to user endpoints the following endpoints need example request and or response bodies in the api documentation wiki page get api user get api user id get api users contacts get api users letters get api users org
| 0
|
508,915
| 14,708,448,969
|
IssuesEvent
|
2021-01-04 23:44:11
|
ChrisNZL/Tallowmere2
|
https://api.github.com/repos/ChrisNZL/Tallowmere2
|
opened
|
Controllers: Add website link to help articles
|
⚠ priority+ 🎮 controllers 🖼 ui 🗨 text
|
Not being able to get a controller working is a frustrating experience.
Add details on the in-game Options > Input category to assist with troubleshooting controller issues.
|
1.0
|
Controllers: Add website link to help articles - Not being able to get a controller working is a frustrating experience.
Add details on the in-game Options > Input category to assist with troubleshooting controller issues.
|
non_test
|
controllers add website link to help articles not being able to get a controller working is a frustrating experience add details on the in game options input category to assist with troubleshooting controller issues
| 0
|
343,732
| 30,686,462,712
|
IssuesEvent
|
2023-07-26 12:41:22
|
wazuh/wazuh
|
https://api.github.com/repos/wazuh/wazuh
|
opened
|
Release 4.5.0 - Alpha 1 - Packages tests
|
type/test tracking level/task type/release
|
### Packages tests information
|||
| :-- | :-- |
| **Main release candidate issue** | #18058 |
| **Version** | 4.5.0 |
| **Release candidate** | Alpha 1 |
| **Tag** | https://github.com/wazuh/wazuh/tree/v4.5.0-alpha1 |
| **Previous packages metrics** | #17078 |
---
| Status | Test | Issue |
| :--: | :-- | :--: |
| :black_circle: | Installation | #18069 |
| :black_circle: | Upgrade | #18070 |
| :black_circle: | SELinux | #18072 |
| :black_circle: | Register | #18071 |
| :black_circle: | Service | #18073 |
| :black_circle: | Specific systems | #18074 |
| :black_circle: | Indexer/Dashboard | #18075 |
---
Status legend:
:black_circle: - Pending/In progress
:white_circle: - Skipped
:red_circle: - Rejected
:yellow_circle: - Ready to review
:green_circle: - Approved
---
## Auditor's validation
In order to close and proceed with the release or the next candidate version, the following auditors must give the green light to this RC.
- [ ] @davidjiglesias
- [ ] @teddytpc1
---
|
1.0
|
Release 4.5.0 - Alpha 1 - Packages tests - ### Packages tests information
|||
| :-- | :-- |
| **Main release candidate issue** | #18058 |
| **Version** | 4.5.0 |
| **Release candidate** | Alpha 1 |
| **Tag** | https://github.com/wazuh/wazuh/tree/v4.5.0-alpha1 |
| **Previous packages metrics** | #17078 |
---
| Status | Test | Issue |
| :--: | :-- | :--: |
| :black_circle: | Installation | #18069 |
| :black_circle: | Upgrade | #18070 |
| :black_circle: | SELinux | #18072 |
| :black_circle: | Register | #18071 |
| :black_circle: | Service | #18073 |
| :black_circle: | Specific systems | #18074 |
| :black_circle: | Indexer/Dashboard | #18075 |
---
Status legend:
:black_circle: - Pending/In progress
:white_circle: - Skipped
:red_circle: - Rejected
:yellow_circle: - Ready to review
:green_circle: - Approved
---
## Auditor's validation
In order to close and proceed with the release or the next candidate version, the following auditors must give the green light to this RC.
- [ ] @davidjiglesias
- [ ] @teddytpc1
---
|
test
|
release alpha packages tests packages tests information main release candidate issue version release candidate alpha tag previous packages metrics status test issue black circle installation black circle upgrade black circle selinux black circle register black circle service black circle specific systems black circle indexer dashboard status legend black circle pending in progress white circle skipped red circle rejected yellow circle ready to review green circle approved auditor s validation in order to close and proceed with the release or the next candidate version the following auditors must give the green light to this rc davidjiglesias
| 1
|
615,264
| 19,251,703,592
|
IssuesEvent
|
2021-12-09 06:27:58
|
kubesphere/console
|
https://api.github.com/repos/kubesphere/console
|
closed
|
Request to disable "Stop" button when Pipeline record is in "Not Run" status
|
area/devops kind/bug kind/need-to-verify priority/high
|
Request to disable "Stop" button when Pipeline record is in "Not Run" status, or backend would complain an error like below:
/area devops
/cc @kubesphere/sig-devops
/kind bug
/priority high
/milestone v3.2
|
1.0
|
Request to disable "Stop" button when Pipeline record is in "Not Run" status - Request to disable "Stop" button when Pipeline record is in "Not Run" status, or backend would complain an error like below:
/area devops
/cc @kubesphere/sig-devops
/kind bug
/priority high
/milestone v3.2
|
non_test
|
request to disable stop button when pipeline record is in not run status request to disable stop button when pipeline record is in not run status or backend would complain an error like below area devops cc kubesphere sig devops kind bug priority high milestone
| 0
|
148,723
| 19,542,171,642
|
IssuesEvent
|
2022-01-01 04:57:33
|
berviantoleo/msgraph-automate
|
https://api.github.com/repos/berviantoleo/msgraph-automate
|
opened
|
CVE-2019-0820 (High) detected in system.text.regularexpressions.4.1.0.nupkg
|
security vulnerability
|
## CVE-2019-0820 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>system.text.regularexpressions.4.1.0.nupkg</b></p></summary>
<p>Provides the System.Text.RegularExpressions.Regex class, an implementation of a regular expression e...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/system.text.regularexpressions.4.1.0.nupkg">https://api.nuget.org/packages/system.text.regularexpressions.4.1.0.nupkg</a></p>
<p>Path to dependency file: /MsGraphAutomate.Test/MsGraphAutomate.Test.csproj</p>
<p>Path to vulnerable library: /usr/share/dotnet/sdk/NuGetFallbackFolder/system.text.regularexpressions/4.1.0/system.text.regularexpressions.4.1.0.nupkg</p>
<p>
Dependency Hierarchy:
- microsoft.net.test.sdk.16.5.0.nupkg (Root Library)
- microsoft.testplatform.testhost.16.5.0.nupkg
- newtonsoft.json.9.0.1.nupkg
- :x: **system.text.regularexpressions.4.1.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/berviantoleo/msgraph-automate/commit/905871a74954855066980c8dc053d80c118a85a4">905871a74954855066980c8dc053d80c118a85a4</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 denial of service vulnerability exists when .NET Framework and .NET Core improperly process RegEx strings, aka '.NET Framework and .NET Core Denial of Service Vulnerability'. This CVE ID is unique from CVE-2019-0980, CVE-2019-0981.
<p>Publish Date: 2019-05-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-0820>CVE-2019-0820</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-cmhx-cq75-c4mj">https://github.com/advisories/GHSA-cmhx-cq75-c4mj</a></p>
<p>Release Date: 2020-08-24</p>
<p>Fix Resolution: System.Text.RegularExpressions - 4.3.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
|
True
|
CVE-2019-0820 (High) detected in system.text.regularexpressions.4.1.0.nupkg - ## CVE-2019-0820 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>system.text.regularexpressions.4.1.0.nupkg</b></p></summary>
<p>Provides the System.Text.RegularExpressions.Regex class, an implementation of a regular expression e...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/system.text.regularexpressions.4.1.0.nupkg">https://api.nuget.org/packages/system.text.regularexpressions.4.1.0.nupkg</a></p>
<p>Path to dependency file: /MsGraphAutomate.Test/MsGraphAutomate.Test.csproj</p>
<p>Path to vulnerable library: /usr/share/dotnet/sdk/NuGetFallbackFolder/system.text.regularexpressions/4.1.0/system.text.regularexpressions.4.1.0.nupkg</p>
<p>
Dependency Hierarchy:
- microsoft.net.test.sdk.16.5.0.nupkg (Root Library)
- microsoft.testplatform.testhost.16.5.0.nupkg
- newtonsoft.json.9.0.1.nupkg
- :x: **system.text.regularexpressions.4.1.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/berviantoleo/msgraph-automate/commit/905871a74954855066980c8dc053d80c118a85a4">905871a74954855066980c8dc053d80c118a85a4</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 denial of service vulnerability exists when .NET Framework and .NET Core improperly process RegEx strings, aka '.NET Framework and .NET Core Denial of Service Vulnerability'. This CVE ID is unique from CVE-2019-0980, CVE-2019-0981.
<p>Publish Date: 2019-05-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-0820>CVE-2019-0820</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-cmhx-cq75-c4mj">https://github.com/advisories/GHSA-cmhx-cq75-c4mj</a></p>
<p>Release Date: 2020-08-24</p>
<p>Fix Resolution: System.Text.RegularExpressions - 4.3.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 high detected in system text regularexpressions nupkg cve high severity vulnerability vulnerable library system text regularexpressions nupkg provides the system text regularexpressions regex class an implementation of a regular expression e library home page a href path to dependency file msgraphautomate test msgraphautomate test csproj path to vulnerable library usr share dotnet sdk nugetfallbackfolder system text regularexpressions system text regularexpressions nupkg dependency hierarchy microsoft net test sdk nupkg root library microsoft testplatform testhost nupkg newtonsoft json nupkg x system text regularexpressions nupkg vulnerable library found in head commit a href found in base branch main vulnerability details a denial of service vulnerability exists when net framework and net core improperly process regex strings aka net framework and net core denial of service vulnerability this cve id is unique from cve cve publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution system text regularexpressions step up your open source security game with whitesource
| 0
|
382,800
| 11,320,085,777
|
IssuesEvent
|
2020-01-21 02:33:14
|
C4C-TC-MSS/Sprint_Demo
|
https://api.github.com/repos/C4C-TC-MSS/Sprint_Demo
|
closed
|
Add next steps content at the end of the app
|
enhancement high priority
|
Add content around what potential applicants need to do next after receiving certificate information.
|
1.0
|
Add next steps content at the end of the app - Add content around what potential applicants need to do next after receiving certificate information.
|
non_test
|
add next steps content at the end of the app add content around what potential applicants need to do next after receiving certificate information
| 0
|
41,350
| 8,960,739,377
|
IssuesEvent
|
2019-01-28 07:19:40
|
Microsoft/vscode-python
|
https://api.github.com/repos/Microsoft/vscode-python
|
closed
|
The fallback default settings (in PythonSettings.update) are out of sync with package.json.
|
internal contributor needs PR type-code health
|
In `PythonSettings.update()` a bunch of default values are set if expected data is missing. However, there doesn't appear to be any strict relationship between those defaults and the ones in `package.json`. There isn't any explicit dependency and there aren't any tests that verify equivalency (for defaults).
Consequently, the two sets of defaults are out of sync. I noticed this specifically (while working on PR #4094) with [the`python.linting.flake8Path` setting](https://github.com/Microsoft/vscode-python/blob/57fca15b4e8e9db64ebd2f9b4a84690fa43971fb/src/client/common/configSettings.ts#L200), where `PythonSettings.update()` uses a default of "flake", while `package.json` uses "flake8". Keep in mind that, if I remember correctly, there used to be a `flake` tool that was superseded by `flake8` a while back. In this case using the value of "flake" is problematic because it doesn't match up with the linter machinery (which depends on `flake8`), leading to bad behavior (e.g. with the linter's `NotInstalledErrorHandler`).
Notably, the defaults (at least for linting) in `PythonSettings.update()` don't ever seem to actually be applied (so the code might just be dead weight). This is likely because the initial configuration is reliable and complete, as is the system for coordinating settings between VSCode and the extension. So none of the settings, including `python.linting' are ever missing (ergo the defaults in `PythonSettings.update()` are never applied).
Regardless, here are key questions which remain unclear (and unvalidated/untested?) regarding `PythonSettings.update()`:
* does it handle defaults for *all* config values (i.e. is it missing any)?
* does it handle defaults for settings that no longer exist?
* do the defaults there match those in `package.json`?
* do we even need the defaults-related code in `update()` (i.e. can we rip it out)?
My expectation is that the two should be in sync and that defaults-handling should not be ripped out of `PythonSettings.update()`. So the following would need to be done:
1. add unit tests verifying that the defaults in `PythonSettings` match those in 'package.json`
2. manually update `PythonSettings` to be in sync with `package.json` (we *could* programmatically derive the defaults from `package.json` but there's little churn in the settings and the unit tests will ensure `PythonSettings` is in sync)
|
1.0
|
The fallback default settings (in PythonSettings.update) are out of sync with package.json. - In `PythonSettings.update()` a bunch of default values are set if expected data is missing. However, there doesn't appear to be any strict relationship between those defaults and the ones in `package.json`. There isn't any explicit dependency and there aren't any tests that verify equivalency (for defaults).
Consequently, the two sets of defaults are out of sync. I noticed this specifically (while working on PR #4094) with [the`python.linting.flake8Path` setting](https://github.com/Microsoft/vscode-python/blob/57fca15b4e8e9db64ebd2f9b4a84690fa43971fb/src/client/common/configSettings.ts#L200), where `PythonSettings.update()` uses a default of "flake", while `package.json` uses "flake8". Keep in mind that, if I remember correctly, there used to be a `flake` tool that was superseded by `flake8` a while back. In this case using the value of "flake" is problematic because it doesn't match up with the linter machinery (which depends on `flake8`), leading to bad behavior (e.g. with the linter's `NotInstalledErrorHandler`).
Notably, the defaults (at least for linting) in `PythonSettings.update()` don't ever seem to actually be applied (so the code might just be dead weight). This is likely because the initial configuration is reliable and complete, as is the system for coordinating settings between VSCode and the extension. So none of the settings, including `python.linting' are ever missing (ergo the defaults in `PythonSettings.update()` are never applied).
Regardless, here are key questions which remain unclear (and unvalidated/untested?) regarding `PythonSettings.update()`:
* does it handle defaults for *all* config values (i.e. is it missing any)?
* does it handle defaults for settings that no longer exist?
* do the defaults there match those in `package.json`?
* do we even need the defaults-related code in `update()` (i.e. can we rip it out)?
My expectation is that the two should be in sync and that defaults-handling should not be ripped out of `PythonSettings.update()`. So the following would need to be done:
1. add unit tests verifying that the defaults in `PythonSettings` match those in 'package.json`
2. manually update `PythonSettings` to be in sync with `package.json` (we *could* programmatically derive the defaults from `package.json` but there's little churn in the settings and the unit tests will ensure `PythonSettings` is in sync)
|
non_test
|
the fallback default settings in pythonsettings update are out of sync with package json in pythonsettings update a bunch of default values are set if expected data is missing however there doesn t appear to be any strict relationship between those defaults and the ones in package json there isn t any explicit dependency and there aren t any tests that verify equivalency for defaults consequently the two sets of defaults are out of sync i noticed this specifically while working on pr with where pythonsettings update uses a default of flake while package json uses keep in mind that if i remember correctly there used to be a flake tool that was superseded by a while back in this case using the value of flake is problematic because it doesn t match up with the linter machinery which depends on leading to bad behavior e g with the linter s notinstallederrorhandler notably the defaults at least for linting in pythonsettings update don t ever seem to actually be applied so the code might just be dead weight this is likely because the initial configuration is reliable and complete as is the system for coordinating settings between vscode and the extension so none of the settings including python linting are ever missing ergo the defaults in pythonsettings update are never applied regardless here are key questions which remain unclear and unvalidated untested regarding pythonsettings update does it handle defaults for all config values i e is it missing any does it handle defaults for settings that no longer exist do the defaults there match those in package json do we even need the defaults related code in update i e can we rip it out my expectation is that the two should be in sync and that defaults handling should not be ripped out of pythonsettings update so the following would need to be done add unit tests verifying that the defaults in pythonsettings match those in package json manually update pythonsettings to be in sync with package json we could programmatically derive the defaults from package json but there s little churn in the settings and the unit tests will ensure pythonsettings is in sync
| 0
|
214,789
| 16,612,053,241
|
IssuesEvent
|
2021-06-02 12:45:09
|
microsoft/vscode
|
https://api.github.com/repos/microsoft/vscode
|
closed
|
Test: terminal icon extension API
|
testplan-item
|
Refs #120538
- [x] macOS @lramos15
- [x] linux @alexdima
- [x] windows @bamurtaugh
Complexity: 3
Authors: @meganrogge, @tyriar
[Create Issue](https://github.com/microsoft/vscode/issues/new?body=Testing+%23124398%0A%0A)
---
With proposed API [enabled](https://code.visualstudio.com/api/advanced-topics/using-proposed-api), use the extension-terminal-sample to test that you can:
- set terminal icons using all of the argument types, with and without providing a `pty` to `createTerminal`:
`ThemeIcon | URI | { light: URI; dark: URI };`
- view the icons in the TerminalQuickPick with `Switch Active Terminal`
- view the icons in the terminal tabs list
- view the icon update as you switch active terminals in the single tab terminal view action item
- anything else you can think of
|
1.0
|
Test: terminal icon extension API - Refs #120538
- [x] macOS @lramos15
- [x] linux @alexdima
- [x] windows @bamurtaugh
Complexity: 3
Authors: @meganrogge, @tyriar
[Create Issue](https://github.com/microsoft/vscode/issues/new?body=Testing+%23124398%0A%0A)
---
With proposed API [enabled](https://code.visualstudio.com/api/advanced-topics/using-proposed-api), use the extension-terminal-sample to test that you can:
- set terminal icons using all of the argument types, with and without providing a `pty` to `createTerminal`:
`ThemeIcon | URI | { light: URI; dark: URI };`
- view the icons in the TerminalQuickPick with `Switch Active Terminal`
- view the icons in the terminal tabs list
- view the icon update as you switch active terminals in the single tab terminal view action item
- anything else you can think of
|
test
|
test terminal icon extension api refs macos linux alexdima windows bamurtaugh complexity authors meganrogge tyriar with proposed api use the extension terminal sample to test that you can set terminal icons using all of the argument types with and without providing a pty to createterminal themeicon uri light uri dark uri view the icons in the terminalquickpick with switch active terminal view the icons in the terminal tabs list view the icon update as you switch active terminals in the single tab terminal view action item anything else you can think of
| 1
|
448,214
| 31,774,497,893
|
IssuesEvent
|
2023-09-12 13:42:34
|
cloudnative-pg/cloudnative-pg
|
https://api.github.com/repos/cloudnative-pg/cloudnative-pg
|
opened
|
Organise the documentation left bar in sections
|
documentation :book:
|
The documentation of CloudNativePG has grown over time in scar tissue mode. The left bar now looks like an infinite list of sections. While we find better ways to improve the overall content (maybe have tutorials, references, admin guides formats), let's organise the left bar in sections.
|
1.0
|
Organise the documentation left bar in sections - The documentation of CloudNativePG has grown over time in scar tissue mode. The left bar now looks like an infinite list of sections. While we find better ways to improve the overall content (maybe have tutorials, references, admin guides formats), let's organise the left bar in sections.
|
non_test
|
organise the documentation left bar in sections the documentation of cloudnativepg has grown over time in scar tissue mode the left bar now looks like an infinite list of sections while we find better ways to improve the overall content maybe have tutorials references admin guides formats let s organise the left bar in sections
| 0
|
288,587
| 24,917,760,448
|
IssuesEvent
|
2022-10-30 15:59:51
|
dromara/hertzbeat
|
https://api.github.com/repos/dromara/hertzbeat
|
closed
|
[Task] <Unit Test Case> manager/dao/NoticeRuleDaoTest.java
|
status: volunteer wanted unit test case
|
### Description
Help us impl Unit Test For [manager/dao/NoticeRuleDaoTest.java](https://github.com/dromara/hertzbeat/blob/master/manager/src/test/java/com/usthe/manager/dao/NoticeRuleDaoTest.java)
You can learn and refer to the previous test cases impl.
1. controller example unit case: https://github.com/dromara/hertzbeat/blob/master/manager/src/test/java/com/usthe/manager/controller/AccountControllerTest.java
2. service example unit case: https://github.com/dromara/hertzbeat/blob/master/manager/src/test/java/com/usthe/manager/service/TagServiceTest.java
3. jpa sql dao example unit case: https://github.com/dromara/hertzbeat/blob/master/manager/src/test/java/com/usthe/manager/dao/MonitorDaoTest.java
### Task List
- [ ] Impl Unit Test For [manager/dao/NoticeRuleDaoTest.java](https://github.com/dromara/hertzbeat/blob/master/manager/src/test/java/com/usthe/manager/dao/NoticeRuleDaoTest.java)
|
1.0
|
[Task] <Unit Test Case> manager/dao/NoticeRuleDaoTest.java - ### Description
Help us impl Unit Test For [manager/dao/NoticeRuleDaoTest.java](https://github.com/dromara/hertzbeat/blob/master/manager/src/test/java/com/usthe/manager/dao/NoticeRuleDaoTest.java)
You can learn and refer to the previous test cases impl.
1. controller example unit case: https://github.com/dromara/hertzbeat/blob/master/manager/src/test/java/com/usthe/manager/controller/AccountControllerTest.java
2. service example unit case: https://github.com/dromara/hertzbeat/blob/master/manager/src/test/java/com/usthe/manager/service/TagServiceTest.java
3. jpa sql dao example unit case: https://github.com/dromara/hertzbeat/blob/master/manager/src/test/java/com/usthe/manager/dao/MonitorDaoTest.java
### Task List
- [ ] Impl Unit Test For [manager/dao/NoticeRuleDaoTest.java](https://github.com/dromara/hertzbeat/blob/master/manager/src/test/java/com/usthe/manager/dao/NoticeRuleDaoTest.java)
|
test
|
manager dao noticeruledaotest java description help us impl unit test for you can learn and refer to the previous test cases impl controller example unit case service example unit case jpa sql dao example unit case task list impl unit test for
| 1
|
170,284
| 13,182,421,426
|
IssuesEvent
|
2020-08-12 15:45:52
|
status-im/status-react
|
https://api.github.com/repos/status-im/status-react
|
opened
|
No redirect to 1-1 chat in tapping on push notification
|
android bug e2e test blocker high-priority push-notifications
|
# Bug Report
## Problem
Currently on tapping on push notification user is not redirected to 1-1 chat.
Issue is not reproducible on 1.5.
Blocks test `test_push_notification_1_1_chat`
#### Expected behavior
User will be redirected to 1-1 chat
#### Actual behavior
no redirect
### Reproduction
[comment]: # (Describe how we can replicate the bug step by step.)
- Device 1: Open Status
- Device 1: Enable notifications
- Device 1: Put app to background
- Device 2: send message to 1-1 chat to Device 2
- Device 1: Tap on push notification
### Additional Information
- Status version: nightly 12/08/20
- Operating System: Android
|
1.0
|
No redirect to 1-1 chat in tapping on push notification - # Bug Report
## Problem
Currently on tapping on push notification user is not redirected to 1-1 chat.
Issue is not reproducible on 1.5.
Blocks test `test_push_notification_1_1_chat`
#### Expected behavior
User will be redirected to 1-1 chat
#### Actual behavior
no redirect
### Reproduction
[comment]: # (Describe how we can replicate the bug step by step.)
- Device 1: Open Status
- Device 1: Enable notifications
- Device 1: Put app to background
- Device 2: send message to 1-1 chat to Device 2
- Device 1: Tap on push notification
### Additional Information
- Status version: nightly 12/08/20
- Operating System: Android
|
test
|
no redirect to chat in tapping on push notification bug report problem currently on tapping on push notification user is not redirected to chat issue is not reproducible on blocks test test push notification chat expected behavior user will be redirected to chat actual behavior no redirect reproduction describe how we can replicate the bug step by step device open status device enable notifications device put app to background device send message to chat to device device tap on push notification additional information status version nightly operating system android
| 1
|
231,508
| 18,771,849,893
|
IssuesEvent
|
2021-11-07 00:37:35
|
elastic/kibana
|
https://api.github.com/repos/elastic/kibana
|
reopened
|
Failing test: Jest Tests.x-pack/plugins/apm/public/components/app/service_inventory/service_list - ServiceList with ML data renders the health column
|
Team:apm [zube]: Done failed-test
|
A test failed on a tracked branch
```
Error: thrown: "Exceeded timeout of 5000 ms for a test.
Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."
at /opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/x-pack/plugins/apm/public/components/app/service_inventory/service_list/service_list.test.tsx:192:5
at _dispatchDescribe (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/index.js:67:26)
at describe (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/index.js:30:5)
at /opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/x-pack/plugins/apm/public/components/app/service_inventory/service_list/service_list.test.tsx:191:3
at _dispatchDescribe (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/index.js:67:26)
at describe (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/index.js:30:5)
at Object.<anonymous> (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/x-pack/plugins/apm/public/components/app/service_inventory/service_list/service_list.test.tsx:18:1)
at Runtime._execModule (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-runtime/build/index.js:1299:24)
at Runtime._loadModule (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-runtime/build/index.js:898:12)
at Runtime.requireModule (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-runtime/build/index.js:746:10)
at jestAdapter (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:106:13)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at runTestInternal (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-runner/build/runTest.js:380:16)
at runTest (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-runner/build/runTest.js:472:34)
at Object.worker (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-runner/build/testWorker.js:133:12)
```
First failure: [CI Build - master](https://buildkite.com/elastic/kibana-hourly/builds/2031#59212c9d-07db-4d5b-b96e-781094820bba)
<!-- kibanaCiData = {"failed-test":{"test.class":"Jest Tests.x-pack/plugins/apm/public/components/app/service_inventory/service_list","test.name":"ServiceList with ML data renders the health column","test.failCount":7}} -->
|
1.0
|
Failing test: Jest Tests.x-pack/plugins/apm/public/components/app/service_inventory/service_list - ServiceList with ML data renders the health column - A test failed on a tracked branch
```
Error: thrown: "Exceeded timeout of 5000 ms for a test.
Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."
at /opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/x-pack/plugins/apm/public/components/app/service_inventory/service_list/service_list.test.tsx:192:5
at _dispatchDescribe (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/index.js:67:26)
at describe (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/index.js:30:5)
at /opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/x-pack/plugins/apm/public/components/app/service_inventory/service_list/service_list.test.tsx:191:3
at _dispatchDescribe (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/index.js:67:26)
at describe (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/index.js:30:5)
at Object.<anonymous> (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/x-pack/plugins/apm/public/components/app/service_inventory/service_list/service_list.test.tsx:18:1)
at Runtime._execModule (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-runtime/build/index.js:1299:24)
at Runtime._loadModule (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-runtime/build/index.js:898:12)
at Runtime.requireModule (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-runtime/build/index.js:746:10)
at jestAdapter (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:106:13)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at runTestInternal (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-runner/build/runTest.js:380:16)
at runTest (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-runner/build/runTest.js:472:34)
at Object.worker (/opt/local-ssd/buildkite/builds/kb-c2-16-d0e9773327ff19f5/elastic/kibana-hourly/kibana/node_modules/jest-runner/build/testWorker.js:133:12)
```
First failure: [CI Build - master](https://buildkite.com/elastic/kibana-hourly/builds/2031#59212c9d-07db-4d5b-b96e-781094820bba)
<!-- kibanaCiData = {"failed-test":{"test.class":"Jest Tests.x-pack/plugins/apm/public/components/app/service_inventory/service_list","test.name":"ServiceList with ML data renders the health column","test.failCount":7}} -->
|
test
|
failing test jest tests x pack plugins apm public components app service inventory service list servicelist with ml data renders the health column a test failed on a tracked branch error thrown exceeded timeout of ms for a test use jest settimeout newtimeout to increase the timeout value if this is a long running test at opt local ssd buildkite builds kb elastic kibana hourly kibana x pack plugins apm public components app service inventory service list service list test tsx at dispatchdescribe opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest circus build index js at describe opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest circus build index js at opt local ssd buildkite builds kb elastic kibana hourly kibana x pack plugins apm public components app service inventory service list service list test tsx at dispatchdescribe opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest circus build index js at describe opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest circus build index js at object opt local ssd buildkite builds kb elastic kibana hourly kibana x pack plugins apm public components app service inventory service list service list test tsx at runtime execmodule opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest runtime build index js at runtime loadmodule opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest runtime build index js at runtime requiremodule opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest runtime build index js at jestadapter opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest circus build legacy code todo rewrite jestadapter js at processticksandrejections node internal process task queues at runtestinternal opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest runner build runtest js at runtest opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest runner build runtest js at object worker opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest runner build testworker js first failure
| 1
|
31,945
| 15,159,360,523
|
IssuesEvent
|
2021-02-12 04:02:07
|
microsoft/onnxruntime
|
https://api.github.com/repos/microsoft/onnxruntime
|
closed
|
Model loading is too slow with onnxruntime-gpu
|
ep:CUDA type:performance
|
Using the cpu version, I have no problem. Loading onnx models using "InferenceSession" with onnxruntime-gpu takes >102 seconds for the first model. If we load more than one models, the others take no time at all; we only wait for the first call of "onnxruntime.InferenceSession(onnx_fn)" I have tried with yolov3, yolov3-tiny, yolov4, yolov5, ssd_mobilenet.
**System information**
- OS: Windows 10 x64
- ONNX Runtime installed with pip using: "pip3 install onnxruntime-gpu"
- ONNX Runtime version: onnxruntime-gpu==1.5.2
- Python version: 3.7.9
- Using latest version of pycharm
- CUDA 10.2 and cuDNN 8.0.3
- GPU: GeForce RTX 3070 8GB
- CPU/Ram/hard drive: AMD Ryzen 7 3700x / 64GB / ~3000mb/sec io capable SSD
Is this normal? Should I try other versions of CUDA or cuDNN?
|
True
|
Model loading is too slow with onnxruntime-gpu - Using the cpu version, I have no problem. Loading onnx models using "InferenceSession" with onnxruntime-gpu takes >102 seconds for the first model. If we load more than one models, the others take no time at all; we only wait for the first call of "onnxruntime.InferenceSession(onnx_fn)" I have tried with yolov3, yolov3-tiny, yolov4, yolov5, ssd_mobilenet.
**System information**
- OS: Windows 10 x64
- ONNX Runtime installed with pip using: "pip3 install onnxruntime-gpu"
- ONNX Runtime version: onnxruntime-gpu==1.5.2
- Python version: 3.7.9
- Using latest version of pycharm
- CUDA 10.2 and cuDNN 8.0.3
- GPU: GeForce RTX 3070 8GB
- CPU/Ram/hard drive: AMD Ryzen 7 3700x / 64GB / ~3000mb/sec io capable SSD
Is this normal? Should I try other versions of CUDA or cuDNN?
|
non_test
|
model loading is too slow with onnxruntime gpu using the cpu version i have no problem loading onnx models using inferencesession with onnxruntime gpu takes seconds for the first model if we load more than one models the others take no time at all we only wait for the first call of onnxruntime inferencesession onnx fn i have tried with tiny ssd mobilenet system information os windows onnx runtime installed with pip using install onnxruntime gpu onnx runtime version onnxruntime gpu python version using latest version of pycharm cuda and cudnn gpu geforce rtx cpu ram hard drive amd ryzen sec io capable ssd is this normal should i try other versions of cuda or cudnn
| 0
|
246,343
| 18,842,789,803
|
IssuesEvent
|
2021-11-11 11:34:46
|
alphagov/govuk-prototype-kit
|
https://api.github.com/repos/alphagov/govuk-prototype-kit
|
closed
|
Create release notes for GOV.UK Prototype Kit v.10.0.0 (breaking changes release)
|
documentation breaking change 2i
|
## What
Create release notes for GOV.UK Prototype Kit v10.0.0 (breaking changes release).
## Why
Users will no longer be able to run the Kit on Node.js v10, so we're advising them to update to Node.js v16.
We may also want to tell users about another breaking change, which would involve [updating the Notify client](https://github.com/alphagov/govuk-prototype-kit/pull/925).
## Who needs to work on this
Content Designer, Developer
## Who needs to review this
Another Developer, also a Technical Writer (for 2i)
## Done when
- [x] Kit team decides what's going into the release
- [x] Release notes drafted in full
- [x] Developer reviews and approves draft
- [x] Draft passes 2i
- [x] Draft published
|
1.0
|
Create release notes for GOV.UK Prototype Kit v.10.0.0 (breaking changes release) - ## What
Create release notes for GOV.UK Prototype Kit v10.0.0 (breaking changes release).
## Why
Users will no longer be able to run the Kit on Node.js v10, so we're advising them to update to Node.js v16.
We may also want to tell users about another breaking change, which would involve [updating the Notify client](https://github.com/alphagov/govuk-prototype-kit/pull/925).
## Who needs to work on this
Content Designer, Developer
## Who needs to review this
Another Developer, also a Technical Writer (for 2i)
## Done when
- [x] Kit team decides what's going into the release
- [x] Release notes drafted in full
- [x] Developer reviews and approves draft
- [x] Draft passes 2i
- [x] Draft published
|
non_test
|
create release notes for gov uk prototype kit v breaking changes release what create release notes for gov uk prototype kit breaking changes release why users will no longer be able to run the kit on node js so we re advising them to update to node js we may also want to tell users about another breaking change which would involve who needs to work on this content designer developer who needs to review this another developer also a technical writer for done when kit team decides what s going into the release release notes drafted in full developer reviews and approves draft draft passes draft published
| 0
|
4,166
| 2,712,265,450
|
IssuesEvent
|
2015-04-09 12:47:42
|
molgenis/molgenis
|
https://api.github.com/repos/molgenis/molgenis
|
closed
|
OMIM HPO annotator broken
|
bug data-annotators dataexplorer release test v15.04
|
try running the omim hpo annotator:
Message:org.molgenis.data.UnknownAttributeException: OMIM_Causal_ID
|
1.0
|
OMIM HPO annotator broken - try running the omim hpo annotator:
Message:org.molgenis.data.UnknownAttributeException: OMIM_Causal_ID
|
test
|
omim hpo annotator broken try running the omim hpo annotator message org molgenis data unknownattributeexception omim causal id
| 1
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.