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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
128,224 | 5,051,134,850 | IssuesEvent | 2016-12-20 20:54:55 | mozilla/normandy | https://api.github.com/repos/mozilla/normandy | closed | Remove uses of Jetpack from system add-on | priority: P1 status: ready for work | Jetpack add-ons are not suitable for system add-ons. We should stop being a Jetpack add-on. This covers:
* Removing any usage of an ambient require (such as provided by Jetpack)
* Changing all modules to do imports/exports using the `Cu.import` machinery
* Get the tests either passing in mozilla-central tree, or out of it, whichever is actually possible
Note that this is currently happening in an [external repo](https://github.com/mozilla/normandy-addon), since #353 is unresolved. | 1.0 | Remove uses of Jetpack from system add-on - Jetpack add-ons are not suitable for system add-ons. We should stop being a Jetpack add-on. This covers:
* Removing any usage of an ambient require (such as provided by Jetpack)
* Changing all modules to do imports/exports using the `Cu.import` machinery
* Get the tests either passing in mozilla-central tree, or out of it, whichever is actually possible
Note that this is currently happening in an [external repo](https://github.com/mozilla/normandy-addon), since #353 is unresolved. | non_test | remove uses of jetpack from system add on jetpack add ons are not suitable for system add ons we should stop being a jetpack add on this covers removing any usage of an ambient require such as provided by jetpack changing all modules to do imports exports using the cu import machinery get the tests either passing in mozilla central tree or out of it whichever is actually possible note that this is currently happening in an since is unresolved | 0 |
88,758 | 8,176,781,149 | IssuesEvent | 2018-08-28 08:40:52 | mantidproject/mantid | https://api.github.com/repos/mantidproject/mantid | opened | Muon - Unit Test the Thread Model | Component: Muon Quality: Unit Tests | The `thread_model` class which underpins the background thread used for loading Muon data needs some unit tests to ensure its continued stability in the GUI.
This issue will attempt to unit test the multi-threading behavior in a roust way.
| 1.0 | Muon - Unit Test the Thread Model - The `thread_model` class which underpins the background thread used for loading Muon data needs some unit tests to ensure its continued stability in the GUI.
This issue will attempt to unit test the multi-threading behavior in a roust way.
| test | muon unit test the thread model the thread model class which underpins the background thread used for loading muon data needs some unit tests to ensure its continued stability in the gui this issue will attempt to unit test the multi threading behavior in a roust way | 1 |
18,209 | 3,035,168,303 | IssuesEvent | 2015-08-06 00:26:33 | mkpanchal/phppi | https://api.github.com/repos/mkpanchal/phppi | closed | [Request] White List | auto-migrated Priority-Medium Type-Defect | ```
In addition to the folder_blacklist option it would be helpful to have a
folder_whitelist option. The gallery_folder option is currently scanning all
subolders. With a whitelist option this could be restricted to a selection of
folders. When only a few folders should be displayed in a gallery with a lot of
subfolders it would be easier to configure a white list instead of adding lot
of foldernames to the blacklist.
```
Original issue reported on code.google.com by `achim.gy...@googlemail.com` on 21 Nov 2013 at 9:39 | 1.0 | [Request] White List - ```
In addition to the folder_blacklist option it would be helpful to have a
folder_whitelist option. The gallery_folder option is currently scanning all
subolders. With a whitelist option this could be restricted to a selection of
folders. When only a few folders should be displayed in a gallery with a lot of
subfolders it would be easier to configure a white list instead of adding lot
of foldernames to the blacklist.
```
Original issue reported on code.google.com by `achim.gy...@googlemail.com` on 21 Nov 2013 at 9:39 | non_test | white list in addition to the folder blacklist option it would be helpful to have a folder whitelist option the gallery folder option is currently scanning all subolders with a whitelist option this could be restricted to a selection of folders when only a few folders should be displayed in a gallery with a lot of subfolders it would be easier to configure a white list instead of adding lot of foldernames to the blacklist original issue reported on code google com by achim gy googlemail com on nov at | 0 |
278,312 | 24,145,022,671 | IssuesEvent | 2022-09-21 17:56:28 | b-nagaj/Morel | https://api.github.com/repos/b-nagaj/Morel | closed | Add Unit Testing for the Setup Class | Testing | Making use of the BOOST automated test suite, add unit testing for the functions inside of the _Setup_ class. Functions such as:
- _Setup_ constructor
- _ValidatePaths()_
- _Write()_ | 1.0 | Add Unit Testing for the Setup Class - Making use of the BOOST automated test suite, add unit testing for the functions inside of the _Setup_ class. Functions such as:
- _Setup_ constructor
- _ValidatePaths()_
- _Write()_ | test | add unit testing for the setup class making use of the boost automated test suite add unit testing for the functions inside of the setup class functions such as setup constructor validatepaths write | 1 |
91,535 | 8,307,484,705 | IssuesEvent | 2018-09-23 09:54:14 | yiisoft/yii2-bootstrap4 | https://api.github.com/repos/yiisoft/yii2-bootstrap4 | closed | Resetting widget counter has no effect | status:to be verified type:test | I'm currently trying to fix the tests and it seems that resetting the widget counter has no effect. Taking `ToggleButtonGroupTest` as example, neither `\yii\base\Widget::$counter = 0;` nor `ToggleButtonGroup::$counter = 0;` change the actual result of the test (see below).
The big problem is that even if I would test against an incremented counter ID, tests would break instantly if the order of the tests change.
Does someone of the core team have an idea why a public static property behaves like this?
### What steps will reproduce the problem?
Execute the tests and look for the ID's in `ToggleButtonGroupTest::testRadio` (second test in the class)
### What's expected?
Two inputs with the ID's `i1` and `i2`
### What do you get instead?
ID's `i3` and `i4`
### Additional info
| Q | A
| ---------------- | ---
| Yii version | ~2.0
| PHP version | 7.1
| Operating system | Win10x64
| 1.0 | Resetting widget counter has no effect - I'm currently trying to fix the tests and it seems that resetting the widget counter has no effect. Taking `ToggleButtonGroupTest` as example, neither `\yii\base\Widget::$counter = 0;` nor `ToggleButtonGroup::$counter = 0;` change the actual result of the test (see below).
The big problem is that even if I would test against an incremented counter ID, tests would break instantly if the order of the tests change.
Does someone of the core team have an idea why a public static property behaves like this?
### What steps will reproduce the problem?
Execute the tests and look for the ID's in `ToggleButtonGroupTest::testRadio` (second test in the class)
### What's expected?
Two inputs with the ID's `i1` and `i2`
### What do you get instead?
ID's `i3` and `i4`
### Additional info
| Q | A
| ---------------- | ---
| Yii version | ~2.0
| PHP version | 7.1
| Operating system | Win10x64
| test | resetting widget counter has no effect i m currently trying to fix the tests and it seems that resetting the widget counter has no effect taking togglebuttongrouptest as example neither yii base widget counter nor togglebuttongroup counter change the actual result of the test see below the big problem is that even if i would test against an incremented counter id tests would break instantly if the order of the tests change does someone of the core team have an idea why a public static property behaves like this what steps will reproduce the problem execute the tests and look for the id s in togglebuttongrouptest testradio second test in the class what s expected two inputs with the id s and what do you get instead id s and additional info q a yii version php version operating system | 1 |
218,541 | 16,996,092,863 | IssuesEvent | 2021-07-01 06:39:34 | LongOddCode/lerna-test | https://api.github.com/repos/LongOddCode/lerna-test | opened | E2E Tests failed at Thursday, July 1st 2021, 6AM | e2e-test | E2E Tests failed, see https://github.com/LongOddCode/lerna-test/actions/runs/989035281
**Log:**
3758d91 Thu Jul 1 14:39:13 2021 +0800 - ci: add unit test coverage checker (LongOddCode) 83db021 Thu Jul 1 14:37:43 2021 +0800 - ci: add unit test coverage checker (LongOddCode) e4f7db7 Thu Jul 1 14:15:09 2021 +0800 - Merge pull request #9 from LongOddCode/t-yiqingzhao/test (Yiqing Zhao)
| 1.0 | E2E Tests failed at Thursday, July 1st 2021, 6AM - E2E Tests failed, see https://github.com/LongOddCode/lerna-test/actions/runs/989035281
**Log:**
3758d91 Thu Jul 1 14:39:13 2021 +0800 - ci: add unit test coverage checker (LongOddCode) 83db021 Thu Jul 1 14:37:43 2021 +0800 - ci: add unit test coverage checker (LongOddCode) e4f7db7 Thu Jul 1 14:15:09 2021 +0800 - Merge pull request #9 from LongOddCode/t-yiqingzhao/test (Yiqing Zhao)
| test | tests failed at thursday july tests failed see log thu jul ci add unit test coverage checker longoddcode thu jul ci add unit test coverage checker longoddcode thu jul merge pull request from longoddcode t yiqingzhao test yiqing zhao | 1 |
376,097 | 26,185,677,548 | IssuesEvent | 2023-01-02 23:35:43 | paperless-ngx/paperless-ngx | https://api.github.com/repos/paperless-ngx/paperless-ngx | closed | [BUG] [DOCS] PAPERLESS_URL should only be a domain name, don't set full URL | documentation | ### Description
I encountered a problem when migrating from paperless-ng to ngx.
Background: my -ng install runs from a subpath: https://example.com/scan/ , behind a reverse proxy.
Problem (1): https://docs.paperless-ngx.com/setup/#migrating-from-paperless-ng doesn't tell you to set the new envvar, "PAPERLESS_URL". So although I could login and view docs just fine after taking the steps documented in https://docs.paperless-ngx.com/setup/#migrating-from-paperless-ng , some operations were failing because of a security check.
Problem (2): I set the URL to https://example.com/scan , but loading the web interface just returns a completely blank page - no error message, nothing. Thankfully, shell output told me that "(corsheaders.E014) Origin 'https://example.com/scan' in CORS_ALLOWED_ORIGINS should not have path"
The fix was to change "PAPERLESS_URL" so it's just a domain (https:///example.com), with no further path elements (i.e. it's not the actual install URL)
I therefore suggest at least updating the documentation to specify that not only should a trailing slash be omitted, but in fact *only* the domain should be included, not any other path element. Or the code could strip it, when it's going to be a problem.
Perhaps "PAPERLESS_DOMAIN" would make for a better variable name, but that's probably going to be a breaking change for not much gain.
### Steps to reproduce
Set PAPERLESS_URL to https://example.com/scan , but loading the web interface just returns a completely blank page - no error message, nothing.
### Webserver logs
```bash
"(corsheaders.E014) Origin 'https://example.com/scan' in CORS_ALLOWED_ORIGINS should not have path"
```
### Browser logs
_No response_
### Paperless-ngx version
1.11.3
### Host OS
Ubuntu
### Installation method
Docker - official image
### Browser
Firefox
### Configuration changes
Set PAPERLESS_URL to https://example.com/scan
### Other
_No response_ | 1.0 | [BUG] [DOCS] PAPERLESS_URL should only be a domain name, don't set full URL - ### Description
I encountered a problem when migrating from paperless-ng to ngx.
Background: my -ng install runs from a subpath: https://example.com/scan/ , behind a reverse proxy.
Problem (1): https://docs.paperless-ngx.com/setup/#migrating-from-paperless-ng doesn't tell you to set the new envvar, "PAPERLESS_URL". So although I could login and view docs just fine after taking the steps documented in https://docs.paperless-ngx.com/setup/#migrating-from-paperless-ng , some operations were failing because of a security check.
Problem (2): I set the URL to https://example.com/scan , but loading the web interface just returns a completely blank page - no error message, nothing. Thankfully, shell output told me that "(corsheaders.E014) Origin 'https://example.com/scan' in CORS_ALLOWED_ORIGINS should not have path"
The fix was to change "PAPERLESS_URL" so it's just a domain (https:///example.com), with no further path elements (i.e. it's not the actual install URL)
I therefore suggest at least updating the documentation to specify that not only should a trailing slash be omitted, but in fact *only* the domain should be included, not any other path element. Or the code could strip it, when it's going to be a problem.
Perhaps "PAPERLESS_DOMAIN" would make for a better variable name, but that's probably going to be a breaking change for not much gain.
### Steps to reproduce
Set PAPERLESS_URL to https://example.com/scan , but loading the web interface just returns a completely blank page - no error message, nothing.
### Webserver logs
```bash
"(corsheaders.E014) Origin 'https://example.com/scan' in CORS_ALLOWED_ORIGINS should not have path"
```
### Browser logs
_No response_
### Paperless-ngx version
1.11.3
### Host OS
Ubuntu
### Installation method
Docker - official image
### Browser
Firefox
### Configuration changes
Set PAPERLESS_URL to https://example.com/scan
### Other
_No response_ | non_test | paperless url should only be a domain name don t set full url description i encountered a problem when migrating from paperless ng to ngx background my ng install runs from a subpath behind a reverse proxy problem doesn t tell you to set the new envvar paperless url so although i could login and view docs just fine after taking the steps documented in some operations were failing because of a security check problem i set the url to but loading the web interface just returns a completely blank page no error message nothing thankfully shell output told me that corsheaders origin in cors allowed origins should not have path the fix was to change paperless url so it s just a domain with no further path elements i e it s not the actual install url i therefore suggest at least updating the documentation to specify that not only should a trailing slash be omitted but in fact only the domain should be included not any other path element or the code could strip it when it s going to be a problem perhaps paperless domain would make for a better variable name but that s probably going to be a breaking change for not much gain steps to reproduce set paperless url to but loading the web interface just returns a completely blank page no error message nothing webserver logs bash corsheaders origin in cors allowed origins should not have path browser logs no response paperless ngx version host os ubuntu installation method docker official image browser firefox configuration changes set paperless url to other no response | 0 |
96,740 | 12,155,272,718 | IssuesEvent | 2020-04-25 12:23:34 | awaketogether/Site | https://api.github.com/repos/awaketogether/Site | opened | Full Design Template UI/UX | design | Before being able to construct a site, we should have the following design propositions:
- Home Page proposition
- Description content
- Base UI elements [buttons, fonts]
- Legal Mentions Page
- FAQ proposition | 1.0 | Full Design Template UI/UX - Before being able to construct a site, we should have the following design propositions:
- Home Page proposition
- Description content
- Base UI elements [buttons, fonts]
- Legal Mentions Page
- FAQ proposition | non_test | full design template ui ux before being able to construct a site we should have the following design propositions home page proposition description content base ui elements legal mentions page faq proposition | 0 |
395,449 | 11,686,549,472 | IssuesEvent | 2020-03-05 11:04:19 | yalla-coop/tempo | https://api.github.com/repos/yalla-coop/tempo | opened | Agree Data Architecture | discuss priority-2 technical | **This issue is to discuss the data architecture which we'll be talking through in the lead up to the data workshop (05/03) and beyond - so all documentation should go here.**
| 1.0 | Agree Data Architecture - **This issue is to discuss the data architecture which we'll be talking through in the lead up to the data workshop (05/03) and beyond - so all documentation should go here.**
| non_test | agree data architecture this issue is to discuss the data architecture which we ll be talking through in the lead up to the data workshop and beyond so all documentation should go here | 0 |
263,575 | 8,292,925,880 | IssuesEvent | 2018-09-20 03:41:45 | wso2/product-is | https://api.github.com/repos/wso2/product-is | closed | oidcdiscovery/.well-known/openid-configuration returns additional scopes when configure IS as a KM | Affected/5.6.0 Component/OIDC Priority/Highest | In our setup we have configured IS as KM with APIM
IS-Km 5.60
APIM 2.50
When I invoke the oidcdiscovery/.well-known/openid-configuration, it returns additional scopes (registry.*) that we haven't defined
Any idea what are those?
{
"scopes_supported": [
"profile",
**"registry.user",**
**"registry.realpath",**
**"registry.link",**
**"registry.author",**
"phone",
"email",
"address",
**"registry.mount",**
"openid"
],
"check_session_iframe": "https://localhost:9444/oidc/checksession",
"issuer": "https://localhost:9444/oauth2/token",
"authorization_endpoint": "https://localhost:9444/oauth2/authorize",
"claims_supported": [
.......
],
"token_endpoint": "https://localhost:9444/oauth2/token",
"response_types_supported": [
"id_token token",
"code",
"id_token",
"token"
],
"end_session_endpoint": "https://localhost:9444/oidc/logout",
"userinfo_endpoint": "https://localhost:9444/oauth2/userinfo",
"jwks_uri": "https://localhost:9444/oauth2/jwks",
"subject_types_supported": [
"pairwise"
],
"id_token_signing_alg_values_supported": [
"RS256"
],
"registration_endpoint": "https://localhost:9444/api/identity/oauth2/dcr/v1.0/register"
}
This did not reproduce in standalone iskm560 | 1.0 | oidcdiscovery/.well-known/openid-configuration returns additional scopes when configure IS as a KM - In our setup we have configured IS as KM with APIM
IS-Km 5.60
APIM 2.50
When I invoke the oidcdiscovery/.well-known/openid-configuration, it returns additional scopes (registry.*) that we haven't defined
Any idea what are those?
{
"scopes_supported": [
"profile",
**"registry.user",**
**"registry.realpath",**
**"registry.link",**
**"registry.author",**
"phone",
"email",
"address",
**"registry.mount",**
"openid"
],
"check_session_iframe": "https://localhost:9444/oidc/checksession",
"issuer": "https://localhost:9444/oauth2/token",
"authorization_endpoint": "https://localhost:9444/oauth2/authorize",
"claims_supported": [
.......
],
"token_endpoint": "https://localhost:9444/oauth2/token",
"response_types_supported": [
"id_token token",
"code",
"id_token",
"token"
],
"end_session_endpoint": "https://localhost:9444/oidc/logout",
"userinfo_endpoint": "https://localhost:9444/oauth2/userinfo",
"jwks_uri": "https://localhost:9444/oauth2/jwks",
"subject_types_supported": [
"pairwise"
],
"id_token_signing_alg_values_supported": [
"RS256"
],
"registration_endpoint": "https://localhost:9444/api/identity/oauth2/dcr/v1.0/register"
}
This did not reproduce in standalone iskm560 | non_test | oidcdiscovery well known openid configuration returns additional scopes when configure is as a km in our setup we have configured is as km with apim is km apim when i invoke the oidcdiscovery well known openid configuration it returns additional scopes registry that we haven t defined any idea what are those scopes supported profile registry user registry realpath registry link registry author phone email address registry mount openid check session iframe issuer authorization endpoint claims supported token endpoint response types supported id token token code id token token end session endpoint userinfo endpoint jwks uri subject types supported pairwise id token signing alg values supported registration endpoint this did not reproduce in standalone | 0 |
695,754 | 23,870,887,250 | IssuesEvent | 2022-09-07 14:44:53 | celo-org/celo-monorepo | https://api.github.com/repos/celo-org/celo-monorepo | closed | Add Code Examples to SDK Documentation | docs Priority: P3 Applications dog stale | - Show what a transaction looks like (object blob) and the extra fields
- How to use the wallets
- Sign a transaction
- Send a transaction
- Check logs/events(?)
- Make a connection (pull out of tutorials)
- Updates
- Calling your contract (?) | 1.0 | Add Code Examples to SDK Documentation - - Show what a transaction looks like (object blob) and the extra fields
- How to use the wallets
- Sign a transaction
- Send a transaction
- Check logs/events(?)
- Make a connection (pull out of tutorials)
- Updates
- Calling your contract (?) | non_test | add code examples to sdk documentation show what a transaction looks like object blob and the extra fields how to use the wallets sign a transaction send a transaction check logs events make a connection pull out of tutorials updates calling your contract | 0 |
159,597 | 12,483,668,149 | IssuesEvent | 2020-05-30 10:39:43 | WoWManiaUK/Redemption | https://api.github.com/repos/WoWManiaUK/Redemption | closed | [Quest] Enraged Spirits of Fire and Earth - 10458 - Shadowmoon Valley | Fix - Tester Confirmed | **Links:**
https://wow-mania.com/armory/?quest=10458
Item: https://wow-mania.com/armory/?item=30094
which uses spell: https://wow-mania.com/armory/?spell=36107
which summons NPC: https://wow-mania.com/armory/?npc=21071
**What is Happening:**
The "NPC" 21071 totem placed by the player using item 30094 casting 36107 moves with the player.
**What Should happen:**
The totem should stay still where it is placed.
| 1.0 | [Quest] Enraged Spirits of Fire and Earth - 10458 - Shadowmoon Valley - **Links:**
https://wow-mania.com/armory/?quest=10458
Item: https://wow-mania.com/armory/?item=30094
which uses spell: https://wow-mania.com/armory/?spell=36107
which summons NPC: https://wow-mania.com/armory/?npc=21071
**What is Happening:**
The "NPC" 21071 totem placed by the player using item 30094 casting 36107 moves with the player.
**What Should happen:**
The totem should stay still where it is placed.
| test | enraged spirits of fire and earth shadowmoon valley links item which uses spell which summons npc what is happening the npc totem placed by the player using item casting moves with the player what should happen the totem should stay still where it is placed | 1 |
61,437 | 6,736,259,979 | IssuesEvent | 2017-10-19 02:46:54 | omegaup/omegaup | https://api.github.com/repos/omegaup/omegaup | closed | contestcreate.php no tiene texto localizado | 1 help wanted omegaUp For Contests P3 ready UI Task | @lhchavez me imagino que esto se resuelve con el getWords que hay en todos los demás phps. | 1.0 | contestcreate.php no tiene texto localizado - @lhchavez me imagino que esto se resuelve con el getWords que hay en todos los demás phps. | test | contestcreate php no tiene texto localizado lhchavez me imagino que esto se resuelve con el getwords que hay en todos los demás phps | 1 |
278,702 | 24,169,355,083 | IssuesEvent | 2022-09-22 17:43:42 | apollographql/apollo-client | https://api.github.com/repos/apollographql/apollo-client | closed | Parse http response | 🐞 bug 🙏 help-wanted :books: good-first-issue 😍 pull-requests-welcome 👩🔬 needs-more-tests 🔗 apollo-link | We run into issue that when server does not respond in JSON format, there will be a ServerParseError instead of the ServerError. This happens because JSON.parse() is done before checking the status code:
https://github.com/apollographql/apollo-client/blob/main/src/link/http/parseAndCheckHttpResponse.ts (lines 19 and 30).
In this case, the error message of ServerParseError does not provide the information about the actual cause but only the parse error.
In some error cases, there is no guarantee that server will repsonse in JSON fromat.
For example if there is an authentication error. Or if response is an uncomplete JSON object because of 500 out of memory.
Could you please check if it is intended to be this way?
Thank you! | 1.0 | Parse http response - We run into issue that when server does not respond in JSON format, there will be a ServerParseError instead of the ServerError. This happens because JSON.parse() is done before checking the status code:
https://github.com/apollographql/apollo-client/blob/main/src/link/http/parseAndCheckHttpResponse.ts (lines 19 and 30).
In this case, the error message of ServerParseError does not provide the information about the actual cause but only the parse error.
In some error cases, there is no guarantee that server will repsonse in JSON fromat.
For example if there is an authentication error. Or if response is an uncomplete JSON object because of 500 out of memory.
Could you please check if it is intended to be this way?
Thank you! | test | parse http response we run into issue that when server does not respond in json format there will be a serverparseerror instead of the servererror this happens because json parse is done before checking the status code lines and in this case the error message of serverparseerror does not provide the information about the actual cause but only the parse error in some error cases there is no guarantee that server will repsonse in json fromat for example if there is an authentication error or if response is an uncomplete json object because of out of memory could you please check if it is intended to be this way thank you | 1 |
31,524 | 7,382,835,627 | IssuesEvent | 2018-03-15 07:10:25 | marbl/MetagenomeScope | https://api.github.com/repos/marbl/MetagenomeScope | closed | Clean up finishing controls' code | codeissue | There's some repeated code which makes reading this section kind of difficult. | 1.0 | Clean up finishing controls' code - There's some repeated code which makes reading this section kind of difficult. | non_test | clean up finishing controls code there s some repeated code which makes reading this section kind of difficult | 0 |
128,585 | 18,062,747,720 | IssuesEvent | 2021-09-20 15:33:37 | scriptex/react-svg-donuts | https://api.github.com/repos/scriptex/react-svg-donuts | closed | CVE-2021-3803 (Medium) detected in nth-check-2.0.0.tgz | security vulnerability | ## CVE-2021-3803 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>nth-check-2.0.0.tgz</b></p></summary>
<p>Parses and compiles CSS nth-checks to highly optimized functions.</p>
<p>Library home page: <a href="https://registry.npmjs.org/nth-check/-/nth-check-2.0.0.tgz">https://registry.npmjs.org/nth-check/-/nth-check-2.0.0.tgz</a></p>
<p>Path to dependency file: react-svg-donuts/package.json</p>
<p>Path to vulnerable library: react-svg-donuts/node_modules/nth-check/package.json</p>
<p>
Dependency Hierarchy:
- html-webpack-plugin-5.3.2.tgz (Root Library)
- pretty-error-3.0.4.tgz
- renderkid-2.0.7.tgz
- css-select-4.1.3.tgz
- :x: **nth-check-2.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/scriptex/react-svg-donuts/commit/0501bbb0319df85f906277fdef62358ca99a2283">0501bbb0319df85f906277fdef62358ca99a2283</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
nth-check is vulnerable to Inefficient Regular Expression Complexity
<p>Publish Date: 2021-09-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3803>CVE-2021-3803</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: N/A
- Attack Complexity: N/A
- Privileges Required: N/A
- User Interaction: N/A
- Scope: N/A
- Impact Metrics:
- Confidentiality Impact: N/A
- Integrity Impact: N/A
- Availability Impact: N/A
</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/fb55/nth-check/compare/v2.0.0...v2.0.1">https://github.com/fb55/nth-check/compare/v2.0.0...v2.0.1</a></p>
<p>Release Date: 2021-09-17</p>
<p>Fix Resolution: nth-check - v2.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-3803 (Medium) detected in nth-check-2.0.0.tgz - ## CVE-2021-3803 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>nth-check-2.0.0.tgz</b></p></summary>
<p>Parses and compiles CSS nth-checks to highly optimized functions.</p>
<p>Library home page: <a href="https://registry.npmjs.org/nth-check/-/nth-check-2.0.0.tgz">https://registry.npmjs.org/nth-check/-/nth-check-2.0.0.tgz</a></p>
<p>Path to dependency file: react-svg-donuts/package.json</p>
<p>Path to vulnerable library: react-svg-donuts/node_modules/nth-check/package.json</p>
<p>
Dependency Hierarchy:
- html-webpack-plugin-5.3.2.tgz (Root Library)
- pretty-error-3.0.4.tgz
- renderkid-2.0.7.tgz
- css-select-4.1.3.tgz
- :x: **nth-check-2.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/scriptex/react-svg-donuts/commit/0501bbb0319df85f906277fdef62358ca99a2283">0501bbb0319df85f906277fdef62358ca99a2283</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
nth-check is vulnerable to Inefficient Regular Expression Complexity
<p>Publish Date: 2021-09-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3803>CVE-2021-3803</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: N/A
- Attack Complexity: N/A
- Privileges Required: N/A
- User Interaction: N/A
- Scope: N/A
- Impact Metrics:
- Confidentiality Impact: N/A
- Integrity Impact: N/A
- Availability Impact: N/A
</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/fb55/nth-check/compare/v2.0.0...v2.0.1">https://github.com/fb55/nth-check/compare/v2.0.0...v2.0.1</a></p>
<p>Release Date: 2021-09-17</p>
<p>Fix Resolution: nth-check - v2.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_test | cve medium detected in nth check tgz cve medium severity vulnerability vulnerable library nth check tgz parses and compiles css nth checks to highly optimized functions library home page a href path to dependency file react svg donuts package json path to vulnerable library react svg donuts node modules nth check package json dependency hierarchy html webpack plugin tgz root library pretty error tgz renderkid tgz css select tgz x nth check tgz vulnerable library found in head commit a href vulnerability details nth check is vulnerable to inefficient regular expression complexity publish date url a href cvss score details base score metrics exploitability metrics attack vector n a attack complexity n a privileges required n a user interaction n a scope n a impact metrics confidentiality impact n a integrity impact n a availability impact n a for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution nth check step up your open source security game with whitesource | 0 |
266,922 | 23,268,717,148 | IssuesEvent | 2022-08-04 20:12:01 | foundry-rs/foundry | https://api.github.com/repos/foundry-rs/foundry | closed | Print unit names in `forge test` failures report | T-feature Cmd-forge-test C-forge | ### Component
Forge
### Describe the feature you would like
We have multiple test cases with the same name but in different units. Typical examples:
- testEmitEvent
- testRevertIfPaused
When a test with a "popular" name fails, it's not immediately obvious what unit we should look at, so the next step after encountering the failure is almost always `forge test --match-test`. I would like to see the unit name in the output instead, for instance:
> [FAIL. Reason: Log != expected log. Counterexample: calldata=0xe3ea2b1d0000000000000000000000000000000000000000000000000000000000800000, args=[8388608]] UnitDeploySomething.testEmitEvent(int24) (runs: 10, μ: 89131, ~: 50072)
Please consider adding this. Thank you 🌈
### Additional context
#2328 might help too. | 1.0 | Print unit names in `forge test` failures report - ### Component
Forge
### Describe the feature you would like
We have multiple test cases with the same name but in different units. Typical examples:
- testEmitEvent
- testRevertIfPaused
When a test with a "popular" name fails, it's not immediately obvious what unit we should look at, so the next step after encountering the failure is almost always `forge test --match-test`. I would like to see the unit name in the output instead, for instance:
> [FAIL. Reason: Log != expected log. Counterexample: calldata=0xe3ea2b1d0000000000000000000000000000000000000000000000000000000000800000, args=[8388608]] UnitDeploySomething.testEmitEvent(int24) (runs: 10, μ: 89131, ~: 50072)
Please consider adding this. Thank you 🌈
### Additional context
#2328 might help too. | test | print unit names in forge test failures report component forge describe the feature you would like we have multiple test cases with the same name but in different units typical examples testemitevent testrevertifpaused when a test with a popular name fails it s not immediately obvious what unit we should look at so the next step after encountering the failure is almost always forge test match test i would like to see the unit name in the output instead for instance unitdeploysomething testemitevent runs μ please consider adding this thank you 🌈 additional context might help too | 1 |
9,606 | 8,051,690,476 | IssuesEvent | 2018-08-01 16:53:16 | eventespresso/event-espresso-core | https://api.github.com/repos/eventespresso/event-espresso-core | closed | Account for "Index column size too large" database error | category:models-and-data-infrastructure status:in-progress type:bug 🐞 | There was a site that migrated data from EE3 to EE4 and none of the attendee data was migrated into `wp_esp_attendee_meta`. This error was captured when doing the migration:
```WordPress database error: [Index column size too large. The maximum column size is 767 bytes.]
CREATE TABLE wp_esp_attendee_meta ( ATTM_ID INT(10) UNSIGNED NOT NULL AUTO_INCREMENT, ATT_ID BIGINT(20) UNSIGNED NOT NULL, ATT_fname VARCHAR(45) NOT NULL, ATT_lname VARCHAR(45) NOT NULL, ATT_address VARCHAR(255) DEFAULT NULL, ATT_address2 VARCHAR(255) DEFAULT NULL, ATT_city VARCHAR(45) DEFAULT NULL, STA_ID INT(10) DEFAULT NULL, CNT_ISO VARCHAR(45) DEFAULT NULL, ATT_zip VARCHAR(12) DEFAULT NULL, ATT_email VARCHAR(255) NOT NULL, ATT_phone VARCHAR(45) DEFAULT NULL, PRIMARY KEY (ATTM_ID), KEY ATT_fname (ATT_fname), KEY ATT_lname (ATT_lname), KEY ATT_email (ATT_email) ) ENGINE=InnoDB DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci```
```Stack Trace:#0 /wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Activation.helper.php(671): EventEspresso\core\services\database\TableManager->createTable('esp_attendee_me...', 'ATTM_ID INT(10)...', 'InnoDB ') #1 /wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Base.core.php(647): EEH_Activation::create_table('esp_attendee_me...', 'ATTM_ID INT(10)...', 'ENGINE=InnoDB ', true) #2 /wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Base.core.php(471): EE_Data_Migration_Script_Base->_create_table_and_catch_errors('esp_attendee_me...', 'ATTM_ID INT(10)...', 'ENGINE=InnoDB ', true) #3 /wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_DMS_Core_4_1_0.dms.php(147): EE_Data_Migration_Script_Base->_table_is_new_in_this_version('esp_attendee_me...', 'ATTM_ID INT(10)...', 'ENGINE=InnoDB ') #4 /wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Base.core.php(419): EE_DMS_Core_4_1_0->schema_changes_before_migration() #5 /wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Base.core.php(323): EE_Data_Migration_Script_Base->_maybe_do_schema_changes(true) #6 /wp-content/plugins/event-espresso-core-reg/core/EE_Data_Migration_Manager.core.php(663): EE_Data_Migration_Script_Base->migration_step(50) #7 /wp-content/plugins/event-espresso-core-reg/core/EE_Data_Migration_Manager.core.php(779): EE_Data_Migration_Manager->migration_step() #8 /wp-content/plugins/event-espresso-core-reg/admin_pages/maintenance/Maintenance_Admin_Page.core.php(362): EE_Data_Migration_Manager->response_to_migration_ajax_request() #9 [internal function]: Maintenance_Admin_Page->migration_step('') #10 /wp-includes/class-wp-hook.php(286): call_user_func_array(Array, Array) #11 /wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters('', Array) #12 /wp-includes/plugin.php(453): WP_Hook->do_action(Array) #13 /wp-admin/admin-ajax.php(99): do_action('wp_ajax_migrati...') #14 {main}Migrated 55 records successfully during Organization Options/Config``` | 1.0 | Account for "Index column size too large" database error - There was a site that migrated data from EE3 to EE4 and none of the attendee data was migrated into `wp_esp_attendee_meta`. This error was captured when doing the migration:
```WordPress database error: [Index column size too large. The maximum column size is 767 bytes.]
CREATE TABLE wp_esp_attendee_meta ( ATTM_ID INT(10) UNSIGNED NOT NULL AUTO_INCREMENT, ATT_ID BIGINT(20) UNSIGNED NOT NULL, ATT_fname VARCHAR(45) NOT NULL, ATT_lname VARCHAR(45) NOT NULL, ATT_address VARCHAR(255) DEFAULT NULL, ATT_address2 VARCHAR(255) DEFAULT NULL, ATT_city VARCHAR(45) DEFAULT NULL, STA_ID INT(10) DEFAULT NULL, CNT_ISO VARCHAR(45) DEFAULT NULL, ATT_zip VARCHAR(12) DEFAULT NULL, ATT_email VARCHAR(255) NOT NULL, ATT_phone VARCHAR(45) DEFAULT NULL, PRIMARY KEY (ATTM_ID), KEY ATT_fname (ATT_fname), KEY ATT_lname (ATT_lname), KEY ATT_email (ATT_email) ) ENGINE=InnoDB DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci```
```Stack Trace:#0 /wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Activation.helper.php(671): EventEspresso\core\services\database\TableManager->createTable('esp_attendee_me...', 'ATTM_ID INT(10)...', 'InnoDB ') #1 /wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Base.core.php(647): EEH_Activation::create_table('esp_attendee_me...', 'ATTM_ID INT(10)...', 'ENGINE=InnoDB ', true) #2 /wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Base.core.php(471): EE_Data_Migration_Script_Base->_create_table_and_catch_errors('esp_attendee_me...', 'ATTM_ID INT(10)...', 'ENGINE=InnoDB ', true) #3 /wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_DMS_Core_4_1_0.dms.php(147): EE_Data_Migration_Script_Base->_table_is_new_in_this_version('esp_attendee_me...', 'ATTM_ID INT(10)...', 'ENGINE=InnoDB ') #4 /wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Base.core.php(419): EE_DMS_Core_4_1_0->schema_changes_before_migration() #5 /wp-content/plugins/event-espresso-core-reg/core/data_migration_scripts/EE_Data_Migration_Script_Base.core.php(323): EE_Data_Migration_Script_Base->_maybe_do_schema_changes(true) #6 /wp-content/plugins/event-espresso-core-reg/core/EE_Data_Migration_Manager.core.php(663): EE_Data_Migration_Script_Base->migration_step(50) #7 /wp-content/plugins/event-espresso-core-reg/core/EE_Data_Migration_Manager.core.php(779): EE_Data_Migration_Manager->migration_step() #8 /wp-content/plugins/event-espresso-core-reg/admin_pages/maintenance/Maintenance_Admin_Page.core.php(362): EE_Data_Migration_Manager->response_to_migration_ajax_request() #9 [internal function]: Maintenance_Admin_Page->migration_step('') #10 /wp-includes/class-wp-hook.php(286): call_user_func_array(Array, Array) #11 /wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters('', Array) #12 /wp-includes/plugin.php(453): WP_Hook->do_action(Array) #13 /wp-admin/admin-ajax.php(99): do_action('wp_ajax_migrati...') #14 {main}Migrated 55 records successfully during Organization Options/Config``` | non_test | account for index column size too large database error there was a site that migrated data from to and none of the attendee data was migrated into wp esp attendee meta this error was captured when doing the migration wordpress database error
create table wp esp attendee meta attm id int unsigned not null auto increment att id bigint unsigned not null att fname varchar not null att lname varchar not null att address varchar default null att varchar default null att city varchar default null sta id int default null cnt iso varchar default null att zip varchar default null att email varchar not null att phone varchar default null primary key attm id key att fname att fname key att lname att lname key att email att email engine innodb default character set collate unicode ci stack trace wp content plugins event espresso core reg core helpers eeh activation helper php eventespresso core services database tablemanager createtable esp attendee me attm id int innodb wp content plugins event espresso core reg core data migration scripts ee data migration script base core php eeh activation create table esp attendee me attm id int engine innodb true wp content plugins event espresso core reg core data migration scripts ee data migration script base core php ee data migration script base create table and catch errors esp attendee me attm id int engine innodb true wp content plugins event espresso core reg core data migration scripts ee dms core dms php ee data migration script base table is new in this version esp attendee me attm id int engine innodb wp content plugins event espresso core reg core data migration scripts ee data migration script base core php ee dms core schema changes before migration wp content plugins event espresso core reg core data migration scripts ee data migration script base core php ee data migration script base maybe do schema changes true wp content plugins event espresso core reg core ee data migration manager core php ee data migration script base migration step wp content plugins event espresso core reg core ee data migration manager core php ee data migration manager migration step wp content plugins event espresso core reg admin pages maintenance maintenance admin page core php ee data migration manager response to migration ajax request maintenance admin page migration step wp includes class wp hook php call user func array array array wp includes class wp hook php wp hook apply filters array wp includes plugin php wp hook do action array wp admin admin ajax php do action wp ajax migrati main migrated records successfully during organization options config | 0 |
87,861 | 8,124,402,191 | IssuesEvent | 2018-08-16 17:26:16 | prometheus/prometheus | https://api.github.com/repos/prometheus/prometheus | closed | Flaky TestForStateRestore test | component/tests kind/bug | `make test` has failed on my local machine with:
```
--- FAIL: TestForStateRestore (0.02s)
testing.go:68:
exp: labels.Labels{labels.Label{Name:"alertname", Value:"HTTPRequestRateLow"}, labels.Label{Name:"group", Value:"canary"}, labels.Label{Name:"instance", Value:"1"}, labels.Label{Name:"job", Value:"app-server"}, labels.Label{Name:"severity", Value:"critical"}}
got: labels.Labels{labels.Label{Name:"alertname", Value:"HTTPRequestRateLow"}, labels.Label{Name:"group", Value:"canary"}, labels.Label{Name:"instance", Value:"0"}, labels.Label{Name:"job", Value:"app-server"}, labels.Label{Name:"severity", Value:"critical"}}
FAIL
FAIL github.com/prometheus/prometheus/rules 0.156s
``` | 1.0 | Flaky TestForStateRestore test - `make test` has failed on my local machine with:
```
--- FAIL: TestForStateRestore (0.02s)
testing.go:68:
exp: labels.Labels{labels.Label{Name:"alertname", Value:"HTTPRequestRateLow"}, labels.Label{Name:"group", Value:"canary"}, labels.Label{Name:"instance", Value:"1"}, labels.Label{Name:"job", Value:"app-server"}, labels.Label{Name:"severity", Value:"critical"}}
got: labels.Labels{labels.Label{Name:"alertname", Value:"HTTPRequestRateLow"}, labels.Label{Name:"group", Value:"canary"}, labels.Label{Name:"instance", Value:"0"}, labels.Label{Name:"job", Value:"app-server"}, labels.Label{Name:"severity", Value:"critical"}}
FAIL
FAIL github.com/prometheus/prometheus/rules 0.156s
``` | test | flaky testforstaterestore test make test has failed on my local machine with fail testforstaterestore testing go exp labels labels labels label name alertname value httprequestratelow labels label name group value canary labels label name instance value labels label name job value app server labels label name severity value critical got labels labels labels label name alertname value httprequestratelow labels label name group value canary labels label name instance value labels label name job value app server labels label name severity value critical fail fail github com prometheus prometheus rules | 1 |
786,985 | 27,700,623,125 | IssuesEvent | 2023-03-14 07:41:51 | googleapis/google-api-dotnet-client | https://api.github.com/repos/googleapis/google-api-dotnet-client | closed | Question - why were class names renamed (again)? | type: question priority: p3 | This is just a question, out of curiosity more than anything else.
I try to keep on top of NuGet packages in my projects. A couple of weeks ago, I updated to version 1.59.0.2950, which changed a number of class names, such as:
```
GoogleSecuritySafebrowsingV4FindThreatMatchesRequest => FindThreatMatchesRequest
GoogleSecuritySafebrowsingV4ClientInfo => ClientInfo
GoogleSecuritySafebrowsingV4ThreatInfo => ThreatInfo
```
etc.
I've just updated to 1.60.0.2968, which seems to have reversed this object naming back to what it was previously.
I'm all for the descriptive naming of classes, but I was quite glad to see the back of the `GoogleSecuritySafebrowsingV4` naming convention prefix. These prefixes always seemed clunky to me, making code harder to read. They always felt redundant anyway, being as they were contained in the `Google.Apis.Safebrowsing.v4` and `using Google.Apis.Safebrowsing.v4.Data` namespaces.
Sure, it was a breaking change, but in reality, was one that took seconds to remedy (at least in my case). This was worth the more succinct naming convention and increased readability of the code.
What drove the need to revert to the older, prefixed names?
| 1.0 | Question - why were class names renamed (again)? - This is just a question, out of curiosity more than anything else.
I try to keep on top of NuGet packages in my projects. A couple of weeks ago, I updated to version 1.59.0.2950, which changed a number of class names, such as:
```
GoogleSecuritySafebrowsingV4FindThreatMatchesRequest => FindThreatMatchesRequest
GoogleSecuritySafebrowsingV4ClientInfo => ClientInfo
GoogleSecuritySafebrowsingV4ThreatInfo => ThreatInfo
```
etc.
I've just updated to 1.60.0.2968, which seems to have reversed this object naming back to what it was previously.
I'm all for the descriptive naming of classes, but I was quite glad to see the back of the `GoogleSecuritySafebrowsingV4` naming convention prefix. These prefixes always seemed clunky to me, making code harder to read. They always felt redundant anyway, being as they were contained in the `Google.Apis.Safebrowsing.v4` and `using Google.Apis.Safebrowsing.v4.Data` namespaces.
Sure, it was a breaking change, but in reality, was one that took seconds to remedy (at least in my case). This was worth the more succinct naming convention and increased readability of the code.
What drove the need to revert to the older, prefixed names?
| non_test | question why were class names renamed again this is just a question out of curiosity more than anything else i try to keep on top of nuget packages in my projects a couple of weeks ago i updated to version which changed a number of class names such as findthreatmatchesrequest clientinfo threatinfo etc i ve just updated to which seems to have reversed this object naming back to what it was previously i m all for the descriptive naming of classes but i was quite glad to see the back of the naming convention prefix these prefixes always seemed clunky to me making code harder to read they always felt redundant anyway being as they were contained in the google apis safebrowsing and using google apis safebrowsing data namespaces sure it was a breaking change but in reality was one that took seconds to remedy at least in my case this was worth the more succinct naming convention and increased readability of the code what drove the need to revert to the older prefixed names | 0 |
320,547 | 27,440,107,198 | IssuesEvent | 2023-03-02 10:23:50 | WPChill/kb-support | https://api.github.com/repos/WPChill/kb-support | closed | KB Articles lead to a 404 | bug Needs Testing | **Describe the bug**
I have set up a page with the [kbs_articles] shortcode, and I have three articles showing on the page, however when I click on them, they lead to a 404 page. This plugin is doing everything I need besides this.
I can provide some screenshots though.
[KB Articles in WordPress Dashboard](https://drive.google.com/file/d/1-wYOXjQsJZhgIahJ79hAc0b35p8vVJNa/view?usp=sharing)
[KB Articles on KB articles page](https://drive.google.com/file/d/1a4Fpz2iVrGzup-oeOa1X_l58vgenvG81/view?usp=sharing)
[After clicking on an article](https://drive.google.com/file/d/1wOYHrNcV1januGE0Bvb5IcyzDB6LTc7S/view?usp=sharing)
As you can see, I have added three articles, and they display just fine on the page I have specified as the KB articles page, but when I click on any of the articles, it takes me to a 404 page.
https://wordpress.org/support/topic/kb-articles-lead-to-a-404/ | 1.0 | KB Articles lead to a 404 - **Describe the bug**
I have set up a page with the [kbs_articles] shortcode, and I have three articles showing on the page, however when I click on them, they lead to a 404 page. This plugin is doing everything I need besides this.
I can provide some screenshots though.
[KB Articles in WordPress Dashboard](https://drive.google.com/file/d/1-wYOXjQsJZhgIahJ79hAc0b35p8vVJNa/view?usp=sharing)
[KB Articles on KB articles page](https://drive.google.com/file/d/1a4Fpz2iVrGzup-oeOa1X_l58vgenvG81/view?usp=sharing)
[After clicking on an article](https://drive.google.com/file/d/1wOYHrNcV1januGE0Bvb5IcyzDB6LTc7S/view?usp=sharing)
As you can see, I have added three articles, and they display just fine on the page I have specified as the KB articles page, but when I click on any of the articles, it takes me to a 404 page.
https://wordpress.org/support/topic/kb-articles-lead-to-a-404/ | test | kb articles lead to a describe the bug i have set up a page with the shortcode and i have three articles showing on the page however when i click on them they lead to a page this plugin is doing everything i need besides this i can provide some screenshots though as you can see i have added three articles and they display just fine on the page i have specified as the kb articles page but when i click on any of the articles it takes me to a page | 1 |
185,797 | 15,032,824,086 | IssuesEvent | 2021-02-02 10:40:09 | rlespinasse/docker-drawio-desktop-headless | https://api.github.com/repos/rlespinasse/docker-drawio-desktop-headless | closed | not exporting | bug documentation | Nice work! This seems to be what I am looking for, but I can't get it to work. I might be a bit too quick, since you only released it 2 days ago. I didn't see any issue templates so I hope I have given you everything you need to know.
I don't have drawio-desktop installed on this machine. Let me know if it is a fault on my side!
## intended use
I have a repo with UML diagrams: https://gitlab.com/powderbooking/readme/-/tree/3-uml-architecture-diagram
I would like to keep the `.drawio` data in git. In my CI/CD pipeline, I want to export those files to `.png` files and publish them as artifacts. Therefore, I want to export the `.drawio` files using a CLI that can be run inside my pipeline. This way, I do not need to store a large blob inside my repo, yet still get access to the `.png` files.
## command executed
```
git clone https://gitlab.com/powderbooking/readme.git
cd readme/img
docker run -it -v $(pwd):/data rlespinasse/drawio-desktop-headless -f png -o infra.png -x powderbooking_uml_infra.drawio
```
## expected output
a png file named `infra.png`
a log statement with `powderbooking_uml_infra.drawio -> infra.png`
## observed output
Nothing. No log statements, no file. It hangs after the given timeout window. I have also tried it with a 60s timeout.
## system used
```
$ uname -a
Linux ithilien-Aspire-V3-371 4.15.0-132-generic #136-Ubuntu SMP Tue Jan 12 14:58:42 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$ docker -v
Docker version 20.10.2, build 2291f61
``` | 1.0 | not exporting - Nice work! This seems to be what I am looking for, but I can't get it to work. I might be a bit too quick, since you only released it 2 days ago. I didn't see any issue templates so I hope I have given you everything you need to know.
I don't have drawio-desktop installed on this machine. Let me know if it is a fault on my side!
## intended use
I have a repo with UML diagrams: https://gitlab.com/powderbooking/readme/-/tree/3-uml-architecture-diagram
I would like to keep the `.drawio` data in git. In my CI/CD pipeline, I want to export those files to `.png` files and publish them as artifacts. Therefore, I want to export the `.drawio` files using a CLI that can be run inside my pipeline. This way, I do not need to store a large blob inside my repo, yet still get access to the `.png` files.
## command executed
```
git clone https://gitlab.com/powderbooking/readme.git
cd readme/img
docker run -it -v $(pwd):/data rlespinasse/drawio-desktop-headless -f png -o infra.png -x powderbooking_uml_infra.drawio
```
## expected output
a png file named `infra.png`
a log statement with `powderbooking_uml_infra.drawio -> infra.png`
## observed output
Nothing. No log statements, no file. It hangs after the given timeout window. I have also tried it with a 60s timeout.
## system used
```
$ uname -a
Linux ithilien-Aspire-V3-371 4.15.0-132-generic #136-Ubuntu SMP Tue Jan 12 14:58:42 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$ docker -v
Docker version 20.10.2, build 2291f61
``` | non_test | not exporting nice work this seems to be what i am looking for but i can t get it to work i might be a bit too quick since you only released it days ago i didn t see any issue templates so i hope i have given you everything you need to know i don t have drawio desktop installed on this machine let me know if it is a fault on my side intended use i have a repo with uml diagrams i would like to keep the drawio data in git in my ci cd pipeline i want to export those files to png files and publish them as artifacts therefore i want to export the drawio files using a cli that can be run inside my pipeline this way i do not need to store a large blob inside my repo yet still get access to the png files command executed git clone cd readme img docker run it v pwd data rlespinasse drawio desktop headless f png o infra png x powderbooking uml infra drawio expected output a png file named infra png a log statement with powderbooking uml infra drawio infra png observed output nothing no log statements no file it hangs after the given timeout window i have also tried it with a timeout system used uname a linux ithilien aspire generic ubuntu smp tue jan utc gnu linux docker v docker version build | 0 |
289,840 | 25,017,305,620 | IssuesEvent | 2022-11-03 20:03:33 | CMAP-REPOS/cmap_csvm | https://api.github.com/repos/CMAP-REPOS/cmap_csvm | closed | Forecast year: set up and testing of future year scenario | enhancement testing | Once received inputs for future year, set up and run the scenario. Debugging and initial checks on outputs for reasonableness (e.g., growth from base year) | 1.0 | Forecast year: set up and testing of future year scenario - Once received inputs for future year, set up and run the scenario. Debugging and initial checks on outputs for reasonableness (e.g., growth from base year) | test | forecast year set up and testing of future year scenario once received inputs for future year set up and run the scenario debugging and initial checks on outputs for reasonableness e g growth from base year | 1 |
236,345 | 18,094,177,645 | IssuesEvent | 2021-09-22 07:09:06 | AY2122S1-CS2103T-W10-2/tp | https://api.github.com/repos/AY2122S1-CS2103T-W10-2/tp | closed | About us - Information on Yunseong not given | documentation | Information on Yunseong is not present in About us | 1.0 | About us - Information on Yunseong not given - Information on Yunseong is not present in About us | non_test | about us information on yunseong not given information on yunseong is not present in about us | 0 |
111,431 | 24,127,873,774 | IssuesEvent | 2022-09-21 03:27:15 | withfig/fig | https://api.github.com/repos/withfig/fig | closed | Could not load URL... | type:bug codebase:dashboard | ### Description:
Every time I open fig settings, I get this.
<img width="1030" alt="CleanShot 2022-09-20 at 11 56 49@2x" src="https://user-images.githubusercontent.com/25026967/191164173-6a011d5c-53a7-4533-b4a6-4ba2cfca7358.png">
### Details:
|macOS|Fig|Shell|
|-|-|-|
|12.6.0|Version 1.0.61 (B528)|/bin/zsh|
<details><summary><code>fig diagnostic</code></summary>
<p>
<pre>Version 1.0.61 (B528) [ABC]
UserShell: /bin/zsh
Bundle path: /Applications/Fig.app
Autocomplete: true
Settings.json: true
CLI installed: true
CLI tool path: /Users/phuctm97/.fig/bin/fig
Accessibility: true
SSH Integration: false
Tmux Integration: false
iTerm Integration: false
Hyper Integration: false
VSCode Integration: true
Docker Integration: false
Symlinked dotfiles: false
Only insert on tab: false
UNIX Socket Exists: true
Installation Script: true
PseudoTerminal Path: /Users/phuctm97/.nvm/versions/node/v14.19.0/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin:/Users/phuctm97/.fig/bin:/Users/phuctm97/.local/bin:/Users/phuctm97/Library/Android/sdk/emulator:/Users/phuctm97/Library/Android/sdk/tools:/Users/phuctm97/Library/Android/sdk/tools/bin:/Users/phuctm97/Library/Android/sdk/platform-tools:/Users/phuctm97/.antigen/bundles/robbyrussell/oh-my-zsh/lib:/Users/phuctm97/.antigen/bundles/dracula/zsh
SecureKeyboardInput: false
SecureKeyboardProcess: <none>
Current active process: ??? (???) - ???
Current terminal session: ???
Current working directory: ???
Current window identifier: ???</pre>
</p>
</details> | 1.0 | Could not load URL... - ### Description:
Every time I open fig settings, I get this.
<img width="1030" alt="CleanShot 2022-09-20 at 11 56 49@2x" src="https://user-images.githubusercontent.com/25026967/191164173-6a011d5c-53a7-4533-b4a6-4ba2cfca7358.png">
### Details:
|macOS|Fig|Shell|
|-|-|-|
|12.6.0|Version 1.0.61 (B528)|/bin/zsh|
<details><summary><code>fig diagnostic</code></summary>
<p>
<pre>Version 1.0.61 (B528) [ABC]
UserShell: /bin/zsh
Bundle path: /Applications/Fig.app
Autocomplete: true
Settings.json: true
CLI installed: true
CLI tool path: /Users/phuctm97/.fig/bin/fig
Accessibility: true
SSH Integration: false
Tmux Integration: false
iTerm Integration: false
Hyper Integration: false
VSCode Integration: true
Docker Integration: false
Symlinked dotfiles: false
Only insert on tab: false
UNIX Socket Exists: true
Installation Script: true
PseudoTerminal Path: /Users/phuctm97/.nvm/versions/node/v14.19.0/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin:/Users/phuctm97/.fig/bin:/Users/phuctm97/.local/bin:/Users/phuctm97/Library/Android/sdk/emulator:/Users/phuctm97/Library/Android/sdk/tools:/Users/phuctm97/Library/Android/sdk/tools/bin:/Users/phuctm97/Library/Android/sdk/platform-tools:/Users/phuctm97/.antigen/bundles/robbyrussell/oh-my-zsh/lib:/Users/phuctm97/.antigen/bundles/dracula/zsh
SecureKeyboardInput: false
SecureKeyboardProcess: <none>
Current active process: ??? (???) - ???
Current terminal session: ???
Current working directory: ???
Current window identifier: ???</pre>
</p>
</details> | non_test | could not load url description every time i open fig settings i get this img width alt cleanshot at src details macos fig shell version bin zsh fig diagnostic version usershell bin zsh bundle path applications fig app autocomplete true settings json true cli installed true cli tool path users fig bin fig accessibility true ssh integration false tmux integration false iterm integration false hyper integration false vscode integration true docker integration false symlinked dotfiles false only insert on tab false unix socket exists true installation script true pseudoterminal path users nvm versions node bin opt homebrew bin opt homebrew sbin usr local bin usr bin bin usr sbin sbin library apple usr bin users fig bin users local bin users library android sdk emulator users library android sdk tools users library android sdk tools bin users library android sdk platform tools users antigen bundles robbyrussell oh my zsh lib users antigen bundles dracula zsh securekeyboardinput false securekeyboardprocess current active process current terminal session current working directory current window identifier | 0 |
35,657 | 4,691,154,975 | IssuesEvent | 2016-10-11 09:31:59 | vaadin/framework8-issues | https://api.github.com/repos/vaadin/framework8-issues | closed | Fields mapped to a bean property with @NotNull or @NotEmpty should be visually marked as required | Forms and field components needs design SHOULD | Still needs to consider the exact details since e.g. @NotNull would accept `""`, even though that is usually not considered acceptable for a required field.
This also relates to https://dev.vaadin.com/ticket/14746 | 1.0 | Fields mapped to a bean property with @NotNull or @NotEmpty should be visually marked as required - Still needs to consider the exact details since e.g. @NotNull would accept `""`, even though that is usually not considered acceptable for a required field.
This also relates to https://dev.vaadin.com/ticket/14746 | non_test | fields mapped to a bean property with notnull or notempty should be visually marked as required still needs to consider the exact details since e g notnull would accept even though that is usually not considered acceptable for a required field this also relates to | 0 |
323,745 | 27,748,527,896 | IssuesEvent | 2023-03-15 18:48:36 | MPMG-DCC-UFMG/F01 | https://api.github.com/repos/MPMG-DCC-UFMG/F01 | closed | Teste de generalizacao para a tag Despesas - Pagamentos - Ervália | generalization test development | DoD: Realizar o teste de Generalização do validador da tag Despesas - Pagamentos para o Município de Ervália. | 1.0 | Teste de generalizacao para a tag Despesas - Pagamentos - Ervália - DoD: Realizar o teste de Generalização do validador da tag Despesas - Pagamentos para o Município de Ervália. | test | teste de generalizacao para a tag despesas pagamentos ervália dod realizar o teste de generalização do validador da tag despesas pagamentos para o município de ervália | 1 |
265,399 | 23,165,369,200 | IssuesEvent | 2022-07-29 23:38:38 | redpanda-data/redpanda | https://api.github.com/repos/redpanda-data/redpanda | closed | Error: seastar::condition_variable_timed_out (Condition variable timed out) | kind/bug area/redpanda area/tests ci-failure | This showed up as a CI failure [here](https://buildkite.com/redpanda/redpanda/builds/11465#0181756f-c616-457e-be53-8f0dcea2d29c), and I cannot tell from the logs which condition variable has timed out. ([link to log file](https://ci-artifacts.dev.vectorized.cloud/redpanda/0181756f-c616-457e-be53-8f0dcea2d29c/vbuild/ducktape/results/2022-06-18--001/NodeResizeTest/test_node_resize/46/RedpandaService-0-139697655586048/docker-rp-9/redpanda.log))
This happened in NodeResizeTest test_node_resize, but I'm guessing this is a general error that can occur with any test, considering that it is explicitly allowed in chaos tests.
```
ERROR 2022-06-18 06:52:16,604 [shard 0] rpc - Service handler threw an exception: seastar::condition_variable_timed_out (Condition variable timed out)
```
To Fix: add better diagnostic logging (e.g. named semaphore) so we have a chance of narrowing these down. | 1.0 | Error: seastar::condition_variable_timed_out (Condition variable timed out) - This showed up as a CI failure [here](https://buildkite.com/redpanda/redpanda/builds/11465#0181756f-c616-457e-be53-8f0dcea2d29c), and I cannot tell from the logs which condition variable has timed out. ([link to log file](https://ci-artifacts.dev.vectorized.cloud/redpanda/0181756f-c616-457e-be53-8f0dcea2d29c/vbuild/ducktape/results/2022-06-18--001/NodeResizeTest/test_node_resize/46/RedpandaService-0-139697655586048/docker-rp-9/redpanda.log))
This happened in NodeResizeTest test_node_resize, but I'm guessing this is a general error that can occur with any test, considering that it is explicitly allowed in chaos tests.
```
ERROR 2022-06-18 06:52:16,604 [shard 0] rpc - Service handler threw an exception: seastar::condition_variable_timed_out (Condition variable timed out)
```
To Fix: add better diagnostic logging (e.g. named semaphore) so we have a chance of narrowing these down. | test | error seastar condition variable timed out condition variable timed out this showed up as a ci failure and i cannot tell from the logs which condition variable has timed out this happened in noderesizetest test node resize but i m guessing this is a general error that can occur with any test considering that it is explicitly allowed in chaos tests error rpc service handler threw an exception seastar condition variable timed out condition variable timed out to fix add better diagnostic logging e g named semaphore so we have a chance of narrowing these down | 1 |
472,664 | 13,628,957,482 | IssuesEvent | 2020-09-24 14:32:27 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.facebook.com - video or audio doesn't play | browser-firefox engine-gecko priority-critical | <!-- @browser: Firefox 82.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 6.1; rv:82.0) Gecko/20100101 Firefox/82.0 -->
<!-- @reported_with: desktop-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/58744 -->
**URL**: https://www.facebook.com/messages/archived/t/2596043857177461
**Browser / Version**: Firefox 82.0
**Operating System**: Windows 7
**Tested Another Browser**: Yes Internet Explorer
**Problem type**: Video or audio doesn't play
**Description**: The video or audio does not play
**Steps to Reproduce**:
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20200922183749</li><li>channel: beta</li><li>hasTouchScreen: false</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2020/9/dd7b552a-d300-4700-ba22-bc539bc8a3a4)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.facebook.com - video or audio doesn't play - <!-- @browser: Firefox 82.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 6.1; rv:82.0) Gecko/20100101 Firefox/82.0 -->
<!-- @reported_with: desktop-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/58744 -->
**URL**: https://www.facebook.com/messages/archived/t/2596043857177461
**Browser / Version**: Firefox 82.0
**Operating System**: Windows 7
**Tested Another Browser**: Yes Internet Explorer
**Problem type**: Video or audio doesn't play
**Description**: The video or audio does not play
**Steps to Reproduce**:
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20200922183749</li><li>channel: beta</li><li>hasTouchScreen: false</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2020/9/dd7b552a-d300-4700-ba22-bc539bc8a3a4)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_test | video or audio doesn t play url browser version firefox operating system windows tested another browser yes internet explorer problem type video or audio doesn t play description the video or audio does not play steps to reproduce browser configuration gfx webrender all false gfx webrender blob images true gfx webrender enabled false image mem shared true buildid channel beta hastouchscreen false mixed active content blocked false mixed passive content blocked false tracking content blocked false from with ❤️ | 0 |
150,622 | 11,969,035,164 | IssuesEvent | 2020-04-06 09:39:03 | zeebe-io/zeebe | https://api.github.com/repos/zeebe-io/zeebe | closed | StreamProcessorTest#shouldCreateSnapshotAfterInterval is flaky | Scope: broker Status: In Progress Type: Unstable Test | **Description**
It seems the test sometimes is too fast and does not wait for the event to have been processed - or there is a bug. But I verified that the way we await processing is race-prone (is that correct to say? :sweat_smile:), so I think it is flaky.
Sample output:
```
Error
expected:<[tru]e> but was:<[fals]e>
Stacktrace
org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e>
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at io.zeebe.test.util.TestUtil$Invocation.until(TestUtil.java:91)
at io.zeebe.test.util.TestUtil$Invocation.until(TestUtil.java:64)
at io.zeebe.test.util.TestUtil.waitUntil(TestUtil.java:36)
at io.zeebe.engine.processor.StreamProcessorTest.shouldCreateSnapshotsAfterInterval(StreamProcessorTest.java:644)
```
From the output logs we can see that it skipped taking a snapshot because we were still on processed position -1.
```
16:50:52.220 [Broker-0-StreamProcessor-0] INFO io.zeebe.logstreams - Recovered state of partition 0 from snapshot at position -1
16:50:52.250 [Broker-0-SnapshotDirector-0] DEBUG io.zeebe.logstreams.snapshot - We will skip taking this snapshot, because we haven't processed something yet.
``` | 1.0 | StreamProcessorTest#shouldCreateSnapshotAfterInterval is flaky - **Description**
It seems the test sometimes is too fast and does not wait for the event to have been processed - or there is a bug. But I verified that the way we await processing is race-prone (is that correct to say? :sweat_smile:), so I think it is flaky.
Sample output:
```
Error
expected:<[tru]e> but was:<[fals]e>
Stacktrace
org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e>
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at io.zeebe.test.util.TestUtil$Invocation.until(TestUtil.java:91)
at io.zeebe.test.util.TestUtil$Invocation.until(TestUtil.java:64)
at io.zeebe.test.util.TestUtil.waitUntil(TestUtil.java:36)
at io.zeebe.engine.processor.StreamProcessorTest.shouldCreateSnapshotsAfterInterval(StreamProcessorTest.java:644)
```
From the output logs we can see that it skipped taking a snapshot because we were still on processed position -1.
```
16:50:52.220 [Broker-0-StreamProcessor-0] INFO io.zeebe.logstreams - Recovered state of partition 0 from snapshot at position -1
16:50:52.250 [Broker-0-SnapshotDirector-0] DEBUG io.zeebe.logstreams.snapshot - We will skip taking this snapshot, because we haven't processed something yet.
``` | test | streamprocessortest shouldcreatesnapshotafterinterval is flaky description it seems the test sometimes is too fast and does not wait for the event to have been processed or there is a bug but i verified that the way we await processing is race prone is that correct to say sweat smile so i think it is flaky sample output error expected but was stacktrace org junit comparisonfailure expected but was at java base jdk internal reflect nativeconstructoraccessorimpl native method at java base jdk internal reflect nativeconstructoraccessorimpl newinstance nativeconstructoraccessorimpl java at java base jdk internal reflect delegatingconstructoraccessorimpl newinstance delegatingconstructoraccessorimpl java at io zeebe test util testutil invocation until testutil java at io zeebe test util testutil invocation until testutil java at io zeebe test util testutil waituntil testutil java at io zeebe engine processor streamprocessortest shouldcreatesnapshotsafterinterval streamprocessortest java from the output logs we can see that it skipped taking a snapshot because we were still on processed position info io zeebe logstreams recovered state of partition from snapshot at position debug io zeebe logstreams snapshot we will skip taking this snapshot because we haven t processed something yet | 1 |
9,670 | 11,731,199,958 | IssuesEvent | 2020-03-10 23:21:06 | google/model-viewer | https://api.github.com/repos/google/model-viewer | closed | Interaction prompt does not animate in Shadow DOM in some browsers | arc: compatibility arc: interaction type: bug | ### Description
The animation prompt does not render properly in Safari or Firefox.
What it's supposed to look like:
<img width="371" alt="Screen Shot 2019-04-02 at 5 12 28 PM" src="https://user-images.githubusercontent.com/190692/55436507-83583080-556a-11e9-81ed-b5e6b14ebdea.png">
What it looks like:
<img width="222" alt="Screen Shot 2019-04-02 at 5 12 57 PM" src="https://user-images.githubusercontent.com/190692/55437070-0037da00-556c-11e9-99c5-2f5a6c876e40.png">
(it's also not animating in firefox)
I believe the issue is related to Shadow DOMs. SVG transforms seem to not have consistent behaviour when inside of a Shadow DOM. I isolated the issue to show that it is not related to model viewer:
#### Live Demo
https://codepen.io/pushmatrix/pen/XQmrvx
On Firefox the animation doesn't even happen. On Safari the animation happens, but some elements are off.
Here's a more minimal one with just a rotating triangle:
https://codepen.io/pushmatrix/pen/ZZbzPo.
The animation doesn't work on Firefox.
You can also see this behaviour in model viewer by loading it in Safari or Firefox, and clicking the model viewer to get focus, and waiting for the prompt to appear.
### Browser Affected
<!-- Check all that apply and please include the version tested -->
- [ ] Chrome
- [ ] Edge (not tested)
- [x] Firefox 66.0.2
- [ ] Helios (not tested)
- [ ] IE (not tested)
- [x] Safari 12.0.3
### OS
<!-- Check all that apply and please include the version tested -->
- [ ] Android (not tested)
- [x] iOS 12.2
- [ ] Linux (not tested)
- [x] MacOS 10.14.3
- [ ] Windows (not tested)
### Versions
This is version agnostic. The svg animation issue is happening regardless of whether it is in the model viewer or not.
| True | Interaction prompt does not animate in Shadow DOM in some browsers - ### Description
The animation prompt does not render properly in Safari or Firefox.
What it's supposed to look like:
<img width="371" alt="Screen Shot 2019-04-02 at 5 12 28 PM" src="https://user-images.githubusercontent.com/190692/55436507-83583080-556a-11e9-81ed-b5e6b14ebdea.png">
What it looks like:
<img width="222" alt="Screen Shot 2019-04-02 at 5 12 57 PM" src="https://user-images.githubusercontent.com/190692/55437070-0037da00-556c-11e9-99c5-2f5a6c876e40.png">
(it's also not animating in firefox)
I believe the issue is related to Shadow DOMs. SVG transforms seem to not have consistent behaviour when inside of a Shadow DOM. I isolated the issue to show that it is not related to model viewer:
#### Live Demo
https://codepen.io/pushmatrix/pen/XQmrvx
On Firefox the animation doesn't even happen. On Safari the animation happens, but some elements are off.
Here's a more minimal one with just a rotating triangle:
https://codepen.io/pushmatrix/pen/ZZbzPo.
The animation doesn't work on Firefox.
You can also see this behaviour in model viewer by loading it in Safari or Firefox, and clicking the model viewer to get focus, and waiting for the prompt to appear.
### Browser Affected
<!-- Check all that apply and please include the version tested -->
- [ ] Chrome
- [ ] Edge (not tested)
- [x] Firefox 66.0.2
- [ ] Helios (not tested)
- [ ] IE (not tested)
- [x] Safari 12.0.3
### OS
<!-- Check all that apply and please include the version tested -->
- [ ] Android (not tested)
- [x] iOS 12.2
- [ ] Linux (not tested)
- [x] MacOS 10.14.3
- [ ] Windows (not tested)
### Versions
This is version agnostic. The svg animation issue is happening regardless of whether it is in the model viewer or not.
| non_test | interaction prompt does not animate in shadow dom in some browsers description the animation prompt does not render properly in safari or firefox what it s supposed to look like img width alt screen shot at pm src what it looks like img width alt screen shot at pm src it s also not animating in firefox i believe the issue is related to shadow doms svg transforms seem to not have consistent behaviour when inside of a shadow dom i isolated the issue to show that it is not related to model viewer live demo on firefox the animation doesn t even happen on safari the animation happens but some elements are off here s a more minimal one with just a rotating triangle the animation doesn t work on firefox you can also see this behaviour in model viewer by loading it in safari or firefox and clicking the model viewer to get focus and waiting for the prompt to appear browser affected chrome edge not tested firefox helios not tested ie not tested safari os android not tested ios linux not tested macos windows not tested versions this is version agnostic the svg animation issue is happening regardless of whether it is in the model viewer or not | 0 |
310,024 | 26,694,708,130 | IssuesEvent | 2023-01-27 09:20:29 | privacyidea/php-client | https://api.github.com/repos/privacyidea/php-client | closed | Update the test utils | enhancement testing testing prio: low | Move the response strings to the utils, to simplify the tests and make them better to understand. | 2.0 | Update the test utils - Move the response strings to the utils, to simplify the tests and make them better to understand. | test | update the test utils move the response strings to the utils to simplify the tests and make them better to understand | 1 |
208,886 | 15,947,299,061 | IssuesEvent | 2021-04-15 03:09:25 | kubernetes-sigs/azuredisk-csi-driver | https://api.github.com/repos/kubernetes-sigs/azuredisk-csi-driver | opened | add ZRS disk e2e test | kind/test | **Is your feature request related to a problem?/Why is this needed**
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
**Describe the solution you'd like in detail**
<!-- A clear and concise description of what you want to happen. -->
Once ZRS disk is ready on westus2 region(end of April), we could add ZRS disk e2e test
**Describe alternatives you've considered**
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
**Additional context**
<!-- Add any other context or screenshots about the feature request here. -->
| 1.0 | add ZRS disk e2e test - **Is your feature request related to a problem?/Why is this needed**
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
**Describe the solution you'd like in detail**
<!-- A clear and concise description of what you want to happen. -->
Once ZRS disk is ready on westus2 region(end of April), we could add ZRS disk e2e test
**Describe alternatives you've considered**
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
**Additional context**
<!-- Add any other context or screenshots about the feature request here. -->
| test | add zrs disk test is your feature request related to a problem why is this needed describe the solution you d like in detail once zrs disk is ready on region end of april we could add zrs disk test describe alternatives you ve considered additional context | 1 |
208,770 | 15,932,137,873 | IssuesEvent | 2021-04-14 05:08:04 | jordan528/issues-demo | https://api.github.com/repos/jordan528/issues-demo | opened | ABAC_Level3 on PUT:/api/v1/bank-account/withdraw-amount | CVSS_3.1 8.1 Major NB-testing apisec |
Title: ABAC_Level3 Vulnerability on PUT:/api/v1/bank-account/withdraw-amount
Project: NB-testing
Description: The ABAC exploit allows an attacker to read, modify, delete, add and perform actions on customer/un-authorized data.
<style>strong { color: #ef5350!important;}</style><strong>Assertion </strong>
<b><font color="#ef5350">Name: </font></b> Attribute Based Access Control 3 (ABAC 3) <b><font color="#ef5350"><sup>( 1 )</sup></font></b><br> <br> <b><font color="#ef5350">Overview: </font></b> Access Control (or Authorization) is the process of granting or denying specific requests from a user, program, or process. Access control also involves the act of granting and revoking those privileges. Attribute Based Access Control (ABAC) will grant or deny user requests based on arbitrary attributes of the user and arbitrary attributes of the object, and environment conditions that may be globally recognized and more relevant to the policies at hand. <br> <br>'Attribute-based-access-control 3' identifies dependent and nested resource/data/record vulnerabilities. e.g. vulnerabilities in tasks which is nested within a project and the access-controls may only be applied at the project level. ABAC scanning identifies data/resource leak/attack vulnerabilities. Looks for private user/account data being illegally read, written, updated, deleted or operated by other users or tenants or accounts.<br> <br>This scanner requires a private-account/user to create private data/resources e.g. UserA. And it also requires other users who shouldn't have any access to UserA's data like UserB, UserC, & UserD based on your App multi-tenancy model. e.g. UserA can be a user from tenant/org-a and UserB can be a user in tenant-b and UserC can be a user in tenant-c with admin privileges.<br/> <br/>APIs tend to expose endpoints that handle object identifiers, creating a wide attack surface Level Access Control issue. Object-level authorization checks should be considered in every function that accesses a data source using input from the user.<br> <br> <b><font color="#ef5350">Severity: </font></b> OWASP 2019 API Top 10 ranks ABAC vulnerabilities at Top 1 position and is named Broken Object Level Authorization. <b><font color="#ef5350"><sup>( 2 )</sup></font></b> <br> <br> <b><font color="#ef5350">Vulnerability Impact: </font></b> With flawed or broken ABAC security control policy in place, The following are some of the consequences. <br> <br><ul> <li>Unauthorized access can result in data disclosure to unauthorized parties, data loss, or data manipulation.</li> <li>Unauthorized access to objects can also lead to full account takeover.</li> </ul> <b><font color="#ef5350">Exploitation: </font></b> Attackers can exploit API endpoints that are vulnerable to broken object level authorization by manipulating the ID of an object that is sent within the request. This may lead to unauthorized access to sensitive data. This issue is extremely common in API-based applications because the server component usually does not fully track the client’s state, and instead, relies more on parameters like object IDs, that are sent from the client to decide which objects to access. <br> <br> <b><font color="#ef5350">Remediation: </font></b> The following techniques may be checked for ensuring RBAC is in place <b><font color="#ef5350"><sup>( 2 ) ( 3 ) ( 4 )</sup></font></b>.<br><ul> <li>Implement a proper authorization mechanism that relies on the user policies and hierarchy.</li> <li>Prefer not to use an ID that has been sent from the client, but instead use an ID that is stored in the session object when accessing a database record by the record ID.</li> <li>Use an authorization mechanism to check if the logged-in user has access to perform the requested action on the record in every function that uses an client input to access a record in the database.</li> <li>Prefer to use random and unpredictable values as GUIDs for records’ IDs.</li> <li>Write tests to evaluate the authorization mechanism. Do not deploy vulnerable changes that break the tests.</li> </ul> <b><font color="#ef5350">References: </font></b><br> <ol> <li>Enforce Access Controls - https://owasp-top-10-proactive-controls-2018.readthedocs.io/en/latest/c7-enforce-access-controls.html</li> <li>OWASP 2019 API Top 10 - https://github.com/OWASP/API-Security/raw/master/2019/en/dist/owasp-api-security-top-10.pdf</li> <li>OWASP Access Control Cheat Sheet - https://cheatsheetseries.owasp.org/cheatsheets/Access_Control_Cheat_Sheet.html</li> <li>OWASP REST Security Cheat Sheet - https://cheatsheetseries.owasp.org/cheatsheets/REST_Security_Cheat_Sheet.html</li> </ol> <br>Risk: ABAC_Level3
Severity: Major
API Endpoint: http://95.217.118.53:8080/api/v1/bank-account/withdraw-amount
Environment: Master
Playbook: ApiV1BankAccountWithdrawAmountPutBankaccountuserbDisallowAbact3
Researcher: [apisec Bot]
QUICK TIPS
Suggestion: Add access-control checks on incoming requests against all data calls.
Effort Estimate: 2.0
Wire Logs:
IMPORTANT LINKS
Vulnerability Details:
https://cloud.fxlabs.io/#/app/projects/8a8081de7217c47801725dd1d8f478b9/recommendations/8a80933a78cabd920178cec7661903c7/details
Project:
https://cloud.fxlabs.io/#/app/projects/8a8081de7217c47801725dd1d8f478b9/jobs
Environment:
https://cloud.fxlabs.io/#/app/projects/8a8081de7217c47801725dd1d8f478b9/environments/8a8081de7217c47801725dd1d8ff78bb/edit
Scan Dashboard:
https://cloud.fxlabs.io/#/app/projects/8a8081de7217c47801725dd1d8f478b9/jobs/8a8081de7217c47801725dd263187a19/runs/8a80933a78cabd920178cec712c9035c
Playbook:
https://cloud.fxlabs.io/#/app/projects/8a8081de7217c47801725dd1d8f478b9/template/ApiV1BankAccountWithdrawAmountPutBankaccountuserbDisallowAbact3
Coverage:
https://cloud.fxlabs.io/#/app/projects/8a8081de7217c47801725dd1d8f478b9/configuration
Code Sample:
https://cloud.fxlabs.io/#/app/projects/8a8081de7217c47801725dd1d8f478b9/recommendations/8a80933a78cabd920178cec7661903c7/codesamples
PS: Please contact support@apisec.ai for apisec access and login issues.
--- apisec Bot --- | 1.0 | ABAC_Level3 on PUT:/api/v1/bank-account/withdraw-amount -
Title: ABAC_Level3 Vulnerability on PUT:/api/v1/bank-account/withdraw-amount
Project: NB-testing
Description: The ABAC exploit allows an attacker to read, modify, delete, add and perform actions on customer/un-authorized data.
<style>strong { color: #ef5350!important;}</style><strong>Assertion </strong>
<b><font color="#ef5350">Name: </font></b> Attribute Based Access Control 3 (ABAC 3) <b><font color="#ef5350"><sup>( 1 )</sup></font></b><br> <br> <b><font color="#ef5350">Overview: </font></b> Access Control (or Authorization) is the process of granting or denying specific requests from a user, program, or process. Access control also involves the act of granting and revoking those privileges. Attribute Based Access Control (ABAC) will grant or deny user requests based on arbitrary attributes of the user and arbitrary attributes of the object, and environment conditions that may be globally recognized and more relevant to the policies at hand. <br> <br>'Attribute-based-access-control 3' identifies dependent and nested resource/data/record vulnerabilities. e.g. vulnerabilities in tasks which is nested within a project and the access-controls may only be applied at the project level. ABAC scanning identifies data/resource leak/attack vulnerabilities. Looks for private user/account data being illegally read, written, updated, deleted or operated by other users or tenants or accounts.<br> <br>This scanner requires a private-account/user to create private data/resources e.g. UserA. And it also requires other users who shouldn't have any access to UserA's data like UserB, UserC, & UserD based on your App multi-tenancy model. e.g. UserA can be a user from tenant/org-a and UserB can be a user in tenant-b and UserC can be a user in tenant-c with admin privileges.<br/> <br/>APIs tend to expose endpoints that handle object identifiers, creating a wide attack surface Level Access Control issue. Object-level authorization checks should be considered in every function that accesses a data source using input from the user.<br> <br> <b><font color="#ef5350">Severity: </font></b> OWASP 2019 API Top 10 ranks ABAC vulnerabilities at Top 1 position and is named Broken Object Level Authorization. <b><font color="#ef5350"><sup>( 2 )</sup></font></b> <br> <br> <b><font color="#ef5350">Vulnerability Impact: </font></b> With flawed or broken ABAC security control policy in place, The following are some of the consequences. <br> <br><ul> <li>Unauthorized access can result in data disclosure to unauthorized parties, data loss, or data manipulation.</li> <li>Unauthorized access to objects can also lead to full account takeover.</li> </ul> <b><font color="#ef5350">Exploitation: </font></b> Attackers can exploit API endpoints that are vulnerable to broken object level authorization by manipulating the ID of an object that is sent within the request. This may lead to unauthorized access to sensitive data. This issue is extremely common in API-based applications because the server component usually does not fully track the client’s state, and instead, relies more on parameters like object IDs, that are sent from the client to decide which objects to access. <br> <br> <b><font color="#ef5350">Remediation: </font></b> The following techniques may be checked for ensuring RBAC is in place <b><font color="#ef5350"><sup>( 2 ) ( 3 ) ( 4 )</sup></font></b>.<br><ul> <li>Implement a proper authorization mechanism that relies on the user policies and hierarchy.</li> <li>Prefer not to use an ID that has been sent from the client, but instead use an ID that is stored in the session object when accessing a database record by the record ID.</li> <li>Use an authorization mechanism to check if the logged-in user has access to perform the requested action on the record in every function that uses an client input to access a record in the database.</li> <li>Prefer to use random and unpredictable values as GUIDs for records’ IDs.</li> <li>Write tests to evaluate the authorization mechanism. Do not deploy vulnerable changes that break the tests.</li> </ul> <b><font color="#ef5350">References: </font></b><br> <ol> <li>Enforce Access Controls - https://owasp-top-10-proactive-controls-2018.readthedocs.io/en/latest/c7-enforce-access-controls.html</li> <li>OWASP 2019 API Top 10 - https://github.com/OWASP/API-Security/raw/master/2019/en/dist/owasp-api-security-top-10.pdf</li> <li>OWASP Access Control Cheat Sheet - https://cheatsheetseries.owasp.org/cheatsheets/Access_Control_Cheat_Sheet.html</li> <li>OWASP REST Security Cheat Sheet - https://cheatsheetseries.owasp.org/cheatsheets/REST_Security_Cheat_Sheet.html</li> </ol> <br>Risk: ABAC_Level3
Severity: Major
API Endpoint: http://95.217.118.53:8080/api/v1/bank-account/withdraw-amount
Environment: Master
Playbook: ApiV1BankAccountWithdrawAmountPutBankaccountuserbDisallowAbact3
Researcher: [apisec Bot]
QUICK TIPS
Suggestion: Add access-control checks on incoming requests against all data calls.
Effort Estimate: 2.0
Wire Logs:
IMPORTANT LINKS
Vulnerability Details:
https://cloud.fxlabs.io/#/app/projects/8a8081de7217c47801725dd1d8f478b9/recommendations/8a80933a78cabd920178cec7661903c7/details
Project:
https://cloud.fxlabs.io/#/app/projects/8a8081de7217c47801725dd1d8f478b9/jobs
Environment:
https://cloud.fxlabs.io/#/app/projects/8a8081de7217c47801725dd1d8f478b9/environments/8a8081de7217c47801725dd1d8ff78bb/edit
Scan Dashboard:
https://cloud.fxlabs.io/#/app/projects/8a8081de7217c47801725dd1d8f478b9/jobs/8a8081de7217c47801725dd263187a19/runs/8a80933a78cabd920178cec712c9035c
Playbook:
https://cloud.fxlabs.io/#/app/projects/8a8081de7217c47801725dd1d8f478b9/template/ApiV1BankAccountWithdrawAmountPutBankaccountuserbDisallowAbact3
Coverage:
https://cloud.fxlabs.io/#/app/projects/8a8081de7217c47801725dd1d8f478b9/configuration
Code Sample:
https://cloud.fxlabs.io/#/app/projects/8a8081de7217c47801725dd1d8f478b9/recommendations/8a80933a78cabd920178cec7661903c7/codesamples
PS: Please contact support@apisec.ai for apisec access and login issues.
--- apisec Bot --- | test | abac on put api bank account withdraw amount title abac vulnerability on put api bank account withdraw amount project nb testing description the abac exploit allows an attacker to read modify delete add and perform actions on customer un authorized data strong color important assertion name attribute based access control abac overview access control or authorization is the process of granting or denying specific requests from a user program or process access control also involves the act of granting and revoking those privileges attribute based access control abac will grant or deny user requests based on arbitrary attributes of the user and arbitrary attributes of the object and environment conditions that may be globally recognized and more relevant to the policies at hand attribute based access control identifies dependent and nested resource data record vulnerabilities e g vulnerabilities in tasks which is nested within a project and the access controls may only be applied at the project level abac scanning identifies data resource leak attack vulnerabilities looks for private user account data being illegally read written updated deleted or operated by other users or tenants or accounts this scanner requires a private account user to create private data resources e g usera and it also requires other users who shouldn t have any access to usera s data like userb userc userd based on your app multi tenancy model e g usera can be a user from tenant org a and userb can be a user in tenant b and userc can be a user in tenant c with admin privileges apis tend to expose endpoints that handle object identifiers creating a wide attack surface level access control issue object level authorization checks should be considered in every function that accesses a data source using input from the user severity owasp api top ranks abac vulnerabilities at top position and is named broken object level authorization vulnerability impact with flawed or broken abac security control policy in place the following are some of the consequences unauthorized access can result in data disclosure to unauthorized parties data loss or data manipulation unauthorized access to objects can also lead to full account takeover exploitation attackers can exploit api endpoints that are vulnerable to broken object level authorization by manipulating the id of an object that is sent within the request this may lead to unauthorized access to sensitive data this issue is extremely common in api based applications because the server component usually does not fully track the client’s state and instead relies more on parameters like object ids that are sent from the client to decide which objects to access remediation the following techniques may be checked for ensuring rbac is in place implement a proper authorization mechanism that relies on the user policies and hierarchy prefer not to use an id that has been sent from the client but instead use an id that is stored in the session object when accessing a database record by the record id use an authorization mechanism to check if the logged in user has access to perform the requested action on the record in every function that uses an client input to access a record in the database prefer to use random and unpredictable values as guids for records’ ids write tests to evaluate the authorization mechanism do not deploy vulnerable changes that break the tests references enforce access controls owasp api top owasp access control cheat sheet owasp rest security cheat sheet risk abac severity major api endpoint environment master playbook researcher quick tips suggestion add access control checks on incoming requests against all data calls effort estimate wire logs important links vulnerability details project environment scan dashboard playbook coverage code sample ps please contact support apisec ai for apisec access and login issues apisec bot | 1 |
53,603 | 6,337,359,891 | IssuesEvent | 2017-07-26 23:41:01 | rust-lang/rust | https://api.github.com/repos/rust-lang/rust | closed | ICE: Shadowing a unit-like enum in a closure crashes compiler | C-bug E-needstest I-ICE | Shadowing a unit-like enum in a closure crashes compiler.
I tried this code:
```
struct Test;
fn main() {
|| {
let Test = 1;
};
}
```
I expected to see this happen: Failure message E0413
Instead, this happened: Compiler crash
```
driver.rs:5:13: 5:17 error: declaration of `Test` shadows an enum variant or unit-like struct in scope [E0413]
driver.rs:5 let Test = 1;
^~~~
driver.rs:5:13: 5:17 help: run `rustc --explain E0413` to see a detailed explanation
error: internal compiler error: ../src/librustc/middle/mem_categorization.rs:614: Def::Err in memory categorization
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
thread 'rustc' panicked at 'Box<Any>', ../src/libsyntax/errors/mod.rs:576
note: Run with `RUST_BACKTRACE=1` for a backtrace.
```
## Meta
`rustc --version --verbose`:
```
rustc 1.10.0-nightly (62e2b2fb7 2016-05-06)
binary: rustc
commit-hash: 62e2b2fb7acf5f8331781cd7128c754ed1b66c4f
commit-date: 2016-05-06
host: x86_64-unknown-linux-gnu
release: 1.10.0-nightly
```
Backtrace:
```
thread 'rustc' panicked at 'Box<Any>', ../src/libsyntax/errors/mod.rs:576
stack backtrace:
1: 0x7f95e967bd10 - std::sys::backtrace::tracing::imp::write::h9fb600083204ae7f
2: 0x7f95e968958b - std::panicking::default_hook::_$u7b$$u7b$closure$u7d$$u7d$::hca543c34f11229ac
3: 0x7f95e968912c - std::panicking::default_hook::hc2c969e7453d080c
4: 0x7f95e964e8cf - std::sys_common::unwind::begin_unwind_inner::h30e12d15ce2b2e25
5: 0x7f95e4ca6717 - std::sys_common::unwind::begin_unwind::h24c4c0fa2cfe995a
6: 0x7f95e4ca607e - syntax::errors::Handler::bug::h4846e60601033e50
7: 0x7f95e5d2fab2 - rustc::session::opt_span_bug_fmt::_$u7b$$u7b$closure$u7d$$u7d$::hf0fb5697f8f25f40
8: 0x7f95e5d2f942 - rustc::session::opt_span_bug_fmt::hc581ba88c4e2ec53
9: 0x7f95e5d47826 - rustc::session::bug_fmt::had96c08cb43bd8a1
10: 0x7f95e5ebecb0 - rustc::middle::mem_categorization::MemCategorizationContext::cat_def::h1e6d1d71a3ac3d06
11: 0x7f95e5ebcce9 - rustc::middle::mem_categorization::MemCategorizationContext::cat_pattern_::h688ac5141fed7601
12: 0x7f95e5eba413 - rustc::middle::expr_use_visitor::ExprUseVisitor::walk_pat::h95254f9d39fba4a1
13: 0x7f95e5eb5cf3 - rustc::middle::expr_use_visitor::ExprUseVisitor::walk_irrefutable_pat::h7304094e79d13564
14: 0x7f95e5eb8d46 - rustc::middle::expr_use_visitor::ExprUseVisitor::walk_stmt::h8bc9b54fe3fcb6f0
15: 0x7f95e5eb7f0e - rustc::middle::expr_use_visitor::ExprUseVisitor::walk_expr::h9cca31560139037e
16: 0x7f95e5eb5e84 - rustc::middle::expr_use_visitor::ExprUseVisitor::consume_expr::ha16e99aa14e61262
17: 0x7f95e5eb5b65 - rustc::middle::expr_use_visitor::ExprUseVisitor::walk_fn::h5a4a2ab4ebcdb73a
18: 0x7f95e6cb635d - _<check..upvar..AdjustBorrowKind<'a, 'tcx> as rustc..hir..intravisit..Visitor<'v>>::visit_fn::hba13755c61d6d401
19: 0x7f95e6cb5e48 - rustc::hir::intravisit::walk_expr::h4743b97a2ee4072c
20: 0x7f95e6c14a5a - rustc_typeck::check::check_bare_fn::h7e4c2ad58d1814dd
21: 0x7f95e6c12196 - rustc_typeck::check::check_item_body::h7ffec660fc242796
22: 0x7f95e6c0a011 - rustc_typeck::check::check_item_bodies::ha729008a2e67410e
23: 0x7f95e6c02012 - rustc_typeck::check_crate::hb08ba31a6a5f65b5
24: 0x7f95e9bd0860 - rustc_driver::driver::phase_3_run_analysis_passes::_$u7b$$u7b$closure$u7d$$u7d$::hfdd8d88ff571b474
25: 0x7f95e9bce8be - rustc::ty::context::TyCtxt::create_and_enter::ha551c2427049829f
26: 0x7f95e9b9a285 - rustc_driver::driver::compile_input::h0629572e6f316b31
27: 0x7f95e9b8a4fd - rustc_driver::run_compiler::h8902aebf8b1849a8
28: 0x7f95e9b877bd - std::sys_common::unwind::try::try_fn::h4c74456035d0fcc7
29: 0x7f95e96794eb - __rust_try
30: 0x7f95e967947d - std::sys_common::unwind::inner_try::h47a4d9cd4a369dcd
31: 0x7f95e9b881ea - _<F as std..boxed..FnBox<A>>::call_box::h27f542a39f1d61ef
32: 0x7f95e96876f4 - std::sys::thread::Thread::new::thread_start::h6f266e069bf4ec2b
33: 0x7f95e1424473 - start_thread
34: 0x7f95e92e5acc - clone
35: 0x0 - <unknown>
```
| 1.0 | ICE: Shadowing a unit-like enum in a closure crashes compiler - Shadowing a unit-like enum in a closure crashes compiler.
I tried this code:
```
struct Test;
fn main() {
|| {
let Test = 1;
};
}
```
I expected to see this happen: Failure message E0413
Instead, this happened: Compiler crash
```
driver.rs:5:13: 5:17 error: declaration of `Test` shadows an enum variant or unit-like struct in scope [E0413]
driver.rs:5 let Test = 1;
^~~~
driver.rs:5:13: 5:17 help: run `rustc --explain E0413` to see a detailed explanation
error: internal compiler error: ../src/librustc/middle/mem_categorization.rs:614: Def::Err in memory categorization
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
thread 'rustc' panicked at 'Box<Any>', ../src/libsyntax/errors/mod.rs:576
note: Run with `RUST_BACKTRACE=1` for a backtrace.
```
## Meta
`rustc --version --verbose`:
```
rustc 1.10.0-nightly (62e2b2fb7 2016-05-06)
binary: rustc
commit-hash: 62e2b2fb7acf5f8331781cd7128c754ed1b66c4f
commit-date: 2016-05-06
host: x86_64-unknown-linux-gnu
release: 1.10.0-nightly
```
Backtrace:
```
thread 'rustc' panicked at 'Box<Any>', ../src/libsyntax/errors/mod.rs:576
stack backtrace:
1: 0x7f95e967bd10 - std::sys::backtrace::tracing::imp::write::h9fb600083204ae7f
2: 0x7f95e968958b - std::panicking::default_hook::_$u7b$$u7b$closure$u7d$$u7d$::hca543c34f11229ac
3: 0x7f95e968912c - std::panicking::default_hook::hc2c969e7453d080c
4: 0x7f95e964e8cf - std::sys_common::unwind::begin_unwind_inner::h30e12d15ce2b2e25
5: 0x7f95e4ca6717 - std::sys_common::unwind::begin_unwind::h24c4c0fa2cfe995a
6: 0x7f95e4ca607e - syntax::errors::Handler::bug::h4846e60601033e50
7: 0x7f95e5d2fab2 - rustc::session::opt_span_bug_fmt::_$u7b$$u7b$closure$u7d$$u7d$::hf0fb5697f8f25f40
8: 0x7f95e5d2f942 - rustc::session::opt_span_bug_fmt::hc581ba88c4e2ec53
9: 0x7f95e5d47826 - rustc::session::bug_fmt::had96c08cb43bd8a1
10: 0x7f95e5ebecb0 - rustc::middle::mem_categorization::MemCategorizationContext::cat_def::h1e6d1d71a3ac3d06
11: 0x7f95e5ebcce9 - rustc::middle::mem_categorization::MemCategorizationContext::cat_pattern_::h688ac5141fed7601
12: 0x7f95e5eba413 - rustc::middle::expr_use_visitor::ExprUseVisitor::walk_pat::h95254f9d39fba4a1
13: 0x7f95e5eb5cf3 - rustc::middle::expr_use_visitor::ExprUseVisitor::walk_irrefutable_pat::h7304094e79d13564
14: 0x7f95e5eb8d46 - rustc::middle::expr_use_visitor::ExprUseVisitor::walk_stmt::h8bc9b54fe3fcb6f0
15: 0x7f95e5eb7f0e - rustc::middle::expr_use_visitor::ExprUseVisitor::walk_expr::h9cca31560139037e
16: 0x7f95e5eb5e84 - rustc::middle::expr_use_visitor::ExprUseVisitor::consume_expr::ha16e99aa14e61262
17: 0x7f95e5eb5b65 - rustc::middle::expr_use_visitor::ExprUseVisitor::walk_fn::h5a4a2ab4ebcdb73a
18: 0x7f95e6cb635d - _<check..upvar..AdjustBorrowKind<'a, 'tcx> as rustc..hir..intravisit..Visitor<'v>>::visit_fn::hba13755c61d6d401
19: 0x7f95e6cb5e48 - rustc::hir::intravisit::walk_expr::h4743b97a2ee4072c
20: 0x7f95e6c14a5a - rustc_typeck::check::check_bare_fn::h7e4c2ad58d1814dd
21: 0x7f95e6c12196 - rustc_typeck::check::check_item_body::h7ffec660fc242796
22: 0x7f95e6c0a011 - rustc_typeck::check::check_item_bodies::ha729008a2e67410e
23: 0x7f95e6c02012 - rustc_typeck::check_crate::hb08ba31a6a5f65b5
24: 0x7f95e9bd0860 - rustc_driver::driver::phase_3_run_analysis_passes::_$u7b$$u7b$closure$u7d$$u7d$::hfdd8d88ff571b474
25: 0x7f95e9bce8be - rustc::ty::context::TyCtxt::create_and_enter::ha551c2427049829f
26: 0x7f95e9b9a285 - rustc_driver::driver::compile_input::h0629572e6f316b31
27: 0x7f95e9b8a4fd - rustc_driver::run_compiler::h8902aebf8b1849a8
28: 0x7f95e9b877bd - std::sys_common::unwind::try::try_fn::h4c74456035d0fcc7
29: 0x7f95e96794eb - __rust_try
30: 0x7f95e967947d - std::sys_common::unwind::inner_try::h47a4d9cd4a369dcd
31: 0x7f95e9b881ea - _<F as std..boxed..FnBox<A>>::call_box::h27f542a39f1d61ef
32: 0x7f95e96876f4 - std::sys::thread::Thread::new::thread_start::h6f266e069bf4ec2b
33: 0x7f95e1424473 - start_thread
34: 0x7f95e92e5acc - clone
35: 0x0 - <unknown>
```
| test | ice shadowing a unit like enum in a closure crashes compiler shadowing a unit like enum in a closure crashes compiler i tried this code struct test fn main let test i expected to see this happen failure message instead this happened compiler crash driver rs error declaration of test shadows an enum variant or unit like struct in scope driver rs let test driver rs help run rustc explain to see a detailed explanation error internal compiler error src librustc middle mem categorization rs def err in memory categorization note the compiler unexpectedly panicked this is a bug note we would appreciate a bug report thread rustc panicked at box src libsyntax errors mod rs note run with rust backtrace for a backtrace meta rustc version verbose rustc nightly binary rustc commit hash commit date host unknown linux gnu release nightly backtrace thread rustc panicked at box src libsyntax errors mod rs stack backtrace std sys backtrace tracing imp write std panicking default hook closure std panicking default hook std sys common unwind begin unwind inner std sys common unwind begin unwind syntax errors handler bug rustc session opt span bug fmt closure rustc session opt span bug fmt rustc session bug fmt rustc middle mem categorization memcategorizationcontext cat def rustc middle mem categorization memcategorizationcontext cat pattern rustc middle expr use visitor exprusevisitor walk pat rustc middle expr use visitor exprusevisitor walk irrefutable pat rustc middle expr use visitor exprusevisitor walk stmt rustc middle expr use visitor exprusevisitor walk expr rustc middle expr use visitor exprusevisitor consume expr rustc middle expr use visitor exprusevisitor walk fn as rustc hir intravisit visitor visit fn rustc hir intravisit walk expr rustc typeck check check bare fn rustc typeck check check item body rustc typeck check check item bodies rustc typeck check crate rustc driver driver phase run analysis passes closure rustc ty context tyctxt create and enter rustc driver driver compile input rustc driver run compiler std sys common unwind try try fn rust try std sys common unwind inner try call box std sys thread thread new thread start start thread clone | 1 |
183,454 | 14,232,229,297 | IssuesEvent | 2020-11-18 10:30:32 | secureCodeBox/secureCodeBox | https://api.github.com/repos/secureCodeBox/secureCodeBox | closed | 👮♂️ Add End2End Integration Tests for the SSLyze Scanner Integration | security scanner testing | As a secureCodeBox developer i would like to have some end-to-end integration tests for the SSLyze security scanner to ensure its correctness during the development process.
There are already existing integration tests for other security scanners but for now SSLyze is missing: https://github.com/secureCodeBox/secureCodeBox/tree/main/tests/integration/scanner | 1.0 | 👮♂️ Add End2End Integration Tests for the SSLyze Scanner Integration - As a secureCodeBox developer i would like to have some end-to-end integration tests for the SSLyze security scanner to ensure its correctness during the development process.
There are already existing integration tests for other security scanners but for now SSLyze is missing: https://github.com/secureCodeBox/secureCodeBox/tree/main/tests/integration/scanner | test | 👮♂️ add integration tests for the sslyze scanner integration as a securecodebox developer i would like to have some end to end integration tests for the sslyze security scanner to ensure its correctness during the development process there are already existing integration tests for other security scanners but for now sslyze is missing | 1 |
348,534 | 31,624,898,294 | IssuesEvent | 2023-09-06 04:05:54 | exograph/exograph | https://api.github.com/repos/exograph/exograph | opened | Make init.gql format the same as exotest | int-test | Currently, "init*.gql" files allow only one operation. As a result, it is not possible to, for example, perform multiple initialization on behalf of multiple auth users. Using a variable bound in one initialization operation in another is also impossible.
We can make "init*.gql" and "*.exotest" have the same format (including assertions, which may come in handy, sometimes). It will also be easier to explain the format. | 1.0 | Make init.gql format the same as exotest - Currently, "init*.gql" files allow only one operation. As a result, it is not possible to, for example, perform multiple initialization on behalf of multiple auth users. Using a variable bound in one initialization operation in another is also impossible.
We can make "init*.gql" and "*.exotest" have the same format (including assertions, which may come in handy, sometimes). It will also be easier to explain the format. | test | make init gql format the same as exotest currently init gql files allow only one operation as a result it is not possible to for example perform multiple initialization on behalf of multiple auth users using a variable bound in one initialization operation in another is also impossible we can make init gql and exotest have the same format including assertions which may come in handy sometimes it will also be easier to explain the format | 1 |
45,594 | 5,720,632,774 | IssuesEvent | 2017-04-20 02:40:44 | ushahidi/platform | https://api.github.com/repos/ushahidi/platform | closed | Private survey and task fields | P1 - Immediate Stage: Testing Theme: Security and privacy Theme: Surveys | ### Expected behaviour
I can make a specific survey field, or task field, only visable to the logged in users, or by certain role. Particularly when doing verification, I want to include the original post details from FB for our internal team, but they have PII on them so I dont' want them published. This means I have to delete the content or not publish it.
### Actual behaviour
All fields are public
### Steps to reproduce the behaviour/error | 1.0 | Private survey and task fields - ### Expected behaviour
I can make a specific survey field, or task field, only visable to the logged in users, or by certain role. Particularly when doing verification, I want to include the original post details from FB for our internal team, but they have PII on them so I dont' want them published. This means I have to delete the content or not publish it.
### Actual behaviour
All fields are public
### Steps to reproduce the behaviour/error | test | private survey and task fields expected behaviour i can make a specific survey field or task field only visable to the logged in users or by certain role particularly when doing verification i want to include the original post details from fb for our internal team but they have pii on them so i dont want them published this means i have to delete the content or not publish it actual behaviour all fields are public steps to reproduce the behaviour error | 1 |
175,140 | 6,547,496,838 | IssuesEvent | 2017-09-04 15:02:16 | craftercms/craftercms | https://api.github.com/repos/craftercms/craftercms | closed | [studio-ui] Change template fails when changing template from page to section defaults | bug Priority: Medium | Steps to reproduce:
1. Go to the Site Dropdown of the site created previously (preconditions)
2. Create a Folder under Pages/Home tree (name: mytest)
3. Create a child folder under folder above (name: big-tree1)
4. Copy the next pages of the Home root folder (and paste those into the big-tree1):
5. Style
6. Health
7. Entertainment
8. Publish all on big-tree1 folder
9. Copy big-tree1 folder (leave selected all the content)
10. Right click in the Home and select paste
11. Go to big-tree1 just created folder (of Home)
12. Select any of the pages into it (e.g: Style) and right click
13. Select Change Template
14. Click on Yes of the Change Template Warning
15. Select Section Defaults and click on ok
16. Leave as default all in the form, and click on save and close
In the logs there is a NPE stack trace or message:
"Failed to extract dependencies. Content not found for site: <my_site>, path: <my_path>"
It is caused by invalid parameters sent by ui.
Example:
site = "craftercms1251"
oldContentPath = "/site/website/big-tree1/health/index.xml"
path = "/site/website/big-tree1/health/health.xml"
fileName = "index.xml"
contentType = "/component/level-descriptor"
createFolders = "true"
edit = null
unlock = "true"
createFolder = true
Issue discovered with https://github.com/craftercms/craftercms/issues/1251 use case | 1.0 | [studio-ui] Change template fails when changing template from page to section defaults - Steps to reproduce:
1. Go to the Site Dropdown of the site created previously (preconditions)
2. Create a Folder under Pages/Home tree (name: mytest)
3. Create a child folder under folder above (name: big-tree1)
4. Copy the next pages of the Home root folder (and paste those into the big-tree1):
5. Style
6. Health
7. Entertainment
8. Publish all on big-tree1 folder
9. Copy big-tree1 folder (leave selected all the content)
10. Right click in the Home and select paste
11. Go to big-tree1 just created folder (of Home)
12. Select any of the pages into it (e.g: Style) and right click
13. Select Change Template
14. Click on Yes of the Change Template Warning
15. Select Section Defaults and click on ok
16. Leave as default all in the form, and click on save and close
In the logs there is a NPE stack trace or message:
"Failed to extract dependencies. Content not found for site: <my_site>, path: <my_path>"
It is caused by invalid parameters sent by ui.
Example:
site = "craftercms1251"
oldContentPath = "/site/website/big-tree1/health/index.xml"
path = "/site/website/big-tree1/health/health.xml"
fileName = "index.xml"
contentType = "/component/level-descriptor"
createFolders = "true"
edit = null
unlock = "true"
createFolder = true
Issue discovered with https://github.com/craftercms/craftercms/issues/1251 use case | non_test | change template fails when changing template from page to section defaults steps to reproduce go to the site dropdown of the site created previously preconditions create a folder under pages home tree name mytest create a child folder under folder above name big copy the next pages of the home root folder and paste those into the big style health entertainment publish all on big folder copy big folder leave selected all the content right click in the home and select paste go to big just created folder of home select any of the pages into it e g style and right click select change template click on yes of the change template warning select section defaults and click on ok leave as default all in the form and click on save and close in the logs there is a npe stack trace or message failed to extract dependencies content not found for site path it is caused by invalid parameters sent by ui example site oldcontentpath site website big health index xml path site website big health health xml filename index xml contenttype component level descriptor createfolders true edit null unlock true createfolder true issue discovered with use case | 0 |
333,992 | 29,820,331,390 | IssuesEvent | 2023-06-17 01:29:07 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | reopened | Fix manipulation.test_roll | Sub Task Failing Test | | | |
|---|---|
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5051015638/jobs/9062401964" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5051015638/jobs/9062401964" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5051015638/jobs/9062401964" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5051015638/jobs/9062401964" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="null" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
| 1.0 | Fix manipulation.test_roll - | | |
|---|---|
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5051015638/jobs/9062401964" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5051015638/jobs/9062401964" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5051015638/jobs/9062401964" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5051015638/jobs/9062401964" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="null" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
| test | fix manipulation test roll tensorflow img src torch img src numpy img src jax img src paddle img src | 1 |
15,843 | 3,487,405,163 | IssuesEvent | 2016-01-01 21:38:29 | FreeCodeCamp/FreeCodeCamp | https://api.github.com/repos/FreeCodeCamp/FreeCodeCamp | closed | Waypoint: Local Scope and Functions | confirmed help wanted tests | Challenge [Waypoint: Local Scope and Functions](http://www.freecodecamp.com/challenges/waypoint-local-scope-and-functions#?solution=function%20myFunction()%20%7B%0A%20%20var%20myVar%20%3D%205%3B%20%20%0A%20%20console.log(myVar)%3B%0A%7D%0AmyFunction()%3B%0A%0A%2F%2F%20run%20and%20check%20the%20console%20%0A%2F%2F%20myVar%20is%20not%20defined%20outside%20of%20myFunction%0A%0A%2F%2F%20now%20remove%20the%20console.log%20line%20to%20pass%20the%20test%0A%0A) has an issue.
User Agent is: <code>Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.48 Safari/537.36</code>.
The test asks you to remove the second console.log() to pass. When you remove the second console.log() it still fails. You have to remove both console.log() calls to pass(including the one inside myFunction().)
Reproducible every time by removing the console.log() outside of myFunction(), as asked by test. I'm assuming this is a bug in the test and not the text as there's no reason to remove the console.log() call within myFunction(). | 1.0 | Waypoint: Local Scope and Functions - Challenge [Waypoint: Local Scope and Functions](http://www.freecodecamp.com/challenges/waypoint-local-scope-and-functions#?solution=function%20myFunction()%20%7B%0A%20%20var%20myVar%20%3D%205%3B%20%20%0A%20%20console.log(myVar)%3B%0A%7D%0AmyFunction()%3B%0A%0A%2F%2F%20run%20and%20check%20the%20console%20%0A%2F%2F%20myVar%20is%20not%20defined%20outside%20of%20myFunction%0A%0A%2F%2F%20now%20remove%20the%20console.log%20line%20to%20pass%20the%20test%0A%0A) has an issue.
User Agent is: <code>Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.48 Safari/537.36</code>.
The test asks you to remove the second console.log() to pass. When you remove the second console.log() it still fails. You have to remove both console.log() calls to pass(including the one inside myFunction().)
Reproducible every time by removing the console.log() outside of myFunction(), as asked by test. I'm assuming this is a bug in the test and not the text as there's no reason to remove the console.log() call within myFunction(). | test | waypoint local scope and functions challenge has an issue user agent is mozilla macintosh intel mac os x applewebkit khtml like gecko chrome safari the test asks you to remove the second console log to pass when you remove the second console log it still fails you have to remove both console log calls to pass including the one inside myfunction reproducible every time by removing the console log outside of myfunction as asked by test i m assuming this is a bug in the test and not the text as there s no reason to remove the console log call within myfunction | 1 |
102,284 | 31,884,702,379 | IssuesEvent | 2023-09-16 20:10:27 | moby/moby | https://api.github.com/repos/moby/moby | closed | --oom-kill-disable not available as build option | area/builder kind/enhancement | I'm running a machine on which multiple docker containers are running and where new images are build at the same time. To prevent the intermediate containers created during the build from using too much memory (so the other running containers are not deprived from memory), I've limited the maximum memory the build container is allowed to use using `docker build -f dockerfile --pull --memory="512m" -t test .`
I've noticed that this does help restricting memory usage, but occasionally can lead to the oom killer being triggered:
```
Mar 22 17:49:28 37-97-165-17 kernel: [97823.482993] grunt invoked oom-killer: gfp_mask=0x24000c0, order=0, oom_score_adj=0
Mar 22 17:49:28 37-97-165-17 kernel: [97823.482999] grunt cpuset=112dcd167f8491026f719a58b3b87d69e63b3ec666146f21270da8307ed38810 mems_allowed=0
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483008] CPU: 1 PID: 28564 Comm: grunt Not tainted 4.4.0-67-generic #88-Ubuntu
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483011] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org 04/01/2014
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483019] 0000000000000286 00000000445df54c ffff8800749c7c68 ffffffff813f86d3
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483024] ffff8800749c7d48 ffff88000a3c5940 ffff8800749c7cd8 ffffffff8120b24e
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483029] ffff88013fd16dc0 ffff8800749c7ca8 ffffffff811922fb ffff880002e1d940
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483033] Call Trace:
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483047] [<ffffffff813f86d3>] dump_stack+0x63/0x90
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483053] [<ffffffff8120b24e>] dump_header+0x5a/0x1c5
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483058] [<ffffffff811922fb>] ? find_lock_task_mm+0x3b/0x80
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483062] [<ffffffff811928c2>] oom_kill_process+0x202/0x3c0
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483067] [<ffffffff811feec4>] ? mem_cgroup_iter+0x204/0x390
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483072] [<ffffffff81200f23>] mem_cgroup_out_of_memory+0x2b3/0x300
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483077] [<ffffffff81201cf8>] mem_cgroup_oom_synchronize+0x338/0x350
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483081] [<ffffffff811fcdd0>] ? kzalloc_node.constprop.49+0x20/0x20
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483085] [<ffffffff81192f74>] pagefault_out_of_memory+0x44/0xc0
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483090] [<ffffffff8106b2b2>] mm_fault_error+0x82/0x160
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483094] [<ffffffff8106b768>] __do_page_fault+0x3d8/0x400
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483097] [<ffffffff8106b7f7>] trace_do_page_fault+0x37/0xe0
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483102] [<ffffffff81063ef9>] do_async_page_fault+0x19/0x70
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483106] [<ffffffff8183e828>] async_page_fault+0x28/0x30
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483153] Task in /docker/112dcd167f8491026f719a58b3b87d69e63b3ec666146f21270da8307ed38810 killed as a result of limit of /docker/112dcd167f8491026f719a58b3b87d69e63b3ec666146f21270da8307ed38810
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483161] memory: usage 524184kB, limit 524288kB, failcnt 249307
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483164] memory+swap: usage 1048576kB, limit 1048576kB, failcnt 6738
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483166] kmem: usage 6296kB, limit 9007199254740988kB, failcnt 0
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483168] Memory cgroup stats for /docker/112dcd167f8491026f719a58b3b87d69e63b3ec666146f21270da8307ed38810: cache:128KB rss:517760KB rss_huge:0KB mapped_file:44KB dirty:0KB writeback:0KB swap:524392KB inactive_anon:259084KB active_anon:258676KB inactive_file:64KB active_file:64KB unevictable:0KB
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483187] [ pid ] uid tgid total_vm rss nr_ptes nr_pmds swapents oom_score_adj name
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483431] [28211] 0 28211 1084 171 8 3 25 0 sh
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483436] [28253] 0 28253 226297 2986 64 28 6657 0 grunt
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483440] [28504] 0 28504 233514 4339 77 41 9373 0 grunt
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483443] [28564] 0 28564 504064 131255 954 769 114997 0 grunt
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483450] Memory cgroup out of memory: Kill process 28564 (grunt) score 945 or sacrifice child
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483573] Killed process 28564 (grunt) total-vm:2016256kB, anon-rss:512408kB, file-rss:12612kB
```
Would it be nice to disable the oom-killer for build containers, just as this is an option with `docker run`? | 1.0 | --oom-kill-disable not available as build option - I'm running a machine on which multiple docker containers are running and where new images are build at the same time. To prevent the intermediate containers created during the build from using too much memory (so the other running containers are not deprived from memory), I've limited the maximum memory the build container is allowed to use using `docker build -f dockerfile --pull --memory="512m" -t test .`
I've noticed that this does help restricting memory usage, but occasionally can lead to the oom killer being triggered:
```
Mar 22 17:49:28 37-97-165-17 kernel: [97823.482993] grunt invoked oom-killer: gfp_mask=0x24000c0, order=0, oom_score_adj=0
Mar 22 17:49:28 37-97-165-17 kernel: [97823.482999] grunt cpuset=112dcd167f8491026f719a58b3b87d69e63b3ec666146f21270da8307ed38810 mems_allowed=0
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483008] CPU: 1 PID: 28564 Comm: grunt Not tainted 4.4.0-67-generic #88-Ubuntu
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483011] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org 04/01/2014
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483019] 0000000000000286 00000000445df54c ffff8800749c7c68 ffffffff813f86d3
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483024] ffff8800749c7d48 ffff88000a3c5940 ffff8800749c7cd8 ffffffff8120b24e
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483029] ffff88013fd16dc0 ffff8800749c7ca8 ffffffff811922fb ffff880002e1d940
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483033] Call Trace:
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483047] [<ffffffff813f86d3>] dump_stack+0x63/0x90
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483053] [<ffffffff8120b24e>] dump_header+0x5a/0x1c5
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483058] [<ffffffff811922fb>] ? find_lock_task_mm+0x3b/0x80
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483062] [<ffffffff811928c2>] oom_kill_process+0x202/0x3c0
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483067] [<ffffffff811feec4>] ? mem_cgroup_iter+0x204/0x390
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483072] [<ffffffff81200f23>] mem_cgroup_out_of_memory+0x2b3/0x300
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483077] [<ffffffff81201cf8>] mem_cgroup_oom_synchronize+0x338/0x350
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483081] [<ffffffff811fcdd0>] ? kzalloc_node.constprop.49+0x20/0x20
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483085] [<ffffffff81192f74>] pagefault_out_of_memory+0x44/0xc0
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483090] [<ffffffff8106b2b2>] mm_fault_error+0x82/0x160
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483094] [<ffffffff8106b768>] __do_page_fault+0x3d8/0x400
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483097] [<ffffffff8106b7f7>] trace_do_page_fault+0x37/0xe0
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483102] [<ffffffff81063ef9>] do_async_page_fault+0x19/0x70
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483106] [<ffffffff8183e828>] async_page_fault+0x28/0x30
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483153] Task in /docker/112dcd167f8491026f719a58b3b87d69e63b3ec666146f21270da8307ed38810 killed as a result of limit of /docker/112dcd167f8491026f719a58b3b87d69e63b3ec666146f21270da8307ed38810
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483161] memory: usage 524184kB, limit 524288kB, failcnt 249307
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483164] memory+swap: usage 1048576kB, limit 1048576kB, failcnt 6738
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483166] kmem: usage 6296kB, limit 9007199254740988kB, failcnt 0
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483168] Memory cgroup stats for /docker/112dcd167f8491026f719a58b3b87d69e63b3ec666146f21270da8307ed38810: cache:128KB rss:517760KB rss_huge:0KB mapped_file:44KB dirty:0KB writeback:0KB swap:524392KB inactive_anon:259084KB active_anon:258676KB inactive_file:64KB active_file:64KB unevictable:0KB
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483187] [ pid ] uid tgid total_vm rss nr_ptes nr_pmds swapents oom_score_adj name
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483431] [28211] 0 28211 1084 171 8 3 25 0 sh
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483436] [28253] 0 28253 226297 2986 64 28 6657 0 grunt
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483440] [28504] 0 28504 233514 4339 77 41 9373 0 grunt
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483443] [28564] 0 28564 504064 131255 954 769 114997 0 grunt
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483450] Memory cgroup out of memory: Kill process 28564 (grunt) score 945 or sacrifice child
Mar 22 17:49:28 37-97-165-17 kernel: [97823.483573] Killed process 28564 (grunt) total-vm:2016256kB, anon-rss:512408kB, file-rss:12612kB
```
Would it be nice to disable the oom-killer for build containers, just as this is an option with `docker run`? | non_test | oom kill disable not available as build option i m running a machine on which multiple docker containers are running and where new images are build at the same time to prevent the intermediate containers created during the build from using too much memory so the other running containers are not deprived from memory i ve limited the maximum memory the build container is allowed to use using docker build f dockerfile pull memory t test i ve noticed that this does help restricting memory usage but occasionally can lead to the oom killer being triggered mar kernel grunt invoked oom killer gfp mask order oom score adj mar kernel grunt cpuset mems allowed mar kernel cpu pid comm grunt not tainted generic ubuntu mar kernel hardware name qemu standard pc piix bios rel prebuilt qemu project org mar kernel mar kernel mar kernel mar kernel call trace mar kernel dump stack mar kernel dump header mar kernel find lock task mm mar kernel oom kill process mar kernel mem cgroup iter mar kernel mem cgroup out of memory mar kernel mem cgroup oom synchronize mar kernel kzalloc node constprop mar kernel pagefault out of memory mar kernel mm fault error mar kernel do page fault mar kernel trace do page fault mar kernel do async page fault mar kernel async page fault mar kernel task in docker killed as a result of limit of docker mar kernel memory usage limit failcnt mar kernel memory swap usage limit failcnt mar kernel kmem usage limit failcnt mar kernel memory cgroup stats for docker cache rss rss huge mapped file dirty writeback swap inactive anon active anon inactive file active file unevictable mar kernel uid tgid total vm rss nr ptes nr pmds swapents oom score adj name mar kernel sh mar kernel grunt mar kernel grunt mar kernel grunt mar kernel memory cgroup out of memory kill process grunt score or sacrifice child mar kernel killed process grunt total vm anon rss file rss would it be nice to disable the oom killer for build containers just as this is an option with docker run | 0 |
306,197 | 26,447,103,087 | IssuesEvent | 2023-01-16 08:21:56 | airbytehq/airbyte | https://api.github.com/repos/airbytehq/airbyte | closed | Source Salesforce: enable `high` test strictness level in SAT | type/enhancement area/connectors team/connectors-python test-strictness-level | ## What
A `test_strictness_level` field was introduced to Source Acceptance Tests (SAT).
Salesforce is a generally_available connector, we want it to have a `high` test strictness level.
**This will help**:
- maximize the SAT coverage on this connector.
- document its potential weaknesses in term of test coverage.
## How
1. Migrate the existing `acceptance-test-config.yml` file to the latest configuration format. (See instructions [here](https://github.com/airbytehq/airbyte/blob/master/airbyte-integrations/bases/source-acceptance-test/README.md#L61))
2. Enable `high` test strictness level in `acceptance-test-config.yml`. (See instructions [here](https://github.com/airbytehq/airbyte/blob/master/docs/connector-development/testing-connectors/source-acceptance-tests-reference.md#L240))
3. Commit changes on `acceptance-test-config.yml` and open a PR.
4. Run SAT with the `/test` command on the branch.
5. If tests are failing please fix the failing test or use `bypass_reason` fields to explain why a specific test can't be run.
| 1.0 | Source Salesforce: enable `high` test strictness level in SAT - ## What
A `test_strictness_level` field was introduced to Source Acceptance Tests (SAT).
Salesforce is a generally_available connector, we want it to have a `high` test strictness level.
**This will help**:
- maximize the SAT coverage on this connector.
- document its potential weaknesses in term of test coverage.
## How
1. Migrate the existing `acceptance-test-config.yml` file to the latest configuration format. (See instructions [here](https://github.com/airbytehq/airbyte/blob/master/airbyte-integrations/bases/source-acceptance-test/README.md#L61))
2. Enable `high` test strictness level in `acceptance-test-config.yml`. (See instructions [here](https://github.com/airbytehq/airbyte/blob/master/docs/connector-development/testing-connectors/source-acceptance-tests-reference.md#L240))
3. Commit changes on `acceptance-test-config.yml` and open a PR.
4. Run SAT with the `/test` command on the branch.
5. If tests are failing please fix the failing test or use `bypass_reason` fields to explain why a specific test can't be run.
| test | source salesforce enable high test strictness level in sat what a test strictness level field was introduced to source acceptance tests sat salesforce is a generally available connector we want it to have a high test strictness level this will help maximize the sat coverage on this connector document its potential weaknesses in term of test coverage how migrate the existing acceptance test config yml file to the latest configuration format see instructions enable high test strictness level in acceptance test config yml see instructions commit changes on acceptance test config yml and open a pr run sat with the test command on the branch if tests are failing please fix the failing test or use bypass reason fields to explain why a specific test can t be run | 1 |
30,949 | 13,389,661,363 | IssuesEvent | 2020-09-02 19:15:01 | kubesphere/kubesphere | https://api.github.com/repos/kubesphere/kubesphere | closed | 微服务功能中，流量治理有数据，Tracing无数据 | area/microservice stale | **Describe the bug(描述下问题)**
项目开启了网关和服务治理功能，并且已经通过watch命令不断发送请求了
watch -n1 curl http://productpage.test1.xxx.xxx.xxx.xxx.nip.io:30294/productpage?u=normal
但是`流量治理`能看到数据，`Tracing`无数据。所有namespace的pod状态都正常。kubesphere也开启了logging功能。
<img width="1626" alt="Snipaste_2019-12-24_15-42-48" src="https://user-images.githubusercontent.com/16133390/71401200-1a6a9880-2664-11ea-9aad-39bde9223e6f.png">
<img width="1632" alt="Snipaste_2019-12-24_15-42-57" src="https://user-images.githubusercontent.com/16133390/71401217-222a3d00-2664-11ea-820c-eff0e8b7e024.png">
**Versions used(KubeSphere/Kubernetes的版本)**
KubeSphere: 2.1.0
Kubernetes: 1.15.7
**Environment(环境的硬件配置)**
How many nodes and their hardware configuration:
For example:
1 masters: 4cpu/16g
3 nodes: 4cpu/16g | 1.0 | 微服务功能中，流量治理有数据，Tracing无数据 - **Describe the bug(描述下问题)**
项目开启了网关和服务治理功能，并且已经通过watch命令不断发送请求了
watch -n1 curl http://productpage.test1.xxx.xxx.xxx.xxx.nip.io:30294/productpage?u=normal
但是`流量治理`能看到数据，`Tracing`无数据。所有namespace的pod状态都正常。kubesphere也开启了logging功能。
<img width="1626" alt="Snipaste_2019-12-24_15-42-48" src="https://user-images.githubusercontent.com/16133390/71401200-1a6a9880-2664-11ea-9aad-39bde9223e6f.png">
<img width="1632" alt="Snipaste_2019-12-24_15-42-57" src="https://user-images.githubusercontent.com/16133390/71401217-222a3d00-2664-11ea-820c-eff0e8b7e024.png">
**Versions used(KubeSphere/Kubernetes的版本)**
KubeSphere: 2.1.0
Kubernetes: 1.15.7
**Environment(环境的硬件配置)**
How many nodes and their hardware configuration:
For example:
1 masters: 4cpu/16g
3 nodes: 4cpu/16g | non_test | 微服务功能中，流量治理有数据，tracing无数据 describe the bug 描述下问题 项目开启了网关和服务治理功能，并且已经通过watch命令不断发送请求了 watch curl 但是 流量治理 能看到数据， tracing 无数据。所有namespace的pod状态都正常。kubesphere也开启了logging功能。 img width alt snipaste src img width alt snipaste src versions used kubesphere kubernetes的版本 kubesphere kubernetes environment 环境的硬件配置 how many nodes and their hardware configuration for example masters nodes | 0 |
6,010 | 8,677,818,250 | IssuesEvent | 2018-11-30 17:54:37 | isawnyu/isaw.web | https://api.github.com/repos/isawnyu/isaw.web | closed | eliminate redundant links in "events listing": 2 | WCAG A deploy high priority requirement | At present, the "events listing" creates a link around the event title for each listed event. When there is a lead image associated with an event, it creates a separate link around the image. Like this:
```html
<div class="event-result-detail">
<a href="http://isaw.nyu.edu/events/object-history">
<img src="http://isaw.nyu.edu/events/object-history/leadImage_mini" alt="">
</a>
<a href="http://isaw.nyu.edu/events/object-history">
<h3 class="event-title">Exhibition Gallery Talk: Object Histories</h3>
</a>
᠁
</div>
```
Redundant links like this are a WCAG violation. As in other templates we've revised for accessibility, we need one and only one link to each event, so something like this would be ideal:
```html
<div class="event-result-detail">
<a href="http://isaw.nyu.edu/events/object-history">
<img src="http://isaw.nyu.edu/events/object-history/leadImage_mini" alt="">
<h3 class="event-title">Exhibition Gallery Talk: Object Histories</h3>
</a>
᠁
</div>
```
| 1.0 | eliminate redundant links in "events listing": 2 - At present, the "events listing" creates a link around the event title for each listed event. When there is a lead image associated with an event, it creates a separate link around the image. Like this:
```html
<div class="event-result-detail">
<a href="http://isaw.nyu.edu/events/object-history">
<img src="http://isaw.nyu.edu/events/object-history/leadImage_mini" alt="">
</a>
<a href="http://isaw.nyu.edu/events/object-history">
<h3 class="event-title">Exhibition Gallery Talk: Object Histories</h3>
</a>
᠁
</div>
```
Redundant links like this are a WCAG violation. As in other templates we've revised for accessibility, we need one and only one link to each event, so something like this would be ideal:
```html
<div class="event-result-detail">
<a href="http://isaw.nyu.edu/events/object-history">
<img src="http://isaw.nyu.edu/events/object-history/leadImage_mini" alt="">
<h3 class="event-title">Exhibition Gallery Talk: Object Histories</h3>
</a>
᠁
</div>
```
| non_test | eliminate redundant links in events listing at present the events listing creates a link around the event title for each listed event when there is a lead image associated with an event it creates a separate link around the image like this html a href a href exhibition gallery talk object histories ᠁ redundant links like this are a wcag violation as in other templates we ve revised for accessibility we need one and only one link to each event so something like this would be ideal html a href exhibition gallery talk object histories ᠁ | 0 |
15,224 | 3,453,100,772 | IssuesEvent | 2015-12-17 09:34:29 | Piiit/tpg | https://api.github.com/repos/Piiit/tpg | closed | Add a test case to all tests where temporal queries have distinct names for all boundaries | 3-IN DEVELOPMENT bug testing | The test case `test-temporal-setop.sql` fails!
```
-- Testing: scalars and functions for temporal boundaries
select a,b,lower(t) ts1, upper(t) te1 from e
UNION PERIOD WITH (ts1,te1,ts2,te2)
select a,b,lower(t) ts2, upper(t) te2 from f
order by 1,2,3,4;
```
```
psql:unibz/tests/test-temporal-setop.sql:74: ERROR: column temporal_setop_x2.ts2 does not exist
LINE 2: UNION PERIOD WITH (ts1,te1,ts2,te2)
^
HINT: Perhaps you meant to reference the column "temporal_setop_x2"."ts1".
``` | 1.0 | Add a test case to all tests where temporal queries have distinct names for all boundaries - The test case `test-temporal-setop.sql` fails!
```
-- Testing: scalars and functions for temporal boundaries
select a,b,lower(t) ts1, upper(t) te1 from e
UNION PERIOD WITH (ts1,te1,ts2,te2)
select a,b,lower(t) ts2, upper(t) te2 from f
order by 1,2,3,4;
```
```
psql:unibz/tests/test-temporal-setop.sql:74: ERROR: column temporal_setop_x2.ts2 does not exist
LINE 2: UNION PERIOD WITH (ts1,te1,ts2,te2)
^
HINT: Perhaps you meant to reference the column "temporal_setop_x2"."ts1".
``` | test | add a test case to all tests where temporal queries have distinct names for all boundaries the test case test temporal setop sql fails testing scalars and functions for temporal boundaries select a b lower t upper t from e union period with select a b lower t upper t from f order by psql unibz tests test temporal setop sql error column temporal setop does not exist line union period with hint perhaps you meant to reference the column temporal setop | 1 |
431,470 | 30,234,977,749 | IssuesEvent | 2023-07-06 09:35:20 | UCL/hivpy | https://api.github.com/repos/UCL/hivpy | closed | Re-structure tutorials | documentation | Make general tutorials along with more module-specific ones. Include a table of contents and links to other resources. | 1.0 | Re-structure tutorials - Make general tutorials along with more module-specific ones. Include a table of contents and links to other resources. | non_test | re structure tutorials make general tutorials along with more module specific ones include a table of contents and links to other resources | 0 |
26,797 | 4,242,671,666 | IssuesEvent | 2016-07-06 20:18:09 | maine-cyber/mcsc-unisim | https://api.github.com/repos/maine-cyber/mcsc-unisim | closed | Engine Clock Test Required | C++ test todo | Currently the UniSim Engine clock is running rather well, but it is experiencing some drift. We need to write a test to gather and visualize data about the engine clock to determine whether the drift is a system scheduling issue or a bug.
The test will be written to be reusable and committed under the `tools/` directory. | 1.0 | Engine Clock Test Required - Currently the UniSim Engine clock is running rather well, but it is experiencing some drift. We need to write a test to gather and visualize data about the engine clock to determine whether the drift is a system scheduling issue or a bug.
The test will be written to be reusable and committed under the `tools/` directory. | test | engine clock test required currently the unisim engine clock is running rather well but it is experiencing some drift we need to write a test to gather and visualize data about the engine clock to determine whether the drift is a system scheduling issue or a bug the test will be written to be reusable and committed under the tools directory | 1 |
297,980 | 25,778,629,137 | IssuesEvent | 2022-12-09 14:07:23 | bottlerocket-os/bottlerocket | https://api.github.com/repos/bottlerocket-os/bottlerocket | closed | cargo make test for vmware-k8s variants | status/needs-triage area/testing | Get `cargo make test` working for testing vmware-k8s variants in vSphere.
depends on (for precedence):
- #2148
- #2149
We might also say that it depends on this:
- https://github.com/bottlerocket-os/bottlerocket-test-system/issues/414 | 1.0 | cargo make test for vmware-k8s variants - Get `cargo make test` working for testing vmware-k8s variants in vSphere.
depends on (for precedence):
- #2148
- #2149
We might also say that it depends on this:
- https://github.com/bottlerocket-os/bottlerocket-test-system/issues/414 | test | cargo make test for vmware variants get cargo make test working for testing vmware variants in vsphere depends on for precedence we might also say that it depends on this | 1 |
67,121 | 7,035,888,607 | IssuesEvent | 2017-12-28 04:15:05 | litehelpers/Cordova-sqlcipher-adapter | https://api.github.com/repos/litehelpers/Cordova-sqlcipher-adapter | opened | Not working on cordova-android@7, should use Gradle | bug testing | As reported in litehelpers/Cordova-sqlite-storage#729 this plugin will not work on cordova-android@7, which is standard for latest Cordova CLI (8.0.0). The best solution would be to include SQLCipher for Android using Gradle. I would like to resolve this when supporting SQLCipher 3.4.2 / 3.5.8 (#62). | 1.0 | Not working on cordova-android@7, should use Gradle - As reported in litehelpers/Cordova-sqlite-storage#729 this plugin will not work on cordova-android@7, which is standard for latest Cordova CLI (8.0.0). The best solution would be to include SQLCipher for Android using Gradle. I would like to resolve this when supporting SQLCipher 3.4.2 / 3.5.8 (#62). | test | not working on cordova android should use gradle as reported in litehelpers cordova sqlite storage this plugin will not work on cordova android which is standard for latest cordova cli the best solution would be to include sqlcipher for android using gradle i would like to resolve this when supporting sqlcipher | 1 |
101,812 | 12,707,427,221 | IssuesEvent | 2020-06-23 08:53:55 | liqd/a4-meinberlin | https://api.github.com/repos/liqd/a4-meinberlin | closed | testing 2961: captcha | Dev: A11y Prio: Medium Type: UX/UI or design | **URL:** https://meinberlin-dev.liqd.net/feedback/
**user:** non-registered user
**expected behaviour:** my answer using the text mode is not correct
**behaviour:** I still get an alert
**important screensize:**
**device & browser:**
**Comment/Question:** I sometimes find the text mode a bit complicated and didn't always get it right, but I guess that's how it is?
Screenshot?
| 1.0 | testing 2961: captcha - **URL:** https://meinberlin-dev.liqd.net/feedback/
**user:** non-registered user
**expected behaviour:** my answer using the text mode is not correct
**behaviour:** I still get an alert
**important screensize:**
**device & browser:**
**Comment/Question:** I sometimes find the text mode a bit complicated and didn't always get it right, but I guess that's how it is?
Screenshot?
| non_test | testing captcha url user non registered user expected behaviour my answer using the text mode is not correct behaviour i still get an alert important screensize device browser comment question i sometimes find the text mode a bit complicated and didn t always get it right but i guess that s how it is screenshot | 0 |
1,341 | 3,193,639,229 | IssuesEvent | 2015-09-30 07:12:58 | raml-org/raml-spec | https://api.github.com/repos/raml-org/raml-spec | opened | Support for API Key-Based Access Control | v1-enhanced-security-schemes | Many APIs require a key (token) to be submitted in a header and/or a query parameter. Support such security schemes explicitly. | True | Support for API Key-Based Access Control - Many APIs require a key (token) to be submitted in a header and/or a query parameter. Support such security schemes explicitly. | non_test | support for api key based access control many apis require a key token to be submitted in a header and or a query parameter support such security schemes explicitly | 0 |
225,094 | 17,792,951,467 | IssuesEvent | 2021-08-31 18:25:21 | architecture-building-systems/CityEnergyAnalyst | https://api.github.com/repos/architecture-building-systems/CityEnergyAnalyst | closed | MoudleNotFoundError: No module named 'osmnx.footprints' | bug testing | **Describe the bug**
The package osmnx has no module footprints, so you cannot import it
```
======================================================================
ERROR: test_inputs_setup_workflow (unittest.loader._FailedTest)
----------------------------------------------------------------------
ImportError: Failed to import test module: test_inputs_setup_workflow
Traceback (most recent call last):
File "/cluster/apps/nss/gcc-6.3.0/python/3.8.5/x86_64/lib64/python3.8/unittest/loader.py", line 436, in _find_test_path
module = self._get_module_from_name(name)
File "/cluster/apps/nss/gcc-6.3.0/python/3.8.5/x86_64/lib64/python3.8/unittest/loader.py", line 377, in _get_module_from_name
__import__(name)
File "/cluster/apps/nss/gcc-6.3.0/python/3.8.5/x86_64/lib64/python3.8/site-packages/cea/tests/test_inputs_setup_workflow.py", line 6, in <module>
from cea.datamanagement import zone_helper, surroundings_helper, terrain_helper, streets_helper, data_initializer, \
File "/cluster/apps/nss/gcc-6.3.0/python/3.8.5/x86_64/lib64/python3.8/site-packages/cea/datamanagement/zone_helper.py", line 10, in <module>
import osmnx.footprints
ModuleNotFoundError: No module named 'osmnx.footprints'
```
**To Reproduce**
Steps to reproduce the behavior:
1. run "cea test" with version 3.11.0
**Expected behaviour**
No error should be thrown
**Screenshots**
no screenshot
**Hardware (please complete the following information):**
- OS and version: CentOS 7.9
- Version of CEA you are using: 3.11.0
| 1.0 | MoudleNotFoundError: No module named 'osmnx.footprints' - **Describe the bug**
The package osmnx has no module footprints, so you cannot import it
```
======================================================================
ERROR: test_inputs_setup_workflow (unittest.loader._FailedTest)
----------------------------------------------------------------------
ImportError: Failed to import test module: test_inputs_setup_workflow
Traceback (most recent call last):
File "/cluster/apps/nss/gcc-6.3.0/python/3.8.5/x86_64/lib64/python3.8/unittest/loader.py", line 436, in _find_test_path
module = self._get_module_from_name(name)
File "/cluster/apps/nss/gcc-6.3.0/python/3.8.5/x86_64/lib64/python3.8/unittest/loader.py", line 377, in _get_module_from_name
__import__(name)
File "/cluster/apps/nss/gcc-6.3.0/python/3.8.5/x86_64/lib64/python3.8/site-packages/cea/tests/test_inputs_setup_workflow.py", line 6, in <module>
from cea.datamanagement import zone_helper, surroundings_helper, terrain_helper, streets_helper, data_initializer, \
File "/cluster/apps/nss/gcc-6.3.0/python/3.8.5/x86_64/lib64/python3.8/site-packages/cea/datamanagement/zone_helper.py", line 10, in <module>
import osmnx.footprints
ModuleNotFoundError: No module named 'osmnx.footprints'
```
**To Reproduce**
Steps to reproduce the behavior:
1. run "cea test" with version 3.11.0
**Expected behaviour**
No error should be thrown
**Screenshots**
no screenshot
**Hardware (please complete the following information):**
- OS and version: CentOS 7.9
- Version of CEA you are using: 3.11.0
| test | moudlenotfounderror no module named osmnx footprints describe the bug the package osmnx has no module footprints so you cannot import it error test inputs setup workflow unittest loader failedtest importerror failed to import test module test inputs setup workflow traceback most recent call last file cluster apps nss gcc python unittest loader py line in find test path module self get module from name name file cluster apps nss gcc python unittest loader py line in get module from name import name file cluster apps nss gcc python site packages cea tests test inputs setup workflow py line in from cea datamanagement import zone helper surroundings helper terrain helper streets helper data initializer file cluster apps nss gcc python site packages cea datamanagement zone helper py line in import osmnx footprints modulenotfounderror no module named osmnx footprints to reproduce steps to reproduce the behavior run cea test with version expected behaviour no error should be thrown screenshots no screenshot hardware please complete the following information os and version centos version of cea you are using | 1 |
94,448 | 8,491,764,879 | IssuesEvent | 2018-10-27 16:16:00 | pods-framework/pods | https://api.github.com/repos/pods-framework/pods | closed | Missing Styles of dfv form field using $pods->form(...) | Component: CSS Keywords: Regression Status: Fixed / Needs Testing Type: Bug | **Describe the bug**
Styles of pods form DFV fields not working correctly in plain wordpress installation with pod.
JavaScript to upload and delete file works but the styles of pods 2.6.x do not work anymore.
**To Reproduce**
Steps to reproduce the behavior:
1. Create Custom Post Type with DFV Field
2. Add a form for Custom Post Type in theme like a page template over $pods->form( ..
**Expected behavior**
Working styles of frontend form in Pods 2.7.x like in previous version Pods 2.6.x.
**Screenshots**
| 1.0 | Missing Styles of dfv form field using $pods->form(...) - **Describe the bug**
Styles of pods form DFV fields not working correctly in plain wordpress installation with pod.
JavaScript to upload and delete file works but the styles of pods 2.6.x do not work anymore.
**To Reproduce**
Steps to reproduce the behavior:
1. Create Custom Post Type with DFV Field
2. Add a form for Custom Post Type in theme like a page template over $pods->form( ..
**Expected behavior**
Working styles of frontend form in Pods 2.7.x like in previous version Pods 2.6.x.
**Screenshots**
| test | missing styles of dfv form field using pods form describe the bug styles of pods form dfv fields not working correctly in plain wordpress installation with pod javascript to upload and delete file works but the styles of pods x do not work anymore to reproduce steps to reproduce the behavior create custom post type with dfv field add a form for custom post type in theme like a page template over pods form expected behavior working styles of frontend form in pods x like in previous version pods x screenshots | 1 |
67,885 | 9,103,848,090 | IssuesEvent | 2019-02-20 16:45:28 | FreeUKGen/MyopicVicar | https://api.github.com/repos/FreeUKGen/MyopicVicar | closed | Amend Transcriber Information to include informing their coordinator of any Data Restrictions on images or data they find for themselves | P25 Ready for Deployment documentation needs info testing | Priority 25 (0 10 8 7)
a note is needed in the Transcribers Information to say that they must tell the CC about new data. The CC then sets the restrictions. Perhaps when we program in the restrictions a message needs to go to the Data Manager whenever a Church gets entries for the first time. | 1.0 | Amend Transcriber Information to include informing their coordinator of any Data Restrictions on images or data they find for themselves - Priority 25 (0 10 8 7)
a note is needed in the Transcribers Information to say that they must tell the CC about new data. The CC then sets the restrictions. Perhaps when we program in the restrictions a message needs to go to the Data Manager whenever a Church gets entries for the first time. | non_test | amend transcriber information to include informing their coordinator of any data restrictions on images or data they find for themselves priority a note is needed in the transcribers information to say that they must tell the cc about new data the cc then sets the restrictions perhaps when we program in the restrictions a message needs to go to the data manager whenever a church gets entries for the first time | 0 |
133,359 | 10,819,280,929 | IssuesEvent | 2019-11-08 14:04:28 | kubernetes/kubernetes | https://api.github.com/repos/kubernetes/kubernetes | closed | flake: TestWebhookAdmission | kind/failing-test kind/flake sig/api-machinery | <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
pull-kubernetes-integration
**Which test(s) are failing**:
https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/directory/pull-kubernetes-integration/1172176898202013696
```
=== RUN TestWebhookAdmissionWithWatchCache/apiextensions.k8s.io.v1.customresourcedefinitions/delete
I0912 16:14:28.130136 104492 client.go:361] parsed scheme: "endpoint"
I0912 16:14:28.130461 104492 endpoint.go:66] ccResolverWrapper: sending new addresses to cc: [{http://127.0.0.1:2379 0 <nil>}]
--- FAIL: TestWebhookAdmissionWithWatchCache/apiextensions.k8s.io.v1.customresourcedefinitions/delete (0.24s)
admission_test.go:676: waiting for schema.GroupVersionResource{Group:"apiextensions.k8s.io", Version:"v1", Resource:"customresourcedefinitions"} to be deleted (name: openshiftwebconsoleconfigs.webconsole2.operator.openshift.io, finalizers: [customresourcecleanup.apiextensions.k8s.io])...
admission_test.go:702: CustomResourceDefinition.apiextensions.k8s.io "openshiftwebconsoleconfigs.webconsole2.operator.openshift.io" is invalid: metadata.finalizers: Forbidden: no new finalizers can be added if the object is being deleted, found new finalizers []string{"test/k8s.io"}
```
**Since when has it been failing**:
**Testgrid link**:
https://testgrid.k8s.io/presubmits-kubernetes-blocking#pull-kubernetes-integration&sort-by-flakiness=&include-filter-by-regex=TestWebhookAdmission&width=5
**Reason for failure**:
**Anything else we need to know**:
The flake is currently rare. It is unclear yet if it is a test issue, timing issue, or a bug.
/sig api-machinery
/assign | 1.0 | flake: TestWebhookAdmission - <!-- Please only use this template for submitting reports about failing tests in Kubernetes CI jobs -->
**Which jobs are failing**:
pull-kubernetes-integration
**Which test(s) are failing**:
https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/directory/pull-kubernetes-integration/1172176898202013696
```
=== RUN TestWebhookAdmissionWithWatchCache/apiextensions.k8s.io.v1.customresourcedefinitions/delete
I0912 16:14:28.130136 104492 client.go:361] parsed scheme: "endpoint"
I0912 16:14:28.130461 104492 endpoint.go:66] ccResolverWrapper: sending new addresses to cc: [{http://127.0.0.1:2379 0 <nil>}]
--- FAIL: TestWebhookAdmissionWithWatchCache/apiextensions.k8s.io.v1.customresourcedefinitions/delete (0.24s)
admission_test.go:676: waiting for schema.GroupVersionResource{Group:"apiextensions.k8s.io", Version:"v1", Resource:"customresourcedefinitions"} to be deleted (name: openshiftwebconsoleconfigs.webconsole2.operator.openshift.io, finalizers: [customresourcecleanup.apiextensions.k8s.io])...
admission_test.go:702: CustomResourceDefinition.apiextensions.k8s.io "openshiftwebconsoleconfigs.webconsole2.operator.openshift.io" is invalid: metadata.finalizers: Forbidden: no new finalizers can be added if the object is being deleted, found new finalizers []string{"test/k8s.io"}
```
**Since when has it been failing**:
**Testgrid link**:
https://testgrid.k8s.io/presubmits-kubernetes-blocking#pull-kubernetes-integration&sort-by-flakiness=&include-filter-by-regex=TestWebhookAdmission&width=5
**Reason for failure**:
**Anything else we need to know**:
The flake is currently rare. It is unclear yet if it is a test issue, timing issue, or a bug.
/sig api-machinery
/assign | test | flake testwebhookadmission which jobs are failing pull kubernetes integration which test s are failing run testwebhookadmissionwithwatchcache apiextensions io customresourcedefinitions delete client go parsed scheme endpoint endpoint go ccresolverwrapper sending new addresses to cc fail testwebhookadmissionwithwatchcache apiextensions io customresourcedefinitions delete admission test go waiting for schema groupversionresource group apiextensions io version resource customresourcedefinitions to be deleted name openshiftwebconsoleconfigs operator openshift io finalizers admission test go customresourcedefinition apiextensions io openshiftwebconsoleconfigs operator openshift io is invalid metadata finalizers forbidden no new finalizers can be added if the object is being deleted found new finalizers string test io since when has it been failing testgrid link reason for failure anything else we need to know the flake is currently rare it is unclear yet if it is a test issue timing issue or a bug sig api machinery assign | 1 |
134,431 | 10,915,520,487 | IssuesEvent | 2019-11-21 11:20:36 | ubtue/DatenProbleme | https://api.github.com/repos/ubtue/DatenProbleme | closed | ISSN 2157-6475 International Journal of Comparative and Applied Criminal Justice Tag 041 Sprache | high priority ready for testing | Das Tag 041 fehlt bei allen regulären Aufsätzen. Dagegen ist es bei den Online First Aufsätzen vorhanden.
| 1.0 | ISSN 2157-6475 International Journal of Comparative and Applied Criminal Justice Tag 041 Sprache - Das Tag 041 fehlt bei allen regulären Aufsätzen. Dagegen ist es bei den Online First Aufsätzen vorhanden.
| test | issn international journal of comparative and applied criminal justice tag sprache das tag fehlt bei allen regulären aufsätzen dagegen ist es bei den online first aufsätzen vorhanden | 1 |
167,944 | 26,569,872,951 | IssuesEvent | 2023-01-21 02:12:56 | form-maker/FFF-FE | https://api.github.com/repos/form-maker/FFF-FE | closed | 회원가입 버그 수정#31 | fix design | ---
name: 'Issue: ✔Feature '
about: Feature 작업 사항을 입력해주세요.
title: '회원가입 버그'
labels: ''
assignees: ''
---
## Description
회원가입 관련 기능 버그 수정 등 기타 기능 버그 수정
## Todo
- [ ] 회원가입 버그 수정
## Etc
기타사항
| 1.0 | 회원가입 버그 수정#31 - ---
name: 'Issue: ✔Feature '
about: Feature 작업 사항을 입력해주세요.
title: '회원가입 버그'
labels: ''
assignees: ''
---
## Description
회원가입 관련 기능 버그 수정 등 기타 기능 버그 수정
## Todo
- [ ] 회원가입 버그 수정
## Etc
기타사항
| non_test | 회원가입 버그 수정 name issue ✔feature about feature 작업 사항을 입력해주세요 title 회원가입 버그 labels assignees description 회원가입 관련 기능 버그 수정 등 기타 기능 버그 수정 todo 회원가입 버그 수정 etc 기타사항 | 0 |
63,624 | 15,684,793,750 | IssuesEvent | 2021-03-25 10:25:14 | eclipse/eclipse.jdt.ls | https://api.github.com/repos/eclipse/eclipse.jdt.ls | opened | Stop generating .gz artifacts during builds | build/infra | With pack200 support in the JDK being removed, it's basically useless to generate .gz artifacts now, and projects are advised to stop producing them: https://www.eclipse.org/lists/cross-project-issues-dev/msg18273.html | 1.0 | Stop generating .gz artifacts during builds - With pack200 support in the JDK being removed, it's basically useless to generate .gz artifacts now, and projects are advised to stop producing them: https://www.eclipse.org/lists/cross-project-issues-dev/msg18273.html | non_test | stop generating gz artifacts during builds with support in the jdk being removed it s basically useless to generate gz artifacts now and projects are advised to stop producing them | 0 |
11,110 | 3,175,979,233 | IssuesEvent | 2015-09-24 05:14:51 | cyoung/stratux | https://api.github.com/repos/cyoung/stratux | closed | [0.3b1] UAT-only pi lockup in an area with fairly heavy traffic | bug testing | [UAT log here](https://gist.github.com/egid/04e77cf1f9260aaebcd2) - seems to have missed most of the flight, though (09:40-10:20, log starts at 10:20).
Went up today with v0.3b1, a single NooElec dongle, and powered off an Anker. No battery issues the whole flight. Most of the time was just the KPAE hi ADS-B tower, it picked up one other towards the tail end.
We had two iPad Minis in the plane - a retina, and my original - both running ForeFlight latest. My original Mini kept locking up with the traffic view enabled; shortly after that, the pi would crash (or hang) with solid power and no activity LED. The Retina mini seemed more stable, slightly. | 1.0 | [0.3b1] UAT-only pi lockup in an area with fairly heavy traffic - [UAT log here](https://gist.github.com/egid/04e77cf1f9260aaebcd2) - seems to have missed most of the flight, though (09:40-10:20, log starts at 10:20).
Went up today with v0.3b1, a single NooElec dongle, and powered off an Anker. No battery issues the whole flight. Most of the time was just the KPAE hi ADS-B tower, it picked up one other towards the tail end.
We had two iPad Minis in the plane - a retina, and my original - both running ForeFlight latest. My original Mini kept locking up with the traffic view enabled; shortly after that, the pi would crash (or hang) with solid power and no activity LED. The Retina mini seemed more stable, slightly. | test | uat only pi lockup in an area with fairly heavy traffic seems to have missed most of the flight though log starts at went up today with a single nooelec dongle and powered off an anker no battery issues the whole flight most of the time was just the kpae hi ads b tower it picked up one other towards the tail end we had two ipad minis in the plane a retina and my original both running foreflight latest my original mini kept locking up with the traffic view enabled shortly after that the pi would crash or hang with solid power and no activity led the retina mini seemed more stable slightly | 1 |
223,791 | 7,460,708,838 | IssuesEvent | 2018-03-30 20:59:12 | bounswe/bounswe2018group7 | https://api.github.com/repos/bounswe/bounswe2018group7 | opened | Create Test Cases for Memory Post and Comment Creation | priority:high status:in-progress type:project-task | Here is the test case for `Successful Memory Post Creation`:
**Related Requirements:** 1.1.4.2
**Pre-Conditions:**
1. User is signed-in to the system.
2. User is currently on homepage.
| STEPS | ACTIONS | INPUT DATA | EXPECTED OUTPUT | ACTUAL OUTPUT | RESULT |
| :---: | :---: | :---: | :---: | :---: | :---: |
| 1 | Click "New Memory Post" button on homepage header. | - | Memory Post creation page is displayed. | - | - |
| 2 | Write a title in "Memory Title" text input. | The Maiden's Tower | - | - | - |
| 3 | Write a story in "Memory Story" text input. | According to a legend, ... | - | - | - |
| 4 | Find and select the location of The Maiden's Tower in map. | - | - | - | - |
| 5 | Select a time (interval) from calender widget. | 1700 - 1800 | - | - | - |
| 6 | Choose an image file from computer. | maidens_tower.png | - | - | - |
| 7 | Write comma separated tags in "Tags" text input. | maidens,tower,uskudar | - | - | - |
| 8 | Click "Create Memory Post" button. | - | A success message is displayed and user is redirected to the newly created Memory Post page. | - | - |
**Post-Conditions:**
1. "maidens", "tower" and "uskudar" tags are saved to database.
2. Memory Location is saved to database.
3. Memory Time is saved to database.
4. Memory Post is saved to database. | 1.0 | Create Test Cases for Memory Post and Comment Creation - Here is the test case for `Successful Memory Post Creation`:
**Related Requirements:** 1.1.4.2
**Pre-Conditions:**
1. User is signed-in to the system.
2. User is currently on homepage.
| STEPS | ACTIONS | INPUT DATA | EXPECTED OUTPUT | ACTUAL OUTPUT | RESULT |
| :---: | :---: | :---: | :---: | :---: | :---: |
| 1 | Click "New Memory Post" button on homepage header. | - | Memory Post creation page is displayed. | - | - |
| 2 | Write a title in "Memory Title" text input. | The Maiden's Tower | - | - | - |
| 3 | Write a story in "Memory Story" text input. | According to a legend, ... | - | - | - |
| 4 | Find and select the location of The Maiden's Tower in map. | - | - | - | - |
| 5 | Select a time (interval) from calender widget. | 1700 - 1800 | - | - | - |
| 6 | Choose an image file from computer. | maidens_tower.png | - | - | - |
| 7 | Write comma separated tags in "Tags" text input. | maidens,tower,uskudar | - | - | - |
| 8 | Click "Create Memory Post" button. | - | A success message is displayed and user is redirected to the newly created Memory Post page. | - | - |
**Post-Conditions:**
1. "maidens", "tower" and "uskudar" tags are saved to database.
2. Memory Location is saved to database.
3. Memory Time is saved to database.
4. Memory Post is saved to database. | non_test | create test cases for memory post and comment creation here is the test case for successful memory post creation related requirements pre conditions user is signed in to the system user is currently on homepage steps actions input data expected output actual output result click new memory post button on homepage header memory post creation page is displayed write a title in memory title text input the maiden s tower write a story in memory story text input according to a legend find and select the location of the maiden s tower in map select a time interval from calender widget choose an image file from computer maidens tower png write comma separated tags in tags text input maidens tower uskudar click create memory post button a success message is displayed and user is redirected to the newly created memory post page post conditions maidens tower and uskudar tags are saved to database memory location is saved to database memory time is saved to database memory post is saved to database | 0 |
44,541 | 9,601,883,770 | IssuesEvent | 2019-05-10 13:20:10 | bimloket/visi | https://api.github.com/repos/bimloket/visi | closed | Prio-013: Keurmerktest op DateTime, Boolean, etc. | 1.4 - 20140331 Impact: Low enhancement migrated from CodePlex | Gemeld op : ?
Melder : ?
Omschrijving
Motivatie
Impact
Oplossing
Wanneer een userDefinedType als baseType dateTime heeft is dit een DateTime veld.
Bij de keurmerktest moet in het testraamwerk een dateTime worden opgenomen zodat er getest kan worden of dateTime ondersteund wordt.
Actie
dateTime opnemen in testraamwerk en testscenario 1 (AB, Status=done).
#### This work item was migrated from CodePlex
CodePlex work item ID: '1022'
Assigned to: 'Arne_Bruinse'
Vote count: '1'
| 1.0 | Prio-013: Keurmerktest op DateTime, Boolean, etc. - Gemeld op : ?
Melder : ?
Omschrijving
Motivatie
Impact
Oplossing
Wanneer een userDefinedType als baseType dateTime heeft is dit een DateTime veld.
Bij de keurmerktest moet in het testraamwerk een dateTime worden opgenomen zodat er getest kan worden of dateTime ondersteund wordt.
Actie
dateTime opnemen in testraamwerk en testscenario 1 (AB, Status=done).
#### This work item was migrated from CodePlex
CodePlex work item ID: '1022'
Assigned to: 'Arne_Bruinse'
Vote count: '1'
| non_test | prio keurmerktest op datetime boolean etc gemeld op melder omschrijving motivatie impact oplossing wanneer een userdefinedtype als basetype datetime heeft is dit een datetime veld bij de keurmerktest moet in het testraamwerk een datetime worden opgenomen zodat er getest kan worden of datetime ondersteund wordt actie datetime opnemen in testraamwerk en testscenario ab status done this work item was migrated from codeplex codeplex work item id assigned to arne bruinse vote count | 0 |
88,783 | 10,579,610,877 | IssuesEvent | 2019-10-08 03:22:43 | JacobMGEvans/lake-county-tech-meetup | https://api.github.com/repos/JacobMGEvans/lake-county-tech-meetup | opened | Remove Learning Gatsby Section | documentation good first issue hacktoberfest | - Simply remove the learning Gatsby section.
- Add a simple header for the future **Contributors** section.
- For Hacktoberfest and new people to OSS contribution please provide a detailed commit message and Pull Request. I will review thoroughly. | 1.0 | Remove Learning Gatsby Section - - Simply remove the learning Gatsby section.
- Add a simple header for the future **Contributors** section.
- For Hacktoberfest and new people to OSS contribution please provide a detailed commit message and Pull Request. I will review thoroughly. | non_test | remove learning gatsby section simply remove the learning gatsby section add a simple header for the future contributors section for hacktoberfest and new people to oss contribution please provide a detailed commit message and pull request i will review thoroughly | 0 |
621,896 | 19,599,057,681 | IssuesEvent | 2022-01-05 21:53:09 | public-accountability/littlesis-rails | https://api.github.com/repos/public-accountability/littlesis-rails | closed | On add relationship page, "create new entity" link shouldn't appear until search results have been returned | low-priority | sometimes there is a significant delay in returning search results and it is tempting to click new entity – maybe a spinning gear with word "searching" next to it should appear | 1.0 | On add relationship page, "create new entity" link shouldn't appear until search results have been returned - sometimes there is a significant delay in returning search results and it is tempting to click new entity – maybe a spinning gear with word "searching" next to it should appear | non_test | on add relationship page create new entity link shouldn t appear until search results have been returned sometimes there is a significant delay in returning search results and it is tempting to click new entity – maybe a spinning gear with word searching next to it should appear | 0 |
229,025 | 18,277,355,947 | IssuesEvent | 2021-10-04 20:33:46 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | crdb_internal.reset_multi_region_zone_configs_for_database hits `concurrent txn use detected` | C-test-failure O-robot O-roachtest branch-master T-sql-queries | roachtest.sqlsmith/setup=seed/setting=no-mutations [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=3359107&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=3359107&tab=artifacts#/sqlsmith/setup=seed/setting=no-mutations) on master @ [ab1fc343c9a1140191f96353995258e609a84d02](https://github.com/cockroachdb/cockroach/commits/ab1fc343c9a1140191f96353995258e609a84d02):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/sqlsmith/setup=seed/setting=no-mutations/run_1
sqlsmith.go:223,sqlsmith.go:258,test_runner.go:777: error: pq: internal error: crdb_internal.reset_multi_region_zone_configs_for_database(): concurrent txn use detected. ba: Get [/Table/3/1/1198049476/2/1,/Min), [txn: a6ec9626], [can-forward-ts]
stmt:
SELECT
tab_205427._timestamp AS col_500148,
tab_205425._string AS col_500149,
tab_205427._float4 AS col_500150,
(-23471):::INT8 AS col_500151,
tab_205424._timestamptz AS col_500152,
tab_205426._bool AS col_500153,
tab_205427._decimal AS col_500154,
tab_205426._enum AS col_500155
FROM
defaultdb.public.seed@seed__int8__float8__date_idx AS tab_205424,
defaultdb.public.seed@[0] AS tab_205425,
defaultdb.public.seed@[0] AS tab_205426
JOIN defaultdb.public.seed@seed__int8__float8__date_idx AS tab_205427 ON
(tab_205426._float8) = (tab_205427._float8)
AND (tab_205426._int4) = (tab_205427._int4)
AND (tab_205426._float8) = (tab_205427._float4)
AND (tab_205426._int4) = (tab_205427._int2)
WHERE
crdb_internal.reset_multi_region_zone_configs_for_database((-8570920568719095612):::INT8::INT8)::BOOL;
```
<details><summary>Reproduce</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
</p>
</details>
/cc @cockroachdb/sql-queries
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*sqlsmith/setup=seed/setting=no-mutations.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| 2.0 | crdb_internal.reset_multi_region_zone_configs_for_database hits `concurrent txn use detected` - roachtest.sqlsmith/setup=seed/setting=no-mutations [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=3359107&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=3359107&tab=artifacts#/sqlsmith/setup=seed/setting=no-mutations) on master @ [ab1fc343c9a1140191f96353995258e609a84d02](https://github.com/cockroachdb/cockroach/commits/ab1fc343c9a1140191f96353995258e609a84d02):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/sqlsmith/setup=seed/setting=no-mutations/run_1
sqlsmith.go:223,sqlsmith.go:258,test_runner.go:777: error: pq: internal error: crdb_internal.reset_multi_region_zone_configs_for_database(): concurrent txn use detected. ba: Get [/Table/3/1/1198049476/2/1,/Min), [txn: a6ec9626], [can-forward-ts]
stmt:
SELECT
tab_205427._timestamp AS col_500148,
tab_205425._string AS col_500149,
tab_205427._float4 AS col_500150,
(-23471):::INT8 AS col_500151,
tab_205424._timestamptz AS col_500152,
tab_205426._bool AS col_500153,
tab_205427._decimal AS col_500154,
tab_205426._enum AS col_500155
FROM
defaultdb.public.seed@seed__int8__float8__date_idx AS tab_205424,
defaultdb.public.seed@[0] AS tab_205425,
defaultdb.public.seed@[0] AS tab_205426
JOIN defaultdb.public.seed@seed__int8__float8__date_idx AS tab_205427 ON
(tab_205426._float8) = (tab_205427._float8)
AND (tab_205426._int4) = (tab_205427._int4)
AND (tab_205426._float8) = (tab_205427._float4)
AND (tab_205426._int4) = (tab_205427._int2)
WHERE
crdb_internal.reset_multi_region_zone_configs_for_database((-8570920568719095612):::INT8::INT8)::BOOL;
```
<details><summary>Reproduce</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
</p>
</details>
/cc @cockroachdb/sql-queries
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*sqlsmith/setup=seed/setting=no-mutations.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| test | crdb internal reset multi region zone configs for database hits concurrent txn use detected roachtest sqlsmith setup seed setting no mutations with on master the test failed on branch master cloud gce test artifacts and logs in home agent work go src github com cockroachdb cockroach artifacts sqlsmith setup seed setting no mutations run sqlsmith go sqlsmith go test runner go error pq internal error crdb internal reset multi region zone configs for database concurrent txn use detected ba get stmt select tab timestamp as col tab string as col tab as col as col tab timestamptz as col tab bool as col tab decimal as col tab enum as col from defaultdb public seed seed date idx as tab defaultdb public seed as tab defaultdb public seed as tab join defaultdb public seed seed date idx as tab on tab tab and tab tab and tab tab and tab tab where crdb internal reset multi region zone configs for database bool reproduce see cc cockroachdb sql queries | 1 |
187,312 | 14,427,513,039 | IssuesEvent | 2020-12-06 04:30:40 | kalexmills/github-vet-tests-dec2020 | https://api.github.com/repos/kalexmills/github-vet-tests-dec2020 | closed | cisco-ie/pipeline-gnmi: xport_udp_test.go; 39 LoC | fresh small test |
Found a possible issue in [cisco-ie/pipeline-gnmi](https://www.github.com/cisco-ie/pipeline-gnmi) at [xport_udp_test.go](https://github.com/cisco-ie/pipeline-gnmi/blob/d931496b9d70a8d9a14c047a9f94b6081469ed21/xport_udp_test.go#L208-L246)
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.
> function call at line 221 may store a reference to subt
[Click here to see the code in its original context.](https://github.com/cisco-ie/pipeline-gnmi/blob/d931496b9d70a8d9a14c047a9f94b6081469ed21/xport_udp_test.go#L208-L246)
<details>
<summary>Click here to show the 39 line(s) of Go which triggered the analyzer.</summary>
```go
for _, subt := range subtests {
subt.lock = &udpTestContextLock{}
tb.Run(
fmt.Sprint(subt.name),
func(tb *testing.T) {
subt.tDone = make(chan struct{})
subt.conn = outConn
subt.dataChan = dataChan
subt.lock.Add(2)
go udpTestHandleMessages(&subt)
time.Sleep(time.Millisecond * 500)
go udpTestSendMessages(&subt)
ticker := time.NewTicker(time.Second * 2)
old_handled := 0
for range ticker.C {
subt.lock.Lock()
if subt.handled >= subt.max {
ticker.Stop()
break
}
if subt.handled == old_handled {
//
// stopped making progress
ticker.Stop()
tb.Fatalf("Progress stalled: handled %d, sent %d, max %d",
subt.handled, subt.send, subt.max)
}
old_handled = subt.handled
subt.lock.Unlock()
}
close(subt.tDone)
subt.lock.Wait()
})
}
```
</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: d931496b9d70a8d9a14c047a9f94b6081469ed21
| 1.0 | cisco-ie/pipeline-gnmi: xport_udp_test.go; 39 LoC -
Found a possible issue in [cisco-ie/pipeline-gnmi](https://www.github.com/cisco-ie/pipeline-gnmi) at [xport_udp_test.go](https://github.com/cisco-ie/pipeline-gnmi/blob/d931496b9d70a8d9a14c047a9f94b6081469ed21/xport_udp_test.go#L208-L246)
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.
> function call at line 221 may store a reference to subt
[Click here to see the code in its original context.](https://github.com/cisco-ie/pipeline-gnmi/blob/d931496b9d70a8d9a14c047a9f94b6081469ed21/xport_udp_test.go#L208-L246)
<details>
<summary>Click here to show the 39 line(s) of Go which triggered the analyzer.</summary>
```go
for _, subt := range subtests {
subt.lock = &udpTestContextLock{}
tb.Run(
fmt.Sprint(subt.name),
func(tb *testing.T) {
subt.tDone = make(chan struct{})
subt.conn = outConn
subt.dataChan = dataChan
subt.lock.Add(2)
go udpTestHandleMessages(&subt)
time.Sleep(time.Millisecond * 500)
go udpTestSendMessages(&subt)
ticker := time.NewTicker(time.Second * 2)
old_handled := 0
for range ticker.C {
subt.lock.Lock()
if subt.handled >= subt.max {
ticker.Stop()
break
}
if subt.handled == old_handled {
//
// stopped making progress
ticker.Stop()
tb.Fatalf("Progress stalled: handled %d, sent %d, max %d",
subt.handled, subt.send, subt.max)
}
old_handled = subt.handled
subt.lock.Unlock()
}
close(subt.tDone)
subt.lock.Wait()
})
}
```
</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: d931496b9d70a8d9a14c047a9f94b6081469ed21
| test | cisco ie pipeline gnmi xport udp 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 function call at line may store a reference to subt click here to show the line s of go which triggered the analyzer go for subt range subtests subt lock udptestcontextlock tb run fmt sprint subt name func tb testing t subt tdone make chan struct subt conn outconn subt datachan datachan subt lock add go udptesthandlemessages subt time sleep time millisecond go udptestsendmessages subt ticker time newticker time second old handled for range ticker c subt lock lock if subt handled subt max ticker stop break if subt handled old handled stopped making progress ticker stop tb fatalf progress stalled handled d sent d max d subt handled subt send subt max old handled subt handled subt lock unlock close subt tdone subt lock wait 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 |
277,197 | 21,032,063,897 | IssuesEvent | 2022-03-31 02:14:16 | ember-modifier/ember-modifier | https://api.github.com/repos/ember-modifier/ember-modifier | closed | strongly typed arguments | documentation good first issue | How would you strongly type your modifier class arguments?
e.g.
```ts
interface InjectLiveDataModifierArgs extends ModifierArgs<unknown> {
device: string,
metric: string
}
export default class InjectLiveDataModifier extends Modifier<InjectLiveDataModifierArgs> {
get device(): string {
return this.args.named.device; // Type 'unknown' is not assignable to type 'string'
}
}
``` | 1.0 | strongly typed arguments - How would you strongly type your modifier class arguments?
e.g.
```ts
interface InjectLiveDataModifierArgs extends ModifierArgs<unknown> {
device: string,
metric: string
}
export default class InjectLiveDataModifier extends Modifier<InjectLiveDataModifierArgs> {
get device(): string {
return this.args.named.device; // Type 'unknown' is not assignable to type 'string'
}
}
``` | non_test | strongly typed arguments how would you strongly type your modifier class arguments e g ts interface injectlivedatamodifierargs extends modifierargs device string metric string export default class injectlivedatamodifier extends modifier get device string return this args named device type unknown is not assignable to type string | 0 |
237,064 | 19,592,055,718 | IssuesEvent | 2022-01-05 14:02:30 | elastic/kibana | https://api.github.com/repos/elastic/kibana | closed | Failing test: Jest Tests.x-pack/plugins/security_solution/public/detections/pages/detection_engine/rules/all - AllRules it pulls from storage and does not set an auto refresh interval if storage indicates refresh is paused | failed-test Team:SIEM Team:Detections and Resp Team: SecuritySolution | A test failed on a tracked branch
```
Error: Method “simulate” is meant to be run on 1 node. 0 found instead.
<html>
<head>
<style
id="ace_editor.css"
>
.ace_editor {position: relative;overflow: hidden;font: 12px/normal 'Monaco', 'Menlo', 'Ubuntu Mono', 'Consolas', 'source-code-pro', monospace;direction: ltr;text-align: left;-webkit-tap-highlight-color: rgba(0, 0, 0, 0);}.ace_scroller {position: absolute;overflow: hidden;top: 0;bottom: 0;background-color: inherit;-ms-user-select: none;-moz-user-select: none;-webkit-user-select: none;user-select: none;cursor: text;}.ace_content {position: absolute;-moz-box-sizing: border-box;-webkit-box-sizing: border-box;box-sizing: border-box;min-width: 100%;}.ace_dragging .ace_scroller:before{position: absolute;top: 0;left: 0;right: 0;bottom: 0;content: '';background: rgba(250, 250, 250, 0.01);z-index: 1000;}.ace_dragging.ace_dark .ace_scroller:before{background: rgba(0, 0, 0, 0.01);}.ace_selecting, .ace_selecting * {cursor: text !important;}.ace_gutter {position: absolute;overflow : hidden;width: auto;top: 0;bottom: 0;left: 0;cursor: default;z-index: 4;-ms-user-select: none;-moz-user-select: none;-webkit-user-select: none;user-select: none;}.ace_gutter-active-line {position: absolute;left: 0;right: 0;}.ace_scroller.ace_scroll-left {box-shadow: 17px 0 16px -16px rgba(0, 0, 0, 0.4) inset;}.ace_gutter-cell {padding-left: 19px;padding-right: 6px;background-repeat: no-repeat;}.ace_gutter-cell.ace_error {background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAMAAAAoLQ9TAAABOFBMVEX/////////QRswFAb/Ui4wFAYwFAYwFAaWGAfDRymzOSH/PxswFAb/SiUwFAYwFAbUPRvjQiDllog5HhHdRybsTi3/Tyv9Tir+Syj/UC3////XurebMBIwFAb/RSHbPx/gUzfdwL3kzMivKBAwFAbbvbnhPx66NhowFAYwFAaZJg8wFAaxKBDZurf/RB6mMxb/SCMwFAYwFAbxQB3+RB4wFAb/Qhy4Oh+4QifbNRcwFAYwFAYwFAb/QRzdNhgwFAYwFAbav7v/Uy7oaE68MBK5LxLewr/r2NXewLswFAaxJw4wFAbkPRy2PyYwFAaxKhLm1tMwFAazPiQwFAaUGAb/QBrfOx3bvrv/VC/maE4wFAbRPBq6MRO8Qynew8Dp2tjfwb0wFAbx6eju5+by6uns4uH9/f36+vr/GkHjAAAAYnRSTlMAGt+64rnWu/bo8eAA4InH3+DwoN7j4eLi4xP99Nfg4+b+/u9B/eDs1MD1mO7+4PHg2MXa347g7vDizMLN4eG+Pv7i5evs/v79yu7S3/DV7/498Yv24eH+4ufQ3Ozu/v7+y13sRqwAAADLSURBVHjaZc/XDsFgGIBhtDrshlitmk2IrbHFqL2pvXf/+78DPokj7+Fz9qpU/9UXJIlhmPaTaQ6QPaz0mm+5gwkgovcV6GZzd5JtCQwgsxoHOvJO15kleRLAnMgHFIESUEPmawB9ngmelTtipwwfASilxOLyiV5UVUyVAfbG0cCPHig+GBkzAENHS0AstVF6bacZIOzgLmxsHbt2OecNgJC83JERmePUYq8ARGkJx6XtFsdddBQgZE2nPR6CICZhawjA4Fb/chv+399kfR+MMMDGOQAAAABJRU5ErkJggg==");background-repeat: no-repeat;background-position: 2px center;}.ace_gutter-cell.ace_warning {background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAMAAAAoLQ9TAAAAmVBMVEX///8AAAD///8AAAAAAABPSzb/5sAAAAB/blH/73z/ulkAAAAAAAD85pkAAAAAAAACAgP/vGz/rkDerGbGrV7/pkQICAf////e0IsAAAD/oED/qTvhrnUAAAD/yHD/njcAAADuv2r/nz//oTj/p064oGf/zHAAAAA9Nir/tFIAAAD/tlTiuWf/tkIAAACynXEAAAAAAAAtIRW7zBpBAAAAM3RSTlMAABR1m7RXO8Ln31Z36zT+neXe5OzooRDfn+TZ4p3h2hTf4t3k3ucyrN1K5+Xaks52Sfs9CXgrAAAAjklEQVR42o3PbQ+CIBQFYEwboPhSYgoYunIqqLn6/z8uYdH8Vmdnu9vz4WwXgN/xTPRD2+sgOcZjsge/whXZgUaYYvT8QnuJaUrjrHUQreGczuEafQCO/SJTufTbroWsPgsllVhq3wJEk2jUSzX3CUEDJC84707djRc5MTAQxoLgupWRwW6UB5fS++NV8AbOZgnsC7BpEAAAAABJRU5ErkJggg==");background-position: 2px center;}.ace_gutter-cell.ace_info {background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAAAAAA6mKC9AAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAAJ0Uk5TAAB2k804AAAAPklEQVQY02NgIB68QuO3tiLznjAwpKTgNyDbMegwisCHZUETUZV0ZqOquBpXj2rtnpSJT1AEnnRmL2OgGgAAIKkRQap2htgAAAAASUVORK5CYII=");background-position: 2px center;}.ace_dark .ace_gutter-cell.ace_info {background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQBAMAAADt3eJSAAAAJFBMVEUAAAChoaGAgIAqKiq+vr6tra1ZWVmUlJSbm5s8PDxubm56enrdgzg3AAAAAXRSTlMAQObYZgAAAClJREFUeNpjYMAPdsMYHegyJZFQBlsUlMFVCWUYKkAZMxZAGdxlDMQBAG+TBP4B6RyJAAAAAElFTkSuQmCC");}.ace_scrollbar {position: absolute;right: 0;bottom: 0;z-index: 6;}.ace_scrollbar-inner {position: absolute;cursor: text;left: 0;top: 0;}.ace_scrollbar-v{overflow-x: hidden;overflow-y: scroll;top: 0;}.ace_scrollbar-h {overflow-x: scroll;overflow-y: hidden;left: 0;}.ace_print-margin {position: absolute;height: 100%;}.ace_text-input {position: absolute;z-index: 0;width: 0.5em;height: 1em;opacity: 0;background: transparent;-moz-appearance: none;appearance: none;border: none;resize: none;outline: none;overflow: hidden;font: inherit;padding: 0 1px;margin: 0 -1px;text-indent: -1em;-ms-user-select: text;-moz-user-select: text;-webkit-user-select: text;user-select: text;white-space: pre!important;}.ace_text-input.ace_composition {background: inherit;color: inherit;z-index: 1000;opacity: 1;text-indent: 0;}.ace_layer {z-index: 1;position: absolute;overflow: hidden;word-wrap: normal;white-space: pre;height: 100%;width: 100%;-moz-box-sizing: border-box;-webkit-box-sizing: border-box;box-sizing: border-box;pointer-events: none;}.ace_gutter-layer {position: relative;width: auto;text-align: right;pointer-events: auto;}.ace_text-layer {font: inherit !important;}.ace_cjk {display: inline-block;text-align: center;}.ace_cursor-layer {z-index: 4;}.ace_cursor {z-index: 4;position: absolute;-moz-box-sizing: border-box;-webkit-box-sizing: border-box;box-sizing: border-box;border-left: 2px solid;transform: translatez(0);}.ace_multiselect .ace_cursor {border-left-width: 1px;}.ace_slim-cursors .ace_cursor {border-left-width: 1px;}.ace_overwrite-cursors .ace_cursor {border-left-width: 0;border-bottom: 1px solid;}.ace_hidden-cursors .ace_cursor {opacity: 0.2;}.ace_smooth-blinking .ace_cursor {-webkit-transition: opacity 0.18s;transition: opacity 0.18s;}.ace_marker-layer .ace_step, .ace_marker-layer .ace_stack {position: absolute;z-index: 3;}.ace_marker-layer .ace_selection {position: absolute;z-index: 5;}.ace_marker-layer .ace_bracket {position: absolute;z-index: 6;}.ace_marker-layer .ace_active-line {position: absolute;z-index: 2;}.ace_marker-layer .ace_selected-word {position: absolute;z-index: 4;-moz-box-sizing: border-box;-webkit-box-sizing: border-box;box-sizing: border-box;}.ace_line .ace_fold {-moz-box-sizing: border-box;-webkit-box-sizing: border-box;box-sizing: border-box;display: inline-block;height: 11px;margin-top: -2px;vertical-align: middle;background-image:url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABEAAAAJCAYAAADU6McMAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAJpJREFUeNpi/P//PwOlgAXGYGRklAVSokD8GmjwY1wasKljQpYACtpCFeADcHVQfQyMQAwzwAZI3wJKvCLkfKBaMSClBlR7BOQikCFGQEErIH0VqkabiGCAqwUadAzZJRxQr/0gwiXIal8zQQPnNVTgJ1TdawL0T5gBIP1MUJNhBv2HKoQHHjqNrA4WO4zY0glyNKLT2KIfIMAAQsdgGiXvgnYAAAAASUVORK5CYII="),url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAA3CAYAAADNNiA5AAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAACJJREFUeNpi+P//fxgTAwPDBxDxD078RSX+YeEyDFMCIMAAI3INmXiwf2YAAAAASUVORK5CYII=");background-repeat: no-repeat, repeat-x;background-position: center center, top left;color: transparent;border: 1px solid black;border-radius: 2px;cursor: pointer;pointer-events: auto;}.ace_dark .ace_fold {}.ace_fold:hover{background-image:url("data:image/png;ba...
at ReactWrapper.single (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/enzyme/src/ReactWrapper.js:1168:13)
at ReactWrapper.simulate (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/enzyme/src/ReactWrapper.js:665:17)
at /opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/x-pack/plugins/security_solution/public/detections/pages/detection_engine/rules/all/index.test.tsx:269:72
at runWithExpensiveErrorDiagnosticsDisabled (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/@testing-library/dom/dist/config.js:51:12)
at checkCallback (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/@testing-library/dom/dist/wait-for.js:127:77)
at /opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/@testing-library/dom/dist/wait-for.js:72:9
at new Promise (<anonymous>)
at waitFor (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/@testing-library/dom/dist/wait-for.js:40:10)
at /opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/@testing-library/dom/dist/wait-for.js:174:54
at /opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/@testing-library/react/dist/pure.js:57:22
at batchedUpdates$1 (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/react-dom/cjs/react-dom.development.js:24386:12)
at act (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/react-dom/cjs/react-dom-test-utils.development.js:1092:14)
at asyncAct (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/@testing-library/react/dist/act-compat.js:119:12)
at Object.asyncWrapper (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/@testing-library/react/dist/pure.js:56:35)
at waitForWrapper (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/@testing-library/dom/dist/wait-for.js:174:35)
at Object.<anonymous> (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/x-pack/plugins/security_solution/public/detections/pages/detection_engine/rules/all/index.test.tsx:261:11)
at Promise.then.completed (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/utils.js:276:28)
at new Promise (<anonymous>)
at callAsyncCircusFn (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/utils.js:216:10)
at _callCircusTest (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/run.js:212:40)
at _runTest (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/run.js:149:3)
at _runTestsForDescribeBlock (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/run.js:63:9)
at _runTestsForDescribeBlock (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/run.js:57:9)
at run (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/run.js:25:3)
at runAndTransformResultsToJestFormat (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapterInit.js:176:21)
at jestAdapter (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:109:19)
at runTestInternal (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-runner/build/runTest.js:380:16)
at runTest (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-runner/build/runTest.js:472:34)
at Object.worker (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-runner/build/testWorker.js:133:12)
```
First failure: [CI Build - 7.16](https://buildkite.com/elastic/kibana-hourly/builds/1857#bf83d7ba-ceb5-49c6-976f-46f0d8fddf64)
<!-- kibanaCiData = {"failed-test":{"test.class":"Jest Tests.x-pack/plugins/security_solution/public/detections/pages/detection_engine/rules/all","test.name":"AllRules it pulls from storage and does not set an auto refresh interval if storage indicates refresh is paused","test.failCount":1}} --> | 1.0 | Failing test: Jest Tests.x-pack/plugins/security_solution/public/detections/pages/detection_engine/rules/all - AllRules it pulls from storage and does not set an auto refresh interval if storage indicates refresh is paused - A test failed on a tracked branch
```
Error: Method “simulate” is meant to be run on 1 node. 0 found instead.
<html>
<head>
<style
id="ace_editor.css"
>
.ace_editor {position: relative;overflow: hidden;font: 12px/normal 'Monaco', 'Menlo', 'Ubuntu Mono', 'Consolas', 'source-code-pro', monospace;direction: ltr;text-align: left;-webkit-tap-highlight-color: rgba(0, 0, 0, 0);}.ace_scroller {position: absolute;overflow: hidden;top: 0;bottom: 0;background-color: inherit;-ms-user-select: none;-moz-user-select: none;-webkit-user-select: none;user-select: none;cursor: text;}.ace_content {position: absolute;-moz-box-sizing: border-box;-webkit-box-sizing: border-box;box-sizing: border-box;min-width: 100%;}.ace_dragging .ace_scroller:before{position: absolute;top: 0;left: 0;right: 0;bottom: 0;content: '';background: rgba(250, 250, 250, 0.01);z-index: 1000;}.ace_dragging.ace_dark .ace_scroller:before{background: rgba(0, 0, 0, 0.01);}.ace_selecting, .ace_selecting * {cursor: text !important;}.ace_gutter {position: absolute;overflow : hidden;width: auto;top: 0;bottom: 0;left: 0;cursor: default;z-index: 4;-ms-user-select: none;-moz-user-select: none;-webkit-user-select: none;user-select: none;}.ace_gutter-active-line {position: absolute;left: 0;right: 0;}.ace_scroller.ace_scroll-left {box-shadow: 17px 0 16px -16px rgba(0, 0, 0, 0.4) inset;}.ace_gutter-cell {padding-left: 19px;padding-right: 6px;background-repeat: no-repeat;}.ace_gutter-cell.ace_error {background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAMAAAAoLQ9TAAABOFBMVEX/////////QRswFAb/Ui4wFAYwFAYwFAaWGAfDRymzOSH/PxswFAb/SiUwFAYwFAbUPRvjQiDllog5HhHdRybsTi3/Tyv9Tir+Syj/UC3////XurebMBIwFAb/RSHbPx/gUzfdwL3kzMivKBAwFAbbvbnhPx66NhowFAYwFAaZJg8wFAaxKBDZurf/RB6mMxb/SCMwFAYwFAbxQB3+RB4wFAb/Qhy4Oh+4QifbNRcwFAYwFAYwFAb/QRzdNhgwFAYwFAbav7v/Uy7oaE68MBK5LxLewr/r2NXewLswFAaxJw4wFAbkPRy2PyYwFAaxKhLm1tMwFAazPiQwFAaUGAb/QBrfOx3bvrv/VC/maE4wFAbRPBq6MRO8Qynew8Dp2tjfwb0wFAbx6eju5+by6uns4uH9/f36+vr/GkHjAAAAYnRSTlMAGt+64rnWu/bo8eAA4InH3+DwoN7j4eLi4xP99Nfg4+b+/u9B/eDs1MD1mO7+4PHg2MXa347g7vDizMLN4eG+Pv7i5evs/v79yu7S3/DV7/498Yv24eH+4ufQ3Ozu/v7+y13sRqwAAADLSURBVHjaZc/XDsFgGIBhtDrshlitmk2IrbHFqL2pvXf/+78DPokj7+Fz9qpU/9UXJIlhmPaTaQ6QPaz0mm+5gwkgovcV6GZzd5JtCQwgsxoHOvJO15kleRLAnMgHFIESUEPmawB9ngmelTtipwwfASilxOLyiV5UVUyVAfbG0cCPHig+GBkzAENHS0AstVF6bacZIOzgLmxsHbt2OecNgJC83JERmePUYq8ARGkJx6XtFsdddBQgZE2nPR6CICZhawjA4Fb/chv+399kfR+MMMDGOQAAAABJRU5ErkJggg==");background-repeat: no-repeat;background-position: 2px center;}.ace_gutter-cell.ace_warning {background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAMAAAAoLQ9TAAAAmVBMVEX///8AAAD///8AAAAAAABPSzb/5sAAAAB/blH/73z/ulkAAAAAAAD85pkAAAAAAAACAgP/vGz/rkDerGbGrV7/pkQICAf////e0IsAAAD/oED/qTvhrnUAAAD/yHD/njcAAADuv2r/nz//oTj/p064oGf/zHAAAAA9Nir/tFIAAAD/tlTiuWf/tkIAAACynXEAAAAAAAAtIRW7zBpBAAAAM3RSTlMAABR1m7RXO8Ln31Z36zT+neXe5OzooRDfn+TZ4p3h2hTf4t3k3ucyrN1K5+Xaks52Sfs9CXgrAAAAjklEQVR42o3PbQ+CIBQFYEwboPhSYgoYunIqqLn6/z8uYdH8Vmdnu9vz4WwXgN/xTPRD2+sgOcZjsge/whXZgUaYYvT8QnuJaUrjrHUQreGczuEafQCO/SJTufTbroWsPgsllVhq3wJEk2jUSzX3CUEDJC84707djRc5MTAQxoLgupWRwW6UB5fS++NV8AbOZgnsC7BpEAAAAABJRU5ErkJggg==");background-position: 2px center;}.ace_gutter-cell.ace_info {background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAAAAAA6mKC9AAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAAJ0Uk5TAAB2k804AAAAPklEQVQY02NgIB68QuO3tiLznjAwpKTgNyDbMegwisCHZUETUZV0ZqOquBpXj2rtnpSJT1AEnnRmL2OgGgAAIKkRQap2htgAAAAASUVORK5CYII=");background-position: 2px center;}.ace_dark .ace_gutter-cell.ace_info {background-image: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQBAMAAADt3eJSAAAAJFBMVEUAAAChoaGAgIAqKiq+vr6tra1ZWVmUlJSbm5s8PDxubm56enrdgzg3AAAAAXRSTlMAQObYZgAAAClJREFUeNpjYMAPdsMYHegyJZFQBlsUlMFVCWUYKkAZMxZAGdxlDMQBAG+TBP4B6RyJAAAAAElFTkSuQmCC");}.ace_scrollbar {position: absolute;right: 0;bottom: 0;z-index: 6;}.ace_scrollbar-inner {position: absolute;cursor: text;left: 0;top: 0;}.ace_scrollbar-v{overflow-x: hidden;overflow-y: scroll;top: 0;}.ace_scrollbar-h {overflow-x: scroll;overflow-y: hidden;left: 0;}.ace_print-margin {position: absolute;height: 100%;}.ace_text-input {position: absolute;z-index: 0;width: 0.5em;height: 1em;opacity: 0;background: transparent;-moz-appearance: none;appearance: none;border: none;resize: none;outline: none;overflow: hidden;font: inherit;padding: 0 1px;margin: 0 -1px;text-indent: -1em;-ms-user-select: text;-moz-user-select: text;-webkit-user-select: text;user-select: text;white-space: pre!important;}.ace_text-input.ace_composition {background: inherit;color: inherit;z-index: 1000;opacity: 1;text-indent: 0;}.ace_layer {z-index: 1;position: absolute;overflow: hidden;word-wrap: normal;white-space: pre;height: 100%;width: 100%;-moz-box-sizing: border-box;-webkit-box-sizing: border-box;box-sizing: border-box;pointer-events: none;}.ace_gutter-layer {position: relative;width: auto;text-align: right;pointer-events: auto;}.ace_text-layer {font: inherit !important;}.ace_cjk {display: inline-block;text-align: center;}.ace_cursor-layer {z-index: 4;}.ace_cursor {z-index: 4;position: absolute;-moz-box-sizing: border-box;-webkit-box-sizing: border-box;box-sizing: border-box;border-left: 2px solid;transform: translatez(0);}.ace_multiselect .ace_cursor {border-left-width: 1px;}.ace_slim-cursors .ace_cursor {border-left-width: 1px;}.ace_overwrite-cursors .ace_cursor {border-left-width: 0;border-bottom: 1px solid;}.ace_hidden-cursors .ace_cursor {opacity: 0.2;}.ace_smooth-blinking .ace_cursor {-webkit-transition: opacity 0.18s;transition: opacity 0.18s;}.ace_marker-layer .ace_step, .ace_marker-layer .ace_stack {position: absolute;z-index: 3;}.ace_marker-layer .ace_selection {position: absolute;z-index: 5;}.ace_marker-layer .ace_bracket {position: absolute;z-index: 6;}.ace_marker-layer .ace_active-line {position: absolute;z-index: 2;}.ace_marker-layer .ace_selected-word {position: absolute;z-index: 4;-moz-box-sizing: border-box;-webkit-box-sizing: border-box;box-sizing: border-box;}.ace_line .ace_fold {-moz-box-sizing: border-box;-webkit-box-sizing: border-box;box-sizing: border-box;display: inline-block;height: 11px;margin-top: -2px;vertical-align: middle;background-image:url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABEAAAAJCAYAAADU6McMAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAJpJREFUeNpi/P//PwOlgAXGYGRklAVSokD8GmjwY1wasKljQpYACtpCFeADcHVQfQyMQAwzwAZI3wJKvCLkfKBaMSClBlR7BOQikCFGQEErIH0VqkabiGCAqwUadAzZJRxQr/0gwiXIal8zQQPnNVTgJ1TdawL0T5gBIP1MUJNhBv2HKoQHHjqNrA4WO4zY0glyNKLT2KIfIMAAQsdgGiXvgnYAAAAASUVORK5CYII="),url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAA3CAYAAADNNiA5AAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAACJJREFUeNpi+P//fxgTAwPDBxDxD078RSX+YeEyDFMCIMAAI3INmXiwf2YAAAAASUVORK5CYII=");background-repeat: no-repeat, repeat-x;background-position: center center, top left;color: transparent;border: 1px solid black;border-radius: 2px;cursor: pointer;pointer-events: auto;}.ace_dark .ace_fold {}.ace_fold:hover{background-image:url("data:image/png;ba...
at ReactWrapper.single (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/enzyme/src/ReactWrapper.js:1168:13)
at ReactWrapper.simulate (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/enzyme/src/ReactWrapper.js:665:17)
at /opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/x-pack/plugins/security_solution/public/detections/pages/detection_engine/rules/all/index.test.tsx:269:72
at runWithExpensiveErrorDiagnosticsDisabled (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/@testing-library/dom/dist/config.js:51:12)
at checkCallback (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/@testing-library/dom/dist/wait-for.js:127:77)
at /opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/@testing-library/dom/dist/wait-for.js:72:9
at new Promise (<anonymous>)
at waitFor (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/@testing-library/dom/dist/wait-for.js:40:10)
at /opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/@testing-library/dom/dist/wait-for.js:174:54
at /opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/@testing-library/react/dist/pure.js:57:22
at batchedUpdates$1 (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/react-dom/cjs/react-dom.development.js:24386:12)
at act (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/react-dom/cjs/react-dom-test-utils.development.js:1092:14)
at asyncAct (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/@testing-library/react/dist/act-compat.js:119:12)
at Object.asyncWrapper (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/@testing-library/react/dist/pure.js:56:35)
at waitForWrapper (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/@testing-library/dom/dist/wait-for.js:174:35)
at Object.<anonymous> (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/x-pack/plugins/security_solution/public/detections/pages/detection_engine/rules/all/index.test.tsx:261:11)
at Promise.then.completed (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/utils.js:276:28)
at new Promise (<anonymous>)
at callAsyncCircusFn (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/utils.js:216:10)
at _callCircusTest (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/run.js:212:40)
at _runTest (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/run.js:149:3)
at _runTestsForDescribeBlock (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/run.js:63:9)
at _runTestsForDescribeBlock (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/run.js:57:9)
at run (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/run.js:25:3)
at runAndTransformResultsToJestFormat (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapterInit.js:176:21)
at jestAdapter (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:109:19)
at runTestInternal (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-runner/build/runTest.js:380:16)
at runTest (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-runner/build/runTest.js:472:34)
at Object.worker (/opt/local-ssd/buildkite/builds/kb-c2-16-5f46ff99a20c2822/elastic/kibana-hourly/kibana/node_modules/jest-runner/build/testWorker.js:133:12)
```
First failure: [CI Build - 7.16](https://buildkite.com/elastic/kibana-hourly/builds/1857#bf83d7ba-ceb5-49c6-976f-46f0d8fddf64)
<!-- kibanaCiData = {"failed-test":{"test.class":"Jest Tests.x-pack/plugins/security_solution/public/detections/pages/detection_engine/rules/all","test.name":"AllRules it pulls from storage and does not set an auto refresh interval if storage indicates refresh is paused","test.failCount":1}} --> | test | failing test jest tests x pack plugins security solution public detections pages detection engine rules all allrules it pulls from storage and does not set an auto refresh interval if storage indicates refresh is paused a test failed on a tracked branch error method “simulate” is meant to be run on node found instead style id ace editor css ace editor position relative overflow hidden font normal monaco menlo ubuntu mono consolas source code pro monospace direction ltr text align left webkit tap highlight color rgba ace scroller position absolute overflow hidden top bottom background color inherit ms user select none moz user select none webkit user select none user select none cursor text ace content position absolute moz box sizing border box webkit box sizing border box box sizing border box min width ace dragging ace scroller before position absolute top left right bottom content background rgba z index ace dragging ace dark ace scroller before background rgba ace selecting ace selecting cursor text important ace gutter position absolute overflow hidden width auto top bottom left cursor default z index ms user select none moz user select none webkit user select none user select none ace gutter active line position absolute left right ace scroller ace scroll left box shadow rgba inset ace gutter cell padding left padding right background repeat no repeat ace gutter cell ace error background image url data image png qrswfab pxswfab syj xurebmbiwfab rshbpx vc vr gkhjaaaaynrstlmagt b chv background repeat no repeat background position center ace gutter cell ace warning background image url data image png blh vgz pkqicaf oed qtvhrnuaaad yhd nz otj tfiaaad tltiuwf sgoczjsge background position center ace gutter cell ace info background image url data image png background position center ace dark ace gutter cell ace info background image url data image png ace scrollbar position absolute right bottom z index ace scrollbar inner position absolute cursor text left top ace scrollbar v overflow x hidden overflow y scroll top ace scrollbar h overflow x scroll overflow y hidden left ace print margin position absolute height ace text input position absolute z index width height opacity background transparent moz appearance none appearance none border none resize none outline none overflow hidden font inherit padding margin text indent ms user select text moz user select text webkit user select text user select text white space pre important ace text input ace composition background inherit color inherit z index opacity text indent ace layer z index position absolute overflow hidden word wrap normal white space pre height width moz box sizing border box webkit box sizing border box box sizing border box pointer events none ace gutter layer position relative width auto text align right pointer events auto ace text layer font inherit important ace cjk display inline block text align center ace cursor layer z index ace cursor z index position absolute moz box sizing border box webkit box sizing border box box sizing border box border left solid transform translatez ace multiselect ace cursor border left width ace slim cursors ace cursor border left width ace overwrite cursors ace cursor border left width border bottom solid ace hidden cursors ace cursor opacity ace smooth blinking ace cursor webkit transition opacity transition opacity ace marker layer ace step ace marker layer ace stack position absolute z index ace marker layer ace selection position absolute z index ace marker layer ace bracket position absolute z index ace marker layer ace active line position absolute z index ace marker layer ace selected word position absolute z index moz box sizing border box webkit box sizing border box box sizing border box ace line ace fold moz box sizing border box webkit box sizing border box box sizing border box display inline block height margin top vertical align middle background image url data image png p url data image png p background repeat no repeat repeat x background position center center top left color transparent border solid black border radius cursor pointer pointer events auto ace dark ace fold ace fold hover background image url data image png ba at reactwrapper single opt local ssd buildkite builds kb elastic kibana hourly kibana node modules enzyme src reactwrapper js at reactwrapper simulate opt local ssd buildkite builds kb elastic kibana hourly kibana node modules enzyme src reactwrapper js at opt local ssd buildkite builds kb elastic kibana hourly kibana x pack plugins security solution public detections pages detection engine rules all index test tsx at runwithexpensiveerrordiagnosticsdisabled opt local ssd buildkite builds kb elastic kibana hourly kibana node modules testing library dom dist config js at checkcallback opt local ssd buildkite builds kb elastic kibana hourly kibana node modules testing library dom dist wait for js at opt local ssd buildkite builds kb elastic kibana hourly kibana node modules testing library dom dist wait for js at new promise at waitfor opt local ssd buildkite builds kb elastic kibana hourly kibana node modules testing library dom dist wait for js at opt local ssd buildkite builds kb elastic kibana hourly kibana node modules testing library dom dist wait for js at opt local ssd buildkite builds kb elastic kibana hourly kibana node modules testing library react dist pure js at batchedupdates opt local ssd buildkite builds kb elastic kibana hourly kibana node modules react dom cjs react dom development js at act opt local ssd buildkite builds kb elastic kibana hourly kibana node modules react dom cjs react dom test utils development js at asyncact opt local ssd buildkite builds kb elastic kibana hourly kibana node modules testing library react dist act compat js at object asyncwrapper opt local ssd buildkite builds kb elastic kibana hourly kibana node modules testing library react dist pure js at waitforwrapper opt local ssd buildkite builds kb elastic kibana hourly kibana node modules testing library dom dist wait for js at object opt local ssd buildkite builds kb elastic kibana hourly kibana x pack plugins security solution public detections pages detection engine rules all index test tsx at promise then completed opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest circus build utils js at new promise at callasynccircusfn opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest circus build utils js at callcircustest opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest circus build run js at runtest opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest circus build run js at runtestsfordescribeblock opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest circus build run js at runtestsfordescribeblock opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest circus build run js at run opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest circus build run js at runandtransformresultstojestformat opt local ssd buildkite builds kb elastic kibana hourly kibana node modules jest circus build legacy code todo rewrite jestadapterinit 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 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 |
2,823 | 8,365,065,520 | IssuesEvent | 2018-10-04 02:43:18 | number9473/nn-algorithm | https://api.github.com/repos/number9473/nn-algorithm | opened | Local Binary Convolutional Neural Networks | Network Architecture | # Local Binary Convolutional Neural Networks #
- Author: Felix Juefei-Xu, Vishnu Naresh Boddeti, Marios Savvides
- Origin: https://arxiv.org/abs/1608.06049
- Related:
- https://github.com/whoisraibolt/LBCNN
| 1.0 | Local Binary Convolutional Neural Networks - # Local Binary Convolutional Neural Networks #
- Author: Felix Juefei-Xu, Vishnu Naresh Boddeti, Marios Savvides
- Origin: https://arxiv.org/abs/1608.06049
- Related:
- https://github.com/whoisraibolt/LBCNN
| non_test | local binary convolutional neural networks local binary convolutional neural networks author felix juefei xu vishnu naresh boddeti marios savvides origin related | 0 |
162,499 | 12,678,544,041 | IssuesEvent | 2020-06-19 09:57:41 | microsoft/azure-tools-for-java | https://api.github.com/repos/microsoft/azure-tools-for-java | closed | [Intellij][Spark on ADL] The containers number does not update right now | HDInsight IntelliJ Internal Test wontfix | **Repro bits**
https://vscjavaci.cloudapp.net/job/Azure_Toolkits_for_Java/job/AzureToolsManager_PR/1678/Azure/
**Repro Steps**
1. Create a new Provision cluster with **2** containers
2. Right click it and choose Update item
3. Change the containers number to **4** and Click OK
4. Choose view cluster status on context menu
**Actual result**
The containers number does not update, until wait a moment, it can be changed
**Screenshot**
| 1.0 | [Intellij][Spark on ADL] The containers number does not update right now - **Repro bits**
https://vscjavaci.cloudapp.net/job/Azure_Toolkits_for_Java/job/AzureToolsManager_PR/1678/Azure/
**Repro Steps**
1. Create a new Provision cluster with **2** containers
2. Right click it and choose Update item
3. Change the containers number to **4** and Click OK
4. Choose view cluster status on context menu
**Actual result**
The containers number does not update, until wait a moment, it can be changed
**Screenshot**
| test | the containers number does not update right now repro bits repro steps create a new provision cluster with containers right click it and choose update item change the containers number to and click ok choose view cluster status on context menu actual result the containers number does not update until wait a moment it can be changed screenshot | 1 |
308,656 | 26,620,926,379 | IssuesEvent | 2023-01-24 11:09:27 | microsoft/vscode | https://api.github.com/repos/microsoft/vscode | closed | Test: Detect unsafe terminal profiles | testplan-item | Refs: #167721, #125387
- [x] windows @dbaeumer
Complexity: 3
[Create Issue](https://github.com/microsoft/vscode/issues/new?body=Testing+%23172085%0A%0A&assignees=Tyriar)
---
Shells with "unsafe paths", those writable to by multiple users, can now be detected. Check https://github.com/microsoft/vscode/pull/170193 for detailed instructions on the new UX. To verify, install the following shells and ensure they are detected and warn the user that it's potentially unsafe:
- Cygwin installed to either `c:\cygwin` or `c:\cygwin64`
- MSYS2 bash installed to `c:\msys64`
- Cmder
- Installed to `c:\cmder` should warn
- Installed to a manually set up `CMDER_ROOT` variable should be detected and _not_ warn
| 1.0 | Test: Detect unsafe terminal profiles - Refs: #167721, #125387
- [x] windows @dbaeumer
Complexity: 3
[Create Issue](https://github.com/microsoft/vscode/issues/new?body=Testing+%23172085%0A%0A&assignees=Tyriar)
---
Shells with "unsafe paths", those writable to by multiple users, can now be detected. Check https://github.com/microsoft/vscode/pull/170193 for detailed instructions on the new UX. To verify, install the following shells and ensure they are detected and warn the user that it's potentially unsafe:
- Cygwin installed to either `c:\cygwin` or `c:\cygwin64`
- MSYS2 bash installed to `c:\msys64`
- Cmder
- Installed to `c:\cmder` should warn
- Installed to a manually set up `CMDER_ROOT` variable should be detected and _not_ warn
| test | test detect unsafe terminal profiles refs windows dbaeumer complexity shells with unsafe paths those writable to by multiple users can now be detected check for detailed instructions on the new ux to verify install the following shells and ensure they are detected and warn the user that it s potentially unsafe cygwin installed to either c cygwin or c bash installed to c cmder installed to c cmder should warn installed to a manually set up cmder root variable should be detected and not warn | 1 |
761,098 | 26,666,926,400 | IssuesEvent | 2023-01-26 05:38:23 | wso2/api-manager | https://api.github.com/repos/wso2/api-manager | closed | Maven cannot build a CApp for the Integration Studio project which contains a Proxy Service | Type/Bug Priority/High Component/IntegrationStudio Affected/IntegrationStudio-8.1.0 | ### Description
When we try to build a CApp for the Integration Studio project which contains a Proxy Service using maven, the following error is observed. As a result, the CApp won't get created.
### Steps to Reproduce
1. Create a new Integration Studio Project
2. Create a new Proxy Service
3. Make sure the Proxy Service config is selected in the CompositeExporter project
4. Execute `mvn clean install` command to build the project
### Affected Component
IntegrationStudio
### Version
8.1.0
### Environment Details (with versions)
_No response_
### Relevant Log Output
```shell
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.593 s
[INFO] Finished at: 2023-01-25T14:41:17+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project TestProxyCompositeExporter: Could not resolve dependencies for project com.example:TestProxyCompositeExporter:carbon/application:1.0.0-SNAPSHOT: Failure to find com.example.proxy-service.metadata:HelloWorldProxy_proxy_metadata:yaml:1.0.0 in https://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the local repository, resolution will not be reattempted until the update interval of wso2-nexus has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
```
### Related Issues
_No response_
### Suggested Labels
_No response_ | 1.0 | Maven cannot build a CApp for the Integration Studio project which contains a Proxy Service - ### Description
When we try to build a CApp for the Integration Studio project which contains a Proxy Service using maven, the following error is observed. As a result, the CApp won't get created.
### Steps to Reproduce
1. Create a new Integration Studio Project
2. Create a new Proxy Service
3. Make sure the Proxy Service config is selected in the CompositeExporter project
4. Execute `mvn clean install` command to build the project
### Affected Component
IntegrationStudio
### Version
8.1.0
### Environment Details (with versions)
_No response_
### Relevant Log Output
```shell
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.593 s
[INFO] Finished at: 2023-01-25T14:41:17+05:30
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project TestProxyCompositeExporter: Could not resolve dependencies for project com.example:TestProxyCompositeExporter:carbon/application:1.0.0-SNAPSHOT: Failure to find com.example.proxy-service.metadata:HelloWorldProxy_proxy_metadata:yaml:1.0.0 in https://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the local repository, resolution will not be reattempted until the update interval of wso2-nexus has elapsed or updates are forced -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
```
### Related Issues
_No response_
### Suggested Labels
_No response_ | non_test | maven cannot build a capp for the integration studio project which contains a proxy service description when we try to build a capp for the integration studio project which contains a proxy service using maven the following error is observed as a result the capp won t get created steps to reproduce create a new integration studio project create a new proxy service make sure the proxy service config is selected in the compositeexporter project execute mvn clean install command to build the project affected component integrationstudio version environment details with versions no response relevant log output shell build failure total time s finished at failed to execute goal on project testproxycompositeexporter could not resolve dependencies for project com example testproxycompositeexporter carbon application snapshot failure to find com example proxy service metadata helloworldproxy proxy metadata yaml in was cached in the local repository resolution will not be reattempted until the update interval of nexus has elapsed or updates are forced to see the full stack trace of the errors re run maven with the e switch re run maven using the x switch to enable full debug logging related issues no response suggested labels no response | 0 |
203,354 | 15,363,484,429 | IssuesEvent | 2021-03-01 20:49:46 | nucypher/nucypher | https://api.github.com/repos/nucypher/nucypher | opened | FleetSensor in tests has access to fully-functional Ursulas | Test 🔍 | In `test/fixtures.py` there are several fixtures that create a bunch of Ursulas: `fleet_of_highperf_mocked_ursulas`, `blockchain_ursulas`. After creation they are given to each other to learn about circumventing the standard channel (REST API). As a result:
- `FleetSensor`s own fully-functional Ursulas, and not `is_me=False` remote images. This can result in different test and production behavior, and possible side effects (since `is_me=True` Ursulas can mutate their internal state, which `FleetSensor` does not expect to happen).
- Ursulas are shared between `FleetSensor`s, which can also interfere with test behavior (since, again, these Ursulas are mutable).
| 1.0 | FleetSensor in tests has access to fully-functional Ursulas - In `test/fixtures.py` there are several fixtures that create a bunch of Ursulas: `fleet_of_highperf_mocked_ursulas`, `blockchain_ursulas`. After creation they are given to each other to learn about circumventing the standard channel (REST API). As a result:
- `FleetSensor`s own fully-functional Ursulas, and not `is_me=False` remote images. This can result in different test and production behavior, and possible side effects (since `is_me=True` Ursulas can mutate their internal state, which `FleetSensor` does not expect to happen).
- Ursulas are shared between `FleetSensor`s, which can also interfere with test behavior (since, again, these Ursulas are mutable).
| test | fleetsensor in tests has access to fully functional ursulas in test fixtures py there are several fixtures that create a bunch of ursulas fleet of highperf mocked ursulas blockchain ursulas after creation they are given to each other to learn about circumventing the standard channel rest api as a result fleetsensor s own fully functional ursulas and not is me false remote images this can result in different test and production behavior and possible side effects since is me true ursulas can mutate their internal state which fleetsensor does not expect to happen ursulas are shared between fleetsensor s which can also interfere with test behavior since again these ursulas are mutable | 1 |
546,606 | 16,015,861,137 | IssuesEvent | 2021-04-20 15:55:36 | ampproject/amphtml | https://api.github.com/repos/ampproject/amphtml | closed | Remote page attachments broken on iOS webviews | P1: High Priority Type: Bug WG: stories | Remote page attachments are broken on iOS webviews, or at least in the Google native app and Discover.
All history navigations need to originate from a clicked anchor tag. We should replace our navigation based on the history API, and trigger a click on the anchor tag.
https://github.com/ampproject/amphtml/blob/e03dba1b1fe7ff1d4dfeb59ba257ab4d0d93341f/extensions/amp-story/1.0/amp-story-page-attachment.js#L294-L298
The swipe up interaction we get is not a trusted interaction on Safari (it is on Chrome), but because this is a `_self` navigation, it won't be blocked by the browser/webview.
This fix has been prototyped and tested already.
cc @ampproject/wg-stories | 1.0 | Remote page attachments broken on iOS webviews - Remote page attachments are broken on iOS webviews, or at least in the Google native app and Discover.
All history navigations need to originate from a clicked anchor tag. We should replace our navigation based on the history API, and trigger a click on the anchor tag.
https://github.com/ampproject/amphtml/blob/e03dba1b1fe7ff1d4dfeb59ba257ab4d0d93341f/extensions/amp-story/1.0/amp-story-page-attachment.js#L294-L298
The swipe up interaction we get is not a trusted interaction on Safari (it is on Chrome), but because this is a `_self` navigation, it won't be blocked by the browser/webview.
This fix has been prototyped and tested already.
cc @ampproject/wg-stories | non_test | remote page attachments broken on ios webviews remote page attachments are broken on ios webviews or at least in the google native app and discover all history navigations need to originate from a clicked anchor tag we should replace our navigation based on the history api and trigger a click on the anchor tag the swipe up interaction we get is not a trusted interaction on safari it is on chrome but because this is a self navigation it won t be blocked by the browser webview this fix has been prototyped and tested already cc ampproject wg stories | 0 |
50,663 | 13,551,403,126 | IssuesEvent | 2020-09-17 11:03:02 | loftwah/trouble.gg | https://api.github.com/repos/loftwah/trouble.gg | closed | CVE-2020-13822 (High) detected in elliptic-6.5.2.tgz - autoclosed | security vulnerability | ## CVE-2020-13822 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>elliptic-6.5.2.tgz</b></p></summary>
<p>EC cryptography</p>
<p>Library home page: <a href="https://registry.npmjs.org/elliptic/-/elliptic-6.5.2.tgz">https://registry.npmjs.org/elliptic/-/elliptic-6.5.2.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/trouble.gg/wp-content/themes/twentytwenty/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/trouble.gg/wp-content/themes/twentytwenty/node_modules/elliptic/package.json</p>
<p>
Dependency Hierarchy:
- scripts-5.1.0.tgz (Root Library)
- webpack-4.43.0.tgz
- node-libs-browser-2.2.1.tgz
- crypto-browserify-3.12.0.tgz
- browserify-sign-4.2.0.tgz
- :x: **elliptic-6.5.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/loftwah/trouble.gg/commit/41cee91bec8d7f7b602f0068a0d8f245894224b8">41cee91bec8d7f7b602f0068a0d8f245894224b8</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The Elliptic package 6.5.2 for Node.js allows ECDSA signature malleability via variations in encoding, leading '\0' bytes, or integer overflows. This could conceivably have a security-relevant impact if an application relied on a single canonical signature.
<p>Publish Date: 2020-06-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-13822>CVE-2020-13822</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/indutny/elliptic/tree/v6.5.3">https://github.com/indutny/elliptic/tree/v6.5.3</a></p>
<p>Release Date: 2020-06-04</p>
<p>Fix Resolution: v6.5.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-13822 (High) detected in elliptic-6.5.2.tgz - autoclosed - ## CVE-2020-13822 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>elliptic-6.5.2.tgz</b></p></summary>
<p>EC cryptography</p>
<p>Library home page: <a href="https://registry.npmjs.org/elliptic/-/elliptic-6.5.2.tgz">https://registry.npmjs.org/elliptic/-/elliptic-6.5.2.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/trouble.gg/wp-content/themes/twentytwenty/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/trouble.gg/wp-content/themes/twentytwenty/node_modules/elliptic/package.json</p>
<p>
Dependency Hierarchy:
- scripts-5.1.0.tgz (Root Library)
- webpack-4.43.0.tgz
- node-libs-browser-2.2.1.tgz
- crypto-browserify-3.12.0.tgz
- browserify-sign-4.2.0.tgz
- :x: **elliptic-6.5.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/loftwah/trouble.gg/commit/41cee91bec8d7f7b602f0068a0d8f245894224b8">41cee91bec8d7f7b602f0068a0d8f245894224b8</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The Elliptic package 6.5.2 for Node.js allows ECDSA signature malleability via variations in encoding, leading '\0' bytes, or integer overflows. This could conceivably have a security-relevant impact if an application relied on a single canonical signature.
<p>Publish Date: 2020-06-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-13822>CVE-2020-13822</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/indutny/elliptic/tree/v6.5.3">https://github.com/indutny/elliptic/tree/v6.5.3</a></p>
<p>Release Date: 2020-06-04</p>
<p>Fix Resolution: v6.5.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_test | cve high detected in elliptic tgz autoclosed cve high severity vulnerability vulnerable library elliptic tgz ec cryptography library home page a href path to dependency file tmp ws scm trouble gg wp content themes twentytwenty package json path to vulnerable library tmp ws scm trouble gg wp content themes twentytwenty node modules elliptic package json dependency hierarchy scripts tgz root library webpack tgz node libs browser tgz crypto browserify tgz browserify sign tgz x elliptic tgz vulnerable library found in head commit a href vulnerability details the elliptic package for node js allows ecdsa signature malleability via variations in encoding leading bytes or integer overflows this could conceivably have a security relevant impact if an application relied on a single canonical signature publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
231,840 | 18,798,549,503 | IssuesEvent | 2021-11-09 02:53:58 | microsoft/AzureStorageExplorer | https://api.github.com/repos/microsoft/AzureStorageExplorer | closed | There is an extra slash at the beginning of the path for file share items | 🧪 testing :gear: files :beetle: regression | **Storage Explorer Version**: 1.22.0-dev
**Build Number**: 20211106.4
**Branch**: main
**Platform/OS**: Windows 10/Linux Ubuntu 20.04/MacOS Monterey 12.0.1
**Architecture**: ia32/x64
**How Found**: From running test cases
**Regression From**: Previous release (1.21.3)
## Steps to Reproduce ##
1. Expand one storage account -> File Shares.
2. Create a file share -> Upload one file (without changing the 'Destination directory' field).
3. Right click the file -> Click 'Copy Path' -> Paste the path to the clipboard
4. Check the path does not begin with a slash.
## Expected Experience ##
The path does not begin with a slash.
## Actual Experience ##
The path begins with a slash.
## Additional Context ##
1. Fail to run 'Selection Statistics' for items under file shares.
For one item:
For multi items:
2. Fail to check properties for one item under file shares.
3. There is an extra slash in the URL of one item under file shares.
https://arbactest.file.core.windows.net/fs1//clone1
| 1.0 | There is an extra slash at the beginning of the path for file share items - **Storage Explorer Version**: 1.22.0-dev
**Build Number**: 20211106.4
**Branch**: main
**Platform/OS**: Windows 10/Linux Ubuntu 20.04/MacOS Monterey 12.0.1
**Architecture**: ia32/x64
**How Found**: From running test cases
**Regression From**: Previous release (1.21.3)
## Steps to Reproduce ##
1. Expand one storage account -> File Shares.
2. Create a file share -> Upload one file (without changing the 'Destination directory' field).
3. Right click the file -> Click 'Copy Path' -> Paste the path to the clipboard
4. Check the path does not begin with a slash.
## Expected Experience ##
The path does not begin with a slash.
## Actual Experience ##
The path begins with a slash.
## Additional Context ##
1. Fail to run 'Selection Statistics' for items under file shares.
For one item:
For multi items:
2. Fail to check properties for one item under file shares.
3. There is an extra slash in the URL of one item under file shares.
https://arbactest.file.core.windows.net/fs1//clone1
| test | there is an extra slash at the beginning of the path for file share items storage explorer version dev build number branch main platform os windows linux ubuntu macos monterey architecture how found from running test cases regression from previous release steps to reproduce expand one storage account file shares create a file share upload one file without changing the destination directory field right click the file click copy path paste the path to the clipboard check the path does not begin with a slash expected experience the path does not begin with a slash actual experience the path begins with a slash additional context fail to run selection statistics for items under file shares for one item for multi items fail to check properties for one item under file shares there is an extra slash in the url of one item under file shares | 1 |
216,693 | 16,795,527,543 | IssuesEvent | 2021-06-16 02:33:01 | pombase/pombase-chado | https://api.github.com/repos/pombase/pombase-chado | closed | in the logs, misreported ID | bug needs testing | https://curation.pombase.org/dumps/latest_build/logs/identifier_problems.txt
CDS SPAC750.08c.1 from gene: SPAC750.08c: can't find feature for: FAM155A
CDS SPAC750.08c.1 from gene: SPAC750.08c: can't find feature for: FAM155B
CDS SPAC750.08c.1 from gene: SPAC750.08c: can't find feature for: SGD:S000029663
CDS SPAC750.08c.1 from gene: SPAC750.08c: can't find feature for: SGD:S000029664
CDS SPAC750.08c.1 from gene: SPAC750.08c: can't find feature for: SGD:S000029665
CDS SPAC750.08c.1 from gene: SPAC750.08c: can't find feature for: SGD:S000029662
the first 2 aren't SPAC750.08c, they are SPAC1F5.08c ? | 1.0 | in the logs, misreported ID - https://curation.pombase.org/dumps/latest_build/logs/identifier_problems.txt
CDS SPAC750.08c.1 from gene: SPAC750.08c: can't find feature for: FAM155A
CDS SPAC750.08c.1 from gene: SPAC750.08c: can't find feature for: FAM155B
CDS SPAC750.08c.1 from gene: SPAC750.08c: can't find feature for: SGD:S000029663
CDS SPAC750.08c.1 from gene: SPAC750.08c: can't find feature for: SGD:S000029664
CDS SPAC750.08c.1 from gene: SPAC750.08c: can't find feature for: SGD:S000029665
CDS SPAC750.08c.1 from gene: SPAC750.08c: can't find feature for: SGD:S000029662
the first 2 aren't SPAC750.08c, they are SPAC1F5.08c ? | test | in the logs misreported id cds from gene can t find feature for cds from gene can t find feature for cds from gene can t find feature for sgd cds from gene can t find feature for sgd cds from gene can t find feature for sgd cds from gene can t find feature for sgd the first aren t they are | 1 |
120,296 | 10,112,819,745 | IssuesEvent | 2019-07-30 15:24:44 | nim-lang/Nim | https://api.github.com/repos/nim-lang/Nim | closed | regression: CI failing (texplain.nim) | High Priority Test suite | CI is failing (texplain.nim), making all recently rebased PR's fail since ~ july 26
see https://travis-ci.org/nim-lang/Nim/jobs/565206359 for nim's own CI:
```
FAIL: tests/concepts/texplain.nim C
Test "tests/concepts/texplain.nim" in category "concepts"
Failure: reMsgsDiffer
```
### Additional Information
https://github.com/nim-lang/Nim/commit/ceb1a1b6884b28f3f3f88a4be5663d7f0b1f1155 shows as the 1st red commit; not sure if that commit is the culprit though.
| 1.0 | regression: CI failing (texplain.nim) - CI is failing (texplain.nim), making all recently rebased PR's fail since ~ july 26
see https://travis-ci.org/nim-lang/Nim/jobs/565206359 for nim's own CI:
```
FAIL: tests/concepts/texplain.nim C
Test "tests/concepts/texplain.nim" in category "concepts"
Failure: reMsgsDiffer
```
### Additional Information
https://github.com/nim-lang/Nim/commit/ceb1a1b6884b28f3f3f88a4be5663d7f0b1f1155 shows as the 1st red commit; not sure if that commit is the culprit though.
| test | regression ci failing texplain nim ci is failing texplain nim making all recently rebased pr s fail since july see for nim s own ci fail tests concepts texplain nim c test tests concepts texplain nim in category concepts failure remsgsdiffer additional information shows as the red commit not sure if that commit is the culprit though | 1 |
16,020 | 3,493,320,022 | IssuesEvent | 2016-01-05 01:06:42 | winjs/winjs | https://api.github.com/repos/winjs/winjs | opened | Protractor: test case "CorsicaTests.ViewBox: SwappingChildren" may be flakey | .kind: testbug | `Test case "CorsicaTests.ViewBox: SwappingChildren " in "winjs/bin/tests/ViewBox/test.html" failed in the latest Protractor run. Protractor determined that this failure is a regression from a previous build of Microsoft Edge (based on historical data). Please investigate why this test has begun failing.`
Dodesn't repro when run manually, may be a flakey test. | 1.0 | Protractor: test case "CorsicaTests.ViewBox: SwappingChildren" may be flakey - `Test case "CorsicaTests.ViewBox: SwappingChildren " in "winjs/bin/tests/ViewBox/test.html" failed in the latest Protractor run. Protractor determined that this failure is a regression from a previous build of Microsoft Edge (based on historical data). Please investigate why this test has begun failing.`
Dodesn't repro when run manually, may be a flakey test. | test | protractor test case corsicatests viewbox swappingchildren may be flakey test case corsicatests viewbox swappingchildren in winjs bin tests viewbox test html failed in the latest protractor run protractor determined that this failure is a regression from a previous build of microsoft edge based on historical data please investigate why this test has begun failing dodesn t repro when run manually may be a flakey test | 1 |
94,940 | 8,527,039,461 | IssuesEvent | 2018-11-02 18:10:02 | ukwa/ukwa-ui | https://api.github.com/repos/ukwa/ukwa-ui | closed | Images for Special Collections | priority: high tested: all good | Could we add the following images to the Special Collections (https://beta.webarchive.org.uk/en/ukwa/collection) please?
19th Century English literature https://pixabay.com/en/book-read-old-literature-pages-1659717/
Aging https://pixabay.com/en/hands-walking-stick-elderly-981400/
British Countryside https://pixabay.com/en/mailbox-postbox-red-box-postal-1497635/
Cambridge Network https://pixabay.com/en/academic-ancient-architecture-2769/
Celtic Studies https://pixabay.com/en/dolmen-celtic-artifact-menhir-474072/
Children’s website https://pixabay.com/en/children-win-success-video-game-593313/
Climate Change Debates https://pixabay.com/en/hands-globe-earth-protection-1222866/
Cornwall https://pixabay.com/en/charlestown-cornwall-maritime-1361248/
Credit Crunch https://pixabay.com/en/credit-squeeze-taxation-purse-tax-522549/
Darwin 200 https://pixabay.com/en/charles-robert-darwin-scientists-62911/
Dickens Bicentenary https://commons.wikimedia.org/wiki/File:Dickens_by_Watkins_1858.png
Energy https://pixabay.com/en/light-bulb-lights-bokeh-energy-3535435/
European Parliament Elections 2009 https://alpha.webarchive.org.uk/en/ukwa/img/collections/collection_4.png
Family History https://pixabay.com/en/library-card-catalog-books-research-2811601/
Festivals https://pixabay.com/en/concert-confetti-party-event-club-2527495/
First World War Centenary https://pixabay.com/en/color-cross-day-death-flower-loss-20701/
G8 Summit 2005 https://pixabay.com/en/g8-states-industrialized-countries-1693446/
Indian Ocean Tsunami 2004 https://pixabay.com/en/jungle-lost-stranded-tsunami-1433858/
Isle of Man https://pixabay.com/en/isle-of-man-flag-legs-official-26904/
Jersey Collection https://pixabay.com/en/jersey-castle-orgueil-knight-horse-1703449/
London Mayoral Election 2008 https://alpha.webarchive.org.uk/en/ukwa/img/collections/collection_60.png
National Assembly for Wales Election 2016 https://alpha.webarchive.org.uk/en/ukwa/img/collections/collection_60.png
Parliamentary archives https://pixabay.com/en/palace-of-westminster-palace-of-3554588/ Religion/Theology https://pixabay.com/en/candles-church-light-lights-prayer-2628473/
Political Action and Communication https://pixabay.com/en/megaphone-loud-speaker-speaker-1480342/
Scottish Government https://pixabay.com/en/glasgow-city-chambers-glasgow-city-3508561/
Queens diamond jubilee 2012 https://alpha.webarchive.org.uk/en/ukwa/img/collections/collection_851.png
Scottish Parliamentary Election 2007 https://alpha.webarchive.org.uk/en/ukwa/img/collections/collection_60.png
Spending Cuts 2010: Impact on Social Welfare https://pixabay.com/en/credit-squeeze-taxation-purse-tax-522549/
Sports Collection https://www.pexels.com/photo/brown-and-white-track-field-163444/
Stephen Hawking https://commons.wikimedia.org/wiki/Stephen_Hawking#/media/File:Stephen_Hawking.StarChild.jpg
UK General Election 2005 https://alpha.webarchive.org.uk/en/ukwa/img/collections/collection_60.png
UK General Election 2010 https://alpha.webarchive.org.uk/en/ukwa/img/collections/collection_60.png
Video Games https://unsplash.com/photos/eCktzGjC-iU
Web Comic Archive https://unsplash.com/photos/rNNmnC67h7g
Welsh devolution referendum 2011 https://alpha.webarchive.org.uk/en/ukwa/img/collections/collection_60.png
| 1.0 | Images for Special Collections - Could we add the following images to the Special Collections (https://beta.webarchive.org.uk/en/ukwa/collection) please?
19th Century English literature https://pixabay.com/en/book-read-old-literature-pages-1659717/
Aging https://pixabay.com/en/hands-walking-stick-elderly-981400/
British Countryside https://pixabay.com/en/mailbox-postbox-red-box-postal-1497635/
Cambridge Network https://pixabay.com/en/academic-ancient-architecture-2769/
Celtic Studies https://pixabay.com/en/dolmen-celtic-artifact-menhir-474072/
Children’s website https://pixabay.com/en/children-win-success-video-game-593313/
Climate Change Debates https://pixabay.com/en/hands-globe-earth-protection-1222866/
Cornwall https://pixabay.com/en/charlestown-cornwall-maritime-1361248/
Credit Crunch https://pixabay.com/en/credit-squeeze-taxation-purse-tax-522549/
Darwin 200 https://pixabay.com/en/charles-robert-darwin-scientists-62911/
Dickens Bicentenary https://commons.wikimedia.org/wiki/File:Dickens_by_Watkins_1858.png
Energy https://pixabay.com/en/light-bulb-lights-bokeh-energy-3535435/
European Parliament Elections 2009 https://alpha.webarchive.org.uk/en/ukwa/img/collections/collection_4.png
Family History https://pixabay.com/en/library-card-catalog-books-research-2811601/
Festivals https://pixabay.com/en/concert-confetti-party-event-club-2527495/
First World War Centenary https://pixabay.com/en/color-cross-day-death-flower-loss-20701/
G8 Summit 2005 https://pixabay.com/en/g8-states-industrialized-countries-1693446/
Indian Ocean Tsunami 2004 https://pixabay.com/en/jungle-lost-stranded-tsunami-1433858/
Isle of Man https://pixabay.com/en/isle-of-man-flag-legs-official-26904/
Jersey Collection https://pixabay.com/en/jersey-castle-orgueil-knight-horse-1703449/
London Mayoral Election 2008 https://alpha.webarchive.org.uk/en/ukwa/img/collections/collection_60.png
National Assembly for Wales Election 2016 https://alpha.webarchive.org.uk/en/ukwa/img/collections/collection_60.png
Parliamentary archives https://pixabay.com/en/palace-of-westminster-palace-of-3554588/ Religion/Theology https://pixabay.com/en/candles-church-light-lights-prayer-2628473/
Political Action and Communication https://pixabay.com/en/megaphone-loud-speaker-speaker-1480342/
Scottish Government https://pixabay.com/en/glasgow-city-chambers-glasgow-city-3508561/
Queens diamond jubilee 2012 https://alpha.webarchive.org.uk/en/ukwa/img/collections/collection_851.png
Scottish Parliamentary Election 2007 https://alpha.webarchive.org.uk/en/ukwa/img/collections/collection_60.png
Spending Cuts 2010: Impact on Social Welfare https://pixabay.com/en/credit-squeeze-taxation-purse-tax-522549/
Sports Collection https://www.pexels.com/photo/brown-and-white-track-field-163444/
Stephen Hawking https://commons.wikimedia.org/wiki/Stephen_Hawking#/media/File:Stephen_Hawking.StarChild.jpg
UK General Election 2005 https://alpha.webarchive.org.uk/en/ukwa/img/collections/collection_60.png
UK General Election 2010 https://alpha.webarchive.org.uk/en/ukwa/img/collections/collection_60.png
Video Games https://unsplash.com/photos/eCktzGjC-iU
Web Comic Archive https://unsplash.com/photos/rNNmnC67h7g
Welsh devolution referendum 2011 https://alpha.webarchive.org.uk/en/ukwa/img/collections/collection_60.png
| test | images for special collections could we add the following images to the special collections please century english literature aging british countryside cambridge network celtic studies children’s website climate change debates cornwall credit crunch darwin dickens bicentenary energy european parliament elections family history festivals first world war centenary summit indian ocean tsunami isle of man jersey collection london mayoral election national assembly for wales election parliamentary archives religion theology political action and communication scottish government queens diamond jubilee scottish parliamentary election spending cuts impact on social welfare sports collection stephen hawking uk general election uk general election video games web comic archive welsh devolution referendum | 1 |
232,026 | 18,840,691,697 | IssuesEvent | 2021-11-11 09:12:41 | kyberorg/yalsee | https://api.github.com/repos/kyberorg/yalsee | closed | Rename Test methods to improve readablility | tests refactoring | 1. `beforeTests` -> `beforeAllTests`
2. `beforeTest` -> `beforeEachTest` | 1.0 | Rename Test methods to improve readablility - 1. `beforeTests` -> `beforeAllTests`
2. `beforeTest` -> `beforeEachTest` | test | rename test methods to improve readablility beforetests beforealltests beforetest beforeeachtest | 1 |
127,065 | 10,450,691,354 | IssuesEvent | 2019-09-19 11:09:02 | AeroScripts/QuestieDev | https://api.github.com/repos/AeroScripts/QuestieDev | closed | buzzbox 827 missing turnin location | database test again | buzzbox 827 is missing quest turnin location. it is at Darkshore 36.6 46.3 | 1.0 | buzzbox 827 missing turnin location - buzzbox 827 is missing quest turnin location. it is at Darkshore 36.6 46.3 | test | buzzbox missing turnin location buzzbox is missing quest turnin location it is at darkshore | 1 |
110,270 | 9,441,435,287 | IssuesEvent | 2019-04-15 01:34:27 | dotnet/corefx | https://api.github.com/repos/dotnet/corefx | closed | Multicast Socket tests failing on Nano | area-System.Net.Sockets disabled-test os-windows-nano | https://github.com/dotnet/corefx/pull/29903#issuecomment-392196091
The Sockets multicast tests are failing on Nano:
https://mc.dot.net/#/user/davidsh/pr~2Fjenkins~2Fdotnet~2Fcorefx~2Fmaster~2F/test~2Ffunctional~2Fcli~2F/5f5dae7b004d88bdc2927927d655380c56087396/workItem/System.Net.Sockets.Tests
>System.Net.Sockets.SocketException : The requested address is not valid in its context. | 1.0 | Multicast Socket tests failing on Nano - https://github.com/dotnet/corefx/pull/29903#issuecomment-392196091
The Sockets multicast tests are failing on Nano:
https://mc.dot.net/#/user/davidsh/pr~2Fjenkins~2Fdotnet~2Fcorefx~2Fmaster~2F/test~2Ffunctional~2Fcli~2F/5f5dae7b004d88bdc2927927d655380c56087396/workItem/System.Net.Sockets.Tests
>System.Net.Sockets.SocketException : The requested address is not valid in its context. | test | multicast socket tests failing on nano the sockets multicast tests are failing on nano system net sockets socketexception the requested address is not valid in its context | 1 |
295,414 | 25,474,121,117 | IssuesEvent | 2022-11-25 12:54:30 | NFDI4Chem/nmrium-react-wrapper | https://api.github.com/repos/NFDI4Chem/nmrium-react-wrapper | closed | save version object with the other data inside the database | testing | @CS76
```ts
{
version: <number>
spectra:[],
molecules:[],
// ... other properties
}
```
what is missing in the data you save in the database is the version object which is important for the migration process that is done when importing the .nmrium object inside the NMRium and without it the NMRium went be able to display the data.
another thing worth mentioning is the migration functionality moved to nmr-load-save package which means we can use the migration separately if we need it to migrate the old data | 1.0 | save version object with the other data inside the database - @CS76
```ts
{
version: <number>
spectra:[],
molecules:[],
// ... other properties
}
```
what is missing in the data you save in the database is the version object which is important for the migration process that is done when importing the .nmrium object inside the NMRium and without it the NMRium went be able to display the data.
another thing worth mentioning is the migration functionality moved to nmr-load-save package which means we can use the migration separately if we need it to migrate the old data | test | save version object with the other data inside the database ts version spectra molecules other properties what is missing in the data you save in the database is the version object which is important for the migration process that is done when importing the nmrium object inside the nmrium and without it the nmrium went be able to display the data another thing worth mentioning is the migration functionality moved to nmr load save package which means we can use the migration separately if we need it to migrate the old data | 1 |
87,000 | 10,861,085,255 | IssuesEvent | 2019-11-14 10:22:03 | davidsalsa/behind-the-tankard | https://api.github.com/repos/davidsalsa/behind-the-tankard | opened | Intergration design team 14-11-2019 | Design | Create a scene with the art assets that follow the rules of the level layout. | 1.0 | Intergration design team 14-11-2019 - Create a scene with the art assets that follow the rules of the level layout. | non_test | intergration design team create a scene with the art assets that follow the rules of the level layout | 0 |
435,866 | 30,524,192,467 | IssuesEvent | 2023-07-19 10:04:53 | scikit-learn/scikit-learn | https://api.github.com/repos/scikit-learn/scikit-learn | closed | DOC Link to headers mis-poisitioned | Documentation Needs Triage | ### Describe the issue linked to the documentation
Link to a header in a page, e.g., the 'regression' subheading: https://scikit-learn.org/1.2/modules/linear_model.html#regression directs a position a bit further down the page from the header. Tested on firefox and chromium.
Potentially this is caused by the navbar, i.e. the header would start at the top of the page if there was no navbar.
This may be unique to my system and happy to close if others can't replicate.
### Suggest a potential alternative/fix
_No response_ | 1.0 | DOC Link to headers mis-poisitioned - ### Describe the issue linked to the documentation
Link to a header in a page, e.g., the 'regression' subheading: https://scikit-learn.org/1.2/modules/linear_model.html#regression directs a position a bit further down the page from the header. Tested on firefox and chromium.
Potentially this is caused by the navbar, i.e. the header would start at the top of the page if there was no navbar.
This may be unique to my system and happy to close if others can't replicate.
### Suggest a potential alternative/fix
_No response_ | non_test | doc link to headers mis poisitioned describe the issue linked to the documentation link to a header in a page e g the regression subheading directs a position a bit further down the page from the header tested on firefox and chromium potentially this is caused by the navbar i e the header would start at the top of the page if there was no navbar this may be unique to my system and happy to close if others can t replicate suggest a potential alternative fix no response | 0 |
117,481 | 17,482,019,455 | IssuesEvent | 2021-08-09 05:06:08 | turkdevops/sourcegraph | https://api.github.com/repos/turkdevops/sourcegraph | opened | CVE-2021-3664 (Medium) detected in url-parse-1.4.4.tgz | security vulnerability | ## CVE-2021-3664 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>url-parse-1.4.4.tgz</b></p></summary>
<p>Small footprint URL parser that works seamlessly across Node.js and browser environments</p>
<p>Library home page: <a href="https://registry.npmjs.org/url-parse/-/url-parse-1.4.4.tgz">https://registry.npmjs.org/url-parse/-/url-parse-1.4.4.tgz</a></p>
<p>Path to dependency file: sourcegraph/package.json</p>
<p>Path to vulnerable library: sourcegraph/node_modules/url-parse</p>
<p>
Dependency Hierarchy:
- core-5.3.18.tgz (Root Library)
- react-dev-utils-9.0.1.tgz
- sockjs-client-1.3.0.tgz
- :x: **url-parse-1.4.4.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/sourcegraph/commit/9d189cf333b1133a03812b329b4b97da449f5469">9d189cf333b1133a03812b329b4b97da449f5469</a></p>
<p>Found in base branch: <b>dev/seed-tool</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>
url-parse is vulnerable to URL Redirection to Untrusted Site
<p>Publish Date: 2021-07-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3664>CVE-2021-3664</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: 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-2021-3664">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3664</a></p>
<p>Release Date: 2021-07-26</p>
<p>Fix Resolution: url-parse - 1.5.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-3664 (Medium) detected in url-parse-1.4.4.tgz - ## CVE-2021-3664 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>url-parse-1.4.4.tgz</b></p></summary>
<p>Small footprint URL parser that works seamlessly across Node.js and browser environments</p>
<p>Library home page: <a href="https://registry.npmjs.org/url-parse/-/url-parse-1.4.4.tgz">https://registry.npmjs.org/url-parse/-/url-parse-1.4.4.tgz</a></p>
<p>Path to dependency file: sourcegraph/package.json</p>
<p>Path to vulnerable library: sourcegraph/node_modules/url-parse</p>
<p>
Dependency Hierarchy:
- core-5.3.18.tgz (Root Library)
- react-dev-utils-9.0.1.tgz
- sockjs-client-1.3.0.tgz
- :x: **url-parse-1.4.4.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/sourcegraph/commit/9d189cf333b1133a03812b329b4b97da449f5469">9d189cf333b1133a03812b329b4b97da449f5469</a></p>
<p>Found in base branch: <b>dev/seed-tool</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>
url-parse is vulnerable to URL Redirection to Untrusted Site
<p>Publish Date: 2021-07-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3664>CVE-2021-3664</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: 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-2021-3664">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3664</a></p>
<p>Release Date: 2021-07-26</p>
<p>Fix Resolution: url-parse - 1.5.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 url parse tgz cve medium severity vulnerability vulnerable library url parse tgz small footprint url parser that works seamlessly across node js and browser environments library home page a href path to dependency file sourcegraph package json path to vulnerable library sourcegraph node modules url parse dependency hierarchy core tgz root library react dev utils tgz sockjs client tgz x url parse tgz vulnerable library found in head commit a href found in base branch dev seed tool vulnerability details url parse is vulnerable to url redirection to untrusted site 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 low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution url parse step up your open source security game with whitesource | 0 |
291,381 | 8,924,111,393 | IssuesEvent | 2019-01-21 17:31:07 | fac-15/casual-sports | https://api.github.com/repos/fac-15/casual-sports | closed | Your commented-out tests work! | Priority-2 rubie | From what I can see, your commented out database tests work for the most part - you just need to tweak them to match your linting rules (`prefer-arrow-function`)
That said, your `error` tests aren't working, and that's pretty important - you need to know if errors are thrown when they're supposed to be, otherwise your tests might be passing by accident | 1.0 | Your commented-out tests work! - From what I can see, your commented out database tests work for the most part - you just need to tweak them to match your linting rules (`prefer-arrow-function`)
That said, your `error` tests aren't working, and that's pretty important - you need to know if errors are thrown when they're supposed to be, otherwise your tests might be passing by accident | non_test | your commented out tests work from what i can see your commented out database tests work for the most part you just need to tweak them to match your linting rules prefer arrow function that said your error tests aren t working and that s pretty important you need to know if errors are thrown when they re supposed to be otherwise your tests might be passing by accident | 0 |
177,386 | 21,474,005,787 | IssuesEvent | 2022-04-26 12:10:19 | tabacws-remediation-demos/Java-Demo-Rem | https://api.github.com/repos/tabacws-remediation-demos/Java-Demo-Rem | opened | CVE-2022-23457 (High) detected in esapi-2.1.0.1.jar | security vulnerability | ## CVE-2022-23457 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>esapi-2.1.0.1.jar</b></p></summary>
<p>The Enterprise Security API (ESAPI) project is an OWASP project
to create simple strong security controls for every web platform.
Security controls are not simple to build. You can read about the
hundreds of pitfalls for unwary developers on the OWASP web site. By
providing developers with a set of strong controls, we aim to
eliminate some of the complexity of creating secure web applications.
This can result in significant cost savings across the SDLC.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /ository/org/owasp/esapi/esapi/2.1.0.1/esapi-2.1.0.1.jar</p>
<p>
Dependency Hierarchy:
- :x: **esapi-2.1.0.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/tabacws-remediation-demos/Java-Demo-Rem/commit/018eccd7980798c5f39292e9c7133e829e9ed7a3">018eccd7980798c5f39292e9c7133e829e9ed7a3</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>
ESAPI (The OWASP Enterprise Security API) is a free, open source, web application security control library. Prior to version 2.3.0.0, the default implementation of `Validator.getValidDirectoryPath(String, String, File, boolean)` may incorrectly treat the tested input string as a child of the specified parent directory. This potentially could allow control-flow bypass checks to be defeated if an attack can specify the entire string representing the 'input' path. This vulnerability is patched in release 2.3.0.0 of ESAPI. As a workaround, it is possible to write one's own implementation of the Validator interface. However, maintainers do not recommend this.
<p>Publish Date: 2022-04-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23457>CVE-2022-23457</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: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/ESAPI/esapi-java-legacy/security/advisories/GHSA-8m5h-hrqm-pxm2">https://github.com/ESAPI/esapi-java-legacy/security/advisories/GHSA-8m5h-hrqm-pxm2</a></p>
<p>Release Date: 2022-04-25</p>
<p>Fix Resolution: org.owasp.esapi:esapi:2.3.0.0</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.owasp.esapi","packageName":"esapi","packageVersion":"2.1.0.1","packageFilePaths":["/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"org.owasp.esapi:esapi:2.1.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.owasp.esapi:esapi:2.3.0.0","isBinary":false}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2022-23457","vulnerabilityDetails":"ESAPI (The OWASP Enterprise Security API) is a free, open source, web application security control library. Prior to version 2.3.0.0, the default implementation of `Validator.getValidDirectoryPath(String, String, File, boolean)` may incorrectly treat the tested input string as a child of the specified parent directory. This potentially could allow control-flow bypass checks to be defeated if an attack can specify the entire string representing the \u0027input\u0027 path. This vulnerability is patched in release 2.3.0.0 of ESAPI. As a workaround, it is possible to write one\u0027s own implementation of the Validator interface. However, maintainers do not recommend this.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23457","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"High","PR":"Low","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2022-23457 (High) detected in esapi-2.1.0.1.jar - ## CVE-2022-23457 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>esapi-2.1.0.1.jar</b></p></summary>
<p>The Enterprise Security API (ESAPI) project is an OWASP project
to create simple strong security controls for every web platform.
Security controls are not simple to build. You can read about the
hundreds of pitfalls for unwary developers on the OWASP web site. By
providing developers with a set of strong controls, we aim to
eliminate some of the complexity of creating secure web applications.
This can result in significant cost savings across the SDLC.</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /ository/org/owasp/esapi/esapi/2.1.0.1/esapi-2.1.0.1.jar</p>
<p>
Dependency Hierarchy:
- :x: **esapi-2.1.0.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/tabacws-remediation-demos/Java-Demo-Rem/commit/018eccd7980798c5f39292e9c7133e829e9ed7a3">018eccd7980798c5f39292e9c7133e829e9ed7a3</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>
ESAPI (The OWASP Enterprise Security API) is a free, open source, web application security control library. Prior to version 2.3.0.0, the default implementation of `Validator.getValidDirectoryPath(String, String, File, boolean)` may incorrectly treat the tested input string as a child of the specified parent directory. This potentially could allow control-flow bypass checks to be defeated if an attack can specify the entire string representing the 'input' path. This vulnerability is patched in release 2.3.0.0 of ESAPI. As a workaround, it is possible to write one's own implementation of the Validator interface. However, maintainers do not recommend this.
<p>Publish Date: 2022-04-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23457>CVE-2022-23457</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: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/ESAPI/esapi-java-legacy/security/advisories/GHSA-8m5h-hrqm-pxm2">https://github.com/ESAPI/esapi-java-legacy/security/advisories/GHSA-8m5h-hrqm-pxm2</a></p>
<p>Release Date: 2022-04-25</p>
<p>Fix Resolution: org.owasp.esapi:esapi:2.3.0.0</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.owasp.esapi","packageName":"esapi","packageVersion":"2.1.0.1","packageFilePaths":["/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"org.owasp.esapi:esapi:2.1.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.owasp.esapi:esapi:2.3.0.0","isBinary":false}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2022-23457","vulnerabilityDetails":"ESAPI (The OWASP Enterprise Security API) is a free, open source, web application security control library. Prior to version 2.3.0.0, the default implementation of `Validator.getValidDirectoryPath(String, String, File, boolean)` may incorrectly treat the tested input string as a child of the specified parent directory. This potentially could allow control-flow bypass checks to be defeated if an attack can specify the entire string representing the \u0027input\u0027 path. This vulnerability is patched in release 2.3.0.0 of ESAPI. As a workaround, it is possible to write one\u0027s own implementation of the Validator interface. However, maintainers do not recommend this.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23457","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"High","PR":"Low","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_test | cve high detected in esapi jar cve high severity vulnerability vulnerable library esapi jar the enterprise security api esapi project is an owasp project to create simple strong security controls for every web platform security controls are not simple to build you can read about the hundreds of pitfalls for unwary developers on the owasp web site by providing developers with a set of strong controls we aim to eliminate some of the complexity of creating secure web applications this can result in significant cost savings across the sdlc path to dependency file pom xml path to vulnerable library ository org owasp esapi esapi esapi jar dependency hierarchy x esapi jar vulnerable library found in head commit a href found in base branch main vulnerability details esapi the owasp enterprise security api is a free open source web application security control library prior to version the default implementation of validator getvaliddirectorypath string string file boolean may incorrectly treat the tested input string as a child of the specified parent directory this potentially could allow control flow bypass checks to be defeated if an attack can specify the entire string representing the input path this vulnerability is patched in release of esapi as a workaround it is possible to write one s own implementation of the validator interface however maintainers do not recommend this publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org owasp esapi esapi rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree org owasp esapi esapi isminimumfixversionavailable true minimumfixversion org owasp esapi esapi isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails esapi the owasp enterprise security api is a free open source web application security control library prior to version the default implementation of validator getvaliddirectorypath string string file boolean may incorrectly treat the tested input string as a child of the specified parent directory this potentially could allow control flow bypass checks to be defeated if an attack can specify the entire string representing the path this vulnerability is patched in release of esapi as a workaround it is possible to write one own implementation of the validator interface however maintainers do not recommend this vulnerabilityurl | 0 |
299,413 | 25,901,505,483 | IssuesEvent | 2022-12-15 06:18:52 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | roachtest: sequelize failed | C-test-failure O-robot O-roachtest T-sql-sessions branch-release-22.2.0 | roachtest.sequelize [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/7423859?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/7423859?buildTab=artifacts#/sequelize) on release-22.2.0 @ [234c9295cc02150f919cfa96b09ee2fa07b68ace](https://github.com/cockroachdb/cockroach/commits/234c9295cc02150f919cfa96b09ee2fa07b68ace):
```
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/canary.go:138
| [...repeated from below...]
Wraps: (2) all attempts failed for install dependencies
Wraps: (3) attached stack trace
-- stack trace:
| main.(*clusterImpl).RunE
| main/pkg/cmd/roachtest/cluster.go:2018
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.repeatRunE
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/canary.go:131
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerSequelize.func1
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/sequelize.go:134
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerSequelize.func2
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/sequelize.go:159
| main.(*testRunner).runTest.func2
| main/pkg/cmd/roachtest/test_runner.go:930
| runtime.goexit
| GOROOT/src/runtime/asm_amd64.s:1594
Wraps: (4) output in run_134242.146558784_n1_cd
Wraps: (5) cd /mnt/data1/sequelize && sudo npm i returned
| stderr:
| ERROR: npm v9.1.1 is known not to run on Node.js v12.22.12. You'll need to
| upgrade to a newer Node.js version in order to use this version of npm. This
| version of npm supports the following node versions: ``^14.17.0 || ^16.13.0 ||
| >=18.0.0``. You can find the latest version at https://nodejs.org/.
|
| ERROR:
| /usr/lib/node_modules/npm/lib/utils/exit-handler.js:22
| const hasLoadedNpm = npm?.config.loaded
| ^
|
| SyntaxError: Unexpected token '.'
| at wrapSafe (internal/modules/cjs/loader.js:915:16)
| at Module._compile (internal/modules/cjs/loader.js:963:27)
| at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
| at Module.load (internal/modules/cjs/loader.js:863:32)
| at Function.Module._load (internal/modules/cjs/loader.js:708:14)
| at Module.require (internal/modules/cjs/loader.js:887:19)
| at require (internal/modules/cjs/helpers.js:74:18)
| at module.exports (/usr/lib/node_modules/npm/lib/cli.js:76:23)
| at Object.<anonymous> (/usr/lib/node_modules/npm/bin/npm-cli.js:2:25)
| at Module._compile (internal/modules/cjs/loader.js:999:30)
|
| stdout:
Wraps: (6) COMMAND_PROBLEM
Wraps: (7) Node 1. Command with error:
| ``````
| cd /mnt/data1/sequelize && sudo npm i
| ``````
Wraps: (8) exit status 1
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) *errutil.withPrefix (5) *cluster.WithCommandDetails (6) errors.Cmd (7) *hintdetail.withDetail (8) *exec.ExitError
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=4</code>
, <code>ROACHTEST_encrypted=false</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
<details><summary>Same failure on other branches</summary>
<p>
- #91661 roachtest: sequelize failed [C-test-failure O-roachtest O-robot T-sql-experience branch-release-22.1 release-blocker]
</p>
</details>
/cc @cockroachdb/sql-experience
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*sequelize.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-21372 | 2.0 | roachtest: sequelize failed - roachtest.sequelize [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/7423859?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/7423859?buildTab=artifacts#/sequelize) on release-22.2.0 @ [234c9295cc02150f919cfa96b09ee2fa07b68ace](https://github.com/cockroachdb/cockroach/commits/234c9295cc02150f919cfa96b09ee2fa07b68ace):
```
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/canary.go:138
| [...repeated from below...]
Wraps: (2) all attempts failed for install dependencies
Wraps: (3) attached stack trace
-- stack trace:
| main.(*clusterImpl).RunE
| main/pkg/cmd/roachtest/cluster.go:2018
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.repeatRunE
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/canary.go:131
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerSequelize.func1
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/sequelize.go:134
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerSequelize.func2
| github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/sequelize.go:159
| main.(*testRunner).runTest.func2
| main/pkg/cmd/roachtest/test_runner.go:930
| runtime.goexit
| GOROOT/src/runtime/asm_amd64.s:1594
Wraps: (4) output in run_134242.146558784_n1_cd
Wraps: (5) cd /mnt/data1/sequelize && sudo npm i returned
| stderr:
| ERROR: npm v9.1.1 is known not to run on Node.js v12.22.12. You'll need to
| upgrade to a newer Node.js version in order to use this version of npm. This
| version of npm supports the following node versions: ``^14.17.0 || ^16.13.0 ||
| >=18.0.0``. You can find the latest version at https://nodejs.org/.
|
| ERROR:
| /usr/lib/node_modules/npm/lib/utils/exit-handler.js:22
| const hasLoadedNpm = npm?.config.loaded
| ^
|
| SyntaxError: Unexpected token '.'
| at wrapSafe (internal/modules/cjs/loader.js:915:16)
| at Module._compile (internal/modules/cjs/loader.js:963:27)
| at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
| at Module.load (internal/modules/cjs/loader.js:863:32)
| at Function.Module._load (internal/modules/cjs/loader.js:708:14)
| at Module.require (internal/modules/cjs/loader.js:887:19)
| at require (internal/modules/cjs/helpers.js:74:18)
| at module.exports (/usr/lib/node_modules/npm/lib/cli.js:76:23)
| at Object.<anonymous> (/usr/lib/node_modules/npm/bin/npm-cli.js:2:25)
| at Module._compile (internal/modules/cjs/loader.js:999:30)
|
| stdout:
Wraps: (6) COMMAND_PROBLEM
Wraps: (7) Node 1. Command with error:
| ``````
| cd /mnt/data1/sequelize && sudo npm i
| ``````
Wraps: (8) exit status 1
Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) *errutil.withPrefix (5) *cluster.WithCommandDetails (6) errors.Cmd (7) *hintdetail.withDetail (8) *exec.ExitError
```
<p>Parameters: <code>ROACHTEST_cloud=gce</code>
, <code>ROACHTEST_cpu=4</code>
, <code>ROACHTEST_encrypted=false</code>
, <code>ROACHTEST_ssd=0</code>
</p>
<details><summary>Help</summary>
<p>
See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md)
See: [How To Investigate \(internal\)](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7)
</p>
</details>
<details><summary>Same failure on other branches</summary>
<p>
- #91661 roachtest: sequelize failed [C-test-failure O-roachtest O-robot T-sql-experience branch-release-22.1 release-blocker]
</p>
</details>
/cc @cockroachdb/sql-experience
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*sequelize.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-21372 | test | roachtest sequelize failed roachtest sequelize with on release github com cockroachdb cockroach pkg cmd roachtest tests canary go wraps all attempts failed for install dependencies wraps attached stack trace stack trace main clusterimpl rune main pkg cmd roachtest cluster go github com cockroachdb cockroach pkg cmd roachtest tests repeatrune github com cockroachdb cockroach pkg cmd roachtest tests canary go github com cockroachdb cockroach pkg cmd roachtest tests registersequelize github com cockroachdb cockroach pkg cmd roachtest tests sequelize go github com cockroachdb cockroach pkg cmd roachtest tests registersequelize github com cockroachdb cockroach pkg cmd roachtest tests sequelize go main testrunner runtest main pkg cmd roachtest test runner go runtime goexit goroot src runtime asm s wraps output in run cd wraps cd mnt sequelize sudo npm i returned stderr error npm is known not to run on node js you ll need to upgrade to a newer node js version in order to use this version of npm this version of npm supports the following node versions you can find the latest version at error usr lib node modules npm lib utils exit handler js const hasloadednpm npm config loaded syntaxerror unexpected token at wrapsafe internal modules cjs loader js at module compile internal modules cjs loader js at object module extensions js internal modules cjs loader js at module load internal modules cjs loader js at function module load internal modules cjs loader js at module require internal modules cjs loader js at require internal modules cjs helpers js at module exports usr lib node modules npm lib cli js at object usr lib node modules npm bin npm cli js at module compile internal modules cjs loader js stdout wraps command problem wraps node command with error cd mnt sequelize sudo npm i wraps exit status error types withstack withstack errutil withprefix withstack withstack errutil withprefix cluster withcommanddetails errors cmd hintdetail withdetail exec exiterror parameters roachtest cloud gce roachtest cpu roachtest encrypted false roachtest ssd help see see same failure on other branches roachtest sequelize failed cc cockroachdb sql experience jira issue crdb | 1 |
108,472 | 23,614,048,460 | IssuesEvent | 2022-08-24 14:32:42 | arduino/arduino-ide | https://api.github.com/repos/arduino/arduino-ide | opened | Fix dialogs UI scalability vol 2 - Unexpected dialog layouts | topic: code type: imperfection | ### Describe the problem
This is a follow-up of https://github.com/arduino/arduino-ide/pull/1311.
Several dialogs have an unexpected layout.
- If the board name is long, the board select dialog is ugly
- The new file dialog is too small. Start typing and use an unsupported file extension. The dialog grows with the validation error message.
<img width="248" alt="Screen Shot 2022-08-24 at 16 30 48" src="https://user-images.githubusercontent.com/1405703/186445358-43c671a0-40e5-4b31-956c-eed35a7d9194.png">
### To reproduce
See above
### Expected behavior
The dialogs look the same as before #1311
### Arduino IDE version
Version: 2.0.0-rc9.2.nightly-20220824 Date: 2022-08-24T03:48:57.272Z CLI Version: git-snapshot [04e70c53] Copyright © 2022 Arduino SA
### Operating system
macOS
### Operating system version
12.5.1
### Additional context
_No response_
### Issue checklist
- [X] I searched for previous reports in [the issue tracker](https://github.com/arduino/arduino-ide/issues?q=)
- [X] I verified the problem still occurs when using the latest [nightly build](https://github.com/arduino/arduino-ide#nightly-builds)
- [X] My report contains all necessary details | 1.0 | Fix dialogs UI scalability vol 2 - Unexpected dialog layouts - ### Describe the problem
This is a follow-up of https://github.com/arduino/arduino-ide/pull/1311.
Several dialogs have an unexpected layout.
- If the board name is long, the board select dialog is ugly
- The new file dialog is too small. Start typing and use an unsupported file extension. The dialog grows with the validation error message.
<img width="248" alt="Screen Shot 2022-08-24 at 16 30 48" src="https://user-images.githubusercontent.com/1405703/186445358-43c671a0-40e5-4b31-956c-eed35a7d9194.png">
### To reproduce
See above
### Expected behavior
The dialogs look the same as before #1311
### Arduino IDE version
Version: 2.0.0-rc9.2.nightly-20220824 Date: 2022-08-24T03:48:57.272Z CLI Version: git-snapshot [04e70c53] Copyright © 2022 Arduino SA
### Operating system
macOS
### Operating system version
12.5.1
### Additional context
_No response_
### Issue checklist
- [X] I searched for previous reports in [the issue tracker](https://github.com/arduino/arduino-ide/issues?q=)
- [X] I verified the problem still occurs when using the latest [nightly build](https://github.com/arduino/arduino-ide#nightly-builds)
- [X] My report contains all necessary details | non_test | fix dialogs ui scalability vol unexpected dialog layouts describe the problem this is a follow up of several dialogs have an unexpected layout if the board name is long the board select dialog is ugly the new file dialog is too small start typing and use an unsupported file extension the dialog grows with the validation error message img width alt screen shot at src to reproduce see above expected behavior the dialogs look the same as before arduino ide version version nightly date cli version git snapshot copyright © arduino sa operating system macos operating system version additional context no response issue checklist i searched for previous reports in i verified the problem still occurs when using the latest my report contains all necessary details | 0 |
244,282 | 20,621,440,748 | IssuesEvent | 2022-03-07 17:48:21 | near/nearcore | https://api.github.com/repos/near/nearcore | closed | Add script for checking requirements for running other CI scripts. | C-enhancement C-housekeeping A-testing A-CI | I've spent a few hours debugging why scripts don't work locally.
I found out that I had wrong version of yarn installed.
Let's add a script, which checks whenever all requirements are installed.
PR: https://github.com/near/nearcore/pull/5798 | 1.0 | Add script for checking requirements for running other CI scripts. - I've spent a few hours debugging why scripts don't work locally.
I found out that I had wrong version of yarn installed.
Let's add a script, which checks whenever all requirements are installed.
PR: https://github.com/near/nearcore/pull/5798 | test | add script for checking requirements for running other ci scripts i ve spent a few hours debugging why scripts don t work locally i found out that i had wrong version of yarn installed let s add a script which checks whenever all requirements are installed pr | 1 |
40,294 | 2,868,477,004 | IssuesEvent | 2015-06-05 19:03:27 | ceylon/ceylon-ide-eclipse | https://api.github.com/repos/ceylon/ceylon-ide-eclipse | closed | Performance bottleneck when stepping into a function with defaulted arguments | bug high priority launch/run/debug | When `JavaSearch.getCeylonSimpleName()` tries to find the Ceylon mapping of the method with defaulted arguments generated in Java Bytecode, it triggers the JDT parsingon the corresponding Ceylon code, which of course generates all sort of errors internally, but without throwing them. This makes debugging these parts of code very long !
This was show by the Java Mission Control profiler immediately ! | 1.0 | Performance bottleneck when stepping into a function with defaulted arguments - When `JavaSearch.getCeylonSimpleName()` tries to find the Ceylon mapping of the method with defaulted arguments generated in Java Bytecode, it triggers the JDT parsingon the corresponding Ceylon code, which of course generates all sort of errors internally, but without throwing them. This makes debugging these parts of code very long !
This was show by the Java Mission Control profiler immediately ! | non_test | performance bottleneck when stepping into a function with defaulted arguments when javasearch getceylonsimplename tries to find the ceylon mapping of the method with defaulted arguments generated in java bytecode it triggers the jdt parsingon the corresponding ceylon code which of course generates all sort of errors internally but without throwing them this makes debugging these parts of code very long this was show by the java mission control profiler immediately | 0 |
155,424 | 5,955,139,365 | IssuesEvent | 2017-05-28 01:53:44 | SWE574-Groupago/heritago | https://api.github.com/repos/SWE574-Groupago/heritago | closed | Target_id should be URI | annotations back-end bug priority: high | Target_id is currently saved as an integer. It should be a URI in accordance with the annotation specification. | 1.0 | Target_id should be URI - Target_id is currently saved as an integer. It should be a URI in accordance with the annotation specification. | non_test | target id should be uri target id is currently saved as an integer it should be a uri in accordance with the annotation specification | 0 |
427,196 | 29,802,420,637 | IssuesEvent | 2023-06-16 09:06:35 | RotherOSS/otobo | https://api.github.com/repos/RotherOSS/otobo | closed | Update POD of DynamicField/Backend.pm HasBehavior | documentation | I encountered a few behaviors missing in the POD. | 1.0 | Update POD of DynamicField/Backend.pm HasBehavior - I encountered a few behaviors missing in the POD. | non_test | update pod of dynamicfield backend pm hasbehavior i encountered a few behaviors missing in the pod | 0 |
227,575 | 25,081,506,552 | IssuesEvent | 2022-11-07 19:44:56 | AdamOswald/Hugging | https://api.github.com/repos/AdamOswald/Hugging | opened | protobuf-3.20.0-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl: 1 vulnerabilities (highest severity is: 7.5) | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>protobuf-3.20.0-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl</b></p></summary>
<p>Protocol Buffers</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/af/26/cf27940ece6bb8890a67f741eb9da5359b72749f816edf210a28fe01a247/protobuf-3.20.0-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/af/26/cf27940ece6bb8890a67f741eb9da5359b72749f816edf210a28fe01a247/protobuf-3.20.0-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/AdamOswald/Hugging/commit/53b8b4edbf9b8031770e7ae42ff1813e397b0d63">53b8b4edbf9b8031770e7ae42ff1813e397b0d63</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (protobuf version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-1941](https://www.mend.io/vulnerability-database/CVE-2022-1941) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | protobuf-3.20.0-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl | Direct | Google.Protobuf - 3.18.3,3.19.5,3.20.2,3.21.6;protobuf-python - 3.18.3,3.19.5,3.20.2,4.21.6 | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-1941</summary>
### Vulnerable Library - <b>protobuf-3.20.0-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl</b></p>
<p>Protocol Buffers</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/af/26/cf27940ece6bb8890a67f741eb9da5359b72749f816edf210a28fe01a247/protobuf-3.20.0-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/af/26/cf27940ece6bb8890a67f741eb9da5359b72749f816edf210a28fe01a247/protobuf-3.20.0-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **protobuf-3.20.0-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AdamOswald/Hugging/commit/53b8b4edbf9b8031770e7ae42ff1813e397b0d63">53b8b4edbf9b8031770e7ae42ff1813e397b0d63</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A parsing vulnerability for the MessageSet type in the ProtocolBuffers versions prior to and including 3.16.1, 3.17.3, 3.18.2, 3.19.4, 3.20.1 and 3.21.5 for protobuf-cpp, and versions prior to and including 3.16.1, 3.17.3, 3.18.2, 3.19.4, 3.20.1 and 4.21.5 for protobuf-python can lead to out of memory failures. A specially crafted message with multiple key-value per elements creates parsing issues, and can lead to a Denial of Service against services receiving unsanitized input. We recommend upgrading to versions 3.18.3, 3.19.5, 3.20.2, 3.21.6 for protobuf-cpp and 3.18.3, 3.19.5, 3.20.2, 4.21.6 for protobuf-python. Versions for 3.16 and 3.17 are no longer updated.
<p>Publish Date: 2022-09-22
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-1941>CVE-2022-1941</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cloud.google.com/support/bulletins#GCP-2022-019">https://cloud.google.com/support/bulletins#GCP-2022-019</a></p>
<p>Release Date: 2022-09-22</p>
<p>Fix Resolution: Google.Protobuf - 3.18.3,3.19.5,3.20.2,3.21.6;protobuf-python - 3.18.3,3.19.5,3.20.2,4.21.6</p>
</p>
<p></p>
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details> | True | protobuf-3.20.0-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl: 1 vulnerabilities (highest severity is: 7.5) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>protobuf-3.20.0-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl</b></p></summary>
<p>Protocol Buffers</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/af/26/cf27940ece6bb8890a67f741eb9da5359b72749f816edf210a28fe01a247/protobuf-3.20.0-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/af/26/cf27940ece6bb8890a67f741eb9da5359b72749f816edf210a28fe01a247/protobuf-3.20.0-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/AdamOswald/Hugging/commit/53b8b4edbf9b8031770e7ae42ff1813e397b0d63">53b8b4edbf9b8031770e7ae42ff1813e397b0d63</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (protobuf version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-1941](https://www.mend.io/vulnerability-database/CVE-2022-1941) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | protobuf-3.20.0-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl | Direct | Google.Protobuf - 3.18.3,3.19.5,3.20.2,3.21.6;protobuf-python - 3.18.3,3.19.5,3.20.2,4.21.6 | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-1941</summary>
### Vulnerable Library - <b>protobuf-3.20.0-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl</b></p>
<p>Protocol Buffers</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/af/26/cf27940ece6bb8890a67f741eb9da5359b72749f816edf210a28fe01a247/protobuf-3.20.0-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/af/26/cf27940ece6bb8890a67f741eb9da5359b72749f816edf210a28fe01a247/protobuf-3.20.0-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **protobuf-3.20.0-cp37-cp37m-manylinux_2_5_x86_64.manylinux1_x86_64.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AdamOswald/Hugging/commit/53b8b4edbf9b8031770e7ae42ff1813e397b0d63">53b8b4edbf9b8031770e7ae42ff1813e397b0d63</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A parsing vulnerability for the MessageSet type in the ProtocolBuffers versions prior to and including 3.16.1, 3.17.3, 3.18.2, 3.19.4, 3.20.1 and 3.21.5 for protobuf-cpp, and versions prior to and including 3.16.1, 3.17.3, 3.18.2, 3.19.4, 3.20.1 and 4.21.5 for protobuf-python can lead to out of memory failures. A specially crafted message with multiple key-value per elements creates parsing issues, and can lead to a Denial of Service against services receiving unsanitized input. We recommend upgrading to versions 3.18.3, 3.19.5, 3.20.2, 3.21.6 for protobuf-cpp and 3.18.3, 3.19.5, 3.20.2, 4.21.6 for protobuf-python. Versions for 3.16 and 3.17 are no longer updated.
<p>Publish Date: 2022-09-22
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-1941>CVE-2022-1941</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cloud.google.com/support/bulletins#GCP-2022-019">https://cloud.google.com/support/bulletins#GCP-2022-019</a></p>
<p>Release Date: 2022-09-22</p>
<p>Fix Resolution: Google.Protobuf - 3.18.3,3.19.5,3.20.2,3.21.6;protobuf-python - 3.18.3,3.19.5,3.20.2,4.21.6</p>
</p>
<p></p>
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details> | non_test | protobuf manylinux whl vulnerabilities highest severity is vulnerable library protobuf manylinux whl protocol buffers library home page a href path to dependency file requirements txt path to vulnerable library requirements txt found in head commit a href vulnerabilities cve severity cvss dependency type fixed in protobuf version remediation available high protobuf manylinux whl direct google protobuf protobuf python details cve vulnerable library protobuf manylinux whl protocol buffers library home page a href path to dependency file requirements txt path to vulnerable library requirements txt dependency hierarchy x protobuf manylinux whl vulnerable library found in head commit a href found in base branch main vulnerability details a parsing vulnerability for the messageset type in the protocolbuffers versions prior to and including and for protobuf cpp and versions prior to and including and for protobuf python can lead to out of memory failures a specially crafted message with multiple key value per elements creates parsing issues and can lead to a denial of service against services receiving unsanitized input we recommend upgrading to versions for protobuf cpp and for protobuf python versions for and are no longer updated 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 google protobuf protobuf python step up your open source security game with mend | 0 |
173,537 | 21,176,822,256 | IssuesEvent | 2022-04-08 01:27:04 | directoryxx/Inventory-SISI | https://api.github.com/repos/directoryxx/Inventory-SISI | opened | CVE-2022-24785 (High) detected in moment-2.24.0.tgz | security vulnerability | ## CVE-2022-24785 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>moment-2.24.0.tgz</b></p></summary>
<p>Parse, validate, manipulate, and display dates</p>
<p>Library home page: <a href="https://registry.npmjs.org/moment/-/moment-2.24.0.tgz">https://registry.npmjs.org/moment/-/moment-2.24.0.tgz</a></p>
<p>Path to dependency file: /assets/adminlte/bower_components/bootstrap-daterangepicker/package.json</p>
<p>Path to vulnerable library: /assets/adminlte/bower_components/bootstrap-daterangepicker/node_modules/moment/package.json</p>
<p>
Dependency Hierarchy:
- :x: **moment-2.24.0.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Moment.js is a JavaScript date library for parsing, validating, manipulating, and formatting dates. A path traversal vulnerability impacts npm (server) users of Moment.js between versions 1.0.1 and 2.29.1, especially if a user-provided locale string is directly used to switch moment locale. This problem is patched in 2.29.2, and the patch can be applied to all affected versions. As a workaround, sanitize the user-provided locale name before passing it to Moment.js.
<p>Publish Date: 2022-04-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24785>CVE-2022-24785</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: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/moment/moment/security/advisories/GHSA-8hfj-j24r-96c4">https://github.com/moment/moment/security/advisories/GHSA-8hfj-j24r-96c4</a></p>
<p>Release Date: 2022-04-04</p>
<p>Fix Resolution: moment - 2.29.2,Moment.js - 2.29.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-2022-24785 (High) detected in moment-2.24.0.tgz - ## CVE-2022-24785 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>moment-2.24.0.tgz</b></p></summary>
<p>Parse, validate, manipulate, and display dates</p>
<p>Library home page: <a href="https://registry.npmjs.org/moment/-/moment-2.24.0.tgz">https://registry.npmjs.org/moment/-/moment-2.24.0.tgz</a></p>
<p>Path to dependency file: /assets/adminlte/bower_components/bootstrap-daterangepicker/package.json</p>
<p>Path to vulnerable library: /assets/adminlte/bower_components/bootstrap-daterangepicker/node_modules/moment/package.json</p>
<p>
Dependency Hierarchy:
- :x: **moment-2.24.0.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Moment.js is a JavaScript date library for parsing, validating, manipulating, and formatting dates. A path traversal vulnerability impacts npm (server) users of Moment.js between versions 1.0.1 and 2.29.1, especially if a user-provided locale string is directly used to switch moment locale. This problem is patched in 2.29.2, and the patch can be applied to all affected versions. As a workaround, sanitize the user-provided locale name before passing it to Moment.js.
<p>Publish Date: 2022-04-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24785>CVE-2022-24785</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: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/moment/moment/security/advisories/GHSA-8hfj-j24r-96c4">https://github.com/moment/moment/security/advisories/GHSA-8hfj-j24r-96c4</a></p>
<p>Release Date: 2022-04-04</p>
<p>Fix Resolution: moment - 2.29.2,Moment.js - 2.29.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 high detected in moment tgz cve high severity vulnerability vulnerable library moment tgz parse validate manipulate and display dates library home page a href path to dependency file assets adminlte bower components bootstrap daterangepicker package json path to vulnerable library assets adminlte bower components bootstrap daterangepicker node modules moment package json dependency hierarchy x moment tgz vulnerable library vulnerability details moment js is a javascript date library for parsing validating manipulating and formatting dates a path traversal vulnerability impacts npm server users of moment js between versions and especially if a user provided locale string is directly used to switch moment locale this problem is patched in and the patch can be applied to all affected versions as a workaround sanitize the user provided locale name before passing it to moment js 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 high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution moment moment js step up your open source security game with whitesource | 0 |
62,571 | 17,068,364,039 | IssuesEvent | 2021-07-07 10:08:52 | PowerDNS/pdns | https://api.github.com/repos/PowerDNS/pdns | closed | dnsdist: dnstap writes down wrong protocol | defect dnsdist | <!-- Hi! Thanks for filing an issue. It will be read with care by human beings. Can we ask you to please fill out this template and not simply demand new features or send in complaints? Thanks! -->
<!-- Also please search the existing issues (both open and closed) to see if your report might be duplicate -->
<!-- Please don't file an issue when you have a support question, send support questions to the mailinglist or ask them on IRC (https://www.powerdns.com/opensource.html) -->
<!-- Before filing your ticket, please read our 'out in the open' support policy at https://blog.powerdns.com/2016/01/18/open-source-support-out-in-the-open/ -->
<!-- Tell us what is issue is about -->
- Program: dnsdist <!-- delete the ones that do not apply -->
- Issue type: Bug report
### Short description
<!-- Explain in a few sentences what the issue/request is -->
Dnstap writes down wrong protocol (see https://mailman.powerdns.com/pipermail/dnsdist/2021-June/001090.html). When querying dnsdist with DoH (tcp), dnstap shows UDP.
### Environment
<!-- Tell us about the environment -->
- Operating system: ---
- Software version: 1.5.2
- Software source: self-compiled<!-- e.g. Operating system repository, PowerDNS repository, compiled yourself -->
### Steps to reproduce
<!-- Tell us step-by-step how the issue can be triggered. Please include your configuration files and any (Lua) scripts that are loaded. -->
1. Query dnsdist with DoH (dig @10.1.1.1 +https google.com)
### Expected behaviour
I expect to see TCP for the DoH query in the dnstap logfile.
<!-- What would you expect to happen when the reproduction steps are run -->
### Actual behaviour
Dnstap writes down the wrong protocol (UDP instead of TCP).
```
$ dnstap-read -p 2021-06-13-dnstap.fstrm
...
...
14-Jun-2021 14:19:30.058 CQ x.x.x.x:44749 -> y.y.y.y:443 UDP 51b google.com/IN/A
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1015
;; flags: rd ad; QUESTION: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 1f5e39ad95e85cd8
;; QUESTION SECTION:
;google.com. IN A
14-Jun-2021 14:19:30.059 CR x.x.x.x:44749 <- y.y.y.y:443 UDP 83b google.com/IN/A
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1015
;; flags: qr rd ra; QUESTION: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 1f5e39ad95e85cd80100000060c74952f681b113fec0d503
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 266 IN A 216.58.215.238
...
...
```
<!-- What did happen? Please (if possible) provide logs, output from `dig` and/or tcpdump/wireshark data -->
### Other information
<!-- if you already did more digging into the issue, please provide all the information you gathered -->
| 1.0 | dnsdist: dnstap writes down wrong protocol - <!-- Hi! Thanks for filing an issue. It will be read with care by human beings. Can we ask you to please fill out this template and not simply demand new features or send in complaints? Thanks! -->
<!-- Also please search the existing issues (both open and closed) to see if your report might be duplicate -->
<!-- Please don't file an issue when you have a support question, send support questions to the mailinglist or ask them on IRC (https://www.powerdns.com/opensource.html) -->
<!-- Before filing your ticket, please read our 'out in the open' support policy at https://blog.powerdns.com/2016/01/18/open-source-support-out-in-the-open/ -->
<!-- Tell us what is issue is about -->
- Program: dnsdist <!-- delete the ones that do not apply -->
- Issue type: Bug report
### Short description
<!-- Explain in a few sentences what the issue/request is -->
Dnstap writes down wrong protocol (see https://mailman.powerdns.com/pipermail/dnsdist/2021-June/001090.html). When querying dnsdist with DoH (tcp), dnstap shows UDP.
### Environment
<!-- Tell us about the environment -->
- Operating system: ---
- Software version: 1.5.2
- Software source: self-compiled<!-- e.g. Operating system repository, PowerDNS repository, compiled yourself -->
### Steps to reproduce
<!-- Tell us step-by-step how the issue can be triggered. Please include your configuration files and any (Lua) scripts that are loaded. -->
1. Query dnsdist with DoH (dig @10.1.1.1 +https google.com)
### Expected behaviour
I expect to see TCP for the DoH query in the dnstap logfile.
<!-- What would you expect to happen when the reproduction steps are run -->
### Actual behaviour
Dnstap writes down the wrong protocol (UDP instead of TCP).
```
$ dnstap-read -p 2021-06-13-dnstap.fstrm
...
...
14-Jun-2021 14:19:30.058 CQ x.x.x.x:44749 -> y.y.y.y:443 UDP 51b google.com/IN/A
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1015
;; flags: rd ad; QUESTION: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 1f5e39ad95e85cd8
;; QUESTION SECTION:
;google.com. IN A
14-Jun-2021 14:19:30.059 CR x.x.x.x:44749 <- y.y.y.y:443 UDP 83b google.com/IN/A
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1015
;; flags: qr rd ra; QUESTION: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 1f5e39ad95e85cd80100000060c74952f681b113fec0d503
;; QUESTION SECTION:
;google.com. IN A
;; ANSWER SECTION:
google.com. 266 IN A 216.58.215.238
...
...
```
<!-- What did happen? Please (if possible) provide logs, output from `dig` and/or tcpdump/wireshark data -->
### Other information
<!-- if you already did more digging into the issue, please provide all the information you gathered -->
| non_test | dnsdist dnstap writes down wrong protocol program dnsdist issue type bug report short description dnstap writes down wrong protocol see when querying dnsdist with doh tcp dnstap shows udp environment operating system software version software source self compiled steps to reproduce query dnsdist with doh dig https google com expected behaviour i expect to see tcp for the doh query in the dnstap logfile actual behaviour dnstap writes down the wrong protocol udp instead of tcp dnstap read p dnstap fstrm jun cq x x x x y y y y udp google com in a header opcode query status noerror id flags rd ad question answer authority additional opt pseudosection edns version flags udp cookie question section google com in a jun cr x x x x y y y y udp google com in a header opcode query status noerror id flags qr rd ra question answer authority additional opt pseudosection edns version flags udp cookie question section google com in a answer section google com in a other information | 0 |
307,232 | 26,519,455,897 | IssuesEvent | 2023-01-19 00:30:13 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | reopened | Fix jax_devicearray.test_jax_special_mod | JAX Frontend Sub Task Failing Test | | | |
|---|---|
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/3944623117/jobs/6750731420" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/3952846902/jobs/6768449116" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-failure-red></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/3952846902/jobs/6768447830" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/3952846902/jobs/6768459874" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
<details>
<summary>Not found</summary>
Not found
</details>
| 1.0 | Fix jax_devicearray.test_jax_special_mod - | | |
|---|---|
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/3944623117/jobs/6750731420" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/3952846902/jobs/6768449116" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-failure-red></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/3952846902/jobs/6768447830" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/3952846902/jobs/6768459874" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
<details>
<summary>Not found</summary>
Not found
</details>
| test | fix jax devicearray test jax special mod tensorflow img src torch img src numpy img src jax img src not found not found | 1 |
318,298 | 9,690,429,937 | IssuesEvent | 2019-05-24 08:37:24 | bitshares/bitshares-ui | https://api.github.com/repos/bitshares/bitshares-ui | closed | [1] Show reason why a proposal has failed to execute | [1b] User Story [3] Feature [4c] High Priority [5b] Small [7] Estimated | **Is your feature request related to a problem? Please describe.**
Now a failed proposal only shows a "failed" status but does not show the reason. With the latest core release, it's possible to get the reason: `proposal_object` now have a `fail_reason` field.
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
| 1.0 | [1] Show reason why a proposal has failed to execute - **Is your feature request related to a problem? Please describe.**
Now a failed proposal only shows a "failed" status but does not show the reason. With the latest core release, it's possible to get the reason: `proposal_object` now have a `fail_reason` field.
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
| non_test | show reason why a proposal has failed to execute is your feature request related to a problem please describe now a failed proposal only shows a failed status but does not show the reason with the latest core release it s possible to get the reason proposal object now have a fail reason field describe the solution you d like a clear and concise description of what you want to happen describe alternatives you ve considered a clear and concise description of any alternative solutions or features you ve considered additional context add any other context or screenshots about the feature request here | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.