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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
735,254 | 25,386,406,841 | IssuesEvent | 2022-11-21 22:19:42 | AirSkyBoat/AirSkyBoat | https://api.github.com/repos/AirSkyBoat/AirSkyBoat | closed | 🐛 [Exploit] Stackable synthesis support | bug System Crafting High-Priority High | **_I affirm:_**
- [x] I understand that if I do not agree to the following points by completing the checkboxes my issue will be ignored.
- [x] I have read and understood the [Contributing Guide](https://github.com/AirSkyBoat/AirSkyBoat/blob/staging/CONTRIBUTING.md) and the [Code of Conduct](https://github.com/AirSkyBoat/AirSkyBoat/blob/staging/CODE_OF_CONDUCT.md).
- [x] I have searched existing [issues](https://github.com/AirSkyBoat/AirSkyBoat/issues) to see if the issue has already been opened, and I have checked the commit log to see if the issue has been resolved since my server was last updated.
## Overview Of Issue
You can stack synth support by using a belt from one craft and talking to NPC for the other.
## If possible, provide steps to reproduce
Equip synth support belt
Use belt
Talk to Synth support NPC
Gain synth support from second craft
## If participating in HorizonXI Bugsquasher Campaign, please provide your character name used during the HorizonXI Beta:
Nishida
### If more than one player participated in discovering this bug, please also provide their beta character names:
<!-- Add other character names here -->
## Please provide any screenshots related to the reported bug by attaching them to this issue
| 1.0 | 🐛 [Exploit] Stackable synthesis support - **_I affirm:_**
- [x] I understand that if I do not agree to the following points by completing the checkboxes my issue will be ignored.
- [x] I have read and understood the [Contributing Guide](https://github.com/AirSkyBoat/AirSkyBoat/blob/staging/CONTRIBUTING.md) and the [Code of Conduct](https://github.com/AirSkyBoat/AirSkyBoat/blob/staging/CODE_OF_CONDUCT.md).
- [x] I have searched existing [issues](https://github.com/AirSkyBoat/AirSkyBoat/issues) to see if the issue has already been opened, and I have checked the commit log to see if the issue has been resolved since my server was last updated.
## Overview Of Issue
You can stack synth support by using a belt from one craft and talking to NPC for the other.
## If possible, provide steps to reproduce
Equip synth support belt
Use belt
Talk to Synth support NPC
Gain synth support from second craft
## If participating in HorizonXI Bugsquasher Campaign, please provide your character name used during the HorizonXI Beta:
Nishida
### If more than one player participated in discovering this bug, please also provide their beta character names:
<!-- Add other character names here -->
## Please provide any screenshots related to the reported bug by attaching them to this issue
| non_test | 🐛 stackable synthesis support i affirm i understand that if i do not agree to the following points by completing the checkboxes my issue will be ignored i have read and understood the and the i have searched existing to see if the issue has already been opened and i have checked the commit log to see if the issue has been resolved since my server was last updated overview of issue you can stack synth support by using a belt from one craft and talking to npc for the other if possible provide steps to reproduce equip synth support belt use belt talk to synth support npc gain synth support from second craft if participating in horizonxi bugsquasher campaign please provide your character name used during the horizonxi beta nishida if more than one player participated in discovering this bug please also provide their beta character names please provide any screenshots related to the reported bug by attaching them to this issue | 0 |
34,213 | 16,480,584,780 | IssuesEvent | 2021-05-24 11:01:24 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | kvcoord: txn heartbeater should stop monitoring record before sending EndTxn(commit=false) | A-kv-transactions C-performance | As seen in e.g. `TestRollbackSyncRangedIntentResolution`, when a large transaction is being rolled back and hits the synchronous intent resolution path because the async task pool is full
https://github.com/cockroachdb/cockroach/blob/a4b7a431093870393cac9f11287eaf282abdbd22/pkg/kv/kvserver/intentresolver/intent_resolver.go#L430-L435
then the txn heartbeater may notice the txn record has been aborted before the `EndTxn` call returns (because it's still cleaning up intents) and kick off its own intent resolution:
https://github.com/cockroachdb/cockroach/blob/5e7f8bd7a511f58204a1419452fd4d439f9ccec8/pkg/kv/kvclient/kvcoord/txn_interceptor_heartbeater.go#L331-L343
This may contend with the `EndTxn` resolution which may be doing ranged intent resolution via `ResumeSpans`, causing the client to wait longer than necessary. This was a contributing factor for #64092.
The heartbeater should probably stop monitoring the tnx record before sending the final `EndTxn` request, rather than waiting for the response. | True | kvcoord: txn heartbeater should stop monitoring record before sending EndTxn(commit=false) - As seen in e.g. `TestRollbackSyncRangedIntentResolution`, when a large transaction is being rolled back and hits the synchronous intent resolution path because the async task pool is full
https://github.com/cockroachdb/cockroach/blob/a4b7a431093870393cac9f11287eaf282abdbd22/pkg/kv/kvserver/intentresolver/intent_resolver.go#L430-L435
then the txn heartbeater may notice the txn record has been aborted before the `EndTxn` call returns (because it's still cleaning up intents) and kick off its own intent resolution:
https://github.com/cockroachdb/cockroach/blob/5e7f8bd7a511f58204a1419452fd4d439f9ccec8/pkg/kv/kvclient/kvcoord/txn_interceptor_heartbeater.go#L331-L343
This may contend with the `EndTxn` resolution which may be doing ranged intent resolution via `ResumeSpans`, causing the client to wait longer than necessary. This was a contributing factor for #64092.
The heartbeater should probably stop monitoring the tnx record before sending the final `EndTxn` request, rather than waiting for the response. | non_test | kvcoord txn heartbeater should stop monitoring record before sending endtxn commit false as seen in e g testrollbacksyncrangedintentresolution when a large transaction is being rolled back and hits the synchronous intent resolution path because the async task pool is full then the txn heartbeater may notice the txn record has been aborted before the endtxn call returns because it s still cleaning up intents and kick off its own intent resolution this may contend with the endtxn resolution which may be doing ranged intent resolution via resumespans causing the client to wait longer than necessary this was a contributing factor for the heartbeater should probably stop monitoring the tnx record before sending the final endtxn request rather than waiting for the response | 0 |
53,452 | 11,061,745,341 | IssuesEvent | 2019-12-11 08:00:19 | phetsims/molarity | https://api.github.com/repos/phetsims/molarity | closed | Store color strings on Solute.js instead of SoluteDescriber.getCurrentColor() | dev:code-review status:ready-for-review | From https://github.com/phetsims/molarity/issues/171
It feels much more robust to store color strings in the model, rather than have a switch case in a describer. I also feel the same way about the lowercase versions of the solute names.
This feels better to me for a few reasons:
* The switch case obfuscates the additional logic needed to support adding/removing Solutes. You may remove something from the model, and not know to change the switch case to keep things in sync
* This parallels the way everything else is created in this sim, in which MolarityModel.solutes is the kingpin, and everything get's its solute data from that list. It would be nice if the guts of where `MolarityModel.solutes` is declared was the only spot where solute-specific data was needed to be given.
| 1.0 | Store color strings on Solute.js instead of SoluteDescriber.getCurrentColor() - From https://github.com/phetsims/molarity/issues/171
It feels much more robust to store color strings in the model, rather than have a switch case in a describer. I also feel the same way about the lowercase versions of the solute names.
This feels better to me for a few reasons:
* The switch case obfuscates the additional logic needed to support adding/removing Solutes. You may remove something from the model, and not know to change the switch case to keep things in sync
* This parallels the way everything else is created in this sim, in which MolarityModel.solutes is the kingpin, and everything get's its solute data from that list. It would be nice if the guts of where `MolarityModel.solutes` is declared was the only spot where solute-specific data was needed to be given.
| non_test | store color strings on solute js instead of solutedescriber getcurrentcolor from it feels much more robust to store color strings in the model rather than have a switch case in a describer i also feel the same way about the lowercase versions of the solute names this feels better to me for a few reasons the switch case obfuscates the additional logic needed to support adding removing solutes you may remove something from the model and not know to change the switch case to keep things in sync this parallels the way everything else is created in this sim in which molaritymodel solutes is the kingpin and everything get s its solute data from that list it would be nice if the guts of where molaritymodel solutes is declared was the only spot where solute specific data was needed to be given | 0 |
257,353 | 22,156,177,947 | IssuesEvent | 2022-06-03 23:03:21 | apache/beam | https://api.github.com/repos/apache/beam | opened | Need ability to test Jenkins job changes without affecting live jobs | new feature P3 testing | Our Jenkins jobs are maintained in source code using the Groovy Job DSL, and kept up-to-date on our Apache Jenkins instance by regularly running the Seed Job.
Updating jobs is pretty easy by modifying the Groovy code, but there's no way to validate changes other than running the Seed Job and affecting the live job definitions. We should have some way to validate job changes outside of running the Seed job on production.
Imported from Jira [BEAM-6402](https://issues.apache.org/jira/browse/BEAM-6402). Original Jira may contain additional context.
Reported by: swegner. | 1.0 | Need ability to test Jenkins job changes without affecting live jobs - Our Jenkins jobs are maintained in source code using the Groovy Job DSL, and kept up-to-date on our Apache Jenkins instance by regularly running the Seed Job.
Updating jobs is pretty easy by modifying the Groovy code, but there's no way to validate changes other than running the Seed Job and affecting the live job definitions. We should have some way to validate job changes outside of running the Seed job on production.
Imported from Jira [BEAM-6402](https://issues.apache.org/jira/browse/BEAM-6402). Original Jira may contain additional context.
Reported by: swegner. | test | need ability to test jenkins job changes without affecting live jobs our jenkins jobs are maintained in source code using the groovy job dsl and kept up to date on our apache jenkins instance by regularly running the seed job updating jobs is pretty easy by modifying the groovy code but there s no way to validate changes other than running the seed job and affecting the live job definitions we should have some way to validate job changes outside of running the seed job on production imported from jira original jira may contain additional context reported by swegner | 1 |
556,866 | 16,493,250,719 | IssuesEvent | 2021-05-25 07:31:20 | ballerina-platform/ballerina-standard-library | https://api.github.com/repos/ballerina-platform/ballerina-standard-library | closed | Union type returns the results of all union type members | Priority/Blocker Team/PCP Type/Bug module/graphql | Query,
```graphql
{
search(status:OPEN) {
... on Trail {
name
trees
}
}
}
```
The result,
Here the third result should not be there. Because it is part of Lifts. Hence, trees end up being `null`.
```graphql
{
"data": {
"search": [
{
"name": "Blue Bird",
"trees": false
},
{
"name": "Blackhawk",
"trees": false
},
{
"name": "Astra Express",
"trees": null
}
]
}
}
```
Implementation,
```ballerina
resource function get search (ds:Status status) returns SearchResult[] {
ds:TrailRecord[] trails = from var trail in ds:trailTable where trail.status == status select trail;
SearchResult[] searchResults = trails.map(function (ds:TrailRecord trail) returns Trail => new Trail(trail));
ds:LiftRecord[] lifts = from var lift in ds:liftTable where lift.status == status select lift;
lifts.forEach(function (ds:LiftRecord lift) returns () => searchResults.push(new Lift(lift)));
return searchResults;
}
```
| 1.0 | Union type returns the results of all union type members - Query,
```graphql
{
search(status:OPEN) {
... on Trail {
name
trees
}
}
}
```
The result,
Here the third result should not be there. Because it is part of Lifts. Hence, trees end up being `null`.
```graphql
{
"data": {
"search": [
{
"name": "Blue Bird",
"trees": false
},
{
"name": "Blackhawk",
"trees": false
},
{
"name": "Astra Express",
"trees": null
}
]
}
}
```
Implementation,
```ballerina
resource function get search (ds:Status status) returns SearchResult[] {
ds:TrailRecord[] trails = from var trail in ds:trailTable where trail.status == status select trail;
SearchResult[] searchResults = trails.map(function (ds:TrailRecord trail) returns Trail => new Trail(trail));
ds:LiftRecord[] lifts = from var lift in ds:liftTable where lift.status == status select lift;
lifts.forEach(function (ds:LiftRecord lift) returns () => searchResults.push(new Lift(lift)));
return searchResults;
}
```
| non_test | union type returns the results of all union type members query graphql search status open on trail name trees the result here the third result should not be there because it is part of lifts hence trees end up being null graphql data search name blue bird trees false name blackhawk trees false name astra express trees null implementation ballerina resource function get search ds status status returns searchresult ds trailrecord trails from var trail in ds trailtable where trail status status select trail searchresult searchresults trails map function ds trailrecord trail returns trail new trail trail ds liftrecord lifts from var lift in ds lifttable where lift status status select lift lifts foreach function ds liftrecord lift returns searchresults push new lift lift return searchresults | 0 |
537,103 | 15,723,073,439 | IssuesEvent | 2021-03-29 06:56:42 | AY2021S2-CS2103T-T11-1/tp | https://api.github.com/repos/AY2021S2-CS2103T-T11-1/tp | closed | Add RecurringSession Feature | priority.High | RecurringSession that extends Session.
With methods to be used by reminder and fee calculation | 1.0 | Add RecurringSession Feature - RecurringSession that extends Session.
With methods to be used by reminder and fee calculation | non_test | add recurringsession feature recurringsession that extends session with methods to be used by reminder and fee calculation | 0 |
136,746 | 11,082,183,228 | IssuesEvent | 2019-12-13 11:28:43 | dzhw/SLC-IntEr | https://api.github.com/repos/dzhw/SLC-IntEr | closed | Layout mobile Ansicht st**09 | Modul: Episoden Modul: Studium layout mittlere Priorität testing | Nach dem Umbau der Frage ist hier die Darstellung im Portrait noch problematisch:
bitte anpassen für:
staa09 stab09 stac09 stad09 stae09
stba09 stbb09 stbc09 stbd09
stca09 stcb09 stcc09
stda09 stdb09
stea09
und
stu_95 | 1.0 | Layout mobile Ansicht st**09 - Nach dem Umbau der Frage ist hier die Darstellung im Portrait noch problematisch:
bitte anpassen für:
staa09 stab09 stac09 stad09 stae09
stba09 stbb09 stbc09 stbd09
stca09 stcb09 stcc09
stda09 stdb09
stea09
und
stu_95 | test | layout mobile ansicht st nach dem umbau der frage ist hier die darstellung im portrait noch problematisch bitte anpassen für und stu | 1 |
172,737 | 13,338,755,120 | IssuesEvent | 2020-08-28 11:39:20 | tikv/tikv | https://api.github.com/repos/tikv/tikv | closed | Worker not correctly released in a lot of tests | component/test-bench type/bug | ## Feature Request
Worker.stop() not called. | 1.0 | Worker not correctly released in a lot of tests - ## Feature Request
Worker.stop() not called. | test | worker not correctly released in a lot of tests feature request worker stop not called | 1 |
93,444 | 8,416,468,268 | IssuesEvent | 2018-10-14 02:41:07 | brave/brave-browser | https://api.github.com/repos/brave/brave-browser | closed | Autocomplete does not default to brave://xyz as URL | QA/Test-Plan-Specified QA/Yes feature/url-bar | Whilst brave://xyz URLs work (they redirect to chrome://xyz), the default action in the LocationBar on typing such a url results in a search query.
A scheme classifier was implemented in https://github.com/brave/brave-core/pull/164 which specifies brave:// as a URL, but it is not loaded as part of the actual chrome omnibox UI.
Test plan:
1. Type brave://settings in LocationBar
2. Press enter
Observed: Sent to a search URL with "brave://settings" as query
Expected: Sent to `brave://settings` URL (right now this displays `chrome://settings` which is ok, but will change as of https://github.com/brave/brave-browser/issues/1458)
| 1.0 | Autocomplete does not default to brave://xyz as URL - Whilst brave://xyz URLs work (they redirect to chrome://xyz), the default action in the LocationBar on typing such a url results in a search query.
A scheme classifier was implemented in https://github.com/brave/brave-core/pull/164 which specifies brave:// as a URL, but it is not loaded as part of the actual chrome omnibox UI.
Test plan:
1. Type brave://settings in LocationBar
2. Press enter
Observed: Sent to a search URL with "brave://settings" as query
Expected: Sent to `brave://settings` URL (right now this displays `chrome://settings` which is ok, but will change as of https://github.com/brave/brave-browser/issues/1458)
| test | autocomplete does not default to brave xyz as url whilst brave xyz urls work they redirect to chrome xyz the default action in the locationbar on typing such a url results in a search query a scheme classifier was implemented in which specifies brave as a url but it is not loaded as part of the actual chrome omnibox ui test plan type brave settings in locationbar press enter observed sent to a search url with brave settings as query expected sent to brave settings url right now this displays chrome settings which is ok but will change as of | 1 |
189,914 | 14,528,201,718 | IssuesEvent | 2020-12-14 16:15:13 | dwp/design-system | https://api.github.com/repos/dwp/design-system | opened | Selenium Accessibility Tests | a11y development test | **Is your feature request related to a problem? Please describe.**
We need to automate a11y testing for common problems when developing/release. | 1.0 | Selenium Accessibility Tests - **Is your feature request related to a problem? Please describe.**
We need to automate a11y testing for common problems when developing/release. | test | selenium accessibility tests is your feature request related to a problem please describe we need to automate testing for common problems when developing release | 1 |
360,291 | 10,686,562,261 | IssuesEvent | 2019-10-22 14:38:08 | City-of-Helsinki/kerrokantasi-ui | https://api.github.com/repos/City-of-Helsinki/kerrokantasi-ui | closed | Fix comment image upload | 2019 priority bug | Currently, images cannot be uploaded with a comment, due to `e.forEach is not a function` at https://github.com/City-of-Helsinki/kerrokantasi-ui/blob/master/src/components/BaseCommentForm.js row 179.
This bug is caused by recent changes, since it started appearing in sentry two months ago. | 1.0 | Fix comment image upload - Currently, images cannot be uploaded with a comment, due to `e.forEach is not a function` at https://github.com/City-of-Helsinki/kerrokantasi-ui/blob/master/src/components/BaseCommentForm.js row 179.
This bug is caused by recent changes, since it started appearing in sentry two months ago. | non_test | fix comment image upload currently images cannot be uploaded with a comment due to e foreach is not a function at row this bug is caused by recent changes since it started appearing in sentry two months ago | 0 |
235,222 | 19,308,985,812 | IssuesEvent | 2021-12-13 14:29:17 | eclipse/che | https://api.github.com/repos/eclipse/che | closed | Figure out reasons and fix failing of the HappyPath tests for the CHE dashboard and DWO projects | kind/task severity/P1 e2e-test/failure area/qe | ### Is your task related to a problem? Please describe
After resolving problems with cloud providers for PROW CI:
We get a strange error when we run HappyPath test. For instance: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/23945/rehearse-23945-pull-ci-eclipse-che-che-dashboard-main-v8-dashboard-happy-path/1463444053726072832.
We have 2 problems:
* Sometimes the **htpswd** provider does not appear in the IDP table
* When **htpswd** provider and test user create successfully and we login in as test user using **oc** client - we get strange error on the Login page like **Error creation user**
### Describe the solution you'd like
I can try to reproduce this problem on a similar infra (cluster bot ) and figure out what it is more deeply.
### Describe alternatives you've considered
_No response_
### Additional context
_No response_ | 1.0 | Figure out reasons and fix failing of the HappyPath tests for the CHE dashboard and DWO projects - ### Is your task related to a problem? Please describe
After resolving problems with cloud providers for PROW CI:
We get a strange error when we run HappyPath test. For instance: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/23945/rehearse-23945-pull-ci-eclipse-che-che-dashboard-main-v8-dashboard-happy-path/1463444053726072832.
We have 2 problems:
* Sometimes the **htpswd** provider does not appear in the IDP table
* When **htpswd** provider and test user create successfully and we login in as test user using **oc** client - we get strange error on the Login page like **Error creation user**
### Describe the solution you'd like
I can try to reproduce this problem on a similar infra (cluster bot ) and figure out what it is more deeply.
### Describe alternatives you've considered
_No response_
### Additional context
_No response_ | test | figure out reasons and fix failing of the happypath tests for the che dashboard and dwo projects is your task related to a problem please describe after resolving problems with cloud providers for prow ci we get a strange error when we run happypath test for instance we have problems sometimes the htpswd provider does not appear in the idp table when htpswd provider and test user create successfully and we login in as test user using oc client we get strange error on the login page like error creation user describe the solution you d like i can try to reproduce this problem on a similar infra cluster bot and figure out what it is more deeply describe alternatives you ve considered no response additional context no response | 1 |
293,733 | 25,318,975,725 | IssuesEvent | 2022-11-18 01:01:58 | dotnet/maui | https://api.github.com/repos/dotnet/maui | closed | Build error for Maui App icon svg format is not supported in iOS plaftform | t/bug area/single project ☝️ platform/iOS 🍎 s/verified s/try-latest-version | ### Description
I see a Build error when trying to use a maui app icon in svg format , attaching the icon which i am using , iOS build fails with this error
**actool error : The stickers icon set or app icon set named "appicon" did not have any applicable content**
Svg content :
```xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg xmlns="http://www.w3.org/2000/svg" version="1.1" width="732px" height="309px" style="shape-rendering:geometricPrecision; text-rendering:geometricPrecision; image-rendering:optimizeQuality; fill-rule:evenodd; clip-rule:evenodd" xmlns:xlink="http://www.w3.org/1999/xlink">
<g><path style="opacity:0.986" fill="#05b442" d="M 442.5,82.5 C 442.672,81.5084 442.338,80.8417 441.5,80.5C 440.978,75.0377 439.311,70.5377 436.5,67C 434.114,55.0325 427.114,46.3659 415.5,41C 405.984,37.6255 396.984,37.1255 388.5,39.5C 375.478,40.7902 365.978,47.4568 360,59.5C 355.693,68.6986 353.026,78.3653 352,88.5C 351.173,102.852 350.173,117.185 349,131.5C 344.439,160.345 328.773,179.678 302,189.5C 291.762,194.358 285.928,190.858 284.5,179C 285.203,171.486 286.036,163.653 287,155.5C 291.882,152.975 296.715,150.308 301.5,147.5C 304.586,144.245 307.086,140.578 309,136.5C 311.219,129.588 312.719,122.754 313.5,116C 313.497,107.698 313.497,99.3647 313.5,91C 314.632,65.9026 323.632,43.4026 340.5,23.5C 361.565,3.09454 386.565,-4.07213 415.5,2C 445.262,9.09367 464.762,27.2603 474,56.5C 475.98,63.0871 477.647,69.7538 479,76.5C 480.871,93.454 482.204,110.454 483,127.5C 485.256,140.876 492.756,149.71 505.5,154C 506.893,155.171 507.727,156.671 508,158.5C 508.667,167.5 508.667,176.5 508,185.5C 504.93,191.856 500.263,193.189 494,189.5C 479.163,185.04 466.663,176.04 456.5,162.5C 446.824,144.034 442.824,125.034 444.5,105.5C 442.948,98.5843 441.948,91.751 441.5,85C 442.252,84.3292 442.586,83.4959 442.5,82.5 Z"/></g>
<g><path style="opacity:0.991" fill="#00559b" d="M 594.5,2.5 C 613.968,0.904491 632.968,3.07116 651.5,9C 674.169,19.3053 686.503,36.9719 688.5,62C 688.359,63.9552 687.526,65.4552 686,66.5C 672.572,66.0401 659.072,65.8734 645.5,66C 642.422,45.645 630.255,36.145 609,37.5C 596.622,36.9473 586.289,40.614 578,48.5C 573.464,58.2759 575.964,65.7759 585.5,71C 589.419,72.8618 593.419,74.5285 597.5,76C 616.357,80.7139 635.024,86.0472 653.5,92C 683.447,104.049 696.947,126.215 694,158.5C 687.706,189.458 668.873,207.624 637.5,213C 630.921,213.607 624.421,214.44 618,215.5C 611.8,214.569 605.134,214.569 598,215.5C 597.5,215 597,214.5 596.5,214C 554.483,209.149 531.483,185.649 527.5,143.5C 541.155,142.001 554.821,140.834 568.5,140C 575.053,170.166 593.719,182.5 624.5,177C 644.362,173.516 652.862,162.016 650,142.5C 645.908,136.755 640.408,132.922 633.5,131C 617.878,126.511 602.211,122.178 586.5,118C 569.692,113.349 555.525,104.515 544,91.5C 530.909,70.2782 531.242,48.9449 545,27.5C 558.216,12.6419 574.716,4.30854 594.5,2.5 Z"/></g>
<g><path style="opacity:0.991" fill="#00559b" d="M 33.5,15.5 C 47.4123,15.1767 61.2456,15.5101 75,16.5C 84.3319,59.1616 93.6652,101.828 103,144.5C 114.956,101.679 126.456,58.6787 137.5,15.5C 153.744,15.1752 169.911,15.5086 186,16.5C 196.692,59.9344 207.692,103.268 219,146.5C 228.539,103.138 238.206,59.8048 248,16.5C 261.421,15.5103 274.921,15.177 288.5,15.5C 273.526,80.2621 258.026,144.929 242,209.5C 234.743,210.159 227.41,210.492 220,210.5C 212.431,210.481 205.097,209.815 198,208.5C 185.739,162.14 173.406,115.473 161,68.5C 148.652,115.561 136.152,162.561 123.5,209.5C 108.833,210.833 94.1667,210.833 79.5,209.5C 63.8701,145.446 48.5368,80.7792 33.5,15.5 Z"/></g>
<g><path style="opacity:0.09" fill="#0b749c" d="M 441.5,80.5 C 442.338,80.8417 442.672,81.5084 442.5,82.5C 440.895,81.9941 440.561,81.3274 441.5,80.5 Z"/></g>
<g><path style="opacity:0.965" fill="#04b441" d="M 360.5,189.5 C 385.169,189.333 409.836,189.5 434.5,190C 436.594,191.255 437.594,193.088 437.5,195.5C 433.819,214.014 422.819,225.514 404.5,230C 380.961,231.986 365.461,221.82 358,199.5C 356.861,195.579 357.695,192.246 360.5,189.5 Z"/></g>
<g><path style="opacity:0.897" fill="#0469b6" d="M 131.5,254.5 C 136.214,254.353 140.881,254.686 145.5,255.5C 145.82,258.898 145.487,262.232 144.5,265.5C 142.154,258.437 137.488,256.27 130.5,259C 127.277,262.112 126.777,265.612 129,269.5C 134.301,273.8 139.301,278.466 144,283.5C 149.636,297.23 145.136,305.23 130.5,307.5C 127.157,306.974 123.99,305.974 121,304.5C 120.087,300.638 120.42,296.972 122,293.5C 123.822,302.494 128.989,305.327 137.5,302C 142.644,297.392 142.81,292.559 138,287.5C 131.874,283.047 126.874,277.713 123,271.5C 120.588,262.99 123.421,257.323 131.5,254.5 Z"/></g>
<g><path style="opacity:0.897" fill="#0269b7" d="M 155.5,254.5 C 168.846,255.797 182.179,255.797 195.5,254.5C 196.833,257.833 196.833,261.167 195.5,264.5C 194.937,262.291 193.604,260.791 191.5,260C 187.179,259.501 182.846,259.334 178.5,259.5C 178.333,272.837 178.5,286.171 179,299.5C 179.425,303.306 181.592,305.14 185.5,305C 182.522,306.125 179.355,306.625 176,306.5C 173.167,306.167 170.333,305.833 167.5,305.5C 170.229,304.938 171.729,303.272 172,300.5C 172.5,286.837 172.667,273.171 172.5,259.5C 167.821,259.334 163.155,259.501 158.5,260C 156.824,261.177 155.491,262.677 154.5,264.5C 154.167,263.833 153.833,263.167 153.5,262.5C 154.171,259.815 154.838,257.148 155.5,254.5 Z"/></g>
<g><path style="opacity:0.909" fill="#0469b5" d="M 240.5,254.5 C 242.124,254.36 243.29,255.027 244,256.5C 249.413,271.739 255.413,286.739 262,301.5C 263.925,303.213 266.092,304.547 268.5,305.5C 263.416,306.89 258.416,306.723 253.5,305C 254.022,304.439 254.355,303.772 254.5,303C 252.916,297.667 250.916,292.5 248.5,287.5C 243.615,286.198 238.782,286.198 234,287.5C 232.399,292.136 230.899,296.802 229.5,301.5C 229.728,303.397 230.728,304.73 232.5,305.5C 231.372,306.262 230.205,306.929 229,307.5C 224.735,306.965 220.568,306.131 216.5,305C 221.849,304.653 225.016,301.819 226,296.5C 231.342,282.641 236.175,268.641 240.5,254.5 Z M 240.5,266.5 C 242.928,271.868 245.261,277.368 247.5,283C 243.459,283.827 239.459,283.66 235.5,282.5C 237.575,277.276 239.242,271.942 240.5,266.5 Z"/></g>
<g><path style="opacity:0.897" fill="#0269b7" d="M 394.5,254.5 C 407.846,255.797 421.179,255.797 434.5,254.5C 435.833,257.833 435.833,261.167 434.5,264.5C 433.937,262.291 432.604,260.791 430.5,260C 426.179,259.501 421.846,259.334 417.5,259.5C 417.333,272.837 417.5,286.171 418,299.5C 418.425,303.306 420.592,305.14 424.5,305C 421.522,306.125 418.355,306.625 415,306.5C 412.167,306.167 409.333,305.833 406.5,305.5C 409.229,304.938 410.729,303.272 411,300.5C 411.5,286.837 411.667,273.171 411.5,259.5C 406.821,259.334 402.155,259.501 397.5,260C 395.824,261.177 394.491,262.677 393.5,264.5C 393.167,263.833 392.833,263.167 392.5,262.5C 393.171,259.815 393.838,257.148 394.5,254.5 Z"/></g>
<g><path style="opacity:0.897" fill="#0469b6" d="M 475.5,254.5 C 480.214,254.353 484.881,254.686 489.5,255.5C 489.82,258.898 489.487,262.232 488.5,265.5C 486.154,258.437 481.488,256.27 474.5,259C 471.277,262.112 470.777,265.612 473,269.5C 478.301,273.8 483.301,278.466 488,283.5C 493.636,297.23 489.136,305.23 474.5,307.5C 471.157,306.974 467.99,305.974 465,304.5C 464.087,300.638 464.42,296.972 466,293.5C 467.822,302.494 472.989,305.327 481.5,302C 486.644,297.392 486.81,292.559 482,287.5C 475.874,283.047 470.874,277.713 467,271.5C 464.588,262.99 467.421,257.323 475.5,254.5 Z"/></g>
<g><path style="opacity:0.897" fill="#0469b6" d="M 556.5,254.5 C 561.214,254.353 565.881,254.686 570.5,255.5C 570.82,258.898 570.487,262.232 569.5,265.5C 567.154,258.437 562.488,256.27 555.5,259C 552.277,262.112 551.777,265.612 554,269.5C 559.301,273.8 564.301,278.466 569,283.5C 574.636,297.23 570.136,305.23 555.5,307.5C 552.157,306.974 548.99,305.974 546,304.5C 545.087,300.638 545.42,296.972 547,293.5C 548.822,302.494 553.989,305.327 562.5,302C 567.644,297.392 567.81,292.559 563,287.5C 556.874,283.047 551.874,277.713 548,271.5C 545.588,262.99 548.421,257.323 556.5,254.5 Z"/></g>
<g><path style="opacity:0.897" fill="#0269b7" d="M 579.5,254.5 C 592.846,255.797 606.179,255.797 619.5,254.5C 620.833,257.833 620.833,261.167 619.5,264.5C 618.937,262.291 617.604,260.791 615.5,260C 611.179,259.501 606.846,259.334 602.5,259.5C 602.333,272.837 602.5,286.171 603,299.5C 603.425,303.306 605.592,305.14 609.5,305C 606.522,306.125 603.355,306.625 600,306.5C 597.167,306.167 594.333,305.833 591.5,305.5C 594.229,304.938 595.729,303.272 596,300.5C 596.5,286.837 596.667,273.171 596.5,259.5C 591.821,259.334 587.155,259.501 582.5,260C 580.824,261.177 579.491,262.677 578.5,264.5C 578.167,263.833 577.833,263.167 577.5,262.5C 578.171,259.815 578.838,257.148 579.5,254.5 Z"/></g>
<g><path style="opacity:0.912" fill="#0369b6" d="M 731.5,304.5 C 731.5,305.167 731.5,305.833 731.5,306.5C 726.819,306.331 722.152,305.998 717.5,305.5C 717.328,293.782 716.162,282.116 714,270.5C 708.661,282.511 702.828,294.178 696.5,305.5C 694.768,303.717 693.268,301.717 692,299.5C 687.711,289.956 683.044,280.623 678,271.5C 677.194,280.67 676.361,289.836 675.5,299C 675.104,302.767 676.77,304.767 680.5,305C 678.03,306.114 675.364,306.614 672.5,306.5C 670.167,306.167 667.833,305.833 665.5,305.5C 667.193,304.772 668.693,303.772 670,302.5C 670.834,296.331 671.667,290.165 672.5,284C 672.415,282.893 672.081,281.893 671.5,281C 673.274,272.223 674.941,263.389 676.5,254.5C 683.94,267.958 691.107,281.625 698,295.5C 701.947,287.274 705.614,278.941 709,270.5C 711.93,264.966 715.096,259.633 718.5,254.5C 720.734,269.101 722.567,283.768 724,298.5C 724.863,302.518 727.363,304.518 731.5,304.5 Z"/></g>
<g><path style="opacity:0.904" fill="#0469b6" d="M 1.5,255.5 C 7.50924,255.334 13.5092,255.501 19.5,256C 18.4366,257.188 17.1033,257.688 15.5,257.5C 17.5666,270.099 20.7333,282.433 25,294.5C 26.9754,288.904 29.142,283.404 31.5,278C 31.1667,277.667 30.8333,277.333 30.5,277C 33.7485,269.735 37.0819,262.569 40.5,255.5C 45.815,268.273 50.6483,281.273 55,294.5C 58.4216,284.582 61.7549,274.249 65,263.5C 65.6667,261.5 65.6667,259.5 65,257.5C 63.7567,258.336 62.5901,258.003 61.5,256.5C 66.5,255.167 71.5,255.167 76.5,256.5C 72.9065,256.926 70.7398,258.926 70,262.5C 65.4651,275.771 61.1318,289.105 57,302.5C 56.2515,304.332 55.2515,305.999 54,307.5C 48.6171,294.69 43.6171,281.69 39,268.5C 34.2352,281.809 28.9019,294.809 23,307.5C 21.3859,303.828 19.5526,300.328 17.5,297C 17.9574,296.586 18.2907,296.086 18.5,295.5C 15.103,284.142 11.603,272.808 8,261.5C 6.32165,258.77 4.15498,256.77 1.5,255.5 Z"/></g>
<g><path style="opacity:0.911" fill="#0368b6" d="M 107.5,254.5 C 108.736,257.818 108.403,261.151 106.5,264.5C 105.756,263.009 105.09,261.509 104.5,260C 100.582,258.844 96.5817,258.344 92.5,258.5C 92.5,264.833 92.5,271.167 92.5,277.5C 96.5138,277.666 100.514,277.499 104.5,277C 106.382,274.935 107.382,275.435 107.5,278.5C 107.064,281.179 106.564,283.845 106,286.5C 104.98,285.109 104.147,283.609 103.5,282C 99.9399,280.763 96.2733,280.263 92.5,280.5C 92.3337,287.175 92.5004,293.842 93,300.5C 93.5,301 94,301.5 94.5,302C 98.1667,302.667 101.833,302.667 105.5,302C 106.956,300.255 108.289,298.422 109.5,296.5C 110.52,300.562 109.687,304.228 107,307.5C 98.3882,306.535 89.8882,305.869 81.5,305.5C 82.7598,304.618 83.9264,303.618 85,302.5C 85.6667,287.833 85.6667,273.167 85,258.5C 83.4905,257.91 81.9905,257.244 80.5,256.5C 89.6577,255.833 98.6577,255.167 107.5,254.5 Z"/></g>
<g><path style="opacity:0.919" fill="#0268b6" d="M 271.5,255.5 C 277.206,255.171 282.872,255.505 288.5,256.5C 287.009,257.244 285.509,257.91 284,258.5C 283.333,272.167 283.333,285.833 284,299.5C 284.374,300.416 284.874,301.25 285.5,302C 289.833,302.667 294.167,302.667 298.5,302C 299.956,300.255 301.289,298.422 302.5,296.5C 303.296,299.717 302.963,302.883 301.5,306C 291.633,306.564 281.967,306.398 272.5,305.5C 273.76,304.618 274.926,303.618 276,302.5C 276.667,287.833 276.667,273.167 276,258.5C 273.974,258.085 272.474,257.085 271.5,255.5 Z"/></g>
<g><path style="opacity:0.911" fill="#0368b6" d="M 337.5,254.5 C 338.736,257.818 338.403,261.151 336.5,264.5C 335.756,263.009 335.09,261.509 334.5,260C 330.582,258.844 326.582,258.344 322.5,258.5C 322.5,264.833 322.5,271.167 322.5,277.5C 326.514,277.666 330.514,277.499 334.5,277C 336.382,274.935 337.382,275.435 337.5,278.5C 337.064,281.179 336.564,283.845 336,286.5C 334.98,285.109 334.147,283.609 333.5,282C 329.94,280.763 326.273,280.263 322.5,280.5C 322.334,287.175 322.5,293.842 323,300.5C 323.5,301 324,301.5 324.5,302C 328.167,302.667 331.833,302.667 335.5,302C 336.956,300.255 338.289,298.422 339.5,296.5C 340.52,300.562 339.687,304.228 337,307.5C 328.388,306.535 319.888,305.869 311.5,305.5C 312.76,304.618 313.926,303.618 315,302.5C 315.667,287.833 315.667,273.167 315,258.5C 313.491,257.91 311.991,257.244 310.5,256.5C 319.658,255.833 328.658,255.167 337.5,254.5 Z"/></g>
<g><path style="opacity:0.934" fill="#0569b5" d="M 351.5,255.5 C 359.174,255.334 366.841,255.5 374.5,256C 383.231,258.62 386.398,264.453 384,273.5C 382.224,276.941 380.057,280.108 377.5,283C 382.358,289.704 387.691,296.037 393.5,302C 396.218,303.072 398.885,304.238 401.5,305.5C 396.799,306.731 392.132,306.564 387.5,305C 381.82,298.985 376.487,292.651 371.5,286C 368.883,285.178 366.216,284.678 363.5,284.5C 363.334,290.509 363.501,296.509 364,302.5C 365.6,303.866 367.433,304.866 369.5,305.5C 363.681,306.207 358.014,306.207 352.5,305.5C 353.76,304.618 354.926,303.618 356,302.5C 356.667,287.833 356.667,273.167 356,258.5C 353.974,258.085 352.474,257.085 351.5,255.5 Z M 363.5,258.5 C 376.291,258.713 380.791,265.046 377,277.5C 375.688,280.581 373.355,282.248 370,282.5C 367.959,281.577 365.792,281.244 363.5,281.5C 363.5,273.833 363.5,266.167 363.5,258.5 Z"/></g>
<g><path style="opacity:0.905" fill="#0369b5" d="M 494.5,255.5 C 499.214,255.173 503.88,255.507 508.5,256.5C 507.975,257.192 507.308,257.692 506.5,258C 510.456,265.416 514.79,272.583 519.5,279.5C 522.791,273.376 526.291,267.376 530,261.5C 530.651,259.765 530.485,258.098 529.5,256.5C 533.833,255.167 538.167,255.167 542.5,256.5C 539.345,257.15 536.845,258.817 535,261.5C 529.893,268.712 525.56,276.379 522,284.5C 521.333,290.167 521.333,295.833 522,301.5C 523.362,303.436 525.195,304.769 527.5,305.5C 521.833,306.833 516.167,306.833 510.5,305.5C 511.628,304.738 512.795,304.071 514,303.5C 516.266,295.703 515.933,288.036 513,280.5C 510.083,276.334 507.416,272.001 505,267.5C 502.291,262.636 498.791,258.636 494.5,255.5 Z"/></g>
<g><path style="opacity:0.911" fill="#0368b6" d="M 655.5,254.5 C 656.736,257.818 656.403,261.151 654.5,264.5C 653.756,263.009 653.09,261.509 652.5,260C 648.582,258.844 644.582,258.344 640.5,258.5C 640.5,264.833 640.5,271.167 640.5,277.5C 644.514,277.666 648.514,277.499 652.5,277C 654.382,274.935 655.382,275.435 655.5,278.5C 655.064,281.179 654.564,283.845 654,286.5C 652.98,285.109 652.147,283.609 651.5,282C 647.94,280.763 644.273,280.263 640.5,280.5C 640.334,287.175 640.5,293.842 641,300.5C 641.5,301 642,301.5 642.5,302C 646.167,302.667 649.833,302.667 653.5,302C 654.956,300.255 656.289,298.422 657.5,296.5C 658.52,300.562 657.687,304.228 655,307.5C 646.388,306.535 637.888,305.869 629.5,305.5C 630.76,304.618 631.926,303.618 633,302.5C 633.667,287.833 633.667,273.167 633,258.5C 631.491,257.91 629.991,257.244 628.5,256.5C 637.658,255.833 646.658,255.167 655.5,254.5 Z"/></g>
</svg>
```
### Steps to Reproduce
Create a Maui app , change the appicon to the svg image given , try to build the solution you will get this error
### Version with bug
Preview 13 (current)
### Last version that worked well
Unknown/Other
### Affected platforms
iOS
### Affected platform versions
iOS 15.2
### Did you find any workaround?
_No response_
### Relevant log output
```shell
/usr/local/share/dotnet/packs/Microsoft.iOS.Sdk/15.2.301-preview.13.7/tools/msbuild/iOS/Xamarin.Shared.targets(808,3): error : /usr/bin/xcrun exited with code 1 [/Users/rockclane/MyMauiApp/MyMauiApp.csproj]
/usr/local/share/dotnet/packs/Microsoft.iOS.Sdk/15.2.301-preview.13.7/tools/msbuild/iOS/Xamarin.Shared.targets(808,3): error : [/Users/rockclane/MyMauiApp/MyMauiApp.csproj]
/usr/local/share/dotnet/packs/Microsoft.iOS.Sdk/15.2.301-preview.13.7/tools/msbuild/iOS/Xamarin.Shared.targets(808,3): error : actool exited with code 1 [/Users/rockclane/MyMauiApp/MyMauiApp.csproj]
/usr/local/share/dotnet/packs/Microsoft.iOS.Sdk/15.2.301-preview.13.7/tools/msbuild/iOS/Xamarin.Shared.targets(808,3): error : [/Users/rockclane/MyMauiApp/MyMauiApp.csproj]
/Users/rockclane/MyMauiApp/obj/Debug/net6.0-ios/iossimulator-x64/actool/cloned-assets/Assets.xcassets : actool error : The stickers icon set or app icon set named "appicon" did not have any applicable content. [/Users/rockclane/MyMauiApp/MyMauiApp.csproj]
```
| 1.0 | Build error for Maui App icon svg format is not supported in iOS plaftform - ### Description
I see a Build error when trying to use a maui app icon in svg format , attaching the icon which i am using , iOS build fails with this error
**actool error : The stickers icon set or app icon set named "appicon" did not have any applicable content**
Svg content :
```xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg xmlns="http://www.w3.org/2000/svg" version="1.1" width="732px" height="309px" style="shape-rendering:geometricPrecision; text-rendering:geometricPrecision; image-rendering:optimizeQuality; fill-rule:evenodd; clip-rule:evenodd" xmlns:xlink="http://www.w3.org/1999/xlink">
<g><path style="opacity:0.986" fill="#05b442" d="M 442.5,82.5 C 442.672,81.5084 442.338,80.8417 441.5,80.5C 440.978,75.0377 439.311,70.5377 436.5,67C 434.114,55.0325 427.114,46.3659 415.5,41C 405.984,37.6255 396.984,37.1255 388.5,39.5C 375.478,40.7902 365.978,47.4568 360,59.5C 355.693,68.6986 353.026,78.3653 352,88.5C 351.173,102.852 350.173,117.185 349,131.5C 344.439,160.345 328.773,179.678 302,189.5C 291.762,194.358 285.928,190.858 284.5,179C 285.203,171.486 286.036,163.653 287,155.5C 291.882,152.975 296.715,150.308 301.5,147.5C 304.586,144.245 307.086,140.578 309,136.5C 311.219,129.588 312.719,122.754 313.5,116C 313.497,107.698 313.497,99.3647 313.5,91C 314.632,65.9026 323.632,43.4026 340.5,23.5C 361.565,3.09454 386.565,-4.07213 415.5,2C 445.262,9.09367 464.762,27.2603 474,56.5C 475.98,63.0871 477.647,69.7538 479,76.5C 480.871,93.454 482.204,110.454 483,127.5C 485.256,140.876 492.756,149.71 505.5,154C 506.893,155.171 507.727,156.671 508,158.5C 508.667,167.5 508.667,176.5 508,185.5C 504.93,191.856 500.263,193.189 494,189.5C 479.163,185.04 466.663,176.04 456.5,162.5C 446.824,144.034 442.824,125.034 444.5,105.5C 442.948,98.5843 441.948,91.751 441.5,85C 442.252,84.3292 442.586,83.4959 442.5,82.5 Z"/></g>
<g><path style="opacity:0.991" fill="#00559b" d="M 594.5,2.5 C 613.968,0.904491 632.968,3.07116 651.5,9C 674.169,19.3053 686.503,36.9719 688.5,62C 688.359,63.9552 687.526,65.4552 686,66.5C 672.572,66.0401 659.072,65.8734 645.5,66C 642.422,45.645 630.255,36.145 609,37.5C 596.622,36.9473 586.289,40.614 578,48.5C 573.464,58.2759 575.964,65.7759 585.5,71C 589.419,72.8618 593.419,74.5285 597.5,76C 616.357,80.7139 635.024,86.0472 653.5,92C 683.447,104.049 696.947,126.215 694,158.5C 687.706,189.458 668.873,207.624 637.5,213C 630.921,213.607 624.421,214.44 618,215.5C 611.8,214.569 605.134,214.569 598,215.5C 597.5,215 597,214.5 596.5,214C 554.483,209.149 531.483,185.649 527.5,143.5C 541.155,142.001 554.821,140.834 568.5,140C 575.053,170.166 593.719,182.5 624.5,177C 644.362,173.516 652.862,162.016 650,142.5C 645.908,136.755 640.408,132.922 633.5,131C 617.878,126.511 602.211,122.178 586.5,118C 569.692,113.349 555.525,104.515 544,91.5C 530.909,70.2782 531.242,48.9449 545,27.5C 558.216,12.6419 574.716,4.30854 594.5,2.5 Z"/></g>
<g><path style="opacity:0.991" fill="#00559b" d="M 33.5,15.5 C 47.4123,15.1767 61.2456,15.5101 75,16.5C 84.3319,59.1616 93.6652,101.828 103,144.5C 114.956,101.679 126.456,58.6787 137.5,15.5C 153.744,15.1752 169.911,15.5086 186,16.5C 196.692,59.9344 207.692,103.268 219,146.5C 228.539,103.138 238.206,59.8048 248,16.5C 261.421,15.5103 274.921,15.177 288.5,15.5C 273.526,80.2621 258.026,144.929 242,209.5C 234.743,210.159 227.41,210.492 220,210.5C 212.431,210.481 205.097,209.815 198,208.5C 185.739,162.14 173.406,115.473 161,68.5C 148.652,115.561 136.152,162.561 123.5,209.5C 108.833,210.833 94.1667,210.833 79.5,209.5C 63.8701,145.446 48.5368,80.7792 33.5,15.5 Z"/></g>
<g><path style="opacity:0.09" fill="#0b749c" d="M 441.5,80.5 C 442.338,80.8417 442.672,81.5084 442.5,82.5C 440.895,81.9941 440.561,81.3274 441.5,80.5 Z"/></g>
<g><path style="opacity:0.965" fill="#04b441" d="M 360.5,189.5 C 385.169,189.333 409.836,189.5 434.5,190C 436.594,191.255 437.594,193.088 437.5,195.5C 433.819,214.014 422.819,225.514 404.5,230C 380.961,231.986 365.461,221.82 358,199.5C 356.861,195.579 357.695,192.246 360.5,189.5 Z"/></g>
<g><path style="opacity:0.897" fill="#0469b6" d="M 131.5,254.5 C 136.214,254.353 140.881,254.686 145.5,255.5C 145.82,258.898 145.487,262.232 144.5,265.5C 142.154,258.437 137.488,256.27 130.5,259C 127.277,262.112 126.777,265.612 129,269.5C 134.301,273.8 139.301,278.466 144,283.5C 149.636,297.23 145.136,305.23 130.5,307.5C 127.157,306.974 123.99,305.974 121,304.5C 120.087,300.638 120.42,296.972 122,293.5C 123.822,302.494 128.989,305.327 137.5,302C 142.644,297.392 142.81,292.559 138,287.5C 131.874,283.047 126.874,277.713 123,271.5C 120.588,262.99 123.421,257.323 131.5,254.5 Z"/></g>
<g><path style="opacity:0.897" fill="#0269b7" d="M 155.5,254.5 C 168.846,255.797 182.179,255.797 195.5,254.5C 196.833,257.833 196.833,261.167 195.5,264.5C 194.937,262.291 193.604,260.791 191.5,260C 187.179,259.501 182.846,259.334 178.5,259.5C 178.333,272.837 178.5,286.171 179,299.5C 179.425,303.306 181.592,305.14 185.5,305C 182.522,306.125 179.355,306.625 176,306.5C 173.167,306.167 170.333,305.833 167.5,305.5C 170.229,304.938 171.729,303.272 172,300.5C 172.5,286.837 172.667,273.171 172.5,259.5C 167.821,259.334 163.155,259.501 158.5,260C 156.824,261.177 155.491,262.677 154.5,264.5C 154.167,263.833 153.833,263.167 153.5,262.5C 154.171,259.815 154.838,257.148 155.5,254.5 Z"/></g>
<g><path style="opacity:0.909" fill="#0469b5" d="M 240.5,254.5 C 242.124,254.36 243.29,255.027 244,256.5C 249.413,271.739 255.413,286.739 262,301.5C 263.925,303.213 266.092,304.547 268.5,305.5C 263.416,306.89 258.416,306.723 253.5,305C 254.022,304.439 254.355,303.772 254.5,303C 252.916,297.667 250.916,292.5 248.5,287.5C 243.615,286.198 238.782,286.198 234,287.5C 232.399,292.136 230.899,296.802 229.5,301.5C 229.728,303.397 230.728,304.73 232.5,305.5C 231.372,306.262 230.205,306.929 229,307.5C 224.735,306.965 220.568,306.131 216.5,305C 221.849,304.653 225.016,301.819 226,296.5C 231.342,282.641 236.175,268.641 240.5,254.5 Z M 240.5,266.5 C 242.928,271.868 245.261,277.368 247.5,283C 243.459,283.827 239.459,283.66 235.5,282.5C 237.575,277.276 239.242,271.942 240.5,266.5 Z"/></g>
<g><path style="opacity:0.897" fill="#0269b7" d="M 394.5,254.5 C 407.846,255.797 421.179,255.797 434.5,254.5C 435.833,257.833 435.833,261.167 434.5,264.5C 433.937,262.291 432.604,260.791 430.5,260C 426.179,259.501 421.846,259.334 417.5,259.5C 417.333,272.837 417.5,286.171 418,299.5C 418.425,303.306 420.592,305.14 424.5,305C 421.522,306.125 418.355,306.625 415,306.5C 412.167,306.167 409.333,305.833 406.5,305.5C 409.229,304.938 410.729,303.272 411,300.5C 411.5,286.837 411.667,273.171 411.5,259.5C 406.821,259.334 402.155,259.501 397.5,260C 395.824,261.177 394.491,262.677 393.5,264.5C 393.167,263.833 392.833,263.167 392.5,262.5C 393.171,259.815 393.838,257.148 394.5,254.5 Z"/></g>
<g><path style="opacity:0.897" fill="#0469b6" d="M 475.5,254.5 C 480.214,254.353 484.881,254.686 489.5,255.5C 489.82,258.898 489.487,262.232 488.5,265.5C 486.154,258.437 481.488,256.27 474.5,259C 471.277,262.112 470.777,265.612 473,269.5C 478.301,273.8 483.301,278.466 488,283.5C 493.636,297.23 489.136,305.23 474.5,307.5C 471.157,306.974 467.99,305.974 465,304.5C 464.087,300.638 464.42,296.972 466,293.5C 467.822,302.494 472.989,305.327 481.5,302C 486.644,297.392 486.81,292.559 482,287.5C 475.874,283.047 470.874,277.713 467,271.5C 464.588,262.99 467.421,257.323 475.5,254.5 Z"/></g>
<g><path style="opacity:0.897" fill="#0469b6" d="M 556.5,254.5 C 561.214,254.353 565.881,254.686 570.5,255.5C 570.82,258.898 570.487,262.232 569.5,265.5C 567.154,258.437 562.488,256.27 555.5,259C 552.277,262.112 551.777,265.612 554,269.5C 559.301,273.8 564.301,278.466 569,283.5C 574.636,297.23 570.136,305.23 555.5,307.5C 552.157,306.974 548.99,305.974 546,304.5C 545.087,300.638 545.42,296.972 547,293.5C 548.822,302.494 553.989,305.327 562.5,302C 567.644,297.392 567.81,292.559 563,287.5C 556.874,283.047 551.874,277.713 548,271.5C 545.588,262.99 548.421,257.323 556.5,254.5 Z"/></g>
<g><path style="opacity:0.897" fill="#0269b7" d="M 579.5,254.5 C 592.846,255.797 606.179,255.797 619.5,254.5C 620.833,257.833 620.833,261.167 619.5,264.5C 618.937,262.291 617.604,260.791 615.5,260C 611.179,259.501 606.846,259.334 602.5,259.5C 602.333,272.837 602.5,286.171 603,299.5C 603.425,303.306 605.592,305.14 609.5,305C 606.522,306.125 603.355,306.625 600,306.5C 597.167,306.167 594.333,305.833 591.5,305.5C 594.229,304.938 595.729,303.272 596,300.5C 596.5,286.837 596.667,273.171 596.5,259.5C 591.821,259.334 587.155,259.501 582.5,260C 580.824,261.177 579.491,262.677 578.5,264.5C 578.167,263.833 577.833,263.167 577.5,262.5C 578.171,259.815 578.838,257.148 579.5,254.5 Z"/></g>
<g><path style="opacity:0.912" fill="#0369b6" d="M 731.5,304.5 C 731.5,305.167 731.5,305.833 731.5,306.5C 726.819,306.331 722.152,305.998 717.5,305.5C 717.328,293.782 716.162,282.116 714,270.5C 708.661,282.511 702.828,294.178 696.5,305.5C 694.768,303.717 693.268,301.717 692,299.5C 687.711,289.956 683.044,280.623 678,271.5C 677.194,280.67 676.361,289.836 675.5,299C 675.104,302.767 676.77,304.767 680.5,305C 678.03,306.114 675.364,306.614 672.5,306.5C 670.167,306.167 667.833,305.833 665.5,305.5C 667.193,304.772 668.693,303.772 670,302.5C 670.834,296.331 671.667,290.165 672.5,284C 672.415,282.893 672.081,281.893 671.5,281C 673.274,272.223 674.941,263.389 676.5,254.5C 683.94,267.958 691.107,281.625 698,295.5C 701.947,287.274 705.614,278.941 709,270.5C 711.93,264.966 715.096,259.633 718.5,254.5C 720.734,269.101 722.567,283.768 724,298.5C 724.863,302.518 727.363,304.518 731.5,304.5 Z"/></g>
<g><path style="opacity:0.904" fill="#0469b6" d="M 1.5,255.5 C 7.50924,255.334 13.5092,255.501 19.5,256C 18.4366,257.188 17.1033,257.688 15.5,257.5C 17.5666,270.099 20.7333,282.433 25,294.5C 26.9754,288.904 29.142,283.404 31.5,278C 31.1667,277.667 30.8333,277.333 30.5,277C 33.7485,269.735 37.0819,262.569 40.5,255.5C 45.815,268.273 50.6483,281.273 55,294.5C 58.4216,284.582 61.7549,274.249 65,263.5C 65.6667,261.5 65.6667,259.5 65,257.5C 63.7567,258.336 62.5901,258.003 61.5,256.5C 66.5,255.167 71.5,255.167 76.5,256.5C 72.9065,256.926 70.7398,258.926 70,262.5C 65.4651,275.771 61.1318,289.105 57,302.5C 56.2515,304.332 55.2515,305.999 54,307.5C 48.6171,294.69 43.6171,281.69 39,268.5C 34.2352,281.809 28.9019,294.809 23,307.5C 21.3859,303.828 19.5526,300.328 17.5,297C 17.9574,296.586 18.2907,296.086 18.5,295.5C 15.103,284.142 11.603,272.808 8,261.5C 6.32165,258.77 4.15498,256.77 1.5,255.5 Z"/></g>
<g><path style="opacity:0.911" fill="#0368b6" d="M 107.5,254.5 C 108.736,257.818 108.403,261.151 106.5,264.5C 105.756,263.009 105.09,261.509 104.5,260C 100.582,258.844 96.5817,258.344 92.5,258.5C 92.5,264.833 92.5,271.167 92.5,277.5C 96.5138,277.666 100.514,277.499 104.5,277C 106.382,274.935 107.382,275.435 107.5,278.5C 107.064,281.179 106.564,283.845 106,286.5C 104.98,285.109 104.147,283.609 103.5,282C 99.9399,280.763 96.2733,280.263 92.5,280.5C 92.3337,287.175 92.5004,293.842 93,300.5C 93.5,301 94,301.5 94.5,302C 98.1667,302.667 101.833,302.667 105.5,302C 106.956,300.255 108.289,298.422 109.5,296.5C 110.52,300.562 109.687,304.228 107,307.5C 98.3882,306.535 89.8882,305.869 81.5,305.5C 82.7598,304.618 83.9264,303.618 85,302.5C 85.6667,287.833 85.6667,273.167 85,258.5C 83.4905,257.91 81.9905,257.244 80.5,256.5C 89.6577,255.833 98.6577,255.167 107.5,254.5 Z"/></g>
<g><path style="opacity:0.919" fill="#0268b6" d="M 271.5,255.5 C 277.206,255.171 282.872,255.505 288.5,256.5C 287.009,257.244 285.509,257.91 284,258.5C 283.333,272.167 283.333,285.833 284,299.5C 284.374,300.416 284.874,301.25 285.5,302C 289.833,302.667 294.167,302.667 298.5,302C 299.956,300.255 301.289,298.422 302.5,296.5C 303.296,299.717 302.963,302.883 301.5,306C 291.633,306.564 281.967,306.398 272.5,305.5C 273.76,304.618 274.926,303.618 276,302.5C 276.667,287.833 276.667,273.167 276,258.5C 273.974,258.085 272.474,257.085 271.5,255.5 Z"/></g>
<g><path style="opacity:0.911" fill="#0368b6" d="M 337.5,254.5 C 338.736,257.818 338.403,261.151 336.5,264.5C 335.756,263.009 335.09,261.509 334.5,260C 330.582,258.844 326.582,258.344 322.5,258.5C 322.5,264.833 322.5,271.167 322.5,277.5C 326.514,277.666 330.514,277.499 334.5,277C 336.382,274.935 337.382,275.435 337.5,278.5C 337.064,281.179 336.564,283.845 336,286.5C 334.98,285.109 334.147,283.609 333.5,282C 329.94,280.763 326.273,280.263 322.5,280.5C 322.334,287.175 322.5,293.842 323,300.5C 323.5,301 324,301.5 324.5,302C 328.167,302.667 331.833,302.667 335.5,302C 336.956,300.255 338.289,298.422 339.5,296.5C 340.52,300.562 339.687,304.228 337,307.5C 328.388,306.535 319.888,305.869 311.5,305.5C 312.76,304.618 313.926,303.618 315,302.5C 315.667,287.833 315.667,273.167 315,258.5C 313.491,257.91 311.991,257.244 310.5,256.5C 319.658,255.833 328.658,255.167 337.5,254.5 Z"/></g>
<g><path style="opacity:0.934" fill="#0569b5" d="M 351.5,255.5 C 359.174,255.334 366.841,255.5 374.5,256C 383.231,258.62 386.398,264.453 384,273.5C 382.224,276.941 380.057,280.108 377.5,283C 382.358,289.704 387.691,296.037 393.5,302C 396.218,303.072 398.885,304.238 401.5,305.5C 396.799,306.731 392.132,306.564 387.5,305C 381.82,298.985 376.487,292.651 371.5,286C 368.883,285.178 366.216,284.678 363.5,284.5C 363.334,290.509 363.501,296.509 364,302.5C 365.6,303.866 367.433,304.866 369.5,305.5C 363.681,306.207 358.014,306.207 352.5,305.5C 353.76,304.618 354.926,303.618 356,302.5C 356.667,287.833 356.667,273.167 356,258.5C 353.974,258.085 352.474,257.085 351.5,255.5 Z M 363.5,258.5 C 376.291,258.713 380.791,265.046 377,277.5C 375.688,280.581 373.355,282.248 370,282.5C 367.959,281.577 365.792,281.244 363.5,281.5C 363.5,273.833 363.5,266.167 363.5,258.5 Z"/></g>
<g><path style="opacity:0.905" fill="#0369b5" d="M 494.5,255.5 C 499.214,255.173 503.88,255.507 508.5,256.5C 507.975,257.192 507.308,257.692 506.5,258C 510.456,265.416 514.79,272.583 519.5,279.5C 522.791,273.376 526.291,267.376 530,261.5C 530.651,259.765 530.485,258.098 529.5,256.5C 533.833,255.167 538.167,255.167 542.5,256.5C 539.345,257.15 536.845,258.817 535,261.5C 529.893,268.712 525.56,276.379 522,284.5C 521.333,290.167 521.333,295.833 522,301.5C 523.362,303.436 525.195,304.769 527.5,305.5C 521.833,306.833 516.167,306.833 510.5,305.5C 511.628,304.738 512.795,304.071 514,303.5C 516.266,295.703 515.933,288.036 513,280.5C 510.083,276.334 507.416,272.001 505,267.5C 502.291,262.636 498.791,258.636 494.5,255.5 Z"/></g>
<g><path style="opacity:0.911" fill="#0368b6" d="M 655.5,254.5 C 656.736,257.818 656.403,261.151 654.5,264.5C 653.756,263.009 653.09,261.509 652.5,260C 648.582,258.844 644.582,258.344 640.5,258.5C 640.5,264.833 640.5,271.167 640.5,277.5C 644.514,277.666 648.514,277.499 652.5,277C 654.382,274.935 655.382,275.435 655.5,278.5C 655.064,281.179 654.564,283.845 654,286.5C 652.98,285.109 652.147,283.609 651.5,282C 647.94,280.763 644.273,280.263 640.5,280.5C 640.334,287.175 640.5,293.842 641,300.5C 641.5,301 642,301.5 642.5,302C 646.167,302.667 649.833,302.667 653.5,302C 654.956,300.255 656.289,298.422 657.5,296.5C 658.52,300.562 657.687,304.228 655,307.5C 646.388,306.535 637.888,305.869 629.5,305.5C 630.76,304.618 631.926,303.618 633,302.5C 633.667,287.833 633.667,273.167 633,258.5C 631.491,257.91 629.991,257.244 628.5,256.5C 637.658,255.833 646.658,255.167 655.5,254.5 Z"/></g>
</svg>
```
### Steps to Reproduce
Create a Maui app , change the appicon to the svg image given , try to build the solution you will get this error
### Version with bug
Preview 13 (current)
### Last version that worked well
Unknown/Other
### Affected platforms
iOS
### Affected platform versions
iOS 15.2
### Did you find any workaround?
_No response_
### Relevant log output
```shell
/usr/local/share/dotnet/packs/Microsoft.iOS.Sdk/15.2.301-preview.13.7/tools/msbuild/iOS/Xamarin.Shared.targets(808,3): error : /usr/bin/xcrun exited with code 1 [/Users/rockclane/MyMauiApp/MyMauiApp.csproj]
/usr/local/share/dotnet/packs/Microsoft.iOS.Sdk/15.2.301-preview.13.7/tools/msbuild/iOS/Xamarin.Shared.targets(808,3): error : [/Users/rockclane/MyMauiApp/MyMauiApp.csproj]
/usr/local/share/dotnet/packs/Microsoft.iOS.Sdk/15.2.301-preview.13.7/tools/msbuild/iOS/Xamarin.Shared.targets(808,3): error : actool exited with code 1 [/Users/rockclane/MyMauiApp/MyMauiApp.csproj]
/usr/local/share/dotnet/packs/Microsoft.iOS.Sdk/15.2.301-preview.13.7/tools/msbuild/iOS/Xamarin.Shared.targets(808,3): error : [/Users/rockclane/MyMauiApp/MyMauiApp.csproj]
/Users/rockclane/MyMauiApp/obj/Debug/net6.0-ios/iossimulator-x64/actool/cloned-assets/Assets.xcassets : actool error : The stickers icon set or app icon set named "appicon" did not have any applicable content. [/Users/rockclane/MyMauiApp/MyMauiApp.csproj]
```
| test | build error for maui app icon svg format is not supported in ios plaftform description i see a build error when trying to use a maui app icon in svg format attaching the icon which i am using ios build fails with this error actool error the stickers icon set or app icon set named appicon did not have any applicable content svg content xml doctype svg public dtd svg en svg xmlns version width height style shape rendering geometricprecision text rendering geometricprecision image rendering optimizequality fill rule evenodd clip rule evenodd xmlns xlink steps to reproduce create a maui app change the appicon to the svg image given try to build the solution you will get this error version with bug preview current last version that worked well unknown other affected platforms ios affected platform versions ios did you find any workaround no response relevant log output shell usr local share dotnet packs microsoft ios sdk preview tools msbuild ios xamarin shared targets error usr bin xcrun exited with code usr local share dotnet packs microsoft ios sdk preview tools msbuild ios xamarin shared targets error usr local share dotnet packs microsoft ios sdk preview tools msbuild ios xamarin shared targets error actool exited with code usr local share dotnet packs microsoft ios sdk preview tools msbuild ios xamarin shared targets error users rockclane mymauiapp obj debug ios iossimulator actool cloned assets assets xcassets actool error the stickers icon set or app icon set named appicon did not have any applicable content | 1 |
693,061 | 23,761,343,269 | IssuesEvent | 2022-09-01 09:07:33 | o3de/o3de | https://api.github.com/repos/o3de/o3de | reopened | Installing O3DE on Ubuntu breaks the Package Manager | kind/bug sig/core triage/accepted triage/needs-information priority/blocker | **Describe the bug**
Installing O3DE on Ubuntu breaks the Advanced Package Manager, making it impossible to introduce any change to the packages in the system. Installation process returns an error, but the Editor can be launched. The following workaround for fixing APT has been found:
```
sudo rm /var/lib/dpkg/info/o3de*
sudo dpkg --configure -D 777 o3de
sudo apt -f install
```
**Steps to reproduce**
Steps to reproduce the behavior:
1. Download the latest Debian package.
2. Follow the official installation instruction (https://www.o3de.org/docs/welcome-guide/setup/installing-linux/).
3. Attempt to install or remove any package using APT.
**Expected behavior**
APT is fully functional after installing O3DE using a Debian package.
**Actual behavior**
APT does not function after the installation process.
**Screenshots/Video**
https://user-images.githubusercontent.com/86951905/150796372-2420d736-3480-4efa-8279-68e50fba45e2.mp4
**Found in Branch**
Stabilization/2111RTE deb package
**Desktop/Device:**
- Device: PC
- OS: Ubuntu
- Version 18.04
- CPU AMD Ryzen 3600
- GPU Nvidia GeForce RTX 2060 SUPER
- Memory 16GB | 1.0 | Installing O3DE on Ubuntu breaks the Package Manager - **Describe the bug**
Installing O3DE on Ubuntu breaks the Advanced Package Manager, making it impossible to introduce any change to the packages in the system. Installation process returns an error, but the Editor can be launched. The following workaround for fixing APT has been found:
```
sudo rm /var/lib/dpkg/info/o3de*
sudo dpkg --configure -D 777 o3de
sudo apt -f install
```
**Steps to reproduce**
Steps to reproduce the behavior:
1. Download the latest Debian package.
2. Follow the official installation instruction (https://www.o3de.org/docs/welcome-guide/setup/installing-linux/).
3. Attempt to install or remove any package using APT.
**Expected behavior**
APT is fully functional after installing O3DE using a Debian package.
**Actual behavior**
APT does not function after the installation process.
**Screenshots/Video**
https://user-images.githubusercontent.com/86951905/150796372-2420d736-3480-4efa-8279-68e50fba45e2.mp4
**Found in Branch**
Stabilization/2111RTE deb package
**Desktop/Device:**
- Device: PC
- OS: Ubuntu
- Version 18.04
- CPU AMD Ryzen 3600
- GPU Nvidia GeForce RTX 2060 SUPER
- Memory 16GB | non_test | installing on ubuntu breaks the package manager describe the bug installing on ubuntu breaks the advanced package manager making it impossible to introduce any change to the packages in the system installation process returns an error but the editor can be launched the following workaround for fixing apt has been found sudo rm var lib dpkg info sudo dpkg configure d sudo apt f install steps to reproduce steps to reproduce the behavior download the latest debian package follow the official installation instruction attempt to install or remove any package using apt expected behavior apt is fully functional after installing using a debian package actual behavior apt does not function after the installation process screenshots video found in branch stabilization deb package desktop device device pc os ubuntu version cpu amd ryzen gpu nvidia geforce rtx super memory | 0 |
42,896 | 17,362,208,103 | IssuesEvent | 2021-07-29 22:43:39 | MicrosoftDocs/azure-docs | https://api.github.com/repos/MicrosoftDocs/azure-docs | closed | Document "agentpool" node label | Pri1 assigned-to-author container-service/svc doc-enhancement triaged | It appears that [AKS nodes automatically include a label that identifies the node pool to which they belong](https://stackoverflow.com/a/56371867/67824):
`agentpool=pool_name`
This seems to be an extremely useful fact, but I couldn't find it documented anywhere in the MS docs.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 8c420b2c-e868-9a6a-49fb-913f2cd007ef
* Version Independent ID: 5c543e08-7d75-21eb-9510-22e2cd56d16b
* Content: [Use multiple node pools in Azure Kubernetes Service (AKS) - Azure Kubernetes Service](https://docs.microsoft.com/en-us/azure/aks/use-multiple-node-pools)
* Content Source: [articles/aks/use-multiple-node-pools.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/aks/use-multiple-node-pools.md)
* Service: **container-service**
* GitHub Login: @mlearned
* Microsoft Alias: **mlearned** | 1.0 | Document "agentpool" node label - It appears that [AKS nodes automatically include a label that identifies the node pool to which they belong](https://stackoverflow.com/a/56371867/67824):
`agentpool=pool_name`
This seems to be an extremely useful fact, but I couldn't find it documented anywhere in the MS docs.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 8c420b2c-e868-9a6a-49fb-913f2cd007ef
* Version Independent ID: 5c543e08-7d75-21eb-9510-22e2cd56d16b
* Content: [Use multiple node pools in Azure Kubernetes Service (AKS) - Azure Kubernetes Service](https://docs.microsoft.com/en-us/azure/aks/use-multiple-node-pools)
* Content Source: [articles/aks/use-multiple-node-pools.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/aks/use-multiple-node-pools.md)
* Service: **container-service**
* GitHub Login: @mlearned
* Microsoft Alias: **mlearned** | non_test | document agentpool node label it appears that agentpool pool name this seems to be an extremely useful fact but i couldn t find it documented anywhere in the ms docs document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service container service github login mlearned microsoft alias mlearned | 0 |
114,119 | 17,187,966,817 | IssuesEvent | 2021-07-16 06:42:21 | elastic/kibana | https://api.github.com/repos/elastic/kibana | closed | [Security Solution]"Detection Rules" is getting displayed instead of "Rules" in breadcrumb | QA:Validated Team: SecuritySolution Team:Detections and Resp bug fixed impact:high v7.14.0 | **Description:**
"Detection Rules" is getting displayed instead of "Rules" in breadcrumb
**Build Details:**
Version: 7.14.0 BC1
Commit: 071a74e02f82b79a4a10026b5c9e02d593112fd4
Build: 42292
Artifact Page : https://staging.elastic.co/7.14.0-8eba2f5f/summary-7.14.0.html
**Browser Details:**
All
**Preconditions:**
- Kibana Environment should exist.
- Endpoint Security and elastic agent should be installed
**Steps to Reproduce:**
1. Navigate to 'Rules' tab under Security Solutions
2. Click on any rule and notice that user is navigated to Edit Rule/Rule Detail page.
3. Observe that "Detection Rules" is getting displayed instead of "Rules" in breadcrumb
**Actual Result:**
"Detection Rules" is getting displayed instead of "Rules" in breadcrumb
**Screen-Shot**
**Expected Result:**
"Detection Rules" should be "Rules" in breadcrumb
**What's not working:**
- NA
**What's working:**
- NA | True | [Security Solution]"Detection Rules" is getting displayed instead of "Rules" in breadcrumb - **Description:**
"Detection Rules" is getting displayed instead of "Rules" in breadcrumb
**Build Details:**
Version: 7.14.0 BC1
Commit: 071a74e02f82b79a4a10026b5c9e02d593112fd4
Build: 42292
Artifact Page : https://staging.elastic.co/7.14.0-8eba2f5f/summary-7.14.0.html
**Browser Details:**
All
**Preconditions:**
- Kibana Environment should exist.
- Endpoint Security and elastic agent should be installed
**Steps to Reproduce:**
1. Navigate to 'Rules' tab under Security Solutions
2. Click on any rule and notice that user is navigated to Edit Rule/Rule Detail page.
3. Observe that "Detection Rules" is getting displayed instead of "Rules" in breadcrumb
**Actual Result:**
"Detection Rules" is getting displayed instead of "Rules" in breadcrumb
**Screen-Shot**
**Expected Result:**
"Detection Rules" should be "Rules" in breadcrumb
**What's not working:**
- NA
**What's working:**
- NA | non_test | detection rules is getting displayed instead of rules in breadcrumb description detection rules is getting displayed instead of rules in breadcrumb build details version commit build artifact page browser details all preconditions kibana environment should exist endpoint security and elastic agent should be installed steps to reproduce navigate to rules tab under security solutions click on any rule and notice that user is navigated to edit rule rule detail page observe that detection rules is getting displayed instead of rules in breadcrumb actual result detection rules is getting displayed instead of rules in breadcrumb screen shot expected result detection rules should be rules in breadcrumb what s not working na what s working na | 0 |
499,221 | 14,443,221,888 | IssuesEvent | 2020-12-07 19:19:11 | colab-coop/hello-voter | https://api.github.com/repos/colab-coop/hello-voter | closed | Fix State Field Case Sensitivity for Ambassador Sign-Up | Highest Priority | # Summary
As an Ambassador going through the sign-up workflow, I do not want to be blocked by entering my state in lowercase format so that I do not experience any friction in the sign-up process.
# Requirements
* When I am signing up to be an Ambassador, if I enter either or both characters for my state in lowercase format, I should not see an error
* Currently the error message for using any lowercase characters is "Sorry, but state employment laws don't allow us to pay Voting Ambassadors in your state."
Current page/error message for reference:
<img width="719" alt="Screen Shot 2020-09-25 at 6 49 45 PM" src="https://user-images.githubusercontent.com/8608070/94345311-d84afa80-ffd9-11ea-9bb4-2e0ca3eede0a.png">
| 1.0 | Fix State Field Case Sensitivity for Ambassador Sign-Up - # Summary
As an Ambassador going through the sign-up workflow, I do not want to be blocked by entering my state in lowercase format so that I do not experience any friction in the sign-up process.
# Requirements
* When I am signing up to be an Ambassador, if I enter either or both characters for my state in lowercase format, I should not see an error
* Currently the error message for using any lowercase characters is "Sorry, but state employment laws don't allow us to pay Voting Ambassadors in your state."
Current page/error message for reference:
<img width="719" alt="Screen Shot 2020-09-25 at 6 49 45 PM" src="https://user-images.githubusercontent.com/8608070/94345311-d84afa80-ffd9-11ea-9bb4-2e0ca3eede0a.png">
| non_test | fix state field case sensitivity for ambassador sign up summary as an ambassador going through the sign up workflow i do not want to be blocked by entering my state in lowercase format so that i do not experience any friction in the sign up process requirements when i am signing up to be an ambassador if i enter either or both characters for my state in lowercase format i should not see an error currently the error message for using any lowercase characters is sorry but state employment laws don t allow us to pay voting ambassadors in your state current page error message for reference img width alt screen shot at pm src | 0 |
152,969 | 24,047,675,514 | IssuesEvent | 2022-09-16 09:47:21 | MTES-MCT/monitorfish | https://api.github.com/repos/MTES-MCT/monitorfish | closed | Pistes VMS - Pouvoir filtrer les pistes par horaires | design dev new feature | Deux besoins identifiés :
- côté pôle SIP, pour les réquisitions judiciaires
- côté unités, pour faciliter l'élaboration des contrôles croisés
Ce ne sont pas des besoins opérationnels purs, en tous cas pas du temps réel. A voir si rajouter les horaires sur les pistes est le bon moyen de répondre à ces besoins | 1.0 | Pistes VMS - Pouvoir filtrer les pistes par horaires - Deux besoins identifiés :
- côté pôle SIP, pour les réquisitions judiciaires
- côté unités, pour faciliter l'élaboration des contrôles croisés
Ce ne sont pas des besoins opérationnels purs, en tous cas pas du temps réel. A voir si rajouter les horaires sur les pistes est le bon moyen de répondre à ces besoins | non_test | pistes vms pouvoir filtrer les pistes par horaires deux besoins identifiés côté pôle sip pour les réquisitions judiciaires côté unités pour faciliter l élaboration des contrôles croisés ce ne sont pas des besoins opérationnels purs en tous cas pas du temps réel a voir si rajouter les horaires sur les pistes est le bon moyen de répondre à ces besoins | 0 |
246,138 | 20,825,062,547 | IssuesEvent | 2022-03-18 19:43:43 | radiasoft/pykern | https://api.github.com/repos/radiasoft/pykern | opened | Add xlsx cases to pkunitN_test.py (case_dirs) | test | case_dirs has a lot of code for xlsx conversions. go through a few of the paths. will serve as good examples | 1.0 | Add xlsx cases to pkunitN_test.py (case_dirs) - case_dirs has a lot of code for xlsx conversions. go through a few of the paths. will serve as good examples | test | add xlsx cases to pkunitn test py case dirs case dirs has a lot of code for xlsx conversions go through a few of the paths will serve as good examples | 1 |
173,771 | 13,443,204,511 | IssuesEvent | 2020-09-08 08:00:34 | Cookie-AutoDelete/Cookie-AutoDelete | https://api.github.com/repos/Cookie-AutoDelete/Cookie-AutoDelete | closed | [BUG] List of Expression shows lots (30+) of "INVALID CONTAINER" messages under each of the containers | incomplete untested bug/issue | Under List of Expressions, "INVALID CONTAINER" appears 38 times (in red)
** Steps to reproduce the behavior ** :
1. Open CAD Settings
2. Go to "List of Expressions"
3. See error
**Expected Behavior**
Have not seen this behaviour befor
A clear and concise description of what you expected to happen.
**Screenshots**
See screenshot:
**Your System Info**
- MacOS 10.15.6
- Firefox 80.0.1 (64-bit)
- CookieAutoDelete Version: 3.5.1 | 1.0 | [BUG] List of Expression shows lots (30+) of "INVALID CONTAINER" messages under each of the containers - Under List of Expressions, "INVALID CONTAINER" appears 38 times (in red)
** Steps to reproduce the behavior ** :
1. Open CAD Settings
2. Go to "List of Expressions"
3. See error
**Expected Behavior**
Have not seen this behaviour befor
A clear and concise description of what you expected to happen.
**Screenshots**
See screenshot:
**Your System Info**
- MacOS 10.15.6
- Firefox 80.0.1 (64-bit)
- CookieAutoDelete Version: 3.5.1 | test | list of expression shows lots of invalid container messages under each of the containers under list of expressions invalid container appears times in red steps to reproduce the behavior open cad settings go to list of expressions see error expected behavior have not seen this behaviour befor a clear and concise description of what you expected to happen screenshots see screenshot your system info macos firefox bit cookieautodelete version | 1 |
42,180 | 5,428,252,930 | IssuesEvent | 2017-03-03 15:29:11 | TheScienceMuseum/collectionsonline | https://api.github.com/repos/TheScienceMuseum/collectionsonline | closed | New API route/method to convert a OBJECT NUMBER to it's path | enhancement please-test priority-2 T4h | Given `OBJECT NUMBER `-> return the path to it's page
ie. 1998-599 would return /objects/co467174/hypothermia-advice-card-england-1994-1995-card
Additional, if we could add a flag `redirect=true` to automatically perform a `301 redirect` to the page that would be super useful.
- /search?oid=1998-599 ---> return page path for this object as JSON _(as per other API calls)_
- /search?oid=1998-599&redirect=true ---> simply return a 301 redirect to the page `(with a full url/path).`
_(feel free to adjust params as makes sense)_
| 1.0 | New API route/method to convert a OBJECT NUMBER to it's path - Given `OBJECT NUMBER `-> return the path to it's page
ie. 1998-599 would return /objects/co467174/hypothermia-advice-card-england-1994-1995-card
Additional, if we could add a flag `redirect=true` to automatically perform a `301 redirect` to the page that would be super useful.
- /search?oid=1998-599 ---> return page path for this object as JSON _(as per other API calls)_
- /search?oid=1998-599&redirect=true ---> simply return a 301 redirect to the page `(with a full url/path).`
_(feel free to adjust params as makes sense)_
| test | new api route method to convert a object number to it s path given object number return the path to it s page ie would return objects hypothermia advice card england card additional if we could add a flag redirect true to automatically perform a redirect to the page that would be super useful search oid return page path for this object as json as per other api calls search oid redirect true simply return a redirect to the page with a full url path feel free to adjust params as makes sense | 1 |
404,138 | 27,451,194,140 | IssuesEvent | 2023-03-02 17:29:57 | LibertyDSNP/spec | https://api.github.com/repos/LibertyDSNP/spec | closed | DIP-226 Add Public Key Announcement | documentation enhancement DSNP | # Abstract
Proposes a new Public Key Announcement with initial support for a `keyAgreement` key type.
# Motivation
DSNP Users need to be able to share public keys in order to secure and transmit private data. An initial use case for this is to allow users to encrypt and decrypt their private social graph, and to enable two users to generate a shared secret that can be used to pseudonymously identify a relationship.
# Specification Pull Request
TBD
# Rationale
We expect every DSNP user to need at least one public key, which will typically be created contemporaneously with the creation of their DSNP User Id. Announcements provide a DSNP-centric approach that ensures public keys will be propagated to interested applications without requiring a new interface.
The choice of the term `keyAgreement` and the use of `publicKeyMultibase` serialization for keys is based on the same terms in the [W3C DID](https://www.w3.org/TR/did-core/) specification. These are rapidly evolving standards but appear to be aligned with usage in major decentralized projects including IPFS.
# Backwards Compatibility
Not applicable.
# Reference Implementation and/or Tests
None at this time.
# Security Considerations
Unlike Control Keys, public keys in announcements do not need to uniquely identify a DSNP User. Therefore, there is no requirement to ensure that all public keys are different. It is therefore possible (though extremely improbable if keys are generated randomly) that two users will publish the same public key.
The `revokedAsOf` field proposed is intended to allow for post-hoc revocation of keys that have been compromised, as well as keys that users wish to explicitly ensure are not trusted after a certain point in time.
# Dependencies
None.
# References
None at this time.
# Copyright
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
| 1.0 | DIP-226 Add Public Key Announcement - # Abstract
Proposes a new Public Key Announcement with initial support for a `keyAgreement` key type.
# Motivation
DSNP Users need to be able to share public keys in order to secure and transmit private data. An initial use case for this is to allow users to encrypt and decrypt their private social graph, and to enable two users to generate a shared secret that can be used to pseudonymously identify a relationship.
# Specification Pull Request
TBD
# Rationale
We expect every DSNP user to need at least one public key, which will typically be created contemporaneously with the creation of their DSNP User Id. Announcements provide a DSNP-centric approach that ensures public keys will be propagated to interested applications without requiring a new interface.
The choice of the term `keyAgreement` and the use of `publicKeyMultibase` serialization for keys is based on the same terms in the [W3C DID](https://www.w3.org/TR/did-core/) specification. These are rapidly evolving standards but appear to be aligned with usage in major decentralized projects including IPFS.
# Backwards Compatibility
Not applicable.
# Reference Implementation and/or Tests
None at this time.
# Security Considerations
Unlike Control Keys, public keys in announcements do not need to uniquely identify a DSNP User. Therefore, there is no requirement to ensure that all public keys are different. It is therefore possible (though extremely improbable if keys are generated randomly) that two users will publish the same public key.
The `revokedAsOf` field proposed is intended to allow for post-hoc revocation of keys that have been compromised, as well as keys that users wish to explicitly ensure are not trusted after a certain point in time.
# Dependencies
None.
# References
None at this time.
# Copyright
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
| non_test | dip add public key announcement abstract proposes a new public key announcement with initial support for a keyagreement key type motivation dsnp users need to be able to share public keys in order to secure and transmit private data an initial use case for this is to allow users to encrypt and decrypt their private social graph and to enable two users to generate a shared secret that can be used to pseudonymously identify a relationship specification pull request tbd rationale we expect every dsnp user to need at least one public key which will typically be created contemporaneously with the creation of their dsnp user id announcements provide a dsnp centric approach that ensures public keys will be propagated to interested applications without requiring a new interface the choice of the term keyagreement and the use of publickeymultibase serialization for keys is based on the same terms in the specification these are rapidly evolving standards but appear to be aligned with usage in major decentralized projects including ipfs backwards compatibility not applicable reference implementation and or tests none at this time security considerations unlike control keys public keys in announcements do not need to uniquely identify a dsnp user therefore there is no requirement to ensure that all public keys are different it is therefore possible though extremely improbable if keys are generated randomly that two users will publish the same public key the revokedasof field proposed is intended to allow for post hoc revocation of keys that have been compromised as well as keys that users wish to explicitly ensure are not trusted after a certain point in time dependencies none references none at this time copyright copyright and related rights waived via | 0 |
5,279 | 2,770,146,395 | IssuesEvent | 2015-05-01 11:33:44 | AAndharia/iManager | https://api.github.com/repos/AAndharia/iManager | reopened | Save employee in DB | Status - Tested & Working Type - Wiki | **Click on Submit or save button at step-3 bottom**
1 Check modal state
2.check email is not assigned to other check at server side.
3.create 8 character OTP(one time password).
4.add employee details in employee table.
5.send an welcome email to employee with account activation link. employee added successfully verify once then send an e-mail.
| 1.0 | Save employee in DB - **Click on Submit or save button at step-3 bottom**
1 Check modal state
2.check email is not assigned to other check at server side.
3.create 8 character OTP(one time password).
4.add employee details in employee table.
5.send an welcome email to employee with account activation link. employee added successfully verify once then send an e-mail.
| test | save employee in db click on submit or save button at step bottom check modal state check email is not assigned to other check at server side create character otp one time password add employee details in employee table send an welcome email to employee with account activation link employee added successfully verify once then send an e mail | 1 |
402,600 | 27,375,669,180 | IssuesEvent | 2023-02-28 05:35:35 | aws-samples/measuring-demand-forecast-benefits | https://api.github.com/repos/aws-samples/measuring-demand-forecast-benefits | opened | Update for Forecast expanded holiday calendar launch | documentation good first issue | Last week Amazon Forecast [expanded country support](https://aws.amazon.com/about-aws/whats-new/2023/02/amazon-forecast-built-in-holiday-data-251-countries/) for its built-in holiday featurization.
In the past we've used [workalendar](https://github.com/workalendar/workalendar) for holiday RTS for 2 reasons:
1. At the time of writing it covered some relevant countries that weren't available with Forecast's built-in calendars, particularly for Asia
- This should no longer be the case
2. At the time of writing, Forecast (and Canvas) didn't support trans-national models including multiple different holiday calendars
- I believe this still applies
Need somebody to go through the repo and check for + remove any mentions of (1) in the commentary, to avoid confusing people with inaccurate info. Probably no actual code changes required because (2) means our demonstrated approach still makes sense.
An extra observation: I'm not seeing the new Forecast countries available through SageMaker Canvas UI yet, but assume they'll get there at some point 🤷♂️ Something to be aware of when updating the comments. | 1.0 | Update for Forecast expanded holiday calendar launch - Last week Amazon Forecast [expanded country support](https://aws.amazon.com/about-aws/whats-new/2023/02/amazon-forecast-built-in-holiday-data-251-countries/) for its built-in holiday featurization.
In the past we've used [workalendar](https://github.com/workalendar/workalendar) for holiday RTS for 2 reasons:
1. At the time of writing it covered some relevant countries that weren't available with Forecast's built-in calendars, particularly for Asia
- This should no longer be the case
2. At the time of writing, Forecast (and Canvas) didn't support trans-national models including multiple different holiday calendars
- I believe this still applies
Need somebody to go through the repo and check for + remove any mentions of (1) in the commentary, to avoid confusing people with inaccurate info. Probably no actual code changes required because (2) means our demonstrated approach still makes sense.
An extra observation: I'm not seeing the new Forecast countries available through SageMaker Canvas UI yet, but assume they'll get there at some point 🤷♂️ Something to be aware of when updating the comments. | non_test | update for forecast expanded holiday calendar launch last week amazon forecast for its built in holiday featurization in the past we ve used for holiday rts for reasons at the time of writing it covered some relevant countries that weren t available with forecast s built in calendars particularly for asia this should no longer be the case at the time of writing forecast and canvas didn t support trans national models including multiple different holiday calendars i believe this still applies need somebody to go through the repo and check for remove any mentions of in the commentary to avoid confusing people with inaccurate info probably no actual code changes required because means our demonstrated approach still makes sense an extra observation i m not seeing the new forecast countries available through sagemaker canvas ui yet but assume they ll get there at some point 🤷♂️ something to be aware of when updating the comments | 0 |
242,034 | 20,190,045,028 | IssuesEvent | 2022-02-11 03:59:12 | bitngu/LStore | https://api.github.com/repos/bitngu/LStore | closed | Select an existing record from the table | Needs Final Testing | The select function returns the specified set of
columns from the record with the given key (if available). | 1.0 | Select an existing record from the table - The select function returns the specified set of
columns from the record with the given key (if available). | test | select an existing record from the table the select function returns the specified set of columns from the record with the given key if available | 1 |
311,677 | 26,804,844,414 | IssuesEvent | 2023-02-01 17:28:53 | brave/brave-browser | https://api.github.com/repos/brave/brave-browser | closed | Remove 30 day history from `unconnected` and `grandfather unverified` states | feature/rewards QA/Yes QA/Test-Plan-Specified blocked feature/ads OS/Desktop | Since we don't pay for ads we shouldn't show their history. cc @tmancey
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
#### `unconnected` state
1. Clean profile
2. Enable rewards and ads
3. Open `brave://rewards`
#### `grandfather unverified` state
1. Install 1.47.x
1. Clean profile
1. Enable rewards and ads
1. Upgrade to 1.48.x
1. Open `brave://rewards`
## Actual result:
<!--Please add screenshots if needed-->
`30 day history` is shown
## Expected result:
`30 day history` is not shown
## Reproduces how often:
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
Easily reproduced
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->
Brave | 1.48.132 Chromium: 109.0.5414.87 (Official Build) beta (64-bit)
-- | --
Revision | 2dc18eb511c56e012081b4abc9e38c81c885f7d4-refs/branch-heads/5414@{#1241}
OS | Linux
cc @tmancey @Miyayes @LaurenWags | 1.0 | Remove 30 day history from `unconnected` and `grandfather unverified` states - Since we don't pay for ads we shouldn't show their history. cc @tmancey
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
#### `unconnected` state
1. Clean profile
2. Enable rewards and ads
3. Open `brave://rewards`
#### `grandfather unverified` state
1. Install 1.47.x
1. Clean profile
1. Enable rewards and ads
1. Upgrade to 1.48.x
1. Open `brave://rewards`
## Actual result:
<!--Please add screenshots if needed-->
`30 day history` is shown
## Expected result:
`30 day history` is not shown
## Reproduces how often:
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
Easily reproduced
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->
Brave | 1.48.132 Chromium: 109.0.5414.87 (Official Build) beta (64-bit)
-- | --
Revision | 2dc18eb511c56e012081b4abc9e38c81c885f7d4-refs/branch-heads/5414@{#1241}
OS | Linux
cc @tmancey @Miyayes @LaurenWags | test | remove day history from unconnected and grandfather unverified states since we don t pay for ads we shouldn t show their history cc tmancey steps to reproduce unconnected state clean profile enable rewards and ads open brave rewards grandfather unverified state install x clean profile enable rewards and ads upgrade to x open brave rewards actual result day history is shown expected result day history is not shown reproduces how often easily reproduced brave version brave version info brave chromium official build beta bit revision refs branch heads os linux cc tmancey miyayes laurenwags | 1 |
255,542 | 8,125,325,389 | IssuesEvent | 2018-08-16 20:33:14 | mozilla/addons-frontend | https://api.github.com/repos/mozilla/addons-frontend | closed | Add an underline to the links to "all reviews" from the AddonMeta component | component: add-on ratings priority: p3 size: S | The number of reviews and the title that reads "Reviews" was turned into a link in the `AddonMeta` component, with the number being displayed in black text and the title in grey text. To make these more obviously links, we should also display an underline for them. Both of them should become blue in colour when hovered over. | 1.0 | Add an underline to the links to "all reviews" from the AddonMeta component - The number of reviews and the title that reads "Reviews" was turned into a link in the `AddonMeta` component, with the number being displayed in black text and the title in grey text. To make these more obviously links, we should also display an underline for them. Both of them should become blue in colour when hovered over. | non_test | add an underline to the links to all reviews from the addonmeta component the number of reviews and the title that reads reviews was turned into a link in the addonmeta component with the number being displayed in black text and the title in grey text to make these more obviously links we should also display an underline for them both of them should become blue in colour when hovered over | 0 |
216,039 | 7,300,599,812 | IssuesEvent | 2018-02-27 00:30:25 | Microsoft/AdaptiveCards | https://api.github.com/repos/Microsoft/AdaptiveCards | opened | Refactor renderCard() | Area-Renderers Bug Platform-Android Priority-Now | API renderCard() refactor to return RenderedAdaptive -> Card, View, GathreInputs(), Warnings | 1.0 | Refactor renderCard() - API renderCard() refactor to return RenderedAdaptive -> Card, View, GathreInputs(), Warnings | non_test | refactor rendercard api rendercard refactor to return renderedadaptive card view gathreinputs warnings | 0 |
142,302 | 5,468,464,374 | IssuesEvent | 2017-03-10 06:14:01 | CS2103JAN2017-T09-B4/main | https://api.github.com/repos/CS2103JAN2017-T09-B4/main | opened | Attach related documents and links to my tasks | priority.medium type.story | Conveniently access documents needed for me to work on the tasks | 1.0 | Attach related documents and links to my tasks - Conveniently access documents needed for me to work on the tasks | non_test | attach related documents and links to my tasks conveniently access documents needed for me to work on the tasks | 0 |
36,163 | 9,762,241,914 | IssuesEvent | 2019-06-05 10:48:23 | mapbox/MapboxStatic.swift | https://api.github.com/repos/mapbox/MapboxStatic.swift | opened | Support Swift Package Manager | build | Add a Package.swift file so that [Swift Package Manager](https://swift.org/package-manager/) can incorporate this library into a project.
/ref mapbox/MapboxDirections.swift#234
/cc @mapbox/maps-ios @frederoni | 1.0 | Support Swift Package Manager - Add a Package.swift file so that [Swift Package Manager](https://swift.org/package-manager/) can incorporate this library into a project.
/ref mapbox/MapboxDirections.swift#234
/cc @mapbox/maps-ios @frederoni | non_test | support swift package manager add a package swift file so that can incorporate this library into a project ref mapbox mapboxdirections swift cc mapbox maps ios frederoni | 0 |
361,899 | 25,353,380,425 | IssuesEvent | 2022-11-20 02:42:55 | frodeheg/no.sparegris | https://api.github.com/repos/frodeheg/no.sparegris | closed | "Override device" flow card lists out-of-date device/zone names | documentation | I renamed most of my devices and zones (standardized on English).
When updating the existing "override device" flow cards, they listed the old names.
After restarting PB, all was OK again. | 1.0 | "Override device" flow card lists out-of-date device/zone names - I renamed most of my devices and zones (standardized on English).
When updating the existing "override device" flow cards, they listed the old names.
After restarting PB, all was OK again. | non_test | override device flow card lists out of date device zone names i renamed most of my devices and zones standardized on english when updating the existing override device flow cards they listed the old names after restarting pb all was ok again | 0 |
277,161 | 24,053,795,671 | IssuesEvent | 2022-09-16 14:58:16 | wazuh/wazuh | https://api.github.com/repos/wazuh/wazuh | closed | Release 4.3.8 - Release Candidate 1 - Register | release test/4.3.8 | ### Packages tests metrics information
| | |
|---------------------------------|--------------------------------------------|
| **Main release candidate issue** | #14827|
| **Main packages metrics issue** | #14862 |
| **Version** | 4.3.8 |
| **Release candidate #** | RC1 |
| **Tag** | https://github.com/wazuh/wazuh/tree/v4.3.8-rc1 |
---
| Test | AMD64 Build |
| -- | -- |
| Tier | https://ci.wazuh.info/job/Test_registration_tier/ |
---
| System | Test Result |
| :-- | :--: |
| CentOS 8 | 🟢 |
| CentOS 7 | 🟢 |
| CentOS 6 | 🟢 |
| CentOS 5 | 🟢 |
| Debian 10 | 🟢 |
| Debian 9 | 🟢 |
| Debian 8 | 🟢 |
| Debian 7 | 🟢 |
| Fedora 32 | 🟢 |
| Fedora 31 | 🟢 |
| Ubuntu Focal | 🟢 |
| Ubuntu Bionic | 🟢 |
| Ubuntu Xenial | 🟢 |
| Ubuntu Precise | 🟢 |
| Ubuntu Trusty | 🟢 |
| Amazon Linux 1 | 🟢 |
| Amazon Linux 2 | 🟢
| Oracle Linux 6 | 🟢 |
| Oracle Linux 7 | 🟢 |
| Oracle Linux 8 | 🟢 |
| OpenSuse Tumbleweed | 🟢 |
| Redhat 6 | 🟢 |
| Redhat 7 | 🟢 |
| Redhat 8 | 🟢 |
Legend:
Pending/In progress: 🕐
Test not launched: ⚫
Test failed: 🔴
Test success: 🟢
Need review: 🟡 | 1.0 | Release 4.3.8 - Release Candidate 1 - Register - ### Packages tests metrics information
| | |
|---------------------------------|--------------------------------------------|
| **Main release candidate issue** | #14827|
| **Main packages metrics issue** | #14862 |
| **Version** | 4.3.8 |
| **Release candidate #** | RC1 |
| **Tag** | https://github.com/wazuh/wazuh/tree/v4.3.8-rc1 |
---
| Test | AMD64 Build |
| -- | -- |
| Tier | https://ci.wazuh.info/job/Test_registration_tier/ |
---
| System | Test Result |
| :-- | :--: |
| CentOS 8 | 🟢 |
| CentOS 7 | 🟢 |
| CentOS 6 | 🟢 |
| CentOS 5 | 🟢 |
| Debian 10 | 🟢 |
| Debian 9 | 🟢 |
| Debian 8 | 🟢 |
| Debian 7 | 🟢 |
| Fedora 32 | 🟢 |
| Fedora 31 | 🟢 |
| Ubuntu Focal | 🟢 |
| Ubuntu Bionic | 🟢 |
| Ubuntu Xenial | 🟢 |
| Ubuntu Precise | 🟢 |
| Ubuntu Trusty | 🟢 |
| Amazon Linux 1 | 🟢 |
| Amazon Linux 2 | 🟢
| Oracle Linux 6 | 🟢 |
| Oracle Linux 7 | 🟢 |
| Oracle Linux 8 | 🟢 |
| OpenSuse Tumbleweed | 🟢 |
| Redhat 6 | 🟢 |
| Redhat 7 | 🟢 |
| Redhat 8 | 🟢 |
Legend:
Pending/In progress: 🕐
Test not launched: ⚫
Test failed: 🔴
Test success: 🟢
Need review: 🟡 | test | release release candidate register packages tests metrics information main release candidate issue main packages metrics issue version release candidate tag test build tier system test result centos 🟢 centos 🟢 centos 🟢 centos 🟢 debian 🟢 debian 🟢 debian 🟢 debian 🟢 fedora 🟢 fedora 🟢 ubuntu focal 🟢 ubuntu bionic 🟢 ubuntu xenial 🟢 ubuntu precise 🟢 ubuntu trusty 🟢 amazon linux 🟢 amazon linux 🟢 oracle linux 🟢 oracle linux 🟢 oracle linux 🟢 opensuse tumbleweed 🟢 redhat 🟢 redhat 🟢 redhat 🟢 legend pending in progress 🕐 test not launched ⚫ test failed 🔴 test success 🟢 need review 🟡 | 1 |
167,826 | 13,044,217,054 | IssuesEvent | 2020-07-29 03:58:41 | celo-org/celo-monorepo | https://api.github.com/repos/celo-org/celo-monorepo | closed | [FLAKEY TEST] protocol-test -> protocol -> Contract: Accounts -> #createAccount -> should fail sometimes | FLAKEY protocol protocol-test | Discovered in PR https://github.com/celo-org/celo-monorepo/pull/4303
Attempt No. 1:
AssertionError: expected 1 to be above 1
at /home/circleci/app/packages/protocol/test/common/accounts.ts:140:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 2:
AssertionError: expected 0 to be above 1
at /home/circleci/app/packages/protocol/test/common/accounts.ts:140:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 3:
AssertionError: expected 2 to be above 2
at /home/circleci/app/packages/protocol/test/common/accounts.ts:142:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 4:
AssertionError: expected 1 to be above 1
at /home/circleci/app/packages/protocol/test/common/accounts.ts:140:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 5:
AssertionError: expected 1 to be above 1
at /home/circleci/app/packages/protocol/test/common/accounts.ts:140:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 6:
AssertionError: expected 1 to be above 2
at /home/circleci/app/packages/protocol/test/common/accounts.ts:142:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 7:
AssertionError: expected 2 to be above 2
at /home/circleci/app/packages/protocol/test/common/accounts.ts:142:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 8:
AssertionError: expected 1 to be above 2
at /home/circleci/app/packages/protocol/test/common/accounts.ts:142:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 9:
AssertionError: expected 0 to be above 1
at /home/circleci/app/packages/protocol/test/common/accounts.ts:140:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 10:
AssertionError: expected 2 to be above 2
at /home/circleci/app/packages/protocol/test/common/accounts.ts:142:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 11:
AssertionError: expected 1 to be above 1
at /home/circleci/app/packages/protocol/test/common/accounts.ts:140:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 12:
AssertionError: expected 1 to be above 1
at /home/circleci/app/packages/protocol/test/common/accounts.ts:140:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 13:
AssertionError: expected 1 to be above 2
at /home/circleci/app/packages/protocol/test/common/accounts.ts:142:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 14:
Test Passed!
| 1.0 | [FLAKEY TEST] protocol-test -> protocol -> Contract: Accounts -> #createAccount -> should fail sometimes - Discovered in PR https://github.com/celo-org/celo-monorepo/pull/4303
Attempt No. 1:
AssertionError: expected 1 to be above 1
at /home/circleci/app/packages/protocol/test/common/accounts.ts:140:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 2:
AssertionError: expected 0 to be above 1
at /home/circleci/app/packages/protocol/test/common/accounts.ts:140:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 3:
AssertionError: expected 2 to be above 2
at /home/circleci/app/packages/protocol/test/common/accounts.ts:142:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 4:
AssertionError: expected 1 to be above 1
at /home/circleci/app/packages/protocol/test/common/accounts.ts:140:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 5:
AssertionError: expected 1 to be above 1
at /home/circleci/app/packages/protocol/test/common/accounts.ts:140:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 6:
AssertionError: expected 1 to be above 2
at /home/circleci/app/packages/protocol/test/common/accounts.ts:142:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 7:
AssertionError: expected 2 to be above 2
at /home/circleci/app/packages/protocol/test/common/accounts.ts:142:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 8:
AssertionError: expected 1 to be above 2
at /home/circleci/app/packages/protocol/test/common/accounts.ts:142:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 9:
AssertionError: expected 0 to be above 1
at /home/circleci/app/packages/protocol/test/common/accounts.ts:140:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 10:
AssertionError: expected 2 to be above 2
at /home/circleci/app/packages/protocol/test/common/accounts.ts:142:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 11:
AssertionError: expected 1 to be above 1
at /home/circleci/app/packages/protocol/test/common/accounts.ts:140:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 12:
AssertionError: expected 1 to be above 1
at /home/circleci/app/packages/protocol/test/common/accounts.ts:140:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 13:
AssertionError: expected 1 to be above 2
at /home/circleci/app/packages/protocol/test/common/accounts.ts:142:24
at step (/home/circleci/app/packages/protocol/test/common/accounts.ts:33:23)
at Object.next (/home/circleci/app/packages/protocol/test/common/accounts.ts:14:53)
at /home/circleci/app/packages/protocol/test/common/accounts.ts:8:71
at new Promise (<anonymous>)
at __awaiter (/home/circleci/app/packages/protocol/test/common/accounts.ts:4:12)
at Context.<anonymous> (/home/circleci/app/packages/protocol/test/common/accounts.ts:136:58)
at callFn (/home/circleci/app/node_modules/mocha/lib/runnable.js:387:21)
at Test.Runnable.run (/home/circleci/app/node_modules/mocha/lib/runnable.js:379:7)
at Runner.runTest (/home/circleci/app/node_modules/mocha/lib/runner.js:535:10)
at /home/circleci/app/node_modules/mocha/lib/runner.js:653:12
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:447:14)
at /home/circleci/app/node_modules/mocha/lib/runner.js:457:7
at next (/home/circleci/app/node_modules/mocha/lib/runner.js:362:14)
at Immediate.<anonymous> (/home/circleci/app/node_modules/mocha/lib/runner.js:425:5)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)
Attempt No. 14:
Test Passed!
| test | protocol test protocol contract accounts createaccount should fail sometimes discovered in pr attempt no assertionerror expected to be above at home circleci app packages protocol test common accounts ts at step home circleci app packages protocol test common accounts ts at object next home circleci app packages protocol test common accounts ts at home circleci app packages protocol test common accounts ts at new promise at awaiter home circleci app packages protocol test common accounts ts at context home circleci app packages protocol test common accounts ts at callfn home circleci app node modules mocha lib runnable js at test runnable run home circleci app node modules mocha lib runnable js at runner runtest home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at immediate home circleci app node modules mocha lib runner js at runcallback timers js at tryonimmediate timers js at processimmediate timers js attempt no assertionerror expected to be above at home circleci app packages protocol test common accounts ts at step home circleci app packages protocol test common accounts ts at object next home circleci app packages protocol test common accounts ts at home circleci app packages protocol test common accounts ts at new promise at awaiter home circleci app packages protocol test common accounts ts at context home circleci app packages protocol test common accounts ts at callfn home circleci app node modules mocha lib runnable js at test runnable run home circleci app node modules mocha lib runnable js at runner runtest home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at immediate home circleci app node modules mocha lib runner js at runcallback timers js at tryonimmediate timers js at processimmediate timers js attempt no assertionerror expected to be above at home circleci app packages protocol test common accounts ts at step home circleci app packages protocol test common accounts ts at object next home circleci app packages protocol test common accounts ts at home circleci app packages protocol test common accounts ts at new promise at awaiter home circleci app packages protocol test common accounts ts at context home circleci app packages protocol test common accounts ts at callfn home circleci app node modules mocha lib runnable js at test runnable run home circleci app node modules mocha lib runnable js at runner runtest home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at immediate home circleci app node modules mocha lib runner js at runcallback timers js at tryonimmediate timers js at processimmediate timers js attempt no assertionerror expected to be above at home circleci app packages protocol test common accounts ts at step home circleci app packages protocol test common accounts ts at object next home circleci app packages protocol test common accounts ts at home circleci app packages protocol test common accounts ts at new promise at awaiter home circleci app packages protocol test common accounts ts at context home circleci app packages protocol test common accounts ts at callfn home circleci app node modules mocha lib runnable js at test runnable run home circleci app node modules mocha lib runnable js at runner runtest home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at immediate home circleci app node modules mocha lib runner js at runcallback timers js at tryonimmediate timers js at processimmediate timers js attempt no assertionerror expected to be above at home circleci app packages protocol test common accounts ts at step home circleci app packages protocol test common accounts ts at object next home circleci app packages protocol test common accounts ts at home circleci app packages protocol test common accounts ts at new promise at awaiter home circleci app packages protocol test common accounts ts at context home circleci app packages protocol test common accounts ts at callfn home circleci app node modules mocha lib runnable js at test runnable run home circleci app node modules mocha lib runnable js at runner runtest home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at immediate home circleci app node modules mocha lib runner js at runcallback timers js at tryonimmediate timers js at processimmediate timers js attempt no assertionerror expected to be above at home circleci app packages protocol test common accounts ts at step home circleci app packages protocol test common accounts ts at object next home circleci app packages protocol test common accounts ts at home circleci app packages protocol test common accounts ts at new promise at awaiter home circleci app packages protocol test common accounts ts at context home circleci app packages protocol test common accounts ts at callfn home circleci app node modules mocha lib runnable js at test runnable run home circleci app node modules mocha lib runnable js at runner runtest home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at immediate home circleci app node modules mocha lib runner js at runcallback timers js at tryonimmediate timers js at processimmediate timers js attempt no assertionerror expected to be above at home circleci app packages protocol test common accounts ts at step home circleci app packages protocol test common accounts ts at object next home circleci app packages protocol test common accounts ts at home circleci app packages protocol test common accounts ts at new promise at awaiter home circleci app packages protocol test common accounts ts at context home circleci app packages protocol test common accounts ts at callfn home circleci app node modules mocha lib runnable js at test runnable run home circleci app node modules mocha lib runnable js at runner runtest home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at immediate home circleci app node modules mocha lib runner js at runcallback timers js at tryonimmediate timers js at processimmediate timers js attempt no assertionerror expected to be above at home circleci app packages protocol test common accounts ts at step home circleci app packages protocol test common accounts ts at object next home circleci app packages protocol test common accounts ts at home circleci app packages protocol test common accounts ts at new promise at awaiter home circleci app packages protocol test common accounts ts at context home circleci app packages protocol test common accounts ts at callfn home circleci app node modules mocha lib runnable js at test runnable run home circleci app node modules mocha lib runnable js at runner runtest home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at immediate home circleci app node modules mocha lib runner js at runcallback timers js at tryonimmediate timers js at processimmediate timers js attempt no assertionerror expected to be above at home circleci app packages protocol test common accounts ts at step home circleci app packages protocol test common accounts ts at object next home circleci app packages protocol test common accounts ts at home circleci app packages protocol test common accounts ts at new promise at awaiter home circleci app packages protocol test common accounts ts at context home circleci app packages protocol test common accounts ts at callfn home circleci app node modules mocha lib runnable js at test runnable run home circleci app node modules mocha lib runnable js at runner runtest home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at immediate home circleci app node modules mocha lib runner js at runcallback timers js at tryonimmediate timers js at processimmediate timers js attempt no assertionerror expected to be above at home circleci app packages protocol test common accounts ts at step home circleci app packages protocol test common accounts ts at object next home circleci app packages protocol test common accounts ts at home circleci app packages protocol test common accounts ts at new promise at awaiter home circleci app packages protocol test common accounts ts at context home circleci app packages protocol test common accounts ts at callfn home circleci app node modules mocha lib runnable js at test runnable run home circleci app node modules mocha lib runnable js at runner runtest home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at immediate home circleci app node modules mocha lib runner js at runcallback timers js at tryonimmediate timers js at processimmediate timers js attempt no assertionerror expected to be above at home circleci app packages protocol test common accounts ts at step home circleci app packages protocol test common accounts ts at object next home circleci app packages protocol test common accounts ts at home circleci app packages protocol test common accounts ts at new promise at awaiter home circleci app packages protocol test common accounts ts at context home circleci app packages protocol test common accounts ts at callfn home circleci app node modules mocha lib runnable js at test runnable run home circleci app node modules mocha lib runnable js at runner runtest home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at immediate home circleci app node modules mocha lib runner js at runcallback timers js at tryonimmediate timers js at processimmediate timers js attempt no assertionerror expected to be above at home circleci app packages protocol test common accounts ts at step home circleci app packages protocol test common accounts ts at object next home circleci app packages protocol test common accounts ts at home circleci app packages protocol test common accounts ts at new promise at awaiter home circleci app packages protocol test common accounts ts at context home circleci app packages protocol test common accounts ts at callfn home circleci app node modules mocha lib runnable js at test runnable run home circleci app node modules mocha lib runnable js at runner runtest home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at immediate home circleci app node modules mocha lib runner js at runcallback timers js at tryonimmediate timers js at processimmediate timers js attempt no assertionerror expected to be above at home circleci app packages protocol test common accounts ts at step home circleci app packages protocol test common accounts ts at object next home circleci app packages protocol test common accounts ts at home circleci app packages protocol test common accounts ts at new promise at awaiter home circleci app packages protocol test common accounts ts at context home circleci app packages protocol test common accounts ts at callfn home circleci app node modules mocha lib runnable js at test runnable run home circleci app node modules mocha lib runnable js at runner runtest home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at home circleci app node modules mocha lib runner js at next home circleci app node modules mocha lib runner js at immediate home circleci app node modules mocha lib runner js at runcallback timers js at tryonimmediate timers js at processimmediate timers js attempt no test passed | 1 |
68,461 | 7,097,269,956 | IssuesEvent | 2018-01-14 17:29:05 | OAButton/discussion | https://api.github.com/repos/OAButton/discussion | opened | Workflow for talking to OABottan | 1. Chatbot 2. Enhancement 3. Blocked: Dev 3. Blocked: Test | * m.me/openaccessbutton is the link that will take you direct to the bot.
* https://thenounproject.com/search/?q=chat&i=376471 is probably an OK icon
Can display these on mobile where folks normally see calls to download | 1.0 | Workflow for talking to OABottan - * m.me/openaccessbutton is the link that will take you direct to the bot.
* https://thenounproject.com/search/?q=chat&i=376471 is probably an OK icon
Can display these on mobile where folks normally see calls to download | test | workflow for talking to oabottan m me openaccessbutton is the link that will take you direct to the bot is probably an ok icon can display these on mobile where folks normally see calls to download | 1 |
282,348 | 24,469,793,209 | IssuesEvent | 2022-10-07 18:35:51 | omeka/omeka-s | https://api.github.com/repos/omeka/omeka-s | closed | Testing: Search by resource ID | Testing | On the develop branch users can now search by resource (item, item set, media) ID. To test this, go to the item advanced search page and under "Search by ID" enter an existing item ID. After submitting the form the result should only include the item you entered. Now enter more than one ID, separated by commas. The results should include every item you entered. Now try the same for the item set and media advanced searches. | 1.0 | Testing: Search by resource ID - On the develop branch users can now search by resource (item, item set, media) ID. To test this, go to the item advanced search page and under "Search by ID" enter an existing item ID. After submitting the form the result should only include the item you entered. Now enter more than one ID, separated by commas. The results should include every item you entered. Now try the same for the item set and media advanced searches. | test | testing search by resource id on the develop branch users can now search by resource item item set media id to test this go to the item advanced search page and under search by id enter an existing item id after submitting the form the result should only include the item you entered now enter more than one id separated by commas the results should include every item you entered now try the same for the item set and media advanced searches | 1 |
170,967 | 14,273,767,604 | IssuesEvent | 2020-11-21 23:29:55 | bee-queue/arena | https://api.github.com/repos/bee-queue/arena | closed | document bullmq support | bullmq documentation question | ## Description
I was trying to use `bull-arena` for my project which uses `bullmq`. The project is written in typescript.
Here's what I am trying to do
```
import Arena from "bull-arena";
import { Queue } from "bullmq";
const arena = Arena({
Bull: Queue,
queues: [
{
name: "link-account-queue",
hostId: "Link Account Queue",
redis: {
host: REDIS_HOST,
port: REDIS_PORT
}
}
]
});
```
Typescript throws an error saying
```
Type 'typeof Queue' is not assignable to type '{ <T = any>(queueName: string, opts?: QueueOptions): Queue<T>; <T = any>(queueName: string, url: string, opts?: QueueOptions): Queue<T>; new <T = any>(queueName: string, opts?: QueueOptions): Queue<...>; new <T = any>(queueName: string, url: string, opts?: QueueOptions): Queue<...>; }'.
Type 'typeof Queue' provides no match for the signature '<T = any>(queueName: string, opts?: QueueOptions): Queue<T>'
```
If i force the type to never, I can start the application but I get the following error when opening the arena ui.
```
TypeError: queue.client.info is not a function
```
## Question
- Does `bull-arena` support `bullmq` with `typescript`?
- If so, what am I doing wrong and what are the workarounds?
Can someone help me out. Thanks in advance | 1.0 | document bullmq support - ## Description
I was trying to use `bull-arena` for my project which uses `bullmq`. The project is written in typescript.
Here's what I am trying to do
```
import Arena from "bull-arena";
import { Queue } from "bullmq";
const arena = Arena({
Bull: Queue,
queues: [
{
name: "link-account-queue",
hostId: "Link Account Queue",
redis: {
host: REDIS_HOST,
port: REDIS_PORT
}
}
]
});
```
Typescript throws an error saying
```
Type 'typeof Queue' is not assignable to type '{ <T = any>(queueName: string, opts?: QueueOptions): Queue<T>; <T = any>(queueName: string, url: string, opts?: QueueOptions): Queue<T>; new <T = any>(queueName: string, opts?: QueueOptions): Queue<...>; new <T = any>(queueName: string, url: string, opts?: QueueOptions): Queue<...>; }'.
Type 'typeof Queue' provides no match for the signature '<T = any>(queueName: string, opts?: QueueOptions): Queue<T>'
```
If i force the type to never, I can start the application but I get the following error when opening the arena ui.
```
TypeError: queue.client.info is not a function
```
## Question
- Does `bull-arena` support `bullmq` with `typescript`?
- If so, what am I doing wrong and what are the workarounds?
Can someone help me out. Thanks in advance | non_test | document bullmq support description i was trying to use bull arena for my project which uses bullmq the project is written in typescript here s what i am trying to do import arena from bull arena import queue from bullmq const arena arena bull queue queues name link account queue hostid link account queue redis host redis host port redis port typescript throws an error saying type typeof queue is not assignable to type queuename string opts queueoptions queue queuename string url string opts queueoptions queue new queuename string opts queueoptions queue new queuename string url string opts queueoptions queue type typeof queue provides no match for the signature queuename string opts queueoptions queue if i force the type to never i can start the application but i get the following error when opening the arena ui typeerror queue client info is not a function question does bull arena support bullmq with typescript if so what am i doing wrong and what are the workarounds can someone help me out thanks in advance | 0 |
285,918 | 21,558,386,727 | IssuesEvent | 2022-04-30 20:20:14 | godot-escoria/escoria-issues | https://api.github.com/repos/godot-escoria/escoria-issues | closed | ESCItems with TextureRect are ignored when the mouse moves over the TextureRect | documentation | Hi, I'm a newbie so I hope I'm reporting a real thing.
In Escoria Step-by-step Guide, ESCItem nodes aren't working as stated in Making The Player Walk Behind Items and Creating An Inventory sections; it is directed to add TextureRect nodes for the walk behind (barrel) and inventory (mug) items but by doing so, CollisionShape2D/Polygon2D areas (where they overlap with the texture images) can't be clicked or interacted when the scene played but changing the TextureRect setting to Mouse>Filter>Ignore or using a Sprite node instead of a TextureRect solved the issue for me and ESCItems worked as stated in the guide. Before that I had monkeyed with z-indexes, area nodes' orders on object trees, and had tried different interaction methods (verbs) in associated ESC script file etc. with no avail, it seemed the problem was irrelevant to all of these.
Steps to reproduce the behavior:
1. Add an ESCItem node to a new or a room scene.
2. Add TextureRect node to ESCItem and assign an image to texture.
3. Add CollisionShape2D/Polygon2D node to ESCItem.
4. Adjust the collision area as necessary to cover the item's interactable zone.
5. Add some text to Tooltip Name of ESCItem to be able to check later if the item would interact with the mouse cursor or not.
6. If you have added item as a separate scene, instance it in the room scene.
7. Add ESCLocation to ESCItem in the room scene and place its crosshair in the walkable zone just in case (in fact it doesn't matter if you don't, also it isn't mentioned in the guide).
8. Play the room scene and see the collision area of the ESCItem is not clickable or interactable where it overlaps with its texture image. If you use Simple Mouse UI, you see neither you can cycle through the interaction types by right clicking the item nor left clicking does something, even tooltip doesn't show up when hovering over the texture area. Collision area which by any chance doesn't overlap with the ESCItem's texture image's rectangle can be clicked or interacted in a way but it still prevents the item to be used in some means like as an inventory item.
**Expected behavior**
ESCItem nodes should work properly if we follow the Step-by-step Guide.
**Versions**
* Escoria: escoria-game-template-4.0.0-alpha.128
* Assetlibs: Simple Dialogs 4.0.0-alpha.16, Simple Mouse UI 4.0.0-alpha.22
* Godot: v3.4.4-stable_win64, v3.5-beta4_win64
**Additional context**
Related guide pages:
1. https://docs.escoria-framework.org/en/devel/getting_started/step_by_step/5_adding_items.html#making-the-player-walk-behind-items
2. https://docs.escoria-framework.org/en/devel/getting_started/step_by_step/6_handling_inventory.html#creating-an-inventory-item
Thanks for your time in advance.
| 1.0 | ESCItems with TextureRect are ignored when the mouse moves over the TextureRect - Hi, I'm a newbie so I hope I'm reporting a real thing.
In Escoria Step-by-step Guide, ESCItem nodes aren't working as stated in Making The Player Walk Behind Items and Creating An Inventory sections; it is directed to add TextureRect nodes for the walk behind (barrel) and inventory (mug) items but by doing so, CollisionShape2D/Polygon2D areas (where they overlap with the texture images) can't be clicked or interacted when the scene played but changing the TextureRect setting to Mouse>Filter>Ignore or using a Sprite node instead of a TextureRect solved the issue for me and ESCItems worked as stated in the guide. Before that I had monkeyed with z-indexes, area nodes' orders on object trees, and had tried different interaction methods (verbs) in associated ESC script file etc. with no avail, it seemed the problem was irrelevant to all of these.
Steps to reproduce the behavior:
1. Add an ESCItem node to a new or a room scene.
2. Add TextureRect node to ESCItem and assign an image to texture.
3. Add CollisionShape2D/Polygon2D node to ESCItem.
4. Adjust the collision area as necessary to cover the item's interactable zone.
5. Add some text to Tooltip Name of ESCItem to be able to check later if the item would interact with the mouse cursor or not.
6. If you have added item as a separate scene, instance it in the room scene.
7. Add ESCLocation to ESCItem in the room scene and place its crosshair in the walkable zone just in case (in fact it doesn't matter if you don't, also it isn't mentioned in the guide).
8. Play the room scene and see the collision area of the ESCItem is not clickable or interactable where it overlaps with its texture image. If you use Simple Mouse UI, you see neither you can cycle through the interaction types by right clicking the item nor left clicking does something, even tooltip doesn't show up when hovering over the texture area. Collision area which by any chance doesn't overlap with the ESCItem's texture image's rectangle can be clicked or interacted in a way but it still prevents the item to be used in some means like as an inventory item.
**Expected behavior**
ESCItem nodes should work properly if we follow the Step-by-step Guide.
**Versions**
* Escoria: escoria-game-template-4.0.0-alpha.128
* Assetlibs: Simple Dialogs 4.0.0-alpha.16, Simple Mouse UI 4.0.0-alpha.22
* Godot: v3.4.4-stable_win64, v3.5-beta4_win64
**Additional context**
Related guide pages:
1. https://docs.escoria-framework.org/en/devel/getting_started/step_by_step/5_adding_items.html#making-the-player-walk-behind-items
2. https://docs.escoria-framework.org/en/devel/getting_started/step_by_step/6_handling_inventory.html#creating-an-inventory-item
Thanks for your time in advance.
| non_test | escitems with texturerect are ignored when the mouse moves over the texturerect hi i m a newbie so i hope i m reporting a real thing in escoria step by step guide escitem nodes aren t working as stated in making the player walk behind items and creating an inventory sections it is directed to add texturerect nodes for the walk behind barrel and inventory mug items but by doing so areas where they overlap with the texture images can t be clicked or interacted when the scene played but changing the texturerect setting to mouse filter ignore or using a sprite node instead of a texturerect solved the issue for me and escitems worked as stated in the guide before that i had monkeyed with z indexes area nodes orders on object trees and had tried different interaction methods verbs in associated esc script file etc with no avail it seemed the problem was irrelevant to all of these steps to reproduce the behavior add an escitem node to a new or a room scene add texturerect node to escitem and assign an image to texture add node to escitem adjust the collision area as necessary to cover the item s interactable zone add some text to tooltip name of escitem to be able to check later if the item would interact with the mouse cursor or not if you have added item as a separate scene instance it in the room scene add esclocation to escitem in the room scene and place its crosshair in the walkable zone just in case in fact it doesn t matter if you don t also it isn t mentioned in the guide play the room scene and see the collision area of the escitem is not clickable or interactable where it overlaps with its texture image if you use simple mouse ui you see neither you can cycle through the interaction types by right clicking the item nor left clicking does something even tooltip doesn t show up when hovering over the texture area collision area which by any chance doesn t overlap with the escitem s texture image s rectangle can be clicked or interacted in a way but it still prevents the item to be used in some means like as an inventory item expected behavior escitem nodes should work properly if we follow the step by step guide versions escoria escoria game template alpha assetlibs simple dialogs alpha simple mouse ui alpha godot stable additional context related guide pages thanks for your time in advance | 0 |
323,547 | 27,734,303,835 | IssuesEvent | 2023-03-15 10:10:32 | facebook/react-native | https://api.github.com/repos/facebook/react-native | closed | Can't resolve '../Utilities/Platform' | Needs: Triage :mag: Needs: Verify on Latest Version Type: Expo | ### Description
I reported this error when running `expo start --web` using `expo`，How can I solve it? please!
### React Native Version
0.70.5
### Output of `npx react-native info`
Module not found: Can't resolve '../Utilities/Platform'
23 | const PixelRatio = require('../Utilities/PixelRatio');
24 | const {pickScale} = require('./AssetUtils');
> 25 | const Platform = require('../Utilities/Platform');
| ^
26 |
27 | const invariant = require('invariant');
### Steps to reproduce
expo start --web
### Snack, code example, screenshot, or link to a repository
| 1.0 | Can't resolve '../Utilities/Platform' - ### Description
I reported this error when running `expo start --web` using `expo`，How can I solve it? please!
### React Native Version
0.70.5
### Output of `npx react-native info`
Module not found: Can't resolve '../Utilities/Platform'
23 | const PixelRatio = require('../Utilities/PixelRatio');
24 | const {pickScale} = require('./AssetUtils');
> 25 | const Platform = require('../Utilities/Platform');
| ^
26 |
27 | const invariant = require('invariant');
### Steps to reproduce
expo start --web
### Snack, code example, screenshot, or link to a repository
| test | can t resolve utilities platform description i reported this error when running expo start web using expo ，how can i solve it please react native version output of npx react native info module not found can t resolve utilities platform const pixelratio require utilities pixelratio const pickscale require assetutils const platform require utilities platform const invariant require invariant steps to reproduce expo start web snack code example screenshot or link to a repository | 1 |
182,520 | 21,665,366,144 | IssuesEvent | 2022-05-07 04:40:20 | temporalio/samples-typescript | https://api.github.com/repos/temporalio/samples-typescript | closed | axios-0.21.1.tgz: 2 vulnerabilities (highest severity is: 8.8) - autoclosed | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>axios-0.21.1.tgz</b></p></summary>
<p>Promise based HTTP client for the browser and node.js</p>
<p>Library home page: <a href="https://registry.npmjs.org/axios/-/axios-0.21.1.tgz">https://registry.npmjs.org/axios/-/axios-0.21.1.tgz</a></p>
<p>Path to dependency file: /patching-api/package.json</p>
<p>Path to vulnerable library: /patching-api/node_modules/axios/package.json,/activities-examples/node_modules/axios/package.json</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/temporalio/samples-typescript/commit/3b9bae980eb794fab08e5addef96e9ace5acb327">3b9bae980eb794fab08e5addef96e9ace5acb327</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2022-1214](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-1214) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.8 | axios-0.21.1.tgz | Direct | 0.26.0 | ✅ |
| [CVE-2021-3749](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3749) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | axios-0.21.1.tgz | Direct | 0.21.2 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-1214</summary>
### Vulnerable Library - <b>axios-0.21.1.tgz</b></p>
<p>Promise based HTTP client for the browser and node.js</p>
<p>Library home page: <a href="https://registry.npmjs.org/axios/-/axios-0.21.1.tgz">https://registry.npmjs.org/axios/-/axios-0.21.1.tgz</a></p>
<p>Path to dependency file: /patching-api/package.json</p>
<p>Path to vulnerable library: /patching-api/node_modules/axios/package.json,/activities-examples/node_modules/axios/package.json</p>
<p>
Dependency Hierarchy:
- :x: **axios-0.21.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/temporalio/samples-typescript/commit/3b9bae980eb794fab08e5addef96e9ace5acb327">3b9bae980eb794fab08e5addef96e9ace5acb327</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository axios/axios prior to 0.26.
<p>Publish Date: 2022-05-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-1214>CVE-2022-1214</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://huntr.dev/bounties/ef7b4ab6-a3f6-4268-a21a-e7104d344607/">https://huntr.dev/bounties/ef7b4ab6-a3f6-4268-a21a-e7104d344607/</a></p>
<p>Release Date: 2022-05-03</p>
<p>Fix Resolution: 0.26.0</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-3749</summary>
### Vulnerable Library - <b>axios-0.21.1.tgz</b></p>
<p>Promise based HTTP client for the browser and node.js</p>
<p>Library home page: <a href="https://registry.npmjs.org/axios/-/axios-0.21.1.tgz">https://registry.npmjs.org/axios/-/axios-0.21.1.tgz</a></p>
<p>Path to dependency file: /patching-api/package.json</p>
<p>Path to vulnerable library: /patching-api/node_modules/axios/package.json,/activities-examples/node_modules/axios/package.json</p>
<p>
Dependency Hierarchy:
- :x: **axios-0.21.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/temporalio/samples-typescript/commit/3b9bae980eb794fab08e5addef96e9ace5acb327">3b9bae980eb794fab08e5addef96e9ace5acb327</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
axios is vulnerable to Inefficient Regular Expression Complexity
<p>Publish Date: 2021-08-31
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3749>CVE-2021-3749</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://huntr.dev/bounties/1e8f07fc-c384-4ff9-8498-0690de2e8c31/">https://huntr.dev/bounties/1e8f07fc-c384-4ff9-8498-0690de2e8c31/</a></p>
<p>Release Date: 2021-08-31</p>
<p>Fix Resolution: 0.21.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>
<!-- <REMEDIATE>[{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"axios","packageVersion":"0.21.1","packageFilePaths":["/patching-api/package.json"],"isTransitiveDependency":false,"dependencyTree":"axios:0.21.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.26.0","isBinary":false}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2022-1214","vulnerabilityDetails":"Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository axios/axios prior to 0.26.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-1214","cvss3Severity":"high","cvss3Score":"8.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"Low","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"axios","packageVersion":"0.21.1","packageFilePaths":["/patching-api/package.json"],"isTransitiveDependency":false,"dependencyTree":"axios:0.21.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.21.2","isBinary":false}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2021-3749","vulnerabilityDetails":"axios is vulnerable to Inefficient Regular Expression Complexity","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3749","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}]</REMEDIATE> --> | True | axios-0.21.1.tgz: 2 vulnerabilities (highest severity is: 8.8) - autoclosed - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>axios-0.21.1.tgz</b></p></summary>
<p>Promise based HTTP client for the browser and node.js</p>
<p>Library home page: <a href="https://registry.npmjs.org/axios/-/axios-0.21.1.tgz">https://registry.npmjs.org/axios/-/axios-0.21.1.tgz</a></p>
<p>Path to dependency file: /patching-api/package.json</p>
<p>Path to vulnerable library: /patching-api/node_modules/axios/package.json,/activities-examples/node_modules/axios/package.json</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/temporalio/samples-typescript/commit/3b9bae980eb794fab08e5addef96e9ace5acb327">3b9bae980eb794fab08e5addef96e9ace5acb327</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2022-1214](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-1214) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.8 | axios-0.21.1.tgz | Direct | 0.26.0 | ✅ |
| [CVE-2021-3749](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3749) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | axios-0.21.1.tgz | Direct | 0.21.2 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-1214</summary>
### Vulnerable Library - <b>axios-0.21.1.tgz</b></p>
<p>Promise based HTTP client for the browser and node.js</p>
<p>Library home page: <a href="https://registry.npmjs.org/axios/-/axios-0.21.1.tgz">https://registry.npmjs.org/axios/-/axios-0.21.1.tgz</a></p>
<p>Path to dependency file: /patching-api/package.json</p>
<p>Path to vulnerable library: /patching-api/node_modules/axios/package.json,/activities-examples/node_modules/axios/package.json</p>
<p>
Dependency Hierarchy:
- :x: **axios-0.21.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/temporalio/samples-typescript/commit/3b9bae980eb794fab08e5addef96e9ace5acb327">3b9bae980eb794fab08e5addef96e9ace5acb327</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository axios/axios prior to 0.26.
<p>Publish Date: 2022-05-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-1214>CVE-2022-1214</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://huntr.dev/bounties/ef7b4ab6-a3f6-4268-a21a-e7104d344607/">https://huntr.dev/bounties/ef7b4ab6-a3f6-4268-a21a-e7104d344607/</a></p>
<p>Release Date: 2022-05-03</p>
<p>Fix Resolution: 0.26.0</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-3749</summary>
### Vulnerable Library - <b>axios-0.21.1.tgz</b></p>
<p>Promise based HTTP client for the browser and node.js</p>
<p>Library home page: <a href="https://registry.npmjs.org/axios/-/axios-0.21.1.tgz">https://registry.npmjs.org/axios/-/axios-0.21.1.tgz</a></p>
<p>Path to dependency file: /patching-api/package.json</p>
<p>Path to vulnerable library: /patching-api/node_modules/axios/package.json,/activities-examples/node_modules/axios/package.json</p>
<p>
Dependency Hierarchy:
- :x: **axios-0.21.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/temporalio/samples-typescript/commit/3b9bae980eb794fab08e5addef96e9ace5acb327">3b9bae980eb794fab08e5addef96e9ace5acb327</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
axios is vulnerable to Inefficient Regular Expression Complexity
<p>Publish Date: 2021-08-31
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3749>CVE-2021-3749</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://huntr.dev/bounties/1e8f07fc-c384-4ff9-8498-0690de2e8c31/">https://huntr.dev/bounties/1e8f07fc-c384-4ff9-8498-0690de2e8c31/</a></p>
<p>Release Date: 2021-08-31</p>
<p>Fix Resolution: 0.21.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>
<!-- <REMEDIATE>[{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"axios","packageVersion":"0.21.1","packageFilePaths":["/patching-api/package.json"],"isTransitiveDependency":false,"dependencyTree":"axios:0.21.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.26.0","isBinary":false}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2022-1214","vulnerabilityDetails":"Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository axios/axios prior to 0.26.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-1214","cvss3Severity":"high","cvss3Score":"8.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"Low","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"axios","packageVersion":"0.21.1","packageFilePaths":["/patching-api/package.json"],"isTransitiveDependency":false,"dependencyTree":"axios:0.21.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.21.2","isBinary":false}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2021-3749","vulnerabilityDetails":"axios is vulnerable to Inefficient Regular Expression Complexity","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3749","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}]</REMEDIATE> --> | non_test | axios tgz vulnerabilities highest severity is autoclosed vulnerable library axios tgz promise based http client for the browser and node js library home page a href path to dependency file patching api package json path to vulnerable library patching api node modules axios package json activities examples node modules axios package json found in head commit a href vulnerabilities cve severity cvss dependency type fixed in remediation available high axios tgz direct high axios tgz direct details cve vulnerable library axios tgz promise based http client for the browser and node js library home page a href path to dependency file patching api package json path to vulnerable library patching api node modules axios package json activities examples node modules axios package json dependency hierarchy x axios tgz vulnerable library found in head commit a href found in base branch main vulnerability details exposure of sensitive information to an unauthorized actor in github repository axios axios prior to publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library axios tgz promise based http client for the browser and node js library home page a href path to dependency file patching api package json path to vulnerable library patching api node modules axios package json activities examples node modules axios package json dependency hierarchy x axios tgz vulnerable library found in head commit a href found in base branch main vulnerability details axios is vulnerable to inefficient regular expression complexity 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 rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue istransitivedependency false dependencytree axios isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails exposure of sensitive information to an unauthorized actor in github repository axios axios prior to vulnerabilityurl istransitivedependency false dependencytree axios isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails axios is vulnerable to inefficient regular expression complexity vulnerabilityurl | 0 |
217,056 | 16,834,117,505 | IssuesEvent | 2021-06-18 09:37:36 | elastic/elasticsearch | https://api.github.com/repos/elastic/elasticsearch | closed | [CI] FrozenSearchableSnapshotsIntegTests testCreateAndRestorePartialSearchableSnapshot failing | :Distributed/Snapshot/Restore >test-failure Team:Distributed | This failure happened on my PR. But it is reproducible locally on master.
**Build scan:**
https://gradle-enterprise.elastic.co/s/kg5ihic3hphg6/tests/:x-pack:plugin:searchable-snapshots:internalClusterTest/org.elasticsearch.xpack.searchablesnapshots.FrozenSearchableSnapshotsIntegTests/testCreateAndRestorePartialSearchableSnapshot
**Reproduction line:**
`./gradlew ':x-pack:plugin:searchable-snapshots:internalClusterTest' --tests "org.elasticsearch.xpack.searchablesnapshots.FrozenSearchableSnapshotsIntegTests.testCreateAndRestorePartialSearchableSnapshot" -Dtests.seed=805705F5E3402F57 -Dtests.locale=it -Dtests.timezone=Asia/Aqtobe -Druntime.java=11`
**Applicable branches:**
master
**Reproduces locally?:**
Yes
**Failure history:**
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.xpack.searchablesnapshots.FrozenSearchableSnapshotsIntegTests&tests.test=testCreateAndRestorePartialSearchableSnapshot
**Failure excerpt:**
```
java.lang.AssertionError:
Expected: "false"
but: was "checksum"
at __randomizedtesting.SeedInfo.seed([805705F5E3402F57:F4D0C424DE2701B5]:0)
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
at org.junit.Assert.assertThat(Assert.java:956)
at org.junit.Assert.assertThat(Assert.java:923)
at org.elasticsearch.xpack.searchablesnapshots.FrozenSearchableSnapshotsIntegTests.testCreateAndRestorePartialSearchableSnapshot(FrozenSearchableSnapshotsIntegTests.java:294)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:566)
at com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1758)
at com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:946)
at com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:982)
at com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:996)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:49)
at org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:45)
at org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:48)
at org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:64)
at org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:47)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:375)
at com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:824)
at com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:475)
at com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:955)
at com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:840)
at com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:891)
at com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:902)
at org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:45)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:41)
at com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at org.apache.lucene.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:53)
at org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:47)
at org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:64)
at org.apache.lucene.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:54)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:375)
at com.carrotsearch.randomizedtesting.ThreadLeakControl.lambda$forkTimeoutingTask$0(ThreadLeakControl.java:831)
at java.lang.Thread.run(Thread.java:834)
``` | 1.0 | [CI] FrozenSearchableSnapshotsIntegTests testCreateAndRestorePartialSearchableSnapshot failing - This failure happened on my PR. But it is reproducible locally on master.
**Build scan:**
https://gradle-enterprise.elastic.co/s/kg5ihic3hphg6/tests/:x-pack:plugin:searchable-snapshots:internalClusterTest/org.elasticsearch.xpack.searchablesnapshots.FrozenSearchableSnapshotsIntegTests/testCreateAndRestorePartialSearchableSnapshot
**Reproduction line:**
`./gradlew ':x-pack:plugin:searchable-snapshots:internalClusterTest' --tests "org.elasticsearch.xpack.searchablesnapshots.FrozenSearchableSnapshotsIntegTests.testCreateAndRestorePartialSearchableSnapshot" -Dtests.seed=805705F5E3402F57 -Dtests.locale=it -Dtests.timezone=Asia/Aqtobe -Druntime.java=11`
**Applicable branches:**
master
**Reproduces locally?:**
Yes
**Failure history:**
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.xpack.searchablesnapshots.FrozenSearchableSnapshotsIntegTests&tests.test=testCreateAndRestorePartialSearchableSnapshot
**Failure excerpt:**
```
java.lang.AssertionError:
Expected: "false"
but: was "checksum"
at __randomizedtesting.SeedInfo.seed([805705F5E3402F57:F4D0C424DE2701B5]:0)
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:18)
at org.junit.Assert.assertThat(Assert.java:956)
at org.junit.Assert.assertThat(Assert.java:923)
at org.elasticsearch.xpack.searchablesnapshots.FrozenSearchableSnapshotsIntegTests.testCreateAndRestorePartialSearchableSnapshot(FrozenSearchableSnapshotsIntegTests.java:294)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:566)
at com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1758)
at com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:946)
at com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:982)
at com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:996)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:49)
at org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:45)
at org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:48)
at org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:64)
at org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:47)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:375)
at com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:824)
at com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:475)
at com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:955)
at com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:840)
at com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:891)
at com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:902)
at org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:45)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:41)
at com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at org.apache.lucene.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:53)
at org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:47)
at org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:64)
at org.apache.lucene.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:54)
at com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
at com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:375)
at com.carrotsearch.randomizedtesting.ThreadLeakControl.lambda$forkTimeoutingTask$0(ThreadLeakControl.java:831)
at java.lang.Thread.run(Thread.java:834)
``` | test | frozensearchablesnapshotsintegtests testcreateandrestorepartialsearchablesnapshot failing this failure happened on my pr but it is reproducible locally on master build scan reproduction line gradlew x pack plugin searchable snapshots internalclustertest tests org elasticsearch xpack searchablesnapshots frozensearchablesnapshotsintegtests testcreateandrestorepartialsearchablesnapshot dtests seed dtests locale it dtests timezone asia aqtobe druntime java applicable branches master reproduces locally yes failure history failure excerpt java lang assertionerror expected false but was checksum at randomizedtesting seedinfo seed at org hamcrest matcherassert assertthat matcherassert java at org junit assert assertthat assert java at org junit assert assertthat assert java at org elasticsearch xpack searchablesnapshots frozensearchablesnapshotsintegtests testcreateandrestorepartialsearchablesnapshot frozensearchablesnapshotsintegtests java at jdk internal reflect nativemethodaccessorimpl nativemethodaccessorimpl java at jdk internal reflect nativemethodaccessorimpl invoke nativemethodaccessorimpl java at jdk internal reflect delegatingmethodaccessorimpl invoke delegatingmethodaccessorimpl java at java lang reflect method invoke method java at com carrotsearch randomizedtesting randomizedrunner invoke randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at org apache lucene util testrulesetupteardownchained evaluate testrulesetupteardownchained java at org apache lucene util abstractbeforeafterrule evaluate abstractbeforeafterrule java at org apache lucene util testrulethreadandtestname evaluate testrulethreadandtestname java at org apache lucene util testruleignoreaftermaxfailures evaluate testruleignoreaftermaxfailures java at org apache lucene util testrulemarkfailure evaluate testrulemarkfailure java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at com carrotsearch randomizedtesting threadleakcontrol statementrunner run threadleakcontrol java at com carrotsearch randomizedtesting threadleakcontrol forktimeoutingtask threadleakcontrol java at com carrotsearch randomizedtesting threadleakcontrol evaluate threadleakcontrol java at com carrotsearch randomizedtesting randomizedrunner runsingletest randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at com carrotsearch randomizedtesting randomizedrunner evaluate randomizedrunner java at org apache lucene util abstractbeforeafterrule evaluate abstractbeforeafterrule java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at org apache lucene util testrulestoreclassname evaluate testrulestoreclassname java at com carrotsearch randomizedtesting rules noshadowingoroverridesonmethodsrule evaluate noshadowingoroverridesonmethodsrule java at com carrotsearch randomizedtesting rules noshadowingoroverridesonmethodsrule evaluate noshadowingoroverridesonmethodsrule java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at org apache lucene util testruleassertionsrequired evaluate testruleassertionsrequired java at org apache lucene util testrulemarkfailure evaluate testrulemarkfailure java at org apache lucene util testruleignoreaftermaxfailures evaluate testruleignoreaftermaxfailures java at org apache lucene util testruleignoretestsuites evaluate testruleignoretestsuites java at com carrotsearch randomizedtesting rules statementadapter evaluate statementadapter java at com carrotsearch randomizedtesting threadleakcontrol statementrunner run threadleakcontrol java at com carrotsearch randomizedtesting threadleakcontrol lambda forktimeoutingtask threadleakcontrol java at java lang thread run thread java | 1 |
94,670 | 27,260,956,667 | IssuesEvent | 2023-02-22 14:52:07 | xhochy/fletcher | https://api.github.com/repos/xhochy/fletcher | closed | Add str.endswith | good first issue usecase-202003-qc no-unicode no-regex no-stringbuilder | - ✔️ [pandas function](https://pandas.pydata.org/docs/reference/api/pandas.Series.str.endswith.html#pandas.Series.str.endswith)
- ✔️ [Python function](https://docs.python.org/3/library/stdtypes.html#str.endswith)
- ✔️ simple C++ STL function: https://stackoverflow.com/a/62280289/1689261
- ✔️ no need for a regular expression library
- ✔️ no need for a Unicode database
- ✔️ can pre-compute size, output is a boolean array
Pseudo-Code:
```
Inputs: pat
output = BooleanArray(len(rows))
for i, row in enumerate(rows):
if isnull(row):
output.setnull(i)
else
output[i] = (row[-len(pat):] == pat)
``` | 1.0 | Add str.endswith - - ✔️ [pandas function](https://pandas.pydata.org/docs/reference/api/pandas.Series.str.endswith.html#pandas.Series.str.endswith)
- ✔️ [Python function](https://docs.python.org/3/library/stdtypes.html#str.endswith)
- ✔️ simple C++ STL function: https://stackoverflow.com/a/62280289/1689261
- ✔️ no need for a regular expression library
- ✔️ no need for a Unicode database
- ✔️ can pre-compute size, output is a boolean array
Pseudo-Code:
```
Inputs: pat
output = BooleanArray(len(rows))
for i, row in enumerate(rows):
if isnull(row):
output.setnull(i)
else
output[i] = (row[-len(pat):] == pat)
``` | non_test | add str endswith ✔️ ✔️ ✔️ simple c stl function ✔️ no need for a regular expression library ✔️ no need for a unicode database ✔️ can pre compute size output is a boolean array pseudo code inputs pat output booleanarray len rows for i row in enumerate rows if isnull row output setnull i else output row pat | 0 |
706,986 | 24,290,410,514 | IssuesEvent | 2022-09-29 05:09:59 | valora-inc/wallet | https://api.github.com/repos/valora-inc/wallet | closed | [Query] Can we redirect user to homepage when user tries to invite a friend using inapp-CTA and with zero balance instead of staying on enter amount page | Priority: P3 wallet qa-report qa-query | **Frequency :** 100%
**Repro on build version:** iOS Test Flight build V 1.41.0, Android Internal Release build V 1.41.0 , iOS Appstore build V 1.40.1
**Repro on device version:** iPhone 12(14.7.1), iPhone 13mini (15.1.1), Google Pixel 2XL(11.0) , OnePlus 7T (11.0), Google Pixel 4a(12.0)
**Pre-condition:**
1] User must have downloaded mainnet application
2] User must have completed onboarding process'
3] User must have created a new account
4] User must be on homepage
**Repro Steps :**
1] on homepage send button will be seen disabled
2] navigate to invite friend CTA
3] Tap on invite friend button
4] redirects to select contact page
5] Enter contact number / select a non valora contact
6] On review page loader will be seen
**Query :**
Loader takes a long time and then there is no redirection so Whether user will be redirected to send invite page or it will stay on enter amount page
**Expected Behavior :**
- It should redirect back to homepage stating that "you have very low balance to make a transaction"
**Attachment :** [invite.mp4](https://drive.google.com/file/d/197cVxA32SLJTRKHx2eRTXG9DRGQbv9vY/view) | 1.0 | [Query] Can we redirect user to homepage when user tries to invite a friend using inapp-CTA and with zero balance instead of staying on enter amount page - **Frequency :** 100%
**Repro on build version:** iOS Test Flight build V 1.41.0, Android Internal Release build V 1.41.0 , iOS Appstore build V 1.40.1
**Repro on device version:** iPhone 12(14.7.1), iPhone 13mini (15.1.1), Google Pixel 2XL(11.0) , OnePlus 7T (11.0), Google Pixel 4a(12.0)
**Pre-condition:**
1] User must have downloaded mainnet application
2] User must have completed onboarding process'
3] User must have created a new account
4] User must be on homepage
**Repro Steps :**
1] on homepage send button will be seen disabled
2] navigate to invite friend CTA
3] Tap on invite friend button
4] redirects to select contact page
5] Enter contact number / select a non valora contact
6] On review page loader will be seen
**Query :**
Loader takes a long time and then there is no redirection so Whether user will be redirected to send invite page or it will stay on enter amount page
**Expected Behavior :**
- It should redirect back to homepage stating that "you have very low balance to make a transaction"
**Attachment :** [invite.mp4](https://drive.google.com/file/d/197cVxA32SLJTRKHx2eRTXG9DRGQbv9vY/view) | non_test | can we redirect user to homepage when user tries to invite a friend using inapp cta and with zero balance instead of staying on enter amount page frequency repro on build version ios test flight build v android internal release build v ios appstore build v repro on device version iphone iphone google pixel oneplus google pixel pre condition user must have downloaded mainnet application user must have completed onboarding process user must have created a new account user must be on homepage repro steps on homepage send button will be seen disabled navigate to invite friend cta tap on invite friend button redirects to select contact page enter contact number select a non valora contact on review page loader will be seen query loader takes a long time and then there is no redirection so whether user will be redirected to send invite page or it will stay on enter amount page expected behavior it should redirect back to homepage stating that you have very low balance to make a transaction attachment | 0 |
329,138 | 28,153,171,753 | IssuesEvent | 2023-04-03 04:28:45 | Joystream/pioneer | https://api.github.com/repos/Joystream/pioneer | closed | [USERSNAP] Page crash | bug scope:working-groups high-prio qa-task community-dev qa-tested-ready-for-prod release:1.3.2 |
**Taken at**: https://pioneerapp.xyz/#/working-groups/builders
**Fields**:
- Houston, we have a problem.: Page crash
- Comment: When I go to the history of the Builders WG openings the page crashes. White screen
- Feedback: adovrn
*[Download original image](https://resources.usersnap.com/company/f9f719df-a929-4461-bb6e-46dbfbceffb7/datapoint_screenshot/0d949575-1036-47b2-9928-6e581791af9b-annotated_fb50e55a-28c6-4bdc-946a-51a86428820f.png?etag=44348f26b8a36a2dc6cdbd0a8ecc2e64)*
**Browser**: Chrome 110 (Windows 10)
**Screen size**: 1536x864
**Browser size**: 1536x792
**[Open #399 in Usersnap](https://app.usersnap.com/l/feedback/524f6563-7c6f-4df1-949d-d817e09560ba?utm_medium=integration&utm_campaign=integration&utm_content=open)**
Powered by **[Usersnap](https://usersnap.com/?utm_source=product&utm_medium=poweredbylink&utm_campaign=github_entry)**. | 1.0 | [USERSNAP] Page crash -
**Taken at**: https://pioneerapp.xyz/#/working-groups/builders
**Fields**:
- Houston, we have a problem.: Page crash
- Comment: When I go to the history of the Builders WG openings the page crashes. White screen
- Feedback: adovrn
*[Download original image](https://resources.usersnap.com/company/f9f719df-a929-4461-bb6e-46dbfbceffb7/datapoint_screenshot/0d949575-1036-47b2-9928-6e581791af9b-annotated_fb50e55a-28c6-4bdc-946a-51a86428820f.png?etag=44348f26b8a36a2dc6cdbd0a8ecc2e64)*
**Browser**: Chrome 110 (Windows 10)
**Screen size**: 1536x864
**Browser size**: 1536x792
**[Open #399 in Usersnap](https://app.usersnap.com/l/feedback/524f6563-7c6f-4df1-949d-d817e09560ba?utm_medium=integration&utm_campaign=integration&utm_content=open)**
Powered by **[Usersnap](https://usersnap.com/?utm_source=product&utm_medium=poweredbylink&utm_campaign=github_entry)**. | test | page crash taken at fields houston we have a problem page crash comment when i go to the history of the builders wg openings the page crashes white screen feedback adovrn browser chrome windows screen size browser size powered by | 1 |
333,354 | 29,577,295,055 | IssuesEvent | 2023-06-07 00:39:38 | ray-project/ray | https://api.github.com/repos/ray-project/ray | closed | Release test remove_before_commit failed | bug P0 release-test | Release test remove_before_commit failed. See https://buildkite.com/ray-project/release-tests-pr/builds/40519#01886f25-5608-45f6-824f-d3c4aee5d13c for more details. | 1.0 | Release test remove_before_commit failed - Release test remove_before_commit failed. See https://buildkite.com/ray-project/release-tests-pr/builds/40519#01886f25-5608-45f6-824f-d3c4aee5d13c for more details. | test | release test remove before commit failed release test remove before commit failed see for more details | 1 |
212,647 | 16,471,881,643 | IssuesEvent | 2021-05-23 15:25:25 | urapadmin/kiosk | https://api.github.com/repos/urapadmin/kiosk | closed | use date container made not image creation date in dayplans | request test-stage | As discovered in the long haul that was for nothing that was #976, the date on the images in dayplans is the image creation date. Is it possible to use the date of creation of the container instead? The image creation date will always be available in the file repository, but in the context of the recording system and that list of images (which are ordered by creation date of container, not image creation date) the important thing is when it was used, not when it was made. | 1.0 | use date container made not image creation date in dayplans - As discovered in the long haul that was for nothing that was #976, the date on the images in dayplans is the image creation date. Is it possible to use the date of creation of the container instead? The image creation date will always be available in the file repository, but in the context of the recording system and that list of images (which are ordered by creation date of container, not image creation date) the important thing is when it was used, not when it was made. | test | use date container made not image creation date in dayplans as discovered in the long haul that was for nothing that was the date on the images in dayplans is the image creation date is it possible to use the date of creation of the container instead the image creation date will always be available in the file repository but in the context of the recording system and that list of images which are ordered by creation date of container not image creation date the important thing is when it was used not when it was made | 1 |
197,337 | 14,919,274,532 | IssuesEvent | 2021-01-22 23:38:44 | rclone/rclone | https://api.github.com/repos/rclone/rclone | closed | v1.51 Constantly high IOWAIT | Remote: Crypt Remote: Drive bug needs retest waiting for reply... | Bug report for tracking purpose based of https://forum.rclone.org/t/constantly-high-iowait-add-log/14156/15
#### What is the problem you are having with rclone?
Constantly high IOWAIT
#### What is your rclone version (output from `rclone version`)
v1.51
#### Which OS you are using and how many bits (eg Windows 7, 64 bit)
Ubuntu 18.04.3 LTS / 64 Bit
#### Which cloud storage system are you using? (eg Google Drive)
Ubuntu 18.04.3 LTS / 64 Bit
#### The command you were trying to run (eg `rclone copy /tmp remote:tmp`)
/usr/bin/screen -dmS gc /usr/bin/rclone mount gdrive_crypt: /mnt/gc
--config /mnt/hdd/rclone/rclone.conf
--use-mmap --fast-list --vfs-cache-mode writes
--cache-dir /mnt/hdd/tmp/gc/cache
--allow-other --umask 0 --tpslimit 10 --tpslimit-burst 20
--rc --rc-user xxxx --rc-pass xxxx -vv --log-file=/mnt/hdd/tmp/rclone.log
#### A log from the command with the `-vv` flag (eg output from `rclone -vv copy /tmp remote:tmp`)
http://www.mediafire.com/file/2ilu9k2nu9m9rzp/rclone_1_51.log/file
http://www.mediafire.com/file/wxbyldxn065v3vt/rclone_1_50.2.log/file
The following lines have been added.
2020/02/03 23:58:31 DEBUG : media/드라마/스토브리그.E01.191213.1080p-NEXT.mp4: waiting for in-sequence read to 1008861184 for 5ms
Netdata graph when testing
v1.51
v1.50.2
bhpark:
below test removed crypt backend.
no difference, with or without a crypt backend.
executed 'dd if=/mnt/tmp/1g_zero of=/dev/null bs=2M'
Increasing the time decreases the error output frequency.
wait time and error output count(somewhat variable)
5ms => 394
10ms => 63
20ms => 11
50ms => 4
However, IOWAIT will not decrease over 10ms.
It is also still high compared to the --async-read=false option.
bhpark:
Upload debug trace/profile
http://www.mediafire.com/file/h6yd7089tljhptt/pprof.zip/file
This was my first time using debug tool.
Please let me know if something is wrong
`Test method
mount
./rclone mount --async-read=true --vfs-read-wait 10ms -vv gdrive_media: /mnt/tmp/ --rc 2>&1 | grep 'abort.*in-sequence'
transfer
dd if=/mnt/tmp/1g_zero of=/dev/null bs=2M
get profile(In transmit)
wget http://localhost:5572/debug/pprof/trace?seconds=5
wget http://localhost:5572/debug/pprof/profile
wget http://localhost:5572/debug/pprof/goroutine?debug=1
wget http://localhost:5572/debug/pprof/block
wget http://localhost:5572/debug/pprof/mutex
wget http://localhost:5572/debug/pprof/heap`
| 1.0 | v1.51 Constantly high IOWAIT - Bug report for tracking purpose based of https://forum.rclone.org/t/constantly-high-iowait-add-log/14156/15
#### What is the problem you are having with rclone?
Constantly high IOWAIT
#### What is your rclone version (output from `rclone version`)
v1.51
#### Which OS you are using and how many bits (eg Windows 7, 64 bit)
Ubuntu 18.04.3 LTS / 64 Bit
#### Which cloud storage system are you using? (eg Google Drive)
Ubuntu 18.04.3 LTS / 64 Bit
#### The command you were trying to run (eg `rclone copy /tmp remote:tmp`)
/usr/bin/screen -dmS gc /usr/bin/rclone mount gdrive_crypt: /mnt/gc
--config /mnt/hdd/rclone/rclone.conf
--use-mmap --fast-list --vfs-cache-mode writes
--cache-dir /mnt/hdd/tmp/gc/cache
--allow-other --umask 0 --tpslimit 10 --tpslimit-burst 20
--rc --rc-user xxxx --rc-pass xxxx -vv --log-file=/mnt/hdd/tmp/rclone.log
#### A log from the command with the `-vv` flag (eg output from `rclone -vv copy /tmp remote:tmp`)
http://www.mediafire.com/file/2ilu9k2nu9m9rzp/rclone_1_51.log/file
http://www.mediafire.com/file/wxbyldxn065v3vt/rclone_1_50.2.log/file
The following lines have been added.
2020/02/03 23:58:31 DEBUG : media/드라마/스토브리그.E01.191213.1080p-NEXT.mp4: waiting for in-sequence read to 1008861184 for 5ms
Netdata graph when testing
v1.51
v1.50.2
bhpark:
below test removed crypt backend.
no difference, with or without a crypt backend.
executed 'dd if=/mnt/tmp/1g_zero of=/dev/null bs=2M'
Increasing the time decreases the error output frequency.
wait time and error output count(somewhat variable)
5ms => 394
10ms => 63
20ms => 11
50ms => 4
However, IOWAIT will not decrease over 10ms.
It is also still high compared to the --async-read=false option.
bhpark:
Upload debug trace/profile
http://www.mediafire.com/file/h6yd7089tljhptt/pprof.zip/file
This was my first time using debug tool.
Please let me know if something is wrong
`Test method
mount
./rclone mount --async-read=true --vfs-read-wait 10ms -vv gdrive_media: /mnt/tmp/ --rc 2>&1 | grep 'abort.*in-sequence'
transfer
dd if=/mnt/tmp/1g_zero of=/dev/null bs=2M
get profile(In transmit)
wget http://localhost:5572/debug/pprof/trace?seconds=5
wget http://localhost:5572/debug/pprof/profile
wget http://localhost:5572/debug/pprof/goroutine?debug=1
wget http://localhost:5572/debug/pprof/block
wget http://localhost:5572/debug/pprof/mutex
wget http://localhost:5572/debug/pprof/heap`
| test | constantly high iowait bug report for tracking purpose based of what is the problem you are having with rclone constantly high iowait what is your rclone version output from rclone version which os you are using and how many bits eg windows bit ubuntu lts bit which cloud storage system are you using eg google drive ubuntu lts bit the command you were trying to run eg rclone copy tmp remote tmp usr bin screen dms gc usr bin rclone mount gdrive crypt mnt gc config mnt hdd rclone rclone conf use mmap fast list vfs cache mode writes cache dir mnt hdd tmp gc cache allow other umask tpslimit tpslimit burst rc rc user xxxx rc pass xxxx vv log file mnt hdd tmp rclone log a log from the command with the vv flag eg output from rclone vv copy tmp remote tmp the following lines have been added debug media 드라마 스토브리그 next waiting for in sequence read to for netdata graph when testing bhpark below test removed crypt backend no difference with or without a crypt backend executed dd if mnt tmp zero of dev null bs increasing the time decreases the error output frequency wait time and error output count somewhat variable however iowait will not decrease over it is also still high compared to the async read false option bhpark upload debug trace profile this was my first time using debug tool please let me know if something is wrong test method mount rclone mount async read true vfs read wait vv gdrive media mnt tmp rc grep abort in sequence transfer dd if mnt tmp zero of dev null bs get profile in transmit wget wget wget wget wget wget | 1 |
110,982 | 9,486,705,432 | IssuesEvent | 2019-04-22 14:47:00 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | teamcity: failed test: TestEncodeBitArray | C-test-failure O-robot | The following tests appear to have failed on master (test): TestEncodeBitArray/desc/100/27/11111111111111111111111111111111111111111111111111111111111111111
You may want to check [for open issues](https://github.com/cockroachdb/cockroach/issues?q=is%3Aissue+is%3Aopen+TestEncodeBitArray).
[#1253381](https://teamcity.cockroachdb.com/viewLog.html?buildId=1253381):
```
TestEncodeBitArray/desc/100/27/11111111111111111111111111111111111111111111111111111111111111111
--- FAIL: test/TestEncodeBitArray/desc/100/27/11111111111111111111111111111111111111111111111111111111111111111 (0.000s)
Test ended in panic.
```
Please assign, take a look and update the issue accordingly.
| 1.0 | teamcity: failed test: TestEncodeBitArray - The following tests appear to have failed on master (test): TestEncodeBitArray/desc/100/27/11111111111111111111111111111111111111111111111111111111111111111
You may want to check [for open issues](https://github.com/cockroachdb/cockroach/issues?q=is%3Aissue+is%3Aopen+TestEncodeBitArray).
[#1253381](https://teamcity.cockroachdb.com/viewLog.html?buildId=1253381):
```
TestEncodeBitArray/desc/100/27/11111111111111111111111111111111111111111111111111111111111111111
--- FAIL: test/TestEncodeBitArray/desc/100/27/11111111111111111111111111111111111111111111111111111111111111111 (0.000s)
Test ended in panic.
```
Please assign, take a look and update the issue accordingly.
| test | teamcity failed test testencodebitarray the following tests appear to have failed on master test testencodebitarray desc you may want to check testencodebitarray desc fail test testencodebitarray desc test ended in panic please assign take a look and update the issue accordingly | 1 |
174,766 | 13,519,998,802 | IssuesEvent | 2020-09-15 03:30:56 | microsoft/msquic | https://api.github.com/repos/microsoft/msquic | opened | Test TLS HelloRetryRequest | Area: Testing | We need an automated test case for the TLS HelloRetryRequest message. | 1.0 | Test TLS HelloRetryRequest - We need an automated test case for the TLS HelloRetryRequest message. | test | test tls helloretryrequest we need an automated test case for the tls helloretryrequest message | 1 |
271,331 | 8,482,773,541 | IssuesEvent | 2018-10-25 19:31:52 | containous/traefik | https://api.github.com/repos/containous/traefik | closed | Multiple basic auth entries with same username | area/authentication contributor/waiting-for-feedback kind/enhancement priority/P3 | <!--
DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS.
The issue tracker is for reporting bugs and feature requests only.
For end-user related support questions, please refer to one of the following:
- Stack Overflow (using the "traefik" tag): https://stackoverflow.com/questions/tagged/traefik
- the Traefik community Slack channel: https://slack.traefik.io
-->
### Do you want to request a *feature* or report a *bug*?
Bug
### What did you do?
Looks like basic auth entries are overwritten when using multiple entries for the same username?
I want multiple passwords for same user.
I am using `traefik.frontend.auth.basic.users`
<!--
HOW TO WRITE A GOOD BUG REPORT?
- Respect the issue template as much as possible.
- If possible, use the command `traefik bug`. See https://www.youtube.com/watch?v=Lyz62L8m93I.
- The title should be short and descriptive.
- Explain the conditions which led you to report this issue: the context.
- The context should lead to something, an idea or a problem that you’re facing.
- Remain clear and concise.
- Format your messages to help the reader focus on what matters and understand the structure of your message, use Markdown syntax https://help.github.com/articles/github-flavored-markdown
-->
### What did you expect to see?
Use all the provided entries
### What did you see instead?
Only last entry was used for the username
### Output of `traefik version`: (_What version of Traefik are you using?_)
<!--
For the Traefik Docker image:
docker run [IMAGE] version
ex: docker run traefik version
For the alpine Traefik Docker image:
docker run [IMAGE] traefik version
ex: docker run traefik traefik version
-->
```
(paste your output here)
```
### What is your environment & configuration (arguments, toml, provider, platform, ...)?
```toml
# (paste your configuration here)
```
<!--
Add more configuration information here.
-->
### If applicable, please paste the log output in DEBUG level (`--logLevel=DEBUG` switch)
```
(paste your output here)
```
| 1.0 | Multiple basic auth entries with same username - <!--
DO NOT FILE ISSUES FOR GENERAL SUPPORT QUESTIONS.
The issue tracker is for reporting bugs and feature requests only.
For end-user related support questions, please refer to one of the following:
- Stack Overflow (using the "traefik" tag): https://stackoverflow.com/questions/tagged/traefik
- the Traefik community Slack channel: https://slack.traefik.io
-->
### Do you want to request a *feature* or report a *bug*?
Bug
### What did you do?
Looks like basic auth entries are overwritten when using multiple entries for the same username?
I want multiple passwords for same user.
I am using `traefik.frontend.auth.basic.users`
<!--
HOW TO WRITE A GOOD BUG REPORT?
- Respect the issue template as much as possible.
- If possible, use the command `traefik bug`. See https://www.youtube.com/watch?v=Lyz62L8m93I.
- The title should be short and descriptive.
- Explain the conditions which led you to report this issue: the context.
- The context should lead to something, an idea or a problem that you’re facing.
- Remain clear and concise.
- Format your messages to help the reader focus on what matters and understand the structure of your message, use Markdown syntax https://help.github.com/articles/github-flavored-markdown
-->
### What did you expect to see?
Use all the provided entries
### What did you see instead?
Only last entry was used for the username
### Output of `traefik version`: (_What version of Traefik are you using?_)
<!--
For the Traefik Docker image:
docker run [IMAGE] version
ex: docker run traefik version
For the alpine Traefik Docker image:
docker run [IMAGE] traefik version
ex: docker run traefik traefik version
-->
```
(paste your output here)
```
### What is your environment & configuration (arguments, toml, provider, platform, ...)?
```toml
# (paste your configuration here)
```
<!--
Add more configuration information here.
-->
### If applicable, please paste the log output in DEBUG level (`--logLevel=DEBUG` switch)
```
(paste your output here)
```
| non_test | multiple basic auth entries with same username do not file issues for general support questions the issue tracker is for reporting bugs and feature requests only for end user related support questions please refer to one of the following stack overflow using the traefik tag the traefik community slack channel do you want to request a feature or report a bug bug what did you do looks like basic auth entries are overwritten when using multiple entries for the same username i want multiple passwords for same user i am using traefik frontend auth basic users how to write a good bug report respect the issue template as much as possible if possible use the command traefik bug see the title should be short and descriptive explain the conditions which led you to report this issue the context the context should lead to something an idea or a problem that you’re facing remain clear and concise format your messages to help the reader focus on what matters and understand the structure of your message use markdown syntax what did you expect to see use all the provided entries what did you see instead only last entry was used for the username output of traefik version what version of traefik are you using for the traefik docker image docker run version ex docker run traefik version for the alpine traefik docker image docker run traefik version ex docker run traefik traefik version paste your output here what is your environment configuration arguments toml provider platform toml paste your configuration here add more configuration information here if applicable please paste the log output in debug level loglevel debug switch paste your output here | 0 |
288,357 | 21,700,692,584 | IssuesEvent | 2022-05-10 03:29:44 | jae-yong-2/HCI_Project | https://api.github.com/repos/jae-yong-2/HCI_Project | opened | [#1] README.md 작성 요청 | documentation | ### 프로젝트 README.md 작성
- [ ] 그라운드 규칙 명시
- [ ] 프로젝트 설명
- [ ] TODO 리스트
- [ ] 역할 분담 | 1.0 | [#1] README.md 작성 요청 - ### 프로젝트 README.md 작성
- [ ] 그라운드 규칙 명시
- [ ] 프로젝트 설명
- [ ] TODO 리스트
- [ ] 역할 분담 | non_test | readme md 작성 요청 프로젝트 readme md 작성 그라운드 규칙 명시 프로젝트 설명 todo 리스트 역할 분담 | 0 |
312,208 | 9,544,812,259 | IssuesEvent | 2019-05-01 15:16:06 | NCIOCPL/cgov-digital-platform | https://api.github.com/repos/NCIOCPL/cgov-digital-platform | closed | Fix Related Resources paragraph templates for Internal, External and Media Link | High priority In Scope (June 2019) change request | Work to be done:
* Delete the `paragraph--<type>--related-resource.html.twig` templates
* Delete the default `paragraph--<type>.html.twig` templates
* Change the Related Resources field on all types to render items as `List Item: Title` view mode
Related to #1539 | 1.0 | Fix Related Resources paragraph templates for Internal, External and Media Link - Work to be done:
* Delete the `paragraph--<type>--related-resource.html.twig` templates
* Delete the default `paragraph--<type>.html.twig` templates
* Change the Related Resources field on all types to render items as `List Item: Title` view mode
Related to #1539 | non_test | fix related resources paragraph templates for internal external and media link work to be done delete the paragraph related resource html twig templates delete the default paragraph html twig templates change the related resources field on all types to render items as list item title view mode related to | 0 |
21,329 | 3,891,710,765 | IssuesEvent | 2016-04-15 00:07:16 | bskinn/opan | https://api.github.com/repos/bskinn/opan | closed | Finish shaking down _arraysqueeze | enhancement in testing needs tests | `_arraysqueeze` decorator appears to be working nicely, in preliminary testing. May go cuckoo-bananas when used more broadly... | 2.0 | Finish shaking down _arraysqueeze - `_arraysqueeze` decorator appears to be working nicely, in preliminary testing. May go cuckoo-bananas when used more broadly... | test | finish shaking down arraysqueeze arraysqueeze decorator appears to be working nicely in preliminary testing may go cuckoo bananas when used more broadly | 1 |
40,543 | 6,828,189,871 | IssuesEvent | 2017-11-08 19:33:28 | kubernetes/kubeadm | https://api.github.com/repos/kubernetes/kubeadm | closed | Document how to pass custom args through to control plane components | area/UX documentation/content-gap | Often folks will want to custom configure components with extra args. You can do this with the configuration file, but we should focus on how to document this use case a bit better. If I'm a user, the flag isn't documented or made very visible.
This might be superseded by #265.
/cc @ahmetb | 1.0 | Document how to pass custom args through to control plane components - Often folks will want to custom configure components with extra args. You can do this with the configuration file, but we should focus on how to document this use case a bit better. If I'm a user, the flag isn't documented or made very visible.
This might be superseded by #265.
/cc @ahmetb | non_test | document how to pass custom args through to control plane components often folks will want to custom configure components with extra args you can do this with the configuration file but we should focus on how to document this use case a bit better if i m a user the flag isn t documented or made very visible this might be superseded by cc ahmetb | 0 |
19,573 | 3,775,828,954 | IssuesEvent | 2016-03-17 14:51:36 | sass/libsass | https://api.github.com/repos/sass/libsass | closed | Should throw error when & has no parent | Bug - Confirmed Bug - Regression Bug - Selectors Bug - Should Error Dev - PR Ready Dev - Test Written | This is a followup to issue #1569 .
Libsass no longer crashes in the specified test-case, but instead outputs the "&" in the css.
```
$tablet-portrait: 768px;
$tablet-landscape: 980px;
$desk-normal: 1120px;
$desk-big: 1280px;
$grid-breakpoints-immobile: (
'tablet-portrait': '(min-width: ' + $tablet-portrait + ') and (max-width: ' + $tablet-landscape + ')',
'tablet-landscape': '(min-width: ' + $tablet-landscape + ') and (max-width: ' + $desk-normal + ')',
'desk-normal': '(min-width: ' + $desk-normal + ') and (max-width: ' + $desk-big + ')',
'desk-big': '(min-width: ' + $desk-big + ')'
);
@mixin grid-media-query($media-query, $breakpointDefinitions) {
$breakpoint-found: false;
@each $breakpoint, $breakpointvalue in $breakpointDefinitions{
$name: $breakpoint;
$declaration: $breakpointvalue;
@if $media-query == $name and $declaration{
$breakpoint-found: true;
@media only screen and #{$declaration} {
@content;
}
}
}
}
@each $name in map-keys($grid-breakpoints-immobile) {
@include grid-media-query($name, $grid-breakpoints-immobile) {
body.immobile & {
margin-bottom: 0;
}
}
}
```
Produces the following outputs:
libsass version 3.2.5
```
@media only screen and (min-width: 768px) and (max-width: 980px) {
body.immobile {
margin-bottom: 0;
}
}
@media only screen and (min-width: 980px) and (max-width: 1120px) {
body.immobile {
margin-bottom: 0;
}
}
@media only screen and (min-width: 1120px) and (max-width: 1280px) {
body.immobile {
margin-bottom: 0;
}
}
@media only screen and (min-width: 1280px) {
body.immobile {
margin-bottom: 0;
}
}
```
libsass version 3.3.1
```
@media only screen and (min-width: 768px) and (max-width: 980px) {
body.immobile & {
margin-bottom: 0;
}
}
@media only screen and (min-width: 980px) and (max-width: 1120px) {
body.immobile & {
margin-bottom: 0;
}
}
@media only screen and (min-width: 1120px) and (max-width: 1280px) {
body.immobile & {
margin-bottom: 0;
}
}
@media only screen and (min-width: 1280px) {
body.immobile & {
margin-bottom: 0;
}
}
```
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/27734207-should-throw-error-when-has-no-parent?utm_campaign=plugin&utm_content=tracker%2F283068&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F283068&utm_medium=issues&utm_source=github).
</bountysource-plugin> | 1.0 | Should throw error when & has no parent - This is a followup to issue #1569 .
Libsass no longer crashes in the specified test-case, but instead outputs the "&" in the css.
```
$tablet-portrait: 768px;
$tablet-landscape: 980px;
$desk-normal: 1120px;
$desk-big: 1280px;
$grid-breakpoints-immobile: (
'tablet-portrait': '(min-width: ' + $tablet-portrait + ') and (max-width: ' + $tablet-landscape + ')',
'tablet-landscape': '(min-width: ' + $tablet-landscape + ') and (max-width: ' + $desk-normal + ')',
'desk-normal': '(min-width: ' + $desk-normal + ') and (max-width: ' + $desk-big + ')',
'desk-big': '(min-width: ' + $desk-big + ')'
);
@mixin grid-media-query($media-query, $breakpointDefinitions) {
$breakpoint-found: false;
@each $breakpoint, $breakpointvalue in $breakpointDefinitions{
$name: $breakpoint;
$declaration: $breakpointvalue;
@if $media-query == $name and $declaration{
$breakpoint-found: true;
@media only screen and #{$declaration} {
@content;
}
}
}
}
@each $name in map-keys($grid-breakpoints-immobile) {
@include grid-media-query($name, $grid-breakpoints-immobile) {
body.immobile & {
margin-bottom: 0;
}
}
}
```
Produces the following outputs:
libsass version 3.2.5
```
@media only screen and (min-width: 768px) and (max-width: 980px) {
body.immobile {
margin-bottom: 0;
}
}
@media only screen and (min-width: 980px) and (max-width: 1120px) {
body.immobile {
margin-bottom: 0;
}
}
@media only screen and (min-width: 1120px) and (max-width: 1280px) {
body.immobile {
margin-bottom: 0;
}
}
@media only screen and (min-width: 1280px) {
body.immobile {
margin-bottom: 0;
}
}
```
libsass version 3.3.1
```
@media only screen and (min-width: 768px) and (max-width: 980px) {
body.immobile & {
margin-bottom: 0;
}
}
@media only screen and (min-width: 980px) and (max-width: 1120px) {
body.immobile & {
margin-bottom: 0;
}
}
@media only screen and (min-width: 1120px) and (max-width: 1280px) {
body.immobile & {
margin-bottom: 0;
}
}
@media only screen and (min-width: 1280px) {
body.immobile & {
margin-bottom: 0;
}
}
```
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/27734207-should-throw-error-when-has-no-parent?utm_campaign=plugin&utm_content=tracker%2F283068&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F283068&utm_medium=issues&utm_source=github).
</bountysource-plugin> | test | should throw error when has no parent this is a followup to issue libsass no longer crashes in the specified test case but instead outputs the in the css tablet portrait tablet landscape desk normal desk big grid breakpoints immobile tablet portrait min width tablet portrait and max width tablet landscape tablet landscape min width tablet landscape and max width desk normal desk normal min width desk normal and max width desk big desk big min width desk big mixin grid media query media query breakpointdefinitions breakpoint found false each breakpoint breakpointvalue in breakpointdefinitions name breakpoint declaration breakpointvalue if media query name and declaration breakpoint found true media only screen and declaration content each name in map keys grid breakpoints immobile include grid media query name grid breakpoints immobile body immobile margin bottom produces the following outputs libsass version media only screen and min width and max width body immobile margin bottom media only screen and min width and max width body immobile margin bottom media only screen and min width and max width body immobile margin bottom media only screen and min width body immobile margin bottom libsass version media only screen and min width and max width body immobile margin bottom media only screen and min width and max width body immobile margin bottom media only screen and min width and max width body immobile margin bottom media only screen and min width body immobile margin bottom want to back this issue we accept bounties via | 1 |
6 | 2,489,911,015 | IssuesEvent | 2015-01-02 00:08:31 | firejake308/code-versus-bugs | https://api.github.com/repos/firejake308/code-versus-bugs | closed | Tutorial slides for different malwares | enhancement High Priority | I need to add tutorial slides for the different types of minions, but before I do that, we need to stabilize the first few levels so that I don't have to redo the work. For the purpose of the tutorial, we should probably adopt an incremental development strategy where we add a new feature, stabilize the first few levels, then add the next feature in the unstable levels that follow, stabilize those levels, and so on. As an added bonus, this will also seem impressive to the judges. :) | 1.0 | Tutorial slides for different malwares - I need to add tutorial slides for the different types of minions, but before I do that, we need to stabilize the first few levels so that I don't have to redo the work. For the purpose of the tutorial, we should probably adopt an incremental development strategy where we add a new feature, stabilize the first few levels, then add the next feature in the unstable levels that follow, stabilize those levels, and so on. As an added bonus, this will also seem impressive to the judges. :) | non_test | tutorial slides for different malwares i need to add tutorial slides for the different types of minions but before i do that we need to stabilize the first few levels so that i don t have to redo the work for the purpose of the tutorial we should probably adopt an incremental development strategy where we add a new feature stabilize the first few levels then add the next feature in the unstable levels that follow stabilize those levels and so on as an added bonus this will also seem impressive to the judges | 0 |
104,872 | 11,424,998,236 | IssuesEvent | 2020-02-03 18:55:27 | FlightControl-Master/MOOSE | https://api.github.com/repos/FlightControl-Master/MOOSE | closed | DOC ERROR - https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/Core.Spawn.html | bug documentation fixed | https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/Core.Spawn.html
scroll down to section
**Delay the initial spawning**
SPAWN.SpawnScheduledStop() SPAWN.SpawnScheduledStart()
these are both typos and do not exist there is no d in the proper method names ....... | 1.0 | DOC ERROR - https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/Core.Spawn.html - https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/Core.Spawn.html
scroll down to section
**Delay the initial spawning**
SPAWN.SpawnScheduledStop() SPAWN.SpawnScheduledStart()
these are both typos and do not exist there is no d in the proper method names ....... | non_test | doc error scroll down to section delay the initial spawning spawn spawnscheduledstop spawn spawnscheduledstart these are both typos and do not exist there is no d in the proper method names | 0 |
273,673 | 23,776,667,891 | IssuesEvent | 2022-09-01 21:45:43 | nromanen/pratical_testing_2022 | https://api.github.com/repos/nromanen/pratical_testing_2022 | opened | Verify that submit button for search by track number is disabled when the field 'Track number' is empty | test case | # [TC-23.3.1] : Verify that submit button for search by track number is disabled when the field 'Track number' is empty
## Description
Submit button for search by track number is disabled when the field 'Track number' is empty
### Precondition
There is a stable internet connection. Users should have access to Chrome, Firefox, Microsoft Edge, or Safari.
## Test Steps
| Step No. | Step description | Expected result |
| ------------- |:-------------:| -----:|
| 1. | Open main page - https://ttrackster.herokuapp.com/ | Form with the field 'Track number' displayed on the screen |
| 2. | Leave field 'Track number' empty and click on submit button | Submit button is disabled |
## Expected Result
Submit button is disabled
| 1.0 | Verify that submit button for search by track number is disabled when the field 'Track number' is empty - # [TC-23.3.1] : Verify that submit button for search by track number is disabled when the field 'Track number' is empty
## Description
Submit button for search by track number is disabled when the field 'Track number' is empty
### Precondition
There is a stable internet connection. Users should have access to Chrome, Firefox, Microsoft Edge, or Safari.
## Test Steps
| Step No. | Step description | Expected result |
| ------------- |:-------------:| -----:|
| 1. | Open main page - https://ttrackster.herokuapp.com/ | Form with the field 'Track number' displayed on the screen |
| 2. | Leave field 'Track number' empty and click on submit button | Submit button is disabled |
## Expected Result
Submit button is disabled
| test | verify that submit button for search by track number is disabled when the field track number is empty verify that submit button for search by track number is disabled when the field track number is empty description submit button for search by track number is disabled when the field track number is empty precondition there is a stable internet connection users should have access to chrome firefox microsoft edge or safari test steps step no step description expected result open main page form with the field track number displayed on the screen leave field track number empty and click on submit button submit button is disabled expected result submit button is disabled | 1 |
6,651 | 3,427,673,713 | IssuesEvent | 2015-12-10 03:28:39 | OData/odata.net | https://api.github.com/repos/OData/odata.net | closed | EdmUtil's static method DictionaryGetOrUpdate is not thread safe | 3 - Resolved (code ready) bug | https://github.com/OData/odata.net/blob/master/src/Microsoft.OData.Edm/EdmUtil.cs#L429-L448
Ref to:
http://stackoverflow.com/questions/6738634/is-this-non-locked-trygetvalue-dictionary-access-thread-safe
http://stackoverflow.com/questions/5885193/lock-on-dictionarys-trygetvalue-performance-issues
http://blogs.msdn.com/b/kimhamil/archive/2008/03/08/hashtable-and-dictionary-thread-safety-considerations.aspx
This may apply to both v4 and v3.
Related issue: https://github.com/OData/odata.net/issues/243 | 1.0 | EdmUtil's static method DictionaryGetOrUpdate is not thread safe - https://github.com/OData/odata.net/blob/master/src/Microsoft.OData.Edm/EdmUtil.cs#L429-L448
Ref to:
http://stackoverflow.com/questions/6738634/is-this-non-locked-trygetvalue-dictionary-access-thread-safe
http://stackoverflow.com/questions/5885193/lock-on-dictionarys-trygetvalue-performance-issues
http://blogs.msdn.com/b/kimhamil/archive/2008/03/08/hashtable-and-dictionary-thread-safety-considerations.aspx
This may apply to both v4 and v3.
Related issue: https://github.com/OData/odata.net/issues/243 | non_test | edmutil s static method dictionarygetorupdate is not thread safe ref to this may apply to both and related issue | 0 |
115,811 | 9,812,648,187 | IssuesEvent | 2019-06-13 05:30:35 | tdwg/bdq | https://api.github.com/repos/tdwg/bdq | closed | TG2-VALIDATION_YEAR_OUTOFRANGE | Conformance DO NOT IMPLEMENT Parameterized TG2 TIME Test Validation | | Field | Value |
| ----- | ----- |
| **GUID** | ad0c8855-de69-4843-a80c-a5387d20fbc8 |
| **Label** | VALIDATION_YEAR_OUTOFRANGE |
| **Output Type** | Validation |
| **Resource Type** | SingleRecord |
| **Darwin Core Class** | Event |
| **Information Elements** | dwc:year |
| **Expected Response** | INTERNAL_PREREQUISITES_NOT_MET if dwc:year is not present, or is EMPTY or can not be cast as an integer; COMPLIANT if the value of dwc:year cast as an integer does not extend outside optionally-provided begin and end years; otherwise NOT_COMPLIANT |
| **Dimension** | Time |
| **Data Quality Dimension** | Conformance |
| **Term-Actions** | YEAR_OUTOFRANGE |
| **Warning Type** | Invalid |
| **Parameter(s)** | Default values: earliest year = 1600, latest year = current year |
| **Example** | dwc:year="2230" |
| **Source** | VertNet |
| **References** | |
| **Example Implementations (Mechanisms)** | Kurator:event_date_qc |
| **Link to Specification Source Code** | https://github.com/FilteredPush/event_date_qc/blob/fb472b8fe25b72fc1203472b261900def3af61a9/src/main/java/org/filteredpush/qc/date/DwCEventDQ.java#L1601 unit test at https://github.com/FilteredPush/event_date_qc/blob/fb472b8fe25b72fc1203472b261900def3af61a9/src/test/java/org/filteredpush/qc/date/DwcEventDQTest.java#L1794 |
| **Notes** | The results of this test are time-dependent. Next year is not valid now. Next year it will be. This test provides the option to designate lower and upper limits to the year. The upper limit, if not provided, should default to the year when the test is run. NB By convention, use 1600 as a lower limit for collecting dates of biological specimens. | | 1.0 | TG2-VALIDATION_YEAR_OUTOFRANGE - | Field | Value |
| ----- | ----- |
| **GUID** | ad0c8855-de69-4843-a80c-a5387d20fbc8 |
| **Label** | VALIDATION_YEAR_OUTOFRANGE |
| **Output Type** | Validation |
| **Resource Type** | SingleRecord |
| **Darwin Core Class** | Event |
| **Information Elements** | dwc:year |
| **Expected Response** | INTERNAL_PREREQUISITES_NOT_MET if dwc:year is not present, or is EMPTY or can not be cast as an integer; COMPLIANT if the value of dwc:year cast as an integer does not extend outside optionally-provided begin and end years; otherwise NOT_COMPLIANT |
| **Dimension** | Time |
| **Data Quality Dimension** | Conformance |
| **Term-Actions** | YEAR_OUTOFRANGE |
| **Warning Type** | Invalid |
| **Parameter(s)** | Default values: earliest year = 1600, latest year = current year |
| **Example** | dwc:year="2230" |
| **Source** | VertNet |
| **References** | |
| **Example Implementations (Mechanisms)** | Kurator:event_date_qc |
| **Link to Specification Source Code** | https://github.com/FilteredPush/event_date_qc/blob/fb472b8fe25b72fc1203472b261900def3af61a9/src/main/java/org/filteredpush/qc/date/DwCEventDQ.java#L1601 unit test at https://github.com/FilteredPush/event_date_qc/blob/fb472b8fe25b72fc1203472b261900def3af61a9/src/test/java/org/filteredpush/qc/date/DwcEventDQTest.java#L1794 |
| **Notes** | The results of this test are time-dependent. Next year is not valid now. Next year it will be. This test provides the option to designate lower and upper limits to the year. The upper limit, if not provided, should default to the year when the test is run. NB By convention, use 1600 as a lower limit for collecting dates of biological specimens. | | test | validation year outofrange field value guid label validation year outofrange output type validation resource type singlerecord darwin core class event information elements dwc year expected response internal prerequisites not met if dwc year is not present or is empty or can not be cast as an integer compliant if the value of dwc year cast as an integer does not extend outside optionally provided begin and end years otherwise not compliant dimension time data quality dimension conformance term actions year outofrange warning type invalid parameter s default values earliest year latest year current year example dwc year source vertnet references example implementations mechanisms kurator event date qc link to specification source code unit test at notes the results of this test are time dependent next year is not valid now next year it will be this test provides the option to designate lower and upper limits to the year the upper limit if not provided should default to the year when the test is run nb by convention use as a lower limit for collecting dates of biological specimens | 1 |
141,291 | 11,411,408,517 | IssuesEvent | 2020-02-01 05:22:31 | projectclarify/clarify | https://api.github.com/repos/projectclarify/clarify | opened | Prow primary presubmit fails for PRs from ext. forks | good first issue priority/p2 sig/test | As titled, because it expects the commit SHA1 to be in the git tree of the main repo, having git cloned the main repo then trying to git checkout with a SHA1 that may be from a fork. | 1.0 | Prow primary presubmit fails for PRs from ext. forks - As titled, because it expects the commit SHA1 to be in the git tree of the main repo, having git cloned the main repo then trying to git checkout with a SHA1 that may be from a fork. | test | prow primary presubmit fails for prs from ext forks as titled because it expects the commit to be in the git tree of the main repo having git cloned the main repo then trying to git checkout with a that may be from a fork | 1 |
283,600 | 21,318,917,922 | IssuesEvent | 2022-04-16 19:23:12 | gurtejboparai/bookwyrm | https://api.github.com/repos/gurtejboparai/bookwyrm | opened | Make front end file naming conventions consistant | documentation | BookBriefView, SearchBar, userComponent, LoginScreen, and UserDetailsScreen all are inconsistent with the other file names of similar type. | 1.0 | Make front end file naming conventions consistant - BookBriefView, SearchBar, userComponent, LoginScreen, and UserDetailsScreen all are inconsistent with the other file names of similar type. | non_test | make front end file naming conventions consistant bookbriefview searchbar usercomponent loginscreen and userdetailsscreen all are inconsistent with the other file names of similar type | 0 |
6,878 | 2,867,231,040 | IssuesEvent | 2015-06-05 11:58:08 | bpmn-miwg/bpmn-miwg-test-suite | https://api.github.com/repos/bpmn-miwg/bpmn-miwg-test-suite | closed | Label for group is center inside the shape when it should be on the outside upper right corner | enhancement Import Test: B.1.0 Test: B.2.0 Tool: W4 BPMN+ Composer | Label for group is always display this way for now
see also http://bpmn-miwg.github.io/bpmn-miwg-tools/visual-test-result-comparison.html?tool=W4%20BPMN%2B%20Composer%20V.9.1 | 2.0 | Label for group is center inside the shape when it should be on the outside upper right corner - Label for group is always display this way for now
see also http://bpmn-miwg.github.io/bpmn-miwg-tools/visual-test-result-comparison.html?tool=W4%20BPMN%2B%20Composer%20V.9.1 | test | label for group is center inside the shape when it should be on the outside upper right corner label for group is always display this way for now see also | 1 |
133,125 | 10,790,617,572 | IssuesEvent | 2019-11-05 15:16:22 | cirosantilli/linux-kernel-module-cheat | https://api.github.com/repos/cirosantilli/linux-kernel-module-cheat | opened | Prevent use mode simulation tests that create files and run in parallel from clashing | test | As of 6936bd6ba996dee40f7cd826e5cf01ef39c2cabf, tests such as userland/c/file_write_read.c use `#define LKMC_TMP_FILE __FILE__ LKMC_TMP_EXT` to select what file they should write to.
`__FILE__` expands to the full C soure path, so multiple runs of the same files would write and read to the same output, possibly leading to clashes.
The only ANSI C standard solution I can see that works for both `test-executables-in-tree` (which should output those files in-tree) and `test-executables` would be to make all of those tests take a CLI parameter that points to the desired output path to use. We can then make the test system pass unique output path arguments to those programs. | 1.0 | Prevent use mode simulation tests that create files and run in parallel from clashing - As of 6936bd6ba996dee40f7cd826e5cf01ef39c2cabf, tests such as userland/c/file_write_read.c use `#define LKMC_TMP_FILE __FILE__ LKMC_TMP_EXT` to select what file they should write to.
`__FILE__` expands to the full C soure path, so multiple runs of the same files would write and read to the same output, possibly leading to clashes.
The only ANSI C standard solution I can see that works for both `test-executables-in-tree` (which should output those files in-tree) and `test-executables` would be to make all of those tests take a CLI parameter that points to the desired output path to use. We can then make the test system pass unique output path arguments to those programs. | test | prevent use mode simulation tests that create files and run in parallel from clashing as of tests such as userland c file write read c use define lkmc tmp file file lkmc tmp ext to select what file they should write to file expands to the full c soure path so multiple runs of the same files would write and read to the same output possibly leading to clashes the only ansi c standard solution i can see that works for both test executables in tree which should output those files in tree and test executables would be to make all of those tests take a cli parameter that points to the desired output path to use we can then make the test system pass unique output path arguments to those programs | 1 |
7,622 | 2,918,141,614 | IssuesEvent | 2015-06-24 05:29:28 | TEAMMATES/repo | https://api.github.com/repos/TEAMMATES/repo | opened | InstructorFeedbackPageUiTest fails sometimes due to ElementNotVisibleException | a-Testing | At line 495
testCopyToAction() - fillCopyToOtherCoursesForm() - markCheckBoxAsChecked() | 1.0 | InstructorFeedbackPageUiTest fails sometimes due to ElementNotVisibleException - At line 495
testCopyToAction() - fillCopyToOtherCoursesForm() - markCheckBoxAsChecked() | test | instructorfeedbackpageuitest fails sometimes due to elementnotvisibleexception at line testcopytoaction fillcopytoothercoursesform markcheckboxaschecked | 1 |
223,252 | 17,576,678,545 | IssuesEvent | 2021-08-15 18:49:43 | jjvanzon/JJ.Framework | https://api.github.com/repos/jjvanzon/JJ.Framework | closed | AssertHelper refactorings | enhancement file-dedup JJ.Framework.Testing | *+/- 2020-09-30*
- [x] Added optional name arguments.
- [x] `IsOfType`: "// TODO: Beating around the bush in code seems evidence of abstraction failure."
- [x] Other refactorings | 1.0 | AssertHelper refactorings - *+/- 2020-09-30*
- [x] Added optional name arguments.
- [x] `IsOfType`: "// TODO: Beating around the bush in code seems evidence of abstraction failure."
- [x] Other refactorings | test | asserthelper refactorings added optional name arguments isoftype todo beating around the bush in code seems evidence of abstraction failure other refactorings | 1 |
338,405 | 30,295,944,153 | IssuesEvent | 2023-07-09 21:17:56 | Alderon-Games/pathoftitans-bugs | https://api.github.com/repos/Alderon-Games/pathoftitans-bugs | closed | Storing homecave decorations causes game to freeze (Only alt+f4 works) | Needs Testing | ## Expected Behavior
Being able to go in and out of the storing and placing menu in home cave to decorate.
## Current Behavior
As soon as you go to store decorations the game freezes and locks your camera facing up.
## Reproduction Steps
seems to only happen when you've 100/100 placed
## Evidence (Screenshots & Videos)
Unable to get evidence as it locks up my pc when it occurs
## Build Information
**Game Version:** 0.0.0.26458
**Operating System & Version:** PC- Windows 10
**Alderon Games ID:** 832-504-759
| 1.0 | Storing homecave decorations causes game to freeze (Only alt+f4 works) - ## Expected Behavior
Being able to go in and out of the storing and placing menu in home cave to decorate.
## Current Behavior
As soon as you go to store decorations the game freezes and locks your camera facing up.
## Reproduction Steps
seems to only happen when you've 100/100 placed
## Evidence (Screenshots & Videos)
Unable to get evidence as it locks up my pc when it occurs
## Build Information
**Game Version:** 0.0.0.26458
**Operating System & Version:** PC- Windows 10
**Alderon Games ID:** 832-504-759
| test | storing homecave decorations causes game to freeze only alt works expected behavior being able to go in and out of the storing and placing menu in home cave to decorate current behavior as soon as you go to store decorations the game freezes and locks your camera facing up reproduction steps seems to only happen when you ve placed evidence screenshots videos unable to get evidence as it locks up my pc when it occurs build information game version operating system version pc windows alderon games id | 1 |
249,505 | 21,163,985,789 | IssuesEvent | 2022-04-07 12:02:05 | ita-social-projects/EventsExpress | https://api.github.com/repos/ita-social-projects/EventsExpress | opened | Check that registered user can view personal information in "my profile" page | test case | **Date Time**
04-07-2022 14:42
**Priority**
High
**Description**
Check that registered user can view personal information in "my profile" page for future editing.
**Pre-requisites**
1. Move to https://eventsexpress-test.azurewebsites.net/landing
2. Authorize as test User8
**Test Cases**
| S# | Action | Test Data | Expected Result | Actual Result | P/F | Automated |
|:-----------:|:-----------:|:-----------:|:---------------:|:-------------:|:-----------:|:-----------:|
| 1 | Clink on dropdown toggle [](https://user-images.githubusercontent.com/95763588/146768502-cba82e80-d1a6-48e1-a544-906e80bdae93.png)'image' in header | <br> | Open dropdown list | <br> | <br> | <br> |
| 2 | Click on "my profile" | <br> | Open profile page | <br> | <br> | <br> |
| 3 | Verify that page consist of fields for editind | <br> | Page consist of fields for editind from mockup | <br> | <br> | <br> |
| <br> | <br> | <br> | <br> | <br> | <br> | <br> |
| <br> | <br> | <br> | <br> | <br> | <br> | <br> |
**Screenshots**
**Environment:**
- OS: Windows 10
- Browser Opera
- Version 85.0.4341.47
**Additional context**
User story link E.g.: "User story #991 "
Labels to be added "Test case", Priority ("pri: "), Type ("UI, "Functional"), "API" .
| 1.0 | Check that registered user can view personal information in "my profile" page - **Date Time**
04-07-2022 14:42
**Priority**
High
**Description**
Check that registered user can view personal information in "my profile" page for future editing.
**Pre-requisites**
1. Move to https://eventsexpress-test.azurewebsites.net/landing
2. Authorize as test User8
**Test Cases**
| S# | Action | Test Data | Expected Result | Actual Result | P/F | Automated |
|:-----------:|:-----------:|:-----------:|:---------------:|:-------------:|:-----------:|:-----------:|
| 1 | Clink on dropdown toggle [](https://user-images.githubusercontent.com/95763588/146768502-cba82e80-d1a6-48e1-a544-906e80bdae93.png)'image' in header | <br> | Open dropdown list | <br> | <br> | <br> |
| 2 | Click on "my profile" | <br> | Open profile page | <br> | <br> | <br> |
| 3 | Verify that page consist of fields for editind | <br> | Page consist of fields for editind from mockup | <br> | <br> | <br> |
| <br> | <br> | <br> | <br> | <br> | <br> | <br> |
| <br> | <br> | <br> | <br> | <br> | <br> | <br> |
**Screenshots**
**Environment:**
- OS: Windows 10
- Browser Opera
- Version 85.0.4341.47
**Additional context**
User story link E.g.: "User story #991 "
Labels to be added "Test case", Priority ("pri: "), Type ("UI, "Functional"), "API" .
| test | check that registered user can view personal information in my profile page date time priority high description check that registered user can view personal information in my profile page for future editing pre requisites move to authorize as test test cases s action test data expected result actual result p f automated clink on dropdown toggle in header open dropdown list click on my profile open profile page verify that page consist of fields for editind page consist of fields for editind from mockup screenshots environment os windows browser opera version additional context user story link e g user story labels to be added test case priority pri type ui functional api | 1 |
749,003 | 26,147,191,525 | IssuesEvent | 2022-12-30 07:34:47 | tradingstrategy-ai/trade-executor | https://api.github.com/repos/tradingstrategy-ai/trade-executor | closed | Differing position_ids between TradePosition and TradingPosition | priority: P2 size: S | See #157, specifically [this comment](https://github.com/tradingstrategy-ai/trade-executor/issues/157#issuecomment-1366321402)
| 1.0 | Differing position_ids between TradePosition and TradingPosition - See #157, specifically [this comment](https://github.com/tradingstrategy-ai/trade-executor/issues/157#issuecomment-1366321402)
| non_test | differing position ids between tradeposition and tradingposition see specifically | 0 |
83,781 | 24,144,249,976 | IssuesEvent | 2022-09-21 17:15:42 | gradle/gradle | https://api.github.com/repos/gradle/gradle | closed | Task resolution in multi-product builds | a:feature in:composite-builds stale | From single-product builds I'm used to call tasks by matching prefix (`te` instead of `test`) or camelcase (`tD` instead of `testDebug`). I'm also used to the fact that Gradle matches only those subprojects that have that task configured, while ignoring all else.
Entering multi-product builds (i.e. included builds) with a Gradle wrapper in the root directory, things get a little more complicated. Neither of the above works out-of-the-box, e.g `./gradlew :product:tD` will not find any task `td` in the root project of the component `product`.
### Expected Behavior
Advanced task name matching should work for multi-product builds. One could think of a syntax like
```shell
$ ./gradlew --component product tD
```
or
```shell
$ ./gradlew :product::tD
```
where the double colon suggests that wildcard matching for the following term should happen within the build of `product`. (Right now, extra colons are simply ignored, which might therefor introduce an API break.)
### Current Behavior
Wildcard task name matching does not work. One has to use shell workarounds like
```shell
$ ( cd product && ../gradlew tD )
```
to achieve it.
### Version
Gradle 6.9 | 1.0 | Task resolution in multi-product builds - From single-product builds I'm used to call tasks by matching prefix (`te` instead of `test`) or camelcase (`tD` instead of `testDebug`). I'm also used to the fact that Gradle matches only those subprojects that have that task configured, while ignoring all else.
Entering multi-product builds (i.e. included builds) with a Gradle wrapper in the root directory, things get a little more complicated. Neither of the above works out-of-the-box, e.g `./gradlew :product:tD` will not find any task `td` in the root project of the component `product`.
### Expected Behavior
Advanced task name matching should work for multi-product builds. One could think of a syntax like
```shell
$ ./gradlew --component product tD
```
or
```shell
$ ./gradlew :product::tD
```
where the double colon suggests that wildcard matching for the following term should happen within the build of `product`. (Right now, extra colons are simply ignored, which might therefor introduce an API break.)
### Current Behavior
Wildcard task name matching does not work. One has to use shell workarounds like
```shell
$ ( cd product && ../gradlew tD )
```
to achieve it.
### Version
Gradle 6.9 | non_test | task resolution in multi product builds from single product builds i m used to call tasks by matching prefix te instead of test or camelcase td instead of testdebug i m also used to the fact that gradle matches only those subprojects that have that task configured while ignoring all else entering multi product builds i e included builds with a gradle wrapper in the root directory things get a little more complicated neither of the above works out of the box e g gradlew product td will not find any task td in the root project of the component product expected behavior advanced task name matching should work for multi product builds one could think of a syntax like shell gradlew component product td or shell gradlew product td where the double colon suggests that wildcard matching for the following term should happen within the build of product right now extra colons are simply ignored which might therefor introduce an api break current behavior wildcard task name matching does not work one has to use shell workarounds like shell cd product gradlew td to achieve it version gradle | 0 |
115,142 | 9,781,933,479 | IssuesEvent | 2019-06-07 21:21:44 | IIS-ZPI/ZPI_2019_Dzienni_IO4_JanuszeBiznesu | https://api.github.com/repos/IIS-ZPI/ZPI_2019_Dzienni_IO4_JanuszeBiznesu | closed | Create start structure of project | does'nt need test | Application is building in concrete IDE and language.
Project need correct and thought-out structure files and directors | 1.0 | Create start structure of project - Application is building in concrete IDE and language.
Project need correct and thought-out structure files and directors | test | create start structure of project application is building in concrete ide and language project need correct and thought out structure files and directors | 1 |
347,909 | 31,333,565,937 | IssuesEvent | 2023-08-24 02:59:58 | Plant-for-the-Planet-org/treemapper | https://api.github.com/repos/Plant-for-the-Planet-org/treemapper | opened | AxiosError in AxiosError: Network Error:0 | bug bugsnag testflight 1.0.9 | ## Error in Tree Mapper
**AxiosError** in **AxiosError: Network Error:0**
Network Error
[View on Bugsnag](https://app.bugsnag.com/plant-for-the-planet/tree-mapper/errors/64e6c7aaa7f742000852efb0?event_id=64e6c7a800becb8262bb0002&i=gh&m=ci)
## Stacktrace
AxiosError: Network Error:0 -
[View full stacktrace](https://app.bugsnag.com/plant-for-the-planet/tree-mapper/errors/64e6c7aaa7f742000852efb0?event_id=64e6c7a800becb8262bb0002&i=gh&m=ci)
*Created automatically via Bugsnag* | 1.0 | AxiosError in AxiosError: Network Error:0 - ## Error in Tree Mapper
**AxiosError** in **AxiosError: Network Error:0**
Network Error
[View on Bugsnag](https://app.bugsnag.com/plant-for-the-planet/tree-mapper/errors/64e6c7aaa7f742000852efb0?event_id=64e6c7a800becb8262bb0002&i=gh&m=ci)
## Stacktrace
AxiosError: Network Error:0 -
[View full stacktrace](https://app.bugsnag.com/plant-for-the-planet/tree-mapper/errors/64e6c7aaa7f742000852efb0?event_id=64e6c7a800becb8262bb0002&i=gh&m=ci)
*Created automatically via Bugsnag* | test | axioserror in axioserror network error error in tree mapper axioserror in axioserror network error network error stacktrace axioserror network error created automatically via bugsnag | 1 |
335,596 | 30,054,000,092 | IssuesEvent | 2023-06-28 04:40:49 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | opened | Fix arithmetic_operations.test_numpy_remainder | NumPy Frontend Sub Task Failing Test | | | |
|---|---|
|torch|<a href="null"><img src=https://img.shields.io/badge/-failure-red></a>
|paddle|<a href="null"><img src=https://img.shields.io/badge/-failure-red></a>
| 1.0 | Fix arithmetic_operations.test_numpy_remainder - | | |
|---|---|
|torch|<a href="null"><img src=https://img.shields.io/badge/-failure-red></a>
|paddle|<a href="null"><img src=https://img.shields.io/badge/-failure-red></a>
| test | fix arithmetic operations test numpy remainder torch img src paddle img src | 1 |
99,899 | 30,574,232,686 | IssuesEvent | 2023-07-21 02:54:51 | turnkeylinux/tracker | https://api.github.com/repos/turnkeylinux/tracker | closed | Domain Controller fails in LXC | feature container-lxc (build type) domain-controller | TL;DR: Samba fails in TurnKey Domain Controller. The best path for now is to use a VM instead. To persevere with LXC, please read on.
----
When initialising the [TurnKey Domain Controller](https://www.turnkeylinux.org/domain-controller) on Proxmox LXC, it fails. Here's is part of the stacktrace:
```
[...]
Setting up self join
Security context active token stack underflow!
PANIC (pid 3299): Security context active token stack underflow!
BACKTRACE: 45 stack frames:
#0 /lib/x86_64-linux-gnu/libsamba-util.so.0(log_stack_trace +0x32) [0x7f6d959228d2]
#1 /lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20) [0x7f6d936ce1c0]
#2 /lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7f6d959229df]
#3 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(sec_ct x_active_token+0x72) [0x7f6d9339b1a2]
[...]
```
It appears that it's actually an issue with Samba, rather than LXC (see this closed, "won't fix" [LXC bug report](https://github.com/lxc/lxc/issues/2708)).
There is a [workaround](https://github.com/lxc/lxc/issues/2708#issuecomment-473466062) noted and it appears to work.
I propose that we have a firstboot hook that checks to see if the appliance is running in LXC (`systemd-detect-virt`) and if so apply the workaround.
Having said that, the file that needs to be tweaked (`/usr/share/samba/setup/idmap_init.ldif`) is handled by package management. So we'd also need to update the file for future package upgrades. So we'd need to consider using `icron` or similar to re-apply the tweak if/when the file is updated. It seems that `smb.conf` may also need to be tweaked (to also ensure UIDs of 65533 or less) but I can't yet confirm that.
It's perhaps also worth checking for `xattrs` and directing users on how to do that (also mentioned in that workaround post). It seems using btrfs is a workaround to support that. | 1.0 | Domain Controller fails in LXC - TL;DR: Samba fails in TurnKey Domain Controller. The best path for now is to use a VM instead. To persevere with LXC, please read on.
----
When initialising the [TurnKey Domain Controller](https://www.turnkeylinux.org/domain-controller) on Proxmox LXC, it fails. Here's is part of the stacktrace:
```
[...]
Setting up self join
Security context active token stack underflow!
PANIC (pid 3299): Security context active token stack underflow!
BACKTRACE: 45 stack frames:
#0 /lib/x86_64-linux-gnu/libsamba-util.so.0(log_stack_trace +0x32) [0x7f6d959228d2]
#1 /lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20) [0x7f6d936ce1c0]
#2 /lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7f6d959229df]
#3 /usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0(sec_ct x_active_token+0x72) [0x7f6d9339b1a2]
[...]
```
It appears that it's actually an issue with Samba, rather than LXC (see this closed, "won't fix" [LXC bug report](https://github.com/lxc/lxc/issues/2708)).
There is a [workaround](https://github.com/lxc/lxc/issues/2708#issuecomment-473466062) noted and it appears to work.
I propose that we have a firstboot hook that checks to see if the appliance is running in LXC (`systemd-detect-virt`) and if so apply the workaround.
Having said that, the file that needs to be tweaked (`/usr/share/samba/setup/idmap_init.ldif`) is handled by package management. So we'd also need to update the file for future package upgrades. So we'd need to consider using `icron` or similar to re-apply the tweak if/when the file is updated. It seems that `smb.conf` may also need to be tweaked (to also ensure UIDs of 65533 or less) but I can't yet confirm that.
It's perhaps also worth checking for `xattrs` and directing users on how to do that (also mentioned in that workaround post). It seems using btrfs is a workaround to support that. | non_test | domain controller fails in lxc tl dr samba fails in turnkey domain controller the best path for now is to use a vm instead to persevere with lxc please read on when initialising the on proxmox lxc it fails here s is part of the stacktrace setting up self join security context active token stack underflow panic pid security context active token stack underflow backtrace stack frames lib linux gnu libsamba util so log stack trace lib linux gnu libsmbconf so smb panic lib linux gnu libsamba util so smb panic usr lib linux gnu samba libsmbd base so sec ct x active token it appears that it s actually an issue with samba rather than lxc see this closed won t fix there is a noted and it appears to work i propose that we have a firstboot hook that checks to see if the appliance is running in lxc systemd detect virt and if so apply the workaround having said that the file that needs to be tweaked usr share samba setup idmap init ldif is handled by package management so we d also need to update the file for future package upgrades so we d need to consider using icron or similar to re apply the tweak if when the file is updated it seems that smb conf may also need to be tweaked to also ensure uids of or less but i can t yet confirm that it s perhaps also worth checking for xattrs and directing users on how to do that also mentioned in that workaround post it seems using btrfs is a workaround to support that | 0 |
235,507 | 19,350,510,945 | IssuesEvent | 2021-12-15 15:12:43 | elastic/elasticsearch | https://api.github.com/repos/elastic/elasticsearch | closed | [CI] ActivateWatchTests testDeactivateAndActivate failing | >test-failure :Data Management/Watcher Team:Data Management | **Build scan:**
https://gradle-enterprise.elastic.co/s/7tp3knsxy7zok/tests/:x-pack:plugin:watcher:internalClusterTest/org.elasticsearch.xpack.watcher.transport.action.activate.ActivateWatchTests/testDeactivateAndActivate
**Reproduction line:**
`./gradlew ':x-pack:plugin:watcher:internalClusterTest' --tests "org.elasticsearch.xpack.watcher.transport.action.activate.ActivateWatchTests.testDeactivateAndActivate" -Dtests.seed=1A848E0804358E18 -Dtests.locale=zh-Hans-SG -Dtests.timezone=America/Adak -Druntime.java=17`
**Applicable branches:**
8.0
**Reproduces locally?:**
No
**Failure history:**
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.xpack.watcher.transport.action.activate.ActivateWatchTests&tests.test=testDeactivateAndActivate
**Failure excerpt:**
```
java.lang.IllegalArgumentException: index [.ds-.watcher-history-14-2021.12.13-000001] is the write index for data stream [.watcher-history-14] and cannot be deleted
at __randomizedtesting.SeedInfo.seed([1A848E0804358E18:BADCF6F5CB6C5864]:0)
at org.elasticsearch.cluster.metadata.MetadataDeleteIndexService.deleteIndices(MetadataDeleteIndexService.java:90)
at org.elasticsearch.cluster.metadata.MetadataDeleteIndexService$1.execute(MetadataDeleteIndexService.java:68)
at org.elasticsearch.cluster.ClusterStateUpdateTask.execute(ClusterStateUpdateTask.java:51)
at org.elasticsearch.cluster.service.MasterService.executeTasks(MasterService.java:828)
at org.elasticsearch.cluster.service.MasterService.calculateTaskOutputs(MasterService.java:395)
at org.elasticsearch.cluster.service.MasterService.runTasks(MasterService.java:235)
at org.elasticsearch.cluster.service.MasterService$Batcher.run(MasterService.java:167)
at org.elasticsearch.cluster.service.TaskBatcher.runIfNotProcessed(TaskBatcher.java:146)
at org.elasticsearch.cluster.service.TaskBatcher$BatchedTask.run(TaskBatcher.java:202)
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:716)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:262)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:225)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.lang.Thread.run(Thread.java:833)
``` | 1.0 | [CI] ActivateWatchTests testDeactivateAndActivate failing - **Build scan:**
https://gradle-enterprise.elastic.co/s/7tp3knsxy7zok/tests/:x-pack:plugin:watcher:internalClusterTest/org.elasticsearch.xpack.watcher.transport.action.activate.ActivateWatchTests/testDeactivateAndActivate
**Reproduction line:**
`./gradlew ':x-pack:plugin:watcher:internalClusterTest' --tests "org.elasticsearch.xpack.watcher.transport.action.activate.ActivateWatchTests.testDeactivateAndActivate" -Dtests.seed=1A848E0804358E18 -Dtests.locale=zh-Hans-SG -Dtests.timezone=America/Adak -Druntime.java=17`
**Applicable branches:**
8.0
**Reproduces locally?:**
No
**Failure history:**
https://gradle-enterprise.elastic.co/scans/tests?tests.container=org.elasticsearch.xpack.watcher.transport.action.activate.ActivateWatchTests&tests.test=testDeactivateAndActivate
**Failure excerpt:**
```
java.lang.IllegalArgumentException: index [.ds-.watcher-history-14-2021.12.13-000001] is the write index for data stream [.watcher-history-14] and cannot be deleted
at __randomizedtesting.SeedInfo.seed([1A848E0804358E18:BADCF6F5CB6C5864]:0)
at org.elasticsearch.cluster.metadata.MetadataDeleteIndexService.deleteIndices(MetadataDeleteIndexService.java:90)
at org.elasticsearch.cluster.metadata.MetadataDeleteIndexService$1.execute(MetadataDeleteIndexService.java:68)
at org.elasticsearch.cluster.ClusterStateUpdateTask.execute(ClusterStateUpdateTask.java:51)
at org.elasticsearch.cluster.service.MasterService.executeTasks(MasterService.java:828)
at org.elasticsearch.cluster.service.MasterService.calculateTaskOutputs(MasterService.java:395)
at org.elasticsearch.cluster.service.MasterService.runTasks(MasterService.java:235)
at org.elasticsearch.cluster.service.MasterService$Batcher.run(MasterService.java:167)
at org.elasticsearch.cluster.service.TaskBatcher.runIfNotProcessed(TaskBatcher.java:146)
at org.elasticsearch.cluster.service.TaskBatcher$BatchedTask.run(TaskBatcher.java:202)
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:716)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:262)
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:225)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.lang.Thread.run(Thread.java:833)
``` | test | activatewatchtests testdeactivateandactivate failing build scan reproduction line gradlew x pack plugin watcher internalclustertest tests org elasticsearch xpack watcher transport action activate activatewatchtests testdeactivateandactivate dtests seed dtests locale zh hans sg dtests timezone america adak druntime java applicable branches reproduces locally no failure history failure excerpt java lang illegalargumentexception index is the write index for data stream and cannot be deleted at randomizedtesting seedinfo seed at org elasticsearch cluster metadata metadatadeleteindexservice deleteindices metadatadeleteindexservice java at org elasticsearch cluster metadata metadatadeleteindexservice execute metadatadeleteindexservice java at org elasticsearch cluster clusterstateupdatetask execute clusterstateupdatetask java at org elasticsearch cluster service masterservice executetasks masterservice java at org elasticsearch cluster service masterservice calculatetaskoutputs masterservice java at org elasticsearch cluster service masterservice runtasks masterservice java at org elasticsearch cluster service masterservice batcher run masterservice java at org elasticsearch cluster service taskbatcher runifnotprocessed taskbatcher java at org elasticsearch cluster service taskbatcher batchedtask run taskbatcher java at org elasticsearch common util concurrent threadcontext contextpreservingrunnable run threadcontext java at org elasticsearch common util concurrent prioritizedesthreadpoolexecutor tiebreakingprioritizedrunnable runandclean prioritizedesthreadpoolexecutor java at org elasticsearch common util concurrent prioritizedesthreadpoolexecutor tiebreakingprioritizedrunnable run prioritizedesthreadpoolexecutor java at java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java util concurrent threadpoolexecutor worker run threadpoolexecutor java at java lang thread run thread java | 1 |
10,604 | 4,074,399,835 | IssuesEvent | 2016-05-28 12:19:10 | DotSpatial/DotSpatial | https://api.github.com/repos/DotSpatial/DotSpatial | closed | PolygonSymbolizerEditor problems? | bug CodePlex | **This issue was imported from [CodePlex](http://dotspatial.codeplex.com/workitem/51)**
**[Shade1974](http://www.codeplex.com/site/users/view/Shade1974)** wrote 2010-09-14 at 19:32
Hi Ted,
I've played with the PolygonSymbolizerEditor a bit so that it would create a new PolygonSymbolizer if it tries to edit a null value. Now the problem is once the editor is launched. I may be using it wrong but it simply does nothing when you click the add button
at the bottom of the Patterns list and if the length of the pattern list is 0 then it crashes.
Got any ideas?
Thnx, Brian | 1.0 | PolygonSymbolizerEditor problems? - **This issue was imported from [CodePlex](http://dotspatial.codeplex.com/workitem/51)**
**[Shade1974](http://www.codeplex.com/site/users/view/Shade1974)** wrote 2010-09-14 at 19:32
Hi Ted,
I've played with the PolygonSymbolizerEditor a bit so that it would create a new PolygonSymbolizer if it tries to edit a null value. Now the problem is once the editor is launched. I may be using it wrong but it simply does nothing when you click the add button
at the bottom of the Patterns list and if the length of the pattern list is 0 then it crashes.
Got any ideas?
Thnx, Brian | non_test | polygonsymbolizereditor problems this issue was imported from wrote at hi ted i ve played with the polygonsymbolizereditor a bit so that it would create a new polygonsymbolizer if it tries to edit a null value now the problem is once the editor is launched i may be using it wrong but it simply does nothing when you click the add button at the bottom of the patterns list and if the length of the pattern list is then it crashes got any ideas thnx brian | 0 |
191,217 | 14,593,504,335 | IssuesEvent | 2020-12-19 23:13:31 | github-vet/rangeloop-pointer-findings | https://api.github.com/repos/github-vet/rangeloop-pointer-findings | closed | nolash/psstalk: main_test.go; 55 LoC | fresh medium test |
Found a possible issue in [nolash/psstalk](https://www.github.com/nolash/psstalk) at [main_test.go](https://github.com/nolash/psstalk/blob/24102a5a1bde09ade043757b39154784b80eaf7b/main_test.go#L530-L584)
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.
> range-loop variable cfg used in defer or goroutine at line 573
[Click here to see the code in its original context.](https://github.com/nolash/psstalk/blob/24102a5a1bde09ade043757b39154784b80eaf7b/main_test.go#L530-L584)
<details>
<summary>Click here to show the 55 line(s) of Go which triggered the analyzer.</summary>
```go
for i, cfg := range fakenodeconfigs {
chatlog.Debug("fakenode", "idx", i, "addr", fakepots[cfg.ID], "id", fmt.Sprintf("%x", cfg.ID[:8]))
fakenode, err := simnet.NewNodeWithConfig(cfg)
if err != nil {
shutdown()
t.Fatalf("node create fail: %v", err)
}
fakenodes = append(fakenodes, fakenode)
if err := simnet.Start(fakenode.ID()); err != nil {
shutdown()
t.Fatalf("node start fail: %v", err)
}
fakerpc, err := fakenode.Client()
if err != nil {
shutdown()
t.Fatalf("rpc err: %v", err)
}
fakeclients[cfg.ID], err = pssclient.NewClientWithRPC(ctx, fakerpc)
if err != nil {
t.Fatalf(err)
}
fakeclients[cfg.ID].Start()
//fakeclients[cfg.ID].RunProtocol(newTestProtocol(inCs[cfg.ID], outCs[cfg.ID]))
fakeclients[cfg.ID].RunProtocol(psschat.New(inCs[cfg.ID], nil, newTestChatInject(outCs[cfg.ID])))
peerevents := make(chan *p2p.PeerEvent)
peersub, err := fakerpc.Subscribe(ctx, "admin", peerevents, "peerEvents")
if err != nil {
shutdown()
t.Fatalf("node subscribe fail: %v", err)
}
go func() {
gotit := false
for {
select {
case event := <-peerevents:
if event.Type == "add" {
if !gotit {
readyC <-cfg.ID
gotit = true
}
chatlog.Debug("add", "node", cfg.ID, "peer", event.Peer)
}
case <-quitRPCC:
peersub.Unsubscribe()
return
}
}
}()
}
```
</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: 24102a5a1bde09ade043757b39154784b80eaf7b
| 1.0 | nolash/psstalk: main_test.go; 55 LoC -
Found a possible issue in [nolash/psstalk](https://www.github.com/nolash/psstalk) at [main_test.go](https://github.com/nolash/psstalk/blob/24102a5a1bde09ade043757b39154784b80eaf7b/main_test.go#L530-L584)
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.
> range-loop variable cfg used in defer or goroutine at line 573
[Click here to see the code in its original context.](https://github.com/nolash/psstalk/blob/24102a5a1bde09ade043757b39154784b80eaf7b/main_test.go#L530-L584)
<details>
<summary>Click here to show the 55 line(s) of Go which triggered the analyzer.</summary>
```go
for i, cfg := range fakenodeconfigs {
chatlog.Debug("fakenode", "idx", i, "addr", fakepots[cfg.ID], "id", fmt.Sprintf("%x", cfg.ID[:8]))
fakenode, err := simnet.NewNodeWithConfig(cfg)
if err != nil {
shutdown()
t.Fatalf("node create fail: %v", err)
}
fakenodes = append(fakenodes, fakenode)
if err := simnet.Start(fakenode.ID()); err != nil {
shutdown()
t.Fatalf("node start fail: %v", err)
}
fakerpc, err := fakenode.Client()
if err != nil {
shutdown()
t.Fatalf("rpc err: %v", err)
}
fakeclients[cfg.ID], err = pssclient.NewClientWithRPC(ctx, fakerpc)
if err != nil {
t.Fatalf(err)
}
fakeclients[cfg.ID].Start()
//fakeclients[cfg.ID].RunProtocol(newTestProtocol(inCs[cfg.ID], outCs[cfg.ID]))
fakeclients[cfg.ID].RunProtocol(psschat.New(inCs[cfg.ID], nil, newTestChatInject(outCs[cfg.ID])))
peerevents := make(chan *p2p.PeerEvent)
peersub, err := fakerpc.Subscribe(ctx, "admin", peerevents, "peerEvents")
if err != nil {
shutdown()
t.Fatalf("node subscribe fail: %v", err)
}
go func() {
gotit := false
for {
select {
case event := <-peerevents:
if event.Type == "add" {
if !gotit {
readyC <-cfg.ID
gotit = true
}
chatlog.Debug("add", "node", cfg.ID, "peer", event.Peer)
}
case <-quitRPCC:
peersub.Unsubscribe()
return
}
}
}()
}
```
</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: 24102a5a1bde09ade043757b39154784b80eaf7b
| test | nolash psstalk main 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 range loop variable cfg used in defer or goroutine at line click here to show the line s of go which triggered the analyzer go for i cfg range fakenodeconfigs chatlog debug fakenode idx i addr fakepots id fmt sprintf x cfg id fakenode err simnet newnodewithconfig cfg if err nil shutdown t fatalf node create fail v err fakenodes append fakenodes fakenode if err simnet start fakenode id err nil shutdown t fatalf node start fail v err fakerpc err fakenode client if err nil shutdown t fatalf rpc err v err fakeclients err pssclient newclientwithrpc ctx fakerpc if err nil t fatalf err fakeclients start fakeclients runprotocol newtestprotocol incs outcs fakeclients runprotocol psschat new incs nil newtestchatinject outcs peerevents make chan peerevent peersub err fakerpc subscribe ctx admin peerevents peerevents if err nil shutdown t fatalf node subscribe fail v err go func gotit false for select case event peerevents if event type add if gotit readyc cfg id gotit true chatlog debug add node cfg id peer event peer case quitrpcc peersub unsubscribe return 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 |
107,748 | 9,222,397,407 | IssuesEvent | 2019-03-11 22:45:07 | rancher/rancher | https://api.github.com/repos/rancher/rancher | closed | Upgrade - Rotating certificates on a cluster created pre-upgrade causes cluster to go unavailable | area/rke kind/bug-qa status/ready-for-review status/resolved status/to-test team/ca version/2.0 | rancher/rancher:master-0f189f13 3/8
HA install
Rotating certificates on a cluster that was created prior to upgrading to master causes the cluster to become unavailable.
This does not occur for clusters created post-upgrade, or on a fresh-install.
To reproduce:
* Deploy Rancher - v2.1.7
* Provision RKE cluster (EC2)
* Upgrade Rancher to master
* Rotate certificates for the cluster
Expected:
* Certificates rotate and cluster is accessible
Actual:
* Certificates appear to rotate, but cluster becomes unavailable.
Logs show:
```
2019/03/08 23:02:02 [INFO] cluster [c-7vbbh] provisioning: Rebuilding Kubernetes cluster with rotated certificates
2019/03/08 23:02:02 [INFO] cluster [c-7vbbh] provisioning: [dialer] Setup tunnel for host [54.184.213.43]
2019/03/08 23:02:02 [INFO] cluster [c-7vbbh] provisioning: [certificates] Deploying kubernetes certificates to Cluster nodes
2019/03/08 23:02:07 [INFO] cluster [c-7vbbh] provisioning: [reconcile] Rebuilding and updating local kube config
I0308 23:02:07.838353 7 http.go:110] HTTP2 has been explicitly disabled
2019/03/08 23:02:07 [INFO] cluster [c-7vbbh] provisioning: Successfully Deployed local admin kubeconfig at [management-state/rke/rke-052893049/kube_config_cluster.yml]
2019/03/08 23:02:07 [INFO] cluster [c-7vbbh] provisioning: [certificates] Successfully deployed kubernetes certificates to Cluster nodes
2019/03/08 23:02:07 [INFO] cluster [c-7vbbh] provisioning: Successfully Deployed state file at [management-state/rke/rke-052893049/cluster.rkestate]
2019/03/08 23:02:07 [INFO] cluster [c-7vbbh] provisioning: [etcd] Restarting up etcd plane..
2019/03/08 23:02:13 [INFO] cluster [c-7vbbh] provisioning: [restart/etcd] Successfully restarted container on host [54.184.213.43]
2019/03/08 23:02:13 [INFO] cluster [c-7vbbh] provisioning: [etcd] Successfully restarted etcd plane..
2019/03/08 23:02:13 [INFO] cluster [c-7vbbh] provisioning: [controlplane] Restarting the Controller Plane..
2019/03/08 23:02:13 [ERROR] ClusterController c-7vbbh [user-controllers-controller] failed with : failed to start user controllers for cluster c-7vbbh: failed to contact server: Get https://54.184.213.43:6443/version?timeout=30s: dial tcp 172.31.35.242:6443: connect: connection refused
2019/03/08 23:02:14 [ERROR] ClusterController c-7vbbh [user-controllers-controller] failed with : failed to start user controllers for cluster c-7vbbh: failed to contact server: Get https://54.184.213.43:6443/version?timeout=30s: dial tcp 172.31.35.242:6443: connect: connection refused
2019/03/08 23:02:15 [ERROR] ClusterController c-7vbbh [user-controllers-controller] failed with : failed to start user controllers for cluster c-7vbbh: failed to contact server: Get https://54.184.213.43:6443/version?timeout=30s: dial tcp 172.31.35.242:6443: connect: connection refused
2019/03/08 23:02:17 [ERROR] ClusterController c-7vbbh [user-controllers-controller] failed with : failed to start user controllers for cluster c-7vbbh: failed to contact server: Get https://54.184.213.43:6443/version?timeout=30s: dial tcp 172.31.35.242:6443: connect: connection refused
E0308 23:02:18.537952 7 reflector.go:251] github.com/rancher/norman/controller/generic_controller.go:175: Failed to watch *v1.Role: Get https://54.184.213.43:6443/apis/rbac.authorization.k8s.io/v1/watch/roles?resourceVersion=498&timeout=30m0s&timeoutSeconds=439: dial tcp 172.31.35.242:6443: connect: connection refused
E0308 23:02:18.539703 7 reflector.go:251] github.com/rancher/norman/controller/generic_controller.go:175: Failed to watch *v1.Service: Get https://54.184.213.43:6443/api/v1/watch/services?resourceVersion=509&timeout=30m0s&timeoutSeconds=336: dial tcp 172.31.35.242:6443: connect: connection refused
E0308 23:02:18.539710 7 reflector.go:251] github.com/rancher/norman/controller/generic_controller.go:175: Failed to watch *v1.Namespace: Get https://54.184.213.43:6443/api/v1/watch/namespaces?resourceVersion=779&timeout=30m0s&timeoutSeconds=533: dial tcp 172.31.35.242:6443: connect: connection refused
E0308 23:02:18.539880 7 reflector.go:251] github.com/rancher/norman/controller/generic_controller.go:175: Failed to watch *v1.RoleBinding: Get https://54.184.213.43:6443/apis/rbac.authorization.k8s.io/v1/watch/rolebindings?resourceVersion=1261&timeout=30m0s&timeoutSeconds=332: dial tcp 172.31.35.242:6443: connect: connection refused
E0308 23:02:18.539912 7 reflector.go:251] github.com/rancher/norman/controller/generic_controller.go:175: Failed to watch *v1.ClusterRoleBinding: Get https://54.184.213.43:6443/apis/rbac.authorization.k8s.io/v1/watch/clusterrolebindings?resourceVersion=1279&timeout=30m0s&timeoutSeconds=364: dial tcp 172.31.35.242:6443: connect: connection refused
E0308 23:02:18.539917 7 reflector.go:251] github.com/rancher/norman/controller/generic_controller.go:175: Failed to watch *v1.ClusterRole: Get https://54.184.213.43:6443/apis/rbac.authorization.k8s.io/v1/watch/clusterroles?resourceVersion=1468&timeout=30m0s&timeoutSeconds=456: dial tcp 172.31.35.242:6443: connect: connection refused
2019/03/08 23:02:18 [INFO] cluster [c-7vbbh] provisioning: [restart/kube-apiserver] Successfully restarted container on host [54.184.213.43]
2019/03/08 23:02:18 [ERROR] ClusterController c-7vbbh [user-controllers-controller] failed with : failed to start user controllers for cluster c-7vbbh: failed to contact server: Get https://54.184.213.43:6443/version?timeout=30s: dial tcp 172.31.35.242:6443: connect: connection refused
2019/03/08 23:02:20 [INFO] cluster [c-7vbbh] provisioning: [restart/kube-controller-manager] Successfully restarted container on host [54.184.213.43]
2019/03/08 23:02:20 [INFO] cluster [c-7vbbh] provisioning: [restart/kube-scheduler] Successfully restarted container on host [54.184.213.43]
2019/03/08 23:02:20 [INFO] cluster [c-7vbbh] provisioning: [controlplane] Successfully restarted Controller Plane..
2019/03/08 23:02:20 [INFO] cluster [c-7vbbh] provisioning: [worker] Restarting Worker Plane..
2019/03/08 23:02:20 [INFO] cluster [c-7vbbh] provisioning: [restart/kubelet] Successfully restarted container on host [54.184.213.43]
2019/03/08 23:02:26 [INFO] cluster [c-7vbbh] provisioning: [restart/kube-proxy] Successfully restarted container on host [54.184.213.43]
2019/03/08 23:02:26 [INFO] cluster [c-7vbbh] provisioning: [worker] Successfully restarted Worker Plane..
2019/03/08 23:02:26 [INFO] cluster [c-7vbbh] provisioning: Restarting network, ingress, and metrics pods
E0308 23:02:28.448156 7 reflector.go:134] github.com/rancher/norman/controller/generic_controller.go:175: Failed to list *v1.RoleBinding: Get https://54.184.213.43:6443/apis/rbac.authorization.k8s.io/v1/rolebindings?limit=500&resourceVersion=0&timeout=30s: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kube-ca")
E0308 23:02:28.453516 7 reflector.go:134] github.com/rancher/norman/controller/generic_controller.go:175: Failed to list *v1.ClusterRoleBinding: Get https://54.184.213.43:6443/apis/rbac.authorization.k8s.io/v1/clusterrolebindings?limit=500&resourceVersion=0&timeout=30s: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kube-ca")
E0308 23:02:28.464744 7 reflector.go:134] github.com/rancher/norman/controller/generic_controller.go:175: Failed to list *v1.ClusterRole: Get https://54.184.213.43:6443/apis/rbac.authorization.k8s.io/v1/clusterroles?limit=500&resourceVersion=0&timeout=30s: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kube-ca")
2019/03/08 23:02:28 [ERROR] ClusterController c-7vbbh [user-controllers-controller] failed with : failed to start user controllers for cluster c-7vbbh: failed to contact server: Get https://54.184.213.43:6443/version?timeout=30s: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kube-ca")
E0308 23:02:28.616013 7 reflector.go:134] github.com/rancher/norman/controller/generic_controller.go:175: Failed to list *v1.Role: Get https://54.184.213.43:6443/apis/rbac.authorization.k8s.io/v1/roles?limit=500&resourceVersion=0&timeout=30s: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kube-ca")
```
| 1.0 | Upgrade - Rotating certificates on a cluster created pre-upgrade causes cluster to go unavailable - rancher/rancher:master-0f189f13 3/8
HA install
Rotating certificates on a cluster that was created prior to upgrading to master causes the cluster to become unavailable.
This does not occur for clusters created post-upgrade, or on a fresh-install.
To reproduce:
* Deploy Rancher - v2.1.7
* Provision RKE cluster (EC2)
* Upgrade Rancher to master
* Rotate certificates for the cluster
Expected:
* Certificates rotate and cluster is accessible
Actual:
* Certificates appear to rotate, but cluster becomes unavailable.
Logs show:
```
2019/03/08 23:02:02 [INFO] cluster [c-7vbbh] provisioning: Rebuilding Kubernetes cluster with rotated certificates
2019/03/08 23:02:02 [INFO] cluster [c-7vbbh] provisioning: [dialer] Setup tunnel for host [54.184.213.43]
2019/03/08 23:02:02 [INFO] cluster [c-7vbbh] provisioning: [certificates] Deploying kubernetes certificates to Cluster nodes
2019/03/08 23:02:07 [INFO] cluster [c-7vbbh] provisioning: [reconcile] Rebuilding and updating local kube config
I0308 23:02:07.838353 7 http.go:110] HTTP2 has been explicitly disabled
2019/03/08 23:02:07 [INFO] cluster [c-7vbbh] provisioning: Successfully Deployed local admin kubeconfig at [management-state/rke/rke-052893049/kube_config_cluster.yml]
2019/03/08 23:02:07 [INFO] cluster [c-7vbbh] provisioning: [certificates] Successfully deployed kubernetes certificates to Cluster nodes
2019/03/08 23:02:07 [INFO] cluster [c-7vbbh] provisioning: Successfully Deployed state file at [management-state/rke/rke-052893049/cluster.rkestate]
2019/03/08 23:02:07 [INFO] cluster [c-7vbbh] provisioning: [etcd] Restarting up etcd plane..
2019/03/08 23:02:13 [INFO] cluster [c-7vbbh] provisioning: [restart/etcd] Successfully restarted container on host [54.184.213.43]
2019/03/08 23:02:13 [INFO] cluster [c-7vbbh] provisioning: [etcd] Successfully restarted etcd plane..
2019/03/08 23:02:13 [INFO] cluster [c-7vbbh] provisioning: [controlplane] Restarting the Controller Plane..
2019/03/08 23:02:13 [ERROR] ClusterController c-7vbbh [user-controllers-controller] failed with : failed to start user controllers for cluster c-7vbbh: failed to contact server: Get https://54.184.213.43:6443/version?timeout=30s: dial tcp 172.31.35.242:6443: connect: connection refused
2019/03/08 23:02:14 [ERROR] ClusterController c-7vbbh [user-controllers-controller] failed with : failed to start user controllers for cluster c-7vbbh: failed to contact server: Get https://54.184.213.43:6443/version?timeout=30s: dial tcp 172.31.35.242:6443: connect: connection refused
2019/03/08 23:02:15 [ERROR] ClusterController c-7vbbh [user-controllers-controller] failed with : failed to start user controllers for cluster c-7vbbh: failed to contact server: Get https://54.184.213.43:6443/version?timeout=30s: dial tcp 172.31.35.242:6443: connect: connection refused
2019/03/08 23:02:17 [ERROR] ClusterController c-7vbbh [user-controllers-controller] failed with : failed to start user controllers for cluster c-7vbbh: failed to contact server: Get https://54.184.213.43:6443/version?timeout=30s: dial tcp 172.31.35.242:6443: connect: connection refused
E0308 23:02:18.537952 7 reflector.go:251] github.com/rancher/norman/controller/generic_controller.go:175: Failed to watch *v1.Role: Get https://54.184.213.43:6443/apis/rbac.authorization.k8s.io/v1/watch/roles?resourceVersion=498&timeout=30m0s&timeoutSeconds=439: dial tcp 172.31.35.242:6443: connect: connection refused
E0308 23:02:18.539703 7 reflector.go:251] github.com/rancher/norman/controller/generic_controller.go:175: Failed to watch *v1.Service: Get https://54.184.213.43:6443/api/v1/watch/services?resourceVersion=509&timeout=30m0s&timeoutSeconds=336: dial tcp 172.31.35.242:6443: connect: connection refused
E0308 23:02:18.539710 7 reflector.go:251] github.com/rancher/norman/controller/generic_controller.go:175: Failed to watch *v1.Namespace: Get https://54.184.213.43:6443/api/v1/watch/namespaces?resourceVersion=779&timeout=30m0s&timeoutSeconds=533: dial tcp 172.31.35.242:6443: connect: connection refused
E0308 23:02:18.539880 7 reflector.go:251] github.com/rancher/norman/controller/generic_controller.go:175: Failed to watch *v1.RoleBinding: Get https://54.184.213.43:6443/apis/rbac.authorization.k8s.io/v1/watch/rolebindings?resourceVersion=1261&timeout=30m0s&timeoutSeconds=332: dial tcp 172.31.35.242:6443: connect: connection refused
E0308 23:02:18.539912 7 reflector.go:251] github.com/rancher/norman/controller/generic_controller.go:175: Failed to watch *v1.ClusterRoleBinding: Get https://54.184.213.43:6443/apis/rbac.authorization.k8s.io/v1/watch/clusterrolebindings?resourceVersion=1279&timeout=30m0s&timeoutSeconds=364: dial tcp 172.31.35.242:6443: connect: connection refused
E0308 23:02:18.539917 7 reflector.go:251] github.com/rancher/norman/controller/generic_controller.go:175: Failed to watch *v1.ClusterRole: Get https://54.184.213.43:6443/apis/rbac.authorization.k8s.io/v1/watch/clusterroles?resourceVersion=1468&timeout=30m0s&timeoutSeconds=456: dial tcp 172.31.35.242:6443: connect: connection refused
2019/03/08 23:02:18 [INFO] cluster [c-7vbbh] provisioning: [restart/kube-apiserver] Successfully restarted container on host [54.184.213.43]
2019/03/08 23:02:18 [ERROR] ClusterController c-7vbbh [user-controllers-controller] failed with : failed to start user controllers for cluster c-7vbbh: failed to contact server: Get https://54.184.213.43:6443/version?timeout=30s: dial tcp 172.31.35.242:6443: connect: connection refused
2019/03/08 23:02:20 [INFO] cluster [c-7vbbh] provisioning: [restart/kube-controller-manager] Successfully restarted container on host [54.184.213.43]
2019/03/08 23:02:20 [INFO] cluster [c-7vbbh] provisioning: [restart/kube-scheduler] Successfully restarted container on host [54.184.213.43]
2019/03/08 23:02:20 [INFO] cluster [c-7vbbh] provisioning: [controlplane] Successfully restarted Controller Plane..
2019/03/08 23:02:20 [INFO] cluster [c-7vbbh] provisioning: [worker] Restarting Worker Plane..
2019/03/08 23:02:20 [INFO] cluster [c-7vbbh] provisioning: [restart/kubelet] Successfully restarted container on host [54.184.213.43]
2019/03/08 23:02:26 [INFO] cluster [c-7vbbh] provisioning: [restart/kube-proxy] Successfully restarted container on host [54.184.213.43]
2019/03/08 23:02:26 [INFO] cluster [c-7vbbh] provisioning: [worker] Successfully restarted Worker Plane..
2019/03/08 23:02:26 [INFO] cluster [c-7vbbh] provisioning: Restarting network, ingress, and metrics pods
E0308 23:02:28.448156 7 reflector.go:134] github.com/rancher/norman/controller/generic_controller.go:175: Failed to list *v1.RoleBinding: Get https://54.184.213.43:6443/apis/rbac.authorization.k8s.io/v1/rolebindings?limit=500&resourceVersion=0&timeout=30s: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kube-ca")
E0308 23:02:28.453516 7 reflector.go:134] github.com/rancher/norman/controller/generic_controller.go:175: Failed to list *v1.ClusterRoleBinding: Get https://54.184.213.43:6443/apis/rbac.authorization.k8s.io/v1/clusterrolebindings?limit=500&resourceVersion=0&timeout=30s: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kube-ca")
E0308 23:02:28.464744 7 reflector.go:134] github.com/rancher/norman/controller/generic_controller.go:175: Failed to list *v1.ClusterRole: Get https://54.184.213.43:6443/apis/rbac.authorization.k8s.io/v1/clusterroles?limit=500&resourceVersion=0&timeout=30s: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kube-ca")
2019/03/08 23:02:28 [ERROR] ClusterController c-7vbbh [user-controllers-controller] failed with : failed to start user controllers for cluster c-7vbbh: failed to contact server: Get https://54.184.213.43:6443/version?timeout=30s: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kube-ca")
E0308 23:02:28.616013 7 reflector.go:134] github.com/rancher/norman/controller/generic_controller.go:175: Failed to list *v1.Role: Get https://54.184.213.43:6443/apis/rbac.authorization.k8s.io/v1/roles?limit=500&resourceVersion=0&timeout=30s: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kube-ca")
```
| test | upgrade rotating certificates on a cluster created pre upgrade causes cluster to go unavailable rancher rancher master ha install rotating certificates on a cluster that was created prior to upgrading to master causes the cluster to become unavailable this does not occur for clusters created post upgrade or on a fresh install to reproduce deploy rancher provision rke cluster upgrade rancher to master rotate certificates for the cluster expected certificates rotate and cluster is accessible actual certificates appear to rotate but cluster becomes unavailable logs show cluster provisioning rebuilding kubernetes cluster with rotated certificates cluster provisioning setup tunnel for host cluster provisioning deploying kubernetes certificates to cluster nodes cluster provisioning rebuilding and updating local kube config http go has been explicitly disabled cluster provisioning successfully deployed local admin kubeconfig at cluster provisioning successfully deployed kubernetes certificates to cluster nodes cluster provisioning successfully deployed state file at cluster provisioning restarting up etcd plane cluster provisioning successfully restarted container on host cluster provisioning successfully restarted etcd plane cluster provisioning restarting the controller plane clustercontroller c failed with failed to start user controllers for cluster c failed to contact server get dial tcp connect connection refused clustercontroller c failed with failed to start user controllers for cluster c failed to contact server get dial tcp connect connection refused clustercontroller c failed with failed to start user controllers for cluster c failed to contact server get dial tcp connect connection refused clustercontroller c failed with failed to start user controllers for cluster c failed to contact server get dial tcp connect connection refused reflector go github com rancher norman controller generic controller go failed to watch role get dial tcp connect connection refused reflector go github com rancher norman controller generic controller go failed to watch service get dial tcp connect connection refused reflector go github com rancher norman controller generic controller go failed to watch namespace get dial tcp connect connection refused reflector go github com rancher norman controller generic controller go failed to watch rolebinding get dial tcp connect connection refused reflector go github com rancher norman controller generic controller go failed to watch clusterrolebinding get dial tcp connect connection refused reflector go github com rancher norman controller generic controller go failed to watch clusterrole get dial tcp connect connection refused cluster provisioning successfully restarted container on host clustercontroller c failed with failed to start user controllers for cluster c failed to contact server get dial tcp connect connection refused cluster provisioning successfully restarted container on host cluster provisioning successfully restarted container on host cluster provisioning successfully restarted controller plane cluster provisioning restarting worker plane cluster provisioning successfully restarted container on host cluster provisioning successfully restarted container on host cluster provisioning successfully restarted worker plane cluster provisioning restarting network ingress and metrics pods reflector go github com rancher norman controller generic controller go failed to list rolebinding get certificate signed by unknown authority possibly because of crypto rsa verification error while trying to verify candidate authority certificate kube ca reflector go github com rancher norman controller generic controller go failed to list clusterrolebinding get certificate signed by unknown authority possibly because of crypto rsa verification error while trying to verify candidate authority certificate kube ca reflector go github com rancher norman controller generic controller go failed to list clusterrole get certificate signed by unknown authority possibly because of crypto rsa verification error while trying to verify candidate authority certificate kube ca clustercontroller c failed with failed to start user controllers for cluster c failed to contact server get certificate signed by unknown authority possibly because of crypto rsa verification error while trying to verify candidate authority certificate kube ca reflector go github com rancher norman controller generic controller go failed to list role get certificate signed by unknown authority possibly because of crypto rsa verification error while trying to verify candidate authority certificate kube ca | 1 |
388,876 | 26,785,753,841 | IssuesEvent | 2023-02-01 02:30:25 | john-waczak/SelfOrganizingMaps.jl | https://api.github.com/repos/john-waczak/SelfOrganizingMaps.jl | opened | Documentation Update | documentation enhancement | Need to update `README.md` and github-pages documentation to reflect details of the package. | 1.0 | Documentation Update - Need to update `README.md` and github-pages documentation to reflect details of the package. | non_test | documentation update need to update readme md and github pages documentation to reflect details of the package | 0 |
765,598 | 26,853,187,132 | IssuesEvent | 2023-02-03 12:42:37 | GoogleCloudPlatform/python-docs-samples | https://api.github.com/repos/GoogleCloudPlatform/python-docs-samples | closed | monitoring.snippets.v3.uptime-check-client.snippets_test: test_update_uptime_config failed | priority: p2 type: bug api: monitoring samples flakybot: issue flakybot: flaky | This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot).
If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.
---
commit: a67f11916b0ca8f91e661d39074da866cf09c024
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/05deda49-21af-42e8-9f31-704f779be4fb), [Sponge](http://sponge2/05deda49-21af-42e8-9f31-704f779be4fb)
status: failed
<details><summary>Test output</summary><br><pre>Traceback (most recent call last):
File "/workspace/monitoring/snippets/v3/uptime-check-client/.nox/py-3-9/lib/python3.9/site-packages/google/api_core/grpc_helpers.py", line 72, in error_remapped_callable
return callable_(*args, **kwargs)
File "/workspace/monitoring/snippets/v3/uptime-check-client/.nox/py-3-9/lib/python3.9/site-packages/grpc/_channel.py", line 946, in __call__
return _end_unary_response_blocking(state, call, False, None)
File "/workspace/monitoring/snippets/v3/uptime-check-client/.nox/py-3-9/lib/python3.9/site-packages/grpc/_channel.py", line 849, in _end_unary_response_blocking
raise _InactiveRpcError(state)
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = "The service is currently unavailable."
debug_error_string = "UNKNOWN:Error received from peer ipv4:74.125.195.95:443 {grpc_message:"The service is currently unavailable.", grpc_status:14, created_time:"2023-01-07T14:02:47.467167222+00:00"}"
>
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/workspace/monitoring/snippets/v3/uptime-check-client/.nox/py-3-9/lib/python3.9/site-packages/google/api_core/retry.py", line 191, in retry_target
return target()
File "/workspace/monitoring/snippets/v3/uptime-check-client/.nox/py-3-9/lib/python3.9/site-packages/google/api_core/grpc_helpers.py", line 74, in error_remapped_callable
raise exceptions.from_grpc_error(exc) from exc
google.api_core.exceptions.ServiceUnavailable: 503 The service is currently unavailable.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/workspace/monitoring/snippets/v3/uptime-check-client/snippets_test.py", line 87, in test_update_uptime_config
assert new_uptime_check_path in out
File "/workspace/monitoring/snippets/v3/uptime-check-client/snippets_test.py", line 52, in __exit__
snippets.delete_uptime_check_config(self.config_get.name)
File "/workspace/monitoring/snippets/v3/uptime-check-client/snippets.py", line 134, in delete_uptime_check_config
client.delete_uptime_check_config(request={"name": config_name})
File "/workspace/monitoring/snippets/v3/uptime-check-client/.nox/py-3-9/lib/python3.9/site-packages/google/cloud/monitoring_v3/services/uptime_check_service/client.py", line 1003, in delete_uptime_check_config
rpc(
File "/workspace/monitoring/snippets/v3/uptime-check-client/.nox/py-3-9/lib/python3.9/site-packages/google/api_core/gapic_v1/method.py", line 113, in __call__
return wrapped_func(*args, **kwargs)
File "/workspace/monitoring/snippets/v3/uptime-check-client/.nox/py-3-9/lib/python3.9/site-packages/google/api_core/retry.py", line 349, in retry_wrapped_func
return retry_target(
File "/workspace/monitoring/snippets/v3/uptime-check-client/.nox/py-3-9/lib/python3.9/site-packages/google/api_core/retry.py", line 207, in retry_target
raise exceptions.RetryError(
google.api_core.exceptions.RetryError: Deadline of 30.0s exceeded while calling target function, last exception: 503 The service is currently unavailable.</pre></details> | 1.0 | monitoring.snippets.v3.uptime-check-client.snippets_test: test_update_uptime_config failed - This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot).
If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.
---
commit: a67f11916b0ca8f91e661d39074da866cf09c024
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/05deda49-21af-42e8-9f31-704f779be4fb), [Sponge](http://sponge2/05deda49-21af-42e8-9f31-704f779be4fb)
status: failed
<details><summary>Test output</summary><br><pre>Traceback (most recent call last):
File "/workspace/monitoring/snippets/v3/uptime-check-client/.nox/py-3-9/lib/python3.9/site-packages/google/api_core/grpc_helpers.py", line 72, in error_remapped_callable
return callable_(*args, **kwargs)
File "/workspace/monitoring/snippets/v3/uptime-check-client/.nox/py-3-9/lib/python3.9/site-packages/grpc/_channel.py", line 946, in __call__
return _end_unary_response_blocking(state, call, False, None)
File "/workspace/monitoring/snippets/v3/uptime-check-client/.nox/py-3-9/lib/python3.9/site-packages/grpc/_channel.py", line 849, in _end_unary_response_blocking
raise _InactiveRpcError(state)
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = "The service is currently unavailable."
debug_error_string = "UNKNOWN:Error received from peer ipv4:74.125.195.95:443 {grpc_message:"The service is currently unavailable.", grpc_status:14, created_time:"2023-01-07T14:02:47.467167222+00:00"}"
>
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/workspace/monitoring/snippets/v3/uptime-check-client/.nox/py-3-9/lib/python3.9/site-packages/google/api_core/retry.py", line 191, in retry_target
return target()
File "/workspace/monitoring/snippets/v3/uptime-check-client/.nox/py-3-9/lib/python3.9/site-packages/google/api_core/grpc_helpers.py", line 74, in error_remapped_callable
raise exceptions.from_grpc_error(exc) from exc
google.api_core.exceptions.ServiceUnavailable: 503 The service is currently unavailable.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/workspace/monitoring/snippets/v3/uptime-check-client/snippets_test.py", line 87, in test_update_uptime_config
assert new_uptime_check_path in out
File "/workspace/monitoring/snippets/v3/uptime-check-client/snippets_test.py", line 52, in __exit__
snippets.delete_uptime_check_config(self.config_get.name)
File "/workspace/monitoring/snippets/v3/uptime-check-client/snippets.py", line 134, in delete_uptime_check_config
client.delete_uptime_check_config(request={"name": config_name})
File "/workspace/monitoring/snippets/v3/uptime-check-client/.nox/py-3-9/lib/python3.9/site-packages/google/cloud/monitoring_v3/services/uptime_check_service/client.py", line 1003, in delete_uptime_check_config
rpc(
File "/workspace/monitoring/snippets/v3/uptime-check-client/.nox/py-3-9/lib/python3.9/site-packages/google/api_core/gapic_v1/method.py", line 113, in __call__
return wrapped_func(*args, **kwargs)
File "/workspace/monitoring/snippets/v3/uptime-check-client/.nox/py-3-9/lib/python3.9/site-packages/google/api_core/retry.py", line 349, in retry_wrapped_func
return retry_target(
File "/workspace/monitoring/snippets/v3/uptime-check-client/.nox/py-3-9/lib/python3.9/site-packages/google/api_core/retry.py", line 207, in retry_target
raise exceptions.RetryError(
google.api_core.exceptions.RetryError: Deadline of 30.0s exceeded while calling target function, last exception: 503 The service is currently unavailable.</pre></details> | non_test | monitoring snippets uptime check client snippets test test update uptime config failed this test failed to configure my behavior see if i m commenting on this issue too often add the flakybot quiet label and i will stop commenting commit buildurl status failed test output traceback most recent call last file workspace monitoring snippets uptime check client nox py lib site packages google api core grpc helpers py line in error remapped callable return callable args kwargs file workspace monitoring snippets uptime check client nox py lib site packages grpc channel py line in call return end unary response blocking state call false none file workspace monitoring snippets uptime check client nox py lib site packages grpc channel py line in end unary response blocking raise inactiverpcerror state grpc channel inactiverpcerror inactiverpcerror of rpc that terminated with status statuscode unavailable details the service is currently unavailable debug error string unknown error received from peer grpc message the service is currently unavailable grpc status created time the above exception was the direct cause of the following exception traceback most recent call last file workspace monitoring snippets uptime check client nox py lib site packages google api core retry py line in retry target return target file workspace monitoring snippets uptime check client nox py lib site packages google api core grpc helpers py line in error remapped callable raise exceptions from grpc error exc from exc google api core exceptions serviceunavailable the service is currently unavailable the above exception was the direct cause of the following exception traceback most recent call last file workspace monitoring snippets uptime check client snippets test py line in test update uptime config assert new uptime check path in out file workspace monitoring snippets uptime check client snippets test py line in exit snippets delete uptime check config self config get name file workspace monitoring snippets uptime check client snippets py line in delete uptime check config client delete uptime check config request name config name file workspace monitoring snippets uptime check client nox py lib site packages google cloud monitoring services uptime check service client py line in delete uptime check config rpc file workspace monitoring snippets uptime check client nox py lib site packages google api core gapic method py line in call return wrapped func args kwargs file workspace monitoring snippets uptime check client nox py lib site packages google api core retry py line in retry wrapped func return retry target file workspace monitoring snippets uptime check client nox py lib site packages google api core retry py line in retry target raise exceptions retryerror google api core exceptions retryerror deadline of exceeded while calling target function last exception the service is currently unavailable | 0 |
797,680 | 28,151,787,271 | IssuesEvent | 2023-04-03 02:21:15 | tahowallet/extension | https://api.github.com/repos/tahowallet/extension | opened | Implement Show Recovery Phrase menu option and initial Show Recovery Phrase screen | Type: Enhancement Priority: High Status: Available | https://www.figma.com/file/q8gfu9XTbYBF07KMnDCtsD/UI---Dark?node-id=17769%3A334818&t=NBripafp5rsqcxWM-1
<img width="970" alt="image" src="https://user-images.githubusercontent.com/94649004/229396662-79515b1a-8c1a-4fcf-ac34-0d8311a97de3.png">
- [ ] Clicking `Show Recovery Phrase` should prompt for password regardless of it wallet is already unlocked or not.
- [ ] Implementing the functionality of the `Show Recovery Phrase` screen is not necessary to complete this ticket.
| 1.0 | Implement Show Recovery Phrase menu option and initial Show Recovery Phrase screen - https://www.figma.com/file/q8gfu9XTbYBF07KMnDCtsD/UI---Dark?node-id=17769%3A334818&t=NBripafp5rsqcxWM-1
<img width="970" alt="image" src="https://user-images.githubusercontent.com/94649004/229396662-79515b1a-8c1a-4fcf-ac34-0d8311a97de3.png">
- [ ] Clicking `Show Recovery Phrase` should prompt for password regardless of it wallet is already unlocked or not.
- [ ] Implementing the functionality of the `Show Recovery Phrase` screen is not necessary to complete this ticket.
| non_test | implement show recovery phrase menu option and initial show recovery phrase screen img width alt image src clicking show recovery phrase should prompt for password regardless of it wallet is already unlocked or not implementing the functionality of the show recovery phrase screen is not necessary to complete this ticket | 0 |
284,451 | 30,913,633,069 | IssuesEvent | 2023-08-05 02:27:13 | Nivaskumark/kernel_v4.19.72_old | https://api.github.com/repos/Nivaskumark/kernel_v4.19.72_old | opened | CVE-2023-3390 (High) detected in linux-yoctov5.4.51 | Mend: dependency security vulnerability | ## CVE-2023-3390 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yoctov5.4.51</b></p></summary>
<p>
<p>Yocto Linux Embedded kernel</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto>https://git.yoctoproject.org/git/linux-yocto</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Nivaskumark/kernel_v4.19.72/commit/ce49083a1c14be2d13cb5e878257d293e6c748bc">ce49083a1c14be2d13cb5e878257d293e6c748bc</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/netfilter/nf_tables_api.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
A use-after-free vulnerability was found in the Linux kernel's netfilter subsystem in net/netfilter/nf_tables_api.c.
Mishandled error handling with NFT_MSG_NEWRULE makes it possible to use a dangling pointer in the same transaction causing a use-after-free vulnerability. This flaw allows a local attacker with user access to cause a privilege escalation issue.
We recommend upgrading past commit 1240eb93f0616b21c675416516ff3d74798fdc97.
<p>Publish Date: 2023-06-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-3390>CVE-2023-3390</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.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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://www.linuxkernelcves.com/cves/CVE-2023-3390">https://www.linuxkernelcves.com/cves/CVE-2023-3390</a></p>
<p>Release Date: 2023-06-28</p>
<p>Fix Resolution: v5.15.118,v6.1.35,v6.3.9,v6.4-rc7</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2023-3390 (High) detected in linux-yoctov5.4.51 - ## CVE-2023-3390 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-yoctov5.4.51</b></p></summary>
<p>
<p>Yocto Linux Embedded kernel</p>
<p>Library home page: <a href=https://git.yoctoproject.org/git/linux-yocto>https://git.yoctoproject.org/git/linux-yocto</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Nivaskumark/kernel_v4.19.72/commit/ce49083a1c14be2d13cb5e878257d293e6c748bc">ce49083a1c14be2d13cb5e878257d293e6c748bc</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/netfilter/nf_tables_api.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
A use-after-free vulnerability was found in the Linux kernel's netfilter subsystem in net/netfilter/nf_tables_api.c.
Mishandled error handling with NFT_MSG_NEWRULE makes it possible to use a dangling pointer in the same transaction causing a use-after-free vulnerability. This flaw allows a local attacker with user access to cause a privilege escalation issue.
We recommend upgrading past commit 1240eb93f0616b21c675416516ff3d74798fdc97.
<p>Publish Date: 2023-06-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-3390>CVE-2023-3390</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.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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://www.linuxkernelcves.com/cves/CVE-2023-3390">https://www.linuxkernelcves.com/cves/CVE-2023-3390</a></p>
<p>Release Date: 2023-06-28</p>
<p>Fix Resolution: v5.15.118,v6.1.35,v6.3.9,v6.4-rc7</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_test | cve high detected in linux cve high severity vulnerability vulnerable library linux yocto linux embedded kernel library home page a href found in head commit a href found in base branch master vulnerable source files net netfilter nf tables api c vulnerability details a use after free vulnerability was found in the linux kernel s netfilter subsystem in net netfilter nf tables api c mishandled error handling with nft msg newrule makes it possible to use a dangling pointer in the same transaction causing a use after free vulnerability this flaw allows a local attacker with user access to cause a privilege escalation issue we recommend upgrading past commit publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact 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 step up your open source security game with mend | 0 |
83,943 | 15,720,762,317 | IssuesEvent | 2021-03-29 01:07:30 | andygonzalez2010/store | https://api.github.com/repos/andygonzalez2010/store | opened | CVE-2021-23362 (Medium) detected in hosted-git-info-2.7.1.tgz | security vulnerability | ## CVE-2021-23362 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hosted-git-info-2.7.1.tgz</b></p></summary>
<p>Provides metadata and conversions from repository urls for Github, Bitbucket and Gitlab</p>
<p>Library home page: <a href="https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.7.1.tgz">https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.7.1.tgz</a></p>
<p>Path to dependency file: store/package.json</p>
<p>Path to vulnerable library: store/node_modules/hosted-git-info/package.json</p>
<p>
Dependency Hierarchy:
- generator-jhipster-6.0.1.tgz (Root Library)
- meow-5.0.0.tgz
- normalize-package-data-2.5.0.tgz
- :x: **hosted-git-info-2.7.1.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package hosted-git-info before 3.0.8 are vulnerable to Regular Expression Denial of Service (ReDoS) via shortcutMatch in fromUrl().
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23362>CVE-2021-23362</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: None
- 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/npm/hosted-git-info/releases/tag/v3.0.8">https://github.com/npm/hosted-git-info/releases/tag/v3.0.8</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: hosted-git-info - 3.0.8</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-23362 (Medium) detected in hosted-git-info-2.7.1.tgz - ## CVE-2021-23362 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hosted-git-info-2.7.1.tgz</b></p></summary>
<p>Provides metadata and conversions from repository urls for Github, Bitbucket and Gitlab</p>
<p>Library home page: <a href="https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.7.1.tgz">https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.7.1.tgz</a></p>
<p>Path to dependency file: store/package.json</p>
<p>Path to vulnerable library: store/node_modules/hosted-git-info/package.json</p>
<p>
Dependency Hierarchy:
- generator-jhipster-6.0.1.tgz (Root Library)
- meow-5.0.0.tgz
- normalize-package-data-2.5.0.tgz
- :x: **hosted-git-info-2.7.1.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package hosted-git-info before 3.0.8 are vulnerable to Regular Expression Denial of Service (ReDoS) via shortcutMatch in fromUrl().
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23362>CVE-2021-23362</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: None
- 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/npm/hosted-git-info/releases/tag/v3.0.8">https://github.com/npm/hosted-git-info/releases/tag/v3.0.8</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: hosted-git-info - 3.0.8</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 hosted git info tgz cve medium severity vulnerability vulnerable library hosted git info tgz provides metadata and conversions from repository urls for github bitbucket and gitlab library home page a href path to dependency file store package json path to vulnerable library store node modules hosted git info package json dependency hierarchy generator jhipster tgz root library meow tgz normalize package data tgz x hosted git info tgz vulnerable library found in base branch master vulnerability details the package hosted git info before are vulnerable to regular expression denial of service redos via shortcutmatch in fromurl publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution hosted git info step up your open source security game with whitesource | 0 |
347,619 | 31,235,292,243 | IssuesEvent | 2023-08-20 07:38:01 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | ccl/multiregionccl: TestRegionAddDropWithConcurrentBackupOps failed | C-test-failure O-robot branch-master T-sql-foundations | ccl/multiregionccl.TestRegionAddDropWithConcurrentBackupOps [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/11401737?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/11401737?buildTab=artifacts#/) on master @ [31fe139c74640a383599c53719a39f0190a7065d](https://github.com/cockroachdb/cockroach/commits/31fe139c74640a383599c53719a39f0190a7065d):
Fatal error:
```
panic: use of Span after Finish. Span: /cockroach.roachpb.Internal/Batch. Finish previously called at: <stack not captured. Set debugUseAfterFinish> [recovered]
panic: use of Span after Finish. Span: /cockroach.roachpb.Internal/Batch. Finish previously called at: <stack not captured. Set debugUseAfterFinish>
```
Stack:
```
goroutine 164288838 [running]:
github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).recover(0x3bc2bea?, {0x7a21e80, 0xc0602352f0})
github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:230 +0x6a
panic({0x5cb9c60, 0xc023dac450})
GOROOT/src/runtime/panic.go:884 +0x212
github.com/cockroachdb/cockroach/pkg/util/tracing.(*Span).detectUseAfterFinish(0x7a21e80?)
github.com/cockroachdb/cockroach/pkg/util/tracing/span.go:182 +0x12e
github.com/cockroachdb/cockroach/pkg/util/tracing.(*Span).Tracer(...)
github.com/cockroachdb/cockroach/pkg/util/tracing/span.go:225
github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*replicaDecoder).createTracingSpans(0xc008f190d8, {0x7a21e80, 0xc01ba6dd70})
github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/replica_application_decoder.go:154 +0x4f0
github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*replicaDecoder).DecodeAndBind(0xc008f18c80?, {0x7a21e80, 0xc01ba6dd70}, {0xc027500000?, 0x2?, 0x10?})
github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/replica_application_decoder.go:63 +0x66
github.com/cockroachdb/cockroach/pkg/kv/kvserver/apply.(*Task).Decode(...)
github.com/cockroachdb/cockroach/pkg/kv/kvserver/apply/task.go:142
github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*Replica).handleRaftReadyRaftMuLocked(_, {_, _}, {{0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...}, ...})
github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/replica_raft.go:878 +0x73a
github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*Replica).handleRaftReady(_, {_, _}, {{0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...}, ...})
github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/replica_raft.go:728 +0x190
github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*Store).processReady(0xc00c99a000, 0x7a21e80?)
github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/store_raft.go:689 +0x145
github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*raftSchedulerShard).worker(0xc0045c4620, {0x7a21e80, 0xc0602352f0}, {0x7a052d0, 0xc00c99a000}, 0xc015948a80)
github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/scheduler.go:418 +0x195
github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*raftScheduler).Start.func2({0x7a21e80?, 0xc0602352f0?})
github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/scheduler.go:321 +0x45
github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTaskEx.func2()
github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:484 +0x146
created by github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTaskEx
github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:475 +0x43b
```
<details><summary>Log preceding fatal error</summary>
<p>
```
=== RUN TestRegionAddDropWithConcurrentBackupOps
test_log_scope.go:167: test logs captured to: /artifacts/tmp/_tmp/e558fc8050776f4c54ea39ba371b49da/logTestRegionAddDropWithConcurrentBackupOps1039750523
test_log_scope.go:81: use -show-logs to present logs inline
=== RUN TestRegionAddDropWithConcurrentBackupOps/drop-region-fail-backup-database
=== RUN TestRegionAddDropWithConcurrentBackupOps/drop-region-succeed-backup-database
*
* ERROR: a panic has occurred!
* use of Span after Finish. Span: /cockroach.roachpb.Internal/Batch. Finish previously called at: <stack not captured. Set debugUseAfterFinish>
* (1) attached stack trace
* -- stack trace:
* | runtime.gopanic
* | GOROOT/src/runtime/panic.go:884
* | [...repeated from below...]
* Wraps: (2) assertion failure
* Wraps: (3) attached stack trace
* -- stack trace:
* | github.com/cockroachdb/cockroach/pkg/util/tracing.(*Span).detectUseAfterFinish
* | github.com/cockroachdb/cockroach/pkg/util/tracing/span.go:182
* | github.com/cockroachdb/cockroach/pkg/util/tracing.(*Span).Tracer
* | github.com/cockroachdb/cockroach/pkg/util/tracing/span.go:225
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*replicaDecoder).createTracingSpans
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/replica_application_decoder.go:154
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*replicaDecoder).DecodeAndBind
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/replica_application_decoder.go:63
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver/apply.(*Task).Decode
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver/apply/task.go:142
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*Replica).handleRaftReadyRaftMuLocked
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/replica_raft.go:878
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*Replica).handleRaftReady
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/replica_raft.go:728
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*Store).processReady
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/store_raft.go:689
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*raftSchedulerShard).worker
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/scheduler.go:418
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*raftScheduler).Start.func2
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/scheduler.go:321
* | github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTaskEx.func2
* | github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:484
* | runtime.goexit
* | GOROOT/src/runtime/asm_amd64.s:1594
* Wraps: (4) use of Span after Finish. Span: /cockroach.roachpb.Internal/Batch. Finish previously called at: <stack not captured. Set debugUseAfterFinish>
* Error types: (1) *withstack.withStack (2) *assert.withAssertionFailure (3) *withstack.withStack (4) *errutil.leafError
*
```
</p>
</details>
<p>Parameters: <code>TAGS=bazel,gss,deadlock</code>
, <code>stress=true</code>
</p>
<details><summary>Help</summary>
<p>
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
</p>
</details>
/cc @cockroachdb/sql-foundations
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestRegionAddDropWithConcurrentBackupOps.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| 1.0 | ccl/multiregionccl: TestRegionAddDropWithConcurrentBackupOps failed - ccl/multiregionccl.TestRegionAddDropWithConcurrentBackupOps [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/11401737?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/11401737?buildTab=artifacts#/) on master @ [31fe139c74640a383599c53719a39f0190a7065d](https://github.com/cockroachdb/cockroach/commits/31fe139c74640a383599c53719a39f0190a7065d):
Fatal error:
```
panic: use of Span after Finish. Span: /cockroach.roachpb.Internal/Batch. Finish previously called at: <stack not captured. Set debugUseAfterFinish> [recovered]
panic: use of Span after Finish. Span: /cockroach.roachpb.Internal/Batch. Finish previously called at: <stack not captured. Set debugUseAfterFinish>
```
Stack:
```
goroutine 164288838 [running]:
github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).recover(0x3bc2bea?, {0x7a21e80, 0xc0602352f0})
github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:230 +0x6a
panic({0x5cb9c60, 0xc023dac450})
GOROOT/src/runtime/panic.go:884 +0x212
github.com/cockroachdb/cockroach/pkg/util/tracing.(*Span).detectUseAfterFinish(0x7a21e80?)
github.com/cockroachdb/cockroach/pkg/util/tracing/span.go:182 +0x12e
github.com/cockroachdb/cockroach/pkg/util/tracing.(*Span).Tracer(...)
github.com/cockroachdb/cockroach/pkg/util/tracing/span.go:225
github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*replicaDecoder).createTracingSpans(0xc008f190d8, {0x7a21e80, 0xc01ba6dd70})
github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/replica_application_decoder.go:154 +0x4f0
github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*replicaDecoder).DecodeAndBind(0xc008f18c80?, {0x7a21e80, 0xc01ba6dd70}, {0xc027500000?, 0x2?, 0x10?})
github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/replica_application_decoder.go:63 +0x66
github.com/cockroachdb/cockroach/pkg/kv/kvserver/apply.(*Task).Decode(...)
github.com/cockroachdb/cockroach/pkg/kv/kvserver/apply/task.go:142
github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*Replica).handleRaftReadyRaftMuLocked(_, {_, _}, {{0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...}, ...})
github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/replica_raft.go:878 +0x73a
github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*Replica).handleRaftReady(_, {_, _}, {{0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...}, ...})
github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/replica_raft.go:728 +0x190
github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*Store).processReady(0xc00c99a000, 0x7a21e80?)
github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/store_raft.go:689 +0x145
github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*raftSchedulerShard).worker(0xc0045c4620, {0x7a21e80, 0xc0602352f0}, {0x7a052d0, 0xc00c99a000}, 0xc015948a80)
github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/scheduler.go:418 +0x195
github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*raftScheduler).Start.func2({0x7a21e80?, 0xc0602352f0?})
github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/scheduler.go:321 +0x45
github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTaskEx.func2()
github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:484 +0x146
created by github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTaskEx
github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:475 +0x43b
```
<details><summary>Log preceding fatal error</summary>
<p>
```
=== RUN TestRegionAddDropWithConcurrentBackupOps
test_log_scope.go:167: test logs captured to: /artifacts/tmp/_tmp/e558fc8050776f4c54ea39ba371b49da/logTestRegionAddDropWithConcurrentBackupOps1039750523
test_log_scope.go:81: use -show-logs to present logs inline
=== RUN TestRegionAddDropWithConcurrentBackupOps/drop-region-fail-backup-database
=== RUN TestRegionAddDropWithConcurrentBackupOps/drop-region-succeed-backup-database
*
* ERROR: a panic has occurred!
* use of Span after Finish. Span: /cockroach.roachpb.Internal/Batch. Finish previously called at: <stack not captured. Set debugUseAfterFinish>
* (1) attached stack trace
* -- stack trace:
* | runtime.gopanic
* | GOROOT/src/runtime/panic.go:884
* | [...repeated from below...]
* Wraps: (2) assertion failure
* Wraps: (3) attached stack trace
* -- stack trace:
* | github.com/cockroachdb/cockroach/pkg/util/tracing.(*Span).detectUseAfterFinish
* | github.com/cockroachdb/cockroach/pkg/util/tracing/span.go:182
* | github.com/cockroachdb/cockroach/pkg/util/tracing.(*Span).Tracer
* | github.com/cockroachdb/cockroach/pkg/util/tracing/span.go:225
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*replicaDecoder).createTracingSpans
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/replica_application_decoder.go:154
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*replicaDecoder).DecodeAndBind
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/replica_application_decoder.go:63
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver/apply.(*Task).Decode
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver/apply/task.go:142
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*Replica).handleRaftReadyRaftMuLocked
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/replica_raft.go:878
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*Replica).handleRaftReady
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/replica_raft.go:728
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*Store).processReady
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/store_raft.go:689
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*raftSchedulerShard).worker
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/scheduler.go:418
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver.(*raftScheduler).Start.func2
* | github.com/cockroachdb/cockroach/pkg/kv/kvserver/pkg/kv/kvserver/scheduler.go:321
* | github.com/cockroachdb/cockroach/pkg/util/stop.(*Stopper).RunAsyncTaskEx.func2
* | github.com/cockroachdb/cockroach/pkg/util/stop/stopper.go:484
* | runtime.goexit
* | GOROOT/src/runtime/asm_amd64.s:1594
* Wraps: (4) use of Span after Finish. Span: /cockroach.roachpb.Internal/Batch. Finish previously called at: <stack not captured. Set debugUseAfterFinish>
* Error types: (1) *withstack.withStack (2) *assert.withAssertionFailure (3) *withstack.withStack (4) *errutil.leafError
*
```
</p>
</details>
<p>Parameters: <code>TAGS=bazel,gss,deadlock</code>
, <code>stress=true</code>
</p>
<details><summary>Help</summary>
<p>
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
</p>
</details>
/cc @cockroachdb/sql-foundations
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestRegionAddDropWithConcurrentBackupOps.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| test | ccl multiregionccl testregionadddropwithconcurrentbackupops failed ccl multiregionccl testregionadddropwithconcurrentbackupops with on master fatal error panic use of span after finish span cockroach roachpb internal batch finish previously called at panic use of span after finish span cockroach roachpb internal batch finish previously called at stack goroutine github com cockroachdb cockroach pkg util stop stopper recover github com cockroachdb cockroach pkg util stop stopper go panic goroot src runtime panic go github com cockroachdb cockroach pkg util tracing span detectuseafterfinish github com cockroachdb cockroach pkg util tracing span go github com cockroachdb cockroach pkg util tracing span tracer github com cockroachdb cockroach pkg util tracing span go github com cockroachdb cockroach pkg kv kvserver replicadecoder createtracingspans github com cockroachdb cockroach pkg kv kvserver pkg kv kvserver replica application decoder go github com cockroachdb cockroach pkg kv kvserver replicadecoder decodeandbind github com cockroachdb cockroach pkg kv kvserver pkg kv kvserver replica application decoder go github com cockroachdb cockroach pkg kv kvserver apply task decode github com cockroachdb cockroach pkg kv kvserver apply task go github com cockroachdb cockroach pkg kv kvserver replica handleraftreadyraftmulocked github com cockroachdb cockroach pkg kv kvserver pkg kv kvserver replica raft go github com cockroachdb cockroach pkg kv kvserver replica handleraftready github com cockroachdb cockroach pkg kv kvserver pkg kv kvserver replica raft go github com cockroachdb cockroach pkg kv kvserver store processready github com cockroachdb cockroach pkg kv kvserver pkg kv kvserver store raft go github com cockroachdb cockroach pkg kv kvserver raftschedulershard worker github com cockroachdb cockroach pkg kv kvserver pkg kv kvserver scheduler go github com cockroachdb cockroach pkg kv kvserver raftscheduler start github com cockroachdb cockroach pkg kv kvserver pkg kv kvserver scheduler go github com cockroachdb cockroach pkg util stop stopper runasynctaskex github com cockroachdb cockroach pkg util stop stopper go created by github com cockroachdb cockroach pkg util stop stopper runasynctaskex github com cockroachdb cockroach pkg util stop stopper go log preceding fatal error run testregionadddropwithconcurrentbackupops test log scope go test logs captured to artifacts tmp tmp test log scope go use show logs to present logs inline run testregionadddropwithconcurrentbackupops drop region fail backup database run testregionadddropwithconcurrentbackupops drop region succeed backup database error a panic has occurred use of span after finish span cockroach roachpb internal batch finish previously called at attached stack trace stack trace runtime gopanic goroot src runtime panic go wraps assertion failure wraps attached stack trace stack trace github com cockroachdb cockroach pkg util tracing span detectuseafterfinish github com cockroachdb cockroach pkg util tracing span go github com cockroachdb cockroach pkg util tracing span tracer github com cockroachdb cockroach pkg util tracing span go github com cockroachdb cockroach pkg kv kvserver replicadecoder createtracingspans github com cockroachdb cockroach pkg kv kvserver pkg kv kvserver replica application decoder go github com cockroachdb cockroach pkg kv kvserver replicadecoder decodeandbind github com cockroachdb cockroach pkg kv kvserver pkg kv kvserver replica application decoder go github com cockroachdb cockroach pkg kv kvserver apply task decode github com cockroachdb cockroach pkg kv kvserver apply task go github com cockroachdb cockroach pkg kv kvserver replica handleraftreadyraftmulocked github com cockroachdb cockroach pkg kv kvserver pkg kv kvserver replica raft go github com cockroachdb cockroach pkg kv kvserver replica handleraftready github com cockroachdb cockroach pkg kv kvserver pkg kv kvserver replica raft go github com cockroachdb cockroach pkg kv kvserver store processready github com cockroachdb cockroach pkg kv kvserver pkg kv kvserver store raft go github com cockroachdb cockroach pkg kv kvserver raftschedulershard worker github com cockroachdb cockroach pkg kv kvserver pkg kv kvserver scheduler go github com cockroachdb cockroach pkg kv kvserver raftscheduler start github com cockroachdb cockroach pkg kv kvserver pkg kv kvserver scheduler go github com cockroachdb cockroach pkg util stop stopper runasynctaskex github com cockroachdb cockroach pkg util stop stopper go runtime goexit goroot src runtime asm s wraps use of span after finish span cockroach roachpb internal batch finish previously called at error types withstack withstack assert withassertionfailure withstack withstack errutil leaferror parameters tags bazel gss deadlock stress true help see also cc cockroachdb sql foundations | 1 |
707,272 | 24,300,689,441 | IssuesEvent | 2022-09-29 13:39:55 | dotCMS/core | https://api.github.com/repos/dotCMS/core | opened | Set language in docker image to C.UTF8 | Type : Bug Severity : Support Priority Maintenance Sprint | Our docker image is set to using a non UTF8 language as its default. The result of this is that we cannot store files that contain extended characters in their names. The fix for this is to set the environmental variable `lang` in our docker image to `C.UTF8`. You can see this work by adding the environmental variable to a docker config:
```
environment:
LANG: 'C.UTF-8'
```
To test example create a PDF file called `July groups – net adjustment results (145 KB PDF), updated May 2019.pdf` and try to upload it into a dockerized dotCMS. This will fail with a message like:
```
[28/09/22 21:04:37:340 UTC] ERROR temp.TempFileResource: Malformed input or input contains unmappable characters: /data/shared/assets/tmp_upload/temp_a547a9e844/July groups â€Â" net adjustment results (145 KB PDF), updated May 2019.pdf
com.dotmarketing.exception.DotRuntimeException: Malformed input or input contains unmappable characters: /data/shared/assets/tmp_upload/temp_a547a9e844/July groups â€Â" net adjustment results (145 KB PDF), updated May 2019.pdf
at com.dotcms.rest.api.v1.temp.TempFileAPI.createTempFile(TempFileAPI.java:185) ~[dotcms_22.03.2_999999.jar:?]
at com.dotcms.rest.api.v1.temp.TempFileResource.lambda$0(TempFileResource.java:171) ~[dotcms_22.03.2_999999.jar:?]
Caused by: java.nio.file.InvalidPathException: Malformed input or input contains unmappable characters: /data/shared/assets/tmp_upload/temp_a547a9e844/July groups â€Â" net adjustment results (145 KB PDF), updated May 2019.pdf
at com.dotcms.rest.api.v1.temp.TempFileAPI.createTempFile(TempFileAPI.java:172) ~[dotcms_22.03.2_999999.jar:?]
... 7 more
```
export LANG=C.UTF8 | 1.0 | Set language in docker image to C.UTF8 - Our docker image is set to using a non UTF8 language as its default. The result of this is that we cannot store files that contain extended characters in their names. The fix for this is to set the environmental variable `lang` in our docker image to `C.UTF8`. You can see this work by adding the environmental variable to a docker config:
```
environment:
LANG: 'C.UTF-8'
```
To test example create a PDF file called `July groups – net adjustment results (145 KB PDF), updated May 2019.pdf` and try to upload it into a dockerized dotCMS. This will fail with a message like:
```
[28/09/22 21:04:37:340 UTC] ERROR temp.TempFileResource: Malformed input or input contains unmappable characters: /data/shared/assets/tmp_upload/temp_a547a9e844/July groups â€Â" net adjustment results (145 KB PDF), updated May 2019.pdf
com.dotmarketing.exception.DotRuntimeException: Malformed input or input contains unmappable characters: /data/shared/assets/tmp_upload/temp_a547a9e844/July groups â€Â" net adjustment results (145 KB PDF), updated May 2019.pdf
at com.dotcms.rest.api.v1.temp.TempFileAPI.createTempFile(TempFileAPI.java:185) ~[dotcms_22.03.2_999999.jar:?]
at com.dotcms.rest.api.v1.temp.TempFileResource.lambda$0(TempFileResource.java:171) ~[dotcms_22.03.2_999999.jar:?]
Caused by: java.nio.file.InvalidPathException: Malformed input or input contains unmappable characters: /data/shared/assets/tmp_upload/temp_a547a9e844/July groups â€Â" net adjustment results (145 KB PDF), updated May 2019.pdf
at com.dotcms.rest.api.v1.temp.TempFileAPI.createTempFile(TempFileAPI.java:172) ~[dotcms_22.03.2_999999.jar:?]
... 7 more
```
export LANG=C.UTF8 | non_test | set language in docker image to c our docker image is set to using a non language as its default the result of this is that we cannot store files that contain extended characters in their names the fix for this is to set the environmental variable lang in our docker image to c you can see this work by adding the environmental variable to a docker config environment lang c utf to test example create a pdf file called july groups – net adjustment results kb pdf updated may pdf and try to upload it into a dockerized dotcms this will fail with a message like error temp tempfileresource malformed input or input contains unmappable characters data shared assets tmp upload temp july groups ã¢â€â net adjustment results kb pdf updated may pdf com dotmarketing exception dotruntimeexception malformed input or input contains unmappable characters data shared assets tmp upload temp july groups ã¢â€â net adjustment results kb pdf updated may pdf at com dotcms rest api temp tempfileapi createtempfile tempfileapi java at com dotcms rest api temp tempfileresource lambda tempfileresource java caused by java nio file invalidpathexception malformed input or input contains unmappable characters data shared assets tmp upload temp july groups ã¢â€â net adjustment results kb pdf updated may pdf at com dotcms rest api temp tempfileapi createtempfile tempfileapi java more export lang c | 0 |
158,182 | 12,405,427,030 | IssuesEvent | 2020-05-21 17:15:19 | HMIS/LSASampleCode | https://api.github.com/repos/HMIS/LSASampleCode | closed | Test Data - Inventory designated beds issues | Test Kit Data | InventoryID = 4083317,
- HouseholdType = 4 (Households with only Children)
- Designated beds for this Inventory include CHVetBeds, VetBed, CHBeds
- For HouseholdType 4, we have no way to add this type of designated beds to the inventory.
InventoryID = 4083318,
- HouseholdType = 3 (Households with at least one adult and one child)
- Designated beds for this Inventory include CHYouthBedInventory
- For HouseholdType 3, we have no way to add this type of designated bed to the inventory.
| 1.0 | Test Data - Inventory designated beds issues - InventoryID = 4083317,
- HouseholdType = 4 (Households with only Children)
- Designated beds for this Inventory include CHVetBeds, VetBed, CHBeds
- For HouseholdType 4, we have no way to add this type of designated beds to the inventory.
InventoryID = 4083318,
- HouseholdType = 3 (Households with at least one adult and one child)
- Designated beds for this Inventory include CHYouthBedInventory
- For HouseholdType 3, we have no way to add this type of designated bed to the inventory.
| test | test data inventory designated beds issues inventoryid householdtype households with only children designated beds for this inventory include chvetbeds vetbed chbeds for householdtype we have no way to add this type of designated beds to the inventory inventoryid householdtype households with at least one adult and one child designated beds for this inventory include chyouthbedinventory for householdtype we have no way to add this type of designated bed to the inventory | 1 |
43,510 | 23,269,903,607 | IssuesEvent | 2022-08-04 21:32:06 | WDscholia/scholia | https://api.github.com/repos/WDscholia/scholia | opened | Add LIMITs to queries on the software profile | SPARQL performance | **What query is this about**
Please provide a link to a Scholia profile and the appropriate section heading and/ or .sparql file.
On well-curated software profiles like [that for ImageJ](https://scholia.toolforge.org/software/Q1659584), some of the queries — especially the one for [Topics of works using the software](https://scholia.toolforge.org/software/Q1659584#topics) are too busy, putting strain on Query Service and browser.
**What change do you propose, and why?**
We should add LIMITs to software_topics.sparql and also review the other queries on the profile whether they need similar adjustments.
**Anything else to consider here?**
This is similar to #2070 and #2075 | True | Add LIMITs to queries on the software profile - **What query is this about**
Please provide a link to a Scholia profile and the appropriate section heading and/ or .sparql file.
On well-curated software profiles like [that for ImageJ](https://scholia.toolforge.org/software/Q1659584), some of the queries — especially the one for [Topics of works using the software](https://scholia.toolforge.org/software/Q1659584#topics) are too busy, putting strain on Query Service and browser.
**What change do you propose, and why?**
We should add LIMITs to software_topics.sparql and also review the other queries on the profile whether they need similar adjustments.
**Anything else to consider here?**
This is similar to #2070 and #2075 | non_test | add limits to queries on the software profile what query is this about please provide a link to a scholia profile and the appropriate section heading and or sparql file on well curated software profiles like some of the queries mdash especially the one for are too busy putting strain on query service and browser what change do you propose and why we should add limits to software topics sparql and also review the other queries on the profile whether they need similar adjustments anything else to consider here this is similar to and | 0 |
224,168 | 17,663,820,986 | IssuesEvent | 2021-08-22 03:28:47 | red/red | https://api.github.com/repos/red/red | closed | Division by negative zero isn't handled correctly | status.built type.bug test.written priority.low | **Describe the bug**
See https://stackoverflow.com/questions/5095968/does-float-have-a-negative-zero-0f for the description of this edge case.
*R/S:*
```
Red/System [] probe 1.0 / -0.0
```
Output:
```
-1.#INF
```
*Red:*
```
>> 1.0 / -0.0
== 1.#INF
>> atan2 0.0 -0.0
== 3.141592653589793
>> atan2 -0.0 -0.0
== -3.141592653589793
>> -0.0 == 0.0
== true
>> -0.0 =? 0.0
== false
```
**Expected behavior**
All is correct except `1.#INF` result. Should be negative infinity.
**Platform version**
```
Red 0.6.4 for Windows built 22-Jul-2021/20:44:06+03:00 commit #3c8d386
```
| 1.0 | Division by negative zero isn't handled correctly - **Describe the bug**
See https://stackoverflow.com/questions/5095968/does-float-have-a-negative-zero-0f for the description of this edge case.
*R/S:*
```
Red/System [] probe 1.0 / -0.0
```
Output:
```
-1.#INF
```
*Red:*
```
>> 1.0 / -0.0
== 1.#INF
>> atan2 0.0 -0.0
== 3.141592653589793
>> atan2 -0.0 -0.0
== -3.141592653589793
>> -0.0 == 0.0
== true
>> -0.0 =? 0.0
== false
```
**Expected behavior**
All is correct except `1.#INF` result. Should be negative infinity.
**Platform version**
```
Red 0.6.4 for Windows built 22-Jul-2021/20:44:06+03:00 commit #3c8d386
```
| test | division by negative zero isn t handled correctly describe the bug see for the description of this edge case r s red system probe output inf red inf true false expected behavior all is correct except inf result should be negative infinity platform version red for windows built jul commit | 1 |
246,798 | 20,916,752,236 | IssuesEvent | 2022-03-24 14:03:42 | bichvan-1711/FeedbackOnline | https://api.github.com/repos/bichvan-1711/FeedbackOnline | opened | FUNC_Xóa Template thành công_Click [Xóa] button không hiển thị popup message | bug Low Cosmetic Integration Test Open Fun_Wrong Business logic | Precondition :
- Admin đang ở màn hình Quản lý Template
- Template được chọn không được sử dụng ở module khác (ex: Quản lý Lớp)
1. Click [Xóa] button tại record bất kỳ
2.Click [Có] button
Hiện tại:
-Popup message tắt
-Record được chọn sẽ được update trong DB table Template với status = 0
-Quay về màn hình trước đó và refresh grid
Mong muốn:
-Hiển thị message “Xóa Template thành công”
------------------------
TestCaseID=37 | 1.0 | FUNC_Xóa Template thành công_Click [Xóa] button không hiển thị popup message - Precondition :
- Admin đang ở màn hình Quản lý Template
- Template được chọn không được sử dụng ở module khác (ex: Quản lý Lớp)
1. Click [Xóa] button tại record bất kỳ
2.Click [Có] button
Hiện tại:
-Popup message tắt
-Record được chọn sẽ được update trong DB table Template với status = 0
-Quay về màn hình trước đó và refresh grid
Mong muốn:
-Hiển thị message “Xóa Template thành công”
------------------------
TestCaseID=37 | test | func xóa template thành công click button không hiển thị popup message precondition admin đang ở màn hình quản lý template template được chọn không được sử dụng ở module khác ex quản lý lớp click button tại record bất kỳ click button hiện tại popup message tắt record được chọn sẽ được update trong db table template với status quay về màn hình trước đó và refresh grid mong muốn hiển thị message “xóa template thành công” testcaseid | 1 |
27,868 | 12,728,394,692 | IssuesEvent | 2020-06-25 02:26:01 | dcoghlan/dfwoptimzer | https://api.github.com/repos/dcoghlan/dfwoptimzer | closed | parse errors | dfw_services parse_error | The following parse errors were encountered in an NSX-T 2.5.1 setup.
```
rule 4151 at 8 inout protocol any from addrset 953c5cd8-100d-47d0-b333-e7cd28c71772 to addrset c96d6075-1d3d-4705-98cb-69a5b5bdfc90 with attribute profile a4175bf4-6aff-4caa-8a9f-fb5f9f24c2f8 accept with log tag 'My_Test-DFW(M&A)';
rule 4151 at 9 inout protocol any from addrset 953c5cd8-100d-47d0-b333-e7cd28c71772 to addrset c96d6075-1d3d-4705-98cb-69a5b5bdfc90 with attribute profile 7fb7cc4c-08c6-4f37-909c-4509cad9f4ff accept with log tag 'My_Test-DFW(M&A)';
rule 4151 at 10 inout protocol any from addrset 953c5cd8-100d-47d0-b333-e7cd28c71772 to addrset c96d6075-1d3d-4705-98cb-69a5b5bdfc90 with attribute profile 6399ef25-fd7b-41fc-94c7-b8885c1fa307 accept with log tag 'My_Test-DFW(M&A)';
rule 4134 at 21 inout protocol any from addrset 8ed1b6fd-fa60-4d74-80a0-9c5ea8341249 to addrset 7fbdc37a-4f47-4df7-9cc9-cf31a6595bc4 with attribute profile a4175bf4-6aff-4caa-8a9f-fb5f9f24c2f8 accept with log tag 'WindowsMachines';
rule 4134 at 22 inout protocol any from addrset 8ed1b6fd-fa60-4d74-80a0-9c5ea8341249 to addrset 7fbdc37a-4f47-4df7-9cc9-cf31a6595bc4 with attribute profile 7fb7cc4c-08c6-4f37-909c-4509cad9f4ff accept with log tag 'WindowsMachines';
rule 4149 at 54 inout protocol any from addrset 77cb1f67-a198-425e-8a17-7436462a9929 to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile e0a2e2eb-0fe1-4d48-bf16-5ede3755bf1b accept with log tag 'LBDFWTag';
rule 4149 at 55 inout protocol any from addrset 77cb1f67-a198-425e-8a17-7436462a9929 to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile a4175bf4-6aff-4caa-8a9f-fb5f9f24c2f8 accept with log tag 'LBDFWTag';
rule 4149 at 56 inout protocol any from addrset 77cb1f67-a198-425e-8a17-7436462a9929 to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 7fb7cc4c-08c6-4f37-909c-4509cad9f4ff accept with log tag 'LBDFWTag';
rule 4149 at 57 inout protocol any from addrset 77cb1f67-a198-425e-8a17-7436462a9929 to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 91faf9e8-d825-4415-89f7-f64424b7746a accept with log tag 'LBDFWTag';
rule 4149 at 58 inout protocol any from addrset 77cb1f67-a198-425e-8a17-7436462a9929 to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 6399ef25-fd7b-41fc-94c7-b8885c1fa307 accept with log tag 'LBDFWTag';
rule 4149 at 59 inout protocol any from addrset 77cb1f67-a198-425e-8a17-7436462a9929 to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 8cd8637e-2455-43a9-94d4-222e4dfa3252 accept with log tag 'LBDFWTag';
rule 4149 at 60 inout protocol any from addrset 77cb1f67-a198-425e-8a17-7436462a9929 to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 42b762f5-1309-4c87-827a-dec25de900a4 accept with log tag 'LBDFWTag';
rule 4149 at 61 inout protocol any from addrset 77cb1f67-a198-425e-8a17-7436462a9929 to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 43a52857-4ad8-44a0-9951-d70a5f04a74d accept with log tag 'LBDFWTag';
rule 4140 at 65 inout protocol any from addrset e93bdd08-d93f-44ac-9eeb-b31b8b9eefca to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile e0a2e2eb-0fe1-4d48-bf16-5ede3755bf1b accept with log tag 'WebDFWTag';
rule 4140 at 66 inout protocol any from addrset e93bdd08-d93f-44ac-9eeb-b31b8b9eefca to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile a4175bf4-6aff-4caa-8a9f-fb5f9f24c2f8 accept with log tag 'WebDFWTag';
rule 4140 at 67 inout protocol any from addrset e93bdd08-d93f-44ac-9eeb-b31b8b9eefca to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 7fb7cc4c-08c6-4f37-909c-4509cad9f4ff accept with log tag 'WebDFWTag';
rule 4140 at 68 inout protocol any from addrset e93bdd08-d93f-44ac-9eeb-b31b8b9eefca to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 91faf9e8-d825-4415-89f7-f64424b7746a accept with log tag 'WebDFWTag';
rule 4140 at 69 inout protocol any from addrset e93bdd08-d93f-44ac-9eeb-b31b8b9eefca to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 6399ef25-fd7b-41fc-94c7-b8885c1fa307 accept with log tag 'WebDFWTag';
rule 4140 at 70 inout protocol any from addrset e93bdd08-d93f-44ac-9eeb-b31b8b9eefca to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 8cd8637e-2455-43a9-94d4-222e4dfa3252 accept with log tag 'WebDFWTag';
rule 4140 at 71 inout protocol any from addrset e93bdd08-d93f-44ac-9eeb-b31b8b9eefca to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 42b762f5-1309-4c87-827a-dec25de900a4 accept with log tag 'WebDFWTag';
rule 4140 at 72 inout protocol any from addrset e93bdd08-d93f-44ac-9eeb-b31b8b9eefca to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 43a52857-4ad8-44a0-9951-d70a5f04a74d accept with log tag 'WebDFWTag';
``` | 1.0 | parse errors - The following parse errors were encountered in an NSX-T 2.5.1 setup.
```
rule 4151 at 8 inout protocol any from addrset 953c5cd8-100d-47d0-b333-e7cd28c71772 to addrset c96d6075-1d3d-4705-98cb-69a5b5bdfc90 with attribute profile a4175bf4-6aff-4caa-8a9f-fb5f9f24c2f8 accept with log tag 'My_Test-DFW(M&A)';
rule 4151 at 9 inout protocol any from addrset 953c5cd8-100d-47d0-b333-e7cd28c71772 to addrset c96d6075-1d3d-4705-98cb-69a5b5bdfc90 with attribute profile 7fb7cc4c-08c6-4f37-909c-4509cad9f4ff accept with log tag 'My_Test-DFW(M&A)';
rule 4151 at 10 inout protocol any from addrset 953c5cd8-100d-47d0-b333-e7cd28c71772 to addrset c96d6075-1d3d-4705-98cb-69a5b5bdfc90 with attribute profile 6399ef25-fd7b-41fc-94c7-b8885c1fa307 accept with log tag 'My_Test-DFW(M&A)';
rule 4134 at 21 inout protocol any from addrset 8ed1b6fd-fa60-4d74-80a0-9c5ea8341249 to addrset 7fbdc37a-4f47-4df7-9cc9-cf31a6595bc4 with attribute profile a4175bf4-6aff-4caa-8a9f-fb5f9f24c2f8 accept with log tag 'WindowsMachines';
rule 4134 at 22 inout protocol any from addrset 8ed1b6fd-fa60-4d74-80a0-9c5ea8341249 to addrset 7fbdc37a-4f47-4df7-9cc9-cf31a6595bc4 with attribute profile 7fb7cc4c-08c6-4f37-909c-4509cad9f4ff accept with log tag 'WindowsMachines';
rule 4149 at 54 inout protocol any from addrset 77cb1f67-a198-425e-8a17-7436462a9929 to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile e0a2e2eb-0fe1-4d48-bf16-5ede3755bf1b accept with log tag 'LBDFWTag';
rule 4149 at 55 inout protocol any from addrset 77cb1f67-a198-425e-8a17-7436462a9929 to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile a4175bf4-6aff-4caa-8a9f-fb5f9f24c2f8 accept with log tag 'LBDFWTag';
rule 4149 at 56 inout protocol any from addrset 77cb1f67-a198-425e-8a17-7436462a9929 to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 7fb7cc4c-08c6-4f37-909c-4509cad9f4ff accept with log tag 'LBDFWTag';
rule 4149 at 57 inout protocol any from addrset 77cb1f67-a198-425e-8a17-7436462a9929 to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 91faf9e8-d825-4415-89f7-f64424b7746a accept with log tag 'LBDFWTag';
rule 4149 at 58 inout protocol any from addrset 77cb1f67-a198-425e-8a17-7436462a9929 to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 6399ef25-fd7b-41fc-94c7-b8885c1fa307 accept with log tag 'LBDFWTag';
rule 4149 at 59 inout protocol any from addrset 77cb1f67-a198-425e-8a17-7436462a9929 to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 8cd8637e-2455-43a9-94d4-222e4dfa3252 accept with log tag 'LBDFWTag';
rule 4149 at 60 inout protocol any from addrset 77cb1f67-a198-425e-8a17-7436462a9929 to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 42b762f5-1309-4c87-827a-dec25de900a4 accept with log tag 'LBDFWTag';
rule 4149 at 61 inout protocol any from addrset 77cb1f67-a198-425e-8a17-7436462a9929 to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 43a52857-4ad8-44a0-9951-d70a5f04a74d accept with log tag 'LBDFWTag';
rule 4140 at 65 inout protocol any from addrset e93bdd08-d93f-44ac-9eeb-b31b8b9eefca to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile e0a2e2eb-0fe1-4d48-bf16-5ede3755bf1b accept with log tag 'WebDFWTag';
rule 4140 at 66 inout protocol any from addrset e93bdd08-d93f-44ac-9eeb-b31b8b9eefca to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile a4175bf4-6aff-4caa-8a9f-fb5f9f24c2f8 accept with log tag 'WebDFWTag';
rule 4140 at 67 inout protocol any from addrset e93bdd08-d93f-44ac-9eeb-b31b8b9eefca to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 7fb7cc4c-08c6-4f37-909c-4509cad9f4ff accept with log tag 'WebDFWTag';
rule 4140 at 68 inout protocol any from addrset e93bdd08-d93f-44ac-9eeb-b31b8b9eefca to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 91faf9e8-d825-4415-89f7-f64424b7746a accept with log tag 'WebDFWTag';
rule 4140 at 69 inout protocol any from addrset e93bdd08-d93f-44ac-9eeb-b31b8b9eefca to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 6399ef25-fd7b-41fc-94c7-b8885c1fa307 accept with log tag 'WebDFWTag';
rule 4140 at 70 inout protocol any from addrset e93bdd08-d93f-44ac-9eeb-b31b8b9eefca to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 8cd8637e-2455-43a9-94d4-222e4dfa3252 accept with log tag 'WebDFWTag';
rule 4140 at 71 inout protocol any from addrset e93bdd08-d93f-44ac-9eeb-b31b8b9eefca to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 42b762f5-1309-4c87-827a-dec25de900a4 accept with log tag 'WebDFWTag';
rule 4140 at 72 inout protocol any from addrset e93bdd08-d93f-44ac-9eeb-b31b8b9eefca to addrset 77cb1f67-a198-425e-8a17-7436462a9929 with attribute profile 43a52857-4ad8-44a0-9951-d70a5f04a74d accept with log tag 'WebDFWTag';
``` | non_test | parse errors the following parse errors were encountered in an nsx t setup rule at inout protocol any from addrset to addrset with attribute profile accept with log tag my test dfw m a rule at inout protocol any from addrset to addrset with attribute profile accept with log tag my test dfw m a rule at inout protocol any from addrset to addrset with attribute profile accept with log tag my test dfw m a rule at inout protocol any from addrset to addrset with attribute profile accept with log tag windowsmachines rule at inout protocol any from addrset to addrset with attribute profile accept with log tag windowsmachines rule at inout protocol any from addrset to addrset with attribute profile accept with log tag lbdfwtag rule at inout protocol any from addrset to addrset with attribute profile accept with log tag lbdfwtag rule at inout protocol any from addrset to addrset with attribute profile accept with log tag lbdfwtag rule at inout protocol any from addrset to addrset with attribute profile accept with log tag lbdfwtag rule at inout protocol any from addrset to addrset with attribute profile accept with log tag lbdfwtag rule at inout protocol any from addrset to addrset with attribute profile accept with log tag lbdfwtag rule at inout protocol any from addrset to addrset with attribute profile accept with log tag lbdfwtag rule at inout protocol any from addrset to addrset with attribute profile accept with log tag lbdfwtag rule at inout protocol any from addrset to addrset with attribute profile accept with log tag webdfwtag rule at inout protocol any from addrset to addrset with attribute profile accept with log tag webdfwtag rule at inout protocol any from addrset to addrset with attribute profile accept with log tag webdfwtag rule at inout protocol any from addrset to addrset with attribute profile accept with log tag webdfwtag rule at inout protocol any from addrset to addrset with attribute profile accept with log tag webdfwtag rule at inout protocol any from addrset to addrset with attribute profile accept with log tag webdfwtag rule at inout protocol any from addrset to addrset with attribute profile accept with log tag webdfwtag rule at inout protocol any from addrset to addrset with attribute profile accept with log tag webdfwtag | 0 |
62,136 | 6,777,176,873 | IssuesEvent | 2017-10-27 20:56:36 | brave/browser-laptop | https://api.github.com/repos/brave/browser-laptop | closed | Manual test run on Windows ia-32 for 0.19.x Hotfix 2 (Release channel) | OS/Windows release-notes/exclude tests | ## Per release specialty tests
- [ ] Time is not displayed correctly . ([#11675](https://github.com/brave/browser-laptop/issues/11675))
- [ ] Default download path is not working. ([#11649](https://github.com/brave/browser-laptop/issues/11649))
- [ ] Hiding/removing "update to preview release". ([#11638](https://github.com/brave/browser-laptop/issues/11638))
- [ ] Attempting to Print causes crash. ([#11637](https://github.com/brave/browser-laptop/issues/11637))
- [ ] Filtering for iframes not working for c62. ([#11621](https://github.com/brave/browser-laptop/issues/11621))
- [ ] Youtube ads shown after upgrade to chromium 62. ([#11619](https://github.com/brave/browser-laptop/issues/11619))
- [ ] Send updates to `about` pages more efficiently. ([#11615](https://github.com/brave/browser-laptop/issues/11615))
- [ ] Publishers lost if upgrading from 0.18 with wallet disabled. ([#11614](https://github.com/brave/browser-laptop/issues/11614))
- [ ] Transition when users wallet is disabled. ([#11611](https://github.com/brave/browser-laptop/issues/11611))
- [ ] Metamask contentscript is injected on about pages when it should not be. ([#11596](https://github.com/brave/browser-laptop/issues/11596))
- [ ] Ledger persists newClient but restores it to newClient.state. ([#11585](https://github.com/brave/browser-laptop/issues/11585))
- [ ] Page data refactor. ([#11575](https://github.com/brave/browser-laptop/issues/11575))
- [ ] Publishers auto-included even with auto-include switch disabled. ([#11553](https://github.com/brave/browser-laptop/issues/11553))
- [ ] Upgrade to muon 4.5.x. ([#11498](https://github.com/brave/browser-laptop/issues/11498))
- [ ] Site not added to publisher list even after spending ~10 mins on the site. ([#11274](https://github.com/brave/browser-laptop/issues/11274))
- [ ] Ledger table doesnt auto populate the publishers. ([#11273](https://github.com/brave/browser-laptop/issues/11273))
## Installer
1. [ ] Check that installer is close to the size of last release.
2. [ ] Check signature: If OS Run `spctl --assess --verbose /Applications/Brave.app/` and make sure it returns `accepted`. If Windows right click on the installer exe and go to Properties, go to the Digital Signatures tab and double click on the signature. Make sure it says "The digital signature is OK" in the popup window.
3. [ ] Check Brave, muon, and libchromiumcontent version in About and make sure it is EXACTLY as expected.
## Last changeset test
1. [ ] Test what is covered by the last changeset (you can find this by clicking on the SHA in about:brave).
## Widevine/Netflix test
1. [ ] Test that you can log into Netflix and start a show.
## Ledger
- [ ] Verify wallet is auto created after enabling payments
- [ ] Verify monthly budget and account balance shows correct BAT and USD value
- [ ] Click on `add funds` and click on each currency and verify it shows wallet address and QR Code
- [ ] Verify that Brave BAT wallet address can be copied
- [ ] Verify adding funds via any of the currencies flows into BAT Wallet after specified amount of time
- [ ] Verify adding funds to an existing wallet with amount, adjusts the BAT value appropriately
- [ ] Change min visit and min time in advance setting and verify if the publisher list gets updated based on new setting
- [ ] Visit nytimes.com for a few seconds and make sure it shows up in the Payments table.
- [ ] Check that disabling payments and enabling them again does not lose state.
- [ ] Upgrade from older version
- [ ] Verify the wallet overlay is shown when wallet transition is happening upon upgrade
- [ ] Verify transition overlay is shown post upgrade even if the payment is disabled before upgrade
- [ ] Verify publishers list is not lost after upgrade when payment is disabled in the older version
## Sync
1. [ ] Verify you are able to sync two devices using the secret code
2. [ ] Visit a site on device 1 and change shield setting, ensure that the saved site preference is synced to device 2
3. [ ] Enable Browsing history sync on device 1, ensure the history is shown on device 2
4. [ ] Import/Add bookmarks on device 1, ensure it is synced on device 2
5. [ ] Ensure imported bookmark folder structure is maintained on device 2
6. [ ] Ensure bookmark favicons are shown after sync
## Data
1. [ ] Make sure that data from the last version appears in the new version OK.
2. [ ] Test that the previous version's cookies are preserved in the next version.
## About pages
1. [ ] Test that about:adblock loads
2. [ ] Test that about:autofill loads
3. [ ] Test that about:bookmarks loads bookmarks
4. [ ] Test that about:downloads loads downloads
5. [ ] Test that about:extensions loads
6. [ ] Test that about:history loads history
7. [ ] Test that about:passwords loads
8. [ ] Test that about:styles loads
9. [ ] Test that about:welcome loads
10. [ ] Test that about:preferences changing a preference takes effect right away
11. [ ] Test that about:preferences language change takes effect on re-start
## Bookmarks
1. [ ] Test that creating a bookmark on the bookmarks toolbar with the star button works
2. [ ] Test that creating a bookmark on the bookmarks toolbar by dragging the un/lock icon works
3. [ ] Test that creating a bookmark folder on the bookmarks toolbar works
4. [ ] Test that moving a bookmark into a folder by drag and drop on the bookmarks folder works
5. [ ] Test that clicking a bookmark in the toolbar loads the bookmark.
6. [ ] Test that clicking a bookmark in a bookmark toolbar folder loads the bookmark.
## Context menus
1. [ ] Make sure context menu items in the URL bar work
2. [ ] Make sure context menu items on content work with no selected text.
3. [ ] Make sure context menu items on content work with selected text.
4. [ ] Make sure context menu items on content work inside an editable control on `about:styles` (input, textarea, or contenteditable).
## Find on page
1. [ ] Ensure search box is shown with shortcut
2. [ ] Test successful find
3. [ ] Test forward and backward find navigation
4. [ ] Test failed find shows 0 results
5. [ ] Test match case find
## Geolocation
1. [ ] Check that https://developer.mozilla.org/en-US/docs/Web/API/Geolocation/Using_geolocation works
## Site hacks
1. [ ] Test https://www.twitch.tv/adobe sub-page loads a video and you can play it
## Downloads
1. [ ] Test downloading a file works and that all actions on the download item works.
## Fullscreen
1. [ ] Test that entering full screen window works View -> Toggle Full Screen. And exit back (Not Esc).
2. [ ] Test that entering HTML5 full screen works. And Esc to go back. (youtube.com)
## Tabs, Pinning and Tear off tabs
1. [ ] Test that tabs are pinnable
2. [ ] Test that tabs are unpinnable
3. [ ] Test that tabs are draggable to same tabset
4. [ ] Test that tabs are draggable to alternate tabset
5. [ ] Test that tabs can be teared off into a new window
6. [ ] Test that you are able to reattach a tab that is teared off into a new window
7. [ ] Test that tab pages can be closed
8. [ ] Test that tab pages can be muted
## Zoom
1. [ ] Test zoom in / out shortcut works
2. [ ] Test hamburger menu zooms.
3. [ ] Test zoom saved when you close the browser and restore on a single site.
4. [ ] Test zoom saved when you navigate within a single origin site.
5. [ ] Test that navigating to a different origin resets the zoom
## Bravery settings
1. [ ] Check that HTTPS Everywhere works by loading https://https-everywhere.badssl.com/
2. [ ] Turning HTTPS Everywhere off and shields off both disable the redirect to https://https-everywhere.badssl.com/
3. [ ] Check that ad replacement works on http://slashdot.org
4. [ ] Check that toggling to blocking and allow ads works as expected.
5. [ ] Test that clicking through a cert error in https://badssl.com/ works.
6. [ ] Test that Safe Browsing works (http://downloadme.org/)
7. [ ] Turning Safe Browsing off and shields off both disable safe browsing for http://downloadme.org/.
8. [ ] Visit https://brianbondy.com/ and then turn on script blocking, nothing should load. Allow it from the script blocking UI in the URL bar and it should work.
9. [ ] Test that about:preferences default Bravery settings take effect on pages with no site settings.
10. [ ] Test that turning on fingerprinting protection in about:preferences shows 3 fingerprints blocked at https://jsfiddle.net/bkf50r8v/13/. Test that turning it off in the Bravery menu shows 0 fingerprints blocked.
11. [ ] Test that 3rd party storage results are blank at https://jsfiddle.net/7ke9r14a/9/ when 3rd party cookies are blocked and not blank when 3rd party cookies are unblocked.
12. [ ] Test that audio fingerprint is blocked at https://audiofingerprint.openwpm.com/ when fingerprinting protection is on.
13. [ ] Test that browser is not detected on https://extensions.inrialpes.fr/brave/
## Content tests
1. [ ] Go to https://brianbondy.com/ and click on the twitter icon on the top right. Test that context menus work in the new twitter tab.
2. [ ] Load twitter and click on a tweet so the popup div shows. Click to dismiss and repeat with another div. Make sure it shows.
3. [ ] Go to https://www.bennish.net/web-notifications.html and test that clicking on 'Show' pops up a notification asking for permission. Make sure that clicking 'Deny' leads to no notifications being shown.
4. [ ] Go to https://trac.torproject.org/projects/tor/login and make sure that the password can be saved. Make sure the saved password shows up in `about:passwords`. Then reload https://trac.torproject.org/projects/tor/login and make sure the password is autofilled.
5. [ ] Open `about:styles` and type some misspellings on a textbox, make sure they are underlined.
6. [ ] Make sure that right clicking on a word with suggestions gives a suggestion and that clicking on the suggestion replaces the text.
7. [ ] Make sure that Command + Click (Control + Click on Windows, Control + Click on Ubuntu) on a link opens a new tab but does NOT switch to it. Click on it and make sure it is already loaded.
8. [ ] Open an email on http://mail.google.com/ or inbox.google.com and click on a link. Make sure it works.
9. [ ] Test that PDF is loaded at http://www.orimi.com/pdf-test.pdf
10. [ ] Test that https://mixed-script.badssl.com/ shows up as grey not red (no mixed content scripts are run).
## Flash tests
1. [ ] Turn on Flash in about:preferences#security. Test that clicking on 'Install Flash' banner on myspace.com shows a notification to allow Flash and that the banner disappears when 'Allow' is clicked.
2. [ ] Test that flash placeholder appears on http://www.homestarrunner.com
## Autofill tests
1. [ ] Test that autofill works on http://www.roboform.com/filling-test-all-fields
## Session storage
Do not forget to make a backup of your entire `~/Library/Application\ Support/Brave` folder.
1. [ ] Temporarily move away your `~/Library/Application\ Support/Brave/session-store-1` and test that clean session storage works. (`%appdata%\Brave in Windows`, `./config/brave` in Ubuntu)
2. [ ] Test that windows and tabs restore when closed, including active tab.
3. [ ] Move away your entire `~/Library/Application\ Support/Brave` folder (`%appdata%\Brave in Windows`, `./config/brave` in Ubuntu)
## Cookie and Cache
1. [ ] Make a backup of your profile, turn on all clearing in preferences and shut down. Make sure when you bring the browser back up everything is gone that is specified.
2. [ ] Go to http://samy.pl/evercookie/ and set an evercookie. Check that going to prefs, clearing site data and cache, and going back to the Evercookie site does not remember the old evercookie value.
## Update tests
1. [ ] Test that updating using `BRAVE_UPDATE_VERSION=0.8.3` env variable works correctly.
| 1.0 | Manual test run on Windows ia-32 for 0.19.x Hotfix 2 (Release channel) - ## Per release specialty tests
- [ ] Time is not displayed correctly . ([#11675](https://github.com/brave/browser-laptop/issues/11675))
- [ ] Default download path is not working. ([#11649](https://github.com/brave/browser-laptop/issues/11649))
- [ ] Hiding/removing "update to preview release". ([#11638](https://github.com/brave/browser-laptop/issues/11638))
- [ ] Attempting to Print causes crash. ([#11637](https://github.com/brave/browser-laptop/issues/11637))
- [ ] Filtering for iframes not working for c62. ([#11621](https://github.com/brave/browser-laptop/issues/11621))
- [ ] Youtube ads shown after upgrade to chromium 62. ([#11619](https://github.com/brave/browser-laptop/issues/11619))
- [ ] Send updates to `about` pages more efficiently. ([#11615](https://github.com/brave/browser-laptop/issues/11615))
- [ ] Publishers lost if upgrading from 0.18 with wallet disabled. ([#11614](https://github.com/brave/browser-laptop/issues/11614))
- [ ] Transition when users wallet is disabled. ([#11611](https://github.com/brave/browser-laptop/issues/11611))
- [ ] Metamask contentscript is injected on about pages when it should not be. ([#11596](https://github.com/brave/browser-laptop/issues/11596))
- [ ] Ledger persists newClient but restores it to newClient.state. ([#11585](https://github.com/brave/browser-laptop/issues/11585))
- [ ] Page data refactor. ([#11575](https://github.com/brave/browser-laptop/issues/11575))
- [ ] Publishers auto-included even with auto-include switch disabled. ([#11553](https://github.com/brave/browser-laptop/issues/11553))
- [ ] Upgrade to muon 4.5.x. ([#11498](https://github.com/brave/browser-laptop/issues/11498))
- [ ] Site not added to publisher list even after spending ~10 mins on the site. ([#11274](https://github.com/brave/browser-laptop/issues/11274))
- [ ] Ledger table doesnt auto populate the publishers. ([#11273](https://github.com/brave/browser-laptop/issues/11273))
## Installer
1. [ ] Check that installer is close to the size of last release.
2. [ ] Check signature: If OS Run `spctl --assess --verbose /Applications/Brave.app/` and make sure it returns `accepted`. If Windows right click on the installer exe and go to Properties, go to the Digital Signatures tab and double click on the signature. Make sure it says "The digital signature is OK" in the popup window.
3. [ ] Check Brave, muon, and libchromiumcontent version in About and make sure it is EXACTLY as expected.
## Last changeset test
1. [ ] Test what is covered by the last changeset (you can find this by clicking on the SHA in about:brave).
## Widevine/Netflix test
1. [ ] Test that you can log into Netflix and start a show.
## Ledger
- [ ] Verify wallet is auto created after enabling payments
- [ ] Verify monthly budget and account balance shows correct BAT and USD value
- [ ] Click on `add funds` and click on each currency and verify it shows wallet address and QR Code
- [ ] Verify that Brave BAT wallet address can be copied
- [ ] Verify adding funds via any of the currencies flows into BAT Wallet after specified amount of time
- [ ] Verify adding funds to an existing wallet with amount, adjusts the BAT value appropriately
- [ ] Change min visit and min time in advance setting and verify if the publisher list gets updated based on new setting
- [ ] Visit nytimes.com for a few seconds and make sure it shows up in the Payments table.
- [ ] Check that disabling payments and enabling them again does not lose state.
- [ ] Upgrade from older version
- [ ] Verify the wallet overlay is shown when wallet transition is happening upon upgrade
- [ ] Verify transition overlay is shown post upgrade even if the payment is disabled before upgrade
- [ ] Verify publishers list is not lost after upgrade when payment is disabled in the older version
## Sync
1. [ ] Verify you are able to sync two devices using the secret code
2. [ ] Visit a site on device 1 and change shield setting, ensure that the saved site preference is synced to device 2
3. [ ] Enable Browsing history sync on device 1, ensure the history is shown on device 2
4. [ ] Import/Add bookmarks on device 1, ensure it is synced on device 2
5. [ ] Ensure imported bookmark folder structure is maintained on device 2
6. [ ] Ensure bookmark favicons are shown after sync
## Data
1. [ ] Make sure that data from the last version appears in the new version OK.
2. [ ] Test that the previous version's cookies are preserved in the next version.
## About pages
1. [ ] Test that about:adblock loads
2. [ ] Test that about:autofill loads
3. [ ] Test that about:bookmarks loads bookmarks
4. [ ] Test that about:downloads loads downloads
5. [ ] Test that about:extensions loads
6. [ ] Test that about:history loads history
7. [ ] Test that about:passwords loads
8. [ ] Test that about:styles loads
9. [ ] Test that about:welcome loads
10. [ ] Test that about:preferences changing a preference takes effect right away
11. [ ] Test that about:preferences language change takes effect on re-start
## Bookmarks
1. [ ] Test that creating a bookmark on the bookmarks toolbar with the star button works
2. [ ] Test that creating a bookmark on the bookmarks toolbar by dragging the un/lock icon works
3. [ ] Test that creating a bookmark folder on the bookmarks toolbar works
4. [ ] Test that moving a bookmark into a folder by drag and drop on the bookmarks folder works
5. [ ] Test that clicking a bookmark in the toolbar loads the bookmark.
6. [ ] Test that clicking a bookmark in a bookmark toolbar folder loads the bookmark.
## Context menus
1. [ ] Make sure context menu items in the URL bar work
2. [ ] Make sure context menu items on content work with no selected text.
3. [ ] Make sure context menu items on content work with selected text.
4. [ ] Make sure context menu items on content work inside an editable control on `about:styles` (input, textarea, or contenteditable).
## Find on page
1. [ ] Ensure search box is shown with shortcut
2. [ ] Test successful find
3. [ ] Test forward and backward find navigation
4. [ ] Test failed find shows 0 results
5. [ ] Test match case find
## Geolocation
1. [ ] Check that https://developer.mozilla.org/en-US/docs/Web/API/Geolocation/Using_geolocation works
## Site hacks
1. [ ] Test https://www.twitch.tv/adobe sub-page loads a video and you can play it
## Downloads
1. [ ] Test downloading a file works and that all actions on the download item works.
## Fullscreen
1. [ ] Test that entering full screen window works View -> Toggle Full Screen. And exit back (Not Esc).
2. [ ] Test that entering HTML5 full screen works. And Esc to go back. (youtube.com)
## Tabs, Pinning and Tear off tabs
1. [ ] Test that tabs are pinnable
2. [ ] Test that tabs are unpinnable
3. [ ] Test that tabs are draggable to same tabset
4. [ ] Test that tabs are draggable to alternate tabset
5. [ ] Test that tabs can be teared off into a new window
6. [ ] Test that you are able to reattach a tab that is teared off into a new window
7. [ ] Test that tab pages can be closed
8. [ ] Test that tab pages can be muted
## Zoom
1. [ ] Test zoom in / out shortcut works
2. [ ] Test hamburger menu zooms.
3. [ ] Test zoom saved when you close the browser and restore on a single site.
4. [ ] Test zoom saved when you navigate within a single origin site.
5. [ ] Test that navigating to a different origin resets the zoom
## Bravery settings
1. [ ] Check that HTTPS Everywhere works by loading https://https-everywhere.badssl.com/
2. [ ] Turning HTTPS Everywhere off and shields off both disable the redirect to https://https-everywhere.badssl.com/
3. [ ] Check that ad replacement works on http://slashdot.org
4. [ ] Check that toggling to blocking and allow ads works as expected.
5. [ ] Test that clicking through a cert error in https://badssl.com/ works.
6. [ ] Test that Safe Browsing works (http://downloadme.org/)
7. [ ] Turning Safe Browsing off and shields off both disable safe browsing for http://downloadme.org/.
8. [ ] Visit https://brianbondy.com/ and then turn on script blocking, nothing should load. Allow it from the script blocking UI in the URL bar and it should work.
9. [ ] Test that about:preferences default Bravery settings take effect on pages with no site settings.
10. [ ] Test that turning on fingerprinting protection in about:preferences shows 3 fingerprints blocked at https://jsfiddle.net/bkf50r8v/13/. Test that turning it off in the Bravery menu shows 0 fingerprints blocked.
11. [ ] Test that 3rd party storage results are blank at https://jsfiddle.net/7ke9r14a/9/ when 3rd party cookies are blocked and not blank when 3rd party cookies are unblocked.
12. [ ] Test that audio fingerprint is blocked at https://audiofingerprint.openwpm.com/ when fingerprinting protection is on.
13. [ ] Test that browser is not detected on https://extensions.inrialpes.fr/brave/
## Content tests
1. [ ] Go to https://brianbondy.com/ and click on the twitter icon on the top right. Test that context menus work in the new twitter tab.
2. [ ] Load twitter and click on a tweet so the popup div shows. Click to dismiss and repeat with another div. Make sure it shows.
3. [ ] Go to https://www.bennish.net/web-notifications.html and test that clicking on 'Show' pops up a notification asking for permission. Make sure that clicking 'Deny' leads to no notifications being shown.
4. [ ] Go to https://trac.torproject.org/projects/tor/login and make sure that the password can be saved. Make sure the saved password shows up in `about:passwords`. Then reload https://trac.torproject.org/projects/tor/login and make sure the password is autofilled.
5. [ ] Open `about:styles` and type some misspellings on a textbox, make sure they are underlined.
6. [ ] Make sure that right clicking on a word with suggestions gives a suggestion and that clicking on the suggestion replaces the text.
7. [ ] Make sure that Command + Click (Control + Click on Windows, Control + Click on Ubuntu) on a link opens a new tab but does NOT switch to it. Click on it and make sure it is already loaded.
8. [ ] Open an email on http://mail.google.com/ or inbox.google.com and click on a link. Make sure it works.
9. [ ] Test that PDF is loaded at http://www.orimi.com/pdf-test.pdf
10. [ ] Test that https://mixed-script.badssl.com/ shows up as grey not red (no mixed content scripts are run).
## Flash tests
1. [ ] Turn on Flash in about:preferences#security. Test that clicking on 'Install Flash' banner on myspace.com shows a notification to allow Flash and that the banner disappears when 'Allow' is clicked.
2. [ ] Test that flash placeholder appears on http://www.homestarrunner.com
## Autofill tests
1. [ ] Test that autofill works on http://www.roboform.com/filling-test-all-fields
## Session storage
Do not forget to make a backup of your entire `~/Library/Application\ Support/Brave` folder.
1. [ ] Temporarily move away your `~/Library/Application\ Support/Brave/session-store-1` and test that clean session storage works. (`%appdata%\Brave in Windows`, `./config/brave` in Ubuntu)
2. [ ] Test that windows and tabs restore when closed, including active tab.
3. [ ] Move away your entire `~/Library/Application\ Support/Brave` folder (`%appdata%\Brave in Windows`, `./config/brave` in Ubuntu)
## Cookie and Cache
1. [ ] Make a backup of your profile, turn on all clearing in preferences and shut down. Make sure when you bring the browser back up everything is gone that is specified.
2. [ ] Go to http://samy.pl/evercookie/ and set an evercookie. Check that going to prefs, clearing site data and cache, and going back to the Evercookie site does not remember the old evercookie value.
## Update tests
1. [ ] Test that updating using `BRAVE_UPDATE_VERSION=0.8.3` env variable works correctly.
| test | manual test run on windows ia for x hotfix release channel per release specialty tests time is not displayed correctly default download path is not working hiding removing update to preview release attempting to print causes crash filtering for iframes not working for youtube ads shown after upgrade to chromium send updates to about pages more efficiently publishers lost if upgrading from with wallet disabled transition when users wallet is disabled metamask contentscript is injected on about pages when it should not be ledger persists newclient but restores it to newclient state page data refactor publishers auto included even with auto include switch disabled upgrade to muon x site not added to publisher list even after spending mins on the site ledger table doesnt auto populate the publishers installer check that installer is close to the size of last release check signature if os run spctl assess verbose applications brave app and make sure it returns accepted if windows right click on the installer exe and go to properties go to the digital signatures tab and double click on the signature make sure it says the digital signature is ok in the popup window check brave muon and libchromiumcontent version in about and make sure it is exactly as expected last changeset test test what is covered by the last changeset you can find this by clicking on the sha in about brave widevine netflix test test that you can log into netflix and start a show ledger verify wallet is auto created after enabling payments verify monthly budget and account balance shows correct bat and usd value click on add funds and click on each currency and verify it shows wallet address and qr code verify that brave bat wallet address can be copied verify adding funds via any of the currencies flows into bat wallet after specified amount of time verify adding funds to an existing wallet with amount adjusts the bat value appropriately change min visit and min time in advance setting and verify if the publisher list gets updated based on new setting visit nytimes com for a few seconds and make sure it shows up in the payments table check that disabling payments and enabling them again does not lose state upgrade from older version verify the wallet overlay is shown when wallet transition is happening upon upgrade verify transition overlay is shown post upgrade even if the payment is disabled before upgrade verify publishers list is not lost after upgrade when payment is disabled in the older version sync verify you are able to sync two devices using the secret code visit a site on device and change shield setting ensure that the saved site preference is synced to device enable browsing history sync on device ensure the history is shown on device import add bookmarks on device ensure it is synced on device ensure imported bookmark folder structure is maintained on device ensure bookmark favicons are shown after sync data make sure that data from the last version appears in the new version ok test that the previous version s cookies are preserved in the next version about pages test that about adblock loads test that about autofill loads test that about bookmarks loads bookmarks test that about downloads loads downloads test that about extensions loads test that about history loads history test that about passwords loads test that about styles loads test that about welcome loads test that about preferences changing a preference takes effect right away test that about preferences language change takes effect on re start bookmarks test that creating a bookmark on the bookmarks toolbar with the star button works test that creating a bookmark on the bookmarks toolbar by dragging the un lock icon works test that creating a bookmark folder on the bookmarks toolbar works test that moving a bookmark into a folder by drag and drop on the bookmarks folder works test that clicking a bookmark in the toolbar loads the bookmark test that clicking a bookmark in a bookmark toolbar folder loads the bookmark context menus make sure context menu items in the url bar work make sure context menu items on content work with no selected text make sure context menu items on content work with selected text make sure context menu items on content work inside an editable control on about styles input textarea or contenteditable find on page ensure search box is shown with shortcut test successful find test forward and backward find navigation test failed find shows results test match case find geolocation check that works site hacks test sub page loads a video and you can play it downloads test downloading a file works and that all actions on the download item works fullscreen test that entering full screen window works view toggle full screen and exit back not esc test that entering full screen works and esc to go back youtube com tabs pinning and tear off tabs test that tabs are pinnable test that tabs are unpinnable test that tabs are draggable to same tabset test that tabs are draggable to alternate tabset test that tabs can be teared off into a new window test that you are able to reattach a tab that is teared off into a new window test that tab pages can be closed test that tab pages can be muted zoom test zoom in out shortcut works test hamburger menu zooms test zoom saved when you close the browser and restore on a single site test zoom saved when you navigate within a single origin site test that navigating to a different origin resets the zoom bravery settings check that https everywhere works by loading turning https everywhere off and shields off both disable the redirect to check that ad replacement works on check that toggling to blocking and allow ads works as expected test that clicking through a cert error in works test that safe browsing works turning safe browsing off and shields off both disable safe browsing for visit and then turn on script blocking nothing should load allow it from the script blocking ui in the url bar and it should work test that about preferences default bravery settings take effect on pages with no site settings test that turning on fingerprinting protection in about preferences shows fingerprints blocked at test that turning it off in the bravery menu shows fingerprints blocked test that party storage results are blank at when party cookies are blocked and not blank when party cookies are unblocked test that audio fingerprint is blocked at when fingerprinting protection is on test that browser is not detected on content tests go to and click on the twitter icon on the top right test that context menus work in the new twitter tab load twitter and click on a tweet so the popup div shows click to dismiss and repeat with another div make sure it shows go to and test that clicking on show pops up a notification asking for permission make sure that clicking deny leads to no notifications being shown go to and make sure that the password can be saved make sure the saved password shows up in about passwords then reload and make sure the password is autofilled open about styles and type some misspellings on a textbox make sure they are underlined make sure that right clicking on a word with suggestions gives a suggestion and that clicking on the suggestion replaces the text make sure that command click control click on windows control click on ubuntu on a link opens a new tab but does not switch to it click on it and make sure it is already loaded open an email on or inbox google com and click on a link make sure it works test that pdf is loaded at test that shows up as grey not red no mixed content scripts are run flash tests turn on flash in about preferences security test that clicking on install flash banner on myspace com shows a notification to allow flash and that the banner disappears when allow is clicked test that flash placeholder appears on autofill tests test that autofill works on session storage do not forget to make a backup of your entire library application support brave folder temporarily move away your library application support brave session store and test that clean session storage works appdata brave in windows config brave in ubuntu test that windows and tabs restore when closed including active tab move away your entire library application support brave folder appdata brave in windows config brave in ubuntu cookie and cache make a backup of your profile turn on all clearing in preferences and shut down make sure when you bring the browser back up everything is gone that is specified go to and set an evercookie check that going to prefs clearing site data and cache and going back to the evercookie site does not remember the old evercookie value update tests test that updating using brave update version env variable works correctly | 1 |
20,107 | 3,793,083,280 | IssuesEvent | 2016-03-22 12:35:14 | chill-rs/chill | https://api.github.com/repos/chill-rs/chill | opened | Unit tests for the HyperTransport | test | The `HyperTransport` is tested indirectly, via the integration tests. Consider writing unit tests for it to ensure all cases are covered. | 1.0 | Unit tests for the HyperTransport - The `HyperTransport` is tested indirectly, via the integration tests. Consider writing unit tests for it to ensure all cases are covered. | test | unit tests for the hypertransport the hypertransport is tested indirectly via the integration tests consider writing unit tests for it to ensure all cases are covered | 1 |
351,993 | 25,045,245,713 | IssuesEvent | 2022-11-05 06:24:41 | greatscottgadgets/hackrf | https://api.github.com/repos/greatscottgadgets/hackrf | opened | [Documentation]: Why are these functions not documented properly? | documentation | ### What would you like us to add to or change about the HackRF One documentation?
I was looking at the "libhackRF API" section in https://hackrf.readthedocs.io/_/downloads/en/latest/pdf/ and noticed quite a few of the functions are not completely documented.
The documentation for the function hackrf_open doesn't state which unit is opened if more than one unit is connected. Is it the one that was first plugged in? Is it the one with the lowest, or maybe highest, serial number?
The documentation for the following functions don't describe at all what kind of input are expected for their parameters, nor is it intuitive what some of the parameters should be.
hackrf_start_rx (missing explanation of the hackrf_sample_block_cb_fn and rx_ctx parameters)
hackrf_start_tx (missing explanation of the hackrf_sample_block_cb_fn and tx_ctx parameters)
| 1.0 | [Documentation]: Why are these functions not documented properly? - ### What would you like us to add to or change about the HackRF One documentation?
I was looking at the "libhackRF API" section in https://hackrf.readthedocs.io/_/downloads/en/latest/pdf/ and noticed quite a few of the functions are not completely documented.
The documentation for the function hackrf_open doesn't state which unit is opened if more than one unit is connected. Is it the one that was first plugged in? Is it the one with the lowest, or maybe highest, serial number?
The documentation for the following functions don't describe at all what kind of input are expected for their parameters, nor is it intuitive what some of the parameters should be.
hackrf_start_rx (missing explanation of the hackrf_sample_block_cb_fn and rx_ctx parameters)
hackrf_start_tx (missing explanation of the hackrf_sample_block_cb_fn and tx_ctx parameters)
| non_test | why are these functions not documented properly what would you like us to add to or change about the hackrf one documentation i was looking at the libhackrf api section in and noticed quite a few of the functions are not completely documented the documentation for the function hackrf open doesn t state which unit is opened if more than one unit is connected is it the one that was first plugged in is it the one with the lowest or maybe highest serial number the documentation for the following functions don t describe at all what kind of input are expected for their parameters nor is it intuitive what some of the parameters should be hackrf start rx missing explanation of the hackrf sample block cb fn and rx ctx parameters hackrf start tx missing explanation of the hackrf sample block cb fn and tx ctx parameters | 0 |
738,967 | 25,574,595,073 | IssuesEvent | 2022-11-30 20:50:15 | GoogleCloudPlatform/python-docs-samples | https://api.github.com/repos/GoogleCloudPlatform/python-docs-samples | closed | vision.snippets.detect.detect_test: test_logos_uri failed | priority: p1 type: bug api: vision samples flakybot: issue flakybot: flaky | This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot).
If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.
---
commit: 07e8b8145670fc1f9f9ed99e348d8fe28ca2ca7e
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/be880b63-6128-4dd8-b998-bc6eebd17b8c), [Sponge](http://sponge2/be880b63-6128-4dd8-b998-bc6eebd17b8c)
status: failed
<details><summary>Test output</summary><br><pre>Traceback (most recent call last):
File "/workspace/vision/snippets/detect/.nox/py-3-9/lib/python3.9/site-packages/google/api_core/grpc_helpers.py", line 72, in error_remapped_callable
return callable_(*args, **kwargs)
File "/workspace/vision/snippets/detect/.nox/py-3-9/lib/python3.9/site-packages/grpc/_channel.py", line 946, in __call__
return _end_unary_response_blocking(state, call, False, None)
File "/workspace/vision/snippets/detect/.nox/py-3-9/lib/python3.9/site-packages/grpc/_channel.py", line 849, in _end_unary_response_blocking
raise _InactiveRpcError(state)
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNAUTHENTICATED
details = "Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project."
debug_error_string = "UNKNOWN:Error received from peer ipv4:74.125.199.95:443 {created_time:"2022-11-30T14:01:28.705376722+00:00", grpc_status:16, grpc_message:"Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project."}"
>
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/workspace/vision/snippets/detect/detect_test.py", line 91, in test_logos_uri
detect.detect_logos_uri(file_name)
File "/workspace/vision/snippets/detect/detect.py", line 265, in detect_logos_uri
response = client.logo_detection(image=image)
File "/workspace/vision/snippets/detect/.nox/py-3-9/lib/python3.9/site-packages/google/cloud/vision_helpers/decorators.py", line 112, in inner
response = self.annotate_image(
File "/workspace/vision/snippets/detect/.nox/py-3-9/lib/python3.9/site-packages/google/cloud/vision_helpers/__init__.py", line 76, in annotate_image
r = self.batch_annotate_images(
File "/workspace/vision/snippets/detect/.nox/py-3-9/lib/python3.9/site-packages/google/cloud/vision_v1/services/image_annotator/client.py", line 548, in batch_annotate_images
response = rpc(
File "/workspace/vision/snippets/detect/.nox/py-3-9/lib/python3.9/site-packages/google/api_core/gapic_v1/method.py", line 154, in __call__
return wrapped_func(*args, **kwargs)
File "/workspace/vision/snippets/detect/.nox/py-3-9/lib/python3.9/site-packages/google/api_core/grpc_helpers.py", line 74, in error_remapped_callable
raise exceptions.from_grpc_error(exc) from exc
google.api_core.exceptions.Unauthenticated: 401 Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.</pre></details> | 1.0 | vision.snippets.detect.detect_test: test_logos_uri failed - This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot).
If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.
---
commit: 07e8b8145670fc1f9f9ed99e348d8fe28ca2ca7e
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/be880b63-6128-4dd8-b998-bc6eebd17b8c), [Sponge](http://sponge2/be880b63-6128-4dd8-b998-bc6eebd17b8c)
status: failed
<details><summary>Test output</summary><br><pre>Traceback (most recent call last):
File "/workspace/vision/snippets/detect/.nox/py-3-9/lib/python3.9/site-packages/google/api_core/grpc_helpers.py", line 72, in error_remapped_callable
return callable_(*args, **kwargs)
File "/workspace/vision/snippets/detect/.nox/py-3-9/lib/python3.9/site-packages/grpc/_channel.py", line 946, in __call__
return _end_unary_response_blocking(state, call, False, None)
File "/workspace/vision/snippets/detect/.nox/py-3-9/lib/python3.9/site-packages/grpc/_channel.py", line 849, in _end_unary_response_blocking
raise _InactiveRpcError(state)
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNAUTHENTICATED
details = "Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project."
debug_error_string = "UNKNOWN:Error received from peer ipv4:74.125.199.95:443 {created_time:"2022-11-30T14:01:28.705376722+00:00", grpc_status:16, grpc_message:"Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project."}"
>
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/workspace/vision/snippets/detect/detect_test.py", line 91, in test_logos_uri
detect.detect_logos_uri(file_name)
File "/workspace/vision/snippets/detect/detect.py", line 265, in detect_logos_uri
response = client.logo_detection(image=image)
File "/workspace/vision/snippets/detect/.nox/py-3-9/lib/python3.9/site-packages/google/cloud/vision_helpers/decorators.py", line 112, in inner
response = self.annotate_image(
File "/workspace/vision/snippets/detect/.nox/py-3-9/lib/python3.9/site-packages/google/cloud/vision_helpers/__init__.py", line 76, in annotate_image
r = self.batch_annotate_images(
File "/workspace/vision/snippets/detect/.nox/py-3-9/lib/python3.9/site-packages/google/cloud/vision_v1/services/image_annotator/client.py", line 548, in batch_annotate_images
response = rpc(
File "/workspace/vision/snippets/detect/.nox/py-3-9/lib/python3.9/site-packages/google/api_core/gapic_v1/method.py", line 154, in __call__
return wrapped_func(*args, **kwargs)
File "/workspace/vision/snippets/detect/.nox/py-3-9/lib/python3.9/site-packages/google/api_core/grpc_helpers.py", line 74, in error_remapped_callable
raise exceptions.from_grpc_error(exc) from exc
google.api_core.exceptions.Unauthenticated: 401 Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.</pre></details> | non_test | vision snippets detect detect test test logos uri failed this test failed to configure my behavior see if i m commenting on this issue too often add the flakybot quiet label and i will stop commenting commit buildurl status failed test output traceback most recent call last file workspace vision snippets detect nox py lib site packages google api core grpc helpers py line in error remapped callable return callable args kwargs file workspace vision snippets detect nox py lib site packages grpc channel py line in call return end unary response blocking state call false none file workspace vision snippets detect nox py lib site packages grpc channel py line in end unary response blocking raise inactiverpcerror state grpc channel inactiverpcerror inactiverpcerror of rpc that terminated with status statuscode unauthenticated details request had invalid authentication credentials expected oauth access token login cookie or other valid authentication credential see debug error string unknown error received from peer created time grpc status grpc message request had invalid authentication credentials expected oauth access token login cookie or other valid authentication credential see the above exception was the direct cause of the following exception traceback most recent call last file workspace vision snippets detect detect test py line in test logos uri detect detect logos uri file name file workspace vision snippets detect detect py line in detect logos uri response client logo detection image image file workspace vision snippets detect nox py lib site packages google cloud vision helpers decorators py line in inner response self annotate image file workspace vision snippets detect nox py lib site packages google cloud vision helpers init py line in annotate image r self batch annotate images file workspace vision snippets detect nox py lib site packages google cloud vision services image annotator client py line in batch annotate images response rpc file workspace vision snippets detect nox py lib site packages google api core gapic method py line in call return wrapped func args kwargs file workspace vision snippets detect nox py lib site packages google api core grpc helpers py line in error remapped callable raise exceptions from grpc error exc from exc google api core exceptions unauthenticated request had invalid authentication credentials expected oauth access token login cookie or other valid authentication credential see | 0 |
92,794 | 8,378,416,599 | IssuesEvent | 2018-10-06 14:07:12 | kowainik/co-log | https://api.github.com/repos/kowainik/co-log | closed | Add `doctest` tests to `co-log-core` package | Hacktoberfest doc package:co-log-core tests | Blocked by #46
It's a great idea to test all functions in `Colog.Core` package using `doctest`. After #46 is implemented, `logStringStdout` action can be used as testing example. This will improve documentation significantly. | 1.0 | Add `doctest` tests to `co-log-core` package - Blocked by #46
It's a great idea to test all functions in `Colog.Core` package using `doctest`. After #46 is implemented, `logStringStdout` action can be used as testing example. This will improve documentation significantly. | test | add doctest tests to co log core package blocked by it s a great idea to test all functions in colog core package using doctest after is implemented logstringstdout action can be used as testing example this will improve documentation significantly | 1 |
76,800 | 7,545,579,960 | IssuesEvent | 2018-04-17 22:11:46 | ansible/ansible | https://api.github.com/repos/ansible/ansible | closed | Unstable integration test win_regedit | affects_2.6 bug module support:core test windows | ##### ISSUE TYPE
Bug Report
##### COMPONENT NAME
win_regedit integration test
##### ANSIBLE VERSION
```
2.6
```
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
Shippable
##### SUMMARY
Unstable integration test win_regedit:
https://app.shippable.com/github/ansible/ansible/runs/61213/17/tests
##### STEPS TO REPRODUCE
Run tests on Shippable.
##### EXPECTED RESULTS
Tests pass.
##### ACTUAL RESULTS
Tests are unstable or fail.
> test/integration/targets/win_regedit/tasks/tests.yml:712 / [windows-2016] windows: win_regedit : remove key in loaded hive (idempotent) path={{test_win_regedit_hive_key}}, state=absent, hive=C:\Users\Default\NTUSER.dat, delete_yes=True
> failure: failed to unload registry hive HKLM:\ANSIBLE from C:\Users\Default\NTUSER.dat: Failed to unload registry hive at ANSIBLE (Access is denied, Win32ErrorCode 5)
```
{
"changed": false,
"data_changed": false,
"data_type_changed": false,
"msg": "failed to unload registry hive HKLM:\\ANSIBLE from C:\\Users\\Default\\NTUSER.dat: Failed to unload registry hive at ANSIBLE (Access is denied, Win32ErrorCode 5)"
}
``` | 1.0 | Unstable integration test win_regedit - ##### ISSUE TYPE
Bug Report
##### COMPONENT NAME
win_regedit integration test
##### ANSIBLE VERSION
```
2.6
```
##### CONFIGURATION
N/A
##### OS / ENVIRONMENT
Shippable
##### SUMMARY
Unstable integration test win_regedit:
https://app.shippable.com/github/ansible/ansible/runs/61213/17/tests
##### STEPS TO REPRODUCE
Run tests on Shippable.
##### EXPECTED RESULTS
Tests pass.
##### ACTUAL RESULTS
Tests are unstable or fail.
> test/integration/targets/win_regedit/tasks/tests.yml:712 / [windows-2016] windows: win_regedit : remove key in loaded hive (idempotent) path={{test_win_regedit_hive_key}}, state=absent, hive=C:\Users\Default\NTUSER.dat, delete_yes=True
> failure: failed to unload registry hive HKLM:\ANSIBLE from C:\Users\Default\NTUSER.dat: Failed to unload registry hive at ANSIBLE (Access is denied, Win32ErrorCode 5)
```
{
"changed": false,
"data_changed": false,
"data_type_changed": false,
"msg": "failed to unload registry hive HKLM:\\ANSIBLE from C:\\Users\\Default\\NTUSER.dat: Failed to unload registry hive at ANSIBLE (Access is denied, Win32ErrorCode 5)"
}
``` | test | unstable integration test win regedit issue type bug report component name win regedit integration test ansible version configuration n a os environment shippable summary unstable integration test win regedit steps to reproduce run tests on shippable expected results tests pass actual results tests are unstable or fail test integration targets win regedit tasks tests yml windows win regedit remove key in loaded hive idempotent path test win regedit hive key state absent hive c users default ntuser dat delete yes true failure failed to unload registry hive hklm ansible from c users default ntuser dat failed to unload registry hive at ansible access is denied changed false data changed false data type changed false msg failed to unload registry hive hklm ansible from c users default ntuser dat failed to unload registry hive at ansible access is denied | 1 |
183,523 | 14,235,703,373 | IssuesEvent | 2020-11-18 15:08:10 | GTNewHorizons/GT-New-Horizons-Modpack | https://api.github.com/repos/GTNewHorizons/GT-New-Horizons-Modpack | closed | rework wetware and bio circuit boards | Status: FixedInDev Status: need to be tested Type: balancing Type: suggestion | #### Which modpack version are you using?
9.0 qf4
#### What do you suggest instead/what changes do you propose?
the curent cost for wetware and bio circuits make the only viable for UHV and UEV circuits
change the LuV sensors to 2-4 IV sensors this way you dont need 4 luV circuits to make 16 of them
the bio boards need UV sensors so if you want to make 16 zpm circuits you need 4UV or 8 ZPM
but if you want to make UV circuits with it then you need 12 UV circuits to make 16 of a total of 4 UV circuits
this makes the UV circuits the bio way basicly 4 times more expansif
for a 1 tier in circuit increase you need UV components for it witch is 2T higher then the LuV for wetware
change it to ZPM components and change the sensor to 2x LuV | 1.0 | rework wetware and bio circuit boards - #### Which modpack version are you using?
9.0 qf4
#### What do you suggest instead/what changes do you propose?
the curent cost for wetware and bio circuits make the only viable for UHV and UEV circuits
change the LuV sensors to 2-4 IV sensors this way you dont need 4 luV circuits to make 16 of them
the bio boards need UV sensors so if you want to make 16 zpm circuits you need 4UV or 8 ZPM
but if you want to make UV circuits with it then you need 12 UV circuits to make 16 of a total of 4 UV circuits
this makes the UV circuits the bio way basicly 4 times more expansif
for a 1 tier in circuit increase you need UV components for it witch is 2T higher then the LuV for wetware
change it to ZPM components and change the sensor to 2x LuV | test | rework wetware and bio circuit boards which modpack version are you using what do you suggest instead what changes do you propose the curent cost for wetware and bio circuits make the only viable for uhv and uev circuits change the luv sensors to iv sensors this way you dont need luv circuits to make of them the bio boards need uv sensors so if you want to make zpm circuits you need or zpm but if you want to make uv circuits with it then you need uv circuits to make of a total of uv circuits this makes the uv circuits the bio way basicly times more expansif for a tier in circuit increase you need uv components for it witch is higher then the luv for wetware change it to zpm components and change the sensor to luv | 1 |
114,385 | 11,845,315,543 | IssuesEvent | 2020-03-24 08:06:31 | SeasideSt/Seaside | https://api.github.com/repos/SeasideSt/Seaside | closed | Better documentation for caching restful handler routes | Documentation |
> I just stumbled across a fun problem that I hope someone can help me work around.
When using RESTful stuff (Seaside on VW 8.3 or thereabouts) with an image set to be headless and no-sources I hit a curious place where scanning for the route(s) involves parsing the sources (that I don't have connected) in order to find argument names. There is also an apparent option to cache the routes - presumably meaning that at some development stage I should be able to pickle the list of possible url to method mappings. However, it doesn't appear to be supported by any means other than editing the #shouldCacheRoutes method which seems to me to be an indication that this is not very supported.
>
> Does anyone remember anything about this that might help? Is/was there an expectation that deployed systems would have the routes cached before deployment? Any code that I haven't found that is meant for setting this up?
> You're supposed to override the method in your filter class. The
methods initial purpose was to avoid the performance hit of doing an
introspection on every web request as this may involve decompilation
or parsing to get the method names. You could use this for our problem
it you initialize a filter with sources present and then save the
image.
> You can use positional syntax like this {1} to avoid having to access
the parameter names. See also #852. | 1.0 | Better documentation for caching restful handler routes -
> I just stumbled across a fun problem that I hope someone can help me work around.
When using RESTful stuff (Seaside on VW 8.3 or thereabouts) with an image set to be headless and no-sources I hit a curious place where scanning for the route(s) involves parsing the sources (that I don't have connected) in order to find argument names. There is also an apparent option to cache the routes - presumably meaning that at some development stage I should be able to pickle the list of possible url to method mappings. However, it doesn't appear to be supported by any means other than editing the #shouldCacheRoutes method which seems to me to be an indication that this is not very supported.
>
> Does anyone remember anything about this that might help? Is/was there an expectation that deployed systems would have the routes cached before deployment? Any code that I haven't found that is meant for setting this up?
> You're supposed to override the method in your filter class. The
methods initial purpose was to avoid the performance hit of doing an
introspection on every web request as this may involve decompilation
or parsing to get the method names. You could use this for our problem
it you initialize a filter with sources present and then save the
image.
> You can use positional syntax like this {1} to avoid having to access
the parameter names. See also #852. | non_test | better documentation for caching restful handler routes i just stumbled across a fun problem that i hope someone can help me work around when using restful stuff seaside on vw or thereabouts with an image set to be headless and no sources i hit a curious place where scanning for the route s involves parsing the sources that i don t have connected in order to find argument names there is also an apparent option to cache the routes presumably meaning that at some development stage i should be able to pickle the list of possible url to method mappings however it doesn t appear to be supported by any means other than editing the shouldcacheroutes method which seems to me to be an indication that this is not very supported does anyone remember anything about this that might help is was there an expectation that deployed systems would have the routes cached before deployment any code that i haven t found that is meant for setting this up you re supposed to override the method in your filter class the methods initial purpose was to avoid the performance hit of doing an introspection on every web request as this may involve decompilation or parsing to get the method names you could use this for our problem it you initialize a filter with sources present and then save the image you can use positional syntax like this to avoid having to access the parameter names see also | 0 |
90,113 | 8,228,970,632 | IssuesEvent | 2018-09-07 07:50:14 | Cha-OS/colabo | https://api.github.com/repos/Cha-OS/colabo | opened | Simplify Navigation | Testing UX.UsrOnBoard+AvoidUsrErr | поједноставити онБоардинг - не треба специјална страница након логовања са дугмадима Почетак и Логоут, довољно одмах да се прикаже списак свих страница као и иначе и само се на врху дода опција за логоут | 1.0 | Simplify Navigation - поједноставити онБоардинг - не треба специјална страница након логовања са дугмадима Почетак и Логоут, довољно одмах да се прикаже списак свих страница као и иначе и само се на врху дода опција за логоут | test | simplify navigation поједноставити онбоардинг не треба специјална страница након логовања са дугмадима почетак и логоут довољно одмах да се прикаже списак свих страница као и иначе и само се на врху дода опција за логоут | 1 |
92,194 | 8,354,926,817 | IssuesEvent | 2018-10-02 14:30:35 | JuliaDynamics/DynamicalBilliards.jl | https://api.github.com/repos/JuliaDynamics/DynamicalBilliards.jl | closed | Rework tests: The have to be testing something more specific | tests | The amount of tests should not be reduced, but I suggest to make them test more specific stuff.
Like all collision times with all obstacles, or using `bounce!` directly, etc.
This will allow us to faster find breakages and faster fix buges and easier check failing PRs. | 1.0 | Rework tests: The have to be testing something more specific - The amount of tests should not be reduced, but I suggest to make them test more specific stuff.
Like all collision times with all obstacles, or using `bounce!` directly, etc.
This will allow us to faster find breakages and faster fix buges and easier check failing PRs. | test | rework tests the have to be testing something more specific the amount of tests should not be reduced but i suggest to make them test more specific stuff like all collision times with all obstacles or using bounce directly etc this will allow us to faster find breakages and faster fix buges and easier check failing prs | 1 |
106,793 | 16,719,043,342 | IssuesEvent | 2021-06-10 03:45:48 | alt-how/altinn-studio | https://api.github.com/repos/alt-how/altinn-studio | opened | WS-2021-0153 (Medium) detected in ejs-2.7.4.tgz | security vulnerability | ## WS-2021-0153 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ejs-2.7.4.tgz</b></p></summary>
<p>Embedded JavaScript templates</p>
<p>Library home page: <a href="https://registry.npmjs.org/ejs/-/ejs-2.7.4.tgz">https://registry.npmjs.org/ejs/-/ejs-2.7.4.tgz</a></p>
<p>Path to dependency file: altinn-studio/src/studio/src/designer/frontend/packages/schema-editor/package.json</p>
<p>Path to vulnerable library: altinn-studio/src/studio/src/designer/frontend/packages/schema-editor/node_modules/ejs/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-4.0.3.tgz (Root Library)
- workbox-webpack-plugin-5.1.4.tgz
- workbox-build-5.1.4.tgz
- rollup-plugin-off-main-thread-1.4.2.tgz
- :x: **ejs-2.7.4.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/alt-how/altinn-studio/commit/d21e22cf7e0e28119db7065baa1447a15df3d9e2">d21e22cf7e0e28119db7065baa1447a15df3d9e2</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Arbitrary Code Injection vulnerability was found in ejs before 3.1.6. Caused by filename which isn't sanitized for display.
<p>Publish Date: 2021-01-22
<p>URL: <a href=https://github.com/mde/ejs/commit/abaee2be937236b1b8da9a1f55096c17dda905fd>WS-2021-0153</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/mde/ejs/issues/571">https://github.com/mde/ejs/issues/571</a></p>
<p>Release Date: 2021-01-22</p>
<p>Fix Resolution: ejs - 3.1.6</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2021-0153 (Medium) detected in ejs-2.7.4.tgz - ## WS-2021-0153 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ejs-2.7.4.tgz</b></p></summary>
<p>Embedded JavaScript templates</p>
<p>Library home page: <a href="https://registry.npmjs.org/ejs/-/ejs-2.7.4.tgz">https://registry.npmjs.org/ejs/-/ejs-2.7.4.tgz</a></p>
<p>Path to dependency file: altinn-studio/src/studio/src/designer/frontend/packages/schema-editor/package.json</p>
<p>Path to vulnerable library: altinn-studio/src/studio/src/designer/frontend/packages/schema-editor/node_modules/ejs/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-4.0.3.tgz (Root Library)
- workbox-webpack-plugin-5.1.4.tgz
- workbox-build-5.1.4.tgz
- rollup-plugin-off-main-thread-1.4.2.tgz
- :x: **ejs-2.7.4.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/alt-how/altinn-studio/commit/d21e22cf7e0e28119db7065baa1447a15df3d9e2">d21e22cf7e0e28119db7065baa1447a15df3d9e2</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Arbitrary Code Injection vulnerability was found in ejs before 3.1.6. Caused by filename which isn't sanitized for display.
<p>Publish Date: 2021-01-22
<p>URL: <a href=https://github.com/mde/ejs/commit/abaee2be937236b1b8da9a1f55096c17dda905fd>WS-2021-0153</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/mde/ejs/issues/571">https://github.com/mde/ejs/issues/571</a></p>
<p>Release Date: 2021-01-22</p>
<p>Fix Resolution: ejs - 3.1.6</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_test | ws medium detected in ejs tgz ws medium severity vulnerability vulnerable library ejs tgz embedded javascript templates library home page a href path to dependency file altinn studio src studio src designer frontend packages schema editor package json path to vulnerable library altinn studio src studio src designer frontend packages schema editor node modules ejs package json dependency hierarchy react scripts tgz root library workbox webpack plugin tgz workbox build tgz rollup plugin off main thread tgz x ejs tgz vulnerable library found in head commit a href found in base branch master vulnerability details arbitrary code injection vulnerability was found in ejs before caused by filename which isn t sanitized for display publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required high user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution ejs step up your open source security game with whitesource | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.