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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
534,731 | 15,647,759,963 | IssuesEvent | 2021-03-23 04:04:57 | AY2021S2-CS2113T-T09-1/tp | https://api.github.com/repos/AY2021S2-CS2113T-T09-1/tp | closed | Add EditMaxCommand | priority.High type.Enhancement | As a user, I want to change the maximum capacity at any point of time so that I can manage the crowd efficiently depending on the situation. | 1.0 | Add EditMaxCommand - As a user, I want to change the maximum capacity at any point of time so that I can manage the crowd efficiently depending on the situation. | non_test | add editmaxcommand as a user i want to change the maximum capacity at any point of time so that i can manage the crowd efficiently depending on the situation | 0 |
133,353 | 10,819,036,407 | IssuesEvent | 2019-11-08 13:32:44 | bitcoin/bitcoin | https://api.github.com/repos/bitcoin/bitcoin | closed | v0.19.0 testing | Tests | Link to binaries:
* v0.19.0rc1 : https://bitcoincore.org/bin/bitcoin-core-0.19.0/test.rc1/ (coming soon)
Let us know which version you tested on which operating system.
If you find an issue, please search Github for known issues first and then open a new Github issue. This meta issue should not be used to report bugs, as a single thread makes it impossible to track more than one topic.
See [Release Notes](https://github.com/bitcoin-core/bitcoin-devwiki/wiki/0.19.0-Release-Notes-Draft) for a list of changes, and testing reports for earlier releases ([v0.18.0](https://github.com/bitcoin/bitcoin/issues/15555)), for an idea what to test. | 1.0 | v0.19.0 testing - Link to binaries:
* v0.19.0rc1 : https://bitcoincore.org/bin/bitcoin-core-0.19.0/test.rc1/ (coming soon)
Let us know which version you tested on which operating system.
If you find an issue, please search Github for known issues first and then open a new Github issue. This meta issue should not be used to report bugs, as a single thread makes it impossible to track more than one topic.
See [Release Notes](https://github.com/bitcoin-core/bitcoin-devwiki/wiki/0.19.0-Release-Notes-Draft) for a list of changes, and testing reports for earlier releases ([v0.18.0](https://github.com/bitcoin/bitcoin/issues/15555)), for an idea what to test. | test | testing link to binaries coming soon let us know which version you tested on which operating system if you find an issue please search github for known issues first and then open a new github issue this meta issue should not be used to report bugs as a single thread makes it impossible to track more than one topic see for a list of changes and testing reports for earlier releases for an idea what to test | 1 |
172,856 | 13,349,283,524 | IssuesEvent | 2020-08-29 23:43:00 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | roachtest: sqlsmith/setup=tpch-sf1/setting=no-mutations failed | C-test-failure O-roachtest O-robot branch-master release-blocker | [(roachtest).sqlsmith/setup=tpch-sf1/setting=no-mutations failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2231078&tab=buildLog) on [master@8b91062f9351d18f9104aff567cb152df162021e](https://github.com/cockroachdb/cockroach/commits/8b91062f9351d18f9104aff567cb152df162021e):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/sqlsmith/setup=tpch-sf1/setting=no-mutations/run_1
sqlsmith.go:172,sqlsmith.go:202,test_runner.go:754: error: pq: internal error: runtime error: invalid memory address or nil pointer dereference
stmt:
SELECT
tab_12.s_nationkey AS col_26,
tab_11.tableoid AS col_27,
tab_12.s_address AS col_28,
NULL AS col_29,
tab_12.s_phone AS col_30,
tab_11.ps_partkey AS col_31,
tab_12.s_nationkey AS col_32,
tab_12.s_comment AS col_33,
tab_11.ps_supplycost AS col_34,
tab_12.tableoid AS col_35,
e'\x04\x03%/TN':::STRING AS col_36,
tab_11.ps_partkey AS col_37
FROM
defaultdb.public.partsupp@ps_sk AS tab_11, defaultdb.public.supplier@[0] AS tab_12
ORDER BY
tab_11.tableoid ASC
LIMIT
38:::INT8;
```
<details><summary>More</summary><p>
Artifacts: [/sqlsmith/setup=tpch-sf1/setting=no-mutations](https://teamcity.cockroachdb.com/viewLog.html?buildId=2231078&tab=artifacts#/sqlsmith/setup=tpch-sf1/setting=no-mutations)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Asqlsmith%2Fsetup%3Dtpch-sf1%2Fsetting%3Dno-mutations.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
| 2.0 | roachtest: sqlsmith/setup=tpch-sf1/setting=no-mutations failed - [(roachtest).sqlsmith/setup=tpch-sf1/setting=no-mutations failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=2231078&tab=buildLog) on [master@8b91062f9351d18f9104aff567cb152df162021e](https://github.com/cockroachdb/cockroach/commits/8b91062f9351d18f9104aff567cb152df162021e):
```
The test failed on branch=master, cloud=gce:
test artifacts and logs in: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/artifacts/sqlsmith/setup=tpch-sf1/setting=no-mutations/run_1
sqlsmith.go:172,sqlsmith.go:202,test_runner.go:754: error: pq: internal error: runtime error: invalid memory address or nil pointer dereference
stmt:
SELECT
tab_12.s_nationkey AS col_26,
tab_11.tableoid AS col_27,
tab_12.s_address AS col_28,
NULL AS col_29,
tab_12.s_phone AS col_30,
tab_11.ps_partkey AS col_31,
tab_12.s_nationkey AS col_32,
tab_12.s_comment AS col_33,
tab_11.ps_supplycost AS col_34,
tab_12.tableoid AS col_35,
e'\x04\x03%/TN':::STRING AS col_36,
tab_11.ps_partkey AS col_37
FROM
defaultdb.public.partsupp@ps_sk AS tab_11, defaultdb.public.supplier@[0] AS tab_12
ORDER BY
tab_11.tableoid ASC
LIMIT
38:::INT8;
```
<details><summary>More</summary><p>
Artifacts: [/sqlsmith/setup=tpch-sf1/setting=no-mutations](https://teamcity.cockroachdb.com/viewLog.html?buildId=2231078&tab=artifacts#/sqlsmith/setup=tpch-sf1/setting=no-mutations)
[See this test on roachdash](https://roachdash.crdb.dev/?filter=status%3Aopen+t%3A.%2Asqlsmith%2Fsetup%3Dtpch-sf1%2Fsetting%3Dno-mutations.%2A&sort=title&restgroup=false&display=lastcommented+project)
<sub>powered by [pkg/cmd/internal/issues](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)</sub></p></details>
| test | roachtest sqlsmith setup tpch setting no mutations failed on the test failed on branch master cloud gce test artifacts and logs in home agent work go src github com cockroachdb cockroach artifacts sqlsmith setup tpch setting no mutations run sqlsmith go sqlsmith go test runner go error pq internal error runtime error invalid memory address or nil pointer dereference stmt select tab s nationkey as col tab tableoid as col tab s address as col null as col tab s phone as col tab ps partkey as col tab s nationkey as col tab s comment as col tab ps supplycost as col tab tableoid as col e tn string as col tab ps partkey as col from defaultdb public partsupp ps sk as tab defaultdb public supplier as tab order by tab tableoid asc limit more artifacts powered by | 1 |
105,323 | 9,056,439,654 | IssuesEvent | 2019-02-13 00:22:29 | phetsims/QA | https://api.github.com/repos/phetsims/QA | opened | RC test: Graphing Lines 1.3.0-rc.3 | QA:rc-test | <!---
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~ PhET Release Candidate Test Template ~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Notes and Instructions for Developers:
1. Comments indicate whether something can be omitted or edited.
2. Please check the comments before trying to omit or edit something.
3. Please don't rearrange the sections.
-->
@KatieWoe , @ariel-phet , @amanda-phet graphing-lines/1.3.0-rc.3 is ready for RC testing. This is a `brand=phet` release only (no PhET-iO, no a11y).
Document issues in https://github.com/phetsims/graphing-lines/issues and link to this issue.
NOTE: This should be tested at the same time as Graphing Slope-Intercept 1.1.0-rc.3.
Assigning to @ariel-phet for prioritization.
<!---
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
////////// Section 1: General RC Testing [CAN BE OMITTED, SHOULD BE EDITED IF NOT OMITTED]
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-->
<details>
<summary><b>General RC Test</b></summary>
<!--- [DO NOT OMIT, CAN BE EDITED] -->
<h3>What to Test</h3>
- Click every single button.
- Test all possible forms of input.
- Test all mouse/trackpad inputs.
- Test all touchscreen inputs.
- If there is sound, make sure it works.
- Make sure you can't lose anything.
- Play with the sim normally.
- Try to break the sim.
- Test all query parameters on all platforms. (See [QA Book](https://github.com/phetsims/QA/blob/master/doc/qa-book.md) for a list of query parameters.)
- Download HTML on Chrome and iOS.
- Make sure the iFrame version of the simulation is working as intended on all platforms.
- Make sure the XHTML version of the simulation is working as intended on all platforms.
- Complete the test matrix.
- Don't forget to make sure the sim works with Legends of Learning.
- Check [this](https://docs.google.com/spreadsheets/d/1umIAmhn89WN1nzcHKhYJcv-n3Oj6ps1wITc-CjWYytE/edit#gid=0) LoL spreadsheet and notify AR if it not there.
- If this is rc.1 please do a memory test.
<!--- [CAN BE OMITTED, SHOULD BE EDITED IF NOT OMITTED] -->
<h3>Issues to Verify</h3>
Check these issues off and close them if they are fixed. Otherwise, post a comment in the issue saying that it wasn't fixed.
This issue is specific to Graphing Lines, and can be tested on 1 platform:
- [ ] [update credits for 1.3.0 release](https://github.com/phetsims/graphing-lines/issues/123)
These issues must be tested for both Graphing Lines and Graphing Slope-Intercept. They are all platform independent; if they work on one platform, they will work on all platforms. So a full test matrix is unnecessary for this RC. Spot checking on a couple of platforms is sufficient.
- [ ] [Short max widths for game answers](https://github.com/phetsims/graphing-lines/issues/117)
- [ ] [Pink shadow stays behind when manipulator is moved](https://github.com/phetsims/graphing-lines/issues/119)
- [ ] [Active line label overlaps...](https://github.com/phetsims/graphing-lines/issues/120)
<!--- [DO NOT OMIT, CAN BE EDITED] -->
<h3>Link(s)</h3>
- **[Simulation](https://phet-dev.colorado.edu/html/graphing-lines/1.3.0-rc.3/phet/graphing-lines_en_phet.html)**
- **[iFrame](https://phet-dev.colorado.edu/html/graphing-lines/1.3.0-rc.3/phet/graphing-lines_en_iframe_phet.html)**
- **[XHTML](https://phet-dev.colorado.edu/html/graphing-lines/1.3.0-rc.3/phet/xhtml/graphing-lines_all_phet.html)**
- **[Test Matrix](https://docs.google.com/spreadsheets/d/1J-Fb_6PLNqrygQgCjQj0tVtPovb3P0CBWPsrrz3d4Uw/edit#gid=34592960)**
- **[Legends of Learning Harness](https://developers.legendsoflearning.com/public-harness/index.html?startPayload=%7B%22languageCode%22%3A%22en%22%7D)**
<hr>
</details>
<!---
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
////////// Section 0: FAQs for QA Members [DO NOT OMIT, DO NOT EDIT]
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-->
<details>
<summary><b>FAQs for QA Members</b></summary>
<br>
<!--- Subsection 0.1: There are multiple tests in this issue... What should I test first? [DO NOT OMIT, DO NOT EDIT] -->
<details>
<summary><i>There are multiple tests in this issue... Which test should I do first?</i></summary>
Test in order! Test the first thing first, the second thing second, and so on.
</details>
<br>
<!--- Subsection 0.2: How should I format my issue? [DO NOT OMIT, DO NOT EDIT] -->
<details>
<summary><i>How should I format my issue?</i></summary>
Here's a template for making issues:
<b>Test Device</b>
blah
<b>Operating System</b>
blah
<b>Browser</b>
blah
<b>Problem Description</b>
blah
<b>Steps to Reproduce</b>
blah
<b>Visuals</b>
blah
<details>
<summary><b>Troubleshooting Information</b></summary>
blah
</details>
</details>
<br>
<!--- Subsection 0.3: Who should I assign? [DO NOT OMIT, DO NOT EDIT] -->
<details>
<summary><i>Who should I assign?</i></summary>
We typically assign the developer who opened the issue in the QA repository.
</details>
<br>
<!--- Subsection 0.4: My question isn't in here... What should I do? [DO NOT OMIT, DO NOT EDIT] -->
<details>
<summary><i>My question isn't in here... What should I do?</i></summary>
You should:
1. Consult the [QA Book](https://github.com/phetsims/QA/blob/master/doc/qa-book.md).
2. Google it.
3. Ask Katie.
4. Ask a developer.
5. Google it again.
6. Cry.
</details>
<br>
<hr>
</details> | 1.0 | RC test: Graphing Lines 1.3.0-rc.3 - <!---
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~ PhET Release Candidate Test Template ~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Notes and Instructions for Developers:
1. Comments indicate whether something can be omitted or edited.
2. Please check the comments before trying to omit or edit something.
3. Please don't rearrange the sections.
-->
@KatieWoe , @ariel-phet , @amanda-phet graphing-lines/1.3.0-rc.3 is ready for RC testing. This is a `brand=phet` release only (no PhET-iO, no a11y).
Document issues in https://github.com/phetsims/graphing-lines/issues and link to this issue.
NOTE: This should be tested at the same time as Graphing Slope-Intercept 1.1.0-rc.3.
Assigning to @ariel-phet for prioritization.
<!---
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
////////// Section 1: General RC Testing [CAN BE OMITTED, SHOULD BE EDITED IF NOT OMITTED]
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-->
<details>
<summary><b>General RC Test</b></summary>
<!--- [DO NOT OMIT, CAN BE EDITED] -->
<h3>What to Test</h3>
- Click every single button.
- Test all possible forms of input.
- Test all mouse/trackpad inputs.
- Test all touchscreen inputs.
- If there is sound, make sure it works.
- Make sure you can't lose anything.
- Play with the sim normally.
- Try to break the sim.
- Test all query parameters on all platforms. (See [QA Book](https://github.com/phetsims/QA/blob/master/doc/qa-book.md) for a list of query parameters.)
- Download HTML on Chrome and iOS.
- Make sure the iFrame version of the simulation is working as intended on all platforms.
- Make sure the XHTML version of the simulation is working as intended on all platforms.
- Complete the test matrix.
- Don't forget to make sure the sim works with Legends of Learning.
- Check [this](https://docs.google.com/spreadsheets/d/1umIAmhn89WN1nzcHKhYJcv-n3Oj6ps1wITc-CjWYytE/edit#gid=0) LoL spreadsheet and notify AR if it not there.
- If this is rc.1 please do a memory test.
<!--- [CAN BE OMITTED, SHOULD BE EDITED IF NOT OMITTED] -->
<h3>Issues to Verify</h3>
Check these issues off and close them if they are fixed. Otherwise, post a comment in the issue saying that it wasn't fixed.
This issue is specific to Graphing Lines, and can be tested on 1 platform:
- [ ] [update credits for 1.3.0 release](https://github.com/phetsims/graphing-lines/issues/123)
These issues must be tested for both Graphing Lines and Graphing Slope-Intercept. They are all platform independent; if they work on one platform, they will work on all platforms. So a full test matrix is unnecessary for this RC. Spot checking on a couple of platforms is sufficient.
- [ ] [Short max widths for game answers](https://github.com/phetsims/graphing-lines/issues/117)
- [ ] [Pink shadow stays behind when manipulator is moved](https://github.com/phetsims/graphing-lines/issues/119)
- [ ] [Active line label overlaps...](https://github.com/phetsims/graphing-lines/issues/120)
<!--- [DO NOT OMIT, CAN BE EDITED] -->
<h3>Link(s)</h3>
- **[Simulation](https://phet-dev.colorado.edu/html/graphing-lines/1.3.0-rc.3/phet/graphing-lines_en_phet.html)**
- **[iFrame](https://phet-dev.colorado.edu/html/graphing-lines/1.3.0-rc.3/phet/graphing-lines_en_iframe_phet.html)**
- **[XHTML](https://phet-dev.colorado.edu/html/graphing-lines/1.3.0-rc.3/phet/xhtml/graphing-lines_all_phet.html)**
- **[Test Matrix](https://docs.google.com/spreadsheets/d/1J-Fb_6PLNqrygQgCjQj0tVtPovb3P0CBWPsrrz3d4Uw/edit#gid=34592960)**
- **[Legends of Learning Harness](https://developers.legendsoflearning.com/public-harness/index.html?startPayload=%7B%22languageCode%22%3A%22en%22%7D)**
<hr>
</details>
<!---
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
////////// Section 0: FAQs for QA Members [DO NOT OMIT, DO NOT EDIT]
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
-->
<details>
<summary><b>FAQs for QA Members</b></summary>
<br>
<!--- Subsection 0.1: There are multiple tests in this issue... What should I test first? [DO NOT OMIT, DO NOT EDIT] -->
<details>
<summary><i>There are multiple tests in this issue... Which test should I do first?</i></summary>
Test in order! Test the first thing first, the second thing second, and so on.
</details>
<br>
<!--- Subsection 0.2: How should I format my issue? [DO NOT OMIT, DO NOT EDIT] -->
<details>
<summary><i>How should I format my issue?</i></summary>
Here's a template for making issues:
<b>Test Device</b>
blah
<b>Operating System</b>
blah
<b>Browser</b>
blah
<b>Problem Description</b>
blah
<b>Steps to Reproduce</b>
blah
<b>Visuals</b>
blah
<details>
<summary><b>Troubleshooting Information</b></summary>
blah
</details>
</details>
<br>
<!--- Subsection 0.3: Who should I assign? [DO NOT OMIT, DO NOT EDIT] -->
<details>
<summary><i>Who should I assign?</i></summary>
We typically assign the developer who opened the issue in the QA repository.
</details>
<br>
<!--- Subsection 0.4: My question isn't in here... What should I do? [DO NOT OMIT, DO NOT EDIT] -->
<details>
<summary><i>My question isn't in here... What should I do?</i></summary>
You should:
1. Consult the [QA Book](https://github.com/phetsims/QA/blob/master/doc/qa-book.md).
2. Google it.
3. Ask Katie.
4. Ask a developer.
5. Google it again.
6. Cry.
</details>
<br>
<hr>
</details> | test | rc test graphing lines rc phet release candidate test template notes and instructions for developers comments indicate whether something can be omitted or edited please check the comments before trying to omit or edit something please don t rearrange the sections katiewoe ariel phet amanda phet graphing lines rc is ready for rc testing this is a brand phet release only no phet io no document issues in and link to this issue note this should be tested at the same time as graphing slope intercept rc assigning to ariel phet for prioritization section general rc testing general rc test what to test click every single button test all possible forms of input test all mouse trackpad inputs test all touchscreen inputs if there is sound make sure it works make sure you can t lose anything play with the sim normally try to break the sim test all query parameters on all platforms see for a list of query parameters download html on chrome and ios make sure the iframe version of the simulation is working as intended on all platforms make sure the xhtml version of the simulation is working as intended on all platforms complete the test matrix don t forget to make sure the sim works with legends of learning check lol spreadsheet and notify ar if it not there if this is rc please do a memory test issues to verify check these issues off and close them if they are fixed otherwise post a comment in the issue saying that it wasn t fixed this issue is specific to graphing lines and can be tested on platform these issues must be tested for both graphing lines and graphing slope intercept they are all platform independent if they work on one platform they will work on all platforms so a full test matrix is unnecessary for this rc spot checking on a couple of platforms is sufficient link s section faqs for qa members faqs for qa members there are multiple tests in this issue which test should i do first test in order test the first thing first the second thing second and so on how should i format my issue here s a template for making issues test device blah operating system blah browser blah problem description blah steps to reproduce blah visuals blah troubleshooting information blah who should i assign we typically assign the developer who opened the issue in the qa repository my question isn t in here what should i do you should consult the google it ask katie ask a developer google it again cry | 1 |
13,351 | 10,218,714,741 | IssuesEvent | 2019-08-15 16:38:29 | algorand/go-algorand | https://api.github.com/repos/algorand/go-algorand | opened | Investigate agreement message drops during auctions | bug infrastructure | (originally reported by @tsachiherman)
During the auctions, I have noticed that some of the agreement messages are being dropped.
The "messagesDropped.Inc(nil)" counter was increasing, which could be an issue.
We would likely want to argument this counter with some data that would help us to identify which tag and data size are being dropped. this should help us resolving this issue.
Excessive message drops (like this) could lead to stalls, so we want to handle this early. I suspect that we haven't seen this before due to past network library performance issues. | 1.0 | Investigate agreement message drops during auctions - (originally reported by @tsachiherman)
During the auctions, I have noticed that some of the agreement messages are being dropped.
The "messagesDropped.Inc(nil)" counter was increasing, which could be an issue.
We would likely want to argument this counter with some data that would help us to identify which tag and data size are being dropped. this should help us resolving this issue.
Excessive message drops (like this) could lead to stalls, so we want to handle this early. I suspect that we haven't seen this before due to past network library performance issues. | non_test | investigate agreement message drops during auctions originally reported by tsachiherman during the auctions i have noticed that some of the agreement messages are being dropped the messagesdropped inc nil counter was increasing which could be an issue we would likely want to argument this counter with some data that would help us to identify which tag and data size are being dropped this should help us resolving this issue excessive message drops like this could lead to stalls so we want to handle this early i suspect that we haven t seen this before due to past network library performance issues | 0 |
150,316 | 19,603,608,856 | IssuesEvent | 2022-01-06 06:06:57 | snykiotcubedev/react-17.0.2 | https://api.github.com/repos/snykiotcubedev/react-17.0.2 | opened | CVE-2021-3803 (High) detected in nth-check-1.0.1.tgz, nth-check-1.0.2.tgz | security vulnerability | ## CVE-2021-3803 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>nth-check-1.0.1.tgz</b>, <b>nth-check-1.0.2.tgz</b></p></summary>
<p>
<details><summary><b>nth-check-1.0.1.tgz</b></p></summary>
<p>performant nth-check parser & compiler</p>
<p>Library home page: <a href="https://registry.npmjs.org/nth-check/-/nth-check-1.0.1.tgz">https://registry.npmjs.org/nth-check/-/nth-check-1.0.1.tgz</a></p>
<p>
Dependency Hierarchy:
- react-scripts-1.1.4.tgz (Root Library)
- html-webpack-plugin-2.29.0.tgz
- pretty-error-2.1.1.tgz
- renderkid-2.0.1.tgz
- css-select-1.2.0.tgz
- :x: **nth-check-1.0.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>nth-check-1.0.2.tgz</b></p></summary>
<p>performant nth-check parser & compiler</p>
<p>Library home page: <a href="https://registry.npmjs.org/nth-check/-/nth-check-1.0.2.tgz">https://registry.npmjs.org/nth-check/-/nth-check-1.0.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/nth-check/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-3.4.1.tgz (Root Library)
- html-webpack-plugin-4.0.0-beta.11.tgz
- pretty-error-2.1.1.tgz
- renderkid-2.0.3.tgz
- css-select-1.2.0.tgz
- :x: **nth-check-1.0.2.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/snykiotcubedev/react-17.0.2/commit/c546697344431dcd6c04b4fea877c488ef3a6ad5">c546697344431dcd6c04b4fea877c488ef3a6ad5</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
nth-check is vulnerable to Inefficient Regular Expression Complexity
<p>Publish Date: 2021-09-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3803>CVE-2021-3803</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/fb55/nth-check/compare/v2.0.0...v2.0.1">https://github.com/fb55/nth-check/compare/v2.0.0...v2.0.1</a></p>
<p>Release Date: 2021-09-17</p>
<p>Fix Resolution: nth-check - v2.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-3803 (High) detected in nth-check-1.0.1.tgz, nth-check-1.0.2.tgz - ## CVE-2021-3803 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>nth-check-1.0.1.tgz</b>, <b>nth-check-1.0.2.tgz</b></p></summary>
<p>
<details><summary><b>nth-check-1.0.1.tgz</b></p></summary>
<p>performant nth-check parser & compiler</p>
<p>Library home page: <a href="https://registry.npmjs.org/nth-check/-/nth-check-1.0.1.tgz">https://registry.npmjs.org/nth-check/-/nth-check-1.0.1.tgz</a></p>
<p>
Dependency Hierarchy:
- react-scripts-1.1.4.tgz (Root Library)
- html-webpack-plugin-2.29.0.tgz
- pretty-error-2.1.1.tgz
- renderkid-2.0.1.tgz
- css-select-1.2.0.tgz
- :x: **nth-check-1.0.1.tgz** (Vulnerable Library)
</details>
<details><summary><b>nth-check-1.0.2.tgz</b></p></summary>
<p>performant nth-check parser & compiler</p>
<p>Library home page: <a href="https://registry.npmjs.org/nth-check/-/nth-check-1.0.2.tgz">https://registry.npmjs.org/nth-check/-/nth-check-1.0.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/nth-check/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-3.4.1.tgz (Root Library)
- html-webpack-plugin-4.0.0-beta.11.tgz
- pretty-error-2.1.1.tgz
- renderkid-2.0.3.tgz
- css-select-1.2.0.tgz
- :x: **nth-check-1.0.2.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/snykiotcubedev/react-17.0.2/commit/c546697344431dcd6c04b4fea877c488ef3a6ad5">c546697344431dcd6c04b4fea877c488ef3a6ad5</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
nth-check is vulnerable to Inefficient Regular Expression Complexity
<p>Publish Date: 2021-09-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3803>CVE-2021-3803</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/fb55/nth-check/compare/v2.0.0...v2.0.1">https://github.com/fb55/nth-check/compare/v2.0.0...v2.0.1</a></p>
<p>Release Date: 2021-09-17</p>
<p>Fix Resolution: nth-check - v2.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_test | cve high detected in nth check tgz nth check tgz cve high severity vulnerability vulnerable libraries nth check tgz nth check tgz nth check tgz performant nth check parser compiler library home page a href dependency hierarchy react scripts tgz root library html webpack plugin tgz pretty error tgz renderkid tgz css select tgz x nth check tgz vulnerable library nth check tgz performant nth check parser compiler library home page a href path to dependency file package json path to vulnerable library node modules nth check package json dependency hierarchy react scripts tgz root library html webpack plugin beta tgz pretty error tgz renderkid tgz css select tgz x nth check tgz vulnerable library found in head commit a href found in base branch main vulnerability details nth check is vulnerable to inefficient regular expression complexity publish date url a href cvss score details base score metrics exploitability metrics attack vector 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 nth check step up your open source security game with whitesource | 0 |
329,346 | 10,014,988,719 | IssuesEvent | 2019-07-15 18:55:21 | pravega/pravega | https://api.github.com/repos/pravega/pravega | opened | Add Metric for Container Recovery Time | area/metrics area/segmentstore kind/enhancement priority/P2 version/0.6.0 | **Problem description**
Container recovery in the Segment Store may take a variable amount of time to complete. In some situations, container recoveries may take long time to complete, which could indicate a problem in the Pravega deployment (e.g., slow tier 2 storage). We need a metric to expose the time that container recoveries take, to identify and alert if there is some problem.
**Problem location**
Segment Store metrics.
**Suggestions for an improvement**
Add new metric publishing container recovery times. | 1.0 | Add Metric for Container Recovery Time - **Problem description**
Container recovery in the Segment Store may take a variable amount of time to complete. In some situations, container recoveries may take long time to complete, which could indicate a problem in the Pravega deployment (e.g., slow tier 2 storage). We need a metric to expose the time that container recoveries take, to identify and alert if there is some problem.
**Problem location**
Segment Store metrics.
**Suggestions for an improvement**
Add new metric publishing container recovery times. | non_test | add metric for container recovery time problem description container recovery in the segment store may take a variable amount of time to complete in some situations container recoveries may take long time to complete which could indicate a problem in the pravega deployment e g slow tier storage we need a metric to expose the time that container recoveries take to identify and alert if there is some problem problem location segment store metrics suggestions for an improvement add new metric publishing container recovery times | 0 |
587,737 | 17,630,511,244 | IssuesEvent | 2021-08-19 07:19:39 | wso2/product-is | https://api.github.com/repos/wso2/product-is | closed | Inconsistent OIDC claim mapping for http://wso2.org/claims/locality claim | Priority/Highest docs bug | **Problem:**
The localization functionality of email templates works with the language code given to the local claim "http://wso2.org/claims/locality" (which has been mapped to OIDC claim "locality")
The local claim "http://wso2.org/claims/locality" is being mapped to the OIDC claim "locality". But according to the OIDC specification [2] the purpose of this claim is to have an address of a city (example "Los Angeles").
**Possible solutions:**
1. change OIDC to local mapping as below.
locale > http://wso2.org/claims/locality
locality > http://wso2.org/claims/local
OR
locale > http://wso2.org/claims/locality
locality > http://wso2.org/claims/address.locality
2. change the email localization implementation by considering local claim "http://wso2.org/claims/local" instead of "http://wso2.org/claims/locality
| 1.0 | Inconsistent OIDC claim mapping for http://wso2.org/claims/locality claim - **Problem:**
The localization functionality of email templates works with the language code given to the local claim "http://wso2.org/claims/locality" (which has been mapped to OIDC claim "locality")
The local claim "http://wso2.org/claims/locality" is being mapped to the OIDC claim "locality". But according to the OIDC specification [2] the purpose of this claim is to have an address of a city (example "Los Angeles").
**Possible solutions:**
1. change OIDC to local mapping as below.
locale > http://wso2.org/claims/locality
locality > http://wso2.org/claims/local
OR
locale > http://wso2.org/claims/locality
locality > http://wso2.org/claims/address.locality
2. change the email localization implementation by considering local claim "http://wso2.org/claims/local" instead of "http://wso2.org/claims/locality
| non_test | inconsistent oidc claim mapping for claim problem the localization functionality of email templates works with the language code given to the local claim which has been mapped to oidc claim locality the local claim is being mapped to the oidc claim locality but according to the oidc specification the purpose of this claim is to have an address of a city example los angeles possible solutions change oidc to local mapping as below locale locality or locale locality change the email localization implementation by considering local claim instead of | 0 |
344,246 | 30,728,282,225 | IssuesEvent | 2023-07-27 21:46:57 | Chingling152/my-financial-hub-api | https://api.github.com/repos/Chingling152/my-financial-hub-api | closed | Improve Auth unit tests | invalid tests improvements | - [x] Remove exception tests
- [x] Services
- [x] Providers
- [x] Repositories
| 1.0 | Improve Auth unit tests - - [x] Remove exception tests
- [x] Services
- [x] Providers
- [x] Repositories
| test | improve auth unit tests remove exception tests services providers repositories | 1 |
557,900 | 16,521,980,157 | IssuesEvent | 2021-05-26 15:25:56 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | classic.minecraft.net - site is not usable | browser-fixme priority-normal | <!-- @browser: 13.1 -->
<!-- @ua_header: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1 Safari/605.1.15 -->
<!-- @reported_with: mobile-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/74839 -->
**URL**: https://classic.minecraft.net/?host=xoXkgad16MQntZqz
**Browser / Version**: 13.1
**Operating System**: Mac OS X 10.15.4
**Tested Another Browser**: Yes Chrome
**Problem type**: Site is not usable
**Description**: Page not loading correctly
**Steps to Reproduce**:
It just wouldnโt load and it just didnโt work.
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with โค๏ธ_ | 1.0 | classic.minecraft.net - site is not usable - <!-- @browser: 13.1 -->
<!-- @ua_header: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1 Safari/605.1.15 -->
<!-- @reported_with: mobile-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/74839 -->
**URL**: https://classic.minecraft.net/?host=xoXkgad16MQntZqz
**Browser / Version**: 13.1
**Operating System**: Mac OS X 10.15.4
**Tested Another Browser**: Yes Chrome
**Problem type**: Site is not usable
**Description**: Page not loading correctly
**Steps to Reproduce**:
It just wouldnโt load and it just didnโt work.
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with โค๏ธ_ | non_test | classic minecraft net site is not usable url browser version operating system mac os x tested another browser yes chrome problem type site is not usable description page not loading correctly steps to reproduce it just wouldnโt load and it just didnโt work browser configuration none from with โค๏ธ | 0 |
159,053 | 13,754,758,782 | IssuesEvent | 2020-10-06 17:24:53 | warriordog/mooltipage | https://api.github.com/repos/warriordog/mooltipage | opened | Docs: headers are not in evenly-descending order | bug documentation good first issue | In the documentation site, header classes (h1, h2, h3, etc) currently skip from h1 or h2 straight to h5. These h5s need to be changed to h3s, but the site CSS should be adjusted so that h3 looks like h5 currently does. h4, h5, and h6 will also need to downsized appropriately, so that all the header classes are smaller / less attention-grabbing than the previous one. | 1.0 | Docs: headers are not in evenly-descending order - In the documentation site, header classes (h1, h2, h3, etc) currently skip from h1 or h2 straight to h5. These h5s need to be changed to h3s, but the site CSS should be adjusted so that h3 looks like h5 currently does. h4, h5, and h6 will also need to downsized appropriately, so that all the header classes are smaller / less attention-grabbing than the previous one. | non_test | docs headers are not in evenly descending order in the documentation site header classes etc currently skip from or straight to these need to be changed to but the site css should be adjusted so that looks like currently does and will also need to downsized appropriately so that all the header classes are smaller less attention grabbing than the previous one | 0 |
187,855 | 6,761,657,278 | IssuesEvent | 2017-10-25 03:12:02 | CS2103AUG2017-W11-B2/main | https://api.github.com/repos/CS2103AUG2017-W11-B2/main | closed | Make use of API | priority.high type.bug type.task | Make use of the respective command's COMMAND_WORD instead of manual string literals for the `autocompleteCommandList` and make use of CliSyntax.java class for any generic string literals you encounter. `addCommandFieldList` values can be set as a property in all the commands or as fields in CliSyntax.
| 1.0 | Make use of API - Make use of the respective command's COMMAND_WORD instead of manual string literals for the `autocompleteCommandList` and make use of CliSyntax.java class for any generic string literals you encounter. `addCommandFieldList` values can be set as a property in all the commands or as fields in CliSyntax.
| non_test | make use of api make use of the respective command s command word instead of manual string literals for the autocompletecommandlist and make use of clisyntax java class for any generic string literals you encounter addcommandfieldlist values can be set as a property in all the commands or as fields in clisyntax | 0 |
142,270 | 13,019,020,716 | IssuesEvent | 2020-07-26 20:16:44 | aaugustin/websockets | https://api.github.com/repos/aaugustin/websockets | closed | Object oriented Websocket Client and Server example | documentation help wanted low priority | I'm trying to implement object oriented Websocket client and server. Since `websockets` is completely coroutine based, I'm finding it difficult to go ahead with implementation. Is it possible to wrap it around classes? Are there any examples of using it in this way? | 1.0 | Object oriented Websocket Client and Server example - I'm trying to implement object oriented Websocket client and server. Since `websockets` is completely coroutine based, I'm finding it difficult to go ahead with implementation. Is it possible to wrap it around classes? Are there any examples of using it in this way? | non_test | object oriented websocket client and server example i m trying to implement object oriented websocket client and server since websockets is completely coroutine based i m finding it difficult to go ahead with implementation is it possible to wrap it around classes are there any examples of using it in this way | 0 |
342,061 | 30,607,393,405 | IssuesEvent | 2023-07-23 07:07:32 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | closed | Fix tensor.test_torch_instance_split | PyTorch Frontend Sub Task Failing Test | | | |
|---|---|
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5634736017/job/15264943658"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5634736017/job/15264943658"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5634736017/job/15264943658"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5634736017/job/15264943658"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5634736017/job/15264943658"><img src=https://img.shields.io/badge/-success-success></a>
| 1.0 | Fix tensor.test_torch_instance_split - | | |
|---|---|
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5634736017/job/15264943658"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5634736017/job/15264943658"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5634736017/job/15264943658"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5634736017/job/15264943658"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5634736017/job/15264943658"><img src=https://img.shields.io/badge/-success-success></a>
| test | fix tensor test torch instance split tensorflow a href src jax a href src numpy a href src torch a href src paddle a href src | 1 |
88,084 | 15,800,728,535 | IssuesEvent | 2021-04-03 01:01:15 | Mohib-hub/concord | https://api.github.com/repos/Mohib-hub/concord | opened | CVE-2021-28165 (High) detected in jetty-io-9.4.26.v20200117.jar | security vulnerability | ## CVE-2021-28165 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jetty-io-9.4.26.v20200117.jar</b></p></summary>
<p>The Eclipse Jetty Project</p>
<p>Library home page: <a href="http://www.eclipse.org/jetty">http://www.eclipse.org/jetty</a></p>
<p>Path to dependency file: concord/docker-images/agent/pom.xml</p>
<p>Path to vulnerable library: /tmp/ws-ua_20200427143311_SKNJZT/downloadResource_PWLLDD/20200427143716/jetty-io-9.4.26.v20200117.jar</p>
<p>
Dependency Hierarchy:
- concord-queue-client-1.48.2-SNAPSHOT.jar (Root Library)
- jetty-client-9.4.26.v20200117.jar
- :x: **jetty-io-9.4.26.v20200117.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Eclipse Jetty 7.2.2 to 9.4.38, 10.0.0.alpha0 to 10.0.1, and 11.0.0.alpha0 to 11.0.1, CPU usage can reach 100% upon receiving a large invalid TLS frame.
<p>Publish Date: 2021-04-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-28165>CVE-2021-28165</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/eclipse/jetty.project/security/advisories/GHSA-26vr-8j45-3r4w">https://github.com/eclipse/jetty.project/security/advisories/GHSA-26vr-8j45-3r4w</a></p>
<p>Release Date: 2021-04-01</p>
<p>Fix Resolution: org.eclipse.jetty:jetty-io:9.4.39, org.eclipse.jetty:jetty-io:10.0.2, org.eclipse.jetty:jetty-io:11.0.2</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.eclipse.jetty","packageName":"jetty-io","packageVersion":"9.4.26.v20200117","packageFilePaths":["/docker-images/agent/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"com.walmartlabs.concord.server:concord-queue-client:1.48.2-SNAPSHOT;org.eclipse.jetty:jetty-client:9.4.26.v20200117;org.eclipse.jetty:jetty-io:9.4.26.v20200117","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.eclipse.jetty:jetty-io:9.4.39, org.eclipse.jetty:jetty-io:10.0.2, org.eclipse.jetty:jetty-io:11.0.2"}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2021-28165","vulnerabilityDetails":"In Eclipse Jetty 7.2.2 to 9.4.38, 10.0.0.alpha0 to 10.0.1, and 11.0.0.alpha0 to 11.0.1, CPU usage can reach 100% upon receiving a large invalid TLS frame.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-28165","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 | CVE-2021-28165 (High) detected in jetty-io-9.4.26.v20200117.jar - ## CVE-2021-28165 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jetty-io-9.4.26.v20200117.jar</b></p></summary>
<p>The Eclipse Jetty Project</p>
<p>Library home page: <a href="http://www.eclipse.org/jetty">http://www.eclipse.org/jetty</a></p>
<p>Path to dependency file: concord/docker-images/agent/pom.xml</p>
<p>Path to vulnerable library: /tmp/ws-ua_20200427143311_SKNJZT/downloadResource_PWLLDD/20200427143716/jetty-io-9.4.26.v20200117.jar</p>
<p>
Dependency Hierarchy:
- concord-queue-client-1.48.2-SNAPSHOT.jar (Root Library)
- jetty-client-9.4.26.v20200117.jar
- :x: **jetty-io-9.4.26.v20200117.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Eclipse Jetty 7.2.2 to 9.4.38, 10.0.0.alpha0 to 10.0.1, and 11.0.0.alpha0 to 11.0.1, CPU usage can reach 100% upon receiving a large invalid TLS frame.
<p>Publish Date: 2021-04-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-28165>CVE-2021-28165</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/eclipse/jetty.project/security/advisories/GHSA-26vr-8j45-3r4w">https://github.com/eclipse/jetty.project/security/advisories/GHSA-26vr-8j45-3r4w</a></p>
<p>Release Date: 2021-04-01</p>
<p>Fix Resolution: org.eclipse.jetty:jetty-io:9.4.39, org.eclipse.jetty:jetty-io:10.0.2, org.eclipse.jetty:jetty-io:11.0.2</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.eclipse.jetty","packageName":"jetty-io","packageVersion":"9.4.26.v20200117","packageFilePaths":["/docker-images/agent/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"com.walmartlabs.concord.server:concord-queue-client:1.48.2-SNAPSHOT;org.eclipse.jetty:jetty-client:9.4.26.v20200117;org.eclipse.jetty:jetty-io:9.4.26.v20200117","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.eclipse.jetty:jetty-io:9.4.39, org.eclipse.jetty:jetty-io:10.0.2, org.eclipse.jetty:jetty-io:11.0.2"}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2021-28165","vulnerabilityDetails":"In Eclipse Jetty 7.2.2 to 9.4.38, 10.0.0.alpha0 to 10.0.1, and 11.0.0.alpha0 to 11.0.1, CPU usage can reach 100% upon receiving a large invalid TLS frame.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-28165","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 | cve high detected in jetty io jar cve high severity vulnerability vulnerable library jetty io jar the eclipse jetty project library home page a href path to dependency file concord docker images agent pom xml path to vulnerable library tmp ws ua sknjzt downloadresource pwlldd jetty io jar dependency hierarchy concord queue client snapshot jar root library jetty client jar x jetty io jar vulnerable library vulnerability details in eclipse jetty to to and to cpu usage can reach upon receiving a large invalid tls frame 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 org eclipse jetty jetty io org eclipse jetty jetty io org eclipse jetty jetty io isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree com walmartlabs concord server concord queue client snapshot org eclipse jetty jetty client org eclipse jetty jetty io isminimumfixversionavailable true minimumfixversion org eclipse jetty jetty io org eclipse jetty jetty io org eclipse jetty jetty io basebranches vulnerabilityidentifier cve vulnerabilitydetails in eclipse jetty to to and to cpu usage can reach upon receiving a large invalid tls frame vulnerabilityurl | 0 |
137,769 | 20,237,103,558 | IssuesEvent | 2022-02-14 04:07:37 | HICC-Bootcamp/2022-1-Happiness-Moneybox | https://api.github.com/repos/HICC-Bootcamp/2022-1-Happiness-Moneybox | closed | [์ค๊ณ] DB ์ค๊ณ | design | ์๋น์ค์ ์๊ตฌ์ฌํญ์ ๋ง๊ฒ DB๋ฅผ ์ค๊ณํด๋ณด์.
## ์์ธ
- ์ด๋ค DBMS๋ฅผ ์ฌ์ฉํ ๊ฒ์ด๋์ ๋ฐ๋ผ ์ค๊ณ๋ฐฉ์์ด ์กฐ๊ธ ๋ค๋ฆ
๋๋ค๋ง, RDB ๋ฐฉ์์ ๋ฐ๋ผ๊ฐ๋ ๋ฌธ์ ๋ ์์ต๋๋ค.
- RDB๋ฅผ ์ฌ์ฉํ๋ค๋ฉด ํ๋ก ํ
์ด๋ธ ๊ตฌ์กฐ๋ฅผ ๊ทธ๋ฆฌ๊ณ , ๊ฐ ์นผ๋ผ ์ด๋ฆ๊ณผ ๋ฐ์ดํฐ ํ์
, ์ ์ฝ, ํ
์ด๋ธ ๊ฐ์ ๊ด๊ณ๋ฅผ ์์ฑํ๋ฉด ๋๊ณ ,
- NoSQL์ ์ฌ์ฉํ๋ค๋ฉด ๊ธฐ๋ฅ ์๊ตฌ์ฌํญ์ ๋ฐ๋ผ ๋ํ๋จผํธ์ ์ปฌ๋ ์
์ ์ค๊ณํ๋ฉด ๋ฉ๋๋ค.
- NoSQL์ด๋ผ๊ณ ํน๋ณํ ๋ค๋ฅด๊ฒ ์ค๊ณํด์ผํ๋ ๊ฒ์ ์๋๋, ERD๋ฅผ ์ฌ์ฉํด ์ค๊ณํด๋ ์๊ด์์ต๋๋ค.
- ์ค์ํ ๊ฒ์ ๊ฐ๋ฐํ ๋ ๋ฐ์ดํฐ๋ฅผ ์ด๋ป๊ฒ ์ ์ฅํ ๊ฒ์ธ์ง๋ฅผ ๋ฏธ๋ฆฌ ์ ํด๋๊ณ ๋ค์ด๊ฐ๋ ๊ฒ์
๋๋ค.
[์ข์ ๊ธ](https://meetup.toast.com/posts/276)์ด ์์ด์ ํ๋ ์ฒจ๋ถํฉ๋๋ค. ์ฐธ๊ณ ํ์ธ์~ :) (๋ด์ฉ์ด ์ด๋ ต๋ค๋ฉด ๊ทธ๋ฅ ๋ง๋ ๋ฐฉ์์ผ๋ก ์ค๊ณํด๋ ๋ฉ๋๋ค.)
## ๋ฐฉ๋ฒ
Wiki ํ์ด์ง์ 'DB ์ค๊ณ' ํ์ด์ง ์์ฑํด์ ์์ฑํ ๋ค ๋ณธ ์ด์์ ์ฝ๋ฉํธ๋ก ๋งํฌ ๋ฌ๋ฉด ๋ฉ๋๋ค. | 1.0 | [์ค๊ณ] DB ์ค๊ณ - ์๋น์ค์ ์๊ตฌ์ฌํญ์ ๋ง๊ฒ DB๋ฅผ ์ค๊ณํด๋ณด์.
## ์์ธ
- ์ด๋ค DBMS๋ฅผ ์ฌ์ฉํ ๊ฒ์ด๋์ ๋ฐ๋ผ ์ค๊ณ๋ฐฉ์์ด ์กฐ๊ธ ๋ค๋ฆ
๋๋ค๋ง, RDB ๋ฐฉ์์ ๋ฐ๋ผ๊ฐ๋ ๋ฌธ์ ๋ ์์ต๋๋ค.
- RDB๋ฅผ ์ฌ์ฉํ๋ค๋ฉด ํ๋ก ํ
์ด๋ธ ๊ตฌ์กฐ๋ฅผ ๊ทธ๋ฆฌ๊ณ , ๊ฐ ์นผ๋ผ ์ด๋ฆ๊ณผ ๋ฐ์ดํฐ ํ์
, ์ ์ฝ, ํ
์ด๋ธ ๊ฐ์ ๊ด๊ณ๋ฅผ ์์ฑํ๋ฉด ๋๊ณ ,
- NoSQL์ ์ฌ์ฉํ๋ค๋ฉด ๊ธฐ๋ฅ ์๊ตฌ์ฌํญ์ ๋ฐ๋ผ ๋ํ๋จผํธ์ ์ปฌ๋ ์
์ ์ค๊ณํ๋ฉด ๋ฉ๋๋ค.
- NoSQL์ด๋ผ๊ณ ํน๋ณํ ๋ค๋ฅด๊ฒ ์ค๊ณํด์ผํ๋ ๊ฒ์ ์๋๋, ERD๋ฅผ ์ฌ์ฉํด ์ค๊ณํด๋ ์๊ด์์ต๋๋ค.
- ์ค์ํ ๊ฒ์ ๊ฐ๋ฐํ ๋ ๋ฐ์ดํฐ๋ฅผ ์ด๋ป๊ฒ ์ ์ฅํ ๊ฒ์ธ์ง๋ฅผ ๋ฏธ๋ฆฌ ์ ํด๋๊ณ ๋ค์ด๊ฐ๋ ๊ฒ์
๋๋ค.
[์ข์ ๊ธ](https://meetup.toast.com/posts/276)์ด ์์ด์ ํ๋ ์ฒจ๋ถํฉ๋๋ค. ์ฐธ๊ณ ํ์ธ์~ :) (๋ด์ฉ์ด ์ด๋ ต๋ค๋ฉด ๊ทธ๋ฅ ๋ง๋ ๋ฐฉ์์ผ๋ก ์ค๊ณํด๋ ๋ฉ๋๋ค.)
## ๋ฐฉ๋ฒ
Wiki ํ์ด์ง์ 'DB ์ค๊ณ' ํ์ด์ง ์์ฑํด์ ์์ฑํ ๋ค ๋ณธ ์ด์์ ์ฝ๋ฉํธ๋ก ๋งํฌ ๋ฌ๋ฉด ๋ฉ๋๋ค. | non_test | db ์ค๊ณ ์๋น์ค์ ์๊ตฌ์ฌํญ์ ๋ง๊ฒ db๋ฅผ ์ค๊ณํด๋ณด์ ์์ธ ์ด๋ค dbms๋ฅผ ์ฌ์ฉํ ๊ฒ์ด๋์ ๋ฐ๋ผ ์ค๊ณ๋ฐฉ์์ด ์กฐ๊ธ ๋ค๋ฆ
๋๋ค๋ง rdb ๋ฐฉ์์ ๋ฐ๋ผ๊ฐ๋ ๋ฌธ์ ๋ ์์ต๋๋ค rdb๋ฅผ ์ฌ์ฉํ๋ค๋ฉด ํ๋ก ํ
์ด๋ธ ๊ตฌ์กฐ๋ฅผ ๊ทธ๋ฆฌ๊ณ ๊ฐ ์นผ๋ผ ์ด๋ฆ๊ณผ ๋ฐ์ดํฐ ํ์
์ ์ฝ ํ
์ด๋ธ ๊ฐ์ ๊ด๊ณ๋ฅผ ์์ฑํ๋ฉด ๋๊ณ nosql์ ์ฌ์ฉํ๋ค๋ฉด ๊ธฐ๋ฅ ์๊ตฌ์ฌํญ์ ๋ฐ๋ผ ๋ํ๋จผํธ์ ์ปฌ๋ ์
์ ์ค๊ณํ๋ฉด ๋ฉ๋๋ค nosql์ด๋ผ๊ณ ํน๋ณํ ๋ค๋ฅด๊ฒ ์ค๊ณํด์ผํ๋ ๊ฒ์ ์๋๋ erd๋ฅผ ์ฌ์ฉํด ์ค๊ณํด๋ ์๊ด์์ต๋๋ค ์ค์ํ ๊ฒ์ ๊ฐ๋ฐํ ๋ ๋ฐ์ดํฐ๋ฅผ ์ด๋ป๊ฒ ์ ์ฅํ ๊ฒ์ธ์ง๋ฅผ ๋ฏธ๋ฆฌ ์ ํด๋๊ณ ๋ค์ด๊ฐ๋ ๊ฒ์
๋๋ค ์์ด์ ํ๋ ์ฒจ๋ถํฉ๋๋ค ์ฐธ๊ณ ํ์ธ์ ๋ด์ฉ์ด ์ด๋ ต๋ค๋ฉด ๊ทธ๋ฅ ๋ง๋ ๋ฐฉ์์ผ๋ก ์ค๊ณํด๋ ๋ฉ๋๋ค ๋ฐฉ๋ฒ wiki ํ์ด์ง์ db ์ค๊ณ ํ์ด์ง ์์ฑํด์ ์์ฑํ ๋ค ๋ณธ ์ด์์ ์ฝ๋ฉํธ๋ก ๋งํฌ ๋ฌ๋ฉด ๋ฉ๋๋ค | 0 |
254,798 | 21,877,602,471 | IssuesEvent | 2022-05-19 11:40:13 | googleapis/python-spanner-django | https://api.github.com/repos/googleapis/python-spanner-django | closed | django: Meta.order_with_respect_to column name is incompatible with Spanner | django-test-suite priority: p2 api: spanner | Tried running contenttypes_tests and it failed with
```shell
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/google/api_core/future/polling.py", line 127, in result
raise self._exception
google.api_core.exceptions.GoogleAPICallError: None Column name not valid: contenttypes_tests_answer._order.
```
where the generated SQL look like this
```sql
CREATE TABLE contenttypes_tests_answer (
id INT64 NOT NULL,
text STRING(200) NOT NULL,
content_type_id INT64 NOT NULL,
object_id INT64 NOT NULL,
_order INT64 NOT NULL
) PRIMARY KEY(id)
```
even trying backticks on the column name doesn't fix the problem `_order`, per
and then without the backticks
Over all this is a broader issue of spanner not supporting column names starting with special characters. | 1.0 | django: Meta.order_with_respect_to column name is incompatible with Spanner - Tried running contenttypes_tests and it failed with
```shell
File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/google/api_core/future/polling.py", line 127, in result
raise self._exception
google.api_core.exceptions.GoogleAPICallError: None Column name not valid: contenttypes_tests_answer._order.
```
where the generated SQL look like this
```sql
CREATE TABLE contenttypes_tests_answer (
id INT64 NOT NULL,
text STRING(200) NOT NULL,
content_type_id INT64 NOT NULL,
object_id INT64 NOT NULL,
_order INT64 NOT NULL
) PRIMARY KEY(id)
```
even trying backticks on the column name doesn't fix the problem `_order`, per
and then without the backticks
Over all this is a broader issue of spanner not supporting column names starting with special characters. | test | django meta order with respect to column name is incompatible with spanner tried running contenttypes tests and it failed with shell file library frameworks python framework versions lib site packages google api core future polling py line in result raise self exception google api core exceptions googleapicallerror none column name not valid contenttypes tests answer order where the generated sql look like this sql create table contenttypes tests answer id not null text string not null content type id not null object id not null order not null primary key id even trying backticks on the column name doesn t fix the problem order per and then without the backticks over all this is a broader issue of spanner not supporting column names starting with special characters | 1 |
51,484 | 21,689,235,996 | IssuesEvent | 2022-05-09 14:02:56 | hashicorp/terraform-provider-aws | https://api.github.com/repos/hashicorp/terraform-provider-aws | closed | Allow time for propagation of new IAM resources on KMS policy update | bug service/iam service/kms | ### Community Note
* Please vote on this issue by adding a ๐ [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
### Terraform CLI and Terraform AWS Provider Version
Terraform v1.1.5
Provider v4.14.0 (HEAD: cffbd38)
### Affected Resource(s)
* `aws_kms_key`
### Terraform Configuration Files
Given the distributed nature of AWS, IAM changes take time to propagate. During the creation of KMS keys and their resource policies, a `MalformedPolicyDocumentException` indicates that IAM changes might not have propagated, and this is handled by the provider, which retries for up to two minutes.
However, when updating the resource policy of an already existing key, the provider fails to handle the same error.
```hcl
data "aws_caller_identity" "this" {}
#resource "aws_iam_role" "example_role" {
# name = "example_role"
# assume_role_policy = data.aws_iam_policy_document.assume_example_role.json
#}
#data "aws_iam_policy_document" "assume_example_role" {
# statement {
# actions = ["sts:AssumeRole"]
# principals {
# type = "AWS"
# identifiers = [data.aws_caller_identity.this.arn]
# }
# }
#}
resource "aws_kms_key" "example_key" {
policy = data.aws_iam_policy_document.example_key_policy.json
}
data "aws_iam_policy_document" "example_key_policy" {
# statement {
# sid = "Decrypt"
# effect = "Allow"
# principals {
# type = "AWS"
# identifiers = [aws_iam_role.example_role.arn]
# }
# actions = [
# "kms:Decrypt",
# ]
# resources = ["*"]
# }
statement {
sid = "Administrate"
effect = "Allow"
principals {
type = "AWS"
identifiers = [data.aws_caller_identity.this.arn]
}
actions = [
"kms:*"
]
resources = ["*"]
}
}
```
### Debug Output
```
2022-05-08T18:53:33.578+0100 [ERROR] vertex "aws_kms_key.example_key" error: error updating KMS Key (xxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) policy: MalformedPolicyDocumentException: Policy contains a statement with one or more invalid principals.
|
โ Error: error updating KMS Key (xxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) policy: MalformedPolicyDocumentException: Policy contains a statement with one or more invalid principals.
โ
โ with aws_kms_key.example_key,
โ on kms_update_wait_iam.tf line 18, in resource "aws_kms_key" "example_key":
โ 18: resource "aws_kms_key" "example_key" {
โ
```
### Expected Behavior
As with key creation, the provider should retry the key update until the timeout allowed for IAM propagation (two minutes) is reached.
### Actual Behavior
The provider doesn't retry, instead failing on the first `MalformedPolicyDocumentException`.
### Steps to Reproduce
1. `terraform apply` the Terraform configuration from above to create a KMS key
2. Uncomment the commented lines and `terraform apply` again to create a new IAM role and reference it in the policy
### References
* #7646
| 2.0 | Allow time for propagation of new IAM resources on KMS policy update - ### Community Note
* Please vote on this issue by adding a ๐ [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
### Terraform CLI and Terraform AWS Provider Version
Terraform v1.1.5
Provider v4.14.0 (HEAD: cffbd38)
### Affected Resource(s)
* `aws_kms_key`
### Terraform Configuration Files
Given the distributed nature of AWS, IAM changes take time to propagate. During the creation of KMS keys and their resource policies, a `MalformedPolicyDocumentException` indicates that IAM changes might not have propagated, and this is handled by the provider, which retries for up to two minutes.
However, when updating the resource policy of an already existing key, the provider fails to handle the same error.
```hcl
data "aws_caller_identity" "this" {}
#resource "aws_iam_role" "example_role" {
# name = "example_role"
# assume_role_policy = data.aws_iam_policy_document.assume_example_role.json
#}
#data "aws_iam_policy_document" "assume_example_role" {
# statement {
# actions = ["sts:AssumeRole"]
# principals {
# type = "AWS"
# identifiers = [data.aws_caller_identity.this.arn]
# }
# }
#}
resource "aws_kms_key" "example_key" {
policy = data.aws_iam_policy_document.example_key_policy.json
}
data "aws_iam_policy_document" "example_key_policy" {
# statement {
# sid = "Decrypt"
# effect = "Allow"
# principals {
# type = "AWS"
# identifiers = [aws_iam_role.example_role.arn]
# }
# actions = [
# "kms:Decrypt",
# ]
# resources = ["*"]
# }
statement {
sid = "Administrate"
effect = "Allow"
principals {
type = "AWS"
identifiers = [data.aws_caller_identity.this.arn]
}
actions = [
"kms:*"
]
resources = ["*"]
}
}
```
### Debug Output
```
2022-05-08T18:53:33.578+0100 [ERROR] vertex "aws_kms_key.example_key" error: error updating KMS Key (xxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) policy: MalformedPolicyDocumentException: Policy contains a statement with one or more invalid principals.
|
โ Error: error updating KMS Key (xxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) policy: MalformedPolicyDocumentException: Policy contains a statement with one or more invalid principals.
โ
โ with aws_kms_key.example_key,
โ on kms_update_wait_iam.tf line 18, in resource "aws_kms_key" "example_key":
โ 18: resource "aws_kms_key" "example_key" {
โ
```
### Expected Behavior
As with key creation, the provider should retry the key update until the timeout allowed for IAM propagation (two minutes) is reached.
### Actual Behavior
The provider doesn't retry, instead failing on the first `MalformedPolicyDocumentException`.
### Steps to Reproduce
1. `terraform apply` the Terraform configuration from above to create a KMS key
2. Uncomment the commented lines and `terraform apply` again to create a new IAM role and reference it in the policy
### References
* #7646
| non_test | allow time for propagation of new iam resources on kms policy update community note please vote on this issue by adding a ๐ to the original issue to help the community and maintainers prioritize this request please do not leave or other comments that do not add relevant new information or questions they generate extra noise for issue followers and do not help prioritize the request if you are interested in working on this issue or have submitted a pull request please leave a comment terraform cli and terraform aws provider version terraform provider head affected resource s aws kms key terraform configuration files given the distributed nature of aws iam changes take time to propagate during the creation of kms keys and their resource policies a malformedpolicydocumentexception indicates that iam changes might not have propagated and this is handled by the provider which retries for up to two minutes however when updating the resource policy of an already existing key the provider fails to handle the same error hcl data aws caller identity this resource aws iam role example role name example role assume role policy data aws iam policy document assume example role json data aws iam policy document assume example role statement actions principals type aws identifiers resource aws kms key example key policy data aws iam policy document example key policy json data aws iam policy document example key policy statement sid decrypt effect allow principals type aws identifiers actions kms decrypt resources statement sid administrate effect allow principals type aws identifiers actions kms resources debug output vertex aws kms key example key error error updating kms key xxxx xxxx xxxx xxxx xxxxxxxxxxxx policy malformedpolicydocumentexception policy contains a statement with one or more invalid principals โ error error updating kms key xxxx xxxx xxxx xxxx xxxxxxxxxxxx policy malformedpolicydocumentexception policy contains a statement with one or more invalid principals โ โ with aws kms key example key โ on kms update wait iam tf line in resource aws kms key example key โ resource aws kms key example key โ expected behavior as with key creation the provider should retry the key update until the timeout allowed for iam propagation two minutes is reached actual behavior the provider doesn t retry instead failing on the first malformedpolicydocumentexception steps to reproduce terraform apply the terraform configuration from above to create a kms key uncomment the commented lines and terraform apply again to create a new iam role and reference it in the policy references | 0 |
70,522 | 23,217,700,147 | IssuesEvent | 2022-08-02 15:19:25 | primefaces/primereact | https://api.github.com/repos/primefaces/primereact | opened | DataTable: onRowToggle event returns the wrong type for the data property | defect :bangbang: needs-triage | ### Describe the bug
When clicking the row expand button, the `onRowToggle` event will log an object of the type `Record<any, boolean>`, where the keys are the `dataKey`s of the toggled rows, and the value is a boolean that says whether the rows are toggled or not when it should log an array of data keys like the [typed value suggests](https://github.com/primefaces/primereact/blob/5e60927bf91e967ff2e653a2a0d673b1214558b9/components/lib/datatable/DataTable.d.ts#L90).
By the way, it only ever shows the ids of the rows that are toggled, so the value is always `true`, hence the suggestion. As the expected type in the d.ts would make most implementations easier without the need to use the `Object.keys()` method which is usually what most people want, the keys of the toggled values.
### Reproducer
https://codesandbox.io/s/epic-sunset-xmuhit?file=/src/demo/DataTableRowExpansionDemo.tsx
### PrimeReact version
8.3.0
### React version
18.x
### Language
TypeScript
### Build / Runtime
Create React App (CRA)
### Browser(s)
Chrome 103.0.5060.134
### Steps to reproduce the behavior
1. Click the row expand button.
2. The console will log an object of the type Record<string | number, boolean>, where the keys are the dataKeys of the toggled rows, and the value is a boolean that says whether the rows are toggled or not. The problem is that it only ever shows the ids of the rows that are toggled, so the value is always true.
So it doesn't even make sense to have an object for that. **A list containing the data keys of the toggled rows makes more sense.**
### Expected behavior
The console will log an object of the type **`Array` containing the data keys of the toggled rows makes more sense.** Which could be the `any[]` that the type [`DataTableRowToggleParams`](https://github.com/primefaces/primereact/blob/5e60927bf91e967ff2e653a2a0d673b1214558b9/components/lib/datatable/DataTable.d.ts#L90) already specifies for the `data` parameter.
| 1.0 | DataTable: onRowToggle event returns the wrong type for the data property - ### Describe the bug
When clicking the row expand button, the `onRowToggle` event will log an object of the type `Record<any, boolean>`, where the keys are the `dataKey`s of the toggled rows, and the value is a boolean that says whether the rows are toggled or not when it should log an array of data keys like the [typed value suggests](https://github.com/primefaces/primereact/blob/5e60927bf91e967ff2e653a2a0d673b1214558b9/components/lib/datatable/DataTable.d.ts#L90).
By the way, it only ever shows the ids of the rows that are toggled, so the value is always `true`, hence the suggestion. As the expected type in the d.ts would make most implementations easier without the need to use the `Object.keys()` method which is usually what most people want, the keys of the toggled values.
### Reproducer
https://codesandbox.io/s/epic-sunset-xmuhit?file=/src/demo/DataTableRowExpansionDemo.tsx
### PrimeReact version
8.3.0
### React version
18.x
### Language
TypeScript
### Build / Runtime
Create React App (CRA)
### Browser(s)
Chrome 103.0.5060.134
### Steps to reproduce the behavior
1. Click the row expand button.
2. The console will log an object of the type Record<string | number, boolean>, where the keys are the dataKeys of the toggled rows, and the value is a boolean that says whether the rows are toggled or not. The problem is that it only ever shows the ids of the rows that are toggled, so the value is always true.
So it doesn't even make sense to have an object for that. **A list containing the data keys of the toggled rows makes more sense.**
### Expected behavior
The console will log an object of the type **`Array` containing the data keys of the toggled rows makes more sense.** Which could be the `any[]` that the type [`DataTableRowToggleParams`](https://github.com/primefaces/primereact/blob/5e60927bf91e967ff2e653a2a0d673b1214558b9/components/lib/datatable/DataTable.d.ts#L90) already specifies for the `data` parameter.
| non_test | datatable onrowtoggle event returns the wrong type for the data property describe the bug when clicking the row expand button the onrowtoggle event will log an object of the type record where the keys are the datakey s of the toggled rows and the value is a boolean that says whether the rows are toggled or not when it should log an array of data keys like the by the way it only ever shows the ids of the rows that are toggled so the value is always true hence the suggestion as the expected type in the d ts would make most implementations easier without the need to use the object keys method which is usually what most people want the keys of the toggled values reproducer primereact version react version x language typescript build runtime create react app cra browser s chrome steps to reproduce the behavior click the row expand button the console will log an object of the type record where the keys are the datakeys of the toggled rows and the value is a boolean that says whether the rows are toggled or not the problem is that it only ever shows the ids of the rows that are toggled so the value is always true so it doesn t even make sense to have an object for that a list containing the data keys of the toggled rows makes more sense expected behavior the console will log an object of the type array containing the data keys of the toggled rows makes more sense which could be the any that the type already specifies for the data parameter | 0 |
318,722 | 23,737,287,102 | IssuesEvent | 2022-08-31 09:13:13 | coppolaemilio/dialogic | https://api.github.com/repos/coppolaemilio/dialogic | closed | Documentation links are all broken | Bug ๐ Documentation ๐ Noob Friendly ๐ | ## The problem
**Describe the bug**
The links in the README and in the wiki don't go to any useful pages
**To Reproduce**
Steps to reproduce the behavior:
1. Go to 'https://godotengine.org/asset-library/asset/833'
2. Download the package
3. Unzip the package
4. Notice the README.md
5. Open the README
6. Observe a link to https://github.com/coppolaemilio/dialogic/blob/main/addons/dialogic/Documentation/Content/Tutorials/BeginnersGuideStepByStep.md
7. Click on that link
8. Observe a 404
***Alternate repro steps***
1. Go to the project wiki https://github.com/coppolaemilio/dialogic/wiki
2. Scroll down to the Tutorials
3. Notice Beginner's Guide
4. Click on the link https://github.com/coppolaemilio/dialogic/wiki/Tutorials/BeginnersGuideStepByStep.md
5. Observe that there's no page at that address so GitHup asks me to write the beginner's step-by-step guide?
**Expected behavior**
I expect that the links you provide in your README and your wiki will lead to pages that exist
**Screenshots**
N/A just click the above links and observe the issues
**System (please complete the following information):**
- OS: Windows
- Godot Version: 3.5
- Dialogic Version: 1.4.5
## Solutions
**Workaround**
Idk??? I tried going to the wiki when the link in the README didn't work but was not able to find the documentation I needed. i guess I could scour the wiki and hope that I stumble upon the right page?
**Possible fixes**
You should either update the links to point to documentation pages that exist, or write documentation pages and put them in the place of the links
| 1.0 | Documentation links are all broken - ## The problem
**Describe the bug**
The links in the README and in the wiki don't go to any useful pages
**To Reproduce**
Steps to reproduce the behavior:
1. Go to 'https://godotengine.org/asset-library/asset/833'
2. Download the package
3. Unzip the package
4. Notice the README.md
5. Open the README
6. Observe a link to https://github.com/coppolaemilio/dialogic/blob/main/addons/dialogic/Documentation/Content/Tutorials/BeginnersGuideStepByStep.md
7. Click on that link
8. Observe a 404
***Alternate repro steps***
1. Go to the project wiki https://github.com/coppolaemilio/dialogic/wiki
2. Scroll down to the Tutorials
3. Notice Beginner's Guide
4. Click on the link https://github.com/coppolaemilio/dialogic/wiki/Tutorials/BeginnersGuideStepByStep.md
5. Observe that there's no page at that address so GitHup asks me to write the beginner's step-by-step guide?
**Expected behavior**
I expect that the links you provide in your README and your wiki will lead to pages that exist
**Screenshots**
N/A just click the above links and observe the issues
**System (please complete the following information):**
- OS: Windows
- Godot Version: 3.5
- Dialogic Version: 1.4.5
## Solutions
**Workaround**
Idk??? I tried going to the wiki when the link in the README didn't work but was not able to find the documentation I needed. i guess I could scour the wiki and hope that I stumble upon the right page?
**Possible fixes**
You should either update the links to point to documentation pages that exist, or write documentation pages and put them in the place of the links
| non_test | documentation links are all broken the problem describe the bug the links in the readme and in the wiki don t go to any useful pages to reproduce steps to reproduce the behavior go to download the package unzip the package notice the readme md open the readme observe a link to click on that link observe a alternate repro steps go to the project wiki scroll down to the tutorials notice beginner s guide click on the link observe that there s no page at that address so githup asks me to write the beginner s step by step guide expected behavior i expect that the links you provide in your readme and your wiki will lead to pages that exist screenshots n a just click the above links and observe the issues system please complete the following information os windows godot version dialogic version solutions workaround idk i tried going to the wiki when the link in the readme didn t work but was not able to find the documentation i needed i guess i could scour the wiki and hope that i stumble upon the right page possible fixes you should either update the links to point to documentation pages that exist or write documentation pages and put them in the place of the links | 0 |
324,237 | 27,790,782,013 | IssuesEvent | 2023-03-17 08:46:25 | wazuh/wazuh | https://api.github.com/repos/wazuh/wazuh | opened | Release 4.4.0 - RC 2 - WPK upgrade tests | module/upgrade/wpk type/test/manual team/core/watchdogs release test/4.4.0 | The following issue aims to run `upgrade WPK tests` for the current release candidate, report the results, and open new issues for any encountered errors.
## WPK upgrade tests information
|Main RC issue|Version|Release candidate|Tag|Previous issue|
|---|---|---|---|---|
|https://github.com/wazuh/wazuh/issues/16390|4.4.0|RC 2|[v4.4.0-rc2](https://github.com/wazuh/wazuh/tree/v4.4.0-rc2)| https://github.com/wazuh/wazuh/issues/16132|
## Test report procedure
All individual test checks must be marked as:
| | |
|---------------------------------|--------------------------------------------|
| Pass | The test ran successfully. |
| Xfail | The test was expected to fail, and it failed. It must be properly justified and reported in an issue. |
| Skip | The test was not run. It must be properly justified and reported in an issue. |
| Fail | The test failed. A new issue must be opened to evaluate and address the problem. |
All test results must have one of the following statuses:
| | |
|---------------------------------|--------------------------------------------|
| :green_circle: | All checks passed. |
| :red_circle: | There is at least one failed check result. |
| :yellow_circle: | There is at least one expected failure or skipped test and no failures. |
Any failing test must be properly addressed with a new issue, detailing the error and the possible cause. It must be included in the `Fixes` section of the current release candidate's main issue.
Any expected fail or skipped test must have an issue justifying the reason. All auditors must validate the justification for an expected fail or skipped test.
An extended report of the test results must be attached as a ZIP or TXT file. This report can be used by the auditors to dig deeper into any possible failures and details.
## Tests
To evaluate this feature, it is necessary to test upgrading the agent and also the case when the upgrade fails (rollback). The `tree` command will be used to compare, before and after the upgrade/rollback process, and check that the presence, ownership, and permissions of the files and directories are expected.
Wazuh versions to test (Upgrade to the current agent version):
|OS|Version|Status|Upgrade fail|Upgrade OK|Comments
|----|-----|------|---------------|------------------|---------------|
|Ubuntu 22|4.3.10| โช Skipped | | | |
|Windows Server 2022|4.3.10| โช Skipped | | | |
## Findings
## Auditors' validation
The definition of done for this one is the validation of the conclusions and the test results from all auditors.
All checks from below must be accepted in order to close this issue.
- [ ] @chemamartinez
- [ ] @davidjiglesias | 2.0 | Release 4.4.0 - RC 2 - WPK upgrade tests - The following issue aims to run `upgrade WPK tests` for the current release candidate, report the results, and open new issues for any encountered errors.
## WPK upgrade tests information
|Main RC issue|Version|Release candidate|Tag|Previous issue|
|---|---|---|---|---|
|https://github.com/wazuh/wazuh/issues/16390|4.4.0|RC 2|[v4.4.0-rc2](https://github.com/wazuh/wazuh/tree/v4.4.0-rc2)| https://github.com/wazuh/wazuh/issues/16132|
## Test report procedure
All individual test checks must be marked as:
| | |
|---------------------------------|--------------------------------------------|
| Pass | The test ran successfully. |
| Xfail | The test was expected to fail, and it failed. It must be properly justified and reported in an issue. |
| Skip | The test was not run. It must be properly justified and reported in an issue. |
| Fail | The test failed. A new issue must be opened to evaluate and address the problem. |
All test results must have one of the following statuses:
| | |
|---------------------------------|--------------------------------------------|
| :green_circle: | All checks passed. |
| :red_circle: | There is at least one failed check result. |
| :yellow_circle: | There is at least one expected failure or skipped test and no failures. |
Any failing test must be properly addressed with a new issue, detailing the error and the possible cause. It must be included in the `Fixes` section of the current release candidate's main issue.
Any expected fail or skipped test must have an issue justifying the reason. All auditors must validate the justification for an expected fail or skipped test.
An extended report of the test results must be attached as a ZIP or TXT file. This report can be used by the auditors to dig deeper into any possible failures and details.
## Tests
To evaluate this feature, it is necessary to test upgrading the agent and also the case when the upgrade fails (rollback). The `tree` command will be used to compare, before and after the upgrade/rollback process, and check that the presence, ownership, and permissions of the files and directories are expected.
Wazuh versions to test (Upgrade to the current agent version):
|OS|Version|Status|Upgrade fail|Upgrade OK|Comments
|----|-----|------|---------------|------------------|---------------|
|Ubuntu 22|4.3.10| โช Skipped | | | |
|Windows Server 2022|4.3.10| โช Skipped | | | |
## Findings
## Auditors' validation
The definition of done for this one is the validation of the conclusions and the test results from all auditors.
All checks from below must be accepted in order to close this issue.
- [ ] @chemamartinez
- [ ] @davidjiglesias | test | release rc wpk upgrade tests the following issue aims to run upgrade wpk tests for the current release candidate report the results and open new issues for any encountered errors wpk upgrade tests information main rc issue version release candidate tag previous issue test report procedure all individual test checks must be marked as pass the test ran successfully xfail the test was expected to fail and it failed it must be properly justified and reported in an issue skip the test was not run it must be properly justified and reported in an issue fail the test failed a new issue must be opened to evaluate and address the problem all test results must have one of the following statuses green circle all checks passed red circle there is at least one failed check result yellow circle there is at least one expected failure or skipped test and no failures any failing test must be properly addressed with a new issue detailing the error and the possible cause it must be included in the fixes section of the current release candidate s main issue any expected fail or skipped test must have an issue justifying the reason all auditors must validate the justification for an expected fail or skipped test an extended report of the test results must be attached as a zip or txt file this report can be used by the auditors to dig deeper into any possible failures and details tests to evaluate this feature it is necessary to test upgrading the agent and also the case when the upgrade fails rollback the tree command will be used to compare before and after the upgrade rollback process and check that the presence ownership and permissions of the files and directories are expected wazuh versions to test upgrade to the current agent version os version status upgrade fail upgrade ok comments ubuntu โช skipped windows server โช skipped findings auditors validation the definition of done for this one is the validation of the conclusions and the test results from all auditors all checks from below must be accepted in order to close this issue chemamartinez davidjiglesias | 1 |
472,581 | 13,627,345,299 | IssuesEvent | 2020-09-24 12:28:25 | epiphany-platform/epiphany | https://api.github.com/repos/epiphany-platform/epiphany | closed | EKS cluster epiphany configuration | area/development area/kubernetes priority/important-soon provider/aws type/feature-request | Create EKS cluster configuration to be able to create it using epiphany.
**Is your feature request related to a problem? Please describe.**
We need to have possibility to create EKS cluster with epiphany.
**Describe the solution you'd like**
In previous tasks in order (#1442, #1443) terraform scripts should already be prepared. That means that here we want to develop yaml configs similar to what we have in epicli, inserting those previously prepared terraform scripts, embed it in epiphany environment to be able to create cluster with epiphany. This task is basically "do the thing" task. Previous ones are preparations.
**Describe alternatives you've considered**
This task has to consider what would be output from task #1462 as it will discuss modularisation in epiphany.
**Additional context**
No.
| 1.0 | EKS cluster epiphany configuration - Create EKS cluster configuration to be able to create it using epiphany.
**Is your feature request related to a problem? Please describe.**
We need to have possibility to create EKS cluster with epiphany.
**Describe the solution you'd like**
In previous tasks in order (#1442, #1443) terraform scripts should already be prepared. That means that here we want to develop yaml configs similar to what we have in epicli, inserting those previously prepared terraform scripts, embed it in epiphany environment to be able to create cluster with epiphany. This task is basically "do the thing" task. Previous ones are preparations.
**Describe alternatives you've considered**
This task has to consider what would be output from task #1462 as it will discuss modularisation in epiphany.
**Additional context**
No.
| non_test | eks cluster epiphany configuration create eks cluster configuration to be able to create it using epiphany is your feature request related to a problem please describe we need to have possibility to create eks cluster with epiphany describe the solution you d like in previous tasks in order terraform scripts should already be prepared that means that here we want to develop yaml configs similar to what we have in epicli inserting those previously prepared terraform scripts embed it in epiphany environment to be able to create cluster with epiphany this task is basically do the thing task previous ones are preparations describe alternatives you ve considered this task has to consider what would be output from task as it will discuss modularisation in epiphany additional context no | 0 |
831,748 | 32,059,998,681 | IssuesEvent | 2023-09-24 14:47:32 | AY2324S1-CS2103T-T14-2/tp | https://api.github.com/repos/AY2324S1-CS2103T-T14-2/tp | opened | View vitals of patients | type.Story priority.Low | As an ED doctor i can view real-time vitals of patients so that i can monitor patientโs condition efficiently. | 1.0 | View vitals of patients - As an ED doctor i can view real-time vitals of patients so that i can monitor patientโs condition efficiently. | non_test | view vitals of patients as an ed doctor i can view real time vitals of patients so that i can monitor patientโs condition efficiently | 0 |
10,916 | 13,691,292,357 | IssuesEvent | 2020-09-30 15:22:14 | prisma/prisma | https://api.github.com/repos/prisma/prisma | closed | When CLI and Client are not in sync, generate errors with TypeError: Cannot read property 'type' of undefined | bug/2-confirmed kind/bug process/candidate team/typescript topic: cli-generate | <!--
Thanks for helping us improve Prisma! ๐ Please follow the sections in the template and provide as much information as possible about your problem, e.g. by setting the `DEBUG="*"` environment variable and enabling additional logging output in Prisma Client.
Learn more about writing proper bug reports here: https://pris.ly/d/bug-reports
-->
## Bug description
When CLI and Client are not in sync, generate errors with
`TypeError: Cannot read property 'type' of undefined`
## How to reproduce
1. package.json
```
{
"name": "p2-dev",
"version": "1.0.0",
"main": "index.js",
"license": "MIT",
"devDependencies": {
"@prisma/cli": "2.8.0-dev.27",
"@prisma/client": "2.8.0-dev.9"
}
}
```
2. schema.prisma
```
datasource db {
provider = "postgresql"
url = "postgresql://this-will-not-be-used-but-overwritten-in-the-prisma-client-constructor"
}
generator client {
provider = "prisma-client-js"
}
model User {
email String @default("")
id String @id
name String @default("")
}
```
3. Run `yarn; yarn prisma generate`
4. Observe the error
```
divyendusingh [p2-dev]$ yarn; yarn prisma generate
yarn install v1.22.4
[1/4] ๐ Resolving packages...
success Already up-to-date.
โจ Done in 0.07s.
yarn run v1.22.4
$ /Users/divyendusingh/Documents/prisma/triage/p2-dev/node_modules/.bin/prisma generate
Prisma Schema loaded from schema.prisma
Error:
TypeError: Cannot read property 'type' of undefined
at /Users/divyendusingh/Documents/prisma/triage/p2-dev/node_modules/@prisma/client/generator-build/index.js:9439:45
at Array.map (<anonymous>)
at /Users/divyendusingh/Documents/prisma/triage/p2-dev/node_modules/@prisma/client/generator-build/index.js:9436:43
at Array.map (<anonymous>)
at transformInputTypes (/Users/divyendusingh/Documents/prisma/triage/p2-dev/node_modules/@prisma/client/generator-build/index.js:9424:61)
at transformDmmf (/Users/divyendusingh/Documents/prisma/triage/p2-dev/node_modules/@prisma/client/generator-build/index.js:9383:15)
at getPrismaClientDMMF (/Users/divyendusingh/Documents/prisma/triage/p2-dev/node_modules/@prisma/client/generator-build/index.js:9521:10)
at buildClient (/Users/divyendusingh/Documents/prisma/triage/p2-dev/node_modules/@prisma/client/generator-build/index.js:11092:21)
at generateClient (/Users/divyendusingh/Documents/prisma/triage/p2-dev/node_modules/@prisma/client/generator-build/index.js:11148:45)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
```
## Expected behavior
It should not crash
## Prisma information
```
yarn run v1.22.4
$ /Users/divyendusingh/Documents/prisma/triage/p2-dev/node_modules/.bin/prisma --version
@prisma/cli : 2.8.0-dev.27
Current platform : darwin
Query Engine : query-engine 7aef029819840cd88e6333b5037105264c82e2f4 (at node_modules/@prisma/cli/query-engine-darwin)
Migration Engine : migration-engine-cli 7aef029819840cd88e6333b5037105264c82e2f4 (at node_modules/@prisma/cli/migration-engine-darwin)
Introspection Engine : introspection-core 7aef029819840cd88e6333b5037105264c82e2f4 (at node_modules/@prisma/cli/introspection-engine-darwin)
Format Binary : prisma-fmt 7aef029819840cd88e6333b5037105264c82e2f4 (at node_modules/@prisma/cli/prisma-fmt-darwin)
Studio : 0.291.0
Done in 2.05s.
``` | 1.0 | When CLI and Client are not in sync, generate errors with TypeError: Cannot read property 'type' of undefined - <!--
Thanks for helping us improve Prisma! ๐ Please follow the sections in the template and provide as much information as possible about your problem, e.g. by setting the `DEBUG="*"` environment variable and enabling additional logging output in Prisma Client.
Learn more about writing proper bug reports here: https://pris.ly/d/bug-reports
-->
## Bug description
When CLI and Client are not in sync, generate errors with
`TypeError: Cannot read property 'type' of undefined`
## How to reproduce
1. package.json
```
{
"name": "p2-dev",
"version": "1.0.0",
"main": "index.js",
"license": "MIT",
"devDependencies": {
"@prisma/cli": "2.8.0-dev.27",
"@prisma/client": "2.8.0-dev.9"
}
}
```
2. schema.prisma
```
datasource db {
provider = "postgresql"
url = "postgresql://this-will-not-be-used-but-overwritten-in-the-prisma-client-constructor"
}
generator client {
provider = "prisma-client-js"
}
model User {
email String @default("")
id String @id
name String @default("")
}
```
3. Run `yarn; yarn prisma generate`
4. Observe the error
```
divyendusingh [p2-dev]$ yarn; yarn prisma generate
yarn install v1.22.4
[1/4] ๐ Resolving packages...
success Already up-to-date.
โจ Done in 0.07s.
yarn run v1.22.4
$ /Users/divyendusingh/Documents/prisma/triage/p2-dev/node_modules/.bin/prisma generate
Prisma Schema loaded from schema.prisma
Error:
TypeError: Cannot read property 'type' of undefined
at /Users/divyendusingh/Documents/prisma/triage/p2-dev/node_modules/@prisma/client/generator-build/index.js:9439:45
at Array.map (<anonymous>)
at /Users/divyendusingh/Documents/prisma/triage/p2-dev/node_modules/@prisma/client/generator-build/index.js:9436:43
at Array.map (<anonymous>)
at transformInputTypes (/Users/divyendusingh/Documents/prisma/triage/p2-dev/node_modules/@prisma/client/generator-build/index.js:9424:61)
at transformDmmf (/Users/divyendusingh/Documents/prisma/triage/p2-dev/node_modules/@prisma/client/generator-build/index.js:9383:15)
at getPrismaClientDMMF (/Users/divyendusingh/Documents/prisma/triage/p2-dev/node_modules/@prisma/client/generator-build/index.js:9521:10)
at buildClient (/Users/divyendusingh/Documents/prisma/triage/p2-dev/node_modules/@prisma/client/generator-build/index.js:11092:21)
at generateClient (/Users/divyendusingh/Documents/prisma/triage/p2-dev/node_modules/@prisma/client/generator-build/index.js:11148:45)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
```
## Expected behavior
It should not crash
## Prisma information
```
yarn run v1.22.4
$ /Users/divyendusingh/Documents/prisma/triage/p2-dev/node_modules/.bin/prisma --version
@prisma/cli : 2.8.0-dev.27
Current platform : darwin
Query Engine : query-engine 7aef029819840cd88e6333b5037105264c82e2f4 (at node_modules/@prisma/cli/query-engine-darwin)
Migration Engine : migration-engine-cli 7aef029819840cd88e6333b5037105264c82e2f4 (at node_modules/@prisma/cli/migration-engine-darwin)
Introspection Engine : introspection-core 7aef029819840cd88e6333b5037105264c82e2f4 (at node_modules/@prisma/cli/introspection-engine-darwin)
Format Binary : prisma-fmt 7aef029819840cd88e6333b5037105264c82e2f4 (at node_modules/@prisma/cli/prisma-fmt-darwin)
Studio : 0.291.0
Done in 2.05s.
``` | non_test | when cli and client are not in sync generate errors with typeerror cannot read property type of undefined thanks for helping us improve prisma ๐ please follow the sections in the template and provide as much information as possible about your problem e g by setting the debug environment variable and enabling additional logging output in prisma client learn more about writing proper bug reports here bug description when cli and client are not in sync generate errors with typeerror cannot read property type of undefined how to reproduce package json name dev version main index js license mit devdependencies prisma cli dev prisma client dev schema prisma datasource db provider postgresql url postgresql this will not be used but overwritten in the prisma client constructor generator client provider prisma client js model user email string default id string id name string default run yarn yarn prisma generate observe the error divyendusingh yarn yarn prisma generate yarn install ๐ resolving packages success already up to date โจ done in yarn run users divyendusingh documents prisma triage dev node modules bin prisma generate prisma schema loaded from schema prisma error typeerror cannot read property type of undefined at users divyendusingh documents prisma triage dev node modules prisma client generator build index js at array map at users divyendusingh documents prisma triage dev node modules prisma client generator build index js at array map at transforminputtypes users divyendusingh documents prisma triage dev node modules prisma client generator build index js at transformdmmf users divyendusingh documents prisma triage dev node modules prisma client generator build index js at getprismaclientdmmf users divyendusingh documents prisma triage dev node modules prisma client generator build index js at buildclient users divyendusingh documents prisma triage dev node modules prisma client generator build index js at generateclient users divyendusingh documents prisma triage dev node modules prisma client generator build index js at processticksandrejections internal process task queues js error command failed with exit code info visit for documentation about this command expected behavior it should not crash prisma information yarn run users divyendusingh documents prisma triage dev node modules bin prisma version prisma cli dev current platform darwin query engine query engine at node modules prisma cli query engine darwin migration engine migration engine cli at node modules prisma cli migration engine darwin introspection engine introspection core at node modules prisma cli introspection engine darwin format binary prisma fmt at node modules prisma cli prisma fmt darwin studio done in | 0 |
140,935 | 11,383,895,719 | IssuesEvent | 2020-01-29 07:33:35 | brave/brave-browser | https://api.github.com/repos/brave/brave-browser | closed | Moving of bookmark is not propagated to another device | QA/Test-Plan-Specified QA/Yes feature/sync regression release-notes/exclude | Found while testing: https://github.com/brave/brave-core/pull/4324
The issue is also randomly reproducible with more bookmarks. My bookmarks were all messed up. Sometimes moving of bookmarks works as expected.
Important: Reproducible on 1.5.x. Not reproducible on 1.2.x, 1.3.x.
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
1. Clean profile DeviceA and DeviceB
2. DeviceA: open `interia.pl`
3. DeviceA: open `youtube.com`
4. DeviceA: create sync chain and copy code words
5. DeviceB: enter code words
6. Wait for sync
7. DeviceA: bookmark `interia.pl`
8. DeviceA: bookmark `youtube.com`
9. Wait till bookmarks are synced to DeviceB
10. DeviceA:Move `interia.pl` after `youtube.com` bookmark
11. Wait till the change is propagated to DeviceB
DeviceA: Ubuntu 18.04LTS
DeviceB: Windows 7x64
## Actual result:
<!--Please add screenshots if needed-->
The moving of bookmark is not propagate to another device
DeviceA
DeviceB
## Expected result:
The moving of the bookmark is always propagated
## Reproduces how often:
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
100% repro rate with above STR
## 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-->
**Reproducible on**
Brave | 1.5.62 Chromium: 79.0.3945.130ย (Official Build)ย nightlyย (64-bit)
-- | --
Revision | e22de67c28798d98833a7137c0e22876237fc40a-refs/branch-heads/3945@{#1047}
OS | Windowsย 7 Service Pack 1 (Build 7601.24544)
Brave | 1.5.62 Chromium: 79.0.3945.130ย (Official Build)ย nightlyย (64-bit)
-- | --
Revision | e22de67c28798d98833a7137c0e22876237fc40a-refs/branch-heads/3945@{#1047}
OS | Ubuntu 18.04 LTS
**Not Reproducible on**
Brave | 1.2.43 Chromium: 79.0.3945.130ย (Official Build)ย (64-bit)
-- | --
Revision | e22de67c28798d98833a7137c0e22876237fc40a-refs/branch-heads/3945@{#1047}
OS | Ubuntu 18.04 LTS
Brave | 1.2.43 Chromium: 79.0.3945.130ย (Official Build)ย (64-bit)
-- | --
Revision | e22de67c28798d98833a7137c0e22876237fc40a-refs/branch-heads/3945@{#1047}
OS | Windowsย 7 Service Pack 1 (Build 7601.24544)
Brave | 1.3.102 Chromium: 79.0.3945.130ย (Official Build)ย betaย (64-bit)
-- | --
Revision | e22de67c28798d98833a7137c0e22876237fc40a-refs/branch-heads/3945@{#1047}
OS | Ubuntu 18.04 LTS
Brave | 1.3.102 Chromium: 79.0.3945.130ย (Official Build)ย betaย (64-bit)
-- | --
Revision | e22de67c28798d98833a7137c0e22876237fc40a-refs/branch-heads/3945@{#1047}
OS | Windowsย 7 Service Pack 1 (Build 7601.24544)
cc @brave/legacy_qa @jsecretan @AlexeyBarabash @darkdh @rebron | 1.0 | Moving of bookmark is not propagated to another device - Found while testing: https://github.com/brave/brave-core/pull/4324
The issue is also randomly reproducible with more bookmarks. My bookmarks were all messed up. Sometimes moving of bookmarks works as expected.
Important: Reproducible on 1.5.x. Not reproducible on 1.2.x, 1.3.x.
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
1. Clean profile DeviceA and DeviceB
2. DeviceA: open `interia.pl`
3. DeviceA: open `youtube.com`
4. DeviceA: create sync chain and copy code words
5. DeviceB: enter code words
6. Wait for sync
7. DeviceA: bookmark `interia.pl`
8. DeviceA: bookmark `youtube.com`
9. Wait till bookmarks are synced to DeviceB
10. DeviceA:Move `interia.pl` after `youtube.com` bookmark
11. Wait till the change is propagated to DeviceB
DeviceA: Ubuntu 18.04LTS
DeviceB: Windows 7x64
## Actual result:
<!--Please add screenshots if needed-->
The moving of bookmark is not propagate to another device
DeviceA
DeviceB
## Expected result:
The moving of the bookmark is always propagated
## Reproduces how often:
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
100% repro rate with above STR
## 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-->
**Reproducible on**
Brave | 1.5.62 Chromium: 79.0.3945.130ย (Official Build)ย nightlyย (64-bit)
-- | --
Revision | e22de67c28798d98833a7137c0e22876237fc40a-refs/branch-heads/3945@{#1047}
OS | Windowsย 7 Service Pack 1 (Build 7601.24544)
Brave | 1.5.62 Chromium: 79.0.3945.130ย (Official Build)ย nightlyย (64-bit)
-- | --
Revision | e22de67c28798d98833a7137c0e22876237fc40a-refs/branch-heads/3945@{#1047}
OS | Ubuntu 18.04 LTS
**Not Reproducible on**
Brave | 1.2.43 Chromium: 79.0.3945.130ย (Official Build)ย (64-bit)
-- | --
Revision | e22de67c28798d98833a7137c0e22876237fc40a-refs/branch-heads/3945@{#1047}
OS | Ubuntu 18.04 LTS
Brave | 1.2.43 Chromium: 79.0.3945.130ย (Official Build)ย (64-bit)
-- | --
Revision | e22de67c28798d98833a7137c0e22876237fc40a-refs/branch-heads/3945@{#1047}
OS | Windowsย 7 Service Pack 1 (Build 7601.24544)
Brave | 1.3.102 Chromium: 79.0.3945.130ย (Official Build)ย betaย (64-bit)
-- | --
Revision | e22de67c28798d98833a7137c0e22876237fc40a-refs/branch-heads/3945@{#1047}
OS | Ubuntu 18.04 LTS
Brave | 1.3.102 Chromium: 79.0.3945.130ย (Official Build)ย betaย (64-bit)
-- | --
Revision | e22de67c28798d98833a7137c0e22876237fc40a-refs/branch-heads/3945@{#1047}
OS | Windowsย 7 Service Pack 1 (Build 7601.24544)
cc @brave/legacy_qa @jsecretan @AlexeyBarabash @darkdh @rebron | test | moving of bookmark is not propagated to another device found while testing the issue is also randomly reproducible with more bookmarks my bookmarks were all messed up sometimes moving of bookmarks works as expected important reproducible on x not reproducible on x x steps to reproduce clean profile devicea and deviceb devicea open interia pl devicea open youtube com devicea create sync chain and copy code words deviceb enter code words wait for sync devicea bookmark interia pl devicea bookmark youtube com wait till bookmarks are synced to deviceb devicea move interia pl after youtube com bookmark wait till the change is propagated to deviceb devicea ubuntu deviceb windows actual result the moving of bookmark is not propagate to another device devicea deviceb expected result the moving of the bookmark is always propagated reproduces how often repro rate with above str brave version brave version info reproducible on brave chromium ย official build ย nightlyย bit revision refs branch heads os windowsย service pack build brave chromium ย official build ย nightlyย bit revision refs branch heads os ubuntu lts not reproducible on brave chromium ย official build ย bit revision refs branch heads os ubuntu lts brave chromium ย official build ย bit revision refs branch heads os windowsย service pack build brave chromium ย official build ย betaย bit revision refs branch heads os ubuntu lts brave chromium ย official build ย betaย bit revision refs branch heads os windowsย service pack build cc brave legacy qa jsecretan alexeybarabash darkdh rebron | 1 |
275,826 | 20,959,032,116 | IssuesEvent | 2022-03-27 14:19:08 | dbodanilo/Source-Code-Inspection | https://api.github.com/repos/dbodanilo/Source-Code-Inspection | closed | Documentaรงรฃo - Inconsistรชncia | documentation | O usuรกrio pode ter inserido uma nota de uma valor e preenchido o bloco de texto com outro valor. | 1.0 | Documentaรงรฃo - Inconsistรชncia - O usuรกrio pode ter inserido uma nota de uma valor e preenchido o bloco de texto com outro valor. | non_test | documentaรงรฃo inconsistรชncia o usuรกrio pode ter inserido uma nota de uma valor e preenchido o bloco de texto com outro valor | 0 |
148,737 | 11,863,199,205 | IssuesEvent | 2020-03-25 19:16:13 | MaelSemler/mini-cap | https://api.github.com/repos/MaelSemler/mini-cap | opened | Acceptance Test AT2-7 | Acceptance test | **Acceptance test:**
AT2-7
**Feature:**
FT2-7
**Feature description:**
As a user I want to see the time required to get to my destination.
**Acceptance criteria:**
Given that I am on the map page,
And I have put in my current location, and destination
I can click start and choose a transportation method,
I can choose from the suggested route,
Then i should see the estimated time of the chosen route
**Result:**
To be filled in by product owner upon evaluation.
**Date:**
To be filled in by product owner upon evaluation.
**Signature:**
To be filled in by product owner upon evaluation.
| 1.0 | Acceptance Test AT2-7 - **Acceptance test:**
AT2-7
**Feature:**
FT2-7
**Feature description:**
As a user I want to see the time required to get to my destination.
**Acceptance criteria:**
Given that I am on the map page,
And I have put in my current location, and destination
I can click start and choose a transportation method,
I can choose from the suggested route,
Then i should see the estimated time of the chosen route
**Result:**
To be filled in by product owner upon evaluation.
**Date:**
To be filled in by product owner upon evaluation.
**Signature:**
To be filled in by product owner upon evaluation.
| test | acceptance test acceptance test feature feature description as a user i want to see the time required to get to my destination acceptance criteria given that i am on the map page and i have put in my current location and destination i can click start and choose a transportation method i can choose from the suggested route then i should see the estimated time of the chosen route result to be filled in by product owner upon evaluation date to be filled in by product owner upon evaluation signature to be filled in by product owner upon evaluation | 1 |
399,509 | 11,756,286,291 | IssuesEvent | 2020-03-13 11:13:56 | lowRISC/opentitan | https://api.github.com/repos/lowRISC/opentitan | closed | [DV] Regression runs firing tb.dut.top_earlgrey.tl_adapter_ram_main.TlOutKnown_A | Component:DV Priority:P1 | Private CI is failing due to an assert firing.
<hr/>
**TEST:** chip_sanity, **SEED:** 3726260937<br>
**LOG:** $scratch_path/0.chip_sanity/out/run.log<br>
```
UVM_ERROR @ 8568613506 ps: (prim_assert.sv:18) [ASSERT FAILED] [tb.dut.top_earlgrey.tl_adapter_ram_main.TlOutKnown_A] TlOutKnown_A: !$isunknown(tl_o) (../src/lowrisc_tlul_adapter_sram_0.1/rtl/tlul_adapter_sram.sv:279)
```
<hr/>
A solution is most likely being worked on as part of https://github.com/lowRISC/opentitan/pull/1729.
CI [failed first](https://dev.azure.com/lowrisc/opentitan-private/_build?definitionId=8&_a=summary&repositoryFilter=7&branchFilter=2063) for https://github.com/lowRISC/opentitan/pull/1616, which is unrelated and had clean CI. I've filed https://github.com/lowRISC/opentitan/issues/1735 to hopefully address the underlying reason for the flaky test. | 1.0 | [DV] Regression runs firing tb.dut.top_earlgrey.tl_adapter_ram_main.TlOutKnown_A - Private CI is failing due to an assert firing.
<hr/>
**TEST:** chip_sanity, **SEED:** 3726260937<br>
**LOG:** $scratch_path/0.chip_sanity/out/run.log<br>
```
UVM_ERROR @ 8568613506 ps: (prim_assert.sv:18) [ASSERT FAILED] [tb.dut.top_earlgrey.tl_adapter_ram_main.TlOutKnown_A] TlOutKnown_A: !$isunknown(tl_o) (../src/lowrisc_tlul_adapter_sram_0.1/rtl/tlul_adapter_sram.sv:279)
```
<hr/>
A solution is most likely being worked on as part of https://github.com/lowRISC/opentitan/pull/1729.
CI [failed first](https://dev.azure.com/lowrisc/opentitan-private/_build?definitionId=8&_a=summary&repositoryFilter=7&branchFilter=2063) for https://github.com/lowRISC/opentitan/pull/1616, which is unrelated and had clean CI. I've filed https://github.com/lowRISC/opentitan/issues/1735 to hopefully address the underlying reason for the flaky test. | non_test | regression runs firing tb dut top earlgrey tl adapter ram main tloutknown a private ci is failing due to an assert firing test chip sanity seed log scratch path chip sanity out run log uvm error ps prim assert sv tloutknown a isunknown tl o src lowrisc tlul adapter sram rtl tlul adapter sram sv a solution is most likely being worked on as part of ci for which is unrelated and had clean ci i ve filed to hopefully address the underlying reason for the flaky test | 0 |
151,935 | 12,066,264,506 | IssuesEvent | 2020-04-16 11:26:45 | pywbem/pywbem | https://api.github.com/repos/pywbem/pywbem | closed | virtualenv setup failure during install test on Python 3.7 with minimum package levels | area: test resolution: fixed roll back/forward done type: bug | The Travis run on OS-X on Python 3.7.7 with minimum package levels fails when setting up the virtualenv for an install test (see https://travis-ci.org/github/pywbem/pywbem/jobs/674559955):
```
Testcase test1: Pip install from repo root directory: tests/installtest/../..
Saving current virtualenv: /Users/travis/venv
Creating virtualenv: tests/installtest/../../tmp_installtest/virtualenvs/pywbem_test_test1
..using this Python command: /Users/travis/venv/bin/python
Error: Command failed with rc=100: virtualenv -p /Users/travis/venv/bin/python tests/installtest/../../tmp_installtest/virtualenvs/pywbem_test_test1, output follows:
/Users/travis/venv/lib/python3.7/site-packages/virtualenv.py:991: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
import imp
Using base prefix '/usr/local/opt/python/bin/../Frameworks/Python.framework/Versions/3.7'
New python executable in /Users/travis/build/pywbem/pywbem/tmp_installtest/virtualenvs/pywbem_test_test1/bin/python
ERROR: The executable /Users/travis/build/pywbem/pywbem/tmp_installtest/virtualenvs/pywbem_test_test1/bin/python is not functioning
ERROR: It thinks sys.prefix is '/usr/local/Cellar/python/3.7.7/Frameworks/Python.framework/Versions/3.7' (should be '/Users/travis/build/pywbem/pywbem/tmp_installtest/virtualenvs/pywbem_test_test1')
ERROR: virtualenv is not compatible with this system or executable
Running virtualenv with interpreter /Users/travis/venv/bin/python
make: *** [installtest] Error 1
```
Since this was a run with minimum package levels, it used virtualenv 14.0.0. That version does not state support for Python 3.7 yet. | 1.0 | virtualenv setup failure during install test on Python 3.7 with minimum package levels - The Travis run on OS-X on Python 3.7.7 with minimum package levels fails when setting up the virtualenv for an install test (see https://travis-ci.org/github/pywbem/pywbem/jobs/674559955):
```
Testcase test1: Pip install from repo root directory: tests/installtest/../..
Saving current virtualenv: /Users/travis/venv
Creating virtualenv: tests/installtest/../../tmp_installtest/virtualenvs/pywbem_test_test1
..using this Python command: /Users/travis/venv/bin/python
Error: Command failed with rc=100: virtualenv -p /Users/travis/venv/bin/python tests/installtest/../../tmp_installtest/virtualenvs/pywbem_test_test1, output follows:
/Users/travis/venv/lib/python3.7/site-packages/virtualenv.py:991: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
import imp
Using base prefix '/usr/local/opt/python/bin/../Frameworks/Python.framework/Versions/3.7'
New python executable in /Users/travis/build/pywbem/pywbem/tmp_installtest/virtualenvs/pywbem_test_test1/bin/python
ERROR: The executable /Users/travis/build/pywbem/pywbem/tmp_installtest/virtualenvs/pywbem_test_test1/bin/python is not functioning
ERROR: It thinks sys.prefix is '/usr/local/Cellar/python/3.7.7/Frameworks/Python.framework/Versions/3.7' (should be '/Users/travis/build/pywbem/pywbem/tmp_installtest/virtualenvs/pywbem_test_test1')
ERROR: virtualenv is not compatible with this system or executable
Running virtualenv with interpreter /Users/travis/venv/bin/python
make: *** [installtest] Error 1
```
Since this was a run with minimum package levels, it used virtualenv 14.0.0. That version does not state support for Python 3.7 yet. | test | virtualenv setup failure during install test on python with minimum package levels the travis run on os x on python with minimum package levels fails when setting up the virtualenv for an install test see testcase pip install from repo root directory tests installtest saving current virtualenv users travis venv creating virtualenv tests installtest tmp installtest virtualenvs pywbem test using this python command users travis venv bin python error command failed with rc virtualenv p users travis venv bin python tests installtest tmp installtest virtualenvs pywbem test output follows users travis venv lib site packages virtualenv py deprecationwarning the imp module is deprecated in favour of importlib see the module s documentation for alternative uses import imp using base prefix usr local opt python bin frameworks python framework versions new python executable in users travis build pywbem pywbem tmp installtest virtualenvs pywbem test bin python error the executable users travis build pywbem pywbem tmp installtest virtualenvs pywbem test bin python is not functioning error it thinks sys prefix is usr local cellar python frameworks python framework versions should be users travis build pywbem pywbem tmp installtest virtualenvs pywbem test error virtualenv is not compatible with this system or executable running virtualenv with interpreter users travis venv bin python make error since this was a run with minimum package levels it used virtualenv that version does not state support for python yet | 1 |
63,000 | 6,822,589,214 | IssuesEvent | 2017-11-07 20:37:13 | eclipse/openj9 | https://api.github.com/repos/eclipse/openj9 | closed | cmdLineTest: URLClassLoaderTests: failed message printed out during test execution | comp:test | excluded tests are in `test/cmdLineTests/URLClassLoaderTests/exclude.xml`
```
<exclude id="Sanity.verifySuccess" platform="all"><reason>Unexpected message printed out in cmdLineTester_SCURLClassLoaderNPTests_SE90 and cmdLineTester_SCURLClassLoaderTests_SE90</reason></exclude>
<exclude id="FindStore.FindExplicit" platform="all"><reason>Unexpected message printed out in cmdLineTester_SCURLClassLoaderNPTests_SE90 and cmdLineTester_SCURLClassLoaderTests_SE90</reason></exclude>
<exclude id="FindStore.FindRelative" platform="all"><reason>Unexpected message printed out in cmdLineTester_SCURLClassLoaderNPTests_SE90 and cmdLineTester_SCURLClassLoaderTests_SE90</reason></exclude>
<exclude id="FindStore.FindNetUse" platform="all"><reason>Unexpected message printed out in cmdLineTester_SCURLClassLoaderNPTests_SE90 and cmdLineTester_SCURLClassLoaderTests_SE90</reason></exclude>
<exclude id="FindStore.FindClassfile" platform="all"><reason>Unexpected message printed out in cmdLineTester_SCURLClassLoaderNPTests_SE90 and cmdLineTester_SCURLClassLoaderTests_SE90</reason></exclude>
<exclude id="FindStore.FindDiffcpClassfile" platform="all"><reason>Unexpected message printed out in cmdLineTester_SCURLClassLoaderNPTests_SE90 and cmdLineTester_SCURLClassLoaderTests_SE90</reason></exclude>
<exclude id="JarExtensionsTests.SingleJarInManifestWithIndex.Verify1" platform="all"><reason>Unexpected message printed out in cmdLineTester_SCURLClassLoaderNPTests_SE90 and cmdLineTester_SCURLClassLoaderTests_SE90</reason></exclude>
<exclude id="JarExtensionsTests.MultipleJarsInManifestsWithIndex.Verify1" platform="all"><reason>Unexpected message printed out in cmdLineTester_SCURLClassLoaderNPTests_SE90 and cmdLineTester_SCURLClassLoaderTests_SE90</reason></exclude>
```
java -version:
```
root@1c569afa5e3e:/test/TestConfig# /java/bin/java -version
openjdk version "9-internal"
OpenJDK Runtime Environment (build 9-internal+0-adhoc.openj9.openjdk)
Eclipse OpenJ9 VM (build 2.9, JRE 9 Linux amd64-64 Compressed References 20171011_366953 (JIT enabled, AOT enabled)
OpenJ9 - 26f4ca3
OMR - 5d625a3
OpenJDK - a4765a5 based on jdk-9+181)
```
test error messagre example:
```
Testing: FindStore.FindDiffcpClassfile
Test start time: 2017/10/17 21:49:06 Coordinated Universal Time
Running command: "/java/bin/java" -Xcompressedrefs -Xcompressedrefs -Xjit -Xgcpolicy:gencon -Xshareclasses:persistent,controlDir=.,name=FindStore,noTimestampChecks -cp ./FindStore/M_Classes:./FindStore/N_Classes:./FindStore/O_Classes:./FindStore/P_Classes jnurlcldr.shared.findstore.M_Main
Time spent starting: 4 milliseconds
Time spent executing: 332 milliseconds
Test result: FAILED
[OUT] LOCAL M
[OUT] LOCAL N
[OUT] LOCAL O
[OUT] LOCAL P
[OUT] Result=3
>> Success condition was found: [Output match: Result=3]
>> Failure condition was found: [Output match: LOCAL]
>> Failure condition was not found: [Output match: Unhandled Exception]
>> Failure condition was not found: [Output match: Exception:]
>> Failure condition was not found: [Output match: Error:]
``` | 1.0 | cmdLineTest: URLClassLoaderTests: failed message printed out during test execution - excluded tests are in `test/cmdLineTests/URLClassLoaderTests/exclude.xml`
```
<exclude id="Sanity.verifySuccess" platform="all"><reason>Unexpected message printed out in cmdLineTester_SCURLClassLoaderNPTests_SE90 and cmdLineTester_SCURLClassLoaderTests_SE90</reason></exclude>
<exclude id="FindStore.FindExplicit" platform="all"><reason>Unexpected message printed out in cmdLineTester_SCURLClassLoaderNPTests_SE90 and cmdLineTester_SCURLClassLoaderTests_SE90</reason></exclude>
<exclude id="FindStore.FindRelative" platform="all"><reason>Unexpected message printed out in cmdLineTester_SCURLClassLoaderNPTests_SE90 and cmdLineTester_SCURLClassLoaderTests_SE90</reason></exclude>
<exclude id="FindStore.FindNetUse" platform="all"><reason>Unexpected message printed out in cmdLineTester_SCURLClassLoaderNPTests_SE90 and cmdLineTester_SCURLClassLoaderTests_SE90</reason></exclude>
<exclude id="FindStore.FindClassfile" platform="all"><reason>Unexpected message printed out in cmdLineTester_SCURLClassLoaderNPTests_SE90 and cmdLineTester_SCURLClassLoaderTests_SE90</reason></exclude>
<exclude id="FindStore.FindDiffcpClassfile" platform="all"><reason>Unexpected message printed out in cmdLineTester_SCURLClassLoaderNPTests_SE90 and cmdLineTester_SCURLClassLoaderTests_SE90</reason></exclude>
<exclude id="JarExtensionsTests.SingleJarInManifestWithIndex.Verify1" platform="all"><reason>Unexpected message printed out in cmdLineTester_SCURLClassLoaderNPTests_SE90 and cmdLineTester_SCURLClassLoaderTests_SE90</reason></exclude>
<exclude id="JarExtensionsTests.MultipleJarsInManifestsWithIndex.Verify1" platform="all"><reason>Unexpected message printed out in cmdLineTester_SCURLClassLoaderNPTests_SE90 and cmdLineTester_SCURLClassLoaderTests_SE90</reason></exclude>
```
java -version:
```
root@1c569afa5e3e:/test/TestConfig# /java/bin/java -version
openjdk version "9-internal"
OpenJDK Runtime Environment (build 9-internal+0-adhoc.openj9.openjdk)
Eclipse OpenJ9 VM (build 2.9, JRE 9 Linux amd64-64 Compressed References 20171011_366953 (JIT enabled, AOT enabled)
OpenJ9 - 26f4ca3
OMR - 5d625a3
OpenJDK - a4765a5 based on jdk-9+181)
```
test error messagre example:
```
Testing: FindStore.FindDiffcpClassfile
Test start time: 2017/10/17 21:49:06 Coordinated Universal Time
Running command: "/java/bin/java" -Xcompressedrefs -Xcompressedrefs -Xjit -Xgcpolicy:gencon -Xshareclasses:persistent,controlDir=.,name=FindStore,noTimestampChecks -cp ./FindStore/M_Classes:./FindStore/N_Classes:./FindStore/O_Classes:./FindStore/P_Classes jnurlcldr.shared.findstore.M_Main
Time spent starting: 4 milliseconds
Time spent executing: 332 milliseconds
Test result: FAILED
[OUT] LOCAL M
[OUT] LOCAL N
[OUT] LOCAL O
[OUT] LOCAL P
[OUT] Result=3
>> Success condition was found: [Output match: Result=3]
>> Failure condition was found: [Output match: LOCAL]
>> Failure condition was not found: [Output match: Unhandled Exception]
>> Failure condition was not found: [Output match: Exception:]
>> Failure condition was not found: [Output match: Error:]
``` | test | cmdlinetest urlclassloadertests failed message printed out during test execution excluded tests are in test cmdlinetests urlclassloadertests exclude xml unexpected message printed out in cmdlinetester scurlclassloadernptests and cmdlinetester scurlclassloadertests unexpected message printed out in cmdlinetester scurlclassloadernptests and cmdlinetester scurlclassloadertests unexpected message printed out in cmdlinetester scurlclassloadernptests and cmdlinetester scurlclassloadertests unexpected message printed out in cmdlinetester scurlclassloadernptests and cmdlinetester scurlclassloadertests unexpected message printed out in cmdlinetester scurlclassloadernptests and cmdlinetester scurlclassloadertests unexpected message printed out in cmdlinetester scurlclassloadernptests and cmdlinetester scurlclassloadertests unexpected message printed out in cmdlinetester scurlclassloadernptests and cmdlinetester scurlclassloadertests unexpected message printed out in cmdlinetester scurlclassloadernptests and cmdlinetester scurlclassloadertests java version root test testconfig java bin java version openjdk version internal openjdk runtime environment build internal adhoc openjdk eclipse vm build jre linux compressed references jit enabled aot enabled omr openjdk based on jdk test error messagre example testing findstore finddiffcpclassfile test start time coordinated universal time running command java bin java xcompressedrefs xcompressedrefs xjit xgcpolicy gencon xshareclasses persistent controldir name findstore notimestampchecks cp findstore m classes findstore n classes findstore o classes findstore p classes jnurlcldr shared findstore m main time spent starting milliseconds time spent executing milliseconds test result failed local m local n local o local p result success condition was found failure condition was found failure condition was not found failure condition was not found failure condition was not found | 1 |
97,473 | 8,656,935,003 | IssuesEvent | 2018-11-27 19:50:53 | elastic/kibana | https://api.github.com/repos/elastic/kibana | opened | Add discover tests to getting started (shakespeare) test suite | test | **Describe the feature:**
Getting started test suite needs couple of tests for discover so that we won't have any regressions with non time-based index patterns.
1. Load the index pattern, look for shakespeare index pattern in discover and ensure no of hits (total) match the no of documents
2. Search for a play name (turn on the auto-complete?) and ensure no of hits match the no of documents with the play name | 1.0 | Add discover tests to getting started (shakespeare) test suite - **Describe the feature:**
Getting started test suite needs couple of tests for discover so that we won't have any regressions with non time-based index patterns.
1. Load the index pattern, look for shakespeare index pattern in discover and ensure no of hits (total) match the no of documents
2. Search for a play name (turn on the auto-complete?) and ensure no of hits match the no of documents with the play name | test | add discover tests to getting started shakespeare test suite describe the feature getting started test suite needs couple of tests for discover so that we won t have any regressions with non time based index patterns load the index pattern look for shakespeare index pattern in discover and ensure no of hits total match the no of documents search for a play name turn on the auto complete and ensure no of hits match the no of documents with the play name | 1 |
197,892 | 22,615,766,245 | IssuesEvent | 2022-06-29 21:52:24 | veeveewang/play-webgoat | https://api.github.com/repos/veeveewang/play-webgoat | opened | CVE-2020-36518 (High) detected in jackson-databind-2.11.4.jar | security vulnerability | ## CVE-2020-36518 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.11.4.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>
Dependency Hierarchy:
- play-ahc-ws_2.13-2.8.8.jar (Root Library)
- play-ws_2.13-2.8.8.jar
- play_2.13-2.8.8.jar
- :x: **jackson-databind-2.11.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/veeveewang/play-webgoat/commit/bd07c171f3e663057324c7cd6e77122963fcb27e">bd07c171f3e663057324c7cd6e77122963fcb27e</a></p>
<p>Found in base branch: <b>2.8.x</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
jackson-databind before 2.13.0 allows a Java StackOverflow exception and denial of service via a large depth of nested objects.
Mend Note: After conducting further research, Mend has determined that all versions of com.fasterxml.jackson.core:jackson-databind up to version 2.13.2 are vulnerable to CVE-2020-36518.
<p>Publish Date: 2022-03-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36518>CVE-2020-36518</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-03-11</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.12.6.1,2.13.2.1</p>
</p>
</details>
<p></p>
| True | CVE-2020-36518 (High) detected in jackson-databind-2.11.4.jar - ## CVE-2020-36518 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.11.4.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>
Dependency Hierarchy:
- play-ahc-ws_2.13-2.8.8.jar (Root Library)
- play-ws_2.13-2.8.8.jar
- play_2.13-2.8.8.jar
- :x: **jackson-databind-2.11.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/veeveewang/play-webgoat/commit/bd07c171f3e663057324c7cd6e77122963fcb27e">bd07c171f3e663057324c7cd6e77122963fcb27e</a></p>
<p>Found in base branch: <b>2.8.x</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
jackson-databind before 2.13.0 allows a Java StackOverflow exception and denial of service via a large depth of nested objects.
Mend Note: After conducting further research, Mend has determined that all versions of com.fasterxml.jackson.core:jackson-databind up to version 2.13.2 are vulnerable to CVE-2020-36518.
<p>Publish Date: 2022-03-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36518>CVE-2020-36518</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-03-11</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.12.6.1,2.13.2.1</p>
</p>
</details>
<p></p>
| non_test | cve high detected in jackson databind jar cve high severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href dependency hierarchy play ahc ws jar root library play ws jar play jar x jackson databind jar vulnerable library found in head commit a href found in base branch x vulnerability details jackson databind before allows a java stackoverflow exception and denial of service via a large depth of nested objects mend note after conducting further research mend has determined that all versions of com fasterxml jackson core jackson databind up to version are vulnerable to cve publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version release date fix resolution com fasterxml jackson core jackson databind | 0 |
258,121 | 22,284,579,169 | IssuesEvent | 2022-06-11 12:14:45 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | sql/logictest: TestSqlLiteLogic failed | C-test-failure O-robot branch-release-22.1 | sql/logictest.TestSqlLiteLogic [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=5442482&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=5442482&tab=artifacts#/) on release-22.1 @ [3181b7faa2f3b41d6a15ab4b74d2c60bcfe5132d](https://github.com/cockroachdb/cockroach/commits/3181b7faa2f3b41d6a15ab4b74d2c60bcfe5132d):
```
[09:26:23] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_0.test: 2700 statements
[09:26:23] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_1.test: 6973 statements
[09:26:23] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test: 848 statements
[09:26:24] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_6.test: 3930 statements
[09:26:25] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_0.test: 2861 statements
[09:26:25] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_1.test: 7125 statements
[09:26:25] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test: 1021 statements
[09:26:26] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_6.test: 4091 statements
[09:26:27] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_0.test: 3032 statements
[09:26:27] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_1.test: 7288 statements
[09:26:27] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test: 1182 statements
[09:26:28] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_6.test: 4256 statements
[09:26:29] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_0.test: 3184 statements
[09:26:29] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_1.test: 7466 statements
[09:26:29] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test: 1358 statements
[09:26:30] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_6.test: 4379 statements
[09:26:31] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_0.test: 3344 statements
[09:26:31] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_1.test: 7628 statements
[09:26:31] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test: 1548 statements
[09:26:32] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_6.test: 4528 statements
[09:26:33] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_0.test: 3505 statements
[09:26:33] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_1.test: 7743 statements
[09:26:33] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test: 1721 statements
[09:26:34] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_6.test: 4691 statements
[09:26:35] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_0.test: 3675 statements
[09:26:35] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_1.test: 7905 statements
[09:26:35] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test: 1895 statements
[09:26:36] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_6.test: 4838 statements
[09:26:37] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_0.test: 3828 statements
[09:26:37] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_1.test: 8078 statements
[09:26:37] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test: 2079 statements
[09:26:38] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_6.test: 5001 statements
[09:26:39] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_0.test: 3988 statements
[09:26:39] --- done: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_1.test with config fakedist-metadata: 8172 tests, 0 failures
[09:26:39] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test: 2240 statements
[09:26:40] --- total progress: 9491370 statements
=== CONT TestSqlLiteLogic/fakedist-metadata/slt_good_3.test#13
logic.go:3484:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test:18360: SELECT pk, col0 FROM view_2_tab2_410
expected success, but found
(XXUUU) txn already encountered an error; cannot be used anymore (previous err: concurrent txn use detected. ba: Scan [/Table/108/1/5,/Table/108/1/6), [txn: 5142c00a])
logic.go:3195:
pq: txn already encountered an error; cannot be used anymore (previous err: concurrent txn use detected. ba: Scan [/Table/108/1/5,/Table/108/1/6), [txn: 5142c00a])
[09:27:07] --- done: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test with config fakedist-metadata: 3888 tests, 2 failures
logic.go:4216:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test:18366: error while processing
logic.go:4216: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test:18366: too many errors encountered, skipping the rest of the input
[09:27:07] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_0.test: 5930 statements
--- FAIL: TestSqlLiteLogic/fakedist-metadata/slt_good_3.test#13 (57.24s)
```
<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-queries
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestSqlLiteLogic.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| 1.0 | sql/logictest: TestSqlLiteLogic failed - sql/logictest.TestSqlLiteLogic [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=5442482&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=5442482&tab=artifacts#/) on release-22.1 @ [3181b7faa2f3b41d6a15ab4b74d2c60bcfe5132d](https://github.com/cockroachdb/cockroach/commits/3181b7faa2f3b41d6a15ab4b74d2c60bcfe5132d):
```
[09:26:23] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_0.test: 2700 statements
[09:26:23] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_1.test: 6973 statements
[09:26:23] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test: 848 statements
[09:26:24] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_6.test: 3930 statements
[09:26:25] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_0.test: 2861 statements
[09:26:25] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_1.test: 7125 statements
[09:26:25] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test: 1021 statements
[09:26:26] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_6.test: 4091 statements
[09:26:27] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_0.test: 3032 statements
[09:26:27] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_1.test: 7288 statements
[09:26:27] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test: 1182 statements
[09:26:28] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_6.test: 4256 statements
[09:26:29] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_0.test: 3184 statements
[09:26:29] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_1.test: 7466 statements
[09:26:29] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test: 1358 statements
[09:26:30] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_6.test: 4379 statements
[09:26:31] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_0.test: 3344 statements
[09:26:31] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_1.test: 7628 statements
[09:26:31] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test: 1548 statements
[09:26:32] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_6.test: 4528 statements
[09:26:33] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_0.test: 3505 statements
[09:26:33] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_1.test: 7743 statements
[09:26:33] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test: 1721 statements
[09:26:34] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_6.test: 4691 statements
[09:26:35] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_0.test: 3675 statements
[09:26:35] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_1.test: 7905 statements
[09:26:35] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test: 1895 statements
[09:26:36] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_6.test: 4838 statements
[09:26:37] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_0.test: 3828 statements
[09:26:37] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_1.test: 8078 statements
[09:26:37] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test: 2079 statements
[09:26:38] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_6.test: 5001 statements
[09:26:39] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_0.test: 3988 statements
[09:26:39] --- done: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_1.test with config fakedist-metadata: 8172 tests, 0 failures
[09:26:39] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test: 2240 statements
[09:26:40] --- total progress: 9491370 statements
=== CONT TestSqlLiteLogic/fakedist-metadata/slt_good_3.test#13
logic.go:3484:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test:18360: SELECT pk, col0 FROM view_2_tab2_410
expected success, but found
(XXUUU) txn already encountered an error; cannot be used anymore (previous err: concurrent txn use detected. ba: Scan [/Table/108/1/5,/Table/108/1/6), [txn: 5142c00a])
logic.go:3195:
pq: txn already encountered an error; cannot be used anymore (previous err: concurrent txn use detected. ba: Scan [/Table/108/1/5,/Table/108/1/6), [txn: 5142c00a])
[09:27:07] --- done: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test with config fakedist-metadata: 3888 tests, 2 failures
logic.go:4216:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test:18366: error while processing
logic.go:4216: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/10/slt_good_3.test:18366: too many errors encountered, skipping the rest of the input
[09:27:07] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3574/execroot/cockroach/bazel-out/k8-dbg/bin/pkg/sql/logictest/logictest_test_/logictest_test.runfiles/cockroach/external/com_github_cockroachdb_sqllogictest/test/index/view/100/slt_good_0.test: 5930 statements
--- FAIL: TestSqlLiteLogic/fakedist-metadata/slt_good_3.test#13 (57.24s)
```
<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-queries
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestSqlLiteLogic.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| test | sql logictest testsqllitelogic failed sql logictest testsqllitelogic with on release progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements done home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test with config fakedist metadata tests failures progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements total progress statements cont testsqllitelogic fakedist metadata slt good test logic go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test select pk from view expected success but found xxuuu txn already encountered an error cannot be used anymore previous err concurrent txn use detected ba scan logic go pq txn already encountered an error cannot be used anymore previous err concurrent txn use detected ba scan done home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test with config fakedist metadata tests failures logic go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test error while processing logic go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test too many errors encountered skipping the rest of the input progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot cockroach bazel out dbg bin pkg sql logictest logictest test logictest test runfiles cockroach external com github cockroachdb sqllogictest test index view slt good test statements fail testsqllitelogic fakedist metadata slt good test help see also cc cockroachdb sql queries | 1 |
16,320 | 2,613,635,721 | IssuesEvent | 2015-02-27 22:23:14 | nprapps/dailygraphics | https://api.github.com/repos/nprapps/dailygraphics | opened | Still possible to redeploy all the graphics | Priority: Low | ```fab production deploy``` returns an error, but ```fab production deploy:``` (with colon) will start to redeploy everything in the ```graphics``` folder. | 1.0 | Still possible to redeploy all the graphics - ```fab production deploy``` returns an error, but ```fab production deploy:``` (with colon) will start to redeploy everything in the ```graphics``` folder. | non_test | still possible to redeploy all the graphics fab production deploy returns an error but fab production deploy with colon will start to redeploy everything in the graphics folder | 0 |
33,201 | 4,818,060,806 | IssuesEvent | 2016-11-04 15:24:04 | uProxy/uproxy | https://api.github.com/repos/uProxy/uproxy | closed | Docker-based latency test | C:Performance C:SOCKS C:Testing P2 T:Obsolete | Thanks to @mollyling and @trevj we now have a good throughput test based on Docker. The flip side of throughput is latency, so IMHO we should try to build a latency test, to see how much additional delay is imposed by uProxy. In my manual testing, latency appears to be variable, and spikes dramatically during heavy load (e.g. many simultaneous requests for a complex page), so the simplest possible test probably will not suffice to see the behavior we care about.
See https://github.com/uProxy/uproxy/issues/1830 for a discussion of how we can reach high latency, and what we might do about it. I have a prototype of a change to improve latency, but without a test it is hard to have confidence that the change works.
| 1.0 | Docker-based latency test - Thanks to @mollyling and @trevj we now have a good throughput test based on Docker. The flip side of throughput is latency, so IMHO we should try to build a latency test, to see how much additional delay is imposed by uProxy. In my manual testing, latency appears to be variable, and spikes dramatically during heavy load (e.g. many simultaneous requests for a complex page), so the simplest possible test probably will not suffice to see the behavior we care about.
See https://github.com/uProxy/uproxy/issues/1830 for a discussion of how we can reach high latency, and what we might do about it. I have a prototype of a change to improve latency, but without a test it is hard to have confidence that the change works.
| test | docker based latency test thanks to mollyling and trevj we now have a good throughput test based on docker the flip side of throughput is latency so imho we should try to build a latency test to see how much additional delay is imposed by uproxy in my manual testing latency appears to be variable and spikes dramatically during heavy load e g many simultaneous requests for a complex page so the simplest possible test probably will not suffice to see the behavior we care about see for a discussion of how we can reach high latency and what we might do about it i have a prototype of a change to improve latency but without a test it is hard to have confidence that the change works | 1 |
340,872 | 30,550,532,447 | IssuesEvent | 2023-07-20 08:13:00 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | server: `TestAdminAPIStatementDiagnosticsBundle` does not work with secondary tenants | C-test-failure A-multitenancy T-observability-inf A-observability-inf | Epic: CRDB-26687
Issue uncovered by #106931.
Informs #76378.
**Describe the problem**
When `TestAdminAPIStatementDiagnosticsBundle` is modified to use a secondary tenant, the test fails with a 404 error on one of the API endpoints. This suggests that the underlying "stmt bundle retrieval" HTTP API does not function properly on secondary tenants.
**To Reproduce**
On top of the branch from #106931, modify the test and replace `TestDoesNotWorkWithSecondaryTenantsButWeDontKnowWhyYet` by `TestTenantAlwaysEnabled`.
**Expected behavior**
The test should work the same regardless of whether a secondary tenant is used or not.
(The test should succeed when the parameter `DefaultTestTenant` is omitted entirely, which makes it default to `TestTenantProbabilistic`).
Jira issue: CRDB-29768 | 1.0 | server: `TestAdminAPIStatementDiagnosticsBundle` does not work with secondary tenants - Epic: CRDB-26687
Issue uncovered by #106931.
Informs #76378.
**Describe the problem**
When `TestAdminAPIStatementDiagnosticsBundle` is modified to use a secondary tenant, the test fails with a 404 error on one of the API endpoints. This suggests that the underlying "stmt bundle retrieval" HTTP API does not function properly on secondary tenants.
**To Reproduce**
On top of the branch from #106931, modify the test and replace `TestDoesNotWorkWithSecondaryTenantsButWeDontKnowWhyYet` by `TestTenantAlwaysEnabled`.
**Expected behavior**
The test should work the same regardless of whether a secondary tenant is used or not.
(The test should succeed when the parameter `DefaultTestTenant` is omitted entirely, which makes it default to `TestTenantProbabilistic`).
Jira issue: CRDB-29768 | test | server testadminapistatementdiagnosticsbundle does not work with secondary tenants epic crdb issue uncovered by informs describe the problem when testadminapistatementdiagnosticsbundle is modified to use a secondary tenant the test fails with a error on one of the api endpoints this suggests that the underlying stmt bundle retrieval http api does not function properly on secondary tenants to reproduce on top of the branch from modify the test and replace testdoesnotworkwithsecondarytenantsbutwedontknowwhyyet by testtenantalwaysenabled expected behavior the test should work the same regardless of whether a secondary tenant is used or not the test should succeed when the parameter defaulttesttenant is omitted entirely which makes it default to testtenantprobabilistic jira issue crdb | 1 |
77,411 | 21,789,758,353 | IssuesEvent | 2022-05-14 17:57:27 | RoboJackets/mtrain-firmware | https://api.github.com/repos/RoboJackets/mtrain-firmware | closed | Adjust build system to work with external projects | exp / intermediate priority / medium status / development type / enchancement area / build-system | * Be able to use as submodule with external source files
... | 1.0 | Adjust build system to work with external projects - * Be able to use as submodule with external source files
... | non_test | adjust build system to work with external projects be able to use as submodule with external source files | 0 |
185,197 | 14,344,907,442 | IssuesEvent | 2020-11-28 16:35:21 | nanovms/nanos | https://api.github.com/repos/nanovms/nanos | closed | proper test for mmap(2), munmap(2), mremap(2), etc. | good first issue help wanted memory tests | We need a runtime test to exercise the following syscalls in unix/mmap.c:
~~- mmap~~
~~- mincore~~
~~- munmap~~
~~- mremap~~
~~- mprotect (add to "paging" runtime test - which really should be called "page_prot" or something)~~
| 1.0 | proper test for mmap(2), munmap(2), mremap(2), etc. - We need a runtime test to exercise the following syscalls in unix/mmap.c:
~~- mmap~~
~~- mincore~~
~~- munmap~~
~~- mremap~~
~~- mprotect (add to "paging" runtime test - which really should be called "page_prot" or something)~~
| test | proper test for mmap munmap mremap etc we need a runtime test to exercise the following syscalls in unix mmap c mmap mincore munmap mremap mprotect add to paging runtime test which really should be called page prot or something | 1 |
473,335 | 13,640,885,073 | IssuesEvent | 2020-09-25 13:25:09 | enso-org/ide | https://api.github.com/repos/enso-org/ide | opened | Check for webgl version | Category: IDE Change: Non-Breaking Difficulty: Beginner Priority: Medium Type: Enhancement | ### Summary
When user browser or hardware does not support webgl2 it receives an rather obscure error message in console. It should be a clear alert instead.
The `get_webgl2_context function` in src/rust/lib/system/web/src/lib.rs currently panics with an obscure error when the user's hardware does not support webgl2.
### Value
Less bug reports titled "IDE does not work and I don't know why"
### Specification
The get_webgl2_context function in src/rust/lib/system/web/src/lib.rs currently panics. It should return Result with appropriate error, and propagate it up to `IdeInitializer::start_and_forget` function. There the error (and any else error returned during intialization) should be displayed somehow; the basic javascript alert is sufficient.
### Acceptance Criteria & Test Cases
Test it on the browser with disabled webgl2.
| 1.0 | Check for webgl version - ### Summary
When user browser or hardware does not support webgl2 it receives an rather obscure error message in console. It should be a clear alert instead.
The `get_webgl2_context function` in src/rust/lib/system/web/src/lib.rs currently panics with an obscure error when the user's hardware does not support webgl2.
### Value
Less bug reports titled "IDE does not work and I don't know why"
### Specification
The get_webgl2_context function in src/rust/lib/system/web/src/lib.rs currently panics. It should return Result with appropriate error, and propagate it up to `IdeInitializer::start_and_forget` function. There the error (and any else error returned during intialization) should be displayed somehow; the basic javascript alert is sufficient.
### Acceptance Criteria & Test Cases
Test it on the browser with disabled webgl2.
| non_test | check for webgl version summary when user browser or hardware does not support it receives an rather obscure error message in console it should be a clear alert instead the get context function in src rust lib system web src lib rs currently panics with an obscure error when the user s hardware does not support value less bug reports titled ide does not work and i don t know why specification the get context function in src rust lib system web src lib rs currently panics it should return result with appropriate error and propagate it up to ideinitializer start and forget function there the error and any else error returned during intialization should be displayed somehow the basic javascript alert is sufficient acceptance criteria test cases test it on the browser with disabled | 0 |
19,803 | 13,462,938,131 | IssuesEvent | 2020-09-09 16:48:09 | patternfly/patternfly-org | https://api.github.com/repos/patternfly/patternfly-org | closed | Update "Colors for charts" page with new design | infrastructure | The "Colors for charts" pages has been redesigned as follows: https://marvelapp.com/prototype/4j44628
Need to update it to reflect that!
@evwilkin | 1.0 | Update "Colors for charts" page with new design - The "Colors for charts" pages has been redesigned as follows: https://marvelapp.com/prototype/4j44628
Need to update it to reflect that!
@evwilkin | non_test | update colors for charts page with new design the colors for charts pages has been redesigned as follows need to update it to reflect that evwilkin | 0 |
2,984 | 2,729,603,273 | IssuesEvent | 2015-04-16 09:39:09 | Lesterpig/openparty | https://api.github.com/repos/Lesterpig/openparty | closed | Build a decent documentation for gameplay definitions | Documentation Major | Would be easier for plugin development :) | 1.0 | Build a decent documentation for gameplay definitions - Would be easier for plugin development :) | non_test | build a decent documentation for gameplay definitions would be easier for plugin development | 0 |
26,851 | 4,257,826,655 | IssuesEvent | 2016-07-11 01:48:00 | area515/Creation-Workshop-Host | https://api.github.com/repos/area515/Creation-Workshop-Host | closed | NegativeArraySizeException loading STL File | testing help wanted | The attached STL file is an ASCII format STL file that begins with the string `solid OpenSCAD_Model` and was generated by OpenSCAD.
Looking at the stack trace, it would seem that the file is being loaded as a binary STL rather than an ASCII STL file.
```
Caused by: java.lang.NegativeArraySizeException
at org.area515.resinprinter.slice.StlFile.readBinaryFile(StlFile.java:317) ~[main/:?]
at org.area515.resinprinter.slice.StlFile.load(StlFile.java:433) ~[main/:?]
at org.area515.resinprinter.slice.ZSlicer.loadFile(ZSlicer.java:939) ~[main/:?]
at org.area515.resinprinter.job.STLFileProcessor.processFile(STLFileProcessor.java:88) ~[main/:?]
at org.area515.resinprinter.job.PrintJobProcessingThread.call(PrintJobProcessingThread.java:38) ~[main/:?]
at org.area515.resinprinter.job.PrintJobProcessingThread.call(PrintJobProcessingThread.java:11) ~[main/:?]
```
I suspect that the logic in in commit f1b20e84cb40defe84a2f3ab3e7c764b87183222 for #226 is having trouble here, but I'm not sure where the `facet` seeking code is going wrong.
[lenscap-36mm.stl.zip](https://github.com/area515/Creation-Workshop-Host/files/356265/lenscap-36mm.stl.zip) | 1.0 | NegativeArraySizeException loading STL File - The attached STL file is an ASCII format STL file that begins with the string `solid OpenSCAD_Model` and was generated by OpenSCAD.
Looking at the stack trace, it would seem that the file is being loaded as a binary STL rather than an ASCII STL file.
```
Caused by: java.lang.NegativeArraySizeException
at org.area515.resinprinter.slice.StlFile.readBinaryFile(StlFile.java:317) ~[main/:?]
at org.area515.resinprinter.slice.StlFile.load(StlFile.java:433) ~[main/:?]
at org.area515.resinprinter.slice.ZSlicer.loadFile(ZSlicer.java:939) ~[main/:?]
at org.area515.resinprinter.job.STLFileProcessor.processFile(STLFileProcessor.java:88) ~[main/:?]
at org.area515.resinprinter.job.PrintJobProcessingThread.call(PrintJobProcessingThread.java:38) ~[main/:?]
at org.area515.resinprinter.job.PrintJobProcessingThread.call(PrintJobProcessingThread.java:11) ~[main/:?]
```
I suspect that the logic in in commit f1b20e84cb40defe84a2f3ab3e7c764b87183222 for #226 is having trouble here, but I'm not sure where the `facet` seeking code is going wrong.
[lenscap-36mm.stl.zip](https://github.com/area515/Creation-Workshop-Host/files/356265/lenscap-36mm.stl.zip) | test | negativearraysizeexception loading stl file the attached stl file is an ascii format stl file that begins with the string solid openscad model and was generated by openscad looking at the stack trace it would seem that the file is being loaded as a binary stl rather than an ascii stl file caused by java lang negativearraysizeexception at org resinprinter slice stlfile readbinaryfile stlfile java at org resinprinter slice stlfile load stlfile java at org resinprinter slice zslicer loadfile zslicer java at org resinprinter job stlfileprocessor processfile stlfileprocessor java at org resinprinter job printjobprocessingthread call printjobprocessingthread java at org resinprinter job printjobprocessingthread call printjobprocessingthread java i suspect that the logic in in commit for is having trouble here but i m not sure where the facet seeking code is going wrong | 1 |
347,335 | 24,888,005,452 | IssuesEvent | 2022-10-28 09:26:35 | wrewsama/ped | https://api.github.com/repos/wrewsama/ped | opened | Wrong numbering in Quick start section | severity.VeryLow type.DocumentationBug | The number in the last point is incorrect.
<!--session: 1666943752219-ab42b068-3b76-4b0f-978d-954f8e09e177-->
<!--Version: Web v3.4.4--> | 1.0 | Wrong numbering in Quick start section - The number in the last point is incorrect.
<!--session: 1666943752219-ab42b068-3b76-4b0f-978d-954f8e09e177-->
<!--Version: Web v3.4.4--> | non_test | wrong numbering in quick start section the number in the last point is incorrect | 0 |
280,957 | 24,348,672,303 | IssuesEvent | 2022-10-02 17:08:18 | tomaae/homeassistant-mikrotik_router | https://api.github.com/repos/tomaae/homeassistant-mikrotik_router | closed | Kid control blocked status | enhancement testing | Is it possible to implement dedicated sensor or add an attribute to existing sensor that inform about the current status of blocking? It's indicated in the winnbox by B letter in the first column of the Kids tab. | 1.0 | Kid control blocked status - Is it possible to implement dedicated sensor or add an attribute to existing sensor that inform about the current status of blocking? It's indicated in the winnbox by B letter in the first column of the Kids tab. | test | kid control blocked status is it possible to implement dedicated sensor or add an attribute to existing sensor that inform about the current status of blocking it s indicated in the winnbox by b letter in the first column of the kids tab | 1 |
146,142 | 22,970,098,079 | IssuesEvent | 2022-07-20 01:41:06 | rancher/dashboard | https://api.github.com/repos/rancher/dashboard | opened | Show breadcrumbs when user has filtered by project | area/navigation kind/design | It is not clear to new Rancher users when their view is filtered by project. For example, if you install a Helm chart, you might not immediately see it in Installed Apps due to a project filter:
<img width="1660" alt="Screen Shot 2022-07-19 at 6 38 12 PM" src="https://user-images.githubusercontent.com/20599230/179877119-26ed3af8-0388-4791-9dff-1e654a148475.png">
This could be done in addition to table filtering, depending on how the UX design turns out.
We would still need to decide what to do if the user filters to show multiple projects. | 1.0 | Show breadcrumbs when user has filtered by project - It is not clear to new Rancher users when their view is filtered by project. For example, if you install a Helm chart, you might not immediately see it in Installed Apps due to a project filter:
<img width="1660" alt="Screen Shot 2022-07-19 at 6 38 12 PM" src="https://user-images.githubusercontent.com/20599230/179877119-26ed3af8-0388-4791-9dff-1e654a148475.png">
This could be done in addition to table filtering, depending on how the UX design turns out.
We would still need to decide what to do if the user filters to show multiple projects. | non_test | show breadcrumbs when user has filtered by project it is not clear to new rancher users when their view is filtered by project for example if you install a helm chart you might not immediately see it in installed apps due to a project filter img width alt screen shot at pm src this could be done in addition to table filtering depending on how the ux design turns out we would still need to decide what to do if the user filters to show multiple projects | 0 |
67,692 | 7,057,947,802 | IssuesEvent | 2018-01-04 18:21:23 | scalacenter/scalafix | https://api.github.com/repos/scalacenter/scalafix | opened | Testkit should check that rules are compilable from source | testkit | See #543, this was not caught in unit tests because they only use classloading. We should make it easy to test that rules are loadable from source. | 1.0 | Testkit should check that rules are compilable from source - See #543, this was not caught in unit tests because they only use classloading. We should make it easy to test that rules are loadable from source. | test | testkit should check that rules are compilable from source see this was not caught in unit tests because they only use classloading we should make it easy to test that rules are loadable from source | 1 |
167,172 | 13,003,762,891 | IssuesEvent | 2020-07-24 07:32:52 | kushalarora/LMPL | https://api.github.com/repos/kushalarora/LMPL | opened | Verify top_k and top_p sampling is working fine. | tests | Write tests to verify top_k_top_p_filtering in auto_regressive_decoder.py is working fine.
<!-- Edit the body of your new issue then click the โ "Create Issue" button in the top right of the editor. The first line will be the issue title. Assignees and Labels follow after a blank line. Leave an empty line before beginning the body of the issue. --> | 1.0 | Verify top_k and top_p sampling is working fine. - Write tests to verify top_k_top_p_filtering in auto_regressive_decoder.py is working fine.
<!-- Edit the body of your new issue then click the โ "Create Issue" button in the top right of the editor. The first line will be the issue title. Assignees and Labels follow after a blank line. Leave an empty line before beginning the body of the issue. --> | test | verify top k and top p sampling is working fine write tests to verify top k top p filtering in auto regressive decoder py is working fine | 1 |
187,886 | 6,762,068,449 | IssuesEvent | 2017-10-25 06:06:53 | SpamExperts/directadmin-addon | https://api.github.com/repos/SpamExperts/directadmin-addon | opened | Privacy domain issue when 2 users have the same localpart username | bug priority-high | It appears when 2 users have the same beginning part of the username, the domain list shows the domain from the other user with the same first part of their username. This is a data/privacy issue.
### Version information
```
# cat available_version.txt
4.0.1490694693
```
### Steps to replicate
1. install addon
2. Create reseller
3. Create user `bob` and add domain example.com
4. Create user `bobsfriend` and add domain example.net
5. Login as `bob`
6. Click Professional Spam Filter
7. Click domain list
### Actual result
Result shows the domain from `bob` and `bobsfriend`
### Expected result
Only the domains from that user should be shown.
### Other notes
| 1.0 | Privacy domain issue when 2 users have the same localpart username - It appears when 2 users have the same beginning part of the username, the domain list shows the domain from the other user with the same first part of their username. This is a data/privacy issue.
### Version information
```
# cat available_version.txt
4.0.1490694693
```
### Steps to replicate
1. install addon
2. Create reseller
3. Create user `bob` and add domain example.com
4. Create user `bobsfriend` and add domain example.net
5. Login as `bob`
6. Click Professional Spam Filter
7. Click domain list
### Actual result
Result shows the domain from `bob` and `bobsfriend`
### Expected result
Only the domains from that user should be shown.
### Other notes
| non_test | privacy domain issue when users have the same localpart username it appears when users have the same beginning part of the username the domain list shows the domain from the other user with the same first part of their username this is a data privacy issue version information cat available version txt steps to replicate install addon create reseller create user bob and add domain example com create user bobsfriend and add domain example net login as bob click professional spam filter click domain list actual result result shows the domain from bob and bobsfriend expected result only the domains from that user should be shown other notes | 0 |
157,664 | 19,977,035,201 | IssuesEvent | 2022-01-29 08:45:40 | ignatandrei/NETCoreBlockly | https://api.github.com/repos/ignatandrei/NETCoreBlockly | closed | CVE-2017-0247 (High) detected in system.net.http.4.3.0.nupkg | security vulnerability | ## CVE-2017-0247 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>system.net.http.4.3.0.nupkg</b></p></summary>
<p>Provides a programming interface for modern HTTP applications, including HTTP client components that...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/system.net.http.4.3.0.nupkg">https://api.nuget.org/packages/system.net.http.4.3.0.nupkg</a></p>
<p>Path to dependency file: /src/NetCore2Blockly/TestBlocklyHtml/TestBlocklyHtml.csproj</p>
<p>Path to vulnerable library: /usr/share/dotnet/sdk/NuGetFallbackFolder/system.net.http/4.3.0/system.net.http.4.3.0.nupkg</p>
<p>
Dependency Hierarchy:
- xunit.runner.visualstudio.2.4.0.nupkg (Root Library)
- microsoft.net.test.sdk.16.2.0.nupkg
- microsoft.testplatform.testhost.16.2.0.nupkg
- microsoft.testplatform.objectmodel.16.2.0.nupkg
- netstandard.library.1.6.1.nupkg
- :x: **system.net.http.4.3.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ignatandrei/NETCoreBlockly/commit/6302c9693ee12ca646abef7d34539622c15ec6e1">6302c9693ee12ca646abef7d34539622c15ec6e1</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A denial of service vulnerability exists when the ASP.NET Core fails to properly validate web requests. NOTE: Microsoft has not commented on third-party claims that the issue is that the TextEncoder.EncodeCore function in the System.Text.Encodings.Web package in ASP.NET Core Mvc before 1.0.4 and 1.1.x before 1.1.3 allows remote attackers to cause a denial of service by leveraging failure to properly calculate the length of 4-byte characters in the Unicode Non-Character range.
<p>Publish Date: 2017-05-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-0247>CVE-2017-0247</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/aspnet/Announcements/issues/239">https://github.com/aspnet/Announcements/issues/239</a></p>
<p>Release Date: 2017-05-12</p>
<p>Fix Resolution: System.Text.Encodings.Web - 4.0.1,4.3.1;System.Net.Http - 4.1.2,4.3.2;System.Net.Http.WinHttpHandler - 4.0.2,4.5.4;System.Net.Security - 4.0.1,4.3.1;System.Net.WebSockets.Client - 4.0.1,4.3.1;Microsoft.AspNetCore.Mvc - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Core - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Abstractions - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.ApiExplorer - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Cors - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.DataAnnotations - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Formatters.Json - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Formatters.Xml - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Localization - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Razor.Host - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Razor - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.TagHelpers - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.ViewFeatures - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.WebApiCompatShim - 1.0.4,1.1.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2017-0247 (High) detected in system.net.http.4.3.0.nupkg - ## CVE-2017-0247 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>system.net.http.4.3.0.nupkg</b></p></summary>
<p>Provides a programming interface for modern HTTP applications, including HTTP client components that...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/system.net.http.4.3.0.nupkg">https://api.nuget.org/packages/system.net.http.4.3.0.nupkg</a></p>
<p>Path to dependency file: /src/NetCore2Blockly/TestBlocklyHtml/TestBlocklyHtml.csproj</p>
<p>Path to vulnerable library: /usr/share/dotnet/sdk/NuGetFallbackFolder/system.net.http/4.3.0/system.net.http.4.3.0.nupkg</p>
<p>
Dependency Hierarchy:
- xunit.runner.visualstudio.2.4.0.nupkg (Root Library)
- microsoft.net.test.sdk.16.2.0.nupkg
- microsoft.testplatform.testhost.16.2.0.nupkg
- microsoft.testplatform.objectmodel.16.2.0.nupkg
- netstandard.library.1.6.1.nupkg
- :x: **system.net.http.4.3.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ignatandrei/NETCoreBlockly/commit/6302c9693ee12ca646abef7d34539622c15ec6e1">6302c9693ee12ca646abef7d34539622c15ec6e1</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A denial of service vulnerability exists when the ASP.NET Core fails to properly validate web requests. NOTE: Microsoft has not commented on third-party claims that the issue is that the TextEncoder.EncodeCore function in the System.Text.Encodings.Web package in ASP.NET Core Mvc before 1.0.4 and 1.1.x before 1.1.3 allows remote attackers to cause a denial of service by leveraging failure to properly calculate the length of 4-byte characters in the Unicode Non-Character range.
<p>Publish Date: 2017-05-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-0247>CVE-2017-0247</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/aspnet/Announcements/issues/239">https://github.com/aspnet/Announcements/issues/239</a></p>
<p>Release Date: 2017-05-12</p>
<p>Fix Resolution: System.Text.Encodings.Web - 4.0.1,4.3.1;System.Net.Http - 4.1.2,4.3.2;System.Net.Http.WinHttpHandler - 4.0.2,4.5.4;System.Net.Security - 4.0.1,4.3.1;System.Net.WebSockets.Client - 4.0.1,4.3.1;Microsoft.AspNetCore.Mvc - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Core - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Abstractions - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.ApiExplorer - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Cors - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.DataAnnotations - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Formatters.Json - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Formatters.Xml - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Localization - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Razor.Host - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Razor - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.TagHelpers - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.ViewFeatures - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.WebApiCompatShim - 1.0.4,1.1.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_test | cve high detected in system net http nupkg cve high severity vulnerability vulnerable library system net http nupkg provides a programming interface for modern http applications including http client components that library home page a href path to dependency file src testblocklyhtml testblocklyhtml csproj path to vulnerable library usr share dotnet sdk nugetfallbackfolder system net http system net http nupkg dependency hierarchy xunit runner visualstudio nupkg root library microsoft net test sdk nupkg microsoft testplatform testhost nupkg microsoft testplatform objectmodel nupkg netstandard library nupkg x system net http nupkg vulnerable library found in head commit a href found in base branch master vulnerability details a denial of service vulnerability exists when the asp net core fails to properly validate web requests note microsoft has not commented on third party claims that the issue is that the textencoder encodecore function in the system text encodings web package in asp net core mvc before and x before allows remote attackers to cause a denial of service by leveraging failure to properly calculate the length of byte characters in the unicode non character range publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution system text encodings web system net http system net http winhttphandler system net security system net websockets client microsoft aspnetcore mvc microsoft aspnetcore mvc core microsoft aspnetcore mvc abstractions microsoft aspnetcore mvc apiexplorer microsoft aspnetcore mvc cors microsoft aspnetcore mvc dataannotations microsoft aspnetcore mvc formatters json microsoft aspnetcore mvc formatters xml microsoft aspnetcore mvc localization microsoft aspnetcore mvc razor host microsoft aspnetcore mvc razor microsoft aspnetcore mvc taghelpers microsoft aspnetcore mvc viewfeatures microsoft aspnetcore mvc webapicompatshim step up your open source security game with whitesource | 0 |
21,272 | 6,996,248,680 | IssuesEvent | 2017-12-15 23:14:14 | hashicorp/packer | https://api.github.com/repos/hashicorp/packer | closed | Enhancement: Ability to continue long boot_command's from snapshots | builder/hyperv builder/parallels builder/vmware enhancement | Some VM's take a very long time to build, multiple hours. Testing tweaks to `boot_command` for such long builds is frustrating, because the developer won't know whether the tweak is successful or not until the entire build replays.
For Docker, builds have the benefit of separating the steps into distinct `RUN` commands, and Docker caches and replays from the last good `RUN`, so the development cycle of a Docker image is much faster. Once the whole image builds, the developer can cleanup multiple `RUN` commands into a single `RUN` for a correct, efficient build script.
Could packer get something like this, by leveraging the hypervisor's ability to record and replay snapshots? For example, packer could search for `<checkpoint>` markers along the `boot_command` when a build is about to be executed. The build could skip to the last reached `<checkpoint>`, load the snapshot, and continue executing keys from `boot_command` to save development time. Whenever a new `<checkpoint>` step is reached, packer records a snapshot. When a developer is happy with the whole build, then he can delete the `<checkpoint>` markers to cleanup, and optionally run `packer build` one more time to check his or her work.
Notes:
* Not sure which hypervisors support checkpoints, though at least VMware does. Other hypervisors could treat `<checkpoint>` as a NOP.
* One thing that would probably have to change in order to support this snapshot integration is that `packer build` would have to become better at reusing artifacts. It would do no good to record snapshots, if the next `packer build` execution discards the previous build's artifacts. | 3.0 | Enhancement: Ability to continue long boot_command's from snapshots - Some VM's take a very long time to build, multiple hours. Testing tweaks to `boot_command` for such long builds is frustrating, because the developer won't know whether the tweak is successful or not until the entire build replays.
For Docker, builds have the benefit of separating the steps into distinct `RUN` commands, and Docker caches and replays from the last good `RUN`, so the development cycle of a Docker image is much faster. Once the whole image builds, the developer can cleanup multiple `RUN` commands into a single `RUN` for a correct, efficient build script.
Could packer get something like this, by leveraging the hypervisor's ability to record and replay snapshots? For example, packer could search for `<checkpoint>` markers along the `boot_command` when a build is about to be executed. The build could skip to the last reached `<checkpoint>`, load the snapshot, and continue executing keys from `boot_command` to save development time. Whenever a new `<checkpoint>` step is reached, packer records a snapshot. When a developer is happy with the whole build, then he can delete the `<checkpoint>` markers to cleanup, and optionally run `packer build` one more time to check his or her work.
Notes:
* Not sure which hypervisors support checkpoints, though at least VMware does. Other hypervisors could treat `<checkpoint>` as a NOP.
* One thing that would probably have to change in order to support this snapshot integration is that `packer build` would have to become better at reusing artifacts. It would do no good to record snapshots, if the next `packer build` execution discards the previous build's artifacts. | non_test | enhancement ability to continue long boot command s from snapshots some vm s take a very long time to build multiple hours testing tweaks to boot command for such long builds is frustrating because the developer won t know whether the tweak is successful or not until the entire build replays for docker builds have the benefit of separating the steps into distinct run commands and docker caches and replays from the last good run so the development cycle of a docker image is much faster once the whole image builds the developer can cleanup multiple run commands into a single run for a correct efficient build script could packer get something like this by leveraging the hypervisor s ability to record and replay snapshots for example packer could search for markers along the boot command when a build is about to be executed the build could skip to the last reached load the snapshot and continue executing keys from boot command to save development time whenever a new step is reached packer records a snapshot when a developer is happy with the whole build then he can delete the markers to cleanup and optionally run packer build one more time to check his or her work notes not sure which hypervisors support checkpoints though at least vmware does other hypervisors could treat as a nop one thing that would probably have to change in order to support this snapshot integration is that packer build would have to become better at reusing artifacts it would do no good to record snapshots if the next packer build execution discards the previous build s artifacts | 0 |
1,545 | 2,546,608,680 | IssuesEvent | 2015-01-30 01:45:11 | mozilla/webmaker-app | https://api.github.com/repos/mozilla/webmaker-app | closed | Improve design of "Community Announcement" template | design: needs visual design | * Replace photo with illustration
* Improve typography
Any ideas to make this more interactive/exciting? | 2.0 | Improve design of "Community Announcement" template - * Replace photo with illustration
* Improve typography
Any ideas to make this more interactive/exciting? | non_test | improve design of community announcement template replace photo with illustration improve typography any ideas to make this more interactive exciting | 0 |
344,399 | 30,743,673,128 | IssuesEvent | 2023-07-28 13:28:57 | Azure/azure-sdk-for-net | https://api.github.com/repos/Azure/azure-sdk-for-net | closed | [FormRecognizer]GetAndListOperations(True) failing in nightly runs | Client needs-team-triage Cognitive - Form Recognizer test-reliability | FormRecognizer nightly test runs are failing with:
> Error message
> System.AggregateException : One or more errors occurred. (An unexpected error occurred.
> Status: 500 (Internal Server Error)
> ErrorCode: InternalServerError
>
>
> Content:
> {
> "error": {
> "code": "InternalServerError",
> "message": "An unexpected error occurred."
> }
> }
>
>
> Headers:
> Transfer-Encoding: chunked
> x-envoy-upstream-service-time: 674
> apim-request-id: 9dbccf2e-c224-4d5a-832f-d8efd3b598a2
> Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
> X-Content-Type-Options: nosniff
> x-ms-region: REDACTED
> Date: Fri, 28 Jul 2023 04:40:42 GMT
> Content-Type: application/json
> )
> ----> Azure.RequestFailedException : An unexpected error occurred.
> Status: 500 (Internal Server Error)
> ErrorCode: InternalServerError
>
>
> Content:
> {
> "error": {
> "code": "InternalServerError",
> "message": "An unexpected error occurred."
> }
> }
>
>
> Headers:
> Transfer-Encoding: chunked
> x-envoy-upstream-service-time: 674
> apim-request-id: 9dbccf2e-c224-4d5a-832f-d8efd3b598a2
> Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
> X-Content-Type-Options: nosniff
> x-ms-region: REDACTED
> Date: Fri, 28 Jul 2023 04:40:42 GMT
> Content-Type: application/json
>
>
>
> Stack trace
> at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
> at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
> at Azure.AI.FormRecognizer.DocumentAnalysis.Tests.MiscellaneousOperationsLiveTests.GetAndListOperations(Boolean useTokenCredential) in D:\a\_work\1\s\sdk\formrecognizer\Azure.AI.FormRecognizer\tests\DocumentModelAdministrationClient\MiscellaneousOperationsLiveTests.cs:line 59
> at Azure.AI.FormRecognizer.DocumentAnalysis.Tests.MiscellaneousOperationsLiveTests.GetAndListOperations(Boolean useTokenCredential) in D:\a\_work\1\s\sdk\formrecognizer\Azure.AI.FormRecognizer\tests\DocumentModelAdministrationClient\MiscellaneousOperationsLiveTests.cs:line 66
> at NUnit.Framework.Internal.TaskAwaitAdapter.GenericAdapter`1.GetResult()
> at NUnit.Framework.Internal.AsyncToSyncAdapter.Await(Func`1 invoke)
> at NUnit.Framework.Internal.Commands.TestMethodCommand.RunTestMethod(TestExecutionContext context)
> at NUnit.Framework.Internal.Commands.TestMethodCommand.Execute(TestExecutionContext context)
> at NUnit.Framework.Internal.Commands.BeforeAndAfterTestCommand.<>c__DisplayClass1_0.<Execute>b__0()
> at NUnit.Framework.Internal.Commands.BeforeAndAfterTestCommand.RunTestMethodInThreadAbortSafeZone(TestExecutionContext context, Action action)
> --RequestFailedException
> at Azure.AI.FormRecognizer.DocumentAnalysis.DocumentAnalysisRestClient.MiscellaneousListOperationsNextPage(String nextLink, CancellationToken cancellationToken) in D:\a\_work\1\s\sdk\formrecognizer\Azure.AI.FormRecognizer\src\Generated\DocumentAnalysisRestClient.cs:line 1752
> at Azure.AI.FormRecognizer.DocumentAnalysis.DocumentModelAdministrationClient.<>c__DisplayClass34_0.<GetOperations>g__NextPageFunc|1(String nextLink, Nullable`1 pageSizeHint) in D:\a\_work\1\s\sdk\formrecognizer\Azure.AI.FormRecognizer\src\DocumentModelAdministrationClient.cs:line 1257
> at Azure.Core.PageableHelpers.FuncPageable`1.AsPages(String continuationToken, Nullable`1 pageSizeHint)+MoveNext() in /_/microsoft.azure.autorest.csharp/3.0.0-beta.20230726.2/content/Generator.Shared/PageableHelpers.cs:line 158
> at Azure.Core.TestFramework.UseSyncMethodsInterceptor.SyncPageableWrapper`1.AsPages(String continuationToken, Nullable`1 pageSizeHint)+MoveNext() in D:\a\_work\1\s\sdk\core\Azure.Core.TestFramework\src\Instrumentation\UseSyncMethodsInterceptor.cs:line 263
> at Azure.Core.TestFramework.UseSyncMethodsInterceptor.SyncPageableWrapper`1.AsPages(String continuationToken, Nullable`1 pageSizeHint)+System.Threading.Tasks.Sources.IValueTaskSource<System.Boolean>.GetResult()
> at Azure.Core.TestFramework.DiagnosticScopeValidatingInterceptor.DiagnosticScopeValidatingAsyncEnumerable`1.<>c__DisplayClass6_0.<<AsPages>b__0>d.MoveNext() in D:\a\_work\1\s\sdk\core\Azure.Core.TestFramework\src\Instrumentation\DiagnosticScopeValidatingInterceptor.cs:line 304
> --- End of stack trace from previous location ---
> at Azure.Core.TestFramework.DiagnosticScopeValidatingInterceptor.ValidateDiagnosticScope[T](Func`1 action, MethodInfo methodInfo, String source) in D:\a\_work\1\s\sdk\core\Azure.Core.TestFramework\src\Instrumentation\DiagnosticScopeValidatingInterceptor.cs:line 201
> at Azure.Core.TestFramework.DiagnosticScopeValidatingInterceptor.DiagnosticScopeValidatingAsyncEnumerable`1.AsPages(String continuationToken, Nullable`1 pageSizeHint)+MoveNext() in D:\a\_work\1\s\sdk\core\Azure.Core.TestFramework\src\Instrumentation\DiagnosticScopeValidatingInterceptor.cs:line 302
> at Azure.Core.TestFramework.DiagnosticScopeValidatingInterceptor.DiagnosticScopeValidatingAsyncEnumerable`1.AsPages(String continuationToken, Nullable`1 pageSizeHint)+MoveNext() in D:\a\_work\1\s\sdk\core\Azure.Core.TestFramework\src\Instrumentation\DiagnosticScopeValidatingInterceptor.cs:line 302
> at Azure.Core.TestFramework.DiagnosticScopeValidatingInterceptor.DiagnosticScopeValidatingAsyncEnumerable`1.AsPages(String continuationToken,
For more details check here:
- https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2955729&view=results
@jsquire for notification. | 1.0 | [FormRecognizer]GetAndListOperations(True) failing in nightly runs - FormRecognizer nightly test runs are failing with:
> Error message
> System.AggregateException : One or more errors occurred. (An unexpected error occurred.
> Status: 500 (Internal Server Error)
> ErrorCode: InternalServerError
>
>
> Content:
> {
> "error": {
> "code": "InternalServerError",
> "message": "An unexpected error occurred."
> }
> }
>
>
> Headers:
> Transfer-Encoding: chunked
> x-envoy-upstream-service-time: 674
> apim-request-id: 9dbccf2e-c224-4d5a-832f-d8efd3b598a2
> Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
> X-Content-Type-Options: nosniff
> x-ms-region: REDACTED
> Date: Fri, 28 Jul 2023 04:40:42 GMT
> Content-Type: application/json
> )
> ----> Azure.RequestFailedException : An unexpected error occurred.
> Status: 500 (Internal Server Error)
> ErrorCode: InternalServerError
>
>
> Content:
> {
> "error": {
> "code": "InternalServerError",
> "message": "An unexpected error occurred."
> }
> }
>
>
> Headers:
> Transfer-Encoding: chunked
> x-envoy-upstream-service-time: 674
> apim-request-id: 9dbccf2e-c224-4d5a-832f-d8efd3b598a2
> Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
> X-Content-Type-Options: nosniff
> x-ms-region: REDACTED
> Date: Fri, 28 Jul 2023 04:40:42 GMT
> Content-Type: application/json
>
>
>
> Stack trace
> at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
> at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
> at Azure.AI.FormRecognizer.DocumentAnalysis.Tests.MiscellaneousOperationsLiveTests.GetAndListOperations(Boolean useTokenCredential) in D:\a\_work\1\s\sdk\formrecognizer\Azure.AI.FormRecognizer\tests\DocumentModelAdministrationClient\MiscellaneousOperationsLiveTests.cs:line 59
> at Azure.AI.FormRecognizer.DocumentAnalysis.Tests.MiscellaneousOperationsLiveTests.GetAndListOperations(Boolean useTokenCredential) in D:\a\_work\1\s\sdk\formrecognizer\Azure.AI.FormRecognizer\tests\DocumentModelAdministrationClient\MiscellaneousOperationsLiveTests.cs:line 66
> at NUnit.Framework.Internal.TaskAwaitAdapter.GenericAdapter`1.GetResult()
> at NUnit.Framework.Internal.AsyncToSyncAdapter.Await(Func`1 invoke)
> at NUnit.Framework.Internal.Commands.TestMethodCommand.RunTestMethod(TestExecutionContext context)
> at NUnit.Framework.Internal.Commands.TestMethodCommand.Execute(TestExecutionContext context)
> at NUnit.Framework.Internal.Commands.BeforeAndAfterTestCommand.<>c__DisplayClass1_0.<Execute>b__0()
> at NUnit.Framework.Internal.Commands.BeforeAndAfterTestCommand.RunTestMethodInThreadAbortSafeZone(TestExecutionContext context, Action action)
> --RequestFailedException
> at Azure.AI.FormRecognizer.DocumentAnalysis.DocumentAnalysisRestClient.MiscellaneousListOperationsNextPage(String nextLink, CancellationToken cancellationToken) in D:\a\_work\1\s\sdk\formrecognizer\Azure.AI.FormRecognizer\src\Generated\DocumentAnalysisRestClient.cs:line 1752
> at Azure.AI.FormRecognizer.DocumentAnalysis.DocumentModelAdministrationClient.<>c__DisplayClass34_0.<GetOperations>g__NextPageFunc|1(String nextLink, Nullable`1 pageSizeHint) in D:\a\_work\1\s\sdk\formrecognizer\Azure.AI.FormRecognizer\src\DocumentModelAdministrationClient.cs:line 1257
> at Azure.Core.PageableHelpers.FuncPageable`1.AsPages(String continuationToken, Nullable`1 pageSizeHint)+MoveNext() in /_/microsoft.azure.autorest.csharp/3.0.0-beta.20230726.2/content/Generator.Shared/PageableHelpers.cs:line 158
> at Azure.Core.TestFramework.UseSyncMethodsInterceptor.SyncPageableWrapper`1.AsPages(String continuationToken, Nullable`1 pageSizeHint)+MoveNext() in D:\a\_work\1\s\sdk\core\Azure.Core.TestFramework\src\Instrumentation\UseSyncMethodsInterceptor.cs:line 263
> at Azure.Core.TestFramework.UseSyncMethodsInterceptor.SyncPageableWrapper`1.AsPages(String continuationToken, Nullable`1 pageSizeHint)+System.Threading.Tasks.Sources.IValueTaskSource<System.Boolean>.GetResult()
> at Azure.Core.TestFramework.DiagnosticScopeValidatingInterceptor.DiagnosticScopeValidatingAsyncEnumerable`1.<>c__DisplayClass6_0.<<AsPages>b__0>d.MoveNext() in D:\a\_work\1\s\sdk\core\Azure.Core.TestFramework\src\Instrumentation\DiagnosticScopeValidatingInterceptor.cs:line 304
> --- End of stack trace from previous location ---
> at Azure.Core.TestFramework.DiagnosticScopeValidatingInterceptor.ValidateDiagnosticScope[T](Func`1 action, MethodInfo methodInfo, String source) in D:\a\_work\1\s\sdk\core\Azure.Core.TestFramework\src\Instrumentation\DiagnosticScopeValidatingInterceptor.cs:line 201
> at Azure.Core.TestFramework.DiagnosticScopeValidatingInterceptor.DiagnosticScopeValidatingAsyncEnumerable`1.AsPages(String continuationToken, Nullable`1 pageSizeHint)+MoveNext() in D:\a\_work\1\s\sdk\core\Azure.Core.TestFramework\src\Instrumentation\DiagnosticScopeValidatingInterceptor.cs:line 302
> at Azure.Core.TestFramework.DiagnosticScopeValidatingInterceptor.DiagnosticScopeValidatingAsyncEnumerable`1.AsPages(String continuationToken, Nullable`1 pageSizeHint)+MoveNext() in D:\a\_work\1\s\sdk\core\Azure.Core.TestFramework\src\Instrumentation\DiagnosticScopeValidatingInterceptor.cs:line 302
> at Azure.Core.TestFramework.DiagnosticScopeValidatingInterceptor.DiagnosticScopeValidatingAsyncEnumerable`1.AsPages(String continuationToken,
For more details check here:
- https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2955729&view=results
@jsquire for notification. | test | getandlistoperations true failing in nightly runs formrecognizer nightly test runs are failing with error message system aggregateexception one or more errors occurred an unexpected error occurred status internal server error errorcode internalservererror content error code internalservererror message an unexpected error occurred headers transfer encoding chunked x envoy upstream service time apim request id strict transport security max age includesubdomains preload x content type options nosniff x ms region redacted date fri jul gmt content type application json azure requestfailedexception an unexpected error occurred status internal server error errorcode internalservererror content error code internalservererror message an unexpected error occurred headers transfer encoding chunked x envoy upstream service time apim request id strict transport security max age includesubdomains preload x content type options nosniff x ms region redacted date fri jul gmt content type application json stack trace at system threading tasks task throwifexceptional boolean includetaskcanceledexceptions at system threading tasks task getresultcore boolean waitcompletionnotification at azure ai formrecognizer documentanalysis tests miscellaneousoperationslivetests getandlistoperations boolean usetokencredential in d a work s sdk formrecognizer azure ai formrecognizer tests documentmodeladministrationclient miscellaneousoperationslivetests cs line at azure ai formrecognizer documentanalysis tests miscellaneousoperationslivetests getandlistoperations boolean usetokencredential in d a work s sdk formrecognizer azure ai formrecognizer tests documentmodeladministrationclient miscellaneousoperationslivetests cs line at nunit framework internal taskawaitadapter genericadapter getresult at nunit framework internal asynctosyncadapter await func invoke at nunit framework internal commands testmethodcommand runtestmethod testexecutioncontext context at nunit framework internal commands testmethodcommand execute testexecutioncontext context at nunit framework internal commands beforeandaftertestcommand c b at nunit framework internal commands beforeandaftertestcommand runtestmethodinthreadabortsafezone testexecutioncontext context action action requestfailedexception at azure ai formrecognizer documentanalysis documentanalysisrestclient miscellaneouslistoperationsnextpage string nextlink cancellationtoken cancellationtoken in d a work s sdk formrecognizer azure ai formrecognizer src generated documentanalysisrestclient cs line at azure ai formrecognizer documentanalysis documentmodeladministrationclient c g nextpagefunc string nextlink nullable pagesizehint in d a work s sdk formrecognizer azure ai formrecognizer src documentmodeladministrationclient cs line at azure core pageablehelpers funcpageable aspages string continuationtoken nullable pagesizehint movenext in microsoft azure autorest csharp beta content generator shared pageablehelpers cs line at azure core testframework usesyncmethodsinterceptor syncpageablewrapper aspages string continuationtoken nullable pagesizehint movenext in d a work s sdk core azure core testframework src instrumentation usesyncmethodsinterceptor cs line at azure core testframework usesyncmethodsinterceptor syncpageablewrapper aspages string continuationtoken nullable pagesizehint system threading tasks sources ivaluetasksource getresult at azure core testframework diagnosticscopevalidatinginterceptor diagnosticscopevalidatingasyncenumerable c b d movenext in d a work s sdk core azure core testframework src instrumentation diagnosticscopevalidatinginterceptor cs line end of stack trace from previous location at azure core testframework diagnosticscopevalidatinginterceptor validatediagnosticscope func action methodinfo methodinfo string source in d a work s sdk core azure core testframework src instrumentation diagnosticscopevalidatinginterceptor cs line at azure core testframework diagnosticscopevalidatinginterceptor diagnosticscopevalidatingasyncenumerable aspages string continuationtoken nullable pagesizehint movenext in d a work s sdk core azure core testframework src instrumentation diagnosticscopevalidatinginterceptor cs line at azure core testframework diagnosticscopevalidatinginterceptor diagnosticscopevalidatingasyncenumerable aspages string continuationtoken nullable pagesizehint movenext in d a work s sdk core azure core testframework src instrumentation diagnosticscopevalidatinginterceptor cs line at azure core testframework diagnosticscopevalidatinginterceptor diagnosticscopevalidatingasyncenumerable aspages string continuationtoken for more details check here jsquire for notification | 1 |
30,534 | 4,210,176,919 | IssuesEvent | 2016-06-29 08:59:58 | pythonapis/6ZJYP2PXGY5CWP2LWTZZFRIL | https://api.github.com/repos/pythonapis/6ZJYP2PXGY5CWP2LWTZZFRIL | closed | dFjzBjEiCJ31hU0SosIsyRHh3aUtblHOd0KFapHhpXlNq8gads/CqSbMVIvzYRP3zDwD10U/9gnG6FoRm/BaeytvEvx/pQDw7bz22ZM2lkJeYwYL0/dmqKnMHXRvTMdHwHO0jbufaNgKMCKjSmAjR9QMuCnP+MsiKpajrMdAV6g= | design | GVKgHfyc93HCOf1omgEWXEvZXNprIxLtKZpzdKAId81de4YsD9udOlJvuJT1+6aZMpr2wPqdUb1zjtNid7SIlakOWhc5CKQ4oyZt2j9OtQDOH1TzMfJ9MUvBpOkfL1KU+8WBSFVDLKq56sE50bfXdqLHnxcm88ciw/CZDU7N/wbGeFWGnwXKslizrcQUWKTym4Feff2vdTbU7QjxtU2s/qnQ7W3fiDvQQuED+YaTQ19AY6BecoPXGOD1rKO294UvJHIwUdgvsWRPmZW2WCbB8/8X0XrxF0e6KOoaXwh4dagRqvfLZBBtMD/jE2ntPP+vqVSPTHqqFgL/HnNUu+qxnPv4T+lVrz+h4TvjDmImaLMmSHKIlFp66DOgQpByavcUKnoPEKTDMgYt7KN1ApOz70+5ApeD37od5jKL4zDAX1+SBJAb0fgR45h1wPYmQ6auWeedsM3BMDowzr+RaxpW9DctE9anJVH7kby7mFKG5XHr5ZcSYCzEOC/ygVGPLfai9P23Xv+z+RcYbUsvwJIeb51cWtfJi1joxM3qdOgp71mL6RZgNSbSr0DJeWZU1sboC3uHDr3gFTA3UcpRfr1m2IHBcbFEijYl76E0rvBN3LHeEe4NbHc6dnoss/cojsXxdMCVb76uQScYcV8M8Md/4Tq6Z+49Ju0iEHsqwOLJZPeG/1oy4E35KPPDfRj0He/ep9UzUU/QfbNmUsmFAxRECbdL9i93009By90+ZBOt3pTOksCujsPTVXT5VfW0saSUwTOsvsphoA/dddxth/KQXaOLbpNwDnFpLsqm17Xp099IL8NcFoDRBL6gsOimibERCLNWOjT2crvPQ5evrPE203fF65DrajkWJ0X2tkwpyxBP9p4NteRN+gww+IpOBG6Ex07YzAeC8UhstBS7VkK0uuu+c4DQ9820AUfIlLba7JjTVCJ1EYxGfMaB/N487ZNQlRQRoWmo8QAW2SjQsTevEvgh7VLPG3ROy6Mc8zbAdIvdGTqx2gP9XPM2l7NcttSY4YDopHsHzIQNcaLVE3bHv1PDpU04AddJqggBLnMuX7UwIlgkFUOCQVa1e5RkGMUjqiUM/S8XpDd+2oUXjunYsn+ETsyxGVK9gpzSTVfJSvF1wc0Eou+iv1ZLjlxjXsRO5//1z+Ym9sA0W7a4WutX+tSemtbeAwSRihegJFWdDUpiPxRoxqlA5oUYy8PmlFdmxyQZ6WBaGHHV5dvgp8S0om86UTEbgEqK4lwwPgZjaRc6PBycHzfgNYkjFr/0gI6cTMY5bAIx/8YAgaeQRRQo0m71Lo3OR7F8uPLzWcqCA2ESlOpUa97Ar2OVkINyEW4S8ZVCnqCcDZPrutSfWOX1aGoO98NAvaBT80cBQYZbGX74gnIbZDLIFZzP6kbMXEpctBPqMfU2RzPu5NXCaKDEebNAoXxdvrg7o4f9QGGO8KRQAzyt4yqzKtklclDQFD+n10Wm0/rKMMUfK3ub5tx+jujU7SUbEEsAuPLfwI2K+goUKYOAiwLGji3Mf3eUjcEdHe2TYqCsBKmvzBqusyCKqlOOOhjP7hmW5PMG0FcItD6QzBSL0zkbxg/us5UIuzZgribG9TJq6VqtfQrhJWAr2Fmg6Qqyc+nb3PLHkh/YXs3RtsCvUmQKxXe3cKkVNvbMjqdwAoZv+N/PUGNjdG8aprc1rPb2QkLqxQMkQIuAUT3ZRnKGu/1wTrskGLgDSS4I6WO6wlNLhJe1STcNipyqZWBWCVhQBBnBouL9NT04bbr7vKua/vRF0h2GjbJmo/8SvmA02WzPmUmaYrVf9Y3eHkv206fFeNMYpZKKzYXMrUsLiL3awU9b/rwkkFW/tJSMUr2wyBKAjPDP9hUwnZQDln+fS+0fwZzELf7JrxfjXKBcw/GXwGD1x0b3Sbn/q46nHaN9U6xRKezycCylXoV5mmODKhL3ow9vDhTc0sgFH36DiGW2Iaz37Q+umL6oJ3zCGlY54WlOLbdRBfJMwPvoP7qBh+Ket7obH5m+SGZqzCqJSsKfzpy28qDDJ6DurLATUHD4XMMjPN1LG+vCgwYmEhDAaJyRaiwUE3ku81C4U8deNOhEMuBYNYwEoXwdws7z0eV/o1OpVrqCpPEC40cAkMDrMN+t1zIwrkWrqum+8YhT4qMh6giV97aewbbdPiRRAtarzsWhvWjB2KQOxjBxBtgCkakvnnFK7MPozuApv1BKO+mW7kvLYYhh39QaeQpLXIsNtdWaMq0pA6Jjn72nkr4xUwoxvtN6HbKzs8sEQzedyYiZwk5gbTZFyKX8OKy7HL8zBovMZYgPxItgXkXSkLYXhem04UiK/MpNMAjXfZxdTConvdgFWCaD/yhyNLbwn+wNW/FJEdr1J2fqIwZDwxbgzEUs9kxIEigoytq364AwqSPp5spEAxWzONG5N7J2LopEEQOpLQdEqu6Pyr3cvSUMF0F11vhRFLz9UgqCjfXNntHz1e0qPkb9arEzvSHAZX+3UAwAhgISPrJytDSoI8GDozvvfiN7wBLC6aezZM0NPE1IWQIVPE01jp0GP5QNO5S5vfOub9VOBWX5WqANuHdWchVH71zTtjakSx8UY4vdEQ2yFQJ3rJRjYDAGxYAoaUsSSy+crVfnFuO8i+k5bOGfe4a1IVZL2/oxEK+lm3XthXtrhhVvNE8omdqJqGZ33CiyJPm6/z8rNiCiUCvGYrJTaLPhOIGfRJD8SayXpt4uj2jmjBirFp2/9ECjP6AhnpFueJwhOdjOq9z8flypx9/sZ0HlFmuK/XqFRKnvkPfoh48oqZn2pb15GWZuv6XQuNiQV7CPHu0PTdkuohZ1En/+iynpsgh730iw0DUCDRFOPHJq/Iipu5SBVoRkjIfCvba3OFPsQAbrBxt5/GZ8ryJ71wEcJbtTq7RAk6z2NmzIjNHczcjQcobWJZaA3GzJg6lk1OorZSCR+tm9+zFJ6uGleeVEfV/BaxUtkIt08BeaLLF8TrVr+4kNrzXJOEA29EdoATkblmB8rz30ptMn4ALWq87Fob1owdikDsYwcQanjjENMlR5XBb8Q01TiT1RGqe2/jxeshoFjVnAkY5kYTMWNUjJHZ9JPBKgl1JJyF+hxm3kSK3qqnHAHWxMOsXmm+vMuWexgQ87Fi4hxCw8adZEHB2ES4BRChFT0I9By7FDFsejIX7pX3X1xvoV4UdyIrvPxDgH7j/FPhYUEncIXVz8grithd0m2F7GXoZqz6MjZHdTADwf9FrtBwljxNMskVbujHAVTFQG6dPcHA9b7BYGeKc3F0zujgBf+aaB/hXjY4I8PXOMDWt0DAE0TM2lazc5i1WizPvCBQr1E/iqwTq1OoEqSKdlGPonR1w6W1JkV1DX/842TX72gbtIFsaOmwBWzaGSdJs7bjso5nXU1IxFiGymctssrn0ksKBTS1GIKLsYD/c3UNCBqMO+roxXxadfm85aCrYAfK+J5cK0iGwX12zUEiAcVbq/rWmbv/qgTaaB+U0GCQu8bc4VPTsEuSXFM/S9XItW+et0fkV/7aIhXyyRv8pFBGnCZdeQJwXGAAS41UxdFJUzukIFGim16HyOutaCw2FRmk9PTc8reJmTepN1S9ZntFslA9eSvwrkHp3SmSKKMNU/at6jBaVcbzWQwcwwQwWApJhr3j9uRiuQ0OVQceDSl9GyBnrGrZWtOC9vOZT/p5/wfnbQNCTyoqufY4MC1nQulA122NsQMAL4Jz4E/oclzny1fDO5pQwgDyJe9i6ivbhQ4P8mNG2TIczTRBfI82rOLDeHVqOvGlipKOM/ohwsZ6ORUPPxaonYsByWT1gro1rS4l6U+n0bF0YAqljX7WzKQkMKtH8jb7B2zEWN71+BhJLzlnHxyF/+QqBraUo9AjDkLiEo40XPAuCrGTTO4bfcY2cMzlvCARztLX5mjln4rSETGQyIzzjOyCIGb8BcEqYhijZUeiiQaE8lfIeCyLYAtLW51LK2+RQPmGSCpRg8EEA7sbiy5EOHX+3gVOrqL/VmU866boXzMqJmURUmPxdWHzTIQoHE8NHxzl6SVP9zcDgPhF1VXhyb7lH9srsvURwDA1p/gAXZAGXDung74BCQickXqGcOlzKiZlEVJj8XVh80yEKBxPCq72VT4MHE7ZcOnUnwx6I7KHE59z93N3EMZJgI9dJuPAFTDovFU9+vGtsZqtAFYZ1mdACLcoexUEjJvaM0HwToQyUZvCYPGZdAgj63Nsy3Qr5qVZdXJmIxp/KoTtoc0QJ0RTgheyvgINe0qN/SaEWxke+M0StrTiThkmfzsUJr3NoWMdOrMuP0Y/of2wO5VKJIYUAN8m/If9ndCGRBm9gDq6Gr4EJKs81GhGh4ykXyUhthoWBOThp+Aa+jq7GA0ZPq+TMBGvNc12TUVJh9MUvaXO6WegWzfuTsKN8R7vnmX2EoXs2DCIJ57TsVqVh9uBtuyRiBmFaLrwcFVsFK70Yk2NHiYtfSY5EEpM9ewsD4ujR3tFCosnBv66/W54D+95tasP4B0lzhBO+UYemoPhoyh+Uj3MRNTGNsKKAdASfHujVbt7wThf1EOLq4j5oDh0QHDeso6cGb7DExdhP90P1V0vK803BQTKyb8u2tQI1KWlNy/pxVJsD8eohnfckgs6+hmmifrIK7kHR7f5/C9XYVm772v+3UxymluBHzwWciiE8eYmX2/U2wu6e8MUlR+Xh7kcIDH6mrkMspVWJIcH+UeywSr+PCjhHLsJWfOLMtGQTHf5/b0RSC84K0GKqc0/uM8fcFd+otoSKRsfhRxTrtGKlSKqU/hB5pbMG9Hf8QBuUTgPlPiGqILwKq3kJtEg4PJdP7lunPXHfOJEFzyZPYyW+8eb5OewPyFNJhTBwYGAiVOuJuFZ0b2ty+s0LyHePnrotuv/yZXgBmc2j0BzUQUNmSFxxkbk4svzIGplyynry2/dm5/6u3uv5zcJpoDktX/p/XF9j+QSEo2Nk+lCPve6FeNB9KjDQAFBjpZOLFzdS5fQLSpCmw60USsg+IHHAuDcR6glaaRm5AHxnARpNxgMbIOVBXt2DBGCtDmAK123WrruVE+wQYdo4cTsw5p/mad6PQo9tbYevz3UwPNsW/xz8B8zckjUASeEsPkWZAiwX514LnIx1WHh2g5cyPBUj3wu9P86OHwybpfTxJQYF5eRRI7bIRgsfbV5KnDzkkrGIdiC0Qh39/LCJszfPn7xGVJ2xgQJs0q6V7AEluv/2qam6daIoMThzWgzgNH02aocAuKLmuVDiEKFP54xmAWnQTunwK6UJALpREMvWTeCgR5Fzkf9l8PZoOAkD4aeehKTYyOykzzKcfJW3n+WL5RDJwuJ98kiCHluA1uQC0ha/ZAtyWhvWB3blQYHH+casFw4P4cx5ncUWMkHrYAPVzeluGm6dRhy+vGdrcilrmDF4wkIrGQqKxZ0W6WEDADGUNKAF6xCXRRLtABt1pXT8sF2jjcdAescTj4ZT5Km9DEZUDYGTVgGKnBEK6II+L+fGjHAZBCd7+Ux+3sXdZbOAVLbi4cYjAw5+wmHIGV5qvoe9K9qfUb9AalQEUy4FvgTbpcbry38rSygjS3RNWhy9hboLEhoGvAYCMpz87+Uh0+vVSapvVNtBIIkLTfRzHjBd38xd9RCIOrgQGkrYF2wi4D3y/7kFjhoWpo3shssa9aM42+UqhTpjg56nLn0vCfpw4ei5pN6Yq8ffJGZzlAVfSD+gNL8DYkTtzg2QGQ7kGKiyBg9qh/B5hob6kOm29HFupgKdIYgCUlYsiUyQ3PomkN/zmSOpUFFgDO3Vns6KY5n93jljHvYI6Lx9Q+V7LxMGNJVmpvym5CAghAAVVWLeGQ2XSrTjvFqF88yo/LgJbMjjB6MMI6hi6ht5OlHURp1VW4rp365sDaP2QZvBqm55dis6fB5Xy2i64BXenMKoOr215qqDPMcrEbMZYJKVvnnA2do4NsiCs9qG4JlgKpB9Py4zWqASU3SEN5GnKrjvT00HHZpfZhDcRnDfTw5ccD0sZzPJFjFnGm2wmAQkaizc+1+t4b6gBuQGhEvbyEcvbZzLY0SZRxt9UJD6qq/17T8HHWexU+EXcM4rZqJ0qTrzCcqDvscMSOy7lInpyQu8aEuOgf0n1gNLbkoieKe58YxE7oF+yk6EgsVBQz66Gap5U3TCEKhgN2iS3vKsaz8ix9dllnbZY8N9qKYv/IQYrYonXhL05oqT4vITWjCUDE48NG5oTRnfJOU9S7JDgoaWgzK5oF/WP+3pA0CZfyuatMTOgqvmS9GbyPEVKfpYk30F8LF6CGMnLLFlXETAuB4F2EGCm21dIY0Ed8PKEnG63kpH2nRp9ibXbLUR5XhETcuw7IQrehopn/R/78jng1gmmhZ23lsspe2F8KEUX5TBkUxHhLNoewgnNDhZzU9TY0ZSV5pE29nB84tABZMCJjagUg0kaMs6JVZWZ9QQeUIoTaob1d6t8am9AMEq5NCZ2r9u7qp6M4LjpamtYz7o64qGwsnBpn2yib9IoILXbQwFlQ5LIJhR8zgFMUtMqeI+DtLYmcJQAbrCly39imLbrOLh/1ITZWEs4/fwIouY2cgpXfrcCnrFu5lm8S0V4Bms2xZyZXSM7T4cLKJCtUi35Vq7SKRx2JpZjEubG2g+MmX7cNYeimaEV38lIVQmcO89J+oStz2cNwMQS3jATqCIJ4NFzNo8yZnQAi3KHsVBIyb2jNB8E6CPhR6GOyP0oCXw+u+0Vr1w5s/O3O55cDuPzm/lWnTz1V8jPEzzPHHlKytC1yb6CYNOQHCEW1EUIM0Qju3lVg+JyuL3PTxIB3RvYSq/k/NS8w2MS6Mgq1wAWKxzhpy6PP0YP38eAQzVqglFUjt/6nDVWX2ZI0RxjjafMAbEl1IdG77eMP7JOzLG6qJK87o1SYGJ53QMJsJFJw8BB6y5WUzaeeMAxxt2CwI/apC46EjLdkmF+ot2Cw8rCq8R8ULGhFPhGJSfYWwHVrKk+dqDaHKiut7Js7yuryP8YwCdFl1nR8kWMWcabbCYBCRqLNz7X69BxTFcYS+XauODCCwQ0+guAx3CLhAdhWx43xbhjMc1uyuNj2zMk8Z6geJR/sL7ebWYyvtwuLoJoZfAUAQPHONKgbebHpzaoPTcSAbmkfgdLxUej86ehDLks5xBDwT+cycoUBIVevqqs72+krIXKtmdog7zU7ptVX/e2eE0l9W3tbl5934dvVj1H/qMc9ev7SbKTCC9VXoHwQNrVgNJ3ryFQQgNhJJcD5ksTvVLsaDR2+i0CYApbVY7dyXdyN0YnNPjo0bWLqDI81uOjOBPiFpz7SZnCHkf9uITvjRqJHRmj2uIt4QmDkzr73m3fDGY6IyYEhXyHx9spnyWQuHodFHuKwm68UV0AxeoiTuAVU/hcM2e6kiyrs5VEEOfimzBx0eEVd4jVbi296UJeQc4rCCHwZDH4vVHX+5g0EVd5ZBAQLs9HMnktcpwrIisS8jshElPUJjOWSn54l7T5JIBK/wlyQcA9SUbkKYKFP3aw0KyIMTpQQRc+STuY2ipW0FSQJF2f9qHwZMRZPwq39EqC3He6jhVxG24/ChrgDajkEQ+7PNBT1pADEGqNAdJfy9YTAxE+TTE0qNx3prx8bTdJpNje/4ixG+Ol+Yt9gNLqyJP2r9dzv1iJLvt1/PJxCSpkDKGwf0zZ4XZcJtzlaHerDtZU6daFsp9k8CLpjj1KKgZ2+Ba/n+aHe95WLz54VETdNi31hbd4by29uhv3ylpCgNh9UWgclc9oCTxv/fagZqkr+ovNalj3mLYMImMeQg8HfJ77izq+XXYDmzkCc2yQHN6pLELQ1JzngZgunV5egZy5Znu48I9N1LAeMQ7aKys8QFLIsyjvC8zJKyfuQgu2j5O6PjdTJYdlWTWnRbpClkiyiBtODWNIKax8Te9+GhAT9/1m9qenwvAH5N7TOhDtrFtW7t3vY9R00UPtKaEDHuLo5c7FTaIa7q3fLst+E17O1G9USU8tnZtK/h18cEZqmQF7CdCwhuG14nOd2wPgjmw//62foM2H72k2t5AwdfVte/au7xi2SPWMVX1vqTvGuZvC1C0dhA2zwlNafK5c8ASaarlgJ/oRs6A+1z8GtRbjW6BomJ5UC3IvBlj7gR4y1C1Tl/XSaidremBgofZY8ZfGMF+R+bD4PeCOEEKxnlczLG/uU1zzDZjrXsRKsx4L9EMorztyqik9gTSvnjs85N5Nof4HPXefoFIMAabCZNahR9ezrAlM4B07enpHlN8TSi1MgSlNu6JNLpAQkUFnKw16RZ37f/XTRos1wdnFbFfdjdPMqZYuXUsCGZcfoW3DOuoAe8+GSq4yqGBwAnayUKxUHVI8tZ8cZDMYhPP1c3Wt0UDplJUUi7c++pS0PJCZoK3E0KsZt2S1NtT0Scylo5FzJB0K83/7I2S52Q43DUe0WUicRXHBc2gPed8bf7ItwXNFM1LxJB/Fo/ovGJJz3u4YB86arpbhcIKBtZE23/eDL1mm5M8ppS5ffxW6cRYnrnfMXjZdNf3VfcHh4Zfd6UPTbEa9MZEBbT2FMD83t3yG4w6ZLufzQNgu+OOqr4wpwBwWDolE0ZCtY+rvFmXKGQCgwTYppmJXk7paLAT8ECi3AkP6RMWylMVgW9HGsowYp1v2eOqiVtorAucO+tZbEHauHKDMdNLAD7mCtLBJfd5baAT9FqlvDh5lqv3CDT1MFFT5T2Rs8mzxR/CXpLqLM33Qg1zzcL17dxZBYrWNsq5FppOPYYqtoJQLmQeS24gjVJorY2j7i2KumpvkA1q7Fsjxc5U10/eB0CwmDAnaBccgtHyVe6lhJz1goWNX/qNrZNfbOI2c7DvCdcx4Ulo47R5JjiUh5UYtRTQuji5kkez+tPdOftvTf3fiPnSQFapGpMMPW92wGkh2pQXaCz5MNWmc2bTRZBtDxfjuPHi0TBwseq++x3DTKHb2hLqEEmNWFFwPx6eDffpSopM14LwJdqgEhTt7IDyQhrwKFIkYw5656hoinzqWqhPyBahu4MWeeNtTS/obnzgZcxH5B9ylGFHLm2/a9HBtNqTrXYBFlQsLTfVJI0Tfeyl/50Y/o7NdVRyxvPkzmmdX629LpQFUZbH7pz62asIDZ40ndVYanc+ZsSnDmdZW5oiQvicMfL5rG1l3W56BrJ8prw+Npjjyiiy6mlcz65o4jr4+FE8vmEHVDdcmhhE568cmXbfOwDeh4NIcozk6hTRf7R37baSwTBL2ONHpDCdT97Uy6aQaYCb1IPM3ZL0e8fvbbzjyDPL6j866dMWYUW3ZXCEyP0U92RNG8rwPQUQiSIb20VjeTA8ptWBj84eNtgKByqqGe6d36qqZghWeBdOUGWa2OWWe9xIQ3j+qYt+Mac/wqGban+Dm8tDS/x0MbdBia9w9IMBXjSrkqeRiGMOhiumxOrBKtBza1/VYJF8M8uzmvOb0WSJ/vKqsVF0TXCR7cFEidEAOqc527sRDh+3vLBS0xHV2rqaw/O+nXR75p8iNEP09iu8Onatm7r7giks3J/pexN5B8vUR2QDLYjX4birZkcLbRZCi8c/Fg5Ep0tfksDTeA4sXIZsZzTMkTVzlxOrLXpmiYNo3VCKIpu42B93QtYRh/Eh5ERxBNwezw8XgDMm3WZa0pIhkPsBxXhkgSXEvy4IEiLhZM/FEMiEPpxvgTp1+NXAGcG4F2mKVm/NVtwSdssvWH4Fodw8u2EzXW65JwDS9dQTkBnePfKY+pYJdMTQHtunGgGl3nIiO5NpVsbwz+nGIae/2ikYhK7GcePO00uJDZvsR3RpjkClst8yz+5go+jGQaKw0VyraRgAYCzYNQXEt0CToyL1v6VRrBQlVdzhwU3UNn8rcKW4FRRkcnGY7ut2Foghz5i9Y9EIS3HQISuZw+NTK+rVOkb/62NpQ59EcurGqqupp7O0rNOs246+IDFiCErJAghF1r3+2wYKclTlIGzH/D0GQSRhRDUFBM+8ka9ynuzrzO8nhmmpoJYLz/VCb+Kqz7dOL05PaFL7vTj4BG0ZhfU0EHStZyzOKchcMhGqqEh0n7KqFxppB+apOq6LXp4trUF++XznN/Anb9DTDnd9aWQr84Xm/gvm8IFSbPdJBNE2+NuWbSA0RZnLFPsh1nBeP6G4w+E67AH9M/qS/yrAyIDBuyFFHYugarx20qbO9FWmxGXsWga50o0BM71scKs0PLiN58DBBnCd4f5pCuQE7jPsNmA4uhQ278CRxDBrrvnOA0PfNtAFHyJS22uyYroIAOtSYFH03sZyk8laxO8C1u9u6WJWcvF97QnCsNGZ5Fu5dJ4UERvkBCiA6PStBRU/d056IGymf3kT0Nh5NHpc7tdnYXlNQ2qffBlLlcU6zEjwHXwrh37lIyeHRI95jZKaCq5+R+a0ns3rTKAZ06OnwyHAEHKgdJJ24k+PoNcz2XrNpNPKqBirE3lxZIW0sIZ9K7X3psl8j1DTR0vY+gPRnVA4/6kvnOMkWPGfaB1/IHS6cYzKsxTUJ98925njQ1QL+/P5JgOfe74Ur8ghP9qtQ1tmm7vpxugw+wM4f/MNgaGFXHSWcarZr/EwiPNXQaH81p+R/pE9y7SLrwPe7n/mrBfkU0Pm/POQJjhqNVhxdfIuxCAHOCa8pYktQ8mBdCD7SRv4skKQU+PTbAQawuJ9wZumts5gmkXogoH/k0k3GuAVgBeTXMpFqZ6cIsndAieT7mXWSrEe4O/ReH0r8CGGspSssr/rA2/xpinV45GKZ/Ve2aDv3mCvXEbwdjAnQaL2SU6lrI7CzSuK/fqPVIDOeep4TORVgh4nntI9u507gx+TybNWbRbiBIcM0CHAdGn7SNNRNYQJyG7qEZk/mT3TL6TgF6AtLrIeKfHFk9sqwSXua2f8RT9tWPvhloMS0UdibQr4gLO5sNSvuGyBTULv3BeDI3cv9wikXz589GJpK713tPhUgLjQlU1kAYgL06MxZx6XyE0YrIhBJsRsARgtqF8YPoAo0g7DvQwRz2Me+HqfVAPBaQhr1YgbXfkUktT1Gsq9WvSYGkgpuYLn3rnnFeRTEodp0/Xf808NMGDpDSNn/I8h0yG2SiqNLhEnCh4pai3m8Aa10Eb8RBq6rHcxNhMmThZ67T6BYuhhUy8hq3QIJr+qrlfX/uQYFpBS4 | 1.0 | dFjzBjEiCJ31hU0SosIsyRHh3aUtblHOd0KFapHhpXlNq8gads/CqSbMVIvzYRP3zDwD10U/9gnG6FoRm/BaeytvEvx/pQDw7bz22ZM2lkJeYwYL0/dmqKnMHXRvTMdHwHO0jbufaNgKMCKjSmAjR9QMuCnP+MsiKpajrMdAV6g= - GVKgHfyc93HCOf1omgEWXEvZXNprIxLtKZpzdKAId81de4YsD9udOlJvuJT1+6aZMpr2wPqdUb1zjtNid7SIlakOWhc5CKQ4oyZt2j9OtQDOH1TzMfJ9MUvBpOkfL1KU+8WBSFVDLKq56sE50bfXdqLHnxcm88ciw/CZDU7N/wbGeFWGnwXKslizrcQUWKTym4Feff2vdTbU7QjxtU2s/qnQ7W3fiDvQQuED+YaTQ19AY6BecoPXGOD1rKO294UvJHIwUdgvsWRPmZW2WCbB8/8X0XrxF0e6KOoaXwh4dagRqvfLZBBtMD/jE2ntPP+vqVSPTHqqFgL/HnNUu+qxnPv4T+lVrz+h4TvjDmImaLMmSHKIlFp66DOgQpByavcUKnoPEKTDMgYt7KN1ApOz70+5ApeD37od5jKL4zDAX1+SBJAb0fgR45h1wPYmQ6auWeedsM3BMDowzr+RaxpW9DctE9anJVH7kby7mFKG5XHr5ZcSYCzEOC/ygVGPLfai9P23Xv+z+RcYbUsvwJIeb51cWtfJi1joxM3qdOgp71mL6RZgNSbSr0DJeWZU1sboC3uHDr3gFTA3UcpRfr1m2IHBcbFEijYl76E0rvBN3LHeEe4NbHc6dnoss/cojsXxdMCVb76uQScYcV8M8Md/4Tq6Z+49Ju0iEHsqwOLJZPeG/1oy4E35KPPDfRj0He/ep9UzUU/QfbNmUsmFAxRECbdL9i93009By90+ZBOt3pTOksCujsPTVXT5VfW0saSUwTOsvsphoA/dddxth/KQXaOLbpNwDnFpLsqm17Xp099IL8NcFoDRBL6gsOimibERCLNWOjT2crvPQ5evrPE203fF65DrajkWJ0X2tkwpyxBP9p4NteRN+gww+IpOBG6Ex07YzAeC8UhstBS7VkK0uuu+c4DQ9820AUfIlLba7JjTVCJ1EYxGfMaB/N487ZNQlRQRoWmo8QAW2SjQsTevEvgh7VLPG3ROy6Mc8zbAdIvdGTqx2gP9XPM2l7NcttSY4YDopHsHzIQNcaLVE3bHv1PDpU04AddJqggBLnMuX7UwIlgkFUOCQVa1e5RkGMUjqiUM/S8XpDd+2oUXjunYsn+ETsyxGVK9gpzSTVfJSvF1wc0Eou+iv1ZLjlxjXsRO5//1z+Ym9sA0W7a4WutX+tSemtbeAwSRihegJFWdDUpiPxRoxqlA5oUYy8PmlFdmxyQZ6WBaGHHV5dvgp8S0om86UTEbgEqK4lwwPgZjaRc6PBycHzfgNYkjFr/0gI6cTMY5bAIx/8YAgaeQRRQo0m71Lo3OR7F8uPLzWcqCA2ESlOpUa97Ar2OVkINyEW4S8ZVCnqCcDZPrutSfWOX1aGoO98NAvaBT80cBQYZbGX74gnIbZDLIFZzP6kbMXEpctBPqMfU2RzPu5NXCaKDEebNAoXxdvrg7o4f9QGGO8KRQAzyt4yqzKtklclDQFD+n10Wm0/rKMMUfK3ub5tx+jujU7SUbEEsAuPLfwI2K+goUKYOAiwLGji3Mf3eUjcEdHe2TYqCsBKmvzBqusyCKqlOOOhjP7hmW5PMG0FcItD6QzBSL0zkbxg/us5UIuzZgribG9TJq6VqtfQrhJWAr2Fmg6Qqyc+nb3PLHkh/YXs3RtsCvUmQKxXe3cKkVNvbMjqdwAoZv+N/PUGNjdG8aprc1rPb2QkLqxQMkQIuAUT3ZRnKGu/1wTrskGLgDSS4I6WO6wlNLhJe1STcNipyqZWBWCVhQBBnBouL9NT04bbr7vKua/vRF0h2GjbJmo/8SvmA02WzPmUmaYrVf9Y3eHkv206fFeNMYpZKKzYXMrUsLiL3awU9b/rwkkFW/tJSMUr2wyBKAjPDP9hUwnZQDln+fS+0fwZzELf7JrxfjXKBcw/GXwGD1x0b3Sbn/q46nHaN9U6xRKezycCylXoV5mmODKhL3ow9vDhTc0sgFH36DiGW2Iaz37Q+umL6oJ3zCGlY54WlOLbdRBfJMwPvoP7qBh+Ket7obH5m+SGZqzCqJSsKfzpy28qDDJ6DurLATUHD4XMMjPN1LG+vCgwYmEhDAaJyRaiwUE3ku81C4U8deNOhEMuBYNYwEoXwdws7z0eV/o1OpVrqCpPEC40cAkMDrMN+t1zIwrkWrqum+8YhT4qMh6giV97aewbbdPiRRAtarzsWhvWjB2KQOxjBxBtgCkakvnnFK7MPozuApv1BKO+mW7kvLYYhh39QaeQpLXIsNtdWaMq0pA6Jjn72nkr4xUwoxvtN6HbKzs8sEQzedyYiZwk5gbTZFyKX8OKy7HL8zBovMZYgPxItgXkXSkLYXhem04UiK/MpNMAjXfZxdTConvdgFWCaD/yhyNLbwn+wNW/FJEdr1J2fqIwZDwxbgzEUs9kxIEigoytq364AwqSPp5spEAxWzONG5N7J2LopEEQOpLQdEqu6Pyr3cvSUMF0F11vhRFLz9UgqCjfXNntHz1e0qPkb9arEzvSHAZX+3UAwAhgISPrJytDSoI8GDozvvfiN7wBLC6aezZM0NPE1IWQIVPE01jp0GP5QNO5S5vfOub9VOBWX5WqANuHdWchVH71zTtjakSx8UY4vdEQ2yFQJ3rJRjYDAGxYAoaUsSSy+crVfnFuO8i+k5bOGfe4a1IVZL2/oxEK+lm3XthXtrhhVvNE8omdqJqGZ33CiyJPm6/z8rNiCiUCvGYrJTaLPhOIGfRJD8SayXpt4uj2jmjBirFp2/9ECjP6AhnpFueJwhOdjOq9z8flypx9/sZ0HlFmuK/XqFRKnvkPfoh48oqZn2pb15GWZuv6XQuNiQV7CPHu0PTdkuohZ1En/+iynpsgh730iw0DUCDRFOPHJq/Iipu5SBVoRkjIfCvba3OFPsQAbrBxt5/GZ8ryJ71wEcJbtTq7RAk6z2NmzIjNHczcjQcobWJZaA3GzJg6lk1OorZSCR+tm9+zFJ6uGleeVEfV/BaxUtkIt08BeaLLF8TrVr+4kNrzXJOEA29EdoATkblmB8rz30ptMn4ALWq87Fob1owdikDsYwcQanjjENMlR5XBb8Q01TiT1RGqe2/jxeshoFjVnAkY5kYTMWNUjJHZ9JPBKgl1JJyF+hxm3kSK3qqnHAHWxMOsXmm+vMuWexgQ87Fi4hxCw8adZEHB2ES4BRChFT0I9By7FDFsejIX7pX3X1xvoV4UdyIrvPxDgH7j/FPhYUEncIXVz8grithd0m2F7GXoZqz6MjZHdTADwf9FrtBwljxNMskVbujHAVTFQG6dPcHA9b7BYGeKc3F0zujgBf+aaB/hXjY4I8PXOMDWt0DAE0TM2lazc5i1WizPvCBQr1E/iqwTq1OoEqSKdlGPonR1w6W1JkV1DX/842TX72gbtIFsaOmwBWzaGSdJs7bjso5nXU1IxFiGymctssrn0ksKBTS1GIKLsYD/c3UNCBqMO+roxXxadfm85aCrYAfK+J5cK0iGwX12zUEiAcVbq/rWmbv/qgTaaB+U0GCQu8bc4VPTsEuSXFM/S9XItW+et0fkV/7aIhXyyRv8pFBGnCZdeQJwXGAAS41UxdFJUzukIFGim16HyOutaCw2FRmk9PTc8reJmTepN1S9ZntFslA9eSvwrkHp3SmSKKMNU/at6jBaVcbzWQwcwwQwWApJhr3j9uRiuQ0OVQceDSl9GyBnrGrZWtOC9vOZT/p5/wfnbQNCTyoqufY4MC1nQulA122NsQMAL4Jz4E/oclzny1fDO5pQwgDyJe9i6ivbhQ4P8mNG2TIczTRBfI82rOLDeHVqOvGlipKOM/ohwsZ6ORUPPxaonYsByWT1gro1rS4l6U+n0bF0YAqljX7WzKQkMKtH8jb7B2zEWN71+BhJLzlnHxyF/+QqBraUo9AjDkLiEo40XPAuCrGTTO4bfcY2cMzlvCARztLX5mjln4rSETGQyIzzjOyCIGb8BcEqYhijZUeiiQaE8lfIeCyLYAtLW51LK2+RQPmGSCpRg8EEA7sbiy5EOHX+3gVOrqL/VmU866boXzMqJmURUmPxdWHzTIQoHE8NHxzl6SVP9zcDgPhF1VXhyb7lH9srsvURwDA1p/gAXZAGXDung74BCQickXqGcOlzKiZlEVJj8XVh80yEKBxPCq72VT4MHE7ZcOnUnwx6I7KHE59z93N3EMZJgI9dJuPAFTDovFU9+vGtsZqtAFYZ1mdACLcoexUEjJvaM0HwToQyUZvCYPGZdAgj63Nsy3Qr5qVZdXJmIxp/KoTtoc0QJ0RTgheyvgINe0qN/SaEWxke+M0StrTiThkmfzsUJr3NoWMdOrMuP0Y/of2wO5VKJIYUAN8m/If9ndCGRBm9gDq6Gr4EJKs81GhGh4ykXyUhthoWBOThp+Aa+jq7GA0ZPq+TMBGvNc12TUVJh9MUvaXO6WegWzfuTsKN8R7vnmX2EoXs2DCIJ57TsVqVh9uBtuyRiBmFaLrwcFVsFK70Yk2NHiYtfSY5EEpM9ewsD4ujR3tFCosnBv66/W54D+95tasP4B0lzhBO+UYemoPhoyh+Uj3MRNTGNsKKAdASfHujVbt7wThf1EOLq4j5oDh0QHDeso6cGb7DExdhP90P1V0vK803BQTKyb8u2tQI1KWlNy/pxVJsD8eohnfckgs6+hmmifrIK7kHR7f5/C9XYVm772v+3UxymluBHzwWciiE8eYmX2/U2wu6e8MUlR+Xh7kcIDH6mrkMspVWJIcH+UeywSr+PCjhHLsJWfOLMtGQTHf5/b0RSC84K0GKqc0/uM8fcFd+otoSKRsfhRxTrtGKlSKqU/hB5pbMG9Hf8QBuUTgPlPiGqILwKq3kJtEg4PJdP7lunPXHfOJEFzyZPYyW+8eb5OewPyFNJhTBwYGAiVOuJuFZ0b2ty+s0LyHePnrotuv/yZXgBmc2j0BzUQUNmSFxxkbk4svzIGplyynry2/dm5/6u3uv5zcJpoDktX/p/XF9j+QSEo2Nk+lCPve6FeNB9KjDQAFBjpZOLFzdS5fQLSpCmw60USsg+IHHAuDcR6glaaRm5AHxnARpNxgMbIOVBXt2DBGCtDmAK123WrruVE+wQYdo4cTsw5p/mad6PQo9tbYevz3UwPNsW/xz8B8zckjUASeEsPkWZAiwX514LnIx1WHh2g5cyPBUj3wu9P86OHwybpfTxJQYF5eRRI7bIRgsfbV5KnDzkkrGIdiC0Qh39/LCJszfPn7xGVJ2xgQJs0q6V7AEluv/2qam6daIoMThzWgzgNH02aocAuKLmuVDiEKFP54xmAWnQTunwK6UJALpREMvWTeCgR5Fzkf9l8PZoOAkD4aeehKTYyOykzzKcfJW3n+WL5RDJwuJ98kiCHluA1uQC0ha/ZAtyWhvWB3blQYHH+casFw4P4cx5ncUWMkHrYAPVzeluGm6dRhy+vGdrcilrmDF4wkIrGQqKxZ0W6WEDADGUNKAF6xCXRRLtABt1pXT8sF2jjcdAescTj4ZT5Km9DEZUDYGTVgGKnBEK6II+L+fGjHAZBCd7+Ux+3sXdZbOAVLbi4cYjAw5+wmHIGV5qvoe9K9qfUb9AalQEUy4FvgTbpcbry38rSygjS3RNWhy9hboLEhoGvAYCMpz87+Uh0+vVSapvVNtBIIkLTfRzHjBd38xd9RCIOrgQGkrYF2wi4D3y/7kFjhoWpo3shssa9aM42+UqhTpjg56nLn0vCfpw4ei5pN6Yq8ffJGZzlAVfSD+gNL8DYkTtzg2QGQ7kGKiyBg9qh/B5hob6kOm29HFupgKdIYgCUlYsiUyQ3PomkN/zmSOpUFFgDO3Vns6KY5n93jljHvYI6Lx9Q+V7LxMGNJVmpvym5CAghAAVVWLeGQ2XSrTjvFqF88yo/LgJbMjjB6MMI6hi6ht5OlHURp1VW4rp365sDaP2QZvBqm55dis6fB5Xy2i64BXenMKoOr215qqDPMcrEbMZYJKVvnnA2do4NsiCs9qG4JlgKpB9Py4zWqASU3SEN5GnKrjvT00HHZpfZhDcRnDfTw5ccD0sZzPJFjFnGm2wmAQkaizc+1+t4b6gBuQGhEvbyEcvbZzLY0SZRxt9UJD6qq/17T8HHWexU+EXcM4rZqJ0qTrzCcqDvscMSOy7lInpyQu8aEuOgf0n1gNLbkoieKe58YxE7oF+yk6EgsVBQz66Gap5U3TCEKhgN2iS3vKsaz8ix9dllnbZY8N9qKYv/IQYrYonXhL05oqT4vITWjCUDE48NG5oTRnfJOU9S7JDgoaWgzK5oF/WP+3pA0CZfyuatMTOgqvmS9GbyPEVKfpYk30F8LF6CGMnLLFlXETAuB4F2EGCm21dIY0Ed8PKEnG63kpH2nRp9ibXbLUR5XhETcuw7IQrehopn/R/78jng1gmmhZ23lsspe2F8KEUX5TBkUxHhLNoewgnNDhZzU9TY0ZSV5pE29nB84tABZMCJjagUg0kaMs6JVZWZ9QQeUIoTaob1d6t8am9AMEq5NCZ2r9u7qp6M4LjpamtYz7o64qGwsnBpn2yib9IoILXbQwFlQ5LIJhR8zgFMUtMqeI+DtLYmcJQAbrCly39imLbrOLh/1ITZWEs4/fwIouY2cgpXfrcCnrFu5lm8S0V4Bms2xZyZXSM7T4cLKJCtUi35Vq7SKRx2JpZjEubG2g+MmX7cNYeimaEV38lIVQmcO89J+oStz2cNwMQS3jATqCIJ4NFzNo8yZnQAi3KHsVBIyb2jNB8E6CPhR6GOyP0oCXw+u+0Vr1w5s/O3O55cDuPzm/lWnTz1V8jPEzzPHHlKytC1yb6CYNOQHCEW1EUIM0Qju3lVg+JyuL3PTxIB3RvYSq/k/NS8w2MS6Mgq1wAWKxzhpy6PP0YP38eAQzVqglFUjt/6nDVWX2ZI0RxjjafMAbEl1IdG77eMP7JOzLG6qJK87o1SYGJ53QMJsJFJw8BB6y5WUzaeeMAxxt2CwI/apC46EjLdkmF+ot2Cw8rCq8R8ULGhFPhGJSfYWwHVrKk+dqDaHKiut7Js7yuryP8YwCdFl1nR8kWMWcabbCYBCRqLNz7X69BxTFcYS+XauODCCwQ0+guAx3CLhAdhWx43xbhjMc1uyuNj2zMk8Z6geJR/sL7ebWYyvtwuLoJoZfAUAQPHONKgbebHpzaoPTcSAbmkfgdLxUej86ehDLks5xBDwT+cycoUBIVevqqs72+krIXKtmdog7zU7ptVX/e2eE0l9W3tbl5934dvVj1H/qMc9ev7SbKTCC9VXoHwQNrVgNJ3ryFQQgNhJJcD5ksTvVLsaDR2+i0CYApbVY7dyXdyN0YnNPjo0bWLqDI81uOjOBPiFpz7SZnCHkf9uITvjRqJHRmj2uIt4QmDkzr73m3fDGY6IyYEhXyHx9spnyWQuHodFHuKwm68UV0AxeoiTuAVU/hcM2e6kiyrs5VEEOfimzBx0eEVd4jVbi296UJeQc4rCCHwZDH4vVHX+5g0EVd5ZBAQLs9HMnktcpwrIisS8jshElPUJjOWSn54l7T5JIBK/wlyQcA9SUbkKYKFP3aw0KyIMTpQQRc+STuY2ipW0FSQJF2f9qHwZMRZPwq39EqC3He6jhVxG24/ChrgDajkEQ+7PNBT1pADEGqNAdJfy9YTAxE+TTE0qNx3prx8bTdJpNje/4ixG+Ol+Yt9gNLqyJP2r9dzv1iJLvt1/PJxCSpkDKGwf0zZ4XZcJtzlaHerDtZU6daFsp9k8CLpjj1KKgZ2+Ba/n+aHe95WLz54VETdNi31hbd4by29uhv3ylpCgNh9UWgclc9oCTxv/fagZqkr+ovNalj3mLYMImMeQg8HfJ77izq+XXYDmzkCc2yQHN6pLELQ1JzngZgunV5egZy5Znu48I9N1LAeMQ7aKys8QFLIsyjvC8zJKyfuQgu2j5O6PjdTJYdlWTWnRbpClkiyiBtODWNIKax8Te9+GhAT9/1m9qenwvAH5N7TOhDtrFtW7t3vY9R00UPtKaEDHuLo5c7FTaIa7q3fLst+E17O1G9USU8tnZtK/h18cEZqmQF7CdCwhuG14nOd2wPgjmw//62foM2H72k2t5AwdfVte/au7xi2SPWMVX1vqTvGuZvC1C0dhA2zwlNafK5c8ASaarlgJ/oRs6A+1z8GtRbjW6BomJ5UC3IvBlj7gR4y1C1Tl/XSaidremBgofZY8ZfGMF+R+bD4PeCOEEKxnlczLG/uU1zzDZjrXsRKsx4L9EMorztyqik9gTSvnjs85N5Nof4HPXefoFIMAabCZNahR9ezrAlM4B07enpHlN8TSi1MgSlNu6JNLpAQkUFnKw16RZ37f/XTRos1wdnFbFfdjdPMqZYuXUsCGZcfoW3DOuoAe8+GSq4yqGBwAnayUKxUHVI8tZ8cZDMYhPP1c3Wt0UDplJUUi7c++pS0PJCZoK3E0KsZt2S1NtT0Scylo5FzJB0K83/7I2S52Q43DUe0WUicRXHBc2gPed8bf7ItwXNFM1LxJB/Fo/ovGJJz3u4YB86arpbhcIKBtZE23/eDL1mm5M8ppS5ffxW6cRYnrnfMXjZdNf3VfcHh4Zfd6UPTbEa9MZEBbT2FMD83t3yG4w6ZLufzQNgu+OOqr4wpwBwWDolE0ZCtY+rvFmXKGQCgwTYppmJXk7paLAT8ECi3AkP6RMWylMVgW9HGsowYp1v2eOqiVtorAucO+tZbEHauHKDMdNLAD7mCtLBJfd5baAT9FqlvDh5lqv3CDT1MFFT5T2Rs8mzxR/CXpLqLM33Qg1zzcL17dxZBYrWNsq5FppOPYYqtoJQLmQeS24gjVJorY2j7i2KumpvkA1q7Fsjxc5U10/eB0CwmDAnaBccgtHyVe6lhJz1goWNX/qNrZNfbOI2c7DvCdcx4Ulo47R5JjiUh5UYtRTQuji5kkez+tPdOftvTf3fiPnSQFapGpMMPW92wGkh2pQXaCz5MNWmc2bTRZBtDxfjuPHi0TBwseq++x3DTKHb2hLqEEmNWFFwPx6eDffpSopM14LwJdqgEhTt7IDyQhrwKFIkYw5656hoinzqWqhPyBahu4MWeeNtTS/obnzgZcxH5B9ylGFHLm2/a9HBtNqTrXYBFlQsLTfVJI0Tfeyl/50Y/o7NdVRyxvPkzmmdX629LpQFUZbH7pz62asIDZ40ndVYanc+ZsSnDmdZW5oiQvicMfL5rG1l3W56BrJ8prw+Npjjyiiy6mlcz65o4jr4+FE8vmEHVDdcmhhE568cmXbfOwDeh4NIcozk6hTRf7R37baSwTBL2ONHpDCdT97Uy6aQaYCb1IPM3ZL0e8fvbbzjyDPL6j866dMWYUW3ZXCEyP0U92RNG8rwPQUQiSIb20VjeTA8ptWBj84eNtgKByqqGe6d36qqZghWeBdOUGWa2OWWe9xIQ3j+qYt+Mac/wqGban+Dm8tDS/x0MbdBia9w9IMBXjSrkqeRiGMOhiumxOrBKtBza1/VYJF8M8uzmvOb0WSJ/vKqsVF0TXCR7cFEidEAOqc527sRDh+3vLBS0xHV2rqaw/O+nXR75p8iNEP09iu8Onatm7r7giks3J/pexN5B8vUR2QDLYjX4birZkcLbRZCi8c/Fg5Ep0tfksDTeA4sXIZsZzTMkTVzlxOrLXpmiYNo3VCKIpu42B93QtYRh/Eh5ERxBNwezw8XgDMm3WZa0pIhkPsBxXhkgSXEvy4IEiLhZM/FEMiEPpxvgTp1+NXAGcG4F2mKVm/NVtwSdssvWH4Fodw8u2EzXW65JwDS9dQTkBnePfKY+pYJdMTQHtunGgGl3nIiO5NpVsbwz+nGIae/2ikYhK7GcePO00uJDZvsR3RpjkClst8yz+5go+jGQaKw0VyraRgAYCzYNQXEt0CToyL1v6VRrBQlVdzhwU3UNn8rcKW4FRRkcnGY7ut2Foghz5i9Y9EIS3HQISuZw+NTK+rVOkb/62NpQ59EcurGqqupp7O0rNOs246+IDFiCErJAghF1r3+2wYKclTlIGzH/D0GQSRhRDUFBM+8ka9ynuzrzO8nhmmpoJYLz/VCb+Kqz7dOL05PaFL7vTj4BG0ZhfU0EHStZyzOKchcMhGqqEh0n7KqFxppB+apOq6LXp4trUF++XznN/Anb9DTDnd9aWQr84Xm/gvm8IFSbPdJBNE2+NuWbSA0RZnLFPsh1nBeP6G4w+E67AH9M/qS/yrAyIDBuyFFHYugarx20qbO9FWmxGXsWga50o0BM71scKs0PLiN58DBBnCd4f5pCuQE7jPsNmA4uhQ278CRxDBrrvnOA0PfNtAFHyJS22uyYroIAOtSYFH03sZyk8laxO8C1u9u6WJWcvF97QnCsNGZ5Fu5dJ4UERvkBCiA6PStBRU/d056IGymf3kT0Nh5NHpc7tdnYXlNQ2qffBlLlcU6zEjwHXwrh37lIyeHRI95jZKaCq5+R+a0ns3rTKAZ06OnwyHAEHKgdJJ24k+PoNcz2XrNpNPKqBirE3lxZIW0sIZ9K7X3psl8j1DTR0vY+gPRnVA4/6kvnOMkWPGfaB1/IHS6cYzKsxTUJ98925njQ1QL+/P5JgOfe74Ur8ghP9qtQ1tmm7vpxugw+wM4f/MNgaGFXHSWcarZr/EwiPNXQaH81p+R/pE9y7SLrwPe7n/mrBfkU0Pm/POQJjhqNVhxdfIuxCAHOCa8pYktQ8mBdCD7SRv4skKQU+PTbAQawuJ9wZumts5gmkXogoH/k0k3GuAVgBeTXMpFqZ6cIsndAieT7mXWSrEe4O/ReH0r8CGGspSssr/rA2/xpinV45GKZ/Ve2aDv3mCvXEbwdjAnQaL2SU6lrI7CzSuK/fqPVIDOeep4TORVgh4nntI9u507gx+TybNWbRbiBIcM0CHAdGn7SNNRNYQJyG7qEZk/mT3TL6TgF6AtLrIeKfHFk9sqwSXua2f8RT9tWPvhloMS0UdibQr4gLO5sNSvuGyBTULv3BeDI3cv9wikXz589GJpK713tPhUgLjQlU1kAYgL06MxZx6XyE0YrIhBJsRsARgtqF8YPoAo0g7DvQwRz2Me+HqfVAPBaQhr1YgbXfkUktT1Gsq9WvSYGkgpuYLn3rnnFeRTEodp0/Xf808NMGDpDSNn/I8h0yG2SiqNLhEnCh4pai3m8Aa10Eb8RBq6rHcxNhMmThZ67T6BYuhhUy8hq3QIJr+qrlfX/uQYFpBS4 | non_test | baeytvevx vqvspthqqfgl hnnuu lvrz z dddxth gww n rwkkfw fs mpnmajxfzxdtconvdgfwcad yhynlbwn wnw oxek aab rwmbv qgtaab bhjlzlnhxyf saewxke aa uyemophoyh ueywsr otoskrsfhrxtrtgklskqu p l ux wp r u k chrgdajkeq ol ba n fagzqkr r fo qyt mac wqgban o ngiae ntk rvokb vcb xznn qs r mngagfxhswcarzr r qrlfx | 0 |
340,306 | 30,509,336,545 | IssuesEvent | 2023-07-18 19:28:22 | web-platform-tests/interop | https://api.github.com/repos/web-platform-tests/interop | closed | Remove wpt/webgl/idlharness.any.html & idlharness.any.worker.html from Interop list | test-change-proposal focus area: Offscreen Canvas | ### Test List
[wpt](https://wpt.fyi/results/?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned&view=interop&q=label%3Ainterop-2023-offscreencanvas%20chrome%3A%21ok%20chrome%3A%21pass) /[webgl](https://wpt.fyi/results/webgl?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned&view=interop&q=label%3Ainterop-2023-offscreencanvas%20chrome%3A%21ok%20chrome%3A%21pass)/[idlharness.any.html](https://wpt.fyi/results/webgl/idlharness.any.html?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned&view=interop&q=label%3Ainterop-2023-offscreencanvas%20chrome%3A%21ok%20chrome%3A%21pass)
[wpt](https://wpt.fyi/results/?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned&view=interop&q=label%3Ainterop-2023-offscreencanvas%20chrome%3A%21ok%20chrome%3A%21pass) /[webgl](https://wpt.fyi/results/webgl?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned&view=interop&q=label%3Ainterop-2023-offscreencanvas%20chrome%3A%21ok%20chrome%3A%21pass)/[idlharness.any.worker.html](https://wpt.fyi/results/webgl/idlharness.any.worker.html?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned&view=interop&q=label%3Ainterop-2023-offscreencanvas%20chrome%3A%21ok%20chrome%3A%21pass)
### Rationale
These two tests are exercising the corner cases of the WebGL specification related to the prototype chain of JavaScript wrappers. The issues they revealed have existed for 10 years and have not disturbed any web developers. Note that no current browser passes these tests. These tests are not included in the WebGL conformance suite at https://github.com/KhronosGroup/WebGL as well.
Rather than churn all existing WebGL implementations, the WebGL working group thinks these tests should be removed from the Interop 2023 suite. WebGL working group also suggested that future WebGL tests be proposed for inclusion in the WebGL conformance suite itself, before being added to the Interop 2023 suite.
| 1.0 | Remove wpt/webgl/idlharness.any.html & idlharness.any.worker.html from Interop list - ### Test List
[wpt](https://wpt.fyi/results/?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned&view=interop&q=label%3Ainterop-2023-offscreencanvas%20chrome%3A%21ok%20chrome%3A%21pass) /[webgl](https://wpt.fyi/results/webgl?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned&view=interop&q=label%3Ainterop-2023-offscreencanvas%20chrome%3A%21ok%20chrome%3A%21pass)/[idlharness.any.html](https://wpt.fyi/results/webgl/idlharness.any.html?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned&view=interop&q=label%3Ainterop-2023-offscreencanvas%20chrome%3A%21ok%20chrome%3A%21pass)
[wpt](https://wpt.fyi/results/?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned&view=interop&q=label%3Ainterop-2023-offscreencanvas%20chrome%3A%21ok%20chrome%3A%21pass) /[webgl](https://wpt.fyi/results/webgl?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned&view=interop&q=label%3Ainterop-2023-offscreencanvas%20chrome%3A%21ok%20chrome%3A%21pass)/[idlharness.any.worker.html](https://wpt.fyi/results/webgl/idlharness.any.worker.html?label=master&label=experimental&product=chrome&product=firefox&product=safari&aligned&view=interop&q=label%3Ainterop-2023-offscreencanvas%20chrome%3A%21ok%20chrome%3A%21pass)
### Rationale
These two tests are exercising the corner cases of the WebGL specification related to the prototype chain of JavaScript wrappers. The issues they revealed have existed for 10 years and have not disturbed any web developers. Note that no current browser passes these tests. These tests are not included in the WebGL conformance suite at https://github.com/KhronosGroup/WebGL as well.
Rather than churn all existing WebGL implementations, the WebGL working group thinks these tests should be removed from the Interop 2023 suite. WebGL working group also suggested that future WebGL tests be proposed for inclusion in the WebGL conformance suite itself, before being added to the Interop 2023 suite.
| test | remove wpt webgl idlharness any html idlharness any worker html from interop list test list rationale these two tests are exercising the corner cases of the webgl specification related to the prototype chain of javascript wrappers the issues they revealed have existed for years and have not disturbed any web developers note that no current browser passes these tests these tests are not included in the webgl conformance suite at as well rather than churn all existing webgl implementations the webgl working group thinks these tests should be removed from the interop suite webgl working group also suggested that future webgl tests be proposed for inclusion in the webgl conformance suite itself before being added to the interop suite | 1 |
62,334 | 6,794,352,197 | IssuesEvent | 2017-11-01 11:46:45 | atlasmap/atlasmap-ui | https://api.github.com/repos/atlasmap/atlasmap-ui | opened | Element IDs on mapping details | test | @igarashitm
Hi Tomo, we'd like to enhance the UI a bit and create IDs to specifically select elements like Action dropdwon, input fields, etc.
Matej @mmelko wanted to look into it, but if you happen to have a plan for it already don't hesitate to comment :)
| 1.0 | Element IDs on mapping details - @igarashitm
Hi Tomo, we'd like to enhance the UI a bit and create IDs to specifically select elements like Action dropdwon, input fields, etc.
Matej @mmelko wanted to look into it, but if you happen to have a plan for it already don't hesitate to comment :)
| test | element ids on mapping details igarashitm hi tomo we d like to enhance the ui a bit and create ids to specifically select elements like action dropdwon input fields etc matej mmelko wanted to look into it but if you happen to have a plan for it already don t hesitate to comment | 1 |
256,502 | 22,057,289,843 | IssuesEvent | 2022-05-30 13:58:59 | IBM/operator-sample-go | https://api.github.com/repos/IBM/operator-sample-go | closed | TestCase 1 related to step 3 - .yaml extension is missing | test_manual | **Issue:**
ERROR:
โโโโ
While running the below steps:
```
$ kubectl create namespace database
$ kubectl apply -f config/samples/database.sample_v1alpha1_database.yaml
```
โโ>. $ kubectl apply -f config/samples/database.sample_v1alpha1_databasecluster
Got the below error:
Observation: .yaml extension is missing form the file name.
Resolution: Added .yaml extension to my local machine and the file is executed successfully.
Needs to append .yaml in the documentation of GitHub repository.
Warning:
โโโโโ
ERROR:
โโโโ-
While deploying Operator-application without OLMโฆ
While executing the below command
$ make deploy IMG="$REGISTRY/$ORG/$IMAGE_APPLICATION_OPERATOR"
Observation: Cert-manager is missing.
Even though we are running operator withOut OLM, We need to run the script(Automation) scripts/install-required-kubernetes-components.sh, Which includes the installation of Cert-Manager, OLM,Prometheus.
It could be better to provide mannual commands to install only cert-manager.
Resolution: Ran scripts/install-required-kubernetes-components.sh For now.
After running the scriptโฆ
It Went to the Infinite loopโฆ.
**Link to the documentation:**
https://github.com/IBM/operator-sample-go/blob/main/documentation/DbSetupWithoutOLM.md
| 1.0 | TestCase 1 related to step 3 - .yaml extension is missing - **Issue:**
ERROR:
โโโโ
While running the below steps:
```
$ kubectl create namespace database
$ kubectl apply -f config/samples/database.sample_v1alpha1_database.yaml
```
โโ>. $ kubectl apply -f config/samples/database.sample_v1alpha1_databasecluster
Got the below error:
Observation: .yaml extension is missing form the file name.
Resolution: Added .yaml extension to my local machine and the file is executed successfully.
Needs to append .yaml in the documentation of GitHub repository.
Warning:
โโโโโ
ERROR:
โโโโ-
While deploying Operator-application without OLMโฆ
While executing the below command
$ make deploy IMG="$REGISTRY/$ORG/$IMAGE_APPLICATION_OPERATOR"
Observation: Cert-manager is missing.
Even though we are running operator withOut OLM, We need to run the script(Automation) scripts/install-required-kubernetes-components.sh, Which includes the installation of Cert-Manager, OLM,Prometheus.
It could be better to provide mannual commands to install only cert-manager.
Resolution: Ran scripts/install-required-kubernetes-components.sh For now.
After running the scriptโฆ
It Went to the Infinite loopโฆ.
**Link to the documentation:**
https://github.com/IBM/operator-sample-go/blob/main/documentation/DbSetupWithoutOLM.md
| test | testcase related to step yaml extension is missing issue error โโโโ while running the below steps kubectl create namespace database kubectl apply f config samples database sample database yaml โโ kubectl apply f config samples database sample databasecluster got the below error observation yaml extension is missing form the file name resolution added yaml extension to my local machine and the file is executed successfully needs to append yaml in the documentation of github repository warning โโโโโ error โโโโ while deploying operator application without olmโฆ while executing the below command make deploy img registry org image application operator observation cert manager is missing even though we are running operator without olm we need to run the script automation scripts install required kubernetes components sh which includes the installation of cert manager olm prometheus it could be better to provide mannual commands to install only cert manager resolution ran scripts install required kubernetes components sh for now after running the scriptโฆ it went to the infinite loopโฆ link to the documentation | 1 |
275,062 | 23,892,534,752 | IssuesEvent | 2022-09-08 12:37:05 | Tencent/bk-job | https://api.github.com/repos/Tencent/bk-job | closed | bugfix: ๅๅปบๅฏๆๅ้ๆถ๏ผ้ๆฉๅฏ่งไนๅๆ ๆณ้่ไบ๏ผๅ้ไฟๅญไนๅๅ็นๅผ๏ผๅๆฏ้่็๏ผ่ไธไธ่ฝ่ฎพ็ฝฎๅฏ่ง | kind/bug stage/test accepted | **Version / Branch / tag**
**ๅบไบไปไน้ฎ้ข๏ผ(What Happened?)**
ๅๅปบๅฏๆๅ้ๆถ๏ผ้ๆฉๅฏ่งไนๅๆ ๆณ้่ไบ๏ผๅ้ไฟๅญไนๅๅ็นๅผ๏ผๅๆฏ้่็๏ผ่ไธไธ่ฝ่ฎพ็ฝฎๅฏ่ง
**ๅฆไฝๅค็ฐ๏ผ(How to reproduce?)**
ๅๅปบไธไธช `ๅฏๆ` ๅ้๏ผๅกซๅ
ฅๅๅงๅผ๏ผๅนถ็นๅปๅณไพงๅฐ็ผ็ๆพ็คบๆๆ๏ผ
<img width="1721" alt="ไผไธๅพฎไฟกๆชๅพ_ee6ccd32-54f1-4ad6-b574-92b94b8baac4" src="https://user-images.githubusercontent.com/3852595/186141025-2175edaf-a5dd-41ab-ab9c-3044c81d3d03.png">
ไนๅๅฐฑๆ ๆณๅ้ๆฐ้่ๆๆไธบ***ไบ๏ผ
<img width="1707" alt="ไผไธๅพฎไฟกๆชๅพ_dc0e4a84-6e04-4134-bfaa-6d8f4bbeb8df" src="https://user-images.githubusercontent.com/3852595/186141203-7becb568-aaae-45ab-842b-a0cd7a3cb20b.png">
**้ขๆ็ปๆ(What you expect?)**
ๆฅ็ๅฏๆๅๆขๅคๅฏๆ็ไบคไบๆฏๅฏๅๆข็๏ผไธ่ฝๆถๅคฑ | 1.0 | bugfix: ๅๅปบๅฏๆๅ้ๆถ๏ผ้ๆฉๅฏ่งไนๅๆ ๆณ้่ไบ๏ผๅ้ไฟๅญไนๅๅ็นๅผ๏ผๅๆฏ้่็๏ผ่ไธไธ่ฝ่ฎพ็ฝฎๅฏ่ง - **Version / Branch / tag**
**ๅบไบไปไน้ฎ้ข๏ผ(What Happened?)**
ๅๅปบๅฏๆๅ้ๆถ๏ผ้ๆฉๅฏ่งไนๅๆ ๆณ้่ไบ๏ผๅ้ไฟๅญไนๅๅ็นๅผ๏ผๅๆฏ้่็๏ผ่ไธไธ่ฝ่ฎพ็ฝฎๅฏ่ง
**ๅฆไฝๅค็ฐ๏ผ(How to reproduce?)**
ๅๅปบไธไธช `ๅฏๆ` ๅ้๏ผๅกซๅ
ฅๅๅงๅผ๏ผๅนถ็นๅปๅณไพงๅฐ็ผ็ๆพ็คบๆๆ๏ผ
<img width="1721" alt="ไผไธๅพฎไฟกๆชๅพ_ee6ccd32-54f1-4ad6-b574-92b94b8baac4" src="https://user-images.githubusercontent.com/3852595/186141025-2175edaf-a5dd-41ab-ab9c-3044c81d3d03.png">
ไนๅๅฐฑๆ ๆณๅ้ๆฐ้่ๆๆไธบ***ไบ๏ผ
<img width="1707" alt="ไผไธๅพฎไฟกๆชๅพ_dc0e4a84-6e04-4134-bfaa-6d8f4bbeb8df" src="https://user-images.githubusercontent.com/3852595/186141203-7becb568-aaae-45ab-842b-a0cd7a3cb20b.png">
**้ขๆ็ปๆ(What you expect?)**
ๆฅ็ๅฏๆๅๆขๅคๅฏๆ็ไบคไบๆฏๅฏๅๆข็๏ผไธ่ฝๆถๅคฑ | test | bugfix ๅๅปบๅฏๆๅ้ๆถ๏ผ้ๆฉๅฏ่งไนๅๆ ๆณ้่ไบ๏ผๅ้ไฟๅญไนๅๅ็นๅผ๏ผๅๆฏ้่็๏ผ่ไธไธ่ฝ่ฎพ็ฝฎๅฏ่ง version branch tag ๅบไบไปไน้ฎ้ข๏ผ what happened ๅๅปบๅฏๆๅ้ๆถ๏ผ้ๆฉๅฏ่งไนๅๆ ๆณ้่ไบ๏ผๅ้ไฟๅญไนๅๅ็นๅผ๏ผๅๆฏ้่็๏ผ่ไธไธ่ฝ่ฎพ็ฝฎๅฏ่ง ๅฆไฝๅค็ฐ๏ผ how to reproduce ๅๅปบไธไธช ๅฏๆ ๅ้๏ผๅกซๅ
ฅๅๅงๅผ๏ผๅนถ็นๅปๅณไพงๅฐ็ผ็ๆพ็คบๆๆ๏ผ img width alt ไผไธๅพฎไฟกๆชๅพ src ไนๅๅฐฑๆ ๆณๅ้ๆฐ้่ๆๆไธบ ไบ๏ผ img width alt ไผไธๅพฎไฟกๆชๅพ bfaa src ้ขๆ็ปๆ what you expect ๆฅ็ๅฏๆๅๆขๅคๅฏๆ็ไบคไบๆฏๅฏๅๆข็๏ผไธ่ฝๆถๅคฑ | 1 |
244,439 | 20,671,034,298 | IssuesEvent | 2022-03-10 02:12:20 | datafuselabs/databend | https://api.github.com/repos/datafuselabs/databend | opened | test_stateless_cluster: OnQuery Error: Code: 1068, displayText = Cannot join handle from context's runtime, cause: panic. | C-testing | **Summary**
https://github.com/datafuselabs/databend/runs/5481335834?check_suite_focus=true#step:3:5854
```
2022-03-09T14:12:37.009778Z ERROR databend_query::servers::mysql::writers::query_result_writer: OnQuery Error: Code: 1068, displayText = Cannot join handle from context's runtime, cause: panic.
0: common_exception::exception_code::<impl common_exception::exception::ErrorCode>::TokioError
at common/exception/src/exception_code.rs:36:66
1: core::ops::function::FnOnce::call_once
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/ops/function.rs:227:5
<core::result::Result<T,E> as common_exception::exception::ToErrorCode<T,E,CtxFn>>::map_err_to_code::{{closure}}
at common/exception/src/exception.rs:196:13
core::result::Result<T,E>::map_err
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/result.rs:842:27
<core::result::Result<T,E> as common_exception::exception::ToErrorCode<T,E,CtxFn>>::map_err_to_code
at common/exception/src/exception.rs:194:9
2: databend_query::servers::mysql::mysql_interactive_worker::InteractiveWorkerBase<W>::exec_query::{{closure}}::{{closure}}
at query/src/servers/mysql/mysql_interactive_worker.rs:342:28
<core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/future/mod.rs:91:19
3: databend_query::servers::mysql::mysql_interactive_worker::InteractiveWorkerBase<W>::exec_query::{{closure}}
at query/src/servers/mysql/mysql_interactive_worker.rs:308:5
<core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/future/mod.rs:91:19
4: databend_query::servers::mysql::mysql_interactive_worker::InteractiveWorkerBase<W>::do_query::{{closure}}::{{closure}}
at query/src/servers/mysql/mysql_interactive_worker.rs:286:57
<core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/future/mod.rs:91:19
5: databend_query::servers::mysql::mysql_interactive_worker::InteractiveWorkerBase<W>::do_query::{{closure}}
at query/src/servers/mysql/mysql_interactive_worker.rs:270:5
<core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/future/mod.rs:91:19
6: <databend_query::servers::mysql::mysql_interactive_worker::InteractiveWorker<W> as msql_srv::AsyncMysqlShim<W>>::on_query::{{closure}}
at query/src/servers/mysql/mysql_interactive_worker.rs:176:47
<core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/future/mod.rs:91:19
7: <core::pin::Pin<P> as core::future::future::Future>::poll
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/future/future.rs:124:9
msql_srv::AsyncMysqlIntermediary<B,S>::run::{{closure}}
at /home/runner/.cargo/git/checkouts/msql-srv-62b5153e0120bb3a/af29f7b/src/lib.rs:1069:30
<core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/future/mod.rs:91:19
msql_srv::AsyncMysqlIntermediary<B,S>::run_with_options::{{closure}}
at /home/runner/.cargo/git/checkouts/msql-srv-62b5153e0120bb3a/af29f7b/src/lib.rs:821:17
8: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/future/mod.rs:91:19
msql_srv::AsyncMysqlIntermediary<B,S>::run_on::{{closure}}
at /home/runner/.cargo/git/checkouts/msql-srv-62b5153e0120bb3a/af29f7b/src/lib.rs:801:66
<core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/future/mod.rs:91:19
databend_query::servers::mysql::mysql_session::MySQLConnection::run_on_stream::{{closure}}::{{closure}}
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/thread_pool/worker.rs:373:5
14: tokio::runtime::thread_pool::worker::Launch::launch::{{closure}}
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/thread_pool/worker.rs:352:45
<tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/blocking/task.rs:42:21
tokio::runtime::task::core::CoreStage<T>::poll::{{closure}}
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/task/core.rs:161:17
tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/loom/std/unsafe_cell.rs:14:9
tokio::runtime::task::core::CoreStage<T>::poll
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/task/core.rs:151:13
tokio::runtime::task::harness::poll_future::{{closure}}
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/task/harness.rs:467:19
<core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/panic/unwind_safe.rs:271:9
std::panicking::try::do_call
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/std/src/panicking.rs:492:40
std::panicking::try
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/std/src/panicking.rs:456:19
std::panic::catch_unwind
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/std/src/panic.rs:137:14
tokio::runtime::task::harness::poll_future
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/task/harness.rs:455:18
tokio::runtime::task::harness::Harness<T,S>::poll_inner
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/task/harness.rs:103:27
tokio::runtime::task::harness::Harness<T,S>::poll
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/task/harness.rs:57:15
tokio::runtime::task::raw::poll
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/task/raw.rs:128:5
15: tokio::runtime::task::raw::RawTask::poll
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/task/raw.rs:80:18
tokio::runtime::task::UnownedTask<S>::run
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/task/mod.rs:384:9
tokio::runtime::blocking::pool::Task::run
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/blocking/pool.rs:91:9
tokio::runtime::blocking::pool::Inner::run
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/blocking/pool.rs:308:17
tokio::runtime::blocking::pool::Spawner::spawn_thread::{{closure}}
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/blocking/pool.rs:288:17
std::sys_common::backtrace::__rust_begin_short_backtrace
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/std/src/sys_common/backtrace.rs:122:18
16: std::thread::Builder::spawn_unchecked_::{{closure}}::{{closure}}
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/std/src/thread/mod.rs:498:17
<core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/panic/unwind_safe.rs:271:9
std::panicking::try::do_call
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/std/src/panicking.rs:492:40
std::panicking::try
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/std/src/panicking.rs:456:19
std::panic::catch_unwind
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/std/src/panic.rs:137:14
std::thread::Builder::spawn_unchecked_::{{closure}}
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/std/src/thread/mod.rs:497:30
core::ops::function::FnOnce::call_once{{vtable.shim}}
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/ops/function.rs:227:5
17: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/alloc/src/boxed.rs:1854:9
<alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/alloc/src/boxed.rs:1854:9
std::sys::unix::thread::Thread::new::thread_start
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/std/src/sys/unix/thread.rs:108:17
18: start_thread
19: clone
``` | 1.0 | test_stateless_cluster: OnQuery Error: Code: 1068, displayText = Cannot join handle from context's runtime, cause: panic. - **Summary**
https://github.com/datafuselabs/databend/runs/5481335834?check_suite_focus=true#step:3:5854
```
2022-03-09T14:12:37.009778Z ERROR databend_query::servers::mysql::writers::query_result_writer: OnQuery Error: Code: 1068, displayText = Cannot join handle from context's runtime, cause: panic.
0: common_exception::exception_code::<impl common_exception::exception::ErrorCode>::TokioError
at common/exception/src/exception_code.rs:36:66
1: core::ops::function::FnOnce::call_once
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/ops/function.rs:227:5
<core::result::Result<T,E> as common_exception::exception::ToErrorCode<T,E,CtxFn>>::map_err_to_code::{{closure}}
at common/exception/src/exception.rs:196:13
core::result::Result<T,E>::map_err
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/result.rs:842:27
<core::result::Result<T,E> as common_exception::exception::ToErrorCode<T,E,CtxFn>>::map_err_to_code
at common/exception/src/exception.rs:194:9
2: databend_query::servers::mysql::mysql_interactive_worker::InteractiveWorkerBase<W>::exec_query::{{closure}}::{{closure}}
at query/src/servers/mysql/mysql_interactive_worker.rs:342:28
<core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/future/mod.rs:91:19
3: databend_query::servers::mysql::mysql_interactive_worker::InteractiveWorkerBase<W>::exec_query::{{closure}}
at query/src/servers/mysql/mysql_interactive_worker.rs:308:5
<core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/future/mod.rs:91:19
4: databend_query::servers::mysql::mysql_interactive_worker::InteractiveWorkerBase<W>::do_query::{{closure}}::{{closure}}
at query/src/servers/mysql/mysql_interactive_worker.rs:286:57
<core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/future/mod.rs:91:19
5: databend_query::servers::mysql::mysql_interactive_worker::InteractiveWorkerBase<W>::do_query::{{closure}}
at query/src/servers/mysql/mysql_interactive_worker.rs:270:5
<core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/future/mod.rs:91:19
6: <databend_query::servers::mysql::mysql_interactive_worker::InteractiveWorker<W> as msql_srv::AsyncMysqlShim<W>>::on_query::{{closure}}
at query/src/servers/mysql/mysql_interactive_worker.rs:176:47
<core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/future/mod.rs:91:19
7: <core::pin::Pin<P> as core::future::future::Future>::poll
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/future/future.rs:124:9
msql_srv::AsyncMysqlIntermediary<B,S>::run::{{closure}}
at /home/runner/.cargo/git/checkouts/msql-srv-62b5153e0120bb3a/af29f7b/src/lib.rs:1069:30
<core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/future/mod.rs:91:19
msql_srv::AsyncMysqlIntermediary<B,S>::run_with_options::{{closure}}
at /home/runner/.cargo/git/checkouts/msql-srv-62b5153e0120bb3a/af29f7b/src/lib.rs:821:17
8: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/future/mod.rs:91:19
msql_srv::AsyncMysqlIntermediary<B,S>::run_on::{{closure}}
at /home/runner/.cargo/git/checkouts/msql-srv-62b5153e0120bb3a/af29f7b/src/lib.rs:801:66
<core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/future/mod.rs:91:19
databend_query::servers::mysql::mysql_session::MySQLConnection::run_on_stream::{{closure}}::{{closure}}
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/thread_pool/worker.rs:373:5
14: tokio::runtime::thread_pool::worker::Launch::launch::{{closure}}
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/thread_pool/worker.rs:352:45
<tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/blocking/task.rs:42:21
tokio::runtime::task::core::CoreStage<T>::poll::{{closure}}
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/task/core.rs:161:17
tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/loom/std/unsafe_cell.rs:14:9
tokio::runtime::task::core::CoreStage<T>::poll
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/task/core.rs:151:13
tokio::runtime::task::harness::poll_future::{{closure}}
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/task/harness.rs:467:19
<core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/panic/unwind_safe.rs:271:9
std::panicking::try::do_call
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/std/src/panicking.rs:492:40
std::panicking::try
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/std/src/panicking.rs:456:19
std::panic::catch_unwind
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/std/src/panic.rs:137:14
tokio::runtime::task::harness::poll_future
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/task/harness.rs:455:18
tokio::runtime::task::harness::Harness<T,S>::poll_inner
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/task/harness.rs:103:27
tokio::runtime::task::harness::Harness<T,S>::poll
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/task/harness.rs:57:15
tokio::runtime::task::raw::poll
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/task/raw.rs:128:5
15: tokio::runtime::task::raw::RawTask::poll
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/task/raw.rs:80:18
tokio::runtime::task::UnownedTask<S>::run
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/task/mod.rs:384:9
tokio::runtime::blocking::pool::Task::run
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/blocking/pool.rs:91:9
tokio::runtime::blocking::pool::Inner::run
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/blocking/pool.rs:308:17
tokio::runtime::blocking::pool::Spawner::spawn_thread::{{closure}}
at /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.17.0/src/runtime/blocking/pool.rs:288:17
std::sys_common::backtrace::__rust_begin_short_backtrace
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/std/src/sys_common/backtrace.rs:122:18
16: std::thread::Builder::spawn_unchecked_::{{closure}}::{{closure}}
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/std/src/thread/mod.rs:498:17
<core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/panic/unwind_safe.rs:271:9
std::panicking::try::do_call
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/std/src/panicking.rs:492:40
std::panicking::try
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/std/src/panicking.rs:456:19
std::panic::catch_unwind
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/std/src/panic.rs:137:14
std::thread::Builder::spawn_unchecked_::{{closure}}
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/std/src/thread/mod.rs:497:30
core::ops::function::FnOnce::call_once{{vtable.shim}}
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/core/src/ops/function.rs:227:5
17: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/alloc/src/boxed.rs:1854:9
<alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/alloc/src/boxed.rs:1854:9
std::sys::unix::thread::Thread::new::thread_start
at /rustc/8769f4ef2fe1efddd1f072485f97f568e7328f79/library/std/src/sys/unix/thread.rs:108:17
18: start_thread
19: clone
``` | test | test stateless cluster onquery error code displaytext cannot join handle from context s runtime cause panic summary error databend query servers mysql writers query result writer onquery error code displaytext cannot join handle from context s runtime cause panic common exception exception code tokioerror at common exception src exception code rs core ops function fnonce call once at rustc library core src ops function rs as common exception exception toerrorcode map err to code closure at common exception src exception rs core result result map err at rustc library core src result rs as common exception exception toerrorcode map err to code at common exception src exception rs databend query servers mysql mysql interactive worker interactiveworkerbase exec query closure closure at query src servers mysql mysql interactive worker rs as core future future future poll at rustc library core src future mod rs databend query servers mysql mysql interactive worker interactiveworkerbase exec query closure at query src servers mysql mysql interactive worker rs as core future future future poll at rustc library core src future mod rs databend query servers mysql mysql interactive worker interactiveworkerbase do query closure closure at query src servers mysql mysql interactive worker rs as core future future future poll at rustc library core src future mod rs databend query servers mysql mysql interactive worker interactiveworkerbase do query closure at query src servers mysql mysql interactive worker rs as core future future future poll at rustc library core src future mod rs as msql srv asyncmysqlshim on query closure at query src servers mysql mysql interactive worker rs as core future future future poll at rustc library core src future mod rs as core future future future poll at rustc library core src future future rs msql srv asyncmysqlintermediary run closure at home runner cargo git checkouts msql srv src lib rs as core future future future poll at rustc library core src future mod rs msql srv asyncmysqlintermediary run with options closure at home runner cargo git checkouts msql srv src lib rs as core future future future poll at rustc library core src future mod rs msql srv asyncmysqlintermediary run on closure at home runner cargo git checkouts msql srv src lib rs as core future future future poll at rustc library core src future mod rs databend query servers mysql mysql session mysqlconnection run on stream closure closure at home runner cargo registry src github com tokio src runtime thread pool worker rs tokio runtime thread pool worker launch launch closure at home runner cargo registry src github com tokio src runtime thread pool worker rs as core future future future poll at home runner cargo registry src github com tokio src runtime blocking task rs tokio runtime task core corestage poll closure at home runner cargo registry src github com tokio src runtime task core rs tokio loom std unsafe cell unsafecell with mut at home runner cargo registry src github com tokio src loom std unsafe cell rs tokio runtime task core corestage poll at home runner cargo registry src github com tokio src runtime task core rs tokio runtime task harness poll future closure at home runner cargo registry src github com tokio src runtime task harness rs as core ops function fnonce call once at rustc library core src panic unwind safe rs std panicking try do call at rustc library std src panicking rs std panicking try at rustc library std src panicking rs std panic catch unwind at rustc library std src panic rs tokio runtime task harness poll future at home runner cargo registry src github com tokio src runtime task harness rs tokio runtime task harness harness poll inner at home runner cargo registry src github com tokio src runtime task harness rs tokio runtime task harness harness poll at home runner cargo registry src github com tokio src runtime task harness rs tokio runtime task raw poll at home runner cargo registry src github com tokio src runtime task raw rs tokio runtime task raw rawtask poll at home runner cargo registry src github com tokio src runtime task raw rs tokio runtime task unownedtask run at home runner cargo registry src github com tokio src runtime task mod rs tokio runtime blocking pool task run at home runner cargo registry src github com tokio src runtime blocking pool rs tokio runtime blocking pool inner run at home runner cargo registry src github com tokio src runtime blocking pool rs tokio runtime blocking pool spawner spawn thread closure at home runner cargo registry src github com tokio src runtime blocking pool rs std sys common backtrace rust begin short backtrace at rustc library std src sys common backtrace rs std thread builder spawn unchecked closure closure at rustc library std src thread mod rs as core ops function fnonce call once at rustc library core src panic unwind safe rs std panicking try do call at rustc library std src panicking rs std panicking try at rustc library std src panicking rs std panic catch unwind at rustc library std src panic rs std thread builder spawn unchecked closure at rustc library std src thread mod rs core ops function fnonce call once vtable shim at rustc library core src ops function rs as core ops function fnonce call once at rustc library alloc src boxed rs as core ops function fnonce call once at rustc library alloc src boxed rs std sys unix thread thread new thread start at rustc library std src sys unix thread rs start thread clone | 1 |
316,776 | 27,183,007,240 | IssuesEvent | 2023-02-18 21:45:03 | MicrosoftDocs/minecraft-creator | https://api.github.com/repos/MicrosoftDocs/minecraft-creator | closed | [Gametest] using addItem while the player has selected the first hotbar slot doesn't add the item. | GameTest/Scripting | **Describe the bug**
My code adds an item to the player's inventory but when a player's inventory has no items and the first hotbar is selected it doesn't add the item in the inventory. Selecting the 2nd slot and repeating the process will add the item.
**To Reproduce**
Steps to reproduce the behavior:
1. Use this code in this screenshot
2. select first hotbar slot
3. break a block
**Expected behavior**
should add the item in the inventory
**Screenshots**
**Desktop (please complete the following information):**
- OS:Windows 10
| 1.0 | [Gametest] using addItem while the player has selected the first hotbar slot doesn't add the item. - **Describe the bug**
My code adds an item to the player's inventory but when a player's inventory has no items and the first hotbar is selected it doesn't add the item in the inventory. Selecting the 2nd slot and repeating the process will add the item.
**To Reproduce**
Steps to reproduce the behavior:
1. Use this code in this screenshot
2. select first hotbar slot
3. break a block
**Expected behavior**
should add the item in the inventory
**Screenshots**
**Desktop (please complete the following information):**
- OS:Windows 10
| test | using additem while the player has selected the first hotbar slot doesn t add the item describe the bug my code adds an item to the player s inventory but when a player s inventory has no items and the first hotbar is selected it doesn t add the item in the inventory selecting the slot and repeating the process will add the item to reproduce steps to reproduce the behavior use this code in this screenshot select first hotbar slot break a block expected behavior should add the item in the inventory screenshots desktop please complete the following information os windows | 1 |
250,619 | 21,316,597,053 | IssuesEvent | 2022-04-16 11:42:48 | MARS-crew/flip_be_nest | https://api.github.com/repos/MARS-crew/flip_be_nest | closed | TODO : unit test ์ฝ๋ ์์ฑ | TODO TEST | ## unit test
- auth
- [x] #35
- workbook
- [x] #34
- workbookCard
- [x] #37
- user
- [ ] ๋ด ํ๋กํ ์กฐํ | 1.0 | TODO : unit test ์ฝ๋ ์์ฑ - ## unit test
- auth
- [x] #35
- workbook
- [x] #34
- workbookCard
- [x] #37
- user
- [ ] ๋ด ํ๋กํ ์กฐํ | test | todo unit test ์ฝ๋ ์์ฑ unit test auth workbook workbookcard user ๋ด ํ๋กํ ์กฐํ | 1 |
253,098 | 8,051,455,519 | IssuesEvent | 2018-08-01 16:10:11 | Wikidata/soweego | https://api.github.com/repos/Wikidata/soweego | opened | Compute discogs coverage estimation | high priority story | - [ ] use the [Wikidata musicians and bands sample](https://github.com/Wikidata/soweego/blob/master/target_selection/musicians_and_bands_1_percent_sample);
- [ ] implement the following baseline matchers:
- [ ] #6;
- [ ] #7;
- [ ] #8;
- [ ] #11;
- [ ] compute the following ratio: `# unique matches / (sample length - #already linked Wikidata items)`;
- [ ] report the result here: https://meta.wikimedia.org/wiki/Grants:Project/Hjfocs/soweego/Timeline#Big_fishes | 1.0 | Compute discogs coverage estimation - - [ ] use the [Wikidata musicians and bands sample](https://github.com/Wikidata/soweego/blob/master/target_selection/musicians_and_bands_1_percent_sample);
- [ ] implement the following baseline matchers:
- [ ] #6;
- [ ] #7;
- [ ] #8;
- [ ] #11;
- [ ] compute the following ratio: `# unique matches / (sample length - #already linked Wikidata items)`;
- [ ] report the result here: https://meta.wikimedia.org/wiki/Grants:Project/Hjfocs/soweego/Timeline#Big_fishes | non_test | compute discogs coverage estimation use the implement the following baseline matchers compute the following ratio unique matches sample length already linked wikidata items report the result here | 0 |
730,959 | 25,196,256,369 | IssuesEvent | 2022-11-12 14:58:48 | plex1on/Survival-Games | https://api.github.com/repos/plex1on/Survival-Games | closed | spawning issues | bug priority:0 | had spawning issues before, need to look into this ASAP.
from reddit:
> Niclas from Mojang here. I tried to play this map, but I unfortunately spawn in creative mode, overlooking the central area where I think the players spawn once the game has been initiated? I did not see any lobby area where I could adjust the settings.
> The coordinates that I spawned at are XYZ: 0.5 / 152 / 1.5 | 1.0 | spawning issues - had spawning issues before, need to look into this ASAP.
from reddit:
> Niclas from Mojang here. I tried to play this map, but I unfortunately spawn in creative mode, overlooking the central area where I think the players spawn once the game has been initiated? I did not see any lobby area where I could adjust the settings.
> The coordinates that I spawned at are XYZ: 0.5 / 152 / 1.5 | non_test | spawning issues had spawning issues before need to look into this asap from reddit niclas from mojang here i tried to play this map but i unfortunately spawn in creative mode overlooking the central area where i think the players spawn once the game has been initiated i did not see any lobby area where i could adjust the settings the coordinates that i spawned at are xyz | 0 |
433,267 | 30,320,738,728 | IssuesEvent | 2023-07-10 19:02:03 | microsoft/dynamics365patternspractices | https://api.github.com/repos/microsoft/dynamics365patternspractices | closed | [AREA]: Define product and service costing | documentation business-process product and service lifecycle management | ### Contact details
[email protected]
### Organization type
Microsoft employee
### End-to-end business process
Product and service lifecycle management
### Specify the business process area name for the article.
Define product and service pricing
### Enter any additional comments or information you want us to know about this business process area.
Published
### Specify the date you expect the article to be completed and ready for review.
7/1/2023
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct | 1.0 | [AREA]: Define product and service costing - ### Contact details
[email protected]
### Organization type
Microsoft employee
### End-to-end business process
Product and service lifecycle management
### Specify the business process area name for the article.
Define product and service pricing
### Enter any additional comments or information you want us to know about this business process area.
Published
### Specify the date you expect the article to be completed and ready for review.
7/1/2023
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct | non_test | define product and service costing contact details raprofit microsoft com organization type microsoft employee end to end business process product and service lifecycle management specify the business process area name for the article define product and service pricing enter any additional comments or information you want us to know about this business process area published specify the date you expect the article to be completed and ready for review code of conduct i agree to follow this project s code of conduct | 0 |
58,107 | 8,229,675,763 | IssuesEvent | 2018-09-07 10:08:04 | fossasia/badgeyay | https://api.github.com/repos/fossasia/badgeyay | opened | Update Installation Docs for Backend | Documentation Open-for-all Parent issue | **I'm submitting a ...**
- [X] bug report
- [ ] feature request
Please update the Installation Docs for following:
- [ ] Generic Installation Instructions. Please see [this](https://github.com/fossasia/open-event-server/blob/development/docs/installation/basic.md) for reference.
- [ ] Installation on Linux/Unix using Virtualenv. Please see [this](https://github.com/fossasia/open-event-server/blob/development/docs/installation/local.md) for reference.
- [ ] Installaion on Windows or Vagrant Installation. Please see [this](https://github.com/fossasia/open-event-server/blob/development/docs/installation/vagrant.md) for reference.
- [ ] Deployment on Heroku. Please see [this](https://github.com/fossasia/open-event-server/blob/development/docs/installation/heroku.md) for reference.
- [ ] Deployment on Docker. Please see [this](https://github.com/fossasia/open-event-server/blob/development/docs/installation/docker.md) for reference.
1. Please **open separate Issue** for respective Installation docs.
2. Installation docs should be placed [`api/docs/installation`](https://github.com/fossasia/badgeyay/tree/development/api/docs/installation).
3. Please update the link of installation docs in the [`README`](https://github.com/fossasia/badgeyay/blob/development/api/README.md)
3. Every Installation doc should contain a good quality screenshot for every step mentioned.
4. Use Github `Markdown` uniformly for formatting the Installation steps. | 1.0 | Update Installation Docs for Backend - **I'm submitting a ...**
- [X] bug report
- [ ] feature request
Please update the Installation Docs for following:
- [ ] Generic Installation Instructions. Please see [this](https://github.com/fossasia/open-event-server/blob/development/docs/installation/basic.md) for reference.
- [ ] Installation on Linux/Unix using Virtualenv. Please see [this](https://github.com/fossasia/open-event-server/blob/development/docs/installation/local.md) for reference.
- [ ] Installaion on Windows or Vagrant Installation. Please see [this](https://github.com/fossasia/open-event-server/blob/development/docs/installation/vagrant.md) for reference.
- [ ] Deployment on Heroku. Please see [this](https://github.com/fossasia/open-event-server/blob/development/docs/installation/heroku.md) for reference.
- [ ] Deployment on Docker. Please see [this](https://github.com/fossasia/open-event-server/blob/development/docs/installation/docker.md) for reference.
1. Please **open separate Issue** for respective Installation docs.
2. Installation docs should be placed [`api/docs/installation`](https://github.com/fossasia/badgeyay/tree/development/api/docs/installation).
3. Please update the link of installation docs in the [`README`](https://github.com/fossasia/badgeyay/blob/development/api/README.md)
3. Every Installation doc should contain a good quality screenshot for every step mentioned.
4. Use Github `Markdown` uniformly for formatting the Installation steps. | non_test | update installation docs for backend i m submitting a bug report feature request please update the installation docs for following generic installation instructions please see for reference installation on linux unix using virtualenv please see for reference installaion on windows or vagrant installation please see for reference deployment on heroku please see for reference deployment on docker please see for reference please open separate issue for respective installation docs installation docs should be placed please update the link of installation docs in the every installation doc should contain a good quality screenshot for every step mentioned use github markdown uniformly for formatting the installation steps | 0 |
16,234 | 5,231,794,624 | IssuesEvent | 2017-01-30 05:36:20 | flutter/flutter | https://api.github.com/repos/flutter/flutter | closed | ios/.generated contains 150mb of data | dev: tool team: code health โบโฌ platform-ios | Not entirely sure what's in there, but my tiny demo app was 70mb compressed as a zip, until I realized that all of it's space was used by ios/.generated. Once I removed ios/.generated it was 600k compressed.
Maybe we should move .generated into the `build` folder or something more obviously temporary?
| 1.0 | ios/.generated contains 150mb of data - Not entirely sure what's in there, but my tiny demo app was 70mb compressed as a zip, until I realized that all of it's space was used by ios/.generated. Once I removed ios/.generated it was 600k compressed.
Maybe we should move .generated into the `build` folder or something more obviously temporary?
| non_test | ios generated contains of data not entirely sure what s in there but my tiny demo app was compressed as a zip until i realized that all of it s space was used by ios generated once i removed ios generated it was compressed maybe we should move generated into the build folder or something more obviously temporary | 0 |
336,284 | 30,183,336,856 | IssuesEvent | 2023-07-04 10:19:38 | Kong/kubernetes-ingress-controller | https://api.github.com/repos/Kong/kubernetes-ingress-controller | closed | Update certificates used in integration tests | area/tests | ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Problem Statement
The integration test `TestHTTPSIngress` fails in running validation tests against Kong gateway image `kong/kong-gateway-dev:2.8.4.2-rc1`. After deep dive into the case, we found that the certificates used in the test case is problematic. The certificate having CN `foo.com` has an empty SAN field and is used for hostname `bar.example.com`.
### Proposed Solution
- Update the certificate used in `TestHTTPSIngress`
- use the same hostname as in the certificate
### Additional information
_No response_
### Acceptance Criteria
_No response_ | 1.0 | Update certificates used in integration tests - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Problem Statement
The integration test `TestHTTPSIngress` fails in running validation tests against Kong gateway image `kong/kong-gateway-dev:2.8.4.2-rc1`. After deep dive into the case, we found that the certificates used in the test case is problematic. The certificate having CN `foo.com` has an empty SAN field and is used for hostname `bar.example.com`.
### Proposed Solution
- Update the certificate used in `TestHTTPSIngress`
- use the same hostname as in the certificate
### Additional information
_No response_
### Acceptance Criteria
_No response_ | test | update certificates used in integration tests is there an existing issue for this i have searched the existing issues problem statement the integration test testhttpsingress fails in running validation tests against kong gateway image kong kong gateway dev after deep dive into the case we found that the certificates used in the test case is problematic the certificate having cn foo com has an empty san field and is used for hostname bar example com proposed solution update the certificate used in testhttpsingress use the same hostname as in the certificate additional information no response acceptance criteria no response | 1 |
57,821 | 6,558,082,779 | IssuesEvent | 2017-09-06 19:57:06 | PowerShell/PowerShell | https://api.github.com/repos/PowerShell/PowerShell | opened | Get-ComputerInfo test failing in the nightly build validating CsPhysicallyInstalledMemory | Area-Test | Steps to reproduce
------------------
Run nightly build.
```
Expected behavior
-----------------
All tests pass.
Actual behavior
---------------
Test 01. Standard Property test - all properties (CsPhysicallyInstalledMemory) fails due to CsPhysicallyInstalledMemory not being available.
```
[-] Test 01. Standard Property test - all properties (CsPhysicallyInstalledMemory) 50ms
Expected: {0}
But was: {}
at line: 1050 in C:\projects\powershell-f975h\test\powershell\Modules\Microsoft.PowerShell.Management\Get-ComputerInfo.Tests.ps1
1050: $left | should be $right
Environment data
----------------
git checkout -qf 955e01dc658c44f68268abb5694f958a964d2919
| 1.0 | Get-ComputerInfo test failing in the nightly build validating CsPhysicallyInstalledMemory - Steps to reproduce
------------------
Run nightly build.
```
Expected behavior
-----------------
All tests pass.
Actual behavior
---------------
Test 01. Standard Property test - all properties (CsPhysicallyInstalledMemory) fails due to CsPhysicallyInstalledMemory not being available.
```
[-] Test 01. Standard Property test - all properties (CsPhysicallyInstalledMemory) 50ms
Expected: {0}
But was: {}
at line: 1050 in C:\projects\powershell-f975h\test\powershell\Modules\Microsoft.PowerShell.Management\Get-ComputerInfo.Tests.ps1
1050: $left | should be $right
Environment data
----------------
git checkout -qf 955e01dc658c44f68268abb5694f958a964d2919
| test | get computerinfo test failing in the nightly build validating csphysicallyinstalledmemory steps to reproduce run nightly build expected behavior all tests pass actual behavior test standard property test all properties csphysicallyinstalledmemory fails due to csphysicallyinstalledmemory not being available test standard property test all properties csphysicallyinstalledmemory expected but was at line in c projects powershell test powershell modules microsoft powershell management get computerinfo tests left should be right environment data git checkout qf | 1 |
326,759 | 28,017,277,182 | IssuesEvent | 2023-03-28 00:25:38 | MinaProtocol/mina | https://api.github.com/repos/MinaProtocol/mina | closed | Berkeley: Archive node fails to restore block 4810 | bug priority-high triage berkeley-rampup berkeley-incentivized ITN-zkApps-E2E-testing | ### Preliminary Checks
- [X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/MinaProtocol/mina/issues
- [X] This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/MinaProtocol/mina/discussions
### Description
There is an issue adding block 4810 to the archive node.
```
[BOOTSTRAP] Restoring blocks individually from https://storage.googleapis.com/xxx
Downloading berkeley-4810-3NK5N5GmtB6WrXY7ECvqidULAzmwsoSQwufJnKbj5RyUcoFTMJLe.json block
https://storage.googleapis.com/xxx/berkeley-4810-3NK5N5GmtB6WrXY7ECvqidULAzmwsoSQwufJnKbj5RyUcoFTMJLe.json
(monitor.ml.Error "Assert_failure src/app/archive/lib/processor.ml:102:8"
("Raised at Archive_lib__Processor.Token.add_if_doesn't_exist.(fun) in file \"src/app/archive/lib/processor.ml\", line 102, characters 8-50"
"Called from Archive_lib__Processor.Account_identifiers.add_if_doesn't_exist.(fun) in file \"src/app/archive/lib/processor.ml\", line 186, characters 24-73"
"Called from Async_kernel__Deferred0.bind.(fun) in file \"src/deferred0.ml\", line 54, characters 64-69"
"Called from Async_kernel__Job_queue.run_job in file \"src/job_queue.ml\" (inlined), line 128, characters 2-5"
"Called from Async_kernel__Job_queue.run_jobs in file \"src/job_queue.ml\", line 169, characters 6-47"))
```
There was just a single failed zkApp tx in 4810 which was https://berkeley.minaexplorer.com/transaction/5JtbP8D6uUk7yaCf6gPyNoSEtxY4k5szEhSc5rvKX6tPVtaEhm88.
### Steps to Reproduce
Import block 4810 to the archive node
### Expected Result
It works.
### Actual Result
It throws an error.
### How frequently do you see this issue?
Always
### What is the impact of this issue on your ability to run a node?
Blocker
### Status
```shell
gcr.io/o1labs-192920/mina-archive:1.3.2beta2-rampup-2884275-focal
```
### Additional information
_No response_ | 1.0 | Berkeley: Archive node fails to restore block 4810 - ### Preliminary Checks
- [X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/MinaProtocol/mina/issues
- [X] This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/MinaProtocol/mina/discussions
### Description
There is an issue adding block 4810 to the archive node.
```
[BOOTSTRAP] Restoring blocks individually from https://storage.googleapis.com/xxx
Downloading berkeley-4810-3NK5N5GmtB6WrXY7ECvqidULAzmwsoSQwufJnKbj5RyUcoFTMJLe.json block
https://storage.googleapis.com/xxx/berkeley-4810-3NK5N5GmtB6WrXY7ECvqidULAzmwsoSQwufJnKbj5RyUcoFTMJLe.json
(monitor.ml.Error "Assert_failure src/app/archive/lib/processor.ml:102:8"
("Raised at Archive_lib__Processor.Token.add_if_doesn't_exist.(fun) in file \"src/app/archive/lib/processor.ml\", line 102, characters 8-50"
"Called from Archive_lib__Processor.Account_identifiers.add_if_doesn't_exist.(fun) in file \"src/app/archive/lib/processor.ml\", line 186, characters 24-73"
"Called from Async_kernel__Deferred0.bind.(fun) in file \"src/deferred0.ml\", line 54, characters 64-69"
"Called from Async_kernel__Job_queue.run_job in file \"src/job_queue.ml\" (inlined), line 128, characters 2-5"
"Called from Async_kernel__Job_queue.run_jobs in file \"src/job_queue.ml\", line 169, characters 6-47"))
```
There was just a single failed zkApp tx in 4810 which was https://berkeley.minaexplorer.com/transaction/5JtbP8D6uUk7yaCf6gPyNoSEtxY4k5szEhSc5rvKX6tPVtaEhm88.
### Steps to Reproduce
Import block 4810 to the archive node
### Expected Result
It works.
### Actual Result
It throws an error.
### How frequently do you see this issue?
Always
### What is the impact of this issue on your ability to run a node?
Blocker
### Status
```shell
gcr.io/o1labs-192920/mina-archive:1.3.2beta2-rampup-2884275-focal
```
### Additional information
_No response_ | test | berkeley archive node fails to restore block preliminary checks this issue is not a duplicate before opening a new issue please search existing issues this issue is not a question feature request rfc or anything other than a bug report please post those things in github discussions description there is an issue adding block to the archive node restoring blocks individually from downloading berkeley json block monitor ml error assert failure src app archive lib processor ml raised at archive lib processor token add if doesn t exist fun in file src app archive lib processor ml line characters called from archive lib processor account identifiers add if doesn t exist fun in file src app archive lib processor ml line characters called from async kernel bind fun in file src ml line characters called from async kernel job queue run job in file src job queue ml inlined line characters called from async kernel job queue run jobs in file src job queue ml line characters there was just a single failed zkapp tx in which was steps to reproduce import block to the archive node expected result it works actual result it throws an error how frequently do you see this issue always what is the impact of this issue on your ability to run a node blocker status shell gcr io mina archive rampup focal additional information no response | 1 |
39,317 | 5,227,138,475 | IssuesEvent | 2017-01-28 00:01:16 | rancher/rancher | https://api.github.com/repos/rancher/rancher | closed | Need config file framework for validation tests | area/test kind/enhancement | Need a simple framework for using environment specific config files.
| 1.0 | Need config file framework for validation tests - Need a simple framework for using environment specific config files.
| test | need config file framework for validation tests need a simple framework for using environment specific config files | 1 |
129,771 | 10,585,913,175 | IssuesEvent | 2019-10-08 18:33:48 | dotnet/corefx | https://api.github.com/repos/dotnet/corefx | closed | SafeWaitHandle tests run finalizer with invalid values | area-System.Threading test bug | Originally reported as https://github.com/mono/mono/issues/17224.
At least one SafeWaitHandle test constructs the `SafeWaitHandle` object with invalid handle value:
https://github.com/dotnet/corefx/blob/95e35e10d7c52a7eea38c2ae6402d29e2a01efc6/src/System.Runtime.Handles/tests/SafeWaitHandle.cs#L19-L25
The `SafeWaitHandle` is left in this invalid state and when the finalizer runs the `ReleaseHandle` method is called with the invalid value. Current Mono implementation is not resilient to these invalid values while the CoreCLR implementation is.
The test should be fixed to either reset the `SafeWaitHandle` to invalid value using `SetHandleAsInvalid()` call, or to use derived class with overrridden `ReleaseHandle` method (like [here](https://github.com/dotnet/corefx/blob/7407443d51b92780914732d880e65ffaabbba17c/src/System.Runtime.Handles/tests/SafeHandle.cs#L11-L35)). | 1.0 | SafeWaitHandle tests run finalizer with invalid values - Originally reported as https://github.com/mono/mono/issues/17224.
At least one SafeWaitHandle test constructs the `SafeWaitHandle` object with invalid handle value:
https://github.com/dotnet/corefx/blob/95e35e10d7c52a7eea38c2ae6402d29e2a01efc6/src/System.Runtime.Handles/tests/SafeWaitHandle.cs#L19-L25
The `SafeWaitHandle` is left in this invalid state and when the finalizer runs the `ReleaseHandle` method is called with the invalid value. Current Mono implementation is not resilient to these invalid values while the CoreCLR implementation is.
The test should be fixed to either reset the `SafeWaitHandle` to invalid value using `SetHandleAsInvalid()` call, or to use derived class with overrridden `ReleaseHandle` method (like [here](https://github.com/dotnet/corefx/blob/7407443d51b92780914732d880e65ffaabbba17c/src/System.Runtime.Handles/tests/SafeHandle.cs#L11-L35)). | test | safewaithandle tests run finalizer with invalid values originally reported as at least one safewaithandle test constructs the safewaithandle object with invalid handle value the safewaithandle is left in this invalid state and when the finalizer runs the releasehandle method is called with the invalid value current mono implementation is not resilient to these invalid values while the coreclr implementation is the test should be fixed to either reset the safewaithandle to invalid value using sethandleasinvalid call or to use derived class with overrridden releasehandle method like | 1 |
71,379 | 15,194,670,815 | IssuesEvent | 2021-02-16 04:22:08 | MythicDrops/github-cdkactions | https://api.github.com/repos/MythicDrops/github-cdkactions | opened | CVE-2020-7789 (Medium) detected in node-notifier-6.0.0.tgz | security vulnerability | ## CVE-2020-7789 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-notifier-6.0.0.tgz</b></p></summary>
<p>A Node.js module for sending notifications on native Mac, Windows (post and pre 8) and Linux (or Growl as fallback)</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-notifier/-/node-notifier-6.0.0.tgz">https://registry.npmjs.org/node-notifier/-/node-notifier-6.0.0.tgz</a></p>
<p>Path to dependency file: github-cdkactions/package.json</p>
<p>Path to vulnerable library: github-cdkactions/node_modules/node-notifier/package.json</p>
<p>
Dependency Hierarchy:
- tsdx-0.14.1.tgz (Root Library)
- jest-25.5.4.tgz
- core-25.5.4.tgz
- reporters-25.5.1.tgz
- :x: **node-notifier-6.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/MythicDrops/github-cdkactions/commit/04b2f3e92f863f8bca9985906899f6e50eb9ef79">04b2f3e92f863f8bca9985906899f6e50eb9ef79</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
This affects the package node-notifier before 9.0.0. It allows an attacker to run arbitrary commands on Linux machines due to the options params not being sanitised when being passed an array.
<p>Publish Date: 2020-12-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7789>CVE-2020-7789</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.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7789">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7789</a></p>
<p>Release Date: 2020-12-11</p>
<p>Fix Resolution: 9.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-7789 (Medium) detected in node-notifier-6.0.0.tgz - ## CVE-2020-7789 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-notifier-6.0.0.tgz</b></p></summary>
<p>A Node.js module for sending notifications on native Mac, Windows (post and pre 8) and Linux (or Growl as fallback)</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-notifier/-/node-notifier-6.0.0.tgz">https://registry.npmjs.org/node-notifier/-/node-notifier-6.0.0.tgz</a></p>
<p>Path to dependency file: github-cdkactions/package.json</p>
<p>Path to vulnerable library: github-cdkactions/node_modules/node-notifier/package.json</p>
<p>
Dependency Hierarchy:
- tsdx-0.14.1.tgz (Root Library)
- jest-25.5.4.tgz
- core-25.5.4.tgz
- reporters-25.5.1.tgz
- :x: **node-notifier-6.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/MythicDrops/github-cdkactions/commit/04b2f3e92f863f8bca9985906899f6e50eb9ef79">04b2f3e92f863f8bca9985906899f6e50eb9ef79</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
This affects the package node-notifier before 9.0.0. It allows an attacker to run arbitrary commands on Linux machines due to the options params not being sanitised when being passed an array.
<p>Publish Date: 2020-12-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7789>CVE-2020-7789</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.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7789">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7789</a></p>
<p>Release Date: 2020-12-11</p>
<p>Fix Resolution: 9.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_test | cve medium detected in node notifier tgz cve medium severity vulnerability vulnerable library node notifier tgz a node js module for sending notifications on native mac windows post and pre and linux or growl as fallback library home page a href path to dependency file github cdkactions package json path to vulnerable library github cdkactions node modules node notifier package json dependency hierarchy tsdx tgz root library jest tgz core tgz reporters tgz x node notifier tgz vulnerable library found in head commit a href found in base branch main vulnerability details this affects the package node notifier before it allows an attacker to run arbitrary commands on linux machines due to the options params not being sanitised when being passed an array publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
174,368 | 13,485,114,941 | IssuesEvent | 2020-09-11 07:32:37 | crate/crate | https://api.github.com/repos/crate/crate | closed | Flaky testAcquirePrimaryAllOperationsPermits | test-failure | `testAcquirePrimaryAllOperationsPermits` in `IndexShardTests` is flaky:
```
## FAILURE: Test testAcquirePrimaryAllOperationsPermits(org.elasticsearch.index.shard.IndexShardTests)
[2020-08-12T09:52:30,103][INFO ][o.e.i.s.IndexShardTests ] [testAcquirePrimaryAllOperationsPermits] before test
Aug. 12, 2020 9:52:30 VM. com.carrotsearch.randomizedtesting.RandomizedRunner$QueueUncaughtExceptionsHandler uncaughtException
WARNING: Uncaught exception in thread: Thread[Thread-3950,5,TGRP-IndexShardTests]
java.lang.AssertionError: expected:<0> but was:<1>
at __randomizedtesting.SeedInfo.seed([5B9E2146EE282ED1]:0)
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at org.elasticsearch.index.shard.IndexShardTests.lambda$testAcquirePrimaryAllOperationsPermits$11(IndexShardTests.java:213)
at java.base/java.lang.Thread.run(Thread.java:832)
[2020-08-12T09:52:30,201][INFO ][o.e.i.s.IndexShardTests ] [testAcquirePrimaryAllOperationsPermits] after test
REPRODUCE WITH: ./gradlew null -Dtests.seed=5B9E2146EE282ED1 -Dtests.class=org.elasticsearch.index.shard.IndexShardTests -Dtests.method="testAcquirePrimaryAllOperationsPermits" -Dtests.locale=af-ZA -Dtests.timezone=Asia/Aden
com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an uncaught exception in thread: Thread[id=7853, name=Thread-3950, state=RUNNABLE, group=TGRP-IndexShardTests]
at __randomizedtesting.SeedInfo.seed([5B9E2146EE282ED1:A7B82AB56B3E80DE]:0)
Caused by: java.lang.AssertionError: expected:<0> but was:<1>
at __randomizedtesting.SeedInfo.seed([5B9E2146EE282ED1]:0)
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at org.elasticsearch.index.shard.IndexShardTests.lambda$testAcquirePrimaryAllOperationsPermits$11(IndexShardTests.java:213)
at java.base/java.lang.Thread.run(Thread.java:832)
IndexShardTests > testAcquirePrimaryAllOperationsPermits FAILED
com.carrotsearch.randomizedtesting.UncaughtExceptionError at [5B9E2146EE282ED1:A7B82AB56B3E80DE]:0
Caused by: java.lang.AssertionError at IndexShardTests.java:213
```
| 1.0 | Flaky testAcquirePrimaryAllOperationsPermits - `testAcquirePrimaryAllOperationsPermits` in `IndexShardTests` is flaky:
```
## FAILURE: Test testAcquirePrimaryAllOperationsPermits(org.elasticsearch.index.shard.IndexShardTests)
[2020-08-12T09:52:30,103][INFO ][o.e.i.s.IndexShardTests ] [testAcquirePrimaryAllOperationsPermits] before test
Aug. 12, 2020 9:52:30 VM. com.carrotsearch.randomizedtesting.RandomizedRunner$QueueUncaughtExceptionsHandler uncaughtException
WARNING: Uncaught exception in thread: Thread[Thread-3950,5,TGRP-IndexShardTests]
java.lang.AssertionError: expected:<0> but was:<1>
at __randomizedtesting.SeedInfo.seed([5B9E2146EE282ED1]:0)
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at org.elasticsearch.index.shard.IndexShardTests.lambda$testAcquirePrimaryAllOperationsPermits$11(IndexShardTests.java:213)
at java.base/java.lang.Thread.run(Thread.java:832)
[2020-08-12T09:52:30,201][INFO ][o.e.i.s.IndexShardTests ] [testAcquirePrimaryAllOperationsPermits] after test
REPRODUCE WITH: ./gradlew null -Dtests.seed=5B9E2146EE282ED1 -Dtests.class=org.elasticsearch.index.shard.IndexShardTests -Dtests.method="testAcquirePrimaryAllOperationsPermits" -Dtests.locale=af-ZA -Dtests.timezone=Asia/Aden
com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an uncaught exception in thread: Thread[id=7853, name=Thread-3950, state=RUNNABLE, group=TGRP-IndexShardTests]
at __randomizedtesting.SeedInfo.seed([5B9E2146EE282ED1:A7B82AB56B3E80DE]:0)
Caused by: java.lang.AssertionError: expected:<0> but was:<1>
at __randomizedtesting.SeedInfo.seed([5B9E2146EE282ED1]:0)
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at org.elasticsearch.index.shard.IndexShardTests.lambda$testAcquirePrimaryAllOperationsPermits$11(IndexShardTests.java:213)
at java.base/java.lang.Thread.run(Thread.java:832)
IndexShardTests > testAcquirePrimaryAllOperationsPermits FAILED
com.carrotsearch.randomizedtesting.UncaughtExceptionError at [5B9E2146EE282ED1:A7B82AB56B3E80DE]:0
Caused by: java.lang.AssertionError at IndexShardTests.java:213
```
| test | flaky testacquireprimaryalloperationspermits testacquireprimaryalloperationspermits in indexshardtests is flaky failure test testacquireprimaryalloperationspermits org elasticsearch index shard indexshardtests before test aug vm com carrotsearch randomizedtesting randomizedrunner queueuncaughtexceptionshandler uncaughtexception warning uncaught exception in thread thread java lang assertionerror expected but was at randomizedtesting seedinfo seed at org junit assert fail assert java at org junit assert failnotequals assert java at org junit assert assertequals assert java at org junit assert assertequals assert java at org elasticsearch index shard indexshardtests lambda testacquireprimaryalloperationspermits indexshardtests java at java base java lang thread run thread java after test reproduce with gradlew null dtests seed dtests class org elasticsearch index shard indexshardtests dtests method testacquireprimaryalloperationspermits dtests locale af za dtests timezone asia aden com carrotsearch randomizedtesting uncaughtexceptionerror captured an uncaught exception in thread thread at randomizedtesting seedinfo seed caused by java lang assertionerror expected but was at randomizedtesting seedinfo seed at org junit assert fail assert java at org junit assert failnotequals assert java at org junit assert assertequals assert java at org junit assert assertequals assert java at org elasticsearch index shard indexshardtests lambda testacquireprimaryalloperationspermits indexshardtests java at java base java lang thread run thread java indexshardtests testacquireprimaryalloperationspermits failed com carrotsearch randomizedtesting uncaughtexceptionerror at caused by java lang assertionerror at indexshardtests java | 1 |
335,431 | 30,029,981,346 | IssuesEvent | 2023-06-27 08:58:10 | wpeventmanager/wp-event-manager | https://api.github.com/repos/wpeventmanager/wp-event-manager | closed | Edit event page choose event type & category is display | In Testing | First click on the edit icon from event dashboard.
Click on the Save Changes button.
Here selected type & categories are remove .
Observed that label display as Choose event type & Choose category
| 1.0 | Edit event page choose event type & category is display - First click on the edit icon from event dashboard.
Click on the Save Changes button.
Here selected type & categories are remove .
Observed that label display as Choose event type & Choose category
| test | edit event page choose event type category is display first click on the edit icon from event dashboard click on the save changes button here selected type categories are remove observed that label display as choose event type choose category | 1 |
16,096 | 9,239,167,415 | IssuesEvent | 2019-03-14 00:11:04 | dotnet/corefx | https://api.github.com/repos/dotnet/corefx | closed | Performance Epic | Epic Top Level Epic area-Meta tenet-performance | This Epic is to track work we are doing in CoreFX (and corelib) to monitor and improve performance for the next release - excepting Networking performance, which is likely in the [Networking Epic](https://github.com/dotnet/corefx/issues/24742).
Like all our Epics in order to see the child work items you must have the free [Zenhub browser plugin ](https://www.zenhub.com/) enabled. | True | Performance Epic - This Epic is to track work we are doing in CoreFX (and corelib) to monitor and improve performance for the next release - excepting Networking performance, which is likely in the [Networking Epic](https://github.com/dotnet/corefx/issues/24742).
Like all our Epics in order to see the child work items you must have the free [Zenhub browser plugin ](https://www.zenhub.com/) enabled. | non_test | performance epic this epic is to track work we are doing in corefx and corelib to monitor and improve performance for the next release excepting networking performance which is likely in the like all our epics in order to see the child work items you must have the free enabled | 0 |
323,637 | 27,742,777,822 | IssuesEvent | 2023-03-15 15:15:55 | quadratic-funding/mpc-phase2-suite | https://api.github.com/repos/quadratic-funding/mpc-phase2-suite | closed | Add missing e2e and unit tests for `finalize` command | Test ๐งช High Priority ๐ฅ | Prerequisites: None
Goal: >=90% code coverage. | 1.0 | Add missing e2e and unit tests for `finalize` command - Prerequisites: None
Goal: >=90% code coverage. | test | add missing and unit tests for finalize command prerequisites none goal code coverage | 1 |
39,537 | 8,663,342,531 | IssuesEvent | 2018-11-28 17:05:11 | certbot/certbot | https://api.github.com/repos/certbot/certbot | closed | Treat warnings as failures during testing | area: code health area: testing current sprint | We should use something like https://docs.pytest.org/en/latest/warnings.html to have warnings treated as errors when running our tests with pytest so we can fix anything like deprecation warnings before it's a problem. | 1.0 | Treat warnings as failures during testing - We should use something like https://docs.pytest.org/en/latest/warnings.html to have warnings treated as errors when running our tests with pytest so we can fix anything like deprecation warnings before it's a problem. | non_test | treat warnings as failures during testing we should use something like to have warnings treated as errors when running our tests with pytest so we can fix anything like deprecation warnings before it s a problem | 0 |
266,913 | 23,268,163,021 | IssuesEvent | 2022-08-04 19:36:30 | python/cpython | https://api.github.com/repos/python/cpython | opened | pipe test failures on some Linux configurations | type-bug tests 3.11 3.10 3.12 | # Bug report
On Linux systems, when configured with a default pipe capacity of 4096, the following test fail:
- test_fcntl.test_fcntl_f_pipesize
- test_subprocess.test_pipesizes
From a recent `fcntl(2)` Linux man page:
```
F_SETPIPE_SZ:
...
Attempts to set the pipe capacity below the page size are silently rounded up to the page size.
```
There's a check that attempts to skip the tests if the pipe capacity is [512 bytes](https://github.com/python/cpython/blob/6a5104f4fa83ed08fe31f712757dddabfede394c/Lib/test/test_fcntl.py#L202), but that's less than the smallest page size on x86.
Since this feature appears to be Linux specific, the check should:
1) Use `os.sysconf('SC_PAGESIZE')` as a minimum
2) Fix the typos ("SkitTest") in [test_fcntl_f_pipesize](https://github.com/python/cpython/blob/6a5104f4fa83ed08fe31f712757dddabfede394c/Lib/test/test_fcntl.py#L203) and [test_pipesizes](https://github.com/python/cpython/blob/f6dd14c65336cda4e2ebccbc6408dfe3b0a68a34/Lib/test/test_subprocess.py#L715)
| 1.0 | pipe test failures on some Linux configurations - # Bug report
On Linux systems, when configured with a default pipe capacity of 4096, the following test fail:
- test_fcntl.test_fcntl_f_pipesize
- test_subprocess.test_pipesizes
From a recent `fcntl(2)` Linux man page:
```
F_SETPIPE_SZ:
...
Attempts to set the pipe capacity below the page size are silently rounded up to the page size.
```
There's a check that attempts to skip the tests if the pipe capacity is [512 bytes](https://github.com/python/cpython/blob/6a5104f4fa83ed08fe31f712757dddabfede394c/Lib/test/test_fcntl.py#L202), but that's less than the smallest page size on x86.
Since this feature appears to be Linux specific, the check should:
1) Use `os.sysconf('SC_PAGESIZE')` as a minimum
2) Fix the typos ("SkitTest") in [test_fcntl_f_pipesize](https://github.com/python/cpython/blob/6a5104f4fa83ed08fe31f712757dddabfede394c/Lib/test/test_fcntl.py#L203) and [test_pipesizes](https://github.com/python/cpython/blob/f6dd14c65336cda4e2ebccbc6408dfe3b0a68a34/Lib/test/test_subprocess.py#L715)
| test | pipe test failures on some linux configurations bug report on linux systems when configured with a default pipe capacity of the following test fail test fcntl test fcntl f pipesize test subprocess test pipesizes from a recent fcntl linux man page f setpipe sz attempts to set the pipe capacity below the page size are silently rounded up to the page size there s a check that attempts to skip the tests if the pipe capacity is but that s less than the smallest page size on since this feature appears to be linux specific the check should use os sysconf sc pagesize as a minimum fix the typos skittest in and | 1 |
294,077 | 25,344,066,470 | IssuesEvent | 2022-11-19 02:27:37 | ValveSoftware/steam-runtime | https://api.github.com/repos/ValveSoftware/steam-runtime | closed | Mesa fails to render with libudev.so.0 to libudev.so.1.6.3 symlink and Steam Runtime Soldier 0.20220919.0 | Need Retest Pressure Vessel | #### Your system information
* Steam Runtime Version: latest Steam beta client
* Distribution (e.g. Ubuntu 18.04): Void Linux
* Link to your full system information (Help -> System Information) in a [Gist](https://gist.github.com/):
<!-- Please wait for the extended system infomation to be collected by Steam -->
https://gist.github.com/Ophidiophobia/4c560bcb6819a6ad1adc69d03d36dbff
* Have you checked for system updates?: [Yes/No] Yes
* What compatibility tool are you using?: [None / Steam Linux Runtime / Proton 5.13+ / older Proton] Proton 7.0
* If you are using Steam Linux Runtime for native Linux games: What versions are listed in `SteamLinuxRuntime/VERSIONS.txt`?
* If you are using Steam Linux Runtime, or Proton 5.13 or newer: What versions are listed in `SteamLinuxRuntime_soldier/VERSIONS.txt`?
```
#Name Version Runtime Runtime_Version Comment
depot 0.20220919.70 # Overall version number
pressure-vessel 0.20220919.0
scripts v0.20220823.0-0-gcc4e44f # Entry point scripts, etc.
soldier 0.20220919.0 soldier 0.20220919.0 # soldier_platform_0.20220919.0/
```
#### Please describe your issue in as much detail as possible:
<!-- Describe what you _expected_ should happen and what _did_ happen. Please link any large code pastes as a [Github Gist](https://gist.github.com/) -->
I try running Windows games through Proton and the games do not start.
Most show some kind of error message (different for each game) or they silently abort.
Tested with Raft, Borderlands 3, Cyberpunk 2077.
Info provided below is only on Cyberpunk 2077.
Expectation: Game starts and shows intro or loads into main menu.
In case of Cybyerpunk 2077 the game is marked as running in Steam for some time (less than a minute) and then silently stops without showing any window or other visible activity (launcher is skipped).
<!--
If you are using Proton or the Steam Linux Runtime compatibility tool, please
provide the information requested here:
https://github.com/ValveSoftware/steam-runtime/blob/master/doc/reporting-steamlinuxruntime-bugs.md
-->
#### Steps for reproducing this issue:
1. Start Cyberpunk 2077
2. Wait until REDLauncher opens and click Run to start Cyberpunk (or use the Steam launch option "%command% --launcher-skip" on second run onward)
3. Wait; the launcher closes, Steam shows Steampunk 2077 as running for some seconds until it looks like Steampunk 2077 was closed without further error indications
#### Additional Notes:
Workaround: Set Linux Runtime Soldier to use the beta branch "previous release"
It looks like the current Steam Runtime Soldier does not load any vulkan extensions.
Steam Proton Log of borked run with current Steam Runtime Soldier: https://gist.github.com/Ophidiophobia/fb62bb96a9932c07823e7462e7558c60
Steam Proton Log of successful run with previous release of Steam Runtime Soldier: https://gist.github.com/Ophidiophobia/64c23375106eae8bc693f83cb3833905
| 1.0 | Mesa fails to render with libudev.so.0 to libudev.so.1.6.3 symlink and Steam Runtime Soldier 0.20220919.0 - #### Your system information
* Steam Runtime Version: latest Steam beta client
* Distribution (e.g. Ubuntu 18.04): Void Linux
* Link to your full system information (Help -> System Information) in a [Gist](https://gist.github.com/):
<!-- Please wait for the extended system infomation to be collected by Steam -->
https://gist.github.com/Ophidiophobia/4c560bcb6819a6ad1adc69d03d36dbff
* Have you checked for system updates?: [Yes/No] Yes
* What compatibility tool are you using?: [None / Steam Linux Runtime / Proton 5.13+ / older Proton] Proton 7.0
* If you are using Steam Linux Runtime for native Linux games: What versions are listed in `SteamLinuxRuntime/VERSIONS.txt`?
* If you are using Steam Linux Runtime, or Proton 5.13 or newer: What versions are listed in `SteamLinuxRuntime_soldier/VERSIONS.txt`?
```
#Name Version Runtime Runtime_Version Comment
depot 0.20220919.70 # Overall version number
pressure-vessel 0.20220919.0
scripts v0.20220823.0-0-gcc4e44f # Entry point scripts, etc.
soldier 0.20220919.0 soldier 0.20220919.0 # soldier_platform_0.20220919.0/
```
#### Please describe your issue in as much detail as possible:
<!-- Describe what you _expected_ should happen and what _did_ happen. Please link any large code pastes as a [Github Gist](https://gist.github.com/) -->
I try running Windows games through Proton and the games do not start.
Most show some kind of error message (different for each game) or they silently abort.
Tested with Raft, Borderlands 3, Cyberpunk 2077.
Info provided below is only on Cyberpunk 2077.
Expectation: Game starts and shows intro or loads into main menu.
In case of Cybyerpunk 2077 the game is marked as running in Steam for some time (less than a minute) and then silently stops without showing any window or other visible activity (launcher is skipped).
<!--
If you are using Proton or the Steam Linux Runtime compatibility tool, please
provide the information requested here:
https://github.com/ValveSoftware/steam-runtime/blob/master/doc/reporting-steamlinuxruntime-bugs.md
-->
#### Steps for reproducing this issue:
1. Start Cyberpunk 2077
2. Wait until REDLauncher opens and click Run to start Cyberpunk (or use the Steam launch option "%command% --launcher-skip" on second run onward)
3. Wait; the launcher closes, Steam shows Steampunk 2077 as running for some seconds until it looks like Steampunk 2077 was closed without further error indications
#### Additional Notes:
Workaround: Set Linux Runtime Soldier to use the beta branch "previous release"
It looks like the current Steam Runtime Soldier does not load any vulkan extensions.
Steam Proton Log of borked run with current Steam Runtime Soldier: https://gist.github.com/Ophidiophobia/fb62bb96a9932c07823e7462e7558c60
Steam Proton Log of successful run with previous release of Steam Runtime Soldier: https://gist.github.com/Ophidiophobia/64c23375106eae8bc693f83cb3833905
| test | mesa fails to render with libudev so to libudev so symlink and steam runtime soldier your system information steam runtime version latest steam beta client distribution e g ubuntu void linux link to your full system information help system information in a have you checked for system updates yes what compatibility tool are you using proton if you are using steam linux runtime for native linux games what versions are listed in steamlinuxruntime versions txt if you are using steam linux runtime or proton or newer what versions are listed in steamlinuxruntime soldier versions txt name version runtime runtime version comment depot overall version number pressure vessel scripts entry point scripts etc soldier soldier soldier platform please describe your issue in as much detail as possible i try running windows games through proton and the games do not start most show some kind of error message different for each game or they silently abort tested with raft borderlands cyberpunk info provided below is only on cyberpunk expectation game starts and shows intro or loads into main menu in case of cybyerpunk the game is marked as running in steam for some time less than a minute and then silently stops without showing any window or other visible activity launcher is skipped if you are using proton or the steam linux runtime compatibility tool please provide the information requested here steps for reproducing this issue start cyberpunk wait until redlauncher opens and click run to start cyberpunk or use the steam launch option command launcher skip on second run onward wait the launcher closes steam shows steampunk as running for some seconds until it looks like steampunk was closed without further error indications additional notes workaround set linux runtime soldier to use the beta branch previous release it looks like the current steam runtime soldier does not load any vulkan extensions steam proton log of borked run with current steam runtime soldier steam proton log of successful run with previous release of steam runtime soldier | 1 |
14,629 | 3,282,333,298 | IssuesEvent | 2015-10-28 05:27:27 | timvideos/HDMI2USB-numato-opsis-hardware | https://api.github.com/repos/timvideos/HDMI2USB-numato-opsis-hardware | closed | Issues with low speed signal lines HDMI signal | bug design-pcb-layout part-video-hdmi-in | The HDMI RX ports have a 15k resistor pulling them down and a 1k resistor pulling them up!? | 1.0 | Issues with low speed signal lines HDMI signal - The HDMI RX ports have a 15k resistor pulling them down and a 1k resistor pulling them up!? | non_test | issues with low speed signal lines hdmi signal the hdmi rx ports have a resistor pulling them down and a resistor pulling them up | 0 |
309,914 | 26,683,140,275 | IssuesEvent | 2023-01-26 19:26:17 | filecoin-project/ref-fvm | https://api.github.com/repos/filecoin-project/ref-fvm | closed | EVM: Arithmetic Tests | Topic: Testing | - [x] `ADD`
- [x] `MUL`
- [x] `SUB`
- [x] `DIV`
- [x] `SDIV`
- [x] `MOD`
- [x] `SMOD`
- [x] `ADDMOD`
- [x] `MULMOD`
- [x] `EXP`
- [x] `SIGNEXTEND` | 1.0 | EVM: Arithmetic Tests - - [x] `ADD`
- [x] `MUL`
- [x] `SUB`
- [x] `DIV`
- [x] `SDIV`
- [x] `MOD`
- [x] `SMOD`
- [x] `ADDMOD`
- [x] `MULMOD`
- [x] `EXP`
- [x] `SIGNEXTEND` | test | evm arithmetic tests add mul sub div sdiv mod smod addmod mulmod exp signextend | 1 |
657,859 | 21,870,004,186 | IssuesEvent | 2022-05-19 03:37:13 | encorelab/ck-board | https://api.github.com/repos/encorelab/ck-board | closed | Close Tasks by Re-clicking Task Icon | enhancement good first issue low priority 1 | Rather than needing to click "close" in the snackbar to close a task, can we re-click the task icon in the top left to close the task snackbar? That way if someone clicks once to read they can quickly re-click again to close without moving their cursor across the screen... sometimes its the little things :) | 1.0 | Close Tasks by Re-clicking Task Icon - Rather than needing to click "close" in the snackbar to close a task, can we re-click the task icon in the top left to close the task snackbar? That way if someone clicks once to read they can quickly re-click again to close without moving their cursor across the screen... sometimes its the little things :) | non_test | close tasks by re clicking task icon rather than needing to click close in the snackbar to close a task can we re click the task icon in the top left to close the task snackbar that way if someone clicks once to read they can quickly re click again to close without moving their cursor across the screen sometimes its the little things | 0 |
81,390 | 30,829,320,310 | IssuesEvent | 2023-08-01 23:26:38 | dotCMS/core | https://api.github.com/repos/dotCMS/core | closed | Content detailed page throwing 404 when URL contains a trailing slash. | Type : Defect QA : Approved Merged QA : Passed Internal Team : Scout Next LTS Release OKR : Customer Success Priority : 2 High OKR : Customer Support Next Release Release : 23.07 Release : 22.03.8 | ### Describe the bug
Content detailed page throwing 404 when URL contains a trailing slash.
Reproduced on 22.10
Related ticket: https://dotcms.zendesk.com/agent/tickets/108893
### To Reproduce
https://demo.dotcms.com/store/products/k2-mens-mindbender-99ti-skis Works fine
https://demo.dotcms.com/store/products/k2-mens-mindbender-99ti-skis/ throws 404
### Expected behavior
The detailed page should return the desired contentlet when a trailing slash exists
### Additional context
This behavior works fine on 21.06.*, 5.3.8.*
| 1.0 | Content detailed page throwing 404 when URL contains a trailing slash. - ### Describe the bug
Content detailed page throwing 404 when URL contains a trailing slash.
Reproduced on 22.10
Related ticket: https://dotcms.zendesk.com/agent/tickets/108893
### To Reproduce
https://demo.dotcms.com/store/products/k2-mens-mindbender-99ti-skis Works fine
https://demo.dotcms.com/store/products/k2-mens-mindbender-99ti-skis/ throws 404
### Expected behavior
The detailed page should return the desired contentlet when a trailing slash exists
### Additional context
This behavior works fine on 21.06.*, 5.3.8.*
| non_test | content detailed page throwing when url contains a trailing slash describe the bug content detailed page throwing when url contains a trailing slash reproduced on related ticket to reproduce works fine throws expected behavior the detailed page should return the desired contentlet when a trailing slash exists additional context this behavior works fine on | 0 |
242,179 | 26,257,125,047 | IssuesEvent | 2023-01-06 02:25:53 | rvvergara/hackernews-nextjs-clone | https://api.github.com/repos/rvvergara/hackernews-nextjs-clone | opened | CVE-2021-23364 (Medium) detected in browserslist-4.6.6.tgz | security vulnerability | ## CVE-2021-23364 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>browserslist-4.6.6.tgz</b></p></summary>
<p>Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-env-preset</p>
<p>Library home page: <a href="https://registry.npmjs.org/browserslist/-/browserslist-4.6.6.tgz">https://registry.npmjs.org/browserslist/-/browserslist-4.6.6.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/browserslist/package.json</p>
<p>
Dependency Hierarchy:
- next-9.0.2.tgz (Root Library)
- preset-env-7.4.5.tgz
- :x: **browserslist-4.6.6.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package browserslist from 4.0.0 and before 4.16.5 are vulnerable to Regular Expression Denial of Service (ReDoS) during parsing of queries.
<p>Publish Date: 2021-04-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23364>CVE-2021-23364</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23364">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23364</a></p>
<p>Release Date: 2021-04-28</p>
<p>Fix Resolution (browserslist): 4.16.5</p>
<p>Direct dependency fix Resolution (next): 9.0.3-canary.0</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-2021-23364 (Medium) detected in browserslist-4.6.6.tgz - ## CVE-2021-23364 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>browserslist-4.6.6.tgz</b></p></summary>
<p>Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-env-preset</p>
<p>Library home page: <a href="https://registry.npmjs.org/browserslist/-/browserslist-4.6.6.tgz">https://registry.npmjs.org/browserslist/-/browserslist-4.6.6.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/browserslist/package.json</p>
<p>
Dependency Hierarchy:
- next-9.0.2.tgz (Root Library)
- preset-env-7.4.5.tgz
- :x: **browserslist-4.6.6.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package browserslist from 4.0.0 and before 4.16.5 are vulnerable to Regular Expression Denial of Service (ReDoS) during parsing of queries.
<p>Publish Date: 2021-04-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23364>CVE-2021-23364</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23364">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23364</a></p>
<p>Release Date: 2021-04-28</p>
<p>Fix Resolution (browserslist): 4.16.5</p>
<p>Direct dependency fix Resolution (next): 9.0.3-canary.0</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 medium detected in browserslist tgz cve medium severity vulnerability vulnerable library browserslist tgz share target browsers between different front end tools like autoprefixer stylelint and babel env preset library home page a href path to dependency file package json path to vulnerable library node modules browserslist package json dependency hierarchy next tgz root library preset env tgz x browserslist tgz vulnerable library vulnerability details the package browserslist from and before are vulnerable to regular expression denial of service redos during parsing of queries 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 browserslist direct dependency fix resolution next canary step up your open source security game with mend | 0 |
43,932 | 23,425,981,895 | IssuesEvent | 2022-08-14 11:53:00 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | Performance has doubled since a couple of days ago. | area-Meta tenet-performance untriaged needs-further-triage | According to my numbers since 7.0.100-rc.1.22412.1 my performance doubled.
Can this be?
I need to know maybe I broke something. The runtime has since forever had a hot (contested from many CPU) locking speed limit of ~`28, 000 FPS`. Now it is ~`54, 000 FPS`. Either I broke something or something spectacular has taken place inside the runtime. I would love to know, or I will have to walk back changes. | True | Performance has doubled since a couple of days ago. - According to my numbers since 7.0.100-rc.1.22412.1 my performance doubled.
Can this be?
I need to know maybe I broke something. The runtime has since forever had a hot (contested from many CPU) locking speed limit of ~`28, 000 FPS`. Now it is ~`54, 000 FPS`. Either I broke something or something spectacular has taken place inside the runtime. I would love to know, or I will have to walk back changes. | non_test | performance has doubled since a couple of days ago according to my numbers since rc my performance doubled can this be i need to know maybe i broke something the runtime has since forever had a hot contested from many cpu locking speed limit of fps now it is fps either i broke something or something spectacular has taken place inside the runtime i would love to know or i will have to walk back changes | 0 |
63,934 | 8,701,234,793 | IssuesEvent | 2018-12-05 10:57:24 | visual-framework/vf-core | https://api.github.com/repos/visual-framework/vf-core | closed | DOCS - Branch naming convention | Priority: Low Status: Feedback Needed Type: Documentation Type: Question | We will be adopting the branch naming convention previously used:
```
type/good-name
```
but we should clarify the `type` a little better. In the aim to have this documented somewhere.
1. `feature` - to be used when working on a new component. Is `feature` the right word here, maybe `new-item` or something?
2. `fix` - to be used for ... fixes. Do we want to split this and add `hot-fix` for things for the `master` branch?
3. `docs` - for anything to do with documentation. Content or code.
4. `updates` - when we update anything - is this a good enough term? What about `refactor` as that is mainly that `updates` have been used for.
Are there any more we can think of?
| 1.0 | DOCS - Branch naming convention - We will be adopting the branch naming convention previously used:
```
type/good-name
```
but we should clarify the `type` a little better. In the aim to have this documented somewhere.
1. `feature` - to be used when working on a new component. Is `feature` the right word here, maybe `new-item` or something?
2. `fix` - to be used for ... fixes. Do we want to split this and add `hot-fix` for things for the `master` branch?
3. `docs` - for anything to do with documentation. Content or code.
4. `updates` - when we update anything - is this a good enough term? What about `refactor` as that is mainly that `updates` have been used for.
Are there any more we can think of?
| non_test | docs branch naming convention we will be adopting the branch naming convention previously used type good name but we should clarify the type a little better in the aim to have this documented somewhere feature to be used when working on a new component is feature the right word here maybe new item or something fix to be used for fixes do we want to split this and add hot fix for things for the master branch docs for anything to do with documentation content or code updates when we update anything is this a good enough term what about refactor as that is mainly that updates have been used for are there any more we can think of | 0 |
108,231 | 13,595,369,107 | IssuesEvent | 2020-09-22 02:52:39 | openenclave/openenclave | https://api.github.com/repos/openenclave/openenclave | closed | oe_terminate_enclave return OE_OUT_OF_THREADS after switchless ecall exit when TCSNUM=1 | core design investigation triaged | test case in PR [https://github.com/openenclave/openenclave/pull/2887](url)
details as follow:
1. Create enclave with Switchless Calls and one TCS only.
2. Call empty switchless ecall, it is expected to pass.
3. Call empty ecall, it is expected to fail since TCS is occupied by trusted worker thread.
4. empty switchless ecall exit
5. Destroy enclave (this step failure, return OE_OUT_OF_THREADS)
if I replaced switchless ecall with regular ecall, test is PASS. | 1.0 | oe_terminate_enclave return OE_OUT_OF_THREADS after switchless ecall exit when TCSNUM=1 - test case in PR [https://github.com/openenclave/openenclave/pull/2887](url)
details as follow:
1. Create enclave with Switchless Calls and one TCS only.
2. Call empty switchless ecall, it is expected to pass.
3. Call empty ecall, it is expected to fail since TCS is occupied by trusted worker thread.
4. empty switchless ecall exit
5. Destroy enclave (this step failure, return OE_OUT_OF_THREADS)
if I replaced switchless ecall with regular ecall, test is PASS. | non_test | oe terminate enclave return oe out of threads after switchless ecall exit when tcsnum test case in pr url details as follow create enclave with switchless calls and one tcs only call empty switchless ecall it is expected to pass call empty ecall it is expected to fail since tcs is occupied by trusted worker thread empty switchless ecall exit destroy enclave this step failure return oe out of threads if i replaced switchless ecall with regular ecall test is pass | 0 |
563,108 | 16,676,132,946 | IssuesEvent | 2021-06-07 16:24:28 | glciampaglia/infodiversity-mock-social-media | https://api.github.com/repos/glciampaglia/infodiversity-mock-social-media | closed | Keep logs of the backend | medium priority | We need to make sure that both the python and node.js parts of the backend keep track of a log where to store all information, including warnings, debugging messages (if running in debug mode), and errors.
Ideally, it would be great to have both node.js and python log to the same file, but since this is probably, complicated, we will keep two separate log files. With python, we can use [the built-in logging module](https://docs.python.org/3/library/logging.html), and save to a file. With node.js, we'll simply keep a file open and save messages there.
We need to:
- [x] Set up logging module in python
- [x] Set up logging file in node.js
- [x] Go through code add INFO messages for any relevant step as part of its normal flow
- [x] Go through code and make sure any exception is logged at the ERROR level (or above) | 1.0 | Keep logs of the backend - We need to make sure that both the python and node.js parts of the backend keep track of a log where to store all information, including warnings, debugging messages (if running in debug mode), and errors.
Ideally, it would be great to have both node.js and python log to the same file, but since this is probably, complicated, we will keep two separate log files. With python, we can use [the built-in logging module](https://docs.python.org/3/library/logging.html), and save to a file. With node.js, we'll simply keep a file open and save messages there.
We need to:
- [x] Set up logging module in python
- [x] Set up logging file in node.js
- [x] Go through code add INFO messages for any relevant step as part of its normal flow
- [x] Go through code and make sure any exception is logged at the ERROR level (or above) | non_test | keep logs of the backend we need to make sure that both the python and node js parts of the backend keep track of a log where to store all information including warnings debugging messages if running in debug mode and errors ideally it would be great to have both node js and python log to the same file but since this is probably complicated we will keep two separate log files with python we can use and save to a file with node js we ll simply keep a file open and save messages there we need to set up logging module in python set up logging file in node js go through code add info messages for any relevant step as part of its normal flow go through code and make sure any exception is logged at the error level or above | 0 |
385,092 | 26,617,237,646 | IssuesEvent | 2023-01-24 08:24:03 | BIG-MAP/BattINFO | https://api.github.com/repos/BIG-MAP/BattINFO | opened | Make URI/IRIs work from a browser | documentation enhancement | When putting in the URI/IRI in a browser, one should get information up about the concept.
As this is syntactically and semantically the same as going to an anchor on a page (a same-page link), this is probably the solution. | 1.0 | Make URI/IRIs work from a browser - When putting in the URI/IRI in a browser, one should get information up about the concept.
As this is syntactically and semantically the same as going to an anchor on a page (a same-page link), this is probably the solution. | non_test | make uri iris work from a browser when putting in the uri iri in a browser one should get information up about the concept as this is syntactically and semantically the same as going to an anchor on a page a same page link this is probably the solution | 0 |
12,583 | 3,282,209,423 | IssuesEvent | 2015-10-28 04:05:07 | FreeCodeCamp/FreeCodeCamp | https://api.github.com/repos/FreeCodeCamp/FreeCodeCamp | closed | Waypoint: Target the same element with multiple jQuery Selectors BUG | confirmed tests | Challenge [Waypoint: Target the same element with multiple jQuery Selectors](http://freecodecamp.com/challenges/waypoint-target-the-same-element-with-multiple-jquery-selectors) has an issue.
User Agent is: <code>Mozilla/5.0 (Windows NT 6.1; rv:39.0) Gecko/20100101 Firefox/39.0</code>.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
```html
<script>
$(document).ready(function() {
$("button").addClass("animated shake");
$(".btn").addClass("animated shake");
$("#target1").addClass("animated shake btn-primary");
});
</script>
<!-- You shouldn't need to modify code below this line -->
<div class="container-fluid">
<h3 class="text-primary text-center">jQuery Playground</h3>
<div class="row">
<div class="col-xs-6">
<h4>#left-well</h4>
<div class="well" id="left-well">
<button class="btn btn-default target" id="target1">#target1</button>
<button class="btn btn-default target" id="target2">#target2</button>
<button class="btn btn-default target" id="target3">#target3</button>
</div>
</div>
<div class="col-xs-6">
<h4>#right-well</h4>
<div class="well" id="right-well">
<button class="btn btn-default target" id="target4">#target4</button>
<button class="btn btn-default target" id="target5">#target5</button>
<button class="btn btn-default target" id="target6">#target6</button>
</div>
</div>
</div>
</div>
```
Your #target1 element should have the classes animatedโ shake and btn-primary. The error is marked down that my code doesn't have the right classes. Wich is in this case they are right. I asked on Gitter and I need to do all of them instead of only #target1. Just let you guys know this ;)
| 1.0 | Waypoint: Target the same element with multiple jQuery Selectors BUG - Challenge [Waypoint: Target the same element with multiple jQuery Selectors](http://freecodecamp.com/challenges/waypoint-target-the-same-element-with-multiple-jquery-selectors) has an issue.
User Agent is: <code>Mozilla/5.0 (Windows NT 6.1; rv:39.0) Gecko/20100101 Firefox/39.0</code>.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
```html
<script>
$(document).ready(function() {
$("button").addClass("animated shake");
$(".btn").addClass("animated shake");
$("#target1").addClass("animated shake btn-primary");
});
</script>
<!-- You shouldn't need to modify code below this line -->
<div class="container-fluid">
<h3 class="text-primary text-center">jQuery Playground</h3>
<div class="row">
<div class="col-xs-6">
<h4>#left-well</h4>
<div class="well" id="left-well">
<button class="btn btn-default target" id="target1">#target1</button>
<button class="btn btn-default target" id="target2">#target2</button>
<button class="btn btn-default target" id="target3">#target3</button>
</div>
</div>
<div class="col-xs-6">
<h4>#right-well</h4>
<div class="well" id="right-well">
<button class="btn btn-default target" id="target4">#target4</button>
<button class="btn btn-default target" id="target5">#target5</button>
<button class="btn btn-default target" id="target6">#target6</button>
</div>
</div>
</div>
</div>
```
Your #target1 element should have the classes animatedโ shake and btn-primary. The error is marked down that my code doesn't have the right classes. Wich is in this case they are right. I asked on Gitter and I need to do all of them instead of only #target1. Just let you guys know this ;)
| test | waypoint target the same element with multiple jquery selectors bug challenge has an issue user agent is mozilla windows nt rv gecko firefox please describe how to reproduce this issue and include links to screenshots if possible my code html document ready function button addclass animated shake btn addclass animated shake addclass animated shake btn primary jquery playground left well right well your element should have the classes animatedโ shake and btn primary the error is marked down that my code doesn t have the right classes wich is in this case they are right i asked on gitter and i need to do all of them instead of only just let you guys know this | 1 |
334,415 | 29,837,379,023 | IssuesEvent | 2023-06-19 00:59:43 | pytorch/pytorch | https://api.github.com/repos/pytorch/pytorch | closed | DISABLED test_ddp_comparison_uneven_inputs (__main__.TensorPipeDdpComparisonTest) | high priority triage review oncall: distributed triaged module: flaky-tests skipped module: ddp | Platforms: linux
This test was disabled because it is failing in CI. See [recent examples](http://torch-ci.com/failure/test_ddp_comparison_uneven_inputs%2C%20TensorPipeDdpComparisonTest) and the most recent
[workflow logs](https://github.com/pytorch/pytorch/actions/runs/1844534065).
Over the past 3 hours, it has been determined flaky in 1 workflow(s) with
1 red and 3 green.
cc @ezyang @gchanan @zou3519 @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang | 1.0 | DISABLED test_ddp_comparison_uneven_inputs (__main__.TensorPipeDdpComparisonTest) - Platforms: linux
This test was disabled because it is failing in CI. See [recent examples](http://torch-ci.com/failure/test_ddp_comparison_uneven_inputs%2C%20TensorPipeDdpComparisonTest) and the most recent
[workflow logs](https://github.com/pytorch/pytorch/actions/runs/1844534065).
Over the past 3 hours, it has been determined flaky in 1 workflow(s) with
1 red and 3 green.
cc @ezyang @gchanan @zou3519 @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang | test | disabled test ddp comparison uneven inputs main tensorpipeddpcomparisontest platforms linux this test was disabled because it is failing in ci see and the most recent over the past hours it has been determined flaky in workflow s with red and green cc ezyang gchanan pietern mrshenli zhaojuanmao satgera rohan varma gqchen aazzolini osalpekar jiayisuse scipioneer h huang | 1 |
7,147 | 2,610,329,259 | IssuesEvent | 2015-02-26 19:46:07 | chrsmith/republic-at-war | https://api.github.com/repos/chrsmith/republic-at-war | closed | Jugger and AT-TE garrison | auto-migrated Priority-Medium Type-Defect | ```
If you take a look at the enhanced juggernaut XMl i sent, one thing i thought
is neccesary, is decreasing its infantry slots from 10 to 5-6.
Also, AT-TE is known for being able to house a squad of clones. So it needs one
infantry slot. I can help with coding if needed.
```
-----
Original issue reported on code.google.com by `[email protected]` on 13 Jun 2011 at 5:47 | 1.0 | Jugger and AT-TE garrison - ```
If you take a look at the enhanced juggernaut XMl i sent, one thing i thought
is neccesary, is decreasing its infantry slots from 10 to 5-6.
Also, AT-TE is known for being able to house a squad of clones. So it needs one
infantry slot. I can help with coding if needed.
```
-----
Original issue reported on code.google.com by `[email protected]` on 13 Jun 2011 at 5:47 | non_test | jugger and at te garrison if you take a look at the enhanced juggernaut xml i sent one thing i thought is neccesary is decreasing its infantry slots from to also at te is known for being able to house a squad of clones so it needs one infantry slot i can help with coding if needed original issue reported on code google com by richarda gmail com on jun at | 0 |
94,762 | 19,580,374,920 | IssuesEvent | 2022-01-04 20:26:45 | NREL/celavi | https://api.github.com/repos/NREL/celavi | opened | Refactor component.py loops. | code review | In the `eol_process()` method of the `Component` class, there are multiple occurrences of loops with the following pattern:
```
for material, mass in self.mass_tonnes.items():
fac1_transport.increment_inbound_tonne_km(
self.split_dict[factype]['fraction'] * mass * distance,
env.now
)
fac1_mass_inventory.increment_quantity(
material,
self.split_dict[factype]['fraction'] * mass,
env.now
)
```
Refactor this code to a method to reduce code duplication. | 1.0 | Refactor component.py loops. - In the `eol_process()` method of the `Component` class, there are multiple occurrences of loops with the following pattern:
```
for material, mass in self.mass_tonnes.items():
fac1_transport.increment_inbound_tonne_km(
self.split_dict[factype]['fraction'] * mass * distance,
env.now
)
fac1_mass_inventory.increment_quantity(
material,
self.split_dict[factype]['fraction'] * mass,
env.now
)
```
Refactor this code to a method to reduce code duplication. | non_test | refactor component py loops in the eol process method of the component class there are multiple occurrences of loops with the following pattern for material mass in self mass tonnes items transport increment inbound tonne km self split dict mass distance env now mass inventory increment quantity material self split dict mass env now refactor this code to a method to reduce code duplication | 0 |
318,835 | 27,325,114,284 | IssuesEvent | 2023-02-25 00:58:08 | flutter/flutter | https://api.github.com/repos/flutter/flutter | closed | [url_launcher] link_widget_test.dart test failing on stable | a: tests team p: url_launcher package P3 | In merging flutter/plugins into flutter/packages, I'm seeing persistent failures in the Link widget integration tests on web, but only on `stable`. I don't see any differences in the test config relative to flutter/plugins, where it's passing, so to avoid blocking the merge I'm going to turn it off for `stable` for now and we can investigate further after the merge.
/cc @ditman | 1.0 | [url_launcher] link_widget_test.dart test failing on stable - In merging flutter/plugins into flutter/packages, I'm seeing persistent failures in the Link widget integration tests on web, but only on `stable`. I don't see any differences in the test config relative to flutter/plugins, where it's passing, so to avoid blocking the merge I'm going to turn it off for `stable` for now and we can investigate further after the merge.
/cc @ditman | test | link widget test dart test failing on stable in merging flutter plugins into flutter packages i m seeing persistent failures in the link widget integration tests on web but only on stable i don t see any differences in the test config relative to flutter plugins where it s passing so to avoid blocking the merge i m going to turn it off for stable for now and we can investigate further after the merge cc ditman | 1 |
830,284 | 31,999,826,113 | IssuesEvent | 2023-09-21 11:33:37 | Team-Ampersand/GKR-Android | https://api.github.com/repos/Team-Ampersand/GKR-Android | closed | (#120) ๋ก๊ทธ์ธ model ํ์
์๋ฌ ์์ | 0๏ธโฃ Priority: Critical ๐ Type: Bug | ### Describe
- ๋ก๊ทธ์ธ model ํ์
์๋ฌ ์์
### ETC
- ์ฐธ๊ณ ์ฌํญ์ด๋ ๊ธฐํ์ฌํญ์ ์ค๋ช
ํด์ฃผ์ธ์.
| 1.0 | (#120) ๋ก๊ทธ์ธ model ํ์
์๋ฌ ์์ - ### Describe
- ๋ก๊ทธ์ธ model ํ์
์๋ฌ ์์
### ETC
- ์ฐธ๊ณ ์ฌํญ์ด๋ ๊ธฐํ์ฌํญ์ ์ค๋ช
ํด์ฃผ์ธ์.
| non_test | ๋ก๊ทธ์ธ model ํ์
์๋ฌ ์์ describe ๋ก๊ทธ์ธ model ํ์
์๋ฌ ์์ etc ์ฐธ๊ณ ์ฌํญ์ด๋ ๊ธฐํ์ฌํญ์ ์ค๋ช
ํด์ฃผ์ธ์ | 0 |
36,403 | 5,050,669,616 | IssuesEvent | 2016-12-20 19:27:56 | shelljs/shelljs | https://api.github.com/repos/shelljs/shelljs | closed | Switch to the ava test framework | high priority refactor test | This is a bug to track the progress of switching to the ava test framework.
Here is the proposed approach:
- [x] make a directory called `ava-test/`
- [x] copy the resources to `ava-test/resources/` (leave a copy where it is now, too)
- [x] one by one, remove a file from `test/` and put its ava equivalent in `ava-test/`
- [x] modify `npm test`: instead of `node scripts/run-tests`, turn it into `node scripts/run-tests && ava --serial ava-test/*.js`
- [x] remove the old `test/` folder, and run `git mv ava-test/ test/`
- [x] remove the `run-tests` script and change `npm test` to run only `ava --serial test/*.js` | 1.0 | Switch to the ava test framework - This is a bug to track the progress of switching to the ava test framework.
Here is the proposed approach:
- [x] make a directory called `ava-test/`
- [x] copy the resources to `ava-test/resources/` (leave a copy where it is now, too)
- [x] one by one, remove a file from `test/` and put its ava equivalent in `ava-test/`
- [x] modify `npm test`: instead of `node scripts/run-tests`, turn it into `node scripts/run-tests && ava --serial ava-test/*.js`
- [x] remove the old `test/` folder, and run `git mv ava-test/ test/`
- [x] remove the `run-tests` script and change `npm test` to run only `ava --serial test/*.js` | test | switch to the ava test framework this is a bug to track the progress of switching to the ava test framework here is the proposed approach make a directory called ava test copy the resources to ava test resources leave a copy where it is now too one by one remove a file from test and put its ava equivalent in ava test modify npm test instead of node scripts run tests turn it into node scripts run tests ava serial ava test js remove the old test folder and run git mv ava test test remove the run tests script and change npm test to run only ava serial test js | 1 |
435,796 | 30,520,317,962 | IssuesEvent | 2023-07-19 07:37:26 | yungd1plomat/AdvancedSharpAdbClient | https://api.github.com/repos/yungd1plomat/AdvancedSharpAdbClient | opened | Announcing the WinRT package of AdvancedSharpAdbClient | documentation enhancement | ## Announcing
We have packaged this project into winrt. With the winrt version, we can use it in cpp/winrt and other projects. You can find the winrt version in [`winrt branch`](https://github.com/yungd1plomat/AdvancedSharpAdbClient/tree/winrt).
## How to use it
There are two way to reference it.
- Reference to the project directly
Fork this repository and change the branch to `winrt`.
If your project is face to uwp, add this to your `.vcproj`
```xml
<ProjectReference Include="\path\to\AdvancedSharpAdbClient.WinRT.csproj">
<Project>{083cdc04-9cc2-46e4-84c2-55b645be9d50}</Project>
<SetTargetFramework>TargetFramework=uap10.0</SetTargetFramework>
</ProjectReference>
```
If your project is face to desktop, add this to your `.vcproj`
```xml
<ProjectReference Include="\path\to\AdvancedSharpAdbClient.WinRT.csproj">
<Project>{083cdc04-9cc2-46e4-84c2-55b645be9d50}</Project>
<SetTargetFramework>TargetFramework=net6.0-windows10.0.17763.0</SetTargetFramework>
</ProjectReference>
```
- Reference to the nuget package
Download [AdvancedSharpAdbClient.WinRT.zip](https://github.com/yungd1plomat/AdvancedSharpAdbClient/files/12092217/AdvancedSharpAdbClient.WinRT.0.0.1.zip).
Unzip it into `nupkgs` folder of the root path of your project
Create `nuget.config` into the root path of your project and add
```xml
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<packageSources>
<add key="Offline Nugets" value="nupkgs" />
</packageSources>
</configuration>
```
Open the manager of nuget and you will find it. Just install it like a normal nuget.
| 1.0 | Announcing the WinRT package of AdvancedSharpAdbClient - ## Announcing
We have packaged this project into winrt. With the winrt version, we can use it in cpp/winrt and other projects. You can find the winrt version in [`winrt branch`](https://github.com/yungd1plomat/AdvancedSharpAdbClient/tree/winrt).
## How to use it
There are two way to reference it.
- Reference to the project directly
Fork this repository and change the branch to `winrt`.
If your project is face to uwp, add this to your `.vcproj`
```xml
<ProjectReference Include="\path\to\AdvancedSharpAdbClient.WinRT.csproj">
<Project>{083cdc04-9cc2-46e4-84c2-55b645be9d50}</Project>
<SetTargetFramework>TargetFramework=uap10.0</SetTargetFramework>
</ProjectReference>
```
If your project is face to desktop, add this to your `.vcproj`
```xml
<ProjectReference Include="\path\to\AdvancedSharpAdbClient.WinRT.csproj">
<Project>{083cdc04-9cc2-46e4-84c2-55b645be9d50}</Project>
<SetTargetFramework>TargetFramework=net6.0-windows10.0.17763.0</SetTargetFramework>
</ProjectReference>
```
- Reference to the nuget package
Download [AdvancedSharpAdbClient.WinRT.zip](https://github.com/yungd1plomat/AdvancedSharpAdbClient/files/12092217/AdvancedSharpAdbClient.WinRT.0.0.1.zip).
Unzip it into `nupkgs` folder of the root path of your project
Create `nuget.config` into the root path of your project and add
```xml
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<packageSources>
<add key="Offline Nugets" value="nupkgs" />
</packageSources>
</configuration>
```
Open the manager of nuget and you will find it. Just install it like a normal nuget.
| non_test | announcing the winrt package of advancedsharpadbclient announcing we have packaged this project into winrt with the winrt version we can use it in cpp winrt and other projects you can find the winrt version in how to use it there are two way to reference it reference to the project directly fork this repository and change the branch to winrt if your project is face to uwp add this to your vcproj xml targetframework if your project is face to desktop add this to your vcproj xml targetframework reference to the nuget package download unzip it into nupkgs folder of the root path of your project create nuget config into the root path of your project and add xml open the manager of nuget and you will find it just install it like a normal nuget | 0 |
50,896 | 12,601,912,452 | IssuesEvent | 2020-06-11 10:43:09 | googleapis/nodejs-spanner | https://api.github.com/repos/googleapis/nodejs-spanner | closed | Mocha Tests: should delete a row from an example table using a DML statement failed | api: spanner buildcop: issue priority: p1 type: bug | Note: #1000 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
----
commit: 8973cbcc9158b37650af2edb6015c575da1cc3ec
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/8ddd9032-02b7-43d0-9fd1-2d1e7b9a7841), [Sponge](http://sponge2/8ddd9032-02b7-43d0-9fd1-2d1e7b9a7841)
status: failed
<details><summary>Test output</summary><br><pre>expected 'Successfully deleted 0 record.\n' to match /Successfully deleted 1 record\./
AssertionError: expected 'Successfully deleted 0 record.\n' to match /Successfully deleted 1 record\./
at Context.it (system-test/spanner.test.js:544:12)</pre></details> | 1.0 | Mocha Tests: should delete a row from an example table using a DML statement failed - Note: #1000 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
----
commit: 8973cbcc9158b37650af2edb6015c575da1cc3ec
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/8ddd9032-02b7-43d0-9fd1-2d1e7b9a7841), [Sponge](http://sponge2/8ddd9032-02b7-43d0-9fd1-2d1e7b9a7841)
status: failed
<details><summary>Test output</summary><br><pre>expected 'Successfully deleted 0 record.\n' to match /Successfully deleted 1 record\./
AssertionError: expected 'Successfully deleted 0 record.\n' to match /Successfully deleted 1 record\./
at Context.it (system-test/spanner.test.js:544:12)</pre></details> | non_test | mocha tests should delete a row from an example table using a dml statement failed note was also for this test but it was closed more than days ago so i didn t mark it flaky commit buildurl status failed test output expected successfully deleted record n to match successfully deleted record assertionerror expected successfully deleted record n to match successfully deleted record at context it system test spanner test js | 0 |
145,575 | 5,578,157,366 | IssuesEvent | 2017-03-28 11:38:25 | k0shk0sh/FastHub | https://api.github.com/repos/k0shk0sh/FastHub | closed | Milestones Creation Issue | Priority: High Status: Accepted Status: In Progress Type: Enhancement | Hey man, I have noticed i can no longer add a description for a milestone within the app. For now you have to ask for due date and tittle. Is it possible you can add another text heading and text field so we can add description for milestones within the application.
Screenshot: https://drive.google.com/file/d/0B7eMBI2WGcwMOTZsZEZnY09KSE0/view?usp=drivesdk | 1.0 | Milestones Creation Issue - Hey man, I have noticed i can no longer add a description for a milestone within the app. For now you have to ask for due date and tittle. Is it possible you can add another text heading and text field so we can add description for milestones within the application.
Screenshot: https://drive.google.com/file/d/0B7eMBI2WGcwMOTZsZEZnY09KSE0/view?usp=drivesdk | non_test | milestones creation issue hey man i have noticed i can no longer add a description for a milestone within the app for now you have to ask for due date and tittle is it possible you can add another text heading and text field so we can add description for milestones within the application screenshot | 0 |
122,826 | 26,171,655,712 | IssuesEvent | 2023-01-02 01:05:30 | yakra/DataProcessing | https://api.github.com/repos/yakra/DataProcessing | opened | path as argument | code organization C++ | There's still a function somewhere out there that receives Args::SomePathOrOther as an argument and then appends the filename to that.
Remove the arg and just have the function itself look up the path in Args directly. | 1.0 | path as argument - There's still a function somewhere out there that receives Args::SomePathOrOther as an argument and then appends the filename to that.
Remove the arg and just have the function itself look up the path in Args directly. | non_test | path as argument there s still a function somewhere out there that receives args somepathorother as an argument and then appends the filename to that remove the arg and just have the function itself look up the path in args directly | 0 |
286,129 | 21,564,339,832 | IssuesEvent | 2022-05-01 16:40:18 | sawshep/sawsge | https://api.github.com/repos/sawshep/sawsge | opened | Debug messages | documentation | Sawsge should have some debug messages to inform the user of the progress and results of builds. | 1.0 | Debug messages - Sawsge should have some debug messages to inform the user of the progress and results of builds. | non_test | debug messages sawsge should have some debug messages to inform the user of the progress and results of builds | 0 |
Subsets and Splits